I used the guide on this site,
I don't know what I did wrong, but now it just hangs on the screen shown below.
Any help, guidance, words of wisdom, or berating would be awesome.
Pull the battery. Hold the volume down button on the phone and put the battery back in and power it on (while still holding the button). Select recovery and see what happens. . . Cross your fingers, pray to Allah, etc.
how far did you get in the rooting process? were you able to install amon_ra's recovery image yet? also can you get into fastboot mode or recovery mode?
momohammed20 said:
how far did you get in the rooting process? were you able to install amon_ra's recovery image yet? also can you get into fastboot mode or recovery mode?
Click to expand...
Click to collapse
i got the bootloader unlocked.....not 100% sure that the root through fastboot was fully completed. Tried flashing amon_ra's recovery image and got the error message:
"downloading 'recovery.img'...failed <remote: not allow>"
byalansmithee said:
i got the bootloader unlocked.....not 100% sure that the root through fastboot was fully completed. Tried flashing amon_ra's recovery image and got the error message:
"downloading 'recovery.img'...failed <remote: not allow>"
Click to expand...
Click to collapse
It's the oem unlock that will allow you to flash the recovery image, not root.
Sounds like it's not quite unlocked although you have the unlock boot image (which is odd).
Have you tried doing the oem unlock again and then tried to reflash the recovery image?
SC
ScaredyCat said:
It's the oem unlock that will allow you to flash the recovery image, not root.
Sounds like it's not quite unlocked although you have the unlock boot image (which is odd).
Have you tried doing the oem unlock again and then tried to reflash the recovery image?
SC
Click to expand...
Click to collapse
Yeah, I tried the whole process (the oem unlock and superuser root) a second time and got the response: ... INFODevice was already unlocked!
OKAY
I can still boot to the bootloader and fastboot, but can do nothing more.
Related
Before I describe my issue I'll let you know I've been looking up articles on how to solve this for weeks now. first post to XDA, so bear with me I'm new
I have two OPT, both have a similar problem, but one is working (I dare not try to mess with it) and the other I've already tried and tried and now I'm stuck in fastboot, no recovery, no OS.
I HAD an OS on it (Paranoid Android 6.0.1), but I couldn't factory reset, and I needed to, so that I could sell the phone. when I tried to factory reset through OS settings, it would boot loop until I hard reset the phone. I had no recovery apparently (IDK how I did that) but trying to install a recovery requires the "OEM Unlocking" setting to be checked. and for some reason it won't let me check the box. My working OPT phone has the same problem, the "Allow OEM unlocking?" box pops up, I select enable, and the toggle moves itself back to the grayed out selection. so I couldn't install a custom recovery, I can't do any formatting or erasing in fastboot either without that selection for some reason either. trying to only gives me a "FAILED (remote: device is locked. cannot erase images)" or "FAILED (remote: device is locked. cannot flash images)"
AND SO, I tried this (search google for "mega unbrick guide for a hard bricked oneplus 2". I can't post links apparently as it is my first post. it will be on the oneplus website) and now I have no OS. or at least I believe I have no OS because trying boot causes a bootloop. I've tried all the methods, but I'm assuming because my bootloader is locked, It failed with the "A2001_save_brick_mini" tool.
And so, all I have right now is bootloader. didn't have a recovery I guess, and now I think I don't have an OS. and I can't do anything in fastboot because is returns with a "FAILED" hehe. dang locked bootloader. I have no idea how both of these phones have locked bootloaders anyways, because I obviously unlocked the bootloader to install a custom ROM in the first place. did the bootloader relock itself, or maybe during the process of installing the ROM, the bootloader relocked? I'm not sure as I wasn't watching for that. the phones had booted with the new OS, and so I happily went along my business and didn't find out I had a problem until I tried to factory reset one of them.
no I have no phones now with similar problems, but at different stages of the same issue.
My ONE A2005 is working, but I can't toggle the "OEM unlocking". At least it has a working custom recovery (TWRP)
and MY ONE A2003 is stuck in fastboot (fastboot recognizes it via "fastboot devices" and I can reboot and "fastboot oem device-info") with what I believe to be no recovery or OS.
ask me any questions to further explain my predicament, and PLEASE offer me any things to try. I ave two phones to test different things with. I would prefer to keep the working one working though.
Have you tried the fastboot oem unlock command?
DR_HAX34 said:
Have you tried the fastboot oem unlock command?
Click to expand...
Click to collapse
Ah yes, I forgot to write that in. That also results in a "FAILED (remote: unlock device to use this command)"
I can't unlock because of the OS, or perhaps lack of OS now; And I can't install a new OS or recovery because my bootloader is locked
use qualcomm recovery tool if you can't get any help. it'll restore your phone to 100% stock
UPDATE:
The oem was already unlocked so thats why the command did nothing. (I found it by locking and unlocking it again)
Also I had the wrong SuperSU, I first installed CM14 and than installed the right SuperSU
So I was trying to root my OP2 for the second time (apparently it derooted itself for some reason?)
But now I can't unlock oem from fastboot.
I magicly could flash TWRP and from there I installed SuperSU.
But when I booted my device up, it get's bricked into a boot loop.
I got out of the boot loop and tried again.
So I go into fastboot mode and tried the command again:
>fastboot oem unlock
...
OKAY [ 0.020s]
finished. total time: 0.022s
Click to expand...
Click to collapse
PLEASE do not link me to the unbrick guides - the problem is NOT that it's bricked - The problem is that I can't unlock oem from fastboot and so I can't succesfull root my phone.
What works:
+ getting into the OS
+ getting into fastboot
+ flashing a recovery (even if the device is locked?!)
+ booting into recovery
What doesn't work:
- unlocking via fastboot oem unlock
PepRoween said:
So I was trying to root my OP2 for the second time (apparently it derooted itself for some reason?)
But now I can't unlock oem from fastboot.
I magicly could flash TWRP and from there I installed SuperSU.
But when I booted my device up, it get's bricked into a boot loop.
I got out of the boot loop and tried again.
So I go into fastboot mode and tried the command again:
PLEASE do not link me to the unbrick guides - the problem is NOT that it's bricked - The problem is that I can't unlock oem from fastboot and so I can't succesfull root my phone.
What works:
+ getting into the OS
+ getting into fastboot
+ flashing a recovery (even if the device is locked?!)
+ booting into recovery
What doesn't work:
- unlocking via fastboot oem unlock
Click to expand...
Click to collapse
If you can fastboot flash a custom recovery then your device isn't locked.
When you flashed SuperSU, did you use the stock version and force a systemless installation or did you use a modified version that does this automatically?
If you used the stock version and didn't force a systemless installation, this is probably the reason you're bootlooping.
Spannaa said:
If you can fastboot flash a custom recovery then your device isn't locked.
When you flashed SuperSU, did you use the stock version and force a systemless installation or did you use a modified version that does this automatically?
If you used the stock version and didn't force a systemless installation, this is probably the reason you're bootlooping.
Click to expand...
Click to collapse
Thank you for the advice, maybe I can use it another time.
I saw where someone said you could flash B20 bootloader and flash TWRP on Nougat, is this true? Is anyone working on a guide for Nougat TWRP and root. On another note I thought that I read that ZTE would be bringing Wifi calling for Nougat with carries such as T-Mobile? I was unable.to find it under options and assume that it is not possible, anyone have any idea about this.
Thanks
I have an unlocked BL and recently upgraded to Nougat, but when I try to reinstall TWRP via fastboot flash method, it fails. I have tried two different versions of TWRP 3.0.3-1 & 3.0.4-1. This is the message I get.
PS C:\adb> fastboot flash recovery twrp-3.0.4-1-a7.img
target reported max download size of 536870912 bytes
sending 'recovery' (14472 KB)...
OKAY [ 0.332s]
writing 'recovery'...
FAILED (remote: unknown command)
finished. total time: 0.363s
Any ideas?
jim262 said:
I have an unlocked BL and recently upgraded to Nougat, but when I try to reinstall TWRP via fastboot flash method, it fails. I have tried two different versions of TWRP 3.0.3-1 & 3.0.4-1. This is the message I get.
PS C:\adb> fastboot flash recovery twrp-3.0.4-1-a7.img
target reported max download size of 536870912 bytes
sending 'recovery' (14472 KB)...
OKAY [ 0.332s]
writing 'recovery'...
FAILED (remote: unknown command)
finished. total time: 0.363s
Any ideas?
Click to expand...
Click to collapse
I got TWRP 3.0.4 installed (as well as 3.0.3-1)... It installed sucessfully via Fastboot for me, I even flashed SU, but I couldn't get my phone to boot into the OS (tried with and without SU).......It just hung at the boot pre-boot screen (where it warns you the bootloader is unlocked). I'd restart it, and it always hangs at that screen..... Only way to fix it was to boot back into TWRP, revert back to B29 (using DrakenFX guide) and then update to Nougat again. I spent about 16 hours straight working on this on Tuesday, before I gave up and decided to keep it stock until a custom ROM comes out, soon (Z.A.D. v.4), hopefully?
I have an issue where I installed B15 but whenever I boot my phone, it hangs on the Linux Tux logo. Any fix?
xDaDeevellopar said:
I have an issue where I installed B15 but whenever I boot my phone, it hangs on the Linux Tux logo. Any fix?
Click to expand...
Click to collapse
You probably pushed the power button to "Start"? Try letting it sit there about 10-15 seconds, if it won't boot...This is the exact same problem I had. I had to go back to B29, then do the update again. There is now a B15 "return to stock" walk-through, that may be the quicker route.....But I know returning to B29, turning on OEM Unlock in Dev options and then taking the update via your SD card was what I did (3 times in one day).
Flash signed TWRP with tennear's tool (axon7tool):
https://forum.xda-developers.com/axon-7/development/axon7tool-flash-backup-boot-recovery-t3514254
https://we.tl/dv78KwQZCY
and then follow this guide:
https://forum.xda-developers.com/axon-7/how-to/guide-how-to-unlock-bootloader-stay-t3461165
3 files and 10 minutes of your time for TWRP + unlocked bootloader
bornlivedie said:
Flash signed TWRP with tennear's tool (axon7tool):
https://forum.xda-developers.com/axo...overy-t3514254
https://we.tl/dv78KwQZCY
and then follow this guide:
https://forum.xda-developers.com/axo...-stay-t3461165
3 files and 10 minutes of your time for TWRP + unlocked bootloader
Click to expand...
Click to collapse
Those 2 XDA links don't work, take me to a generic XDA 404 error page (on both)...the WeShare page worked.
tele_jas said:
Those 2 XDA links don't work, take me to a generic XDA 404 error page (on both)...the WeShare page worked.
Click to expand...
Click to collapse
That's because I copypasted lol
https://forum.xda-developers.com/axon-7/development/axon7tool-flash-backup-boot-recovery-t3514254
https://forum.xda-developers.com/axon-7/how-to/guide-how-to-unlock-bootloader-stay-t3461165
bornlivedie said:
That's because I copypasted lol
https://forum.xda-developers.com/axon-7/development/axon7tool-flash-backup-boot-recovery-t3514254
https://forum.xda-developers.com/axon-7/how-to/guide-how-to-unlock-bootloader-stay-t3461165
Click to expand...
Click to collapse
If my bootloader is already unlocked, can I skip that part (the 2nd link)?? Or is it necessary?
tele_jas said:
If my bootloader is already unlocked, can I skip that part (the 2nd link)?? Or is it necessary?
Click to expand...
Click to collapse
Those steps are meant to unlock the bootloader.
You don't need any of it. You already have TWRP (skip step 1) and bootloader unlocked (skip step 2) so yeah...
What do you want exactly?
bornlivedie said:
Those steps are meant to unlock the bootloader.
You don't need any of it. You already have TWRP (skip step 1) and bootloader unlocked (skip step 2) so yeah...
What do you want exactly?
Click to expand...
Click to collapse
My bootloader is unlocked (back when ZTE actually provided the unlocking)....adb fastboot works on my phone as well and I've flashed TWRP (3.0.4 and 3.0.3-1) and it's booted into TWRP, but I cannot boot into the actual OS...My phone goes all black and just hangs there, I think this may be booting directly into EDL mode and not the OS? I can plug my phone into the computer and my computer makes noises as if a USB device has been attached, but my screen is completely black. If I push the start button while the phone is booting (to bypass the bootloader is unlocked warning screen), I boot to a small penguin screen.
The only thing I can do from there is revert back to stock B29, then update back to stock B15.
I want to be able to install TWRP, root my phone, on Nougat, and be able to use my phone too?
tele_jas said:
My bootloader is unlocked (back when ZTE actually provided the unlocking)....adb fastboot works on my phone as well and I've flashed TWRP (3.0.4 and 3.0.3-1) and it's booted into TWRP, but I cannot boot into the actual OS...My phone goes all black and just hangs there, I think this may be booting directly into EDL mode and not the OS? I can plug my phone into the computer and my computer makes noises as if a USB device has been attached, but my screen is completely black. If I push the start button while the phone is booting (to bypass the bootloader is unlocked warning screen), I boot to a small penguin screen.
The only thing I can do from there is revert back to stock B29, then update back to stock B15.
I want to be able to install TWRP, root my phone, on Nougat, and be able to use my phone too?
Click to expand...
Click to collapse
Then follow this:
https://forum.xda-developers.com/axon-7/development/edl-emergency-dl-mode-twrp-unlock-t3553514
and flash this:
https://forum.xda-developers.com/showpost.php?p=68873482&postcount=2
I think I know what happened to you... did you by any chance allow system modifications in TWRP? That makes the OS bootloop if you have Nougat.
bornlivedie said:
Then follow this:
https://forum.xda-developers.com/axon-7/development/edl-emergency-dl-mode-twrp-unlock-t3553514
and flash this:
https://forum.xda-developers.com/showpost.php?p=68873482&postcount=2
I think I know what happened to you... did you by any chance allow system modifications in TWRP? That makes the OS bootloop if you have Nougat.
Click to expand...
Click to collapse
The MiFlash program found my phone, but failed every time I ran it.. So, I just bit the bullet and downloaded the latest TWRP 3.0.4-1 and flashed that.....And it worked! I then flashed SU, my fonts and changed my Emoji's....I'm about there with customization, and it's all booting up just fine!
But, yes the first few times I did allow system modifications......But I also did this last time too and it's working fine?
Long story short. I had an Axon 7 A2017 B11 which I updated to B13. I was able to unlock the bootloader, root the phone then flash a custom rom Z.A.D.Mix7_v0.3. I was having fun with the phone but I did something very stupid when I realised I could not use Android pay due to unlocked boot loader. Without doing enough research, I went to fastboot and did a fastboot oem lock. The command was successful but I could no longer boot into the system or recovery or fastboot. I tried MiFlash with B07 which was posted in this forum, but it did not work, came back an error of bad format. Then I used axon7tool to flash TWRP 3.0.2 and the boot.img which I extracted from B13. I am now able to boot into TWRP and fastboot. But I still do not have a working system. I tried fastboot oem unlock, it does not let me do it. I flash ZAD Mix7 again but once I flash that it does not boot anymore. I am now really stuck. What should I do to go back to stock then start everything again. Thanks a lot for the help.
I understand your device doesn't boot into system anymore, but can adb on your pc detect it at all? If so, you can try following all steps after "B)" in my tutorial. I think your aboot img and fbop partition are messed up. If you can use adb to replace the files in aboot and fbop with files that allow the fastboot oem unlock command to be executed, it should be unlockable again. After that, custom ROMs should boot.
Stock bootloader
Controllerboy said:
If you can use adb to replace the files in aboot and fbop with files that allow the fastboot oem unlock command to be executed, it should be unlockable again. After that, custom ROMs should boot.
Click to expand...
Click to collapse
I'm having a similar issue. Although my phone boots to stock rom I seem to have messed up my bootloader. I had TWRP and unlocked bootloader. I, similarly, locked the bootloader and things seemed to be fine. After attempting to install Nougat received from OTA I realized my bootloader is corrupted. When I hold the power and volume up the phone seems to just turn off (or go to EDL mode? I'm not sure) I can always just hold power and it'll boot up normally. Is there a way to get the stock bootloader to work and keep it locked?
I also bricked my A7 after relocking my bootloader. I used tenfar's tool to make TWRP my boot.img, then flashed ZTE's stock B20 image. Here's the thread where I found the file links.
From there I updated all the way up to the OTA Nougat, but I suppose you can decide where you want to go after it's unbricked. Hope this helps.
Why are so many people relocking bl? Regardless, always take an ota before locking to ensure you are completely shock.
Stock bootloader
lafester said:
Why are so many people relocking bl? Regardless, always take an ota before locking to ensure you are completely shock.
Click to expand...
Click to collapse
Don't you have to be running a locked bootloader in order to be able to install OTAs?
aabnamak said:
Don't you have to be running a locked bootloader in order to be able to install OTAs?
Click to expand...
Click to collapse
Of course not.
aabnamak said:
Don't you have to be running a locked bootloader in order to be able to install OTAs?
Click to expand...
Click to collapse
No, you do not. I thought that was the case at first as well, but I was mistaken. You do, however, need the stock recovery and an untouched system partition.
My problem is that I don't seem to have a recovery at all. I realized once the ZTE logo pops up I can hold down both volume keys and get to the bootloader. The bootloader is locked but does not display a bootloader version or basedband version. I tried the tenfar tool (axon7root.exe) and now my phone doesn't boot into the system either. I really need help...
Just an update to everyone that helped.
I finally managed to fix it.
I used axon7tool to flash a signed TWRP, so that i can boot into TWRP. The signed TWRP is the only way to make it work. Then I downloaded the A2017 B11 from this thread
https://forum.xda-developers.com/axon-7/development/rom-guide-updates-to-stock-files-via-t3469484
There are two zip files. The boot stack and the rom. Because it is a stock rom, I can boot into the system. The next thing I did was to enable the developer option and turn back on the option to allow OEM unlock.
I went back to TWRP. boot into the fastboot screen. Then I simply typed in 'fastboot oem unlock'.
I went back to TWRP, which says can't read encrypted device. I formated everything. mount the USB then flash the custom rom again.
Hola, phone fixed. Made me sweat for the whole day.
deleted...forgot I had a micro sd card. Flashed stock update from the card and it worked. Phew!
I was trying to flash the stock image and i guess i messed up somewhere because after i did that i locked the bootloder and not it is not booting past the google screen. i want to reflash all images but i cant cause the bootloader is locked. so is there anyway to unlock the oem in bootloader or recovery mode TWRP? i can access terminal in TWRP so any command that can help me?
TheTickReborn said:
I was trying to flash the stock image and i guess i messed up somewhere because after i did that i locked the bootloder and not it is not booting past the google screen. i want to reflash all images but i cant cause the bootloader is locked. so is there anyway to unlock the oem in bootloader or recovery mode TWRP? i can access terminal in TWRP so any command that can help me?
Click to expand...
Click to collapse
Maybe try and sideloading the it's through twrp. I can't remember if an unlocked bootloader is needed though. Also, you could maybe try flashing a custom ROM to see if you can boot into it.