Database Info

Help with Fastboot

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

[Q] After erasing the recovery with fastboot my LG p350 don't start

Hello,
I have followed a tutorial for solving the problem of "Fastboot mode started
udc_start()" from this thread http://forum.xda-developers.com/showthread.php?t=2131247 and something was go wrong.
I have done this steps in the sdk platform tools folder:
1- fastboot erase recovery
2- fastboot flash recovery recovery.img ( here i've got an error)
3- fastboot reboot
Everyting was ok until I have tried to write the .img file on the phone. I've got an error that I don't have enough space. I think I have deleted the recovery file and now it's stuck, because it's not booting. The 4 leds from the bottom it's flashing continuously and the screen remains to the LG logo. I have tried to connect the phone to the PC but the device it's not recognized anymore. I get this message in the adb tool "Waiting for device"
I really appreciate if it's someone that can help me

I have a p500 and I had the exact same problem as you. But I was able to fix it after a lot of Googling.
Can you get to fastboot right now? If so, make sure that the recovery you downloaded is correctly named "recovery.img" and is placed in the same folder as adb.exe is located. After that, type:
Code:
fastboot devices
into ADB. If your device is listed then proceed and type:
Code:
fastboot flash recovery recovery.img
If nothing comes up when you ask it to list fastboot devices you need to delete all of the drivers associated with your p350, and then reinstall them using a toolkit or PDAnet. Then go back and try fastboot devices again.
.

Logan_M said:
I have a p500 and I had the exact same problem as you. But I was able to fix it after a lot of Googling.
Can you get to fastboot right now? If so, make sure that the recovery you downloaded is correctly named "recovery.img" and is placed in the same folder as adb.exe is located. After that, type:
Code:
fastboot devices
into ADB. If your device is listed then proceed and type:
Code:
fastboot flash recovery recovery.img
If nothing comes up when you ask it to list fastboot devices you need to delete all of the drivers associated with your p350, and then reinstall them using a toolkit or PDAnet. Then go back and try fastboot devices again.
.
Click to expand...
Click to collapse
No, I can't get to fastboot. I can't do anything with the command line. It remains to the logo screen

catalin11 said:
No, I can't get to fastboot. I can't do anything with the command line. It remains to the logo screen
Click to expand...
Click to collapse
Can you pull the battery and then use the combination to get into Fastboot? If you can't get to fastboot, then the problem is beyond what I'm capable of doing.
Though, the problem may be that you completely deleted your recovery.

Logan_M said:
Can you pull the battery and then use the combination to get into Fastboot? If you can't get to fastboot, then the problem is beyond what I'm capable of doing.
Though, the problem may be that you completely deleted your recovery.
Click to expand...
Click to collapse
Now, I'm back to the first problem
"Fastboot mode started udc_start()
-- suspend --
-- suspend --
"

catalin11 said:
Now, I'm back to the first problem
"Fastboot mode started udc_start()
-- suspend --
-- suspend --
"
Click to expand...
Click to collapse
if i write this in cmd "fastboot flash recovery recovery.img" it apear < waiting for device > and nothing happens

catalin11 said:
if i write this in cmd "fastboot flash recovery recovery.img" it apear < waiting for device > and nothing happens
Click to expand...
Click to collapse
now i'm in the emergency mode

Problem solved:
1- download the official drivers from LG Site
2- cmd and:
fastboot erase boot
fastboot erase system
fastboot erase userdata
fastboot -w
fastboot flash recovery recovery.img (Clowork custom recovery)
Fastboot Reboot
Installing Cyanogen after i erase everything (fastboot erase sdcard). I like fresh starts

some1 pls help me
catalin11 said:
Problem solved:
1- download the official drivers from LG Site
2- cmd and:
fastboot erase boot
fastboot erase system
fastboot erase userdata
fastboot -w
fastboot flash recovery recovery.img (Clowork custom recovery)
Fastboot Reboot
Installing Cyanogen after i erase everything (fastboot erase sdcard). I like fresh starts
Click to expand...
Click to collapse
can u plz elaborate...i too have the same problem....plz..

Logan_M said:
If so, make sure that the recovery you downloaded is correctly named "recovery.img" and is placed in the same folder as adb.exe is located.
Click to expand...
Click to collapse
That is incorrect. The recovery does NOT have to be named recovery to use fastboot to flash it, although it does make life simpler

Bricked Moto G - Need help urgently!

So, I am in the middle of trying to fix my Moto G that is bricked/bootloop.
What happened is that I "accidentally" factory reset my phone using Philz Touch Recovery, after I did that, my phone wouldn't boot. After doing some research on the interwebs I found that since Philz is based of CWM it also deleted the /os folder, so I had to install a custom ROM to fix it. I did install 2 different ROM's twice each (CM11 and Carbon) and still am stuck in a boot loop. (I wiped cache and data .etc before I installed) I have no idea what to do, please help me!
TL;DR: Moto G stuck in Bootloop/bricked

Megadarkwood said:
So, I am in the middle of trying to fix my Moto G that is bricked/bootloop.
What happened is that I "accidentally" factory reset my phone using Philz Touch Recovery, after I did that, my phone wouldn't boot. After doing some research on the interwebs I found that since Philz is based of CWM it also deleted the /os folder, so I had to install a custom ROM to fix it. I did install 2 different ROM's twice each (CM11 and Carbon) and still am stuck in a boot loop. (I wiped cache and data .etc before I installed) I have no idea what to do, please help me!
TL;DR: Moto G stuck in Bootloop/bricked
Click to expand...
Click to collapse
First things first..there are many Moto G models..which model do you have.?
And what version OS is your device on.?
sent by my 4.2.2_12.15.15
(Unlocked) XT1080M Droid Maxx #1
http://waynekent.com/page6.html

NWKENT said:
First things first..there are many Moto G models..which model do you have.?
And what version OS is your device on.?
sent by my 4.2.2_12.15.15
(Unlocked) XT1080M Droid Maxx #1
Click to expand...
Click to collapse
It's on 4.4.2 and I don't know the model number but its the Canadian Rogers Version

Megadarkwood said:
It's on 4.4.2 and I don't know the model number but its the Canadian Rogers Version
Click to expand...
Click to collapse
Try to flash your recovery again, IF you cannot get back into recovery..which ever one you are using, flash again and go into the recovery in order to erase cache/dalvik..if you do erase cache/dalvik and still in a bootloop, then most likely you'll need to flash a new/undefiled OS..
There is a chance that a flash of OS could be done without loosing all your data, but a custom FXZ would be needed..
Go down this list and find your device OS..and download..and flash the new/fresh OS..this list is factory FXZ's which will erase your data..
I personally prefer TWRP recoveries..
Here >> http://sbf.droid-developers.org/phone.php?device=14
Sent from my 4.4_19.6.3
(Unlocked) XT1080M Droid Maxx #2
http://waynekent.com/page6.html

NWKENT said:
Try to flash your recovery again, IF you cannot get back into recovery..which ever one you are using, flash again and go into the recovery in order to erase cache/dalvik..if you do erase cache/dalvik and still in a bootloop, then most likely you'll need to flash a new/undefiled OS..
There is a chance that a flash of OS could be done without loosing all your data, but a custom FXZ would be needed..
Go down this list and find your device OS..and download..and flash the new/fresh OS..this list is factory FXZ's which will erase your data..
I personally prefer TWRP recoveries..
Here >>
Sent from my 4.4_19.6.3
(Unlocked) XT1080M Droid Maxx #2
Click to expand...
Click to collapse
Alright, so since I am a noob let me get this right..
Wipe dalvik cache, done. Still in bootloop.
Now I should flash a new recovery? I am still able to get into my current one.
Sorry for my noob-ness.

Megadarkwood said:
Alright, so since I am a noob let me get this right..
Wipe dalvik cache, done. Still in bootloop.
Now I should flash a new recovery? I am still able to get into my current one.
Sorry for my noob-ness.
Click to expand...
Click to collapse
OK..if you erased cache..then that's all you can do with that..
Reflash your recovery..make sure you have a known good recovery for your particular device..if reflash recovery and still a bootloop..then flashing a clean/fresh OS is the only thing that is left..of course you certainly deserve a second opinion..
If you are concerned about loosing all your data..then there is a way to flash a new/clean OS without erase your data..BUT..it takes a special modified FXZ to do so, and get your device back up..
Sent from my 4.4_19.6.3
(Unlocked) XT1080M Droid Maxx #2
http://waynekent.com/page6.html

NWKENT said:
OK..if you erased cache..then that's all you can do with that..
Reflash your recovery..make sure you have a known good recovery for your particular device..if reflash recovery and still a bootloop..then flashing a clean/fresh OS is the only thing that is left..of course you certainly deserve a second opinion..
If you are concerned about loosing all your data..then there is a way to flash a new/clean OS without erase your data..BUT..it takes a special modified FXZ to do so, and get your device back up..
Sent from my 4.4_19.6.3
(Unlocked) XT1080M Droid Maxx #
Click to expand...
Click to collapse
I am not concerned about any data, just need to get it working. I will flash TWRP as soon as I get back to my computer

Bro, try flashing TWRP, it's easier (my opinion) to use... Do you have the .zip of CM11? If yes, make a Factory Reset and install CM11. If it still in a bootloop, instal the stock firmware.
Sent from my Moto G using XDA Premium 4 mobile app

NWKENT said:
OK..if you erased cache..then that's all you can do with that..
Reflash your recovery..make sure you have a known good recovery for your particular device..if reflash recovery and still a bootloop..then flashing a clean/fresh OS is the only thing that is left..of course you certainly deserve a second opinion..
If you are concerned about loosing all your data..then there is a way to flash a new/clean OS without erase your data..BUT..it takes a special modified FXZ to do so, and get your device back up..
Sent from my 4.4_19.6.3
(Unlocked) XT1080M Droid Maxx #2
Click to expand...
Click to collapse
nArdow said:
Bro, try flashing TWRP, it's easier (my opinion) to use... Do you have the .zip of CM11? If yes, make a Factory Reset and install CM11. If it still in a bootloop, instal the stock firmware.
Sent from my Moto G using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Alright, how am I supposed to sideload the .img for TWRP?

Just download TWRP and flash using your current recovery.. Also you could try going into advance in TWRP and clicking fix permissions..
If you cannot flash a new Recovery using the recovery already on the device.. Flash with adb.
Download a new recovery using a PC.
Place the .IMG into your fastboot folder.
Rename the recovery 'recovery.img' without quotes.
Boot into bootloader.
On your PC hold shift and right click the folder your fastboot is in and select to start your cmd directory their.
A command window should open and type...
"Fastboot flash recovery recovery.img"
Sent from my XT1032 using Tapatalk

Clarkiieh said:
Just download TWRP and flash using your current recovery.. Also you could try going into advance in TWRP and clicking fix permissions..
If you cannot flash a new Recovery using the recovery already on the device.. Flash with adb.
Download a new recovery using a PC.
Place the .IMG into your fastboot folder.
Rename the recovery 'recovery.img' without quotes.
Boot into bootloader.
On your PC hold shift and right click the folder your fastboot is in and select to start your cmd directory their.
A command window should open and type...
"Fastboot flash recovery recovery.img"
Sent from my XT1032 using Tapatalk
Click to expand...
Click to collapse
Won't work, says "Waiting for Device"

Megadarkwood said:
Won't work, says "Waiting for Device"
Click to expand...
Click to collapse
I will try and make this simple as possible, this process will get your device back to stock if you are able to get into fastboot mode.
- Step 1: Put device into fastboot mode.
- Step 1a: Run ADB and check for devices.
Code:
adb devices
- Step 1b: If ADB cannot see the device unplug the USB and plug it back in.
- Step 1c: Run ADB and check for devices again, if device is detected in ADB move to step 3, if not continue on to step 2.
Code:
adb devices
- Step 2: If ADB does not detect the device unplug the USB
- Step 2a: Restart the device in fastboot mode
- Step 2b: Plug USB back in
- Step 2c: Run ADB and check for devices, if device is detected in ADB move to step 3.
Code:
adb devices
- Step 3: Start the flashing process with ADB using your systems firmware.
Code:
fastboot flash partition gpt.bin
fastboot flash motoboot motoboot.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk1
fastboot flash system system.img_sparsechunk2
fastboot flash system system.img_sparsechunk3
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot reboot
- or run the bat file for your firmware.
- Step 3a: If you get errors or hang ups at anytime during the flashing process after recovery.img make more than 1 attempt to run the command in ADB. I have the XT1034 and my sparsechunk2 and 3 along with erase cache and erase userdata likes to hang up and then fail but I am still able to fully restore my Moto G. I hope this helps.

The Closet Candian said:
I will try and make this simple as possible, this process will get your device back to stock if you are able to get into fastboot mode.
- Step 1: Put device into fastboot mode.
- Step 1a: Run ADB and check for devices.
Code:
adb devices
- Step 1b: If ADB cannot see the device unplug the USB and plug it back in.
- Step 1c: Run ADB and check for devices again, if device is detected in ADB move to step 3, if not continue on to step 2.
Code:
adb devices
- Step 2: If ADB does not detect the device unplug the USB
- Step 2a: Restart the device in fastboot mode
- Step 2b: Plug USB back in
- Step 2c: Run ADB and check for devices, if device is detected in ADB move to step 3.
Code:
adb devices
- Step 3: Start the flashing process with ADB using your systems firmware.
Code:
fastboot flash partition gpt.bin
fastboot flash motoboot motoboot.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk1
fastboot flash system system.img_sparsechunk2
fastboot flash system system.img_sparsechunk3
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot reboot
- or run the bat file for your firmware.
- Step 3a: If you get errors or hang ups at anytime during the flashing process after recovery.img make more than 1 attempt to run the command in ADB. I have the XT1034 and my sparsechunk2 and 3 along with erase cache and erase userdata likes to hang up and then fail but I am still able to fully restore my Moto G. I hope this helps.
Click to expand...
Click to collapse
Alright, but do I need a OS file or something in the folder before I do this?
Also, it reconizes the device with "adb devices" but it still says "Waiting for device"

Megadarkwood said:
Also, it reconizes the device with "adb devices" but it still says "Waiting for device"
Click to expand...
Click to collapse
Since you are in fastboot mode you should use "fastboot devices".

meekrawb said:
Since you are in fastboot mode you should use "fastboot devices".
Click to expand...
Click to collapse
It just doesn't work
screenshot: http://gyazo.com/f863d5e9bff06e49d375f62901a38520

Megadarkwood said:
It just doesn't work
screenshot: http://gyazo.com/f863d5e9bff06e49d375f62901a38520
Click to expand...
Click to collapse
Only thing I can think of is to re-install the drivers or try different USB ports.

Megadarkwood said:
It just doesn't work
screenshot: http://gyazo.com/f863d5e9bff06e49d375f62901a38520
Click to expand...
Click to collapse
First of all run the adb setup file and press (Y) all 3 times.
Next unzip the twrp.zip folder. Then flash the twrp recovery by using the "fastboot flash recovery twrp.img" command. Make sure phone is in fastboot mode.
Next boot the phone into the recovery and select advanced. Then click on terminal command and navigate to the /sdcard/ folder. Lastly click "select" on the bottom right corner.
Now download whatever rom and gapps you would like to install on your phone and rename them to something short. Then open a command prompt at the directory where the rom and gapps are. In the command prompt enter these commands "adb push NAMEOFROM.zip /sdcard/" and "adb push NAMEOFGAPPS.zip /sdcard/".
The command prompt will not show change for a few minutes. After you notice the command prompt is ready for the next command it is okay to exit it.
Now just flash the rom and gapps normally and hopefully your phone will be okay.
**BTW the adb setup program makes adb and fastboot accessible from any directory even without the actual adb and fastboot files.

eg0097 said:
First of all run the adb setup file and press (Y) all 3 times.
Next unzip the twrp.zip folder. Then flash the twrp recovery by using the "fastboot flash recovery twrp.img" command. Make sure phone is in fastboot mode.
Next boot the phone into the recovery and select advanced. Then click on terminal command and navigate to the /sdcard/ folder. Lastly click "select" on the bottom right corner.
Now download whatever rom and gapps you would like to install on your phone and rename them to something short. Then open a command prompt at the directory where the rom and gapps are. In the command prompt enter these commands "adb push NAMEOFROM.zip /sdcard/" and "adb push NAMEOFGAPPS.zip /sdcard/".
The command prompt will not show change for a few minutes. After you notice the command prompt is ready for the next command it is okay to exit it.
Now just flash the rom and gapps normally and hopefully your phone will be okay.
**BTW the adb setup program makes adb and fastboot accessible from any directory even without the actual adb and fastboot files.
Click to expand...
Click to collapse
Got TWRP on and everything flashed but carbon is still in a boot loop.

Honestly dude I just bricked my phone converting to gpe and I somehow got out of it... Sometimes it can be a load of factors... Drivers is the biggie!! Delete your old ones reboot computer and reinstall..
Sent from my XT1032 using Tapatalk
---------- Post added at 10:39 PM ---------- Previous post was at 10:30 PM ----------
OK if you hear a beep when connecting your phone while it's in fastboot its not your drivers as such
.. If not tell me cause you will need to activate them!
Sent from my XT1032 using Tapatalk

Clarkiieh said:
Honestly dude I just bricked my phone converting to gpe and I somehow got out of it... Sometimes it can be a load of factors... Drivers is the biggie!! Delete your old ones reboot computer and reinstall..
Sent from my XT1032 using Tapatalk
---------- Post added at 10:39 PM ---------- Previous post was at 10:30 PM ----------
OK if you hear a beep when connecting your phone while it's in fastboot its not your drivers as such
.. If not tell me cause you will need to activate them!
Sent from my XT1032 using Tapatalk
Click to expand...
Click to collapse
Yeah I hear the beep.

[Being resolved!] MotoG Bootup Problem - Recovery Mode failed

CURRENT UPDATE 25/6 :
unlocked the bootloader and flashed the O.S (5.0.2) without erasing userdata.
stock recovery mode works now.
booted using custom recoveries : a)TWRP 2.8.X.X b)Philz Touch (will add details later)
data recovery almost done.
NEXT STEP : time to install a CLEAN STOCK ROM
PROBLEM : Not booting up to the Android lock-screen
DEVICE INFO :
Phone Model : Moto G XT 1033 Dual SIM (India)
No Root.Bootloader is LOCKED.No customizations.
ADB Debugging disabled (default).
Moto G XT1033(Black, 16 GB)
Using : Android Lollipop (the latest update done by OTA as part of System Update)
Upgraded : 2-3 weeks after the update was released.
Info from Motorola Media Manager (when connected through USB)
{
"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"
}
What Happened :
Day before : Phone switched off at 0% battery.
Put for recharge the next day (29/5) and I tried to switch it on as it reached 35%.
Didn’t boot.Tried a few more times.
I can access :
Only the bootloader
Problem after Moto Boot Animation
http://imgur.com/l5bUHyq
VIDEO :
Main problem :
https://drive.google.com/open?id=0B3l72ArFhLc1ZThqU3ZoY29hWWM&authuser=0
Recovery mode issue:
https://drive.google.com/open?id=0B3l72ArFhLc1LWJ2VXI3SmxEQjA&authuser=0
HD Quality Videos & Images
-> https://drive.google.com/open?id=0B...k50a3VEa1RmZGkwRjJja3E5M0NpSHQzQ3c&authuser=0
Windows Device Mgr:
http://i.imgur.com/lGjFzDR.jpg
What I tried :
http://i.imgur.com/Lq9qHs1.jpg
(suggested on motorola website)Reboot - 10 seconds
(suggested on motorola website)Reboot - 120 seconds power button
Erased cache using fastboot - works.
Recovery mode : I got “bootup failed”
ADB not able to detect the device.Fastboot can.
PC able to detect USB but as a “Falcon Device”
WHAT I WANT :
I want to get a copy of all my internal SD Card data,eg : photos,Contacts,WhatsApp folder,etc.
Flashing it in any way that causes data loss would be my last option.
Besides,i don't have relevant experience and would be asking a friend who has experience with this stuff.
What I found out :
Bootloader UNLOCK will wipe all my internal memory user data.
To root the phone,I’ll have to UNLOCK the Bootloader.
ADB can be used to backup using PUSH,PULL (may or may not require Android USB Debugging enabled)
Battery drained to 0% from 75% in one night when i kept the phone in the blank but bright screen mode.
STEPS AHEAD :
Service Centre Visit (Saturday) - Problem Detection -> Won’t be giving the phone since they might damage the data in a situation where it can be recovered.
More Research about such cases and solutions?
Eg : Battery replacement,re-adjustment.
Any way to make it appear as a storage volume on PC?
Any links,suggestions,etc. can
Motorola Support Says :
Service Centre can help
ADB Reqd to recover data
Or use backup software (how can I do this when i am not able to boot :| )
Went to a Service Centre today,they said they will have to "download" software to the phone to check for problems
So my data will be lost.
So I am currently searching for more solutions.
ANY ADVICE,TIP,COMMENT or even a positive post would be really appreciated.THANKS FOR READING

