i m using darkside Rom ,and my phone reboots almost in every hour, i am new to android please solve my problem ,its very annoying,thanx!
Ahmed Zahoor said:
i m using darkside Rom ,and my phone reboots almost in every hour, i am new to android please solve my problem ,its very annoying,thanx!
Click to expand...
Click to collapse
gingerbread 2.3.5
have you tried to flash the rom again to c if thats the problem
Hi there,
1. Did u do a full wipe before installing the new rom?
2. You could try installing faux123 1Ghz kernel LINK use "Enhanced Stock Kernel, Max @ 1.0 GHz". Install the one for GINGERBREAD
Link to Faux123 1.0 GHz kernel
[ Installation procedure: ]
[ CWM Method ]
1. reboot to CWM
2. Clear cache
3. install zip from SDcard
4. Reboot
Hope this helps
P.S.: "Wet Dream" is the new version of "The Darkside" might be worth to take a look
Grtz
Faux kernel will prevent boots but will erase every widget at every reboot...
I has the best results with the stock intl kernel (see GingerMod Rom). I don't have reboots anymore...
Sounds like the rom didn't install properly, I'd go through the wipe and factory reset/dalvik once again and reinstall. Just make sure to do a backup just in case it backfires.
DannyBiker said:
Faux kernel will prevent boots but will erase every widget at every reboot...
Click to expand...
Click to collapse
That's just not true. I've used both .23 and .24beta kernels and the widget thing rarely happens. It does happen, but not on every reboot.
troycarpenter said:
That's just not true. I've used both .23 and .24beta kernels and the widget thing rarely happens. It does happen, but not on every reboot.
Click to expand...
Click to collapse
Hey, do you know where I can find faux123's 0.24 beta kernel? I looked but couldn't find it. Thanks.
mabe try differnt Kernal too
Sent from my MB860 using Tapatalk
Ahmed Zahoor said:
i m using darkside Rom ,and my phone reboots almost in every hour, i am new to android please solve my problem ,its very annoying,thanx!
Click to expand...
Click to collapse
As has been already mentioned, make sure you do a full and proper wipe of your phone before flashing roms, but another problem could be that you're being too extreme with undervolting. Try reducing your undervolts if you have been undervolting. Or, if you have an extreme overclock kernel, consider lowering clock speeds because each phone is different, and some (even ones of the same type) can't handle as high of clock speeds as others. But, I suspect that your main problem is that you didn't follow the proper steps before flashing.
1. Boot into recovery (hold the volume down button while booting, then press down until you see android recovery, and then press up)
2. Do a factory reset
3. Clear cache partition
4. Clear dalvik cache
5. flash the zip
Note: factory reset will erase all your data, so backup any files you want to keep before doing so.
To flash a new kernel, do what denbeutels said, except you should clear dalvik as well. Android needs to recompile certain things to optimize them for the new kernel, so it's a very important step.
Atrix_Owner said:
Hey, do you know where I can find faux123's 0.24 beta kernel? I looked but couldn't find it. Thanks.
Click to expand...
Click to collapse
Are you following the faux123 kernel thread in development?
http://forum.xda-developers.com/showpost.php?p=22178618&postcount=2965
Ok, after running a few days on the new faux 0.2.4 1.45GHz kernel, I've experienced quite a few reboots as well (ok, an order of magnitude more than before). Right now I have gone back to faux 0.2.3 1.3GHz and haven't seen any problems yet. I was mainly getting reboots during undocking (all dock types), but also sometimes during normal use. And I'm talking about 3-5 reboots throughout the day.
Edit: And of course, as soon as I posted this, I got another reboot (this time while using webtop in the lapdock and simply closing a Synaptic window). Next I'll have to start tracking down anything I installed recently that may be doing this.
Related
This is the problem I had after I flashed my vibrant with the simply honey revolution 3.9.1 rom I couldn't receive any phone calls. I learned this happened randomly and managed to fix it for me it should work for others too. Don't know if this was posted already but I couldn't find a fix for it. =/
Well I got it to work this is the steps I did. Thanks kyle51 and Majin_X for the heads up.
1) Odin back to stock JFD
2) Root phone
3) Odin Simply Honey 3.8
4) Flash through recovery 3.9 Lite (make sure you have a GB boot-loader to see recovery)
5) Flash in recovery 3.9 Full (Probably don't need this step but this is what I did)
6) Boot to recovery and wipe data/factory reset. Stay in recovery don't reboot
7) While in recovery Wipe cache
8) While in recovery Wipe Delvik
9) While in recovery Fix permissions
10) Flash 3.9 Lite through recovery and finally reboot when done
11) Now if you like you can flash the medium or full package through recovery
This is what I did and it worked if anyone else has the same problem give this a try it should work and post your results if it worked. Good Luck!
its random, it only happens to a few people, i've never had it in 3.8 or 3.9
thought he fixed it in 3.9.1
try reflashing with a wipe and clear all caches and fix permissions
The same thing is happening to me.
Tried both lite and large versions.
Hmmm thanks for the input guys this is what im going to do Im going to go back to stock with a clean install and then im going to flash the simply honey rom then format delvik and all those other things see what happens ill report back once i come bacl from the beach
Armen1er said:
Hmmm thanks for the input guys this is what im going to do Im going to go back to stock with a clean install and then im going to flash the simply honey rom then format delvik and all those other things see what happens ill report back once i come bacl from the beach
Click to expand...
Click to collapse
I came from stock, flashed 3.8, flashed 3.9 light, then flashed large pack...... had the same problem.... on both my vibrants... so i wiped data/factory reset and reflashed 3.9 light..... problem solved... on both phones
Majin_X said:
I came from stock, flashed 3.8, flashed 3.9 light, then flashed large pack...... had the same problem.... on both my vibrants... so i wiped data/factory reset and reflashed 3.9 light..... problem solved... on both phones
Click to expand...
Click to collapse
Thanks for the input didnt have time to try it. I actually just rooted my phone right now so I am going to do that now. I will post results once I'm finished.
And one more question if anyone has any input OC your phone does it kill the phone or its just rare cases or myth? Just curious I seen people say no and others say yes not sure if I should try the 1.54 Ghz bullet kernal :/
It works finally lol
Well I got it to work this is the steps I did.
1) Odin back to stock JFD
2) Root phone
3) Odin Simply Honey 3.8
4) Flash through recovery 3.9 Lite (make sure you have a GB boot-loader to see recovery)
5) Flash in recovery 3.9 Full (Probably don't need this step but this is what I did)
6) Boot to recovery and wipe data/factory reset. Stay in recovery don't reboot
7) While in recovery Wipe cache
8) While in recovery Wipe Delvik
9) While in recovery Fix permissions
10) Flash 3.9 Lite through recovery and finally reboot when done
11) Now if you like you can flash the medium or full package through recovery
This is what I did and it worked if anyone else has the same problem give this a try it should work and post your results if it worked. Good Luck!
Armen1er said:
Thanks for the input didnt have time to try it. I actually just rooted my phone right now so I am going to do that now. I will post results once I'm finished.
And one more question if anyone has any input OC your phone does it kill the phone or its just rare cases or myth? Just curious I seen people say no and others say yes not sure if I should try the 1.54 Ghz bullet kernal :/
Click to expand...
Click to collapse
my mate thats got an iphone and knows abit more about phones and computer stuff than me says it can (probably just saying that cos his phone cant OC)
not every phone can OC that high so u'll have to try it, and its not running that high all the time so it probably wont kill it
it might bring the life of it down abit but probably not that much and might have some heating problems but thats probably about it
Armen1er said:
Thanks for the input didnt have time to try it. I actually just rooted my phone right now so I am going to do that now. I will post results once I'm finished.
And one more question if anyone has any input OC your phone does it kill the phone or its just rare cases or myth? Just curious I seen people say no and others say yes not sure if I should try the 1.54 Ghz bullet kernal :/
Click to expand...
Click to collapse
I ran the 1.54 with ALMOST no problems.... From time to time it would crash and reboot. Using setcpu you can change governors..... If your going to use it to the max then it will drain pretty quick if your USING it. Performance at a price. I use smartass because it eliminates the need for profiles. It lasts long if its at idle (black screen).
Sent from my GT-I9000 using XDA Premium App
Armen1er said:
Well I got it to work this is the steps I did.
1) Odin back to stock JFD
2) Root phone
3) Odin Simply Honey 3.8
4) Flash through recovery 3.9 Lite (make sure you have a GB boot-loader to see recovery)
5) Flash in recovery 3.9 Full (Probably don't need this step but this is what I did)
6) Boot to recovery and wipe data/factory reset. Stay in recovery don't reboot
7) While in recovery Wipe cache
8) While in recovery Wipe Delvik
9) While in recovery Fix permissions
10) Flash 3.9 Lite through recovery and finally reboot when done
11) Now if you like you can flash the medium or full package through recovery
This is what I did and it worked if anyone else has the same problem give this a try it should work and post your results if it worked. Good Luck!
Click to expand...
Click to collapse
I forgot to mention above the whole part about reflashing the large our med packs..... Thanks for this....although I did not wipe dalvik and do not have any problems.
Sent from my GT-I9000 using XDA Premium App
Thanks for the reply guys I have the bullet 1.54 Ghz kernal and basically just use it for the N64 emulator it runs games so much faster but eventually after a few mins of playing the phone would reboot so im going to stick to 1.2 for now even though that quadrant score of 3364 was nice lol
Armen1er said:
Thanks for the reply guys I have the bullet 1.54 Ghz kernal and basically just use it for the N64 emulator it runs games so much faster but eventually after a few mins of playing the phone would reboot so im going to stick to 1.2 for now even though that quadrant score of 3364 was nice lol
Click to expand...
Click to collapse
did you mix it with chainfire?????
Majin_X said:
did you mix it with chainfire?????
Click to expand...
Click to collapse
This is noobish but never heard of chain fire just came back into the xda scene from a loooong break lol haven't kept up with most things
Armen1er said:
This is noobish but never heard of chain fire just came back into the xda scene from a loooong break lol haven't kept up with most things
Click to expand...
Click to collapse
get it from market
Im downading it now and am on 1.2 ghz but im not good with OC how can you tell that the phone cant handle the OC like heat wise freezing rebooting? How can you tell I dont want to kill my vibrant lol
Armen1er said:
Im downading it now and am on 1.2 ghz but im not good with OC how can you tell that the phone cant handle the OC like heat wise freezing rebooting? How can you tell I dont want to kill my vibrant lol
Click to expand...
Click to collapse
try it dont set it at boot though then run quadrant, if it doesnt like it it'll freeze then you can just pull battery and reboot, it'll start up at 1GHz
I dont know what setting to use I put unroll textures for performance and then reduce texture size going to see how that goes.
Didnt even see your post lol but yea basically quadrant is the stress test if the phone can handle it?
Armen1er said:
Didnt even see your post lol but yea basically quadrant is the stress test if the phone can handle it?
Click to expand...
Click to collapse
i just installed the 3d thing, didnt know what the other stuff does so not playing with it
yeh, it wont OC if it doesnt need it but if you put load on it like quadrant it does as much as it can so it might freeze or might not
i think on 2.2 mine ran fine at 1.4 but froze at 1.5, cant remember though
im just on 1.2 now, dont need anymore
Yea i was on 1.54 and quadrant ran fine but when I would load up n64oid and play a game it would reboot the phone after a couple of mins
Title practically says it all.
I'm running Nottach's Darkside v1.3, 1.97 radio, and v0.1.9 of Faux's kernel.
I was informed that the disappearing widgets was almost solely kernel related, as well as that v0.1.9 fixed such issue.
Any ideas? Was I simply misinformed?
Delete widgets, open Rom Manager, fix permissions, reboot, set widgets, should be fine. Works for me.
Assimilated via WinBorg 4G
CaelanT said:
Delete widgets, open Rom Manager, fix permissions, reboot, set widgets, should be fine. Works for me.
Assimilated via WinBorg 4G
Click to expand...
Click to collapse
Thanks. I'll give it a try.
Oddly enough, I ended up fixing my permissions a couple times today (for an unrelated reason), but that was after I had my widgets set up. Maybe it takes doing it before I throw stuff on my home screen.
Thanks again.
_______________________________
Alright- fixed permissions and re-placed my widgets. Fingies crossed
Faux claims that it's a ROM issue, so i guess we dunno who the culprit is.
i do know that some people have luck using fastboot to clear their data/cache/dalvik, and other people have luck fixing permissions.
i've never had a problem with disappearing widgets, but i do have a problem with my widgets taking a while to load up. they'll be there, and none of their settings or features will work for a few minutes after random reboots. using CM7 on 0.1.9, i just take it as a small price to pay for having such an awesome kernel and ROM.
Alcapone263 said:
i do know that some people have luck using fastboot to clear their data/cache/dalvik, and other people have luck fixing permissions.
QUOTE]
This is a point worth noting. I always fastboot -w before installing a new ROM. I have found that this is the best way for me to have a clean flash with no issues after. Maybe this coupled with fixing permissions is the best way to go. I do believe it works better using fix permissions through Rom Manager than through CWM also. I don't know what the differences are if any, but there has been feedback to indicate one works better than the other for the widget problem.
Click to expand...
Click to collapse
I got no love with anything.
Heard it was out down to possibly being launcher pro.
I had to do a radical revamp.
Swyped from "Mount" Olympus
Its not Launcher Pro, I use Go Launcher and have the exact same issue.
What I have is:
Brazilian Atrix - d00
nCrust 0.7
faux 0.1.9 oc kernel (working great at 1.3GHz and UV, ROCK STABLE)
Trying the fix permissions thing now, will post the results.
Good luck,
Well I will say that when I was using faux's kernel I had the issue, but now since installing Alien 4 and using the stock kernel, I have not had the issue (knock on wood). I still kringe every time I reboot because I use a few small widgets and it is a pain setting them up especially when you are on the go.
But my point is that it may have something to do with the kernel mod. I will Nandroid and install faux's latest and see what happens. If they disappear the kernel may be the culprit.
Alcapone263 said:
but there has been feedback to indicate one works better than the other for the widget problem.
Click to expand...
Click to collapse
Yes, I love the Romracer CWM but the fix permissions in it did nothing to fix the widget problems for me on other Faux kernels. The Rom Manager that was bundled with the Aura ROM fixed it first time (I tried everything else other than fastboot).
rpolansky said:
Yes, I love the Romracer CWM but the fix permissions in it did nothing to fix the widget problems for me on other Faux kernels. The Rom Manager that was bundled with the Aura ROM fixed it first time (I tried everything else other than fastboot).
Click to expand...
Click to collapse
I tried everything as well...for me apparently it was the way I unlocked the bootloader. I used the Pudding files to unlock my BL and when I tried using KP's unlock sbf it fixed my widget issues with all the faux kernel's.
See the details from this post http://forum.xda-developers.com/showpost.php?p=16508191&postcount=6 it's the only thing that worked for me. I did all the suggestions...flash stock sbf, fix permissions, wipe cache before installing the kernel in all possible method. If it was suggested I tried it and this is the only thing that worked for me.
Hopefully this helps.
gpagador said:
I tried everything as well...for me apparently it was the way I unlocked the bootloader. I used the Pudding files to unlock my BL and when I tried using KP's unlock sbf it fixed my widget issues with all the faux kernel's.
See the details from this post http://forum.xda-developers.com/showpost.php?p=16508191&postcount=6 it's the only thing that worked for me. I did all the suggestions...flash stock sbf, fix permissions, wipe cache before installing the kernel in all possible method. If it was suggested I tried it and this is the only thing that worked for me.
Hopefully this helps.
Click to expand...
Click to collapse
I guess it depends on which ROM one is on. I tried the reunlock above and no joy. It wasn't until I fixed permissions using ROM manager that it worked. 15 hrs and multiple reboots no loss of widgets or errors.
rpolansky said:
I guess it depends on which ROM one is on. I tried the reunlock above and no joy. It wasn't until I fixed permissions using ROM manager that it worked. 15 hrs and multiple reboots no loss of widgets or errors.
Click to expand...
Click to collapse
Hmm...this may be my problem. I've been using Romracer's recovery, but if people are saying it does nothing in terms of properly fixing the permissions, then I may have to try a different recovery.
Also, CaelanT, the -w command...is that done on the phone after you power up/hold volume down (to access the menu) or is it done through ADB or some other command interface?
Also, how deep does it wipe?
I'm glad to see people coming together and looking for solutions here.
Alcapone263 said:
Faux claims that it's a ROM issue, so i guess we dunno who the culprit is.
i do know that some people have luck using fastboot to clear their data/cache/dalvik, and other people have luck fixing permissions.
i've never had a problem with disappearing widgets, but i do have a problem with my widgets taking a while to load up. they'll be there, and none of their settings or features will work for a few minutes after random reboots. using CM7 on 0.1.9, i just take it as a small price to pay for having such an awesome kernel and ROM.
Click to expand...
Click to collapse
i'm almost positive it's his kernel. im running the stock rom, on his previous kernels (i haven't tried 1.9 yet because of this issue) i had this problem. when i switched to kholks kernel or the stock kernel i no longer had the issue despite being on the same rom.
xyrovice said:
Hmm...this may be my problem. I've been using Romracer's recovery, but if people are saying it does nothing in terms of properly fixing the permissions, then I may have to try a different recovery.
Also, CaelanT, the -w command...is that done on the phone after you power up/hold volume down (to access the menu) or is it done through ADB or some other command interface?
Also, how deep does it wipe?
I'm glad to see people coming together and looking for solutions here.
Click to expand...
Click to collapse
Use Rom Manager to fix permissions. Romracers doesn't fix the widget problem.
You will need moto-fastboot on your PC. Download here - http://forum.xda-developers.com/showthread.php?t=1138092 and unzip to the root of your C drive. Should be in C:\moto-fastboot.
For moto-fastboot -w, boot holding down volume, then press up volume when you see fastboot on your phone.
Connect phone to PC via USB.
Open a cmd prompt on your PC and type cd C:\moto-fastboot
Type moto-fastboot devices (Your phone should show up if you are connected).
Type moto-fastboot -w (Your phone will be wiped like a data/factory reset wipe, but it appears to be a deeper wipe. Internal SDCard and ext-SDCard should not be touched).
Type moto-fastboot reboot (Phone will reboot).
Note where there are spaces in the commands above!
legion21 said:
i'm almost positive it's his kernel. im running the stock rom, on his previous kernels (i haven't tried 1.9 yet because of this issue) i had this problem. when i switched to kholks kernel or the stock kernel i no longer had the issue despite being on the same rom.
Click to expand...
Click to collapse
I think so too because I did a fruitcake gbread reload and no problems with stock. I then loaded the Faux 1.3OC kernel and widget problems again.
Using fastboot for the deep clean makes a lot of sense. Next time I switch roms this is what I am going to do.
Hi there again,
Well, I just confirmed that the Rom Manager - Fix Permissions method works, at least for my combination of hw, Kernel and Rom.
Tried fixing via CWM without results, downloaded Rom Manager from the Market, Fixed the permissions using it, re-added my widgets and 3 boots aftear they are all there.
Again, I have the following:
Brazilian Atrix - d00 Tegrapart
nCrust 0.7 ROM
faux Kernel 0.1.9 (working rock solid at 1.3GHz AND undervolted).
Hope it helps.
sandro.bertini said:
Hi there again,
Well, I just confirmed that the Rom Manager - Fix Permissions method works, at least for my combination of hw, Kernel and Rom.
Tried fixing via CWM without results, downloaded Rom Manager from the Market, Fixed the permissions using it, re-added my widgets and 3 boots aftear they are all there.
Again, I have the following:
Brazilian Atrix - d00 Tegrapart
nCrust 0.7 ROM
faux Kernel 0.1.9 (working rock solid at 1.3GHz AND undervolted).
Hope it helps.
Click to expand...
Click to collapse
the fix permissions didnt work for me on the older versions of his kernel, but im not using it now anyway so i can't say about the current version
Im having this same disappearing widget problem despite fixing the permissions via rim manager... im on fauz1.7 tho running alien... I can't seem to find 1.9 tho iv looked everywhere ... can anyone post the link for faux 1.9...??
DrunkFuX666 said:
Im having this same disappearing widget problem despite fixing the permissions via rim manager... im on fauz1.7 tho running alien... I can't seem to find 1.9 tho iv looked everywhere ... can anyone post the link for faux 1.9...??
Click to expand...
Click to collapse
http://rootzwiki.com/showthread.php...Unified-v0.1.9)OC-1.3GHz-SLQB-BFQ-EXT4-Aug-27
Alright so despite fixing permissions and the whole shenanigans faux 1.9 just isn't working for me... on alien v4... and its definitely a kernel related issue not anything else... 1.7 works fine but at times gets moody and goes crazy... hope this issue is fixed soon...
Sent from my Motorola Atrix
Hi S3 fellow users,
Yesterday i wanted to try some new rom so i flashed Darkys rom with siyah kernel, works fine but flashed back to stock because didnt like the rom, now it reboots itself everytime when its on the lock screen and by itself...
I flashed different stock roms and custom roms with odin for 15times, i wiped everything for 100 times.... dont know what to do? any tips?
I try to flash siyah kernel but that also didnt work.... is there something that can wipe everything and is not a odin flash or a wipe factory from recovery. Please help i need my s3:crying:
Try deleting the initd folder.might be conflicting scripts in that folder..
You'll find in system/etc,delete initd and reboot..
I have no other idea without more info.
zodiaxe66 said:
Try deleting the initd folder.might be conflicting scripts in that folder..
You'll find in system/etc,delete initd and reboot..
I have no other idea without more info.
Click to expand...
Click to collapse
Thank you:good:, i am try to do that but cant find initd in that folder also not anywhere else but i find other init files but not the initd. Is there any other way to clean such things up? atm i have stock 4.1.1 and latest siyah kernel, everything rooted su, busybox and root browers with all the tools installed running.
dimi22 said:
Hi S3 fellow users,
Yesterday i wanted to try some new rom so i flashed Darkys rom with siyah kernel, works fine but flashed back to stock because didnt like the rom, now it reboots itself everytime when its on the lock screen and by itself...
I flashed different stock roms and custom roms with odin for 15times, i wiped everything for 100 times.... dont know what to do? any tips?
Click to expand...
Click to collapse
Why not try another rom using stock kernel
ignatios123 said:
Why not try another rom using stock kernel
Click to expand...
Click to collapse
Thanks for your help but i did that, tryd different stock roms and didnt work
Did you do a wipe? Roms don't always transition /data smoothly from one to another.
Sent from my GT-I9300 using Tapatalk 2
xSpeced said:
Did you do a wipe? Roms don't always transition /data smoothly from one to another.
Sent from my GT-I9300 using Tapatalk 2
Click to expand...
Click to collapse
Yes i did 10 times wipe, i tryd different custom roms, and different stock roms, with odin and with cwm..
Now what i found out is that it only reboots when the screen is off so in lockscreen. if i hold the phone awake it wont reboot,
is there an tool to clean the whole system up? like intitd that i cant found in any way..
How could i delete all the mods that came from other roms? i cant find the initd folder...
My phone is on stock 4.1.1 siyah kernel, rooted, busybox, cwm recovery 6.0.1.2, have root explorer working.
I did wipe/factory reset, dalvik, fix permission, wipe batt stats, wipe cach flashing kernel/rom official and non official
and my phone keeps rebooting when the screen go's off auto or if i pres the power button.
Did you changed CPU voltage or clock settings earlier?
BTW you can remove files with ADB.
1) Boot into recovery
2) Connect USB
3) open ADB shell - 'adb shell'
4) navigate to the folder - 'cd /system/etc/'
5) Remove the files - 'rm -r init.d'
6) exit and reboot phone
Yes i did that early i try 1800 max in stweaks on siyahkernel and then the phone rebooted, dont know exactly what happend then but everything was fine after that... i also used other roms and kernels...
But thanks for your advice i will try to do this, i am new to ADB so i am going to figure that out right now.
is it possible to do that with cwm recovery on it?
That's what the problem is. I did it to my phone once. I overcolocked and undervolt.
Everything worked fine for few mins. But when I rebooted my phone, it went to lock screen and hang for few secs and then reboot again.
Never go to 1800 but a max of 1600. mine max is 1500 now.
Let me gather more info for you.
rl421403 said:
That's what the problem is. I did it to my phone once. I overcolocked and undervolt.
Everything worked fine for few mins. But when I rebooted my phone, it went to lock screen and hang for few secs and then reboot again.
Never go to 1800 but a max of 1600. mine max is 1500 now.
Let me gather more info for you.
Click to expand...
Click to collapse
Oke thanks very much for your help i realy appriciate that! but when i look inside the s tweaks my clock speed is just normal was that for you also?
Did you change any other settings in stweaks, voltage settings?
You can try some different kernel if your phone have problem with siyah.
rl421403 said:
Did you change any other settings in stweaks, voltage settings?
You can try some different kernel if your phone have problem with siyah.
Click to expand...
Click to collapse
No i think not, but atm i did a fix permisson and now the phone is not rebooting but it takes about 5 seconds for the screen to turn on when the screen is of in lockscreen. i am very confused
Guys i there any way to clean every bit of **** that could be on the phone like init.d??? please help
Had same thing happen to me, my fix, 1st save everything to pc from sdcard and titanium backup if you can. Flash stock rom and then put (i use omega v34) on external sdcard. Flash touch recovery. Wipe cache and dalvik, fact reset then go to usb mount and format everything (except external card obviously) then flash omega rom.
Sent from my GT-I9300 using xda premium
jj92942000 said:
Had same thing happen to me, my fix, 1st save everything to pc from sdcard and titanium backup if you can. Flash stock rom and then put (i use omega v34) on external sdcard. Flash touch recovery. Wipe cache and dalvik, fact reset then go to usb mount and format everything (except external card obviously) then flash omega rom.
Sent from my GT-I9300 using xda premium
Click to expand...
Click to collapse
THank you but i try out this before, nothing works..... :crying:
I didn't read that you formatted your card before, that wipes any conflicting setting, otherwise might be hardware related.
Sent from my GT-I9300 using xda premium
jj92942000 said:
I didn't read that you formatted your card before, that wipes any conflicting setting, otherwise might be hardware related.
Sent from my GT-I9300 using xda premium
Click to expand...
Click to collapse
I just try the exact method you say just to be sure but the same problem remains, i wiped everything that i could but it remains the phone reboots when the screen is off or it dont reboot but it freezes when the screen is off.
I dont think of hardware related problem because when i keep the screen awake i can do whatever i want without problem....
Hello,
I have flashed a few custom ROMs onto my x10i and each time it reaches the lock screen when it starts up it just seems to go into a reboot loop from kernel splash screen to lock screen again. Is there any fix for this ? I have tried using SEUS and restarting the whole process of flashing a kernel, rooting etc but it doesn't seem to work. it literately only happens when it reaches the lock screen. sometimes it lasts longer than that. Whenever I wipe the system it seems to work fine but as soon as a few things are running it starts to reboot again. The current ROM I'm running is PAC-man, with the kernel supplied along with it.
Could anyone help me ?
Thanks,
mmy4life
I have the same problem
use the phone until the battery become empty charge it in off mode up to 100 enter in xrecovery advanced options wipe battery stats and reboot
maybe you did an error when flashing or it runs wrong kernel. my suggestion : just use another ROM there are many nice ROM you can choose, and dont forget to follow step by step installation guide provide by developers.
Is the rom overclocked as this can can happen on some devices try and set the CPU to 998
Sent from my Google Nexus S
mmy4life said:
Hello,
I have flashed a few custom ROMs onto my x10i and each time it reaches the lock screen when it starts up it just seems to go into a reboot loop from kernel splash screen to lock screen again. Is there any fix for this ? I have tried using SEUS and restarting the whole process of flashing a kernel, rooting etc but it doesn't seem to work. it literately only happens when it reaches the lock screen. sometimes it lasts longer than that. Whenever I wipe the system it seems to work fine but as soon as a few things are running it starts to reboot again. The current ROM I'm running is PAC-man, with the kernel supplied along with it.
Could anyone help me ?
Thanks,
mmy4life
Click to expand...
Click to collapse
That usually happens when the ROM is using overclocked CPU settings or an unstable CPU governor as default but it can also be defaulted inside the kernel. You simply flash another kernel and appropriate ROM.
CCVader13 said:
That usually happens when the ROM is using overclocked CPU settings or an unstable CPU governor as default but it can also be defaulted inside the kernel. You simply flash another kernel and appropriate ROM.
Click to expand...
Click to collapse
I've tried this multiple times, it happens on the stock ROM and kernel.
mmy4life said:
I've tried this multiple times, it happens on the stock ROM and kernel.
Click to expand...
Click to collapse
Install xrecovery and wipe the dalvik cache.
Sent from my Xperia X10 using xda app-developers app
CCVader13 said:
Install xrecovery and wipe the dalvik cache.
Sent from my Xperia X10 using xda app-developers app
Click to expand...
Click to collapse
I've also tried that. I went through all the proper procedures when installing a new rom.
mmy4life said:
I've also tried that. I went through all the proper procedures when installing a new rom.
Click to expand...
Click to collapse
Then it has to be a hardware problem. Try removing your SD card before booting it up.
Sent from my Xperia X10 using xda app-developers app
I've had the same problem
1eyedmonster said:
Is the rom overclocked as this can can happen on some devices try and set the CPU to 998
Sent from my Google Nexus S
Click to expand...
Click to collapse
I flashed 2.3 and it kept rebooting after a while, so i re flashed 2.1 and it is more stable but reboots if i open a app or anything that uses ram.
btw 1eyedmonster how do you set the CPU to 998?
I am also having ths reboot and crash issue... is there no fix for it? I have read about this reboot error at numerous sites. Must be a bug or summin man... or we dn summin wrong... and if it were hardwars related then to what hardware wd you be referring to? Is it a replaceable part? How easy wd such a task honestly be... i have 2.3.3 with 3.0.0.75 and no matter what it just wont stop dropping itself while i just start to appreciate it all over again... so im sure there have bn plenty issues regards this... so is there an answer?
Sent from S3Terry, Galaxy SIII GTI9300, using 8ta/Telkom Mobile.
reboot issue
mmy4life said:
I've also tried that. I went through all the proper procedures when installing a new rom.
Click to expand...
Click to collapse
hi,
i have the issue, did you fixe your phone ?
thank
I'm using Beanstalk on my phone and I get a lot of random reboots. Mostly when I'm unlocking the phone. I press the button and the soft keys light up the phone freezes and 5 or so seconds later it reboots. It also happens during calls sometimes when I take the phone away from my face and the screen turns on and sometimes when I'm listening to music. It's also happened a few times while I was using the phone. I don't restore any data(unless you count the apps that automatically reinstall from the playstore when I boot the phone, and a few apks from blackmart) I've tried reflashing but that was only a temporary fix. I always have problems with roms being really buggy even though I always to clean flashes.
Can someone help me to fix this? I use this device to play music over a sound system for crowds of people so I really need this bug fixed. (preferably without reflashing but I will if need be.)
maybe try this
SockmanTGR said:
I'm using Beanstalk on my phone and I get a lot of random reboots. Mostly when I'm unlocking the phone. I press the button and the soft keys light up the phone freezes and 5 or so seconds later it reboots. It also happens during calls sometimes when I take the phone away from my face and the screen turns on and sometimes when I'm listening to music. It's also happened a few times while I was using the phone. I don't restore any data(unless you count the apps that automatically reinstall from the playstore when I boot the phone, and a few apks from blackmart) I've tried reflashing but that was only a temporary fix. I always have problems with roms being really buggy even though I always to clean flashes.
Can someone help me to fix this? I use this device to play music over a sound system for crowds of people so I really need this bug fixed. (preferably without reflashing but I will if need be.)
Click to expand...
Click to collapse
Try Doing a Full Wipe of Your Android System.
Use [TWRP_Recovery_2.7.0.0][Unofficial][quincyatt] Go into factory Wipe > Then Click Advance > Then Wipe Everything but your SD card .
Flash Beanstalk > then Wipe Cache and dalvik > then install PA Gapps > then Wipe Cache & Dalvik again then reboot, Also try installing > Polluti0n's Rom Patch!!
It worked wonders for me , Use Uber kernal & Set Govener to Whetle.
Happy Flashing , Any more Questions Please ask
Joshua Mr PC Repair said:
Try Doing a Full Wipe of Your Android System.
Use [TWRP_Recovery_2.7.0.0][Unofficial][quincyatt] Go into factory Wipe > Then Click Advance > Then Wipe Everything but your SD card .
Flash Beanstalk > then Wipe Cache and dalvik > then install PA Gapps > then Wipe Cache & Dalvik again then reboot, Also try installing > Polluti0n's Rom Patch!!
It worked wonders for me , Use Uber kernal & Set Govener to Whetle.
Happy Flashing , Any more Questions Please ask
Click to expand...
Click to collapse
I flashed twrp with odin and now I can't flash most roms. (I managed to get an old cyanogenmod 10.1 to work). Not even my backup of my stock will work. I tried switching back to cwm but I get the same problems. sometimes it say they are invalid sometimes it say they aren't for my device(These are all roms I've flashed before). I've even tried new roms. Please Help Quickly!
SockmanTGR said:
I flashed twrp with odin and now I can't flash most roms. (I managed to get an old cyanogenmod 10.1 to work). Not even my backup of my stock will work. I tried switching back to cwm but I get the same problems. sometimes it say they are invalid sometimes it say they aren't for my device(These are all roms I've flashed before). I've even tried new roms. Please Help Quickly!
Click to expand...
Click to collapse
I just Tried it again .
Had No Issues ,
Can You Try with a new SD Card .
Then Do The Wipe
also load TWRP Via Recovery , If You have CWM Go to Install Click > TWRP .
SockmanTGR said:
I flashed twrp with odin and now I can't flash most roms. (I managed to get an old cyanogenmod 10.1 to work). Not even my backup of my stock will work. I tried switching back to cwm but I get the same problems. sometimes it say they are invalid sometimes it say they aren't for my device(These are all roms I've flashed before). I've even tried new roms. Please Help Quickly!
Click to expand...
Click to collapse
Have you vot the right TWRP? One wont work on KK
If you are getting a status 7, your recovery needs updating.
Are you formatting your system?
Sent from my SAMSUNG-SGH-I527 using xda app-developers app
Put on SD Card and install
captemo said:
Have you vot the right TWRP? One wont work on KK
If you are getting a status 7, your recovery needs updating.
Are you formatting your system?
Sent from my SAMSUNG-SGH-I527 using xda app-developers app
Click to expand...
Click to collapse
This is the one that works for KK
[TWRP_Recovery_2.7.0.0][Unofficial][quincyatt]
Alright i managed to fix the damage but i'm back to beanstalk with cwm. (i had to go through cyanogenmod and put it on using rom manager)
I'm still getting the bugs though(as far as I can tell. I've had one reboot already)
CWM is now functioning normally.
You mentioned a kernel? How would I go about that? I'm still relatively new to rooted devices. So please provide a detailed step-by-step information if you can.
SockmanTGR said:
Alright i managed to fix the damage but i'm back to beanstalk with cwm. (i had to go through cyanogenmod and put it on using rom manager)
I'm still getting the bugs though(as far as I can tell. I've had one reboot already)
CWM is now functioning normally.
You mentioned a kernel? How would I go about that? I'm still relatively new to rooted devices.
Click to expand...
Click to collapse
you can go to the Original Development thread and find the thread for the Uber kernel. pay attention cause one is for JB and the other for KK. whichever Beanstalk your running get the right kernel.
you will flash it just like you flash a rom, or more like you would flash the gapps. you don't have to start over flashing rom again, you are just flashing the kernel to it.
the reboots sound a bit off to me as if you are flashing completely clean, KK is very stable for me and most others. maybe try flashing rom twice as you can get 2 different reactions on 2 different flashes.
flash rom
flash rom again
gapps
boot and wait
reboot
go back and flash your kernel
make sure you get all your wipes in middle of all this.
25625292 7345
captemo said:
you can go to the Original Development thread and find the thread for the Uber kernel. pay attention cause one is for JB and the other for KK. whichever Beanstalk your running get the right kernel.
you will flash it just like you flash a rom, or more like you would flash the gapps. you don't have to start over flashing rom again, you are just flashing the kernel to it.
the reboots sound a bit off to me as if you are flashing completely clean, KK is very stable for me and most others. maybe try flashing rom twice as you can get 2 different reactions on 2 different flashes.
flash rom
flash rom again
gapps
boot and wait
reboot
go back and flash your kernel
make sure you get all your wipes in middle of all this.
Click to expand...
Click to collapse
I followed your instruction with the kernel(http://forum.xda-developers.com/showthread.php?t=2326786) Had to download it directly to my phone. It didn't like it from my laptop.
Successfully installed.
I'll let you guys know if my problem continues,
SockmanTGR said:
I flashed twrp with odin and now I can't flash most roms. (I managed to get an old cyanogenmod 10.1 to work). Not even my backup of my stock will work. I tried switching back to cwm but I get the same problems. sometimes it say they are invalid sometimes it say they aren't for my device(These are all roms I've flashed before). I've even tried new roms. Please Help Quickly!
Click to expand...
Click to collapse
You are not using twrp from the thread linked. Also do NOT use the twrp app for the recovery as my recovery is not found there. It can only be found in my thread. Flash it in recovery & you're good to go.
SockmanTGR said:
I'm using Beanstalk on my phone and I get a lot of random reboots. Mostly when I'm unlocking the phone. I press the button and the soft keys light up the phone freezes and 5 or so seconds later it reboots. It also happens during calls sometimes when I take the phone away from my face and the screen turns on and sometimes when I'm listening to music. It's also happened a few times while I was using the phone. I don't restore any data(unless you count the apps that automatically reinstall from the playstore when I boot the phone, and a few apks from blackmart) I've tried reflashing but that was only a temporary fix. I always have problems with roms being really buggy even though I always to clean flashes.
Can someone help me to fix this? I use this device to play music over a sound system for crowds of people so I really need this bug fixed. (preferably without reflashing but I will if need be.)
Click to expand...
Click to collapse
i had the same problem and went to liquid smooth and is stable
jemsTV said:
i had the same problem and went to liquid smooth and is stable
Click to expand...
Click to collapse
If you like beanstalk try this fix. New problem I'm getting a lot of graphical bugs now. So far just in browser but everything flickers including system ui
SockmanTGR said:
If you like beanstalk try this fix. New problem I'm getting a lot of graphical bugs now. So far just in browser but everything flickers including system ui
Click to expand...
Click to collapse
If you are using Beanstalk you should probably read the BeanStalk thread, both of these common problems (screen flicker and failure to wake) are solved with a Aroma package made by p0llution. You flash it in recovery and all is good. Link is in 1st post, right next to ROM link. You can also switch kernels and boot animations with same package.
delawaredrew said:
If you are using Beanstalk you should probably read the BeanStalk thread, both of these common problems (screen flicker and failure to wake) are solved with a Aroma package made by p0llution. You flash it in recovery and all is good. Link is in 1st post, right next to ROM link. You can also switch kernels and boot animations with same package.
Click to expand...
Click to collapse
Would I need to reflash the ROM to ally another kernel?
SockmanTGR said:
Would I need to reflash the ROM to ally another kernel?
Click to expand...
Click to collapse
As instructed, you need to do some reading. In my last post I gave you instructions on how to add kernel.
Help yourself first, then others will be more than happy to assist.
Sent from my SAMSUNG-SGH-I527 using xda app-developers app
SockmanTGR said:
Would I need to reflash the ROM to ally another kernel?
Click to expand...
Click to collapse
I'll give you some slack 'cause I am still close enough to my first flash that I remember being full of questions, but at least read the OP and most recent pages in your ROM thread. You should skim through it all ideally but some are 100+ pages so....
Kernel switching in general does not require any ROM action, there are likely cases that it might be useful but I've never had a problem. You will need to ensure that the kernel is matched to your ROM; KitKat or Jellybean or whatever. I usually do it as I flash a ROM but I have gone back and installed a kernel on a running ROM plenty of times; Uber for instance was released after I had BeanStalk up and running, it is a good kernel so I switched to that.
As a more general point the Note is hard to brick, as long as you don't somehow mess up the recovery (CWM or TWRP) you are just a quick restore away from back to normal. Use the backup function in your recovery, it is your friend and savior. Keep a copy of the back-up on your PC (or Mac) and you will usually be golden.
SockmanTGR said:
Would I need to reflash the ROM to ally another kernel?
Click to expand...
Click to collapse
If you are on BS Rom you should know that all you need to to know is on the OP post-the rom and the patch. The latter contains about 5 different kernels which you can switch betw. to your hearts content. The patch is n00bie proof to make your switches. Really hit BS OP.
SockmanTGR said:
Would I need to reflash the ROM to ally another kernel?
Click to expand...
Click to collapse
Just like all the other kind gents adv'd, it's all in patch's OP:
http://forum.xda-developers.com/showthread.php?t=2535857
Including polluti0n's patches thread:
http://forum.xda-developers.com/showpost.php?p=50529734&postcount=854
He uses aroma installer, so when you flash it (personally, I did it with CWM) you don't need to wipe cache/dalvik nor wipe phone, he mentons this on patch's thread while answering questions I believe. The screenshots show you some differences between the kernels he has available, either CM, Uber or PAC.
Personally, I'm using PAC since for me it seemed to work better with the Xposed's Netflix workaround, whereas it didn't work that well with Uber.
Also, the patch provides fixes, for camera, screen flicker and such.. Give it a try, and you'll definitely love your phone more!