Database Users

Why cant they give us MZ602.SBF FILES!!!!

********************************************UPDATE01/17/12***************************************************************************
Allrighty then finally found a fix that is 10x easier to fix ur 4g/lte
1)Unlock bootloader
2)download RSD v5.4.4 and MZ602 .SBF files from my dropbox below
3)use RSD to flash back to stock 3.2.2 should be back and baseband should allow it be shown if not just do a factory reset and after boot up, it should be fixed!!!
BOOTLOADER 1.50
http://dl.dropbox.com/u/47975216/LTE-Baseband.zip
MZ602 .SBF 3g/4g BASEBAND STOCK FIX use the latest RSD v5
http://dl.dropbox.com/u/47975216/VZ...00_03.1A.54_signed_LTEDC_U_05.19.00.combo.rar
RSD VERSION 5.4.4
http://dl.dropbox.com/u/47975216/RSDLite 5.4.4.msi
if baseband does not show go into settings privacy and do a factory reset should fix xoom back to 3.2.2 with radio working
"Its one thing to thank somebody just hit the button and make it a true thank you!"

Thanks a lot!!!
BTW, stuck on the "Starting LTE (USB2) Software Bypass Mode"
ended up RSD says "Phone disconnected"
my Xoom managed to boot though but it doesn't seem to help flash the baseband

Do you flash the bootloader ZIP in ClockworkMod or stock recovery? I would assume stock recovery since the updater script uses a motorola flash function that I would assume is not built into ClockworkMod.

oldblue910 said:
Do you flash the bootloader ZIP in ClockworkMod or stock recovery? I would assume stock recovery since the updater script uses a motorola flash function that I would assume is not built into ClockworkMod.
Click to expand...
Click to collapse
My bootloader is actually v1.50 so there is no need to flash it

Yes but there may be in the future, thus the question.

I would reccomend to just reflash anyways even if your bootloader is at 1.5, I only did this because I flashed 1.35 everest when I f'ed up my xoom from the start

That's my point. So how do you flash it? ClockworkMod or stock recovery? Given that the update script uses some kind of Motorola function to flash the bootloader, I'm assuming stock since I doubt ClockworkMod has Motorola functions built into it. On the off chance that I'm wrong though, can someone verify?
Sent from my Xoom using Tapatalk

oldblue910 said:
That's my point. So how do you flash it? ClockworkMod or stock recovery? Given that the update script uses some kind of Motorola function to flash the bootloader, I'm assuming stock since I doubt ClockworkMod has Motorola functions built into it. On the off chance that I'm wrong though, can someone verify?
Sent from my Xoom using Tapatalk
Click to expand...
Click to collapse
Hey bro just give some time I'll make a in depth tutorial seems like you your going to have to flash back to 3.0 flash the 1.50 boot then go back and flash the mz602
Sent from my Xoom using Tapatalk

amysdadforever said:
Hey bro just give some time I'll make a in depth tutorial seems like you your going to have to flash back to 3.0 flash the 1.50 boot then go back and flash the mz602
Sent from my Xoom using Tapatalk
Click to expand...
Click to collapse
Actually, if you use the bootloader image in combination with the SBF and 3.2.2 fastboot images from developer.motorola.com/xoomsoftware, you can flash back to totally stock with the 1.50 bootloader and the original LTE radio without having to flash back to 3.0.
For my MZ602, I just did the following tonight:
Go into ClockworkMod and flash the bootloader.
Reboot and watch the bootloader update screen.
When it reboots automatically, keep pressing down until you get the prompt.
Go into Fastboot mode.
Fastboot flash the 3.2.2 images (boot, system, recovery, and userdata) for MZ602 found at http://developer.motorola.com/xoomsoftare
Do a fastboot erase cache.
Powercycle the Xoom.
Press down on the bootloader until you get the prompt.
This time go into RSD mode.
Fire up RSD Lite on your PC, load up the SBF file, and press start.
Let it go.
When it's done, you'll be on stock 3.2.2 with the original LTE radio and original bootloader.
Oh, and cool that you're from Clovis. I was born and raised in Madera.

oldblue910 said:
Actually, if you use the bootloader image in combination with the SBF and 3.2.2 fastboot images from developer.motorola.com/xoomsoftware, you can flash back to totally stock with the 1.50 bootloader and the original LTE radio without having to flash back to 3.0.
For my MZ602, I just did the following tonight:
Go into ClockworkMod and flash the bootloader.
Reboot and watch the bootloader update screen.
When it reboots automatically, keep pressing down until you get the prompt.
Go into Fastboot mode.
Fastboot flash the 3.2.2 images (boot, system, recovery, and userdata) for MZ602 found at http://developer.motorola.com/xoomsoftare
Do a fastboot erase cache.
Powercycle the Xoom.
Press down on the bootloader until you get the prompt.
This time go into RSD mode.
Fire up RSD Lite on your PC, load up the SBF file, and press start.
Let it go.
When it's done, you'll be on stock 3.2.2 with the original LTE radio and original bootloader.
Oh, and cool that you're from Clovis. I was born and raised in Madera.
Click to expand...
Click to collapse
Oh cool saves me the troubles of making a tut thanks bro and good job on the fix. I guess your fix does well and yeah awesome why east coast tired of the farms

oldblue910 said:
Actually, if you use the bootloader image in combination with the SBF and 3.2.2 fastboot images from developer.motorola.com/xoomsoftware, you can flash back to totally stock with the 1.50 bootloader and the original LTE radio without having to flash back to 3.0.
For my MZ602, I just did the following tonight:
Go into ClockworkMod and flash the bootloader.
Reboot and watch the bootloader update screen.
When it reboots automatically, keep pressing down until you get the prompt.
Go into Fastboot mode.
Fastboot flash the 3.2.2 images (boot, system, recovery, and userdata) for MZ602 found at http://developer.motorola.com/xoomsoftare
Do a fastboot erase cache.
Powercycle the Xoom.
Press down on the bootloader until you get the prompt.
This time go into RSD mode.
Fire up RSD Lite on your PC, load up the SBF file, and press start.
Let it go.
When it's done, you'll be on stock 3.2.2 with the original LTE radio and original bootloader.
Oh, and cool that you're from Clovis. I was born and raised in Madera.
Click to expand...
Click to collapse
The point is have you seen the "Start LTE Software Bypass Mode" screen? And how did you pass through it? Because when my xoom boot into that screen, it lost connection with my computer(I checked the "Device Manager" actually, there is no unknown devices, no motorola flash interface, etc..)
So what operating system you are using? (I tried both Windows XP and Win7 64bits) And what's the cable you are using(stock cable or program cable)? Also did you plug your power when flash? Did you pull out your sim card? etc..

Its Work with MZ605/MZ601 3G ?

