Related
Hey guys, I'm currently trying to flash back to the new 4.3 factory image that I downloaded from Google, however, it all goes fine, I flashed the bootloader, flashed the radio and it all says it has been updated properly, then when I try and flash the system.img files and boot.img files they just say no such file or directory exists and stops, meaning the phone is unusable at the moment until I flash something.
Anyone know why this is happening?
BTW I'm using a mac.
Issue fixed, see below!
************************************************************************************************
Ok guys, the problem was solved in an odd way!
I got annoyed with the flashing errors, and flashed the old kernel and radio I was using with my Illusion rom which thankfully got me back to that even though I had lost all of my data (backed up though).
For anyone having this problem and wants to unroot to go back to 4.3 or is trying to flash the legit 4.3 rom from Google and then maybe unroot or just use the 4.3 rom direct from Google...
DOWNLOAD THE LEAKED 4.3 ROM AND FLASH USING STANDARD CWM METHOD.
DOWNLOAD THE .84/.83 KERNEL AND FLASH THIS AS WELL.
After this I got the legitimate OTA update which was only 3.4mb and it even fixed root so I am now back to complete stock, locked bootloader and no root!
Hope this helps
Click to expand...
Click to collapse
Easiest way of flashing the system image is to just use the flash-all script included in the TGZ - just extract it out and run it when the phone is connected in fastboot mode. Personally, I do the following:
1. Extract the entire TGZ (including the update.zip)
2. Move all the IMG files into one folder
3. Rename them to easy names, e.g. bootloader, radio, system, userdata, boot, recovery, etc.
4. Flash them all in turn, rebooting the bootloader each time
5. Once all done, erase/format the cache (fastboot erase cache and fastboot format cache)
6. Boot into recovery and clear cache again and then do a factory reset (this makes sure the unit see all the internal memory)
7. Reboot the phone
Should all work now
siravarice said:
Hey guys, I'm currently trying to flash back to the new 4.3 factory image that I downloaded from Google, however, it all goes fine, I flashed the bootloader, flashed the radio and it all says it has been updated properly, then when I try and flash the system.img files and boot.img files they just say no such file or directory exists and stops, meaning the phone is unusable at the moment until I flash something.
Anyone know why this is happening?
BTW I'm using a mac.
Click to expand...
Click to collapse
Maybe you have corrupted files? Retry the download from google and unpack all with 7zip.
I did that yesterday and all works fine.
4.3 (JWR66V)
https://dl.google.com/dl/android/aosp/occam-jwr66v-factory-08d2b697.tgz
7zip
http://www.7-zip.de/
[HOW-TO] How to flash a factory image / return to stock / unlock / root #
http://forum.xda-developers.com/showthread.php?t=2010312
EddyOS said:
Easiest way of flashing the system image is to just use the flash-all script included in the TGZ - just extract it out and run it when the phone is connected in fastboot mode
Click to expand...
Click to collapse
How would I do that on a mac? I tried typing:
./fastboot flash flash-all.bat
but do I need to use the .sh version?
info.brandenburg said:
Maybe you have corrupted files? Retry the download from google and unpack all with 7zip.
I did that yesterday and all works fine.
Click to expand...
Click to collapse
Did that, same thing happened. I tried flashing the entire .zip and then I tried separately and it still didn't work.
Ok so I know it is just the system.img file that doesn't work, as all the other files have just flashed fine! Going to re-download and see if that helps.
siravarice said:
How would I do that on a mac? I tried typing:
./fastboot flash flash-all.bat
but do I need to use the .sh version?
Click to expand...
Click to collapse
You just run the script, you don't flash it. It's a batch file which then does all the fastboot commands. You also use flash-all.sh as you don't have Windows
EddyOS said:
You just run the script, you don't flash it. It's a batch file which then does all the fastboot commands. You also use flash-all.sh as you don't have Windows
Click to expand...
Click to collapse
Still doesn't work.
I used: bash flash-al.sh
And it just said fastboot not found in certain lines for the command and did nothing. I thought it fixed itself when I swapped USB ports but when it got to the system.img it just gave me the same error again. It flashes everything else ok but not this file, it's the third time I have downloaded it and now I have no way to get it back to being useable as when I press start it just gives me a black screen
HELP PLEASE!
I would but I use Windows and it's all fine. Might be worth downloading the factory image again, checking the md5 and trying to flash the system image again
EddyOS said:
I would but I use Windows and it's all fine. Might be worth downloading the factory image again, checking the md5 and trying to flash the system image again
Click to expand...
Click to collapse
Im trying to install some Samsung Android Drivers on my old laptop but the thing is so slow it's basically impossible to work from now
I've redownloaded the files, I don't know how to check the MD5Sum though. Still nothing doing. I get this error:
checking product... OKAY
checking version-bootloader... OKAY
checking version-baseband... OKAY
sending 'boot' (6166 KB)... OKAY
writing 'boot'... OKAY
sending 'recovery' (6664 KB)... OKAY
writing 'recovery'... OKAY
sending 'system' (531281 KB)... ERROR: usb_write failed with status e00002be
FAILED (data transfer failure (No such file or directory))
edue3e4:4.2unrootnexus4 Simon$
It really doesn't want to write the system.img file, or maybe it doesn't want to write to system?
What happens if you extract the system.img file and flash it via fastboot manually?
fastboot flash system system.img
I always use this guide if I forget:
efrant said:
D. Type in the commands into the command prompt
1) Make sure your computer recognizes your device by typing: fastboot devices
2) Unlock your bootloader (if you have not already done so): fastboot oem unlock
3) You will see a prompt on your device. This will wipe your entire device (including the /sdcard folder). Accept. Note: you use the volume keys to change the option and the power button to accept. You cannot use the touch screen.
4) Reboot by typing: fastboot reboot-bootloader
5) Flash the bootloader: fastboot flash bootloader bootloader-mako-makoz10o.img (or whatever the name of the bootloader image that you downloaded).
6) Reboot: fastboot reboot-bootloader
7) Flash the radio: fastboot flash radio radio-mako-m9615a-cefwmazm-2.0.1700.48.img (or whatever the name is of the radio image that you downloaded).
8) Reboot: fastboot reboot-bootloader
9) Flash the system partition: fastboot flash system system.img
10) Flash the data partition: fastboot flash userdata userdata.img Note: this command will wipe your device (including /sdcard), EVEN if your bootloader is already unlocked. See note 2 below.
11) Flash the kernel/ramdisk: fastboot flash boot boot.img
12) Flash the recovery partition: fastboot flash recovery recovery.img
13) Erase the cache partition: either a) fastboot erase cache OR b) fastboot format cache <<== the second option seems to work better for most people. Thanks joostburg.
14) Reboot: fastboot reboot
15) Done! The first boot will likely take quite a bit longer than you are used to, as Android builds the Dalvik cache.
Now you have a fully stock image on your device. The only thing that is different from out-of-the-box condition is that your bootloader is unlocked. See the notes section at the end of this post for information on re-locking the bootloader.
Note that some users indicate that they can't get past the X on boot. If this happens to you, reboot into the bootloader and select recovery. Then, when you see the Android with the red exclamation mark, hold power and press volume up to take you to the menu. Wipe cache. If that still doesn't work, boot back into recovery and do a factory reset.
If you have a 16GB device, and it now shows up as 8GB, reboot into recovery (hold power and press volume up when you are at the screen with the android and the red exclamation mark), and wipe cache. If that still doesn't work, boot back into recovery and do a factory reset. Or do this
Click to expand...
Click to collapse
EddyOS said:
What happens if you extract the system.img file and flash it via fastboot manually?
fastboot flash system system.img
I always use this guide if I forget:
Click to expand...
Click to collapse
That's exactly what I have been doing, I prefer doing it manually as I don't like using Toolkits and finding a good one for mac is hard enough.
It just says that it cannot send it because the file or directory does not exist, yet if I unplug the phone it does go back into my old rom I was using before that, even though I flashed a new radio and recovery.img, boot.img, user data.img, everything except system.img as it doesn't work
Something clearly wrong with the partition but no idea what...
I know right, I've gone back to the ROM I had previously and downloaded the leaked 4.3 rom and flashed it through flashify. If it works I will simply lock the bootloader again and it should be good to go!
i did the same way through nexus tool kit 2.0 n p.s i guess the file was corrupted that y it failed in the mid. ill try it again
Hmmy 4444 said:
i did the same way through nexus tool kit 2.0 n p.s i guess the file was corrupted that y it failed in the mid. ill try it again
Click to expand...
Click to collapse
Let me know if you get anywhere with it!
it worked.. jst copy the image n dont rename it n go to google nexus 4 toolkit folder n there u would see a folder named *put googlr factory image here* paste it there n before starting ur bootloader must be unlocked.. so thats that.. after that that open the nexus 4 toolkit n then click on number 9 whch says download extract + flash google factore stock rom n then after that type 2 whch says flash google factory image... n thats it. it will automatically flash it.... gv me thanks too
Sent from my Nexus 4 using xda app-developers app
Hi there, same issue with me on a mac
Plus can you tell me how you went back to the previous rom, my phone is unusable right now and i do have a nandroid backup so.
Have either of your tried to flash the 4.2.2 factory image? Would be interested to see if it works
Sent from my Nexus 4 using xda premium
EddyOS said:
Have either of your tried to flash the 4.2.2 factory image? Would be interested to see if it works
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
I dont mind, can you direct me towards a post where they show how to, i m not sure of all this and dont want to mess around with wrong files.
UPDATE: I tried and that works just fine. Rebooted to 4.2.1
I decided to go to Android 5.0.1 from CM10.2 on my Nexus 4. I guess I did not think it though that well and relied on some crappy guides too much.
I have CWM Recovery 6.4.3 installed, so I thought I just place the factory image on the phone and install it via CWM. So:
1) Copied occam-....tgz on the phone;
2) Rebooted into CWM recovery;
3) Did wipe cache/format system/wipe dalvik;
4) Went to install .zip menu... and figured out that the file is no longer on my phone.
I thought OK, I do it via ADB and cable, so installed ADB, drivers etc. and connected my phone to my computer. However, adb does not see it most of the time (when at logo, bootloader, recovery) and only once adb managed to see it (*some number* device unauthorized) while the phone was at Google logo. And I realized I forgot to set up the USB debug option. What are my options now? I can go into CWM recovery, but ADB does not see the device, as I forgot to set up recovery before flashing. Help, please?
The computer sees the phone as MLP, but I still cannot see its storage in Explorer, so I cannot copy the .zip file.
Update
I managed to make adb recognize the phone, but consistently says that it is not authorized, which makes sense. And there is not way I can mount it as an external storage .
first of all, you have a serious lack of knowledge. not activating USB debugging in android settings has no effect whatsoever on ADB usage ability when you are in recovery mode. Secondly, installing factory images is not done through recovery (the downloaded factory image zip is not even flashable so it would work not in recovery), as factory images also contain RADIO and BOOTLOADER images that are flashable through fastboot (not the recovery). The only thing from factory image that you could flash via recovery is a zip file named - in case of 5.0.1 factory image - image-occam-lrx22c.zip (you can find it if you unpack the downloaded factory image on your PC). And this zip file is a classic ROM (system,userdata,boot,cache,recovery partitions). However, even if you were to flash the correct zip (rather than the zip containing entire factory image complete with ROM, RADIO and BOOTLOADER) Android 5.0 (or 5.0.1) comes with updated RADIO (maybe bootloader aswell, i did not check), so you are supposed to update that aswell prior to switching to 5.0/5.0.1
now here is what you should do:
1. download 5.0.1 factory image from gooogle
2. make sure you have ADB and drivers for Nexus4 correctly set up (in order to check wheter it works go see point 3 of this instruction set)
3. boot to fastboot mode (vol down+power) and check if 'fastboot devices' gives you back device id (you should open command prompt in platform-tools folder, where both adb.exe and fastboot.exe are present)
4. proceed with this instruction, start at step 8 http://androidforums.com/threads/guide-how-to-flash-a-nexus-factory-image-manually.706533/ (in step 11, name of zip file is the one that is INSIDE downloaded factiory image file (image-occam-lrx22c.zip) and you either do the single zip flash or flashing each of .img files separately (system,boot,userdata,cache,recovery)
ps. 1st android 5.0.1 boot after flashing will take up to 15 minutes. (it took 10 in my case)
Update 2
Thanks dzumagos! Sure, I do not claim to be a specialist by any means. I managed to successfully install Cyanogenmod many times, so thought I would give this one a go as well.
I read your post after I fixed the issue. Basically I did exactly what you suggested, but following another guide and it worked fine, also took it around 15 minutes to load the first time. I noticed I do miss a few tricks from Cyanogenmod
Tired of waiting for the OTA? Can't use it because you're rooted? Don't want to wipe your entire phone? No problem! Here's how you can upgrade with Google's Nexus factory images without wiping your apps or sdcard.
NOTE: You must have your bootloader unlocked. If you've never unlocked your bootloader, I don't think there's any way to do this without wiping your data.
STEP 1: Install fastboot
Fastboot is Google's utility for flashing factory images. You can also use it to flash custom recoveries like TWRP and CWM. The standard way to get is is through Google's Android SDK, but that's a bit heavy-duty, so you can also download just the most important tools (fastboot and adb) separately, packaged by users. Here are some links:
Official Google Android SDK (cross-platform): http://developer.android.com/sdk/index.html#Other[1]
Unofficial for Windows: http://developer.android.com/sdk/index.html#Other[2]
Unofficial Mac/Linux: http://code.google.com/p/adb-fastboot-install/[3]
Windows users might also need to install drivers: http://developer.android.com/sdk/win-usb.html[4] (can any Windows users confirm whether it's necessary?)
STEP 2: Prepare factory image
Download the latest Nexus 6 factory image at https://developers.google.com/android/nexus/images#shamu[5]
Unzip it and open the resulting folder
Unzip the "image-shamu-*.zip" file in there
You should now be looking at something like this: http://i.imgur.com/mzrfwrP.png [6]
STEP 3: Flash! (Ah-ahhhhh! [7] )
Connect your phone to your computer via USB, and enter the bootloader. You can enter the bootloader by holding down the power and volume-down buttons to boot. Once you see the bootloader, you can release the buttons.
Open a terminal/command prompt. The syntax might be slightly different on Windows than on Mac or Linux, but basically the same. Anything you see in <> you need to replace, e.g. with the actual path to your factory image folder. The rest you should be able to copy and paste. (Tip: you can easily enter a folder path into your terminal/command prompt by simply dragging the folder onto your terminal window. This works on Mac, Windows, and the vast majority of Linux GUIs.) Enter these commands:
cd </path/to/shamu-lmy47d>
fastboot flash bootloader bootloader-shamu-moto-apq8084-71.08.img
Reboot the bootloader.
fastboot flash radio radio-shamu-d4.0-9625-02.95.img
cd <image-shamu-lmy47d>
fastboot flash boot boot.img
fastboot flash cache cache.img
fastboot flash system system.img
If you DO NOT use a custom recovery (like TWRP or CWM), then also: fastboot flash recovery recovery.img
Don't worry if you see messages like "target reported max download size of 1073741824 bytes". Just wait and let it finish.
Reboot your phone and enjoy. It's normal for the first boot to take a while. Going from Kitkat to Lollipop took about 20 minutes. Going from 5.0 to 5.0.1 took 5-10, I think. YMMV.
A WORD OF WARNING: If you're moving between ROMs, you generally should do a complete reset, including wiping data. Many users have reported problems going from KitKat to Lollipop without wiping data and recommend a factory reset anyway. If you're okay with wiping everything, you can simply use Google's included flash-all scripts, or flash the userdata.img file yourself. Personally, I'm not going to bother wiping adta for an incremental update like 5.0.1->5.1. As always, be sure to back up your data!
Shamelessly stolen from: http://www.reddit.com/r/Nexus5/comments/2phqy7/howto_upgrade_android_using_nexus_factory_images/
Shouldn't you also fastboot reboot bootloader after radio flash?
This is the scenic route.
I tried to update using wugz, without unlocking the bootloader. failed. Oh well, I'll wait to receive ota
Unless this method doesnt require unlocking?
If you have an OTA zip file, this is different than using a System Img?
I do not think you need to lose data or unlock your bootloader?
Found a link for the OTA zip file.
If I remember right you can copy the zip to you phone with a USB cable.
Go into the bootloader, Volume Down and Power.
Select the zip.
I did not think you needed a terminal and all the commands if you had the OTA zip on your phones SD card.
Am I wrong does something like this not work?
or
I can just wait.....
This worked great.
I was unbranded with VZ sim, unlocked, rooted with TWRP recovery. Didn't want to lose all that nor my apps or data. This method upgrades to 5.1 without any loss.
When I was done with the flashing, I rebooted to TWRP recovery (not system) in order to wipe dalvik and cache (just to be certain). I wiped and then rebooted to system. TWRP noticed I didn't have SuperSU installed so it installed it for me. Meaning, once I got my system rebooted, I still had root too.
All in all, this process worked great for me. Thanks.
I run the first two commands
fastboot flash bootloader bootloader-shamu-moto-apq8084-71.08.img
fastboot reboot-bootloader
they worked, then i moved to the radio
fastboot flash radio radio-shamu-d4.0-9625-02.95.img
but it failed.
Any idea?
---------- Post added 14th March 2015 at 12:17 AM ---------- Previous post was 13th March 2015 at 11:53 PM ----------
Nikos2k said:
I run the first two commands
fastboot flash bootloader bootloader-shamu-moto-apq8084-71.08.img
fastboot reboot-bootloader
they worked, then i moved to the radio
fastboot flash radio radio-shamu-d4.0-9625-02.95.img
but it failed.
Any idea?
Click to expand...
Click to collapse
This is the message after the radio flash command:
fastboot flash radio radio-shamu-d4.0-9625-02.95.img
target reported max download size of 536870912 bytes
sending 'radio' (85422 KB)...
OKAY [ 2.697s]
writing 'radio'...
(bootloader) flashing modem ...
(bootloader) flashing modem ...**☺
FAILED (unknown status code)
finished. total time: 3.721s
Why the failed message?
I'm decrypted. Will this re encrypt my Nexus or do I have to flash a non enforce img?
Thank you, this really helped.
Since my bootloader was locked i had to unlock it as well.
Had a bit of a scare with the whole erasing screen staying on for too long.
Went back and redid the process, and went downstairs for 5 minutes, came back and phone was booted.
Anyway, thank you again
Will this work on an encrypted phone?
mikeadamz said:
Tired of waiting for the OTA? Can't use it because you're rooted? Don't want to wipe your entire phone? No problem! Here's how you can upgrade with Google's Nexus factory images without wiping your apps or sdcard.
<<snip>>
Click to expand...
Click to collapse
I don't suggest that anyone read and follow someone else's instructions when doing something like this. Not because the instructions are wrong or anything, but because blindly following instructions doesn't involve *understanding* anything.
So rather than reading and following instructions, read and UNDERSTAND the process of installing factory images as delivered with the factory images (flash-all.sh). If you UNDERSTAND the process and what everything does, then (a) you *already know* what needs to be adjusted to do what you want, and (b) if something starts going wrong in the middle of it, you will understand why, and what to do to correct it.
mikeadamz said:
cd </path/to/shamu-lmy47d>
fastboot flash bootloader bootloader-shamu-moto-apq8084-71.08.img
Click to expand...
Click to collapse
First, thanks for the write up, I do greatly appreciate it. Second, thanks for the tip on dragging file locations into the command prompt. Very helpful.
Now my question. When I did this I tried using exactly the steps above and had no luck whatsoever. I'd cd to the location of the img files as noted and it would say fastboot is unrecognized as an internal or external command. I moved the file into the fastboot location and got the same issue. I finally ran the fastboot from the adb folder location and just referenced the full file path for each img file (using the drag and drop method) and everything went swimmingly. My question is just about using fastboot. Should it have worked when I used cd to go to the img file location? Is there something I need to do to make it work as you described?
Thanks!
Nick
Nick D said:
First, thanks for the write up, I do greatly appreciate it. Second, thanks for the tip on dragging file locations into the command prompt. Very helpful.
Now my question. When I did this I tried using exactly the steps above and had no luck whatsoever. I'd cd to the location of the img files as noted and it would say fastboot is unrecognized as an internal or external command. I moved the file into the fastboot location and got the same issue. I finally ran the fastboot from the adb folder location and just referenced the full file path for each img file (using the drag and drop method) and everything went swimmingly. My question is just about using fastboot. Should it have worked when I used cd to go to the img file location? Is there something I need to do to make it work as you described?
Thanks!
Nick
Click to expand...
Click to collapse
Install this:
http://forum.xda-developers.com/showthread.php?t=2588979
Now ADB and fastboot are installed system wide. Put your files anywhere, I use the desktop. Hold shift and right click on wherever your files are and select "open command prompt here" and flash away. Simplified, no more dragging and dropping.
Will try with the new update (5.1.1 (LMY48M)) to ensure it works. Thanks!
[/COLOR]
handyarrow said:
Will this work on an encrypted phone?
Click to expand...
Click to collapse
Have been flashing this zip in twrp after the fastboot stage without an issue for the last few updates - http://forum.xda-developers.com/nexus-6/development/mod-disable-force-encryption-rom-kernel-t3000788
Flashed LMY48M with fastboot method and it works great.
My phone is encrypted.
Hi,
I did search, but I didn't find any solution to the issue. I got the Nexus 6P 64 GB.
I unlocked my bootloader using the 6p Multitool. Thereafter I used my normal method of fastboot (Minimal ADB) to flash the boot.img from this thread http://forum.xda-developers.com/apps/supersu/wip-android-6-0-marshmellow-t3219344.
After that I flashed TWRP. Basically I followed the instructions here: http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928.
But my phone is not booting up.
It gives me this error:
Your device software cannot be checked for corruption. Please lock the bootloader."
But I tried that and it doesn't work. I tried from fastboot restoring to factory, but get the same message.
Please help me!
Did you check the enable oem unlocking in developer settings?
Sent from my Nexus 6P using Tapatalk
Yes. As I said, I achieved the unlock. Now I just can't get back into my phone or recovery or anything other than fastboot (where it says unlock)
isn't "Your device software cannot be checked for corruption. Please lock the bootloader." the new msg on boot when you are unlocked, and you have to wait ~10 secs before it startup ?
After that, I'm stuck on the Google screen. It just goes on and on. Left it for over 20 minutes at one point and it didn't get past it.
Edit: The multicolored animated google screen. The animation just keeps going and going.
Del.
Your issue might be due to the encryption of the phone. Take a look at this thread: http://forum.xda-developers.com/nex...recovery-twrp-2-8-7-0-touch-recovery-t3234976
From this thread:
NOTE: Decrypting data is not supported yet. The Nexus 6P will normally attempt to encrypt the device automatically on first boot. To use TWRP as you normally would, you will have to format data and install a slightly modified boot image with forceencrypt disabled. My Nexus 6P should arrive tomorrow and I will start working on decrypt once I get my hands on it.
Team Win Recovery Project 2.x, or twrp2 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
Read through that thread. Part of the issue is that I don't know which variant (MDA89D & MDB08K) I have, or how to find that out seeing as I can't boot into the phone.
If I have the variant I may be able to fix this through the unified toolkit (though I'm not sure of that)
Did you ever fix this?
Try flashing the factory image and starting from scratch. You must have messed up somewhere. Re-download the boot.img from Chainfire's thread, maybe that was corrupt or something.
1. Download the MDB08K factory image (it's not a variant, it's a Marshmallow update) and unzip it.
2. Download the MDB08K boot.zip from Chainfire's modified boot.img thread
3. Download latest SuperSU beta zip
Wipe phone in TWRP, to include format data.
In bootloader, fastboot flash MDB08K
fastboot flash modified boot.img (from zip)
In TWRP, ADB sideload SuperSU
Reboot and it should perform normally.
kibmikey1 said:
1. Download the MDB08K factory image (it's not a variant, it's a Marshmallow update) and unzip it.
2. Download the MDB08K boot.zip from Chainfire's modified boot.img thread
3. Download latest SuperSU beta zip
Wipe phone in TWRP, to include format data.
In bootloader, fastboot flash MDB08K
fastboot flash modified boot.img (from zip)
In TWRP, ADB sideload SuperSU
Reboot and it should perform normally.
Click to expand...
Click to collapse
Thank you for your reply, but I can't get into TWRP either!! Any way for me to restore to factory or do the repairs from in flashboot without the restore?
I ran into the same issue last night trying to install TWRP. I'm still not sure how to get around it but I did get my phone back. you should be able to get to the bootloader (hold the power button until phone turns off, then hold vol up+vol down+power) once there use ADB fastboot to go back to stock.
this link will walk you through what you need. follow step 7.
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
here it is as well:
How To Flash The Factory Images (And Return To Stock)
Prerequisites: unlocked bootloader (section 1).
Download the appropriate factory images for your model here.
Unzip the angler-xxxxxx-factory-xxxxxxxx (x's replace variables) into a directory on your PC (for this guide we'll use C:\angler\).
Once unzipped you should have a folder named angler-xxxxxx (x's replace variables). Open it and move the following files to a new directory named C:\angler\images\:
bootloader-angler-angler-01.31.img
radio-angler-angler-01.29.img
(Please note that radio and bootloader naming changes from build to build so the filenames and below commands will change with them)
Within C:\angler\angler-xxxxxx\ you'll see another zip archive named image-angler-xxxxxx, unzip the contents of that zip into the C:\angler\images\ folder we created before. Now within C:\angler\images\ you should have the following files:
android-info.txt
boot.img
bootloader-angler-angler-01.31.img
cache.img
radio-angler-angler-01.29.img
recovery.img
system.img
userdata.img
vendor.img
Boot into the bootloader and connect your phone to your PC via usb cable.
Open a command prompt from within your fastboot folder (navigate to where you have fastboot.exe located on your PC, shift + right click anywhere within that folder, select open command prompt here), enter these commands to flash:
Code:
fastboot flash bootloader C:\angler\images\bootloader-angler-angler-01.31.img
fastboot reboot-bootloader
fastboot flash radio C:\angler\images\radio-angler-m8994f-2.6.28.0.65.img
fastboot reboot-bootloader
fastboot flash boot C:\angler\images\boot.img
fastboot erase cache
fastboot flash cache C:\angler\images\cache.img
fastboot flash recovery C:\angler\images\recovery.img
fastboot flash system C:\angler\images\system.img
fastboot flash userdata C:\angler\images\userdata.img
fastboot flash vendor C:\angler\images\vendor.img
Thank you. I was eventually able to do tysonwald's suggestion. First I didn't know what my version was, so I couldn't.
At some point I was able to get into the phone with constant gapp errors, check it.
Now my phone is unlocked and rooted. But when I go to settings to security (and when I tried to set up my fingerprint) settings crashes. Any ideas?
There was still some issue. I wiped the phone with the above method again, did NOT set up twrp/root, and everything works. It was something about the custom boot image I guess. Any advice if I want to try to set it up again?
Problem solved. Needed to update to newer image before doing everything. Issue resolve from Heisenberg's thread. Thank you all!
I had the same damn issue last night. Thise bootleg instructions had me flashing build k boot.img on build D. Maybe i wasnt paying attention lol!
I have a very similar problem, I flashed the k boot img. and now I'm stuck in an endless bootloop any idea?
TeriusPR said:
I have a very similar problem, I flashed the k boot img. and now I'm stuck in an endless bootloop any idea?
Click to expand...
Click to collapse
Read thru this guide and follow the instructions to the T. http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
I had a similar issue just now where my phone got stuck at the TWRP logo. Selecting the reboot option in download mode refused to remove it. I had to follow step 10 to get my phone back to stock. I'm afraid to try this again now
Is there anyway to know which version do i need to download? i bought the phone already bricked and i am trying to bring it back to life
I tried to update my phone to the latest version. I hit install from the notification, my phone reboots goes into TWRP recovery.... does nothing, then I have to "reboot into system" and then the phone boots up like normal.
Without updating to 6.0.1. Does anyone know why this is happening, or how to fix it?
I think you can't update the phone with official update method (Settings/About/System Updates) when you have unlocked bootloader and root.
READ.
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
xT29c said:
I tried to update my phone to the latest version. I hit install from the notification, my phone reboots goes into TWRP recovery.... does nothing, then I have to "reboot into system" and then the phone boots up like normal.
Without updating to 6.0.1. Does anyone know why this is happening, or how to fix it?
Click to expand...
Click to collapse
You must return to complete stock, including recovery, before attempting an OTA update
Sent from my Nexus 6P using Tapatalk
As mentioned above, you can't use the traditional method of updating if you are are rooted and have TWRP installed. You will need to flash the images manually with your PC in order to update. There are multiple ways of doing this, but the easiest way I've found takes about 5 or 10 minutes and is documented elsewhere on this site, but long story short:
-install and confirm that ADB/Fastboot works on your PC and can see your phone
-download the latest image directly from google
-unzip the downloaded file on your PC and then unzip the file that was just extracted into your ADB folder
-edit the "flash-all.bat" batch file to remove the "-w" toward the end (to prevent wiping your data)
-put all extracted files into your ADB / Fastboot directory.
-connect your phone to your PC, power it on or reboot it into bootloader mode, and run the batch file that you edited (this will put you back to stock / unrooted)
-re-flash the twrp recovery image using fastboot
-re-root (install SU.zip using twrp).
That's my preferred method, and once you have everything setup (ADB / Fastboot working & factory image downloaded) is should only take a couple of minutes to perform.
As mentioned before, this is well documented elsewhere on this site. I may have missed steps or left out information as I am writing fast because I am currently at work.
Good Luck!