[Completed] My Asus Zenfone 2(Z00A, ZE551ML) is stuck at fastboot bootloader. What to do? - XDA Assist

I was trying to install the CM13. I followed the CM wiki page and created a CM13 build on my machine. The build was successful. But I couldn't load the CM zip file using adb sideload. I also unloacked the bootloader using the app from asus website. After this I rooted my device referring to androidroot_org.
Then I used "fastboot -w" to wipe the userdata. It failed when it reach erasing user-data field(saying "FAILED(remote: permssion denied)"). Next I went into recovery mode from fastboot screen and wiped user data/factory reset. After that I wiped the cache partition. I thought that now I can try "fastboot -w flashall". But when I tried it in linux cmd, it failed to write boot with same error of Permission denied.
Now I can't go into recovery mode to install the stock rom. Whichever option I select at the Fastboot among "Normal Boot", "Recovery Mode" it always end up restarting the bootloader. I also tried install the TWRP recovery image using "fastboot flash recovery" command. But it gives the error "cannot load 'twrp-3.0.2-0-Z00A.img.img'".
So eventually I'm stuck at the fastboot screen and don't know what to do.

XDA Visitor said:
I was trying to install the CM13. I followed the CM wiki page and created a CM13 build on my machine. The build was successful. But I couldn't load the CM zip file using adb sideload. I also unloacked the bootloader using the app from asus website. After this I rooted my device referring to androidroot_org.
Then I used "fastboot -w" to wipe the userdata. It failed when it reach erasing user-data field(saying "FAILED(remote: permssion denied)"). Next I went into recovery mode from fastboot screen and wiped user data/factory reset. After that I wiped the cache partition. I thought that now I can try "fastboot -w flashall". But when I tried it in linux cmd, it failed to write boot with same error of Permission denied.
Now I can't go into recovery mode to install the stock rom. Whichever option I select at the Fastboot among "Normal Boot", "Recovery Mode" it always end up restarting the bootloader. I also tried install the TWRP recovery image using "fastboot flash recovery" command. But it gives the error "cannot load 'twrp-3.0.2-0-Z00A.img.img'".
So eventually I'm stuck at the fastboot screen and don't know what to do.
Click to expand...
Click to collapse
Hi and welcome to XDA.
Please create an account so you can have full posting privileges.
Then you can post post in your device section:
ZenFone 2 Q&A, Help & Troubleshooting
Experts there may be able to help you.
Good luck

Related

Restore Android Stock's Recovery Mode

