Database Users

[Q] Issue with Clockwork mod recovery after JOP40D update

I recently updated to android 4.2.1 and ever since then I cannot boot into recovery using CWM. When I try to do it, a picture of an android guy and a red triangle with an exclamation point inside appears and after a couple minutes it reboots as normal. Please help! I couldn't find any answers in the forums.

From efrant's nexus 4 101 sticky: http://forum.xda-developers.com/showthread.php?t=2010338
I just flashed CWM, but every time I try to boot into CWM, I keep seeing the stock recovery. Why?
If you updated your Android build using an OTA update file (either manually or over-the-air), the update placed two files on your device that re-flash the stock recovery every time you reboot your device. These two files are:
/system/etc/install-recovery.sh <== this is the script that installs the patch file
/system/recovery-from-boot.p <== this is the patch
You have to rename (or delete) one or both of them, then re-flash your custom recovery. Now it will stick.
Click to expand...
Click to collapse

Couldn't locate
El Daddy said:
From efrant's nexus 4 101 sticky: http://forum.xda-developers.com/showthread.php?t=2010338
Click to expand...
Click to collapse
I could not locate those files on my device. Am I doing something wrong?

gson55 said:
I could not locate those files on my device. Am I doing something wrong?
Click to expand...
Click to collapse
Have you tried flashing cwr with fastboot?
fastboot flash recovery cwr.img
Sent from my Nexus 7 using Tapatalk HD

El Daddy said:
Have you tried flashing cwr with fastboot?
fastboot flash recovery cwr.img
Sent from my Nexus 7 using Tapatalk HD
Click to expand...
Click to collapse
No I have not used fastboot.

What is your ultimate goal here?
Do you want stock with root? Or a custom ROM?
Sent from my Nexus 7 using Tapatalk HD

El Daddy said:
What is your ultimate goal here?
Do you want stock with root? Or a custom ROM?
Sent from my Nexus 7 using Tapatalk HD
Click to expand...
Click to collapse
Originally I had root and was just using my stock ROM but I wanted to flash a custom ROM now.

OK. First you'll need the platform tools located here: http://forum.xda-developers.com/attachment.php?attachmentid=1506153&d=1353717141
If you don't have fastboot drivers installed get them from here: http://forum.xda-developers.com/showthread.php?t=1996051
Once those are set up download the rom and gapps of your choice and put them on your phone.
Then, download CWR from here: http://www.clockworkmod.com/rommanager and put the image in the same directory as fastboot.exe. And rename it something easy to type such as cwr.img
Next, reboot into the bootloader.
Open the command window from the fastboot.exe directory. (hold shift and right click then choose open command window here)
Type "fastboot devices" (no quotes) and make sure it returns the serial number. If it doesn't, the drivers aren't installed correctly.
Next type: fastboot flash recovery cwr.img
Then reboot into recovery and flash your custom rom and gapps per usual.

[Q] Recovery Mode

I get stucked showing an android laying on its back with the triangle thing on its tummy.
I have to randomly press my hardware buttons to get to CWM
is there anyway I can fix this that when I choose recovery mode it will go directly CWM?

That is the stock recovery. Not clockwork recovery.
I'm guessing you used the command "fastboot boot" instead of "fastboot flash" when trying to flash recovery.
Sent from my Nexus 7 using Tapatalk HD

El Daddy said:
That is the stock recovery. Not clockwork recovery.
I'm guessing you used the command "fastboot boot" instead of "fastboot flash" when trying to flash recovery.
Sent from my Nexus 7 using Tapatalk HD
Click to expand...
Click to collapse
I was able to flash the CWM already tho.
I'll just reflash the CWM.

This could be your problem too.
From efrant's N4 101 guide:
" I just flashed CWM, but every time I try to boot into CWM, I keep seeing the stock recovery. Why?
If you updated your Android build using an OTA update file (either manually or over-the-air), the update placed two files on your device that re-flash the stock recovery every time you reboot your device. These two files are:
/system/etc/install-recovery.sh <== this is the script that installs the patch file
/system/recovery-from-boot.p <== this is the patch
You have to rename (or delete) one or both of them, then re-flash your custom recovery. Now it will stick."
Sent from my Nexus 4 using xda premium

