Related
I installed the new update on my rooted phone accidentally and it went into a bootloop. I went into recovery mode and clicked erase cache, but my phone died before it was done erasing. Now whenever I start my phone after the ASUS loading screen, and sleeping android with a red warning signal and the text 'ERROR' start flashing every three seconds. I can get to the bootloader screen fine, but when I click recovery mode and the phone restarts, its just shows the blinking android error screen and I can get the recovery mode option by pressing power+up.
When plugged into my computer, adb doesn't recognize a device is connected (I have all the drivers). So I'm stuck right now.
Please any help would be greatly appreciated!
Same thing happened to me, finally while in the bootloader I used fastboot to restore it, I used the big ZIP file from Asus website and did a fastboot sideload of it
fastboot?
How do I go into fastboot from bootloader?
Thanks!
You are in the bootloader, it should display "waiting for fastboot command" or something like this, in a command prompt on your PC type "fastboot devices" and your devive should appear there.
Next
Magister54 said:
You are in the bootloader, it should display "waiting for fastboot command" or something like this, in a command prompt on your PC type "fastboot devices" and your devive should appear there.
Click to expand...
Click to collapse
kk perfect it shows my device, what do I exactly type to sideload the zip? I placed the zip file in the adb folder. Do I type 'adb sideload xxx.zip' ?
argh no you can only sideload from ADB, you must go into recovery to use adb sideload, you cannot use it from fastboot
In recovery mode you have to select "apply update from ADB" first
Magister54 said:
argh no you can only sideload from ADB, you must go into recovery to use adb sideload, you cannot use it from fastboot
In recovery mode you have to select "apply update from ADB" first
Click to expand...
Click to collapse
From bootloader I go to recovery mode, it restarts goes to the error screen, but when I press power+up nothing happens. The error screen just keeps blinking. If I can just get into recovery mode ugh
G0BI said:
From bootloader I go to recovery mode, it restarts goes to the error screen, but when I press power+up nothing happens. The error screen just keeps blinking. If I can just get into recovery mode ugh
Click to expand...
Click to collapse
Ok, it took me a few minutes to get into stock recovery, too! From bootloader, boot into recovery. Wait for the "installing update" screen to turn to Android error bot. Then hold down power button and quickly press volume up and then release both buttons at the same time! If done correctly, you'll successfully boot into stock recovery. If not, keep trying! It can take a while to get the timing right. Stock recovery on this device is very annoying!
Blinking Error Screen
rlaw said:
Ok, it took me a few minutes to get into stock recovery, too! From bootloader, boot into recovery. Wait for the "installing update" screen to turn to Android error bot. Then hold down power button and quickly press volume up and then release both buttons at the same time! If done correctly, you'll successfully boot into stock recovery. If not, keep trying! It can take a while to get the timing right. Stock recovery on this device is very annoying!
Click to expand...
Click to collapse
So the blinking Error screen isn't a problem? I've gotten into stock recovery before pretty easily, but the error screen wasn't blinking when I got in.
G0BI said:
So the blinking Error screen isn't a problem? I've gotten into stock recovery before pretty easily, but the error screen wasn't blinking when I got in.
Click to expand...
Click to collapse
No, it's not a problem! I thought it was as well, no worries - easy mistake to make, especially since getting into recovery mode from that screen can be tricky!
Easy way
Works with problems regarding wipe cache sudden hang or reload and showing android robot with "error" message + no recovery options avilable.
http://forum.xda-developers.com/zenfone2/general/asus-zenfone-2-flashing-recovery-mode-t3096596
get zenfone 2 into fastboot mode (volume + and power) and connect to your windows machine (usb)
install adb drivers and 15 sec package from the link
now go to c: drive and find the abd folder
in that drag fastboot and drop in command prompt *(administrator)
now type fastboot device
you sholud see a device
then type
1) fastboot erase cache
2) fastboot reload
now phone will restart and show error then remove usb cable and switch off the phone
after 10 sec turn on the phone and you will be back...
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
@varunanduri.......... You are a GOD! Nothing from the web helped me except this comment.
Hello.
I need your help.
I bought this phone (Asus Zenfone 2 ZE551ML 4GB/32GB 1.8Ghz) recently on online store. It is CN version but it already came with WW firmware, but not the latest (I believe it was WW 2.20.40.90 but I'm not sure).
Then I tried to update to the latest WW version 2.20.40.139 by putting firmware zip file from asus site in internal memory. The phone recognized this update and started to upgrade. When it reboot, I got an error of a blinking droid with the word "Error" below, and the phone doesn't boot anymore.
I can get to fastboot mode, but no to recovery mode. When trying to enter recovery, I got some errors (cannot mount /cache...) and it goes back to the blinking droid.
I cannot insert images and urls so the text errors include E:failed to mount /cache (Invalid Argument) various times
In fastboot mode I tried erase cache, format cache, format userdata, flashing latest WW recovery, boot, fastboot and system, but nothing resolved issue of blinking droid with error.
I tried other how to that uses a CWM recovery and I can get to that recovery, can clean and wipe, tried installing asus zip firmware from external sd (WW and CN) but without success (I believe it had CN recovery SKU but WW firmware -is this possible?). After rebooting the phone is still in the same error (blinking droid).
Here is fastboot messages (format userdata gave an error):
Code:
C:\adb>fastboot devices
F5AZFG27Z395 fastboot
C:\adb>fastboot flash recovery recovery.img
target reported max download size of 536870912 bytes
sending 'recovery' (11882 KB)...
OKAY [ 0.610s]
writing 'recovery'...
OKAY [ 0.470s]
finished. total time: 1.080s
C:\adb>fastboot flash boot boot.img
target reported max download size of 536870912 bytes
sending 'boot' (11870 KB)...
OKAY [ 0.610s]
writing 'boot'...
OKAY [ 0.450s]
finished. total time: 1.060s
C:\adb>fastboot flash fastboot droidboot.img
target reported max download size of 536870912 bytes
sending 'fastboot' (14824 KB)...
OKAY [ 0.700s]
writing 'fastboot'...
OKAY [ 0.460s]
finished. total time: 1.170s
C:\adb>fastboot flash system system.img
target reported max download size of 536870912 bytes
erasing 'system'...
OKAY [ 1.220s]
sending sparse 'system' (524056 KB)...
OKAY [ 18.310s]
writing 'system'...
OKAY [ 11.970s]
sending sparse 'system' (517822 KB)...
OKAY [ 17.540s]
writing 'system'...
OKAY [ 12.340s]
sending sparse 'system' (520627 KB)...
OKAY [ 17.560s]
writing 'system'...
OKAY [ 10.890s]
sending sparse 'system' (522703 KB)...
OKAY [ 17.630s]
writing 'system'...
OKAY [ 10.910s]
sending sparse 'system' (154528 KB)...
OKAY [ 5.450s]
writing 'system'...
OKAY [ 3.500s]
finished. total time: 127.320s
C:\adb>fastboot reboot
rebooting...
finished. total time: 0.110s
C:\adb>fastboot devices
F5AZFG27Z395 fastboot
C:\adb>fastboot erase cache
******** Did you mean to fastboot format this partition?
erasing 'cache'...
OKAY [ 0.490s]
finished. total time: 0.490s
C:\adb>fastboot format cache
Creating filesystem with parameters:
Size: 268435456
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 1024
Label:
Blocks: 65536
Block groups: 2
Reserved block group size: 15
Created filesystem with 11/16384 inodes and 2089/65536 blocks
target reported max download size of 536870912 bytes
erasing 'cache'...
OKAY [ 0.390s]
sending 'cache' (6248 KB)...
OKAY [ 0.410s]
writing 'cache'...
OKAY [ 0.390s]
finished. total time: 1.190s
C:\adb>fastboot erase cache
******** Did you mean to fastboot format this partition?
erasing 'cache'...
OKAY [ 0.400s]
finished. total time: 0.410s
C:\adb>fastboot devices
F5AZFG27Z395 fastboot
C:\adb>fastboot format userdata
Creating filesystem with parameters:
Size: 27984359424
Block size: 4096
Blocks per group: 32768
Inodes per group: 8176
Inode size: 256
Journal blocks: 32768
Label:
Blocks: 6832119
Block groups: 209
Reserved block group size: 1024
Created filesystem with 11/1708784 inodes and 151285/6832119 blocks
target reported max download size of 536870912 bytes
erasing 'userdata'...
OKAY [ 4.290s]
sending 'userdata' (139033 KB)...
OKAY [ 4.600s]
writing 'userdata'...
FAILED (remote: flash_cmds error!
)
finished. total time: 9.180s
C:\adb>fastboot format cache
Creating filesystem with parameters:
Size: 268435456
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 1024
Label:
Blocks: 65536
Block groups: 2
Reserved block group size: 15
Created filesystem with 11/16384 inodes and 2089/65536 blocks
target reported max download size of 536870912 bytes
erasing 'cache'...
OKAY [ 0.370s]
sending 'cache' (6248 KB)...
OKAY [ 0.420s]
writing 'cache'...
OKAY [ 0.380s]
finished. total time: 1.170s
C:\adb>fastboot format userdata
Creating filesystem with parameters:
Size: 27984359424
Block size: 4096
Blocks per group: 32768
Inodes per group: 8176
Inode size: 256
Journal blocks: 32768
Label:
Blocks: 6832119
Block groups: 209
Reserved block group size: 1024
Created filesystem with 11/1708784 inodes and 151285/6832119 blocks
target reported max download size of 536870912 bytes
erasing 'userdata'...
OKAY [ 4.050s]
sending 'userdata' (139033 KB)...
OKAY [ 4.490s]
writing 'userdata'...
FAILED (remote: flash_cmds error!
)
finished. total time: 8.840s
C:\adb>fastboot reboot
rebooting...
finished. total time: 0.108s
C:\adb>
Is there a way to get the phone working again?
Thank you very much.
After flashing the recovery image, you should be able to get into the recovery mode, and sideload the full zip file. Don't flash the system image.
KillerNo2 said:
After flashing the recovery image, you should be able to get into the recovery mode, and sideload the full zip file. Don't flash the system image.
Click to expand...
Click to collapse
Before flashing WW 2.20.40.139 recovery, boot, fastboot and system, I tried flashing only recovery, boot and fastboot from WW 2.20.40.90 but couldn't also get into recovery mode. Always the same error.
Maybe the firmware zip file I copied previously (when the phone was working) to the internal memory was somehow corrupted and it remains there?
Is there anything more I could do?
Thank you very much.
cdiogooliveira said:
Before flashing WW 2.20.40.139 recovery, boot, fastboot and system, I tried flashing only recovery, boot and fastboot from WW 2.20.40.90 but couldn't also get into recovery mode. Always the same error.
Maybe the firmware zip file I copied previously (when the phone was working) to the internal memory was somehow corrupted and it remains there?
Is there anything more I could do?
Thank you very much.
Click to expand...
Click to collapse
I think you should've updated to version .97 first. So download .97 recovery from here,and try it again.
Hello KillerNo2
Could you please share another link, because the one you posted in not working?
Thank you.
cdiogooliveira said:
Hello KillerNo2
Could you please share another link, because the one you posted in not working?
Thank you.
Click to expand...
Click to collapse
It works now.
KillerNo2 said:
It works now.
Click to expand...
Click to collapse
Hello. Recovery .97 didn't work also. It has always the blinking droid and doesn't boot.
I could run tethered (without install) TWRP recovery and tried to install full zip rom, but TWRP couldn't also access /cache partition. TWRP cannot mount cache and system partitions.
Anyone can help?
Thank you very much.
Hi, that's my first customisation:
1. Device unlocked:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
2. TWRP flashed + *zip ready on /sdcard1
3. Install Zip fails
The checksums of all zips are ok, verified on my notebook.
I also can't wipe. And the standard Android 7.1 is recovering itself, if I boot-up.
Please advise, thanks!
1. Try unchecking signature verification in TWRP
2. Most likely, you will have to downgrade to CM13.1 first with that mounting error
3. I recommend using the standard LOS zip, it seems you have one with microG embedded
SECURE BOOT - enabled — Am I root?
kabu83 said:
1. Try unchecking signature verification in TWRP
2. Most likely, you will have to downgrade to CM13.1 first with that mounting error
3. I recommend using the standard LOS zip, it seems you have one with microG embedded
Click to expand...
Click to collapse
Thanks, I did all that and much more, trying to install CM 13.1, crDroid, OrangeFox, SuperSu => nothing installs!
Now I wonder: Am I root at all? I thought so, since I installed TWRP on a naked device?!
The bootloader shows: DEVICE STATE - unlocked
The Problem is, that TWRP cannot mount /system in the first place.
Have you tried downgrading following these steps: https://forum.xda-developers.com/showpost.php?p=72261104
TWRP cannot mount /system
kabu83 said:
The Problem is, that TWRP cannot mount /system in the first place.
Have you tried downgrading following these steps: https://forum.xda-developers.com/showpost.php?p=72261104
Click to expand...
Click to collapse
Now, that my holidays are over, I want this Crackling to crack!
Here my efforts to crack it via Fastboot:
Since the vintage Cyanogen fails as well as the state of the art Linage, I suspect that the payload might not be the cause for the failure?!
Code:
# fastboot flash system lineage-16.0-20190826-microG-crackling.zip
target reported max download size of 268435456 bytes
Invalid sparse file format at header magic
error: write_sparse_skip_chunk: don't care size 271225615 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 2794255 is not a multiple of the block size 4096
erasing 'system'...
OKAY [ 0.841s]
sending sparse 'system' 1/3 (262140 KB)...
error: write_sparse_skip_chunk: don't care size 271225615 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 271225615 is not a multiple of the block size 4096
OKAY [ 8.258s]
writing 'system' 1/3...
FAILED (remote: buffer overreads occured due to invalid sparse header)
finished. total time: 16.173s
# fastboot erase system
******** Did you mean to fastboot format this ext4 partition?
erasing 'system'...
OKAY [ 1.042s]
finished. total time: 1.043s
# fastboot flash system SW27-WF-CRACKLING-CM-13.1.5-ZNH2KAS7EB-RECOVERY.zip
target reported max download size of 268435456 bytes
Invalid sparse file format at header magic
error: write_sparse_skip_chunk: don't care size 619158578 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 350727218 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 82295858 is not a multiple of the block size 4096
erasing 'system'...
OKAY [ 0.831s]
sending sparse 'system' 1/4 (262140 KB)...
error: write_sparse_skip_chunk: don't care size 619158578 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 619158578 is not a multiple of the block size 4096
OKAY [ 8.290s]
writing 'system' 1/4...
FAILED (remote: buffer overreads occured due to invalid sparse header)
finished. total time: 14.176s
# fastboot erase recovery
erasing 'recovery'...
OKAY [ 0.205s]
finished. total time: 0.205s
# fastboot flash recovery twrp-3.3.1-0-crackling.img
target reported max download size of 268435456 bytes
sending 'recovery' (16984 KB)...
OKAY [ 0.563s]
writing 'recovery'...
OKAY [ 1.188s]
finished. total time: 1.751s
# fastboot boot twrp-3.3.1-0-crackling.img
downloading 'boot.img'...
OKAY [ 0.535s]
booting...
OKAY [ 0.672s]
finished. total time: 1.208s
Boot to recovery (TWRP), then touch the bottom right menu button, what does it say in the terminal log? (Similar to the 2nd screenshot you posted.)
Bootloader vs BIOS
kabu83 said:
Boot to recovery (TWRP), then touch the bottom right menu button, what does it say in the terminal log? (Similar to the 2nd screenshot you posted.)
Click to expand...
Click to collapse
At the time of the Cyanogen/Linage installation I had no TWRP installed! Would it help to repeat the process?
In general, I assumed the Bootloader to function similar to the BIOS at a PC? That makes me wonder, why an Android installation-process via Fastboot can't just reformat the entire drive and do a fresh partitioning? (instead of complaining about 'chunks' and 'block-sizes')
Thanks for all your assistance, most appreciated! :good:
[email protected] said:
At the time of the Cyanogen/Linage installation I had no TWRP installed! Would it help to repeat the process?
In general, I assumed the Bootloader to function similar to the BIOS at a PC? That makes me wonder, why an Android installation-process via Fastboot can't just reformat the entire drive and do a fresh partitioning? (instead of complaining about 'chunks' and 'block-sizes')
Thanks for all your assistance, most appreciated! :good:
Click to expand...
Click to collapse
I would recommend installing TWRP, Version 3.2.1-0.
Then boot to recovery and check, if TWRP can mount the system Partition.
What OS do you have currentyl installed?
/system is empty
kabu83 said:
I would recommend installing TWRP, Version 3.2.1-0.
Then boot to recovery and check, if TWRP can mount the system Partition.
What OS do you have currently installed?
Click to expand...
Click to collapse
As mentioned, I prefer a clean install. Thus formatted /system with ext4 via Fastboot (it's default). It should be possible to mount an empty /system -- isn't it?
A clean install is needed anyway. It seems just easier to install the OS via TWRP and for future nightly updates anyway.
Heureka!
kabu83 said:
I would recommend installing TWRP, Version 3.2.1-0.
Click to expand...
Click to collapse
With TWRP 3.2.1-0 I managed to install SW27-WF-CRACKLING-CM-13.1.5-ZNH2KAS7EB-RECOVERY.zip :good:
(I failed though to install "lineage-16.0-20190826-microG-crackling.zip" before.)
What's next? Replacing Cyanogen Bootloader with TWRP 3.2.1-0 again?
Then trying a pure Lineage and later Gapps seperately?
[email protected] said:
With TWRP 3.2.1-0 I managed to install SW27-WF-CRACKLING-CM-13.1.5-ZNH2KAS7EB-RECOVERY.zip :good:
(I failed though to install "lineage-16.0-20190826-microG-crackling.zip" before.)
What's next? Replacing Cyanogen Bootloader with TWRP 3.2.1-0 again?
Then trying a pure Lineage and later Gapps seperately?
Click to expand...
Click to collapse
Can you boot into CM 13 now?
Has it replaced TWRP as recovery?
Bingo!
kabu83 said:
Can you boot into CM 13 now?
Has it replaced TWRP as recovery?
Click to expand...
Click to collapse
I've got Cyanogen Fastboot, Lineage Bootloader, and Lineage Crackling 190801.002 up and running… :good:
With CM 13 installed, TWRP directly installed "lineage-16.0-20190826-microG-crackling.zip" from SD-card.
Thanks again for your advice, it appears that the Android System which Google offers as update to CM13, indeed prevented the alternative OS installation somehow.
[email protected] said:
I've got Cyanogen Fastboot, Lineage Bootloader, and Lineage Crackling 190801.002 up and running… :good:
With CM 13 installed, TWRP directly installed "lineage-16.0-20190826-microG-crackling.zip" from SD-card.
Thanks again for your advice, it appears that the Android System which Google offers as update to CM13, indeed prevented the alternative OS installation somehow.
Click to expand...
Click to collapse
Happy to help. So you are all set now?
Things are changing with the advent of project treble and seamless updates. OnePlus will no longer release ROMs flashable via recovery (either stock) because is no more needed. The updates will be done on the slot not used for example if you are using slot a the update will be installed on slot b and the slot b will be set as default. If you brick and you are in bootloop how you can restore the rom? You can't with Stock ROM you have, because the zip can be only installed via Update Engine, so what can you do? Flash a stock rom via fastboot. I have extracted all images from the stock zip and i have made a new zip with the Fastboot ROM with a flash-all.bat included. This will work only if your bootloader is unlocked. This will erase all your data and will wipe your internal storage.
HOW TO FLASH
This version is only for not branded devices
Download the zip;
Unpack the zip in a folder;
Reboot the OnePlus 7T in fastboot-bootloader mode (Power and volume + and volume-);
Connect the OnePlus 7T to PC;
Run flash-all.bat flasher you need;
Wait until the process end;
The phone will automatically reboot.
DOWNLOAD
All roms on AFH: https://www.androidfilehost.com/?w=files&flid=300020
All roms on Sourceforge: https://sourceforge.net/projects/fastbootroms/files/OnePlus 7T
BRANDED PHONE
For now branded device are not supported
MANUAL FLASH: Windows - OSX - Linux
If you want to manual flash these roms these are the commands (You need the latest sdk platform tools, you can find it here
Is reccomended to format data or the rom cannot boot:
Code:
fastboot -w
Others Commands to flash a fastboot rom
Code:
fastboot flash aop aop.img
fastboot flash bluetooth bluetooth.img
fastboot flash boot boot.img
fastboot flash dsp dsp.img
fastboot flash dtbo dtbo.img
fastboot flash LOGO LOGO.img
fastboot flash modem modem.img
fastboot flash oem_stanvbk oem_stanvbk.img
fastboot flash qupfw qupfw.img
fastboot flash storsec storsec.img
fastboot flash multiimgoem multiimgoem.img
fastboot flash uefisecapp uefisecapp.img
fastboot flash recovery recovery.img
fastboot --disable-verity flash vbmeta vbmeta.img
fastboot --disable-verity flash vbmeta_system vbmeta_system.img
fastboot flash opproduct opproduct.img
fastboot reboot fastboot
fastboot flash system system.img
fastboot flash vendor vendor.img
fastboot flash product product.img
fastboot reboot
REMEMBER
"Invalid sparce file format at header magic" is not an error, you need to wait a bit when you see that string, just wait.
If the device automatically reboot in Stock Recovery mode don't reboot it and wait the flash end.
These ROMs can't be used to update or downgrade your phone but just to restore your phone.
If the rom seems doesn't start go in recovery stock and follow this guideline: English -> Wipe data and cache -> Erase everything.
If you want to rebrand your phone from HydrogenOS to OxygenOS you can follow this guide: Rebrand Guide
If you want you can use also my tool to flash Factory Images, unlock bootloader, flash twrp or to understand if the device is recognized: https://toolaio.tk/
If you got some problems like write error or no partition, check this: https://forum.xda-developers.com/showpost.php?p=76658555&postcount=34
DONATE LINK
If you want to support this and others my projects please consider making a donation, thanks.
Unfortunately i have not tested this fastboot rom, i did some tests with an user and nothing else, actually you can't flash from normal fastboot mode system, vendor and product images, you need to use "fastboot reboot fastboot" command to reboot in stock recovery with fastbootd enabled, after that using the fastboot commands you can flash system, vendor and product images.
If you have any problems with this fastboot rom or you see errors during the script execution, contact me
Really thanks for this.
Any update on root ?
RohanAJoshi said:
Really thanks for this.
Any update on root ?
Click to expand...
Click to collapse
Unfortunately no, i will check in the next hours, but without a tester should be not easy
mauronofrio said:
Unfortunately no, i will check in the next hours, but without a tester should be not easy
Click to expand...
Click to collapse
I have device.
I can test.
I will pm you my telegram id.
Please check.
Edit : can't pm
My telegram id
RohanAJoshi7
"This will work only if your bootloader is unlocked."
Supposed someone gets into trouble - as seen in another thread with a bricked device.
Wouldn't that happen usually if the bootloader is unlocked?
Like if someone want to do some modifications/tweaking, I believe it requuires to unlock the bootloader.
What other scenario could be happening to get into issues with and locked bootloader?
Please excuse the lack of knowledge on a/b partitions and stuff.
Thank you.
Wifi and speaker did not work anymore after messing with the magisk compatible boot image and/or update to 10.0.3. This fixed it for me, thanks!
Small note though, I was using older drivers which caused some errors while running the bat script. Namely "Flashing is not allowed for Critical Partitions" and " Failed to boot into userspace fastboot; one or more components might be unbootable". After running the 15 seconds adb installer and running the script again everything worked fine: https://forum.xda-developers.com/showthread.php?t=2588979
Rescla said:
Wifi and speaker did not work anymore after messing with the magisk compatible boot image and/or update to 10.0.3. This fixed it for me, thanks!
Small note though, I was using older drivers which caused some errors while running the bat script. Namely "Flashing is not allowed for Critical Partitions" and " Failed to boot into userspace fastboot; one or more components might be unbootable". After running the 15 seconds adb installer and running the script again everything worked fine: https://forum.xda-developers.com/showthread.php?t=2588979
Click to expand...
Click to collapse
please help me Bro My wifi is not working and if someone calls me it auto rejected all call
Do you want to wipe all the data ( Reccomended )[Y/N]?y
Erasing 'userdata' OKAY [ 0.421s]
mke2fs 1.44.4 (18-Aug-2018)
Creating filesystem with 56734085 4k blocks and 14188544 inodes
Filesystem UUID: 63051112-f179-11e9-b2d0-d132c7036180
Superblock backups stored on blocks:
32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208,
4096000, 7962624, 11239424, 20480000, 23887872
Allocating group tables: done
Writing inode tables: done
Creating journal (262144 blocks): done
Writing superblocks and filesystem accounting information: done
Sending 'userdata' (5024 KB) OKAY [ 0.125s]
Writing 'userdata' OKAY [ 0.000s]
Erasing 'metadata' OKAY [ 0.016s]
Erase successful, but not automatically formatting.
File system type raw not supported.
Finished. Total time: 1.638s
Sending 'aop' (200 KB) OKAY [ 0.016s]
Writing 'aop' OKAY [ 0.000s]
Finished. Total time: 0.031s
Sending 'bluetooth' (828 KB) OKAY [ 0.031s]
Writing 'bluetooth' OKAY [ 0.000s]
Finished. Total time: 0.078s
Sending 'boot_a' (98304 KB) OKAY [ 2.215s]
Writing 'boot_a' OKAY [ 0.421s]
Finished. Total time: 4.072s
Sending 'dsp' (65536 KB) OKAY [ 1.466s]
Writing 'dsp' OKAY [ 0.234s]
Finished. Total time: 2.496s
Sending 'cmnlib' (384 KB) OKAY [ 0.016s]
Writing 'cmnlib' FAILED (remote: 'Flashing is
not allowed for Critical Partitions
')
fastboot: error: Command failed
Sending 'cmnlib64' (500 KB) OKAY [ 0.031s]
Writing 'cmnlib64' FAILED (remote: 'Flashing is
not allowed for Critical Partitions
')
fastboot: error: Command failed
Sending 'devcfg' (52 KB) OKAY [ 0.000s]
Writing 'devcfg' FAILED (remote: 'Flashing is
not allowed for Critical Partitions
sandeep chauhan 2722 said:
please help me Bro My wifi is not working and if someone calls me it auto rejected all call
Do you want to wipe all the data ( Reccomended )[Y/N]?y
Erasing 'userdata' OKAY [ 0.421s]
mke2fs 1.44.4 (18-Aug-2018)
Creating filesystem with 56734085 4k blocks and 14188544 inodes
Filesystem UUID: 63051112-f179-11e9-b2d0-d132c7036180
Superblock backups stored on blocks:
32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208,
4096000, 7962624, 11239424, 20480000, 23887872
Allocating group tables: done
Writing inode tables: done
Creating journal (262144 blocks): done
Writing superblocks and filesystem accounting information: done
Sending 'userdata' (5024 KB) OKAY [ 0.125s]
Writing 'userdata' OKAY [ 0.000s]
Erasing 'metadata' OKAY [ 0.016s]
Erase successful, but not automatically formatting.
File system type raw not supported.
Finished. Total time: 1.638s
Sending 'aop' (200 KB) OKAY [ 0.016s]
Writing 'aop' OKAY [ 0.000s]
Finished. Total time: 0.031s
Sending 'bluetooth' (828 KB) OKAY [ 0.031s]
Writing 'bluetooth' OKAY [ 0.000s]
Finished. Total time: 0.078s
Sending 'boot_a' (98304 KB) OKAY [ 2.215s]
Writing 'boot_a' OKAY [ 0.421s]
Finished. Total time: 4.072s
Sending 'dsp' (65536 KB) OKAY [ 1.466s]
Writing 'dsp' OKAY [ 0.234s]
Finished. Total time: 2.496s
Sending 'cmnlib' (384 KB) OKAY [ 0.016s]
Writing 'cmnlib' FAILED (remote: 'Flashing is
not allowed for Critical Partitions
')
fastboot: error: Command failed
Sending 'cmnlib64' (500 KB) OKAY [ 0.031s]
Writing 'cmnlib64' FAILED (remote: 'Flashing is
not allowed for Critical Partitions
')
fastboot: error: Command failed
Sending 'devcfg' (52 KB) OKAY [ 0.000s]
Writing 'devcfg' FAILED (remote: 'Flashing is
not allowed for Critical Partitions
Click to expand...
Click to collapse
And others partitions?
mauronofrio said:
And others partitions?
Click to expand...
Click to collapse
flashing process stop here.
i also try to flash manually but when I give 4th command to flash "fastboot flash cmnlib cmnlib.img" it gives me error now I cany use my phone no sound no wifi no calls please help me
sandeep chauhan 2722 said:
flashing process stop here.
i also try to flash manually but when I give 4th command to flash "fastboot flash cmnlib cmnlib.img" it gives me error now I cany use my phone no sound no wifi no calls please help me
Click to expand...
Click to collapse
if some partition fail is not a problem, you should wait a bit
Found Solution
I download this file from support one plus https://support.oneplus.com/app/answers/detail/a_id/4583/kw/7t and install it from as Local upgrade from system update ( While bootloader is still unlock) and after it completed I reboot my device and Volla!! It works. I was also thinking to sideload same file in case local upgrade not work.
I am getting
Invalid sparse file format at header magic
Sending sparse 'system' 1/3 (784696 KB) OKAY [ 18.274s]
Writing 'system' FAILED (remote: 'Partition not found')
ANy ideas???
I can flash other partitions though
suzook said:
I am getting
Invalid sparse file format at header magic
Sending sparse 'system' 1/3 (784696 KB) OKAY [ 18.274s]
Writing 'system' FAILED (remote: 'Partition not found')
ANy ideas???
I can flash other partitions though
Click to expand...
Click to collapse
when the device reboot itself in recovery doesn't touch it.
mauronofrio said:
when the device reboot itself in recovery doesn't touch it.
Click to expand...
Click to collapse
I just tried fastboot flash system...it wouldnt work. But what di was the flashall. Thanks
After flashing the stock rom it boots up and everything seems fine. When I try to lock the bootloader I get the "Your device is corrupt. It can´t be trusted anymore and will not boot" I've unlocked the bootloader a few times tried reflashing stock rom but everytime I lock the bootloader I get that error message. Any ideas?
***Downloaded and Installed the stock rom through the system update in settings menu. Locked the bootloader without issues afterwards***
954wrecker said:
After flashing the stock rom it boots up and everything seems fine. When I try to lock the bootloader I get the "Your device is corrupt. It can´t be trusted anymore and will not boot" I've unlocked the bootloader a few times tried reflashing stock rom but everytime I lock the bootloader I get that error message. Any ideas?
***Downloaded and Installed the stock rom through the system update in settings menu. Locked the bootloader without issues afterwards***
Click to expand...
Click to collapse
So after flashed this fastboot rom, you should local update the original .zip rom to be sure that all partitions are replaced
I am stuck on the "The boot loader is unlocked....." and i tried to flash this but i am getting too many errors and post reboot its back on the same screen. Can anybody please help me?
Creating filesystem with parameters:
Size: 232382812160
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 32768
Label:
Blocks: 56734085
Block groups: 1732
Reserved block group size: 1024
Created filesystem with 11/14188544 inodes and 938604/56734085 blocks
target reported max download size of 805306368 bytes
Erase successful, but not automatically formatting.
Can't determine partition type.
FAILED (remote: GetVar Variable Not found)
erasing 'userdata'...
OKAY [ 0.688s]
sending 'userdata' (152025 KB)...
OKAY [ 3.922s]
writing 'userdata'...
OKAY [ 0.000s]
erasing 'cache'...
FAILED (remote: Check device console.)
finished. total time: 8.001s
error: cannot load 'aop.img'
error: cannot load 'bluetooth.img'
error: cannot load 'boot.img'
error: cannot load 'dsp.img'
error: cannot load 'cmnlib.img'
error: cannot load 'cmnlib64.img'
error: cannot load 'devcfg.img'
error: cannot load 'dtbo.img'
error: cannot load 'LOGO.img'
error: cannot load 'modem.img'
error: cannot load 'oem_stanvbk.img'
error: cannot load 'qupfw.img'
error: cannot load 'storsec.img'
error: cannot load 'multiimgoem.img'
error: cannot load 'hyp.img'
error: cannot load 'imagefv.img'
error: cannot load 'keymaster.img'
error: cannot load 'uefisecapp.img'
error: cannot load 'recovery.img'
fastboot: unknown option -- disable-verity
fastboot: unknown option -- disable-verity
error: cannot load 'opproduct.img'
error: cannot load 'tz.img'
usage: fastboot [ <option> ] <command>
commands:
update <filename> reflash device from update.zip
flashall flash boot, system, vendor and if found,
recovery
flash <partition> [ <filename> ] write a file to a flash partition
erase <partition> erase a flash partition
format[:[<fs type>][:[<size>]] <partition> format a flash partition.
Can override the fs type and/or
size the bootloader reports.
getvar <variable> display a bootloader variable
boot <kernel> [ <ramdisk> [ <second> ] ] download and boot kernel
flash:raw boot <kernel> [ <ramdisk> [ <second> ] ] create bootimage and
flash it
devices list all connected devices
continue continue with autoboot
reboot reboot device normally
reboot-bootloader reboot device into bootloader
help show this help message
options:
-w erase userdata and cache (and format
if supported by partition type)
-u do not first erase partition before
formatting
-s <specific device> specify device serial number
or path to device port
-l with "devices", lists device paths
-p <product> specify product name
-c <cmdline> override kernel commandline
-i <vendor id> specify a custom USB vendor id
-b <base_addr> specify a custom kernel base address.
default: 0x10000000
-n <page size> specify the nand page size.
default: 2048
-S <size>[K|M|G] automatically sparse files greater
than size. 0 to disable
error: cannot load 'system.img'
error: cannot load 'vendor.img'
error: cannot load 'product.img'
rebooting...
sathya said:
I am stuck on the "The boot loader is unlocked....." and i tried to flash this but i am getting too many errors and post reboot its back on the same screen. Can anybody please help me?
Creating filesystem with parameters:
Size: 232382812160
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 32768
Label:
Blocks: 56734085
Block groups: 1732
Reserved block group size: 1024
Created filesystem with 11/14188544 inodes and 938604/56734085 blocks
target reported max download size of 805306368 bytes
Erase successful, but not automatically formatting.
Can't determine partition type.
FAILED (remote: GetVar Variable Not found)
erasing 'userdata'...
OKAY [ 0.688s]
sending 'userdata' (152025 KB)...
OKAY [ 3.922s]
writing 'userdata'...
OKAY [ 0.000s]
erasing 'cache'...
FAILED (remote: Check device console.)
finished. total time: 8.001s
error: cannot load 'aop.img'
error: cannot load 'bluetooth.img'
error: cannot load 'boot.img'
error: cannot load 'dsp.img'
error: cannot load 'cmnlib.img'
error: cannot load 'cmnlib64.img'
error: cannot load 'devcfg.img'
error: cannot load 'dtbo.img'
error: cannot load 'LOGO.img'
error: cannot load 'modem.img'
error: cannot load 'oem_stanvbk.img'
error: cannot load 'qupfw.img'
error: cannot load 'storsec.img'
error: cannot load 'multiimgoem.img'
error: cannot load 'hyp.img'
error: cannot load 'imagefv.img'
error: cannot load 'keymaster.img'
error: cannot load 'uefisecapp.img'
error: cannot load 'recovery.img'
fastboot: unknown option -- disable-verity
fastboot: unknown option -- disable-verity
error: cannot load 'opproduct.img'
error: cannot load 'tz.img'
usage: fastboot [ <option> ] <command>
commands:
update <filename> reflash device from update.zip
flashall flash boot, system, vendor and if found,
recovery
flash <partition> [ <filename> ] write a file to a flash partition
erase <partition> erase a flash partition
format[:[<fs type>][:[<size>]] <partition> format a flash partition.
Can override the fs type and/or
size the bootloader reports.
getvar <variable> display a bootloader variable
boot <kernel> [ <ramdisk> [ <second> ] ] download and boot kernel
flash:raw boot <kernel> [ <ramdisk> [ <second> ] ] create bootimage and
flash it
devices list all connected devices
continue continue with autoboot
reboot reboot device normally
reboot-bootloader reboot device into bootloader
help show this help message
options:
-w erase userdata and cache (and format
if supported by partition type)
-u do not first erase partition before
formatting
-s <specific device> specify device serial number
or path to device port
-l with "devices", lists device paths
-p <product> specify product name
-c <cmdline> override kernel commandline
-i <vendor id> specify a custom USB vendor id
-b <base_addr> specify a custom kernel base address.
default: 0x10000000
-n <page size> specify the nand page size.
default: 2048
-S <size>[K|M|G] automatically sparse files greater
than size. 0 to disable
error: cannot load 'system.img'
error: cannot load 'vendor.img'
error: cannot load 'product.img'
rebooting...
Click to expand...
Click to collapse
You should extract all the rom
soft bricked oneplus 7t
mauronofrio said:
Things are changing with the advent of project treble and seamless updates. OnePlus will no longer release ROMs flashable via recovery (either stock) because is no more needed. The updates will be done on the slot not used for example if you are using slot a the update will be installed on slot b and the slot b will be set as default. If you brick and you are in bootloop how you can restore the rom? You can't with Stock ROM you have, because the zip can be only installed via Update Engine, so what can you do? Flash a stock rom via fastboot. I have extracted all images from the stock zip and i have made a new zip with the Fastboot ROM with a flash-all.bat included. This will work only if your bootloader is unlocked. This will erase all your data and will wipe your internal storage.
HOW TO FLASH
This version is only for not branded devices
Download the zip;
Unpack the zip in a folder;
Reboot the OnePlus 7T in fastboot-bootloader mode (Power and volume + and volume-);
Connect the OnePlus 7T to PC;
Run flash-all.bat flasher you need;
Wait until the process end;
The phone will automatically reboot.
DOWNLOAD
All roms on AFH: https://www.androidfilehost.com/?w=files&flid=300020
All roms on Sourceforge: https://sourceforge.net/projects/fastbootroms/files/OnePlus 7T
BRANDED PHONE
For now branded device are not supported
MANUAL FLASH: Windows - OSX - Linux
If you want to manual flash these roms these are the commands (You need the latest sdk platform tools, you can find it here
Is reccomended to format data or the rom cannot boot:
Code:
fastboot -w
Others Commands to flash a fastboot rom
Code:
fastboot flash aop aop.img
fastboot flash bluetooth bluetooth.img
fastboot flash boot boot.img
fastboot flash dsp dsp.img
fastboot flash dtbo dtbo.img
fastboot flash LOGO LOGO.img
fastboot flash modem modem.img
fastboot flash oem_stanvbk oem_stanvbk.img
fastboot flash qupfw qupfw.img
fastboot flash storsec storsec.img
fastboot flash multiimgoem multiimgoem.img
fastboot flash uefisecapp uefisecapp.img
fastboot flash recovery recovery.img
fastboot --disable-verity flash vbmeta vbmeta.img
fastboot --disable-verity flash vbmeta_system vbmeta_system.img
fastboot flash opproduct opproduct.img
fastboot reboot fastboot
fastboot flash system system.img
fastboot flash vendor vendor.img
fastboot flash product product.img
fastboot reboot
REMEMBER
"Invalid sparce file format at header magic" is not an error, you need to wait a bit when you see that string, just wait.
These ROMs can't be used to update or downgrade your phone but just to restore your phone.
If the rom seems doesn't start go in recovery stock and follow this guideline: English -> Wipe data and cache -> Erase everything.
If you want to rebrand your phone from HydrogenOS to OxygenOS you can follow this guide: Rebrand Guide
If you want you can use also my tool to flash Factory Images, unlock bootloader, flash twrp or to understand if the device is recognized: https://toolaio.tk/
If you got some problems like write error or no partition, check this: https://forum.xda-developers.com/showpost.php?p=76658555&postcount=34
DONATE LINK
If you want to support this and others my projects please consider making a donation, thanks.
Click to expand...
Click to collapse
Hi mauronofrio
I downloaded your version of twrp for my oneplus 7t and unlocked the bootloader in an attempt to change to Oxygen OS. Unfortunately the system, vendor and product partitions are locked and 0MB so seem to be stuck, can write to the /recovery directory but that's about it. I try to flash it but always get the mount error on those directories. I downloaded the rom in this post and extracted to a folder but not quite clear how to run the bat command.
Any clues or tips would be most appreciated. By the way I somehow deleted the recovery rom so can't even boot into Hydrogen OS anymore.
thanks
Dave
Hi All,
used my OP7T for a week before deciding to unlock. That went fine, but when I tried to flash a GSI (no custom ROMs available yet), it says partition not found?? Tried system and system_a.
Code:
[email protected]:~/Downloads/Android$ fastboot flash system system-quack-arm64-ab-vanilla.img
Sending sparse 'system' 1/3 (786428 KB) OKAY [ 24.933s]
Writing sparse 'system' 1/3 FAILED (remote: 'Partition not found')
Finished. Total time: 24.950s
[email protected]:~/Downloads/Android$ fastboot flash system_a Havoc-OS-3.0_ARM64-AB.img
Sending sparse 'system_a' 1/3 (786428 KB) OKAY [ 24.953s]
Writing sparse 'system_a' 1/3 FAILED (remote: 'Partition not found')
Finished. Total time: 24.965s
[email protected]:~/Downloads/Android$
Hey,
I have the same issue, did you ever find a solution?
You must unlock first
You don't say
In the meantime I found the actual solution, here it is for the record : reboot from fastboot to fastbootd using "fastboot reboot fastboot"
And then the commands will work
natinusala said:
You don't say
In the meantime I found the actual solution, here it is for the record : reboot from fastboot to fastbootd using "fastboot reboot fastboot"
And then the commands will work
Click to expand...
Click to collapse
Got: "fastboot: usage: unknown reboot target fastboot"
bump
SecondSon1 said:
Got: "fastboot: usage: unknown reboot target fastboot"
Click to expand...
Click to collapse
been messing all night with fastboot trying to get it to boot to fastbootd
i keep getting this same error and so my phone is currently bricked as i cannot install the
system.img or anything that follows. also tried booting to fastbootd by doing
fastboot reboot recovery but it cannot find reboot target recovery either.
this is what i did
dosnoventa said:
been messing all night with fastboot trying to get it to boot to fastbootd
i keep getting this same error and so my phone is currently bricked as i cannot install the
system.img or anything that follows. also tried booting to fastbootd by doing
fastboot reboot recovery but it cannot find reboot target recovery either.
Click to expand...
Click to collapse
i got it working
Please help
sathara said:
i got it working
Click to expand...
Click to collapse
I'm getting
remote: Failed operation not permitted
and
remote: value to large for defined data type please help
i had the same problem. solved it by flashing msm extended recovery to both slots. that recovery has option to enter fastbootd
altojd said:
i had the same problem. solved it by flashing msm extended recovery to both slots. that recovery has option to enter fastbootd
Click to expand...
Click to collapse
Can you share that recovery image?
I couldn't find it in the Rom files.
For my 600th post on XDA, I offer this info in hopes it will help.
This one is T-mobile. Don't know if it will help ort harm but it works for me.
I don't have both hands right now; yoiu'll have to search for yourself on how to enter "EDL" mode and possibly an MSM (or is it MDM?) version of stock flashable file for your model and carrier, else maybe try the T-Mobile one at your own risk: Unbrick Tool for T-Mobile
GOOD LUCK
Hi guys,
When I type ' fastboot reboot fastboot ' in windows command prompt, I got the help menu of fastboot, anyone got a solution ?
My phone (Redmi 9 Note Pro) is bricked because I can't flash a system.img
Booting into fastboot using volumedown + power isn't working.
OKAY [ 17.778s]
writing 'system'...
FAILED (remote: Partition not found)
josdehaes said:
Hi All,
used my OP7T for a week before deciding to unlock. That went fine, but when I tried to flash a GSI (no custom ROMs available yet), it says partition not found?? Tried system and system_a.
Code:
[email protected]:~/Downloads/Android$ fastboot flash system system-quack-arm64-ab-vanilla.img
Sending sparse 'system' 1/3 (786428 KB) OKAY [ 24.933s]
Writing sparse 'system' 1/3 FAILED (remote: 'Partition not found')
Finished. Total time: 24.950s
[email protected]:~/Downloads/Android$ fastboot flash system_a Havoc-OS-3.0_ARM64-AB.img
Sending sparse 'system_a' 1/3 (786428 KB) OKAY [ 24.953s]
Writing sparse 'system_a' 1/3 FAILED (remote: 'Partition not found')
Finished. Total time: 24.965s
[email protected]:~/Downloads/Android$
Click to expand...
Click to collapse
Did you find a solution ?
Download latest fastboot drivers.
From OS:
adb reboot fastboot
Or from bootloader
fastboot reboot fastboot
With devices launched on Android 10 there is a new interface called fastbootd, this is where you flash the system.
Lethien said:
Did you find a solution ?
Click to expand...
Click to collapse
clearly. there is a difference between "old" fastboot (bootloader) and fastbootd (userspace fastboot to support dynamic partitions). You need to be in fastbootd to do most stuff nowadays.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
My problem is bit different, can anybody help through this --- System partitioned doesn't exist !!!! while Gsi flashing on Realme 7 RMX2151
So when you see people posting in their tutorial;
fastboot reboot fastboot
NOW we type in;
fastboot reboot fastbootd?
No, same command, but you need stock recovery for this to work (twrp prevents fastbootd entry)
I tried for days to get to work but for TMobile follow guide on here and if it doesn't work even after you install drivers and all then use a different PC bc I have 7t and 8t OnePlus and my 8t unlocked works on my gf PC and her 7t TMobile works on mine figured that out the hard way but it's truthfully a solution when everything won't work
Levi0630 said:
I tried for days to get to work but for TMobile follow guide on here and if it doesn't work even after you install drivers and all then use a different PC bc I have 7t and 8t OnePlus and my 8t unlocked works on my gf PC and her 7t TMobile works on mine figured that out the hard way but it's truthfully a solution when everything won't work
Click to expand...
Click to collapse
Convert TMobile op7t to global using msmtool
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I found this in twrp official web site. I guess this is the reason that every time i try to install twrp and after that, my device get bootloop.
So how can i disable dm-verity?
(Sorry, my English may bad because we don't use that in our country)
Here is the file you need to flash it
zuhaibsarwar said:
Here is the file you need to flash it
Click to expand...
Click to collapse
Thanks you, but one more thing i need to ask
I tried many times to install LineageOS 18.1 with zip file (by twrp of course). I found out that my phone is a/b device, so i search on youtube "install custom rom on a/b devices" and follow step by step. But nothing happend, twrp still warn "no OS installed" and bootloop everytime
Please, if you know something i really want to use Lineage
cl3izv said:
I found this in twrp official web site. I guess this is the reason that every time i try to install twrp and after that, my device get bootloop.
So how can i disable dm-verity?
(Sorry, my English may bad because we don't use that in our country)
Click to expand...
Click to collapse
Everytime you install any custom ROM you always need to change slot .if you flash on a then switch to b and if flash on b switch to a
zuhaibsarwar said:
Everytime you install any custom ROM you always need to change slot .if you flash on a then switch to b and if flash on b switch to
Click to expand...
Click to collapse
i read your cmt about twrp, but yes, i use that twrp 3.4.0 file too but i got some problem
After fastboot boot twrp-3.4.0-0-PL2_sprout.img
Sending 'boot.img' (42412 KB) OKAY [ 1.206s]
Booting OKAY [ 5.049s]
Finished. Total time: 6.466s
Im stuck on android one screen
But when i return to download mode, i type:
fastboot flash recovery twrp-3.4.0-0-PL2_sprout.img (alway getting error)
fastboot boot twrp-3.4.0-0-PL2_sprout.img
I can go to twrp screen normally
Do you got any idea?
cl3izv said:
i read your cmt about twrp, but yes, i use that twrp 3.4.0 file too but i got some problem
After fastboot boot twrp-3.4.0-0-PL2_sprout.img
Sending 'boot.img' (42412 KB) OKAY [ 1.206s]
Booting OKAY [ 5.049s]
Finished. Total time: 6.466s
Im stuck on android one screen
But when i return to download mode, i type:
fastboot flash recovery twrp-3.4.0-0-PL2_sprout.img (alway getting error)
fastboot boot twrp-3.4.0-0-PL2_sprout.img
I can go to twrp screen normally
Do you got any idea?
Click to expand...
Click to collapse
Fastboot flash boot twrp.img
Fastboot reboot
It will take to TWRP now flash the lineage 18.1 and after flashing it successful with no errors change slot to b or a depends on which you flash lineage 18.1 and you will successful boot in lineage 18.1
If still failed i will try to make a full video of whole procedure by tomorrow morning
cl3izv said:
i read your cmt about twrp, but yes, i use that twrp 3.4.0 file too but i got some problem
After fastboot boot twrp-3.4.0-0-PL2_sprout.img
Sending 'boot.img' (42412 KB) OKAY [ 1.206s]
Booting OKAY [ 5.049s]
Finished. Total time: 6.466s
Im stuck on android one screen
But when i return to download mode, i type:
fastboot flash recovery twrp-3.4.0-0-PL2_sprout.img (alway getting error)
fastboot boot twrp-3.4.0-0-PL2_sprout.img
I can go to twrp screen normally
Do you got any idea?
Click to expand...
Click to collapse
cl3izv said:
i read your cmt about twrp, but yes, i use that twrp 3.4.0 file too but i got some problem
After fastboot boot twrp-3.4.0-0-PL2_sprout.img
Sending 'boot.img' (42412 KB) OKAY [ 1.206s]
Booting OKAY [ 5.049s]
Finished. Total time: 6.466s
Im stuck on android one screen
But when i return to download mode, i type:
fastboot flash recovery twrp-3.4.0-0-PL2_sprout.img (alway getting error)
fastboot boot twrp-3.4.0-0-PL2_sprout.img
I can go to twrp screen normally
Do you got any idea?
Click to expand...
Click to collapse
Fastboot flash boot twrp.img
Fastboot reboot
It will take to TWRP now flash the lineage 18.1 and after flashing it successful with no errors change slot to b or a depends on which you flash lineage 18.1 and you will successful boot in lineage 18.1
If still failed i will try to make a full video of whole procedure by tomorrow morning
Don't flash dm verification file here np needed just install twrp boot tp twrp flash lineage and change boot slot and boom enjoy 18.1
Lol my comment messed up
cl3izv said:
i read your cmt about twrp, but yes, i use that twrp 3.4.0 file too but i got some problem
After fastboot boot twrp-3.4.0-0-PL2_sprout.img
Sending 'boot.img' (42412 KB) OKAY [ 1.206s]
Booting OKAY [ 5.049s]
Finished. Total time: 6.466s
Im stuck on android one screen
But when i return to download mode, i type:
fastboot flash recovery twrp-3.4.0-0-PL2_sprout.img (alway getting error)
fastboot boot twrp-3.4.0-0-PL2_sprout.img
I can go to twrp screen normally
Do you got any idea?
Click to expand...
Click to collapse
I have another idea.i tried it before . don't install twrp simple go impulsion lineage and download lineage boot.img I mean lineage recovery .if you have SD card copy lineage on SD and after installing lineage recovery with these commands with adb
Fastboot flash boot lineage recovery.img
Fastboot reboot
And now in lineage recovery go to update and select lineage file and flash it after flashing in done simple reboot to lineage
Download latest recovery image of lineage os
LineageOS Downloads
download.lineageos.org
i will try, but also need your video, thank you
here the commands while i was flashing twrp on my mobile
C:\Users\480\OneDrive\Desktop\platform-tools>fastboot flash boot abc.img
Sending 'boot_b' (42412 KB) OKAY [ 4.609s]
Writing 'boot_b' OKAY [ 0.344s]
Finished. Total time: 12.000s
C:\Users\480\OneDrive\Desktop\platform-tools>fastboot reboot
Rebooting OKAY [ 0.000s]
Finished. Total time: 0.031s
C:\Users\480\OneDrive\Desktop\platform-tools>
zuhaibsarwar said:
here the commands while i was flashing twrp on my mobile
C:\Users\480\OneDrive\Desktop\platform-tools>fastboot flash boot abc.img
Sending 'boot_b' (42412 KB) OKAY [ 4.609s]
Writing 'boot_b' OKAY [ 0.344s]
Finished. Total time: 12.000s
C:\Users\480\OneDrive\Desktop\platform-tools>fastboot reboot
Rebooting OKAY [ 0.000s]
Finished. Total time: 0.031s
C:\Users\480\OneDrive\Desktop\platform-tools>
Click to expand...
Click to collapse
when i flash stock rom, it's andoird 8.1 and i don't update to android 10
fastboot flash boot abc.img
Sending 'boot_a' (42412 KB) OKAY [ 4.609s]
Writing 'boot_a' OKAY [ 0.344s]
Finished. Total time: 6s
fastboot reboot
Then it's stuck on logo
But when i flash stock again and update to android 10, it's like what i said
I don't know why my device is harder than any other or i have wrong on any step but it doesn't like any tutorial video on youtube
wait i gotta make video now
cl3izv said:
I don't know why my device is harder than any other or i have wrong on any step but it doesn't like any tutorial video on youtube
Click to expand...
Click to collapse
in this i used pixel experienced recover and pixel experienced rom andriod 11 . same procedure for lineage 18.1
zuhaibsarwar said:
in this i used pixel experienced recover and pixel experienced rom andriod 11 . same procedure for lineage 18.1
Click to expand...
Click to collapse
here is CMD PROCESSSING
C:\Users\480\OneDrive\Desktop\platform-tools>fastboot flash boot C:\Users\480\OneDrive\Desktop\boot.img
Sending 'boot_a' (37309 KB) OKAY [ 1.205s]
Writing 'boot_a' OKAY [ 0.300s]
Finished. Total time: 2.035s
C:\Users\480\OneDrive\Desktop\platform-tools>fastboot reboot
Rebooting OKAY [ 0.000s]
Finished. Total time: 0.011s
thank you, i will try it when i'm home
cl3izv said:
I don't know why my device is harder than any other or i have wrong on any step but it doesn't like any tutorial video
Click to expand...
Click to collapse
cl3izv said:
thank you, i will try it when i'm home
Click to expand...
Click to collapse
welcome and okay
WAO dude, i really did it, it working Very helpful, thank you
and how about twrp and gapps? should i install Disable Force encryption again?
cl3izv said:
WAO dude, i really did it, it working Very helpful, thank you
and how about twrp and gapps? should i install Disable Force encryption again?
Click to expand...
Click to collapse
dont try to install twrp .i tried to install twrp permanently many times but always failed always bootloop . dont flash disable force . flash gapps using lineage recovery only and you can flash magisk too