Database Info

[RESOLVED] I bricked my Desire S

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..

Cannot Install OTA Update

after I tried to restore my phone by using stock rom and I can turn S-on already.
but after I use OTA update . After downloading OTA it cannot install.
Variant System etc..... cannot remember.
It means that it is not complete restore my phone to original?
Can we solve this problem?

Do you have stock recovery?
Sent from my HTC Sensation XE with Beats Audio using XDA App

yes I recovered from stock RUU in this forum

did you fix it? I have the same problem now.

Can you explain what the problems is? Need some basic info to try to help you!
What modelid?
Which hBoot?
Whats ur CID?
What OS version?
Whats the weather like outside???

SquithyX said:
Can you explain what the problems is? Need some basic info to try to help you!
What modelid?
Which hBoot?
Whats ur CID?
What OS version?
Whats the weather like outside???
Click to expand...
Click to collapse
Got it to work, needed the XE ruu, so i downloaded and ran "RUU_Pyramid_LE_HTC_Europe_1.72.401.1_Radio_10.58.9035.00U_10.15.9035.02_2_release_214840_signed.exe",
Everything worked fine, was back on GB and S-ON. Then I updated the OTA update to ICS, and installed it. Now it won't boot. Just the HTC splash screen, then rebooting again. Can't see the boot animation, just the white screen with green "hTC".
I have booted into bootloader and fastboot, tried boot into recovery, but that didn't work it just rebooted again (and I don't have a recovery installed). I tried "Factory reset" but it just rebooted again. It does not get passed the splash screen. Any help?
Info:
HTC Sensation XE
Pyramid PVT SHIP S-ON RL
HBOOT-1.27.0000
eMMC-boot
Jan 13 2012, 17:33:34
This is what it says in the HBOOT and FASTBOOT.
Any tips on what to do? It will be greatly appreciated.
Edit: saw another thread, maybe the firmware is too old? I thought it got updated with the RUU, but maybe it doesnt? To install a new firmware do i just adb push it to the sd card? As mentioned above I can't get into recovery and mount sd-card.

Ok, whats your CID?
The base rom you needed to install for OTA update was 1.73.401.4 not 1.73.401.1
Did you have s-off??

