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.
Related
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.
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...
We've got two G870A phones. I updated both of them to OA1 and re-rooted with Towelroot using the NE1 kernel flash trick. One of them works great, while the other constantly hangs up, cannot maintain wifi connections, etc.
I reflashed with the complete NE1 thinking that I'd do the OTA update again and see what happened. Now, however, the phone boots to the AT&T logo and stays there. After about three minutes, I get a message about Android.process.acore stopping, the phone reboots, and the cycle continues. I've booted to the stock recovery and cleared the cache since that's about all I can do.
Is there anything else I can do or try before doing a factory reset? Naturally, it's my wife's phone that's having all of the problems.
On edit: I did a factory reset. Hopefully this also resolves the battery life issues that this handset was having.
My S6 edge is in a bootloop. I put off the 5.1.1 OTA for a while when my wifi would not turn on. Rebooted, still didnt work. I decided to do the update. installation went great but now its in a boot loop. I flashed the firmware (BOG7) using Odin. It worked. The phone was back on again but then it shut off after a few hours.
Its been stuck in the bootloop again. I flashed BOG7 again. Ive Flashed BOG9. Ive flashed the stock PIT. Ive tried ADB sideload. Smartswitch and Kies do not recognize the device. Of course, Ive wiped cache and factory reset. Attempted booting in safemode. All flashes were successful but when it reboots, It says "erasing" and goes to bootloop (Samsung powered by android).... Drivers are installed and working. MTP is not installed and I cant find the file.
Please .
same problem
I'm having the same problem with boot loop on g925v stock. I'm wondering if the op or anyone else can help!
No mater what I do, phone reboots after almost exactly 1min9 sec. Just enough time to select a language, but not get past the next "activation" screen.
Background: Phone has never been rooted, at first was on og5 and started freezing on the verizon logo, so I factory data reset, and after that nothing has really changed. knox has not been tripped, frp not tripped
First I tried flashing og5 with odin,
(of course checked md5, and odin=pass, then after flashing, I always tried several combinations of booting to recovery for wipe cache partition/ factory reset / and also power down by holding volume down and power button, then select boot in safe mode)
Then tried flashing og7, still boot loop
then tried flashing og9, 3 times, again, also many attempts of factory data reset/ wipe cache partition / safe mode.
I am starting to think this may be a hardware problem, BUT unfortunately I do not have samsung warranty available on this phone so I am pretty much stuck messing with it.
In researching the issue, I have run across quite a few similar freeze/boot loop problems all over the web, and never any real solutions, for both g925v, g920v, and other s6 models. I've also seen a stock s6 g920v that freezes randomly, flashing stock og9 never helped, owner was planning to replace the battery and see if that helps (I have not heard back).
I've tried looking at the boot log but I'm no expert. I know I can't downgrade, but I'm wondering if there is anything I can do with adb, or any other bootloaders that I could try flashing over the og9 (even if just temporarily, assuming I will flash stock og9 again after).
Thanks for any encouragement, help or advice.
I finally gave up on my GS6 Edge because upon carefully taking it apart for the 3rd time I noticed physical damage up by the wifi receiver and SIM card slot. My advice would be to try the things I tried (above) and, if it's not a hardware issue, it may fix the problem. Good luck.
beefriendly said:
I'm having the same problem with boot loop on g925v stock. I'm wondering if the op or anyone else can help!
No mater what I do, phone reboots after almost exactly 1min9 sec. Just enough time to select a language, but not get past the next "activation" screen.
Background: Phone has never been rooted, at first was on og5 and started freezing on the verizon logo, so I factory data reset, and after that nothing has really changed. knox has not been tripped, frp not tripped
First I tried flashing og5 with odin,
(of course checked md5, and odin=pass, then after flashing, I always tried several combinations of booting to recovery for wipe cache partition/ factory reset / and also power down by holding volume down and power button, then select boot in safe mode)
Then tried flashing og7, still boot loop
then tried flashing og9, 3 times, again, also many attempts of factory data reset/ wipe cache partition / safe mode.
I am starting to think this may be a hardware problem, BUT unfortunately I do not have samsung warranty available on this phone so I am pretty much stuck messing with it.
In researching the issue, I have run across quite a few similar freeze/boot loop problems all over the web, and never any real solutions, for both g925v, g920v, and other s6 models. I've also seen a stock s6 g920v that freezes randomly, flashing stock og9 never helped, owner was planning to replace the battery and see if that helps (I have not heard back).
I've tried looking at the boot log but I'm no expert. I know I can't downgrade, but I'm wondering if there is anything I can do with adb, or any other bootloaders that I could try flashing over the og9 (even if just temporarily, assuming I will flash stock og9 again after).
Thanks for any encouragement, help or advice.
Click to expand...
Click to collapse
Sooo... I had a rom installed and decided for the giggles to another one. I wiped everything and it. It worked fine for about an hour, and then it rebooted randomly, i did not think much of it until i tried to unlock the phone. As soon as I entered the pattern it rebooted. I tried it a couple times and it happened every time. Thinking it was a bad rom I wiped everything and flashed my old one back on. Guess what, it kept happening. So I "figured" I must have screwed something up badly. Decided to do a full factory wipe using kdz and lgup. Once that finished I flashed the newest twrp which I believe is 3.0.2, then i flashed the old one back on. Same thing happened, worked for a bit then rebooted randomly and then kept rebooting every time I tried to unlock the phone. (Also flashing the newest gapps package each time, and I redownloaded both gapps and both roms multiple times) I just did another kdz wipe but tried flashing twrp 2.8.7.1. Will flash the old rom again and let you know how it goes in the morning. In the meantime, any ideas of why this might be happening?