Hi and thanks in advance for your time.
I was on Vengence ROM (MIUI) and Philz kernel until 2 days ago when I suddenly developed a taste for some Kitkat. So I flashed the RawKernel and Mokee rom, following the instructions given on the ROM page.
Initial boot was ok, then I recovered some apps from Titanium Backup, installed Xposed modules and got about my usual work. After a while, I realized the phone would automatically turn off. This was not the usual shutdown process which takes several seconds, when i press the power button to turn the screen off, i found the phone would never wake up, it had shut down.
Then I wanted to reflash the ROM or recover my previous ROM from an image. When I tried to do either, the recovery would just shut down.
Then I tried to flash with ODIN, first the stock rom and then Darky ROM 3.4 RE. Flashing process works fine, the stock rom never boots beyond the samsung logo. DarkyROM loads but in about 5 seconds, it shuts down, without any warning.
I'm out of ideas. Any suggestions / solutions are greatly appreciated
dak****haw said:
Hi and thanks in advance for your time.
I was on Vengence ROM (MIUI) and Philz kernel until 2 days ago when I suddenly developed a taste for some Kitkat. So I flashed the RawKernel and Mokee rom, following the instructions given on the ROM page.
Initial boot was ok, then I recovered some apps from Titanium Backup, installed Xposed modules and got about my usual work. After a while, I realized the phone would automatically turn off. This was not the usual shutdown process which takes several seconds, when i press the power button to turn the screen off, i found the phone would never wake up, it had shut down.
Then I wanted to reflash the ROM or recover my previous ROM from an image. When I tried to do either, the recovery would just shut down.
Then I tried to flash with ODIN, first the stock rom and then Darky ROM 3.4 RE. Flashing process works fine, the stock rom never boots beyond the samsung logo. DarkyROM loads but in about 5 seconds, it shuts down, without any warning.
I'm out of ideas. Any suggestions / solutions are greatly appreciated
Click to expand...
Click to collapse
Change the battery first. Sometimes the battery just die without any warning
Related
okay i had just installed a new rom on my phone it was working fine until i had turned off the phone for awhile then turned it on it was loading then it got stuck on the startup page i took out the battery put back in it got stuck on the samething again please help!!!
slausell said:
okay i had just installed a new rom on my phone it was working fine until i had turned off the phone for awhile then turned it on it was loading then it got stuck on the startup page i took out the battery put back in it got stuck on the samething again please help!!!
Click to expand...
Click to collapse
If nothing else works, you may have to try a hard-reset: With the phone off, hold down the Talk/Send and End buttons then (while still holding down those other buttons) press the power button. This wipes out all the data on your phone and gives a fresh try at the new rom.
If you really want to start from scratch with a freshly-clean rom-memory, use the Task 29 -- recommended for weird problems.
Is this a custom rom -- which one? Have you posted this problem on that rom's thread?
Start the phone in bootloader mode. Then flash task 29. Then boot into bootloader again and flash another rom
alright it worked thank you so much
i haven't posted the problem the rom was a valkyrie v6 titanium
Next time you should ask this questions in the valkyrie thread. Because this has nothing to do with rom development.
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,
FYI; I'm running a Galaxy S i9000 with Slim Bean 3.1 (4.1.2) and semaphore kernel 2.6.5 (was 2.6.0)
So today I woke up my battery was a low at 5%. But everything was normal and had been for a long time. I fell back asleep as I have the day off.
Woke up an hour or two later and my phone was dead. So I put my phone into charge.
Came back about 40 minutes later, enough charge to boot the phone, check my messages, but as I pressed the power button it just went into bootloop. And it hasn't done anything but that since. Every time I try to turn the phone on, the Galaxy S logo appears, then semaphore kernel logo appears, then disappears and reappears and then the whole process repeats.
And I tried plugging in the phone again to charge, but every time I do, the empty battery icon appears, it disappears and reappears, then turns off and turns back on again to do the exact same thing.
So on and off charge, it won't do anything but repeat a few steps over and over.
I cannot enter recovery, cannot boot the phone, the phone does not respond to being plugged into the charger, but I can enter download mode.
So I started googling and trying to fix my problem.
So far I have tried:
- Several three button combos to enter recovery.
- Using ADB to enter recovery (but as the phone isn't on, this doesn't do anything)
- Pulling out the battery, putting it in holding three button combos
- Trying different batteries
- Charging the phone
- Flashing semaphore JB 2.6.5 using ODIN
So basically the phone is bootlooping; when in charge, charge looping (is that even a thing?); and won't respond to any attempts to boot into recovery or boot at all.
I'm trying to avoid just wiping the phone using ODIN and reinstalling from GB to JB (which I have done before, and know how to do).
I'm currently leaving it to bootloop until the battery is actually dead and then I'll see if I can try all over again. Doubt it though.
Try a Devil I9000 kernel .tar from here:
http://rootaxbox.no-ip.org/derteufel/jellybean/
Bejda said:
Try a Devil I9000 kernel .tar from here:
http://rootaxbox.no-ip.org/derteufel/jellybean/
Click to expand...
Click to collapse
What would that do?
It can be or battery this happens with me if the battery is dead it will only go into download mode.....
Sent from my GT-I9000 using xda premium
Zorigo said:
What would that do?
Click to expand...
Click to collapse
Flash it like you did with semaphore .tar,there's good chances your device will just boot fine as if nothing happened.
Such boot loops are a long unexplained story but if you want to use semaphore try 2.6.6 version if it matches your rom,I was having many cwmless bootloops like you had and it didn't happened anymore since this version.
Ahh thanks for the info
I just got impatient and reinstalled everything from the ground up so everything's okay now and I have semaphore 2.9.x on slim (4.2.2)
Where I am:
My Samsung Captivate i897 is soft bricked. When I boot it (On key), it freezes at the at&t screen, or Corn-Kernel screen. I have to remove the battery to shut it off. I can boot into Download mode by connecting USB while holding volume up and down. Odin sees the phone, and I can flash TARs.
If I try a normal boot, the phone freezes at the at&t screen if I flashed KK4_stock_kernel.tar last, and at the Corn-Kernel screen if I flashed CornKernel_UCKK4_v705.tar last.
If I try a recovery boot and I flashed the CornKernel_UCKK4_v705.tar, the phone still freezes at the Corn-Kernel screen.
If I try a recovery boot and I flashed the KK4_stock_kernel.tar, the phone displays the recovery menu. If I choose "reboot system now", the phone freezes at the at&t screen.
How I got there:
I rooted my i897 and was running CyanogenMod 9 with no problems for almost a year. Suddenly, the i897 started using excessive power, discharging the battery in a few hours while the i897 was on but doing nothing with a dark display. The battery monitor said the 60-70% of the power was being used by the Android OS. I factory reset the phone, and flashed CyanogenMod 10.1 (cm-10.1.0-RC1-captivatemtd). The i897 continued to use excessive power. I flashed an old Nandroid backup from a year ago, probably made just after I rooted the i897 and installed ClockworkMod. When I tried to reboot, the phone was bricked. It froze at the at&t screen.
What's wrong? Is there something I can flash from Odin to get the phone working again? Is there some other way to get it working?
remmons said:
Where I am:
My Samsung Captivate i897 is soft bricked. When I boot it (On key), it freezes at the at&t screen, or Corn-Kernel screen. I have to remove the battery to shut it off. I can boot into Download mode by connecting USB while holding volume up and down. Odin sees the phone, and I can flash TARs.
If I try a normal boot, the phone freezes at the at&t screen if I flashed KK4_stock_kernel.tar last, and at the Corn-Kernel screen if I flashed CornKernel_UCKK4_v705.tar last.
If I try a recovery boot and I flashed the CornKernel_UCKK4_v705.tar, the phone still freezes at the Corn-Kernel screen.
If I try a recovery boot and I flashed the KK4_stock_kernel.tar, the phone displays the recovery menu. If I choose "reboot system now", the phone freezes at the at&t screen.
How I got there:
I rooted my i897 and was running CyanogenMod 9 with no problems for almost a year. Suddenly, the i897 started using excessive power, discharging the battery in a few hours while the i897 was on but doing nothing with a dark display. The battery monitor said the 60-70% of the power was being used by the Android OS. I factory reset the phone, and flashed CyanogenMod 10.1 (cm-10.1.0-RC1-captivatemtd). The i897 continued to use excessive power. I flashed an old Nandroid backup from a year ago, probably made just after I rooted the i897 and installed ClockworkMod. When I tried to reboot, the phone was bricked. It froze at the at&t screen.
What's wrong? Is there something I can flash from Odin to get the phone working again? Is there some other way to get it working?
Click to expand...
Click to collapse
Flash Odin KK4 with bootloaders from this post: http://forum.xda-developers.com/showpost.php?p=18370912&postcount=3
From there, Get Corn and then back up to CM10.1.
Now your problem is probably due to a old battery, buy a new one and you should be good to go.
Thanks for the help. As you suggested, I flashed the KK4 with bootloaders, and the phone appears to be back to the factory OS. I will be re-rooting and upgrading to CM10.
As for the battery, I did swap it, and the rapid discharge continued. I will try to go step by step upgrading the OS, and turning on features to try to see if the drain is being caused by hardware or software.
remmons said:
Thanks for the help. As you suggested, I flashed the KK4 with bootloaders, and the phone appears to be back to the factory OS. I will be re-rooting and upgrading to CM10.
As for the battery, I did swap it, and the rapid discharge continued. I will try to go step by step upgrading the OS, and turning on features to try to see if the drain is being caused by hardware or software.
Click to expand...
Click to collapse
Download BBS (BetterBatteryStats) that is in the app section here. It will monitor what drains your battery (software wise). If you're not sure about the results, you can post the screenshots here and we'll do our best to help.
Hi, I installed the Codename Android 4.1.2 firmware on my phone a month back and it was working fine until now.
Last night, I rebooted my phone and kept it to charge. This morning I realized that the phone did not turn on and the screen was black with just the capacitive buttons lighting up on touch.
The only change I made to the setting was to turn off the boot animation for a quicker boot.
I changed the kernel via Odin but it's still not proceeding to reach the homescreen.
Some help please?
hi,
although i am not an experienced user...i may suggest trying to take battery out and push the power button for at least 30 sec and also trying to push middle button for at least 30 sec before you try anything else.
and again, did you check about partition(and themes around it) when or before you make changes to kernel?
may i also just ask because of curiosity as a kind of noob, how long does it take to boot with animation screen and without it?
Hey,
I did a factory reset and it managed to work somehow but I lost all data as I didn't have a backup made.
I rebooted my phone again and now its again stuck on the boot animation.
I tried your method but it's still stuck.
Previously, before changing the kernel it took around 20 seconds to boot with the logo and about 15 without it.
With the new one... well it's been 2 hours now.
how come u change ur kernel via Odin ? is it suitable with ur ROM? try reflash all again. There something wrong with ur kernel, or u tick da repartition on Odin while u flashing kernel