Database Users

Attempting to repartition SD card = Device not found in recovery

Hello,
I just got my Hero this weekend and I was interested in partitioning the SD Card. I have been following a guide and when I boot into recovery(Screen that shows phone with triangle and exclamation point) the computer does not seem to see the Hero anymore.
When I plug the phone in while it is running Android the computer picks it up fine in Device manager. Once I type adb shell reboot recovery it boots into the screen the computer no longer picks it up. I have tried unplugging and replugging the USB cable while in the recovery screen but still get nothing. If I type adb devices before I run the recovery command I am able to get the serial number, once it boots into the recovery screen it no longer shows me the serial number when I type in adb devices. But this is due to it no longer being picked up once in the recovery screen.
I'm not really sure what I am doing wrong here. Can anyone help me get this issue sorted out?
I have tried it on Windows 7 and read that a lot of people had issues with the syncing so I just finished attempting it on an Windows XP machine and still get the same issue.
One more thing, when in the recovery screen the phone does not respond to the power button anymore. It seems almost like it locks up or something. The only way I can get back out of the screen is by taking the battery out and putting it back in. Is this normal?
Any help would be really appreciated!
Thank you,
Mizex

You need to root the phone and install the recovery partition first.

Mizex said:
when I boot into recovery(Screen that shows phone with triangle and exclamation point)
Click to expand...
Click to collapse
jonnythan said:
You need to root the phone and install the recovery partition first.
Click to expand...
Click to collapse
Exactly what jonnythan said. If your recovery screen shows the triangle then you haven't installed a modified recovery image yet. Follow any of the guides on this site for rooting.

Oh wow I feel dumb the guide I was following said nothing about the phone needing to be rooted. I attempted to follow a 1 click root and while attempting to do the backup step I get a message saying that it can't complete the command. According to the guide if I get this error then it means I have a patched firmware and need to downgrade to a cupcake firmware.
Anyone know of a good guide for doing the downgrade? Or can perhaps share a bit of knowledge on the error?

[solved][Q] no boot, no adb, no sbf_flash, no access, no nothing

I tried to flash my MS2, but now I have no boot and no access to the phone.
Story:
- root via paxChristos' Linux Port of DooMLoRD's Easy Rooting Toolkit
- backup via Titanium Backup
- backup via Bootstrap
- installed CyanogenMod and the nightly build cm_droid2_full-139.zip
- realized ... it is the wrong Mod, because for Druid2 and I have a Milestone2 = not the same
- sudo ./sbf_flash MILS2_U6_2.2.16_SIGNED_UCAMILESTONE2B1B80E100A.0R_USXMILE20RTDACH_P016_A005_HWp2a_Service1FF.sbf
And now, I have a dead phone ... even could not start it. It is just a black screen and nothing more!
The only thing that show "life" is the LED on the side of the USB-Cable plug!
I also tried Vol-Up/Dwon + Camera, Arrow-Up + Power On, x + Power On ... with and without USB-Cable!
Is there a way to flash the phone anyway?
Would be nice to have a little help!

A little more info:
Plug in USB cable and lsusb:
Bus 002 Device 013: ID 22b8:4280 Motorola PCS
Long press on the power button and lsusb:
no Motorola
Keep USB cabel in the phone, unplug the batterie and plug in back ... lsusb:
Bus 002 Device 015: ID 22b8:4280 Motorola PCS
And more info:
udev-rule1 (worked to flash the phone)
SUBSYSTEMS=="usb", ATTRS{idVendor}=="22b8", ATTRS{idProduct}=="41db", MODE="0666", OWNER="sasch" #Normal, Debug & Recovery droid
udev-rule2 (tried after reboot of phone showed lsusb shown before)
SUBSYSTEMS=="usb", ATTRS{idVendor}=="22b8", ATTRS{idProduct}=="4280", MODE="0666", OWNER="sasch" #Normal, Debug & Recovery droid
Also ... not worked:
SUBSYSTEMS=="usb", ATTRS{idVendor}=="22b8", MODE="0666", OWNER="sasch" #Normal, Debug & Recovery droid
$ ./adb kill-server
$ ./adb start-server
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
$ ./adb shell
error: device not found

Your only chance is SBF right now. Hold camera, vol down and power together, which can brings up bootloader mode and then flash it via RSDLite, because sbf_flash did not worked for me.

I made the same mistake myself back in the day .
I could get into bootloader no worries though... are you sure you didn't drain the battery or something?
Just seems pretty odd that you could remove an impossible to unlock, locked bootloader

First of all ... thanks for helping me!
Anonymous_ said:
Your only chance is SBF right now. Hold camera, vol down and power together, which can brings up bootloader mode and then flash it via RSDLite, because sbf_flash did not worked for me.
Click to expand...
Click to collapse
Nothing happend ... screen is black, LEDs are off!
DreadPirateDan said:
I made the same mistake myself back in the day .
I could get into bootloader no worries though... are you sure you didn't drain the battery or something?
Just seems pretty odd that you could remove an impossible to unlock, locked bootloader
Click to expand...
Click to collapse
Battery should be ok, it also don't work with Charger on!
If it is impossible to remove the locked bootloader, why can I still not boot?!

If the device bricked only a black screen shows up. This is bootloader mode. RSDLite will recognise your phone and flash an SBF.
Sent from my MotoA953 using XDA App

