Database Info

[Q] [HELP] finding for HELP! my DS has been bricked, very hard and hard [HELP]

I tried flashing a new rom for my DS
on this forum:
update-saga-runnymede-s-v5.zip
unluckily
my phone just can turn on once, then it lagged for a long time.
i took out the battery and insert again. turn on again.
badly it lagged again. i repeated
then the third time it stucked at HTC white screen for about an hour
then i tried many times but failed
i try to updated the recovery
'updating recovery' <- this screen has been showing for mayb few hours ( i fell asleep while waiting, when i woke up it's out of battery. then i reboot again but in bootloader NO 'RECOVERY' option!
now my phone has this option but when i choose it it disappears!
so i couldn't flash new recovery through phone
HELP HELP I AM REALLY GETTING CRAZY OF THIS!
can anyone help?

Ok. It seems that your recovery is gone by some reason.
Since you are using adb, I suppose that you have fastboot command also.
Download this file, rename it to recovery.img. Reboot your phone to bootloader (vol down + power), connect it to PC. It should be "FASTBOOT USB" written on the screen. Then open command prompt and type:
Code:
fastboot flash recovery {path to the file}\recovery.img
It should take less than a second to flash it (if longer than you may have troubles with the eMMC chip). If ok reboot to recovery and flash a custom ROM.
If not OK, connect to PC again as described above and type:
Code:
fastboot getvar all
and post the output here.

firstly i haven't tried
Code:
fastboot getvar all
yet since i am still waiting for <waiting for device>
so mayb it has failed.
what should i do to end this and try another method?
close adb directly ?

here is the details when i try fastboot getover all
environmental variables:
ADB_TRACE - Print debug information. A comma separated list
of the following values
1 or all, adb, sockets, packets, rwx, usb, sync
, sysdeps, transport, jdwp
ANDROID_SERIAL - The serial number to connect to. -s takes prior
ity over this if given.
ANDROID_LOG_TAGS - When used with the logcat option, only these de
bug tags are printed.
C:\Users\Chris>fastboot getover all
usage: fastboot [ <option> ] <command>
commands:
update <filename> reflash device from update.zip
flashall flash boot + recovery + system
flash <partition> [ <filename> ] write a file to a flash partition
erase <partition> erase a flash partition
getvar <variable> display a bootloader variable
boot <kernel> [ <ramdisk> ] download and boot kernel
flash:raw boot <kernel> [ <ramdisk> ] create bootimage and flash it
devices list all connected devices
continue continue with autoboot
reboot reboot device normally
reboot-bootloader reboot device into bootloader
options:
-w erase userdata and cache
-s <serial number> specify device serial number
-p <product> specify product name
-c <cmdline> override kernel commandline
-i <vendor id> specify a custom USB vendor id
-b <base_addr> specify a custom kernel base address
-n <page size> specify the nand page size. default:
2048
C:\Users\Chris>

not getover, but getvar
copy the command from my post and paste it to your command prompt to avoid mistakes
EDIT: have you managed to flash the recovery?? the text in the brackets {} has to be replaced with the path to your file - e.g. C:\android
then the command will look like this:
fastboot flash recovery C:\android\recovery.img

sorry for that i missed the word
C:\Users\Chris>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 6.98.1002
(bootloader) version-baseband: 3805.06.02.03_M
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.47.832.1
(bootloader) serialno: SH14MTJ01449
(bootloader) imei: 355067046266979
(bootloader) product: saga
(bootloader) platform: HBOOT-7230
(bootloader) modelid: PG8810000
(bootloader) cidnum: HTC__622
(bootloader) battery-status: good
(bootloader) battery-voltage: 3805mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 361a7ba6
(bootloader) hbootpreupdate: 12
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.031s
here's the result

is it possible that the chip fried while "all done"?

all seems ok. Have you managed to flash the recovery image. My previous post is updated, check it

sorry what do you mean your previous post? which is it?

cckwan said:
sorry what do you mean your previous post? which is it?
Click to expand...
Click to collapse
amidabuddha said:
EDIT: have you managed to flash the recovery??
Click to expand...
Click to collapse
the text in the brackets {} has to be replaced with the path to your file - e.g. C:\android
then the command will look like this:
fastboot flash recovery C:\android\recovery.img

oh now when i type
Code:
fastboot flash recovery C:\Users\Chris\Downloads\recovery.img
it shows:
Code:
sending 'recovery' <6000 kb>
OKAY [0.995s]
writing recovery...
then no continue action
staying here
what should i do the next?

Your next step is to go to the [GUIDE] Read this before going for eMMC replacement in my signature and follow point 4.1
Use this RUU
You will lose S-OFF and root, but eventually your phone will work again

how about my flash recovery still not yet complete...?
btw i am still trying to understand that post step 4.1
but i wanna know is it ok that recovery not yet finished?

4.1 If you have a 6.98.xxxx hboot
You probably already have the adb properly configured on your PC
Change your hboot with this one There are 3 ways:
i should download "this one" right? there are <Eng S-Off.rar> and <PG88IMG.zip> inside.
1) use the one click - it will flash it for you
what means by the 'one click"?
2) put PG88IMG.zip on your SDcard and rebot to bootloader. It will flash automatically. After flashing delete PG88IMG.zip from the SDcard
i can't see my sd card on PC, should i pull out the sd card to another phone and put in the files required then insert back to my phone ?
3) extract the image from PG88IMG.zip, rename it to hboot.img, connect the device to PC, reboot it to bootloader (it should be written "FASTBOOT USB" on the phone, open a command prompt on the PC and type:

sorry...
when i am installing ruu
error occurs: usb connection may lost
so wht can i do><
totally lost now

sorry... now i found i haven't flash hboot.img completely
as it showed: image update is bypassed!
so what should i do?

***updates***
i tried 'fastboot flash hboot G:\a1\hboot.img'
(tried:
http://forum.xda-developers.com/showthread.php?t=1236890
&
http://forum.xda-developers.com/showthread.php?t=1113820
then it showed
Code:
C:\Users\Chris>fastboot flash hboot G:\a1\hboot.img
sending 'hboot' (1024 KB)...
OKAY [ 0.201s]
writing 'hboot'...
(bootloader) image update is bypassed!
OKAY [ 0.029s]
finished. total time: 0.231s
---------------------------------------------------
cannot flash hboot to 0.98.2000 or what
----------------------------------------------------
i can see my serial no. on PC cmd by using 'fastboot devices'
but adb devices shows nothing
---------------------------------------------------
-Revolutionary-
SAGA PUT SHIP S-OFF RL
HBOOT-6.98.1002
RADIO- 3805.06.02.03_M
eMMC-boot
Mar 10 2011, 14:58:38
---------------------------------------------------
WHEN I choose 'recovery' option on fastboot it blacked for 0.1s then fastboot screen again without 'recovery' option
---------------------------------------------------
sleep time now 2:15am here
thank you very much amidabuddha reli so much!
you have done a lot i know but i just need some more help getting my DS turn on again...or there will be a murder news here which parents killed their son sosad
thank you. hope you can reply me ASAP when you are convenient!
--------------------------------------------------
i tried tpbklake'sadvice to flash a cwm recovery but the cmd stayed at writing recovery...

cckwan said:
***updates***
i tried 'fastboot flash hboot G:\a1\hboot.img'
(tried:
http://forum.xda-developers.com/showthread.php?t=1236890
&
http://forum.xda-developers.com/showthread.php?t=1113820
then it showed
Code:
C:\Users\Chris>fastboot flash hboot G:\a1\hboot.img
sending 'hboot' (1024 KB)...
OKAY [ 0.201s]
writing 'hboot'...
(bootloader) image update is bypassed!
OKAY [ 0.029s]
finished. total time: 0.231s
---------------------------------------------------
cannot flash hboot to 0.98.2000 or what
----------------------------------------------------
i can see my serial no. on PC cmd by using 'fastboot devices'
but adb devices shows nothing
---------------------------------------------------
-Revolutionary-
SAGA PUT SHIP S-OFF RL
HBOOT-6.98.1002
RADIO- 3805.06.02.03_M
eMMC-boot
Mar 10 2011, 14:58:38
---------------------------------------------------
WHEN I choose 'recovery' option on fastboot it blacked for 0.1s then fastboot screen again without 'recovery' option
---------------------------------------------------
sleep time now 2:15am here
thank you very much amidabuddha reli so much!
you have done a lot i know but i just need some more help getting my DS turn on again...or there will be a murder news here which parents killed their son sosad
thank you. hope you can reply me ASAP when you are convenient!
Click to expand...
Click to collapse
The Revolutionary HBOOT 6.98.1002 will not allow you to overwrite it. You can only overwrite it using a special version from Revolutionary/AlphaRevX for removing S-OFF and returning to S-ON. Search for Revolutionary return to S-ON.

sorry i am quite new in android
can u tell me how to find revolutionary?
i even dunno what type of file i should search
or can you give me the download link? please

tpbklake said:
The Revolutionary HBOOT 6.98.1002 will not allow you to overwrite it. You can only overwrite it using a special version from Revolutionary/AlphaRevX for removing S-OFF and returning to S-ON. Search for Revolutionary return to S-ON.
Click to expand...
Click to collapse
cckwan said:
sorry i am quite new in android
can u tell me how to find revolutionary?
i even dunno what type of file i should search
or can you give me the download link? please
Click to expand...
Click to collapse
Use the search function of this forum using the key word 'revolutionary s-on'
It should turn up a few threads that address the topic.

VomerGuides [M7]: S-OFF, SuperCID, Firmware Upgrade & Custom Recovery

Welcome to VomerGuides: [M7 Edition]
Have an M8? There's a guide for that!
Hey folks!
Many of you will find this post similar to the ARHD posts I have made.
Based on several suggestions and PM's - I decided to make a separate thread in the hope that this will stop some repeated questions asked in multiple threads.
Following this guide will allow you to (in this sequence):
- Achieve S-OFF using revone
- Change your CID to SuperCID (allowing you to bypass regional ROM restrictions)
- Upgrade to the latest firmware (UL edition) without loosing any data on your SD card
- Install the latest TWRP recovery
Donations:
I do not believe that I should be charging for information sharing. However, having the physical hardware helps me improve this content and support you better as I do require hardware to test/work on for all my content and it's not always possible for me to find someone to borrow devices from.
If you would like to support my work donate to me via:
Thank you
Disclaimer & Copyrights:
I test everything before I share these guides - thus I know they work as intended. However, please proceed at your own risk as I do not take any liability for your devices.
Please do not copy contents of this guide without explicit permission from me. I like to maintain a set standard and quality of the information I share.
Please refrain from posting mirrors as I like to track downloads - I primarily use AndroidFileHost and they mirror files on multiple servers automatically.
I like to track downloads - so please use the official links provided in this guide.
Here is a mirror for all the files in case main links down:
- Firmwares
- Everything Else
Other useful files:
These files can be used to replace/add features in the latest firmware zips posted in this thread.
- Hboot v1.44: http://d-h.st/1zJ
- Touch panel Driver from firmware 2.24.401.1: http://d-h.st/lL4
- Flash-able Radio Collection: http://forum.xda-developers.com/showthread.php?t=2419699
- Going back to stock ROM: http://forum.xda-developers.com/showthread.php?t=2265618
Click to expand...
Click to collapse
Windows Users: It's a good idea to install the HTC drivers on your pc: http://d-h.st/4LL or use this toolkit to install the drivers.
READING & FOLLOWING EACH STEP IS KEY TO SUCCESS.
SECTION 0: SYSTEM PREPARATION:
First we need to get you ADB and fastboot
Windows Users, download this file and extract the folder called "adb" to your C: drive. Your path should look like this:
Code:
C:\adb\
Also, you will need to open a command prompt window using this method:
Code:
Go to the C:\adb\ folder - hold down SHIFT key and RIGHT-CLICK and select "Open command window here".
Mac/Linux users install ADB & fastboot using: Download
1. Extract the downloaded zip to your desktop
2. Open Terminal and type in:
Code:
su
cd Desktop/Android/ (note: Android is the directory extracted from zip file)
3. Now type
Code:
./ADB-Install-Mac.sh
Note: By using the method above, your adb and fastboot files are stored at this location on your Mac: /usr/bin/
SECTION 1: S-OFF & SUPERCID
Downloads Required:
- revone (hboot 1.44)
- rumrunner (hboot 1.5x)
Note: If you are running a 4.4 based ROM and do not want to downgrade to a lower version to use revone or rumrunner - try this tool to S-OFF
Note: revone (used for s-off) has been reported to work best with 4.2.2 roms. Please install a 4.2.2 ROM before attempting S-OFF.
Note: If you are using rumrunner - please follow the instructions to s-off provided on the rumrunner link above. Steps below are for revone only.
Note: Read these useful tips before attempting S-OFF
Mac/Linux users: Save this file to your Desktop
Windows users: Save this file to the C:/adb/ folder
Also, before continuing - make sure you have USB Debugging enabled on your phone (Settings -> Developer Options -> USB Debugging)
If you do not see "Developer Options", Go to Settings > About phone > Software > More > click on build number 10 times. This should enable that section.
Part 1
1. Push revone to your device:
Code:
Mac/Linux: adb push /Users/vomer/Desktop/revone /data/local/tmp/
Windows: adb push C:/adb/revone /data/local/tmp/
2. Open adb shell by writing:
Code:
adb shell
su
3. Write in the shell:
Code:
cd /data/local/tmp
4. Then write this:
Code:
chmod 755 revone
5. Next, write the following command:
Code:
./revone -P
6. Revone reported that I needed to reboot and try again. So I wrote :
Code:
reboot
[COLOR=Red][B]Note:[/B][/COLOR]
[B]Stuck with error: -1?[/B]
When initiating a reboot after "./revone -P" please press and hold the power button for 15 seconds.
To start the entire process from scratch please power off the device and wait 30 seconds, turn it on and continue to ."/revone -P".
7. Close your Command Prompt/Terminal window. Open it again and type:
Code:
adb shell
su
8. Write (to change directory in the phone):
Code:
cd /data/local/tmp
8a. Write the following command:
Code:
./revone -P (it will now say success and ask to reboot phone - do it by typing: reboot)
8b. Once rebooted - repeat steps 7 & 8
9. To get S-OFF & unlock, write the following command:
Code:
./revone -s 0 -u
10. revone will report success. Exit the shell:
Code:
exit (or just close terminal and open a new one)
11. Reboot into bootloader:
Code:
adb reboot bootloader
12. Check if the bootloader screen show's you as S-OFF (it should be in the in the first line under the "pink" highlighted text)
13. Reboot the phone
14. Start the adb shell, again:
Code:
adb shell
15. Change to the folder where revone is stored by typing:
Code:
cd /data/local/tmp
16. Request revone to reset tampered flag by typing:
Code:
./revone -t
17. Exit the adb shell by writing: exit (or just close terminal and open a new one)
18. Reboot to the bootloader by writing:
Code:
adb reboot bootloader
19. Phone should now be S-OFF and tampered flag should be gone
Now stay at this bootloader screen with your phone plugged in to the PC - and follow the steps in Part 2 below.
Part 2
Now lets get you SuperCID:
1. Open terminal/command prompt and type (copy paste command below or make sure there a eight 1's):
Code:
fastboot oem writecid 11111111
2. Reboot phone into bootloader mode (by typing: adb reboot bootloader) and verify CID#. It should look similar to this:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
SECTION 2: FIRMWARE UPGRADE
FIRMWARE FAQ:
Q: Do I need S-OFF for firmware flashing?
A: YES!
Q: Do I NEED to update my firmware?
A: NO! But doing so ensures optimal phone performance.
Q: Does it matter when I flash the firmware (before or after new ROM install)
A: NO!
Q: Will updating the firmware erase my SD card or Apps?
A: NO! The firmware files provided in this guide take care of this for you so none of those get erased.
Q: If I only flash the ROM, will I get updated to the latest firmware?
A: NO!
Q: Can I install a U edition firmware on a UL edition phone?
A: YES, but you might loose the ability to connect to LTE or have some other incompatibilities.
FIRMWARE FLASHING:
Firmware Downloads (SD card will not be wiped using these files):
4.2.2 Base Firmwares:
- 2.17.401.1: http://d-h.st/PJv (Rename to firmware.zip after downloading)
- 2.24.401.1: http://d-h.st/WO9 (Rename to firmware.zip after downloading)
- 2.24.401.8: http://d-h.st/qPT (Rename to firmware.zip after downloading) *LATEST*
4.3 Base Firmwares:
- 3.06.1700.10: http://d-h.st/maA (Rename to firmware.zip after downloading)
- 3.09.401.1: http://d-h.st/PSE (Rename to firmware.zip after downloading)
- 3.17.401.2: http://d-h.st/bgE (Rename to firmware.zip after downloading)
- 3.22.1540.1: http://d-h.st/LLO (Rename to firmware.zip after downloading)
- 3.57.401.500 : http://d-h.st/z6g (Rename to firmware.zip after downloading)
- 3.62.401.1 : http://d-h.st/in6 (Rename to firmware.zip after downloading) *LATEST*
4.4 Base
- 4.06.1540.2 (Rename to firmware.zip after downloading)
- 4.06.1540.3 (Rename to firmware.zip after downloading)
- 4.19.401.8 (Rename to firmware.zip after downloading)
- 4.19.401.9 (Rename to firmware.zip after downloading)
- 4.19.401.11 (Rename to firmware.zip after downloading)
- 5.11.1540.9 (Rename to firmware.zip after downloading)
- 5.11.401.10 (Rename to firmware.zip after downloading)
- 6.06.401.1 (Rename to firmware.zip after downloading)
- 6.09.401.5 (Rename to firmware.zip after downloading)
- 6.09.401.10 (Rename to firmware.zip after downloading) *LATEST*
-----
Windows users, you need to do these steps first:
- move the file you downloaded and renamed (firmware.zip) to the C:\adb\ folder.
- next, in the C:\adb\ folder hold down SHIFT key and RIGHT-CLICK and select "Open command window here".
-----
First, plug in phone to PC and type this in terminal/command prompt:
Code:
adb reboot bootloader
-----
Let's start by checking current system details. Type:
Code:
fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000 [COLOR=Red][B]< This is your bootloader version[/B][/COLOR]
(bootloader) version-baseband: 4A.16.3250.24 [COLOR=Red][B]< This is your radio version[/B][/COLOR]
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.29.666.17 [COLOR=Red][B]< This is your firmware version[/B][/COLOR]
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: <you don't need to know my serial#>
(bootloader) imei: <you don't need to know my IMEI>
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: 11111111 [COLOR=Red][B]< This is your CID[/B][/COLOR]
(bootloader) battery-status: good
(bootloader) battery-voltage: 4077mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
Now type:
Code:
fastboot reboot-bootloader
After that, type:
Code:
fastboot oem rebootRUU
Note: You should see a silver HTC logo come up on your phone after executing this command.
Note: if this command freezes, just disconnect the USB cable and hold the power and volume down buttons until the device reboots. Then, repeat the steps above again.
Finally:
Code:
fastboot flash zip /Users/vomer/Desktop/firmware.zip
Windows users: your command will look something like this: fastboot flash zip C:\adb\firmware.zip
Got this:
Code:
sending 'zip' (71868 KB)...
OKAY [ 4.936s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
(bootloader) checking custom ID...
(bootloader) start image[hboot] unzipping for pre-update check...
(bootloader) start image[hboot] flushing...
(bootloader) [RUU]WP,hboot,0
(bootloader) [RUU]WP,hboot,99
(bootloader) [RUU]WP,hboot,100
(bootloader) ...... Successful
FAILED (remote: 90 hboot pre-update! please flush image again immediately)
finished. total time: 6.410s
Repeated same command:
Code:
fastboot flash zip /Users/vomer/Desktop/firmware.zip
Got this:
Code:
sending 'zip' (71868 KB)...
OKAY [ 4.884s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
(bootloader) checking custom ID...
(bootloader) start image[adsp] unzipping & flushing...
(bootloader) [RUU]WP,adsp,0
(bootloader) [RUU]WP,adsp,100
(bootloader) ...... Successful
(bootloader) start image[cir] unzipping & flushing...
(bootloader) ...... Successful
(bootloader) start image[rpm] unzipping & flushing...
(bootloader) [RUU]WP,rpm,0
(bootloader) [RUU]WP,rpm,100
(bootloader) ...... Successful
(bootloader) start image[sbl1-1] unzipping & flushing...
(bootloader) signature checking...
(bootloader) verified fail
(bootloader) ..... Bypassed
(bootloader) start image[sbl1-2] unzipping & flushing...
(bootloader) signature checking...
(bootloader) verified fail
(bootloader) ..... Bypassed
(bootloader) start image[sbl1-3] unzipping & flushing...
(bootloader) signature checking...
(bootloader) [RUU]WP,sbl1-3,0
(bootloader) [RUU]WP,sbl1-3,100
(bootloader) ...... Successful
(bootloader) start image[sbl2] unzipping & flushing...
(bootloader) [RUU]WP,sbl2,0
(bootloader) [RUU]WP,sbl2,100
(bootloader) ...... Successful
(bootloader) start image[sbl3] unzipping & flushing...
(bootloader) [RUU]WP,sbl3,0
(bootloader) [RUU]WP,sbl3,100
(bootloader) ...... Successful
(bootloader) start image[tp] unzipping & flushing...
(bootloader) ...... Successful
(bootloader) start image[tz] unzipping & flushing...
(bootloader) [RUU]WP,tz,0
(bootloader) [RUU]WP,tz,100
(bootloader) ...... Successful
(bootloader) start image[radio] unzipping & flushing...
(bootloader) [RUU]WP,radio,0
(bootloader) [RUU]WP,radio,26
(bootloader) [RUU]WP,radio,53
(bootloader) [RUU]WP,radio,79
(bootloader) [RUU]WP,radio,100
(bootloader) ...... Successful
OKAY [ 39.601s]
finished. total time: 44.485s
Note: On my phone's screen the green bar did not go to 100% of the bar ... but everything seemed ok so I moved on.
Last Step:
Code:
fastboot reboot
Then I went back to the bootloader mode (after the phone reboots successfully):
Code:
adb reboot bootloader
Checked if the update worked:
Code:
fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.54.0000 [COLOR=Red][B]< Looks New![/B][/COLOR]
(bootloader) version-baseband: 4A.17.3250.14 [COLOR=Red][B]< Looks New![/B][/COLOR]
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 2.24.401.1 [COLOR=Red][B]< Looks New![/B][/COLOR]
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: you don't need to know my serial#
(bootloader) imei: you don't need to know my IMEI#
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: 11111111 [COLOR=Red][B]< Oh Look! I'm Superman :) [/B][/COLOR]
(bootloader) battery-status: good
(bootloader) battery-voltage: 4331mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-d16dc66985
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.061s
SECTION 3: RECOVERY
Note: I personally prefer TWRP - so my guide below points to using TWRP.
If you like CWM, you can follow the same steps but with the latest CWM file.
----
Get latest TWRP: http://techerrata.com/browse/twrp2/m7ul
With your phone plugged into your PC, type in:
Code:
adb reboot bootloader
Once in bootloader mode, type:
Code:
Mac/Linux: fastboot flash recovery /Users/vomer/Desktop/openrecovery-twrp-2.6.1.0-m7.img
Windows: fastboot flash recovery C:\adb\openrecovery-twrp-2.6.1.0-m7.img
Then:
Code:
fastboot reboot
You are now the the latest version of TWRP.
----
That's it! Enjoy your new found freedom

finally you made own thread

descenpet said:
finally you made own thread
Click to expand...
Click to collapse
haha yes sir! got so many PM's to do it but I didn't want to half-ass it. Had some time today so decided to get it done the proper way!

It is necessary to have bootloader unlocked?
Sent from my HTC One using xda premium

Omg thank you so much I hope this will fix my sleep of death on cm roms issue.

Amazing and easy to follow. Thanks OP

vengadorhq said:
It is necessary to have bootloader unlocked?
Sent from my HTC One using xda premium
Click to expand...
Click to collapse
Yes, bootloader must be unlocked if your looking to do any customization!

STICKY THIS THREAD!!!
Great guide!

Wait... I need to re-lock my bootloader and remove root and go back to stock to get S-OFF? o.o?

aulterra said:
Wait... I need to re-lock my bootloader and remove root and go back to stock to get S-OFF? o.o?
Click to expand...
Click to collapse
What?
Sent from my HTC One using xda premium

Wonderful thread. It's of no use to me, but I tossed you a Thanks because when it concerns S-OFF, the simplest and most easy-to-follow guides make all the difference for frightened users.
Thanks!

descenpet said:
What?
Sent from my HTC One using xda premium
Click to expand...
Click to collapse
Well i'm rooted and have my bootloader unlocked from htcdev but i'm S-ON so do I need to relock to use revone to get S-OFF? Or not? Or relock and un root? Or?

aulterra said:
Well i'm rooted and have my bootloader unlocked from htcdev but i'm S-ON so do I need to relock to use revone to get S-OFF? Or not? Or relock and un root? Or?
Click to expand...
Click to collapse
No relock needed
Sent from my HTC One using xda premium

Devaster said:
No relock needed
Sent from my HTC One using xda premium
Click to expand...
Click to collapse
So I can Go ahead now and get S-OFF right now using revone even with an already unlocked bootloader?

aulterra said:
So I can Go ahead now and get S-OFF right now using revone even with an already unlocked bootloader?
Click to expand...
Click to collapse
Yes
Sent from my Nexus 7

vomer said:
Yes
Sent from my Nexus 7
Click to expand...
Click to collapse
Ok sounds great. Do you think that once I have S-OFF and Super CID that the Firmware update will fix my Sleep of Death issues on CM roms? codeworkx said the issue is from what he said a KGSL derp or something. The firmware update would update the gpu driver or update stuff that would effect the gpu driver?
Just wondering, thanks for the amazing guide btw, easiest i've seen so far to follow. Will be doing it tonight after work. Wanted to do it now but I decided not to since I need my phone charged as much as possible before I go to work today (have to get into work early and I didn't know until before so My phone was nearly flat xD)

aulterra said:
Ok sounds great. Do you think that once I have S-OFF and Super CID that the Firmware update will fix my Sleep of Death issues on CM roms? codeworkx said the issue is from what he said a KGSL derp or something. The firmware update would update the gpu driver or update stuff that would effect the gpu driver?
Just wondering, thanks for the amazing guide btw, easiest i've seen so far to follow. Will be doing it tonight after work. Wanted to do it now but I decided not to since I need my phone charged as much as possible before I go to work today (have to get into work early and I didn't know until before so My phone was nearly flat xD)
Click to expand...
Click to collapse
I am not sure on gpu drivers, but this should solve the issue if it is firmware related.
Sent from my Nexus 7

Superb guide! Thanks a lot bro!

Do you no how to get rid of the red writing in boot up splash screen. One thread I read is very confusing. Do I just flash the modified hboot zip?
Sent from my HTC One

Excellent guide, should definitely be stickied. Thanks Vomer :beer: :beer: :beer:
Sent from my HTC One using Tapatalk 2

[Q] Drivers for recovery not installed.

Hello there, recently i got my One S (S4 - 1,5GHz dual core), now im trying to gain root and make s-off, but when i enter the recovery. Win7 starts to install drivers, but after few seconds it says "Fail to install drivers" and phone restarts.
And in ADB (cmd propt) it says - "
Code:
error: device not found
" when i tried to push files or smtin else.
And i am not able to turn on Debuging mode, because i have not got working android on my phone.
So there are any passway to gain root and make s-off? Installing trird party drivers so pc can recognize phone?
Thanks, waiting for answer.
.edit tried this - http://forum.xda-developers.com/showthread.php?t=1644730
And this is what pc says -
http://www.bildites.lv/viewer.php?file=vj3jdvo2c40vt1lqto6r.png
After 1 min ...
http://www.bildites.lv/viewer.php?file=t35ob5ubdnupxxgur44.png
Why???
-----------------------------------------------------------------------------
Im really stuck at this ... Im getting error that device is not found, but i had installed all drivesrs, htc sync etc ...
I locked bootloader, to flash RUU.exe, but Im getting Error [130] - ID model error
So i decided to flash some ROM, but now im reunlocking bootloader by HTC dev, and there another error -
Code:
Error Code: Invalid Bootloader Token Length.
Error Reason: The submitted Token appears to be the wrong length and won't work.
My code (w/o spaces, etc)
Code:
<<<< Identifier Token Start >>>>
3754E3D1ECFA48847C155B76C63A4A44
9789FD9AC4A7C6509E0B32F7D973C421
2A597C06941493D004751FD6F74F2720
D62EF475879305467F0077DF81451D24
51D4DC5B9440DBB1378571A44568F8D8
07948341BF8420F913CE81807194BDA0
29B4DDADA05E76CFB7DBD0E5FEF03D83
FE8B0E7C053309DBBD6C06AC93CF2B6B
95B6D1EDEDBCF950F6C3E33E8BE092CE
001A4CA21DB2291004590E1A671F0F36
D0A17A102BF8353FDD0BF39E78FA8808
7D10A58A6D886BF089A1150C576436F5
9B92E142FA2280C4174F93A51CE970BE
91E2A039DEEAE8451FB8D451ACB3F00E
F10F142D555E2E2FE07EDAF6AEE84B39
570895B7030E33C145E5A35F9AE147BF
<<<<< Identifier Token End >>>>>
So thats all ... My phone stats in bootloader ...
Code:
HBoot - 2.13.0000
Radio - 1.11.50.05.28
Helppp....!
------------------------------------------------------------------------
(bootloader) version: 0.5
(bootloader) version-bootloader: 2.13.0000
(bootloader) version-baseband: 1.11.50.05.28
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HT23TW405786
(bootloader) imei: 359901041281029
(bootloader) product: vle
(bootloader) platform: HBOOT-8960
(bootloader) modelid: PJ4010000
(bootloader) cidnum: H3G__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3927mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-26dff973
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.064s

Im really stuck at this ... Im getting error that device is not found, but i had installed all drivesrs, htc sync etc ...
I locked bootloader, to flash RUU.exe, but Im getting Error [130] - ID model error
So i decided to flash some ROM, but now im reunlocking bootloader by HTC dev, and there another error -
Code:
Error Code: Invalid Bootloader Token Length.
Error Reason: The submitted Token appears to be the wrong length and won't work.
My code (w/o spaces, etc)
Code:
<<<< Identifier Token Start >>>>
3754E3D1ECFA48847C155B76C63A4A44
9789FD9AC4A7C6509E0B32F7D973C421
2A597C06941493D004751FD6F74F2720
D62EF475879305467F0077DF81451D24
51D4DC5B9440DBB1378571A44568F8D8
07948341BF8420F913CE81807194BDA0
29B4DDADA05E76CFB7DBD0E5FEF03D83
FE8B0E7C053309DBBD6C06AC93CF2B6B
95B6D1EDEDBCF950F6C3E33E8BE092CE
001A4CA21DB2291004590E1A671F0F36
D0A17A102BF8353FDD0BF39E78FA8808
7D10A58A6D886BF089A1150C576436F5
9B92E142FA2280C4174F93A51CE970BE
91E2A039DEEAE8451FB8D451ACB3F00E
F10F142D555E2E2FE07EDAF6AEE84B39
570895B7030E33C145E5A35F9AE147BF
<<<<< Identifier Token End >>>>>
So thats all ... My phone stats in bootloader ...
Code:
HBoot - 2.13.0000
Radio - 1.11.50.05.28
Helppp....!

..

This is what i get if i tried to flash RUU zip -
Code:
error: device not found
C:\Users\Useritis\Desktop\WinDroid HTC One S Toolkit>
when clilc X
Code:
...
(bootloader) Device was already locked!
OKAY [ 0.010s]
finished. total time: 0.011s
C:\Users\Useritis\Desktop\WinDroid HTC One S Toolkit>
then ...
goes to HTC black logo ...
Code:
...
(bootloader) Start Verify: 3
OKAY [ 0.083s]
finished. total time: 0.085s
C:\Users\Useritis\Desktop\WinDroid HTC One S Toolkit>
and
Code:
< waiting for device >
error: cannot load 'C:\Users\Useritis\Desktop\New': Unknown error
C:\Users\Useritis\Desktop\WinDroid HTC One S Toolkit>

emilz23 said:
This is what i get .............snipped
Click to expand...
Click to collapse
Geesh, what a mess.
Your main problem is your drivers on your pc, you aren't going to be able to do anything until you get that sorted.
Uninstall them and reinstall them. Restart your pc and go from there.

tivofool said:
Geesh, what a mess.
Your main problem is your drivers on your pc, you aren't going to be able to do anything until you get that sorted.
Uninstall them and reinstall them. Restart your pc and go from there.
Click to expand...
Click to collapse
Will give a shot ... and P.s. there are only one port of USB working ... with phone.
Installed - restart, HTC Driver installer, HTC Sync, Adb Universal drivers, restart ... now trying to see what phone will give
Still the same - no device found.

emilz23 said:
Will give a shot ... and P.s. there are only one port of USB working ... with phone.
Installed - restart, HTC Driver installer, HTC Sync, Adb Universal drivers, restart ... now trying to see what phone will give
Still the same - no device found.
Click to expand...
Click to collapse
I'm no expert, maybe someone here will understand your problem and post
Have you tried the device manager?
Start>right click Computer>Properties>Select Device Manager
You see the device with the question mark by it and click it and have windows automatically install drivers

Yup, im tried really much of things ...
- To install, HTC sync, HTC drivers, ADB drivers
- Reinstall them
- Different PC's (with and without drivers)
- tried orginal USB calbe, and one who came with Nexus7, all the same result.
- And in my PC works only one port with phone, other does not. But with other devices, like flash, all works. There are two 2.0 and one 3.0. Connected to one of 2.0.
- Tried to manually install drivers (allways says their are up to date)
- Unlocking bootloader with my PC dont works (site is loading extreamly slow and then shows white page, after refresh - failed to send code (too long))
- Can unlock with frend PC's
- When I firstly reinstalled drivers, in adb command "adb devices" it showed up, then when tried different commands, like, "adb shell" again the same error. So i cant set SuperCID.
... And so on, with no success.
Cant enable USB Debugging, but previous owner does done - bootloader unlock (so, prehaps, its ticked enable) ... , because have no working android, when i turn on
- now will set full adt bundle with all drivers ... maybe it will work.
P.s. My PC - Dell Inspiron 15R (i5, gt525m, 6gb) and win7 ultimate 64bit.
Pic time!!!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

help plz

deleted ssorry

what your cid number...?
first you must know what your cid number in your phone..to know that..you can typing at fastboot command "fastboot getvar all" or "fastboot getvar cid", after that you must find the right RUU that are suitable with your cid number and had equal or higher build number version than yours..or you can show the output in here..(i will try help you find it the right RUU for your phone) but don't forget to remove your imei and serial number from the list first..to avoid someone that can cloning your phone..
for completed information you can following a guide all about RUU from here..
hope this help..

JJeamy said:
what your cid number...?
first you must know what your cid number in your phone..to know that..you can typing at fastboot command "fastboot getvar all" or "fastboot getvar cid", after that you must find the right RUU that are suitable with your cid number and had equal or higher build number version than yours..or you can show the output in here..(i will try help you find it the right RUU for your phone) but don't forget to remove your imei and serial number from the list first..to avoid someone that can cloning your phone..
for completed information you can following a guide all about RUU from here..
hope this help..
Click to expand...
Click to collapse
CID IS T-MOB1010
C:\Program Files\Android\android-sdk\platform-tools>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.27.0000
(bootloader) version-baseband: N/A
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.32.531.14
(bootloader) serialno: SH165T505068
(bootloader) imei: 355066045054832
(bootloader) product: pyramid
(bootloader) platform: HBOOT-8260
(bootloader) modelid: PG5810000
(bootloader) cidnum: T-MOB010
(bootloader) battery-status: good
(bootloader) battery-voltage: 4203mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: RUU
(bootloader) commitno-bootloader: 617f0a98
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!

SHOULD I GO TO Unlock bootloader

arunkarnwal1981 said:
CID IS T-MOB1010
C:\Program Files\Android\android-sdk\platform-tools>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.27.0000
(bootloader) version-baseband: N/A
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.32.531.14
(bootloader) serialno: SH165T505068
(bootloader) imei: 355066045054832
(bootloader) product: pyramid
(bootloader) platform: HBOOT-8260
(bootloader) modelid: PG5810000
(bootloader) cidnum: T-MOB010
(bootloader) battery-status: good
(bootloader) battery-voltage: 4203mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: RUU
(bootloader) commitno-bootloader: 617f0a98
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
Click to expand...
Click to collapse
i've found your RUU in here...
just running that ruu.exe from pc...while connecting your phone to pc and the phone position in Black background with HTC in middle and four triangle with exclamation mark on all four corners
arunkarnwal1981 said:
SHOULD I GO TO Unlock bootloader
Click to expand...
Click to collapse
if you wanna still using stock rom...you just need flashing the RUU that i give the link above..
but if you wanna rooting and installing custom rom...you must unlock bootloader first via htcdev.com..or else using jupunutbear method to s-off

JJeamy said:
i've found your RUU in here...
just running that ruu.exe from pc...while connecting your phone to pc and the phone position in Black background with HTC in middle and four triangle with exclamation mark on all four corners
if you wanna still using stock rom...you just need flashing the RUU that i give the link above..
but if you wanna rooting and installing custom rom...you must unlock bootloader first via htcdev.com..or else using jupunutbear method to s-off
Click to expand...
Click to collapse
thanks for your quik reply but i was already tried above RUU and it stuck on signature verify fail error.

arunkarnwal1981 said:
thanks for your quik reply but i was already tried above RUU and it stuck on signature verify fail error.
Click to expand...
Click to collapse
you sure that you already tried running that RUU.exe from pc..?, i mean not just flashing it the rom.zip through fastboot

JJeamy said:
you sure that you already tried running that RUU.exe from pc..?, i mean not just flashing it the rom.zip through fastboot
Click to expand...
Click to collapse
yes i tried both exe and zip

arunkarnwal1981 said:
yes i tried both exe and zip
Click to expand...
Click to collapse
what about if you tried it to unlock bootloader via htcdev.com...?
if you already success unlocking bootloader via htcdev.com...you can continued installing 4ext recovery touch..then installing custom that you want..

JJeamy said:
what about if you tried it to unlock bootloader via htcdev.com...?
Click to expand...
Click to collapse
not tried. should i go to unlock it and then RUU. is RUU installable with unlocked boot loader???

JJeamy said:
what about if you tried it to unlock bootloader via htcdev.com...?
if you already success unlocking bootloader via htcdev.com...you can continued installing 4ext recovery touch..then installing custom that you want..
Click to expand...
Click to collapse
but i am S-ON
then how to install custom recovery

arunkarnwal1981 said:
not tried. should i go to unlock it and then RUU. is RUU installable with unlocked boot loader???
Click to expand...
Click to collapse
arunkarnwal1981 said:
but i am S-ON
then how to install custom recovery
Click to expand...
Click to collapse
No...after you success unlocking bootloader...you can't running RUU again..
after unlocking bootloader...you can installing 4ext recovery touch from fastboot..even you're still had s-on
just download and extracted this 4ext recovery touch file from here..
"fastboot flash recovery recovery.img" [note : that "recovery.img" is mean your custom recovery name with *.img extension]

JJeamy said:
No...after you success unlocking bootloader...you can't running RUU again..
after unlocking bootloader...you can installing 4ext recovery touch from fastboot..even you're still had s-on
"fastboot flash recovery recovery.img" [note : that "recovery.img" is mean your custom recovery name with *.img extension]
Click to expand...
Click to collapse
i unlocked boot loader (still phone in RUU mode). installed 4ext recovery (still phone show only RUU screen). so now tell me how to go in recovery as when press vol down+power it directly show mr RUU mode (no bootloader mode), when i remove usb cable it show me hboot screen but there is no option (such as bootloader, fastboot, recovery, crc etc,) , it only show ruu written just below hboot information.
but i am able to use fastboot commands from here.

arunkarnwal1981 said:
i unlocked boot loader (still phone in RUU mode). installed 4ext recovery (still phone show only RUU screen). so now tell me how to go in recovery as when press vol down+power it directly show mr RUU mode (no bootloader mode), when i remove usb cable it show me hboot screen but there is no option (such as bootloader, fastboot, recovery, crc etc,) , it only show ruu written just below hboot information.
but i am able to use fastboot commands from here.
Click to expand...
Click to collapse
yap you must flashing firmware to replace corrupt bootloader first..
that's mean now your bootloader had a text "UNLOCKED" in the top of bootloader..?
if the bootloader had already text "unlocked" in the top of bootloader..?, you must relocked first with command "fastboot oem lock", then tried it flashing this firmware from bootloader..

JJeamy said:
yap you must flashing firmware to replace corrupt bootloader first..
that's mean now your bootloader had a text "UNLOCKED" in the top of bootloader..?
if the bootloader had already text "unlocked" in the top of bootloader..?, you must relocked first with command "fastboot oem lock", then tried it flashing this firmware from bootloader..
Click to expand...
Click to collapse
yes it show me unlocked
but from where i can get firmware???

JJeamy said:
yap you must flashing firmware to replace corrupt bootloader first..
that's mean now your bootloader had a text "UNLOCKED" in the top of bootloader..?
if the bootloader had already text "unlocked" in the top of bootloader..?, you must relocked first with command "fastboot oem lock", then tried it flashing this firmware from bootloader..
Click to expand...
Click to collapse
after re locking bootloader and flashing suggested firmware it give me following error
C:\Program Files\Android\android-sdk\platform-tools>fastboot flash zip C:\Users\
Microbiology\Downloads\Compressed\firmware.zip
sending 'zip' (23769 KB)...
OKAY [ 4.254s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 8.602s

arunkarnwal1981 said:
after re locking bootloader and flashing suggested firmware it give me following error
C:\Program Files\Android\android-sdk\platform-tools>fastboot flash zip C:\Users\
Microbiology\Downloads\Compressed\firmware.zip
sending 'zip' (23769 KB)...
OKAY [ 4.254s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 8.602s
Click to expand...
Click to collapse
what about if you tried installing RUU again...?, because just only this way can fix your bootloader.. just don't forget to relock your boorloader first before that..
because your bootloader is already corrupt..that's why can't show all bootloader menu..
EDITED: IF RUU still fail...maybe you can tried flash this firmware (this TMOUS firmware) through bootloader...just copied this firmware file (PG58IMG.zip) to the root of your sdcard (root sdcard is mean don't placed in any folder on your sdcard..just outside them)..and boot to bootloader..then let bootloader check it..then wait to confirm updating with pressing vol up...wait until finish..confirm reboot with power button..

JJeamy said:
what about if you tried installing RUU again...?, because just only this way can fix your bootloader.. just don't forget to relock your boorloader first before that..
because your bootloader is already corrupt..that's why can't show all bootloader menu..
Click to expand...
Click to collapse
RUU not working again same error

arunkarnwal1981 said:
RUU not working again same error
Click to expand...
Click to collapse
the last hope just tried this :
IF RUU still fail...maybe you can tried flash this firmware (this TMOUS firmware) through bootloader...just copied this firmware file (PG58IMG.zip) to the root of your sdcard (root sdcard is mean don't placed in any folder on your sdcard..just outside them)..and boot to bootloader..then let bootloader check it..then wait to confirm updating with pressing vol up...wait until finish..confirm reboot with power button..
and if still fail...try flashing it with different way...like through fastboot flash zip rom.zip
hope this help..

JJeamy said:
the last hope just tried this :
IF RUU still fail...maybe you can tried flash this firmware (this TMOUS firmware) through bootloader...just copied this firmware file (PG58IMG.zip) to the root of your sdcard (root sdcard is mean don't placed in any folder on your sdcard..just outside them)..and boot to bootloader..then let bootloader check it..then wait to confirm updating with pressing vol up...wait until finish..confirm reboot with power button..
hope this help..
Click to expand...
Click to collapse
it dose not show me bootloader screen then how i install this??

Stuck while flashing RUU [HTC logo with 4 triangles in corner]

Hello ,
Today I want test new rom but I get error in TWRP recovery can't mount system cache data I tried other recovery (4ext) same problem , wipe data system .... not succeed
I tried to flush a RUU (I flush this RUU version always in my phone with succeed ) after relock bootload S-ON I stuck in 39% I think it's stop in dzdata
know my phone stuck in black screen and HTC logo with 4 triangles in corner
Hboot just have RUU in yellow
Code:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.27.0000
(bootloader) version-baseband: N/A
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.33.401.53
(bootloader) product: pyramid
(bootloader) platform: HBOOT-8260
(bootloader) modelid: PG5813000
(bootloader) cidnum: HTC__304
(bootloader) battery-status: good
(bootloader) battery-voltage: 3781mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: RUU
(bootloader) hbootpreupdate: 11
Thank for help .

popo020 said:
Hello ,
Today I want test new rom but I get error in TWRP recovery can't mount system cache data I tried other recovery (4ext) same problem , wipe data system .... not succeed
I tried to flush a RUU (I flush this RUU version always in my phone with succeed ) after relock bootload S-ON I stuck in 39% I think it's stop in dzdata
know my phone stuck in black screen and HTC logo with 4 triangles in corner
Hboot just have RUU in yellow
Code:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.27.0000
(bootloader) version-baseband: N/A
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.33.401.53
(bootloader) product: pyramid
(bootloader) platform: HBOOT-8260
(bootloader) modelid: PG5813000
(bootloader) cidnum: HTC__304
(bootloader) battery-status: good
(bootloader) battery-voltage: 3781mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: RUU
(bootloader) hbootpreupdate: 11
Thank for help .
Click to expand...
Click to collapse
look here
http://forum.xda-developers.com/htc-sensation/help/recovering-data-mount-issues-t2859588

Thank you for reply
but I have different problem in Hboot I don't have any option like fastboot/recovery/rest ...
I have only RUU with yellow color like in this image
i1160.photo bucket.com/albums/q492/arjaycabling/bcefc324-8e37-45be-b07d-a75c1b164a73_zpsac8ba21f.jpg
please help

popo020 said:
Thank you for reply
but I have different problem in Hboot I don't have any option like fastboot/recovery/rest ...
I have only RUU with yellow color like in this image
i1160.photo bucket.com/albums/q492/arjaycabling/bcefc324-8e37-45be-b07d-a75c1b164a73_zpsac8ba21f.jpg
please help
Click to expand...
Click to collapse
post it again
i can't see it
but i think you have stuck in ruu mode

This what I have in my HBOOT
=================================
*** RELOCKED ***
PYRAMID PVT SHIP S-ON RL
HBOOT-1.27.0000
RADIO-11.24A.3504.31_M
OpenADSP-v05.6.0.2226.00.0418
eMMC-boot
Jan 13 2012,17:33:34
RUU
=================================
like in this picture
#remove space from link
Code:
i1160.photo bucket.com/albums/q492/arjaycabling/bcefc324-8e37-45be-b07d-a75c1b164a73_zpsac8ba21f.jpg

If I want flash anything by fastboot i get
Code:
FAILED (remote: 12 signature verify fail)

popo020 said:
If I want flash anything by fastboot i get
Code:
FAILED (remote: 12 signature verify fail)
Click to expand...
Click to collapse
since you are relocked you are limited to fastboot commands
try this one
fastboot reboot bootloader
edit: by the way did you use any wipe option from TWRP ?

rzr86 said:
since you are relocked you are limited to fastboot commands
try this one
fastboot reboot bootloader
edit: by the way did you use any wipe option from TWRP ?
Click to expand...
Click to collapse
yep this is it start with this problem I use wipe from TWRP but didn't work so I decide go back to stock RUU and have this problem
Code:
fastboot reboot bootloader
back to same black screen with htc logo and 4 triangle

popo020 said:
yep this is it start with this problem I use wipe from TWRP but didn't work so I decide go back to stock RUU and have this problem
Code:
fastboot reboot bootloader
back to same black screen with htc logo and 4 triangle
Click to expand...
Click to collapse
you shouldn't use any wipe option from twrp
your system and data partitoin are corrupted probably
also you are stuck in ruu mode
try to flash the ruu manually
see how it goes
otherwise your only option is the thread i gave you in my previous post

Thank you again
but Bootloader can't find PG58IMG.zip in my SD card how can I flash the RUU manually
phone stuck in 39% when start system flashing

popo020 said:
Thank you again
but Bootloader can't find PG58IMG.zip in my SD card how can I flash the RUU manually
phone stuck in 39% when start system flashing
Click to expand...
Click to collapse
try with fastboot flash zip pg58img.zip

rzr86 said:
try with fastboot flash zip pg58img.zip
Click to expand...
Click to collapse
I got this error :crying:
Code:
FAILED (remote: 12 signature verify fail)

any help bro ?

At first you said you have relocked your bootloader in order to flash the RUU.You have not S-OFF so you are forbidden to use the recovery right now and probably you are stuck in RUU mode.
As long as you have "relocked" status you could unlock your bootloader again by using the command
Code:
fastboot oem unlock
or by flashing the Unlock_code.bin again
Code:
fastboot flash unlocktoken Unlock_code.bin
After those steps you should have access to bootloader again and you should be able to use recovery to correct (the possibly corrupted) partitions by using the guide that gave you rzr86.
http://forum.xda-developers.com/htc-sensation/help/recovering-data-mount-issues-t2859588
It's a painful proccess but it is the only solution I can think right now.
---------- Post added at 03:53 AM ---------- Previous post was at 03:35 AM ----------
You could also check this guide out how to reformat a partition from recovery.(This guide is for HTC One and the /data partition number is probably not the same with the sensation /data partition number but I think it's a good start to read this solution)
---------- Post added at 04:06 AM ---------- Previous post was at 03:53 AM ----------
If you have access to recovery you can use adb shell to give the command
Code:
cat /proc/emmc
so you can see the numbers for every partition in your device.
You can also check this guide out.

for
Code:
fastboot oem unlock
give me this error
Code:
(bootloader) [ERR] Command error !!!
OKAY [ 0.018s]
finished. total time: 0.019s
and for
Code:
fastboot flash unlocktoken Unlock_code.bin
pass successfully but nothing happen to screen I don't have any room in phone to unlock it
and adb commands don't work fastboot only work

popo020 said:
for
Code:
fastboot oem unlock
give me this error
Code:
(bootloader) [ERR] Command error !!!
OKAY [ 0.018s]
finished. total time: 0.019s
and for
Code:
fastboot flash unlocktoken Unlock_code.bin
pass successfully but nothing happen to screen I don't have any room in phone to unlock it
and adb commands don't work fastboot only work
Click to expand...
Click to collapse
The first command doesn't always work but the unlocktoken should unlock your bootloader again.
If you use the command
Code:
fastboot reboot bootloader
after the flash of unlocktoken you should be able to see the bootloader on the next reboot.(If you can't just try to remove the battery for some time ,put it back in and press (power) + (vol-) to get the phone in bootloader mode.
Adb commands doesn't work on fastboot or RUU modes.You can only use adb by using a recovery with that capability or with a working rom.
Anyway...If nothing of them can help you you could try (by relocking your bootloader at first) to flash an extracted system.img from an RUU by using fastboot
Code:
fastboot flash system system.img
You should better try to erase data and cache partitions before you reboot and see if you have a working ROM.
Code:
fastboot erase userdata
fastboot erase cache
fastboot reboot

Thank you for reply , I have only the tow screens displayed exactly like the image
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
And [VOL -] +[ POWER BUT ] give the black screen
I think unlocktoken need ROM installed for choosing between unlock or not
and all flash commands failed
Code:
FAILED (remote: 12 signature verify fail)
:crying:

popo020 said:
for
Code:
fastboot oem unlock
give me this error
Code:
(bootloader) [ERR] Command error !!!
OKAY [ 0.018s]
finished. total time: 0.019s
and for
Code:
fastboot flash unlocktoken Unlock_code.bin
pass successfully but nothing happen to screen I don't have any room in phone to unlock it
and adb commands don't work fastboot only work
Click to expand...
Click to collapse
popo020 said:
Thank you for reply , I have only the tow screens displayed exactly like the image
And [VOL -] +[ POWER BUT ] give the black screen
I think unlocktoken need ROM installed for choosing between unlock or not
and all flash commands failed
Code:
FAILED (remote: 12 signature verify fail)
:crying:
Click to expand...
Click to collapse
As I saw in your first post here you are saying you have hboot 1.27 (probably from a command you gave in RUU mode)
Code:
fastboot getvar all
Now as I can see in the image your bootloader status seems to be 0.85 for the model ACE (HTC DESIRE HD).If this is an enginering HBOOT and you reverted to S-ON you probably breaked your device.I just don't get it!
HTC Desire HD HBOOT
HTC Sensation HBOOT
The sensation phones are PYRAMID models!
If it has to do with wrong flash you could try this guide.
But before you try anything give the command
Code:
fastboot getvar all
one more time and copy-paste everything here.

the image not from my phone I found it in the net , just to show you what look like
This what I have in my HBOOT
=================================
*** RELOCKED ***
PYRAMID PVT SHIP S-ON RL
HBOOT-1.27.0000
RADIO-11.24A.3504.31_M
OpenADSP-v05.6.0.2226.00.0418
eMMC-boot
Jan 13 2012,17:33:34
RUU
=================================
and getVar All
Code:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.27.0000
(bootloader) version-baseband: 11.24A.3504.31_M
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.33.401.53
(bootloader) product: pyramid
(bootloader) platform: HBOOT-8260
(bootloader) modelid: PG5813000
(bootloader) cidnum: HTC__304
(bootloader) battery-status: good
(bootloader) battery-voltage: 3930mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: RUU
(bootloader) commitno-bootloader: 617f0a98
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0

If you cannot unlock your device from relocked status and you cannot flash anything to it I don't think I can help you further.You can always use varius tools like riffbox to repartition emmc chip or maybe to s-off your device (Too).
Are you apsolutely sure you tried to flash a signed system.img with relocked bootloader and it didn't flash??