Do you have a custom recovery installed? If not, try installing TWRP from here: http://forum.xda-developers.com/moto-g/development/recovery-twrp-2-8-2-0-touch-recovery-t2980621
Then use the following ADB command: adb pull /sdcard c:/Motog_backup

Thanks for reading and giving your suggestion
I've never rooted,flashed or unlocked my device,no major modifications as well.
So no custom recovery.
I tried what you suggested but it didn't work for now.
Here's what I got :
Maybe because of the LOCKED Bootloader.
ADB doesn't detect my device probably because i don't have debugging enabled.
Thanks Again @lost101
lost101 said:
Do you have a custom recovery installed? If not, try installing TWRP from here: http://forum.xda-developers.com/moto-g/development/recovery-twrp-2-8-2-0-touch-recovery-t2980621
Then use the following ADB command: adb pull /sdcard c:/Motog_backup
Click to expand...
Click to collapse

@ravibhat - Could you unlock the Bootloader? See FAQ for instructions: http://forum.xda-developers.com/showthread.php?t=2537119

@lost101 : I did consider the option using the "fastboot oem lock" option.But it was claimed that it will delete my user data which i don't want

ravibhat said:
@lost101 : I did consider the option using the "fastboot oem lock" option.But it was claimed that it will delete my user data which i don't want
Click to expand...
Click to collapse
Ah yes, I forgot about that. Good thing you caught it.
XT1032 Retail Asia 5.0.2 Firmware Image: http://forum.xda-developers.com/moto-g/general/index-moto-g-falcon-factory-firmware-t3110795
mFastboot commands:
mfastboot flash system system.img_sparsechunk.0
mfastboot flash system system.img_sparsechunk.1
mfastboot flash system system.img_sparsechunk.2
mfastboot flash system system.img_sparsechunk.3​
Doing only the above commands will not erase userdata, only reinstall Android.