reflashed CWM. its still not sticking.
El Daddy said:
This could be your problem too.
From efrant's N4 101 guide:
" I just flashed CWM, but every time I try to boot into CWM, I keep seeing the stock recovery. Why?
If you updated your Android build using an OTA update file (either manually or over-the-air), the update placed two files on your device that re-flash the stock recovery every time you reboot your device. These two files are:
/system/etc/install-recovery.sh <== this is the script that installs the patch file
/system/recovery-from-boot.p <== this is the patch
You have to rename (or delete) one or both of them, then re-flash your custom recovery. Now it will stick."
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
okay I'll try this. but a got a quick question if I rename both of them (install-recovery.bak & recovery-from-boot.bak) will this possibly brick my device? or nothing major will be affected?

It won't brick your device.
Sent from my Nexus 4 using xda premium

El Daddy said:
It won't brick your device.
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
thanks man. got it working. it doesn't show the stock recovery anymore. (renamed both files).

[Q] [Softbricked[ Help! Accidentally flashed recovery image to boot partition...

Ok, so I unlocked my Nexus 7 (2013). Then I was trying to root it and after booting it into the bootloader, I typed:
"fastboot flash boot twrp.img" I was supposed to type "fastboot flash recovery twrp.img"
PLEASE HELP! My device boots into TWRP EXCLUSIVELY!
How do I get my os back? Is it gone? Can this be easily fixed?
I will be eternally in your debt if you can help me out, I feel so stupid, this is the first time I've bricked something and I've been unlocking, rooting, flashing android devices since my G1, then my Nexus One, which I even repartitioned the system partition so it could fit 4.2.2 Cm 10. I also unlocked, my touch pad and flashed cm dual booting with web os. Unlocking/rooting/flashingcustomrecovery on my Nexus 4 was a one click though so I guess I was rusty.
Edit: messed up a bracket in the title... Great...

I am not an expert, but I think you'll be fine flashing a ROM image as that will install the boot files. I'd get confirmation though.
But no crying!
Sent from my Nexus 7 using xda app-developers app

Coronado is dead said:
I am not an expert, but I think you'll be fine flashing a ROM image as that will install the boot files. I'd get confirmation though.
But no crying!
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
I don't have a rom image on my device though? How can I get one on there when I can only get into the bootloader or recovery...
Thanks for responding! I hope I can get this fixed...

In TWRP I think there is a way to mount USB and transfer it over. Maybe under advanced?
Sent from my Nexus 7 using xda app-developers app

Hmm maybe someone could make a .zip file to flash the boot loader in twrp

And there is always the option of getting the factory image from Google and using it over USB with fastboot on. Clean slate.
Sent from my Nexus 7 using xda app-developers app
---------- Post added at 12:54 AM ---------- Previous post was at 12:53 AM ----------
How to factory image restore:
http://www.androidpolice.com/2013/0...stock-using-a-full-factory-image-and-root-it/
Sent from my Nexus 7 using xda app-developers app

Flash any custom kernel, as it stands as "boot" partition.
Or just flash the boot image manually from the factory image:
Code:
fastboot flash boot boot.img
Then flash TWRP like normally you did before:
Code:
fastboot flash recovery recovery.img
Sent from my Galaxy S3 i9300

If you can go to bootloader or TWP, then you have many choices to fix your Nexus.
1. Download a factory image from Google, boot to bootloader and flash the whole thing. And remember to download the right factory image for Nexus 7(2013) (flo or razor). Check MD5 after downloading to make sure everything is OK. If you dont know how to flash a factory image, there is a couple topics in General and Q&A to assist you.
2. Or you can download a custom kernel in the Original Development area. THen boot to TWRP, use ADB to push the custom kernel file to your device, then install it by TWRP.
3. You can use a toolkit which I dont recommend.

Ok, so in my frantic attempts to fix this, I was trying to get adb sideload to work and was told to try and do a factory reset and wipe system and internal storage. I did this and still can't figure out how to get sideloading to work, I'm trying adb sideload rom.zip, and adb push rom.zip /sdcard which is what I read from another thread, but have not been able to get the factory image over.
Also, when I go to flash the .img that came with the factory image, fasboot says:
<code>sending 'boot' <2100 KB>....
OKAY [ 0.080s]
writing 'boot'...
FAILED <remote: image is not a boot image>
finished total time: 0.090s
</code>

OH GOD!
Download the Factory Image of Android 4.3 for ‘razor’ Nexus 7 tablet from here.
> this download contains the full system, bootloader, recovery and kernel boot img files.
Extract the ‘tgz’ factory image archive and place all contents into a single folder.
Next, you will need to edit a file so that your data will not be wiped. If you want to wipe data then you should skip this step.
> so, edit the ‘flash-all.bat’ for Windows or ‘flash-all.sh’ for Mac / Linux using a text editing tool:
- you will need to edit the ‘fastboot update’ command so that it will transform from ‘fastboot -w update image-razor-jss15j.zip’ into ‘fastboot update image-razor-jss15j.zip’. You will basically need to delete the ‘-w’ text, which is the command that tells fastboot to wipe data from your device.
- continue to the next step when you’re sure that the ‘-w’ text has been removed.
Now, power off your Nexus 7 2013 tablet.
Boot it into Bootloader Mode.
Connect it with your computer via USB cable.
Run the ‘flash-all’ script and wait for the factory image to be successfully installed.
Ok, so I did this, I downloaded the factory image, and ran the flash all command and that failed and now it's hard bricked! here is a screenshot of what the flash-all command output...
I will seriously pay someone to help me fix this at this point! I'm freaking out!
http://imgur.com/XsAJ4FV

mattj7 said:
Also, when I go to flash the .img that came with the factory image, fasboot says:
<code>sending 'boot' <2100 KB>....
OKAY [ 0.080s]
writing 'boot'...
FAILED <remote: image is not a boot image>
finished total time: 0.090s
</code>
Click to expand...
Click to collapse
You must have done something wrong. The boot.img that came with the factory restore is 6880KB not 2100KB.
Take things slow. You are still in a place where you can recover. If you make too many mistakes, you can make it even harder to recover.

Never mind, the problem had been solved.

sfhub said:
You must have done something wrong. The boot.img that came with the factory restore is 6880KB not 2100KB.
Take things slow. You are still in a place where you can recover. If you make too many mistakes, you can make it even harder to recover.
Click to expand...
Click to collapse
Yes, it was the factory image for the first nexus 7, I just ran the flash all on the right one and now I can boot just fine
WHEW
Ok guys, great job everyone!
Now I'm going to figure out if the custom recovery is still there, it probably isn't, and I can just flash it with fastboot now.

slamdunksaliby said:
Hmm maybe someone could make a .zip file to flash the boot loader in twrp
Click to expand...
Click to collapse
The only way is by the fastboot way, because it's an .img file
And don't forget that you can find all files that you need to this thread => [Index] REPO for all you need for your nexus 7 FLO (2013)

philos64 said:
The only way is by the fastboot way, because it's an .img file
]
Click to expand...
Click to collapse
Well, that is untrue. The bootloader .img is just a collection of other .img that get flashed to their respective partitions, such as aboot, sbl1, sbl2, sbl2b, sbl3, sbl3b, and rpm. :good:

Nburnes said:
Well, that is untrue. The bootloader .img is just a collection of other .img that get flashed to their respective partitions, such as aboot, sbl1, sbl2, sbl2b, sbl3, sbl3b, and rpm. :good:
Click to expand...
Click to collapse
Please I don't agree when you say it's untrue.
For most users, this is the easiest solution for this.
If you do a survey, I would like to see how many people know that you can flash by other means

philos64 said:
Please I don't agree when you say it's untrue.
For most users, this is the easiest solution for this.
If you do a survey, I would like to see how many people know that you can flash by other means
Click to expand...
Click to collapse
Well, I know you can flash by other means.
I don't think he said it was the easiest to flash from twrp. He just said it could be done, which it can.
I think far more people have done it through recovery than have known they have done it.
Everyone who flashes the JSS15J OTA will get the bootloader flashed in the way he described. If twrp is using the same kernel as stock recovery, then it can be done in twrp also.

philos64 said:
Please I don't agree when you say it's untrue.
For most users, this is the easiest solution for this.
If you do a survey, I would like to see how many people know that you can flash by other means
Click to expand...
Click to collapse
I'm not personally attacking you or anything and I am sorry if you took it that way.
I'm just stating that saying fastboot is the only way is not true. The partitions can easily be flashed through CWM/TWRP as they have been with, from my experience, Galaxy Nexus, Nexus 4, and Nexus 7 (2012).

sfhub said:
Well, I know you can flash by other means.
I don't think he said it was the easiest to flash from twrp. He just said it could be done, which it can.
I think far more people have done it through recovery than have known they have done it.
Everyone who flashes the JSS15J OTA will get the bootloader flashed in the way he described. If twrp is using the same kernel as stock recovery, then it can be done in twrp also.
Click to expand...
Click to collapse
Nburnes said:
I'm not personally attacking you or anything and I am sorry if you took it that way.
I'm just stating that saying fastboot is the only way is not true. The partitions can easily be flashed through CWM/TWRP as they have been with, from my experience, Galaxy Nexus, Nexus 4, and Nexus 7 (2012).
Click to expand...
Click to collapse
No problem
But as I said, almost users don't flashed by the way of the partitions.
It would be better to say the easiest way
Sent from my HTC One using Tapatalk 4 between sky and earth

Nexus 7 2012 trwp and cwp and side load android 4.4 zip flash error

Hello xda, I unfortunately have an issue with flashing the android 4.4 factory zip. I know there are many different problems including the "status 7" issue which is ticking of some people. But I have a different error,
no md5 file found..
verifying current system..
"/system/app/Currents.apk" has unexpected contents.
E: Error executing updater binary in zip...
Can someone please explain this error and the solution for me? I have tried everything I could find, I'm rooted with trwp and I even tried cwp and adb side load to flash the android 4.4 factory zip but the same error always appears.
Someone help me.
I must of deleted Google currents by accident. And I couldn't even flash the android 4.3 factory zip without getting the same error.
Sent from my Nexus 7 using XDA Premium HD app

Please help guys
Sent from my Nexus 7 using XDA Premium HD app

the same as me
GoldenNexus7 said:
Please help guys
Sent from my Nexus 7 using XDA Premium HD app
Click to expand...
Click to collapse
I also receive update via OTA but it still error, so i try adb sideload but the error is
Code:
"/system/app/Currents.apk" has unexpected cotents
Error (status 7)
Installation aborted

Use a file manager to check to see if you have the Currents.apk in the /system/app directory, if it is missing just copy the attached one to /system/ap and change the permissions to rw-r-r to match the other files. The attached Currents.apk is from the JWR66V file system.

GMPOWER said:
Use a file manager to check to see if you have the Currents.apk in the /system/app directory, if it is missing just copy the attached one to /system/ap and change the permissions to rw-r-r to match the other files. The attached Currents.apk is from the JWR66V file system.
Click to expand...
Click to collapse
Not sure how to change permissions but I'll try that thanks.
Sent from my Nexus 7 using XDA Premium HD app

GMPOWER said:
Use a file manager to check to see if you have the Currents.apk in the /system/app directory, if it is missing just copy the attached one to /system/ap and change the permissions to rw-r-r to match the other files. The attached Currents.apk is from the JWR66V file system.
Click to expand...
Click to collapse
That worked well but then when I tied to flash it again in both twrp and cwm recovery it gives a new error,
"/System/bin/app-process" has unexpeted contents
E:error in /tmp/update.zip
PLEASE HELP ME ON THIS,SOMEONE SAID THIS MIGHT HAVE SOMETHING TO DO WITH XPOSED AND I SHOULD DELETE FRAMEWORK FIRST. not sure what he meant by remove framework.
Sent from my Nexus 7 using XDA Premium HD app

GoldenNexus7 said:
That worked well but then when I tied to flash it again in both twrp and cwm recovery it gives a new error,
"/System/bin/app-process" has unexpeted contents
E:error in /tmp/update.zip
PLEASE HELP ME ON THIS,SOMEONE SAID THIS MIGHT HAVE SOMETHING TO DO WITH XPOSED AND I SHOULD DELETE FRAMEWORK FIRST. not sure what he meant by remove framework.
Sent from my Nexus 7 using XDA Premium HD app
Click to expand...
Click to collapse
For permissions, if using ES File Explorer, long press on the app, press “more” in the bottom right corner, select “Properties,” then press the change box that is next to permissions. If you are using Root Explorer, long press on the file, and then select “Permissions.”
If you continue to receive errors, I recommend downloading the following stock JWR66V ROM, HERE. You can then pick out each file that you need, or you can just dirty flash it to restore all the needed files.
Attached is that file, you just need to unzip the file, and then change the permission on the file too rwxr-xr-x.

GMPOWER said:
For permissions, if using ES File Explorer, long press on the app, press “more” in the bottom right corner, select “Properties,” then press the change box that is next to permissions. If you are using Root Explorer, long press on the file, and then select “Permissions.”
If you continue to receive errors, I recommend downloading the following stock JWR66V ROM, HERE. You can then pick out each file that you need, or you can just dirty flash it to restore all the needed files.
Attached is that file, you just need to unzip the file, and then change the permission on the file too rwxr-xr-x.
Click to expand...
Click to collapse
Alright, thank you , I'll try to flash the ROM but if the same error appears again when I flash it I'll let you know.
Sent from my Nexus 7 using XDA Premium HD app

I have similiar issue on 2012 3g, stock, locked, no root, stock recovery. Did a side load, but during system verification i got "/system/media/bootanimation.zip" has unexpected contents. Error in /sdcard/0/ update.zip. (Status 7)". I'm on jrw66y tried to reflash, successfuly, tried 4.4 ota again, same error. I recived two OTA's for 4.3 and had no issues. I can understand errors for apks, but for a stock bootanimation i just can't... Does someone have a idea what next? Thanks in advance.
Востани Сербие, востани царице

GMPOWER said:
For permissions, if using ES File Explorer, long press on the app, press “more” in the bottom right corner, select “Properties,” then press the change box that is next to permissions. If you are using Root Explorer, long press on the file, and then select “Permissions.”
If you continue to receive errors, I recommend downloading the following stock JWR66V ROM, HERE. You can then pick out each file that you need, or you can just dirty flash it to restore all the needed files.
Attached is that file, you just need to unzip the file, and then change the permission on the file too rwxr-xr-x.
Click to expand...
Click to collapse
OK I reinstalled the old android 4.3 factory zip and then updated to the second 4.3 update and then the 4.4 , when I update I'm quarter way, it said error, boot animation has unexpected contents, I need the old boot animation back because when I turn on my nexus it doesn't have the traditional "x" boot animation anymore. I guess this new boot animation is from the JWR66V factory zip for rooted devices you gave me from before. Can you please give me the old boot animation file, I hope this is the only error I'm gonna get.
Sent from my Nexus 7 using XDA Premium HD app

Now You have same issue as i do. I tried to dig it from several roms but in vain - couldn't find appropriate. Next question is if i get that file, can i put it to /system/media w/o root. I think i can't. Anyway @GoldenNexus7, if You aquire that bootanimation pls notice me, I'll notice You if I get it first.
Востани Сербие, востани царице

I had the same problem and I solved it flashing system.img an boot.img from factory image. I don't remember the post so I'ill explain you. (For this method you have been bootloader unlocked)
1. Download Factory Image from Google site.
2. Unzip the .tgz file.
3. Unzip the .zip file in.
4. Copy system.img and boot.img to the location of fastboot (i. e. in SDK platform tools).
5. Open CMD in that location (shiftRightClick> Open Command Prompt Here).
6. Write this commands:
fastboot flash system system.img
fastboot flash boot boot.img
Note: Userdata partition factory reset your tablet. Don't flash it!
And that's all. Your Nexus 7 has been updated.
Enviado desde mi Galaxy Nexus mediante Tapatalk

slif24 said:
I had the same problem and I solved it flashing system.img an boot.img from factory image. I don't remember the post so I'ill explain you. (For this method you have been bootloader unlocked)
1. Download Factory Image from Google site.
2. Unzip the .tgz file.
3. Unzip the .zip file in.
4. Copy system.img and boot.img to the location of fastboot (i. e. in SDK platform tools).
5. Open CMD in that location (shiftRightClick> Open Command Prompt Here).
6. Write this commands:
fastboot flash system system.img
fastboot flash boot boot.img
Note: Userdata partition factory reset your tablet. Don't flash it!
And that's all. Your Nexus 7 has been updated.
Enviado desde mi Galaxy Nexus mediante Tapatalk
Click to expand...
Click to collapse
Will the flashing system.img and boot.img wipe the data?

Unlocking bootloader wipes data. Flashing system and boot won't . But, sometimes device won't boot if data is not wiped. Now, as i wage lurking around for a solution or rooting and wipe data, I'm much closer to 2nd solution.
Востани Сербие, востани царице

slif24 said:
I had the same problem and I solved it flashing system.img an boot.img from factory image. I don't remember the post so I'ill explain you. (For this method you have been bootloader unlocked)
1. Download Factory Image from Google site.
2. Unzip the .tgz file.
3. Unzip the .zip file in.
4. Copy system.img and boot.img to the location of fastboot (i. e. in SDK platform tools).
5. Open CMD in that location (shiftRightClick> Open Command Prompt Here).
6. Write this commands:
fastboot flash system system.img
fastboot flash boot boot.img
Note: Userdata partition factory reset your tablet. Don't flash it!
And that's all. Your Nexus 7 has been updated.
Enviado desde mi Galaxy Nexus mediante Tapatalk
Click to expand...
Click to collapse
I installed the OTA and I don't know what happened, I got stuck on the Kitkat logo screen (boot animation). I am unlocked and have CWM installed. Now I can't get past that screen. I can access adb and also CWM recovery.
I am also planning to try this method now. Is it okay if I have CWM Recovery installed? Do I have to remove it in order for this to work?

Loreane Van Daal said:
Now You have same issue as i do. I tried to dig it from several roms but in vain - couldn't find appropriate. Next question is if i get that file, can i put it to /system/media w/o root. I think i can't. Anyway @GoldenNexus7, if You aquire that bootanimation pls notice me, I'll notice You if I get it first.
Востани Сербие, востани царице
Click to expand...
Click to collapse
Not sure if it would make a big difference, it will probably give me a different error once I try to update to 4.4 again.
SIGH
Sent from my Nexus 7 using XDA Premium HD app

slif24 said:
I had the same problem and I solved it flashing system.img an boot.img from factory image. I don't remember the post so I'ill explain you. (For this method you have been bootloader unlocked)
1. Download Factory Image from Google site.
2. Unzip the .tgz file.
3. Unzip the .zip file in.
4. Copy system.img and boot.img to the location of fastboot (i. e. in SDK platform tools).
5. Open CMD in that location (shiftRightClick> Open Command Prompt Here).
6. Write this commands:
fastboot flash system system.img
fastboot flash boot boot.img
Note: Userdata partition factory reset your tablet. Don't flash it!
And that's all. Your Nexus 7 has been updated.
Enviado desde mi Galaxy Nexus mediante Tapatalk
Click to expand...
Click to collapse
Which factory image should I download? Is it the kit Kat one?
Sent from my Nexus 7 using XDA Premium HD app

alfred_heaven said:
Will the flashing system.img and boot.img wipe the data?
Click to expand...
Click to collapse
No. "userdata.img" wipes your data. I had that fear, but no problem.
hardikrajgor123 said:
I installed the OTA and I don't know what happened, I got stuck on the Kitkat logo screen (boot animation). I am unlocked and have CWM installed. Now I can't get past that screen. I can access adb and also CWM recovery.
I am also planning to try this method now. Is it okay if I have CWM Recovery installed? Do I have to remove it in order for this to work?
Click to expand...
Click to collapse
The Factory Image include 4 files: boot.img, system.img, userdata.img (this wipes your data) and recovery.img (if you use a Custom Recovery, you don't have to flash this, if you don't, you must to flash it. In addition, your recovery isn't important. You only have to reboot your device in bootloader mode (Turn on pressing Power+VolUp+VolDown) and connect it to your PC. Finally you have tu follow the steps. Simply and clear. Your device has been updated.
GoldenNexus7 said:
Which factory image should I download? Is it the kit Kat one?
Sent from my Nexus 7 using XDA Premium HD app
Click to expand...
Click to collapse
You must to download KitKat image.
nakasi (Wi-Fi): https : // dl. google. com /dl/android/aosp/nakasi-krt16s-factory-da7dee49.tgz
nakasig (3G): https : // dl. google. com /dl/android/aosp/nakasig-krt16s-factory-1e882585.tgz
Erase spaces. I can't publish links.
Hope this help you

slif24 said:
No. "userdata.img" wipes your data. I had that fear, but no problem.
The Factory Image include 4 files: boot.img, system.img, userdata.img (this wipes your data) and recovery.img (if you use a Custom Recovery, you don't have to flash this, if you don't, you must to flash it. In addition, your recovery isn't important. You only have to reboot your device in bootloader mode (Turn on pressing Power+VolUp+VolDown) and connect it to your PC. Finally you have tu follow the steps. Simply and clear. Your device has been updated.
You must to download KitKat image.
nakasi (Wi-Fi): https : // dl. google. com /dl/android/aosp/nakasi-krt16s-factory-da7dee49.tgz
nakasig (3G): https : // dl. google. com /dl/android/aosp/nakasig-krt16s-factory-1e882585.tgz
Erase spaces. I can't publish links.
Hope this help you
Click to expand...
Click to collapse
For some reason I lost root, but my nexus 7 is still unlocked so I can root again using root tool kit.
Sent from my Nexus 7 using XDA Premium HD app

GoldenNexus7 said:
For some reason I lost root, but my nexus 7 is still unlocked so I can root again using root tool kit.
Sent from my Nexus 7 using XDA Premium HD app
Click to expand...
Click to collapse
I have the same problem. I've tried to flash it from Custom Recovery (TWRP) and no root. I'm investigating that. I post if I found a solution. Recovery maybe the guilty.
Enviado desde mi Galaxy Nexus mediante Tapatalk

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...