Please help, possible bricked phone??? - Nexus 6P Q&A, Help & Troubleshooting

Hey guys so my phone appears to me to be bricked. I have a rooted angler on stock 7.0.0 (NBD90X, Oct 2016). I have ElementalX kernal.
A few weeks ago I was looking in to putting on MultiROM. After I flashed the custom TWRP recovery for MultiROM, the recovery wouldn't work. It just goes to the TWRP blue startup screen and freezes. I have been procrastinating on flashing a functioning recovery ever since. I know, I'm an idiot. Lesson learned. Well the November security update was pushed to my phone a few days ago. I ignored it. Last night I wanted to see if the update included 7.1 or if it was just security update, so I tapped on the update notification and it automatically downloaded the updates without prompt (which I did not want to do.)
Well an hour later my phone died. When I plugged in to the charger, it immediatly started up by itself and booted to the non-functioning recovery and froze. It does this every time I try to boot the device now. I booted in to the bootloader and tried plugging in to my PC to flash a working recovery, but the device will not get picked up by the PC anymore. I don't believe it's a driver issue I use adb all the time with this same device and pc.
Also want to add, factory reset from bootloader went to google startup animation, but then just shut off as soon as it was done. Also, when I select shutdown from bootloader with it plugged in to charger, it will turn off and stay off but does not appear to be charging in any way.
Well that's the backstory. Any help you all can provide is very much appreciated. Turns out the battery in my backup phone is only good for a couple hours anymore. You all know how helpless we are without our phones, ha! Please help! Is it bricked?

I'm confused. How did you factory reset from the bootloader? That's done from recovery. Also, when in the bootloader you use fastboot, not ADB. ADB is not used from the bootloader. Only while booted into android or from recovery.
Use fastboot to flash factory images and you should be Okay.

RoyJ said:
I'm confused. How did you factory reset from the bootloader? That's done from recovery. Also, when in the bootloader you use fastboot, not ADB. ADB is not used from the bootloader. Only while booted into android or from recovery.
Use fastboot to flash factory images and you should be Okay.
Click to expand...
Click to collapse
I meant to say fastboot. Thanks for the clarification. When in the bootloader, scrolling through the options with volume rocker is a "factory" option. I assumed it meant factory reset?

Nebul0us said:
I meant to say fastboot. Thanks for the clarification. When in the bootloader, scrolling through the options with volume rocker is a "factory" option. I assumed it meant factory reset?
Click to expand...
Click to collapse
Never messed with that so I'm not sure. Since your bootloader is unlocked just download and install what you need. Start by downloading and flashing TWRP. In the 6P original development section, find the thread and search it for 3.0.2-3. It's an unofficial version that fixes the issues since (-1). After you flash that boot into it and go to 'Wipe' > Factory reset. You can also do 'Wipe' > Advanced and select system, data, cache & dalvik. Do not select internal storage. After that download a factory image zip. Extract it and flash the bootloader and radio images from fastboot. Now extract the 2nd zip inside of the 1st one and in that folder you'll find system.img, boot.img, vendor.img, cache.img, recovery.img & userdata.img.
Flash those with the exceptions of userdata.img, cache.img & recovery.img. No need to flash recovery if you plan on keeping TWRP. Cache was taken care of from TWRP in the previous step and flashing userdata will wipe your internal storage. Plus you don't want to flash that anyways if your storage is more than 32gb. Refer to Heisenberg's guide for more info.
Edit: If you can boot to bootloader your device should be read with 'fastboot devices' - if it isn't, delete any Android / Nexus / Google drivers. **Reboot your PC** and install them again. After you install them again reboot your PC one more time and try again.

RoyJ said:
Never messed with that so I'm not sure. Since your bootloader is unlocked just download and install what you need. Start by downloading and flashing TWRP. In the 6P original development section, find the thread and search it for 3.0.2-3. It's an unofficial version that fixes the issues since (-1). After you flash that boot into it and go to 'Wipe' > Factory reset. You can also do 'Wipe' > Advanced and select system, data, cache & dalvik. Do not select internal storage. After that download a factory image zip. Extract it and flash the bootloader and radio images from fastboot. Now extract the 2nd zip inside of the 1st one and in that folder you'll find system.img, boot.img, vendor.img, cache.img, recovery.img & userdata.img.
Flash those with the exceptions of userdata.img, cache.img & recovery.img. No need to flash recovery if you plan on keeping TWRP. Cache was taken care of from TWRP in the previous step and flashing userdata will wipe your internal storage. Plus you don't want to flash that anyways if your storage is more than 32gb. Refer to Heisenberg's guide for more info.
Click to expand...
Click to collapse
I can't get the PC/fastboot to recognize the device. I've never had a problem getting my pc to pick it up before. I even reinstalled the drivers.

Nebul0us said:
I can't get the PC/fastboot to recognize the device. I've never had a problem getting my pc to pick it up before. I even reinstalled the drivers.
Click to expand...
Click to collapse
How are you installing them? Using a toolkit? If so, stop and use the instructions in this thread. You shouldn't have any issues. Make sure you're rebooting your PC after deleting all Android / Nexus / Google drivers before installing them again. Install using the guide and reboot again.
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928/page508
Edit/addition: Toolkits often use outdated or incomplete ADB/fastboot drivers. Always always always use the Android SDK to install them. That way you will always have the latest versions. If you ever have issues detecting your phone, just open the SDK and check for updates.

