Database Info

Fastboot flash system.img - Possible with unrooted S-ON Stock Sensation?

*********
Hi,
down there you find the original thread/question but i think the only possibility to keep the data on a Sensation with not working touchscreen may be to flash a system.img from a RUU and hope it boots.
Is it possible to flash system.img via fastboot with a locked S-ON Sensation?
Thanks
Regards
Daniel
*********
Hello,
my GF owns a unrooted S-ON completely stock Sensation and did the official german t-mobile update (sorry we did not write the number down).
After the update the phone boots but the touchscreen does not work. You can't enter the pin code and also the volume buttons does not work. Only the power button works "a little bit". You can turn on / off screen but you can't open the shutdown menu.
I can enter Bootloader but as it's locked i don't know what i can do there.
Is it possible to mount the file system to backup some data?
Or is there any other way to apply a official htc firmware WITHOUT DELETING ALL USER DATA?
Thank you very much
PS I should have rooted / s-offed it before, damn it... ;-)

Wrong thread, this should go in Q&A section
Sent from my HTC Sensation XE with Beats Audio Z715e using xda premium

Okay sorry - could someone move it please?

Anyone?
Sent from my Desire HD using XDA App

Okay another idea.
Is it possible to extract a german T-Mobile RUU and just flash the system.img via fastboot? Do i have a chance to make it work again this way?
Or is it not possible to flash system.img when the phone is stock?

hey... i got the same problem.. tried a few things but still no working sensation :/

What did you try?
I think running a T Mobile RUU should work (but the user data is beeing deleted)
Sent from my Desire HD using XDA App

no, there is till now no matching tmob ruu :/

So is it only possible to run a RUU with the exactly same version as on the phone?

please help me
Dacoco said:
*********
Hi,
down there you find the original thread/question but i think the only possibility to keep the data on a Sensation with not working touchscreen may be to flash a system.img from a RUU and hope it boots.
Is it possible to flash system.img via fastboot with a locked S-ON Sensation?
Thanks
Regards
Daniel
*********
Hello,
my GF owns a unrooted S-ON completely stock Sensation and did the official german t-mobile update (sorry we did not write the number down).
After the update the phone boots but the touchscreen does not work. You can't enter the pin code and also the volume buttons does not work. Only the power button works "a little bit". You can turn on / off screen but you can't open the shutdown menu.
I can enter Bootloader but as it's locked i don't know what i can do there.
Is it possible to mount the file system to backup some data?
Or is there any other way to apply a official htc firmware WITHOUT DELETING ALL USER DATA?
Thank you very much
PS I should have rooted / s-offed it before, damn it...
Click to expand...
Click to collapse
My device doesn't start, only I can see is HTC logo in start, I flashed a new Rom but it didn't work, some peoples said that my device ruu is currupt, can anyone please give link to system.img?

Ahmedsiar24 said:
My device doesn't start, only I can see is HTC logo in start, I flashed a new Rom but it didn't work, some peoples said that my device ruu is currupt, can anyone please give link to system.img?
Click to expand...
Click to collapse
Please start a new thread, is the htc logo in black with four "!" signs at the edges of the screen? please give us more information about the phone(s-off?). also there are lots of RUUs in this link, you can just try them or manually pull the files you want from them.

m.m.m said:
Please start a new thread, is the htc logo in black with four "!" signs at the edges of the screen? please give us more information about the phone(s-off?). also there are lots of RUUs in this link, you can just try them or manually pull the files you want from them.
Click to expand...
Click to collapse
Thanks but I couldn't found system.img
And my device is pyramid s-off

Ahmedsiar24 said:
Thanks but I couldn't found system.img
And my device is pyramid s-off
Click to expand...
Click to collapse
Type fastboot getvar all
Post everything except imei and serial number

all info
rzr86 said:
Type fastboot getvar all
Post everything except imei and serial number
Click to expand...
Click to collapse
INFOversion: 0.5
INFOversion-bootloader: 1.27.0000
INFOversion-baseband: 11.23.3504.07_M2
INFOversion-cpld: None
INFOversion-microp: None
INFOversion-main: 3.32.61.51
INFOserialno: SH17MV803118
INFOimei: 358313041667499
INFOproduct: pyramid
INFOplatform: HBOOT-8260
INFOmodelid: PG5813000
INFOcidnum: ORANG001
INFObattery-status: good
INFObattery-voltage: 3854mV
INFOpartition-layout: Generic
INFOsecurity: on
INFObuild-mode: SHIP
INFOboot-mode: FASTBOOT
INFOcommitno-bootloader: 617f0a98
INFOhbootpreupdate: 11
INFOgencheckpt: 0
all: Done!

