I'm on the OOS version before the new year's Nougat update. The device is completly untouched: stock rom, stock recovery, bootloader locked.
I'm both interested in updating to nougat (got the OTA notification) and also possibly having root in the future. Now, if I'm understanding this correctly, I need to unlock the bootloader to flash TWRP; and I need TWRP to create nandroid backups.
So how would I backup my current system, so that I'd be able to come back to the current state after unlocking the bootloader? I've only found out about the unlock process wiping the user data after already personalizing all system settings/permissions and apps to my needs... Don't really want to spend days re-doing all of that.
I've heard it's possible to boot into TWRP via fastboot without actually flashing it, would that be an option, or does it also require an unlocked bootloader? Are there maybe exploits to (ab)use in order to get root without unlocking the bootloader, so that I could backup stuff that way, or even flash a custom recovery from within the system, like I did on my old Samsung ages ago? (e.g. Dirty Cow, would that trigger dm-verity and soft-brick my phone to the point where I had to wipe it?)
Any help would be greatly appreciated.
Related
I just picked up an AT&T HTC One locally and it has HBOOT 1.44, S-ON. It's also 1.26.502.10 and there is pending OTA update for it (I assume to get it to 1.26.502.15).
I'm trying to make sure I get the progression of steps properly and here's what I have, looking for corrections
Backup - Holo Backup (formerly Simple ADB Backup) or adb CLI tools - This will let me backup as much as humanly possible without any kind of unlock/root, correct? I can also just copy/paste everything I'm allowed to when the phone shows up in Windows as a drive. I'm trying to make sure I Have as much original as-shipped phone data as possible
S-OFF - As I have HBOOT 1.44, I might as well do S-OFF, yes? I just run revone and done?
Unlock - Do I have to use htcdev.com for bootloader unlock if I have S-OFF, or is there an alternate method?
Custom Recovery - Install whichever I like, anyone have an opinion on best one available today?
Backup - With the custom recovery, I can do a nandroid backup and backup the stock ROM, correct?
Root
Do whatever I want
Is this order correct? Will this insure I have everything I need to do a 100% restore to stock, or is there something else I need to do or get? If I go this route, will I be able to set the bootloader back to S-ON and LOCKED (as opposed to RELOCKED) ?
Lastly, the question of the pending OTA update. Is this something I should inset into the process above, or is there another way to get what's included in the update? For AT&T I understand it to include radio firmware which I want to make sure is current.
I don't know about step 1.
But instead of installing custom recovery first time i'd use the command:
fastboot boot recovery.img.
That way you can boot into custom recovery and do a nandroid backup that will contain the stock recovery.
Then install custom recovery.
All the other steps seem right.
I did the unlock and root before s-off. I believe if you are using HTCdev you should unlock first, if you are unlocking a different way might not matter.
With s-off there's no need to use htcdev.
So here's what I ended up with so far:
Backup - Used Holo Backup/Simple ADB Backup and did a backup of every possible option. Also ran backup directly with adb from Android SDK using "adb backup -apk -all". I'm sure I have quadruple copies of stuff, but better safe than sorry
S-OFF - Performed with revone
Unlock - Performed with revone (in same step as S-OFF)
Backup using custom recovery - Per your suggestion Ardmanz, I booted a custom recovery while the stock recovery was still installed, then did a full backup from the custom recovery. I did this with both CWM and TWRP, mainly because I wanted to get a feel for each custom recovery, but also to get a couple backup sets, incase one ended up bad for some reason
So that leaves me with flashing custom recovery and root, and then onto trying out custom ROM's.
One thing I'm still not sure on is addressing the updates from the pending AT&T August 1 OTA update. I know it includes new radio software, but not sure if it has any other important software. Am I safest to just find the relevant items from within the OTA and apply them with adb given that I'm S-OFF, or should I take the OTA directly before I start with any custom recovery/root/rom's? I know there is a new HBOOT in the update but I thought I read that since I did S-OFF with revone I'm pretty much protected from any updates or locks that come form OTA and I can always downgrade/reverse/etc, but not really certain on it.
I bought the T-Mobile version (on AT&T) and received it yesterday, based on the numerous threads that seemed to be the best option for me. I've been unlocking, rooting, and flashing the previous 3 Android phones and have yet to brick or "damage" any of them (knock on wood). Not too worried about voiding warranty since unfortunately they sold out of DE early on.
Originally, all I wanted to do was root. Though, I should have read more carefully before accepting the 4.4 OTA, chalk it up to "new phone" excitement. Seems like you needed to remain on 4.2.2. to root and THEN updating to 4.4. Decided to go ahead and unlock the bootloader and rooting the "traditional" method. Worked fine. Unlocked bootloader, flashed TWRP, and installed SuperSU. Profit. Thanks to the all the helpful people here.
I plan to stay on stock with the Moto X...for the first time ever with an Android device. Will I be able to accept future OTA updates? From what I've interpreted, I can't because I no longer have stock recovery, is that correct? If that is the case, what would I have to do to "keep up" with future official OTA updates?
Despite unlocking, rooting, and flashing previous phones - I've realized that this is far more complicated than I thought for a layman like myself.
It is still possible, and should remain so, that you can flash OTAs using CWM or TWRP recovery while rooted if you have not made any changes to system apps. I just updated my rooted, stock rom & kernel N7 with TWRP recovery to Kitkat 4.2.2. After updating successfully, I just restored TWRP with a fastboot flash of the twrp recovery image and used TWRP to flash SuperSU 1.8. to restore root. It all worked perfectly, but I had to unfreeze a couple of apps and uninstall the AOSP root browser app. After updating, I reinstalled the AOSP browser and all is well.
Groid said:
It is still possible, and should remain so, that you can flash OTAs using CWM or TWRP recovery while rooted if you have not made any changes to system apps. I just updated my rooted, stock rom & kernel N7 with TWRP recovery to Kitkat 4.2.2. After updating successfully, I just restored TWRP with a fastboot flash of the twrp recovery image and used TWRP to flash SuperSU 1.8. to restore root. It all worked perfectly, but I had to unfreeze a couple of apps and uninstall the AOSP root browser app. After updating, I reinstalled the AOSP browser and all is well.
Click to expand...
Click to collapse
someone will have to provide the OTA zip file for us to flash throu twrp right? we wont be able to install the OTA right on the phone like normally.
claudiuslu2011 said:
someone will have to provide the OTA zip file for us to flash throu twrp right? we wont be able to install the OTA right on the phone like normally.
Click to expand...
Click to collapse
You can't flash the ota with twrp recovery, it will bootloop, other have tried it and always goes south, unlike the previous person who had a nexus 7 , the moto x is a different beast. We do have access to the firmware which you can flash with rsdlite but it wipes the phone, wipes recovery and puts the phone back to original specs
Sent on my Moto X
Hi, I was just wondering what the steps were to keep stock software and root so I can still install OTA updates. I saw the guide here: http://forum.xda-developers.com/showthread.php?t=2265618 but I wasn't quite sure under 'Rooting Stock ROM', whether this meant I had to have an unlocked bootloader and custom recovery, just an unlocked bootloader or whether I could flash this through the stock recovery.
Thanks!
leo.sutton said:
Hi, I was just wondering what the steps were to keep stock software and root so I can still install OTA updates. I saw the guide here: http://forum.xda-developers.com/showthread.php?t=2265618 but I wasn't quite sure under 'Rooting Stock ROM', whether this meant I had to have an unlocked bootloader and custom recovery, just an unlocked bootloader or whether I could flash this through the stock recovery.
Thanks!
Click to expand...
Click to collapse
Step require to root is to first unlock the bootloader, flash a custom recovery like TWRP, then root using TWRP.
When you unlock the bootloader, the process will wipe /data partition. This include the /data/preload folder were HTC preloaded apps are (flashlight, calculator, soundhound and much more). In alsmost each ota updates, some of these apps are patched but because they were wiped, the ota installation will fail. So in order to still receive ota, you must restore the entire content of that folder after unlocking bootloader. This can be done using someone's backup, guru reset rom, or a RUU.
You'll also need to restore stock recovery for your version which is needed to install ota updates.
You will probably need to re-root after each ota, which is not a really hard thing to do.
Hello,
I would like to root my phone, but do I also have to unlock the bootloader and install a custom recovery? I don't want to install custom roms, and I want to be able to install updates from Google. The phone is also unlocked, but I'm not sure if unlocking the bootloader is a totally different thing. Basically I just want to root to get features such as the notification light and install exposed.
NOTE: This will only work on lollipop, for M preview you need a modified kernel, otherwise it won't boot!
If you only need root then use Chainfire's CF-Auto-Root (https://download.chainfire.eu/628/CF-Root/CF-Auto-Root/CF-Auto-Root-shamu-shamu-nexus6.zip).
To install root, you need to unlock the bootloader (CF-Auto-Root will do it for you if it's locked), but it will wipe you entire phone, and do a factory reset. So backup everything before you root it.
This will leave your stock recovery unchanged.
Thank you. This is exactly what I wanted.
You might want to consider installing twrp also, at least you can do a backup before you start messing around with stuff. Just rooting the phone will allow you to do everything you need /want but if you change something that makes things go south you have no reference point to return to.
Also, just to clarify: You will NOT be able to recieve OTA updates after rooting your phone. Rooting, using custom recovery, custom kernel or anything at all that tampers with the system prevents OTA updates from installing.
If any of the above has occured, the only way to be able to start updating through OTA again is to flash a factory image (or at least relevant parts of one).
Unlocking the bootloader will not affect the ability to update through OTA.
I have the Amazon variant of the 16gb Blu R1 HD. I installed TWRP with the Unlock Tool for all versions tutorial (https://forum.xda-developers.com/r1-hd/how-to/unlock-tool-t3561333) on this forum and also removed ads. I would like to get back to the stock bootloader and image for my phone, to receive OTA updates and have the original experience, I am alright with having the ads back, I would just like my phone the exact same way it came from the factory. I know the updated roms will be ported and etc. I would like it back as the way it came, ads and all. (I'm aware I will not get my warranty back.) I read this tutorial: https://forum.xda-developers.com/r1-hd/how-to/firmware-amazon-blu-r1-hd-t3428197 but I'm not sure if it will work with TWRP, I'm confused whether or not fastboot works with TWRP installed. I would also like the bootloader to be locked again as well, I'm not sure whether or not flashing stock firmware would do this. If anyone could help explain this to me or point me to a tutorial somewhere it would be appreciated. I searched through the forum for similar entries, I didn't find anything for the R1 HD specifically, and entries for other phones on removing twrp/flashing stock recovery didn't seem to make sense. I apologize if I missed another post concerning this issue. Thanks.
Ladyslayer said:
I have the Amazon variant of the 16gb Blu R1 HD. I installed TWRP with the Unlock Tool for all versions tutorial (https://forum.xda-developers.com/r1-hd/how-to/unlock-tool-t3561333) on this forum and also removed ads. I would like to get back to the stock bootloader and image for my phone, to receive OTA updates and have the original experience, I am alright with having the ads back, I would just like my phone the exact same way it came from the factory. I know the updated roms will be ported and etc. I would like it back as the way it came, ads and all. (I'm aware I will not get my warranty back.) I read this tutorial: https://forum.xda-developers.com/r1-hd/how-to/firmware-amazon-blu-r1-hd-t3428197 but I'm not sure if it will work with TWRP, I'm confused whether or not fastboot works with TWRP installed. If anyone could help explain this to me or point me to a tutorial somewhere it would be appreciated. I searched through the forum for similar entries, I didn't find anything for the R1 HD specifically, and entries for other phones on removing twrp/flashing stock recovery didn't seem to make sense. I apologize if I missed another post concerning this issue. Thanks.
Click to expand...
Click to collapse
this is not quite a normal request.
any and all changes done to your phone are done at your own risk, no guarantee that the process will be "safe". and no guarantee the end result will be as expected.
I can upload stock system, boot, and recovery images.
download them, unzip the file. put the 3 .img files to the phone.
reboot phone to twrp.
select install, browse to the folder you loaded files to, you should not see the file yet. Select flash image in lower part of screen. Now select system.img, on next screen select system and swipe to confirm.
when done do same for boot.img to boot
then recovery to recovery
when all three are done do a wipe(factory reset)
this should bring you back to prime v6.1
be advised that re-locking the boot loader has potential of bricking the pone so it is not advised to do it.
also on all the early versions there are reports that after ota update with unlocked bootloader it caused a bootloop most times it was recoverable by performing "oem unlock" again.
once booted to v6.1 I suspect there will be proper update notice. but if not here is a list of the official update download links.
6.1 to 6.4
http://hwfotadown.mayitek.com/ota/r....4_GENERIC_6.0_20160710-00151468612925207.zip
6.4 to 6.5
http://hwfotadown.mayitek.com/ota/r....5_GENERIC_6.0_20160729-21551470255454500.zip
6.5 to 6.6
http://hwfotadown.mayitek.com/ota/r....6_GENERIC_6.0_20160823-20201472826184648.zip
7.4.2 to 8.4
http://hwfotadown.mayitek.com/ota/r..._V8.4_GENERIC_6.0_20170505-18551493981392.zip
17 to 21
http://hwfotadown.mayitek.com/ota/r...RIC_6.0_20170505-17451495815395129/update.zip
==>>V6.1 images.zip
.
.
@Ladyslayer
Can you tell your experience to restore phone to original condition?
Were you able to avoid bootlop and relock bootloader?
After development ceased I also wanted to restore my phone to original factory state but following restore guides leaves my phone in bootloop. BTW in @rootjunky thread there are all original 6.1 partitions that is if you feel brave and lucky, myself am scared to flash these.
@mrmazak
I think warnings in guides are misleading. Most people are aware of risks to flash modified firmware but they are not aware there is no way to restore phone to original firmware once they modify phone.
No intention to criticize you. Thank you for your effort to keep modified firmwares up to date. Looks like you are only one not giving up
kfn said:
@Ladyslayer
Can you tell your experience to restore phone to original condition?
Were you able to avoid bootlop and relock bootloader?
After development ceased I also wanted to restore my phone to original factory state but following restore guides leaves my phone in bootloop. BTW in @rootjunky thread there are all original 6.1 partitions that is if you feel brave and lucky, myself am scared to flash these.
@mrmazak
I think warnings in guides are misleading. Most people are aware of risks to flash modified firmware but they are not aware there is no way to restore phone to original firmware once they modify phone.
No intention to criticize you. Thank you for your effort to keep modified firmwares up to date. Looks like you are only one not giving up
Click to expand...
Click to collapse
well you can go back to locked but it is tricky. Think of it like this.
unlocking , allows anything you put on phone to try and load.
when you re-lock it only properly signed images are allowed to load.
so you can potentially lock yourself out of allowing phone to boot up, so the warning is more relevant when trying to go back to a locked state.
kfn said:
@Ladyslayer
Can you tell your experience to restore phone to original condition?
Were you able to avoid bootlop and relock bootloader?
After development ceased I also wanted to restore my phone to original factory state but following restore guides leaves my phone in bootloop. BTW in @rootjunky thread there are all original 6.1 partitions that is if you feel brave and lucky, myself am scared to flash these.
@mrmazak
I think warnings in guides are misleading. Most people are aware of risks to flash modified firmware but they are not aware there is no way to restore phone to original firmware once they modify phone.
No intention to criticize you. Thank you for your effort to keep modified firmwares up to date. Looks like you are only one not giving up
Click to expand...
Click to collapse
Sorry guys I have yet to try it out, I don't have a lot of time and am a little nervous to bite the bullet. @kfn, did you follow the guidelines in the above post to restore to original condition or a different set of instructions from somewhere else? Btw any suggestions on how to back up pretty much everything? Sorry Noob here obviously.
I flashed 3 original partitions system, boot, recovery as described by mrmazak then I took OTA update. After OTA update phone was in bootloop. I did not bother with backup because I do not have important data on phone.
kfn said:
I flashed 3 original partitions system, boot, recovery as described by mrmazak then I took OTA update. After OTA update phone was in bootloop. I did not bother with backup because I do not have important data on phone.
Click to expand...
Click to collapse
Which version update was it?
I can't be certain about the 8.4 or 21 updates, but older ones when that happened you needed to boot into fastboot mode and do oem unlock again.
kfn said:
I flashed 3 original partitions system, boot, recovery as described by mrmazak then I took OTA update. After OTA update phone was in bootloop. I did not bother with backup because I do not have important data on phone.
Click to expand...
Click to collapse
Did you re-lock the bootloader or was this because of an unlocked bootloader?
It was a quite a while ago, got 3 partitions from ColtonDRG's thread:
https://forum.xda-developers.com/r1-hd/how-to/guide-convert-to-prime-rollback-ota-t3432499
I downloaded from his website, I believe they were 6.1 versions.
At the time 7.4.2 was current firmware, I think phone rebooted few times taking OTA updates. And yes 'fastboot oem unlock' trick worked to get rid off bootloop.
I presume fastboot oem lock might relock bootlader but got scared to try it because of bootloop.
kfn said:
It was a quite a while ago, got 3 partitions from ColtonDRG's thread:
https://forum.xda-developers.com/r1-hd/how-to/guide-convert-to-prime-rollback-ota-t3432499
I downloaded from his website, I believe they were 6.1 versions.
At the time 7.4.2 was current firmware, I think phone rebooted few times taking OTA updates. And yes 'fastboot oem unlock' trick worked to get rid off bootloop.
I presume fastboot oem lock might relock bootlader but got scared to try it because of bootloop.
Click to expand...
Click to collapse
Do you still have the phone? Have you done the OTA updates since then with an unlocked bootloader?
did not try another OTA, put back modified ROM and disabled OTA.
Here post #312 with similar unanswered question about relocking bootloader, it is unclear for me if another OTA would properly relock it without bricking.
https://forum.xda-developers.com/r1...tock-rom-6-5-flashed-via-twrp-t3455532/page32
@mrmazak, do you know whether or not installing OTA updates would relock the bootloader? Wouldn't it be possible to do fastboot OEM lock and then do OTA updates without the risk of a bootloop? Noob question: does locking the bootloader reset the phone as well? I seem to have read something about this but I can't remember.
Ladyslayer said:
@mrmazak, do you know whether or not installing OTA updates would relock the bootloader? Wouldn't it be possible to do fastboot OEM lock and then do OTA updates without the risk of a bootloop? Noob question: does locking the bootloader reset the phone as well? I seem to have read something about this but I can't remember.
Click to expand...
Click to collapse
The update has not relocked the bootloader before.
Let me clearify a little.
There are three things I know that get changed when doing OEM unlock
1. Unlock status changed to a yes
2. Secure status changed to a no
3. Warranty status changes to no
After an ota #2 above( secure ) changes back to yes
This conflict is what makes the boot loop. As far as I know.
I do not know what it does when put back to lock and you do an ota.
I think each time you change, lock or unlock it needs to be reset the phone.
mrmazak said:
The update has not relocked the bootloader before.
Let me clearify a little.
There are three things I know that get changed when doing OEM unlock
1. Unlock status changed to a yes
2. Secure status changed to a no
3. Warranty status changes to no
After an ota #2 above( secure ) changes back to yes
This conflict is what makes the boot loop. As far as I know.
I do not know what it does when put back to lock and you do an ota.
I think each time you change, lock or unlock it needs to be reset the phone.
Click to expand...
Click to collapse
Wouldn't it change number one to a no, and two to a yes? What is the likelihood of a bootloop out bricking the phone if I re-lock the bootloader or do an OTA with the bootloader relocked? Isn't that the same as doing a normal OTA with a phone that had no changes from factory version, just the warranty status is a no and that's it?
Ladyslayer said:
Wouldn't it change number one to a no, and two to a yes? What is the likelihood of a bootloop out bricking the phone if I re-lock the bootloader or do an OTA with the bootloader relocked? Isn't that the same as doing a normal OTA with a phone that had no changes from factory version, just the warranty status is a no and that's it?
Click to expand...
Click to collapse
I do not know for sure. And there fore cannot recommend to do it. In the event something goes wrong and bootloader is locked, you cannot use fastboot to flash a repair, there fore MY opinion is the same "DO NOT relock bootloader". If something goes wrong it will be a brick.
Run stock version un modified all you want but if you unlocked I do not think you should relock. My opinion, do as you want.