RoyJ said:
How are you installing them? Using a toolkit? If so, stop and use the instructions in this thread. You shouldn't have any issues. Make sure you're rebooting your PC after deleting all Android / Nexus / Google drivers before installing them again. Install using the guide and reboot again.
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928/page508
Edit/addition: Toolkits often use outdated or incomplete ADB/fastboot drivers. Always always always use the Android SDK to install them. That way you will always have the latest versions. If you ever have issues detecting your phone, just open the SDK and check for updates.
Click to expand...
Click to collapse
Okay so I left the phone on the charger with the frozen screen in twrp multirom edition. After that rebooted in to the bootloader. I then selected the factory option. If loaded the google animation like before, but this time actually booted up the system. The notification bar had two diagnostic tools that said tap to run...one was called sims i think? Anyways I held power button and did a hard reboot. It booted up fine. I then used twrp manager to install 3.0.2.2....then i used fastboot to flash 3.0.2.3 that i had a copy of. Things seem to be working fine now. Close call. I'm not sure what the factory option is in the bootloader, but it's not factory reset and it was the only way I could boot. I think the phone was trying to boot to recovery to install the latest updates and I had to boot to factory to get it out of "update mode," if you will...
Does anyone know what the factory option is in the bootloader?
Thanks for your help RoyJ

Nebul0us said:
I meant to say fastboot. Thanks for the clarification. When in the bootloader, scrolling through the options with volume rocker is a "factory" option. I assumed it meant factory reset?
Click to expand...
Click to collapse
Factory options is meant to restart the system with some manufacturers apps available just so you can test certain functions of the phone, mostly to see if all sensors and hardware are working properly.

Related

[Q] [Solved] Factory Rooted

