Database Users

Stock Recovery

I flashed TWRP to make backups and am finding I want to revert to stock recovery for whenever the next OTA is pushed. I'm on stock 4.2.2. Is there a repository to flash the stock recovery specific to the version of android I'm on or other way to backup/re-flash stock android prior to installing custom recovery?

ravenofdoom said:
I flashed TWRP to make backups and am finding I want to revert to stock recovery for whenever the next OTA is pushed. I'm on stock 4.2.2. Is there a repository to flash the stock recovery specific to the version of android I'm on or other way to backup/re-flash stock android prior to installing custom recovery?
Click to expand...
Click to collapse
The stock Android recovery cannot make entire system (NANDROID) backups like TWRP or CWMR can. If your looking to re-install stock Android 4.2.2 for the Nexus 10 you can download and flash the Nexus 10 factory image from here (I would recommend taking a look at this great guide if your are unfamiliar with how to flash factory images). If you just want to reflash the Nexus 10 stock recovery you can download it from here, boot into fastboot mode and then flash it with the following command:
Code:
fastboot flash recovery path/to/recovery-stock-manta.img
After it completes you can reboot into recovery mode and you should now have the stock Nexus 10 recovery image installed. For flashing the stock recovery you should try and match it to the Android version so if your on Android 4.2.2 try and flash the recovery.img that was pulled from the Android 4.2.2 factory image. However usually you can get away with flashing 4.2 or 4.2.1 version of the stock recovery.img as it is unlikely that anything major changed with the stock recovery image in those small incremental Android updates.

Is there a repo or other way to make a backup of stock recovery before flashing custom (TWRP/CWMR). If I'm on the go and want to interchange between custom recovery and previous stock recovery without the aid of a computer nearby, how would I do that? Is there an app that can save/snapshot my current stock recovery before flashing custom recovery (and then can later let me re-flash that saved recovery)?

Flashing stock recovery wont make me lose any data will it? because 4.3 was released for s4 google edition so im sure nexus 10 is close and i want to be ready.

abdel12345 said:
Flashing stock recovery wont make me lose any data will it? because 4.3 was released for s4 google edition so im sure nexus 10 is close and i want to be ready.
Click to expand...
Click to collapse
Correct flashing stock recovery won't make you loose any data. But as always when your flashing anything and if you have even the slightest hesitation backup any data you wouldn't want to loose.
Sent from my SCH-I535 using xda premium

Alright thanks man. I already used my 8 for today but ill thank you tomorrow and ill back up my apps with titanium backup

OK what is the command to use to flash because the one from the previous page didn't work it said something about not finding it or something are there any drivers that need to be installed or something I'm missing? I connected it to my CPU and turned it on while holding power and volume and it went menu where you see tablet info? Any help please
Sent from my Xperia Play (r800x)

ravenofdoom said:
Is there a repo or other way to make a backup of stock recovery before flashing custom (TWRP/CWMR). If I'm on the go and want to interchange between custom recovery and previous stock recovery without the aid of a computer nearby, how would I do that? Is there an app that can save/snapshot my current stock recovery before flashing custom recovery (and then can later let me re-flash that saved recovery)?
Click to expand...
Click to collapse
Don't know if you still need this info, but you can use flash_image to flash recoveries without having to connect to a PC. So if you save the recovery image files, you can switch easily. Have a look here:
http://theunlockr.com/2009/10/15/how-to-flash-a-new-recovery-image-if-you-are-already-rooted/
I haven't done this on my N10, but I've used the method several times on my HTC Vivid phone.
Sent from my Nexus 10 using Tapatalk HD

bruce7373 said:
Don't know if you still need this info, but you can use flash_image to flash recoveries without having to connect to a PC. So if you save the recovery image files, you can switch easily. Have a look here:
http://theunlockr.com/2009/10/15/how-to-flash-a-new-recovery-image-if-you-are-already-rooted/
I haven't done this on my N10, but I've used the method several times on my HTC Vivid phone.
Sent from my Nexus 10 using Tapatalk HD
Click to expand...
Click to collapse
That actually helped me out with my problem thanks because I couldn't get it to flash from cpu
Sent from my Xperia Play (r800x)

