Hey guys I've been trying to get my phone reset back to stock, I was coming from a rooted stock 3.15 and did what this thread said http://forum.xda-developers.com/showthread.php?t=1706070 to get the RUU to run, after running it. My phone was restored to normal except my sdcard still had everything on it (I think this is expected) and the main issue is that SuperSU was still installed. While my phone was at this state my girlfriend changed the theme of the phone to something else, the only reason I'm saying this is because after running VipeRUU the theme was still the one that was set.
So after that I booted up my phone and ran VipeRUU http://forum.xda-developers.com/showthread.php?t=2197909 and still it worked but again SuperSU was still installed.
Going into my bootloader at this point reveals Tampered and Relocked and S-On, hitting recovery takes my phone to the htc boot logo then a black screen with a red exclaimation mark over a phone. Hopefully someone can help me getting my phone back to 100% stock.
I am currently trying the fix in the sticky with the 3.15 ruu.
After flashing the zip like it says to, the htc sign has a green bar under it that looks nearly full. I tried to run the RUU at this point and it went a fair amount through and stopped eventually due to a usb connection error (I think when the phone switched into fastboot). So I did the fix again and when it got to the green bar I rebooted the phone and am now running the RUU.
Blowdryer said:
Hey guys I've been trying to get my phone reset back to stock, I was coming from a rooted stock 3.15 and did what this thread said http://forum.xda-developers.com/showthread.php?t=1706070 to get the RUU to run, after running it. My phone was restored to normal except my sdcard still had everything on it (I think this is expected) and the main issue is that SuperSU was still installed. While my phone was at this state my girlfriend changed the theme of the phone to something else, the only reason I'm saying this is because after running VipeRUU the theme was still the one that was set.
So after that I booted up my phone and ran VipeRUU http://forum.xda-developers.com/showthread.php?t=2197909 and still it worked but again SuperSU was still installed.
Going into my bootloader at this point reveals Tampered and Relocked and S-On, hitting recovery takes my phone to the htc boot logo then a black screen with a red exclaimation mark over a phone. Hopefully someone can help me getting my phone back to 100% stock.
I am currently trying the fix in the sticky with the 3.15 ruu.
After flashing the zip like it says to, the htc sign has a green bar under it that looks nearly full. I tried to run the RUU at this point and it went a fair amount through and stopped eventually due to a usb connection error (I think when the phone switched into fastboot). So I did the fix again and when it got to the green bar I rebooted the phone and am now running the RUU.
Click to expand...
Click to collapse
You will need to get s-off again and then use VipeRuu to remove s-off and the tampered message... I know it doesn't make sense but that's the only way to do it since there is no official ruu for 3.16...
Sent from my EVO using xda app-developers app
Related
Well I got myself into a real pickle here. I was trying to get the newer OTA with my unlocked rooted 3D I tried everything I have here on how to do it but now my phone just reboots itself after it get to the sprint screen sometimes it does make it to where is show the info bar at the top with the time but reboots soon after. I have tried a stock recovery and a new OTA RUU using hboot and the PG86IMG.IMG which did install at hboot but I still have the same issues. Any ideas on how to at least get back to normal?
mviars said:
Well I got myself into a real pickle here. I was trying to get the newer OTA with my unlocked rooted 3D I tried everything I have here on how to do it but now my phone just reboots itself after it get to the sprint screen sometimes it does make it to where is show the info bar at the top with the time but reboots soon after. I have tried a stock recovery and a new OTA RUU using hboot and the PG86IMG.IMG which did install at hboot but I still have the same issues. Any ideas on how to at least get back to normal?
Click to expand...
Click to collapse
What hboot are you ? Also what software are you on 2.08 ? You are CDMA I am guessing? If all else fails man boot into your recovery and wipe just not your SD card and go back to hboot relock your phone and use the latest 2.17 ruu exe.. Works every time and then root again and your set... This info is for CDMA only Not GSM>>>
THanks reaper. I was on hboot 1.5 and CDMA sorry for not stating. I ended up just taking it back to sprint and they gave me a new phone which I am actually happy about because of a few blemishes I had on the phone. I think I will wait till after ICS and see if they can get it rooted. I really only want the ability to wireless tether.
Again thanks for the reply
how does this happen? solutions? im also not able to flash an ruu for some reason...stumped and have been working on this for an hour or so
rezin said:
how does this happen? solutions? im also not able to flash an ruu for some reason...stumped and have been working on this for an hour or so
Click to expand...
Click to collapse
Tampered is normal. Did you try flashing it with a ph98img, or as an .exe
It happens after you unlock and install a custom recovery I believe. Are you re-locked when you try to ruu?
Sent from my ADR6425LVW using Tapatalk 2
big_mike_2k6 said:
And are you re-locked when you try to ruu?
Sent from my ADR6425LVW using Tapatalk 2
Click to expand...
Click to collapse
Yeah make sure your bootloader is relocked
i was in the middle of doing s-off when the phone froze and corrupted the mem card...so i tried redoing the whole process over and i havent been able to get past the hboot...im still unlocked and have access to recovery and hboot but i cant flash a rom and boot into it...i cant run an ruu but the phone is not technically bricked...its an odd predicament...i just flashed a rom and i still cant get it to get past the hboot
Have you tried re-locking the bootloader and then run the ruu?
Sent from my ADR6425LVW using Tapatalk 2
i was hesitant to do anything else aside from the things i mentioned incase i was unable to get those back...gonna let the phone recharge and try again later tonight...any ideas are welcome in the mean time...and ill go ahead and relock it and try later
rezin said:
i was hesitant to do anything else aside from the things i mentioned incase i was unable to get those back...gonna let the phone recharge and try again later tonight...any ideas are welcome in the mean time...and ill go ahead and relock it and try later
Click to expand...
Click to collapse
just run the latest ruu in hboot if you are s-off it will make the phone like it was from factory.
if you are s-on but unlocked you will need to do the "fastboot oem lock" then runn the ruu.
in both cases the ruu will nuke the internal storage. first pass with install a new hboot and stock recovery along with 2 other items, then the phone will reboot into fastboot and install the rest. i recommend that you have a 60% or more battery life.
synisterwolf said:
just run the latest ruu in hboot if you are s-off it will make the phone like it was from factory.
if you are s-on but unlocked you will need to do the "fastboot oem lock" then runn the ruu.
in both cases the ruu will nuke the internal storage. first pass with install a new hboot and stock recovery along with 2 other items, then the phone will reboot into fastboot and install the rest. i recommend that you have a 60% or more battery life.
Click to expand...
Click to collapse
Yeah I already got it up n running...between being unlocked and having a slightly dead battery I wasn't even being given the option to run an ruu...its running now but I still need to do s-off again, and of course my sd card is corrupted so ill work on that tonight
The same thing happened to me, glad I found your thread! Were you trying to s-off on the official ICS? That's what I was trying. I ran the .12 RUU and had unlocked, rooted and was trying to get S-off. I did the wire trick I was getting an HTC logo instead of Jbear logo. Right now I just relocked and it's running the RUU so I hope I can get back up and running.
I guess I should have just S-offed before running the ICS RUU
Edit: I am back up and running!
willdo7474 said:
The same thing happened to me, glad I found your thread! Were you trying to s-off on the official ICS? That's what I was trying. I ran the .12 RUU and had unlocked, rooted and was trying to get S-off. I did the wire trick I was getting an HTC logo instead of Jbear logo. Right now I just relocked and it's running the RUU so I hope I can get back up and running.
I guess I should have just S-offed before running the ICS RUU
Edit: I am back up and running!
Click to expand...
Click to collapse
Hey, I didn't have to do this, but if you noticed, controlbear makes backup copies of stuff like boot.img (forget what else) and puts them on your computer. If you crap out you ought to be able to fastboot flash boot [bootimgfilename.img] and be able to boot up your phone. I saw where one person did this to get going again after a failed soff.
Yeah well happened in my case is that I was already s-offed and then I flashed the ruu to go back to stock...then I relocked my phone cuz I'm having an issue with one of the pins on phone (the terminal that connects to battery).so I was gonna get it exchanged, I wanted it to look absolutely stock...so the "relocked" status wasn't good enough, so someone suggested doing s-off again so it will show locked in hboot...well that's where everything went wrong, the phone froze at the wire trick and then the entire memory card was corrupted which is normal...so when I went to redo the whole s-off procedure again I kept rebooting into the blank screen with the arrow...could not get past that, so I resorted to putting my real sd card in...I had no backups for that card cuz that one has my actual personal stuff so I figures it'd be ok since I used a spare to do s-off anyway...well upon powering on the phone it was also corrupted...so Ive actually given up on s-off and getting my phone restored and replaced for a while...I don't know why s-off has always given me problems I've watched and read every vid or post about s-off and am in no way tech illiterate but I've always had problems with s-off (i lost all my pics and documents the first time I did s-off even thought I backed everything up cuz the only way to get it right was to eliminate every file in the folder and rerun it again cuz it didn't back up my sd correctly If at all)...its beyond infuriating
well that didnt last long...i just unlocked and s-offed my phone again, only to be returned to s-on and fully locked (indistinguishable from brand new in box), as i originally intended...im gonna miss this particular phone but it has to be done
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, 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.
So yesterday I had my Aria in my pocket and I guess the power button got nudged and the screen turned on, lo and behold I pull my phone out of my pocket to find the lovely words written on the screen that too many pattern attempts have been attempted and that the device is locked. Only problem is I use this phone for everything but the phone function, I don't even have a sim in there. So with WiFi off, and no mobile network I was stuck for a bit. But then I finally sat down with it and luckily I had kept USB debugging on so I used adb to hack it. And that is where my urgent problem starts. After finally unlocking it I decided to might as well upgrade it, it was running 2.0.2 I believe Liberated ROM with CWM. So I started browsing around because I haven't really worked with this phone before all that much, I ended up reflashing to stock rom and then was going to use a nifty tool to get my hboot to 1.02, well it worked, the nifty tool flashed my hboot alright, along with my ROM and everything else there was. I am now stuck with a brick, the phone goes to the boot logo and then reboots... over and over and over until I pull the battery. I was charging the phone the whole time while working on it and after the tool was done flashing the hboot I unplugged the phone and a long list of errors ran down the screen of files that the OS was missing. I can get into fastboot, haven't had luck with any reflashs, adb is dud (while in recovery computer recognizes the adb connection but adb only lists the device as inactive. Ever since I lost my Inspire 4G this was my only working mobile device. If you have any tips tricks or clues as to how or if it is possible to come back from this destruction I am all ears.
Thank you in advance :fingers-crossed:
To clarify a bit further, the part that screwed me was the Upgrade HTC Gratia HBOOT for AlpharevX S-OFF tool. It was chugging along just fine up until the very end. The original sites listed for making a gold card are all dead but I managed to find a working one. Now I am trying to figure out what went wrong and why.
LIBERTY PVT SHIP S-ON
HBOOT-1.02.0000
MICROP-031b
TOUCH PANEL-STN21_03
RADIO-7.13.35.13
Nov 4 2010,23:12:58
The time and date are frozen
First you should S-OFF your phone with revolutionary. Then you need to flash a working recovery image and reflash ROM from there. Should work. If this still doesn't work, flash a modified hboot from the Development forum and see if you have any luck with that...
dansou901 said:
First you should S-OFF your phone with revolutionary. Then you need to flash a working recovery image and reflash ROM from there. Should work. If this still doesn't work, flash a modified hboot from the Development forum and see if you have any luck with that...
Click to expand...
Click to collapse
I cannot get revolutionary to find the device, the system version is 2.37.709.11 and I cannot do anything, if I try flashing anything the sig verification always fails.
(EDIT: Well I got lucky, found an asian RUU with same version, reflashed phone, S-Off, flashed unofficial CWM recovery and unofficial cyanogen 11.)
The problem I was having with revolutionary not recognizing the device was because my hboot version was too old (0.57). I used this AT&T Update package to get back to stock 2.2 and revolutionary worked straight away.
HTC_Aria_for_ATT_Android_2.2_ROM_Update.exe
http://www.mediafire.com/download/mch2657rdy8aqct/HTC_Aria_for_ATT_Android_2.2_ROM_Update.exe