Database Users

Am I Soft Bricked?

Here's the rundown:
I installed the Dark Paranoid Android (Grouper) ROM this morning. I flashed Gapps, and rebooted the device. No issues at that point, because I came from another ROM I did a clean install and got through the registration screens no problem. Once at the home screen, I remembered I had not flashed the Trinity (Grouper) kernel like I had planned, so I rebooted to recovery and flashed it.
That's when I ran into problems. Rebooted device and it stuck at the Google screen. Tried to bootloader into recovery, I still get stuck at the Google screen. Have tried to boot up both the recovery and into Android several times from bootloader, but I always get stuck at the Google screen. I guess my device didn't like the kernel, or somehow installing it damaged my recovery maybe?
Basically, I am asking if I am soft-bricked and have to restore factory and therefore wipe the device clean. Doing that would suck, but it's better than not having the device.

Also, I'd like to know if it's possible to flash stock through the Wugfresh toolkit without removing root. I just want to get back to stock so I can reinstall the ROM and try a different kernel.

liquid150 said:
Also, I'd like to know if it's possible to flash stock through the Wugfresh toolkit without removing root. I just want to get back to stock so I can reinstall the ROM and try a different kernel.
Click to expand...
Click to collapse
Try to wipe everything and reinstall

kinhbang1989 said:
Try to wipe everything and reinstall
Click to expand...
Click to collapse
Impossible with my device in the state I described.
Since the answers were fairly slow I already flashed factory image from Google with the toolkit. Issue was resolved, just will take a while to get everything put back on it.
Sent from my Paranoid Galaxy Nexus

Did you check the md5 on the kernel download? If there wasn't an md5 supplied, download the file a few times and compare the md5's between them for consistency. Could've been as simple as a bad download.

mustbepbs said:
Did you check the md5 on the kernel download? If there wasn't an md5 supplied, download the file a few times and compare the md5's between them for consistency. Could've been as simple as a bad download.
Click to expand...
Click to collapse
I did not check it. Maybe I will try it again later. Was able to right the problem by using the Nexus Toolkit to flash 4.1.2. Then I put DarkPA on it and started over. Not really the end of the world, just slightly time consuming.
I love the Trinity kernel on my phone. I want to use one for Nexus but I didn't see a stable one yet, all are in experimental phase.
Sent from my Paranoid Galaxy Nexus

Need help, please!

Hi all,
Recently I've had a few troubles with flashing ROMS, to the point where I cant start my phone without it rebooting. I've been using CWM PhilZ 6.0.4.4, GT-I9505 and I did a full wipe everytime.
Originally I was on Omega 10 and decided to try out a new ROM (phone kept dying at 15% for some reason as well). Flashed PACman ROMs latest nightly and had some troubles getting past the set up as it froze every time, and when I tried rebooting it, it would simply not start. It was suggested to upgrade my recovery, so I did so from PhilZ CWM 3.0.3.3 to 3.0.4.4. Tried it again and it worked fine, but due to my own clumsiness I accidentally restored system data from Omega to PACman. Obviously it wouldn't start properly after that, reflashed again and was very careful to only restore apps (restored SMS as well as .xml). Everything was fine except a few bugs here and there, but then I rebooted it and it just wouldn't start.
After that I tried cyanogenmod, as I thought it would be more stable. Pretty much same thing happened, less bugs but when I tried rebooting it just wouldn't start.
Given up by this point, I tried reflashing Omega v10. It worked perfectly for a few hours, flashed the latest 3minit framework and ausdim kernel. The next day, my phone suddenly died at 42% and when I try to start it up it gets stuck at the Omega logo. Went into recovery, tried doing full wipe again and cant get past setup without it turning off. Furthermore, when I try to reflash, it just unpacks the zip but turns off randomly.
I'm not quite sure what to do next, I'm thinking it's my recovery not doing wipes properly since when I try to wipe dalvik it says "path not found", and if I try to reboot with recovery it says "root may have been lost, would you like to root?"
Sorry for the whole wall of text, just thought all the information would be better than not enough! If anyone could help it would be greatly appreciated as I cant even access my phone currently
Sent from my GT-N5110 using Tapatalk

