My Nexus 5 is rooted and in the past OTA updates have always worked just fine. I don't use a custom recovery. However, the November Android security update fails. I was thinking this was because BBS was installed as a system app. After uninstalling that it still doesn't work. The only other thing I use is Adaway, so I reverted back to the original hostfile and also uninstalled BusyBox. Still no dice. Or is it perhaps Marshmallow OTA updates simply won't work if the phone is rooted? How come in the past I've been able to do OTA updates with my phone being rooted?
What can I do to get the update? Does that mean I have to basically lose my user data every month to do an OTA update now and reroot my device? That's ridiculous!
anthonypiccolo said:
My Nexus 5 is rooted and in the past OTA updates have always worked just fine. I don't use a custom recovery. However, the November Android security update fails. I was thinking this was because BBS was installed as a system app. After uninstalling that it still doesn't work. The only other thing I use is Adaway, so I reverted back to the original hostfile and also uninstalled BusyBox. Still no dice. Or is it perhaps Marshmallow OTA updates simply won't work if the phone is rooted? How come in the past I've been able to do OTA updates with my phone being rooted?
What can I do to get the update? Does that mean I have to basically lose my user data every month to do an OTA update now and reroot my device? That's ridiculous!
Click to expand...
Click to collapse
Flash stock kernel with fastboot from the stock images if you have custom kernel. Also flash the system.img from stock images with fastboot to revert all changes you made on the system partition. Both action will NOT wipe your data.
If you dont have fastboot exe then the easiest way to get it and set up it correctly is to use 15 seconds adb installer http://forum.xda-developers.com/showthread.php?t=2588979
I would advise to reply NO to the installer when it ask for installing drivers. Use google's driver instead if your device does not recognised in fastboot mode by your pc.
If you done that correctly you can just shift+right click in the folder where the system.img and boot.img are and select open command window here. Then you can type
fastboot flash system system.img
fastboot flash boot boot.img
bitdomo said:
Flash stock kernel with fastboot from the stock images if you have custom kernel. Also flash the system.img from stock images with fastboot to revert all changes you made on the system partition. Both action will NOT wipe your data.
If you dont have fastboot exe then the easiest way to get it and set up it correctly is to use 15 seconds adb installer http://forum.xda-developers.com/showthread.php?t=2588979
I would advise to reply NO to the installer when it ask for installing drivers. Use google's driver instead if your device does not recognised in fastboot mode by your pc.
If you done that correctly you can just shift+right click in the folder where the system.img and boot.img are and select open command window here. Then you can type
fastboot flash system system.img
fastboot flash boot boot.img
Click to expand...
Click to collapse
I don't have a custom kernel. So I just need to do system.img?
What's boot.img?
Where do I download the correct system.img from?
anthonypiccolo said:
I don't have a custom kernel. So I just need to do system.img?
What's boot.img?
Click to expand...
Click to collapse
boot.img is usually the filename for kernels. The stock kernel has boot.img as file name. Download the stock rom for your current build from here https://developers.google.com/android/nexus/images
Extract the tar.gz file then the .zip file after that. You will the system.img file after extracting the zip file.
bitdomo said:
boot.img is usually the filename for kernels. The stock kernel has boot.img as file name. Download the stock rom for your current build from here https://developers.google.com/android/nexus/images
Extract the tar.gz file then the .zip file after that. You will the system.img file after extracting the zip file.
Click to expand...
Click to collapse
Okay, and I don't need the adb installer right? I can just use the NRT.
DoI still need to flash the boot.img if I don't use a custom kernel?
anthonypiccolo said:
Okay, and I don't need the adb installer right? I can just use the NRT.
DoI still need to flash the boot.img if I don't use a custom kernel?
Click to expand...
Click to collapse
You dont need to flash boot.img if you have stock kernel
I cannot tell can you use NRT to flash invidual .img files, I never used it.
Tapatalk-kal küldve az én Nexus 5-el
bitdomo said:
You dont need to flash boot.img if you have stock kernel
I cannot tell can you use NRT to flash invidual .img files, I never used it.
Tapatalk-kal küldve az én Nexus 5-el
Click to expand...
Click to collapse
Yep, worked just fine with NRT.
Cheers!
And that right there is the problem. Using a Root toolkit and doesn't know what a boot image is. The most basic of information.
Just a quick question in relation to this, besides system.img, should the radio also be flashed?
Related
I'm new to rooting and android in general. I'm currently running 4.4 rooted with stock I believe. Says ponury kernal in my settings.
I'm trying to flash the update for 4.4.2 via the TWRP install. I get a failed error: error executing updater binary in zip.
I've made sure my zip is the 4.4 to 4.4.2 but still no luck. Any ideas what I can do? Do I need to wipe something before I can put it on there?
On a first thought, you need to get back to the original kernel.
Update from 4.4.1 to .4.4.2. has no problems with different kernels installed, however this won't work from 4.4. to 4.4.2.
The exact error message would be also helpful
tom1807 said:
On a first thought, you need to get back to the original kernel.
Update from 4.4.1 to .4.4.2. has no problems with different kernels installed, however this won't work from 4.4. to 4.4.2.
The exact error message would be also helpful
Click to expand...
Click to collapse
The error was : error executing updater binary in zip. I will look into getting back to stock.
matthewordie said:
The error was : error executing updater binary in zip. I will look into getting back to stock.
Click to expand...
Click to collapse
You need to fastboot flash the system and boot image from 4.4 if you have a custom kernel. Then flash the update
jd1639 said:
You need to fastboot flash the system and boot image from 4.4 if you have a custom kernel. Then flash the update
Click to expand...
Click to collapse
How do I fastboot flash the system and boot image? Can I do that from TWRP or do I need to use the command line with the fastboot? I have fastboot installed on my mac already. I was playing with that as well.
matthewordie said:
How do I fastboot flash the system and boot image? Can I do that from TWRP or do I need to use the command line with the fastboot? I have fastboot installed on my mac already. I was playing with that as well.
Click to expand...
Click to collapse
You'll need to get the factory image and extract the files. Inside there is another zip file which you'll need to extract. That's where you'll find the images. Use fastboot flash system system.img The Mac command is slightly different, I don't remember exactly what it is. To fastboot boot its the similar format
jd1639 said:
You'll need to get the factory image and extract the files. Inside there is another zip file which you'll need to extract. That's where you'll find the images. Use fastboot flash system system.img The Mac command is slightly different, I don't remember exactly what it is. To fastboot boot its the similar format
Click to expand...
Click to collapse
Is there a method of rooting or a specific kernal that will make it easier to update next time? I'd really hate to have to wipe everything every time there's an OTA update.
matthewordie said:
Is there a method of rooting or a specific kernal that will make it easier to update next time? I'd really hate to have to wipe everything every time there's an OTA update.
Click to expand...
Click to collapse
then stop modding your phone if you want OTAs.
its really that simple.
just flash the 4.4.2 factory images.
matthewordie said:
Is there a method of rooting or a specific kernal that will make it easier to update next time? I'd really hate to have to wipe everything every time there's an OTA update.
Click to expand...
Click to collapse
Flashing the system image won't wipe anything
http://forum.xda-developers.com/showthread.php?p=14
Sent from my Nexus 5 using Tapatalk
Zepius said:
then stop modding your phone if you want OTAs.
its really that simple.
just flash the 4.4.2 factory images.
Click to expand...
Click to collapse
Well I really don't know the exact steps involved in "flashing the image". That's what I'm asking.
jd1639 said:
Flashing the system image won't wipe anything
Click to expand...
Click to collapse
Then I guess I had the wrong impression of what flashing the image is. Is there a guide available?
matthewordie said:
Then I guess I had the wrong impression of what flashing the image is. Is there a guide available?
Click to expand...
Click to collapse
Follow method#2. But only flash the system.img and boot.img. http://forum.xda-developers.com/showthread.php?p=47156064
Edit, your bootloader is unlocked, right? If not then you will lose all you data unlocking it
jd1639 said:
Follow method#2. But only flash the system.img and boot.img. http://forum.xda-developers.com/showthread.php?p=47156064
Edit, your bootloader is unlocked, right? If not then you will lose all you data unlocking it
Click to expand...
Click to collapse
Ah, I was close I actually did method 1. Yeah I did leave it unlocked since i'm going to root again right away. Thanks
I'm trying to flash the OTA update to 4.4.3, but during the system file check I'm getting an error that says that /system/bin/thermal-engine-hh has unexpected contents. I'm running stock rooted with franco kernel, but I flashed back to the stock 4.4.2 kernel before trying this. The only other thing I have installed non-stock is busybox.
Does anyone know what messes with that file and how to revert the changes?
vaindil said:
I'm trying to flash the OTA update to 4.4.3, but during the system file check I'm getting an error that says that /system/bin/thermal-engine-hh has unexpected contents. I'm running stock rooted with franco kernel, but I flashed back to the stock 4.4.2 kernel before trying this. The only other thing I have installed non-stock is busybox.
Does anyone know what messes with that file and how to revert the changes?
Click to expand...
Click to collapse
you CAN NOT install an ota when you are not fully stock. you will receive an ota, but it will always error out. you have to be completely stock to update via ota. by completely stock i mean completely, not even a build.prop edit. busybox is not stock.
simms22 said:
you CAN NOT install an ota when you are not fully stock. you will receive an ota, but it will always error out. you have to be completely stock to update via ota. by completely stock i mean completely, not even a build.prop edit. busybox is not stock.
Click to expand...
Click to collapse
I just uninstalled busybox and tried again, but I'm unfortunately getting the same error. I know that custom recovery and root are safe for flashing an OTA update, and they're the only two remaining non-stock things I have on the device.
Flashed stock boot.img again and this time also included stock system.img, then the OTA update flashed properly.
vaindil said:
Flashed stock boot.img again and this time also included stock system.img, then the OTA update flashed properly.
Click to expand...
Click to collapse
Haha ha. Crazy. If you were going to Flash a stock system.img, why not flash the 4.4.3 one?
Sent from my Nexus 5 using Tapatalk
Rename the files after uninstalling Franco kernel
Refer to here: plus.google.com/wm/1/+EzioTroito86/posts/LxN2SqqCpa4
You need to rename two files in the /system partition after removing Franco kernel. I renamed the files, and update my Nexus 5 to 4.4.3 successfully.
vaindil said:
I'm trying to flash the OTA update to 4.4.3, but during the system file check I'm getting an error that says that /system/bin/thermal-engine-hh has unexpected contents. I'm running stock rooted with franco kernel, but I flashed back to the stock 4.4.2 kernel before trying this. The only other thing I have installed non-stock is busybox.
Does anyone know what messes with that file and how to revert the changes?
Click to expand...
Click to collapse
harrysummer said:
Refer to here: plus.google.com/wm/1/+EzioTroito86/posts/LxN2SqqCpa4
You need to rename two files in the /system partition after removing Franco kernel. I renamed the files, and update my Nexus 5 to 4.4.3 successfully.
Click to expand...
Click to collapse
Thanks a lot for this suggestion.
I removed xposed, SU and franco kernel but was stuck at this issue.
Renaming the files did it.
Thanks once again.
No need to remove SU
You are doing almost the same thing as I did. I was using supersu. And, I found that SU do not bother the update, because it do not modify any files in the system. However, the update will remove the su binary automatically...
nirmit14 said:
Thanks a lot for this suggestion.
I removed xposed, SU and franco kernel but was stuck at this issue.
Renaming the files did it.
Thanks once again.
Click to expand...
Click to collapse
harrysummer said:
Refer to here: plus.google.com/wm/1/+EzioTroito86/posts/LxN2SqqCpa4
You need to rename two files in the /system partition after removing Franco kernel. I renamed the files, and update my Nexus 5 to 4.4.3 successfully.
Click to expand...
Click to collapse
Thanks! That solved it for me
Sorry for the thread revival, but I'm in the same boat. I am using Linaro kernel however, which is a Franco spinoff if I remember correctly. Would the above mentioned page with fix of filenames for Franco, fix my issue as well?
Mysticodex said:
Sorry for the thread revival, but I'm in the same boat. I am using Linaro kernel however, which is a Franco spinoff if I remember correctly. Would the above mentioned page with fix of filenames for Franco, fix my issue as well?
Click to expand...
Click to collapse
Things have changed. You must be fully stock now, including recovery. As before, stock kernel etc. You're best just flashing the updated system.img and boot.img, or one of the rom.zip
I have a thread about this in my signature.
rootSU said:
Things have changed. You must be fully stock now, including recovery. As before, stock kernel etc. You're best just flashing the updated system.img and boot.img, or one of the rom.zip
I have a thread about this in my signature.
Click to expand...
Click to collapse
I've flashed in stock system.img, and stock boot.img. Just finished re-doing it via NExus Toolkit. The latest error I am getting is the thermal engine system error. This led me to think I need to rename the files, as per the instructions about Franco, as people were saying even AFTER putting on stock system.img, these files remained?
Mysticodex said:
I've flashed in stock system.img, and stock boot.img. Just finished re-doing it via NExus Toolkit. The latest error I am getting is the thermal engine system error. This led me to think I need to rename the files, as per the instructions about Franco, as people were saying even AFTER putting on stock system.img, these files remained?
Click to expand...
Click to collapse
1) please done use toolkits. Its simple enough to do manually
2) these files exist in stock anyway
3) if you're flashing stock system image, why not just flash the latest then it won't matter?
rootSU said:
1) please done use toolkits. Its simple enough to do manually
2) these files exist in stock anyway
3) if you're flashing stock system image, why not just flash the latest then it won't matter?
Click to expand...
Click to collapse
I flashed system.img, and boot.img. I did not install 5.0 completely. I am just trying to repair my main system/recovery/boot files to work with the normal OTA.
Mysticodex said:
I flashed system.img, and boot.img. I did not install 5.0 completely. I am just trying to repair my main system/recovery/boot files to work with the normal OTA.
Click to expand...
Click to collapse
Sorry, no idea what you're talking about now or what the problem is.
rootSU said:
Sorry, no idea what you're talking about now or what the problem is.
Click to expand...
Click to collapse
nirmit14 says he had to rename two files, most importantly thermal-engine-hh.bak, however Is am not quite sure how to get access to these files, so I ask for advice on that.
Thanks.
Mysticodex said:
nirmit14 says he had to rename two files, most importantly thermal-engine-hh.bak, however Is am not quite sure how to get access to these files, so I ask for advice on that.
Thanks.
Click to expand...
Click to collapse
If you flash the kernel, it renames existing STOCK thermal-engine-hh to thermal-engine-hh.bak then creates new thermal-engine-hh. OTA Will not work with new thermal-engine-hh so you must delete that and rename STOCK thermal-engine-hh.bak Back to thermal-engine-hh
HOWEVER, if you flashed system.img like you said, then you only have STOCK thermal-engine-hh (because it is in system.img) and have NO thermal-engine-hh.bak at all.
So the answer to your question is irrelevant as you don't need to.
As for now you rename system files, options are
- root explorer
- adb shell
- file manager in recovery
But just flash 5.0 system.img and boot.img and be done with it.
I had originally manually flashed system.img and boot.img, and the file is there there.
I have sinced pulled the file onto my PC, renamed it, and pushed it back on. I will try the OTA again.
Mysticodex said:
I had originally manually flashed system.img and boot.img, and the file is there there.
I have sinced pulled the file onto my PC, renamed it, and pushed it back on. I will try the OTA again.
Click to expand...
Click to collapse
The. Bak file was still there? Assume you didn't wipe system when you flashed it then
rootSU said:
The. Bak file was still there? Assume you didn't wipe system when you flashed it then
Click to expand...
Click to collapse
Correct, everything was left on, I simply flashed the img files from the factory image. I assumed it would just overwrite it system.img.
Flashing recovery.img removed TWRM, so I thought the others would do the same.
Edit: Reflashed system.img using Nexus toolkit, and now the OTA took. I had confirmed that this flashing did remove the thermal file entirely. Still not sure what modified it, but I'm guessing it's Linaro kernel.
Currently running Android 4.4.3. I have TWRP installed. To upgrade can I just flash system.img and radio.img within TWRP? I believe that this is how I upgraded from 4.4.2 to 4.4.3 but my memory is hazy and this was before I installed a custom kernel. I'm not sure on whether I need to do anything additional such as rolling back to stock 4.4.3 before upgrading to 4.4.4. I've seen people discuss this but I think that's just if one wants to run the OTA update.
you can. or you can just dirty flash(no wiping) a stock rooted rom from the android development section, and your kernel, and reboot
prnz said:
Currently running Android 4.4.3. I have TWRP installed. To upgrade can I just flash system.img and radio.img within TWRP? I believe that this is how I upgraded from 4.4.2 to 4.4.3 but my memory is hazy and this was before I installed a custom kernel. I'm not sure on whether I need to do anything additional such as rolling back to stock 4.4.3 before upgrading to 4.4.4. I've seen people discuss this but I think that's just if one wants to run the OTA update.
Click to expand...
Click to collapse
You are correct, except you flash img files with fastboot.
Aerowinder said:
You are correct, except you flash img files with fastboot.
Click to expand...
Click to collapse
Thanks. Is there any way to do it from recovery? I hate having to hook up the USB cable, etc.
Also, this seems a lot easier than what is suggested here (Special Scenario #1) http://forum.xda-developers.com/google-nexus-5/general/info-nexus-5-ota-help-desk-t2523217
1) downloaded factory image from https://developers.google.com/androi...ges#hammerhead
2) extract the tgz, the tar within that, then extract the the zip within that to get the system.img and boot.img files
3) moved these two files into the adb folder (for the fastboot/adb method)
4) downloade SuperSU-v1.80.zip from http://download.chainfire.eu/supersu
5) put SuperSU-v1.80.zip on your phone's internal storage
6) download the 4.4.1 OTA update zip from http://android.clients.google.com/pa...M.7ed504f6.zip
7) rename it to ota.zip
8) move ota.zip onto your phone's internal storage
9) boot into bootloader
10) open command prompt from your adb folder
11) connect USB cable
12) type 'fastboot devices' to check the connection
13) type 'fastboot flash system system.img'
14) type 'fastboot flash boot boot.img'
15) use volume and power buttons to boot into recovery (TWRP)
16) install ota.zip
17) install SuperSU-v1.80.zip
18) clear dalvik and cache
19) reboot phone
Click to expand...
Click to collapse
Seems to me like people go to a lot of extra work installing the OTA instead of the factory images.
prnz said:
Thanks. Is there any way to do it from recovery? I hate having to hook up the USB cable, etc.
Also, this seems a lot easier than what is suggested here (Special Scenario #1) http://forum.xda-developers.com/google-nexus-5/general/info-nexus-5-ota-help-desk-t2523217
Seems to me like people go to a lot of extra work installing the OTA instead of the factory images.
Click to expand...
Click to collapse
extra work is done in both those methods. just dirty flash a precompiled rooted stock rom and your kernel. itll take seconds to a minute, and you wont lose anything. and you do that in recovery.
simms22 said:
extra work is done in both those methods. just dirty flash a precompiled rooted stock rom and your kernel. itll take seconds to a minute, and you wont lose anything. and you do that in recovery.
Click to expand...
Click to collapse
Not to create a flamewar but I'm too afraid of security issues to install a pre-rooted ROM.
prnz said:
Not to create a flamewar but I'm too afraid of security issues to install a pre-rooted ROM.
Click to expand...
Click to collapse
have you ever seen or heard(a real one, not just "stories") of a security issue?
prnz said:
Not to create a flamewar but I'm too afraid of security issues to install a pre-rooted ROM.
Click to expand...
Click to collapse
The ones on XDA are safe. Just as safe as you rooting your stock ROM.
Sent from my Nexus 5 using Tapatalk
I recently unlocked my Nexus 5's bootloader and flashed Android L on it, which wiped all my data. I just downloaded the Google image for Android 5.0.1 for my device from the Android site, and need someone to point me in the right direction on how to apply the update without wiping my user data. I just checked on my phone for an OTA update and it didn't find one. I have AT&T, but bought the phone from Google Play Store.
Edit the flash-all.bat and remove the "-w" bit in the "fastboot -w update image-hammerhead-lrx22c.zip" line
Delete the userdata.img in the image-hammerhead-lrx22c.zip file (you can do this in 7zip or the built-in Windows zip tool)
Flash as normal using the flash-all.bat once your phone is in the bootloader.
Just done the above myself and it has upgraded fine without losing my data.
ianm said:
Edit the flash-all.bat and remove the "-w" bit in the "fastboot -w update image-hammerhead-lrx22c.zip" line
Delete the userdata.img in the image-hammerhead-lrx22c.zip file (you can do this in 7zip or the built-in Windows zip tool)
Flash as normal using the flash-all.bat once your phone is in the bootloader.
Click to expand...
Click to collapse
Thanks for the quick response! I'll try this.
Edit: It worked!
You also could have extracted the image files and done
Code:
fastboot flash system system.img
fastboot flash radio radio.img
fastboot flash boot boot.img
rootSU said:
You also could have extracted the image files and done
Code:
fastboot flash system system.img
fastboot flash radio radio.img
fastboot flash boot boot.img
Click to expand...
Click to collapse
Are these the only .img files you need to flash? Why not the others? I know flashing userdata.img will erase your data but the others? Is nothing else updated, e.g. recovery or bootloader?
The factory image is to return it all to stock so you can start again but you only really need those three if you want to keep your custom recovery. Personally, I flash everything and set my phone up fresh with every factory image but then again most of my data is in the cloud these days so I don't mind wiping data
EddyOS said:
The factory image is to return it all to stock so you can start again but you only really need those three if you want to keep your custom recovery. Personally, I flash everything and set my phone up fresh with every factory image but then again most of my data is in the cloud these days so I don't mind wiping data
Click to expand...
Click to collapse
It worked great. Used the same method on my Nexus 7 2013 the other day sans flashing radio. I have too many apps so I gladly avoid the hassle of re-installing everything and signing in on 20+ different apps. I know I can use titanium or other methods to backup all data etc, but I think the fastboot method is the most convenient if you don't have limited bandwidth.
If someone want's a guide on how to use the non OTA fastboot method without loosing data I made a separate one here: http://forum.xda-developers.com/google-nexus-5/help/guide-how-to-update-5-0-to-5-x-loosing-t2975174
update to 5.0.1
I'm on root, stock rom and custom recovery. I got the notification for 5.0.1 update and I'm not sure how to do the update. Can I flash the image from TWRP custom recovery?
g33kos said:
I'm on root, stock rom and custom recovery. I got the notification for 5.0.1 update and I'm not sure how to do the update. Can I flash the image from TWRP custom recovery?
Click to expand...
Click to collapse
no you can not. You have to sideload the ota in the stock recovery. This is different than before. You also have to be stock recovery, system, kernel and radio
Sent from my Nexus 5 using XDA Free mobile app
I've got a Nexus 5 with Android 5.0. I've had it rooted and unlocked using SkipSoft Unified Android Toolkit. I recently got a notification for an OTA update for 5.0.1. When I tried to install it, it downloaded ok but upon restarting it dropped me into teamwin recovery menu with options for: Install, Wipe, Backup, Restore, Mount, Settings, Advanced, Reboot. Not knowing what to do I clicked on Reboot -> System which booted back into the phone. Nothing changed or got installed.
Does anyone know how I can apply the latest OTA update? Do I have to unroot first, apply and then re-root? Does the Toolkit have support for 5.0.1 rooting yet?
TIA
You must be 100% stock to update so yes, you need to fully unroot.
Though you should just fastboot flash the system.img and boot.img
Don't use toolkits. Do things manually. You can either flash SuperSU from recovery or use cf-auto root from a computer.
Its very easy, there is flashable 5.0 stock ROM, I dirty flashed, or you can do it like rootSU said via fastboot, root has been lost, then I flashed stock recovery via fastboot, there is thread for recoveries, then I upgraded via ota and flashed twrp via fastboot and flashed SuperSU to gain root and custom kernel.
My way is much quicker though as you flash 5.0.1 system and boot straight away. Nothing else.
rootSU said:
My way is much quicker though as you flash 5.0.1 system and boot straight away. Nothing else.
Click to expand...
Click to collapse
We will never understand why people even bother with OTAs regardless what we ever tell them
rootSU said:
You must be 100% stock to update so yes, you need to fully unroot.
Though you should just fastboot flash the system.img and boot.img
Don't use toolkits. Do things manually. You can either flash SuperSU from recovery or use cf-auto root from a computer.
Click to expand...
Click to collapse
Ok, I'm not 100% sure I understood everything you said. I've downloaded the 5.0.1 update from here: https://developers.google.com/android/nexus/images. Using 7zip, I noticed the system.img and boot.img is contained in the tgz file (along with several other files). Do I just extract just those two files? And then what do I do in Teamwin?
Will all my apps and data persist?
TIA
Techno79 said:
Ok, I'm not 100% sure I understood everything you said. I've downloaded the 5.0.1 update from here: https://developers.google.com/android/nexus/images. Using 7zip, I noticed the system.img and boot.img is contained in the tgz file (along with several other files). Do I just extract just those two files? And then what do I do in Teamwin?
Will all my apps and data persist?
TIA
Click to expand...
Click to collapse
Boot into bootloader
fastboot flash system system.img
fastboot flash boot boot.img
Boot into Lollipop
You didn't touch userdata.img so it doesn't touch the data partition, although a wipe is usually recommended anyways because it's a new version of Android.
Lethargy said:
Boot into bootloader
fastboot flash system system.img
fastboot flash boot boot.img
Boot into Lollipop
You didn't touch userdata.img so it doesn't touch the data partition, although a wipe is usually recommended anyways because it's a new version of Android.
Click to expand...
Click to collapse
Sweet, that worked a great. Thank you.