Related
Hey guys, got a few problems after I flashed this rom. Hope you can help.
1st. For some reason, I cannot get the phone to boot with my memory card I partitioned for use with A2SD. If I take it out, it will boot up fine. Also I cannot format it back to its standard form. I.e. It is currently formatted to 6.9GB whereas before it was around 7.6GB. I haven't yet installed A2SD due to the fact the phone wouldn't boot correctly.
2nd. I flashed the Rom and everything was fine, until I partitioned my memory card. When I had the problem, I was booting the phone and then inserting the card after it had finished booting. For some reason, the apps I had installed had disappeared and I had to reinstall them but as soon as you reboot the phone, they're gone again. This also happened with Wi-Fi tether, which comes stock on the Rom. I have now changed the memory card to a normal unpartitioned card and the phone is fine. Apps stay as they should. I have performed several factory resets and the Wi-Fi tether still hasn't returned. I will re download the Rom again and try and install it again.
Thanks
Liam
Hi Liam,
sounds very much like an A2SD issue to me. I was waiting for others who use A2SD to reply to you but I personally will suggest that you head on over to the modaco forums android.modaco.com/forums.html and ask there.
the rom originates from Paul's forum and the best resource will likely be found there.
Best Regards,
Lawrence
here is what i would suggest:
- do a full wipe
- repartition your sdcard in recovery menu
- flash the rom
if you still experience problems give us the logcat output of the boot process.
Hi,
I ve been through all this forum and the rest of the internet, but I couldnt find the answer ... so hopefully you will help me.
I have Desire Z - about 3 months old.
I ve rooted the phone and flashed to cyanogenmod 7.1 stable. All the time Ive followed guides here or on cyanogen section/wiki. CM has been running stable for a month maybe until today.
This morning I couldnt make a call - so I rebooted phone.
After reboot phone gets to the home screen and automatically reboots itself after 5 seconds.
info from hboot
VISION PVT ENG S-OFF
HBOOT-0.84.2000 (PC1011000)
MICROP-0425
eMMC-boot
OS ver 1.34.707.3
CID 1111111111
Click to expand...
Click to collapse
Ive already tried:
Wipe cache / davik cache
Wipe battery status
Recover to CM - backup created right after first flash - successfully - problem remains
Recover to original ROM - successfully - problem remains
any ideas?
also - if you dont have any advice to fix this problem - Id like to ask you, if you could point me to the best way, how to unroot/(s-on) etc. phone and make it look like its like stocked one for the purpose of waranty. - i dont mind any data nor in phone nor on sdcard, everything I need is synced to gmail acc. Thank you
cyber-mythius said:
Hi,
I ve been through all this forum and the rest of the internet, but I couldnt find the answer ... so hopefully you will help me.
I have Desire Z - about 3 months old.
I ve rooted the phone and flashed to cyanogenmod 7.1 stable. All the time Ive followed guides here or on cyanogen section/wiki. CM has been running stable for a month maybe until today.
This morning I couldnt make a call - so I rebooted phone.
After reboot phone gets to the home screen and automatically reboots itself after 5 seconds.
info from hboot
Ive already tried:
Wipe cache / davik cache
Wipe battery status
Recover to CM - backup created right after first flash - successfully - problem remains
Recover to original ROM - successfully - problem remains
any ideas?
also - if you dont have any advice to fix this problem - Id like to ask you, if you could point me to the best way, how to unroot/(s-on) etc. phone and make it look like its like stocked one for the purpose of waranty. - i dont mind any data nor in phone nor on sdcard, everything I need is synced to gmail acc. Thank you
Click to expand...
Click to collapse
Pull /proc/last_kmsg and see what it says; should help you narrow it down.
Sent from my HTC Vision using XDA App
could you gimme hand how? - the only point where I can get in the phone is to bootloader / recovery.
so i cant run terminal from apps in phone.
+ could anyone help me how to charge up battery with my problem? I have about 20% on both batteries and I dont want to loose them during repair progress.
to the /proc/last_kmsg - i could not find anything like this on sd
cyber-mythius said:
+ could anyone help me how to charge up battery with my problem? I have about 20% on both batteries and I dont want to loose them during repair progress.
to the /proc/last_kmsg - i could not find anything like this on sd
Click to expand...
Click to collapse
Sorry, I just got to work. The last_kmsg is on your device, not the sdcard. If you have ADB set up you should be able to access it by connecting your phone to your computer
Sent from my HTC Vision using XDA App
I have everything installed on the other PC where Ill be on monday. Maybe Ill find some time to look through it tommorow.
Thank you now for pointing me somewhere - Ill add more info when I ll have it.
I had a similar problem after flashing new rom. My Desire Z was also rebooting after a few seconds.
I downloaded 1.34.707.3 firmware(used to downgrade Desire Z from gingerbread) from CM wiki, installed it through fastboot (step 8) , rooted my phone once again following the wiki and since then my phone is working without any problems.
Battery can be charged up while the phone is turned off.
well I flashed phone with the downgrading rom as you mentioned and it helped a little
- phone is running and not restarting after few seconds - but randomly after 5-60 seconds (so I am able to do at least something ))...
On monday I ll root that bi*ch again, pull there CM7 or some other ROM and post here actual status.
Thank you so far
Similar problem
Hi, I have the exact same problem with my Desire Z. I've attached the last_msg if someone could help me with that.. also, my sdcard is not partitioned so could that have anything to do with it? Thanks, hopefully I'll get an answer soon
Resurrecting a bit of an old thread here but I have just experienced these exact symptoms.
A friend gave me his old Desire-Z so of course I immediately set about rooting it and trying some ROMs.
As a start I went with the most recent Cyanogenmod which is 7.2 at this time. Everything was going smoothly and was just getting used to the phone and it's physical keyboard. My biggest worry was that the battery life wouldn't be good enough for me so I was running a test to see how long it would last. I am a very light phone user. With background wifi disabled, gps disabled and the phone set to 2G only it ran for 7days and 3 hours! No problems there even with a well used battery. When it eventually died I hit the power button to wake it and it started booting and then shutdown again as you would expect. However after I had fully charged it it booted no problems but then went into the boot loop described above. It boots successfully to the home screen but then after 10-15 seconds it reboots. Frustrating!
I tried some things:
Clear cache from CWM: No change
Factory reset from CWM: No change
Reflash CM7.2 from CWM: No change
Clear Dalvik Cache from CWM: No change
Clear Battery stats from CWM: No change. I was hopeful this might be the problem as the battery had been unusually flat, perhaps some flag had been set that caused the reboot.
I have now recovered by reflashing the exploitable original image, PC10IMG.zip, and then going back through the rooting process. I wouldn't want to have to do it again though.
Possible explainations for the behaviour: I was running a battery monitor app (GSam Battery Monitor) which runs continuously and has various power related functions. Though I would have thought anything that was doing would have been removed by factory reset or reflashing CM.
During the 7 days I was testing ROM manager prompted me to update it and then to update the version of CWM that I had. This is perhaps more likely as would have survived everything else I tried to recover until I reflashed the original recovery.
Hope that helps someone and if anyone has any insight on this I'd lobe to hear it.
Steve
Looks like I spoke too soon. First time I had to reboot the phone I got stuck in the reboot loop again.
Hmm, really confused now. No idea what can be causing this that isn't solved by reflashing CM7.2 but is by going back to the original rom?
Steve
the only thing, that helped me back then was to flash another ROM ... give it a try.
there is several other ROMs based on CM, I'm pretty sure, that you'll find one, that will suit you best.
Thanks for the reply I appreciate you taking the time.
It's very odd I can't think what might be causing this. I ran CM7.2 with zero issues for a week. Then first time I had to reboot it gets stuck in the loop.
Since I was away from home I could not get into recovery. I could get into HBoot (by holing Vol. Down + Power) but because I had a PC10IMG.zip file on my sdcard it would just go straight in to asking if I wanted to update from that with no way to select recovery. And of course I needed to have the sdcard in the phone to get an image from it!
So I have been running from the exploitable 2.2 Rom from the rooting procedure since. That can reboot no problems.
Today I tried a much more recent CM10.1 based rom - stuck in boot loop.
Then a tried the Rooted G2 stock ROM which is obviously much older. It booted correctly one time. Then I rebooted it (actually shutdown and then turned on, it doesn't have a reboot option) and now I'm stuck in the reboot loop.
I'm doing a factory reset and clearing the Dalvik cache after flashing each ROM.
I have also tried booting without the sdcard or SIM card, no change.
Something I have observed is that the phone will reboot once after flashing with every ROM, even the original ROM, but then either runs correctly or continuously reboots.
I can only think that possibly I have wrong phone model. I know that the previous owner bought this contract free so it may be some import. Perhaps it's actually a G2 and I'm using the wrong HBoot? I think that's unlikely as it would show an error during the rooting process.
Steve
I doubt you have the wrong hboot, it wouldn't even start if you did. I would do a complete wipe and format maybe change firmware as well. Backup SD and reformat that as well. If you have true radio soff (rooted via gfree) then you are safe to use one of the pc10img.zips I created here
http://forum.xda-developers.com/showthread.php?p=27796375 (see post 30)
Make sure to remove it from SD this time or at least change the name when done
This will give you new engineering hboot, updated 4ext recovery, .19 radio but all can be changed to whatever if you want.
After the flash reformat all in recovery and flash a new rom
Sent from my Nexus 7 using xda premium
Thanks for your input.
Updating the radio rom does seem tempting if potentially dangerous! The claimed power saving especially. I haven't ever used 4ext recovery but given how CWM seems to be failing me I might give it a try.
I don't wan to speak too soon here (but doing so anyway!) it looks like I may have corrected the problems by using SuperWipeG2+ from here: http://forum.xda-developers.com/showthread.php?t=1044992
After running that, which can easily be done from CWM, the phone booted first time with no reboots.
I'll update this if that did not fix it.
Steve
Yep spoke too soon!
However I have found a way to reliably recover but it's not straight forward.
Boot to recovery. Run SuperWipeG2+.
Attempt to boot the phone, boot fails as there is no ROM installed. This step seems important.
Boot to recovery. Install ROM from zip and Gapps from zip.
Reboot and phone will boot successfully and stay booted!
I then have to recover all my contacts and apps from Google which takes a further 20/25 mins.
Having done that I still cannot reboot the phone. If I reboot (or shutdown and power on) it is then stuck ion the boot loop and I have to do that all over again!
This means I cannot ever allow the phone to go flat.
Aaarrgh!
Any suggestions? It has been suggested that installing another ROM could fix this. Any specific ROM? Any idea why that would work?
I have found that the light sensor doesn't seem to be working and the suggested fix for that is to install a Sense based ROM and then switch back. I can't see how that could work either.
Steve
Yeah I've heard the sense ROM thing works, I don't see how but people seem to swear by it. I would suggest you change all your firmware, new hboot, new radio, new recovery and what not a new ROM. There are lots of good ROMs to choose from so I wouldn't know what to recommend for you, personally I almost always use gingerbread based ones
Sent from my Nexus 7 using xda premium
After flashing the latest CM9 nightly, I turned on my phone and found that it is running incredibly slow. Like, it takes over 15 seconds to launch any app. I have reflashed different nightlys and HO!NO!'s rom but the problem persists. I have also checked to make sure that I don't have any CPU settings that are keeping the processor slow. I even restored a nandroid backup, it didn't help.
I have now done the following:
-Wiped Data/factory reset
-Wiped Cache
-Wiped Dalvik Cache
-Install from zip
It is still slow.
Is there something I am overlooking? Any idea what is going on?
EDIT:
This is a logcat(whittled down to ~400 lines) of the issue happening in kernalpanics rom. I had the dialer open, put phone to sleep, woke up phone, and immediately started dialing a number. The phone hangs for about 5-15 seconds, and "catches up" later. The log starts right after I woke the phone, so it should pop up at the beginning.
http://dl.dropbox.com/u/16882142/logcat-copy.txt
Here are two videos of the problem(sorry for the wmv):
CM9
GB Rom
Recap:
-I have formatted SD card and tried without SD
-I have tried with and without the SIM card
-I have flashed many different nandroid backups
-I have formatted everything and installed new Roms (I couldn't get HO!NO!s Rom working though)
-I am trying to follow the "unbrick methods" to flash stock firmware. I cannot get the flash to start though(Post)
-I am running out of ideas!
Sounds to me like you got a lemon. Look into this http://forum.xda-developers.com/showpost.php?p=24179363&postcount=4
Out of curiosity is it a phone from bell?
No, its from AT&T. It is actually a refurbished replacement to a new phone I got in December. I want to return it to factory settings but ADB will not recognize the LGP930. This is incredibly frustrating, when I try to install the drivers through LG software I manually put in my IMEI and it says "File not found"
Thank you for the reply, I really need to try to restore this thing.
EDIT: To reiterate, something is seriously messed up with this phone. It takes ~30 second to launch any app. IT will say the program is not responsding and I have to "wait" instead of close to get it to load.
Try formatting system partition then install CM9 again.
Thank you for taking the time Drumist. I have actually already reformatted /system then reinstalled a nightly. I just did it again and still, it is messed up. My main issue right now is that I can't even connect this damn phone to ADB, I can't try to replace this with CM9, rooted, and CWM.
Can anyone help with the driver issue. HO!NO! won't even install anymore, it just sticks on the LG logo. So I am stuck with CM9, but the drivers don't work. Everytime I hook it up to either of my computers, it will detect it as LGP930 for a split second, then try to find drivers, then it recognizes the device as 4 different devices! LGE Modem, LG USB Composite device, LG GPS, and unidentified device. Please, does anyone know how to get into ADB, I am desperate here.
I essentially have an unusable phone. Just to make a call I have to click on phone, then it hangs for about 30 seconds until it says the app is not responding and asks if I want to force close it. I have to select wait, then eventually the app will load. All list-views work fine so I can scroll the contact list. But when i select a contact I have to wait another 30 seconds.
I have searched and read this forum for hours on what to do about the drivers, but no luck.
Is it possible that this is the fesult of a corrupted file system?
My very limited troubleshooting skills with Android says you've either got a/some app(s) running that's soaking up all the CPU/System resources, or there's some major I/O issues going on with your phone (whether because of messing with the ROM or with Hardware is unknown).
Unfortunately you've also stated that you can't get ADB to work, which throws a big wrench in the works to get some debug logs.
If you haven't already tried, there's a very helpful thread on getting ADB working on the Nitro (via stock Google USB driver, not LG). I highly recommend doing those steps and get ADB working for further troubleshooting: http://forum.xda-developers.com/showthread.php?t=1601159
Another thing to try, for giggles, pull the SDCard out and see if there's any performance gain...Maybe you've got a hosed SDCard, or bent/bad pins in the SDCard slot (worth a shot anyway).
Good luck!
Namuna! Thanks for your reply.
I figured out it is somehow related to the SD card, THANK YOU! I actually tried removing the SD card yesterday when the problem first started, but the trick is I have to boot my phone up with no card in it. Once I put a card in, even if I take it out, the problem starts up again.
Since my phone ran out of battery hours ago, I am at work, and I left my cable at home; I cannot try the google drivers. I won't be geting home until late so I'm going to have to do some more experimenting tomorrow.
You don't need the Google drivers now. LG drivers are working again.
I remember that that is the case Malnilion, but I need to try something.
Bad news, apparently I jumped the gun because my phone is super slow again, with or without an SD card.
I just really need ADB access, a log would be a godsend.
I have found I can get to ADB when in CWM, but I can't get the drivers to work when in CM9 so I can't get a logcat.
Try to adb in recovery. Did you format that SD card?
Sent from my LG-P930 using XDA
I now have a version of kernalpan1cs rom running on my nitro. Almost everything runs fine, but the slowness happens when I try to make any phone call and with other random apps.
I have ADB now, and I am going to post a logcat of what happens when I try to dial a number using the phone app, then when I try to make a phone call.
I just need some help, I can look at the logcat when I do ADB logcat, but I have a hard time keeping track of when the problems happen. There are so many things that happen immediately after it that I cannot keep track of where the previous information was in the console window.
BTW, I notice that when the slowness happens when I dial a number in the phone app that the log reports a bunch of stuff about going into wakelocks and coming out of wakelocks. I thought this was kind of weird.
2 things.
1. I salute you for sticking with this phone through all the issues you've had (and still continue to have). I would've got the thing back as close to stock as possible and then exchanged it for another Nitro a long time ago. You've already done it once, it seems the refurb you got is also suffering some hardware issues...Might be time to do it again!
2. If you are dead set on chasing this rabbit down its' rabbit hole though, then I suggest getting acquainted with another debug tool called ddms (http://developer.android.com/guide/developing/debugging/ddms.html). It's a GUI based debugger that utilizes logcat, but is much more robust with tools for filtering and viewing associated processes.
Good luck!
Have you tried replacing the sim? Sounds like a shot sim to me.
beaups said:
Have you tried replacing the sim? Sounds like a shot sim to me.
Click to expand...
Click to collapse
This is a good point, especially if it's the same SIM that you used on your previous Nitro...Thereby bringing the issues with it!
Thanks guys! First off, I have exams going on so this has definitely taken the backburner, otherwise I would be on top of this.
@beaups: I'm pretty sure it isn't the SIM, when the SIM is out the slowness continues in either ROM.
@Namuna: I think I will give ddms a try once I have some time(hopefully this weekend). Thanks for the tip, I usually like getting my hands dirty
This is a logcat(whittled down to ~400 lines) of the issue happening in kernalpanics rom. I had the dialer open, put phone to sleep, woke up phone, and immediately started dialing a number. The phone hangs for about 5-15 seconds, and "catches up" later. The log starts right after I woke the phone, so it should pop up at the beginning.
http://dl.dropbox.com/u/16882142/logcat-copy.txt
Lastly, if I try to exchange this phone for another, what should I do in order to make it more factory-like? Install a stock ROM? Uninstall CWM?
EDIT:
Here are two videos of the problem(sorry for the wmv):
CM9
GB Rom
I also got the same thing here after updating the cm9 followed by a wipe data.. Tried all the things listed.. format system, gb roms.. Have you had any luck with the unbricking method?
I have same situation about the super slow after cm9. However, i fixed the problem after using the unbricking method. everything back to normal now. You can take a try. It seems like cm9 mess up some I/O address, cause it only slow down whenever you need to input or output from system.(Example: phone call, music ..etc)
did it
had the same problem, [Guide] Unbricking Solution for LG Nitro HD (P930) did it for me, back to usual speed
Yes, the unbricking solution worked for me, I just had to use the method in the original post once I worked out some driver issues.
I still am wondering what caused this though.
I've had my Inc2 since 2011 and have flashed different ROMs more than I can count.
In the last 2 weeks, I keep getting SD Card was removed messages.
I reboot and its back. I figured the SD Card was dying on me...
Since then, I've switched to a NEW SD Card and am having the same troubles, but more frequently, like everyday.
In fact it took and hour to get it to work again yesterday.
Anybody know whats going on?
I'm running the same ROM I've had for months, I've used a couple different ones over the weekend to see if that was the issue... It's not.
I've cleaned all the contacts and blown our the SD Slot.
Is she dead Jim? or am I missing something?
Have u tried using a different rom?
If u installed the original SD card incorrectly on the same rom maybe it's remembering that?
Sent from my Incredible 2 using xda app-developers app
Assumed that you've already saved contents on your mSD card, wipe it clean on a PC/Mac/Linux OS (Fat or Fat32) then put it back on the DI2,
boot into recovery - wipe dalvik & cache, REFORMAT the mSD card - then boot up normally.
What Rom are you running? If above steps still do not work, try a Master Reset from the Rom before doing a Clean & Fresh Install of the Rom.
Keep a watch on error messages on the screen as you do all these & post your results, good luck !
Letitride said:
Assumed that you've already saved contents on your mSD card, wipe it clean on a PC/Mac/Linux OS (Fat or Fat32) then put it back on the DI2,
boot into recovery - wipe dalvik & cache, REFORMAT the mSD card - then boot up normally.
What Rom are you running? If above steps still do not work, try a Master Reset from the Rom before doing a Clean & Fresh Install of the Rom.
Keep a watch on error messages on the screen as you do all these & post your results, good luck !
Click to expand...
Click to collapse
Been Runnin Miui for the last year. No changes on phone.
SD card acts like it was pulled. Have to poweroff and remove battery to have it back.
A reboot into recovery still doesn't give me access to the card.
I've also tried different SD cards with the same results.
Anyone reading this with this problem, try returning to stock recovery and rom with the pg83.IMG(I think that's the name) and try doing a factory reset in stock recovery. My SD card works after that
persom55 said:
Anyone reading this with this problem, try returning to stock recovery and rom with the pg83.IMG(I think that's the name) and try doing a factory reset in stock recovery. My SD card works after that
Click to expand...
Click to collapse
This problem has gotten worse. And most of the time the SD card isn't even available in recovery either.
plupien79 said:
This problem has gotten worse. And most of the time the SD card isn't even available in recovery either.
Click to expand...
Click to collapse
Yeah that's about what my problem was. Usually if you go for about a day without an SD card in, it will most likely recognize it again. If not, I could usually tap the back of the phone on a table, down near the bottom where the SD port is.
If that still doesn't work, you'll have to fastboot flash the return to stock image
My theory on this problem is that after flashing Roms/s-off and messing with stuff eventually corrupts some part of the filesystem. You might also try following the guide to unroot and s-on to see if that works, though that will be a little harder.
Flashing the ICS firmware didn't help.
Guess I'll have to try going the long way around...
Flashing the ICS firmware didn't help.
Guess I'll have to try going the long way around...
Well Then...
Got the PG32IMG factory restore... that was a wash. Got everything but s-on done... and upon getting through the setup... SD Card removed unexpectedly.
So had to use ADP and FASTBOOT to get a recovery installed and back to square one.
plupien79 said:
Got the PG32IMG factory restore... that was a wash. Got everything but s-on done... and upon getting through the setup... SD Card removed unexpectedly.
So had to use ADP and FASTBOOT to get a recovery installed and back to square one.
Click to expand...
Click to collapse
Did you try doing a factory reset with stock recovery though?
I've read about some people with roaming problems on their HTC one, and flashing the stock recovery back and doing a factory reset fixed it.
Sooo give that a try if you haven't already
Edit: that probably sound un related but maybe after messing around with HTC devices they get mad and sabotage themselves haha. But seriously though. I messed around with the return to stock image a couple months ago, and I could get it work for a very short time, like you experienced. But just the other day I entered stock recovery mode from bootloader and it started doing a factory reset on it own. After it started up it recognized an SD card when I put it in and i then fastboot flashed a custom recovery(not cwm or twrp can't thnk of the name) then I flashed the andromadus mimicry ICS ROM that was still on the SD card and right now I've been playing music off it for about an hour and it seems to be fine
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!