Hey @lost101,
I'll be using the firmware for XT1033 (Asia-Retail 5.0.2) since the one i have is the dual-sim version.
I came across additional commands in this format:
fastboot flash partition gpt.bin
fastboot flash motoboot motoboot.img
fastboot reboot-bootloader
fastboot flash logo Moto-logo.bin
fastboot flash boot boot.img
<SYSTEM IMAGE FLASH FILES go here - 4 commands like you said here since it's Lollipop>
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
Since I want to save my data i won't be using "oem unlock" and "erase userdata" commands.
So,
a) Can you tell me if there's a specific reason you didn't add them?Will they damage or reset any of my data or affect user partition?
They were also mentioned by a few folks who are trying something similar while trying to protect their data.
I thought they were part of the process.
b) mfastboot or fastboot - will using the normal "fastboot".exe cause any problems?And so you suggest mfastboot?
And thanks a lot for helping me out
lost101 said:
Ah yes, I forgot about that. Good thing you caught it.
XT1032 Retail Asia 5.0.2 Firmware Image: http://forum.xda-developers.com/moto-g/general/index-moto-g-falcon-factory-firmware-t3110795
mFastboot commands:
mfastboot flash system system.img_sparsechunk.0
mfastboot flash system system.img_sparsechunk.1
mfastboot flash system system.img_sparsechunk.2
mfastboot flash system system.img_sparsechunk.3​
Doing only the above commands will not erase userdata, only reinstall Android.
Click to expand...
Click to collapse

