process stopped unexpectedly errors on newly rooted mytouch - myTouch 3G, Magic Android Development

I have a mytouch phone functioning fairly well on the 32A based ROM by AMON RA via this protocol
http://forum.xda-developers.com/showthread.php?t=547133
I get a series of error messages when trying to run various programs, e.g.
"the process android.process.acore has stopped unexpectedly, please try again"
"the process comandroid.phone has stopped unexpectedly..."
"the application setup wizard (process.com.android.setup wizard) has stopped unexpectedly..."
I did a search on this issue, and found related but different problem on
http://forum.xda-developers.com/showthread.php?t=473130.
Anyone have thoughts/experiences of this issue, links for resolutions for other rooting efforts on this or other phones, with this or other roms?
Regards,
Dave

I'm getting something similar, but the other apps that are crashing are handsent and google voice. As it stands I can't make phone calls, and my contacts don't sync. I would say it's a radio issue, but everything else works fine. Oh well, I'm going to go browse through the how to thread and see if I come up with something.

I saw some people having the same problems as yours. I would recommend doing the "Daredevil steps" from Amon_RA's how to root the mytouch thread. Then flash a 32B firmware on your phone. I believe you may be getting those errors due to the 32A firmwares being intended to work on 32A boards with more memory. I have cyan's 32B rom on my myTouch and it's working great

typically, you'll get these errors if you did not do a data wipe before you installed the rom...
i would suggest you data wipe, revert back to the recovery rom in the root process, wipe again, then apply the update

motivecc said:
typically, you'll get these errors if you did not do a data wipe before you installed the rom...
i would suggest you data wipe, revert back to the recovery rom in the root process, wipe again, then apply the update
Click to expand...
Click to collapse
I was planning on wiping the data on my google data base as well. I'm sure I can find out how to do your data wipe idea by reading through the forum. However, if you would be willing to give me a direction here, would be a nice shortcut, and I would be appreciative of your assistance.
I'm using this 32A based rom as a first foray into the altenative rom world, as a way to learn about how to do this. I will eventually be taking a daredevil approach back to 32b, I suppose, but would like to see if I can get this working.
While the error messages come up saying the phone program will shut down, I can still make and take calls, and pretty much do everything, but can't sync contacts, probably because of data base contradictions (between google and android).
Dave

I'm getting the same problem after rooting my mytouch. I had constant errors with the 32A identical to the ones leiko49 posted, along with performance issues, even after flashing to the 32B radio.img and running CM's 3.9.10, after having done a complete data wipe from recovery-RAv1.2.0G.
The device seemed smoother, but had problems with the phone portion such as failing on most outgoing calls and not receiving any incoming calls. I returned to recovery mode, did a complete data wipe again, reflashed 3.9.10 and booted it up. Testing the phone showed the same initial symptoms as before, but after about 1-2 minutes it seemed to hook onto the network properly and calls seem to go through fine in both directions now.
I'll post any updates if I notice it giving problems again.

I deleted all contacts in google on the web, unchecked syc contacts on the device, all unexpected stoppages have disappeared. So far everything appears to be working perfectly on 32 a rom. I had suspected from reading other related forums that the attempt to syc incompatable data fields was the problem with the error messages. This appears to fix the problem completely. I'll keep you posted.
I think next step (after a couple days of error free use of phone) will be to re syc outlook with google, then resycn google with android, see if the problem re appears. I hope that it won't because when it resyncs with android will just sync the compatable fields. But I really don't know much about this.
Then, since it was so successful, will eventually go over to a 32 b rom, I suppose, have to read more about pros and cons of that.

Related

Error on startup.. Help greatly appreciated.

