Related
Not sure what happened, but my Desire won't get past the logo boot screen any longer, and RECOVERY mode in HBOOT just reboots the phone (regardless whether the SD card is installed or not). I can get into FASTBOOT however. I tried communicating with the Desire via adb console on my Windows XP system (after ensuring that I have the latest version of HTC Sync installed). "adb" commands do not recognize the phone (error: device not found). "Fastboot" commands do recognize the phone. (The command "fastboot devices", gives me this in return: SH09ER801629). So I'm not sure if my USB drivers are okay with adb, but the fastboot success seems to suggest so. (Also, "MyHTC" shows up under "Android Devices" in Device Manager).
The phone was rooted with ClockWork Mod using UnRevoked, and had Teppic stock Froy v.2.10.405.2 initd as the OS. Originally, it had TELUS-branded Eclair. I've downloaded the TELUS Froyo RUU.exe, but don't know how to install it on the phone, if I can't access RECOVERY mode or adb console. I don't think I ever set up a Gold Card, to my recollection. Also, I've been out of the smartphone scene for 6 months, and did no mods, no flashes, no program installs to my phone in that time. So it's a mystery as to why this is happening. But the phone had been acting up lately, rebooting by itself during a call every so often.
HBOOT screen:
Bravo PVT-3 SHIP S-ON
HBOOT 0.83 0001
RADIO 5.10.05.30
Cyanoid said:
Not sure what happened, but my Desire won't get past the logo boot screen any longer, and RECOVERY mode in HBOOT just reboots the phone (regardless whether the SD card is installed or not). I can get into FASTBOOT however. I tried communicating with the Desire via adb console on my Windows XP system (after ensuring that I have the latest version of HTC Sync installed). "adb" commands do not recognize the phone (error: device not found). "Fastboot" commands do recognize the phone. (The command "fastboot devices", gives me this in return: SH09ER801629). So I'm not sure if my USB drivers are okay with adb, but the fastboot success seems to suggest so. (Also, "MyHTC" shows up under "Android Devices" in Device Manager).
The phone was rooted with ClockWork Mod using UnRevoked, and had Teppic stock Froy v.2.10.405.2 initd as the OS. Originally, it had TELUS-branded Eclair. I've downloaded the TELUS Froyo RUU.exe, but don't know how to install it on the phone, if I can't access RECOVERY mode or adb console. I don't think I ever set up a Gold Card, to my recollection. Also, I've been out of the smartphone scene for 6 months, and did no mods, no flashes, no program installs to my phone in that time. So it's a mystery as to why this is happening. But the phone had been acting up lately, rebooting by itself during a call every so often.
HBOOT screen:
Bravo PVT-3 SHIP S-ON
HBOOT 0.83 0001
RADIO 5.10.05.30
Click to expand...
Click to collapse
if i'm not mistaken you can run the ruu and it should see the device if connected to pc with fastboot loaded.
as for trying to get back without losing data i'm new to all this so no idea
if you had run ruu on the phone and it was wrong type (i.e gsm ruu on cdma phone or other way round) then that explains the lack of capability.
Thanks for the tip. I ran the Froyo TELUS RUU.exe (should be the right type, as I have a Telus phone). It wouldn't work (in both main HBOOT screen and FASTBOOT screen). Gave me an "error 170". It could not connect to the phone, despite that I'm on Windows XP, that it says "Android Bootloader Interface" in Windows Device Manager, that it says "HBOOT USB PLUG" on the HBOOT screen when connected via USB, and that I am able to issue FASTBOOT commands from the PC. But I can't issue adb commands, so it appears I can only "partially" communicate with the phone from the PC.
Should I try CLEAR STORAGE, or could that fully brick my phone?
On the HBOOT screen, these are the status messages that load:
Loading...[PB99DIAG.zip]
No Image!
Loading...[PB99DIAG.nbh]
No Image!
Loading...[PB99IMG.zip]
No Image!
Loading...[PB99DIMG.nbh]
No Image or wrong image!
waynestir said:
if i'm not mistaken you can run the ruu and it should see the device if connected to pc with fastboot loaded.
as for trying to get back without losing data i'm new to all this so no idea
if you had run ruu on the phone and it was wrong type (i.e gsm ruu on cdma phone or other way round) then that explains the lack of capability.
Click to expand...
Click to collapse
USB Brick
For me, it sounds like a typical usb brick :/ I hope you still have rooted ROM. Search through this forum for unbricking guide.
Put the ROM.zip from the RUU on your SDCard but name it PB99IMG.zip and then boot with volume down again to enter HBOOT, it should give you the option to flash your phone back to factory default then.
HTC Desire Stuck on HTC logo - Recovery not Working - SOLVED!!
madcr0w said:
Put the ROM.zip from the RUU on your SDCard but name it PB99IMG.zip and then boot with volume down again to enter HBOOT, it should give you the option to flash your phone back to factory default then.
Click to expand...
Click to collapse
Thanks! I just tried that on the advice of another poster on another forum (before reading your reply), and that's the one and only thing that worked!
Especially when, after the RUU.exe wouldn't install, RECOVERY mode wouldn't work, nor adb, nor HTC Sync. Yes, I've lost my root access, but small consideration, considering I haven't lost my $500 investment! I'm sticking with stock now, as I'd rather not risk having a brick in the future.
As for what went wrong, I can't say for sure. But considering it took months after I had installed a ROM or otherwise modified the phone for problems to show up, I'm guessing it was probably the overclocking heating the chips. Which led to eventual random reboots during phone calls, and the eventual freezing of the boot screen, and subsequent inability of HBOOT to load PB99IMG.ZIP.
xda rocks, thanks to you and all those who took the time to reply.
sorry for delayed responce. I'm sure you had already found a solution by now but in the off chance you didn't.
you have to load fastboot not hboot.
from a power off state hold back button and power on phone. this will load fastboot and ruu will find device when run.
Cyanoid said:
Thanks for the tip. I ran the Froyo TELUS RUU.exe (should be the right type, as I have a Telus phone). It wouldn't work (in both main HBOOT screen and FASTBOOT screen). Gave me an "error 170". It could not connect to the phone, despite that I'm on Windows XP, that it o Image!
Click to expand...
Click to collapse
Fastboot will only work in Fastboot. ADB will only work when phone is booted and USB Debugging is on.
I don't know that as fact, I only know it from personal experience.
Use Fastboot to flash a new ROM, or at least a new recovery image. If you can get into Fastboot, you 'should' be able to fix your phone.
expza said:
Fastboot will only work in Fastboot. ADB will only work when phone is booted and USB Debugging is on.
I don't know that as fact, I only know it from personal experience.
Use Fastboot to flash a new ROM, or at least a new recovery image. If you can get into Fastboot, you 'should' be able to fix your phone.
Click to expand...
Click to collapse
+1 There is a good guide to fastboot commands on the android wiki:
http://android-dls.com/wiki/index.php?title=Fastboot
Should be a case of wiping system, data, cache, then flashing recovery image. Then boot into that and restore a backup or flash a rom.
Cyanoid said:
Thanks! I just tried that on the advice of another poster on another forum (before reading your reply), and that's the one and only thing that worked!
Especially when, after the RUU.exe wouldn't install, RECOVERY mode wouldn't work, nor adb, nor HTC Sync. Yes, I've lost my root access, but small consideration, considering I haven't lost my $500 investment! I'm sticking with stock now, as I'd rather not risk having a brick in the future.
As for what went wrong, I can't say for sure. But considering it took months after I had installed a ROM or otherwise modified the phone for problems to show up, I'm guessing it was probably the overclocking heating the chips. Which led to eventual random reboots during phone calls, and the eventual freezing of the boot screen, and subsequent inability of HBOOT to load PB99IMG.ZIP.
xda rocks, thanks to you and all those who took the time to reply.
Click to expand...
Click to collapse
can u plz help me frm with post u solved ur probs....i m stuck too
1st Post, got my htc desire this morning and after researching for a long time already knew i wanted to root my device.I followed the instructions on this site.[HOWTO] Root Your Desire In 1 Click With UnrEVOked! *UPDATED 20/7* - xda-developers I used unrevoked3, and rooted the device. no trouble Ive backed up the device with titanium backup. Placed cyanogen onto the 4gb sd card which came with the phone.Power off the device. Rebooted whilst holding the volume down button. Got the options up. Navigated to recovery and selected it with the power button. The screen goes blank. The o2 screen comes up saying welcome and thats it, it freezes. I have to pull the battery out of the back in order to reset the device and then it starts up perfectly normal. Tried accessing recovery mode using the clockworkmod but i get the same result.All of the points on the link above were followed. Im pretty much right at the bottom! still researching the net for the answer but im now in need of additional
Does your phone get hot and overheated during the htc logo? It did so to me and it turned out to that my CPU had melted and overheated. Take it to your retailer and they will fix it for free because it's not your fault, it's the phone that overheated.
Try this:
-download this with ur pc and rename it a PB99IMG.zip (not PB99IMG.zip.zip ok?)
-then put it on the root of ur sdcard (not in some folder) through an sd card reader
-ensure the battery is charged much than 30%..better more
-with the phone off (remove battery and put again) press and HOLD the volume down key and press (still holding the volume down key) and hold the power button..hold both and wait to enter in the hboot
-there wait a bit, and it will ask to u if u want apply the update, select yes with the volume keys and confirm with power button
awayra said:
1st Post, got my htc desire this morning and after researching for a long time already knew i wanted to root my device.I followed the instructions on this site.[HOWTO] Root Your Desire In 1 Click With UnrEVOked! *UPDATED 20/7* - xda-developers I used unrevoked3, and rooted the device. no trouble Ive backed up the device with titanium backup. Placed cyanogen onto the 4gb sd card which came with the phone.Power off the device. Rebooted whilst holding the volume down button. Got the options up. Navigated to recovery and selected it with the power button. The screen goes blank. The o2 screen comes up saying welcome and thats it, it freezes. I have to pull the battery out of the back in order to reset the device and then it starts up perfectly normal. Tried accessing recovery mode using the clockworkmod but i get the same result.All of the points on the link above were followed. Im pretty much right at the bottom! still researching the net for the answer but im now in need of additional
Click to expand...
Click to collapse
Just go to my troubleshooting guide, you'll probably find an answer there.
Send it back for warranty repair.
Sent from my Motorola Startac running Atari 2600 software!
@nhrsak - you save me, thanks very much!!
Did you try getting s-off with Revolutionary?
I had problems when i was s-on, but when i s-offed, everything went fine.
Have you tried flashing recovery.img via AndroidFlasher(from XDA)?
Hiya guys,
I recently purchased a HTC desire and its been nothing but trouble. THe phone simply refuses to function. It loads directly into the boot loader after around 3 seconds after I press the power button. It will NOT go into recovery mode, I have tried many times but nothing. Even worste when it enters bootloader all buttons cease to function and I cannot scroll to select an option or enter FASTBOOT, no buttons function whatsoever.
The devices is detected via usb, fastboot commander gives me this error when reading the device details -
Code:
HT05PPL02709 Connected.
-----------------------------------.
STARTING PRINT OF DEVICE INFO.
-----------------------------------.
SPL/hboot version: failed.
Radio version: failed.
Main software version: failed.
cid: failed.
cpld: failed.
getvar:product failed (command write failed (unknown error)).
getvar:mid failed (command write failed (unknown error)).
getvar:security failed (status malformed (1 bytes)).
getvar:build-mode failed (command write failed (unknown error)).
-----------------------------------.
Print of device info SUCCESSFUL.
This device does not have s-off nor eng hboot.
ARE YOU SURE THAT THIS IS THE RIGHT TOOL FOR YOU?.
Within the bootloader itself I get this information -
HTML:
BRAVO PVT1 SHIP S-OFF
RIFF: 0.93.0001
MICROP-051d
TOUCH PANEL-SYNT0101
RADIO-4.06.00.02_2
AUG 10 2010, 17:52:18
When the USB is plugged in I get "HBOOT USB PLUG"
Devices is detected as "MY HTC"
I tried flashing with official htc update utility but I get error 170 (bad usb connection). The device charges etc but that's about all I have been able to do thus far.
I will provide further details if needed, I just really want this fixed.
A small reward of £10 (around $18 dollars) will be issued via Paypal to the first one to fix my problem as a token of goodwill. Would appreciate any help here guys!
Ensure to have the correct drivers (uninstall all htc drivers u have and install the latest htc synch from htc website)
then run the latest ruu for the desire 2.29.405.5
ps. no reward needed
poweroff and hold BACK and POWER. this boots you directly into fastboot mode.
From there you can issue the command
Code:
fastboot oem gencheckpt
which boots you into recovery. Try to flash a rom or restore a backup and get back at us
And yeah we don't help people for profit
bortak said:
poweroff and hold BACK and POWER. this boots you directly into fastboot mode.
From there you can issue the command
Code:
fastboot oem gencheckpt
which boots you into recovery. Try to flash a rom or restore a backup and get back at us
And yeah we don't help people for profit
Click to expand...
Click to collapse
When powered off back and power, or any combination of keys still just instantly load the boot-loader. This is what makes my problem ever more difficult to solve.
The 'reward' is merely a token of my appreciation. Anyone have any ideas please let me know!
I would say put the relevant PB99IMG.zip on the sd card via whatever means you can and return it to stock via the bootloader.
rootSU said:
I would say put the relevant PB99IMG.zip on the sd card via whatever means you can and return it to stock via the bootloader.
Click to expand...
Click to collapse
hardware keys don't work so he won't be able to begin the update :/
bortak said:
hardware keys don't work so he won't be able to begin the update :/
Click to expand...
Click to collapse
Thats exactly my problem. The strange thing is the buttons do actually work but the boot loader just doesn't. So i'm stumped! Is there any solution, i'm starting to lose hope!
Im confused. How do you know the buttons work if you can only get into bootloader and the buttons dont work in teh bootloader?
rootSU said:
Im confused. How do you know the buttons work if you can only get into bootloader and the buttons dont work in teh bootloader?
Click to expand...
Click to collapse
Well I assume they work since the power button works just fine to turn it on to the bootloader. And since they ceases to respond once there I thought perhaps the same could apply to the other buttons.
When I plug in the usb it says "HBOOT USB PLUG" and when I unplug it it simply says "HBOOT" perhaps that is relevant in any way shape or form?
Thanks for sticking by!
So when it goes into hboot, it shoudl highlight fastboot. Pressing power at that point does not take you to fastboot?
Has the device ever had water damage? It could be that the volume button is stuck down or thinks its stuck down.
Also thats an old radio you have there, from 2.1
has this device every worked for you?
rootSU said:
So when it goes into hboot, it shoudl highlight fastboot. Pressing power at that point does not take you to fastboot?
Has the device ever had water damage? It could be that the volume button is stuck down or thinks its stuck down.
Also thats an old radio you have there, from 2.1
has this device every worked for you?
Click to expand...
Click to collapse
It does simply not respond whatsoever to input from the buttons. I ran the command 'fast boot devices' and it did find a device and listed its ID. But when I try reboot or flash witt fastboot I get a 'malformed bytes' error code.
No water damage
crackmunky said:
It does simply not respond whatsoever to input from the buttons. I ran the command 'fast boot devices' and it did find a device and listed its ID. But when I try reboot or flash witt fastboot I get a 'malformed bytes' error code.
No water damage
Click to expand...
Click to collapse
Have you tried running RUU? You can try running the 2.2 RUU and if that doesn't help, 2.3. As your device recognizes that it's plugged in, it could respond to RUU
matus.karahuta said:
Have you tried running RUU? You can try running the 2.2 RUU and if that doesn't help, 2.3. As your device recognizes that it's plugged in, it could respond to RUU
Click to expand...
Click to collapse
RUU recognizes it I think, It alerts me if the battery is lower than 30%, once charged it then loads for about 40 seconds than I receive error 170, USB error. Perhaps this is a sign that it could possibly work.
I have googled the error 170 and alot of people seem to think its a driver issue? However after installing, re-installing and installing again the official, latest HTC sync files it still refuses to work.
Any ideas where to go from there?
Are you using the original cabe? Aftermarket cables seems to work, but using mine original cable, resolved all errors for my colleague who could not flash a RUU.
And try the driver from Unrevoked: http://unrevoked.com/rootwiki/doku.php/public/windows_hboot_driver_install
I NEVER used the official HTC drivers nor HTC sync, but I was able to do everything with the modified USB drivers.
The unrevoked files are currently down FYI
Sent from my HTC Desire using xda premium
Trying a different cable with Unrevoked drivers, will port back shortly. Thank you for the replies thus far guys!
Dam no luck, still 170 error! Tried with two separate cables. Anything else which would cause this?
This is usually only fixable by using PB99IMG.zip but you're stuck there. Really not sure what you can do now. I think you're stuck
Sent from my HTC Desire using xda premium
crackmunky said:
Trying a different cable with Unrevoked drivers, will port back shortly. Thank you for the replies thus far guys!
Click to expand...
Click to collapse
can you take the sd card from the mobile and download "PB99IMG_downgrade" from alpharev.nl, save as PM99IMG.zip in the SD card via PC. put the SD card in the mobile and switch it on. if it is successful, then try the RUU. Hope it helps you.
kmaq said:
can you take the sd card from the mobile and download "PB99IMG_downgrade" from alpharev.nl, save as PM99IMG.zip in the SD card via PC. put the SD card in the mobile and switch it on. if it is successful, then try the RUU. Hope it helps you.
Click to expand...
Click to collapse
I will try this as soon as I get home. Will this work since I cant hit any keys? How will this take effect without me bein able to 'apply' it? or will its presence on the sd card stimulate some kind of effect? Thankyou for the reply!
Hey guys, I was flashing a rom on my One x but for some reason it got stuck in a bootloop. After that, I tried restoring to my earlier rom using CWM but I forgot to flash the boot.img from cmd first so it didn't work. After that I tried restarting my phone but it wouldn't turn on after turning off. When I plug in my charger the red light comes up but I can't turn it on. I left it to charge for a few hours but it still won't turn on, the only sign of it working is that it vibrates when I attempt to turn it on. I also tried connecting it to my pc and it senses it but I get no results when I type adb devices in cmd. Can someone please help me with this issue? Thanks!
What can you see in windows device management? Does
Code:
fastboot devices
give you any info?
No, nothing, but when I connect to pc it says installing device software
Oh yeah, I also forgot to mention that it did turn on before and I got into the bootloader but then it turned off again
I mean the device management in the control panel. It should be there if it says something about drivers.
It says MTP USB Device
What ROM are you on?
I was attempting to flash Blade rom when it got stuck in bootloop
MTP should be only available when the phone is booted. I really don't know what is the problem here, sorry.
Ok, Thanks anyway
I just restarted my pc and after running cmd and entering adb devices I get: SH24KW107359 recovery. But the phone is still off. Any ideas?
If the phone vibrates and your computer sees it like MTP that it might be a hardware failure. Contact HTC for further assistance, or try search the forum. I am sure many faced the same problem, and some got it working finally.
I'm no longer getting MTP, it now says E:\
Wait, were you on android 4.0.4 just before you tried flashing Blade?
BlueSingA said:
Wait, were you on android 4.0.4 just before you tried flashing Blade?
Click to expand...
Click to collapse
No, I was not. At least I don't think so. It's my sisters phone so I'm not sure. Why?
I believe that the phone is switched on, but the screen remains off. Try this:
Code:
fastboot getvar all
I tried turning it on and it turns on then it shows the HTC logo, then when I try to get into CMW it shows a dark screen but u can tell its on.
Ok, if your in cwm, from a cmd prompt run:
adb reboot bootloader
That should put you in the bootloader.
From there use fastboot to flash the kernel to boot as you should have done earlier.
When your done just:
fastboot reboot
-SLS-
When I type fastboot devices in cmd i get: SH24KW107359 fastboot. Can I flash a boot.img by using fastboot flash boot boot.img?
Yes, and also reflash cwm. Dl from clockworkmod site and flash using:
fastboot flash recovery nameofthefile.zip
Sent from my HTC One X using xda app-developers app
Searched many places for my problem but cannot find it specifically and this forum seems to be more clued up than most so here goes.
One x screen started to occasionally freeze on unlock screen (volume buttons worked also the volume pop up came on so screen itself not frozen just couldnt touch input i presume) but would fix with either a full power down or a few presses of the top button. Over the course of a day or two this has progressed to virtually always freezing and finally to where i couldnt unfreeze it even after powering down.
Did a factory reset which did give me access to my phone again but still the problem persists.
From my research it could possibly be some sort of cache problem. Also noticed after factory reset with no apps or data installed, apart from the preinstalled ones, am using 4.7 gb of internal memory with only htc sense running. this seems excessive to me but never checked it before so not sure if this is about right. If not then the cache theory could be right.
So can anyone help me please.
bump
thebarran said:
Searched many places for my problem but cannot find it specifically and this forum seems to be more clued up than most so here goes.
One x screen started to occasionally freeze on unlock screen (volume buttons worked also the volume pop up came on so screen itself not frozen just couldnt touch input i presume) but would fix with either a full power down or a few presses of the top button. Over the course of a day or two this has progressed to virtually always freezing and finally to where i couldnt unfreeze it even after powering down.
Did a factory reset which did give me access to my phone again but still the problem persists.
From my research it could possibly be some sort of cache problem. Also noticed after factory reset with no apps or data installed, apart from the preinstalled ones, am using 4.7 gb of internal memory with only htc sense running. this seems excessive to me but never checked it before so not sure if this is about right. If not then the cache theory could be right.
So can anyone help me please.
Click to expand...
Click to collapse
Did you try RUU?
Not rooted my phone so was hoping to find a fix without rooting in case i have to send it back.
thebarran said:
Not rooted my phone so was hoping to find a fix without rooting in case i have to send it back.
Click to expand...
Click to collapse
Try following this:
http://forum.xda-developers.com/showthread.php?t=1859714
No need to root / unlock bootloader
EDIT: follow option 2
following option 2 but stuck.
Make sure that USB debugging is enabled (Settings/Developer options). In order to determine which ruu file you require, boot your device into bootloader mode (Power off and then restart device by holding Power and Volume Down button together). Connect to pc via USB and check that device shows FASTBOOT USB on screen. Enter the following command in command prompt:
fastboot getvar version-main
But when i enter that in Command prompt i get fastboot is not recognised command etc using windows 8. Any help
Note: my phone is locked
thebarran said:
following option 2 but stuck.
Make sure that USB debugging is enabled (Settings/Developer options). In order to determine which ruu file you require, boot your device into bootloader mode (Power off and then restart device by holding Power and Volume Down button together). Connect to pc via USB and check that device shows FASTBOOT USB on screen. Enter the following command in command prompt:
fastboot getvar version-main
But when i enter that in Command prompt i get fastboot is not recognised command etc using windows 8. Any help
Note: my phone is locked
Click to expand...
Click to collapse
Can you try running fastboot on a different OS? Windows XP/7, Ubuntu? Something else?
EDIT: BTW, are you sure you are running the fastboot command from the fastboot folder?
davidk-il said:
EDIT: BTW, are you sure you are running the fastboot command from the fastboot folder?
Click to expand...
Click to collapse
not doing this what do you mean?
thebarran said:
not doing this what do you mean?
Click to expand...
Click to collapse
Navigate on your PC to the fastboot folder lets say "c:\fastboot".
Shift+right click on any blank place and choose open command window here(or something like that my OS is not in english now).
Try using fastboot commands .
ah nice works, thanks. stay with me in case i get stuck again.
thebarran said:
ah nice works, thanks. stay with me in case i get stuck again.
Click to expand...
Click to collapse
Sorry,
Gotta get some sleep =)
If after running RUU nothing changes take the phone to service.
more problems
Ran and installed the ruu but got an
error[152]:image update error
The ROM update utility cannot update your android phone.
Please get the correct ROM update utility and try again
But i have the correct version already 3.14.401.31 it just wont install and now my phone is stuck on a black screen with htc in centre and nothing else.
Did you run the ruu.exe as a administrator ?
Right click the ruu exe and select that.....and put the phone in the bootloader/fastboot usb mode
Mr Hofs said:
Did you run the ruu.exe as a administrator ?
Right click the ruu exe and select that.....and put the phone in the bootloader/fastboot usb mode
Click to expand...
Click to collapse
tried it in admin mode still no good and cant get to any other screen on my phone now other than the black screen with htc in the middle
thebarran said:
tried it in admin mode still no good and cant get to any other screen on my phone now other than the black screen with htc in the middle
Click to expand...
Click to collapse
Phone for sure in fastboot usb mode?
davidk-il said:
Phone for sure in fastboot usb mode?
Click to expand...
Click to collapse
it was when i first did it biut cannot check no more
Hold the power button and the volume - button together until it reboots and boots into the bootloader, hook the usb cable and you should see "fastboot usb" in red text. At that point you run the ruu with administrator rights
Mr Hofs said:
Hold the power button and the volume - button together until it reboots and boots into the bootloader, hook the usb cable and you should see "fastboot usb" in red text. At that point you run the ruu with administrator rights
Click to expand...
Click to collapse
i cannot. all that happens now is that it powers down and comes back to the black htc screen. cannot get to boot screen anymore.
thebarran said:
i cannot. all that happens now is that it powers down and comes back to the black htc screen. cannot get to boot screen anymore.
Click to expand...
Click to collapse
Try shutting of the phone, powering on when holding power button+volume down for about 8s.
You will get a hboot, choose fastboot connect usb cable and try ruu with admin permissions
finally did get to hboot screen by letting the phone shutdown itself but couldnt ruu as battery power to low so i powered down and recharged battery but back to square one where i cannot get to boot screen just constant black htc screen and cant power down again.
So ill let my battery run down again to power off completely open boot screen then stay on that til i power up enough to try ruu again.
Il let you know what happens when this is done later.
Hi all.
My HTC One X (international version) is stuck in a boot loop. If I press Volumen Down button I can see the HBOOT screen where on top it says **** LOCKED ****
I am trying to unlock it using HTCdev. But that requires me to run the command
Code:
fastboot oem get_token_identifier
But since my device is already stuck in boot loop, my computer is having trouble detecting it.
As output of the above, I only see
Code:
<waiting for device>
If I press Volume Down now, the HBOOT says "Checking SD card for updates", "Failed to open usb master mode", "Loading PJ46IMG.zip" etc. and reboots again.
When I try
Code:
fastboot devices
sometimes I am able to retrieve the serial number of my device correctly.
Any suggestions on how I can get the unlock_code.bin ?
Regards,
Amit
amit112amit said:
Hi all.
My HTC One X (international version) is stuck in a boot loop. If I press Volumen Down button I can see the HBOOT screen where on top it says **** LOCKED ****
I am trying to unlock it using HTCdev. But that requires me to run the command
Code:
fastboot oem get_token_identifier
But since my device is already stuck in boot loop, my computer is having trouble detecting it.
As output of the above, I only see
Code:
<waiting for device>
If I press Volume Down now, the HBOOT says "Checking SD card for updates", "Failed to open usb master mode", "Loading PJ46IMG.zip" etc. and reboots again.
When I try
Code:
fastboot devices
sometimes I am able to retrieve the serial number of my device correctly.
Any suggestions on how I can get the unlock_code.bin ?
Regards,
Amit
Click to expand...
Click to collapse
U haven't installed proper drivers that's what causing probs
Regards
My phone would connect fine previously and I updated the drivers too
kantry123 said:
U haven't installed proper drivers that's what causing probs
Regards
Click to expand...
Click to collapse
Hi kantry123.
My phone would connect to my laptop fine before this issue. I also updated HTCSync and tried to ensure I have latest drivers.
Is updating HTC Sync not enough to ensure driver update?
Regards,
Amit