Hello! I've tried to root my phone (Moto G XT1541 Europe 1GB) but failed. I got an error when trying to flash the custom recovery. Unfortunately, it has overwritten the stock recovery and it didn't install. So, now I have a phone without recovery and I can't do a factory reset because of that (I think).
So, this is my question: how can I re install the default Android 6.0 recovery mode for my phone?
Also, my phone boots automatically on bootloader mode and I can't re-lock the bootloader because I can't flash anymore either; I got an error because the pre flash validation failed when trying to flash with adb fastboot, but this is minimal issues that doesn't really bother me, but they could be helpful and if someone knows how to get rid of them, I want to know!
I hope someone will help me!
Azyreal said:
Hello! I've tried to root my phone (Moto G XT1541 Europe 1GB) but failed. I got an error when trying to flash the custom recovery. Unfortunately, it has overwritten the stock recovery and it didn't install. So, now I have a phone without recovery and I can't do a factory reset because of that (I think).
So, this is my question: how can I re install the default Android 6.0 recovery mode for my phone?
Also, my phone boots automatically on bootloader mode and I can't re-lock the bootloader because I can't flash anymore either; I got an error because the pre flash validation failed when trying to flash with adb fastboot, but this is minimal issues that doesn't really bother me, but they could be helpful and if someone knows how to get rid of them, I want to know!
I hope someone will help me!
Click to expand...
Click to collapse
The bootloader cannot be relocked in the Moto G 2015, the best you can do is hide the warning screen. Find the stock image and fastboot flash the recovery from there, or better yet, flash the entire image so you are in a known working state
If you are in Pre-Flash validation, you do not have the correct image for your device... I suggest you post in the "How to flash factory images" thread about returning to stock, if it is possible. You MUST factory default before flashing factory images, if you can't, try 'fastboot erase userdata' and try again.
Flash latest twrp via fastboot and reboot into recovery ,
don't reboot into system,
reboot into recovery manually, then you can enter twrp recovery and can flash supersu 2.62.3.
when you just reboot after flash twrp and reboot system erase custom recovery and save stock recovery, so don't enter fastboot reboot, enter fastboot reboot recovery after flash recovery via pc.
Rename twrp recovery as only twrp in fastboot folder in your pc , not as twrp.img,
But cmd as fastboot flash recovery twrp.img , then no errors ( are you unlocked bootloader ?)
acejavelin said:
The bootloader cannot be relocked in the Moto G 2015, the best you can do is hide the warning screen. Find the stock image and fastboot flash the recovery from there, or better yet, flash the entire image so you are in a known working state
If you are in Pre-Flash validation, you do not have the correct image for your device... I suggest you post in the "How to flash factory images" thread about returning to stock, if it is possible. You MUST factory default before flashing factory images, if you can't, try 'fastboot erase userdata' and try again.
Click to expand...
Click to collapse
drmuruga said:
Flash latest twrp via fastboot and reboot into recovery ,
don't reboot into system,
reboot into recovery manually, then you can enter twrp recovery and can flash supersu 2.62.3.
when you just reboot after flash twrp and reboot system erase custom recovery and save stock recovery, so don't enter fastboot reboot, enter fastboot reboot recovery after flash recovery via pc.
Rename twrp recovery as only twrp in fastboot folder in your pc , not as twrp.img,
But cmd as fastboot flash recovery twrp.img , then no errors ( are you unlocked bootloader ?)
Click to expand...
Click to collapse
Hey! Thank you! I've been able to flash the TWRP recovery and now I can do a factory reset (and also send sms, which I couldn't do anymore for some reason).
I still have the issue where the bootloader screen appears everytime I turn my phone on, and I still can't re lock my device because I can't flash anything either. I've recovered all of my data, so I think I'm going to stick with that for a moment but maybe I'll try what you said some day.
Again, really thank you for helping me!
drmuruga said:
Flash latest twrp via fastboot and reboot into recovery ,
don't reboot into system, reboot into recovery manually, then you can enter twrp recovery and can flash supersu 2.62.3.
when you just reboot after flash twrp and reboot system erase custom recovery and save stock recovery, so don't enter fastboot reboot, enter fastboot reboot recovery after flash recovery via pc.
Click to expand...
Click to collapse
Now I understand why my flashing TWRP did not take. I simply rebooted to system and still have stock recovery installed. I was successful booting twrp via fastboot and successfully flashed supersu 2.62.3. Is this step in listed in any faq? I must have missed it.
So after flashing TWRP, do you then power down device prior to manually booting to recovery?
MrTooPhone said:
Now I understand why my flashing TWRP did not take. I simply rebooted to system and still have stock recovery installed. I was successful booting twrp via fastboot and successfully flashed supersu 2.62.3. Is this step in listed in any faq? I must have missed it.
So after flashing TWRP, do you then power down device prior to manually booting to recovery?
Click to expand...
Click to collapse
Don't power down, already you are in fastboot mode, you can just enter recovery from that. I forget the reference, but i will search and post.
---------- Post added at 04:41 PM ---------- Previous post was at 04:18 PM ----------
I get this from twrp official page
Note many devices will replace your custom recovery automatically during first boot. To prevent this, use Google to find the proper key combo to enter recovery. After typing fastboot reboot, hold the key combo and boot to TWRP. Once TWRP is booted, TWRP will patch the stock ROM to prevent the stock ROM from replacing TWRP. If you don't follow this step, you will have to repeat the install.
In our phone press simultaneously volume down + power button to enter recovery.

Mi4i Always boots to fastboot even after flasing rom. Download mode also not opening.

