Related
The files were posted today. Remember to grab the MZ604 files if you have the Wifi only version of the Xoom.
http://developer.motorola.com/products/software/ <------ Grab the files here. The files are for the US version of the Wifi Xoom only.
Instructions to return it to stock
1) First you need the Moto Drivers - Read this thread to START you - http://forum.xda-developers.com/showthread.php?t=981578
Should have these drivers installed if you have rooted your Xoom before.
2) Make sure you have the latest SDK - adb and fastboot should be in /platform-tools - http://developer.android.com/sdk/index.html
Should have the android SDK if you have rooted your Xoom before.
3) Place all the downloaded stock image files into the SDK Tools folder.
4) If you are booting up from scratch, you can get the Xoom in fastboot mode by doing the following. Use command prompt to perform the rest of the steps
Hold VolDown and Power button will boot unit for fastboot mode
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash userdata userdata.img
fastboot erase cache
fastboot oem lock
If you Xoom is booted up already follow the commands below using command prompt to perform the steps
adb reboot bootloader <---- reboots the Xoom into fastboot mode.
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash userdata userdata.img
fastboot erase cache
fastboot oem lock
You noticed this too I see. Glad you posted this as a new thread. I was just randomly posting that link in threads where stock images may have helped.
I'm not home to try it yet but I'm guessing that's a US image?
Ahhhhh finally.
i just followed this process, everything worked on the xoom wifi (US), im back to stock and everything is ok so far.
but im an idiot and pressed vol up instead of down on the last step (oem lock) which aborted the oem lock step. before i did this i was rooted, so i think technically im still rooted.
can i simply go back into fastboot oem lock and try again and press the rightbutton this time to re lock the xoom or would that brick it?
ok thanks guys!
vista64 said:
i just followed this process, everything worked on the xoom wifi (US), im back to stock and everything is ok so far.
but im an idiot and pressed vol up instead of down on the last step (oem lock) which aborted the oem lock step. before i did this i was rooted, so i think technically im still rooted.
can i simply go back into fastboot oem lock and try again and press the rightbutton this time to re lock the xoom or would that brick it?
ok thanks guys!
Click to expand...
Click to collapse
If you want to be extra safe, start over from the beginning. You're probably still unlocked (but not rooted) if you managed to flash boot and system.
i have error failed to boot lnx 0x0004 - starting rsd mode 2
can i use this file ??
DinarQ8 said:
i have error failed to boot lnx 0x0004 - starting rsd mode 2
can i use this file ??
Click to expand...
Click to collapse
Only if you can get into fastboot mode AND your computer can see it. But if I recall, neither ADB, Fastboot nor RSD Lite will see your Xoom?
maybe solution i wait SBF file
Hi Scourge1024,
Are you going to try and flash the images to your Canadian Xoom AND then see if you can OEM re-lock it again??
I haven't been able to find out if all the WiFi images ie US, Canadian or European are all interchangeable on a Wifi only xoom??
I guess what I'd like to know is, if I ever wanted to re-lock my UK xoom, could I simply flash the Motorola MZ604_HWI69 files, then oem re-lock OR would have to wait for European Motorola backup files?
Cheers
Ody
what he said ^
Just tried downloading the Wi-fi files... On both my Mac and PC, it's saying it can't extract the ZIP. Crap crap crap crap crap...
If i remember correctly, scourge said that both devices are exactly the same hardware. Therefore flashing either version's set of images is irrelevant as long as you do WIFI for that model and 3G for that one.
odyseus said:
Hi Scourge1024,
Are you going to try and flash the images to your Canadian Xoom AND then see if you can OEM re-lock it again??
I haven't been able to find out if all the WiFi images ie US, Canadian or European are all interchangeable on a Wifi only xoom??
I guess what I'd like to know is, if I ever wanted to re-lock my UK xoom, could I simply flash the Motorola MZ604_HWI69 files, then oem re-lock OR would have to wait for European Motorola backup files?
Cheers
Ody
Click to expand...
Click to collapse
Nope. I'm done being the guinea pig (with the OEM locking). I bricked my first Xoom trying to OEM lock it. I managed to lock it a few times. Then I tried a different boot.img and bricked...
Personally, I have no issues flashing the US image on. It's just the re-locking. There's really no point to relock it. The Americans with the 3G/4G Verizon ones had to be able to relock for a hardware upgrade. I have managed to flash US images onto my Xoom but they were extracted by BeagleBoy here. I posted a comparison here: http://forum.xda-developers.com/showthread.php?p=13070124
The software is interchangable between the MZ604 Xoom models (Wi-fi only). There are a bunch of other Brits using the Canadian images I extracted from me and my friend's XOOMs. I've used the US ones. You just need to do a "fastboot -w" after flashing both the system and boot images because going between versions sometimes requires userdata to be wiped.
Scourge1024 said:
Just tried downloading the Wi-fi files... On both my Mac and PC, it's saying it can't extract the ZIP. Crap crap crap crap crap...
Click to expand...
Click to collapse
FYI,
$ md5sum MZ604_HWI69.zip
ae9b9f5693c4b49c745cb017afe1a4b5 MZ604_HWI69.zip
$ unzip -t MZ604_HWI69.zip
Archive: MZ604_HWI69.zip
warning [MZ604_HWI69.zip]: 36325409 extra bytes at beginning or within zipfile
(attempting to process anyway)
testing: MZ604_HWI69/boot.img OK
testing: MZ604_HWI69/recovery.img OK
testing: MZ604_HWI69/system.img OK
testing: MZ604_HWI69/userdata.img OK
No errors detected in compressed data of MZ604_HWI69.zip
You might be OK if you can get something that'll handle errors better.
In Windows, WinRar worked. On my Mac, I did what you posted and well, it seemed to work. I also did a compare against BeagleBoy's ripped images and boot was perfect. System was 1 byte off. Maybe a counter for the file system being mounted?
Code:
mac-mini:mz604_img Howard$ md5 MZ604_HWI69.zip
MD5 (MZ604_HWI69.zip) = ae9b9f5693c4b49c745cb017afe1a4b5
mac-mini:mz604_img Howard$ unzip -t MZ604_HWI69.zip
Archive: MZ604_HWI69.zip
warning [MZ604_HWI69.zip]: 36325409 extra bytes at beginning or within zipfile
(attempting to process anyway)
testing: MZ604_HWI69/boot.img OK
testing: MZ604_HWI69/recovery.img OK
testing: MZ604_HWI69/system.img OK
testing: MZ604_HWI69/userdata.img OK
No errors detected in compressed data of MZ604_HWI69.zip.
mac-mini:mz604_img Howard$
Scourge1024 said:
In Windows, WinRar worked. On my Mac, I did what you posted and well, it seemed to work. I also did a compare against BeagleBoy's ripped images and boot was perfect. System was 1 byte off. Maybe a counter for the file system being mounted?
Click to expand...
Click to collapse
Yep, IIRC, ext maintains a mount count. One'd need some file system tools to properly verify.
Can someone post a walk through on how to do this?
pricej636 said:
Can someone post a walk through on how to do this?
Click to expand...
Click to collapse
from the op:
Instructions to return it to stock
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash userdata userdata.img
fastboot erase cache
fastboot oem lock
Scourge1024 said:
Nope. I'm done being the guinea pig (with the OEM locking). I bricked my first Xoom trying to OEM lock it. I managed to lock it a few times. Then I tried a different boot.img and bricked...
Personally, I have no issues flashing the US image on. It's just the re-locking. There's really no point to relock it. The Americans with the 3G/4G Verizon ones had to be able to relock for a hardware upgrade. I have managed to flash US images onto my Xoom but they were extracted by BeagleBoy here. I posted a comparison here: http://forum.xda-developers.com/showthread.php?p=13070124
The software is interchangable between the MZ604 Xoom models (Wi-fi only). There are a bunch of other Brits using the Canadian images I extracted from me and my friend's XOOMs. I've used the US ones. You just need to do a "fastboot -w" after flashing both the system and boot images because going between versions sometimes requires userdata to be wiped.
Click to expand...
Click to collapse
Fair do's - I don't blame you! You've done enough As you say why re-lock on WiFi?
What I would really like to do is flash all the images to my UK WiFi Xoom and then try to install Bignadad's BigDX Xoom|Zoom Theme..
Previously flashing this theme soft-bricked my UK xoom - got loads of Force Closures. Installing the extracted images from you, still caused the same problem. Maybe it only works on the US WiFi Xoom, but I might re-flash with 'stock' ROM to see if that makes any difference? (I do have CWM nandroid backups in case of another soft brick!)
Cheers
Ody
Is there a risk with using these cause of zip extra bytes warning?
First, take your own risk!
Be sure you knwo what you are doing now and familiar with fastboot and your Xoom.
I am not responsible for anything.
The following founding are just proved to be work on my Xoom and I guarantee nothing.
===========================================
Rom Source:
Obtained from this thread
[!!Thanks changguangyu for his (and his fd's) kind sharing!!]
http://forum.xda-developers.com/showthread.php?p=21096478
Download the leaked rom
Extract the sbf using "MotoAndroidDepacker v1.3"
CG57.smg rename to recovery.img
CG58.smg rename to boot.img
CG59.smg rename to system.img
Issue the following command:
fastboot oem unlock
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot erase cache
fastboot erase userdata
fastboot reboot
Done.
Tried on my own Hong Kong Wifi version Xoom(MZ604).
Run smoothly.
can this be flash to canadian xoom ?
Probably can but I would probably wait for eos version with the good bits taken out....
Sent from my HTC Desire using xda premium
thanks ...good to go
In case somebody wondering where to find MotoAndroidDepacker
http://www.mediafire.com/?pk0gb8tgxg4uecg
Hello,
owning a Gedified french Xoom with stock ICS, I thought the official Jelly Bean OTA upgrade would be easy ... But it was not !
That's why I thought it would be good to make a little tutorial on how to do it.
There are 2 conditions for the OTA upgrade to work :
1) The recovery installed on your Xoom should be the STOCK ICS 4.04 one.
2) The bootloader must be LOCKED.
In my case, when I GEDified my Xoom, I left the bootloader unlocked after having flashed the Honeycomb U.S. image. There was no problem at this time, I could then easily upgrade upto ICS 4.04 with my bootloader unlocked. But when I tried to update with Jelly Bean, after the Xoom rebooted it was stuck with an image of the Android robot laying down ... It was impossible to do the upgrade. So I flashed the stock 4.04 Recovery, the installation of Jelly Bean could then go a little more further, but crashed again.
So I tried to re-lock the bootloader, but when done, when the Xoom rebooted it was stuck on an error message :
"failed image lnx 0x0002"
So in the case where your GEDified Xoom has still its bootloader unlocked, as you cannot re-lock it when running ICS, you only have one solution which will let you loose all your Xoom datas :
you need to unlock the bootloader, then re-flash the stock U.S. Honeycomb, then relock the bootloader, then re-apply all the Android updates upto Jelly Bean. At the end, your Xoom will be locked, unrooted, but running the stock Jelly Bean.
Here is how to do this :
Put all the HWI69 files into the same directory as the adb commands (I assume that you already know how to flash a ROM into the Xoom and you know where to download the ROM as your Xoom should have been already GEDified in the past), then open a dos commands window and do the following commands :
adb reboot bootloader (wait for the bootloader screen to be displayed).
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash userdata userdata.img
fastboot erase cache
fastboot oem lock
So as said earlier, then your Xoom will be running the stock Honeycomb but with a locked bootloader this time, which will then let you to update your Xoom upto Jelly Bean.
I hope this little Tutorial will help you.
So it means that if you have rooted your Xoom, you cannot update to Jelly Bean without reverting to stock Honeycomb and therefore loose your data ...
Now I will have to manually reinstall each software, one by one, from the market as no backup software works without root permission ...
If I knew that before installing ICS, I would think twice before rooting it !
Thanks
Thanks for this. I was in the same boat, ie UK GEDified Xoom with an unlocked bootloader...
As dizzy33 has said in the bottom of his post this seems to appear if you rooted your Xoom. If you only unlocked the boot loader to flash the US ROM to make you Xoom a GED and did not do the step to root it the OTA update will work successfully and your data won't be wiped.
Mark-IE said:
As dizzy33 has said in the bottom of his post this seems to appear if you rooted your Xoom. If you only unlocked the boot loader to flash the US ROM to make you Xoom a GED and did not do the step to root it the OTA update will work successfully and your data won't be wiped.
Click to expand...
Click to collapse
No, what you say is only partially true : on a GEDified Xoom you need to have a locked bootloader, otherwise the OTA will not work.
The problem of rooting a Xoom is that you need to unlock the bootloader, and you cannot re-lock a bootloader if your Xoom is running ICS.
That's why you need to go back to Honeycomb to re-lock the bootloader, and then proceed with all the upgrades upto Jelly Bean.
But there is still the root issue. You cannot gain root access.
dizzy33 said:
No, what you say is only partially true : on a GEDified Xoom you need to have a locked bootloader, otherwise the OTA will not work.
The problem of rooting a Xoom is that you need to unlock the bootloader, and you cannot re-lock a bootloader if your Xoom is running ICS.
That's why you need to go back to Honeycomb to re-lock the bootloader, and then proceed with all the upgrades upto Jelly Bean.
Click to expand...
Click to collapse
My boot loader was unlocked and the OTA worked fine so something else must have caused your problem.
Mark-IE said:
My boot loader was unlocked and the OTA worked fine so something else must have caused your problem.
Click to expand...
Click to collapse
Mine was unlocked and I did have the issue Rolled back to honeycomb, locked the bootloader and im now all JB'ed up. Odd.
I, too, have been going through this crapola with my Xoom WiFi. The culprit is the locked bootloader the HC laden Xoom shipped with (as are some of the HTC devices, which are also a PiTHB because of bootloader issues).
The only issue, albeit not a major one, is that the JB update after the OTA is not rooted. I suppose it is a matter of time before we get a JB custom ROM with root.
I had grown to like my ICS rooted, unlocked Xoom. Now the annoying JB OTA notice will not go away until I go back to HC.
---------- Post added at 09:20 PM ---------- Previous post was at 08:57 PM ----------
Forgot to mention that I have had no luck (YET) flashing stachre's Stock rooted JB build http://forum.xda-developers.com/showthread.php?t=1796335
dizzy33 said:
Hello,
owning a Gedified french Xoom with stock ICS, I thought the official Jelly Bean OTA upgrade would be easy ... But it was not !
That's why I thought it would be good to make a little tutorial on how to do it.
There are 2 conditions for the OTA upgrade to work :
1) The recovery installed on your Xoom should be the STOCK ICS 4.04 one.
2) The bootloader must be LOCKED.
In my case, when I GEDified my Xoom, I left the bootloader unlocked after having flashed the Honeycomb U.S. image. There was no problem at this time, I could then easily upgrade upto ICS 4.04 with my bootloader unlocked. But when I tried to update with Jelly Bean, after the Xoom rebooted it was stuck with an image of the Android robot laying down ... It was impossible to do the upgrade. So I flashed the stock 4.04 Recovery, the installation of Jelly Bean could then go a little more further, but crashed again.
So I tried to re-lock the bootloader, but when done, when the Xoom rebooted it was stuck on an error message :
"failed image lnx 0x0002"
So in the case where your GEDified Xoom has still its bootloader unlocked, as you cannot re-lock it when running ICS, you only have one solution which will let you loose all your Xoom datas :
you need to unlock the bootloader, then re-flash the stock U.S. Honeycomb, then relock the bootloader, then re-apply all the Android updates upto Jelly Bean. At the end, your Xoom will be locked, unrooted, but running the stock Jelly Bean.
Here is how to do this :
Put all the HWI69 files into the same directory as the adb commands (I assume that you already know how to flash a ROM into the Xoom and you know where to download the ROM as your Xoom should have been already GEDified in the past), then open a dos commands window and do the following commands :
adb reboot bootloader (wait for the bootloader screen to be displayed).
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash userdata userdata.img
fastboot erase cache
fastboot oem lock
So as said earlier, then your Xoom will be running the stock Honeycomb but with a locked bootloader this time, which will then let you to update your Xoom upto Jelly Bean.
I hope this little Tutorial will help you.
So it means that if you have rooted your Xoom, you cannot update to Jelly Bean without reverting to stock Honeycomb and therefore loose your data ...
Now I will have to manually reinstall each software, one by one, from the market as no backup software works without root permission ...
If I knew that before installing ICS, I would think twice before rooting it !
Thanks
Click to expand...
Click to collapse
Hi
I wonder if you could help
I have a stock UK Xoom on ICS
I have been trying to get it to jellybean using this method
I have used these commands successfully
adb reboot bootloader
fastboot oem unlock
it's at
fastboot flash boot boot.img
I get stuck
The xoom is in debug mode and when I run this command all I get is "waiting for device"
What am I doing wrong
Thanks
Hi all,
on my Nexus 9, update to LRX21Q failed: After reboot, the android icon was shown with "error" below.
I suppose, update failed as my system is rooted with the method Chainfire posted in the development forum.
After an additional reboot, the previous firmware is still shown. The system does not offer the update anymore but claims to be up-to-date.
Any hints? Thanks in advance.
Maybe it's the modified kernel from Chainfire. Try to get back to the stock kernel and try again.
Download the factory image, flash recovery, boot, system & vendor.
Your software will be updated and you won't lose any data. You will lose root however.
I got the same error from OTA with no root. Only had 9 for 2 days, got OTA rite out of box no issue.
Yesterday for new build i get little error android icon upon reboot/install.
Obviously, something that is being changed by the "root" process is being checked DURING the update process. Probably a checksum on the boot partition. If it doesn't match, it bails on the update.
The likely reason for this is they acknowledge that you don't want to lose your root.
All it means is that you need to do the update manually.
It may be possible for a modified recovery to bypass this check, or possibly even be made to auto-root new boot images.
Thanks, guys. Will try as suggest above and post results.
Update: worked perfectly, needed to root again though.
StuMcBill said:
Download the factory image, flash recovery, boot, system & vendor.
Your software will be updated and you won't lose any data. You will lose root however.
Click to expand...
Click to collapse
has anyone tried this? i would like to update without losing data...
Flash through fastboot and you will be fine. Thats what I did then rerooted with CF autoroot
mk92595 said:
Flash through fastboot and you will be fine. Thats what I did then rerooted with CF autoroot
Click to expand...
Click to collapse
What's the fastboot command for the img? Do you flash as boot, system, etc?
zeebone said:
What's the fastboot command for the img? Do you flash as boot, system, etc?
Click to expand...
Click to collapse
Fastboot flash bootloader bootloader.img
Fastboot reboot-bootloader
Fastboot flash system system.img
Fastboot reboot-bootloader
Fastboot flash boot boot.img
Fastboot reboot-bootloader
Fastboot flash vender vendor.img
Fastboot reboot-bootloader
Fastboot erase cache
Fastboot flash cache cache.img
Fastboot reboot
Not sure if I forgot one but I think thats all of them
mk92595 said:
Fastboot flash bootloader bootloader.img
Fastboot reboot-bootloader
Fastboot flash system system.img
Fastboot reboot-bootloader
Fastboot flash boot boot.img
Fastboot reboot-bootloader
Fastboot flash vender vendor.img
Fastboot reboot-bootloader
Fastboot erase cache
Fastboot flash cache cache.img
Fastboot reboot
Not sure if I forgot one but I think thats all of them
Click to expand...
Click to collapse
Should there be a - sign between reboot and bootloader .. And is fastboot flash vender or vendor... Just making sure .
pantmunu said:
Should there be a - sign between reboot and bootloader .. And is fastboot flash vender or vendor... Just making sure .
Click to expand...
Click to collapse
Yes there should be a - sign and vendor. Sorry i'm not home so I don't have the files near me.
mk92595 said:
Yes there should be a - sign and vendor. Sorry i'm not home so I don't have the files near me.
Click to expand...
Click to collapse
Thank you sir .
Where can i find the images for download. Thx
Google for nexus factory image.
Sent from my Nexus 9 using XDA Premium HD app
Update failed on me too. Completely stock
UPDATE:
Apparently *some* devices didn't get the recovery updated with the last update (LRX21L).
The new update (LRX21Q) requires the newer version of the recovery to install.
Google really messed up the launch of the Nexus 9 with all the HW/SW quality control issues
Serious f#ck-up from Google really
Interesting thing I noticed: I restored factory images manually in order to unroot and the OTA was no longer available. I verified I was still running on L. I manually installed the update and it went in just fine.
Now waiting on the root package to be updated for the Q kernel. You can re-root but you will be running on the L kernel, not the Q kernel.
maarten08 said:
Update failed on me too. Completely stock
Click to expand...
Click to collapse
My too fck Google
Mine failed and Im not even rooted
And im not sure if it did the update as its not showing a new one. Im on L
LTE version:
https://dl.google.com/dl/android/aosp/volantisg-lmy48m-factory-bcd49c4e.tgz
md5sum: 6763b300481f5499e52bbd31b203f501
sha1sum: bcd49c4e9f0a912026065074c89d1bbbd8cbca31
---------------------------------
WiFi version:
https://dl.google.com/dl/android/aosp/volantis-lmy48m-factory-3ae75e8e.tgz
md5sum: 6c6ccd7d96514ba1090ec8cf4bda7365
sha1sum: 3ae75e8e444123e4c9c22b755e16e5bcc5652123
Talk about good timing! I literally just checked into the forums to see if a new image had been out.
I'm guessing no one has tried to flash + root again? I just use the factory image on mine anyways, currently at LMY48I
Well, since no one else has jumped on board yet and I always hate it when there's not a consolidated "How To"...
Starting from a rooted stock LMY48I -
adb reboot bootloader
<Reboots>
fastboot flash bootloader bootloader-flounder-3.44.1.0123.img
fastboot reboot-bootloader
<Reboots>
fastboot flash boot boot.img
fastboot flash cache cache.img
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot flash vendor vendor.img
< Reboot into Android >
Successfully rebooted into 5.1.1, "Android is upgrading..." , verified LMY48M Build number
adb reboot bootloader
<Reboots>
fastboot boot CF-Auto-Root-flounder-volantis-nexus9.img
<Red Android + Reboot>
<"Android is starting">
Rooted + validated LMY48M again! Apps + Data were retained.
Any improvement in memory ????
Less redraws, high ram usage ???
I'm good / happy until the final release.
HasnaCuz said:
Any improvement in memory ????
Less redraws, high ram usage ???
Click to expand...
Click to collapse
So far nothing noticeable, though I haven't really had a chance to play with it too terribly much thanks to work. Hopefully I'll get some playtime over this upcoming weekend! Offhand I didn't notice anything.
My understanding is that it is just a security update. Hoping the next one will be M!
Do we have link to download OTA?
I'm currently running it, its OK thank God now my tab is not vulnerable from stage fright that was the point of update, security fixes, redraws and memory leaks are still alive
After I installed this with adb/fastboot I can't turn off the tablet. Turn off button just makes the tablet reboot. I klick in the turn off button then the spinning circle spin for a second then freezes and after than the tablet reboots. The only way to turn it off is to boot into bootloader and turn it off from there :/
Am I safe jumping two releases flashing manually? Or do I have to install the prior update, *then* this one? (currently running LMY47X)
Also stupid question, but an unlocked bootloader stays unlocked after flashing the new version, right?
xfullmetal17 said:
Am I safe jumping two releases flashing manually?
Unlocked bootloader stays unlocked after flashing the new version, right?
Click to expand...
Click to collapse
Yes and Yes.
Sent from my Nexus 9
HasnaCuz said:
I'm currently running it, its OK thank God now my tab is not vulnerable from stage fright that was the point of update, security fixes, redraws and memory leaks are still alive
Click to expand...
Click to collapse
Took me awhile to make back to the thread.
But yeah Performance is still the same.
Anyone have a no forced encryption boot img link?
Is there anywhere a flashable zip of the latest update?
figured out how to do this ...
unencrypted LMY48M for wifi : https://www.dropbox.com/s/tjdaz3wdsn85525/flounder-wifi-lmy48m-noencrypt.zip?dl=0
TheMuffnMan said:
Well, since no one else has jumped on board yet and I always hate it when there's not a consolidated "How To"...
Starting from a rooted stock LMY48I -
adb reboot bootloader
<Reboots>
fastboot flash bootloader bootloader-flounder-3.44.1.0123.img
fastboot reboot-bootloader
<Reboots>
fastboot flash boot boot.img
fastboot flash cache cache.img
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot flash vendor vendor.img
< Reboot into Android >
Successfully rebooted into 5.1.1, "Android is upgrading..." , verified LMY48M Build number
adb reboot bootloader
<Reboots>
fastboot boot CF-Auto-Root-flounder-volantis-nexus9.img
<Red Android + Reboot>
<"Android is starting">
Rooted + validated LMY48M again! Apps + Data were retained.
Click to expand...
Click to collapse
Thanks, MuffinMan. Where/what is CF-Auto-Root-flounder-volantis-nexus9.img?
eecummings said:
Thanks, MuffinMan. Where/what is CF-Auto-Root-flounder-volantis-nexus9.img?
Click to expand...
Click to collapse
https://download.chainfire.eu/595/CF-Root/CF-Auto-Root/CF-Auto-Root-flounder-volantis-nexus9.zip
Download link is at the bottom
Are these steps likely to still be valid for upgrading to Marshmallow (for a rooted, but otherwise stock Nexus 9)?