Related
Let me start by saying I'm new to posting on these forums. I've been flashing roms now for over 7 months and have enjoyed it immensely.
The other day I ran into a problem that I've never had before. I was running Nil's 3.5 rom which is a great rom, and installed the V6 Supercharger Script (also great) to see how it would work with the rom. I installed everything, had V6 working and was prompted by V6 to change I believe it was /data and /cache files. I thought ok there shouldn't be a problem. So I ran V6 and everything seemed to run with no problems. Then things got a bit laggy so I decided lets try and uninstall V6 and see if that helps. V6 restored my settings that were backed up, and I uninstalled V6. I decided at this point to do a complete wipe and reflash the rom. This is when I encountered my problem.
I reboot the phone into recovery mode: (Using the lastest clockworkmod recovery)
wipe data factory reset
wipe cache partition
I go under mounts and storage, format
/boot
/system
/datadata
/data
/cache
I get an error stating "error formatting /data" and "error formatting /cache".
I am unable to restore any backups that I had already made because I receive this error message. When I install a new rom, I receive bootloops. The only rom that works, is Nils 3.5 rom that is still stuck on the phone, and when that loads, nothing works properly. I cannot download apps, the apps already installed force close on me.
I have no clue on what to do. Now I am asking myself, did I brick my phone? Any help, suggestions would greatly be appreciated.
Thanks
Update:
I decided to try downgrading to the official 2.2 stock version with S-On with hopes of trying to start from scratch and now I am stuck in bootloops. The phone goes to the red eye, pauses for about 20 seconds and reboots. Any suggestions on what to do now?
Just had this issue on my wife's phone. System random rebooted after an app update and now /cache and /data won't format. Nothing posts past the white Incredible screen.
Came up with some solutions that I have yet to try, but here's what I found:
http://forum.cyanogenmod.com/topic/32272-error-formatting-data-when-restoring/
http://forum.cyanogenmod.com/topic/6433-solved-messed-up-partitions-on-internal-storage/page__st__20
http://forum.cyanogenmod.com/topic/18288-error-formating-cache-wont-boot-past-htc-screen/
Looks like basically we need to force fix the file system and push something initial onto the phone though adb.
I'll keep this tab open and post my results as I try some fixes tonight on my wife's phone.
Bad news for you guys. I had this happen a month ago and could not fix it. Someone over at the CM forums helped me try and fix the partitions in the internal memory, but we both think the hardware was the culprit. I was under warranty still and got a replacement phone.
Link
That is the thread I'm following. So far I've had moderate success with the commands posted here:
http://forum.cyanogenmod.com/topic/...hen-restoring/page__view__findpost__p__250529
that are designed to totally re-create the partitions. Attempting to format at the moment from the phone recovery with no connection to the computer. I'm hoping this isn't all hardware related.
---------- Post added at 09:12 PM ---------- Previous post was at 09:11 PM ----------
Grr... still getting errors. Might be dead in the water.
After about a week and a half messing around with things, I have been unable to fix this issue. Luckily I was able to upgrade and went with the Rezound.
I was able to get the format data command to work from within CWM once or twice, but not consistently. I really do think my phone hardware failed. It is scary that if it happened three months later, I would have been out money.
If I'm not mistaken nils roms format the phone to a different type ext. You may want to find a way to reformat the phone to the stock ext. I may be completely wrong on this but since you currently have a brick it might be worth looking into.
Sent from my Incredible Stock+ Ginger Tiny
I've practically tried everything, I posted in the thread for the Team Vicious ROM about this problem, a received many responses. But so far all the proposed ideas to fix this problem have come to no success. I am left with the Google X boot animation every time I tried flashing.
I'm curious what would be the best plan of action for getting to Jelly Bean successfully?
Status of GN:
verizon ROM 4.0.4 stock (unlocked and rooted)
What I'm flashing?
Team Vicious 4.1 Jellybean ROM v3 + faux kernel
My process of flashing:
factory reset in stock ROM
superwipe, or do a format to (/dalvik-cache, /cache, /data, /system)
flash jb ROM
wipe cache again (sanity check)
umount /system and /data
reboot
wait up to an hour at least 15 minutes
The Result:
Google boot animation (X)
Frustrated user
restore nandroid backup
try again
unknownzero said:
I've practically tried everything, I posted in the thread for the Team Vicious ROM about this problem, a received many responses. But so far all the proposed ideas to fix this problem have come to no success. I am left with the Google X boot animation every time I tried flashing.
I'm curious what would be the best plan of action for getting to Jelly Bean successfully?
[note: I'm kind of new here, hope I posted in the right place]
Click to expand...
Click to collapse
Well what process have you been using?
What's the current stat on your phone? What ROM?
And as far as I know... your in the right place :cyclops:
Well...
I'm going to assume that you've waited a good 10-15 minutes during the first boot after installation? I haven't experienced it but I've read that pulling on first boot before getting to the opening screen may cause the phone to not boot fully. Again, I haven't experienced this, but FWIW.
Next I guess I would validate that you're not doing a dirty install (installing directly over a ROM without wiping). I've had good success using the 'super wipe' script prior to loading up a new ROM.
If you haven't gone through all of the dev forums I'd suggest at least starting here: http://thesuperusersguide.weebly.com/everything-jelly-bean.html
You'll find quite a bit of relatively up to date material for getting started.
Hopefully this helps, but what I would suggest is trying super wipe, then loading up your ROM. On first boot - walk away. Don't come back for 20 minutes. If it still hasn't booted at that point maybe try reverting back to 4.0.x, making sure your phone is working and then start over step by step.
I saw this morning that there is a one-click restoration script out there now, check this out for more info:
http://forum.xda-developers.com/showthread.php?t=1743939
Good luck!
Wolfbeef123 said:
Well what process have you been using?
What's the current stat on your phone? What ROM?
And as far as I know... your in the right place :cyclops:
Click to expand...
Click to collapse
The current state of my phone is restored to 4.0.4 stock, as always unlocked and rooted. The one I'm attempting to flash is the Team Vicious v3, I have already tried v1 and v2.
The processes I've been using are a combination of following directions, then trying to the superwipe, and some other scripts. Wiping /system /cache /dalvik-cache / data, then flashing, then wiping the aforementioned and flashing again. I've practically done almost every combination possible with no success.
windexh8er said:
Well...
I'm going to assume that you've waited a good 10-15 minutes during the first boot after installation? I haven't experienced it but I've read that pulling on first boot before getting to the opening screen may cause the phone to not boot fully. Again, I haven't experienced this, but FWIW.
Next I guess I would validate that you're not doing a dirty install (installing directly over a ROM without wiping). I've had good success using the 'super wipe' script prior to loading up a new ROM.
If you haven't gone through all of the dev forums I'd suggest at least starting here: http://thesuperusersguide.weebly.com/everything-jelly-bean.html
You'll find quite a bit of relatively up to date material for getting started.
Hopefully this helps, but what I would suggest is trying super wipe, then loading up your ROM. On first boot - walk away. Don't come back for 20 minutes. If it still hasn't booted at that point maybe try reverting back to 4.0.x, making sure your phone is working and then start over step by step.
I saw this morning that there is a one-click restoration script out there now, check this out for more info:
http://forum.xda-developers.com/showthread.php?t=1743939
Good luck!
Click to expand...
Click to collapse
I wait usually 20-30 minutes, but I notice that the device heat is not fluxuating ( to me that indicated very low usage) I have reverted to 4.0.4 stock after each attempt from a nandroid backup.
I have also md5 verified all the files against the ones listed one the page, in the case you wonder about dirty data. I'm tempted to try the superwipe, flash, factory reset, then flash, wait an hour. I don't do dirty installs also, I might be a little new here but I know not to do that. What else is there?
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?
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.
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!