Hello,
I had Resurrection Remix Android 7.1.2 installed in my Mi4i. The apps were suddendly crashing (was getting app crashed alert) and thought to reboot the phone once.
Once I tried to reboot abnormality started showing up.
Tried flashing the Resurrection Remix again but it stuck at the boot animation screen.
Then tried flashing the official MIUI developer rom and it worked.
Again tried with RR but it did not boot up.
After trying a couple of times, none of the roms did boot up.
After some research found in TWRP logs that it is unable to mount system, cache, dalvik cache etc.
Also I could see that the space/memory is displayed as 0MB.
Some forums said to format the file system as ext4 and even the format failed saying it is unable to mount.
Now whenever I start the phone to goes to the fastboot screen.
The interesting point is that I tried flashing manually the developer rom and it said it falshed successfully.
But i still see the twrp as my recovery and not the stock recovery after flasing.
Also tried manually flashing the recovery like "fastboot flash recovery recovery.img" and did not find any errors still the stock recovery was not flashed instead the twrp remained as the recovery even after successful flash.
I am stuck with my phone now and not sure how to proceed.
Any help regarding this would really be helpful.
Help me to recover my phone please. :crying:
Thanks.
So have you format all of your data including internal data from TWRP ? Is it show some error like "unmount /data" types N how you flash rom manually means you tried of ADB slide load ??
Mukulkathuria008 said:
So have you format all of your data including internal data from TWRP ? Is it show some error like "unmount /data" types N how you flash rom manually means you tried of ADB slide load ??
Click to expand...
Click to collapse
1. Tried formating the partitions from TWRP.. Failed with error message saying cant mount
2. Hence thought TWRP was broken.. Tried flashing twrp again from fastboot as follows :
Code:
fastboot flash recovery recovery.img
Fastboot flashed successfully(got OKAY response in terminal).
3. Rebooted into recovery and tried formatting partitions again. Still got the same error saying cant mount partitions.
4. Thought to flash stock recovery. Had miui fastboot room. Picked up recovery.img from it and flashed from fastboot as follows :
Code:
fastboot flash recovery recovery.img
5. Surprisingly when I rebooted into recovery, the custom recovery was still twrp.. The stock recovery didn't got flashed.
6. To crosscheck, I directly booted the stock recovery fastboot boot recovery.img. But nothing boots up.. Gets stuck at the distorted fastboot screen (Attaching screenshot if possible).
Probal Basak said:
1. Tried formating the partitions from TWRP.. Failed with error message saying cant mount
2. Hence thought TWRP was broken.. Tried flashing twrp again from fastboot as follows :
Code:
fastboot flash recovery recovery.img
Fastboot flashed successfully(got OKAY response in terminal).
3. Rebooted into recovery and tried formatting partitions again. Still got the same error saying cant mount partitions.
4. Thought to flash stock recovery. Had miui fastboot room. Picked up recovery.img from it and flashed from fastboot as follows :
Code:
fastboot flash recovery recovery.img
5. Surprisingly when I rebooted into recovery, the custom recovery was still twrp.. The stock recovery didn't got flashed.
6. To crosscheck, I directly booted the stock recovery fastboot boot recovery.img. But nothing boots up.. Gets stuck at the distorted fastboot screen (Attaching screenshot if possible).
Click to expand...
Click to collapse
Try to flash TWRP v3.2.1.0 you can download from link below:
https://dl.twrp.me/ferrari/twrp-3.2.1-0-ferrari.img.html
And Advance Wipe And change the file format to ex4 and wipe all the data try ROM try flash ROM link below through OTG:
https://forum.xda-developers.com/mi-4i/development/unofficial-dotos-v1-2-t3726924
that surely solve your all problems :fingers-crossed:
Mukulkathuria008 said:
Try to flash TWRP v3.2.1.0 you can download from link below:
https://dl.twrp.me/ferrari/twrp-3.2.1-0-ferrari.img.html
And Advance Wipe And change the file format to ex4 and wipe all the data try ROM try flash ROM link below through OTG:
https://forum.xda-developers.com/mi-4i/development/unofficial-dotos-v1-2-t3726924
that surely solve your all problems :fingers-crossed:
Click to expand...
Click to collapse
Tried formating to ext4.. But nothing happened.. Still getting mount error.
Attaching pics below.
Attachment 1 : Advanced Wipe -> Wipe
Attachment 2 : Advanced Wipe -> Change File System -> /system -> ext4
I have also tried this
Code:
fastboot getvar all
Output:
Code:
all:
finished. total time: 0.001s
Any comments what may have gone wrong?
fix file system. or maybe emmc died

adb problem