Hey guys.
I seem to be having an error message popup on my phone about 3/4 of the time once I reboot. (see attached image)
Usually hitting wait works, but sometimes i have to force close it.
I have JFs 1.41
I thought at first it was due to the fact that I removed several stock apps (amazon mp3, calculator & alarm clock)
I also removed my entire stock ringtones folder.
So I put everything back in its place.
However, I still have the same issue!
I also tried debugging with dalvik. Didn't get much...
Anyone know whats goin on?
TIA
EDIT: Also, just wondering if theres a way to reset the phone without losin all my apps. Other than backup, i'm trying to avoid installing all of em again ;0.
I get the same error on startup
Just to add my 2 cents... I have as well removed the Alarm Clock, and Amazon MP3, and the stock ringtones (but left the folders intact & put my own tones in). I am running JF1.41, and have never seen this message.
Did you do a Nandroid backup before you started messing with things? If so, you can simply restore that, otherwise.... You would have to re-install everything in order to do a factory reset.
Have you tried going to Manage Applications - Media Storage - and clearing the data?
I would try doing a full wipe of the phone and see if the problem continues.
Just my 2 cents
daveid said:
Just to add my 2 cents... I have as well removed the Alarm Clock, and Amazon MP3, and the stock ringtones (but left the folders intact & put my own tones in). I am running JF1.41, and have never seen this message.
Did you do a Nandroid backup before you started messing with things? If so, you can simply restore that, otherwise.... You would have to re-install everything in order to do a factory reset.
Have you tried going to Manage Applications - Media Storage - and clearing the data?
Click to expand...
Click to collapse
Yea I've tried clearing the data. Its not fixin it tho. I have several nandroid backups. I would do a wipe but wouldn't that get rid of my apps?
Thanks guys.
restoring a nandroid backup to a time when you didn't have this issue would be the best bet, you would only lose the changes you have made since that backup.
topdnbass said:
EDIT: Also, just wondering if theres a way to reset the phone without losin all my apps. Other than backup, i'm trying to avoid installing all of em again ;0.
Click to expand...
Click to collapse
Well I had my apps and cache on my SDcard and after updating to JF 1.41 i had to do a wipe to get it to work, but after it was up and running I just replaced the mountd.conf and init.rc files and recreated the symolic links again and rebooted and all my programs were back. Just thought I would share cause this way pretty much worked for me to not have to reinstall all my apps... I'm still pretty new to all this so maybe there is a better way.. but this worked for me...
Unusual...
First I did a nandroid restore to the time a little after I got JF's 1.41. Everything was fine at first. I installed all of my apps. Tried to reboot a few times, and bam, I see it again.
In a rage--I wipe my fone from recovery mode. I then use MyBackup to restore all of my settings and apps.
I finish, and then i try a reboot and BAMMM ****in android.process.media is not responding.
Then I tried to reboot 3 more times wthout a problem and then the 4th time gave me the same problem.
Can anyone else whose having the same issue tell me what apps theyve recently installed?
Ive figured it out. But still stuck.
The problem was that i setup a symlink for my market cache to my sd card.
I removed the /data/data/com.android.vending/cache folder and my sd cards linked cache folder.
I then made a new cache directory in com.android.vending however I noticed that it wasnt working properly. It wasnt filling up with cache when i used the market.
I removed the symlink so why wouldn't it, right?
So I chmodded it.
I tried to chown it but i keep getting back unknown user app_5 (the markets ID)
I'm stuck please someone help me out here, and hopefully we can even get the market cache properly directed to my sdcard in the process.
THANKS!
topdnbass said:
Ive figured it out. But still stuck.
The problem was that i setup a symlink for my market cache to my sd card.
I removed the /data/data/com.android.vending/cache folder and my sd cards linked cache folder.
I then made a new cache directory in com.android.vending however I noticed that it wasnt working properly. It wasnt filling up with cache when i used the market.
I removed the symlink so why wouldn't it, right?
So I chmodded it.
I tried to chown it but i keep getting back unknown user app_5 (the markets ID)
I'm stuck please someone help me out here, and hopefully we can even get the market cache properly directed to my sdcard in the process.
THANKS!
Click to expand...
Click to collapse
try using the numeric id with chown instead. i.e. 10005 (not positive if it will work.. just something to try)
AHhh Yay JF ILY! That worked . I feel like a retard now.
The cache appears to be filling up as normal. The error isnt gone yet tho.
The question still remains. What causes that error?
How could i stop it?
The crashing process has the same gid/uid as Android.providers.media
it seems to be an app. I wiped and then I reinstalled 1.41. Then I installed all of my apps using mybackup. I made sure to do nothing else after, and I still got it.
Its either JF's 1.41 or an app.
How can I find out
Process of elimination. Wipe the phone again, instal jf's 1.41 and boot the phone. If you don't have the error, bingo, it's an app. Then, tedious as it may be, install the apps 1 at a time and reboot after install to see if you get the error.
Yeah I have done that.
However, its reallly hard because sometimes itll go 4-5 boots without a hitch, and then suddenly itll happen.
Then at other times it'll happen nearly every time.
I have about 65 apps. That's 4-5 boots, after installing each one.
So that would mean HUNDREDS of boots. At least 200.
I've been thinking that maybe its a problem with the MyBackup app.
What if the fact that mybackup overloads the phone with 20-30 installations at a time is whats causing the issues.
Well i'm off to error and error. I mean trial and error.
I've figured it out!
It's something to do with my wifi connection.
I think its that my dns's are from opendns.
Basically whenever my wifi is active when I turn on my phone i get that error.
If i turn it off and reboot into 3g, i never have a issue.
That's why it was so random before and I couldn't find any patterns!
I'm gonna call my ISP tomorrow, but anyone know what it could be?
I don't think it has anything to do with OpenDNS. I use JF1.41 RC30, MyBackup, and OpenDNS and never have any problems...
Hmm, do you have your router setup for opendns or your phone.
I have issues where i cant get my damn router to give out working IP's, so I
need to setup the phone for a static ip and dns.
I think that if I could get it to automatically get an IP i'd be set.
EDIT: Also, could it have anything to do with the fact that I have wpa personal security (AES)
Im having a similar problem but my error is slightly different
"com.google.process.gapps" anyone know WTF that is
Its the G Talk service.
If you dont use that app you could try removing it and see if that does anything ..
Since this has been bumped, i'd like to add that it still happens whenever I'm on wifi. Really blows
topdnbass said:
Its the G Talk service.
If you dont use that app you could try removing it and see if that does anything ..
Since this has been bumped, i'd like to add that it still happens whenever I'm on wifi. Really blows
Click to expand...
Click to collapse
Care to explain how?? Im a serious noob lol

