I'm having issues flashing factory images for 5.1.0 LMY47D & LMY47E (tried both) from my ubuntu box. Every time I try these images, I see this:
Code:
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
and then end up with:
Code:
sending 'system' (1736396 KB)...
(bootloader) Data size exceeds download buffer
FAILED (remote failure)
Boot loader on "Device is UNLOCKED Status Code: 3" and I've updated fastboot to the best of my knowledge, using Android Studio SDK Manager, as well as ran apt-get update. Bootloader version is moto-apq8084-71.08. I did an md5sum on the .tgz files and confirmed I'm not getting a bad download on either. After extracting I removed the -w from
Code:
fastboot -w update image-shamu-LMY47D.zip
in the flash-all.sh file, really would rather not wipe, but if someone tells me there's a valid reason I need to, I'll do it. I do not have encryption turned off.
This leaves my phone in an unusable state due to the partial flash, so I'm about to FDR it, but was hoping someone could help first.
Have you tried flashing each image manually?
jfcooley said:
Have you tried flashing each image manually?
Click to expand...
Click to collapse
That was a good idea, just tried it. no dice:
Code:
****@Ubuntu-Media:~/Downloads/shamu-lmy47e$ fastboot flash system system.img
sending 'system' (1736380 KB)...
(bootloader) Data size exceeds download buffer
FAILED (remote failure)
I just read something about how I might need to use mFastboot made by motorola... trying that now
You have to unzip. Fastboot flashes IMG.
When you download the factory image you unzip, should leave you with 2 image files and another .zip. You have to unzip that as well. It contains the rest of the img you need to manually flash.
jfcooley said:
You have to unzip. Fastboot flashes IMG.
When you download the factory image you unzip, should leave you with 2 image files and another .zip. You have to unzip that as well. It contains the rest of the img you need to manually flash.
Click to expand...
Click to collapse
yeah, sorry realized that seconds after I posted... edited my original post, sorry for thread confusion.
So after a few other mistakes I'd rather not own up to, I figured out that yes, mFastBoot was the solution to my issue. I'm not sure why I can't find any other folks posting about needing it for 5.1 builds on the the N6, but I did. I never needed it before 5.1, but I'm assuming the system.img file has grown larger than the standard SDK fastboot supports. I'm wondering if this is only an issue when flashing from linux. Theoretically, it should not be though; this issue is based on the memory available on the device (tmo N6, btw).
For those that don't know, "mFastboot" aka Motorola Fastboot is a tweaked version of fastboot provided by Motorola. It will actually split up the image and flash it in pieces.
Here are Instruction for installing and using mFastBoot to flash a Moto G on linux, but the process is the same, except for the images obviously. You'll have to either modify the flash-all.sh file or do each of the images manually.
Hope this helps someone else... it would be really weird if I'm the only one that runs into this.
GoldPaintedLemons said:
So after a few other mistakes I'd rather not own up to, I figured out that yes, mFastBoot was the solution to my issue. I'm not sure why I can't find any other folks posting about needing it for 5.1 builds on the the N6, but I did. I never needed it before 5.1, but I'm assuming the system.img file has grown larger than the standard SDK fastboot supports. I'm wondering if this is only an issue when flashing from linux. Theoretically, it should not be though; this issue is based on the memory available on the device (tmo N6, btw).
For those that don't know, "mFastboot" aka Motorola Fastboot is a tweaked version of fastboot provided by Motorola. It will actually split up the image and flash it in pieces.
Here are Instruction for installing and using mFastBoot to flash a Moto G on linux, but the process is the same, except for the images obviously. You'll have to either modify the flash-all.sh file or do each of the images manually.
Hope this helps someone else... it would be really weird if I'm the only one that runs into this.
Click to expand...
Click to collapse
just fyi, fastboot works fine with all the factory images google puts online but you have to use the latest version. it's available as part of the Android sdk and is included with Android studio.
PhilDX said:
just fyi, fastboot works fine with all the factory images google puts online but you have to use the latest version. it's available as part of the Android sdk and is included with Android studio.
Click to expand...
Click to collapse
Thanks, but if you read my original post you'll see I did that and more. Not saying you're wrong, but unless someone can tell me specifically a step in that process I apparently missed, I think there might be exceptions to that rule.
GoldPaintedLemons said:
Thanks, but if you read my original post you'll see I did that and more. Not saying you're wrong, but unless someone can tell me specifically a step in that process I apparently missed, I think there might be exceptions to that rule.
Click to expand...
Click to collapse
guilty as charged
I see now that you're on Linux, I use a Windows box so that's probably the difference. glad to see you found a solution.
GoldPaintedLemons said:
Thanks, but if you read my original post you'll see I did that and more. Not saying you're wrong, but unless someone can tell me specifically a step in that process I apparently missed, I think there might be exceptions to that rule.
Click to expand...
Click to collapse
On Windows with virtually the exact same issue. I went back to 5.0.1 but the bootloader is stuck on the newer version and can not be modified. I do not use ADB manually anymore. I use toolkits these days and then try manually. Now I'm stuck on 5.0.1 and can not update the OS at all. I get some message when attempting to ADB-Sideload the 5.1m T-Mo OTA saying that "a file located at dev/block/msm.... Has been changed to R/W. Reflash and reboot to regain OTA privilege."
Only issue is I am on a LRX22C Factory Image with Stock recovery. Any help or questions will be welcomed.
PhilDX said:
guilty as charged
I see now that you're on Linux, I use a Windows box so that's probably the difference. glad to see you found a solution.
Click to expand...
Click to collapse
Google images flash perfectly fine in Linux with fastboot.
Sent from my Nexus 6 using XDA Free mobile app
Freshly_Snipes said:
On Windows with virtually the exact same issue. I went back to 5.0.1 but the bootloader is stuck on the newer version and can not be modified. I do not use ADB manually anymore. I use toolkits these days and then try manually. Now I'm stuck on 5.0.1 and can not update the OS at all. I get some message when attempting to ADB-Sideload the 5.1m T-Mo OTA saying that "a file located at dev/block/msm.... Has been changed to R/W. Reflash and reboot to regain OTA privilege."
Only issue is I am on a LRX22C Factory Image with Stock recovery. Any help or questions will be welcomed.
Click to expand...
Click to collapse
I'm not a T-Mobile guy but based on the posts I've come across, the radio in the M update is 95R. since you can't take the OTA now with the boot loader issue, one option may be to flash the D or E factory image to get back onto 5.1. either way I think you want the 95R radio included with D, not the 98R included with E. I have to believe the M update will be released as a factory image at some point or something newer will be released.
GoldPaintedLemons said:
So after a few other mistakes I'd rather not own up to, I figured out that yes, mFastBoot was the solution to my issue. I'm not sure why I can't find any other folks posting about needing it for 5.1 builds on the the N6, but I did. I never needed it before 5.1, but I'm assuming the system.img file has grown larger than the standard SDK fastboot supports. I'm wondering if this is only an issue when flashing from linux. Theoretically, it should not be though; this issue is based on the memory available on the device (tmo N6, btw).
For those that don't know, "mFastboot" aka Motorola Fastboot is a tweaked version of fastboot provided by Motorola. It will actually split up the image and flash it in pieces.
Here are Instruction for installing and using mFastBoot to flash a Moto G on linux, but the process is the same, except for the images obviously. You'll have to either modify the flash-all.sh file or do each of the images manually.
Hope this helps someone else... it would be really weird if I'm the only one that runs into this.
Click to expand...
Click to collapse
You're not alone. I spent over 11hrs trying to get one or the other to flash too using a Mac with OS v10.10.2 and had the exact same issues. Found an mfastboot and was able to flash the images separately (flash-all.sh still failed).
Glad we're both all set... Now to delete the Android SDK and Java files!
X
Nexus 6 via Tapatalk
Freshly_Snipes said:
On Windows with virtually the exact same issue. I went back to 5.0.1 but the bootloader is stuck on the newer version and can not be modified. I do not use ADB manually anymore. I use toolkits these days and then try manually. Now I'm stuck on 5.0.1 and can not update the OS at all. I get some message when attempting to ADB-Sideload the 5.1m T-Mo OTA saying that "a file located at dev/block/msm.... Has been changed to R/W. Reflash and reboot to regain OTA privilege."
Only issue is I am on a LRX22C Factory Image with Stock recovery. Any help or questions will be welcomed.
Click to expand...
Click to collapse
Have you tried using mFastboot (just google it the windows exe is easily found)? You'll need to use that and flash each .img separately.
THANK YOU
I've been working with this off and on for some time, and your post was immensely helpful.
Latest fastboot drivers, latest ADB (truly the latest, not just apt-get-whatever). Same issue - system.img would not flash. Not with a script, not standalone, not in the zip file, nothing. What I see (almost constantly) is a buffer issue where the actual size of system.img is throwing a significant error with fastboot drivers. mFastboot (as you provided) on the other hand, utilizes a component called "sparse-flash", which appears to break large files into smaller (256mb) chunks that for whatever reason my N6 preferred. No issues with flashing after that, but again it must be done individually (system, boot, radio, etc.) - never as a zip with "-w update".
I find it curious that so few people have this issue (others can use the "normal" fastboot with large system files and no issue occurs). Those who do run into this problem seem to know their way around a terminal, so it makes me wonder what the underlying difference between us is.
For the record, I was on a machine running Mint 17.2, which is essentially Ubuntu 14.04.
Just really wanted to say thank you and hopefully promote the thread a bit to help others. Especially as many of us are flashing to bone stock momentarily to properly activate Project Fi.
@caain,
A couple of points/questions:
1) You mention having the latest fastboot "drivers". I'm not sure what you are referring to, but I've never heard of such a thing on Linux.
2) Where did you get ADB and fastboot from? Did you download the latest Android SDK?
2a) The point here, is that Google updated fastboot in November of last year to enable flashing the very large system.img from Lollipop. You can only get this necessary version of (if your are running Linux) fastboot via the Android SDK.... And without it, you can not successfully flash a Lollipop system.img.
cam30era said:
@caain,
A couple of points/questions:
1) You mention having the latest fastboot "drivers". I'm not sure what you are referring to, but I've never heard of such a thing on Linux.
2) Where did you get ADB and fastboot from? Did you download the latest Android SDK?
2a) The point here, is that Google updated fastboot in November of last year to enable flashing the very large system.img from Lollipop. You can only get this necessary version of fastboot via the Android SDK.... And without it, you can not successfully flash a Lollipop system.img.
Click to expand...
Click to collapse
You can flash the system image manually with fastboot. Can't fastboot flash the flash-all.bat without SDK 23+ platform tools. System image will fail. The 15 second adb/fastboot is not updated to achieve this. Not sure about Linux but if have latest SDK updated it will do the flash-all.bat.
none
I flashed M just to check it out, but prior to doing that I grabbed the SDK that had very recently updated to include the 6.0 M files, so I updated the 6.0 SDK prior to trying M, and when I went back I had zero issues with the flash.bat The only issue I had which was more of a pain than a problem is that flashing the factory image it unrooted the phone so I had to completely set up the phone all over again.
No more M for me until it's released because in the preview 3 not every component is functional, why they would do that I have no idea, so after learning that M wasn't complete I abandoned it. Hope this helps if you want to go back
cam30era said:
@caain,
A couple of points/questions:
1) You mention having the latest fastboot "drivers". I'm not sure what you are referring to, but I've never heard of such a thing on Linux.
2) Where did you get ADB and fastboot from? Did you download the latest Android SDK?
2a) The point here, is that Google updated fastboot in November of last year to enable flashing the very large system.img from Lollipop. You can only get this necessary version of (if your are running Linux) fastboot via the Android SDK.... And without it, you can not successfully flash a Lollipop system.img.
Click to expand...
Click to collapse
I suppose I use the word "drivers" a bit too flippantly, as you are correct and there is most certainly not a fastboot "driver" for linux. Perhaps the issue I was running into is that I was merely installing ABD and fastboot standalone, without including the entire Android SDK. In which case I ought to feel quite foolish!
Thank you for the clarification regarding the patch from November. I've no need for fastboot in the immediate future, but will certainly make sure install the SDK as a whole rather than pulling tools from other repositories in the future.
caain said:
I've no need for fastboot in the immediate future, but will certainly make sure install the SDK as a whole rather than pulling tools from other repositories in the future.
Click to expand...
Click to collapse
That's a very good idea. I would suggest doing this soon, so it's set up and ready to go when you need it.
Related
I know a couple people asked for a guide and I didn't see anything concise had been posted (Mods feel free to remove if it's a duplicate.). Things are still a bit fresh, but this should be a short list of steps to perform the upgrade of your Nexus 7 (2012) WiFi to Lollipop.
As with other guides, I make no expressed or implied warranties - you break it, it's on you.
This is how I was able to get Lollipop working on my own Nexus 7 (2012). I was coming from a rooted factory image of 4.4.4.4 which was the previous most-recent factory image released by Google for this device. I like my device as bone stock as possible and wanted to upgrade and keep it that way.
I assume the following:
You know how to use both adb and fastboot and have already configured your system to use these utilities.
You have already performed an oem unlock on your device.
That out of the way, on to the guide...
It goes without saying, but I'll call it out anyway... Take a backup of your current device setup. Most likely this is within your custom recovery or TiBu. If your not familiar with how to do so, consult the help pages for those apps.
Download & unpack the requisite files
LRX21P factory image from Google.
CF-Auto-Root from Chainfire.
OPTIONAL Only if you're upgrading from a version of Android prior to the JWR66Y Android 4.3 factory image, download the KRT16S factory image from Google.
Start by rebooting your device to the bootloader.
Code:
$ adb reboot bootloader
OPTIONAL If you have ignored my assumption and haven't already done so, now would be the time to oem unlock the bootloader
Code:
$ fastboot oem unlock
Run the following commands to prep your device to install Android L. NOTE:This will erase your device
Code:
$ fastboot erase cache
$ fastboot erase recovery
$ fastboot erase system
$ fastboot erase userdata
OPTIONAL If you are upgrading from a version of Android prior to the 4.23 bootloader release which was originally released along with the Android 4.3 JWR66Y factory image, then you will need to upgrade the bootloader also. The bootloader included in the Android L factory image is not correct and will fail to install. Your best bet is to download the KRT16S factory image from Google and use the bootloader-grouper-4.23.img file from that factory image. Be sure whatever version of the bootloader-grouper-4.23.img file you use has the correct md5sum.
Code:
$ md5sum nakasi-krt16s/bootloader-grouper-4.23.img
df53028033c9eccf4fe5ba7bc198ce24 nakasi-krt16s/bootloader-grouper-4.23.img
$ fastboot erase boot
$ fastboot flash bootloader nakasi-krt16s/bootloader-grouper-4.23.img
Now, install the actual Android L system
Code:
$ fastboot -w update image-nakasi-lrx21p.zip
Your device will automatically reboot at this point and when it does, you will be running Android L (5.0) 100% stock and WITHOUT ROOT. This boot usually takes a very long time (~5-10 minutes) as it's performing the initial setup of the OS. When the device is back up fully, you will have to go through the setup steps as if it were a new device. Once that's done, proceed to the next step.
Now that Android L is freshly-installed, not only have you lost root, but you've also lost the Developer Options menu and the USB Debugging option contained therein. So, before we proceed, we need to enable Developer options & USB Debugging in the settings menu so that adb & fastboot will work recognize the device. Again, if you have any experience with running adb & fastboot, you will know how to do this. The process is exactly the same as with previous versions, so there should not be any surprises here.
Go to the Settings menu and scroll down to and tap on "About Tablet"
On the next screen tap on the "Build Number" field seven (7) times and you'll be presented with a message of "You're now a Developer!"
Hit the back "triangle" and go into the Developer Options menu and turn on USB Debugging.
Just be sure to accept the key on your device when you connect it to your computer.
Now, we can use adb to reboot the device so we can apply the CF-Auto-Root patches and SuperSU from the bootloader
Code:
$ adb reboot bootloader
Once in the bootloader you will need to apply the cf-auto-root. Use the following command.
Code:
$ fastboot boot image/CF-Auto-Root-grouper-nakasi-nexus7.img
NOTE: Windows users have reported that the file is in the same directory so just double-check the path to the file.
This will boot the device onto a custom kernel, install the kernel fix to allow root and also install the latest beta version of SuperSU (2.20) for Android L.
You will now end up with a device running Android L with root. I did not mention at any point about installing a custom recovery. These steps will remove a custom recovery, so if you want to install that, you will need to consult the instructions for your custom recovery of choice. I usually use the CM instructions for installing CWM as they're easy to find. This is not strictly necessary for root. Similarly, my main purpose for rooting was to use Titanium Backup. The current production version of TiBu doesn't support Android L, but the TiBu team has released a test version for L via their twitter feed. Here's a direct link or you can go to their twitter feed for more info...
Questions? Comments? Did I miss something? Let me know.
EDIT: Seems that the performance has really gone down over the past few days. Not really sure what the cause of the performance degradation is but it's quite severe. I noticed last night after having left it plugged in all night that the device wouldn't even turn on or took an inordinately long amount of time (many minutes) to wake from sleep. As it stands I attempted to play a game that's slightly intensive and after a short period of time the device got really hot and started really having performance issues to the point where it rebooted on it's own. Further, I noticed a number of things aren't working that probably should... Bluetooth & "Battery Saver" mode are the first two that come to mind.
Anyone else experiencing similar issues?
worked for me, with 2 changes:
- I had to enable developer mode on my first boot into L before I could execute the command "adb reboot bootloader"
- on my Windows machine, I had unzipped the root zip file, so I executed the command this way: "fastboot boot CF-Auto-Root-grouper-nakasi-nexus7.img", leaving out the "image/"
Thanks for your guide!
SuperSU is there. It does not complain about the binary. But TitaniumBackup can't find SU...
EDIT: Found the solution for TB in another thread.
petenatas said:
SuperSU is there. It does not complain about the binary. But TitaniumBackup can't find SU...
EDIT: Found the solution for TB in another thread.
Click to expand...
Click to collapse
Would you mind pointing me to it?
If you're like me and haven't updated your bootloader to 4.23 you will need to do so... sadly that which is included with the most recent files is corrupt (yes the files from google.) download the krt16s version and overwrite your bootloader-grouper-4.23.img file. Then from the command line like before type "fastboot flash bootloader bootloader-grouper-4.23.img" then "fastboot reboot-bootloader" and follow the directions above!
Enjoy!
jasoraso said:
worked for me, with 2 changes:
- I had to enable developer mode on my first boot into L before I could execute the command "adb reboot bootloader"
Click to expand...
Click to collapse
added
- on my Windows machine, I had unzipped the root zip file, so I executed the command this way: "fastboot boot CF-Auto-Root-grouper-nakasi-nexus7.img", leaving out the "image/"
Thanks for your guide!
Click to expand...
Click to collapse
Not sure about on Windows, but on Linux when I unzipped the root zip file, there was a directory layout as such...
Code:
cf-auto-root/
cf-auto-root/image/
cf-auto-root/image/CF-Auto-Root-grouper-nakasi-nexus7.img
cf-auto-root/root-linux.sh
cf-auto-root/root-mac.sh
cf-auto-root/root-windows.bat
cf-auto-root/tools/
cf-auto-root/tools/AdbWinApi.dll
cf-auto-root/tools/AdbWinUsbApi.dll
cf-auto-root/tools/fastboot-linux
cf-auto-root/tools/fastboot-mac
cf-auto-root/tools/fastboot-windows.exe
In any case, you were able to find it. Should be pretty obvious which file I'm referring to...
apocope said:
Would you mind pointing me to it?
Click to expand...
Click to collapse
Added a link in the paragraph at the end.
Yes!
I needed my root. (The stock kernel underclocks like crazy, making the tablet nearly unusable.)
Thanks for the guide brother. You are awesome
I am now on a Rooted Android L tablet, thanks to the CF-Root 'boot.img' by Chainfire.
I have a question though. I wanted to ask ... this specific boot.img by chainfire seems to have automatically upgraded my SuperSU app to v2.20, so i didn't flash the 2.19 BETA. How did this happen? Any idea? (Did that CF-Root get updated after you made this guide?) i am curious to know
A very very very very usefull guide!!!!
All working fine!!!!
Thanks!!!!!!!
pyrostic said:
If you're like me and haven't updated your bootloader to 4.23 you will need to do so... sadly that which is included with the most recent files is corrupt (yes the files from google.) download the krt16s version and overwrite your bootloader-grouper-4.23.img file. Then from the command line like before type "fastboot flash bootloader bootloader-grouper-4.23.img" then "fastboot reboot-bootloader" and follow the directions above!
Enjoy!
Click to expand...
Click to collapse
OMG corrupted bootloader AGAIN.
GOOGLE what's wrong with you???
Thanks for the guide! Works fantastically on my aging N7.
Short rundown video by me on YouTube here:
Does it wipe internal storage?
abobobilly said:
Thanks for the guide brother. You are awesome
Click to expand...
Click to collapse
:good:
I am now on a Rooted Android L tablet, thanks to the CF-Root 'boot.img' by Chainfire.
Click to expand...
Click to collapse
:good::good:
I have a question though. I wanted to ask ... this specific boot.img by chainfire seems to have automatically upgraded my SuperSU app to v2.20, so i didn't flash the 2.19 BETA. How did this happen? Any idea? (Did that CF-Root get updated after you made this guide?) i am curious to know
Click to expand...
Click to collapse
I made a mistake on the version number that I listed in my instructions. When I did my N7, I had originally just tried flashing SuperSU via the standard zip file method. The most recent version of SuperSU available in the SuperSU XDA thread is/was 2.19, so I just assumed that it was the same version being used in the CF-Auto-Root. But as you correctly point out, the process installs 2.20 not 2.19. I updated the version number in the guide. Thanks.
ToucherCD said:
Does it wipe internal storage?
Click to expand...
Click to collapse
Yes, unfortunately it does.
I wouldn't recommend trying to upgrade without wiping user data. There may be internal changes to the file system and layout that could make a Kit Kat install (4.4.X) incompatible with this. Best to save off your data and start from scratch.
pyrostic said:
If you're like me and haven't updated your bootloader to 4.23 you will need to do so... sadly that which is included with the most recent files is corrupt (yes the files from google.) download the krt16s version and overwrite your bootloader-grouper-4.23.img file. Then from the command line like before type "fastboot flash bootloader bootloader-grouper-4.23.img" then "fastboot reboot-bootloader" and follow the directions above!
Enjoy!
Click to expand...
Click to collapse
Added a link to the KRT16S factory image which contains a proper bootloader-grouper-4.23.img file that you could use.
jetsaredim said:
Yes, unfortunately it does.
I wouldn't recommend trying to upgrade without wiping user data. There may be internal changes to the file system and layout that could make a Kit Kat install (4.4.X) incompatible with this. Best to save off your data and start from scratch.
Click to expand...
Click to collapse
Hi. Good job on the guide. Very detailed. That's good.
Thanks for the tip with booting CFautoroot img. I was wandering why superSU 2.16 was not working and was looking for modified karnel all morning.
BTW. I know it's not recommended, even my Tapatalk signature says it
but I didn't wipe user data while upgrading. See my post here with details.
The Answer to The Ultimate Question of Life, the Universe, and Everything is: CLEAN FLASH.
Can I just ask about the bootloader?
I'm seeing alot of users reporting there's an issue within the bootloader that is included on the LRX21P image for Grouper, I performed a clean flash yesterday and flashed the leaked image for grouper, I haven't had any single issue flashing all of the images, even bootloader that came from the lollipop image doesn't seem to cause an issue.
Btw, everyone's suggesting to flash the bootloader from JB & KK on this lollipop build, is there any impact on the performance of why's that recommended to flash the old bootloader?
And I didn't really expect this but lollipop made it worst to run on this device! Even if it's a 2012 device, why's that it can't handle lollipop smoothly? I can't even drop the status bar down at a rate of 60fps as promised by Google, can't even swipe the screen smoothly and it's freezing as hell! It feels like something's wrong with this build.
We can't always tell the reason that this is a very old device so that it performs really bad, how come that my 2011 device with a CM11 installed that is still functioning well and smoothly performing operations on just top of its single core 1Ghz and 512 megabytes of RAM? Rather than this quad core tegra device that is WAY MORE faster supposedly?
JovieBrett said:
We can't always tell the reason that this is a very old device so that it performs really bad, how come that my 2011 device with a CM11 installed that is still functioning well and smoothly performing operations on just top of its single core 1Ghz and 512 megabytes of RAM? Rather than this quad core tegra device that is WAY MORE faster supposedly?
Click to expand...
Click to collapse
Because Asus used chip silicon chips as requested by Google to bring the cost down. They degrade with time and slow down. My wife's 32GB Grouper is unusable in my standards (using Nexus 5 for list year and OnePlus One now), it lags as hell no matter what, F2FS or ext4, stock or custom ROM, it lags. I so much regret I didn't convince her to change it to N7 2013 last year, as she didn't feel the need to spend money...
I was so looking forward to N9, but not for the price they ask. 16GB is useless, so 32GB is the only option, but 489 EUR (=610 USD) they ask in Europe is way over what I'd spend on YouTube player (that's what she most uses it for) with, wait, wrong screen aspect to watch videos!
/rant
The Answer to The Ultimate Question of Life, the Universe, and Everything is: CLEAN FLASH.
Natakranta said:
Because Asus used chip silicon chips as requested by Google to bring the cost down. They degrade with time and slow down. My wife's 32GB Grouper is unusable in my standards (using Nexus 5 for list year and OnePlus One now), it lags as hell no matter what, F2FS or ext4, stock or custom ROM, it lags. I so much regret I didn't convince her to change it to N7 2013 last year, as she didn't feel the need to spend money...
I was so looking forward to N9, but not for the price they ask. 16GB is useless, so 32GB is the only option, but 489 EUR (=610 USD) they ask in Europe is way over what I'd spend on YouTube player (that's what she most uses it for) with, wait, wrong screen aspect to watch videos!
/rant
The Answer to The Ultimate Question of Life, the Universe, and Everything is: CLEAN FLASH.
Click to expand...
Click to collapse
Yup, I all agree of what have you said. I tried ext4, f2fs etc etc, none of them improves the N7's performance or at least the stock one has the best performance and stability for me.
Heard alot of users blaiming about the tegra chip for this, they said that tegra chips are getting worst every year and if all of these are true, I have doubts about Nexus 9's performance since even the one of the famous 'Android Police' senior editors have found that there are unusual freezes and glitches from the device itself, idk if that happened on the latest build for N9.
The 2011 device I'm currently comparing to is an Xperia Mini, snapdragon chip with 1Ghz single core, 512MB of RAM, I'll look away from tegra based devices...
Btw, do you have an N7 2013? I'm planning to buy one this December to replace my 2011 device. Can I trust this 2013 model with snapdragon processor? I always trust these snapdragon based devices.
I'm assuming that since I've rooted my Pure Edition that once the official 5.1 OTA comes it will fail to install just like 5.0-5.02 on my N7 did. I'm wondering how I can get back to unrooted without wiping the phone out (if that's possible). I can't seem to find the factory 5.0 image at the Motorola site so right now I'm assuming I'll have to install the 4.4..4 image and then let the OTA's roll in?
When I ran into this on my N7 other than rooting the only system installed app I had added in was better battery stats and removing root and getting rid of (at least I think I got rid of it) BBS the OTA failed still and I had to just flash the system.img from the factory image. On my XT1095 I only have SuperSU installed. I never installed BBS or any other new apps as system apps so maybe telling SuperSU to unroot and clean up will work?
Maybe I'm wrong, but I was under the impression you could still receive the OTA with root as long as you were on stock recovery, you would just lose root access in the process. I could be way off, though. I have always had TWRP on my rooted phones. I am pretty confident that you cannot switch back to stock recovery from TWRP without wiping. You can always use Helium Pro to back everything up. Unlike TiBu, it does not require root. Or you could just wait on someone to release a .zip of the OTA and flash it manually.
Paddington said:
Maybe I'm wrong, but I was under the impression you could still receive the OTA with root as long as you were on stock recovery, you would just lose root access in the process. I could be way off, though. I have always had TWRP on my rooted phones. I am pretty confident that you cannot switch back to stock recovery from TWRP without wiping. You can always use Helium Pro to back everything up. Unlike TiBu, it does not require root. Or you could just wait on someone to release a .zip of the OTA and flash it manually.
Click to expand...
Click to collapse
It used to be that way before 5.0. Something changed in 5.0+ and now if certain parts of the file system are off at all from stock, OTA will fail. That's why I mentioned the example of my Nexus 7 failing the update from 5.0 to 5.02. I don't know if Motorola is keeping the same kinds of checks as Nexus OTA's though. I do still have the stock recovery. If I need TWRP for something I just temporarily boot it with fastboot instead.
Any luck with this? I too would like to unroot. Still stock recovery.
flyinion said:
I can't seem to find the factory 5.0 image at the Motorola site
Click to expand...
Click to collapse
Here you go:
http://www.graffixnyc.com/motox.php
flyinion said:
so right now I'm assuming I'll have to install the 4.4..4 image and then let the OTA's roll in?:cyclops:
Click to expand...
Click to collapse
No, 4.4.4 won't boot with the 5.0 boot.img. And NEVER attempt to downgrade the bootloader (motoboot.img) or partition table (gpt.bin) of a Motorola Moto X. These are NOT Nexus devices.
Thanks very much! So...in an abundance of caution, I should be able to flash boot.img and that will get rid of root? Or system.img too? And neither of those affect my data? Edit: I am rooted on 22.21.11 XT1095 with stock recovery
Hmm. Not available on that site anymore but found it at http://motofirmware.center/files/file/76-tmo_xt1095_50_lxe2246-11_cid9_cfcxmlzip/
Mnemoch said:
Thanks very much! So...in an abundance of caution, I should be able to flash boot.img and that will get rid of root? Or system.img too? And neither of those affect my data? Edit: I am rooted on 22.21.11 XT1095 with stock recovery
Click to expand...
Click to collapse
Just flash 5.0 system.img that is all you need unless you flashed a custom kernel
Personally I would not take the OTA - I would use Motorola Device Manager to update. If you are rooted you can uninstall MotorolaOTA and then when people report the OTA is being pushed, flash system back to stock and then let MDM update you - you will have a copy of the 5.1 fxz on your computer then.
Thanks for the advice, I will check out MDM and yes, waiting for the OTA to be published officially.
That other link I posted for the full image file was corrupt, but I found http://graffixnyc.com/development/motox2014/lollipop/22.21.11/ which has system.img available. But this is huge! Does it seem correct to you by any chance? Should be able to flash without losing my data?
JulesJam said:
Just flash 5.0 system.img that is all you need unless you flashed a custom kernel
Personally I would not take the OTA - I would use Motorola Device Manager to update. If you are rooted you can uninstall MotorolaOTA and then when people report the OTA is being pushed, flash system back to stock and then let MDM update you - you will have a copy of the 5.1 fxz on your computer then.
Click to expand...
Click to collapse
Thanks guys, I did find the image and had downloaded it from that link a while back. I also picked up the mfastboot tool, but I'm not sure how to use it to flash a system.img. That download has a bunch of system.img_sparsechunk.n files where .n is a number from 0-7 but there's no "base" system.img file. Do I just tell it to flash file 0 and it will pick up the rest of them automatically?
flyinion said:
Thanks guys, I did find the image and had downloaded it from that link a while back. I also picked up the mfastboot tool, but I'm not sure how to use it to flash a system.img. That download has a bunch of system.img_sparsechunk.n files where .n is a number from 0-7 but there's no "base" system.img file. Do I just tell it to flash file 0 and it will pick up the rest of them automatically?
Click to expand...
Click to collapse
No you have to do each 1 at a time. Regular fastboot can flash the sparsechunks - you only need mfastboot if the image is a single file.
fastboot flash system sparsechunk0
then when it is done
fastboot flash system sparsechunk1
until you have flashed them all
JulesJam said:
No you have to do each 1 at a time. Regular fastboot can flash the sparsechunks - you only need mfastboot if the image is a single file.
fastboot flash system sparsechunk0
then when it is done
fastboot flash system sparsechunk1
until you have flashed them all
Click to expand...
Click to collapse
Ah ok, I thought I needed mfastboot from what I was able to read around here. So the standard fastboot that comes with the android sdk can be used on the chunks?
Actually I think maybe I understand now. I read something a little bit ago about the difference between fastboot and mfastboot (Motorola Fastboot) and that the latter was created due to a file size limitation with the original fastboot. It didn't go into more detail than that. My assumption instantly was motorola was splitting the system image up into chunks and created that new fastboot to handle that. Seems it's the other way around? Google's fastboot can handle chunks and Moto's can handle a single image that is larger than what the standard fastboot can so they don't have to split it up in the first place?
Which download has chunks, the zip that we can't download any more or the system.img that I found? Should I try to extract it?
flyinion said:
Actually I think maybe I understand now. I read something a little bit ago about the difference between fastboot and mfastboot (Motorola Fastboot) and that the latter was created due to a file size limitation with the original fastboot. It didn't go into more detail than that. My assumption instantly was motorola was splitting the system image up into chunks and created that new fastboot to handle that. Seems it's the other way around? Google's fastboot can handle chunks and Moto's can handle a single image that is larger than what the standard fastboot can so they don't have to split it up in the first place?
Click to expand...
Click to collapse
Mnemoch said:
Which download has chunks, the zip that we can't download any more or the system.img that I found? Should I try to extract it?
Click to expand...
Click to collapse
Oh, the one that doesn't work anymore. I downloaded it a few weeks ago. Not sure when it got taken offline since the link is there, but yeah I see the download doesn't work any longer. If you have just a single system.img and not a bunch of system.img_sparsechunk.n files then you have a different image.
Anyone unrooted since the OTA came out?
JulesJam said:
No you have to do each 1 at a time. Regular fastboot can flash the sparsechunks - you only need mfastboot if the image is a single file.
fastboot flash system sparsechunk0
then when it is done
fastboot flash system sparsechunk1
until you have flashed them all
Click to expand...
Click to collapse
Anyone use this process to unroot stock 22.21.11?
And if so, did you get and take the 5.1 OTA or did you sideload it?
Thanks
eKeith said:
Anyone use this process to unroot stock 22.21.11?
And if so, did you get and take the 5.1 OTA or did you sideload it?
Thanks
Click to expand...
Click to collapse
Unrooting using this method does work!
Maybe unrelated, but in my confusion as to what's going on, is it at all possible to flash the 5.1 ota update over a custom rom? I'm currently on resurrection remix that's running on 5.1.1, but I really want to go back to stock. Thanks in advance.
dcdrew713 said:
Maybe unrelated, but in my confusion as to what's going on, is it at all possible to flash the 5.1 ota update over a custom rom? I'm currently on resurrection remix that's running on 5.1.1, but I really want to go back to stock. Thanks in advance.
Click to expand...
Click to collapse
Not possible. You have to flash the stock rom first, then take the ota.
Sent from my XT1095 using Tapatalk
Any idea what stock rom to use? 5.0? Sorry, I'm not the best with this stuff anymore, haha.
I just bought a sim unlocked Nexus 6 from Amazon about a week ago and I need some help with it.... I guess I jumped the gun without gathering enough info on the N6
As soon as it was delivered I checked it out and found it had 5.0 on it.... I was unaware that there were two updates for it that increase battery life among other improvements, 5.1 and 5.1.1
( I had it search for updates 5 minutes out of the box, it said it was up to date, so I assumed it was)
So I rooted it and unlocked the bootloader and installed TWRP... I used it for several days to find the battery didn't last much past 3pm so I started researching battery issues on the N6 to find out that there are two updates for my N6 that resolve the battery issue.
So tonight I set out to try and get the 5.1 or 5.1.1 on it for the better battery life in the new updates. That's when I discovered that rooted, it won't get any ota updates...
So after reading countless posts and watching videos on trying to get the updates on a rooted N6, I installed Scotts 5.1 Rooted DeOdex Rom
HTML:
http://www.scottsroms.com/downloads.php?do=file&id=604
which is supposed to put me into a rom with the better battery life update.........
So now that 5.1 is installed I keep getting a pop up a notification that an update it available (5.1.1), I downloaded it on my phone and followed the prompts to "reboot and install"
when it reboots is goes into TWRP but I get an error message that the update failed..... So I am not sure how to install this 5.1.1 update OR if it is entirely necessary.
The error message in TWRP is as follows: "Package expects build fingerprint of google/shamu/shamu:5.1/LMY47D:user/release/keys; This device has google/omni-shamu:5.0.2/LRX22G/4:eng/test-keys.
Error executing updater binary in zip '/cache/updater.zip' E:Error installing zip file '/cache/update.zip'
Could somebody please shed some light on this for me.... I have spent hours here trying to figure this out to no avail....
Thank you
(Please don't beat me up to bad....I like to completely unlock my devices when I get a new one but I don't do this stuff very often)
jessepatty said:
I just bought a sim unlocked Nexus 6 from Amazon about a week ago and I need some help with it.... I guess I jumped the gun without gathering enough info on the N6
As soon as it was delivered I checked it out and found it had 5.0 on it.... I was unaware that there were two updates for it that increase battery life among other improvements, 5.1 and 5.1.1
( I had it search for updates 5 minutes out of the box, it said it was up to date, so I assumed it was)
So I rooted it and unlocked the bootloader and installed TWRP... I used it for several days to find the battery didn't last much past 3pm so I started researching battery issues on the N6 to find out that there are two updates for my N6 that resolve the battery issue.
So tonight I set out to try and get the 5.1 or 5.1.1 on it for the better battery life in the new updates. That's when I discovered that rooted, it won't get any ota updates...
So after reading countless posts and watching videos on trying to get the updates on a rooted N6, I installed Scotts 5.1 Rooted DeOdex Rom
HTML:
http://www.scottsroms.com/downloads.php?do=file&id=604
which is supposed to put me into a rom with the better battery life update.........
So now that 5.1 is installed I keep getting a pop up a notification that an update it available (5.1.1), I downloaded it on my phone and followed the prompts to "reboot and install"
when it reboots is goes into TWRP but I get an error message that the update failed..... So I am not sure how to install this 5.1.1 update OR if it is entirely necessary.
The error message in TWRP is as follows: "Package expects build fingerprint of google/shamu/shamu:5.1/LMY47D:user/release/keys; This device has google/omni-shamu:5.0.2/LRX22G/4:eng/test-keys.
Error executing updater binary in zip '/cache/updater.zip' E:Error installing zip file '/cache/update.zip'
Could somebody please shed some light on this for me.... I have spent hours here trying to figure this out to no avail....
Thank you
(Please don't beat me up to bad....I like to completely unlock my devices when I get a new one but I don't do this stuff very often)
Click to expand...
Click to collapse
Can't OTA update with root or custom recovery. Have to be full stock. Will have to fastboot the factory image. Might as well do latest 5.1.1 for your carrier. If going to do root and recovery will have to forget about OTAs and flash factory images.
prdog1 said:
Can't OTA update with root or custom recovery. Have to be full stock. Will have to fastboot the factory image. Might as well do latest 5.1.1 for your carrier. If going to do root and recovery will have to forget about OTAs and flash factory images.
Click to expand...
Click to collapse
I appreciate the reply..... that is exactly what I have come to learn.... (the hard way)
I guess I need to figure out:
1) if the 5.1.1 is much of an improvement over the 5.1 I have now
2) Find the correct 5.1.1 image for my N6
3) Learn how to fastboot it.... I seem to have issues getting the commands right....
Do you know of a step by step I can follow with all the proper commands?
You guy will have to forgive me as I am very novice in this and although I thoroughly enjoy knowing I did it, the pure terror of possibly bricking my $600 phone scares the hell out of me.
jessepatty said:
I appreciate the reply..... that is exactly what I have come to learn.... (the hard way)
I guess I need to figure out:
1) if the 5.1.1 is much of an improvement over the 5.1 I have now
2) Find the correct 5.1.1 image for my N6
3) Learn how to fastboot it.... I seem to have issues getting the commands right....
Do you know of a step by step I can follow with all the proper commands?
You guy will have to forgive me as I am very novice in this and although I thoroughly enjoy knowing I did it, the pure terror of possibly bricking my $600 phone scares the hell out of me.
Click to expand...
Click to collapse
Look here for how to flash a stock rom (in parts) http://forum.xda-developers.com/nexus-6/general/guide-flash-factory-images-nexus-6shamu-t2954008 step 2.
Look here for all Nexus 6 Images https://developers.google.com/android/nexus/images.
What carrier do you use? For: T-Mobile 28E, Verizon 47E, ATT/US/International 47Z.
BTW batterylife is mainly determined by the setup of the phone and usage of the user, not so much by roms and kernels
jessepatty said:
I appreciate the reply..... that is exactly what I have come to learn.... (the hard way)
I guess I need to figure out:
1) if the 5.1.1 is much of an improvement over the 5.1 I have now
2) Find the correct 5.1.1 image for my N6
3) Learn how to fastboot it.... I seem to have issues getting the commands right....
Do you know of a step by step I can follow with all the proper commands?
You guy will have to forgive me as I am very novice in this and although I thoroughly enjoy knowing I did it, the pure terror of possibly bricking my $600 phone scares the hell out of me.
Click to expand...
Click to collapse
More than likely your battery is being ate by something you have loaded on phone. There is a T-Mobile based rooted rom here. If want to try it can just flash in recovery but wipe everything including data in TWRP. Full wipe will make a big difference. System, dalvic, cache.and data.
http://forum.xda-developers.com/showpost.php?p=59561445&postcount=1
If know how to fastboot here is how to do it.
Drag and Drop or Copy/Paste Images to {}
STEP #1
fastboot flash bootloader {bootloader.img}
fastboot reboot-bootloader
fastboot flash radio {radio.img}
Step #2
fastboot erase recovery
fastboot erase system
fastboot erase boot
fastboot format vendor {don't need for phone}
fastboot format cache
fastboot format userdata {optional}
Step#3
fastboot flash recovery {recovery.img}
fastboot flash system {system.img}
fastboot flash boot {boot.img}
fastboot flash vendor {vendor.img}
fastboot flash cache {cache.img}
fastboot flash userdata {userdata.img}
fastboot reboot
---------- Post added at 01:55 AM ---------- Previous post was at 01:50 AM ----------
gee2012 said:
Look here for how to flash a stock rom (in parts) http://forum.xda-developers.com/nexus-6/general/guide-flash-factory-images-nexus-6shamu-t2954008 step 2.
Look here for all Nexus 6 Images https://developers.google.com/android/nexus/images.
What carrier do you use? For: T-Mobile 28E, Verizon 47E, ATT/US/International 47Z.
Click to expand...
Click to collapse
Verizon is also the Z image as per today. I updated tonight.
prdog1 said:
More than likely your battery is being ate by something you have loaded on phone. There is a T-Mobile based rooted rom here. If want to try it can just flash in recovery but wipe everything including data in TWRP. Full wipe will make a big difference. System, dalvic, cache.and data.
http://forum.xda-developers.com/showpost.php?p=59561445&postcount=1
If know how to fastboot here is how to do it.
Drag and Drop or Copy/Paste Images to {}
STEP #1
fastboot flash bootloader {bootloader.img}
fastboot reboot-bootloader
fastboot flash radio {radio.img}
Step #2
fastboot erase recovery
fastboot erase system
fastboot erase boot
fastboot format vendor {don't need for phone}
fastboot format cache
fastboot format userdata {optional}
Step#3
fastboot flash recovery {recovery.img}
fastboot flash system {system.img}
fastboot flash boot {boot.img}
fastboot flash vendor {vendor.img}
fastboot flash cache {cache.img}
fastboot flash userdata {userdata.img}
fastboot reboot
---------- Post added at 01:55 AM ---------- Previous post was at 01:50 AM ----------
Verizon is also the Z image as per today. I updated tonight.
Click to expand...
Click to collapse
Thans for the info, didn`t know that. Image is not up yet atm on the Google dev site.
gee2012 said:
Thans for the info, didn`t know that. Image is not up yet atm on the Google dev site.
Click to expand...
Click to collapse
http://www.droid-life.com/2015/07/01/verizon-says-android-5-1-1-lmy47z-is-ready-for-its-nexus-6/
Ok guys, I appreciate all the info. It helped allot. Thank you
I did manage to get CyanogenMod 12.1 nightly on it which is 5.1.1 but now I have run into another issue that I cannot figure out....
Whenever a notification calls for one of my added notification sounds to play, it doesn't play the sound and a pop up comes up and says "Server died" when it tries to play the sound.... It plays all the preinstalled sounds and all my added music, it's just notifications in the wav format that it keeps giving me the "Server died" error on and it's not all the wav's I added, just a few... It makes no sense to me... I've taken them back off, rebooted the phone, added them back on and it will not play them at all.. These are the same notification sounds I have used for years on all my previous android devices and never had this issue with them working before... Everytime I get a new device I just transfer them over....
Hello,
I'm using RSD Lite 6.1.5 on my XT 1058 and trying to flash back to stock. It's connected, but when I try to flash the "Ghost_att-user 5.1 LPA23.12-21.1 1. I keep getting "Failed flashing Process. Unknown fastboot command."
Am I getting this error because I took the "stagefright" update?
Any insight would be helpful.
Thanks,
Adam
97vulcan said:
Hello,
I'm using RSD Lite 6.1.5 on my XT 1058 and trying to flash back to stock. It's connected, but when I try to flash the "Ghost_att-user 5.1 LPA23.12-21.1 1. I keep getting "Failed flashing Process. Unknown fastboot command."
Am I getting this error because I took the "stagefright" update?
Any insight would be helpful.
Thanks,
Adam
Click to expand...
Click to collapse
I've used RSD6.2.4 without problem on Moto X (xt1060). I attached it if you're wanting to give it a shot. Stagefright should have nothing to do with it and flashing any legit version of 5.1 should be kosher since there's nothing newer that is official. All that "should" have to be true is that your phone is for sure in the bootloader, and your version of RSDlite is compatible and of course that your .xml content is not corrupt.
If you can't do this, I'd give the manual version a shot (look at the .xml file that's flashing everything): From the XML file, just get into mfastboot (or fastboot if it works OK) and do the manual flash commands on everything in the .xml file. If there's any errors, just report them back here. --
Note: Yeah, there's a lot of stuff written about not trying to flash over the bootloader, but that only applies if you were going "down" by a version or more, not if you're flashing 5.1.
hachamacha said:
I've used RSD6.2.4 without problem on Moto X (xt1060). I attached it if you're wanting to give it a shot. Stagefright should have nothing to do with it and flashing any legit version of 5.1 should be kosher since there's nothing newer that is official. All that "should" have to be true is that your phone is for sure in the bootloader, and your version of RSDlite is compatible and of course that your .xml content is not corrupt.
If you can't do this, I'd give the manual version a shot (look at the .xml file that's flashing everything): From the XML file, just get into mfastboot (or fastboot if it works OK) and do the manual flash commands on everything in the .xml file. If there's any errors, just report them back here. --
Note: Yeah, there's a lot of stuff written about not trying to flash over the bootloader, but that only applies if you were going "down" by a version or more, not if you're flashing 5.1.
Click to expand...
Click to collapse
hachamacha,
thank you! I will give it a try with 6.2.4. Appreciate your help, and it's good to know that I will not cause any issues by reflashing 5.1.
Thanks,
Adam
hmm so I tried to flash, but I'm getting "downgraded security version" update gpt_main version failed preflash validation failed for GPT"
Thanks
97vulcan said:
hmm so I tried to flash, but I'm getting "downgraded security version" update gpt_main version failed preflash validation failed for GPT"
Thanks
Click to expand...
Click to collapse
Now I'm curious: Your thread title implies that you're somehow going "back" (as in backwards from a higher version) to stock 5.1. What exactly is on your phone right now, and does it boot at all? Is the bootloader unlocked or locked? Also: Do you know (from looking at RSD) which file was being flashed when the error occurred?
The error you're getting almost implies that you're flashing a lower version of motoboot.img or perhaps fsg.* , or I suppose are having the problem like people that took OTA's to upgrade and then tried to downgrade. I guess I'd want to know what's on the phone, what's working right now, and anything else like bootloader status, etc. You're certain you've got correct drivers for the USB on whatever computer you're using?
My temptation would be to attempt to comment out (in the .xml file that RSD is using) the line that flashes motoboot & the line that flashes gpt (partition table) and see if the rest of it works, or just gives the same error. There's a long thread of "successes" of people even downgrading as long as they don't touch those two files, but I'm sure no technique works every time.
One other way to look at this (I probably already mentioned) is to forget RSD & XML and just look at the XML as a guide for what you actually want to flash and then with the phone in bootloader, flash those things "mfastboot flash partition {part_name.img} etc. Don't flash motoboot or fsb and see where you get errors if you get errors. Try to boot it up and see what you get. --
What does your phone say in FastbootMode in the top left corner somewhere?
like 30.BE or something along those lines
No XML File located????
I also am getting this. I have the official 5.1 from Motorola. I took the stagefreight update previously, but assume that this would be integrated into the newest firmware (which I DL'd from moto yesterday).
Any thoughts?
Also, when I extract the firmware I cannot see the XML file anywhere. Am I extracting this incorrectly?
Nexus 6 Rooted and Unlocked and now new OTA – confused
Dear Friends,
I am currently having Nexus 6 with Build Number MRA58N which is rooted unlocked. Last time I had to format Nexus 6 just to update to this build. The nexus toolkit was somehow not working for me.
Now I see again that there is an OTA called android 6.0.1
image hosting
Now I tried using Wugfresh Toolkit first to take android backup but it fails and shows as shown in screenshot that currently there is no modified boot.img available for MRA58N.
free photo upload
I really don’t want to flash factory image bcz it will overwrite everything and erase all.
Kindly help.
Reformatting and again restoring is too much of pain.
Google is your friend, you should Google something like that before creating a post, but anyway you can't take an Ota on a rooted device, if you want the Ota, flash system.img of the current rom, and then take the Ota
I did try and read many posts but still could not conclude anything for sure. Yes I agree OTA cannot be taken on rooted device and thats why my question. you suggested flashing system.img of current rom. Now thats where confusion starts as many posts mention that one needs to be 100percent stock. Many people recommended complete wipe and yet many posed lot of questions because of marshmallow special kernel rom issues which is beyond my technical understanding.
Hence I summarized to pose my query to get considered opinion and guidance. Your response is helpful but am not able to fully comprehend.
Hence request for more guidance.
Really appreciate if some experts would kindly reply to my query and guide me. It will be very helpful as I really want to update but really scared of messing up. Kindly respond.
http://www.droidviews.com/how-to-install-ota-updates-on-rooted-nexus-6/
also watch a few youtube vid's - it is a road well traveled.
i.e.
- Flash the system image for build that you are currently running.
- sideload the update
be patient and don't even think of interrupting the process.
Read the stickies and learn something, toolkits and no skills spell disaster.
Did all what was suggested word by word and now my device is stuck with ADB sideload step. Pls see the two screenshots which i took as photo from another phone. (So apologise pic quality).
Kindly guide what went wrong.
The current build was rooted using wugfresh toolkit.
Now i am stuck at this ADB step. Kindly help Pls.
upload an image
image hosting site over 5mb
Did all what was suggested word by word and now my device is stuck with ADB sideload step. Pls see the two screenshots which i took as photo from another phone. (So apologise pic quality).
Kindly guide what went wrong.
The current build was rooted using wugfresh toolkit. Did all what was suggested word by word and now my device is stuck with ADB sideload step. Pls see the two screenshots which i took as photo from another phone. (So apologise pic quality).
Kindly guide what went wrong.
The current build was rooted using wugfresh toolkit.
Now i am stuck at this ADB step. Kindly help Pls.
upload an image
image hosting site over 5mb
Now i am stuck at this ADB step. Kindly help Pls.
Something got messed up in the process. You can try to individually flash your corresponding boot.img from your version via fastboot. You can download and extract that boot.img from Google's stock images.
This is just me speaking my mind but why people go through the trouble to root just to keep the stock ROM is beyond me.
Given your situation you are better off wiping/formatting and reflashing a new ROM stock (hopefully not) or custom.
Offering this as a comment, not an answer. I agree with mikeprius - in your position I would bite the bullet, download the latest MMB29K image, and run flash-all to wipe and set your device to the newest version - or perhaps even wait for the one which may arrive within a few days. If you leave the device on stock, unrooted, you'll be able to apply OTAs without any problem at all.
For curiosity, why do you even need root? As you've discovered, it opens up cans of worms that can be more trouble than they're worth unless there's an *overwhelming* necessity for root.
looks like failed with verification of /boot
reflash these for build you are currently on - I've done this without losing data:
fastboot flash boot boot.img
fastboot flash cache cache.img
fastboot flash recovery recovery.img
fastboot flash radio radio.img
fastboot flash system system.img
fastboot reboot-bootloader
it''ll probably pop up with the dead android -- don't reboot. Press
power button+vol up
you may have have to do a bunch of times -- eventually it go to the menu to allow you sideload the update.
Why are people so fixated on installing an old ROM and then sideloading the update when the obvious answer is to simply install the components of the latest ROM? I get the desire to retain the existing data, but to my eyes it looks as if the phone is now in an unstable and unreliable state and a complete refresh is the best solution.
it's a choice and there is experience gained in the exercise - and the existing data thing is big deal to many.