Hey guys, i updated my Evo 3D with the OTA update that's posted in the development section. Now everything is fine except I don't have WiFi. My Wifi just says error...doesn't even try to start.
I tried to use the RUU to downgrade back to shipped/stock ROM but it gives me the 140 Invalid bootloader error. This is because the hboot got upgraded to 1.40 from 1.30. I am assuming to go back to the original shipped ROM, I need to downgrade hboot back to 1.30.
Any ideas? I've created a Goldcard also and tried to apply the OTA update using that, but I get some "invalid operations.....boot successful" error and it doesn't even update anything...just reboots. I'm not sure if I created the goldcard correctly or whats going on. But right now I have no Wifi and I'm out of country so I have no cellular data either and I can't go to Sprint store either.
Please help!
I've tried restoring my HTC One to stock rom for more than a day now with no luck.
I converted my ATT HTC One to stock Android 4.3. I've tried flashing several stock roms i found from xda developers and all of them "sucessfully install" but the phone never goes past the green bar. The green bar gets to full but the phone never reboots after that. I've also tried to change CID. I've changed it to the stock, CWS__001, and Supercid and that doesn't work either. I downloaded the ruu cingular.exe file and it fails to run. It gives me an error saying Please make sure you have finished any previous setup and closed other applications. My hboot is currently 1.54 and ive restored it to 1.44 but that didnt make a difference either.
Any help would be greatly appreciated, thanks!
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.
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
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?