Related
Yesterday I received my one from T-Mobile UK with 1.28.61.7 on board. I am not quite a noob but I have always had devices with WWE un-branded firmwares. There is no bloatware on the device but I guess that, until s-off, I am dependant on T-Mobile to provide updates.
I am not particularly bothered about custom roms and, in the past I have usually gone with stock rooted roms so that I can go add-free and remove anything that I do not require.
Last night I lied awake thinking about the implications about what I have and I really need some informed advice about it.
If I root my device, how can I return it to stock in the future so that I can receive any ota updates that T-Mobile may eventually offer without a RUU which appear to be quite scarce?
Am I able to install custom firmwares based on higher firmwares ie. 1.29.401.12 and, if yes, will I be able to return my device back to stock without an RUU as backup?
I am most confused about the scenario which I have. I love the device apart from the 3 dot menu bar which is doing my head in and am confident in my ability to remove it but am worried about my safety net if something goes wrong. Please somebody enlighten me as to what I am and are not able to do. Thanks in advance.
bobsie41 said:
Yesterday I received my one from T-Mobile UK with 1.28.61.7 on board. I am not quite a noob but I have always had devices with WWE un-branded firmwares. There is no bloatware on the device but I guess that, until s-off, I am dependant on T-Mobile to provide updates.
I am not particularly bothered about custom roms and, in the past I have usually gone with stock rooted roms so that I can go add-free and remove anything that I do not require.
Last night I lied awake thinking about the implications about what I have and I really need some informed advice about it.
If I root my device, how can I return it to stock in the future so that I can receive any ota updates that T-Mobile may eventually offer without a RUU which appear to be quite scarce?
Am I able to install custom firmwares based on higher firmwares ie. 1.29.401.12 and, if yes, will I be able to return my device back to stock without an RUU as backup?
I am most confused about the scenario which I have. I love the device apart from the 3 dot menu bar which is doing my head in and am confident in my ability to remove it but am worried about my safety net if something goes wrong. Please somebody enlighten me as to what I am and are not able to do. Thanks in advance.
Click to expand...
Click to collapse
You have options. Firstly S-Off is not likely to come soon if at all. HTC made it such a pig to crack, the entire year I had my One X it was never (to my knowledge) posted here how to do it. But it's not really that necessary. S-Off just adds convenience for flashing kernels in recovery at the same time as a ROM. With S-on you just have to accept that a bit more faff is required using fastboot to change a kernel.
(Side note: I have not had my device arrive yet so I am staying out of the development threads. I heard a rumour you can have a flashable kernel for this phone with S-On. Anyone know if this is true?)
Once a custom recovery is on, take a backup of your stock ROM. That way if you ever really wanted to go back for an official OTA update, you could restore the backup, flash back the stock recovery and relock the bootloader. Not sure why you'd want to go this route though.
Being on XDA and knowing how to do this stuff means you can get all the features an official update will bring you, usually months before any carrier will be providing it. You'll just be going through all this extra work to get an update that has been in the custom ROMs for ages.
wnp_79 said:
You have options. Firstly S-Off is not likely to come soon if at all. HTC made it such a pig to crack, the entire year I had my One X it was never (to my knowledge) posted here how to do it. But it's not really that necessary. S-Off just adds convenience for flashing kernels in recovery at the same time as a ROM. With S-on you just have to accept that a bit more faff is required using fastboot to change a kernel.
(Side note: I have not had my device arrive yet so I am staying out of the development threads. I heard a rumour you can have a flashable kernel for this phone with S-On. Anyone know if this is true?)
Once a custom recovery is on, take a backup of your stock ROM. That way if you ever really wanted to go back for an official OTA update, you could restore the backup, flash back the stock recovery and relock the bootloader. Not sure why you'd want to go this route though.
Being on XDA and knowing how to do this stuff means you can get all the features an official update will bring you, usually months before any carrier will be providing it. You'll just be going through all this extra work to get an update that has been in the custom ROMs for ages.
Click to expand...
Click to collapse
Thanks for your answer. As I said, I am not quite a noob :silly:. The reason I am looking to go back to stock at a later date is that I believe (rightly or wrongly you tell me) that to update firmware in it's entirety, it is necessary to use an official update from the provider.
If I back up my official stock rom after I root, are you absolutely sure that when restoring this backup, I will be able to receive official ota updates? It is not that I don't believe you, just want to be 100% sure.
Edit Perhaps we are more likely to get s-off now that we are on Quallcom not Tegra?
S-off together with super cid would give us the ability to use any RUU for this device which gives us an excellent safety net.
bobsie41 said:
Thanks for your answer. As I said, I am not quite a noob :silly:. The reason I am looking to go back to stock at a later date is that I believe (rightly or wrongly you tell me) that to update firmware in it's entirety, it is necessary to use an official update from the provider.
If I back up my official stock rom after I root, are you absolutely sure that when restoring this backup, I will be able to receive official ota updates? It is not that I don't believe you, just want to be 100% sure.
Edit Perhaps we are more likely to get s-off now that we are on Quallcom not Tegra?
Click to expand...
Click to collapse
It's ok. It's always best to be sure before attempting something!
You will not loose out on anything by not using an official update. All it will be is the stock firmware with T-Mobile's add touches. More often than improvements to the stock firmware, carries tend to restrict the features of a ROM and add bloatware (like game demos you can't uninstall) because they have made a deal with a game developer to make some money forcing them upon you.
Even without a nandroid backup you'll still be able to download and flash the stock firmware somewhere here. Basically anything you do to your phone you will be able to undo if you so choose. The only exception to this is that if you re-lock your bootloader, HTC will still be able to tell that it was at some point unlocked if you wanted a warranty return.
Yeah, as long as the stock bootloader is available, you just need to flash it after restoring the backup, and the updates should arrive.
The firmware might be flashable without the RUU or OTA, it was on the One X, but it was necessary to relock the bootloader.
I say go for it, mike1986 has the stock ROM in the dev section as well as his stock like improved ROM.
Hi Guys, I just got the phone (international/ non-carrier version) yesterday. Updated it to 4.3, and rooted it, following the guide from HTCOneRoot.com.
Everything is fine and dandy, as when I rooted my previous phone. But in my sheer eagerness, I didn't find out that the 4.4 was available also.
I now have a rooted phone, and I can't update it, as it goes directly to TWRP recovery when I try to install. I guess this is what it's supposed to do?
From what I can read you cannot install OTA when you have rooted your phone.
So I tried looking up how to unroot it. But this seems like a rather difficult project, and I am not sure I understand. From what I read I need to download a RUU, to install a stock rom(?) and I tried looking up this, but there are tons to select from, and I haven't the slightest clue which matches my phone. Can anyone be of assistance, as to how I can revert my root and update to 4.4, so I can root my phone with the latest android, instead? I'm not really interested in getting a custom rom on my phone.
Guess I should've read more about rooting before doing it, as I'm kind of a novice, but I'm more a trial and error kinda guy .
Thanks.
Edit: Or should I just find a custom "stock" KitKat ROM, and install that, from my current position? Is that even possible?
Sort of an answer
Faderskibet said:
Hi Guys, I just got the phone (international/ non-carrier version) yesterday. Updated it to 4.3, and rooted it, following the guide from HTCOneRoot.com.
Everything is fine and dandy, as when I rooted my previous phone. But in my sheer eagerness, I didn't find out that the 4.4 was available also.
I now have a rooted phone, and I can't update it, as it goes directly to TWRP recovery when I try to install. I guess this is what it's supposed to do?
From what I can read you cannot install OTA when you have rooted your phone.
So I tried looking up how to unroot it. But this seems like a rather difficult project, and I am not sure I understand. From what I read I need to download a RUU, to install a stock rom(?) and I tried looking up this, but there are tons to select from, and I haven't the slightest clue which matches my phone. Can anyone be of assistance, as to how I can revert my root and update to 4.4, so I can root my phone with the latest android, instead? I'm not really interested in getting a custom rom on my phone.
Guess I should've read more about rooting before doing it, as I'm kind of a novice, but I'm more a trial and error kinda guy .
Thanks.
Edit: Or should I just find a custom "stock" KitKat ROM, and install that, from my current position? Is that even possible?
Click to expand...
Click to collapse
Hey man, so to find the right ruu go here htcdev webiste, go under kernel source code and then choose device as the one and then choose carrier and download one of the matching ones.
For the other stuff I'm in the same boat as you. Just waiting for answers...I would try looking at youtube and type how to unbrick htc one and try those first. Didn't work for me but might for you.
christianpencz said:
Hey man, so to find the right ruu go here htcdev webiste, go under kernel source code and then choose device as the one and then choose carrier and download one of the matching ones.
For the other stuff I'm in the same boat as you. Just waiting for answers...I would try looking at youtube and type how to unbrick htc one and try those first. Didn't work for me but might for you.
Click to expand...
Click to collapse
Thanks. I'll look that up.
I am not bricked, as the situation is now. I just have a rooted phone, working with 4.3. And I want to upgrade to 4.4.
So I guess I have to choose HTC as carrier? I live in Denmark and am unsure whether to choose EU or EU NFC as region? Also what kernel version do I want to download? I am somewhat unsure what to do next.
Faderskibet said:
Thanks. I'll look that up.
I am not bricked, as the situation is now. I just have a rooted phone, working with 4.3. And I want to upgrade to 4.4.
So I guess I have to choose HTC as carrier? I live in Denmark and am unsure whether to choose EU or EU NFC as region? Also what kernel version do I want to download? I am somewhat unsure what to do next.
Click to expand...
Click to collapse
Do a fastboot getvar all, and choose the RUU that matches your MID and your CID
I've only rooted my phone so far. From what I understand I can just install a "custom 4.4" from this point, right?
So Im no noob to android nor the rom/rooting crap. But i come from nexus devices and we all know how super simple those are to use and return to stock. I dont understand the HTC crap. I bought this m9 and thought it was going to be dev friendly like nexus's are but I was wrong. This is what I did. Unlocked bootloader, flashed TWRP (and before I made the backup, I set it to r/w) then i made a stock backup that was set on R/W and did some other things like flashing CM etc.. My question is, if i wanted to return to stock and be able to receive OTAs, what must I do. Would downloading a stock nandroid from here be enough or must I run an RUU(which i dont understand). Also, I still have S-ON and have not modified that. If read some guides but Im still confused. Nothing like a nexus. Any help would be appreciated. Thanks (tmobile USA)
bynarie said:
So Im no noob to android nor the rom/rooting crap. But i come from nexus devices and we all know how super simple those are to use and return to stock. I dont understand the HTC crap. I bought this m9 and thought it was going to be dev friendly like nexus's are but I was wrong. This is what I did. Unlocked bootloader, flashed TWRP (and before I made the backup, I set it to r/w) then i made a stock backup that was set on R/W and did some other things like flashing CM etc.. My question is, if i wanted to return to stock and be able to receive OTAs, what must I do. Would downloading a stock nandroid from here be enough or must I run an RUU(which i dont understand). Also, I still have S-ON and have not modified that. If read some guides but Im still confused. Nothing like a nexus. Any help would be appreciated. Thanks (tmobile USA)
Click to expand...
Click to collapse
Your best bet is to run the RUU exe from your pc, its very simple and takes about 10 min. It wipes everything and put you back to 100% stock.
it will not change your unlocked bootloader or S-on/S-off. keep in mind since you are S-on you can only use the RUU for the current version that is on your phone, you cant go back to earlier version
you can get the RUU's here
also the get OTA you have to be unrooted, and have stock recovery
Hope this helps
kc6wke said:
Your best bet is to run the RUU exe from your pc, its very simple and takes about 10 min. It wipes everything and put you back to 100% stock.
it will not change your unlocked bootloader or S-on/S-off. keep in mind since you are S-on you can only use the RUU for the current version that is on your phone, you cant go back to earlier version
you can get the RUU's here
also the get OTA you have to be unrooted, and have stock recovery
Hope this helps
Click to expand...
Click to collapse
So, if I S-off I can run an RUU for any version, even the newest? And as long as I have stock recovery/unrooted I will be able to get OTA? Its that easy? Thanks for the help
I am trying to update to marshmallow ( little behind I know). I have searched for my stock recovery and due to my CID number not being on the stock nandroid&recovery thread, it was a bit harder. I found a few posts elsewhere that Gabe a direct link to it, but I am running into a problem when flashing it. I may be doing something wrong, so hopefully someone can point it out, if I am.
When I flashed it the first time (to update to lollipop) everything went fine. But now when I flash it, I just get a little green progress bar that shows up at the upper right hand side of the bootloader screen. I have been using Windroid by the way, to flash said recovery. When windroid says it's completed, the phone reboots back to bootloader, and I am forced to re-flash TWRP.
Is this because I have the wrong recovery? Or am I missing a step in the process? You DO need a stock recovery to run the RUU, correct? My understanding of the process is:
Flash stock rom & recovery
Relock bootloader
Run RUU.
Please help. Thanks
If you are s-on all you need to do is re-lock bootloader and run the RUU.
Damn. See, I see all these other instructions and get confused. That's what I thought, but I was nervous to try it. The way I described would be for an OTA update, right?
Thank you, by the way
garyg199 said:
Damn. See, I see all these other instructions and get confused. That's what I thought, but I was nervous to try it. The way I described would be for an OTA update, right?
Thank you, by the way
Click to expand...
Click to collapse
I've never taken an OTA lol but as far as I know you need a stock rom (with nothing modified) and stock recovery in order for the OTA to go through without issues.
Easiest way to accomplish that would be to RUU 1 update before the current 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.