Related
Just to report that for me i couldn't get network(no service) signal for 1 or 2 minutes even after crashing the system server
http://forum.xda-developers.com/showthread.php?t=1037855
I can't post in there yet, if someone can do that for me, i appreciate that.
I don't if it is connected but the signal showed up when i went to the system update on settings.
Settings> System > About Phone > System updates> Then it crashes in here and FC
Once it gets back to the home everything gets alright.
The rom seems a bit laggy yet, but maybe is something configuration or procedure i did wrongly.
Also from time to time, the screen gets lighted (bright) and after that dark again when i am not using it, not even near.
Just flashed it 20min ago.
you should attempted to reflash the ROM. Make sure you are on basebrand.49 or .52. Wipe data, cache, dalvik cache, and battery stats, then flash the custom zip ROM. Crash system server like you said and you should have a clean ROM
If you want a GB ROM you may try this one http://forum.xda-developers.com/showthread.php?t=911364
You're gonna get more suport from J with this ROM =)
what I did and it worked for me was flash TripNMIUI_BTS_02.zip first, then I rooted it again and installed xRecovery. I then flashed bb.52, booted into xRecovery, cleaned the cache, dalvik, battery, etc. and then flashed this ROM. Do a system crash and once it reboots it should pick up a signal within 10 sec.
aval1392 said:
you should attempted to reflash the ROM. Make sure you are on basebrand.49 or .52. Wipe data, cache, dalvik cache, and battery stats, then flash the custom zip ROM. Crash system server like you said and you should have a clean ROM
Click to expand...
Click to collapse
As i said before, after the last FC in the settings, it did work normally i have the rom working perfectly fine, what i wanted was to someone that can post there to do this for me, or that trip could see this to add to the install steps so people can try also what worked for me may work for others.
ironjose said:
If you want a GB ROM you may try this one http://forum.xda-developers.com/showthread.php?t=911364
You're gonna get more suport from J with this ROM =)
Click to expand...
Click to collapse
I normally try every rom for one or two weeks at least so i can be sure which one is better, so far i've tried one based in this rom, but is wasn't faster than TripNMIUI version.
In TripNMIUI i got 36,5 in Linpack without using any APP2SD tool, also got in Quadrant from 1100 to 1200.
The other roms i tried hardly passed up than 32k in linpack and normally near 900 in quadrant.
i have a serious random reboot problem when my phone is in idle. here is what i did...
while on Alien v.3 i .sbf flashed the 1.97.00 radio and then flashed Kholk's kernel
then...
in romracer's CWM:
wiped dalvick cache
wiped cache
wiped data/factory reset
flashed Alien v.4
reboot
skipped blur setup
waited 10 minutes
went through set up (reset apn to default, added gmail account)
reboot into CWM
wiped dalvick cache
wiped cache
flashed Alien theme 4
reboot
restored apps
reboot into CWM
wiped dalvick cache
wiped cache
flashed Kholk's kernel
reboot
i started getting random reboots. i cant figure out what the problem is. i tried flashing a different theme, and still got reboots. tried flashing the stock kernel and still got reboots. i tried re-flashing Alien v.4 and not restoring any apps and still got reboots. argh... any ideas?
can the radio cause a reboot issue? i really dont think its a ROM/Theme thing since noone else seems to be reporting the same problem... am i noobing this whole mod process?
this happens to me too. Turn your wifi off when you aren't using it. Mine only reboots when its in standby with wifi on
fischwrap said:
i have a serious random reboot problem when my phone is in idle. here is what i did...
while on Alien v.3 i .sbf flashed the 1.97.00 radio and then flashed Kholk's kernel
then...
in romracer's CWM:
wiped dalvick cache
wiped cache
wiped data/factory reset
flashed Alien v.4
reboot
skipped blur setup
waited 10 minutes
went through set up (reset apn to default, added gmail account)
reboot into CWM
wiped dalvick cache
wiped cache
flashed Alien theme 4
reboot
restored apps
reboot into CWM
wiped dalvick cache
wiped cache
flashed Kholk's kernel
reboot
i started getting random reboots. i cant figure out what the problem is. i tried flashing a different theme, and still got reboots. tried flashing the stock kernel and still got reboots. i tried re-flashing Alien v.4 and not restoring any apps and still got reboots. argh... any ideas?
can the radio cause a reboot issue? i really dont think its a ROM/Theme thing since noone else seems to be reporting the same problem... am i noobing this whole mod process?
Click to expand...
Click to collapse
try version 4 of alien. It has less bugs, faster and better performance.
Voelker45 said:
try version 4 of alien. It has less bugs, faster and better performance.
Click to expand...
Click to collapse
i was using Alien v.4, but it turns out it wasnt an issue with alien...
i think i figured it out (for those of you who care!)
I hadnt correctly removed the old install-recovery.sh file, so i think that may have resulted in incorrect flashes/installs... so i removed it, then flashed romracer's CWM
also, i sbf flashed this 4.5.91 Radio: http://forum.xda-developers.com/showthread.php?t=1159505&highlight=radio
between those two things, i seem to finally be on a fully functional, seemingly bug-less Atrix running Alien v.4 + Theme on Kholk's kernel and the 4.5.91 radio!
thanks for sharing.
Since installing Alien 4 on the weekend, I've had two spontaneous reboots. Both times were while playing music with the screen off and wifi on. Could be the music app, but I didn't have any reboots in Alien 3 or the other GB roms I tried.
Sent from my MB860 using XDA App
whenever I flash a new ROM (whatever it is) I get a string of random reboots.
Then after a few days it settles down...... seems to be worse if
a.) playing music
b.) bad data reception <---- this has happened to me on stock when I have 5 bars but there is some kind of data issue with the carrier and I open too many data using apps that all time out and causes some kind of kernel panic BAM reboot
I think my phone maybe has an issue when it first runs apps after a fresh build if its deodexed (compiling the cache etc. or the JIT first run whatever I'm not a dev) as that would explain why it settles down after a day or two.
Well I may have spoken too soon... my phone has rebooted twice, with about 90 minutes between each one, since I took it off the charger.
Sent from my MB860 using XDA App
I have heard that if you restore apps with tibu it causes problems. Try a fresh start with apps and no restore
Sent from my MB860 using XDA Premium App
hate to necro an old thread, but since the kernel has been updated and this issue persists i figured it was relevant...
As others in this thread have discovered, it is an issue with WiFi while the phone is asleep. Particularly reboots the phone when moving in and out of known WiFi reception areas. While I'm now using WiFi much more conservatively and saving battery life, its still a troublesome issue. Has anyone else made any attempts to fix it? I will be trying a few things myself soon.
So I flash the Ics update (LPQ) last friday and all went well, my phone was working perfectly. However on sunday my phone kept freezing and the only was to get it working again was to pull the battery. So because of this i decided to go back to GB and wiped everything and flask a stock firmware (KI8) which is my carrier firmware. Now my phone keeps turns off every 10 minutes or so any it is really annoying. It only seems to happen when the phone is not plugged in to charge and I have tested it out and it doesn't tend to happen in flight mode either. At the moment I have wiped the phone completely and haven't even installed an app yet it is still happening. Has anyone got a clue what this could be as its driving me mad.
Thanks in advance
I have the same problem, i updated to ICS and now my phone reboots every 2 / 30mins.
I tryed lots of roms and now downgraded to a 2.3.3 stock rom, with re-partition, no SDcard .. but still ... it reboots itself a lot .
The strange thing is that it reboots when left alone, the sgs2 can stay up for 3h+ when it plays music on GoogleMusic ...
Oh, and i also tryed with a new samsung 2000mah battery kit, still no changes, so it's not a battery problem
I had this problem with GB 2.3.5 stock firmware. After flashing custom ICS - Lite'ning Rom - http://forum.xda-developers.com/showthread.php?t=1095274 , the problem disappeared. Of course I did full wipe of device before flashing.
Thanks, Ill try flash lightning later when i get home. As i think that it is something to do with the radio I have also tried flashing a new modem (KE7) but that did not solve the issue either. It there any app that can monitor processes so that i can look at what is happening just before it turns off.
I had this when I was using MIUI. I flashed Spikes Pure ICS yesterday and haven't noticed it since.
Strange, I had this issue on GB, and not on ICS. Try flashing some different roms, full wipes of course, and see if that helps
bmbm said:
I had this problem with GB 2.3.5 stock firmware. After flashing custom ICS - Lite'ning Rom - http://forum.xda-developers.com/showthread.php?t=1095274 , the problem disappeared. Of course I did full wipe of device before flashing.
Click to expand...
Click to collapse
didn't work for me :'(
First factory reset and then flash the ics.
rocky23 said:
First factory reset and then flash the ics.
Click to expand...
Click to collapse
i did a factory reset by using the *2767*3855# command , then i went to the recovery to format data/system/cache/sdcard/emmc .
Still, no luck and getting reboots
Last night I flashed both lite'ning ron and Check rom. Did a full wipe before both and I am still getting reboots and freezes. Think Ill have to get a jig and bring it back to the shop
So just to update. The latest think i have tried is changing the modem to KE3 and I tried the speedmod kernel and the syriah kernel. Still having the freezing issue. Have also tried a kernel cleaner but to no avail. Anything else I should try before bringing it back. Thanks
Why dont you try to install a stock rom, then root it, and within CWM recovery wipe everything, then reinstall your stock rom thru odin
Have tried flashing the stock firmware 2.3.5 KI7 and wiped the cache,the dalvick cache and factory reset the phone before but that didnt work. Is there specific firmwares that will wipe everything?
Corrupt SD can sometimes also cause random reboots. Do you have an external SD on top of the included internal SD? Try formatting them both. Start fresh.
ctomgee said:
Corrupt SD can sometimes also cause random reboots. Do you have an external SD on top of the included internal SD? Try formatting them both. Start fresh.
Click to expand...
Click to collapse
i agree with you i tried this method last year and it worked,, you should try this and if doesnt work format your phone system wipe data, wipe cache , wipe dalvik for a very fresh start..
Yes I thought it could have been the sd card to so I removed it from from the phone and formatted the internal memory, then wiped the dalvik cache, the cache and the phone and flashed a new rom but my phone started to freeze after about 20 minutes. Its weird originally my phone was Freeze and wouldnt wake from sleep, then it would just randomly reboot and now its back to freezing and not waking from sleep
I would try KH3 rom. For me that was the most stable GB rom
Sent from my GT-I9100 using xda premium
I was listening to music on my Evo 3D over bluetooth today, when I put it in my pocket and paused the music. After going back to my phone, I noticed it had reboot itself, and now it's stuck on a boot loop. Does this sound familiar to anyone? I can't think of any reason why it would boot loop like this. Wiping cache+dalvik doesn't fix the boot loop. After clearing cache+dalvik and booting the phone, it does go to the screen saying that Android is updating apps, but as soon as it finishes it goes right back to the boot loop. I'd appreciate any assistance in figuring this out. Thanks!
it happened to me the other day. i was using CM10.1 Wild for the night along with Saring Gas Kernel. i managed to fix this by wiping everything manually instead of using a superwipe, and then flashing again. and then i had this issue with MidNight Rom CM10.1 where whenever i turned bluetooth on, after turning it off the phone would freeze, reboot and then bootloop. however the Dev had specified that bluetooth was broken.
if the boot loop is at the Rom's boot animation, and you cant fix this by deleting Cache, Dalvik and Data, then you will certainly have to wipe it all and flash again. hopefully you had all you data backed up.
Kite-G said:
it happened to me the other day. i was using CM10.1 Wild for the night along with Saring Gas Kernel. i managed to fix this by wiping everything manually instead of using a superwipe, and then flashing again. and then i had this issue with MidNight Rom CM10.1 where whenever i turned bluetooth on, after turning it off the phone would freeze, reboot and then bootloop. however the Dev had specified that bluetooth was broken.
if the boot loop is at the Rom's boot animation, and you cant fix this by deleting Cache, Dalvik and Data, then you will certainly have to wipe it all and flash again. hopefully you had all you data backed up.
Click to expand...
Click to collapse
Yeah, I ultimately had to restore from a backup. This is an almost stock ICS rom, deodex plus a few other apps baked into the ROM, and the stock kernel.
Now this doesn't happen every single time I turn the screen off with bluetooth turned on, or every time I turn off bluetooth. This is just a random boot loop that hits out of nowhere. Since I can't figure out what causes it, I was hoping someone who had encountered it would know.
while i cant point out the exact cause, these random bootloops happen due to file system errors, or namely the kernel. but you say you had stock kernel, so if it was not overclocked or tempered with then that cant be it.
in my case, for example, last night i overclocked my phone to 1.8GHz and set the governor to performance, I/O to vr. turned the phone off and forgot to lower the settings or to increase voltage, and then when i turned it on the phone was in a bootloop. went to recovery and it said that cache was unreadable, suggesting a full wipe. what happened here was that the kernel settings i had used were saved in cache, so when i tried to boot with such high settings without the proper power for the cpu, the phone just couldnt boot. i wiped cache and the kernel settings got restored to default. so it booted.
another example was that i flashed an update.zip that was corrupted. the phone booted and behaved normally. then when i loaded any of the apps from the update.zip the phone would freeze, reboot and boot loop.
and then theres this one, my EVO could run every ICS rom perfectly, but every single 4.1+ rom i used had bugs, lag, visual glitches, and whatnot. i tried wiping multiple times, redownloading the roms, etc. in the end nothing helped. then i tried a superwipe which checks the filesystem for errors and optimizes it. after using that superwipe, every 4.1+ rom ran smoothly, and the ICS roms i had used benchmarked better than before
so if you say you got that boot loop randomly, and using stock kernel, i can safely assume that either the rom did not flashed properly, or that your EVO has some file system errors. you could try either a new fresh install or using a superwipe and flash your Nand, but if it was me, i would use superwipe, then manually wipe everything, and fresh install the rom. if the nand backup you installed after the bootloop was from the same install as the one who gave you the bootloop, then its a safe bet that it could happen again. i would backup all my apps and data, and do as i said earlier.
hopefully this info helped you a little.
in case you would want to give it a shot, here is the superwipe i used.
like i said, just flash the file on recovery, you dont need to wipe beforehand. and after its flashed, i recommend you wipe but its not necessary. then just flash your rom, and other files if any, and boot. hope it helps.
(i was gonna link to the thread where i got the super wipe, but i forgot where i found it. anyways, credit goes to author)
Kite-G said:
while i cant point out the exact cause, these random bootloops happen due to file system errors, or namely the kernel. but you say you had stock kernel, so if it was not overclocked or tempered with then that cant be it.
in my case, for example, last night i overclocked my phone to 1.8GHz and set the governor to performance, I/O to vr. turned the phone off and forgot to lower the settings or to increase voltage, and then when i turned it on the phone was in a bootloop. went to recovery and it said that cache was unreadable, suggesting a full wipe. what happened here was that the kernel settings i had used were saved in cache, so when i tried to boot with such high settings without the proper power for the cpu, the phone just couldnt boot. i wiped cache and the kernel settings got restored to default. so it booted.
another example was that i flashed an update.zip that was corrupted. the phone booted and behaved normally. then when i loaded any of the apps from the update.zip the phone would freeze, reboot and boot loop.
and then theres this one, my EVO could run every ICS rom perfectly, but every single 4.1+ rom i used had bugs, lag, visual glitches, and whatnot. i tried wiping multiple times, redownloading the roms, etc. in the end nothing helped. then i tried a superwipe which checks the filesystem for errors and optimizes it. after using that superwipe, every 4.1+ rom ran smoothly, and the ICS roms i had used benchmarked better than before
so if you say you got that boot loop randomly, and using stock kernel, i can safely assume that either the rom did not flashed properly, or that your EVO has some file system errors. you could try either a new fresh install or using a superwipe and flash your Nand, but if it was me, i would use superwipe, then manually wipe everything, and fresh install the rom. if the nand backup you installed after the bootloop was from the same install as the one who gave you the bootloop, then its a safe bet that it could happen again. i would backup all my apps and data, and do as i said earlier.
hopefully this info helped you a little.
in case you would want to give it a shot, here is the superwipe i used.
like i said, just flash the file on recovery, you dont need to wipe beforehand. and after its flashed, i recommend you wipe but its not necessary. then just flash your rom, and other files if any, and boot. hope it helps.
(i was gonna link to the thread where i got the super wipe, but i forgot where i found it. anyways, credit goes to author)
Click to expand...
Click to collapse
Just FYI, the Wild For The Night OP specifically says do NOT use superwipes. Superwipe scripts and AOSP Roms don't always play together nicely. That's and CM Rom. Factory reset wipe in recovery is fine.
I am aware of that. But thanks for pointing it out. Althought I haven't had any problems with AOSP roms & superwipes when I wipe manually after the superwipe, only when I don't. But then again results may vary. At least in my case, I'm pretty satisfied with the results.
Sent from my HTC EVO V 4G using xda app-developers app
hey guys, im having an issue with GS3 i9300.
after the phone boots it freezes and becomes unusable, it'll sit there with the screen on in the frozen state for hours until i do a battery pull or holding down the power button.
the real weird part is that ive tried 7 different roms all wiping and cache, delvick cache. they all boot up fine but immediately after boot the phone freezes. and this happens with all the roms ive tried :
any help please? cuz the phone is unusable at the moment :/
Format
System
Data
Cache
Wipe dalvik
Then flash rom
Wipe cache again
Wipe dalvik again
Reboot.
--------------
alliances+siyah
iamdutchy said:
hey guys, im having an issue with GS3 i9300.
after the phone boots it freezes and becomes unusable, it'll sit there with the screen on in the frozen state for hours until i do a battery pull or holding down the power button.
the real weird part is that ive tried 7 different roms all wiping and cache, delvick cache. they all boot up fine but immediately after boot the phone freezes. and this happens with all the roms ive tried :
any help please? cuz the phone is unusable at the moment :/
Click to expand...
Click to collapse
(1) Do you use any custom kernel? I assume not as it happens with all roms and usually a custom kernel is overwritten by the one included in the rom.
(2) Try to flash a stock rom with complete fresh setup by using e.g. Mega or Super Wipe (Mega Wipe will give you the most clean start).
(3) If it is still not better, have a look here, maybe this will help.
(4) If nothing helps, Samsung service centre I guess.
chrismast said:
(1) Do you use any custom kernel? I assume not as it happens with all roms and usually a custom kernel is overwritten by the one included in the rom.
(2) Try to flash a stock rom with complete fresh setup by using e.g. Mega or Super Wipe (Mega Wipe will give you the most clean start).
(3) If it is still not better, have a look here, maybe this will help.
(4) If nothing helps, Samsung service centre I guess.
Click to expand...
Click to collapse
hey, thanks allot for your reply. i followed your instructions, did the mega and tried again, but the problem still persisted with the roms i tried (CM 10.2, aokp, paranoid android) but i tried liquid smooth and it seems to be working fine now, it froze once and i did a battery pull and its been smooth sailing since.
is it possible that it may have been the SDS issue?? from what i understand tho any rom above 4.1 would have fixed this issue.
iamdutchy said:
hey, thanks allot for your reply. i followed your instructions, did the mega and tried again, but the problem still persisted with the roms i tried (CM 10.2, aokp, paranoid android) but i tried liquid smooth and it seems to be working fine now, it froze once and i did a battery pull and its been smooth sailing since.
is it possible that it may have been the SDS issue?? from what i understand tho any rom above 4.1 would have fixed this issue.
Click to expand...
Click to collapse
SDS is, if I am not totally wrong, kernel related (btw @rootSU got a very informative thread about it). Hence the Android version does not matter that much whereas if a rom is using an "unsafe" kernel obviously it is not SDS safe. As described in that mentioned thread, if you upgrade recovery (newest CWM versions, e.g. philz) and kernel there should me not issue with SDS.