Database Users

[Q] Unable to Flash Nexus 7

hello everyone..
In serious need of help here and hope someone can help..
Due to the massive battery drain issue I have been having, I tried to flash the original stock rom on my nexus 7 and
things have gone downhill really bad..
in the past, I flashed using this guide (http://forum.xda-developers.com/showthread.php?t=1907796)
without any problems but last night.. I encountered errors when trying to flash the bootloader
and radio IMG files.. neeedless to say when it comes to flashing the rom in, it came out with errors and my nexus remain OS-less
the errors when trying to flash the bootloader and radio are
"failed (command write failed (Invalid Argument))"
can anyone help me?
p.s :- if anyone can even suggest me a easier way to flash custom roms in and so forth, your suggestion will be most welcomed..
also, I did try wug's rootkit plus the nexus 7 toolkit or something, both came out errors too when too do any flashing in relating to
the bootloader or system.. thanks

Why were you trying to flash the bootloader? Were you trying to update to 4.18?

Username invalid said:
Why were you trying to flash the bootloader? Were you trying to update to 4.18?
Click to expand...
Click to collapse
actually, my bootloader boots fine, it shows tilapia 4.18.
so does this mean I dont have to flash it?
if I dont have to flash the bootloader, do I have to flash the radio?
sorry, kind of a noob in these things..

Anyway, is it normal for the bootloader flash attempt to fail?

hamiksu said:
Anyway, is it normal for the bootloader flash attempt to fail?
Click to expand...
Click to collapse
No, it's not normal for it to fail.
You really don't need to flash either unless one of them is screwed up or you are upgrading to a newer version. Bootloader flashes are risky anyway. To avoid flashing them, you can either remove code from the updater script or remove them from the factory image files entirely.

korockinout13 said:
No, it's not normal for it to fail.
You really don't need to flash either unless one of them is screwed up or you are upgrading to a newer version. Bootloader flashes are risky anyway. To avoid flashing them, you can either remove code from the updater script or remove them from the factory image files entirely.
Click to expand...
Click to collapse
hmm, ok..
then I will go back home and do the system flashing and try and post out the errors it stated there..
really hope to get my nexus back on line...

This is what I get when I tried to flash the image
Hope someone can guide me on what to do next.

hamiksu said:
This is what I get when I tried to flash the image
Hope someone can guide me on what to do next.
Click to expand...
Click to collapse
Try to unlock your bootloader before flashing image with the command:
fastboot oem unlock

ameinild said:
Try to unlock your bootloader before flashing image with the command:
fastboot oem unlock
Click to expand...
Click to collapse
it says my bootloader is already unlocked

hamiksu said:
it says my bootloader is already unlocked
Click to expand...
Click to collapse
Then it sounds like something happened to your system partition that should not have happened.
Are you sure the system image you're trying to flash is valid, do the md5 sums match?
How about flashing another system image?
Or flash a custom recovery, and install a new ROM from there?

ameinild said:
Try to unlock your bootloader before flashing image with the command:
fastboot oem unlock
Click to expand...
Click to collapse
ameinild said:
Then it sounds like something happened to your system partition that should not have happened. Sorry, can't help you there...
Click to expand...
Click to collapse
meaning my system partition is screwed?
anyone knows how to go around this problem?
p.s :- anyway ameinild, thanks for trying to help

hamiksu said:
p.s :- anyway ameinild, thanks for trying to help
Click to expand...
Click to collapse
I edited my post with some more suggestions to try first

ameinild said:
I edited my post with some more suggestions to try first
Click to expand...
Click to collapse
yup, the image i tried a few.. even tried stock rom image.
tried both nexus 7 toolkit
as well as wugs nexus root tool kit.
they all seem to encounter problems when trying to "push" the rom images in or something.
is there a way to like format the entire thing and install from scratch>?

hamiksu said:
is there a way to like format the entire thing and install from scratch>?
Click to expand...
Click to collapse
Sorry, I can't really find anything for the N7... Hope someone else can chime in.

ameinild said:
Sorry, I can't really find anything for the N7... Hope someone else can chime in.
Click to expand...
Click to collapse
Yea, I hope someone will pop in and be my guardian angel too..
Thanks again, Ameinild

tried to flash stock rom using wug's rootkit..
this is what happens...

hamiksu said:
tried to flash stock rom using wug's rootkit..
this is what happens...
Click to expand...
Click to collapse
As a rule, don't do anything with a toolkit that you don't know how to do yourself with the relevant fastboot or ADB commands. It has a nasty tendency of leaving you in a lurch.
I noticed that your last run of Wug's toolkit did claim to successfully flash your recovery. Have you been able to access it from the fastboot menu on the device? If so, that's a major step forward.
Perhaps most importantly (based on your mentioning of tilapia earlier), are you 100% certain that you are trying to flash the factory image for your model of the Nexus 7?

Rirere said:
As a rule, don't do anything with a toolkit that you don't know how to do yourself with the relevant fastboot or ADB commands. It has a nasty tendency of leaving you in a lurch.
I noticed that your last run of Wug's toolkit did claim to successfully flash your recovery. Have you been able to access it from the fastboot menu on the device? If so, that's a major step forward.
Perhaps most importantly (based on your mentioning of tilapia earlier), are you 100% certain that you are trying to flash the factory image for your model of the Nexus 7?
Click to expand...
Click to collapse
Yes, I am absolutely sure it is the image for my nexus 7.. which is 3g/wifi model, not just wifi only..
image file is downloaded using wug's rootkit too..
file name = nakasig-jdq39-factory-0798439d.tgz
as the snapshot shows.. it keeps showing failed when "sending system"
please tell me you have an idea on why it keeps failing there...
*crosses fingers*
p.s :- after that (numerous) wug's toolkit attempt to flash back stock rom, I tried booting to recovery and it shows the android on its back with a red exclamation mark on its open body chasis

I'm assuming you haven't tried this yet, if you have tried this just ignore.
1 - Download - http://techerrata.com/file/twrp2/grouper/openrecovery-twrp-2.6.0.0-grouper.img
2 - fastboot flash recovery openrecovery-twrp-2.6.0.0-grouper.img
If flashes fine:
Power off Nexus, Hold Volume down and Power on, keep holding power down until you get to recovery.
Then:
Either - Get a USB OTG and put a ROM on a USB Stick, go to "install" - "Use external storage" find the rom and flash it.
or
Plug in to PC whilst in recovery, - Mount Storage - Now the Nexus should pop up on PC, Drag ROM to Nexus. Unmount and then try to flash.
Let me know how you get on with this.
Regards.

hamiksu said:
Yes, I am absolutely sure it is the image for my nexus 7.. which is 3g/wifi model, not just wifi only..
image file is downloaded using wug's rootkit too..
file name = nakasig-jdq39-factory-0798439d.tgz
as the snapshot shows.. it keeps showing failed when "sending system"
please tell me you have an idea on why it keeps failing there...
*crosses fingers*
p.s :- after that (numerous) wug's toolkit attempt to flash back stock rom, I tried booting to recovery and it shows the android on its back with a red exclamation mark on its open body chasis
Click to expand...
Click to collapse
That's because you have stock recovery installed now and it's unable to verify that your device is in working order, hence the red mark. Find TWRP for your device, download the .img and try to flash it with fastboot flash recovery <path-to-recovery.img>. Since you can at least get into a recovery, it's possible you'll be able to use onboard recovery tools to see what state your internal partitions are in.
Until there's a little more info available, there's nothing I can say that's not pure conjecture.

Back to Factory with no computer access.

I everyone!
I just tried to connect my Nexus 4 to my windows 8.1 laptop and the phone is not recognised by the PC. It gives me Code 43 error, I tried everything, form fresh driver install to cable change. I also tried on another W7 laptop and nothing pops up there. The phone charges but in Device Manager it is not listed under Google ADB devices but appears with an exclamation mark under USB controllers saying Device Descriptor Request Failed. I fear it is an hardware problem and RMA is the only option left. However, my phone is Rooted, Stock but with modified build.prop, with TW touch recovery and unlocked. Since I have no access to ADB I cannot use the Android SDK tools or anything to flash the factory img. Is there any way in which I could flash back the sock image and lock the bootloader via recovery only?
Thanks everyone :crying::crying:

you dont need adb to flash the factory img. you need fastboot to flash it, via your bootloader. but, fastboot still needs to see your device, so thd driver still nedds to be installed.

Wouldnt it be possible to flash the 4.3 stock rom zip in his custom recovery, root it and flash the stock recovery with flashify, and then unroot the device?
Sent from my Nexus 4 using xda app-developers app

Thibaultvw said:
Wouldnt it be possible to flash the 4.3 stock rom zip in his custom recovery, root it and flash the stock recovery with flashify, and then unroot the device?
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
This was what I was thinking, however, the main issue would be locking the bootloader again
simms22 said:
you dont need adb to flash the factory img. you need fastboot to flash it, via your bootloader. but, fastboot still needs to see your device, so thd driver still nedds to be installed.
Click to expand...
Click to collapse
I dont think is a driver problem, I had driver issues before but i got different errors and solved them easily. I do believe is an hardware failure this time

c0sk said:
This was what I was thinking, however, the main issue would be locking the bootloader again
I dont think is a driver problem, I had driver issues before but i got different errors and solved them easily. I do believe is an hardware failure this time
Click to expand...
Click to collapse
READ THIS 1st
http://forum.xda-developers.com/showthread.php?t=2010312
Scroll down to the 2nd post.

mrhiab said:
READ THIS 1st
http://forum.xda-developers.com/showthread.php?t=2010312
Scroll down to the 2nd post.
Click to expand...
Click to collapse
Thanks, exactly what I was looking for! :victory:
However, since I am already on stock andshould have a backup of the build.prop (i just added a line to get rid of the on screen buttons) would you recommend flashing everything again or just lock bootloader, unroot and flash stock recovery only?

c0sk said:
Thanks, exactly what I was looking for! :victory:
However, since I am already on stock andshould have a backup of the build.prop (i just added a line to get rid of the on screen buttons) would you recommend flashing everything again or just lock bootloader, unroot and flash stock recovery only?
Click to expand...
Click to collapse
Restoring the original build.prop, locking the bootloader, remove root and flash stock recovery will be just fine.

efrant said:
Restoring the original build.prop, locking the bootloader, remove root and flash stock recovery will be just fine.
Click to expand...
Click to collapse
Ok! I did a very stupid thing, I did restore my build.prop but without any backup files. The system does not boot up now! Root has been removed and bootloader locked, however, the custom recovery is still there and I did not copy the stock image! Is there any other way in which I could restore the stock recovery or am I screwed??

c0sk said:
Ok! I did a very stupid thing, I did restore my build.prop but without any backup files. The system does not boot up now! Root has been removed and bootloader locked, however, the custom recovery is still there and I did not copy the stock image! Is there any other way in which I could restore the stock recovery or am I screwed??
Click to expand...
Click to collapse
When you restored your build.prop, did you set the proper permissions, i.e., 644? If not, does your recovery allow you to do so? Try it and see if you boot.
Sent from my Nexus 5 using Tapatalk 2

efrant said:
When you restored your build.prop, did you set the proper permissions, i.e., 644? If not, does your recovery allow you to do so? Try it and see if you boot.
Sent from my Nexus 5 using Tapatalk 2
Click to expand...
Click to collapse
I fixed that problem in a different way, more barbaric but effective. I booted it up and managed to get JDQ39 files on the phone via dropbox: odexed image, boot and recovery. I flashed the first 2 (wanted to keep the recovery for safety and flash the stock one at a second stage). Booted successfully and removed root via SuperSu settings. Once flashed stock recovery, am I right to assume it will be completely stock and therefore ready for RMA? Moreover, can I accept OTA since is fully stock?
Thanks!!!!!
edit: Su installer app was there after flashed recovery and did factory reset

c0sk said:
I fixed that problem in a different way, more barbaric but effective. I booted it up and managed to get JDQ39 files on the phone via dropbox: odexed image, boot and recovery. I flashed the first 2 (wanted to keep the recovery for safety and flash the stock one at a second stage). Booted successfully and removed root via SuperSu settings. Once flashed stock recovery, am I right to assume it will be completely stock and therefore ready for RMA? Moreover, can I accept OTA since is fully stock?
Thanks!!!!!
edit: Su installer app was there after flashed recovery and did factory reset
Click to expand...
Click to collapse
The way you removed SuperSU must have not worked properly. (I've never tried doing it from the SuperSU settings.) In any case, there's nothing more you can do now, so might as well send it in for RMA.

Question about flashing updates on a rooted phone

I have a rooted 6P running the stock rom on the February security update with a bunch of Xposed modules and the Franco kernel. I know I won't get OTAs this way. Can I just flash the March security patch (MMB29V) and do nothing else? Or do I have to wipe data or factory reset? Do I have to do anything with the Franco kernel?
For the future, what would I need to do to flash Android N when it comes out on my rooted phone? Thanks a bunch!

Soundtallica said:
I have a rooted 6P running the stock rom on the February security update with a bunch of Xposed modules and the Franco kernel. I know I won't get OTAs this way. Can I just flash the March security patch (MMB29V) and do nothing else? Or do I have to wipe data or factory reset? Do I have to do anything with the Franco kernel?
For the future, what would I need to do to flash Android N when it comes out on my rooted phone? Thanks a bunch!
Click to expand...
Click to collapse
Most likely you cannot. An OTA update will do a check on your system and see that you have modified things and terminate install. You can leave your data alone but you will have to flash your boot and system partitions with the factory image
Sent from my Nexus 6P using Tapatalk

funnel71 said:
Most likely you cannot. An OTA update will do a check on your system and see that you have modified things and terminate install. You can leave your data alone but you will have to flash your boot and system partitions with the factory image
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
I know OTA updates are impossible, so I plan to flash the factory image from the Google developers website via fastboot. Does that change anything?

Soundtallica said:
I know OTA updates are impossible, so I plan to flash the factory image from the Google developers website via fastboot. Does that change anything?
Click to expand...
Click to collapse
Don't flash the entire factory image or you will lose data. / only the boot and system images to their respective partitions. Once you complete that you can Flash the OTA update zip file and you will still have your data you can extract the boot and system images from the main factory image you download from Google using WinRAR
Sent from my Nexus 6P using Tapatalk

funnel71 said:
Don't flash the entire factory image or you will lose data. / only the boot and system images to their respective partitions. Once you complete that you can Flash the OTA update zip file and you will still have your data you can extract the boot and system images from the main factory image you download from Google using WinRAR
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
It's easier to just flash all of the images (except userdata) top to update, rather than flashing two and then messing around with OTA.

So is there anyway to flash the update without losing my data/apps??
Thanks!

cattel said:
So is there anyway to flash the update without losing my data/apps??
Thanks!
Click to expand...
Click to collapse
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928

Heisenberg said:
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
Click to expand...
Click to collapse
Thank you very much!
Enviado de meu Nexus 6P usando Tapatalk

Step 9, right @Heisenberg ?

joooe said:
Step 9, right @Heisenberg ?
Click to expand...
Click to collapse
Yep. Probably would be a good idea to wipe data and the caches in TWRP first.

i used fastboot to install march update on my nexus 6p but now when trying to install twrp through fastboot it during writing it says permission denied. why is this?

mystertom said:
i used fastboot to install march update on my nexus 6p but now when trying to install twrp through fastboot it during writing it says permission denied. why is this?
Click to expand...
Click to collapse
Can you provide a screenshot of your attemp to flash the recovery? Also you might want to try opening the command prompt as administrator, right click on the command window in start menu and select open as administrator.

Heisenberg said:
Yep. Probably would be a good idea to wipe data and the caches in TWRP first.
Click to expand...
Click to collapse
Not at all a good idea @Heisenberg, as I just experienced. We were talking about keeping the apps and system as it was. Just wiped data and got an hardreset.
Clear cache only.

joooe said:
Not at all a good idea @Heisenberg, as I just experienced. We were talking about keeping the apps and system as it was. Just wiped data and got an hardreset.
Clear cache only.
Click to expand...
Click to collapse
Where did you say that? I know that wiping data will remove apps, but it's the right way to go about it to ensure no problems occur.

cattel said:
So is there anyway to flash the update without losing my data/apps??
Thanks!
Click to expand...
Click to collapse
It all went after this post.
But no problem.

joooe said:
It all went after this post.
But no problem.
Click to expand...
Click to collapse
Surely you were aware that wiping data was going to remove your apps? So all you needed to do was back them up first and restore them after you flashed. Apologies if I should have made that clear in my previous posts.

No problem. It was my stupid mistake.:good:

fastboot flash bootloader bootloader-angler-angler-02.45.img
fastboot reboot-bootloader
sleep 5
fastboot flash radio radio-angler-angler-02.50.img
fastboot reboot-bootloader
sleep 5
fastboot update image-angler-mmb29v.zip
Normally in the last line there is an option "-w" this wipes the data.
Don't do that and modify the script so the option is gone, like I did.

Uh, my phone just downloaded a system update of some sort, but I haven't installed it. Is this supposed to happen on a phone that's rooted and on the stock ROM? Can I install it safely or should I still flash the factory image instead?
And @Heisenberg, in your guide do you type in all the fastboot commands at once or do you do it line by line? Thanks again, your guide is super useful for rooting noobs like me :thumbup:

Soundtallica said:
Uh, my phone just downloaded a system update of some sort, but I haven't installed it. Is this supposed to happen on a phone that's rooted and on the stock ROM? Can I install it safely or should I still flash the factory image instead?
And @Heisenberg, in your guide do you type in all the fastboot commands at once or do you do it line by line? Thanks again, your guide is super useful for rooting noobs like me :thumbup:
Click to expand...
Click to collapse
Don't install it, it'll fail, you must flash the factory images. Each command is entered individually (press enter key to send the command), wait for flash to finish then enter the next command.

Help to get N preview 3 installed from a custom rom with no pc just TWrp

Is it possible? It not I will wait till I get home tonight. I'm thinking flash a stock rom zip. Then opt in. Don't loose all internal storage? Thoughts
Sent from my Nexus 6P using Tapatalk

iamdarren said:
Is it possible? It not I will wait till I get home tonight. I'm thinking flash a stock rom zip. Then opt in. Don't loose all internal storage? Thoughts
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
Yes it is possible. Just download the complete N factory image, plus the modified boot image (kernel).
Extract the system.img, and vendor.img out of the factory image.
And now, flash the three files using TWRP - system.img (system image), vendor.img (vendor image), and boot.img (kernel).

DJBhardwaj said:
Yes it is possible. Just download the complete N factory image, plus the modified boot image (kernel).
Extract the system.img, and vendor.img out of the factory image.
And now, flash the three files using TWRP - system.img (system image), vendor.img (vendor image), and boot.img (kernel).
Click to expand...
Click to collapse
Where can I find the modified boot image?
Edit: Found it, nevermind.

messiahfreedom said:
Where can I find the modified boot image?
Edit: Found it, nevermind.
Click to expand...
Click to collapse
Grab it from here, and make sure to download the corresponding boot.img to your build number.
Link: http://forum.xda-developers.com/nexus-6p/general/stock-modified-boot-img-regular-root-t3306684

DJBhardwaj said:
Yes it is possible. Just download the complete N factory image, plus the modified boot image (kernel).
Extract the system.img, and vendor.img out of the factory image.
And now, flash the three files using TWRP - system.img (system image), vendor.img (vendor image), and boot.img (kernel).
Click to expand...
Click to collapse
If we do it this way, will we lose data? Can we just update from 6.0.1?

jorgis1 said:
If we do it this way, will we lose data? Can we just update from 6.0.1?
Click to expand...
Click to collapse
You can if you were on a stock rom.
Sent from my Nexus 6P using Tapatalk

jorgis1 said:
If we do it this way, will we lose data? Can we just update from 6.0.1?
Click to expand...
Click to collapse
No, you won't loose any data. Your userdata/data partition will stay as is. You will just wipe the system and boot through TWRP, and then flash the listed image files.

superchilpil said:
You can if you were on a stock rom.
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
But if we do it the manual way as stated before, do we lose root? What about gapps? Will those be included?

flashfire is a great app, does it all for you...
I simply downloaded OTA through the system update, then after it was downloaded instead of allowing it to "Restart and Install" which would have failed due to my custom recovery, I just opened flashfire. It found the OTA automatically and I hit Flash button. Done!

I ended up loading up from the PC. It's better this way because I only had 2gb of space on my 64gb!!! Bad thing is, I have spent about 2hrs installing!
Sent from my Nexus 6P using Tapatalk

So I can use flashfire to flash the latest N beta even though I'm currently running a custom ROM?
Sent from my Nexus 6P using XDA-Developers mobile app

GatorsUF said:
flashfire is a great app, does it all for you...
I simply downloaded OTA through the system update, then after it was downloaded instead of allowing it to "Restart and Install" which would have failed due to my custom recovery, I just opened flashfire. It found the OTA automatically and I hit Flash button. Done!
Click to expand...
Click to collapse
Foes your custom recovery still work? I tried this method and it just wouldn't boot into TWRP. Been trying all day thru different methods. Idk how to use adb fastboot on a computer so I'm a lil lost when trying any other method. I've been using Wug's toolkit but until he pushes an update for it I'm on stock MM until i can figure something out.

x.0ni.x said:
Foes your custom recovery still work? I tried this method and it just wouldn't boot into TWRP. Been trying all day thru different methods. Idk how to use adb fastboot on a computer so I'm a lil lost when trying any other method. I've been using Wug's toolkit but until he pushes an update for it I'm on stock MM until i can figure something out.
Click to expand...
Click to collapse
why does the wug toolkit not work?

I don't know a lot about Flashfire as far as it's compatibility with Custom Roms and such. I was previously on stock android Marshmellow with root and twrp. My phone downloaded the OTA for Android N when I "enrolled" in the beta program. I chose not to allow the phone to attempt to install the OTA as it would likely fail due to my custom recovery, to my surprise when I opened flashfire it offered to install the "update.zip" (AKA the OTA) and I simply hit "flash". It installed the OTA (did not use TWRP) and rooted my phone all on it's own, I did not lose anything no data was lost.
As a side not I would not recommend using Flashfire if you don't know how to use fastboot commands and the Android SDK. It is not complicated and it is a almost certain way to fix your phone when things go haywire. I strongly encourage you to learn how to use it as it is essential to owning a Nexus imo. These root kits and flashfire programs are cool, but they are always subject to failures...

Get softbrick with bootloop

Hey guys,
This afternoon I tried to change my file system fo f2fs, I failed and got into bootloop. Follow some instructions, I flash the factory image (I was using stock 7.1.1 Feb and EX Kernel before trying f2fs) but I still face the bootloop. As I know this is a softbrick, because I can still boot into bootloader and flash recovery. But no matter how I try (flash stock, flash rom cook, flash older stock)...my 6P is still in the bootloop. I check in the TWRP that my phone is still in ext4, not f2fs anymore.
I really need some advice to wake him up. Really appreciate your help.

In all honesty bro, I never noticed much difference if any with ext4 vs f2fs. On another note, what kernel and ROM did you flash with f2fs? The the version that supports f2fs gives bootloops when you flash a custom kernel with that recovery. Try flashing the official version of recovery, reboot, then ROM and kernel if you wish and try again.
Sent from my Nexus 6P using XDA-Developers Legacy app

nhatminhng said:
Hey guys, I really need some advice to wake him up. Really appreciate your help.
Click to expand...
Click to collapse
Fastboot format your partitions and use flash-all.bat with a stock Google image.

nhatminhng said:
Hey guys,
This afternoon I tried to change my file system fo f2fs, I failed and got into bootloop. Follow some instructions, I flash the factory image (I was using stock 7.1.1 Feb and EX Kernel before trying f2fs) but I still face the bootloop. As I know this is a softbrick, because I can still boot into bootloader and flash recovery. But no matter how I try (flash stock, flash rom cook, flash older stock)...my 6P is still in the bootloop. I check in the TWRP that my phone is still in ext4, not f2fs anymore.
I really need some advice to wake him up. Really appreciate your help.
Click to expand...
Click to collapse
Why do you still have TWRP if you flashed stock? You need to flash the complete stock image including the stock recovery.

MidnightDevil said:
In all honesty bro, I never noticed much difference if any with ext4 vs f2fs. On another note, what kernel and ROM did you flash with f2fs? The the version that supports f2fs gives bootloops when you flash a custom kernel with that recovery. Try flashing the official version of recovery, reboot, then ROM and kernel if you wish and try again.
Sent from my Nexus 6P using XDA-Developers Legacy app
Click to expand...
Click to collapse
jhs39 said:
Why do you still have TWRP if you flashed stock? You need to flash the complete stock image including the stock recovery.
Click to expand...
Click to collapse
v12xke said:
Fastboot format your partitions and use flash-all.bat with a stock Google image.
Click to expand...
Click to collapse
Thanks guys for helping. I fixed it.
I always flashed the stock image step by step followed by heisenberg, and never use the flash-all.bat just because I dont understand how to run it. However a guy in the f2fs told me to add in some steps
fastboot format system
fastboot format userdata
fastboot format cache
Click to expand...
Click to collapse
And it works. It seems like the step by step way is not clear enough. Any guys can tell me how to run the flash-all.bat please? When I run it always said fastboot is not etc...

nhatminhng said:
Thanks guys for helping. I fixed it. I always flashed the stock image step by step followed by heisenberg, and never use the flash-all.bat just because I dont understand how to run it. However a guy in the f2fs told me to add in some steps And it works. It seems like the step by step way is not clear enough. Any guys can tell me how to run the flash-all.bat please? When I run it always said fastboot is not etc...
Click to expand...
Click to collapse
It's a good sign you formatted and received no errors in fastboot. Google provides instructions for flash-all.bat on the same page you download the images from. https://developers.google.com/android/images
If you are not comfortable using the command window in Windows, you could also use a toolkit like Wugfresh's NRT or Skipsoft's Toolkit to automate the whole process.

v12xke said:
It's a good sign you formatted and received no errors in fastboot. Google provides instructions for flash-all.bat on the same page you download the images from. https://developers.google.com/android/images
If you are not comfortable using the command window in Windows, you could also use a toolkit like Wugfresh's NRT or Skipsoft's Toolkit to automate the whole process.
Click to expand...
Click to collapse
Yes sir of course I read it. But I dont understand this step.
Open a terminal and navigate to the unzipped system image directory.
Click to expand...
Click to collapse
Is it I open the fastboot cmd, use cd command to navigate to that directory? I already tried but failed to run :'( Although I have fixed it but I want to know just in case the next time. Thanks.

nhatminhng said:
Yes sir of course I read it. But I dont understand this step.
Is it I open the fastboot cmd, use cd command to navigate to that directory? I already tried but failed to run :'( Although I have fixed it but I want to know just in case the next time. Thanks.
Click to expand...
Click to collapse
Hi... Here's a pretty good detailed process on how to unlock/flash, etc...
https://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928/page549
Also, before using any toolkit, I suggest using manual commands and getting comfortable with it. At least, you learn exactly what command do what! Simply pressing a button in a program may result in a bricked device. Plus with command line you learn something. :good:

@nhatminhng How did you get your phone fixed? is your phone unlocked?

tjchuot287 said:
@nhatminhng How did you get your phone fixed? is your phone unlocked?
Click to expand...
Click to collapse
What do you mean "unlocked"? The bootloader is unlocked and I can flash recovery too. I use the command line in heisenberg thread and flash my phone to stock. Add in some more steps I mentioned above. Boom. It's back again.

nhatminhng said:
What do you mean "unlocked"? The bootloader is unlocked and I can flash recovery too. I use the command line in heisenberg thread and flash my phone to stock. Add in some more steps I mentioned above. Boom. It's back again.
Click to expand...
Click to collapse
@nhatminhng oh, im sorry, i mean unlocked bootloader. So my bootloader is locked, it still doesnt have any solutions yet.

tjchuot287 said:
@nhatminhng oh, im sorry, i mean unlocked bootloader. So my bootloader is locked, it still doesnt have any solutions yet.
Click to expand...
Click to collapse
Do you have access to recovery or just boot loader?
Sent from my Nexus 6P using XDA-Developers Legacy app

CyberpodS2 said:
Do you have access to recovery or just boot loader?
Sent from my Nexus 6P using XDA-Developers Legacy app
Click to expand...
Click to collapse
Yes i can. I tried to sideload multiple version of OTA but all have failed.

tjchuot287 said:
Yes i can. I tried to sideload multiple version of OTA but all have failed.
Click to expand...
Click to collapse
I'm guessing you've already tried a factory reset from the stock recovery. Because your bootloader is locked you are limited to sideloading OTA's. And yes, sideloading an older or equal version OTA will fail. You can try a newer revision OTA when available. The 7.1.2 beta may come out before the March security update.

v12xke said:
I'm guessing you've already tried a factory reset from the stock recovery. Because your bootloader is locked you are limited to sideloading OTA's. And yes, sideloading an older or equal version OTA will fail. You can try a newer revision OTA when available. The 7.1.2 beta may come out before the March security update.
Click to expand...
Click to collapse
Good point. It didn't occur to me that equal version would fail. Folks need to unlock their boot loaders! Lol
Sent from my Nexus 6P using XDA-Developers Legacy app

CyberpodS2 said:
Good point. It didn't occur to me that equal version would fail. Folks need to unlock their boot loaders! Lol
Click to expand...
Click to collapse
I agree. Unless you absolutely cannot live without Android Pay or Wallet, work phone, etc., there is no reason to not unlock the bootloader as a safeguard. Of course it's no guarantee, but you just have a whole lot more tools at your disposal when SHTF, including restoring a recent backup or flashing a complete stock image. The initial pain of losing your data can be largely mitigated by pulling it off first, and eventually you even forget about the boot nag screen.

v12xke said:
I agree. Unless you absolutely cannot live without Android Pay or Wallet, work phone, etc., there is no reason to not unlock the bootloader as a safeguard. Of course it's no guarantee, but you just have a whole lot more tools at your disposal when SHTF, including restoring a recent backup or flashing a complete stock image. The initial pain of losing your data can be largely mitigated by pulling it off first, and eventually you even forget about the boot nag screen.
Click to expand...
Click to collapse
Now i have unlocked bootloader but the phone keep restart and stuck at logo again. i followed @Heisenberg thread but same result.