Hey, I'm going to make this short because I'm freaking out right now like the noob I am.
I was going through Closeone's downgrade S-OFF/Downgrade Bootloader tutorial and and relocked my phone. OK. I AM ON STOCK, I MADE A BACKUP AS SOON AS I UNLOCKED USING HTC DEV. That's what I restored before I relocked. But I'm still getting a security warning.
THE PROBLEM:
I cannot find the stock RUU for the Evo V 4G anywhere. I've checked here, VMROMs and Phandroid, nothing. They all lead to the same goo.manager link that says the file cannot be found.
PLEASE help, I'm stuck in bootloader and don't know what to do.
Thank you for your time...
OFFICIALLY FIXED... SORT OF
So I relocked using HTC Dev and from there attempted a reboot. It boots!.. up to the end of the animation, from there it stops. So unfortunate. Any ideas?
I cannot get to bootloader by any normal means (via commands or volume rockers).
SOLVED
With some help from LeslieAnn and a couple of other people over at VMroms.com I was able to boot again.
http://www.vmroms.com/index.php?topic=370.0
Will try the wire trick tomorrow.
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've done a bunch of searching on this and finally gave up and decided to ask it here because I can't find anywhere with actual info on it... I was trying to ruu back to the 2.13 base and then reroot from scratch with the new radios but ended up getting stuck in the bootloader with **TAMPERED** **RELOCKED** and **Security Warning** as the headers. It won't let me reboot, it won't let me into recovery, and I'm getting frustrated ... I still have access to fastboot but I'm useless with commands so I haven't been able to fix it. Any help?
Basically, here's the whole details.
I'm on hboot 1.15 s-on, dev-unlocked using regaw's rooting+unlocking tool. The phone had the 2.13 deodexed running, got it from here http://forum.xda-developers.com/showthread.php?t=1860728
Had twrp 2.X (the version before the latest) installed
I tried running the latest ruu.exe on my computer but it kept failing so I looked it up and assumed it must be because I was dev-unlocked.
Went into the bootloader>fastboot and locked it with fastboot oem lock
The phone rebooted into bootloader with the ** Security Warning** header and now I'm stuck...
I would try the downgrade thread.. It's pretty easy and I believe it can be done from bootloader. Then instead of going thru all that hassle, use one of the radio upgrades from captain throw back on themikmik. Just my opinion. Worst that could happen is it doesn't work. Anyone else have feedback on this??
Sent from my EVO using xda premium
sparytrainor said:
I would try the downgrade thread.. It's pretty easy and I believe it can be done from bootloader. Then instead of going thru all that hassle, use one of the radio upgrades from captain throw back on themikmik. Just my opinion. Worst that could happen is it doesn't work. Anyone else have feedback on this??
Sent from my EVO using xda premium
Click to expand...
Click to collapse
I think I figured it out.. I dug a little deeper into some other threads I found on it from people who've done this before. One of them managed to fix it by running the RUU from the bootloader. It took me a bit to realize it had to be in fastboot (facepalm) for it to run. It failed the first time but it looks like its working this time. :good:
Good luck to ya. I hope it works out.. I would still recommend using the hacked upgrades for radios and such.
Sent from my EVO using xda premium
Do you know with the security warning will cause running an RUU to fail?
rubyknight said:
I think I figured it out.. I dug a little deeper into some other threads I found on it from people who've done this before. One of them managed to fix it by running the RUU from the bootloader. It took me a bit to realize it had to be in fastboot (facepalm) for it to run. It failed the first time but it looks like its working this time. :good:
Click to expand...
Click to collapse
I'm in the same boat as you were - can you point me to where/how you got the RUU to run? I've got exactly the same situation, but my RUU (2.13) won't run, either in fastboot or the bootloader.
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.
Dudes,
Too many dead pixels dying on my phone and ATT is sending me another replacement device through warranty. I RUU'd and brought everything back to normal from the CID, hboot, radio, and back to s-on but I cannot get my bootloader to show "Locked". It just shows relocked. Im certain I cannot send it back to them saying relocked. Ive searched and maybe im not searching good enough. Care to share some commands?
"fastboot oem lock" only relocks it.
I restored the phone to 3.17 firmware and RUU but before I update it to the 4.3 id like it to show locked. Any help is appreciated.
Edit: Nevermind I found my answer. Read that this was not possible.
kennypow3rs said:
Dudes,
Too many dead pixels dying on my phone and ATT is sending me another replacement device through warranty. I RUU'd and brought everything back to normal from the CID, hboot, radio, and back to s-on but I cannot get my bootloader to show "Locked". It just shows relocked. Im certain I cannot send it back to them saying relocked. Ive searched and maybe im not searching good enough. Care to share some commands?
"fastboot oem lock" only relocks it.
I restored the phone to 3.17 firmware and RUU but before I update it to the 4.3 id like it to show locked. Any help is appreciated.
Edit: Nevermind I found my answer. Read that this was not possible.
Click to expand...
Click to collapse
If you're s-off it is totally possible there's a command for it built right in to revone.
Sent from my HTC One using Tapatalk
to my knowledge any htc device no longer show "locked" after you unlocked it the first time..it will always show relocked when locked again..
Nick281051 said:
If you're s-off it is totally possible there's a command for it built right in to revone.
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
Too bad i found this out after i s-on'd the phone again lol. So now im in the process of unlocking with rumrunner, then re s-off, then try to "lock" it again. Thanks for the replies guys
kennypow3rs said:
Too bad i found this out after i s-on'd the phone again lol. So now im in the process of unlocking with rumrunner, then re s-off, then try to "lock" it again. Thanks for the replies guys
Click to expand...
Click to collapse
No problem lol good luck
Sent from my HTC One using Tapatalk
Nick281051 said:
No problem lol good luck
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
ok now I have some problems. I unlocked again, s-off'd and then tried to "lock" and s-on again. Something went wrong and now I have a message in hboot that says "security warning" and tampared over the words "locked". I doesnt boot to the rom again just goes to recovery im guessing with the phone and the red triangle. lol Pain in the butt.
To be honest I have no clue how to fix that lol I haven't tried to lock it yet
Sent from my HTC One using Tapatalk
Nick281051 said:
To be honest I have no clue how to fix that lol I haven't tried to lock it yet
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
Theres no rom on the phone now lol.Gotta figure this out! Thanks for your help dude!
Run a ruu that will fix it tampered will be gone too
Sent from my HTC One using Tapatalk
So right now it's unlocked with tampered above an s-off. Is it wise to lock bootloader first before I run ruu? Which order should I go? I know s-on is last for sure...
Sent from my HTC One using Tapatalk
For anyone that's searching for this exact issue ill share what i did to get my phone completely back to stock. I did search the forum but the info was all over the place and in my opinion it was as clear as "I" needed it to be hence me creating a thread for something so simple. Ok as follows here is what I did step by step.
First I had to make sure I installed HTC sync of course. At the moment my firmware was 3.57 and I downloaded the 3.17 RUU.exe from HTC.com
Your firmware *HBOOT* and the RUU you download have to match or you will get errors. Well, least I did.
Make sure you download some type of toolkit it would make life a lot easier. I used this one it worked like a charm!
At the moment, my phone is bootloader unlocked and s-off fyi.
Next, Use the tool to "lock" your bootloader first not "re-lock" just "lock". If you're having issues push revone again and follow commands on toolbox.
Now, check hboot to see if it shows "locked" if it has tampered above locked that's ok the RUU will take care of that.
Run, the RUU, make sure usb debugging on and htc sync already installed. Let it run.
After its done, start up phone again, turn off fastboot under "power" and turn usb debugging on again.
Start up toolkit, look to the right and it will say "s-on" device. You can only s-on after you've ran the RUU and are on stock hboot and rom.
Check Hboot again and it should read "Locked" and now "s-on".
Phone now ready to send back for warranty or etc.
Hope this helps anyone that searches. I found a few thread via google and they helped out a bunch.
I rooted my HTC One M7 (AT&T) and am tired of playing around. I am trying to get as close back to complete stock as I can. I re-locked my bootloader, I am S-On, I followed all the instructions I could find online, but when I try to use the ruu exe, I get stuck at "sending 1/6". I am not positive if I am using the correct ruu but I am pretty sure. Bootloader says my OS is 4.18.502.7 (4.20.502.1) and the ruu I downloaded is "RUU_M7_UL_K44_SENSE55_MR_Cingular_US_4.18.502.7_R10_Radio_4T.24.3218.09_10.26.1718.01L_release_356565_signed_2" I don't know what I should try now. I have managed to keep myself unbricked but I figured I should ask before I do something dumb. I want to go back to stock so I can receive OTA updates through the phone, and not have any root capabilities. My HBOOT is 1.56.0000 if that makes a difference. Sorry if this makes no sense, as I am new and trying to make sense of it all.
Any help is appreciated and if this is in the wrong spot, I am sorry in advance.