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.
Related
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.
*** LOCK ***
M4_UL PVT SHIP S-ON RL
HBOOT-2.19.0000
It boots right into boot loader without holding the volume button down
Is there a way to fix this without losing data?
Okay so now I am using ruu but keep getting error 171
Pretty sure you need to be s-off to use the RUU .. Why not use a stock based Rom off dev section?
Sent from my GT-I9000 using Xparent Skyblue Tapatalk 2
UnicycleWheelie said:
*** LOCK ***
M4_UL PVT SHIP S-ON RL
HBOOT-2.19.0000
It boots right into boot loader without holding the volume button down
Is there a way to fix this without losing data?
Okay so now I am using ruu but keep getting error 171
Click to expand...
Click to collapse
Can you tell us exactly what happened or what you did before you kept booting into bootloader?
Omarion23145 said:
Can you tell us exactly what happened or what you did before you kept booting into bootloader?
Click to expand...
Click to collapse
My friend brought the one mini (AT&T) to me in bootloader, she didn't know how it got there. she said she only pressed the power button and got there. It did have a case on it, and I thought that maybe it had the down volume key stuck and that's how.
In BL (bootloader) I have tried reboot, power down and pressing the power button, recovery, factory reset...and still comes up in BL.
I have this RUU
RUU_M4_UL_JB_50_Cingular_US_1.32.502.3_Radio_1.19.40d.00.14_10.20.40.4408L_release_333483_signed_2
And when I run it on my windows 7 64bit computer its gets to the end page and restarts the phone into fastboot and the phone says fastbootusb but then on my computer it just says waiting for bootloader................ and then ERROR[171]
I have tried different USB cables and front and back usb ports, I have also tried 2 other computers and still says ERROR 171
And yes, I have the drivers for the phone from HTC Sync... IDK what road to take now
UnicycleWheelie said:
My friend brought the one mini (AT&T) to me in bootloader, she didn't know how it got there. she said she only pressed the power button and got there. It did have a case on it, and I thought that maybe it had the down volume key stuck and that's how.
In BL (bootloader) I have tried reboot, power down and pressing the power button, recovery, factory reset...and still comes up in BL.
I have this RUU
RUU_M4_UL_JB_50_Cingular_US_1.32.502.3_Radio_1.19.40d.00.14_10.20.40.4408L_release_333483_signed_2
And when I run it on my windows 7 64bit computer its gets to the end page and restarts the phone into fastboot and the phone says fastbootusb but then on my computer it just says waiting for bootloader................ and then ERROR[171]
I have tried different USB cables and front and back usb ports, I have also tried 2 other computers and still says ERROR 171
And yes, I have the drivers for the phone from HTC Sync... IDK what road to take now
Click to expand...
Click to collapse
Okay. Is there an OS on there? Try flashing a custom recovery on it ( Try TWRP 2.7.0.0 or higher ), and go to recovery after you flash it, then press install and go into SDCARD. What do you see there? And how much internal memory does it show you?
Omarion23145 said:
Okay. Is there an OS on there? Try flashing a custom recovery on it ( Try TWRP 2.7.0.0 or higher ), and go to recovery after you flash it, then press install and go into SDCARD. What do you see there? And how much internal memory does it show you?
Click to expand...
Click to collapse
I'm not 100% but I think there is no os...and for the flash I did the fastboot and had the img twrp file I renamed it (twrp) and in the CMD typed fastboot flash twrp.img and it comes up with
C:\Users\Gigabyte\Desktop\adt-bundle-windows-x86_64-20140321\sdk\platform-tools>
fastboot flash twrp.img
unknown partition 'twrp.img'
error: cannot determine image filename for 'twrp.img'
C:\Users\Gigabyte\Desktop\adt-bundle-windows-x86_64-20140321\sdk\platform-tools>
fastboot flash twrp
unknown partition 'twrp'
error: cannot determine image filename for 'twrp'
And the htc one mini doesn't have a sdcard slot...it doesn't even show up in my Computer when its connected via usb
Omarion23145 said:
Okay. Is there an OS on there? Try flashing a custom recovery on it ( Try TWRP 2.7.0.0 or higher ), and go to recovery after you flash it, then press install and go into SDCARD. What do you see there? And how much internal memory does it show you?
Click to expand...
Click to collapse
okay I got this
C:\Users\Gigabyte\Desktop\adt-bundle-windows-x86_64-20140321\sdk\platform-tools>
fastboot flash recovery twrp.img
sending 'recovery' (8572 KB)...
OKAY [ 1.207s]
writing 'recovery'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 1.916s
UnicycleWheelie said:
okay I got this
C:\Users\Gigabyte\Desktop\adt-bundle-windows-x86_64-20140321\sdk\platform-tools>
fastboot flash recovery twrp.img
sending 'recovery' (8572 KB)...
OKAY [ 1.207s]
writing 'recovery'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 1.916s
Click to expand...
Click to collapse
you need to unlock your bootloader via htcdev website, then flash the recovery again in fastboot **this will void your warranty ** so if this just happened to your friends phone without any reason,probably better just taking it to your cell provider
Braddison said:
you need to unlock your bootloader via htcdev website, then flash the recovery again in fastboot **this will void your warranty ** so if this just happened to your friends phone without any reason,probably better just taking it to your cell provider
Click to expand...
Click to collapse
So I did the fastboot flash unlocktoken Unlock_code.bin
with htcdev
and it says
C:\Users\Gigabyte\Desktop\adt-bundle-windows-x86_64-20140321\sdk\platform-tools>
fastboot flash unlocktoken Unlock_code.bin
sending 'unlocktoken' (0 KB)...
OKAY [ 0.155s]
writing 'unlocktoken'...
(bootloader) unlock token check successfully
OKAY [ 0.007s]
finished. total time: 0.162s
but its still locked so I do it again and it freezes and there is a green like loading bar on the side but the phone is froze untill you unplud it and replug it in and when you reboot into BL its still locked
when you flash the unlock token you should get a screen appear on your phone (see below)
hit yes...tghe phone will reboot a few times
i would try again but be patient, wait till the phone stops doing what it needs to
Braddison said:
when you flash the unlock token you should get a screen appear on your phone (see below)
hit yes...tghe phone will reboot a few times
i would try again but be patient, wait till the phone stops doing what it needs to
Click to expand...
Click to collapse
and when I do the flash it just stays in the boot loader
Alright will try it again,
UnicycleWheelie said:
and when I do the flash it just stays in the boot loader
Alright will try it again,
Click to expand...
Click to collapse
Yeah. If it doesn't work the first time, try again. Sometimes it doesn't work the first time .
Omarion23145 said:
Yeah. If it doesn't work the first time, try again. Sometimes it doesn't work the first time .
Click to expand...
Click to collapse
https://www.youtube.com/watch?v=XZDuXmy4buY
C:\Users\Gigabyte\Desktop\adt-bundle-windows-x86_64-20140321\sdk\platform-tools>
adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
C:\Users\Gigabyte\Desktop\adt-bundle-windows-x86_64-20140321\sdk\platform-tools>
adb devices
List of devices attached
C:\Users\Gigabyte\Desktop\adt-bundle-windows-x86_64-20140321\sdk\platform-tools>
fastboot devices
HT382WA01938 fastboot
so adb cant find the phone but fastboot can?
i think you deleted the os... can you boot into recovery???
htconemini said:
i think you deleted the os... can you boot into recovery???
Click to expand...
Click to collapse
When I turn it on it goes strigh to boot loader, in hboot/bootloader, I go to recovery and hit the power button, it vibrates and shoes an all white screen with the 3 androids in the middle, then goes to fastboot
I asked her what happened to the phone before this problem happened. and this is what she said...Hey! So, when it first crashed it was a few months ago and it pretty much just ran out of battery and powered down. I don't remember doing anything strange or anything weird happening before it died. And then I got the charger and plugged it in and the boot loader screen popped up. I was really confused and not really sure what was going on so I clicked on reboot and shut down and reboot boot loader and everything to try to get it back to normal. After I clicked those a few times it went back to normal. And it's done that about 4 times total in the past but I could always get it back to normal by selecting the options randomly. And it would always come up after the phone ran out of battery. And then the other night when it died I put it on the charger the screen came up and it wouldn't go away no matter what I did.
To unlock the bootloader do you need adb or only fastboot...because this phone takes the htcdev unlockcode.bin but the phone just stays in bootloader. when you do fastboot devices it shows up but when you do adb devices there is nothing.
UnicycleWheelie said:
To unlock the bootloader do you need adb or only fastboot...because this phone takes the htcdev unlockcode.bin but the phone just stays in bootloader. when you do fastboot devices it shows up but when you do adb devices there is nothing.
Click to expand...
Click to collapse
I'm not alone - The exact same scenario (almost) happened to me a few days ago with my HTC1Mini and now I am stuck at the BL screen also. I lost connectivity (no service), rebooted and the phone went straight to the BL screen. I have tried everything mentioned, including the HTCDev unlock code - no joy, even dough it stated successfully. Also, I did not get the "Yes/No Confirmation" on the phone, it remained on the boot loader screen. It seems that regardless of what method one uses, if the phone is "Locked" nothing will work. If you have figured out how to exist the BL screen, please share your methods/steps/files. Your time and consideration is greatly appreciated. Thanks.
Shacho said:
I'm not alone - The exact same scenario (almost) happened to me a few days ago with my HTC1Mini and now I am stuck at the BL screen also. I lost connectivity (no service), rebooted and the phone went straight to the BL screen. I have tried everything mentioned, including the HTCDev unlock code - no joy, even dough it stated successfully. Also, I did not get the "Yes/No Confirmation" on the phone, it remained on the boot loader screen. It seems that regardless of what method one uses, if the phone is "Locked" nothing will work. If you have figured out how to exist the BL screen, please share your methods/steps/files. Your time and consideration is greatly appreciated. Thanks.
Click to expand...
Click to collapse
I had to contact HTC via the help chat. and they walked me through all the "try this" and nothing still went into BL. so they had me ship it in, and I got it fix for free. took about a 11days
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
...it sounded like there is a problem/fault with this phone.
UnicycleWheelie said:
I had to contact HTC via the help chat. and they walked me through all the "try this" and nothing still went into BL. so they had me ship it in, and I got it fix for free. took about a 11days
...it sounded like there is a problem/fault with this phone.
Click to expand...
Click to collapse
the kept the SN the same but the IMEI changed (on the back sticker)
Asking for a friend... I'll try to provide all the details. If someone knows a hardware solution, cost isn't an issue within reason.
HTC One X on ATT... the phone battery was run all the way out until the phone died. When it was plugged back in, the phone no longer will boot all the way up, it shows the HTC Logo, then the ATT Logo, then back to the HTC Logo... and it just sits there... forever. If you connect it to a computer, the device is found, but you get a message that the device could not start in device manager and there is no drive.
ATTs solution to the above problem is to Wipe and Reset the phone... but she is worried about her data, especially the pictures more than anything.
Booting to Fastboot is fine, you get the following:
***Locked***
EVITA PVT SHIP S-ON-RL
HBOOT-2.14.0000
RADIO-0.24p.32.09.06
OpenDSP-v34.1.0.45.1219
emmC-boot
Nov 26 2012
I installed the HTC drivers and fastboot on the computer and can run some fastboot commands from the computer, so I know there is communication.
I wanted to install and boot another image, such as Clockworkmod, but... when I try to fastboot flash recovery I get:
sending 'recovery' (8642 KB)...
OKAY [ 1.046s]
writing 'recovery'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 1.938s
Running fastboot oem unlock I get:
(bootloader) [ERR] Command error !!!
OKAY [ 0.011s]
finished. total time: 0.012s(I was told this is the error you get when the OS is not installed properly on her device, which is the case.
I booted to the recovery partition hoping there was something there from an update or something but no dice, you just get a big "!".
I checked and was told the device needed rooted first in order to install clockworkmod or something similar... the problem is, I can go to HTCs site to unlock the bootloader with the get_identifier_token command I get an error MID not allowed... because ATT blocks it of course.
I found several guides on how to get around that... but all of them require a working phone that will boot up, which is what we're trying to fix. Does anyone have ideas for me?
timmaaa provide a guide for youre case, have you try it?
bzhmobile said:
timmaaa provide a guide for youre case, have you try it?
Click to expand...
Click to collapse
Sadly, usb debugging is not turned on and since I can't boot into the OS, I can't turn it on.
sirluke4 said:
Sadly, usb debugging is not turned on and since I can't boot into the OS, I can't turn it on.
Click to expand...
Click to collapse
You can't flash clockworkmod because the bootloader is locked. If you unlock the bootloader you will wipe data, not to mention I think unlock is blocked on that device. You could try booting android in safe mode by holding vol up, otherwise it's factory reset time.
@sirluke4
If you can get into the bootloader (which you can) you can just run an RUU, which should fix your problem without wiping any user data. I'm not sure why the title of this thread mentions hating at&t though, they have nothing to do with what's going on here.
You can use this RUU to stay on the firmware that's currently on the device:
http://dl3.htc.com/application/RUU_..._10.130.32.34_release_signed_With_Partial.exe
You can use this RUU to upgrade to Android 4.2.2 and Sense 5:
http://dl3.htc.com/application/HTC_One_X_RUU_5.18.502.1.exe
RUU tutorial:
http://forum.xda-developers.com/showthread.php?t=2593037
Transmitted via Bacon
timmaaa said:
@sirluke4
If you can get into the bootloader (which you can) you can just run an RUU, which should fix your problem without wiping any user data. I'm not sure why the title of this thread mentions hating at&t though, they have nothing to do with what's going on here.
You can use this RUU to stay on the firmware that's currently on the device:
http://dl3.htc.com/application/RUU_..._10.130.32.34_release_signed_With_Partial.exe
You can use this RUU to upgrade to Android 4.2.2 and Sense 5:
http://dl3.htc.com/application/HTC_One_X_RUU_5.18.502.1.exe
RUU tutorial:
http://forum.xda-developers.com/showthread.php?t=2593037
Transmitted via Bacon
Click to expand...
Click to collapse
Running RUU WILL wipe data....
beaups said:
Running RUU WILL wipe data....
Click to expand...
Click to collapse
Running an RUU on this device doesn't wipe user data, which is what they're worried about, I've done it countless times.
Transmitted via Bacon
timmaaa said:
Running an RUU on this device doesn't wipe user data, which is what they're worried about, I've done it countless times.
Transmitted via Bacon
Click to expand...
Click to collapse
Interesting, on an s on, locked device?
beaups said:
Interesting, on an s on, locked device?
Click to expand...
Click to collapse
Yeah, I've walked a few other people through it too.
Transmitted via Bacon
Good to know.
Hi all,
I have(had) a AT&T HTC One X (evita) that was running CM10.2.1, hboot 2.14, S-OFF, CID 11111111
My story: I wanted to update to CM11 so according to the CyanogenMod website (sorry can't post a link as a new user) I updated from my previous hboot 2.14 to 2.18 by updating to firmware 5.18.502.1, so far so good all went fine. Then I noticed that I should have at least TWRP 2.7.0.8 but I had 2.6.something so I went ahead and wanted to update the twrp recovery. That's were I made the stupid mistake. I went to the TWRP manager app, selected recovery update and by mistake (now as I'm tinking back about that) I selected HTC One X+ ATT i.e. the "evitareul" instead of "evita" and flashed that. Now the phone is dead, the screen is black, when put on charger the red LED doesn't come on, power+volume down doesn't do anything (no flashing, vibration, nothing). When I connect it to windows machine it recognizes some android device. Under linux, ADB doesn't see any device, though fastboot does, but instead of serial number there are just some non sense characters. I can run some bastboot commands like "fastboot oem readcid" and that works, but I can't flash (now correct) twrp recovery, all flash attempts end with FAILED (remote: not allowed). I tried applying RUU from windows but the phone can't boot into bootloader so it fails.
Please, is there any way I can fix this on my own? Or is it permanently bricked and I should start looking into getting a new phone :crying:
Many thanks for any advise!!
Does fastboot reboot bootloader do anything?
Hi, I tried to reboot to bootloader, the command was sent but the phone didn't do a thing, no visible reaction
Code:
$ sudo fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.113s]
finished. total time: 0.113s
You've borked your partition table. You can either have the motherboard replaced by HTC (~$200) or have a jtag repair done (~$50).
Thanks, I'll try to find somebody to get the jtag repair done.
Hello, I have a Pixel 3 XL phone with bootloader locked, unable to enter Recovery Mode or unable to start it.
I tried to put factory image through fastboot but I recieve an error saying that the bootloader is locked.
Prior to that the bootloader was unlocked but I wanted to lock it.
Anything to do about it?
pech_alive said:
Hello, I have a Pixel 3 XL phone with bootloader locked, unable to enter Recovery Mode or unable to start it.
I tried to put factory image through fastboot but I recieve an error saying that the bootloader is locked.
Prior to that the bootloader was unlocked but I wanted to lock it.
Anything to do about it?
Click to expand...
Click to collapse
You can get to fastboot but not recovery?
Yeah if you can get to fastboot then unlock the bootloader and flash the factory image
Tulsadiver said:
You can get to fastboot but not recovery?
Click to expand...
Click to collapse
I can enter fastboot, but when I press to enter Recovery Mode the screen goes black and that's it, nothing happens, same when I press Start.
I can't unlock it because I get an error: failed (remote: 'flashing unlock is not allowed')
Was it 100% stock when you relocked it?
Sent from my crosshatch using XDA Labs
I would open the stock recovery on the PC and try flashing the factory image from there.
ridobe said:
Was it 100% stock when you relocked it?
Click to expand...
Click to collapse
It was 100% stock when I relocked it.
krabman said:
I would open the stock recovery on the PC and try flashing the factory image from there.
Click to expand...
Click to collapse
I tried that but this is what returns to me:
flash-all.bat
Sending 'bootloader_a' (8489 KB) OKAY [ 0.310s]
Writing 'bootloader_a' FAILED (remote: 'Fastboot command (flash is not allowed when locked')
Finished. Total time: 0.867s
rebooting into bootloader OKAY [ 0.050s]
Finished. Total time: 0.054s
Sending 'radio_a' (71148 KB) OKAY [ 1.834s]
Writing 'radio_a' FAILED (remote: 'Fastboot command (flash is not allowed when locked')
Finished. Total time: 2.084s
rebooting into bootloader OKAY [ 0.050s]
Finished. Total time: 0.054s
extracting android-info.txt (0 MB) to RAM...
--------------------------------------------
Bootloader Version...: b1c1-0.1-4852902
Baseband Version.....: g845-00010-180619-B-4850223
Serial Number........: **********
--------------------------------------------
Checking product OKAY [ 0.060s]
Checking version-bootloader FAILED
Device version-bootloader is 'b1c1-0.1-4852902'.
Update requires 'b1c1-0.1-4948814'.
fastboot: error: requirements not met!
Press any key to exit...
Click to expand...
Click to collapse
I seem to remember from my Pixel (original) days that there was some trick to re-locking the bootloader or you would encounter issues.
You might consider searching the original Pixel's subforum here at XDA for that thread and see if the suggestions in it apply to you.
I think this might be the thread.
Read through it to see if anything can help you.
https://forum.xda-developers.com/pixel-xl/how-to/psa-read-relocking-bootloader-t3494615
"Checking version-bootloader FAILED
Device version-bootloader is 'b1c1-0.1-4852902'.
Update requires 'b1c1-0.1-4948814'.
fastboot: error: requirements not met!
Press any key to exit..."
The bootloader on your device is pre-release? Not sure at all, love to get some schooling on where that bootloader came from. Where did you get the phone? From the Ukrainian with the stolen batch from Foxconn? Wow, I am getting Alex Jones like too quick or what? Lol
Sent from my Pixel 3 XL using Tapatalk
MArtyChubbs said:
"Checking version-bootloader FAILED
Device version-bootloader is 'b1c1-0.1-4852902'.
Update requires 'b1c1-0.1-4948814'.
fastboot: error: requirements not met!
Press any key to exit..."
The bootloader on your device is pre-release? Not sure at all, love to get some schooling on where that bootloader came from. Where did you get the phone? From the Ukrainian with the stolen batch from Foxconn? Wow, I am getting Alex Jones like too quick or what? Lol
Click to expand...
Click to collapse
A friend of mine bought this phone from a website similar to eBay.
The software was stock.
pech_alive said:
Hello, I have a Pixel 3 XL phone with bootloader locked, unable to enter Recovery Mode or unable to start it.
I tried to put factory image through fastboot but I recieve an error saying that the bootloader is locked.
Prior to that the bootloader was unlocked but I wanted to lock it.
Anything to do about it?
Click to expand...
Click to collapse
Of course when in recovery it's all black. You have to hold vol up and power then menu pops up.
Since it's already a brick, try fastboot flashing unlock_critical
Sent from my Pixel 3 XL using Tapatalk
lucky_strike33 said:
Of course when in recovery it's all black. You have to hold vol up and power then menu pops up.
Click to expand...
Click to collapse
If the Andorid Robot picture appears, pressing the Power key and click Volume Up once will bring up the menu, however, his screen is black..? I get the robot, but yet to see a black screen. Good tip cuz that may be his way out of this mess.
Regarding the older bootloader, wouldn't the newer bootloader in the current factory image upgrade it? OR (put my custom made tinfoil hat on now) Google has blocked the stolen phones from firmware updates or bricks them..? Toots and Farts, you're screwed. (Taking hat off now)
I've always unlocked my pixels right away (lucked out on my VZW Pixel XL) and haven't encountered BL mismatch unless downgrading locked BL from other manufacturers.
There were at least 120 stolen phones sold prior to launch and unless you bought it from Google or an authorized carrier, I am suspicious..?
superchilpil said:
Since it's already a brick, try fastboot flashing unlock_critical
Sent from my Pixel 3 XL using Tapatalk
Click to expand...
Click to collapse
But, wouldn't he need to Go to Developer Options and enable OEM unlocking first?
superchilpil said:
Since it's already a brick, try fastboot flashing unlock_critical
Click to expand...
Click to collapse
People have already done this on working Pixel 3 XL's and all it did was returned an error.
I've gota a vague recollection of needing to format before flashing the image in this situation. Anyone confirm our deny?
MArtyChubbs said:
If the Andorid Robot picture appears, pressing the Power key and click Volume Up once will bring up the menu, however, his screen is black..? I get the robot, but yet to see a black screen. Good tip cuz that may be his way out of this mess.
Regarding the older bootloader, wouldn't the newer bootloader in the current factory image upgrade it? OR (put my custom made tinfoil hat on now) Google has blocked the stolen phones from firmware updates or bricks them..? Toots and Farts, you're screwed. (Taking hat off now)
I've always unlocked my pixels right away (lucked out on my VZW Pixel XL) and haven't encountered BL mismatch unless downgrading locked BL from other manufacturers.
There were at least 120 stolen phones sold prior to launch and unless you bought it from Google or an authorized carrier, I am suspicious..?
But, wouldn't he need to Go to Developer Options and enable OEM unlocking first?
Click to expand...
Click to collapse
True, that didn't occur to me. But since it was unlocked prior it may still be unlockable.
bp328i said:
People have already done this on working Pixel 3 XL's and all it did was returned an error.
Click to expand...
Click to collapse
Being a possible dev unit it might not error out with said command. At least that was my thought process. Doesn't hurt to try anyway? If it fails, it fails. Can't hurt to try.
Sent from my Pixel 3 XL using Tapatalk
I just soft bricked my PXL3; this means access only to fastboot ( is under warranty ) and you can get it back with fastboot flashing unlock critical then flash the factory image i don't get it why you can't
I thought flashing unlock critical was p2xl and not applicable to p3xl? And was your bootloader relocked prior to softbrick?
Sent from my Pixel 3 XL using Tapatalk
Update your adb tools on your computer and try flashing stock images again. Then reboot.
Help, i'm dealing with an issue too, everything was working fine, rooted with magisk , turned off my phone to charge, it reached 100% turned it back on, and it won't boot up, I see the G logo with a grey loading bar white background screen it does this for a few minutes and it reboots and gives me a screen that says "can't load android system. Your data may be corrupt. If you continue to get this message you may need to perform a factory data reset and erase all user data stored on this device" . I don't want to do a factory reset? WTH is going on here.
The last major change i did is install greenify4magisk but i didn't enable it (unchecked in magisk screen)
Help!
Edit: How do i do rescue OTA?