Related
***TL;DR AT THE BOTTOM***
*^*EDIT 2!!*^*
Utilizing Cerberus, I was able to get passed the boot animation into the lock screen, though the Launcher is, for all intents and purposes, nonexistent. However, I was able to install Nova Launcher and can go to a home screen just fine. THIS IS NOT SATISFACTORY. I want to get back to STOCK Launcher, but it apparently does not exist anymore. I've managed to copy over my backup of Launcher2.apk, but it still refuses to acknowledge its existence. Can I get an update.zip that'll reinstall the default launcher from someone? I can boot into recovery via ROM Manager now I suppose!
+++EDIT!+++
+++~~~I have discovered that my problem is not the device being stuck in boot up, but that the boot animation will not cease--as +in the device is actually powered on, just displaying the boot animation like a screen saver. I cannot boot into recovery as I get +the Google splash screen and it never goes anywhere, my bootloader is freezing every time I plug it into my computer, and the +drivers will not install. My computer cannot detect fastboot and I can't connect to the Nexus via adb either. I CAN access internal +storage but that's about the extent of what I can do.+++~~~
Long version:
I decided I wanted to change the App Drawer icon from stock to a Nexus X that inverted its colours when pressed. I found the icon, converted it to png, inverted the colours and everything was going fine.
After a while I finally managed to find the right icons to replace in the system apk file "launcher2.apk". "ic_allapps.png" and "ic_allapps_pressed.png" or something very similar. I simply replaced them with my two icons, installed my modified launcher2.apk, and that was it.
Immediately, my home wouldn't open at all, no matter how many times I pressed the home button. It just would not exit the app I had up. So I started backing and ended up in an infinite back loop. I powered off the device, waited a minute, and powered it back on.
It came to the usual "Google" screen with the unlocked symbol at the bottom, no problems. However, then it started playing the boot animation. The boot animation never stopped. It looped infinitely. I tried resetting the tablet a few times for the same result. It was after 3 am and I had to get up for work in 4 and a half hours. I thought that maybe it was gonna take a while. So I flipped the Nexus over while it was "booting up" and went to sleep.
When I woke up and checked the tablet at 7:30, it was STILL booting up. Obviously I had screwed something up.
Now, stupid me, I had never flashed CWM recovery on my Nexus 7 (haven't had it that long), so all I'm stuck with is STOCK Recovery. I'm pretty sure I can rescue the Nexus by factory resetting it or something similar, but I'd rather try to save it first. All I modified was a LAUNCHER application, so I'm pretty sure the current state of the Nexus itself shouldn't be too far gone. Is there any way to save the Nexus WITHOUT a data wipe? And if the data wipe DOESN'T fix my problem, is it possible to somehow flash a stock ROM through stock Android Recovery?
***TL;DR***
I modified launcher2.apk and replaced "ic_allapps.png" and "ic_allapps_pressed.png" with two customized .png files (which I renamed to their appropriate file names). Now my Nexus is stuck on the boot animation indefinitely. I would like to save all of my data, as a data wipe would be inconvenient, but if I must do one I shall. I am on a stock ROM and a stock Recovery. If a data wipe/factory reset will not save my device, is it possible to flash a stock ROM through regular Android Recovery?
===Related but irrelevant to the problem===
Is it completely impossible to change the stock App Drawer icon to something different? I'd rather not have to get a different launcher app just to create a Nexus theme! I did a little more research and found that I should've modified the "all_apps_button_icon.xml" file as well, but I have NO idea how to do that.
Many thanks,
VonDerThWood.
As long as you can get into the bootloader you can flash back to stock using fastboot and the image from here
NeoMagus said:
As long as you can get into the bootloader you can flash back to stock using fastboot and the image from here
Click to expand...
Click to collapse
no need to flash back to stock, silly advice. just flash a custom recovery and flash a stock rooted rom. flashing a stock rooted rom will replace what you messed up on. dont wipe.
simms22 said:
no need to flash back to stock, silly advice. just flash a custom recovery and flash a stock rooted rom. flashing a stock rooted rom will replace what you messed up on. dont wipe.
Click to expand...
Click to collapse
How can I reflash the ROM on stock Android recovery? Googling that returns CWM results.
He is suggesting you flash custom recovery with fastboot and just flash over top of what you did thru the custom recovery which you can do as well, what I suggested just returns it to factory state I don't see whats so silly about it I understand he wants to keep his data but worse comes to worse as long as you can get into the bootloader you're fine
NeoMagus said:
He is suggesting you flash custom recovery with fastboot and just flash over top of what you did thru the custom recovery which you can do as well, what I suggested just returns it to factory state I don't see whats so silly about it I understand he wants to keep his data but worse comes to worse as long as you can get into the bootloader you're fine
Click to expand...
Click to collapse
youre right about if worse comes to worse. reflashing the factory image should be the very last thing to do, when all other options have been tried. im just trying to save his data
If you don't have fastboot set up you might want to give this post a look he describes how to get it set up.
simms22 said:
youre right about if worse comes to worse. reflashing the factory image should be the very last thing to do, when all other options have been tried. im just trying to save his data
Click to expand...
Click to collapse
I don't use custom recoveries and backup my data regularly with Titanium, so restoring after a reflash is really just an afterthought here, to each there own
The problem is not as it seems.
When I plug the Nexus into the computer when in Fastboot mode, it freezes the Recovery. I cannot select anything OR move the selection to anything else. The hell?
I noticed that when the Nexus attempts to boot up, the boot animation gets brighter.
__
Wait, when it attempted to boot up when plugged into my PC, AutoPlay recognized the device as Nexus 7. There is nothing on my screen but the boot animation, however I can browse internal storage.
I cannot, however, connect to it via adb apparently. ADB devices returns nothing.
____
Okay, the problem is NOWHERE near what I thought it was. The boot animation is replacing the lock screen/home screen/everything. I just received an email (I could tell because of the notification noise the tablet made). It is booting up, just not displaying anything passed the boot animation and ADB cannot detect the device. I KNOW it has USB Debugging mode activated and all, but what can I do now?
===
I usually make backups and nandroids but I've barely owned this device. ;P
Does fastboot detect the device?
janedoesmith said:
Does fastboot detect the device?
Click to expand...
Click to collapse
Fastboot doesn't detect the device while booted up like this, and when I plugged it into the computer when in recovery/fastboot mode it not only froze the device, but fastboot wouldn't detect it.
I can get into the internal storage (just not the root of the device unfortunately). So what can one do when he cannot connect to the device via fastboot or adb, nor flash a custom recovery image because he can't access fastboot?
This is getting more complicated the more I dig into it. What the hell did I do?
Are you on the correct screen? I see how you are lumping Fastboot/recovery together, Fastboot is used on the screen with the android with his chest open after holding down the power/vol buttons from complete off , has version info/ unlock status in the lower left.. not sure if you can do that in the recovery but that is where I put the commands in
the freezing in the bootloader is a n7 bug. try a few times. try going into the bootloader then plugging in usb, and try plugging in via usb then going into the bootloader. try a few times, eventually you will get it.
VonDerThWood said:
Fastboot doesn't detect the device while booted up like this, and when I plugged it into the computer when in recovery/fastboot mode it not only froze the device, but fastboot wouldn't detect it.
I can get into the internal storage (just not the root of the device unfortunately). So what can one do when he cannot connect to the device via fastboot or adb, nor flash a custom recovery image because he can't access fastboot?
This is getting more complicated the more I dig into it. What the hell did I do?
Click to expand...
Click to collapse
You have to be in bootloader for fastboot to detect your device. Once in bootloader, open a command prompt where your fastboot.exe is stored and type "fastboot devices" without the quotes. If it detects it, it should list your N7's serial number.
NeoMagus said:
Are you on the correct screen? I see how you are lumping Fastboot/recovery together, Fastboot is used on the screen with the android with his chest open after holding down the power/vol buttons from complete off , has version info/ unlock status in the lower left.. not sure if you can do that in the recovery but that is where I put the commands in
Click to expand...
Click to collapse
Fastboot has the "Recovery mode" option but it just gives me the Google logo with the unlocked icon at the bottom indefinitely...which means I cannot access recovery either? Why didn't I notice this before? >_<
simms22 said:
the freezing in the bootloader is a n7 bug. try a few times. try going into the bootloader then plugging in usb, and try plugging in via usb then going into the bootloader. try a few times, eventually you will get it.
Click to expand...
Click to collapse
Tried 10 times by booting into bootloader first, then 10 times by plugging it in and booting into it while it's plugged in. This is a very...odd bug.
janedoesmith said:
You have to be in bootloader for fastboot to detect your device. Once in bootloader, open a command prompt where your fastboot.exe is stored and type "fastboot devices" without the quotes. If it detects it, it should list your N7's serial number.
Click to expand...
Click to collapse
Nothing at all. Won't detect it or anything.
it is an odd bug. i think every n7 owner who likes to flash roms/kernels has had to deal with it at least once.
VonDerThWood said:
janedoesmith said:
You have to be in bootloader for fastboot to detect your device. Once in bootloader, open a command prompt where your fastboot.exe is stored and type "fastboot devices" without the quotes. If it detects it, it should list your N7's serial number.
Click to expand...
Click to collapse
Nothing at all. Won't detect it or anything.
Click to expand...
Click to collapse
What about in device manager? Does it at least show an unknown device or something similar? Try reinstalling the drivers.
janedoesmith said:
What about in device manager? Does it at least show an unknown device or something similar? Try reinstalling the drivers.
Click to expand...
Click to collapse
Now that I think about it, it DID say something about failing to install an unknown driver the first time I plugged it in. Let me uninstall/reinstall the drivers.
____
After reinstalling the drivers (and removing both of the Nexus7 specific ones), I also removed one named "Android", which, coincidentally, is the driver that the tablet is trying to install upon being plugged in. I have tried to reinstall it several times, but it fails each time, AND I just reinstalled the real Nexus 7 drivers.
___
The Nexus drivers won't reinstall now. I even went to Asus's website and downloaded them, but I have no clue how to install it in this format.
Is there a way to open/install an app through JUST the Internal Storage? If so, I have the stock launcher2.apk file right here...I just need to reinstall it! Damn, how can I get to the Root folder without ADB?
Whoa! Stroke of GENIUS!
I have Cerberus installed on my tablet. Since I know the tablet is booting up, just not displaying passed the boot animation, I decided to give it a try.
I started an alarm, which forced the tablet to the lock screen...I can open apps through the Play Store (as I got an update notification) and the like, but I can NOT get to the home screen.
I opened Total Commander via Play Store, but I can't do anything with it. The app that I used was NinjaMorph and I'm pretty sure the only way I can correct my mistake is through that app. What do I do?
Found NinjaMorph in the Play Store, it couldn't fix my problem. Oh hell.
I tried to copy/replace the launcher2.apk file I screwed up with a backed up one but TotalCommander couldn't do it. It was even granted SuperUser permissions. Attempting with Root Explorer.
Success! I have copied the original Launcher2.apk back into the /system/app folder. HOWEVER, I can NOT install it.
Managed to connect via adb! Things are looking up! Now, how to install this stuff...?
When trying to reinstall the launcher2.apk, it gives me the following error:
INSTALL_FAILED_UID_CHANGED
So I tried uninstalling it to no avail. Troubling.
SO! Now what? I am into the device, and any app I have downloaded through the Play Store is available to me, but I cannot go to the home screen. I need to reinstall the original Launcher2.apk!
Retrying NinjaMorph. It supposedly installed my Launcher2.apk. However, I still cannot return to the Home screen. WTF.
I'm going to install a different Launcher. Hope that works!
Success. I can now return home to Nova Launcher. HOWEVER...
This is not satisfactory. I want my STOCK launcher. Anybody know how I can fix this? The stock launcher is acting like it doesn't exist anymore. Is there a way to just wipe THAT data and keep all the other data on my device?? (Though I admit, I do like how I already was able to change my App drawer icon to my Nexus X <3.)
Edit: I see you resolved it. Good job! I'll just leave this here... :good:
Is there a way to open/install an app through JUST the Internal Storage? If so, I have the stock launcher2.apk file right here...I just need to reinstall it! Damn, how can I get to the Root folder without ADB?
Click to expand...
Click to collapse
You sound to be in Windows driver hell. If you have access to a Linux machine or someone who does, this entire driver mess can be avoided.
You can't install an apk via the MTP or PTP usb interface. You have a few options to fix this, but all depends on getting your drivers sorted.
Otherwise, grab the latest Windows USB drivers from Google - https://dl-ssl.google.com/android/repository/usb_driver_r07-windows.zip and follow these instructions to install them - http://developer.android.com/tools/extras/oem-usb.html
With the drivers installed and the nexus 7 plugged in, try adb devices again. Assuming you can resolve the driver issue, run
Code:
adb install path\to\launcher2.apk
comminus said:
You sound to be in Windows driver hell. If you have access to a Linux machine or someone who does, this entire driver mess can be avoided.
You can't install an apk via the MTP or PTP usb interface. You have a few options to fix this, but all depends on getting your drivers sorted.
Otherwise, grab the latest Windows USB drivers from Google - https://dl-ssl.google.com/android/repository/usb_driver_r07-windows.zip and follow these instructions to install them - http://developer.android.com/tools/extras/oem-usb.html
With the drivers installed and the nexus 7 plugged in, try adb devices again. Assuming you can resolve the driver issue, run
Code:
adb install path\to\launcher2.apk
Click to expand...
Click to collapse
I managed to get ADB working (via adbWireless) after the above post I made, however I cannot get launcher2.apk to install. This time I got the "INSTALL_FAILED_DEXOPT" error instead of the "INSTALL_FAILED_UID_CHANGED" one.
Hi
Tried to flash a new kernel and all seemed ok (flashed phones and nexus 7 few times now) when I came out of flashing I hit a bootloop, I though nothing of it and tried to restart....same issue, so next I tried to go into cw recovery, no joy, it will not show again.
I can power/vol keys to android fastboot screen with start power restart boot and so on but if I choose recovery nothing happens, I am stuck with either a bootloop or stuck on android fastboot screen and not able to move from either.
I have tried the toolkit and most other things but the problem is it cannot see my nexus 7, even after installing drivers and so on the toolkit (top right) does not list my nexus as found, because of this I cannot reflash any stock firmware/recover/reflash cwr.
Not sure how I can get around this if my pc cannot see the nexus 7.
Thanks for any help
voodoochild2008 said:
Hi
Tried to flash a new kernel and all seemed ok (flashed phones and nexus 7 few times now) when I came out of flashing I hit a bootloop, I though nothing of it and tried to restart....same issue, so next I tried to go into cw recovery, no joy, it will not show again.
I can power/vol keys to android fastboot screen with start power restart boot and so on but if I choose recovery nothing happens, I am stuck with either a bootloop or stuck on android fastboot screen and not able to move from either.
I have tried the toolkit and most other things but the problem is it cannot see my nexus 7, even after installing drivers and so on the toolkit (top right) does not list my nexus as found, because of this I cannot reflash any stock firmware/recover/reflash cwr.
Not sure how I can get around this if my pc cannot see the nexus 7.
Thanks for any help
Click to expand...
Click to collapse
try to flash recovery again via fastboot...or doesnt pc recognize divice at all?
S.R
shivasrage said:
try to flash recovery again via fastboot...
S.R
Click to expand...
Click to collapse
Hi
I cannot flash anything. On the fastboot screen I can scroll up and down powr off/start/recovery....if I choose any (apart from power off) nothing happens.
When I hook it up to my pc it cannot see it, nexus 7 toolkit also cannot see it, it does not list it as found so I cannot flash anything on to it, if I try it just says waiting for device, tried other things and same thing either waiting for device or asks if fastboot installed.
voodoochild2008 said:
Hi
I cannot flash anything. On the fastboot screen I can scroll up and down powr off/start/recovery....if I choose any (apart from power off) nothing happens.
When I hook it up to my pc it cannot see it, nexus 7 toolkit also cannot see it, it does not list it as found so I cannot flash anything on to it, if I try it just says waiting for device, tried other things and same thing either waiting for device or asks if fastboot installed.
Click to expand...
Click to collapse
f****
have you tried flashing factory image from google site.with flash all-sh?
shivasrage said:
f****
have you tried flashing factory image from google site.with flash all-sh?
Click to expand...
Click to collapse
I have a image ready but not able to flash....but what is flash all-sh? trying to search for it, is it a tool to force flash?
voodoochild2008 said:
I have a image ready but not able to flash....but what is flash all-sh? trying to search for it, is it a tool to force flash?
Click to expand...
Click to collapse
no its included in the factory image to flash all i one so it looks like for the nexus 4:
flash-all .....its a windows batch image with all included.... try this
S:R.
shivasrage said:
no its included in the factory image to flash all i one so it looks like for the nexus 4:
flash-all .....its a windows batch image with all included.... try this
S:R.
Click to expand...
Click to collapse
Thanks....but still get waiting for device, thats the problem, nothing seems to see it so I cannot flash anything to it.
You are already at the bootloader screen. Use your computer to fastboot flash a new kernel. Being able to get into recovery has nothing to do with it. You screwed it up flashing a kernel. Its likely thats all you need to fix it. Flash a new one with fastboot.
You are already at the bootloader screen. Use your computer to fastboot flash a new kernel. Being able to get into recovery has nothing to do with it. You screwed it up flashing a kernel. Its likely thats all you need to fix it. Flash a new one with fastboot.
i thought the same as you but fastboot isn recognizig N7 anymore....always wating for device....
Hemidroids said:
You are already at the bootloader screen. Use your computer to fastboot flash a new kernel. Being able to get into recovery has nothing to do with it. You screwed it up flashing a kernel. Its likely thats all you need to fix it. Flash a new one with fastboot.
Click to expand...
Click to collapse
Downloaded the fastboot exe but unsure what it needs to work as when I click on it a run box opens for like half a second and then closes, dont get a chance to read what it says, think I will have to read up on it.
[/COLOR]
voodoochild2008 said:
Downloaded the fastboot exe but unsure what it needs to work as when I click on it a run box opens for like half a second and then closes, dont get a chance to read what it says, think I will have to read up on it.
Click to expand...
Click to collapse
read this... i hope you can follwow that easily like me...
greets S.R.
http://dottech.org/21534/how-to-ins...ows-computer-for-use-with-your-android-phone/
voodoochild2008 said:
Downloaded the fastboot exe but unsure what it needs to work as when I click on it a run box opens for like half a second and then closes, dont get a chance to read what it says, think I will have to read up on it.
Click to expand...
Click to collapse
EXE? doh.......Windows.......sorry cant help.
shivasrage said:
[/COLOR]
read this... i hope you can follwow that easily like me...
greets S.R.
http://dottech.org/21534/how-to-ins...ows-computer-for-use-with-your-android-phone/
Click to expand...
Click to collapse
Tried some of that already but will try again tomorrow.
Thanks for help with this and will post tomorrow if I can sort it. cheers
I hope this instructions can help you a little bit...but if it fails don´t be angry its all I can think of ...at this time ....merry christmas
S.R.
http://forum.xda-developers.com/showthread.php?p=31931117:D
Sent from my Nexus 7 using xda premium
Well after using bits of jrom flasher and nexus toolkit I got it working again, main issue was making the tablet seen, abd and fastboot would not show device.
All up and running again THANKS TO ALL WHO HELPED
voodoochild2008 said:
Well after using bits of jrom flasher and nexus toolkit I got it working again, main issue was making the tablet seen, abd and fastboot would not show device.
All up and running again THANKS TO ALL WHO HELPED
Click to expand...
Click to collapse
How did you get it to work? I have problem getting my device to be recognized. Stuck on boot loop too..
Hey man, how did you get your computer to recognize your device? Would be great to finally fix mine as this is the same exact problem -- computer doesn't recognize it even though in fastboot.
Quacker245 said:
Hey man, how did you get your computer to recognize your device? Would be great to finally fix mine as this is the same exact problem -- computer doesn't recognize it even though in fastboot.
Click to expand...
Click to collapse
I don't understand exactly what you are trying to do, sorry: you said the pc does not see the nexus, "even thought in fastboot".. If you say even thought, it seems to me that you are able to access Android itself or maybe recovery? In that case I can't see the issue.. Sorry my fault, non english mother tongue
But, if have the device soft bricked and you are able to enter ONLY the bootloader (that is what we call often fastboot), then you should start to remove the not working fastboot drivers installed into your PC: launch the nexus in fastboot mode, go to Device Manager into your PC and search for a driver with an yellow exclamation point. This issue is very common so I hope that you have it, too.. So, uninstall that driver, then unlink the nexus from your PC; after a few seconds attach it to another USB port and see if Windows install a driver (it should). If this new driver doesn't work, too, or if Windows does no install any, try this one: http://forum.xda-developers.com/showthread.php?t=1426502
Hope it helps, let us know, see you!
EDIT: also, if you still have no luck, you should find a Linux or Mac PC/laptop and download the adb/fastboot binary files for that OS; this will definitively solve your driver issue ( @#ò#@!"@# Winzozz )
brainvision said:
I don't understand exactly what you are trying to do, sorry: you said the pc does not see the nexus, "even thought in fastboot".. If you say even thought, it seems to me that you are able to access Android itself or maybe recovery? In that case I can't see the issue.. Sorry my fault, non english mother tongue
But, if have the device soft bricked and you are able to enter ONLY the bootloader (that is what we call often fastboot), then you should start to remove the not working fastboot drivers installed into your PC: launch the nexus in fastboot mode, go to Device Manager into your PC and search for a driver with an yellow exclamation point. This issue is very common so I hope that you have it, too.. So, uninstall that driver, then unlink the nexus from your PC; after a few seconds attach it to another USB port and see if Windows install a driver (it should). If this new driver doesn't work, too, or if Windows does no install any, try this one: http://forum.xda-developers.com/showthread.php?t=1426502
Hope it helps, let us know, see you!
EDIT: also, if you still have no luck, you should find a Linux or Mac PC/laptop and download the adb/fastboot binary files for that OS; this will definitively solve your driver issue ( @#ò#@!"@# Winzozz )
Click to expand...
Click to collapse
Hi sorry for not being clear. Basically I am only allowed to access the bootloader and my device is soft-bricked. I'm pretty sure I tried uninstalling and reinstalling the drivers about a year ago when I originally did it, but I'll try again and let you know. Thanks!
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!
Hi all,
I have a serious problem with my G2 which I could not solve: I used the new LG Flash Tool 2014 with stock KDZ file, everything was going just fine till I received an error message that LG server is not available, I disconnected the USB cable by mistake from my G2 and afterward I saw that it was in the middle of flashing process (12% was completed). I turned it off and tried to reach download mode again and nothing!, I'm receiving the "LG" logo and nothing- the screen goes black (it is still on).
I tried also to connect my phone to the computer- I received a list of 13 "new" local disks "H" to "T", only "H" disk is available and it's showing "image" folder with list of files.
I cannot reach "download mode", nothing is working!
I hope this is not the end for my G2..
please help me
Thank you so much!
If you could receive all those hard disks then you could maybe fix it with linux/ubuntu if you have it. Search for guides to cOpy the neccesary stuff bacK like the bootloader. I can't really help you atm as i am too sleepy.
wulsic said:
If you could receive all those hard disks then you could maybe fix it with linux/ubuntu if you have it. Search for guides to cOpy the neccesary stuff bacK like the bootloader. I can't really help you atm as i am too sleepy.
Click to expand...
Click to collapse
Thank you for your reply. I found this on the sticky threads: "[FIX] NO Recovery mode, No download mode, after OTA on rooted LG G2".
I installed ubuntu and followed the instructions. when I type the following: "gdisk -l /dev/sde" I receive an error message:
"GPT fdisk (gdisk) version 0.5.1
NOTE: Write test failed with error number 13. It will be impossible to save
changes to this disk's partition table!
Problem opening /dev/sde for reading! Error is 13
You must run this program as root or use sudo!"
My device is not rooted, is this the problem?
Please help me!!
Thanks
@NNCa It says you need to run the program as root on ubuntu.
Just use sudo in front of the commands.
You need to type once your password to use sudo, you can't see the password if you enter it for safety I guess but just click enter after you typed ykur password.
wulsic said:
@NNCa It says you need to run the program as root on ubuntu.
Just use sudo in front of the commands.
You need to type once your password to use sudo, you can't see the password if you enter it for safety I guess but just click enter after you typed ykur password.
Click to expand...
Click to collapse
Thank you so much!!
I succeeded to push all the files according to this thread, however I do not see the TWRP menu. I have just constant "LG" logo on screen.
Do I miss something?
Thanks!
NNCa said:
Thank you so much!!
I succeeded to push all the files according to this thread, however I do not see the TWRP menu. I have just constant "LG" logo on screen.
Do I miss something?
Thanks!
Click to expand...
Click to collapse
Well its good you're an step further, try to reboot to recovery using power+volume down i believe or its up idk try both it should say something about wipe data factory reset, press the power button and you are in recovery.
wulsic said:
Well its good you're an step further, try to reboot to recovery using power+volume down i believe or its up idk try both it should say something about wipe data factory reset, press the power button and you are in recovery.
Click to expand...
Click to collapse
Hi,
I powered off my phone by pressing volume down + power for a while ("LG" logo blinked once and phone was fully powered off).
I pushed volume down + power till I saw the LG logo, released it, and pushed again- and finally I reached the Factory Hard Reset screen. I have pushed 3 times the power, and I have got "Factory reset processing..." and nothing is appeared, even when I'm pushing several times on power again.
I guess this is the end of my G2 :crying:
Thank you all for your support, this is an excellent forum!:good::good:
NNCa said:
Hi,
I powered off my phone by pressing volume down + power for a while ("LG" logo blinked once and phone was fully powered off).
I pushed volume down + power till I saw the LG logo, released it, and pushed again- and finally I reached the Factory Hard Reset screen. I have pushed 3 times the power, and I have got "Factory reset processing..." and nothing is appeared, even when I'm pushing several times on power again.
I guess this is the end of my G2 :crying:
Thank you all for your support, this is an excellent forum!:good::good:
Click to expand...
Click to collapse
Nope it isn't the end try to install the recovery again or try to push the custom twrp recovery again to the right partition! Dont give up that fast when i hear your things then its still fixable! you already got the factory reset processing so try to Push the Recovery again and search for an guide about recovery maybe Then you would probably get your device fixed.
Just read my things about simplicity so think easy and you can fix it. AND STAY POSITIVE You will repair your phone today :good:
wulsic said:
Nope it isn't the end try to install the recovery again or try to push the custom twrp recovery again to the right partition! Dont give up that fast when i hear your things then its still fixable! you already got the factory reset processing so try to Push the Recovery again and search for an guide about recovery maybe Then you would probably get your device fixed.
Just read my things about simplicity so think easy and you can fix it. AND STAY POSITIVE You will repair your phone today :good:
Click to expand...
Click to collapse
Thanks, but after connecting the device to linux/windows, it seems that it is not recongized, I do not see the partitions anymore even when typing "ls /dev/sd*" through linux terminal..
NNCa said:
Thanks, but after connecting the device to linux/windows, it seems that it is not recongized, I do not see the partitions anymore even when typing "ls /dev/sd*" through linux terminal..
Click to expand...
Click to collapse
Yeah because the phone has bootloader etc again so maybe you can try this:
http://forum.xda-developers.com/showthread.php?t=2432476
wulsic said:
Yeah because the phone has bootloader etc again so maybe you can try this:
http://forum.xda-developers.com/showthread.php?t=2432476
Click to expand...
Click to collapse
Hi there,
I tried to flash my phone using the lg flash tool, unfortunately it cannot recognized any connected device through USB.. I don't know what else will work for my device
NNCa said:
Hi there,
I tried to flash my phone using the lg flash tool, unfortunately it cannot recognized any connected device through USB.. I don't know what else will work for my device
Click to expand...
Click to collapse
Did you already installed the LG drivers? and checked in device manager or there is like any change when you connect and disconnect your phone?
wulsic said:
Did you already installed the LG drivers? and checked in device manager or there is like any change when you connect and disconnect your phone?
Click to expand...
Click to collapse
Yes, I checked it- no response during connecting/disconnecting the device..
Maybe I did a mistake when trying to push those image files.. I guess there is nothing I can do to fix my phone..
Do you have any other suggestions?
Can someone please help me. How can I get to the LG device- Is there another software I can use to flash files into this device?
Thanks
NNCa said:
Can someone please help me. How can I get to the LG device- Is there another software I can use to flash files into this device?
Thanks
Click to expand...
Click to collapse
Sorry for late reaction but i needed to think of something. Did you tryed to use another cable? Did you tryed to do it on another pc? Did you tryed to maybe install LG PC suite and see if it gets recognized? If you have the PC Suite you may need to turn it off in the LG flashtool idk. Can you tell us more like which windows you have?
wulsic said:
Sorry for late reaction but i needed to think of something. Did you tryed to use another cable? Did you tryed to do it on another pc? Did you tryed to maybe install LG PC suite and see if it gets recognized? If you have the PC Suite you may need to turn it off in the LG flashtool idk. Can you tell us more like which windows you have?
Click to expand...
Click to collapse
Hi,
I tried all you suggested, however my devide is not recognized. I tried to use the LG PC Suite and to flash by IMEI, however it is still saying that no device was connected.. I checked windows device manager, and nothing changed there.
There is any chnage I can see my connected device? use some tool or another software?
Thank you again for your patience and help!
NNCa said:
Hi,
I tried all you suggested, however my devide is not recognized. I tried to use the LG PC Suite and to flash by IMEI, however it is still saying that no device was connected.. I checked windows device manager, and nothing changed there.
There is any chnage I can see my connected device? use some tool or another software?
Thank you again for your patience and help!
Click to expand...
Click to collapse
Hi, sorry to say but you have unfortunately completely hardbricked your device. It happened to me too however I was able to get it replaced under warranty at no extra cost.
What happened was that when your phone was still detected by linux, you had a chance to recover by flashing the correct partitions to gain access to download mode and from there, flash a KDZ to go back to complete stock. However, the files you used were probably incompatible with your variant which has now corrupted your bootloader sequence. I suggest you read this reply by fizzy177 as well as the rest of the thread: http://forum.xda-developers.com/showpost.php?p=51522304&postcount=118
So right now, you cannot do anything as you have already found out, no computer will recognise that your phone is plugged in. Your phone fails to boot when you try enter the download mode and it just freezes on the splash screen which looks like this: http://www.lg-phones.org/wp-content/uploads/2014/03/image2.png
What's meant to happen is your phone should load past that initial splash screen into this http://www.androiddunya.com/wp-content/uploads/2014/01/LG-G2-DownloadMode.jpg which accepts KDZ flashing and warns the device has been rooted.
So it's a blessing that your phone cannot boot as LG cannot find out you have voided warranty and you will be able to get a replacement free of charge.
Issue was solved- device was fixed under warranty
Hi,
I just want to update you all that my device was fixed under warranty! (motherboard replacement)
Thank you all for help and great support, this is a great forum with great community :good::good:
Hello
From past 2 weeks i am wondering on internet for a solution . Hours and hours of surfing and articles but still
Hope some one solve this issue.
Okay. First i m using LG G2 F320 K update to lollipop . Non rooted. It was working fine . I can transfer files in MTP .
But about a month ago i get an update for my phone . And after some days i need to transfer some files to my phone , i wonder when i connected my phone to computer nothing happened . No notification on mobile for changing PTP MTP option . Also nothing happened in Computer device manager..
From that day i am unable to connect my phone with windows 10. It always charging mobile.
I uninstalled all drivers in device manager and installed from LG website. I updates windows N and NK MTP update from windows for windows 10.
I changed different data cables and different computers and different ports . All stuff i can do. Still no luck.
When ever i plug USB data cable it always put my Mobile on Charging . No notification on Mobile. Also i go in setting > storage> and there is no option in upper right corner to select USB PC connection .
I am in developer mode and debugging mode is on also. Also USB tethering option is Disabled .
Kindly some one help me regarding this.
LG G2 F320K updated to stock Koren lollipop 5.0.1 . Non root.( i updated lollipop in April 2015)
Issue i am facing is no notification for Charging/ MTP/PTP Usb Debugging on mobile notice bar when i attach my phone using USB cord with computer. Also in computer device manager nothing happen. Even i checked on windows 10 , 8.1, 8, 7 .
I remember it was working like charm 4 weeks before I can change MTP PTP or Charge only mode by selecting notification when i attach it to my laptop. I can transfer files can use LG PC suit .
Then i received an software update like 40 mb and i updated my mobile. That i remembered.
After that 2 weeks before i need to transfer some books from laptop to my mobile. When i plugged my device there no notification to select MTP mode . Also there is nothing happened in my windows 10. I looked in task manager. No yellow icon in computer task manager for driver thing.
Laptop is just silent and mobile is just on charging .
Then i go to setting in LG and looked for USB PC connection settings. I wonder there is nothing . Settings > storage > 3 dot in upper right corner.. it suppose to be there . But here is no 3 dot in storage. Then i looked into share and networks in android setting and i found that USB tethering. But its faded mean it is disabled and i am unable to use this feature also.
I tried on different computers different cables , original, but nothing. Always when i plug usb mobile went on charging and in all computers nothing happen in device manager.
USB debugging is on.. I factory reset device 2 times. but useless. Also i uninstall all drivers from my laptop and then reinstall drivers from LG website also i tried google drivers , ABD, different ports. Nothing nothing happen.
Also now if i try put mobile on download mode by turning device off and then push + vol button and then put cord in mobile . No download mode also it went on charging. Well charging from laptop or from charger is okay.
Hope i explain all.
I could with some help please. I expect that the answer is already on the forum somewhere, so if someone could post a link, that would be great.
My Nexus - unlocked and rooted - 5.1 with Wugfresh several months ago, today decided not to boot up.
I get "Google" then it goes to a black/glowing screen and stays there.
With some fiddling around I can get the dead Android and "no command". I can get into the power off/recover/reboot bootloader etc screen.
I have wiped the cache - no change.
I have done a factory reset - wiped all data - no change.
Using Wugfresh, I get - no ADB
I am not able to check usb debugging because I can't get into the device.
The thing is obviously alive (although not as we know it) because windows install a driver for it when it is plugged in to the USB post. However it installs an MTP driver and I am not able to change this.
Any ideas anyone?
Thanks
lejars1 said:
I could with some help please. I expect that the answer is already on the forum somewhere, so if someone could post a link, that would be great.
My Nexus - unlocked and rooted - 5.1 with Wugfresh several months ago, today decided not to boot up.
I get "Google" then it goes to a black/glowing screen and stays there.
With some fiddling around I can get the dead Android and "no command". I can get into the power off/recover/reboot bootloader etc screen.
I have wiped the cache - no change.
I have done a factory reset - wiped all data - no change.
Using Wugfresh, I get - no ADB
I am not able to check usb debugging because I can't get into the device.
The thing is obviously alive (although not as we know it) because windows install a driver for it when it is plugged in to the USB post. However it installs an MTP driver and I am not able to change this.
Any ideas anyone?
Thanks
Click to expand...
Click to collapse
It is possible that your system and/or boot partitions have become corrupted.
If that is the case, you'll need to reinstall the ROM. The best way to do this is to install a custom recovery like twrp or clockworkmod, reformat your partitions, and proceed from there.
Hi - thanks for this.
I got it sorted in the end.
Here's a link to what happened.
http://forum.xda-developers.com/showpost.php?p=60970017&postcount=1597