I flashed a GPE RUU on my Tmo One. I have since gone back to Sense, but when initial boot screen is still the GPE screen (just says Google and the unlocked padlock). I'm assuming I need to flash a Sense firmware to get the original screen back. My Hboot version reads 1.54. I want to install a custom firmware that doesn't wipe the phone, but I can't find it. What firmware should I flash?
RangerLG said:
I flashed a GPE RUU on my Tmo One. I have since gone back to Sense, but when initial boot screen is still the GPE screen (just says Google and the unlocked padlock). I'm assuming I need to flash a Sense firmware to get the original screen back. My Hboot version reads 1.54. I want to install a custom firmware that doesn't wipe the phone, but I can't find it. What firmware should I flash?
Click to expand...
Click to collapse
If its a TMo phone, just flash the stock RUU. You can get it from HTC's site.
I'll lose root though and won't it format my entire phone? I just wanted the firmware if possible, not the whole ROM.
Related
I need a little help. I unlocked the bootloader, rooted my phone, made TWRP my recovery, and got s-off. I did not flash a custom ROM. Now though, there is an update for my phone. I want to update it to the latest via OTA and remain on the stock ROM until 4.2.2 comes out. It is my understanding that I may need to run an RUU since I have TWRP as my recovery. This is where I'm a little confused.
1) Which RUU do I select? (I currently have the stock T-Mobile US build version 1.27.531.7 CL170484 release-keys if that helps)
2) Afterr I flash the RUU, do I need to perform s -on and re-lock the bootloader prior to performing the OTA update?
3) Am I missing any major steps?
4) Would it be better to just use a custom ROM like Android Revolution rather than trying to revert back to stock, etc?
Thanks for any and all input.
bloodbath said:
I need a little help. I unlocked the bootloader, rooted my phone, made TWRP my recovery, and got s-off. I did not flash a custom ROM. Now though, there is an update for my phone. I want to update it to the latest via OTA and remain on the stock ROM until 4.2.2 comes out. It is my understanding that I may need to run an RUU since I have TWRP as my recovery. This is where I'm a little confused.
1) Which RUU do I select? (I currently have the stock T-Mobile US build version 1.27.531.7 CL170484 release-keys if that helps)
2) Afterr I flash the RUU, do I need to perform s -on and re-lock the bootloader prior to performing the OTA update?
3) Am I missing any major steps?
4) Would it be better to just use a custom ROM like Android Revolution rather than trying to revert back to stock, etc?
Thanks for any and all input.
Click to expand...
Click to collapse
you need to flash the original recovery to install ota updates,, you will lose root access doing so
Or wait until some package it into a ZIP file and flash using TWRP.
Right?
Just wait a week.
All you need to do is put the stock Tmo recovery on your one. Then go update with ota and you will still be unlocked but you do lose root.
So it seems like there is disagreement to whether the stock ROM causes you to lose root or not. Either way, I would need to "lock" the bootloader again right?
Does the update add anything really worth having? I'm thinking that ARHD would be the best bet until an RUU comes out.
bloodbath said:
So it seems like there is disagreement to whether the stock ROM causes you to lose root or not. Either way, I would need to "lock" the bootloader again right?
Does the update add anything really worth having? I'm thinking that ARHD would be the best bet until an RUU comes out.
Click to expand...
Click to collapse
I'm sorry I was wrong you will lose root after you update ota. But you can do ota while being unlocked so no need to relock bootloader just flash the stock Tmo recovery and update.
chong67 said:
Or wait until some package it into a ZIP file and flash using TWRP.
Right?
Just wait a week.
Click to expand...
Click to collapse
U mean something like this!? https://copy.com/aSLnP
Team-Noctural.com/androidtechy.com/droidnow.com
I'm aware of the OTA update next week that'll update me to Sense 6.
Currently displays in recovery:
Tampered
Unlocked
S-OFF
Currently on stock 4.4.2 rooted, no other kernel changes, etc. but the ROM I'm using has custom black boot screens added (literally just black instead of default white boot background).
Rooting is nice and all but getting tired and would just like to revert to pretty much locked bootloader, unrooted, factory condition, etc. and be able to also do OTA for future updates.
Any help is appreciated. Baby steps please.
Anyone?
First, relock your bootloader. To do that, start your phone in bootloader mode, connect your phone to pc via usb cable and type "fastboot oem lock" on command prompt. Next, download the proper ruu exe file from htc1guru.com. By proper,I mean the one that matches your phones actual model number and custom id. Execute the ruu while connecting your phone to pc in fastboot mode. Follow the on screen instructions and when finished, you will have s phone that says re locked and s-off. You will get ota in this condition and will be able to install ota and upgrade to Sense 6.0 without any problems.
http://forum.xda-developers.com/showthread.php?t=2695749
Can I just flash that RUU in the link above? It should take me back to stock 4.4.2 with no modifications, stock recovery, and since I have an unlocked bootloader + S-OFF I should be able to get OTA's.
I'm just getting replies and finding info in other threads with different methods so I just don't want to screw up anything.
SaHiLzZ said:
If you are only rooted with stock ATT software, unroot using the SuperSU app, make sure you have stock recovery, and you are golden. DO NOT turn S-ON, and also no need to lock bootloader, as with S-OFF, you will get updates with unlocked bootloader
Click to expand...
Click to collapse
I'm running stock AT&T 4.4.2 but the person who uploaded the ROM used a custom black boot screen (black HTC background instead of white when the phone boots) and so I was worried that might affect things. Hence I thought I could just flash an RUU to go back to 100% stock AT&T 4.4.2 (+ unroot) and maintaining unlocked bootloader + S-OFF so I can OTA.
EDIT: Could I just convert it to a Developer Edition using the link in your signature? Will there be any problems with my AT&T SIM card? All I have to do is relock bootloader and flash the Dev. Edition ROM.
Yes you can flash the decrypted ruu. It is the same as using the ruu exe.
If you haven't changed your mid and/cid,then what you need to is just lock the bootloader and flash the ruu (zip or exe). You will be on stock with s-off which is fine for getting ota.
Yes you can convert to developer edition. The DE and the at&t version are the same hardware-wise (except DE have 64gb storage instead of 32gb on at&t version) and have the same radio bands. You will get faster Android upgrades with no at&t bloats.
mch277 said:
http://forum.xda-developers.com/showthread.php?t=2695749
Can I just flash that RUU in the link above? It should take me back to stock 4.4.2 with no modifications, stock recovery, and since I have an unlocked bootloader + S-OFF I should be able to get OTA's.
I'm just getting replies and finding info in other threads with different methods so I just don't want to screw up anything.
I'm running stock AT&T 4.4.2 but the person who uploaded the ROM used a custom black boot screen (black HTC background instead of white when the phone boots) and so I was worried that might affect things. Hence I thought I could just flash an RUU to go back to 100% stock AT&T 4.4.2 (+ unroot) and maintaining unlocked bootloader + S-OFF so I can OTA.
EDIT: Could I just convert it to a Developer Edition using the link in your signature? Will there be any problems with my AT&T SIM card? All I have to do is relock bootloader and flash the Dev. Edition ROM.
Click to expand...
Click to collapse
You may want to just try and apply the OTA when released. I'm not aware that S-OFF is a problem, I know an unlocked bootloader nor rooted isn't an issue. I got the Rogers OTA with an unlocked bootloader a rooted (by the way was still rooted after the OTA)
Just my 0.02
mb_guy said:
You may want to just try and apply the OTA when released. I'm not aware that S-OFF is a problem, I know an unlocked bootloader nor rooted isn't an issue. I got the Rogers OTA with an unlocked bootloader a rooted (by the way was still rooted after the OTA)
Just my 0.02
Click to expand...
Click to collapse
My understanding is that, if there's any modification in system files, applying OTA may result in a bootloop/brick. I agree that rooted devices remain rooted after OTA. As the OP said that s/he us using a rom with modified boot animation, I suggested him/her to return to stock first.
I'm trying to return my HTC One back to being unrooted because I wanna update it and almost everywhere I read, you need to unroot to get over the air updates. So I got S-Off and I relocked my bootloader, but whenever I try running the RUU, it always fails. I tried flashing it and I tried running the exe file. Why does it keep failing? Also, is it true you can't get OTA updates while being rooted? The RUU I use is for Cingular (which from my understanding is the one AT&T uses) and I have Super CID. Lastly, if anyone knows an easier way to return my phone to being completely stock and unrooted that would be great. Thanks in advance!
Which RUU did you use? Apparently the last official one was JB 4.3 w/ Sense 5.0, ver. 3.17.502.3. The one for KK4.4.2 w/ Sense 5.0, ver. 4.18.502.7 was apparently not actually released by ATT and many people were having problems with it.
clsA said:
Well near as I can tell the RUU did not originate from HTC, someone was able to create it and sign it same as HTC would. But the files behave differently than the "Real" HTC RUU. The only solution I found was to use the True HTC RUU from 3.xx.502.x and OTA to 4.xx.502.x to 5.xx.502.x. It requires s-off to flash the OTA's so it's not the perfect solution for everyone.
Click to expand...
Click to collapse
So if you tried with the KK4.4.2 RUU, download the JB4.3 RUU from http://www.htc1guru.com/. Since you're S-OFF, you can use either the .exe or the decrypted .zip. I used the decrypted .zip before and it worked fine. Once you get that flashed you can then take the OTAs to update to KK4.4.2 w/ Sense 6. You'll need to be on the AT&T network to get those OTA. Otherwise you'll need to manually flash the updates, as clsA states in his post that I quoted above.
As for not getting OTAs while being rooted....
It's not so much that being rooted prevents getting OTAs. It's the process of getting to root that modifies or deletes system files that need to be intact for the OTA to work. OTA need to be installed through stock recovery. If you're rooted, it's most likely that you have a custom recovery. Also, unlocking the bootloader deletes some files the OTA checks for. If those files not there, the OTA will not install.
Flashing an RUU is the easiest way to get completely stock. It resets the phone to an out-of-the-box state. Whereas a factory reset done from bootloader or recovery basically just wipes the data partition, which will remove any apps you installed and user data. But any modifications to the system partition that are done remain. You don't get back the files that are deleted when you unlocked the bootloader.
Also, since you are S-OFF, there's no need to relock your bootloader to run an RUU. That's only required if you're S-ON. And once you get S-OFF, there is no reason to go back to S-ON.
Since I just want to get the new OTA update, do you recommend I just flash the update as opposed to going back to stock recovery because I don't mind having a rooted phone? Also, my phones camera suddenly became blurry, is it possible that the rooting had something to do with it? If it did, would flashing the OTA update fix it or would I need to go back to stock recovery or would neither fix it? Sorry for so many questions.
First off, what version is currently on your phone? Depending on where you're currently at you may need to flash more than one update in order to get it to the latest version. And no matter what, you'll need to flash stock recovery in order for the updates to flash. OTA updates, whether taken OTA or flashed manually, require stock recovery, as I mentioned before. Also, again as I mentioned before, the process of rooting your phone (more specifically, the process of unlocking your bootloader) most likely deleted files from your system partition that need to be in place in order for the OTA updates to install. If they are not there, the update will fail. So to answer your question...No, I don't recommend "just flash the update as opposed to going back to stock recovery". It won't work.
Since you didn't answer my question and state which RUU you tried, I don't know if you tried a bad 4.4.2 RUU or if there are other issues with your device and/or computer that's preventing any RUU from installing. If you just don't want to flash the RUU, then you can try flashing the update in the phone's current state and when it fails, you can analyze the error report, try to track down stock versions of the files you're missing and restore them if you find them, then try the update again, hoping you found everything. That's a lot more of a hassle than just flashing the RUU, flashing the updates, rooting, and setting up your phone.
Another option is to just flash a custom ROM. Most of them will bring the phone up to the latest version. Some will even take it higher than what is officially available from AT&T.
As for your camera problem, can't see how just rooting would cause that, but maybe it did. Without knowing the cause of the issue, I can't say if just flashing the OTA would fix it. If it's a software issue, then possibly it would. If it's a hardware issue, then probably not. Focus on updating the phone and worry about the camera issue if it still persists once updated.
Sorry, I forgot about your question. First of all, I got it working using RUU Zip M7 UL JB43 SENSE50 MR Cingular US 3.17.502.3-decrypted. The one that didn't work for me is RUU Zip M7 UL JB 50 Cingular - 1.26.502.12. Second, I am running 4.4.2. Thats for anyone who comes across this and was wondering. Thanks for your help sharksfan7. Also, in case you were wondering, my camera is still blurry, but I'll start a different thread for that.
Ok so im not new to the rooting scene but am new to the flashing scene. I know a good jist of it but cant seam to figure out the whole firmware process.
I want to install this ROM: http://forum.xda-developers.com/showthread.php?t=2699616
I am currently running 4.4.2 with 1.58.xx firmware unlocked S-OFF and rooted. and this ROM requires 2.22.1540.4
Now I have found the 2.22.1540.4 firmware and know that i have to relock my bootloader and such but my phone says my ID is CWS__001 and i cant find any with that.
Also if i flash the newest 2.23.xx firmware will i still be able to flash any rom using older firmware versions?
And last question say i am flashing a new firmware and it screws up, since my custom recovery gets removed how do i flash my nandroid backup.
also if successfully flash the new firmware am i able to flash my old backup to restore to a old firmware or do i need to reflash the old firmware first.
sorry for so many questions i just dont want to blow up my phone due to stupid mistakes.
EDIT: so I think i managed to update my firmware. In bootloader it shows 2.22.1540.3 under os but in the phone settings it still says 4.4.2 and 1.58.xxx. I am assuming all i need is a updated firmware to run the mods and not a updated software? correct me if im wrong.
What exactly did you flash (link it if you can)? I think you are confusing software (OS or ROM) with firmware. Firmware as its mostly commonly discussed here (updating to run 2.xx based ROMs) refers to the hboot, radio, recovery, and other modules (media, WiFi, Bluetooth and more) deployed with an RUU or OTA. You have only flashed firmware if you installed an RUU/OTA or manually flashed it with fastboot.
devonjerothe said:
Also if i flash the newest 2.23.xx firmware will i still be able to flash any rom using older firmware versions?
Click to expand...
Click to collapse
Yes, 2.23 firmware will work as well. But again, make sure you are talking about the right thing (firmware versus software/OS).
There is a master list of stock recovery versions for the HTC One. How do I determine which version I should be using?
None of those. That is hardly a "master" list. It's over 3 years old, never updated past the original Kitkat (M8 release) recoveries, and woefully obsolete. You'll want your recovery number to match your OS number (main version on bootloader screen or getvar all). Also, none of those are valid for AT&T version M8 (which is what I assume you have, since this section is specifically for the AT&T M8). It would need to have "502" in the version number x.xx.502.x which specifically denotes AT&T.
Why exactly do you want stock recovery? Most folks want this, in order to get OTA updates. But you will also need a stock, never rooted ROM (unrooting doesn't work), and also must be connected to the AT&T network. It's probably easier to relock the bootloader, and update by RUU. Note that RUU will wipe all data from the phone. See RUU section in my Index thread: https://forum.xda-developers.com/showthread.php?t=2751432
If you really want stock recovery, you should be able to extract it from the firmware.zip. Find the right firmware version number from the firmware collection, and extract recovery.img from the "Stock, Full Wipe" firmware zip:
https://forum.xda-developers.com/htc-one-m8/development/progress-fuu-m8-t2813792
That is definitely helpful. Thank you. I didn't realize that I could pull the bootloader out of the firmware.zip. The phone was AT&T and later unlocked and made in to a rooted Cyanogenmod phone. I had to un-root and install Android GPE. It's not really AT&T anymore. Now I can download OTA updates, but cannot install them because TWRP is still the bootloader. I would rather do the OTA updates since the phone is already stock-ish and resetting everything is only slightly preferable to stabbing my eye out.
Since I'm unlocked on marshmallow, it looks like I want the 6.12.1540.4 zip.
mortifyxda said:
I didn't realize that I could pull the bootloader out of the firmware.zip.
Click to expand...
Click to collapse
Recovery and bootloader are two completely different things! You can pull recovery.img from firmware.zip, and flash with fastboot. I would not do this with bootloader, which would require s-off (to flash manually) and it would still be risky. Better to flash the whole firmware.zip or RUU, if you want to update bootloader. But I don't think that is what you meant.
mortifyxda said:
I had to un-root and install Android GPE. It's not really AT&T anymore. Now I can download OTA updates, but cannot install them because TWRP is still the bootloader. I would rather do the OTA updates since the phone is already stock-ish and resetting everything is only slightly preferable to stabbing my eye out.
Since I'm unlocked on marshmallow, it looks like I want the 6.12.1540.4 zip.
Click to expand...
Click to collapse
Your description is confusing, and I think you're mixing the terms up again. 6.12.1540.4 is the version number for the US Developer's Edition, which is Sense, and not the same as Google Play Edition (GPE) which is not Sense.
To OTA, the version number of the current stock ROM needs to match your firmware number (in bootloader and getar all), and you also need matching stock recovery.
To be clear, what is the current ROM (and version number) as shown in Settings? And also do fastboot getvar all, and post the result (delete IMEI and serial number). Need those pieces of info, before I can properly advise what stock recovery to use.