Hi,
I have a rooted nexus 6p, all was well until it decided to reboot and boot-loop when I opened my music app. I get as far as the white Google logo then the phone restarts and I'm back to the normal warning then Google logo then reboot.
I have managed to get into the recovery screen (with the android laying down) but when i choose recovery mode the phone just starts boot-looping again.
I am wondering if I have somehow managed to hard brick it?
I have tried to flash the latest OS onto my phone but it said no signature.
I did managed to wipe the device also.
Thanks for any help.
Are you on Nougat or still on MM? Since you're rooted, it means you didn't receive an OTA. Did you flash it yourself, originally?
istperson said:
Are you on Nougat or still on MM? Since you're rooted, it means you didn't receive an OTA. Did you flash it yourself, originally?
Click to expand...
Click to collapse
When my phone started playing up I was still on MM 6.0.1, I tried to flash N after the boot-looping started.
Thanks
Related
Hi,
I have dropped my phone few weeks back and cracked the screen. Still it was in working condition and every thing seemed working fine. But during the last few weeks my phone has received the OTA updates and now it is on Android 2.3.6. Now my phone is rebooting on it own. If I try to reboot it never reboots. When I try to reboot in 'Android Reboot with No BP' option, it reboots and every thing seems working fine but in few minutes it starts rebooting again on its own. Not sure when I dropped the phone it got some hardware damage or the OTA updates causing this reboot issue.
When I tried to boot up using 'Boot Android (no BP)' option it at least boots up and shows me Motoblur log in screen but again with in few seconds it goes back to boot up mode. Some times it stays for 5 to 10 minutes but never stays there more than 10 minutes and it goes back to boot loop.
I have unlocked my Atrix using Automatic boot loader tool. Did not help. Tried to flash with Motorola .SBF files both 2.3.4 and 2.3.6, no luck either. Did the factory reset, wipe out the cache etc....no luck.
I have even tried to install custom ROM (NottachTrix 4G), that didn't help either.
I am thinking it might have caused by Android 2.3.6 updates. So I want to try to flash it with a custom ROM which is built on 2.3.4 or lower but afraid to do that thinking I might hard brick my phone.
Any help is greatly appreciated.
Thanks,
GPR789GPR
Well, unfortunately with the screen cracked, you can't return to Motorola. I had a goof with my Atrix when I first got it because I accidentally did a SBF flash to the wrong version and it bricked the phone and fried the motherboard and Motorola replaced it because I said the Gingerbread update messed it up. Ha.
Anyways, since returning to Moto is not an option for you, I would just go ahead and try to install a custom ROM, maybe try Neutrino ROM 2.2 or 2.5?
Do you have ROMRacer Recovery or CWM Recovery installed? Will it let you get into it? If so, put a custom ROM on your SD card, do a wipe data and cache and install it.
I'm no expert, but I have noticed no one else replied and just trying to help.
Hope all works out for you!
Boot loop issue - at&t Android 2.3.6
Thanks andreww88 for your reply. I read in one of the forums that once the phone is updated with 2.3.6 don't try to go back to older versions especially lower than 2.3.4. That would make the phone to be hard bricked. That is why I didn't try any other ROM other than NottachTrix 4G because it is built on 2.3.6. I could be wrong. That is why I need some guidance to try any other custom ROM.
i had the same issue. What i did was get the Atrix Fastool and whipe the phone. Then i extracted the sbf for 141 and then flashed 59 60 and 61 smg files from fastboot. After that everything worked properly. To then unlock my bootloader i used the flashing script and i was set. This is recoverable not easy but you can recover.
Thanks Moneyman1978 for your reply. Can you be more detail what you did to resolve this issue. Can you send me the links or point me to Fastool and 141 .SBF file also SMG files. Thanks again.
gpr789gpr said:
Hi,
I have dropped my phone few weeks back and cracked the screen. Still it was in working condition and every thing seemed working fine. But during the last few weeks my phone has received the OTA updates and now it is on Android 2.3.6. Now my phone is rebooting on it own. If I try to reboot it never reboots. When I try to reboot in 'Android Reboot with No BP' option, it reboots and every thing seems working fine but in few minutes it starts rebooting again on its own. Not sure when I dropped the phone it got some hardware damage or the OTA updates causing this reboot issue.
When I tried to boot up using 'Boot Android (no BP)' option it at least boots up and shows me Motoblur log in screen but again with in few seconds it goes back to boot up mode. Some times it stays for 5 to 10 minutes but never stays there more than 10 minutes and it goes back to boot loop.
I have unlocked my Atrix using Automatic boot loader tool. Did not help. Tried to flash with Motorola .SBF files both 2.3.4 and 2.3.6, no luck either. Did the factory reset, wipe out the cache etc....no luck.
I have even tried to install custom ROM (NottachTrix 4G), that didn't help either.
I am thinking it might have caused by Android 2.3.6 updates. So I want to try to flash it with a custom ROM which is built on 2.3.4 or lower but afraid to do that thinking I might hard brick my phone.
Any help is greatly appreciated.
Thanks,
GPR789GPR
Click to expand...
Click to collapse
Well, I had a similar issue. I did the 4.5.141 (OS 2.3.6) OTA update and then it would just bootloop. I'm on stock, rooted, locked BL. I then ran the OTA update again via recovery and that didn't help. I then did a full factory reset, then update via recovery and still didn't fix anything (good thing I had TiBu backup). After calling AT&T they finally admitted that Moto recalled the 4.5.141 build update since there was WIDESPREAD boot-loop issues with many Atrix users. Great.
They're sending me a new phone. Luckily, mine is in good condition.
Any one please have any suggestions for me. Do you think it is a hardware issue or can it be fixed by fixing the software??? Any help is appreciated.
If any of you has any ideas about how to fix this issue I would appreciate if you can share it here.
Hey Guys, I updated OTA to Android N from 6.0.1 (Marshmallow). After the upgrade all services crash (all google services including Messenger SMS) and the phone reboots every few minutes.
-Boot-loader is locked.
-No Custom Recovery Image.
-Oddly, entering stock recovery from boot-loader results in "No Command" error message.
Ideas??
Probably something went wrong in the update process and conflicted with something else.
Anyway: hard reset.
The "no command" screen is just a security screen and it's normal, you need to bypass it to enter to the recovery with a button combination (that now I don't remember, but I never remembered it even though I used to enter in recovery after pressing random buttons combinations lol).
Thanks dude. No worries.
Hard reset didn't work. Also tried to flash OTA from Recovery..
I was really hoping to avoid the stock ROM.
For now, I unlocked the bootloader, installed Recovery, and then loaded Stock ROM. All is well under Stock ROM.
Will try again tomorrow.
cybrdude said:
Thanks dude. No worries.
Hard reset didn't work. Also tried to flash OTA from Recovery..
I was really hoping to avoid the stock ROM.
For now, I unlocked the bootloader, installed Recovery, and then loaded Stock ROM. All is well under Stock ROM.
Will try again tomorrow.
Click to expand...
Click to collapse
I've included full instructions on how to safely update in my guide here:
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
(section 14)
cybrdude said:
Hey Guys, I updated OTA to Android N from 6.0.1 (Marshmallow). After the upgrade all services crash (all google services including Messenger SMS) and the phone reboots every few minutes.
-Boot-loader is locked.
-No Custom Recovery Image.
-Oddly, entering stock recovery from boot-loader results in "No Command" error message.
Ideas??
Click to expand...
Click to collapse
Press power + volume up to get recovery menu.
Was having a similar issue. I'm all stock, unlocked bootloader. Signed for N preview and instantly got the OTA download. It installed and pretty much within a few minutes the bootloops started. couldn't even power down without it rebooting on its own. I got it to power down without turning itself back on through recovery/power down. I let it sit and cool down. Upon reboot.....was doing well, and started to boot loop again. I REALLY did not want to factory reset.
Heisenberg said:
I've included full instructions on how to safely update in my guide here:
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
(section 14)
Click to expand...
Click to collapse
Thanks dude, but not a newb. Not using my old account, which I should recover.
I had no issue restoring to stock after unlocking bootloader and flashing Recovery. Strange that the OTA via beta is unstable for some and not for others. Even after a reset of OTA, the services and reboot issues continued.
So for me, a factory reset and setting up a brand new phone (no backups of any kind....even from Google) have seem to do the trick. Unfortunate that I lose my wifi password backups. Asking some people for their wifi passwords again is a PIA. Especially the ones who don't know them, and it's a 27 key password from their cable company. Anyone know how to pull just the wifi backups from google?
My thought is one app or setting was causing my problem so I'm slowing adding everything one at a time. PIA really. I don't miss the Froyo days that's for sure.
cybrdude said:
Thanks dude, but not a newb. Not using my old account, which I should recover.
I had no issue restoring to stock after unlocking bootloader and flashing Recovery. Strange that the OTA via beta is unstable for some and not for others. Even after a reset of OTA, the services and reboot issues continued.
Click to expand...
Click to collapse
What happened to your old account?
Hi all, I ve updated my device to 7.1.2 beta via OTA the day before. Several hours ago, it started bootlooping after experiencing a battery drain.
Locked, out of warranty, cannot get into recovery mode.
I am giving up this device but does anyone know how can I restore my data from the phone?
Vince.L said:
Hi all, I ve updated my device to 7.1.2 beta via OTA the day before. Several hours ago, it started bootlooping after experiencing a battery drain.
Locked, out of warranty, cannot get into recovery mode.
I am giving up this device but does anyone know how can I restore my data from the phone?
Click to expand...
Click to collapse
If you are fully on stock and an OTA boot looped your phone I would contact Google and see if they will do anything to help you. Even out of warranty Google should accept responsibility for screwing up people's phones with their OTA. I had the same problem with the OTA but my bootloader was unlocked so I could flash a factory image and get my phone back. I was able to get to fastboot menu by playing with the power and volume keys for a while. If you can get to that menu you might be able to factory reset your phone or side load the Feb OTA. I don't think you can recover your phone data in the phone's current state.
if you have only access to Fastboot so you cannot backup any data unless somehow install recovery boot to recovery.
Geeks Empire said:
if you have only access to Fastboot so you cannot backup any data unless somehow install recovery boot to recovery.
Click to expand...
Click to collapse
Why are you spamming this forum? Please leave your personal advertisements out of your posts.
can't you sideload the ota file of a 7.1.1 rom? you should be able to access bootloader screen.
if it's not the bootloop of death that's been happening around here (included me) you can download an ota file from google factory image page and sideload it
jhs39 said:
If you are fully on stock and an OTA boot looped your phone I would contact Google and see if they will do anything to help you. Even out of warranty Google should accept responsibility for screwing up people's phones with their OTA. I had the same problem with the OTA but my bootloader was unlocked so I could flash a factory image and get my phone back. I was able to get to fastboot menu by playing with the power and volume keys for a while. If you can get to that menu you might be able to factory reset your phone or side load the Feb OTA. I don't think you can recover your phone data in the phone's current state.
Click to expand...
Click to collapse
Maybe i could donate to the websiteand we can get a thread up and runnig becuaseit took my over an hourto find a fix i havnt even tried yetin regards to the 71.1.1 bootloos onthe Goggle screen as well as the spash scrren, ihave sence lost the spalh screen now its juts black and white google
Some people have reported that the Skipsoft Toolkit got them out of a bootloop. I haven't tried it myself but I think you are giving up too easily. I've gotten lost of phones into boot loops but I don't panic because there is usually a way out. That isn't always the case with the 6P since there is the boot loop of death issue, but I still wouldn't give up just yet.
[My phone is already repaired by Samsung under warranty, my internal storage was broken so they replaced the motherboard. There is no need to reply to this thread anymore. Thanks anyway]
Hello everyone, I need help!!!!
Today my Samsung GS6 Edge+ died. (At least, that's what I think)
I own my G928F for 1,5 years now. I rooted it two weeks after that. Several weeks ago I flashed a new ROM called N-Lite Nougat v4.1 which has worked smoothly and without any problems since I've flashed it.
However, today, the 26th of June, my phone turned off all of a sudden while scrolling through Facebook. I haven't flashed, installed nor done, anything that would affect my phone in such a way that it would crash this way. I tried force rebooting with the 3 buttons pressed (Home, Vol+, On/Off) several times. My phone just boots into the ROM and then freezes instantly. Again tried force rebooting for like 5 times, NO luck. Then I tried booting into recovery mode (TWRP 3.1.0.0), cleared Dalvik and cache, factory reset, rebooted, still no luck. Tried several other custom ROM's, still NO luck. Also tried flashing stock Samsung Firmware using ODIN, no luck whatsoever.
I couldn't find any similar problems in the ROM thread, nor anywhere else on the internet. Besides that, I'm starting to think this problem is a defect to the hardware, not the software.
Does anyone know what would be the best thing to do in my situation? Or perhaps anyone who might know what the problem might be and have a possible solution?
Thanks in Advance.
Recovery mode (TWRP 3.1.0.0) is accessible though, but that's all. While trying to install another ROM it just reboots randomly, during flashing progress.
When you say you tried flashing stock rom with ODIN, does it fail or does it succeed but freezes up when you are back in android OS?
kdogguk said:
When you say you tried flashing stock rom with ODIN, does it fail or does it succeed but freezes up when you are back in android OS?
Click to expand...
Click to collapse
It succeeds. But when it's done it just keeps going in a bootloop. It doesn't even boot into Android now. I've used the right settings in Odin. Even tried several different versions of Odin. No success
Larss97 said:
It succeeds. But when it's done it just keeps going in a bootloop. It doesn't even boot into Android now. I've used the right settings in Odin. Even tried several different versions of Odin. No success
Click to expand...
Click to collapse
Out of curiosity, when you flashed the stock Rom was it 6.0.1 or 7.0?
Does it just get stuck on the S6 EDGE + screen for a while? If so you might be to impatient as first boot on almost all roms both custom or stock take a while to boot up. If it shows the Samsung splash screen over and over then yes it's bootlooping.
I can't think of any other reason for it bootlooping, especially if you have flashed a stock Rom, unless maybe you flashed 7.0 rom and still have a 6.0.1 bootloader. But I think that just causes loss of baseband, not a bootloop.
I would suggest another kernel, but that is normally included in the stock rom.
Do you download them from sammobile or another site? If it's another site, is it a reliable site?
kdogguk said:
Out of curiosity, when you flashed the stock Rom was it 6.0.1 or 7.0?
Does it just get stuck on the S6 EDGE + screen for a while? If so you might be to impatient as first boot on almost all roms both custom or stock take a while to boot up. If it shows the Samsung splash screen over and over then yes it's bootlooping.
I can't think of any other reason for it bootlooping, especially if you have flashed a stock Rom, unless maybe you flashed 7.0 rom and still have a 6.0.1 bootloader. But I think that just causes loss of baseband, not a bootloop.
I would suggest another kernel, but that is normally included in the stock rom.
Do you download them from sammobile or another site? If it's another site, is it a reliable site?
Click to expand...
Click to collapse
It was Android 7.0. I downloaded it from Sammobile. I've waited 40 minutes for it to boot up after successful Odin flash. But it just kept doing the same thing. The bootloader that was installed was a 7.0 bootloader. First i get the Samsung Galaxy S6 Edge + screen then the Samsung boot animation and it repeats for hours untill battery runs out haha
Larss97 said:
It was Android 7.0. I downloaded it from Sammobile. I've waited 40 minutes for it to boot up after successful Odin flash. But it just kept doing the same thing. The bootloader that was installed was a 7.0 bootloader. First i get the Samsung Galaxy S6 Edge + screen then the Samsung boot animation and it repeats for hours untill battery runs out haha
Click to expand...
Click to collapse
The last thing I can think of was did you get the right rom for your phone? 928F or 928T etc.
Other than that it might be a trip to the repair centre I'm afraid.
Larss97 said:
It was Android 7.0. I downloaded it from Sammobile. I've waited 40 minutes for it to boot up after successful Odin flash. But it just kept doing the same thing. The bootloader that was installed was a 7.0 bootloader. First i get the Samsung Galaxy S6 Edge + screen then the Samsung boot animation and it repeats for hours untill battery runs out haha
Click to expand...
Click to collapse
Try to do a factory reset in the stock recovery. It might help.
vishnu8058 said:
Try to do a factory reset in the stock recovery. It might help.
Click to expand...
Click to collapse
Done that, no success
kdogguk said:
The last thing I can think of was did you get the right rom for your phone? 928F or 928T etc.
Other than that it might be a trip to the repair centre I'm afraid.
Click to expand...
Click to collapse
Yeah i got the right rom for my phone. I've already sent it to a certified Samsung repair centre, it's still under warranty. Thanks for the help anyway
I dug out my old Nexus 10 (mantaray/manta) to mess with it and firstly it booted up fine and I updated Android to 5.1.1 (system update). All was well. I was going to flash Pie onto it, so I booted to the bootloader and connected it and unlocked it via fastboot oem unlock. Ever since I did that it will not get passed the boot (colorful balls) screen. I can get back into the bootloader. Next I cleared the cache and then also did a factory reset, same issue. So I flashed the official 5.1.1 (LMY49J) image, and still have the same issue!
No clue how to get to some state where I can boot this thing. My end goal is to have Android Pie / vanilla on it. What should I do?
Edit: I think what I did was I flashed an update rather than the full OTA. I can't find it, so maybe someone can point me to it?
jsm11482 said:
I dug out my old Nexus 10 (mantaray/manta) to mess with it and firstly it booted up fine and I updated Android to 5.1.1 (system update). All was well. I was going to flash Pie onto it, so I booted to the bootloader and connected it and unlocked it via fastboot oem unlock. Ever since I did that it will not get passed the boot (colorful balls) screen. I can get back into the bootloader. Next I cleared the cache and then also did a factory reset, same issue. So I flashed the official 5.1.1 (LMY49J) image, and still have the same issue!
No clue how to get to some state where I can boot this thing. My end goal is to have Android Pie / vanilla on it. What should I do?
Edit: I think what I did was I flashed an update rather than the full OTA. I can't find it, so maybe someone can point me to it?
Click to expand...
Click to collapse
Mine does it aswell, but after like 20 min it boots up. I flash mine with the "Nexus Rool Toolkit" with the option "Flash Stock + Unroot", in your case i wull put the radio button on "Softbrick/Bootloop". Then follow the steps on the screen and then when it reboots the programm will tell you that you need to wait like 20 min. And then it should be up and running again