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.
Related
ok i have run into this weird issue with my G1. it was working perfectly fine yesterday. i turned it off and charged it until it was fully charged like i usually do, but when i turned it on the boot loader screen flashed and the phone turned off! this happens whenever i try to turn the phone on. i cant get into recovery becuase the bootloader screen just flashes. when i try to get to the bootloader screen, it starts up fine but then looks for an image and turns off again. this started happening a few days after flashing haykuros spl if that helps. am i bricked or is there a way to fix this? thanks in advanced
edit: i am also usin the latest experimental build from cyanogen although i dont think this is the problem.
edit2: i managed to get my phone to start up, but im afarid to switch it off just incase it starts happening again so im still looking for a solution to this problem.
edit3: ok back to square one, my phone froze after fully booting up, restarted itself and now the problem is back! wow this is annoying.
it sounds like your camera button could be stuck. if you want to test this type reboot recovery into the recovery console and see if it boots into recovery or bootloader.
check and see if your camera button is stuck or partially stuck since you were able to boot it up once at least
Do you have fastboot working? if so, you can grab your nandroid backups from your SD card and flash them.
or go to cyanogens thread, download the recovery and flash the recovery using the fastboot command to install. i believe its
fastboot flash recovery recovery.img
but plz confirm before you do that
EDIT: david means use adb since you cant get into recovery
adb shell reboot recovery
B-man007 said:
Do you have fastboot working? if so, you can grab your nandroid backups from your SD card and flash them.
or go to cyanogens thread, download the recovery and flash the recovery using the fastboot command to install. i believe its
fastboot flash recovery recovery.img
but plz confirm before you do that
EDIT: david means use adb since you cant get into recovery
adb shell reboot recovery
Click to expand...
Click to collapse
he said he got the phone up and running i meant if he wanted to see if it was a software problem he could type reboot recovery into the terminal emulator and see if he got the bootloader screen or the recovery screen.
also i believe the fastboot commands you posted are correct.
ok thanks for the help guys. before reading your posts a left the phone for a few wins powered it on and now mt phone has booted up and it is working. i will try your solutions still though. i am not sure if i have fast boot working. when the bootloader screen flashed i do remeber it saying fastboot so does that mean i have it running?
edit: camera button seems to be fine although i havent tried the rebbot recovery yet though lol because i need my phone an im not sure if i can get it working again.
do you have adb set up
david1171 said:
do you have adb set up
Click to expand...
Click to collapse
yeah, although im using the 1.5 sdk and not the latest 1.6 does that matter?
if you have adb you will need to have the fastboot.exe (which i think is in the tools folder of the sdk) so cd to the sdk tools folder then use
fastboot flash recovery recovery.img
(also have the recovery.img in the tools folder for this)
ok thanks my phone froze so i had to turn it off and now i am back to square 1 again is there anything besides the camera button that could be casuing this?
djosiah said:
ok thanks my phone froze so i had to turn it off and now i am back to square 1 again is there anything besides the camera button that could be casuing this?
Click to expand...
Click to collapse
have you tried the fastboot flash recovery recovery.img command?
david1171 said:
have you tried the fastboot flash recovery recovery.img command?
Click to expand...
Click to collapse
i cant get into fast boot...the screen with 3 androids on skateboards flashes once really quickly and thats it :/
can anyone help me? the camera button seems to be fine and not stuck. is there another factor that could be causing this? i think i might try unrooting then going through all the steps to root it again. or flashing back to the hardspl and see what happens.
update: i managed to get the phone to boot up again so i went into terminal and typed reboot recovery and i got to the recovery screen ok, but when i pressed home + back to restart the phone the bootloader screen flashed again really quickly :/ it also seems like if i leave the phone off for a few hours it will power up fine but when it is turned off i have to wait another few hours til i can switch it back on.
djosiah said:
can anyone help me? the camera button seems to be fine and not stuck. is there another factor that could be causing this? i think i might try unrooting then going through all the steps to root it again. or flashing back to the hardspl and see what happens.
update: i managed to get the phone to boot up again so i went into terminal and typed reboot recovery and i got to the recovery screen ok, but when i pressed home + back to restart the phone the bootloader screen flashed again really quickly :/ it also seems like if i leave the phone off for a few hours it will power up fine but when it is turned off i have to wait another few hours til i can switch it back on.
Click to expand...
Click to collapse
this sounds like a hardware problem instead of a software problem since there is still a recovery screen, if your phone is still under warranty call your provider and see if there is anything they can do about it, and if they send you another one, just unroot the one you have
my phone isnt under warranty so looks like i will either have to put up with or buy myself a new one. thanks for the help.
If your sure your camera button isn't stuck, check your back button. If not, maybe some sweat or water got into it. some type of hardware dmg possibly. If your the do it yourself type of person, theres always this handy dandy notebook, I mean service manual
http://forum.xda-developers.com/showthread.php?t=468673
wilnotdie said:
If your sure your camera button isn't stuck, check your back button. If not, maybe some sweat or water got into it. some type of hardware dmg possibly. If your the do it yourself type of person, theres always this handy dandy notebook, I mean service manual
http://forum.xda-developers.com/showthread.php?t=468673
Click to expand...
Click to collapse
ahh yes that would make sense seeing as the bootloader screen says fastboot so it must be a problem with the back button. never thought of that. thanks for the help.
ok assuming that the back button is the problem, if i were to flash back to the hard spl would this problem go away seeing as fastobot mode only works with the 'special' spl?
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
Hey guys,
Today I decided to flash TrickDroid 10.0.0. Everything went well, installed it and at the end of flashing appeared a blue screen saying "Please wait". Waited for about 8-10 minutes, than just clicked once a power button. It asked me do I really wanna quit Aroma installation, pressed No. Then something "magical" happened and it was saying that installation is finished, click to reboot. So I did. After this step my phone won't turn on in any ways, tried to connect to pc - still no signs, it even won't charging..
How can I bring it to life!? Or this is it?
Nelayme said:
Hey guys,
Today I decided to flash TrickDroid 10.0.0. Everything went well, installed it and at the end of flashing appeared a blue screen saying "Please wait". Waited for about 8-10 minutes, than just clicked once a power button. It asked me do I really wanna quit Aroma installation, pressed No. Then something "magical" happened and it was saying that installation is finished, click to reboot. So I did. After this step my phone won't turn on in any ways, tried to connect to pc - still no signs, it even won't charging..
How can I bring it to life!? Or this is it?
Click to expand...
Click to collapse
Hold Power and Volume down until it goes into the bootloader, from there go into recovery and try re-flashing.
AllAboutTheCore said:
Hold Power and Volume down until it goes into the bootloader, from there go into recovery and try re-flashing.
Click to expand...
Click to collapse
Tried this many times but still nothing happens. I think it's totally bricked
Put it under a light, a very strong light and longpress the power button, try this
Are you S-On or S-Off? If you're S-On it isn't possible for you to totally brick the phone as far as I'm aware ... Especially not from flashing a ROM.
AllAboutTheCore said:
Are you S-On or S-Off? If you're S-On it isn't possible for you to totally brick the phone as far as I'm aware ... Especially not from flashing a ROM.
Click to expand...
Click to collapse
I'm S-On. I was searching for a solution later today and I found JTAG Riff box (actually, the service which brings the phones back to life by using this tool). However they can't help me at all, cause my phone isn't listed in that repairable list (not sure why). And the other thing they said was that I need to change the mainboard, because there're no other ways how to fix this problem. And it's a job for htc, not for them.
Nelayme said:
I'm S-On. I was searching for a solution later today and I found JTAG Riff box (actually, the service which brings the phones back to life by using this tool). However they can't help me at all, cause my phone isn't listed in that repairable list (not sure why). And the other thing they said was that I need to change the mainboard, because there're no other ways how to fix this problem. And it's a job for htc, not for them.
Click to expand...
Click to collapse
if your phone is booting to recovery you can still fix it without replacing mainboard just download cyanogenmod once and try flashing it after wiping everything and see if phone boots up. if it does you can use another custom sense 5rom and if it doesnt htc is the way to go
You're not bricked at all, calm down. Aroma crashes all the time and you just didn't finish the rom installation. Go back into recovery, wipe everything and flash it again. To turn the phone off, plug it into your PC and type 'adb reboot' and then hold down power and volume down as it is rebooting.
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.
Hey everyone - I've got an interesting one I think.
I had just gotten everything working with CM11 when I got ambitious and went to replace the logo.bin to remove the 'unlocked bootloader' warning that shows up every boot. I realized too late that the logo.bin I used was for a Moto G. Now you'd think that this would just affect the boot logo and I'd be able to try again with the right logo.bin... nope.
On boot all I see is colorful snow. I hear the startup sounds, and I can access the files on my computer when connected via USB. After the screen goes to sleep it shows a flashing white light. Same response with each different startup button combo.
Any ideas? I've tried using adb and fastboot manually, as well as Myth Tools. 'fastboot devices' shows up blank, and adb finds no devices either. I've installed RSDLite but can't find a file to use (lots of broken download links), and I'm not sure that would even solve my problem.
Thanks for any help!
The phone woke me up with it's alarm this morning. That was unexpected. It's also ringing when I call it - CM is running, just the screen is messed up.
How can I get into fastboot in this state? I've never had much success getting the key combos to work on this phone. Adb reboot commands were my most reliable way, but adb isn't detecting a device. If I installed CM11 and have not installed google apps yet, should adb be working?
dta5003 said:
The phone woke me up with it's alarm this morning. That was unexpected. It's also ringing when I call it - CM is running, just the screen is messed up.
How can I get into fastboot in this state? I've never had much success getting the key combos to work on this phone. Adb reboot commands were my most reliable way, but adb isn't detecting a device. If I installed CM11 and have not installed google apps yet, should adb be working?
Click to expand...
Click to collapse
Nope. Not until adb is enabled by going into the developer options or tweaking the build.prop before install.
Just hold down all three buttons when you are booting up and you'll access the boot menu, from there you can select recovery or fastboot or whatever (for me it's easier than using the other key combos as I too have a hard time with them).
skeevydude said:
Just hold down all three buttons when you are booting up and you'll access the boot menu
Click to expand...
Click to collapse
Maybe it's the way you described it, but I was actually able to get into the boot menu this time! I've fixed the logo, and the phone boots normally now.
For anyone else with similar issues, getting the boot menu requires doing a simulated battery pull (vol down + power) followed by booting with all 3 buttons pressed. I think my error was attempting to hold all 3 buttons when the phone was still on and expecting to get the boot menu.
Hooray, my wife has a phone again! And I won't have to worry about touching it ever again because I won't be allowed to. :victory:
Thanks!
Hi, I am having some problem with my Atrix HD. I was doing some rom update and after reboot all I can see is colored snow (not sure whats the technical name for this, as it will help to search better) and goes to nowhere from there. I tried rebooting few times, but nothing except the snow. Its summer now, so How can get rid of this snow and see my normal phone ?
manugoenka said:
Hi, I am having some problem with my Atrix HD. I was doing some rom update and after reboot all I can see is colored snow (not sure whats the technical name for this, as it will help to search better) and goes to nowhere from there. I tried rebooting few times, but nothing except the snow. Its summer now, so How can get rid of this snow and see my normal phone ?
Click to expand...
Click to collapse
What exactly were you doing? Taking the new AT&T OTA or was it something on the custom side?
I know that flashing the wrong sized bootlogo can do this. I actually flashed a bad one I made the other day that turns my screen red and the actual image is all jacked up. The Moto G logo I flashed left it snowing just like you're experiencing. I've also had random bad flashes do this too.
All you can do is fastboot/myth/rsd back to stock and start over. Hopefully you have backups.
Thank you, I managed to fix my phone, it was something related to battery. I simple pressed all three buttons and connected to charger to get to fastboot menu, which also rebooted few times as phone did not had enough battery to run fastboot. Repeated the process few time to get it working. Thanks