Related
Attempted to flash Liquid Jelly Bean, then got stuck on the animation boot screen. I've tried Root tool kit for unbricking and setting it back to stock. Tell me it's successful but stays stuck on the animation screen.
I've also tried to unbrick manually however even though I have the correct files placed in my Platform Tools folder of Android SDK ... I constantly get stuck at the CMD prompt steps. Any time I type in "ADB reboot loader" or ..."fastboot flash bootloader bootloader-grouper-3.34.img" or anything similar I get the error message in CMD saying "___ Is not recognized as an internal or external command"
I'm not sure what to do. The bootloader does say that my device is locked, I just can't get passed the splash screen!
Rovon said:
Attempted to flash Liquid Jelly Bean, then got stuck on the animation boot screen. I've tried Root tool kit for unbricking and setting it back to stock. Tell me it's successful but stays stuck on the animation screen.
I've also tried to unbrick manually however even though I have the correct files placed in my Platform Tools folder of Android SDK ... I constantly get stuck at the CMD prompt steps. Any time I type in "fastboot flash bootloader bootloader-grouper-3.34.img" or anything similar I get the error message in CMD saying "___ Is not recognized as an internal or external command"
I'm not sure what to do. The bootloader does say that my device is locked, I just can't get passed the splash screen!
Click to expand...
Click to collapse
Use Wugfresh's toolkit and press "return to stock"
rohan32 said:
Use Wugfresh's toolkit and press "return to stock"
Click to expand...
Click to collapse
"I've tried Root tool kit for unbricking and setting it back to stock. Tell me it's successful but stays stuck on the animation screen. "
Here's an update:
I think I've made it worse ...
Nothing will boot now and it's currently locked. Any time I hit "Start" it says "Booting Failed"
My CMD now says; Error: Cannot Load "Bootloader Grouper-3.34.img"
I'm seriously lost. I've been working on this for about 6 hours now ....
Can you get into bootloader and then recovery by holding the power and volume down buttons? Was ADB actually working before all of this??
markj338 said:
Can you get into bootloader and then recovery by holding the power and volume down buttons? Was ADB actually working before all of this??
Click to expand...
Click to collapse
Nope. Nothing is allowing me to get into recovery. At first it was just stuck on the google screen now it says "boot failed"
Rovon said:
Nope. Nothing is allowing me to get into recovery. At first it was just stuck on the google screen now it says "boot failed"
Click to expand...
Click to collapse
Where does it say boot failed? On the device?
markj338 said:
Where does it say boot failed? On the device?
Click to expand...
Click to collapse
Yes. Top left hand corner.
Rovon said:
Yes. Top left hand corner.
Click to expand...
Click to collapse
I know I have asked this before but I don't know if I was clear
You can't go to bootloader, and press the volume buttons to go to recovery?
markj338 said:
I know I have asked this before but I don't know if I was clear
You can't go to bootloader, and press the volume buttons to go to recovery?
Click to expand...
Click to collapse
No I can't get into the recovery at all. When I turn on the device I don't even need to use the rocker keys to get into bootloader either. Actually my bootloader is a bit different now too. I have the 'Google' logo and at the top the regular options for Start, Recovery, Power Off, etc.
In simple terms: I can't even get to the animated splash screen anymore
Open the command prompt IN the directly WITH fastboot
Fastboot oem unlock
Then wipe / flash factory images. Fastboot -w update image whatever the image name is.
Then uninstall / delete that stupid toolkit and never use them stupid craps again.
Are you still able to communicate with the device via fastboot? If you issue the command 'fastboot devices' does it return a serial number?
Edit: I'm going to bed so if you are able to use fastboot, download the factory image pack from https://dl.google.com/dl/android/aosp/nakasi-jro03d-factory-e102ba72.tgz
Extract the archive. Inside are there will be an install script, manually issue the commands contained in the script in fastboot. The only thing you need to add is the location of the .img and .zip files from the archive you extracted e.g. 'fastboot flash recovery c:/Users/name/desktop/recovery.IMG'
There is no reason this will not get you up and running again.
Sent from my Nexus 7 using xda app-developers app
Alkaloid said:
Are you still able to communicate with the device via fastboot? If you issue the command 'fastboot devices' does it return a serial number?
Edit: I'm going to bed so if you are able to use fastboot, download the factory image pack from https://dl.google.com/dl/android/aosp/nakasi-jro03d-factory-e102ba72.tgz
Extract the archive. Inside are there will be an install script, manually issue the commands contained in the script in fastboot. The only thing you need to add is the location of the .img and .zip files from the archive you extracted e.g. 'fastboot flash recovery c:/Users/name/desktop/recovery.IMG'
There is no reason this will not get you up and running again.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Thanks for your response.
I've followed the instructions in the file. From previous research, I've had these files. My device does communicate with Fastboot. When I give the command for Devices it gives me my serial. Also, when I ask it to reboot-bootloader in CMD it does.
My issue is when I get to "Fastboot flash bootloader-grouper-3.34.img". CMD states "Error: Cannot load bootloader-grouper-3.34.img"
I've followed the commands previous to that. (Erase boot, cache, recovery, system, userdata)
Open the command prompt IN the directly WITH fastboot
Fastboot oem unlock
Then wipe / flash factory images. Fastboot -w update image whatever the image name is.
Then uninstall / delete that stupid toolkit and never use them stupid craps again.
Click to expand...
Click to collapse
Yes my device is unlocked again, but I still can't get into recovery mode. It just tells me "Recovery Failed" in small text in the upper left hand corner of my N7.
UPDATE:
After unlocking the device again. I used the Nexus Root Toolkit to restore to factory settings and it worked
The Problem: My device was no responding correctly to the toolkit when locked.
Cheers for the help. I'll attempt to root again, hopefully no problems this time If there are I'll be sure to post again!
Thanks to everyone that replied.
Rovon said:
UPDATE:
After unlocking the device again. I used the Nexus Root Toolkit to restore to factory settings and it worked
The Problem: My device was no responding correctly to the toolkit when locked.
Cheers for the help. I'll attempt to root again, hopefully no problems this time If there are I'll be sure to post again!
Thanks to everyone that replied.
Click to expand...
Click to collapse
For the love of God..stop using the toolkit from here on out.. learn how to use ADB and Fastboot so you can avoid these issues.
Sent from my Galaxy Nexus using Tapatalk 2
So you erased the recovery then wonder why you could not boot into recovery....
You flashed or tried to flash the bootloader. You already had the same bootloader installed and there was no need to do so to try and fix your issue.
You still don't know what you're doing and are back using the tool that lead you to this issues. A toolkit. Learn what you're doing and you wont face this type of silly issue again.
Rovon said:
UPDATE:
After unlocking the device again. I used the Nexus Root Toolkit to restore to factory settings and it worked
The Problem: My device was no responding correctly to the toolkit when locked.
Cheers for the help. I'll attempt to root again, hopefully no problems this time If there are I'll be sure to post again!
Thanks to everyone that replied.
Click to expand...
Click to collapse
I think you should reread this post and hit the thanks button of everyone who took the time to help you out of this mess - its good manners. Oh, and learn how to use adb & fastboot
Sent from my Nexus 7 using xda premium
Inaccessible boot loader :/
If you try to fastboot flash all you get nothing?
Sent from my Nexus 7 using xda app-developers app
---------
nvm you fixed it, good job
Don't use toolkits. Most people don't have a clue what the toolkit is actually doing so if something goes wrong they aren't in a good position
Its always nice to see threads like these where the N7 in the face of death but in the end with cutting edge medical technology it is brought back to life and healthy.
Hello Everyone. I need some help with restoring my shield because I seem to have soft-bricked it. Last week I rooted and installed a custom recovery file and all was well but this past weekend I was messing around with it trying to install the custom rom for full android and I think I accidentally deleted the boot file and the recovery file because all I get is the android on his back with the red triangle. Also, when I try to connect to the unit using fastboot nothing is found but I DO get a hit if I put the unit in stock recovery, it gives me the option to click apply update from adb.
From what I have been reading it sounds like I should be able to sideload the recovery and/or the stock firmware. Can anyone confirm or provide me with instructions on how to get this unit back up and running.
Any help is greatly appreciated
Wow I expected people to jump on this one. I guess I'll just keep messing around with it
Hy, here is the firmware and the instructions:
FW:
https://developer.nvidia.com/gameworksdownload (here you will have to scroll down to your console version PRO/non-PRO
Instructions:
http://developer.download.nvidia.co...TV/Upgrade-2.1/HowTo-Flash-Recovery-Image.txt
Thanks but I already looked at those and it only provides details for using fastboot which I am unable to use.. device will only show up when I use the regular recovery method and the only option is apply update from adb.
So, if you perform a adb reboot bootloader command from adb it doesn't reboot into the bootloader?
hpric said:
Thanks but I already looked at those and it only provides details for using fastboot which I am unable to use.. device will only show up when I use the regular recovery method and the only option is apply update from adb.
Click to expand...
Click to collapse
And you have tried restoring boot from stock recovery download ? with 'fastboot flash boot boot.img' ?
gffmac said:
And you have tried restoring boot from stock recovery download ? with 'fastboot flash boot boot.img' ?
Click to expand...
Click to collapse
He can only do this if he can adb into the bootloader, hence my question. The implication appears to be that he can't if I'm reading his comments correctly.
Beefheart said:
So, if you perform a adb reboot bootloader command from adb it doesn't reboot into the bootloader?
Click to expand...
Click to collapse
Correct. I can only use sideload at this time. Yesterday I was messing around with it a little more trying to sideload the recovery but I kept getting a message saying "The footer was incorrect" and it would cancel the install. I tried different files to make sure I wasn't dealing with a corrupted zip file but they all gave the same message.
I'm trying to figure out how to sideload the recovery
Beefheart said:
He can only do this if he can adb into the bootloader, hence my question. The implication appears to be that he can't if I'm reading his comments correctly.
Click to expand...
Click to collapse
Correct
Hello, I am facing the exact issue. Please let me know if you figured a way to debrick?
All I can do is ADB sideload and E:footer error keeps coming up.
Help is appricated,
Thanks
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!
A2017U, my second Android phone (previously had a OnePlus One, which I rooted). I have a Mac, so all the Windows and Linux tools for the Axon 7 have failed me, even with Windows in a virtual machine.
Followed these instructions and got to the point of fastboot oem unlock -> B20 again. Still not rooted. No OTA available.
Then I saw this thread but can't figure out how to flash TWRP to replace the stock recovery.
I've spent a whole day on this effort, including hours following links through threads to find files, and still no root. Can anyone please explain what to do next, in simple terms and with direct links to files?
nuserame said:
A2017U, my second Android phone (previously had a OnePlus One, which I rooted). I have a Mac, so all the Windows and Linux tools for the Axon 7 have failed me, even with Windows in a virtual machine.
Followed these instructions and got to the point of fastboot oem unlock -> B20 again. Still not rooted. No OTA available.
Then I saw this thread but can't figure out how to flash TWRP to replace the stock recovery.
I've spent a whole day on this effort, including hours following links through threads to find files, and still no root. Can anyone please explain what to do next, in simple terms and with direct links to files?
Click to expand...
Click to collapse
Replied to you in the original thread.
If you already did "fastboot oem unlock", then your bootloader is unlocked.
Download TWRP, put it into the folder that your Minimal ADB & Fastboot is located in, and then do "fastboot flash recovery whatever-the-TWRP-filename-is.img". In TWRP, flash SuperSU 2.65 to root, or if you're trying to update to B29, flash DrakenFX's B29 SuperStack and System, then SuperSU 2.65.
xtermmin said:
Replied to you in the original thread.
If you already did "fastboot oem unlock", then your bootloader is unlocked.
Download TWRP, put it into the folder that your Minimal ADB & Fastboot is located in, and then do "fastboot flash recovery whatever-the-TWRP-filename-is.img". In TWRP, flash SuperSU 2.65 to root, or if you're trying to update to B29, flash DrakenFX's B29 SuperStack and System, then SuperSU 2.65.
Click to expand...
Click to collapse
Thank you, thank you!!!
I did this, and the phone is rooted on B29!
But one strange thing: On every reboot I get a weird boot menu with a message warning me "Your device is unlocker and cann't be trusted"
and boot will proceed in 5 seconds.
Is that normal? Is there any way to get rid of that?
nuserame said:
Thank you, thank you!!!
I did this, and the phone is rooted on B29!
But one strange thing: On every reboot I get a weird boot menu with a message warning me "Your device is unlocker and cann't be trusted"
and boot will proceed in 5 seconds.
Is that normal? Is there any way to get rid of that?
Click to expand...
Click to collapse
Normal. If you press a volume button during that screen you can choose what you want to boot to (system, recovery, fastboot). Don't know how to get rid of it.
xtermmin said:
Normal. If you press a volume button during that screen you can choose what you want to boot to (system, recovery, fastboot). Don't know how to get rid of it.
Click to expand...
Click to collapse
Looks like the same message, complete with the same spelling mistakes, happens on the OnePlus 3. I wonder who's copying who.
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