Ahmedsiar24 said:
INFOversion: 0.5
INFOversion-bootloader: 1.27.0000
INFOversion-baseband: 11.23.3504.07_M2
INFOversion-cpld: None
INFOversion-microp: None
INFOversion-main: 3.32.61.51
INFOserialno: SH17MV803118
INFOimei: 358313041667499
INFOproduct: pyramid
INFOplatform: HBOOT-8260
INFOmodelid: PG5813000
INFOcidnum: ORANG001
INFObattery-status: good
INFObattery-voltage: 3854mV
INFOpartition-layout: Generic
INFOsecurity: on
INFObuild-mode: SHIP
INFOboot-mode: FASTBOOT
INFOcommitno-bootloader: 617f0a98
INFOhbootpreupdate: 11
INFOgencheckpt: 0
all: Done!
Click to expand...
Click to collapse
your device is on S-ON not S-OFF
you can use a ruu.exe for your region but unfortunately there is no ics for your device
and with S-ON you can't downgrade
maybe with a goldcard you can by pass it but i am not sure
by the way is your bootloader locked or unlocked?

info
rzr86 said:
your device is on S-ON not S-OFF
you can use a ruu.exe for your region but unfortunately there is no ics for your device
and with S-ON you can't downgrade
maybe with a goldcard you can by pass it but i am not sure
by the way is your bootloader locked or unlocked?
Click to expand...
Click to collapse
It's unlocked

Ahmedsiar24 said:
It's unlocked
Click to expand...
Click to collapse
flash 4ext recovery
take it from here
http://d-h.st/rG7
extract the recovery.img and flash it via fastboot command
the command is fastboot flash recovery recovery.img
then from for 4ext:
format all partitions except sdcard
enable smartflash(because you are on S-ON)
flash a custom rom
done
note: enable smartflash exactly before flashing the rom

[help] desire s blocked on logo, hboot and fastboot blocked !

Hello,
Here I have a desire s that is s-off with HBOOT 0.98 and is stuck on the htc logo
I tried to put it into the s-on to install an official rom, but I think the fastboot and HBOOT do not work, because I run an RUU, or I try to flash with fastboot is the phone hangs or I receive an error message like "writing 'recovery' ... FAILED (remote: not allowed)"
I note that I have not access to recovery and I could not flash it
HBOOT blocks when I try to flash it or do an update pg88img.zip from sd card
flash by fastboot also blocks
and when I try to do a factory reset it also blocks
Can somebody help me please ?
(translate with google)

I need help please
C:\android-sdk-windows>fastboot getvar all
INFOversion: 0.5
INFOversion-bootloader: 0.98.0002
INFOversion-baseband: 3805.06.02.03_M
INFOversion-cpld: None
INFOversion-microp: None
INFOversion-main: 1.47.771.2
INFOserialno: SH1AVTJ00237
INFOimei: 358967042301901
INFOproduct: saga
INFOplatform: HBOOT-7230
INFOmodelid: PG88*****
INFOcidnum: 11111111
INFObattery-status: good
INFObattery-voltage: 4005mV
INFOpartition-layout: Generic
INFOsecurity: off
INFObuild-mode: SHIP
INFOboot-mode: FASTBOOT
INFOcommitno-bootloader: 0e35ea5b
INFOhbootpreupdate: 12
INFOgencheckpt: 0
all: Done!
finished. total time: 0.016s

maybe you have fried your emmc chip, here you can find a kind of workaround http://forum.xda-developers.com/showthread.php?t=1756287

Thank's
the same probleme "C:\Android-win-tools>fastboot boot bootsd.img
downloading 'boot.img'... OKAY [ 0.766s]
booting... FAILED (remote: not allowed)

I need your help thank you
no commands are accepted in HBOOT and fastboot

You are trying to flash with fastboot commands from HBOOT screen, and have been unable or too lazy to figure it out by a simple Google search with the words you're reading as the command fails.
Open Youtube, look for a video of any HTC phone that shows how to flash using fastboot, do the same.
Learning to search before posting will save you days that you will spend waiting for answers.

that's what you think, I often flash htc to learn better android system and specially the htc
I typed all the errors I got on google and I still have not found the right solution
So if anyone can help me ...

Identify your hboot version fron your phone's screen.
Sent from my HTC Desire S using xda app-developers app

hboot: 0.98.0002
Thank's

