Related
Alright, so I got this phone a week ago. First off, I am loving it. Screw Apple.
Anyway, first thing I wanted to do was root it so I can debloat all of T-Mobile's poop applications they cram inside of it.
I've read places that HBOOT 1.45.0013 isn't rootable. I've read it IS rootable, but only with S-OFF on a previous HBOOT. And I've read that it is rootable, but you can't get S-OFF after root.
I've used HTC's unlock tool, which went successful because I flashed CWM through fastboot. I've tried HTC Supertool, MrRoot, and Revolutionary (which says it isn't compatible)
My question then is, which of the above statements is true? If it is rootable, I don't care about S-OFF too much. But I can't ever find a guide that tells me how to root it with this current HBOOT.
Halp pl0x? <3
If you download the Superuser zip (just google superuser android or something), you can flash it in recovery to get root. Alternatively, download a ROM with root preloaded (DS-mod is essentially stock with root and a few other standard root things added in) and flash it.
Limewirelord said:
If you download the Superuser zip (just google superuser android or something), you can flash it in recovery to get root. Alternatively, download a ROM with root preloaded (DS-mod is essentially stock with root and a few other standard root things added in) and flash it.
Click to expand...
Click to collapse
What's the difference in flashing Superuser, and downloading it from the Market?
Sent from my myTouch_4G_Slide using xda premium
It won't install correctly if you do it while the system is on and live (through the market) you have to do it while the operating system is not running (through clockworkmod)
Afterwards, it's fine to update through the market, but the initial install will fail if done on a running version of Android.
Blue6IX said:
It won't install correctly if you do it while the system is on and live (through the market) you have to do it while the operating system is not running (through clockworkmod)
Afterwards, it's fine to update through the market, but the initial install will fail if done on a running version of Android.
Click to expand...
Click to collapse
..Huh, just flashed Superuser. Weird that it's that easy. All the other threads were like "omg HBOOT 1.45.0013 can't be rooted hnnnnnggg"
So, now onto ROMs, are there any ICS based ones you reccomend?
Btw I see tht your question has been answered but in Mr Root's next update will include a Rooter/Unrooter for the newest H-Boot (Without S-Off)
MewTech said:
..Huh, just flashed Superuser. Weird that it's that easy. All the other threads were like "omg HBOOT 1.45.0013 can't be rooted hnnnnnggg"
So, now onto ROMs, are there any ICS based ones you reccomend?
Click to expand...
Click to collapse
For a while it was so - you couldn't do anything with 1.45.0013, HTC broke the OTA so you couldn't unlock it.
In my quest for s-on to s-off (still ongoing) I found a leaked copy of the OTA as a signed HTC package so now we can actually unlock them, and people can work with them and they are now rootable.
Still stuck with s-on though, which is unfortunate - we're working on it and hopefully can crack it soon. Got some leads we're chasing down, each layer we unravel shows us another that has to be solved below it.
ICS? Dunno - i'm not interested in ICS yet, still trying to learn gingerbread through and through (i'm an android newbie) before moving up to ICS. That's on hold right now because of the s-on issue i'm working on. tbalden has been leading the charge on ICS and I would recommend looking into his works if that is your interest.
Limewirelord said:
If you download the Superuser zip (just google superuser android or something), you can flash it in recovery to get root. Alternatively, download a ROM with root preloaded (DS-mod is essentially stock with root and a few other standard root things added in) and flash it.
Click to expand...
Click to collapse
can you explain in detail how to flash it to rom?????
Using CWM to flash it, you will need the super user ZIP file. Find it somewhere (it's everywhere, no doubt) and put it on your SD card. Reboot the phone to recovery mode, and using CWM recovery, select "flash any zip from SD card" (I'd look up the exact wording, except that my phone has been running a solid 24 days without reboot and I really wanna see how long it goes). Navigate to where your super user ZIP file is, and select it. Follow prompts, et voila, root on reboot.
Assuming all works. If something didn't work, you messed up. Try again from step 1, make sure you have a zip file and not an APK file, make sure you select the correct "flash zip" option (there are two, one specifically for update.zip and another for whatever zip you choose).
HIH
ok this is my huge problem i have the same hboot with s-on
i have the full stock stupid t-mobile mt4gs AOS 2.3.4 software# 1.55.531.3 and i DONT have CWM or any of the extras in only thing i succeeded is getting the bootloader unlocked so what should i do?
Install clockworkmod then flash either superuser pr a ROM - if staying stocl with root, be a good time to do some spring cleaning on all the junk it comes with pre-installed.
Blue6IX said:
Install clockworkmod then flash either superuser pr a ROM - if staying stocl with root, be a good time to do some spring cleaning on all the junk it comes with pre-installed.
Click to expand...
Click to collapse
ok i download this now i try flash CWM recovery and i get this
an error occurred while attempting to run privileged commands!
??????
what do i do next??
We love to title our posts here
crimedave1987 said:
ok i download this now i try flash CWM recovery and i get this
an error occurred while attempting to run privileged commands!
??????
what do i do next??
Click to expand...
Click to collapse
Well,
What exactly did you do that returned this error (mainly because I don't remember if fastboot or adb returns that)? What tutorial/guide were you following? Were you in adb trying to "dd" the CWM recovery image or were you trying to flash an img file from within fastboot? Either way, what was the exact command you typed?
Your other thread (sorry, didn't realize I had replied to you in two different places) received an answer as well. After looking around to get the info you need for this post, I see now you've posted in quite a few threads to which I'm subscribed (guess I just never noticed the name, sorry).
So I see you have an unlocked bootloader. At this point, yes, flash CWM. Blue6ix gave an excellent post on how to do this. Is this the one you are currently trying to follow in order to install CWM?
tried to use superuser
I tried to load the superuser zip file in recovery with cwm. installation aborted. any suggestions? I have mytouch4gslide with s on unlocked with HBoot 1.45.0013
wesomatic said:
I tried to load the superuser zip file in recovery with cwm. installation aborted. any suggestion? I have mytouch4g with s on unlocked with HBoot 1.45.0013
Click to expand...
Click to collapse
From my earlier post:
cj chitwood said:
Using CWM to flash it, you will need the super user ZIP file. Find it somewhere (it's everywhere, no doubt) and put it on your SD card. Reboot the phone to recovery mode, and using CWM recovery, select "flash any zip from SD Card”. Navigate to where your super user ZIP file is, and select it. Follow prompts, et voila, root on reboot.
Assuming all works. If something didn't work, you messed up. Try again from step 1, make sure you have a zip file and not an APK file, make sure you select the correct "flash zip" option (there are two, one specifically for update.zip and another for whatever zip you choose).
HIH
Click to expand...
Click to collapse
Did this help? Only things I can think of are (1) using ”flash update.zip” instead of ”flash [any] zip file” or, less likely, (2) trying to flash an apk instead of a zip.
--
Sent from my Android ”phone”:
HTC DoubleShot /T-Mobile MyTouch 4G Slide running Bulletproof
Yes, that thread did help me. I used your instructions. I even have a new sd card. I have read some threads about formating it first. I did not do that. Also where can I get a good zip file? I down loaded it from some file sharing program 2share I think... Tried again ROOTED!!!! It was so easy!!! Been doing this for a week!!! Wow!!!!!!!!!!!!!!!!!!!
bricked my phone!!!
Just want to add... Do not use ROM Manager from The Market. Bricked my phone. Just stays in start up. Had it rooted and everything!!!!
NO BRICK
Thank God For CWM!!!!!
I am stuck someplace in betweem
Hi:
I too have a MyTouch Slidwe 4G with the hboot 1.45.0013. All the contrary information I have found lead me to go to the professionals. I purchased the root-android.org software. It seemed to run fine - I got no errors and it said that the phone was rooted. I see the superuser app on the phone. However, when I try to run Titanium Backup, it says that the phone is not rooted. The people at root-android.org are not answering my emails (I did get my money back). Any ideas of where I should go from here?
Thanks!
You should never have to purchase root for any android, if it has been done once then chances are it is plastered how to all over the internet, if the phone has a thread on xda then it will be there. Being you got yourself this far I'll help you out a bit more
http://forum.xda-developers.com/showthread.php?p=29439712
Read and understand is my advice, always read until you understand, then search if you have questions, then finally ask questions here if you are still stumped.
For the most part every question you can ask is already answered by one of the super helpful xda folk here, and chances are it is the right information.
I do advice to gain radio soff with the wire trick, it will make life easier... Read up and happy flashing!
Sent from my Nexus 7 using xda premium
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
...then again, I might just be being a complete moron and absolutely wasting a lot of people's time. I'm going to try anyway because everytime I Google my multiple problems I seem to get back to this website. Yes, I watched your noob video - I laughed a lot, and unfortunately and unintentionally I feel like I'm going to tick a few of the boxes at the end of it... If you can rescue me from my situation, I'll definitely make a donation towards the upkeep of your site (As long as you have a donation link.)
I have a HTC Sensation XE (with Beats Audio) and it being a Sunday afternoon I thought I would have a crack at rooting and applying custom firmware to me phone for the first ever time. I bet you can see where this is going. I downloaded the SDK Manager, HTC ONE X All In One tool, and the latest Cyanogen for my handset. I DID NOT S-OFF MY PHONE BEFORE JUMPING RIGHT IN FOR I AM AN IDIOT. So I rooted the phone, and all seemed to be going well, I had the Stock ROM, I believe they call it? But it was rooted as confirmed by Root Checker. AT THIS POINT I BACKED UP USING CLOCKWORK. I then got ahead of myself and tried to download the new Custom ROM. After getting aggrieved that the ROM was stuck on 86% consistently with ROM Manager I downloaded it to my PC. Put it onto my SD card. Went into recovery mode. Installed .zip via SD card.
This is where problems began. Once the installation was done I restarted my phone and got caught out by the little blue man, and I believe my screen was stuck in bootloop, where it just continually showed me his image - and the movements around him kept occurring, it didn't freeze. I tried to put the boot.img on from the .zip where I had downloaded it but it came to no avail, it still didn't boot past that point.
I was aggrieved and so restored my phone to the point I said I had backed up. Just after the root of the stock ROM. Then when I tried to boot this up, it got stuck at the Beats Audio symbol in similar vein to how it was stuck on the little blue man.
I turned my phone off, tried to wipe everything using 4ext recovery that I placed on the phone at this point. My All In One tool also stopped recognising my phone, constantly saying "error: device not found" when I tried to do something which it was not doing before the root. Furthermore, when I plug my phone into my PC, it doesn't offer me Removable Drive storage, but it does make the pinging noise which notifies me that the device is recognised. Now after all this, when I boot the phone it is stuck at the HTC screen with a white background and I don't know why it is now halting here as opposed to what it was earlier, could it be something to do with when I was trying to get the all-in-one tool to recognise my phone I tried to reflash recovery of 'Stock'? I really am upset about this and regret even attempting it as I am in love with my phone and can't really live without it. Please help and if I get a successfully, rooted phone I will be very happy and PROMISE to make a donation towards the site of what I can afford.
So please do me and your own site a favour and help me
BRIEF POINTS OF NOTE
ROOT SEEMED TO WORK FINE UNTIL ATTEMPTING TO PUT CUSTOM ROM ON
CUSTOM ROM WOULDN'T BOOT PAST BLUE MAN SCREEN AT FIRST, THEN BEATS AUDIO SCREEN AND THEN HTC SCREEN.
MY PHONE IS S-ON, UNLOCKED, PYRAMID PUT SHIP S-ON RL, HBOOT-1.29.0000,eMMC-boot,Mar 2 2012, 18.14.34
PC IS NOT CURRENTLY RECOGNISING MY PHONE AS A REMOVABLE DEVICE IN THE SENSE THAT IT WON'T ALLOW ME TO PUT ON ANY ITEMS.
I DO HAVE A SPARE, ACCESSIBLE SD CARD AND DO NOT CARE WHAT HAPPENS TO THE CONTENTS OF IT. IF THIS IS USEFUL.
Please. Help me. Thank you
don't panic.many as you had that issue.it is easy
from 4ext recovery enable smartflash and then immediately flash the rom
you should be fine
If it still fails to boot after reflashed with smartflash on, get boot.img from zip, place it in your fastboot/adb folder and flash it manually from fastboot: fastboot flash boot boot.img
Look for Asskicker's guide in General section. "flashing rom with s-on and Hboot 1.27+"
Sent from my HTC Sensation Z710e using xda app-developers app
rzr86 said:
don't panic.many as you had that issue.it is easy
from 4ext recovery enable smartflash and then immediately flash the rom
you should be fine
Click to expand...
Click to collapse
Unfortunately, this hasn't worked for me. I did this...
- Went onto 4EXT recovery.
- Went to tools.
- Clicked on 'Enable Smartflash'.
- Ensured it was on.
- Went to 'install .zip from SD Card'
- Found the Cynagon MOD.
- "Finding update package... Opening update package... Installing update... Install from SD Card complete."
- Rebooted phone.
- A pending update to your boot partition has been detected. Your ROM will reboot once [and then it reboots]. The first time it came up with this though. It said something about how there had been an error.
- Got stuck at the HTC screen again.
I'd just like to reaffirm that before something happened (I believe it was when I tried to flash to stock recovery), my phone was getting to the Beats Audio/Little Blue Man Screen. Now it's getting to the HTC screen.
That donation to the site is still in promise!
matekaneve said:
If it still fails to boot after reflashed with smartflash on, get boot.img from zip, place it in your fastboot/adb folder and flash it manually from fastboot: fastboot flash boot boot.img
Look for Asskicker's guide in General section. "flashing rom with s-on and Hboot 1.27+"
Sent from my HTC Sensation Z710e using xda app-developers app
Click to expand...
Click to collapse
This also didn't work for me. It appeared to run entirely successfully. I rebooted the phone using 'fastboot reboot' and it still got stuck at the same screen.
ElliotHorne32 said:
Unfortunately, this hasn't worked for me. I did this...
- Went onto 4EXT recovery.
- Went to tools.
- Clicked on 'Enable Smartflash'.
- Ensured it was on.
- Went to 'install .zip from SD Card'
- Found the Cynagon MOD.
- "Finding update package... Opening update package... Installing update... Install from SD Card complete."
- Rebooted phone.
- A pending update to your boot partition has been detected. Your ROM will reboot once [and then it reboots]. The first time it came up with this though. It said something about how there had been an error.
- Got stuck at the HTC screen again.
I'd just like to reaffirm that before something happened (I believe it was when I tried to flash to stock recovery), my phone was getting to the Beats Audio/Little Blue Man Screen. Now it's getting to the HTC screen.
That donation to the site is still in promise!
Click to expand...
Click to collapse
did you flash gapps and then the CM rom?
if no then:
flash gapps
flash the rom again
(don't forget to enable smartflash again)
rzr86 said:
did you flash gapps and then the CM rom?
if no then:
flash gapps
flash the rom again
(don't forget to enable smartflash again)
Click to expand...
Click to collapse
Sorry to be a pain, but could you run me through a step-by-step on how to do that? *Noob Klaxon*
ElliotHorne32 said:
Sorry to be a pain, but could you run me through a step-by-step on how to do that? *Noob Klaxon*
Click to expand...
Click to collapse
gapps is google apps.is a zip file
if i remember well maybe is in the thread where you downloaded the rom
simply put it in the root of sdcard and flash it from recovery
after that flash the rom(don't forget smartflash)
rzr86 said:
gapps is google apps.is a zip file
if i remember well maybe is in the thread where you downloaded the rom
simply put it in the root of sdcard and flash it from recovery
after that flash the rom(don't forget smartflash)
Click to expand...
Click to collapse
I downloaded it from here [can't post link, but it's the official Cynagon MOD Website] - I then clicked on the 'Stable Mod'.?
If you straight quick responses go on this forum here I have through similar issues before and they so helpful..I'm S-ON
http://forum.xda-developers.com/showthread.php?t=163186
Sent from from my HTC Sensation XE with Beats Audio Z715e using xda app-developers app
Hi there mate!
What I would recommend you to do is running an appropriate RUU for your device, ( i would recommend GB, because then you can S-off very easy), and then re-run the whole process. If you run a GB RUU, you can gain s-off with revolutionary. And the best part, the RUU can be run in bootloader, so it doesn't matter if your ROM does not boot. I can send you a link once my internet gets faster (im using all my bandwidth for source-building lol)
Please keep me posted and feel free to ask any questions
Best of luck !
InfinityFTW said:
Hi there mate!
What I would recommend you to do is running an appropriate RUU for your device, ( i would recommend GB, because then you can S-off very easy), and then re-run the whole process. If you run a GB RUU, you can gain s-off with revolutionary. And the best part, the RUU can be run in bootloader, so it doesn't matter if your ROM does not boot. I can send you a link once my internet gets faster (im using all my bandwidth for source-building lol)
Please keep me posted and feel free to ask any questions
Best of luck !
Click to expand...
Click to collapse
if i remember well he can't downgrade using a GB ruu because he is S-ON
i think he can only upgrade
you have to be already S-OFF in order to downgrade with ruu
InfinityFTW said:
Hi there mate!
What I would recommend you to do is running an appropriate RUU for your device, ( i would recommend GB, because then you can S-off very easy), and then re-run the whole process. If you run a GB RUU, you can gain s-off with revolutionary. And the best part, the RUU can be run in bootloader, so it doesn't matter if your ROM does not boot. I can send you a link once my internet gets faster (im using all my bandwidth for source-building lol)
Please keep me posted and feel free to ask any questions
Best of luck !
Click to expand...
Click to collapse
Thank you for your helpful paragraph If you could send me the link for that RUU, that would be great, but I do have a couple of other questions. What is an RUU? I assume GB is Gingerbread, but is that the OS that I am on? What will the RUU do? I really stepped out of my depth trying this haha!
Elliot,
ElliotHorne32 said:
Thank you for your helpful paragraph If you could send me the link for that RUU, that would be great, but I do have a couple of other questions. What is an RUU? I assume GB is Gingerbread, but is that the OS that I am on? What will the RUU do? I really stepped out of my depth trying this haha!
Elliot,
Click to expand...
Click to collapse
RUU returns your device into completely stock situation as you bought it
now depending your hboot version you are running ics android
ElliotHorne32 said:
Thank you for your helpful paragraph If you could send me the link for that RUU, that would be great, but I do have a couple of other questions. What is an RUU? I assume GB is Gingerbread, but is that the OS that I am on? What will the RUU do? I really stepped out of my depth trying this haha!
Elliot,
Click to expand...
Click to collapse
forum.xda-developers.com/showthread.php?t=1074559
RUU stands for Rom Update Utility, and it is an executable (.exe) file wich is ran from a pc with a phone connected in fastboot. The RUU is meant to restore all partitions on your phone
Sent from a muffin inside a muffin using muffintalk.
OK try this.
1. Reboot into 4ext recovery.
2. Wipe everything except sdcard.
3.enable 4ext smart flash
4. Reflash Cyanogenmod.
5. Flash gapps add-on from Cyanogenmod thread.
6. Reboot and wait up to 10 minutes.
If this does not work take your Cyanogenmod rom and on your pc extract the boot.IMG file and move it to your adb folder then repeat but add
8. Fastboot flash boot.IMG using adb while in recovery.
Open your cmd and CD to your ad folder.
Issue the command " fastboot flash boot boot.img " with the phone connected.
9. Reboot and wait up to 10 minutes
Thank you all for your responses, I haven't forgotten about this thread at all haha - I've just been very busy lately but will be doing all of your suggestions over the weekend, so thank you. Will keep you posted. Elliot
ElliotHorne32 said:
Thank you all for your responses, I haven't forgotten about this thread at all haha - I've just been very busy lately but will be doing all of your suggestions over the weekend, so thank you. Will keep you posted. Elliot
Click to expand...
Click to collapse
Btw the only RUU that will work on hboot 1.29.0000 devices is the 3.33.401.153 one IIRC. It's also available to download from my FTP - here
Sent from my HTC Sensation XE with Beats Audio Z715e using xda premium
Jonny said:
Btw the only RUU that will work on hboot 1.29.0000 devices is the 3.33.401.153 one IIRC. It's also available to download from my FTP - here
Sent from my HTC Sensation XE with Beats Audio Z715e using xda premium
Click to expand...
Click to collapse
Just when I have everything ready to try this, I am getting '403 Forbidden' on that link you just sent me. What do I do to get that link working?
Also, is it as simple as plugging the phone into Fastboot USB mode and clicking the .exe file?
Elliot,
Any help possible with this one, guys and girls? The last post I made about the 403?
Elliot
Hi, everything messed up from using the stupid TWRP 2.6.0.0 .... I was going to flash a custom rom , but it didn't let me, so I did a little research that I need 2.3.3.0 in order to instal any custom rom.So I tried to switch to 2.3.3.0 but it didn't let me... after that I tried to push stock recovery and now i'm stuck at the white HTC Entering Recovery ( pink letters) screen, ( The recovery just doesn't load) ... I just want to finish with this , and go back to my stock htc rom with not roots or anything.. im tired of this seriously.....
When I try to run RUU I get stuck at the Black HTC Letters screen , the the setup stops and says that it will try to repair my phone, sadly with no result every time.. I think that I don't have any OS on my phone right now, because when RUU starts it shows :
Change image version from : ( blank space)
To: ..... bla bla bla , ( the version of the ruu) ...
I have no problems with entering fastboot and unlocking/relocking my Hboot.
Any help about restoringmy phone will be appreciated . Thanks , I'm online all the time so if I get any responses I'll answer quick.
P.S. I can't mount my usb storage from anywhere, and it doesn't show up on my PC when i connect the usb
looperman said:
Hi, everything messed up from using the stupid TWRP 2.6.0.0 .... I was going to flash a custom rom , but it didn........................
P.S. I can't mount my usb storage from anywhere, and it doesn't show up on my PC when i connect the usb
Click to expand...
Click to collapse
Don't lose hope, don't panic.
Tell me which RUU did you use?
Also, what is your CID?
How did you flash your recovery ?
Sent from my HTC One S using Tapatalk 4 Beta
khan.orak said:
Don't lose hope, don't panic.
Tell me which RUU did you use?
Also, what is your CID?
How did you flash your recovery ?
Sent from my HTC One S using Tapatalk 4 Beta
Click to expand...
Click to collapse
well I think that it doesn't really matter which RUU I "used" because it doesn't even get me in the process of installing...
still , tried these two:
RUU_VILLEC2_U_ICS_40_S_HTC_Europe_2.15.401.100_Radio_16.21.20.02U_16.09.20.11_M2_release_286571_signed
RUU_Ville_U_ICS_40_S_HTC_Europe_2.21.401.10_Radio_1.06s.50.02.27_2_10.08.50.04L__release_271119_signed
I flashed all recoveries with ONE S all in one tool kit,
first i was with TWRP 2.5 i think , then i flashed 2.6, and 2.3.3.... now I flashed the stock recovery , still stuck...
looperman said:
well I think that it doesn't really matter which RUU I "used" because it doesn't even get me in the process of installing...
still , tried these two:
RUU_VILLEC2_U_ICS_40_S_HTC_Europe_2.15.401.100_Rad io_16.21.20.02U_16.09.20.11_M2_release_286571_sign ed
RUU_Ville_U_ICS_40_S_HTC_Europe_2.21.401.10_Radio_ 1.06s.50.02.27_2_10.08.50.04L__release_271119_sign ed
I flashed all recoveries with ONE S all in one tool kit,
first i was with TWRP 2.5 i think , then i flashed 2.6, and 2.3.3.... now I flashed the stock recovery , still stuck...
Click to expand...
Click to collapse
If you downloaded RUUs from androidruu, then it's a case of bad RUU.
Sent from my HTC One S using Tapatalk 4 Beta
khan.orak said:
If you downloaded RUUs from androidruu, then it's a case of bad RUU.
Sent from my HTC One S using Tapatalk 4 Beta
Click to expand...
Click to collapse
well what am I supposed to do ?
looperman said:
well I think that it doesn't really matter which RUU I "used" because it doesn't even get me in the process of installing...
still , tried these two:
RUU_VILLEC2_U_ICS_40_S_HTC_Europe_2.15.401.100_Radio_16.21.20.02U_16.09.20.11_M2_release_286571_signed
RUU_Ville_U_ICS_40_S_HTC_Europe_2.21.401.10_Radio_1.06s.50.02.27_2_10.08.50.04L__release_271119_signed
I flashed all recoveries with ONE S all in one tool kit,
first i was with TWRP 2.5 i think , then i flashed 2.6, and 2.3.3.... now I flashed the stock recovery , still stuck...
Click to expand...
Click to collapse
Okay, just now I noticed. You used two Different RUUs for two different versions.
The 1st one is for S3/C2 version, the 2nd one is for S4 version.
Use This Thread to download RUU's only for your version (S4 or S3 whichever you have got). In your case, it does matter which RUU you use.
If you need any help further just ask away.
the thing is that the RUU doesn't get to the process of installing , and I have used those RUU's before....
I need some solution the get to a working recovery and instal some kind of OS because the last time I could get in my recovery it said that I don't have any OS installed...
looperman said:
the thing is that the RUU doesn't get to the process of installing , and I have used those RUU's before....
I need some solution the get to a working recovery and instal some kind of OS because the last time I could get in my recovery it said that I don't have any OS installed...
Click to expand...
Click to collapse
okay you gonna need fastboot for this. What I have been successful with is:
1. Download an RUU (VERSION SPECIFIC!).
2. Go into Bootloader -> Then select FASTBOOT
3. Connect your Phone to PC. It should say Fastboot - USB mode.
4. Run the RUU, it will get you through all the steps.
khan.orak said:
okay you gonna need fastboot for this. What I have been successful with is:
1. Download an RUU (VERSION SPECIFIC!).
2. Go into Bootloader -> Then select FASTBOOT
3. Connect your Phone to PC. It should say Fastboot - USB mode.
4. Run the RUU, it will get you through all the steps.
Click to expand...
Click to collapse
doesn't work as I've told you , it happens with every RUU ... I get the Black screen with white HTC letters...
I think that what RUU does is : it updates the version my software I think it just doesn't place a new software right away( just an update), but as TWRP said I don't have OS installed...
can anyone help me ?
looperman said:
doesn't work as I've told you , it happens with every RUU ... I get the Black screen with white HTC letters...
I think that what RUU does is : it updates the version my software I think it just doesn't place a new software right away( just an update), but as TWRP said I don't have OS installed...
Click to expand...
Click to collapse
Man you're making this difficult. The more I want to help you, the more you become hasty.
RUU doesn't do what you think. It puts New software, updates firmware (hboot, radio, RECOVERY), so yes it is basically a one-stop solution.
Please calm down as panicking won't help.
Tell me your One S version (S3/S4) at least? so that we can move forward in right direction. and also your CID
Tell me what recoveries and RUU you tried. and what errors do you get while you run them.
EDIT: Thanks to @tivofool I forgot to mention that you have to RELOCK your bootloader before running RUU
I'm with S3
I wrote the 2 RUU's I tried to use,
before that i tried TWRP 2.5.0.0,2.3.0.0.,2.6 and finally I flashed factory stock recovery that's it and both my carrier and bl are unlocked
P.S. : Yeah i knew about the relocking but still stuck on black screen with white HTC Letters
looperman said:
I'm with S3
I wrote the 2 RUU's I tried to use,
before that i tried TWRP 2.5.0.0,2.3.0.0.,2.6 and finally I flashed factory stock recovery that's it and both my carrier and bl are unlocked
P.S. : Yeah i knew about the relocking but still stuck on black screen with white HTC Letters
Click to expand...
Click to collapse
Black Screen with HTC is the oem update screen.
Okay do this please and we'll try to see if there's a problem with the HBOOT. Give me this info and We'll reflash HBOOT.
Go to fastboot and connect your phone to PC.
Enter this command from your PC:
Code:
fastboot getvar all
post results here (MINUS IMEI AND SERIAL #)
just a second, I got a working recovery... I mean i can get in it and everything and I can mount the USB Storage too.
What Rom would you recommend ?
looperman said:
just a second, I got a working recovery... I mean i can get in it and everything and I can mount the USB Storage too.
What Rom would you recommend ?
Click to expand...
Click to collapse
That was fast.
I am using Viper ROM and it's very good. Customization and speed.
For a better battery life, BULLETPROOF KERNEL.
Edit: how did you get it to work by the way.
Viper rom is for s4 only isn't it ?
looperman said:
just a second, I got a working recovery... I mean i can get in it and everything and I can mount the USB Storage too.
What Rom would you recommend ?
Click to expand...
Click to collapse
Make sure you flash a S3 Rom (you mentioned having a s3 right?)
Sent from my HTC VLE_U using Tapatalk 2
looperman said:
Viper rom is for s4 only isn't it ?
Click to expand...
Click to collapse
Oh yes sorry.
okay, so ... I'm going to explane everything I did, I hope I'll help some other people too.
I flashed TWRP from One_S_All-In-One_Kit_v4.0 but without luck, then i flash the factory stock recovery, still the phone was letting me into any of these two recoveries, then i decided reflash the same TWRP again and it worked,
First I couldn't mount the storage from the recovery , but it was still showing in "My Computer" , I had only one option and it was to Format the Storage. So I did.. then copied this rom with gapps on it ---> http://forum.xda-developers.com/showthread.php?t=2164406
Fully wiped --> Flash Rom , then Flash Gapps, ---> then I booted in fastboot to boot from CMD the "boot.img" with "fastboot flash boot boot.img" from the Pacman Rom and then I Rebooted the HTC and Done
Huge thanks to @khan.orak
I hope I helped someone with the same ****tyass problem.
looperman said:
okay, so ... I'm going to explane everything I did, I hope I'll help some other people too.
I flashed TWRP from One_S_All-In-One_Kit_v4.0 but without luck, then i flash the factory stock recovery, still the phone was letting me into any of these two recoveries, then i decided reflash the same TWRP again and it worked,
First I couldn't mount the storage from the recovery , but it was still showing in "My Computer" , I had only one option and it was to Format the Storage. So I did.. then copied this rom with gapps on it ---> http://forum.xda-developers.com/showthread.php?t=2164406
Fully wiped --> Flash Rom , then Flash Gapps, ---> then I booted in fastboot to boot from CMD the "boot.img" with "fastboot flash boot boot.img" from the Pacman Rom and then I Rebooted the HTC and Done
Huge thanks to @khan.orak
I hope I helped someone with the same ****tyass problem.
Click to expand...
Click to collapse
Glad it worked for you buddy.
Hi guys,
My phone now is on LeeDroid custom ROM (Build 1.03.401.6.9_g CL923215)
What are the steps to return the htc u11 to stock please?
The original software number of my phone is: 1.11.400.4
EDIT: I went to: https://forum.xda-developers.com/showpost.php?p=72425224&postcount=5
& downloaded stock recovery & nandroid TWRP backup (for 1.11.400.4).
However, I couldnt flash that nandroid TWRP from TWRP recovery.
Long story short, I just got the phone today, I made a big mistake by not inserting the simcard in & testing to see if the phone working or not.
So, I went straight through the process of unlocking bootloader, installing TWRP, Rooting, Installing custom ROM without making a nandroid backup.
For all that, the phone did not recognize the sim cards (tried both my sim & my gf's sim. not working)
The store will take back the phone as long as I return it to stock.
Thanks for your help!!!
dsymbol said:
Hi guys,
What's the process of returning the htc u11 to stock please?
Googling doesn't give me much result.
Long story short but I just got the phone today, I made a big mistake by not inserting the simcard in & testing to see if the phone working or not.
So, I went straight through the process of unlocking bootloader, installing TWRP, Rooting, Installing custom ROM without making a nandroid backup.
For all that, the phone did not recognize the sim cards (tried both my sim & my gf's sim. not working)
The store will take back the phone as long as I return it to stock.
Thanks for your help!!!
Click to expand...
Click to collapse
You'll need to download the stock rom for your verison (ruu). Hopefully one is available. Check the guide section here.
purple patch said:
You'll need to download the stock rom for your verison (ruu). Hopefully one is available. Check the guide section here.
Click to expand...
Click to collapse
I've downloaded stock recovery & nandroid TWRP backup of my stock ROM now.
What are the steps to revert the phone to stock please?
Thanks
dsymbol said:
I've downloaded stock recovery & nandroid TWRP backup of my stock ROM now.
What are the steps to revert the phone to stock please?
Thanks
Click to expand...
Click to collapse
Restore the TWRP backup, check everything is working, then flash stock recovery if you need to. The stock Nandroid should include recovery asfaik. I'm more of a trial and error guy lol. Read guide pages to know for certain, check HTC 10 guides, same steps.
purple patch said:
Restore the TWRP backup, check everything is working, then flash stock recovery if you need to. The stock Nandroid should include recovery asfaik.
Click to expand...
Click to collapse
ok so I downloaded TWRP_Backup_Untouched_System_Image_+_Boot_1.11.400.4_OCEAN_DUGL_with_recovery.
1. Transfering the TWRP backup to the phone's storage
2. Flashing that backup just like flashing the custom ROM (it says Invalid zip file format. Error ect...) Please help
3. Flashing the recovery just like flashing the TWRP using adb commands
4. Lock the bootloader? I don't know how to do this.
Please advice
Thanks purple patch
dsymbol said:
ok so I downloaded TWRP_Backup_Untouched_System_Image_+_Boot_1.11.400.4_OCEAN_DUGL_with_recovery.
1. Transfering the TWRP backup to the phone's storage
2. Flashing that backup just like flashing the custom ROM (it says Invalid zip file format. Error ect...) Please help
3. Flashing the recovery just like flashing the TWRP using adb commands
4. Lock the bootloader? I don't know how to do this.
Please advice
Thanks purple patch
Click to expand...
Click to collapse
Get the one from here and follow instructions. That's what the thread is for. https://forum.xda-developers.com/u11/how-to/collection-htcu-u11-ruu-firmware-t3612048. Sorry i don't have time to do the leg work for you (i'm out atm), but it's all there.
download this Official RRU firmware and install it https://forum.xda-developers.com/u11/how-to/unlocked-htc-u11-software-update-6-19-t3624814
Use the ruu, you might need the HTC drivers but in the future never not make a backup, 15 mins could save u a major headache
AllGamer said:
download this Official RRU firmware and install it https://forum.xda-developers.com/u11/how-to/unlocked-htc-u11-software-update-6-19-t3624814
Click to expand...
Click to collapse
I'm downloading it now & will report back very soon.
Thanks for the tip AllGamer!!!
AllGamer said:
download this Official RRU firmware and install it https://forum.xda-developers.com/u11/how-to/unlocked-htc-u11-software-update-6-19-t3624814
Click to expand...
Click to collapse
Finished downloading & now I got an ERROR installation, something like a wrong ROM, probably because I'm currently on LeeDroid custom ROM (Build 1.03.401.6.9_g CL923215)
Please advice
Thank you
dsymbol said:
Finished downloading & now I got an ERROR installation, something like a wrong ROM, probably because I'm currently on LeeDroid custom ROM (Build 1.03.401.6.9_g CL923215)
Please advice
Thank you
Click to expand...
Click to collapse
Your going to need a full signed RUU zip matching your original firmware and CID buddy.
Based on your original build number its an Indian dual SIM device so here is the ruu:
https://www.androidfilehost.com/?fid=817550096634780026
1. Rename it to 2PZCIMG.zip
2. Lock your bootloader
3. Drop the zip on your external SD card.
3. Boot to download mode, at that point you will be prompted to flash... Accept... Profit.
If you don't have an external SD.
1. Lock your bootloader.
2. Boot to download mode.
3. Open a cmd window and run the below commands.
fastboot orm rebootRUU (hit enter)
fastboot flash zip (drag the zip into the cmd window then hit enter)
dsymbol said:
Finished downloading & now I got an ERROR installation, something like a wrong ROM, probably because I'm currently on LeeDroid custom ROM (Build 1.03.401.6.9_g CL923215)
Please advice
Thank you
Click to expand...
Click to collapse
On the PC side, what was the exact error message?
you can ignore the warning from the phone side.
I had a similar issue the other day, but then I was able to run the RUU upgrade to rest my phone back to stock as I had to ship it back for a refund, to get the new Red ones
When I ran the RUU thing it wouldn't detect the phone, did a few things, and then it was finally able to detect the phone.
and when it started updating the Boot image it hung for a long while, I had to restart the phone back into download mode, then run the RUU again, and it was able to continue from there.
AllGamer said:
On the PC side, what was the exact error message?
you can ignore the warning from the phone side.
I had a similar issue the other day, but then I was able to run the RUU upgrade to rest my phone back to stock as I had to ship it back for a refund, to get the new Red ones
When I ran the RUU thing it wouldn't detect the phone, did a few things, and then it was finally able to detect the phone.
and when it started updating the Boot image it hung for a long while, I had to restart the phone back into download mode, then run the RUU again, and it was able to continue from there.
Click to expand...
Click to collapse
It says: ERROR [130]: MODEL ID ERROR
The ROM Update Utility cannot update your Android phone.
Please get the correct ROM Update Utility and try again.
The previous screen says:
Verifying that you want to update
Image version 1.03.401.6
to
Image version 1.11.617.4
LeeDroid said:
Your going to need a full signed RUU zip matching your original firmware and CID buddy.
Based on your original build number its an Indian dual SIM device so here is the ruu:
https://www.androidfilehost.com/?fid=817550096634780026
1. Rename it to 2PZCIMG.zip
2. Lock your bootloader
3. Drop the zip on your external SD card.
3. Boot to download mode, at that point you will be prompted to flash... Accept... Profit.
Click to expand...
Click to collapse
I'm on it now & will report back!
Thank you Sir for joining the party. I have hope now
dsymbol said:
I'm on it now & will report back!
Thank you Sir for joining the party. I have hope now
Click to expand...
Click to collapse
Added an extra step incase you don't have an external sd
dsymbol said:
It says: ERROR [130]: MODEL ID ERROR
The ROM Update Utility cannot update your Android phone.
Please get the correct ROM Update Utility and try again.
The previous screen says:
Verifying that you want to update
Image version 1.03.401.6
to
Image version 1.11.617.4
Click to expand...
Click to collapse
The 1.03.401.6 may be European software. You will need the RUU for your exact phone model from: http://www.htc.com/us/support/updates.aspx
or https://forum.xda-developers.com/u1...u-firmware-t3612048/post72425227#post72425227
michaelbsheldon said:
The 1.03.401.6 may be European software. You will need the RUU for your exact phone model from: http://www.htc.com/us/support/updates.aspx
or https://forum.xda-developers.com/u1...u-firmware-t3612048/post72425227#post72425227
Click to expand...
Click to collapse
I have linked the correct ruu in my post above as per the original firmware mentioned in the op
The correct build is 1.11.400.4
LeeDroid said:
I have linked the correct ruu in my post above as per the original firmware mentioned in the op
The correct build is 1.11.400.4
Click to expand...
Click to collapse
I have the ext. sdcard ready.
I have a question about locking the bootloader please
To lock the bootloader, I have to do this? (found instruction from google)
adb reboot bootloader
& type in 1 of these commands & stop there if it works?
fastboot oem lock
fastboot flashing lock
fastboot oem relock
Please advice
dsymbol said:
I have the ext. sdcard ready.
I have a question about locking the bootloader please
To lock the bootloader, I have to do this? (found instruction from google)
adb reboot bootloader
& type in 1 of these commands & stop there if it works?
fastboot oem lock
fastboot flashing lock
fastboot oem relock
Please advice
Click to expand...
Click to collapse
adb reboot download
fastboot oem lock
LeeDroid said:
adb reboot download
fastboot oem lock
Click to expand...
Click to collapse
Confirmation number: 5G354245BV234401U