@ravibhat - the fastboot commands I mentioned are the only ones that should be necessary. Report back what happens, and if needed I will suggest additional commands.
mFastboot is preferred because it was created by Motorola for flashing these files. Traditional fastboot may fail to successfully flash the files, and often does.

Hey @lost101!
Man,i tried the commands you mentioned first,didn't work.
Also tried it with the other commands,still no result.
Overall : i didn't get any errors except the ones where i tried to flash a custom recovery.
When i choose the "Recovery" option in the bootloader - I get "booting failed" error for both stock and custom recovery images.
Also,i couldn't directly boot using a custom recovery image file using the "boot" command.
Is it something to do with the files i used or...something else?
Any other tips?
lost101 said:
@ravibhat - the fastboot commands I mentioned are the only ones that should be necessary. Report back what happens, and if needed I will suggest additional commands.
mFastboot is preferred because it was created by Motorola for flashing these files. Traditional fastboot may fail to successfully flash the files, and often does.
Click to expand...
Click to collapse

@lost101 :
Can't boot from stock recovery,however able to flash it (why???)
Can't boot or flash custom recovery (probably because bootloader is locked which i can understand.)
@deej_roamer @deeplyyoung : thoughts and advise please

ravibhat said:
@lost101 :
Can't boot from stock recovery,however able to flash it (why???)
Can't boot or flash custom recovery (probably because bootloader is locked which i can understand.)
Click to expand...
Click to collapse
Please provide a log of what mfastboot responds with when you try to flash a system.img as instructed above. Do not say 'it did not work' - I need to see exactly what is being said by mfastboot.

