Database Users

Stuck at boot screen after JB install help!

Hi guys,
After an attempt to install the new EOS JB rom, I got stuck at the loading screen and would not go further. I then tried to recover my backup rom and that still gets stuck at the boot screen. Can anyone point me in the right direction? I did some google search and I tried alot of methods. I am getting scared that I could brick my device and I need some guidance before I go any further. Please help!

The backup doesn't work because u need to flash the kernel,
In order to do that, Just flash your previous rom or if u know which kernel u had, flash the kernel

My TF101 will no longer boot. I was running the CM10 preview build, but I was having some random reboots and other issues, so I decided to flash CM9 this weekend. Like a good boy, I backed up apps with Titanium Backup and did a full backup in CWM (Roach).
I flashed the the ROM and GAPPS and was able to boot no problem. I used Titanium to restore my apps. I rebooted after the restore and was stuck on the boot animation for close to 20 min. before I forced a shutdown and went back into CWM. First, I tried a factory reset and tried to reboot, with the same effect, then I restored my CWM backup and had the same boot problem, then I tried a earlier CWM backup that also had the same effect.
I'm starting to worry about battery levels now. I started on a full charge, but it's been running a lot. I'm also out of ideas barring NVFlash, which I don't want to do unless I have to.
Is this the same issue?
---------- Post added at 05:06 PM ---------- Previous post was at 04:38 PM ----------
Took the advice and tried flashing a ROM that thankfully I still had on my SDCard that was CM10 based and that let me restore my backup.

Prof-KOS said:
My TF101 will no longer boot. I was running the CM10 preview build, but I was having some random reboots and other issues, so I decided to flash CM9 this weekend. Like a good boy, I backed up apps with Titanium Backup and did a full backup in CWM (Roach).
I flashed the the ROM and GAPPS and was able to boot no problem. I used Titanium to restore my apps. I rebooted after the restore and was stuck on the boot animation for close to 20 min. before I forced a shutdown and went back into CWM. First, I tried a factory reset and tried to reboot, with the same effect, then I restored my CWM backup and had the same boot problem, then I tried a earlier CWM backup that also had the same effect.
I'm starting to worry about battery levels now. I started on a full charge, but it's been running a lot. I'm also out of ideas barring NVFlash, which I don't want to do unless I have to.
Is this the same issue?
---------- Post added at 05:06 PM ---------- Previous post was at 04:38 PM ----------
Took the advice and tried flashing a ROM that thankfully I still had on my SDCard that was CM10 based and that let me restore my backup.
Click to expand...
Click to collapse
ICS based ROMs can't boot up with JB kernels and CWM backups don't contain the kernel as far as I am aware. If you want to go back to CM9, you would have to flash the appropriate kernel. Once you put CM10 on your device, it would contain a JB kernel, hence why it couldn't restore your nandroid.
Sent from my Transformer TF101 using Tapatalk 2

i9apps said:
The backup doesn't work because u need to flash the kernel,
In order to do that, Just flash your previous rom or if u know which kernel u had, flash the kernel
Click to expand...
Click to collapse
I never flashed the kernel, I have been on stock. The EOS team says that JB will run with stock kernel so I did not change anything. How would I flash the kernel if I am stuck at boot screen? And which kernel should I get

Why can't you go back to CWM recovery, (holding down power and volume down button until you see some text then volume up?
For any ROM fresh install, you need to wipe data (factory reset), davik cache, cache, all in CWM Recovery before installing the ROM and kernel (optional).

AstroTrain said:
Why can't you go back to CWM recovery, (holding down power and volume down button until you see some text then volume up?
For any ROM fresh install, you need to wipe data (factory reset), davik cache, cache, all in CWM Recovery before installing the ROM and kernel (optional).
Click to expand...
Click to collapse
I tried but apparently my CWM version does not work well with tf 101. I found a solution by flashing another CWM. Here is guide for those with the same problem.
http://www.transformerforums.com/for...0-windows.html
Everything worked perfectly after I switched CWM to the rogue one