[Q] My Fuze refuses to run unsigned software now!

I have an Att Fuze running the stock 6.1 firmware from Att.
I tried running XDAndroid 2.2 Final build for my phone, it appeared to crash while loading so I hard-resetted my phone.
Despite the fact that XDAndroid is supposed to run completely off the sdcard and not touch my internal memory, it appears to have corrupted my phone!
TouchFlo no longer launches (it keeps saying touch screen to launch TouchFlo, and if I do it goes crazy trying to launch and failing over and over), the phone is VERY slow and laggy, and the worst of it all, I CANT RUN ANY UNSIGNED SOFTWARE ANYMORE! Any attempt to run any program that isn't signed results in "The file (whatever) cannot be opened. Either it is not signed with a trusted certificate, or one of its components cannot be found"
I can't even run PimBackup to backup my contacts and text message logs!
I tried to install HardSPL since I figured might as well flash a custom rom to it but it failed too! It kept saying "Error 246 Device not responding" even though it identified it correctly when its booted into WM, and when I force it into bootloader mode it starts the process but gets stuck at 0% and eventually HardSPL gives up.
Is there anything I can try? Any way I can backup not just my contacts buy my call logs, text logs, etc before trying to reflash it? Any idea why XDAndroid would do this to my phone?
From what I understand, it isn't specifically Haret that did it, but some weird response to an error in starting Haret. I can't remember exactly what I did but I tried to run Haret incorrectly (my finger slipped on the touch-screen) and after that nothing would run. It triggered some weird thing in the OS.
I've heard of some people needing to get into reset mode before they can flash their phone -- not sure what the process is though.
Might be best to post in THIS thread. Keep in mind, you don't want to keep creating threads. It doesn't help our forum at all...
Also, it helps to read the post in it's entirety then try it out or if you need further assistance, post a reply.
R^7Z said:
Might be best to post in THIS thread. Keep in mind, you don't want to keep creating threads. It doesn't help our forum at all...
Also, it helps to read the post in it's entirety then try it out or if you need further assistance, post a reply.
Click to expand...
Click to collapse
Sorry about that, pretty much every forum I have ever posted in prefers you to make a new topic instead of post in an existing one when you have a problem.
I'll post my question there, although I wasn't sure where to ask a question about disabling that annoying signed programs thing.

Stock UI not as crappy after all

