Hello,
trying flash latest RUU leak for Sensation. Can't do that... Idk why, but every time I run RUU I'm getting 132 signature error. MID and CID are same like in android-info.txt. Tryied to run RUU when on bootloader - nothing, same error on PC. Tryied to put rom.zip renamed to PG58IMG.zip, and I can see this:
loading PG58IMG...
when loaded:
checking PG, and thats it, nothing happens. Indicator of % of checking finished, and nothing happens, just return to main HBOOT menu.
Any way to fix this without rooting/s-off? I just want ICS
P.S, once I've been rooted for a while (maybe this caused 132 now?), but now I'm totally stock, and i Dont want to change it in case of warranty.
You will be scolded for posting this here, questions go in the question forum
Ok, thx. Any mod can change this?
Moved to Q&A
Again, no help
Wait for the official RUU.
Or flash a custom Rom, having flashed the latest firmware beforehand ofcourse
My Sensation has never been rooted, and I am also getting 132 signature error..
FINALLY!!
Had the same issue, totally stock and really fed up that i can't answer incoming calls so why not flash this RUU?
.. Error 132 tried everything and in the end gave up..
F**K THIS PHONE, so close i threw it out the window (as many times before)
Hmm my Desire worked like a charm with Cayongenmod so i'll try that, first order of business, S-OFF, off to Revolutionary followed the instructions.. Fail.. again.. Failed.. again FAILED! LEMONS!!!
Uninstalled everything rebooted and started over, got the S-off prog to work even thou it said failed (cruel joke), didn't dare to restart the phone so just try the RUU one more time and TADAA! It worked!
I haz Ice Cream Sandwich!
I think it has to be S-OFF (for some of us), also uninstalled avast antivirus and reinstalled the USB drivers but the S-OFF did the trick.
It's going to be fun to try ICS (already have it on the Desire but it's slooow) but if it hangs only once again on incoming call it's going to taste tarmac, i still from the bottom of my heart hate this phone.. Hope ICS prove me wrong.
Thanks, Wwax! S-off fixed the 132 error. RUU was installed, and I am running ICS.
Related
*ATTENTION MODS* I am reposting.... sort of... the original thread is here
http://forum.xda-developers.com/showthread.php?p=9074948#post9074948
Hello! I am not new to rooting...I did get a new EVO 4G at best buy yesterday...
Went home and tried to root following another method than unrEVOked 3.21 and long story short had to RUU with "RUU_SuperSonic_S_Sprint_WWE_3.26.651.6_Radio_2.15 .00.07.28_NV_1.40_release_140444_signed"
I then tried unrEVOked 3.21 which SEEMED to work... I followed all onscreen prompts...
Plugged in my phone, ran the program, phone rebooted, selected HBOOT USB, Program reported that everything was going along nicely...even saw the program say waiting for root..."this was a triumph" Rebooted..then came back up to desktop...didnt reboot in recover like i have seen... the program then reverts to saying the thing about HBOOT USB.... there is NO SuperUser app and it is NOT rooted...
Please tell me where I went wrong...and what I need to do to fix it...
Info about MY Phone
Android Version 2.2
Baseband Version 2.15.00.07.28
Kernel 2.6.32.15-g746f4f0
Software Version 3.26.651.1
PLEASE help....I am having withdrawals lol...
***UPDATE***
Following this Guide
http://forum.xda-developers.com/showthread.php?t=829045
I made it to Step 19...then S#*+ went crazy...It appears that the recover did NOT flash...not really sure...I am now trying to RUU my phone back...and start over but it keeps saying the phone is low battery <30% and its NOT...I looked at 3 batterys on a Hero and it says all are over 70%...
and ..since im pretty sure this matters...with S-OFF
When I try to flash PC36IMG.zip Radio_V2 FAIL-PU and...Bootloader FAIL-IC is what I get...
ALL help greatly appreciated...thankfully I am off work the next two days...So I know I can get this resolved
Ok I have done a lot of reading that seems to indicate that I have no ROM or my ROM is Broken...and seeing as how RUU keeps saying my battery level is too low I am going to put it on the charger til the light turns green...Try to RUU in the Morning...
***SOMEONE PLEASE CORRECT ME IF I AM WRONG ***
I am under the impression that RUU'ing will NOT Turn S-ON and will Leave S-OFF
But will just load a ROM and allow me to boot in and then run unrEVOked and be on my merry rooted way...
If ANYONE knows that it will turn S-ON please stop me lol...I am going to stop trying for now and get some sleep... will check this post before continuing..
Hi,
Im probably going to have to return my sensation for repair as its having some weird charging issues, anyway when i bought it it came with gingerbread on a vodafone uk firmware, ive s-off'd it and super cid it, then upgraded firmware and installed ics roms. Just wondering whats the best way about going back to stock, my thought was to go back to a GB rom, then OTA ICS upgrade (although as far as return this isnt necessary), so in order to do this what would I need to do, would I have to flash the 1.17 multi firmware then a custom gb rom then a gb ruu? as I tried to use the original ruu that was on my phone when i got it but got a usb error,
Or should I just try a ics ruu
ive done it once before following the guide on here successfully but for the life of me cant remember how
thank them...
bradmax57 said:
Hi,
Im probably going to have to return my sensation for repair as its having some weird charging issues, anyway when i bought it it came with gingerbread on a vodafone uk firmware, ive s-off'd it and super cid it, then upgraded firmware and installed ics roms. Just wondering whats the best way about going back to stock, my thought was to go back to a GB rom, then OTA ICS upgrade (although as far as return this isnt necessary), so in order to do this what would I need to do, would I have to flash the 1.17 multi firmware then a custom gb rom then a gb ruu? as I tried to use the original ruu that was on my phone when i got it but got a usb error,
Or should I just try a ics ruu
ive done it once before following the guide on here successfully but for the life of me cant remember how
Click to expand...
Click to collapse
[GUIDE] How to Debrand, Rebrand & Flash Stock ROMs to your Sensation
http://forum.xda-developers.com/showthread.php?t=1193033
hope it helps...
I used 1.27.161.xxxx RUU from http://shipped-roms.com/index.php?category=android&model=Pyramid
The CID is "VODAP001"
So change CID, run the RUU.
Then when you are 100% certain it's fine change to S-ON.
Ok thaks, but in order for me to flash a GB RUU do I have to flash a GB Firmware first or is that part of the RUU? The other thing is Im supercid atm, should I change it back to the carrier cid for return?
bradmax57 said:
Ok thaks, but in order for me to flash a GB RUU do I have to flash a GB Firmware first or is that part of the RUU? The other thing is Im supercid atm, should I change it back to the carrier cid for return?
Click to expand...
Click to collapse
The RUU contains everything you need (firmware including radio, standard recovery and of course the ROM itself). You'll end up with a standard Vodafone bloated HTC un-rooted ROM. You'll still have S-OFF but no custom recovery.
Yes change the CID back either before or after installing the RUU.
You should change it back to S-ON BUT ONLY after you're sure everything is as it should be. There are a few guides on the final step, I'll let you dig them up, IIRC it's a fastboot command.
hmmm now i cant get the RUU to work, i already had an older vodafone ruu but downloaded yours too, when I try the one you mentioned it just hangs at the "verifying information on your android phone. please wait..." screen if I try the one i had it comes up with error [170] usb connection error, i have HTC Driver 3.0.0.007 installed
will try and download the newest ones
EDIT
Managed to do it by extracting the rom.zip from the ruu and renaming it to PG581IMG.zip Is it correct that it should have the large vodafone logo on boot, when I bought the phone (was a used from an online store) they said it was a vodafone handset however it never originally had the logo like it does now
bradmax57 said:
hmmm now i cant get the RUU to work, i already had an older vodafone ruu but downloaded yours too, when I try the one you mentioned it just hangs at the "verifying information on your android phone. please wait..." screen if I try the one i had it comes up with error [170] usb connection error, i have HTC Driver 3.0.0.007 installed
will try and download the newest ones
Click to expand...
Click to collapse
I just checked in Device Manager and it looks like the HTC device driver I used is 2.0.7.8, in Control panel add/remove programs the HTC Driver Installer is 3.0.0.021.
After installing the HTC stuff I then removed HTC Sync.
Check the MD5 of the RUUs, just rechecked mine and they're the same as on that site. for both 1.24.161.xxx & 1.27.161.xxx.
I run mine with the phone on the home screen, I have also seen recommendations that it should be run with the phone in Fastboot mode (from bootloader).
Apart from that I don't know what it may be apart from a suspect USB cable.
GL
Up and running, just wanted to check the vodafone logo on boot is correct?
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!
Afternoon all,
A little help and advice if I may?
Running a custom ROM with HBoot 2.19 and S-On
Trying very hard to return to full blown unrooted stock so banking apps will work (I've tried every work around there is possible to fake unroot but they just don't work).
This gentleman here (http://forum.xda-developers.com/htc...m-official-stock-android-4-3-sense-5-t2837799 ) seems to be the means of getting back to stock but requires S-Off and HBoot 2.22
I've tried firewater but get an error saying HTC have put anti-firewater protection in then it bombs out. (Tried using KAngaroo kernal and SS Kernal from the dev page)
I've tried rumrunner_HTC_0.5.0 but even with Windows Firewall off, no anti-virus and even putting my laptop into a DMZ I still get the fatal error when trying to download the tool.
From what I gather I cannot get onto HBoot 2.22 to try alternative custom Roms until I S-Off the bloody thing which appears to be impossible.
Any ideas?
All comments will receive thumbs up and a cake in the post.
Thanks
That backup should still work even if you're S-on. It did for me. I'm not sure about the HBOOT but if you backup where you are now, you're no worse off if it doesn't work.
I had to do the same thing so my network's Wi-Fi calling app would work.
I only had to S-off afterwards to change my CID to get official OTA updates, you may not need to do that step in which case S-off is fine.