Good morning,
I've been having some issues after trying to flash AOKP & CM10.1 on my Note 2. In the past I've had no issues flashing on any phones that I've had, but this one for some reason just doesn't want to work.
After I'll flash a rom using TeamWin recovery, it will just sit at the Samsung splash screen for as long as you keep the phone on. When I flash AOKP, it at least goes to the X screen where it sits forever. I'm kind of at a loss because I've never seen this happen before. I can flash back to OEM using my backup just fine, but just nothing other than OEM works.
I've got root, and I even got desperate and followed instructions on this YouTube video: http://www.youtube.com/watch?v=caU-onGSk5o
Am I missing a kernal, or something? Or am I just doing something completely stupid and don't realize it.
Related
I charge my phone overnight everynight. There are times when i wake up in the morning my phone is just stuck on the splash screen. What could be the problem?
-I'm Running on CM6.1.1
-I have a customize splash screen and boot animation
-I used unrevoked root and unrevoked s-off
-I noticed that the random reboot happened when wifi is on (noticed this twice, not sure about the other times)
-And this started to happen (from what i remember) when i tried to flash something over my recovery (toast or something like that, i can't remember i was just following a tutorial for me to able to put a new splash screen. It was for fast reboot to work) then i got stuck on a loop in bootloader. Then i flashed CM6.1.1 to get an image.
Help please?
A clean flash of cm 6.1.2 should not give you any issues. Are you using a custom kernel?
ald3n3 said:
I charge my phone overnight everynight. There are times when i wake up in the morning my phone is just stuck on the splash screen. What could be the problem?
-I'm Running on CM6.1.1
-I have a customize splash screen and boot animation
-I used unrevoked root and unrevoked s-off
-I noticed that the random reboot happened when wifi is on (noticed this twice, not sure about the other times)
-And this started to happen (from what i remember) when i tried to flash something over my recovery (toast or something like that, i can't remember i was just following a tutorial for me to able to put a new splash screen. It was for fast reboot to work) then i got stuck on a loop in bootloader. Then i flashed CM6.1.1 to get an image.
Help please?
Click to expand...
Click to collapse
Random reboots are usually always caused by a custom kernel that your phone does not like.. I could be wrong but that is my experience anyway...
i had the same exact thing except i actually had 6.1.2 clean with no custom stuff. the only thing custom would be the galaxy s theme i put on it.
i would be trying to go to sleep and i would feel my phone vibrate and then i noticed its rebooting, the rebooting is pretty frequent.
i wiped and restored my original backup and installed all the new stuff (radio/wimax/etc.., except hboot)
right now im gonna install a clean 6.1.2 and see how it goes
No custom kernel. Maybe i just need to manually flash cm6 so i can wipe data 3 or 4 times. I kinda don't trust the rom manager and clockwork work recovery method i feel like it doesnt really wipe everything clean before installing.
Sent from my PC36100 using XDA App
How do you un-install a custom ROM
I installed a custom ROM and now (a month or two later) I'm getting reboot after reboot. How do I get rid of the custom ROM?
Also, what does it mean when the phone reboots, then vibrates 5 times and locks up?
To get rid of the custom rom just do wipe through recovery...
And the the locking up? I have no clue why that is... sorry
Sent from my PC36100 using XDA App
I was flashing the newest cm10 as I do every few days. I flash that, then inverted apps, then kernel, then reboot and never had a problem. Now I am getting a blank screen after the "Samsung Galaxy SIII" splash with the button back-lights lit. Nothing else happens, no response. Never had an issue, but now I am worried. Any help here?
EDIT: I tried booting into recovery a few times with no success. Just tried it again and held all 3 buttons past the recovery flash on the top of the screen. Booted into that and re-flashed the update by itself. Phone just booted back up. Not sure what happened, but all is well in my s3 land again.
Usually not a good idea to flash a ROM and kernel at the same time. I know you said that that's the way you've been doing it buuuut....what happened to your phone is the symptom of your phone trying to match up a ROM and separate kernel at the same time, it got confused while booting lol. Best practice it ROM, gapps, reboot system let phone fully boot, reboot recovery and install kernel. Its an extra step but usually avoids what happened to you.
If your using ktoonsez kernel he has a special build for the latest nightly for people with the same problem as yours, it's not in the op, start from the end of the thread and work backwards.
Sent from my SGH-I747 using Tapatalk 2
Dear XDA,
I have tried all I can to fix this problem. Let me explain how it all started.
I was using my phone normally, running the same custom rom ive been running for the past 6 months. I went to turn on wifi then turned off the screen. Later when i went to check my phone the screen would not turn on, so i performed a battery pull. After that i saw the normal google boot screen and then the custom rom boot screen. It stayed on that screen for a few seconds and then went back to the google boot screen. It then did this over and over, ive left it on for an hour once and it kept doing the same thing. Only way to stop this is with battery pull.
So what can i do with the phone:
I can access fastboot
I can access download mode
What have i tried:
I tried the following methods:
1) Flashing a Back Up
2) Wiping data, flashing a rom and gapps
3) fastboot adb http://rootzwiki.com/topic/13819-how-tovzw-return-to-factory-state-unroot-and-relock/
4) ODIN http://rootzwiki.com/topic/27050-vzwodin-files-needed-for-odin-winstructions/
The same issue continues even after successfully completing these methods. Im now down to my last strand and hoping the great xda community can help me.
seanrobot said:
Dear XDA,
I have tried all I can to fix this problem. Let me explain how it all started.
I was using my phone normally, running the same custom rom ive been running for the past 6 months. I went to turn on wifi then turned off the screen. Later when i went to check my phone the screen would not turn on, so i performed a battery pull. After that i saw the normal google boot screen and then the custom rom boot screen. It stayed on that screen for a few seconds and then went back to the google boot screen. It then did this over and over, ive left it on for an hour once and it kept doing the same thing. Only way to stop this is with battery pull.
So what can i do with the phone:
I can access fastboot
I can access download mode
What have i tried:
I tried the following methods:
1) Flashing a Back Up
2) Wiping data, flashing a rom and gapps
3) fastboot adb http://rootzwiki.com/topic/13819-how-tovzw-return-to-factory-state-unroot-and-relock/
4) ODIN http://rootzwiki.com/topic/27050-vzwodin-files-needed-for-odin-winstructions/
The same issue continues even after successfully completing these methods. Im now down to my last strand and hoping the great xda community can help me.
Click to expand...
Click to collapse
Fastboot seems the best solution to me. What exactly went wrong? Also you could try a OMAP flash.
Sent from my Galaxy Nexus using XDA Premium HD app
To be honest I have no idea what happened. It happened out of no where didn't flash a new rom or anything. OMAP flash? Never heard of it but I'll definitely look into it and try it. I've tried fastboot method and still got the same problem sadly
Really hoping this isn't a hardware issue
I just tried an OMAP Flash and still have the same problem. Ive moved on to a new phone but I still want to get this one working. Any other ideas to fix this problem?
Got into the same problem as yours. I googled around, and most people fix this problem by flashing stock image. Basically wipe your phone clean, e.g system,data,cache etc. and then flash in the stock image u downloaded from google website throught fastboot mode. I tried that method, but my phone is still stuck in bootloop. You can give it a try and see if it works
My phone seems to get stuck at the samsung logo whenever I turn off the phone. I am using AOKP, and the first time I just recovered back to ICE then flashed back to AOKP. I can get into recovery but any time I turn/reboot the phone it will not go past the samsung logo. Any solutions other than flashing every time?
edit: I solved it via going into TWRP, doing a backup (I was still stuck), then recovering that backup and rebooting. It seems to work fine now. Odd.
Hey there. Something strange has been going on ever since I re-flashed my phone. When I flash the kernel/rom other than the stock one I get a duplicate Samsung logo when the phone boots. (phone displays Samsung logo, goes black for a second then displays again before boot) I've been flashing and reflashing ever since I got the phone and now I'm getting this. I can get into recovery and download mode just fine and other than that there don't seem to be any other problems. This is just weird. I'm wondering if there's a way to fix this. Also, I'm wondering how such a thing can happen in the first place. I've re-flashed twice now and the result is still the same.
[EDIT]
From what I understand, the boot screen file is located in param.lfs. I've read before that you can add a screen but how in the world would a re-flash cause a duplicate screen to appear? I had a failed kernal flash happen where i couldn't access the recovery and had to start over from scratch but that's happened before.
[UPDATE]
Just tried to mod the boot logo and found out it's requesting "gaudi_bootimage.jpg" twice. I have no idea what this means. Gonna go back in and re-flash the old one back in.