Develop Bugs

Did I ruin my phone?

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.

Bricked Nexus 5x? DP4 OTA issues...

So, started my OTA DP4 update with N today... on the reboot it just got stuck in a loop. Over, and over, and over... after about an Hour I decided try and power it off and manually boot up. Same thing. I can get to fastboot and I can see it using the fastboot commands. However, my device is OEM locked . I cannot unlock it. So I decided to try and boot to recovery and try to fix it that way... no dice! I get a dead Android with a Red Exclamation and a message that says "No command".
Anyone have any help or ideas on what I can do?
Thanks in advance!

dbaker0926 said:
I get a dead Android with a Red Exclamation and a message that says "No command".
Anyone have any help or ideas on what I can do?
Click to expand...
Click to collapse
Fallen down (dead) android is just an image overlay, like a book cover.
To get to the recovery menu do the following
While pressing [Power]
Press/Release [Vol+]
Release [Power]
Then go and do a factory reset.
Alternatively, I am guessing you could get past your bootloop by booting to bootloader and typing (not sure if these are allowed with locked bootloader)
fastboot erase user
fastboot format user
BTW bootloop is not the same thing as a brick. The latter is much more serious.

sfhub said:
Fallen down (dead) android is just an image overlay, like a book cover.
To get to the recovery menu do the following
While pressing [Power]
Press/Release [Vol+]
Release [Power]
Then go and do a factory reset.
Alternatively, I am guessing you could get past your bootloop by booting to bootloader and typing (not sure if these are allowed with locked bootloader)
fastboot erase user
fastboot format user
BTW bootloop is not the same thing as a brick. The latter is much more serious.
Click to expand...
Click to collapse
Perfect! This was the piece I was missing. Thanks, I think I am all set now

[Solved] Unlocked Bootloader now having trouble

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:

Unlocked boot advise, how to get rid of it?

Hi ppl,
I've unlocked my bootloader and now, every time i power on the OP3, shows a screen saying my phone is insecure because it is unlocked, and offer key settings to go recovery menu, etc.
It shows about 3 seconds and continues the booting process.
Is there any way to flash my own image or something to hide it (as i did on my old moto g/g3-te)?
Thanks.
Sergio.

Nope, you'll have to live with it.
You can skip that message by pressing power button, but there's no way to remove it.
Sent from my OnePlus 3 using Tapatalk

recrunchi said:
Hi ppl,
I've unlocked my bootloader and now, every time i power on the OP3, shows a screen saying my phone is insecure because it is unlocked, and offer key settings to go recovery menu, etc.
It shows about 3 seconds and continues the booting process.
Is there any way to flash my own image or something to hide it (as i did on my old moto g/g3-te)?
Thanks.
Sergio.
Click to expand...
Click to collapse
Other way of removing that message is to lock the bootloader.
Type in terminal: fastboot oem lock. this will wipe clean the userdata and you'll need to install everthing again.
You can't remove that message with the unlocked bootloader. You'll have to live with it.

Unable to boot into system or recovery after locking bootloader

So after locking the bootloader in an attempt to get Android Pay to work, my OP3 tried to reboot itself but the only thing that happens is the Android logo flashes for half a second and the phone vibrates as it usually does when I boot it, then the screen goes dark for a second, and it repeats continuously like this. I'm completely unable to use my phone because of this.
I've tried entering fastboot mode which seems to work but when I try to enter recovery mode or start the phone, the same thing happens. I can only power off or restart the bootloader from this screen.
I'm assuming the bootloader is locked because the device state is displayed as locked in red while I'm in fastboot mode (or bootloader mode?).

Skred300 said:
So after locking the bootloader in an attempt to get Android Pay to work, my OP3 tried to reboot itself but the only thing that happens is the Android logo flashes for half a second and the phone vibrates as it usually does when I boot it, then the screen goes dark for a second, and it repeats continuously like this. I'm completely unable to use my phone because of this.
I've tried entering fastboot mode which seems to work but when I try to enter recovery mode or start the phone, the same thing happens. I can only power off or restart the bootloader from this screen.
I'm assuming the bootloader is locked because the device state is displayed as locked in red while I'm in fastboot mode (or bootloader mode?).
Click to expand...
Click to collapse
Congratulations, you have succesfully hardbricked you device.
Try method 1 from below link if it does not work, method 2 will but you'll lose All your data.
https://forums.oneplus.net/threads/guide-mega-unbrick-guide-for-a-hard-bricked-oneplus-3.452634/

danecr7 said:
Congratulations, you have succesfully hardbricked you device.
Try method 1 from below link if it does not work, method 2 will but you'll lose All your data.
https://forums.oneplus.net/threads/guide-mega-unbrick-guide-for-a-hard-bricked-oneplus-3.452634/
Click to expand...
Click to collapse
Turns out I just needed to unlock the bootloader again. That seems to have done the trick for this issue.

Skred300 said:
Turns out I just needed to unlock the bootloader again. That seems to have done the trick for this issue.
Click to expand...
Click to collapse
OK that's fine, mine suffered the same things but the bootloader was still unlocked.