Database Users

[Q] Help. Stuck on flashing bootup after installing bootloader

First post, longtime lurker.
FInally I was brave enough to play around my Nexus 4. Using ADB and Fastboot, I unlocked the bootloader and install custom recovery (tried both twrp and hen cwm). However when I reboot the system, it gets stuck on the flashing 4-circles screen. I had wiped the cache and others, including factory reset, but it is not rebooting.
On the first attempt , I installed twrp, it went well. During the reboot, TWRP asked if I want to unroot to which I agreed. Then that it went to flashing loop. I don't think the SU file was in the phone.
Phone is stock 4.4.2
Please help.
Thanks in advance.

Can you get into recovery and what rom ate you trying to flash?
Sent from my Nexus 5

jd1639 said:
Can you get into recovery and what rom ate you trying to flash?
Sent from my Nexus 5
Click to expand...
Click to collapse
I could get into the bootloader. After massive web-search, I managed to solve the problem using Wugfresh Toolkit. I'm restoring everything now.
Thanks for the concern.

kelso_et said:
I could get into the bootloader. After massive web-search, I managed to solve the problem using Wugfresh Toolkit. I'm restoring everything now.
Thanks for the concern.
Click to expand...
Click to collapse
You should have restored the phone using this http://forum.xda-developers.com/showthread.php?p=47156064
Once you learn how to use it you could have restored your phone with out losing all your apps and data
Sent from my Nexus 5

Bootloop on all custom roms

Anyone else getting bootloops on all custom Roms I unlocked the bootloader and installed twrp latest version though wugs nexus program and I have rooted stock with custom kernel which works fine but is missing a few features I would like to have so I try factory reseting and installing for example chroma or minimal and they both bootloop on fresh install not sure what I'm doing wrong even tried cm13 and same thing but if I flash stock rooted it works fine like normal never had this problem on nexus 5. Any help would be much appreciated.

Did you flash vendor?
Sent from my Nexus 6P using Tapatalk

Ovrclck said:
Did you flash vendor?
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
Not sure what you mean like Rom from google direct?

Ovrclck said:
Did you flash vendor?
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
Not sure that would be an issue, I ran a ROM with an outdated vendor and all that happened was I'd get a popup reminding me that it was out of date

Chief_runningwater said:
Anyone else getting bootloops on all custom Roms I unlocked the bootloader and installed twrp latest version though wugs nexus program and I have rooted stock with custom kernel which works fine but is missing a few features I would like to have so I try factory reseting and installing for example chroma or minimal and they both bootloop on fresh install not sure what I'm doing wrong even tried cm13 and same thing but if I flash stock rooted it works fine like normal never had this problem on nexus 5.
Click to expand...
Click to collapse
WOW! What a sentence! :silly:

Chief_runningwater said:
Anyone else getting bootloops on all custom Roms I unlocked the bootloader and installed twrp latest version though wugs nexus program and I have rooted stock with custom kernel which works fine but is missing a few features I would like to have so I try factory reseting and installing for example chroma or minimal and they both bootloop on fresh install not sure what I'm doing wrong even tried cm13 and same thing but if I flash stock rooted it works fine like normal never had this problem on nexus 5. Any help would be much appreciated.
Click to expand...
Click to collapse
I'm having the same problem as you. No matter what I end up bootlooping at the rom splash screen eventually. Even after the rom appears to be doing well.

dirtyreturn said:
I'm having the same problem as you. No matter what I end up bootlooping at the rom splash screen eventually. Even after the rom appears to be doing well.
Click to expand...
Click to collapse
Most likely a vendor issue. I had the same. Most roms are fine with the stock Google vendor, except for SinLess rom (which I use) that has its own vendor file. Its a new thing that came with the 6P and 5X I believe.
If you're on stock already and you have the factory image from Google, extract it, you'll find the flashall script with another zip file containing system and other images. If you're fine with flashing over, run the script. If not just extract the second file, you'll get the system, boot, cache.. imgs as well as vendor.img
Code:
fastboot flash vendor vendor.img

Dissmeister said:
Most likely a vendor issue. I had the same. Most roms are fine with the stock Google vendor, except for SinLess rom (which I use) that has its own vendor file. Its a new thing that came with the 6P and 5X I believe.
If you're on stock already and you have the factory image from Google, extract it, you'll find the flashall script with another zip file containing system and other images. If you're fine with flashing over, run the script. If not just extract the second file, you'll get the system, boot, cache.. imgs as well as vendor.img
Code:
fastboot flash vendor vendor.img
Click to expand...
Click to collapse
Must we flash the vendor.img after every rom?

dirtyreturn said:
Must we flash the vendor.img after every rom?
Click to expand...
Click to collapse
Nope, once, and you should be good. Unless you somehow managed to erase it in recovery or something. If you see a bootloop again, you know what to do. Its just another partition like system, cache, recovery..
Like I said, only some roms require you to flash their own vendor images. From what I know so far, SinLess and PureNexus.
I'd try a stock rom with the stock vendor first, if I were you, just to get things running. Then flash a custom rom.

Dissmeister said:
Nope, once, and you should be good. Unless you somehow managed to erase it in recovery or something. If you see a bootloop again, you know what to do. Its just another partition like system, cache, recovery..
Like I said, only some roms require you to flash their own vendor images. From what I know so far, SinLess and PureNexus.
I'd try a stock rom with the stock vendor first, if I were you, just to get things running. Then flash a custom rom.
Click to expand...
Click to collapse
Slight correction, aside from screwing over with the actual partitions being the cause, it's mandatory for every major android update from google (e.g. 6.0 --> 6.0.1) if you want to update your rom to the following android version (For just nexus as far as i'm aware).
The images that needs to be flashed when updating are radio, vendor, boot and bootloader. (Unless stated otherwise by the developer of the rom you wanna use)
Sent from my Nexus 6P using Tapatalk

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!