instinct408 said:
I tried but apparently my CWM version does not work well with tf 101. I found a solution by flashing another CWM. Here is guide for those with the same problem.
Everything worked perfectly after I switched CWM to the rogue one
Click to expand...
Click to collapse
Your link is broken and i would love to try it.
I have the same problem.....
I rooted, installed Rom Manager to get CWM Recovery installed and then flashed the new CyanogenMod 10 - B1 ♦ K.A.T. As soon as I restarted, after it appeared that the flash went fine, it hung at the boot screen - not frozen just wont go any further.
I tried rebooting by holding the power button, I tried re-flashing both the CY 10 and the original Rom and tried "restoring" my backed up rom.
I have tried recovering through Easy Flasher but I don't think my PC is seeing the transformer properly.
I have ADB drivers installed but because the TF dose not boot properly it dose not seem to get there.
I have let the battery drain as some report a resolve when they get it to power down all the way but as soon as I plug it in and power it up it goes back to the boot screen and stays there.
Please help as I cant afford to lose this pad (yes I knew the risks).

[Q] Xt907 Freezes at bootloader unlock screen on 4.3 Roms

Hi guys I've been searching and cant seem to find an answer. My xt907 is rooted and my boot loader is unlocked I'm running CWM. If i install any 4.3 roms they work great for initial boot but as soon as i reboot it hangs at the warning boot loader unlocked screen. And the only way i can get the phone working again is to get to ap fastboot and use the DROID_RAZR_M_Utility_1.20 to factory reset everything. If i flash a 4.2.2 rom i don't have any problems. Any ideas guys ? Ive searched and cant seem to find an answer anywhere. Thanks in advance!

My first flash of 4.3 did this... after that I used twrp and haven't had it happen since...
Sent from my XT907 using xda app-developers app

The latest TWRP+mounting system prior to data/system wipes will probably solve your problems. Also, if you have a backup stored, you shouldn't need to fastboot every time.

I've been having the same problem. I thought it might be because I was using CWM, so I thought I'd give it a go with TWRP 2.323. I made a backup, wiped System, Formatted Data and wiped cache and Dalvik cache and installed [ROM][4.4.1][Official][OSE Rom][XT907].
It installed and booted up fine. After a restart, it hung on the bootloader screen. After booting up into TWRP and restoring the backup, it's still hanging on the bootloader unlocked screen. Doh!
I just reinstalled the new ROM and will hope I don't have to restart while I'm out today. Any ideas on things I can try to get things working?

Ryan F said:
I've been having the same problem. I thought it might be because I was using CWM, so I thought I'd give it a go with TWRP 2.323. I made a backup, wiped System, Formatted Data and wiped cache and Dalvik cache and installed [ROM][4.4.1][Official][OSE Rom][XT907].
It installed and booted up fine. After a restart, it hung on the bootloader screen. After booting up into TWRP and restoring the backup, it's still hanging on the bootloader unlocked screen. Doh!
I just reinstalled the new ROM and will hope I don't have to restart while I'm out today. Any ideas on things I can try to get things working?
Click to expand...
Click to collapse
twrp 2323???
You need twrp 2630
see my goodies.

aviwdoowks said:
twrp 2323???
You need twrp 2630
see my goodies.
Click to expand...
Click to collapse
Okay, I downloaded xt907-twrp-2.6.3.0. In trying to flash with fastboot, it's hanging on <waiting for device>. USB Debugging is enabled and the device is showing up. Thanks for the help!

Ryan F said:
Okay, I downloaded xt907-twrp-2.6.3.0. In trying to flash with fastboot, it's hanging on <waiting for device>. USB Debugging is enabled and the device is showing up. Thanks for the help!
Click to expand...
Click to collapse
Fastboot!
Extract the recovery.img from the zip.
But why do that, just flash the zip from your twrp you now have installed

Ryan F said:
Okay, I downloaded xt907-twrp-2.6.3.0. In trying to flash with fastboot, it's hanging on <waiting for device>. USB Debugging is enabled and the device is showing up. Thanks for the help!
Click to expand...
Click to collapse
I believe the one that Avi has is a .zip, not a .xml, so it needs to be flashed in recovery. Load it up on your SD, boot into the recovery you have now, flash the new recovery, and then reboot recovery.

