HELP - Droid X General

I was changing some files in the framework-res.apk and when I reinstalled, the phone starts up and when I unlock its just blank. On the notification bar I can access Folder Organizer lite and thats all. Any help would be helpful because my pc cant recognize it anymore otherwise I would adb it back to normal.
Update: Now I tried rebooting it again and now its stuck in a boot loop. Is there anyone that can create and update.zip from a stock 2.1 droid x that will install all the data, and system files so I can get it back up and running?

Push the original framework.apk back to your phone.

I cant cause it doesnt connect via PC. The usb output wont register on my PC. And now I cant because its stuck in a boot loop

Follow the sbf flash guide here
http://rootzwiki.com/index.php/Smartphones/Motorola/Droid-X/Droid-X.html
It will restore your phone back to factory, keep your settings, and will unroot you if you rooted (you can root again though)

OMG THANK YOU SO MUCH!!!! This is why I love the Android community.

Related

Any advise?

I recently upgraded my G1 to the cyanogenmod 2.1 ROM and everything went fine untill i went to the market and installed a program called ROM manager. while i was using ROM manager it had an option, i cant remember what its name was, that said it fixes FC's if needed. Well i was getting those in ROM manager so i clicked it. It did a bunch of stuff and then suddenly tossed an error at me. Next thing i know im getting LOTS of FC's and when i rebooted my phone im suddenly stuck staring at the G1 boot screen and thats where it stays......indefinetly.
I cant get into recovery mode, already tried that. And so far the only thing(that i know of) that i can do is get into fastboot. Does anyone know how i can fix this? Its gotta be software related from whatever that ROM Manager program did to my permissions. But now im basically bricked and cant do anything.
My storage card still has all of the ROM's and files from when i flashed last but i dont know if or how i can use that to re-flash my phone again and start over.
Any suggestions?
I had a similar issue just yesterday. Dowloaded rom manager from the marketplace - attempted to flash recovery - pulled an error and ended up on the G1 screen. Could not get into recovery, but fastboot was available.
I followed these instructions
( reboot holding camera button, connect usb and press back button )
on pc
HTML Code:
fastboot erase system -w
fastboot flash recovery <recovery.img>where <recovery.img> is the full path to the recovery you want to flash
I had to do a full erase in fastboot - that is the first line of text above, I then flashed my recovery.img again - that is the second line of text above (I placed my recovery.img file directly in the adb folder - so it easy to find )
Once I was able to get back into recovery - I restored my last back-up, and the phone booted once again.
If you do not have any backups - I am not aware of the next step. Hopefully someone with more experience can direct you accordingly
Good luck
How is it that you send the commands? I plug in my USB, then hit back and it says FASTBOOT USB but how do i input the HTML codes to get it to do anything?
Do i make an HTML file on the pc and upload it, if so, how? I understand all of it except how to get the commands into it.
Well that and what the full path will be for the recovery.img.
well i feel like a total moron !!! lol
I had been being a script kiddie for the last few years and forgot my roots. I got it figured out and got the commands sent to fastboot in a CMD prompt.
Ugh, i gotta stop using google so much and finding all the easy ways out of things that others have already written.
Thanks for the help, much appreciated and worked a treat. I flashed everything and its working great again

Nexus 7 Stuck in Boot Animation Loop--Please Help

***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.

[Q] Stupidly bricked phone, need ADB push

