Hi. I was on #xoom at freenode earlier and I got some help, but unfortunately no solution. (thank you Kas, EbonyGhost, Pyrator and the others)
I flashed the recovery here:
http://forum.xda-developers.com/showthread.php?t=1074979
I flashed... THE ZIP!!
The flash went well, then the device rebooted and showed "Starting RSD mode 3"
I have only 2 screens:
- with VolUp + power = dual core techno + "Starting RSD mode 3"
- with VolUp + power then immediately VolDown = only the dual core tech logo, no text
Either way: no adb, no fastboot. Tried other usb slots. Tried reinstalling moto drivers.
The xoom never gets recognised by windows. I don't have the dongdong sound when I plug it, in either mode.
I already tried this:
http://forum.xda-developers.com/showthread.php?t=973355
but I get < waiting for device > because it's not recognised by windows...
Any other idea?
Thanks
Regards
Note: I might be away for several days. I'll try everything you say, but maybe I won't be able to post my feedback until monday night (around GMT timezone)
I have this exact problem.
So, when you power up the device, you press 'vol-down' when you see the Motorola logo? Because that should put you into fastboot mode. Don't use the power+vol-up, only turn on device and press vol-down when you see the logo. I've been in the same situation, but was able to get fastboot working like this...
if you hold the volume down button and power on the device and get no fastboot then you may as well just send it to motorola. looks like this is becoming a problem and cannot be fixed.
mbroeders said:
So, when you power up the device, you press 'vol-down' when you see the Motorola logo? Because that should put you into fastboot mode. Don't use the power+vol-up, only turn on device and press vol-down when you see the logo. I've been in the same situation, but was able to get fastboot working like this...
Click to expand...
Click to collapse
This. Flashing the wrong partition should *not* mean that you can't get into fastboot any more.
I know that volume down should get me to fastboot but in fact it doesn't. Windows never makes dong dong when i plug the xoom... My drivers are ok because my nexus one gets recognized instantly and adb is working fine on the phone...
Any reason you don't use RSD to flash the wifi xoom sbf file? (I'm pretty sure someone said that was released not too long ago)
I didn't try yet, I can't find the SBF for the wifi xoom.
I tried the 3G SBF file it's not even working. I know it's not the right file for my device but since it's already bricked...
I have RSD Lite 4.9, latest moto drivers, updated using the moto tool.
When I load the sbf file in rsd lite, I can't see the device, and pushing start has no effect.
I did that when the device was showing "Starting RSD mode 3"
How can I get it back?! I tried on my windows laptop and also on a macbook, without any luck.
This is happened to me , and i flipped cuz i rendered my $600 Xoom to a paper weight , i rebooted (Volup+power then voldown) , i tried ADB and it didn't work... then i left my computer to do something, i returned to my PC and i was flipping through DOS command lines (up and down arrows) and click enter in one of the commands by mistake and it worked! the command was "fastboot erase cache"
i then typed the following to return to stock (you need the stock files)
Code:
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
Thanks, but I don't have fastboot. It's always < waiting for device >
Topper Harley said:
Thanks, but I don't have fastboot. It's always < waiting for device >
Click to expand...
Click to collapse
You mentioned you tried the steps in http://forum.xda-developers.com/showthread.php?t=973355, but how did this section go:
"Even though there was no response from the device, I pressed Vol Down + power until the screen went black. I then quickly pressed and held Vol Up + power. The device then went into the bootloader, received the queued command from fastboot, and flashed the boot.img."
ed. The other suggestion I heard floating around is to flash the CDMA Xoom's SBF -- yes, it won't get you all the way there, but it might restore things up to the point where you can get into fastboot and then flash the stock images.
I did try already to fastboot flash boot boot.img (stock), then reboot pushing vol up, vol down, both, using clicking or holding them... no luck
I also tried to flash the VZW SBF file but RSD Lite doesn't even see the device. I'm trying now to get some linux running and use sbf_flash instead because I was told that it's more efficient than the linux one.
No luck yet on that part either.
I was able to get my xoom restore with the following steps:
Hold Power + Vol up to start reboot
immdiately hold Power + Vol down (This will get you to the Fastboot menu)
enter the commands
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 fastboot oem lock, wait for the menu, the 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.
hoopsdavis said:
I was able to get my xoom restore with the following steps:
Hold Power + Vol up to start reboot
immdiately hold Power + Vol down (This will get you to the Fastboot menu)
Click to expand...
Click to collapse
It stops here. I can't get fastboot.
I tried waiting for the battery to die and tried every combination of vol up/down/power, hold/click/double click the buttons...
I'll let it cool off for one day without battery... maybe it'll wake up wanting to give me fastboot...
I'm losing hope...
Topper Harley said:
It stops here. I can't get fastboot.
I tried waiting for the battery to die and tried every combination of vol up/down/power, hold/click/double click the buttons...
I'll let it cool off for one day without battery... maybe it'll wake up wanting to give me fastboot...
I'm losing hope...
Click to expand...
Click to collapse
I'm in the same situation here... tried basically all the same steps. I'm lost too... can't connect with ADB, Fastboot or RSD... tried all kinds of key combos as well. "Starting RSD Mode 3"... its wearing me down!!
How can i change the topic title? I wanted to say "xoom bricked?" but I typed rooted by mistake
I'm in this exact situation, and I've tried everything suggested here. I spent some time in IRC talking to a few developers, and we tried pretty much everything to get fastboot to work. No luck, so I tried RSD like you said, and that didn't work, either. Eventually we gave up, and I got an RMA from Motorola via their website. I should receive the FedEx box tomorrow so I can return it to them.
If you want, I'll report back here when the whole process is over and tell you if they end up fixing it for free or not. It sounds like it'll probably be at least a week, though.
benso87: yes, tell me. I have time don't worry (away from home until may 28th)
Otherwise, I think mine is definitely a brick. I tried the last thing I didn't: boot linux and test sbf_flash: not working.
I'll try to send it to moto (the device is imported).
I'm kinda sad... not for the money, but for the bad command that completely destroys a device in seconds... and right, for the money aswell...
Small update: I got the box yesterday and sent it back, then got an email this morning saying Motorola received it. Hopefully the whole process will go this fast.
They gave me a tracking number and a site to check to see how things are going, so that's more info than I was expecting. They haven't asked any questions yet, so that's also good.
Hi
After being on numerous custom Roms for the xoom I decided to return to stock and was succesful in return to the 3.01 stock image for the wifi MZ604 model
I was also successful in relocking the xoom.
I then began to receive the offical updates though everytime the were applied I had to go into recovery and wipe the device as otherwise it would bootloop on the dual core screen.
On the last update that it received and that was installed , on rebooting nothing happend and the screen just went blank
No combination of volume up + power would show any sign of doing anything.
After leaving the tablet to the side for awhile I noticed it came up with the following
model mz604 : Revision0 (0x8000) modem none
InitBl Info function failed with codes 299/3
failed to boot 0x0001
starting RSD mode 3
one wire : charger is not connected or battery is not being charged
battery charge level : 56%
I tried fastbooting and adb at this point but no devices are found. However when plugging in the xoom my laptop recognises something is attached.
After some searching I found out about RSd lite and SBF files.
When opening rsdlite v5.6 (running as admin) the tablet is recognised and I have now attempted to use two sbf files
HUBWF_W5.H.6.4-20_SIGNED_UCAHUBLWFRTCOREEU_P010_A010_M004_HWwifi_hubble_AP1FF.sb f
and
HUBWF_W5.H.6.2-24_SIGNED_UCAHUBLWFRTCOREEU_P006_A006_M003_HWwifi_hubble_Service1 FF.sbf
however both fail when it attempts re numeration.
I would greatly appreciate any help that anyone could give on this
Thanks
Try this.
My mom's Xoom had a similar problem. Reboot the tablet by pressing Volume Up and Power.
Then quickly turn on the xoom and press the down button as fast as possible, and continue pressing until you see "Recovery Mode" (or something similar) on the top left of the screen.
Once you see that, press the volume up button. Quickly, when you see the Android guy with the exclamation mark tap the power button and the up button.
This will take you to recovery mode. In there use the up and down volume keys to navigate and the power button to confirm things.
Go down to restore/delete data (may vary) and press power. use the volume down key to scroll to Yes.
This will restore your tablet back to factory settings. If you're trying to backup your data, don't try... No such luck and you won't be able to without the tablet booted.
thanks for the reply but this didnt work. Tried quite a few times. The screen just goes blank and again after a long while the error shown in the op appears. Should add there is no Motorola logo showing.
I have also tried forcing fastboot by the instructions found in other similar threads but again this does not work.
I think my best bet is the SBF files , but need to understand why this is failing on re-numeration
Well, I was using the version ics, rooted, and I upgraded to jb via ota, but I had several problems, such as high power consumption and decided to flash the sbf of jb via rsd lite ... That is, besides losing root now I can not go back to ics. how could downgrade? help me please!! thank you
please, help meeeee!!!
asaaaave me!!!!
My battery is suck!!!!!!!! And i disabled all that can drain my battery, incluiding google now!
Would help to know if you're on XT925 or XT926...
If you're on the XT926 you could use Matt's Droid Razr utility. If you're on the XT925 try using a fastboot for ICS.
lecomiquelin said:
Well, I was using the version ics, rooted, and I upgraded to jb via ota, but I had several problems, such as high power consumption and decided to flash the sbf of jb via rsd lite ... That is, besides losing root now I can not go back to ics. how could downgrade? help me please!! thank you
Click to expand...
Click to collapse
If you have a XT925 then
Download an RUU rom from the "Firmware SuperThread" http://forum.xda-developers.com/showthread.php?t=1943879
Power down your device
Press and hold the Vol+ and Vol- keys, then press and hold the power button until a white screen appears and you can now release all three buttons.
Use the Vol- key (and ONLY the Vol- key) to scroll through the list. Scroll until “AP Fastboot” is highlighted and press the Vol+ key to select it.
Then unzip the file you downloaded, inside will be a file called "flash_fastboot.bat" Run it.
Should Work.
So guys
thanks for the help, but I had tried it all, that is if I had just updated via ota I could return quietly via rsd or fastboot, but I updated to jb via rsd, no ota ...
So as I tried to go back to ics via rsd or fastboot error appeared preflash, dronwgrade security, and never worked out
I just unlocked the bootloader and lost the warranty :/
And Incredibly, even going back to ics, my battery did not return as before, is very bad, and already I did everything
Not to mention that fastboot is not coming back, it was updated with the jb, and now every time I turn on the phone it connects into fastboot, and then gotta enter the vol -, vol + and power and select Normal power up
Is it still may have left over kernel, or another part of jb on ics?
I've done factory reset, and deleted userdata etc.
There's something very strange now.
---------
Ah
Before unlocking the bootloader I also had tried flashing without flash partition line (. Xml file), and various other modes, fastboot, using the razr hd utility, but nothing worked ... It was really necessary unlock to make a donwgrade ...
and my phone is xt925
I was so happy with the device, then I did sh*t and now I'm super sad
I was trying to take my wife's XT926 back to stock and think I may have bricked the device. The phone was on 4.1.2 and was rooted and I ran this utility http://forum.xda-developers.com/showthread.php?t=2757285
The phone is now stuck on the AP Fastboot menu and here's what it says:
Device is Locked. Status Code:0
Battery OK
Transfer Mode: USB connected
No valid PIV block in SP for system
piv validation failed (system)
fastboot Reason: Boot Failure
usb connected
I cannot get into the stock recovery to do a factory reset. I've tried holding down the volume up button when powering on and it brings up the boot menu, but the phone always goes to this screen no matter what I select.
Not sure if I did something wrong, but I thought I followed all of the instructions. I've done plenty of rooting and tinkering with other phones and this is the first time I've had a problem like this.
Any ideas?
EDIT: This was the only thing that worked for me:
http://www.droidrzr.com/index.php/topic/45494-how-to-xt926-upgrade-to-kitkat-ota/
My device is a BKL-L09
Previously running cr6.1 (8.1)
When I tried flashing a new Kernel(Radioactive) thinking it might fix the safetynet CTS profile mismatch, it (or actually I) broke something so that now I can't boot into the custom recovery or the system. eRecovery seems to work just fine (except that it, well ... doesn't since I have the international version where restoring is a non-working option).
That being said I can't really boot anything and I've already been looking everywhere on how to boot(not unlock) into the BL from shutdown. But all didn't work.
Does somebody have a working BKL-L09 and can look into booting it?
Edit:
eRecovery boots everytime after 3 times of bootlooping.
The phone will restart on it's own after having it shutdown after 15!! seconds of pressing the power button (is this behaviour normal?) and the only way to shut it down for good is selecting "shutdown" in eRecovery.
No matter the other buttons, pressing VOL UP will always boot the update installer, which will always output "Software install failed! (get help from...)"
MY00 said:
My device is a BKL-L09
Previously running cr6.1 (8.1)
When I tried flashing a new Kernel(Radioactive) thinking it might fix the safetynet CTS profile mismatch, it (or actually I) broke something so that now I can't boot into the custom recovery or the system. eRecovery seems to work just fine (except that it, well ... doesn't since I have the international version where restoring is a non-working option).
That being said I can't really boot anything and I've already been looking everywhere on how to boot(not unlock) into the BL from shutdown. But all didn't work.
Does somebody have a working BKL-L09 and can look into booting it?
Edit:
eRecovery boots everytime after 3 times of bootlooping.
The phone will restart on it's own after having it shutdown after 15!! seconds of pressing the power button (is this behaviour normal?) and the only way to shut it down for good is selecting "shutdown" in eRecovery.
No matter the other buttons, pressing VOL UP will always boot the update installer, which will always output "Software install failed! (get help from...)"
Click to expand...
Click to collapse
can you either delet this thread or delete your post in the kernels thread... no need for duplicates mate.
i also posted your solution... search around for how to get into fastboot mode (it can be trucky, but it us possible with some patience)
and the fastboot flash both your backed up stock kernel.img and ramdisk.img
kevp75 said:
can you either delet this thread or delete your post in the kernels thread... no need for duplicates mate.
i also posted your solution... search around for how to get into fastboot mode (it can be trucky, but it us possible with some patience)
and the fastboot flash both your backed up stock kernel.img and ramdisk.img
Click to expand...
Click to collapse
Sorry, I must've missed the L04(too thrilled :cyclops.
But I don't really care about the data (of course I would like it back, but... priorities), and right now I have a broken phone that won't boot into BL nmw.
List i tried:
Vol down; 3s; cable
Vol down; cable
Same with vol up and vol up/down
just power on loads erecovery after a bit
Vol up gives installing update
I think I somehow broke my BL.
Is a kernel pre or past BL on boot? (Pre, isn't it..?)