TWRP 2.6.3.0 flashed successfully. Unfortunately, that didn't help at all. My phone still froze on the boot screen. I then booted into the new recovery, wiped everything and reinstalled the rom. Now it won't even boot the first time into the ROM, it just freezes on the boot screen. Help!
*EDIT
I just reinstalled it again and formatted data on top of the wipes this time. It booted into the new rom this time, but it did not get past the boot screen after restarting still.

Ryan F said:
TWRP 2.6.3.0 flashed successfully. Unfortunately, that didn't help at all. My phone still froze on the boot screen. I then booted into the new recovery, wiped everything and reinstalled the rom. Now it won't even boot the first time into the ROM, it just freezes on the boot screen. Help!
*EDIT
I just reinstalled it again and formatted data on top of the wipes this time. It booted into the new rom this time, but it did not get past the boot screen after restarting still.
Click to expand...
Click to collapse
If your rom DL is corrupt?
Also
Arrrghhh has advice on twrp 263, http://forum.xda-developers.com/showthread.php?goto=newpost&t=2573153
It should apply to our 263 also.
---------- Post added at 11:40 PM ---------- Previous post was at 11:29 PM ----------
I use their version (Q)(EDIT ONLY 261 HAS USB MOUNT) and it has usb mount! But it is hard to navigate but I am used to it

Ryan F said:
TWRP 2.6.3.0 flashed successfully. Unfortunately, that didn't help at all. My phone still froze on the boot screen. I then booted into the new recovery, wiped everything and reinstalled the rom. Now it won't even boot the first time into the ROM, it just freezes on the boot screen. Help!
*EDIT
I just reinstalled it again and formatted data on top of the wipes this time. It booted into the new rom this time, but it did not get past the boot screen after restarting still.
Click to expand...
Click to collapse
Many people ran into this issue when 4.3 came out and then someone realized that we were forgetting something when wiping. It was something that we did when the BL was first unlocked, but everyone seemed to forget about it. We were forgetting to mount system, prior to performing wipes of the data/caches. Like Avi said, first, I would DL the ROM again and then place it in your SD. When you wipe, do the FDR option first. After that, go into mount and mount system. Then, go into the advanced wipe options and wipe data, system, cache/dalvik, and format data again. At this point, you can install the ROM as normal, don't re-mount system prior to installing, though. When I am done wiping, I always reboot recovery, but you don't have to do that.

aviwdoowks said:
If your rom DL is corrupt?
Also
Arrrghhh has advice on twrp 263, http://forum.xda-developers.com/showthread.php?goto=newpost&t=2573153
It should apply to our 263 also.
---------- Post added at 11:40 PM ---------- Previous post was at 11:29 PM ----------
I use their version (Q)(EDIT ONLY 261 HAS USB MOUNT) and it has usb mount! But it is hard to navigate but I am used to it
Click to expand...
Click to collapse
Okay, I downloaded the zips again to make sure. This freezing at bootloader screen has happened with every of the dozen or so roms I've tried installing over the past 6 months since I unlocked the bootloader.
RikRong said:
Many people ran into this issue when 4.3 came out and then someone realized that we were forgetting something when wiping. It was something that we did when the BL was first unlocked, but everyone seemed to forget about it. We were forgetting to mount system, prior to performing wipes of the data/caches. Like Avi said, first, I would DL the ROM again and then place it in your SD. When you wipe, do the FDR option first. After that, go into mount and mount system. Then, go into the advanced wipe options and wipe data, system, cache/dalvik, and format data again. At this point, you can install the ROM as normal, don't re-mount system prior to installing, though. When I am done wiping, I always reboot recovery, but you don't have to do that.
Click to expand...
Click to collapse
Could you clarify a little bit?
1.) Mount system
2.) Wipe (Factory Reset: data, cache, dalvik)
3.) Format data
4.) Install zips
What's the FDR option?
---------- Post added at 09:21 AM ---------- Previous post was at 09:07 AM ----------
Ryan F said:
1.) Mount system
2.) Wipe (Factory Reset: data, cache, dalvik)
3.) Format data
4.) Install zips
Click to expand...
Click to collapse
Following the above steps didn't solve it The rom installs fine, boots up for first time normally, but still freezes on the bootloader screen after a restart.

Try geting to the bootloader options & choose normal pwr up.
The new twrp will stick at the big M sometimes.