Well, I've gotten my tablet for 5 days now and have been playing with it a lot, tried all the different ROMS, anyways, upon receiving the tablet, pretty much nothing worked, e-mail app wont launch at all, a lot of the stuff in the settings crashed when I try to change them, just figured something out today after going back to stock rom, I formatted the internal storage and did a factory reset. Upon startup, I notice that it went through a TnT wizzard which I never got when I first received the tablet, and e-mail and all other apps are now working, and no more FC (still crappy, but atleast it works). I really think this is the problem viewsonic has, the devices didn't come factory reset, or atleast mine didn't anyone else's tablet didn't run the setup wizzard when you first received it, or is it just me? Because I really think they would have a lot less returns if all tablets came and started the setup wizzard on boot up as mine didn't have any problems at all after the reset/format. I tried the 3361 update and wow, its actually decent now, VS is definitely listening to the community when they added the ability to use the regular launcher.
Original Rom
Where can I get the Original Rom?
da-slicksta said:
Where can I get the Original Rom?
Click to expand...
Click to collapse
FAQs are your friend
http://forum.xda-developers.com/showthread.php?t=842899
For the latest version of the stock fw, check out the thread whose title ends with 3316. The first post has a link to it, and if you read through the thread you'll find posts with instructions on how to load it with or w/o clockwork mod.
http://forum.xda-developers.com/showthread.php?t=879534
For the original fw, check in the dev forum, there should be a thread with instructions on how to revert to stock fw.
http://forum.xda-developers.com/showthread.php?t=861950
http://forum.xda-developers.com/showthread.php?t=842000
Mine did not perform setup wizard as the manual said it would on first boot. As others have reported, about 20+ FC on first boot. I will try the factory reset to see if that helps like it did for you.
UnRoot
Do we need to unroot to get OTAs
eviltuna said:
I formatted the internal storage and did a factory reset. Upon startup, I notice that it went through a TnT wizzard which I never got when I first received the tablet, and e-mail and all other apps are now working, and no more FC (still crappy, but atleast it works). I really think this is the problem viewsonic has, the devices didn't come factory reset, or atleast mine didn't anyone else's tablet didn't run the setup wizzard when you first received it, or is it just me? Because I really think they would have a lot less returns if all tablets came and started the setup wizzard on boot up as mine didn't have any problems at all after the reset/format.
Click to expand...
Click to collapse
When I returned my first GTab to Sears I did a factory reset. When the person at the store opened the the box and turned it on it didn't go to the wizard. I believe that the power button can activate during shipping and after a certain amount of time it skips the wizard and then shuts off. VS should put a piece of paper inside the box with instructions on doing a factory reset FIRST. This could solve a ton of problems for new customers
There's a new one out - just see the vanilla ROM's section in the faq, in my sig. I'm going to post a link to the new ROM, shortly.
roebeet said:
There's a new one out - just see the vanilla ROM's section in the faq, in my sig. I'm going to post a link to the new ROM, shortly.
Click to expand...
Click to collapse
I already gave them links to the FAQ, new stock fw, and two threads for flashing original stock fw...
To get the setup Wizzard you must first Format you Internal Storage (Settings -> Storage), then do a factory reset (Security -> Reset to Factory). Once you do this the gTablet will shut itself down, then when you start it up you will get the wizzard, just doing a factory reset alone will not do this, you must format the storage + factory reset. Anyways, all the FC I had prior to doing this are now gone, I really think that after doing Quality control at the factory, they never did these steps and so the tablet comes borked with bad softare which can easily be fixed with this 30 second format/reset.

[Q] OTA 1.63.xxxx upgrade only on T-Mo network?