Strange version. It's not eng HBOOT (eng is 0.98.2000), so fastboot won't work and isn't expected to.
Get into fastboot mode, and flash an RUU (run RUU.exe). Write down and post the error from the log.

when I try to install an RUU it gets stuck on "Trying to reboot in bootloader" and the phone remains locked until I removed the battery
thank you very much

octopus82 said:
INFOversion-bootloader: 0.98.0002
INFOcidnum: 11111111
INFOsecurity: off
Click to expand...
Click to collapse
Looks like xtcclip S-OFF. IMO there's no way to go back to S-ON.
Try to flash an ENG hboot like 2.00.2002 to be able to flash others parts like recovery or any partition.

octopus82 said:
when I try to install an RUU it gets stuck on "Trying to reboot in bootloader" and the phone remains locked until I removed the battery
thank you very much
Click to expand...
Click to collapse
Even though you start RUU in FASTBOOT screen?
In that case, I don't know if any help can be given. If it locks up upon any attempt to reboot it - something is deeply wrong with it.
And yes, looks like you're unlocked by XTC-clip, it's the only way to get SuperCID (cid=11111111). So no S-ON will be possible anyway. Try to use the warranty on this phone.

chninkel said:
Looks like xtcclip S-OFF. IMO there's no way to go back to S-ON.
Try to flash an ENG hboot like 2.00.2002 to be able to flash others parts like recovery or any partition.
Click to expand...
Click to collapse
I tried to flash some HBOOT with this command "fastboot flash HBOOT hboot.img" but I always had the same error message
if you can give me a link to download eng HBOOT and a good method for flash would be nice
thank you
Jack_R1 said:
Even though you start RUU in FASTBOOT screen?
In that case, I don't know if any help can be given. If it locks up upon any attempt to reboot it - something is deeply wrong with it.
And yes, looks like you're unlocked by XTC-clip, it's the only way to get SuperCID (cid=11111111). So no S-ON will be possible anyway. Try to use the warranty on this phone.
Click to expand...
Click to collapse
yes, I run the RUU in fastbootusb
For the rest I do sauraus tell you how he was flashed
For the warranty I think it is not possible, there is no service htc here, the phone was purchased in another country
You think that there is no solution or there is still hope?
thank you

You could try with the file attached. Rename it PG88IMG.zip, put it on the root of sdcard, reboot bootloader and hit power to accept the update. And ofc hope.

the phone does not want to turn on! and it's not mine!
Is there a way to recover it?!
thank you
P.S: I do not know if the battery has discharged completely, either because I took the battery while the phone was on the htc logo

octopus82 said:
took the battery while the phone was on the htc logo
Click to expand...
Click to collapse
If you have no led when charging, no vibration, nothing. You have probably fried your emmc chip while pulling out the battery. This is a known problem with the desire S and the worst case as you need to change the motherboard.

when I start charging the red light comes on, and when I remove the charger it stays always on
, but no vibration
Is there a solution to turn it on again?
thank you

[Q] How can I revert completely to stock... and is it even needed?

Hi, I received a replacement from AT&T for a phone that had a damaged sim connection, so I am sending back the old one.
My question is how can I revert the phone I am sending back completely to stock?
Currently my bootloader screen shows:
*** LOCKED ***
EVITA PVT SHIP S-OFF RL
CID-11111111
HBOOT-2.14.0000
RADIO-0.24p.32.09.06
OpenDSP-V34.1.0.45.1219
eMMC-boot
Nov 26 2012,12:37:14:-1
Also, if anyone has sent back a non-stock phone, did everything go alright?
----EDIT Sept 08 2013----
In case anyone would like to do something similar, here are the steps I took.
1) Copy off all my data
2) Run the 2.20 RUU
3) fastboot oem writecid CWS__001
4) Factory Reset
5) Check that all my data was deleted
6) fastboot oem writesecureflag 3

antichamp said:
Hi, I received a replacement from AT&T for a phone that had a damaged sim connection, so I am sending back the old one.
My question is how can I revert the phone I am sending back completely to stock?
Currently my bootloader screen shows:
*** LOCKED ***
EVITA PVT SHIP S-OFF RL
CID-11111111
HBOOT-2.14.0000
RADIO-0.24p.32.09.06
OpenDSP-V34.1.0.45.1219
eMMC-boot
Nov 26 2012,12:37:14:-1
Also, if anyone has sent back a non-stock phone, did everything go alright?
Click to expand...
Click to collapse
I would have changed the cid back to stock personally:
fastboot oem writecid CWS__001
I don't think you can with a locked bootloader. But if that Locked is just spoofed, it should be doable.
You could also S-ON:
fastboot oem writesecureflag 3