abdel12345 said:
That actually helped me out with my problem thanks because I couldn't get it to flash from cpu
Sent from my Xperia Play (r800x)
Click to expand...
Click to collapse
Cool. :thumbup:
Sent from my Nexus 10 using Tapatalk HD

@bruce7373 it didnt work it just tells me flash_image not found when i put in the command and i checked and its there on the sd card

abdel12345 said:
@bruce7373 it didnt work it just tells me flash_image not found when i put in the command and i checked and its there on the sd card
Click to expand...
Click to collapse
The IMG file is not found or flash_image itself isn't there? If you don't have flash_image, you can download it (I think there's a link on that page I referenced, or just Google it). If the former, you need to first navigate to the folder flash_image is in (/system/bin with the ROM I have on my N10), then run the command, making sure the IMG file is in the root of /sdcard.
Sent from my Nexus 10 using Tapatalk HD

bruce7373 said:
The IMG file is not found or flash_image itself isn't there? If you don't have flash_image, you can download it (I think there's a link on that page I referenced, or just Google it). If the former, you need to first navigate to the folder flash_image is in (/system/bin with the ROM I have on my N10), then run the command, making sure the IMG file is in the root of /sdcard.
Sent from my Nexus 10 using Tapatalk HD
Click to expand...
Click to collapse
OK I'll try yhat
Sent from my Xperia Play (r800x)

[Q] [HELP] Missing recovery 4.3

I was running TWRP with the franco kernel and stock rom on my nexus 4 4.2.2. When I got my OTA update notification, I did the needful and reverted back to stock rom and un rooted the phone using wugs root kit. Like wise the update was successful and I went about restoring all the backup's i created using wugs root kit 1.6.4.
Now the issue is after all this when I went about rooting the thus phone, I faced horrors for which I couldn't find exact answers on this forum. I want to flash TWRP 2.6 and to do that I went into fastboot and tried to flash it, but i keep getting an error saying "cannot load recovery.img: No error. And when I do try into get into the stock recovery then I get an image of fallen droid with a red exclamation mark and a message saying "No Command". Can anyone tell me what is the issue and how can i fix/workaround it..
Thank You:good:
EDIT: when I get the no command "fallen android" when i select recovery from the bootloader on pressing power+vol up does give me acces to the stock recovery. But even on using wug's 1.6.6 root kit I'm unable to root the device and install a custom recovery

Vikas Rao said:
I was running TWRP with the franco kernel and stock rom on my nexus 4 4.2.2. When I got my OTA update notification, I did the needful and reverted back to stock rom and un rooted the phone using wugs root kit. Like wise the update was successful and I went about restoring all the backup's i created using wugs root kit 1.6.4.
Now the issue is after all this when I went about rooting the thus phone, I faced horrors for which I couldn't find exact answers on this forum. I want to flash TWRP 2.6 and to do that I went into fastboot and tried to flash it, but i keep getting an error saying "cannot load recovery.img: No error. And when I do try into get into the stock recovery then I get an image of fallen droid with a red exclamation mark and a message saying "No Command". Can anyone tell me what is the issue and how can i fix/workaround it..
Thank You:good:
Click to expand...
Click to collapse
Have you tried redownloading twrp seems like a bad download?

yamani.m said:
Have you tried redownloading twrp seems like a bad download?
Click to expand...
Click to collapse
Tried Twrp, CWM and stock recovery too!! No luck, Still can't access recovery!
PS I tried to flash recovery buy using wug nrt which has not still been updated for JB 4.3 to begin with that is, later used fastboot

Vikas Rao said:
Tried Twrp, CWM and stock recovery too!! No luck, Still can't access recovery!
PS I tried to flash recovery buy using wug nrt which has not still been updated for JB 4.3 to begin with that is, later used fastboot
Click to expand...
Click to collapse
I would try to flash the full stock google image with fastboot and see what happens ?

Using fastboot to flash the recovery definitely works as I've done it, just have to make sure you use the right command:
fastboot flash recovery recovery.img
Make sure you're using the correct filename of the recovery image you have, I prefer to rename mine recovery.img so I can't get it wrong. Also make sure you're not putting recovery.img.img - sounds silly but people do do it!

EddyOS said:
Using fastboot to flash the recovery definitely works as I've done it, just have to make sure you use the right command:
fastboot flash recovery recovery.img
Make sure you're using the correct filename of the recovery image you have, I prefer to rename mine recovery.img so I can't get it wrong. Also make sure you're not putting recovery.img.img - sounds silly but people do do it!
Click to expand...
Click to collapse
I also did it this morning, works fine

EddyOS said:
Using fastboot to flash the recovery definitely works as I've done it, just have to make sure you use the right command:
fastboot flash recovery recovery.img
Make sure you're using the correct filename of the recovery image you have, I prefer to rename mine recovery.img so I can't get it wrong. Also make sure you're not putting recovery.img.img - sounds silly but people do do it!
Click to expand...
Click to collapse
Nope did the same thing! gives me the cannot load error, I just copy pasted the filename so can't go wrong there. And a stock rom flash is an option but the thing is i don't have a custom recovery nor root access for titanium backup don't wanna spend time again personalizing. I'm sure there is a simpler way.

Please Recovery Stock LG G PAD 7 LTE v410

Hi I'm looking for the recovery of the stock LG G PAD tablet 7 "LTE I am root backup with TWRP but I can not go back to Recovery Stock.
Before flashing the TWRP I forgot to make a backup of Recovery
Sorry for my bad English.
thanks

exebuera said:
Hi I'm looking for the recovery of the stock LG G PAD tablet 7 "LTE I am root backup with TWRP but I can not go back to Recovery Stock.
Before flashing the TWRP I forgot to make a back of Recovery
Sorry for my bad English.
thanks
Click to expand...
Click to collapse
here's a link to an image I made before flashing twrp on my v410. I've restored it with dd and flashify and it works fine. https://docs.google.com/file/d/0B1l3W9XHAqEgX0ZCUWc1QTlfWjg/edit?usp=docslist_api

jason2678 said:
here's a link to an image I made before flashing twrp on my v410. I've restored it with dd and flashify and it works fine. https://docs.google.com/file/d/0B1l3W9XHAqEgX0ZCUWc1QTlfWjg/edit?usp=docslist_api
Click to expand...
Click to collapse
hey @jason2678 thanks, but how did i flash this if i dont have twrp installed? can i use fastboot or adb?

dreamtheater17 said:
hey @jason2678 thanks, but how did i flash this if i dont have twrp installed? can i use fastboot or adb?
Click to expand...
Click to collapse
I'd recommend flashify to flash recovery images. You can download it from the play store. So easy to make a typo and mess things up with adb and dd.
You could do it with a terminal or adb shell. Say you store the image in /sdcard
Code:
su
dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p14
Verify mmcblk0p14 is recovery before you try this. I'm pretty sure that's right, but I don't have my tablet right now and you can make a serious mess of your device this way if you overwrite the wrong partition. Check it by listing your partitions with this:
Code:
su
ls -al /dev/block/platform/*/by-name
By default this little tablet does not have fastboot, but you can enable it with this method. I've zeroed out my laf partition and verified I can boot into fastboot mode, but I've never actually used it to flash anything. It just seemed like a good idea to have fastboot available to fall back on rather than LG download mode since there was no kdz available for the V410 for a long time.

jason2678 said:
I'd recommend flashify to flash recovery images. You can download it from the play store. So easy to make a typo and mess things up with adb and dd.
You could do it with a terminal or adb shell. Say you store the image in /sdcard
Code:
su
dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p14
Verify mmcblk0p14 is recovery before you try this. I'm pretty sure that's right, but I don't have my tablet right now and you can make a serious mess of your device this way if you overwrite the wrong partition. Check it by listing your partitions with this:
Code:
su
ls -al /dev/block/platform/*/by-name
By default this little tablet does not have fastboot, but you can enable it with this method. I've zeroed out my laf partition and verified I can boot into fastboot mode, but I've never actually used it to flash anything. It just seemed like a good idea to have fastboot available to fall back on rather than LG download mode since there was no kdz available for the V410 for a long time.
Click to expand...
Click to collapse
Thank you! the thing is i bricked my g pad, i really dont know much about the tab because the lack of support it has. I was using it with cm12.1 and i use a stock recovery founded in Android central to revert back to stock, but in TWRP i flashed the img as recovery and also as boot, so the g pad entered in a bootloop were only enters in stock recovery, my Windows 10 laptop doesn't recognize the tab when in adb sideload, and doesn't know much about adb Shell, i'm following the comandas you wrote but i'm always getting error: closed.
i know how to get back to stock using the kdz, but using the kdz will make the partition issue and will have to folllow a looong looong process.
If you could give me a hand with this i would really apprecciate it

Sorry I've never encountered the adb closed problem myself, but I have heard about it before. Some people have reported the following series of commands fixes it:
Code:
adb usb
adb devices
adb kill-server
adb start-server
The first two commands normally don't really do anything and its pretty obvious what the second two do, but some people have reported success doing this.
Some people have reported the closed error was fixed by updating their adb binary. If you're using the android-sdk update platform-tools, or if you're using a standalone adb consider looking for an update for it.
Good luck. That procedure to get things back to normal following using the kdz to restore sounds messy.

dreamtheater17 said:
Thank you! the thing is i bricked my g pad, i really dont know much about the tab because the lack of support it has. I was using it with cm12.1 and i use a stock recovery founded in Android central to revert back to stock, but in TWRP i flashed the img as recovery and also as boot, so the g pad entered in a bootloop were only enters in stock recovery, my Windows 10 laptop doesn't recognize the tab when in adb sideload, and doesn't know much about adb Shell, i'm following the comandas you wrote but i'm always getting error: closed.
i know how to get back to stock using the kdz, but using the kdz will make the partition issue and will have to folllow a looong looong process.
If you could give me a hand with this i would really apprecciate it
Click to expand...
Click to collapse
hi, i have the same problem than u, i wanna know if i can flash the US CELLULAR kdz for solve the partition issue? because i already flash the kdz test from ATT

jason2678 said:
here's a link to an image I made before flashing twrp on my v410. I've restored it with dd and flashify and it works fine. https://docs.google.com/file/d/0B1l3W9XHAqEgX0ZCUWc1QTlfWjg/edit?usp=docslist_api
Click to expand...
Click to collapse
I flashed stock rooted 4.4.2, and I want to OTA to Stock Lollipop, but it says there is no update. Any ideas of how I can get back to fully stock? Would flashing this stock recovery make it work? Is being rooted blocking the OTA update from seeing an available update?

mxpxboi said:
I flashed stock rooted 4.4.2, and I want to OTA to Stock Lollipop, but it says there is no update. Any ideas of how I can get back to fully stock? Would flashing this stock recovery make it work? Is being rooted blocking the OTA update from seeing an available update?
Click to expand...
Click to collapse
If you applied an OTA with a custom recovery installed it might soft brick your tablet, but I don't see why that would stop it from detecting and downloading the update. It is always safest to flash stock recovery, fully unroot, and undo any modifications you've made to /system before taking an OTA, but some devices are more picky than others. With what you're describing I'm afraid that even if you do unroot and flash stock recovery your tablet still won't find the OTA.
Do you have a nandroid backup of an unmodified stock ROM you could restore?
And just so you know that lollipop bootloader is not vulnerable to the bump exploit, so no custom recovery or ROMs if you get it to apply.

Whenever I type "reboot recovery" in terminal emulator, it boots straight to factory reset. I have tried this multiple times with both dd and flashify. Do you know what causes this? I'm downloading the OTA right now, I hope it doesn't wipe then too...

please help
i was a dumbass and accidently flashed my boot instead of recovery do you by chance have a boot.img that i can use to reflash my boot.img please help as im really stuck..thanks in advance

Devil911 said:
i was a dumbass and accidently flashed my boot instead of recovery do you by chance have a boot.img that i can use to reflash my boot.img please help as im really stuck..thanks in advance
Click to expand...
Click to collapse
Download the timmytim stock ROM, and extract the boot.img from it. There are probably quicker ways, but having the stock ROM on hand is a good idea.
Sent from my Amazon Fire using XDA Labs

Thank you...
I resolved my issue i had forgotten in my haste i posted the same question in two different sections. However after fixing everything my tablet was broke not the out glass but the inner display. I cant afford another one or a replacement part to even fix mine. So unless i can find one someone who bricked theirs completely or get a handme down im tabless for awhile.... Thank you though for the reply. The original boot file wouldnt work properly i had to use the boot file from the stock rooted rom and not the timmytim deoxedized rom.. i dont know why unless the bootfile is specific to each rom. Maybe i did something wromg during the flash. But i had gotten it fixed nevertheless.

Devil911 said:
I resolved my issue i had forgotten in my haste i posted the same question in two different sections. However after fixing everything my tablet was broke not the out glass but the inner display. I cant afford another one or a replacement part to even fix mine. So unless i can find one someone who bricked theirs completely or get a handme down im tabless for awhile.... Thank you though for the reply. The original boot file wouldnt work properly i had to use the boot file from the stock rooted rom and not the timmytim deoxedized rom.. i dont know why unless the bootfile is specific to each rom. Maybe i did something wromg during the flash. But i had gotten it fixed nevertheless.
Click to expand...
Click to collapse
The stock rooted is by timmytim ?
I forgot about deodexed, actually.
Glad you fixed boot, shame your tablet broke ?
Sent from my Amazon Fire using XDA Labs

[Guide] Flash OTAs with TWRP (OS 2.1.3/ 005)

Firstly, you cannot install OTA's with TWRP. You'll have to get back to stock recovery in order to install patches.
Thanks to @eng.stk, with the recovery compiled from source, we now can flash OTA Zips from TWRP.
Download TWRP 2.8.7.0: http://forum.xda-developers.com/devdb/project/dl/?id=15364
Download the following OTA's and move them to internal/external storage and proceed to install them from TWRP.
OxygenOS_X_Rom.zip (003)
OTA Patch 003-004.zip
OTA Patch 004-005.zip (Uploaded by @Razertje)
____
Stock Recovery (Just in case if someone requires it)
- Stock_Recovery.img

I got an error when I try to flash it

PoloB49 said:
I got an error when I try to flash it
Click to expand...
Click to collapse
Are you rooted? Did you flash TWRP recovery?

PoloB49 said:
I got an error when I try to flash it
Click to expand...
Click to collapse
It's most likely that you tampered the system and recovery partition. I uploaded the stock recovery here, flash the stock recovery, then flash to system dump, then this patch.

Well, i did a nandroid backup before getting rooted, i tried to restore my phone so i could properly do the ota, but now there is no OS installed
But my computer still detect my phone, where can i download the full rom please ?

PoloB49 said:
Well, i did a nandroid backup before getting rooted, i tried to restore my phone so i could properly do the ota, but now there is no OS installed
But my computer still detect my phone, where can i download the full rom please ?
Click to expand...
Click to collapse
It's at the front page. http://forum.xda-developers.com/oneplus-x/general/ota003all20151024193-oxygenos-ota-dump-t3244996

SpiritBreak3r said:
It's at the front page. http://forum.xda-developers.com/oneplus-x/general/ota003all20151024193-oxygenos-ota-dump-t3244996
Click to expand...
Click to collapse
Thanks, i wasn't sure it was the full rom because of the "ota" in the name.

SpiritBreak3r said:
It's most likely that you tampered the system and recovery partition. I uploaded the stock recovery here, flash the stock recovery, then flash to system dump, then this patch.
Click to expand...
Click to collapse
hey i did as you said to try and get the update but i have a question. what does flash to system dump mean?
Already flashed stock recovery. next step?

Savya said:
hey i did as you said to try and get the update but i have a question. what does flash to system dump mean?
Already flashed stock recovery. next step?
Click to expand...
Click to collapse
By flashing the system dump I meant, install this zip package http://forum.xda-developers.com/oneplus-x/general/ota003all20151024193-oxygenos-ota-dump-t3244996. This zip package is stock system dump bearing version 03. Then flash to 03-04 patch.

is this OTA solved the problem with microsd cards?

Can anybody help with a generic error trying to flash the stock recovery again?
No reason why just says failed. I am rooted with TWRP and trying to revert to stock to be able to OTA. Last android was a nexus 4 and been away a little while so I may be missing something.. I don't want to have to wipe all my data and such can somebody assist and refresh my understanding?

Dizzyrul3z: No, microSD card issue remains according to official forum--next OTA I bet.
I'm rooted, TWRP also errored when I attempted the OTA installed.
So to clarify, using TWRP I want to install three zips: stock rom, OTA03 (system dump), and OTA04 (update), wipe cache/dalvik. Correct?
Question: I install them all at once in TWRP, right? Will any of this erase my apps/data?
Thanks,

Dizzyrul3z said:
is this OTA solved the problem with microsd cards?
Click to expand...
Click to collapse
I don't know about you guys, but I have the E-1003 model, SD card is working fine. I have a Samsung EVO+ 32GB card.
BakedGoodsX said:
Dizzyrul3z: No, microSD card issue remains according to official forum--next OTA I bet.
I'm rooted, TWRP also errored when I attempted the OTA installed.
So to clarify, using TWRP I want to install three zips: stock rom, OTA03 (system dump), and OTA04 (update), wipe cache/dalvik. Correct?
Question: I install them all at once in TWRP, right? Will any of this erase my apps/data?
Thanks,
Click to expand...
Click to collapse
You need to flash to Stock recovery as well. I'll be updating the OP.

So this update is newer than the one mentioned here right ? : https://forums.oneplus.net/threads/oxygenos-2-1-2-will-start-roll-out-to-oneplus-x-today.402637/
Thanks

SpiritBreak3r said:
Just received this OTA mins ago.
Size: 17MB
https://drive.google.com/file/d/0B3AIip-hiOnNb1pBeGNlcUIyYmc/view?usp=sharing
Instructions:
1. Switch to Stock Recovery if you're running TWRP. But how to do it? Restore this backup from TWRP.
2. Flash the system dump available at this thread.
3. Now flash this update/patch.
4. Then fastboot flash TWRP recovery if you only need it.
Just my 2 cents, boot TWRP instead of flashing it. I personally suggest.
Code:
fastboot boot twrp_directory_of_your_pc.img
PSA: You'll need Stock recovery to patch official updates.
PS: My Memory Card is working exceptionally fine. I am using a Samsung EVO+ 32GB.
Click to expand...
Click to collapse
I can't restore the stock recovery.
in TWRP:
error flashing zip '/sdcard/*/oneplusx_x_stock_recovery.zip'
I also copied the zip into the TWRP backup folder, but can't select it to restore.
TWRP ist v.2.8.7.0
What am I doing wrong?
...rebooting the device from TWRP is also not working, anybody with the same problem?

umpalumpa1799 said:
I can't restore the stock recovery.
in TWRP:
error flashing zip '/sdcard/*/oneplusx_x_stock_recovery.zip'
I also copied the zip into the TWRP backup folder, but can't select it to restore.
TWRP ist v.2.8.7.0
What am I doing wrong?
...rebooting the device from TWRP is also not working, anybody with the same problem?
Click to expand...
Click to collapse
Extract the recovery.img from the zip file and flash it from fastboot:
Code:
fastboot flash recovery recovery.img

CafeKampuchia said:
Extract the recovery.img from the zip file and flash it from fastboot:
Code:
fastboot flash recovery recovery.img
Click to expand...
Click to collapse
so rename the recovery.emmc.win from the zip file to recovery.img and flash it with fastboot.

umpalumpa1799 said:
so rename the recovery.emmc.win from the zip file to recovery.img and flash it with fastboot.
Click to expand...
Click to collapse
even better, download the img from the op.

SpiritBreak3r said:
even better, download the img from the op.
Click to expand...
Click to collapse
my fault, I downloaded the stock recovery from a nother post

Thank you for the update OP.
To clarify, when you say '...stick with stock recovery, disable the apps instead of deleting them...' what exactly does that mean?

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