Hey @lost101
Sorry for not being clear.
Here's the exact response :
Response on the screen:
The responses upto "boot up failed" in the below image were the ones i got while trying to flash recovery images.
The responses below it are the ones i got for flashing those 4 commands.
After this when I try to bootup - the same problem as mentioned in the main thread - getting stuck after Motorola Logo on a blank but active screen.
VIDEO :
Main problem :
https://drive.google.com/open?id=0B3...WWM&authuser=0
Recovery mode issue:
https://drive.google.com/open?id=0B3...QjA&authuser=0
HD Quality Videos & Images
-> https://drive.google.com/open?id=0B3...Q3c&authuser=0
Anything else you'd like to know that can help
lost101 said:
Please provide a log of what mfastboot responds with when you try to flash a system.img as instructed above. Do not say 'it did not work' - I need to see exactly what is being said by mfastboot.
Click to expand...
Click to collapse

@ravibhat - You mention in OP: ADB can be used to backup using PUSH,PULL (may or may not require Android USB Debugging enabled)
When is it working? While the Android is booting up? If so, you could pull the /sdcard/ during that time.
Regarding your previous post:
Mismatched Partition Size - is a normal error when flashing TWRP and can be ignored. It does not mean flashing has failed.
mfastboot is successfully flashing the Android ROM (system.img)​Has anything changed if you let Android boot?