No, the lock isn't spoofed, but I still have the unlock token.
I probably should have mentioned I still have a custom rom; what order should I reset everything?
Unlock > RUU > UnSuperCID > Relock > S-ON > Done?

You may need to s-on before relock. Other than that. Looks like the right order.
But typically it will say relocked instead of locked unless spoofed.
Sent from my HTC One XL using xda app-developers app

In all honesty being a hardware fault, they likely won't check into it that thoroughly, however I suppose better safe than sorry.

The steps should be
Unlock > RUU > UnSuperCID > S-ON > Relock > Done?
Where is the "Relock" step in your description ?
1) Copy off all my data
2) Run the 2.20 RUU
3) fastboot oem writecid CWS__001
4) Factory Reset
5) Check that all my data was deleted
6) fastboot oem writesecureflag 3
I am asking because I am Unlock and I want to know how to Relock.(back to stock for warranty)
Thanks for your help

1. Backup data.
2. Run 3.18 RUU (must have s-off first).
3. fastboot oem writecid CWS__001.
4. Relock bootloader.
5. Edit relocked flag in bootloader to locked.
6. Factory reset.
Don't worry about making the phone s-on again as they don't worry about this for warranty purposes. It's far more important to change the relocked flag in the bootloader to locked. I've seen one case where having the altered bootloader flags and going back to s-on has bricked the device, so leave it s-off.
Sent from my Evita

timmaaa said:
1. Backup data.
2. Run 3.18 RUU (must have s-off first).
3. fastboot oem writecid CWS__001.
4. Relock bootloader.
5. Edit relocked flag in bootloader to locked.
6. Factory reset.
Don't worry about making the phone s-on again as they don't worry about this for warranty purposes. It's far more important to change the relocked flag in the bootloader to locked. I've seen one case where having the altered bootloader flags and going back to s-on has bricked the device, so leave it s-off.
Sent from my Evita
Click to expand...
Click to collapse
Thanks for your answer,
One more question, if I don't have the last RUU ( I am on Telus) but I have my original Nandroid backup with TWRP (before root and unlock) can I use it to go back to stock ?
Or should I use an old RUU and upgrade to last update OTA after ?
What is the best option
Thanks
Info:
bootloader) version: 0.5
(bootloader) version-bootloader: 2.14.0000
(bootloader) version-baseband: 0.23a.32.09.29
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.17.661.2
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno:
(bootloader) imei:
(bootloader) product: evita
(bootloader) platform: HBOOT-8960
(bootloader) modelid: PJ8310000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 4119mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-97c9a06e
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0

Using a backup only restores the ROM partition to stock, you'll need to use an older RUU and upgrade via OTA. So run the RUU, then return your CID to the Telus CID and take the OTA updates.
Sent from my Evita

Hello everybody,
I'm tired of these custom ROMs. There is always something not working or the phone just doesn't perform as good. Now I just want to return my phone back to stock. I read the thread, as well as some other threads but I'm not sure what the correct steps are. That is why I want to ask again just in case. Here's my phone info AT&T HTC ONE X:
***UNLOCKED***
EVITA PVT S-ON RL
HBOOT-2.14.0000
RADIO-0.24p.32.09.06
OpenDSP-v34.1.0.45.1219
emmc-boot
Nov 26,2012
Rooted
SuperCID-11111111
TWRP Recovery 2.3.6
ViperXL 3.8.0
I have used the [TOOL] OneClick SuperCID for Unlocking Bootloader tool from the forum and unlocked my bootloader through HTC developer webpage. I was unable to S-OFF my device I don't know why.
Is it necessary to S-OFF the device to return it back to stock?
Which RUU should I flash the 2.20 or the 3.18?
And then should I do this:
3) fastboot oem writecid CWS__001
4) Factory Reset
5) Check that all my data was deleted
6) fastboot oem writesecureflag 3
Or this:
3. fastboot oem writecid CWS__001.
4. Relock bootloader.
5. Edit relocked flag in bootloader to locked.
6. Factory reset.
Thank you guys

My suggestion would be to get s-off and then run the 3.18 RUU. You don't really need to worry about locking the bootloader that way, just in case you decide you want the ability to go custom again in the future.
Sent from my Evita

timmaaa said:
My suggestion would be to get s-off and then run the 3.18 RUU. You don't really need to worry about locking the bootloader that way, just in case you decide you want the ability to go custom again in the future.
Sent from my Evita
Click to expand...
Click to collapse
The thing is that I can't get it to s-off. I've everything I found in the forum and I can't turn it off. What if I don't s-off it can I still run the RUU? Or I'll brick my phone?

