Hello,
I have a problem with my Desire S, when I was updating the GoogleMaps app, my phone went off. When I've always stays on the HTC home screen. The recovery and the factory reset does not work. My phone is Vodafone Spain stock rom with the S-ON and HBOOT is 002.
I tried to install roms from htc official signed with the RUU but does not load, it always comes message "loading bootloader". I have also tried to install from SD but tells me that files are missing and PG88DIAG.nbh PG88DIAG.zip. The PG88IMG.zip is extracted but finally sends message "CID error."
I have also tried to load an official rom and modifying the file by entering the CID xxx.txt my VODAP304 operator. So give me the error again missing the first two files, but extracts PG88IMG.zip well, but does nothing.
I made a last test from the console Windows7 with fastboot and I tried to load the partitions one by one (boot.img recovery.img, etc ...), but warning recognizes files that do not load because they are not signed , extracted from a signed official rom, this will not understand why it happens.
I ask for help if anyone knows how to solve the problem. I also ask where or how I can get the stock rom 1.47.161.2 Vodafone Spain.
I do not want root and S-OFF if I can not fix send the SAT because it is in warranty.
Sounds like this : http://forum.xda-developers.com/showthread.php?t=1150917 . Returning it under warranty will be the best what you can do...
Thanks,
this thread had not read it, I decided to send the SAT to repair or Vodafone send me a new phone.
Quite a few people are having this problem now. What would happen if you are S-Off and have a modified ROM. Bad luck or would it still be possible to get warranty?
Related
Guys,
I have found a definite issue regarding trying to debrand and flash the 2.3.4 OTA update to my Bell debranded sensation...Here are my steps and results...
1. Performed Revolutionary on shipping Bell Canada Sensation
2. Changed CID to 11111111 via fastboot.
3. Flashed generic UK 1.35.401.1 software via RUU file.
4. Downloaded 2.3.4 OTA update.
5. Try to install the OTA update.zip from recovery, it errors out with Status 7 error. No matter what CID I use, I always get this error status 7.
6. Change CID to HTC__E11 to try and get the OTA update automatically, Downloads and then gives me a "variant system software" error when it goes to install. I've never heard of or seen this error before.
7. Run Revolutionary again and then flash the update.zip. It appears to successfully flash, but when the phone reboots, all I get is a black screen. the phone makes noises and appears to be functioning somewhat, but screen is black.
8. I am now thinking, great, I just bricked my phone...
9. Reboot into hboot. It still shows Bootloader of 1.17.0011, which is strange because the OTA is supposed to update it to 1.18.0000.
10. I then change the CID to 11111111 and reflash with the 1.35.401.1 RUU and thank god the phone is back to working condition.
It appears that there is either a hardware difference or something really low level that is being changed with this new update and it might not work properly with the different radio from the Bell Canada version with the 850/1900 radio, but I don't understand why flashing to the 1.35.401.1 RUU works fine. If anyone else can shed any light on this or give me any hints, I would appreciate. I thought my experiences might help the devs out there further understand the new OTA and the Sensation software/hardware. My end goal is to have the most up to date stock unbranded software installed on my Sensation. I am using with AT&T if anyone is wondering.
Y2J
y2jdmbfan said:
Guys,
I have found a definite issue regarding trying to debrand and flash the 2.3.4 OTA update to my Bell debranded sensation...Here are my steps and results...
1. Performed Revolutionary on shipping Bell Canada Sensation
2. Changed CID to 11111111 via fastboot.
3. Flashed generic UK 1.35.401.1 software via RUU file.
4. Downloaded 2.3.4 OTA update.
5. Try to install the OTA update.zip from recovery, it errors out with Status 7 error. No matter what CID I use, I always get this error status 7.
6. Change CID to HTC__E11 to try and get the OTA update automatically, Downloads and then gives me a "variant system software" error when it goes to install. I've never heard of or seen this error before.
7. Run Revolutionary again and then flash the update.zip. It appears to successfully flash, but when the phone reboots, all I get is a black screen. the phone makes noises and appears to be functioning somewhat, but screen is black.
8. I am now thinking, great, I just bricked my phone...
9. Reboot into hboot. It still shows Bootloader of 1.17.0011, which is strange because the OTA is supposed to update it to 1.18.0000.
10. I then change the CID to 11111111 and reflash with the 1.35.401.1 RUU and thank god the phone is back to working condition.
It appears that there is either a hardware difference or something really low level that is being changed with this new update and it might not work properly with the different radio from the Bell Canada version with the 850/1900 radio, but I don't understand why flashing to the 1.35.401.1 RUU works fine. If anyone else can shed any light on this or give me any hints, I would appreciate. I thought my experiences might help the devs out there further understand the new OTA and the Sensation software/hardware. My end goal is to have the most up to date stock unbranded software installed on my Sensation. I am using with AT&T if anyone is wondering.
Y2J
Click to expand...
Click to collapse
I would venture to guess you're not aware that you should probably not (at least not now), do an official FOTA/OTA on an unauthorized S-OFF Sensation.
The official HTC 2.3.4 OTA that came out a few days ago, LOCKS your device. It puts it back into an S-ON state.
Unless something has changed, if you have S-OFF via Revolutionary....stay far away from official HTC updates.
Something has changed...revolutionary now supports the new "locked" bootloader!
Hoggles said:
I would venture to guess you're not aware that you should probably not (at least not now), do an official FOTA/OTA on an unauthorized S-OFF Sensation.
The official HTC 2.3.4 OTA that came out a few days ago, LOCKS your device. It puts it back into an S-ON state.
Unless something has changed, if you have S-OFF via Revolutionary....stay far away from official HTC updates.
Click to expand...
Click to collapse
I'm well aware that the the official HTC 2.3.4 OTA locks the device. As long as I have a debranded Sensation running the latest and greatest firmware/software, that is all I am looking for. And now that Revolutionary works on the new HBOOT there shouldn't be much trouble getting back to the original shipping software. I still am curious as to what is causing this "Error Status 7" error code.
So how can I update my sensation with s-off?
A bug in me from being updated.
That would really interest me too! don't want to be S-ON again to make this update. Another question (maybe off topic): how can i update to new S-OFF version 04pre4? I'm now on 03pre7.
Hi
I have the exact same problem as yours, what can we do to update it?
Same on Swisscom-branded phone
I tried the OTA on my swisscom phone, it reboots and I get an exclamation mark with a blue droid. Waited 10 minutes just in case, but no change.
Removed battery and rebooted. Phone still ok, but not updated obviously.
I'm not sure it will remove S-OFF, but I don't care, HTC provides an official procedure for that and we have what we need.
But I need this update to work on my rooted, S-OFF stock sensation. Will try again anyway...
EDIT: I tried going into recovery and manually flashing the OTAxx.zip file, but it gave me an assert_failed: check_cid!? Though I never changed the phone CID! So why propose me an update on my phone if it's the wrong one??? Not sure I want to change the CID of my phone now.
Ok So my friend from work wanted his sensation rooted after I did mine. He has S-OFF and has sucessfully permanently rooted it with the SU-bin 3.03 blah blah zip file. I've succesfully rooted my own with CID of 11111111 and used 4EXT recovery to install the 3.24 firmware. He, however, gets the known boot loop problem, which I know is due to firmware not being upgraded. I can't for the life of me connect his phone and have ADB connect to it to change his CID.
I've got the same exact model phone, down to the same carrier, so I have the HTC sensation USB drivers (HTC sync) installed on my pc. It won't detect it though because of it not being able to boot into android's OS.
I'm attempting to download a rom that is based off of the stock firmware hoping this will solve my problem, but wouldn't mind any insight on it.
Well, if i got it right you just need to pick a firmware flashable for that phone without supercid, am i right? In that case there's the topic where you can find all firmware adjusted to a particular CID, grab that from your phone, put into your sd (you may want to put a ROM to flash too), then put your SD with the matching firmware onto his phone, reboot and it's done! Finally swap again the SD card.
daddoso said:
Well, if i got it right you just need to pick a firmware flashable for that phone without supercid, am i right? In that case there's the topic where you can find all firmware adjusted to a particular CID, grab that from your phone, put into your sd (you may want to put a ROM to flash too), then put your SD with the matching firmware onto his phone, reboot and it's done! Finally swap again the SD card.
Click to expand...
Click to collapse
Yes I would think so, but I can't figure out what current CID he has on his phone because I can't boot up into android's OS and connect to my phone on my PC with ADB (adb devices shows up, but when I try to set the CID it wont work).
Fails to "set" or fails just the command? Because if its only a "set" issue, the command may (unlikely) work and show you the cid! Or we can try to find it out with some info like brand/country/etc ..
Figured it out, had to do with the sync cable I was using. used a different one and i was able to set the CID to 1111111 or w/e. Installed the new firmware and the silly boot loop stopped.
Sent from my Asus Transformer of The Prime Kind.
Hi all,
I have tired to flash the new Rom yesterday and during checking the signature device reboot and installer said that it can not proceed.
After reboot phone goes directly into fastboot and gives ***Locked*** with Security Warning massage. I have tried different RUU but it is exactly the same.
Installation is failing on the checking signature.
I have tried Unrevoked3 but it is not able to find the device. Could you please let me know how to do it?
SAGA PVT SHIP S-ON RL
HBOOT-2.00.0002
RADIO-2822.10.0804_M
eMMC-boot
I was trying to upload RUU_Saga_S_HTC_Europe_2.10.401.9_Radio_20.4801.30. 0822U_3822.10.08.04_M_release_234765_signed
http://forum.xda-developers.com/search.php?searchid=23896455
Error nr 141?
LE: hope it works now, if not search the forum, the link reffers to the search results.
You will certainly get the answer there.
Link does not work:
Sorry - no matches. Please try some different terms.
I have tried to find an answer but no luck so far, I am quite new to this. Is there anyone who can point me in the right direction?
Another solution is to try the RUU 2.10.401.8
I had some problems with the same Ruu, but not with the signature, and the previous version worked flawlesly.
What's your CID?
Sent from my HTC Desire S
I have tried few others RUU and every single of them is falling during the installation.
ok I manage to unlock the device finally
But again it is falling during the installation of a new ROM. Do I have to revert back Hboot to 0.98 before installation? if so how to do it?
So the RUU that I recommended completed successfully?
What do you want to do next?
Now you are S-ON, if you want to install custom roms you have to unlock your bootloader with the htcdev method(you will lose your warranty and need to flag manually the boot file) or to downgrade.
Sent from my Samsung Galaxy Tab
I want to downgrade the phone to orginal ROM T-mobile uk. So I could take off the simlock, I have put the unlocking code yesterday but nothing happens. I was advised to downgrade the rom and should be ok.
Could some help me out with my problem please when ever I am trying to upload new rom it is stuck on signature verification.
I will quote Enigmaamit as he said it better than me:
enigmaamit said:
SIM unlock and bootloader unlock are two completely different things.
Click to expand...
Click to collapse
The only way to SIM-unlock your phone yourself is a XTC clip... better ask your phone operator.
I know the diffrance between those two, I have ordered unlocking code. After putting this into device when ever I put into new sim card it stoped nofifing me about it. But it is not able to find a new network. Below what I have receive form operator:
"It said "Successful" but nothing has happened
Darren
posted this on Apr 11 16:22
This has happened to a handful of customers who have all had one thing in common - the phones have been "rooted".
By rooting a handset the owner has removed some of the restrictions on the phone, which allows the owner to install whichever software of the phone that they wish. Unfortunately this has caused some issues when an unlock code has been entered.
It is easily rectified by reinstalling the original operating system that the phone was supplied with, then applying the unlock code and the phone should be unlocked, truly, successfully.
You can then reinstall the software you had on the phone before attempting the unlock and continue using the phone as you wish."
So that is the reason why I am trying to revert any changes.
i for one don't believe this
So their replay is bull**** in that case?
In my opinion yes(i can't say that i am a very experienced user) but i like to think i know some stuff about this.
I can't imagine what custom rom/Ruu version/app will "block" you to sim unlock your phone.
The only restrictions may be made by the phone manufacturer.
So i will try through HTC Clip in that case. But why I can upload any new RUU?
like i said earlier, i had some problems to with the 2.10.401.9 ruu.
Try the 2.10.401.8 it should work, if your phone is branded try a gold card.
Hello. I have a htc one s ville c2(s3 proc) and a long time ago i installed a custom rom (trickdroid 5.0.0 ) and it started to work hard, wi-fi not working, and things like this.So i decided to go back to stock. My phone's cid is htc_032 wich means that is for Eastern europe. I downloaded a ruu 2.15......... and i installed it. The mobile network was working very hard (100kb/s) so i think the baseband is not good.Then i found an ota for htc_032 and i tried to install it. i relocked the hboot, then flashed the firmware.zip with fastboot. All fine, but after the install i candt even open my phone or enter in hboot........ please help...
Hi Everyone,
knowing it's all out there, just need to read (a lot), please help me finding the correct way to solve my problem. I can not change to other ROM, mostly due to lack of knowledge. Please before you judge and claim I should read and learn, i have kids who don't allow me read things properly, and there are tons of information out there, seems simplier to ask for directions this time, based on the situation of the phone.
This is the first custom rom I tried on my new S4 HTC One S (not brand new, just new to me). It was stock rom, locked. Followed instructions on different threads, I unlocked the phone, flashed TWRP recovery, installed SuperSU, copied Venom Rom zip to SD card and installed from recovery, with the aroma. Success. Before installation I did a backup in TWRP.
I very much like the rom (though have 2 issues: 1. phone reboots randomly without any notification. 2 phone loses carrier randomly, so I see no GSM connection as if SIM was removed. This happens when phone is untouched so no way SIM is loosy or something). When I try to chose carrier manually from settings, it sais no SIM card is installed...
But I would like to try other roms as well, and also wish to compare some stock roms. So I downloaded a generic HTC Europe stock RUU, hoping I can easily flash it. Relocked the phone, ran the RUU.exe with Fastboot USB mode in bootloader, but it all came up with error messages and left me at the HTC logo. All I can do is to re-install Venom 3.0.0 from recovery, that works, otherwise I end up in boot loop.
Also I can not go back to the original state using the backup from TWRP. It installs boots but it basicaly freezes before the phone setup comes. I can see the background image, the clock and the GSM antenna sign, but thats all, nothing else happens, no matter how hard I try to reboot.
Phone current boot screen shows: Tampered + Unlocked
VLE PVT SHIP S-ON RL
HBOOT-2.15.0000
Radio-1.15.50.05.29
OpenDSP-v31.1.0.45.0815
eMMC-boot
Dec 14 2012, 17:10
When I re-locked the phone it said Tampered + Relocked + Security Warning
As recovery I have TWRP 2.6.0.0 flashed. I did nothing else.
Could someone help me with instructions or at least directions how I could go back to a nice stock RUU? With the one I downloaded i had different error codes 213 (wrong ID) and 255 Unkown error.
I believe as the phone is not S-OFF and/or Super CID, it is relevant which RUU I download. The phone used to boot with a voda logo, so I believe it was one of the UK or AT voda stock roms, but neither works.
Your opinion/feedback is highly appreciated.
Cheers,
skee
skee81 said:
Hi Everyone,
knowing it's all out there, just need to read (a lot), please help me finding the correct way to solve my problem. I can not change to other ROM, mostly due to lack of knowledge. Please before you judge and claim I should read and learn, i have kids who don't allow me read things properly, and there are tons of information out there, seems simplier to ask for directions this time, based on the situation of the phone.
This is the first custom rom I tried on my new S4 HTC One S (not brand new, just new to me). It was stock rom, locked. Followed instructions on different threads, I unlocked the phone, flashed TWRP recovery, installed SuperSU, copied Venom Rom zip to SD card and installed from recovery, with the aroma. Success. Before installation I did a backup in TWRP.
I very much like the rom (though have 2 issues: 1. phone reboots randomly without any notification. 2 phone loses carrier randomly, so I see no GSM connection as if SIM was removed. This happens when phone is untouched so no way SIM is loosy or something). When I try to chose carrier manually from settings, it sais no SIM card is installed...
But I would like to try other roms as well, and also wish to compare some stock roms. So I downloaded a generic HTC Europe stock RUU, hoping I can easily flash it. Relocked the phone, ran the RUU.exe with Fastboot USB mode in bootloader, but it all came up with error messages and left me at the HTC logo. All I can do is to re-install Venom 3.0.0 from recovery, that works, otherwise I end up in boot loop.
Also I can not go back to the original state using the backup from TWRP. It installs boots but it basicaly freezes before the phone setup comes. I can see the background image, the clock and the GSM antenna sign, but thats all, nothing else happens, no matter how hard I try to reboot.
Phone current boot screen shows: Tampered + Unlocked
VLE PVT SHIP S-ON RL
HBOOT-2.15.0000
Radio-1.15.50.05.29
OpenDSP-v31.1.0.45.0815
eMMC-boot
Dec 14 2012, 17:10
When I re-locked the phone it said Tampered + Relocked + Security Warning
As recovery I have TWRP 2.6.0.0 flashed. I did nothing else.
Could someone help me with instructions or at least directions how I could go back to a nice stock RUU? With the one I downloaded i had different error codes 213 (wrong ID) and 255 Unkown error.
I believe as the phone is not S-OFF and/or Super CID, it is relevant which RUU I download. The phone used to boot with a voda logo, so I believe it was one of the UK or AT voda stock roms, but neither works.
Your opinion/feedback is highly appreciated.
Cheers,
skee
Click to expand...
Click to collapse
To go back to stock u have to flash the right RUU, depends on which CID ur phone got.
u can download it here: http://www.androidruu.com/?developer=Ville
If u downloaded the right RUU, boot ur HOS into fastboot relock the phone and start the RUU.
Let it finish and u r on stock
Hi Homeboy, thanks for the answer. Seems clear. I have only 1 question. How can I make sure which is the right RUU?
I believe I should do a getvar all command, to see the CID id? Then what shall I look at the RUU's filename?
And after the phone having been relocked, shall it be in fatboot USB in bootloader or shall the phone be up and running when I start the RUU.exe from the computer?
thanks
skee81 said:
Hi Homeboy, thanks for the answer. Seems clear. I have only 1 question. How can I make sure which is the right RUU?
I believe I should do a getvar all command, to see the CID id? Then what shall I look at the RUU's filename?
And after the phone having been relocked, shall it be in fatboot USB in bootloader or shall the phone be up and running when I start the RUU.exe from the computer?
thanks
Click to expand...
Click to collapse
hi,
i saw u live in Hungary so it should be the Europe RUU try this:
http://www.androidruu.com/getdownload.php?file=Ville/RUU_Ville_U_ICS_40_S_HTC_Europe_2.31.401.5_Radio_1.06es.50.02.31_10.09a.50.04L_release_275655_signed.exe
And yes phone should be in fastboot when u start the RUU.