Related
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!
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
Hello all
As you can tell Im new to this and thought i would be able to root my device..
Here what I have done I unlocked my device with HTCDev installed CWM 6.0.2.7 treid to boot to recovery no go just stays on a black screen. So then install TWRP 2.4.1.0 Booted to recovery and still the back screen.. so I re-locked the phone and now for some reason all my phone will boot up to is
***TAMPERED***
***Relocked***
EVITA PVT SHIP S-ON RL
HBOOT-2.14.0000
RADIO-0.23a.32.02.29
OpenDSP-v31.1.0.45.28.15
eMMC-boot
Nov 26 2013
So I would like to know before I go buy a new device If this one can be fix and if it can would some one be able to inform me of the steps ? I can still unlock the device but cant boot to any recovery....
I also Tried to Reload the rogers Ruu and keep getting errors.
Please help
Tookie.
Some one please Help I have been working on this for like 20 hours now and I dont have a phone that can be used :S
tookie69 said:
Hello all
As you can tell Im new to this and thought i would be able to root my device..
Here what I have done I unlocked my device with HTCDev installed CWM 6.0.2.7 treid to boot to recovery no go just stays on a black screen. So then install TWRP 2.4.1.0 Booted to recovery and still the back screen.. so I re-locked the phone and now for some reason all my phone will boot up to is
***TAMPERED***
***Relocked***
EVITA PVT SHIP S-ON RL
HBOOT-2.14.0000
RADIO-0.23a.32.02.29
OpenDSP-v31.1.0.45.28.15
eMMC-boot
Nov 26 2013
So I would like to know before I go buy a new device If this one can be fix and if it can would some one be able to inform me of the steps ? I can still unlock the device but cant boot to any recovery....
I also Tried to Reload the rogers Ruu and keep getting errors.
Please help
Tookie.
Some one please Help I have been working on this for like 20 hours now and I dont have a phone that can be used :S
Click to expand...
Click to collapse
Just reflash your unlock code from HTC dev install twrp then flash away
Sent from my HTC One X using Tapatalk 2
Don't panic, this should be an easy fix.
Once you relock, you have to run a ruu or unlock again. But you're trying to run a ruu for older firmware, which is why it's failing.
Just push the unlock token again, and you should be able to boot to recovery. If not, push the recovery image again. I don't recommend CWM, even though it's been ported to this phone. That version of TWRP should work, just confirm that you've got the Evita version.
OK i have unlocked again and re pushed recovery TWRP 2.4.1.0
But I still cant boot into the recovery option..
PLease tell me what im doing wrong..
iElvis said:
Don't panic, this should be an easy fix.
Once you relock, you have to run a ruu or unlock again. But you're trying to run a ruu for older firmware, which is why it's failing.
Just push the unlock token again, and you should be able to boot to recovery. If not, push the recovery image again. I don't recommend CWM, even though it's been ported to this phone. That version of TWRP should work, just confirm that you've got the Evita version.
Click to expand...
Click to collapse
I reflashed the unlcok code I reinstall TWRP but i cant boot into recovery..
is there another way to flash away ?
Kole_Ackerson said:
Just reflash your unlock code from HTC dev install twrp then flash away
Sent from my HTC One X using Tapatalk 2
Click to expand...
Click to collapse
tookie69 said:
I reflashed the unlcok code I reinstall TWRP but i cant boot into recovery..
is there another way to flash away ?
Click to expand...
Click to collapse
I believe through adv but is way simpler to do it through recovery. Try a earlier version of twrp
Sent from my HTC One X using Tapatalk 2
did you verify you are unlocked now, or did you just assume since you pushed the token again?
Also, are you certain you're using the right version of TWRP and not one for another phone (like the endeavour/Tegra One X)?
I pushed the same token and rebooted the device at the top its now says unlocked
DvineLord said:
did you verify you are unlocked now, or did you just assume since you pushed the token again?
Click to expand...
Click to collapse
make sure to run "fastboot erase cache" after changing recovery
IM pretty sure.. I also tried and older TWRP still same issue would you happen to have a link ? I have been using the all in one for HTC one X Tool
iElvis said:
Also, are you certain you're using the right version of TWRP and not one for another phone (like the endeavour/Tegra One X)?
Click to expand...
Click to collapse
bah, all-in-one don't learn anything without doing it yourself. evita is a pretty easy phone once you learn the basics. the op link for twrp in the dev section lists every twrp version officially released for our phone. http://techerrata.com/browse/twrp2/evita
ok i loaded that last night before i went to bed I went this morning to look at the phone and now it just goes to a black screen no madder what I do i put it in the computer the computer goes beep now when its plugged in my computer only the red light at the top flashes and then it disconnects from my computer because i can here the beep of adding and removing hard ware.
is my phone now bricked ?
DvineLord said:
bah, all-in-one don't learn anything without doing it yourself. evita is a pretty easy phone once you learn the basics. the op link for twrp in the dev section lists every twrp version officially released for our phone. http://techerrata.com/browse/twrp2/evita
Click to expand...
Click to collapse
Just relock and boot into boot loader the tampered screen then run a ruu am you should be back to stock
Although I had a EVO before that I flashed the wroung bootloader an bricked it an it wouldn't go anywhere but the bootloader
Sent from my HTC One X using xda premium
If I were you I'd reinstall drivers and manually push the recovery via adb. Use this command- fastboot flash recovery (filename).img
Sent from my HTC One X using Tapatalk 2
Thanks
Thanks for all the help maybe a little late but the issue was the main board on the phone was messed up sent it to HTC and they replaced the board and the battery.. but now i dont need the phone got the HTC one
Rom installation fails on Rogers HTC One X, S-ON, EVITA, HBOOT 2.14.0000
tookie69 said:
Thanks for all the help maybe a little late but the issue was the main board on the phone was messed up sent it to HTC and they replaced the board and the battery.. but now i dont need the phone got the HTC one
Click to expand...
Click to collapse
Hi Guys,
I have the same phone as the specs mentioned below. This is my first android phone and my first time playing around with it.
Here are the specs for "Rogers HTC One X":
***TAMPERED***
***Relocked***
EVITA PVT SHIP S-ON RL
HBOOT-2.14.0000
RADIO-0.23a.32.02.29
OpenDSP-v31.1.0.45.28.15
eMMC-boot
Nov 26 2013
Here is my accomplishments so far:
- Unlocked with HTC Dec, therefore it says unlocked as mentioned above
- Installed TWRP v2.5.0.0, and can successfully boot into recovery
Yet to be done and do not know how to:
- S-OFF
- Super CID
- Permanent Root
Problems installing ROM:
- unable to install. Various errors with different roms, such as:
1) unable to mount sdcard
2) assert failed: getprop("ro.product.device")
3) error executing updater binary in zip
Please advise. Thank you for your time.
Note: the device is locked to Rogers. It is currently in bootloop. I do not know what I did but before installing TWRP, the device went in bootloop after unlocking bootloader and it would simply not start. Although, as mentioned I can successfully boot into the recovery and mount the sdcard from there to transfer files to the phone.
iccrcmember said:
Hi Guys,
I have the same phone as the specs mentioned below. This is my first android phone and my first time playing around with it.
Here are the specs for "Rogers HTC One X":
***TAMPERED***
***Relocked***
EVITA PVT SHIP S-ON RL
HBOOT-2.14.0000
RADIO-0.23a.32.02.29
OpenDSP-v31.1.0.45.28.15
eMMC-boot
Nov 26 2013
Here is my accomplishments so far:
- Unlocked with HTC Dec, therefore it says unlocked as mentioned above
- Installed TWRP v2.5.0.0, and can successfully boot into recovery
Yet to be done and do not know how to:
- S-OFF
- Super CID
- Permanent Root
Problems installing ROM:
- unable to install. Various errors with different roms, such as:
1) unable to mount sdcard
2) assert failed: getprop("ro.product.device")
3) error executing updater binary in zip
Please advise. Thank you for your time.
Note: the device is locked to Rogers. It is currently in bootloop. I do not know what I did but before installing TWRP, the device went in bootloop after unlocking bootloader and it would simply not start. Although, as mentioned I can successfully boot into the recovery and mount the sdcard from there to transfer files to the phone.
Click to expand...
Click to collapse
Why are you relocked?
Unlock again and update TWRP, then try to flash a ROM again. What ROM(s) are you trying to flash.
Be aware that since you are s-off, you will need to extract boot.img from the ROM you are trying to flash, and manually flash with fastboot. You will need to do this every time you flash a ROM, unless you get s-off.
Also, I don't know why you posted to this old thread. Aside from the OP also having the Rogers version, it has nothing to do with your issue. Should have started your own thread.
I'll just clarify that when Redpoint said you need to update TWRP you should update it to TWRP 2.6, your current version (2.5) is very buggy. Also, he means since you are s-on you need to flash the boot.img, when you get s-off this will no longer be required.
Sent from my Evita
Thank you redpoint73
redpoint73 said:
Why are you relocked?
Unlock again and update TWRP, then try to flash a ROM again. What ROM(s) are you trying to flash.
Be aware that since you are s-off, you will need to extract boot.img from the ROM you are trying to flash, and manually flash with fastboot. You will need to do this every time you flash a ROM, unless you get s-off.
Also, I don't know why you posted to this old thread. Aside from the OP also having the Rogers version, it has nothing to do with your issue. Should have started your own thread.
Click to expand...
Click to collapse
I made an error. my bootloader was already unlocked. Any how flashing the boot.img of the Rom before installing the Rom worked. Thank you for your insight. My phone is up and running.
For others: below is the rom i flashed:
[ROM] 10/10 Team Venom ViperX 4.0.4 - Sense 5 JellyBean | orig. OTA | Tweaks
http://forum.xda-developers.com/showthread.php?t=2087443
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
Hey guys, so I bought a HTC Sensation XE yesterday (2nd hand), and it's my very first time owning this phone so I'm completely new here on this forum section.
Anyway, I want to get it to S-OFF and I tried following many different guides. In the end, I got really confused, and since I don't wanna risk bricking my phone, I thought I'd ask for some help. But first, here's some basic information about my phone:
1. Stock ICS v4.0.3
2. Software number - 3.33.709.152
3. Baseband version - 11.76A.3504.00U_11.24A.3504.31_M
4. HBoot - v1.29.0000
5. HTCdev Unlocked
6. CWM recovery installed and Rooted with SuperSu
Ok, so here's what I did. I followed this guide here, since the topic title says it's for any 1.2x HBoot:
http://forum.xda-developers.com/showthread.php?t=1661631
But since I'm already HTCdev Unlocked, then I have to go to this guide instead (as stated in the instructions):
http://forum.xda-developers.com/showthread.php?t=1614617
BUT, the topic clearly says it's for "HBOOT 1.27.0000 with 3.32 ICS Firmware".
So am I suppose to downgrade my HBoot and firmware then? But then, why would the guide (the first link) say it works for any 1.2x HBoot?
Well, I decided to attempt S-OFF anyway by skipping steps #1, #2 and #3 and jumping straight to step #4. I ran ControlBear, and I get the following error:
Connecting to device...
Searching device.....
Found device.....
Backing up......
Transferring backups....
Secondary backup FAILED!!
Press ENTER to exit.....
Click to expand...
Click to collapse
I searched on the net and apparently the "Secondary Backup" shows up if you're using a custom rom (which I'm not). Other than that, I can't find any other info on this.
What should I do here?
anyone?
OK nvm I got it working. Apparently, I flashed the Superuser v3.07.zip file after getting my HTCdev unlock (because I needed to root it in order to attempt S-OFF), and somehow forgot I did that and then rooted it again by flashing SuperSu.
Somehow, having 2 superuser installed will cause Juopunutbear S-OFF to fail.
Anyway, I achieved S-OFF now, and at the end of the process it asked me if I want to install a modified (custom) HBoot, so I chose yes.
It said installed successfully, but it still shows I'm using HBoot v1.29.0000 in the boot menu (power off + volume down).
Is this suppose to be correct? I dunno what advantages there are for installing a custom HBoot, and apparently it's suppose to be v1.27, so I dunno if I did it correctly or not. It does say I have S-OFF in the menu so that went successfully, but not sure about my HBoot.......
get the hboot flashed. it gives you added benefit when you face any issues.
the best was to get a patched hboot flashed is by flashing revolutionary hboot (patch from hboot 1.29.0000 to 1.27.1100 i think -at the end of first post) ..from kohr-ah's firmware thread in sensation development section...flash that like a firmware (instructions in the same thread )
To delete one of the su apps go into system apps folder and delete the one you want.
Sent from my KFTT using xda premium