I have to disagree there, you most likely can get s-off, but haven't found why it isn't working yet. If you run the RUU while s-on it'll brick. That's if the RUU even works, while s-on you can't RUU backwards which I'm assuming also means you can't RUU to the same version you're already on. What ROM have you attempted getting s-off on?
Sent from my Evita

superlamer said:
What if I don't s-off it can I still run the RUU? Or I'll brick my phone?
Click to expand...
Click to collapse
3.18 with S-on and SuperCID is a sure brick. DO NOT ATTEMPT.
---------- Post added at 09:15 AM ---------- Previous post was at 09:11 AM ----------
timmaaa said:
while s-on you can't RUU backwards which I'm assuming also means you can't RUU to the same version you're already on.
Click to expand...
Click to collapse
Same version is normally ok, you just can't go backwards with s-on. Of course I say "normally" since as mentioned with SuperCID and S-on, running 3.18 will brick the device.
timmaaa said:
What ROM have you attempted getting s-off on?
Click to expand...
Click to collapse
Seems like he is trying to S-off on ViperXL 3.8.0. Its a good question, as it seems that some folks have had trouble getting s-off on certain ROMs.
---------- Post added at 09:17 AM ---------- Previous post was at 09:15 AM ----------
superlamer said:
Hello everybody,
I'm tired of these custom ROMs. There is always something not working or the phone just doesn't perform as good. Now I just want to return my phone back to stock.
Click to expand...
Click to collapse
I think you are insane. Stock AT&T ROM is full of bloat and gimped of basic features. There are quite a few stock-based ROMs that are superior to stock AT&T, or even stock rooted ROMs for almost any other carrier but AT&T.
---------- Post added at 09:24 AM ---------- Previous post was at 09:17 AM ----------
superlamer said:
Is it necessary to S-OFF the device to return it back to stock?
Which RUU should I flash the 2.20 or the 3.18?
And then should I do this:
3) fastboot oem writecid CWS__001
4) Factory Reset
5) Check that all my data was deleted
6) fastboot oem writesecureflag 3
Or this:
3. fastboot oem writecid CWS__001.
4. Relock bootloader.
5. Edit relocked flag in bootloader to locked.
6. Factory reset.
Click to expand...
Click to collapse
You don't need s-off to change from SuperCID to CWS__001 using the fastboot command. In theory, you should be able to do this, relock the bootloader, and run the 3.18 RUU.
But again, its not my personal recommendation.

Ok If I am on HBOOT-2.14.0000 and want to S-OFF should I upgrade my firmware to 2.20 using this thread?
http://forum.xda-developers.com/showthread.php?t=1952038
Or I should use the method form this?
http://forum.xda-developers.com/showthread.php?t=2155071
I have tried this method and it didn't work for me, may be I am doing something wrong. Do you know any other ways I can try?
Thanks for the help

superlamer said:
Ok If I am on HBOOT-2.14.0000 and want to S-OFF should I upgrade my firmware to 2.20 using this thread?
http://forum.xda-developers.com/showthread.php?t=1952038
Click to expand...
Click to collapse
That is not a method to upgrade firmware, its a method to root. You are already rooted.
superlamer said:
http://forum.xda-developers.com/showthread.php?t=2423735
I have tried this method and it didn't work for me, may be I am doing something wrong. Do you know any other ways I can try?
Click to expand...
Click to collapse
That is the only method for s-off. So yes that is what you should be using for s-off.
Some folks have had trouble getting S-off on some ROMs. You might try to flash an older ROM (even ICS) and try the Facepalm method again.

Ok, just to make sure I don't screw up my phone before I do this. Sorry for asking things that have already been asked.
I'm on ViperXL 3.2.8 (not 3.8.0 as I said in one of my previous posts). The Android version is 4.1.1
Is there a chance to brick the phone doing this?
These are the steps I should follow correct?
Reboot to bootloader (adb reboot bootloader if "USB Debugging" is enabled in Android)
Run: fastboot oem rebootRUU
Run: fastboot flash zip <PathToFirmware.zip> this zipt file 2.15.0000_5.08.111.2-1.31a.32.45.16_2_10.141.32.34a.zip
If the output ends with "FAILED (remote: 90 hboot pre-update! please flush image again immediately)", run the previous command AGAIN if it fails keeep on trying until it succeeds
If it ends with "INFO..... OK", reboot to the bootloader: fastboot reboot-bootloader
Verify everything was successful by running: fastboot getvar all
If this doesn't work can I flash an ICS rom? The HBOOT version shouldn't matter right?
I also found this thread:
http://forum.xda-developers.com/showthread.php?t=2494998&page=3
Looks like this guy has exactly the same issue as I do. I admin I did not looked at the error it was giving me, I was looking for "INFO..... OK". I will try again and and try to capture the error this time
If everything is successfull I guess I should be able to even upgrade to Android 4.2.2 and not have the random reboots and the signal drops (this is the reason I went back to ViperXL 3.28 and Android 4.1.1).

