Database Info

Help with wifi!!! I beg u guys!!!

myxoom wont boot and it stuck at the boot logo! help pls!

Walk back into the store, walk up to customer service and say "It won't turn on"
That's about your only solution when someone loads a 3g kernel.
You might be able to try to Power Off, power on Press and hole Volume up and power when you see the moto logo.

i tried but failed! sad thing is i m staying malaysia n i ordered it via online!!!
pls! help me!

pls! i m gonna cry

Can you get into fastboot? You might want to try reflashing your boot and system partitions. I believe it was BeagleBoy that grabbed them off of a stock Xoom Wi-Fi. You're already unlocked I imagine. Should let you flash those right back in and start fresh.

This guy got out of a semi-brick by doing something similar.
http://forum.xda-developers.com/showthread.php?t=973355

Scourge1024 said:
Can you get into fastboot? You might want to try reflashing your boot and system partitions. I believe it was BeagleBoy that grabbed them off of a stock Xoom Wi-Fi. You're already unlocked I imagine. Should let you flash those right back in and start fresh.
Click to expand...
Click to collapse
If you can get into fastboot, you should be fine. Don't panic just yet.
Try reflashing the stock boot.img and system.img files through fastboot. I did it a few days ago http://forum.xda-developers.com/showpost.php?p=12832155&postcount=33
You can find boot.img and system.img for stock wifi xoom on the OP of that thread.
Failing that try the semi bricked solution.
I hope you solve your problem.

how do i enter fastboot?
sad is, now my machine stucks in boot screen (moto logo) .. n my com have no respond with it at all. any suggestion pls

omnia1994 said:
how do i enter fastboot?
sad is, now my machine stucks in boot screen (moto logo) .. n my com have no respond with it at all. any suggestion pls
Click to expand...
Click to collapse
Power off the device.
Then hold Volume Down and hold Power on at the same time.