Then the file is bad or you are missing the install steps. FDR (Factory Data Reset) is the first option you get when you go into the wipe menu, before you go into advanced options. Make sure you're wiping system too, after you mount. If it doesn't work, then it's a bad file or you're still doing something wrong. Upgrading to the most current TWRP and mounting system fixed the issues for 99% of the people. The other 1% just have one of those phones that is "quirky."

okay not sure if your still having this problem. But i never did solve my issue just kept using 4.2.2. But i just flashed the new jbx kernel and a KitKat rom the other along with the newest version on safestrap and i have no issues. Everything flashed and installed perfectly and it boots like a champ. So maybe just skip over 4.3 like i did and see if you still have the issues. Sorry didnt see you were trying to flash 4.4. Only thing i can suggest is make sure you have newest safestrap and wipe out the old etc. But im sure everyone already touched on this stuff before me

beady1 said:
okay not sure if your still having this problem. But i never did solve my issue just kept using 4.2.2. But i just flashed the new jbx kernel and a KitKat rom the other along with the newest version on safestrap and i have no issues. Everything flashed and installed perfectly and it boots like a champ. So maybe just skip over 4.3 like i did and see if you still have the issues. Sorry didnt see you were trying to flash 4.4. Only thing i can suggest is make sure you have newest safestrap and wipe out the old etc. But im sure everyone already touched on this stuff before me
Click to expand...
Click to collapse
Part of your problem is because you are using SS. If you're BL is unlocked, get rid of SS and use CWM or TWRP. SS is not a real recovery replacement, your stock recovery is still there. That's probably part of the reason you had issues.

possibly but i have 0 issues now so its not a big deal.

I have the stable Cyanogenmod 10.1 installed on my phone now. I'm able to restart my phone without any consequences finally. Yay.
I also tried the cm-11-20131221-NIGHTLY-xt907.zip build. That one would initially start up fine, but a restart gave me the frozen bootloader screen. I tried it twice, redownloading it, too. Gah, it's frustrating not being able to try out different roms, but at least I have one that works!
Well, thanks for the help guys. I'd still like to be able to install other roms, so if anyone else has something I can try, I'll do it!

Stuck at Google logo on CM13 flash

I saw another user or two had the same issue as I am having here. I've tried dirty flashing, factory reset, system wipe, and a full reflash of Googles stock images. Still when I try and boot into CM13, I get stuck at the Google logo. Does anyone have any tips or tricks on how you booted the latest nightly?
I know it's still very early in the development process, so bugs are to be expected, but I can't even boot the rom.

i am in the same issue... i was on factory, flashed cm13, never fully booted, so wasnt able to get to turn usb debugging on.... now im stuck... cannot get it to boot no matter what...
cannot flash a factory image as adb does not get detected because i cannot get into android to turn it on...
HELP!!

I never could boot either
Sent from my Nexus 6P using Tapatalk

i did nandroid backup then i flashed official cm13 25 nov nightly, first time it get booted and then i restore the nandroid due to some other data i stored in stock and take titanium backup and once again flash cm13 this time i get bootloop and try wipe all again flash again boot loop. Still now i try 10 to 15 times of flashing cm13 but not booted. Some time i get error with out wiping data as attached. I noticed one thing at the first time when i get booted the bootloader msg like this "your system is modified" during bootloop i get msg like "lock the bootloader to perform system check " any solution guys
Sorry for my English

I wonder if it's a boot.img issue

stalin.sk2 said:
i did nandroid backup then i flashed official cm13 25 nov nightly, first time it get booted and then i restore the nandroid due to some other data i stored in stock and take titanium backup and once again flash cm13 this time i get bootloop and try wipe all again flash again boot loop. Still now i try 10 to 15 times of flashing cm13 but not booted. Some time i get error with out wiping data as attached. I noticed one thing at the first time when i get booted the bootloader msg like this "your system is modified" during bootloop i get msg like "lock the bootloader to perform system check " any solution guys
Sorry for my English
Click to expand...
Click to collapse
What all did you restore in the nandroid backup? Just System, or everything?

Jacob Schwab said:
What all did you restore in the nandroid backup? Just System, or everything?
Click to expand...
Click to collapse
Everything

why is this so hard to flash... i just tried again with tonights nightly and still stuck at google logo...
who has actually installed this? what steps did you use?

