Related
Hi please could somebody help me, I have a Desire S which I got on contract from 02 with a 02 branded rom on there originally and hboot 0.98.0002.
I had S-off, 4ext recovery, upgraded to hboot 2.00.0002 and a custom rom installed.
I have flashed a offical RUU RUU_Saga_O2_UK_1.31.206.1_Radio_20.28b.30.0805U_38.03.02.14_M_release_178935_signed.exe
and now I am stuck in hboot and it says **security warning** hboot version 0.98.000
I tried to flash the above o2 RUU again but it says bootloader version error, So I tried RUU 1.28, 1.47 and 2.10 with a gold card in the phone but the same error all the time.
I have also extracted the rom.zip from each of these and put it onto the goldcard renamed to PG88IMG.zip but then this says MAIN VERSION OLDER and will not flash.
Now I am really stuck on what I need to do, do I need to flash a 0.98.0002 hboot? as at the momment I have 0.98.000, if so how can I do this?
I have lost 4ext recovery, and back to S-On.
If anyone has any ideas I would be really grateful.
Thank you in advance
Cheers
edit: I think the bootloader I currently have on the phone 0.98.000 is incorrect ? , it should be 0.98.0000 or 0.98.0002? . As the hboot is S-ON is there anyway I can flash a hboot through using adb, or does it have to be S-OFF, if so is there anyway I can S-OFF in bootloader or fastboot alone, as I can't do anything else.
I think that the O2 RUU that you have used has an older hboot version (0.98.0000) than the version that was on your phone when you s-offed.
But with the Goldcard you should be able to flash it. So try another SDcard to create a goldcard, as far as I know not each one is suitable.
Do not try RUU for other brands/regions you may end up with a bricked device.
amidabuddha said:
I think that the O2 RUU that you have used has an older hboot version (0.98.0000) than the version that was on your phone when you s-offed.
But with the Goldcard you should be able to flash it. So try another SDcard to create a goldcard, as far as I know not each one is suitable.
Do not try RUU for other brands/regions you may end up with a bricked device.
Click to expand...
Click to collapse
Hi thanks for your reply, I currently have 0.98.000 hboot on the phone now which is S-ON. My gold card seems to be working as it doesn't say any CID errors.
How can I tell if my device is bricked?
I can only get into hboot, and fastboot/stock recovery. The phone won't do anything else and I can't flash any rom as it says about the bootloader version, but on the bootloader it says **security warning** at the top. Is there anyway I can flash a newer hboot? or won't it let me as it is S-ON, if its S-ON will I be able to flash a hboot or even 4ext recovery to flash a rom?
If so how can I s-off just using bootloader and fastboot?
I thought goldcard is only to bypass the CID checks so you can flash a debranded RUU.
It is not exactly clear: have you tried to extract the rom.zip from the O2 RUU, rename to PG88IMG.zip and flash in hboot?
Also you have to be completely sure that your version is the O2 one.
Follow the guide in my signature to make fastboot working on your PC.
Then connect your device to the PC while in the hboot. There should be 'FASTBOOT USB' written on the phone screen.
Then open a command prompt on your PC and type:
Code:
fastboot devices {your serial number should appear}
fastboot getvar all
Post here the output that is printed in the cmd.
amidabuddha said:
It is not exactly clear: have you tried to extract the rom.zip from the O2 RUU, rename to PG88IMG.zip and flash in hboot?
Also you have to be completely sure that your version is the O2 one.
Follow the guide in my signature to make fastboot working on your PC.
Then connect your device to the PC while in the hboot. There should be 'FASTBOOT USB' written on the phone screen.
Then open a command prompt on your PC and type:
Code:
fastboot devices {your serial number should appear}
fastboot getvar all
Post here the output that is printed in the cmd.
Click to expand...
Click to collapse
Hi, I have done the fastboot commands you said and below are the numbers I got:
fastboot devices - serial number which came up is: HT15NTJ00403
fastboot getvar version-main: 11.10.401.4
Can you help me?
Do you think my phone is bricked?
Thank you for your help with this
Try to put last rom.zip on sdcard with PG88IMG.zip name from version 2.10.401.8 RUU and maybe you will have new hboot 2.00.2002 and then have to unlock hboot from http://htcdev.com/.
first_damned said:
fastboot getvar version-main: 11.10.401.4
Can you help me?
Do you think my phone is bricked?
Click to expand...
Click to collapse
Cannot tell that it's bricked but now your software version is 2.10.401.4.
So you have to use a European RUU with the same version or higher. Probably you have debranded your device without an intention to do so.
Try with the RUU. If this is not working maybe you can try to flash hboot through the fastboot.
amidabuddha said:
Cannot tell that it's bricked but now your software version is 2.10.401.4.
So you have to use a European RUU with the same version or higher. Probably you have debranded your device without an intention to do so.
Try with the RUU. If this is not working maybe you can try to flash hboot through the fastboot.
Click to expand...
Click to collapse
Hi, I have tried RUU_Saga_S_HTC_Europe_2.10.401.8_Radio_20.4801.30. 0822U_3822.10.08.04_M_release_225161_signed.exe using the RUU on the laptop and tried extracting the rom.zip, renaming as PG88IMG.zip and flashing off sd card (goldcard), but the RUU said bootloader version error and flashing the PG88IMG.zip says main version older error.
There isn't a 2.10.401.4 version, but there is a
RUU_Saga_S_HTC_Europe_2.10.401.5_Radio_20.4801.30. 0822U_3822.10.08.04_M_release_219480_signed.exe
I would of thought the 2.10.401.8 should of worked?
also would I be able to flash a hboot being S-ON do you think?
I'm not sure how low my battery is also, If I plug it into the charger will it charge the phone on the bootloader do you know?
Thanks
All version info
INFOversion: 0.5
INFOversion-bootloader: 0.98.0000
INFOversion-baseband: 38.03.02.14_M
INFOversion-cpld: None
INFOversion-microp: None
INFOversion-main: 11.10.401.4
INFOserialno: HT15NTJ00403
INFOimei: 356708041449842
INFOproduct: saga
INFOplatform: HBOOT-7230
INFOmodelid: PG8810000
INFOcidnum: O2___001
INFObattery-status: good
INFObattery-voltage: 3851mV
INFOpartition-layout: Generic
INFOsecurity: on
INFObuild-mode: SHIP
INFOboot-mode: FASTBOOT
INFOcommitno-bootloader: 361a7ba6
INFOhbootpreupdate: 12
INFOgencheckpt: 0
all: Done!
Ok so we have a nice mess here.
Your hboot and radio are still from the O2 RUU, but the main version changed to the European one. The cid is still O2 one (but with the goldcard it should not matter).
The security warning gives a chance that you are still able to have root.
So if you can enter the recovery you may be able to use adb as root.
Do the procedure, described here
If you can get the misc.img, after opening with Hex editor change the numbers to 1.31.206.1. Save the file, copy it to you SDcard and from adb flash it back:
Code:
dd if=/sdcard/misc.img of=/dev/block/mmcblk0p17
Then try the O2 RUU again.
Do not make attempts to change the hboot yet. Try the above and post back
The phone should be charging when you connect it to your PC.
amidabuddha said:
Ok so we have a nice mess here.
Your hboot and radio are still from the O2 RUU, but the main version changed to the European one. The cid is still O2 one (but with the goldcard it should not matter).
The security warning gives a chance that you are still able to have root.
So if you can enter the recovery you may be able to use adb as root.
Do the procedure, described here
If you can get the misc.img, after opening with Hex editor change the numbers to 1.31.206.1. Save the file, copy it to you SDcard and from adb flash it back:
Code:
dd if=/sdcard/misc.img of=/dev/block/mmcblk0p17
Then try the O2 RUU again.
Do not make attempts to change the hboot yet. Try the above and post back
The phone should be charging when you connect it to your PC.
Click to expand...
Click to collapse
Hi there, I have tried adb devices but it doesn't come up with my device which is strange. Maybe because my device is S-ON?
Do you think if I took it to a mobile repair shop and had it jtagged to restore original software would do the trick?
thanks
Both adb and fastboot commands are working on S-ON devices.
To use adb your device should be in Recovery mode (you can enter there from the hboot menu).
Of course you can bring it to a repair shop if you do not want to mess it yourself.
amidabuddha said:
Both adb and fastboot commands are working on S-ON devices.
To use adb your device should be in Recovery mode (you can enter there from the hboot menu).
Of course you can bring it to a repair shop if you do not want to mess it yourself.
Click to expand...
Click to collapse
Hi, I have entered recovery mode but thats where it says **security warning** at the top of the screen in pink. I have tried adb devices in cmd prompt but it says list of devices but nothing is listed. any idea why this is?
first_damned said:
Hi, I have entered recovery mode but thats where it says **security warning** at the top of the screen in pink. I have tried adb devices in cmd prompt but it says list of devices but nothing is listed. any idea why this is?
Click to expand...
Click to collapse
Obviously adb is not working in Recovery on S-ON devices. Sorry for misleading. I have just tried on my device, the adb works while booted to OS but not in Recovery.
I am afraid that doing anything further can brick the phone completely and the repair shop is your best option.
amidabuddha said:
Obviously adb is not working in Recovery on S-ON devices. Sorry for misleading. I have just tried on my device, the adb works while booted to OS but not in Recovery.
I am afraid that doing anything further can brick the phone completely and the repair shop is your best option.
Click to expand...
Click to collapse
I can't get adb to see the device, fastboot will do though but won't flash hboot, it says remote signature fail.
Looks like im going to have to send the phone off to be J Tagged. I have found a shop that does this for £24.99 and they know there stuff.
But if anyone has anymore ideas please let me know.
Thank you amidabuddha for your help, I will keep you updated on any progress.
Simon
You can repair it in HTC services or S-OFF again by Xtc-clip (as my HTC before).
Sent from my Desire S using xda premium
poppy8x said:
You can repair it in HTC services or S-OFF again by Xtc-clip (as my HTC before).
Sent from my Desire S using xda premium
Click to expand...
Click to collapse
Did the problem I have happen to you in the past also with the **security warning** ?
If so what did you do after s-off?
first_damned said:
Did the problem I have happen to you in the past also with the **security warning** ?
If so what did you do after s-off?
Click to expand...
Click to collapse
Yup, u can S-OFF your DS again by xtc-clip and then "security warning" is gone. But affter s-off by xtc-clip, u can't S-ON it. U can use custom rom only.
Sent from my HTC Desire S using xda premium
poppy8x said:
Yup, u can S-OFF your DS again by xtc-clip and then "security warning" is gone. But affter s-off by xtc-clip, u can't S-ON it. U can use custom rom only.
Sent from my HTC Desire S using xda premium
Click to expand...
Click to collapse
Sounds promising )
So did you s-off with xtc clip, then flash hboot to newer version, flash recovery (4ext or clockworkmod) and then flash a custom rom and all worked?
first_damned said:
Sounds promising )
So did you s-off with xtc clip, then flash hboot to newer version, flash recovery (4ext or clockworkmod) and then flash a custom rom and all worked?
Click to expand...
Click to collapse
Yeah. All worked. Look at my sig.
A month ago, i had "sercurity warning" too (i run RUU 1.48). Gold card coudn't do anything. And then i s-off by xtc-clip (in 5 mins)
Sry for my english bad.
Sent from my HTC Desire S using xda premium
hi, i had the problem that my htc sensation xe wasnt working because it was stuck at the htc bootscreen, so i had the idea to use my backup that was made until i rooted the phone. it was an backup made by the adb commands (.. adb pull / \AndroidBackup). so will it work if i would push this backup back on my phone? (.. adb push C:\AndroidBackup / ) and what do i have to do to get it working again because the fastboot commands are working unproblematic as the phone is in the fastboot menu but if it is in the hboot menu and i try to use adb commands it isnt working anyway. (".. fastboot devices" is working so the phone is recognized but ".. adb devices" doesnt show my phne) i have already tried to reinstall the adb driver but that hasnt changed anything. the device manager of my pc tells me the drivers etc. are working smoothly and i shows the phone as adb device so the driver is installed correctly... my phone is almost bircked, i know how i can solve it and now its a problem of my f******* computer. i hope you can help me to get my phone recognized by the adb commands. thanks
some information: hboot 1.18.0000; adb drivers version 2.0.10.2; hboot says:
*** UNLOCKED ***
PYRAMID PVT SHIP S-ON RL
eMMC-boot
Aug 2... (it is unlocked by htcdev.com)
same problem here!!!
i am not able to do anything.
it happened with me, when i was trying to use the cam of the phone, but wasn't working...
i restarted my phone and all of a sudden it started bootlooping all the time,
was able to unlock the bootloader.
but the phone kept restarting and wasn't able to do anything afterwards...
Reboot to bootloader.
Go to recovery.
ADB is functional and you can use the commands.
EDIT: Are you using/trying to use a custom ROM?
If so, which one?
kgs1992 said:
Reboot to bootloader.
Go to recovery.
ADB is functional and you can use the commands.
Click to expand...
Click to collapse
if i press recovery in the fastboot menu, phones do restarts again
lZooZl said:
if i press recovery in the fastboot menu, phones do restarts again
Click to expand...
Click to collapse
You Hboot version and status? Also, S ON or S Off?
Are you using/ trying to use a custom ROM?
UNLOCKED
S-ON
HBOOT: 1.27
will use the same rom but add root and recovery to it
lZooZl said:
UNLOCKED
S-ON
HBOOT: 1.27
will use the same rom but add root and recovery to it
Click to expand...
Click to collapse
Have you installed the right firmware?
Follow steps 3 & 4 from here.
The link in the guide for firmware is dead. Here is the working link.
it is parsing the file
but then nothing happens!!
lZooZl said:
it is parsing the file
but then nothing happens!!
Click to expand...
Click to collapse
Step 3 from here to get correct firmware.
Not working too
lZooZl said:
Not working too
Click to expand...
Click to collapse
What is your cid? If you don't know, go to the ruu guide in my signature, there are steps to find cid under point 2.1.
Sent from my HTC Sensation XE with beats audio
Cid: Htc__j15
mid: Pg5813001
lZooZl said:
Cid: Htc__j15
mid: Pg5813001
Click to expand...
Click to collapse
Try flashing 4ext recovery.
The first guide that I linked you to should help. After flashing the recovery, format all partitions except SD card and then install the Rom.
Sent from my HTC Sensation XE with beats audio
excuse my ignorance at the moment (been reading all day long)
but how am i supposed to flash a 4ext recovery if it is not taking any ADB command?
lZooZl said:
excuse my ignorance at the moment (been reading all day long)
but how am i supposed to flash a 4ext recovery if it is not taking any ADB command?
Click to expand...
Click to collapse
It's very weird that nothing works and even PG58IMG can't be flashed.
JB Soff is your only option now.
inserted my CID
but it is still stuck on the parsing, and getting back to HBOOT
lZooZl said:
inserted my CID
but it is still stuck on the parsing, and getting back to HBOOT
Click to expand...
Click to collapse
Are you sure you are HTC Dev Unlocked?
the thing is i unlocked the phone after i have my BootLoop issue!!
lZooZl said:
the thing is i unlocked the phone after i have my BootLoop issue!!
Click to expand...
Click to collapse
I can only suggest JB S Off right now. It's very weird that an unlocked phone doesn't flash PG58IMG.zip
i was able to flash recovery through method two!
but when restarting, it continued the boot loop!!!
I'm stuck in a bootloop / soft brick and would like to go back to stock rom / RUU
Phone is: HTC One S - UK - Vodafone
I'm tried using:
RUU_Ville_U_Vodafone_UK_1.78.161.2_Radio_0.16.31501S.17_2_10.23.31501S.10L_release_258386_signed
RUU_Ville_U_Vodafone_UK_1.53.161.3_Radio_0.15.31501S.19_2_10.13.31501S.06L_release_251482_signed
RUU_Ville_U_ICS_40_S_HTC_Europe_2.31.401.5_Radio_1.06es.50.02.31_10.09a.50.04L_release_275655_signed
Always getting the same error message:
ERROR(155): UNKNOWN ERROR
The ROM Update Utility cannot update your Androidphone
Please get the correct ROM Update Utiility and try again
Pretty obvious what I should do
But cant seem to be able to locate the correct RUU file
Any idea?
Many thanks
Cedric
What is your current software version?
You can change your CID to HTC__001 and then flash unbranded 2.31 (the one you already have)
Did you relock your bootloader?
Sent from my HTC One S using xda premium
Yes I did, Thank you
mikeyinid said:
Did you relock your bootloader?
Sent from my HTC One S using xda premium
Click to expand...
Click to collapse
cid: VODAP001
Could you pleaase confirm how to change my CID?
Tried fastboot oem writecid HTC__001 and that blocked bootloader...
Thank you!
Error message
C:\fastboot oem writecid HTC__001
...
(bootloader) ville_init_sd, SD card already power on
(bootloader) sdhw_7xxx_open: id=0
(bootloader) [SD_HW_ERR] SD: No device attached
(bootloader) 902910 902E20
FAILED (status read failed (Too many links))
finished. total time: 1.271s
Since I posted this morning
I also tried to change CID via adb shell but it doesnt work - error message = error: device not found
And I allowed USB debugging + fastboot recognise USB connection
Any idea? really lost now!!
Thank you very much
usaff22 said:
What is your current software version?
You can change your CID to HTC__001 and then flash unbranded 2.31 (the one you already have)
Click to expand...
Click to collapse
Any luck? Haven't any progress...
Many thanks
cplessier said:
Any luck? Haven't any progress...
Many thanks
Click to expand...
Click to collapse
I had a similar problem with my orange branded one s but got it up and running by doing the following :
unlock bootloader
install twrp recovery
boot into recovery (must be in recovery not bootloader or adb shell will not work)
change orange cid to generic cid http://forum.xda-developers.com/showthread.php?p=26516911#post26516911
flash stock recovery
relock bootloader
install latest european ruu
Hope this helps
I managed to change the CID to Super CID
But still getting Error 155 when trying to install RUU
Any other idea?
Many thanks
cplessier said:
I managed to change the CID to Super CID
But still getting Error 155 when trying to install RUU
Any other idea?
Many thanks
Click to expand...
Click to collapse
If your sure the cid was sucessfully changed (i used HTC_001) and you flashed stock recovery then relocked bootloader im all out of ideas. thats what worked for me.
cplessier said:
I managed to change the CID to Super CID
But still getting Error 155 when trying to install RUU
Any other idea?
Many thanks
Click to expand...
Click to collapse
What is error 155?
usaff22 said:
What is error 155?
Click to expand...
Click to collapse
Error 155 gets when either your bootloader is locked or u r using the wrong RUU
If you updated to jelly bean , sense 4+ and then rooted your ONE S and then installed other roms like CM10, etc, you will get error 155 if you try to use any RUU. Thats because your hboot is updated when upgrading to sense 4+,JB.
Thus to revert back to stock....
1. get stock ICS Sense 4.1 ROM,
2. flash stock recovery.
3. Use OTA update to jelly bean,Sense 4+.
4. Factory reset your phone to remove any non-stock stuff from the ROM.
5. you have STOCK Sense 4+!!
6. then if you want you can relock boot loader .( but I havent tried it, might cause problem)
Your hboot won't be updated unless it's a ota or a ruu am I right eg I was on 4.04 then rooted and installed trickdroid but I am still on the hboot that came with 4.04 ruu.
Sent from my HTC One S using xda premium
Same problem: Error 155: Unknown Error
I'm on Vodafone IE.
Successfully changed CID to HTC__001, restored stock, relocked bootloader and I can't install any RUU, tried
RUU_Ville_U_HTC_Europe_1.78.401.2_Radio_0.16.31501S.17_2_10.23.31501S.10L_release_258480_signed
RUU_Ville_U_ICS_40_S_HTC_Europe_2.21.401.10_Radio_1.06s.50.02.27_2_10.08.50.04L__release_271119_signed
Any ideas?
OK
managed to update with
RUU_Ville_U_JB_45_S_HTC_Europe_3.16.401.8_Radio_1.11.50.05.28_10.27.50.08L_release_301814_signed_2_4
cplessier said:
I'm stuck in a bootloop / soft brick and would like to go back to stock rom / RUU
Phone is: HTC One S - UK - Vodafone
I'm tried using:
RUU_Ville_U_Vodafone_UK_1.78.161.2_Radio_0.16.31501S.17_2_10.23.31501S.10L_release_258386_signed
RUU_Ville_U_Vodafone_UK_1.53.161.3_Radio_0.15.31501S.19_2_10.13.31501S.06L_release_251482_signed
RUU_Ville_U_ICS_40_S_HTC_Europe_2.31.401.5_Radio_1.06es.50.02.31_10.09a.50.04L_release_275655_signed
Always getting the same error message:
ERROR(155): UNKNOWN ERROR
The ROM Update Utility cannot update your Androidphone
Please get the correct ROM Update Utiility and try again
Pretty obvious what I should do
But cant seem to be able to locate the correct RUU file
Any idea?
Many thanks
Cedric
Click to expand...
Click to collapse
Wipe everything.Should be able to flash CyanogenMod 10. After that, change back the CID to VODAP001 (mmcblk0p4 and build.prop).
My phone, HTC Sensation XE, is S-ON, on default ROM, and has HBOOT 1.29.000. Needless to say, my phone is not rooted.
The phone is on a boot loop ever since I last took off the battery and placed it back. I sometimes get a message that my Android system is getting upgraded, terminating with an error "System UI has stopped working" before the phone restarts itself again.
I don't know if this is a hardware issue or software.
How do I get my phone to a normal state? I don't mind rooting the phone if I need to for the purpose of installing default/custom ROM. But I don't know if this would be possible because I only have access to boot screen at present.
Please suggest me suitable solutions. Thank you
jiteshgawali said:
My phone, HTC Sensation XE, is S-ON, on default ROM, and has HBOOT 1.29.000. Needless to say, my phone is not rooted.
The phone is on a boot loop ever since I last took off the battery and placed it back. I sometimes get a message that my Android system is getting upgraded, terminating with an error "System UI has stopped working" before the phone restarts itself again.
I don't know if this is a hardware issue or software.
How do I get my phone to a normal state? I don't mind rooting the phone if I need to for the purpose of installing default/custom ROM. But I don't know if this would be possible because I only have access to boot screen at present.
Please suggest me suitable solutions. Thank you
Click to expand...
Click to collapse
if you are completely stock then i think you only option is to use a ruu.exe
http://forum.xda-developers.com/showthread.php?t=1672425
find the one which corresponds with your region and cid
rzr86 said:
if you are completely stock then i think you only option is to use a ruu.exe
http://forum.xda-developers.com/showthread.php?t=1672425
find the one which corresponds with your region and cid
Click to expand...
Click to collapse
Thanks rzr86
I looked into the thread you suggested. For my region and CID, I was not able to get the RUU from the thread. What I could get was this - an OTA zip file that matches my software version exactly (3.33.720.106) from this thread: http://forum.xda-developers.com/showthread.php?t=1764025
How do I proceed further with this zip file, since I don't have an executable RUU file?
I am hoping you can be of help -)
(The zip file contains -- META-INF, patch, system, firmware.zip, fotaBoot, version.txt)
Get s off
Install custom recovery(4ext)
and flash any ics / jelly bean custom Rom
Itsakash said:
Get s off
Install custom recovery(4ext)
and flash any ics / jelly bean custom Rom
Click to expand...
Click to collapse
I was of the same opinion itsakash, but I am not sure if I can SOFF from the bootloader screen because I have only that option available with me. Can you please refer to me a good guide on this forum where I can SOFF from bootloader?
jiteshgawali said:
I was of the same opinion itsakash, but I am not sure if I can SOFF from the bootloader screen because I have only that option available with me. Can you please refer to me a good guide on this forum where I can SOFF from bootloader?
Click to expand...
Click to collapse
Yes u can s off from bootloader
Use KGS utility or ganeshp one click root. ,s off method Check general section in sensation forum
Connect mobile to pc on bootloader screen( mobile should say fastboot USB )
And follow instruction carefully
:thumbup:
Itsakash said:
Yes u can s off from bootloader
Use KGS utility or ganeshp one click root. ,s off method Check general section in sensation forum
Connect mobile to pc on bootloader screen( mobile should say fastboot USB )
And follow instruction carefully
:thumbup:
Click to expand...
Click to collapse
When I try and do SOFF using KGS utility, it restarts my phone because my phone is not HTC dev unlocked. (My phone's motherboard was replaced some time ago, and so I cannot unlock my phone.)
ganeshp's one click root requires SOFF. I can't SOFF using his technique because temp_root.bat doesn't work in bootloader screen.
I am in trouble, and don't look like getting out of it
jiteshgawali said:
When I try and do SOFF using KGS utility, it restarts my phone because my phone is not HTC dev unlocked. (My phone's motherboard was replaced some time ago, and so I cannot unlock my phone.)
ganeshp's one click root requires SOFF. I can't SOFF using his technique because temp_root.bat doesn't work in bootloader screen.
I am in trouble, and don't look like getting out of it
Click to expand...
Click to collapse
@ganeshp's one click root doesn't require htc dev unlock (meaning no prequisite permanent root; the guide has steps for temproot).
You just need one boot.
Do this: get the boot.img of your current (stock rom) and type fastboot boot boot.img.
jiteshgawali said:
My phone, HTC Sensation XE, is S-ON, on default ROM, and has HBOOT 1.29.000. Needless to say, my phone is not rooted.
The phone is on a boot loop ever since I last took off the battery and placed it back. I sometimes get a message that my Android system is getting upgraded, terminating with an error "System UI has stopped working" before the phone restarts itself again.
I don't know if this is a hardware issue or software.
How do I get my phone to a normal state? I don't mind rooting the phone if I need to for the purpose of installing default/custom ROM. But I don't know if this would be possible because I only have access to boot screen at present.
Please suggest me suitable solutions. Thank you
Click to expand...
Click to collapse
I know its a long shot, but you should try doing a factory-reset from the bootloader, just in case it works.
Otherwise run an RUU from the bootloader.
firstly Itsakash he can't S-OFF because the device must be booted to the OS
secondly Far_SighT the command is fastboot flash boot boot.img
thirdly as raz0rf1sh suggested factory reset is a good idea and
fourthly jiteshgawali can you post your bootloader details?
It really is great to see your input guys.
@Far_SighT: I have tried doing the temp_root method, but it doesn't work for me. I could successfully run temp_root.bat just once (luckily, even in boot loop), but next when I tried doing the Juopunutbear SOFF it missed detecting my phone (again, because of the bootloop)
I don''t know where I can get a boot.img file from; for what it's worth, I could only get an OTA zip file for my region/CID from this thread: http://forum.xda-developers.com/showthread.php?t=1764025
@raz0rf1sh: I have done factory reset several times from bootloader, doesn't help friend. I don't have an RUU for my region/CID, all I have is an OTA zip file for my phone from the link I have specified right above this. Can't seem to get an RUU for firmware base 3.33, and CID HTC__038.
@rzr86: Posting all the details I am aware of currently:
PYRAMID PVT SHIP S-ON RL
HBOOT - 1.29.0000
eMMC-boot
Mar 2 2012, 18:14:34
CID - HTC__038
Software version - 3.33.720.106
rzr86 said:
firstly Itsakash he can't S-OFF because the device must be booted to the OS
secondly Far_SighT the command is fastboot flash boot boot.img
thirdly as raz0rf1sh suggested factory reset is a good idea and
fourthly jiteshgawali can you post your bootloader details?
Click to expand...
Click to collapse
Nope
Not necessary to boot into os for s off
Itsakash said:
Nope
Not necessary to boot into os for s off
Click to expand...
Click to collapse
It would help if you can tell me how to do this or direct me to any specific guide
jiteshgawali said:
I have tried doing the temp_root method, but it doesn't work for me. I could successfully run temp_root.bat just once (luckily, even in boot loop), but next when I tried doing the Juopunutbear SOFF it missed detecting my phone (again, because of the bootloop)
Click to expand...
Click to collapse
Did u connected mobile to pc from bootloader??
If yes then I'm helpless may b rzr was right
But in s off section I read somewhere that it doesn't require boot into android
Anyway do PM to Ganeshp he is good guy. I'm damn sure he will help u
jiteshgawali said:
I don''t know where I can get a boot.img file from; for what it's worth, I could only get an OTA zip file for my region/CID from this thread: http://forum.xda-developers.com/showthread.php?t=1764025
Click to expand...
Click to collapse
For stock rom go http://forum.xda-developers.com/showthread.php?t=1923629.
Get the rom and extract boot.img.
Then use the earlier command I posted.
Yes I haven't seen Indian version ruu until now ..so ruu is out of question AFAIK
Now the factory reset over boot loader should help if you have software problems but as per your replies it didn't work it seems
Tried HTC Dev unlock ? Even if the motherboard is replaced its worth a try
If htcdev unlock failed
Then try to go to recovery first ..from boot loader and if you went to recovery properly let me know
The other solution I propose is try to do change the cid ..even on locked bootloader sometimes it works
Try these commands one by one
fastboot oem writecid HTC__001
Then
fastboot reboot-bootloader
Then check cid using this command
fastboot getvar cid
If cid changed that's a good sign
Sent from my Nexus 7 using XDA Premium 4 mobile app
rzr86 said:
secondly Far_SighT the command is fastboot flash boot boot.img
Click to expand...
Click to collapse
I said fastboot boot boot.im instead of fastboot flash boot booti.img as the previous one boots the rom with with the new image but doesn't attempt to write that to the boot partition. Hence it might get him a much needed boot to s-off.
jiteshgawali said:
It really is great to see your input guys.
@Far_SighT: I have tried doing the temp_root method, but it doesn't work for me. I could successfully run temp_root.bat just once (luckily, even in boot loop), but next when I tried doing the Juopunutbear SOFF it missed detecting my phone (again, because of the bootloop)
I don''t know where I can get a boot.img file from; for what it's worth, I could only get an OTA zip file for my region/CID from this thread: http://forum.xda-developers.com/showthread.php?t=1764025
@raz0rf1sh: I have done factory reset several times from bootloader, doesn't help friend. I don't have an RUU for my region/CID, all I have is an OTA zip file for my phone from the link I have specified right above this. Can't seem to get an RUU for firmware base 3.33, and CID HTC__038.
@rzr86: Posting all the details I am aware of currently:
PYRAMID PVT SHIP S-ON RL
HBOOT - 1.29.0000
eMMC-boot
Mar 2 2012, 18:14:34
CID - HTC__038
Software version - 3.33.720.106
Click to expand...
Click to collapse
as you stated your current is 3.33.720.106 so the OTA update is unnecessary
do as ganeshp suggested
Itsakash said:
Did u connected mobile to pc from bootloader??
If yes then I'm helpless may b rzr was right
But in s off section I read somewhere that it doesn't require boot into android
Anyway do PM to Ganeshp he is good guy. I'm damn sure he will help u
Click to expand...
Click to collapse
both S-OFF guides say that stock rom is required in order to follow the S-OFF procedure
ganeshp said:
Yes I haven't seen Indian version ruu until now ..so ruu is out of question AFAIK
Now the factory reset over boot loader should help if you have software problems but as per your replies it didn't work it seems
Tried HTC Dev unlock ? Even if the motherboard is replaced its worth a try
If htcdev unlock failed
Then try to go to recovery first ..from boot loader and if you went to recovery properly let me know
The other solution I propose is try to do change the cid ..even on locked bootloader sometimes it works
Try these commands one by one
fastboot oem writecid HTC__001
Then
fastboot reboot-bootloader
Then check cid using this command
fastboot getvar cid
If cid changed that's a good sign
Sent from my Nexus 7 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Thanks for responding Ganesh. HTC Dev Unlock never worked for me post change of motherboard, but thanks for the suggestion.
I am able to browse the recovery option from bootloader properly.
And it gives me a little satisfaction to let you know that I was able to change the CID to HTC__001 following your steps. Can you suggest what I should be doing next?
jiteshgawali said:
Thanks for responding Ganesh. HTC Dev Unlock never worked for me post change of motherboard, but thanks for the suggestion.
I am able to browse the recovery option from bootloader properly.
And it gives me a little satisfaction to let you know that I was able to change the CID to HTC__001 following your steps. Can you suggest what I should be doing next?
Click to expand...
Click to collapse
Great now just download the HTC wwe ruu and install it... I'll link it up in a second.. Watch this space
Here is the link
http://htc.vi8.info/Sensation-XE/RU...0U-11.24A.3504.31-M-release-281004-signed.exe
Sent from my HTC Sensation 4G using XDA Premium 4 mobile app
Hi everyone,
I need your help because I can't S-OFF my HTC One S (s4) : Latest official ROM 3.16.401 (if I remember well), Bootloader unlocked, SuperCID and Hboot 2.15
I can't S-OFF with Facepalm, cause I have Hboot 2.15 right ?
And I can't either with Moonshine cause only compatible with :
3.14.531.11 (T-MOB)
3.16.666.9 (BM)
3.16.111.10 (TMO_DE)
3.16.661.4 (Telus)
So if I am SupedCID i must be able to flash any firmware above mine right ? Or do I need to match the CID anyway ?
In fact I didn't succeed in, at first with bootloader unlocked it said error in parsing android-info file (tried with 2 RUUs) then I tried with bootloader relocked and then it says "remote 12 : signature verify fail"
So...I am a little bit lost, what should I do ? Any idea ?
Thanks.
A bit off topic but still kinda related.
So i got my phone used, and when i got it, it was already bootloader unlocked and s-off. Now my question is, a lot of people are having trouble getting s-off on 2.15 hBoot, but that's what i have, along with TMOB010 CID.
I want to know how this device got s-off, and the thing is, in bootloader it doesn't even have **tampered** showing on there.
Anyone have any idea? I just want to know so that if i mess up the phone I'd know how to get it back to its previous state.
Sent from my One S using XDA Premium 4 mobile app
Noplait said:
Hi everyone,
I need your help because I can't S-OFF my HTC One S (s4) : Latest official ROM 3.16.401 (if I remember well), Bootloader unlocked, SuperCID and Hboot 2.15
I can't S-OFF with Facepalm, cause I have Hboot 2.15 right ?
And I can't either with Moonshine cause only compatible with :
3.14.531.11 (T-MOB)
3.16.666.9 (BM)
3.16.111.10 (TMO_DE)
3.16.661.4 (Telus)
So if I am SupedCID i must be able to flash any firmware above mine right ? Or do I need to match the CID anyway ?
In fact I didn't succeed in, at first with bootloader unlocked it said error in parsing android-info file (tried with 2 RUUs) then I tried with bootloader relocked and then it says "remote 12 : signature verify fail"
So...I am a little bit lost, what should I do ? Any idea ?
Thanks.
Click to expand...
Click to collapse
If you have SuperCID then yes you can flash RUU above yours. I did, but for me moonshine still didn't work but occasionally Facepalm did.
---------- Post added at 12:25 AM ---------- Previous post was at 12:20 AM ----------
JiroPrinz8 said:
A bit off topic but still kinda related.
So i got my phone used, and when i got it, it was already bootloader unlocked and s-off. Now my question is, a lot of people are having trouble getting s-off on 2.15 hBoot, but that's what i have, along with TMOB010 CID.
I want to know how this device got s-off, and the thing is, in bootloader it doesn't even have **tampered** showing on there.
Anyone have any idea? I just want to know so that if i mess up the phone I'd know how to get it back to its previous state.
Sent from my One S using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Tampered flag can be removed by tool revone.
This time I know just 2 methods how to do S-Off, moonshine and facepalm.
Can't think of one!
------> Noplait
Managed to S-Off mine with the following specs...
Baseband version : 1.12.50.05.05_10.28.50.08L
Software number : 3.16.61.10
Android version: 4.1.1
Hboot: 2.15.0000
Followed the instructions Exactly.
1. Bootloader unlock via HTCDev.
2. Steps 1,2&3 as found here
http://forum.xda-developers.com/showthread.php?t=1583427
3. SuperCID as found here
http://forum.xda-developers.com/showthread.php?p=26516911#post26516911
4. Bootloader unlock via HTCDev
(Out of curiosity did you go back to HTCDev and go through the unlock process again? As this is what I did (as per instructions)?).
5. Facepalm S-Off as found here
http://forum.xda-developers.com/showthread.php?t=2155135
(Note: for instructions 5, I dragged the appropriate zip into the command prompt line from where I had downloaded zip file,
and for instruction 7 dragged the appropriate file from the folder into the first command prompt line only - adb push <locaction of this file only: soffbin3> /data/local/tmp/
Then copied and paste the remaining two commands one at a time, remember to press enter after each of the 3 commands)
Hope that helps.
Step 3 (changig CID) seems to cause trouble to users with base 3.16.401.8, including me.
It looks like mmcblk0p4 is write protected here, so the changing of the CID just does not work.
I also didn't find a working way around yet...
Hello! I need some help here.Probably not the right place,sorry about that!
My problem is that I'm s-on,and it's seems that I can't do the supercid witch is the first step for Facepalm process.
I red a lot about this topic, everything what I have found.
It appears that I got the hboot 2.15 version with Jb ota Update ,because of this the mmcblk0p4 file is write protected... so the cid overwrite is undone.
Tried on ViperOneS 1.2.1 - 2.2.0,on Tricktroid 7-9.1 and on Jb Stock also.The adb ,the termal emulaton on phone ,hex editing works well.
This is my hboot:
*** TEMPERED ***
*** UNLOCKED ***
VLE PVT SHIP S-ON RL
HBOOT-2.15.0000
RADIO-1.11.50.05.28
OpenDSP-v31.1.0.45.0815
eMM-boot
Dec 14 2012,17:10:57:-1
My cid is Tim--401 so not Moonshine s-off compatibile.
Is exist any other method to gain S-off? or the only solution is riff/jtag?
I red the folowing treads about supercid:
http://forum.xda-developers.com/showthread.php?t=2446750&highlight=hboot+2+15+supercid&page=5
http://forum.xda-developers.com/showthread.php?t=2460148
http://forum.xda-developers.com/showthread.php?t=2453595&highlight=hboot+2+15+supercid
http://forum.xda-developers.com/showthread.php?t=1671643&page=48
http://forum.xda-developers.com/showthread.php?p=26516911#post26516911
gforums said:
Step 3 (changig CID) seems to cause trouble to users with base 3.16.401.8, including me.
It looks like mmcblk0p4 is write protected here, so the changing of the CID just does not work.
I also didn't find a working way around yet...
Click to expand...
Click to collapse
You're certain it's .8 and not the .9
I did it on 8 with no problems way back.
Verzonden vanaf mijn HTC One S met behulp van Tapatalk now Free
Here is what worked for me to get supercid 22222222 then facepalm to S-Off. Easy as Pie! But that was for me, hboot 2.15. I take no responsibility! Lol
LibertyMonger said:
Here is what worked for me to get supercid 22222222 then facepalm to S-Off. Easy as Pie! But that was for me, hboot 2.15. I take no responsibility! Lol
Click to expand...
Click to collapse
I had the 3.16.401.9, en after de ruu of 3.16.401.8 it is still write protected.
echo -ne "22222222" | dd of=/dev/block/mmcblk0p5 bs=1 seek=20
worked for me.
robertus12 said:
I had the 3.16.401.9, en after de ruu of 3.16.401.8 it is still write protected.
echo -ne "22222222" | dd of=/dev/block/mmcblk0p5 bs=1 seek=20
worked for me.
Click to expand...
Click to collapse
It was very relieving huh? I thought we couldn't do it! Glad it worked! :good:
Hi,
This ia maybe very noop question but i gonna give a shot.
I have also 16.401.9 version with hboot 2.15 i will a root access.
Unlock bootloader already done.
But supercid en s-off is mess.
I read here about special line that you must typ in command AFTER su permission.
Can somebody tell me how you gonna get SU permission? When i typ it down is tell me not found? Pfff
Sorry for my english.
Sent from my HTC One S using xda app-developers app
cashvillle said:
Hi,
This ia maybe very noop question but i gonna give a shot.
I have also 16.401.9 version with hboot 2.15 i will a root access.
Unlock bootloader already done.
But supercid en s-off is mess.
I read here about special line that you must typ in command AFTER su permission.
Can somebody tell me how you gonna get SU permission? When i typ it down is tell me not found? Pfff
Sorry for my english.
Sent from my HTC One S using xda app-developers app
Click to expand...
Click to collapse
1. Fire up your command prompt and go to the directory that you have ADB installed to. Type "adb shell" and hit enter.
2. Type "su" and hit enter. You now have root privileges.
You have the key!
robertus12 said:
I had the 3.16.401.9, en after de ruu of 3.16.401.8 it is still write protected.
echo -ne "22222222" | dd of=/dev/block/mmcblk0p5 bs=1 seek=20
worked for me.
Click to expand...
Click to collapse
Could you please elaborate on your process for getting your CID to 22222222? Do I need to modify mmcblk0p4 as the other guides have indicated? Could you please write a short guide?
sliponby said:
Could you please elaborate on your process for getting your CID to 22222222? Do I need to modify mmcblk0p4 as the other guides have indicated? Could you please write a short guide?
Click to expand...
Click to collapse
1. Fire up your command prompt and go to the directory that you have ADB installed to. Type "adb shell" and hit enter.
2. Type "su" and hit enter. You now have root privileges.
3. Type "echo -ne "22222222" | dd of=/dev/block/mmcblk0p5 bs=1 seek=20" and hit enter. To test if it worked restart the phone into fastboot (type "adb reboot bootloader" and hit enter) and once the bootloader screen comes up
type "fastboot oem readcid" and hit enter. It should read "22222222".
4. type "fastboot oem get_identifier_token" and hit enter. Leave that up on your screen and go to HTCdev.com. Follow the instructions from there.
5. Once you have confirmed you have SuperCID, get started with facepalm.
Thanks!
robertus12 said:
1. Fire up your command prompt and go to the directory that you have ADB installed to. Type "adb shell" and hit enter.
2. Type "su" and hit enter. You now have root privileges.
3. Type "echo -ne "22222222" | dd of=/dev/block/mmcblk0p5 bs=1 seek=20" and hit enter. To test if it worked restart the phone into fastboot (type "adb reboot bootloader" and hit enter) and once the bootloader screen comes up
type "fastboot oem readcid" and hit enter. It should read "22222222".
4. type "fastboot oem get_identifier_token" and hit enter. Leave that up on your screen and go to HTCdev.com. Follow the instructions from there.
5. Once you have confirmed you have SuperCID, get started with facepalm.
Click to expand...
Click to collapse
Thanks for the quick reply! Unfortunately it looks like I'm stills screwed. I followed your instructions exactly and I'm still getting my CID as TMOBO-10. If you have any other ideas, I'm listening.
sliponby said:
Thanks for the quick reply! Unfortunately it looks like I'm stills screwed. I followed your instructions exactly and I'm still getting my CID as TMOBO-10. If you have any other ideas, I'm listening.
Click to expand...
Click to collapse
you can ask the guys on irc
http://chat.andirc.net:8080/?channels=facepalm
They Know what to do.
You can't get facepalm s-off, but you could get moonshine s-off
Go to moonshine.io and look for the supported RUU versions and install one that corresponds to your cid. Then you could install moonshine s-off.
Sent from my One S using Tapatalk 4
RyogoNA said:
You can't get facepalm s-off, but you could get moonshine s-off
Go to moonshine.io and look for the supported RUU versions and install one that corresponds to your cid. Then you could install moonshine s-off.
Sent from my One S using Tapatalk 4
Click to expand...
Click to collapse
i have tried... after second test, monshine awaits adb for too short time...about 2-3 secs is missing for phone to reboot completly for monshine could connect with adb... after time counts 60 secs, monshine says i need to fix my adb...
try here
EDIT - I found a workaround and have successfully achieved s-off