So I really want to install the 4.4.2 update to KitKat, my HTC One is still on the stock T Mobile ROM that came with it.
However, when I try to update it goes to CWM and it aborts the installation all the time.
I then found out I need the phone to be S-OFF, so I tried RumRunner and it is stuck at pouring, eventually after a lot of boot loops I get: Turn on your device, run RumRunner again and pray.
Or something off that nature.
I did everything by the book, everything.
Also the System Update notification pops up every time I open my phone. I need to tell it to notify me later again, every time.
I am lost....
Any answer?....
If you are stock, and unrooted, just flash a stock recovery and relock your bootloader.
Related
I relocked my phone, did the stock RUU.exe, went back to a stock Rom, got the update and no matter what I try I can't get unlocked again. Is there a way to uninstall the Update
You can try rerunning the RUU with admin privileges see if that works. Also you can try unlocking bootloader before the update then OTA updating see if that works
Sent from my ViperDNA infected with ViperBlue DNA
EchoX860 said:
I relocked my phone, did the stock RUU.exe, went back to a stock Rom, got the update and no matter what I try I can't get unlocked again. Is there a way to uninstall the Update
Click to expand...
Click to collapse
Did you not read the guide I posted here?
Also try flashing your unlock token a few times some people it works the first time others 10 times later
Sent from my HTC6435LVW using XDA Premium HD app
turn phone completely off, then boot straight in to bootloader by holding power and vol down. then run unlock.bin. works every time.
EchoX860 said:
I relocked my phone, did the stock RUU.exe, went back to a stock Rom, got the update and no matter what I try I can't get unlocked again. Is there a way to uninstall the Update
Click to expand...
Click to collapse
It took 5 attempts for me to unlock. Pain in the rear, I know, but it'll eventually work. Good luck to you. BTW, update DEF improves bluetooth & beats. Major difference, at least, for me there is.:victory:
Forgot to Flash the Kernel Modules, so now I'm having Boot Loops, and am unable to do the Stock.RUU exe because I took the update. I am 90% I'm screwed. Command prompt is also giving me the device not found error. Backups aren't working either, get the same boot loop
EchoX860 said:
Forgot to Flash the Kernel Modules, so now I'm having Boot Loops, and am unable to do the Stock.RUU exe because I took the update. I am 90% I'm screwed. Command prompt is also giving me the device not found error. Backups aren't working either, get the same boot loop
Click to expand...
Click to collapse
i had this problem took two days of pluging and unpluging trying adb sideload and everything under the sun uninstall re install just keep trying and it will connect again just takes a while for it to reconnect
I tried rooted my rezound could not get the custom rom to work properly and tried going back to stock. I relocked, tried flashing the latest RUU, both from the phone and fastboot on the computer. When I do it on the phone it gets to the checking stage, finishes the check and then returns to the hboot screen, and dose not seem to do anything after that. When I try it from the computer I get a FAILED <remote: not allowed error >. I next tried to reunlock the phone to try flashing a different rom, I generated a new token, and then tried flashing it but I get a FAILED (remote: signature verify fail) error. Any help would be greatly apperciated.
Make sure the RUU is named PH98IMG.zip and put it on the root of the sdcard. Make sure it accidentally doesn't have .zip.zip on the name. If that doesn't work download the zip again and check the md5 checks out...
Sent from my ADR6425LVW using Tapatalk 2
You can still get to the bootloader then?
And even if the RUU doesn't seem like it's doing anything just let it keep going. At one point it will go to a black screen then back to hboot and it will run again. Just let it go. Could take up to 15 min. or so. Just make sure you don't interrupt it at an unfortunate time or you could brick.
Once you get the RUU to finish properly, flash a custom recovery and immediately make a nandroid of stock and label it as such. Then you can just restore that if you ever want/need to go back to stock. Easier than running the RUU.
I make nandroids at several stages, at a clean stock, immediately after flashing a ROM, after I get the ROM set up, etc... then I just append the name to describe what it is and I feel secure knowing I'm covered. I keep them on my ext sd and copy them to my pc as well.
Got it working
Never got the stock rom back on the phone. I was able to unlock the phone after regenrating like 5 diffrent unlock keys, and then installing a custom rom. Im glad to have a phone that works agian. As far as the restoring stock, the issue I was having was that it would open the zip, run the check and then jump back to the bootloader menu, so I never got to the black screen.
Ok, I will try to give as much info as I can, please let me know if there is anything else I should provide. I really appreciate any help and advice as I've been pulling my hair out for the last 3 days, spending 10+ hours trying to get my Amaze back working.
Problem started a few days ago, phone shut off, when it powered back on it was stuck on the White HTC logo. That same day the phone died completely and would not power on at all, not even the amber light. Eventually the amber light would blink the but phone wouldn't charge. I fixed this first issue by jump starting the battery with a 9V battery, something someone suggested on a thread. Worked great to get the phone charging again... but that's it. So basically I have access to the HBOOT/Fastboot and EXT4 Recovery menu's, and there is no OS on the phone, I know for sure now because I wiped the system.
When I try (but fail) to install the RUU 1.41 exe, and it checks the phone, i comes back saying my "current" version on the phone is 2.14.661.2 even though there isn't any OS on there...
Bit more background info. I purchased this phone last year off someone, it was running 4.1.2 and the bootloader was unlocked. It *is S-ON though.
Whatever else this guy did, I'm not sure as this is what I can tell, however the CID pulls up as Telus001? which the guy did tell me it was a Telus phone.
So I'm trying to load the Telus stock rom and I've been getting nowhere and pulling my hair out. I'm 10hrs in and no further then I was. So first I downloaded the Telus RUU 1.41 exe from the stock rom but it gives an Error 43. I tried this with both the bootloader locked again, and unlocked. I then downloaded the OTA 2.14.661 zip from the stock roms, and renamed it to PH85IMG, stuck that on the Ext SD card. Problem is when it boots into the HBOOT it actually see's the file, loads it, then checks it, but then returns me to the main menu. I don't get promted to update. Now I've tried this too with the bootloader unlocked, and locked. So a third go, I extracted the Rom from the 1.41 RUU and made that PH85IMG, tossed it onto the SD card and again this time it actually went further but gave another error.
I have tried to Sideload the above Roms through recovery but they give error's.
In that All In One program there is an option to fix the Mainver error, however when I run that all I get is "Device not found". The phone IS loaded under device manager as HTC Phone as I had installed the drivers. I've tried to google this fix but I can't get anywhere.
Everyone has said on forums that sticking a PH85IMG.zip file on an Ex SD and having it boot into the HBOOT menu will rebuild the phone, but I'm out of idea's how to get there because it loads the rom's, checks them, and then boots me back to the menu. There is only 2 Rom's I can find for Telus, and that's the 1.41 EXE or the OTA 2.14.661.2. My HBOOT version is 1.93.0002, RUBY PVT SHIP S-ON RL.
Thanks in advance for any help/suggestions, desperately just want my phone working again. I feel like I've been to the 4 corner's of google trying to solve this problem.
Strange This should not happen.Also if your phone is running 4.1.2 which should be a custom then that means your phone was updated to ics so the ruu.exe will fail.if you have access to 4ext recovery then you can flash any custom rom to boot your phone.But if you want stock and both of the stock roms for your carrier is not working then the only thing you can do is s-off the phone then use supercid so you can flash any carrier's rom then flash t-mobile ics stock.Tell me if this worked for you.
darkshadow1997 said:
Strange This should not happen.Also if your phone is running 4.1.2 which should be a custom then that means your phone was updated to ics so the ruu.exe will fail.if you have access to 4ext recovery then you can flash any custom rom to boot your phone.But if you want stock and both of the stock roms for your carrier is not working then the only thing you can do is s-off the phone then use supercid so you can flash any carrier's rom then flash t-mobile ics stock.Tell me if this worked for you.
Click to expand...
Click to collapse
Got it going!! Thanks for the suggestions. What did it in the end was this thread --> http://forum.xda-developers.com/showpost.php?p=27058110
I had EXT4 Recovery already, so I used his Zip and just flashed that. Phone came back up and is running great now... if only I had found his thread before the hr's and hr's I've been googling and trying things.
Hello everyone. This is my first post with my first problem from my first android phone. Please exercise some patience with me. When kitkat was pushed to the HTC One (T-Mobile) the install failed miserably. When I thought it was done it booted into recovery and just stayed there. I did a hard reboot and the splash screen was all crazy and the HTC boot screen was off colored and it was stuck at the boot screen. Obviously something was corrupted. I ran RUU for 4.3 to get back and flashed twrp and restored from my back up. All is well. I downloaded the OTA (I forget where but I believe somewhere on here) in an attempt to flash it from the stock recovery. Those were the instructions on that post. I ran RUU for 4.3 again to be completely fresh. I get to stock recovery and when I select to "apply from phone storage" I get an "invalid CID" error and the phone reboots. I ran "fastboot getvar all" and my cidnum= T-MOB010. What is the deal? That cid is correct, isn't it? I am also S-On with a "relocked" bootloader. I had to relock in order to run RUU because I was getting error 155. What am I missing? Why is it doing this?
Okay. I really need help guys. My phone is completely wiped and I have NO OS!! I side loaded Android Revolution kitkat and I'm getting errors with that. I can't unzip it!! I'm screwed guys. Please. Any help at this moment!! I'm desperate.
I was able to get out of this hell hole. I was able to run "adb push" and move my nandroid backup from my pc to the phone and restore.
What do I have to do to update to kitkat??? Why did check cid fail? I never changed that. What else could change it?? I had a stock recovery installed but the OTA failed still. Do I have to have the "right" stock recovery? I'm unlocked, rooted and S-off. Do I need to fix something else? Do I need to "relock" first? Is updating to kitkat even possible?? (sarcasim) The information seems to be scattered all over the place. I can not be the only one unlocked, rooted w/ S-off and trying to update my OS.
Hi. I attempted to root my device. I'm S-ON with Hboot 3.19
I was successful in unlocking the bootloader and installing a custom recovery. I then flashed SuperSU 2.02.
I rebooted and clicked SuperSU. It tells me there is no SU binary installed, if i upgraded to Android 4.3 i need to manually re-root it.
I thought fixing permissions in recovery would do the trick. Most of my apps are gone now, and i still don't have root.
Any suggestions?
I installed a newer version of SuperSU and was able to obtain root.
Most of my apps are still gone, since i changed the permissions.
Does anyone have a twrp stock rom backup or a stock rom i can flash?
I don't want to RUU because of fears of bricking my device. But if doing that is the only way to go back to stock, i might as well. I don't mind redoing the root process, as long as i have a working phone.
I went ahead and relocked the bootloader but didn't flash the stock recovery (oops), and i'm attempting to RUU, but it's stuck at 14% and my phone just says htc, no green bar. I hope i didn't just brick my phone.
jackzilla241 said:
I went ahead and relocked the bootloader but didn't flash the stock recovery (oops), and i'm attempting to RUU, but it's stuck at 14% and my phone just says htc, no green bar. I hope i didn't just brick my phone.
Click to expand...
Click to collapse
with exe ruu, be sure other programs in windows isn't talking to the phone of the ruu utility will hang. This means uninstalling things like Eclipse, HTC Sync, etc.
jackzilla241 said:
I went ahead and relocked the bootloader but didn't flash the stock recovery (oops), and i'm attempting to RUU, but it's stuck at 14% and my phone just says htc, no green bar. I hope i didn't just brick my phone.
Click to expand...
Click to collapse
You don't need stock recovery to RUU, typically (only for OTA, a different animal altogether).
RUU just gets stuck sometimes. Disconnect the phone, and start again (as scary as that sounds).
Use Win7 and USB 2.0 for the best results.