hi
I would like to install twrp image, but adb says device not found, while on the list it sees, the serial nr is there..
I can even install the img, it writes 2x the okay, but doesn't boot. I'm stuck on fastboot screen, can I fix it?
When at the bootloader, you need to use fastboot commands, not adb.
So the command should be "fastboot boot imgname.img"
Hunter3U said:
When at the bootloader, you need to use fastboot commands, not adb.
So the command should be "fastboot boot imgname.img"
Click to expand...
Click to collapse
+1 for this.
Folks often mix up fastboot and adb. They are related, but different. Different operation requirements and functions.
adb:
- Only works in OS, or alternately in TWRP.
- Requires debugging toggled on in settings.
Fastboot:
- Only works in bootloader-fastboot mode.
- Does not require debugging to be toggled on.
Fastboot is typically what you want for unlocking bootloader, and booting TWRP (for root, etc.).
---------- Post added at 09:04 AM ---------- Previous post was at 09:00 AM ----------
ii9 said:
adb says device not found
I can even install the img, it writes 2x the okay, but doesn't boot. I'm stuck on fastboot screen, can I fix it?
Click to expand...
Click to collapse
Not completely clear based on your description. But is sounds like you are trying to do "adb devices" and then "fastboot flash twrp.img"?
In fastboot, you want to do "fastboot devices" (no quotes) and should see the phone's ID number in response.
Then you want to do "fastboot boot twrp.img" to boot TWRP, then flash the TWRP installer zip within TWRP. This is per the recommended install guide from the TWRP thread: https://forum.xda-developers.com/on...nt/recovery-unofficial-twrp-recovery-t3931322
Although it's hard to determine exactly what you did wrong, unless you provide a more detailed sequence of what you did, and with the exact commands.
And to be clear, your bootloader is unlocked, correct?
well, sorry for being noob, for me was never a problem with older phones. I always managed to root, put twrp, change rom without any pc, but this double slot system kills me
so I managed to wipe everything before, vendor, sytem.., all
I wanted to put the havoc rom after formatting, but there was 5 local disks when I opened the phone folder on the pc, and obviously didn't copy the files on it. Therefore I did reboot to recovery, since that I had only the fastboot screen.
After that I unbricked it, all was fine again on the stock
After opened again the bootloader (yes, also before it was) installed the twrp.img, Installed the twrp zip, reboot it.
I followed the steps from havoc, but it said error 7, few times I tried. I reboooted the recovery again, and now I'm again the fastboot only, doesn't even show the warning msg about open bl, and doesn't go anywhere again.
I tried now with the fastboot command You gave, it says:
downloading 'boot.img'...
OKAY [ 1.265s]
booting...
FAILED (remote: Failed to load/authenticate boot image: Load Error)
finished. total time: 1.312s
So I'm affraid I need to unbrick again.
If You can help me out, I'd apprecite :good: thanks!
Edit: I'm doing the unbrick again, but this time I'll wait for some info before I try the havoc. Also I'd love to get rid off this double slot thing, is there any way to do the normal method?
ii9 said:
*SNIP*
I tried now with the fastboot command You gave, it says:
downloading 'boot.img'...
OKAY [ 1.265s]
booting...
FAILED (remote: Failed to load/authenticate boot image: Load Error)
finished. total time: 1.312s
So I'm affraid I need to unbrick again.
If You can help me out, I'd apprecite :good: thanks!
Edit: I'm doing the unbrick again, but this time I'll wait for some info before I try the havoc. Also I'd love to get rid off this double slot thing, is there any way to do the normal method?
Click to expand...
Click to collapse
I ran into the same error (and I have not been able to narrow down what causes it), and I had to fastboot flash boot twrp.img and actually flash TWRP to boot.
Once you flash TWRP to boot, and reboot your phone, you will be dropped right into TWRP.
Once in TWRP I was able to flash the stock boot image, then flash the TWRP installer zip, and finally Magisk. Basically you need to follow the instructions in the TWRP thread, with the only difference being that you flash TWRP to boot and not use fastboot boot. I hope to look into what the possible causes for this failure could be this weekend.
As for getting rid of slot A/B -- nope. That is part of the bootloader, so you will just have to get used to it. It is actually quite useful once you get the hang of it. For example, dual booting if you never intend to take OTA updates. It requires a bit of work to get setup (for example, you have to partition userdata since there is no userdata_a and userdata_b), and you need kernels and ROMs that understand the partitioning scheme.
-- Brian
Did you do fastboot flash boot imagename or fastboot flash recovery imagename
runningnak3d said:
I ran into the same error (and I have not been able to narrow down what causes it), and I had to fastboot flash boot twrp.img and actually flash TWRP to boot.
Once you flash TWRP to boot, and reboot your phone, you will be dropped right into TWRP.
Once in TWRP I was able to flash the stock boot image, then flash the TWRP installer zip, and finally Magisk. Basically you need to follow the instructions in the TWRP thread, with the only difference being that you flash TWRP to boot and not use fastboot boot. I hope to look into what the possible causes for this failure could be this weekend.
As for getting rid of slot A/B -- nope. That is part of the bootloader, so you will just have to get used to it. It is actually quite useful once you get the hang of it. For example, dual booting if you never intend to take OTA updates. It requires a bit of work to get setup (for example, you have to partition userdata since there is no userdata_a and userdata_b), and you need kernels and ROMs that understand the partitioning scheme.
-- Brian
Click to expand...
Click to collapse
I guess I lost it, time to accept the stock rom :crying:
I' not that old, but I can understand now why my grandma doesn't know even what is a phone
At the end I managed to do the unbrick again, after I installed havoc, I get rid of the error 7, and it showed me st like qualcomm crashdump, I was about to give up, but I went back to twrp installed again, now it's fine. Such a pity that it's not stable yet, I don't dare to touch after this..
tHanks for the info, in case I'll ever need I'll try to read again another 100x maybe I'll find out.
Bradl79 said:
Did you do fastboot flash boot imagename or fastboot flash recovery imagename
Click to expand...
Click to collapse
fastboot flash boot imagename
I did this
ii9 said:
I tried now with the fastboot command You gave, it says:
downloading 'boot.img'...
OKAY [ 1.265s]
booting...
FAILED (remote: Failed to load/authenticate boot image: Load Error)
finished. total time: 1.312s
Click to expand...
Click to collapse
I think you are doing something wrong.
boot.img is basically a kernel, not TWRP.
Booting TWRP and flashing a boot.img are two completely different things.
It would help if you cut/paste the actual command you typed, so we can see what you did.
The command should be: fastboot boot twrp.img
That isn't what you did.
---------- Post added at 11:55 AM ---------- Previous post was at 11:48 AM ----------
ii9 said:
fastboot flash boot imagename
I did this
Click to expand...
Click to collapse
Nobody told you to do this.
The proper syntax is:
fastboot boot twrp.img
Seems similar, but this does something very different from the command you used. Syntax in fastboot/adb is absolutely ciritical. Always type fastboot and adb commands exactly as indicated, and double check everything before issuing the command.
fastboot boot twrp.img This boots the image file that is named. Note that you are not flashing anything with this command. Think of it as a remote boot of the TWRP file that is on your computer.
fastboot flash boot imagename This flashes the named file to the boot partition (basically the kernel)
If Havoc is the end goal here, from absolute stock start to finish it would be
1. Enable developer options
2. Enable oem unlock and usb debugging through the developer options menu (I also enable advanced reboot but not required)
3. Reboot to bootloader via the advanced reboot menu or through adb command "adb reboot bootloader"
4. While in bootloader, type in cmd, "fastboot oem unlock"
5. Allow bootloader unlock and wipe and let system reboot back to oos
6. Repeat steps 1-3 to get back to bootloader
7. While in bootloader, type in cmd, "fastboot boot twrpimagename.img"
8. Wipe Data and Dalvik (after data wipe, you might not be able to copy files to phone)
9. Reboot back to bootloader
10. While in bootloader, type in cmd, "fastboot boot twrpimagename.img"
11. Copy Havoc, TWRP.zip, GAPPS, Magisk to device (GAPPS and Magisk are optional...if not needed, skip the steps for them)
12. Flash Havoc and TWRP.zip through normal install process
13. Reboot to recovery
14. Flash Havoc and TWRP.zip through normal install process again
15. Reboot to recovery
16. Flash GAPPS and Magisk (If error 70 thrown with GAPPS install, reboot to system once and run through any setup then reboot back to recovery to flash)
17. Reboot system
As long as no other errors are thrown, you should now be in Havoc with GAPPS and Magisk installed
redpoint73 said:
Nobody told you to do this.
The proper syntax is:
fastboot boot twrp.img
Click to expand...
Click to collapse
Sorry, I messed up with the copy and paste, I didn't sleep too much in the last days for the hot, I'm a bit heavy in the head, pls exuse my bs. I also tried this one that you wrote, but didn't manage to boot still.. I have no clue what went wrong, but again, thanks, in case I can come back to read again.
Hunter3U said:
If Havoc is the end goal here, from absolute stock start to finish it would be
1. Enable developer options
2. Enable oem unlock and usb debugging through the developer options menu (I also enable advanced reboot but not required)
3. Reboot to bootloader via the advanced reboot menu or through adb command "adb reboot bootloader"
4. While in bootloader, type in cmd, "fastboot oem unlock"
5. Allow bootloader unlock and wipe and let system reboot back to oos
6. Repeat steps 1-3 to get back to bootloader
7. While in bootloader, type in cmd, "fastboot boot twrpimagename.img"
8. Wipe Data and Dalvik (after data wipe, you might not be able to copy files to phone)
9. Reboot back to bootloader
10. While in bootloader, type in cmd, "fastboot boot twrpimagename.img"
11. Copy Havoc, TWRP.zip, GAPPS, Magisk to device (GAPPS and Magisk are optional...if not needed, skip the steps for them)
12. Flash Havoc and TWRP.zip through normal install process
13. Reboot to recovery
14. Flash Havoc and TWRP.zip through normal install process again
15. Reboot to recovery
16. Flash GAPPS and Magisk (If error 70 thrown with GAPPS install, reboot to system once and run through any setup then reboot back to recovery to flash)
17. Reboot system
As long as no other errors are thrown, you should now be in Havoc with GAPPS and Magisk installed
Click to expand...
Click to collapse
Not exactly, the end goal to have a clean rom, with basic custumization, that even stock should include in my opinion, like disable headups.., extended screen etc. Plus without google staff, for me it's too strict. As in this moment not so many choice, havoc looked the most near to my wishes, in fact very nice after these hours, I guess I'll be fine with it when the bugs will disappear.
Anyway 1-7 was always without problem. Today after 2 unbrick and bl opening what I did is, through fastboot I entered to the img, from there I flashed the zip, reboot recovery to make sure it stays. I put files on the phone, wiped dalvik and data, install rom+twrp and as it is written here and also on that thread, I rebooted recovery. And I wanted to repeat the flash, but I had the internal storage 0mb thing. So I needed to format data (that's the solition I found) and reboot again, put back files, flash, reboot, flash again, and after I got that qualcomm crashdump screen. I hold the up+power to get back to twrp (or down, not sure) and I flashed again, but only once, so after it worked finally. Since that I'm fine
But sure I need to learn this stuff, it cannot be that I always face st that nobody else does
I hope the managed soon the ota for custom roms and we can do it easy and quick without setting the phone over and over again with all the apps, settings.. (probably only me in the world need to do so, as I start to loose it with the tech staff)
Poor phone is just couple of weeks old, but already saw everything
Thanks for writing
If it means anything to you, I use stock OOS+TWRP+Magisk+Renovate ICE+Xposed (to ignore the secure flag, otherwise Netflix doesn't work over HDMI). Everything works, including Google Pay.

[SOLVED] Android Recovery Factory Reset not effective (rooted, bootloader unlocked)

Hi,
I backed up my kernel using TWRP by fastbooting into the Pixel 3 blueline TWRP image. When I then tried to reboot the phone I get following error:
"Android Recovery
google/blueline/blueline
9/PI/gucheng0719045
userdebug/dev-keys
...
Can't load Android system."
I tried both options "try again" and "factory data reset" but both brought me back to this screen. I also tried booting into recovery mode and doing "Wipe data factory reset"; this also brought me back to the above error.
Finally, I tried installing OTA using sideload but the signature verification failed since I have an unlocked bootloader and had custom ROM running on the device.
How can I get the device into a usable state again? I don't care about keeping the data. Also note that I still have the TWRP kernel backup saved.
gardeimasei said:
Hi,
I backed up my kernel using TWRP by fastbooting into the Pixel 3 blueline TWRP image. When I then tried to reboot the phone I get following error:
"Android Recovery
google/blueline/blueline
9/PI/gucheng0719045
userdebug/dev-keys
...
Can't load Android system."
I tried both options "try again" and "factory data reset" but both brought me back to this screen. I also tried booting into recovery mode and doing "Wipe data factory reset"; this also brought me back to the above error.
Finally, I tried installing OTA using sideload but the signature verification failed since I have an unlocked bootloader and had custom ROM running on the device.
How can I get the device into a usable state again? I don't care about keeping the data. Also note that I still have the TWRP kernel backup saved.
Click to expand...
Click to collapse
Flash factory image with fastboot.
wangdaning said:
Flash factory image with fastboot.
Click to expand...
Click to collapse
Where can I get the factory image? And how do I use fastboot to flash the device? Like so?:
Code:
fastboot boot <image name>.img
I am able to fastboot boot into the blueline TWRP image. Selecting the "Fix bootloop" didn't work however
So I tried doing:
Code:
fastboot flash boot bootloader-blueline-b1c1-0.1-5578427.img
I got following error though:
Sending 'boot_a' (8493 KB) OKAY [ 0.130s]
Writing 'boot_a' (bootloader) Flashing Pack version b1c1-0.1-5578427
FAILED (remote: '(boot_a) No such partition')
fastboot: error: Command failed
Any suggestions on how to proceed?
gardeimasei said:
So I tried doing:
Code:
fastboot flash boot bootloader-blueline-b1c1-0.1-5578427.img
I got following error though:
Sending 'boot_a' (8493 KB) OKAY [ 0.130s]
Writing 'boot_a' (bootloader) Flashing Pack version b1c1-0.1-5578427
FAILED (remote: '(boot_a) No such partition')
fastboot: error: Command failed
Any suggestions on how to proceed?
Click to expand...
Click to collapse
That command flashes only the boot loader, not the factory image. The factory image and instructions for flashing are at https://developers.google.com/android/images
What android version were you on when you started? TWRP does not run on a Pixel 3 with Android 10.
Also, the boot partition is not the bootloader partition. Just run the flash-all script that google provides with the factory image download.
dcarvil said:
That command flashes only the boot loader, not the factory image. The factory image and instructions for flashing are at https://developers.google.com/android/images
What android version were you on when you started? TWRP does not run on a Pixel 3 with Android 10.
Click to expand...
Click to collapse
I was using Android 9. I tried running the flash-all script (i.e., follow the official instructions) but the fastboot commands would hang. Maybe I just didn't wait for long enough.
I wiped system,data,cache using TWRP following some online guide and now I can't boot into recovery mode. I can get into the bootloader menu though. When I try to boot into TWRP using:
Code:
fastboot boot twrp-3.3.0-0-blueline.img
I get the following error on the PC: Booting FAILED (remote: 'Error calling AvbLoadAndVerifyBootImages Load Error')
When I try to enter recovery mode the screen turns black indefinitely.
I still have the TWRP .win files from my backup on my PC. Is there a way out of this?
EDIT:
Weirdly, after trying the flash-all.sh script again it worked basically instantly. Possibly it took so long the first time i ran it because it was wiping data (which i then did manually).
Was able to get the factory image on there. Thanks a lot!

[ AIO ] Guide TECNO SPARK 5 PRO (KD7) bootloader unlocking,root,twrp & stock firmware

AIO GUIDE TECNO KD7
1. Bootloader Unlocking
1. Download & install the ADB driver
2.Enable devloper mode by taping on Build verson(setting->my phone) then enable Oem Unlock & usb debugging from (settings->System->Devloper option)
3.Now connect device & open ADB path & run cmd
command: ADB devices
then reboot to bootloader
command: ADB reboot bootloader
4. unlock bootloader
command: fastboot flashing unlock the phone will ask to confirm
5. now reboot to system
command:fastboot reboot
If you are stuck waiting for the device screen
2. TWRP [unoficial]
https://forum.xda-developers.com/t/twrp-recovery-for-tecno-kd7.4378493/
3. Orange state disabler:
Flashing guide & zip file
Click Wipe →Format Data → Yes → Press Enter.
Then Click Reboot → Recovery (Reboot to Recovery ).
After this, TWRP Recovery Mode will be installed on your phone
Link: Orange disabler.zip
4. Root
1.boot into recovery
2. Flash magisk .zip
llink:https://github.com/topjohnwu/Magisk/releases/download/v21.0/Magisk-v21.0.zip
3.1. Unroot
1.boot into recovery
2. Flash magisk unistaller .zip
link:https://github.com/topjohnwu/Magisk/releases/download/v21.0/Magisk-uninstaller-20201003.zip
5.Stock Firmware Files
Stock boot ,stock recovery & Full Firmware are added
To Flash full firmware
Extract zip & run flash.bat
Link: TECNO-SPARK-5-PRO-KD7-H6211FQRSTU-Q-GL-211101V404-fastboot flash full rom.zip
6. Gsi rom / Custom rom Installation guide:
https://forum.xda-developers.com/t/custom-rom-for-tecno-phone-dynamic-partition.4379341/
vendor : ( 3 sim problem guide )
TECNO-SPARK-5-PRO-KD7-H6211FQRSTU-Q-GL-211101V404
7. Phone Hard Brick fix
https://forum.xda-developers.com/t/phone-soft-brick-phone-on-off-poblem-tecno-device.4378501/
7.1. Flash file:
Link :
TECNO-SPARK-5-PRO-KD7-H6211FQRSTU-Q-GL-211101V404
HIT THE THANKS BUTTON IF ABOVE INFORMATION IS HELPFUL TO YOU
Tecno kd7 full guide
https://forum.xda-developers.com/t/...r-unlocking-root-twrp-stock-firmware.4345557/
What do you mean by boot into recovery? Going fastboot mode? And then writing fastboot flash recovery magisk.zip( for step 3(root)) ?
Also should have the updatest kd7 before rooting?
Thanks in advance for your hard work.
Tanjin01: Thanks
Fast time twrp recovery install: (any bulid version)
[command]
adb devices
adb reboot bootloader
fastboot flashing unlock
fastboot flash recovery twrp.img
fastboot flash vbmeta vbmeta.img
fastboot reboot recovery
[command]
Now boot into twrp recovery and from there "wipe option->Format Data -> yes Format.
Next, Reboot option -> recovery click Wait reboot recovery and flash magisk.zip
Any time root and unroot:
2.going to recovery
Open recovery and install magisk zip. /Magisk uninstall flash
Parvej789 said:
Tanjin01: Thanks
Fast time twrp recovery install: (any bulid version)
1.Fastboot flash recovery .
Fastboot reboot recovery -
Open recovery -wipe format data-yes.
reboot to recovery
and install magisk zip.
Any time root and unroot:
2.going to recovery
Open recovery and install magisk zip. /Magisk uninstall
Click to expand...
Click to collapse
Thank a bunch for consist help with my nobby question(s)!
Correct me if i am wrong before i procced,
Fire up pc, open terminal/cmd and writing the following one after another
[Command]
adb devices
adb reboot bootloader
fastboot flashing unlock
fastboot flash recovery twrp.img
fastboot flash vbmeta vbmeta.img
[command]
Now i boot into twrp recovery and from there "wipe data". Then "advanced wipe" with delvic cache.
Next, again, twrp recovery and flash magisk.zip
Right?
Tanzin01
[Command]
adb devices
adb reboot bootloader
fastboot flashing unlock
fastboot flash recovery twrp.img
fastboot flash vbmeta vbmeta.img
fastboot reboot recovery
[command]
Now i boot into twrp recovery and from there "wipe ". Then "Format Data" with yes Format.
Next, Reboot to recovery .again, twrp recovery and flash magisk.zip
Right?
Thanks man. Have a nice day&life
hey man, all went well till format. in format i saw some error, eg failed to mount /data(something like this). Any idaea why i got this?
[i got a success msg though]]
also can i access twrp recovery mode via volume and power button?(i tried volume up+power button but got adnroid image with "No command".)
Command]
adb devices
adb reboot bootloader
fastboot flashing unlock
fastboot flash recovery twrp.img
fastboot flash vbmeta vbmeta.img
fastboot reboot recovery
[command]
Now boot into twrp recovery and from there "wipe option ->Format Data -> yes Format .
Next,
Reboot options -> recovery click Wait reboot to recovery and magisk.zip flash
Parvej789 said:
Command]
adb devices
adb reboot bootloader
fastboot flashing unlock
fastboot flash recovery twrp.img
fastboot flash vbmeta vbmeta.img
fastboot reboot recovery
[command]
Now i boot into twrp recovery and from there "wipe ". Then "Format Data" with yes Format.
Next,
Reboot options to recovery .again, twrp recovery and flash magisk.zip
Right?
Click to expand...
Click to collapse
All the commands worked smoothly but when again tried to go twrp recovery for rooting, I can't seem to find twrp. I got no command with Android pic and after few seconds default device recovery option. From where I can navigate to fastboot, recovery, wipe and etc.
"
Next,
Reboot options to recovery .again, tw
Parvej789 said:
Next,
Reboot options to recovery .again, twrp recovery and flash magisk.zip
Right?
Click to expand...
Click to collapse
Not sure what you mean by this. But tried
[Command]
adb reboot bootloader
fastboot reboot recovery
[Command]
Which took me to deafult recovery, no Twrp this time.
However I spent some time on xda and found this Command "fastboot boot twrp.img". Will try tomorrow again, will let you know if it worked! Man I'm probably bothering you!
Tanzin01 said:
"
Next,
Reboot options to recovery .again, tw
Not sure what you mean by this. But tried
[Command]
adb reboot bootloader
fastboot reboot recovery
[Command]
Which took me to deafult recovery, no Twrp this time.
However I spent some time on xda and found this Command "fastboot boot twrp.img". Will try tomorrow again, will let you know if it worked! Man I'm probably bothering you!
Click to expand...
Click to collapse
[command]
adb devices
adb reboot bootloader
fastboot flashing unlock
fastboot flash recovery twrp.img
fastboot flash vbmeta vbmeta.img
fastboot reboot recovery
[command]
Now boot into twrp recovery and from there "wipe option->Format Data -> yes Format and back home menu
Next, Reboot option -> recovery click Wait reboot recovery and flash magisk.zip
Unorganized posts! Its xda's fault. Your edited post wasn't shown to me until my last post was posted!
Thanks man. This time I got it. I wrongly rebooted after "format data". I will reflash the twrp file again tomorrow.
Hey, i got myself in trouble again! Everything was working fine till i clicked on "Erase data" from settings. Now i cant boot into sytem, always booting into twrp.Any help?
Should i try flashing android 11, the one you provided here?
Tanzin01 said:
Hey, i got myself in trouble again! Everything was working fine till i clicked on "Erase data" from settings. Now i cant boot into sytem, always booting into twrp.Any help?
Should i try flashing android 11, the one you provided here?
Click to expand...
Click to collapse
Stock recovery.img flash and reboot
To make sure, i am donig as you described,
download stock firmware and get recovery.img.
now flash it: fastboot flash recovery recovery.img
Now reboot, right?
Btw cant i just flash andoid 11 altogether? (and thanks for your constant help
Tanzin01 said:
To make sure, i am donig as you described,
download stock firmware and get recovery.img.
now flash it: fastboot flash recovery recovery.img
Now reboot, right?
Btw cant i just flash andoid 11 altogether? (and thanks for your constant help :fashfashfashfash)
Click to expand...
Click to collapse
Yes
Or
Full flash
KD7-H6211FQRSTU-Q-GL-210520V392.zip
drive.google.com
how to do full flash?
[command]
fastboot flash system FullFlashfirmware.zip
[command]
or
sideload the zip file and then swipe install via twrp?
No .
PC to mobile(fastboot flash)
Now connect device to PC
Unzip flash file PC
Folder open
Click flash.bat
CMD open:
1.Do you want to Reboot device into fastboot [Y/N]=y type enter
2.wipe user data [Y/N]=y type enter
Then flash started
FLASHING success
Reboot to phone on
sadly im not on windows. Anyway thnx. i will try and see flashing recovery. Will let you know the result.
Stock recovery.img flash and reboot options->system click.
Reboot to phone on
Parvej789 said:
Stock recovery.img flash and reboot options->system click.
Reboot to phone on
Click to expand...
Click to collapse
got error
```
fastboot flash recovery recovery.img
Sending 'recovery' (39936 KB)
FAILED (Write to device failed (No such device))
fastboot: error: Command failed
``
tried changing cable but no change.
Oky so i had a hunch, and it was correct. i mounted system and didnt get that error.
Thanks buddy. Took me few tries and combination. but now im back with my device. And as guessed, twrp was/is the culprit. It was locking the system or something like this, perhaps a glich? anyway had to mount system and already wrote the command on terminal, so as soon as phone screen turns on, i get to send the data from pc to phone before phone starts doing many of its stuff.
Wipe option->format data -yes
Reboot option-> recovery and Twrp open
1.boot.img flash
2.super.img flash
3.recovery.img flash
Than reboot
Tanzin01 said:
Thanks buddy. Took me few tries and combination. but now im back with my device. And as guessed, twrp was/is the culprit. It was locking the system or something like this, perhaps a glich? anyway had to mount system and already wrote the command on terminal, so as soon as phone screen turns on, i get to send the data from pc to phone before phone starts doing many of its stuff.
Click to expand...
Click to collapse
Build version correct
Your build version

Categories

Resources