Hello XDA,
I stupidly put my G2 in bootloop. It is 802, 20h, stock rom/recovery and rooted with ioroot.
I managed to break it by removing the LGweather.apk and LGslideaside.apk from system app because I was tired of seeing them taking memory for no reason. After a reboot, it is blocked at LG logo.
I have made a nandroid backup some time ago through an app so I have those APK on my computer, I just need to put them back with adb.
I can get it to download mode (picture here http://forum.xda-developers.com/showpost.php?p=58181792&postcount=4), but I can't get adb to detect the device although I tried many drivers.
My question are: Am I losing my time by trying to have adb work or it is a driver problem and it will eventually be able to push the file if I can have the phone recognised by adb?
Should I try the hard reset offered through the keys combination? I am very much afraid it would make it worse as I changed many things in the phone through xposed.
Thanks a lot in advance for your help.
Flash the SAME rom via lg flash tool (choose normal mode because it doesn't touch your files)
bender_007 said:
Flash the SAME rom via lg flash tool (choose normal mode because it doesn't touch your files)
Click to expand...
Click to collapse
Well I would have prefered not to, but as I couldn't get adb to work and the hard reset only brought me back LG sound when bootlooping, I had to.
It worked wonderfully, thanks. I have to try to get root back now (even if it shows as rooted in download mode).
The rooted is more like cosmetic

[D802] Download mode is not working with FlashTool2014 - SOLVED

Hi,
I'm opening a thread because I just couldn't find any way to unbrick my device. In the past I used the FlashTool2014 to go back to the stock LP KDZ for my device.
I was in the stock rom when I decided to mess with the build.prop and then went back to the stock backup. When I restarted the phone it showed the LG logo, screen went black and never booted android. I could access the stock recovery but the Factory Reset won't work.
Then I decided to go to download mode, it connects and the PC detects it as an MTP device. I open the FlashTool2014 and it detects the device OK. When the LGUserCSTool opens it says the Upgrade stopped due to an error and the device stays on 0% and shows USER B70 in the console. I can press Retry, turn off the phone and reconnect in Download mode but the LGCSTool just wont push the firmware.
I suspected I had a driver issue so I tried using a clean win8 install I have for this purposes without success. I cant flash with the TOT method since the other LG Flash Tool wont detect the device in download mode when connected to the pc. This is really weird.
Any ideas ?
Thanks in advance.
EDIT: Solved with another tot file (almost lost all hope), took me 20+ hours to download it, I'll better make a backup of this files on the cloud. Still having problems with STOCK firmwares but could install TWRP and get CM13 which doesn't give any problems.
lg g2
ZareliMan said:
Hi,
I'm opening a thread because I just couldn't find any way to unbrick my device. In the past I used the FlashTool2014 to go back to the stock LP KDZ for my device.
I was in the stock rom when I decided to mess with the build.prop and then went back to the stock backup. When I restarted the phone it showed the LG logo, screen went black and never booted android. I could access the stock recovery but the Factory Reset won't work.
Then I decided to go to download mode, it connects and the PC detects it as an MTP device. I open the FlashTool2014 and it detects the device OK. When the LGUserCSTool opens it says the Upgrade stopped due to an error and the device stays on 0% and shows USER B70 in the console. I can press Retry, turn off the phone and reconnect in Download mode but the LGCSTool just wont push the firmware.
I suspected I had a driver issue so I tried using a clean win8 install I have for this purposes without success. I cant flash with the TOT method since the other LG Flash Tool wont detect the device in download mode when connected to the pc. This is really weird.
Any ideas ?
Thanks in advance.
EDIT: Solved with another tot file (almost lost all hope), took me 20+ hours to download it, I'll better make a backup of this files on the cloud. Still having problems with STOCK firmwares but could install TWRP and get CM13 which doesn't give any problems.
Click to expand...
Click to collapse
enjoy:good:

Totally ****ed up p9 lite

Hi,
Oke i will save you most of the details which is normally not the best part but i think it doesn't matter how i got here anymore. Basically i tried to update my phone to nougat. So i installed TWRP. Before i could install that i had to unlock bootloader and my phone which i did. After that i succesfully installed TWRP and directly my problems started...
I couldnt get my phone booted into recovery. Finally after hours spending i managed to hook it up on the adb tools via the command line. Long story short, the only thing my phone does right now is boot, where i get the warning that my device is unlocked. If i do a normal boot, nothing happens, if i go to fastboot i can do nothing there because my PC doesn't see the device anymore. I cant use HiSuite to recover it because it shows me a warning that i dont have right for support. When i go to erecovery and connect to my wifi and recover the phone, the package info always fails.
So is there anything i can do to get my phone back to work? Because i am really out of options, somehow sometimes i managed to get into that "installing update" part but appearantly the file in my dload is not the right version so the update always fails.
What to do i? I am really about to smash my phone because i am so mad at myself that i bricked my dive :crying:
Try to get the right firmware for your device or if you remember your old one.
Flash stock recovery and then lock your bootloader also.
Put the firmware inside of your sd card and make a folder called 'dload' push the update.app there inside and make the 3 button way
Good luck.
And if its gonna end badly, Huawei have a VIP service which they will repair it for free IF it is still under warranty.
https://forum.xda-developers.com/hu...huawei-p9-lite-firmware-compilations-t3517124
Get correct firmware from this page & put update.app in dload folder
if you can boot into fastboot, the pc should be able to see it. have you tried looking into device manager to see if the driver is working?
anyway, if you were on stock marshmallow, you should be able use the 3 button combo to reflash the stock rom. after that the phone should be in factory state, with stock recovery and locked bootloader (eventhough in fastboot it still says unlocked).

Categories

Resources