Hello all, I just had a quick questions for those of you who have unlocked / rooted your Nexus 10 and installed the factory image:
1. Did you all use the toolkit in the Android Dev Forum for Nexus 10 to achieve the root?
2. Once you flashed a custom recovery was installing the factory image as simple as downloading the zip from google (https://developers.google.com/android/nexus/images#mantaray) and then flashing it via recovery and rebooting AFTER you unlock the bootloader etc?
I was under the impression that once you Unlock / Root, you have no OS on your device, is this correct? Or can I root and Android 4.2.1 will still be there, albeit completely wiped of my user data from before.
Thanks for the help, don't wanna get started on this until I know what I'm doing! Don't want a $400 makeshift frisbee disk
You can achieve root in a number of ways including flashing the SuperSU zip found in the How-to Root thread(s) or flashing a ROM with root already built in through the custom recovery.
Unlocking the device does not usually (is not supposed to) remove the OS but it does wipe data back to factory default. There has been, however, an issue with 4.2 on the N10 that causes it not to boot until you go back into Recovery and either factory reset there again or flash the stock image from Google.
Fromako said:
You can achieve root in a number of ways including flashing the SuperSU zip found in the How-to Root thread(s) or flashing a ROM with root already built in through the custom recovery.
Unlocking the device does not usually (is not supposed to) remove the OS but it does wipe data back to factory default. There has been, however, an issue with 4.2 on the N10 that causes it not to boot until you go back into Recovery and either factory reset there again or flash the stock image from Google.
Click to expand...
Click to collapse
Thanks! I think I will go through with using the toolkit tonight and see if I can get it to boot into the factory image. Glad that it sticks around (hopefully) if not I can just flash 4.2 from google via TWRP...thats what I needed to know
So really all I need to root is this:
1. fastboot oem unlock
2. fastboot flash recovery [recovery.img]
3. Boot into recovery
4. Flash SuperSU.zip? --- Where can I download SuperSU.zip ?
5. Wipe Cache / Factory Reset via TWRP wipe data
6. Reboot
7. Profit?
I won't use the toolkit if I don't have to since I am familiar with some fastboot stuff
TheEmpyre said:
I won't use the toolkit if I don't have to since I am familiar with some fastboot stuff
Click to expand...
Click to collapse
Sounds like you know enough to do it without resorting to a toolkit, yeah. This zip file from http://forum.xda-developers.com/showthread.php?t=1997227 is one place to get fastboot drivers and the SuperSU.
http://downloadandroidrom.com/file/Nexus10/Nexus10RootNew.zip
I'd recommend (although it may not be necessary) making sure your devices fully boots after unlocking and wiping before going back to recovery to flash SU. Again, this is just because of the unlock boot loop issue that didn't happen on pre-4.2 nexus devices like the Galaxy Nexus.
Fromako said:
Sounds like you know enough to do it without resorting to a toolkit, yeah. This zip file from http://forum.xda-developers.com/showthread.php?t=1997227 is one place to get fastboot drivers and the SuperSU.
http://downloadandroidrom.com/file/Nexus10/Nexus10RootNew.zip
I'd recommend (although it may not be necessary) making sure your devices fully boots after unlocking and wiping before going back to recovery to flash SU. Again, this is just because of the unlock boot loop issue that didn't happen on pre-4.2 nexus devices like the Galaxy Nexus.
Click to expand...
Click to collapse
I just finished successfully rooting...got hung up after I unlocked the bootloader and flashing TWRP but all I had to do was Format the Data and wipe cache after to successfully boot into the OS. After that I was able to load SuperSU to my SDcard and then flashed it, reboot, did root-checker and I'm all good! Thought I was screwed there for a sec cuz I didn't pre-load SuperSU or the factory image in-case it hit the fan and I wasn't able to mount my SDcard storage via TWRP...Figured it all out though thanks for the help! Glad I was able to do it without the tool-kit!

I think my system portion is corrupt... Any chance of saving it?

I have a 2012 Nexus 7. At the time it had a locked bootloader but it was rooted with cm11 & TWRP on board. I downloaded the Nexus toolkit & tried to upgrade to lollipop when it was officially released. Somewhere along the line, I think the system partition got corrupted. I can manually flash all IMG files except system. I can get into bootloader & recovery. I even tried flashing TWRP again to reflash cm. TWRP took but cm failed to install. Anyone else have this issue? The tablet appears to boot but it just gets stuck at the Google screen with the lock at the bottom. Never goes past that point. Any help to revive this tablet would be much appreciated.
Beast84 said:
I have a 2012 Nexus 7. At the time it had a locked bootloader but it was rooted with cm11 & TWRP on board. I downloaded the Nexus toolkit & tried to upgrade to lollipop when it was officially released. Somewhere along the line, I think the system partition got corrupted. I can manually flash all IMG files except system. I can get into bootloader & recovery. I even tried flashing TWRP again to reflash cm. TWRP took but cm failed to install. Anyone else have this issue? The tablet appears to boot but it just gets stuck at the Google screen with the lock at the bottom. Never goes past that point. Any help to revive this tablet would be much appreciated.
Click to expand...
Click to collapse
Can you enter recovery or fastboot mode? If so, use either to attempt and repair (format) the system partition, then reflash the ROM of your choice.
PrizmaticSmoke said:
Can you enter recovery or fastboot mode? If so, use either to attempt and repair (format) the system partition, then reflash the ROM of your choice.
Click to expand...
Click to collapse
I already did. I flashed stock recovery & factory reset. Still the same thing. I flashed TWRP, the roms flashed through there just fail
Bumping to see if anyone else can help...
Beast84 said:
I already did. I flashed stock recovery & factory reset. Still the same thing. I flashed TWRP, the roms flashed through there just fail
Click to expand...
Click to collapse
In Twrp recovery,
1. go to wipe menu and advanced wipe.
2. select system partition then tap repair.
3.Flash your rom
Paramesh96 said:
In Twrp recovery,
1. go to wipe menu and advanced wipe.
2. select system partition then tap repair.
3.Flash your rom
Click to expand...
Click to collapse
Ok so that worked to flash cm but will this continue to happen if I try flashing the official lollipop update? I'm trying to return to stock so I can give the tablet to my nephew. I don't want him jumping into recovery or bootloader & wrecking it for good

Lg G2 LS980: Having Problems After Trying To Flash CyanogenMod 12.1

Sprint LS980 in an odd state after trying to flash CyanogenMod 12.1
Ok... so I got two of these Sprint LG G2's. I was able to successfully flash the first one with a minimum amount of problems considering I was just learning how to do it.
This second one is a problem though. Here's what I did:
I tried to root but it could not due to the version of the Sprint firmware on the phone. I did the TOT stock flash to get it back to stock. That worked fine.
Then I was able to root it via ioroot. Once rooted, I installed FreeGee and tried to install TWRP, that didn't seem to work, so I installed CWM Recovery. I did option two on this thread to try to get the loki stuff installed using openrecovery-twrp-2.6.3.4-ls980. That "installed" and I was able to boot into it. I installed cm-12.1-20151125-NIGHTLY-ls980 (same one I used on the other phone). That would not install via CWM and gave an error about not being able to lokify (or something like that).
So I said, OK, I must have done something wrong, so I tried to redo stock flash again. That acts like everything works fine LGFlash does it's thing (using LS980ZVA_01.TOT), but the phone boots up and does not seem to finish the install process. The LG logo comes up and not the Sprint screen that I would expect. I can do this over and over again and the results are the same whether I let it sit for an hour or 10 minutes after flashing. So now, the phone boots, but I can't do anything with the touch screen, and will then go into a reboot loop (getting into the OS but rebooting shortly after). I CAN get into CWM where I can wipe data/factory reset and wipe cache partition. After I do that, the phone will boot and will let me interact with it, but after a short time (a few minutes I think), it will reboot again and be in the same state it was before I went into CWM. I tried to do a factory reset in settings. It would say that two reboots would occur, but then nothing happens.
I'm at a bit of a loss as to where to go from here. I don't think that it's an unrecoverable brick, but heck if I know how to fix it.
In between reboots, ADB does see the device in ADB Devices, but shows that it's offline, so I can push an APK to it.
Here are the options that I get in recovery mode:
Reboot System Now
Apply Update From External SD Card
Apply Update From Cache
Apply Update from ADB
Wipe data/factory reset
Wipe cache partition
Any assistance is greatly appreciated!
Ok.. well.. I downloaded and flashed ZVE and it seems to have greatly stabilized the phone. However, it seems that I have lost the ability to do download mode and recovery mode. I can still get into the device through ADB, but ioroot no longer is able to root the device, so I can't install any recovery. There is a system update available to install, but didn't want to do that unless I'm good an stuck in this mode.
I also don't seem to be able to enable the cellular service. I don't know if the update it wants to install would fix that or not.
Edit: I can still do ADB reboot recovery and get into recovery mode with these options:
Apply Update From External SD Card
Apply Update From Cache
Apply Update from ADB
Wipe data/factory reset
Wipe cache partition
Edit2: I was able to root with Stump. FreeGee won't run on ZVE, so not sure what to do from here. The phone does not work at all. None of the phone info is listed in About Phone. No IMEI or anything.
Edit3: I have been able to get TWRP installed and can boot into it. I have also verified that I can get into download mode now. I'm very concerned about my EFS info though. I did back it up, but not to the PC, so effectively I have no EFS backup and no way to recover the IMEI information. Not cool...

Downgrading from Nougat to Marshmallow

I've been reading about bricked devices and want to downgrade from N to MM. I seen a thread in the 5X forum about it but want to be be sure before I attempt it with my 6P. Anyone have trouble downgrading? Can I just flash the factory image like usual? Thanks in advance.
Sent from my Nexus 6P using Tapatalk
Advice for now - Don't even bother unless your ready for a soft bricked device until the issue is resolved and considering we dont even have a factory image it could be weeks away.
its your descision but there are two threads now attempting to fix this and people have had mixed results, the only seemingly helpful thing is to back up 100% of your devices partitions / efs and absolutely everything from your MM build and store it safe on your PC for when your device eventually soft bricks.
just don't bother ! if your on MM stay for another month or so or lump it with stock rooted N, don't attempt to go back !
hutzdani said:
Advice for now - Don't even bother unless your ready for a soft bricked device until the issue is resolved and considering we dont even have a factory image it could be weeks away.
its your descision but there are two threads now attempting to fix this and people have had mixed results, the only seemingly helpful thing is to back up 100% of your devices partitions / efs and absolutely everything from your MM build and store it safe on your PC for when your device eventually soft bricks.
just don't bother ! if your on MM stay for another month or so or lump it with stock rooted N, don't attempt to go back !
Click to expand...
Click to collapse
Yeah, so many stories of expensive paperweights when trying the downgrade. I suspect they're having some major issues with the 6p factory image, since the 5x has been posted for nearly two weeks. I've got mine working pretty well, with really good battery and ARISE sound actually working system-wide. I suspect we may see the factory image when this month's security update is rolled out - at least I hope so, given we're already into September.
That's what I figured. Looks like I'm staying on N. Thanks!
Sent from my Nexus 6P using Tapatalk
@dutchy716, you should be fine. Only people I saw who bricked either flashed the OTA package over a custom ROM (never, ever do this even on "stock debloated" ROMs) or restored a MM nandroid backup while being on N. I have gone back to MM plenty of times (at this point, close to 10). The steps to downgrade and not brick have always been the same and from what I've seen it's only been user error that put people in that position. Make sure you're using the latest TWRP which at this point and time is 3.0.2-1. This guide assumes you know ADB/fastboot and have drivers correctly installed. Follow sticky guide 'how to' links in general if this isn't the case. Using a PC, download and extract the 6.0.1 factory image.
Step 0.5: If you don't already have it, fastboot flash TWRP 3.0.2-1
Step 1: Reboot to TWRP
Step 2: Wipe > Factory Reset / Wipe > Advanced > System, Data, Cache & Dalvik
Step 3: Reboot to bootloader, swipe to ignore TWRP warning of no OS installed if you wiped system partition from advanced section.
Step 4: Fastboot time;
fastboot devices
fastboot flash bootloader bootloader-angler-angler-03.54.img
-use volume & power keys to reboot back to bootloader
fastboot flash radio radio-angler-angler-03.61.img
fastboot flash vendor vendor.img
fastboot flash system system.img
fastboot flash boot boot.img
fastboot flash recovery recovery.img
Step 5: Reboot to recovery. When you see the android on its back alongside a red triangle & exclamation mark; hold down the power button & while holding power, press and release volume up. This will bring up the stock recovery menu. Use volume keys to select wipe cache partition and power to confirm. Then select reboot system now.
Let the phone boot and you're now on complete stock 6.0.1. Follow the steps exactly and I guarantee you won't have issues. Don't take shortcuts to save time (oh I can skip so and so step, do this order instead, etc.). At this point you can reboot once again to bootloader and;
fastboot devices
fastboot flash recovery twrp-3.0.2-1-angler.img
Boot to TWRP & flash your favorite MM ROM.
Notes: This method does NOT wipe user data. Any pictures you've taken, files you've downloaded, etc. will all still be there. You do not need 'cache' or 'userdata' when flashing the factory images. Skip both of those. A factory reset from stock recovery will wipe all userdata from internal storage as will fastboot flashing userdata.img. That is why we do it from TWRP before starting and skip flashing it in fastboot. Cache will build itself as it boots. So long as you wipe it from TWRP/STOCK recovery you will be fine.
That'll do it.
Edit: Just look for yourself. This post is surrounded by "bricked after restoring nandroid posts" Do not restore a 6.0 nandroid over a 7.0 ROM. It appears there's an issue with backup & restore from TWRP at this time so just don't do it. Downgrade the way I posted to avoid data loss and bricks. All of my sensors, sim, data, etc. all work perfect.
Great thanks! I'll give it a go
Sent from my Nexus 6P using Tapatalk
RoyJ said:
@dutchy716, you should be fine. Only people I saw who bricked either flashed the OTA package over a custom ROM (never, ever do this even on "stock debloated" ROMs) or restored a MM nandroid backup while being on N. I have gone back to MM plenty of times (at this point, close to 10). The steps to downgrade and not brick have always been the same and from what I've seen it's only been user error that put people in that position. Make sure you're using the latest TWRP which at this point and time is 3.0.2-1. This guide assumes you know ADB/fastboot and have drivers correctly installed. Follow sticky guide 'how to' links in general if this isn't the case. Using a PC, download and extract the 6.0.1 factory image.
Step 0.5: If you don't already have it, fastboot flash TWRP 3.0.2-1
Step 1: Reboot to TWRP
Step 2: Wipe > Factory Reset / Wipe > Advanced > System, Data, Cache & Dalvik
Step 3: Reboot to bootloader, swipe to ignore TWRP warning of no OS installed if you wiped system partition from advanced section.
Step 4: Fastboot time;
fastboot devices
fastboot flash bootloader bootloader-angler-angler-03.54.img
-use volume & power keys to reboot back to bootloader
fastboot flash radio radio-angler-angler-03.61.img
fastboot flash vendor vendor.img
fastboot flash system system.img
fastboot flash boot boot.img
fastboot flash recovery recovery.img
Step 5: Reboot to recovery. When you see the android on its back alongside a red triangle & exclamation mark; hold down the power button & while holding power, press and release volume up. This will bring up the stock recovery menu. Use volume keys to select wipe cache partition and power to confirm. Then select reboot system now.
Let the phone boot and you're now on complete stock 6.0.1. Follow the steps exactly and I guarantee you won't have issues. Don't take shortcuts to save time (oh I can skip so and so step, do this order instead, etc.). At this point you can reboot once again to bootloader and;
fastboot devices
fastboot flash recovery twrp-3.0.2-1-angler.img
Boot to TWRP & flash your favorite MM ROM.
Notes: This method does NOT wipe user data. Any pictures you've taken, files you've downloaded, etc. will all still be there. You do not need 'cache' or 'userdata' when flashing the factory images. Skip both of those. A factory reset from stock recovery will wipe all userdata from internal storage as will fastboot flashing userdata.img. That is why we do it from TWRP before starting and skip flashing it in fastboot. Cache will build itself as it boots. So long as you wipe it from TWRP/STOCK recovery you will be fine.
That'll do it.
Edit: Just look for yourself. This post is surrounded by "bricked after restoring nandroid posts" Do not restore a 6.0 nandroid over a 7.0 ROM. It appears there's an issue with backup & restore from TWRP at this time so just don't do it. Downgrade the way I posted to avoid data loss and bricks. All of my sensors, sim, data, etc. all work perfect.
Click to expand...
Click to collapse
Works fine, thanks!
RoyJ said:
@dutchy716, you should be fine. Only people I saw who bricked either flashed the OTA package over a custom ROM (never, ever do this even on "stock debloated" ROMs) or restored a MM nandroid backup while being on N. I have gone back to MM plenty of times (at this point, close to 10). The steps to downgrade and not brick have always been the same and from what I've seen it's only been user error that put people in that position. Make sure you're using the latest TWRP which at this point and time is 3.0.2-1. This guide assumes you know ADB/fastboot and have drivers correctly installed. Follow sticky guide 'how to' links in general if this isn't the case. Using a PC, download and extract the 6.0.1 factory image.
Step 0.5: If you don't already have it, fastboot flash TWRP 3.0.2-1
Step 1: Reboot to TWRP
Step 2: Wipe > Factory Reset / Wipe > Advanced > System, Data, Cache & Dalvik
Step 3: Reboot to bootloader, swipe to ignore TWRP warning of no OS installed if you wiped system partition from advanced section.
Step 4: Fastboot time;
fastboot devices
fastboot flash bootloader bootloader-angler-angler-03.54.img
-use volume & power keys to reboot back to bootloader
fastboot flash radio radio-angler-angler-03.61.img
fastboot flash vendor vendor.img
fastboot flash system system.img
fastboot flash boot boot.img
fastboot flash recovery recovery.img
Step 5: Reboot to recovery. When you see the android on its back alongside a red triangle & exclamation mark; hold down the power button & while holding power, press and release volume up. This will bring up the stock recovery menu. Use volume keys to select wipe cache partition and power to confirm. Then select reboot system now.
Let the phone boot and you're now on complete stock 6.0.1. Follow the steps exactly and I guarantee you won't have issues. Don't take shortcuts to save time (oh I can skip so and so step, do this order instead, etc.). At this point you can reboot once again to bootloader and;
fastboot devices
fastboot flash recovery twrp-3.0.2-1-angler.img
Boot to TWRP & flash your favorite MM ROM.
Notes: This method does NOT wipe user data. Any pictures you've taken, files you've downloaded, etc. will all still be there. You do not need 'cache' or 'userdata' when flashing the factory images. Skip both of those. A factory reset from stock recovery will wipe all userdata from internal storage as will fastboot flashing userdata.img. That is why we do it from TWRP before starting and skip flashing it in fastboot. Cache will build itself as it boots. So long as you wipe it from TWRP/STOCK recovery you will be fine.
That'll do it.
Edit: Just look for yourself. This post is surrounded by "bricked after restoring nandroid posts" Do not restore a 6.0 nandroid over a 7.0 ROM. It appears there's an issue with backup & restore from TWRP at this time so just don't do it. Downgrade the way I posted to avoid data loss and bricks. All of my sensors, sim, data, etc. all work perfect.
Click to expand...
Click to collapse
Okay, it's been a while for me and I don't want to mess my phone up.
I have a Nexus 6P and the bootloader is still locked, phone is not rooted, and running official 7.0 from the beta signup a couple weeks ago.
I'd like to go back to MM because my battery life has been atrocious. Now my questions:
1. Do I have to unlock the bootloader first before I attempt the steps above?
2. Where is the best place to extract the last MM factory image to use during fastboot?
srt4mn said:
Okay, it's been a while for me and I don't want to mess my phone up.
I have a Nexus 6P and the bootloader is still locked, phone is not rooted, and running official 7.0 from the beta signup a couple weeks ago.
I'd like to go back to MM because my battery life has been atrocious. Now my questions:
1. Do I have to unlock the bootloader first before I attempt the steps above?
2. Where is the best place to extract the last MM factory image to use during fastboot?
Click to expand...
Click to collapse
Yes in order to use fastboot, you need to unlock the bootloader. This will wipe all userdata off of the phone so backup to your PC first. I just unzip everything in platform-tools.
RoyJ said:
Yes in order to use fastboot, you need to unlock the bootloader. This will wipe all userdata off of the phone so backup to your PC first. I just unzip everything in platform-tools.
Click to expand...
Click to collapse
Thanks! I'll give it a shot here after I figure out this bootloader usb data cable issue.
EDIT:
Got back to 6.0.1 after following your instructions, thanks again!!
Worked like a charm. Thanks @RoyJ!
No problem, glad it worked for everyone.
I have been running Weta 7.1 for a week and went back to Pure Nexus using TWRP 3.0.2-3. I went into recovery, wiped everything except internal storage, flashed the vendor image, then flashed the rom and gapps,then flashed the vendor image again. The phone booted up just fine. I never back up or restore the EFS partition.
bmwkeith said:
I have been running Weta 7.1 for a week and went back to Pure Nexus using TWRP 3.0.2-3. I went into recovery, wiped everything except internal storage, flashed the vendor image, then flashed the rom and gapps,then flashed the vendor image again. The phone booted up just fine. I never back up or restore the EFS partition.
Click to expand...
Click to collapse
So your in PN MM with new nougat modem and bootloader ?
dutchy716 said:
I've been reading about bricked devices and want to downgrade from N to MM. I seen a thread in the 5X forum about it but want to be be sure before I attempt it with my 6P. Anyone have trouble downgrading? Can I just flash the factory image like usual? Thanks in advance.
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
Hey so I actually bricked my first Nexus 6p doing this but I have been fine with my replacement. The Key is to update your twrp to 3.0.2-2 (make sure you do this). I then from Android 7 did a full backup in Twrp and then in the bootloader flashed the MTC20F factory image and it rebooted just fine. I guess in Twrp 3.0.2-1 there is an efs partition problem that is causing the bricks; my old bricked nexus 6p was on 3.0.2-1. So just please make sure you flash 3.0.2-2 twrp
ariefabuzaky said:
So your in PN MM with new nougat modem and bootloader ?
Click to expand...
Click to collapse
Yes, and everything is working fine.
ariefabuzaky said:
So your in PN MM with new nougat modem and bootloader ?
Click to expand...
Click to collapse
This is also how I downgraded mine. Also works on 3.0.2-0 if you were wondering.
rndll said:
This is also how I downgraded mine. Also works on 3.0.2-0 if you were wondering.
Click to expand...
Click to collapse
Yes. Already try it and everything is working fine.
What about downgrading a stock android 7.0 without TWRP and unlocked bootloader to MM?
Does anyone have a guidance for this, too?
Edit: Solved.
NedbuR said:
What about downgrading a stock android 7.0 without TWRP and unlocked bootloader to MM?
Does anyone have a guidance for this, too?
Edit: Solved.
Click to expand...
Click to collapse
Did you sideload 7.0 or upgrade from the beta program?
Sent from my Nexus 6P using Tapatalk

Need Help; My LG G6 (H870) keeps booting in TWRP and I can't install stock ROM

Hi,
I unlocked the bootloader of my H870, installed TWRP 3.1.1.0 and SUPERSU. Everything was working great untill I decided to restore my system defaults to make a fresh start with my G6. After choosing the option to restore system defaults, my phone rebooted and it booted into TWRP. I rebooted my phone and it kept doing this all the time.
I decided to look for a stock ROM and flash that ROM.
I succesfully flashed the "LG-H87010f-Flashable.COMPLETE.zip" ROM (from autoprime's post) trough TWRP. But this did not work. I even wiped all the data from my phone (even system) and flashed the ROM again; still nothing.
Before having this issue, I had the same Baseband version, Kernel version, Build number. Only the dates and the Software Version are different.
I had the V10b-EUR-XX Software Version installed on my phone. I see this is the 10f version. I guess this should not be a problem right?
After this I took these steps solve this issue:
1. Downloaded new LG Mobile Drivers (LGMobileDriver_WHQL_Ver_4.2.0)
2. Downloaded and installed LGUP. LGUP doesnt recognize my phone as a LG G6 and this method did not work for that reason.
Fastboot mode is working on my phone; I can reboot my phone trough the commandline on my PC and things like that . However, my PC is not recognizing my phone as a LG G6 device in Fastboot mode.
My PC recognices my phone as a H870 when in TWRP. In Fastboot mode it recognices my phone as Android Device.
3. Installed LG Bridge for more drivers; did not work either
4. Downloaded Uppercut, but it doenst work without LGUP.
4. Looked all over the internet to find a Stock ROM in .zip or .img format; found nothing
5. Downloaded WindowsLGFirmwareExtract-1.2.6.1 and tried to extract the H87010d_00_OPEN_EU_OP_0327.kdz file. I extracted it into .bin files, but they were not usable. After that, I combined these .bin files into a system.img file. But that .img file was bigger then 5 GB and for that reason it was not usable to flash trough Fastboot or TWRP.
7. Looked for other methods to obtain a H870 Stock Rom, including another extraction method, but I cant figure out how to do this.
I have spend countless hours on this problem, but I cant find an usable H870 stock rom to flash my phone with.
Is there someone that can help me out with this problem? Im willing to donate some € if someone helps me to get my phone working again.
Really hoping for a kind person to help me out and provide me solution for this issue.
Thanks in advance
Try formating data in TWRP(not factory reset) then flash the 10f complete zip. Trying to perform a factory reset from within Android could have possibly messed up your data (due to TWRP being installed instead of stock recovery) so a full data format is needed.
Lgup most likely doesn't detect the phone because you wiped system. But flashing the complete zip should have restored system.
In the future make backups in TWRP to restore later.. or flash a kdz with lg bridge or lgup without wiping system first.
autoprime said:
Try formating data in TWRP(not factory reset) then flash the 10f complete zip. Trying to perform a factory reset from within Android could have possibly messed up your data (due to TWRP being installed instead of stock recovery) so a full data format is needed.
Lgup most likely doesn't detect the phone because you wiped system. But flashing the complete zip should have restored system.
In the future make backups in TWRP to restore later.. or flash a kdz with lg bridge or lgup without wiping system first.
Click to expand...
Click to collapse
Thanks for your reply. I have already formatted data in TWRP, but im still having this problem . It seems like something is preventing my device from starting up. I have flashed several ROMS on other devices, but never experienced something like this. Is there something else I can try? Can I flash the stock recovery and flash the stock ROM? I got the feeling TWRP is causing this issue.
If its possible to flash stock recovery, where can I find it?
RoyalD said:
Thanks for your reply. I have already formatted data in TWRP, but im still having this problem . It seems like something is preventing my device from starting up. I have flashed several ROMS on other devices, but never experienced something like this. Is there something else I can try? Can I flash the stock recovery and flash the stock ROM? I got the feeling TWRP is causing this issue.
If its possible to flash stock recovery, where can I find it?
Click to expand...
Click to collapse
Flash the complete zip then boot into download mode and flash kdz. Lgup should see the device as a g6 now instead of unknown device. If lgup isn't seeing any device at all (including unknown device) then your setup is off.. missing drivers or something. If that doesn't work.. idk.
RoyalD said:
Thanks for your reply. I have already formatted data in TWRP, but im still having this problem . It seems like something is preventing my device from starting up. I have flashed several ROMS on other devices, but never experienced something like this. Is there something else I can try? Can I flash the stock recovery and flash the stock ROM? I got the feeling TWRP is causing this issue.
If its possible to flash stock recovery, where can I find it?
Click to expand...
Click to collapse
autoprime said:
Try formating data in TWRP(not factory reset) then flash the 10f complete zip. Trying to perform a factory reset from within Android could have possibly messed up your data (due to TWRP being installed instead of stock recovery) so a full data format is needed.
Lgup most likely doesn't detect the phone because you wiped system. But flashing the complete zip should have restored system.
In the future make backups in TWRP to restore later.. or flash a kdz with lg bridge or lgup without wiping system first.
Click to expand...
Click to collapse
Don't factory reset using the in phone option. You can only do this through twrp's option. To fix this you'll need to boot through the hard side, using power and volume down until the lg logo appears then release power for 1 sec and then repress keeping volume down pressed. Confirm yes twice on the white screens to get to twrp. Once in twrp then reset again and reflash the system. Then using twrps img installer flash your twrp img(make sure it is on ext sd) again. Then reboot.
Swizzle82 said:
Don't factory reset using the in phone option. You can only do this through twrp's option. To fix this you'll need to boot through the hard side, using power and volume down until the lg logo appears then release power for 1 sec and then repress keeping volume down pressed. Confirm yes twice on the white screens to get to twrp. Once in twrp then reset again and reflash the system. Then using twrps img installer flash your twrp img(make sure it is on ext sd) again. Then reboot.
Click to expand...
Click to collapse
Ohhh F*** YEAHH!!! :victory: Booting the "hard side" fixed the problem!! It was the first thing I tried this morning. I just booted this way and rebooted my phone without resetting or flashing anything. Im so damn happy lol. I still dont understand what happened and why my device was actling like this. But I learned a hard lesson; backup, backup and once again: BACKUP. And dont Factory reset in Android!
Thanks a lot for your help guys! I really apreciate it! :victory::victory:
autoprime said:
Flash the complete zip then boot into download mode and flash kdz. Lgup should see the device as a g6 now instead of unknown device. If lgup isn't seeing any device at all (including unknown device) then your setup is off.. missing drivers or something. If that doesn't work.. idk.
Click to expand...
Click to collapse
Thanks a lot for taking your time to help me out. The combination of your ROM/tips and Swizzle82's tip made me fix my phone. You're the man! :victory:
RoyalD said:
Thanks for your reply. I have already formatted data in TWRP, but im still having this problem . It seems like something is preventing my device from starting up. I have flashed several ROMS on other devices, but never experienced something like this. Is there something else I can try? Can I flash the stock recovery and flash the stock ROM? I got the feeling TWRP is causing this issue.
If its possible to flash stock recovery, where can I find it?
Click to expand...
Click to collapse
RoyalD said:
Ohhh F*** YEAHH!!! :victory: Booting the "hard side" fixed the problem!! It was the first thing I tried this morning. I just booted this way and rebooted my phone without resetting or flashing anything. Im so damn happy lol. I still dont understand what happened and why my device was actling like this. But I learned a hard lesson; backup, backup and once again: BACKUP. And dont Factory reset in Android!
Thanks a lot for your help guys! I really apreciate it! :victory::victory:
Click to expand...
Click to collapse
Probably because you already did all the flashing prior to. Glad it worked. This happened when I first got my V20 and was stoned not thinking. I reset using the in phone option and it caused twrp bootloop. I too learned the hard way.
Had the same issue, fixed it, thanks.
My phone kept doing this booting into recovery no mattery what ROM I installed.
I got into twrp by holding volume down and selecting yes on next 2 white screens....but now this message appears all the time.
please can someone help??
Here is message:
"Encryption Unsuccessful
The password you entered is correct, but unfortunately your data is corrupt.
To resume using your phone, you need to perform a factory reset. When you set up your phone after the reset , you'll have an opportunity to restore any data that was backed up to your Google Account."
Matt.
matthew33 said:
My phone kept doing this booting into recovery no mattery what ROM I installed.
I got into twrp by holding volume down and selecting yes on next 2 white screens....but now this message appears all the time.
please can someone help??
Here is message:
"Encryption Unsuccessful
The password you entered is correct, but unfortunately your data is corrupt.
To resume using your phone, you need to perform a factory reset. When you set up your phone after the reset , you'll have an opportunity to restore any data that was backed up to your Google Account."
Matt.
Click to expand...
Click to collapse
Flash a firmware trough LGUp, or flash again the last TWRP available trough fastboot.
RoyalD said:
Thanks a lot for taking your time to help me out. The combination of your ROM/tips and Swizzle82's tip made me fix my phone. You're the man! :victory:
Click to expand...
Click to collapse
Please help, i have the same problem and nothing, what exactly is a boot to the hard side? I ve tried to power off the phone, press vol down and power, realase power 1 sec, press again...but nothing...still boot on twrp...
Well, I finally solved it with lgup and uppercut... what a nightmare.
matthew33 said:
My phone kept doing this booting into recovery no mattery what ROM I installed.
I got into twrp by holding volume down and selecting yes on next 2 white screens....but now this message appears all the time.
please can someone help??
Here is message:
"Encryption Unsuccessful
The password you entered is correct, but unfortunately your data is corrupt.
To resume using your phone, you need to perform a factory reset. When you set up your phone after the reset , you'll have an opportunity to restore any data that was backed up to your Google Account."
Matt.
Click to expand...
Click to collapse
Flash stocl .kdz with uppercut and lg up
Saved my G6!
Swizzle82 said:
Don't factory reset using the in phone option. You can only do this through twrp's option. To fix this you'll need to boot through the hard side, using power and volume down until the lg logo appears then release power for 1 sec and then repress keeping volume down pressed. Confirm yes twice on the white screens to get to twrp. Once in twrp then reset again and reflash the system. Then using twrps img installer flash your twrp img(make sure it is on ext sd) again. Then reboot.
Click to expand...
Click to collapse
Great tip @Swizzle82! It allowed me to restore my LG G6 after bootloop. It had not been detected by PC, and this hardware reset helped!
Hi, all
If I understand, and to sum up :
I rooted my LG-G6 few weeks ago, and intall TWRP. When OTA wants to install official update, the reboot stops in TWRP mod, so ... failed :-/
Is the solution to flash through Uppercut/LGUP with a .kdz file, without risk of brick the phone ?
Thx

Categories

Resources