Related
I have tried everything under the sun, but I cannot get this thing to work. My phone will not find any recovery img I put on my SD card. No matter how new or old it may be. It is really frustrating. Can anyone help?
You're doing it wrong.
Take the recovery.img off your SD card and put it on your desktop. Then use fastboot to flash the recovery image.
Wait how do I use fastboot? I used a Mac to unlock my phone using htvdev.com's method.
My intentions are to also root my phone and install the new set Coindroid rom. Can I do that with my current setup? I couldn't use revolutionary because I own a Mac.
If you unlocked, then you know how to use fastboot!
To install the recovery you use
Code:
fastboot flash recovery recovery.img
Rusty! said:
If you unlocked, then you know how to use fastboot!
To install the recovery you use
Code:
fastboot flash recovery recovery.img
Click to expand...
Click to collapse
ok well what about install a custom ROM such as coindroid and rooting the phone? Do i follow the same steps every time?
Nope, once you've installed recovery, you just enter that and install the ROM/root files.
Ok which recovery would you recommend? I am mostly used to ClockworkMod, but does the touch interface ClockworkMod work for the Sensation 4g?
Yes it does, that's what I use. You can find it here: www.clockworkmod.com/rommanager
Rusty! said:
Yes it does, that's what I use. You can find it here: www.clockworkmod.com/rommanager
Click to expand...
Click to collapse
Ok.
And the code for that would be:
Code:
fastboot flash recovery (what I just downloaded?)
TO OP: Coindroid is an ICS ROM. All ICS roms require updated "ICS" firmware found in HTC's 3.32 software update. Here's the problem, you CAN'T update your firmware (except for stock TMobile versions) because you didn't s-off. HTC bootloader unlock does not give you s-off and only allows for flashing rom, recovery, and in a round about way kernel. You need to update your hboot and radio by updating firmware, which, as i said, you no longer can do. You are now stuck on gingerbread based ROMs until TMobile releases their version of the ICS update next month. If you flash an ICS ROM you will end up in a bootloop.
Behold_this said:
TO OP: Coindroid is an ICS ROM. All ICS roms require updated firmware. Here's the problem, you CAN'T update your firmware because you didn't s-off. HTC bootloader unlock does not give you s-off and only allows for flashing rom, recovery, and in a round about way kernel. You need to update your hboot and radio by updating firmware, which, as i said, you no longer can. You are now stuck on gingerbread until TMobile releases the ICS update next month. If you flash an ICS ROM you will end up in a bootloop.
Click to expand...
Click to collapse
hrm. Well if I root can I still get the update from T-Mobile? I want to remove the crap off of my phone. And then would it be wise to still install a recovery?
cashman0712 said:
hrm. Well if I root can I still get the update from T-Mobile? I want to remove the crap off of my phone. And then would it be wise to still install a recovery?
Click to expand...
Click to collapse
You would need full stock ROM to successfully install the update via OTA, meaning stock recovery and all system apps present.
**edit** I also added a little more info in my previous post, to give you a clearer understanding of what's happened.
Ok, So I only unlocked the bootloader via htcdev.com. Should I just leave my phone as is until the update then? And did the bootloader unlocker mess up my chances of getting the update?
I honestly don't know how HTC bootloader unlock may or may not effect OTA's, but I will say this, if you don't get the update or if you do and it causes problems with your device, you're on your own. Your warranty has been voided by the HTC unlock method and TMobile will not service the device so you will have to go through HTC which can cost $$$!
Behold_this said:
I honestly don't know how HTC bootloader unlock may or may not effect OTA's, but I will say this, if you don't get the update or if you do and it causes problems with your device, you're on your own. Your warranty has been voided by the HTC unlock method and TMobile will not service the device so you will have to go through HTC which can cost $$$!
Click to expand...
Click to collapse
Won't there be a way to update it even if I don't get updated through T-Mobile?
EDIT: Also couldn't I just relock it just in case?
There probably will be. In your case, your best hope is that the official RUU for the TMobile updated software gets leaked and posted. They usually do. Look for it in this thread. Probably won't be available until sometime after it's official release.
Behold_this said:
There probably will be. In your case, your best hope is that the official RUU for the TMobile updated software gets leaked and posted. They usually do. Look for it in this thread. Probably won't be available until sometime after it's official release.
Click to expand...
Click to collapse
Ok thanks for the help and tips!
Another quick question. Can't I just flash the GB Stock ROM and then update if I need to?
Hey folks,
I'm trying to return my AT&T HTC One XL to stock so I can upgrade using the official 1.85 OTA. I backed up via ADB this morning and planned on restoring to factory status, upgrading, and then replacing my data. I rooted but never unlocked the bootloader.
Can anyone point me to an official AT&T recovery image?
I was previously using the tutorial found here, but I believe that includes the One X recovery image and not the one for the One XL. So it doesn't work for me.
Just performing a factory reset from the GUI or the bootloader menu doesn't work either - the OTA update will download, but when it installs I get the red triangle with the exclamation point.
Any help would be greatly appreciated.
wormyrocks said:
Hey folks,
I'm trying to return my AT&T HTC One XL to stock so I can upgrade using the official 1.85 OTA. I backed up via ADB this morning and planned on restoring to factory status, upgrading, and then replacing my data.
Can anyone point me to an official AT&T recovery image?
I was previously using the tutorial found here, but I believe that includes the One X recovery image and not the one for the One XL. So it doesn't work for me.
Just performing a factory reset from the GUI or the bootloader menu doesn't work either.
Any help would be greatly appreciated.
Click to expand...
Click to collapse
would be easier to flash the 1.85 RUU in the dev section. You'll end up in the same place.
Just re-lock your bootlooder first if it's unlocked.
while in bootloader type fastboot oem lock.
Do you end up able to receive OTA updates with the RUU flashed?
wormyrocks said:
Do you end up able to receive OTA updates with the RUU flashed?
Click to expand...
Click to collapse
yes. and the 1.85 RUU is the exact same software that went out OTA.
Thanks - I'll give that a spin.
If it's not too much trouble, could someone extract and post the rom.zip?
My Windows partition is running XP and has about 1 GB free even after clearing out all of my unnecessary files.. not enough to install the USB drivers AND run the RUU. So I'd rather do it under Linux.
wormyrocks said:
If it's not too much trouble, could someone extract and post the rom.zip?
My Windows partition is running XP and has about 1 GB free even after clearing out all of my unnecessary files.. not enough to install the USB drivers AND run the RUU. So I'd rather do it under Linux.
Click to expand...
Click to collapse
there's a rooted de-odexed 1.85 flashable with CWM in the dev section
As tempting as that is, I would rather keep my bootloader untouched and my OS OTA-safe.
wormyrocks said:
As tempting as that is, I would rather keep my bootloader untouched and my OS OTA-safe.
Click to expand...
Click to collapse
ok then how about this, from linux install virtualbox and the free windows 8 developer preview.
Voila
gunnyman said:
would be easier to flash the 1.85 RUU in the dev section. You'll end up in the same place.
Just re-lock your bootlooder first if it's unlocked.
while in bootloader type fastboot oem lock.
Click to expand...
Click to collapse
He still wont have a recovery at this point, which is where i'm at.
Need some help from you rooted guys here
http://forum.xda-developers.com/showthread.php?t=1699379
Sent from my HTC One X using xda premium
I have an HTC One X updated to 4.0.4, software number 2.20.502.7 710RD. I messed up my phone trying to install a cyanogenmod 10 preview but messed up flashing a recovery. Long story short, it would not boot into the regular firmware and wouldn't let me get access anything but the bootloader menu, flashboot, and cwm recovery menu. I ended up using the ruu, htc_one_x_RUU_2.20.502.7_att_us_08022012. I heard that you can't root this new firmware unless you still have you unlock token id thing which i do. I tried running the same tool I used to root my phone before and it did unlock the bootloader but it didn't root it. It installed supersu but not the su binary. If someone would be willing to walk me though rooting my phone that would be great and if someone would be willing to link me to the most up to date clockwork mod recovery page that would be great. And if I misheard and it isn't possible to root at all right now then just say so and I'll shut up. Also all I want to do is install google now for ics on my phone, not flash a rom, because I heard that it wouldn't be safe to do that right now.
pizzalover2 said:
I have an HTC One X updated to 4.0.4, software number 2.20.502.7 710RD. I messed up my phone trying to install a cyanogenmod 10 preview but messed up flashing a recovery. Long story short, it would not boot into the regular firmware and wouldn't let me get access anything but the bootloader menu, flashboot, and cwm recovery menu. I ended up using the ruu, htc_one_x_RUU_2.20.502.7_att_us_08022012. I heard that you can't root this new firmware unless you still have you unlock token id thing which i do. I tried running the same tool I used to root my phone before and it did unlock the bootloader but it didn't root it. It installed supersu but not the su binary. If someone would be willing to walk me though rooting my phone that would be great and if someone would be willing to link me to the most up to date clockwork mod recovery page that would be great. And if I misheard and it isn't possible to root at all right now then just say so and I'll shut up. Also all I want to do is install google now for ics on my phone, not flash a rom, because I heard that it wouldn't be safe to do that right now.
Click to expand...
Click to collapse
You can't. There's a dozen threads right now stating that you cannot root on 2.20.
pizzalover2 said:
I have an HTC One X updated to 4.0.4, software number 2.20.502.7 710RD. I messed up my phone trying to install a cyanogenmod 10 preview but messed up flashing a recovery. Long story short, it would not boot into the regular firmware and wouldn't let me get access anything but the bootloader menu, flashboot, and cwm recovery menu. I ended up using the ruu, htc_one_x_RUU_2.20.502.7_att_us_08022012. I heard that you can't root this new firmware unless you still have you unlock token id thing which i do. I tried running the same tool I used to root my phone before and it did unlock the bootloader but it didn't root it. It installed supersu but not the su binary. If someone would be willing to walk me though rooting my phone that would be great and if someone would be willing to link me to the most up to date clockwork mod recovery page that would be great. And if I misheard and it isn't possible to root at all right now then just say so and I'll shut up. Also all I want to do is install google now for ics on my phone, not flash a rom, because I heard that it wouldn't be safe to do that right now.
Click to expand...
Click to collapse
Not safe to flash a rom? Of course it's safe. Just flash one and you'll have root. Otherwise stay on stock with no root.
Where did you hear that it wouldn't be safe to flash a rom?
Sent from my One X using xda app-developers app
XNine said:
You can't. There's a dozen threads right now stating that you cannot root on 2.20.
Click to expand...
Click to collapse
This is true but not in his case he was unlocked prior to update so he can unlock and root again.
To the op
Don't use cwm use twrp its officilay supported for the one x download goo manager from the market and install it from the app as far the root not working try the process again because it should work.
Edit
Open Su and try to update the binary.
Sent from my Nocturnalized Beast
---------- Post added at 12:48 AM ---------- Previous post was at 12:43 AM ----------
He can't just flash a rom with the new hboot you will need to flash the boot image from fastboot unless flashing a rom that is 2.20 or 2.23 base and even then he will.lose init.d support if he skips flashing the boot from fastboot
Sent from my Nocturnalized Beast
How to Root 4.04 w/ unlock token
Ok, this is what worked for me. First, make sure you have your bootloader unlocked with your unlock token. CIDspoofer will not give you root, but it will unlock your bootloader with the unlock token.
Next, go here http://theunlockr.com/2012/06/05/how-to-install-twrp-2-1-recovery-on-att-and-rogers-htc-one-x/ and download the twrp recovery image and flash it with adb running the commands in the instructions.
Get yourself the 4.04 stock rooted zip from here in the OP of this thread. Take your pick of ODEXED or DE-ODEXED. http://forum.xda-developers.com/showthread.php?t=1812459
Put zip on sd, reboot into recovery, flash the zip and you should be good to go. Stock, rooted update.
I hope this helps.
Ok, I am really excited now. Instead of flashing just a rooted version of the stock, would it be possible to flash to a jelly bean rom. If so how would i do that and which jelly bean rom is the most stable. I am really excited to use google now. I have flashed twrp and can flash the new firmware if i need but if I can get a jelly bean rom that would be preferable.
pizzalover2 said:
Ok, I am really excited now. Instead of flashing just a rooted version of the stock, would it be possible to flash to a jelly bean rom. If so how would i do that and which jelly bean rom is the most stable. I am really excited to use google now. I have flashed twrp and can flash the new firmware if i need but if I can get a jelly bean rom that would be preferable.
Click to expand...
Click to collapse
Just check the dev section. Whatever you find for Jellybean isn't going to be 100% since it's being worked on by the devs, and it's not official. If you don't care about camera and video not working, check out cyanogenmod 10 alpha in the original dev section.
pizzalover2 said:
Ok, I am really excited now. Instead of flashing just a rooted version of the stock, would it be possible to flash to a jelly bean rom. If so how would i do that and which jelly bean rom is the most stable. I am really excited to use google now. I have flashed twrp and can flash the new firmware if i need but if I can get a jelly bean rom that would be preferable.
Click to expand...
Click to collapse
You don't need Jellybean for Google Now anymore, there's a thread in general. You can just flash a .zip and get google now, that way you can get a really stable rom like cleanrom 4.5
Ruayly said:
Can anyone send me a link to root on 1.85 please
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
Dev section http://forum.xda-developers.com/showthread.php?t=1709424
SO I am sure I will get the barrage of no's but, of course I am dumb and have my HTCOX ATT stock at 2.20.502.7 never got a token at 1.85 and want to go Cyanagenmod 10 on my phone. Is there any way to revert firmware and then root using the 1.85 method? Or any other thoughts?
jackdforme said:
SO I am sure I will get the barrage of no's but, of course I am dumb and have my HTCOX ATT stock at 2.20.502.7 never got a token at 1.85 and want to go Cyanagenmod 10 on my phone. Is there any way to revert firmware and then root using the 1.85 method? Or any other thoughts?
Click to expand...
Click to collapse
Please search before posting things like this. There is at least I mean at least 10 threads about this. If you upgraded and did not change your cid or unlock your bootloader you are out of luck until a new exploit is found or s off is achieved.
Sent from my Nocturnalized Beast
Root 1.85
Ruayly said:
Can anyone send me a link to root on 1.85 please
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
http://www.xda-developers.com/xda-tv-2/how-to-root-the-htc-one-x-xda-tv/
http://forum.xda-developers.com/showthread.php?t=1577671
http://forum.xda-developers.com/showthread.php?t=1709424
Root 1.85
Ruayly said:
Can anyone send me a link to root on 1.85 please
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1678138
Hello Everyone,
As of today, my phone received the new OTA Update for my HTC One S. However, obviously I cannot update due to my phone being rooted. As a person who is still relatively new with rooting (about a month rooted with my phone-first time), I have a couple questions.
First and foremost, have you guys enjoyed the OTA Update so far? I have read about the list of improvements, and they look promising.
Secondly, I obviously want to stay rooted, are there any suggestions about how to update and then have my phone rooted? Preferably without losing my root, but I don't think that's possible.
Thirdly, I saw a thread about the viper (I believe that's what it's called) rom and that could be my possible solution. But, I am rooted on stock rom and have never put on another rom before. So what are your thoughts on this rom?
Thanks in advance
Sent from my HTC VLE_U using xda app-developers app
Problem Fixed
DrOfLife said:
Hello Everyone,
As of today, my phone received the new OTA Update for my HTC One S. However, obviously I cannot update due to my phone being rooted. As a person who is still relatively new with rooting (about a month rooted with my phone-first time), I have a couple questions.
First and foremost, have you guys enjoyed the OTA Update so far? I have read about the list of improvements, and they look promising.
Secondly, I obviously want to stay rooted, are there any suggestions about how to update and then have my phone rooted? Preferably without losing my root, but I don't think that's possible.
Thirdly, I saw a thread about the viper (I believe that's what it's called) rom and that could be my possible solution. But, I am rooted on stock rom and have never put on another rom before. So what are your thoughts on this rom?
Thanks in advance
Sent from my HTC VLE_U using xda app-developers app
Click to expand...
Click to collapse
Hey Dr.
I had the same issue and fixed it. I'm enjoying the OTA update...seems snappier and the option to change the menu button and get rid of that eyesore at the bottom of the screen is great....See this post on how to fix it:
http://forum.xda-developers.com/showthread.php?p=32069130
All you have to do is download the stock recovery (link located in the post above), rename it "Recovery.IMG" and put it in the /Data/Recoveries folder that your All In One Kit uses. Then open up the All In One root kit, flash the stock recovery, and reboot your phone. It should look the same, and give you the same notification that an update is available. Install the update, and then reflash your TWRP or CWM and reroot (the OTA unroots the device, so you need to reinstall SuperSu.
Thanks to all the people that have helped me do the same!!!
fsustrength said:
Hey Dr.
I had the same issue and fixed it. I'm enjoying the OTA update...seems snappier and the option to change the menu button and get rid of that eyesore at the bottom of the screen is great....See this post on how to fix it:
http://forum.xda-developers.com/showthread.php?p=32069130
All you have to do is download the stock recovery (link located in the post above), rename it "Recovery.IMG" and put it in the /Data/Recoveries folder that your All In One Kit uses. Then open up the All In One root kit, flash the stock recovery, and reboot your phone. It should look the same, and give you the same notification that an update is available. Install the update, and then reflash your TWRP or CWM and reroot (the OTA unroots the device, so you need to reinstall SuperSu.
Thanks to all the people that have helped me do the same!!!
Click to expand...
Click to collapse
I keep flashing the stock recovery with all-in-one and then downloading and installing the update. Everytime, about halfway it goes back to the red triangle with the exclamation point and restarts the phone five minutes later.
I check software and its still 4.0.3 and the update redownloads. I've tried several "stock recoveries" and the update afterwards... never works.
TheAdictsPunk said:
I keep flashing the stock recovery with all-in-one and then downloading and installing the update. Everytime, about halfway it goes back to the red triangle with the exclamation point and restarts the phone five minutes later.
I check software and its still 4.0.3 and the update redownloads. I've tried several "stock recoveries" and the update afterwards... never works.
Click to expand...
Click to collapse
I have also tried the steps and have run into the same problem. All is well when I flash into recovery, but when the phone starts updating about quarter or half-way through it also gives me the same red error message and the phone restarts soon after with no update. I have tried several times with the same problem.
However, thanks fsustrength for the instructions, before I was getting no where, but now I almost got it
Sent from my HTC VLE_U using xda app-developers app
ckpv5 said:
As there are many questions on how to do OTA update & to revert to stock after a device is rooted and bootloader unlocked; I made this simple guide which I hope will help the newbies especially.
NOTE : always do a backup and a nandroid backup before trying any of these.
OTA update:
A) ROM is stock, bootloader unlocked, stock recovery and not rooted.
- just run the OTA update, there is no need to relock the bootloader
B) ROM is stock, bootloader unlocked, CWM recovery and not rooted.
- flash the stock recovery that comes with your RUU, extract the RUU for the stock recovery.
* boot to bootloader
* fastboot flash recovery recovery_signed.img
* fastboot reboot-bootloader
* fastboot erase cache
* fastboot reboot
- run the OTA update
C) ROM is stock, bootloader unlocked, stock recovery and rooted
- download OTA Rootkeeper from Play Store
- run the OTA Rootkeeper and click protect root
- run the OTA update, there is no need to relock bootloader
- Once done, run OTA Rootkeeper and click restore root
D) ROM is stock, bootloader unlocked, CWM recovery and rooted
- download OTA Rootkeeper from Play Store
- run the OTA Rootkeeper and click protect root
- no need to relock bootloader
- boot to bootloader and fastboot flash the stock recovery
- run the OTA update
- Once done, run OTA Rootkeeper and click restore root
E) ROM is custom, bootloader unlocked, CWM recovery and rooted and you have a stock nandroid backup
- flash the stock boot.img if after nandroid restore, you have a bootloop
- flash the stock recovery.img
- relock the bootloader - fastboot oem lock
- boot your device and run the OTA update
F) ROM is custom, bootloader unlocked, CWM recovery and rooted and you don't have a stock nandroid backup
- if you dont have the stock nandroid backup, you need to run RUU
- before you can run the RUU you need to:
* flash the stock recovery.img
* flash the stock boot.img (maybe no need)
* relock the bootloader - fastboot oem lock
* run RUU
- run device setup
- run the OTA update
Flashing RUU to revert to stock or to update your One V after you have a custom ROM installed.
- you must have the correct RUU for your device.
- if you are not sure, download CID Getter from Play Store and run it, it will show your CID.
- with your CID, you may be able to find a correct RUU for your device
then (even though some people may not agree with this, but this will bring no harm and it is noob-proof) do this:
1- flash a stock recovery.img
fastboot flash recovery recovery_signed.img
fastboot reboot-bootloader
fastboot erase cache
2- flash a stock boot.img
fastboot flash boot boot_signed.img
fastboot reboot-bootloader
fastboot erase cache
3- re-lock bootloader
fastboot oem lock
fastboot reboot-bootloader
fastboot erase cache
4- flash RUU
Note : for people with ERROR 155 UNKNOWN ERROR they need to go into HBOOT and select FASTBOOT and run the RUU to revert to stock (thanks Lloir)
And usually:
Error 155 - usually wrong recovery.img /wrong boot.img
Error 140 - wrong bootloader / bootloader unlocked
Error 131 - wrong RUU for your device
Credit to all XDA members that posted all the guides in various forum thread and some from own experience which I compiled here for easy reference.
Click to expand...
Click to collapse
Some wonderful person wrote a guide for the One V. Every though it's not the same phone the rules are the same. If these instructions help you click the link and thank the guy for writing it.
http://forum.xda-developers.com/showpost.php?p=27288357&postcount=1
Wow, that is a very useful guide right there! However, while reading the guide, Step D is exactly what both TheAdictsPunk and I seem to have done (I'm making an assumption that he did). I did in fact have and used the root keeper app, put it on temporary unroot, and flashed the stock rom and ran the update. Yet, I still run into the problem of the red error sign. I'm sure there is a factor that maybe could cause it to stop, but I cannot put a finger on it.
However, I did notice something while following the procedures of the guide on my phone. When I flash the stock rom on my phone, I have to re-download the system update. While downloading the system update I notice that some of my apps get root permissions from SuperSu in the background, even though in root keeper I temporarily took off root. Rootkeeper also states that my phone is unrooted. Could this problem cause the red error message? If so, any way to fix it?
Sent from my HTC VLE_U using xda app-developers app
DrOfLife said:
Wow, that is a very useful guide right there! However, while reading the guide, Step D is exactly what both TheAdictsPunk and I seem to have done (I'm making an assumption that he did).
Sent from my HTC VLE_U using xda app-developers app
Click to expand...
Click to collapse
I did! Last night I even tried flashing the recovery image through fastboot instead of the all-in-one kit. Then, even, the recovery image wouldn't flash all the way through... maybe our phones are having a problem with the recovery being reflashed and not the update at all.
I had the same exact issue. I finally got fed up and just flashed the RUU with my computer and then just used the All-in-one program to re-root. I am now enjoying 2.31 and really glad I updated. Obviously the RUU wipes everything, but I had done a full backup using Titanium Backup, and then restored all the important settings and data (like accounts, wifi list, bookmarks, dictionary, etc.) (but not the system apps themselves! ) and it worked out pretty well. Still had some things to adjust, like sounds and such. If you want to keep your SMS's use the built-in backup in the messaging app, then restore after the update.. more reliable than any other app I've tried.
mmceorange said:
I had the same exact issue. I finally got fed up and just flashed the RUU with my computer and then just used the All-in-one program to re-root. I am now enjoying 2.31 and really glad I updated. Obviously the RUU wipes everything, but I had done a full backup using Titanium Backup, and then restored all the important settings and data (like accounts, wifi list, bookmarks, dictionary, etc.) (but not the system apps themselves! ) and it worked out pretty well. Still had some things to adjust, like sounds and such. If you want to keep your SMS's use the built-in backup in the messaging app, then restore after the update.. more reliable than any other app I've tried.
Click to expand...
Click to collapse
I'm strongly considering doing that, I can back all my contacts and apps and sms messages via Mobile Go. So, wiping my phone isn't too big of an issue for me because I can restore almost everything I need back on my phone. If you don't mind me asking, where did you get the source that you got the RUU? Also, I have never flashed an ruu before so is their a guide for our phone to flash a RUU?
Sent from my HTC VLE_U using xda app-developers app
DrOfLife said:
I'm strongly considering doing that, I can back all my contacts and apps and sms messages via Mobile Go. So, wiping my phone isn't too big of an issue for me because I can restore almost everything I need back on my phone. If you don't mind me asking, where did you get the source that you got the RUU? Also, I have never flashed an ruu before so is their a guide for our phone to flash a RUU?
Sent from my HTC VLE_U using xda app-developers app
Click to expand...
Click to collapse
http://www.lastnite.de/RUU_Ville_U_ICS_40_S_HTC_Europe_2.31.401.5.exe
Links to downloads are on that page.. just copy/paste.
Basically start your phone in fastboot, connect to usb, then run the ruu with admin privileges. Make sure you are on stock recovery, and already have the USB drivers installed on your PC (unless you're on Linux.. already has them.. and maybe Mac too?)
mmceorange said:
http://www.lastnite.de/RUU_Ville_U_ICS_40_S_HTC_Europe_2.31.401.5.exe
Links to downloads are on that page.. just copy/paste.
Basically start your phone in fastboot, connect to usb, then run the ruu with admin privileges. Make sure you are on stock recovery, and already have the USB drivers installed on your PC (unless you're on Linux.. already has them.. and maybe Mac too?)
Click to expand...
Click to collapse
Well I followed all your steps, and all was going well until I ran across RUU error 130, which states that it was using the incorrect RUU. I looked into it and I found that it was the Europe version, and I have the T-Mobile version of my phone. I'm assuming that this is the issue, am I right? Does the RUU in Europe different than the T-Mobile USA one? If so, are there any RUU's out there that cover my phone? I have searched for them with no luck..
Sent from my HTC VLE_U using xda app-developers app
DrOfLife said:
Well I followed all your steps, and all was going well until I ran across RUU error 130, which states that it was using the incorrect RUU. I looked into it and I found that it was the Europe version, and I have the T-Mobile version of my phone. I'm assuming that this is the issue, am I right? Does the RUU in Europe different than the T-Mobile USA one? If so, are there any RUU's out there that cover my phone? I have searched for them with no luck..
Click to expand...
Click to collapse
Ok I figured out a couple answers to my questions. One, the Europe version and the T-Mobile Version are different. That explains why the RUU did not work and gave me Error 130. However, the T-Mobile RUU, RUU_Ville_U_TMOUS_1.84.531.2_R2_Radio_0.16.31501S, is the alternate version that also recieves the OTA update. The RUU is found here http://androidforums.com/one-s-all-things-root/560329-ruu-download-mirrors.html
Then, following the steps, I have successfully updated my phone to the newer softeware!
But of course, I run into another problem.... The CWM recovery does not work for my phone. I flashed the recovery via the HTC One S All-in-One Toolkit. But when getting my phone into recovery mode, it "crashes." (By crashes I mean the phone will go into the htc developmental screen, then turn to black, then reload the normal bootup screen and boot normally up) So, I don't have CWM and I'm unable to root my phone again because I don't have CWM to flash SuperSu. Any thoughts on this?
Rerooting
DrOfLife said:
So, I don't have CWM and I'm unable to root my phone again because I don't have CWM to flash SuperSu. Any thoughts on this?
Click to expand...
Click to collapse
I'm still running stock 1.84, but I'm rooted and unlocked. I do not have any kind recovery like CWM or TWRP. You may have to flash a stock recovery image in order to re-install the recovery of your choice. If you want to get rooted again try this method: http://forum.xda-developers.com/showthread.php?t=1577831 It's what I used to gain root. It's a rather easy to follow guide. I used this instead of the AIO kit.
I'm going to try and revert to locked and unroot in order to get the update. Wish me luck.
DrOfLife said:
Well I followed all your steps, and all was going well until I ran across RUU error 130, which states that it was using the incorrect RUU. I looked into it and I found that it was the Europe version, and I have the T-Mobile version of my phone. I'm assuming that this is the issue, am I right? Does the RUU in Europe different than the T-Mobile USA one? If so, are there any RUU's out there that cover my phone? I have searched for them with no luck..
Sent from my HTC VLE_U using xda app-developers app
Click to expand...
Click to collapse
Oh lol sorry about that.
DrOfLife said:
Ok I figured out a couple answers to my questions. One, the Europe version and the T-Mobile Version are different. That explains why the RUU did not work and gave me Error 130. However, the T-Mobile RUU, RUU_Ville_U_TMOUS_1.84.531.2_R2_Radio_0.16.31501S, is the alternate version that also recieves the OTA update. The RUU is found here http://androidforums.com/one-s-all-things-root/560329-ruu-download-mirrors.html
Then, following the steps, I have successfully updated my phone to the newer softeware!
Click to expand...
Click to collapse
Awesome!
DrOfLife said:
But of course, I run into another problem.... The CWM recovery does not work for my phone. I flashed the recovery via the HTC One S All-in-One Toolkit. But when getting my phone into recovery mode, it "crashes." (By crashes I mean the phone will go into the htc developmental screen, then turn to black, then reload the normal bootup screen and boot normally up) So, I don't have CWM and I'm unable to root my phone again because I don't have CWM to flash SuperSu. Any thoughts on this?
Click to expand...
Click to collapse
I personally have never encountered that before, so I am of little help here. The suggestion above me sounds like the right direction though.
Red triangle error
dc211 said:
Some wonderful person wrote a guide for the One V. Every though it's not the same phone the rules are the same. If these instructions help you click the link and thank the guy for writing it.
http://forum.xda-developers.com/showpost.php?p=27288357&postcount=1
Click to expand...
Click to collapse
I'm using method C, i still get that red triangle error. Also i can't get the ruu for my phone. I'm desperate can you please help me.
lonegunman0 said:
I'm using method C, i still get that red triangle error. Also i can't get the ruu for my phone. I'm desperate can you please help me.
Click to expand...
Click to collapse
Im getting the same thing. Even after flashing "stock recovery" that i got from the modaco link, I can't update or even go into the stock recovery...I would absolutely love to enjoy the update too!
skidmarc11 said:
Im getting the same thing. Even after flashing "stock recovery" that i got from the modaco link, I can't update or even go into the stock recovery...I would absolutely love to enjoy the update too!
Click to expand...
Click to collapse
If this many people are running into this problem, maybe we can get a role call of whose using what method, if not stock ROM what custom they are using, and what carrier they us?
I'm stock ROM, Stock Recovery, and Tmobile US. I used Method C.
I'm wondering if they have changed the update in a way that is preventing some people from updating. like it detects a certain file before update or something idk. I'm not any sort of advanced android user so I am probably wrong, but it's the first thing that comes to mind. Otherwise, maybe they sent out a bad update file, but I feel like that probably wouldn't be the case since it's been happening for a couple days now.
Thought's ideas anyone, or am I alone in any of these thoughts?
Stock rom
mylegiscramped said:
If this many people are running into this problem, maybe we can get a role call of whose using what method, if not stock ROM what custom they are using, and what carrier they us?
I'm stock ROM, Stock Recovery, and Tmobile US. I used Method C.
I'm wondering if they have changed the update in a way that is preventing some people from updating. like it detects a certain file before update or something idk. I'm not any sort of advanced android user so I am probably wrong, but it's the first thing that comes to mind. Otherwise, maybe they sent out a bad update file, but I feel like that probably wouldn't be the case since it's been happening for a couple days now.
Thought's ideas anyone, or am I alone in any of these thoughts?
Click to expand...
Click to collapse
skidmarc11 said:
Im getting the same thing. Even after flashing "stock recovery" that i got from the modaco link, I can't update or even go into the stock recovery...I would absolutely love to enjoy the update too!
Click to expand...
Click to collapse
Yes i agree about the file detection. I'm running stock rom but i think i've just realised my problem. Although i have a stock rom my problem is that the stock rom i'm running is deodexed. I read somewhere that if the stock rom is tweaked in any way or if any bloatware is deleted you can't get OTA updates.
Hope this helped
Wouldn't an RUU fix any of those problems?
Yes it would
Sent from my HTC One S using xda app-developers app
[RUU] [OTA] T-Mobile US Android 4.3 OTA (3.24.531.3) w/ Nandroid, Firmware & Radio
T-Mobile USA OTA to Android 4.3 Jelly Bean
Build: 3.24.531.3
Android 4.3, Sense 5.0
* includes Wi-Fi Calling​
This is the actual OTA Zip file that is downloaded and then flashed during the update process. I saw that T-Mobile's instructions tell users they must check through their phone, and are not providing a download link.
I extracted it off of my phone's SD Card before I updated, so it is untouched, it comes as T-Mobile distributed it.
DISCLAIMER
I am sharing this so everyone can have access to the official OTA. What you do with it from here is not my responsibility, nor do I care. Enjoy. I am not claiming ownership, nor am I claiming this will be much help by itself.
Update 10/23
The community has spoken, and this has brought a lot of stock options for the end user. As of 10/23 (today), we now have the OTA, a full Nandroid TWRP backup, two versions of the firmware, the radio only and now the RUU itself. The OP has been fully updated with links and credits to everything. Thank you to the Android community, this thread is a pretty great example of open source and people coming together with end products. Thanks for all the help here as well.
DOWNLOADS
RUU
3.24.531.3 T-Mobile RUU: http://forum.xda-developers.com/showthread.php?p=46756958
* thanks to Behold_this
OTA
*UPDATED 10/21 8PM*
My DropBox Link: https://db.tt/MWAGXkFc
Mirror Link: http://www.mediafire.com/?xjwbggpj5pw0l1l
* thanks to Mikey
NANDROIDS
TWRP Backup, No Root: http://forum.xda-developers.com/showpost.php?p=46695324&postcount=50
* thanks to Mikey
FIRMWARE
FIRMWARE (slim): http://forum.xda-developers.com/showpost.php?p=46691733&postcount=30
* does not include: boot.img, recovery.img or hboot.img
* thanks HTC_Phone
FIRMWARE + HBOOT: http://forum.xda-developers.com/showpost.php?p=46694631&postcount=43
* contains modded hboot without red warning text
* thanks to HTC_Phone
RADIO
RADIO: http://forum.xda-developers.com/showpost.php?p=46684321&postcount=339
* flashable radio only zip can be found here
* thanks to Mikey
Thanks for the link
Just removed the radio from this update and made it into a flashable zip........
http://forum.xda-developers.com/showpost.php?p=46684321&postcount=339
Mikey said:
Just removed the radio from this update and made it into a flashable zip........
http://forum.xda-developers.com/showpost.php?p=46684321&postcount=339
Click to expand...
Click to collapse
Any chance you can mirror the OTA? Dropbox terminated the OPs link
frettfreak said:
Any chance you can mirror the OTA? Dropbox terminated the OPs link
Click to expand...
Click to collapse
Uploading it now.......give me a couple minutes
TJD319 said:
T-Mobile USA OTA to Android 4.3 Jelly Bean
Build: 3.24.531.3
Android 4.3, Sense 5.0
* includes Wi-Fi Calling​
This is the actual OTA Zip file that is downloaded and then flashed during the update process. I saw that T-Mobile's instructions tell users they must check through their phone, and are not providing a download link. I am just sharing this with the community for developmental purposes. Hopefully, this may bring Wi-Fi Calling addons to ROMs like ViperOne and others I'm sure.
I extracted it off of my phone's SD Card before I updated, so it is untouched, it comes as T-Mobile distributed it.
DropBox Link: https://db.tt/MWAGXkFc
Click to expand...
Click to collapse
So after hours of searching through the forums, I just wanted to clarify a couple of questions.
I have S-Off and unlocked bootloader but Stock Rom - NOT rooted and stock recovery. I also have the original MID/CID - 0713000 / T-MOB010.
I can still get the latest OTA - 3.24.531.3? The only requirement for the OTA is CID/ MID, stock recovery and stock ROM, correct?
Also, If I go ahead update it, My HBOOT will be updated to 1.54 and Bootloader will be locked but I still will retain s-OFF, correct?
And the only way in future to flash a custom ROM is via, htcdev bootloader unlock?
Thank You!!
Mikey said:
Just removed the radio from this update and made it into a flashable zip........
http://forum.xda-developers.com/showpost.php?p=46684321&postcount=339
Click to expand...
Click to collapse
f_v_man said:
So after hours of searching through the forums, I just wanted to clarify a couple of questions.
I have S-Off and unlocked bootloader but Stock Rom - NOT rooted and stock recovery. I also have the original MID/CID - 0713000 / T-MOB010.
I can still get the latest OTA - 3.24.531.3? The only requirement for the OTA is CID/ MID, stock recovery and stock ROM, correct?
Also, If I go ahead update it, My HBOOT will be updated to 1.54 and Bootloader will be locked but I still will retain s-OFF, correct?
And the only way in future to flash a custom ROM is via, htcdev bootloader unlock?
Thank You!!
Click to expand...
Click to collapse
I am pretty sure you need to relock the bootloader, and have stock recovery. AFAIK those are the requirements. HBOOT may be 1.55 as that is the latest but you SHOULD still keep s-off. But i make no promises. lol But yes, you will have to go to HTCDEV and get your unlock key again if you wantt o flash another rom (its a really easy process though)
TJD319 said:
T-Mobile USA OTA to Android 4.3 Jelly Bean
Build: 3.24.531.3
Android 4.3, Sense 5.0
* includes Wi-Fi Calling​
This is the actual OTA Zip file that is downloaded and then flashed during the update process. I saw that T-Mobile's instructions tell users they must check through their phone, and are not providing a download link. I am just sharing this with the community for developmental purposes. Hopefully, this may bring Wi-Fi Calling addons to ROMs like ViperOne and others I'm sure.
I extracted it off of my phone's SD Card before I updated, so it is untouched, it comes as T-Mobile distributed it.
DropBox Link: https://db.tt/MWAGXkFc
Click to expand...
Click to collapse
Anyways to get a nandroid or to pull /system on an installed update.
I'm currently on a custom 4.2.2 ROM with Firmware 2.24.401.1, HBOOT 1.54, S-OFF, Super CID, and TWRP 2.6 bootloader on T-Mobile HTC One.
What is the process to upgrade to this OTA? Or is there a better to go to latest base, firmware, etc.?
Mikey said:
Uploading it now.......give me a couple minutes
Click to expand...
Click to collapse
Here you go
http://www.mediafire.com/download/xjwbggpj5pw0l1l/OTA_M7_UL_JB43_SENSE50_MR_TMOUS_3.24.531.3-1.27.531.11_release_337024c11bis4e2ha8yy5i.zip
I was on a rooted stock TMo ROM in order to get the update. However, i kept my Bootloader unlocked S-OFF, and I was rooted. Only thing really required is the stock odexed 4.1.2 ROM and the Stoxk boot and Recovery. SOFF doesnt matter, for me it didnt.
I was on Viper 4.2.2. I restored a nandroid of my stock 4.1.2 rooted, and all I then did was flash TMO stock recovery in fastboot.
Sent from my HTC One using XDA Premium 4 mobile app
TJD319 said:
I was on a rooted stock TMo ROM in order to get the update. However, i kept my Bootloader unlocked S-OFF, and I was rooted. Only thing really required is the stock odexed 4.1.2 ROM and the Stoxk boot and Recovery. SOFF doesnt matter, for me it didnt.
I was on Viper 4.2.2. I restored a nandroid of my stock 4.1.2 rooted, and all I then did was flash TMO stock recovery in fastboot.
Sent from my HTC One using XDA Premium 4 mobile app
Click to expand...
Click to collapse
The OTA doesn't help developers, they need the patched APK's after the OTA is installed.
SmiLey497 said:
The OTA doesn't help developers, they need the patched APK's after the OTA is installed.
Click to expand...
Click to collapse
I was answering someone's question about if they need the bootloader relocked or not.
As far as the devs go, now they've got the OTA and can do whatever they or anyone else wants with it. Its not really a crime to share.
Sent from my HTC One using XDA Premium 4 mobile app
Thanks for the upload. Question, to flash this, its just like flashing a firmware update, with the silver HTC on the screen? Pushed through ADB?
Rob
cvseuy said:
I'm currently on a custom 4.2.2 ROM with Firmware 2.24.401.1, HBOOT 1.54, S-OFF, Super CID, and TWRP 2.6 bootloader on T-Mobile HTC One.
What is the process to upgrade to this OTA? Or is there a better to go to latest base, firmware, etc.?
Click to expand...
Click to collapse
1. Restore nandroid backup for stock 4.1.2
2. Make sure boot.img and recovery.img are from stock T-Mobile.
3. Get OTA
OR
Download and install the stock T-Mobile ODEX ROM. Flash the ROM, doesnt matter if its rooted or not. Make sure it has stock recovery and boot images. And you can get OTA.
Sent from my HTC One using XDA Premium 4 mobile app
TJD319 said:
I was answering someone's question about if they need the bootloader relocked or not.
As far as the devs go, now they've got the OTA and can do whatever they or anyone else wants with it. Its not really a crime to share.
Sent from my HTC One using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Said by a developer
"ota is just a patch, patches the existing files, with new code, there isn't a whole apk there. is useless unless you have a phone to apply patch on and then pull system"
that's why I was asking. No ROM can include stuff like Wi-Fi calling without the patched APK's.
i noticed this is a higher build number compared to the att 4.3 version
SmiLey497 said:
Said by a developer
"ota is just a patch, patches the existing files, with new code, there isn't a whole apk there. is useless unless you have a phone to apply patch on and then pull system"
that's why I was asking. No ROM can include stuff like Wi-Fi calling without the patched APK's.
Click to expand...
Click to collapse
Once again, i completely get this and for someone who wants to provide a full system dump would be great. But im not wiping yet, so i cant do that. Also, the OTA file contains an encrypted firmware.zip file which is completely independent of the patched apks. That's why Mikey posted the Radio. This is the whole reason I gave it to the community.
Anyway, im done. Im not trying to argue about some stupid OTA. If you don't want it, then don't download it.
Sent from my HTC One using XDA Premium 4 mobile app
So, I noticed a problem on 4.3 when trying to boot a recovery in fastboot. According to the following thread, Android 4.3 bootloader has changed the function of this fastboot command:
Code:
fastboot boot recovery_twrp.img
Reference URL of same solved issue on N4: http://forum.xda-developers.com/showthread.php?t=2380675
Now, we have to retrigger the command somehow inputting the right information in. When i ran the regular command, it says downloading ...OK and goes through the regular steps, but the phone hangs on the bootloader screen.
It never actually loads the custom recovery, just completely freezes the bootloader. I tried a couple different recoveries (CWM, TWRP) and they just don't do anything except lock up the phone.
I want to preserve my stock partitions and make a backup. I plan to go back to my 4.1.2 and perform the update, then load it and wipe so i can provide the stock nandroid backup for full throttle development. So if anyone knows the current command to boot a custom recovery in fastboot on 4.3, let me know.
Sent from my HTC One using XDA Premium 4 mobile app
TJD319 said:
So, I noticed a problem on 4.3 when trying to boot a recovery in fastboot. According to the following thread, Android 4.3 bootloader has changed the function of this fastboot command:
Code:
fastboot boot recovery_twrp.img
Reference URL of same solved issue on N4: http://forum.xda-developers.com/showthread.php?t=2380675
Now, we have to retrigger the command somehow inputting the right information in. When i ran the regular command, it says downloading ...OK and goes through the regular steps, but the phone hangs on the bootloader screen.
It never actually loads the custom recovery, just completely freezes the bootloader. I tried a couple different recoveries (CWM, TWRP) and they just don't do anything except lock up the phone.
I want to preserve my stock partitions and make a backup. I plan to go back to my 4.1.2 and perform the update, then load it and wipe so i can provide the stock nandroid backup for full throttle development. So if anyone knows the current command to boot a custom recovery in fastboot on 4.3, let me know.
Sent from my HTC One using XDA Premium 4 mobile app
Click to expand...
Click to collapse
You ran this one correct,
Code:
fastboot -c "lge.kcal=0|0|0|x" boot twrp.img
because that's the only solution I've seen so far, I'll try to look further.