Related
I was running jelly time no problems and all of a sudden the phone turned off and has a red blinking led on the bottom. i cant get into fastboot or recovery nothing.... dont understand cant turn on. even the ntoolki\t drivers dont look installed please give me suggestions i cant loose this phone.
Only thing I can think of is to fully charge it, then hold down power and volume down button.. hopefully it boots to fastboot - which you can then install stock ROM.
Also wrong section, should have been posted to General.
First of all, completely wrong area to post this. This does not belong in development. I'll report the thread to get it moved.
Second of all, a few people have noted these symptoms before. I believe some people were able to get out of it by plugging the phone in and repeatedly trying to reboot the phone or try to get into fastboot.
A few people had to RMA the device. Good luck.
slambkny said:
I was running jelly time no problems and all of a sudden the phone turned off and has a red blinking led on the bottom. i cant get into fastboot or recovery nothing.... dont understand cant turn on. even the ntoolki\t drivers dont look installed please give me suggestions i cant loose this phone.
Click to expand...
Click to collapse
This has been happened to quite a few people (including myself.) Here's a thread I made about it with other folks reporting the same thing as well. The only solution so far is to get a replacement.
Also, don't post things like this in the dev section.
Please post in the correct sections and in existing threads. Thanks.
Hello guys,
I'm in a very frustrating situation. After hours of research i finally post this because i couldn't find anything that helped yet.
So here's my problem:
I got my OnePlus2 today, wanted to root it straight away, and so i did. After installing TWRP and rooting my phone, i f'ed up (as i found out until now):
I went back into the developer options, disabled USB-Debugging as well as the OEM-lock, which allowed me to unlock the bootloader , because i wanted to disable developer options again (i like it clean). Bad idea, as it turns out. My bootloader is now locked again and could not be unlocked as of now, after hours of trying to figure out a way.
Another problem that came with it is the bootloop when i try to (re)start the device. The phone flashes the OnePlus-logo for half a second, vibrates, and starts again, over and over. The only way to get the phone out of the loop is by pressing POWER + VOLUME UP and booting into fastboot. Then i can do all the fastboot-commands on my PC, but i can't get into the recovery or flash anything because the bootloader is locked. Trying to 'fastboot oem unlock' only results in the device restarting and getting stuck in the bootloop i mentioned before again.
I managed to get the phone to work a few times by executing 'fastboot continue', which either starts to show the charging battery symbol or booting up like normal (about a 50% chance I'd say).
ADB commands can then be executed, but I'd need a way to flash a ROM without going into the bootloader or recovery, which seems to be impossible.
Is there any way you could help? Is there an ADB command to reset the phone to the state it was delivered, without me having any sort of backup? Or can the bootloader be unlocked via ADB?
Thanks a million in advance! :fingers-crossed:
Rattig said:
Hello guys,
I'm in a very frustrating situation. After hours of research i finally post this because i couldn't find anything that helped yet.
So here's my problem:
I got my OnePlus2 today, wanted to root it straight away, and so i did. After installing TWRP and rooting my phone, i f'ed up (as i found out until now):
I went back into the developer options, disabled USB-Debugging as well as the OEM-lock, which allowed me to unlock the bootloader , because i wanted to disable developer options again (i like it clean). Bad idea, as it turns out. My bootloader is now locked again and could not be unlocked as of now, after hours of trying to figure out a way.
Another problem that came with it is the bootloop when i try to (re)start the device. The phone flashes the OnePlus-logo for half a second, vibrates, and starts again, over and over. The only way to get the phone out of the loop is by pressing POWER + VOLUME UP and booting into fastboot. Then i can do all the fastboot-commands on my PC, but i can't get into the recovery or flash anything because the bootloader is locked. Trying to 'fastboot oem unlock' only results in the device restarting and getting stuck in the bootloop i mentioned before again.
I managed to get the phone to work a few times by executing 'fastboot continue', which either starts to show the charging battery symbol or booting up like normal (about a 50% chance I'd say).
ADB commands can then be executed, but I'd need a way to flash a ROM without going into the bootloader or recovery, which seems to be impossible.
Is there any way you could help? Is there an ADB command to reset the phone to the state it was delivered, without me having any sort of backup? Or can the bootloader be unlocked via ADB?
Thanks a million in advance! :fingers-crossed:
Click to expand...
Click to collapse
You might want to contact Naman Bhalla. I know he's helping out people fix bricked phones on xda as well as opo forums. I've messaged him as well. Hope he's got time today.
Till he replies, try to make sure that your battery stay charged, somehow.
Hetalk said:
You might want to contact Naman Bhalla. I know he's helping out people fix bricked phones on xda as well as opo forums. I've messaged him as well. Hope he's got time today.
Till he replies, try to make sure that your battery stay charged, somehow.
Click to expand...
Click to collapse
Thank you so very much! I will try to contact him.
Also battery should be no problem as I can boot the phone via fastboot. Either way, I'll have an eye on it!
Rattig said:
Thank you so very much! I will try to contact him.
Also battery should be no problem as I can boot the phone via fastboot. Either way, I'll have an eye on it!
Click to expand...
Click to collapse
I think he did message you. Check your private messages.
Hetalk said:
I think he did message you. Check your private messages.
Click to expand...
Click to collapse
Yes he did. Thanks a lot!
Rattig said:
Yes he did. Thanks a lot!
Click to expand...
Click to collapse
I'm glad your issue got resolved. :good:
If your issue is resolved then please post the solution for others it might help someone
The solution was simple i followed the guide below and it bought my phone back from the dead.
https://www.youtube.com/watch?v=R4SVSovw4Jo
sandeeppathak007 said:
If your issue is resolved then please post the solution for others it might help someone
Click to expand...
Click to collapse
I'm really sorry, I meant to post the solution but obviously I forgot...
So here's how I (with the help of aforementioned Naman Bhalla) fixed my OP2:
https:// forums.oneplus. net/threads/mega-unbrick-guide-for-a-hard-bricked-oneplus-2.347607/ (just remove the spaces i put in because I'm not allowed to post links just yet)
It's as simple as to follow the steps in this Guide. Take some time, read through it and everything should work out fine.
I can't really give more tips as I was lucky enough to be helped by the OP of the guide linked above. If nothing works for you, just try to PM him, he's a very nice and friendly guy!
Hi,
I've totally buggered my Note 3.
The only stage I can boot into something very similar to the attached photo.
I tried installing philz_touch_6.12.8-i9500.tar.md5 using Odin but when it reboots it just hangs at the boot logo screen.
TBH, I'm probably making it worse because it did have TWRP (see link below) but it coudln't install any ROM whatsoever, it just kept rebooting to the logo screen after a few seconds.
This all began when I followed this chap to letter but obviously didn't work out as expected:
https://www.youtube.com/watch?v=-i6DsGKTsJc
Would someone please point me in the right direction on how to bring my phone back to life or let me know if you can tell it's permanently screwed.
Thanks very much and really hope (pray!) you can help.
Just to say, I have sorted it.
Used the stock ROM via ODIN3.
Case closed.
Hi all,
I'm sure I am still one of many that cannot use XCnathan32's solution to fix their phones. I think the biggest problem is that it is difficult to discern between hardware vs. software being the culprit. If hardware, nothing I do can help. I've wanted to use the solution but when the computer cannot even find the device/recognize it, I cannot even start the solution. Let me explain what my phone is like/ the state the boot loader is in:
Google logo is the only thing to show.
Even when trying to boot from bootloader -> recovery mode, it only goes to the google logo and boot loops from there.
Unfortunately I did not unlock developer options / USB debugging so my bootloader is LOCKED, my computer does not recognize the 6P at all unless in boot loader. It gives a strange description of the device, but does not treat it as a device in the device manager. Even if it does show I cannot update it's driver. It essentially seems like only the bootloader is a device rather than the phone.
I have tried leaving the device to boot in hopes of it miraculously starting and allowing me to go to developer options, this has failed as well.
Would anyone know/ be willing to explain how to proceed from here? I'm sure the options are limited when the device does not even show up on the computer.
Note: I don't know much about TWRP, ADB, SDK etc, its all 2 days new to me.
Thanks for any help!
Take a trip to home Depot. Put your heat gun above the finger print unlock after getting power to 5%. Profit.
mattrb said:
Take a trip to home Depot. Put your heat gun above the finger print unlock after getting power to 5%. Profit.
Click to expand...
Click to collapse
I got it! Used a blowdryer though. Unfortunately it went back to boot looping even after I did a factory reset. I'm going to apply the fix now that OEM has been unlocked and USB debugging!
Archavius said:
I got it! Used a blowdryer though. Unfortunately it went back to boot looping even after I did a factory reset. I'm going to apply the fix now that OEM has been unlocked and USB debugging!
Click to expand...
Click to collapse
Congrats on getting it to work! Let me know if you need any help with flashing the modified images.
XCnathan32 said:
Congrats on getting it to work! Let me know if you need any help with flashing the modified images.
Click to expand...
Click to collapse
I'm currently writing a guide to get to the OEM unlock stage on your thread . Thanks so much for all of your work, my phone is currently booting. Its got the google logo with a unlocked pad lock on the bottom and then it switches to a section with android warnings saying "Device software cant be checked for corruption, please lock the bootloader".
Its actually bootlooping again... I've flashed all the images possible on your downloads part of the thread Not sure if there's another option to take to get rid of the bootlooping.
Archavius said:
Its actually bootlooping again... I've flashed all the images possible on your downloads part of the thread Not sure if there's another option to take to get rid of the bootlooping.
Click to expand...
Click to collapse
Have you been here? ?
Exodusche said:
Have you been here?
Click to expand...
Click to collapse
That's the exact guide I used. I also used his first guide before that one was published by XDA. It almost seems too simple though. I feel like I'm missing something. I flashed the 48B_A4 firmware, then the twrp3_1_1_4Cores.img and reboot. It still boot looped. I then proceeded to flash the other possible imgs to see if they would work. I cant flash the EX kernel since I can't boot into recovery since it just boot loops again.
mattrb said:
Take a trip to home Depot. Put your heat gun above the finger print unlock after getting power to 5%. Profit.[/QUOTE
Excuse my pessimism, but for real? I'm having the same issue, what exactly does this do?
Click to expand...
Click to collapse
JohnnyKilo said:
mattrb said:
Take a trip to home Depot. Put your heat gun above the finger print unlock after getting power to 5%. Profit.[/QUOTE
Excuse my pessimism, but for real? I'm having the same issue, what exactly does this do?
Click to expand...
Click to collapse
This will throttle the big cluster of processors making it so the phone can stop boot looping by using only the small clusters.
Click to expand...
Click to collapse
Archavius said:
JohnnyKilo said:
This will throttle the big cluster of processors making it so the phone can stop boot looping by using only the small clusters.
Click to expand...
Click to collapse
Format all partition except for internal storage.
1. Flash N2G48B_vendor.img into vendor partition
2. Flash N2G48B_4Cores.img into boot partition
3. Flash purenexus_angler-7.1.2-20170725-OFFICIAL.zip
4. Flash BeansGapps-Full-7.1.x-20170610.zip
5. Flash EX4_1_1_4Cores.zip (Elemental Kernel), step up the core speed one notch on first screen, leave the rest on default.
Reboot.
Waited about 10min on the animation screen (4 dot jumping), eventually phone completed booting
Click to expand...
Click to collapse
sorry to hijack your thread, can i know the steps that you took to enable oem unlock ?
Because i am in your similar situation, all i can see is the google logo & bootloader is locked (i cannot go to the settings menu because the phone doesnt bootup, i am stuck in the google logo).
If i run the fastboot flashing unlocl it fails (since bootloader is locked)
ShadowSounds said:
sorry to hijack your thread, can i know the steps that you took to enable oem unlock ?
Because i am in your similar situation, all i can see is the google logo & bootloader is locked (i cannot go to the settings menu because the phone doesnt bootup, i am stuck in the google logo).
If i run the fastboot flashing unlocl it fails (since bootloader is locked)
Click to expand...
Click to collapse
You need to use a heat gun or hair dryer above the fingerprint sensor. Keep phone at low battery but not empty. 5%
.....
mattrb said:
You need to use a heat gun or hair dryer above the fingerprint sensor. Keep phone at low battery but not empty. 5%
Click to expand...
Click to collapse
lol it worked. Thanks
ShadowSounds said:
lol it worked. Thanks
Click to expand...
Click to collapse
How did you know your battery was at 5%? At the fastboot screen I see that the battery says OK, but not a specific number. Does that battery field change when it gets below "OK"?
Archavius said:
I'm currently writing a guide to get to the OEM unlock stage on your thread . Thanks so much for all of your work, my phone is currently booting. Its got the google logo with a unlocked pad lock on the bottom and then it switches to a section with android warnings saying "Device software cant be checked for corruption, please lock the bootloader".
Click to expand...
Click to collapse
This is my phone. Can you help me?
Hi there - I ended up having to use a blow dryer to throttle the phone using High heat. I wouldn't recommend it, it wasnt safe and my phone after fixing stopped working in an hour. If your phone isn't working despite following the fix above get a new phone, the pixel 3a seems like a nice new option, good luck!
Stuck in recovery mode
Archavius said:
JohnnyKilo said:
This will throttle the big cluster of processors making it so the phone can stop boot looping by using only the small clusters.
Click to expand...
Click to collapse
OK, I don't have a bootloop problem per se, but I changed my battery and now it only goes to the Reboot bootloader screen. The arrow keys don't work to change the menu. Sometimes I can get it to Recovery mode, but neither the power key or arrow keys will work. Once I got it to the Start, but the power key did nothing. ADB devices returns nothing, so even though I installed the Google USB drivers in Android Studio I can't get the computer and the Nexus to talk to each other. I'm ready to try heating the device, but that goes against everything I've ever known about electronic devices. Are you sure? .
Click to expand...
Click to collapse
Don't heat up your phone, this thread is uselss for you.
Hi all, thanks to developers for their good job.
I have a zte axon 7 2017G with an official lineageOS 15.1 and I'm experiencing a weird and annoying boot process each time I reboot the device:
1.- First I see a screen saying push any button before 5 secs
2.- Despite push or not any button, I see a pretty similar screen saying that I have 30 sec to push any button to continue boot process.
If no key is pressed, the boot process start again and again and the device never start up.
Only the volume down button works and I can see more boot options, but even it move the options in wrong direction (from bottom to up), the volume up button doesn't work at all.
I've tried different bootstacks, but the boot process doesn't change.
Is there any bootstack, or aboot image or some "magical" process that I could do to change the boot process into a more working one?
Thanks in advance for the help
Are you serious dude,there are dozen of threads and mentions about this.
On the second screen you press the power button to proceed booting(pinguin logo is normal).just like the bootscreen is saying.
if you dont want this you can use other bootstack
Predatorhaze said:
Are you serious dude,there are dozen of threads and mentions about this.
On the second screen you press the power button to proceed booting(pinguin logo is normal).just like the bootscreen is saying.
if you dont want this you can use other bootstack
Click to expand...
Click to collapse
Hi predartorhaze, thanks for your info. Yes I'm serious, I'm know how to manage to boot my device, but what I want is to change this behavior for a lot of reason, one of them is if the device reboot itself, it will keep booting until exhaust the battery or a human being push buttons.
Please, could you share a link with a bootstack to change this behaviour. As I said, I've tried some, and all of them have the same behaviour.
starvoid said:
Hi predartorhaze, thanks for your info. Yes I'm serious, I'm know how to manage to boot my device, but what I want is to change this behavior for a lot of reason, one of them is if the device reboot itself, it will keep booting until exhaust the battery or a human being push buttons.
Please, could you share a link with a bootstack to change this behaviour. As I said, I've tried some, and all of them have the same behaviour.
Click to expand...
Click to collapse
go here https://forum.xda-developers.com/axon-7/how-to/guide-axon-7-path-to-havocos-2-0-pie-t3869732
and try B20 Bootstack by DrakenFX - Modified by Verequies (Splash or NoSplash)
Read the faq for the difference with splash or no splash
Predatorhaze said:
go here https://forum.xda-developers.com/axon-7/how-to/guide-axon-7-path-to-havocos-2-0-pie-t3869732
and try B20 Bootstack by DrakenFX - Modified by Verequies (Splash or NoSplash)
Read the faq for the difference with splash or no splash
Click to expand...
Click to collapse
Thanks predatorhaze, it works as I expected. I tried the splash version, in order to not to loose EDL mode, just in case. Only one 5 second warning screen shows up and if no one button is pressed, the boot process finish completely instead reboot again.
Only one warning just in case anyone would try it. The pin to unlock the phone is lost, and you would not be able to unlock it.
starvoid said:
Thanks predatorhaze, it works as I expected. I tried the splash version, in order to not to loose EDL mode, just in case. Only one 5 second warning screen shows up and if no one button is pressed, the boot process finish completely instead reboot again.
Only one warning just in case anyone would try it. The pin to unlock the phone is lost, and you would not be able to unlock it.
Click to expand...
Click to collapse
You can unlock pin in twrp.B20 splash does not have warning screen for me,i use it too