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!
Related
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.
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?
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
So I recently updated my hboot to 2.15 for the new 3.4 kernel. I have a Telus branded One S, so I used this firmware to update: http://www.androidfiles.org/ruu/getdownload.php?file=Ville/OTA_Ville_U_JB_45_S_TELUS_WWE_3.16.661.4_1.13.50.05.31_10.30.50.08L_release_307532nohrvy5j6i2o2i8i.zip
However, when I update to this hboot, I lose service. I will have it for a couple seconds or so, then I will lose it. This has happened on every ROM I have tried, including the new ones with 3.4 (CM, PAC, Carbon). I have tried going back and using the previous RUU's (I've tried this, and this) But those two aren't on the same hboot correct? Those two don't work, and I am unaware of any others as none are listed on that site.
So my problem is that I have no service, and I can't go back to previous hboots and I don't know why. Is it a problem with the new radio? If so I haven't found any great tutorials on where and how to get different radios.
If anyone could help me at all I would be so grateful if they could point me in the right direction. If someone helps me I could definitely make it worth their while over paypal
I can post screen shots or whatever if someone could tell me if they need any information in order to help.
Hboot-2.15.000
Radio-1.13.50...
Can't SuperCID as it's JB... CID is Telus_001 atm
Did you look at the s=off post?. Go to http://www.moonshine.io and see if your phone is on the list. I had OTA 2.15 and with moonshine script I got the s=off. With s=off you can go back to stock.
cuiltheory said:
Did you look at the s=off post?. Go to http://www.moonshine.io and see if your phone is on the list. I had OTA 2.15 and with moonshine script I got the s=off. With s=off you can go back to stock.
Click to expand...
Click to collapse
Doesn't work since I am on the TELUS WWE 3.16.6614, and that says it is only for 3.14
Ster76 said:
So I recently updated my hboot to 2.15 for the new 3.4 kernel. I have a Telus branded One S, so I used this firmware to update: http://www.androidfiles.org/ruu/getdownload.php?file=Ville/OTA_Ville_U_JB_45_S_TELUS_WWE_3.16.661.4_1.13.50.05.31_10.30.50.08L_release_307532nohrvy5j6i2o2i8i.zip
However, when I update to this hboot, I lose service. I will have it for a couple seconds or so, then I will lose it. This has happened on every ROM I have tried, including the new ones with 3.4 (CM, PAC, Carbon). I have tried going back and using the previous RUU's (I've tried this, and this) But those two aren't on the same hboot correct? Those two don't work, and I am unaware of any others as none are listed on that site.
So my problem is that I have no service, and I can't go back to previous hboots and I don't know why. Is it a problem with the new radio? If so I haven't found any great tutorials on where and how to get different radios.
If anyone could help me at all I would be so grateful if they could point me in the right direction. If someone helps me I could definitely make it worth their while over paypal
I can post screen shots or whatever if someone could tell me if they need any information in order to help.
Hboot-2.15.000
Radio-1.13.50...
Can't SuperCID as it's JB... CID is Telus_001 atm
Click to expand...
Click to collapse
I'm on the same boat with you. CID is Telus_001 too. If you find a way to solve the problem, please let me know, I'll do the same too. Thanks a lot.
Moonshine is updating the script, so check his web site from time to time.
the problem is not the new hboot. is new cm10.1 based roms. (NOW SEEMS FIXED)
it happened to me too. I did not update hboot and stayed with 1.14.0004 and flashed early versions of Carbon_HALO roms with 3.0.80 kernel by $droyd$ and lost signal until toggle airplane mode on-off.. then wiped and flashed carbon with 3.4 kernel.. same thing. data issue again. Then flashed carbon 6-21 build and data has worked well so far for 20+ hours.
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.