My DS is it bricked forever ? - HTC Desire S

Hello,
I can access the hboot menu only, but I can't access to recovery : 7 vibrations.
I can't unlocked, have error with : fastboot oem get_identifier_token ==> (bootloader) [ERR] Command error !!!
When I start flashing a RUU, my Desire S hangs
When I try to flash a PG88IMG.zip it hangs at bootlaoder updating.
adb shell doesn't work, fastboot devices work.
need help please.
Thanx
My DS :
hboot:0.98.0000, LOCKED and S-ON

TF85 said:
Hello,
I can access the hboot menu only, but I can't access to recovery : 7 vibrations.
I can't unlocked, have error with : fastboot oem get_identifier_token ==> (bootloader) [ERR] Command error !!!
When I start flashing a RUU, my Desire S hangs
When I try to flash a PG88IMG.zip it hangs at bootlaoder updating.
adb shell doesn't work, fastboot devices work.
need help please.
Thanx
My DS :
hboot:0.98.0000, LOCKED and S-ON
Click to expand...
Click to collapse
Seven vibrations can sometimes mean that your partitions have became corrupted. While you are s-on this will be very hard to fix. If I was you I would try to locate someone near you with access to an xtc clip. Its a hardware device that can s-off certain htc models, yours included. Once you have s-off you could then run a ruu and hopefully your hboot would be able to fix the damaged partitions. Failing that gaining access to someone with a j-tag like a riff box would allow them to perform a full restore of the nand, s-on or not, and they could rebuild your partitions. Given that you are s-on and cannot flash a stable ROM software is not a viable option.
Sent from my Desire S using Tapatalk

Hello,
Thank you very much for your help.
I'll try with xtc clip somewhere.
Thank you a lot.

TF85 said:
Hello,
Thank you very much for your help.
I'll try with xtc clip somewhere.
Thank you a lot.
Click to expand...
Click to collapse
There is no HTCunlock for this bootloader version.
Use the command
fastboot getvar all
to find you exact software number (example 1.47.401.4). Then find a RUU with the same number and run it on your PC with phone connected via USB.
After that your phone has to be running normally.
Use Revolutionary to gain S-OFF or update the software to newer version to use HTCunlock after this if you still need it.

Related

ICS Rooted to Stock S-on

