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
Related
I flash Bliss ROM and wasn't getting 4G. Went to go restore my backup and TWRP said it can't because the system was read only. I went to mount option adn took system off read only, restored back up, but my phone wouldn't boot. So I booted back into recovery, flashed Pure Nexus, phone still wouldn't boot up. Tried another ROM, still nothing. Can't get the shome to boot back up.
Now when I go back into TWRP recovery and click on mount, System isn't checked. Did I mess something up? And how to fix?
Have you flashed the vendor image, you have to flash vendor image accordingly.
luckyfate said:
Have you flashed the vendor image, you have to flash vendor image accordingly.
Click to expand...
Click to collapse
Flashed the vendor image when I first flashed the newest version of Pure Nexus a couple weeks ago. Was running it just fine. But, as I know it, if you don't flash the vendor image the phone will still boot but just tells you that you have the incorrect vendor image.
schmaltzy said:
Flashed the vendor image when I first flashed the newest version of Pure Nexus a couple weeks ago. Was running it just fine. But, as I know it, if you don't flash the vendor image the phone will still boot but just tells you that you have the incorrect vendor image.
Click to expand...
Click to collapse
Interesting, for me I'd try to flash back to factory stock image and re-root it. I just use NexusRoot Toolkit to do everything from flashing back to stock and rooting.
---------- Post added at 04:19 PM ---------- Previous post was at 04:17 PM ----------
schmaltzy said:
Flashed the vendor image when I first flashed the newest version of Pure Nexus a couple weeks ago. Was running it just fine. But, as I know it, if you don't flash the vendor image the phone will still boot but just tells you that you have the incorrect vendor image.
Click to expand...
Click to collapse
Well, it is strange then. I'd try to flash everything back to stock and root phone again if I have no choice. I just use NexusRoot Toolkit to do everything from flashing stock to rooting phone.
I downloaded Wug's toolkit and that fixed it. I just flashed stock and didn't have to wipe everything. Thanks for the help!
Please help me. I'm using a Google Nexus 6P. I'm in a softbrick state (bootloop). At first, i taught a simple flash of stock factory image from google with help. But nothing helped. I tried everyhting from the internet asked me to do. I used adb, fastboot, nexus toolkit, but nothing helps. The phone keep on bootlooping. I can go to bootloader and recovery. The bootloop starts when i was flashing a nandroid backup (PureNexus Rom) from a BenzoRom. When i finished flashing the nandroid backup, the bootloop starts. I even did a factory reset, wipe everything, flash a fully stock rom (7.0.0), but the phone won't start..please help me XDA..i really need your help!
Are the android versions of Benzo and PureNexus the same?
CharliexCharger said:
Are the android versions of Benzo and PureNexus the same?
Click to expand...
Click to collapse
Yes it was 7.0 for both of them
afdhalzaed said:
Please help me. I'm using a Google Nexus 6P. I'm in a softbrick state (bootloop). At first, i taught a simple flash of stock factory image from google with help. But nothing helped. I tried everyhting from the internet asked me to do. I used adb, fastboot, nexus toolkit, but nothing helps. The phone keep on bootlooping. I can go to bootloader and recovery. The bootloop starts when i was flashing a nandroid backup (PureNexus Rom) from a BenzoRom. When i finished flashing the nandroid backup, the bootloop starts. I even did a factory reset, wipe everything, flash a fully stock rom (7.0.0), but the phone won't start..please help me XDA..i really need your help!
Click to expand...
Click to collapse
Welcome to the club..
http://forum.xda-developers.com/nexus-6p/help/figure-brick-t3450921/page38
---------- Post added at 07:50 PM ---------- Previous post was at 07:44 PM ----------
Same thing happened to a lot of us. Some were able to recover and some were not, unfortunate I couldn't no matter what I tried. And believe me I tried everything possible. Fastboot , toolkits no go , as for me I couldn't even access recovery. So I did the next best thing, as I was able to flash factory images and lock bootloader I had to rma the device. Waiting on the new one now.
BIGSAMDA1ST said:
Welcome to the club..
http://forum.xda-developers.com/nexus-6p/help/figure-brick-t3450921/page38
---------- Post added at 07:50 PM ---------- Previous post was at 07:44 PM ----------
Same thing happened to a lot of us. Some were able to recover and some were not, unfortunate I couldn't no matter what I tried. And believe me I tried everything possible. Fastboot , toolkits no go , as for me I couldn't even access recovery. So I did the next best thing, as I was able to flash factory images and lock bootloader I had to rma the device. Waiting on the new one now.
Click to expand...
Click to collapse
that's hard..your device was in hardbrick state yes? mine is in softbrick..that's why im so stressed out why this thing cant be fixed..because usually soft brick is easy to be fix..
afdhalzaed said:
that's hard..your device was in hardbrick state yes? mine is in softbrick..that's why im so stressed out why this thing cant be fixed..because usually soft brick is easy to be fix..
Click to expand...
Click to collapse
I was able to flash all factory images manually, I was able to use a toolkit which I normally won't use to download all the images fine. Just that when it came to booting up or even accessing recovery it was a no go. Everything flashed fine via fastboot or toolkit.
I actually did it! oh my god i actually did it! i got out from the freaking bootloop! and trust me i tried EVERYHTING else. Only this method, for me at least, helped. I will described exactly what i did.
1. You need a nandroid backup. Any nandroid backup for your phone is good i think. You NEED to know what version of nandroid backup you are having, and what version of ROM.
2. Wiped, erased everything on my phone.
3. Reverted my phone to stock version of the nandroid. (Google Factory) (For me i reverted to MTC20F full stock because my nandroid backup was on PureNexus MTC20F, used flash all.bat)
4. Tried booting to system but failed, still bootlooped.
5. Flashed TWRP, for me, TWRP 3.0.2.0 works. My suggestion, don't go above this version of TWRP, lots of problems!
5. Flashed the custom ROM the nandroid you had (for me, the nandroid backup was PureNexus MTC20F 6.0.1, so i flashed the PureNexus ROM running MTC20F vendor)
6. I tried rebooting to system, but not to avail.
7. I restored the nandroid backup i had earlier.
8. Progress, the boot animation appeared. Before, only Google logo poped out and then it restarts again.
9. Flash back to full stock MTC20F. (flash all.bat without wiping anything)
10. The phone fully boots!
Hi,
I have a Nexus 6P and have been playing with custom roms and stuff for a while now. Yesterday I tried to perform a TWRP restore of a Pure Nexus ROM (7.0) on the existing Hydrogen OS ROM(7.1) without wiping anything (my bad ). Since then I have been stuck. The phone gets to Google logo and then restarts.
Things I have tried:
- TWRP wipe (all)
- Installing Hydrogen OS after complete wipe.
- Installing Pure Nexus OS after complete wipe.
- Restoring Hydrogen OS TWRP Backup after complete wipe.
- Flashing stock 7.0 NBD90X.
- Flashing stock 6.0 MHC19i.
- Flashing stock ROMs using WUG's toolkit.
- Flashing Hydrogen/ Pure Nexus after Flashing Stock (7.0/6.0)
Everytime the same thing happens. Bootloader Unlocked warning >> Google Logo >> Reboot.
One interesting thing is when I flashed MHC19i vendor before Flashing Hydrogen OS and then After Installing Hydrogen OS, the phone boots up to welcome screen with SIM card error and WiFi not scanning( because of vendor difference I think ).
Anybody got any ideas about what might be wrong and how to fix it?
I would really appreciate any help.
Thanks.
What twrp version are you running?
Sent from my ONE A2003 using Tapatalk
sherri55 said:
Hi,
I have a Nexus 6P and have been playing with custom roms and stuff for a while now. Yesterday I tried to perform a TWRP restore of a Pure Nexus ROM (7.0) on the existing Hydrogen OS ROM(7.1) without wiping anything (my bad ). Since then I have been stuck. The phone gets to Google logo and then restarts.
Things I have tried:
- TWRP wipe (all)
- Installing Hydrogen OS after complete wipe.
- Installing Pure Nexus OS after complete wipe.
- Restoring Hydrogen OS TWRP Backup after complete wipe.
- Flashing stock 7.0 NBD90X.
- Flashing stock 6.0 MHC19i.
- Flashing stock ROMs using WUG's toolkit.
- Flashing Hydrogen/ Pure Nexus after Flashing Stock (7.0/6.0)
Everytime the same thing happens. Bootloader Unlocked warning >> Google Logo >> Reboot.
One interesting thing is when I flashed MHC19i vendor before Flashing Hydrogen OS and then After Installing Hydrogen OS, the phone boots up to welcome screen with SIM card error and WiFi not scanning( because of vendor difference I think ).
Anybody got any ideas about what might be wrong and how to fix it?
I would really appreciate any help.
Thanks.
Click to expand...
Click to collapse
If you used TWRP 3.0.2-1 and restored your EFS, then that's the issue. You need to delete your EFS partition(s) and install 3.0.2-3.
Sent from my Nexus 6P using Tapatalk
im_Zak said:
What twrp version are you running?
Sent from my ONE A2003 using Tapatalk
Click to expand...
Click to collapse
I tried to recover using TWRP 3.0.2-1
but after trying almost everything, tried updating recovery to TWRP 3.0.2-2.
sherri55 said:
I tried to recover using TWRP 3.0.2-1
but after trying almost everything, tried updating recovery to TWRP 3.0.2-2.
Click to expand...
Click to collapse
Thought so! You borked up your efs partition. I actually did the Same and seriously was scared I lost by device. Do not use twrp 3.0.2.1!!!
---------- Post added at 12:06 PM ---------- Previous post was at 12:05 PM ----------
http://forum.xda-developers.com/showthread.php?t=3490168
Follow my thread to the letter and you should be good to go.
Sent from my ONE A2003 using Tapatalk
ultyrunner said:
If you used TWRP 3.0.2-1 and restored your EFS, then that's the issue. You need to delete your EFS partition(s) and install 3.0.2-3.
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
Thanks a lot brother. Formatting the efs solved the issue Installed pure nexus and device running good.
thank you both for your support.
im_Zak said:
Thought so! You borked up your efs partition. I actually did the Same and seriously was scared I lost by device. Do not use twrp 3.0.2.1!!!
---------- Post added at 12:06 PM ---------- Previous post was at 12:05 PM ----------
http://forum.xda-developers.com/showthread.php?t=3490168
Follow my thread to the letter and you should be good to go.
Sent from my ONE A2003 using Tapatalk
Click to expand...
Click to collapse
I was scared too. I had also got the phone from US with no hope of warranty and has almost tried everything but all in vain. finally feeling good.. thanks ..
sherri55 said:
Thanks a lot brother. Formatting the efs solved the issue Installed pure nexus and device running good.
thank you both for your support.
Click to expand...
Click to collapse
NP, the thanks button is good too
Sent from my Nexus 6P using Tapatalk
I have a asus zenfone ze550kl. I was running a cm14 nightly and a new one came so I downloaded it through cm14 and when it finished it said that it would flash it automaticly. Then it booted into twrp but nothing happend. I tried restoring my back up and stock rom also but it doesnt boot into it. Im not able to boot to fastboot mode either.
IDK IF A BRICKED IT. PLS URGENT HELP NEEDED
THANKS
Can you still boot in TWRP? Then flash again CM14.
24imelqui said:
Can you still boot in TWRP? Then flash again CM14.
Click to expand...
Click to collapse
Im able to boot to Twrp and Fastboot now. I just flashed cm14 it flashed succesfully, but when I start it it boot to recovery
Wipe system and flash again, also try to flash the previous build.
abhishek_los said:
Im able to boot to Twrp and Fastboot now. I just flashed cm14 it flashed succesfully, but when I start it it boot to recovery
Click to expand...
Click to collapse
Just flash TWRP latest version using computer
Same happened with me. Nothing is flashing. Tried almost all ROM and even Backup of stockroom is not booting. Every reboot moves back to TWRP. CM14.1 update messed my device.
---------- Post added at 07:29 AM ---------- Previous post was at 07:13 AM ----------
Ok This is stupid. Asked for help minute ago and I am now with solution. Here what I did and got my device back. Download CM recovery from CM downloads page. Download recovery of 12 not 13. and now download TWRP recovery latest version. Both can be found on XDA. Flash CM recovery first. Boot your device into recovery by taking off battery and then vol. down + Power. Now CM recovery will bootup. Now power off device and again boot into bootloader. Now flash latest TWRP recovery and do same as with CM. Now it will work flash anything.
aayushgupta219 said:
Same happened with me. Nothing is flashing. Tried almost all ROM and even Backup of stockroom is not booting. Every reboot moves back to TWRP. CM14.1 update messed my device.
---------- Post added at 07:29 AM ---------- Previous post was at 07:13 AM ----------
Ok This is stupid. Asked for help minute ago and I am now with solution. Here what I did and got my device back. Download CM recovery from CM downloads page. Download recovery of 12 not 13. and now download TWRP recovery latest version. Both can be found on XDA. Flash CM recovery first. Boot your device into recovery by taking off battery and then vol. down + Power. Now CM recovery will bootup. Now power off device and again boot into bootloader. Now flash latest TWRP recovery and do same as with CM. Now it will work flash anything.
Click to expand...
Click to collapse
So many steps to solve a simple issue that simply required updating your TWRP. lmao
LuK1337 said:
So many steps to solve a simple issue that simply required updating your TWRP. lmao
Click to expand...
Click to collapse
Atleast i posted my way out before you My great developer who even didn't think to inform guys to update TWRP or we could have this problem.:fingers-crossed: LOL
aayushgupta219 said:
Atleast i posted my way out before you My great developer who even didn't think to inform guys to update TWRP or we could have this problem.:fingers-crossed: LOL
Click to expand...
Click to collapse
Oh yeah?
http://forum.xda-developers.com/showpost.php?p=69689618&postcount=348
http://forum.xda-developers.com/showpost.php?p=69689621&postcount=1054
Before you do something, make sure you read all of the dev posts in the thread or ask there.
aayushgupta219 said:
Same happened with me. Nothing is flashing. Tried almost all ROM and even Backup of stockroom is not booting. Every reboot moves back to TWRP. CM14.1 update messed my device.
---------- Post added at 07:29 AM ---------- Previous post was at 07:13 AM ----------
Ok This is stupid. Asked for help minute ago and I am now with solution. Here what I did and got my device back. Download CM recovery from CM downloads page. Download recovery of 12 not 13. and now download TWRP recovery latest version. Both can be found on XDA. Flash CM recovery first. Boot your device into recovery by taking off battery and then vol. down + Power. Now CM recovery will bootup. Now power off device and again boot into bootloader. Now flash latest TWRP recovery and do same as with CM. Now it will work flash anything.
Click to expand...
Click to collapse
Thanks I used this and it works well
OS is LineageOS 14 (7.1)
With latest TWR
Been using my ZE551KL normally without installing anything new for the past 10 days. Today I rebooted it hoping to fix a weak phone signal but got a bootloop.
Tried wiping dalvic and cache via TWR without luck.
Tried restoring system+boot+data from a 1 month old backup image. No dice...
Tried restoring another TWRP backup image from when I had CM on, also didn't work.
tried wiping everything [dalvic/system/data/internal/cache] and flashed a fresh Lineage ROM then gapps for a brand new system.... no luck... Same bootloop.
Still get bootlooped whenever the OS animation starts, whether it's Lineage's animation or CM's. Sometimes it bootloops before the animation, just before the animation starts.
Do you think I should restore an ASDF image from my brother's phone which is same model and OS?
If anyone got an idea on how to solve this, please let me know. I'm all ears.
Thanks
The last app you used/install might have corrupted something. Make sure you always check the permission an app uses, ESPECIALLY if you're granting it superSU permission. That's some dangerous stuffs. Two ways of unbricking:
1. Reflash your custom rom.
2. Reflash stock firmware.
---------- Post added at 05:05 PM ---------- Previous post was at 05:05 PM ----------
Let me add another way. If you backed up via TWRP, then restore it. That's another fix