Bootloop solved after flashing vendor.img through fastboot

Was coming to tell you mine stop soon as I fastboot vendor again
Sent from my Nexus 6P using Tapatalk
---------- Post added at 03:25 PM ---------- Previous post was at 03:24 PM ----------
Fastboot the vendor fixed mine .The flashable vendor didn't work for some reason.
Sent from my Nexus 6P using Tapatalk

kenbrownstone said:
Was coming to tell you mine stop soon as I fastboot vendor again
Sent from my Nexus 6P using Tapatalk
---------- Post added at 03:25 PM ---------- Previous post was at 03:24 PM ----------
Fastboot the vendor fixed mine .The flashable vendor didn't work for some reason.
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
Can you link it please, the .img file I mean.

Flash the vendor.img didn't work for me :/
Or is there a specific vendor.img I need to flash? I flashed the 7.0 stock version

Nexus 6p with Android 7.0 in bootloop cannot access recovery

Hi Guys,
I'm Kinda new about making a new thread, so if anything's wrong let me know.
Just last evening my nexus 6p (on Android 7.0 official) got into a boot loop from a normal state. It just boots & right after when the white google logo transforms into 4 round object, it just reboots (it takes about 3-5 secs). I can access the boot loader but was unable to access to recovery from there as that takes it to bootloop again. I've tried flashing it, but since i had already updated to Nougat official version & the official image for 6p is yet to come, i tried with some earlier version of Marshmallow. but that failed as well. can it be that i need to select the right version of factory image as i really do not remember my old marshmallow versions anymore.
It seems i'm out of options right now. :crying:
Any advice guys??
TIA

Found this on Nexus 6p help forum. Haven't tried it though so I'm unable to confirm if it works or not.
https://productforums.google.com/forum/#!topic/nexus/hdrNONCCoNE

@sirluigi, this EXACT thing just happened to me ..
stock nougat, only bootloader unlocked ((( and since I've got no access to recovery and no Nougat image, I don't know what to do next
minicoop7, unfortunately, for that guide I need to go into recovery mode

ciocu said:
@sirluigi, this EXACT thing just happened to me ..
stock nougat, only bootloader unlocked ((( and since I've got no access to recovery and no Nougat image, I don't know what to do next
minicoop7, unfortunately, for that guide I need to go into recovery mode
Click to expand...
Click to collapse
Have you tried using fastboot to temp boot to recovery?

fastboot boot twrp-3.0.2-1-angler.img
downloading 'boot.img'...
OKAY [ 0.409s]
booting...
OKAY [ 0.680s]
finished. total time: 1.097s
Click to expand...
Click to collapse
same behavior, nothing but a bootloop
I'm dowloading an official MM image, just to get the stock recovery and see if I can temp boot in it
edit: not possible, I even tried to flash twrp, I tried flashing stock recovery from MTC20F.. tried to temp boot in both, all with no luck and with phone constantly alternating between the "Your device cannot be checked for corruption" screen and the white Google screen with the open lock.

sirluigi said:
Hi Guys,
I'm Kinda new about making a new thread, so if anything's wrong let me know.
Just last evening my nexus 6p (on Android 7.0 official) got into a boot loop from a normal state. It just boots & right after when the white google logo transforms into 4 round object, it just reboots (it takes about 3-5 secs). I can access the boot loader but was unable to access to recovery from there as that takes it to bootloop again. I've tried flashing it, but since i had already updated to Nougat official version & the official image for 6p is yet to come, i tried with some earlier version of Marshmallow. but that failed as well. can it be that i need to select the right version of factory image as i really do not remember my old marshmallow versions anymore.
It seems i'm out of options right now. :crying:
Any advice guys??
TIA
Click to expand...
Click to collapse
Guys its very simple, flash the stock mtc20f image first. After that boot it, it wont work but don't worry. Onece it bootloops go into bootloader and fastboot flash twrp 3.0.2-0. once thats done boot into twrp recovery. Onece in twrp make a backup of the image you just flashed that don't work. Once thats done mount system in recovery. Once mounted plug phone into computer and open the twrp folder you will see on your internal wich will have the backup that you just made. Transfer an old working backup into that folder that way twrp will recognize that backup. Once the backup is in the folder you shoukd see 2 backups in there, your new one that doesn't boot and your old one that does work wich you just put into the twrp folder. Once done go to restore and restore the backup of the working rom you just put in there, make sure to check off all on restore. Once done reboot system and it should boot. This will only work if you have a backup of an old working rom.
---------- Post added at 01:13 AM ---------- Previous post was at 01:00 AM ----------
sirluigi said:
Hi Guys,
I'm Kinda new about making a new thread, so if anything's wrong let me know.
Just last evening my nexus 6p (on Android 7.0 official) got into a boot loop from a normal state. It just boots & right after when the white google logo transforms into 4 round object, it just reboots (it takes about 3-5 secs). I can access the boot loader but was unable to access to recovery from there as that takes it to bootloop again. I've tried flashing it, but since i had already updated to Nougat official version & the official image for 6p is yet to come, i tried with some earlier version of Marshmallow. but that failed as well. can it be that i need to select the right version of factory image as i really do not remember my old marshmallow versions anymore.
It seems i'm out of options right now. :crying:
Any advice guys??
TIA
Click to expand...
Click to collapse
OMG I finally got mine to work
I'll note down the exact steps , most of which may or may not be relevant
1) Flashed MTC20F using TWRP 3.0.2-1
2) Booted into recovery and wiped everything and the partitions
- Add - Booted back into twrp 3.0.2-1 and then swiped to allow modifications
3) Then fastboot flashed TWRP 3.0.2-0
4) Restored my backup ( except recovery)
5) Still got stuck in the google screen.
Now the next parts are a bit weird
6) Booted into TWRP, flashed vendor.img from pure nexus rom
7) wiped everything except internal storage
8) Flashed vendor.img, pure nexus rom and gapps and then flashed vendor.img again
9) Rebooted and it worked
Let me know if it worked for you guys or if you need any more help

