Related
Was trying to switch from TWRP to CWM (having trouble with TWRP installing CM nightlies). I installed the latest CWM via fastboot. Seemed to load OK, but when I tried to start up the recovery, it just rebooted after showing 'Entering Recovery...' in pink at the top.
Now I'm really stuck. No matter what I do, the phone starts up, shows Entering Recovery at the top, and then shuts down. I cannot enter the bootloader. I cannot start up the phone into the ROM (which is a TikTak ROM that was working fine). Basically, I'm unable to do anything.
When the phone is plugged in, no orange charge light comes on. Vol Down + Power doesn't work. Vol Up + Power doesn't work. Either way, the phone tries to enter recovery, then shuts down.
Is there anything else I can try? Is this phone bricked?
What was the fastboot command you did? It sounds like you flashed to the wrong partition, or flashed an m7 recovery instead of an m7wlv
Sent from my HTC6500LVWBLU using XDA Free mobile app
Uzephi said:
What was the fastboot command you did? It sounds like you flashed to the wrong partition, or flashed an m7 recovery instead of an m7wlv
Sent from my HTC6500LVWBLU using XDA Free mobile app
Click to expand...
Click to collapse
fastboot flash recovery <cwm.zip> (whatever it was called)
Same way I did it for TWRP which worked perfectly.
Really need a solution here, if there is one. Currently planning on just letting the battery drain and starting again...
mobilemedic20 said:
fastboot flash recovery <cwm.zip> (whatever it was called)
Same way I did it for TWRP which worked perfectly.
Really need a solution here, if there is one. Currently planning on just letting the battery drain and starting again...
Click to expand...
Click to collapse
If you can't get a charge light while it is off, DO NOT let it die! It will not charge while dead. When it is booting, can you do adb or fastboot commands from your PC? If so, try:
ADB/fastboot reboot bootloader
Sent from my HTC6500LVWBLU using XDA Free mobile app
Usually, the command: fastboot erase cache
Will resolve such issues, though it doesn't always work, depends on what's causing the actual issue.
But that is what I would suggest trying from fastboot.
Problem is I can NOT get into the boot loader at all, unless i'm missing something. Start phone, tries to load recovery, shuts off. That's it. Is there a way to get the bootloader to open? I seem to have no options.
mobilemedic20 said:
Problem is I can NOT get into the boot loader at all, unless i'm missing something. Start phone, tries to load recovery, shuts off. That's it. Is there a way to get the bootloader to open? I seem to have no options.
Click to expand...
Click to collapse
With device powered off,
Power + volume down
Even if partially powered on, trying to load recovery,....
Same process, hold volume down and power until it boots to hboot.
santod040 said:
With device powered off,
Power + volume down
Even if partially powered on, trying to load recovery,....
Same process, hold volume down and power until it boots to hboot.
Click to expand...
Click to collapse
Tried it man, vol down + power as much as you want. It starts, tries to enter recovery (for about 3 seconds) then goes dead. The thing is, even with the screen off and I plug it into the computer, the computer recognizes the phone a little... It says 'driver not recognized' (even though they're installed). So maybe it's actually partially on in the background, and locked up? That's why I'm hoping the battery running down will fix it.
I'm literally dusting off my old galaxy nexus to get that loaded up, because I need my phone. I'm worried the One is bricked.
***Edit / update - when I plug the phone in 'off' (not responsive) mode, and try fastboot anything, it hangs saying 'waiting for device'. Whatever that means.
mobilemedic20 said:
Tried it man, vol down + power as much as you want. It starts, tries to enter recovery (for about 3 seconds) then goes dead. The thing is, even with the screen off and I plug it into the computer, the computer recognizes the phone a little... It says 'driver not recognized' (even though they're installed). So maybe it's actually partially on in the background, and locked up? That's why I'm hoping the battery running down will fix it.
I'm literally dusting off my old galaxy nexus to get that loaded up, because I need my phone. I'm worried the One is bricked.
***Edit / update - when I plug the phone in 'off' (not responsive) mode, and try fastboot anything, it hangs saying 'waiting for device'. Whatever that means.
Click to expand...
Click to collapse
You are holding down on both the volume down and the power button for as long as your fingers can stand to?
It's not a quick press of both, but a steady hold down of both buttons, even if it tries to do the recovery loading , keep holding both down.
Make sure you are pressing them both FIRMly and for at least 30 seconds or more.
If you are already trying that, then disregard.
But the way it's behaving, it doesn't sound like you are.
If so, again, disregard, just making sure you are attempting one of the only possible methods you have, correctly.
As it won't do what it's supposed to if you do not continue to hold them down, even if that entering recovery screen comes up, you need to continue holding them down.
santod040 said:
You are holding down on both the volume down and the power button for as long as your fingers can stand to?
It's not a quick press of both, but a steady hold down of both buttons, even if it tries to do the recovery loading , keep holding both down.
Make sure you are pressing them both FIRMly and for at least 30 seconds or more.
If you are already trying that, then disregard.
But the way it's behaving, it doesn't sound like you are.
If so, again, disregard, just making sure you are attempting one of the only possible methods you have, correctly.
As it won't do what it's supposed to if you do not continue to hold them down, even if that entering recovery screen comes up, you need to continue holding them down.
Click to expand...
Click to collapse
Yes, that's what I've been doing - and if I hold it down for a longer time, the phone will just cycle through. Off, "Entering recovery", off, "entering recovery", etc every 10 seconds or so. It's clearly not working.
mobilemedic20 said:
Yes, that's what I've been doing - and if I hold it down for a longer time, the phone will just cycle through. Off, "Entering recovery", off, "entering recovery", etc every 10 seconds or so. It's clearly not working.
Click to expand...
Click to collapse
Well that's too bad. Sorry to hear you're having these issues.
I noticed in your first post in this thread, you said you did this:
fastboot flash recovery cwm.zip
Was the file actually a zip?
It should have been a .img file.
Just trying to figure out what happened, as it could help in finding a resolution.
As it stands right now, there is nothing really to go off of.
Anyone, still trying to recover my phone... Here's where I'm at. I figured out that while the phone is off, if I plug it in, I can access ADB via the computer's cmd prompt, but no fastboot (says 'waiting for device'). If I use ADB to reboot the bootloader or recovery, I get the same problem - phone resets, tries to enter recovery for 2 seconds, then back off again.
Can I somehow use ADB to get the phone working again?
mobilemedic20 said:
Anyone, still trying to recover my phone... Here's where I'm at. I figured out that while the phone is off, if I plug it in, I can access ADB via the computer's cmd prompt, but no fastboot (says 'waiting for device'). If I use ADB to reboot the bootloader or recovery, I get the same problem - phone resets, tries to enter recovery for 2 seconds, then back off again.
Can I somehow use ADB to get the phone working again?
Click to expand...
Click to collapse
If you borked your boot loader where you can't access it, there isn't much we can do to help. If the phone can't boot to the boot loader, we can't do anything to help. I think the only thing you can do is send it in for JTAG.
Sent from my One using XDA Free mobile app
Uzephi said:
If you borked your boot loader where you can't access it, there isn't much we can do to help. If the phone can't boot to the boot loader, we can't do anything to help. I think the only thing you can do is send it in for JTAG.
Sent from my One using XDA Free mobile app
Click to expand...
Click to collapse
'Send it in for JTAG'... sorry, what does this mean?
I'm also going to try bringing it to Verizon and claiming ignorance to see if I can get a warranty replacement. What's the downside, right?
adb shell
dd if=/sdcard/LOCATIONOFHBOOT/HBOOT.img of=/dev/block/nameofblock
should work, but i have no clue what the hboot block name is and that this way is really risky. Maybe a dev can chime in and help.
http://forum.xda-developers.com/showthread.php?t=2320271
maybe pm this guy for help?
synisterwolf said:
adb shell
dd if=/sdcard/LOCATIONOFHBOOT/HBOOT.img of=/dev/block/nameofblock
should work, but i have no clue what the hboot block name is and that this way is really risky. Maybe a dev can chime in and help.
http://forum.xda-developers.com/showthread.php?t=2320271
maybe pm this guy for help?
Click to expand...
Click to collapse
Appreciate the suggestion but have no idea how to proceed with this. Read that link, even more clueless.
i seem to have hard bricked the device and i have been attempting to find a way i can fix it for hours.. i seem to be stuck. Its stuck on the boot animation cyanogenMod logo. I am unable to get into the recovery mode, as well as fast boot mode. i let it sit on that boot logo for hours without anything at all happening. No progress what so ever. Now the biggest thing i am trying to figure out is how i even managed to get this to happen. there was a software update notification that i received, so i figured it may have been the Android L update or something, so without taking into considering what exactly i was agreeing to i accepted, and continued. Let it reboot, and thats how i got to come across this issue. Any suggestions.
So if you hold down "volume up", "volume down", and then press and hold the power button, does it not boot into the bootloader? You may have to hold all three down for 15 seconds or so... Based on the fact that you can see the boot animation, it tells me that your bootloader is indeed functional, so, once booted into the bootloader, you can easily flash the factory images (as per this) and restore your device to working condition.
efrant said:
So if you hold down "volume up", "volume down", and then press and hold the power button, does it not boot into the bootloader? You may have to hold all three down for 15 seconds or so... Based on the fact that you can see the boot animation, it tells me that your bootloader is indeed functional, so, once booted into the bootloader, you can easily flash the factory images (as per this) and restore your device to working condition.
Click to expand...
Click to collapse
Yeah ive tried that, and nothing is working it just keeps going back to that same boot animation & im out of ideas. Iknow there has to be a way though.
Jewelzxo said:
Yeah ive tried that, and nothing is working it just keeps going back to that same boot animation & im out of ideas. Iknow there has to be a way though.
Click to expand...
Click to collapse
What I find strange is that it boots to the boot animation -- that means the bootloader has loaded up the kernel and Android is attempting to start. The bootloader loads up before anything, so it is obviously working. Don't know why you can't access its menu though with the 3-key press. Maybe one of your volumes keys is not working properly? By holding those three keys down, it should not boot to the boot animation...
Can you get into download mode? Hold only volume down and press and hold power. If so, then you can use Odin and flash a stock ROM as per this thread.
In any case, if you can't get into the bootloader or download mode, then your only option is using OMAPFlash (as per this thread). That will re-flash your bootloader. If you still can't get into the bootloader menu after that, then there is a hardware issue.
Phone gives error reports when booted Help my HTC One m8 went ballistic after I tried to install lollipop. For reference I have a sprint (unconnected) Htc One m8 Harmon Karman edition with Ł launcher as a launcher. I went to settings and found an update. The update download and then installed. When the phone went to boot it booted then instead of taking me to the home screen, it took me to a white page with a loop of error reports of apps not working. I can't get into the phone at all. I tried to boot in recovery but that did nothing. Please help I'm desperate. The pictures show examples of the errors I get them for different apps and hitting buttons to send reportso does nothing but give another report. Please help fix this.
weirdeyedkid said:
I can't get into the phone at all. I tried to boot in recovery but that did nothing.
Click to expand...
Click to collapse
What does that mean exactly? Can you get into bootloader? Do you get a red triangle when you select recovery from bootloader?
Hold power and vol up for several seconds to force a reboot. The moment the screen goes dark to reboot, let go of those buttons and just hold vol down until the bootloader screen appears.
fixed
redpoint73 said:
What does that mean exactly? Can you get into bootloader? Do you get a red triangle when you select recovery from bootloader?
Hold power and vol up for several seconds to force a reboot. The moment the screen goes dark to reboot, let go of those buttons and just hold vol down until the bootloader screen appears.
Click to expand...
Click to collapse
I tried to boot load but it just put me back where I was. I left the phone on over night and it fixed itself so yeah
weirdeyedkid said:
I tried to boot load but it just put me back where I was.
Click to expand...
Click to collapse
If you can't get into bootloader (but can force a reboot), its because you didn't do the button combo correctly. Either you started pressing vol down too late, or let go of it too early.
Bootloader will always work as long as the screen comes on.
Hello,
My friends own an htc m8. A non professional lab has flashed him Android Revoultion Rom (without making a wipe, he used to use stock rom before that)
Since than the device suffer from a lot of problem,we would like to flash a stock rom.
What's the problem? the device refuses to go into bootloader at all & than refuses to turn on, only after a while in the charger it does turn on.
But any attempt to make the device go into the bootloader, has failed.
tried also RUU - it won't load the bootloader, and the pc recognize him as QHSUSB_BULK if the device is off, which is soft brick as far a i know.
The device actually turn on after a while, than when i connect it to the PC, the pc does recognize him normally.
What's the best option to flash a recovery and a stock rom?
Thank you.
efi2222 said:
Hello,
My friends own an htc m8. A non professional lab has flashed him Android Revoultion Rom (without making a wipe, he used to use stock rom before that)
Since than the device suffer from a lot of problem,we would like to flash a stock rom.
What's the problem? the device refuses to go into bootloader at all & than refuses to turn on, only after a while in the charger it does turn on.
But any attempt to make the device go into the bootloader, has failed.
tried also RUU - it won't load the bootloader, and the pc recognize him as QHSUSB_BULK if the device is off, which is soft brick as far a i know.
The device actually turn on after a while, than when i connect it to the PC, the pc does recognize him normally.
What's the best option to flash a recovery and a stock rom?
Thank you.
Click to expand...
Click to collapse
There is definately some information missing here. Flashing a ROM without wiping will never get you into this state, unless maybe the ROM was meant for a different device.
It sounds more like a deleted bootloader partition, or borked eMMC.
It's bricked. You need to take it to a shop to see if they can JTAG it back to life.
Sorry.
xunholyx said:
There is definately some information missing here. Flashing a ROM without wiping will never get you into this state, unless maybe the ROM was meant for a different device.
It sounds more like a deleted bootloader partition, or borked eMMC.
It's bricked. You need to take it to a shop to see if they can JTAG it back to life.
Sorry.
Click to expand...
Click to collapse
Hey,
We don't know what they have done exactly
They device does turn on after a while... Can i just flash the whole bootloader through the computer anyhow? If the device is on, the computer does recognize him and i can use adb/transfer files.
In a few minutes when the device will turn on i'll write the software information
Edit:
Android version 6.0
HTC Sense Version 7.0
Software number Android Revoultion 51.0 by mike1986
kernel version: 3.4.0-perf-g708019f
[email protected] #1
SMP PREEMPT
baseband version: 1.25.2145000021.06_20.68.4196t.01_F
build number: 6.12.1540.4 CL662736 release-keys
forgot to mention WIFI and BT does not work. went to phone identify and wifi mac ddress if 02:00:00:00:00:00 and bluetooth address is: Unavailable
Thank you
efi2222 said:
Hey,
We don't know what they have done exactly
They device does turn on after a while... Can i just flash the whole bootloader through the computer anyhow? If the device is on, the computer does recognize him and i can use adb/transfer files.
In a few minutes when the device will turn on i'll write the software information
Edit:
Android version 6.0
HTC Sense Version 7.0
Software number Android Revoultion 51.0 by mike1986
kernel version: 3.4.0-perf-g708019f
[email protected] #1
SMP PREEMPT
baseband version: 1.25.2145000021.06_20.68.4196t.01_F
build number: 6.12.1540.4 CL662736 release-keys
forgot to mention WIFI and BT does not work. went to phone identify and wifi mac ddress if 02:00:00:00:00:00 and bluetooth address is: Unavailable
Thank you
Click to expand...
Click to collapse
Have you tried turning off the phone, and booting it by holding down power + vol down? That should take you to bootloader. It's not bricked if you can boot it.
Tried that already...Doesn't work. The device refused to turn on that way.
Tried also through adb/an app when the device was on (yeah it's rooted), than the device turned off and the computer see it as QHSUSB_BULK.
Than i have to plug it off the pc, connect to AC and after a while it's just turn on by itself....
efi2222 said:
Tried that already...Doesn't work. The device refused to turn on that way.
Tried also through adb/an app when the device was on (yeah it's rooted), than the device turned off and the computer see it as QHSUSB_BULK.
Than i have to plug it off the pc, connect to AC and after a while it's just turn on by itself....
Click to expand...
Click to collapse
Not sure about this. If you didn't have a bootloader, I don't think your phone would boot at all.
It does boot, but not normally.
Anyway, there's no way of getting into bootloader
Did you enable developer options and within those option check USB debugging, so it's enabled. If not got to "settings > about > software information > more" and tab the build number entry several times until you get prompt the developer options have been enabled. Then got to developer options and check USB debugging. Try running the RUU again. Many this already works. Otherwise we'd have to look further.
Send by the swarm intelligence of my coffee machine ?.
I hgve already enabled dev options. once the ruu tries go get into the bootloader, the device just turn off and i can see on pc device manager it's QHSUSB_BULK
efi2222 said:
It does boot, but not normally.
Click to expand...
Click to collapse
Meaning what, specifically? Stuck on HTC logo screen, or something else?
As long as the screen is on (on any screen), you can:
1) Hold Power + vol up for 20-30 second, which will force a reboot.
2) The moment the screen goes dark, let go of those buttons, and only hold vol down. Don't let go until the bootloader appears.
redpoint73 said:
Meaning what, specifically? Stuck on HTC logo screen, or something else?
As long as the screen is on (on any screen), you can:
1) Hold Power + vol up for 20-30 second, which will force a reboot.
2) The moment the screen goes dark, let go of those buttons, and only hold vol down. Don't let go until the bootloader appears.
Click to expand...
Click to collapse
Tried that yesterday but i have tried that again right now.
Does not work....doesn't load bootloader and the screeen remains black. Brick....
efi2222 said:
Tried that yesterday but i have tried that again right now.
Does not work....doesn't load bootloader and the screeen remains black. Brick....
Click to expand...
Click to collapse
I'm still confused about what you are describing, and I think others trying to help are confused also.
You said the phone boots, but not normally. I asked what that meant specifically (which you did not answer at all). Stuck on HTC screen?
So the screen is on, when you try the button sequence I suggested? Then when the screen goes black to reboot, it just stays black?
Hard to help, if you don't provide details and specifics.
The phone boot and you can use it, that's how i have provided information from the settings. If i try to reboot, the device does not turn on. only after about 5 minutes.
same for bootloader. if you try to get into bootloader from adb for example, than there is only a black screen and after a few minutes it's just load the OS normally. but no bootloader.
efi2222 said:
Tried that yesterday but i have tried that again right now.
Does not work....doesn't load bootloader and the screeen remains black. Brick....
Click to expand...
Click to collapse
So if you try the button combo I suggested, it eventually boots to OS? Are you still holding vol down when it boots to OS? If not, you should be (and let go too early).
---------- Post added at 01:28 PM ---------- Previous post was at 01:28 PM ----------
efi2222 said:
if you try to get into bootloader from adb for example, than there is only a black screen and after a few minutes it's just load the OS normally. but no bootloader.
Click to expand...
Click to collapse
What's the exact adb command? I'm sure you probably have it right, but just want to confirm.
It doesn't boot when i try the button combo... and after a few minutes it boot to OS.
also tried though an app because the device is rooted.... and also through RUU. The RUU restart the device and should make him to go into bootloader but it failes doing it.
adb reboot-bootloader
when the device is turned off the pc only see it as QHSUSB_BULK
efi2222 said:
It doesn't boot when i try the button combo... and after a few minutes it boot to OS.
Click to expand...
Click to collapse
It still really confusing how you are phrasing things "It doesn't boot . . . after a few minutes it boot"
Either it boots (just takes a long time; or boot OS, but not bootloader) or it doesn't.
Holding power + vol down makes it shutdown, right? Once the screen goes dark, hold only vol down and don't stop until you either see bootloader or the OS loads. Its not clear from the way you've typed it, but it sounds like you are pressing vol down for a while, then give up and let go, then it eventually loads OS.
I understand that it doesn't look like it wants to boot into bootloader, from any method. But we really need to eliminate all possibilities and be sure you can't do it with the button combo.
Its really unusual to see a device that can boot into OS, but not go into bootloader at all. I've never seen this once, after being on these forums extensively over the course of 4 different HTC Android devices.
redpoint73 said:
It still really confusing how you are phrasing things "It doesn't boot . . . after a few minutes it boot"
Either it boots (just takes a long time; or boot OS, but not bootloader) or it doesn't.
Holding power + vol down makes it shutdown, right? Once the screen goes dark, hold only vol down and don't stop until you either see bootloader or the OS loads. Its not clear from the way you've typed it, but it sounds like you are pressing vol down for a while, then give up and let go, then it eventually loads OS.
I understand that it doesn't look like it wants to boot into bootloader, from any method. But we really need to eliminate all possibilities and be sure you can't do it with the button combo.
Its really unusual to see a device that can boot into OS, but not go into bootloader at all. I've never seen this once, after being on these forums extensively over the course of 4 different HTC Android devices.
Click to expand...
Click to collapse
Yes, Holding power + vol down makes it shutdown. After the screen goes dark, i tried to hold only vol down. nothing happends. tried to hold it for a few minutes. nothing.
When i release it, only after a few minutes, the device load the OS by itself (if i try to press the power button it doesn't work at all)
efi2222 said:
When i release it, only after a few minutes, the device load the OS by itself
Click to expand...
Click to collapse
So how do you know whether releasing the button is a condition of it booting, or a coincidence?
For that matter, how do you know it won't go to bootloader if vol down is held when it finally powers on?
I'd say the answer to both those questions is: you don't know. At least, not for sure.
How long is a "few minutes"? 3 minutes? 10 minutes?
Maybe hold down the vol down button with some tape, if you can hold it down manually the whole time?
It's doesn't really Matter, as the adb/ruu/quick bot app should have be able to load the bootloader....
efi2222 said:
It's doesn't really Matter, as the adb/ruu/quick bot app should have be able to load the bootloader....
Click to expand...
Click to collapse
It does matter. As I already explained, you should eliminate all possibilities. At least I assume that someone who genuinely want to fix the phone would try every possibility.
You spent about as much time replying, as it would have taken to try my suggestion.
I agree, I don't think it will work. But you don't know if you don't try.
I unlocked the bootloader and installed TWRP Recovery using the OP3 Tool. However now the phone will not boot unless I press the power button a few times. When it does boot I get the "Your device is not safe message", if I boot from here I get the OnePlus logo with the "powered by android" text but then it just shuts off. If I use the volume keys to select something else, I get nothing, the fastboot mode just gets stuck on the fastboot until I turn the device off, recovery just reboots to the "Your device is not safe screen".
Any help would be wonderful
McreativeH said:
I unlocked the bootloader and installed TWRP Recovery using the OP3 Tool. However now the phone will not boot unless I press the power button a few times. When it does boot I get the "Your device is not safe message", if I boot from here I get the OnePlus logo with the "powered by android" text but then it just shuts off. If I use the volume keys to select something else, I get nothing, the fastboot mode just gets stuck on the fastboot until I turn the device off, recovery just reboots to the "Your device is not safe screen".
Any help would be wonderful
Click to expand...
Click to collapse
Did you flash anything while you were unlocking the bootloader? The message is shown when the bootloader is unlocked so that is ok. Your phone, however, should turn on by long pressing the power button. You're getting a bootloop, If I were in such a situation I'd use the fastboot mode to flash the stock firmware again to get the phone working...
mharis05 said:
Did you flash anything while you were unlocking the bootloader? The message is shown when the bootloader is unlocked so that is ok. Your phone, however, should turn on by long pressing the power button. You're getting a bootloop, If I were in such a situation I'd use the fastboot mode to flash the stock firmware again to get the phone working...
Click to expand...
Click to collapse
I managed to get it working in the end by reflashing the stock recovery image ???? thank you for the help
McreativeH said:
I managed to get it working in the end by reflashing the stock recovery image ???? thank you for the help
Click to expand...
Click to collapse
Awesome! Enjoy :good: