Hello xda
I know there quite a few posts out there with people detailing their phones rebooting randomly but my phone just hit a new level of weird.
My i9000 reboots randomly into cwm recovery menu for no good reason (I know there is another thread about this but that instance is on the Nexus S and the thread has basically died). This started occurring shortly after I flashed slim ROM 4.2.2 build 5 (came from CM10.1 nightlies). Flashing the rom again and updating it to build 6 has done nothing to alleviate the issue.
I'm using the Semaphore kernel with no OC or changed settings, and having recently bought a new battery, I'm really not sure where to start looking for the problem.
If anyone can give me some tips it'd be greatly appreciate, thanks in advance.
HellDiv3r said:
Hello xda
I know there quite a few posts out there with people detailing their phones rebooting randomly but my phone just hit a new level of weird.
My i9000 reboots randomly into cwm recovery menu for no good reason (I know there is another thread about this but that instance is on the Nexus S and the thread has basically died). This started occurring shortly after I flashed slim ROM 4.2.2 build 5 (came from CM10.1 nightlies). Flashing the rom again and updating it to build 6 has done nothing to alleviate the issue.
I'm using the Semaphore kernel with no OC or changed settings, and having recently bought a new battery, I'm really not sure where to start looking for the problem.
If anyone can give me some tips it'd be greatly appreciate, thanks in advance.
Click to expand...
Click to collapse
hi
randomly i will got this problem if i m flashing backward. like from 4.2.2 - 4.2.1, or 4.1.x to 4.0.x. or repeatedly changing between kernel (i always do this to modified ROM to suits my settings n need) its probably due to changing partition in system or kernel clash (even i did all wipe) in internalsd.
Sorry to say. it will come worst sometimes if u ignore da problem or keep flashing ROM to avoid it. 'Luckily' about 2 hour ago my sgs just did. Constantly booting to recovery n its juz bootloop between kernel splashscreen n sgs white splashscreen after it.3 combo button will not working for recovery n only download mode accessible.
no more method for me . Juz flashing back to stock firmware JVU +CF-ROOT with odin was da answers
but if u dont familiar with odin.seek guide here
http://forum.xda-developers.com/showthread.php?t=2149455
but use it as ur last method!
clashing between titan.....no! kernel maybe da reason.do some wiping before changing kernel or ROM. n format system if necessary before flashing!
Sent from my GT-I9000 using xda app-developers app
---------- Post added at 04:45 AM ---------- Previous post was at 04:37 AM ----------
Now i m stick with GB Saurom for a while. really tired unbricking my fone as after my sgs softbrick,my pc went crazy :what: n i m stuck with repairing my pc first. then flash my ol lil i9000
Sent from my GT-I9000 using xda app-developers app
Reboots into CMW with Slim Bean 4.3 and Semaphore
Hi guys, any news on the subject? Exactly the same thing happening to me. I did a clean installation of Slim 4.3, after using CM10 and everything seems to be working perfectly except it reboots into CWM every 1-2h!!! I haven't changed any configuration and didn't mess with the kernel that came with the ROM, which is Semaphore... Is it a kernel issue? Should I try to flash the latest version?
HellDiv3r said:
Hello xda
I know there quite a few posts out there with people detailing their phones rebooting randomly but my phone just hit a new level of weird.
My i9000 reboots randomly into cwm recovery menu for no good reason (I know there is another thread about this but that instance is on the Nexus S and the thread has basically died). This started occurring shortly after I flashed slim ROM 4.2.2 build 5 (came from CM10.1 nightlies). Flashing the rom again and updating it to build 6 has done nothing to alleviate the issue.
I'm using the Semaphore kernel with no OC or changed settings, and having recently bought a new battery, I'm really not sure where to start looking for the problem.
If anyone can give me some tips it'd be greatly appreciate, thanks in advance.
Click to expand...
Click to collapse
I run into the same problem with my current update of my I9000 to CM 10.2.1 and the Semaphore Kernel 3.3.0 (JB).
Any ideas on this issue from the pros?
I realized that it was happening to me only when I was loosing the network coverage, like being in the underground or roaming or things like that... I don't know if it happens to everyone but in my case it's definitely this. If there is no network available my phone will boot into recovery after a while. If the signal is OK, it doesn't happen. Maybe it has something to do with the modem?!
mar0ni said:
I run into the same problem with my current update of my I9000 to CM 10.2.1 and the Semaphore Kernel 3.3.0 (JB).
Any ideas on this issue from the pros?
Click to expand...
Click to collapse
mlw_es said:
Hi guys, any news on the subject? Exactly the same thing happening to me. I did a clean installation of Slim 4.3, after using CM10 and everything seems to be working perfectly except it reboots into CWM every 1-2h!!! I haven't changed any configuration and didn't mess with the kernel that came with the ROM, which is Semaphore... Is it a kernel issue? Should I try to flash the latest version?
Click to expand...
Click to collapse
mar0ni said:
I run into the same problem with my current update of my I9000 to CM 10.2.1 and the Semaphore Kernel 3.3.0 (JB).
Any ideas on this issue from the pros?
Click to expand...
Click to collapse
mlw_es said:
I realized that it was happening to me only when I was loosing the network coverage, like being in the underground or roaming or things like that... I don't know if it happens to everyone but in my case it's definitely this. If there is no network available my phone will boot into recovery after a while. If the signal is OK, it doesn't happen. Maybe it has something to do with the modem?!
Click to expand...
Click to collapse
Deactivate Deepidle in Semaphore manager app and these reboots should be gone.
Did the trick for me.
hertzschi said:
Deactivate Deepidle in Semaphore manager app and these reboots should be gone.
Did the trick for me.
Click to expand...
Click to collapse
Yes, I did this and so far no reboots anymore.
Related
Hi, I have rooted using Doomlord's method. But I have problems waking the note up from sleep. Upon pressing home/power button, the black screen displays random red/blue/green/white pixels appearing slowly until the entire screen is filled like in milkyway. I have to try repeatedly to get back to my widget locker screen. Anyone can help? Thank you.
I have never heard of your problem before, but it sounds like a cool effect.
Sent from my superior GT-N7000 using Tapatalk
Zamboney said:
I have never heard of your problem before, but it sounds like a cool effect.
Sent from my superior GT-N7000 using Tapatalk
Click to expand...
Click to collapse
Yeah it looks pretty cool. like the milky way. Haha I think it's just a problem with the set's display. I'm fine when on stock firmware and kernel. When I tried flashing franco kernel the problem recurred. Found a guy on franco.kernel's thread with the same issue.
iamastone said:
Yeah it looks pretty cool. like the milky way. Haha I think it's just a problem with the set's display. I'm fine when on stock firmware and kernel. When I tried flashing franco kernel the problem recurred. Found a guy on franco.kernel's thread with the same issue.
Click to expand...
Click to collapse
Did you recently buy your SGN? I remember reading somewhere that it is due to the newer notes' kernel sources. I get the same issues too. So atm, I just stick with a rooted CF kernel.
coolfire said:
Did you recently buy your SGN? I remember reading somewhere that it is due to the newer notes' kernel sources. I get the same issues too. So atm, I just stick with a rooted CF kernel.
Click to expand...
Click to collapse
Yes it's only a couple of weeks old someone with similar issues has rocket rom v22 and has no issues, so maybe you'd wanna try also.
Hi Guys,
mine is a few days old and has the exactly same problem with all not stock kernels. So do you think there will be a fix for this?
greets
phasA
phasA said:
Hi Guys,
mine is a few days old and has the exactly same problem with all not stock kernels. So do you think there will be a fix for this?
greets
phasA
Click to expand...
Click to collapse
I really have no idea man. I hope there'd be a fix. I tried flashing rocket rom v22 and got bootloop. Not sure if i did it wrong or if it's the new kernel causing the problem reverted back to stock.
iamastone said:
I really have no idea man. I hope there'd be a fix. I tried flashing rocket rom v22 and got bootloop. Not sure if i did it wrong or if it's the new kernel causing the problem reverted back to stock.
Click to expand...
Click to collapse
Hey, I have the same problem and after my research, our note from SG which I believe you recently bought too needs to use kernel 2.3.6.14 above. So suppose your rom is fitted with say a Franco kernel, what you can do is:
1. Flash the rom, then after which reboot and make sure it loads fine. Access back to recovery with VOL UP + MENU + POWER, flash a new kernel.
2. replace the kernel in the .zip of the rom and then flash it as normal.
Scared the **** out of me too, I thought I bricked my phone
Kernel related 100%
Hi, I have an SGSplus (i9001) and I've been using arco68's and ivendor's CM9 ROMs for a few months now. Right now I'm using ivendor's latest RC9 plus CastagnaIT's ExtremeUV (without any OC, I'm using the standard 245-1401 MHz range) and it's fairly stable.
I always had some problems in real-time performance: it seems to me that when there is a process background the application in foreground becomes incredibly sluggish, maybe needing 10 seconds to input a single key… then, after a bit, the background process finishes his business and things go back to normal. Using BetterBatteryStats I have pinpointed a couple of bad application and removed them and now this happens rarely enough (but still happens). But this is not my question…
On Friday I decided to try ivendor's new CM10 alpha 5 and it simply doesn't boot: no "blue boy" loader at all.
I tried both the straight ROM and with the addition of CastagnaIT's kernel. I tried both with and without google apps (but I guess that doesn't matter at all, since that's userland stuff and I'm not seeing the kernel boot yet)
I put CM9 ivendor+CastagnaIT(extremeOC) back and everything is back to normal, but I'm wondering why CM10 is not booting; I think I've done it all correctly… using the new CWM 6.0.1.9 and all.
What could it be?
lap0 said:
Hi, I have an SGSplus (i9001) and I've been using arco68's and ivendor's ROMs for a few months now. Right now I'm using ivendor's latest RC9 plus CastagnaIT's ExtremeUV (without any OC, I'm using the standard 245-1401 MHz range) and it's fairly stable.
I always had some problems in real-time performance: it seems to me that when there is a process background the application in foreground becomes incredibly sluggish, maybe needing 10 seconds to input a single key… then, after a bit, the background process finishes his business and things go back to normal. Using BetterBatteryStats I have pinpointed a couple of bad application and removed them and now this happens rarely enough (but still happens). But this is not my question…
On Friday I decided to try ivendor's new CM10 alpha 5 and it simply doesn't boot: no "blue boy" loader at all.
I tried both the straight ROM and with the addition of CastagnaIT's kernel. I tried both with and without google apps (but I guess that doesn't matter at all, since that's userland stuff and I'm not seeing the kernel boot yet)
I put CM9 ivendor+CastagnaIT(extremeOC) back and everything is back to normal, but I'm wondering why CM10 is not booting; I think I've done it all correctly… using the new CWM 6.0.1.9 and all.
What could it be?
Click to expand...
Click to collapse
Dont call it blue boy his name is cid hm i flashed aokp jb in cwm 5 and all works fine try to flash cwm 5 via odin and try again because cwm 6 are buggy i think..
EDIT: first boot can take long time so be patient
Sent from my GT-I9001 using xda premium
Jonboy2011 said:
Dont call it blue boy his name is cid
Click to expand...
Click to collapse
Wops. :angel:
Jonboy2011 said:
try to flash cwm 5 via odin and try again because cwm 6 are buggy i think..
Click to expand...
Click to collapse
I tried with CWM 5.5.0.4 but it also doesn't work.
Doesn't hang on boot like it did with 6.0.1.9, but just resets back into CWM5 menu after a few seconds.
Oh, nice, it also resets back to CWM5 using the CM9 zip file which always worken with CWM6.0.1.2.
(I guess I'll use Odin to put CWM6 back and CM9 with that and be content with that)
lap0 said:
Wops. :angel:
I tried with CWM 5.5.0.4 but it also doesn't work.
Doesn't hang on boot like it did with 6.0.1.9, but just resets back into CWM5 menu after a few seconds.
Oh, nice, it also resets back to CWM5 using the CM9 zip file which always worken with CWM6.0.1.2.
(I guess I'll use Odin to put CWM6 back and CM9 with that and be content with that)
Click to expand...
Click to collapse
Hm have you try to flash aokp jb rom by crybert ? Full wipe flash full wipe and wait.. If this doesnt work your s plus is a transformer and at night a toaster sorry O-
EDIT : wait system.boots every time in.recovery without any butten pressed ?
Sent from my GT-I9001 using xda premium
Jonboy2011 said:
system.boots every time in.recovery without any butten pressed ?
Click to expand...
Click to collapse
Yep. That's what it did.
Now I've put CWM6.0.1.9 back with Odin and using that I managed to put ivendor CM9 RC5 back, so that I can put AOKP rom in the /sdcard and try it.
Whops. I guess that the changelog might explain what was happening.
2012-11-22: CM10 alpha4 [1] [2]
No changes only a working build, instead of the crappy alpha3 build
Click to expand...
Click to collapse
lap0 said:
Whops. I guess that the changelog might explain what was happening.
Click to expand...
Click to collapse
Whops oh sorry for the work with cwm :/
Sent from my GT-I9001 using xda premium
No problem.I wonder why CWM5504 didn't work for me, but oh well, newer ivendor CM10 RC5 just booted correctly, case solved!
today i flashed your 4.2.1beta to galaxy note n7000 i got some problems
my bluetooth is not even working its not starting
camera got hanged after clicking some photos and have to restart the phont
my bettry was 80% and after only 2 restarts my battery is only 15% i restarted phone because of camera got hanged and it happened in 1 hour its so bad and i have isue with my that my phone some times hang and dont responds so i have to restart it some times it happen >3 times in a day and some times it wont happen this happen with every rom i installed and i tried most of roms kindly give me some instruction to do something
please reply as soon as posible because ur rom is very nice and dont want to change it. thanks in advance...
its beta 1 so bugs are expected...
those are known bugs and maybe fixed in time, maybe on next build...
didnt have that battery issue though...
slimbean lover too
I know that its beta version but this thing are needed so and please can you tell me why my phone habg a lot it happens with every rom
Sent from my GT-N7000 using xda app-developers app
The BT bug is a known one, I'm not sure about the camera one and definitetly not the battery sucker one.
Boot into recovery and wipe data , cache & dalvik cahe.....
Flash ROM again and then see if the problem persists.
If it does, get Better Battery Stats (from the play store) and see if there are any battery draining apps/services running.
As for the speed problem, I've never run into it but a full-wipe should solve it ( full-wipe means wiping cache, dalvik cache and data )
Before flashing a rom read about it..
If want a ROM like Stock Jellybean I suggest you:
CaynogenMod10
OR
Paranoid Droid
If you want Galaxy Note's Official I suggest you
Ultimate_N7000_XXLSC_JBv5.1
OR
JB RocketROM
Yiannis75 said:
Before flashing a rom read about it..
If want a ROM like Stock Jellybean I suggest you:
CaynogenMod10
OR
Paranoid Droid
If you want Galaxy Note's Official I suggest you
Ultimate_N7000_XXLSC_JBv5.1
OR
JB RocketROM
Click to expand...
Click to collapse
Why on earth are you giving a list of ROMs ? :silly:
He's asking for help on a problem not a list of ROMs to flash ?
Are you in the right thread ?
@warfareonky u r rught i m not asking about rom i am in androind from 2 years and i have knowledge about toms and how to flash bro my problem is that my phn some time hangs some time while working and i have to restart it and thnxx all to reply
Sent from my GT-N7000 using xda app-developers app
warfareonly said:
Why on earth are you giving a list of ROMs ? :silly:
He's asking for help on a problem not a list of ROMs to flash ?
Are you in the right thread ?
Click to expand...
Click to collapse
I give a list of roms cause Slimbean Is beta and the problems will not be fixed until an Slimbean 4.2.1 v2]
Anyway he can take files from CM10 or Paranoid DROID ROM
Yiannis75 said:
I give a list of roms cause Slimbean Is beta and the problems will not be fixed until an Slimbean 4.2.1 v2]
Anyway he can take files from CM10 or Paranoid DROID ROM[/QUOT]
thnxx for the list bro.....:good:
but can you solve my other problem that my phone hangs sometimes and have to restart to put it normal and this things happens in every rom i tried mostly all rom but dont no why this things happens
Click to expand...
Click to collapse
Yiannis75 said:
I give a list of roms cause Slimbean Is beta and the problems will not be fixed until an Slimbean 4.2.1 v2]
Anyway he can take files from CM10 or Paranoid DROID ROM
Click to expand...
Click to collapse
thnxx for the list bro.....:good:
but can you solve my other problem that my phone hangs sometimes and have to restart to put it normal and this things happens in every rom i tried mostly all rom but dont no why this things happens
Hi to all,
some days ago I flashed my I9001 from Stock Rom 2.3.6 to CM9 rc4 with Kernel 3.0.62.
Now I have some issues with spontaneously reboots or mobile goes off. Do you encounter same problems? What can I do? Thanks for your help guys.
one2web said:
Hi to all,
some days ago I flashed my I9001 from Stock Rom 2.3.6 to CM9 rc4 with Kernel 3.0.62.
Now I have some issues with spontaneously reboots or mobile goes off. Do you encounter same problems? What can I do? Thanks for your help guys.
Click to expand...
Click to collapse
Have you over clocked played with Theda kernel settings
sent from my 4.2.2 i9000
kevtrysmoddin said:
Have you over clocked played with Theda kernel settings
sent from my 4.2.2 i9000
Click to expand...
Click to collapse
no i haven't done anything.
one2web said:
no i haven't done anything.
Click to expand...
Click to collapse
It sounds like an unstable system have you tried another ROM with full wipes?
It may be your best option
sent from my 4.2.2 i9000
kevtrysmoddin said:
It sounds like an unstable system have you tried another ROM with full wipes?
It may be your best option
sent from my 4.2.2 i9000
Click to expand...
Click to collapse
of course I did a full wipe.
CM9 rc3 seems to be stable although wifi connection seems to be a bit weak.
Will flash again CM9rc4 these days to exclude the flashing was maybe improper.
one2web said:
of course I did a full wipe.
CM9 rc3 seems to be stable although wifi connection seems to be a bit weak.
Will flash again CM9rc4 these days to exclude the flashing was maybe improper.
Click to expand...
Click to collapse
Have u tried jellybean yet?
Sent from my GT-I9000 using XDA Premium HD app
I had the same problem.
However, Doomsday provided a modified and updated kernel some days ago. I've been using that one for a while and I don't remember having many problems since. This is the post http://forum.xda-developers.com/showthread.php?p=37952778&postcount=3555 Hope it helps!
Also, MIsterLemons has just released an updated kernel based on arco's sources which you can find here http://forum.xda-developers.com/showthread.php?p=38059967&postcount=3575, I haven't tested that one (I rather like doomsday's additions) but his kernel might just fix your issues as well without diverging from arco's builds.
EDIT: it appears I had been lucky. I've just had 2 random shutdowns in 5 minutes using Doomsday's kernel...
I know a lot of people will curse me for opening this thread but i really need help. I have searched and could not find my query resolved and i have no other choice left except to post here,
So my dad randomly gave me Galaxy Note (Indian version) today. I mean, this phone is 3 years old. Anyway, i have Sony Xperia L and Xperia SP as my daily drivers and flashing Roms, kernels is quite easy on them as i only require flashtool. I have never before used a samsung product. So, i do not have a clue on how to root it and flash CM/AOSP on it.
I searched quite a lot and came upon a rooting guides and Philz kernel but i have no idea what to do.
Any help would be appreciated, all i want to do is flash a custom Rom (CM 10.1, CM11)
Android 4.1.2 sucks on this beast.
Android: 4.1.2
Baseband: N7000DDLS6
Build No.: JZO54K.N7000DDLSC
UPDATE: So i flashed a .zip:- PhilZ-cwm6-XXLT9-ORA-5.11.2-signed and voila, i have root ;
Any help would be appreciated.
Thanks a lot
Regards,
Ishaan
Didn't you try the cm installer app?
Anyway once you have Philz kernel installed, you can flash the cm 10.1\10.2 zip from recovery. To flash cm 11 you will need to first install raw r4/5 kernel and then go with cm 11.
I appreciate your reply man
Yes I have his kernel the one I have named in the OP.
So I just need to flash cm10/10.1 from recovery?
No need to unlock bootloader or anything or flash a cm based kernel? :$
Regards,
Ishaan
Sent from my GT-N7000 using Tapatalk
So i pretty much messed everything up.
I did as you said and download cyanogenmod installer on both my note and laptop. Everything was going fine and all files were downloaded.
But all of a sudden, CM installer on PC said something like device not found. And on note, there was the CM logo. So i pressed retry but the problem persisted.
So i turned of cm installer, removed battery from device and turned it on. Below the Samsung Galaxy note, there is a yellow triangle and after that the screen goes blank. No samsung or CM bootlogo.
I tried and i am able to get into recovery and download mode. What do i do guys? :'(
Just help me get back to stock and ill be happy.
Thanks in advance
N7000 does not have a lock bootloader at all.
Sent from my GT-N7000 using Tapatalk 2
EDIT: So flashed CM10.2 (4.3.1). Finally the phone is working. Flashed it manually through recovery.
Still getting the yellow error icon.
Only 2 things i require now,
How to get back on complete stock firmware? (4.1.2 INDIAN)
AND,
Remove the stupid error?
Thanks a lot Guys :'D
By flashing a stock firmware using odin. More help here
AND
Google for "Triangle Away"
nokiamodeln91 said:
By flashing a stock firmware using odin. More help here
AND
Google for "Triangle Away"
Click to expand...
Click to collapse
Thank you man
I flashed stock GB Indian version and even the triangle went away. So far so good.
Currently I am on Ultimate Rom v6 with speedmod kernel. The battery life is not impresive.
Any idea how to increase it? Any suggested rom or kernel?
Fyi- I'm using an original samsung battery. Bought a week ago so its brand new.
Regards,
Ishaan
Sent from my GT-N7000 using Tapatalk
Why did you name this "Urgent Help Needed" when it obviously isn't urgent and doesn't say anything about what the problem concerns?
Since the battery is new then you should be getting at least 4h on screen time.
ishanbhatnagr96 said:
Thank you man
I flashed stock GB Indian version and even the triangle went away. So far so good.
Currently I am on Ultimate Rom v6 with speedmod kernel. The battery life is not impresive.
Any idea how to increase it? Any suggested rom or kernel?
Fyi- I'm using an original samsung battery. Bought a week ago so its brand new.
Regards,
Ishaan
Sent from my GT-N7000 using Tapatalk
Click to expand...
Click to collapse
Start by finding issues using wake lock detector and then uninstalling or freezing apps.
XxPixX said:
Why did you name this "Urgent Help Needed" when it obviously isn't urgent and doesn't say anything about what the problem concerns?
Since the battery is new then you should be getting at least 4h on screen time.
Click to expand...
Click to collapse
I had no other name in mind. Sorry for the inconvenience.
Sent from my GT-N7000 using Tapatalk