So I've read here about people doing upgrades to 1.63.xxxx stock ROM, but whenever I run HTC update I'm told there are no updates :/
Do you have to be on T-Mobile network for OTA update/upgrade to work or what?
Sorry to tell you this but u have missed the update. I don't know no other way to get it but your not missing nothing. Hell I'm not even using the stock launcher so yea.
MT4GS said:
So I've read here about people doing upgrades to 1.63.xxxx stock ROM, but whenever I run HTC update I'm told there are no updates :/
Do you have to be on T-Mobile network for OTA update/upgrade to work or what?
Click to expand...
Click to collapse
For the OTA, yes, you would have needed to be on T-Mobile. However, there are pure stock 1.63.531.2 as well as "tweaked/optimised/debloated" versions of that ROM now available here to download and install, if you're rooted.
I am running the MikTouch 0.7 ROM, which is an optimized version of the stock 1.63.531.2 ROM. It is fast, clean, everything works as it is supposed to work without any weirdness.
Thx for replies.
I can't get "MikTouch" or any other ROMs because I haven't "rooted" my phone yet. I never do anything if I don't fully understand "what it does", and since nobody have answered my questions here:
http://forum.xda-developers.com/showthread.php?t=1659952 -
and being new to Android and to this phone - I only did what I did understand... so my phone is unlocked but not rooted yet (and still with s-on).
What I did to get OTA update:
- I removed my SIM card
- I removed my microSD card
- Shutdown the phone.
Then I charged my phone and removed battery for few seconds when it was full, and inserted the battery and microSD card back (also I moved everything off the card and formatted on my computer before I inserted it back).
- Entered hboot menu (volume down + power button)
- Selected Factory Reset
After phone rebooted and started up it asked me to setup gmail account- I wanted to follow this "setup wizard", but without SIM card there was no data connection and it seems impossible to finish it without logging-in to gmail first (? it seems that way?) so I just cancel it and I setup my home wi-fi connection, and once I saw wi-fi working I restarted the phone.
"Setup wizard" started again after reboot and this time I finish setting up my gmail account.
- Then I had notification about HTC update available. I run it, and after it rebooted itself 2 times (maybe 3 times, I didn't stare at it all the time) it wiped out everything (I think) because it started with "setup wizard" again, so I knew it must have updated the ROM. I went to my phone's About Phone -> Software number and sure it is version "1.63.531.2.710RD" now
I have hard reset it again ("factory reset") and am using it since morning.
There are few changes I have noticed so far.
edit: Main difference I have noticed so far: "Visual Voicemail" somewhat partially work with my provider (Wind does NOt have visual voicemail). By partially I mean that now when I have new voicemail I also have another notification as if it came from the person who left the voicemail, saying for example "(number) I have left you a voicemail (length of the message). Press 00021 to listen to the message or go to voicemail" or something like this. When I touched the clickable "00021" it went straight to this message in my voicemail - nice! - even though Wind Mobile doesn't have Visual Voicemail, so I guess it is some general GSM networks option I didn't knew about. Anyways, with previous software I never had such message or notification, phone simply showed usual Voicemail icon and notification only.
MT4GS said:
Thx for replies.
I can't get "MikTouch" or any other ROMs because I haven't "rooted" my phone yet. I never do anything if I don't fully understand "what it does", and since nobody have answered my questions here:
http://forum.xda-developers.com/showthread.php?t=1659952 -
and being new to Android and to this phone - I only did what I did understand... so my phone is unlocked but not rooted yet (and still with s-on).
What I did to get OTA update:
- I removed my SIM card
- I removed my microSD card
- Shutdown the phone.
Then I charged my phone and removed battery for few seconds when it was full, and inserted the battery and microSD card back (also I moved everything off the card and formatted on my computer before I inserted it back).
- Entered hboot menu (volume down + power button)
- Selected Factory Reset
After phone rebooted and started up it asked me to setup gmail account- I wanted to follow this "setup wizard", but without SIM card there was no data connection and it seems impossible to finish it without logging-in to gmail first (? it seems that way?) so I just cancel it and I setup my home wi-fi connection, and once I saw wi-fi working I restarted the phone.
"Setup wizard" started again after reboot and this time I finish setting up my gmail account.
- Then I had notification about HTC update available. I run it, and after it rebooted itself 2 times (maybe 3 times, I didn't stare at it all the time) it wiped out everything (I think) because it started with "setup wizard" again, so I knew it must have updated the ROM. I went to my phone's About Phone -> Software number and sure it is version "1.63.531.2.710RD" now
I have hard reset it again ("factory reset") and am using it since morning.
There are few changes I have noticed so far.
edit: Main difference I have noticed so far: "Visual Voicemail" somewhat partially work with my provider (Wind does NOt have visual voicemail). By partially I mean that now when I have new voicemail I also have another notification as if it came from the person who left the voicemail, saying for example "(number) I have left you a voicemail (length of the message). Press 00021 to listen to the message or go to voicemail" or something like this. When I touched the clickable "00021" it went straight to this message in my voicemail - nice! - even though Wind Mobile doesn't have Visual Voicemail, so I guess it is some general GSM networks option I didn't knew about. Anyways, with previous software I never had such message or notification, phone simply showed usual Voicemail icon and notification only.
Click to expand...
Click to collapse
If you are "unlocked", you could easily flash CWM Recovery and other ROMS, it just requires an extra step since you are still S-On (flashing the boot.img through fastboot). Also, being unlocked means you can also easily root with just a simple flash. So, you could flash the MikTouch ROM and enjoy the same 1.63.531.2 level of service but in a more optimized and tweaked manner, that is also rooted.
But, if you're happy the way you are, then, "if it isn't broken, don't fix it".
Yes the MikTouch seems like the one I would love to try. I always prefer "minimal ROMs", because if I like the ROM I usually keep it forever and I don't want any obsolete app's "junk bytes" taking space inside the ROM image.
The stock 1.45.x and 1.65.x ROMs seem actually usable, but even though T-Mobile have crapped them with much less garbage (than what I usually saw in their Windows Mobile ROMs), there are still many "apps" I would like to get rid of. So yes, I would want to root my phone at least for "debloating" purpose.
Unfortunately most of knowledge and instructions here always assume the reader already knows more than "basics" about Android. But what is obvious to the devs actually often confuse noobs to Android like myself... That's why I'm still "stuck" unrooted yet.
For example:
You said "easily flash CWM Recovery" - OK, but what are the exact steps? (I have already asked this here: http://forum.xda-developers.com/show....php?t=1659952 ) Not to mention I still don't know which recovery I should actually go with (CWM or "Stock") and why...
MT4GS said:
Yes the MikTouch seems like the one I would love to try. I always prefer "minimal ROMs", because if I like the ROM I usually keep it forever and I don't want any obsolete app's "junk bytes" taking space inside the ROM image.
The stock 1.45.x and 1.65.x ROMs seem actually usable, but even though T-Mobile have crapped them with much less garbage (than what I usually saw in their Windows Mobile ROMs), there are still many "apps" I would like to get rid of. So yes, I would want to root my phone at least for "debloating" purpose.
Unfortunately most of knowledge and instructions here always assume the reader already knows more than "basics" about Android. But what is obvious to the devs actually often confuse noobs to Android like myself... That's why I'm still "stuck" unrooted yet.
For example:
You said "easily flash CWM Recovery" - OK, but what are the exact steps? (I have already asked this here: http://forum.xda-developers.com/show....php?t=1659952 ) Not to mention I still don't know which recovery I should actually go with (CWM or "Stock") and why...
Click to expand...
Click to collapse
Since you are S-On Unlocked, you could flash CWM Recovery (version 5.0.2.7). That gives you much more capability, like doing a nandroid backup/restore. You would do that using flashboot. Obtain the correct recovery.img, do fastboot flash recovery recovery.img and then you're ready. From then on you can boot into HBOOT, choose Recovery and then flash ROMs or other packages, including the SU (for rooting). The Miktouch ROM is already rooted, so all you would need is to flash CWM, then the ROM. Since it is still Sense, as soon as I signed in with Google, it automatically synced all my apps and contacts, which is a nice bonus.

[Q] Über-crash = reformat? What to do? thx

Hey gang -
Yesterday at home I pulled my phone out of my pocket and it was at the "touch the Android to begin" (!) screen. But it was still connected to my WiFi... And I was confused.
Rather than do that, I reset the phone, wiped Davlik cache and Fixed Permissions (took a long time!), then rebooted.
That sort of worked, but a LOT of my apps are crashing on start, and others are missing altogether. Even when I re-download them and re-install them, they don't work.
What's the way-ahead here? Am I stuck doing a factory reset? Or even formatting the SD card?
Thanks in advance.
When things get that fouled up, a clean install over a freshly formatted microSD is probably the best thing to do. You might be able to get away with restoring from a "nandroid" backup from before things started going bad, but "Your mileage may vary."
jeffsf said:
When things get that fouled up, a clean install over a freshly formatted microSD is probably the best thing to do. You might be able to get away with restoring from a "nandroid" backup from before things started going bad, but "Your mileage may vary."
Click to expand...
Click to collapse
Okay, thanks!
Anything else on the SD card I should back up besides DCIM / Media-> Ringtones/MP3s / "ui" / TitaniumBackup?
(Got about an hour while this stuff goes off to my HD...)
Hoo! Thought I effed myself for a sec - from CWM I was wiping all partitions... including /sdcard.
Then I realized... $#¡+... my ROM is on there!
Fortunately CWM has the "mount USB storage" option.
*whew!*
I was going to add format the sdcard from the phone. But you did that. Typically when what happened to you would happen to me it would be from some app updating and for whatever reason got corrupted during install and fouled the phone up. If you use TiB I highly suggest setting a automated task to back up your TiB backups to drop box, google drive or box.net. Then in these situations you have a recent TiB to fall back on.
JaimeZX said:
Hey gang -
Yesterday at home I pulled my phone out of my pocket and it was at the "touch the Android to begin" (!) screen. But it was still connected to my WiFi... And I was confused.[...]...a LOT of my apps are crashing on start, and others are missing altogether. Even when I re-download them and re-install them, they don't work.
Click to expand...
Click to collapse
Hi JaimeZX,
I am curious if you have recently rooted, flashed to stock, or installed the VB or Basic w/a twist kernel? I am running the exact same setup as you list (minus the modem) and this *exact* same scenario happened to me on the exact same day. March 12th, at about 10pm.
Detail as much information as you can, I've had many problems since flashing back to stock, formatting the SD, wiping everything multiple times, and re-installing Valhalla Black, Basic w/a Twist and all fresh apps d/l'd from the market. I'm on multiple attempts to stabilize the device and have questioned whether or not there is some issue with either the Rom or the Kernel. Perhaps there is an issue with the stock packages, or the USB driver ghosts (I've deleted all USB assigns at all ports and reinstalled for device detection in Heimdall). Hopefully we can get a good list of information to help us fix an issue that is apparently quite catastrophic (in that /data seems to corrupt) and save others from a future headache.
I have searched the dev threads to no avail, and as a general rule it seems that if problems are brought up they are usually met with "try flashing back to stock," "gremlins," "no one else is having problem 'X'," etc. even in cases of users with multiple complaints of the same issue. Both the DSP Sound force close upon EQ preset select and the issue that some had with the Messages, Phone Dialer, Search, Call Logs closing to homescreen are issues that I've seen this with. I believe this is a real issue, and I need to get it fixed without wasting time on messaging replies to anyone advising "try this," "Try that," etc.
My hope is that between the two of us we can address any of the common responses from developers before taking the issue to them and reporting it. I personally cannot today get my phone to boot without freezing (after boot cycle completes - not bootlooping or freezing during the bootleader seq) and am currently attempting to get into d'l mode without much luck.
When this happened to me on Tuesday night I was able to reboot to recovery, reflash the final-fixed.zip first without wiping data (which failed-/data is corrupted somehow here) and then *with* wipe/data and it booted, ran fine, so I then re-flashed BasicWithaTwist Kernel and was fine until late last night again.
I had been using the phone for some fairly constant web searching and the screen went black, appeared to soft reboot, and then froze. I pulled the battery, waited a few mins, reinstalled battery, once again, Freeze after boot.
No indication that an app crashes, phone just completely freezes, remains screen on, capkeys lit, power button does not respond, nor do softkeys or touchscreen. Makes it though the scan device and scan SD processes *sometimes* and other times freezes before it completes them.
I pulled the both the SD and the SIM and booted up, same issue, though it makes it through the scan device processes everytime since it's not scanning 18gb of data on an SD. This tells me it is not SD or SIM related, and is most likely software related, either ROM or Kernel. I've also ruled out the possibility of an old app/data package by reformatting the SD (long format - wipe all containers to "o,") let Android rebuild menu structure on SD, redownloaded a short list of commonly used apps and installed fresh - *NO* TiBackup apps were restored and the actual backup folder was not replaced to the SD after flashing.
I've tried both the Odin (Fb KJ6 back to stock) and the one click (lumin's tutorial) back to stock. Checked the download of Final-Fixed, MD5 checksum is correct. Cannot find MD5 on the sms-T959V-KJ6-antsvx.v1.1.3.zip file. Doesn't seem to be listed on Anton's github site, perhaps I don't know how to find it there. That is the only puzzle piece I haven't double checked.
All for now, looking forward to yours or anyone's replies or suggestions for anything I may be overlooking. Thanks.
0
---------- Post added at 11:19 AM ---------- Previous post was at 11:12 AM ----------
devlinandersen said:
Hi JaimeZX,
... I've had many problems since flashing back to stock, formatting the SD, wiping everything multiple times, and re-installing Valhalla Black, Basic w/a Twist and all fresh apps d/l'd from the market. I'm on multiple attempts to stabilize the device and have questioned whether or not there is some issue with either the Rom or the Kernel....
0
Click to expand...
Click to collapse
I should add that I have been on Valhalla Black Edition since it was in beta and have been quite happy with it. I only did a back to stock flash to try to (one more time) see if I could get a cooperative DSP sound manager. No such luck, and now a few headaches, and this issue on Tuesday coupled with yours in the exact same timeframe...I'm just thinking there is a problem somewhere in the chain of attack and hope to find it with the help of others.
Also, phone freezes after boot, needless to say, I'm not able to run a logcat.
devlinandersen said:
No indication that an app crashes
[...]
Also, phone freezes after boot, needless to say, I'm not able to run a logcat.
Click to expand...
Click to collapse
Try running logcat > /sdcard/some_file and cat /proc/kmsg > /sdcard/some_other_file so you have a capture of both the Android logs as well as the kernel logs. If you're not comfortable with command-line work, aLogrec should be able to at least help with the Android logs.
Given the number of people successfully running stock and custom ROMs on this device with stability, it either is going to be a hardware problem with your phone, corruption of a file system, or some app or combination of apps you are running, not a "dev" issue. Without logs, it is going to be nearly impossible to differentiate between the causes.
jeffsf said:
Try running logcat > /sdcard/some_file and cat /proc/kmsg > /sdcard/some_other_file so you have a capture of both the Android logs as well as the kernel logs. If you're not comfortable with command-line work, aLogrec should be able to at least help with the Android logs.
Click to expand...
Click to collapse
I will try in a bit, collecting files for another fresh install, different ROM.
jeffsf said:
Given the number of people successfully running stock and custom ROMs on this device with stability, it either is going to be a hardware problem with your phone, corruption of a file system, or some app or combination of apps you are running, not a "dev" issue. Without logs, it is going to be nearly impossible to differentiate between the causes.
Click to expand...
Click to collapse
This is false logic and is just what I was trying to avoid. I will attempt to explain to hopefully help build a stronger environment that is conducive to problem solving. It still very well could be a dev issue if say, a certain ROM or Kernel begins to wrestle with an app that has recently updated. Is it the apps or the rom's fault? Maybe it is a seldom used feature of an app that just missed all the users testing until now, it's well within the realm of possibilities and would just like to see helpful comments (such as the first portion directly above) to help solve issues. Truth is, I don't know *what* is wrong and neither do you, so a focus on constructive commentary would just help everyone out.
Logs or it didn't happen.
Update...
After a factory reset/data wipe, wipe cache, wipe dalvik cache I had to let the battery charge for a bit. Came back and decided to just try to boot phone, still freezes after boot sequence. I decide that I will flash a different kernel and a different ROM in order to see if I can make a difference. Before flashing Blastoff v2.5 Kernel I decided to factory wipe/data wipe, wipe cache and dalvik again...I am not sure if this is news, but when doing the Dalvik cache wipe in CWM it returned no result, perhaps because I had previously performed and is empty, but I thought it strange that there was *no* communication that it was already empty/wiped, etc.
Installed Blastoff v2.5 and was able to boot without freezing. Something else was damaged with the Rom as well, would not load home screen, only had pulldown menu. Rebooted to Recovery and flashed Unnamed RC-2.zip and have been charging the battery, talking on the phone and reinstalling apps from market.
Same error happened twice to me and once with Jaime. Both of us on VB and Basic+Twist. After installing new kernel i'd point towards kernel. Also uninstalled DSP and installed voodoo sound on VB, but had that on previous version as well. If I had to start somewhere, I'd start right around there.
Hope this helps, will provide logs from SD backup I made before reflash of new kernel/rom. Gotta run. Adios...
-devil.
I had to get my phone going today, it appears to be working without freezing, though on this new app the phone dialer/phone caller force closes on outgoing calls (I am only mentioning here, I will visit the Q&A for the ROM if I need assistance). Unfortunately I was unable to replicate the problem without flashing back to my previous nandroid. I have it saved and given some time I will do my due diligence and get a logcat **if** Jaime doesn't do it before me...because I kinda have a feeling that something was updated in the market on Tuesday evening that is now fighting with the kernel somehow. But again...I didn't run a logcat so it's not even happening...yet...
...to be continued...
Devlin - sorry for the delayed reply.
I did notice that I'd had more and more apps FCing on me in the week leading up to the Über-crash. Unfortunately I don't have any more "background" to add than that.
I backed up everything I wanted on the SD card and then formatted that, plus /data, /system /everythingelsethatwasanoptioninCWM. Then did my installs.
FORTUNATELY (knock on wood) I have not had any recurrence of the major issue.

Categories

Resources