Battery
Williamharv said:
Hi all,
Recently I've had a few troubles with flashing ROMS, to the point where I cant start my phone without it rebooting. I've been using CWM PhilZ 6.0.4.4, GT-I9505 and I did a full wipe everytime.
Originally I was on Omega 10 and decided to try out a new ROM (phone kept dying at 15% for some reason as well). Flashed PACman ROMs latest nightly and had some troubles getting past the set up as it froze every time, and when I tried rebooting it, it would simply not start. It was suggested to upgrade my recovery, so I did so from PhilZ CWM 3.0.3.3 to 3.0.4.4. Tried it again and it worked fine, but due to my own clumsiness I accidentally restored system data from Omega to PACman. Obviously it wouldn't start properly after that, reflashed again and was very careful to only restore apps (restored SMS as well as .xml). Everything was fine except a few bugs here and there, but then I rebooted it and it just wouldn't start.
After that I tried cyanogenmod, as I thought it would be more stable. Pretty much same thing happened, less bugs but when I tried rebooting it just wouldn't start.
Given up by this point, I tried reflashing Omega v10. It worked perfectly for a few hours, flashed the latest 3minit framework and ausdim kernel. The next day, my phone suddenly died at 42% and when I try to start it up it gets stuck at the Omega logo. Went into recovery, tried doing full wipe again and cant get past setup without it turning off. Furthermore, when I try to reflash, it just unpacks the zip but turns off randomly.
I'm not quite sure what to do next, I'm thinking it's my recovery not doing wipes properly since when I try to wipe dalvik it says "path not found", and if I try to reboot with recovery it says "root may have been lost, would you like to root?"
Sorry for the whole wall of text, just thought all the information would be better than not enough! If anyone could help it would be greatly appreciated as I cant even access my phone currently
Sent from my GT-N5110 using Tapatalk
Click to expand...
Click to collapse
Seems to me that you are having battery issues. You might need to get a replacement. If that doesn't work you could try flashing a pre-knox ROM though ODIN 3.04. This would mean starting from scratch, but it could be your solution.
Quick question. Are you downloading the ROMs with your phone or downloading them with your computer then moving them to your phone via usb? because it might be your pc's/usb fault.

I also think there's a problem with your battery, it might need to be replaced.

ebahena said:
Seems to me that you are having battery issues. You might need to get a replacement. If that doesn't work you could try flashing a pre-knox ROM though ODIN 3.04. This would mean starting from scratch, but it could be your solution.
Quick question. Are you downloading the ROMs with your phone or downloading them with your computer then moving them to your phone via usb? because it might be your pc's/usb fault.
Click to expand...
Click to collapse
Thanks for the quick reply! Would the battery explain why my ROMS wouldn't start though? Such as how Omega got stuck at the logo. I will try using my friend's battery, or just keeping the phone on charge whilst doing it and see how that works.
Im sending them through Usb currently, is there any other way to get it on my phone as I can't turn it on to send it over wifi :/
Sent from my GT-N5110 using Tapatalk

Whenever you flash stock tar through Odin, the phone will restart by itself and wipe cache. After it does this, you should factory wipe and no more bootloop, or soft bricks. I would start from scratch if i were you. If you have working custom recovery installed., I would go in and do a format, not a wipe, but format the sdcard and restart into download mode and flash stock tar, cf auto root, and then flash a custom recovery. And then decide what rom to flash.

norml said:
Whenever you flash stock tar through Odin, the phone will restart by itself and wipe cache. After it does this, you should factory wipe and no more bootloop, or soft bricks. I would start from scratch if i were you. If you have working custom recovery installed., I would go in and do a format, not a wipe, but format the sdcard and restart into download mode and flash stock tar, cf auto root, and then flash a custom recovery. And then decide what rom to flash.
Click to expand...
Click to collapse
Thank you for the reply i just got home so I'll try this soon, would it be risky though since my battery and/or cable may be damaged, meaning if it turns off during flashing stock, I'll get a hard brick?
Update: just reflashed Omega whilst it was on a charger and it actually worked.
Does this suggest that the battery is damaged?

Sounds to me like a definite battery problem.
Samsung recalled batteries with a serial number starting with BD. have a look and check your battery mate.
Also check it's not swollen
Sent from my GT-I9505 using XDA Premium HD app

