Related
stuck in bootloop.
hboot info:
*** TAMPERED ***
*** UNLOCKED ***
VLE PVT SHIP S-ON RL
HBOOT-1.14.0002
RADIO-1.06es.50.02.31
OpenDSP-v29.1.0.45.0622
eMMC-BOOT
Jun 11 2012, 14:36:28
cid is HTC__001
was on stock god knows which rom, left phone on overnight, woke up in the morning and phone was off. turned it on and it's stuck in bootloop. so i thought if i could root the phone, I could install a rom through CWM. unlocked the bootloader via htcdev, fastboot flashed CWM, tried booting into CWM and it just boot loops. i then ran out of the little amount of battery i had left, and couldn't charge the phone because of bootloop. so flashed stock recovery to get phone to charge. relocked the bootloader and tried flashing "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", flashed successfully but still bootloop. tried flashing an older version, RUU_Ville_U_HTC_Europe_1.47.401.1_Radio_0.15.31501S.13_3_10.08.31501S.04L_release_250115_signed, didn't flash due to older hboot.
unlocked bootloader again and tried HTC One S AIO Kit by Hasoon, flashed CWM and still stuck in bootloop. flashed TWRP and also stuck in bootloop. running out of ideas here
at the moment, I still have access to bootloader. anyone have any ideas?
thanks in advance
but can u go into the bootloader mode ???
acerulz said:
but can u go into the bootloader mode ???
Click to expand...
Click to collapse
thanks for replying so quick!
not really good with my terms. i'm guessing bootloader mode is vol dn + power?, yes i can get into that. and i can see device in fastboot aswell when i type "fastboot devices"
so simply your phone is not bricked mate, read the posts and you'll get to it very quickly.
Wish u luck
drakexpl said:
so simply your phone is not bricked mate, read the posts and you'll get to it very quickly.
Wish u luck
Click to expand...
Click to collapse
ok that's a relief. can you direct me to which post? i've read through soo many and tried soo much but always failed
kid_maximus said:
ok that's a relief. can you direct me to which post? i've read through soo many and tried soo much but always failed
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1599363
in fastboot, either reflash recovery or erase cache
thanks for the replies :good:
fastboot erase cache doesn't look like it did anything, still bootloops
i tried flashing the CWM recovery i had again via fastboot, didn't work, still bootloops when i try accessing recovery. grabbed the CWM and TWRP recovery images from HTC AIO kit, tried flashing them with fastboot, still nothing stuck in bootloop.
although once i did flash the recovery image, the htc logo screen changed in that there is now red writing underneath it:
"This build is for development purposes only. Do not distribute outside of HTC without HTC's written permission. Failure to comply may lead to legal action", after a minute, the screen goes off for 5 seconds and comes back with standard htc logo and bootloops.
any other ideas? :crying:
thanks again.
Lock bootloader and flash ruu most simple for beginners
Sent from a man, using a mobile phone
k1llacanon said:
Lock bootloader and flash ruu most simple for beginners
Sent from a man, using a mobile phone
Click to expand...
Click to collapse
Thats a little overkill IMO
You should be able to
fastboot flash recovery pathtoyourtwrprecovery.img
boot into recovery factory reset install a rom
reboot
and you should be ok
k1llacanon said:
Lock bootloader and flash ruu most simple for beginners
Sent from a man, using a mobile phone
Click to expand...
Click to collapse
tried that many times, but i'll try again and write what happens
i've done fastboot oem lock, it says:
(bootloader) Lock successfully...
(bootloader) TZ_HTC_SVC_DISABLE ret = 534642040 (0x1FDDFD78)
FAILED (status read failed (Too many links))
finished. total time: 0.942s
i'm guessing that's right because it's gone from "unlocked" to "relocked" in bootloader, including "security warning" added underneath it.
(erased the cache next using fastboot)
ran the RUU, completed successfully, no errors...phone rebooted, still bootloops
can still access bootloader
ran the RUU again, this time as administrator...completed successfully, no errors...phone rebooted, still bootloops
still have access to bootloader and working fastboot.
there must be some way to fix this
Zarboz said:
Thats a little overkill IMO
You should be able to
fastboot flash recovery pathtoyourtwrprecovery.img
boot into recovery factory reset install a rom
reboot
and you should be ok
Click to expand...
Click to collapse
you are sooo right, if only i could access recovery, i know what to do
but the problem is, i can't...i've tried atleast 15 times if not more to flash as you said using fastboot, cwm twrp and stock recoveries, using many files (to rule out having a corrupted recovery img) and using the HTC AIO kit too to flash recovery, always bootloops
as i said, i tried to fastboot flash the recoveries provided with the HTC AIO kit, this also bootloops.
do you have any other ideas? i'd appreciate anything rather than using this as a paperweight lol
The situation:
No OS, no recovery, and no mountable SD card. Bootloader unlocked and rooted. Currently Relocked.
What I've tried:
"One X ATT All in one kit" gives me this error: (remote: 92 supercid! please flush image again immediately) when doing recovery.
"fastboot boot recovery.img" gives me: FAILED (remote: not allowed)
"fastboot flash recovery recovery.img" gives me INFOsignature checking... FAILED (remote: signature verify fail)
Running the RUU.exe doesnt give me any errors but doesn't work.
When unlocked
"fastboot boot recovery.img" i get: FAILED (remote: reproduce boot image with on-flash ramdisk error)
EDIT: TWRP gives me a black screen.
so what can i do the fix this?
Thanks.
shadyboy039 said:
The situation:
No OS, no recovery, and no mountable SD card. Bootloader unlocked and rooted. Currently Relocked.
What I've tried:
"One X ATT All in one kit" gives me this error: (remote: 92 supercid! please flush image again immediately) when doing recovery.
"fastboot boot recovery.img" gives me: FAILED (remote: not allowed)
"fastboot flash recovery recovery.img" gives me INFOsignature checking... FAILED (remote: signature verify fail)
Running the RUU.exe doesnt give me any errors but doesn't work.
When unlocked
"fastboot boot recovery.img" i get: FAILED (remote: reproduce boot image with on-flash ramdisk error)
EDIT: TWRP gives me a black screen.
so what can i do the fix this?
Thanks.
Click to expand...
Click to collapse
Try to flash RUU Att 2.20
http://dl3.htc.com/application/htc_one_x_RUU_2.20.502.7_att_us_08022012.exe
Sent from my HTC One XL
shadyboy039 said:
The situation:
No OS, no recovery, and no mountable SD card. Bootloader unlocked and rooted. Currently Relocked.
Click to expand...
Click to collapse
How did you get to this point, exactly?
Do you see the device, if you adb the command:
adb devices
If you did a factory reset in bootloader, it corrupted the SD card, which may be why it won't mount. Connect the phone to your PC via USB, and open Device Manager, and see if it shows up. If you have the option to format it, do so as FAT32.
shadyboy039 said:
The situation:
No OS, no recovery, and no mountable SD card. Bootloader unlocked and rooted. Currently Relocked.
What I've tried:
"One X ATT All in one kit" gives me this error: (remote: 92 supercid! please flush image again immediately) when doing recovery.
"fastboot boot recovery.img" gives me: FAILED (remote: not allowed)
"fastboot flash recovery recovery.img" gives me INFOsignature checking... FAILED (remote: signature verify fail)
Running the RUU.exe doesnt give me any errors but doesn't work.
When unlocked
"fastboot boot recovery.img" i get: FAILED (remote: reproduce boot image with on-flash ramdisk error)
EDIT: TWRP gives me a black screen.
so what can i do the fix this?
Thanks.
Click to expand...
Click to collapse
Why did you relock? If you downgraded hboot I do not suggest running the RUU. Unlock bootloader then you can flash twrp recovery then check resources compilation sticky in Android device section for unmountable sd card if still cannot access sd card. Then flash rom. If you did not downgrade hboot you can run your carriers ruu which will bring you back to stock if that is what you were trying to accomplish.
Sent from my One X using xda app-developers app
kaiser347 said:
Try to flash RUU Att 2.20
http://dl3.htc.com/application/htc_one_x_RUU_2.20.502.7_att_us_08022012.exe
Sent from my HTC One XL
Click to expand...
Click to collapse
been using 2.20 RUU
redpoint73 said:
How did you get to this point, exactly?
Do you see the device, if you adb the command:
adb devices
If you did a factory reset in bootloader, it corrupted the SD card, which may be why it won't mount. Connect the phone to your PC via USB, and open Device Manager, and see if it shows up. If you have the option to format it, do so as FAT32.
Click to expand...
Click to collapse
i don't quite understand how i got here. i just kept getting stuck on bootloop even after reflashing to CM10. i only got into twrp once and i've been on loop since.
EDIT: no adb device. and ya the factory reset did screw me over. but after getting loopped even after reflashing twrp, i didnt know what to do.
exad said:
Why did you relock? If you downgraded hboot I do not suggest running the RUU. Unlock bootloader then you can flash twrp recovery then check resources compilation sticky in Android device section for unmountable sd card if still cannot access sd card. Then flash rom. If you did not downgrade hboot you can run your carriers ruu which will bring you back to stock if that is what you were trying to accomplish.
Sent from my One X using xda app-developers app
Click to expand...
Click to collapse
last i checked you cant downgrade from 2.20. but that was way back when x-factor exploit was released, that's way im doing 2.20 RUU.
Sorry I wasn't descriptive enough on that part.
Well, things took a turn for the worst and now i think it's bricked cause of the QHSUSB_dload thing.
Thanks for the replies.
shadyboy039 said:
been using 2.20 RUU
i don't quite understand how i got here. i just kept getting stuck on bootloop even after reflashing to CM10. i only got into twrp once and i've been on loop since.
EDIT: no adb device. and ya the factory reset did screw me over. but after getting loopped even after reflashing twrp, i didnt know what to do.
last i checked you cant downgrade from 2.20. but that was way back when x-factor exploit was released, that's way im doing 2.20 RUU.
Sorry I wasn't descriptive enough on that part.
Well, things took a turn for the worst and now i think it's bricked cause of the QHSUSB_dload thing.
Thanks for the replies.
Click to expand...
Click to collapse
Can you access bootloader? And yes you can downgrade any hboot. But you do risk a possible brick as the hboot downgrade purposefully bricks to downgrade hboot.
Sent from my One X using xda app-developers app
shadyboy039 said:
Well, things took a turn for the worst and now i think it's bricked cause of the QHSUSB_dload thing.
Click to expand...
Click to collapse
Is the PC actually saying "QHSUSB_dload" or not?
What is the current state of the phone? Any charge LED, or screen come on at all?
exad said:
Can you access bootloader? And yes you can downgrade any hboot. But you do risk a possible brick as the hboot downgrade purposefully bricks to downgrade hboot.
Sent from my One X using xda app-developers app
Click to expand...
Click to collapse
No hboot. O that's great I'm currently reading up this thread http://forum.xda-developers.com/showthread.php?t=1966850 . Is this the right thread or is there another one?
redpoint73 said:
Is the PC actually saying "QHSUSB_dload" or not?
What is the current state of the phone? Any charge LED, or screen come on at all?
Click to expand...
Click to collapse
No LED. Computer says "QHSUSB_dload" when it trys to install drivers.
It's not turning on with any button combination.
Edit: None of my computers are detecting it anymore.
To go from a simple fix to where u are at now u must of done something. If you state everything you did it might help us help you better. Hopefully you didnt do anything meant for the htc one x(international).
DvineLord said:
To go from a simple fix to where u are at now u must of done something. If you state everything you did it might help us help you better. Hopefully you didnt do anything meant for the htc one x(international).
Click to expand...
Click to collapse
I made sure to stay away from the international board after I accidentally posted there 6 months ago. So that's not possible. Not sure where I went wrong. Been at this for over 12 hours with it turning on and off. Like I said I just couldn't get out of bootloop when I had hboot. Now that it's not turning on anymore I don't know what to do.
EDIT: It's been about 2 hours now. No LED. Haven't touched it yet and don't plan to for a while longer. But I'm thinking about bring it in and asking for a replacement tomorrow. What are the chances that they'll replace it?
If you plug it up to wall charger does the led come on after awhile, if it was battery was dead it can take 10-15 minutes for led to turn on?
DvineLord said:
If you plug it up to wall charger does the led come on after awhile, if it was battery was dead it can take 10-15 minutes for led to turn on?
Click to expand...
Click to collapse
I've left it for for around 20 minutes and still no dice. I'm gonna try leaving it for a few hours and hope it'll bounce back.
EDIT: It's been about 2 hours now. No LED. Haven't touched it yet and don't plan to for a while longer. But I'm thinking about bring it in and asking for a replacement tomorrow. What are the chances that they'll replace it?
EDIT: Don't know if this means anything but the area under the camera is slightly warmer than the rest of the phone. It's been plugged in and it's been hanging at the edge of the table because i don't like setting it on the camera.
shadyboy039 said:
I've left it for for around 20 minutes and still no dice. I'm gonna try leaving it for a few hours and hope it'll bounce back.
EDIT: It's been about 2 hours now. No LED. Haven't touched it yet and don't plan to for a while longer. But I'm thinking about bring it in and asking for a replacement tomorrow. What are the chances that they'll replace it?
EDIT: Don't know if this means anything but the area under the camera is slightly warmer than the rest of the phone. It's been plugged in and it's been hanging at the edge of the table because i don't like setting it on the camera.
Click to expand...
Click to collapse
sounds like it may be bricked. how did you get to this point? you can try the unbricking thread. if you can catch your emmc partitions you may be able to recover.
here's the link just in case youre unable to find it. http://forum.xda-developers.com/showthread.php?t=1966850
shadyboy039 said:
Computer says "QHSUSB_dload" when it trys to install drivers.
Click to expand...
Click to collapse
You're in Qualcomm download mode. No bootloader, so the phone isn't going to boot by itself. You're screwed. Unless you want to try the unbricking thread using a Linux machine, as previously suggested.
---------- Post added at 01:46 PM ---------- Previous post was at 01:41 PM ----------
shadyboy039 said:
ut I'm thinking about bring it in and asking for a replacement tomorrow. What are the chances that they'll replace it?
Click to expand...
Click to collapse
Warranty covers defects by the manufacturer, not damage done by you. You knew the risks of trying to mod the phone.
My HTC One XL went on low battery and i plugged it on charge. Power outages meant the phone couldn't charge and when power came back on, I plugged it again on charge for about two hours. I tried booting the phone and the phone couldn't start, but the red light kept blinking even though it was unplugged from the charger. I pressed and held the power button for a while and turned it on again. It came on, but could not boot pass the "HTC quietly brilliant" screen, it kept restarting from that screen after it stays on for some seconds.
Next thing i did was to boot into bootloader. The bootloader was initially "Unlocked" but when the bootloader came up, it showed "LOCKED", which means the bootloader has gone back to locked all by itself. I tried unlocking the bootloader again, but when the unlocking warning screen shows up and i select "YES", it restarts and the "HTC quietly brilliant" screen keeps restarting. I tried factory reset from bootloader but the htc screen comes up and restarts from there.
The next thing i did was to look for an RUU. I couldn't find any, as most of the links were down. So i downloaded "RUU_EVITA_UL_ICS_40_S_Cingular_US_2.20.502.7_Radi o_0.19as.32.09.11_2_10.105.32.25L_release_271865_s igned" and I tried flashing from there, but the RUU loader could not load on the phone, could not even restart into the bootloader, as the HTC screen keeps restarting. RUU could not also be loaded from fastboot commands. I tried flashing a new kernel, but the phone doesn't allow the command to push the "boot" image file.
The phone was running on the official T-Mobile 4.2.2 Sense 5 which I updated OTA before unlocking the bootloader, and everything was working just fine, until the phones battery run low and the bootloader went back to locked by itself. Please help, as it seems all options have been exhausted. I have attached a copy of an image of my bootloader. But the details are as follows:
*** LOCKED ***
EVITA PVT SHIP S-ON RL
HBOOT-2.15.0000
RADIO-1.31a.32.45.16_2
OpenDSP-v33.1.0.45.1128
eMMC-boot
Aug 14 2013, 16:02:22:-1
Please help :'(
Running an older RUU (older hboot version) is not possible with S-on.
You also can't run another carrier's RUU unless you are SuperCID.
Also, you can't flash a kernel with a locked bootloader and S-on.
Don't know how your phone got screwed up the way it is. But since you are hboot 2.15 and s-on, you are somewhat stuck (no current RUU, no way to run an older RUU).
redpoint73 said:
Running an older RUU (older hboot version) is not possible with S-on.
You also can't run another carrier's RUU unless you are SuperCID.
Also, you can't flash a kernel with a locked bootloader and S-on.
Don't know how your phone got screwed up the way it is. But since you are hboot 2.15 and s-on, you are somewhat stuck (no current RUU, no way to run an older RUU).
Click to expand...
Click to collapse
Thank you very much. At least, you replied. I don't even know how this is possible. I have tried "fastboot flash unlocktoken Unlock_code.bin" over a million times, still, the bootloader shows "*** LOCKED ***"
I have almost exhausted every option out here. I've spend so many days trying everything possible, but all i get is this locked bootloader.
Economistaterry said:
Thank you very much. At least, you replied. I don't even know how this is possible. I have tried "fastboot flash unlocktoken Unlock_code.bin" over a million times, still, the bootloader shows "*** LOCKED ***"
I have almost exhausted every option out here. I've spend so many days trying everything possible, but all i get is this locked bootloader.
Click to expand...
Click to collapse
Its very odd that it says "LOCKED", as its not supposed to say that after being UNLOCKED, only RELOCKED. Its also not supposed to go back to LOCKED by itself. No technical evidence to think so (just a hunch), but it makes me think that the bootloader has been damaged or corrupted.
redpoint73 said:
Its very odd that it says "LOCKED", as its not supposed to say that after being UNLOCKED, only RELOCKED. Its also not supposed to go back to LOCKED by itself. No technical evidence to think so (just a hunch), but it makes me think that the bootloader has been damaged or corrupted.
Click to expand...
Click to collapse
so can the bootloader be repaired? if yes, how?
Economistaterry said:
so can the bootloader be repaired? if yes, how?
Click to expand...
Click to collapse
Possibly. But since you are s-on, your only option (that I can think of) is an appropriate RUU (equal or higher hboot version). But since no RUU with hboot 2.15 or higher is available, you will have to wait for one to be released.
Don't know what else can be done. You might be stuck.
Flash the original firmware.zip from 5.08 ota with no changes in rebootRUU mode.
Without changes the signature will be correct and same hboot version is allowed.
This should reflash the 2.15 hboot.
redpoint73 said:
Possibly. But since you are s-on, your only option (that I can think of) is an appropriate RUU (equal or higher hboot version). But since no RUU with hboot 2.15 or higher is available, you will have to wait for one to be released.
Don't know what else can be done. You might be stuck.
Click to expand...
Click to collapse
The red light which shows that the battery is charging never turns green. I have left it on charge over night so many times, but green never shows. Then the red light also stays solid for like 6seconds, goes off for like 2 or 3 seconds and comes back on. It never turns solid like it does when it's fully working, even when I leave it on charge for a long time.
twistedddx said:
Flash the original firmware.zip from 5.08 ota with no changes in rebootRUU mode.
Without changes the signature will be correct and same hboot version is allowed.
This should reflash the 2.15 hboot.
Click to expand...
Click to collapse
When ever I give the rebootRUU command, the phone restarts, the black HTC screen never shows.
Have you tried
fastboot erase cache
and then try rebootRUU?
twistedddx said:
Have you tried
fastboot erase cache
and then try rebootRUU?
Click to expand...
Click to collapse
Yes please, I just did that a couple of times. It only reboots the HTC white screen, same problem.
From bootloader, can you flash the recovery image found in the official 5.08 firmware.zip?
Then try rebootRUU?
twistedddx said:
From bootloader, can you flash the recovery image found in the official 5.08 firmware.zip?
Then try rebootRUU?
Click to expand...
Click to collapse
I gave the "fastboot flash recovery recovery.img" command and all i get is "sending 'recovery' (9060 kb) . . ." and nothing happens. The green bar which will show on the bootloader shows, but doesn't load. I have done this a couple of times, same results
twistedddx said:
Flash the original firmware.zip from 5.08 ota with no changes in rebootRUU mode.
Without changes the signature will be correct and same hboot version is allowed.
This should reflash the 2.15 hboot.
Click to expand...
Click to collapse
Its a good idea, and certainly worth a try.
Although it must be remembered that not all the hboot modules were deployed with the 5.08 OTA. Just one of the three modules, I forget.
So to recap(these are more questions then statements):
-phone was upgraded to T-Mobile 5.08 and therefore has all 5.08 firmwares
-your phone can not boot into a ROM.
-your phone can not boot into recovery?
-fastboot works? You tried: fastboot oem readcid and get a response? What response?
-you cleared cache with fastboot erase cache
-flashing recovery fails?
-relock the phone, power cycle then do fastboot oem lock. Even though the phones says locked it might help to reset the lock state manually.
-Unlock token fails? Did you try to get a new token from HTCDev. Old tokens become invalid if your CID changes etc, go get a new one and try again
-RUU fails? You tried 2.20 I know but why not try 3.18 just for fun.
-rebootRUU mode fails? note it is cAsE sEnSiTiVe.
You are quickly running out of options, sending to HTC or independent jtag repair are probably the only way forwards.
If timmaaa and redpoint73 are out of ideas your problems are beyond repair by "XDA Q&A helpdesk support"
twistedddx said:
So to recap(these are more questions then statements):
-phone was upgraded to T-Mobile 5.08 and therefore has all 5.08 firmwares
-your phone can not boot into a ROM.
-your phone can not boot into recovery?
-fastboot works? You tried: fastboot oem readcid and get a response? What response?
-you cleared cache with fastboot erase cache
-flashing recovery fails?
-relock the phone, power cycle then do fastboot oem lock. Even though the phones says locked it might help to reset the lock state manually.
-Unlock token fails? Did you try to get a new token from HTCDev. Old tokens become invalid if your CID changes etc, go get a new one and try again
-RUU fails? You tried 2.20 I know but why not try 3.18 just for fun.
-rebootRUU mode fails? note it is cAsE sEnSiTiVe.
You are quickly running out of options, sending to HTC or independent jtag repair are probably the only way forwards.
If timmaaa and redpoint73 are out of ideas your problems are beyond repair by "XDA Q&A helpdesk support"
Click to expand...
Click to collapse
-yes, 5.08 OTA
-yes, can not boot into a ROM
-yes, can not boot into recovery
-yes, INFOcid: T-MOB101
-yes, can clear cache with fastboot
-yes, flash recovery fails
-fastboot oem lock comes "INFODevice is already locked!"
-yes, unlocktoken fails. Got millions of new tokens from htcdev, all can't unlock, but will try again
-yes, RUU fails, will try the version u mentioned
-yes, rebootRUU fails, and i know its case sensitive
Thanks a lot for your support. Am in Ghana, no htc servive center here, no jtag repair center too.
Another observation I've made.
The red light which shows the battery is charging, never turns green. I left it on charge for almost 24hours. Then the red light which shows a charge also does not stay solid for more than 5 seconds. It goes off, and comes on again, never stays solid red to indicate a charge, like it normally does when it was was fully working. I run fastboot getvar all and the battery status shows good, but sometimes too low.
Again, if I unplug the charger, the red light continues to show, like its still on charge, shows for like 5 seconds, and goes off, and comes back on, never stops.
Can it be that the battery is damaged? And if the battery is damaged, can it be the cause of all these issues?
Economistaterry said:
Another observation I've made.
The red light which shows the battery is charging, never turns green. I left it on charge for almost 24hours. Then the red light which shows a charge also does not stay solid for more than 5 seconds. It goes off, and comes on again, never stays solid red to indicate a charge, like it normally does when it was was fully working. I run fastboot getvar all and the battery status shows good, but sometimes too low.
Again, if I unplug the charger, the red light continues to show, like its still on charge, shows for like 5 seconds, and goes off, and comes back on, never stops.
Can it be that the battery is damaged? And if the battery is damaged, can it be the cause of all these issues?
Click to expand...
Click to collapse
It could be a hardware issue.. But I doubt a hardware issue would mess up your hboot to the point you cant do anything.
You won't be able to flash anything with a locked bootloader. Keep trying to unlock the bootloader. Use the same unlock token, you do not need to re-request new ones everytime. if/when it fails to unlock, press and hold power until the phone shuts off, let go of power, press and hold volume down to go back into bootloader then try again with the same unlockcode bin file. Repeat until it unlocks. It may take many many tries. Press and hold power to hard power off the phone between tries every time.
When you finally do get it to unlock post here and we will fix your hboot issues.
redpoint73 said:
Its a good idea, and certainly worth a try.
Although it must be remembered that not all the hboot modules were deployed with the 5.08 OTA. Just one of the three modules, I forget.
Click to expand...
Click to collapse
twistedddx said:
From bootloader, can you flash the recovery image found in the official 5.08 firmware.zip?
Then try rebootRUU?
Click to expand...
Click to collapse
guys, there has been some slight improvement. Initially, "fastboot flash recovery recovery.img" or "fastboot flash boot boot.img" wasn't giving any reply, but today, i get this from flashing the boot and recovery image in the OTA 5.08 ...
C:\Users\user\Desktop\Fastboot>fastboot flash boot boot.img
sending 'boot' (6052 KB)... OKAY [ 1.182s]
writing 'boot'... INFOsignature checking...
FAILED (remote: signature verify fail)
finished. total time: 1.836s
C:\Users\user\Desktop\Fastboot>fastboot flash recovery recovery.img
sending 'recovery' (9060 KB)... OKAY [ 1.512s]
writing 'recovery'... INFOsignature checking...
FAILED (remote: signature verify fail)
finished. total time: 2.490s
Does it mean anything? Does it mean flashing a different boot.img or recovery.img may work?
Economistaterry said:
guys, there has been some slight improvement. Initially, "fastboot flash recovery recovery.img" or "fastboot flash boot boot.img" wasn't giving any reply, but today, i get this from flashing the boot and recovery image in the OTA 5.08 ...
C:\Users\user\Desktop\Fastboot>fastboot flash boot boot.img
sending 'boot' (6052 KB)... OKAY [ 1.182s]
writing 'boot'... INFOsignature checking...
FAILED (remote: signature verify fail)
finished. total time: 1.836s
C:\Users\user\Desktop\Fastboot>fastboot flash recovery recovery.img
sending 'recovery' (9060 KB)... OKAY [ 1.512s]
writing 'recovery'... INFOsignature checking...
FAILED (remote: signature verify fail)
finished. total time: 2.490s
Does it mean anything? Does it mean flashing a different boot.img or recovery.img may work?
Click to expand...
Click to collapse
absolutely nothing will flash with a locked bootloader. Nothing nothing nothing.
Hello Guys, I need your help.
I got this INSPIRE 4G from a friend. When he gave it to me, he said it needed to be flashed.
The thing is, When you press the power button, it boots straight up into Fastboot.
Here Is my Hboot Info
ACE PVT SHIP S-OFF RL
HBOOT-0.85.0024
MICROP-0438
RADIO-26.09.04.11_M2
Emmc-boot
Apr 12 2011,00:55:45
In Fastboot, i can move around with the volume buttons and power buttons(so that means the phone booting straight into Fastboot isnt a result of one of the volume buttons being stuck.)
When i try to access recovery from the Bootloader, It vibrates 6 to 8 times then the screen becomes black,it stays that way until i do a battery pull.
When i select factory reset from the bootloader, it does nothing.
WHen i select Image CRC from the Bootloader,These is what is printed on the screen.
OSBL: 0xC2C4DD79
AMSS: 0x6CC260EB
HBOOT: 0xF9E06F63
BOOT: 0x0
RECOVERY: 0x0
SYSTEM: 0x0
As the digit are displayed, the first three look okay,but the last three which are BOOT RECOVERY and SYSTEM seem to have no digits, Which kinda looks like its empty.
THESE ARE THE SOLUTIONS I HAVE TRIED.
1. I tried flashing a recovery from Fastboot, but it gives an error like this:
C:\Program Files\Minimal ADB and Fastboot>fastboot devices
HT0BFRX06133 fastboot
C:\Program Files\Minimal ADB and Fastboot>fastboot flash recovery recovery.img
sending 'recovery' (3704 KB)...
OKAY [ 0.664s]
writing 'recovery'...
FAILED (remote: not allowed)
finished. total time: 0.672s
I get the same errors when i try to flash,erase or format the rest of the partitions(BOOT,SYSTEM).
2. I have also tried the HTC RUU, it finds the device and then gets stuck when it tries to boot into Android.
I have also tried the HTC RUU Hboot update but it also fails like the RUU ROm update.
3. I have also tried to flash the STock rom as PD98IMG.zip via bootloader, but when it finds the file, it asks me to press volume up to start update, when i press volume up, it loads the file and when its suppose to flash it, it sort of skips it and move to the next. It does that until its done the asks me to press power to reboot. Since it skips the files it stays the same after reboot.
3.I have Also tried flashing Eng-Hboot as PD98IMG.zip, But it skips that also.
4. I also tried to use this command Fastboot oem boot
And this is what i get:
C:\Program Files\Minimal ADB and Fastboot>Fastboot oem boot
...
(bootloader) Error status=0x400008
(bootloader) [SD_HW_ERR] SD: read fail ..
(bootloader) DATA_TIMEOUT
(bootloader) [SD_HW_ERR] read data fail in CMD17
(bootloader) [SD_HW_ERR] SD: Read data fail..
(bootloader) [ERR] partition_read_emmc(453): error 13
(bootloader) [ERR] boot image does not exist!!!
OKAY [ 1.418s]
finished. total time: 1.418s
I am begining to think that some how the partitions are corrupt or something.
PLEASE HELP ME OUT!!
@krook6023 The reason why i posted there also was because i wasnt sure what device it is wether its a DHD or INSPIRE 4G since it doesnt boot up and is stuck in bootloader,thats why i posted there also.Hope you understand and open the other thread incase someone over there has the answer to my problem.
You are almost on the right track but are doing each step wrong.
1. You are still bootloader locked so no fastboot commands will work.
2. If you want to run the RUU you have to place the phone into. Fastboot mode first. Select fastboot mode and you should see fastboot usb on phone screen and then the RUU will recognize it as long as you have an uncoerupted sd card installed.
3. PD98IMG files need to have the appropriate android-info.txt to run properly.
4. This is obvious as you don't have a boot img.
I would try the RUU method first.
spokanite said:
You are almost on the right track but are doing each step wrong.
1. You are still bootloader locked so no fastboot commands will work.
2. If you want to run the RUU you have to place the phone into. Fastboot mode first. Select fastboot mode and you should see fastboot usb on phone screen and then the RUU will recognize it as long as you have an uncoerupted sd card installed.
3. PD98IMG files need to have the appropriate android-info.txt to run properly.
4. This is obvious as you don't have a boot img.
I would try the RUU method first.
Click to expand...
Click to collapse
Thanks for your reply.But i tried 2. and made sure android-info.txt was appropriate, it just wouldnt flash. Looked like the partitions were corrupt thats why it wouldnt flash.
This is how it usually acts.
It finds the file, Loads the file on the upper right side of the bootloader with a green loading bar, after that, when its time for it to flash, normally shows up in red loading bar. It just moves as if it was flashing a 1kilobyte file. Then asks me to reboot.
After reboot nothing happens. Stays the same way.
But Right now, its even worse. After installing QHSUSB_DLOAD drivers, its refused to boot into bootloader ever since. but shows up as QHSUSB_DLOAD when connected to my pc.
Wait, you're S-Off, so you don't need to unlock. What recovery are you trying to flash?
bananagranola said:
Wait, you're S-Off, so you don't need to unlock. What recovery are you trying to flash?
Click to expand...
Click to collapse
I tried flashing CWM,TWRP,STOCK.... but non of them worked.
But as i said, after installing some drivers i found for QHSUSB_DLOAD, it no longer boots into bootloader.
But when i connect the device to a computer it only shows up as QHSUSB_DLOAD.
Any Help On that?
Nope, no idea. What drivers? From where?
bananagranola said:
Nope, no idea. What drivers? From where?
Click to expand...
Click to collapse
I found it on one of the threads.
at first, when the phone is connected to the pc, the charge light turns on and shows up as QHSUSB_DLOAD, but now no light or bootloader, just QHSUSB_DLOAD
Was it a DHD thread?
bananagranola said:
Was it a DHD thread?
Click to expand...
Click to collapse
Yea i guess so.
After the driver stopped the device from booting into bootloader, i read the README file that came with the driver and found out that it was for Some sort of Qualcomm Modem Device.
I guess thats why it bricked the device.
What thread?
bananagranola said:
What thread?
Click to expand...
Click to collapse
I cant seem to remember what thread it is. Cause I downloaded lost of the drivers from different threads. So I cant tell which one is from which thread.
Yeah, I don't think I can help you then.
Is it actually fully bricked yet? What exactly happen when you power on the device unplugged usb?
Hey Guys! so recently I purchased Sunshine to S-OFF my SPRINT HTC U11. I changed the CID to unlocked version BS_US001 to flash the unlocked RUU. it kept on failing because the bootloader was unlocked. so then I typed the worst command ever "fastboot oem lock" and now my bootloader is locked, device is S ON, and the worst part is that the bootloader comes up saying that the device is corrupted and cannot be trusted. Now I cannot get into twrp, or my rom. because I changed the CID I can't use my original RUU to revert back. Moreover the android OS version in the download mode comes up as 1.28.651.3 and the unlocked RUU which could work is 1.16.617.6 . The unlocked RUU gives me an error that the android versions either missing or set to 1 and the sprint RUU gives me Invalid Customer ID error. I have access to fastboot. I need a way to change the CID back to SPCS_001. I know I should've used superCID but I panicked while doing all the steps. if anyone could give me or provide me with a way to create a sprint rom.zip which is signed and has a modified android-info.txt including the CID for my phone. I cannot unlock my bootloader as it expects bootloader unlocking to be turned on the android system which unfortunately has been factory reset due to the corruption and is no longer booting. if there is a way to S OFF via fastboot then I can recover. please help me. I have good experience with flashing roms and messing with this stuff but I was out of the android scene for 2 years until recently when I got the U11.
kunalrokz said:
Hey Guys! so recently I purchased Sunshine to S-OFF my SPRINT HTC U11. I changed the CID to unlocked version BS_US001 to flash the unlocked RUU. it kept on failing because the bootloader was unlocked. so then I typed the worst command ever "fastboot oem lock" and now my bootloader is locked, device is S ON, and the worst part is that the bootloader comes up saying that the device is corrupted and cannot be trusted. Now I cannot get into twrp, or my rom. because I changed the CID I can't use my original RUU to revert back. Moreover the android OS version in the download mode comes up as 1.28.651.3 and the unlocked RUU which could work is 1.16.617.6 . The unlocked RUU gives me an error that the android versions either missing or set to 1 and the sprint RUU gives me Invalid Customer ID error. I have access to fastboot. I need a way to change the CID back to SPCS_001. I know I should've used superCID but I panicked while doing all the steps. if anyone could give me or provide me with a way to create a sprint rom.zip which is signed and has a modified android-info.txt including the CID for my phone. I cannot unlock my bootloader as it expects bootloader unlocking to be turned on the android system which unfortunately has been factory reset due to the corruption and is no longer booting. if there is a way to S OFF via fastboot then I can recover. please help me. I have good experience with flashing roms and messing with this stuff but I was out of the android scene for 2 years until recently when I got the U11.
Click to expand...
Click to collapse
sounds like you're in a pickle....someone had a similar issue, read here
you may be able to boot into twrp via fastboot boot twrp-3.1.1-0-ocn.img while in bootloader
then you could try either erasing OS version or changing it
good luck!
OMJ said:
sounds like you're in a pickle....someone had a similar issue, read here
you may be able to boot into twrp via fastboot boot twrp-3.1.1-0-ocn.img while in bootloader
then you could try either erasing OS version or changing it
good luck!
Click to expand...
Click to collapse
Thanks I'll try it out shortly!!
kunalrokz said:
Thanks I'll try it out shortly!!
Click to expand...
Click to collapse
Maybe try to reflash the unlock token again from fastboot and get the bootloader unlocked and reflash twrp
I'm on the same boat as you... Any news?
wranglerray said:
Maybe try to reflash the unlock token again from fastboot and get the bootloader unlocked and reflash twrp
Click to expand...
Click to collapse
The unlock token wont flash gives me a permission error. I will post the exact error in a while.
OMJ said:
sounds like you're in a pickle....someone had a similar issue, read here
you may be able to boot into twrp via fastboot boot twrp-3.1.1-0-ocn.img while in bootloader
then you could try either erasing OS version or changing it
good luck!
Click to expand...
Click to collapse
I tried your recommendation but to no avail. when I boot into the bootloader and send the fastboot command it gives me error "FAILED (remote: GetVar Variable Not found)" and when I do it in download mode it says okay and gets stuck on booting... the phone itself downloads the recovery and displays flash images success (1/1) but nothing else happens.
HOWEVER after sending that command I tried the unlock bootloader command and miraculously it WORKED! I got access to recovery!! I think that being in the download mode explicitly helped the bootloader recognize the unlock token.
zopostyle said:
I'm on the same boat as you... Any news?
Click to expand...
Click to collapse
I tried the fastboot boot twrp-3.1.1-0-ocn.img command as recommended by @OMJ which got stuck on booting...
I then pressed ctrl+c which exits out of the stuck command and allows you to type "fastboot flash unlocktoken unlock_code.bin"
Somehow the bootloader got unlock which removed the device corruption check and I was able to boot.
@wranglerray and @OMJ thank you so much for your help
kunalrokz said:
I tried the fastboot boot twrp-3.1.1-0-ocn.img command as recommended by @OMJ which got stuck on booting...
I then pressed ctrl+c which exits out of the stuck command and allows you to type "fastboot flash unlocktoken unlock_code.bin"
Somehow the bootloader got unlock which removed the device corruption check and I was able to boot.
@wranglerray and @OMJ thank you so much for your help
Click to expand...
Click to collapse
I was able to boot to recovery only... Couldn't make any rom boot,don't know where I'm going wrong...
kunalrokz said:
I tried the fastboot boot twrp-3.1.1-0-ocn.img command as recommended by @OMJ which got stuck on booting...
I then pressed ctrl+c which exits out of the stuck command and allows you to type "fastboot flash unlocktoken unlock_code.bin"
Somehow the bootloader got unlock which removed the device corruption check and I was able to boot.
@wranglerray and @OMJ thank you so much for your help
Click to expand...
Click to collapse
Good to hear!
Cheers
Your neighbor to the south
kunalrokz said:
I tried the fastboot boot twrp-3.1.1-0-ocn.img command as recommended by @OMJ which got stuck on booting...
I then pressed ctrl+c which exits out of the stuck command and allows you to type "fastboot flash unlocktoken unlock_code.bin"
Somehow the bootloader got unlock which removed the device corruption check and I was able to boot.
@wranglerray and @OMJ thank you so much for your help
Click to expand...
Click to collapse
sweet!
zopostyle said:
I was able to boot to recovery only... Couldn't make any rom boot,don't know where I'm going wrong...
Click to expand...
Click to collapse
stock recovery or twrp? you'll need to give more specifics...
OMJ said:
sweet!
stock recovery or twrp? you'll need to give more specifics...
Click to expand...
Click to collapse
With both, I flashed twrp tried to restore a nandroid backup and it stop at the black screen with HTC and powered by android.
I've also tried with stock recovery flash a RUU from SDCard, but I receives Error 14.
What I did was change this:
(bootloader) mid: 2PZC10000
(bootloader) cid: VODAP110
To this:
modelid: 2PZC50000
cidnum: BS_US001
I also tried to change the mainver from 1.27.166.7 to 1.16.617.6, and without it.
RUU from SDCard or PC always give me error 14 or 8.
Oh forgot to mention, when I'm in twrp I always get a message Failed to mount /cota (Invalid Argument)
zopostyle said:
With both, I flashed twrp tried to restore a nandroid backup and it stop at the black screen with HTC and powered by android.
I've also tried with stock recovery flash a RUU from SDCard, but I receives Error 14.
What I did was change this:
(bootloader) mid: 2PZC10000
(bootloader) cid: VODAP110
To this:
modelid: 2PZC50000
cidnum: BS_US001
I also tried to change the mainver from 1.27.166.7 to 1.16.617.6, and without it.
RUU from SDCard or PC always give me error 14 or 8.
Oh forgot to mention, when I'm in twrp I always get a message Failed to mount /cota (Invalid Argument)
Click to expand...
Click to collapse
I would recommend flashing a custom rom. I'm going to take a wild guess and say that you successfully unlocked your bootloader. if that's the case then you just reflashed twrp on an unlocked bootloader. now because you're trying to downgrade your OS you need S OFF.
not sure about the mounting error in twrp. maybe try fastboot -w in download mode. sounds like the file system is corrupt. but once you're able to install a rom, use any custom rom and get sunshine for s off. the s off will allow you to downgrade using RUU mode. make sure you get the new htc_fastboot.exe from the temp folder of the RUU that you want to install.
kunalrokz said:
I would recommend flashing a custom rom. I'm going to take a wild guess and say that you successfully unlocked your bootloader. if that's the case then you just reflashed twrp on an unlocked bootloader. now because you're trying to downgrade your OS you need S OFF.
not sure about the mounting error in twrp. maybe try fastboot -w in download mode. sounds like the file system is corrupt. but once you're able to install a rom, use any custom rom and get sunshine for s off. the s off will allow you to downgrade using RUU mode. make sure you get the new htc_fastboot.exe from the temp folder of the RUU that you want to install.
Click to expand...
Click to collapse
Hum, OK, thanks.
Yes, my bootloader is unlocked and I can flash recovery and boot.img successfully.
I'm at work right now at night I'm gonna try that fastboot -w option.
About the custom rom I've already tried leeDroid and MaximusHD but none of then booted.
What is this?
Failed to mount '/cota' (invalid argument)
AndrzejQ said:
What is this?
Failed to mount '/cota' (invalid argument)
Click to expand...
Click to collapse
An error that I received.
I got it working already.
i have the same problem. had you worked this out ? what's the solution ?
Same issue , but i can't unlock the phone's bootloader , it gives me the message about ticking allow bootloader unlock in developer options but i can't access the OS...
Void tracer said:
Same issue , but i can't unlock the phone's bootloader , it gives me the message about ticking allow bootloader unlock in developer options but i can't access the OS...
Click to expand...
Click to collapse
Same here. It doesn't say that, but o know that's what my error messages mean because when I did this before, I forgot to tick that option in developer options. Now, since after I flashed leedroid, I haven't checked that box again, and now I can't boot. I was simply trying to relock the bootloader to get rid of that annoying message everytime it turned on, then this corrupt error pops up. Please someone lead us in the direction of the fix, even if that fix happens to be get a new phone, just so I have closure, tho I have a hard time giving up and I kinda never believed that a device can be fully "bricked," just super locked.
MSMC said:
Same here. It doesn't say that, but o know that's what my error messages mean because when I did this before, I forgot to tick that option in developer options. Now, since after I flashed leedroid, I haven't checked that box again, and now I can't boot. I was simply trying to relock the bootloader to get rid of that annoying message everytime it turned on, then this corrupt error pops up. Please someone lead us in the direction of the fix, even if that fix happens to be get a new phone, just so I have closure, tho I have a hard time giving up and I kinda never believed that a device can be fully "bricked," just super locked.
Click to expand...
Click to collapse
I can't guarantee this will work, but try the following:
Use the spreadsheet here to find the latest RUU for your phone's CID and MID.
Rename the downloaded RUU to 2PZCIMG.zip
Move 2PZCIMG.zip to the root of your external SD card. If you don't have an external SD card you'll need to get one. If using a PC make sure to format the card as exFAT.
Follow the instructions at 'https://www.the custom droid.com/how-to-restore-htc-u11-stock-firmware/#Method-1-Flashing-RUU-in-Download-Mode' to flash the RUU to your phone.
Good luck!
EDIT: I don't why but XDA forums are filtering the string c u s t o m d r o i d (w/o the spaces)