I have a rooted Droid X that already has the 2.3.340 from the original ota. I have have been having a lot of issues with the X recently, with random reboots, lock ups, and just extremely slow. I was trying to find something I can do to possibly fix this issue, without doing a full factory reset and wiping my whole phone. I tried the system only 2.3.340, rebooted into recovery, wiped cache, and it's stuck on "Installing update"
briankeith513 said:
I have a rooted Droid X that already has the 2.3.340 from the original ota. I have have been having a lot of issues with the X recently, with random reboots, lock ups, and just extremely slow. I was trying to find something I can do to possibly fix this issue, without doing a full factory reset and wiping my whole phone. I tried the system only 2.3.340, rebooted into recovery, wiped cache, and it's stuck on "Installing update"
Click to expand...
Click to collapse
I know you said you did a factory reset, but try pulling the battery, then booting into recovery again, and doing another wipe... Then try another install. I have had to wipe 2x before when installing ROM's or updates.
briankeith513 said:
I have a rooted Droid X that already has the 2.3.340 from the original ota. I have have been having a lot of issues with the X recently, with random reboots, lock ups, and just extremely slow. I was trying to find something I can do to possibly fix this issue, without doing a full factory reset and wiping my whole phone. I tried the system only 2.3.340, rebooted into recovery, wiped cache, and it's stuck on "Installing update"
Click to expand...
Click to collapse
Since you already have .340, a factory reset is best. Don't mess around with SBF or anything like that unless you have to or you've soft bricked your phone. You will have to backup all your apps and what ever else you want saved on your SD Card. If you don't have a lot of patience to back up the apps, Android Market has a list of your downloaded apps at android.market.com under My Market Account and you can just re-download them from there to your phone through Google. ( live as of yesterday, so cool! )
There are no good solutions in your case for what you want to do. You’re going to save a lot of headache and time wasted by just taking the time to factory reset your phone now rather then trying to find jerririgs. Some of your system files are probably corrupt.
You can flash the 2.3.320 full sbf while on .340. I've done it. Then you can re-root and flash the maderstcok.zip to get to full .340.
Related
I have been having this issue ever since my phone booted up and all my apps sequentally had force close dialogs happen. I am running my apps from the SD and figured something went wrong with the boot up sequence. I tried doing a nandroid backup, reinstall fresh 1.1, but no luck.
I then used my backups to reinstall over all my apps, then went into Market to install them via that. Everything seemed to be just fine, but the phone app would still not dial anything and when I recieved a call, it gives the error "The process com.android.phone has stopped unexpectedly" and then proceeds to try to reset the phone connection. Most times I lose all data connection and need to reboot.
Recently, I tried installing the latest Modoco CDMA rom. No luck. I then did a Titanium backup and force reinstalled everything again. Still no luck.
Anyone have this issue and get it resolved? My Hero can do everything but make and accept calls. I really don't want to do a wipe as this problem can just happen again, so I would rather understand the process.
Thanks in advance.
Ceger
Simplest way to fix this should be clearing the dalvik/boot cache from fresh's kitchen. I really should write up a guide on how to do these simple tasks manually.
obelisk79 said:
Simplest way to fix this should be clearing the dalvik/boot cache from fresh's kitchen. I really should write up a guide on how to do these simple tasks manually.
Click to expand...
Click to collapse
Will that work on MCR 2.2 as well? I'll look into that. Is it something I can do from recovery?
Ceger
yes should work on mcr 2.2 and can be done manually from recovery, I know recovery does dalvik cache, not sure if it also kils the boot cache as well though. The older version only did dalvik.
obelisk79 said:
yes should work on mcr 2.2 and can be done manually from recovery, I know recovery does dalvik cache, not sure if it also kils the boot cache as well though. The older version only did dalvik.
Click to expand...
Click to collapse
Do you need to do both? Wiping the dalvik cache created lots of app fc issues, which would be fine if the phone actually worked. Still won't make or receieve calls.
And thank you for the assistance.
Ceger
Edit. Clearing the boot cashe got rid of the FC issues. However, still have same issue with the phone app. This is so annoying.
honestly the best bet to clear up the issues would be to do a full wipe from recovery. Wipe the phone clean then run the stock RUU and re-root and install your custom rom. Do a nandroid backup first just to prevent losing any of your info.
Unfortunately despite the many well written guides here on XDA there are always a few issues most likely a result of slight hardware quirks or unfortunate circumstances at the time of flashing.
Just for '****s and giggles' have you tried pulling your battery for 30 seconds, reinstalling it and booting the phone up?
Heck sometimes just a reflash of the rom right over top of itself. I've been tinkering with this phone since the day root came out and I still don't fully understand all of it's quirks.
Ceger said:
I have been having this issue ever since my phone booted up and all my apps sequentally had force close dialogs happen. I am running my apps from the SD and figured something went wrong with the boot up sequence. I tried doing a nandroid backup, reinstall fresh 1.1, but no luck.
I then used my backups to reinstall over all my apps, then went into Market to install them via that. Everything seemed to be just fine, but the phone app would still not dial anything and when I recieved a call, it gives the error "The process com.android.phone has stopped unexpectedly" and then proceeds to try to reset the phone connection. Most times I lose all data connection and need to reboot.
Recently, I tried installing the latest Modoco CDMA rom. No luck. I then did a Titanium backup and force reinstalled everything again. Still no luck.
Anyone have this issue and get it resolved? My Hero can do everything but make and accept calls. I really don't want to do a wipe as this problem can just happen again, so I would rather understand the process.
Thanks in advance.
Ceger
Click to expand...
Click to collapse
use these commands to clear cache
rm -r /data/boot-cache/
rm /data/dalvik-cache/
once you finish then reboot.everything should go away...
he's done that already.
then i suggest to extract the rom zip file, and get into command on your device and go under the system/lib or app and see what is listed in the folders. and compare it to the rom folder.
That's how i was able to fix the voice search on my device, one of the lib file was missing and got it to work after that.
obelisk79 said:
honestly the best bet to clear up the issues would be to do a full wipe from recovery. Wipe the phone clean then run the stock RUU and re-root and install your custom rom. Do a nandroid backup first just to prevent losing any of your info.
Unfortunately despite the many well written guides here on XDA there are always a few issues most likely a result of slight hardware quirks or unfortunate circumstances at the time of flashing.
Just for '****s and giggles' have you tried pulling your battery for 30 seconds, reinstalling it and booting the phone up?
Heck sometimes just a reflash of the rom right over top of itself. I've been tinkering with this phone since the day root came out and I still don't fully understand all of it's quirks.
Click to expand...
Click to collapse
Done and done and no difference.
reddick said:
then i suggest to extract the rom zip file, and get into command on your device and go under the system/lib or app and see what is listed in the folders. and compare it to the rom folder.
That's how i was able to fix the voice search on my device, one of the lib file was missing and got it to work after that.
Click to expand...
Click to collapse
Done, even manually moved some files in case they were corrupted at one point. Very bad move, nandroid backup was my friend there.
Guess a wipe will be the only option then. How annoying.
Thanks for all of your inputs.
Ceger
Another thought... would updating my phone with latest kernal compile possibly do the trick? Or how about a replacement process for google.com.phone?
Ceger
Interesting theory.... worth a try.
i had this issue once and it was because of somehow the uids for the apps got messed up. a wipe should fix this in most cases. but for me it went like ur issue. i almost event went back stock. then i looked into it and found that in my packages.xml file the the uids were all messed up. i had multiple uids and certs for the apps i was having issues with. so what i did was pulled the packages.xml from the device and erased the apps i was having issues with. then pushed it back and rebooted. that cleared the issue. so if i were u i would research that. do a google search on it. then if it doesnt work do the ruu and reroot. good luck man. i know how u must be feeling. i was there
toastcfh said:
i had this issue once and it was because of somehow the uids for the apps got messed up. a wipe should fix this in most cases. but for me it went like ur issue. i almost event went back stock. then i looked into it and found that in my packages.xml file the the uids were all messed up. i had multiple uids and certs for the apps i was having issues with. so what i did was pulled the packages.xml from the device and erased the apps i was having issues with. then pushed it back and rebooted. that cleared the issue. so if i were u i would research that. do a google search on it. then if it doesnt work do the ruu and reroot. good luck man. i know how u must be feeling. i was there
Click to expand...
Click to collapse
Actually, the fix was much simpler. I wiped the SD ext partition and just did a Recovery Wipe. It went back to stock modded rom that remained rooted. I then used Titanium to reinstall my apps with data and then MyBackup to get back some settings such as my scenes, etc. and all was good. Took all of 30 minutes to get my Hero back up and running in better condition than before.
Thanks all for the assists.
Ceger
com.android.phone
com.android.phone
i am facing this prob on cyanogen mod10....when ever i reboot my optimus 2x....i face this damn problem
help plzzzzzzzzzz.....!!!!!
I literally cant do a damn thing with my Droid 2. This all started when I started noticing an increasing number of Force Close popups. I hadn't installed anything new recently so I just rebooted and dealt with it. At this point, it was a completely stock Droid 2 with only market-approved apps installed.
So, I decided to do a factory restore and... it didnt work. It sat at the recovery screen and did nothing. I pressed search and selected wipe data\cache and it said something to the effect of "Cant open E:\recovery\something" but the Wipe data\cache completed successfully. Needless to say, my issue remained.
So I found the stock recovery SBF and went to flash it... it got to 98% on the final step and then said FAIL. Error message: Failed flashing process. Error verifying Code Group 31 checksums. File 0x4BAF (0x4007031); phone connected. The phone still show SW Update when this occurs, and then eventually "completes", reboots, and boots back up as if nothing ever happened.
So then I tried the root process so I could install rom manager and try EUnleashed or something. The rooting steps all took, and I tried to open the Superuser app it just stuck on a blank screen. So I rebooted, and wtf.. it disappeared.
So then I went to Applications and uninstalled every single application except for Maps, rebooted, and WTF THEY ALL CAME BACK AGAIN. I did this 3 times and each time every single app was reinstalled and working after a reboot. Only now I cant complete the root process again, and Rom Manager doesnt work.
So, to recap... I cant do a factory restore. I cant flash the stock SBF. I cant root. I cant do f*$&#*$ ANYTHING!
If I cant fix this today I will be giving this junk phone to my 2 year old because that's about the only thing this POS is good for. I never had any of these issues on my Droid, Droid X, or Samsung Captivate. How Motorola could fail so hard while simultaneously succeeding so well with other devices is mind-boggling.
HELP!
lwright84 said:
I literally cant do a damn thing with my Droid 2. This all started when I started noticing an increasing number of Force Close popups. I hadn't installed anything new recently so I just rebooted and dealt with it. At this point, it was a completely stock Droid 2 with only market-approved apps installed.
So, I decided to do a factory restore and... it didnt work. It sat at the recovery screen and did nothing. I pressed search and selected wipe data\cache and it said something to the effect of "Cant open E:\recovery\something" but the Wipe data\cache completed successfully. Needless to say, my issue remained.
So I found the stock recovery SBF and went to flash it... it got to 98% on the final step and then said FAIL. Error message: Failed flashing process. Error verifying Code Group 31 checksums. File 0x4BAF (0x4007031); phone connected. The phone still show SW Update when this occurs, and then eventually "completes", reboots, and boots back up as if nothing ever happened.
So then I tried the root process so I could install rom manager and try EUnleashed or something. The rooting steps all took, and I tried to open the Superuser app it just stuck on a blank screen. So I rebooted, and wtf.. it disappeared.
So then I went to Applications and uninstalled every single application except for Maps, rebooted, and WTF THEY ALL CAME BACK AGAIN. I did this 3 times and each time every single app was reinstalled and working after a reboot. Only now I cant complete the root process again, and Rom Manager doesnt work.
So, to recap... I cant do a factory restore. I cant flash the stock SBF. I cant root. I cant do f*$&#*$ ANYTHING!
If I cant fix this today I will be giving this junk phone to my 2 year old because that's about the only thing this POS is good for. I never had any of these issues on my Droid, Droid X, or Samsung Captivate. How Motorola could fail so hard while simultaneously succeeding so well with other devices is mind-boggling.
HELP!
Click to expand...
Click to collapse
I think you might be overreacting here.
First, I haven't flashed the SBF yet but I do remember seeing the fail screen on original Droid SBF flashes and it was something you could ignore. You booted back into Android, right? That means it worked.
Second, the Superuser app is supposed to show a blank screen because the purpose of it to manage apps to which you have granted to superuser permissions. If you just installed it, there would be nothing listed.
Third, Froyo restores apps if you have "back up my data" checked under Privacy settings.
Fourth, you never mentioned the Droid 2 bootstrapper. I wouldn't expect ROM Manager to work properly without it.
First, no that doesnt mean it worked. I boot back into my exact same Android install as before. Same settings, same notifications, same alarm, same problems, same everything. If it was successful, it would be like a factory restore (Which I cant even do).
Second, ok that makes sense. But after rebooting it disappeared and RomManager wouldn't recognize that it was rooted. Now the rooting process wont work at all when I try and redo it.
Third, I dont think this is the same thing. It's not restoring apps... the apps are there as if they were never removed. Same customizations, settings, etc.
Its like my D2 is stuck with a certain "image" on it, and it wont let me edit, delete, format, reinstall, or reimage. It's infuriating.
Also, ROM Manager works without bootstrapper as long as you have Superuser. Ive used it fine on my Captivate.
lwright84 said:
First, no that doesnt mean it worked. I boot back into my exact same Android install as before. Same settings, same notifications, same alarm, same problems, same everything. If it was successful, it would be like a factory restore (Which I cant even do).
Second, ok that makes sense. But after rebooting it disappeared and RomManager wouldn't recognize that it was rooted. Now the rooting process wont work at all when I try and redo it.
Third, I dont think this is the same thing. It's not restoring apps... the apps are there as if they were never removed. Same customizations, settings, etc.
Its like my D2 is stuck with a certain "image" on it, and it wont let me edit, delete, format, reinstall, or reimage. It's infuriating.
Also, ROM Manager works without bootstrapper as long as you have Superuser. Ive used it fine on my Captivate.
Click to expand...
Click to collapse
Captivate is not a Droid 2. I'd be surprised if it works without the bootstrapper, since that's the only way to flash anything on a Droid 2.
My suggestion is to keep trying the SBF. Once you get it to work, get the SW update and then root. From there, I wouldn't go messing with anything in ROM Manager until you confirm the files are 100% legit for the Droid 2. As far as I know, only a few themes are working without issue on the Droid 2 - the ROMs all have bugs.
The same thing happened to me. I am assuming we were using the same instructions to flash the .sbf. Here is a link to instructions I followed.
http://forum.xda-developers.com/showthread.php?p=8245826#post8245826
I did not heed the red flag I got when I unzipped the .jpg file. I saw some error message and ignored it, and went ahead with the procedure to end up as many others with "fail".
Long story short, I deleated the .jpg file and downloaded it again.
When I used 7 Zip to extract the files, this time I had no error msg and everything went smoothly.
If a moderator can remove this thread, please go ahead!
I dug deeper into fallingup's recovery thread. It never occurred to me that it might make a difference to clear cache and factory reset AFTER doing an update. I did that, which seemed to clear up my FC loop. I fell into a page that asked me what language I was speaking, and was prompted to set up my google account -- which failed. Couldn't connect to data services, not even WIFI. So *228 and Activated my phone (again). Google still wouldn't log in. Went to Settings/Privacy/Factory reset. Selected English, google logged in this time. My phone appears to be completely back to its original stock state. Root is gone. Even bing is back, lovely. Thanks angel12!
... now if I could just figure out why that update.zip paired with the modem.tar that started all this wouldn't sing for me in recovery mode.
>>>>>>>>>>>>>>>>>>
First off, I apologize for cluttering this forum, but I'm at a bit of a loss here. I also failed to find the server for IRC. I'd really appreciate a small push.
Here goes: I got into download mode from the command line. I flashed over my modem with Odin, got a PASS, rebooted fully (shouldn't have done this) with no errors. Next, I popped into recovery mode. From there, I decided to factory reset _and_ wipe my cache -- it seemed like a good idea at the time. It seems like a bad idea now. Finally, I told recovery to apply update.zip from my sdcard. It flat out refused! Complained that the .zip wasn't signed. So, I rebooted.
I then experienced my first FC loop! The culprit is TouchWiz launcher, which just repeatedly closes unexpectedly.
So then I restored the DI01 modem, which didn't change a thing. Next, I ran Stock-i500-VZW-System.tar.md5 through Odin. It updated with no problems.
However, I still have my Force Close Loop, which I expected going to stock would fix.
What I think is really going on is I'd been using ADW Launcher, coupled with an app that switched it to being the 'default'. Something somewhere, must be giving TWiz a hard time.
The good news is I still have adb shell access and root.
* Is there anything I can do to make that homescreen switcher app run on my phone without using a launcher (from shell, for instance)?
* Is there some important point I'm missing about my recovery (I've flashed back everything I changed, at least in my mind)
* Perhaps I could flash something else from Recovery, and that would clear this up?
* It would be great to know what I did that messed this up.
EDIT:
I meant DI01, not "Di05". Nice catch!
It turned out in my case that data wipes were crucial - the factory wipe in system, and the data/factory reset &or cache partition in recovery mode.
http://forum.xda-developers.com/showthread.php?t=782204
Follow this to the letter. Been there, done that. Home Switcher isn't what went wrong. You'll be fine in 10 minutes.
Wait. DI05??? Do you mean DI01 or DJ05? You need to make sure you flash the modem that matches your ROM. Either easy is fine, and probably didn't have anything to do with your force close loop, but make sure they match or you won't be able to text.
And PDA in Odin.
I have a Verizon Galaxy Tab SCH-I800 and I woke up today and it was missing some programs that I had installed the night before. Launcher pro keeps crashing so I had to put the Samsung Launcher back on. Now random programs all keep crashing and locking up the device. I performed a factory reset through settings -> privacy -> perform factory reset.
It restarts and goes to the samsung bootloader and I performed wipedata/factory reset.. It says it does it but when it restarts its in the same condition as before.
I've booted directly to the bootloader and tried it too (volume up and power key). I've also tried to wipe cache with no luck..
Any ideas? Can I root it and put a custom rom on it? I saw that there really aren't any roms for the Verizon tabs.. Any reason why?
Thanks for any help..
I just did a restore with all the stock verizon firmware using heimdall and it flashed and everything went through properly..
I booted into recovery and wiped data/cache and restarted...
SAME THING! It will NOT wipe out my existing data.. It restarts with all of my old programs installed and NOTHING will work.. The OS is hosed. How can I wipe this thing back to factory??
kgelso said:
I just did a restore with all the stock verizon firmware using heimdall and it flashed and everything went through properly..
I booted into recovery and wiped data/cache and restarted...
SAME THING! It will NOT wipe out my existing data.. It restarts with all of my old programs installed and NOTHING will work.. The OS is hosed. How can I wipe this thing back to factory??
Click to expand...
Click to collapse
Any luck with this? I'm having the same issue and don't have ODIN setup for it.
Same Issue
Same Issue
I changed my passwords on Facebook, Twitter and Gmail. After about 30 minutes the tablet finally stopped bringing up my information.
Need help!
Same to me...
I've tried to uninstall some apps several time, GTab automatically rebooted and these apps are still there...
Could anyone solve this issue?
Bump...
Bump...
I'm in the same boat..half my apps crash when you try to open them. I've wiped the data partition 3 times, and the cache as well..not avail. Apps are still on the device after a master reset!
scruffy828 said:
Bump...
I'm in the same boat..half my apps crash when you try to open them. I've wiped the data partition 3 times, and the cache as well..not avail. Apps are still on the device after a master reset!
Click to expand...
Click to collapse
I had that problem, and I wound up sending it back to Samsung. It appeared to be a bad part on the board, so they replaced it and it's on its way back now. Not the answer you want, I'm sure, but call it in and get your RMA number.
student.driver said:
I had that problem, and I wound up sending it back to Samsung. It appeared to be a bad part on the board, so they replaced it and it's on its way back now. Not the answer you want, I'm sure, but call it in and get your RMA number.
Click to expand...
Click to collapse
On your new Tab can you perform a hard reset and have it actually work?
my sprint Tab seems to be in the same boat
Was on stock/rooted 4.1.2, twrp 2.3.1.1 and applied the signed OTA 4.2 update via twrp.
The update installed with no errors (saved and restored root via voodoo, schweetness) However, whenever I reboot I get through normal colored X screen and then a dialog box saying 'andriod updating, starting apps' which shows for a few seconds right before it goes to the 4.2 lock screen.
Could this be due to some incompatible programs still installed or is this normal behavior others are seeing?
Also it seems that the 'complete' boot time seems longer than 4.1.2 which I assume is normal as well??
Afterwards the system seems to run normal/stable and very quick.....
Thanks
Totally normal. It's the apps cache rebuilding since it was cleared on the install. If you use twrp to clear cache and dalvik....mainly dalvik, you'll see it do it again. Its normal.
gokart2 said:
Totally normal. It's the apps cache rebuilding since it was cleared on the install. If you use twrp to clear cache and dalvik....mainly dalvik, you'll see it do it again. Its normal.
Click to expand...
Click to collapse
Thanks for the confirmation, much appreciated.....
bonzer2u said:
Was on stock/rooted 4.1.2, twrp 2.3.1.1 and applied the signed OTA 4.2 update via twrp.
The update installed with no errors (saved and restored root via voodoo, schweetness) However, whenever I reboot I get through normal colored X screen and then a dialog box saying 'andriod updating, starting apps' which shows for a few seconds right before it goes to the 4.2 lock screen.
Could this be due to some incompatible programs still installed or is this normal behavior others are seeing?
Also it seems that the 'complete' boot time seems longer than 4.1.2 which I assume is normal as well??
Afterwards the system seems to run normal/stable and very quick.....
Thanks
Click to expand...
Click to collapse
Hi bonzer2u,
i am stock, rooted but with no custom recovery and the Voodoo rootkeeper app. I am contemplating doing the OTA update but heard from other posts that SuperSU v0.98 caused major headaches and issues. Since you were successful in installing the update I was hoping you can confirm if you had the SuperSU installed with the latest version?
Thanks,
JBIRD