Trying to go back to stock from viperone. I relocked bootloader and ran the latest RUU from HTCDEV and it has been stuck at 44% updating system for about an hour now. No error codes or anything. What should I do?
Well, if anyone else runs into this problem, here is what I did:
Redownload RUU in case something went wrong with initial download
Stop current RUU with task manager
Switch phone to different USB port
Restart computer
Run new RUU as administrator
And we're back in business.
Glad you fixed it. Quick question: what would happen if you had tried to install the RUU with the unlocked bootloader?
Related
Gave my Evo 3d to my borother a few months back, but hes come back to me today saying it was stuck in bootloop.
He booted into the bootloader and did a factory reset, but it was still stuck in bootloop.
I tried to get into recovery to flash a new rom, but when i select recovery from the bootloader, that also goes into a bootloop.
Used adb to push the recovery onto the phone again but still just keeps bootlooping.
Not sure if its important but the phone is s-off. Any ideas on whats going on or how to fix?
Apologies, supposed to put this in Q&A forum
While you're at bootloader, connect USB and then flash a stock RUU.
androidcdma said:
While you're at bootloader, connect USB and then flash a stock RUU.
Click to expand...
Click to collapse
Thanks for the reply. Will i lose s-off with this?
Tones1971 said:
Gave my Evo 3d to my borother a few months back, but hes come back to me today saying it was stuck in bootloop.
He booted into the bootloader and did a factory reset, but it was still stuck in bootloop.
I tried to get into recovery to flash a new rom, but when i select recovery from the bootloader, that also goes into a bootloop.
Used adb to push the recovery onto the phone again but still just keeps bootlooping.
Not sure if its important but the phone is s-off. Any ideas on whats going on or how to fix?
Apologies, supposed to put this in Q&A forum
Click to expand...
Click to collapse
You didn't say what version of the Evo 3D you have (CDMA or GSM) or what bootloader is installed, but if it's a Sprint CDMA model I would recommend flashing the Sprint ICS RUU.exe from Windows after putting the phone into fastboot mode in the bootloader. You may have to relock the bootloader with the "fastboot oem lock" command first if it shows "***UNLOCKED***" at the top of the screen.
That will fix a lot of problems, especially when the phone is in an indeterminate state. After flashing the RUU you can HTC unlock, flash a custom recovery and then root the stock ROM or flash a rooted ROM.
ramjet73
Sorry it is a UK GSM (Europe). I have revolutionary bootloader installed. Got an RUU to try now thanks.
androidcdma said:
While you're at bootloader, connect USB and then flash a stock RUU.
Click to expand...
Click to collapse
Tones1971 said:
Thanks for the reply. Will i lose s-off with this?
Click to expand...
Click to collapse
^^^^ He got it first with the short version.
No, you won't lose S-OFF and won't need to relock the bootloader first if that's your current status.
And if it's a GSM model everything still applies, you just need a different RUU, which you already have.
ramjet73
Thanks ramjet. Thought this was going to be straightforward but cant get ruu to install. Error 170. Ill keep plugging away / googling away, hopefully come up with something
Tones1971 said:
Thanks ramjet. Thought this was going to be straightforward but cant get ruu to install. Error 170. Ill keep plugging away / googling away, hopefully come up with something
Click to expand...
Click to collapse
Error 170 means that the RUU utility can't find the phone. There's a readme.doc for running the RUU here, and the error codes are towards the end of that.
Are you putting it into "fastboot" mode in the bootloader, which should change to "fastboot usb" when it is connected to a computer? You also need to have the HTC USB drivers active, which can be accomplished by installing HTC Sync.
ramjet73
Tones1971 said:
Used adb to push the recovery onto the phone again but still just keeps bootlooping.
Click to expand...
Click to collapse
adb push into a bootlooping phone?
do you have the drivers for the phone? (if not download and install HTC Sync as they come with it)
did you try flashing a custom recovery img through fastboot? (go to bootloader select fastboot, connect USB, type "fastboot flash recovery nameOfYourRecoveryImg.img")
Yeah have tried installing custom recovery through fast boot again, and im in fastboot ok when trying to run the RUU. Also have HTC Sync installed from when i had the phone.. Drivers seemed to be ok as i was able to install the custom recovery with adb, alhough i still got bootloop after that.
Ive a few other things to try when i get home from work. Im sure it shouldnt be too difficult to resolve. Hopefully anyway.
Well this isnt going smoothly at all. Used another PC and was able to get the RUU to run.
However it now comes up with Error 131 Customer ID problem. The RUU was for HTC Europe (non branded). The phone was sim free. When i posted months back my cid was HTC_001. I checked it here: http://forum.xda-developers.com/showpost.php?p=22394863&postcount=172
However now when i get my CID it is showing as CID0202. Any way i can get an RUU to install? Any idea how a CID could change?
EDIT: noticed i used a different command last time.
fastboot getvar cid shows CID0202
adb shell getprop ro.cid now shows device not found (previously showed CID_001)
Thats typing both commands in same window, one after the other. One gets CID0202, the other device not found???
There's a change cid command in fastboot, fastboot oem writecid or something along those lines... however i believe the cid check is in the updater scripts of the ruu in which case a fastboot flash of all the img files should avoid it entirely... i don't remember the procedure for extracting the img files from the ruu but i believe ur supposed to run it and then dig through your temp files...
dessolator666 said:
There's a change cid command in fastboot, fastboot oem writecid or something along those lines... however i believe the cid check is in the updater scripts of the ruu in which case a fastboot flash of all the img files should avoid it entirely... i don't remember the procedure for extracting the img files from the ruu but i believe ur supposed to run it and then dig through your temp files...
Click to expand...
Click to collapse
Thanks for this. Ill see if i can find anything else out about it. So saves running the RUU exe and no cid check done then?
Need to bump this as im not getting anywhere. No RUU's will install, error 31 customer error. Have flashed recovery via ADB and through PG86IMG.ZIP, but still cant get in to recovery as it just continually reboots.
S-OFF with revolutionary. Anybody any ideas please?
Got bigger problems than i thought. Finally got an RUU to install after 4 days of trying, by first using fastboot oem writecid 11111111. But when the phone rebooted it was back bootlooping again. Is there any hope for my phone?
Tones1971 said:
Got bigger problems than i thought. Finally got an RUU to install after 4 days of trying, by first using fastboot oem writecid 11111111. But when the phone rebooted it was back bootlooping again. Is there any hope for my phone?
Click to expand...
Click to collapse
You need to stop cross posting in the d3rp Q&A thread and your own thread if you want more help. Cross-posting is stongly discouraged on XDA and it's really confusing when you are asking for help in one thread while getting different advice in another.
It sounds to me like all the CID changes on your phone have left it in an indeterminate state and I'm not sure at this point what is the correct CID and RUU for your model. If you could detemine that, set the CID correctly and flash the right RUU the phone should work, but it might be too late if you have in fact been flashing firmware that doesn't match your phone because the right RUU may not back that out properly.
That's all I can offer at this point, but since I don't know the history of your phone and how it got the various CID's you have reported, you will probably be the one that needs to figure it out.
ramjet73
Hi everyone,
I used RegawMod to unlock the bootloader, get root, and installed TWRP flash recovery. Phone is "S-ON". The phone was having issues with repeated SMS and I couldn't take the OTA. So I was told to relock the bootloader and install stock RUU file.
Ok so I did just that, relocked bootloader and then went to reinstall the RUU. When I went to download the RUU's I saw that the latest version was:
"RUU_JEWEL_CL_JB_45_S_Sprint_WWE_3.15.651.16_Radio_1.12.11.1119_NV_2.87_003_25007_release_299302_signed.exe"
I figured it would be ok to flash this and this would give me Jelly Bean all in one shot. My phone was running the stock rom which was software version "1.13.651.1"
So I installed the RUU and everything seemed to work properly until the phone rebooted. I noticed that none of the settings had been reset and the email account was still there etc. Typically when you flash an RUU everything goes back to configure mode on reboot. So I went into the settings software version etc and sure enough the software was the old software.
Looks like the RUU only changed my boot loader! When I checked originally I had bootloader 1.12.0000 after flashing the latest RUU file my bootloader was now 2.09.0000.
I then downloaded the "1.13.651.1" RUU to try and install it but it said not compatible with the bootloader.
Any advice on why the rom didn't update? What can I do now?
http://forum.xda-developers.com/showthread.php?p=36308826#post36308826
Welcome to the machine, where have you been? It's alright, we know where you've been.
Got a pretty lengthy thread, it seems the more people that run the new RUU are having the same exact issue. My radio is stuck on 1.05 and hboot 2.09 after running that thing. Should have known not to trust anything stock. Always thought those RUUs were safe.
Anyways, a bunch of us are subscribed to the thread I posted at the top of this post, I recommend you subscribe to it to keep things clean.
http://www.htc.com/us/support/news.aspx?p_id=628&p_name=htc-one-att
Decrypted rom.zip from this RUU:
https://mega.co.nz/#!HQ4zBTQR!YeYOQ0PPkUEvl0g9yAG7Wk7ejapyfXevazjAkYvYC_o
It says "Cingular" because thats what it says in the RUU's name.
The ROM.zip contains everything that goes onto the phone from the RUU, it does not contain the flashing tech.
Sneakyghost said:
Decrypted rom.zip from this RUU:
https://mega.co.nz/#!HQ4zBTQR!YeYOQ0PPkUEvl0g9yAG7Wk7ejapyfXevazjAkYvYC_o
It says "Cingular" because thats what it says in the RUU's name.
The ROM.zip contains everything that goes onto the phone from the RUU, it does not contain the flashing tech.
Click to expand...
Click to collapse
Does anyone know if this can be flashed like a normal RUU, thrugh fast boot and booting into ruu mode??
Just confused on what removing the flashing tech means...
Can this be installed on a rooted phone. I tried installing it and kept getting an error, it never would finish "sending" to the phone.
stedean said:
Can this be installed on a rooted phone. I tried installing it and kept getting an error, it never would finish "sending" to the phone.
Click to expand...
Click to collapse
I wasn't rooted, but I did flash it yesterday. The only thing that stopped me the first time was having an unlocked bootloader. I relocked it, and it worked flawlessly. It also removed the tampered flag in my bootloader after failing to s-off my phone with Rumrunner.
I'm about to try this since I can't S-Off properly and stuck with tampered and all.
Time to re-lock bootloader, run ruu.exe and start over.
Thanks everyone for all your help.
i tryed install this RUU by PC connect. but it appear 152 error and my phone has "HTC" on center screen, 4 triangle icons corner screen.
then i install this rom "RUU_M7_UL_JB_50_Cingular_US_1.26.502.12_Radio_4A.14.3250.13_10.33.1150.01_release_318450_signed_2" and it works
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.
I've been restraining myself from posting this for a few days, while browsing and looking through threads trying to figure out my answers. Something is wrong within my device, something is corrupted. Phone keeps rebooting on phone calls, and my UI is trashed, its all zoomed out and looking crazy. Flashing different ROMs has not helped. I have taken under advisement to RUU. However, I just want to make sure there is nothing I need to do before RUU'ing to keep from screwing up the device. Here is my current status: the only things I have done to this device since I got it last may are root and unlock using moonshine. So I have had no OTAs that I know of. This is the RUU I have:
RUU_DLX_WL_JB_50_S_VERIZON_WWE_3.06.605.4_Radio_1.01.01.1112_NV_VZW_4.46_002_release_340974_signed_2
I just want to make sure I only need to run that, and don't need to flash anything else (such as hboot, etc)
Thanks.
UPDATE: I tried running the RUU. I got Error 158. I was watching, and I had the phone in fastboot already, and when the screen said Rebooting Bootloader, then Waiting for Bootloader..... I never saw the phone actually boot to bootloader again, it just stayed black. then the program kept running like the phone was responding, and eventually shot out Error 158. should I follow this method http://forum.xda-developers.com/showthread.php?t=2293919 and relock the bootloader and then RUU? and does anyone know if I will be able to unlock again after I do this?
UPDATE: This is my main question if anyone can help. I have the above RUU, and I got error 158. Since I used moonshine's method, I am under the impression I need to re-lock bootloader, and THEN RUU. However, can someone please tell me if I need a different hboot version or if I'm just fine to go ahead like this? my hboot is below. I ask this because last failed RUU, i had to re-install the ROM im using to boot the phone, and if I re-lock I dont want to be in a position where the RUU fails and I can't get into recovery to re-flash a ROM.
BTW : My hboot version is 1.33.4444
lemonoid said:
UPDATE: I tried running the RUU. I got Error 158. I was watching, and I had the phone in fastboot already, and when the screen said Rebooting Bootloader, then Waiting for Bootloader..... I never saw the phone actually boot to bootloader again, it just stayed black. then the program kept running like the phone was responding, and eventually shot out Error 158. should I follow this method http://forum.xda-developers.com/showthread.php?t=2293919 and relock the bootloader and then RUU? and does anyone know if I will be able to unlock again after I do this?
UPDATE: This is my main question if anyone can help. I have the above RUU, and I got error 158. Since I used moonshine's method, I am under the impression I need to re-lock bootloader, and THEN RUU. However, can someone please tell me if I need a different hboot version or if I'm just fine to go ahead like this? my hboot is below. I ask this because last failed RUU, i had to re-install the ROM im using to boot the phone, and if I re-lock I dont want to be in a position where the RUU fails and I can't get into recovery to re-flash a ROM.
BTW : My hboot version is 1.33.4444
Click to expand...
Click to collapse
Manually boot the phone to the bootloader before you start and it will go. For whatever reason it doesn't do it itself so manually doing it will give you success.
Sent from my HTC6435LVW using XDA Premium 4 mobile app
lemonoid said:
UPDATE: I tried running the RUU. I got Error 158. I was watching, and I had the phone in fastboot already, and when the screen said Rebooting Bootloader, then Waiting for Bootloader..... I never saw the phone actually boot to bootloader again, it just stayed black. then the program kept running like the phone was responding, and eventually shot out Error 158. should I follow this method http://forum.xda-developers.com/showthread.php?t=2293919 and relock the bootloader and then RUU? and does anyone know if I will be able to unlock again after I do this?
UPDATE: This is my main question if anyone can help. I have the above RUU, and I got error 158. Since I used moonshine's method, I am under the impression I need to re-lock bootloader, and THEN RUU. However, can someone please tell me if I need a different hboot version or if I'm just fine to go ahead like this? my hboot is below. I ask this because last failed RUU, i had to re-install the ROM im using to boot the phone, and if I re-lock I dont want to be in a position where the RUU fails and I can't get into recovery to re-flash a ROM.
BTW : My hboot version is 1.33.4444
Click to expand...
Click to collapse
error 158= wrong Hboot ; Solution *You need to Update Hboot to 1.54 in order to Run RUU 3.06
http://forum.xda-developers.com/showpost.php?p=42352912&postcount=4
Jaggar345 said:
Manually boot the phone to the bootloader before you start and it will go. For whatever reason it doesn't do it itself so manually doing it will give you success.
Sent from my HTC6435LVW using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I started the RUU with the phone in fastboot. I'm going to try to upgrade to 1.54 then RUU