Obagleyfreer said:
Sounds to me like a definite battery problem.
Samsung recalled batteries with a serial number starting with BD. have a look and check your battery mate.
Also check it's not swollen
Sent from my GT-I9505 using XDA Premium HD app
Click to expand...
Click to collapse
I just checked my battery, it does start with BD, and it does appear to be somewhat swollen.. I haven't noticed it before :l Could I just return it to Samsung for a replacement, without going back to stock ROM? I'm currently in Australia, haven't really seen a Samsung support center anywhere nearby.
Update: got my hands on a new battery, everything seems to be working great now. Flashed paranoid android, no reboots or any other problems.
Thank you so much to everyone who helped

[Q] Only 4.2 works (4.3 and 4.4 fails)

I was 4.3 (locked bootloader) and the phone worked fine until one instance where the lcd glitched in the messaging app and it stopped responding. So I hard reset the phone and then it got stuck at the nexus logo (Bootloop).
So, i tried the following things:
1) Unlock bootloader
2) Flash 4.4 (KRT16S) from fastboot. Flash completed successfully, there were NO errors. Waited for a while, still stuck in the nexus circling logo. So i went to recovery and wiped data and cache, rebooted and waited for atleast 30mins.
3) Next, I tried 4.3 (jwr66y). Went through the same drill, still not booting. At this point I starting looking online to see if others are having the same problem. This is probably close to what I could find (http://www.reddit.com/r/nexus4/comments/1nefzy/)
4) Lastly I flashed 4.2 (jdq39) using the same procedure as the last 2, but this time it boots successfully! I cannot explain why, I have not done anything different this time.
So I thought I'll give 4.4 another try, but it doesnt work. Stuck in a bootloop. Immediately I flashed back 4.2. So, ultimately only 4.2 works on this phone for some reason. Any ideas as to why this is happening?
Is there a hardware problem with the nandflash, if so how do I verify it?
Also I did not use the toolkit to flash, I just ran flash-all.bat and verified that each command was executed successfully.
UPDATE: This is a rare problem that has affects a handful nexus 4s. The best option is to RMA the phone if it is under warranty of sell the phone for parts. This post gives a good summary of the problem: http://forum.xda-developers.com/showpost.php?p=47532787&postcount=282
jblack248 said:
I have the unknown IMEI and baseband problem that I've seen a number of people have without resolution. While I appreciate the efforts made here, I am including myself in the group that this unbricking method did not work for. For the sake of hoping to save other people time, I'm going to write out my experiences with this problem so far.
I was running CM 10.2 nightly 20131114 without issue when after a reboot my phone bootlooped on the starting animation. I've had errors on nightlies before, so I did the normal routine of fixes. I tried everything from restoring nandroid backups, flashing newer and older radios, doing a fresh install of a known working CM build, then wiped the entire device and tried flashing factory images for 4.4 and 4.3. None of these got the device to boot. Based on a recommendation I went back to the 4.2 factory image and had some luck, but it took a very long time to boot and had an unknown IMEI and baseband. It took a very long time to boot with or without the SIM card.
At this point I tried the unbrick method listed here, and when I restored the factory image I had the exact same problem. I applied the 16 GB fix, but since I'm going to give up for the RMA long-haul I'm not even bothering with the MAC address fixes. I'm restoring to the 4.2 factory image and locking the bootloader so I can send this device back to Google / LG.
I haven't seen anyone recover from the unknown IMEI and baseband problem, and it's scary because it happens for no reason on both stock and custom ROMs. I really like my Nexus 4, but it's going to be hard to trust whatever replacement I get (if any) from Google / LG.
Click to expand...
Click to collapse

@pravarth It looks like you flashed the wrong image to the nexus 4. Always flash image which says occam (thats the codename) . If 4.2 works then surely 4.3 and 4.4 will work successfully.
Always downlaod image from here :
HTML:
https://developers.google.com/android/nexus/images#occam
.
Just flash 4.4 again and see .

Abhiheart said:
@pravarth It looks like you flashed the wrong image to the nexus 4. Always flash image which says occam (thats the codename) . If 4.2 works then surely 4.3 and 4.4 will work successfully.
Always downlaod image from here :
HTML:
https://developers.google.com/android/nexus/images#occam
.
Just flash 4.4 again and see .
Click to expand...
Click to collapse
I got the images from that link and I also double checked that I'm using occam images
occam-jdq39-factory-345dc199 (4.2)
occam-jwr66y-factory-74b1deab (4.3)
occam-krt16s-factory-2006f418 (4.4)
I also verified the md5 hash on all 3. The files are fine

