Related
Hello. The subject matter says it all.
I currently have a rooted and unlocked AT&T Atrix on 1.26 version (yeah...still in ice age ) with a locked bootloader. Im with a non-US telco carrier. It came unlocked and rooted so that was great. No hassle but now I have started doing research on custom roms and webtop mods. I am trying to get around the info overload, so pls bear with my questions.
The overall goal is to have a stock/custom rom devoid of all the bloatwares and can run webtop2sd, and if that is not possible then, webtop. Very simple needs.
Option 1
======
To remain on stock rom and update to 1.83 version, and then to install the webtop2sd mod. Ideally I would like to boot off Debian from the microsd card. There was a post in which a forumer mentioned that he was able to "frankenstein" the webtop2sd and webtop mods. Thats great if I understood correctly.
Option 2
======
To update to 4.5.91 (probably a custom rom like Aura) and then install the webtop2sd/webtop mod.
What should be done?
I am going to update 1.26 -> 1.57 -> 1.83 -> 4.5.91 via system update. (which means I now have to signed with moto account...yes I have not as I read that there were some privacy issues.)
Through the update process, I would lose root. To keep everything clean, I am going to go through factory reset and then perform the update.
Once I am in 1.83 or 4.5.91, I will apply the root and unlock the bootloader. Which is the best way to go about this? Should I just follow the instruction here or this way. Or is there any other better way?
This is all I have for now until I install the webtop mod or the custom rom...
update your phone to wherever you want it at, then use this script to unlock the bootloader:
http://forum.xda-developers.com/showthread.php?t=1182871
after that, you can easily root your phone using the preinstall method found here:
http://forum.xda-developers.com/showthread.php?t=1138204 (second post)
if you update to 4.5.91 though, as you attempt to unlock the bootloader you will get a semi-hard brick, just have it boot up into fastboot mode and continue using the script. easy as pie!
I never got a semi-hard or *soft* brick from unlocking but that's just cause I must love to eat pudding =D . Do all the OTA updates, unlock / root, and then install the 2.3.4 fruitcake and install webtop. Best option by far, IMO, as far as the ease of transition goes. Should be cake. That's what I did and as long as you don't RSD lite with an .SBF back once on 2.3.4 OTA yer good to go.
eat yer fruitcake once updated to 2.3.4 OTA *stock gingerbread*-http://forum.xda-developers.com/showthread.php?t=1163009
Install a custom kernel if ya wanna overclock or undervolt, I would personally suggest Faux123's. -http://forum.xda-developers.com/showthread.php?t=1156040
aaand freeeze all that bloatware!-http://forum.xda-developers.com/showthread.php?t=972459
I read that its easier to update via SBF than OTA? What have your experiences been so far?
Alcapone263 said:
if you update to 4.5.91 though, as you attempt to unlock the bootloader you will get a semi-hard brick, just have it boot up into fastboot mode and continue using the script. easy as pie!
Click to expand...
Click to collapse
Maybe I should try to unlock it now... And then update.
tech_girl said:
I read that its easier to update via SBF than OTA? What have your experiences been so far?
Click to expand...
Click to collapse
well, i can't find it anymore but there is an SBF in the development forum that will allow you to update to 2.3.4 android without getting the brickable bootloader, but i personally don't see a point in using SBF. it's not meant for the end user, and using it can be risky.
SBF flashing is faster i believe, but as i said can also potentially harm your device if you're unsure of what you're doing.
SamCripp, one of the most esteemed devs here, suggests for the average person to completely stay away from sbf flashing after you've unlocked your bootloader unless you absolutely have to use it for something.
remember though, if you use the OTA update you CANNOT downgrade your device through SBF flashing, you HAVE to use the fruitcakes method. it WILL brick your device to downgrade, but only with the OTA update.
EDIT: and it's a semi-hard brick, it doesn't hurt your device in the least. you might panic at first, but it's as simple as booting into fastboot mode and finishing the script. or if you're more tech inclined, you can just do the fastboot oem unlock command through fastboot.
Phalanx7621 said:
....
eat yer fruitcake once updated to 2.3.4 OTA *stock gingerbread*-....
Click to expand...
Click to collapse
Alcapone263 said:
......
remember though, if you use the OTA update you CANNOT downgrade your device through SBF flashing, you HAVE to use the fruitcakes method.....
Click to expand...
Click to collapse
Fruitcakes??? All this jargon.... Hmmm...gotta check this out.
http://forum.xda-developers.com/showthread.php?t=1163009
yep, Fruitcakes. it's a CWM alternative to sbf flashing, much safer since it doesn't edit the bootloader at all, so there's no risk in hard bricking your device.
after you unlock your bootloader, you should install Romracer's CWM recovery here: http://forum.xda-developers.com/showthread.php?t=1204500
do all of your flashing through CWM after you unlock your bootloader, just remember to clear cache/dalvik/data between each ROM or you might get stuck in a bootloop.
Ok...CWM sounds more familiar....
If I understand correctly, I actually dont have to go via OTA. As long as I have the img file for flashing to each version, I could just use the CWM and not via OTA, right?
tech_girl said:
Ok...CWM sounds more familiar....
If I understand correctly, I actually dont have to go via OTA. As long as I have the img file for flashing to each version, I could just use the CWM and not via OTA, right?
Click to expand...
Click to collapse
well, you have to have an unlocked bootloader to get CWM. and to unlock your bootloader, you have to update to 1.8.3 or later.
after you unlock your bootloader, you can install CWM and proceed to just use CWM for your flashing needs.
i repeat again though, after you unlock your bootloader you should stay away from SBF flashing altogether. it's the quickest way to brick your device.
Alcapone263 said:
well, you have to have an unlocked bootloader to get CWM. and to unlock your bootloader, you have to update to 1.8.3 or later.
after you unlock your bootloader, you can install CWM and proceed to just use CWM for your flashing needs.
i repeat again though, after you unlock your bootloader you should stay away from SBF flashing altogether. it's the quickest way to brick your device.
Click to expand...
Click to collapse
+1
Once you unlock and get CWM installed its just a case of wiping the device and flashing zip files.
Yep after unlocking and getting rom racers cwm in, you get to have lots of fun and almost zero chance of hard bricking. Make sure you understand the pudding part. After you unlock throw rsd lite away.
After updating to 1.83 and unlocked, can I immediately installing a GB custom rom like Aura or Alien? Or do I need to update to 4.5.91 stock before I can install a custom rom? Which I assume is pre-rooted, which mean I dont have to root it..
tech_girl said:
After updating to 1.83 and unlocked, can I immediately installing a GB custom rom like Aura or Alien? Or do I need to update to 4.5.91 stock before I can install a custom rom? Which I assume is pre-rooted, which mean I dont have to root it..
Click to expand...
Click to collapse
You should be able to start flashing if you used pudding. No need to upgrade to .91 stock. I didn't. I think most roms are pre rooted now. Not that the rooting method was hard for the atrix.
I voided my warranty.
pukemon said:
You should be able to start flashing if you used pudding. No need to upgrade to .91 stock. I didn't. I think most roms are pre rooted now. Not that the rooting method was hard for the atrix.
I voided my warranty.
Click to expand...
Click to collapse
Yep thats how it works. once BL unlocked and CWM installed you can flash anything, including yes .91 stock.
Note that .91 stock OTA is not only the operating system but also modifies the bootloader hence all the hard brick warnings about flashing sbfs. When you flash zip files you don't touch the bootloader, so there is no chance of hard bricking. i.e. if you flash .91 stock from zip file from CWM as opposed to OTA, you get only the OS, not the bootloader update (which doesn't matter ).
So here's my goal, to leave everything stock, with only root (su installed), so I can install a Verizon locked app, su, and perhaps busybox (I installed Terminal Emulator, but virutally no commands available).
1. Why use the one-click method over the method? As I understand it, the just unlocks the bootloader, so I'd need to install a custom recovery, to be able to flash an unsigned zip (su). I'd like to keep the stock recovery. Perhaps the process is to flash custom recovery, su, then restore stock recovery?
2. After I get root, will future OTA updates work? I'd like to not break that functionality.
3. It would be nice if would also allow you to just get root on your phone without dealing with the bootloader.
I've rooted and flashed my old Cliq, and it's nice having root when I need it. I also wanted to play around with setting the button led backlight levels, which via the command line requires root.
wrong section man
Well, perhaps I mis-understood the sections. Seems any questions having to do with roms/rooting go in this section.
Either way, questions still stands, and it seems your the resident expert for this phone.
Forgot to add, from all the other threads I've read, it seems there is/was some confusion as to whether or not the method would all you to flash a new kernel, not that I currently want to do that.
Edit: Since this is apparently in the wrong section, can one of the mods move it?
Edit 2: Thanks Binary100100 for moving this thread to the correct section.
oryan_dunn said:
Well, perhaps I mis-understood the sections. Seems any questions having to do with roms/rooting go in this section.
Either way, questions still stands, and it seems your the resident expert for this phone.
Forgot to add, from all the other threads I've read, it seems there is/was some confusion as to whether or not the method would all you to flash a new kernel, not that I currently want to do that.
Edit: Since this is apparently in the wrong section, can one of the mods move it?
Click to expand...
Click to collapse
you can flash kernels it is harder what else you need to know
How do I backup the stock recovery?
If I unlock the bootloader, do I need to flash a custom recovery to move forward? Or does unlocking the bootloader allow me to flash unsigned zips?
yes and its hard to backup stock recovery i got a backup all ready
So with an unlocked bootloader, I won't need a custom recovery? Just trying to learn, as it's a bit different than my Cliq.
you do need custom recovery sorry man i cant do much more explaing so busy butother people help you and look around read root threads etc
Well, thanks for the help so far.
If any one else is reading this thread, these are the questions I still have:
1. How do I backup the stock recovery? I know once I load a custom recovery, I will be able to backup the stock ROM.
2. Disregarding any warranty issues, why choose the method or the One-Click method?
3. Once unlocked/rooted, will DRM content still work? Will the Movies section in the Android Market still be available? It's not on my Cliq with CyanogenMod 7.
4. Once unlocked/rooted, will OTA updates apply correctly? Was anyone rooted on 1.36.531.5 and have the 1.36.531.6 update apply correctly?
5. Does the method wipe the device?
Thanks,
Ryan
oryan_dunn said:
Well, thanks for the help so far.
If any one else is reading this thread, these are the questions I still have:
1. How do I backup the stock recovery? I know once I load a custom recovery, I will be able to backup the stock ROM.
2. Disregarding any warranty issues, why choose the method or the One-Click method?
3. Once unlocked/rooted, will DRM content still work? Will the Movies section in the Android Market still be available? It's not on my Cliq with CyanogenMod 7.
4. Once unlocked/rooted, will OTA updates apply correctly? Was anyone rooted on 1.36.531.5 and have the 1.36.531.6 update apply correctly?
5. Does the method wipe the device?
Thanks,
Ryan
Click to expand...
Click to collapse
1. There is no need to backup the stock recovery. Once you flash a custom recovery there will never be a need to go back to stock. If for whatever reason you do want stock then just flash an ruu and you'll go completely back to stock.
2. You MUST use the method to get the unlock_code.bin file to unlock your bootloader before you even attempt to get root access. Once you have your bootloader unlocked you can make changes to the root of your device. With it locked you can only obtain a partial root which will reset itself after a reboot. For example, if you obtain a temporary root and remove a system app (like boatware), or two, or ten (whatever) then reboot they will re-appear. So you MUST have either s-off (not going to happen until an exploit is found and really isn't needed) or an unlocked bootloader. Once you receive the file from HTC then follow the included instructions to unlock your device. NOTE: You will lose all of your data when you unlock your bootloader so back it up first! After your bootloader is unlocked you can obtain root by one of two methods.
a) 1-Click root script.
This simply pushes an app called SuperUser.apk to the /system partition and a su binary file to the /system/bin directory which gives us root. Then download ClorckworkMod app from Market and install the custom recovery. From the app you can select "reboot to recovery" and install your custom roms.
b) Placing a custom recovery in a form of a PH85IMG.zip on the root of your external sdcard and boot into the bootloader. Then update the recovery.
Now with all of that being said I want to make something clear. The unlock method does NOT allow you to use the device for other carriers! You would still require the T-Mobile SIM to use the device.
3. Having root does have some disadvantages. Some roms may effect the ability to watch DRM movies, watch movies from Market, etc. Depends on your rom though. Check with the developer. ALWAYS make a nandroid backup prior to flashing any rom! That way if you don't like what you flashed you can always revert.
4. Okay... well I stand corrected.... this is the ONLY real reason to install the stock recovery. However installing an OTA update will cause you to lose root. Even with a custom recovery and a stock rom... if you receive a notice to install an update it will not work! The best alternative if you really really really want the update and lose all root then flash an RUU, do the update and hope that HTC didn't do anything to prevent you from getting root again. My best advice would be to wait for your favorite developer to update his/her rom with the update that you're trying to flash. That way you won't lose your data (shouldn't anyway) and no real risk of losing root.
With all that being said... I'm moving this to General because it's where all the Q&A's go.
Thanks for all the detailed info. I'd like root (installation of Superuser only) for the stock ROM. I don't plan on installing a custom ROM at this time. If I have an unlocked bootloader, how could HTC block root access? Couldn't I just flash an su zip? Ideally, I'd like to be able to swap recoveries out to apply the OTA updates. I kinda wish they had a code to just give me root access on the stock ROM.
I see the ruu thread, but am concerned about the source of the ROMs. Does HTC ever officially release a complete stock ROM?
Sent from my HTC_Amaze_4G using XDA App
oryan_dunn said:
Thanks for all the detailed info. I'd like root (installation of Superuser only) for the stock ROM. I don't plan on installing a custom ROM at this time. If I have an unlocked bootloader, how could HTC block root access? Couldn't I just flash an su zip? Ideally, I'd like to be able to swap recoveries out to apply the OTA updates. I kinda wish they had a code to just give me root access on the stock ROM.
I see the ruu thread, but am concerned about the source of the ROMs. Does HTC ever officially release a complete stock ROM?
Sent from my HTC_Amaze_4G using XDA App
Click to expand...
Click to collapse
This is all that you really need here.
http://forum.xda-developers.com/showthread.php?t=1324177
If you really want to be able to download and install system updates you will need the stock recovery in step 4.
oryan_dunn said:
Thanks for all the detailed info. I'd like root (installation of Superuser only) for the stock ROM. I don't plan on installing a custom ROM at this time. If I have an unlocked bootloader, how could HTC block root access? Couldn't I just flash an su zip? Ideally, I'd like to be able to swap recoveries out to apply the OTA updates. I kinda wish they had a code to just give me root access on the stock ROM.
I see the ruu thread, but am concerned about the source of the ROMs. Does HTC ever officially release a complete stock ROM?
Sent from my HTC_Amaze_4G using XDA App
Click to expand...
Click to collapse
IDK but I read your questions in a very slow voice like mr. mackey in southpark or something
anyways, why are you so worried about getting OTA updates?
a developer will eventually root and deodex it anyways.
You say you want to keep stock rom, but why don't you try the Custom ROMs which are basically stock ROMs on steroids?
You do realize when you apply an OTA update you lose your root access and there is a possibility that it'll be harder to even have your device rooted in the future.
For example, the mt4g, everybody got happy and updated to the gingerbread OTA, but lost root and nobody found out how to exploit it until about a month later or so.. and that is only by downgrading which is a tedious process that many, who don't know how to use ADB, have troubles with.
I believe the OTA updates comes with new bootloaders and radios, not only the rom, so it will lock your bootloader. (I think) that's what it does to other devices. Who knows if htcdev will work on all bootloaders. just my two cents, if you want full control of your device, unlock bootloader and root it. You can get every OTA update through developers here.
Teo032 said:
IDK but I read your questions in a very slow voice like mr. mackey in southpark or something
Click to expand...
Click to collapse
Man, hopefully I don't sound like that. I really appreciate all the step-by-step guides; but, unlike most people, I want to understand what I'm doing, not just run through the steps.
anyways, why are you so worried about getting OTA updates?
a developer will eventually root and deodex it anyways.
You say you want to keep stock rom, but why don't you try the Custom ROMs which are basically stock ROMs on steroids?
Click to expand...
Click to collapse
Well, I don't really want to wipe my device at this time, so that probably rules out the HTC Dev method and installing a custom ROM. I asked about the source of the ROMs in the RUU thread, but if the stock recovery would flash them, then they'd obviously have been signed by HTC. If software is available via an official source, why would I download it from a forum? If I can get Ubuntu from Canonical, I wouldn't go download the ISO from an unofficial mirror (or if I did, I'd verify with the md5sum keys posted by Canonical).
Since I am really happy with my device as it is, and the ease of updating via OTA, I didn't want to give that up, just for the couple things I want to do with root access.
You do realize when you apply an OTA update you lose your root access and there is a possibility that it'll be harder to even have your device rooted in the future.
For example, the mt4g, everybody got happy and updated to the gingerbread OTA, but lost root and nobody found out how to exploit it until about a month later or so.. and that is only by downgrading which is a tedious process that many, who don't know how to use ADB, have troubles with.
I believe the OTA updates comes with new bootloaders and radios, not only the rom, so it will lock your bootloader. (I think) that's what it does to other devices. Who knows if htcdev will work on all bootloaders. just my two cents, if you want full control of your device, unlock bootloader and root it. You can get every OTA update through developers here.
Click to expand...
Click to collapse
Hmm, unless these devices have backup/secondary bootloaders, I doubt and OTA update would flash a new one, as an error during that flash could brick the device. It would seem odd that HTC would promise to unlock bootloaders, give an OTA update that would not work with their site. I'm not saying that it couldn't happen, just seems unlikely. Was the MT4G unlock done via? If it was an exploit to gain root, then I'd understand why they'd loose root.
oryan_dunn said:
Hmm, unless these devices have backup/secondary bootloaders, I doubt and OTA update would flash a new one, as an error during that flash could brick the device. It would seem odd that HTC would promise to unlock bootloaders, give an OTA update that would not work with their site. I'm not saying that it couldn't happen, just seems unlikely. Was the MT4G unlock done via? If it was an exploit to gain root, then I'd understand why they'd loose root.
Click to expand...
Click to collapse
HTC has updated their bootloaders via OTA on a few occasions. And we know that HTC and T-Mobile (along with other carriers) read these forums as well (shout out to HTC and our wireless carriers) so almost literally the day of an exploit is discovered and if HTC isn't happy with our findings what do you suppose they will do? They will almost always look for the safest way to update the bootloader and keep us from being able to use that exploit. Seeing that we still don't have S-OFF (and may never have it) they are obviously doing all they can to make it more and more difficult. That in itself is proof that they don't want us to have it. So would they push an OTA to keep us locked to S-ON if they can? You better believe it!
I can see them patching a hole that would get you S-OFF, but seems odd that they would take back an unlocked bootloader that they themselves unlocked.
I guess I'm ok with the offical unlock method without S-OFF, if the only things I can't do are flash a new bootloader, radio, or unlock the SIM. Did I miss anything there?
I don't get it, you say you want to use root on the stock roms, and now you're saying why bother downloading a stock ROM that is prerooted when you can download stock ROM that isn't rooted ota? What is the difference? You're going to want to root the ota updates and the developers are already providing it for you. it doesn't matter where you get it, you're gonna use some 3rd party exploit to root the ROM anyways.
You my friend seems to have a indecisive problem. I understand that you want to understand the process, but if you don't want anything to do with 3rd party developing you're in the wrong place. You're making your life very hard.
And i think that's about it about being s-on. It's more of the hardware functionality that is locked.
Think about it as a locked bios kinda... Lol
Sent from my HTC_Amaze_4G using XDA App
Teo032 said:
I don't get it, you say you want to use root on the stock roms, and now you're saying why bother downloading a stock ROM that is prerooted when you can download stock ROM that isn't rooted ota? What is the difference? You're going to want to root the ota updates and the developers are already providing it for you. it doesn't matter where you get it, you're gonna use some 3rd party exploit to root the ROM anyways.
You my friend seems to have a indecisive problem. I understand that you want to understand the process, but if you don't want anything to do with 3rd party developing you're in the wrong place. You're making your life very hard.
Sent from my HTC_Amaze_4G using XDA App
Click to expand...
Click to collapse
I don't need to use an exploit to root the stock rom. I can unlock my bootloader direct from HTC, flash a new recovery, and then flash the superuser program. That was kinda my point in asking in the first place... why use an exploit (one-click), when an official route is available?
oryan_dunn said:
I don't need to use an exploit to root the stock rom. I can unlock my bootloader direct from HTC, flash a new recovery, and then flash the superuser program. That was kinda my point in asking in the first place... why use an exploit (one-click), when an official route is available?
Click to expand...
Click to collapse
That's considered official? It's basically the same thing..
Sent from my HTC_Amaze_4G using XDA App
Teo032 said:
That's considered official? It's basically the same thing..
Sent from my HTC_Amaze_4G using XDA App
Click to expand...
Click to collapse
Well, yeah, you end up at the same place, except instead of using an exploit, I go to HTC to get an unlock code. I'd consider it official since I'd go through HTC to get the ball rolling.
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 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.
Hey everyone, I've done some research and found plenty of people trying to keep root while accepting an OTA, but couldn't find anything pertaining exactly to my question. does anyone know if i accept the next OTA from att will it unroot and remove the tampered banner on my m8? all i've done is root my device. haven't changed anything or flashed anything other than twrp recovery. just want to go back to stock as easily as possible.
thanks for any help
stumcmahan said:
Hey everyone, I've done some research and found plenty of people trying to keep root while accepting an OTA, but couldn't find anything pertaining exactly to my question. does anyone know if i accept the next OTA from att will it unroot and remove the tampered banner on my m8? all i've done is root my device. haven't changed anything or flashed anything other than twrp recovery. just want to go back to stock as easily as possible.
thanks for any help
Click to expand...
Click to collapse
You need to flash stock recovery, or the OTA won't install. In fact, you might even get stuck in a bootloop as the phone repeatedly boots into TWRP, looking for stock recovery (to install the OTA) and not finding it.
Also, if any system files have been modified by root, you need to return them to "stock" state. Otherwise the OTA will fail to install, saying the system has been modified. You can either return any system files to stock manually, or flash a stock ROM, nandroid, or RUU.
You will lose root when you OTA. But its an easy manner to just flash TWRP again, and flash SU/SuperSU to gain root. Unlocked bootloader is okay for OTA, so you don't even need to relock, unlock again, etc. to flash TWRP. But locked bootloader is required for RUU (unless you have s-off) if you choose that route in the paragraph above.