I had a hard time finding this information, so thought I would post a new thread!
After you root your phone, even if using standard recovery, the OTA updates will no longer install. You may get the notifications, but after it reboots to install, you will get a failed notification. Even if you uninstall root. This is because if there is any change to the system image at all, the OTA update will fail.
To install it is actually easy, just requires some legwork. I assume you understand what the bootloader is, and what adb and fastboot tools are since your phone is already rooted. If you used a toolkit, there are plenty of guides on XDA on how to install these tools manually.
Step 1 - Collect Needed Files:
Visit the Google System Images page and download the image for your existing ROM. Check your About Device page to get the exact ID, it should say something like LVY48E.
Extract the system.img file so you can flash it later.
Download the OTA image. All OTA images are listed on the Nexus 6 OTA Images thread. Find the file which upgrades "From" your current ROM id. It will only work if from matches your current image version. It will be named something like 2bef78c4a5ec8dbaa3df9d94e78af8622cd2a394.signed-shamu-LVY48F-from-LVY48E.2bef78c4.zip, and this file in particular flashes to the new LVY48F version from LVY48E version.
Step 2 - Flash Stock System Image:
This step replaces your system image with the stock system image. This will not delete your apps or other personal data, only the information stored on the system partition. The only exception is if you rooted and stored any data on this partition. Plug your phone into your computer. There is no way to do this without a PC.
Reboot into bootloader mode either from booting with POWER+VOLDOWN or via adb:
Code:
adb reboot bootloader
and flash the image
Code:
fastboot erase system
fastboot flash system system.img
At this point your system is stock again (unrooted).
Step 3 - Flash Update Image:
Enter the recovery mode. You can also do this via TWRP but I will cover with stock recovery. Press Volume Up/Down until you see RECOVERY and press power to choose. You are now in recovery.
Press and hold Power and tap Volume Up once to get the recovery menu. Then use Volume Up/Down to select "apply update from ADB" and then Power to select
I had to unplug and plug my phone back in at this point to get it to show up to adb. You can confirm it is visible with the command adb devices.
Apply the OTA update file using the following command, replacing the file name with your own:
Code:
adb sideload 2bef78c4a5ec8dbaa3df9d94e78af8622cd2a394.signed-shamu-LVY48F-from-LVY48E.2bef78c4.zip
After a few minutes the sideload will complete, the phone will reboot and optimize apps, and you can verify the update worked by checking your about system page again.
To root your device again, re-install SuperSU and you're good to go.
I actually just asked about this in the T-Mobile thread, but thanks for making this. My question is, when installing system.img is there anything else you NEED to flash as well, specifically boot and/or cache?
Google has the latest stock image for T-Mobile so I was planning on flashing system and radio, but I wasn't sure if there was anything else required when flashing system.img.
I know I don't want recovery or userdata as that would replace TWRP and all my data, so I'd of course leave those out.
hayzooos said:
I actually just asked about this in the T-Mobile thread, but thanks for making this. My question is, when installing system.img is there anything else you NEED to flash as well, specifically boot and/or cache?
Google has the latest stock image for T-Mobile so I was planning on flashing system and radio, but I wasn't sure if there was anything else required when flashing system.img.
I know I don't want recovery or userdata as that would replace TWRP and all my data, so I'd of course leave those out.
Click to expand...
Click to collapse
Nope, system.img was all that I flashed, verified it worked fine with just that.
So you just have to re-root after right?
JTheAppMerchant said:
So you just have to re-root after right?
Click to expand...
Click to collapse
Correct
Thanks for this guide. I've been trying to figure out how to do this exact thing. When I do the command:
adb sideload 4458964f84d2e44ecd2c1c31c301d47eec4b080e.signed-shamu-LMY48M-from-LMY48I.4458964f
Click to expand...
Click to collapse
it gets to about 50%, then gives a Error message,
E:Error in /sideload/package.zip (Status 7) Installation aborted.
Click to expand...
Click to collapse
Any suggestions?
falconfox said:
Thanks for this guide. I've been trying to figure out how to do this exact thing. When I do the command:
it gets to about 50%, then gives a Error message,
Any suggestions?
Click to expand...
Click to collapse
First try a different USB cable and port.
Thanks for the guide. Does it wipe all the data and files in internal storage?
I did this successfully
torecdude said:
Thanks for the guide. Does it wipe all the data and files in internal storage?
Click to expand...
Click to collapse
I wanted to say thanks first of all for putting this up. It helps those rooted users out there that do actually want security patches applied to the system image. To answer the question above, No it does not wipe data or storage if you follow the instructions to only modify /system partition.
A note about the LMY48M update file and the above comments in the OP : This update changes the kernel (in other words), the boot.img file as well. So if you have flashed a non-stock kernel, you will need to go back to stock during the update (and I suggest just leaving it). That is the partition called boot where boot.img lives. It mainly is the kernel. The way to go back to stock (say if you flashed franco with the FKupdate tool and did not do it manually) is to simply do like above and flash it from the factory image he mentions above for 48I file.
You reboot to the bootloader (*I assume you know how*) with power and vol down button. And then the following command after flashing system.img:
fastboot flash boot boot.img
This takes you to stock LMY48I and should allow you to update now to 48M. I learned this by watching the update failure messages as well as noticed it has boot.img changed in the zip file. Hope this helps others. :good:
bitpushr said:
First try a different USB cable and port.
Click to expand...
Click to collapse
I'm having the exact same issue/error. Already tried new USB ports and cables.
falconfox said:
When I do the command:
it gets to about 50%, then gives a Error message, Any suggestions?
Click to expand...
Click to collapse
confused2much said:
I'm having the exact same issue/error. Already tried new USB ports and cables.
Click to expand...
Click to collapse
Open the update .zip file and go to META_INF > COM > GOOGLE > ANDROID. You will find the "updater-script" file.
Open that file using a text editor like notepad or notepad++ and delete the following text; starting from "assert ....... till the semicolon of the last getprop command.
Place that file back into the update .zip file and reflash. This should remove the status 7 error.
jase33 said:
Open the update .zip file and go to META_INF > COM > GOOGLE > ANDROID. You will find the "updater-script" file.
Open that file using a text editor like notepad or notepad++ and delete the following text; starting from "assert ....... till the semicolon of the last getprop command.
Place that file back into the update .zip file and reflash. This should remove the status 7 error.
Click to expand...
Click to collapse
I'll try this now, thanks for the response!
Honest question: why would you flash a system image and an ota when you could just flash the new system image?
jhotmann said:
Honest question: why would you flash a system image and an ota when you could just flash the new system image?
Click to expand...
Click to collapse
By flashing just the current system image your data stays in tact. Then you can take the OTA, it will see the system image unmodified, and it will update everything for that new version without wiping data.
jase33 said:
Open the update .zip file and go to META_INF > COM > GOOGLE > ANDROID. You will find the "updater-script" file.
Open that file using a text editor like notepad or notepad++ and delete the following text; starting from "assert ....... till the semicolon of the last getprop command.
Place that file back into the update .zip file and reflash. This should remove the status 7 error.
Click to expand...
Click to collapse
I do not have the text "assert" anywhere in that file....
jase33 said:
By flashing just the current system image your data stays in tact. Then you can take the OTA, it will see the system image unmodified, and it will update everything for that new version without wiping data.
Click to expand...
Click to collapse
Easier to just flash the new system image that gets you to the same place as the OTA.
jhotmann said:
Honest question: why would you flash a system image and an ota when you could just flash the new system image?
Click to expand...
Click to collapse
I was wondering this same exact thing, but I was assuming it was because the OTA was hitting people before that matching Google Factory Image was available. This would bring you almost back a version (to being stock) so you could take the OTA.
If the OTA is to match the same Factory Image you can get from Google, I have no idea why you'd do both steps.
Hi, I have the LNX07M, and I don't find it in the google page. Can you help me? please!
hayzooos said:
I was wondering this same exact thing, but I was assuming it was because the OTA was hitting people before that matching Google Factory Image was available. This would bring you almost back a version (to being stock) so you could take the OTA.
If the OTA is to match the same Factory Image you can get from Google, I have no idea why you'd do both steps.
Click to expand...
Click to collapse
I think the only reason to do both steps is to apply the update ASAP. If you are ok waiting, then only flash the new system.img. That's definitely what I always do. I don't mind waiting. I have Google Play Services notifications hidden now anyway, so those update notifications don't show up and bug me.
Thanks for the walk through though, @bitpushr, I'm sure many can make use of it.
confused2much said:
I do not have the text "assert" anywhere in that file....
Click to expand...
Click to collapse
Honestly, you shouldn't edit those files as that can be dangerous, and disabling the filesystem check can be dangerous, and it probably won't work because then the zip would fail signing verification.
If you followed all of the instructions in OP and still get error 7, try, on top of erasing and flashing the stock system.img, also extract and erase then flash boot.img and recovery.img. You will get error 7 if your recovery and kernel (boot.img) aren't stock.
Related
Rooting and updating your MotoActv is about to get significantly easier! No more waiting games for developers to update their ROMs or tools when Motorola pushes a new OTA; now you can do it yourself! I honestly have not seen these types of files ANYWHERE else, so I had to create these myself (with quite a bit of help from [mbm]). But enough blabbing, here are the files and how to use them:
(Note: all these methods assume we have full fastboot access! -- Which we still have at this point)
- Stock Images:
These are not just mere update.zips that you might be accustomed to elsewhere in Android. Nor are these mere fxzs that you might be accustomed to elsewhere with newer Motorola devices. They are in fact both and more. There are 3 main ways to flash these files onto your device, giving you options based on what OS you run and how comfortable you are flashing files to your device.
1) FXZ:
- Operating System: Windows
- Requires: RSD Lite with FXZ Support
- Instructions: Simply load up the file as any standard fxz (it is very straight-forward)
2) Recovery:
- Operating System: Anything that can mount your device
- Requires: The ability to get into recovery
- Instructions: Place the file on the sdcard, boot into recovery, flash as normal
- Note: Recovery does not wipe your device, it is suggested that you do so before flashing stock images
3) Fastboot:
- Operating System: Windows/Linux/Mac
- Instructions (Windows): Unpack the zip, run flash-all.bat (if it fails, run as administrator)
- Instructions (Linux/Mac): Unpack the zip, run flash-all.sh (it should already have proper permissions)
Miscellaneous Images:
These miscellaneous images are nothing you haven't seen before at this point, but their purposes are new, so they too require explanation.
1) AnyRoot:
AnyRoot is based on koush's AnyKernel in the sense that it unpacks and repacks the boot.img on the fly. However, as the name suggests, AnyKernel is meant for kernels, while AnyRoot, actually roots the device on the fly. This will work on any MotoActv device. It is flashed as a normal update.zip and everything is done in the background so you won't noticed much. However, for ease of access, the stock and rooted boot.img is exported to your sdcard in /sdcard/recovery/. Also note, that if you happen to flash AnyRoot over an already rooted device, nothing will happen as it has built-in error checking.
2) rebootRecovery:
rebootRecovery is another fxz type zip, the same as the stock and rooted images, except it can't be flashed in recovery (would be a little redundant don't you think?). This flashes a specially made misc.img by [mbm] that tells the device to reboot into recovery from boot. This means you can flash AnyRoot on any stock device.
How Tos / FAQs:
Now that you know what the files do, I can explain in short steps how to use these files to get what you want:
1) How to Return the Device to Stock?
- flash a stock image using any of the 3 methods
- you can now update via Motocast if you so wish
2) How to Root a Stock Device?
- update your device via Motocast to the latest version (suggested)
- place AnyRoot on your sdcard
- boot into fastboot, and flash rebootRecovery using either of the 2 methods
- flash AnyRoot in recovery
- reboot
3) How do I update my Rooted Device?
- flash a stock image using any of the 3 methods
- update your device via Motocast to the latest version
- place AnyRoot on your sdcard
- boot into fastboot, and flash rebootRecovery using either of the 2 methods
- flash AnyRoot in recovery
- reboot
Q: After using rebootRecovery I can't get out of recovery!?
A: You are using an old recovery that doesn't clear the 'reboot-recovery' command; use the newer recovery: https://dl.dropbox.com/u/5849675/android/f100/CWMR5x_F100_recoveryB2.img
Q: What do these ROM offer over other custom ROMs?
A: Nothing, they are simply stock images, but you can upgrade with them.
Q: How much battery should I have when I flash?
A: Performing any kind of these flashes will drain at least 10% of your battery, I wouldn't suggest you flash below 60% ESPECIALLY IF YOU FLASH rebootRecovery!
Q: What happens if I flash a 16gb zip on my 8gb or visa-versa?
A: Don't freak, it will still boot, but it's not the best thing in the world to do, just go back and flash the correct model zip.
Q: Can I extract the images from your zips and flash them my own way?
A: yep (couldn't really think of anything else to say)
Q: I manually flashed the stock-boot.img from AnyRoot, and now I can't update. Why?!
A: The boot.imgs need to be truncated before they can be flashed to correctly work with Motorola's updates, just use the stock images.
Q: What's next?
A: HyprActv -- What's this?
Stock Images (w/ md5sums):
8gb-NA: https://dl.dropbox.com/u/5849675/android/f100/MA_1710_8GB_NA.zip (5e228bf56a67aced012c8cbb2d7f7c76)
16gb-NA: https://dl.dropbox.com/u/5849675/android/f100/MA_1710_16GB_NA.zip (21b067dc629f7ccd18b43799d8d5fb17)
8gb-EU: https://dl.dropbox.com/u/5849675/android/f100/MA_1710_8GB_EU.zip (5b79a46d87728303fc2c920eec71c2e8)
Miscellaneous Images (w/ md5sums:
AnyRoot: https://dl.dropbox.com/u/5849675/android/f100/MA_AnyRoot.zip (2f867b006da42865ef861094db0eb6e6)
Reboot Recovery: https://dl.dropbox.com/u/5849675/android/f100/MA_RebootRecovery.zip (1623c9c61462db9bb20b55bc8f1144aa)
Mirror (thanks Iownox!): http://www.androtransfer.com/?developer=lownox&folder=MotoACTV
This is Reserved.
I rooted and flashed in recovery (the stock 4.55.97 and the the rooted version 4.55.97) and I stay on 4.55.78 no matter what! The flashes go through successfully... But nothing has changed and the System version still says 4.55.78... But like I said, the flashes both completed! I did a factory reset... and the updater-script wipes system, so what could be my issue?
Moose8106 said:
I rooted and flashed in recovery (the stock 4.55.97 and the the rooted version 4.55.97) and I stay on 4.55.78 no matter what! The flashes go through successfully... But nothing has changed and the System version still says 4.55.78... But like I said, the flashes both completed! I did a factory reset... and the updater-script wipes system, so what could be my issue?
Click to expand...
Click to collapse
It sounds like you flashed that old boot.img. Do you have the battery percentage in the status bar? According to TheEndGame7 that is another surefire way to tell if you are on 4.55.97, if you used any of the root tools, it's possible that they automatically flash the old boot.img.
CEnnis91 said:
It sounds like you flashed that old boot.img. Do you have the battery percentage in the status bar? According to TheEndGame7 that is another surefire way to tell if you are on 4.55.97, if you used any of the root tools, it's possible that they automatically flash the old boot.img.
Click to expand...
Click to collapse
I think I did flash the old boot.img (root tools :O ). I'll try flashing the modified boot img again. Thanks! I had no idea the root tool took me back to the old boot img
Moose8106 said:
I think I did flash the old boot.img (root tools :O ). I'll try flashing the modified boot img again. Thanks! I had no idea the root tool took me back to the old boot img
Click to expand...
Click to collapse
Yes, any and all tools that exist so far will need to be updated.
I wiped data / cache and used recovery (b) to install the rooted-4.55.97 zip and didn't have any luck either. I did not use the root tools to flash. Also wiped dalvik cache after and fastboot -w for fun.
innovatelife said:
I wiped data / cache and used recovery (b) to install the rooted-4.55.97 zip and didn't have any luck either. I did not use the root tools to flash. Also wiped dalvik cache after and fastboot -w for fun.
Click to expand...
Click to collapse
Did you end up doing any restore of some kind after you flashed?
Update
There are "new" instructions that might fix the issue where the rooted 4.55.97 appears to not flash. Simply wipe the boot.img image before you flash. And don't use the root tools until they are updated.
Also, if you have success, please post it. Usually "Thanks, it works" is annoying, but in this case where I don't have the device, I need to make sure this is working on some level.
I formated everything from recovery, now I got stuck with Moto logo with no animation when it starts, how to get out of this?
NA
Is there any mirrors for the download of these roms? the dropbox links are down
NORCALkID said:
Is there any mirrors for the download of these roms? the dropbox links are down
Click to expand...
Click to collapse
They were pulled, they're not working. There has been some form of mis-communication when I did my testing. I am not working on these until I can get the device from utkanos. Check Update 2, in the initial post.
Success
CEnnis91
I was lucky the second time, first time I succeeded to upgrade to rooted 4.55.97 but for some reason I didn't get the battery percentage on the status bar but all other issues are OK and status indicated version number 4.55.97, I repeated flash from recovery but after wiping and remounting all folders, this time for stock 4.55.97
Now I'm on stock 4.55.97 with battery percent on status bar and syncing from my mac.
thanks CEnnis91
NA
I went into recovery>mounts, and didn't see any wipe for boot. I took a shot at system since I had already wiped cache and data. Didn't seem to help either. Tried 'fastboot erase boot" and re-flashed. No go. Couldn't start back up the device at all. Tried flashing the latest rooted image using "fastboot flash boot boot.img". No go.
I messed around trying to get the device to boot back up for a while, but it won't even charge right. Only charges long enough to kick off the Motorola 'M', and that is it. On attempts at loading fastboot, I just keep getting an error saying that the battery is low. I know I can only blame myself for this. No fastboot access and no adb access. All attempts at resetting the device have failed.
Before I attempted all of this, my battery was full. Unfortunately, wouldn't charge anymore even plugged into the wall. Any ideas?
Hopefully nobody else makes my mistake.
Man I can't wait till this is perfect, you guys are fricken awesome. I raped your thanks buttons op lol
MoPhoACTV Initiative
Will be working on this tonight. I just found out how to make the flash script clear cache and dalvik for you, pre-install. That'll probably save some headache, but it works only in edify format. Not sure what the stock recovery uses...
Anyways, I'm home!
ClearD said:
Will be working on this tonight. I just found out how to make the flash script clear cache and dalvik for you, pre-install. That'll probably save some headache, but it works only in edify format. Not sure what the stock recovery uses...
Anyways, I'm home!
Click to expand...
Click to collapse
All recoveries will now use edify, amend is old and depreciated, you will only find that on old devices.
Corrupt Kernel...
innovatelife said:
I went into recovery>mounts, and didn't see any wipe for boot. I took a shot at system since I had already wiped cache and data. Didn't seem to help either. Tried 'fastboot erase boot" and re-flashed. No go. Couldn't start back up the device at all. Tried flashing the latest rooted image using "fastboot flash boot boot.img". No go.
I messed around trying to get the device to boot back up for a while, but it won't even charge right. Only charges long enough to kick off the Motorola 'M', and that is it. On attempts at loading fastboot, I just keep getting an error saying that the battery is low. I know I can only blame myself for this. No fastboot access and no adb access. All attempts at resetting the device have failed.
Before I attempted all of this, my battery was full. Unfortunately, wouldn't charge anymore even plugged into the wall. Any ideas?
Hopefully nobody else makes my mistake.
Click to expand...
Click to collapse
This is a classical case of a corrupt Kernel. Not that the images are corrupt, but somewhere along your update, your boot.img did not install the kernel properly and now you have a broken power manager within kernel.
What I would do is the following:
Hook your watch to the charger and let the M sign show up.
Even if it hangs on the M, leave your watch hooked over night.
Try downloading an older image and use fastboot to erase everything and then flash everything back again. This should return your watch to a working state again.
You may then choose to customize it as you see fit.
Root tool > "return to stock"
Sent from my HTC Inspire 4G using XDA-funded carrier pigeons
simx said:
CEnnis91
I was lucky the second time, first time I succeeded to upgrade to rooted 4.55.97 but for some reason I didn't get the battery percentage on the status bar but all other issues are OK and status indicated version number 4.55.97, I repeated flash from recovery but after wiping and remounting all folders, this time for stock 4.55.97
Now I'm on stock 4.55.97 with battery percent on status bar and syncing from my mac.
thanks CEnnis91
NA
Click to expand...
Click to collapse
I'm about to try this.. but it's making me think... Do you think the updater-script doesn't correctly format system? Think about it... our devices say 4.55.97 (mine changed to that after a reboot or two), and we only had partial features... sounds like something isn't wiping correctly.
Tried to update my wife's Nexus 10 tonight. It's unlocked and rooted, formerly on the stock version of Jelly Bean. I thought this would be an easy update since it was stock jellybean to kitkat with the official OTA file but I guess I was wrong. Got the OTA update notification so I allowed it to reboot and install. CWM Touch Recovery picked it up and I told it to install the unsigned zip. Got near the end and it had an error. Now it's stuck in boot (appears to be Kit Kat boot). Just sits on the 4 colored circles going in/out in the middle of the screen.
I need to fix this without wiping data. It's her only computer that she uses daily so she's got a million things on there she uses all the time. If I have to wipe data, she'll be pissed (and I'll lose my hard earned game saves).
Attached is a picture of the error. I've got WUG's toolkit if it's necessary to use to fix this. Any ideas what's going on and how to fix it? Thanks.
Stinger2300 said:
Tried to update my wife's Nexus 10 tonight. It's unlocked and rooted, formerly on the stock version of Jelly Bean. I thought this would be an easy update since it was stock jellybean to kitkat with the official OTA file but I guess I was wrong. Got the OTA update notification so I allowed it to reboot and install. CWM Touch Recovery picked it up and I told it to install the unsigned zip. Got near the end and it had an error. Now it's stuck in boot (appears to be Kit Kat boot). Just sits on the 4 colored circles going in/out in the middle of the screen.
I need to fix this without wiping data. It's her only computer that she uses daily so she's got a million things on there she uses all the time. If I have to wipe data, she'll be pissed (and I'll lose my hard earned game saves).
Attached is a picture of the error. I've got WUG's toolkit if it's necessary to use to fix this. Any ideas what's going on and how to fix it? Thanks.
Click to expand...
Click to collapse
I have a rooted/unlocked Nexus 10, I used wugfresh's kit also. I got the OTA update last night. it installed. CWM never came up or did anything. During one of the boots after the green droid bot was saying "installing" the boot finished, but my green bot is now on his side. stomach open and it says "Error" in red bold letter.
I had to go to work, so I couldnt trouble shoot, but power off/on and soft reset (power+volume up select reset) didnt help. always comes to that "error".
I have data that is also not currently backed up with TBpro. hindsight I should have made sure I turned the scheduler on.
So I'm stuck also. not sure how to proceed. Got one recommendation to flash stock back on. But I think that will for sure wipe all my data. And beyond that, I dont know how, unless WUGs kit will do that.
Your best bet it is to sideload. Grab the OTA and the FULL 4.4
Pull the recovery.img from the full 4.4 rar (its in the zip), fastboot flash it, reboot into bootloader, go to recovery and sideload the OTA and that should restore it just fine
EDIT: http://forum.xda-developers.com/showpost.php?p=47656450&postcount=8
my detailed instructions there for sideloading
planet_x69 said:
Your best bet it is to sideload. Grab the OTA and the FULL 4.4
Pull the recovery.img from the full 4.4 rar (its in the zip), fastboot flash it, reboot into bootloader, go to recovery and sideload the OTA and that should restore it just fine
EDIT: http://forum.xda-developers.com/showpost.php?p=47656450&postcount=8
my detailed instructions there for sideloading
Click to expand...
Click to collapse
I was about to say. whaaaaat? then saw the link with some details. Never done that stuff before, just used other tools kits, like wugs. But doesnt sound to bad. Will try when I get home. I presume when you say into a adb directory, its something on the desktop pc you are connected to. outside of perhaps some drivers, do I need other applications on the PC to facilitate the adb stuff you mention?
jetguat said:
I was about to say. whaaaaat? then saw the link with some details. Never done that stuff before, just used other tools kits, like wugs. But doesnt sound to bad. Will try when I get home. I presume when you say into a adb directory, its something on the desktop pc you are connected to. outside of perhaps some drivers, do I need other applications on the PC to facilitate the adb stuff you mention?
Click to expand...
Click to collapse
Well if you are unfamiliar with the process you will need to get the android SDK installed or find one of the pre-packaged current adb loads. It's very simple, get this package here: http://downloadandroidrom.com/file/Nexus10/Nexus10RootNew.zip# (yes its a crappy ad link but hey the guy packaged it all up so...).
If you are on a PC extract these to a folder of your choice.
Open file manager
Navigage to the folder you extracted the files to
on the left pan select the folder, press SHIFT and Right Click mouse, then select "Open command window here"
You can now follow my instructions from the other page - Do the following below FIRST
If you are prompted to accept security allowance on your device do so. you will likely only see this once you are back into the Android OS not in recovery.
This folder has all the basics you need to fastboot and run adb.
Connect your device to your pc and run >fastboot reboot-bootloader.
If your device restarts and goes into the bootloader you can relax and follow my instructions.
Hope this helps.
One other thing, that su zip is dated, you will need to flash the 1.51 version and you should be good to complete root process.
Wow, this seems about 3 miles over my head but I guess I'll dive in and try it. Thanks for the info. I'm sure I'll be back with problems/questions.
planet_x69 said:
Well if you are unfamiliar with the process you will need to get the android SDK installed or find one of the pre-packaged current adb loads. It's very simple, get this package here: http://downloadandroidrom.com/file/Nexus10/Nexus10RootNew.zip# (yes its a crappy ad link but hey the guy packaged it all up so...).
If you are on a PC extract these to a folder of your choice.
Open file manager
Navigage to the folder you extracted the files to
on the left pan select the folder, press SHIFT and Right Click mouse, then select "Open command window here"
You can now follow my instructions from the other page - Do the following below FIRST
If you are prompted to accept security allowance on your device do so. you will likely only see this once you are back into the Android OS not in recovery.
This folder has all the basics you need to fastboot and run adb.
Connect your device to your pc and run >fastboot reboot-bootloader.
If your device restarts and goes into the bootloader you can relax and follow my instructions.
Hope this helps.
One other thing, that su zip is dated, you will need to flash the 1.51 version and you should be good to complete root process.
Click to expand...
Click to collapse
OK, I downloaded the packaged linked above and extracted it to the desktop. Then I used file manager to "open command window here". Where do I get su zip 1.51? I tried to google a link but they all seemed newer (1.75 for example). Does it matter if it's 1.51 exactly or can it be any version 1.51 or newer? One last question regarding su zip, does that need to be updated after this whole process is complete and I'm up and running again, or does it need to be done before I move on to the instructions you linked to above? Thanks.
Stinger2300 said:
OK, I downloaded the packaged linked above and extracted it to the desktop. Then I used file manager to "open command window here". Where do I get su zip 1.51? I tried to google a link but they all seemed newer (1.75 for example). Does it matter if it's 1.51 exactly or can it be any version 1.51 or newer? One last question regarding su zip, does that need to be updated after this whole process is complete and I'm up and running again, or does it need to be done before I move on to the instructions you linked to above? Thanks.
Click to expand...
Click to collapse
You don't need to root at all but the updated supersu 1.75 will be just fine as its universal. You can get the official from here: http://download.chainfire.eu/368/SuperSU/UPDATE-SuperSU-v1.75.zip
You will install that ONLY after you have installed the OTA's and your custom recovery and only if you want root.
good luck!
planet_x69 said:
Your best bet it is to sideload. Grab the OTA and the FULL 4.4
Pull the recovery.img from the full 4.4 rar (its in the zip), fastboot flash it, reboot into bootloader, go to recovery and sideload the OTA and that should restore it just fine
EDIT: http://forum.xda-developers.com/showpost.php?p=47656450&postcount=8
my detailed instructions there for sideloading
Click to expand...
Click to collapse
In this link, you said to do the following:
Pull the full stock 4.4 image from here : https://developers.google.com/androi...mages#mantaray
open it and pull out from the zip in the rar the recovery.img, move a copy to your adb folder along with a copy of your custom recovery ( for discussion sake I'll use twrp.recovery.img)
Put copy of the patch in the adb folder and rename it to a short name like krt16s.zip
I got the full stock 4.4 image downloaded, extracted it, extracted the zip file inside (image-mantaray-krt16s.zip) and that provided me with "recovery.img" you mentioned above.
Now I have 2 problems, where is this "adb folder" you say to put the recovery.img in, and where is the custom recovery? I assume it's on the N10 after I connect it to my laptop. Is there a preferred custom recovery I should use? I saw mention of TWRP not working with Kit Kat elsewhere. Not sure if that is dated info or not.
Lastly, just to confirm this is true, none of this whole process will wipe my data correct?
planet_x69 said:
You don't need to root at all but the updated supersu 1.75 will be just fine as its universal. You can get the official from here: http://download.chainfire.eu/368/SuperSU/UPDATE-SuperSU-v1.75.zip
You will install that ONLY after you have installed the OTA's and your custom recovery and only if you want root.
good luck!
Click to expand...
Click to collapse
OK, downloaded that and will hold it for later. Hopefully after the questions I just asked are answered, I'll have enough info to proceed. Thanks for the help so far.
Stinger2300 said:
In this link, you said to do the following:
Pull the full stock 4.4 image from here : https://developers.google.com/androi...mages#mantaray
open it and pull out from the zip in the rar the recovery.img, move a copy to your adb folder along with a copy of your custom recovery ( for discussion sake I'll use twrp.recovery.img)
Put copy of the patch in the adb folder and rename it to a short name like krt16s.zip
I got the full stock 4.4 image downloaded, extracted it, extracted the zip file inside (image-mantaray-krt16s.zip) and that provided me with "recovery.img" you mentioned above.
Now I have 2 problems, where is this "adb folder" you say to put the recovery.img in, and where is the custom recovery? I assume it's on the N10 after I connect it to my laptop. Is there a preferred custom recovery I should use? I saw mention of TWRP not working with Kit Kat elsewhere. Not sure if that is dated info or not.
Lastly, just to confirm this is true, none of this whole process will wipe my data correct?
Click to expand...
Click to collapse
Correct - if you SIDELOAD the OTA it will UPGRADE and retain all data and application settings etc...
If you run the 4.4 update from the factory image it will WIPE ALL. So do not do that ....just pull the recover.img from it and get rid of the rest.
If you downloaded this: http://downloadandroidrom.com/file/N...10RootNew.zip#
and extracted it to a new folder - do this first!!!
then copy the recovery.img you just extracted from the factory 4.4 rar to the same folder as the adb and fastboot commands
copy the OTA file to same folder and rename it ota.zip to make your life easier
>fastboot reboot-bootloader to validate your computer can see the device and that the next steps will go as planned
If you are now back bootloader then:
>fastboot flash recovery recover.img
wait till its done..will take about 15 seconds tops
>fastboot reboot-bootloader again and go to recovery using the volume buttons
select and enter recovery mode
wait for dead droid to appear
press both Volume UP and Power at same time and you should get the load menu
select "apply updated from adb" and press power after selecting
orange colored type will now appear at the bottom of the screen
on your PC
>adb sideload ota.zip
wait till you see its completed successfully
then reboot
(you can also apply the smaller ota (1.7MB) this same way)
If all went well you have now booted up successfully and see that your ass has been saved from eternal hell from your wife's wrath...
reboot and fastboot flash your favorite custom recovery reboot again to recovery and apply the su update for root access
I hope this helps
You can also read this: http://www.androidpolice.com/2013/1...-download-and-install-android-4-4-now-krt16o/
You said: "just pull the recover.img from it and get rid of the rest."
So is your instruction from the original link to: "Put copy of the patch in the adb folder and rename it to a short name like krt16s.zip" replaced by the OTA file I renamed to ota.zip in order to retain all data? For reference, krt16s.zip is 390mb, ota.zip is 225mb.
Stinger2300 said:
You said: "just pull the recover.img from it and get rid of the rest."
So is your instruction from the original link to: "Put copy of the patch in the adb folder and rename it to a short name like krt16s.zip" replaced by the OTA file I renamed to ota.zip in order to retain all data? For reference, krt16s.zip is 390mb, ota.zip is 225mb.
Click to expand...
Click to collapse
not sure i follow you but from the 4.4 factory image you will need the recovery.img file thats it. You will also need the OTA upgrade that takes you from 4.3 to 4.4. You need the OTA so that you wont lose your wifes data and will upgrade only and not image the device.
I have to leave and wont be back on till later this weekend.
Going well so far...had an issue but figured it out.
Got to sideloading ota.zip, then after it got to 100% it started verifying the update package. Got an error:
'/system/app/BasicDreams.apk" has unexpected contents
E:Error in /tmp/update.zip
(status 7)
Installation aborted.
Now what?
I found this in the Nexus 7 section but not sure if it applies here or if there is a better way, if it's guaranteed to not wipe data, etc.: http://forum.xda-developers.com/showpost.php?p=47474021&postcount=26
Did you try this solution? I'm stuck on the "Error in /tmp/update.zip" as well. Having the same issues, and I hope to update without loosing data.
No, I haven't tried it as I can't risk losing data by randomly trying stuff I don't understand. I need someone who knows what they are doing to confirm that the steps in this link http://forum.xda-developers.com/showpost.php?p=47474021&postcount=26 won't wipe data or do anything that will require wiping data to finish this process.
have well
Stinger2300 said:
No, I haven't tried it as I can't risk losing data by randomly trying stuff I don't understand. I need someone who knows what they are doing to confirm that the steps in this link http://forum.xda-developers.com/showpost.php?p=47474021&postcount=26 won't wipe data or do anything that will require wiping data to finish this process.
Click to expand...
Click to collapse
I just tried it. And it worked. Didn't loose any data.
Flashing the img files, and then proceeding to sideload the OTA zip. Booting didn't take too long, Android then started upgrading ("Optimizing app..."), and booted successfully. It took a while to open de app drawer though... But everything was still there.
Regaining root access is something I'll try later. I'm just happy to have my N7 booting again.
Just a small disclaimer. I don't really know what I'm doing (I kinda like messing around with my device, it's only way to learn something), so I cannot guarantee it will work for you.
Glad it worked for you, it didn't work for me. I got another error after doing the following commands:
Then, run the following commands:
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot erase system
fastboot flash system system.img
then I rebooted back to bootloader, then "apply updated from adb" and then from the command line: >adb sideload ota.zip
It again loaded 100% and then started verifying the package. Then I got this error:
Package expects build fingerprint of google/mantaray/manta:4.3/JWR66Y/776638:user/release-keys or google/mantaray/manta:4.4/KRT160/907817:user/release-keys; this device has google/mantaray/manta:4.4/KRT16S/920375:user/release-keys.
E:Error in /tmp/update.zip
(Status 7)
Installation aborted.
What a F***ing nightmare...
Why do I apparently have the wrong version?
Hmm, might be the wrong OTA zip idd...
I downloaded mine from here: http://www.droid-life.com/2013/11/2...ial-update-for-nexus-7-2012-and-nexus-7-2013/
When I tried to update my rooted stock N7 to 4.4.2 from 4.4.0, the script always failed saying "debuggerd has unexpected content."
This is apparently a known issue revolving around stickmount. Unfortunately, I didn't have a replacement debuggerd and didnt' want to take the time to find and install the right one... So, if you need a quick list of things to do to get the update working (Used Windows 7)
Please note that
:
1) Download
the stock 4.4.0 image from https://developers.google.com/android/nexus/images#nakasi
the Android SDK bundle from here: https://developer.android.com/sdk/index.html
SuperSU from http://forum.xda-developers.com/showthread.php?t=1538053
The actual update file if you don't have it already (mine was already in /cache when I started down this road)
Install the Android SDK.
Run the Android SDK manager and make SURE you get the USB drivers.
Enable Android debugging on the N7 and plug it in via USB to the computer.
Once it fails to find a driver for one of the options, open the device manager.
Locate the "Nexus 7" in "other devices"
Right click and select "update driver"
Tell Windows to look in the ...\adt-bundle-windows-x86_64-20131030\sdk\extras\google\usb_driver directory
Once the driver is installed, open a command prompt and CD to the ...\adt-bundle-windows-x86_64-20131030\sdk\platform-tools directory
Run "adb devices"
You should get a prompt on the N7 asking for permission. Allow it.
You should see your device in the list.
put the SuperSU update file on the N7 by running:
adb push {downloadpath}\UPDATE-SuperSU-v1.80.zip /sdcard/
if needed, push the OTA file to the same place.
adb push {downloadpath}\{taht awfully long name} /sdcard/
run adb reboot bootloader
You should be in the bootloader.
Another device driver should install. After that "fastboot devices" should show your device.
Extract the 4.4 factory image to its own directory
Locate the "image-nakasi-krt16s.zip" file in the "nakasi-krt16s" subdirectory.
extract that .zip file to it's own directory
CD to that last directory in the command prompt
run fastboot flash-image system system.img
use the bootloader interface to boot into recovery
Flash the OTA file
Flash the SuperSU update
wipe cache and Dalvik
reboot normally.
In my case, I used TWRP and created a flash queue to flash both the OTA file and SuperSu. When I rebooted, everything came up. The first boot was a little long, and I got the normal post-OTA "Optimizing app n of 200" count.
I just take the OTA, unzip it, edit the update script and remove where it patches boot, recovery-from-boot, power.grouper.so, and in this case, debuggerd. Zip it back up, flash with twrp.
khaytsus said:
I just take the OTA, unzip it, edit the update script and remove where it patches boot, recovery-from-boot, power.grouper.so, and in this case, debuggerd. Zip it back up, flash with twrp.
Click to expand...
Click to collapse
Well, I'm not that up on editing update scripts. Then someone posts the factory image URLs.... That would have been SOOO much faster. That's how I got to 4.3. I used fastboot to flash the 4.3 system image....
Sent from my Nexus 7 using Tapatalk 4
khaytsus said:
I just take the OTA, unzip it, edit the update script and remove where it patches boot, recovery-from-boot, power.grouper.so, and in this case, debuggerd. Zip it back up, flash with twrp.
Click to expand...
Click to collapse
I have the zip, where is the script located?
Sent from my Nexus 7 using Tapatalk
redmonke255 said:
I have the zip, where is the script located?
Click to expand...
Click to collapse
./META-INF/com/google/android/updater-script
Remove every line related to power.grouper.so and LNX:5109760 (part partition reference). There's two of each, one apply_check_patch and one apply_patch plus a set_metadata for the power.grouper.so
I could put the file on Dropbox but I think it's more useful to see what's going on than just handing it out. As they say, give a man a fish and you'll feed him for a day. Teach a man to fish and he'll sit out in a boat drinking beer all day.
khaytsus said:
./META-INF/com/google/android/updater-script
Remove every line related to power.grouper.so and LNX:5109760 (part partition reference). There's two of each, one apply_check_patch and one apply_patch plus a set_metadata for the power.grouper.so
I could put the file on Dropbox but I think it's more useful to see what's going on than just handing it out. As they say, give a man a fish and you'll feed him for a day. Teach a man to fish and he'll sit out in a boat drinking beer all day.
Click to expand...
Click to collapse
That's good information. I know last time someone posted details exactly what lines in updater-script needs to be removed (i believe it was 4.3 OTA update). it would be wonderful if someone posts an updated updater-script here, so avoid any kind of other issues.
looking forward to see updater-script attached here!
bunch of thanks!!
small correction on command: run fastboot flash system system.img
in my case, I had to flash boot as well (wrong kernel I guess), otherwise TWRP was giving the emmc error, when flashing the OTA "emmc /dev/block/platform/msm_sdcc.1/by-name/boot 71"
I did fastboot flash boot boot.img
and then flashed the OTA in recovery, followed by SuperSU. And everything was back to normal, including xposed framework, which I had disabled prior to starting the OTA flashing.
I'm unable to unpate as of right now because I have TWRP recovery installed.
When I try to, it tells me " Package expects fingerprint of *original device fingerprint* this device has TWRP\Team_Win_Recovery_Proejct/ailsa_ii
Updater process ended with ERROR: 8
Error installing zip file '@/cache/recovery/block.map'"
I tried removing the part of the script that checks this, but then I got a different error (I don't remember what it was, it said something about "Boot:1826459185:1U57126581(Random numbers not the actual ones) contains unexpected content" or something like that
So I was wondering, how would I go and update to the new Android 7.0 update? (I also have the zip file of the update locally)
I would assume that I could flash stock recovery but a. I don't have the stock recovery.img, and b. I was reading around and someone mentioned that if I flashed stock recovery it'd delete all my data.
I'd be highly disappointed if the only way I could update to the 7.0 update is by deleting all my data. I'm sure there must be some way around it.
Can anyone help me out? I'm sure I'm not the only one that'll have this issue
EDIT: Flashed Recovery.img (Only recovery.img, via fastboot)
Results: Recovery is flashed and working.
Phone does boot up perfectly fine, no issues
Data is NOT lost.
Flashing the 7.0 update(A2017UV110B15) (Via stock recovery) [Remember to put it on your SDCard]:
Verifying update package...
Verified.
"EMC /dev/block/bootdevice/by-name/boot****load of numbers)" has unexpected contents
Aborted
Click to expand...
Click to collapse
( Same error as when I removed device verification.. maybe this is a user error and not a system/update error )
( Maybe I failed to download the update zip properly? I'll try the OTA update instead )
Downloading..
Rebooting..
Installing System Update...
Has unexpected contents
Package mixmatched
Aborted
Click to expand...
Click to collapse
( No, not a user error I suppose.. I don't know what is wrong then! This is odd )
System update failed
Reason: The system update package did not match the phone
Click to expand...
Click to collapse
And for the record, I am on A2017UV1.0.0B29
Andrew S.S. said:
I'm unable to unpate as of right now because I have TWRP recovery installed.
When I try to, it tells me " Package expects fingerprint of *original device fingerprint* this device has TWRP\Team_Win_Recovery_Proejct/ailsa_ii
Updater process ended with ERROR: 8
Error installing zip file '@/cache/recovery/block.map'"
I tried removing the part of the script that checks this, but then I got a different error (I don't remember what it was, it said something about "Boot:1826459185:1U57126581(Random numbers not the actual ones) contains unexpected content" or something like that
So I was wondering, how would I go and update to the new Android 7.0 update? (I also have the zip file of the update locally)
I would assume that I could flash stock recovery but a. I don't have the stock recovery.img, and b. I was reading around and someone mentioned that if I flashed stock recovery it'd delete all my data.
I'd be highly disappointed if the only way I could update to the 7.0 update is by deleting all my data. I'm sure there must be some way around it.
Can anyone help me out? I'm sure I'm not the only one that'll have this issue
Click to expand...
Click to collapse
Flashing stock recovery will not delete your data. Find your stock firmware download on the forum or zte, pull recovery.img from it and flash in twrp.
Of course those who whine about wiping data usually are the ones who need to do it most.
FYI I updated, flashed twrp and then restored data from my b29 backup without issue. At least this way you can make a new backup before attempting.
You can also wait for the flashable .zips to show up and avoid all the hassle.
lafester said:
Flashing stock recovery will not delete your data. Find your stock firmware download on the forum or zte, pull recovery.img from it and flash in twrp.
Of course those who whine about wiping data usually are the ones who need to do it most.
FYI I updated, flashed twrp and then restored data from my b29 backup without issue. At least this way you can make a new backup before attempting.
You can also wait for the flashable .zips to show up and avoid all the hassle.
Click to expand...
Click to collapse
Read my updated comment; Sorry that I didn't just edit the thread. And that makes sense. I think it would be wise for me to just wait.
First of all, flash rollback zip from DrakenFX.
Then update via OTA. That's all. I've done these steps yesterday and I'm using Nougat now.
WesTD said:
First of all, flash rollback zip from DrakenFX.
Then update via OTA. That's all. I've done these steps yesterday and I'm using Nougat now.
Click to expand...
Click to collapse
I saw your post then had forgotten about it til now ( haven't checked ) but in the last month I've forgotten where the rollback zip is located / what thread. Any help would be appreciated.
Only use ota if you don't want twrp/root anymore.
Andrew S.S. said:
I saw your post then had forgotten about it til now ( haven't checked ) but in the last month I've forgotten where the rollback zip is located / what thread. Any help would be appreciated.
Click to expand...
Click to collapse
Here you go; https://forum.xda-developers.com/showpost.php?p=68873482&postcount=2
Hi everyone,
Since Wileyfox didn't want to supply us with Recovery and Fastboot images, and the update has arrived to my phone already, I've captured the OTA link with Wireshark, so that anyone can update to Android 7.1.2.
INCREMENTAL UPDATE (OFFICIAL LINK) (DRIVE MIRROR LINK by me) (from TOS118C to TOS163B / from aa4d5d86bc to 8eec3af77b)
Just as I have commented earlier,
linuxct said:
If you directly click (the official download link), it will return an Error 404, but that is not true since the file actually exists... But requires a special HTTP header to be visible.
Since I wanted to grab the OTA link now that, for once, I finally got an OTA in this phone after always upgrading through fastboot images, I used wireshark to determine the server where it fetches it and the full file route. It turns out the header sends a special UA string as you can see in the picture attached: rsotaua 1.0, which is, most probably, a randomly generated string.
Now here's the thing: if you want to switch the UA you'll need an extension to do so. I've used this one. As soon as it's installed, go to the Options of the extension and add it like here:
Code:
WILEYFOX wfotaagent/2.3 Chrome Replace WF
Once the string is inserted, switch to it and hit the URL. The OTA should be downloadable now.
Click to expand...
Click to collapse
Please, note the UA string has changed from rsotaua 1.0 to wfotaagent/2.3, which makes a bit more sense. Enjoy!
Thank you!
Can I update my phone with the OTA-File with TWRP?
For me the OTA failed (probably because I rooted my device) and after a restart it asked me to download again.
Is there a chance to install this update using this file with fastboot, twrp or adb?
BTW, if you are using Linux (or any other OS providing wget, I have actually only used it for Linux so I'm not sure if it's available for other OS) you can easily download the package:
Code:
wget --user-agent="wfotaagent/2.3" LINK_TO_OTA_AS_I_HAVE_TO_REMOVE_TO_BE_ALLOWED_TO_POST_UNTIL_I_REMOVE_THE_LINK
I am currently downloading it although I don't know if it will be useful to me.
P.S. Omg, sending this comment already keeps me busy for minutes to figure out which scripts to allow to be able to send.
P.P.S Iframes are very ugly, requiring google services also.
P.P.S Having to do this Captcha game for a second third fourth time after it already recognized I'm not a robot makes me think my first post here will be my last...
P.P.P.S I'll try to temporarily switch of everything concerning security and privacy to get this post done as i spent so much time and will return to be a passive reader again.
Cappucinto said:
Thank you!
Can I update my phone with the OTA-File with TWRP?
Click to expand...
Click to collapse
mdosch said:
For me the OTA failed (probably because I rooted my device) and after a restart it asked me to download again.
Is there a chance to install this update using this file with fastboot, twrp or adb?
Click to expand...
Click to collapse
You will need to reflash AOSP's recovery in order to install this update, but please do note it's an accumulative patch, not a "Patching system image unconditionally" kind of installation. If the contents of the system partition, or the boot image (yes, that's for us magisk users out there) are unexpected, it will stop the update, and probably try to roll it back.
Recommendation: Reflash AOSP's recovery, then the System image from TOS118C (I can provide those if needed), and then apply the update.
mdosch said:
P.S. Omg, sending this comment already keeps me busy for minutes to figure out which scripts to allow to be able to send.
P.P.S Iframes are very ugly, requiring google services also.
P.P.S Having to do this Captcha game for a second third fourth time after it already recognized I'm not a robot makes me think my first post here will be my last...
P.P.P.S I'll try to temporarily switch of everything concerning security and privacy to get this post done as i spent so much time and will return to be a passive reader again.
Click to expand...
Click to collapse
It's sad that XDA does that to junior members, tbh. With ten posts they'll remove all those restrictions, though. At least to me, it'd feel bad losing the interest of advanced users that might be new to the forum, yet are experienced in the topic.
linuxct said:
Since Wileyfox didn't want to supply us with Recovery and Fastboot images
Click to expand...
Click to collapse
I'm guessing they will release those eventually, right?
linuxct said:
Recommendation: Reflash AOSP's recovery, then the System image from TOS118C (I can provide those if needed), and then apply the update.
Click to expand...
Click to collapse
Hi can I have a link to the AOSP recovery please
Ok, I'll give this site a new try using a temporary fresh profile to not have to spoil my browsers settings.
After some playing around I got 7.1.2 installed and rooted. I'll write down what I did to get it finally work, but YMMV so be aware you might brick your phone.
I was using Debian 9 with fastboot and adb installed.
The steps I did:
Download and unzip the fastboot image from this thread: https://forum.xda-developers.com/swift-2/how-to/marmite-android-7-1-1-tos118c-fastboot-t3605101
Code:
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
Boot to stock recovery and choose "apply update from adb"
Code:
adb sideload wf-marmite-aa4d5d86bc-to-8eec3af77b-signed.zip
After successful install wipe cache and dalvik/arts cache and reboot to system with the following command:
Code:
adb reboot "dm-verity enforcing"
When the update is configured let the phone switched on for a while (I don't know why, but it ended in a bootloop and I had to start again when I instantly rebooted)
After a while boot to bootloader.
Boot (not flash) twrp: http://twrp.me/devices/wileyfoxswift2.html
Code:
fastboot boot twrp-3.1.1-0-marmite.img
Go to "ADB -> Sideload" and install Superuser: https://forum.xda-developers.com/android/software-hacking/wip-selinux-capable-superuser-t3216394
Code:
adb sideload superuser.zip
Wipe cache and dalvik/arts cache and finally reboot with this command:
Code:
adb reboot "dm-verity enforcing"
I am not 100% sure if all steps are necessary but finally this worked for me and I am enjoying an up-to-date OS without loosing root.
I've downloaded the update as my 2X still hasn't updated.
I just cant get it to update via the recovery, my phone is default, no mods. I go to update from SD and it just errors with failed to mount SD. Even tried another SD card, same issue.
Am I missing something here? Cant be anything extra needed surely?
linuxct said:
I've captured the OTA link with Wireshark, so that anyone can update to Android 7.1.2.
Click to expand...
Click to collapse
Hello,
How did you get Wireshark to capture your phone's traffic? Did you use MITM or do I have to tweak my linux to make this work?
I tried searching online, but those didn't work for me.
boa05 said:
Hello,
How did you get Wireshark to capture your phone's traffic? Did you use MITM or do I have to tweak my linux to make this work?
I tried searching online, but those didn't work for me.
Click to expand...
Click to collapse
I put my windows pc in router mode using the wifi adapter, and ethernet bringing internet connection. Then it was as easy as capturing just that traffic.
Deleted due to development of Android ROM version