@lost101 :
ADB can be used but when i searched,USB Debugging Enabled seemed to be a per-requisite in almost all cases on XDA and other forums which I can't do right now since no access to settings.
Push,Pull can be used to backup and restore - tried this on an emulator (Bluestacks on PC) which was detected by it (image below).
My driver is :
I'm not sure if it's the right one or not,no way to test it except testing with "adb devices" in command line but fastboot works so i guess it is.
Fastboot works well in the bootloader,it was able to flash all system images including the ROM.
I am not sure whether this device is hard-bricked since i haven't tried the "fastboot erase userdata command".
No change in the Android boot up process - it's the same issue as before.
It took a little more time (5-10 seconds more to arrive at the blank but lit screen as in the video mentioning the problem) after those 4 commands but that was most likely due to stocking the new firmware.
What bothers me is that i am unable to boot into recovery directly or boot into it after flashing.
It shows "boot up failed" even for the flashed recovery.
lost101 said:
@ravibhat - You mention in OP: ADB can be used to backup using PUSH,PULL (may or may not require Android USB Debugging enabled)
When is it working? While the Android is booting up? If so, you could pull the /sdcard/ during that time.
Regarding your previous post:
Mismatched Partition Size - is a normal error when flashing TWRP and can be ignored. It does not mean flashing has failed.
mfastboot is successfully flashing the Android ROM (system.img)​Has anything changed if you let Android boot?
Click to expand...
Click to collapse

