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?
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
Can get past Tmobiles tethering block? Also one that has gotten rid of the most bloatware that Tmobile puts on these phone? Looking for the basic apps that come with the phone and less crap that they put on these phones
All the custom roms on this forum will not have any of the bloatware that comes with the stock device.
And to fix the tethering issue, just create a new APN and set it to epc.tmobile.com, that should bypass the tethering/hotspot issue on T-Mobile.
nguyenkendy said:
All the custom roms on this forum will not have any of the bloatware that comes with the stock device.
And to fix the tethering issue, just create a new APN and set it to epc.tmobile.com, that should bypass the tethering/hotspot issue on T-Mobile.
Click to expand...
Click to collapse
Thanks for that info
Wow I thought there was a 1 step root process? Damn I feel like i am downloading so many things just to root my phone. Ive settled on the trickdriod version (NON Tmobile version) I cant seem to get the rom?
FenderGuy said:
Wow I thought there was a 1 step root process? Damn I feel like i am downloading so many things just to root my phone. Ive settled on the trickdriod version (NON Tmobile version) I cant seem to get the rom?
Click to expand...
Click to collapse
It takes like 10 minutes..and then download the ROM and flash it. Voila.
Ok finally unlocked my phone using the HTC method. Downloaded the Trickdriod Rom and tried to go into Recovery mode, but all I get is a screen with a red triangle and exclamation? Rebooted the phone, bootloader, same thing? What is going on? I know the phone is unlocked, because it says it, it just gets stuck in recovery mode...Any advice?
Did you flash a recovery? Doesn't look like it if you are getting android recovery.
Sent from my HTC VLE_U using xda app-developers app
I followed instructions to unlock the phone....download ROM and Tweak package...but no mention of flash recovery? Do you have a link?
Spastic909 said:
Did you flash a recovery? Doesn't look like it if you are getting android recovery.
Sent from my HTC VLE_U using xda app-developers app
Click to expand...
Click to collapse
Ok downloaded a img, flash recovery thru cmd , worked than it wont go into recovery to flash root access...no it says tampered above unlocked
FenderGuy said:
Ok downloaded a img, flash recovery thru cmd , worked than it wont go into recovery to flash root access...no it says tampered above unlocked
Click to expand...
Click to collapse
I'd just start over fresh.
Relock the bootloader
Go back to stock with a ruu install
Unlock bootloader
Flash custom recovery
Flash rom
Flash boot.img
I think that's the order you want to do things in but couldn't hurt to double check on a different guide.
mikeinaus said:
I'd just start over fresh.
Relock the bootloader
Go back to stock with a ruu install
Unlock bootloader
Flash custom recovery
Flash rom
Flash boot.img
I think that's the order you want to do things in but couldn't hurt to double check on a different guide.
Click to expand...
Click to collapse
Tampered means non-official software such as root, it is OK and you will always see it when using custom ROMs.
Might want to check the FAQs, have some basic useful info which will help understand some things too
http://forum.xda-developers.com/showpost.php?p=24884624&postcount=3
After unlocking bootloader on the steps on previous post, I would root the phone. Then flash the custom recovery.
Did you flash the boot.img with fastboot from the ROM you choose? You have to:
1- extract it from the rom you downloaded,
2- place it on your computer on the same folder than fastboot
3- boot into bootloader
4- select fastboot
5- on your PC on a command line run: fastboot flash boot boot.img
Let me know how it goes,
Diego
Ok I tried to redo it again and maybe I know what the issue is ...when I try to go into recovery mode ...It says Andriod development (S3) Do I have the issue phone? If so where is the download items for my phone?
Does anyone know if I have the 3s phone?
I believe so, check your processor speed. S3 I believe is 1.7 not 1.5 as S4 is
If that is the case you are limited to S3 roms. There are a couple. I didn't think S3's are in US--maybe wrong--
Not sure on all this except processor speeds
Good to see you here FenderGuy--think we crossed paths on the Nexus Forums--
rugmankc said:
I believe so, check your processor speed. S3 I believe is 1.7 not 1.5 as S4 is
If that is the case you are limited to S3 roms. There are a couple. I didn't think S3's are in US--maybe wrong--
Not sure on all this except processor speeds
Good to see you here FenderGuy--think we crossed paths on the Nexus Forums--
Click to expand...
Click to collapse
Yeah I think we did...No wonder the phone doesnt want to go into another ROM mode...
Not happy with the Tmobile Insurance or the service lately
My biggest problem with tmo in dayton oh is slow rollout of 42mb
If they don't have it it by March i am changing carriers--speeds are pitiful in doors here--
Hi,
I have this AT&T one x, (I m using on NON AT&T network), so cant have an ota update.
Looking at few forums, downloaded the OTA version on XDA (631 Mb)
Saw people writing, that just rename the file to update.zip and then go to recovery and choose install from internal memory.
That dint work for me.
Error: not able to mount sd mem
Then few people wrote to choose install from external mem.
That dint work either.
Error: not able to mount sd mem
Then saw few people saying that I need to root my device and unlock bootloader.
I dint that, and tried from bootlaoder to install from zip.
That also dint work.
Now saw, I few wrote that i need to be S - OFF.
Which I tried doing it, but i m not able to do s-off for myself.
Pls pls pls.... can any of you EXPERTs out here help me.
Waited like for AT&T to release the update, now when it is out, i m not able to make it through.
Your step by step instruction would be highly appreciable.
Be aware, that if you have the AT&T version, and you are rooted, then you probably have SuperCID (in fact, you must have SuperCID, unless it was already changed back). If you have SuperCID you must S-off (or return to the AT&T CID) before applying the OTA, or you will brick your phone!
I am not all that familiar with the process to install using OTA.zip (and haven't done it myself), but it was discussed in these threads:
http://forum.xda-developers.com/showthread.php?t=2180408
forum.xda-developers.com/showthread.php?t=1701460
redpoint73 said:
Be aware, that if you have the AT&T version, and you are rooted, then you probably have SuperCID (in fact, you must have SuperCID, unless it was already changed back). If you have SuperCID you must S-off (or return to the AT&T CID) before applying the OTA, or you will brick your phone!
I am not all that familiar with the process to install using OTA.zip (and haven't done it myself), but it was discussed in these threads:
http://forum.xda-developers.com/showthread.php?t=2180408
forum.xda-developers.com/showthread.php?t=1701460
Click to expand...
Click to collapse
How to S Off ATT HOX???
Thats the big question.
I have rooted my phone through one click TWRP Toolkit.
abhishek jain said:
How to S Off ATT HOX???
Thats the big question.
Click to expand...
Click to collapse
No, that is a very small question. Or at least a very easy one to answer.
Take 5 minutes to look around before asking "big" questions: http://forum.xda-developers.com/showthread.php?t=1671237
http://forum.xda-developers.com/showthread.php?t=2136172
If you would read my first post, I have already posted that I tried doing that was not able to do.
On the third comment that we need push in , where it given an error 92 or something like that, I dint got that.
Tried many times and then it became a "big" for me.
We all are born not experts in every field.
So before comenting pls try to know what's behind it
Sent from my HTC One X using xda app-developers app
Lol it doesn't take an expert to read and take five mins..this is probably one if the easiest s off methods you'll see for awhile... You probably didn't set up your adb fastboot environment up right
a box of kittens said:
Lol it doesn't take an expert to read and take five mins..this is probably one if the easiest s off methods you'll see for awhile... You probably didn't set up your adb fastboot environment up right
Click to expand...
Click to collapse
Changed my laptop and tried again.
Now I am S-OFF
THough I applied the same comments on three different machine.
4th Time it worked.
Now how to install this OTA updated which I have downlaoded
abhishek jain said:
Changed my laptop and tried again.
Now I am S-OFF
THough I applied the same comments on three different machine.
4th Time it worked.
Now how to install this OTA updated which I have downlaoded
Click to expand...
Click to collapse
Anyone to help me out in this case:
I am S OFF
Rooted
Unlocked bootloader
AT&T HOX on non AT&T network
631 mb update.zip
Looking top update
Rename file update.zip and copy to internal storage.
Reboot to bootloader and enter recovery.
Push power+ vol up when recovery screen appears to enter recovery dialog.
Ignore errors.
Select install from internal storage
Select update.zip
Phone will reboot a couple of times.
iElvis said:
Rename file update.zip and copy to internal storage.
Reboot to bootloader and enter recovery.
Push power+ vol up when recovery screen appears to enter recovery dialog.
Ignore errors.
Select install from internal storage
Select update.zip
Phone will reboot a couple of times.
Click to expand...
Click to collapse
I tried this method couple of time before : unlocking, rooting and S-off ing
In this case , do i need to relock my bootloader and stock recovery?
If yes, where can i find stock recovery, i have deleted it.
By "i deleted it" do you mean you installed a custom recovery? If so, yes you need to get stock recovery back on.
Only way I know of to reinstall stock recovery is to run the 2.20 ruu. Since you're s-off, you don't need to relock; just run it.
iElvis said:
By "i deleted it" do you mean you installed a custom recovery? If so, yes you need to get stock recovery back on.
Only way I know of to reinstall stock recovery is to run the 2.20 ruu. Since you're s-off, you don't need to relock; just run it.
Click to expand...
Click to collapse
I am not a techie but as far as i know, i have not installed a custom recovery.
I did TWRP tool kit, rooting and unlocking bootloader.
How can see if i am custom recovery or stock
abhishek jain said:
I am not a techie but as far as i know, i have not installed a custom recovery.
I did TWRP tool kit, rooting and unlocking bootloader.
How can see if i am custom recovery or stock
Click to expand...
Click to collapse
You probably have a custom recovery. Reboot to bootloader and select recovery and see what you get. If it's TWRP, you'll get a teamwin splash screen and then some options. Stock recovery will just show a screen with a green circle.
iElvis said:
You probably have a custom recovery. Reboot to bootloader and select recovery and see what you get. If it's TWRP, you'll get a teamwin splash screen and then some options. Stock recovery will just show a screen with a green circle.
Click to expand...
Click to collapse
Then I have custome recovery.
Could you gimme a link for stock recovery image
I do not know if one is available. I have never seen one posted. Running a ruu will put it back on.
iElvis said:
I do not know if one is available. I have never seen one posted. Running a ruu will put it back on.
Click to expand...
Click to collapse
Yes now i have got my phone updated with the OTA update
abhishek jain said:
Yes now i have got my phone updated with the OTA update
Click to expand...
Click to collapse
Please click "Thanks" if anyone in the thread helped you.
iElvis said:
Please click "Thanks" if anyone in the thread helped you.
Click to expand...
Click to collapse
I have already done that.
And now in case anyone needs help, i can help those people out.
Coz the method is simple, but it is not at all explained clearly in any of the threads.
It has come in bit and pieces.
I have noticed one thing.
That after installing the update and again unlockin the bootloader and rooting, I am not able to see "TAMPERED" being written in the boatloader.
Also, now when I am rooted and also have SU permission, I m not able to switch on my WiFi tether with the files mentioned in the thread
http://forum.xda-developers.com/showthread.php?t=1677261
The "TAMPERED" flag goes away when you're s-off and flash a new hboot.
I believe wifi tether is blocked on the new AT&T base. You can flash a custom rom on the 3.17 base and it should work.
Hey, I am picking up a used Cincinnati Bell one s from a friend later today. I know he unlocked or did something via the htc method but other then that I think it is s-on and not super cid (however I am not completely sure. I will know for sure when I get it today) I know the phone hasn't had the official JB update yet. When I get the phone later today I was wanting to get the official update so I can install the newer roms. I do know it has a JB rom on it now but he said it is having some issues and I would rather just update it officially and go from there.
What would be the best way to do this? I know a few months ago the friend I am getting it from restored his stock rom nandroid and tried to do the ota but it kept failing, I am assuming it is because of the unlocked bootloader but I dont know for sure.
What steps can I take to get the updated 3.14 kernel?
Thanks in advance.
aadrcw said:
Hey, I am picking up a used Cincinnati Bell one s from a friend later today. I know the phone has a unlocked bootloader via the htc method but other then that I think it is s-on and not super cid (however I am not completely sure. I will know for sure when I get it today) I know the phone hasn't had the official JB update yet. When I get the phone later today I was wanting to get the official update so I can install the newer roms. I do know it has a JB rom on it now but he said it is having some issues and I would rather just update it officially and go from there.
What would be the best way to do this? I know a few months ago the friend I am getting it from restored his stock rom nandroid and tried to do the ota but it kept failing, I am assuming it is because of the unlocked bootloader but I dont know for sure.
What steps can I take to get the updated 3.14 kernel?
Thanks in advance.
Click to expand...
Click to collapse
Not getting official update even when the ROM is stock can be due to
- Custom Recovery presence
- Root
- removal of any bloatware apps
- Unlocked bootloader (not sure, but should be relocked before update )
Never update with SuperCID, Brick is the result.
Sent from my Nexus 7 using Tapatalk HD
khan.orak said:
Not getting official update even when the ROM is stock can be due to
- Custom Recovery presence
- Root
- removal of any bloatware apps
- Unlocked bootloader (not sure, but should be relocked before update )
Never update with SuperCID, Brick is the result.
Sent from my Nexus 7 using Tapatalk HD
Click to expand...
Click to collapse
Alright, I'll be getting the phone here in about 3 hours or so, What would be the best way to remove the recovery, root and then lock the bootloader back? Sorry if this is a known thing, I am nbew to htc devices so Idk if there is some special way with them
aadrcw said:
Alright, I'll be getting the phone here in about 3 hours or so, What would be the best way to remove the recovery, root and then lock the bootloader back? Sorry if this is a known thing, I am nbew to htc devices so Idk if there is some special way with them
Click to expand...
Click to collapse
- Root removal: restore stock OS (from RUU/OTA/NANDROID)
- Custom Recovery removal: flash a stock recovery. (Via RUU or fastboot)
- locking bootloader: via fastboot
You will be needing HTC drivers (standalone or HTC sync), ADB+Fastboot files and from this folder adb+fastboot commands will be given.
Sent from my Nexus 7 using Tapatalk HD
khan.orak said:
- Root removal: restore stock OS (from RUU/OTA/NANDROID)
- Custom Recovery removal: flash a stock recovery. (Via RUU or fastboot)
- locking bootloader: via fastboot
You will be needing HTC drivers (standalone or HTC sync), ADB+Fastboot files and from this folder adb+fastboot commands will be given.
Sent from my Nexus 7 using Tapatalk HD
Click to expand...
Click to collapse
Alright, One more question, Will any stock recovery work or are they rom specific?
aadrcw said:
Alright, One more question, Will any stock recovery work or are they rom specific?
Click to expand...
Click to collapse
Stock/custom Recoveries are actually variant specific. If you have S4 version, download this.
And if you have S3 version, I don't have a recovery at hand but you can extract it from RUU/OTA files or simply ask for it in respective sections.
Sent from my Nexus 7 using Tapatalk HD