Related
##PLEASE NOTE##
These files are from Motorola's Development site and I take no liability with anything that happens with your device if something goes wrong.
DO NOT ATTEMPT TO FLASH THIS FILE ON ANYTHING BUT THE VERIZON WIRELESS MOTOROLA XOOM Z600 (3G MODEL) OR YOU WILL HAVE A SHINEY PAPER WEIGHT!!!!
Click to expand...
Click to collapse
You're going to need to have the Android SDK installed. You can download it here:
ANDROID SDK - DOWNLOAD
XOOM Firmware Downloads:
[3G|MZ600-HRI66]
[4G|MZ602-HLK75D]
Unzip the files in MZ600_HRI66.zip and move or copy them to the /platform-tools folder in your SDK folder.
Connect your Xoom to your computer. Type:
Code:
adb reboot bootloader
Wait for it to reboot into the bootloader.
Type the following commands, waiting for each to finish before continuing:
Code:
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash userdata userdata.img
fastboot erase cache
You've now successfully flashed your Xoom back to stock. Now it's time to relock the device. Type
Code:
fastboot oem lock
wait for the menu
then press the volume-down button.
Then press the volume up button.
It'll take a minute or so, then reboot. You're now completely back to stock and ready for the update.
So if you are on Three . One you can use this to revert back to out of the box freshness?
Brenardo said:
So if you are on Three . One you can use this to revert back to out of the box freshness?
Click to expand...
Click to collapse
Yes. That is correct. This will return your XOOM to 100% stock.
word!
I have already been thru the LNX 0x0004 debacle and it was absolutely no fun whatsoever.
well I got a stuck at moto logo for 10 minutes
I am going to try to fastboot oem unlock, reflash images again and fastboot lock to see if I get out of moto logo
second install fix it
jlouang said:
second install fix it
Click to expand...
Click to collapse
So that means that you got it working, correct?
>.>
So the HRI66 is the latest version on the Motorola site? I really need to get a grasp of their version numbers.
EDIT:
Never mind looks like HRI66 is the latest version Thanks anyway.
i was thinking that with the change to the bootloader in the 3.1 update we couldn't use previous versions img's. But I am glad we can return to stock and get this 4G update!
I'm following all those steps directly. Once I type in adb reboot bootloader, it says starting Fastboot protocol support. Once I try to type any other command it says not recognized in adb. Any ideas?
Dead link...
dchurch85 said:
I'm following all those steps directly. Once I type in adb reboot bootloader, it says starting Fastboot protocol support. Once I try to type any other command it says not recognized in adb. Any ideas?
Click to expand...
Click to collapse
Did you extract all of the files in the ZIP into the 'tools' folder? The same one that adb is in.
Could someone help me,
After the rebooting device I got this massage :
Failed to boot LNX 0x0004
Starting RSD mode 2
Then stuck on Motorola logo. I can't enter the recovery mode.
What should I do ?
My Xoom is H.6.1-38-9 International version
CakraMas said:
Could someone help me,
After the rebooting device I got this massage :
Failed to boot LNX 0x0004
Starting RSD mode 2
Then stuck on Motorola logo. I can't enter the recovery mode.
What should I do ?
My Xoom is H.6.1-38-9 International version
Click to expand...
Click to collapse
This is what I was afraid of..... try searching the error you are getting. Not many options on how to fix.
i am curious about the LNX 0x0004 error. I know it comes from trying to relock with non-factory img's but what exactly does that mean? I am curious what actually causes the device to soft brick.
Finally I made it, .
I can enter to bootloader by fastboot method, flash the stock image, then relock my device.
Kinda having the same issue as dchurch... "adb reboot bootloader" reboots Xoom to the "M" logo with "Starting Fastboot protocol support," but I can't continue with nay further commands. My computer no longer recognizes the presence of my Xoom and my Xoom doesn't progress past this screen. I can boot it normally with no problem. I've extracted all of the necessary files into my platform tools folder with adb.. any input?
gatorhater73 said:
Kinda having the same issue as dchurch... "adb reboot bootloader" reboots Xoom to the "M" logo with "Starting Fastboot protocol support," but I can't continue with nay further commands. My computer no longer recognizes the presence of my Xoom and my Xoom doesn't progress past this screen. I can boot it normally with no problem. I've extracted all of the necessary files into my platform tools folder with adb.. any input?
Click to expand...
Click to collapse
You can try manually going into fastboot as well... there are two ways to do this:
No matter what, power off the Xoom. Then, 1) Power on the Xoom and as soon as you see it turn on (within a second or two of the power on), press the Volume Down button, which kicks it into Fastboot. 2) If you miss the 1st couple of seconds and press Volume Down after 3-5 seconds, it will say "Android Recovery." You can then press Volume Down until you get to Fastboot, then press Volume Up.
My guess is that you have a different issue, something to do with your Fastboot image. Not sure if booting the Xoom into the OS and connecting with USB Debugging on will work or not to flash the files, perhaps maybe just the boot.img?
I also believe that when the Xoom says "Starting Fastboot protocol support", it is in fastboot mode and you can send the fastboot commands to the Xoom. If your PC does not show the Xoom as a device in your PC's Device manager, then you will probably need to load new/correct drivers onto your PC.
Did you make sure that adb recognized your device? Adb devices in the camaned prompt
Sent from my Xoom using Tapatalk
I have a pretty big problem and need some guided help. My stock samsung usb charger sometimes charges the phone and sometimes does not. Tried multiple different chords and got the same results, sometimes works sometimes does not. So now I am assuming this is an internal hardware problem soo I decided I should flash stock images, unroot and relock the bootloader and here comes the worst problem.... My device is NOT recognized when I connect it to my PC... therefor I can't access adb connection to flash stock images so I can return it to VZW....
Not sure what to do next.. any suggestions would be great...
It sounds like you just don't have the drivers installed. Just install the Samsung drivers here.
mwalt2 said:
It sounds like you just don't have the drivers installed. Just install the Samsung drivers here.
Click to expand...
Click to collapse
I tried that. uninstalled the old ones (that worked for 3 months) reinstalled them again and still no luck..
Do you have any other Android processes running on your cpu? Droid Explorer or alike? Droid Ex **** blocks adb; I had a frustrating few minutes once when adb wouldn't connect to my device until I realized DE was running in the background.
Long shot, but just a thought.
This is actually a common hardware error. See http://code.google.com/p/android/is...ary Stars&groupby=&sort=&id=23789#makechanges and http://forum.xda-developers.com/showthread.php?t=1427539
Basicly you need to buy a new USB charging board.
chuckdz3 said:
and here comes the worst problem.... My device is NOT recognized when I connect it to my PC... therefor I can't access adb connection to flash
Click to expand...
Click to collapse
You mean fastboot
Melhouse said:
This is actually a common hardware error. See http://code.google.com/p/android/is...ary Stars&groupby=&sort=&id=23789#makechanges and http://forum.xda-developers.com/showthread.php?t=1427539
Basicly you need to buy a new USB charging board.
Click to expand...
Click to collapse
Yeah I believe that is what I am going to do, I just have to find the sch-i515 CDMA version because I am finding a lot of GSM versions out there right now.
bk201doesntexist said:
You mean fastboot
Click to expand...
Click to collapse
Sure. My adb command prompt does not recognize my device therefor I cannot execute any commands ei fastboot.
chuckdz3 said:
Sure. My adb command prompt does not recognize my device therefor I cannot execute any commands ei fastboot.
Click to expand...
Click to collapse
fastboot doesnt have anything to do with adb; boot your device into bootloader
'fastboot devices'
do you see your device?
bk201doesntexist said:
fastboot doesnt have anything to do with adb; boot your device into bootloader
'fastboot devices'
do you see your device?
Click to expand...
Click to collapse
I am in the bootloader and don't see 'fastboot devices' or do I see my device. I see the product name, variant, bootloader version, baseband version, etc. Would that be considered 'my device' being recognized and I could actually flash the stock images?
chuckdz3 said:
I am in the bootloader and don't see 'fastboot devices' or do I see my device. I see the product name, variant, bootloader version, baseband version, etc. Would that be considered 'my device' being recognized and I could actually flash the stock images?
Click to expand...
Click to collapse
fastboot is like adb. You need to run it from a command line. You should have had to use it when you installed a custom recovery ('fastboot flash recovery customrecovery.img') or unlocked your phone (ie 'fastboot oem unlock'). fastboot is part of the android sdk (think it's in tools folder, but I moved mine so am not sure).
mwalt2 said:
fastboot is like adb. You need to run it from a command line. You should have had to use it when you installed a custom recovery ('fastboot flash recovery customrecovery.img') or unlocked your phone (ie 'fastboot oem unlock'). fastboot is part of the android sdk (think it's in tools folder, but I moved mine so am not sure).
Click to expand...
Click to collapse
That's what my understanding of what it was too. I'm in the bootloader running a command prompt through windows and for the first time I think it recognized my devices. I ran 'fastboot devices' and a bunch of numbers on one line came up followed by fastboot. So I think my device is recognized and I can flash stock images?
chuckdz3 said:
That's what my understanding of what it was too. I'm in the bootloader running a command prompt through windows and for the first time I think it recognized my devices. I ran 'fastboot devices' and a bunch of numbers on one line came up followed by fastboot. So I think my device is recognized and I can flash stock images?
Click to expand...
Click to collapse
yes, you can download the images for your device from google and flash them to your phone using fastboot if you want. I'm pretty sure that would put you back at stock with an unlocked bootloader.
@op, next time read how to flash/get back to stock before flashing anything. there must be like a dozen of topics in xda about this ****.
bk201doesntexist said:
@op, next time read how to flash/get back to stock before flashing anything. there must be like a dozen of topics in xda about this ****.
Click to expand...
Click to collapse
I know how to. It was just your demeanor and wording/phrasing that had me confused.
I have the same problem, fastboot was working this morning, now after flashing Revolution HD, typing "fastboot devices" in CMD doesnt return anything anything, neither does adb push command which replies failed to copy .... As if the phone doesnt exist or its not attached. Does the phone need to be in clockwork mod? or just boot the phone normally?
Edit: This should do the trick, open CMD in Windows, navigate to your c:\android where you have fastboot and adb stored and type:
:cd %:h
adb kill-server
adb reboot bootloader
brooklynite said:
I have the same problem, fastboot was working this morning, now after flashing Revolution HD, typing "fastboot devices" in CMD doesnt return anything anything, neither does adb push command which replies failed to copy .... As if the phone doesnt exist or its not attached. Does the phone need to be in clockwork mod? or just boot the phone normally?
Edit: This should do the trick, open CMD in Windows, navigate to your c:\android where you have fastboot and adb stored and type:
:cd %:h
adb kill-server
adb reboot bootloader
Click to expand...
Click to collapse
*facepalm*
Make sure USB debugging is turned on.
Sent from my Galaxy Nexus
mentose457 said:
Make sure USB debugging is turned on.
Sent from my Galaxy Nexus
Click to expand...
Click to collapse
*facepalm*
Melhouse said:
*facepalm*
Click to expand...
Click to collapse
Did I say something stupid?
mentose457 said:
Did I say something stupid?
Click to expand...
Click to collapse
debugging has nothing to do with it.
Windows XP absolutely HATES the samsung galaxy nexus.
The don't play along and it's almost impossible to get the drivers (especially MTP) installed correct.
Fortunately I have a W7 BEAST rig at home.. But the work XP pc can't handle the Nexus
I'd like to make a batch file to execute a series of commands like below.
adb reboot bootloader
fastboot flash boot boot.img
fastboot erase cache
I flash a lot so I wanted to make things easier, could anyone help me out please?
I once knew a thing or two, something about echo and such, but that was a long time ago.
Thanks!
D3VICE said:
I'd like to make a batch file to execute a series of commands like below.
adb reboot bootloader
fastboot flash boot boot.img
fastboot erase cache
I flash a lot so I wanted to make things easier, could anyone help me out please?
I once knew a thing or two, something about echo and such, but that was a long time ago.
Thanks!
Click to expand...
Click to collapse
START fastboot flash boot boot.img etc...
save it as .bat in your fastboot folder
should work
since there is no wait-for-device on fastboot, you'd probably have to do something like this...
Code:
adb reboot bootloader
sleep 15
fastboot flash boot boot.img
fastboot erase cache
Otherwise the adb command would return the moment the command is sent to the phone and it'd try and execute the fastboot flash command before the phone is actually in fastboot.
Squirrels said:
since there is no wait-for-device on fastboot, you'd probably have to do something like this...
Code:
adb reboot bootloader
sleep 15
fastboot flash boot boot.img
fastboot erase cache
Otherwise the adb command would return the moment the command is sent to the phone and it'd try and execute the fastboot flash command before the phone is actually in fastboot.
Click to expand...
Click to collapse
Makes sense, thanks I will try, hope it works.
Thanks to both of you !
I would use a pause command in the batch script on Windows so that the user can make sure that the phone is actually in fastboot USB mode prior to running fastboot. Sleep is not provided in the default command set on Windows so won't work.
Having said that ignore the above para if your script is running on an Unix environment.
Code:
adb reboot bootloader
timeout /t 10
fastboot flash boot boot.img
fastboot erase cache
try this one, timeout is built in since windows 7 i think
hmm my Windows 7 had sleep, must have been installed by a third-party app then if it is not included by default. Noted.
Squirrels said:
hmm my Windows 7 had sleep, must have been installed by a third-party app then if it is not included by default. Noted.
Click to expand...
Click to collapse
The windows resource kit must have been installed on your PC? Anyway, it can be downloaded from here.
Any idea how to do something like this?
After running the batch it shows a message saying something like.
Please plug in your phone and enable USB-mode and press any button when finished
Click to expand...
Click to collapse
After plugging in the phone you press the button and it executes the bootloader command, then it says.
Please press any button to flash boot.img
Click to expand...
Click to collapse
You press a button, it finishes flashing and then gives a message saying.
Please press any button to erase the cache
Click to expand...
Click to collapse
After pressing a button it erases the caches and displays something like
''Flashing successful, please reboot into recovery to flash your ROM.''
Click to expand...
Click to collapse
I remember needing echo commands for this to work, but all of my attempts have failed .
Hello,
Still working on my kids KF2. I got root, yeah! However at some point it updated to 10.3. Can someone point me in the right direction for getting its bootloader downgraded from a Windows 7 x64 platform? I can use a RHEL box at work if I really need to, but rather not.
so I get CM on this thing
thanks!
http://forum.xda-developers.com/showthread.php?t=2100963
soupmagnet said:
http://forum.xda-developers.com/showthread.php?t=2100963
Click to expand...
Click to collapse
Does that mean I need a fastboot cable? I can make one no problem... but better if I don't have to
I ran: fastboot -i 0x1949 flash bootloader otter2-u-boot-prod-10.2.4.bin, device off, it said waiting for device, but then it just boot up to the lock screen.
Sorry im a little confused on this one.
Code:
adb shell su -c "reboot bootloader"
soupmagnet said:
Code:
adb shell su -c "reboot bootloader"
Click to expand...
Click to collapse
Thanks for the info.. but im gonna be a noob here...
What do I do with that? run it from command prompt? with the device booted, not booted? before the fastboot -i 0x1949 flash bootloader ?
s10010001 said:
Thanks for the info.. but im gonna be a noob here...
What do I do with that? run it from command prompt? with the device booted, not booted? before the fastboot -i 0x1949 flash bootloader ?
Click to expand...
Click to collapse
That is a command to be run from the command lint to put your device in fastboot mode without a factory cable. Once your device is in fastboot, then you can continue with the fastboot commands. If you are in fastboot and you still get "<waiting for device>", you need to make sure your drivers are configured properly.
soupmagnet said:
That is a command to be run from the command lint to put your device in fastboot mode without a factory cable. Once your device is in fastboot, then you can continue with the fastboot commands. If you are in fastboot and you still get "<waiting for device>", you need to make sure your drivers are configured properly.
Click to expand...
Click to collapse
Thanks a ton! Ill give it a try tonight when I get home.
In theroy:
Fastboot with that command
Install downgraded bootloader
install TWRP
Install rom
enjoy...
s10010001 said:
Thanks a ton! Ill give it a try tonight when I get home.
In theroy:
Fastboot with that command
Install downgraded bootloader
install TWRP
Install rom
enjoy...
Click to expand...
Click to collapse
Close
Make backups
Fastboot with that command
Install downgraded bootloader
Install 2nd bootloader
Install TWRP & kernel(boot.img)
Factory Reset in TWRP
Install rom
enjoy..
Enjoyment is relative, of course
Well bummer. I got into fast boot. I think I got a backup. But on a reboot, it just looks the Orange Kindle Fire logo...
Now I really need a fast boot cable hua? Assuming a fastboot cable will let me fast boot. Once there again what can I do?
s10010001 said:
Well bummer. I got into fast boot. I think I got a backup. But on a reboot, it just looks the Orange Kindle Fire logo...
Now I really need a fast boot cable hua? Assuming a fastboot cable will let me fast boot. Once there again what can I do?
Click to expand...
Click to collapse
Hold the power button to turn your device off, enter the following command and boot it up again...
Code:
fastboot -i 0x1949 getvar product
...dose your device boot into fastboot? If so, start over and try again. If not, you'll need a factory cable.
soupmagnet said:
Hold the power button to turn your device off, enter the following command and boot it up again...
Code:
fastboot -i 0x1949 getvar product
...dose your device boot into fastboot? If so, start over and try again. If not, you'll need a factory cable.
Click to expand...
Click to collapse
it was worth a shot, but no Ill be needing that cable
When I make one, will it just boot into fastboot upon boot if the cable is in? Just pins 1 and 4 right?
s10010001 said:
it was worth a shot, but no Ill be needing that cable
When I make one, will it just boot into fastboot upon boot if the cable is in? Just pins 1 and 4 right?
Click to expand...
Click to collapse
If your device is completely off, and you plug a working factory cable in, it will boot into fastboot.
Info on pin layout
You need a 5-pin usb cable BTW.
Cool, thanks for all the help.
One more question. Do you have one of the guides you specially recommend once I do get the cable made?
s10010001 said:
Cool, thanks for all the help.
One more question. Do you have one of the guides you specially recommend once I do get the cable made?
Click to expand...
Click to collapse
Were you able to successfully backup your boot, recovery, and system partitions before everything went wrong?
No I was looking at it, I think it errored out.
I can just fastboot with cable and start over with hash's guide?
s10010001 said:
No I was looking at it, I think it errored out.
I can just fastboot with cable and start over with hash's guide?
Click to expand...
Click to collapse
Possibly, but depending on where things went wrong, you may have to restore first. Do you know what the error was?
Something like this max-download-size: 486,539,264
s10010001 said:
Something like this max-download-size: 486,539,264
Click to expand...
Click to collapse
You are supposed to save your partition images with the 'dd' command using the shell:
Hashcode said:
STEP 1. Backup your stock partitions to your own HD for later if you need disaster recovery:
Code:
adb shell su -c "dd if=/dev/block/platform/omap/omap_hsmmc.1/by-name/boot of=/sdcard/stock-boot.img"
adb shell su -c "dd if=/dev/block/platform/omap/omap_hsmmc.1/by-name/recovery of=/sdcard/stock-recovery.img"
adb shell su -c "dd if=/dev/block/platform/omap/omap_hsmmc.1/by-name/system of=/sdcard/stock-system.img" # This will take a few minutes
adb pull /sdcard/stock-boot.img
adb pull /sdcard/stock-recovery.img
adb pull /sdcard/stock-system.img # This will take a few minutes
Take those files and put them somewhere safe.
Click to expand...
Click to collapse
You won't see a "max-download-size" message unless you are using fastboot to flash those images.
ohh ok.. so I dont have a backup
But the fastboot cable is working! Im in fastboot
keeps telling me no device found
do I want the "Android ADB Interface" or "Andriod Composite ADB Interface"?
Also once booted in to fastboot with the cable, do I just leave the cable or put the stock cable back in? Shouldnt matter... but just want to make sure.
Hy
I had an unlocked bootloader phone. Yesterday I flashed the new Android 6, Europe version from the Huawei blog forum, no beta, on my Huawei GX8. I used the method, dload on SD card, Phone off an the press Volume down+volume up+Power button.The flashing was normaly.
Now the phone starts normaly but I can´t start fastboot. When the phone is off and i press Vol down + Power the phone start the android system and the Huawei logo is coming not the fastboot Modus. I can see my phone and the order under Windows but i can not control my phone with the fastboot command. (example: fastboot device. the answere ist searching devices, but it comes no resolution) I loaded the last version of Fastboot, but the problem is the same.
Please can you help me. What can i do? Many thanks for your help!
Should be connect the charger cable to the phone.
charger or computer
excuse me for bad english
No i use a data cable, debugging is on. I can copy data from my phone to PC or from PC to phone, but fastboot does not found my device.
bertl237 said:
No i use a data cable, debugging is on. I can copy data from my phone to PC or from PC to phone, but fastboot does not found my device.
Click to expand...
Click to collapse
And when you use adb to reboot to bootloader, what happen? Do you have "Minimal adb and fastboot tool" installed?
krispin said:
And when you use adb to reboot to bootloader, what happen? Do you have "Minimal adb and fastboot tool" installed?
Click to expand...
Click to collapse
Sorry for my question, what´s the differents about adb and fastboot tool? I have install the last version of minimal adb and the fastboot tool, also the Windows driver for the phone. Debugging is on. I try to connect my phone about the fastboot terminal. When i try to set the phone into the bootloader mod with the fastboot terminal and the equivalent command, fastboot say´s "searching phone". My phone does not react.
bertl237 said:
Sorry for my question, what´s the differents about adb and fastboot tool? I have install the last version of minimal adb and the fastboot tool, also the Windows driver for the phone. Debugging is on. I try to connect my phone about the fastboot terminal. When i try to set the phone into the bootloader mod with the fastboot terminal and the equivalent command, fastboot say´s "searching phone". My phone does not react.
Click to expand...
Click to collapse
So, you connect your phone, open minimal adb and fastboot too, run "adb devices", you see device id? If yes, run "adb reboot bootloader" . Phone shoult reboot to fastboot mode. Then run "fastboot devices" to see if it is connected properely.
i did it, like you described, but i see not my device id. Only the note "seach device"
Is it possible that TWRP is defect on my device? Is TWRP necessary for fastboot or only for root?
bertl237 said:
i did it, like you described, but i see not my device id. Only the note "seach device"
Is it possible that TWRP is defect on my device? Is TWRP necessary for fastboot or only for root?
Click to expand...
Click to collapse
No, you should be able to use adb and fastboot with stock recovery.
After first adb command you shoult approve authorization on your phone.
Here is screenshot from minimal adb...
Phone must be in MTP mode.
And here is phone in fastboot
Many thanks for your help, now I m in my bootloader.
2 problems i had.
1. My daemon was not started correctly, i have not seen my device.
2. I used the wrong command. I started with fastboot, not with the command adb device. I tap „fastboot reboot-bootloader“,but the correct command is “adb reboot-bootlader“
Now i have seen my phone is unlocked, i hope i can root my android 6.
bertl237 said:
Many thanks for your help, now I m in my bootloader.
2 problems i had.
1. My daemon was not started correctly, i have not seen my device.
2. I used the wrong command. I started with fastboot, not with the command adb device. I tap „fastboot reboot-bootloader“,but the correct command is “adb reboot-bootlader“
Now i have seen my phone is unlocked, i hope i can root my android 6.
Click to expand...
Click to collapse
Just reboot to fastboot and flash surdu-petru version of TWRP recovery 3.0.2 with command "fastboot flash recovery xxxxx.img". And than reboot to recovery and flash supersu zip.