it shows "Starting Fastboot protocol support" and stopped there. what this mean? =(

that means you should be able to get it running again.
follow the first message in this thread:
http://forum.xda-developers.com/showthread.php?t=1010568
probably from the stuck at 'dual core technology' bit...
but I think this is what you should follow:
adb reboot bootloader
fastboot flash boot boot.img
fastboot reboot
adb remount
adb push bcm4329.ko /system/lib/modules/bcm4329.ko
adb push tun.ko /system/lib/modules/tun.ko
adb push scsi_wait_scan.ko /system/lib/modules/scsi_wait_scan.ko
adb push cifs.ko /system/lib/modules/cifs.ko
adb push vold.fstab /system/etc/vold.fstab
adb reboot
you might also want to pick up the stock wifi images:
http://forum.xda-developers.com/showthread.php?t=1017398
and flash them using:
fastboot flash system system.img
fastboot flash recovery recovery.img
(you've already flashed boot.img above).

omnia1994 said:
it shows "Starting Fastboot protocol support" and stopped there. what this mean? =(
Click to expand...
Click to collapse
If you're lucky, your computer will connect and typing in "fastboot devices" will show an entry for your Xoom. You do not need to start with ADB if you're already in fastboot mode.
From there, flash the boot.img for the proper Xoom version you have. You may also want to flash the system.img as well.
From there, simply try to reboot using "fastboot reboot". Make sure your Xoom starts up. If it does, you're pretty much good to go. I'd root from there manually.

omnia1994 said:
it shows "Starting Fastboot protocol support" and stopped there. what this mean? =(
Click to expand...
Click to collapse
That means you are in fastboot.
You can now try to follow this http:// http://forum.xda-developers.com/showthread.php?t=1010568 skipping the unlock section. Or as scourge recommended, fastboot flash the stock .img files. You can find them here http://forum.xda-developers.com/showthread.php?t=1017398 and the instructions around post #26 in that thread.

but my com cant sense my device =(
n it stucks at boot screen with the words "Starting fastboot protocol support" but just stuck there, this works?

qubit76 said:
That means you are in fastboot.
You can now try to follow this http:// http://forum.xda-developers.com/showthread.php?t=1010568 skipping the unlock section. Or as scourge recommended, fastboot flash the stock .img files. You can find them here http://forum.xda-developers.com/showthread.php?t=1017398 and the instructions around post #26 in that thread.
Click to expand...
Click to collapse
That's not necessarily true. My PC can no longer detect my Xoom in any way whether or not it says "Starting Fastboot protocol support" or "Starting RSD mode 2". I can't get it to say anything else.
I used to be able to get into fastboot. That's how I bricked my Xoom... By trying to oem lock it with what I was hoping to be clean boot, system and recovery image files for the wifi.
Now, I can't even get back in to oem unlock or flash. RSD lite doesn't pick it up in RSD mode 2, but does pick up my old RAZR phone.

omnia1994 said:
but my com cant sense my device =(
n it stucks at boot screen with the words "Starting fastboot protocol support" but just stuck there, this works?
Click to expand...
Click to collapse
What sort of computer do you have? Can you copy and paste what you see when you type "fastboot devices"?
Copy and paste from your command prompt (or Linux terminal) and let's see what you've got.

ok. will report once tried. thx very much =)

Okay. If you can get into fastboot (check by "fastboot devices"), all you should need to do are these two commands if you're connected:
Code:
fastboot flash boot boot.img
fastboot flash boot system.img
fastboot reboot
That should get you close to stock first.

wth, i cant install the android SDK, it said it needs java to be installed. i ve installed that but still cant install the android sdk. =(

omnia1994 said:
wth, i cant install the android SDK, it said it needs java to be installed. i ve installed that but still cant install the android sdk. =(
Click to expand...
Click to collapse
Where error messages are you getting? Are you running 64bit?

[Q] Stuck on Google logo. Unable to push image file to phone... Please help.

Tried various possible solutions and still can't get past the Google logo. Installed adb and Samsung driver but when executing commands such as "abd remount" or "adb push file.zip \sdcard\" in cmd I get an error saying "device not found".
Does anyone know how I could resolve this issue?
I tried clearing the cache and wiping the data from the phone, and even heating the phone with a hair dryer. I'd very much appreciate any help.

looks like you still be able to get in reovery ? if so , then nothing you should worry , just flash a new ROM

Do you mean like a boot image or a recovery image?
If so then you need to put phone in fastboot mode, hold volume up and power til it comes up on screen, then on command prompt on your computer type in fastboot flash recovery xxxxxxx.img (xxxxx is the name of the file like cwm5.0.2.0.img or whatever)
That should give you a working recovery to flash roms from.
Is your boot loader unlocked?
If you wanna mount then just go to mounts and storage and mount USB storage and it will show up on your computer!

nodstuff said:
Do you mean like a boot image or a recovery image?
If so then you need to put phone in fastboot mode, hold volume up and power til it comes up on screen, then on command prompt on your computer type in fastboot flash recovery xxxxxxx.img (xxxxx is the name of the file like cwm5.0.2.0.img or whatever)
That should give you a working recovery to flash roms from.
Is your boot loader unlocked?
If you wanna mount then just go to mounts and storage and mount USB storage and it will show up on your computer!
Click to expand...
Click to collapse
Thanks for your reply, seems to be hanging on waiting for device. Fastboot appears to be locked and it just hangs on "waiting for device" when I enter the command fastboot oem unlock... Not sure where to go from here.

leeroy88 said:
Thanks for your reply, seems to be hanging on waiting for device. Fastboot appears to be locked and it just hangs on "waiting for device" when I enter the command fastboot oem unlock... Not sure where to go from here.
Click to expand...
Click to collapse
It was a recovery image file by the way. Tried fastboot flash recovery xxxxx.img like you had said but same problem...

leeroy88 said:
It was a recovery image file by the way. Tried fastboot flash recovery xxxxx.img like you had said but same problem...
Click to expand...
Click to collapse
Hmmm try going to cmd prompt and typing in adb devices, if you get nothing then your adb isn't set up properly and you need to go into setting and change the path on your computer.
I know the details are sketchy but gimme a min and I will find you a link
---------- Post added at 03:05 AM ---------- Previous post was at 03:00 AM ----------
http://forum.xda-developers.com/showthread.php?t=1161776
Find the Android sdk folder in your computer, move it to the root of C.
I don't think adb is where this guide says it is, there is a read me in the folder where it was saying it has moved to the platform tools folder.
So anyway find the path to the file and put it where the guide says and you should be on the ball.

Forget adb. You need to use fastboot.
Open a command prompt in the directory with fastboot or cd into it.
Put phone in fastboot mode.
On the command prompt type fastboot devices.
You will see your serial number. If you don't recheck and make sure you did everything. Sdk PDA drivers if need be etc.
Fastboot flash recovery custom recovery img name.img
Boot into recovery
Mounts and storage.
Mount SD card
Put a rom for you device on there.
Unmount
Wipe everything but sdcard from recovery.
Flash the rom by going to install zip from SD card......

Okay still stuck trying to connect to my phone. I haven't been able to get my serial number show when typing fastboot devices in cmd. adb is set up and seems to be working but the list of devices is blank when I type in adb devices. The phone was put into fastboot mode both times. I get <waiting for device> when I try
fastboot flash recovery clockwork-5.0.2-crespo.img
I think the bootloader may be locked as it does say LOCKED under lock state, which is probably the reason why I can't get the recovery image to work. I couldn't install PDANet as it wanted to connect to my phone while in debugging mode at the end of the installation. Would it be possible that fastboot oem unlock won't work with without having PDANet installed? I'd really appreciate any further help on this topic.

You need the drivers.

albundy2010 said:
You need the drivers.
Click to expand...
Click to collapse
I have the Google USB driver package installed from SDK Manager. I had tried to install some other Samsung driver found on another post but it wouldn't install.

Turns out drivers weren't fully installed, managed to get PDANet installed and could connect to the phone with fastboot devices. Serial number was displayed in cmd. Only problems lies with unlocking the bootloader. fastboot oem unlock fails giving an error: too many links. Anyone have a solution to this?

leeroy88 said:
Turns out drivers weren't fully installed, managed to get PDANet installed and could connect to the phone with fastboot devices. Serial number was displayed in cmd. Only problems lies with unlocking the bootloader. fastboot oem unlock fails giving an error: too many links. Anyone have a solution to this?
Click to expand...
Click to collapse
Did you try booting into bootloader in the first place? Volume up+Power
Then you can use fastboot. Forget PDAnet. Just install SDK and ADB
Use this:
http://forum.xda-developers.com/showthread.php?t=1007782

ismailham said:
Did you try booting into bootloader in the first place? Volume up+Power
Then you can use fastboot. Forget PDAnet. Just install SDK and ADB
Use this:
http://forum.xda-developers.com/showthread.php?t=1007782
Click to expand...
Click to collapse
Yeah I was in bootloader at the time, but I noticed that the Lock-State said locked. So I figured I must first use fastboot oem unlock. If I was to try flash with a stock recovery image would I still need to unlock the bootloader? Like I said I was able to use fastboot devices and get my phones serial number to show up, so I think SDK and ADB is properly installed, path set correctly etc.

leeroy88 said:
Yeah I was in bootloader at the time, but I noticed that the Lock-State said locked. So I figured I must first use fastboot oem unlock. If I was to try flash with a stock recovery image would I still need to unlock the bootloader? Like I said I was able to use fastboot devices and get my phones serial number to show up, so I think SDK and ADB is properly installed, path set correctly etc.
Click to expand...
Click to collapse
I don't think you need to unlock the boot loader to flash a recovery image.
I may be wrong but I remember someone saying that once. I had mine unlocked before I had the chance to try it out. What happens when you type in fastboot oem unlock?

nodstuff said:
I don't think you need to unlock the boot loader to flash a recovery image.
I may be wrong but I remember someone saying that once. I had mine unlocked before I had the chance to try it out. What happens when you type in fastboot oem unlock?
Click to expand...
Click to collapse
After typing fastboot oem unlock I get three dots ...
Pretty much straight away it fails and says something about "too many links".

Did you do all the steps from here http://nexusshacks.com/nexus-s-root/how-to-root-nexus-s-or-nexus-s-4g-on-ics-or-gingerbread/ ?

kvaju said:
Did you do all the steps from here http://nexusshacks.com/nexus-s-root/how-to-root-nexus-s-or-nexus-s-4g-on-ics-or-gingerbread/ ?
Click to expand...
Click to collapse
Thanks for your reply, I followed the steps just now and got the exact same error. Before I was trying fastboot oem unlock while in platform-tools but this time I had downloaded the nexussrootICS.zip file, and extracted it to the root of C. I tried fastboot devices and my serial shows up and after fastboot oem unlock I get "status read failed: too many links."
The only difference I seem to have is that in my device manager I have Android Device > ADB Interface, as opposed to SAMSUNG Android Device > ADB Interface.
Not a big difference but that's all I can think of.

the same issue for me. is there any working solution for that?

I recently had success in recovering from this issue.
Here is the link, read the last comment
http://forum.xda-developers.com/showthread.php?t=1894147

GnubbyaBush said:
I recently had success in recovering from this issue.
Here is the link, read the last comment
http://forum.xda-developers.com/showthread.php?t=1894147
Click to expand...
Click to collapse
Thanks! I'll try to do this fancy dancing

[Q] LG P500 stuck in fastboot - "waiting for device"

Hello.
Earlier today I wanted to try a new JB rom to replace ICS so I transfered it into SD card and tried to reboot into recovery.
Instead of getting to recovery, I got stuck in fastboot mode, so I'm assuming recovery has been damaged.
After a whole afternoon of researching this forum I tried for several times this tutorial in order to install a recovery and afterwards a ROM (http://forum.xda-developers.com/showthread.php?t=1088046) and similar ones in both Mac OS X and Windows 7 (tried both USB 2.0 and USB 3.0 so its not a problem from USB) and I didn't succeed at all.
When I am using Windows 7, when I use "fastboot erase recovery", I keep receiving this message "waiting device". If I write "fastboot devices", I don't get results.
When using Mac OS X, I can get via command line to the folder "platform-tools" where fastboot is located but if I write "fastboot erase recovery" or something, it says "command not found". I've read it could be because I have to set fastboot as an environmental variable, but I having trouble setting it (Mac OS Lion).
Thank you so much for reading. Please help me!!! Any clues would be really appreciated!
-----
UPDATE: I finally managed to communicate with the device.
I used the following commands from this tutorial http://androidforums.com/optimus-m-all-things-root/382525-guide-get-out-fastboot-mode-2.html
fastboot erase boot
fastboot erase recovery
fastboot erase system
fastboot flash recovery
The problem is, now I'm stuck at LG Logo, can't access fastboot... Please help, I think it's even worse now.

boot rom, pull out battery and boot normal, it does or not? if it does use terminal emulator or adb push to install custom recovery, adb will work in fastboot if you had checked android debugging
http://forum.xda-developers.com/showthread.php?t=1007244
http://forum.xda-developers.com/showthread.php?t=1146566

grigtm said:
boot rom, pull out battery and boot normal, it does or not? if it does use terminal emulator or adb push to install custom recovery, adb will work in fastboot if you had checked android debugging
http://forum.xda-developers.com/showthread.php?t=1007244
http://forum.xda-developers.com/showthread.php?t=1146566
Click to expand...
Click to collapse
I don't understand what you mean by boot rom. Every time I turn on the phone, (normal or as POWER+HOME+VOL DOWN) it goes into fastboot. When I pull out the battery, and power again it goes again into fastboot...

techdani said:
I don't understand what you mean by boot rom. Every time I turn on the phone, (normal or as POWER+HOME+VOL DOWN) it goes into fastboot. When I pull out the battery, and power again it goes again into fastboot...
Click to expand...
Click to collapse
ok, read here http://forum.xda-developers.com/showthread.php?t=1088046 do exactly what says in this thread

[Q] Moto G stuck on "Warning Bootloader unlocked" screen

After rootting my moto G around a month ago, the KitKat update has came out, I tried to update on my phone and there was an error, then I tried updating it from the PC, again another error. Then when I would turn my phone on it would turn off after around 1 minute after turning on, So I found a thread to install the update manually, then I had errors flashing partitions as said in the steps on this other website. I uplugged the phone as I kept getting errors, now when I try to turn it on it just gets stuck on "WARNING BOOTLOADER UNLOCKED" screen. Even when I hold down the power button to turn it off, it just turns the screen black, vibrates, turns back on with the warning screen. I cannot enter fastboot with holding down power and the volume key. I am stuck here any tips or anyone know what is going on/ causing the error?

Did u got the phone completlely off? If not - try it and try to Boot in fastboot then.
Sent from my Moto G using xda app-developers app

pspuser97 said:
Did u got the phone completlely off? If not - try it and try to Boot in fastboot then.
Sent from my Moto G using xda app-developers app
Click to expand...
Click to collapse
I have managed to get it into fastboot just now by holding down the power and both volume buttons.But I still can't seem to get it working.

Luke1275 said:
After rootting my moto G around a month ago, the KitKat update has came out, I tried to update on my phone and there was an error, then I tried updating it from the PC, again another error. Then when I would turn my phone on it would turn off after around 1 minute after turning on, So I found a thread to install the update manually, then I had errors flashing partitions as said in the steps on this other website. I uplugged the phone as I kept getting errors, now when I try to turn it on it just gets stuck on "WARNING BOOTLOADER UNLOCKED" screen. Even when I hold down the power button to turn it off, it just turns the screen black, vibrates, turns back on with the warning screen. I cannot enter fastboot with holding down power and the volume key. I am stuck here any tips or anyone know what is going on/ causing the error?
Click to expand...
Click to collapse
what model???
yiu have the usb drivers intalled??

alonsoch said:
what model???
yiu have the usb drivers intalled??
Click to expand...
Click to collapse
Its the vodafone UK moto G, yes I have the drivers installed.

fastboot oem fb_mode_clear
Try fastboot oem fb_mode_clear

i have same problem
I am also having same problem. did anyone found solution for this?

There can be many reasons for this: broken ROM, incorrect kernel etc. Unless you know specifically the last thing you changed; you are better off doing a factory reset and installing a new ROM in Recovery or flashing a firmware image via fastboot.

I am having this exact same issue. the phone is stuck on the unlocked bootloader screen. It is still responsive, I can get into the fastboot and even clockwork recovery mod but nothing i do will escapt the bootloop. I even tried a factory reset in Fastboot and Clockwork and the RSD lite method but it didnt work.

Go to the 'Restore Stock Firmware' thread and re-flash your firmware again. I've had bootloops before.
Sent from my Moto G on MoKee, using XDA app.

mej0248 said:
Go to the 'Restore Stock Firmware' thread and re-flash your firmware again. I've had bootloops before.
Sent from my Moto G on MoKee, using XDA app.
Click to expand...
Click to collapse
I did, I tried that method but when I get to step 3B I cannot get mboot or whatever to work. First it throws an error and asks for an obscure Adb.dll that i hunted down and put in its folder but then i click it to open and it flashes up for a second then closes. Excuse me while I go cry in a corner for a bit. :crying:

Deadboy90 said:
I did, I tried that method but when I get to step 3B I cannot get mboot or whatever to work. First it throws an error and asks for an obscure Adb.dll that i hunted down and put in its folder but then i click it to open and it flashes up for a second then closes. Excuse me while I go cry in a corner for a bit. :crying:
Click to expand...
Click to collapse
Bootloader screen is a boot animation http://forum.xda-developers.com/moto-g/general/guide-how-to-stuck-boot-animation-t2794208
And for restore stock firmware try inputting these commands manually
Code:
fastboot getvar max-sparse-size
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash motoboot motoboot.img
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
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 erase cache
fastboot erase userdata
fastboot oem fb_mode_clear
If all else fails check out my guide : http://forum.xda-developers.com/moto-g/general/unbrick-method-t2794271

NEED URGENT HELP
I accidentally wiped the internal storage of my Moto G XT1033 (dual sim variant), since the OS is lost now my phone is stuck at bootloader warning. I can access TWRP recovery. In device manager I can see Google Nexus ADB Interface. And in taskbar (safely remove hardware and eject media) phone is recognized as Eject XT1032. But in file explorer/My computer I can't see the phone. My phone drivers are installed.
I've tried adb shell command and I am getting this error:
C:\Minimal ADB and Fastboot>adb shell
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
error: device not found
and with adb devices command following error:
C:\Minimal ADB and Fastboot>adb devices
List of devices attached
(this line/area is blank)
C:\Minimal ADB and Fastboot>
Now how can I fix ADB or this problem? Please help

Juste300 said:
NEED URGENT HELP
I accidentally wiped the internal storage of my Moto G XT1033 (dual sim variant), since the OS is lost now my phone is stuck at bootloader warning. I can access TWRP recovery. In device manager I can see Google Nexus ADB Interface. And in taskbar (safely remove hardware and eject media) phone is recognized as Eject XT1032. But in file explorer/My computer I can't see the phone. My phone drivers are installed.
I've tried adb shell command and I am getting this error:
C:\Minimal ADB and Fastboot>adb shell
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
error: device not found
and with adb devices command following error:
C:\Minimal ADB and Fastboot>adb devices
List of devices attached
(this line/area is blank)
C:\Minimal ADB and Fastboot>
Now how can I fix ADB or this problem? Please help
Click to expand...
Click to collapse
If you have access to TWRP, then are you able to go into the Advanced menu and use the ADB Sideload feature to flash over a ROM from your PC? I had a problem while working with my phone the other day during its initial unlocking and flashing where I'd broken the system install but still had access to TWRP, and by swiping and enabling ADB Sideload, I was able to flash in a new ROM with my phone connected to my computer by running: adb sideload /path/to/rom.zip
Alternatively, you may be able to use the stock firmware restoration procedure detailed elsewhere in this forum to restore your stock firmware via fastboot.
Pardon me if I haven't fully grasped your issue. Hope this helps!

a_gert said:
If you have access to TWRP, then are you able to go into the Advanced menu and use the ADB Sideload feature to flash over a ROM from your PC? I had a problem while working with my phone the other day during its initial unlocking and flashing where I'd broken the system install but still had access to TWRP, and by swiping and enabling ADB Sideload, I was able to flash in a new ROM with my phone connected to my computer by running: adb sideload /path/to/rom.zip
Alternatively, you may be able to use the stock firmware restoration procedure detailed elsewhere in this forum to restore your stock firmware via fastboot.
Pardon me if I haven't fully grasped your issue. Hope this helps!
Click to expand...
Click to collapse
Thanks for the help. I tried ADB Sideload feature in twrp as well the adb sideload /path/to/rom.zip this command/feature was not working from the pc.
Anyways, I tried USB OTG method, copied CM nightly into my flash-drive then attached flash-drive + OTG cable with phone, at first OTG was not working don't know why it could not mount, I restarted phone, went into recovery and then I could installed rom from flashdrive. Finally my phone is working now
I am totally new to android and this rom rooting stuff. Moto G is my first android smartphone coming directly from iPhone 5 so I was scared like hell
If anyone failed with ADB Sideload method please try USB OTG method and your phone will work again. Hope this help others

same issue
Juste300 said:
Thanks for the help. I tried ADB Sideload feature in twrp as well the adb sideload /path/to/rom.zip this command/feature was not working from the pc.
Anyways, I tried USB OTG method, copied CM nightly into my flash-drive then attached flash-drive + OTG cable with phone, at first OTG was not working don't know why it could not mount, I restarted phone, went into recovery and then I could installed rom from flashdrive. Finally my phone is working now
I am totally new to android and this rom rooting stuff. Moto G is my first android smartphone coming directly from iPhone 5 so I was scared like hell
If anyone failed with ADB Sideload method please try USB OTG method and your phone will work again. Hope this help others
Click to expand...
Click to collapse
same issue but i dont know how to flash rom though pendrive i didnt find the files that i were in my pendrive in twrp menu
:crying:

shivamtyagi said:
same issue but i dont know how to flash rom though pendrive i didnt find the files that i were in my pendrive in twrp menu
:crying:
Click to expand...
Click to collapse
You first have to select the usb storage in TWRP because TWRP detected internal storage. U can even mount usb otg from TWRP options. after selecting usb then u can see the files in ur usb drive.

I'm stuck on the same Warning screen, it is not a bootloop since the phone just seems to freeze but after a minute I get the windows sound as if you conected something via USB, but the warning screen stays, I've let it for hours and I've flashed stock roms. Even when you flash a no warning boot logo.bin the screen shows again even when mfastboot shows as succesful flash. Out of ideas now, please help
Code:
Model XT1068

Thanks
Thanks

Solution for MotoG locked in bootloader,
I think you must have tried to install another kernel version or so. If you have installed cyanogen try resinsallting the lasted update by going into custom recovery and flashing the latest update in the cmupdater file. Worked for me ! Lets hope that it works for you too. All the best !

LG GPAD 7 stuck on Fast Boot

Purchased an Lg Gpad 7 Wifi tablet (v400) 2 weeks ago. Came with preinstalled Lollipop android so i couldnt install a recovery rom to flash any other custom roms. Downgraded to Kitkat version following the instructions on Xda forums and succesfully installed Twrp. When i installed Cyanogenmod 12.1 through Twrp i got stuck in fastboot screen.
Any suggestions and / or solutions would be greatly appreciated.

I had a similar problem.. Only mine was stuck at the bootloader. Go in TWRP and repair /data and other partitions. My data partition gave me an error since F2FS is a little flaky and some ROMs corrupted it (claimed they supported it). I would recommend erasing the system, cache and data partition if you can't get into TWRP.

The problem is i cant get out of fastboot whatever i try. It says start on bootloader but the tablet just restarts on an empty screen doing nothing.

Hakalai said:
The problem is i cant get out of fastboot whatever i try. It says start on bootloader but the tablet just restarts on an empty screen doing nothing.
Click to expand...
Click to collapse
if you have an sd card, try removing that, then reboot.
if that doesnt work, try entering fastboot command, fastboot continue

Tried without sdcard and i get the same fastboot screen.
How can i give any commands? The only options i have are Restart Bootloader / Restart / Power off. Tried restarting bootloader but i get nothing in return tablet just stays on with nothing on screen.

Hakalai said:
Tried without sdcard and i get the same fastboot screen.
How can i give any commands? The only options i have are Restart Bootloader / Restart / Power off. Tried restarting bootloader but i get nothing in return tablet just stays on with nothing on screen.
Click to expand...
Click to collapse
you said it was stuck on fastboot, if thats the case, install any needed drivers on your pc, connect device to it, open a terminal in the fastboot dir (after you go get fastboot), then try those commands i gave. you could also try, fastboot reboot dont think i mentioned that before.

bweN diorD said:
you said it was stuck on fastboot, if thats the case, install any needed drivers on your pc, connect device to it, open a terminal in the fastboot dir (after you go get fastboot), then try those commands i gave. you could also try, fastboot reboot dont think i mentioned that before.
Click to expand...
Click to collapse
Did as you said but every command i gave gives me an error message in adb terminal. There are new lines in fastboot menu in tablet now. Bottom two are SECURE BOOT - enabled & LOCK STATE - locked.

Hakalai said:
Did as you said but every command i gave gives me an error message in adb terminal. There are new lines in fastboot menu in tablet now. Bottom two are SECURE BOOT - enabled & LOCK STATE - locked.
Click to expand...
Click to collapse
hmm, ok, im guessing it would have said that normally, when not broken. all the command does is try to release it past where its stuck. it doesnt actually flash, lock, unlock, or change anything.
imo, this seems good, because now we know fastboot is working.
i own lg devices, but not your specific device. i would hate to give you some bad advice and make your tablet broken more, but if it were me in this situation, i would try to flash the factory KK firmware you used to downgrade with odin or however you did it. hopefully, that will clean everything up and let it boot properly.
if for whatever reason you cant do that, we could try extracting the factory file, and just flashing recovery and system, those should be the only things that got changed putting on twrp and cm normally.

Sorry, I have the serious proplem wtih my LG pad V400, I rooted it and using <LG Flash Tool 2014> with <V40010c_00.kdz> to downgrate the firmware but their is error then my LG pad stuck in fastboot menu as with just turn off, restart and restart bootloader. if i seclect one one them the tablet just logged again the fastboot menu
it stuck on the fastboot menu and i cannot do nay think with it. I can restart with factory restore mode but when select yes to restore, it will restart and log in fastboot menu again.
I downloaded adb and fastboot program and put in one folder <Minimal ADB and Fastboot> in C:\Program Files (x86)\Minimal ADB and Fastboot
I dont have recovery image so i download file <cm-13.0-20160421-NIGHTLY-v400-recovery.img> form your link to download TWRP file
move it to folder of fastboot programe and changed its name to <recovery.img>
I turn on the tablet and it waited at fastboot menu
when i run the command <fasboot flash recovery recovery.img> and they said some thing wrong like in picture
please help me