Related
This is FINAL working method.
First off you must unlock bootloader, and install twrp.
instructions for unlock bootloader are in this thread
http://forum.xda-developers.com/r1-...mazon-root-t3490882/post69387472#post69387472
I made many cycles between 6.6 and 6.1 and found that this set of files was minimum needed to maintain stable device. I started with only the preloader, and that left the phone able to connect to spft but the preloader was o longer in the "trusted zone" so it would not load the second step of power on (lk). replaceing the lk with spft after that allowed to boot to the boot menu, but would not trust the next step(boot.img). But with the preloader and lk I was able to fastboot, so was able to oem unlock.. this was the first method I was going to suggest. After more trials I decided it better to foll back all the bin files that the update replaced and also the secret bin so no more need to oem unlock after the roll back.
I got so comfortable moving between preloaders and version I got careless. My carelessness allowed me to mix up secure preloader and bin files with custom non secure recovery files and without realizing it I rebooted like that. I was left in a secure environment that was panicking because the recovery was not properly signed. (a terminal soft-brick)
My point is once you roll back DO NOT go back to locked and DO NOT blame me if you forget and restore some backup that does that to you down the road.
I do recomend that you roll back though. Because with the roll back, you are almost certain not able to brick because you can always use spft to to fix things.
THIS WILL ROLL BACK BOOT LOADER AND ALLOWS SPFT .
THIS HAS ONLY BEEN RUN WITH TWRP.
But the fastboot mode can also flash preloader if prefered. Just remember you may also need to oem unlock again after. This has not and will not be tested by me.
ONCE YOU HAVE UNLOCKED BOOTLOADER AND INSTALLED TWRP, return here and download "after_bootloader_roll_back_5.tar" unpack the tar and run the .bat file. It will adb push the recovery image to you phone and then install it.
It will rewrite :
1. preloader
2. lk (little kernel)
3. boot img
4. seccfg.bin
5. frp (to make sure bootloader remains unlockable)
6. trustzone (goes into both TEE1 and TEE2
7. secro.bin
All done.
If you failed to follow the warning and tried without a valid backup here is a link my zero-day backup. It will bring you back to 6.1 and you will need to unlock and root all over again. Good news is that this time you can do it with spft https://drive.google.com/open?id=0ByJNKJ8bGC50Vzg5QjJXS3VjcTQ
Hi, I follow all steps and now my R1HD its in a loop at the first screen (BLU BOLD LIKE US ...). Before that, my cellphone and twrp working well. what can I do?
jhonjahegu said:
Hi, I follow all steps and now my R1HD its in a loop at the first screen (BLU BOLD LIKE US ...). Before that, my cellphone and twrp working well. what can I do?
Click to expand...
Click to collapse
Sounds like you need to do oem unlock again. That is what the first methods needed.
Did you use the current downloaded roll back 5.tar file or one of the earlier ones?
Start with these instructions.
1. Hold volume up while phone is boot looping.
2. Select fastboot mode
3. Open terminal or Windows command window and type "fastboot getvar all"
4. Near the end of the output check for these entries.
Unlock=yes
Secure=no
5. If not these values do "fastboot oem unlock"
6. If need to do oem unlock you will also need to "fastboot format userdata"
The script did not work. It just boot loops and I do have: Unlock=yes and Secure=no
mrmazak said:
Sounds like you need to do OEM unlock again. That is what the first methods needed.
Did you use the current downloaded roll back 5.tar file or one of the earlier ones?
Start with these instructions.
1. Hold volume up while phone e is boot looping.
2. Select fastboot mode
3. Open terminal or Windows command window and type "fastboot getvar all"
4. Near the end of the output check for these entries.
Unlock=yes
Secure=no
5. If not these values do "fastboot OEM unlock"
6. If need to do OEM unlock you will also need to "fastboot format userdata"
Click to expand...
Click to collapse
digihaven said:
The script did not work. It just boot loops and I do have: Unlock=yes and Secure=no
Click to expand...
Click to collapse
If it is looping into twrp then you must do step 6 from above.
I run this with TWRP installed, and it turns off my phone , it disconnects my device, it turns back on, reconnected, then it disconnects again and never reconnects it so I cant send any commands or the like. Does anyone know a solution to this?
clownkitty said:
I run this with TWRP installed, and it turns off my phone , it disconnects my device, it turns back on, reconnected, then it disconnects again and never reconnects it so I cant send any commands or the like. Does anyone know a solution to this?
Click to expand...
Click to collapse
Need more details please.
Like when it comes back on is it on in twrp screen.?
Did you unpack the rar into one folder, leaving the zip file zipped, and run the batch from the folder with the zip in it?
You can also just copy the zip file onto phone and install it in twrp.
mrmazak said:
Need more details please.
Like when it comes back on is it on in twrp screen.?
Did you unpack the rar into one folder, leaving the zip file zipped, and run the batch from the folder with the zip in it?
You can also just copy the zip file onto phone and install it in twrp.
Click to expand...
Click to collapse
Turns out that I'm just having a lot more issues than i thought, i cant get it to the TWRP screen, though I used the method from https://forum.xda-developers.com/r1-hd/how-to/blu-r1-hd-v6-6-dirtycowed-f-amazon-root-t3490882/ and tried manually flashing the recovery file from https://forum.xda-developers.com/r1-hd/development/prime-stock-rom-6-5-flashed-via-twrp-t3455532
If I do adb reboot recovery, it just gives my a screen with a maintenance android logo with the text "no command."
I did just unpack the rar, and leave the zip file zipped as well
clownkitty said:
Turns out that I'm just having a lot more issues than i thought, i cant get it to the TWRP screen, though I used the method from https://forum.xda-developers.com/r1-hd/how-to/blu-r1-hd-v6-6-dirtycowed-f-amazon-root-t3490882/ and tried manually flashing the recovery file from https://forum.xda-developers.com/r1-hd/development/prime-stock-rom-6-5-flashed-via-twrp-t3455532
If I do adb reboot recovery, it just gives my a screen with a maintenance android logo with the text "no command."
I did just unpack the rar, and leave the zip file zipped as well
Click to expand...
Click to collapse
You needed to hold power and volume up when restarting from fastboot during the procedure. [[ I maybe should have more comments in the script. The 6.6 update replaced the lk.bin(in has the fastboot, gaming other things). The replaced version got rid of "fastboot reboot", so when my script issues that command with the updated lk the phone just does nothing.]]. Then from the boot menu load directly into recovery or else the stock recovery gets replaced, like what you have.
Also check that the unlock part worked for you by doing "fastboot getvar all" from fastboot mode. Verify you have "unlock: yes"
If so try again to get recovery flashed,
mrmazak said:
You needed to hold power and volume up when restarting from fastboot during the procedure. [[ I maybe should have more comments in the script. The 6.6 update replaced the lk.bin(in has the fastboot, gaming other things). The replaced version got rid of "fastboot reboot", so when my script issues that command with the updated lk the phone just does nothing.]]. Then from the boot menu load directly into recovery or else the stock recovery gets replaced, like what you have.
Also check that the unlock part worked for you by doing "fastboot getvar all" from fastboot mode. Verify you have "unlock: yes"
If so try again to get recovery flashed,
Click to expand...
Click to collapse
I didn't realize you had to load straight into recovery mode after flashing it, I got it to work now, thank you so much!
Hi,
I'm on version 7.4.2 and do unlock bootloader. And then rollback but now I have a problem with mobile data.
I can't use mobile data anymore I already check and APN are Ok.
Phone reboot some times and change some sim but have the same problem.
tuespazio said:
Hi,
I'm on version 7.4.2 and do unlock bootloader. And then rollback but now I have a problem with mobile data.
I can't use mobile data anymore I already check and APN are Ok.
Phone reboot some times and change some sim but have the same problem.
Click to expand...
Click to collapse
I do not have an answer for you, bit didn't want you to think you are ignored. Nobody else has had this problem before,
mrmazak said:
I do not have an answer for you, bit didn't want you to think you are ignored. Nobody else has had this problem before,
Click to expand...
Click to collapse
Hi, dont worry now is fixed i return to 6.1 and then flash full 6.5 firmware.
Data is now working fine .
Thanks for your Support
sorry, wrong thread
ncy1 said:
Hi guys, sorry to bother you with this
I was on 6.0 rooted and without ads, i just tried to update my phone using the v17 and settings on this thread, when i went to cellphone info on settings it said i was still on 6.0. Did i miss something or this a normal thing? Anyway, i went back to recovery mode, did a wipe and tried to flash the 7.4.2 rom but it sent me an error, now the phone won't boot and gets stuck on the blu loadscreen.
Click to expand...
Click to collapse
Don't get me wrong, I feel bad for you that your phone is in this situation, but that has nothing to do with the thread you are posting in.
This thread is for rolling back the preloader.
And all the oem and Amazon Roms are 6.0
To get help you should post in the thread you got the ROM from.
And include the error you got.
mrmazak said:
If you failed to follow the warning and tried without a valid backup here is a link my zero-day backup. It will bring you back to 6.1 and you will need to unlock and root all over again. Good news is that this time you can do it with spft https://drive.google.com/open?id=0ByJNKJ8bGC50Vzg5QjJXS3VjcTQ
Click to expand...
Click to collapse
I think I just want to try this method, since I want to convert it to OEM and still keep OTA updates anyway. I'm blanking though as to how I need to go about this.
I have adb installed, and I have access. I assume this requires a fastboot command, but I don't know which.
Jessooca said:
Mrmazak... does this work on a new out of the box blu r1 that came with the 6.6 August update already installed?
I'm trying to help a friend, I surprisingly can't get the bootloader unlocked, dirtycow continually failed.
He doesn't care about updates etc... just wanted to flash the no ads firmware onto a prime version blu r1 hd
Click to expand...
Click to collapse
To the best of my knowledge it was.
Last time someone told me they were having trouble, they ran the codes manually one by one instead of using the script, and it worked. Apparently they had trouble pushing the files from the batch file. I had similar trouble when I wrote the script, that is why there are 3 second pauses ,that seemed to fix it for me. I will change them to 10 seconds and see if it helps.
I will update here when I change it then you candownload again and try, or you can make the changes yourself and let the me know
OK i updated the one-click.bat . you can download it again to see if that help. Also you said dirty-cow keeps failing, please let me know the fail message and also the comments displayed during the first part of the script. the part that is pushing files.
Also I have not been able to get feedback on the one-click.sh for linux. I don't normally use linux and did not test the shell. If you are using that one maybe the fail is my poorly written .sh
mrmazak said:
Sounds like you need to do OEM unlock again. That is what the first methods needed.
Did you use the current downloaded roll back 5.tar file or one of the earlier ones?
Start with these instructions.
1. Hold volume up while phone e is boot looping.
2. Select fastboot mode
3. Open terminal or Windows command window and type "fastboot getvar all"
4. Near the end of the output check for these entries.
Unlock=yes
Secure=no
5. If not these values do "fastboot OEM unlock"
6. If need to do OEM unlock you will also need to "fastboot format userdata"
Click to expand...
Click to collapse
Hi, I'm also stuck on the "BLU Bold like us" loop. When I try to do the "fastboot OEM unlock" I get a list of possible commands but it doesn't perform de OEM unlock... Can you help me please? Thanks
danbcooper said:
Hi, I'm also stuck on the "BLU Bold like us" loop. When I try to do the "fastboot OEM unlock" I get a list of possible commands but it doesn't perform de OEM unlock... Can you help me please? Thanks
Click to expand...
Click to collapse
"oem" is not supposed to be capitalized
i went back and edited that original post too.
mrmazak said:
"oem" is not supposed to be capitalized
i went back and edited that original post too.
Click to expand...
Click to collapse
Now I ran "fastboot oem unlock" and it says FAILED (remote: unknown command). Do you know why?
Never mind.. Tried again and worked! Thanks for everything!
EDIT: Fixed! Big thanks to @S0wL , @bkores , @tamahouse02 and @tron1 for the help. I made a guide to help other people with the same problem:
Guide to get TWRP again HERE
Okay, it seems to me that I messed up kinda badly. The phone is fully operational, but after I got to 7.0 the stock recovery replaced good ol' TWRP... which left me with an unlocked bootloader and an useless recovery. I have no root, and that's pretty much the only thing that matters to me. I downloaded @bkores 's Axon7Toolkit but there is NO way to get fastboot on the damned thing. After the program tries to get to bl mode (I assume adb reboot bootloader?) the ZTE logo flashes and the unlocked BL image appears, then the phone starts as normal.
Same thing with the leaked 7.1.1, no difference.
I tried EDL, recovery, that shady factory test mode thing, no one gives fastboot... Any ideas as to why I can't get there??+
I suspect it may be something related to the OEM unlocking option in the dev options, but it is set to ON and greyed out. so no idea
Try the menu on the boot screen.
Choose an username... said:
Okay, it seems to me that I messed up kinda badly. The phone is fully operational, but after I got to 7.0 the stock recovery replaced good ol' TWRP... which left me with an unlocked bootloader and an useless recovery. I have no root, and that's pretty much the only thing that matters to me. I downloaded @bkores 's Axon7Toolkit but there is NO way to get fastboot on the damned thing. After the program tries to get to bl mode (I assume adb reboot bootloader?) the ZTE logo flashes and the unlocked BL image appears, then the phone starts as normal.
Same thing with the leaked 7.1.1, no difference.
I tried EDL, recovery, that shady factory test mode thing, no one gives fastboot... Any ideas as to why I can't get there??+
I suspect it may be something related to the OEM unlocking option in the dev options, but it is set to ON and greyed out. so no idea
Click to expand...
Click to collapse
Sounds like the issue is with the ROM like it is somehow blocking you from accessing bootloader mode. It's definitely not my toolkit.
Choose an username... said:
Okay, it seems to me that I messed up kinda badly. The phone is fully operational, but after I got to 7.0 the stock recovery replaced good ol' TWRP... which left me with an unlocked bootloader and an useless recovery. I have no root, and that's pretty much the only thing that matters to me. I downloaded @bkores 's Axon7Toolkit but there is NO way to get fastboot on the damned thing. After the program tries to get to bl mode (I assume adb reboot bootloader?) the ZTE logo flashes and the unlocked BL image appears, then the phone starts as normal.
Same thing with the leaked 7.1.1, no difference.
I tried EDL, recovery, that shady factory test mode thing, no one gives fastboot... Any ideas as to why I can't get there??+
I suspect it may be something related to the OEM unlocking option in the dev options, but it is set to ON and greyed out. so no idea
Click to expand...
Click to collapse
Feel the same, 7.1.1 stock recovery is evil, it keep coming back after flash twrp. LOL
Here what I didi to get twrp on 7.1.1:
1. Use axon7tool -w recovery (twrp of couse)
2. Watch closely the cmd, when it said "Successful!","Reboot in 5 second" - unplug your phone
3. Use Volume Up + Power to get to recovery (twrp)
4. Mount > Mount System (dont check read only)
5. Flash something - I don't know - But I get the feeling that it stop stock recovery coming back - I personally flash Chinese Modem (because I have to ))
6. Reboot system
@bkores Yeah I'm pretty sure it's not your toolkit since I can't access it even with key comb, adb, option on the unl bl page...
@lafester Nope, tried many times. It just boots to normal whenever I select fastboot
@tamahouse02 Well I believe that should work, but I can't get axon7tool not to crash... I'll keep trying, maybe it's a driver or sth.
Choose an username... said:
@bkores Yeah I'm pretty sure it's not your toolkit since I can't access it even with key comb, adb, option on the unl bl page...
@lafester Nope, tried many times. It just boots to normal whenever I select fastboot
@tamahouse02 Well I believe that should work, but I can't get axon7tool not to crash... I'll keep trying, maybe it's a driver or sth.
Click to expand...
Click to collapse
Have you restart after install zadig driver?
1. From system: adb reboot edl
2. Install zadig driver
3. Hold "Volume Up + Power"
4. Enter system again: adb reboot edl
5. axon7tool -w recovery
tamahouse02 said:
Have you restart after install zadig driver?
1. From system: adb reboot edl
2. Install zadig driver
3. Hold "Volume Up + Power"
4. Enter system again: adb reboot edl
5. axon7tool -w recovery
Click to expand...
Click to collapse
yes, like 4 times already. I even used the stock Qualcomm COM3 drivers... no dice.
the thing is that I had to do the same when I did the stuff on android 6 and it worked after some time. I even wrote the procedure on another thread xd
Choose an username... said:
yes, like 4 times already. I even used the stock Qualcomm COM3 drivers... no dice.
the thing is that I had to do the same when I did the stuff on android 6 and it worked after some time. I even wrote the procedure on another thread xd
Click to expand...
Click to collapse
Not same my axon7tool. I use this https://forum.xda-developers.com/axon-7/development/axon7tool-flash-backup-boot-recovery-t3514254
Bootloader Mode is Disable/strip in G variant, and if this is how ZTE is headed to future updates it seems like U will have a Disable Bootloader Mode as well.
If you guy can rollback to MM , you can Unlock there using @bkores tool.
DrakenFX said:
Bootloader Mode is Disable/strip in G variant, and if this is how ZTE is headed to future updates it seems like U will have a Disable Bootloader Mode as well.
If you guy can rollback to MM , you can Unlock there using @bkores tool.
Click to expand...
Click to collapse
I was thinking about that, but does mifavor let you roll back from an SD update? I'll try later, but i doubt it.
Besides from that is there any way to flash stuff from the stock recovery? It tells me that ZIPs have to be signed only
tamahouse02 said:
Feel the same, 7.1.1 stock recovery is evil, it keep coming back after flash twrp. LOL
Here what I didi to get twrp on 7.1.1:
1. Use axon7tool -w recovery (twrp of couse)
2. Watch closely the cmd, when it said "Successful!","Reboot in 5 second" - unplug your phone
3. Use Volume Up + Power to get to recovery (twrp)
4. Mount > Mount System (dont check read only)
5. Flash something - I don't know - But I get the feeling that it stop stock recovery coming back - I personally flash Chinese Modem (because I have to ))
6. Reboot system
Click to expand...
Click to collapse
In step 1, which TWRP version did you use? The latest 3.1.0.-0 ?
dnlilas said:
In step 1, which TWRP version did you use? The latest 3.1.0.-0 ?
Click to expand...
Click to collapse
Official 3.0.4.1
@tamahouse02
The latest "official" TWRP is at TWRP site https://twrp.me/devices/zteaxon7.html , version 3.1.0-0.
Is there any problem using it instead of the previous "official" 3.0.4.1 ?
Edit: I also read on TWRP site:
"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."
This is in sync with your information requiring to reboot immediately to TWRP (step 2 and 3).
dnlilas said:
@tamahouse02
The latest "official" TWRP is at TWRP site https://twrp.me/devices/zteaxon7.html , version 3.1.0-0.
Is there any problem using it instead of the previous "official" 3.0.4.1 ?
Edit: I also read on TWRP site:
"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."
This is in sync with your information requiring to reboot immediately to TWRP (step 2 and 3).
Click to expand...
Click to collapse
I use 3.0.4.1 because I flash plenty things before without any issue, so I keep using it.
After write recovery by axon7tool, it's reboot automatically and override the recovery, that why I have to unplug to stop the reboot, and also flash all I can - fortunaeally it also stop recovery be overrided
@tamahouse02 sorry to ask, but is the a7tool of the link a fixed version? how does it differ from the one i have?
I've been in the same situation like you @Choose an username... Updated to nougat on G model and I had not bootloader. This is what I did :
1. Downloaded the tool from here https://forum.xda-developers.com/axon-7/development/tool-axon7toolkit-t3573108
2. Installed the driver using the install driver option that you can choose once you connect you phone to your computer
3. Use the tool to perform the unlock bootloader command again even though you have unlocked it before
4. Use the tool to install twrp, it will boot the phone in twrp
5. Flash Supersu before you boot the system first time after flashing twrp
5. Install whatever version of android want after
@S0wL Funny, I had to use Zadig to make it work. I'll try r n, thx
Choose an username... said:
@S0wL Funny, I had to use Zadig to make it work. I'll try r n, thx
Click to expand...
Click to collapse
Use Zadig then and let me know if it worked
@S0wL I can't use bootloader unlock on it, says "This option does not support your device!"
How did you do this??
Choose an username... said:
@tamahouse02 sorry to ask, but is the a7tool of the link a fixed version? how does it differ from the one i have?
Click to expand...
Click to collapse
I try your version once, but it seems not work for me, so I keep using the old one.
---------- Post added at 03:42 AM ---------- Previous post was at 03:39 AM ----------
Choose an username... said:
@S0wL I can't use bootloader unlock on it, says "This option does not support your device!"
How did you do this??
Click to expand...
Click to collapse
I thought you had already unlocked bootloader? Why have you done it twice?
Hi,
don't know if this problem has already occurred before.
I had lineage and TRWP installed on my Axon 7 (EU version) and wanted to go back to the stock a2017g.
Therefore I deleted the ROM and wiped everything with TWRP.
Then I deleted TWRP and now i'm stuck at the the bootloader (which is unlocked), but TWRP seems to be gone.
The main problem is, whenever I try to flash a new stock rom (via recovery), I get the error "signature verification failed" and the process is aborted with no change to the system whatsoever.
Is there anything I can do at this point or is my phone practically dead?
Thanks in advance for any help.
tempest89 said:
Hi,
don't know if this problem has already occurred before.
I had lineage and TRWP installed on my Axon 7 (EU version) and wanted to go back to the stock a2017g.
Therefore I deleted the ROM and wiped everything with TWRP.
Then I deleted TWRP and now i'm stuck at the the bootloader (which is unlocked), but TWRP seems to be gone.
The main problem is, whenever I try to flash a new stock rom (via recovery), I get the error "signature verification failed" and the process is aborted with no change to the system whatsoever.
Is there anything I can do at this point or is my phone practically dead?
Thanks in advance for any help.
Click to expand...
Click to collapse
Try to boot into bootloader interface, and issue command "fastboot flash recovery TWRP.img" on your computer( the current working directory should contain the TWRP.img file) . If your bootloader is unlocked, you should see no error of this command. Then press up/down button to select recovery mode. You should see the familiar TWRP again. Good luck!
tempest89 said:
Hi,
don't know if this problem has already occurred before.
I had lineage and TRWP installed on my Axon 7 (EU version) and wanted to go back to the stock a2017g.
Therefore I deleted the ROM and wiped everything with TWRP.
Then I deleted TWRP and now i'm stuck at the the bootloader (which is unlocked), but TWRP seems to be gone.
The main problem is, whenever I try to flash a new stock rom (via recovery), I get the error "signature verification failed" and the process is aborted with no change to the system whatsoever.
Is there anything I can do at this point or is my phone practically dead?
Thanks in advance for any help.
Click to expand...
Click to collapse
Did you try flashing an official full zip, like B10? That's another thing you can try, since you're going to lose TWRP after you flash a stock rom anyways
If you dont have recovery, flash it from edl mode, you can flash twrp or stock.
Once you install it, performa a full wipe from stock recovery, and flash a full zip.
I have similar problems, I dont loose recovery, but stock dont boot after coming back from aosp, a factory reset did the job. I think is because different filesystems in data partition
Choose an username... said:
Did you try flashing an official full zip, like B10? That's another thing you can try, since you're going to lose TWRP after you flash a stock rom anyways
Click to expand...
Click to collapse
Hi, the B10 ROM from the ZTE homepage did the trick.
Worked out nicely.
Thank you so much.
One final question remains for myself: How can I relock the bootloader (so that the 5 second screen won't show up at the start).
Tried different ways with adb and fastload, but nothing seemed to have an effect here.
So what to do?
Thank you again for your help.
tempest89 said:
Hi, the B10 ROM from the ZTE homepage did the trick.
Worked out nicely.
Thank you so much.
One final question remains for myself: How can I relock the bootloader (so that the 5 second screen won't show up at the start).
Tried different ways with adb and fastload, but nothing seemed to have an effect here.
So what to do?
Thank you again for your help.
Click to expand...
Click to collapse
you shouldn't. Fastboot should do the trick, by doing fastboot oem lock, but many people reported bricking and bad stuff...
Actually that screen comes very handy in case of a brick or if you want to enter a specific mode.l, you just select the mode and voila
Do you have fastboot? I don't know if B10 still has it, but 7.0 hasn't got it
Choose an username... said:
you shouldn't. Fastboot should do the trick, by doing fastboot oem lock, but many people reported bricking and bad stuff...
Actually that screen comes very handy in case of a brick or if you want to enter a specific mode.l, you just select the mode and voila
Do you have fastboot? I don't know if B10 still has it, but 7.0 hasn't got it
Click to expand...
Click to collapse
Hi,
I tried adb and fastboot via pc and with the axon toolkit.
The adb worked fine, but no sign of effect by the fastboot commands.
So I guess I don't have it.
Is there any other solution to at least bypass the 5 second screen?
Thanks
tempest89 said:
Hi,
I tried adb and fastboot via pc and with the axon toolkit.
The adb worked fine, but no sign of effect by the fastboot commands.
So I guess I don't have it.
Is there any other solution to at least bypass the 5 second screen?
Thanks
Click to expand...
Click to collapse
Lol fastboot is not something like EDL, it looks similar to the 5 sec screen...
When you get the 5 sec screen, use the vol keys and pwr to get to the Fastboot option and enter - it should reboot and get to fastboot after some time
You should look up what fastboot, EDL, ADB and DFU are before doing all this stuff - you can mess up badly, and by not knowing you're complicating everything - my explanation and your understanding
I think I messed up my PH-1 something royally.
All I was trying to do is unlock my bootloader and load Magisk.
To preface this, my PH-1 seemed to act a little wonky from the get-go. I bought it 3rd person from a guy on craigslist so anything warranty involved I think I'm out of luck.
The phone would take a while to power on, it took something like 10secs on the power button just to turn it on. And if I set it to reboot , it boots into the bootloader. Also, I was never able to access the recovery (even using power + up). It always felt like I had to hold the buttons for way to long to get to its destination; e.g. up and power to get into fastboot.
Ok where I'm at now. In can occasionally get into fastboot mostly after it bootlooping a few times. It won't get past the Essential logo if I try to boot it up.
PS I was able to unlock the bootloader.
Steps I took to remedy this:
> erase all user data in fastboot
> hold power + u + d to hard power off
> follow this guide https://forum.xda-developers.com/essential-phone/how-to/guide-rooting-essential-ph-1-magisk-t3701976
> attempt to install stock system image via flash-all
>a ton other
Here are the results of that.
https://imgur.com/a/iVwwS
Help me guys please. :crying:
A little progress, I was unable to unlock_critical but its still hanging here
https://imgur.com/a/IdZum
jAm-0 said:
I think I messed up my PH-1 something royally.
All I was trying to do is unlock my bootloader and load Magisk.
To preface this, my PH-1 seemed to act a little wonky from the get-go. I bought it 3rd person from a guy on craigslist so anything warranty involved I think I'm out of luck.
The phone would take a while to power on, it took something like 10secs on the power button just to turn it on. And if I set it to reboot , it boots into the bootloader. Also, I was never able to access the recovery (even using power + up). It always felt like I had to hold the buttons for way to long to get to its destination; e.g. up and power to get into fastboot.
Ok where I'm at now. In can occasionally get into fastboot mostly after it bootlooping a few times. It won't get past the Essential logo if I try to boot it up.
PS I was able to unlock the bootloader.
Steps I took to remedy this:
> erase all user data in fastboot
> hold power + u + d to hard power off
> follow this guide https://forum.xda-developers.com/essential-phone/how-to/guide-rooting-essential-ph-1-magisk-t3701976
> attempt to install stock system image via flash-all
>a ton other
Here are the results of that.
https://imgur.com/a/iVwwS
Help me guys please. :crying:
Click to expand...
Click to collapse
read through this and follow the steps should be good to go.
https://forum.xda-developers.com/essential-phone/development/stock-7-1-1-nmj20d-t3701681
This is also very helpful
https://mata.readthedocs.io/en/latest/
That's the exact process I was going through, and it finally booted up.
The issue I was having was a bad usb connection which wouldn't allow me to unlock_critical.
SOLVED. Still no Magisk, we'll worry about that another time. 5hrs of troubleshooting is enough for one night.
https://imgur.com/a/ZiBzp
SO close to getting Magisk to install, any reason the refuses to flash the boot partition? I used the stock boot.img and had Magisk patch it before I flashed
SO close to getting Magisk to install, any reason the refuses to flash the boot partition? I used the stock boot.img and had Magisk patch it before I flashed
jAm-0 said:
SO close to getting Magisk to install, any reason the refuses to flash the boot partition? I used the stock boot.img and had Magisk patch it before I flashed
Click to expand...
Click to collapse
You have to flash magisk in twrp recovery NOT bootloader mode.
It's right in the OP from the rooting guide you followed:
Do not set up a password if you are on 8.1 twrp doesn't work.
You need to read through that rooting guide and make sure you know what you're doing before you try.
This phone is easy to hard brick and there is no solution to recover from that.
OREO 8.0/8.1
REQUIREMENTS:
An unlocked bootloader.
A working ADB/Fastboot environment on your computer. Knowledge on how ADB and Fastboot works is also preferred.
The stock boot image for whatever build you're running/trying to root.
The latest TWRP build for our device.
If on 8.1, remove your pin/pattern/passcode until the root process is done.
1. Download both the stock boot image for whatever build you're running and the Magisk or SuperSU zip. Transfer both files to your device's internal storage.
2. Reboot your phone into the bootloader, then open up your command prompt or terminal and flash the latest TWRP build for the device using:
Code:
fastboot flash boot twrp.img
3. Once TWRP has finished flashing, reboot into your recovery. When prompted, enter your pattern/passcode/password to decrypt your data in order to gain access to your internal storage.
4. Once you're in TWRP, install the stock boot image and then the Magisk/SuperSU zip.
5. Whenever Magisk/SuperSU finishes installing, simply reboot your device! You should now be rooted.
*NOTE: TWRP will NOT remain installed on your device.
wolfu11 said:
You have to flash magisk in twrp recovery NOT bootloader mode.
It's right in the OP from the rooting guide you followed:
Do not set up a password if you are on 8.1 twrp doesn't work.
You need to read through that rooting guide and make sure you know what you're doing before you try.
This phone is easy to hard brick and there is no solution to recover from that.
OREO 8.0/8.1
REQUIREMENTS:
An unlocked bootloader.
A working ADB/Fastboot environment on your computer. Knowledge on how ADB and Fastboot works is also preferred.
The stock boot image for whatever build you're running/trying to root.
The latest TWRP build for our device.
If on 8.1, remove your pin/pattern/passcode until the root process is done.
1. Download both the stock boot image for whatever build you're running and the Magisk or SuperSU zip. Transfer both files to your device's internal storage.
2. Reboot your phone into the bootloader, then open up your command prompt or terminal and flash the latest TWRP build for the device using:
Code:
fastboot flash boot twrp.img
3. Once TWRP has finished flashing, reboot into your recovery. When prompted, enter your pattern/passcode/password to decrypt your data in order to gain access to your internal storage.
4. Once you're in TWRP, install the stock boot image and then the Magisk/SuperSU zip.
5. Whenever Magisk/SuperSU finishes installing, simply reboot your device! You should now be rooted.
*NOTE: TWRP will NOT remain installed on your device.
Click to expand...
Click to collapse
I realize all that, the issue is I cannot access any sort of recovery because I think my bootloader is defective.
For example from a cold restart if I press the power button for say 3 -5 seconds it wont boot, just boot to the Essential logo and loop. To get the phone to boot I have to hold the power down for 15-20 seconds while it bootloops a couple times then it'll boot.
Is there a possible way to reflash the bootloader software if it is defective? It's unlocked btw
There is a way to install magisk via fastboot with a patched_boot img which I'm working on. Cant seem to find the right boot img to patch for 8.1
PS Is it possible to flash .zips through fastboot? e.g. custom roms etc
Was finally able to get into recovery, so all is well. Thanks for the help yall
OP, what was your process to successfully get into recovery and fix your problems?
It may help others sometime?
gimpy1 said:
OP, what was your process to successfully get into recovery and fix your problems?
It may help others sometime?
Click to expand...
Click to collapse
It's really hard to say, my phone has a serious problem with it. sometimes I cant get it to boot, it will boot into the bootloader over and over and over. I've managed to get Lineage 15.1 on if for a bit until I tried to get back into the recovery which sent it manic.
I just got lucky I was able to get into TWRP and flash lineage.
my first issue not being able to flash the stock image via fastboot because I didn't unlock_critical which can sometimes fail when the usb connection is bad.
Currently flashing stock again if my phone will boot up. I'm not sure whats wrong with my bootloader but its causing a ton of havoc
My essential phone stuck in boot logo,bootloader work but recovery doesn´t work
Bootloader locked.
Oem unlocking disable.
Usb debugging disable.
How to flash stock recovery or twrp on bootloader locked ? please
Thank you!
katastyle971 said:
My essential phone stuck in boot logo,bootloader work but recovery doesn´t work
Bootloader locked.
Oem unlocking disable.
Usb debugging disable.
How to flash stock recovery or twrp on bootloader locked ? please
Thank you!
Click to expand...
Click to collapse
Same boat for me - just keep rebooting to show Powered by Android Screen and then reboot again and again. Was able to see my device using fastboot devices command but all attempts to access recory just repeat the bootloop entry. I would happily check the OEM UNLOCK option in dev settings but can't even get it to book to any OS to make that option happen. Still shows bootloader locked on bootloader screen - any help someone can suggest?
I had this problem tonight also. In my case I suspect it had to do with the install of magisk in which I checked both boxes and patched the bootloader. on reboot I was stuck on boot. Just wanted to add my solution. I got the pie back to stock zip here https://forum.xda-developers.com/essential-phone/development/stock-7-1-1-nmj20d-t3701681 then I put it into the adb folder and ran the flashall.bat script. I tried the no wipe one and it saved my information. very happy I didnt have to resetup my phone in the end.
katastyle971 said:
My essential phone stuck in boot logo,bootloader work but recovery doesn´t work
Bootloader locked.
Oem unlocking disable.
Usb debugging disable.
How to flash stock recovery or twrp on bootloader locked ? please
Thank you!
Click to expand...
Click to collapse
I am in the same boat. I tried to re-install the OS, but because my USB debugging was not enabled, Fastboot worked but ADB would not and since I basically wiped the recovery area, my phone will only boot into Fastboot but will not allow any loading of recovery. I would pay for someone to help. This is so hard to figure out. I have contacted Essential but since my phone is over 12 months old, the warranty has expired.
Help please. It seems like such a waste to have a bricked phone.
I need help! Here’s the story. Sorry for the lengthy post. TL;DR at the bottom..
- Was on B32, unlocked BL, TWRP installed, rooted with SuperSU
- Updated to B35, but lost TWRP and root (I don’t know how, but I assume I must have wiped the wrong things? - system? - I’m clearly a novice)
- Now I’m on B35 with an unlocked BL, but despite days of searching and researching, I can’t for the life of me figure out how to get TWRP reinstalled. I want to have TWRP before trying Magisk (have never used Magisk before, but would like to try it this time instead of SuperSU)
- From my Mac, using terminal, adb recognizes my devices.
- “adb reboot boot loader” gets me to a list of options “power off, restart, recovery, fastboot, back to previous page”. Choosing fastboot simply restarts the phone. What should “fastboot mode” look like?
- I tried flashing TWRP via adb while on this page and terminal stopped at “waiting for any device” and did nothing
My conclusion is that I need to downgrade to whatever latest version allows fastboot commands to work properly? Is this B15? If so, is the only available B15 zip the one that is on the ZTE website? Do I just wipe data/dalvick/cache and flash this zip?
Do I not need a Bootstock and Systemstock like @DrakenFX usually posts? That’s how I’m used to doing any updates.
Thank you all for your help, both past and present!
TL;DR: Would like to downgrade from B35 to B15 so that I can install twrp and root again. What’s the best way to do this and where can I find the appropriate files?
alajoy said:
I need help! Here’s the story. Sorry for the lengthy post. TL;DR at the bottom..
- Was on B32, unlocked BL, TWRP installed, rooted with SuperSU
- Updated to B35, but lost TWRP and root (I don’t know how, but I assume I must have wiped the wrong things? - system? - I’m clearly a novice)
- Now I’m on B35 with an unlocked BL, but despite days of searching and researching, I can’t for the life of me figure out how to get TWRP reinstalled. I want to have TWRP before trying Magisk (have never used Magisk before, but would like to try it this time instead of SuperSU)
- From my Mac, using terminal, adb recognizes my devices.
- “adb reboot boot loader” gets me to a list of options “power off, restart, recovery, fastboot, back to previous page”. Choosing fastboot simply restarts the phone. What should “fastboot mode” look like?
- I tried flashing TWRP via adb while on this page and terminal stopped at “waiting for any device” and did nothing
My conclusion is that I need to downgrade to whatever latest version allows fastboot commands to work properly? Is this B15? If so, is the only available B15 zip the one that is on the ZTE website? Do I just wipe data/dalvick/cache and flash this zip?
Do I not need a Bootstock and Systemstock like @DrakenFX usually posts? That’s how I’m used to doing any updates.
Thank you all for your help, both past and present!
TL;DR: Would like to downgrade from B35 to B15 so that I can install twrp and root again. What’s the best way to do this and where can I find the appropriate files?
Click to expand...
Click to collapse
I'm not sure where you read all that BS, but if your bootloader is unlocked then you can install TWRP via EDL (Or fastboot if you have it). No need to downgrade for anything :laugh: in the past you would have needed to downgrade in order to unlock the bootloader, now it's not even needed
Download EDL Tool by djkuz and install TWRP with that one. Or you can use axon7tool by tennear, but it's much more finicky and ran entirely by commands (no UI).
And just to avoid more trouble, DO NOT LOCK THE BOOTLOADER! You do that with the system even barely modified and you brick the phone. A bunch of people tried to do something, got scared because they made a simple correctable mistake and just locked the bootloader thinking everything would get restored to stock - doesn't work that way.
Not saying you will do this, but I've seen about 4 or 5 people that started just like you and ended up doing that
Choose an username... said:
I'm not sure where you read all that BS, but if your bootloader is unlocked then you can install TWRP via EDL (Or fastboot if you have it). No need to downgrade for anything :laugh: in the past you would have needed to downgrade in order to unlock the bootloader, now it's not even needed
Download EDL Tool by djkuz and install TWRP with that one. Or you can use axon7tool by tennear, but it's much more finicky and ran entirely by commands (no UI).
And just to avoid more trouble, DO NOT LOCK THE BOOTLOADER! You do that with the system even barely modified and you brick the phone. A bunch of people tried to do something, got scared because they made a simple correctable mistake and just locked the bootloader thinking everything would get restored to stock - doesn't work that way.
Not saying you will do this, but I've seen about 4 or 5 people that started just like you and ended up doing that
Click to expand...
Click to collapse
Wow, thanks so much for responding to this. Sounds like this should be easy! A couple of questions before I go about following your advice:
1). Do I download EDL Tool to my computer or phone??
2). If I'm downloading it to my computer, does it matter that I'm using a mac?
Thanks again for your help!
alajoy said:
Wow, thanks so much for responding to this. Sounds like this should be easy! A couple of questions before I go about following your advice:
1). Do I download EDL Tool to my computer or phone??
2). If I'm downloading it to my computer, does it matter that I'm using a mac?
Thanks again for your help!
Click to expand...
Click to collapse
Oh, skipped that part. EDL Tool is a .bat. I'm pretty sure you won't be able to run it on a Mac. If you can find a Windows PC somewhere to do this, it'd be much better...
But there's another way.
Issuing "adb reboot bootloader" effectively sends you into fastboot. That list you mentioned is fastboot (if it says "Start" in green, and you can scroll that, it is fastboot). Just use fastboot from the pc: Put TWRP on the fastboot folder on the PC, then issue "fastboot flash recovery twrp.img" with "twrp.img" being whatever the twrp file name is. After that issue "fastboot reboot recovery". And as soon as you are on TWRP, DON'T GET OUT OF IT. Just wipe data, system, caches; then flash a system (e.g. b10 bootstack and stocksystem), then also flash Magisk, and THEN boot to system
Choose an username... said:
Oh, skipped that part. EDL Tool is a .bat. I'm pretty sure you won't be able to run it on a Mac. If you can find a Windows PC somewhere to do this, it'd be much better...
But there's another way.
Issuing "adb reboot bootloader" effectively sends you into fastboot. That list you mentioned is fastboot (if it says "Start" in green, and you can scroll that, it is fastboot). Just use fastboot from the pc: Put TWRP on the fastboot folder on the PC, then issue "fastboot flash recovery twrp.img" with "twrp.img" being whatever the twrp file name is. After that issue "fastboot reboot recovery". And as soon as you are on TWRP, DON'T GET OUT OF IT. Just wipe data, system, caches; then flash a system (e.g. b10 bootstack and stocksystem), then also flash Magisk, and THEN boot to system
Click to expand...
Click to collapse
"adb reboot bootloader" takes me to the start up screen that says "your device software cannot be checked for corruption..." etc. and gives you 5 sec to either press up or down on volume keys to get to list: “power off, restart, recovery, fastboot, back to previous page”, but the list is all white. If I select "fastboot" it reboots the phone and starts that cycle over again at the "your device software cannot be checked for corruption..." etc page.
Nowhere am I given a chance to use fastboot commands. I'm never on the page with the green "Start".
..This all seemed a lot simpler on my Nexus 5..
Thanks for your help/patience.
alajoy said:
"adb reboot bootloader" takes me to the start up screen that says "your device software cannot be checked for corruption..." etc. and gives you 5 sec to either press up or down on volume keys to get to list: “power off, restart, recovery, fastboot, back to previous page”, but the list is all white. If I select "fastboot" it reboots the phone and starts that cycle over again at the "your device software cannot be checked for corruption..." etc page.
Nowhere am I given a chance to use fastboot commands. I'm never on the page with the green "Start".
..This all seemed a lot simpler on my Nexus 5..
Thanks for your help/patience.
Click to expand...
Click to collapse
I thought you had fastboot since you described the 5 seconds screen and both are very similar. It's normal not to have it though.
I think there's some version of axon7tool for Linux but I'm not sure at all. The best way would be to find a Windows computer.
I wonder how you actually installed TWRP the first time? Via fastboot?
As soon as you get TWRP you should be able to run a few commands to get fastboot back just to have it around.
Choose an username... said:
I thought you had fastboot since you described the 5 seconds screen and both are very similar. It's normal not to have it though.
I think there's some version of axon7tool for Linux but I'm not sure at all. The best way would be to find a Windows computer.
I wonder how you actually installed TWRP the first time? Via fastboot?
As soon as you get TWRP you should be able to run a few commands to get fastboot back just to have it around.
Click to expand...
Click to collapse
I have adb and fastboot installed on my Mac and I can't remember how I got it working on my phone in the first place, but I've only ever used a Mac for all this. Terminal recognizes my device and responds to commands until I try "fastboot flash recovery twrp.img" then it says "<waiting for any device>" and does nothing.
Thanks again for the help. I'll keep hunting though. I don't have access to any Windows computer.
Cheers