disbeyad999989 said:
Guys its very simple, flash the stock mtc20f image first. After that boot it, it wont work but don't worry. Onece it bootloops go into bootloader and fastboot flash twrp 3.0.2-0. once thats done boot into twrp recovery. Onece in twrp make a backup of the image you just flashed that don't work. Once thats done mount system in recovery. Once mounted plug phone into computer and open the twrp folder you will see on your internal wich will have the backup that you just made. Transfer an old working backup into that folder that way twrp will recognize that backup. Once the backup is in the folder you shoukd see 2 backups in there, your new one that doesn't boot and your old one that does work wich you just put into the twrp folder. Once done go to restore and restore the backup of the working rom you just put in there, make sure to check off all on restore. Once done reboot system and it should boot. This will only work if you have a backup of an old working rom.
---------- Post added at 01:13 AM ---------- Previous post was at 01:00 AM ----------
OMG I finally got mine to work
I'll note down the exact steps , most of which may or may not be relevant
1) Flashed MTC20F using TWRP 3.0.2-1
2) Booted into recovery and wiped everything and the partitions
- Add - Booted back into twrp 3.0.2-1 and then swiped to allow modifications
3) Then fastboot flashed TWRP 3.0.2-0
4) Restored my backup ( except recovery)
5) Still got stuck in the google screen.
Now the next parts are a bit weird
6) Booted into TWRP, flashed vendor.img from pure nexus rom
7) wiped everything except internal storage
8) Flashed vendor.img, pure nexus rom and gapps and then flashed vendor.img again
9) Rebooted and it worked
Let me know if it worked for you guys or if you need any more help
Click to expand...
Click to collapse
Unfortunately, this didn't work for me.

I believe you should be fine with just trying to flash an earlier recovery version using fastboot... if you're trying to save your data and then factory flash MM and then restore your data to the phone, you should be able to use fastboot pull and then copy them back once you've got a working device by simple copy from windows.