DragonEarth said:
Its Work with MZ605/MZ601 3G ?
Click to expand...
Click to collapse
It will definitely brick your xoom, don't ever try that.

DragonEarth said:
Its Work with MZ605/MZ601 3G ?
Click to expand...
Click to collapse
NOOO! This is for MZ602 (Verizon US 4G LTE version) ONLY!!! If you try this on ANY other Xoom model, you will brick it. Plain and simple.
---------- Post added at 11:18 AM ---------- Previous post was at 11:17 AM ----------
kerry_xu_cs said:
The point is have you seen the "Start LTE Software Bypass Mode" screen? And how did you pass through it? Because when my xoom boot into that screen, it lost connection with my computer(I checked the "Device Manager" actually, there is no unknown devices, no motorola flash interface, etc..)
So what operating system you are using? (I tried both Windows XP and Win7 64bits) And what's the cable you are using(stock cable or program cable)? Also did you plug your power when flash? Did you pull out your sim card? etc..
Click to expand...
Click to collapse
When it got to that screen for me, it lost connection temporarily, then found the device again, installed the motorola driver for it, and kept on going.

Nexus S Official factory images for 9020t & 9023

http://code.google.com/android/nexus/images.html#yakju
https://groups.google.com/forum/?fromgroups#!topic/android-building/b50nY_onbP4

^Thanks.
This can be flashed via CWM recovery ?
(after a 'fastboot oem lock/unlock' ?)

No. They are fastboot images. If you're not sure what these are and how to use them then I would not mess with them.

^ gotcha
can someone please put up a tutorial/guide to do this.
I really want to try this.

The shell script gives you the exact fastboot commands to run if you want to do it manually. And it will restore your phone to a true factory state with 4.0.4.

if i will use the factory img the baseband version in bootloader will be change? i see now i9020xxkl1 but my nexus is i9023?

I was wondering the same .. In the zip it says :require board=herring
require version-bootloader=I9020XXJK1|I9020XXKA3|I9020XXKI1|I9020XXKL1
require version-baseband=I9020XXJK8|I9020XXKB1|I9020XXKD1|I9020XXKF1|I9020XXKI1|I9020UCKB2|I9020UCKD1|I9020UCKF1|I9020UCKJ1|I9020KRKB3|M200KRKC1
So it should be okay , because when I reboot into the bootloader of my phone it says :
Bootloader version: I9020XXKL1
Baseband version : I9020XXKI1
My phone actually is a I9023 so I gues the images are okay to flash on a I9023

Just noticed that the full ROM version for Nexus S is 4.0.4 IMM76D. Wouldn't be better to flash this complete rom instead of the partial patch OTA which is clearly giving troubles?

HELPPPPP
can someone please put up a tutorial/guide to do this.
I really want to try this.

i wrote a guide
http://forum.xda-developers.com/showthread.php?t=1572307

