If someone can solve my app issue there will be a reward in the form of a donation! How's that for an incentive?
I understand I posted a similar thread before to this but I wasn't resolved and I am completely out of ideas.
Which ever rom I'm on, which ever kernel, after a random amount of time using my phone an app with crash,
which seems to set off a chain reaction and then all my apps begin crashing.
It's usually google apps that start it, such as messaging, play store or contacts. Apex launcher also often gets affected.
Killing all apps and restarting the phone occasionaly fixes the problem for a little while.
I have used different kernels, used different android builds, factory reset the phone, wiped the sd card, cleared cache etc etc. Is this a hardware issue?
Things that might be worth knowing
When entering bootloader I get the following error messages:
Code:
Sd Checking...
Failed to open usb master mode
[COLOR="Red"][Preload] failed to open usb master mode[/COLOR]
[COLOR="Blue"]loading PJ46IMG.zip image...[/COLOR]
Failed to open usb master mode
[COLOR="blue"]Please plug off USB[/COLOR]
I can not save images, in other words it seems I cannot write to the SD card, looking in mounts and storage in CWM
reads:
Code:
unmount /cache
mount /data
mount /sdcard
mount /system
format /cache
format /data
format /sdcard
format /system
format /system
mount USB storage
Which implies that everything is unmounted? Surely this can't be right and this is why I cant write to SD? Mounting them fixes the writing to SD problem temporarily.
When I get problems occuring next time I'll try to capture screenshots. I really hope someone has an idea what's going on here, if it's hardware I guess I'm screwed as the phone is out of warranty? :S
I have attached logcat's from around when the crashing happened last time, maybe someone can skim through them and identify the issue? Thanks
did you try different gapps???
I've tried lots of different gapps, the miui Rom im using now came with gapps as well
Both of your observations are normal, no problem there.
App force closing does not relate to kernel.
You should make a logcat when the apps start crashing so someone can assist you in diagnosing the issue. (Google it if you don't know how)
Also try re-download the ROM, possibly could be corrupted ROMs that you flashed.
tomascus said:
Both of your observations are normal, no problem there.
App force closing does not relate to kernel.
You should make a logcat when the apps start crashing so someone can assist you in diagnosing the issue. (Google it if you don't know how)
Also try re-download the ROM, possibly could be corrupted ROMs that you flashed.
Click to expand...
Click to collapse
Ok I'll make a logcat now, cheers bud. And I have tried with multiple different roms so it seems unlikely its a download issue
Heres the files. It took me ages to get any results, its typical when you want it to crash, it doesn't! Can someone more tech savvy then me have a thumb through them and try to identify the issue? Thank you very much
I think there is errors in both the logs but more in the second!
Now offering a reward for some help leading me to resolving this issue
bump
Taking a look, check back tomorrow.
Sent from my HTC One X using xda app-developers app
hahhahhaaa said:
Taking a look, check back tomorrow.
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
Cheers man, really appreciate it!
If it helps, my hunch (baring in mind I'm not that savvy with this) is something to do with partitions unmounting themselves? when looking in CWM
sometimes they are mounted sometimes they aren't
That error in the bootloader is common for all phones, simply unplug the USB and replug it in.
The USB not mounting is caused by old CWM versions, here is the latest.
About the second problem, it seems you are using custom ROMS and the problem started by the SQL management (i would eliminate hardware as a cause)
But please inform me which Rom you are intending to use so I can confirm the procedure, and whether its Sense/Sense+/AOSP.
For now, try the following:
- Re-Install the Rom with SQL tweaks ON,EXT4 tweak, and FORCED GPU rendering OFF.(if options available)
- DON'T restore anything from the system partition
Are you using the latest CWM recovery v5.8.4.0?
The error you get in bootloader has nothing to do with apps crashing and is totally normal. Even I get the same error.
And like the guy above me told, the FC's are caused by SQlite trying to write to readonly databases.
Similar problems to this have been fixed by wiping phone. Have you restored app using e.g. titanium backup?
And also, try formatting sd-card using pc, not recovery.
Vcek said:
That error in the bootloader is common for all phones, simply unplug the USB and replug it in.
The USB not mounting is caused by old CWM versions, here is the latest.
About the second problem, it seems you are using custom ROMS and the problem started by the SQL management (i would eliminate hardware as a cause)
But please inform me which Rom you are intending to use so I can confirm the procedure, and whether its Sense/Sense+/AOSP.
For now, try the following:
- Re-Install the Rom with SQL tweaks ON,EXT4 tweak, and FORCED GPU rendering OFF.(if options available)
- DON'T restore anything from the system partition
Click to expand...
Click to collapse
I am using the most up to date version of CWM 5.8.4.0
What exactly is SQLite anyway?
Currently I'm using ADRH The ICS version, in the instilation I checked all the tweaks so I expect the EXT 4 tweak was on.
What do you mean about restoring from the system partition? I don't restore anything and still get the problems.
hahhahhaaa said:
Are you using the latest CWM recovery v5.8.4.0?
The error you get in bootloader has nothing to do with apps crashing and is totally normal. Even I get the same error.
And like the guy above me told, the FC's are caused by SQlite trying to write to readonly databases.
Similar problems to this have been fixed by wiping phone. Have you restored app using e.g. titanium backup?
And also, try formatting sd-card using pc, not recovery.
Click to expand...
Click to collapse
I have wiped using - Factory reset (bootloader), factory reset (CWM and factory reset in the phone (running sense)
And nope I left titanium backup alone. Do you mean as in mount storage and format in windows, FAT32?
[★] said:
I am using the most up to date version of CWM 5.8.4.0
What exactly is SQLite anyway?
Currently I'm using ADRH The ICS version, in the instilation I checked all the tweaks so I expect the EXT 4 tweak was on.
What do you mean about restoring from the system partition? I don't restore anything and still get the problems.
I have wiped using - Factory reset (bootloader), factory reset (CWM and factory reset in the phone (running sense)
And nope I left titanium backup alone. Do you mean as in mount storage and format in windows, FAT32?
Click to expand...
Click to collapse
Don't ever wipe from the bootloader if on custom roms/recovery.
Don't check all the tweaks, especially the force gpu rendering, this one is known well for causing FCs.
Sent from my EndeavorU
Unfortunately, i am still having the same problems that you are, and still cant seem to get my phone to boot, but i am on the latest Hboot 1.31 but still getting all the same apps crashing as you are
I am hoping for a potential Jelly bean RUU to released maybe?
try running in safe mode and see if a 3rd party app is causing this. Hold the turn off option in the power menu.
Vcek said:
Don't ever wipe from the bootloader if on custom roms/recovery.
Don't check all the tweaks, especially the force gpu rendering, this one is known well for causing FCs.
Sent from my EndeavorU
Click to expand...
Click to collapse
Alright I'll remember that next time haha! How come anyway?
Installed again, no tweaks, stripped it down with rom cleaner, disabled gps services and haven't (yet) synced my google account just to be safe, we will see what happens
Stuar said:
Unfortunately, i am still having the same problems that you are, and still cant seem to get my phone to boot, but i am on the latest Hboot 1.31 but still getting all the same apps crashing as you are
I am hoping for a potential Jelly bean RUU to released maybe?
Click to expand...
Click to collapse
It's a real pain isn't it! Yeah man the sooner the new RUU (1.28 first please!) come out the better.
Vcek said:
try running in safe mode and see if a 3rd party app is causing this. Hold the turn off option in the power menu.
Click to expand...
Click to collapse
I get this error before installing any apps usually so I dont think 3rd party apps have the chance to cause trouble
First problem which I have had before on a sense rom, Pressing the send button on a message does nothing. This usually leads to apps beginning to crash
Followed by a random screen 'turn off' and phone reboot followed by being stuck in splash screen
..Yep, still getting crashed. Can I reformat the whole memory? What would be the best way to go about this?
[★] said:
First problem which I have had before on a sense rom, Pressing the send button on a message does nothing. This usually leads to apps beginning to crash
Followed by a random screen 'turn off' and phone reboot followed by being stuck in splash screen
..Yep, still getting crashed. Can I reformat the whole memory? What would be the best way to go about this?
Click to expand...
Click to collapse
You could reflash the RUU file to get your phone back to stock and work from there. --this rewrites all partitions
You need to downloading it (there's a thread in android development listing them all), relock your bootloader, and run it as administrator from windows.
peedub said:
You could reflash the RUU file to get your phone back to stock and work from there. --this rewrites all partitions
You need to downloading it (there's a thread in android development listing them all), relock your bootloader, and run it as administrator from windows.
Click to expand...
Click to collapse
would this work for someone on jelly bean?
Related
So yea...as much as I know my desire's motherboard needs replacement...And I dont have warranty. Is there any way to fix it without changeing whole motherboard?
You provide us no information at all about what's wrong with your device.
What do you want to do with it? Solder stuff?
There is a 100% chance that you will destroy your phone when you open it and mess around with the subminiaturized highly vulnerable microelectronics.
There's something called insurance.
Swyped...
hypophysis said:
You provide us no information at all about what's wrong with your device.
What do you want to do with it? Solder stuff?
There is a 100% chance that you will destroy your phone when you open it and mess around with the subminiaturized highly vulnerable microelectronics.
Click to expand...
Click to collapse
It restarts,boot loop i think it's called. So I cant afford new motherboard so could I take my phone to some1 that knows what he's doing and could he fix it?
LordRyver said:
It restarts,boot loop i think it's called. So I cant afford new motherboard so could I take my phone to some1 that knows what he's doing and could he fix it?
Click to expand...
Click to collapse
Maybe the forum can help you
For this we need some more information:
1. Do you have the original HTC Sense ROM?
1a. If YES skip the points 2 - 5 and continue with 6.
2. If NO: which ROM you have installed?
3. Did you change the Radio ROM?
4. Have you unrooted your phone?
5. Are you S-Off / changed Hboot (partition table)
6. Do you use the original SD-Card?
7. Since your reboots started: have you installed any software just before?
8. Which program(s)
If you can answer these question we can help you - I don't think (hope) your motherboard is dead. Often there are simple solution to fix a "dead" phone
MonacoHias said:
Maybe the forum can help you
For this we need some more information:
1. Do you have the original HTC Sense ROM?
1a. If YES skip the points 2 - 5 and continue with 6.
2. If NO: which ROM you have installed?
3. Did you change the Radio ROM?
4. Have you unrooted your phone?
5. Are you S-Off / changed Hboot (partition table)
6. Do you use the original SD-Card?
7. Since your reboots started: have you installed any software just before?
8. Which program(s)
If you can answer these question we can help you - I don't think (hope) your motherboard is dead. Often there are simple solution to fix a "dead" phone
Click to expand...
Click to collapse
1. I had,but it used to turn off and get into boot loop while playing games like GRave defense. Never happened while playing shoot bubbules.
2. DevNull. First was dev,then leedroid,now back to dev. I keep him in sd card in case my phone wont turn on. Sometimes it restarts in middle of movie so I left him 2 times until morning and it first time turned on and second time didnt,again started to restart. Same with reflashing roms. Sometimes helps,sometimes no.
3.Yes.Radio_32.56.00.32U_5.17.05.08
4.Yes. I had hboot 0.83 or 0.93 and I used AlpharevX and then unrevoked.
5.Yes.
6.I dont know, I got it when I bought phone. (it was used when I bought it.)
7.Hm......Well...I dont think so...when I bought it, I turned phone off and after um... about 1 h I tryed turn it on and it started restarting. Then after some time turened on again.
And btw now it sometimes starts restarting not even hot.
So your problem is random reboots? or does your device not start up at all?
If the problem is just a bootloop, you won't need to replace the motherboard. You just need to flash the correct and working software.
mortenmhp said:
So your problem is random reboots? or does your device not start up at all?
If the problem is just a bootloop, you won't need to replace the motherboard. You just need to flash the correct and working software.
Click to expand...
Click to collapse
But that used to happened with original rom too...un...one guy said that bootloop is because motherboard is faulty. Now I just watched whole movie. And it was ok. But I tink if I would use market or opera it would restart. But im not sure. Sometimes it dosnt restart. And if I would flash all correct software my phone would turn on quicker?
oh god...
Don't answer my question with the word but. It's NOT an answer. So lets take the question again and this time do only reply to the question:
Is you problem random reboots or a bootloop?
Those 2 are NOT the same, while random reboots is exactly what the name implies a bootloop implies that your phone is unable to enter the android system due to a failure on startup.
So please in order for anyone to help you, you must make it very clear what you problem is, as otherwise we cannot tell you what to do.
Everything you have told up until now is that you have some problem(you use bootloop and random reboot equally) and that you might or might not know that it happens when running some specific apps.
mortenmhp said:
oh god...
Don't answer my question with the word but. It's NOT an answer. So lets take the question again and this time do only reply to the question:
Is you problem random reboots or a bootloop?
Those 2 are NOT the same, while random reboots is exactly what the name implies a bootloop implies that your phone is unable to enter the android system due to a failure on startup.
So please in order for anyone to help you, you must make it very clear what you problem is, as otherwise we cannot tell you what to do.
Everything you have told up until now is that you have some problem(you use bootloop and random reboot equally) and that you might or might not know that it happens when running some specific apps.
Click to expand...
Click to collapse
Sorry. By bootloop I mean my phone restarts and then just starts viberating and just stays in white htc logo screen. But after some time I can enter android system. This happanes when I do something with my phone.
If I may throw 2 cents in...
I do not know if this will be the fix for you, but if I had this issue, the first thing I would do is boot the phone up and wait until it loads properly (I gather it loads sometimes but not others, which is why you watched a movie??), make a Titanium backup of everything, then Nandroid backup.
Next, do full wipe
1 Factory reset
2 (in Mounts/Storage) Format Dalvic/data/sdext/system
3 (in Advanced) Wipe Dalvic cache.
Now reflash your ROM and restore Titanium.
Might all sound like basic stuff, but any time I have had issues with bootloops or FCs or whatever, it's usually because I didn't wipe properly. Now I always wipe everything with new ROMs and never have an issue.
If this doesn't help, you may commence panicking I'M KIDDING!!
777ace said:
If I may throw 2 cents in...
I do not know if this will be the fix for you, but if I had this issue, the first thing I would do is boot the phone up and wait until it loads properly (I gather it loads sometimes but not others, which is why you watched a movie??), make a Titanium backup of everything, then Nandroid backup.
Next, do full wipe
1 Factory reset
2 (in Mounts/Storage) Format Dalvic/data/sdext/system
3 (in Advanced) Wipe Dalvic cache.
Now reflash your ROM and restore Titanium.
Might all sound like basic stuff, but any time I have had issues with bootloops or FCs or whatever, it's usually because I didn't wipe properly. Now I always wipe everything with new ROMs and never have an issue.
If this doesn't help, you may commence panicking I'M KIDDING!!
Click to expand...
Click to collapse
Did that already...first time all was the same,but now looks kinnda better. If it wont go to restarting screen while chagring i'll be happy...After doing factory reset it started to move things from pc to sd very slowly.
777ace said:
If I may throw 2 cents in...
I do not know if this will be the fix for you, but if I had this issue, the first thing I would do is boot the phone up and wait until it loads properly (I gather it loads sometimes but not others, which is why you watched a movie??), make a Titanium backup of everything, then Nandroid backup.
Next, do full wipe
1 Factory reset
2 (in Mounts/Storage) Format Dalvic/data/sdext/system
3 (in Advanced) Wipe Dalvic cache.
Now reflash your ROM and restore Titanium.
Might all sound like basic stuff, but any time I have had issues with bootloops or FCs or whatever, it's usually because I didn't wipe properly. Now I always wipe everything with new ROMs and never have an issue.
If this doesn't help, you may commence panicking I'M KIDDING!!
Click to expand...
Click to collapse
Hello LordRyve,
follow the great description from 777ace , these are the steps which should bring your Desire back.
I only would not restore all the programs via Titanium Backup after your fresh install. The reason is that there might be a "bad" program you have installed before. Just restore a program, check if system runs without problems, then restore the next and so on.
But NEVER restore system apps via Titanium backup - this mostly WILL mess up your system!
And before flashing devnull ROM download it again and check the MD5SUM, just to be sure your downloaded ROM is ok.
Good luck
MonacoHias said:
Hello LordRyve,
follow the great description from 777ace , these are the steps which should bring your Desire back.
I only would not restore all the programs via Titanium Backup after your fresh install. The reason is that there might be a "bad" program you have installed before. Just restore a program, check if system runs without problems, then restore the next and so on.
But NEVER restore system apps via Titanium backup - this mostly WILL mess up your system!
And before flashing devnull ROM download it again and check the MD5SUM, just to be sure your downloaded ROM is ok.
Good luck
Click to expand...
Click to collapse
Well now it runs rll great And I didn't do anything different. It restarted while charging but at about 98% it was cold again and I succesufly turened it on with first try. If something will go wrong i'll try do 777ace guide. Now I would like to ask...what to do that files would get transefered from my pc to sd faster? Because when my battery is not full it starts charging and overheating and restarting. Also isnt overheating and restarting caused by bad motherboard?
MonacoHias said:
Hello LordRyve,
follow the great description from 777ace , these are the steps which should bring your Desire back.
I only would not restore all the programs via Titanium Backup after your fresh install. The reason is that there might be a "bad" program you have installed before. Just restore a program, check if system runs without problems, then restore the next and so on.
But NEVER restore system apps via Titanium backup - this mostly WILL mess up your system!
And before flashing devnull ROM download it again and check the MD5SUM, just to be sure your downloaded ROM is ok.
Good luck
Click to expand...
Click to collapse
Also if there is bad app,could I try downloading it again after restoring with titanium?
LordRyver said:
Also if there is bad app,could I try downloading it again after restoring with titanium?
Click to expand...
Click to collapse
Sure you can.
With a bad app I ment that an app can mess up your system (not a corrupted program file).
For example task killers I would name "bad" apps as they are useless in current ROM and maybe could things worse.
A very important tip at the end: perform Nandroid backups on a regular basis - so you can allways come back to a working system.
LordRyver said:
...
Now I would like to ask...what to do that files would get transefered from my pc to sd faster? Because when my battery is not full it starts charging and overheating and restarting. Also isnt overheating and restarting caused by bad motherboard?
Click to expand...
Click to collapse
Do you use Windows or Linux? For me file transfer on Linux is much slower compared to Windows. Sometimes it helps to switch to another USB port on your PC.
Does your Desire also restarts when you use the power supply (charging not via PC)?
MonacoHias said:
Do you use Windows or Linux? For me file transfer on Linux is much slower compared to Windows. Sometimes it helps to switch to another USB port on your PC.
Does your Desire also restarts when you use the power supply (charging not via PC)?
Click to expand...
Click to collapse
Windows. Yes. It gets overheat. And switching to another USB port didn't helped. But I noticed that usb cable's part that puts into pc was a bit hot.
MonacoHias said:
Sure you can.
With a bad app I ment that an app can mess up your system (not a corrupted program file).
For example task killers I would name "bad" apps as they are useless in current ROM and maybe could things worse.
A very important tip at the end: perform Nandroid backups on a regular basis - so you can allways come back to a working system.
Click to expand...
Click to collapse
hm...I think problems start when I install classic ghost radar
Ok...can some1 explain me. my phone started to restart while moving movie from pc to sd. Now it's cold. But when I turn it on, it loads and after 1 sec in android system it starts restarting again. why?
I have an Htc incredible rooted 2.3.4
i have recently run an RUU utility to fix something but that was some time ago
So yesterday i installed an app "Linux Installer" and it told me to intalls something on data/local which turns on to be phone storage and i get a message saying "Low Space" long story short i tried deleting it, only way i could was by doing a format phone storage.. but then it boots up and i get the message saying "system UIDs Inconsistent" UIDS on the system are inconsistent, you need to wipe your data partition or your device will unstable and a button saying "im feeling lucky".
So i boot in the hboot menu wipe cache, dalvik and do a factory reset and problem hasnt gone away and is worse now, i cant use the buttons and every app keeps force closing. Please Help
increibleADR619 said:
I have an Htc incredible rooted 2.3.4
i have recently run an RUU utility to fix something but that was some time ago
So yesterday i installed an app "Linux Installer" and it told me to intalls something on data/local which turns on to be phone storage and i get a message saying "Low Space" long story short i tried deleting it, only way i could was by doing a format phone storage.. but then it boots up and i get the message saying "system UIDs Inconsistent" UIDS on the system are inconsistent, you need to wipe your data partition or your device will unstable and a button saying "im feeling lucky".
So i boot in the hboot menu wipe cache, dalvik and do a factory reset and problem hasnt gone away and is worse now, i cant use the buttons and every app keeps force closing. Please Help
Click to expand...
Click to collapse
You could try fixing permissions thru recovery but i doubt if that will help. Your best bet would be to wipe everything in mounts and storage in the recovery menu, and then restore a backup from before you tried the linux app. Also i believe amon ra recovery has an option to repair uid mismatches, but i think its much like fix permissions in cw and probably wont do you much good.
yes i have tried it "fix permission" didnt help but theres an issuse and that is that i thought a had a backup but when i tried using it says "checking MD5 sums..."
"MD5 mismatch!" Another thing im not really into roms but is there a way of installing one without actually using my phone, ive tried cyanogen 7 before and didnt like it and recommendations and a point to the right direction will appreciated.
Also when you say wipe everything from mounts and storage do you mean everything because there are a lot of thing there saying "format"
increibleADR619 said:
Also when you say wipe everything from mounts and storage do you mean everything because there are a lot of thing there saying "format"
Click to expand...
Click to collapse
Jermaines stock plus rom (http://forum.xda-developers.com/showthread.php?t=1260994) is probably for you, it has the original look with some added features, and is very stable. You will have to use the phone to flash any rom.
Sorry should have been more clear,by wipe everything i mean everything except sdcard and emmc, which are your storage areas. This will essentialy wipe your phone clean leaving it fresh for a backup or new rom install.
wiil give it a try
Installed stock plus, no problems. Still wish to know how to fix that without having to restart all over
Sent from my ADR6300 using XDA App
increibleADR619 said:
Installed stock plus, no problems. Still wish to know how to fix that without having to restart all over
Sent from my ADR6300 using XDA App
Click to expand...
Click to collapse
Me too! Had to do full wipe :'(
I also had this issue after installing a stock 2.3.4 Rom. It alerted me on the first boot up that I had mismatched UID's, then never told me again. However, many functions didn't work on the phone, and installing a different Rom fixed the problem. Sucks to have to start over, but that's part of the fun!
Probably the cleanest solution HERE
cmlusco said:
You could try fixing permissions thru recovery but i doubt if that will help. Your best bet would be to wipe everything in mounts and storage in the recovery menu, and then restore a backup from before you tried the linux app. Also i believe amon ra recovery has an option to repair uid mismatches, but i think its much like fix permissions in cw and probably wont do you much good.
Click to expand...
Click to collapse
Probably the cleanest solution HERE
I have an ongoing issue with Galaxy W phone and CM.
The problem is that the phone spontaneously decides to not boot.
I had run CM10 from first Alpha, and on a couple of occasions it would, after several days or weeks use, stay on the CM spinning logo, and refuse to go to interface.
I got around this by keeping a couple of Nandroids handy and just restored them when the boot issue occurred.
On subsequent fresh install, I ran for a couple of weeks with virtually no app installations, to see if something I was running was causing the issue. Turns out no relationship.
I have just flashed Alpha 7 of CM 10 and now its doing it again. This is a fresh install.
I re-downloaded the ROM from the second mirror, and tried flashing with that, but get the same result.
Is it possible the flash memory in my phone is faulty? On a PC if you install an OS - fresh install - and it wont boot, generally its either RAM or HDD. Given this is a recurring issue, I wonder if its the phone, rather than the OS thats causing the problem - as I have tried with several of the Alphas and both download locations of the most recent Alpha and its still happening.
Can anyone suggest?
Is there a chkdsk option for phone flash memory?
thanks
Jim
[edit] just installed CM9 (last beta) and its doing the same thing - stuck at boot animation and will not get to desktop.
Anyone? Any ideas how to fix this?
Sv: [Q] CM10 A7 ongoing boot issue
Flash stock rom and see if the problem still exists. If not, flash cm again. If it does, get a new phone.
Sent through time and space from my s3mini.
16kzx81 said:
I have an ongoing issue with Galaxy W phone and CM.
The problem is that the phone spontaneously decides to not boot.
I had run CM10 from first Alpha, and on a couple of occasions it would, after several days or weeks use, stay on the CM spinning logo, and refuse to go to interface.
I got around this by keeping a couple of Nandroids handy and just restored them when the boot issue occurred.
On subsequent fresh install, I ran for a couple of weeks with virtually no app installations, to see if something I was running was causing the issue. Turns out no relationship.
I have just flashed Alpha 7 of CM 10 and now its doing it again. This is a fresh install.
I re-downloaded the ROM from the second mirror, and tried flashing with that, but get the same result.
Is it possible the flash memory in my phone is faulty? On a PC if you install an OS - fresh install - and it wont boot, generally its either RAM or HDD. Given this is a recurring issue, I wonder if its the phone, rather than the OS thats causing the problem - as I have tried with several of the Alphas and both download locations of the most recent Alpha and its still happening.
Can anyone suggest?
Is there a chkdsk option for phone flash memory?
thanks
Jim
[edit] just installed CM9 (last beta) and its doing the same thing - stuck at boot animation and will not get to desktop.
Anyone? Any ideas how to fix this?
Click to expand...
Click to collapse
What do you mean by clean install?
wipe data and cache?
Try to format /system /data /cache and /sdcard (backup your internal storage first)
MiguelPT said:
What do you mean by clean install?
wipe data and cache?
Try to format /system /data /cache and /sdcard (backup your internal storage first)
Click to expand...
Click to collapse
Thanks guys, very much for your replies
By "clean install" I have gone to wipe menu of CWM and wiped everything, then CM with wipes, then Gapps.
Ok so I need to try to flash with stock ROM. I had considered that but could not find an Australian ROM in the I8150 section of the Forum. Can anyone tell me where I can get one from?
- or -
-- maybe its ok to flash with any English ROM - will achieve the same thing? - sorry if this is a dumb question - I just dont want to make the situation any worse
Try Removing all SD Card,SIM and battery. Then reinsert battery after 15 minutes and reflash the CM10/Stock ROM. It will boot up
miki2o said:
Try Removing all SD Card,SIM and battery. Then reinsert battery after 15 minutes and reflash the CM10/Stock ROM. It will boot up
Click to expand...
Click to collapse
Ok. Thanks for the suggestion. I did that and its stuck on the Logo still. No change.
You can get stock ROM for Australian (Vodafone) from here http://www.hotfile.com/dl/187592956/3abb3c5/I8150TDULM1_I8150TVAULG1_VAU.zip.html
arya_ruby said:
You can get stock ROM for Australian (Vodafone) from here http://www.hotfile.com/dl/187592956/3abb3c5/I8150TDULM1_I8150TVAULG1_VAU.zip.html
Click to expand...
Click to collapse
Thanks very much for the link I have downloaded it
So I noticed something else thats kinda weird.
When I go to /sdcard, its not showing the content of the sd card
So if I swap out the card, it still loads the same folder, not the stuff from the sd card I have inserted.
I have a few of these. All read fine in the PC, but the phone does not seem to recognise the files, as they dont change if I reboot with a different card/different content in.
/sdcard
Code:
../
.android_secure/
Android/
LOST.DIR/
RZR/
Video/
cm-10-2013~ancora-alpha7.zip
gapps-jb-~signed.zip
SD card contents when read from PC
Code:
I8150TDULM1_I8150TVAULG1_VAU.zip
Its as though it has a partition called /sdcard, and can't mount the content of the physical card itself. Anyone seen this before? Is there a way to re-partition internal memory?
16kzx81 said:
Thanks guys, very much for your replies
By "clean install" I have gone to wipe menu of CWM and wiped everything, then CM with wipes, then Gapps.
Ok so I need to try to flash with stock ROM. I had considered that but could not find an Australian ROM in the I8150 section of the Forum. Can anyone tell me where I can get one from?
- or -
-- maybe its ok to flash with any English ROM - will achieve the same thing? - sorry if this is a dumb question - I just dont want to make the situation any worse
Click to expand...
Click to collapse
Just do full wipe you'll not wipe cwm!
My suggestion: Go the Pristine™ Way.
(thread in the General forum)
Sent from my GT-I8150 using xda app-developers app
arya_ruby said:
You can get stock ROM for Australian (Vodafone) from here http://www.hotfile.com/dl/187592956/3abb3c5/I8150TDULM1_I8150TVAULG1_VAU.zip.html
Click to expand...
Click to collapse
I tried that zip, but it started to install and the phone shut down/restarted at beginning of install (just after wipes)
Can anyone else confirms this file actually works?
Is there a Tread source I can refer to?
pepoluan said:
My suggestion: Go the Pristine™ Way.
(thread in the General forum)
Sent from my GT-I8150 using xda app-developers app
Click to expand...
Click to collapse
Thanks for the suggestion. I tried but the problem persists.
Ok here it goes. my network service is off so i use my droin inc for games and such. running custom rom wildstang83 IceCream Scencless 1.0. im not sure what happened to my phone but i left for 3 days and come back to my phone being totally jacked up. It wot dl apps the google play reverted back to the old market icon. wont save my passwords for google sighn in. every time i go to youtube it says to re dl the google play services. im sure other stuff is messed up too. i have tried to flash another rom but when it gets loaded back up it keeps saying process. whatever failed and there a bunch of those that loop and i have to pull battery. when i try to factory reset it says everything was formatted but when i reboot phone its the sme as it was before apps and all. So is there anyone out there who can help me with this. Sorry if i posted in the wrong place or what not. i wasnt sure where to post it cuz its kinda an advanced question but not really a question just need help.
not a virus but it does sound like your phone might have exhausted all the space in the /data folder. I had a similar thing happen to me before I rooted and fixed my phone where i exhausted the space, itt went a factory reset and put the phone into an unusable state.
i don;t know anything about the rom you are running but are rooted and have CWM installed? if so, you should be able flash a new ROM to your device, GAPPS and optionally, the low space disk fix.
tekweezle said:
not a virus but it does sound like your phone might have exhausted all the space in the /data folder. I had a similar thing happen to me before I rooted and fixed my phone where i exhausted the space, itt went a factory reset and put the phone into an unusable state.
i don;t know anything about the rom you are running but are rooted and have CWM installed? if so, you should be able flash a new ROM to your device, GAPPS and optionally, the low space disk fix.
Click to expand...
Click to collapse
Yes i do have cwm but i tried to flash a new rom via the recovery section. after i choose the zip to flash everything goes as expected untill after the reboot and it goes into the setup part where u have to put gmail password and stuff in then it basically freezes up with unlimited process failures. but i will try again. cant hurt from where it is now.
if you are not doing so already, i would wipe cache and dalvik cache after flashing the rom. that may fix the FCs.
I would also suggest you run a newer jelly bean ROM like Tiny;s 5-16 with his version of GAPPS(4-05) version plus the low space disk fix so you can maintain parity with what is the latest.
I am currently using evervolve 6-25 and it is working well for me.
the reason I say that is these newer JB roms have the ability to let you skip the activation easily. I don;t know if it was some feature of GB roms but the activation wizard in the JB roms seem to be better my opinion.
When switching to a different ROM, it is crucial to wipe /system. This can be a source of FCs. Also, if switching, it is also a good idea to do factory reset.
tekweezle said:
if you are not doing so already, i would wipe cache and dalvik cache after flashing the rom. that may fix the FCs.
I would also suggest you run a newer jelly bean ROM like Tiny;s 5-16 with his version of GAPPS(4-05) version plus the low space disk fix so you can maintain parity with what is the latest.
I am currently using evervolve 6-25 and it is working well for me.
the reason I say that is these newer JB roms have the ability to let you skip the activation easily. I don;t know if it was some feature of GB roms but the activation wizard in the JB roms seem to be better my opinion.
Click to expand...
Click to collapse
I just flashed another rom i used in the past by the same dev and so this is my step by step. 1. choose zip from sd. 2. factory reset. 3. wipe dalvik cache. 4. wipe cache partition. If this doesnt work i will try jb roms but i would hate to have to dump the dev that im useing. there the most stabe roms i have come across so far
PonsAsinorem said:
When switching to a different ROM, it is crucial to wipe /system. This can be a source of FCs. Also, if switching, it is also a good idea to do factory reset.
Click to expand...
Click to collapse
what do u mean wipe /system. where do i find that. only reason i ask is cuz maybe ive never done that. but i have never had a problem withthe other 15 roms i have flashed before so thats why im so confused about what happened to my phone. all i did was shut it off and leave it home. nothing changed from my daily use before that and it was working top notch before i shut it off
im getting settings fc. youtube fc, my uploads fc, market fc, clock widget fc, internet fc, rss reader fc, htc sence fc, all those off of a fresh flash ad new sd card
Just lost my bckups that were saved on sd card so now i cant even get on it i dont get it. its not bricked but yet it i unstabe to run any rom but the preivious saved backup (now there deleted)
maybe the rom you downloaded is corrupt. worst case scenerio is that your phone is on it;s last legs.....
i would suggest you try downloading the JB rom and Gapps plus the low space fix.
http://forum.xda-developers.com/showthread.php?t=2050930
it;s kind of proven to work in my opinion. the 5-16 build is pretty stable.
what I do is flash the rom zip, gapps zip and low space zip, then wipe cache and dalvik. it probably should not make a difference but I am using TWRP as my recovery instead of CWM.
goodluck!
tekweezle said:
maybe the rom you downloaded is corrupt. worst case scenerio is that your phone is on it;s last legs.....
i would suggest you try downloading the JB rom and Gapps plus the low space fix.
http://forum.xda-developers.com/showthread.php?t=2050930
it;s kind of proven to work in my opinion. the 5-16 build is pretty stable.
what I do is flash the rom zip, gapps zip and low space zip, then wipe cache and dalvik. it probably should not make a difference but I am using TWRP as my recovery instead of CWM.
goodluck!
Click to expand...
Click to collapse
Thank u and its still not working. probably just takeing a dump on me now it is just bootlooping.
when i do a factory reset i get a wipe completed. but it says "no app2sd partition found. Skipping format of /sd-ext" could that be part of the issue?? ive never noticed that before
i don;t know if switching to TWRP might help you but it might be worth a try. maybe a coincidence but the last time I had a screw up on my Dinc installing a ROM, i was using CWM. I switch right after that. I think i did read something about TWRP specifically supporting the EXT4 Low space fix.
maybe someone more knowledgable can chime in.
tekweezle said:
i don;t know if switching to TWRP might help you but it might be worth a try. maybe a coincidence but the last time I had a screw up on my Dinc installing a ROM, i was using CWM. I switch right after that. I think i did read something about TWRP specifically supporting the EXT4 Low space fix.
maybe someone more knowledgable can chime in.
Click to expand...
Click to collapse
i will try it but it is doing the same thing on every rom i have tried to flash. ive tried 6 different roms so far and i have ran them all in the past so im incined to think its jacked. and is there a specific twrp for the different roms or can i just dl the latest version and it will work
Hey everyone,
Whenever I decide to step away from stock and try a new custom ROM (latest being cm11), my phone won't go a day(well, more like 5 hours) without rebooting and hanging at the boot animation. I'm not sure if its the number of apps i install (like 30 including gapps), or something I'm missing, but its not limited to just one rom. I've tried miui, dirty unicorns, revolt, paranoidandroid, all great ROMS, but they don't LAST!
I'm really sorry if I seem like I'm repeating an already-asked question, but I've researched this problem and tried suggestions such as going back to stock and retrying, using Darkside scripts to wipe, wiping cache and dalvik cache and rebooting, wiping android.secure or moving apps away from sd card, etc. Nothing works. So for now I'm back on stock and not enjoying it I just wanted to know if theres anyone that might have any idea how to fix this?
Thanks!
EDIT: To sum up the thread so far, now instead of wiping completely everytime this occurs, i just need to do a battery pull to fix it. However, its really annoying to do 3-4 times a day. Another thing I might note is that my device is refurbished(mentioned below). I did more research and found some fix perms script reccommended by Real_Pariah, which was supposed to fix the issue. It didn't. Also same problem does happen with stock, I've just never stuck with it long enough to find out. At UltimaniumX's suggestion, I did a logcat, which is attached on the last post. Thanks UltimaniumX for your help so far!
So the way I understand it, you've flashed different custom ROMs and they work fine, but after an unspecified amount of time they decide to reboot and hang?
What is the exact process you're using to flash the custom ROMs? As well, each ROM has a specific method to get it working on your phone.
What recovery are you using and what version is it?
What radio are you using?
UltimaniumX said:
So the way I understand it, you've flashed different custom ROMs and they work fine, but after an unspecified amount of time they decide to reboot and hang?
What is the exact process you're using to flash the custom ROMs? As well, each ROM has a specific method to get it working on your phone.
What recovery are you using and what version is it?
What radio are you using?
Click to expand...
Click to collapse
Yep, that's correct. As for exact process, usually I just full wipe everything but sd, then flash.
For my kitkat roms(paranoidandroid, cyanogenmod 11, beanstalk), i flashed used cwm recovery 6.0.4.3. For jelly bean i used either twrp 2.4.4.0 or cwm 5.x(this was in earlier attempts as that was the recovery a guide on galaxys2root instructed me to flash to root stock in the first place). All used radio UVMC6.
Even on stock it happened, but I was able to fix by wiping cache and dalvik plus removing external sd.
When I first rooted, my major issue was getting the rom to get past the animation screen while hanging, and that still occurs, though lately I've been having some success using rom manager from stock to get to cm11(without ext sd). However that does reboot eventually. The first time I was able to fix it by wiping system, android.secure, cache, and dalvik and then reflashing, but it just happened again and that method doesn't seem to be working...
It's interesting that it's happening to all different ROMS that you install. There's a possibility that it's hardware related and not software related. Though I may not be the best to offer advice (since I've only been here for about a year), I recently installed Beanstalk after going through several troubleshooting steps that I finally resolved.
I know that my friend and I both have an SG2. We installed Jedi Knight 6 (which is an older ROM now) but one of the most important steps that he missed, was that he didn't leave his phone idle for 10 minutes after booting it up for the first time. I recall he had issues with apps not working, force-closing, and irregular reboots on his phone. This may or may not been an issue for you, but for awareness sake I leave it here.
If you want you can give Beanstalk another try since I have some experience trying to get it to work. Beanstalk requires you to use a very specific recovery, and I used TWRP 2.6.1.0 straight from the author's post. I wouldn't suggest using a higher version just because KitKat is new.
- I used INFAMOUS wipe cache to clear everything, and then I did a full wipe (including preload) using TWRP.
- Install Beanstalk 4.4 and the 4.4 GAPPS
- Boot and let sit for 10 minutes.
Once you know for sure that it's been 10 minutes, run the "Android Terminal Emulator" and do a logcat. Here's how to do it:
- Type su
- Type logcat -d -f /sdcard/logcat.log , it will save a .log file where your sdcard is.
- At this point, I guess you would have to leave it running until your phone decides to reboot. Then take that file from your SD and examine it on your computer.
http://wiki.cyanogenmod.org/w/Doc:_debugging_with_logcat
See if that helps. Fixing Permissions may also help reset some of your system settings. If it does the reboot loop, try rebooting into recovery, Fix Permissions, and reboot it again.
Alright I'll try Beanstalk, nothing to lose except my cookie clicker progress
Funny same thing happened in stock but was fixed in stock recovery with simple data wipe. I remember about hearing someone downgrading to ics because of "jelly bean bugs", so if beanstalk doesn't work out I'll try that!
(Couldn't straight reply/quote cause I can't post links yet)
EDIT: can't find beanstalk thread, at least cant find one mention twrp, so i wasnt sure if i was on the right one
Alright Beanstalk up and running, waited 10 minutes, and ran logcat command, however, it went back to prompt after running, so I'm not sure if its running in the background or if it dumped the current log and stopped. I kept terminal running just in case.
Quick side question, do you know if beanstalk disables long press home for recent apps? When I try long-press home it brings up the bottom menu instead.
Also, thanks for your help
So Beanstalk was running all fine and dandy as usual when a random reboot occured. However this time it actually got past the bootanimation. But, it asked me to set the default launcher again and terminal wasn't working(no text on screen). So I rebooted and whaddya know, stuck at bootanimation. Tried fixing perms, didn't work.
I tried wiping cache and dalvik, and reinstalling(which after restarting twrp asked if i wanted root and i said no, maybe thats significant?), nope, now no bootanimation. :'(
I forgot to mention that it is refurbished, so maybe that's of significance? Honestly though, now I'm at a loss of ideas.
avbluestar14 said:
Alright Beanstalk up and running, waited 10 minutes, and ran logcat command, however, it went back to prompt after running, so I'm not sure if its running in the background or if it dumped the current log and stopped. I kept terminal running just in case.
Quick side question, do you know if beanstalk disables long press home for recent apps? When I try long-press home it brings up the bottom menu instead.
Also, thanks for your help
Click to expand...
Click to collapse
If you followed the logcat instructions, the file logcat.log is now saved in your sdcard. The Terminal Emulator would not show anything other than that the logcat has been created. Now all you need to do is go to your SD card and grab that file "logcat.log", it will contain a lot of information regarding the state that your phone is in. It's good that you kept the terminal emulator running otherwise the file would not populate with anything. If you can, attach the logcat so we can see it.
Beanstalk long-press home button should show recent apps like normal. I can't remember if the default launcher shows it, since I use Nova Launcher and can confirm that long-press still brings up recent apps.
avbluestar14 said:
So Beanstalk was running all fine and dandy as usual when a random reboot occured. However this time it actually got past the bootanimation. But, it asked me to set the default launcher again and terminal wasn't working(no text on screen). So I rebooted and whaddya know, stuck at bootanimation. Tried fixing perms, didn't work.
I tried wiping cache and dalvik, and reinstalling(which after restarting twrp asked if i wanted root and i said no, maybe thats significant?), nope, now no bootanimation. :'(
I forgot to mention that it is refurbished, so maybe that's of significance? Honestly though, now I'm at a loss of ideas.
Click to expand...
Click to collapse
Right, it seems like if this is occurring on all your ROMs, that may indicate something hardware-related. Again, it's difficult to diagnose. What happens when you go back to the stock rom? Is it T-Mobile's version and it works fine?
This may seem like a stupid question, but you have rooted your phone right?
UltimaniumX said:
If you followed the logcat instructions, the file logcat.log is now saved in your sdcard. The Terminal Emulator would not show anything other than that the logcat has been created. Now all you need to do is go to your SD card and grab that file "logcat.log", it will contain a lot of information regarding the state that your phone is in. It's good that you kept the terminal emulator running otherwise the file would not populate with anything. If you can, attach the logcat so we can see it.
Beanstalk long-press home button should show recent apps like normal. I can't remember if the default launcher shows it, since I use Nova Launcher and can confirm that long-press still brings up recent apps.
Right, it seems like if this is occurring on all your ROMs, that may indicate something hardware-related. Again, it's difficult to diagnose. What happens when you go back to the stock rom? Is it T-Mobile's version and it works fine?
This may seem like a stupid question, but you have rooted your phone right?
Click to expand...
Click to collapse
yeah, stock works fine. about the logcat..I had restarted to try and fix that home button issue like an hour after starting the logcat, which means i inadvertently stopped terminal. whoops. so, i will try beanstalk again, making sure to keep terminal running i guess. sorry about that! might as well see whats in the current logfile for now. also, yes phone is rooted.
I think we're out of options at this point. My last and only recommendation that I can think of is to just install TWRP 2.6.1.0 (and it HAS to be this), and do a full wipe of the phone.
That means:
- factory reset,
- wipe data
- wipe SYSTEM
- wipe cache
- wipe dalvik
- reinstall the same UVLC3 radio (you're on Tmobile I think right?)
- install Beanstalk, install the 4.4 GAPPS (make sure it's the 4.4 apps)
- reboot the phone from recovery.
- let sit for 10minutes
- run logcat to your sdcard,
- observe and post the logcat if the system reboots itself.
UltimaniumX said:
I think we're out of options at this point. My last and only recommendation that I can think of is to just install TWRP 2.6.1.0 (and it HAS to be this), and do a full wipe of the phone.
That means:
- factory reset,
- wipe data
- wipe SYSTEM
- wipe cache
- wipe dalvik
- reinstall the same UVLC3 radio (you're on Tmobile I think right?)
- install Beanstalk, install the 4.4 GAPPS (make sure it's the 4.4 apps)
- reboot the phone from recovery.
- let sit for 10minutes
- run logcat to your sdcard,
- observe and post the logcat if the system reboots itself.
Click to expand...
Click to collapse
right, isn't UVMC6 the latest? i already have beanstalk running after full wipe, if it don't work, im going to repartition with one of old gb roms and pit file and go from there. no reboot on beanstalk yet, logcat is running though. Googling it, a lot of gs2 have problem with this sort of thing it seems.
avbluestar14 said:
right, isn't UVMC6 the latest? i already have beanstalk running after full wipe, if it don't work, im going to repartition with one of old gb roms and pit file and go from there. no reboot on beanstalk yet, logcat is running though. Googling it, a lot of gs2 have problem with this sort of thing it seems.
Click to expand...
Click to collapse
well beanstalk restarted on friday, can't find anything significant in logcat except for sometimes a long list of apps with perm issues,,,even stock has this reboot problem, but a battery pull+cache wipe fixes it(i hope). After googling, many have this problem with jb... maybe ill try an ics rom or something
hmm, back on cyanogenmod 11, and when it stuck at boot, a battery pull did the trick...running logcat overnight.
Well, here's the logcat, perused through, not sure if the errors I'm seeing are normal or not...honestly I wouldn't know what's contributing to the random reboot, and I'm not reporting it to cyanogenmod because I'm not sure if its a fault of their rom, my phone, or me lol
I took a look at the logcat, and there doesn't seem to be anything that would show a fatal error of some sort. Unfortunately there isn't a guide on how to read logcats, so I'm going off of the little experience that I know. Did the logcat run up until the phone reboot?
Again this may seem like a stupid question, but you are sure that you're using an SGH-989 samsung galaxy s2 and not the I-1900 right?
UltimaniumX said:
I took a look at the logcat, and there doesn't seem to be anything that would show a fatal error of some sort. Unfortunately there isn't a guide on how to read logcats, so I'm going off of the little experience that I know. Did the logcat run up until the phone reboot?
Again this may seem like a stupid question, but you are sure that you're using an SGH-989 samsung galaxy s2 and not the I-1900 right?
Click to expand...
Click to collapse
Yep, logat was running up to reboot. It is a SGH-t989, ordered straight rom tmobile site refurbished. I still think its weird how a simple battery pull fixes it though, is it corrupted memory? or partitions? or some hardware on the device?
Sorry man, looks like there really isn't any other suggestions that I have.
There is another user who seems to be having the same issue as you.
http://forum.xda-developers.com/showthread.php?t=2573854
It looks like he was able to resolve it by slowly flashing ROMS starting from 4.1.2. You will have to ask him exactly how he did it, but his story of ROM issues seems exactly the same as yours.
UltimaniumX said:
Sorry man, looks like there really isn't any other suggestions that I have.
There is another user who seems to be having the same issue as you.
http://forum.xda-developers.com/showthread.php?t=2573854
It looks like he was able to resolve it by slowly flashing ROMS starting from 4.1.2. You will have to ask him exactly how he did it, but his story of ROM issues seems exactly the same as yours.
Click to expand...
Click to collapse
Ah I saw that thread, new plan of action:
1. Hard reset, go to stock, try it for a day, see if it randomly reboots.
2. If it does, get a replacement after Christmas since 90-day warranty. If it doesn't, try AOSP 4.1.2.
3. If AOSP 4.1.2 doesn't reboot, go from there.
Well, I'll make sure to update after I get through. Thanks again!
Well, RMA'ed and now everything's working fine, running latest beanstalk, so i guess some partitioning or hardware issue? Oh well, thanks for your help!