***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, so apparently I screwed up badly?
I have a LG G2 LG D805 and I was trying to install the CloudyG3 LP ROM, but I failed to see it was only for some variants, and mine wasn't included. Except I only noticed it after wiping System and, well, basically everything on my phone. So I'm getting the LG stuck screen, of course.
I can get into Recovery just fine, so I went to TWRP (that is still accessible) and:
* I tried adb push a new ROM on my phone, but I can't make my computer recognize my phone
*I tried adb sideload to the same effect (I get stuck on "Start SDB sideload feature..." and my PC doesn't recognize it)
Funny enough, my computer does makes the little USB connected sound? But when I list adb devices, the list is empty. Doing adb sub just says "device not found". I even changed cable/port, but nothing.
Then I tried to go to Download Mode and use LG Flash Tool to flash my phone but... I'm getting an error on the computer when trying to do that. I can still access TWRP though.
I'm scared of trying something else and making this worse? So if anyone could point me to a way of fixing my phone, I would be so so so grateful. :crying: please this is my only phone and I use it for work!
Nevermind, I managed to fix it
Hello guys, i've got really hard problem with my j5 which is probably totally bricked. But. there is but, i can access recovery mode and connect it to the ADB, but still, aint that easy. While trying to flash new ROM, im getting up to 40 % and its shows "e:signature verification failed" after that it gets to 92% and stops. Total xfer: 2.00x on phone it shows as "E:failed to find /misc partition".
I've been trying literally everything.
Weird thing, cannot open adb shell, "error:closed" been trying killing server, starting server etc.
Most weird thing is J5 CANNOT ACCESS THE "DOWNLOAD MODE" which is the biggest problem in my case.
apart from that, i've got no TWRP or CMW installd, only stock recovery mode, whatever option im trying to get into, always gets same info "E:Failed to find /misc partition".
what else... I've been trying to make SD card as bootable device with android on it, if you've got any ideas about that, im happy to hear.
been trying several rooms, stock, lineage, other customs.
Tried several versions of adb..
sometimes adb shows info "deamon not started" which after i've got communicate that deamon started succesfully and transfered to port 500 something.
Please guys, help me with that. I've wasted about 60 over hours now :crying: getting sick.
anyone that could help ?
tropicca said:
anyone that could help ?
Click to expand...
Click to collapse
Hi there
Are the OEM luck and usbdebuge enable?
Did you tried to flash pit file with Odin?
And how did you wanted to install stock rom without download mode?!(is there any way?)
And the last what did you do to get this?
amirizad_7436 said:
Hi there
Are the OEM luck and usbdebuge enable?
Did you tried to flash pit file with Odin?
And how did you wanted to install stock rom without download mode?!(is there any way?)
And the last what did you do to get this?
Click to expand...
Click to collapse
I was not the first person that touched the phone.
i dont know if they are enabled, no access to the android at all.
i've been trying to push custom rom/ twrp etc. through adb.
There are plenty of samsung tools that allows you to do it, but requires download mode... so thats the reason why I'm asking.
Look up usb jigs. You can make one easily enough with a couple resistors and a usb lead. Here is a guide on how to make one https://www.instructables.com/id/USB-JIG-to-give-life-to-your-Bricked-mobile/#step1
Or you can buy one on like a cheap site somewhere.
Once the jig gets plugged into the device it force boots the device into download mode and you should be able to continue from there
garylawwd said:
Look up usb jigs. You can make one easily enough with a couple resistors and a usb lead. Here is a guide on how to make one https://www.instructables.com/id/USB-JIG-to-give-life-to-your-Bricked-mobile/#step1
Or you can buy one on like a cheap site somewhere.
Once the jig gets plugged into the device it force boots the device into download mode and you should be able to continue from there
Click to expand...
Click to collapse
already 've got one, not working ;/ works perfect on j3 2016
Hi all; thanks for stopping by,
I've looked through multiple seemingly related threads but have been unable to find adequate answers and I am in way over my head to begin with, so please bear with me. Recently my LG G7 ThinQ became totally unresponsive so I figured I'd just use my old Moto G4 Plus while I work on fixing the G7. Problem is, the phone is locked and I have no idea what my swipe password is and I don't want to just completely wipe the phone as there is sentimental content on the phone which I'd like to access anyway.
The G4 Plus is OEM locked but I can access the bootloader, USB debugging is enabled, and I have an SD card. It is "athene_retail," operating on Android 7.0, and I do not have TWRP or CWM or the like installed on the phone. My PC is running Windows 10. Part of my problem is I'm not entirely sure how all this is supposed to work, but after hours of disorganized research I decided this thread was my best bet: https://forum.xda-developers.com/showthread.php?t=2620456 , so I have downloaded a lot of files and whatnot but am struggling with troubleshooting myself as I am likely not using them properly anyway. I tried the simplest-looking Methods -- 1 and 5 -- without success.
The problem I seemed to run into with Method 1 is at step #4 with "Apply update from ADB" and "Apply update from SD card" in Recovery Mode. What would happen is I'd "mount" the "/system" and proceed to choose one of the aforementioned "Apply update" options and the screen would just go black and then after a few seconds it would revert to a "No command" screen. Reading more into Method 1's instructions it seems like I might have to install TWRP or CWM onto my phone in order for this to work, but if that's right, how am I supposed to get them onto the phone if not through those options?
The problem I kept running into with Method 5 is "adb shell" would return "error: closed" and I haven't been able to determine why exactly. I opened cmd.exe from within the ADB folder and got "daemon started" and was able to attach device "emulator-5554" but after this point even "adb usb" would return "error: closed." I tried killing and restarting the server and a couple other potential solutions I found but to no avail. I am using
Code:
Android Debug Bridge version 1.0.41
Version 30.0.3-6597393
Any help would be greatly appreciated! :good:
hackmythinq said:
Hi all; thanks for stopping by,
I've looked through multiple seemingly related threads but have been unable to find adequate answers and I am in way over my head to begin with, so please bear with me. Recently my LG G7 ThinQ became totally unresponsive so I figured I'd just use my old Moto G4 Plus while I work on fixing the G7. Problem is, the phone is locked and I have no idea what my swipe password is and I don't want to just completely wipe the phone as there is sentimental content on the phone which I'd like to access anyway.
The G4 Plus is OEM locked but I can access the bootloader, USB debugging is enabled, and I have an SD card. It is "athene_retail," operating on Android 7.0, and I do not have TWRP or CWM or the like installed on the phone. My PC is running Windows 10. Part of my problem is I'm not entirely sure how all this is supposed to work, but after hours of disorganized research I decided this thread was my best bet: https://forum.xda-developers.com/showthread.php?t=2620456 , so I have downloaded a lot of files and whatnot but am struggling with troubleshooting myself as I am likely not using them properly anyway. I tried the simplest-looking Methods -- 1 and 5 -- without success.
The problem I seemed to run into with Method 1 is at step #4 with "Apply update from ADB" and "Apply update from SD card" in Recovery Mode. What would happen is I'd "mount" the "/system" and proceed to choose one of the aforementioned "Apply update" options and the screen would just go black and then after a few seconds it would revert to a "No command" screen. Reading more into Method 1's instructions it seems like I might have to install TWRP or CWM onto my phone in order for this to work, but if that's right, how am I supposed to get them onto the phone if not through those options?
The problem I kept running into with Method 5 is "adb shell" would return "error: closed" and I haven't been able to determine why exactly. I opened cmd.exe from within the ADB folder and got "daemon started" and was able to attach device "emulator-5554" but after this point even "adb usb" would return "error: closed." I tried killing and restarting the server and a couple other potential solutions I found but to no avail. I am using
Code:
Android Debug Bridge version 1.0.41
Version 30.0.3-6597393
Any help would be greatly appreciated! :good:
Click to expand...
Click to collapse
LMSA has a pin reset, you could try that.
https://forum.xda-developers.com/general/general/update-moto-lenovo-moto-smart-assistant-t3951714
Sent from my Moto E (4) using Tapatalk
hackmythinq said:
The problem I kept running into with Method 5 is "adb shell" would return "error: closed" and I haven't been able to determine why exactly. I opened cmd.exe from within the ADB folder and got "daemon started" and was able to attach device "emulator-5554" but after this point even "adb usb" would return "error: closed." I tried killing and restarting the server and a couple other potential solutions I found but to no avail. I am using
Code:
Android Debug Bridge version 1.0.41
Version 30.0.3-6597393
Any help would be greatly appreciated! :good:
Click to expand...
Click to collapse
"emulator-5554" ? This is a emulator and not your Moto G4. Are you using any emulator? If so, stop it and connect your G4.Once your G4 is connected to ADB, it should show your G4's Serial Number in list of devices attached.
[email protected]!$h said:
"emulator-5554" ? This is a emulator and not your Moto G4. Are you using any emulator? If so, stop it and connect your G4.Once your G4 is connected to ADB, it should show your G4's Serial Number in list of devices attached.
Click to expand...
Click to collapse
Thanks for the reply.
That did seem odd but I'm a noob, so I do have BlueStacks installed on my laptop but I don't believe it was even running at the time. Could that be it? In which case, that means my laptop wasn't even recognizing the phone at all to begin with? Hmm, ok, well I think I found the problem: when I click "adb.exe" a black screen (possibly cmd?) flashes on-screen for a tiny fraction of a second and that's it. Should it be doing something more than that? Does it have a GUI?
hackmythinq said:
Thanks for the reply.
That did seem odd but I'm a noob, so I do have BlueStacks installed on my laptop but I don't believe it was even running at the time. Could that be it?
Click to expand...
Click to collapse
Yes, it could be bluestacks. It's adb connection runs in the background.
In which case, that means my laptop wasn't even recognizing the phone at all to begin with? Hmm, ok, well I think I found the problem: when I click "adb.exe" a black screen (possibly cmd?) flashes on-screen for a tiny fraction of a second and that's it. Should it be doing something more than that? Does it have a GUI?
Click to expand...
Click to collapse
adb doesn't have any GUI and cmd flashing for a second is general behaviour when you run adb.exe. You should always run it from command prompt like you did before.
try installing Moto drivers : https://support.motorola.com/in/en/drivers
if already installed better try different port/cable/pc