When I run the command fastboot devices, does not detect the phone.
When I run the command fastboot flash recovery recovery-clockwork-5.0.2.3-droid2we.img, shows waiting device.
droid 2 global, is updated to android 2.3.3.
yep. d2g doesn't have fastboot, and you can't flash recoveries like that on moto phones anyway
Related
My Xoom has had an odd problem. When I got it new, I unlocked the bootloader and rooted.
However, any pushed updates from Moto such as HLK55 caused my Xoom to boot and show the unhappy !Android icon. I had to shut down cold, and reboot. In other words, it never updated properly.
Now that ICS is out, I have Kang 1/15 running but have some non-crash issues. I'd like to flash to try to update to the factory ICS push file but fear that my XOOM won't complete as well.
Any ideas?
So long as you flash back to complete stock using the Motorola files you should be able to upgrade your way up to ICS (via 3.1 and 3.2).
Get the files from http://developer.motorola.com/products/software/
And as on that page, get ADB running and make sure it detects your device then run these commands.
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
Make sure you get the right version for your device.
Basically, my xoom has been rooted and currently I have CynogenMod9 RC0 Wingray currently installed.
I wanted to install a new rom but I couldn't do this using CWM Recovery as the SD Card doesn't Mount. Upon doing some reading I found I need to install the Rogue (or EOS) Recovery image. This is where my problems begin as I can connect to the device when the xoom is fully booted in the CM9 and connected via debugging mode(running adb devices returns a sequence of numbers ).
But then when I reboot into the bootloader it gets stuck on "Starting Fastboot protocol support." and i can't connect via adb!!!
I believe this started happening after I unlocked the bootloader but i can't be 100% sure (fastboot oemunlock)
Please help!!!
When it is on fastboot mode you can only use fastboot commands (fastboot flash recovery recovery.img) that is how you would install the recovery image from rogue or EOS or TWRP, whichever you choose.
Or to make it easier, you can boot your tablet, install GOO Manager. When you open the GOO manager, tap the setting in the top right corner and choose Install Open Recovery script and let it install TWRP. Then boot to recovery.
Sent from my SGH-I747 using xda premium
d3athsd00r said:
When it is on fastboot mode you can only use fastboot commands (fastboot flash recovery recovery.img) that is how you would install the recovery image from rogue or EOS or TWRP, whichever you choose.
Sent from my SGH-I747 using xda premium
Click to expand...
Click to collapse
But it never gets into fastboot mode now.
miahmad said:
But it never gets into fastboot mode now.
Click to expand...
Click to collapse
You specifically said it says starting fastboot protocol. That's as far as it goes. You then issue fastboot commands, not adb commands
Sent from my SGH-I747 using xda premium
Moved to Q & A.
Sent from my Galaxy Nexus using Tapatalk 2
d3athsd00r said:
You specifically said it says starting fastboot protocol. That's as far as it goes. You then issue fastboot commands, not adb commands
Sent from my SGH-I747 using xda premium
Click to expand...
Click to collapse
Ohh ok, makes sense. I will give it a try later when i'm home. Is there a Fastboot command i can use to check the device is connected??
miahmad said:
Ohh ok, makes sense. I will give it a try later when i'm home. Is there a Fastboot command i can use to check the device is connected??
Click to expand...
Click to collapse
fastboot devices
miahmad said:
Basically, my xoom has been rooted and currently I have CynogenMod9 RC0 Wingray currently installed.
I wanted to install a new rom but I couldn't do this using CWM Recovery as the SD Card doesn't Mount. Upon doing some reading I found I need to install the Rogue (or EOS) Recovery image. This is where my problems begin as I can connect to the device when the xoom is fully booted in the CM9 and connected via debugging mode(running adb devices returns a sequence of numbers ).
But then when I reboot into the bootloader it gets stuck on "Starting Fastboot protocol support." and i can't connect via adb!!!
I believe this started happening after I unlocked the bootloader but i can't be 100% sure (fastboot oemunlock)
Please help!!!
Click to expand...
Click to collapse
These are what i use from day 1
INSTRUCTIONS TO FLASH & RE-LOCK YOUR MOTOROLA XOOM:
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
---------------------------------------------------------------------------------------------------------------------
Type:
adb reboot bootloader
fastboot oem unlock
fastboot flash recovery eos-recovery-r6-softkeys.img
fastboot flash recoverytwrp-2.2.1-stingray_cdma.img
fastboot reboot
adb reboot recovery
-------------------------------------------------------------------------------------------------------------------------
Code:
adb reboot bootloader
fastboot oem unlock
fastboot reboot
3. Flash recovery
Code:
adb reboot bootloader
fastboot flash recovery recovery-Tiamat-R4c-100611-1150-cwm.img
Hello
I have a Motorola Xoom from Verizon, and this is the issue.
When I turn on, the tablet it's stuck in M logo screen, I already read almost any information about this issue, but still I can't use my xoom.
I already done this: the bootloader is already unlock
a) Files From MZ600 HRI39
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash userdata userdata.img
fastboot erase cache
b) used RSD method
c) used recovery method too
I had used every method on this forum to recover my Xoom, and nothing seems to work, at this time I don't know what else do.
adb commands doesn't work for me, only with fastboot and RSD is visible my device.
At this time I accept any sugestions, Since apply a factory reset, or install a new Android version
Oh no! Looks like your kindle wont boot! Dont worry, this thread got ya covered. Welcome to the Unbricking Station!
NOTE: I DO NOT TAKE RESPONSIBILITY IF THESE METHODS WILL MAKE YOUR DEVICE WORSE. USE AT YOUR OWN RISK.
1. I have a red screen at boot-up. What should i do?
This happens when you install the 2nd bootloader when you are on
software version 7.3.0 or higher, even though you downgraded to 7.2.3 the 7.3.0-7.X.X bootloader will retain.
SOLUTION: Flashing the 7.2.3 uboot file will do the trick by booting into fastboot with a fastboot cable and type these commands
fastboot -i 0x1949 flash bootloader kfhd7-u-boot-prod-7.2.3.bin
or if that doesnt work and you have backed-up your stock boot, recovery, and system type these
fastboot -i 0x1949 flash boot stock-boot.img
fastboot -i 0x1949 flash recovery stock-recovery.img
fastboot -i 0x1949 flash system stock-system.img
2. When i bootup it just gets stuck in the blue kindle fire logo or the bootanimation. What should i do?
This happens when you installed the 2nd bootloader successfully and you might have killed a binary during stack installation, or you might have messed with the system files of your OS.
SOLUTION: If you can boot up to TWRP (recovery), you can just flash the stock Amazon OS or CyanogenMod once again.
Booting to recovery can be done by just pressing the volume up button while in the ORANGE kindle fire logo, after that just press install and select which OS you had before the error.
Amazon OS: http://forum.xda-developers.com/showthread.php?t=2218475
CyanogenMod 10.1: http://forum.xda-developers.com/showthread.php?t=2245335
Use adb sideload, if you don't have these files on the kindle's internal storage.
Go to advanced, then to ADB Sideload.
While in your computer, go to a command prompt and type
Adb sideload *osfilename*.zip
After that, it will install itself and you are good to go!
3. When i flashed FireFireFire/broke the bootloader, it wont startup, what should I do?
You flashed a incompatible bootloader (1st Gen) on a 2nd Gen device.
SOLUTION: Your best bet is just send it back for a replacement.
If anyone have anymore methods to unbrick their device, send me a PM to get a chance for your method to be featured in this thread.
Credits to Hashcode for the bootloader and to Amazon for a wonderful device. xD
Yesterday I unlocked my bootloader on Moto G XT1033.After that I tried to flash CWM using mfastboot but after booting to recovery I get black screen with white/multi-colored lines and its gets stuck there.
However,I can still boot to my stock rom (Android 4.4.4) successfully.
I also tried flashing TWRP and Philz but i get the same problem everytime.Please help..
modifan14 said:
Yesterday I unlocked my bootloader on Moto G XT1033.After that I tried to flash CWM using mfastboot but after booting to recovery I get black screen with white/multi-colored lines and its gets stuck there.
However,I can still boot to my stock rom (Android 4.4.4) successfully.
I also tried flashing TWRP and Philz but i get the same problem everytime.Please help..
Click to expand...
Click to collapse
try using regular fastboot from the android sdk platform tools
and the latest TWRP build
and use this command
Code:
fastboot flash recovery openrecovery-twrp-2.8.1.0-xt1032.img
or
Code:
fastboot boot openrecovery-twrp-2.8.1.0-xt1032.img
make sure to the recovery img file in the same folder where fastboot and adb files are
AgentChaos said:
try using regular fastboot from the android sdk platform tools
Code:
fastboot boot openrecovery-twrp-2.8.1.0-xt1032.img
make sure to the recovery img file in the same folder where fastboot and adb files are
Click to expand...
Click to collapse
Thanks. The above command worked perfectly.