Database Info

[Q] Please help...Think i messed up BIG

Hi,
My phone freezes on the boot up screen (where T-mobile pops up) I know there are LOADS of threads on help for problems like that, but I think it's fair to say, I've tried quite a few of them (or at least looked to see if they could help me) but I'm still epically stuck I'll describe what i can in order, because I tried quite a few things..... -.-
I've got Htc desire S, from T-mobile UK
Hboot- 2.00.2002
I tried to root it to get pdroid, of course, found out that i needed to downgrade it to 0.98 for zergRush......got the "Hellions with BLUE flames" message so moved on to tacoroot. it was fine until i got permission denied at the last cmd code. (the posts on the thread suggested using zergRush if tacoroot did not work -.-)
this is the most problematic part i'm guessing. I gave up on those 2 and found this "guide-how-root-desire-s" on android forums, it uses revolutionary and cwm
But while i was trying out that, i found revolutionary-0.4pre4, which sounded alot easier therefore i alternated between both since the rev 0.4 made the guide a lot easier (took out half of part 1 and whole of part 2). I managed to finish, reboot.
At this point Hboot screen had ***locked*** on top and S-off, but it was still on 2.something
I realized I had a RUU left over from one of the previous guides....(RUU_Saga_HTC_Europe_1.28.401.1_Radio_20.28b.30.0805U_38.03.02.11_M_release_177977_signed)
so thinking i had to use it (since i was still on hboot 2.00.something), I stuck my phone on fastboot USB and started RUU up. it ran smoothly and soon finished, I rebooted my phone to check if i was in 0.98, which i was,and happily booted up my phone. But i didn't notice S was ON. Next thing i know, I've frozen on the boot up screen, so i take the battery out, booted to Hboot.
Now i can't access recovery menu, factory reset, and i can't reboot since it freezes on "t-Mobile" screen.
Have i broken it for good? if not what can i do to fix it?
Sorry this was a bit wordy, i didn't know what was useful so i just put it all in (well as much as i can remember accurately)
-quick summary-
HTC desire S
T-mobile
Hboot: 2.00.2002 (now 0.98)
S-ON (now, managed to have it off at a point...)
zergRush > tacoroot > revolutionary + guide using cwm recovery > messing it all up cause i forgot to put rom in SD card + used RUU > mega stuck...
I'm completely new to this rooting and stuff, please help. Thanks
edit..
oh, i don't know if it'll help but on cmd (I've installed adb, fastboot correctly) adb commands do not work, and says something like "device not found" or "waiting for device". Fastboot DOES work when on fastboot USB only.
edit....
change hboot version listed here from 2.00.002 to 2.00.2002
carelessness

Have you tried changing your miscellaneous version then running the RUU again and then use revolutionary to gain S-OFF then flash any rom you want P.S >>>> FALLOUT is probably the best at the moment
Good luck.

Hi, Duty09
Thanks for the quick reply. how do i change my misc version?i can't "adb push" since my phone wont register with cmd.....adb devices show nothing. Do i stick it in root and flash from fastboot?
Thanks

Try following this and see if it will srt your issue out
http://forum.xda-developers.com/showthread.php?t=1525100

Since you are now back to old hboot can't you just run revolutionary again to gain s-off then flash a new Rom?
Sent from my HTC Desire S using XDA

Forcefire said:
Try following this and see if it will srt your issue out
http://forum.xda-developers.com/showthread.php?t=1525100
Click to expand...
Click to collapse
i dont think it'll work. htc desire S in not listed under htcdev. i know some people how been saying it can still work, but i can't find how...

Eclipse_Droid said:
Since you are now back to old hboot can't you just run revolutionary again to gain s-off then flash a new Rom?
Sent from my HTC Desire S using XDA
Click to expand...
Click to collapse
I can't, because when i run revolutionary, it gives me "waiting for device". i've tried running it while in Fastboot USB, HBOOT USB PLUG, even during the frozen t-mobile screen..... is there another way of doing this?

iinock said:
i dont think it'll work. htc desire S in not listed under htcdev. i know some people how been saying it can still work, but i can't find how...
Click to expand...
Click to collapse
From what I recall, you just select "All Other Supported Models"

SimonTS said:
From what I recall, you just select "All Other Supported Models"
Click to expand...
Click to collapse
hi, just tried it and I'm stuck at step 8 at the cmd command "fastboot oem get_identifier_token" the result it gives me is
...
<bootloader> [ERR] command error!!!
OKAY [ 0.016s]
finished. total time: 0.016s
What can i do??

iinock said:
hi, just tried it and I'm stuck at step 8 at the cmd command "fastboot oem get_identifier_token" the result it gives me is
...
<bootloader> [ERR] command error!!!
OKAY [ 0.016s]
finished. total time: 0.016s
What can i do??
Click to expand...
Click to collapse
Did you type
/android/fastboot oem get_identifier_token
Click to expand...
Click to collapse
or
./fastboot oem get_identifier_token
Click to expand...
Click to collapse

SimonTS said:
Did you type
or
Click to expand...
Click to collapse
neither,
started up cmd, cd to file with adb, fastboot, and the other one. and typed in fastboot oem get_identifier_token
i've just tried both 2nd one gave me
'.' is not recognized as an internal or external command,
operable program or batch file.
the first one gave me
...
(bootloader) [ERR] Command error !!!
OKAY [ 0.031s]
finished. total time: 0.031s
0.015s longer than fastboot oem get_identifier_token.......

Putting that into Google and getting many results, it looks like the HBOOT version needs to be spot-on for that command to be present. What version of HBOOT are you running?
Ignore that - just reread the thread. You did have v2.00.002, but you've changed it to v0.98 something?
Have a look here http://androidforums.com/desire-s-all-things-root/444571-unlock-using-htcdev-com.html
You need HBOOT v2.* upwards to use HTCDEV unlock method.

SimonTS said:
Putting that into Google and getting many results, it looks like the HBOOT version needs to be spot-on for that command to be present. What version of HBOOT are you running?
Click to expand...
Click to collapse
right now its 0.98.0000
it was 2.something, but after loads of attempts at tweaking, it changed. think it was the RUU i ran after revolutionary, guessing thats what messed it up as well. but that's just my blind guess...
problem is, i can't change it back, OR change it to anything

Try following this post to restore your 2.0...... HBOOT
http://forum.xda-developers.com/showpost.php?p=18122984&postcount=237
I'm no expert but the guides on this site are wicked and I'm learning so much just reading them.

Forcefire said:
Try following this post to restore your 2.0...... HBOOT
http://forum.xda-developers.com/showpost.php?p=18122984&postcount=237
I'm no expert but the guides on this site are wicked and I'm learning so much just reading them.
Click to expand...
Click to collapse
Thanks, will definitely try that when adb works again. but i can't do that yet since adb is not working with my phone, it wont show up on "adb devices" any commands given just get "waiting for device" as a reply

just found this thread that seemed to have a lot in common with my problem
http://forum.xda-developers.com/showthread.php?t=1412398
but i'm running in to problems with CID, tried to do it with gold card but still no luck (i think gold card is done properly...)

im going to try get gold card with a different SD card.
IF it does work what RUU should i use? what steps should i do after, if it goes smoothly? (trying to get my phone working again and if possible get pdroid...)
thanks

@iinock not sure if this will help but ive got a T-Mobile RUU if you need it or have you already tried this ?
and have you tried android flasher yet ?

iinock said:
im going to try get gold card with a different SD card.
IF it does work what RUU should i use? what steps should i do after, if it goes smoothly? (trying to get my phone working again and if possible get pdroid...)
thanks
Click to expand...
Click to collapse
This is my dropbox link that contains Android flasher with english HBOOT and a T-Mobile RUU. Try and flash the english HBOOT first via android flasher then try and run the RUU but if the HBOOT fails via android flasher then just try the T-Mobile RUU and see if that works if not i am fresh out of ideas mate and hope that some more experienced devs can help you.
Best of luck.
https://www.dropbox.com/sh/0i5xlxrwvut1olf/4Vr_YuH60y
MD5 for RUU - F0773C207F0A87D6FB3A2AB42F1FA637
MD5 for android flasher.rar - FAD89057F68363A1D134E93CE6429BFF

DuTY09 said:
This is my dropbox link that contains Android flasher with english HBOOT and a T-Mobile RUU. Try and flash the english HBOOT first via android flasher then try and run the RUU but if the HBOOT fails via android flasher then just try the T-Mobile RUU and see if that works if not i am fresh out of ideas mate and hope that some more experienced devs can help you.
Best of luck.
https://www.dropbox.com/sh/0i5xlxrwvut1olf/4Vr_YuH60y
MD5 for RUU - F0773C207F0A87D6FB3A2AB42F1FA637
MD5 for android flasher.rar - FAD89057F68363A1D134E93CE6429BFF
Click to expand...
Click to collapse
Thanks for the links.
I managed to fix my phone by using a different SD card as a gold card (used LG 1gb) then flashed OTA_Saga_S_HTC_Europe_2.10.401.8-1.47.401.4_release_225210uj1q93xrps74xzje
now it works , got to try install rom and pdroid now
thanks for your help guys :good:

[Q] Phone won't boot up normally and cannot flash RUU

Hi,
First of all, sorry if this has already been answered somewhere else but I literally spent the last 3 days gathering information on xda reading threads more of less related to my specific problem. I would appreciate any new piece of information that I could have missed.
I had a custom ROM (ARHD 7.1). I wanted to go back to stock ROM for my provider (Bell Mobility). I successfully went back to GB 2.3.4 by flashing my provider's RUU. My phone would not take OTA update to ICS (4.0.3). I changed my SuperCID back to carrier-specific and phone took OTA update. However, it didn't reboot properly. I thought that this was because I was S-OFF and unlocked. I changed to S-ON but that bricked the phone (not even powering on). I found a tool to unbrick the phone that flashes a proper HBOOT (1.17 in my case). That fixed the brick problem and I could get back to bootloader. Since then, I'm stucked with a phone that doesn't boot into the ROM and cannot get into recovery. I can get into bootloader but given that I am S-ON, I'm very limited to what I can do.
I have tried re-flashing my 1.45.666.1 RUU but it looks like some time ago (don't ask me why...), I changed my MID to PG5810000 and the RUU is expecting PG5811000 so it is not possible to use RUU. I even tried modifying the android-info.txt with my MID but then RUU failed for another reason (bad signature I think).
So, this is very confusing but if I could summarize, I would say
*Cannot boot into stock ROM (it should be GB 2.3.4 from Bell Mobility)
*Can boot in bootloader
*S-ON
*MID=PG581000 (should be PG5811000 according to my provider Bell Mobility)
*CID=BM____001 (it is the correct one for Bell Mobility)
Bootloader information
PYRAMID PVT SHIP S-ON RLo
HBOOT-1.17.0008
RADIO-10.14.9035.01_M
eMMC-boot
May 13 2011.21:04:57
Is there any thing I can do to recover? Getting S-OFF would help of course but I cannot use Revolutionary tool normally as it requires you to boot in your ROM. Maybe there are some backdoor commands that Revolutionary uses that I can call with fastboot?
My last resort is to contact HTC or Bell but I'd like to avoid this as I am out of the warranty period, which my messing around would have voided anyway. Thanks for your help.
Fred

fdavidson said:
Hi,
First of all, sorry if this has already been answered somewhere else but I literally spent the last 3 days gathering information on xda reading threads more of less related to my specific problem. I would appreciate any new piece of information that I could have missed.
I had a custom ROM (ARHD 7.1). I wanted to go back to stock ROM for my provider (Bell Mobility). I successfully went back to GB 2.3.4 by flashing my provider's RUU. My phone would not take OTA update to ICS (4.0.3). I changed my SuperCID back to carrier-specific and phone took OTA update. However, it didn't reboot properly. I thought that this was because I was S-OFF and unlocked. I changed to S-ON but that bricked the phone (not even powering on). I found a tool to unbrick the phone that flashes a proper HBOOT (1.17 in my case). That fixed the brick problem and I could get back to bootloader. Since then, I'm stucked with a phone that doesn't boot into the ROM and cannot get into recovery. I can get into bootloader but given that I am S-ON, I'm very limited to what I can do.
I have tried re-flashing my 1.45.666.1 RUU but it looks like some time ago (don't ask me why...), I changed my MID to PG5810000 and the RUU is expecting PG5811000 so it is not possible to use RUU. I even tried modifying the android-info.txt with my MID but then RUU failed for another reason (bad signature I think).
So, this is very confusing but if I could summarize, I would say
*Cannot boot into stock ROM (it should be GB 2.3.4 from Bell Mobility)
*Can boot in bootloader
*S-ON
*MID=PG581000 (should be PG5811000 according to my provider Bell Mobility)
*CID=BM____001 (it is the correct one for Bell Mobility)
Bootloader information
PYRAMID PVT SHIP S-ON RLo
HBOOT-1.17.0008
RADIO-10.14.9035.01_M
eMMC-boot
May 13 2011.21:04:57
Is there any thing I can do to recover? Getting S-OFF would help of course but I cannot use Revolutionary tool normally as it requires you to boot in your ROM. Maybe there are some backdoor commands that Revolutionary uses that I can call with fastboot?
My last resort is to contact HTC or Bell but I'd like to avoid this as I am out of the warranty period, which my messing around would have voided anyway. Thanks for your help.
Fred
Click to expand...
Click to collapse
you sure the RUU you are using is correct ?
if so then best solution is to try revolutionary
try the tool with phone connected in fastboot ...it might work (i remember one guy doing that )

ganeshp said:
you sure the RUU you are using is correct ?
if so then best solution is to try revolutionary
try the tool with phone connected in fastboot ...it might work (i remember one guy doing that )
Click to expand...
Click to collapse
Thanks ganeshp for the quick answer. I am pretty confident about the RUU as it is the same one I originally ran to move from custom ICS ROM to stock 2.3.4 ROM.
For Revolutionary, even in fastboot, it is stuck in "Waiting for devices..." I think it is because it issues "adb devices" command and expects some answer before carrying on to the bootloader. I would need it to skip this step. Are there any argument to revolutionary to do that?
Fred

A little more update on RUU failure. If I change the modelid in android-info.txt, this means that I have to re-package the files back into ROM.zip. I am doing this with WinZip. Even without editing any file, just extracting the files from original ROM.zip from RUU back to another version of ROM.zip (no change), I noticed that file size is not the same. Maybe that explain with the signature check fails when flashing RUU. Now, I don't know what to use to re-package files into a ROM.zip archive to use RUU.
Fred

fdavidson said:
A little more update on RUU failure. If I change the modelid in android-info.txt, this means that I have to re-package the files back into ROM.zip. I am doing this with WinZip. Even without editing any file, just extracting the files from original ROM.zip from RUU back to another version of ROM.zip (no change), I noticed that file size is not the same. Maybe that explain with the signature check fails when flashing RUU. Now, I don't know what to use to re-package files into a ROM.zip archive to use RUU.
Fred
Click to expand...
Click to collapse
Short answer - you cannot touch or do anything to ROM.zip if you want to use RUU, changing anything changes MD5 sum hence the signature error.
What you should do is run an ICS RUU compatible with your MID

Jonny said:
Short answer - you cannot touch or do anything to ROM.zip if you want to use RUU, changing anything changes MD5 sum hence the signature error.
What you should do is run an ICS RUU compatible with your MID
Click to expand...
Click to collapse
Thanks Jonny, that is good information. My problem with this is that I have a provider-specific CID (BM_0001) and not superCID. If I can find an ICS RUU for my MID (the one wrongly change for my device, i.e. PG5810000), would the CID affect anything?
Fred

fdavidson said:
Thanks Jonny, that is good information. My problem with this is that I have a provider-specific CID (BM_0001) and not superCID. If I can find an ICS RUU for my MID (the one wrongly chance for my device, i.e. PG5810000), would the CID affect anything?
Fred
Click to expand...
Click to collapse
Mate MID/CID are checked prior to flashing rom, so if the MID/CID are not "correct" installation will not take place

dublinz said:
Mate MID/CID are checked prior to flashing rom, so if the MID/CID are not "correct" installation will not take place
Click to expand...
Click to collapse
Thanks everyone for taking some of your time to help me. From the information that I've received, it looks that I will not be able to recover my phone, That's bad because I thought I was just a few steps away, maybe by being able to flash an unlocked S-OFF H-Boot 1.17 and by some way tweak RUU so that it would work. I'll wait one or two days in case someone suggests something different and then see if HTC can help. It will be interesting (or embarassing) to hear what they have to say.
Cheers,
Fred

fdavidson said:
Thanks everyone for taking some of your time to help me. From the information that I've received, it looks that I will not be able to recover my phone, That's bad because I thought I was just a few steps away, maybe by being able to flash an unlocked S-OFF H-Boot 1.17 and by some way tweak RUU so that it would work. I'll wait one or two days in case someone suggests something different and then see if HTC can help. It will be interesting (or embarassing) to hear what they have to say.
Cheers,
Fred
Click to expand...
Click to collapse
Change back the android-info.txt and run the ruu again.. From phone connected in fastboot.. And let me know what error it showed
Edit: or simply run the ruu you have.. With phone connected to pc in bootloader/fastboot
Sent from my HTC Sensation 4G using xda premium

ganeshp said:
Change back the android-info.txt and run the ruu again.. From phone connected in fastboot.. And let me know what error it showed
Edit: or simply run the ruu you have.. With phone connected to pc in bootloader/fastboot
Sent from my HTC Sensation 4G using xda premium
Click to expand...
Click to collapse
ganeshp,
Without modifying android-info.txt (just running the RUU_Pyramid_BM_1.45.666.5_Radio_10.56.9035.00U_10.14.9035.01_M_release_220007_signed.exe), I am getting "ERROR [130]: MODEL ID ERROR. This is expected as my MID (modelID is incorrect. My phone is at PG5810000 when RUU expects PG5811000).
When I modify the android-info.txt in ROM.zip to have my correct MID, it goes a little bit further down the process. However, I am getting "ERROR [132]: SIGNATURE ERROR". Below is the related content of ruu_log.txt:
<T084503><DEBUG><CMD>fastboot -s SH16KV601188 flash zip "C:\Documents and Settings\fred\Local Settings\Temp\{A20F8D10-D7EB-4B01-91D2-68167E319F81}\{50F2F878-636A-496F-A7CB-544C067E0C4B}\rom.zip"</CMD>
</DEBUG></T084503>
<T084609><DEBUG><OUT>sending 'zip' (416943 KB)... OKAY</OUT>
</DEBUG></T084609>
<T084609><DEBUG><OUT>writing 'zip'... INFOsignature checking...</OUT>
</DEBUG></T084609>
<T084722><DEBUG><OUT>FAILED (remote: 12 signature verify fail)</OUT>
</DEBUG></T084722>
This is also expected as someone already pointed out earlier in this thread that ROM.zip cannot be modified because of different MD5 checksum. On this point, I am wondering if there would be some tool to re-generate a correct MD5 checksum.
Fred

fdavidson said:
ganeshp,
Without modifying android-info.txt (just running the RUU_Pyramid_BM_1.45.666.5_Radio_10.56.9035.00U_10.14.9035.01_M_release_220007_signed.exe), I am getting "ERROR [130]: MODEL ID ERROR. This is expected as my MID (modelID is incorrect. My phone is at PG5810000 when RUU expects PG5811000).
When I modify the android-info.txt in ROM.zip to have my correct MID, it goes a little bit further down the process. However, I am getting "ERROR [132]: SIGNATURE ERROR". Below is the related content of ruu_log.txt:
<T084503><DEBUG><CMD>fastboot -s SH16KV601188 flash zip "C:\Documents and Settings\fred\Local Settings\Temp\{A20F8D10-D7EB-4B01-91D2-68167E319F81}\{50F2F878-636A-496F-A7CB-544C067E0C4B}\rom.zip"</CMD>
</DEBUG></T084503>
<T084609><DEBUG><OUT>sending 'zip' (416943 KB)... OKAY</OUT>
</DEBUG></T084609>
<T084609><DEBUG><OUT>writing 'zip'... INFOsignature checking...</OUT>
</DEBUG></T084609>
<T084722><DEBUG><OUT>FAILED (remote: 12 signature verify fail)</OUT>
</DEBUG></T084722>
This is also expected as someone already pointed out earlier in this thread that ROM.zip cannot be modified because of different MD5 checksum. On this point, I am wondering if there would be some tool to re-generate a correct MD5 checksum.
Fred
Click to expand...
Click to collapse
ok RUU way is closed for you then
now if you can unlock your bootloader ..things can be better for you
try HTC-DEV unlock ...once done ..you need to flash a custom GB rom from recovery

ganeshp said:
ok RUU way is closed for you then
now if you can unlock your bootloader ..things can be better for you
try HTC-DEV unlock ...once done ..you need to flash a custom GB rom from recovery
Click to expand...
Click to collapse
I'm getting stuck at step 8 of HTC-Dev unlock. When I issue the command "fastboot oem get_identifier_token", I get back "INFO[ERR] Command error !!!". Maybe this oem command doesn't work with my bootloader (1.17.0008).
Fred

fdavidson said:
I'm getting stuck at step 8 of HTC-Dev unlock. When I issue the command "fastboot oem get_identifier_token", I get back "INFO[ERR] Command error !!!". Maybe this oem command doesn't work with my bootloader (1.17.0008).
Fred
Click to expand...
Click to collapse
no man with that hboot version you don't need htc dev unlock.use this site to S-OFF your device
http://revolutionary.io/
edit: i just read your first post
so you can not use revolutionary

fdavidson said:
I'm getting stuck at step 8 of HTC-Dev unlock. When I issue the command "fastboot oem get_identifier_token", I get back "INFO[ERR] Command error !!!". Maybe this oem command doesn't work with my bootloader (1.17.0008).
Fred
Click to expand...
Click to collapse
ahh even that got stuck huh ...try revolutionary again ..with phone boot-looping or when stuck at splash screen ..if revolutionary finds the device all good ..otherwise all doors closed
rzr86 said:
no man with that hboot version you don't need htc dev unlock.use this site to S-OFF your device
http://revolutionary.io/
Click to expand...
Click to collapse
he tried revolutionary already ..and he currently didnt have a booting rom ..so it might not work

rzr86 said:
no man with that hboot version you don't need htc dev unlock.use this site to S-OFF your device
http://revolutionary.io/
Click to expand...
Click to collapse
That was my original attempt but it looks like revolutionary expects the phone to be fully booted so it can set it himself in bootloader/fastboot through adb command. Since I can get into fastboot myself, If I could skip that part from revolutionary and have it do the next steps, I think I'd get a successful S-OFF. Any idea on how to do that?
Fred

wait if revolutionary wants a working adb then we will give it an adb
do this
get the recovery.img from this link (extract it)
copy it to fastboot
and try this command
fastboot boot recovery.img
if it booted ..then run revolutionary

ganeshp said:
wait if revolutionary wants a working adb then we will give it an adb
do this
get the recovery.img from this link (extract it)
copy it to fastboot
and try this command
fastboot boot recovery.img
if it booted ..then run revolutionary
Click to expand...
Click to collapse
I am getting:
downloading 'boot.img'... OKAY [ 1.706s]
booting... FAILED (remote: not allowed)
Is it because I am S-ON? I seem to remember that S-ON will not allow me to write to some partitions. I hope I'm wrong.

fdavidson said:
I am getting:
downloading 'boot.img'... OKAY [ 1.706s]
booting... FAILED (remote: not allowed)
Is it because I am S-ON? I seem to remember that S-ON will not allow me to write to some partitions. I hope I'm wrong.
Click to expand...
Click to collapse
we are not writing but we are trying to read ..
but is the command you typed is
fastboot boot recovery.img ? (coz in the output its saying downloading boot.img )

ganeshp said:
we are not writing but we are trying to read ..
but is the command you typed is
fastboot boot recovery.img ? (coz in the output its saying downloading boot.img )
Click to expand...
Click to collapse
Yes, my mistake. I sent the same command (fastboot boot recovery.img), so the problem is with reading as you said.

fdavidson said:
Yes, my mistake. I sent the same command (fastboot boot recovery.img), so the problem is with reading as you said.
Click to expand...
Click to collapse
then im out of ideas
one last try
try changing cid
fastboot oem writecid HTC__001
then
fastboot reboot-bootloader
then verify it
fastboot getvar cid
EDIT: if this worked then ..immediately flash the european unbranded 3.33 rom

[Q]Bootloader downgrade?flashing firmware(FAILED (remote: 99 unknown fail)),MaximusHD

Hello,
I get an Error when i try to flash the firmware.zip for MaximusHD
Code:
sending 'zip' (36985 KB)...
OKAY [ 2.699s]
writing 'zip'...
(bootloader) zip header checking.
(bootloader) zip info parsing...
FAILED (remote: 99 unknown fail)
finished. total time: 8.146s
I figured out it may relyto my bootloader.
I'm currently on HBoot 1.14.0002,so i guess its bootloader 2.31
S-ON and unlocked
I read it worked on 2.16, so how do i downgrade.
I really dont want to mess up my bootloader, so i better ask for some advice here
I found this Thread
http://forum.xda-developers.com/showthread.php?t=1990043
But i'm not sure if i took the JB OTA(Had an JB based Rom before)

You gotta be s-off and unlocked and do the commands one by one in command promt. First time it will give u an error...re-do the command right away and it should work.
Also as an advise read the instruction carefully at least 3 times so u undestand what u doing.

So i have to follow this guide
http://forum.xda-developers.com/showthread.php?t=2155135
Read it before, but couldn't figure out if it will help me.
Thanks so far.

Try this one.
http://forum.xda-developers.com/showthread.php?t=2325590
And don't worry about bricking the phone, it's almost imposible. As long as you can go into bootloader you can bring it back to life. I've done it many times.
Also I'm using unknown 2.0 becuase maximus 10 gave me too many problems. I recomend you to use the same as me is basically the same.

Well already got superCID and did everything the guide told me.
Was a bit confused about SuperCID since it didnt sayed CW_001 or something similar.
Could now flash the firmware.zip.
Only messed up my sdcard but i saw that one coming
Thank you very much!

jenenser83 said:
Try this one.
http://forum.xda-developers.com/showthread.php?t=2325590
And don't worry about bricking the phone, it's almost imposible. As long as you can go into bootloader you can bring it back to life. I've done it many times.
Also I'm using unknown 2.0 becuase maximus 10 gave me too many problems. I recomend you to use the same as me is basically the same.
Click to expand...
Click to collapse
Hi Jenenser, I'm on Maximus, Hboot 2.16, s-off, unlocked. I'm trying to get back to Unknown 2.0 because I find Maximus to be too buggy as well. I can't seem to flash anything from fastboot (not recovery, not firmware, can't run RUU, nothing seems to take). How did you get back to Unknown?
Thanks!

Go back to complete stock or RUU than repeat the while unlocking process again.
Unlock bootloader, root the phone, install recovery and then from twrp recover install ROM.

[Q] Bootloop and can't find the RUU file!!

Hi everyone
I have this htc sensation it is stack in bootllop and I don't know why!! anyway I tried to fix it with a RUU file but can't find the correct file to my phone.
I belive it is a T-Mobile phone from NL and here the info from my bootloader
**** LOCKED ****
PYRAMID PVT SHIP S-ON RL
HBOOT-1.27.0000
eMMC-boot
jan 13 2012,17:33:34
Click to expand...
Click to collapse
also I got this by cheking my version and CID
fastboot getvar cid
cid: T-MOB003
finished. total time: 0.002s
Click to expand...
Click to collapse
fastboot getvar version-main
version-main: 3.33.114.51
finished. total time: 0.003s
Click to expand...
Click to collapse
If anyone can help me with the link to the correct RUU file it would be nice
thanks guys

if you still can't find your RUU...you can try another RUU (different CID) that have a same or higher version than yours...but ofcourse you must modified first android-info.txt in that rom.zip file..you can follow completed guide from here.. especially read at step 4. Flashing RUU manually
or alternative way..you must make a goldcard..
hope this help...

JJeamy said:
if you still can't find your RUU...you can try another RUU (different CID) that have a same or higher version than yours...but ofcourse you must modified first android-info.txt in that rom.zip file..you can follow completed guide from here.. especially read at step 4. Flashing RUU manually
or alternative way..you must make a goldcard..
hope this help...
Click to expand...
Click to collapse
thanks but how to modify the android-info.txt I add my CID like this :
modelid: PG5813000cidnum: T-MOB003mainver: 3.33.709.6hbootpreupdate:12DelCache:1
Click to expand...
Click to collapse
it does not flash

Topol-Ms said:
thanks but how to modify the android-info.txt I add my CID like this :
it does not flash
Click to expand...
Click to collapse
yap..that's correct...but..what's your MID anyway..?
how do you to change that...did you already extracted the rom.zip file then modified that android-info.txt file..?
because you don't need to extract that rom.zip (because if you extracting that file first that will broken a compiled that rom.zip)...just open it that archive then open it android-info.txt from there..then edited that file and save it
also try open it and edited that file with notepad++..
hope this help..

JJeamy said:
yap..that's correct...but..what's your MID anyway..?
how do you to change that...did you already extracted the rom.zip file then modified that android-info.txt file..?
because you don't need to extract that rom.zip (because if you extracting that file first that will broken a compiled that rom.zip)...just open it that archive then open it android-info.txt from there..then edited that file and save it
also try open it and edited that file with notepad++..
hope this help..
Click to expand...
Click to collapse
sry what what you mean with MID? and the winrare says the file is curopted I can't cahnge it

Topol-Ms said:
sry what what you mean with MID? and the winrare says the file is curopted I can't cahnge it
Click to expand...
Click to collapse
MID = model id ...to know that just using command "fastboot getvar mid" or "fastboot getvar all"
just try open it that archive with Windows Archive Manager (Windows built in ZIP program), then copied android-info.txt to outside (don't extracted) then edited with nopad++ then save it...then deleted original android-info.txt from that archive then drag and drop the new one to that archive..

JJeamy said:
MID = model id ...to know that just using command "fastboot getvar mid" or "fastboot getvar all"
just try open it that archive with Windows Archive Manager (Windows built in ZIP program), then copied android-info.txt to outside (don't extracted) then edited with nopad++ then save it...then deleted original android-info.txt from that archive then drag and drop the new one to that archive..
Click to expand...
Click to collapse
He's already posted it:
modelid: PG5813000cidnum: T-MOB003mainver: 3.33.709.6hbootpreupdate:12DelCache:1
Click to expand...
Click to collapse
FYI, you can't flash unsigned or missing-cid firmware without S-OFF.
Try these:
http://www.tsar3000.com/Joomla/inde...riginal-roms&catid=65:htc-downloads&Itemid=98
http://www.shipped-roms.com/index.php?category=android&model=Pyramid
Use this thread to look for an RUU. Nearly all RUUs are present on above two links. Your CID is included, so I guess an RUU should be available.

Far_SighT said:
He's already posted it:
FYI, you can't flash unsigned or missing-cid firmware without S-OFF.
Try these:
http://www.tsar3000.com/Joomla/inde...riginal-roms&catid=65:htc-downloads&Itemid=98
http://www.shipped-roms.com/index.php?category=android&model=Pyramid
Use this thread to look for an RUU. Nearly all RUUs are present on above two links. Your CID is included, so I guess an RUU should be available.
Click to expand...
Click to collapse
1. what he's already posted it is android-info.txt from ruu that he want changed it..not MID from the phone that he has..that's why i ask him to see his mid and changed it too to android-info.txt from that RUU..
thanks but how to modify the android-info.txt I add my CID like this :
modelid: PG5813000cidnum: T-MOB003mainver: 3.33.709.6hbootpreupdate:12DelCache:1
Click to expand...
Click to collapse
Click to expand...
Click to collapse
2. he can't find the right RUU for his phone...so that's why i suggest it to him to flashing another RUU and try change it cid and mid in android-info.txt from that other RUU to match with his phone..
3. you can see that i've already suggest it him to the same link thread about related RUU that you give it again to him too..
JJeamy said:
if you still can't find your RUU...you can try another RUU (different CID) that have a same or higher version than yours...but ofcourse you must modified first android-info.txt in that rom.zip file..you can follow completed guide from here.. especially read at step 4. Flashing RUU manually
hope this help...
Click to expand...
Click to collapse
4. so you're already guessing that the right RUU for his phone is available from the two link that you're give it to him above...so can you show me and posting it in here exactly the link for that RUU (i mean the correct RUU that have CID and MID that are suitable for his phone and have equal or higher version than he was had right now)..ofcourse this is for helped him..then make an more easy and a simple way to fix his sensation..
so for @Topol-Ms if that's RUU way fail..maybe you can try it a way to unlocking your bootloader first via htcdev.com.. then after that you can continued to flashing custom recovery..then flashing custom rom..
hope this help...and good luck..

JJeamy said:
1. what he's already posted it is android-info.txt from ruu that he want changed it..not MID from the phone that he has..that's why i ask him to see his mid and changed it too to android-info.txt from that RUU..
2. he can't find the right RUU for his phone...so that's why i suggest it to him to flashing another RUU and try change it cid and mid in android-info.txt from that other RUU to match with his phone..
3. you can see that i've already suggest it him to the same link thread about related RUU that you give it again to him too..
4. so you're already guessing that the right RUU for his phone is available from the two link that you're give it to him above...so can you show me and posting it in here exactly the link for that RUU (i mean the correct RUU that have CID and MID that are suitable for his phone and have equal or higher version than he was had right now)..ofcourse this is for helped him..then make an more easy and a simple way to fix his sensation..
so for @Topol-Ms if that's RUU way fail..maybe you can try it a way to unlocking your bootloader first via htcdev.com.. then after that you can continued to flashing custom recovery..then flashing custom rom..
hope this help...and good luck..
Click to expand...
Click to collapse
thanks man I tried to unlock my phone with htcdev.com everything go smooth untill I get the email with unlock_code.bin and when I try to flash it it says this :
C:\Users\Naoufel\Desktop\fastboot-win>fastboot flash unlocktoken Unlock_code.bin
sending 'unlocktoken' (0 KB)...
OKAY [ 0.151s]
writing 'unlocktoken'...
FAILED (remote: unlock token check failed)
finished. total time: 0.157s
Click to expand...
Click to collapse
I hate this phone!!

Topol-Ms said:
thanks man I tried to unlock my phone with htcdev.com everything go smooth untill I get the email with unlock_code.bin and when I try to flash it it says this :
I hate this phone!!
Click to expand...
Click to collapse
what you choice while in the list of "select your device" to unlock in the first gate in htcdev.com..?
that you already choice "All Other Supported Models" ..?

JJeamy said:
what you choice while in the list of "select your device" to unlock in the first gate in htcdev.com..?
that you already choice "All Other Supported Models" ..?
Click to expand...
Click to collapse
I tried 3 kind of sensation phones in the list and also all other supported models but nothing everytime I get the same message

Topol-Ms said:
I tried 3 kind of sensation phones in the list and also all other supported models but nothing everytime I get the same message
Click to expand...
Click to collapse
did you already tried...i think maybe you can try it if don't..just try factory reset from bootloader first..let me know what happen..

JJeamy said:
did you already tried...i think maybe you can try it..just try factory reset from bootloader first..let me know what happen..
Click to expand...
Click to collapse
factory reset and then I unlock again?

Topol-Ms said:
factory reset and then I unlock again?
Click to expand...
Click to collapse
yap..but after factory reset...just try it to boot normal first..who knows that's will worked..
if not...just continued to flashing unlock token again..but this time just using Unlock_code.bin that you get it from selected "All Others Supported Models"

JJeamy said:
yap..but after factory reset...just try it to boot normal first..who knows that's will worked..
if not...just continued to flashing unlock token again..but this time just using Unlock_code.bin that you get it from selected "All Others Supported Models"
Click to expand...
Click to collapse
sorry dude done all nothing happen same error

Topol-Ms said:
sorry dude done all nothing happen same error
Click to expand...
Click to collapse
this is mean a factory reset way is worked and your phone is already back to normal again..?, or this mean the phone still bootlop and still can't flashing Unlock_code.bin too..?

JJeamy said:
this is mean a factory reset way is worked and your phone is already back to normal again..?
Click to expand...
Click to collapse
I don't think the factory reset was complete it doesn't take much time it was fast the phone is still in boot loop

Topol-Ms said:
I don't think the factory reset was complete it doesn't take much time it was fast the phone is still in boot loop
Click to expand...
Click to collapse
OMG...
so after that did you already tried to flashing Unlock_code.bin again..?

JJeamy said:
OMG...
so after that did you already tried to flashing Unlock_code.bin again..?
Click to expand...
Click to collapse
yes!!

Topol-Ms said:
yes!!
Click to expand...
Click to collapse
this is so weird...
because what i know...if sensation can't unlock bootloader almost all the reason is because that phone is ever get to the service center before for replacing some hardware..especially is the display hw because already broken..did you sure your sensation never replacing some hw broken before..?
sorry mate..i can't help you more than this..i think the only way is just brought your sensation to the service center..or 3rd party service center that had some kind of riff box or jtag tools that can flashing a emmc from the beginning again...

Problem need help

My htc u11 is just relock, then when it back factory reset ask me for password, but they touchpal force close
I can't enter password
I can't enter twrp because relock
I was trying to flash ruu over download mode but always said FAIL19 RU_MAIN_VER_FAIL os-version in android-info missing or i
My HTC U11 is 2PZC10
CID is HTC__39

zeropop2018 said:
My htc u11 is just relock, then when it back factory reset ask me for password, but they touchpal force close
I can't enter password
I can't enter twrp because relock
I was trying to flash ruu over download mode but always said FAIL19 RU_MAIN_VER_FAIL os-version in android-info missing or i
My HTC U11 is 2PZC10
CID is HTC__39
Click to expand...
Click to collapse
I also S-ON
I try flash ruu all version i can, but return error:
19_RU_MAIN_VER_FAIL
Please help

are you try with fastboot commands using windows prompt?
all ruu for htc u11 ------>https://docs.google.com/spreadsheets/d/15JL3tRWDSVOUKo_revEYtQ_tRcOSJ0vWcvk8a7TK8Hk/edit#gid=0

Yes, i try
fastboot rebootRUU
then
htc_fastboot flash zip "firmware_xxx.zip"
it always give me error:
htc_fastboot v3.0.9.2 (2015-05-29)
target rom version: 2.47.1405.2
found large-zip header, file count: 23
processing file 1/23...
sending 'zip' (391927 KB)...
OKAY [ 15.204s]
writing 'zip'...
(bootloader) HOSD CL#1002308
(bootloader) ERR Model ID not matched
(bootloader) ERR [SD_UPDATE_ERR] MODEL ID NOT ALLOWED
(bootloader) ERR [SD_UPDATE_ERR] sddownload failed: 10
(bootloader) ERR Update zip file failed.
(bootloader) ERR ZIP signature checking failed...
(bootloader) Update zip file OK
(bootloader) ERR ZIP ERROR CODE, 10
(bootloader) [email protected]
FAILED (remote: 10 RU_MODELID_FAIL modelid in android-info mismatched )
finished. total time: 23.238s
htc_fastboot finished. total time: 28.075s
I don't know what to do know, anyway my firmware version is: 2.33.710.9

fabrizio b92 said:
are you try with fastboot commands using windows prompt?
all ruu for htc u11 ------>https://docs.google.com/spreadsheets/d/15JL3tRWDSVOUKo_revEYtQ_tRcOSJ0vWcvk8a7TK8Hk/edit#gid=0
Click to expand...
Click to collapse
Which version is right ?

zeropop2018 said:
Which version is right ?
Click to expand...
Click to collapse
where do you live? single or dual sim? is it brand or is it free sim?
can you reboot in fastboot mode? here you can find all information
for example my phone codename is ocndugl = DUGL DUAL SIM EMEA
this is my htc u11 fastboot----- >https://drive.google.com/file/d/19g5JiOs72VV_GKjh9f7b51B6cUN0TtKW/view?usp=sharing
Or if you can reinstall twrp recovery, you can bypass pin screen
Follow this instruction ------> https://forums.oneplus.com/threads/fix-wrong-pin-pattern-when-restoring-twrp-nandroid-backup.452384/

fabrizio b92 said:
where do you live? single or dual sim? is it brand or is it free sim?
can you reboot in fastboot mode? here you can find all information
for example my phone codename is ocndugl = DUGL DUAL SIM EMEA
this is my htc u11 fastboot----- >https://drive.google.com/file/d/19g5JiOs72VV_GKjh9f7b51B6cUN0TtKW/view?usp=sharing
Or if you can reinstall twrp recovery, you can bypass pin screen
Follow this instruction ------> https://forums.oneplus.com/threads/fix-wrong-pin-pattern-when-restoring-twrp-nandroid-backup.452384/
Click to expand...
Click to collapse
I live in Viet Nam. Single. Freesim i think so.
I can reboot in fastboot mode, but i cannot flash RUU, because all error.
My fastboot mode the same as you without RELOCKED, because i relocked it.
That's why i can't find way to reinstall twrp recovery.

Can somebody help ?
Is it brick and never go back ?

zeropop2018 said:
Can somebody help ?
Is it brick and never go back ?
Click to expand...
Click to collapse
Try to unlock bootloader and install twrp recovery to unbrick your phone for now

fabrizio b92 said:
Try to unlock bootloader and install twrp recovery to unbrick your phone for now
Click to expand...
Click to collapse
How to unlock if i can't go to usb debug ?

To sum it up, he
1. somehow tinkered with his phone when unlocked
2. relocked bootloader before restoring a stock pristine system
3. is now soft bricked cause he needs to RUU which isn't available as of yet, and we don't know if it'll get leaked
4. he can't boot to OS to re-unlock, S-OFF to downgrade, due to the above mentioned problems.
We're out of options here for the time being. Only one who might currently be able to restore the device might be HTC Support. But that may cost him, as they'll see that the device has been tinkered with.
Sent from my HTC U12+ using XDA Labs

zeropop2018 said:
How to unlock if i can't go to usb debug ?
Click to expand...
Click to collapse
If you have saved the unlock token from the first time you unlocked the phone, you can use this token again!
Simply flash unlock_code.bin with the command:
fastboot flash unlocktoken Unlock_code.bin

scotty2000 said:
If you have saved the unlock token from the first time you unlocked the phone, you can use this token again!
Simply flash unlock_code.bin with the command:
fastboot flash unlocktoken Unlock_code.bin
Click to expand...
Click to collapse
I'm not the one who unlock it so i can't find it ....
Why it so hard

like a genius got too far into the tinkering and have done same. S-On so cannot change CID and re-locked so wont let me get into TWRP. Still have unlock bin but no joy as when I flashed custom it would have reset oem unlock to off so i get following:
(bootloader) flash unlocktoken
(bootloader) [KillSwitch] : /dev/block/bootdevice/by-name/frp
(bootloader) [KillSwitch] Last Byte is 0X00, disable unlock
(bootloader) [KillSwitch] oem unlock Turn Off!
Obviously can't get back into Android to enable said unlock so seemingly out of options unless there is a way to flip that byte.
---------- Post added at 03:26 PM ---------- Previous post was at 03:23 PM ----------
ngodber said:
like a genius got too far into the tinkering and have done same. S-On so cannot change CID and re-locked so wont let me get into TWRP. Still have unlock bin but no joy as when I flashed custom it would have reset oem unlock to off so i get following:
(bootloader) flash unlocktoken
(bootloader) [KillSwitch] : /dev/block/bootdevice/by-name/frp
(bootloader) [KillSwitch] Last Byte is 0X00, disable unlock
(bootloader) [KillSwitch] oem unlock Turn Off!
Obviously can't get back into Android to enable said unlock so seemingly out of options unless there is a way to flip that byte.
Click to expand...
Click to collapse
Also device is Telstra and there is apparently not a single Telstra (Australia) RUU for U11 on face of earth.
---------- Post added at 03:54 PM ---------- Previous post was at 03:26 PM ----------
I do have a second Telstra U11 device around the house. Is there a way to image from that device to this one?

The problem is obvious. It's a Chinese phone. The firmware currently loaded is Chinese and you're trying to flash a Taiwanese firmware on a multi region cid.
My guess is that the phone has been messed with.
If flashing the same version firmware as what is on it now (2.47.1405.2) fails you will need to get the mid to check it matches the cid for region. If not you have problems ahead.

shivadow said:
The problem is obvious. It's a Chinese phone. The firmware currently loaded is Chinese and you're trying to flash a Taiwanese firmware on a multi region cid.
My guess is that the phone has been messed with.
If flashing the same version firmware as what is on it now (2.47.1405.2) fails you will need to get the mid to check it matches the cid for region. If not you have problems ahead.
Click to expand...
Click to collapse
Thank God i fixed my phone, i gave it to a friend and he had tool to s-off ...
Thank God

zeropop2018 said:
Thank God i fixed my phone, i gave it to a friend and he had tool to s-off ...
Thank God
Click to expand...
Click to collapse
So do you know what "tool" he had that fixed your phone?
Sent from my coconut frond hut using Tapatalk

mauiblue said:
So do you know what "tool" he had that fixed your phone?
Sent from my coconut frond hut using Tapatalk
Click to expand...
Click to collapse
He said that tool use to connect to china server

zeropop2018 said:
Thank God i fixed my phone, i gave it to a friend and he had tool to s-off ...
Thank God
Click to expand...
Click to collapse
Can I ask what that tool was? And where did he get it? . Also when he went s- off what did he do to fix it? Just curious as I have been following this thread . Thanks

Cool. Maybe I could could have connected to this "tool" and fixed my U11 [emoji20][emoji22]. I also "relocked" my phone and couldn't find figure out how to fix it. I had to send my phone to the HTC repair shop a couple weeks ago. Still waiting for a positive response from them.
Sent from my coconut frond hut using Tapatalk