Hey I have an unlocked boot loader, stock 4.2.1 ROM but running ktoonz kernel. In order to get the next update will I have to re flash the stock kernel, recovery, and re-lock my bootloader? I'm really only familiar with Samsung galaxy devices where you can just ODIN everything
Sent from my SGH-T999 using xda premium
Jms122589 said:
Hey I have an unlocked boot loader, stock 4.2.1 ROM but running ktoonz kernel. In order to get the next update will I have to re flash the stock kernel, recovery, and re-lock my bootloader? I'm really only familiar with Samsung galaxy devices where you can just ODIN everything
Sent from my SGH-T999 using xda premium
Click to expand...
Click to collapse
You will need the stock kernel and your /system partition must be completely unmodified. Bootloader state and recovery don't matter. After accepting an update you will lose your custom recovery and root, so you will have to reflash but that's no big deal.
Sent from my Nexus 7 using Tapatalk HD
Awesome thanks a lot, is there a link for a flashable stock kernel? I don't ry feel like restoring from my old recovery
Sent from my SGH-T999 using xda premium
Jms122589 said:
Awesome thanks a lot, is there a link for a flashable stock kernel? I don't ry feel like restoring from my old recovery
Sent from my SGH-T999 using xda premium
Click to expand...
Click to collapse
Download the latest factory images at http:// developers.google.com/android/nexus/images. Open the package, and flash boot.img.
Sent from my Galaxy Nexus using Tapatalk 2
oldblue910 said:
Download the latest factory images at http:// developers.google.com/android/nexus/images. Open the package, and flash boot.img.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Hey can u also help me
I was running CM10.1 then I flashed back the stock image of 4.2 and now I am not able to update it to 4.2.1 it shows me an error when installing.
Please help!!!
udimars30 said:
Hey can u also help me
I was running CM10.1 then I flashed back the stock image of 4.2 and now I am not able to update it to 4.2.1 it shows me an error when installing.
Please help!!!
Click to expand...
Click to collapse
You have to flash both system and boot, plus do a full data and cache wipe. As long as you do that and you don't let root apps modify files on your /system partition, the update should install fine. Also, keep in mind that when you get the OTA notification on your phone, you cannot just select "Restart and Install" if you have ClockworkMod recovery. OTAs will only auto flash if you have stock recovery. If you're using ClockworkMod recovery, you'll have to pull the OTA file out of your /cache folder and put it on internal storage somewhere, then flash it manually in ClockworkMod.
OK so am I flashing the boot image and system image through fastboot? If so how do I do that? If not...how do I flash them?
Sent from my SGH-T999 using xda premium
Jms122589 said:
OK so am I flashing the boot image and system image through fastboot? If so how do I do that? If not...how do I flash them?
Sent from my SGH-T999 using xda premium
Click to expand...
Click to collapse
Correct. Just extract system.img and boot.img from the package you download, then plug your tablet into USB, boot it into the bootloader, and do the following two commands:
fastboot flash boot boot.img
fastboot flash system system.img
If you want to wipe data, also do:
fastboot erase cache
fastboot erase userdata
That'll get you back to complete stock.
OK so were am I extracting these files to? Root of mysd card, desktop, etc? Thanks a bunch for your help btw I'm just not experienced at all with flashing outside of recovery or odin
Sent from my Nexus 10 using xda premium
Jms122589 said:
OK so were am I extracting these files to? Root of mysd card, desktop, etc? Thanks a bunch for your help btw I'm just not experienced at all with flashing outside of recovery or odin
Sent from my Nexus 10 using xda premium
Click to expand...
Click to collapse
Extract them to your desktop somewhere, then do fastboot from the command prompt.
oldblue910 said:
You have to flash both system and boot, plus do a full data and cache wipe. As long as you do that and you don't let root apps modify files on your /system partition, the update should install fine. Also, keep in mind that when you get the OTA notification on your phone, you cannot just select "Restart and Install" if you have ClockworkMod recovery. OTAs will only auto flash if you have stock recovery. If you're using ClockworkMod recovery, you'll have to pull the OTA file out of your /cache folder and put it on internal storage somewhere, then flash it manually in ClockworkMod.
Click to expand...
Click to collapse
sorry but i didn't get this part 'As long as you do that and you don't let root apps modify files on your /system partition' and to flash all that i need unlock bootloader??
oldblue910 said:
You have to flash both system and boot, plus do a full data and cache wipe. As long as you do that and you don't let root apps modify files on your /system partition, the update should install fine. Also, keep in mind that when you get the OTA notification on your phone, you cannot just select "Restart and Install" if you have ClockworkMod recovery. OTAs will only auto flash if you have stock recovery. If you're using ClockworkMod recovery, you'll have to pull the OTA file out of your /cache folder and put it on internal storage somewhere, then flash it manually in ClockworkMod.
Click to expand...
Click to collapse
I did all that you said but didn't understand this 'As long as you do that and you don't let root apps modify files on your /system partition' then i tried to update manually and it did again showed me an error like this:
udimars30 said:
I did all that you said but didn't understand this 'As long as you do that and you don't let root apps modify files on your /system partition' then i tried to update manually and it did again showed me an error like this:
Click to expand...
Click to collapse
Did you use the JOP40C factory images downloaded from the Google website somewhat recently? That error is caused when you flash the original set of JOP40C images released when the Nexus 10 first came out. There was a bug in them that Google fixed. They posted new images. You can download them at http://developers.google.com/android/nexus/images or http://www.randomphantasmagoria.com/firmware/nexus-10/mantaray.
Also, what I mean about root apps modifying /system files...so there are a lot of root apps out there that make tweaks to your system...stuff like making changes to your GPS config files for quicker lock-on, you yourself going in and deleting unwanted apps out of /system/app, you or an app making changes to build.prop, installing busybox in the wrong place and having it overwrite system commands with its own...things like that. If you or any app make any change whatsoever to any file anywhere on /system, an OTA will fail every time. It checks the hash of each and every file before applying the update and if a single one of them doesn't match what it expects, the OTA will fail. So just keep that in mind.
But that error you're getting about set_perm is most definitely caused by using the original, bad set of images that Google put out there. Download them again, try again and you should be in business.
oldblue910 said:
Did you use the JOP40C factory images downloaded from the Google website somewhat recently? That error is caused when you flash the original set of JOP40C images released when the Nexus 10 first came out. There was a bug in them that Google fixed. They posted new images. You can download them at http://developers.google.com/android/nexus/images or http://www.randomphantasmagoria.com/firmware/nexus-10/mantaray.
Also, what I mean about root apps modifying /system files...so there are a lot of root apps out there that make tweaks to your system...stuff like making changes to your GPS config files for quicker lock-on, you yourself going in and deleting unwanted apps out of /system/app, you or an app making changes to build.prop, installing busybox in the wrong place and having it overwrite system commands with its own...things like that. If you or any app make any change whatsoever to any file anywhere on /system, an OTA will fail every time. It checks the hash of each and every file before applying the update and if a single one of them doesn't match what it expects, the OTA will fail. So just keep that in mind.
But that error you're getting about set_perm is most definitely caused by using the original, bad set of images that Google put out there. Download them again, try again and you should be in business.
Click to expand...
Click to collapse
Thanks a ton dude but any place where i can talk to you??
like facebook or Google+??
udimars30 said:
Thanks a ton dude but any place where i can talk to you??
like facebook or Google+??
Click to expand...
Click to collapse
I'm on Twitter and G+. Just click on my name over on the left of this post and you can find links to my profiles.
Related
A while back I altered my build.prop file and accidently deleted it. I didn't make a backup so I restored it with one that someone posted and I haven't had any problems.
However since I did that, the OTA update that I got notified for did not install.
My boot loader is unlocked and I am rooted with stock recovery.
How can I update to 4.1.2 manually and still keep root?
I understand there are plenty of posts about this but everyone has a different problem and I'm just trying to get the correct information. Thanks for any help.
Sent from my Nexus 7 using xda app-developers app
somerandomname1 said:
A while back I altered my build.prop file and accidently deleted it. I didn't make a backup so I restored it with one that someone posted and I haven't had any problems.
However since I did that, the OTA update that I got notified for did not install.
My boot loader is unlocked and I am rooted with stock recovery.
How can I update to 4.1.2 manually and still keep root?
I understand there are plenty of posts about this but everyone has a different problem and I'm just trying to get the correct information. Thanks for any help.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Download the OTA update JZO54K-fromJRO03D
Download SuperSu or Superuser
put the OTA update and SuperSu or Superuser in a in your /sdcard/Download directory
Flash ClockworkMod recovery from fastboot
http://download2.clockworkmod.com/recoveries/recovery-clockwork-touch-6.0.1.0-grouper.img
Code:
> fastboot flash recovery recovery-clockwork-touch-6.0.1.0-grouper.img
Boot recovery from the fastboot menu
Install the OTA update, then install SuperSu or Superuser.
Thanks man appreciate it.
Sent from my Nexus 7 using xda app-developers app
this actually didn't work...everything was working fine, but it aborted and mentioned my build.prop file as the reason why...
somerandomname1 said:
this actually didn't work...everything was working fine, but it aborted and mentioned my build.prop file as the reason why...
Click to expand...
Click to collapse
Here's the build.prop from JRO03D load that up and try again. If that fails, you can manually update to 4.1.2 from the factory image without modifying user data.
this worked my friend, thanks.
I'm having the exact same problem, same circumstances, down to the update not taking because I accidentally deleted a system file, except the file in question is the gmail .odex file because I deleted that to install the unreleased gmail 4.2 app. Any help?
EDIT: Fixed thanks to user comminus via PM. Cheers.
So i just switched from HTC ONE X to the nexus 4 and my version is 4.2 and i just rooted it. I have the system OTA update 4.2.1. Should i take it or is there another way to update my phone to 4.2.1 without OTA?
Do not OTA update once you're already rooted; flash this stock ROM (https://www.dropbox.com/s/syi2vmxh0noi2bv/occam-jop40d-factory-ca7602f0.tgz) and re-root.
klvnhng said:
Do not OTA update once you're already rooted; flash this stock ROM (https://www.dropbox.com/s/syi2vmxh0noi2bv/occam-jop40d-factory-ca7602f0.tgz) and re-root.
Click to expand...
Click to collapse
Thank you i was looking for this file! so i just put it in my SD card and then install Zip from sd card from recovery?
ronnyg12 said:
Thank you i was looking for this file! so i just put it in my SD card and then install Zip from sd card from recovery?
Click to expand...
Click to collapse
That is a tgz file, not a zip. You'll need a PC, 7zip and fastboot.
estallings15 said:
That is a tgz file, not a zip. You'll need a PC, 7zip and fastboot.
Click to expand...
Click to collapse
Yes yes i figured it out
I've been trying to do this without wiping my device. It's still downloading so I haven't seen the contents, but I'm assuming just flash the .img files with fastboot and it won't erase anything? Would the Rootkeeper app work for this?
if you're only rooted, ota will work and would install without issues. it will only fail if you have modified some system files or the recovery. no need to reflash anything except the supersu for root if you don't use rootkeeper
I'm using Franco's kernel and CWM recovery. I have the stock system files, so if I flash those back, how do I go about applying this update? I'm so sick of seeing the update message in my notification bar and do not want to wipe to flash a new ROM.
Edit: I have previously tried flashing the stock boot.img and recovery.img, but trying the update via the notification still failed.
Nitemare3219 said:
I'm using Franco's kernel and CWM recovery. I have the stock system files, so if I flash those back, how do I go about applying this update? I'm so sick of seeing the update message in my notification bar and do not want to wipe to flash a new ROM.
Click to expand...
Click to collapse
Flash the stock recovery.img and boot.img. You won't lose anything.
Nitemare3219 said:
I'm using Franco's kernel and CWM recovery. I have the stock system files, so if I flash those back, how do I go about applying this update? I'm so sick of seeing the update message in my notification bar and do not want to wipe to flash a new ROM.
Edit: I have previously tried flashing the stock boot.img and recovery.img, but trying the update via the notification still failed.
Click to expand...
Click to collapse
Your settings probably also modified the system files. Try flashing that too since you have the stock files. Just don't do userdata so your data is kept intact
Sent from my Nexus 4 using Tapatalk 2
why it is not possible to make OTA update on rooted phone?
Sent from my Nexus 4 using Tapatalk 2
I rooted, unlocked bootloader and flashed recovery yesterday then installed the OTA after, had no issues at all. If you are using cwm recovery it re-roots and prevents stock recovery being flashed after the ota is installed.
So am running rooted 4.2.1 at the mo.. And its sick
Sent from my Nexus 4 using xda app-developers app
blablazzz said:
why it is not possible to make OTA update on rooted phone?
Click to expand...
Click to collapse
You can, it's fine and will work as long as you have stock recovery. You might lose root but can easily re-root if necessary.
Sent from my Nexus 4 using xda premium
why OTA will not work if custom recovery will be present?
Sent from my Nexus 4 using Tapatalk 2
blablazzz said:
why OTA will not work if custom recovery will be present?
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
Because it won`t!!!
Hi,
I have been trying to update my N4 for quite sometime now and have had a particular issue every time. First I tried with the OTA file and adb sideload. Didn't work. Then this morning I received the OTA on the phone itself, tried doing it but still got the same error message. It says "Installation aborted. Error (Status 7)" I have no clue whatsoever what it is. Please help.
I am using stock rom, rooted.
P.S. if this has already been posted by someone else, kindly direct me to that thread.
Thanks
Error status 7 means modification to the /system directory. You must fastboot flash the stock 4.4.2 /system image only from the factory image package and then you will be able to sideload the update, all with no loss of data. This is what I did since my /system was heavily modified. After flashing the ota, re apply all your /system tweaks, if any.
Sent from my Nexus 4 using XDA Free mobile app
I used the following thread.
Long story short I grabbed the stock ROM and flashed only the system. img to phone
http://android.stackexchange.com/qu...ttempting-to-adb-sideload-the-ota-update-on-n
Sent from my Nexus 4 using XDA Premium 4 mobile app
anubhavmehta said:
Hi,
I have been trying to update my N4 for quite sometime now and have had a particular issue every time. First I tried with the OTA file and adb sideload. Didn't work. Then this morning I received the OTA on the phone itself, tried doing it but still got the same error message. It says "Installation aborted. Error (Status 7)" I have no clue whatsoever what it is. Please help.
I am using stock rom, rooted.
P.S. if this has already been posted by someone else, kindly direct me to that thread.
Thanks
Click to expand...
Click to collapse
Recovery versión?
Sent from my Nexus 4
Thanks a lot!
Hey, thanks for the info. One more question though, will fastboot flashing 4.4.2 system image remove all data? I guess the problem here might be because of Xposed Module, which might have made some changes in the system directory. The other issue that I am having is that I am unable to access any content on my laptop with my phone connected over USB, so i am unable to take backup of my data. I tried backup using recovery as well but it didn't work as well.
lolcakes203 said:
Error status 7 means modification to the /system directory. You must fastboot flash the stock 4.4.2 /system image only from the factory image package and then you will be able to sideload the update, all with no loss of data. This is what I did since my /system was heavily modified. After flashing the ota, re apply all your /system tweaks, if any.
Sent from my Nexus 4
Click to expand...
Click to collapse
CWM 6.0.4.3
tupac4u said:
Recovery versión?
Sent from my Nexus 4
Click to expand...
Click to collapse
Flashing the entire factory image will delete all your data and return your device to pure stock, but we are not asking you to do that. All you need to do is flash the system.img which is located in the factory image which will return your /system partition to pure stock, and this will not delete any data because it does not touch your /data partition.
Xposed does modify /system and was most likely the cause for your ota error. You can try disabling xposed and flashing again, but if you get more problems, it makes the most sense to flash system.img and then flash the ota and re apply xposed.
Sent from my Nexus 4 using XDA Free mobile app
yep, tried that. didn't work. I'll try the fastboot system.img solution and hope it works.
lolcakes203 said:
Flashing the entire factory image will delete all your data and return your device to pure stock, but we are not asking you to do that. All you need to do is flash the system.img which is located in the factory image which will return your /system partition to pure stock, and this will not delete any data because it does not touch your /data partition.
Xposed does modify /system and was most likely the cause for your ota error. You can try disabling xposed and flashing again, but if you get more problems, it makes the most sense to flash system.img and then flash the ota and re apply xposed.
Sent from my Nexus 4 using XDA Free mobile app
Click to expand...
Click to collapse
I am having the same problem, my nexus 4 is unrooted with clean stock img but I still get error in the middle of the OTA update to 4.4.3, anyone one know why? Please help
Worked!
All done with absolutely no loss of data. Thanks a lot! :good:
lolcakes203 said:
Flashing the entire factory image will delete all your data and return your device to pure stock, but we are not asking you to do that. All you need to do is flash the system.img which is located in the factory image which will return your /system partition to pure stock, and this will not delete any data because it does not touch your /data partition.
Xposed does modify /system and was most likely the cause for your ota error. You can try disabling xposed and flashing again, but if you get more problems, it makes the most sense to flash system.img and then flash the ota and re apply xposed.
Sent from my Nexus 4 using XDA Free mobile app
Click to expand...
Click to collapse
So I have pulled and uploaded the update zip file to drive just in case anyone needs it.
And modified to get it working on twrp with Modified system but important core apps like systemui.apk need to be untouched though, no need to flash stock again, just normal flash via TWRP, worked on mine.
And some people were asking if it flashes default recovery or not, so the Answer is TWRP/CWM will stick.
And you will not lose root Access too
Download Links:
TWRP/CWM flashable
Default OTA zip
Explanation of how solve if still having problems as posted by @[email protected]
[email protected] said:
As OP said,
U only have to edit the updater-script file present under condor_4.4.4_TWRP_flashable.zip\META-INF\com\google\android in order to get the zip file working.
1. Copy the condor_4.4.4_TWRP_flashable.zip file that OP shared to your PC.
2. Now open this file using any zip handler like 7zip/winzip/winrar/windows explorer(if running windows8+), browse to the above location to find updater-script file, now extract /copy this on your PC.
3. Now select an option to edit this file using Notepad++ (step 4 on how/what to edit/change)
4. As per the TWRP error log, remove all the lines from the updater-script in particular to that error.
For Ex. if the error says:
/system/app/LiveWallpapersPicker.apk\" has unexpected contents.
then u need to remove the following line from the updater-script
apply_patch_check("/system/app/LiveWallpapersPicker.apk", "f4b9dc41f0d4691a2f9b71be06036c1de91c43ea", "d57f5cbc092e3e6cab286793da70ee7ffc4f440e") || abort("\"/system/app/LiveWallpapersPicker.apk\" has unexpected contents.");
assert(apply_patch("/system/app/LiveWallpapersPicker.apk", "-",
f4b9dc41f0d4691a2f9b71be06036c1de91c43ea, 160480,
d57f5cbc092e3e6cab286793da70ee7ffc4f440e, package_extract_file("patch/system/app/LiveWallpapersPicker.apk.p")));
5. Once u are done with all such, simply save the updater-script and copy this back to its location and select replace if asked.
6. Now save the condor_4.4.4_TWRP_flashable.zip and copy it back to Phone and try flashing now using TWRP.
hope it helps
Click to expand...
Click to collapse
Only for XT1022
Gogeta said:
So I have pulled and uploaded the update zip file to drive just in case anyone needs it.
https://docs.google.com/file/d/0B72C6RSL0mQmVlVwZ1VBTWwzaVE/edit?usp=docslist_api
Click to expand...
Click to collapse
Can i use it on XT1022?
Anyone knows when the update comes out for the Europe retail?
mrpkarthik said:
Can i use it on XT1022?
Click to expand...
Click to collapse
It's for xt1022.
i have updated my phone though setting now after updating,, it works fine for 1 min, then it gets boot back into twrp(recovery)... any solution guys
sunnyx12x21x said:
i have updated my phone though setting now after updating,, it works fine for 1 min, then it gets boot back into twrp(recovery)... any solution guys
Click to expand...
Click to collapse
I also had the same problem...and flashed STOCK Recovery and Updates works great...
How to flash stock recovery...
Sent from my XT1022 using XDA Premium 4 mobile app
Nandha005 said:
How to flash stock recovery...
Sent from my XT1022 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Flash the attached recovery.img (after unzipping the archive) using fastboot or mfastboot.
This one is only for XT1022.
Okay, so tried to modify the updater script to get it working with TWRP but it won't work if you modified any system file by yourself because it verifies all the system files and then patches them, (I had modified many apks, so it didn't work.), tried to skip verification but then it failed during patch.
So you can try But it won't work for modified system. and must create a nandroid backup.
Use the attached updater script for TWRP.
Even Stock recovery won't work on modified system.
update works on rooted devices but there should be stock recovery
Rooted users can update their moto e but must have stock recovery. If you are facing problem with trwp recovery while updating it, then flash the stock recovery annd then try. It works
Hit thanx if helped
If I flash Stock recovery data is wipe or not...
Sent from my XT1022 using XDA Premium 4 mobile app
Nandha005 said:
If I flash Stock recovery data is wipe or not...
Sent from my XT1022 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
no
I have flashed stock recovery and downloaded update file using settings but now when it start installs it shows installation unsuccessful and whenever I boot into stock recovery it shows no command with dead android
Sent from my XT1022 using XDA Free mobile app
@Gogeta I downloaded the update and choose install later. How to pull the downloaded update file ? I am rooted with TWRP.
gtsfreak said:
I have flashed stock recovery and downloaded update file using settings but now when it start installs it shows installation unsuccessful and whenever I boot into stock recovery it shows no command with dead android
Sent from my XT1022 using XDA Free mobile app
Click to expand...
Click to collapse
As i said, it verifies all system files before update, you must have modified or deleted something.
raj.amalw said:
@Gogeta I downloaded the update and choose install later. How to pull the downloaded update file ? I am rooted with TWRP.
Click to expand...
Click to collapse
/cache
but only if you are rooted
Nope I have only deleted stock apps that's all
Sent from my XT1022 using XDA Free mobile app
gtsfreak said:
Nope I have only deleted stock apps that's all
Sent from my XT1022 using XDA Free mobile app
Click to expand...
Click to collapse
Gogeta said:
As i said, it verifies all system files before update, you must have modified or deleted something.
Click to expand...
Click to collapse
Thats what i said
So what should I do now I don't wanna loose any data please help?
Sent from my Z10 using XDA Free mobile app
[HELP]
How To Manually Flash The OTA.Zip On Stock Unrooted Device ?
ADB sideload
salkollizz said:
How To Manually Flash The OTA.Zip On Stock Unrooted Device ?
Click to expand...
Click to collapse
guys u can use adb sideload on TWRP 2 flash d update package
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...