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.
Related
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.
Question, Im getting alot of "com.google.process.gapps" force closes on my EVO since I restored a few apps thru Titanium Backup. I rooted about a week ago and never had any issues with this. The only apps that I restored was angry birds and a to-do-list app along with all the data that came with the apps. I have tried cleaning caches and restarting the phone and nothing seems to work... what would you suggest? I seen a few threads when i searched - but they were for the G1 and the Captivate, nothing for the EVO... any help would be appriciated...
TIA
JS3
Did u flash any Rom or Theme??
nope, I rooted and am still using the stock ROM... I was going to flash Frost or some thing, but I want to make sure this doesnt carry over to the flashed ROM, or if there is a fix...I would prefere to fix it...
I am also getting a force close on the phone process.... when some one calls me and I ignore the call it force closes the process for the phone as well...
Try reinstalling the gapps.apk. One of them must of been corrupted by the data you restored.
do you know where I can find that at? I have never heard of it...
Also the thing that is confusing, is I can still access my market, maps, latitude, people, gmail... etc
If the apk or files were corrupted, I wouldnt be able to access those apps... i will try to reinstall the apk, but I would like to know what I did to make this error happen, so I know not to do it again...
one thing I think it could have been was there were two "people" files in my Titanium Back up... One was up near the top it said "People 1.00" and then there was one near the bottom with a line thru it that said "People 1.1.1" or some thing to that effect... I deleted the one at the bottom with the line thru it cause I thought I didnt need it any more... could this be wahts up with this error?
I can still access People thru the People widget, but some times it takes abnormally longer to load my list of contacts...
I can also still access Market, Gmail, Maps, Latitude...
I just clciked on Talk and it seems to be the problem, every time I click Talk it brings up the force close issue...
should I just reinstall the Talk.apk?
I also get "com.android.phone" force close when I decline a call...
when I went into my ROM manager, I clicked the "fix permissions" and it says "error occurred while attempting to run privlaged commands"
Any info on any of this would be great...
Anyone out there
Sent from my EVO while tethered into the Matrix thru Wifi...
Okay well I have googled/searched XDA 'til I was green in the face... I still can't figure out how to fix this issue?
Just answer me this, If I do an entire factory reset - will I loose root?
I have wiped the cache thru recovery, Should I try wiping the delvic-cache also, before I factory reset to see if that works??
I can not find any where to download the "gapps.apk" anywhere, I found this one thread that told me to install these in this order:
1. TalkProvider.apk
2. GTalkService.apk
3. Talk.apk
but none of them worked... they wouldnt even install... it just kept saying install failed...so I found another thread with the 2.2 gtalk and it installed...but Im still getting the error...
I have been getting several other errors, like htc.bgp force close (or some thing like that) as well as com.android.phone force close...
So should I just do a NAND restore or should I do a factory reset instead? OR should I run the RUU and start over to root...??
I am at wits end here and am not getting anywhere with searching...
TIA
I would start with a NAND restore. (Hopefully you have one from before the problem started)
If that doesn't fix it, do a factory reset.
If that doesn't fix it, Factory reset and instal a custom ROM (Sprint Lovers is very close to stock if that's what you like)
I don't think running an RUU is necessary. Once you obtain full Root, you should be able to fix any problem with .apk's or programs on the phone.
Biggest Fro said:
I would start with a NAND restore. (Hopefully you have one from before the problem started)
If that doesn't fix it, do a factory reset.
If that doesn't fix it, Factory reset and instal a custom ROM (Sprint Lovers is very close to stock if that's what you like)
I don't think running an RUU is necessary. Once you obtain full Root, you should be able to fix any problem with .apk's or programs on the phone.
Click to expand...
Click to collapse
Thanks for the input, I was beginning to think I was invisible... lol... I will try that and see what happens...
Well, I went ahead and tried one more thing before I did what you said to do and I think it worked... I went into my EVO while in Disk Drive mode and I cut my entire Titanium Backup folder out of the phone and copied it onto my Desk top. Then I went into my OLD EVO files from the end of the year and I copied the latest folder into my phone. I then went to Charge only, clicked TB and refreshed the app list... Then I was left with a ton of apps that were not installed on my phone. I then went thru each one and restored the ones that were still installed and deleted the ones that were not... (except for the stock apps that came with the phone), so far so good... I will test it more tonight and see whats up, have not gotten any force closes since I finished...
One thing I would like to know tho - where can I get the stock dialer.apk
Some how it got deleted off my new EVO and when I try to load up one of the htc.dialer.apk from my old EVO - the new one does not recognize it... I am currently useing "dialer one" from the market - but I would prefere to make my NAND back up of the Official stock ROM with all the stock apps...any ideas?
EDIT: Okay, fixed the com.google.process.apps issue but did not fix the other force closes... I guess I will have to try the steps above - and worse case - ill just run the RUU and start all over...
I had this problem once and it was related to a widget I downloaded that retrieved missed calls. Don't know if that helps.
Sent from my PC36100 using XDA App
sw99 said:
I had this problem once and it was related to a widget I downloaded that retrieved missed calls. Don't know if that helps.
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
But thats the thing - I didnt download anything - I restored two apps, one was opera mini with data and the other was spareparts... then I lost my htc dialer - so I installed Dialer one from the market... I dunno Im just gonna have to do the stpes above and if they dont work - Ill just wipe and run RUU and reroot... no biggie...
Okay I did a NAND restore... then I went thru and set up ALL my apps and settings again and then I did a fresh NAND Backup with clockwork first AND then Amon_Ra... all seemed well except, after I did the Clockwork Backup... I was getting "com.smithmicro.DM has stopped unexpectedly" so searched and read a little and it seemed to have some thing to do with the PRL/Profile updater... so i went into the settings and opened the app manager and cleared the "data" in com.smithmicro.DM and then I restarted the phone and that seemed to fix it... thanks for all the help...
JS3
i tried updating to an rooted kitkat version as we as get the Native hotspot going for my Sprint GS4.. however i did something wrong and now. i keep getting pop ups stating "unfortunately, SAE has stopped as well as many other programs.. how can i get this fixed.. i have tried factory reset, and to return to an stock firmware, but i cant get odin to pass. it keeps failing.. I have downloaded all the necessary stock firmware files, drivers etc.. . I can get a recovery to flash,, but the pop-ups for "stopped apps" still appear.. and i cant get pass them.. .
Same issue here
I have tried odin with stock tar and it fails I have no idea where to go next. I am sure it has something to do with the services.jar and services.odex files but how do you get around that.
Dee Bee said:
i tried updating to an rooted kitkat version as we as get the Native hotspot going for my Sprint GS4.. however i did something wrong and now. i keep getting pop ups stating "unfortunately, SAE has stopped as well as many other programs.. how can i get this fixed.. i have tried factory reset, and to return to an stock firmware, but i cant get odin to pass. it keeps failing.. I have downloaded all the necessary stock firmware files, drivers etc.. . I can get a recovery to flash,, but the pop-ups for "stopped apps" still appear.. and i cant get pass them.. .
Click to expand...
Click to collapse
Dude here is your answer use odin and install clockworkmod latest addition... then download stock kit kat zip put it on your sd card and install via clockworkmod. This work for me cause I was having the same issue. Peace out.
Also having this issue. It started before I rooted. First I did a factory reset, (and assuming that would fix the issue on a completely stock unrooted phone) decided if I was doing a reset there would be no safer time for me to root. So I CF-Autorooted and enabled native hotspot. I believe this is possibly somehow related to my phone and the play market because updating or installing apps seemed to be the common element triggering them to start failing. Google Search would fail over and over every half second after I dismissed the notification making the phone all but unusable, so I did another factory reset, and now SAE (presumably samsung account setup?) is what fails without even the half second in between, completely unusable. I'm afraid my last hope is to one-click it.
After i tried
http://download.chainfire.eu/397/CF-Root/CF-Auto-Root/CF-Auto-Root-klte-kltexx-smg900f.zip
on lollipop on vodafone uk, i got this error message on boot, i press ok and after reboot i got no root
Then i install superuser through twrp that i previously had and keep getting this error message on boot.
The thing is i cant get past it, its covering the whole screen no operating system ui just that in a white box and a press ok, which doesnt work until after 2 minutes.
EDIT: its just constantly saying programs has stopped responding in a loop and cant get into android system. How do i fix this, i tried fixing permission in recovery but that didnt work.
So what i can do without losing all my work on my phone.
I hope you made a backup before flashing root files
Boot into recovery, clear CACHES, reboot - see how you get on with that
If you flashed CF Auto Root, there was no need to flash SuperSU, as it comes part of CF Auto root, someone else just did that and ended up in a boot loop, had to wipe the phone and flash a stock ROM
Thats the thing i didnt, i watched a video saying it wouldnt delete your files rooting and decided not to backup.
I was stuck on samsung logo half the time and other times stick with "unfortunately MTP application has stopped." in a big white box blocking me getting into android.
I tried fix permission, clear cache and delvin cache and nothing worked.
I just system wiped and got in but lost all my work.
Fortunately Google backed up most of my photos and videos and contacts but no sms messages.
Now i gotta get all my apps back on my device and get it back to how it was and hopefully i did not mess any important texts.
Note to self: Always backup.
EDIT: i just had gaaps not working and giving server error, after trying out ways to fix that i tried all the normal stop app and clear cache, and then did fix permission in twrp, and after doing "also fix SELinux contexts" it messed me over and got me back to that white box.
so another note to self not to use "Fix SELinux contexts" as that messed up my system after getting 30 apps back installed.
Hello.
My Galaxy S4 was dying so T-Mobile just replaced it with an S5. It came with:
LMY47X.G900TUVS1FOJ4
I clicked on Software updates in About device and it did whatever updates, but the version stayed the same. Then I went to autoroot [dot] chainfire [dot] eu and downloaded the correct file to root. I unzipped the file and ran Odin 3.10.6 that came with it. I was able to root the device no problem.
What seemed like a problem afterward was that I couldn't find SuperSU in the Application list. I know the phone was rooted though because I could launch Titanium Backup to restore all my stuff from the S4. I went to the Play Store to download SuperSU. It kept complaining that I needed a new binary, but it would fail every time to update. I even tried downloading the latest SuperSU zip to install in the recovery mode, but that failed too. I really wasn't too worried about this.
While looking up how to root the S5, I saw some posts where people mentioned their root access stopped after 24 hours. I just experienced this when I launched Titanium Backup to begin uninstalling bloatware. I was informed that I didn't have root access anymore.
I figured I'd try to reflash the auto-root through Odin. According to Odin, everything passed, but looking at the device, it said it's already patched and the restore failed, so it aborted.
Now the device is stuck in an infinite reboot loop. I can access both the download and recovery modes, but that's it.
I'd really really like to not have to do a factory wipe as it was a pain to get everything copied over from the S4.
Can I flash it with something else?
Once I can get back in the device, how do I keep the device rooted? Do I have to flash TWRP or CWM?
The only root program I use is Titanium Backup and would really really like to keep using it to makr regular backups.
Thanks a lot.
Try booting into recovery and wiping the CACHES
If it still won't boot, grab a stock ROM from sammobile .com for your model S5 (G900T by the looks of the ROM name) and flash it with ODIN from download mode
That won't wipe your data or anything you've restored, as long as you don't reset
If it still won't boot, you might have to suck it up and factory reset after flashing stock
Was the TiBu backup you restored, rooted? Maybe restoring the backup restored an old version of SuperSU and broke the CF AR version
Might need to go down the TWRP and SuperSU from TWRP recovery route to get it rooted properly if CF AR isn't woprking 100%, which it doesn't for a fair few people
I tried clearing the cache, but that didn't work.
Is there a way to download the stock ROM without having to create an account on the download site?
The Titanium Backup I restored was rooted. Everything was totally fine, until I went back to TB and it suddenly told me I wasn't rooted anymore.
I did try TWRP after I made the original post. I think messed up the device, but I can get in now. I flashed the latest version and booted into Recovery Mode. I clicked on Fix Permissions and possibly one other thing. It let booted farther before the infinite bootloop. It'd show my lock screen and give me 1-2 seconds before rebooting. If I swiped quickly, I could see the home screen with most of my icons gone. Clicked on Apps shows most of the apps are gone. When I removed the SIM card, I stopped getting the infinite bootloop. Here are the list of important programs I have left:
Contacts (all cleared out), Gallery (all present), Messages (all present), My Files (shows files from previously installed programs that I can no longer access), Phone (works when I put the SIM card back in), Settings
Unfortunately, TB and the Play Store are both gone. I might be able to install stuff using adb or by copying files over. I haven't tried, but it doesn't look good. I tried reflashing the CF ROM. It didn't change anything. I suspect I may be looking at a factory reset at this point. I'm happy to try any other suggestions.
Thank you.
whynoteel said:
Is there a way to download the stock ROM without having to create an account on the download site?
Click to expand...
Click to collapse
Wut? lol, just make one, it's free...
XDA does not spoon feed
I created an account and downloaded the stock ROM. I flashed the device and got most of the programs to appear again though the Play Store was still missing. I decided to cut my losses and just do a factory reset. I rooted again and put everything back in place. Now I'm experiencing the problem where I lost root after a day or so of use. I'll start a new thread.
Thanks for your help.