disbeyad999989 said:
Guys its very simple, flash the stock mtc20f image first. After that boot it, it wont work but don't worry. Onece it bootloops go into bootloader and fastboot flash twrp 3.0.2-0. once thats done boot into twrp recovery. Onece in twrp make a backup of the image you just flashed that don't work. Once thats done mount system in recovery. Once mounted plug phone into computer and open the twrp folder you will see on your internal wich will have the backup that you just made. Transfer an old working backup into that folder that way twrp will recognize that backup. Once the backup is in the folder you shoukd see 2 backups in there, your new one that doesn't boot and your old one that does work wich you just put into the twrp folder. Once done go to restore and restore the backup of the working rom you just put in there, make sure to check off all on restore. Once done reboot system and it should boot. This will only work if you have a backup of an old working rom.
---------- Post added at 01:13 AM ---------- Previous post was at 01:00 AM ----------
OMG I finally got mine to work
I'll note down the exact steps , most of which may or may not be relevant
1) Flashed MTC20F using TWRP 3.0.2-1
2) Booted into recovery and wiped everything and the partitions
- Add - Booted back into twrp 3.0.2-1 and then swiped to allow modifications
3) Then fastboot flashed TWRP 3.0.2-0
4) Restored my backup ( except recovery)
5) Still got stuck in the google screen.
Now the next parts are a bit weird
6) Booted into TWRP, flashed vendor.img from pure nexus rom
7) wiped everything except internal storage
8) Flashed vendor.img, pure nexus rom and gapps and then flashed vendor.img again
9) Rebooted and it worked
Let me know if it worked for you guys or if you need any more help
Click to expand...
Click to collapse
Can you elaborate the steps pls? also have you had an earlier back up of your phone which i don't have?

Has anyone been able to get this to work without being able to get into TWRP? I can't get into recovery whether it is a temp boot to it, or fastboot flash either version..

I have compiled a list of the 20+ methods from various users in THIS thread. It's the second post.

Stuck in a bootloop still @tr4nqui1i7y but will try your methods as well... Fingers crossed..

So I do not if this may help anyone who as run into this issue but still may want to retrieve their data before formating their data or factory resetting. While running TWRP 3.0.3 and flashing the latest 7.1.1 files for angler. I would sometimes be able to boot into the recovery like 3/10 tries ( from the bootloader menu). My data was encrypted and it woul freeze constantly when trying to decrypt soo i decided once I finally got it to boot again in the recovery menu(TWRP after hours mind you) I let the phone stay idle for a few mins should the cpu would cool down that my battery percentage would drop around 41% and the tried to decrypt data which went tru successfully. I retrieve what I Could and it froze during a process of a nandroid backup and started bootlooping again. I believe the battery percentage may be linked to the early shutdown issues that many user were reported having and the bootloop of death we are experiencing. Hopefully this info may help someone else.

I need your help guys. (bricked nexus 6p)

Okay, so I've been reading XDA for a while now to root my devices and install custom ROMs and its been incredibly helpful. However I have a huge issue with my nexus 6p and can't find a way to solve it.
Here goes....
I bought it of eBay a few months ago and unlocked the boot loader and rooted the phone plus i also installed twrp and made a nandroid backup. I then installed pure nexus rom and the phone was working incredibly well.
Fast forward to this week, I decided I wanted to upgrade to cm13, since I missed the cm theme engine. So I Wiped my device clean using twrp. And installed cm 13 and the gapps then rebooted.
The phone booted perfectly but on the optimising apps screen it would reboot and tell me to enter the password that I originally had on the pure nexus ROM. After doing so it would re optimise the apps but would crash and reboot. It was doing this continuously.
Twrp also asked for this password on every boot before it let me see the main recovery menu.
So then I took the logical next step and decided to wipe the phone clean again using twrp. Seeing as my password seemed to not clear the first time.
After the wipe, I decided to use the original nandroid backup to restore my device as the password thing was still showing up. And cm 13 was still not installing. Neither was pure nexus.
Okay this is where it went downhill. I hit restore and had everything checked. The process was going well but instead of the restore completing and twrp saying it was successful. It crashed halfway and rebooted.
Since then its stuck in a bootloop. Its on the google splash screen and then reboots to the google splash screen continuously. And does not boot to the os.
On another note. The bootloader is still unlocked. The recovery works. And so does adb/fastboot. So I wouldn't consider it hard bricked.
Here's what I've tried so far:
I've used the wugfresh root toolkit to flash stock and unroot the phone. With softbrick checked. Still nothing. Phone boots to the splash screen and then reboots to the splash screen.
I then reflashed twrp 3.0.2-1 . which worked And its not asking for my password anymore.
Again I tried restoring from my nandroid and it crashed midway which makes me think the nandroid backup is/was corrupted causing the issue in the first place?
I've also tried to just restore and Flash twrp again and then install pure nexus ROM. And still nothing?
I can also still mount my phone to the PC and copy and remove files.
On another note I find it interesting that although the ROM is installed. And the storage bar on my PC is partially filled showing that it clearly has a ROM installed. The phone does not have the standard android file system. Just the twrp backup folder and that's it.
I would be honoured if you could help me out here. And get my 6p up and running again.
Thank you . [emoji45]