boot loop

was on version 6.x.x. of Pure Nexus on my Nexus 6P
Downloaded the latest version from here for 7.0.0 r14
http://forum.xda-developers.com/nexus-6p/development/rom-pure-nexus-layers-fi-wifi-calling-t3244563
I made a full system recovery using TWRP prior to install. Used TWRP to install the .zip of the update. install was successful according to TWRP. I clicked to install SuperSU and then rebooted. Now I'm stuck in a bootloop. I tried restoring my full backup from TWRP I made prior to installing the .zip but still stuck in a bootloop. So tried again with my original backup image and also no luck. I currently don't have a USB cable for my phone as I lost it. Any ideas on how to get out of bootloop? I've left it in the boot cycle (colored google splash screen) eachtime for at least 30mins. I can still get into TWRP and bootloader. Any help would be much appreciated. Thanks in advance.
Edit:
I ensured I wiped prior to each restoration. I also ensured that on my backup prior to trying to update that I selected all options in TWRP.

What version of TWRP are u using ?
And you wiped system/data/cache b4 flashing PN 7.0 ?
Then flashed PN 7.0 ROM/Gapps/Vendor ?
Sent from my Pixel XL using Tapatalk

scoot0073 said:
What version of TWRP are u using ?
And you wiped system/data/cache b4 flashing PN 7.0 ?
Then flashed PN 7.0 ROM/Gapps/Vendor ?
Sent from my Pixel XL using Tapatalk
Click to expand...
Click to collapse
TWRP version: 2.8.7.2
I wiped system/data and cache
I didn't flash vendor or Gapps. I currently have 0 ways to put them on phone. I'm gonna try to get a cable tomorrow and attempt to put them on but I don't know how I will without being able to get into the android OS. Now I'm trying to figure out what Vendor img I need.
A little more digging and I scrounged up my long lost cable.
Used fastboot to push new vendor.img and gapps.
Booted up like a champ. Thanks man

theonlyherb said:
TWRP version: 2.8.7.2
I wiped system/data and cache
I didn't flash vendor or Gapps. I currently have 0 ways to put them on phone. I'm gonna try to get a cable tomorrow and attempt to put them on but I don't know how I will without being able to get into the android OS. Now I'm trying to figure out what Vendor img I need.
A little more digging and I scrounged up my long lost cable.
Used fastboot to push new vendor.img and gapps.
Booted up like a champ. Thanks man
Click to expand...
Click to collapse
If you are using Nougat ROMs, you need to upgrade TWRP to 3.0.2-3.
Sent from my Nexus 6P using Tapatalk

Fixing the back-up failure problem of TWRP FBE version?

A lot of Android 10 ROM's for Nexus 6P is using "twrp-3.3.1.0-FBE-10-angler.img". But the problem is that with that TWRP, back-up fails with an error message. I don't think it is because of the ROM, because it was the same for multiple different ROM's. Not being able to back up the storage makes it difficult to test a new ROM, because I cannot go back. Is there a newer version that fixed this, or a way to fix the problem?

yourrealking said:
A lot of Android 10 ROM's for Nexus 6P is using "twrp-3.3.1.0-FBE-10-angler.img". But the problem is that with that TWRP, back-up fails with an error message. I don't think it is because of the ROM, because it was the same for multiple different ROM's. Not being able to back up the storage makes it difficult to test a new ROM, because I cannot go back. Is there a newer version that fixed this, or a way to fix the problem?
Click to expand...
Click to collapse
No, AFAIK backups don't work on this particular TWRP, you can try other method of backup tho e.g : titanium
Sent from my angler using XDA Labs

back in 2019 i was running lineageos for a few years. one day it would no longer boot, just stuck on the google logo. i tried to install a twrp backup with the same result. i re installed lineage which loaded and booted. phew! right-WRONG, after several reboots it returned to logo stall. i put the phone aside and tried several other roms over time, same result, boots several times and then logo stalls. i was looking for a phone to leave on my bicycle with the mapmyride app installed. i did a factory install, which loaded booted and after a few boots asks for the encryption password. is there a workaround for this condition?

dr1445 said:
back in 2019 i was running lineageos for a few years. one day it would no longer boot, just stuck on the google logo. i tried to install a twrp backup with the same result. i re installed lineage which loaded and booted. phew! right-WRONG, after several reboots it returned to logo stall. i put the phone aside and tried several other roms over time, same result, boots several times and then logo stalls. i was looking for a phone to leave on my bicycle with the mapmyride app installed. i did a factory install, which loaded booted and after a few boots asks for the encryption password. is there a workaround for this condition?
Click to expand...
Click to collapse
Bro, thats BLOD! flash patched boot.img and it'll boot
Sent from my angler using XDA Labs

boot.img
Ata Ur Rehman said:
Bro, thats BLOD! flash patched boot.img and it'll boot
Sent from my angler using XDA Labs
Click to expand...
Click to collapse
hi; i searched for the patched boot.img, all i could find was the twrp with core 4 and the workaround. all i can find is the last factory boot.img, can you provide a link to the patch? many thanks for your time.