There is another command: adb reboot recovery
I am no longer clear. Can you access stock recovery mode? Power on while holding Vol up?

@lost101 :
adb doesn't work as i mentioned since it doesnt detect the device,probably since ADB debugging wasn't enabled.
And i cannot access stock recovery (like previously mentioned in the OP - same issue ) - it gives "boot up failed" error on the device.
These are the commands i can use right now (since only fastboot works) :
I would really like to save the data but if that's really not possible or practical at this point,i'd go for the second best option.
Unlock the bootloader - try flashing custom/stock images or recovery - take backup or use recovery software.
Any suggestions on unlocking the bootloader?

@ravibhat - I was under the impression accessing recovery from boot was different depending on Bootloader version. With v14.18, you power on while holding 'vol up.' With older Bootloaders - it's 'vol down.'

@ravibhat
OK so i have understood what problem you got
Now since you wanna save you data here's what you need to do( if it actually works)
As the system boots up, after 2 or 3( not exact) seconds the data partition is mounted ( this is necessary to boot up OS )
Now can you confirm that adb ( not fastboot) is working while you see the blank screen with backlit active
Report

@ravibhat - If you can boot into Stock Recovery, you can enable 'ADB Sideloading.' You will then be able to ADB pull /sdcard/ to PC.

Hey @lost101,
I am able to boot into the bootloader and use fastboot commands.
But when i select "Recovery" on the bootloader as shown in the image in the above post,it says "boot up failed".
I've flashed stock recovery and it was successful but unable to boot directly using "flash boot recovery.img" or even after successful flashing (by choosing Vol down button to navigate and then Vol Up button to select while in the bootloader)
lost101 said:
@ravibhat - I was under the impression accessing recovery from boot was different depending on Bootloader version. With v14.18, you power on while holding 'vol up.' With older Bootloaders - it's 'vol down.'
Click to expand...
Click to collapse
@sjandroiddeveloper
ADB doesn't detect my device.Is USB Debugging required to be enabled to use ADB ?
I don't have USB debugging enabled (it was disabled by default).
sjandroiddeveloper said:
Now can you confirm that adb ( not fastboot) is working while you see the blank screen with backlit active
Report
Click to expand...
Click to collapse
Yes,i saw a lot of posts suggesting this but unfortunately the device doesn't get detected by ADB,also i don't understand the reason why i can boot into Stock Recovery despite being able to successfully flash it,it always says "booting failed".
lost101 said:
@ravibhat - If you can boot into Stock Recovery, you can enable 'ADB Sideloading.' You will then be able to ADB pull /sdcard/ to PC.
Click to expand...
Click to collapse

HP Slate 21 S100 Booting Failed

Friends I have an HP Slate 21 S100.
I installed TWRP a few days ago.
Then I installed software with TWRP and my device was working without any problems.
Then I said to install another software again and the device crashed.
First, I could not enter TWRP, although I reinstalled.
Then it went to boot menu while experimenting with fastboot.
This is the screen when I enter the recovery menu.
{
"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"
}
This is the error she gave when she selected the Recovery Mode
Then it returns to this screen again.
I would be glad if you could help.

gokhanc5 said:
Spoiler: didnt want to clog the thread with repeats of your pics
Friends I have an HP Slate 21 S100.
I installed TWRP a few days ago.
Then I installed software with TWRP and my device was working without any problems.
Then I said to install another software again and the device crashed.
First, I could not enter TWRP, although I reinstalled.
Then it went to boot menu while experimenting with fastboot.
This is the screen when I enter the recovery menu.
This is the error she gave when she selected the Recovery Mode
Then it returns to this screen again.
I would be glad if you could help.
Click to expand...
Click to collapse
id reflash the stock firmware and re-root from there should you choose to do so

Youdoofus said:
id reflash the stock firmware and re-root from there should you choose to do so
Click to expand...
Click to collapse
thank you you answered. I'm uploading boot.img and recovery.img via fastboot. it does not give an error but comes to the same screen again. where am I doing wrong. Can you tell me exactly how to do it one by one.

@gokhanc5
As I can see your phone stucks in Fastboot ( AKA Bootloader ) mode: in Android device's boot-mode is set by ro.bootmode property - what can be normal, recovery or fastboot - which is set in Android's system file named build.prop.
Simply flashing some images as you did doesn't cause this property gets reset.
Typically you reset device's boot-mode property by means of ADB and/or Fastboot commands
ADB
Code:
adb devices
adb reboot
Fastboot
Code:
fastboot devices
fastboot reboot

