Unlocked Bootloader.
CWM.
Root.
Fail in updating, with message something like assert fail apply_update_check status 7.
Revert to Stock Recovery and Unroot (bootloader is still unlock), update again, result in error with the android robot and red exclamation.
Happen to my Nexus 7 and Galaxy Nexus as well (same unlock bootloader cwm root, same revert method, same error).
Has anyone face this and any solution to make OTA works?
Get back to stock, then try again
Sent from my Nexus 4 using xda premium
Had the same problem. This will answer all your questions
http://forum.xda-developers.com/showthread.php?t=2145848
thanks for the link. it did not directly make my device can be updated, but incase others have this problem and looking for solution, here are the things I did and fix it:
flash boot.img and flash system.img
these 2 files are needed to be at STOCK, I extract from the factory image, and flash through fastboot.
flashing these 2 files WILL NOT CAUSE application to be formatted (like what I thought at the first time).
It will simply remove any tweak done to system such as ads blocking (adaway, etc), battery icon mod, etc.
Then, you can update just fine.
Again, BIG THANKS to xda community.
raijinshou said:
thanks for the link. it did not directly make my device can be updated, but incase others have this problem and looking for solution, here are the things I did and fix it:
flash boot.img and flash system.img
these 2 files are needed to be at STOCK, I extract from the factory image, and flash through fastboot.
flashing these 2 files WILL NOT CAUSE application to be formatted (like what I thought at the first time).
It will simply remove any tweak done to system such as ads blocking (adaway, etc), battery icon mod, etc.
Then, you can update just fine.
Again, BIG THANKS to xda community.
Click to expand...
Click to collapse
Sorry, but I searched and searched but I still don't understand. I removed all my mods.
I wanted to update to 4.2.2 but it says apply_patch_check error about Currents.
How do I flash that boot.img and system.img? Trough custom recovery or stock? And where can I find those files? Thanks.
Guzanni said:
Sorry, but I searched and searched but I still don't understand. I removed all my mods.
I wanted to update to 4.2.2 but it says apply_patch_check error about Currents.
How do I flash that boot.img and system.img? Trough custom recovery or stock? And where can I find those files? Thanks.
Click to expand...
Click to collapse
boot.img and system.img can be founded in the STOCK ROM, here is the link for STOCK 4.2.1 for Nexus 4:
https://docs.google.com/open?id=0B_zuNWpIf1ujNlFDVnZ3dzg2WEU
(Source: http://www.randomphantasmagoria.com/firmware/nexus-4/occam/ )
Extract the file, you can find boot.img and system.img inside it.
To flash these 2 files, since I am not familiar with fastboot, I am using Nexus 4 Toolkit to help with it.
You can download Nexus 4 Toolkit: http://goo.im/devs/mskip/toolkit/google_nexus4/Google_Nexus_4_ToolKit_v1.3.0.exe
(Source: http://forum.xda-developers.com/showthread.php?t=1995688 )
Copy boot.img and system.img to Nexus 4 Toolkit folder of "put_img_files_to_flash_here"
then using "11. Boot or Flash .img Files to Device option", flash the file to the correct partition
(when flashing boot.img, to boot partition | when flashing system.img, to system partition).
Related
So I want to update to 4.2.2 using the Nexus Toolkit (I have the latest one) but have been running into problems. Every time I try to update it fails: assert failed: apply_patch_check ("/system/lib/libSR_AudioIn.so", bcc09f67f497c66aedece202942bc4c45f712f62", "85eeeb97d102a3f6656e58cb25ad97bbe29ec613")
After reading around I found out that the Beats Audio drivers I had installed (and thought I removed) modified that .so file. I'd like to be able to just replace that single file with the stock version to save me the hassle of flashing the whole stock image.
Does anyone know where I can find a copy of that file, or a work around that I can use?
Thanks!
http://forum.xda-developers.com/showthread.php?t=2144330
use 'search thread', people have similar issues, you'll find a solution there.
Yeah, I read through about 10 different threads about this but none of them actually had a solution... Just a bunch of "This is happening UPDATE: Fixed it" type posts. No one has actually posted their solution in any of the threads I've looked through (including the one you linked). Thanks for the link though.
issak42 said:
http://forum.xda-developers.com/showthread.php?t=2144330
use 'search thread', people have similar issues, you'll find a solution there.
Click to expand...
Click to collapse
i am also looking for SiMILAR Method like how we installed BEATS AUDIO so the method should be the same if someone can provide stock audio driver ZIP so we can reflash it back to get old drivers
I had this same exact problem.
I had beats audio installed and even with the script uninstaller and uninstalling the APP my LIB file was missing. i copied it from N4 and still it kept failing on that LIB file every time i applied the OTA zip
the BEST way to resolve this is to
extract the SYSTEM.IMG and BOOT.IMG file from the 4.2.1 stock image
FASTBOOT FLASH SYSTEM.IMG to your device
FASTBOOT FLASH BOOT.IMG to your device
this will flash the stock system files AND kernal to your device.
reboot your device and try to flash the OTA again and it should work.
Thanks. That's exactly what I did... I decided to use the Nexus 7 Toolkit to just restore to stock (I was getting frustrated so I didn't care if it removed all my apps, etc). It turns out the toolkit lets you restore the stock image without wiping all of your apps/sd data so I was able to update and everything was great. Not rooted anymore, but I'll deal with that later .
nextelbuddy said:
I had this same exact problem.
I had beats audio installed and even with the script uninstaller and uninstalling the APP my LIB file was missing. i copied it from N4 and still it kept failing on that LIB file every time i applied the OTA zip
the BEST way to resolve this is to
extract the SYSTEM.IMG and BOOT.IMG file from the 4.2.1 stock image
FASTBOOT FLASH SYSTEM.IMG to your device
FASTBOOT FLASH BOOT.IMG to your device
this will flash the stock system files AND kernal to your device.
reboot your device and try to flash the OTA again and it should work.
Click to expand...
Click to collapse
i had the same deal. flashed system.img, updated, flashed su. i didn't flash boot though
?need to flash boot.img
Thanks for above. I have solved the beats audio problem as per above. I only flashed the system.img and not the boot.img. Does this matter? Or should I do so to get the latest kernel? or is my kernel 3.1.10-g05b777c the latest?
Cheers,
Sam
yuo need to be on stock everything so to be safe and retain all user data and apps, just flash system.img and boot.img
it wont hurt anything and saves you headaches
I am currently in the same boat. I can't seem to find the stock image for 4.2.1. On Google's site they only have 4.1.2 and 4.2.2. Does any one know where I can get it or at least the system.img and boot.img from it?? Thanks for the help.
Leif
Leifrn said:
I am currently in the same boat. I can't seem to find the stock image for 4.2.1. On Google's site they only have 4.1.2 and 4.2.2. Does any one know where I can get it or at least the system.img and boot.img from it?? Thanks for the help.
Leif
Click to expand...
Click to collapse
http://goo.im/devs/WugFresh/stock/nakasi
burnitdown said:
i had the same deal. flashed system.img, updated, flashed su. i didn't flash boot though
Click to expand...
Click to collapse
same here. Now on 4.2.2 rooted.
I tried flashing boot.img but I cant seem to fastboot to device because of an unknown partition error. What to do??
swidnik0
You sir, are a gentleman. Thanks for you help.
Leif
Try this command to resolve partition issue
Leonhan said:
I tried flashing boot.img but I cant seem to fastboot to device because of an unknown partition error. What to do??
Click to expand...
Click to collapse
> fastboot flash system system.img
[email protected] said:
> fastboot flash system system.img
Click to expand...
Click to collapse
Oh there, spot on! Thanks man!
nextelbuddy said:
I had this same exact problem.
I had beats audio installed and even with the script uninstaller and uninstalling the APP my LIB file was missing. i copied it from N4 and still it kept failing on that LIB file every time i applied the OTA zip
the BEST way to resolve this is to
extract the SYSTEM.IMG and BOOT.IMG file from the 4.2.1 stock image
FASTBOOT FLASH SYSTEM.IMG to your device
FASTBOOT FLASH BOOT.IMG to your device
this will flash the stock system files AND kernal to your device.
reboot your device and try to flash the OTA again and it should work.
Click to expand...
Click to collapse
Sorry for noon question
Any link for the guide ?
For flashing boot.IMG system.IMG
Sorry I have never done these things before
Sent from my Nexus 7 using Tapatalk HD
How/where to extract system.img and boot.img ??
rm79 said:
Thanks. That's exactly what I did... I decided to use the Nexus 7 Toolkit to just restore to stock (I was getting frustrated so I didn't care if it removed all my apps, etc). It turns out the toolkit lets you restore the stock image without wiping all of your apps/sd data so I was able to update and everything was great. Not rooted anymore, but I'll deal with that later .
Click to expand...
Click to collapse
How/where to extract system.img and boot.img ??
after I flashed 4.2.1 system and boot images
so after flashed system.img and boot.img i was able to upgrage 4.2.2 OTA but now my nexus is not rooted. so if im gonna root it again will i lose all my data and apps?
ashok_jeev said:
so after flashed system.img and boot.img i was able to upgrage 4.2.2 OTA but now my nexus is not rooted. so if im gonna root it again will i lose all my data and apps?
Click to expand...
Click to collapse
If your bootloader is already unlocked, then rooting it won't wipe your data.
I just started using the Nexus 7 (WiFi) and I am on 4.2.1 and I am rooted. I rooted with the Wug's Toolkit. Anyway I want to update to 4.2.2 and I don't want to use any custom rom's, I just want to have an original update that I can flash without having to unroot. I have flashed my nexus with Clockwork Mod Recovery. Any places were I can get this rom and how I can install it?
Help Please!!
hettige677 said:
I just started using the Nexus 7 (WiFi) and I am on 4.2.1 and I am rooted. I rooted with the Wug's Toolkit. Anyway I want to update to 4.2.2 and I don't want to use any custom rom's, I just want to have an original update that I can flash without having to unroot. I have flashed my nexus with Clockwork Mod Recovery. Any places were I can get this rom and how I can install it?
Help Please!!
Click to expand...
Click to collapse
Hello there!
What about a little search? is a search bar in every part of the forum!!!
Anyway there you go:
http://forum.xda-developers.com/showthread.php?t=1745781
Just don't get used to it :good:
Read the forum rules!
So I downloaded the zip but it won't install properly it says error code 7??
Sent from my Nexus 7 using xda app-developers app
n/m
hettige677 said:
So I downloaded the zip but it won't install properly it says error code 7??
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
That's because you are using a custom recovery. You can either flash a stock recovery or edit some files in the zip so you can flash it in the custom recovery.
Leonhan said:
That's because you are using a custom recovery.
Click to expand...
Click to collapse
Possibly, but probably not. In most of the reports that have been coming in - when the users actually report the full error message rather than saying something ambiguous like "I got a Status 7 error" - the problems revolve around altered/removed files in /system, or having a custom kernel (boot or LNX partition) installed. That suggests that the recovery version is not causing assert() failures.
The other thing to rememder is that the program that is interpreting the edify updater-script is the "updater-binary" program which is shipped inside the OTA - so it is virtually identical independent of the choice of recovery (other than perhaps kernel behavior differences).
Leonhan said:
You can either flash a stock recovery or edit some files in the zip so you can flash it in the custom recovery.
Click to expand...
Click to collapse
Even though what you are saying here does only require being able to operate a plain-text editor and a zip tool, it's way above the heads of most folks who think that OTAs should work on non-stock ROMs. And I'm not sure how these folks would be better off with partially-patched ROMs. In any event, if this course is taken indeed a custom recovery would need to be used for this, as modifying the zip contents will break the OTA package signing, so the stock recovery couldn't be used.
The OP should just
- make a full nandroid backup of what they have now
- download the factory 4.2.2 images from Google
- extract the system.img file and boot.img images
( hint for windoze users: 7-zip understands .tgz files)
fastboot flash boot boot.img
fastboot flash system system.img
- reflash a basic SuperSU or Superuser root kit
Sort of crude, but it's a decent hack for the lazy or poorly informed. It won't "erase my data", but presumably it will break whatever it was that altered the stock system and/or boot partitions - the very things that are causing the OTA to fail on them with their rooted & modified ROMs.
If they don't like the result, they can simply restore their nandroid backup.
All,
Thanks in advance for any help you can provide. I have a Nexus 4 that I rooted and installed CWM recovery on, but I never installed any new kernels, ROMs, or radios. I'm currently on 4.4.4 and I want to upgrade to Lollipop. The OTA upgrade failed. So I tried returning to stock recovery and doing both the OTA and adb sideloading the OTA zip. Both fail.
The error message is "Package expects build fingerprint of google/occam/mako:4.4.4/KTU84P/1227136:user/release-keys or google/occam/mako:5.0/LRX21T/1576899:user/release-keys; this device has google/occam/mako:4.4/KRT160/907817:user/release-keys." (But I definitely have 4.4.4 on my phone, not 4.4.0.)
The extra difficulty is that I really, really do not want to wipe my phone. I have a lot of apps with a lot of configuration and other user data. So is there anything I can do? I guess I should try unrooting somehow? Or is there some other zip I can download that, through some type of recovery, will install the OTA without doing this check and also without wiping me?
Thanks again!
moriarty00 said:
All,
Thanks in advance for any help you can provide. I have a Nexus 4 that I rooted and installed CWM recovery on, but I never installed any new kernels, ROMs, or radios. I'm currently on 4.4.4 and I want to upgrade to Lollipop. The OTA upgrade failed. So I tried returning to stock recovery and doing both the OTA and adb sideloading the OTA zip. Both fail.
The error message is "Package expects build fingerprint of google/occam/mako:4.4.4/KTU84P/1227136:user/release-keys or google/occam/mako:5.0/LRX21T/1576899:user/release-keys; this device has google/occam/mako:4.4/KRT160/907817:user/release-keys." (But I definitely have 4.4.4 on my phone, not 4.4.0.)
The extra difficulty is that I really, really do not want to wipe my phone. I have a lot of apps with a lot of configuration and other user data. So is there anything I can do? I guess I should try unrooting somehow? Or is there some other zip I can download that, through some type of recovery, will install the OTA without doing this check and also without wiping me?
Thanks again!
Click to expand...
Click to collapse
OTA wants complete stock and obviously it doesn't think so about your phone. One option could be to back up to the cloud or some place outside the phone with TiBu (or whatever backup app you trust), then flash lollipop and try restore from TiBu. Another option would be to unroot (Supersu has an option to completely unroot), then retry.
Actually, I figured out what works! This was on a stock rooted device with stock recovery, but I bet it would work with custom recovery too. Instructions modified from https://pay.reddit.com/r/nexus4/comments/1qny3f/howto_update_your_stock_w_lte_nexus_4_without/ .
1. Download the image you want from https://developers.google.com/android/nexus/images . Extract it, extract the .zip file inside it too, and collect all of the .img files into one folder.
2. adb reboot bootloader (and wait until the bootloader comes up)
3. fastboot flash bootloader bootloader-mako-makoz30f.img (or whatever file has a similar name, if you got a different image than I did)
4. fastboot reboot-bootloader (and wait until the bootloader comes back up)
5. fastboot flash radio radio-mako-m9615a-cefwmazm-2.0.1701.04.img (or whatever file has a similar name, if you got a different image than I did)
6. fastboot reboot-bootloader (and wait until the bootloader comes back up)
7. fastboot flash boot boot.img
8. fastboot flash recovery recovery.img
9. fastboot flash system system.img
10. fastboot format cache
11. fastboot reboot
12. Don't panic unless you've seen the startup animation for at least 15 minutes without anything else happening.
I lost root, but I imagine re-custom-recoverying and re-rooting won't be any harder than the first time around.
Hi moriarty00,
I'm going to try the same procedure, thank you for posting this.
Can you confirm that your data and app are safe after the upgrade?
moriarty00 said:
Actually, I figured out what works! This was on a stock rooted device with stock recovery, but I bet it would work with custom recovery too. Instructions modified from https://pay.reddit.com/r/nexus4/comments/1qny3f/howto_update_your_stock_w_lte_nexus_4_without/ .
1. Download the image you want from https://developers.google.com/android/nexus/images . Extract it, extract the .zip file inside it too, and collect all of the .img files into one folder.
2. adb reboot bootloader (and wait until the bootloader comes up)
3. fastboot flash bootloader bootloader-mako-makoz30f.img (or whatever file has a similar name, if you got a different image than I did)
4. fastboot reboot-bootloader (and wait until the bootloader comes back up)
5. fastboot flash radio radio-mako-m9615a-cefwmazm-2.0.1701.04.img (or whatever file has a similar name, if you got a different image than I did)
6. fastboot reboot-bootloader (and wait until the bootloader comes back up)
7. fastboot flash boot boot.img
8. fastboot flash recovery recovery.img
9. fastboot flash system system.img
10. fastboot format cache
11. fastboot reboot
12. Don't panic unless you've seen the startup animation for at least 15 minutes without anything else happening.
I lost root, but I imagine re-custom-recoverying and re-rooting won't be any harder than the first time around.
Click to expand...
Click to collapse
Wow, a 12-step program
I simply rolled back my changes, and applying the OTA was as simple as pressing the "restart and install" button Here are some steps:
I used the app Flashify from Play Store to flash stock 4.4.4 recovery. I downloaded the stock factory image from google's own site (this one), used 7zip to extract the archives (tgz and tar), found "recovery.img" and transfered that to my phone. Then chose that file in Flashify.
Uninstalled all apps that made system changes, like Xposed framework and mods, BetterBatteryStats etc.
Removed Root with SuperSU cleanup function
Rebooted for good measure and apply OTA from notification - wait an hour or two for it to complete
Profit (do we still say that on the internet? Getting old here...)
I don't know if certain ways to get root will break the OTA. I used towel-root, and apparently SuperSU was able to undo that completely.
DrDruge said:
Hi moriarty00,
I'm going to try the same procedure, thank you for posting this.
Can you confirm that your data and app are safe after the upgrade?
Click to expand...
Click to collapse
Yup, perfectly safe! Just make sure not to flash other images, like userdata.img.
venu123 said:
OTA wants complete stock and obviously it doesn't think so about your phone. One option could be to back up to the cloud or some place outside the phone with TiBu (or whatever backup app you trust), then flash lollipop and try restore from TiBu. Another option would be to unroot (Supersu has an option to completely unroot), then retry.
Click to expand...
Click to collapse
If I unroot with Supersu how do I get root back?
moriarty00 said:
Yup, perfectly safe! Just make sure not to flash other images, like userdata.img.
Click to expand...
Click to collapse
Thank you!
Unfortunately the steps did not work for me, maybe I had some irreversible modifications or I had followed a different rooting procedure.
Or maybe I made a mistake in the upgrading steps.
Anyway, I had to flash the whole ROM and now everything is working fine.
Hey!
Basically I have similar problem with upgrading from 4.4.4 to 5.0 using OTA. Log from TWRP says:
Package expects build fingerprint of google/occam/mako:4.4.4/KTU84P/1227136:user/release-keys or google/occam/mako:5.0/LRX21T/1576899:user/release-keys; this device has google/occam/mako:4.3/JWR66V/737497:user/release-keys.
Click to expand...
Click to collapse
Phone has been rooted using Nexus Root Toolkit. And as long as there wouldn't be a problem with flashing using adb and wiping all data, there is one setback... My nexus is somehow broken. Communication via USB does not work, at all. Neither phone nor PC sees other device. Certified LG service centre nearby said that it is problem with main board, so generally repair is unprofitable.
So question is: How do I update to 5.0 and then root, without USB connection to my PC?
Is there is an easy to do this without having to wipe everything and start over fresh?
Will this work? http://forum.xda-developers.com/general/paid-software/flashfire-t3075433
WiFivomFranMan said:
Is there is an easy to do this without having to wipe everything and start over fresh?
Will this work? http://forum.xda-developers.com/general/paid-software/flashfire-t3075433
Click to expand...
Click to collapse
I'm on the same boat, but I think our answer will come soon. Today I found out that WugFresh will be updating the NRT Toolkit to support the Nexus Player. See this post.
Why not just download the image and flash it? Plenty of guides on how to do this
lafester said:
Why not just download the image and flash it? Plenty of guides on how to do this
Click to expand...
Click to collapse
I didn't know that there were difficulties with 5.1.1. I used Wugfresh's tool to install 5.1.1 with the "no wipe" option and I had 5.1.1 just fine - but can't figure out how to get root back!! And I need root to expand the storage!! Right now I have a fresh, clean, 5.1.1 install on my NP.
I tried Wugfresh's tool, I sure wish it told me that it didn't work with the firmware that it had already detected!!
I also tried the Chainfire root.img that I used back on 5.0 and it seems to work until I tell SuperSU to update the binaries. At that point it basically times out and asks me to reboot.
What next?! Wait for Wugfresh? Is there another way to root?
I flashed the cm recovery from dhacker and used it to flash the newest beta of supersu. After that the app didn't show up until I installed it from the store but now it works fine
I just want to upgrade it without losing all my stuff (Saved games for my NES ROM, etc...)
Why don't you locate the save data in es file explorer and copy it to the cloud. Reimage nexus player and set up es file explorer, cloud and copy the saved data back to where you stored it.
would anyone be so kind to point me to one of the guides on how to use factory image/OTA to update from 5.0 rooted to 5.1.1? I don't care about keeping my settings, and I don't care about root. just want the latest and greatest.
thanks in advance
The Nexus Player is a Nexus device, and you can always upgrade to the latest version by using the factory images found here: https://developers.google.com/android/nexus/images. The procedure to flash a factory image on any Nexus device has not changed since the Nexus One was released, so you can look at any of the guides for Nexus devices.
Essentially it boils down to this: The factory image contains a few files in an archive format. There are a few images within that you need: bootloader (I can't remember what the name of the file is but it's something like xxxxbootloaderxxx.img), system.img, boot.img, recovery.img). Extract those images from within the archive and flash them. You do this by booting into the bootloader, opening a command prompt in the same folder that you downloaded the image files) on your PC and type the following commands:
fastboot flash bootloader bootloader.img
fastboot flash system system.img
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot format cache
If you also want to start fresh and wipe all your data, execute the following command: fastboot format userdata
Then execute: fastboot reboot
Done.
Notes:
1) You need to extract these files in the same directory as where you downloaded the images before proceeding.
2) if you are using Windows, you need to install the the driver (found here: http://developer.android.com/sdk/win-usb.html)
3) The procedure above assumes your bootloader is unlocked. If not, you will need to unlock it (using: fastboot oem unlock) and it will wipe all your data.
efrant said:
1) There is currently no way to get root on 5.1.1 without modifying the kernel (so that it boots SELinux in permissive mode).
Click to expand...
Click to collapse
??
I have root on my NP... I used SkipSoft's Toolkit - details are here: http://forum.xda-developers.com/nexus-6/orig-development/toolkit-skipsoft-unified-android-t2967053
etnpnys said:
??
I have root on my NP... I used SkipSoft's Toolkit - details are here: http://forum.xda-developers.com/nexus-6/orig-development/toolkit-skipsoft-unified-android-t2967053
Click to expand...
Click to collapse
You are correct. I was reading another thread talking about Android M, and then I replied to this thread, so my mistake.
I've edited my post.
efrant said:
You are correct. I was reading another thread talking about Android M, and then I replied to this thread, so my mistake.
I've edited my post.
Click to expand...
Click to collapse
Ok - whew! I know that I went through the process but I couldn't be 100% sure because I have tried so many things to get expanded storage working to no avail that I've kinda given up for the time being...
It's a nexus - use custom recovery to flash supersu and your rooted.... Done
Toneman07 said:
It's a nexus - use custom recovery to flash supersu and your rooted.... Done
Click to expand...
Click to collapse
Not necessarily... You still need a modified boot.img to get the whole thing working...
etnpnys said:
Not necessarily... You still need a modified boot.img to get the whole thing working...
Click to expand...
Click to collapse
Thats interesting considering both my nexus phone and samsung tablet are running stock kernels (boot.img) and rooted just fine using the above method.
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...