So this is a new one for me,
So I removed some factory apps, the one in question being MOTOHOME.apk, (the home screen), as I prefer ADW and was making space.
However, a couple of days later I went to update ADW and there was an issue, ADW uninstalled and it wouldn't download so I recklessly restarted my phone without putting MOTOHOME back on and now my phone will not go past the motorola M, (as there is no homescreen app).
So I need a way to reinstall my factory apps so I can use it again.
Is there any update.zip I can apply to the SD card?
Thanks so much for the help guys,
appreciate it.
Related
First off I need to state that All of my experience with modding android devices is exclusively with the Samsung Vibrant.
A buddy at work just got the Motorola Droid-X for verizon.
I helped him out through the menus and settings and the standards of Android OS and the apps and yada yada yada.............
His phone is Stock and has never been rooted or modded in any way.
In seeing that My phone looked different I told him about home launcher replacements and that I was using Launcher pro. He wanted this for his phone as well and I installed it.
After I installed it I wanted to show him how to revert back to his original stock launcher (as i do on my vibrant) but to my surprise in pressing the home button it did not show me the choose launcher popup as my vibrant does.
I immediately went into settings/applications/manage applications/launcherPro to clear defaults and again to my surprise the clear defaults button was grayed out.
He is now having reboot issues he did not have before. He states he notices this when launcher pro rotates the home screen.
My questions for this forum is, (sorry it took so long)
How do I get his phone back to the stock launcher?
If I un-install Launcher pro,
Will I un-install the what seems to be the only home launcher and Brick his phone?
If I install a different launcher(Zeam) Will it possible give me the Choose default popup again?
I honestly did not think this simple install would cause this kind of issues.
I hate to think he needs to do a factory reset.
Please help me??
Big Dog KMc said:
First off I need to state that All of my experience with modding android devices is exclusively with the Samsung Vibrant.
A buddy at work just got the Motorola Droid-X for verizon.
I helped him out through the menus and settings and the standards of Android OS and the apps and yada yada yada.............
His phone is Stock and has never been rooted or modded in any way.
In seeing that My phone looked different I told him about home launcher replacements and that I was using Launcher pro. He wanted this for his phone as well and I installed it.
After I installed it I wanted to show him how to revert back to his original stock launcher (as i do on my vibrant) but to my surprise in pressing the home button it did not show me the choose launcher popup as my vibrant does.
I immediately went into settings/applications/manage applications/launcherPro to clear defaults and again to my surprise the clear defaults button was grayed out.
He is now having reboot issues he did not have before. He states he notices this when launcher pro rotates the home screen.
My questions for this forum is, (sorry it took so long)
How do I get his phone back to the stock launcher?
If I un-install Launcher pro,
Will I un-install the what seems to be the only home launcher and Brick his phone?
If I install a different launcher(Zeam) Will it possible give me the Choose default popup again?
I honestly did not think this simple install would cause this kind of issues.
I hate to think he needs to do a factory reset.
Please help me??
Click to expand...
Click to collapse
Settings -> Applications -> Manage Applications -> All -> Home -> Clear Defaults, not hard...
Go to the market and search for home switcher. That should do the trick.
Sent from my GT-I9000 using XDA App
You can also downlaod HomeSmack which is like Home Switcher but Homesmack is way better for Motorola phones. I downloaded it on my Droid X and it works best if you enable MotoHomeHelper on the app.
P.S. If you are getting an install error take out your SD card and try to download the app again. Then when the app is done downloading you can put your SD card back in your phone.
You can try any of the home switching apps that people have suggested... Or if you just uninstall the Launcher Pro app, his original launcher will return. I have done this several times on my X.
all you have to do is uninstall laucher pro
Launchers
Thank you all for your replies.
When I went to him to to preform the fix's He had already turned off rotate within launcher pro and it stopped his reboot issues, so now he is happy.
Thanks again to all.
I have an Optimus M from MetroPCS and I installed ADW. While playing around with the settings, I accidentally deleted the last home screen, so now I'm stuck in a Force Close loop for ADW. I can't get to the home screens (I guess there aren't any), I can't get to the ADW settings, etc. The only thing I can get to is the notification bar. So I can't bring up any programs or anything, including the terminal. USB debugging isn't enabled and I can't get to that setting to enable it, so I don't think I can use adb to help.
Is there anything I can do to get out of this loop? I used to know how to hack my way around a T-Mobile G1 (installing custom recoveries, roms, etc.), but with this Optimus M I don't even know how to flash the stock firmware back on it. I'm not sure how to do a factory reset, but I'm not even sure if that would work anyway, since I may have deleted the custom launcher that came with the phone and I don't know if it has the stock launcher (or any way to enable the stock launcher if the LG launcher isn't there).
Can I get to a terminal from the recovery console and delete the ADW settings file or something to get it to go back to default settings? I even have a good backup of good ADW settings I made before I made the changes but I can't get to a point where I can restore those settings.
Any ideas?
bjquinn said:
I have an Optimus M from MetroPCS and I installed ADW. While playing around with the settings, I accidentally deleted the last home screen, so now I'm stuck in a Force Close loop for ADW. I can't get to the home screens (I guess there aren't any), I can't get to the ADW settings, etc. The only thing I can get to is the notification bar. So I can't bring up any programs or anything, including the terminal. USB debugging isn't enabled and I can't get to that setting to enable it, so I don't think I can use adb to help.
Is there anything I can do to get out of this loop? I used to know how to hack my way around a T-Mobile G1 (installing custom recoveries, roms, etc.), but with this Optimus M I don't even know how to flash the stock firmware back on it. I'm not sure how to do a factory reset, but I'm not even sure if that would work anyway, since I may have deleted the custom launcher that came with the phone and I don't know if it has the stock launcher (or any way to enable the stock launcher if the LG launcher isn't there).
Can I get to a terminal from the recovery console and delete the ADW settings file or something to get it to go back to default settings? I even have a good backup of good ADW settings I made before I made the changes but I can't get to a point where I can restore those settings.
Any ideas?
Click to expand...
Click to collapse
Keep pressing home key and check if you have market running. If so, go there and install ADW launcher again or launcherPro
Thanks for the suggestion. In my case, I couldn't get the little "running apps" view to show up while holding down the home button either, but I was able to get to the market a different way. I don't know how many other people will run into this exact issue, but I've fixed it, and here's what I did for posterity's sake.
1. Get out of the force close loop. The way I did this was to pull down the notifications bar and I happened to have Cardio Trainer running in there so I could get to some program OTHER than the launcher itself so the home screen wasn't attempting to load. If you don't have anything running in your notification bar, you might send yourself a text message so you can get in the messaging app through the notification bar.
2. Press and hold the search button, this brings up voice search. Say something (anything), which will bring up a Google search.
3. Now search for ADW Launcher. What you're looking for is a site that will offer you a "download" link, which will load the Market.
4. Uninstall the launcher and immediately reinstall it. Fortunately, ADW wipes out its settings when you do this, and all should be back to normal.
5. Don't delete your last home screen again. In my defense, I clicked the little X to delete my last home screen just to see what it would say, and figured it was safe since it always asked me to confirm before deleting the other home screens. Nope, it just killed ADW forever instead. Lesson learned.
Hi All, Help needed. My Sensation XE phone updated to ICS a few days ago, stock unrooted. Since the update I can't add any widgets to the home screen, and have difficulty adding Apps too .
If I long hold on home screen space, I can choose an App or widget but once selected I get thrown out to the centre home screen without success (even if I was on a different screen).
I am able to pin an App from the App drawer route, but can't get widgets from any method. Existing widgets work fine, but can't add any new ones, not even HTC ones.
I raised a support query with HTC, they said it is a "software glitch", and to do a factory reset. I really don't want to do this, I don't want to go through setting everything up again. And as I'm NOT rooted will lose App and game data. As I have a stock unrooted phone I'm not even convinced a reset will solve the problem.
Has anyone got any ideas on how to solve this or a work around?
1) Root the phone. It's super easy and you'll end up with the ability to back up all your stuff.
but if that's not for you...
2) Get a different launcher. (ADW is nice. Go Launcher is popular. Both are available on the market. Both are free.)
You'd have to reset up your home screens, but all of your data and system settings could be uneffected. And I'd bet that your problem goes away with a new launcher.
I may be forced to root, but not ready to go down that road yet. I like the simplicity and security of stock. And if things are going wrong with a stock phone I don't really want to venture into more complexity.
I may try another launcher but again I actually like Sense UI.
I thought there could be a service or program I could restart that would solve my problem. I get the feeling HTC customer service just get everyone to reset at the first sign of trouble.
allupnow said:
I get the feeling HTC customer service just get everyone to reset at the first sign of trouble.
Click to expand...
Click to collapse
There's a very good reason that you get that feeling
Factory resetting will fix 99% of software issues that the average dolt causes by doing something goofy. So they recommend it as the go to solution.
Try this.
Go to the settings. Select apps, then "All" instead of 'downloaded'. Find the launcher and clear the settings. If it works it'll clear off all your home screens. But it should reset the application so it'll work like the first day. You won't lose data or anything, just the placement of your icons. I don't know if it'll work without root though.
As for rooting, you can root the phone and keep the stock ROM. You don't have to change anything or install different ROM's. You'd just have the ability to tweak more of the stock ROM if you needed to, and the ability to fix more problems that you're locked out of now .
And there's a chance that wiping the dalvik and cache once you're rooted would fix the problem you're having with the launcher if the 'clear settings' option doesn't work.
hey, 1. confirm that your ROM originally includes those widgets...
2. go to setting-apps-all-htc sense-clean cache-reboot...
Thanks for your help guys. I found the problem which was a troublesome app that worked fine under gingerbread, but not happy with ics. Quickest. Removed it and problem went away.
Issue resolved - uninstalling certain applications was the solution!
allupnow said:
Thanks for your help guys. I found the problem which was a troublesome app that worked fine under gingerbread, but not happy with ics. Quickest. Removed it and problem went away.
Click to expand...
Click to collapse
While I tried almost all the solutions mentioned above, this solution worked for me. I removed all the previously installed applications, that were installed before moving over ICS. Somehow, I couldn't narrow down to the exact application that was causing the problem.
Uninstalling these applications resolved the issue and now I am able to add widgets to HomeScreen.
Thank you very much all of you for your help and suggestions.
being a noob to Android after years of BlackBerry, but LOVING the Android freedom, I rooted my HTC Sensation 4G (not all that easily, I might add). In trying to remove bloatware, I deleted the stock Android default lockscreen, thinking that it was superfluous since T-Mobile/HTC had included the HTC lockscreen. What I failed to realize was that apparently the HTC one works on top of the default one (I even "quarantined" the deleted one before fully removing, and it still functioned fine, but must have been from cache or something because it no longer did after reboot). So, now no lockscreen comes up at all, no ring tab to pull, just a blank screen of wallpaper, effectively meaning I've bricked my phone. I'm hoping that I can do some kind of restore, perhaps an apk I could load from my PC onto my phone's SD card, or alternatively have some kind of recovery whereby I don't lose everything, programs and data such as contacts. I do have a Clockwork backup on the SD from a month or so ago, and can get my HBOOT menu offering me both factory reset and Recovery options, but not sure what I might lose doing either of those. Still learning Android, not even sure of terms like SuperCID and ICS, though reading much as I can to learn. I am looking for suggestions as to how I might recover just my lockscreen, or failing that, the best path to recovery after some sort of restoration. Have never yet flashed a ROM or done anything with firmware, but maybe this is the time since I may have nothing to lose, in a sense, don't know about either of those processes but want to learn and do.
reply to myself
OK, seeing as nobody came to my info rescue, I'll post to myself in case it helps somebody in the future. Finally just got brave enough to push some buttons, and came out smelling like a rose. Did the HBoot via power button together with down volume after battery pull, chose Recovery, then Advanced, and then chose to just recover the System only from the one available recovery. Worked like a charm. Phone no longer rooted, but I'm going to try the OTA of ICS anyway and eventually re-root after that. Know I will have to flash stock recovery to replace the CWM (Clockwork) one that allowed me this recovery, as OTA ICS requires stock recovery, but that doesn't sound like a problem.
Hey,
I purchased a used Nexus 5, 32GB edition (I think the model is D821) as my then current phone (a Samsung Galaxy S4) somehow had a magically broken screen after setting it down on a bed. I have since been able to access my old phone, but it isn't usable as a daily handset.
Anyways, wen I first obtained this phone, I wanted to be safe so I unlocked the bootloader, downloaded the necessary tools to use adb/fastboot, wiped the phones storage, and then flashed the latest version 5.0.1 LRX22C. After installing the normal things I had on my old phone and rooting the device, I have noticed that I get an absurdly abnormal amount of force closes. Mainly dealing with the launcher.
On a daily basis, the launcher, and it seems to mainly ONLY be the launcher (either Google Launcher or Nova, it isn't application specific) force close, freeze, or become unresponsive. I can come to this conclusion on the following basis:
1) The launcher screen shows the background, but doesn't show the dock or any of the shortcut/widgets on the launcher
2) All I can see is a black screen and the notification bar/tab. This is sometimes evaded by switching to the recent apps button and then switching back using the home button.
3) It will show the screen with all applications, but won't swipe between home screens.
There is no major physical damage to the device, there is a hairline crack from the previous owner.
I am guessing that I could go through the process of downloading the firmware and reflashing it, but I was wondering if anyone had ideas on how to solve it, besides flashing the device immediately. I don't want to go through the hassle of flashing firmwares and setting up a device again, especially during finals week. The problem is annoying enough that it would make me post this, but not annoying enough to spend an entire afternoon dealing with that and re-configuring applications and such.
Thanks for the help in advance.
slixzen said:
Hey,
I purchased a used Nexus 5, 32GB edition (I think the model is D821) as my then current phone (a Samsung Galaxy S4) somehow had a magically broken screen after setting it down on a bed. I have since been able to access my old phone, but it isn't usable as a daily handset.
Anyways, wen I first obtained this phone, I wanted to be safe so I unlocked the bootloader, downloaded the necessary tools to use adb/fastboot, wiped the phones storage, and then flashed the latest version 5.0.1 LRX22C. After installing the normal things I had on my old phone and rooting the device, I have noticed that I get an absurdly abnormal amount of force closes. Mainly dealing with the launcher.
On a daily basis, the launcher, and it seems to mainly ONLY be the launcher (either Google Launcher or Nova, it isn't application specific) force close, freeze, or become unresponsive. I can come to this conclusion on the following basis:
1) The launcher screen shows the background, but doesn't show the dock or any of the shortcut/widgets on the launcher
2) All I can see is a black screen and the notification bar/tab. This is sometimes evaded by switching to the recent apps button and then switching back using the home button.
3) It will show the screen with all applications, but won't swipe between home screens.
There is no major physical damage to the device, there is a hairline crack from the previous owner.
I am guessing that I could go through the process of downloading the firmware and reflashing it, but I was wondering if anyone had ideas on how to solve it, besides flashing the device immediately. I don't want to go through the hassle of flashing firmwares and setting up a device again, especially during finals week. The problem is annoying enough that it would make me post this, but not annoying enough to spend an entire afternoon dealing with that and re-configuring applications and such.
Thanks for the help in advance.
Click to expand...
Click to collapse
How did you install the stock firmware? Have you tried wiping cache and dalvik cache in recovery? I'd do that first, and if that doesn't work then try dirty flashing the same ROM (you won't lose anything). If you are still having issues after then flash a factory image with fastboot (do NOT use a toolkit). That should fix it.
_MetalHead_ said:
How did you install the stock firmware? Have you tried wiping cache and dalvik cache in recovery? I'd do that first, and if that doesn't work then try dirty flashing the same ROM (you won't lose anything). If you are still having issues after then flash a factory image with fastboot (do NOT use a toolkit). That should fix it.
Click to expand...
Click to collapse
I know this is a very late response.
The initial way that I installed the stock firmware was using fastboot, and installing each .img file separately.
I just re-flashed the factory image again (except for the recovery image), and am waiting for the phone to boot up (it seems like it takes ages for the phone to actually go from fresh install to fully booted), it has been over a 5 minutes now.
But once that is done, I will see what happens. Is there a way to check for bad hardware (I am specifically thinking flash storage)? Maybe that is causing the problem?