Aplogies if this is not the best starting point but have been reading for 10 hours and am reluctant to take a next step after failure of s-off that has stuck phone in bootloader.
Details
Copied all SD card data to PC
Rooted phone as described by HTCdev
Used SKG utility to attempt s-off
Controlbear got stuck in some strage loop waiting for device after process had started. Never even got prompted to try the wire trick :-( 30 mins later I had to pull the pin
rebooting phone gave me the Controlbear black screen with Green arrow but could now not connect to the device using controlbear just said waiting for device then press any key to exit
Phone will not boot to android OS
when USB connected to phone in bootloader it says FASTBOOT USB and
fastboot devices lists my connected device so USB is OK
Followed instructions at unlimited.io/troubleshooting to try to recover controlbear -f seemed to do somthing so then did
fastboot flash boot recovery_backup.img
which failed could not find image !!!!! der
downloaded 4ext recovery.img
fastboot flash boot recovery.img
worked
Now have
Details of boot
*** UNLOCKED ***
Pyramid PVT SHIP S-ON RL
HBOOT 1.27.0000
Radio 11.24.3504.10_M
OpenADSP-v)2.6.0.2226.00.0131
cMMC-boot
CID reported by fastboot getvar cid is BM__001
Just tried everything from bootloader but always got back bootloader screen no Controlbear screen with arrow as before
At a whim I ran the controlbear -f again and whammo it came up with the 4ext recovery which I was happy to see. Despite doing a backup before starting anything 4ext says no backup present :-(
How can I recover device? I have downloaded the Bell stock RUU which should be correct for this device. Running it says device image version is 3.32.666.13Hesitant to try anything without some good advice. Hopefully I can recover and try the s-off agin but it's been a painful ride. Is it just as simple as clicking update on the RUU exe?
thanks
The backups are not present its saying when you are doing controlbear -f
That means you have no backup present in that controlbear folder
This can be either because of
1.you have another copy of controlbear folder where you done the soff process and where the controlbear saved the backups
(there will be boot_backup.img, recovery_ backup.img)
2.you deleted those images from the controlbear folder
Now what you can do is
1.just find the boot_backup.img and flash it via bootloader
fastboot flash boot boot_backup.img
That will get you out of the Juopunutbear screen..
No need to run the ruu in this case
Edit: and with regards to the 4EXT backup.. The backup will be stored in sdcard and during soff process the sdcard will be wiped.. That's why 4EXT said no backup present.. Just format your sdcard again.. Copy the sdcard backup from your pc (at least copy the Clockworkmod/backup folder to sdcard with the same path in sdcard... It holds your rom backup if you did any)
Then try the 4EXT backup
Sent from my pyramid.. Through blazing fast sonic waves
If your problem was solved, it's a good idea to add [SOLVED] to the topic.
Still in trouble
HI thanks for the advice. Went to the io help and they said relock boot and reflash RUU. Now I have not RUU'd at all as have not been able to find a suitable one. But did fastboot oem lock as suggested. Can I now unlock it again as your post made way more sense and I found the recovery stuff you are speaking of. Just need to unlock and I should be able to recover. is there an unlock command?
markwatson said:
HI thanks for the advice. Went to the io help and they said relock boot and reflash RUU. Now I have not RUU'd at all as have not been able to find a suitable one. But did fastboot oem lock as suggested. Can I now unlock it again as your post made way more sense and I found the recovery stuff you are speaking of. Just need to unlock and I should be able to recover. is there an unlock command?
Click to expand...
Click to collapse
Copy the unlock_code.bin to the folder with adb & fastboot.
Then
Code:
fastboot flash unlocktoken unlock_code.bin
Also, please come down to this channel for support. (I'm only going to help there because you used the tool)
SOLVED
Solved Problem
Hi All Thanks to some sterling efforts by KGS1992 my problem was solved. Take care ye all to ensure that you ensure you get the correct version of controlbear there are many and you need the correct one for your android version. I'll post a detailed summary tomorrow I'm bushed.
Related
So i finally decided to root my phone. i rooted it and got CWM recovery and well i tried updating the firmwire to ics so i can flash an ics rom. and when i updated the firmwire it said cid error update failed. I rebooted my phone but it was stuck on bootloop. i assumed that the firmwire update went through since my phone would't boot up. So i went ahead and flashed the virtous rom and now that doesn't boot up either. i found out that i had to SuperCID first before i flash the ICS Firmwire. But in order to SuperCID my phone has to be On The Home Screen Wich i can not do since my phone is stuck on bootloop >.< ! Help ???
Click my name find post bootloop
Sent from my HTC Sensation XE with Beats Audio using xda premium
19fonzy said:
So i finally decided to root my phone. i rooted it and got CWM recovery and well i tried updating the firmwire to ics so i can flash an ics rom. and when i updated the firmwire it said cid error update failed. I rebooted my phone but it was stuck on bootloop. i assumed that the firmwire update went through since my phone would't boot up. So i went ahead and flashed the virtous rom and now that doesn't boot up either. i found out that i had to SuperCID first before i flash the ICS Firmwire. But in order to SuperCID my phone has to be On The Home Screen Wich i can not do since my phone is stuck on bootloop >.< ! Help ???
Click to expand...
Click to collapse
You are soff?
Did you have fastboot/adb setup?
Can you go into bootloader and post the hboot, radio, son/soff status.
(to go into bootloader remove battery... Put it again then press volume down and power button together... You'll get a white screen.. Post the details from that..)
First of all if you used PG58IMG.zip for firmware update then either remove the file from sdcard via a card reader.. Or just boot into bootloader without sdcard in your phone
sent from my blazing fast pyramid through sonic waves
You can either superCID or add YOUR cid to the firmware file.
Either one is pretty simple. I'm going to assume that you have adb set up already, but if not you'll need that first.
SuperCID:
remove or rename PG58IMG.zip from sdcard
reboot into bootloader (power+vol down)
from adb/fastboot directory:
Code:
fastboot oem writecid 11111111
put PG58IMG.zip back on sdcard
boot into bootloader again and let flash complete
Edit PG58IMG.zip:
extract the zip file
locate the android_info.txt
edit the file with notepad++ to add your cid matching the format of the others listed
compress all extracted files into a new zip and flash
GROGG88 said:
You can either superCID or add YOUR cid to the firmware file.
Either one is pretty simple. I'm going to assume that you have adb set up already, but if not you'll need that first.
SuperCID:
remove or rename PG58IMG.zip from sdcard
reboot into bootloader (power+vol down)
from adb/fastboot directory:
Code:
fastboot oem writecid 11111111
put PG58IMG.zip back on sdcard
boot into bootloader again and let flash complete
Edit PG58IMG.zip:
extract the zip file
locate the android_info.txt
edit the file with notepad++ to add your cid matching the format of the others listed
compress all extracted files into a new zip and flash
Click to expand...
Click to collapse
I'm Such a noob i just got this phone today. I tried doing the Supercid Method but Command prompt isn't recognizing my phone.
and i don't understand the other method
ganeshp said:
You are soff?
Did you have fastboot/adb setup?
Can you go into bootloader and post the hboot, radio, son/soff status.
(to go into bootloader remove battery... Put it again then press volume down and power button together... You'll get a white screen.. Post the details from that..)
First of all if you used PG58IMG.zip for firmware update then either remove the file from sdcard via a card reader.. Or just boot into bootloader without sdcard in your phone
sent from my blazing fast pyramid through sonic waves
Click to expand...
Click to collapse
S-OFF
HBOOT- 1.27.1100
Radio-10.14.9035.01_M
19fonzy said:
S-OFF
HBOOT- 1.27.1100
Radio-10.14.9035.01_M
Click to expand...
Click to collapse
You need to go to fastboot from hboot screen use volume up/down buttons to browse through menu and use power button to enter it once you've selected fastboot.
Then connect your device to your pc
Your phone should read fastboot usb.. Once you've done this
Now go to you pc and
Type fastboot devices
If it shows your device serial number then good its connected
Now to SuperCID
fastboot oem writecid 11111111
This will do.. Make sure it has eight ones
Then after this you can update your firmware using the pg***file you got
sent from my blazing fast pyramid through sonic waves
ganeshp said:
You need to go to fastboot from hboot screen use volume up/down buttons to browse through menu and use power button to enter it once you've selected fastboot.
Then connect your device to your pc
Your phone should read fastboot usb.. Once you've done this
Now go to you pc and
Type fastboot devices
If it shows your device serial number then good its connected
Now to SuperCID
fastboot oem writecid 11111111
This will do.. Make sure it has eight ones
Then after this you can update your firmware using the pg***file you got
sent from my blazing fast pyramid through sonic waves
Click to expand...
Click to collapse
It Worked, Thank you so much
I have the same problem but i dont know how to connect to the computer through fastboot to supercid
BrianM23 said:
I have the same problem but i dont know how to connect to the computer through fastboot to supercid
Click to expand...
Click to collapse
You can use the tool from my signature. It has option for SuperCID.
Please read through the instructions before running the tool.
I don't like starting new threads especially but I have searched and searched and not come up with an answer/problem quite the same as mine. I am not a TOTAL noob and do understand s-on, s-off, htcdev unlock etc. Here goes
I got a Sensation from a friend who acuired it from God knows when but he asked me if it can be fixed. Its currently stuck in fastboot mode. Its Locked S-OFF however NOTHING I try works. Here is some info
BOOTLOADER
*** Locked ***
PYRAMID PVT SHIP S-OFF RL
HBOOT-1.27.0000
eMMC-boot
Jan 13 2012,17:33:34
CID
Is already Super CID = 11111111
RECOVERY
There is no custom recovery flashed and trying to flash recovery via fastboot fails saying "remote: not allowed"
FASTBOOT COMMANDS
Fastboot commands work to get cid etc but get a "remote: not allowed" to erase or flash boot,img, any rom or any hboot or ANYTHING
BOOTLOADER FLASHING
If I try to flash a firmware file through Bootloader, it parses the P58IMG.zip but fails on Bootload saying Fail-PU Partition update failed
FLASH SHIPPED RUU
Trying a shipped ROM also fails. Goes smoothly, reads current image on phone as 1.45.401.3 but once it starts updating, it sticks in waiting for boatloader and gives ERROR[171] while phone has restarted in FASTBOOT mode
HTCDEV Unlock
I thought I would give the HTCDEV method a go even though I know this is redundant since I am already supposedly s-off but even that fails cuz no lock, unlock screen comes up. Flashing of Unlock_boot.bin goes fine
I am at a TOTAL loss now cuz since I am already S-OFF, I should have been able to flash recover or flash a rom or boot image to get phone working again. NOTHING works!!
Any ideas anyone? Apologies if this has been covered before and I couldnt find it.
tabi13 said:
I don't like starting new threads especially but I have searched and searched and not come up with an answer/problem quite the same as mine. I am not a TOTAL noob and do understand s-on, s-off, htcdev unlock etc. Here goes
I got a Sensation from a friend who acuired it from God knows when but he asked me if it can be fixed. Its currently stuck in fastboot mode. Its Locked S-OFF however NOTHING I try works. Here is some info
BOOTLOADER
PYRAMID PVT SHIP S-OFF RL
HBOOT-1.27.0000
eMMC-boot
Jan 13 2012,17:33:34
CID
Is already Super CID = 11111111
RECOVERY
There is no custom recovery flashed and trying to flash recovery via fastboot fails saying "remote: not allowed"
FASTBOOT COMMANDS
Fastboot commands work to get cid etc but get a "remote: not allowed" to erase or flash boot,img, any rom or any hboot or ANYTHING
BOOTLOADER FLASHING
If I try to flash a firmware file through Bootloader, it parses the P58IMG.zip but fails on Bootload saying Fail-PU Partition update failed
FLASH SHIPPED RUU
Trying a shipped ROM also fails. Goes smoothly, reads current image on phone as 1.45.401.3 but once it starts updating, it sticks in waiting for boatloader and gives ERROR[171] while phone has restarted in FASTBOOT mode
HTCDEV Unlock
I thought I would give the HTCDEV method a go even though I know this is redundant since I am already supposedly s-off but even that fails cuz no lock, unlock screen comes up. Flashing of Unlock_boot.bin goes fine
I am at a TOTAL loss now cuz since I am already S-OFF, I should have been able to flash recover or flash a rom or boot image to get phone working again. NOTHING works!!
Any ideas anyone? Apologies if this has been covered before and I couldnt find it.
Click to expand...
Click to collapse
Have you tried playing with fastboot commander? Mabe try formatting all partitions, then installing RUU or PG58IMG ?Or try with different RUUs? The last thing I can think of is to lock the bootloader back, and try to send it to HTC with warranty.
Even fastboot commander, the same as entering commands manually can not flash anything or erase any partition. Dead end there.
tabi13 said:
Even fastboot commander, the same as entering commands manually can not flash anything or erase any partition. Dead end there.
Click to expand...
Click to collapse
what about locking it back to s-on? did you tried it? does it "run" a custom rom ?
First off to use all the fastboot commands you need to have a eng Hboot on the device. You can not use all fastboot commands with a stock Hboot which is what the Hboot 1.27.0000 that you have is. Click on this link to download the JuopunutBear eng Hboot and follow the below instructions to flash it via fastboot.
Code:
fastboot erase cache
fastboot oem rebootRUU
fastboot flash zip jb_hboot.zip
If you still can not get the device up and going using fastboot after flashing the eng Hboot, or if the Hboot will not flash you may have screwed up partitions on the the device. There is a fastboot or a adb command you can use to get a read out of the partitions but I can not remember it right now, just google it you will find it. I mention this because of the "Fail-PU Partition update failed" message you mentioned.
If it does flash the eng Hboot then you should be able to flash a custom recovery or anything else you want to flash via fastboot. If all else fails though do as gallardo5 sayed and flash the stock ROM via RUU while in fastboot and connected to your computer via USB. Then you can try to start from scratch rooting and installing a custom recovery.
T-Macgnolia said:
First off to use all the fastboot commands you need to have a eng Hboot on the device. You can not use all fastboot commands with a stock Hboot which is what the Hboot 1.27.0000 that you have is. Click on this link to download the JuopunutBear eng Hboot and follow the below instructions to flash it via fastboot.
Code:
fastboot erase cache
fastboot oem rebootRUU
fastboot flash zip jb_hboot.zip
If you still can not get the device up and going using fastboot after flashing the eng Hboot, or if the Hboot will not flash you may have screwed up partitions on the the device. There is a fastboot or a adb command you can use to get a read out of the partitions but I can not remember it right now, just google it you will find it. I mention this because of the "Fail-PU Partition update failed" message you mentioned.
If it does flash the eng Hboot then you should be able to flash a custom recovery or anything else you want to flash via fastboot. If all else fails though do as gallardo5 sayed and flash the stock ROM via RUU while in fastboot and connected to your computer via USB. Then you can try to start from scratch rooting and installing a custom recovery.
Click to expand...
Click to collapse
Oh yes, I should have mentioned it. I did even try flashing the JB-hboots, both GB and ICS versions. Neither worked.
It gives error on erase cache, oem rebootRUU reboots back to fastboot and then flashing fails
I think you are spot on about the partitions about being mssed up. Even if they can be read out (i saw the commands somewhere myself) can they be repaired at all?
p.s. Thanks for your help
One more thing I should have mentioned and dont know how I missed, the FASTBOOT page says *** Locked *** not *** Unlocked ***. I dont know if this can/should be changed.
I am sorry in advance if I am being silly
tabi13 said:
One more thing I should have mentioned and dont know how I missed, the FASTBOOT page says *** Locked *** not *** Unlocked ***. I dont know if this can/should be changed.
I am sorry in advance if I am being silly
Click to expand...
Click to collapse
If you have a messed up partition you can not fix it without replacing the whole board. And about the locked in fastboot that is why your fastboot commands are not working. But the fact that you can not flash the eng Hboot sorta tells me you got a bad partition and it will not take the flash. Blackwing had the same issue with his Sensation and all the best guys I know that are over on the IRC Help Now channel could not come up with a fix and finally diagnosed it as bad partitions. Hid was the exact same it would give aerroron erase cache. Find the command to get a read out on the partitions and post the read out here.
T-Macgnolia said:
If you have a messed up partition you can not fix it without replacing the whole board. And about the locked in fastboot that is why your fastboot commands are not working. But the fact that you can not flash the eng Hboot sorta tells me you got a bad partition and it will not take the flash. Blackwing had the same issue with his Sensation and all the best guys I know that are over on the IRC Help Now channel could not come up with a fix and finally diagnosed it as bad partitions. Hid was the exact same it would give aerroron erase cache. Find the command to get a read out on the partitions and post the read out here.
Click to expand...
Click to collapse
Tmac.. I solved one guys FAIL-PU errors.. If the op can boot to recovery.. Maybe we can fix it.. Remember I said we CAN so there's a possibility
Edit: but not now.. Or at least until 20th August.. I'm out of station (as I need to do remotely everything)
Sent from my HTC Sensation 4G using xda premium
gameshp, let me know when you can help me out. IF my friend hasnt given up by then. Thank you
I have the same situation, so I'm really hoping for a solution.
-Revolutionary-
PYRAMID PVT SHIP S-OFF RL
HBOOT-1.27.1100
eMMC-boot
Jan 13 2012,17:33:34
hey ppl im ready ..check your PM's ..and let me know
Did you try to navigate back to "HBOOT" and do a "Factory reset"?
If it does not work, maybe you should flash firmware using JTAG.
marcusgolden said:
I have the same situation, so I'm really hoping for a solution.
-Revolutionary-
PYRAMID PVT SHIP S-OFF RL
HBOOT-1.27.1100
eMMC-boot
Jan 13 2012,17:33:34
Click to expand...
Click to collapse
No you don't have the same problem, cause your bootloader is unlocked
Flash the firmware again and try to flash recovery
i have searched and have found many people with similar problems but none of the solutions have helped me, that said i apologise if ive missed the answer.
so ive used htcdev to unlock my bootloader which went fine then ive decided to "s-off" my phone which has gone fine, well im "s-off"ed however im stuck on the juopunutbear screen everytime i turn the phone on.
ive tried guide on the unlimited.io website - controlbear.exe -r, controlbear.exe -f. when i carry out the next point when i get to "fastboot flash recovery recovery_backup.img" i get a failed.
this i believe has happened because i started the process in kgs1992's aio app which crashed so i shut it and completed in controlbear, i cant think where else i went wrong, ive read loads of guides.
HEEEEEEEEEEEEELLLLPP........gotta ring my dad tomorrow which atm isnt gonna happen!
check the troubleshoot of this thread
it might help
http://forum.xda-developers.com/showthread.php?t=1661631
rzr86 said:
check the troubleshoot of this thread
it might help
http://forum.xda-developers.com/showthread.php?t=1661631
Click to expand...
Click to collapse
have carried out this guide already no fix..any other ideas?
just to fill you in..
controlbear.exe -f
restores from fastboot which it completes then the phone reboots...to the juopunutbear screen!
controlbear.exe -r
restores to normal mode, reset phone, then says the phone should be in normal mode..and is on the juopunutbear screen!!
jesta1988 said:
have carried out this guide already no fix..any other ideas?
just to fill you in..
controlbear.exe -f
restores from fastboot which it completes then the phone reboots...to the juopunutbear screen!
controlbear.exe -r
restores to normal mode, reset phone, then says the phone should be in normal mode..and is on the juopunutbear screen!!
Click to expand...
Click to collapse
did you use the remove_temp_root.bat to return the device in working condition?
if yes then rerun kgs1992's aio and see if you can fix it
i am out of ideas
rzr86 said:
did you use the remove_temp_root.bat to return the device in working condition?
if yes then rerun kgs1992's aio and see if you can fix it
i am out of ideas
Click to expand...
Click to collapse
the temp_route.bat is irrelivent as i didnt use this root method (i used the aio to perm root)
have attempted to use kgs1992's aio as a fix however cant get anywhere i will say when i try and re-"s-off" the phone it says im not rooted then tries to re-root me and fails.
nooo!!..dont quit now!
thanks for the help btw !
jesta1988 said:
the temp_route.bat is irrelivent as i didnt use this root method (i used the aio to perm root)
have attempted to use kgs1992's aio as a fix however cant get anywhere i will say when i try and re-"s-off" the phone it says im not rooted then tries to re-root me and fails.
nooo!!..dont quit now!
thanks for the help btw !
Click to expand...
Click to collapse
Post the boot loader details here ..i can help you after that
Sent from my Nexus 7 using xda premium
ganeshp said:
Post the boot loader details here ..i can help you after that
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
bit noobie not tottally sure what you want me to post...? but heres a guess..
-revolutionary-
PYRAMID PVT SHIP S-OFF RL
HBOOT-1.27.1100
RADIO-11.24A.3504.31_M
OPENADSP-v05.6.0.2226.00.0418
eMMC-boot
jan 13 2012, 17:33:34
jesta1988 said:
bit noobie not tottally sure what you want me to post...? but heres a guess..
-revolutionary-
PYRAMID PVT SHIP S-OFF RL
HBOOT-1.27.1100
RADIO-11.24A.3504.31_M
OPENADSP-v05.6.0.2226.00.0418
eMMC-boot
jan 13 2012, 17:33:34
Click to expand...
Click to collapse
And are you still struck at the juopunutbear screen?
Then what error you got when you used fastboot command?
... wait why did you do juopunutbear when you are already soff?
Edit:
Got the point..
Try those fastboot commands again
Connect the phone properly .. you should connect the phone properly.. If connected properly the phone says FASTBOOT USB .. if it's just saying FASTBOOT then you didn't have drivers installed or the connection is not proper.
If it's saying HBOOT press power button once.. That should take you to required screen
Sent from my Nexus 7 using xda premium
ganeshp said:
And are you still struck at the juopunutbear screen?
Then what error you got when you used fastboot command?
... wait why did you do juopunutbear when you are already soff?
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
when i try to boot into an os it loads to the juopunutbear screen, occasionally restarts itself, but yes.
when i used fastboot command? which command?
i used juopunutbear to get s-off and its been stuck since.
Flash recovery 4ext from fast booth n try flashing Rom
Sent from my HTC Sensation Z710e using xda premium
shrex said:
Flash recovery 4ext from fast booth n try flashing Rom
Sent from my HTC Sensation Z710e using xda premium
Click to expand...
Click to collapse
i have succesfully flash 4ext recovery onto the phone and it is working.
can you suggest a rom? currently downloading Android Revolution HD 6.8.0 to try it with.
can you give me some step by step instructions? worried im never gonna have a phone again.
jesta1988 said:
i have succesfully flash 4ext recovery onto the phone and it is working.
can you suggest a rom? currently downloading Android Revolution HD 6.8.0 to try it with.
can you give me some step by step instructions? worried im never gonna have a phone again.
Click to expand...
Click to collapse
place the zip file in the root of the sdcard
boot to recovery
format all partitions except sdcard
flash the rom
done
rzr86 said:
place the zip file in the root of the sdcard
boot to recovery
format all partitions except sdcard
flash the rom
done
Click to expand...
Click to collapse
This has worked! Thankyou very much for your time!
If Struck on juopunutbear screen:
Well, there's an easy solution if you're struck on the juopunutbear boot screen on your phone. Follow the steps in order:
1.Open the folder where you've extracted the juopunutbear setup files.
2.There'll be a image file in the folder called "boot_backup".
3.Copy that file to the folder you've created during the bootloader unlocking process from HTCDev. The folder contains the fastboot.exe, AdbWinApi.dll etc files, and probably it is in your c:\Android.
4.Rename the copied boot_backup image file to "boot" only.
5.Take out your battery out, reinsert it and boot into the bootloader mode using volume down + power button.
6.You'll see a red writing " fastboot usb"
7.See your computer screen now, the current folder where you copied and renamed.
8.Holding "shift" button on your keyboard, right click inside the folder and select "open command promp window here".
9.Type the command "fastboot flash boot boot.img" and press enter.
10.Then type" fastboot reboot" and press enter.
11.Your phone should reboot normally now.
[****The above method is based on stock sensation rom. If you're struck in a custom rom, then in step 3, copy the boot.img file of the custom rom from where you've downloaded your rom and continue the steps******]
Make sure you unplug all usb devices when doing juopunutbear method, I couldn't do it for hours then I unplugged all devices and restarted PC. It worked on 1st try.
stuck on juopunutbear screen
abachhd said:
Well, there's an easy solution if you're struck on the juopunutbear boot screen on your phone. Follow the steps in order:
1.Open the folder where you've extracted the juopunutbear setup files.
2.There'll be a image file in the folder called "boot_backup".
3.Copy that file to the folder you've created during the bootloader unlocking process from HTCDev. The folder contains the fastboot.exe, AdbWinApi.dll etc files, and probably it is in your c:\Android.
4.Rename the copied boot_backup image file to "boot" only.
5.Take out your battery out, reinsert it and boot into the bootloader mode using volume down + power button.
6.You'll see a red writing " fastboot usb"
7.See your computer screen now, the current folder where you copied and renamed.
8.Holding "shift" button on your keyboard, right click inside the folder and select "open command promp window here".
9.Type the command "fastboot flash boot boot.img" and press enter.
10.Then type" fastboot reboot" and press enter.
11.Your phone should reboot normally now.
[****The above method is based on stock sensation rom. If you're struck in a custom rom, then in step 3, copy the boot.img file of the custom rom from where you've downloaded your rom and continue the steps******]
Click to expand...
Click to collapse
Thank you! You have helped me a lot!
I know that the new roms use a new kernel now.
I'm on 1.14 Hboot
S-ON
*UNLOCKED
*TAMPERED
I am rooted (Not sure if supercid but I assume so)
Since you have to be on 3.18 now, and be S-OFF, Do I have to go back to stock, do official 3.18 OTA and then unlock bootloader and root again?
I'm kind of confused.
(At&t One X)
The best way to do it is just to become s-off and then run the RUU. You need to have SuperCID to get s-off so you'll need to clarify that first. Boot into bootloader, connect your phone to pc (I'm assuming you have adb/fastboot installed on your pc), make sure it says fastboot usb on your phone screen, then open a command prompt in your fastboot folder and issue the following command:
fastboot oem readcid
Hopefully it'll come up as 11111111 or 22222222 and you can continue to the s-off thread here. If it turns out you don't have SuperCID, you'll need to do that first.
While you're doing that you might as well start downloading the 3.18 RUU, then run it once you've completed the previously mentioned steps.
Once the RUU is finished you'll need to flash a custom recovery again, I recommend using TWRP 2.6. Use the following commands:
fastboot flash recovery "TWRP.img"
(Whatever the exact name of the recovery file is, without the talking marks)
fastboot erase cache
fastboot reboot-bootloader
Now you should be able to select recovery and flash whatever ROM you want to.
Sent from my Evita
timmaaa said:
The best way to do it is just to become s-off and then run the RUU. You need to have SuperCID to get s-off so you'll need to clarify that first. Boot into bootloader, connect your phone to pc (I'm assuming you have adb/fastboot installed on your pc), make sure it says fastboot usb on your phone screen, then open a command prompt in your fastboot folder and issue the following command:
fastboot oem readcid
Hopefully it'll come up as 11111111 or 22222222 and you can continue to the s-off thread here. If it turns out you don't have SuperCID, you'll need to do that first.
While you're doing that you might as well start downloading the 3.18 RUU, then run it once you've completed the previously mentioned steps.
Once the RUU is finished you'll need to flash a custom recovery again, I recommend using TWRP 2.6. Use the following commands:
fastboot flash recovery "TWRP.img"
(Whatever the exact name of the recovery file is, without the talking marks)
fastboot erase cache
fastboot reboot-bootloader
Now you should be able to select recovery and flash whatever ROM you want to.
Sent from my Evita
Click to expand...
Click to collapse
I'm trying to get back to stock.
Just sick of this phone.
I didn't know about the 2.20 to 3.18 bricking problem with s-on. so I bricked my phone. warranty replacement on it. got the new on, did the ota update to 3.18. used hasoon's tool to root and unlock the bootloader. got soff, downgraded my touch to use the cm10.1 nightly. and just have had a TON of problems since.
phone turning off, getting stuck in boot loops. tried going to cm10.0 and had the same issues, was able to load a backup from the htc sense rom before I put CM on and even that will reboot and get stuck in a boot loop.
I wish I hadn't touched the damn thing.
Now I'm scared to run the RUU 3.18 because last time it bricked my phone.
I do have my boot loader unlocked, on hboot 2.14 and have s-off.
Should I be okay to run that RUU you listed?
Yeah if you're s-off you can just run the RUU and you'll be back to stock.
Sent from my Evita
timmaaa said:
Yeah if you're s-off you can just run the RUU and you'll be back to stock.
Sent from my Evita
Click to expand...
Click to collapse
Thank you so much! I followed everything you said and it worked, only problem is the TWRP, it freezes for a sec when I click to reboot and then goes unresponsive until it restarts.
A friend has given me his Desire S to fix what I originally thought was just a stuck power button that prevented it from starting up. But the button is now fixes and I've been trying the last few days to get it to start up.
What I have tried so far is to enter Recovery mode, but upon choosing it, the phone would just go to the HTC logo screen, fibrate once and then fibrate agian after a second or two for a few times and the screen would go blank. The same happens with normal bootup. It also seems that the phone is still running with the blank screen because I have to pull the battery to startup again.
I then tried to use the latest RUU (Android 4.0) from HTC but the phone is not recognized by the computer (I think it is because it didn't startup enough to be able to present itself to the computer). So I unlocked it and used fastboot (from Ubuntu as OS) to flash the recovery (recovery_signed.img) and boot (boot_signed.img) from the RUU. With this recovery and normal startup would remain at the HTC screen and wouldn't go blank as before - still fibrates a few times.
I also tried to rename the rom.zip to PG88IMG.zip and putting it on a SD and the bootloader does detect it, but presents the normal boot screen afterwards (I think it complains about it being incorrect - the display is too quick for me to see the error).
Now I also have a Desire S and made a backup of it before I installed a custom ROM. So I also tried the recovery.img that I have from this backup, but then recovery is stuck on the blank screen again.
Is there anything that I did wrong, missed or may not have tried yet? And how can I go about to fix it?
PHONE DETAILS (from bootloader screen)
*** UNLOCKED ***
SAGA PVT SHIP S-ON RL
HBOOT-2.00.0002
RADIO-3822.10.08.04_M
eMMC-boot
The PG88IMG wont work coz ur s-on. Ul need to extract the zip file and put the recovery.img in ur fastboot folder and then flash it from fastboot, volume down + power then select select fastboot then plug ur phone into pc and open a fastboot command window and type
fastboot flash recovery recovery.img
Also a ruu u run from fastboot and u need to relock ur bootloader.
(i dunno how all this is done using ubuntu but thats how on windows so im sure ul know or figure it out)
Ok, didn't know that I needed S-OFF for PG88IMG - thanks for pointing that out . I did flash the recovery (paragraph 3), it is just named `recovery_signed.img` and not 'recovery.img` - I assume that there isn't a difference between the two?
Do I open the RUU while in fastboot on the phone (after relocking) or do I run it from a fastboot command?
(On Ubuntu fastboot is installed as a program so I can call it after I CD to the extracted rom folder and I assume it is working since I didn't get any errors)
Pieter2627 said:
Ok, didn't know that I needed S-OFF for PG88IMG - thanks for pointing that out . I did flash the recovery (paragraph 3), it is just named `recovery_signed.img` and not 'recovery.img` - I assume that there isn't a difference between the two?
Click to expand...
Click to collapse
Well it depends, could be 4ext recovery, CWM, or TWRP. But as far as the name, could be called peterpan.img and it wouldnt matter haha
Pieter2627 said:
Do I open the RUU while in fastboot on the phone (after relocking) or do I run it from a fastboot command?
Click to expand...
Click to collapse
Yh boot ur phone into fastboot, connect it to pc, relock bootloader and then run ruu. The ruu should be exe file so just double click it to run.
Ok, relocked it and went into fastboot mode and then opened the RUU, but was not recognized. Then followed this (droid-now.com/2013/10/fix-working-fastboot-drivers-windows-8-1-x64/) since I used Win 8.1 for the RUU and it flashed successfully.
But it is still stuck on the HTC screen - gave it 30 minutes for the first boot after flash. Recovery is also still stuck, so I reflashed and same issue.
Radio is now 3831.19.00.110