goldy_rocky said:
can someone please put up a tutorial/guide to do this.
I really want to try this.
Click to expand...
Click to collapse
(No time to write a full tutorial right now but...) I'd say...
Pls wait for someone experimented to confirm what I say because I couldn't try it to confirm it works right now... And also try it at your own risk...
If your bootloader is not unlocked, follow PART 1 & PART 2 of this tutorial. (you will loose data)
(Note that ADB is not in tools folder anymore but in /platform-tools so that's where the part2 cmd as to be runned from)
Then if windows (I guess you would know what to do if on Linux) use 7zip to extract (2 times) all files from the archive.
Then copy the files to the /platform-tools folder.
The open a command prompt in that folder (shift+right click>open a command prompt here).
Then use the commands provided in the .sh script to flash all files (you can read it easily with Notepad++ for instance) one by one...
Note I don't think you can run the "sleep 5" cmd manually but you can of course wait 5' manually .
Code:
fastboot flash bootloader bootloader-crespo-i9020xxkl1.img
fastboot reboot-bootloader
sleep 5
fastboot flash radio radio-crespo-i9020xxki1.img
fastboot reboot-bootloader
sleep 5
fastboot -w update image-soju-imm76d.zip
I'm not really sure if bootloader will be locked at this time but my guess is no so just reboot the bootloader ("fastboot reboot-bootloader" or shut down the device then "Boot the SNS into the Bootloader Interface, by holding Volume UP & Power button" and look for the "LOCK STATE - LOCKED" or "LOCK STATE - UNLOCKED").
If "LOCK STATE - UNLOCKED" you may want to lock the bootloader again, just follow part2 again and replace "fastboot oem unlock" by "fastboot oem lock"
EDIT :
ale.landra91 said:
i wrote a guide
http://forum.xda-developers.com/showthread.php?t=1572307
Click to expand...
Click to collapse
You just made me feel so useless ...

First of all, the credits goes to "a2b". I am only put his work here via a link.
Secondly, PLEASE KEEEP IN YOUR MIND THAT NEITHER ME OR "a2b" IS RESPONSABLE FOR ANY LOSS OF YOURS IF YOUR PHONE GET BRICKED.
The thrid, I have tried the method on my Nexus i9023. It works perfectly for me. BUT, I cannot gurentee it works for everyone.
Okay, I just flashed the factory img according to a2b's tutorial for Galaxy Nexus. But for me I just needed to change the names for few files. If you cannot figure out what to change, I suggest you follow albundy2010's advice on post #3
Good luck!
http://androidtobe.blogspot.com/2011/12/galaxy-nexus-installing-ics-402-from.html

Seems most are not familiar with doing this so here are some things you should know.
Doing this will wipe EVERYTHING off your phone. Yes, everything including /sdcard.
Do not be a fool and flash these images to the 4g.
I am not certain about this and if you it and your phone gets messed up do not blame me.
The 9020a should be able to run this factory image. Check to see what version of the bootloader you have. If it matches one of the bootloaders in the .sh script you should be fine. I would NOT flash the bootloader included in this factory image myself. Since I do not know for sure if they are the same for both GSM models. If you follow the guide minus the parts where you flash the bootloader and the radio image I believe it will work.
Again if you try this and it breaks your phone that is on you. I am not responsible for it. I do not have a 9020a to test this on and verify it. I am fairly certain it will work perfectly. If anybody tries it let me/us know the outcome.

is there any specific advantage in flashing the factory image as opposed to flashing the incremental update ? I successfully flashed 4.0.4 using CWR over a full rom installation of 4.0.3 back from December. I wonder if there may be some subtle differences that maybe make it a bit better option to install the factory image ?

mindwalkr said:
is there any specific advantage in flashing the factory image as opposed to flashing the incremental update ? I successfully flashed 4.0.4 using CWR over a full rom installation of 4.0.3 back from December. I wonder if there may be some subtle differences that maybe make it a bit better option to install the factory image ?
Click to expand...
Click to collapse
No
Sent from my Nexus S using XDA App

I used the flash-all.sh script from the factory image file and it didn't wipe the sdcard. Backed it up beforehand anyway just in case. Recovery was broken on reboot. Flashed CWM recovery and all good. i9023.

[GUIDE] [XOOM2/XYBoard]: How to update Xyboard wifi (MZ615) to Jelly Beam (4.1.2)

Warning:
1. This guide comes with ABSOLUTELY NO WARRANTY. I'm not responsible for your data, your Xyboard, your girlfriend or something else . But report at this thread if you have problem. I will try to improve this guide.
2. Follow every step of these instructions carefully.
3. Everytime you reboot or power on your Xyboard, it will stuck at boot screen with warning "CustomerID error, Contact Dealer...", And you need press "+", "-" volume key and "power key" simultaneously to boot. Because you need clear "cid" of your Xyboard to flash this rom.
4. Sorry for my terrible English. I'm Vietnamese
Start:
1. Download Jelly Beam fastboot file for Droid Xyboard (MZ617): [URL="http://www.teamblackhat.net/t...T_127-127-release-keys-cid2-Verizon-US.tar.gz[/URL] Extract by 7z to hard drive.
2. Download this file: [URL="https://dl.dropboxusercontent.com/u/22090623/MZ615%20guide/MZ615.7z%5B/URL%5D"]https://dl.dropboxusercontent.com/u/22090623/MZ615%20guide/MZ615.7z[/URL] (included moto_fasboot, fake_cid, adb. I'm sorry for "license", "rights" because I'm collect it from many thread on many forums. Thereforce I'm can not remember the authors of those). Extract to same folder with fastboot file at step 1.
3. Download and install RDS lite, Motorola Device Manager (google for links, sorry).
4. Backup and Reset your Xyboard.
5. Install Terminal Emulator (free on Google Play)
6. Backup your cid (very be carefully, more information here: How to update you Razr (Gsm) To Official Jelly Bean - xda-developers)
6.a. Open Terminal Emulator
6.b. Run one by one:
su
cd /dev/block
dd if=/dev/block/mmcblk1p15 of=/sdcard/cid.img
Click to expand...
Click to collapse
6.c. Copy "cid.img" file from your Xyboard to safe location (you should keep at least 2 copy on diffirent location, backup on cloud or store it in somewhere safe). Double check this step.
7. Change your cid
7.a. Copy "fake_cid" file from folder you created in step 1 to your Xyboard.
7.b. Connect Xyboard to your PC, enable USB debbuging.
7.c. Open terminal on PC (Windows + R: cmd), "cd" to folder you created in step 1. Run one by one:
adb shell
cat /sdcard/fake_cid > /dev/block/mmcblk1p15
exit
Click to expand...
Click to collapse
8. Shutdown your Xyboard. Press and keep "-" volume key => press Power key => release 2 keys => your Xyboard will boot in fastboot mode.
9. Flash your Xyboard to Jelly Beam
9.a. Open terminal on PC (Windows + R: cmd), "cd" to folder you created in step 1.
9.b. Run one by one
moto-fastboot flash motoboot motoboot.img
moto-fastboot reboot-bootloader
moto-fastboot flash devtree device_tree.bin
moto-fastboot flash boot boot.img
moto-fastboot flash system system.img
moto-fastboot flash logo.bin logo.bin
moto-fastboot flash cdrom cdrom
moto-fastboot flash preinstall preinstall.img
moto-fastboot -w
moto-fastboot reboot
Click to expand...
Click to collapse
10. Your Xyboard will reboot and stuck at boot screen with warning "CustomerID error, Contact Dealer...". Press "+", "-" volume key and "power key" simultaneously to boot.
Now you are get Jelly Beam.
#######################################
Update: Restore to ICS
11. Restore cid
11.a. Copy cid.img file (created in step 6) to folder c:\mz615.
11.a. Open terminal on PC (Windows + R: cmd), "cd" to folder c:\mz615.
11.b. Run one by one
moto-fastboot flash cid cid.img
moto-fastboot reboot
Click to expand...
Click to collapse
12. Restore to ICS: do it with RSD Lite (you can found a lot of guide on XDA)

OMG thank you very much!
I have the MZ607 though. It's the non-lte version. Should the procedure be the same? (i know the fastboot files would be different but does the cid number matter at all if I have a wi-fi only device?)
EDIT: I'm dumb sorry. MZ615 doesn't have lte/3G either. Though I would need the MZ609 fastboot files to do this. Where can I find them?

Did anybody try this already?
Is it really working?

pexlibanis said:
Did anybody try this already?
Is it really working?
Click to expand...
Click to collapse
I would but I have the MZ607 and need the MZ609 file (8.2" version)

I success update my Xyboard. Now it working like a charm.
Sent from my MZ615 (4.1.2) using xda app-developers app

DHD said:
I success update my Xyboard. Now it working like a charm.
Sent from my MZ615 (4.1.2) using xda app-developers app
Click to expand...
Click to collapse
please help me find fastboot file to my version of the tablet.

Can i use this fake CID to flash my MZ616 with MZ617 firmware? I think the only different of MZ616 and MZ617 is the gsm radio and additional sd card in MZ616 compared to verizon xyboard mz617.

GSh0ck said:
Can i use this fake CID to flash my MZ616 with MZ617 firmware? I think the only different of MZ616 and MZ617 is the gsm radio and additional sd card in MZ616 compared to verizon xyboard mz617.
Click to expand...
Click to collapse
Would affect me too

@DHD,
Can you confirm that if you have a working usb connection(mtp) ith pc after cid deletion? I knew someone would come up with this solution. Thank you for the guide.

mtvdeo said:
OMG thank you very much!
I have the MZ607 though. It's the non-lte version. Should the procedure be the same? (i know the fastboot files would be different but does the cid number matter at all if I have a wi-fi only device?)
EDIT: I'm dumb sorry. MZ615 doesn't have lte/3G either. Though I would need the MZ609 fastboot files to do this. Where can I find them?
Click to expand...
Click to collapse
Hi,
I tried with MZ607, but the files aren't accepted by fastboot. When I try to flash the files I got an error of verification failure.

Flashable for XOOM 2 MZ616?
Is it possible to flash it on my XOOM 2 MZ616? Desperately need an update... :crying:

justmoto92 said:
Is it possible to flash it on my XOOM 2 MZ616? Desperately need an update... :crying:
Click to expand...
Click to collapse
Come on, any good cook will find the solution for us, MZ616... : D

Semseddin said:
@DHD,
Can you confirm that if you have a working usb connection(mtp) ith pc after cid deletion? I knew someone would come up with this solution. Thank you for the guide.
Click to expand...
Click to collapse
I will try it tonight and report after that.
mtvdeo said:
please help me find fastboot file to my version of the tablet.
Click to expand...
Click to collapse
Sorry, I don't have it...
chentz78 said:
Hi,
I tried with MZ607, but the files aren't accepted by fastboot. When I try to flash the files I got an error of verification failure.
Click to expand...
Click to collapse
Becase you not clear CID before flash new rom.
GSh0ck said:
Can i use this fake CID to flash my MZ616 with MZ617 firmware? I think the only different of MZ616 and MZ617 is the gsm radio and additional sd card in MZ616 compared to verizon xyboard mz617.
Click to expand...
Click to collapse
justmoto92 said:
Is it possible to flash it on my XOOM 2 MZ616? Desperately need an update... :crying:
Click to expand...
Click to collapse
Give it a try I did not have MZ616 but someone reports this rom works on MZ616 without nees clear CID.
Remember DO NOT flash radio.
If you want flash back to ICS room, just flash or "copy" back original CID afterthat flash ICS rom with RDS Lite.

DHD said:
I will try it tonight and report after that.
Sorry, I don't have it...
Becase you not clear CID before flash new rom.
Give it a try I did not have MZ616 but someone reports this rom works on MZ616 without nees clear CID.
Remember DO NOT flash radio.
If you want flash back to ICS room, just flash or "copy" back original CID afterthat flash ICS rom with RDS Lite.
Click to expand...
Click to collapse
I had try to flash the system img from MZ617 into the MZ616 but fail to do so. Do you think if i flash the boot.img, it will allow me to flash the system.img?

DHD said:
I will try it tonight and report after that.
Sorry, I don't have it...
Becase you not clear CID before flash new rom.
Give it a try I did not have MZ616 but someone reports this rom works on MZ616 without nees clear CID.
Remember DO NOT flash radio.
If you want flash back to ICS room, just flash or "copy" back original CID afterthat flash ICS rom with RDS Lite.
Click to expand...
Click to collapse
Yes, I clear my CID with fake_cid. But without success.

I wonder what was done to the " fake_cid" to make it a fake cid because CID partition is unique and it can't be flashed from other phones in any OMAP4 motorola.

Semseddin said:
I wonder what was done to the " fake_cid" to make it a fake cid because CID partition is unique and it can't be flashed from other phones in any OMAP4 motorola.
Click to expand...
Click to collapse
"fake_cid" is "empty" cid. It's a trick to clear cid if you can not clear cid by adb shell.
Thereforce I think (and already tried on my MZ615) "face_cid" can use on any device if you determine exactly "CID" partition.

I hope someone provides the fastboot file for my MZ607 (I would need the MZ609 ones).

I just followed the guide on my MZ615 and it works flawlessly!
Also, in my case, when I get the initial error about the customer ID thing, I do not have to press -, +, and power button. If I just wait it continues booting normally after a while.
Thanks DHD!

MZ607 and MZ608 owners: you can have jelly bean too!
Find an ICS fastboot (there is no JB one yet), install it as if you were installing from the guide on page one. It might not work in normal mode, so go to BP tools and from then set it up and download the ota update. Then it will install it and work.
This is everything I did to my MZ607. It worked for me, and I'm no developer so please don't blame me for damage:
0. Mistakenly flashed honeycomb from verizon using the method on page one (CID + fastboot)
----HERE comes what matters, the actual GUIDE---
1. Found on a russian forum an ICS verizon fastboot so flash it like the guide on page one and do the CID thing before: http://translate.google.com/transla...da.ru/forum/index.php?showtopic=390298&st=560
TIP: moto-fastboot flash recovery recovery.img might be needed if you mistakenly flashed a honeycomb firmware
like me. But do it anyway if you have the ICS fastboot.
TIP 2: device_tree.bin comes with the fastboot you will download. The one from the OP doesn't work with this device. So use the one in the russian link fastboot.
3. Set up account on BP tools because normal mode didn't work for me.
4. From there downloaded OTA and it installed by itself.
I'm on JB now!

[Q] Slate 7 Extreme root,flash question

Hi, I am a happy owner of the HP Slate 7 Extreme which is basically the same device as you guys are using.I am still on the 4.2 Jelly bean since HP are not pushing over the air updates with our devices.I want to use the script from the development forum "[Script] [Utility] Nvidia Tegra Note 7 Kitkat Unlock BL, Restore, Recovery, & Root", I want to know if anyone has tried to use it with the Slate Extreme or if it simply should work on the Jelly Bean aswell. Thanks guys.

still have freeze/hang issue..
http://forum.xda-developers.com/showthread.php?t=2663449&page=2

mofared said:
still have freeze/hang issue..
http://forum.xda-developers.com/showthread.php?t=2663449&page=2
Click to expand...
Click to collapse
What about the 4.3+ ?

crazyhacker202 said:
What about the 4.3+ ?
Click to expand...
Click to collapse
i have not test that yet but i believe it should work because i have tested the 4.4.2 and 4.2.2 evga ROM from here using the cwm install from sdcard method..
http://forum.xda-developers.com/showthread.php?t=2627671
The only thing that puzzles me now is i am unable to perform a system recovery from HP update.zip using cwm.
http://h10025.www1.hp.com/ewfrf/wc/...en&cc=us&dlc=en&sw_lang=&product=6608632#N147
So right now i am stuck with 4.2.2 evga ROM all is good and functional.
I have read some post that by updating OTA fix issue in 4.4 but i have no idea on how to get the OTA update.
p/s: This is my first tablet and root attempt...
edit:
i found out that rootjunky has already released the 4.4.2 with 2.3 OTA i will give it a try and feedback later

mofared said:
i have not test that yet but i believe it should work because i have tested the 4.4.2 and 4.2.2 evga ROM from here using the cwm install from sdcard method..
http://forum.xda-developers.com/showthread.php?t=2627671
The only thing that puzzles me now is i am unable to perform a system recovery from HP update.zip using cwm.
http://h10025.www1.hp.com/ewfrf/wc/...en&cc=us&dlc=en&sw_lang=&product=6608632#N147
So right now i am stuck with 4.2.2 evga ROM all is good and functional.
I have read some post that by updating OTA fix issue in 4.4 but i have no idea on how to get the OTA update.
p/s: This is my first tablet and root attempt...
edit:
i found out that rootjunky has already released the 4.4.2 with 2.3 OTA i will give it a try and feedback later
Click to expand...
Click to collapse
First, nope, you'll still get freezing. I've tried all the ROMs.
Second, If you want to go back to HP's recovery, do the following:
Create a copy of update.zip and navigate to META-INF\com\google\android and open up updater-script
Delete the first three lines.
Transfer your new update.zip to your device and flash. Allow it to re-write the recovery partition.
NOTE THAT YOUR DEVICE WILL NOT ADVANCE PAST THE BOOT ANIMATION. THIS IS NORMAL.
Copy the original update.zip to a SD card and insert it into the device.
Now go to the HP recovery partition that now exists on your device and follow HP's restore instructions.
You're done, the stock 4.2.2 that came with your device is now installed.
Had to figure this out the hard way after I lost my original backup.
To the original poster, you can get it to work, but you need to make modifications to the script's fastboot commands (they will require "fastboot -i 0x03F0" before they will do anything) and you will need to setup your machine for ADB with the Slate 7 Extreme. It won't work out of the box, you can find support for that here: http://h30434.www3.hp.com/t5/Android-Tablets-e-g-HP-Slate-7/ADB-drivers/td-p/2574571

There was an individual who has received the 4.4.2 update from HP on his Slate Extreme over at the HP forums. I believe he stated he received 20 units donated directly from HP and was wondering why only 1 of them received the update. I believe the reason stated is that he most likely received a non-retail unit by accident. Not sure if he ever dumped the ROM or even knows how. I don't know either otherwise I'd try to contact him to get him to do so.

Re-write recovery partition?
Robo_Leader said:
First, nope, you'll still get freezing. I've tried all the ROMs.
Second, If you want to go back to HP's recovery, do the following:
Create a copy of update.zip and navigate to META-INF\com\google\android and open up updater-script
Delete the first three lines.
Transfer your new update.zip to your device and flash. Allow it to re-write the recovery partition.
NOTE THAT YOUR DEVICE WILL NOT ADVANCE PAST THE BOOT ANIMATION. THIS IS NORMAL.
Copy the original update.zip to a SD card and insert it into the device.
Now go to the HP recovery partition that now exists on your device and follow HP's restore instructions.
You're done, the stock 4.2.2 that came with your device is now installed.
Had to figure this out the hard way after I lost my original backup.
To the original poster, you can get it to work, but you need to make modifications to the script's fastboot commands (they will require "fastboot -i 0x03F0" before they will do anything) and you will need to setup your machine for ADB with the Slate 7 Extreme. It won't work out of the box, you can find support for that here: http://h30434.www3.hp.com/t5/Android-Tablets-e-g-HP-Slate-7/ADB-drivers/td-p/2574571
Click to expand...
Click to collapse
I did flash the modified update.zip but CWM doesn't give me the option to re-write the recovery partition. I go straight to "Install from sdcard complete". How is that re-write done?
*Update* All done - Had to select NO to questions on reboot (Replace recovery and root). Thanks so much - back to stock 4.2.2

Belmichel said:
I did flash the modified update.zip but CWM doesn't give me the option to re-write the recovery partition. I go straight to "Install from sdcard complete". How is that re-write done?
*Update* All done - Had to select NO to questions on reboot (Replace recovery and root). Thanks so much - back to stock 4.2.2
Click to expand...
Click to collapse
See my HP Slate 7 Extreme Root post: http://forum.xda-developers.com/showthread.php?t=2850893

What am I supposed to open updater-script with?
---------- Post added at 03:47 AM ---------- Previous post was at 03:31 AM ----------
Robo_Leader said:
First, nope, you'll still get freezing. I've tried all the ROMs.
Second, If you want to go back to HP's recovery, do the following:
Create a copy of update.zip and navigate to META-INF\com\google\android and open up updater-script
Delete the first three lines.
Transfer your new update.zip to your device and flash. Allow it to re-write the recovery partition.
NOTE THAT YOUR DEVICE WILL NOT ADVANCE PAST THE BOOT ANIMATION. THIS IS NORMAL.
Copy the original update.zip to a SD card and insert it into the device.
Now go to the HP recovery partition that now exists on your device and follow HP's restore instructions.
You're done, the stock 4.2.2 that came with your device is now installed.
Had to figure this out the hard way after I lost my original backup.
To the original poster, you can get it to work, but you need to make modifications to the script's fastboot commands (they will require "fastboot -i 0x03F0" before they will do anything) and you will need to setup your machine for ADB with the Slate 7 Extreme. It won't work out of the box, you can find support for that here: http://h30434.www3.hp.com/t5/Android-Tablets-e-g-HP-Slate-7/ADB-drivers/td-p/2574571
Click to expand...
Click to collapse
---------- Post added at 04:25 AM ---------- Previous post was at 03:47 AM ----------
I downloaded a script editor and deleted the first three lines of updater script but it still fails to flash.

Finally success!
Robo_Leader said:
First, nope, you'll still get freezing. I've tried all the ROMs.
Second, If you want to go back to HP's recovery, do the following:
Create a copy of update.zip and navigate to META-INF\com\google\android and open up updater-script
Delete the first three lines.
Transfer your new update.zip to your device and flash. Allow it to re-write the recovery partition.
NOTE THAT YOUR DEVICE WILL NOT ADVANCE PAST THE BOOT ANIMATION. THIS IS NORMAL.
Copy the original update.zip to a SD card and insert it into the device.
Now go to the HP recovery partition that now exists on your device and follow HP's restore instructions.
You're done, the stock 4.2.2 that came with your device is now installed.
Had to figure this out the hard way after I lost my original backup.
To the original poster, you can get it to work, but you need to make modifications to the script's fastboot commands (they will require "fastboot -i 0x03F0" before they will do anything) and you will need to setup your machine for ADB with the Slate 7 Extreme. It won't work out of the box, you can find support for that here: http://h30434.www3.hp.com/t5/Android-Tablets-e-g-HP-Slate-7/ADB-drivers/td-p/2574571
Click to expand...
Click to collapse
I have the 4450 extreme and one the things that was a little different- is that I had put the update zip on the sd card prior and it did the update on its own... WEIRD but acceptable! rooted and on 4.4.2- thanks man!

I didn't have any luck doing it this way. I ended up getting there by a slightly different avenue.
My s7e was totally non functional beyong fastboot and recovery mode being operational. I ended up downloading tegratools 2.2. Using the fastboot included in that I unlocked my boot loader with fastboot by the command
Code:
fastboot -i 0x03F0 oem unlock
(The '-i 0x03F0' is a code relating to the specific model, apparently without this the tablet will ignore your command. Please also remember that the unlock factory resets the tablet.)
It may be overboard again, but I also formatted all the system partitions
Code:
fastboot -i 0x03F0 erase boot
fastboot -i 0x03F0 erase system
fastboot -i 0x03F0 erase userdata
fastboot -i 0x03F0 erase cache
fastboot -i 0x03F0 erase preinstall
fastboot -i 0x03F0 reboot
I uploaded cwm recovery from the above version of tegratools to my s7e as it seems a bit more forgiving with signatures than the stock recovery. I used that to upload a version of update.zip with the "assert" lines removed from META-INF\com\google\android\updater-script. I also self signed the .zip to reduce the likelyhood of my upload being rejected by the tablet, it may not be needed, but I did it anyway.
Code:
adb sideload slate7update-signed.zip
when completing the firmware flash, apparently there is a common problem of the kernel not flashing correctly when recovery takes place and giving an "Error 7", this is the problem I think you solved by re-writing the unmodified firmware (but that didn't work for me)
Anyway I had to fix it by dropping back to fastboot and flashing it to "staging", which puts the kernel in a placeholder until the next boot, at which point the kernel will be written to the correct spot. Because of this writing to the correct partition, you will notice a quick double-boot as the updated kernel is written to the correct point in firmware.
Code:
fastboot -i 0x03F0 flash staging "c:\fastboot-s7e\blob"
I hope this helps.
Oh and to those curious, the beats version appears incompatible with the standard s7e, I tried modifying a rom in the same way as above and it just went to a blank screen. My guess is they've done some form of sanity check in the kernel, given that every "beats" version I've read about in tablets has been a software-only modification. I've not bothered trying to use the beats version rom with the s7e kernel, I'll leave that for someone else to try in greater depth as I'm just happy that I got everything working again.
references:
Fastboot (previously this): This is a copy of the twrp/cwm roms as well as fastboot & adb taken from tegratools 2.2 mentioned above.
SignApk (Previously this): The java files and self signing certificate I used to sign the .zip file. It was actually a bit of a pain to find a working signapk.jar that had the valid certificates included, most were broken in one way or another when trying to sign on ubuntu 12.04.
slate7update-signed.zip (previously this): A signed copy of update.zip with META-INF\com\google\android\updater-script modified to remove the assert validation lines sanity checks, be careful with this, you could nuke your tablet if you use it on an incompatible bit of hardware.
guide.txt (previously this): A full how-to with a number of things I've omitted from this response.
To those wondering, I collated the above procedure from a dozen different links on a good four or five websites, including a number of threads here on XDA. Thank you to anyone out there that contributed to the information I found, you really made my day so much better in being able to recover my tablet.

It Worked! But...
mike-s said:
I didn't have any luck doing it this way. I ended up getting there by a slightly different avenue.
My s7e was totally non functional beyong fastboot and recovery mode being operational. I ended up downloading tegratools 2.2. Using the fastboot included in that I unlocked my boot loader with fastboot by the command
Code:
fastboot -i 0x03F0 oem unlock
(The '-i 0x03F0' is a code relating to the specific model, apparently without this the tablet will ignore your command. Please also remember that the unlock factory resets the tablet.)
It may be overboard again, but I also formatted all the system partitions
Code:
fastboot -i 0x03F0 erase boot
fastboot -i 0x03F0 erase system
fastboot -i 0x03F0 erase userdata
fastboot -i 0x03F0 erase cache
fastboot -i 0x03F0 erase preinstall
fastboot -i 0x03F0 reboot
I uploaded cwm recovery from the above version of tegratools to my s7e as it seems a bit more forgiving with signatures than the stock recovery. I used that to upload a version of update.zip with the "assert" lines removed from META-INF\com\google\android\updater-script. I also self signed the .zip to reduce the likelyhood of my upload being rejected by the tablet, it may not be needed, but I did it anyway.
Code:
adb sideload slate7update-signed.zip
when completing the firmware flash, apparently there is a common problem of the kernel not flashing correctly when recovery takes place and giving an "Error 7", this is the problem I think you solved by re-writing the unmodified firmware (but that didn't work for me)
Anyway I had to fix it by dropping back to fastboot and flashing it to "staging", which puts the kernel in a placeholder until the next boot, at which point the kernel will be written to the correct spot. Because of this writing to the correct partition, you will notice a quick double-boot as the updated kernel is written to the correct point in firmware.
Code:
fastboot -i 0x03F0 flash staging "c:\fastboot-s7e\blob"
I hope this helps.
Oh and to those curious, the beats version appears incompatible with the standard s7e, I tried modifying a rom in the same way as above and it just went to a blank screen. My guess is they've done some form of sanity check in the kernel, given that every "beats" version I've read about in tablets has been a software-only modification. I've not bothered trying to use the beats version rom with the s7e kernel, I'll leave that for someone else to try in greater depth as I'm just happy that I got everything working again.
references:
Fastboot: This is a copy of the twrp/cwm roms as well as fastboot & adb taken from tegratools 2.2 mentioned above.
SignApk: The java files and self signing certificate I used to sign the .zip file. It was actually a bit of a pain to find a working signapk.jar that had the valid certificates included, most were broken in one way or another when trying to sign on ubuntu 12.04.
slate7update-signed.zip: A signed copy of update.zip with META-INF\com\google\android\updater-script modified to remove the assert validation lines sanity checks, be careful with this, you could nuke your tablet if you use it on an incompatible bit of hardware.
guide.txt: A full how-to with a number of things I've omitted from this response.
To those wondering, I collated the above procedure from a dozen different links on a good four or five websites, including a number of threads here on XDA. Thank you to anyone out there that contributed to the information I found, you really made my day so much better in being able to recover my tablet.
Click to expand...
Click to collapse
I was able to unlock my bootloader using the above method and it worked. My s7e rebooted and everything was working normally. I loaded the bootloader again to go in and do a cache wipe and my 3 year old bumped into me as I was holding down the volume+ and power buttons. Now I'm stuck in ADX mode (black screen but recognized by my pc, have tried connecting to charger, volume+ and power, volume - and power, nothing works) . I've read that Advent has released adx files for the Vega Note 7 and you can use Tegra Note 7 Super Tools to restore the Nvidia Note 7. I'm wondering if I can use the update.zip file and the nvflash files from Nvidia to restore my tablet from ADX mode.
Any suggestions?

Mike-S, Thanks for the in depth how-to. I tried to sell my Extreme 4450 and the guy that I sold it to said when he received it was in boot loop. I got it back and it is indeed the one I sent him, however, now I have a bricked tab that doesn't even allow fastboot. I have, like others tried calling HP, tried installing per you instruction and finally considered just throwing away or selling. I almost seems like the recovery was wiped... I can get to uploading from SD and have tried using your info to accomplish with no success. Any suggestions? I hate to smash it or try and sell if I can fix it.
Thank you in advance for anyone's help

som1special2 said:
however, now I have a bricked tab that doesn't even allow fastboot. I have, like others tried calling HP, tried installing per you instruction and finally considered just throwing away or selling.
Click to expand...
Click to collapse
Damn, I'm sorry to say that I'm unsure if i'll be able to help much or at all. All i can suggest is look and see if there is any pre-boot subsystem that connects to your pc via usb, similar to the mediatek "preboot mt65xx" which can sort of provide a last gasp chance of recovery.

help with ROM
Hi there,
Need desperate help. I followed the instructions here but ended up with no OS in the s7e. I kept on trying to install a signed ROM via ADB, it reaches 100% senidng but always failed inside TWRP. Not succesful even with CWM. I even tried installing from SD card but no success. Please help, thank you.

Anyone still around here?
Mike S ... not sure you (or anyone else) is paying any attention to this thread anymore (and the HP Slate 7 Extreme at this point is a fairly old device) ... but I can't get any of these methods to work and my S7E (model 4450) is basically useless right now. When cold (i.e. not booted up in prior 30mins or so), I can boot it normally, but within about 10mins, it will "crash" to the all-white HP splash screen and will never recover. Holding the power button just has it go through initial startup, get to the white HP splash screen, and sit there until the battery runs down. I haven't been able to root it yet, so the bootloader still shows "locked". What's ironic is that this device is really all I need -- I don't play high-end games and mostly just stream shows -- but now it's completely unusable. I'm not sure which is easier ... trying to get this to root or just buying something else?
So far, to root, I've tried towelroot and Cydia Impactor, but both of those returned errors as others have reported. I tried following the steps that Mike S put up here, but without my tablet being rooted, adb and fastboot don't even detect my device from the PC (though the PC detects it because I'm able to see it in Windows Explorer and drag files to the storage) ... so it seems like I can't even get to install CWM or anything further.
Maybe the right thing to do is just to dump the paperweight ... it used to work so well but about 6 months ago this stupid HP white screen crash started happening, and since then it's become a regular thing that only takes about 10 mins (at most) before it craps out. I can get to the bootloader and onboard recovery mode, but that doesn't let me load anything.
Not sure where to go next but any advice would be appreciated!
--AJ

MGrad92 said:
Mike S ... not sure you (or anyone else) is paying any attention to this thread anymore (and the HP Slate 7 Extreme at this point is a fairly old device) ... but I can't get any of these methods to work and my S7E (model 4450) is basically useless right now. When cold (i.e. not booted up in prior 30mins or so), I can boot it normally, but within about 10mins, it will "crash" to the all-white HP splash screen and will never recover. Holding the power button just has it go through initial startup, get to the white HP splash screen, and sit there until the battery runs down. I haven't been able to root it yet, so the bootloader still shows "locked". What's ironic is that this device is really all I need -- I don't play high-end games and mostly just stream shows -- but now it's completely unusable. I'm not sure which is easier ... trying to get this to root or just buying something else?
So far, to root, I've tried towelroot and Cydia Impactor, but both of those returned errors as others have reported. I tried following the steps that Mike S put up here, but without my tablet being rooted, adb and fastboot don't even detect my device from the PC (though the PC detects it because I'm able to see it in Windows Explorer and drag files to the storage) ... so it seems like I can't even get to install CWM or anything further.
Maybe the right thing to do is just to dump the paperweight ... it used to work so well but about 6 months ago this stupid HP white screen crash started happening, and since then it's become a regular thing that only takes about 10 mins (at most) before it craps out. I can get to the bootloader and onboard recovery mode, but that doesn't let me load anything.
Not sure where to go next but any advice would be appreciated!
--AJ
Click to expand...
Click to collapse
Get your device drivers right (try androidsdk if it's still not getting recognised) and fastboot the stock system images (fastboot is not root dependent). By the way why were you trying those weird rooting methods ??? Just flash supersu from cwm/twrp and be done with it.

Thanks ... I'll try androidsdk. I actually am a root n00b and so I was trying to figure out the simplest way to go. I guess I guessed wrong! But of course before I can get that working I need the right drivers ... So I'll try that first. I was thinking the drivers were OK since my PC recognized the S7E when Android loaded (before it crashed to the white screen).

Couldn't get androidsdk to work
Hello again... I never could get androidsdk to work. My computer never recognized the tablet to be able to fastboot. *sigh* As much as I hate to give up, I don't know what else to do.... I might try another PC?

Looking for update.zip for S7E
mike-s said:
I didn't have any luck doing it this way. I ended up getting there by a slightly different avenue.
My s7e was totally non functional beyong fastboot and recovery mode being operational. I ended up downloading tegratools 2.2. Using the fastboot included in that I unlocked my boot loader with fastboot by the command
Code:
fastboot -i 0x03F0 oem unlock
(The '-i 0x03F0' is a code relating to the specific model, apparently without this the tablet will ignore your command. Please also remember that the unlock factory resets the tablet.)
It may be overboard again, but I also formatted all the system partitions
Code:
fastboot -i 0x03F0 erase boot
fastboot -i 0x03F0 erase system
fastboot -i 0x03F0 erase userdata
fastboot -i 0x03F0 erase cache
fastboot -i 0x03F0 erase preinstall
fastboot -i 0x03F0 reboot
I uploaded cwm recovery from the above version of tegratools to my s7e as it seems a bit more forgiving with signatures than the stock recovery. I used that to upload a version of update.zip with the "assert" lines removed from META-INF\com\google\android\updater-script. I also self signed the .zip to reduce the likelyhood of my upload being rejected by the tablet, it may not be needed, but I did it anyway.
Code:
adb sideload slate7update-signed.zip
when completing the firmware flash, apparently there is a common problem of the kernel not flashing correctly when recovery takes place and giving an "Error 7", this is the problem I think you solved by re-writing the unmodified firmware (but that didn't work for me)
Anyway I had to fix it by dropping back to fastboot and flashing it to "staging", which puts the kernel in a placeholder until the next boot, at which point the kernel will be written to the correct spot. Because of this writing to the correct partition, you will notice a quick double-boot as the updated kernel is written to the correct point in firmware.
Code:
fastboot -i 0x03F0 flash staging "c:\fastboot-s7e\blob"
I hope this helps.
Oh and to those curious, the beats version appears incompatible with the standard s7e, I tried modifying a rom in the same way as above and it just went to a blank screen. My guess is they've done some form of sanity check in the kernel, given that every "beats" version I've read about in tablets has been a software-only modification. I've not bothered trying to use the beats version rom with the s7e kernel, I'll leave that for someone else to try in greater depth as I'm just happy that I got everything working again.
references:
Fastboot: This is a copy of the twrp/cwm roms as well as fastboot & adb taken from tegratools 2.2 mentioned above.
SignApk: The java files and self signing certificate I used to sign the .zip file. It was actually a bit of a pain to find a working signapk.jar that had the valid certificates included, most were broken in one way or another when trying to sign on ubuntu 12.04.
slate7update-signed.zip: A signed copy of update.zip with META-INF\com\google\android\updater-script modified to remove the assert validation lines sanity checks, be careful with this, you could nuke your tablet if you use it on an incompatible bit of hardware.
guide.txt: A full how-to with a number of things I've omitted from this response.
To those wondering, I collated the above procedure from a dozen different links on a good four or five websites, including a number of threads here on XDA. Thank you to anyone out there that contributed to the information I found, you really made my day so much better in being able to recover my tablet.
Click to expand...
Click to collapse
Hey Mike, you wouldn't still happen to have that signed update.zip since you've don't have it on Dropbox anymore?

[GUIDE]Nexus 9 back to stock guide - Unbrick - Restore factory firmware

The aim of this thread is to make an easy guide to flashing stock firmware. Owners of previous nexus devices already know all this stuff, this thread is aimed at making the process as simple as possible for new users. This will work regardless of what modifications you've done to your device. Remember to backup all your important data and do this with the knowledge that all flashing activity carries some risk.
Download
Factory image here
(for windows users) Minimal adb & fastboot
(for mac users) adb & fastboot for mac
Follow the instructions to install adb on your computer.
Prepare your tablet
Enable developer options in settings > about tablet and tapping build number 7 times
Open developer options and enable usb debugging. (If you haven't unlocked your bootloader yet, tick enable oem unlock)
Extract images
Place the downloaded factory image inside your adb folder and extract with 7zip.
A new folder will be there called something like volantis-lrx21. Open and extract "image-xxxxx-zip" to your adb folder. We are interested in these files:
bootloader-flounder-xxxxxx.img
boot.img
recovery.img
cache.img
system.img
vendor.img
Place these files directly into your adb folder.
# I recommend renaming the 'bootloader-flounder-xxxxxx.img' to just 'bootloader.img' to make it easier to type.
Now that everythings set up, we can start flashing
Plug in your device. Open the adb folder, hold shift and right click and select open command window here
(if your having driver issues try using Pdanet)
Run these commands one at a time
Code:
adb devices
adb reboot bootloader
if you haven't unlocked the bootloader yet run
Code:
fastboot oem unlock
and follow the instructions using the volume keys to scroll through the menu. This procedure will wipe all data.
Run the following commands one at a time
Code:
fastboot flash bootloader bootloader-flounder-xxxxxxx.img
[B] [I](replace 'bootloader-flounder-xxxxx.img' with full name of bootloader image[/I])[/B]
fastboot reboot-bootloader
fastboot -w
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash cache cache.img
fastboot flash system system.img
fastboot flash vendor vendor.img
(OPTIONAL) At this stage you can relock the bootloader if you want by running the command
Code:
fastboot oem lock
finally reboot the device by running
Code:
fastboot reboot
Thats it. Enjoy your tablet in factory condition

Great. Is it possible to make a batch file to run all the commands at once?

albsat said:
Great. Is it possible to make a batch file to run all the commands at once?
Click to expand...
Click to collapse
There is already a flash all batch script that comes with the firmware files but I've noticed that some people have problems with it so I decided not to include it. It should work fine most of the time.

i am long-time familiar with htc,but new to nexus. i was looking thru a couple downloaded factory image files and having noticed that "rebootRUU" is an oem command,and that "image-xxxxx-zip" contains an android info document,i am curious if anyone has tried flashing image-xxxxx-zip as a zip file,in ruu mode?

Cool, thanks for the information.

Thanks for creating this! Will come in handy. Saving this for later

This has been useful as the update from 5.0.1 to 5.0.2 kept failing on my rooted device. It was successful and educational.

scotty1223 said:
i am long-time familiar with htc,but new to nexus. i was looking thru a couple downloaded factory image files and having noticed that "rebootRUU" is an oem command,and that "image-xxxxx-zip" contains an android info document,i am curious if anyone has tried flashing image-xxxxx-zip as a zip file,in ruu mode?
Click to expand...
Click to collapse
I indeed tried this as a last chance hoping it would bypass bootloader lock protection. It didn't work since I think the factory image is not signed by HTC as RUU are . It also lead to a fastboot crash. Now sending my nexus 9 for RMA
Sent from my HTC One using XDA Free mobile app

remedya said:
This has been useful as the update from 5.0.1 to 5.0.2 kept failing on my rooted device. It was successful and educational.
Click to expand...
Click to collapse
Same here. The manual flash method worked very well. Here's hoping that Google doesn't muck 5.1

cant flash stock rom
I'm trying to downgrade my nexus 9 from DU rom 5.1.1 to stock for everything. I'm running the flash-all.sh on linux while my tablet is in bootloader mode. Tab makes and few checks and reboots automatically in bootloader mode. I reboot tablet and still has the DU rom. Any tips

nyasha1935 said:
I'm trying to downgrade my nexus 9 from DU rom 5.1.1 to stock for everything. I'm running the flash-all.sh on linux while my tablet is in bootloader mode. Tab makes and few checks and reboots automatically in bootloader mode. I reboot tablet and still has the DU rom. Any tips
Click to expand...
Click to collapse
The flash all script doesn't seem to work on linux. You shouldn't have a problem if you write the commands out manually.

nyasha1935 said:
I'm trying to downgrade my nexus 9 from DU rom 5.1.1 to stock for everything. I'm running the flash-all.sh on linux while my tablet is in bootloader mode. Tab makes and few checks and reboots automatically in bootloader mode. I reboot tablet and still has the DU rom. Any tips
Click to expand...
Click to collapse
Art Vanderlay said:
The flash all script doesn't seem to work on linux. You shouldn't have a problem if you write the commands out manually.
Click to expand...
Click to collapse
As indicated, the flash all script doesn't work very well on any system. Flash each .img separately via fastboot.

cam30era said:
As indicated, the flash all script doesn't work very well on any system. Flash each .img separately via fastboot.
Click to expand...
Click to collapse
Problem is that the tgz is too big for the device's buffer, so it craps out before it actually writes the images. Its been this way for a while over several different nexus devices. Kind of like nobody at google ever even bothered to test the process.

doitright said:
Problem is that the tgz is too big for the device's buffer, so it craps out before it actually writes the images. Its been this way for a while over several different nexus devices. Kind of like nobody at google ever even bothered to test the process.
Click to expand...
Click to collapse
I agree.

I also used Linux but I executed the commands individually rather than using the script. It worked.

remedya said:
I also used Linux but I executed the commands individually rather than using the script. It worked.
Click to expand...
Click to collapse
I cant flash system.img I get error
sending 'system' (1108544 KB)...
FAILED (remote: data length is too large)
finished. total time: 0.105s

nyasha1935 said:
I cant flash system.img I get error
sending 'system' (1108544 KB)...
FAILED (remote: data length is too large)
finished. total time: 0.105s
Click to expand...
Click to collapse
Update your Android SDK.

These instructions also worked with 5.1.1

im trying to install back to facctory i erased my system and recovery and data and now when i try to flash bootloader i get error cannot open bootloader someone please im stuck in bootloader mode

maxtcee said:
im trying to install back to facctory i erased my system and recovery and data and now when i try to flash bootloader i get error cannot open bootloader someone please im stuck in bootloader mode
Click to expand...
Click to collapse
Are you writing the full name and file path for the bootloader img?