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
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
Hey everyone. I cannot find any information specific to my phone. I have the Galaxy SII Hercules, and I've been trying to get Cyanogen Mod 10 on it. I rooted it just fine, everything worked great. I flashed the CWM Recovery, ran super wipe and super cache wipe after installing the mod. Everything was fine. But then the next day, the phone just died with 75% power left and got stuck rebooting over and over. If I take the battery out, it will let me go into recovery, but then the power button is selecting options without me touching it.
If I unroot the phone and go back to stock, the power button works fine when selecting options in the stock recovery, and the boot loop stops. I cannot find anyone who will tell me what's causing this, or how to fix it, other than "YOu have a loose power button!" But then, why have I not had the problem at all using stock? I prefere the way my phone was working on CM10, especially the better battery life and radio reception.
OK. Well, I managed to find information on google. For some reason searching the forums here doesn't yield results other than finding another poster with the same problem. It seems the version of clockwork recovery I was using would cause the issue. I flashed and rooted with twrp 2.4.4.0 (2.5.5.0 would not finish flashing in odin mode for some reason) and everything is running fine so far. But its only been a couple hours.
SGH-T989 / CM 10.0.0.0 Hercules
ThatBillmanGuy said:
OK. Well, I managed to find information on google. For some reason searching the forums here doesn't yield results other than finding another poster with the same problem. It seems the version of clockwork recovery I was using would cause the issue. I flashed and rooted with twrp 2.4.4.0 (2.5.5.0 would not finish flashing in odin mode for some reason) and everything is running fine so far. But its only been a couple hours.
Click to expand...
Click to collapse
Hopefully your post can help other people. If you try to use those super wipe scripts with CWM 6 you will have major problems. Only use them if you are on CWM 5.0.2.7.
Doing fine after 36 hours. The battery life is 8 hours, 15 minutes with WiFi and GPS on the whole time. It did have a black screen earlier with the four home keys along the bottom lit up. I had to take the battery out, but it came back up no problem. Only glitch so far.
SGH-T989 / CM 10.0.0.0 Hercules
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.
Edit #2
Ok so I downloaded stock firmware from sammobile...and that corrected my problem. So I started fresh, by first installing Philz touch cwm...which seems to work fine and I could still at that point boot up normally.
However, upon attempting to flash a couple of different custom Roms(Deleterious and RocketTab), I am left with the same issue ("Since then, when I reboot, it shows the samsung logo, then goes black. Sometimes if I hit the power button, suddenly the screen appears. Sometimes it doesn't.").
Am I missing something? I'm only trying roms that are specifically for the sm-t210r....I've tried using three different recoveries...and I've been flashing roms...tons...since my original galaxy s phone. Simple stuff. So what the heck is going on?
I want a custom rom...lol...grrr Do these roms just not have bootscreens and I'm just being paranoid?
-----------------------------------
Ok so I just got my tablet and started searching for root methods..
I may have gotten a little ahead of myself, and using odin, I used this method:
http://forum.xda-developers.com/showthread.php?t=2391367
Since then, when I reboot, it shows the samsung logo, then goes black. Sometimes if I hit the power button, suddenly the screen appears. Sometimes it doesn't.
I've tried a few different custom roms, using Philz cwm, and even tried using odin to flash a stock rom I found online(in an attempt to see if using odin would help.)
Same issue.
If it goes into the OS, it seems to run fine...but then more often than not when I reboot again the samsung logo appears, then black. Never to return.
I know it's not bricked but I don't know what else to try. Any suggestions would be great.
Im on sm-t210r..
EDIT:
Think this will work?
http://forum.xda-developers.com/showthread.php?t=1840030
If so, how to I find the bootchain files for the sm-t210r? Or maybe the PIT? (from the second post...sounds more like my problem..)
Nevermind...apparently it was a kernel issue..
Sent from my SM-T210 using XDA Premium 4 mobile app
I've got a Galaxy Tab P5210 that's stuck in a constant boot loop. I flashed it with the correct stock firmware from SamMobile using Odin, but it fails to boot properly. It automatically boots to the stock recovery screen, but the problem is it will instantly reboot as soon as it reaches this screen. I see the dead android with the red triangle and exclamation point for just a second, and it instantly reboots. Is that normal? I don't think that's normal. From what I've been reading, this screen is supposed to stay there until you push the volume keys to bring up a menu, but it reboots so fast that I don't have a chance to even push anything.
I've tried flashing it with other recovery images. I tried using CWM, and it almost worked. With that, as soon as the tablet booted, I'd see the CWM splash screen, and it would instantly reboot. Similarly to how it's booting now but with stock recovery.
I'd like to point out that I've never messed with anything like this before. I work in a computer/small electronic repair shop and a customer brought it to me. She ended up getting into stock recovery and a friend of hers did some serious damage in there which prevented it from booting properly. Normally we don't mess with things like this but, with it being how it was, I figured there was no way I could make it even worse than it already is by working on it. I thought if I flashed the original stock firmware back to it, it would fix it, but that looks like a no-go since it's still booting the same way it was when she first brought it to me.
Is this thing completely broken or is there still hope for it?
No - it should be recoverable. However - any data will most likely be lost.
When you flash with Odin, make sure only F. Reset Time is checked. Use Odin 3.07. Make sure again that firmware is correct before you flash. After it flashes, power off and then on again
Latest KK firmware for the US version of the 5210 is P5210UEU0CNK1_P5210XAR0CNK1_HOME.TAR
Good luck. If you're trying to root, then there are threads in the 10.1 Dev section that should help
M,
this firmware was always my goto for device recovery/restoration https://www.androidfilehost.com/?fid=23060877490005046
posted by user chpettit , flash with odin 3.07
m
OKAstro said:
No - it should be recoverable. However - any data will most likely be lost.
When you flash with Odin, make sure only F. Reset Time is checked. Use Odin 3.07. Make sure again that firmware is correct before you flash. After it flashes, power off and then on again
Latest KK firmware for the US version of the 5210 is P5210UEU0CNK1_P5210XAR0CNK1_HOME.TAR
Good luck. If you're trying to root, then there are threads in the 10.1 Dev section that should help
Click to expand...
Click to collapse
Not interested in rooting, just wanna get the stock firmware back on. Maintaining data isn't a necessity, the customer just wants it back in working order. I tried using that firmware, but I had Auto-Reboot checked.
EDIT
Yeah, it's still doing the same thing. When I first boot it up post-firmware flash I see an Android with a loading bar underneath it, and then it reboots. When it boots again, I see the same Android and then it suddenly changes to the dead one with the red triangle. Maybe I'm just doing something wrong here with the button presses following the flash?
EDIT2
It looks to me like the stock recovery image is just broken, since the tablet just automatically reboots the instant it attempts to load it up. Flashing a new firmware replaces that though, so I don't know how or why it would even be corrupted. Odin reports no errors, so I don't know what's going on. And every guide I'm reading with fixing bootloops all say "go into stock recovery and clear the cache", but I can't even boot into stock recovery. It's like it's not even there. And I know it's not a power button issue causing it to shut down, I can power the device off fully with it, and it will stay off until I press it again. I'm banging my head against the desk here.
What if you flashed a TWRP recovery in Odin. Then if that's successful, boot into recovery and wipe/format everything except ext SD, Then try the ODIN flash again with filr your stock tar
I'm having the same problem and that didn't work for me. It shows the twrp splash screen and reboots. I'm looking for the .pit file it has to be the recovery partition right?
Sent from my LG-D851 using Tapatalk