Damn ... just bought a used one on eBay and now I have my old one fixed! *lol*
Thanks to you all ..
I used my laptop with Windows7 and RDS light from Chip Online
Then I used the SBF Version 2.3.4!
reboot ...DONE ... Milestone2 worked again!
But ...
root via zergRush_automated_Linux_root
Installed bootstrap-1.0.0.5-droid2.apk from SD-Card because:
$ sudo ./adb push bootstrap-1.0.0.5-droid2.apk /system/app/
failed to copy 'bootstrap-1.0.0.5-droid2.apk' to '/system/app//bootstrap-1.0.0.5-droid2.apk': Read-only file system
reboot
wipe data/factory reset
wipe cache partition
installzip from sdcard (cm7-111129-2153-NIGHTLY-Milestone2.zip)
reboot ... black screen again!
Maybe the bootstrap installation is the problem?!

I think the message is very clear. The bootstrapper never installed to begin with. Second of all, why are installing the bootstrapper like that? Instead of copying it to your SD-Card and execute it from the file browser on your phone. It will be installed, after which you should execute it. It will ask for root access when you press the bootstrap button. You give it and then you press the button Reboot Recovery. Then you'll be in CWM. You can't install CM7 from Motorola's recovery, which is what you've been doing all the time.
Further: Endless7 has written a guide here: http://forum.xda-developers.com/showthread.php?t=1310641
I'd suggest you follow it, and if you don't understand something ask it.

HAPPY NEW YEAR!!!
Okay, actual I have my MS2 with the original sbf and I wait until my second MS2 is here.
Then I try to install CM!
Never the less I have questions, just to be sure.
When I install the droid2bootstrap, I just copy the file to the sdcard and then install it at the phone?! Is this correct?
Then the HowTo says: 3.open droid2bootstrap and select install recovery
But there is nothing like "install recovery" to select. There is just a screen with two buttons (Bootstrap Recovery and Reboot Recovery) ... I think "Bootstrap Recovery" first, then reboot?
If I do the steps above, I have an bootloader installed on my phone?! Which I can start with the volume buttons at bootup?
Wow, I have to learn a lot about Android phones! I read the wiki, but asking questions will help me more!
Thanks to you all!

What you described is correct except the startup with volume buttons.
You have to use the Reboot Recovery button to get in CWM, where you can flash CM7.
And just for the record: every phone has a bootloader installed, otherwise it wouldn't be able to boot an OS. Fact is that you can't replace it on the Milestone 2.
Don't mix up Recovery and Bootloader. They're different things.

sasch42 said:
$ sudo ./adb push bootstrap-1.0.0.5-droid2.apk /system/app/
failed to copy 'bootstrap-1.0.0.5-droid2.apk' to '/system/app//bootstrap-1.0.0.5-droid2.apk': Read-only file system
reboot
wipe data/factory reset
wipe cache partition
installzip from sdcard (cm7-111129-2153-NIGHTLY-Milestone2.zip)
reboot ... black screen again!
Maybe the bootstrap installation is the problem?!
Click to expand...
Click to collapse
bootstrap is not copied to /system/app , adb said "failed to copy...".
maybe copy it do /data/app ?
You wiped data and cache.. how about dalvik?

