Related
Hello,
Just trying to get my head around Fastbooting, I found a really concise guide about how to hook everything up however I'm puzzled as to the following:
- What is Superuser.zip and is it needed for Fastbooting?
- Some tutorials seem to say download a Fastboot tool from HTC - but there is already a fastboot.exe supplied with the Android 1.5 SDK in the tools folder. Is a default one not to be used?
Thanks!
Temjin said:
Hello,
Just trying to get my head around Fastbooting, I found a really concise guide about how to hook everything up however I'm puzzled as to the following:
- What is Superuser.zip and is it needed for Fastbooting?
- Some tutorials seem to say download a Fastboot tool from HTC - but there is already a fastboot.exe supplied with the Android 1.5 SDK in the tools folder. Is a default one not to be used?
Thanks!
Click to expand...
Click to collapse
Maybe you are able to tell us what you want to do with youre phone?! If you just won't to flash roms i.e. the Modaco just follow the guide as he provided us with. All you need is the SDK for that.
Or follow this guide. From that recovery you are able to partion youre sd-card as described, and do a wipe and then flash the Modaco-rom. I highly recommend that one.
Heppieboeddah said:
Maybe you are able to tell us what you want to do with youre phone?! If you just won't to flash roms i.e. the Modaco just follow the guide as he provided us with. All you need is the SDK for that.
Or follow this guide. From that recovery you are able to partion youre sd-card as described, and do a wipe and then flash the Modaco-rom. I highly recommend that one.
Click to expand...
Click to collapse
Hi Heppieboeddah,
Currently I'm not looking to Flash the phone, right now I want to be able to generate a backup image using RA-HERO-v1.2.2 but via only fastbooting it (i.e. I don't want to make *any* changes to the phone before the backup is made.)
RA-HERO-v1.2.2 obviously can be done by Fastbooting as the command "fastboot boot Recovery-RA-HERO-v1.2.2.img" is supplied however I am still not 100% on the actuall process of setup to get to that point - and I can't find a real newbie guide for it. I have the SDK on my pc and HTC Sync is installed however the most concise guide (which is for a different rom but none the less uses Fastboot) says that additional files SuperUser.zip and Fastboot should be downloaded - I don't know if that is required in my case. (The guide I'm using for ref is: http://forum.xda-developers.com/archive/index.php/t-552793.html)
Anyway, once I have this backup only then will I look into Flashing a new permanent recovery and then the 2.2 MoDoCa rom.
Thanks!
Temjin said:
Hi Heppieboeddah,
Currently I'm not looking to Flash the phone, right now I want to be able to generate a backup image using RA-HERO-v1.2.2 but via only fastbooting it (i.e. I don't want to make *any* changes to the phone before the backup is made.)
RA-HERO-v1.2.2 obviously can be done by Fastbooting as the command "fastboot boot Recovery-RA-HERO-v1.2.2.img" is supplied however I am still not 100% on the actuall process of setup to get to that point - and I can't find a real newbie guide for it. I have the SDK on my pc and HTC Sync is installed however the most concise guide (which is for a different rom but none the less uses Fastboot) says that additional files SuperUser.zip and Fastboot should be downloaded - I don't know if that is required in my case. (The guide I'm using for ref is: http://forum.xda-developers.com/archive/index.php/t-552793.html)
Anyway, once I have this backup only then will I look into Flashing a new permanent recovery and then the 2.2 MoDoCa rom.
Thanks!
Click to expand...
Click to collapse
Problem solved! Used this *VERY* helpful guide by Dayzee (http://forum.xda-developers.com/showpost.php?p=4257045) to learn how to fastboot, just replacing details of the img file name and managed to fastboot RA-HERO-v1.2.2 and create a back-up.
Gotta be careful, one step at a time!
Now onto flashing!
Temjin said:
RA-HERO-v1.2.2 obviously can be done by Fastbooting as the command "fastboot boot Recovery-RA-HERO-v1.2.2.img" is supplied however I am still not 100% on the actual process of setup to get to that point - and I can't find a real newbie guide for it.
Click to expand...
Click to collapse
Try this. Copy the recovery image to the SDK /tools folder, and follow the simple instructions. Replace CM-HERO-RECOVERY.img with Recovery-RA-HERO-v1.2.2.img obviously, but the procedure is the same otherwise.
Shluggity said:
Try this. Copy the recovery image to the SDK /tools folder, and follow the simple instructions. Replace CM-HERO-RECOVERY.img with Recovery-RA-HERO-v1.2.2.img obviously, but the procedure is the same otherwise.
Click to expand...
Click to collapse
Yep - I basically just did that, see above
Thanks!
Since I haven't seen a linux based all in one tutorial for SBF_flash to rooting I figured I'd write up a quick one. I apologize if there is another thread and I haven't looked hard enough.
First things first: SBF_Flash
Download the latest stock OTA update for your phone - http://forum.xda-developers.com/showthread.php?t=1437177 (This is the latest update. No other updates will be necessary.)
Download the sbf_flash file - http://www.mediafire.com/?oxoe35bsxtnom69
Unzip both to somewhere easy to manage. (I have them in Documents)
Connect your phone to the computer via USB and turn the phone off.
Now you'll need to boot your phone into the boot loader. To do this you simply hold the up arrow on the keyboard while turning the phone on. This should get you into an all black screen with white text.
Open up the terminal and navigate to folder in which you have unzipped your files.
Type
Code:
./sbf_flash VRZ_A956_4.5.608_1FF_01.sbf
You may need to type sudo in order to make it work. (I.E.
Code:
sudo ./sbf_flash VRZ_A956_4.5.608_1FF_01.sbf
)
That should take between 10-20 minutes to go through fully. Once the process is done and the phone reboots go through the setup process and make sure that everything works right.
ROOTING:
Once you have finished the SBF process you'll probably be pretty happy to have a functional phone. But wait! SUPAH FUNCTIONAL ROOT TIME!!
Download the droid 3 root file. - http://www.mediafire.com/?11k7i927o4sd47g
Unzip it to a easily finable folder.
Make sure that your phone has USB debugging enabled. To do so go to settings->application->check box for usb debugging (that might be off, I'm running a custom rom and can't remember if that's the exact path lol)
Connect your phone to your computer and make sure the charge mode is to PC mode.
Go to the folder in which you've unzipped the root tool folder. Double click the run_to_root_your_ droid3.sh file and click run in terminal. Do as it says and make sure the phone is unlocked. Everytime the phone reboots unlock it again until the script is finished running. It will close automatically.
Once this is done you should be able to look in your app drawer and see super user. If this is the case then WHOOOOOO.
PREPARING TO FLASH A CUSTOM ROM:
So, you're rooted. Cool. You want to flash a new ROM. COOLER! Let's do it.
Go to the android market and search for ROM Manager. Download and install it.
Run the app and THE FIRST THING YOU DO is click the flash clockwork mod recovery button. It's best to do this on WiFi. When the window asking for your phone model pops up click the one that you own. (In this case Droid 2 Global.) Wait for it to finish, it will tell you in a happy little message.
Once that is done Clockwork Mod recovery is oficially flashed. Next thing is next.
Go to the android market and purchase Droid 2 Recovery Bootstrap. It's only $2.99 american.
Download and install it. Run it and click Bootstrap Recovery.
It will tell you if it was a success or not.
If it was then you can click reboot recovery and it will boot you into clockwork mod. Make a backup. Then feel free to flash any ROM you want. When you mess up and brick the phone make sure you come back to this guide on how to do it all over again.
Happy hacking!
IF THIS HAS WORKED FOR YOU BE SURE TO THANK ME FOR PUTTING IN THE TIME TO CREATE THIS THREAD! Thank you =)
CREDITS:
Credits go to everyone who created the files I am linking to. If you are the author of the file then let me know and I will mention you here.
I did not create any of these files. I am just putting them all together in an easy to access tutorial.
I am on rooted Thor with 13.3.2.4, with the Nexus Rom installed via safestrap. I have been reading all the threads on unlocking the bootloader and find all of the steps to be very scary. I would like to wait until there was some kind of "toolkit" for this rather than having to first downgrade and then use python through adb etc which I am somewhat uncomfortable with. Will there ever be such a simpler solution?
The bootloader unlock procedure is a no brainer, can't mess up anything there. Downgrading is a little risky, but you're on 3.2.4, thus you can even use the rollback images for Safestrap, take a look at this thread (page 1 is about 3.2.5/3.2.6 users who can NOT use the downgrade images). I'm afraid it won't get any easier than that.
If you don't want to use Python, just execute the adb commands to get your ID and serial (post them here, or PM me if you don't want anyone to see them), I'll create the .unlock file for you then. Downgrading and (actual) unlocking are tasks you have to do yourself though.
I think I might try it this weekend. Thanks for the help.
Cl4ncy said:
The bootloader unlock procedure is a no brainer, can't mess up anything there. Downgrading is a little risky, but you're on 3.2.4, thus you can even use the rollback images for Safestrap, take a look at this thread (page 1 is about 3.2.5/3.2.6 users who can NOT use the downgrade images). I'm afraid it won't get any easier than that.
If you don't want to use Python, just execute the adb commands to get your ID and serial (post them here, or PM me if you don't want anyone to see them), I'll create the .unlock file for you then. Downgrading and (actual) unlocking are tasks you have to do yourself though.
Click to expand...
Click to collapse
I have successfully downgraded to 13.3.1.0, but I am confused about how to install TWRP. Since I have not enabled wifi and registered, I can't install flashify or cwm, or even install a file explorer apk to access my storage, and I don't know how to get the twrp.img file (which I guess I can only install via adb?) Where do I get the correct twrp.img file? I'm kind of stuck....
kbs24 said:
I have successfully downgraded to 13.3.1.0, but I am confused about how to install TWRP. Since I have not enabled wifi and registered, I can't install flashify or cwm, or even install a file explorer apk to access my storage, and I don't know how to get the twrp.img file (which I guess I can only install via adb?) Where do I get the correct twrp.img file? I'm kind of stuck....
Click to expand...
Click to collapse
I am by no means an expert but I just went through this process myself yesterday and it was relatively simple. Check this thread. It has a number of helpful posts in it, including my questions from yesterday.
The correct TWRP image is here. Just follow the instructions in that thread. It's super simple if you use the minimal adb and fastboot linked by Cl4ncy in the first thread I linked. If you have any other questions I'll do my best to help you.
kbs24 said:
I have successfully downgraded to 13.3.1.0, but I am confused about how to install TWRP. Since I have not enabled wifi and registered, I can't install flashify or cwm, or even install a file explorer apk to access my storage, and I don't know how to get the twrp.img file (which I guess I can only install via adb?) Where do I get the correct twrp.img file? I'm kind of stuck....
Click to expand...
Click to collapse
Sorry for the late reply, @muunkin pointed you in the right direction already.
Be sure to (re-)root 3.1.0 and disable OTA via HDX ToolKit, and enable USB debugging in Fire OS, hope you installed minimal adb and fastboot, then copy the TWRP image for your HDX (Thor = 7", Apollo = 8.9") to the root of the sdcard (which is the directory you'll see in Explorer after connecting the HDX to your PC, i.e. don't open another directory), open a DOS box, change dir to the adb directory (enter cd\adb) and enter the commands mentioned in the TWRP thread. This will flash the TWRP image to the recovery parition.
Do a backup of your Fire OS in TWRP before you flash any custom ROM, and copy it to your PC, also look for the TWRP backup of the stock recovery (I think TWRP does a backup somewhere), and move that to your PC as well.
In case you don't know how to access TWRP: with the HDX powered off, you press and hold volume up, then press and hold the power button, release both when the grey Kindle Fire logo appears on screen. Some ROMs (e.g. CM12) offer the advanced reboot in developer options, this will add options to reboot into recovery, bootloader or a soft (quick) reboot to the power menu.
Cl4ncy said:
Sorry for the late reply, @muunkin pointed you in the right direction already.
Be sure to (re-)root 3.1.0 and disable OTA via HDX ToolKit, and enable USB debugging in Fire OS, hope you installed minimal adb and fastboot, then copy the TWRP image for your HDX (Thor = 7", Apollo = 8.9") to the root of the sdcard (which is the directory you'll see in Explorer after connecting the HDX to your PC, i.e. don't open another directory), open a DOS box, change dir to the adb directory (enter cd\adb) and enter the commands mentioned in the TWRP thread. This will flash the TWRP image to the recovery parition.
Do a backup of your Fire OS in TWRP before you flash any custom ROM, and copy it to your PC, also look for the TWRP backup of the stock recovery (I think TWRP does a backup somewhere), and move that to your PC as well.
In case you don't know how to access TWRP: with the HDX powered off, you press and hold volume up, then press and hold the power button, release both when the grey Kindle Fire logo appears on screen. Some ROMs (e.g. CM12) offer the advanced reboot in developer options, this will add options to reboot into recovery, bootloader or a soft (quick) reboot to the power menu.
Click to expand...
Click to collapse
Thank you both @muunkin and @Cl4ncy for guiding me through this. It is clear now that I have to flash TWRP via adb. Unfortunately I did, however, last night briefly turn on wifi in order to get es file explorer, and very quickly the OS ugraded itself to 13.3.2.3. Then, stupidly, I decided to go back to Nexus rom 2.0.2, which I did by reinstalling safestrap. And, Nexus rom is installed on the Stock Rom slot, and I did NOT backup the 13.3.2.3 stock rom. SO, since I am on Nexus rom, do I understand correctly that I need to begin again by downgrading to 13.3.1.0? Right? (After printing out all of these threads and printing out a lot of it and carefully reading, it looks to me like if I had stayed on stock 13.3.2.3 I would not have had to downgrade.....but too late now anyway.) I do have the minimal adb and fastboot installed, and my device is recognized, so eventually this will work I'm pretty sure. I appreciate the help!
kbs24 said:
Thank you both @muunkin and @Cl4ncy for guiding me through this. It is clear now that I have to flash TWRP via adb. Unfortunately I did, however, last night briefly turn on wifi in order to get es file explorer, and very quickly the OS ugraded itself to 13.3.2.3. Then, stupidly, I decided to go back to Nexus rom 2.0.2, which I did by reinstalling safestrap. And, Nexus rom is installed on the Stock Rom slot, and I did NOT backup the 13.3.2.3 stock rom. SO, since I am on Nexus rom, do I understand correctly that I need to begin again by downgrading to 13.3.1.0? Right? (After printing out all of these threads and printing out a lot of it and carefully reading, it looks to me like if I had stayed on stock 13.3.2.3 I would not have had to downgrade.....but too late now anyway.) I do have the minimal adb and fastboot installed, and my device is recognized, so eventually this will work I'm pretty sure. I appreciate the help!
Click to expand...
Click to collapse
No, 13.3.2.3 is ok for both TWRP and unlocking the bootloader, i.e. no need to flash 3.1.0 again - a firmware below 3.2.4 is enough.
Cl4ncy said:
No, 13.3.2.3 is ok for both TWRP and unlocking the bootloader, i.e. no need to flash 3.1.0 again - a firmware below 3.2.4 is enough.
Click to expand...
Click to collapse
Even if I am not running on the stock rom? I can adb install TWRP while on Nexus rom?
kbs24 said:
Even if I am not running on the stock rom? I can adb install TWRP while on Nexus rom?
Click to expand...
Click to collapse
Hm, I'm not exactly sure about this - @ggow's answer here seems to point out that you really have to do it all over again.
Why did you install Safestrap again anyway? ADB-flashing TWRP and unlocking the bootloader before you install a custom ROM would've been the next steps. Also I told you to create a backup of your stock slot before you flash any custom ROM, didn't I?
Cl4ncy said:
Hm, I'm not exactly sure about this - @ggow's answer here seems to point out that you really have to do it all over again.
Why did you install Safestrap again anyway? ADB-flashing TWRP and unlocking the bootloader before you install a custom ROM would've been the next steps. Also I told you to create a backup of your stock slot before you flash any custom ROM, didn't I?
Click to expand...
Click to collapse
Yes you sure did, and that's why I said "stupidly" about me putting safestrap back and nexus rom. I was overanxious and acted impulsively, not having a recovery installed was freaking me out. Bad habit. About doing the backup, there did not appear to be enough room on the internal storage. Sorry. We'll start over no problem. Again thanks.
kbs24 said:
Yes you sure did, and that's why I said "stupidly" about me putting safestrap back and nexus rom. I was overanxious and acted impulsively, not having a recovery installed was freaking me out. Bad habit. About doing the backup, there did not appear to be enough room on the internal storage. Sorry. We'll start over no problem. Again thanks.
Click to expand...
Click to collapse
I'm also not sure how to do this now. You don't have any Safestrap 3.2.3 Fire OS backup to restore, you shouldn't use the 3.2.4 rollback image, as you're not on 3.2.4, so what do you want to flash to the stock slot now? Or did I miss anything?
Cl4ncy said:
I'm also not sure how to do this now. You don't have any Safestrap 3.2.3 Fire OS backup to restore, you shouldn't use the 3.2.4 rollback image, as you're not on 3.2.4, so what do you want to flash to the stock slot now? Or did I miss anything?
Click to expand...
Click to collapse
I was going to look for a stock 3.2.3 to flash. If can't find, I do have a backup of stock 3.2.4 on the card which I would flash, thus requiring the downgrade.
kbs24 said:
I was going to look for a stock 3.2.3 to flash. If can't find, I do have a backup of stock 3.2.4 on the card which I would flash, thus requiring the downgrade.
Click to expand...
Click to collapse
I haven't seen a 3.2.3 Safestrap flashable Image, good luck. Regarding the 3.2.4 backup I'm not sure whether it works with the 3.2.3 bootloader.
Cl4ncy said:
I haven't seen a 3.2.3 Safestrap flashable Image, good luck. Regarding the 3.2.4 backup I'm not sure whether it works with the 3.2.3 bootloader.
Click to expand...
Click to collapse
Yeah, I am probably screwed. But we'll see. I'm pretty sure I understand what the process should be at least.
kbs24 said:
Yeah, I am probably screwed. But we'll see. I'm pretty sure I understand what the process should be at least.
Click to expand...
Click to collapse
Not sure how far you got with this but you *should* be able to flash TWRP from Nexus provided the version of FireOS was 3.2.3.2 or lower prior to the installation of Safestrap v3. The customized version of twrp leverages a vulnerability in the HDX bootloader that is installed with FireOS. Neither Safestrap nor Nexus mess with the bootloader so the prerequisites should remain intact. I say should as interactions are complex - further complicated by a fussy device with limited recovery capability should something go wrong. To the best of my knowledge no one has attempted a twrp flash from Nexus while Safestrap v3 is installed.
Thoughts:
- grab flashify from the play store or here; make a backup of your current recovery environment (this step will also help to familiarize you with flashify)
- download the HDX customized version of twrp (here); use ES File Explorer to verify MD5
- use flashify to install twrp (can also be done via adb commands as shown in the twrp op)
Options:
- unlock the bootloader before attempting other remedial steps. Unlocking is a frustrating but low/no risk activity that yields substantially improved recovery capabilities once completed. Yep - you can do this without twrp (unlocking before flashing twrp is the recommended path according to several devs - although I prefer the opposite).
[-or-]
- flash 3.1.0 from here to the stock slot and then attempt to remove Safestrap v3. If successful you can proceed with flashing twrp unlocking, etc in the normal manner. As with any flash there is a risk something will go wrong or FireOS will not start up properly. To help mitigate the latter suggest installing a fallback version of Nexus v2 in a secondary slot. Don't forget to remove this slot before uninstalling SS.
The above is only an outline. Give it some thought and post any questions BEFORE taking action. I also suggest you let this post sit for a few days in case some of the rational is fatally flawed. Lots of smart people in the community who will jump in if my guidance is misdirected (which it has been shown to be on occasion). Don't risk a brick by acting too quickly. Proper preparation is essential for a successful outcome.
Sorry for sounding like your mum ... :angel:
Davey126 said:
Not sure how far you got with this but you *should* be able to flash TWRP from Nexus provided the version of FireOS was 3.2.3.2 or lower prior to the installation of Safestrap v3. The customized version of twrp leverages a vulnerability in the HDX bootloader that is installed with FireOS. Neither Safestrap nor Nexus mess with the bootloader so the prerequisites should remain intact. I say should as interactions are complex - further complicated by a fussy device with limited recovery capability should something go wrong. To the best of my knowledge no one has attempted a twrp flash from Nexus while Safestrap v3 is installed.
Thoughts:
- grab flashify from the play store or here; make a backup of your current recovery environment (this step will also help to familiarize you with flashify)
- download the HDX customized version of twrp (here); use ES File Explorer to verify MD5
- use flashify to install twrp (can also be done via adb commands as shown in the twrp op)
Options:
- unlock the bootloader before attempting other remedial steps. Unlocking is a frustrating but low/no risk activity that yields substantially improved recovery capabilities once completed. Yep - you can do this without twrp (unlocking before flashing twrp is the recommended path according to several devs - although I prefer the opposite).
[-or-]
- flash 3.1.0 from here to the stock slot and then attempt to remove Safestrap v3. If successful you can proceed with flashing twrp unlocking, etc in the normal manner. As with any flash there is a risk something will go wrong or FireOS will not start up properly. To help mitigate the latter suggest installing a fallback version of Nexus v2 in a secondary slot. Don't forget to remove this slot before uninstalling SS.
The above is only an outline. Give it some thought and post any questions BEFORE taking action. I also suggest you let this post sit for a few days in case some of the rational is fatally flawed. Lots of smart people in the community who will jump in if my guidance is misdirected (which it has been shown to be on occasion). Don't risk a brick by acting too quickly. Proper preparation is essential for a successful outcome.
Sorry for sounding like your mum ... :angel:
Click to expand...
Click to collapse
Thanks for your input. I am still on the nexus rom, but I am fairly sure that Safestrap was installed while on 13.3.2.4. Is there a way to tell? It is safestrap 3.75, based on twrp 2.7.
I had some time today to work on this, and after looking over the ideas from all of you (thank you very much!) it seemed that my only option is to restore my backup which will get me back to the Nexus 2.0.2 rom. So I did this successfully. Being on Nexus rom, I was then able to use the 13.3.2.4 rollback file to get back to 13.3.0.9. Then ran into trouble......the system update to 13.3.1.0 was not successful. the .bin file was located, but all that happened was a "validating update file" followed by forced reboot. I remain stuck on 13.3.0.9. There are threads discussing editing build.prop but I know I did not have to do this when I first did a rollback a few days ago. Not sure whether to give up or maybe someone has another idea how to get the system to use that .bin file? Should I turn on wifi and wait for an ota or is that too risky, will it jump me all the way up to the most current build? Will it maybe go incrementally?
kbs24 said:
Thanks for your input. I am still on the nexus rom, but I am fairly sure that Safestrap was installed while on 13.3.2.4. Is there a way to tell? It is safestrap 3.75, based on twrp 2.7.
Click to expand...
Click to collapse
(Also as you suggested, I did try flashing the zip 3.1.0 and it did not work, never rebooted successfully. So went back again to 3.0.9.)
kbs24 said:
I had some time today to work on this, and after looking over the ideas from all of you (thank you very much!) it seemed that my only option is to restore my backup which will get me back to the Nexus 2.0.2 rom. So I did this successfully. Being on Nexus rom, I was then able to use the 13.3.2.4 rollback file to get back to 13.3.0.9. Then ran into trouble......the system update to 13.3.1.0 was not successful. the .bin file was located, but all that happened was a "validating update file" followed by forced reboot. I remain stuck on 13.3.0.9. There are threads discussing editing build.prop but I know I did not have to do this when I first did a rollback a few days ago. Not sure whether to give up or maybe someone has another idea how to get the system to use that .bin file? Should I turn on wifi and wait for an ota or is that too risky, will it jump me all the way up to the most current build? Will it maybe go incrementally?
Click to expand...
Click to collapse
Glad you were able to make some progress. I believe you could have flashed twrp from Nexus as I believe you successfully downgraded/upgraded to 13.3.2.3 which would then be the base version when you reininstalled Safestrap. But you found another path which is just fine.
It is possible the 13.3.1.0 is invalid (possibly corrupt). You can use ES File Explorer to validate the MD5 (c49c0363de4d8dfa5c87c1bdb88aa2ba) or download a fresh copy here. You can also upgrade directly to 13.3.2.3 instead of hopscotching through 13.3.1.0 and then applying the 13.2.3.3 bootloader update.
I strongly suggest you NOT connect to WiFi as it is unpredictable if/when you will receive at OTA and what version will be downloaded. Options for getting files onto you device:
- use HDX toolkit to root and block OTA on 13.3.0.9; you can then enable WiFi
- tether your device and drop files into "Internal Storage"
- use 'adb push' to transfer files
You should not need to mess with build.prop as the 3.2.4->3.0.9 rollback should have handed that. It's quite easy to brick your device if you get any of the edits or permissions wrong.
This place has gotten a bit messy with all of the threads out there and it's especially confusing for those who are new to unlocking and rooting. Or, heck, to those who weren't around as the threads were being written and referenced. I've reposted my consolidated step-by-step list half a dozen times so far - and the steps seem to be working for folks - so I'm going to post it here. You're still going to have to visit the original threads, but hopefully this will serve as a clear outline for you.
Maybe we can also try to keep general unlocking and rooting questions ("I don't know where to start, help me!") to this thread to avoid cluttering up the other ones. Reserve questions in those threads for those specifically related to the OP ("I received ABC error after doing XYZ, what does it mean?"). If anyone sees general unlocking or rooting questions in other threads, maybe direct them here as a place to start. Make sense?
A list of FAQs can be found here in the second post.
Many thanks to @tenfar and @DrakenFX (among others with their help and suggestions!) for the tools and files they provided to make all of this happen.
Unlocking and Rooting your Axon 7
This set of steps has worked successfully for multiple folks (including myself) on the US/NA variant (A2017U) and stock B29. Folks with EU/global variant (A2017G) may have issues and as of right now, should proceed with caution. If you see any problems and/or have a different variant and need additional (or different) steps added, let me know. I will update the thread as necessary.
Copy everything off your internal storage that you don't want to lose.
Get all of the files you need from the steps below and put them on your microSD card.
Backup your boot and recovery (just in case) using the tool found here: http://forum.xda-developers.com/axon-7/development/wip-axon-7-root-bootloader-unlokced-t3441204
Using the same tool as above, flash TWRP (recovery) found in that thread. You do not need to flash the boot image!
Unlock the bootloader: http://forum.xda-developers.com/axon-7/how-to/guide-how-to-unlock-bootloader-stay-t3461165
Flash the bootstack and ROM for your variant: http://forum.xda-developers.com/axon-7/development/rom-guide-updates-to-stock-files-via-t3469484
Boot phone, set it up, whatever
Reboot to TWRP, go to Advanced > Terminal and type: reboot disemmcwp
This will leave you with an unlocked bootloader, fully functioning TWRP (no data encryption issue), and a rooted phone. You will no longer be able to receive OTAs!
Putting Your Axon 7 Back to Stock
If you want to revert back to stock and re-lock your bootloader (eg. sending the phone in for warranty work or are selling it), you should be able to do that using the steps below. It worked for me, anyway, exactly as written below.
Copy everything off your internal storage that you don't want to lose. If you're not rooted (so already stock, but with unlocked bootloader), skip to step 6 below. Otherwise, continue.
Grab the "StockSystem" zip for your variant from this thread and place on your microSD card: http://forum.xda-developers.com/axon-7/development/rom-guide-updates-to-stock-files-via-t3469484
Reboot into TWRP and wipe system, data, dalvik, and cache
Flash the StockSystem zip and power off (doing so will restore stock boot but does not appear to restore recovery)
Boot into EDL mode and flash stock recovery only: http://forum.xda-developers.com/axon-7/development/wip-axon-7-root-bootloader-unlokced-t3441204
Power off the phone, plug from computer, and then boot into stock recovery (hold Vol+ and press Pwr, continue holding Vol+ until recovery comes up)
Select "Wipe data / factory reset" and then "Yes"
After that finishes, select "Reboot to bootloader"
Plug in your phone into your computer and do: fastboot oem lock (see second post if this doesn't work and says <waiting for device>)
Your phone will reboot and should have been totally wiped (including internal storage) by doing the above
This should leave you with a stock, locked, and unrooted phone that can take OTAs. Note: it's possible (in fact, likely) that an OTA could break the ability to unlock your bootloader and gain root again, so be careful about going back to stock if you think you'll want to unlock/root later on!
If you need any stock files for B20 or B27 (stock recovery for re-locking, for example), you can get them here: http://forum.xda-developers.com/axon-7/development/untouched-b20-boot-recovery-files-t3443818
What does disemmcwp do and why should I do it?
disable emmc (internal storage) write protection is what allows changes to system (such as AdAway) to stick with reboot. You need to run this before your changes will stick. You don't have to use TWRP (you could also use a terminal emulator or ADB), but I find that since you have to reboot anyway, it's just as easy to do it in TWRP.
I only see B27 files and not B29. Help!
If you're in any of the threads referenced in the OP that only have files marked as B27, you can use those even if you're on or upgrading to B29. If the thread has B29 files, use those.
Fastboot can't find my device.
If fastboot oem lock returns <waiting for device> or fastboot devices doesn't show anything, the most likely culprit is that Windows is using updated ADB drivers and you need to roll back. You can do this via Device Manager > right-click Android Device (or Kedacom USB device) / Android Bootloader Interface > Update driver > Browse my computer for driver software > Let me pick... > Choose older version (in this case, v9)
For #3, you might want to emphasize that only TWRP is needed, and that people can skip flashing a boot.img. I've seen people who want to unlock their bootloader asking where to find the modified boot.img for B29, which isn't needed.
And of course, thanks for the guide!
xtermmin said:
For #3, you might want to emphasize that only TWRP is needed, and that people can skip flashing a boot.img. I've seen people who want to unlock their bootloader asking where to find the modified boot.img for B29, which isn't needed.
And of course, thanks for the guide!
Click to expand...
Click to collapse
Excellent point. Done!
It would be nice if someone can post a video on YouTube. That would make it that much easier.
Thanks for your guide.
It will be good to post also the steps to lock it again, in case that we need to send the phone for warranty. Because this method does not void warranty, does it?
I think that it is only to push the backup fastboot and 'fastboot oem lock'
I have set up my phone now (with fingerprint security) and want to make a full backup in twrp. Is it true, that i must disable fingerpint and/or pin before i make an backup because when i restore backup with security enabled, that the phone was locked?
Also it would be nice a guide how to go back to stock and update to latest OTA.
Sent from my ZTE A2017G using Tapatalk
tasar said:
I have set up my phone now (with fingerprint security) and want to make a full backup in twrp. Is it true, that i must disable fingerpint and/or pin before i make an backup because when i restore backup with security enabled, that the phone was locked?
Click to expand...
Click to collapse
Yes you must disable your screen lock due to the encryption issue in MiFavor. If you do not disable your screen lock and restore your data, your pin/password/pattern would become wrong and your only option would be to factory reset. Fingerprint would still work but I wouldn't risk it.
dejikocv said:
Thanks for your guide.
It will be good to post also the steps to lock it again, in case that we need to send the phone for warranty. Because this method does not void warranty, does it?
I think that it is only to push the backup fastboot and 'fastboot oem lock'
Click to expand...
Click to collapse
razorsbk said:
Also it would be nice a guide how to go back to stock and update to latest OTA.
Click to expand...
Click to collapse
I've updated the OP with the relevant information. I haven't done it myself so I can't say what the exact screens are, but the steps should be pretty close and you should be able to figure it out.
If no one confirms (or corrects) the steps as I've written them, I'll go through the process before installing CM and update the steps to more accurately describe the process.
@rczrider
I'll updating my sticky thread/guide/info to direct everyone who want to unlock/root their devices, here to your thread....instead of having an outdated one with old info.
Can you also make a guide for g model with 05 update for unlocking and rooting and istalling twrp.
kodrnusa said:
Can you also make a guide for g model with 05 update for unlocking and rooting and istalling twrp.
Click to expand...
Click to collapse
This will be very helpful
Do I have to rollback to B20 or B27 to unlock bootloader?
@rczrider
I have tested the back to stock steps for you on the US model and for now those steps do not get you back to stock. I have wiped the right things and flashed the StockSystem zip multiple times but twrp lives through the wipe and StockSystem install. I'll try to get it working and report back.
Thanks for the great guide!
So, if I do this, no OTA updates. Can I just download the updates and flash them? Are they available anywhere? Or no updates, period, right now?
Orlando1193 said:
I have tested the back to stock steps for you on the US model and for now those steps do not get you back to stock. I have wiped the right things and flashed the StockSystem zip multiple times but twrp lives through the wipe and StockSystem install. I'll try to get it working and report back.
Click to expand...
Click to collapse
I was under the impression that @DrakenFX's StockSystem zip would overwrite boot, but I could be wrong in that. Have you tried doing the same process, but manually replacing recovery using @tenfar's tool and your own original recovery image?
If you don't have your original recovery, it (among other files for B20 and B27) can be found here: http://forum.xda-developers.com/axon-7/development/untouched-b20-boot-recovery-files-t3443818
baconboy said:
Thanks for the great guide!
So, if I do this, no OTA updates. Can I just download the updates and flash them? Are they available anywhere? Or no updates, period, right now?
Click to expand...
Click to collapse
Correct, no updates at all for the moment. As it stands, I believe we would need a modified/merged full zip that included the OTA's content. You definitely won't be able to receive OTAs officially.
Everytime i want unlock bootloader i get this error
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem unlock
...
FAILED (remote: unknown command)
finished. total time: 0.000s
C:\Program Files (x86)\Minimal ADB and Fastboot>
Great thread. Just wish this post was up 2 days ago. I just flashed B29 to my Axon from B20_Boot (which I now have read was a bad move. I just found out call audio & mic arent working). Good thing you put this post up. I have been scrambling through the threads to figure a solution. Just gonna flash back to B20 stock using TWRP :good:
Kevinkuensken said:
Everytime i want unlock bootloader i get this error
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem unlock
...
FAILED (remote: unknown command)
finished. total time: 0.000s
C:\Program Files (x86)\Minimal ADB and Fastboot>
Click to expand...
Click to collapse
You probably haven't enabled OEM Unlock in Developer Options.
So i just decided to join the rest of the world and get myself a rectangle. so i researched the 1 to 200 dollar range for weeks until i found my new shiny metal friend with great specs and a price that wouldn't keep me up at night. the le max 2 x829. but i love tech and was really looking forward to pushing this phone and learn about all it could do! i was really excited.
Until i started to learn about the many confusing programs needed to install custom roms or make a recovery file. things like that All of which need like 6 different programs all of which seem to need some other program in order to functional. I can't seem to even find a starting point! I HAVE NEVER FELT THIS STUPID IN MY ENTIRE LIFE. Someone please help. what programs do i need for a new os ? How does adb fit into the chain of programs needed to mod android? is twrp the first program needed? how does it all sort...fit to gather? Thanks for any help!
Man, honestly this forum is made to help people, but also people should use the search button. This question has been answered a million times already.
Long story short:
- Connect the phone to the PC and install the drivers (including ADB)
- Unlock bootloader (usually it's already unlocked)
- Download TWRP on your PC
- Install TWRP following the developer's steps
- Download your custom ROM
- Put the ROM on the internal memory
- Boot into TWRP
- Install the new ROM according to the instructions given by the developer and you're done...
valy_cta said:
Man, honestly this forum is made to help people, but also people should use the search button. This question has been answered a million times already.
Long story short:
- Connect the phone to the PC and install the drivers (including ADB)
- Unlock bootloader (usually it's already unlocked)
- Download TWRP on your PC
- Install TWRP following the developer's steps
- Download your custom ROM
- Put the ROM on the internal memory
- Boot into TWRP
- Install the new ROM according to the instructions given by the developer and you're done...
Click to expand...
Click to collapse
including adb? what other drivers do i need? xposed? supersu? ...i have done my research by the way...its just not making alot of sense..thats all. i know all you old pros have probably been at it for years but i never even held a smartphone until 6 days ago ha ha
valy_cta said:
Man, honestly this forum is made to help people, but also people should use the search button. This question has been answered a million times already.
Long story short:
- Connect the phone to the PC and install the drivers (including ADB)
- Unlock bootloader (usually it's already unlocked)
- Download TWRP on your PC
- Install TWRP following the developer's steps
- Download your custom ROM
- Put the ROM on the internal memory
- Boot into TWRP
- Install the new ROM according to the instructions given by the developer and you're done...
Click to expand...
Click to collapse
Also how do you download twrp on you're pc ? it won't let me i have it on my phone but it just keeps leading me to a website to download again.
Serialjwalker said:
Also how do you download twrp on you're pc ? it won't let me i have it on my phone but it just keeps leading me to a website to download again.
Click to expand...
Click to collapse
Do you have it installed on the phone or just downloaded? If it's installed, jump over that step. If it's just downloaded, connect the phone to the pc by cable, transfer the files :cyclops:
I understand your concern. It's because there are a few ways of doing it, and so novices might be confused when comparing two different tutorials.
This one is very complete: https://forum.xda-developers.com/le-max-2/how-to/protocol-backup-stock-rom-flash-stock-t3517151
1. Connect your phone, it is supposed to install drivers automatically.
1.1 If not, you'll need to google it, but I believe this toolkit will help you. In fact, this tool is capable of doing all the process for you by simply clicking on some buttons.2. Install ADB Drivers. There are a few options and it is basically
2.1 @greenManGaming recommends 15 seconds ADB installer.
2.2 (Alternative) Minimal ADB and Fastboot. I've used this one.
2.3 (Alternative) ADB and Fastboot (newer) or Universal ADB and Fastboot (older) from the same dev.
OBS: I'm not sure if the toolkit requires or not one of these options to work properly or if it already does this task.3. Download TWRP (on your computer).
3.1 Follow the instructions from the official page. In short, put the img into the ADB folder.4. Follow the commands in the the tutorial mentioned.
4.1 In short, unlock the bootloader, boot twrp, complete backup, reboot into the system, copy the backup to your PC/Cloud service, get back to fastboot mode, flash twrp, then flash your ROM.
OBS: Suggestion for only booting TWRP at the first time is perfectly optional, you can flash it since the beginning but in this case you wouldn't be able to backup the original recovery and everything as the phone came, in case you need go back to request an RMA.
razmth said:
I understand your concern. It's because there are a few ways of doing it, and so novices might be confused when comparing two different tutorials.
This one is very complete: https://forum.xda-developers.com/le-max-2/how-to/protocol-backup-stock-rom-flash-stock-t3517151
1. Connect your phone, it is supposed to install drivers automatically.
1.1 If not, you'll need to google it, but I believe this toolkit will help you. In fact, this tool is capable of doing all the process for you by simply clicking on some buttons.2. Install ADB Drivers. There are a few options and it is basically
2.1 @greenManGaming recommends 15 seconds ADB installer.
2.2 (Alternative) Minimal ADB and Fastboot. I've used this one.
2.3 (Alternative) ADB and Fastboot (newer) or Universal ADB and Fastboot (older) from the same dev.
OBS: I'm not sure if the toolkit requires or not one of these options to work properly or if it already does this task.3. Download TWRP (on your computer).
3.1 Follow the instructions from the official page. In short, put the img into the ADB folder.4. Follow the commands in the the tutorial mentioned.
4.1 In short, unlock the bootloader, boot twrp, complete backup, reboot into the system, copy the backup to your PC/Cloud service, get back to fastboot mode, flash twrp, then flash your ROM.
OBS: Suggestion for only booting TWRP at the first time is perfectly optional, you can flash it since the beginning but in this case you wouldn't be able to backup the original recovery and everything as the phone came, in case you need go back to request an RMA.
Click to expand...
Click to collapse
more questions....twrp will only load onto my phone and not my pc? also there are no adb driver folders just an exe. what do i do about that?
someone tell me how to delete this thread...i am just going to sell my smartphone i can't look at it anymore. every thing i try to do with it it resists every single inch of the way. nothing works according to instructions. i thought this would be fun but its hell... i give up! ...it wins going to trade this thing for the first 30 dollar burner phone i can find
Huge drama for nothing. Sell the thing, it's obviously not for you. If you can't follow some simple instructions, then it's better to sell it to some guy who likes to try at least.
valy_cta said:
Huge drama for nothing. Sell the thing, it's obviously not for you. If you can't follow some simple instructions, then it's better to sell it to some guy who likes to try at least.
Click to expand...
Click to collapse
maybe they are laid out to be simple but nothing is working as instructed. i have been at it for a week . so far installing firefox is the best i can seem to do lol simple? theres nothing simple about the gangbang of programs you need to do stuff on these phones. none of which can actually be compelled to function under any circumstances at least for me.
Serialjwalker said:
maybe they are laid out to be simple but nothing is working as instructed. i have been at it for a week . so far installing firefox is the best i can seem to do lol simple? theres nothing simple about the gangbang of programs you need to do stuff on these phones. none of which can actually be compelled to function under any circumstances at least for me.
Click to expand...
Click to collapse
If you are not familiar with giving commands with command prompt, installing drivers and needed software (android studio or minimal adb install) then you are in for a challenge, if you are not willing to learn its better to sell the phone or use it with de preinstalled android.
i find myself quite skilled( have flashed several brands of phoned in the last 5 years) and it took me a couple of days to figure out what to do and how to install twrp and my first rom, there are no one click shortcuts for this phone
Why need to install rom? It already work.
Serialjwalker said:
more questions....twrp will only load onto my phone and not my pc? also there are no adb driver folders just an exe. what do i do about that?
Click to expand...
Click to collapse
Did you try watching different videos to have a big picture of the process? It would be the first step. Even if you don't understand English, simply watch it. You'll see what would happen after each action.
Then check the written tutorial. Not a big issue at all. Really. Even for newbies, I've been one when I had a Galaxy 5, my first android that doesn't even needed to flash a custom ROM.
Whether you think you can, whether you think you can't, you're right.
The command to load the TWRP will be done on your PC, however, only your phone will load it. In short, you'll be commanding your phone through your PC.
When you install Minimal ADB and Fastboot, it will install its files in a default folder. Inside its default folder is where you should place the TWRP image.
Sent from my Le X820 using Tapatalk