I also posted this in the Q&A section, but I am getting desperate.
ok,
So like an idiot, i began the S-OFF process without reverting my SuperCID. I cannot get past step 8, and i am having errors flashing my RUU.
Right now i cannot get past the bootloader. If i try to fastboot reboot, it takes me back to the bootloader. If i try a reboot, it takes me back to the bootloader.
Is there something that i can flash to get me back and running? I have tried numerous things, and i really need my phone back tonight. Grandfather is in the hospital, and i have no way to contact anyone except through facebook / email.
does anyone have some ideas, or know what i need to do? I honestly dont care about root or s-off, i can do that later. Right now i just need a bootable phone.
help!
squeezyb said:
I also posted this in the Q&A section, but I am getting desperate.
ok,
So like an idiot, i began the S-OFF process without reverting my SuperCID. I cannot get past step 8, and i am having errors flashing my RUU.
Right now i cannot get past the bootloader. If i try to fastboot reboot, it takes me back to the bootloader. If i try a reboot, it takes me back to the bootloader.
Is there something that i can flash to get me back and running? I have tried numerous things, and i really need my phone back tonight. Grandfather is in the hospital, and i have no way to contact anyone except through facebook / email.
does anyone have some ideas, or know what i need to do? I honestly dont care about root or s-off, i can do that later. Right now i just need a bootable phone.
help!
Click to expand...
Click to collapse
Do you have recovery installed, and remember you have to relock your device for ruu to work
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
squeezyb said:
I also posted this in the Q&A section, but I am getting desperate.
ok,
So like an idiot, i began the S-OFF process without reverting my SuperCID. I cannot get past step 8, and i am having errors flashing my RUU.
Right now i cannot get past the bootloader. If i try to fastboot reboot, it takes me back to the bootloader. If i try a reboot, it takes me back to the bootloader.
Is there something that i can flash to get me back and running? I have tried numerous things, and i really need my phone back tonight. Grandfather is in the hospital, and i have no way to contact anyone except through facebook / email.
does anyone have some ideas, or know what i need to do? I honestly dont care about root or s-off, i can do that later. Right now i just need a bootable phone.
help!
Click to expand...
Click to collapse
SuperCID likely isn't your issue. If you get a SuperCID error just flash the RUU again. The instructions say something about error 90, and I think the error code is 92. I got the error the first flash, flashed again and it went on just fine.
its all good now, and superCID was the problem. make sure you revert back before trying to s-off. i missed that step in the process and about pooped my pants when it wasnt working.
Related
I have the Wind Amaze 4G
I tried to get S-off today and being unsuccessful I ended up at the screen where it shows the 3 arrows (2 in a circle and 1 pointing at the phone). I am assuming my stock rom got corrupted.
I can still get into fastboot and recovery (have CWM installed). Bootloader is unlocked (I can still lock/unlock it). I can get into CWM with the bootloader unlocked.
What I want to do is to revert back to stock and found a Wind/Globalive rom, but it's in an exe file. I ran it, but got back an error saying bootloader version incorrect.
I can't find any stock Wind zips...according to juopunutbear's instructions I need the stock rom...
Any help would be appreciated.
Wind's RUU is on the first link:
http://forum.xda-developers.com/showthread.php?t=1570807
I have that, but when I used it (with bootloader relocked), it spits out an error saying Bootloader version error and exits
Then why don't you just keep trying to get s-off, some people said they had tried for hours before they succeeded. And btw, how far you get before s-off install fails?
At the wire trick when it restarted and said failed.
I tried to complete s-off and where it says to do the wire trick, no matter what I did it just kept repeating "Do the wire trick now!".
Right now I'm downloading a custom rom (Energy 3.10) and see if I can flash it on with CWM then try to revert back to stock using that Wind/Globalive exe file and go from there.
I guess while I am waiting on the download I'll keep going with the s-off.
If it works, then I'm flashing the ICS update onto the phone directly and be done with it.
What I don't understand is why I can't revert back to stock in the mean time.
Did you see this video?
Edit: May be something's wrong with the RUU. Actually, there was a flame war recently because someone had posted a broken RUU for T-Mobile, but no one mentioned anything about the Wind one, so I assume its working fine... Go to xboarder56's website an ask him, he was the one who was providing the RUUs for the community
First I'd like to thank you for helping. I really appreciate it.
Now I am attempting the s-off again, got a bit further except after the wire trick it says cannot find device.
As for xboarders site, I can't seem to find it...
No problem, I'll pm you x's site, dont think Im allowed to paste it here, its a long story...
so after several tries I managed to get s-off, I guess my timing was just off the first time and the time where it looked like it looped was me not making proper contact with the wire.
Few other unsuccessful attempts were poor timing, got it right finally after like 6 tries.
Got ICS loaded and s-off!!!!
Now to unlock and re-root then debloat this rom!
THANK YOU SO MUCH FOR YOUR SUPPORT!!!
Im glad it worked out, man, cheers
P.s. Also, you dont need to unlock the bootloader, the best way to install ICS is the one described here, thats how I did it, got ENG hboot, and worked like a charm...
I rooted my evo 4g lte. I was having issues with data today and updating the profile. so I was going to unroot and try it stock. I relocked the bootlader, and somehow my rom image is gone!!!! i cant flash the ruu, it keeps failing error 155. someone please help me
Wrong thread. Need to be posted in q&a
sent from my EVO LTE with it's security flags down.
jrgalioto said:
I rooted my evo 4g lte. I was having issues with data today and updating the profile. so I was going to unroot and try it stock. I relocked the bootlader, and somehow my rom image is gone!!!! i cant flash the ruu, it keeps failing error 155. someone please help me
Click to expand...
Click to collapse
Similar thing happened to me. I have hboot 1.15. I relocked the the phone ran the RUU. Phone booted up normal with the everything stock. I then took the OTA and when it rebooted it was updating then it rebooted and the phone never turned on again. I sent it to HTC for warranty. They will get it tuesday. I'll see how this goes.
Okay guys... Enough with the flaming. If you can help, post! If not, don't. Grow up. It was posted in the wrong section. Use the report button in the upper-right corner of the post and report it.
Now, let me see if I can actually help you.
You're getting this error because you're trying to flash an older RUU on the phone than what's already on there. You'll need to flash the same RUU version or higher. If you took the latest OTA update, there may not be one available yet. I'd suggest you go through the HTCDev unlock again until that RUU makes it to the internet.
Team Nocturnal posted a couple of the older RUU versions.
http://www.androidfilehost.com/main/EVO_4G_LTE_Developers/Team.Nocturnal/RUU/
~co~
closeone said:
Okay guys... Enough with the flaming. If you can help, post! If not, don't. Grow up. It was posted in the wrong section. Use the report button in the upper-right corner of the post and report it.
Now, let me see if I can actually help you.
You're getting this error because you're trying to flash an older RUU on the phone than what's already on there. You'll need to flash the same RUU version or higher. If you took the latest OTA update, there may not be one available yet. I'd suggest you go through the HTCDev unlock again until that RUU makes it to the internet.
Team Nocturnal posted a couple of the older RUU versions.
http://www.androidfilehost.com/main/EVO_4G_LTE_Developers/Team.Nocturnal/RUU/
~co~
Click to expand...
Click to collapse
Here is the issue with that though. When i run the RUU, it says my current image is........nothing. i have tried to flash the newest and the oldest versions.
jrgalioto said:
Here is the issue with that though. When i run the RUU, it says my current image is........nothing. i have tried to flash the newest and the oldest versions.
Click to expand...
Click to collapse
Hi there jrgalioto. Can you do me a favor, and boot into your bootloader for me? I'd like you to check the green text.
What Radio version does it say you have?
Also, if you can connect the phone up to your computer and run the fastboot command (in FASTBOOT USB mode):
Code:
fastboot getvar mainver
What number comes back? (If you can't run the command, don't worry about it)
---
If I might ask, why did you relock the phone?
---
I'm looking into trying to get you a link to a current RUU. One has been posted, but I can't access it because of Filefactory's restrictions. Hopefully somebody will post a mirror to the download soon.
~co~
closeone said:
Hi there jrgalioto. Can you do me a favor, and boot into your bootloader for me? I'd like you to check the green text.
What Radio version does it say you have?
Also, if you can connect the phone up to your computer and run the fastboot command (in FASTBOOT USB mode):
Code:
fastboot getvar mainver
What number comes back? (If you can't run the command, don't worry about it)
---
If I might ask, why did you relock the phone?
---
I'm looking into trying to get you a link to a current RUU. One has been posted, but I can't access it because of Filefactory's restrictions. Hopefully somebody will post a mirror to the download soon.
~co~
Click to expand...
Click to collapse
I relocked because I needed to bring it back to Sprint for service, so I needed to unroot it, because I wasn't receiving data to it. But I got it figured out now. I was able to unlock the bootloader again and my recovery was still there. So i reflashed a custom ROM, so I at least had something on my phone. When I called Sprint, I told them it was not a phone issue, they updated my username in the system, then I was able to ##72786# to get the hands free activation to complete without error 1012. So I am now back in business. However, If I ever do have to unroot again, I will be in the same boat.
jrgalioto said:
I relocked because I needed to bring it back to Sprint for service, so I needed to unroot it, because I wasn't receiving data to it. But I got it figured out now. I was able to unlock the bootloader again and my recovery was still there. So i reflashed a custom ROM, so I at least had something on my phone. When I called Sprint, I told them it was not a phone issue, they updated my username in the system, then I was able to ##72786# to get the hands free activation to complete without error 1012. So I am now back in business. However, If I ever do have to unroot again, I will be in the same boat.
Click to expand...
Click to collapse
For future ref...sprints tep policy covers rooted phones
Of course the first variable that could be the issue in any given situation is the fact that a phone is rooted
Sent from my SPH-L710 using xda app-developers app
00mred00 said:
For future ref...sprints tep policy covers rooted phones
Of course the first variable that could be the issue in any given situation is the fact that a phone is rooted
Sent from my SPH-L710 using xda app-developers app
Click to expand...
Click to collapse
That was the 1st thought I had. What if the root is causing the issue. It, however was not the case. and all is now right with the world, and I am no longer a brick...for now...
jrgalioto said:
That was the 1st thought I had. What if the root is causing the issue. It, however was not the case. and all is now right with the world, and I am no longer a brick...for now...
Click to expand...
Click to collapse
Hi jrgalioto,
I was able to get a link to the new RUU for you. This one should work fine for you.
~co~
Yep...... sprint doesnt care that you're rooted.
I frequently tell them mine is so they dont go messing with things they shouldnt be
OK I just cleaned this thread of a bunch of GARBAGE.
If you don't want to help, post on a blog.
The guy is looking for help.
Seriously .
il Duce said:
OK I just cleaned this thread of a bunch of GARBAGE.
If you don't want to help, post on a blog.
The guy is looking for help.
Seriously .
Click to expand...
Click to collapse
Sorry duce
Sent from the depths of hell
Hey I try to help and I have even written a guide with a ton of info, I even went so far as to write down troubleshooting stuff and they still post the exact same stuff over and over, some times its a bit frustrating. I even gave instructions on what they need to do should they completely ruin the file tree, when have you seen anyone completely destroy the internal memory lol
closeone said:
Hi there jrgalioto. Can you do me a favor, and boot into your bootloader for me? I'd like you to check the green text.
What Radio version does it say you have?
Also, if you can connect the phone up to your computer and run the fastboot command (in FASTBOOT USB mode):
Code:
fastboot getvar mainver
What number comes back? (If you can't run the command, don't worry about it)
---
If I might ask, why did you relock the phone?
---
I'm looking into trying to get you a link to a current RUU. One has been posted, but I can't access it because of Filefactory's restrictions. Hopefully somebody will post a mirror to the download soon.
~co~
Click to expand...
Click to collapse
Any luck on the mirror for the new RUU download? I'm using the latest one I can find and I am stuck and can't get my phone to reboot, shutdown or anything. I can't run fastboot either. all I see is ***Tampered*** unlocked*** ....RUU update fail!
My phone won't respond to the volume down and power button either.
any suggestions?
for some reason i'm having a big problem going back to stock.
here's my current set up...
tampered
unlocked
s-on
hboot 1.12.0000
TWRP recovery
Stock with Goodies 3.40
all i'm trying to do is get back to stock!
here's what i've done so far...
1. connected phone to PC with USB Debugging on and ran RUU of the latest release
2. phone reboots and goes to the black HTC screen and just gets stuck there forever
then I realize I have to relock it so I relock and then reboot but then it just gets stuck in bootloader and won't go into OS or recovery...just reboots to bootloader when I try to do anything. plus when I try to do adb or run RUU from PC, the PC doesn't think the phone is actually connected to it.
so i've re-unlocked and now it goes back to OS but my whole point is to go to stock and unroot...what the hell am I doing wrong? I'm about to just throw the phone into the ground and get a new one since I have squaretrade warranty.
I know many of you are probably just thinking...why doesn't he s-off? because i don't have access to 32 bit windows 7 PC and figured just unrooting and then updating to latest RUU and then rerooting/unlocking would be sufficient.
THANKS in advance for any advice...
maybe
u might watch this video. i did the same this morning. made it easy for me anyway.
http://www.qbking77.com/how-to-unroot/unrootunbrick-the-htc-evo-4g-lte.html
all his videos are great.
that's what I started with...relocked and then ran RUU but it just gets stuck at the black HTC logo screen forever...like we're talking over an hour. the thing says it may take 10 minutes or so...i'm not getting anything status update...it just gets stuck there...
trsix said:
u might watch this video. i did the same this morning. made it easy for me anyway.
http://www.qbking77.com/how-to-unroot/unrootunbrick-the-htc-evo-4g-lte.html
all his videos are great.
Click to expand...
Click to collapse
umm
maybe instead of the latest ruu u should run the 1.12
http://www.androidfilehost.com/?fid=9390326628153819199
then again i'm still learning and don't know jack sheet
mine was 2.09 thats what i ran worked fine
Maybe Try Again
It took me a few tries or so, to get the RUU to work, but it finally worked.
One thing I realized is that I had to flash stock recovery prior to relocking, otherwise you're wasting your time, afaik.
...which leads me to how I came across this thread. I can't remember where I found stock recovery. I've been searching xda almost an hour. Can anyone tell me?
Dr Lexus said:
It took me a few tries or so, to get the RUU to work, but it finally worked.
One thing I realized is that I had to flash stock recovery prior to relocking, otherwise you're wasting your time, afaik.
...which leads me to how I came across this thread. I can't remember where I found stock recovery. I've been searching xda almost an hour. Can anyone tell me?
Click to expand...
Click to collapse
Click the link in my sig
Sent from my PoS MoPho
Ok, so I've been rooted but for he most part stock. The last OTA kept failing to download so I relocked my bootloader, used the ruu update tool from android police, accepted the update, but had the genius idea to run my nandroid restore after. Since then I have not been able to boot up and my efforts to fix the problem have only made it worse. I can no longer get into recovery and when I try it gives me a security warning. I am at a loss and miss my phone, forced to use Iphone 4 as back up and I refuse to learn how to use it. Please give ideas on how to fix in noob language as I am obviously not an expert.
fivedezs said:
Ok, so I've been rooted but for he most part stock. The last OTA kept failing to download so I relocked my bootloader, used the ruu update tool from android police, accepted the update, but had the genius idea to run my nandroid restore after. Since then I have not been able to boot up and my efforts to fix the problem have only made it worse. I can no longer get into recovery and when I try it gives me a security warning. I am at a loss and miss my phone, forced to use Iphone 4 as back up and I refuse to learn how to use it. Please give ideas on how to fix in noob language as I am obviously not an expert.
Click to expand...
Click to collapse
just ruu again. make sure your bootloader is locked and start from square one.
place ruu on root of sd
reboot hboot
let it run twice.
synisterwolf said:
just ruu again. make sure your bootloader is locked and start from square one.
place ruu on root of sd
reboot hboot
let it run twice.
Click to expand...
Click to collapse
I could use help trying to find the RUU I need, my search has been fruitless. What I have is a tool that updates my RUU for me and it only works when my phone successfully boots. I tried using it from the bootloader menu and that gave me a security warning.
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