Database Info

Thinking about unrooting Read this first!!!! ALL MODELS

**********Please Sticky**********
(MOTOROLA HAS RELEASED ALL THE IMAGES FOR ALL COUNTRY VERSIONS OF THE XOOM RECENTLY MAKING THIS A UNIVERSAL TUTORIAL AT THIS POINT)
Listen I notice recently there is a flood of issues with the xoom using different unrooting methods. I personally will say to unroot your device just bring it back to stock images. Its the safest method with the other methods if you do not know what you are doing you will find yourself sending your device to motorola for warranty repairs.
Here is a short and sweet way to unroot your xoom. by doing this you will lose your data and information so start by backing up your stuff to a computer if you have any important things on there.
if starting fastboot is on your xoom screen open up a command prompt:
0. For those who've modified their boot splash graphic with Team Eos' Splash Screen Logo Maker make sure to restore the stock Motorola boot splash FIRST as this process doesn't touch that part of the system. (Posted by Bait-Fish *Thanks for the update*)
1. Goto: http://forum.xda-developers.com/showthread.php?t=1049485 for stock USA 3G and Wifi Images
2. download the files you need
3. extract all the img's into the tools folder
4. with the command prompt open type: cd "replace with tools directory location"
5. disconnect your xoom from your computer and shut off the xoom
6. at the prompt type: fastboot oem unlock
7. it will say waiting for device
8. now plug it into your computer and reboot into fastboot by holding the down volume button and power on
9. follow the on screen instructions and agree to everything
10. your device will reboot you will get the motorola dual core window
11. force restart device by holding volume up and pressing the power button right after the device shuts off hold the down volume button and press power button
12 you should now be in fastboot mode
13. then copy each line one by one into the command window. This will allow you to go back to factory settings like you bought it from the store
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
Note: If no userdata.img file is present in your download, please issue the command:
fastboot erase userdata

Good write up. +1 for sticky if there's not something already.
Sent from my SPH-D700 using XDA Premium App

whats good about this post is that it has been fully tested by me with wifi and 3G versions of the xoom with no problems reported. This method has also fixed some RSD issues. I say some because some people have flashed wrong boot images and ruined fastboot on their xooms from seeing the desktop.

wow you would think with all the issues happening with oneclick root etc you would think this would be a highly read thread. lol.

Nice guide man.

Good to have a thread like this as I was one of those one-click rooters. Unrooted, semi-bricked and learned ADB. If you're going to play with your Xoom, at least have a general idea of ADB.

Please add that this instruction (original post) is only appliable to US Xooms. Not EUs

Thanks!
Thank you so much!
I was also a clueless one-click rooter. I'd tried everything to get rooted again. This was by far the clearest and saved my hanging around waiting for a one-click unroot solution.
Cheers

your welcome enjoy your xoom.

I already upgraded to 3.1, and I unlocked it, but I can't get CWM to work, so I can't root. Can I use this method to go back to the older HC and relock, then go back to 3.1? I bricked mine before, trying to unroot and relock (I know...I know...) I've been adb'ing like crazy trying to get CWM to work, but I feel like giving up and going back to lock, stock, no barrel.

you can if you want it wont hurt the xoom which xoom do you have wifi or 3g?

I have the wifi, running 3.1, build HMJ37

if you go back to 3.0.1 you can root it, install clockwork, then upgrade to 3.1 using clockwork method. its pretty simple. within 25-30 minutes you can be running with clockwork and 3.1 rooted.

