I seriously need help getting back to stock. I'm trying to use RUU 2.35. I double click and it acts like it's about to do something then the screen goes away and nothing happens.
Ok, I figured out why it wasn't allowing me to get passed that screen. But I have no encountered another problem. When it gets to the point where it verify's my android information, nothing shows up in the image version. I went through the rest of the steps, it said that it had failed. Please help, thanks.
Hboot needs to match, if you installed the jelly bean ota, you can't flash the 2.35 ruu because of the lower hboot version.
Have you flashed the standard recovery and re-locked the bootloader.
Related
Sorry as I know these answers are out there, but I have been trying things for 2 days to no avail.
My end goal is a CM9 ROM on my sensation
I used Hasoons idiot proof utility, but apparently I am a super idiot
I clicked on install drivers, nothing happened, I assumed that I had everything I need from the sensation I had and rooted back in Oct 2011, so then I click "S-Off", the cmd box popped up and immediately went away (yes I went to the site and dl'ed the SOFF program).
after an hour of trying to figure that out I ended up skipping that and just going to HTC Dev and unlocked the boot loader. Thank went fine.
Installed CWM, that went fine, I think. If I hold Vol Down and Power it takes me to hboot not CWM? I can get to CWM by hitting recovery in HBOOT but I thought I remember Vol Down +Pwr took me straight to CWM.
THEN THINGS WENT WRONG.
I got a little greedy and tried to immediately flash a CM9 ROM, it flashed ok, but never got past the white HTC screen. So I tried to back pedal but flashing what I thought was a stock IMG file of GB. All the ones I trired would parse but do nothing after that.
Do I need to relock the boot loader to flash stock GB? and if so where is the Stock US T-mo GB IMG?
If I were to get it back to stock and did an HTC OTA ICS update, would I then be able to re-unlock and then install CM9?
Can anyone also help with S-Off, If I remember correctly, my hboot is 1.118??
I also cannot seem to find the latest firmware for CM9 as the ones I clicked on gave me 404 website errors.
Again I apologize as I am sure the answer is easy, but I spent 4 hours on this and just need some help.
Thanks
mikeschevelle said:
Sorry as I know these answers are out there, but I have been trying things for 2 days to no avail.
My end goal is a CM9 ROM on my sensation
I used Hasoons idiot proof utility, but apparently I am a super idiot
I clicked on install drivers, nothing happened, I assumed that I had everything I need from the sensation I had and rooted back in Oct 2011, so then I click "S-Off", the cmd box popped up and immediately went away (yes I went to the site and dl'ed the SOFF program).
after an hour of trying to figure that out I ended up skipping that and just going to HTC Dev and unlocked the boot loader. Thank went fine.
Installed CWM, that went fine, I think. If I hold Vol Down and Power it takes me to hboot not CWM? I can get to CWM by hitting recovery in HBOOT but I thought I remember Vol Down +Pwr took me straight to CWM.
THEN THINGS WENT WRONG.
I got a little greedy and tried to immediately flash a CM9 ROM, it flashed ok, but never got past the white HTC screen. So I tried to back pedal but flashing what I thought was a stock IMG file of GB. All the ones I trired would parse but do nothing after that.
Do I need to relock the boot loader to flash stock GB? and if so where is the Stock US T-mo GB IMG?
If I were to get it back to stock and did an HTC OTA ICS update, would I then be able to re-unlock and then install CM9?
Can anyone also help with S-Off, If I remember correctly, my hboot is 1.118??
I also cannot seem to find the latest firmware for CM9 as the ones I clicked on gave me 404 website errors.
Again I apologize as I am sure the answer is easy, but I spent 4 hours on this and just need some help.
Thanks
Click to expand...
Click to collapse
Please join this IRC Channel: #helpmenow
I could explain here, but it's a little tedious.
I had CM10 Nightlies running, and I decided I just wanted to be done and go back to full unrooted stock. So I downloaded the 1.85 RUU, relocked the BL, and ran the RUU.exe... After that it was just fine, but I realized I missed a lot of the basic things that come from having root. So I rerooted and installed TrickDroid... But The page I was on didn't clearly explain that it was for the European HTC One S. Trick Droid 8.1.0. So I flashed this, and upon running, it was messing up in a lot of ways. Can't explain it, but the point is that it was not something I'd use as a daily driver. I then went to do a full wipe and flash Team Venom's Sense ROM. Which I did.... but the wifi didn't work. AT ALL. Just doesn't turn on. I thought it was the ROM, so I wiped and installed MIUI. (Which I'm loving) But again, no wifi. PLUS Camera crashes. No error message, just closes. Can't use it at all. I realized my mistake with TrickDroid, and tried to reflash the RUU (after flashing a stock ROM and relocking BL etc) But it gives me ERROR 155 (UNKNOWN ERROR) - On my phone it says "Hboot version is too new!" It seems to me, that my Hboot is now the one from 2.35 RUU (Which noone officially has released) The only way I can imagine getting this, is with the european ROM. Can it do that? I have Hboot 1.14.0004
I'm out of ideas, and very very frustrated. I can't flash an RUU. And we don't have S-OFF, so downgrading my hboot isn't an option, right?
Please, anybody that can help will definitely get my verbal thanks as well as click on the button. I need someone to sort this out with me.
Thanks.
EDIT: I changed my CID to SUPERCID and flashed the European 2.21 RUU and I'm all set. Thanks a TON to this thread - http://forum.xda-developers.com/showthread.php?t=1927939
Not quite the same beginning situation, so hopefully people with MY situation will find this post and be helped!
I have RUU which I used a few times, this time one pops me "error 155" and check the CID still gives me H3G-UK H3G__001 but as I check the version does not show any information. Already changed the cables, I have uploaded the drivers, I downloaded the new files from the RUU.
TEMPERED
RELOCKED
VLE PVT SHIP S-ON RL
HBOOT-1.14.0002
RADIO-1.08es 50.02.16
PpenDSP-v29.1.0.45.0622
eMMC-boot
Jun 11 2012, 14:36:28
If anyone can solve this riddle?
Ironic this happened to you because I was just trying to go back to ( which I have successfully have done several times before ) my stock RUU file. I am also getting the ERROR 155. Maybe our issues are the same.
I have :
- Gone back to a stock rom
- Relocked Bootloader
- tried to run RUU from within Fastboot ( and every other way I could imagine )
Still get the ERROR 155! The only difference now is that I am coming back off a Jelly Bean ROM ( every other time I was on a Sense 4.04 based ROM)
Could that be the issue? Did it update my HBOOT to one that my stock RUU won't recognize? That seems to be were the RUU fails everytime. It blinks fast but I do beleive the RUU installer says something about HBOOT before it craps out.
Any suggestions or help would be appreciated by us both I presume!
Thanks! :fingers-crossed:
Have you checked the ruu log on your c drive?
The utility usually saves one there.
That may provide some incite.
Sent from rooted awesomeness using xda premium
TheArtiszan said:
Have you checked the ruu log on your c drive?
The utility usually saves one there.
That may provide some incite.
Click to expand...
Click to collapse
Thanks for the reply! I didn't even think to look for a log file for the RUU. Sure enough it was right on the root of my hard drive! The log confirms my suspicion :
<T230213><DEBUG><OUT>INFOchecking hboot version...</OUT>
</DEBUG></T230213>
<T230213><DEBUG><OUT>FAILED (remote: 44 hboot version check fail)</OUT>
Somehow my HBOOT has been updated from the last time I have went back to stock. I don't remember doing an update last time I was STOCK and RELOCKED ( i might of though, can't remember! ). Is it possible that the Jelly Bean ROM I had installed after my last RELOCK, updated the HBOOT?
Sooooo.....I went ahead and I have extracted the HBOOT NB0 file from the ROM.ZIP that the RUU creates in a temp folder. Is there a way to push that onto my phone, then run the RUU?
Hope this helps!
So first off, to the OP Kobi71, sorry if I hijacked your thread! I was going to post about my issue and came across yours first which sounded pretty much identical! So hopefully my experience can help you!
So I got it to work! I have successfully flashed my RUU. What I found out from reading other threads and poking around was that my HBOOT was to new for the RUU file I had. There isn't an update RUU for my phone out there so I decided to give the HBOOT downgrade to 1.06 a shot.
[TUT] Downgrade/Unbrick Ville S4
http://forum.xda-developers.com/showthread.php?t=1990043&page=16
I followed the instructions and it all worked out just fine. READ through the instructions twice if you have too!
Understand them if you decide to try this because your essentially bricking your phone (at first). All being said, worked like a charm. Downgraded to HBOOT 1.06 from 1.13. The only "troubles" I had during the process, was that when I did step 9 and 12 the phone would hang on Sending Reset randomly throughout the process. Probably about ten times. So I did this each time :
absolutelygrim said:
" If it stalls at "Waiting for /dev/sdc12, hold the power button down on your phone about 10 seconds, or until your see "Qualcomm. Inc. Gobi Wireless Modem (QDL mode) disappear from your terminal window, then release it. 10 seconds or less after you do this, emmc_recovery will see your phone and proceed "
Click to expand...
Click to collapse
It also hung at the very end of the process too, so again hold the power button down if that happens to you.
After all that was done, I flashed the stock recovery from the ROM.ZIP that i got from the RUU ( don't know if I needed to do this ). Wiped everything/Factory reset. Then i relocked the bootloader. I then ran the RUU file, and it worked perfectly. Just like before. HBOOT was also "upgraded" to 1.08
Hope this helps your situation!
Hi Guys, I've tried to do this myself reading other posts and not creating a thread but I have failed miserably so I am in need of some advice now. I need to try and get back to stock due to a warranty issue so I was following this guide here: http://forum.xda-developers.com/showthread.php?t=1460713
It seemed to be going well and I flashed the hboot which removed the revolutionary version, the RUU I used was the only Tmobile version I could find RUU_Saga_TMO_UK_1.30.110.2_R_Radio_20.28b.30.0805U_38.03.02.11_M_release_180106_signed and it started running through, it updated the hboot which is now S-On version 0.98.0000 but after that point it failed with error 140.
I don't understand why this has happened though as surely the version 0.98.0000 HBoot version is what is installed by the RUU itself so how can this be the wrong version? Is there something else I'm missing here.
At this point the phone is connected by USB to my laptop still and sat in HBoot, I'm not even sure if I can safely reboot at the moment so need some advice on what to do next?
I did that, had the same problem (around 3 weeks before you). I just ran it a gazillion times and then, I ended up flashing RUU_SAGA_ICS_35_S_HTC_EU_14.01.401.2_20.76.30.0835_3831.19.00.110_275068 anyway. That worked. T-Mobile/HTC never said a word, fixed it and then sent my phone back.
But beware, the phone sent back will return on:
Android 4.0.4
Sense 3.6
Hboot 2.02.0002
Radio 20.76.30.0835U_3831.19.00.110
rlzzzz said:
Hi Guys, I've tried to do this myself reading other posts and not creating a thread but I have failed miserably so I am in need of some advice now. I need to try and get back to stock due to a warranty issue so I was following this guide here: http://forum.xda-developers.com/showthread.php?t=1460713
It seemed to be going well and I flashed the hboot which removed the revolutionary version, the RUU I used was the only Tmobile version I could find RUU_Saga_TMO_UK_1.30.110.2_R_Radio_20.28b.30.0805U_38.03.02.11_M_release_180106_signed and it started running through, it updated the hboot which is now S-On version 0.98.0000 but after that point it failed with error 140.
I don't understand why this has happened though as surely the version 0.98.0000 HBoot version is what is installed by the RUU itself so how can this be the wrong version? Is there something else I'm missing here.
At this point the phone is connected by USB to my laptop still and sat in HBoot, I'm not even sure if I can safely reboot at the moment so need some advice on what to do next?
Click to expand...
Click to collapse
So your problem is solved ? I want go back to S-ON and would get some feedbacks before doing this
Hello, can somebody please help me. I was trying to go back to stock ROM, I locked my bootloader and ran the RUU but it gave me an error halfway through. Now I'm stuck with a black screen with the grey HTC logo and 4 triangle/error sign things on every corner. I can't install RUU or do anything right now. I can't go into bootloader, everything takes me back to that black screen with the triangles. I've checked lots of threads, I've been trying stuff all day long but nothing seems to work. My phone was S-ON with HBOOT 1.27.000. My CID is HTC__M27. I'm not really experienced with things like this so please bear with me. I don't know what other information I need to post here. PLEASE help me. I tried to run an RUU (3.32.468.12) with the compatible CID (HTC__M27) but its version is older than mine (mine is 3.32.468.51) so I can't install it.