@pravarth : You are on unlocked bootloader, try flashing a 4.4 custom ROM and see
Flash This :
HTML:
http://forum.xda-developers.com/showthread.php?t=2507021

nice
Sent from my Micromax A250 (CanvasTurbo) using XDA Premium 4 mobile app

hmm, the factory images should work. are you under warranty?

same case, my phone only works with 4.2

amartinpascual said:
same case, my phone only works with 4.2
Click to expand...
Click to collapse
Really farfetched but maybe something got damaged in persist or one of the other partitions. If you can figure out a way of enabling usb debugging in 4.3/4.4 (say enabling it in 4.2 and dirty flashing system/boot or maybe flashing a custom rom that has it enabled by default), you might be able to investigate further with logcat.

ziddey said:
Really farfetched but maybe something got damaged in persist or one of the other partitions. If you can figure out a way of enabling usb debugging in 4.3/4.4 (say enabling it in 4.2 and dirty flashing system/boot or maybe flashing a custom rom that has it enabled by default), you might be able to investigate further with logcat.
Click to expand...
Click to collapse
Logcat?
Abhiheart said:
@pravarth : You are on unlocked bootloader, try flashing a 4.4 custom ROM and see
Flash This :
HTML:
http://forum.xda-developers.com/showthread.php?t=2507021
Click to expand...
Click to collapse
Don´t works, same bootloop

Wrong bootloader?
Sent from my Nexus 4 using xda app-developers app

