My nexus 6p has gone into a bootloop at random. I didn't flash or do anything. Its unlocked and rooted running cataclysm rom 6.0.1. Suddenly it started bootlooping but i can access the bootloader. Recovery is not accessible it just bootloops. So I tried flashing factory image from skipsoft toolkit and also by myself from command prompt. But still unfortunately it is bootlooping except in bootloader mode. Can anyone please help me?
After flashing the factory images did you leave it stock? And it's still looping while on fully stock firmware?
Heisenberg said:
After flashing the factory images did you leave it stock? And it's still looping while on fully stock firmware?
Click to expand...
Click to collapse
Yes I didn't do anything after that.. I just flashed the factory images bh toolkit and manually also and just after that booted with no luck.
suneet mehta said:
Yes I didn't do anything after that.. I just flashed the factory images bh toolkit and manually also and just after that booted with no luck.
Click to expand...
Click to collapse
When you flashed manually did you flash every image? Have you flashed or formatted userdata?
Heisenberg said:
When you flashed manually did you flash every image? Have you flashed or formatted userdata?
Click to expand...
Click to collapse
Yes i flashed bootloader and radio first while rebooting bootloader after each of them. Then i erased system recovery boot vendor userdata. Then i flashed each one of them and rebooted. I also tried two different factory images just to be sure the mtc19t and mtc19x.
suneet mehta said:
Yes i flashed bootloader and radio first while rebooting bootloader after each of them. Then i erased system recovery boot vendor userdata. Then i flashed each one of them and rebooted. I also tried two different factory images just to be sure the mtc19t and mtc19x.
Click to expand...
Click to collapse
I'm not sure then, you might be dealing with a hardware failure.
Heisenberg said:
I'm not sure then, you might be dealing with a hardware failure.
Click to expand...
Click to collapse
Also once after flashing I had selected the factory option in the bootloader menu hoping it means factory data reset. Does that have anything to do with this?
suneet mehta said:
Also once after flashing I had selected the factory option in the bootloader menu hoping it means factory data reset. Does that have anything to do with this?
Click to expand...
Click to collapse
I doubt it.
Heisenberg said:
I doubt it.
Click to expand...
Click to collapse
Well, I figured the same. Anyways thanks buddy. I'll check with google now.
Related
HI all,
My nexus 4 just won't boot no matter how i flash any 4.3 version on it.
Tried google's factory image's bat file, efrant's guide, fota, ota file and some custom roms.
Tried each with wiping cache followed by factory settings.
I'm really lost, how could it be?
At which point does it stop?
bootloop, x screen.
You tried using the factory images from google's website? I had to wipe mine recently and flash the bootloader, reset fastboot, flash radio, reset bootloader, and then flash zip with the Boot/System/UserData/Etc in it and then once it was complete booted up fine. Might want to give it another shot, but don't forget to reboot the bootloader between flashes. It does help.
MisterRich said:
You tried using the factory images from google's website? I had to wipe mine recently and flash the bootloader, reset fastboot, flash radio, reset bootloader, and then flash zip with the Boot/System/UserData/Etc in it and then once it was complete booted up fine. Might want to give it another shot, but don't forget to reboot the bootloader between flashes. It does help.
Click to expand...
Click to collapse
I got stuck on this. I was really worried that I'd have to leave my brand new N4.
I ended up flashing Google's stock 4.2.2 images for everything, relocking bootloader then unlocking it. Then at that point, when you are in fastboot make sure you click start. It'll then show the android with a progress bar, just wait from there and it'll boot. I'm sure Google will fix these issues with 4.3.1
I just got my nexus 6p. I turned it off and back on and now it's stuck at the "spinning circles" phase. I tried wipe the cache partition but, it didn't help.
any suggestions?
thanks.
Hal
Factory reset. Worst case you can download the factory image from google and reset it that way.
stuck in bootloop, need help.
Aridon said:
Factory reset. Worst case you can download the factory image from google and reset it that way.
Click to expand...
Click to collapse
i attempted to flash SU after installing TWRP and got stuck in bootloop, I need help getting out of it.
CitySlicka said:
i attempted to flash SU after installing TWRP and got stuck in bootloop, I need help getting out of it.
Click to expand...
Click to collapse
You need to flash boot.img
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
step 5
ShaunWinSC said:
You need to flash boot.img
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
step 5
Click to expand...
Click to collapse
I was able to restore phone via Skipsoft Toolkit. That tool is a lifesaver.
My N10 with stock 5.1 previously had root with TWRP 2.8.6, but for some reason it recently lost root. In addition, it seems that TWRP has been corrupted because whenever I try to boot into recovery I get a dead bootloader with a red exclamation mart. After I flashed the most recent version of TWRP 3.0.0-1 using "fastboot flash recovery twrp-3.0.0-1-manta.img" (bootloader still unlocked), I still get a dead bootloader when booting into recovery.
Then I flashed back to TWRP 2.8.6, but the problem remains!
How to fix the problem? Thanks!
I hope you can go to bootloader mode... Revert to stock by flashing the factory images and then start over again
nitin.chobhe said:
I hope you can go to bootloader mode... Revert to stock by flashing the factory images and then start over again
Click to expand...
Click to collapse
Thanks!
Just flashed an even older version (2.8.5) of TWRP, and now suddenly it can boot into recovery without any problem. I have also gained root now after flashing SuperSU.
I was planning to flash the most recent version of TWRP (3.0.0-1), and then try out CM13, but for some reason my N10 with stock 5.1 does not like those newer versions of TWRP. Do you know why?
mj56gt said:
Thanks!
Just flashed an even older version (2.8.5) of TWRP, and now suddenly it can boot into recovery without any problem. I have also gained root now after flashing SuperSU.
I was planning to flash the most recent version of TWRP (3.0.0-1), and then try out CM13, but for some reason my N10 with stock 5.1 does not like those newer versions of TWRP. Do you know why?
Click to expand...
Click to collapse
No, I do not konw that. Are you flashing correct version of TWRP made for manta?
nitin.chobhe said:
No, I do not konw that. Are you flashing correct version of TWRP made for manta?
Click to expand...
Click to collapse
I downloaded all the three versions (2.8.5, 2.8.6, and 3.0.0-1) of TWRP I've flashed so far from here:
https://dl.twrp.me/manta/
This is weird. Is it because I didn't have root during the time I flashed 2.8.6 or 3.0.0-1? I thought that flashing TWRP would not require root.
Can I flash CM13 with TWRP 2.8.5? I'll definitely make a Nandroid backup before proceeding.
mj56gt said:
I downloaded all the three versions (2.8.5, 2.8.6, and 3.0.0-1) of TWRP I've flashed so far from here:
https://dl.twrp.me/manta/
This is weird. Is it because I didn't have root during the time I flashed 2.8.6 or 3.0.0-1? I thought that flashing TWRP would not require root.
Can I flash CM13 with TWRP 2.8.5? I'll definitely make a Nandroid backup before proceeding.
Click to expand...
Click to collapse
With nandroid, you are good to go.
Should be possible :fingers-crossed:
nitin.chobhe said:
With nandroid, you are good to go.
Should be possible :fingers-crossed:
Click to expand...
Click to collapse
I did factory reset in TWRP 3.0.0-1 and then flashed CM 13.0-20160309 on my N10 with the dynamic Gapps. Now I get this error Unfortunately Google Play Services Has Stopped. Is it because the default factory reset is not good enough or something else? If it needs a full wipe, what exactly should I wipe, system and data? And after a full wipe, do I need to reflash CM13 or just Gapps?
Thanks!
mj56gt said:
I did factory reset in TWRP 3.0.0-1 and then flashed CM 13.0-20160309 on my N10 with the dynamic Gapps. Now I get this error Unfortunately Google Play Services Has Stopped. Is it because the default factory reset is not good enough or something else? If it needs a full wipe, what exactly should I wipe, system and data? And after a full wipe, do I need to reflash CM13 or just Gapps?
Thanks!
Click to expand...
Click to collapse
Problem solved: Just flashed the pico Gapps, and now everything works fine. For some reason the dynamic Gapps didn't work for me.
mj56gt said:
Problem solved: Just flashed the pico Gapps, and now everything works fine. For some reason the dynamic Gapps didn't work for me.
Click to expand...
Click to collapse
May be there isn't enough space to flash them.
Happy that is working now
Sent from my Nexus 4 using XDA Free mobile app
I first rooted my Nexus 6p that was completely stock using the system less root method. After I flashed the modified boot and twrp and rooted, my camera wasn't working. It just shows the camera icon and a black screen. I looked up the problem and many people said flashing a vendor image would work, but after doing so, it just tells me there was an internal error, so I reflashed the factory images. After doing so, camera still wasn't working. I also saw one person flashed a different modified boot but this only gives me a bootloop. Does anyone know a fix to the camera problem? Thanks!
kwcty6888 said:
I first rooted my Nexus 6p that was completely stock using the system less root method. After I flashed the modified boot and twrp and rooted, my camera wasn't working. It just shows the camera icon and a black screen. I looked up the problem and many people said flashing a vendor image would work, but after doing so, it just tells me there was an internal error, so I reflashed the factory images. After doing so, camera still wasn't working. I also saw one person flashed a different modified boot but this only gives me a bootloop. Does anyone know a fix to the camera problem? Thanks!
Click to expand...
Click to collapse
It's most likely caused by flashing the wrong boot.img, when you flashed the factory images to go back to stock did you flash the boot.img too?
Heisenberg said:
It's most likely caused by flashing the wrong boot.img, when you flashed the factory images to go back to stock did you flash the boot.img too?
Click to expand...
Click to collapse
I think I did.. I can try reflashed the stock boot.img again though. But I'm not sure what I did wrong because I just flashed the modified boot necessary for twrp?
kwcty6888 said:
I think I did.. I can try reflashed the stock boot.img again though. But I'm not sure what I did wrong because I just flashed the modified boot necessary for twrp?
Click to expand...
Click to collapse
TWRP doesn't require a modified boot.img anymore, it hasn't for a long time, unless you're using the Android N dev preview. You also need to ensure that you flash the right boot.img to suit your ROM build. For example, if you flash the MHC19I boot.img on a ROM that's based on MTC19T you'll get problems, like the camera not working.
Heisenberg said:
TWRP doesn't require a modified boot.img anymore, it hasn't for a long time, unless you're using the Android N dev preview. You also need to ensure that you flash the right boot.img to suit your ROM build. For example, if you flash the MHC19I boot.img on a ROM that's based on MTC19T you'll get problems, like the camera not working.
Click to expand...
Click to collapse
Unfortunately I re-flashed the factory boot and recovery (using build MTC19T), and the camera is still not working. Do you have any other thoughts? Thanks for your help!
kwcty6888 said:
Unfortunately I re-flashed the factory boot and recovery (using build MTC19T), and the camera is still not working. Do you have any other thoughts? Thanks for your help!
Click to expand...
Click to collapse
Flash the full factory images (except userdata), then flash the latest TWRP, not boot into TWRP and enter the wipe menu, select advanced wipe, tick the data box and wipe it. Boot up and see if that helps.
Hi! Guys I have a problem, which doesn't resemble the BLOD, so here is what has happened. I was running stock android June build on 6p, rooted. And my phone started random reboots. I thought it could be fixed with either stock or custom rom. So I decided to flash AOSPA. I went into twrp but could not flash it, phone rebooted each time. I tried stock images via flash all command as well as manual. No rom worked although I could flash kernel etc. I used The Flash's custom twrp and fixed data and was able to flash rom easily, but it bootlooped on google logo, and rebooted. Now I can flash roms etc but it bootloops. Although Tesla rom did go into bootanimation before bootlooping.
So what can I do? Is it software related? What do you guys say!
PS. I did look into other threads, nothing was similar, although I did try a few mentioned fixes.
osamaasif786 said:
So what can I do? Is it software related? What do you guys say!
Click to expand...
Click to collapse
Use fastboot to FORMAT system, userdata and cache. Note any errors during the FORMAT process.... and then try flashing a full image from Google using flash-all.bat
v12xke said:
Use fastboot to FORMAT system, userdata and cache. Note any errors during the FORMAT process.... and then try flashing a full image from Google using flash-all.bat
Click to expand...
Click to collapse
It gives no error and did try the flash-all.bat method no luck.
osamaasif786 said:
It gives no error and did try the flash-all.bat method no luck.
Click to expand...
Click to collapse
I'd say you were squarely in a small group of people who are able to access and fully use Recovery but still boot loop after formatting and installing a clean image. If you've already tried a factory reset from the stock recovery I think you are done. Hardware issue. Replacing the motherboard is a fix, but not economically viable.
I had the same issue formatting data and cache to Ext4 and flashing modified stock ROM fixed. It would boot to Google logo freeze reboot and sometimes get to boot animation freeze and reboot.
Exodusche said:
I had the same issue formatting data and cache to Ext4 and flashing modified stock ROM fixed. It would boot to Google logo freeze reboot and sometimes get to boot animation freeze and reboot.
Click to expand...
Click to collapse
Which modified one, can you share the link?
osamaasif786 said:
Which modified one, can you share the link?
Click to expand...
Click to collapse
Cortex ROM it's flashable stock firmware with extras . Though my symptoms where the same I hope I'm not giving you false hope. Worth a shot though.
The only was I recover my phone without replacing is using https://forum.xda-developers.com/nexus-6p/general/boot-images-bootloop-t3633723 < method from here... but the phone is lag af as it is only running 1 core on stock july build. Good luck for that.
I have the same issue going on. i was trying to flash magisx and suddenly it is stuck in bootloop. i tried flashing stock images and everything. i can access twrp and flash eveything and they are getting flashed fine but still it is stuck on the bootloop.
TheTickReborn said:
I have the same issue going on. i was trying to flash magisx and suddenly it is stuck in bootloop. i tried flashing stock images and everything. i can access twrp and flash eveything and they are getting flashed fine but still it is stuck on the bootloop.
Click to expand...
Click to collapse
So have you used fastboot to FORMAT system, userdata and cache? Did each format command complete with no errors?