Hi I am with ICS ARHD rom one of the latest firmwares. I have a problem with my phone and I want to use the warranty so what is the best way to revert it to Stock and Unroot and S-on?
SsBloodY said:
Hi I am with ICS ARHD rom one of the latest firmwares. I have a problem with my phone and I want to use the warranty so what is the best way to revert it to Stock and Unroot and S-on?
Click to expand...
Click to collapse
Could you give me the same answer but how to do it without needing to read something from Screen?
My screen is not working - phone works completely, but I can't see anything.
I would like to bring it back to the oryginal state to send it for warranty repair
For both of you, flash the stock RUU for your device. Go to this thread.
T-Macgnolia said:
For both of you, flash the stock RUU for your device. Go to this thread.
Click to expand...
Click to collapse
This is the idea that I had - I downloaded
RUU_PYRAMID_ICS_HTC_Europe_3.32.401.5_Radio_11.69.3504.00U_11.22.3504.07_M_release_246089_signed.exe
it detects my version of rom
Update
"From 1.11.401.110"
To
"3.32.401.5"
Then there is a checking phase and it returns Error[155]: Error during update image.
Maybe should I extract image from %temp% and flash it using P58IMG file?
I don't remember - do I have to do something from menu (using vol up/vol down) using that method?
adminmodeenabled said:
This is the idea that I had - I downloaded
RUU_PYRAMID_ICS_HTC_Europe_3.32.401.5_Radio_11.69.3504.00U_11.22.3504.07_M_release_246089_signed.exe
it detects my version of rom
Update
"From 1.11.401.110"
To
"3.32.401.5"
Then there is a checking phase and it returns Error[155]: Error during update image.
Maybe should I extract image from %temp% and flash it using P58IMG file?
I don't remember - do I have to do something from menu (using vol up/vol down) using that method?
Click to expand...
Click to collapse
error 155 ..is either you didnt run the ruu with phone connected in fastboot or you have HTC-dev unlocked bootloader
if you got HTC-dev unlocked bootloader then relock it and run
make sure you connect the device in fastboot (phone reads fastboot usb) then run the RUU
ganeshp said:
error 155 ..is either you didnt run the ruu with phone connected in fastboot or you have HTC-dev unlocked bootloader
if you got HTC-dev unlocked bootloader then relock it and run
make sure you connect the device in fastboot (phone reads fastboot usb) then run the RUU
Click to expand...
Click to collapse
I have non-HTC dev (changed mainboard) unlocked bootloader.
using adb reboot-bootloader I managed to install RUU.
RUU_PYRAMID_ICS_HTC_Europe_3.32.401.5_Radio_11.69.3504.00U_11.22.3504.07_M_release_246089_signed.exe
I had previously S-OFF and Unlocked bootloader (using non-HTC method)
Do I need to do something more to bring it back to oryginal state?
Because I cannot see the screen
adminmodeenabled said:
I have non-HTC dev (changed mainboard) unlocked bootloader.
using adb reboot-bootloader I managed to install RUU.
RUU_PYRAMID_ICS_HTC_Europe_3.32.401.5_Radio_11.69.3504.00U_11.22.3504.07_M_release_246089_signed.exe
I had previously S-OFF and Unlocked bootloader (using non-HTC method)
Do I need to do something more to bring it back to oryginal state?
Because I cannot see the screen
Click to expand...
Click to collapse
RUU ran means ..rom, recovery and hboot is stock
now two more things
if supercid ..change it back to original cid
get your cid from here
and command is
fastboot oem writecid <your cid>
eg: fastboot oem writecid HTC__001
then do
fastboot reboot-bootloader
then check the cid again
fastboot getvar cid ( it should match with the cid you used to change)
then finally do S-ON (this should be always last step ..when restoring stock)
fastboot oem writesecureflag 3
thats all you are complete stock now
ganeshp said:
RUU ran means ..rom, recovery and hboot is stock
now two more things
if supercid ..change it back to original cid
get your cid from here
and command is
fastboot oem writecid <your cid>
eg: fastboot oem writecid HTC__001
then do
fastboot reboot-bootloader
then check the cid again
fastboot getvar cid ( it should match with the cid you used to change)
then finally do S-ON (this should be always last step ..when restoring stock)
fastboot oem writesecureflag 3
thats all you are complete stock now
Click to expand...
Click to collapse
Thanks -I can handle it but one problem
I flashed oryginal rom and probably my phone is in Android-Setup phase and I cannot connect to it using ADB. Probably because debugging is OFF.
I probably can do it from bootloader, but could please tell me which key I should press after entering it and how many times?
Error 155 means your bootloader is unlocked. Just relock it and try again.
rlamba said:
Error 155 means your bootloader is unlocked. Just relock it and try again.
Click to expand...
Click to collapse
Yes, I know - but how to do it when I flashed oryginal Rom, my phone is in setup phase and I can't enable debugging because my screen isn't working.
adminmodeenabled said:
Yes, I know - but how to do it when I flashed oryginal Rom, my phone is in setup phase and I can't enable debugging because my screen isn't working.
Click to expand...
Click to collapse
for fastboot commands to work..debugging enabling is not required (it is needed for adb to work)
just remove the battery ..reinsert it and hold vol down + power ...you will get a vibration ..and that means you are at bootloader now
then connect the device to pc
and on pc type this
fastboot devices
if it shows your device then you are connected ...and proceed as explained earlier ..otherwise repeat the above process
ganeshp said:
RUU ran means ..rom, recovery and hboot is stock
now two more things
if supercid ..change it back to original cid
get your cid from here
and command is
fastboot oem writecid <your cid>
eg: fastboot oem writecid HTC__001
then do
fastboot reboot-bootloader
then check the cid again
fastboot getvar cid ( it should match with the cid you used to change)
then finally do S-ON (this should be always last step ..when restoring stock)
fastboot oem writesecureflag 3
thats all you are complete stock now
Click to expand...
Click to collapse
Everythings works.
Thanks man!!
perfection
Is there a nomination for a perfect thread? This is short, 100% informative, there is no bs, and it works great! Thanks to all

