Related
I tried searching the threads but couldn't find one with a problem like exactly mine. Sorry if I was a lousy searcher, but here goes:
1 I had TWRP and TrickDroid 5.5.1 installed. Working fine.
2 Downloaded TrickDroid 6.0.1, went into recovery, wiped everything/factory reset etc. and installed the new ROM, rebooted
3 Working fine but there is no root
4 Tried wiping everything again and reflashing the same ROM. Rebooted. Same thing: ROM is working but there's no root
5 Read somewhere that flashing a different kernel might work, so I flashed Bulletproof 1.10 through TWRP. At the end of the installation of the kernel, right before reboot, TWRP said that my root seemed to be broken and asked me if I wanted to fix it. I said yes. As soon as I said yes (by swiping), phone shut off. Now it won't even start so I can't get into recovery. Pressing Volume-down+Power won't get me into fastboot either.
—The only sign of life is this: when I long press the power button, the home and back buttons will blink as long as I continue pressing it. When I release, nothing happens.
—When I plug the phone to PC, it sees it as a "HTC MTP device" and looks for the drivers but fails to find them.
I had never any trouble with flashing ROMs before so I got lazy with time, I don't have any nandroid backup, though since I can't get even into fastboot I guess that's the least of my problems?
Please help; did I really just brick my phone?
Just happened to me too man, I'm not sure what to do! Sorry to hijack your thread, just looking for answers too.
---------- Post added at 10:10 PM ---------- Previous post was at 10:03 PM ----------
kuboa said:
I tried searching the threads but couldn't find one with a problem like exactly mine. Sorry if I was a lousy searcher, but here goes:
1 I had TWRP and TrickDroid 5.5.1 installed. Working fine.
2 Downloaded TrickDroid 6.0.1, went into recovery, wiped everything/factory reset etc. and installed the new ROM, rebooted
3 Working fine but there is no root
4 Tried wiping everything again and reflashing the same ROM. Rebooted. Same thing: ROM is working but there's no root
5 Read somewhere that flashing a different kernel might work, so I flashed Bulletproof 1.10 through TWRP. At the end of the installation of the kernel, right before reboot, TWRP said that my root seemed to be broken and asked me if I wanted to fix it. I said yes. As soon as I said yes (by swiping), phone shut off. Now it won't even start so I can't get into recovery. Pressing Volume-down+Power won't get me into fastboot either.
—The only sign of life is this: when I long press the power button, the home and back buttons will blink as long as I continue pressing it. When I release, nothing happens.
—When I plug the phone to PC, it sees it as a "HTC MTP device" and looks for the drivers but fails to find them.
I had never any trouble with flashing ROMs before so I got lazy with time, I don't have any nandroid backup, though since I can't get even into fastboot I guess that's the least of my problems?
Please help; did I really just brick my phone?
Click to expand...
Click to collapse
Dude, just hold the volume down button and then press the power button...the back and home button will keep flashing and then it will stop...should take you into fastboot..navigate to recovery and try to load a rom up using the SD card mount method...hope it works out for you man!
DarknessTM said:
Just happened to me too man, I'm not sure what to do! Sorry to hijack your thread, just looking for answers too.
Click to expand...
Click to collapse
No need to apologize, that's why we're here. Please report back if you can find a solution.
Google told me that HTC's RUU tool could possibly help unbrick it, so I've downloaded the European variant ("RUU_M7_UL_JB_50_HTC_Europe_1.20.401.1_Radio_4A.13.3227.06_10.27.1127.01_release_308001_signed_2_4"). I fiddled a bit in the Device Manager in my PC and somehow got it to recognize the phone as "My HTC" under "Android ...", then ran the program. HTC logo appeared on the phone's screen so I got excited but after 10 minutes of waiting RUU told me it was the wrong variant and exited. Back to nil. I'm now downloading another variant of the RUU. We'll see if it helps. (I can't for the life of me figure out how to make my PC recognize the phone again though; I'm back to "MTP device, failed to install drivers" phase. Frustrating.)
kuboa said:
No need to apologize, that's why we're here. Please report back if you can find a solution.
Google told me that HTC's RUU tool could possibly help unbrick it, so I've downloaded the European variant ("RUU_M7_UL_JB_50_HTC_Europe_1.20.401.1_Radio_4A.13.3227.06_10.27.1127.01_release_308001_signed_2_4"). I fiddled a bit in the Device Manager in my PC and somehow got it to recognize the phone as "My HTC" under "Android ...", then ran the program. HTC logo appeared on the phone's screen so I got excited but after 10 minutes of waiting RUU told me it was the wrong variant and exited. Back to nil. I'm now downloading another variant of the RUU. We'll see if it helps. (I can't for the life of me figure out how to make my PC recognize the phone again though; I'm back to "MTP device, failed to install drivers" phase. Frustrating.)
Click to expand...
Click to collapse
Dude, just hold the volume down button and then press the power button...the back and home button will keep flashing and then it will stop...should take you into fastboot..navigate to recovery and try to load a rom up using the SD card mount method...hope it works out for you man!
DarknessTM said:
Dude, just hold the volume down button and then press the power button...the back and home button will keep flashing and then it will stop...should take you into fastboot..navigate to recovery and try to load a rom up using the SD card mount method...hope it works out for you man!
Click to expand...
Click to collapse
That doesn't work for me unfortunately, the capacitive buttons just keep on flashing. I can get my PC to recognize it as "HTC Android Interface" but the second RUU failed, too. Glad yours got fixed, though.
kuboa said:
That doesn't work for me unfortunately, the capacitive buttons just keep on flashing. I can get my PC to recognize it as "HTC Android Interface" but the second RUU failed, too. Glad yours got fixed, though.
Click to expand...
Click to collapse
hold it under a bright light and try again
kuboa said:
That doesn't work for me unfortunately, the capacitive buttons just keep on flashing. I can get my PC to recognize it as "HTC Android Interface" but the second RUU failed, too. Glad yours got fixed, though.
Click to expand...
Click to collapse
if you can get still have adb access use Hasoon's AIO Toolkit to reboot to bootloader/recovery and go from there. otherwise hold power and volume down button with the screen facing a very bright light.
Aldo101t said:
hold it under a bright light and try again
Click to expand...
Click to collapse
Whoa! That really did it. Excuse me for swearing but what the f* a bright light has to do with anything?
Thanks, anyways! Phew.
(Now I should figure out why I'm losing my root when flashing this ROM)
kuboa said:
Whoa! That really did it. Excuse me for swearing but what the f* a bright light has to do with anything?
Thanks, anyways! Phew.
(Now I should figure out why I'm losing my root when flashing this ROM)
Click to expand...
Click to collapse
just reflash superuser, i think it was left out by mistake
Aldo101t said:
just reflash superuser, i think it was left out by mistake
Click to expand...
Click to collapse
I tried that but didn't work. Anyways, that's a far less scary problem than a bricked phone, I'll figure it out. Thanks again.
Aldo101t said:
hold it under a bright light and try again
Click to expand...
Click to collapse
hi there.. im having the same problems. i cant access recovery and my computer wont let me access the files on my phone neither. when i boot on the phone it goes right into the bootloader and won't go anywhere else. please help! many many thanks
Bricked after attempted TrickDroid update
I’m having the same problem.
Attempted to update Trickdroid 6.0.1 to 7.0 last night.
My phone now constantly hangs on the boot screen.
I can get to the fastboot and bootloader menus via long press volume down and power but anything from here simply reboots the phone back to the boot screen.
I’ve tried connecting the phone to the PC and using Fastboot and the One all in one kit but the device is never recognised.
Basically I’ve bricked my phone and need help!!
kuboa said:
I tried searching the threads but couldn't find one with a problem like exactly mine. Sorry if I was a lousy searcher, but here goes:
1 I had TWRP and TrickDroid 5.5.1 installed. Working fine.
2 Downloaded TrickDroid 6.0.1, went into recovery, wiped everything/factory reset etc. and installed the new ROM, rebooted
3 Working fine but there is no root
4 Tried wiping everything again and reflashing the same ROM. Rebooted. Same thing: ROM is working but there's no root
5 Read somewhere that flashing a different kernel might work, so I flashed Bulletproof 1.10 through TWRP. At the end of the installation of the kernel, right before reboot, TWRP said that my root seemed to be broken and asked me if I wanted to fix it. I said yes. As soon as I said yes (by swiping), phone shut off. Now it won't even start so I can't get into recovery. Pressing Volume-down+Power won't get me into fastboot either.
—The only sign of life is this: when I long press the power button, the home and back buttons will blink as long as I continue pressing it. When I release, nothing happens.
—When I plug the phone to PC, it sees it as a "HTC MTP device" and looks for the drivers but fails to find them.
I had never any trouble with flashing ROMs before so I got lazy with time, I don't have any nandroid backup, though since I can't get even into fastboot I guess that's the least of my problems?
Please help; did I really just brick my phone?
Click to expand...
Click to collapse
Deano1889 said:
I’m having the same problem.
Attempted to update Trickdroid 6.0.1 to 7.0 last night.
My phone now constantly hangs on the boot screen.
I can get to the fastboot and bootloader menus via long press volume down and power but anything from here simply reboots the phone back to the boot screen.
I’ve tried connecting the phone to the PC and using Fastboot and the One all in one kit but the device is never recognised.
Basically I’ve bricked my phone and need help!!
Click to expand...
Click to collapse
go to fastboot, use HTC all in one kit by hasoon to flash TWRP, go in twrp, Wipe everything including data, system, cache, dalvik cache, again go on HTC kit and put command of adb sideload, go on TWRP advanced menu and sideload roam. once sideload gets transferred, it will start installing and try different rom like ARHD 10.1
I can't belive it, but the bright light thing actually worked for me!
Thanks!
I was in the same situation with an HTC logo and flashing back and home keys. When I tried volume down + power under a bright light, it came back to life in bootloader. Not sure what the bright light has to do with it but glad it worked.
Bright light solution is from twrp sleep bug.. I read it before.. Good luck
Sent from my HTC One using xda app-developers app
ayan15 said:
Bright light solution is from twrp sleep bug.. I read it before.. Good luck
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
The bright light trick is not a bug, and it has nothing to do with TWRP. It happens because HTC built in a "pocket protection" so that the phone will not reboot on its own in your pocket. The proximity sensor needs light shining on it for a hard reboot to work. (Sometime they're not sensitive enough and it takes a brighter light than you would expect)
Sent from my HTC One using XDA Premium 4 mobile app
Hi
Got an HTC for my son 2 weeks back. He used it for a day, but then got an update. After downloading the update, I restarted at the prompt and got a message that the download was corrupted. Switched off the phone and after sometime, restarted, but without the update. I then downloaded it again and got it running for him.
A week later and the phone just crashed and switched off! Charged it and switched it on, but it just crashes and boot loops. Since my son is now not with me, I instructed him to do a reset using hardware buttons (since it does not boot and thereby allow him to do a factory reset from within the phone. I told him to:
Turn off your phone.
With the phone turned off, press and hold the VOLUME DOWN button, and then briefly press the POWER button.
Wait for the screen with the three Android images to appear, and then release the VOLUME DOWN button.
Press VOLUME DOWN to select CLEAR STORAGE, and then press POWER.
Press VOLUME UP to start the factory reset.
Click to expand...
Click to collapse
According to him, this too does not seem to help and it is still crashing (boot loops).
Can someone please suggest something. Problem is that to claim warranty I need him to bring the phone back (as it is a regional warranty) and the earliest he can get it to me is in about 3 months!
Thanks for any help/ suggestions
Does the phone have an unlocked bootloader and custom ROM?
If so then he needs to re flash the rom using Mike's thread:
http://forum.xda-developers.com/showthread.php?t=2265618
http://forum.xda-developers.com/showthread.php?t=2265618
or a more user friendly method is hasoon2000's here:
http://forum.xda-developers.com/showthread.php?t=2183942
Can you please let me know how to check if the bootloader is locked?
It's brand new ... not rooted, nothing .... clean phone 2 weeks of which 1 week has not been used as it was not booting.
Paparasee said:
Can you please let me know how to check if the bootloader is locked?
It's brand new ... not rooted, nothing .... clean phone 2 weeks of which 1 week has not been used as it was not booting.
Click to expand...
Click to collapse
If it's new and clean, then the bootloader will be locked. You have to manually unlock it.
Try going to fastboot and then running "fastboot erase cache".
Though most likely, you may have to take it to a repair center for them to bring it back to stock, without you having to go through the hassle; Especially since it's only 2 weeks old.
Hello All,
Hoping someone will be able to assist me, though I'm starting to lose hope.
I have spent all day so far reading threads, and trying various suggestions and fixes, but nothing has really helped and I'm beginning to think the phone may just be kaput.
Initial issue was nothing out of the ordinary; woke up to find the phone was not responding so pulled the battery. After putting the battery back in, the phone would no longer turn on. Uh oh. Did the obvious, repull the battery, try again. Nothing. Connect to charger (nothing happens, no charging icon on screen). At this point I think the battery has died so I bought a new one. No change, phone still won't turn on and nothing happens when I plug it in to charge.
So now I connect it to my PC, and I get the installing hardware message trying to install the APX stuff which fails. After some research, I manage to get the APX drivers installed such that the phone is detected when I plug it in. More research, decide to try the AOI Toolkit to backup everything first. This works ok.
So now I try and enter recovery mode via Power key + Volume Down key. Nothing. Ok, change the recovery image then. Device is not detected via ADB method. NVFlash method instead then. The bootloader loads fine, the screen wakes up and shows the S/W Download... message. I figure this is a hopeful sign. I try all 3 (ics-cwm-5, ics-cwm-6, twrp-2.5). They all flash successfully. However, I can't enter recovery mode with any of them. Once I disconnect the phone, insert the battery and then hold down the Power + Volume Down buttons, nothing ever happens.
I've also tried the LG Update Tool and the Smartflash options, but the phone is never detected.
As a last resort I repartitioned. This also worked ok, but still no recovery mode.
tl;dr
Phone won't turn on, show as charging, or enter recovery mode. Works when connected as APX with AOI Toolkit.
Am I missing something? Doing something wrong? Any assistance is greatly appreciated. Thx.
Bump
Okay, I'm bumping this thread myself (mostly because I'm an idiot and this could happen to me, too), but to give you my two cents: Have you tried the Full Brick Repair tool? You flash it through NVFlash and apparently "it cures any brick". Try it and tell us how it went.
NoDze said:
Okay, I'm bumping this thread myself (mostly because I'm an idiot and this could happen to me, too), but to give you my two cents: Have you tried the Full Brick Repair tool? You flash it through NVFlash and apparently "it cures any brick". Try it and tell us how it went.
Click to expand...
Click to collapse
Thanks for the suggestion. The flash process itself completed without issue, but still nothing once the battery is inserted and the power button is pressed. I'm going to assume there is some sort of hardware issue at this point and consider the phone officially dead. Now, where's my hammer...?
xda_fanboy said:
Thanks for the suggestion. The flash process itself completed without issue, but still nothing once the battery is inserted and the power button is pressed. I'm going to assume there is some sort of hardware issue at this point and consider the phone officially dead. Now, where's my hammer...?
Click to expand...
Click to collapse
Don't give up yet. Try smartflash and flash stock, or whatever. Seriously. Just keep on trying. I had a Samsung Captivate a year back and something similar happened where I woke up one beautiful morning, tried to unlock my phone: no response. I thought I had an SOD, so I pulled the battery out, reinserted: bootloop. Entered recovery, can't flash anything, unable to mount system/data partitions. Turns out my internal memory/ROM got fried. Yay. But until then, I tried every possible option. Wow, this turned out to be a bit depressing. Just try more stuff. After you've tried everything, and I mean everything, declare the phone dead.
I think i have a similar problem. Just woke up to find my phone to be dead. Tried the usual methods, nothing. Best it could do was from time to time show me a battery sign with a red triangle and a whtie exclamation mark in it. Then sometimes i manage to get into the recovery mode, there i tried practically everything. Used restore, it shows that restore was a success, but when i reboot my phone i get into an endless circle of bootloader icon appearing and dissappearing,
EDIT: somehow from the countless attempt it fired up.
Make sure to have the right bootloader before nvflashing unbrick roms....
xda_fanboy said:
Hello All,
Hoping someone will be able to assist me, though I'm starting to lose hope.
I have spent all day so far reading threads, and trying various suggestions and fixes, but nothing has really helped and I'm beginning to think the phone may just be kaput.
Initial issue was nothing out of the ordinary; woke up to find the phone was not responding so pulled the battery. After putting the battery back in, the phone would no longer turn on. Uh oh. Did the obvious, repull the battery, try again. Nothing. Connect to charger (nothing happens, no charging icon on screen). At this point I think the battery has died so I bought a new one. No change, phone still won't turn on and nothing happens when I plug it in to charge.
So now I connect it to my PC, and I get the installing hardware message trying to install the APX stuff which fails. After some research, I manage to get the APX drivers installed such that the phone is detected when I plug it in. More research, decide to try the AOI Toolkit to backup everything first. This works ok.
So now I try and enter recovery mode via Power key + Volume Down key. Nothing. Ok, change the recovery image then. Device is not detected via ADB method. NVFlash method instead then. The bootloader loads fine, the screen wakes up and shows the S/W Download... message. I figure this is a hopeful sign. I try all 3 (ics-cwm-5, ics-cwm-6, twrp-2.5). They all flash successfully. However, I can't enter recovery mode with any of them. Once I disconnect the phone, insert the battery and then hold down the Power + Volume Down buttons, nothing ever happens.
I've also tried the LG Update Tool and the Smartflash options, but the phone is never detected.
As a last resort I repartitioned. This also worked ok, but still no recovery mode.
tl;dr
Phone won't turn on, show as charging, or enter recovery mode. Works when connected as APX with AOI Toolkit.
Am I missing something? Doing something wrong? Any assistance is greatly appreciated. Thx.
Click to expand...
Click to collapse
Try to flash a new recovery image in apx mode.
And edit the /dev/block/mmcblk0p3 partition your self.
seek=6144 count=75 bs=1 / boot-recovery
Thanks for the added input and encouragement folks.
Just reporting an update:
Having been unsuccessful more times than I could count, I decided to physically disassemble the phone (normally Engineering fix #2, but performed out of order on this occasion). I have zero idea why it should have made a difference, as all I did was take it apart and then put it back together, but the phone has groaned back to life.
Of course, then sausage-fingers here managed to tear the digitizer cable when doing the final reassambly... /facepalm
Anyhow, I have a replacement on order, so I'm hopeful that when I receive that in a few days I'm back to a fully functional Optimus 2x!!
I recently upgraded to an HTC One, on Verizon in the US. I promptly used rumrunner s-off to get S-OFF, unlock the bootloader, and obtain root. I also flashed the latest ClockworkMod recovery, with the intent of installing CyanogenMod, but decided I'd try out the stock ROM for a few days first, since my old phone was still on Gingerbread.
Everything was working fine until I decided to remove some Verizon bloatware. While I did back up each app before removing it, I forgot to make a nandroid backup. I only removed things that seemed nonessential -- such as the NFL Mobile app, Slacker radio, and My Verizon, which I'd also removed without issue on my old phone -- but apparently that was not the case, as after rebooting, I got stuck on the Verizon logo during the boot sequence.
I then attempted to perform a factory reset in CWMR, and it appeared to be stuck on "wiping cache", so -- like the impatient idiot I clearly am, as I later found a few threads explaining that this part of the reset process can just take a very long time -- I rebooted the phone to try again. This resulted in CWMR throwing errors about failing to mount several partitions, but it finally seemed to finish the reset on the second try. However, upon reboot, it just sat at the HTC logo forever.
After about an hour, and no success in finding anything on the internet indicating that it should take this long to boot up after a reset, I powered the phone off and back on again. After rebooting, the bootloader screen displayed "OS" in red followed by some random symbols. I could still get into recovery, and could still access the device with fastboot, so I decided to try to reflash the stock ROM, using the RUU zip found here.
Due to some problem (this was all about 6 hours ago while I was at work, and I was quite frustrated at this point, so I don't remember what exactly was the problem here) and based on the advice of another forum thread, I decided to try TWRP instead of CWM. But, TWRP wouldn't go any further than its logo splash screen, so I re-flashed CWM. Afterwards, my phone went into a reboot loop -- the HTC logo comes up, the phone vibrates shortly, and then after a few seconds the screen turns off and it does the same thing over again. If I hold the power button down for long enough, it will power down, but if I try to turn it back on, it will either go into the loop again, or just sit at the HTC logo (left it there for upwards of an hour at one point).
I have found several threads about similar boot loop issues, but as I can't get into hboot/fastboot or recovery, I can't try to apply any of the solutions. I cannot connect from my computer with fastboot or adb -- "devices" lists nothing, and all other commands return either "error: no device found" or "waiting for device". No amount of power+volume down makes any difference, nor does holding the phone under a bright light as several threads suggested. Occasionally it will go to a black screen (not off, just black) that maybe it thinks is the bootloader menu, but it doesn't display anything, and after about 30 seconds it will reboot itself.
Does anyone have any suggestions for getting into recovery and trying to reflash.... something?
Alternatively, if I return it to Verizon at this point, will they be able to tell that it's rooted/unlocked/S-OFF?
Any ideas would be much appreciated!
brasstongue said:
I recently upgraded to an HTC One, on Verizon in the US. I promptly used rumrunner s-off to get S-OFF, unlock the bootloader, and obtain root. I also flashed the latest ClockworkMod recovery, with the intent of installing CyanogenMod, but decided I'd try out the stock ROM for a few days first, since my old phone was still on Gingerbread.
Everything was working fine until I decided to remove some Verizon bloatware. While I did back up each app before removing it, I forgot to make a nandroid backup. I only removed things that seemed nonessential -- such as the NFL Mobile app, Slacker radio, and My Verizon, which I'd also removed without issue on my old phone -- but apparently that was not the case, as after rebooting, I got stuck on the Verizon logo during the boot sequence.
I then attempted to perform a factory reset in CWMR, and it appeared to be stuck on "wiping cache", so -- like the impatient idiot I clearly am, as I later found a few threads explaining that this part of the reset process can just take a very long time -- I rebooted the phone to try again. This resulted in CWMR throwing errors about failing to mount several partitions, but it finally seemed to finish the reset on the second try. However, upon reboot, it just sat at the HTC logo forever.
After about an hour, and no success in finding anything on the internet indicating that it should take this long to boot up after a reset, I powered the phone off and back on again. After rebooting, the bootloader screen displayed "OS" in red followed by some random symbols. I could still get into recovery, and could still access the device with fastboot, so I decided to try to reflash the stock ROM, using the RUU zip found here.
Due to some problem (this was all about 6 hours ago while I was at work, and I was quite frustrated at this point, so I don't remember what exactly was the problem here) and based on the advice of another forum thread, I decided to try TWRP instead of CWM. But, TWRP wouldn't go any further than its logo splash screen, so I re-flashed CWM. Afterwards, my phone went into a reboot loop -- the HTC logo comes up, the phone vibrates shortly, and then after a few seconds the screen turns off and it does the same thing over again. If I hold the power button down for long enough, it will power down, but if I try to turn it back on, it will either go into the loop again, or just sit at the HTC logo (left it there for upwards of an hour at one point).
I have found several threads about similar boot loop issues, but as I can't get into hboot/fastboot or recovery, I can't try to apply any of the solutions. I cannot connect from my computer with fastboot or adb -- "devices" lists nothing, and all other commands return either "error: no device found" or "waiting for device". No amount of power+volume down makes any difference, nor does holding the phone under a bright light as several threads suggested. Occasionally it will go to a black screen (not off, just black) that maybe it thinks is the bootloader menu, but it doesn't display anything, and after about 30 seconds it will reboot itself.
Does anyone have any suggestions for getting into recovery and trying to reflash.... something?
Alternatively, if I return it to Verizon at this point, will they be able to tell that it's rooted/unlocked/S-OFF?
Any ideas would be much appreciated!
Click to expand...
Click to collapse
Can u get into bootloader?? Press power + vol down??
brasstongue said:
After rebooting, the bootloader screen displayed "OS" in red followed by some random symbols.
Click to expand...
Click to collapse
that means your firmware is either in a state of limbo, or you corrupted one of your partitions.
so I decided to try to reflash the stock ROM, using the RUU zip found here. Due to some problem
Click to expand...
Click to collapse
which ruu, and what was the problem
But, TWRP wouldn't go any further than its logo splash screen, so I re-flashed CWM.
Click to expand...
Click to collapse
Did you flash the correct recovery for Verizon (M7_WLS), it's different than international (M7_U/UL)
as @khandelwalsiddharth mentioned you need to get to bootloader if a fix is even possible, so POWER OFF your phone completely, then HOLD VOLDOWN and POWER, when it boots up let go of POWER but keep holding VOLDOWN until you get to bootloader
then you need to have working "fastboot devices" (if you're on Win8.1, you probably need to use another computer with Win7 or use a Linux Live USB)
if you can't get to bootloader, then I don't think this is fixable, cause hboot is corrupt
Thanks for the reply.
nkk71 said:
which ruu, and what was the problem
Click to expand...
Click to collapse
Oh, I guess I forgot to make that a link... I had downloaded the only VZW one on this page but I'm not even sure why I bothered to mention it, as downloading it to my computer was the only thing I ever did with it; I was never able to get as far as flashing it to the phone, so it actually had nothing to do with the problem...
nkk71 said:
Did you flash the correct recovery for Verizon (M7_WLS), it's different than international (M7_U/UL)
Click to expand...
Click to collapse
I was under the impression that Verizon was m7vzw, in which case yes, I was using the correct recovery (6.0.4.7 version listed next to "HTC One (Verizon)" on this page) and it was working just fine the first time I flashed it.
nkk71 said:
as @khandelwalsiddharth mentioned you need to get to bootloader if a fix is even possible, so POWER OFF your phone completely, then HOLD VOLDOWN and POWER, when it boots up let go of POWER but keep holding VOLDOWN until you get to bootloader
Click to expand...
Click to collapse
Yeah, I've tried this about 100 times, and the only thing holding VOLDOWN does is occasionally interrupt the boot loop to send me to the black screen for 30 seconds before going back into the boot loop. I did find one thread where the poster was able to get into the bootloader after letting the phone sit overnight, so I'll try again tomorrow, but I'm not very hopeful.
nkk71 said:
then you need to have working "fastboot devices" (if you're on Win8.1, you probably need to use another computer with Win7 or use a Linux Live USB)
Click to expand...
Click to collapse
I'm on Win7, and "fastboot devices" was working the other day, so I know my drivers are all set up properly and functioning. The phone just isn't booting far enough to connect to the computer.
nkk71 said:
if you can't get to bootloader, then I don't think this is fixable, cause hboot is corrupt
Click to expand...
Click to collapse
So... should be safe to take it back to Verizon and ask for a replacement, since they won't be able to tell it's unlocked? >_>
brasstongue said:
Thanks for the reply.
Oh, I guess I forgot to make that a link... I had downloaded the only VZW one on this page but I'm not even sure why I bothered to mention it, as downloading it to my computer was the only thing I ever did with it; I was never able to get as far as flashing it to the phone, so it actually had nothing to do with the problem...
I was under the impression that Verizon was m7vzw, in which case yes, I was using the correct recovery (6.0.4.7 version listed next to "HTC One (Verizon)" on this page) and it was working just fine the first time I flashed it.
Yeah, I've tried this about 100 times, and the only thing holding VOLDOWN does is occasionally interrupt the boot loop to send me to the black screen for 30 seconds before going back into the boot loop. I did find one thread where the poster was able to get into the bootloader after letting the phone sit overnight, so I'll try again tomorrow, but I'm not very hopeful.
I'm on Win7, and "fastboot devices" was working the other day, so I know my drivers are all set up properly and functioning. The phone just isn't booting far enough to connect to the computer.
So... should be safe to take it back to Verizon and ask for a replacement, since they won't be able to tell it's unlocked? >_>
Click to expand...
Click to collapse
my bad, thought I read Sprint, not sure if Sprint and Verizon use same recovery, but that doesn't really matter now
unless you can get to bootloader, you're stuck, sorry.
If your pc does see "fastboot devices" then it must be in bootloader and flashing a ruu.zip (if available) could (that's a very big could) get the device working again.
Hi XDA,
I currently have an issue with my One, I'm stuck at the white HTC-screen where it says "powered by android" at the bottom, I can't get into the bootloader, no matter what I try (I've tried every combination there is, multiple times) the PC detects an Android ADB Interface, but it says "unauthorized".
This happened after I unlocked my bootloader regularly via the HTC Dev-method.
If I type "adb reboot bootloader" into a command prompt, it says "error: device unauthorized. Please check the confirmation dialog on your device." but there is nothing on my screen other than the splash-logo.
Is there anything I could do?
Thanks in advance for your time and help.
edit:
I just noticed that the softkeys don't flash when I hold down the power-button, not sure if this helps you determine the error.
No ideas? :/
HeavyHDx said:
Hi XDA,
I currently have an issue with my One, I'm stuck at the white HTC-screen where it says "powered by android" at the bottom, I can't get into the bootloader, no matter what I try (I've tried every combination there is, multiple times) the PC detects an Android ADB Interface, but it says "unauthorized".
This happened after I unlocked my bootloader regularly via the HTC Dev-method.
If I type "adb reboot bootloader" into a command prompt, it says "error: device unauthorized. Please check the confirmation dialog on your device." but there is nothing on my screen other than the splash-logo.
Is there anything I could do?
Thanks in advance for your time and help.
edit:
I just noticed that the softkeys don't flash when I hold down the power-button, not sure if this helps you determine the error.
Click to expand...
Click to collapse
This is a long shot, try Ubuntu/Linux. You can boot into it without installing Linux on your computer and it handles ADB & Fastboot more smoothly. Read and follow FAQ Q5, you must install Ubuntu 12.04 for these procedures to work. If you install the newest version, there are several more steps. Just scroll down the first page and near the bottom there is a link to older versions. If you get fastboot working, then I would try a fastboot erase cache first with fastboot reboot to see if the problem is resolved. If that didn't work then try to get back to bootloader and select factory reset.
majmoz said:
This is a long shot, try Ubuntu/Linux. You can boot into it without installing Linux on your computer and it handles ADB & Fastboot more smoothly. Read and follow FAQ Q5, you must install Ubuntu 12.04 for these procedures to work. If you install the newest version, there are several more steps. Just scroll down the first page and near the bottom there is a link to older versions. If you get fastboot working, then I would try a fastboot erase cache first with fastboot reboot to see if the problem is resolved. If that didn't work then try to get back to bootloader and select factory reset.
Click to expand...
Click to collapse
The problem is that I can't enter the bootloader, so Fastboot won't work.
HeavyHDx said:
The problem is that I can't enter the bootloader, so Fastboot won't work.
Click to expand...
Click to collapse
The other problem is that your phone is not recognized by Windows. If Ubuntu recognizes your phone, then you may be able to use the adb reboot bootloader command. It is a shot in the dark but if it works then great, if not you are in the same place you are now.
If you are S-OFF then try to find a RUU to run, if you are S-ON then you can not run a RUU with an unlocked bootloader.
majmoz said:
The other problem is that your phone is not recognized by Windows. If Ubuntu recognizes your phone, then you may be able to use the adb reboot bootloader command. It is a shot in the dark but if it works then great, if not you are in the same place you are now.
If you are S-OFF then try to find a RUU to run, if you are S-ON then you can not run a RUU with an unlocked bootloader.
Click to expand...
Click to collapse
I don't think using Ubuntu will resolve the "unauthorized"-issue, but It's worth a try, thanks!
Did you try holding the power button under a bright light? Make sure the ambient light sensor (two ports in upper left corner) is exposed.
iElvis said:
Did you try holding the power button under a bright light? Make sure the ambient light sensor (two ports in upper left corner) is exposed.
Click to expand...
Click to collapse
Yep, tried that too, didn't help :/
Has it been stuck at that white screen all this time? You may need to wait until the battery dies and see if it will reboot properly from there.
iElvis said:
Has it been stuck at that white screen all this time? You may need to wait until the battery dies and see if it will reboot properly from there.
Click to expand...
Click to collapse
I left it there for about an hour, no change.
There also isn't anything to boot into, I wiped /system/ and /data/ before unlocking the bootloader.
I was trying to get S-Off and it didn't work with CyanogenMod, so I locked the bootloader and tried to install an RUU and of course, that doesn't work if you don't have S-Off, so I wanted to unlock it again and install a sense based ROM after that, but that's where I got stuck in this bootloop.
In retrospect, it probably was really stupid to wipe those partitions before. Not sure what I was thinking at the time :/
I'll try Ubuntu tomorrow and I'll try it with a brighter light, maybe that works. Otherwise I just have to send it in. Worst that could happen is that they somehow get into the bootloader and discover that it says Tampered, but at that point they can just send it back and with a working bootloader I can fix it myself.
HeavyHDx said:
I left it there for about an hour, no change.
There also isn't anything to boot into, I wiped /system/ and /data/ before unlocking the bootloader.
I was trying to get S-Off and it didn't work with CyanogenMod, so I locked the bootloader and tried to install an RUU and of course, that doesn't work if you don't have S-Off, so I wanted to unlock it again and install a sense based ROM after that, but that's where I got stuck in this bootloop.
In retrospect, it probably was really stupid to wipe those partitions before. Not sure what I was thinking at the time :/
I'll try Ubuntu tomorrow and I'll try it with a brighter light, maybe that works. Otherwise I just have to send it in. Worst that could happen is that they somehow get into the bootloader and discover that it says Tampered, but at that point they can just send it back and with a working bootloader I can fix it myself.
Click to expand...
Click to collapse
Sorry, I was thinking that if you ran it down, then plugged it in, you might be able to get into the bootloader.
Battery's full right now, do you think it will get empty over night?
HeavyHDx said:
Battery's full right now, do you think it will get empty over night?
Click to expand...
Click to collapse
hold the power plus volume down for about 20 seconds when the phone shuts off and comes back on continue holding the buttons till it goes off for a second time. Then let go of power and continue to hold volume down. This has got me into the bootloader many time's. Do this in a well lit room or under a lamp.
HeavyHDx said:
Battery's full right now, do you think it will get empty over night?
Click to expand...
Click to collapse
If it's stuck on the white screen, yeah that should run it down pretty quickly.
But I'm thinking now this might be a bit risky. It will stay on until the battery dies completely instead of shutting down properly. Normally, the system will shut down with a little bit of charge left because if the battery goes completely dead, it may not be able to restart.
I'd try your other ideas first, and if you're ready to return it, give this a shot.
clsA said:
hold the power plus volume down for about 20 seconds when the phone shuts off and comes back on continue holding the buttons till it goes off for a second time. Then let go of power and continue to hold volume down. This has got me into the bootloader many time's. Do this in a well lit room or under a lamp.
Click to expand...
Click to collapse
If I release the power-button when the screen turns black the second time, it just stays off.
It's almost as if the volume-buttons aren't recognized at all :/
@iElvis okay then that'll be my last resort.
HeavyHDx said:
If I release the power-button when the screen turns black the second time, it just stays off.
It's almost as if the volume-buttons aren't recognized at all :/
@iElvis okay then that'll be my last resort.
Click to expand...
Click to collapse
well running the battery dead will not be any different than the shutdown you just did. did you continue to hold volume down and hit the power again after the shut down ? is the usb plugged in this hole time or no?
clsA said:
well running the battery dead will not be any different than the shutdown you just did. did you continue to hold volume down and hit the power again after the shut down ?
Click to expand...
Click to collapse
Yep, I held the button all the time, tried waiting longer and everything, I have already played around with combinations a fair bit before posting this, nothing seemed to work.
Why can't HTC have something like USB Jigs? :/ It's so convenient to just plug this thing in and be in download-mode, regardless how f*cked up your software is.
HeavyHDx said:
Yep, I held the button all the time, tried waiting longer and everything, I have already played around with combinations a fair bit before posting this, nothing seemed to work.
Why can't HTC have something like USB Jigs? :/ It's so convenient to just plug this thing in and be in download-mode, regardless how f*cked up your software is.
Click to expand...
Click to collapse
ok I wish you luck
clsA said:
ok I wish you luck
Click to expand...
Click to collapse
Thanks I just got this thing back from a 2 week repair because the volume-buttons wouldn't work, barely had it a day and now I can send it back again My own fault, but still annoying...
HeavyHDx said:
Thanks I just got this thing back from a 2 week repair because the volume-buttons wouldn't work, barely had it a day and now I can send it back again My own fault, but still annoying...
Click to expand...
Click to collapse
Update:
The place where I sent it to just messaged me this:
http://imgur.com/npdyLgO
I'm curious, how did they manage to get the bootloader working again? Is there another method for getting into the bootloader, other than pressing the buttons?
They want 218€ for fixing it (lol) so I obviously told them to send it back without fixing it, after all I can do that myself if the bootloader works.
Edit:
just got it back, Bootloader works now.