Related
Hello, I've been given a (bricked?) Sensation to try and revive: if you just power it on it goes straight to bootloader/fastboot screen and pressing RECOVERY takes me back to bootloader.
I tinkered with Desire, Desire HD and Flyer and got S-OFF and whatever on all of them, too bad I never got to try a Sensation before therefore I'm asking for some help: moreover I don't even know exactly what's been done to that before...
Sensation's *** LOCKED *** (not HTCdev unlocked, right?), PVT SHIP S-ON RL, HBOOT 1.23, eMMC-boot (is it relevant?). I just can't access it via USB as adb/fastboot devices command doesn't find that and there are no devices appearing in Windows Computer Management (it's fine with my Flyer so I know drivers are ok), can I put some zip/nbh/whatever on the SD to try and resurrect the thing?
Thanks for any help you may give!
teorouge said:
Hello, I've been given a (bricked?) Sensation to try and revive: if you just power it on it goes straight to bootloader/fastboot screen and pressing RECOVERY takes me back to bootloader.
I tinkered with Desire, Desire HD and Flyer and got S-OFF and whatever on all of them, too bad I never got to try a Sensation before therefore I'm asking for some help: moreover I don't even know exactly what's been done to that before...
Sensation's *** LOCKED *** (not HTCdev unlocked, right?), PVT SHIP S-ON RL, HBOOT 1.23, eMMC-boot (is it relevant?). I just can't access it via USB as adb/fastboot devices command doesn't find that and there are no devices appearing in Windows Computer Management (it's fine with my Flyer so I know drivers are ok), can I put some zip/nbh/whatever on the SD to try and resurrect the thing?
Thanks for any help you may give!
Click to expand...
Click to collapse
When connected to pc.. With device is fastboot... Is the device reading fastboot usb? If that's the case try fastboot devices.. Then it should show you the device..
If it does then
Type this
fastboot getvar all
Post the complete output except imei and serial number here
Sent from my pyramid.. Through blazing fast sonic waves
teorouge said:
Hello, I've been given a (bricked?) Sensation to try and revive: if you just power it on it goes straight to bootloader/fastboot screen and pressing RECOVERY takes me back to bootloader.
I tinkered with Desire, Desire HD and Flyer and got S-OFF and whatever on all of them, too bad I never got to try a Sensation before therefore I'm asking for some help: moreover I don't even know exactly what's been done to that before...
Sensation's *** LOCKED *** (not HTCdev unlocked, right?), PVT SHIP S-ON RL, HBOOT 1.23, eMMC-boot (is it relevant?). I just can't access it via USB as adb/fastboot devices command doesn't find that and there are no devices appearing in Windows Computer Management (it's fine with my Flyer so I know drivers are ok), can I put some zip/nbh/whatever on the SD to try and resurrect the thing?
Thanks for any help you may give!
Click to expand...
Click to collapse
No, you haven't. Follow this guide: http://forum.xda-developers.com/showthread.php?p=25587345#post25587345
Or, flash the appropriate RUU is my suggestion.
I can't get any USB connection in bootloader, neither HBOOT USB or FASTBOOT USB.
Any chance for a sd card based procedure?
HTC Flyer p510e
No chances then? Should I write down the time of death?
HTC Flyer p510e
Unplug & replug the cable. Also, it it's in the bootloader, select fastboot.
If the device doesn't say fastboot USB, then you have no fastboot access.
I haven't. That is the main thing I'm trying to point out since post one. Is there anything else I may try before sending this to HTC support?
HTC Flyer p510e
What os is your computer? Pm me if it's a Linux distro then we can gtalk a few ideas to see if we can get advice to recognize device...
irrelephant said:
What os is your computer? Pm me if it's a Linux distro then we can gtalk a few ideas to see if we can get advice to recognize device...
Click to expand...
Click to collapse
Windows 8 build 8400 but of course I can virtualize any OS.
HTC Flyer p510e
hey everyone. i finally got my one x from at&t and now i'm trying to do everything to it before it all gets fixed. i've rooted and now i'm attempting to unlock the bootloader.
the problem is the drivers. if the phone is not in the bootloader, my computer identifies the device as "my htc", however, when it is in the bootloader, it is identified as "android 1.0".
i have already gotten supercid, i just need the identifier token. when i use the command "fastboot oem get_identifier_token" it just says waiting for device. when i put the command in, my hox is in the bootloader.
so can anyone help with my problem? i'm pretty sure it's the drivers, but i can't find them anywhere online, and my computer doesn't automatically look for them.
If you install htc sync which you can get from htc.com you'll get drivers too. Just make sure htc sync is disabled when you use any of the one click tools.
Your phone has to be in fastboot mode, not bootloader. Use the vol up and down to select fastboot, and power button to confirm.
when i installed htc sync, it said the drivers failed to install. is there a direct download to manually install the drivers?
Winters37 said:
when i installed htc sync, it said the drivers failed to install. is there a direct download to manually install the drivers?
Click to expand...
Click to collapse
http://binary100100.googlecode.com/files/HTCDriver3.0.0.007.exe the link i used when i first bought my one x
Hello xda,
a friend of mine just gave me his HTC Sensation because it isnt running quite a while. The problem is that i haven't had a HTC device ever and I don't really know what to do and what information you need to help me so I'd be happy if u just tell me what information you need and I will try to get them for you.
The Information I got so far is:
- if I want to boot it, it stays at the HTC Logo
- CWM starts with some errors but you can't perform a wipe (just turns off)
- Bootloader starts as well but you can't perform wipe either, nor flash new CWM
- If i connect it with the computer while in fastboot it changes to "fastboot usb" but adb cannot find the device, though i installed first the drivers, lateron htc sync. Windows just calls it "myhtc"
bootloader says:
"PYRAMID PVT SHIP S-OFF RL
HBOOT . 1.27.1100
RADIO - 11.22.3594.07_M
OpenADSP-v02.6.0.2226.00.0131
eMMC-boot
Jan 13 2012, 17:33:34"
So what should I try to do or what information will you need.
I would be very happy if u can help me
fnstGoliath said:
Hello xda,
a friend of mine just gave me his HTC Sensation because it isnt running quite a while. The problem is that i haven't had a HTC device ever and I don't really know what to do and what information you need to help me so I'd be happy if u just tell me what information you need and I will try to get them for you.
The Information I got so far is:
- if I want to boot it, it stays at the HTC Logo
- CWM starts with some errors but you can't perform a wipe (just turns off)
- Bootloader starts as well but you can't perform wipe either, nor flash new CWM
- If i connect it with the computer while in fastboot it changes to "fastboot usb" but adb cannot find the device, though i installed first the drivers, lateron htc sync. Windows just calls it "myhtc"
bootloader says:
"PYRAMID PVT SHIP S-OFF RL
HBOOT . 1.27.1100
RADIO - 11.22.3594.07_M
OpenADSP-v02.6.0.2226.00.0131
eMMC-boot
Jan 13 2012, 17:33:34"
So what should I try to do or what information will you need.
I would be very happy if u can help me
Click to expand...
Click to collapse
Hi,
Go HERE
Install 4 EXT recovery,using one of the 3 methods available.(probably third)
Then,try to install ARHD ROM.(same guide)
No need to change the firmware.
So I just tried to flash 4 EXT Recovery but it doesn't work..
It finds the zip, ask me whether i want to start the update, i press vol up and "Update is in progres.." appears but nothing more, I'm waiting since 5 minutes and will probably have to power off the phone now.. the same happened when i tried to install cwm so theres something wrong with the bootloader?
What can I do now?
fnstGoliath said:
So I just tried to flash 4 EXT Recovery but it doesn't work..
It finds the zip, ask me whether i want to start the update, i press vol up and "Update is in progres.." appears but nothing more, I'm waiting since 5 minutes and will probably have to power off the phone now.. the same happened when i tried to install cwm so theres something wrong with the bootloader?
What can I do now?
Click to expand...
Click to collapse
Hi,
Maybe you should run a RUU.
Look HERE
I also thought about this but as I said adb doesn't find the device.
Since I never ran a RUU, can I still flash or do I have to get adb to run with the device.
Anyway, I cannot read out the CID of the device so if it is possible, which RUU should I flash?
Thanks for your help
fnstGoliath said:
I also thought about this but as I said adb doesn't find the device.
Since I never ran a RUU, can I still flash or do I have to get adb to run with the device.
Anyway, I cannot read out the CID of the device so if it is possible, which RUU should I flash?
Thanks for your help
Click to expand...
Click to collapse
Hi,
Try installing these windows 7 & 8 drivers (assuming you have a windows 7 or 8 machine)
Reboot your PC and see if your phone is recognized in ADB.
You are s-off,so you do not have to match it 100%
Just get a RUU that is close to your region or carrier.
If you get the wrong one,it is not a problem.
It will just give you an error.
Then,just try another.
)
Well I just installed those drivers but same result as before..
Windows says "MyHTC" and after i write "adb devices" into the cmd window it says "daemon not running. starting it on port 5037. daemon started succesfully. List of devices attached." and the next time i write adb devices it just says "List of devices attached".
Bootloader still says Fastboot USB.
So maybe there's something wrong with my adb?
Well can i flash RUU without adb finding my device or cant I?
fnstGoliath said:
Well I just installed those drivers but same result as before..
Windows says "MyHTC" and after i write "adb devices" into the cmd window it says "daemon not running. starting it on port 5037. daemon started succesfully. List of devices attached." and the next time i write adb devices it just says "List of devices attached".
Bootloader still says Fastboot USB.
So maybe there's something wrong with my adb?
Well can i flash RUU without adb finding my device or cant I?
Click to expand...
Click to collapse
Hi,
Not sure what is happening with your ADB.
Look HERE for help.
In order to run a RUU ,you need to put the bootloader into fastboot,and plug in the USB.
It should show what yours is showing.
So, it should work.
After "List of devices attached" there is no device shown, I didn't leave anything adb shows, so this is still right? Usually it always shows my device ^^
So my adb is probably not running right or it is about my phone
So my next step should be adb showing my device and therefore reinstall android sdk, java, stuff until it might show the phone
or just do something with the phone?
I still think that i cannot run a ruu without any device shown? Didnt really get an answer on this question I guess or I didnt realize it
fnstGoliath said:
After "List of devices attached" there is no device shown, I didn't leave anything adb shows, so this is still right? Usually it always shows my device ^^
So my adb is probably not running right or it is about my phone
So my next step should be adb showing my device and therefore reinstall android sdk, java, stuff until it might show the phone
or just do something with the phone?
I still think that i cannot run a ruu without any device shown? Didnt really get an answer on this question I guess or I didnt realize it
Click to expand...
Click to collapse
Hi,
Just run the RUU.
It will only show error if it does not work.
No big deal,and no damage done.
Just try another one.
if you enable usb debugging might help too
Well.. I just started "RUU_Pyramid_HTC_Europe_1.50.401.1_Radio_10.56.9035.00U_10.14.9035.01_M_release_223042_signed" and everything went fine until installation, no errors at all. Now the installer is stuck at "restarting bootloader" (or something equal, the installation is german) and the phone didnt do anything at all. It's now 15 minutes since the installation started so I probably will try another one but isn't it weird that ther is no error at all?
What should I do if the next RUU does exactly the same?
*edit:
just seeing page 2. How should I enable usb debugging without booting the phone?
*edit2:
second RUU: Same thing, no error but it didnt go further then "Restarting bootloader".
What to do now?
Any further Ideas what I could try?
Puuuush
fnstGoliath said:
Any further Ideas what I could try?
Puuuush
Click to expand...
Click to collapse
Put phone into bootloader then connect to pc and run the RUU
Sent from my HTC Sensation XE with Beats Audio Z715e using xda premium
The phone was in fastboot usb while running the ruu for sure ..
fnstGoliath said:
The phone was in fastboot usb while running the ruu for sure ..
Click to expand...
Click to collapse
Hi,
Try running a RUU with the same radio (11.22) that you have installed.
You will not damage the phone.
It is not always an exact science with RUU.
Sometimes it is just trial and error.
So it is often that there is no error at all?
I just thought flashing wrong RUU will cause an error and not stopping at restarting bootloader. And anyway the bootloader seems pretty broken since it is not flashing anything at all ^^
Still i gonna try it
fnstGoliath said:
So it is often that there is no error at all?
I just thought flashing wrong RUU will cause an error and not stopping at restarting bootloader. And anyway the bootloader seems pretty broken since it is not flashing anything at all ^^
Still i gonna try it
Click to expand...
Click to collapse
Hi,
Probably ,the only thing that will fix your problem is a RUU.
So,keep trying different ones until it works.
I finally managed to find the phone via adb! I think that's a great step.
The biggest problem is that I lose any contact to the phone when i reboot it into bootloader.
I can just boot the phone into recovery and use any other adb function but as soon as I boot it into bootloader I can't do anything anymore.
That's why I cannot use any fastboot commands to flash a zip, neither run a RUU completely i guess.
So I think that i need any rom to either flash via recovery or just via PC not using fastboot/bootloader at all.
Are there any possibilities for me now?
fnstGoliath said:
I finally managed to find the phone via adb! I think that's a great step.
The biggest problem is that I lose any contact to the phone when i reboot it into bootloader.
I can just boot the phone into recovery and use any other adb function but as soon as I boot it into bootloader I can't do anything anymore.
That's why I cannot use any fastboot commands to flash a zip, neither run a RUU completely i guess.
So I think that i need any rom to either flash via recovery or just via PC not using fastboot/bootloader at all.
Are there any possibilities for me now?
Click to expand...
Click to collapse
Hi,
Plug your phone into the PC.
Go to device manager,and where it says MyHTC,right click and update driver.
Browse to the windows 7 & 8 drivers I gave you earlier.
Update,unplug phone ,and reboot PC.
Get a RUU that shows 3.32 or 3.33 in the title,and matches your region
Pull your battery.
Put it back in,and hold volume down and power button together.
Scroll to fastboot.
Plug in usb and run RUU from the PC
Hi.
I want to unlock bootloader on my HTC ChaCha but I have to use that RAA thingy to make it unlockable. Everything goes well until phone reboots to bootloader. After that, HTC Android Phone ROM Update Utility gets stuck on "Wait for bootloader..." and Windows shows that device couldn't be recognized. I already tried to install several HTC Sync versions and driver packs but it didn't helped.
How to fix that?
Hello guys,
So I have an unlocked, unroot AT&T HTC One X, running stock rom JB 4.1.2 & Sense 4. The other day I was just using it when all of a sudden the phone froze & stop responding. I pressed and held the power button, trying to reset it. Ever since then, it had been stuck in a boot loop ("HTC -quietly brilliant" appeared, then reboot). I did not have any recovery like TWRP installed or anything similar. When I tried to enter HBoot, this is what I get"
***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,18:37:14:-1
and a bunch of options as usual. I tried everything from factory reset, clear storage, to recovery, but nothing works. I tried fastboot then install the RUU, but when I plug the phone in the USB port, it is not recognized by my pc. When I opened cmd and type "fastboot device", it says <waiting for device> and nothing happened.I have already installed HTC Sync Manager and the driver, but the problem is still there. Can anyone please help me? I'm a total noob and don't know what to do now. I just want to wipe everything clean and return it to stock.
Any help would be greatly appreciated. Thanks!
dxbach12 said:
Hello guys,
So I have an unlocked, unroot AT&T HTC One X, running stock rom JB 4.1.2 & Sense 4. The other day I was just using it when all of a sudden the phone froze & stop responding. I pressed and held the power button, trying to reset it. Ever since then, it had been stuck in a boot loop ("HTC -quietly brilliant" appeared, then reboot). I did not have any recovery like TWRP installed or anything similar. When I tried to enter HBoot, this is what I get"
***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,18:37:14:-1
and a bunch of options as usual. I tried everything from factory reset, clear storage, to recovery, but nothing works. I tried fastboot then install the RUU, but when I plug the phone in the USB port, it is not recognized by my pc. When I opened cmd and type "fastboot device", it says <waiting for device> and nothing happened.I have already installed HTC Sync Manager and the driver, but the problem is still there. Can anyone please help me? I'm a total noob and don't know what to do now. I just want to wipe everything clean and return it to stock.
Any help would be greatly appreciated. Thanks!
Click to expand...
Click to collapse
Are you sure the device is unlocked? It says locked in your bootloader screen. Did you perform a factory reset from the bootloader? That causes the sd card to become corrupt on modified devices, so if you've done that you've created another problem for yourself. Whatever you do, absolutely do not run an RUU, you'll brick your phone. S-on + SuperCID + jb RUU = brick, that's assuming your phone is modified like you say, but it isn't worth the risk. What happens when you enter recovery? And did you have fastboot working previously or have you installed it since this happened?
Sent from my Evita
timmaaa said:
Are you sure the device is unlocked? It says locked in your bootloader screen. Did you perform a factory reset from the bootloader? That causes the sd card to become corrupt on modified devices, so if you've done that you've created another problem for yourself. Whatever you do, absolutely do not run an RUU, you'll brick your phone. S-on + SuperCID + jb RUU = brick, that's assuming your phone is modified like you say, but it isn't worth the risk. What happens when you enter recovery? And did you have fastboot working previously or have you installed it since this happened?
Sent from my Evita
Click to expand...
Click to collapse
My bad, I mean the device is sim-unlocked (I used it with t-mobile). I did try the factory reset from the bootloader, and it seems like I do have a corrupt sd card, just like you suggested. When I enter recovery, the phone reboot, and stuck in boot loop again. I also agree that install the RUU with s-on is a recipe for a bricked phone. I never had fastboot working before, I just tried it for the sake of installing the RUU.
Do you think that the phone's microusb port is broken?
Ok, so an RUU is possibly safe for you, if the phone has never been modified in the past. The only way to be sure of this is to check the CID but to do that you need a working fastboot connection. The command is this:
Code:
fastboot oem readcid
If it comes back as CWS__001 you're safe to run an RUU, but if it comes back as 11111111 (or anything else) it isn't safe.
When you connect the phone to your PC while the phone is in bootloader mode what does it say on the screen of the phone? It should either say fastboot usb or fastboot ac. If it says fastboot usb your usb port is fine, if it says fastboot ac there could be a problem with the data pins on the port.
Sent from my Evita
timmaaa said:
Ok, so an RUU is possibly safe for you, if the phone has never been modified in the past. The only way to be sure of this is to check the CID but to do that you need a working fastboot connection. The command is this:
Code:
fastboot oem readcid
If it comes back as CWS__001 you're safe to run an RUU, but if it comes back as 11111111 (or anything else) it isn't safe.
When you connect the phone to your PC while the phone is in bootloader mode what does it say on the screen of the phone? It should either say fastboot usb or fastboot ac. If it says fastboot usb your usb port is fine, if it says fastboot ac there could be a problem with the data pins on the port.
Sent from my Evita
Click to expand...
Click to collapse
Yeah, I tried to look up my CID too, but the pc doesnt recognize the phone. When I connect the phone to the pc and I enter the fastboot menu, there're 4 options: bootloader, reboot, reboot bootloader, and power down. It says fastboot usb when I move down to the 3 bottom options.
Still, when I typed in "fastboot oem readcid" in cmd, it stills says < waiting for device >. Could I be setting up the fastboot wrong?
dxbach12 said:
Yeah, I tried to look up my CID too, but the pc doesnt recognize the phone. When I connect the phone to the pc and I enter the fastboot menu, there're 4 options: bootloader, reboot, reboot bootloader, and power down. It says fastboot usb when I move down to the 3 bottom options.
Still, when I typed in "fastboot oem readcid" in cmd, it stills says < waiting for device >. Could I be setting up the fastboot wrong?
Click to expand...
Click to collapse
You can try "fastboot devices" to see if its connecting, beyond that you can check device manager to check if your PC can actually see the device, but perhaps hasn't installed it properly.
For fastboot to work properly you need fastboot installed (obviously), you need the proper drivers installed, you need to be using a usb 2.0 port, and you need to be using the original HTC cable (or one that's known to have good data transmission properties). Do you meet all those requirements? If you have drivers installed how did you install them? The fact that fastboot usb shows up on your screen suggests that the port on your phone is ok. What os are you running on your PC?
Sent from my Evita
timmaaa said:
For fastboot to work properly you need fastboot installed (obviously), you need the proper drivers installed, you need to be using a usb 2.0 port, and you need to be using the original HTC cable (or one that's known to have good data transmission properties). Do you meet all those requirements? If you have drivers installed how did you install them? The fact that fastboot usb shows up on your screen suggests that the port on your phone is ok. What os are you running on your PC?
Sent from my Evita
Click to expand...
Click to collapse
This may be where the problem lies. I don't have an OEM HTC data cable. I've been using a 3rd party one, and before the boot loop problem, the cable works fine. I tried both USB 2.0 port and 3.0 port, but neither works. The pc runs Windows 8.1. I install the driver using "HTC Driver Installer.msi" from another thread on XDA. Still, in device manager, the phone is shown as "Unknown USB Device (Device Failed Enumeration)". I tried to update the driver using local files with no luck.
Ok, your problem is Windows 8.1, there are no compatible fastboot drivers. You need to downgrade to Windows 8 or lower and you should be fine.
Sent from my Evita
timmaaa said:
Ok, your problem is Windows 8.1, there are no compatible fastboot drivers. You need to downgrade to Windows 8 or lower and you should be fine.
Sent from my Evita
Click to expand...
Click to collapse
Sorry for the delayed response, I have been away on business.
So I tries the fastboot on my wife's win 7 pc and it works, finally. When I ran fastboot oem readcid, it returns CWS_001. It looks like I can install the RUU after all.
What guide would you recommend me following? I tried to google one but there're just too many.
Thanks in advance!
All you need to do is connect your phone in fastboot mode and run the RUU exe in Windows. Make sure HTC Sync Manager is uninstalled, make sure no other programs are running, and make sure screen saver/hibernation is turned off. All you need to do is follow the prompts.
Sent from my Evita
timmaaa said:
All you need to do is connect your phone in fastboot mode and run the RUU exe in Windows. Make sure HTC Sync Manager is uninstalled, make sure no other programs are running, and make sure screen saver/hibernation is turned off. All you need to do is follow the prompts.
Sent from my Evita
Click to expand...
Click to collapse
I put the phone in fastboot, ran the RUU, and after a few prompts, clicked "Update", I reached the screen where it says "Waiting for bootloaders" with a status bar. Then after a while (seems like the bootloader fails?), Error [171]: USB Connection Error screen pops up. I gues this is because I can't boot the phone up and select USB debugging as the connection mode. What can I do now? Is it possible to fix the bootloader or put the phone is USB debugging mode?
Thanks!
dxbach12 said:
I put the phone in fastboot, ran the RUU, and after a few prompts, clicked "Update", I reached the screen where it says "Waiting for bootloaders" with a status bar. Then after a while (seems like the bootloader fails?), Error [171]: USB Connection Error screen pops up. I gues this is because I can't boot the phone up and select USB debugging as the connection mode. What can I do now? Is it possible to fix the bootloader or put the phone is USB debugging mode?
Thanks!
Click to expand...
Click to collapse
It has nothing to do with the usb debugging option, I've run RUUs with no OS on my phone before, they do not require that. The problem is your usb connection, this can be sure to multiple things. Are you using a usb 2.0 port? Are you using an original HTC cable or a cable that's known to work with adb/fastboot? You're not still using the PC with Windows 8.1 on it are you?
Sent from my Evita
timmaaa said:
It has nothing to do with the usb debugging option, I've run RUUs with no OS on my phone before, they do not require that. The problem is your usb connection, this can be sure to multiple things. Are you using a usb 2.0 port? Are you using an original HTC cable or a cable that's known to work with adb/fastboot? You're not still using the PC with Windows 8.1 on it are you?
Sent from my Evita
Click to expand...
Click to collapse
Let me tried borrowing someone else's cable. I was using a LG G2 one, so that could be a usb 3.0 cable.
You didn't answer my question, what OS are you using on the PC now?
Sent from my Evita
timmaaa said:
You didn't answer my question, what OS are you using on the PC now?
Sent from my Evita
Click to expand...
Click to collapse
Sorry. It's Windows 7 Professional SP1.
Ok, check the cable and check the port too.
Sent from my Evita
timmaaa said:
Ok, check the cable and check the port too.
Sent from my Evita
Click to expand...
Click to collapse
Ok, so far I have tried connecting the phone to the usb 2.0 port of the win 7 sp1 laptop using:
- 3rd party usb 2.0 cable
- OEM LG G2 cable (probably usb 3.0)
- OEM Kindle usb 2.0 cable
None have works so far. Every time, error [171] pops up.
Could it be a problem with the battery? The RUU recommends charging the phone at least to 30%. When I plug a charger in the phone, the boot loop continues, so I don't think my phone is charging.
dxbach12 said:
Ok, so far I have tried connecting the phone to the usb 2.0 port of the win 7 sp1 laptop using:
- 3rd party usb 2.0 cable
- OEM LG G2 cable (probably usb 3.0)
- OEM Kindle usb 2.0 cable
None have works so far. Every time, error [171] pops up.
Could it be a problem with the battery? The RUU recommends charging the phone at least to 30%. When I plug a charger in the phone, the boot loop continues, so I don't think my phone is charging.
Click to expand...
Click to collapse
So the phone bootloops even when in the bootloader?
Sent from my Evita
timmaaa said:
So the phone bootloops even when in the bootloader?
Sent from my Evita
Click to expand...
Click to collapse
No, that doesnt happen. When it's not in HBOOT, that happens. I'm charging it while putting in HBOOT right now.