I'm thinking of selling my HTC Aria for a later HTC, But firstly I would like to Get rid of Cockworkmod and also put the latest OTA on the phone, clock work wouldnt be such a problem if the OTA's flashed from clock work, but they dont.. so IM wanting to go Full bog standard factory restore, Anyone able to help me out?? I have searched the internet, and the closest i have found instructions for is the Droid x, and.. I dont wunna screw this up so im not following those instructions
Cheers and thanks in advance.
Matrox02
Which HBOOT version do you currently have?
hboot ver. 6.02.1002
You should be able to run the RUU to revert to a stock, un-rooted ROM. The HBOOT won't be downgraded, but you don't really need to downgrade it. You wouldn't even notice any difference in normal day to day use.
Edit: You will either need to install a Sense ROM before you begin the RUU process or you can put the phone on the FASTBOOT menu.
I can do that the problem with that is the OTA updates wont be able to work as clockworkmod cannot apply OTA, unless someone has a RUU of 2.3 then i wont need it, otherwise the only Ruu i can get is a early 2.2 and im looking for the WWE or Asia version I dont like the Aus one even though im in New Zealand.
matrox02 said:
I can do that the problem with that is the OTA updates wont be able to work as clockworkmod cannot apply OTA, unless someone has a RUU of 2.3 then i wont need it, otherwise the only Ruu i can get is a early 2.2 and im looking for the WWE or Asia version I dont like the Aus one even though im in New Zealand.
Click to expand...
Click to collapse
Well, as far as I know, you can receive OTA updates if you have the ROM installed. I don't think your HBOOT or recovery will matter, although I'm not positive. HOWEVER, you have no reason to worry about it anyway. There won't be any future OTA updates for the Aria, so it doesn't matter.
correct, I am able to recieve them, but the OTA fails to apply as it doesnt liek the clock work mod, if i try to go through just clockworkmod recovery it also fails to apply the update saying it cannot apply OTA's
matrox02 said:
correct, I am able to recieve them, but the OTA fails to apply as it doesnt liek the clock work mod, if i try to go through just clockworkmod recovery it also fails to apply the update saying it cannot apply OTA's
Click to expand...
Click to collapse
What OTA are we talking about?
Oh my mistake, I ment I can get Asia 2.1-update 1 and no later, the Over the air update that comes after that( phone downloads it ) fails to apply, Btw I get my RUU from Shipped-roms.com
Im busy doing the OTA update right now.. it seams to be working, unlike last time i tried.. I dunno why either, Ill update with results..
ok apparently im updated to 2.37 or something.., but the android version is 2.2 now so atleased the OTA's work
Related
Yes, this is a stupid question but I want to make sure I didint screw myself. In the rooting thread everyone says dont accept the OTA's. Well, I did. So... Couldn't I just flash the stock RUU and be back to pre-OTA status? Im sure I can but I never messed with an HTC Android Device before today. I know this would work if it was Windows Mobile.
Thanks!
Not exactly. Since you took the OTA your on a newer version, even though you will be trying to flash a stock RUU you cannot downgrade. You will get an error to the effect of your version is newer. Now if you were fully rooted phone you can certainly downgrade.
That being said don't sweat it. Yea it was recommended not to take OTA just incase, but I doubt taking the OTA is the difference between getting root or not. You may have to wait a bit longer but even that might not be the case. Rule of thumb never take OTAs!
How would you flash it if your not rooted??
an RUU is the HTC app that will flash the software for that particular OS, right from windows
Ok Iv noticed that things are getting really really confusing around here with people saying one thing then someone else saying something else. I want to have a thread that is straight forward coming from people that know what they are talking about and not just assuming.
Now my phone has never had an unlocked bootloader. Before I updated to GB OTA i was on .83 rooted with all the mods added to it (webtop dock, blah, blah blah) I RSD back to .26 (that very old file) and just started doing OTA updates one by one once i logged in with my blurr account. I updated to GB via the official OTA update that was pushed to my phone when i selected to system update under settings.
I was able to Root this ATT OFFICIAL version pushed to my phone using This Pre-install method and that is all that i have done.
What i want to do now is Unlock the bootloader. From what i have read Pudding is the best way of doing this.
Q1: Does this method (Pudding) work with the Official ATT OTA version pushed to phones and not Kenns modded version, and is it the only way to unlock the bootloader?
Q2: Once unlocked what version of CWR do I install to be able to flash ROMs? Would i be able to just install ROM Manager and do the installation from there, Or possibly both ROM Manager and CWR?
Q3: Since RSD is out of the picture for me, if for some reason I'm to soft brick my phone and can still get into Recovery mode, what .sbf do i flash, would it have to be the same one that was pushed to phones that if not already available on here will be really soon?
Thanks for all the help if anyone helps out.
StyleUkno
Q2, if you unlock your phone, cwM of tenfars, the 2nd version for unlocked. Rom manager with official CWM have released before some days, but yet it doesn't support external sd.
As for question 1, and the unlocking pudding. The OTA gb you installed, might updated you bootloader, and maybe can't use that pudding.
For that be very carefull of your next steps.. Personally I would have send a pm to the2dcour, or another dev that knows as much..
Sent from my MB860 using XDA App
Bump to see if any other responses come.
Q1: Does this method (Pudding) work with the Official ATT OTA version pushed to phones and not Kenns modded version, and is it the only way to unlock the bootloader?
Yes, pudding works and is the only way. Have to Flash pudding and run OEM unlock command in fastboot. Because you are already on OTA, there's a high chance you will need an extra couple steps. It will likely soft brick with 0x1000 error but wit fastboot option. From there you need to fastboot and re do the oem unlock command another time. Then you are fine.
Q2: Once unlocked what version of CWR do I install to be able to flash ROMs? Would i be able to just install ROM Manager and do the installation from there, Or possibly both ROM Manager and CWR?
Tenfar's 6/30 unlocked CWM. ROM Manager version doesn't properly wipe as of yet. You can update if you dont' care about wiping, but that usually leads to boot loops when installing roms. Also most devs here are using update scripts tailored for tenfars version
Q3: Since RSD is out of the picture for me, if for some reason I'm to soft brick my phone and can still get into Recovery mode, what .sbf do i flash, would it have to be the same one that was pushed to phones that if not already available on here will be really soon?
if you softbrick (other than the initial unlock soft brick where you just run oem unlock again) then depends on what you want to get to. CWM a rom.zip/fruitcake for the version you want would be ideal. If not then a fastboot version if available. I'd RSD the GB 4.5 with pudding sbf as a last resort.
StyleUkno said:
Ok Iv noticed that things are getting really really confusing around here with people saying one thing then someone else saying something else. I want to have a thread that is straight forward coming from people that know what they are talking about and not just assuming.
Now my phone has never had an unlocked bootloader. Before I updated to GB OTA i was on .83 rooted with all the mods added to it (webtop dock, blah, blah blah) I RSD back to .26 (that very old file) and just started doing OTA updates one by one once i logged in with my blurr account. I updated to GB via the official OTA update that was pushed to my phone when i selected to system update under settings.
I was able to Root this ATT OFFICIAL version pushed to my phone using This Pre-install method and that is all that i have done.
What i want to do now is Unlock the bootloader. From what i have read Pudding is the best way of doing this.
Q1: Does this method (Pudding) work with the Official ATT OTA version pushed to phones and not Kenns modded version, and is it the only way to unlock the bootloader?
If you use the pudding you will hard brick on the OTA (from what people have been saying)
Q2: Once unlocked what version of CWR do I install to be able to flash ROMs? Would i be able to just install ROM Manager and do the installation from there, Or possibly both ROM Manager and CWR?
Out of the picture becuase you cant unlock I think
Q3: Since RSD is out of the picture for me, if for some reason I'm to soft brick my phone and can still get into Recovery mode, what .sbf do i flash, would it have to be the same one that was pushed to phones that if not already available on here will be really soon?
Thanks for all the help if anyone helps out.
StyleUkno
Click to expand...
Click to collapse
asldkjghaa
I downloaded the hBoot upgrade RUU, everything goes fine then it tell's me I'm not updated to the latest version... xx.xxx.406(?).xxx even though I am when I go to phone settings. I even downgraded by RUU and did an OTA to make sure it was HTC official and not rooted. Any ideas?
That program never worked for me... If you are rooted you can get an unlocked bootloader by flashing a package found here
Thanks very much.. it's such a shame as I really wanted to see what HTC had to offer. I didn't even need it much I had a custom recovery before and could do anything from there I jsut wanted to try stock
My phone was rooted with CWM, but now is fully stock. I installed using the official RUU. Now, when I check for updates, it says there aren't any. Does this mean I just need to wait, or does it mean that something is not "right" about my phone? It is currently unlocked with s-off, but the 4.3 RUU installed without balking. Any suggestions for getting stock 4.4.3 with sense 5.5?
I did check T-Mobile's site and it looks like it was updated yesterday, but mentions nothing about the update. I wonder if they pulled the update.
Success. It was just a matter of time. This is the first time that checking for updates hasn't let me download as soon as the update was released with a T-Mobile HTC phone.
its a staged update not every phone will get the OTA immediately. just wait or manually flash.
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.