It's not the FW as it's updated in the OTA - do a factory reset and you should be fine (although you'll lose your data)

@SquithyX: My CID is 11111111, unless it got reset after running the ruu
I had S-OFF but set it to ON, needed to send it in for rep.
@EddyOS: I can't factory reset, when I press it in BOOTLOADER it just get stuck in a boot loop again. I don't have a custom recovery installed due to me beeing S-ON
Also, thanks for help

Are you sure you flashed 1.73.401.1 rom???
Your CID should be the same
If you did, it looks like you need to s-off (not easy now but can be done)
Install 1.73.401.4 GB ROM
Then apply OTA ICS update

thanks, will try to get s-off again? Do you have a guide to get s-off from bootloader/fastboot? I searched around for it but did not get any results

Its not very nice as it uses the HTCDev system by here you go:
http://forum.xda-developers.com/showthread.php?p=21922297#post21922297
You need to downgrade your firmware and install the 1.73.401.4 ROM, from there you will have a smooth upgrade to ICS.

Thanks very much, will give it a go in the morning.

[Q] stuck on splash-screen

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

[Q] HTC one X 4.1.1 Hboot 2.14.000

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

One S 4.1.1 update

Well the update that hit tmous today have any effect on One S user who are already rooted and using a 4.2.2 Rom?
Sent from my One S using xda app-developers app

mrminor13 said:
Well the update that hit tmous today have any effect on One S user who are already rooted and using a 4.2.2 Rom?
Sent from my One S using xda app-developers app
Click to expand...
Click to collapse
No. You must me on the stock rom to get notification. You must then have a locked bootloader and stock recovery to actually run the update.

fbihawk said:
No. You must me on the stock rom to get notification. You must then have a locked bootloader and stock recovery to actually run the update.
Click to expand...
Click to collapse
That's what I thought. I'm excited that I get to see it on my wife's phone.
Sent from my One S using xda app-developers app

fbihawk said:
No. You must me on the stock rom to get notification. You must then have a locked bootloader and stock recovery to actually run the update.
Click to expand...
Click to collapse
Locked bootloader? I have done an update before with an unlocked boot loader. Just curious. Plan to try this afternoon.
Sent from my HTC One S using Tapatalk 2

SoTacMatt said:
Locked bootloader? I have done an update before with an unlocked boot loader. Just curious. Plan to try this afternoon.
Sent from my HTC One S using Tapatalk 2
Click to expand...
Click to collapse
That's been my experience. Try it without if you would like. Can't hurt anything.

i am currently S-off and running viper rom. If I change my cid back to the TMo version and reflash the ruu so I return to stock, would I get the update? DO i need to lock the bootloader and S-ON?

I hav relocked the bootloader bt cn some one provide me stock recovery for cid 044 jelly bean
Sent from my HTC One S using xda app-developers app

Just so you guys know...i dont condone everyone to do this but it worked for me...
Was: SuperCid 111111 , Rooted, and S-Off running latest(before today) Tmo Us rom .
Flashed stock recovery, locked bootloader, ran ota update, unlocked bootloader, flashed twrp, flashed Supersu in said recovery.
Now rooted/supercid/soff on Tmo us jelly bean 4.1.1 ...

aegentirony said:
Just so you guys know...i dont condone everyone to do this but it worked for me...
Was: SuperCid 111111 , Rooted, and S-Off running latest(before today) Tmo Us rom .
Flashed stock recovery, locked bootloader, ran ota update, unlocked bootloader, flashed twrp, flashed Supersu in said recovery.
Now rooted/supercid/soff on Tmo us jelly bean 4.1.1 ...
Click to expand...
Click to collapse
You should not use supercid for an ota there are many reports of bricked phones that way! change your cid to original also stock recovery is a must!

fbihawk said:
That's been my experience. Try it without if you would like. Can't hurt anything.
Click to expand...
Click to collapse
Re-locked bootloader and the RUU is working. Thanks!!!

Have you guys updated your phone yet, and if so were you able to unlock and root again? I just finished restoring the gf's phone back to stock but all her apps were backed up via Titanium and from Viper 2.0, which is JB based. I can't restore her apps and data unless she's on a JB rom, if I remember correctly.
Sent from the other One.

Could someone please point me in the right direction to where I can get my wife's T-MobileUS One S (S4) back to where she can OTA update it to JB? I've been around quite awhile, but am personally a Nexus user and am not very familiar with Sense roms yet. I've done a lot of reading up on it but am getting a little confused. I keep reading about the HBOOT version possibly causing problems? Here is her setup.
Stock 4.0.4/rooted
CWM recovery
CID-T-MOB010
***TAMPERED ***
***UNLOCKED***
VLE PVT SHIP S-ON RL
HBOOT-1.14.0004
RADIO-1.08ts.50.02.16
OpenDSP-v29.1.0.45.0622
eMMC-boot
Aug 14 2012,18:01:48

I'm not sure what ROM my gf was on. First I backed up with Titanium Backup. I flashed the stock recovery with fastboot, locked the bootloader, ran the 2.35 Tmobile RUU (to get her to completely stock), ran the Software Update from the About Menu to get JB, unlocked the bootloader, flashed TWRP recovery with fastboot, and flashed the supersu.zip in TWRP. All is good, I have working root and was able to restore using Titanium. She'll be happy when she wakes up.

Is a locked bootloader necessary?
SoTacMatt said:
Re-locked bootloader and the RUU is working. Thanks!!!
Click to expand...
Click to collapse
Did you try updating without re-locking the bootloader? I was able to update the last time (the security fix they pushed out) without re-locking the bootloader. I'd like to avoid re-locking if possible. I know I need to revert to the stock recovery (that's fine).
--------------
ROM: T-Mobile Stock 4.0.4
HBOOT: 1.14.0005
Recovery: CWM 5.8.3.1
Rooted: Yes

I did try to use the RUU without locking the bootloader. It failed. That is when I did 'fastboot oem lock' and everything else went smoothly!!!

Not necessary to re-lock bootloader for OTA
I can confirm that it is not necessary to re-lock the bootloader to receive the OTA update to JB. I am on Stock TMOUS, rooted and with an unlocked bootloader. I suspect that one needs to re-lock the bootloader only if one is restoring the device to factory settings using an RUU. It certainly isn't required for a successful OTA update.
Here are the steps I followed (assuming you have the android SDK configured and the phone plugged in via USB into a PC):
1. Installed the stock recovery (fastboot flash recovery <name_of_recovery_file.img>)
2. Un-installed Superuser.apk to remove root. ( rm /system/app/Superuser.apk )
3. Rebooted the phone.
4. Checked for system update (Settings - About - Software updates - Check now...)
5. Chose to download the update. It took a while to download even on WiFi.
6. Chose to install the update.
7. Let the phone settle for about 30 minutes. It will not be as responsive during this time.
8. Re-install custom recovery (I use ClockworkMod).
9. Re-install root.
Once the update was complete (step 6 above), I did have a minor issue where the keypad was not showing up for me to enter the PIN to unlock the phone. I rebooted (hold down the Power button for about 10 seconds) and then I was able to get past that just fine.
------------
ROM: T-Mobile US Stock 4.1.1
HBOOT: 2.15.0000
Radio: 1.13.50.05.31
Recovery: CWM 5.8.3.1
Rooted: Yes