I would suggest you flash the factory stock system image using fastboot to get your 6P back up and running.
If you don't have the factory image they can be downloaded from here
Extract the factory image then use fastboot to flash
Code:
fastboot flash bootloader C:\angler\images\bootloader-angler-angler-xx.xx.img
fastboot reboot-bootloader
fastboot flash radio C:\angler\images\radio-angler-angler-xx.xx.img
fastboot reboot-bootloader
fastboot flash boot C:\angler\images\boot.img
fastboot erase cache
fastboot flash cache C:\angler\images\cache.img
fastboot flash recovery C:\angler\images\recovery.img
fastboot flash system C:\angler\images\system.img
fastboot flash vendor C:\angler\images\vendor.img
Check out this guide which has all the information you need, especially around device encryption and flashing roms. Lastly gaining root is as simple as flashing SuperSU or Phh's SuperUser in TWRP.
I hope that helps, let me know if you get stuck.

Yea just flash stock image I had this happen to me before and flashing stock image fixed it.

Thanks guys. I'm going to read the guide and try it out. Then let you know how it all goes. Fingers crossed it all works
Sent from my ONE A2003 using Tapatalk

im_Zak said:
Thanks guys. I'm going to read the guide and try it out. Then let you know how it all goes. Fingers crossed it all works
Sent from my ONE A2003 using Tapatalk
Click to expand...
Click to collapse
FYI don't backup efs partition with that version of twrp. It's a known issue.

i did not realize that twrp had that issue
And guys, I followed the fastboot process by the letter and although everything worked well. The nexus 6p is still bootlooping on the google splash screen and not going any further. :crying:
What should I do? i've added the cmd window screenshot so you guys can have a look.

Try this thread:
http://forum.xda-developers.com/and...r-bootloop-t3454938/post68872362#post68872362
I worked for me when I was having issues. If it worked for you, please make sure to thank the OP in the thread.

this looks promising. thank you. i'll have a go now. might need your help if i get stuck somewhere though :good:

pctechdroid said:
Try this thread:
http://forum.xda-developers.com/and...r-bootloop-t3454938/post68872362#post68872362
I worked for me when I was having issues. If it worked for you, please make sure to thank the OP in the thread.
Click to expand...
Click to collapse
Thank you so so much dude. After countless hours trying everything to get my nexus 6p up and running to no avail this post did the trick.
Respect!!?✌✌??

im_Zak said:
Thank you so so much dude. After countless hours trying everything to get my nexus 6p up and running to no avail this post did the trick.
Respect!!
Click to expand...
Click to collapse
Upgrade to TWRP 3.0.2-2 real quick. You didn't need that guide(in terms of his nandroid) but I am glad it worked. Just need to wipe efs partition using adb commands.

I see. And I have upgraded to the latest twrp so hopefully it doesn't not happen again
Sent from my ONE A2003 using Tapatalk

im_Zak said:
I see. And I have upgraded to the latest twrp so hopefully it doesn't not happen again
Sent from my ONE A2003 using Tapatalk
Click to expand...
Click to collapse
Good deal!!! There's a build that's unofficial of 3.0.2-3 that you can also jump onto. The current version 3.0.2-2 has a bug with backups on Android N. There was a comprehensive post that someone made about the issues with the different versions but I cannot find it for the life of me.

Jammol said:
Good deal!!! There's a build that's unofficial of 3.0.2-3 that you can also jump onto. The current version 3.0.2-2 has a bug with backups on Android N. There was a comprehensive post that someone made about the issues with the different versions but I cannot find it for the life of me.
Click to expand...
Click to collapse
Thanks for the heads up!