[Q] Returning to bone-stock... without using the screen

So, the backlight crapped out on my device after being a bit spotty (would come back after pressing around on the phone a bit). I'm thankfully still within the warranty period, but I'm S-OFF, bootloader's unlocked, and I'm running Sense 5. I'd like to minimize the chances of having my warranty invalidated for taking the bootloader unlock and everything, but it's quite difficult to do so without a screen to look at.
RUU'ing and switching back to CWS__001 should be easy as pie with fastboot, but I'm not sure how to relock the bootloader without the "relocked" tag and return to S-ON without flashing zips in recovery. I can't really adb sideload because I don't know TWRP's UI well enough to navigate around without seeing where all the UI elements are. Perhaps someone could guide me through navigation.
Lastly, I can't really verify visually whether or not I have TAMPERED, RELOCKED, or S-OFF, so is there any way to check all three via fastboot/adb?
To change it so that it's says ***LOCKED*** you can use the customize hboot tool here and make a custom plug hboot file http://forum.xda-developers.com/showthread.php?t=2156368 There is a fastboot comand that will basically read off the bootloader to you, fastboot get... Something. Exad knows this command, so he could tell you.
RollTribe said:
To change it so that it's says ***LOCKED*** you can use the customize hboot tool here and make a custom plug hboot file http://forum.xda-developers.com/showthread.php?t=2156368 There is a fastboot comand that will basically read off the bootloader to you, fastboot get... Something. Exad knows this command, so he could tell you.
Click to expand...
Click to collapse
I think it's
fastboot getvar all
doesn't show if it's locked or not though..
If you run an RUU
then use the Locked spoofer
then fastboot oem writesecureflag 3
You should be just fine.
So that's 5 instances where the backlight/display has stopped working for no apparent reason? I'm thinking it may HTCs fault and not the user..
Sent from my Nexus 4

Htc one s (s3) can't unlock bootloader

Hello for everyone!
Htc one s (s3) can't unlock bootloader, always stay relocked. I try everything, many unlocking tools, regular metod whit Htcdev, token subm, kingo unlocked... Nothing change.
VILLEC2 PVT SHIP S-ON RL
HBOOT-3.01.0000
RADIO-16.11.20.24_M
Software stock JB4.1.1
Any solution.
Greeting from Serbia
Aleksic82 said:
Hello for everyone!
Htc one s (s3) can't unlock bootloader, always stay relocked. I try everything, many unlocking tools, regular metod whit Htcdev, token subm, kingo unlocked... Nothing change.
VILLEC2 PVT SHIP S-ON RL
HBOOT-3.01.0000
RADIO-16.11.20.24_M
Software stock JB4.1.1
Any solution.
Greeting from Serbia
Click to expand...
Click to collapse
Hi,
I have the exact same problem... unable to unlock the phone...
when in bootloader : "adb devices" show my device
when in fastboot : "fastboot devices" show nothing and "fastboot oem get_identifier_token" get stuck in "<waiting for device>"
Also, when in bootloader, if i choose "recovery", i can't enter the recovery menu, instead i have a warning sign for about 1 minut, then unit reboot.
Hope someone found a solution...
Thanks,
ndaneau said:
Hi,
I have the exact same problem... unable to unlock the phone...
when in bootloader : "adb devices" show my device
when in fastboot : "fastboot devices" show nothing and "fastboot oem get_identifier_token" get stuck in "<waiting for device>"
Also, when in bootloader, if i choose "recovery", i can't enter the recovery menu, instead i have a warning sign for about 1 minut, then unit reboot.
Hope someone found a solution...
Thanks,
Click to expand...
Click to collapse
Whn you see the red warning sing, I believe, you have to press VOLUME UP to see the recovery menu. As for undetectable devices in fastboot, I assume you are using Windows 8.1 or higher. Fastboot doesn't work there, unless fixed by using the instructions and registry edit from this thread (I can confirm, it works like a charm).
Let me know if you need any more help and if it worked.