Because the copy failed, I installed the app from the sdcard (/data/app was also read only).
But as described here (http://forum.xda-developers.com/showthread.php?t=1310641) I used the wrong app!
IMHO it is the same to copy the app via adb or install it from sdcard?!

What the shizzle, you are making it so hard for yourself.
If you simply place the .apk file onto the root of you SD card, then using your phone, open the .apk, install it, then open the installed app, you will have no problems at all. I'm not sure of your motivation to try other methods when it allready works fine
Also, i would say that since it has apparently failed for you, no it isn't the same
EDIT: on a side note, it would seem you flashed the official gingerbread sbf, so now you will only be able to use the gingerbread kernel roms. Which is pretty much the cm9 alpha version, endless 7's cm7 defy port. Not really sure about the other gb rom (argen2stone, blurless etc). So make sure you read up on what you need and what will work

DreadPirateDan said:
...
If you simply place the .apk file onto the root of you SD card, then using your phone, open the .apk, install it, then open the installed app, you will have no problems at all. I'm not sure of your motivation to try other methods when it allready works fine
Also, i would say that since it has apparently failed for you, no it isn't the same
...
Click to expand...
Click to collapse
Have you read all the posts?
My mistake was ti follow this guide.
And my way to install the app was, to copy it tio the sdcard because the method in the guid didn't work!

Milestone 2 Bricked
Hello friend, i am having the same problem then you...
It only show black screen and the led on the side of the usb cable and i also tried Vol-Up/Dwon + Camera, Arrow-Up + Power On, x + Power On ... with and without USB-Cable, as you and nothing...
Can you help me? please!

Do you have RSDLite? If yes, then RSDLite should detect your phone as it is already in bootloader mode (the black screen). You can flash an SBF at this point.
Download an appropriate one, if you were on Froyo then Froyo and in case you had upgraded to Gingerbread then download a GB SBF.
Flash the SBF. You would probably end up in a bootloop. Go to moto recovery, wipe data and boot. You should be good to go.
Edit: I believe that only GB sbf is gonna work for you as I suspect that you were somehow on GB and then tried to flash Froyo which led you to the black screen.

[q] problems with lg gt540

hi guys.. could you help me with my problem.!
I have an LG GT540 android 1.6 firmware version(stock)
So here are my problems:
1. I tried to upgrade it from 1.6 to 2.1 using this tutorial http://forum.xda-developers.com/show...27&postcount=3 thanks to lavero.burgos for posting it, I was successful at first part, but I cant follow the next because my device wont go to fast boot,, I tried putting it off, then camera+poweron but it doesnt do anything. It doesn't light, no lg logo appears, just nothing although the computer can read the drive when I connect it through usb. So I cannot flash it to 2.3,2.3 because it just wont go to fastboot.
2. When I turn it on normally, It takes long before it response like after 30sec to light, but just light, no lg logo appears although it wasnt bricked because I can use it normally after just waiting to on.(annoying)
3. Since I upgraded it to 2.1, I lost all 3rd party application and the internal apps were the only left, so I copied all my saved apps (.apk) to my sd card but the problem is there is no saved app on my phone to read and install those apps from my sd card.(irritating)
4. My device wont read my sim card, when I start it it says "sim card unprovisioned" so basically I cant connect to mobile networks here in the philippines(im using globe telecom). I feel that Im stucked in the middle of nowhere since I cannot contact and txt all my family and friends.
5. I cant connect to wifi,, when my device detects wi-fi, I try to connect to it but from the log it only try to connect but doesn't obtain the ip address. Even when the wi-fi signal is strong, it does the same thing.
So please help me guys,,I want to hear from my fellow xda-developers badly,,,
PS. also those who have problems with their LG GT540 pls feel free to post and share it with us here... thank you all guys in advance....

hi so let me get it right the phone is working (can turn on and use but cant call) yes? hmmmmm..... try this
MUST DOWNLOAD THIS DRIVERS!!!!
http://dottech.org/android/26188/usb-adb-and-fastboot-drivers-for-windows-for-all-android-phones/
Step one!
1.turn off phone.
2.hold the POWER button till you feel the beep.
3.let go of the POWER button when you feel the beep and hold onto the CAMERA button only.
4.hopefully it turns on to a blackscreen and nothing else(fastboot)
5.unzip this CLICK ME!! to desktop and open the flash all no wipe file
or......
1.turn on your phone.
2.go to settings>applications>development>tick the usb debugging
3.connect phone to computer (make sure phone is on)
4.unzip this CLICK ME!! to desktop and open the flash all no wipe file
5. phone should boot into blackscreen like the one above......
Click to expand...
Click to collapse
Step 2!
both should flash a recovery image. Next
1.make sure the phone is off
2.press POWER button
3.when you feel the beep let go of POWER button and press the HOME button only.
4.phone should boot into recovery mode.
5.take out battery again
6. download a rom into the sdcard using computer
7.go to recovery again using the steps above (steps 1 to 4)
8.select wipe all data factory reset or something like that....
9.install zip from sdcard
10.select from sdcard
11.choose the file you downloaded
12.finish flash and reboot phone.
Click to expand...
Click to collapse

excellent guide! big thanx

bs828 said:
hi so let me get it right the phone is working (can turn on and use but cant call) yes? hmmmmm..... try this
MUST DOWNLOAD THIS DRIVERS!!!!
http://dottech.org/android/26188/usb-adb-and-fastboot-drivers-for-windows-for-all-android-phones/
Click to expand...
Click to collapse
Thanks,, Ive tried the 2nd option on step one and i think my phone successfully got to fastboot(just clean blank screen) so the cmd automatically run and states
C:\Desktop\adb rebootloader
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
error: protocol fault <no status>
C:\Desktop\fastboot flash recovery recovery.img
< waiting for device >
Did I miss something???

ok try again this time with the phone turned on. and then run the script and did you install the drivers?

bs828 said:
ok try again this time with the phone turned on. and then run the script and did you install the drivers?
Click to expand...
Click to collapse
yeah I installed the drivers...

hmmm maybe there are no fastboot drivers(main suspect....) there are a few ways to get it but for mine i just plug my phone in to my pc (windows 7 64bit) it just recognize it and tries to get the "google fastboot interface" drivers from windows update...

Try Volume Up+Search Key+Power to go into Fast boot Mode, There's different keys to activate Fastboot Mode (There is different versions of Fastboot)
Sent from my LG GT540 CM9 PreRC Polish Blood using xda premium

Your phone is/was bricked
Hey, I'm sorry to bing back such an old thread, but I just wanted to say this for posterity: your phone has/had a soft-brick. This means: you can't see Android nor LG boot logos, can't enter Recovery and (maybe) can't access Fastboot, but I'm not too sure on that last one. Besides that, the phone works "okay", but you should try to fix it.
Basically this soft-brick is almost always caught when upgrading from 1.6 to 2.1, so everyone should have it, including me. It took me a whole year to realize how to friggin' fix it lol, but here goes what I did:
Thanks for your help everyone, I came to a solution after a full year lol. Here's my enlightenment, from another Thread:
------------------------------------------------------------------------------------------
Just wanted to leave my 2 cents here, I've been trying to do my best since around august 2014, no success. 2 days ago I retried this, and I DID IT! I will tell everyone what I did very shortly:
My problem that I solved: I can boot, device works like a charm. But: no boot logos, no recovery.
My solution for TL;DR: UNINSTALL ALL DRIVERS FROM DEVICE MANAGER 1ST, then reinstall. After that, flash a fastboot ROM and use it to WIPE ALL THE DATA IN YOUR PHONE! THIS was what I needed and was never explained: you had to WIPE the old data in order to get the boot screens back.
IN THIS ORDER (THANK YOU to those people from previous replies, gathering all your info was of great value):
Uninstall all of your phone drivers from your PC!!! This is what made most of my headaches go away, just use Device Manager and uninstall anything from LGE. After that, plug in your device in your USB ports (always BACK ports, not front ports, important). It should detect all drivers and download them.
IF it fails (it generally does with LGE USB Modem), you can go to Device Manager > Unknown Device (the one that wasn't recognized) > Right Click and Update > Choose 2nd option, then choose "choose from a list of local controllers" (or whatever the button says). After that, scroll down to LG Electronics, Inc. and install what didn't install.
I also found these drivers, but I did not test them: http://www.mediafire.com/download/p693hcz6kkouh19/USB_Driver_LG_GT540.zip
Huzzah!
Now you're set to begin:
FIRST thing you wanna do is a factory reset, this is something I'd forgotten with time, don't make the same mistake as I did. You can do it by turning your phone on and pressing Volume +/- & Home & Quick Search buttons all together for 5 seconds (it works, be patient and wait for it, even if you open the camera or any other stuff).
Download this Google SDK Tools (unzip and put the folder in C:\ drive) and this Fastboot drivers for GT540 (unzip and put the files inside the folder in C:\android-sdk).
Skip this next line if you know your ROM has fastboot.
Now, if you don't have a ROM with fastboot, I recommend you use either European Open+Fastboot or V20C Orange France Fastboot ROM.
Click to expand...
Click to collapse
Since you have Fastboot enabled, now all you need to do is turn off your device (all this with its battery on it, no weird things) and hold the Camera button before turning it back on. This should take you either to a black screen, or simply to no display, like me. Either one will work anyways.
Now press the Windows key > Type cmd and open it with Right Click > Run as Administrator.
In it, type all this, command by command (you can paste by right clicking):
cd C:\android-sdk
fastboot -w
fastboot erase boot
fastboot erase system
fastboot -w
fastboot reboot
Click to expand...
Click to collapse
And now it's go time! Do what everyone else says in here: Take out your phone's battery, SD and SIM cards, fire KDZ Updater up as Administrator (If your KDZ freezes, then it's either faulty or you did not install msxml, look for a good KDZ that comes with that file and delete your current one), choose CS_Emergency PhoneMode and:
1-Plug your phone while holding the volume DOWN button (don't worry! My phone didn't show "Download Mode" either, if you hear the Windows "Somethingpluggedin" Bump noise, it's ok).
2-Flash French V20A
3-Unplug your phone once KDZ says "==FINISHED==".
4-Plug it once again, holding the volume DOWN button.
5-Flash out.kdz (remember! it's CS_Emergency).
Click to expand...
Click to collapse
THANK YOU XDA!
--------------------------------------------------------------------------------------
Also, if you look in here you'll find how to flash an awesome ROM, Cyanogen Mod 10 (should say "Final Version#2).

No Command Error

I went to update to KitKat and it was nearly done and then the "No Command" error came up. My tablet has an unlocked boot loader but isn't rooted. However it was before but I updated it from an OTA and that got rid of it. I've tried booting into recovery etc but the same thing happens.
Anyone have any advice please?

Same exact issue and set up here. Also, maybe I'm just dumb, but I can't get my tablet to turn off either. It just keeps cycling back to the "no command" screen until I do something.

tgearhar said:
Same exact issue and set up here. Also, maybe I'm just dumb, but I can't get my tablet to turn off either. It just keeps cycling back to the "no command" screen until I do something.
Click to expand...
Click to collapse
I think that both of you what you see (the "no command") is your stock recovery, if indeed you see an android with a yellow !.
If it is the case to access the menu of the stock recovery press power and tap volume up. The menu will give you the choice of rebooting your Nexus 7.

gunner1937 said:
I think that both of you what you see (the "no command") is your stock recovery, if indeed you see an android with a yellow !.
If it is the case to access the menu of the stock recovery press power and tap volume up. The menu will give you the choice of rebooting your Nexus 7.
Click to expand...
Click to collapse
I can get to the menu but when trying the reboot option, it just cycles the same way again. Back to the android with a red ! and says "No command." I also tried clearing cache and data to no avail. I was going to try using ADB to manually push the update but my computer was recently updated and now I can't get the driver installed for some reason.
I spent too much time messing around with and learning how to do things with my SIII and not enough time with this

Same deal here! Not sure what to do short of wiping and losing my info.

Same here...any advice? Not sure what happened. OTA update too.

Significa said:
Same here...any advice? Not sure what happened. OTA update too.
Click to expand...
Click to collapse
Wow, this seems to be widespread, at least somewhat. I'm in same situation. Toolkits, adb, nothing works. I thought this was a soft brick, but now I'm thinking it's toast. Probably doesn't help that I didn't have Dev options enabled along with USB Debugging. I can't even turn it off. Just bootloops after Google logo shows up twice, then to No Command error, then starts over again. I wonder what the hell is causing this. (Device was locked and unrooted)

Same boat here, even sideloaded the factory image via ADB.

[QUOTE [/QUOTE]
I was going to try using ADB to manually push the update but my computer was recently updated and now I can't get the driver installed for some reason.
If you have android-sdk-windows installed on your computer do not forget to update it through "SDK Manager.exe".

Pushing via ADB didn't work for me. That also failed.
I caved and called Google. Tech support is stumped as well.
Sent from my Nexus 5 using Tapatalk

Could this be a widespread issue? Like I don't even understand why it happened at all!
Sent from my Nexus 5 using XDA Premium 4 mobile app

I finally got mine working again!
I tried a million different things so I'm going to try and explain my process as simple as I can, I apologize in advance because I am far from an expert...
First, I tried using the method, well some of it, from this thread: http://forum.xda-developers.com/showthread.php?t=1907796
- I would suggest using this thread to get everything set up (drivers, ADB, the factory image downloaded and in the correct file location) I wasn't able to get the drivers working correctly with that route so I ended up using the toolkit to get them working but that thread helped me get all of the system files in the correct location and helped get all of the ADB stuff set up.
Once you have everything set up and your computer recognizes the tablet, (I checked that by opening a cmd prompt and using the command from the original thread above "adb devices"). As long as you see your device, I think you should be good.
From the "No Command" screen I held down Power and Volume + to get the menu to come up. I then chose the Restart option and immediately held Power and Volume -. This got me into the Fastboot Mode.
Once in Fastboot mode I went to the cmd prompt on my computer and used the following commands in this order from this post:
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot erase system -w
fastboot flash system system.img
fastboot reboot
*Make sure that all of the image files are in the proper location on your computer otherwise this step is worthless
The tablet then rebooted normally and I was able to set everything up again. Again, I am by no means an expert at all, this is just what worked for me. Try at your own risk.
I hope I covered all of the steps, I tried a million different things last night so they all kind of run together.

I ended up doing and it worked for me as well. Wiped everything though. How can I restore / reinstall my apps w/o needing to download them all again?

Two things: That guide says you must have USB Debugging enabled. Since my wife had this tablet, I did not have dev options enabled at all, including USB debug.
The other thing is that when I run the SDK Manager, nothing happens on my computer. I double click it or try Run as Admin, and a small CMD box flashes on my screen for a millesecond and disappears. That's all.

My wife's 2012 N7 is having this same problem. Unlocked bootloader, but I reflashed factory image and unrooted before giving it to her. She got the OTA last night, and now stuck at No Command.
I've subscribed to this thread, hoping that you guys will have it solved before I get home from work tonight! Would love to not have her lose all her data.
(I was kinda mad that she got the OTA last night and I haven't got it yet on my 2013 N7, but that's another gripe for another thread)

killswitch11 said:
Two things: That guide says you must have USB Debugging enabled. Since my wife had this tablet, I did not have dev options enabled at all, including USB debug.
The other thing is that when I run the SDK Manager, nothing happens on my computer. I double click it or try Run as Admin, and a small CMD box flashes on my screen for a millesecond and disappears. That's all.
Click to expand...
Click to collapse
Unfortunately I'm not sure on the SDK manager part. As far as the USB Debugging, I'm 98% sure that I did not have it enabled either. I think I did at one point but after doing several OTA upgrades, I'm sure it got unchecked.
---------- Post added at 01:34 PM ---------- Previous post was at 01:01 PM ----------
kr33mo said:
I ended up doing and it worked for me as well. Wiped everything though. How can I restore / reinstall my apps w/o needing to download them all again?
Click to expand...
Click to collapse
I don't believe there is a way. Maybe someone smarter than myself can chime in but I had to let the play store do it's thing and re-download all of mine.

tgearhar said:
I finally got mine working again!
I tried a million different things so I'm going to try and explain my process as simple as I can, I apologize in advance because I am far from an expert...
First, I tried using the method, well some of it, from this thread: http://forum.xda-developers.com/showthread.php?t=1907796
- I would suggest using this thread to get everything set up (drivers, ADB, the factory image downloaded and in the correct file location) I wasn't able to get the drivers working correctly with that route so I ended up using the toolkit to get them working but that thread helped me get all of the system files in the correct location and helped get all of the ADB stuff set up.
Once you have everything set up and your computer recognizes the tablet, (I checked that by opening a cmd prompt and using the command from the original thread above "adb devices"). As long as you see your device, I think you should be good.
From the "No Command" screen I held down Power and Volume + to get the menu to come up. I then chose the Restart option and immediately held Power and Volume -. This got me into the Fastboot Mode.
Once in Fastboot mode I went to the cmd prompt on my computer and used the following commands in this order from this post:
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot erase system -w
fastboot flash system system.img
fastboot reboot
*Make sure that all of the image files are in the proper location on your computer otherwise this step is worthless
The tablet then rebooted normally and I was able to set everything up again. Again, I am by no means an expert at all, this is just what worked for me. Try at your own risk.
I hope I covered all of the steps, I tried a million different things last night so they all kind of run together.
Click to expand...
Click to collapse
Worked for me! Thanks, I don't believe I had USB Debugging enabled either. Shame it wiped all my data though.

OK, got mine back up and running! I'll just leave what I did here in case anyone can benefit from it.
I first used Wug's Toolkit to download and install the RAW drivers. (Option #4, I believe) They were the only ones that worked for me. I followed the instructions to install them and then when it looped to the No Command screen, I held volume up and power. This got me to the menu, where I chose reboot. I then immediately held down the volume button and power to get into the bootloader screen, where it (thankfully) stopped looping. Then I unlocked the bootloader using the one-click option. Next step was to download and flash factory 4.4 image using the Soft Brick mode. Fastboot recognized my device and pushed the image. Now all is well. Close call... I've already enabled USB Debugging for my wife on this tablet so that crap doesn't happen again. She did lose all her data but she is happy to have a working tablet again instead of a $200 beer coaster.

killswitch11 said:
OK, got mine back up and running! I'll just leave what I did here in case anyone can benefit from it.
Click to expand...
Click to collapse
Worked for me as well. Really appreciate that.
Sent from my Nexus 5 using Tapatalk

killswitch11 said:
OK, got mine back up and running! I'll just leave what I did here in case anyone can benefit from it.
I first used Wug's Toolkit to download and install the RAW drivers. (Option #4, I believe) They were the only ones that worked for me. I followed the instructions to install them and then when it looped to the No Command screen, I held volume up and power. This got me to the menu, where I chose reboot. I then immediately held down the volume button and power to get into the bootloader screen, where it (thankfully) stopped looping. Then I unlocked the bootloader using the one-click option. Next step was to download and flash factory 4.4 image using the Soft Brick mode. Fastboot recognized my device and pushed the image. Now all is well. Close call... I've already enabled USB Debugging for my wife on this tablet so that crap doesn't happen again. She did lose all her data but she is happy to have a working tablet again instead of a $200 beer coaster.
Click to expand...
Click to collapse
I'll give that a go tomorrow. Missed my tablet! Hope it works!

Changing ROM with a small challenge

Today I wanted to switch to CM13 which I found on this forum. I messed up, phone got stuck in a reboot loop, got it into download mode and put it back to a stock version. Now however, I am not able to root my phone using ioroot. This is all I get when I try to root my phone, then it just stops.
Code:
Enable ADB connection..
Developer Options unlocked and ON.
USB debugging ON.
Accept RSA key fingerprint.
Press any key to continue . . .
Waiting for ADB detection...
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
When trying to change to a different stock ROM with LG FLASH TOOL 2014 I get the following error when my phone is connected to my PC with MTP.
Code:
The phone is disconnected from PC.
Connect the USB cable and wait a moment. Press the Retry button to resume the setting analysis process.
My phone is still connected, pressing the retry button brings up the same message.
When I select LG Software instead of MTP I get the following error.
Code:
To try upgrade again, follow the steps below.
1. Disconnect the phone from PC and remove hte battery from the phone.
2. Insert the battery back and reconnect the phone to PC.
3. Turn on the phone.
4. Press the Retry button below to start the upgrade.
I can't remove the battery, pressing retry after a reboot brings up the same message.
Software information:
Code:
Android version: 4.4.2
Baseband version: M8974A-AAAANAZM-1.0.190084
Kernel version: 3.4.0
Build number: KOT491.D80220h
Software version: D80220h-EUR-XX
Hardware information:
Code:
Model number: LG-D802
Memory: 32GB
So what do I want to do? Switch from the current ROM to a different one, as that is currently not possible for me. After this I wil retry to put CM13 on my phone. I am out of ideas (not that much experience) so hopefully someone on this forum can help me out!

MajorTemples said:
Today I wanted to switch to CM13 which I found on this forum. I messed up, phone got stuck in a reboot loop, got it into download mode and put it back to a stock version. Now however, I am not able to root my phone using ioroot. This is all I get when I try to root my phone, then it just stops.
Code:
Enable ADB connection..
Developer Options unlocked and ON.
USB debugging ON.
Accept RSA key fingerprint.
Press any key to continue . . .
Waiting for ADB detection...
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
When trying to change to a different stock ROM with LG FLASH TOOL 2014 I get the following error when my phone is connected to my PC with MTP.
Code:
The phone is disconnected from PC.
Connect the USB cable and wait a moment. Press the Retry button to resume the setting analysis process.
My phone is still connected, pressing the retry button brings up the same message.
When I select LG Software instead of MTP I get the following error.
Code:
To try upgrade again, follow the steps below.
1. Disconnect the phone from PC and remove hte battery from the phone.
2. Insert the battery back and reconnect the phone to PC.
3. Turn on the phone.
4. Press the Retry button below to start the upgrade.
I can't remove the battery, pressing retry after a reboot brings up the same message.
Software information:
Code:
Android version: 4.4.2
Baseband version: M8974A-AAAANAZM-1.0.190084
Kernel version: 3.4.0
Build number: KOT491.D80220h
Software version: D80220h-EUR-XX
Hardware information:
Code:
Model number: LG-D802
Memory: 32GB
So what do I want to do? Switch from the current ROM to a different one, as that is currently not possible for me. After this I wil retry to put CM13 on my phone. I am out of ideas (not that much experience) so hopefully someone on this forum can help me out!
Click to expand...
Click to collapse
Hi,
You don't need to install any further firmware. Go to this thread: http://forum.xda-developers.com/lg-g3/general/guide-root-lg-firmwares-kitkat-lollipop-t3056951
And root your device using the tool. It should root just fine.

iubjaved said:
Hi,
You don't need to install any further firmware. Go to this thread: http://forum.xda-developers.com/lg-g3/general/guide-root-lg-firmwares-kitkat-lollipop-t3056951
And root your device using the tool. It should root just fine.
Click to expand...
Click to collapse
After turning USB debugging off and on then using this I got a bit further.
Code:
Starting adb server...
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
Waiting for device...
Device detected!
Pushing files...
9383 KB/s (1048328 bytes in 0.109s)
4502 KB/s (9226 bytes in 0.002s)
9376 KB/s (4017098 bytes in 0.418s)
Rebooting...
Looking for LG serial port...
Serial port not found! please insert the phone manually into Download mode.
Disconnect the USB cable and turn off the phone.
Then press and hold the Volume Up button, and while you're doing that connect the USB cable again.
Waiting for device...
When I turn my phone off, hold the volume up button while plugging in my phone to my PC it just goes to the charging screen. I however did notice that if I reboot my device and switch to LG software from MTP in the "Select USB connection method" LG One Click Root continues and the following lines appear.
Code:
Waiting for device...
Phone found at COM3!
Rooting phone...
Then nothing happens. If I switch back from LG software to MTP again after this message the following message appears.
Code:
Author : blog.lvu.kr
SPECIAL COMMAND : ENTER, LEAVE
##
Done
Sounds great, so I went to check the root with Root Checker which says the following when I validate my root: "Sorry! Root acces is not properly installed on this device".
Would you have any other suggestions?

MajorTemples said:
After turning USB debugging off and on then using this I got a bit further.
Code:
Starting adb server...
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
Waiting for device...
Device detected!
Pushing files...
9383 KB/s (1048328 bytes in 0.109s)
4502 KB/s (9226 bytes in 0.002s)
9376 KB/s (4017098 bytes in 0.418s)
Rebooting...
Looking for LG serial port...
Serial port not found! please insert the phone manually into Download mode.
Disconnect the USB cable and turn off the phone.
Then press and hold the Volume Up button, and while you're doing that connect the USB cable again.
Waiting for device...
When I turn my phone off, hold the volume up button while plugging in my phone to my PC it just goes to the charging screen. I however did notice that if I reboot my device and switch to LG software from MTP in the "Select USB connection method" LG One Click Root continues and the following lines appear.
Code:
Waiting for device...
Phone found at COM3!
Rooting phone...
Then nothing happens. If I switch back from LG software to MTP again after this message the following message appears.
Code:
Author : blog.lvu.kr
SPECIAL COMMAND : ENTER, LEAVE
##
Done
Sounds great, so I went to check the root with Root Checker which says the following when I validate my root: "Sorry! Root acces is not properly installed on this device".
Would you have any other suggestions?
Click to expand...
Click to collapse
Then i would suggest you install kingo root and use that instead : https://www.kingoapp.com/root-lg.htm

Awesome worked, in hindsight I should've probably done some more reading up. Because I honestly have no idea what to do next. Should I install AutoRec,find a lollipop ROM install. Then root again, install AutoRec again, download CM13 together with GApps and flash these onto my device? I do realise that im starting to go off-topic, so if this is not allowed I'll post it in the official CM13 forum. Thanks for your help anyway!

MajorTemples said:
Awesome worked, in hindsight I should've probably done some more reading up. Because I honestly have no idea what to do next. Should I install AutoRec,find a lollipop ROM install. Then root again, install AutoRec again, download CM13 together with GApps and flash these onto my device? I do realise that im starting to go off-topic, so if this is not allowed I'll post it in the official CM13 forum. Thanks for your help anyway!
Click to expand...
Click to collapse
You don't need to go through all of that.
First, make sure you have the latest TWRP downloaded to your phone along with the hybrid LP bootloader for your phone.
Then, download the CM13 Rom and GApps you want to use to your phone.
Install KK AutoRec and reboot into recovery.
Flash updated TWRP and reboot back into recovery, then hybrid bootstack and reboot back into recovery (not sure entirely necessary to reboot, but it always works for me). Then you can flash most Stock-based LP or most CM13 or AOSP MM roms.
---------- Post added at 07:30 PM ---------- Previous post was at 07:26 PM ----------
One more thing - important! - take time to read through the thread of any roms you are interested in before flashing them. This will give you an idea of what, if any, issues you can expect and if any tricks are needed to get things working.

djchru said:
You don't need to go through all of that.
First, make sure you have the latest TWRP downloaded to your phone along with the hybrid LP bootloader for your phone.
Then, download the CM13 Rom and GApps you want to use to your phone.
Install KK AutoRec and reboot into recovery.
Flash updated TWRP and reboot back into recovery, then hybrid bootstack and reboot back into recovery (not sure entirely necessary to reboot, but it always works for me). Then you can flash most Stock-based LP or most CM13 or AOSP MM roms.
---------- Post added at 07:30 PM ---------- Previous post was at 07:26 PM ----------
One more thing - important! - take time to read through the thread of any roms you are interested in before flashing them. This will give you an idea of what, if any, issues you can expect and if any tricks are needed to get things working.
Click to expand...
Click to collapse
I have TWRP 2.7.0.0, downloaded the latest image from their websirte but for some reason im not able to install the image. I can't select the image within TWRP. The button that you would usually use to select images isn't there.
I've got a LG D802, so do I download the LP bootloader from here: http://forum.xda-developers.com/lg-g2/development/lg-g2-bootstacks-t3173715 ?
Appreciate the help!

MajorTemples said:
I have TWRP 2.7.0.0, downloaded the latest image from their websirte but for some reason im not able to install the image. I can't select the image within TWRP. The button that you would usually use to select images isn't there.
I've got a LG D802, so do I download the LP bootloader from here: http://forum.xda-developers.com/lg-g2/development/lg-g2-bootstacks-t3173715 ?
Appreciate the help!
Click to expand...
Click to collapse
You can use Flashify from the Play Store to install the TWRP for your device. Make sure you look at blastgator 's TWRP in the G2 Android Development section as it has special thermal control for our devices that will help keep you from damaging your screen. It is also flashable.

djchru said:
You can use Flashify from the Play Store to install the TWRP for your device. Make sure you look at blastgator 's TWRP in the G2 Android Development section as it has special thermal control for our devices that will help keep you from damaging your screen. It is also flashable.
Click to expand...
Click to collapse
Thanks for the heads up about the thermal problems, now on the thermal TWRP by blastgator. Downloaded the bootloader that I linked in my last post, flashed it and got stuck into a bootloop again. So now out of that bootloop, rooted again, and on TWRP 3.2.1-1 with thermal control. Should I try a different bootloader? Sorry for pretty much having to guide me through it with baby steps.

http://forum.xda-developers.com/lg-g2/development/boot-g2-hybrid-bootstacks-t3183219
Try this and let me know how it goes .
---------- Post added at 02:06 PM ---------- Previous post was at 02:04 PM ----------
Once you're up and running, you can check here as well http://forum.yairworkshop.com/viewforum.php?f=16

djchru said:
http://forum.xda-developers.com/lg-g2/development/boot-g2-hybrid-bootstacks-t3183219
Try this and let me know how it goes .
---------- Post added at 02:06 PM ---------- Previous post was at 02:04 PM ----------
Once you're up and running, you can check here as well http://forum.yairworkshop.com/viewforum.php?f=16
Click to expand...
Click to collapse
Should probably not have done that.
When I try to boot, nothing happens, when I hold the power button for 10 seconds the following message pops up.
Code:
ERROR : BOOT certification verify
[830]-----------------------------------
[880]
[930]Secure booting Error!
[1030]
[1080]----------------------------------
After this message the screen goes black again and nothing happens. The solution seems to be: http://forum.xda-developers.com/showthread.php?t=2582142
Problem is that I used a KDZ file to get the KK ROM on my G2 so I don't have any img. files.

You can kdz back or try getting back into recovery. If you get back to recovery, you might want to consider trying twrp 2.8.7.3.

djchru said:
You can kdz back or try getting back into recovery. If you get back to recovery, you might want to consider trying twrp 2.8.7.3.
Click to expand...
Click to collapse
KDZ'ing back means using the LG Flash Tool 2014? Because this doesn't seem to work as it says I haven't connected my phone to my PC, even tough it is connected. I cannot get back into recovery or download mode.
EDIT:
I just noted that the screen goes to black, so it's still on. No idead if this is important.

MajorTemples said:
Thanks for the heads up about the thermal problems, now on the thermal TWRP by blastgator. Downloaded the bootloader that I linked in my last post, flashed it and got stuck into a bootloop again. So now out of that bootloop, rooted again, and on TWRP 3.2.1-1 with thermal control. Should I try a different bootloader? Sorry for pretty much having to guide me through it with baby steps.
Click to expand...
Click to collapse
So you rooted and installed twrp. Then go ahead, make a full nandroid backup on an external usb via OTG and then try installing cm13 , follow steps provided by cm13 thread here.
GL

iubjaved said:
So you rooted and installed twrp. Then go ahead, make a full nandroid backup on an external usb via OTG and then try installing cm13 , follow steps provided by cm13 thread here.
GL
Click to expand...
Click to collapse
Unfortonately currently stuck on a black screen.

MajorTemples said:
Unfortonately currently stuck on a black screen.
Click to expand...
Click to collapse
Go to download mode by turning the phone completely off then hold only the volume up button while plugging it in to the computer

MajorTemples said:
Unfortonately currently stuck on a black screen.
Click to expand...
Click to collapse
I thought you successfully rooted and installed twrp. How did that happened?
I suggest go back to stock, upgrade till 5.0.2 lollipop and then root, install twrp via autorec and flash cm13. I did the same and it works. Lmk if you need further assistance.

Thanks for the suggestions, unfortunately I'm unable to enter download mode.

MajorTemples said:
Thanks for the suggestions, unfortunately I'm unable to enter download mode.
Click to expand...
Click to collapse
Hi,
If you are having issue shutting down your phone because it keeps booting back, then hold the power button ( keep holding it) until it goes black, reboot itself and goes black again. Then press volume up and insert usb into your pc to access download mode. It should fix.
If you simply cannot get into download mode, follow this guide : http://forum.xda-developers.com/showthread.php?t=2582142
LMK if it helped

iubjaved said:
Hi,
If you are having issue shutting down your phone because it keeps booting back, then hold the power button ( keep holding it) until it goes black, reboot itself and goes black again. Then press volume up and insert usb into your pc to access download mode. It should fix.
If you simply cannot get into download mode, follow this guide : http://forum.xda-developers.com/showthread.php?t=2582142
LMK if it helped
Click to expand...
Click to collapse
I have tried getting into download mode that way, but it doesn't work (has worked previously). Problem with that link is that I used a KDZ file so I dont have any img files. djchru said I can "KDZ back into recovery" but I have no idea what that means.