jwoegerbauer said:
[USER = 11583799] @ gokhanc5 [/ USER]
Telefonunuzun Fastboot (AKA Bootloader) modunda takıldığını görebildiğim gibi: Android cihazının önyükleme modu, Android'in build.prop adlı sistem dosyasında ayarlanan ro.bootmode özelliği tarafından ayarlanır - normal, kurtarma veya fastboot olabilir .
Yaptığınız gibi bazı görüntüleri basitçe yanıp sönmek, bu özelliğin sıfırlanmasına neden olmaz.
Genellikle aygıtın önyükleme modu özelliğini ADB ve / veya Fastboot komutları aracılığıyla sıfırlarsınız.
ADB
[kod]
adb cihazları
adb yeniden başlatma
[/ kod]
Fastboot
[kod]
fastboot cihazları
fastboot yeniden başlatma
[/ kod]
Click to expand...
Click to collapse
OEM lock is on.
I'm installing recovery.img in fastboot mode.
fastboot flash recovery recovery.img
then when I turn it off and on again it comes to the fast boot mode screen.
I tried all the recovery.img files.
but it didn't happen.
Fast Boot Mode screen
Start - restart booting failed
Power Of
Recovery Mode - restart booting failed
Restart bootloader - restart booting failed
Can you describe how to do it from the very beginning?

gokhanc5 said:
...
Can you describe how to do it from the very beginning?
Click to expand...
Click to collapse
Already told you what to do.

jwoegerbauer said:
Sana ne yapacağını zaten söyledim.
Click to expand...
Click to collapse
I cannot enter anywhere except fastboot.
I cannot install TWRP.
fastboot devices
fastboot reboot
I'm doing these things, nothing changes.
i'm a beginner
sorry

jwoegerbauer said:
Already told you what to do.
Click to expand...
Click to collapse
I tried what they said
usb debugging is turned off
What will I change in the build.prop file.
What should I do for ro.bootmode?
I will be glad if you answer
I tried a lot but couldn't find a solution.
my hope is you

You managed to softbrick your phone hence you also should be able to unbrick it.
But this requires some knowledge: Your posts here show me that you have no understanding how things are working, which action triggers which consequences, what tools are the right ones to be used.
Anyways:
Because phone is accessible in Fastboot mode - as you said - simply re-flash phone's stock ROM to get rid off of all mods you applied to phone. This basically can be achieved by means of Fastboot tool:
Code:
fastboot devices
fastboot flash bootloader <BOOTLOADER-IMG-FILE>
fastboot reboot bootloader
ping -n 5 127.0.0.1 > nul
fastboot -w <STOCK-ROM-ZIP-FILE>
fastboot reboot
Take note that this as 1st thing of all things requires to have installed on computer the Android USB Driver provided by HP matching your HP Slate 21 S100: Request it from HP if you can't find the driver at your own.
Another possibility would be to take the phone to autorized service center and let them fix it.

jwoegerbauer said:
You managed to softbrick your phone hence you also should be able to unbrick it.
But this requires some knowledge: Your posts here show me that you have no understanding how things are working, which action triggers which consequences, what tools are the right ones to be used.
Anyways:
Because phone is accessible in Fastboot mode - as you said - simply re-flash phone's stock ROM to get rid off of all mods you applied to phone. This basically can be achieved by means of Fastboot tool:
Code:
fastboot devices
fastboot flash bootloader <BOOTLOADER-IMG-FILE>
fastboot reboot bootloader
ping -n 5 127.0.0.1 > nul
fastboot -w <STOCK-ROM-ZIP-FILE>
fastboot reboot
Take note that this as 1st thing of all things requires to have installed on computer the Android USB Driver provided by HP matching your HP Slate 21 S100: Request it from HP if you can't find the driver at your own.
Another possibility would be to take the phone to autorized service center and let them fix it.
Click to expand...
Click to collapse
thank you for everything.
but I could not.
-------------------------
fastboot oem unlock
(bootloader) Bootloader is already unlocked.
OKAY [0.008s]
finished. total time: 0.008s
-----------------------------------------
fastboot devices
3CQ3400QG9 fastboot
-----------------------------------------
fastboot flash bootloader Bootloader_phobos_4.4.2.img
target reported max download size of 641728512 bytes
sending 'bootloader' (7137 KB) ...
OKAY [0.266s]
writing 'bootloader' ...
FAILED (remote: (InvalidState))
finished. total time: 0.422s
-------------------------------------------------- ------
thank you for your help

@gokhanc5
Code:
FAILED (remote: (InvalidState))
tells you the boot.img isn't accepted: use the boot.img file that comes with Stock ROM.

jwoegerbauer said:
@gokhanc5
Code:
FAILED (remote: (InvalidState))
tells you the boot.img isn't accepted: use the boot.img file that comes with Stock ROM.
Click to expand...
Click to collapse
gave the same error again.
I downloaded it from 3 different places, the same error in all of them.
fastboot flash bootloader command fails
fastboot flash boot command works but the problem is the same