Hi, I have a Nexus 7 2012 wifi nakasi & my 5.1.1 OTA just landed. As my Nexus is rooted using CF-auto-root & had a TWRP 2.8.5.1 recovery flashed, I fastboot flashed the recovery.img from the 5.1.0 archive & then clicked the button to install the OTA.
It gets half way through, then just says "error". How do I get it to be more informative & could I fix it by just flashing the system partition from my 5.1.0 archive before running the OTA, then re-rooting & re-flashing TWRP?
Thanks
Had the same issue.... Just flashed the update without wiping the use info, so far seems to have worked... Not yet noticing much improvement though so don't get to excited.... Will keep watching it to see if it still crashes in sleep mode whilst sitting in the desk doc/charger...
Sent from my Nexus 7 using XDA Free mobile app
---------- Post added at 07:40 AM ---------- Previous post was at 07:32 AM ----------
Update: loads of system & none system apps still hanging and force closing some without the usual report/wait/OK option
So far:
- Google map
- Android System
- Facebook
- BBC iPlayer
- Chrome
Probably worth a full wipe and re flash to remove any gremlins.....
Sent from my Nexus 7 using XDA Free mobile app
FIXED
JustinSB said:
It gets half way through, then just says "error". How do I get it to be more informative & could I fix it by just flashing the system partition from my 5.1.0 archive before running the OTA, then re-rooting & re-flashing TWRP?
Click to expand...
Click to collapse
I just flashed the system.img from my 5.1.0 archive (the recovery had already been flashed from the first time I tried it), waited half an hour for the OTA to flag up again & it all worked perfectly & upgraded exactly as it should. I haven't tried to root it again yet, as I want to see if it makes a difference.
So that's it, if your Nexus 7 2012 wifi won't let you install the 5.1.1 OTA, flash system.img & recovery.img from the 5.1.0 archive & you will be good to go, with all of your existing software, settings & data still intact. Naturally, you will need to re-root it though.
I flashed the 5.1.1 recovery, boot, and system images and then did a full wipe in recovery. Upon booting into the system, I was offered to restore my previous apps and data which all worked well but took a while to download and install the apps. I had to spend some time setting up the screens but 5.1.1 is running very well (better than 5.1) and I've since flashed twrp to get root. I do believe the wipe is important to get the best performance from the update.
I agree with the poster above me. Not wiping the device, cobbling together some unapproved update scheme pulled out of your ass, then complaining the performance sucks is just plain stupid. Do it right, and it will run butter smooth. But hey, I'm perfectly OK with snapping up several N7's DIRT CHEAP when all the idiots who can't follow instructions start dumping them on eBay and Craigslist thinking they're "broken". I have two cars that could use an in-dash install.
JustinSB said:
Hi, I have a Nexus 7 2012 wifi nakasi & my 5.1.1 OTA just landed. As my Nexus is rooted using CF-auto-root & had a TWRP 2.8.5.1 recovery flashed, I fastboot flashed the recovery.img from the 5.1.0 archive & then clicked the button to install the OTA.
It gets half way through, then just says "error". How do I get it to be more informative & could I fix it by just flashing the system partition from my 5.1.0 archive before running the OTA, then re-rooting & re-flashing TWRP?
Thanks
Click to expand...
Click to collapse
JustinSB,
Since you've already flashed your ROM's stock recovery, I *think* the problem you're encountering is the same one I had when I moved from 5.0.1 to 5.1: The rooting procedure you're using installs a non-stock kernel, which resides in the boot.img partition and is detected in the pre-flash checking phase of things in the OTA update.
If it were me, and I wanted to save a significant amount of time on the update (i.e. keep my userdata and bootloader partitions the same), I'd download the 5.1.1 image archive, uncompress/untar/unzip all the archives, and do the steps outlined here. They involve wiping the cache, recovery, boot, and system partitions and flashing the latter three with the updated images. Definitely do not fail to do any of those steps. Fwiw, and as I note later in that thread, I didn't re-flash the bootloader as it's the same in both ROMs.
All I did to finalize things was to boot to twrp via fastboot and generate a Nandroid back up, and then re-root using the CF-Auto-Root procedure. Afterwards I was set and experienced no particular system slowdowns. The whole process took about 15 minutes, including waiting for the dalvik-cache to reinitialize. I typically do not flash twrp, I just boot to it from fastboot as needed.
As a poster has pointed out in his non-diplomatic way, this is not the recommended path to updating, so if you encounter problems going this route, you can always do the full reset thing and re-load all of your userdata from a back up as a second option.
Which ever path you decide to follow, I wish you good luck.
cheers,
john
Well, I guess I'm going to do the unthinkable and reply to my own post to say that I've just followed the procedure I described above, this time to update from 5.1 to 5.1.1. It also took a total of 15 minutes with the longest portion of that time taken by the dalvik-cache reinitializing during the first reboot.
Good luck to you, OP. I hope that you upgrade goes as smoothly.
cheers,
john
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.
This morning I was able to update my rooted phone to OK4 from OD3 keeping root and my Knox counter at 0 using metalfan78's [ROM]OK4 Stock Rooted Zip, and stock partitions from the full tar. I was able to use Flashfire to create the stok partitions tar and flash them via Odin. I did this based on another thread I followed to update to OD3 to keep root and Knox at 0 a while back. So far everything seems to be working good for me, I dirty flashed and everything seems to have gone like taking an OTA update.
I got the ROM here and used the odexed version:
http://forum.xda-developers.com/spr...rom-ok4-stock-rooted-zips-12-16-2015-t3272692
Stock partitions file is save to my google drive here, it contains everything from the full tar except the system and cache (not sure how well sharing like this will work):
https://drive.google.com/file/d/0Bw7_CzqViQzSSGZHSE1TS3loN1E/view?usp=sharing
Followed the instructions for the update to OD3 here:
http://forum.xda-developers.com/spr...w-to-update-to-g900pod3-5-0-keeproot-t3136932
Hopefully this will help someone get updated, or just provide stock partitions for other use.
If Knox is already tripped this probably isn't worth the effort
You MUST be rooted already for this to work.
Edit:
1. After a couple hours S Health stopped working about every 5 seconds, making it difficult to do anything. Clearing the data and signing back in seems to have fixed it.
2. Play store continuously fails to download app updates on WiFi or Mobil data.
3. Wiped and reinstalled the ROM with Flashfire on Jan 1. I have not had any issues since.
Thank ya for this post, it has actually been a while since I have updated my phone. I haven't had any issues with any of the apps thus far. It's been a little over 24 hours since I've updated. Also, I think my phone runs a lot smoother with the update than it use to. Also, I don't have any issues with the play store updating. I'll post issues if any occurs.
dave011182 said:
This morning I was able to update my rooted phone to OK4 from OD3 keeping root and my Knox counter at 0 using metalfan78's [ROM]OK4 Stock Rooted Zip, and stock partitions from the full tar. I was able to use Flashfire to create the stok partitions tar and flash them via Odin. I did this based on another thread I followed to update to OD3 to keep root and Knox at 0 a while back. So far everything seems to be working good for me, I dirty flashed and everything seems to have gone like taking an OTA update.
I got the ROM here and used the odexed version:
http://forum.xda-developers.com/spr...rom-ok4-stock-rooted-zips-12-16-2015-t3272692
Stock partitions file is save to my google drive here, it contains everything from the full tar except the system and cache (not sure how well sharing like this will work):
https://drive.google.com/file/d/0Bw7_CzqViQzSSGZHSE1TS3loN1E/view?usp=sharing
Followed the instructions for the update to OD3 here:
http://forum.xda-developers.com/spr...w-to-update-to-g900pod3-5-0-keeproot-t3136932
Hopefully this will help someone get updated, or just provide stock partitions for other use.
If Knox is already tripped this probably isn't worth the effort
You MUST be rooted already for this to work.
Edit:
1. After a couple hours S Health stopped working about every 5 seconds, making it difficult to do anything. Clearing the data and signing back in seems to have fixed it.
2. Play store continuously fails to download app updates on WiFi or Mobil data.
3. Wiped and reinstalled the ROM with Flashfire on Jan 1. I have not had any issues since.
Click to expand...
Click to collapse
I followed your instructions and everything went smoothly, but at least once a day I get a message saying: "Device must restart. Device will restart in 25 seconds.". Do you get this? Any suggestions on how to stop it from happening?
IMBigWillie said:
I followed your instructions and everything went smoothly, but at least once a day I get a message saying: "Device must restart. Device will restart in 25 seconds.". Do you get this? Any suggestions on how to stop it from happening?
Click to expand...
Click to collapse
Sorry for my delayed response.
I was having a random system reboot, and assumed it was from my bad habit of dirty flashing. I think what ultimately fixed it for me was using flashfire to flash the stock tar(as far as it recommended) and inject root. Metalfan recommend flashing via Oden and rooting before installing his rom, but that would have tripped kmix for sure. After flashing the stock tar via flashfire I had no data even on WiFi. I flashed Metalfan's rom to get me working again quickly and haven't had any random reboot issues recently. My knox counter is still at 0.
I'm sure I should recommend wiping data in this process but that's up to you. I can't say for sure that I did, then restored backed up data or not. I was pressed for time that morning, and needed my phone working.
dave011182 said:
Sorry for my delayed response.
I was having a random system reboot, and assumed it was from my bad habit of dirty flashing. I think what ultimately fixed it for me was using flashfire to flash the stock tar(as far as it recommended) and inject root. Metalfan recommend flashing via Oden and rooting before installing his rom, but that would have tripped kmix for sure. After flashing the stock tar via flashfire I had no data even on WiFi. I flashed Metalfan's rom to get me working again quickly and haven't had any random reboot issues recently. My knox counter is still at 0.
I'm sure I should recommend wiping data in this process but that's up to you. I can't say for sure that I did, then restored backed up data or not. I was pressed for time that morning, and needed my phone working.
Click to expand...
Click to collapse
Thanks for getting back so soon! I actually did a clean flash and still am having the issue ... I will definitely try your method tonight!
IMBigWillie said:
Thanks for getting back so soon! I actually did a clean flash and still am having the issue ... I will definitely try your method tonight!
Click to expand...
Click to collapse
You may also want to try using flashfire to create your own stock partitions tar to flash in this process to be sure my file on drive isn't somehow corrupted. If you used it in the first place. Use the flash firmware package option, wait for it to read the file partitions, then the download icon to create your partitions file. Use what's highlighted by default, create your file, and transfer it to your computer. Flash what is selected by default from the tar and reboot into download mode to flash the partitions file just created.
If all you want is stock root and your data works you shouldn't need to flash anything else at that point.
Two again - MMB30K & MOB30O. I have no idea what the difference is, but I've used MOB30O successfully.
Link to the Nexus 6 OTA page with instructions for sideloading (no data loss, need to reinstall TWRP & reroot):
https://developers.google.com/android/nexus/ota
For those people who prefer to install separate components:
MMB30K
MOB30O
dahawthorne said:
Two again - MMB30K & MOB30O.
Click to expand...
Click to collapse
Did anyone ever figure out what the difference was? Google did this last time, and the result seemed the same between the two.
I went with MOB30M last time and it worked fine, so I'm going with MOB30O.
@dahawthorne added the links on the first post for you..
Thanks. I should have included the links, but I reckoned that anyone who's interested knows where to find them, and anyone who doesn't know probably shouldn't be tinkering...
But yes, the pointer is appreciated.
Edit: I used the OTA at this link - simpler, and doesn't lose your data:
https://developers.google.com/android/nexus/ota#shamu
Instructions are on the page. A simple sideload, flash recovery, install SuperSU.
Sir , is there any difference between MMB30K and MOB30O versions?
marcus droid said:
Sir , is there any difference between MMB30K and MOB30O versions?
Click to expand...
Click to collapse
we have to wait for the AOSP change logs on that
Encrytable boot/kernel IMGs:
MOB30O:
https://www.androidfilehost.com/?fid=24572369242688110
MMB30K:
https://www.androidfilehost.com/?fid=24572369242688111
What was the difference between the last 2 images? That was released without explanation as well!
I flashed the MOB30O version, anyone having trouble flashing SuperSU like me?
SuperSU flashed alright in TWRP(though the log seems a bit shorter than usual). When I rebooted the system, it says that SuperSU binary is not installed. I've tried to reflash TWRP (since stock recovery takes over) & different versions of SuperSU: 2.74 / 2.76 and can't seem to get root.
Strange. I sideloaded the MOB30O OTA, flashed TWRP (twice - it didn't stick first time) then installed SuperSU 2.76 from TWRP. No problems at all so far.
ayang02 said:
I flashed the MOB30O version, anyone having trouble flashing SuperSU like me?
SuperSU flashed alright in TWRP(though the log seems a bit shorter than usual). When I rebooted the system, it says that SuperSU binary is not installed. I've tried to reflash TWRP (since stock recovery takes over) & different versions of SuperSU: 2.74 / 2.76 and can't seem to get root.
Click to expand...
Click to collapse
I flashed SuperSU 2.76 just fine after flashing the MOB30O image. Also, I've never had stock recovery get replaced on my Nexus 6 ever. That's really strange.
The difference between these two images has been posted many times - not sure why people are confused about it!
MOB is the version you want.
MMB is the version for the Carriers who haven't approved the newer radio in MOB.
MOB also includes some kernel enhancements to increase performance. These changes related to the Kernel "Tick Rate". I think the changes have improved performance a little, but you're not going to think you've purchased a new phone or anything.
Summary:
MOB: Newer kernel with performance improvements, updated Radio image.
MMB: Older kernel sans performance improvements, old radio.
Summary: MOB is the train you want to be on.
ayang02 said:
I flashed the MOB30O version, anyone having trouble flashing SuperSU like me?
SuperSU flashed alright in TWRP(though the log seems a bit shorter than usual). When I rebooted the system, it says that SuperSU binary is not installed. I've tried to reflash TWRP (since stock recovery takes over) & different versions of SuperSU: 2.74 / 2.76 and can't seem to get root.
Click to expand...
Click to collapse
I dl'd the O image, extracted and flashed the system image only through twrp while at work. Rooted using a PC when I got home and I have no issues so fah. I use chainfires method and his method requires running his image with fast boot. Fastboot boot cf... What ever you have the file named. It'll do it's thing on the phone then reboot 1-3x before it boots up fully. This root it rebooted once. On previous updates, up to 3 times before it finally finished.
Why are people insisting on flashing the "old" modular way (extracting components for individual flashing) when Google have provided a total no-data-loss OTA? 15 minutes, risk-free. Why choose the difficult way when there's a seamless simple upgrade? Incomprehensible.
dahawthorne said:
Why are people insisting on flashing the "old" modular way (extracting components for individual flashing) when Google have provided a total no-data-loss OTA? 15 minutes, risk-free. Why choose the difficult way when there's a seamless simple upgrade? Incomprehensible.
Click to expand...
Click to collapse
For me it's because I've lost my data a couple of times in the past doing an OTA update. I guess old habits die hard and I like the control I have flashing each image file manually. At least that way I can be reasonably sure that my data isn't messed with by not flashing the userdata image, plus, I can skip flashing recovery so I don't have to reinstall that. It only took me 9 minutes to complete the process tonight, including re-rooting, doing it the "old" way.
dahawthorne said:
Why are people insisting on flashing the "old" modular way (extracting components for individual flashing) when Google have provided a total no-data-loss OTA? 15 minutes, risk-free. Why choose the difficult way when there's a seamless simple upgrade? Incomprehensible.
Click to expand...
Click to collapse
Two very simple reasons. 1) if you are rooted. 2) if you are unencrypted.
FWIW: it takes about 60 seconds to extract the images from the .zip file. And about 3 minutes to flash the boot and system image files in fastboot.
before i download the entire package can anyone tell me if there is a new modem in july update?
H4X0R46 said:
I flashed SuperSU 2.76 just fine after flashing the MOB30O image. Also, I've never had stock recovery get replaced on my Nexus 6 ever. That's really strange.
Click to expand...
Click to collapse
Then that means you were able to get root successfully. My TWRP recovery got overwritten because I didn't get root. Anyways, I am gonna try flashing stuff from scratch in a few days. I've also never had issues flashing monthly updates and SuperSU until now.
Sent from my Nexus 6 using XDA Free mobile app
adm1jtg said:
before i download the entire package can anyone tell me if there is a new modem in july update?
Click to expand...
Click to collapse
There is no new modem, nor bootloader. Just security updates to boot and system images.
Any ideas?
Im rooted, the update downloads and appears to install but then reboots and its back to where it was, not installed.
Same for me. I did a factory reset and tried to install it again. Same thing.. It just stalls and reboots. Guess I am lucky it don't freeze there at least.. Thought I'd mention that factory reset don't help. That way it will save u the trouble.. I guess I am going to lock the bootloader and try again... I'll let u know how that works... It shouldn't matter though... All prev. Updates went fine with unlocked bootloader.. I just had to reinstall root after update...
Essentially though... I'm pissed at the moment cause I factory reset for Nada.. :/
Going through the same loops now trying second time now but I'm not rooted ... May have TWRP installed though but I don't think so as last time I updated I didn't bother rooting
I don't have twrp installed on mine but it was rooted. Not now after factory reset... My bootloader is unlocked though... I was going to try relocking it and try again but at this point I'm just like... Screw it
I don't think its the issue anyways as I have updated before with it unlocked.
When rooted before, I just booted the twrp image. It seemed the safest approach and worked just fine that way for installing su.. And that's basically all I needed twrp for so...
I'm sure they will fix it or get to the bottom of it.. It seems to be an issue for some people on geforce forums, here and redit
If anyone finds a solution please post here
I am in the same boat. Unlocked bootloader, rooted, but recovery is stock. The only other thing I did was flash a kernel for USB TV tuner support.
https://forums.geforce.com/default/...ficial-usb-tv-tuner-support-to-live-channels/
But I don't think it's related. And just like the rest of you I have never had an issue taking an update. This update goes through the usual process, then reboots, but it just reboots to the same version.
I suspect we'll need to wait for nvidia to post the full firmware on their developer site, so we can flash it via fastboot. Rooting modifies the system partition and is probably why the OTA won't take.
I have not flashed a kernal to mine so I'd rule the kernal out as well. Stock recovery as well
I seen somewhere else its an issue with root. Perhaps so a root removal then try... I factory reset and no dice... Maybe I'll try rerooting and then remove root... Then try installing
bradleyw801 said:
I am in the same boat. Unlocked bootloader, rooted, but recovery is stock. The only other thing I did was flash a kernel for USB TV tuner support.
https://forums.geforce.com/default/...ficial-usb-tv-tuner-support-to-live-channels/
But I don't think it's related. And just like the rest of you I have never had an issue taking an update. This update goes through the usual process, then reboots, but it just reboots to the same version.
Click to expand...
Click to collapse
Same boat, downloads but will not install, I am rooted
Confirmed on the official forum that ota update won't work on root. Firmware available on nvidia developer site in about a week
adam_ky said:
I seen somewhere else its an issue with root. Perhaps so a root removal then try... I factory reset and no dice... Maybe I'll try rerooting and then remove root... Then try installing
Click to expand...
Click to collapse
Don't waste your time, it won't work. I did unroot, then updated and after reboot same pop up coming upgrade notification. Then I did factory reset, updated and after reboot same pop up coming upgrade notification.
aankkurr said:
Don't waste your time, it won't work. I did unroot, then updated and after reboot same pop up coming upgrade notification. Then I did factory reset, updated and after reboot same pop up coming upgrade notification.
Click to expand...
Click to collapse
I'm stock everything and also got loops last night, then just gave up.
I'll add to your list... Don't install stock recovery images either.
I followed accompanied directions to a T. I tried to flash stock 5.1 on top of 5.1. Everything flashed fine, no errors. But upon reboot from flash, shield is dead. No green lights, no boot.
My theory is its an indicator that something is wrong with your shield if it won't take the update..
Some faulty hardware or something perhaps..
Luckily I'm still under warranty and got a replacement coming. Just be careful.
The fail of the update is not strictly related to root. But logically you need a stock firmware to install the update, without root.
Nvidia pushed a progessive update and you need the stock boot.img system.img vendor.img recovery.img to install the 5.2 update
I have two Shield TV 16GB 2015 and a Shield TV 16GB 2017
on the two 2015 models, i reinstalled the stock 5.1 firmware ( all stock ) and i started the update.
on one shield tv the update fail, while on the other the update went well.
the progressive update ( this is the first time that Nvidia published a progressive update ) fail if your internal sdcard have some bad sectors. Can be the only explaination.
To solve we need soon the 5.2 stock complete recovery image.
For the Shield TV 2017 model the update went well, but after the 5.2 update TWRP not work anymore. Therefore you can't do almost nothing.
TWRP instead work on the 2015 model with the last 5.2 firmware.
Yep. Nvidia said they'd post the full 5.2 image in a week or so. Until then we twiddle our thumbs.
Before I got the preview update for 5.2 I was rooted with the kernel that allowed USB TV tuner.
I flashed factory 5.1 image, locked bootloader and once Shield booted back up I did a factory reset since I was still getting the warning about my bootloader being unlocked. After factory reset I no longer had warning and the update went smooth.
This is on 2017 16GB Shield.
The progressive update needs to be undone.... That was a stupid move and looks to have caused tons of problems. The last update to 5.1 I did while rooted.... I don't see the issue... But like I said in my experience... I don't think it was my core issue.. I flashed all the stock 5.1 images and it killed my shield... I would say that some other problem was lurking in the background on my particular device.. But they are sending me a new one... So all is good
Well, I have the 2015 16gb model. I had it with custom ROM (full Android nougat), stock recovery and rooted with SuperSU.
I also had that loop when attempting to upgrade to 5.2, the install would get stuck at the same spot each time I tried and then device rebooted​ automatically afterwards without upgrading, but that's because I forgot to flash stock boot.img to completely remove root, once I did the upgrade installed successfully.
What I did in fastboot to go back to stock 5.1 was:
fastboot flash system system.img
fastboot flash vendor vendor.img
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot -w (very important)
fastboot reboot
* Word of advice Do Not Use flash-all.bat * Flash manually running each command and preferably do a clean install.
Note i didn't flash the bootloader (blob file) as there was no need plus it is a sensitive file which can hard brick your device if wrongly flashed or corrupted.
Also the bootloader version hasn't changed so no update on that matter.
Sent from my Tapatalk beta Hub
If I helped hit the Thanks button. Follow Me! ~ DroidMote user ~ Full Android for Shield TV and Nexus Player
unrooted 2015 16gb here. still can't update. Hell, i can't even restore the factory image since it tells me that the data is too large for system.img and vendor.img. Anyone ever see that?
---------- Post added at 04:15 PM ---------- Previous post was at 03:54 PM ----------
not rooted, still won't install
pendragon666 said:
unrooted 2015 16gb here. still can't update. Hell, i can't even restore the factory image since it tells me that the data is too large for system.img and vendor.img. Anyone ever see that?
---------- Post added at 04:15 PM ---------- Previous post was at 03:54 PM ----------
not rooted, still won't install
Click to expand...
Click to collapse
Yeah, the shield is picky. Just try with other usb cables and/or other usb port in your PC, preferably usb 2.0 as some 3.0 can cause interference.
I myself have flashed on Windows 10 x64 with stock usb cable and usb 2.0 and 3.0 ports on my devices without issues but it is well known what i mentioned above, those tips most of the times help. I remember a user that even formatted his Windows laptop and then finally he could install drivers and flash.
Sent from my Tapatalk beta Hub
If I helped hit the Thanks button. Follow Me! ~ DroidMote user ~ Full Android for Shield TV and Nexus Player
Hello all,
Been a LONG while since I've actively played around with rooting and unlocking an android device. I finally "upgraded" from my very aged Galaxy S4 to the Moto E4 XT1768. I have successfully unlocked the bootloader, got TWRP installed, rooted with Magisk, and gotten Xposed installed with my favorite modules.
This morning, I got a prompt that a new security update is available, and like a noob, I tried to take the update. This resulted in me getting stuck in a loop where the phone only wanted to boot into TWRP. I got that fixed thanks to XDA, got the pending and failing update completely cleared and am booted back into the device normally, and have frozen the moto update service.... but now...
Is there a way without completely flashing back to stock rom? I know how to take titanium or nand/twrp backups, but I feel like this would still be hours of work to go back to stock, flash, re-root restore all apps blah blah. what are the chances of there being a dirty-flashable zip put out at this point?
The way I normally do these type of upgrades is to download the firmware (from here), use fastboot commands to wipe (erase) and flash the needed partitions (everything but data and recovery), boot to TWRP - flash the no-verity-opt-encrypt.zip & root, and then reboot to system - done. It's easy enough for me, but I know some prefer to being able to use a flashable zip in TWRP.
Also, I have to ask - did you get your e4 cheap? It's was replaced by the e5, some other phones seem to be getting replaced like the G6 series (it's gone on clearance at some places), so they can be had cheap.
bast525 said:
Hello all,
Been a LONG while since I've actively played around with rooting and unlocking an android device. I finally "upgraded" from my very aged Galaxy S4 to the Moto E4 XT1768. I have successfully unlocked the bootloader, got TWRP installed, rooted with Magisk, and gotten Xposed installed with my favorite modules.
This morning, I got a prompt that a new security update is available, and like a noob, I tried to take the update. This resulted in me getting stuck in a loop where the phone only wanted to boot into TWRP. I got that fixed thanks to XDA, got the pending and failing update completely cleared and am booted back into the device normally, and have frozen the moto update service.... but now...
Is there a way without completely flashing back to stock rom? I know how to take titanium or nand/twrp backups, but I feel like this would still be hours of work to go back to stock, flash, re-root restore all apps blah blah. what are the chances of there being a dirty-flashable zip put out at this point?
Click to expand...
Click to collapse
Flashing back to stock and taking the updates is really the best way. Unless you can find a complete firmware package of the new update which of course takes back to stock as well. Really the only way to do it. @MotoJunkie01 makes some TWRP flashable stock roms. And he also creates the partition updater which updates your oem partition and other important things that can't be done in the Twrp flashable stock ROM.
madbat99 said:
Flashing back to stock and taking me updates is really the best way. Unless you can find a complete firmware package of the new update which of course takes back to stock as well. Really the only way to do it. @MotoJunkie01 makes some TWRP flashable stock roms. And he also creates the partition updater which updates your oem partition and other important things that can't be done in the Twrp flashable stock ROM.
Click to expand...
Click to collapse
Speaking of that, @ALI12 just posted a stock firmware package for the NCQS26.69-64-10 build. He gave me approval to use it to update my firmware thread to the latest build, so I'll be updating that OP shortly.
MotoJunkie01 said:
Speaking of that, @ALI12 just posted a stock firmware package for the NCQS26.69-64-10 build. He gave me approval to use it to update my firmware thread to the latest build, so I'll be updating that OP shortly.
Click to expand...
Click to collapse
This will be for the XT1766, correct? Or will same build work for XT1768 (me thinks not)?
So what would the easiest/quickest way be to get updated with all of my apps and data intact? Twrp backup of data partition? Or would there be any way to do this without wiping data at all?
bast525 said:
So what would the easiest/quickest way be to get updated with all of my apps and data intact? Twrp backup of data partition? Or would there be any way to do this without wiping data at all?
Click to expand...
Click to collapse
If you're going to slash a firmware package you'll want to wipe everything. Especially data. Make a backup of your data first of course. After you flash TWR P you can try restoring your data and see if everything comes back. but everything in your downloads folder and all of that will be gone once you format data to remove encryption again.