ziddey said:
hmm, the factory images should work. are you under warranty?
Click to expand...
Click to collapse
Yes, I'm under warranty but I bought the phone from USA and I don't want to send it back unless I have to. So I'm trying all options
Oxious119 said:
Wrong bootloader?
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
The appropriate bootloader and radio images were flashed before flashing the image.
According this thread, it seems the problem exists with baseband and apparently is a known problem (http://forum.xda-developers.com/showthread.php?p=48332273#post48332273). So it seems only .48 baseband boots. This is probably what is happening with mine as well. I'll check if they work while on .48 baseband

same problem, like this: http://forum.xda-developers.com/showthread.php?p=48332273#post48332273
tip: you can use 4.3, flash 4.3, then flash the radio of 4.2.2: cwm-radio-mako-m9615a-cefwmazm-2.0.1700.48
but this tip didn't work with 4.4 or 4.4.1, i'm also looking for a solution

Abhiheart said:
@pravarth : You are on unlocked bootloader, try flashing a 4.4 custom ROM and see
Flash This :
HTML:
http://forum.xda-developers.com/showthread.php?t=2507021
Click to expand...
Click to collapse
I tried flashing CM10.2, stuck in bootloop
So, I've found quite a few threads with the same problem and no solution. http://forum.xda-developers.com/showthread.php?t=2525479
http://forum.xda-developers.com/showthread.php?t=2450301
4.2 boots but imei and baseband in settings shows unknown. In bootloader mode the radio version is shown.

jedivulcan said:
Same thing happened to me yesterday. I turned the phone on and it was in a persistent bootloop. Tried everything to get it working until I flashed 4.2.2 and then there was no IMEI or baseband.
Click to expand...
Click to collapse
flash the radio cwm-radio-mako-m9615a-cefwmazm-2.0.1700.48

:/ so this is another problem, good job google! someone have tried to flash the 0.98 radio with 4.4.1/2?

pravarth said:
I tried flashing CM10.2, stuck in bootloop
So, I've found quite a few threads with the same problem and no solution. http://forum.xda-developers.com/showthread.php?t=2525479
http://forum.xda-developers.com/showthread.php?t=2450301
4.2 boots but imei and baseband in settings shows unknown. In bootloader mode the radio version is shown.
Click to expand...
Click to collapse
@pravarth : Did you try factory reset ?? try that might fix your IMEI and baseband

I had a similar issue trying to flash the factory 4.3 and 4.4 images. Everything appeared to flash successfully, but it would never get past the boot logo.
I don't recall where I found it, but someone said to try re-locking then unlocking the bootloader. It worked for me. Maybe it could work for you.

rsilvawashington said:
I had a similar issue trying to flash the factory 4.3 and 4.4 images. Everything appeared to flash successfully, but it would never get past the boot logo.
I don't recall where I found it, but someone said to try re-locking then unlocking the bootloader. It worked for me. Maybe it could work for you.
Click to expand...
Click to collapse
doesn't work

The "no baseband" thing sounds like that old recovery bug. Are you using the latest twrp or cwm?
Sent from my Nexus 4 using xda app-developers app

at4r1 said:
The "no baseband" thing sounds like that old recovery bug. Are you using the latest twrp or cwm?
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
The problem started when i was on stock ROM with stock recovery. It has nothing to do with twrp or cwm in this case

[Q] Bootloop on everything but Stock 4.2, tried everything, looked everywhere (hope)

I am not new to ROMs and flashing etc., but I am completely stumped on this one. I have looked everywhere I know to look (supposedly) but if you find some easily locatable solution that I have missed, please feel free to call me mean names and share the solution with me. Otherwise, this is what I have tried so far (I will start from the beginning):
First, the 4.3 OTA update bricked my phone. I hadn't rooted my N4 yet because it was an updrage from D1 (yes, big jump). I decided to root the phone and install a custom ROM. Can't be too hard right? Its a Nexus for crying out loud. WRONG. Well I rooted pretty easily, and installed my first custom ROM for N4. To install this ROM, I had to erase boot.img, system.img, and userdata.img and then flash each individually from the ROM zip file I downloaded. This worked! I was winging it and it worked out. However, from then on, EVERY ROM I tried to install ended up in a bootloop. I have wiped cache/data, dalvik cache, and even my own (c)ache before flashing new ROM. They all end in bootloop (never ending).
I am able to revert to stock 4.2 easily every time. However, any attempt at installing a custom ROM from there is void. Today I downloaded 4.4.2.tgz from google and ran flash-all.bat. Everything works great! Until I try to boot up; bootloop. I fastboot format this and fastboot erase that, then fastboot flash each .img individually. I fastboot flash new radio, new kernel, etc. etc. but still bootloop.
I really am clueless as to what I am doing wrong or how I screwed myself somewhere along the way, but I am humbly coming before my superiors and asking for help. Please offer me the simplest solution and call me dumb for not seeing it, I will hold you in my heart 4eva

CausableMidget said:
I am not new to ROMs and flashing etc., but I am completely stumped on this one. I have looked everywhere I know to look (supposedly) but if you find some easily locatable solution that I have missed, please feel free to call me mean names and share the solution with me. Otherwise, this is what I have tried so far (I will start from the beginning):
First, the 4.3 OTA update bricked my phone. I hadn't rooted my N4 yet because it was an updrage from D1 (yes, big jump). I decided to root the phone and install a custom ROM. Can't be too hard right? Its a Nexus for crying out loud. WRONG. Well I rooted pretty easily, and installed my first custom ROM for N4. To install this ROM, I had to erase boot.img, system.img, and userdata.img and then flash each individually from the ROM zip file I downloaded. This worked! I was winging it and it worked out. However, from then on, EVERY ROM I tried to install ended up in a bootloop. I have wiped cache/data, dalvik cache, and even my own (c)ache before flashing new ROM. They all end in bootloop (never ending).
I am able to revert to stock 4.2 easily every time. However, any attempt at installing a custom ROM from there is void. Today I downloaded 4.4.2.tgz from google and ran flash-all.bat. Everything works great! Until I try to boot up; bootloop. I fastboot format this and fastboot erase that, then fastboot flash each .img individually. I fastboot flash new radio, new kernel, etc. etc. but still bootloop.
I really am clueless as to what I am doing wrong or how I screwed myself somewhere along the way, but I am humbly coming before my superiors and asking for help. Please offer me the simplest solution and call me dumb for not seeing it, I will hold you in my heart 4eva
Click to expand...
Click to collapse
This is why once I have my phone rooted, there's no turning back to stock.
Are you sure that you wiped system, along with everything else between adventures? (factory reset via recovery)
Sent from my Nexus 7 (2013)

Berrydroidcafe said:
This is why once I have my phone rooted, there's no turning back to stock.
Are you sure that you wiped system, along with everything else between adventures? (factory reset via recovery)
Sent from my Nexus 7 (2013)
Click to expand...
Click to collapse
Yes. I even just did it again to make sure, but I am still watching the beautifully colored circles fold in on themselves.

CausableMidget said:
Yes. I even just did it again to make sure, but I am still watching the beautifully colored circles fold in on themselves.
Click to expand...
Click to collapse
Ok, gonna make a suggestion, and it's totally on you if you want to take it, and of course I won't be held responsible. I have had a bootloop or two on my G2 (the original), I would get impatient and pull the battery. (wish the Nexus 4 had a removable battery) Without fail, that cured the bootloop. Just remember, that was a G2, not a Nexus 4.
Don't ask me why it worked because I have no clue.
Sent from my Nexus 7 (2013)

Berrydroidcafe said:
Ok, gonna make a suggestion, and it's totally on you if you want to take it, and of course I won't be held responsible. I have had a bootloop or two on my G2 (the original), I would get impatient and pull the battery. (wish the Nexus 4 had a removable battery) Without fail, that cured the bootloop. Just remember, that was a G2, not a Nexus 4.
Don't ask me why it worked because I have no clue.
Sent from my Nexus 7 (2013)
Click to expand...
Click to collapse
I have cycled power a few times during the boot to no avail. I also just reverted back to stock 4.2 and then installed OTA 4.3 update hoping outcome would be different (definition of insanity according to Vaas). I don't know what to do. It's just not in me to run 4.2 forever

CausableMidget said:
I have cycled power a few times during the boot to no avail. I also just reverted back to stock 4.2 and then installed OTA 4.3 update hoping outcome would be different (definition of insanity according to Vaas). I don't know what to do. It's just not in me to run 4.2 forever
Click to expand...
Click to collapse
Have you tried calling an Exorcist?
I've run out of ideas!
Sent from my Nexus 7 (2013)

Stuck at Google boot screen

I wanted to tinker around and decided to check out custom roms. Flashed pure nexus and gapps and rebooted without flashing the new vendor image. In fact I had forgotten to download it.
Phone booted into the language choosing screen showing the 'need to flash new vendor'. Not having downloaded it, I booted back into recovery and restored my backup stock rom to quickly get into the xda thread on tapatalk and download it quickly in order to start from fresh
Got the message ' Your device is corrupted ' with a red triangle.(usually got an orange triangle after I unlocked the bootloader). After the red message, the screen got stuck at the white Google screen with a lock pic at the bottom.
I tried restoring my backup again and even flashing pure nexus again with the same result of being stuck at the Google screen with the red warning message.
Totally frustrated not being able to even try one romantic easily. Does anyone has any idea of how to fix it? Or should I start from scratch downloading stock factory image again?
Thank you.
Sent from my SM-G930F using XDA-Developers mobile app

Is everything else in your phone up to date?(bootloader, radio etc. etc.) If you're not sure it Might be safer to just flash stock image and then start flashing roms.

toknitup420 said:
Is everything else in your phone up to date?(bootloader, radio etc. etc.) If you're not sure it Might be safer to just flash stock image and then start flashing roms.
Click to expand...
Click to collapse
My phone had been updated till last month but the rom has this month's patches too. Radio isn't updated by the Rom. By stock I had 3.61. The new one is 3.62 I believe. I have no idea why my phone acted this way though. Does this phone always have the risk of doing this and me flashing stock a lot of times to correct it?
Sent from my SM-G930F using XDA-Developers mobile app

I would suggest try cleaning dalvik and cache. However, I don't think that that would solve the red warning screen. Perhaps the backup you restored was somehow corrupted. I'd say reflash everything (bootloader, radio, rom, vendor, etc), and return to completely stock and see if the problem is still there.

Chillz88 said:
My phone had been updated till last month but the rom has this month's patches too. Radio isn't updated by the Rom. By stock I had 3.61. The new one is 3.62 I believe. I have no idea why my phone acted this way though. Does this phone always have the risk of doing this and me flashing stock a lot of times to correct it?
Click to expand...
Click to collapse
Ok so then just flash the ROM then the latest vendor image and you should boot fine.

http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
I hope the 11th part of this guide would do it? Thanks guys.

Chillz88 said:
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
I hope the 11th part of this guide would do it? Thanks guys.
Click to expand...
Click to collapse
Have you tried flashing the vendor image with the newest version of pure nexus. That red warning is due to the incorrect vendor image. I would try that before flashing the factory image and starting over.