Hopelessly stuck with relocked HTC One M8 Verizon - what options do I have?

I rooted the phone using sunshine and superSU and got TWRP-2.8.7.0-m8 working, flashed a ROM (ViperONEM8) but was stuck in fastboot menu so I opened the fastboot folder shift+right click CMD window and moved the boot.img from the ROM to that folder in hopes I could flash the ROM via CMD. However, I read that I needed to 'relock' the bootloader for it to work which I did, however now the phone is stuck in recovery or fastboot with a relocked bootloader and S-OFF...
I also got the Identifier Token only to learn that with a Verizon phone it gives me a CID error code and I can't unlock it that way.
I just bought the phone this week from Amazon and didn't realize that it was the Verizon version as I am an AT&T customer. I am at my wits end and don't even know how to sell the phone to get even some of my money back.
What can I do?
Phone details:
HTC One M8 (Verizon)
M8_WLV PVT SIP S-OFF
CID-VZW__001
HBOOT-3.19.0.0000
RADIO-1.09.20.0926
OpenDSP-v46.2.2-00564-M8974_FO.0811
OS-3.28.605.9
I've been at this for 72+ hours no sleep and I'm about to pluck my eyeballs out.
Any help would be greatly appreciated!
I did find one link to a RUU that I haven't tried yet due to downloading issues:
Bearathustra said:
I rooted the phone using sunshine and superSU and got TWRP-2.8.7.0-m8 working, flashed a ROM (ViperONEM8) but was stuck in fastboot menu so I opened the fastboot folder shift+right click CMD window and moved the boot.img from the ROM to that folder in hopes I could flash the ROM via CMD. However, I read that I needed to 'relock' the bootloader for it to work which I did, however now the phone is stuck in recovery or fastboot with a relocked bootloader and S-OFF...
I also got the Identifier Token only to learn that with a Verizon phone it gives me a CID error code and I can't unlock it that way.
I just bought the phone this week from Amazon and didn't realize that it was the Verizon version as I am an AT&T customer. I am at my wits end and don't even know how to sell the phone to get even some of my money back.
What can I do?
Phone details:
HTC One M8 (Verizon)
M8_WLV PVT SIP S-OFF
CID-VZW__001
HBOOT-3.19.0.0000
RADIO-1.09.20.0926
OpenDSP-v46.2.2-00564-M8974_FO.0811
OS-3.28.605.9
I've been at this for 72+ hours no sleep and I'm about to pluck my eyeballs out.
Any help would be greatly appreciated!
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2727831
Bearathustra said:
I rooted the phone using sunshine and superSU and got TWRP-2.8.7.0-m8 working, flashed a ROM (ViperONEM8) but was stuck in fastboot menu so I opened the fastboot folder shift+right click CMD window and moved the boot.img from the ROM to that folder in hopes I could flash the ROM via CMD. However, I read that I needed to 'relock' the bootloader for it to work which I did, however now the phone is stuck in recovery or fastboot with a relocked bootloader and S-OFF...
I also got the Identifier Token only to learn that with a Verizon phone it gives me a CID error code and I can't unlock it that way.
I just bought the phone this week from Amazon and didn't realize that it was the Verizon version as I am an AT&T customer. I am at my wits end and don't even know how to sell the phone to get even some of my money back.
What can I do?
Phone details:
HTC One M8 (Verizon)
M8_WLV PVT SIP S-OFF
CID-VZW__001
HBOOT-3.19.0.0000
RADIO-1.09.20.0926
OpenDSP-v46.2.2-00564-M8974_FO.0811
OS-3.28.605.9
I've been at this for 72+ hours no sleep and I'm about to pluck my eyeballs out.
Any help would be greatly appreciated!
Click to expand...
Click to collapse
You are S-OFF so you have nothing to worry about.
You are pretty much never stuck with an S-OFF device unless you brick it by being careless and flashing something not made for the device.
You can always run the RUU, this will put you on stock ROM and update your firmware.
You can also always change to SuperCID since it's a Verizon device that you use on AT&T, but first lets get your bootloader unlocked again. :good:
This thread is what you want:
It explains how to easily, lock/unlock your bootloader - which you can do at anytime as long as you are S-OFF.
http://forum.xda-developers.com/showthread.php?t=2708571
Copy and paste the commands.
This is taken from the above thread:
to UNLOCK your bootloader,enter the following:
adb devices
adb shell
su (if needed to get a # prompt)
echo -ne "HTCU" | dd of=/dev/block/mmcblk0p2 bs=1 seek=33796
(i would very strongly recomend you copy/paste this)
exit
(exit a second time if you need to to get back to a normal > prompt)
adb reboot bootloader
verify you are now unlocked
--------------------------------------------------
Now this isn't a neccesity, but if you want to SuperCID your device the cmd is this:
(run this cmd in fastboot)
fastboot oem writecid 11111111
- highly suggest you copy/paste this
(Not that you need a token from HTC since you are S-OFF..but with SuperCID, I believe you can get one)
Now, as for getting AT&T to run on a Verizon device, I honestly have no clue about. You can flash Verizon ROMs and see what type of service you get.
Also, for selling the device, the best place to do so is http://www.swappa.com
Enjoy, hope this helps.

Help HTC U11 Brick

I tell them what happened to me, my U11 phone had it with the European version and I did s-off with sunshine without problems, I changed cid BS_US001 and mid 2PZC50000 without any problem, but try to load the ruu that you download from htc 1.28.617.3 and came out error 155 that the image was not correct, then what I did was to close the bootloader with the command fastboot oem lock, reset the phone and send me to the bootloader screen, when entering download it appeared and s-on and Bootloader Relocked , try to load the ruu again but it tells me that the image does not correspond, try to install recovery stock, TWRP, and firmware 1.28.617.3 but it does not let me do anything, when trying to enter recovery it sends me to bootloader and if I try to unblock bootloader I gives frp error, it is clear that despite being relocked the bootloader I keep appearing the screen that has been modified the phone, when entering download I appears in OS 1.28.401.7 and putting fastboot getvar all if I see the c id and mid of the American version, but I do not do anything.
Do you think it has a solution?
Waiting answer ...
Thank you ...
Hi.
There are no answers yet, because, honestly, it is difficult to understand what happened. You wrote one single phrase that is 10 lines long. Try to reformulate, using listed items, paragraphs and so on.
Just a friendly suggestion, no offense.
valvaher said:
I tell them what happened to me, my U11 phone had it with the European version and I did s-off with sunshine without problems, I changed cid BS_US001 and mid 2PZC50000 without any problem, but try to load the ruu that you download from htc 1.28.617.3 and came out error 155 that the image was not correct, then what I did was to close the bootloader with the command fastboot oem lock, reset the phone and send me to the bootloader screen, when entering download it appeared and s-on and Bootloader Relocked , try to load the ruu again but it tells me that the image does not correspond, try to install recovery stock, TWRP, and firmware 1.28.617.3 but it does not let me do anything, when trying to enter recovery it sends me to bootloader and if I try to unblock bootloader I gives frp error, it is clear that despite being relocked the bootloader I keep appearing the screen that has been modified the phone, when entering download I appears in OS 1.28.401.7 and putting fastboot getvar all if I see the c id and mid of the American version, but I do not do anything.
Do you think it has a solution?
Waiting answer ...
Thank you ...
Click to expand...
Click to collapse
Ok i may be way off base, but if the phone can boot into the OS go to developer enable usb debug and
Oem unlocking then follow the htc guide to unlock bootloader again ( not positive on that part never relocked a bootloader then unlocked) once that is done redownload the correct ruu per your cid and retry. Just my 2 cents. Hth.
you only flash full ruu 1.28.401.7
try to find in https://forum.xda-developers.com/u11/how-to/collection-htcu-u11-ruu-firmware-t3612048

Categories

Resources