Related
Hi everyone!
This is my first post, since I never had any trouble toying around with my device. I have a rooted Incredible S, that ran MIUI perfectly. I want to return back to stock (this is imperative) and use the official ICS by HTC. I tried putting back my nandroid backup, which didn't work (perhaps an incompatible radio? I have no idea...). That's when I downloaded a stock, cracked ROM from a thread I found here. This is a Gingerbread ROM with Sence 3.0 I think. Obviously, I can't get the OTA to work. I think the issue here is that my recovery is still CWM, and that OTA only works with the stock recovery (this is what I concluded from research).
This is where I'm having trouble. A RUU doesn't seem to recognise my device, so that's not an option right now. Windows recognises my SD card when I hook up my phone through USB, so I can install ROMs just fine. Is there any way to get the stock recovery and the stock ROM without using a RUU, while keeping my device rooted? I really want all of this to be stock, so no mods, hacks or tweaks. I want my phone to be in the same state as when I bought it and rooted it, before installing custom ROMS. Is this possible?
Many, many thanks in advance!
gladii said:
Hi everyone!
This is my first post, since I never had any trouble toying around with my device. I have a rooted Incredible S, that ran MIUI perfectly. I want to return back to stock (this is imperative) and use the official ICS by HTC. I tried putting back my nandroid backup, which didn't work (perhaps an incompatible radio? I have no idea...). That's when I downloaded a stock, cracked ROM from a thread I found here. This is a Gingerbread ROM with Sence 3.0 I think. Obviously, I can't get the OTA to work. I think the issue here is that my recovery is still CWM, and that OTA only works with the stock recovery (this is what I concluded from research).
This is where I'm having trouble. A RUU doesn't seem to recognise my device, so that's not an option right now. Windows recognises my SD card when I hook up my phone through USB, so I can install ROMs just fine. Is there any way to get the stock recovery and the stock ROM without using a RUU, while keeping my device rooted? I really want all of this to be stock, so no mods, hacks or tweaks. I want my phone to be in the same state as when I bought it and rooted it, before installing custom ROMS. Is this possible?
Many, many thanks in advance!
Click to expand...
Click to collapse
Hey mate, official welcome from me Second welcome from me today lol
I would advise against going s-on and fully stock.
You cannot run a ruu or ota with a custom recovery/root.
So the easiest way to get the stock experience you want is by flashing one of tpbklake's rooted stock roms. They are basically stock roms with root and can run on a custom recovery. No tweaks or anything
http://forum.xda-developers.com/showthread.php?t=1773520
http://forum.xda-developers.com/showthread.php?t=1756500
The link above (top one) is based off a newer ruu from asia, although there is not much difference
I would also suggest to try ARHD 3.0.x for the stock optimised rom
Also which bootloader version do you have?
gladii said:
Hi everyone!
This is my first post, since I never had any trouble toying around with my device. I have a rooted Incredible S, that ran MIUI perfectly. I want to return back to stock (this is imperative) and use the official ICS by HTC. I tried putting back my nandroid backup, which didn't work (perhaps an incompatible radio? I have no idea...). That's when I downloaded a stock, cracked ROM from a thread I found here. This is a Gingerbread ROM with Sence 3.0 I think. Obviously, I can't get the OTA to work. I think the issue here is that my recovery is still CWM, and that OTA only works with the stock recovery (this is what I concluded from research).
This is where I'm having trouble. A RUU doesn't seem to recognise my device, so that's not an option right now. Windows recognises my SD card when I hook up my phone through USB, so I can install ROMs just fine. Is there any way to get the stock recovery and the stock ROM without using a RUU, while keeping my device rooted? I really want all of this to be stock, so no mods, hacks or tweaks. I want my phone to be in the same state as when I bought it and rooted it, before installing custom ROMS. Is this possible?
Many, many thanks in advance!
Click to expand...
Click to collapse
Yes there a some ROMs in the Development section that are completely stock that you can flash through recovery.
The original GB 2.3.3/Sense 2.1, the GB 2.3.5/Sense 3.0 and the latest ICS 4.0.4/Sense 3.6
markj338 said:
Hey mate, official welcome from me Second welcome from me today lol
I would advise against going s-on and fully stock.
You cannot run a ruu or ota with a custom recovery/root.
So the easiest way to get the stock experience you want is by flashing one of tpbklake's rooted stock roms. They are basically stock roms with root and can run on a custom recovery. No tweaks or anything
http://forum.xda-developers.com/showthread.php?t=1773520
http://forum.xda-developers.com/showthread.php?t=1756500
The link above (top one) is based off a newer ruu from asia, although there is not much difference
I would also suggest to try ARHD 3.0.x for the stock optimised rom
Also which bootloader version do you have?
Click to expand...
Click to collapse
I'm going to sell my device so I need it back the way it was. I want to keep it rooted though, so that the next owner can decide for himself what he wants to do with it. If he he's no techie, he can enjoy the device in stock (including OTAs, or can this be done like you mentioned?). If whe wants to toy with it, he can do that too. If it's easier to just go back to stock entirely, that's fine too.
It seems that I can no longer get into hboot now? After installing that hacked gingerbread, my device just boots into Android when pressing volume down and power??
tpbklake, I'll try to flash one of those when I can get back into recovery
Weird.. Taking out the battery fixed my recovery issue. I'll flash that ROM
Btw I seem to have hboot 6.13.1002 and radio 3805.06.03.03_M. Is this the info you need?
gladii said:
Weird.. Taking out the battery fixed my recovery issue. I'll flash that ROM
Btw I seem to have hboot 6.13.1002 and radio 3805.06.03.03_M. Is this the info you need?
Click to expand...
Click to collapse
Yes
But since you want stock it won't matter
You CANNOT have both root and ota updates
Either one or the other unfortunately
You have to make a choice a rooted stock ROM will be identical to the official ota from htc but you will be able to keep root, but can't get ota updates
but unfortunately I think sense 3.6 4.0.4 is the last update
But, I have been proven wrong before
Sent from my Nexus 7
K then in my case a full stock device would be best. How do I get started with this? First install a stock ROM, then the stock recovery and then put It back in S-OFF? Which ROM should I install (would prefer the stock 2.3.3)? And where can I find the recovery? Sorry for the basic questions but those lists of ROMs can get a bit complicated..
Still getting nowhere If I flash a stock ROM in CWM, my recovery won't go back to stock, will it? Shouldn't I try to get the stock recovery first and then use a RUU? Problem is that I can't seem to find a stock recovery anywhere. And when I extract the ROM from a RUU, it's only about 180 MB, so that can't be right, can it?
gladii said:
Still getting nowhere If I flash a stock ROM in CWM, my recovery won't go back to stock, will it? Shouldn't I try to get the stock recovery first and then use a RUU? Problem is that I can't seem to find a stock recovery anywhere. And when I extract the ROM from a RUU, it's only about 180 MB, so that can't be right, can it?
Click to expand...
Click to collapse
Which ruu? Here's a good guide http://forum.xda-developers.com/showthread.php?t=1359555 but I find it faster to flash the alparev then run the ruu, 2 steps and done.
Nonverbose said:
Which ruu? Here's a good guide http://forum.xda-developers.com/showthread.php?t=1359555 but I find it faster to flash the alparev then run the ruu, 2 steps and done.
Click to expand...
Click to collapse
Sorry for the late reply. I've been busy with exams. I've tried the RUU RUU_IncredibleC_Verizon_WWE_1.22.605.0_Radio_1.00.03.04.06_release_161493_NoDriver (but I don't actually have a Verizon, could that be the problem?).
I really have no idea what all the info in the filename means, so it's difficult to find one that fits my needs. I'll take a look at your link right now and report back!
gladii said:
Sorry for the late reply. I've been busy with exams. I've tried the RUU RUU_IncredibleC_Verizon_WWE_1.22.605.0_Radio_1.00.03.04.06_release_161493_NoDriver (but I don't actually have a Verizon, could that be the problem?).
I really have no idea what all the info in the filename means, so it's difficult to find one that fits my needs. I'll take a look at your link right now and report back!
Click to expand...
Click to collapse
DO NOT attemtp to flash that one!!!! The Verizon DINC2 is a CDMA device and the radio is not compatible.
Please read the post that nonverbose referenced for you. That tells you all you need to do.
tpbklake said:
DO NOT attemtp to flash that one!!!! The Verizon DINC2 is a CDMA device and the radio is not compatible.
Click to expand...
Click to collapse
Wow, good thing it didn't succeed! How about this one:
RUU_Vivo_Gingerbread_S_HTC_ARA_2.30.415.1_Radio_20.2808.30.085AU_3805.06.03.03_M_release_199399_signed.exe
(download link: http://www.filefactory.com/file/c0af340/n/RUU_Vivo_Gingerbread_S_HTC_ARA_2.30.415.1_Radio_20.2808.30.085AU_3805.06.03.03_M_release_199399_signed.exe)
gladii said:
Wow, good thing it didn't succeed! How about this one:
RUU_Vivo_Gingerbread_S_HTC_ARA_2.30.415.1_Radio_20.2808.30.085AU_3805.06.03.03_M_release_199399_signed.exe
(download link: http://www.filefactory.com/file/c0a...5AU_3805.06.03.03_M_release_199399_signed.exe)
Click to expand...
Click to collapse
What region of the world are you in? I would recommend the HTC WWE 2.30.405.1.
tpbklake said:
What region of the world are you in? I would recommend the HTC WWE 2.30.405.1.
Click to expand...
Click to collapse
Belgium (Brussels), western Europe. I bought the device here so it should be pretty local... I'll try that one. What does the WWE mean? (Just for the info)
gladii said:
Belgium (Brussels), western Europe. I bought the device here so it should be pretty local... I'll try that one. What does the WWE mean? (Just for the info)
Click to expand...
Click to collapse
World Wide English with support for most European languages
gladii said:
Belgium (Brussels), western Europe. I bought the device here so it should be pretty local... I'll try that one. What does the WWE mean? (Just for the info)
Click to expand...
Click to collapse
Ah, perfect! Canceled my download, but there's a 20 minute interval before starting a new one, so it'll take me at least an hour to download it.
I've encountered this issue before, but randomness seemed to solve it back then: a fastboot command just displays "<waiting for device>" and then keeps hanging there. "fastboot devices" returns an empty line, so that's consistent. Phone is in fastboot USB mode, so I'm not sure what could be the issue?
And then I have a question. In that guide, it says that I should extract HBOOT.img from the rom I installed. In my case, my rom only contains a file named "hboot_1.13.0000_CRC_8a731c6e_0401.img" (along with others of course, but I assume they are redundant in this step); will that one do?
gladii said:
I've encountered this issue before, but randomness seemed to solve it back then: a fastboot command just displays "<waiting for device>" and then keeps hanging there. "fastboot devices" returns an empty line, so that's consistent. Phone is in fastboot USB mode, so I'm not sure what could be the issue?
And then I have a question. In that guide, it says that I should extract HBOOT.img from the rom I installed. In my case, my rom only contains a file named "hboot_1.13.0000_CRC_8a731c6e_0401.img" (along with others of course, but I assume they are redundant in this step); will that one do?
Click to expand...
Click to collapse
Sounds like it may be a port issue, cable issue or driver issue on the PC.
Have you tried different ports or a different cable? Do you have HTC Sync running in the System Tray on the PC?
As for the hboot file, yes that is the one.
gladii said:
And then I have a question. In that guide, it says that I should extract HBOOT.img from the rom I installed. In my case, my rom only contains a file named "hboot_1.13.0000_CRC_8a731c6e_0401.img" (along with others of course, but I assume they are redundant in this step); will that one do?
Click to expand...
Click to collapse
I thought you wanted to go to stock ICS? Hboot 1.13 it a gingerbread hboot. If you just flash the vivo_downgrade.img then run the ruu, there will be no need to extract and flash the hboot from the ruu.
Nonverbose said:
I thought you wanted to go to stock ICS? Hboot 1.13 it a gingerbread hboot. If you just flash the vivo_downgrade.img then run the ruu, there will be no need to extract and flash the hboot from the ruu.
Click to expand...
Click to collapse
No I wanted it back the way I wanted it. Rom, recovery,... all stock. But surely I'll give ICS a testdrive via OTA
Hi,
I just rooted my HTC One for sprint.
If HTC comes out with over the air updates in the future, will this over-ride my root access?
Or will my phone remain rooted and still be able to update ?
Yes, you will. You could always try something like Ota Rootkeeper but i've never done anything like that lol. If an update comes out though generally you should wait until someone puts up a rooted build of the new update
We tend to get the rooted builds up very fast
mrkool444 said:
Hi,
I just rooted my HTC One for sprint.
If HTC comes out with over the air updates in the future, will this over-ride my root access?
Or will my phone remain rooted and still be able to update ?
Click to expand...
Click to collapse
Chtulhu and 3000 years of darkness happens, that's what.
Sent from my HTCONE using Tapatalk 4 Beta
Bootloops, lots and lots of bootloops...
If you feel comfortable flashing a stock recovery, you can usually run the ota, flash a custom recovery, and re-root. But, not always, and check first.
-Cupper- said:
Yes, you will. You could always try something like Ota Rootkeeper but i've never done anything like that lol. If an update comes out though generally you should wait until someone puts up a rooted build of the new update
We tend to get the rooted builds up very fast
Click to expand...
Click to collapse
I've never had anything but problems with OTA Rootkeeper it either boot loops or I lose root every single f****** time
Sent from my HTC One running ViperROM v1.1.0
benmatlock said:
I've never had anything but problems with OTA Rootkeeper it either boot loops or I lose root every single f****** time
Sent from my HTC One running ViperROM v1.1.0
Click to expand...
Click to collapse
I've never used it so I wouldn't know lol thanks though i'll stay away for future reference
Also to the OP you should consider installing a 3rd party rom, like Viper ROM
or one of the other variants around Viper ROM is pretty sweet I run it myself and it still has sense
Sent from my HTC One running ViperROM v1.1.0
jaytv said:
Bootloops, lots and lots of bootloops...
If you feel comfortable flashing a stock recovery, you can usually run the ota, flash a custom recovery, and re-root. But, not always, and check first.
Click to expand...
Click to collapse
You probably have to Relock to flash it.
Be sure to backup OFF the phone before doing anything.
I backed up with TWRP, copied it off the phone (which I had), I relocked (one ADB command), ran RUU (longest step), took OTA, re-unlocked (just reflash unlock file with ADB), reflashed TWRP, copied backup back on to phone and restored.
PITA but pretty safe and robust.
mswlogo said:
You probably have to Relock to flash it.
Be sure to backup OFF the phone before doing anything.
I backed up with TWRP, copied it off the phone (which I had), I relocked (one ADB command), ran RUU (longest step), took OTA, re-unlocked (just reflash unlock file with ADB), reflashed TWRP, copied backup back on to phone and restored.
PITA but pretty safe and robust.
Click to expand...
Click to collapse
Nope, the process I describe above works without re-lock. Plus, when you restored your Nandroid, you likely restored the .7 software. I'd check if were you.
jaytv said:
Nope, the process I describe above works without re-lock. Plus, when you restored your Nandroid, you likely restored the .7 software. I'd check if were you.
Click to expand...
Click to collapse
I described one way to robustly get the OTA firmware. After restore you just "Dirty" flash any .10 ROM
Or just restore DATA if you want stock.
I have a similar question. I am thinking about rooting my Sprint HTC One, so that I can install apps that require root. I don't mind the stock ROM and I would like to receive OTA updates. If I root my HTC One, will I continue to receive OTA updates?
RATMdrumer said:
I have a similar question. I am thinking about rooting my Sprint HTC One, so that I can install apps that require root. I don't mind the stock ROM and I would like to receive OTA updates. If I root my HTC One, will I continue to receive OTA updates?
Click to expand...
Click to collapse
if you have a custom recovery installed the updates will not install
Aldo101t said:
if you have a custom recovery installed the updates will not install
Click to expand...
Click to collapse
Can I perform a full system backup without installing a custom recovery?
RATMdrumer said:
Can I perform a full system backup without installing a custom recovery?
Click to expand...
Click to collapse
maybe with htc backup, i don't know cuz i don't use it, only way to back up the complete rom is with custom recovery
I am relatively new to the HTC. I am running a Stock rooted image with TWRP 2.6.3.0 recovery.
The OTA for 4.3 came down and whenever I start the install the phone reboots and ends up in twrp recovery and I do not know where to go from there. I tried searching the forums but the search is down at the moment.
Here comes the Noob question : A little help please as I am not sure where to go next?
I just asked almost the same question. One thing everyone says is don't take the OTA update.
I found a few places with the pre-rooted stock ROM update, but it does not include the firmware update, that is a separate flashable zip, but I'm not sure how to update the "Full Firmware w/o hboot, boot, recovery" without S-off. I don't know if doing the "full firmware update" will mess up my recovery/root.
http://forum.xda-developers.com/showthread.php?t=2467607
http://forum.xda-developers.com/showthread.php?p=46110767
generosity21 said:
I just asked almost the same question. One thing everyone says is don't take the OTA update.
I found a few places with the pre-rooted stock ROM update, but it does not include the firmware update, that is a separate flashable zip, but I'm not sure how to update the "Full Firmware w/o hboot, boot, recovery" without S-off. I don't know if doing the "full firmware update" will mess up my recovery/root.
http://forum.xda-developers.com/showthread.php?t=2467607
http://forum.xda-developers.com/showthread.php?p=46110767
Click to expand...
Click to collapse
I have been all over the forums looking at this and came up with squat.
If I take the OTA will I loose root? Can't seem to find an answer to that.
I was running an earlier version of twrp and thought that might be the issue but after updating twrp I am still at the same place. The sprint update notifications are still coming.
If I find something I will post it here.
Must be on stock firmware and recovery to take the update guys.... It has been posted numerous times. You must also ahve the stock kernel.
Yes you will lose root if you take the OTA, you always do. Also TWRP appears to be broken with 4.3, no responsive, etc, etc
jziggy101 said:
I am relatively new to the HTC. I am running a Stock rooted image with TWRP 2.6.3.0 recovery.
The OTA for 4.3 came down and whenever I start the install the phone reboots and ends up in twrp recovery and I do not know where to go from there. I tried searching the forums but the search is down at the moment.
Here comes the Noob question : A little help please as I am not sure where to go next?
Click to expand...
Click to collapse
you can't flash the update with custom recovery installed, you need thev stock recovery image which is posted numerous times in this forum
jziggy101 said:
The OTA for 4.3 came down and whenever I start the install the phone reboots and ends up in twrp recovery and I do not know where to go from there.
Click to expand...
Click to collapse
You have to have stock recovery to take the OTA
generosity21 said:
I just asked almost the same question. One thing everyone says is don't take the OTA update.
Click to expand...
Click to collapse
You can take the OTA if you are prepared for, and know what to do - also, don't take it if you are currently S-ON and ever want S-OFF because it comes with a new hboot.
jziggy101 said:
If I take the OTA will I loose root? Can't seem to find an answer to that.
Click to expand...
Click to collapse
Yes, you will probably lose root unless you are using the OTA preservation function of SuperSU and it works for you, but either way, it is easy to get it back.
Bottom line, how you take the OTA depends on whether you are S-ON or S-OFF, the latter is much easier. Assuming you are S-ON and running the Sprint stock ROM, here is what you need to do.
1. Flash stock recovery.
2. Lock the bootloader
3. Take the OTA update
4. Unlock the bootloader
5. Flash custom recovery (TWRP)
6. Flash root (SuperSU)
If you are S-off you can skip numbers 2 and 4.
Aldo101t said:
you can't flash the update with custom recovery installed, you need thev stock recovery image which is posted numerous times in this forum
Click to expand...
Click to collapse
Thanks for the replies. It's very confusing whether people are referencing the OTA update, or the tweaked, rooted downloadable update (http://forum.xda-developers.com/showthread.php?p=46110767). This forum should be friendly to questions when things are confusing.
Even with the two replies on this thread, it's still not clear to me if the downloadable (NOT OTA) updates can be flashed with a custom recovery, or what the procedure is for an S-On device regarding firmware and ROM updates. Sorry to offend anyone if they feel this has been answered somewhere in the forums, but it's still unclear to some of us.
EDIT:
@PillowMetal Thanks for the very helpful reply. I guess the next question is, is it possible to get S-Off on 1.31.651.2 without losing everything?
Kraizk said:
Must be on stock firmware and recovery to take the update guys.... It has been posted numerous times. You must also ahve the stock kernel.
Yes you will lose root if you take the OTA, you always do. Also TWRP appears to be broken with 4.3, no responsive, etc, etc
Click to expand...
Click to collapse
If your not stock ota will mess you up big time. I just rooted my HTC one on sprint with the update that was on a swap out for bad speakers . Twrp isn't responsive if you use the one in toolkit. I downloaded 2.6.3 loaded it in the data folder of toolkit installed through the toolkit and bam... I got response out of Twrp. I'll find the link and post for you guys.
Sent from my SGH-M919 using Tapatalk 4
generosity21 said:
@PillowMetal Thanks for the very helpful reply. I guess the next question is, is it possible to get S-Off on 1.31.651.2 without losing everything?
Click to expand...
Click to collapse
Not without losing everything because it requires tricking your bootloader by writing to your misc partition, then running the 1.29 RUU - http://forum.xda-developers.com/showthread.php?t=2390821
http://techerrata.com/browse/twrp2/m7wls
This is the link for people who are stock and unlocking their phone. If you're using the toolkit put it in the data folder and rename to twrp. Be careful though the other files are the same name but in capital letters! Flash it and u will have responsive twrp and rooted 4.3 ota
Sent from my SGH-M919 using Tapatalk 4
---------- Post added at 02:10 PM ---------- Previous post was at 01:34 PM ----------
Anyone having poor reception?
Sent from my SGH-M919 using Tapatalk 4
PillowMetal said:
Not without losing everything because it requires tricking your bootloader by writing to your misc partition, then running the 1.29 RUU - http://forum.xda-developers.com/showthread.php?t=2390821
Click to expand...
Click to collapse
Tried this once more, and successfully got S-off without downgrading anything, as a few others have reported.
http://forum.xda-developers.com/showthread.php?t=2314582
Brand new device Stock 1.29 Rom Uninstalled SuperSU Unrooted for Updates
PillowMetal said:
You have to have stock recovery to take the OTA
You can take the OTA if you are prepared for, and know what to do - also, don't take it if you are currently S-ON and ever want S-OFF because it comes with a new hboot.
Yes, you will probably lose root unless you are using the OTA preservation function of SuperSU and it works for you, but either way, it is easy to get it back.
Bottom line, how you take the OTA depends on whether you are S-ON or S-OFF, the latter is much easier. Assuming you are S-ON and running the Sprint stock ROM, here is what you need to do.
1. Flash stock recovery.
2. Lock the bootloader
3. Take the OTA update
4. Unlock the bootloader
5. Flash custom recovery (TWRP)
6. Flash root (SuperSU)
If you are S-off you can skip numbers 2 and 4.
Click to expand...
Click to collapse
Think I messed up a step in my attempt to return to unroot to be ready to get the 4.3 jellybean update. I was stock rom 1.29, rooted, SuperSU, twerp 2.6.3. Unlocked sim. I unistalled SuperSU using the full unroot option and relocked the bootloader. When the phone attempts to update it reboots into the bootloader straight into fastboot. Will not reboot and stay in hboot. Recovery option does nothing. Do I even want the ota 1.31? Do I just skip the OTA 1.31 and get the 4.3 jellybean update. I'm new first Android phone. Sorry for the idiocy I have portrayed here. Hope someone can help with knowledge of OTA's and Jellybean update. My problem seems so simple compared to all the other posts I read but I can't seem to figure it out on my own. Thanks everyone
upowersystems said:
Think I messed up a step in my attempt to return to unroot to be ready to get the 4.3 jellybean update. I was stock rom 1.29, rooted, SuperSU, twerp 2.6.3. Unlocked sim. I unistalled SuperSU using the full unroot option and relocked the bootloader. When the phone attempts to update it reboots into the bootloader straight into fastboot. Will not reboot and stay in hboot. Recovery option does nothing. Do I even want the ota 1.31? Do I just skip the OTA 1.31 and get the 4.3 jellybean update. I'm new first Android phone. Sorry for the idiocy I have portrayed here. Hope someone can help with knowledge of OTA's and Jellybean update. My problem seems so simple compared to all the other posts I read but I can't seem to figure it out on my own. Thanks everyone
Click to expand...
Click to collapse
Did you flash stock recovery? The OTA needs that. You did not need to unroot though. Also not sure if having an unlocked SIM interferes with OTA, never performed that myself. Since we don't have RUUs for anything later than 1.29, then yes, you will need to take the 1.31 OTA update first, then the 3.04 update.
Twerp to Stock recovery
PillowMetal said:
Did you flash stock recovery? The OTA needs that. You did not need to unroot though. Also not sure if having an unlocked SIM interferes with OTA, never performed that myself. Since we don't have RUUs for anything later than 1.29, then yes, you will need to take the 1.31 OTA update first, then the 3.04 update.
Click to expand...
Click to collapse
Darn, no I did not flash the stock recovery. Also I read another thread said I needed to unroot!lol So I was back tracing my steps to unroot, so I thought.. I did save the original backup before installing Twerp 2.6.3 and rooting so its in there if I can get to it. I really dont know how to proceed from here. There are no options in the bootloader to proceed.
Twerp vs Stock recovery
PillowMetal said:
Did you flash stock recovery? The OTA needs that. You did not need to unroot though. Also not sure if having an unlocked SIM interferes with OTA, never performed that myself. Since we don't have RUUs for anything later than 1.29, then yes, you will need to take the 1.31 OTA update first, then the 3.04 update.
Click to expand...
Click to collapse
Do I need to figure out how to flash or return to stock recovery from Twerp or can I simploy flash the 1.29 ruu back in to the device for a return to stock?
Twerp 2.6.3
PillowMetal said:
Did you flash stock recovery? The OTA needs that. You did not need to unroot though. Also not sure if having an unlocked SIM interferes with OTA, never performed that myself. Since we don't have RUUs for anything later than 1.29, then yes, you will need to take the 1.31 OTA update first, then the 3.04 update.
Click to expand...
Click to collapse
Kraizk said:
Must be on stock firmware and recovery to take the update guys.... It has been posted numerous times. You must also ahve the stock kernel.
Yes you will lose root if you take the OTA, you always do. Also TWRP appears to be broken with 4.3, no responsive, etc, etc
Click to expand...
Click to collapse
Maybe you can help. Will a re-install of the stock ruu 1.29 without removing twerp 2.6.3 and reverting to stock recovery cause issues.. Will this just completely re-install everything including stock Recovery or will twerp remain. I am running stock 1.29 rom, did save an original backup when I loaded twerp. How would I get in it to load it. Then I would not need to load the complete ruu. When I try for the ota it used to reboot to twerp. Since I unrooted it reboots to bootloader and there are NO options for load, Recovery option doesnt work. I have asked this question on several threads no one seems to know or its too simple for them to reply since I'm a newb. Thanks
upowersystems said:
Maybe you can help. Will a re-install of the stock ruu 1.29 without removing twerp 2.6.3 and reverting to stock recovery cause issues.. Will this just completely re-install everything including stock Recovery or will twerp remain. I am running stock 1.29 rom, did save an original backup when I loaded twerp. How would I get in it to load it. Then I would not need to load the complete ruu. When I try for the ota it used to reboot to twerp. Since I unrooted it reboots to bootloader and there are NO options for load, Recovery option doesnt work. I have asked this question on several threads no one seems to know or its too simple for them to reply since I'm a newb. Thanks
Click to expand...
Click to collapse
Are you S-Off? Is so, the easiest way to to get up to date for you would be to RUU back to 1.29 which will restore everything on your phone back to stock including recovery. Make sure you copy anything you want to keep off your phone's internal memory (/sdcard) because it will wipe that too.
But from there, you can then easily take the OTA update for 1.31, then take the update for 3.04. Now you have the latest and greatest and can now flash TWRP, SuperSU, and any 4.3 ROM you want. With S-Off, you do not need the bootloader unlocked, but if you want to, you can flash an old hboot 1.29 from May or earlier and use revone -u, or go through htcdev to unlock. But like I said, totally unnecessary and more of a pain for me than it is worth.
Now, if you are S-ON, that is a totally different story, you cannot flash back to 1.29 RUU unless you still on 1.29 and have not updated to 1.31 yet. If you are currently on 1.31 you will have to try and restore the backup you said you had through TWRP, flash stock recovery from fastboot, re-lock your bootloader and all kinds of other crap to get to 3.04 and unlocked and rooted again.
You would have to tell me more about what condition your phone is currently in. hboot version? recovery custom or stock? ROM version installed? S-On or S-Off, etc.
Current State
PillowMetal said:
Are you S-Off? Is so, the easiest way to to get up to date for you would be to RUU back to 1.29 which will restore everything on your phone back to stock including recovery. Make sure you copy anything you want to keep off your phone's internal memory (/sdcard) because it will wipe that too.
But from there, you can then easily take the OTA update for 1.31, then take the update for 3.04. Now you have the latest and greatest and can now flash TWRP, SuperSU, and any 4.3 ROM you want. With S-Off, you do not need the bootloader unlocked, but if you want to, you can flash an old hboot 1.29 from May or earlier and use revone -u, or go through htcdev to unlock. But like I said, totally unnecessary and more of a pain for me than it is worth.
Now, if you are S-ON, that is a totally different story, you cannot flash back to 1.29 RUU unless you still on 1.29 and have not updated to 1.31 yet. If you are currently on 1.31 you will have to try and restore the backup you said you had through TWRP, flash stock recovery from fastboot, re-lock your bootloader and all kinds of other crap to get to 3.04 and unlocked and rooted again.
You would have to tell me more about what condition your phone is currently in. hboot version? recovery custom or stock? ROM version installed? S-On or S-Off, etc.
Click to expand...
Click to collapse
Was told if I un-rooted and relocked the bootloader I should be able to update. This is a brand new phone. No data to worry about losing.
Currently:
Stock ROM 1.29, S-On, (Was rooted) Now Unrooted
Hboot 1.44 (Bootloader relocked)
Twerp Recovery (although with attempt to update to 1.31 twerp did not open as it did in prior attempts to update before unroot)
Now You have opened an interesting subject. Do I need to S-off before any updates to defeat the new hboot? New stuff is being written for the new hboot as we speak right? Read a thread last night about it. Sounded like they could s-off a 1.31 and I wouldn't need to worry about s-off'ing before upgrading. It also seems like I should be able to re load the backup of the stock recovery somehow and skip the complete load of the ruu 1.29 since I am already running it. I am probably making somethong more difficult than it needs to be but I would like to learn the little details. My first Android here. Want to learn quickly here as I Also bought the New 4g LTE Nexus 7 tablet with jelly bean. I get 4g LTE from T-mobile and just hotspot my phone.
upowersystems said:
Was told if I un-rooted and relocked the bootloader I should be able to update. This is a brand new phone. No data to worry about losing.
Currently:
Stock ROM 1.29, S-On, (Was rooted) Now Unrooted
Hboot 1.44 (Bootloader relocked)
Twerp Recovery (although with attempt to update to 1.31 twerp did not open as it did in prior attempts to update before unroot)
Now You have opened an interesting subject. Do I need to S-off before any updates to defeat the new hboot? New stuff is being written for the new hboot as we speak right? Read a thread last night about it. Sounded like they could s-off a 1.31 and I wouldn't need to worry about s-off'ing before upgrading. It also seems like I should be able to re load the backup of the stock recovery somehow and skip the complete load of the ruu 1.29 since I am already running it. I am probably making somethong more difficult than it needs to be but I would like to learn the little details. My first Android here. Want to learn quickly here as I Also bought the New 4g LTE Nexus 7 tablet with jelly bean. I get 4g LTE from T-mobile and just hotspot my phone.
Click to expand...
Click to collapse
If you don't want to go the RUU route, then the condition your phone is currently in would only require you to flash stock recovery from 1.29.651.10 (which I got from the actual OTA file). The problem is that your bootloader is now locked and your are S-ON, so you will not be able to flash stock recovery unless you unlock again. If you still have the unlock.bin file from htcdev, that will still work if was done on your current hboot version, otherwise, you would have to visit the site again. Then flash stock recovery, and relock bootloader again. Then the 1.31 update will succeed followed by the 3.04 update.
As far as S-OFF, if you ever want it, you should get it now before updating to anything - even 1.31 (as long as the date on your hboot is May 2013 or earlier). Because, you WILL get the new hboots when you update to 1.31 and 3.04 and since you are S-ON, you will be stuck with it. There is no guarantee that you will ever be able to get S-OFF again with the new hboots. People on hboot 1.54 have been waiting and clamoring for months and there has been no progress and other phones have never even been able to get S-OFF.
Using revone to S-OFF will not wipe your phone or remove anything, it does not require root, and it you do not need to be unlocked. I have performed it from the computer 3 times on Sprint phones and even have made a post about how to make it succeed. There is also a video showing how it can be done on the phone too via terminal emulator, but that method requires root.
Having S-OFF just makes life so much easier, but with it carries great responsibility because security has been turned off and you need to know what you are flashing or you can run into trouble. But as long as you can get to the bootloader, you can recover.
PillowMetal said:
You have to have stock recovery to take the OTA
You can take the OTA if you are prepared for, and know what to do - also, don't take it if you are currently S-ON and ever want S-OFF because it comes with a new hboot.
Yes, you will probably lose root unless you are using the OTA preservation function of SuperSU and it works for you, but either way, it is easy to get it back.
Bottom line, how you take the OTA depends on whether you are S-ON or S-OFF, the latter is much easier. Assuming you are S-ON and running the Sprint stock ROM, here is what you need to do.
1. Flash stock recovery.
2. Lock the bootloader
3. Take the OTA update
4. Unlock the bootloader
5. Flash custom recovery (TWRP)
6. Flash root (SuperSU)
If you are S-off you can skip numbers 2 and 4.
Click to expand...
Click to collapse
On the att variant you don't need to relock the boot loader to ota.
Sent from my XT1058 using Tapatalk 2
I have an HTC ONE on verizon.
I have been reading up on unlocking of the bootloader, rooting and achieving s-off, I have a few questions that I am hoping the XDA community can help with.
1.I am on 4.3 jellybean on my ONE will the new tool for HTC devices?
2. I just checked and the new software for the one 4.4 KitKat is out for my version of the one finally! My question is would the new tool still work if I took the 4.4 OTA update or would I loose the ability to use the new tool?
3. Also I know in this process some where that you loose everything on your phone, can someone recommend a method and/or an app to backup all of that stuff so that I do not loose it?
As for backing up your data, I'd suggest Helium. Since you're not rooyed, you will need a companion app on your computer.
Sent from my One using Tapatalk
anyone else ideas?
Noobies should not attempt to root or modify
Dont take the kk update and use firewater to unlock and get s-off. Once s-off flash a recovery and use it to backup the phone. Make sure to move the backup to your pc. Then reflash stock recovery and take the ota. Then reflash custom recovery and flash superuser with it. You would then be s-off stock rooted kitkat.
On the other hand, if you don't want S-Off (I doubt you need it), you should OTA-upgrade first to get the newest firmware for your device, then unlock and root. You should still be able to S-Off after that if you want.
If you go this route, you will lose all the contents of the phone. Helium (buggy as it is, it mostly works) a backup of SMS/call log/contacts (if they're not stored in a Google account), and a backup of /sdcard is approximately everything. Also take screenshots of what your desktop looks like, just in case you have a hard time getting that back.
You can take the ota first, it has been confirmed that firewater works on the new ota.
fenstre said:
On the other hand, if you don't want S-Off (I doubt you need it), you should OTA-upgrade first to get the newest firmware for your device, then unlock and root. You should still be able to S-Off after that if you want.
If you go this route, you will lose all the contents of the phone. Helium (buggy as it is, it mostly works) a backup of SMS/call log/contacts (if they're not stored in a Google account), and a backup of /sdcard is approximately everything. Also take screenshots of what your desktop looks like, just in case you have a hard time getting that back.
Click to expand...
Click to collapse
I agree. I doubt you will need S-OFF. You really only need it if the phone didn't allow flashing kernels, radios, and images with S-ON. But since you only need root with the HTC One, I'd suggest to stay away from S-OFF. A simple typo could brick your phone if I'm not mistaken.
Sent from my One using Tapatalk
cmlusco said:
You can take the ota first, it has been confirmed that firewater works on the new ota.
Click to expand...
Click to collapse
Are you sure? I have been reading around these forums and others and haven't heard anything? Not doubting you just don't want to take the OTA update and then loose my chance to do this to my phone?
I just Ulocked, rooted and S-offed my Freshly OTA updated to 4.4.2 One. No problems or issues.
I used :
HTCDEV to unlock
CWM for recovery and root
and FireWater to S-off
Had some hiccups along the way but nothing that came close to bricking it. Just had to change a few settings and permissions.
Asking questions in International GSM htc one will not help with a Verizon device
sent from my mobile device
cmlusco said:
You can take the ota first, it has been confirmed that firewater works on the new ota.
Click to expand...
Click to collapse
Iz3man said:
I just Ulocked, rooted and S-offed my Freshly OTA updated to 4.4.2 One. No problems or issues.
I used :
HTCDEV to unlock
CWM for recovery and root
and FireWater to S-off
Had some hiccups along the way but nothing that came close to bricking it. Just had to change a few settings and permissions.
Click to expand...
Click to collapse
I thought HTC Dev no longer worked for the htc one?
JSDragon said:
I thought HTC Dev no longer worked for the htc one?
Click to expand...
Click to collapse
Worked great for me yesterday. They emailed me a Unlock.bin file, ran it withbadb and presto unlocked.
Iz3man said:
Worked great for me yesterday. They emailed me a Unlock.bin file, ran it withbadb and presto unlocked.
Click to expand...
Click to collapse
what would you recommend for backing up all of your stuff so you can restore it after all of this?
JSDragon said:
what would you recommend for backing up all of your stuff so you can restore it after all of this?
Click to expand...
Click to collapse
I use adb backup its so far the best I've used... I didntvuse anything this go around, this one was a warranty replacement and I've been driving with my note 3... I just decided to unlock, root and soff this yesterday as a weeknight project
Iz3man said:
I use adb backup its so far the best I've used... I didntvuse anything this go around, this one was a warranty replacement and I've been driving with my note 3... I just decided to unlock, root and soff this yesterday as a weeknight project
Click to expand...
Click to collapse
Mmmmm not sure how to use that for backing up my phone.
Well I've finally rooted my HTC One M7 after months of saying I'll do it soon, I've also flashed the latest CWM recovery on there but now my question is what do I do now? I've downloaded some apps that need root permissions but nothing great. What I want is an OS that uses minimal RAM and battery. I've seen LiquidOS but that runs Android KitKat, are there any that run on Android Lollipop?
Thanks
AJHylton said:
Well I've finally rooted my HTC One M7 after months of saying I'll do it soon, I've also flashed the latest CWM recovery on there but now my question is what do I do now? I've downloaded some apps that need root permissions but nothing great.
Click to expand...
Click to collapse
Normally you only root a phone if you need to use something that requires root privileges. Its like saying: I finally managed to open that locked door to access this room where there is nothing inside that I really need... now what?
What I want is an OS that uses minimal RAM and battery. I've seen LiquidOS but that runs Android KitKat, are there any that run on Android Lollipop?
Click to expand...
Click to collapse
If you want to flash a custom rom, you don't need to root, only need to unlock the bootlaoder and flash a custom recovery (like you already did in the process of rooting). Most custom roms are pre-rooted anyway. There a lot of lollipop roms out there, check in the development section of this forum (Sense 6/7 + Lollipop or GPE lollipop). What will be the best rom for you? Its hard to tell, test a few one yourself, its the best way to find out. If you want something stripped down then probably a GPE rom will fit your needs otherwise if you prefer to have a more "complete" experience I would say go with Sense (6 or 7) rom.
alray said:
Normally you only root a phone if you need to use something that requires root privileges. Its like saying: I finally managed to open that locked door to access this room where there is nothing inside that I really need... now what?
If you want to flash a custom rom, you don't need to root, only need to unlock the bootlaoder and flash a custom recovery (like you already did in the process of rooting). Most custom roms are pre-rooted anyway. There a lot of lollipop roms out there, check in the development section of this forum (Sense 6/7 + Lollipop or GPE lollipop). What will be the best rom for you? Its hard to tell, test a few one yourself, its the best way to find out. If you want something stripped down then probably a GPE rom will fit your needs otherwise if you prefer to have a more "complete" experience I would say go with Sense (6 or 7) rom.
Click to expand...
Click to collapse
I'd like to add - change recovery to TWRP as it's recomended for most ROMs out there
Thank you, I think I'm going to go for ViperOne by Team Venom (http://forum.xda-developers.com/showthread.php?t=2334294)
This is the first time I'll be doing this so any tips or anything you'd advise me on doing?
Thank you
AJHylton said:
Thank you, I think I'm going to go for ViperOne by Team Venom (http://forum.xda-developers.com/showthread.php?t=2334294)
This is the first time I'll be doing this so any tips or anything you'd advise me on doing?
Thank you
Click to expand...
Click to collapse
yep,
Do a Nandroid backup of your current setup before flashing anything so if something goes wrong, you can simply restore that backup and use your phone. Better to save the backup your computer so if its wiped from the phone accidentally, you still have a copy.
read the OP of the ROM you want to flash twice before proceeding
Newer Sense roms (lollipop) requires a recent firmware on your phone to work properly (a 7.xx.xxx.x version). Confirm that before flashing the rom using "fastboot getvar all". The version-main number is your firmware version.
Ask questions if you are unsure about something, better than bricking your phone
You might also want to check if there is a RUU to return your phone back to stock in case you need to in the future. (your version-main will tell you the RUU version you'll need)
alray said:
yep,
Do a Nandroid backup of your current setup before flashing anything so if something goes wrong, you can simply restore that backup and use your phone. Better to save the backup your computer so if its wiped from the phone accidentally, you still have a copy.
read the OP of the ROM you want to flash twice before proceeding
Newer Sense roms (lollipop) requires a recent firmware on your phone to work properly (a 7.xx.xxx.x version). Confirm that before flashing the rom using "fastboot getvar all". The version-main number is your firmware version.
Ask questions if you are unsure about something, better than bricking your phone
You might also want to check if there is a RUU to return your phone back to stock in case you need to in the future. (your version-main will tell you the RUU version you'll need)
Click to expand...
Click to collapse
Thank you very much I think I'm ready to do it I just need to flash TWRP recovery on as I have CWM, the only 2 questions I have are;
Do I need to do anything with the bootloader, its currently unlocked but I've read on other forums some of them require the bootloader to be locked but S-Off or something? There's nothing about this in the Viper install instructions I'm just wondering if it's relevant?
Also an RUU, is that basically a recovery file with an OS? If so would I still need to look into this if I've already done a Nandroid backup?
Thank you for all your help.
AJHylton said:
Thank you very much I think I'm ready to do it I just need to flash TWRP recovery on as I have CWM, the only 2 questions I have are;
Do I need to do anything with the bootloader, its currently unlocked but I've read on other forums some of them require the bootloader to be locked but S-Off or something? There's nothing about this in the Viper install instructions I'm just wondering if it's relevant?
Also an RUU, is that basically a recovery file with an OS? If so would I still need to look into this if I've already done a Nandroid backup?
Thank you for all your help.
Click to expand...
Click to collapse
You don't need S-OFF to flash a custom rom, only an unlocked bootloader with a custom recovery.
A RUU is a factory image. It can reflash the software and firmware back to stock if needed. Its useful to know if there is one for your phone just in case you can't restore your phone using your backup for whatever reason. Tell me what your version-main is and I'll tell you if there is a RUU somewhere.
alray said:
You don't need S-OFF to flash a custom rom, only an unlocked bootloader with a custom recovery.
A RUU is a factory image. It can reflash the software and firmware back to stock if needed. Its useful to know if there is one for your phone just in case you can't restore your phone using your backup for whatever reason. Tell me what your version-main is and I'll tell you if there is a RUU somewhere.
Click to expand...
Click to collapse
Apologies this is a really noob question but how do I find that out because I've been looking at it says about using fastboot in a command window but all I get is "Waiting for device"
edit: apologies I just realised I had to actually be in fastboot mode *duhh* my version main is - version-main: 7.19.401.30
Thank you
AJHylton said:
Apologies this is a really noob question but how do I find that out because I've been looking at it says about using fastboot in a command window but all I get is "Waiting for device"
edit: apologies I just realised I had to actually be in fastboot mode *duhh* my version main is - version-main: 7.19.401.30
Thank you
Click to expand...
Click to collapse
There is no RUU for 7.19.401.30 but there is one for 7.19.401.22 which can be used on your phone if needed in the future. :good: