Related
I get this message when I boot up.
I cannot access settings so I cannot perform a factory reset.
Is there any way to factory reset when you cannot access "Settings" because of constant force closes.
I am running stock but with lots of side-loaded apps.
I can access the file explorer. That is the only thing I can open that will remain open even though I get constant force close popups like "android.process.acore has stopped... android.process.media has stopped unexpectedly...
Is my gtab toast? Can it be saved or should I return it?
I get this all the time, with all the mods I do. Don't worry, your system is fixable.
For me, I use clockworkmod recovery .08. There's a "fix permissions" option and this always fixes the problem for me. It also allows a data wipe within recovery.
If you are 100% stock, you could try one of the stock ROM's here as well - that might get you working. You have a few options, here. Check out the FAQ in my signature. I'm actually posting up the new stock update that I pulled from TnT, today.
EDIT: Direct link the the stock ROM updates -- http://forum.xda-developers.com/showthread.php?t=842000. You'd need to understand how to actually run these, which I mention in the FAQ section.
thx Roebeet, I was able to update to the new stock rom.
But I still have the same problem. Is there any other way to wipe my data. Can it be done while connected by usb or do i have to root it?
Is there any hardware button method to do a factory reset?
I still cannot open settings... it gets canceled by the force closes.
I am ready to give upon my G-Tab which I was enjoying so much.
Does anyone know how to wipe the date if you cannot open settings???
Try clockworkmod - it really is a great tool. You can find it in the Tnt Lite dev section as I have a link for .08.
For UID issues, "fix permissions" will correct it. And you can wipe data via clockworkmod as well. You can even remove it by flashing back to stock -- the latest stock firmware works as I've done it myself, the other day.
Btw, there are so many threads here that I sometimes miss replying. I dont ignore, I just might miss a post. Always feel free to PM me if you have a question.
I had a similar issue where something got corrupted in my user data and I was completely unable to start the settings or open the keyboard. I had to flash back to the full vanilla ROM because it contained clockworkmod, which was the only option available to accomplish a factory reset. That wasn't a fun day.
Think I figured out a key reason for sudden UID issues
People including me are getting UID errors even after having a stable rom and several reboots with no issues. Based on guinea piggin' my G, I can confirm the issues happen on apparently stable installs anytime you update a Google app.
Case in point, I updated Google Voice and Gmail and soon after I rebooted the G- UID city. I have started with a clean rom and installed many different apps to test. The only apps that hose the device at reboot are the GAPPS and it is not just if you update with the package. Simply updating from market will work fine, until you reboot and then it is a few minutes for trying to shut the device down and then perhaps two reboot attempts using fixed permissions.
TnT 2.20 (at least) does NOT like GAPP updates. How could VS bork this up so bad that fundamental apps for Android bork the device?
Again, the Tap UI team and who hired them and approved it on the Gtablet should be fired, rehired for a minute and then fired for good. Word.
This sounds kind of "preachy," but don't give up.
There is a learning curve to the G-Tablet, and it takes a good bit of reading on this site and assimilating the info.
I will testify that I had a hugely bad malfunction and and even worse fix on my tablet.
Using suggestions from helpful folk -- and carefully researching what I needed to do -- I was able to get my tablet back working just fine. To be sure, it's not stock any more!!! But I actually believe that with all I learned about flashing, mods, etc., I now could go back and make it stock again if I wanted to.
Don't give up. Just keep reading and researching the learning.
Rev
rushless said:
People including me are getting UID errors even after having a stable rom and several reboots with no issues. Based on guinea piggin' my G, I can confirm the issues happen on apparently stable installs anytime you update a Google app.
Case in point, I updated Google Voice and Gmail and soon after I rebooted the G- UID city. I have started with a clean rom and installed many different apps to test. The only apps that hose the device at reboot are the GAPPS and it is not just if you update with the package. Simply updating from market will work fine, until you reboot and then it is a few minutes for trying to shut the device down and then perhaps two reboot attempts using fixed permissions.
TnT 2.20 (at least) does NOT like GAPP updates. How could VS bork this up so bad that fundamental apps for Android bork the device?
Click to expand...
Click to collapse
Not true for me, I installed the new Gmail from the Market with no problems. I am on TNTLite 2.2.1.
Google Voice has always been a hack for a tablet, since it is not actually phone. You might want to pull it out and see if your issues are solved.
I am back up and running thanks to clockwordmod. Thanks again!
ninjaprofessor said:
I am back up and running thanks to clockwordmod. Thanks again!
Click to expand...
Click to collapse
Good to hear and thanks for the update!
I am currently having this problem. I am hoping to sell my 10" Android 2.2 Tablet PC on Craigslist... I need to fix this Error... I've only used it 10 times to play Angry Birds. The forum with the links I am confused as to what one to use... I am younger I must say. I am not a 21 year old "computer whiz"/.NET/OS maker... I do make websites. Besides that... I do not know how to "Wipe my system partition" as my Error message says to. Especially due to the fact I cannot open Settings. PLEASE HELP. I may have repeated things said above in his problems but I would like a "NOOB" walk through... (Because I am one). Please help. Thanks in advance. -Sophomoric
Hey, I had a same after my phone battery was empty and it turned off. I kept it off and recharged it, then I had the feeling "I'm feeling Lucky" -.-' so nice from google. xD
Had to wipe everything then full reinstall... such a pain.
Probably the cleanest solution HERE
My phones been acting strange the past two days, but today it decided to die on me.
I was using alien #1 ROM, when I got spammed with error messages. My CDMA radio quit working, giving me the com.android.phone error
I decided to install another ROM, this time Cyanogen Mod 7. Same problem.
I did a standard wipe and install, fix permissions, everything.
Either its the Kernel, or my radio's shot.
If someone has any more insight into this problem, or has fixed it, please let me know
I'm getting a new phone next monday probably, but if anyone can fix my problem before then, I'd be greatful.
Also, Stock ROM link would be awesome.
No homebase ROM, please. I'd like the full stock ROM, bloatware and all.
Different, but similar Google seaches pull up nothing. Almost got hacked as well by a malicious ad.
I just got my other new htc one yesterday and I decided to root it and and unlock it and install the google play system on it. It all went well of course I back up all my stuff including the rom. I got an error saying my phone kept cutting off and kept dropping signal I cut off the phone and got in recovery and cleared the cache. Booted up again and same issue so I go to install the old rom and now its stuck and I cant get it to come off the htc one with the beats audio slogan at the bottom. Please Help!!!!!!!
Ok I got it to come off the that one screen now. It wont let me just click restore and it restore my old rom???? I dont know why. Does anybody know why it didnt backup like it was supposed to? I even created an zip file also. I need to get this thing working again asap. So as of the moment I have the google one back on it sais "Unfortunately, the process com.android.phone has stopped"
I had all kinds of troubles too, so I relocked it, and flashed the rom that is on the HTC support site. It worked for me. It's huge though, like 980 meg I think.
Hey guys; I've been using dastin1015's ROMs for almost a year now on my Sprint Evo 3D. I definitely don't know everything (probably not even close) about using custom ROMs, but I'm not a complete noob.
That said, I screwed up. I successfully replaced my 4ext touch recovery with TWRP as dastin1015 says must be done for this ROM. I then wiped everything except my SD card and 'System' and flashed the latest ROM located here (Villuminati 12/08/13), and the "full complete" GApps package located here (4.4).
I rebooted the phone, and admired the new CM splash screen. Once the ROM loaded, I immediately got a couple of stock (system) apps (com.android.phone and ThemeManager along with some others) forceclosing repeatedly, preventing the phone from fully booting and making it very difficult for me to reboot the phone into recovery-- the messages popped up over and over again on top of the menu for reboot. I eventually did manage to get back into TWRP though.
At that point, I wiped *everything* except my SD card, and flashed the ROM and GApps again. Now I'm having the same problem, but with even more system apps force-closing, and I cannot reboot the phone or do anything else with it via the phone itself.
What do I do now? Can I fix this with ADB?
I read that using this 4.4.1 GApps might solve or prevent this problem, but it's iffy. In any case, unless someone has a better solution, that's the next thing I wanna try after managing to reboot into recovery. Do any of you think that will work?
Thank you.
Yes that one worked for me and I used 4ext with no problems
Sent from my Evo 3D CDMA using XDA Premium 4 mobile app
Glad to hear it dschlemmer.
The proper answer to the first part of my question (can I fix this in adb) is "of course, you idiot, just connect the phone to your pc and type "adb reboot recovery" and then wipe and re-install your old ROM or something."
However, I can't get the PC to recognize the phone, despite it having the proper drivers and having recognized it before. I think it's stuck at a phase in its boot-up that comes before the usb debugging is activated. My PC recognizes something is plugged in, based on the ding noise it makes (it's a Win 7 Pro x64 machine, and I think most of us are familiar with that ding noise), but the normal behavior of searching for and finding the drivers and then telling me the device is ready to use never occurs. Neither is there that "safely remove hardware" button in the taskbar.
So, of course, if the computer itself doesn't recognize it, adb can't either (confirmed by typing "adb devices" and it showing nothing). Is there anything I can do, or have I actually managed to completely (irreparably) brick my phone?
EDIT: The usb port is functioning, at least, as is whatever part of the circuitry or firmware controls the LED while plugged in and/or charging, because that works just like it should. It's just that I can't do anything but repeatedly cycle through the same "Unfortunately, the process com.android.phone has stopped", "Unfortunately, Themes provider has stopped", and a couple other messages that get covered up by those two, including one I briefly saw that mentioned "Settings". Haven't been able to see any of the others for long enough to identify any part of them.
EDIT2: I forgot about using the bootloader. Completely forgot. Stupid. Successfully in recovery, about to flash the same ROM with the new GApps. If it gets screwy again, I'll just remove the battery, replace it, and get into the bootloader to get into recovery.
dschlemmer318 said:
Yes that one worked for me and I used 4ext with no problems
Sent from my Evo 3D CDMA using XDA Premium 4 mobile app
Click to expand...
Click to collapse
From that version of GApps, what all did you download and use, exactly? I grabbed Standard and almost everything that didn't come included with it and flashed it all with the same ROM and the phone went into a bootloop that consisted of repeatedly verifiying apps (67 of them), throwing an error message similar to the ones I was getting before, then rebooting to do it all again.
I got a new Galaxy S4 ($50 at Best Buy with a 2-year contract renewal, woot-- Sprint wanted to charge me $200 for the same thing through them directly), so this isn't a pressing issue anymore, but I'd like to give the Evo 3D to my sister-in-law for Christmas. I ended up putting some AOKP Jelly Bean ROM on it (the zip was labeled Unofficial AOKP JB 3.5, I believe) I had sitting in the roms folder on my sd card with its own kernel next to it, and the phone appears to be functioning fine, but I'd like to a) figure out wtf the problem was/is with this ROM or GApps or whatever (something I did wrong probably) because dastin's stuff has always worked great for me before, and b) see Kit Kat in action on the phone. Either that or put it back to stock, which was, what, ICS? Did Sprint Evo's ever get an official upgrade to Jelly Bean?
In any case, and in lieu of posting in the relevant thread in the development forum since I don't have enough posts yet, here's the information about the phone at the time of this weirdness:
S-OFF
Hboot 1.40
Radio 1.09.00.0706
TWRP v2.6.3.0 recovery
NineInchNails' kernel posted in dastin1015's CM10.1-based ROM thread (Wild for the Night)
The ROM on the phone before the attempt to upgrade was dastin's latest Hood Pope version (Oct. 21st, 2013), which had been running just fine up until...
.... about 2 weeks ago, I uninstalled this Call Recorder app because I was running out of internal storage (~40 MB left) and I thought the app was causing it. Even though all the recordings seem to have been on the sd card, uninstalling it appeared to remove about 350 MB of something from the internal storage. Shortly after that (but not immediately after), every time I would end a phone call com.android.phone would force-close. I thought it was weird, but not too troublesome since it only happened after I ended a call, so it didn't affect my actual usage of the phone beyond having to tap an extra button every time I hung up the phone.
Then the other day, I noticed Villuminati was out and it was Kit Kat, so I went to install it, which failed spectacularly (as I said above, probably due to something I did or didn't do, but I'm not positive), and I posted this thread. You pretty much know the rest if you've read to this point.
electrickoolaid said:
From that version of GApps, what all did you download and use, exactly? I grabbed Standard and almost everything that didn't come included with it and flashed it all with the same ROM and the phone went into a bootloop that consisted of repeatedly verifiying apps (67 of them), throwing an error message similar to the ones I was getting before, then rebooting to do it all again.
I got a new Galaxy S4 ($50 at Best Buy with a 2-year contract renewal, woot-- Sprint wanted to charge me $200 for the same thing through them directly), so this isn't a pressing issue anymore, but I'd like to give the Evo 3D to my sister-in-law for Christmas. I ended up putting some AOKP Jelly Bean ROM on it (the zip was labeled Unofficial AOKP JB 3.5, I believe) I had sitting in the roms folder on my sd card with its own kernel next to it, and the phone appears to be functioning fine, but I'd like to a) figure out wtf the problem was/is with this ROM or GApps or whatever (something I did wrong probably) because dastin's stuff has always worked great for me before, and b) see Kit Kat in action on the phone. Either that or put it back to stock, which was, what, ICS? Did Sprint Evo's ever get an official upgrade to Jelly Bean?
In any case, and in lieu of posting in the relevant thread in the development forum since I don't have enough posts yet, here's the information about the phone at the time of this weirdness:
S-OFF
Hboot 1.40
Radio 1.09.00.0706
TWRP v2.6.3.0 recovery
NineInchNails' kernel posted in dastin1015's CM10.1-based ROM thread (Wild for the Night)
The ROM on the phone before the attempt to upgrade was dastin's latest Hood Pope version (Oct. 21st, 2013), which had been running just fine up until...
.... about 2 weeks ago, I uninstalled this Call Recorder app because I was running out of internal storage (~40 MB left) and I thought the app was causing it. Even though all the recordings seem to have been on the sd card, uninstalling it appeared to remove about 350 MB of something from the internal storage. Shortly after that (but not immediately after), every time I would end a phone call com.android.phone would force-close. I thought it was weird, but not too troublesome since it only happened after I ended a call, so it didn't affect my actual usage of the phone beyond having to tap an extra button every time I hung up the phone.
Then the other day, I noticed Villuminati was out and it was Kit Kat, so I went to install it, which failed spectacularly (as I said above, probably due to something I did or didn't do, but I'm not positive), and I posted this thread. You pretty much know the rest if you've read to this point.
Click to expand...
Click to collapse
i flashed rom then 12-6_gapps_standard_4.4.1_signed then reboot this is the link for the gapps : http://forum.xda-developers.com/showthread.php?t=2012857
Any ideas? Other apps I installed to try (eg Signal) fail too. Stock ROM.
This is my fist post, have visited many times. Here we go.
As a LG V20 owner, I recommended the V30+ to two people at work. In a matter of 24 hours, both units stopped sending and receiving emails. I have taken the sims out and tested these in other phones, not a sim issue. I then moved my sim (Telstra Aus) into the V30 and only in the Messaging app, it came up with the message No SIM. This I thought might be a sim slot issue, moved it into the other slot closest to the outside. This worked for about an hour. Then the same issue occurred again. It has to be software, an update or a network change that has caused this. I did a network setting reset, have cleared cache for messaging app. SAFE MODE etc. Very strange.
yanni_pap said:
Any ideas? Other apps I installed to try (eg Signal) fail too. Stock ROM.
Click to expand...
Click to collapse
Yes I used Messenger app for SMS and this failed. It sounds network setting related but still testing.
I had the same problem on my V30, suddenly SMS has stopped working. (I'm using Textra app)
I checked the sim card on the other phone and it was ok.
I found on the internet that other V30 are also affected.
The solution was to install the Message app from Google and run it.
Now SMS is working on Textra and also on the stock app.
Whoa, didn't see this before I posted in another thread. Same problem here, but I already had Messages installed! Wonder if it's just this phone for some reason?? My partner is also on VZ (S7) and can send SMS
edit: apparently it's something Google broke. Temp fix is to disable Carrier Services!
I just recently started having text messages not sending. I am on Verizon LG V30 using the vs996 30c debloated rom. Everything has worked fine until last week when I installed the latest Resurrection Remix rom. Since these roms’ tethering and WiFi do not work, I tried installing the us998 modem zip. I don’t know if that is the problem or not, but, I could not get it to work. I have since reinstalled my 99630c debloated rom and have now lost the ability to send text messages, although I can receive texts just fine. I have done clean installs and dirty installs of the rom. I, just yesterday, did a restore of a previous 99630c backup, changed messaging apps, etc. I even reinstalled Verizon’s messaging app.The messaging problem still persists.
i just got off the phone with a very nice Verizon tech, who spent about 40 minutes trying to help me. No success. She said everything appears to be working fine on their end. She ran out of things to try. She thinks my rooting the phone might possibly have something to do with it, which I agree with.
Does anyone have a working link to John Fawkes vs99630c zip? The one one his zip thread does not download for me. I thought I would try starting again with that zip. Maybe I need to try a different modem download?
Any suggestions much appreciated. Thx
gimpy1 said:
I just recently started having text messages not sending. I am on Verizon LG V30 using the vs996 30c debloated rom. Everything has worked fine until last week when I installed the latest Resurrection Remix rom. Since these roms’ tethering and WiFi do not work, I tried installing the us998 modem zip. I don’t know if that is the problem or not, but, I could not get it to work. I have since reinstalled my 99630c debloated rom and have now lost the ability to send text messages, although I can receive texts just fine. I have done clean installs and dirty installs of the rom. I, just yesterday, did a restore of a previous 99630c backup, changed messaging apps, etc. I even reinstalled Verizon’s messaging app.The messaging problem still persists.
i just got off the phone with a very nice Verizon tech, who spent about 40 minutes trying to help me. No success. She said everything appears to be working fine on their end. She ran out of things to try. She thinks my rooting the phone might possibly have something to do with it, which I agree with.
Does anyone have a working link to John Fawkes vs99630c zip? The one one his zip thread does not download for me. I thought I would try starting again with that zip. Maybe I need to try a different modem download?
Any suggestions much appreciated. Thx
Click to expand...
Click to collapse
See my solution directly above your question. It's not "rooting" that caused it, it's "Google" that caused it. Uninstalling or freezing Carrier Services will fix it. Did for me.
Check the litany of * reviews from today alone:
https://play.google.com/store/apps/details?id=com.google.android.ims&showAllReviews=true
Also, both the standard and debloat ROMs for VS99630c from their respective threads and androidilehost are downloading fine for me.
Thx, but did not work for me. I went into TiBu and found carrier services sitting in the non installed portion of the apps. So, I installed it (first with app, then with data) and tried both messaging apps with it installed. That did not work, so I went back into TiBu again and froze it. It still does not work.
I have tried downloading the standard zip from Fawkes zip thread 8 or 10 times or so. It gets to about 8 or 9% , then gives the message unsuccessful.
I will keep trying. Thx for your suggestions.
As an edit. My phone has also started giving me problems with my fingerprint recognition and my phone dialed has suddenly changed looks forcing me to constantly press and swipe an unlock button to keep the dial pad open if I hesitate too long in punching in numbers or trying to change to speakerphone from there.
I don’t know if it is something I have done/installed (wrong modem perhaps?).
And having the new XDA transition at the same time certainly didn’t help .
gimpy1 said:
Thx, but did not work for me. I went into TiBu and found carrier services sitting in the non installed portion of the apps. So, I installed it (first with app, then with data) and tried both messaging apps with it installed. That did not work, so I went back into TiBu again and froze it. It still does not work.
I have tried downloading the standard zip from Fawkes zip thread 8 or 10 times or so. It gets to about 8 or 9% , then gives the message unsuccessful.
I will keep trying. Thx for your suggestions.
Click to expand...
Click to collapse
I don't know what to tell you about the downloads, confirmed they work.
You don't need to freeze CS, you can literally just uninstall it from the Play store. It's just an enhancement for the Google MEssages app they broke. if you don't use Messages, you surely don't need it. I don't know what you meant about CS showing up in the "non installed portion of the apps". It's either installed and frozen or thawed, or it's not. Maybe you had a backup there for reasons? Regardless, you certainly need to reboot after changing CS, not sure if you did that.
You have alot of other issues coming from RR, then flashing a modem, then trying to dirty flash VS996. Since you have TB already, you should definitely backup your apps, then Maybe clean flash VS99630c once you've followed the WTF thread. You should probably wipe your system after the other ROMs and just start over.
That certainly was a quick answer. In TiBu, under “backup/restore”, I have all the apps that are currently on my phone—a very long list. This list can be frozen, etc., and is bolded and colored fonts. Scrolling down that list, it ends and a list starts that is not bolded and has lines thru it. I guess these are apps, etc. that I have, at one time, had on the phone and can be re installed via TiBu.
I was trying to “start over” by downloading the vs99630c rom and try it. Where were you thinking I need to start over at? I wish to work only on “zips” via twrp, as I don't have much luck/knowledge with kdz and computers.
Thx, again.
Again, I'm the furthest thing from the expert here, but he's on travel! Check the WTF thread, because I'm not sure what happens when you wipe with the flashes you've made. But you'd probably start from 6.7. MORE TWRP ACTIONS here:
https://forum.xda-developers.com/t/...ar-instructions.3790500/page-10#post-76584629
I would reboot to TWRP and do a complete system backup in case this goes tits up you can restore that from TWRP. Then I would boot to OS and back up everything in TB, then delete all uninstalled backups through the batch actions. Then reboot to TWRP again, wipe, install the VS99630c ROM, install MAgisk, reboot. Make sure your install works then restore your apps through TB.
Ok, thx. I wish to install the vs99630c rom zip now (not the debloated) and am unable to download it from JohnFawkes LG V30 vs 996-30c thread from here on xda. I have tried via my phone about a dozen times now and it stops now generally after the 10 to 20% zip has downloaded. I even tried it a couple of times downloading onto a laptop. Can you possibly point me to a different link that I can try? I need to be on Verizon’s vs 996 and not on the 998 rom, I think? Sorry for the big bother.
Well, I did finally find a download mirror on here from chazzmatts thread using his mirror. It is downloaded now. I will try this installation before going thru the wtf steps you referred me to. If this doesn’t work, then i will try it.
thx, again for your help.
As an update, I did a clean wipe and installed this zip. So far, it seems to have settled things down for. I was able to text (2) and make a phone call. Both worked. I did agree to everything they asked (I normally refuse things such as location, etc.). I’m happy for now. Later, I may try to reinstall the debloated zip.
Ideveraux, thx for all your help on here. I really appreciate it.
Make sure you backup TWRP and TB. Just saying!
And to the OP, I’m sorry I hijacked your thread. I hope you got yours solved, too.
I had this problem after owning the phone for several days.
I'm not sure why, but when i installed Google's "Messages" app, the problem was fixed.
I didn't have to run the messages app, just install it. The stock app suddenly started working again.
I then uninstalled google messages (without ever running it), and the next day I had the same problem.
Once again; I installed google messages, and the problem solved itself without ever running google messages.
This time; I haven't uninstalled google messages.
I'm guessing that something about SMS settings got messed up (i checked them when the problem first happened and couldn't find a problem), and installing a new message app restored the settings to normal.
TLDR: if SMS stops working, Install Google Messages. Problem solved.
Lozv said:
I had this problem after owning the phone for several days.
I'm not sure why, but when i installed Google's "Messages" app, the problem was fixed.
I didn't have to run the messages app, just install it. The stock app suddenly started working again.
I then uninstalled google messages (without ever running it), and the next day I had the same problem.
Once again; I installed google messages, and the problem solved itself without ever running google messages.
This time; I haven't uninstalled google messages.
I'm guessing that something about SMS settings got messed up (i checked them when the problem first happened and couldn't find a problem), and installing a new message app restored the settings to normal.
TLDR: if SMS stops working, Install Google Messages. Problem solved.
Click to expand...
Click to collapse
I tried that initially and that's not the accepted fix at all. Read above.