Hi, I think I may have completely screwed the phone up...
I've been on T-Mobile UK with this phone for quite a while now, 2.3.5 updates being available in Europe and on other UK providers for ages, and I know friends have recently received it on T-Mo UK too, but I couldn't get it for some reason. Investigating why with T-Mo customer service was futile so I decided to try and set about upgrading it myself.
I used superoneclick to get temporary root, flashed revolutionary recovery to get S-Off and got myself permanent root on 2.2 -- however something went wrong after this and I'm not quite sure what.
On trying the European RUU (2.10.401.8) it seemed as though it was successful, but going into HBoot, I could see it was no longer Revolutionary branded - instead it says:
Code:
*** LOCKED ***
SAGA PVT SHIP S-ON RL
HBOOT-2.00.0002
RADIO-3822.10.08.04_M
eMMC-boot
Aug 22 2011, 15:22:13
Trying to flash another recovery tool doesn't work, trying to flash an earlier version of HBOOT doesn't work. Re-flashing the European unbranded RUU doesn't work because its now picking up that the CID isn't right, and in this environment (Hboot) my gold card doesn't seem to be working. The latest Desire S T-Mobile RUU I can find is version 1.30.110.2, and as its older I get the "Main version is older" error.
I tried extracting the rom.zip from the RUU .exe file, renaming it to PG88IMG.zip - but same error there - and trying to fool it by changing the version number in the manifest inside the archive just makes the sig check fail...
I'm totally outta ideas here, anyone got any more for me to try, or am I going to have to send this off to someone to fix?
Cheers!
edit: Issue solved, see page 2.
Also, in case this information helps - I do have a goldcard.img but it doesn't appear to work. My CID is T-Mob005
this guy seems to have been in the same boat as me but he did everything correctly - http://forum.xda-developers.com/showthread.php?t=1378921
if he still has his goldcard.img is there a chance it would work in my phone? I've PM'd him asking if he still has it
FrakEarth said:
Hi, I think I may have completely screwed the phone up...
I've been on T-Mobile UK with this phone for quite a while now, 2.3.5 updates being available in Europe and on other UK providers for ages, and I know friends have recently received it on T-Mo UK too, but I couldn't get it for some reason. Investigating why with T-Mo customer service was futile so I decided to try and set about upgrading it myself.
I used superoneclick to get temporary root, flashed revolutionary recovery to get S-Off and got myself permanent root on 2.2 -- however something went wrong after this and I'm not quite sure what.
On trying the European RUU (2.10.401.8) it seemed as though it was successful, but going into HBoot, I could see it was no longer Revolutionary branded - instead it says:
Code:
*** LOCKED ***
SAGA PVT SHIP S-ON RL
HBOOT-2.00.0002
RADIO-3822.10.08.04_M
eMMC-boot
Aug 22 2011, 15:22:13
Trying to flash another recovery tool doesn't work, trying to flash an earlier version of HBOOT doesn't work. Re-flashing the European unbranded RUU doesn't work because its now picking up that the CID isn't right, and in this environment (Hboot) my gold card doesn't seem to be working. The latest Desire S T-Mobile RUU I can find is version 1.30.110.2, and as its older I get the "Main version is older" error.
I tried extracting the rom.zip from the RUU .exe file, renaming it to PG88IMG.zip - but same error there - and trying to fool it by changing the version number in the manifest inside the archive just makes the sig check fail...
I'm totally outta ideas here, anyone got any more for me to try, or am I going to have to send this off to someone to fix?
Cheers!
Click to expand...
Click to collapse
Relax, you have simply gotten the locked bootloader flashed to your phone. You can go to the HTCDEV.com site and unlock the bootloader and then you will be able to install a custom recovery and root the phone again.
tpbklake said:
Relax, you have simply gotten the locked bootloader flashed to your phone. You can go to the HTCDEV.com site and unlock the bootloader and then you will be able to install a custom recovery and root the phone again.
Click to expand...
Click to collapse
Thanks, that's one problem down!
At present I have this RUU Europe Rom that won't load, and the T-MO UK ones still won't install either. I've installed ClockwordMod Recovery 5.0.2.0, so that's good, but I take it I still need a goldcard if I'm going to install a ROM that doesn't match my phone's carrier ID?
Is the reason these older T-Mobile ROMS won't install because of S-ON and the higher radio version number?
edit: by the way, cyanogenmod and similar ROMs appear to install with no errors in clockworkmod recovery but I don't think they are. If I load one of the RUU exes it shows the same 2.10.4 version number with no changes evident whatsoever.
Don't do all so fast. READ FORUMS, READ COMMENTS. Revolutionary wont work with 2.00.0002 . It wont work
Sent from my HTC Desire S using xda premium
gefilus said:
Don't do all so fast. READ FORUMS, READ COMMENTS. Revolutionary wont work with 2.00.0002 . It wont work
Sent from my HTC Desire S using xda premium
Click to expand...
Click to collapse
I realise that now... I'm less concerned about rooting / getting full S-Off again and more concerned with just getting any working ROM at all onto the phone... as it seems the only ones that are probably going to work are T-Mobile ones, and the only available ROMs I can find are older - I may have to send this off to someone
So you cab get into fastboot?? If you can then use downgrading without HTC Dec unlocked bootloader, there is a post about this, try it should work and use misc_version to let phone thinks he is on older hboot and then use latest T-Mobile ruu. I hope and it should work.
Sent from my HTC Desire S using xda premium
i would do this:
unlock with htcdev.com
downgrade hboot to 0.98.0000
use revolutionary for s-off
change cid to supercid
relock bootloader again
and flash the ruu of youre dreams.
think this should do it
This worked for me in the same situation
http://forum.xda-developers.com/showthread.php?t=1443636
Is there a way to get adb terminal access when the phone won't actually load a ROM?
Because all the tutorials I can find for downgrading HBOOT or installing an older ROM (with misc_version etc) - seem to require adb access. I can *only* get into fastboot or a recovery tool like clockworkmod recovery.
Installs of ROMs just aren't working at all. I'm getting "Security Fail" on some of the official ROMs, and the custom roms just aren't working (I assume because of S-ON).
FrakEarth said:
Is there a way to get adb terminal access when the phone won't actually load a ROM?
Because all the tutorials I can find for downgrading HBOOT or installing an older ROM (with misc_version etc) - seem to require adb access. I can *only* get into fastboot or a recovery tool like clockworkmod recovery.
Installs of ROMs just aren't working at all. I'm getting "Security Fail" on some of the official ROMs, and the custom roms just aren't working (I assume because of S-ON).
Click to expand...
Click to collapse
Only if you left on USB dedebuging if it's off then sorry can't. Bet if its o n you can easy make him to boot into fastboot. Take a try, and you need to be installed sdk and adb tools on, PC. Try switch on phone put into USB and open terminal, write adb devices if it works there will show a list and HTXXXXXXXXXX something. If it so then adb reboot - bootloader or if you have custom recovery boot there. If don't anderstand look commands in Wikipedia about adb. Good luck
Sent from my HTC Desire S using xda premium
Okay guys, managed to get this sorted.
Firstly, I read that if you mounted /system from Clockwork mod that ADB commands work... well I didn't get to try that out, because something else worked.
One of the reason RUU updates were failing was because the bootloader was unlocked, when I relocked (fastboot oem lock) they started working again, but I was getting Carrier ID errors on the European RUUs and the T-Mobile ones were too old.
I decided to visit a friend who also has a Desire S and from his phone I was able to get the CID (card identification register) code from a smaller microSD card I have -- this was one I hadn't tried as a goldcard before, and I was unable to try without being able to get at the GoldCard Helper app on my phone... so after using his phone and writing down BOTH CIDs, I tried both and it worked -- I now have the phone updated fully using the European RUU.
I think my mistake the first time may have been copying the wrong CID from Goldcard Helper: if you press Menu > Copy Code it seems to copy the code from MMC1, whereas my SD card was clearly MMC2 -- so my goldcard.img was completely incorrect the first time I tried it. I don't know why the phone let me partially install the European RUU without a goldcard and almost brick the phone, but I suspect it was because I had the Revolutionary bootloader with S-OFF.
So in summary if you have this problem I would suggest borrowing an Android phone (any should work) to get the right goldcard CID needed and then try installing an RUU.
Many thanks to everyone who replied and tried to help me, you guys helped me exhaust every other possibility - and I appreciate it a lot! Thanks!
Related
Right, had desire s from three, alpharevx'd it installed clockwork mod, flashed eng hboot. Tried to flash RUU 1.47 europe on it, and it started to work and go through process, updated radio fine, then came up with CID error. No option to do anything but exit. Now I have a desire s that will boot into Bootloader, which has now s-on'd itself and upgraded to 0.98.0002.
Only method of comms seems to be via fastboot.
Now i cant flash the h3g one cos its too low a bootloader version, and i cant upgrade to a newer version cos one don't exist. Can anyone come up with a solution please??
Cheers.
What does HBOOT screen say (in full)?
Are you still able to get into recovery? If yes, then have you tried loading a custom ROM onto the SD card and simply flashing that using the flash zip from sd card option of CWM (clock work mod)?
Unfortunately I am unable to get into recovery, only bootloader, nothing else works. Hboot is displaying a security error at the top highlighted in pink, followed by the version number as described
You should have stuck with the alpharev hboot, which does not allow itself to be overwritten by RUU installs.
Anyway, you need to:
- install hboot 0.980000 (so you can run alpharevx again and get S-OFF)
- run alpharevx and reinstall CWM at the end
- DO NOT install the eng hboot
- flash whatever rom whichever way you want. Your hboot is safe
Follow the instructions on:
http://forum.xda-developers.com/showthread.php?t=1187231
How can I run alpharevx when I can only boot into bootloader tho?
Try running it while in bootloader. Never tryed it that way, but I'm pretty sure it only needs the USB comms to be up, same as adb. Which they should be anyway in bootloader...
Have you tried to re-setup your phone by executing one of the RUU.exe?
k, as i expected, with no access to adb in bootloader mode, i am unable to do anything. Remember, i only have bootloader to work from. I don't eve3n have a recovery partition installed, it just comes back to bootloader whatever i choose, well, bootloader and fastboot anyway.
yup, tried running the ruu again but to no avail. Just get cid error. And i can't make a goldcard either cos i cant get the code. Might just send it back i think and act dumb :/
What about using the "normal" upadte procedure? Placing the PG88(whatever).zip on the root of the sdcard, and have the bootloader install it?
Of courtse with S-ON, it must be a signed version...
If all else fails s-off with xtc clip then flash custom rom
Sent from my HTC Desire S using XDA Premium App
Have you tried to use the original RUU for your phone/network? I'm not sure if it would take care of the CID error.
Any of these:
http://forum.xda-developers.com/showthread.php?t=1002506
Clivectmob said:
yup, tried running the ruu again but to no avail. Just get cid error. And i can't make a goldcard either cos i cant get the code. Might just send it back i think and act dumb :/
Click to expand...
Click to collapse
I do not expect this to work, but you said you are able to get into recovery, correct?
Well, I would try to enter fastboot mode and try to flash cwm via fastboot -> fastboot flash recovery XXXXXXXX.img
Correct (windows) drivers installed?
Edit:
lowveld said:
What about using the "normal" upadte procedure? Placing the PG88(whatever).zip on the root of the sdcard, and have the bootloader install it?
Of courtse with S-ON, it must be a signed version...
Click to expand...
Click to collapse
Good suggestion! Try this one first.
The problem with trying my original ruu for my network is that it contains the lower hboot version, when i flashed the generic ruu earlier, it actually started the update and flashed the radio part, then informed me the cid error, of course, by this time it had updated the hboot too. So now i have a desire s with an upgraded hboot so i can't flash a new one because of cid error and i can;t go back cos it reports a hboot version error. Where do i look on the system for the p88ing.zip now? can't remember now!
I haven't run a RUU in years, but I think that when you run it on a windows machine, it extracts a bunch of files to a directory. Cancel the process, find the directory, find th PG88... in the directory... You get the drift.
Clivectmob said:
The problem with trying my original ruu for my network is that it contains the lower hboot version, when i flashed the generic ruu earlier, it actually started the update and flashed the radio part, then informed me the cid error, of course, by this time it had updated the hboot too. So now i have a desire s with an upgraded hboot so i can't flash a new one because of cid error and i can;t go back cos it reports a hboot version error. Where do i look on the system for the p88ing.zip now? can't remember now!
Click to expand...
Click to collapse
It is not relevant which network you are using !!! Just try newest RUU to get control over your phone again in the first place!
Even if you don't get any network access after setup newest RUU you will definitely be abte to execute alpharevx again, flash cwm and flash any stuff you want to.
just tried flashing via fastboot, got a remote bootloader signature fail response (recovery)
Clivectmob said:
just tried flashing via fastboot, got a remote bootloader signature fail response (recovery)
Click to expand...
Click to collapse
I guess that means you tried flashing recovery via fastboot?
Then concentrate on our RUU-suggestions.
Yes, as i said, flashed via fastboot, and i already explained that i cant up/down grade via ruu method because of bootloader version. I can't think of a way out of this as it stands. The only thing that may work is doing it via the p88img method with my original 3uk rom, but i cant find it in my temp files, searched everywhere for it. I've seen it's location posted on here before now, and i've searched it to death and can't seem to find it now
I'm going to extract and upload your 3GUK-PG88*.img although I think you'll need an newer one. Just a few minutes of patience.
My phone is unbranded , unrooted & stock using ROM 1.47.401.4.
I have downloaded the latest ota 2.10.401.4 and in that zip there was a firmware zip in it.
i renamed the firmware zip to pg88img.zip and put it in my phone's sd root.
After the reboot of the phone has updated the firmware BUT thats all.
If i reboot the phone stucks on the HTC logo but also i can go to the bootloader options if on the reboot i hold down the volume button.
Is there any way to restore the phone?
I try to flash the stock rom but nothing.
Can anybody help please??
Resolution:
If anyone has the same problem and has hboot-2.00.0002 & S-ON you have to unlock the bootloader via htcdev.com site following all the steps and flash the EXT4 Recovery via FASTBOOT and NOT ADB.!!
Then go to recovery and flash any custom rom.
avensakias said:
My phone is unbranded , unrooted & stock using ROM 1.47.401.4.
I have downloaded the latest ota 2.10.401.4 and in that zip there was a firmware zip in it.
i renamed the firmware zip to pg88img.zip and put it in my phone's sd root.
After the reboot of the phone has updated the firmware BUT thats all.
If i reboot the phone stucks on the HTC logo but also i can go to the bootloader options if on the reboot i hold down the volume button.
Is there any way to restore the phone?
I try to flash the stock rom but nothing.
Can anybody help please??
Click to expand...
Click to collapse
You can't boot because of new hboot. Have u s-off device ?
Sent from my HTC Desire S using xda premium
No the phone is s-on and up on the screen it says LOCKED.
Never saw LOCKED before.
Is there any way to S-OFF now with the new hboot ??
avensakias said:
No the phone is s-on and up on the screen it says LOCKED.
Never saw LOCKED before.
Is there any way to S-OFF now with the new hboot ??
Click to expand...
Click to collapse
It says locked but nothin is locked. Try to flash 4ext recovery over adb. Should work I think. Instructions in general forum .
Sent from my HTC Desire S using xda premium
Thanks.
i'll try and see whats going to happen.
Which update did you download? There are a couple available - odexed & deodexed.
Maybe worth trying which ever one you didn't download the first time?
Also are you giving it plenty of time to load? First boot from a fresh install always takes a long time.
Don't worry, you don't have a brick
Peace
Sent from my HTC Desire S
Unlock bootloader but still S-ON
Using the http://www.htcdev.com/bootloader/unlock-instructions i managed to get my bootloader UNLOCKED but it still says S-ON.
Tryed to flash the 4EXTvia adb but it says ERROR no device found.
Any other instruction on how to get my DS working again?
Going on bootloader i see:
*** UNLOCKED ***
SAGA PVT SHIP S-ON RL
HBOOT-2.00.0002
RADIO-3822.09.08.20_M
eMMC-boot
Aug 22 2011,15:22:13
Any other suggestion pls??
You need to get your phone s-off using one of the methods in this part of the forum. Then you can install ext4 & new rom
Peace
Sent from my phone
HOW???
My hboot is HBOOT-2.00.0002 and the revolution to s-off is only for hboots 0.98.0000 & 0.98.0002.
Can you be more specific?
The only way that i can communicate to my DS is only via fastboot.
Can anybody help or the phone goes to the trash?? What should i do??
Waiting for stock RUU 2.10.401.4
I believe that the only way to restore the phone is to wait till the stock RUU 2.10.401.4 leak someday..
If anybody else can help me please do.
Thanks.
avensakias said:
I believe that the only way to restore the phone is to wait till the stock RUU 2.10.401.4 leak someday..
If anybody else can help me please do.
Thanks.
Click to expand...
Click to collapse
That would be a choice, but I would say you'll be better of to use xtc-clip to gain s-off, after this everything is possible or just give it back for warranty and let them repair it,
because it's still s-on, but just to know, what else where in the zip?
Could it be that you forgot something, have you tried a factory reset?
Sent from my HTC Desire S using XDA App
Tectas said:
That would be a choice, but I would say you'll be better of to use xtc-clip to gain s-off, after this everything is possible or just give it back for warranty and let them repair it,
because it's still s-on, but just to know, what else where in the zip?
Could it be that you forgot something, have you tried a factory reset?
Sent from my HTC Desire S using XDA App
Click to expand...
Click to collapse
Do you know if I can get it from Greece.?
Does xtc clip works on hboot-2.00.0002.?
avensakias said:
Do you know if I can get it from Greece.?
Does xtc clip works on hboot-2.00.0002.?
Click to expand...
Click to collapse
Xtc-clip works with every version on every HTC device.
Go to a second hand handy shop that also does repairs and stuff like this maybe they get one, I s-offed mine this way for €20^^
Swyped from my HTC Desire S
What did you download originally?
Was it an official ota update, or from this forum?
If you tried to flash the odexed version, many users have problems with this. Can you try the deodexed version?
Sent from my HTC Desire S
I was with the original shipped rom 1.47.401.4 S-ON & UNROOTED.
I downloaded via my computer http://liveimage.htc.com/OTA_Saga_S...1.47.401.4_release_217301kjfuq12qqm0wuhg7.zip
In that zip file there was another zip file called Firmware.zip.
I renamed the firmware.zip to pg88img.zip and i put it in the root of my sd card.
I rebooted holding the volume down button and the phone went to bootloader mode found the pg88img.zip and flashed it.
After that the phone goes only to bootloader showing
*** LOCKED ***
SAGA PVT SHIP S-ON RL
HBOOT-2.00.0002
RADIO-3822.09.08.20_M
eMMC-boot
Aug 22 2011,15:22:13
Is there any way to flash the OTA via fastboot since over adb i get the message device not found..???
Do you have a "recovery" option in the fastboot menu? If so try to go to this menu and see if adb recognises it then. But you have probably tried this already, right.
With adb, when you type 'adb devices', your phone is not shown, correct?
I'm not sure about getting S-off with the new hboot, I did mine with the old hboot.
You could try to download the deodexed rom on this page and flash that, but you need to get into recovery first.
Sorry, not much help I'm afraid.
Did you try to install these fastboot drivers?
Unfortunately i have tried everything so far but didn't work.
The xtc clip maybe is the only way.. Or if the s-off solution of revolution will support in future my hboot and do it that way.
I also noticed that when i tried to flash the stock rom i had 1.47.401.4 and was stuck on the HTC logo the update software said that i had rom 11.10.401.4.!!!!!
Since i flashed the original fota why the version said 11.10.401.4 and not 2.10.401.4??
WTF IS GOING ON.??
Well, I still don't think you have a brick - you can get into the bootloader, you just need your pc to recognise it via USB.
Have you tried flashing the previous hboot version you had? To enable revolutionary s-off?
Also have a look around the general Android forums, there are some very experienced peeps there who may be able to help.
Peace
Sent from my HTC Desire S
avensakias said:
Do you know if I can get it from Greece.?
Does xtc clip works on hboot-2.00.0002.?
Click to expand...
Click to collapse
You should ask this question on the XTC phone tools forum to raskal to be 100% sure that this new version is covered (see link on the XTC in my sig)
and as @tectas has said, there is still a possibility that you are still able to return under warranty and allow them to resolve it for you..
sorry unable to assist with confidence.
EDIT: see this thread that I created a while back that contains another link within it to lots of XTC owners around the world within it, but I'd confirm that the new HBOOT is covered before you run XTC http://forum.xda-developers.com/showthread.php?t=1076937&highlight=xtc
I ask them. Thanks anyway.
The 3 things left.
1. to ask xtc forum if my hboot-2.00.0002 is supported.
2. to wait till revolution s-off supports in the future my hboot.
3. to wait till someone leakes the stock signed ruu 2.10.401.4
That's all unfortunately..
Hey guys
I've got a bit of a situation. A friend of mine gave me this sensation (carrier T-mobiel) wich was all but bricked. Since I have some experience rooting and flashing custom ROMs, he asked me to give it a try at reviving it.
The owner had been messing around a bit himself and he managed to install clockwordmod recovery. Don't know if he installed any ROM, the device gets stuck on splashscreen.
I did the following; full format, superwipe and install a ARHD ROM. result was te same; stuck on splash-screen.
Then I did another full format, wipe and installed Cyanogenmod, still the same result.
I wanted to try and install 4EXT touch recovery, but the device doesn't respond to any USB connection method so ADB won't work. there's no working ROM so installing through the app won't go either. basicly, I don't know if there's a way to uninstall and install a recovery through flashing.
I have another phone to use to store required files on a SDcard.
these are the things dat DO work:
Bootloader, fastboot and clockworkmod recovery v5.8.0.9
this is the device's bootloader information
UNLOCKED
PYRAMID PVT SHIP S-ON RL
HBOOT-1.18.0000
RADIO-10.14.9035.01_M
Aug 2 2011, 22:35:52
my guess is that I'm trying to install ROM's that don't work with the current firmware. I don't know if the owner installed the OTA ICS before he got these problems. But I don't know what firmware is currently on this this device, and how to check it.
Lost for clues here and calling out for help
Onemanshow
onemanshow85 said:
Hey guys
I've got a bit of a situation. A friend of mine gave me this sensation (carrier T-mobiel) wich was all but bricked. Since I have some experience rooting and flashing custom ROMs, he asked me to give it a try at reviving it.
The owner had been messing around a bit himself and he managed to install clockwordmod recovery. Don't know if he installed any ROM, the device gets stuck on splashscreen.
I did the following; full format, superwipe and install a ARHD ROM. result was te same; stuck on splash-screen.
Then I did another full format, wipe and installed Cyanogenmod, still the same result.
I wanted to try and install 4EXT touch recovery, but the device doesn't respond to any USB connection method so ADB won't work. there's no working ROM so installing through the app won't go either. basicly, I don't know if there's a way to uninstall and install a recovery through flashing.
I have another phone to use to store required files on a SDcard.
these are the things dat DO work:
Bootloader, fastboot and clockworkmod recovery v5.8.0.9
this is the device's bootloader information
UNLOCKED
PYRAMID PVT SHIP S-ON RL
HBOOT-1.18.0000
RADIO-10.14.9035.01_M
Aug 2 2011, 22:35:52
my guess is that I'm trying to install ROM's that don't work with the current firmware. I don't know if the owner installed the OTA ICS before he got these problems. But I don't know what firmware is currently on this this device, and how to check it.
Lost for clues here and calling out for help
Onemanshow
Click to expand...
Click to collapse
Hi,
2 things you can try.
1.Run a GingerBread RUU.
Look HERE
2.If that works,try s-off.
Look HERE
Then,you could change firmwares and do whatever you like.
Hi Malybru,
I understand what you suggested and I'm currently working on it. Only I can't find the right RUU for this phone.
Current CID is: T-MOB003
getting it superCID'd was no go since I can't get it S-OFF with the revolutionary utility. is there another way to S-OFF the phone besides revolutionary?
edit: I downloaded and executed a RUU that apearantly wasn't compatible with the phone. I'm guessing it removed whatever ROM was installed, but didn't install the ROM from the RUU.
I also followed step 3; RUU to restore stock up to the part of relocking the bootloader. I didn't come any further cause I can't find the right RUU.
the phone now only boots into bootloader with "security warning" displayed below "relocked".
I'm guessing, if I find the correct RUU with gingerbread, things will be okay again.
on a sidenote, does a RUU install also returns the recovery to stock?
onemanshow85 said:
Hi Malybru,
I understand what you suggested and I'm currently working on it. Only I can't find the right RUU for this phone.
Current CID is: T-MOB003
getting it superCID'd was no go since I can't get it S-OFF with the revolutionary utility. is there another way to S-OFF the phone besides revolutionary?
Click to expand...
Click to collapse
Hi,
RUU does not matter too much as long as it is Europe and GB.
If you can find a dutch tmo ,then even better.
No harm will come if it is the wrong one.
It will only throw up an error.
This will at least get a ROM on your phone,so that you can s-off .
Revolutionary is the easiest way to s-off.
so, to summarize:
the RUU has to be TMO for either UK or EU. Does the radio need to match the one that's currently displayed in the bootloader?
onemanshow85 said:
so, to summarize:
the RUU has to be TMO for either UK or EU. Does the radio need to match the one that's currently displayed in the bootloader?
Click to expand...
Click to collapse
Hi,
The closer the match,the more chance of success.
But close will do.
Yes,with the same radio.
finding a dutch RUU with this radio for TMO is pretty challenging. So I tried it with a german version (DE). Other then that it matches the radio, and the carrier.
the first method through the RUU.exe failed, it tells me to get the right RUU for my carrier/phone.
So I tried it through flashing with a SDcard. I changed the CID in the notepad file in the PG58IMG.zip to T-MOB003. In bootloader, it checks the file twice and after that nothing happens, the regular bootloader screen is prompted.
Then I tried to flash it through fastboot CMD command, pretty much my last option according to the guid you linked me. This also fails with the notification that it failed to verify 12 signatures.
now I found some universal firmware packages but they don't seem to contain any ROM and recovery, only firmware. are there any of these universal packages as complete RUU?
or is there a way to bypass the signature check with a fastboot command?
onemanshow85 said:
finding a dutch RUU with this radio for TMO is pretty challenging. So I tried it with a german version (DE). Other then that it matches the radio, and the carrier.
the first method through the RUU.exe failed, it tells me to get the right RUU for my carrier/phone.
So I tried it through flashing with a SDcard. I changed the CID in the notepad file in the PG58IMG.zip to T-MOB003. In bootloader, it checks the file twice and after that nothing happens, the regular bootloader screen is prompted.
Then I tried to flash it through fastboot CMD command, pretty much my last option according to the guid you linked me. This also fails with the notification that it failed to verify 12 signatures.
now I found some universal firmware packages but they don't seem to contain any ROM and recovery, only firmware. are there any of these universal packages as complete RUU?
or is there a way to bypass the signature check with a fastboot command?
Click to expand...
Click to collapse
Hi,
Try the European RUU with the 10.14 radio that matches yours.
Add your CID in the PG58IMG text file.
Make sure you have the phone in fastboot when you attach your USB cable(it should say "fastboot USB"),and start running the RUU from your PC.
http://db.tt/A7lS7PaD
Here is a link to 4ext touch recovery as a IMG. http://db.tt/KFKpcrhB and here is a pg58img.zip. put the zip file onto the sdcard and boot to boot loader. It will hopefully flash the recovery. If not fast boot flash the IMG. Once you have the recovery installed enable smart flash and then flash the roms. Hopefully that will work for you
Sent from my HTC Sensation using xda premium
tnx for the files.
I tried the suggestions you made but flash from sdcard doesn't work; it checks the file once and doesn't do anything after it.
when I try to flash either one of the files through fastboot I get signature verification fail.
my bootloader says RELOCKED, I got that after following step 3.1 in the RUU flash guide to return to stock. I don't know if this is blocking anything from being flashed with the nasty signature notifications?
also, most like because nothing is installed on my device, when I plug in the USB cable when it's turned off, it automatically swithces on displaying SECURITY WARNING below RELOCKED.
Damn, wasn't fast enough. I'm not sure what the best way to approach this is. Either attempt to full s-off the device with revolutionary/ jupuntobear, or re-unlock your boot loader with htcdev, then fastboot flash the recovery. Then install the rom. Then run jupuntobear to full s-off
Sent from my HTC Sensation using xda premium
heavy_metal_man said the right thing. First focus on unlocking it on hTCdev.com and afterwards, flash a 4Ext Recovery to make things easyer. Then put the device in bootmenu (not in the Graphic shell) and attach a USB, start any Official European RUU that is Gingerbread - with 1.50 in the numbers.
an update
I managed to get it unlocked again with htcdev.com. After that I flashed 4EXT recovery, succesfully.
only thing now I need to do is installing a ROM. I tried the following without succes so far:
with RUU
I can't find a dutch RUU for TMO with radio 10.14.9035 anywhere so I tried the closest match possible, a german one. through the .exe method I get incompatibility errors. So I extracted the ROM/.zip, added my CID and tried with SDcard flash and fastboot flash, both unsuccesfull. Hboot checks the file twice and does nothing afterwards, and fasboot prompts the message "FAILED (remote ** unknown fail)"
Universal firmware package to make sure I'm on 3.32, so I can install ARHD 6.7.2 or any other ICS rom
I took one from http://forum.xda-developers.com/showthread.php?p=21711154#post21711154.
I get the same errors as when I was trying to flash the ROM.zip from the RUU, both with sdcard flash and fastboot flash.
a random Gingerbread ROM
I found this GB ROM http://forum.xda-developers.com/showthread.php?t=1226564.
I installed it through EXT4. after a reboot it's stuck in a bootloop. No splash screen is shown however, it get's to the withe-field-green-HTC-screen and reboots after, showing the same.
I don't understand what's wrong. I got a good recovery now and the bootloader is unlocked. For some reason the ROM's I tried are incompatible with the current state of the device and I can't figure out why. are dutch T-mobile branded phones so tough to crack or what?
also, after a certain step wich I can't remember, my bootloader doesn't display a radio anymore.
Current bootloader:
UNLOCKED
PYRAMID PVT SHIP S-ON RL
HBOOT-1.18.0000
eMMC-boot
Aug 2 2011,22:35:52
EDIT: I would be less restricted in my actions if the damn thing were to be S-OFF. is there any way to get get S-OFF through bootloader/fastboot? All the S-OFF methods and utillities I found so far need the device to have a ROM running.
SOLVED
with help of KGS1992, I managed to restore the device.
- installed a stock GB ROM since I was on hboot 1.18, and to get root acces
- aquired root through adb
- gained S-off with revolutionary
reason why I couldn't manage this before is because I didn't have a genuin stock ROM.
tnx all for the help
onemanshow85 said:
SOLVED
with help of KGS1992, I managed to restore the device.
- installed a stock GB ROM since I was on hboot 1.18, and to get root acces
- aquired root through adb
- gained S-off with revolutionary
reason why I couldn't manage this before is because I didn't have a genuin stock ROM.
tnx all for the help
Click to expand...
Click to collapse
Glad you got sorted pal and thanks for letting us know
hi guys
i have installed some old RUU and it stalled on me, so i'm stuck in bootloader with this.
*** Security Warning ***
SAGA PVT SHIP S-ON RL
HBOOT-0.98.0000
RADIO-38.03.02.11_M
eMMC-boot
What should i do?
BTW i have no goldcard and no way to create one since i can't get to adb (or at least i think so...)
Thanks in advance
I have three questions first:
1. Have you been previously htc dev unlocked
2..has RUU procedure ended successfuly,
or it's stopped with some error
3...why there in not adb access anymore
Name the symptoms
Edit: you hboot is unlockable by revolutionary ( s- off )
Which RUU exactly have you been attempting to install
Is your device branded by any carrier ( branded software or simlock)
tnx for quick reply
1. Yes, i was relocked
2. No, it ended with error
3. I'm stuck in bootloader, i have only fastboot access
edit:
- revolutionary stalls at "waiting for device", maybe it needs adb connection... or i'm doing something wrong...
- RUU_Saga_HTC_Europe_1.28.401.1_Radio_20.28b.30.0805U_38.03.02.11_M_release_177977_signed
- not branded by carrier or simlocked...
nenad_l said:
tnx for quick reply
1. Yes, i was relocked
2. No, it ended with error
3. I'm stuck in bootloader, i have only fastboot access
Click to expand...
Click to collapse
If you're still keen on stock
You best check first whether your device is branded
if not, flash WWE version
Your hboot is one of those that might be s-offed by revolutionary
so, maybe,
it'd be a pity to upgrade it by RUU
Flashing RUU ended up in error because you cannot flash just about anything,
certainly not lower version on top of higher..
Ok, i'd suggest trying to s- off it
or find RUU version =/or < that your phone was shipped with
Was this error- you were having <131> by any chance?
ERROR [140]: BOOTLOADER VERSION ERROR
I'm not sure which RUU is the right one for my device... I have installed this same RUU long time ago when i wanted to downgrade my hboot.
I have intended to go full stock for a while... maybe sell my phone or something...
nenad_l said:
ERROR [140]: BOOTLOADER VERSION ERROR
I'm not sure which RUU is the right one for my device... I have installed this same RUU long time ago when i wanted to downgrade my hboot.
I have intended to go full stock for a while... maybe sell my phone or something...
Click to expand...
Click to collapse
If you wish to pass your device to other hands:
Either find some other higher version like
2.10.401.8,...
or even one of those with < 1 > at the beginning but higher than
one you're trying to flash at the moment,,
Or, go to:
http://forum.xda-developers.com/showthread.php?t=2143855
and ask there- it is help dedicated thread
You may find this interesting to read:
http://forum.xda-developers.com/showthread.php?p=31130746
i hoped to install this RUU, and then allow my device to OTA automatically...
nenad_l said:
i hoped to install this RUU, and then allow my device to OTA automatically...
Click to expand...
Click to collapse
The lattest OTA you'll be able to receive would be:
2.10.401.8... or 9 i do not remember...
You can grab ics 4.0.4 from htcdev site as well- as it has been
released as dev preview only ( no ota )-and flash it( that one probably should go fine)
yep, quietly brilliant greeted me with that famous and annoying sound but it also came as relief...
i have downloaded RUU_SAGA_ICS_35_S_HTC_Europe_14.01.401.2_Radio_20.76.30.0835_3831.19.00.110_release_275068_signed from http://www.htcdev.com/devcenter/downloads and it installed with no problems...
Thank you, asgardr
SAGA PVT SHIP S-ON
HBPOT - 0.98.0000
RADIO-38.03.02.11_M
eMMC-boot
I tried to revert to stock but now the os won't load, can't get the htcdev unlock to work either so can unlock the boot loader and the ruu I'm using is throwing a 140 error. Tried to htc unlock but when asking for the code for it it shows an error in the command.
I feel like I need an older ruu or a way to upgrade the hboot but I'm not sure.
Any help would be appreciated!
chapmana81 said:
SAGA PVT SHIP S-ON
HBPOT - 0.98.0000
RADIO-38.03.02.11_M
eMMC-boot
I tried to revert to stock but now the os won't load, can't get the htcdev unlock to work either so can unlock the boot loader and the ruu I'm using is throwing a 140 error. Tried to htc unlock but when asking for the code for it it shows an error in the command.
I feel like I need an older ruu or a way to upgrade the hboot but I'm not sure.
Any help would be appreciated!
Click to expand...
Click to collapse
Error 140 may ussualy reffer to wrong bootloader version,
the numbers however, are not always the same for similar
issues they reffer to,or perhaps the numbers differ according to
different circumstances they describe- i`m not able to tell you beyond doubt,
but in your case (0.98.xxx) it could be something more like
CID, or region version error,
http://forum.xda-developers.com/showthread.php?t=2143855
posts: #2 and #3- `issues with flashing RUUs`
will sheed some light on that matter for you,
providing that other steps like:
- locking bootloader before flashing a RUU
-always choosing higher RUU version
than the one running on the device
(in a normal circumstances, one is not able to ovewrite higher
bootloader version by the lower one- not without
support of < misc_version >)
you where aware of and complied with.
As for the command, they could sometimes be
little tricky to execute,and must therefore be issued
precise to the letter,
so, always try to find that error in the command first,
before assuming it`s been caused by something like:
- no/broken comunication: PC <--> Phone via ADB,etc..
(but you may also try to look it to that corner
and assure- the obstacle is
not comming from that side)
..To tell you the truth, while flashing RUU- with
all requirements for that procedure fulfilled,
there is very little that might go wrong,
in the end, this is an official conduct that is supported
by device`s manufacturer,...
Another method of loading the stock rom on the NAND,
would be to use PG88IMG method:
-extract the rom.zip from the RUU, (google how to)
-rename it to PG88IMG
-load it on your device`s sdcard
-reboot to bootloader,
let it find an update (this very file)
and flash it...
As for unlocking procedure, it is probably
required to be on a stock rom to proceed-but i might
need a correction here,
or having kept the code obtained in the past-and use that binary,
you've said,you were attempting to come back to stock,
May i ask:
-from what?
-has your device been S-off'ed
in the past-by any chance?
- is 0.98.xxx the hboot that use to be in the device,
or, was that changed after unsuccessful RUU flash,
-what was the original system and sense version
your phone was shipped with,
-and most obvious-most overlooked:
is your phone sim /or firmware branded
to any carrier?
well i tried to use this one:
RUU_Saga_TMO_UK_1.30.110.2_R_Radio_20.28b.30.0805U_38.03.02.11_M_release_180106_signed
i got the 140 error and when i tried this one:
RUU_Saga_S_HTC_Europe_2.10.401.5_Radio_20.4801.30.0822U_3822.10.08.04_M_release_219480_signed
i also tried erasing the boot image and the recovery image using the fastboot commands but im getting some sort of access denied error.
there also seems to be no recovery image so my options are limited, any further thoughts?
I really appreciate your help, hopefully my wife wont kill me!
chapmana81 said:
well i tried to use this one:
RUU_Saga_TMO_UK_1.30.110.2_R_Radio_20.28b.30.0805U_38.03.02.11_M_release_180106_signed
i got the 140 error and when i tried this one:
RUU_Saga_S_HTC_Europe_2.10.401.5_Radio_20.4801.30.0822U_3822.10.08.04_M_release_219480_signed
i also tried erasing the boot image and the recovery image using the fastboot commands but im getting some sort of access denied error.
there also seems to be no recovery image so my options are limited, any further thoughts?
I really appreciate your help, hopefully my wife wont kill me!
Click to expand...
Click to collapse
Try to use <gold card>as my next blind thought,
With a stock recovery, one is limited anyway...
I'd say:
In your case, bootloader is your only recovery