Hang on. You need s-off to flash that 2.15 firmware package. You're a bit all over the place, what is your end objective?
Sent from my Evita

timmaaa said:
Hang on. You need s-off to flash that 2.15 firmware package. You're a bit all over the place, what is your end objective?
Sent from my Evita
Click to expand...
Click to collapse
Haha sorry about that I used to have Samsung Galaxy S and it was so easy to flash that thing, now with the One X there are so many things I don't know where to start. I guess I want to S-OFF it first. Then I would like to return it to the stock Android like when I bought the phone.

Flash an Android 4.0 or 4.1 Sense ROM and try the Facepalm s-off process, if it doesn't work copy the text from the command prompt and paste it here so we can try to diagnose what's wrong.
Sent from my Evita

[HELP] Messed up with HBOOT. Fail-PU

UPDATE: Phone is in QHSUSB_DLOAD mode. I've tried HTC Unbricking Project but it didn't detect my phone. Also I've tired the Ultimate Recovery tool Unbrick and it also didn't help.
I guess the only solution is JTAG / New phone.
Hello,
I think I'm in a real big trouble.
background story:
I was on ARHD 7.3, S-off, Firmware 3.33 Uni. Suddenly after about a month of use, phone started to lose signal. I could recover the signal only with a reboot (hidden menu options and airplane mode didn't help).
I thought it was a problem with the ROM so I've installed an Official RUU RUU_PYRAMID_LE_ICS_35_S_HTC_Europe_3.33.401.153 after installing 3.33.401.x firmware. This didn't solve the problem I had, signal still was going off few times a day and each time I had to reboot. Furthermore, I've lost my IMEI Number, I got a new IMEI number 355195000000017 which I googled and found more people with that number. However the IMEI change didn't interrupt anything.
Realizing that RUU didn't help I've decided to go back to Mike's ROM ARHD 7.3. (after unlocking bootloader again and etc..)
Then the problem started:
com.google.process.gapps and acore.process.android and basically all the phone started to crash. Nothing helped, I've tried to reflash ROM, reflash Google Package, Nothing. Suddenly, the phone was bricked. won't charge, won't boot.
However a very strange thing happened. Suddenly I could boot Into HBOOT (maybe the phone didn't had enough battery power before).
But the HBOOT was getting stuck, I couldn't do anything So I've used the Ultimate Recovery Tool and downgraded my HBOOT. (http://forum.xda-developers.com/showthread.php?t=1653777)
The Problem now:
1. I can go to 4EXT recovery but it won't let me flash any ROM, installing is aborted.
2. HBOOT won't let me flash any recovery, boot, etc saying permission denined.
3. Rebooting bootloader doesn't work, it goes just to a black screen with backlight on.
4. I've tried to change firmware with PG58IMG it won't update saying hboot partition update failed failed-pu
5.I've tried to install the previous RUU @fastboot but it says battery power below 30%. I've checked the voltage it was around 3800~ and in the recovery it had like 50% so I don;t think problem lies here.
Information about HBOOT:
PYRAMID PVT SHIP S-OFF RL
HBOOT-1.49.0007 <--- Bad Bad HBOOT, I know I did a mistake here. This Hboot is for Evo 3D GSM.
RADIO-11.24.3504.31_M
OPENDSP- BLAH BLAH BLAH
eMMC-boot
I don't think I have SuperCID. when I type the command fastboot getvar cid and getvar all I see the CID number is 0418.
However, when I type fastboot oem readcid I get 11111111.
I've tried to change to superCID but again, permission denined.
I'm thinking maybe if I could somehow change the superCID then I could update the firmware and then I could run the RUU?
Or can I somehow via linux box flash a different HBOOT?
Thank everyone who read this long story
I would be truly grateful for anyone who tries to help me.
EDIT: Phone Info:
[email protected]:~# ./fastboot getvar all
INFOversion: 0.5
INFOversion-bootloader: 1.49.0007
INFOversion-baseband: N/A
INFOversion-cpld: None
INFOversion-microp: None
INFOversion-main: 0.33.401.106
INFOserialno: SH19XV803513
INFOimei: 355195000000010
INFOproduct: pyramid
INFOplatform: HBOOT-8260
INFOmodelid: PG58*****
INFOcidnum: 0418
INFObattery-status: good
INFObattery-voltage: 4000mV
INFOpartition-layout: Generic
INFOsecurity: off
INFObuild-mode: SHIP
INFOboot-mode: FASTBOOT
INFOcommitno-bootloader: edba812f
INFOhbootpreupdate: 11
INFOgencheckpt: 0
all: Done!
Click to expand...
Click to collapse
[email protected]:~# fastboot oem readcid
... INFOcid: 11111111
OKAY
Click to expand...
Click to collapse

failed-pu
man is a serious problem AFAIK
did you try to reflash ruu.exe or install 3.33 universal firmware again?
did they show you failed-pu again?
edit: what hboot version is that?
edit 2: why did you use a tool from htc evo 3D forum?
since you are on S-OFF and supercid you could use any ruu.exe you wanted including GB's one
that would take care also of your hboot version(gingerbread ruu->hboot downgrade)

Thanks for your reply,
rzr86 said:
failed-pu
man is a serious problem AFAIK
did you try to reflash ruu.exe or install 3.33 universal firmware again?
did they show you failed-pu again?
Click to expand...
Click to collapse
Yes, Flashing RUU still giving me the below 30% battery (I've charged all night).
And Installing Firmware 3.33 gives me fail-pu
rzr86 said:
edit: what hboot version is that?
edit 2: why did you use a tool from htc evo 3D forum?
since you are on S-OFF and supercid you could use any ruu.exe you wanted including GB's one
that would take care also of your hboot version(gingerbread ruu->hboot downgrade)
Click to expand...
Click to collapse
Idk, I saw ultimate Recovery tool, thought it would help since nothing worked..
I do have S-Off but I don't have SuperCID (my CID num is very strange only 4 digits now).

Romansko said:
Thanks for your reply,
Yes, Flashing RUU still giving me the below 30% battery (I've charged all night).
And Installing Firmware 3.33 gives me fail-pu
Idk, I saw ultimate Recovery tool, thought it would help since nothing worked..
I do have S-Off but I don't have SuperCID (my CID num is very strange only 4 digits now).
Click to expand...
Click to collapse
try to change your cid again
fastboot oem writecid 11111111
fastboot reboot bootloader
fatsboot getvar cid

Failed-PU
rzr86 said:
try to change your cid again
fastboot oem writecid 11111111
fastboot reboot bootloader
fatsboot getvar cid
Click to expand...
Click to collapse
I've tried that already but it didn't work.
./fastboot oem writecid 11111111
... INFOStart Verify: -1
INFOerase sector 65504 ~ 65535 (32)
INFOemmc_erase(1852): sd_write_sector failed!
OKAY

Romansko said:
I've tried that already but it didn't work.
./fastboot oem writecid 11111111
... INFOStart Verify: -1
INFOerase sector 65504 ~ 65535 (32)
INFOemmc_erase(1852): sd_write_sector failed!
OKAY
Click to expand...
Click to collapse
i don't know what else to suggest man
only ganeshp can help you with that
he has more experience about F-PU
the only thing i can tell you is go for jtag

rzr86 said:
i don't know what else to suggest man
only ganeshp can help you with that
he has more experience about F-PU
the only thing i can tell you is go for jtag
Click to expand...
Click to collapse
Thanks for trying! My phone doesn't boot or charge at all now. I guess JTAG it is.

Romansko said:
Thanks for trying! My phone doesn't boot or charge at all now. I guess JTAG it is.
Click to expand...
Click to collapse
give a try with unbricking project
http://forum.xda-developers.com/showthread.php?t=1522351

rzr86 said:
give a try with unbricking project
http://forum.xda-developers.com/showthread.php?t=1522351
Click to expand...
Click to collapse
I did. My phone's in a QHSUSB_DLOAD mode but it doesn't get detected by the Unbricked project script. I saw other people had the same problem and Dexter advised them to JTAG.

Romansko said:
I did. My phone's in a QHSUSB_DLOAD mode but it doesn't get detected by the Unbricked project script. I saw other people had the same problem and Dexter advised them to JTAG.
Click to expand...
Click to collapse
if dexter advised it then go for it

[Q] Stuck in RUU screen with 4 triangles

Hello,
I tried to flush a RUU downloaded from sticky thread for Sensation. then i got an error saying Please use the correct RUU
RUU_PYRAMID_ICS_HTC_Europe_3.32.401.5_Radio_11.69.3504.00U_11.22.3504.07_M_release_246089_signed.exe
Now i am stuck at RUU mode - screen with grey HTC logo and for triangles in every corner. Cannot get to bootloader, recovery, or start system,
When trying to flash another RUU i am told the phone is not connected via USB..... it is always in RUU screen with 4 triangles.
Is there any solution?
Please help
Thanks

What exactly is your device model? (Sensation/Sensation XE)
In your signature you have this model:
Code:
HTC J One (HTL22) (rooted)
4.2.2 Jellybean with HTC Sense freezed and Apex launcher
Are you S-On/S-Off?
If you have not the right RUU we could help you find it.But first try to give fastboot getvar all command and copy-paste what it prints (Remember to hide your IMEI and device serial number before you upload them here)
You can download the latest Europe RUU for Pyramid from here:
RUU_PYRAMID_ICS_HTC_Europe_3.33.401.6_Radio_11.76A.3504.00U_11.24A.3504.31_M_release_266171_signed.exe
You can check here and download the right RUU if this does not match with your cid.

Hello,
thanks for reply.
1) My phone I am having problem with is HTC Sensation XE - with S-Off hboot 1.27, SuperCID
2) Here is fastboot getvar all result
INFOversion: 0.5
INFOversion-bootloader: 1.27.0000
INFOversion-baseband: 11.24A.3504.31_M
INFOversion-cpld: None
INFOversion-microp: None
INFOversion-main: 3.33.401.6
INFOserialno: HT15HV819028
INFOimei: XXXXXXXXXXXXXXXX
INFOproduct: pyramid
INFOplatform: HBOOT-8260
INFOmodelid: PG5813000
INFOcidnum: 11111111
INFObattery-status: good
INFObattery-voltage: 3831mV
INFOpartition-layout: Generic
INFOsecurity: off
INFObuild-mode: SHIP
INFOboot-mode: RUU
INFOcommitno-bootloader: 617f0a98
INFOhbootpreupdate: 11
INFOgencheckpt: 0
all: Done!
3) I have downloaded RUU from th link you kindly gave. So i sthink it is the correct one. Now, I cannot install RUU.exe, I am getting an error saying the device is not conncted.
I am stuck in RUU screen (grey logo with 4 triangles)
I have SuperCID and S-OFF
Please advise
Are there any fastboot commands that work from RUU screen ?
Thank you

After I let my phone sleep for a night, the phone allowed me to flash Ruu from Ruu screen with 4 triangles...
maybe needed some rest?
Anyway thanks very much for help and suggestions.

Can you use the command fastboot reboot-bootloader to get into bootloader from RUU mode?
I think you have try to install 3.33.401.6 (for my opinion EUROPE) package.Try again with the RUU I gave you in the previous post.If it does nothing for you try to install an official Sensation XE RUU.But as long as you are S-OFF and SuperCID user you shouldn't have some problem to install any RUU even if it brick your device.
You told you have a Sensation XE.So the official RUU for a XE device is a PYRAMID_LE.
You can download the latest EUROPE version from here:
RUU_PYRAMID_LE_ICS_35_S_HTC_Europe_3.33.401.153_Radio_11.76A.3504.00U_11.24A.3504.31_M_release_281004_signed.exe
** Except your INFOimei you should also hide INFOserialno too. **

Hello
I fixed the problem as decribed in revious post. but thank you anyway...
I was not able to use fastboot commands from ruu screen. But now i can, i was not able to load to bootloader, but i was just able to run RUU.exe and it isntalled..
thanks

Gatosbil said:
You have a Sensation XE.So the official RUU for a XE device is a PYRAMID_LE.
*
Click to expand...
Click to collapse
off topic
where did you see that the device is sensation XE?
depending from the hboot version,firmware verison and MID corresponds to a normal sensation

rzr86 said:
off topic
where did you see that the device is sensation XE?
depending from the hboot version,firmware verison and MID corresponds to a normal sensation
Click to expand...
Click to collapse
You are right.I know this may be mistaken but as long as he is s-off and supercid he can flash any RUU he wan'ts.By the way he told by himself he has a Sensation XE device.Anyway I think Sensation RUU's are working with Sensation XE devices so I supposed he had just flashed a wrong RUU to try it to his device.
Of cource I forgot to mention that. (Just those devices are somehow familiar)
** I got corrected my phrase.By the way sometimes the pressure of time is not a good guide. **