Hey guys. as many of you know i am no stranger to the Android system, although i have been pretty much totally absent from the forums since i got a job with limited privelages on my comp.
Before I explain what happened to me, i should say that i have not made ANY changes to my system for at least 4 months, with the exception of build.prop updates, which i my phone has been running fine on for weeks. i found a setup i liked and ive been running it, along with the same root applications, for quite some time.
With that said, heres my timeline of events:
Normal day, doing what i always do on my phone everyday: phone was plugged in to a wall outlet at my desk. streaming music, browsing web, youtube, etc. nothing out of the ordinary
i first noticed something wierd was up when i went to install an old .apk i had saved on my sd card. i opened it through file manager which, naturally, brought up the stock package installer. i clicked ok to install, and it said "installing"..however it nevver finished. it was stuck on "installing" for several minutes. i tried a couple more times, same thing kept happening. i had no idea what was going on.
i went into settings>applications>manage applications. i scrolled down to package installer and clicked on it, with the intention of clearing cache/data, however the values never loaded, it just kept saying "computing". it was doing that for all other apps i checked as well.
then i opened titanium backup and wiped data for package installer through that. operation was performed successfully.
i went to reboot my phone, and thats the last thing it remembers. now whenever i try to turn my phone on, it gets past the kernel splash screen and its all black from there (i have the "no boot anamiation" command in my build.prop). the only response i get at that point is the led buttons will light up if i tap them. i have to pull the battery to turn the phone off/reboot.
i tried pushing packageinstaller.apk to /system/app using adb but that didnt solved anything. i also tried wiping cache/dalvik and fixing permissions through clockwork. nothing has worked.
i am running Froyo Trigger w/ Bali kernel.
sorry for the long post, but i figured id be as detailed as possible to minimize questions.
any suggestions would be great. i ask that no one please suggest factory reset/reflash/odin. i realize that those options are there, but i consider them last resorts. id rather brainstorm a solution than bail immediately.
thanks ahead.
also i forgot to mention, there was nothing wrong with the .apk i was originally trying to install. i have installed it/uninstalled it many times. i tested other .apk files i had, but package installer still behaved the same way
Got your PM
Have you tried to capture a logcat while you're phone is booting? That might tell us what is failing or hanging your boot cycle.
I wouldn't call Odin a last resort personally. Most of the time its the cleanest way to get back to a perfect running state.
Try to get that logcat though, and post it up here. It might not work at all, depends on whether the phone even gets to the portion of the boot cycle where logcat even works, but its worth a shot if you want to investigate the problem.
Br1cK'd said:
Got your PM
Have you tried to capture a logcat while you're phone is booting? That might tell us what is failing or hanging your boot cycle.
I wouldn't call Odin a last resort personally. Most of the time its the cleanest way to get back to a perfect running state.
Try to get that logcat though, and post it up here. It might not work at all, depends on whether the phone even gets to the portion of the boot cycle where logcat even works, but its worth a shot if you want to investigate the problem.
Click to expand...
Click to collapse
not sure if i should be embarrassed to admit this, but ive never used logcat...ill look into that
Your first step there is to get the android sdk setup on your pc, then once adb is part of your command line the simple command is "adb logcat" without it quotes. That will start the log displaying in the command line window.
There are other options with the logcat command, that output the log to a text document and its more in depth, but I dont remember it off the top of my head. Maybe someone can post it for you.
The only caveat is how far your phone is booting before it hangs, I think logcat will show something, but won't know for sure until you try it.
Sent from my ZenDroid, meditating on the XDA App
http://forum.xda-developers.com/showthread.php?t=1319802
Eugenes Froyo that doesn't brick, followed by an Odin to jfd.
Sent from my SGH-T959V using XDA App
Related
I cannot find out whats going on with my phone. Ive tried 3 different roms, kernals, radios and settings and I cannot find whats going on with the phone. It locks up for the weirdest reasons at the weirdest time. I cant track down whats causing it, and it is completely random.
Heres a log cat Ive got from BAMF 3.0 RC1 stock kernal MR2
http://www.mediafire.com/?uxljp5prhzff8f7
and another
http://www.mediafire.com/?b9oc6x78ujk7axu
Please help... any ideas will help me out
BTW ive also tried all different kernal speeds and governers
Anytime i connect to usb for logcat it locks right away, and when I pull a logcat on the phone through a terminal emulator i get a the normal thread, but then one always pops up...
E/IPCThreadState (random numbers) failed to find cpu subsys
... any ideas?
http://pastebin.com/CLvMv5HC
^ During this logcat
First boot, fresh install of the new BAMF build 3.0 RC1. Phone is still running and responsive at this point. Ill try and get another when it locks
Didn't look as I can't on my phone but are you undervolting?
Sent from my ThunderBolt using XDA Premium App
joshnichols189 said:
Didn't look as I can't on my phone but are you undervolting?
Sent from my ThunderBolt using XDA Premium App
Click to expand...
Click to collapse
Im running the kernals supplied and without editing them it will still do it
Can you please re-up your logcat dumps and put them on something a bit more friendly like pastebin.com?
Also, what exactly are you doing when you dumped these logcats (both in the foreground and background), just to get an idea of what was going on your phone at the time.
Were these lockups happening on froyo as well?
yareally said:
Can you please re-up your logcat dumps and put them on something a bit more friendly like pastebin.com?
Also, what exactly are you doing when you dumped these logcats (both in the foreground and background), just to get an idea of what was going on your phone at the time.
Were these lockups happening on froyo as well?
Click to expand...
Click to collapse
Ill link them now in the OP
altimax98 said:
Ill link them now in the OP
Click to expand...
Click to collapse
as far as what i was doing..... nothing most of the time lol. most of the time it would lock on connecting to a PC, other times it wont wake up, then some of the times it will lock in the middle of scrolling through tapatalk or browser. its completely random and i can track it down
See if you can find out what process that is (2660) or whatever happens to be in the current error message. Process ID will probably change over time, but it's linked to some process on the phone.
You can find out about the current processes by typing:
Code:
ps
in the terminal emulator
EDIT: Just randrom things that might be causing problems, but cant say for sure:
The error you're getting I think happens when a process is in sync with another end and something more or less hangs up on it or goes out of sync so it can no longer find it. Pretty sure it's related to the davlik vm. If so, try going into recovery and clearing your normal cache and your dalvik vm cache under advanced. If that doesn't work...see below:
1) did you restore any data from previous roms/builds for this? Either previous GB ones or from froyo?
2) since it happens when connecting to the pc, it could be the htc hub crap that's causing the problem. If so, i would try disabling or removing the app, it's not that needed.
3) Are you using setcpu? It might be interfering with things.
Did you wipe data and cache prior to flashing? I've found a lot of my issues are corrected by wiping app data with Titanium b/u.
Well guys thanks for all the assistance. Ive tracked it down to being the speedtweak.sh script. Something just never quite worked right and whenever i would set the speed, governer or attempt a tweek it would then start the errors.
On the new 3.0 Build with the toolkit i dont need to manually go into the script and it seems to work fine. it may have been user error, or something just didnt jive with the phone...
although i still get the same cpu subsys error, but no locks so far
Hi everyone. It's been two days since the process com.google.process.gapps has started crashing, "stopping unexpectedly" whenever i use the browser on my tab.
Reading the error report, it seems (not 100% sure about that) this is somehow related to the bookmarks sync with Chrome, but i can't find a way to disable this.
Has anyone exprerienced the same issue? Any known solution? Thanks
Go to settings > accounts and sync, click on your account then uncheck everything, then manually sync everything one by one to see what is causing the error.
Then go to manage apps and clear the cache of all the problem apps and re-sync them once you're done. It might take a few tries but it should take care of that error.
I'll try that as soon as possible, thanks!
browser sync was causing this for me
I believe that bookmarks sync no long works with galaxy tab. Google changed something on their end that should have worked fine(it still works on the xoom, transformer, etc.) but since samsung changed a bunch of stuff for no apparent reason, it is now broken. samsung is so stupid sometimes..
So you're basically suggesting that bookmarks sync should stay off to avoid problems like that?
well I don't really know. I never used bookmark sync in the first place. I'm just going by what is said in this article.
http://www.zdnet.com/blog/perlow/br...gle-or-the-oems/17840?tag=mantle_skin;content
It turns out that at some point Google started making some changes to the backend systems that handle Google’s user account data. There’s nothing wrong with them doing this; it happens all the time. In fact, no other Android 3.1 tablets had any issues at all with the changes, and their bookmark sync continued to work without a blip on the radar.
Not Samsung, however... I did some digging around the internet, and it’s become somewhat well-known amongst Android developers that Samsung actually modifies core source code in the Android operating system that handles communicating with Google’s backend data services.
Click to expand...
Click to collapse
Well, that's a pity. I had just started to think it was a useful tool to keep track of unread web pages between work, home and outside...
Let's hope Samsung somehow fixes that.
PS: disabling bookmarks sync actually stops the process from crashing, I think I've solved (if we could really say so...) the issue. Thanks to all!
Thanks, disabling auto sync for browser has stopped the error. Samsung developers need to fix this - I can't auto sync my gmail
What am I missing here?
Ok be prepared, this post may be rather long winded however I will try my best to prevent that. I have a Tmobile G2x I purchased on launch date. Ive not attempted to Root, change roms, or anything of the sort. (as much as I always wanted to, I always felt that my skills were not good enough to attempt these ideas no matter how easy they may seem. I just did not want to be the cause of screwing up my phone that I paid dearly for)
So I have a friend who claims to be the master (of disaster so it turns out) of rooting androids and such. He stops by my house just to hang out and eventualy convinces me to let him root my phone and install CM7. Within a few minutes the phone was rooted (super1click) and was running CM7 release candidate. (I really dont know what all these things truly are but I drilled him for answers once he jacked up my phone and left me with a half-bricked phone) So he installed Rom manager and convinced me to upgrade to the premium version via marketplace so I did. He was then showing me how easy it was to flash new roms at the touch of a few buttons. He put on some other rom which looked like CM7 but claimed to have extra tweaks. It worked fine. A few minutes later he put on some Faux Rom which gave a boot up screen like my old Nexus One did. (Multicolored X) It seemed to work fine as well. Then he said lets check out the nightly CM7 Rom so he put it on. (however I dont think it ever actually put CM7 back on.-still on Faux?) Thats when things got crazy.
Now I get the com.google.process.gapps force close message all the time. He tried to fix it for 4 hours and finally gave up. Here is what I know he/we tried: After searching the internet for hours we tried everyone elses ideas. Clearing calenders cashes, un syncing, etc. We did about 40 factory resets. We have tried to install my backup (which was from BEFORE he even touched my phone) and upon holding both volume rockers and plugging in USB (no battery installed) and it still does nothing. Windows recognizes device but phone screen stays black. Tried Debug mode while doing this as well. If we hold the volume down button and power the little install bar comes on the screen and it does its thing (whatever that is) and goes right back to the way it was. I keep getting the gapps message all the time. After factory reset I cant even type in my gmail address to start the initial setup of the phone. The force close keeps cutting me off. If I type fast, I can sync the account but I cant use market whatsoever. Tried installing Rom manager to re-flash but just sticks at starting download and gapps pops up again.
My son is starting school tomorrow and he has a medical condition. I NEED this phone to communicate with the school nurse via emails and such. As of now I can only text, call, or surf web all while dodging force closes. If ANYONE out there can please help me get my phone back to normal Id greatly appreciate it. Im sure its something easy but as I said before, Im not good at this thing and thats why I never attempted it myself. Your welcome to submit answers here or PM me your phone # if you want to walk me through it on the phone. (I have a landline phone to talk to you on) Thanks in advance for everyones time and Im sorry this ended up being so long.
Hello,
Based on your post, I would suggest that you search your phone's development forum on XDA for a compatable clockwork recovery mod which will install a custom recovery on your phone. The thread will give you instructions on how to do so and how to enter recovery mode.
You can then enter the 'Backup and Restore' part of the recovery and restore your backup manually without using ROM manager. If this doesn't work, I would suggest that you then download the ROM of your choice and install it from the clockwork recovery. Make sure you clear user data and wipe the cache before you install.
Any fix yet? This is really annoying me as I rely on my bookmarks tremendously.
try this:
Open stock browser and under settings choose clear cache and deletehistory
Well, I posted about this in another thread but figured I would post here to get more exposure.
So, here is the issue. I rooted my NT and renamed the LatinIME.apk to LatinIME.apk1 so I can move my swiftkey apk (which I was going to rename LatinIME.apk). Of course, I had a blonde moment and renamed the built in APK before renaming the swiftkey apk and I lost the keyboard. No big deal right? Just reset device. So, I reset by going into settings and doing the reset/deregister device. Got back into the set up....still no keyboard. So I tried a hard key reset (n and power) and still no keyboard.
It appears that, when doing a reset, the device wipes all data but does not actually RESET the OS through any recovery type process.
Question........any ideas? I can't get adb obviously because I have lost debugging.
Curious if there might be anyway to boot the device differently to access shell or something. Hopefully someone has an idea, I have to wait tell monday to replace it if it comes to that
what about installing nook color tools then you can get back to the development menu. enable usb debugging and take care of the rest with adb.
Drewmungus said:
what about installing nook color tools then you can get back to the development menu. enable usb debugging and take care of the rest with adb.
Click to expand...
Click to collapse
As I understand it. Nook color tools is an apk...which I cannot install due to not being able to get past the B&N account login screen. Can't get past that without a keyboard
I'm in a similar boat. Was trying to get the market working following the thread on the other page, and I copied the entire apps folder over my existing one (why I didn't backup the old one!) Now I have no keyboard either, and I'm getting constant force closes!
Maybe someone could post an un-modified system folder?
Try a failed 8 boots, turn on, after black N screen hold power until screen turns off and repeat 8 times.
^. After a certain amount of failed boots the nook will default into a total factory reset. Witnessed it earlier today when after installing Chainfire the NT went into a a boot-loop. Then automatically reset itself.
Worth a shot.
Well, I tried 8 failed boots, and it didn't re-image. I then peeked in the rom/devconf/ folder and there's no "bootcnt" file?
*edit* Got it to work. Took 10 times.
Ok, so I kept trying to boot which resulted in it eventually giving me a screen saying "please reboot your device. If the error continues contact customer support or goto nook.com/tablet/support". The website was no help. Took it to a store, they called customer support and got confused. Customer support told them to replace it. So they did...I didn't even have to give back my charger...so now I have an extra!
Returns
I really hope B&N Customer Support figures out it would be a heck of a lot cheaper to let us run our own image off an SD card, and not have to deal with all the customer support calls and returns.
Unfortunately - they are much more likely to yell Warranty Violation and refuse to do anything...
Would it have been possible to mount the device and access it from Ubuntu and then just renaime the file?
Got mine to re-image. Re-rooted and market installed. I'm happy again!
Sent from my BNTV250 using Tapatalk
Details please. How did you do it?
You power down, then power back on. As soon as the white screen comes up (with the "n" on it) hold down the power button until it powers down again. Do this ten times in a row and it will automatically start the re-image. If at any time the boot animation starts up you have to start over.
Sent from my BNTV250 using Tapatalk
tonyp22 said:
Would it have been possible to mount the device and access it from Ubuntu and then just renaime the file?
Click to expand...
Click to collapse
For the particular issue I was having...no. Since I reset the device I was not able to get past the B&N login screen and therefor had no access to the /system/app folder. Although, it seems that some people are having success with the re-image process. I think mine was trying to re-image but something was corrupt and caused my to have worse issues that resulted in nothing but replacement.
Hi all. New to the forums...watched the degrading vid before signing up even and am somewhat newby with phones. I've scoured this site, the motorola support site...which is apparently down til next week now...and a few other sites I came across via pages of google searching. I cannot find the answer other than doing a factory reset...which I really do not want to do as I have a LOT of apps and info of my phone. It should all be backed up via motoblur and the lookout app's backup. But I have months worth of scheduling info in there which will take me more hours to reenter...I reeeeeally don't want to if I don't have to.
Problem: My Atrix 4g is caught in a bootloop. While this is a somewhat common problem, mine seems to be a little different. I'll point form details below and will greatly appreciate any help I get. If you need any more info, please let me know.
-caught in a boot loop. It boots regularly, but reboots about every 2 minutes. There is a good 30-45 seconds where I can access apps etc. However, I don't think that the phone completely finishes its boot cycle before rebooting.
-Occasionally...and I believe ONLY after I reboot via the down volume/power button method...the phone will stay on long enough to receive notifications from the web. Facebook notifications etc etc. Most of the time it doesn't.
-If I had to guess, it's trying to boot some app near the end of its boot cycle that it doesn't like. And I'm assuming it just doesn't like this app's latest update as I've never had this problem before.
-Prior to rebooting via volume/power button, I was getting an error message which I wrote down...and have since accidentally erased. It was something along the lines of "system process failed" and I then had the option of force close or wait.
-Every 3 seconds or so, my notification light flashes purple. It typically shows green during startup, red for notifications...I've never seen purple before.
-I downloaded almost every app I could over the last 10 days of 10, 10c apps from the market.
-I haven't opened most of the apps, and haven't had any problems with any apps that I have opened
-Most of my apps are set to auto-update. Therefore, I don't know which app update could be the problem...assuming this is the problem
-I'm in the process of removing my apps 1 at a time every 2 minutes or so...as I get a chance during the final stages of the phone's rebooting. So far, 10 apps in and no success. Only another 200 apps or so to go. ugh...
Any ideas? help? booze?
Thanks in advance.
How about wiping the cache and Dalvik cache? This will not affect or uninstall any of your apps or personal info.
Sent from my MB860 using Tapatalk
Thanks for the advice and quick response. I don't seem to be able to clear the dalvik cache without rooting the phone...is this correct? Went thru the market for dalvik cache cleaning apps and they all require root. My phone isn't rooted.
ok if your not rooted does this mean your on a stock rom? is it possible one of these 200+ apps are a virus or malicious? root your phone use titanium backup to backup all your apps and factory reset or go try and get a replacement and keep your sd wich will have the backup
I had a boot loop problem too once. Turned out to be a defective SD card. removed it and it booted. It could not be read by any PC either so it was definitely dead.
How's it going, everyone? I just want to apologize ahead of time if this is in the incorrect forum. There's so many to choose from and I didn't see one dedicated to this particular tablet.
I recently acquired a Verizon Ellipsis 8 and the first thing I wanted to do with the device was root it. After trying what must have been 10-15 different methods, I was finally successful at getting the device rooted using a (What I assume to be) Chinese root method called Kingroot. They had support for the tablet and actually got me root access, so I went with it. Shortly after, I installed all my necessary root apks and got the device working in what I would describe as acceptable order. I then began hunting for custom ROMS for the thing, but if there was one thing harder to find for this tablet than root access, it was a custom ROM.
Anyways, I've been living quite happily on rooted stock. I removed all the unnecessary bloatware from the device and everything has been going smoothly, until a few days ago. Verizon pushed out an OTA update and now I am receiving daily prompts from Verizon to update to the latest firmware. Now, this isn't my first rodeo when it comes to dealing with OTA updates, so I began digging around inside my system files to find the update.zip and disable it, as well as remove the different processes that would possibly be spamming this update notification. After several different files given the .bak extension and several different reboots, I felt comfortable that I had taken care of the issue. Hell, I even went so far as to take the same steps on my wife's tablet (She has the same one, rooted in the same fashion), and HER tablet has stopped sending her updates. HOWEVER, even though I have taken all the necessary steps, I still get the same prompt on my tablet at least once a day.
Now, I know for a fact the update files have been disabled, because last night I decided to test the update to see if it would actually go through, but it always results in the same error and the update doesn't apply. But no matter what, the prompt still shows up for me the next morning.
The prompt itself is quite annoying. It takes up the entirety of the screen, disables all other functionality of the tablet and doesn't let me choose other processes, and makes me select one of two options: Either I choose to apply the update, which immediately fails, or I can choose to delay the update to a different time during the day. If I could grab a screenshot, I'd show you guys what it looks like. But, I literally can't do anything on my tablet until after I make that selection, which immediately closes the process. That means I can't freeze the process using TitaniumBackup or something like that. I am helpless to suffer these update prompts every morning.
Now don't get me wrong. I'm not ever going to actually run the update, but the reminder is just such an inconvenience. So, I thought I'd make a post and see if there's anything you guys can think of that might be able to help me find whatever is causing these prompts and get rid of it. I've disabled the update.zip, I've disabled notifications from the Google Play Services, and I've rid myself of all the unnecessary bloatware on my device. I left a few Verizon processes on the tablet that I wasn't 100% sure if they were safe to remove or not, and I've even installed the FOTAKill.apk to see if that would help. The update doesn't work, but the prompt still shows up every morning.
I'd be forever in your guys' debt if you could help me on this one. Thanks for the read, and thanks ahead of time for any help! =D
metalslug53 said:
How's it going, everyone? I just want to apologize ahead of time if this is in the incorrect forum. There's so many to choose from and I didn't see one dedicated to this particular tablet.
I recently acquired a Verizon Ellipsis 8 and the first thing I wanted to do with the device was root it. After trying what must have been 10-15 different methods, I was finally successful at getting the device rooted using a (What I assume to be) Chinese root method called Kingroot. They had support for the tablet and actually got me root access, so I went with it. Shortly after, I installed all my necessary root apks and got the device working in what I would describe as acceptable order. I then began hunting for custom ROMS for the thing, but if there was one thing harder to find for this tablet than root access, it was a custom ROM.
Anyways, I've been living quite happily on rooted stock. I removed all the unnecessary bloatware from the device and everything has been going smoothly, until a few days ago. Verizon pushed out an OTA update and now I am receiving daily prompts from Verizon to update to the latest firmware. Now, this isn't my first rodeo when it comes to dealing with OTA updates, so I began digging around inside my system files to find the update.zip and disable it, as well as remove the different processes that would possibly be spamming this update notification. After several different files given the .bak extension and several different reboots, I felt comfortable that I had taken care of the issue. Hell, I even went so far as to take the same steps on my wife's tablet (She has the same one, rooted in the same fashion), and HER tablet has stopped sending her updates. HOWEVER, even though I have taken all the necessary steps, I still get the same prompt on my tablet at least once a day.
Now, I know for a fact the update files have been disabled, because last night I decided to test the update to see if it would actually go through, but it always results in the same error and the update doesn't apply. But no matter what, the prompt still shows up for me the next morning.
The prompt itself is quite annoying. It takes up the entirety of the screen, disables all other functionality of the tablet and doesn't let me choose other processes, and makes me select one of two options: Either I choose to apply the update, which immediately fails, or I can choose to delay the update to a different time during the day. If I could grab a screenshot, I'd show you guys what it looks like. But, I literally can't do anything on my tablet until after I make that selection, which immediately closes the process. That means I can't freeze the process using TitaniumBackup or something like that. I am helpless to suffer these update prompts every morning.
Now don't get me wrong. I'm not ever going to actually run the update, but the reminder is just such an inconvenience. So, I thought I'd make a post and see if there's anything you guys can think of that might be able to help me find whatever is causing these prompts and get rid of it. I've disabled the update.zip, I've disabled notifications from the Google Play Services, and I've rid myself of all the unnecessary bloatware on my device. I left a few Verizon processes on the tablet that I wasn't 100% sure if they were safe to remove or not, and I've even installed the FOTAKill.apk to see if that would help. The update doesn't work, but the prompt still shows up every morning.
I'd be forever in your guys' debt if you could help me on this one. Thanks for the read, and thanks ahead of time for any help! =D
Click to expand...
Click to collapse
You will need to modify your build.conf to prevent the update screen from prompting you.
Change the build number to something else....
/system/build.prop
Change the build to something like: ro.build.display.id=AKOT49HA
and do the same to the rest of them in the file.