I've had my Note for around a month now, and I'm having an issue where the phone will shut itself down at a random time.
If you try to turn the phone on, it'll get stuck on the Galaxy Note N7000 splashscreen. Occasionally if I go into recovery
and select Reboot Phone Now it'll boot properly, but very rarely does it work. I've also tried leaving it on the splashscreen
and coming back an hour later and it will be fine again. It happened twice yesterday and once today.
If I can't get it to boot, the only thing I can do is restore a CWM backup, but doing that multiple times a day is very frustrating.
I'm running a stock XXLSA deodexed and rooted ROM. I've also tried a stock XXLSA non-deodexed and unrooted ROM with the
same issue. The phone was working fine on ICS 4.0.4, but I really need the use of MultiWindow so downgrading is not an option.
I'm using Philz Kernel 3.99.
Any ideas?
iPWNtehNOOB said:
I've had my Note for around a month now, and I'm having an issue where the phone will shut itself down at a random time.
If you try to turn the phone on, it'll get stuck on the Galaxy Note N7000 splashscreen. Occasionally if I go into recovery
and select Reboot Phone Now it'll boot properly, but very rarely does it work. I've also tried leaving it on the splashscreen
and coming back an hour later and it will be fine again. It happened twice yesterday and once today.
If I can't get it to boot, the only thing I can do is restore a CWM backup, but doing that multiple times a day is very frustrating.
I'm running a stock XXLSA deodexed and rooted ROM. I've also tried a stock XXLSA non-deodexed and unrooted ROM with the
same issue. The phone was working fine on ICS 4.0.4, but I really need the use of MultiWindow so downgrading is not an option.
I'm using Philz Kernel 3.99.
Any ideas?
Click to expand...
Click to collapse
That's a common issue with the JB leaks. You have the following options:
- Do a nand backup, do a full wipe, format cache, system and preload, restore your nand backup (might work)
- Do a full wipe, format cache, system and preload, reflash the rom (works always)
Even if you manage to fix it, be prepared that the problem will occur again. For me it was always the same, I flashed the rom, it worked for several days, suddenly it got stuck at the boot logo, I fixed it, after several days the bootloop reoccured.... Eventually I decided to flash a stock ICS rom in order the get a stable device.
Related
I have been using RemICS 1.3 with Semaphore kernel on my phone for a few months. I had a few problems with bootloop at first, which was solved completely after i flashed the Semaphore kernel and my phone has been running smoothly ever since.
However, today my phone started freezing and giving errors out of nowhere. I open a simple application like alarm clock and it says the application is stopped. I was only be able to open a few applications. So, I rebooted the phone thinking it would go back to normal. Unfortunately, rebooting revealed that my phone no longer can boot. It passes the kernel screen, goes to the RemICS animation and gets stuck there. Since I could go into Recovery Mode I have tried to restore from the backup I had from 10 days ago when my phone was running perfectly. Did not work. I had another backup from July, did not work, actually made things worse by stucking my phone at Samsung screen. Wiped cache, Wiped dalvik cache, did not work.. Made things worse by putting my phone into loop boot. I have tried flashing Devil kernel and another version of Semaphore kernel. Did not work.. Phone back into being stuck at RemICS logo.
Nothing I do seems to work. It just won't boot. I could try flashing a fresh firmware but I have some info on my memo application that i need to save as well as some text messages.
I really don't know how this happened out of nowhere. How can I save my data? Please help?
I've tried lots of ROMs, and been stuck in boot loops many times.
I've always got out of them by using Odin, and trying different kernels until one works, semaphore, devil, and an old GB one. Out of all the boot loops I've been stuck in there's never been a single time that one of those kernels hasn't worked...
Maybe I've just been lucky??
Edit: on reading again tho it looks to me that its your ROM that is the problem not the kernel.
I recommend using SMS Backup+ (free) from the play store next time
Sent from my GT-I9000 using Tapatalk 2
Hello, I have a problem with my Galaxy Note and I don't know what to do.
A few hours ago I tried to start the device as I usually do after I turn it off, but the device does not turn on and only stays stuck on this screen: "Samsung galaxy note n7000".
I'm running this Rom: "[ROM][4.1.2 JB]Ultimate N7000 XXLSC JellyBean 4.1.2 v5.1".
I have the ability to log into CWM by the combination of the known keys
I hope you guys can help me, thanks in advance.
(Note: The battery is charged and i also tried to remove it and put it back in.)
This problem happened to me before with the xxlsa leaked rom
Do a wipe from a safe kernel and flash the rom again
Try to boot into recovery and do a reboot recovery and then reboot.
Else you may do a backup and restore the same backup. It works most of the time. But a little time consuming.
Had same problem by loosing power. The device wont boot anymore. Fix per, reinstall without wipe did not work. Switch rom
i believe this problem comes to all jelly bean leak always Stuck on the first boot.
just got this problem again how i did it ？press power on Stuck on first boot next step straight away press 3 button go to recovery n hit reboot system n my phone bootup n back to normal.
terminator_5505 said:
This problem happened to me before with the xxlsa leaked rom
Do a wipe from a safe kernel and flash the rom again
Click to expand...
Click to collapse
How can i replace the kernel and reinstall the rom if I cannot see the device on my computer when it's connected?
nokiamodeln91 said:
Try to boot into recovery and do a reboot recovery and then reboot.
Else you may do a backup and restore the same backup. It works most of the time. But a little time consuming.
Click to expand...
Click to collapse
I've already tried both methods you have specified and none of them worked.
My attempt to make a Nandroid backup has failed and the CWM said something like "backup of /data failed".
alvinhaw said:
i believe this problem comes to all jelly bean leak always Stuck on the first boot.
just got this problem again how i did it ？press power on Stuck on first boot next step straight away press 3 button go to recovery n hit reboot system n my phone bootup n back to normal.
Click to expand...
Click to collapse
Hi, this is not the first time I try to boot the device after installing a new rom.
I'm with this rom for a few weeks now and the problem occurred only yesterday.
This is well known problem with xlsc rom. U have to wipe everything and to flash rom. There are some solutions with backup/restore but they didn't work for me.
So, complete WIPE, and than flash!!
Backup of data failed because of insufficient space. Make backup to internal if there is more space.
i have the same problem since i full wipe and flashed asylums 20130302 build. after doing a full wipe and clean install, i started downloading my regular apps from playstore and suddenly it turned off just like when you remove the battery.
i tried the following::
1. full wipe and installed the rom -- it boots up few minutes then shuts off and wont boot up without charger
2. restored from nandroid -- same as above
3. full wipe and installed previous builds -- same
4. full wipe + flashed latest build 20130303 + latest gaps for JB 4.2 -- same
5. check battery stat -- ok
whenever it shuts off, it wont turn back on unless without a charger. it just shuts off at random. this is the second day I'm experiencing it and its frustrating.
any help? thanks
edit:: btw it shuts off at boot animation
In the other thread where you asked this question too there are members who replaced their battery and solved it this way.
Maybe you should try this and replace the battery.
Good luck.
I got same issue and I'm for kill someone. Why these problems on a official rom?
Hello everyone,
I just hardbricked my SGS+ and now I'm a bit curious how this could happen.
This is what I did:
I used to run CM9 RC5 from arco68 along with the Kernel for ICS from Christopher83 and CWM 6.0.1.2.
Because my phone always lost the wifi-connection and also had some freezes I decided to try out CM10 Beta 3 from ivendor.
I backuped my phone, downloaded the zips and even verified the MD5sums. Next I flashed CWM 6.0.1.9 as recommended in the thread from ivendor.
After exporting the nandroid backup and other stuff like photos to my computer I wiped everything as mentioned in the thread, flashed the two zips and rebooted. Everything went fine and I was almost ready with setting up my phone again when I got my first softreboot.
Suddenly it showed the CM-bootlogo and after maybe 10 seconds I was back on my homescreen. I got another two or three softreboots until I decided to flash the Kernel 3.x from CastagnaIT.
I rebooted into recovery, wiped cache and dalvik cache, flashed the zip and rebooted.
Now I wanted to reboot into recovery again to fix permissions but instead I got a softreboot and my phone stuck at the CM10 bootlogo.
I waited for around 5 minutes and then I just turned the phone off and booted into the recovery mode.
Because I wanted a clean install without any problems like softreboots I decided to wipe my phone again (data, cache, system) and just reflash the zip for CM10. And at this point everything went wrong.
I flashed CM10 but when I tried to flash gapps my phone just turned off. And no, the battery was not empty. In fact the battery was at around 50-60% and my phone was also connected to my computer.
I tried to turn on my phone but now it stuck at the Samsung bootlogo.
The next thing I did was probably a horrible mistake. I tried to un-brick my phone but I did not realize that I could boot into download mode without problems so I guess my phone wasn't softbricked at all.
Well, after that I still stuck at the Samsung bootlogo and couldn't enter recovery mode. I got into download mode somehow and maybe this was my second mistake. I tried to flash the "i9001Reset.zip" via Odin. Everything went fine but when Odin said "Close serial port and wait until rebooting" my phone was completely dead. I think it was while I tried to flash the reset-file when I got a message like "MBR: read failed". So somehow I managed to destroy my master boot record.
Now I can't turn on my phone or enter download nor recovery mode. I already removed the battery for about 45 minutes but this didn't work either.
My phone is dead but at least I saved the important data and maybe I'll get a new one through warranty. Or I just buy a Nexus 4.
My questions are:
What did I do wrong especially when I tried to save my phone?
How can I prevent such things from happening?
And at which point I should have got help here in the forum or elsewhere?
I would really appreciate some tips for the future because I already flashed and used a lot of different ROMs but this is the first time something really went wrong.
Thanks for reading and thanks for your help in advance.
(Please excuse my non-perfect englisch.)
Greetings,
Mangoniter
Hi guys
I have a problem with my Note. I have installed several roms over the last year without any problems. Recently though I had a problem. I had been using about a week or two the ROM SuperNexus but a few days ago the powerbutton started not to work. It would at some moments work and some other moments it wouldn't. Very frustrating. I reinstalled the ROM, still didn't help. Then I installed a different ROM. It worked but not for long. Now it also started to reboot itself every 5 minutes or so. No idea why. I decided then to flash a new kernel. Abyss didn't work like I wanted so I installed Speedmod kernel and then installed the stock JB rom. Now that worked all fine and well. No problems at all, but the weird thing is when it gets to about 20-30% on battery, it reboots and then gets stuck at the bootscreen.
Why would this be? I'm afraid there is something really wrong with the phone. Does anyone have an idea what this could be or how I may be able to fix it?
Thanks in advance
Daniel
Edit: Also should not when it gets stuck at boot, wiping data/reset factory helps. Also when it's stuck at the bootscreen, it does get warm I find.
I just did a test with the App eMMC BrickBug Test and it said that Yes. Insane chip.
DanielG27 said:
Hi guys
I have a problem with my Note. I have installed several roms over the last year without any problems. Recently though I had a problem. I had been using about a week or two the ROM SuperNexus but a few days ago the powerbutton started not to work. It would at some moments work and some other moments it wouldn't. Very frustrating. I reinstalled the ROM, still didn't help. Then I installed a different ROM. It worked but not for long. Now it also started to reboot itself every 5 minutes or so. No idea why. I decided then to flash a new kernel. Abyss didn't work like I wanted so I installed Speedmod kernel and then installed the stock JB rom. Now that worked all fine and well. No problems at all, but the weird thing is when it gets to about 20-30% on battery, it reboots and then gets stuck at the bootscreen.
Why would this be? I'm afraid there is something really wrong with the phone. Does anyone have an idea what this could be or how I may be able to fix it?
Thanks in advance
Daniel
Edit: Also should not when it gets stuck at boot, wiping data/reset factory helps. Also when it's stuck at the bootscreen, it does get warm I find.
Click to expand...
Click to collapse
1. Boot your phone in recovery and flash the latest kernel from here
http://forum.xda-developers.com/showthread.php?t=1789397
2. Restart and allow some time to settle.
3. reboot and do wipe data /factory reset, wipe cache, wipe dalvik
4. Use pc Odin to flash stock ROM from sammobile.com
5. Check if it works and update...
I was having a few problems with CM11, so I figured I'd start over from stock 4.1.2. flashed (as I have done many times before) via Odin 3.07. On reboot, it went into a boot loop. I never had one before. I re-flashed and got the same result. So, on a hunch, I went into stock recovery, cleared the cache (again) and made a factory reset (again), flashed the root.zip file, flashed CM10.2 and the 4.3 apps, and now it is running.
I'd like to know if anyone can say why the 4.1.2 bootup went into a loop and how to overcome that in the future. I think I might have disconnected from Odin slightly early. It said Reset, but I didn't wait for the beep. Later, I did it again, waited for the beep and now I am back on 4.1.2.