I learned my lesson! And the forum saved me.
I did the one-click root back when I got my Xoom a couple months ago, and then when I tried un-rooting and relocking to get the 3.1 update, I bricked it (you're welcome, angel) and sent it back to Motorola. When I got it back, I tried rooting the long way, but couldn't push CWM onto it. I got lots of help and tireless support from a forum member, and finally got it unlocked, rooted, CWM'd with SD support....re-lovin' the Xoom now. And I'm glad the guy that helped me out made me re-check re-download, and redo everything just to make sure we weren't missing any steps.
I love the Xoom NOW, but when I got it back from getting fixed, I was so not happy with it being unrooted! I love to toy with stuff, and this was a real learning experience. Doing all the commands, getting the stock images, re-flashing....it was very rewarding, even though it took so long to figure out how I screwed up. (can you believe it was a usb cable that wasn't working that made it so difficult! Pushed some things, but not others....changed cables, and everything worked fine.)

Nice walk through. I don't think I'll be unrooting anytime soon but its good fyi.
Sent from my Xoom using XDA Premium App

this tutorial should be more helpful now.

dirtymindedx said:
this tutorial should be more helpful now.
Click to expand...
Click to collapse
You could link to my sticky instead of moto if you want. Its the same 20 images but you don't have to login.
Sent from my Xoom

bwcorvus said:
You could link to my sticky instead of moto if you want. Its the same 20 images but you don't have to login.
Sent from my Xoom
Click to expand...
Click to collapse
how do i go about doing that.

dirtymindedx said:
how do i go about doing that.
Click to expand...
Click to collapse
I would just edit line 1 to say you can get from moto at blah blah or download from blah blah so you don't have to log in.
http://forum.xda-developers.com/showthread.php?t=1049485
Sent from my Xoom

nice set of links definitely treasure in my book. Can you post a link on there to this thread since they still haven't stickied this yet?

[GUIDE] How to fix "Failed image LNX 0x0002 / RSD mode 2

I'm sure theres a few of you out there who've bricked their Xoom in the same way I did:
Locking the boot loader after having custom rom and kernal running on it or something similar and come across an error upon boot that says
Failed image LNX 0x0002
RSD mode 2 initiated
or something to that respect
Then tried to do fastboot oem unlock, only to have the Xoom not be recognised.
The solution for me was to make a Motorola Factory cable as per guide here
For some reason, the Xoom would be instantly recognised by my computer and all fastboot commands would work, as well as RSD Lite (Did not do me any good as there is no Xoom Wifi SBF released)
That should fix the booting problem
If it still does not, follow one of the other guides on how to flash using fastboot, another rom now that you have fastboot working again!
Cheers!

mowassasin said:
I'm sure theres a few of you out there who've bricked their Xoom in the same way I did:
Locking the boot loader after having custom rom and kernal running on it or something similar and come across an error upon boot that says
Failed image LNX 0x0002
RSD mode 2 initiated
or something to that respect
Then tried to do fastboot oem unlock, only to have the Xoom not be recognised.
The solution for me was to make a Motorola Factory cable as per guide here
For some reason, the Xoom would be instantly recognised by my computer and all fastboot commands would work, as well as RSD Lite (Did not do me any good as there is no Xoom Wifi SBF released)
That should fix the booting problem
If it still does not, follow one of the other guides on how to flash using fastboot, another rom now that you have fastboot working again!
Cheers!
Click to expand...
Click to collapse
So I went and bought the factory cable from the Black Hat guys, and luckily haven't had the need to use it. Any advice you'd like to give in case I need to at some point?

I guess the only advice I can give is: don't re-lock the boot loader when you have a custom rom loaded

You don't need the cable. I have recovered 4 times myself and walked many others through on irc. We all use the stock cable that came with the device.
Sent from my PG86100 using Tapatalk

bwcorvus said:
You don't need the cable. I have recovered 4 times myself and walked many others through on irc. We all use the stock cable that came with the device.
Sent from my PG86100 using Tapatalk
Click to expand...
Click to collapse
It wouldn't recognise any fastboot commands nor the RSD Lite program for me.
But if it does, then thats good.
Merely a heads up for those who were in the same situation I was

bwcorvus said:
You don't need the cable. I have recovered 4 times myself and walked many others through on irc. We all use the stock cable that came with the device.
Sent from my PG86100 using Tapatalk
Click to expand...
Click to collapse
you won't care to share how you did it? You have no idea how frustrating it is to see someone say they know how to fix something and leave it it at that.

yaturner said:
you won't care to share how you did it? You have no idea how frustrating it is to see someone say they know how to fix something and leave it it at that.
Click to expand...
Click to collapse
Over the course of a few hours I was able to fix this, so I am going to write this little walkthrough for you using a rom from bwcorvus's page (CLICK HERE) and then used the guide from dirtymindedx -(CLICK HERE)
The reason it took me this long (as well as doing other things) was because I used the wrong set up to unroot my tablet. I was using the Unofficial images that are on bwcorvus's link. Because I didn't read thoroughly enough in his breakdown, I made myself look like a fool...
What you want is NOT
UNOFFICIAL STOCK IMAGES
Click to expand...
Click to collapse
because you will not be able to lock the bootloader (IF you want it to be that way, which I did, and so it gave me a 0x000004 Error, and yes i see that you are having a 0x000002 but somewhere i read this could help that.) I just wanted to get rid of Clockwork Recovery Manager cause it was not working on my 3.2 rooted tablet, and thought that because i messed up teh whole image with playing around and upgrading and seeing how i could break the image without overclocking, i thought i should actually try and make it back to stock too. With this... I needed to do these steps...
1. Upgrade the Motorola drivers while the XOOM was plugged in, so then I would be able to use the Fastboot Correctly.
2. Download the correct roms for my tablet, (Wi-Fi is mine, just grab the one that fits your version and just follow along.)
3. Upgrade my ADB from google because for soem odd reason my fastboot did not like the xoom till i did that...
4. Used the STOCK CABLE. I can Confirm that the STOCK CABLE that allows you to recharge the phones, WILL WORK for this...
5. Once the ADB was set up, I restarted it, aka Hit the red X and then loaded it back up and then closed it again, just to make sure the services were updated somewhat...
6. Opened Command prompt and navigated to the folder that help the zipfile for the fastboot flashing guide (aka dirtymindedx's guide at the top), be using CD (Drive Letter):/location/of/the/folder/that/is/unzipped
7. I then checked over the information in the folder by using dir /a and then proceeded to read through the guide
7-1. A note here... I did the fastboot erase userdata instead, because I wanted to see if it would brick it again... (sorry, I was in a fowl mood with the world last night so I was waiting for it to get bricked so i had a reason to use it as an ice scraper on my car... (not like i would really do it... just wanted a reason for justification haha)
8. ???
9. Profit
This is only to get rid of a "already slightly bricked" device... which I had done after relocking the Rom that was not official to Motorola and now, after a few updates, i now have Android 4.0.3 for the Xoom that was OTA'ed, looking to see how easy it will be to root to reload my rpg game saves that i got caught up in (hence my disappearance from the forums haha...) but I hopefully helped you out in a direction to heads towards... and as long as you don't lock the boot-loader (which someone posted about it before i did...) you should be fine with any changes to the rom after the updates... Also, you can skip steps on this too... you can just flash the image and not the recovery menu and so forth, allowing you to keep other settings that are not part associated to the rom image.
Also sorry for the insanity in my words... I have been up for a good 36 hours with a half hour nap somewhere in there...

Need some quick help

So it had been quite some time since I tried messing with my tf300 so....
I was on cm-9, when to update to cm-10.1, tried to update twrp then it wouldn't boot to recovery, tried to flash back to stock JB bootloader using "fastboot flash system.blob" gave me a flash error (invalid size) and for some reason fastboot doesnt recognize my device.
So I have no recovery and no rom.
I tried "fastboot boot boot.blob" from cm-9 and cm-10 and it wont boot. just stuck on "waiting for device"
When I type "fastboot devices" it just starts a new command line, no serial number.
I can include any information needed to help my situation, I just need to be told where to look.
To be honest, I couldn't remember what bootloader I was on. It had been a while. Is there a way to tell?

Can't get the tablet to stay off either while I wait for help. Lol
Sent from my LG-LS970 using xda premium

Any ideas?
Sent from my LG-LS970 using xda premium

Now I think my situation might have gotten worse.
I can't get into fastboot now. It just keeps trying to go into recovery mode but there is no recovery so it just continuously reboots.

No one can help?
Sent from my LG-LS970 using xda premium

Well that sucks...
Sent from my LG-LS970 using xda premium

Depends on what you were trying to do, were you trying to update the recovery first and to what version. I believe cm 9 is based on an older build of bootloader. What exactly did you do. From my knowladge as to reading and seeing so many people just flashing before reading the threads you should first update the bootloader then the recovery depending on what recovery version you were trying to update to. From what it sound like you tried to update the recovery before bootloader just not sure what version of recovery but if wrong one and didnt update bootloader sounds like you maybe un recoverably bricked like what everyone else is doing before reading and as of now. Aslo if you have an nvflash backup there may be a fix i'm just not sure how as i never had it but accorging to some it seems that was the only hope for them to get out. Reaad the threads there maybe help on here some where just so many are flashing and bricking before reading people are getting frustrated because theres no help for it.

I know it doesn't help, but since you wanted to know what happened, I can tell you that much. Since you were on CM9, you had to be on the original ICS bootloader. Stock JB can't be fastboot-flashed over ICS because of changes to the partitioning and other low-level stuff, which is why it wouldn't flash and why it subsequently failed to boot.
I'm also just picking up my TF300 for the first time since August. I just recovered from a soft-brick today (my story, which in hindsight was a complete f-up on my part), which was why I hadn't been using it. I ended up fastboot-flashing the newest ICS firmware (I actually tried it back in August, but fastboot wouldn't work; I didn't do anything differently today, but fastboot had been updated recently and magically worked), then performing the NVFlash backups from the sticky thread (this isn't quite where our paths diverged, but it may have been a good idea to do that before you tried upgrading to JB -- not that it helps now, but for future reference).
Like you, I tried fastboot-flashing the stock JB firmware over the ICS firmware and got the same error you got. So, I tried flashing the ICS firmware again, but got the same Invalid Size error. At this point, my tablet wouldn't boot past the splash screen (not the animation with the spinner; the first one with the NVidea logo in the corner), and fastboot wouldn't flash any firmware.
This next part is the part where our stories more-or-less fork.
Faced with another soft brick just hours after fixing one, I fastboot-flashed TWRP instead (made sure to use an ICS version since the JB firmware didn't flash, and the NVFlash bootloader I had was based on the ICS bootloader), which worked, and I booted into recovery. I used TWRP to flash the ICS firmware (I actually had it on my internal SD card in August, but I could have also pushed it with ADB if I didn't already have it), and I got a functioning tablet again.
Next, to upgrade to Jellybean correctly, I booted into Android and used ADB to push the Jellybean firmware to my tablet. I put it on the root of the internal storage, and the tablet saw it and alerted me to the update. Since TWRP had been replaced by the stock recovery when I flashed the ICS firmware, I just let the tablet do its thing with the update, and I ended up with a perfectly-functioning stock Jellybean ROM. I then performed each subsequent update (I never once skipped any update steps) the same way until I was on the newest 4.1.1 firmware (I'm not updating to 4.2.1 until CM10.1 works with it).
I'm not sure how much research you did before you updated your tablet, but I was trolling the TF300 forums for a good 2 or 3 hours before I even tried upgrading, and I still had trouble (I never saw any posts about people trying to fastboot-flash JB over ICS, so I didn't know it wouldn't work until I tried it at least 3 times). From the limited details you provided, it doesn't sound like you did much searching before you started flashing. In the future, it may be a good idea to research a lot more than you think you have to before flashing things on expensive devices.
Also, in the future, when you're asking for help like this, it's best to go overboard on the details - just like a murder investigation, we want to help you figure out what killed your tablet, but we can't do that if you don't tell us about the strange footprints you saw in your neighbor's lawn the night before. Mention every single icon or word that appears on the tablet, every single button-press you've made, every keystroke you've typed, etc., whether it seems important or not. We can't be there with you, so you have to bring your situation to us.
At this point, the only advice I can give is to let the tablet die, charge it again (so the battery's full but the tablet's powered off), and try again when the battery's full. If you can get ADB to work while the tablet is trying to boot recovery, you may be able to flash a new recovery and then try flashing the ICS firmware (flashing the JB firmware might work, but then you can't use NVFlash). That's about the best you can do if you can't get it into fastboot mode (short of RMAing your tablet). If you can get fastboot to work somehow, then you can easily flash a new recovery and follow the steps I took. But if you do get your tablet booting with the ICS firmware, perform the NVFlash backups ASAP before you update to Jellybean.
I hope you can get your tablet to work. I thought mine was a goner until I got lucky with an updated fastboot. Now, I'm ecstatic that it works, and I'm going to be a lot more careful in the future.

Motorola Xoom MZ640 Dev Edition?

Hello,
I am not new to android I've had two asus transformer pads currently have the one I am using with Tapatalk. My dad's friend had the same tablet I do and his screen stopped working so my dad's friend who's friend works for motorola gave him a motorola xoom to give to his friend with the tablet that wasn't working. Shortly after my bluetooth stopped on mine and he told me the other day that she has another xoom that is looking for a home asked if I'm interested.
So long story short I got a free Motorola Xoom. It's a MZ640. It's a 32 GB wi-fi only model but it's on 3.1 and can't upgrade. I checked online and the model I have should be able to upgrade to jellybean through system update. However the back of it says something like confidential motorola only and not for re-sell. Also the boot animation has a cool android wallpaper with the honeycomb boot. But when I do the Volume Up or Volume Down start up there is no recovery manager to go into it just freezes. So maybe this is a dev version of some kind of special (in a not good way) version and I am stuck unless I root. I took some pictures to try and explain it better. If anyone has seen this model before or not please let me know. If this works out and I can get jellybean on it (PC is dead..need recovery disk so can't use that) I might replace the tf300t with the xoom. The HD Sound dock looks killer. My dad's friend got it.
Also, strangely enough it came with a micro hdmi cable, car charger, and cable. There was no box..would have been interesting to see the box. If anyone needs any other number or info I have it. Just trying to figure out why I can't do jellybean update.
I have considered doing a factory reset but a little nervous if that might mess something up. Any advice is appreciated thanks guys and I hope to enjoy this Xoom.
Sent from my ASUS Transformer Pad TF300T using Tapatalk 2

maxvsmith said:
Hello,
I am not new to android I've had two asus transformer pads currently have the one I am using with Tapatalk. My dad's friend had the same tablet I do and his screen stopped working so my dad's friend who's friend works for motorola gave him a motorola xoom to give to his friend with the tablet that wasn't working. Shortly after my bluetooth stopped on mine and he told me the other day that she has another xoom that is looking for a home asked if I'm interested.
So long story short I got a free Motorola Xoom. It's a MZ640. It's a 32 GB wi-fi only model but it's on 3.1 and can't upgrade. I checked online and the model I have should be able to upgrade to jellybean through system update. However the back of it says something like confidential motorola only and not for re-sell. Also the boot animation has a cool android wallpaper with the honeycomb boot. But when I do the Volume Up or Volume Down start up there is no recovery manager to go into it just freezes. So maybe this is a dev version of some kind of special (in a not good way) version and I am stuck unless I root. I took some pictures to try and explain it better. If anyone has seen this model before or not please let me know. If this works out and I can get jellybean on it (PC is dead..need recovery disk so can't use that) I might replace the tf300t with the xoom. The HD Sound dock looks killer. My dad's friend got it.
Also, strangely enough it came with a micro hdmi cable, car charger, and cable. There was no box..would have been interesting to see the box. If anyone needs any other number or info I have it. Just trying to figure out why I can't do jellybean update.
I have considered doing a factory reset but a little nervous if that might mess something up. Any advice is appreciated thanks guys and I hope to enjoy this Xoom.
Sent from my ASUS Transformer Pad TF300T using Tapatalk 2
Click to expand...
Click to collapse
Dude, I would have responded to this earlier had I seen it. Sorry about that.
First off, that's really cool. What you have is an MZ604 WiFi-only US Xoom that was used inside Motorola for engineering and testing. It's running an engineering build of Honeycomb 3.1, which is why you're not receiving the OTA updates. What we'll have to do is get stock production firmware onto the device. At that stage, you'll get your updates. Here's what you'll want to do:
1. Install fastboot and adb drivers on your PC. You can find instructions for that here: http://androidteen.com/setup-adb-and-fastboot-driver-with-android-sdk/
2. Reboot your Xoom into bootloader mode. To do that, turn your Xoom off. Then, power it back on. Once you see the Motorola logo, count to three at a reasonable speed and press volume down. At the upper left of the screen, you'll see some text. Press volume down until you see "fastboot mode" and press volume up.
3. Connect the Xoom to your PC via USB.
4. At a command prompt, type "fastboot devices". You should see your device listed. If you don't, then the drivers aren't installed correctly.
5. Type "fastboot oem unlock" and follow the on-screen instructions on your Xoom to unlock your bootloader. If the bootloader is already unlocked (since it's an engineering device), you will get a message in your command prompt window telling you as much. Unlocking your bootloader will wipe all data from the tablet so make sure you back up any photos, documents, music, etc. that you want before you do this!!
6. If the bootloader did need to be unlocked, it will reboot after the unlock is done. Once it reboots, perform step 2 again to get the bootloader back into fastboot mode.
7. Go to http://www.randomphantasmagoria.com/firmware/xoom/tervigon and click the link for "images" in the first row of the table (for Android 3.0.1, build HWI69). Download that file, then unzip them somewhere on your PC.
8. Go back to your command prompt and go into whatever directory you unzipped the files into.
9. Type the following commands, in order:
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash userdata userdata.img
fastboot erase cache
10. Optionally, if you want to re-lock the bootloader (unless you're going to run a custom ROM at some point, I recommend this for security purposes), type "fastboot oem lock". Follow the on-screen instructions to re-lock the bootloader. At the end of the lock process, the Xoom will reboot. Let it boot up.
11. If you choose to leave your bootloader unlocked, just type "fastboot reboot" and you'll boot up.
12. The Xoom will now boot into stock Android 3.0.1. At that point, you'll get eight separate over-the-air updates that will eventually get you all the way up to Android 4.1.2/Jelly Bean, build JZO54K.
13. Once you get the Xoom updated all the way to JZO54K, I'd do a factory reset again just to make sure everything is clear and you're starting anew.
At that point, you should be good to go. Let me know if you have any trouble.

oldblue910 said:
Dude, I would have responded to this earlier had I seen it. Sorry about that.
First off, that's really cool. What you have is an MZ604 WiFi-only US Xoom that was used inside Motorola for engineering and testing. It's running an engineering build of Honeycomb 3.1, which is why you're not receiving the OTA updates. What we'll have to do is get stock production firmware onto the device. At that stage, you'll get your updates. Here's what you'll want to do
Click to expand...
Click to collapse
Thank you for replying. Oh so that's why I could never update. It said verizon on it too that must explain the locked bootloader. I just recently learned about how verizon locks their bootloaders. I already did unlock the boot loader and installed recovery and tried a bunch of roms and I'm running CM 10.1 I was nervous of trying it at first but after realizing even if it's an engineering and testing tablet it's still the MZ604 and it should be similar to the others in terms of rooting and unlocking the bootloader. And fortunately I was right.
It actually came with really cool apps that I've never seen before too. I wish I backed those up before I factory reset. I tried factory resetting it initially but I lost a few of the apps and special things and it went to a Honeycomb 3.0 I believe. The one before the SD card support.
But I'm loving this xoom now that it's on CM 10.1 and using Jellybean 4.2. Even though it's tegra 2 and not as fast as my TF300T and other tablets out there the unique design, the placement for the ports and the accessories like the HD Dock make this a very unique tablet. It was never one I intended to buy so it was really cool getting it for free. My friend has one just like mine and he's not into hacking, rooting, and customization so I might be able to get the special apps and stuff that was on it from him. But even though I've never unlocked a boot loader once I figured out how to use command prompt it was really easy to do. Thank god for youtube.

maxvsmith said:
Thank you for replying. Oh so that's why I could never update. It said verizon on it too that must explain the locked bootloader. I just recently learned about how verizon locks their bootloaders.....
Click to expand...
Click to collapse
The Verizon XOOM's (MZ600/MZ602) boot loader was not locked any differently than any other Xoom (example Wifi MZ604). It is/was unlockable out of the box, and Moto had the directions on their web site.
Funny, if it says Verizon on the front, I would not expect it to be a MZ604 model, unless the previous owner flashed the Wifi only Xoom (MZ604) firmware/software onto it. Does that bar code label on its back have a model or MEID on it?

Razr HD - Hard Bricked?

I have a Motorola Droid RAZR HD XT926 (CDMA for Verizon Wireless). I was running root stock ROM on it, and have run into the following problems:
Phone boot is stuck at Motorola logo.
Attempting to go into recovery (ClockworkMod) gives errors that it can't mount any directory (cache, system, etc).
Attempting to RSDLite back to stock fails (on step 1 out of 6 - boot.img - phone returned FAIL).
Attempts to use Droid RAZR HD Toolkit v1.21 and flashing system.img fails (unable to format remote storage).
Anything else worth trying? Or is this hard-bricked, and going on eBay for parts?
Thank you.

How long should it take for RSD to load the 27 files?
I was trying to FXZ back to stock JB but the boot.img file 10MB too about an hour, so I looked at the next file and it was system.... something and it was over 300 MB anyway quick math it would be days to complete so I stopped it and UT oh got the phone back to booting but then it bricked but that's another story.... How long should it take RSD to load the FXZ files?
Thanks,

daredream777 said:
I was trying to FXZ back to stock JB but the boot.img file 10MB too about an hour, so I looked at the next file and it was system.... something and it was over 300 MB anyway quick math it would be days to complete so I stopped it and UT oh got the phone back to booting but then it bricked but that's another story.... How long should it take RSD to load the FXZ files?
Thanks,
Click to expand...
Click to collapse
i dont think i have had it take much more than 5 minutes, defiantly no more than 10, but i have heard reports of as long as 15.

daredream777 said:
I was trying to FXZ back to stock JB but the boot.img file 10MB too about an hour, so I looked at the next file and it was system.... something and it was over 300 MB anyway quick math it would be days to complete so I stopped it and UT oh got the phone back to booting but then it bricked but that's another story.... How long should it take RSD to load the FXZ files?
Thanks,
Click to expand...
Click to collapse
Have you try flashing it through fastboot? something like
Code:
fastboot flash boot boot.img
but probably you will need to use mfastboot due to the img size
Code:
mfastboot flash boot boot.img

pbosio said:
Have you try flashing it through fastboot? something like
Code:
fastboot flash boot boot.img
but probably you will need to use mfastboot due to the img size
Code:
mfastboot flash boot boot.img
Click to expand...
Click to collapse
fastboot will flash it all day long. you generally only need mfastboot for re-writing partitions. but it will flash the img also, as you suggest.

fastboot
bweN diorD said:
fastboot will flash it all day long. you generally only need mfastboot for re-writing partitions. but it will flash the img also, as you suggest.
Click to expand...
Click to collapse
So you are saying fastboot will take a loooong time to load? I need to get back to factory fresh.... What is the best way to do that without taking 3 days?
I have a Razr Maxx HD on JB and have run djbliss recovery but the phone is still rooted afterward. The phone wants to upgrade to KItKat but I have not allowed that since I have heard about some problems for the XT926.... What do you say? If I could just let it upgrade that may be the easiest path but I just want the thing working again.
On those code lines do I just type that in to a command prompt? Somewhat of a noob so can you give me specifics?
Thanks.
ps. Amazingly my phone was bricked. Black, nothing not fastboot no usb port showing up.... I plugged in to wall charger and after about 24 hours I noticed the green light was on ... I pressed the power button, the battery icon showed 3%. A couple minutes later (after I had pressed the power button) it was 12%. Can you explain that? I guess just enough juice trickles in to eventually get a little charge in .... slow enough to maybe make some people go and get a new phone!
---------- Post added at 12:04 PM ---------- Previous post was at 11:39 AM ----------
Ok so I looked at djrbliss batch file and see he is using "fastboot" so yes I have tried that. and it runs through it but the phone is still rooted. Did something go wrong?
Also, VRZ_XT926_9.8.1Q-94-1_CFC.xml appears to be a newer file then he uses but one difference I noticed. "system.img" .... in this file it is "system.img.ext4" Can you explain that?
Thanks.

daredream777 said:
So you are saying fastboot will take a loooong time to load? I need to get back to factory fresh.... What is the best way to do that without taking 3 days?
I have a Razr Maxx HD on JB and have run djbliss recovery but the phone is still rooted afterward. The phone wants to upgrade to KItKat but I have not allowed that since I have heard about some problems for the XT926.... What do you say? If I could just let it upgrade that may be the easiest path but I just want the thing working again.
On those code lines do I just type that in to a command prompt? Somewhat of a noob so can you give me specifics?
Thanks.
ps. Amazingly my phone was bricked. Black, nothing not fastboot no usb port showing up.... I plugged in to wall charger and after about 24 hours I noticed the green light was on ... I pressed the power button, the battery icon showed 3%. A couple minutes later (after I had pressed the power button) it was 12%. Can you explain that? I guess just enough juice trickles in to eventually get a little charge in .... slow enough to maybe make some people go and get a new phone!
---------- Post added at 12:04 PM ---------- Previous post was at 11:39 AM ----------
Ok so I looked at djrbliss batch file and see he is using "fastboot" so yes I have tried that. and it runs through it but the phone is still rooted. Did something go wrong?
Also, VRZ_XT926_9.8.1Q-94-1_CFC.xml appears to be a newer file then he uses but one difference I noticed. "system.img" .... in this file it is "system.img.ext4" Can you explain that?
Thanks.
Click to expand...
Click to collapse
i did not intend to imply the process took a day to flash, "all day long" is merely 'slang' implying it could do it at any time.
the flash could take any where from a few minutes to as long as 15, however 5min or so is most common.
razr utility from the dev forum will restore your phone to factory. make sure you get the correct version, or a newer one is fine too.
not sure what you mean by "have run djbliss recovery", i wasnt aware he made recoveries. can you provide a link so i can see what your talking about.
if you upgrade to the FIRST kk build, you can unlock the bootloader, then if you dont like kk, you can flash back to jb.
yes you can just enter those into a command prompt, but your phone has to be in fastboot, and you have to have adb and fastboot installed on your pc or it wont work.
i can only assume your battery charging issues are a result of running it completely dead. thats not a good idea, and wont always charge back up no matter how long its plugged in. i would consider yourself lucky on that and try not to do it again.
i cant comment on this "Ok so I looked at djrbliss batch file...." until i see what you are talking about.
i dont know the reason for the "ext" extension. either the partition format changed, or some other reason i cant explain.
as long as you flash all the files in any build, there should be no issues.

Back to fresh & JB vs KK
bweN diorD said:
i did not intend to imply the process took a day to flash, "all day long" is merely 'slang' implying it could do it at any time.
the flash could take any where from a few minutes to as long as 15, however 5min or so is most common.
razr utility from the dev forum will restore your phone to factory. make sure you get the correct version, or a newer one is fine too.
not sure what you mean by "have run djbliss recovery", i wasnt aware he made recoveries. can you provide a link so i can see what your talking about.
if you upgrade to the FIRST kk build, you can unlock the bootloader, then if you dont like kk, you can flash back to jb.
yes you can just enter those into a command prompt, but your phone has to be in fastboot, and you have to have adb and fastboot installed on your pc or it wont work.
i can only assume your battery charging issues are a result of running it completely dead. thats not a good idea, and wont always charge back up no matter how long its plugged in. i would consider yourself lucky on that and try not to do it again.
i cant comment on this "Ok so I looked at djrbliss batch file...." until i see what you are talking about.
i dont know the reason for the "ext" extension. either the partition format changed, or some other reason i cant explain.
as long as you flash all the files in any build, there should be no issues.
Click to expand...
Click to collapse
Thanks for your info! I didn't realize the battery was drained! You are right I was very lucky. I ordered a usb programming adapter from Black Hat.
Yes all of those (adb & fastboot) seem to be present from the Droid Razr Utility 1.21. Which is where djrbliss batch file came from (windowsutility.bat) .... Here is the link from where I got it. http://forum.xda-developers.com/showthread.php?t=2307439
Also, here is the link to the (looks like) newer JB XML http://sbf.droid-developers.org/phone.php?device=5 vs the one that was in the Utility 1.21. This has the "system.img.ext4"
Additionally I have a mac but I don't seem to get good results when I try to use the mac.... failure messages. Does that have anything to do with the usb setting in the phone of MTP or Camera? (debugging is on)
All of this is because my phone doesn't receive text messages on pageplus since trying to unflash and upgrading to 4G. Everything else worked fine calls, data and can send text and I just wanted to try and get back to a totally fresh install to see if that made a difference.
Could the long write time in RSD Lite be due to using a virtual Windows 7 on fusion?
So what is your opinion on Kit Kat? Is it worth the upgrade? Is there anything really gained? I am content with JB but if there are some cool user features or something .... my battery lasts 2 days under JB so that really isn't an issue but hey if KK makes it go even longer that would be a +.
Thanks again.

daredream777 said:
Thanks for your info! I didn't realize the battery was drained! You are right I was very lucky. I ordered a usb programming adapter from Black Hat.
Yes all of those (adb & fastboot) seem to be present from the Droid Razr Utility 1.21. Which is where djrbliss batch file came from (windowsutility.bat) .... Here is the link from where I got it. http://forum.xda-developers.com/showthread.php?t=2307439
Also, here is the link to the (looks like) newer JB XML http://sbf.droid-developers.org/phone.php?device=5 vs the one that was in the Utility 1.21. This has the "system.img.ext4"
Additionally I have a mac but I don't seem to get good results when I try to use the mac.... failure messages. Does that have anything to do with the usb setting in the phone of MTP or Camera? (debugging is on)
All of this is because my phone doesn't receive text messages on pageplus since trying to unflash and upgrading to 4G. Everything else worked fine calls, data and can send text and I just wanted to try and get back to a totally fresh install to see if that made a difference.
Could the long write time in RSD Lite be due to using a virtual Windows 7 on fusion?
So what is your opinion on Kit Kat? Is it worth the upgrade? Is there anything really gained? I am content with JB but if there are some cool user features or something .... my battery lasts 2 days under JB so that really isn't an issue but hey if KK makes it go even longer that would be a +.
Thanks again.
Click to expand...
Click to collapse
thats Matt's utility, not Dan's, the same one i maintain here since Matt stopped.
unfortunately, i havent been updating the mac and osx files, so i doubt you can use it directly on a mac. maybe with a virtual setup, but im no expert on that.
if you are happy with your setup, i would just try to re-flash that if need be. mainly the system, if nothing else, then factory reset, or -w command in fastboot.
everyone's option off kk will be different, i dont think its worth leaving something that you like for though.
if you can use a windows machine for 15min or so, you can use this guide to flash kk, root, unlock the bootloader, then flash back to jb if you dont like it. if you update past the first kk to the current one before unlocking, you will not be able to go back to jb, ever. just a fyi.

RSD vs Fastboot
bweN diorD said:
thats Matt's utility, not Dan's, the same one i maintain here since Matt stopped.
unfortunately, i havent been updating the mac and osx files, so i doubt you can use it directly on a mac. maybe with a virtual setup, but im no expert on that.
if you are happy with your setup, i would just try to re-flash that if need be. mainly the system, if nothing else, then factory reset, or -w command in fastboot.
everyone's option off kk will be different, i dont think its worth leaving something that you like for though.
if you can use a windows machine for 15min or so, you can use this guide to flash kk, root, unlock the bootloader, then flash back to jb if you dont like it. if you update past the first kk to the current one before unlocking, you will not be able to go back to jb, ever. just a fyi.
Click to expand...
Click to collapse
Thanks for the info.
So what is the difference between doing a flash with RSD and using the Utility(or fastboot)? Is one more complete? When I used the utility I was still rooted, so in my mind that is not factory fresh and I had killed the sound on boot up and that is still silent.
What does the -w do?
Is RSD flasher just a fancy automated way of doing an RSD flash?
Did you figure out what the ".ext4" was on the end of the system.img.ext4? VRZ_XT926_9.8.1Q-94-1_CFC.xml
I'm starting to get my head around some of this but wow there is a lot to it!
Thanks for your help.

daredream777 said:
Thanks for the info.
So what is the difference between doing a flash with RSD and using the Utility(or fastboot)? Is one more complete? When I used the utility I was still rooted, so in my mind that is not factory fresh and I had killed the sound on boot up and that is still silent.
What does the -w do?
Is RSD flasher just a fancy automated way of doing an RSD flash?
Did you figure out what the ".ext4" was on the end of the system.img.ext4? VRZ_XT926_9.8.1Q-94-1_CFC.xml
I'm starting to get my head around some of this but wow there is a lot to it!
Thanks for your help.
Click to expand...
Click to collapse
fastboot can do a bit more than rsd and you can flash one file or many rather easily.
most of the utilites only contain key files needed to upgrade or re-flash, regardless if they were changed. i only made 2 builds with a complete flash, v-1.4 and v-1.41.
about root, im pretty sure i have never had that happen, and i have flashed quite a bit. maybe i just never noticed. i believe the system would need to be formatted to completely clean it, but i dont know if its done by default or not. did the system flash properly in the utility? all pass no fail?
if you used the wrong version, some things would fail if your bootloader is locked.
-w is basically a factory reset.
i didnt look into the ext extension.

Utility run failure
bweN diorD said:
fastboot can do a bit more than rsd and you can flash one file or many rather easily.
most of the utilites only contain key files needed to upgrade or re-flash, regardless if they were changed. i only made 2 builds with a complete flash, v-1.4 and v-1.41.
about root, im pretty sure i have never had that happen, and i have flashed quite a bit. maybe i just never noticed. i believe the system would need to be formatted to completely clean it, but i dont know if its done by default or not. did the system flash properly in the utility? all pass no fail?
if you used the wrong version, some things would fail if your bootloader is locked.
-w is basically a factory reset.
i didnt look into the ext extension.
Click to expand...
Click to collapse
Just reran the utility and it did not run clean
Here is the results of the utility run
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I inserted the image but it is not showing up. Basically it said it:
load_file: could not allocate 870148648 bytes
error: cannot load 'system.img'
sending 'boot' (10240 KB) ....
OKAY [ 0.781s]
writing 'boot' ...
Preflash validation failed
FAILED (remote failure)
everything after this point ran fine.
Another note this article http://www.andromods.com/tips-trick...-unroot-unbrick-droid-razr-maxx-hd-xt926.html says to remove the 'getvar' from the xml file and it will be factory fresh. What does that do? Any opinion?
Thanks.
ps running RSD and it appears to hang at system .... has run for 20 minutes so far. This is where I pulled the plug when 'boot' took an hour on my virtual windows 7. This time boot took less than a second on a real windows 7 machine. I just saw it flash up and it was done.

daredream777 said:
Just reran the utility and it did not run clean
Here is the results of the utility run
I inserted the image but it is not showing up. Basically it said it:
load_file: could not allocate 870148648 bytes
error: cannot load 'system.img'
sending 'boot' (10240 KB) ....
OKAY [ 0.781s]
writing 'boot' ...
Preflash validation failed
FAILED (remote failure)
everything after this point ran fine.
Another note this article http://www.andromods.com/tips-trick...-unroot-unbrick-droid-razr-maxx-hd-xt926.html says to remove the 'getvar' from the xml file and it will be factory fresh. What does that do? Any opinion?
Thanks.
ps running RSD and it appears to hang at system .... has run for 20 minutes so far. This is where I pulled the plug when 'boot' took an hour on my virtual windows 7. This time boot took less than a second on a real windows 7 machine. I just saw it flash up and it was done.
Click to expand...
Click to collapse
its acting like you are using too old version of the script or something else unexpected is happening. not everything is failing, thats good. usually means its fixable.
if you are trying to flash jb, use this. it should either fix the problem, or the output failures will let me know what to try next.
if you were trying to flash kk then use this.
dont try the kk version if you havent tried to flash kk yet! it should work, i just dont want to further complicate this if it doesnt.
the getvar line is removed from the utilities and you should edit it out of the xml file if flashing with rsd.
the problem with rsd right now is it cant re-partition the phone unless you are upgrading. im trying to re-partition it for you as is, which mfastboot can do. mfastboot is what the utilities above use, and the partition files, which are not included in the general versions of the script.
post your results and well go from there.

SOLVED! I ran House of Moto utils
bweN diorD said:
its acting like you are using too old version of the script or something else unexpected is happening. not everything is failing, thats good. usually means its fixable.
if you are trying to flash jb, use this. it should either fix the problem, or the output failures will let me know what to try next.
if you were trying to flash kk then use this.
dont try the kk version if you havent tried to flash kk yet! it should work, i just dont want to further complicate this if it doesnt.
the getvar line is removed from the utilities and you should edit it out of the xml file if flashing with rsd.
the problem with rsd right now is it cant re-partition the phone unless you are upgrading. im trying to re-partition it for you as is, which mfastboot can do. mfastboot is what the utilities above use, and the partition files, which are not included in the general versions of the script.
post your results and well go from there.
Click to expand...
Click to collapse
Got it! Finally! Ran House of Moto script gen on it and it loaded back to factory fresh without a hitch. Thanks. So much info out there it takes a while to find the right path.