Related
Hello XDA members
I was wondering, when the new android sandwich comes out, and you got a rooted and S-off HTC sensation. But not custom rom. What will happen to the root and S-off when you update to the new android sandwich?
Thanks
Want to know too ahehhe
We'll lose root but keep S-OFF I'd imagine
Cool, thanks for the answer
I have perm-rooted my Sensation and i was wondering when the new official update from HTC comes out will i be able to install it automatically like when i was not rooted or because i am S-Off it will not let me?
Thanks
i could be wrong but no you wont be able to perform an ota update. im only saying this because the last ota update failed because the update looks for the stock recovery in order to update the system. seeing that you are rooted i assume you have cwm installed and if this ota update does indeed look for the stock recovery than it will fail. the only way around this is to either instal a stock ruu and lose root or instal the stock recovery and again lose root. either way you are gonna lose root.
Could you give me a link where there is a guide to install the stock recovery?
TheStigx said:
Could you give me a link where there is a guide to install the stock recovery?
Click to expand...
Click to collapse
If you check the development forum, there's a thread which has shipped roms in it. Flash one to restore stock recovery.
Panagiotis. said:
I have perm-rooted my Sensation and i was wondering when the new official update from HTC comes out will i be able to install it automatically like when i was not rooted or because i am S-Off it will not let me?
Thanks
Click to expand...
Click to collapse
Depends. If you're just running the original rom which came on your phone but rooted, it should still allow ota updates, but you'll lose root (but keep s-off). If you're on a custom rom you won't receive an ota.
To OP, if you ran an ruu or ota of ice cream sandwich, as eddy says, you'll lose root but remain s-off. That said, a custom ics rom will probably come out weeks/months before an official HTC update
Well, when we got the RUU, we can extract and repack to our rooted ROM
It should be this if i am right ? http://forum.xda-developers.com/showthread.php?t=1074559
satanevil said:
Well, when we got the RUU, we can extract and repack to our rooted ROM
Click to expand...
Click to collapse
That's true, but we'll see aosp ics roms long before we have sense skinned ones, as cyanogen et al don't need to spend months porting frameworks.
TheStigx said:
It should be this if i am right ? http://forum.xda-developers.com/showthread.php?t=1074559
Click to expand...
Click to collapse
That's the one
BTaylor927 said:
Depends. If you're just running the original rom which came on your phone but rooted, it should still allow ota updates, but you'll lose root (but keep s-off). If you're on a custom rom you won't receive an ota.
Click to expand...
Click to collapse
Yes I am running the stock rom so I will receive the pta update. I know that I will lose root in every scenario if I install the stock ROM one way or another.
Thanks.
Sent from my HTC Sensation Z710e using Tapatalk
So i just flash one of these roms, without deleting cache or doing a reset ?
not entirely true. i was rooted on stock rom when the last ota rolled out. i tried installing it but it failed. i did a lil search here and found a few people mentioned that it failed due to cwm and they also mentioned that you should try flashing back the stock recovery. i tried that and it installed successfully. easy way to get the stock recovery is to instal the correct ruu of your rom. but as we all know it wipes out everything off your phone. i did find this guide which the stigx has asked for (sorry buddy didnt see you there ) which shows you how to extracted the stock recovery off of the ruu and than flash it back to your phone.
check here: http://forum.xda-developers.com/showthread.php?t=1228648
Divine flaw said:
not entirely true. i was rooted on stock rom when the last ota rolled out. i tried installing it but it failed. i did a lil search here and found a few people mentioned that it failed due to cwm and they also mentioned that you should try flashing back the stock recovery. i tried that and it installed successfully. easy way to get the stock recovery is to instal the correct ruu of your rom. but as we all know it wipes out everything off your phone. i did find this guide which the stigx has asked for (sorry buddy didnt see you there ) which shows you how to extracted the stock recovery off of the ruu and than flash it back to your phone.
check here: http://forum.xda-developers.com/showthread.php?t=1228648
Click to expand...
Click to collapse
But if I need to follow your guide i have to have the OTA update file,w hich haven't comet out yet. What do i Do? It seems so hard to remove root and custom recovery :'(
But thank for your answer !
well the general idea is to get your stock recovery back without losin your data. so really all you need to do is flash your stock recovery reboot your phone and check for updates. if updates are available: system>about phone>check for updates, download the update and install. it shouldnt fail cause you have stock recovery instead of cwm. in short just do the top part of the guide and skip the rest cause you dont have the updates file on your computer.
So if i do step 1-12 I will have normal phone? Just like I started or do i still keep root?
Thank you so much for your hep !
TheStigx said:
Could you give me a link where there is a guide to install the stock recovery?
Click to expand...
Click to collapse
You can also use this software to install the stock recovery. that way you don't loose settings by installing RUU
TheStigx said:
So if i do step 1-12 I will have normal phone? Just like I started or do i still keep root?
Thank you so much for your hep !
Click to expand...
Click to collapse
yes you do 1-12 but you keep root. the only difference is that you will no longer have cwm for flashing, back up, and all other goodies. but once you run the ota and it installs you lose root.
but have a look at the link frederikh just posted. seems alot better than the current method. im reading over it now
Thanks for the answers!
I think i will go with the link frederikh gave me But God bless you Divine! Thank you for your help !
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
Hey Everyone!
I've been trying to fix this problem for hours with no luck, and while I've found solutions that have worked for others I can't find one that is specific enough to my situation.
So I just got an HTC One X that is locked to Rogers today from Kijiji, and I love it - great phone. The thing I didn't like was the hoard of stock apps that took up about four pages on the app drawer, so I thought hey, I'll root it and delete them. I didn't have any intention of using any custom ROMs, just wanted superuser permission to delete stock apps. Unlocking went fine (finding the token and what not using the app I found on here), and the rooting seemed to go alright until it turned off and didn't start again. I pulled out the cable from the computer and now things are weird..
I can sometimes get into the hboot, but when I try to just start the phone normally it goes to the HTC splash screen and has red writing telling me "this build is for development purposes only", etc etc. I really wanted to get rid of those stock apps but at this point I just want my phone working again. Am I screwed?
I CANNOT find the RUU that I need ANYWHERE. I've tried flashing both Clockwork Recovery and TWRP, and both are apparently successfully installed, but neither will open for me. This is seriously pushing me towards an iPhone
Thanks in advance.
oot-n-aboot said:
Hey Everyone!
I've been trying to fix this problem for hours with no luck, and while I've found solutions that have worked for others I can't find one that is specific enough to my situation.
So I just got an HTC One X that is locked to Rogers today from Kijiji, and I love it - great phone. The thing I didn't like was the hoard of stock apps that took up about four pages on the app drawer, so I thought hey, I'll root it and delete them. I didn't have any intention of using any custom ROMs, just wanted superuser permission to delete stock apps. Unlocking went fine (finding the token and what not using the app I found on here), and the rooting seemed to go alright until it turned off and didn't start again. I pulled out the cable from the computer and now things are weird..
I can sometimes get into the hboot, but when I try to just start the phone normally it goes to the HTC splash screen and has red writing telling me "this build is for development purposes only", etc etc. I really wanted to get rid of those stock apps but at this point I just want my phone working again. Am I screwed?
I CANNOT find the RUU that I need ANYWHERE. I've tried flashing both Clockwork Recovery and TWRP, and both are apparently successfully installed, but neither will open for me. This is seriously pushing me towards an iPhone
Thanks in advance.
Click to expand...
Click to collapse
Yes, please get an iphone! Redpoint73 resource compilation thread, linked in my signature, has all the RUUs and OTAs you would ever need. Good luck.
Sweet, I found the right RUU but it's a zip file and I'm not able to get into recovery mode on my phone. I can get into hboot but rebooting to recovery from there just shows the HTC splash screen with the "developer only" message" then shuts off again. I've tried installing both Clockwork and TWRP with no luck. Any ideas?
exad said:
Yes, please get an iphone! Redpoint73 resource compilation thread, linked in my signature, has all the RUUs and OTAs you would ever need. Good luck.
Click to expand...
Click to collapse
oot-n-aboot said:
Sweet, I found the right RUU but it's a zip file and I'm not able to get into recovery mode on my phone. I can get into hboot but rebooting to recovery from there just shows the HTC splash screen with the "developer only" message" then shuts off again. I've tried installing both Clockwork and TWRP with no luck. Any ideas?
Click to expand...
Click to collapse
The zip file is an OTA and not an RUU. You would need to extract the recovery from that zip file (may be burried deep). Will be called recovery.img or recovery_signed.img or something to that effect. Fastboot flash recovery recoveryfilename.img then boot to that recovery then install the zip through the phone's stock recovery.
I really appreciate the help but I still can't seem to find the proper RUU. I've tried a few and they all fail. If it helps, the number I get when I typed getvar version-main is: 3.17.631.2
Would someone be able to link me to a download for this particular RUU? Thanks
Edit: Thought I'd update a bit of what I've done. Ive found the one I should need in the list you've provided, but there is no link for download. There is the OTA file but not the RUU. I've been using ARUWizard to try to install the RUU, but any one I've tried so far just says it's not the right one. No other error messages, it just tells me to find the appropriate ROM. I can't understand why this is so difficult to find the right one! It seems like all the other models are readily available. Thanks again!
(This looks like the one, but no download link:
3.17.631.2
File Timestamp: 04/12/12
Publically Seen: 08/01/13
Android: 4.1.1
Kernel: 3.4.10-g240d4d5
hboot: 2.14.0000
radio: 0.23a.32.09.29_10.128.32.34
adsp: 31.1.0.45.0815
wcnss: 1031145
tp_syn3202: 3.2_PR1293981
tz: 001.138.010
sbl1: 001.138.003
sbl2: 001.138.004
sbl3: 001.138.005
OTA: OTA_EVITA_UL_JB_45_S_Rogers_WWE_3.17.631.2_0.23a.3 2.09.29_10.128.32.34a_release_299850qstr7rxdbfuofl 6j.zip (full)
RUU: N/A
Source: evitaul-jb-crc-3.4.10-240d4d5.zip
exad said:
The zip file is an OTA and not an RUU. You would need to extract the recovery from that zip file (may be burried deep). Will be called recovery.img or recovery_signed.img or something to that effect. Fastboot flash recovery recoveryfilename.img then boot to that recovery then install the zip through the phone's stock recovery.
Click to expand...
Click to collapse
Rogers did not release an ruu for that software version. Proceed with the ota the way I explained in my last post or s-off if you want to run the ruu for the older software version.
Sent from my One X using xda app-developers app
For some reason flashing stock recovery doesn't work for me. It says it is successful but when I try to boot to recovery it just goes right back to hboot or sits on the HTC splash screen. I can install TWRP though. Do you know of a nandroid backup for my phone? cid is Roger001
exad said:
Rogers did not release an ruu for that software version. Proceed with the ota the way I explained in my last post or s-off if you want to run the ruu for the older software version.
Sent from my One X using xda app-developers app
Click to expand...
Click to collapse
oot-n-aboot said:
For some reason flashing stock recovery doesn't work for me. It says it is successful but when I try to boot to recovery it just goes right back to hboot or sits on the HTC splash screen. I can install TWRP though. Do you know of a nandroid backup for my phone? cid is Roger001
Click to expand...
Click to collapse
Fastboot erase cache
Sent from my HTC One X using xda premium
31ken31 said:
Fastboot erase cache
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Try that. Nandroid will not restore your recovery. Only the ROM/kernel/radio files and settings.
I have tried that but unfortunately still can't get into stock recovery. It just goes to the HTC splash and shuts off after a couple of seconds. I know I have the right OTA so if I can get into stock recovery I shouldn't have a problem. Any other suggestions? Am I downloading the wrong version of the recovery?
exad said:
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Try that. Nandroid will not restore your recovery. Only the ROM/kernel/radio files and settings.
Click to expand...
Click to collapse
oot-n-aboot said:
I have tried that but unfortunately still can't get into stock recovery. It just goes to the HTC splash and shuts off after a couple of seconds. I know I have the right OTA so if I can get into stock recovery I shouldn't have a problem. Any other suggestions? Am I downloading the wrong version of the recovery?
Click to expand...
Click to collapse
Extract the recovery from the OTA Zip file. It will be in there somewhere. I have done this myself so I know it works.
exad said:
Extract the recovery from the OTA Zip file. It will be in there somewhere. I have done this myself so I know it works.
Click to expand...
Click to collapse
I have as well and worked like a charm
Sent from my HTC One X using xda premium
Sorry, I forgot to mention, if you are not S-OFF, you need to relock after flashing stock recovery and doing fastboot erase cache.
Hey guys, sorry for the late reply, it was a busy long weekend. Here's where I'm at now. I've managed to install cyanogenmod, which booted up fine and everything looked great, but the touch screen didn't work. After some searching I found it it is because the firmware is too new or something, and to downgrade the touch firmware I would have to S-OFF, which would require me to superCID... and I don't know what any of that is and I'd really just like to get back to stock anyway, so..
I've done what you said. Taken the "recovery.img" out of the OTA file for my phone. I've flashed the recovery, relocked the bootloader and erased the cache. Upon booting to recovery it will either splash the HTC screen then go to a black screen (I used to think it was powering off but it looks like it is on but just not displaying anything). Sometimes it will show a image of a phone with a red exclamation mark with a triangle around it.
I feel like I've royally screwed up this phone and I'd just like to get it back to stock.
Thanks!
Edit: The internet is telling me hold volume up + power to get to recovery from the red triangle, but it just reboots me into the bootloader.
exad said:
Sorry, I forgot to mention, if you are not S-OFF, you need to relock after flashing stock recovery and doing fastboot erase cache.
Click to expand...
Click to collapse
You just need to get into stock recovery. Then you can install that ota zip file. I remember having a hard time getting into it too. I would reflash stock recovery to try to remember how I got to the flash screen but my motherboard is out on rma.
Sent from my Sony Tablet S using xda app-developers app
Just posting in case other people have my problem:
I didn't fix it myself, but a friend did for me. He said it wasn't rooted properly so he basically started from scratch and redid that part of it. There is no RUU file for my phone, but he used to AT&T version and it seems to have worked perfectly. Nothing I've noticed so far has any problems.
Anyway, thanks for all the help guys!
exad said:
You just need to get into stock recovery. Then you can install that ota zip file. I remember having a hard time getting into it too. I would reflash stock recovery to try to remember how I got to the flash screen but my motherboard is out on rma.
Sent from my Sony Tablet S using xda app-developers app
Click to expand...
Click to collapse
oot-n-aboot said:
Just posting in case other people have my problem:
I didn't fix it myself, but a friend did for me. He said it wasn't rooted properly so he basically started from scratch and redid that part of it. There is no RUU file for my phone, but he used to AT&T version and it seems to have worked perfectly. Nothing I've noticed so far has any problems.
Anyway, thanks for all the help guys!
Click to expand...
Click to collapse
Since your friend fixed the issue for you what firmware are you now now. Is it still rooted?
Looks like I have Android version 4.1.1, HTC Sense 4+, and using CleanROM 6.5.0. Is that what you were wondering?
Also, SuperUser is enabled in SuperSU, so that means I'm rooted right?
takylo said:
Since your friend fixed the issue for you what firmware are you now now. Is it still rooted?
Click to expand...
Click to collapse
Hi All,
I know this might sound like a redundant topic to you all (since there are many discussions about this on here) but after having gone to MANY threads on forums, MANY different websites and trying MANY different things to correct this, to no avail, i'm still stuck!!! :crying:
I am on Evita...running:
S-ON
HBoot-1.14.0002
Radio-0.19as.32.09.11_2
OpenDSP-v29.1.0.45.0622
eMMC-boot
AT&T Stock RUU 2.20
I've relocked the device, flashed stock RUU (via fastboot), erased the cache, factory reset, wiping from TWRP recovery.....NOTHING is working!
All the phone does is boot to the "HTC quietly brilliant" screen, hang for a few moments then restart.
Any help someone can provide, would be greatly appreciated! This is my kid's phone and he's bugging about wanting to get it back. Thanks!:good:
Start with rooting step first.....http://forum.xda-developers.com/showthread.php?t=1952038
And for further guide.... http://forum.xda-developers.com/showthread.php?t=1671237
Swyped from T3DRO1CS RedHoXence
Hang on. You'll need to provide more information, saying you've tried many things could mean anything. What exactly have you tried with this phone? I'm assuming it has been unlocked and rooted in the past? Does it have SuperCID?
Also, you said you flashed an RUU via fastboot, but an RUU is an exe file which runs by itself so flashing via fastboot isn't correct. Where did you get this alleged RUU and how did you run it?
@ted77usa
Just wait a minute, we need to properly identify what has been done to this device before going any further.
Sent from my Evita
timmaaa said:
Hang on. You'll need to provide more information, saying you've tried many things could mean anything. What exactly have you tried with this phone? I'm assuming it has been unlocked and rooted in the past? Does it have SuperCID?
Also, you said you flashed an RUU via fastboot, but an RUU is an exe file which runs by itself so flashing via fastboot isn't correct. Where did you get this alleged RUU and how did you run it?
@ted77usa
Just wait a minute, we need to properly identify what has been done to this device before going any further.
Sent from my Evita
Click to expand...
Click to collapse
Thanks so much for taking your time to reply, guys.
Sorry, I didn't give full details. Yes, the phone has been rooted, unlocked and running CM10.1 fine for several months. All of a sudden, it got into this weird bootloop. So, I tried doing some of the tricks that people have posted about relocking the bootloader and flashing the stock rom via fastboot. That didn't work so I tried running the RUU...that didn't work. I went back in and tried a factory reset from the bootloader...nothing. I did a erase cache from fastboot and fastboot flashing the boot.img...still doing it. I went into TWRP recovery and wiping Delvik, Cache and Factory Reset....again, still stuck in bootloop.
Sorry to be lengthy but I'm trying to retrace as many steps as possible for you guys.
Ok, just to be clear, you ran the full RUU exe file?
Sent from my Evita
Stupid question.....
I just had a thought. I have the same exact HOX as my son. It's rooted, unlocked and running same CM10.1 rom as his was and it's running fine. Could I try backing up from my phone's clean nandroid file? So, it ends up just acting as a mirror of my phone?
Yes, you can create a backup on your son's phone using TWRP, copy the backup to a pc, copy it to your phone, and restore the backup. Being that you're s-on though you'll need to manually flash the boot.img from that ROM using fastboot. Do you still have a copy of the ROM zip?
Sent from my Evita
timmaaa said:
Yes, you can create a backup on your son's phone using TWRP, copy the backup to a pc, copy it to your phone, and restore the backup. Being that you're s-on though you'll need to manually flash the boot.img from that ROM using fastboot. Do you still have a copy of the ROM zip?
Sent from my Evita
Click to expand...
Click to collapse
Yes, I do. I always keep a copy of the rom on my phone for emergencies. Now, the other question is, my phone is running 1.85. The messed up phone is running 2.20 (both S-ON). Will it not work or...coming from a nandroid backup, does that not matter? Never tried doing a mirror before...
The firmware version that either phone is on won't make a difference as the backup tool can't touch that partition.
Sent from my Evita
timmaaa said:
The firmware version that either phone is on won't make a difference as the backup tool can't touch that partition.
Sent from my Evita
Click to expand...
Click to collapse
So, I need to just make sure the phone is back to being rooted, unlocked and running TWRP, then mount it and load the nandroid to the SD card. Should I do backup from fastboot or TWRP?
Do you think it will throw it out of that bootloop? I've spent two days on this and I'm ready to be done!
Add long as you have TWRP installed it should work just fine. You have to do the backup using the backup tool in TWRP. When you create the backup on your son's phone you will find it on the sd card at TWRP/backups/serial number, you need to put it in the same file tree on your sd card.
Whether or not it's going to solve your problem I'm not sure, but anything is worth a shot.
Sent from my Evita
timmaaa said:
Add long as you have TWRP installed it should work just fine. You have to do the backup using the backup tool in TWRP. When you create the backup on your son's phone you will find it on the sd card at TWRP/backups/serial number, you need to put it in the same file tree on your sd card.
Whether or not it's going to solve your problem I'm not sure, but anything is worth a shot.
Sent from my Evita
Click to expand...
Click to collapse
Thanks, well..here goes nothing. I will report back the progress! I really appreciate the time for your advice. :good:
It's no problem at all, I'm always happy to help someone get their phone back on track.
Sent from my Evita
timmaaa said:
It's no problem at all, I'm always happy to help someone get their phone back on track.
Sent from my Evita
Click to expand...
Click to collapse
Well, I've got the phone loading into TWRP 2.5.0.0 and when I try to do a wipe Delvik, Cache and Factory Reset...it's telling me it can't find the SD Card.
"E: Unable to mount '/sdcard'
E: Unable to mount storage"
Phone says it's still CID: 11111111
Bootloader: Unlocked.
Any clue how to get the phone to read/write to the SD Card so I can back up to a nandroid?
Did you mention doing a factory reset from bootloader? If so, you'd corrupted the sd card and you'll need to format it using Windows before you can use it. Also, you'll need to flash TWRP 2.6 because 2.5 is full of bugs.
Sent from my Evita
timmaaa said:
Did you mention doing a factory reset from bootloader? If so, you'd corrupted the sd card and you'll need to format it using Windows before you can use it. Also, you'll need to flash TWRP 2.6 because 2.5 is full of bugs.
Sent from my Evita
Click to expand...
Click to collapse
I did! Thanks for remembering. :good:
Any special way I should format the sd card when I do it on Windows? Thanks for the tip on 2.6!
It should come up as fat32 as the default, if not just make sure you format it to fat32 and that's it. It'll probably take twenty minutes or so.
Sent from my Evita
timmaaa said:
It should come up as fat32 as the default, if not just make sure you format it to fat32 and that's it. It'll probably take twenty minutes or so.
Sent from my Evita
Click to expand...
Click to collapse
Got it! Flashed 2.6 in getting ready to back up from my phone's nandroid. Fingers crossed!:fingers-crossed:
After I back up from my nandroid in TWRP, should I flash the boot.img from fastboot?
Yes you'll need to flash the boot.img afterwards, good luck.
Sent from my Evita
timmaaa said:
Yes you'll need to flash the boot.img afterwards, good luck.
Sent from my Evita
Click to expand...
Click to collapse
How can I get it to see my nandroid backup? I have it installed inside the TWRP folder just like it would be on my phone but when I go to Restore, it shows nothing on my sd card. wtf?? I think I'm getting one step closer and another hurdle arrises!! ugh...
Thanks for your help btw, timmaaa!! :good:
I just rooted and s-off'ed. I flashed a rom without making a backing first in twrp. Is there a stock rom or RUU? Also if i flash a RUU with s-off will i lose it? thanks
Here is a cwm backup posted earlier.
http://forum.xda-developers.com/showthread.php?t=2714438
how do u install it? the last post on the thread you gave said to unzip it? where do i put it?
thanks so much
I just figured it out. It cant be flashed as a zip because its a nandroid backup and clockwork mod keeps its backups under data/media/.
Also found this mod here that can fix the red txt problem! obviously going to be seen by verizon if brought in for warranty. you can also use a
Faux Locked hboot and make it look locked with s-on and its NOT! pretty cool! Would really like to ses a stock RUU tho.
http://forum.xda-developers.com/showthread.php?t=2710503
Paulb787 said:
I just figured it out. It cant be flashed as a zip because its a nandroid backup and clockwork mod keeps its backups under data/media/.
Also found this mod here that can fix the red txt problem! obviously going to be seen by verizon if brought in for warranty. you can also use a
Faux Locked hboot and make it look locked with s-on and its NOT! pretty cool! Would really like to ses a stock RUU tho.
http://forum.xda-developers.com/showthread.php?t=2710503
Click to expand...
Click to collapse
Did you have any luck with this file? I got it into CWM recovery and the MD5 didn't match. I'm currently stuck with a phone that can't make or receive calls...very hopeful though
Paulb787 said:
I just rooted and s-off'ed. I flashed a rom without making a backing first in twrp. Is there a stock rom or RUU? Also if i flash a RUU with s-off will i lose it? thanks
Click to expand...
Click to collapse
Ruu.....An if that don't work I have another way to get you going. Try the link first....post back if it worked.
http://forum.xda-developers.com/showthread.php?t=2727831
Sent from my HTC6525LVW using XDA Premium 4 mobile app