Develop Bugs

Constant Bootloop after flashing ANY kernel

Hey everyone,
Hopefully someone can help me with this situation. I haven't been able to find relevant information yet.
I'm currently running a Rooted Incredible with the latest Virtuous ROM. I'm trying to flash back to the stock .17 kernel from HTC, but ANY kernel I flash onto it causes the screen to load up as far as the red eye, stall and then reboot causing a constant loop. The only way I can get beyond this so far is just flashing my recovery image. I've installed from ROM manager and checked to wipe data/cache (backed up before of course!) and have even booted into recovery manually and flashed from the download folder and the actual zip file. Before that I've wiped data and dalvik cache. I can't figure out what I'm missing here. Any suggestions??? I hope I haven't crippled my Droid by doin this.

DL the new stock kernel to pc mount card to pc put the new kernel somewhere you'll remember then reinstall sdcard and try flashing the kernel that way if you haven't already
Sent from my ADR6300 using XDA App

Hypcrsy said:
Hey everyone,
Hopefully someone can help me with this situation. I haven't been able to find relevant information yet.
I'm currently running a Rooted Incredible with the latest Virtuous ROM. I'm trying to flash back to the stock .17 kernel from HTC, but ANY kernel I flash onto it causes the screen to load up as far as the red eye, stall and then reboot causing a constant loop. The only way I can get beyond this so far is just flashing my recovery image. I've installed from ROM manager and checked to wipe data/cache (backed up before of course!) and have even booted into recovery manually and flashed from the download folder and the actual zip file. Before that I've wiped data and dalvik cache. I can't figure out what I'm missing here. Any suggestions??? I hope I haven't crippled my Droid by doin this.
Click to expand...
Click to collapse
You should not be wiping data when flashing a new kernel.

How does that differ from flashing it from recovery if I may ask? I figured I had done everything properly and even after just going to recovery, wiping dalvik, wiping data then flashing I keep getting the issue.
I'm actually at work at the moment and don't have access to my PC to download it. But I'll give it a shot when I get home. Luckily flashing my recovery image works just fine, I'm just stumped why now it wants to cause me grief.

Hypcrsy said:
How does that differ from flashing it from recovery if I may ask? I figured I had done everything properly and even after just going to recovery, wiping dalvik, wiping data then flashing I keep getting the issue.
I'm actually at work at the moment and don't have access to my PC to download it. But I'll give it a shot when I get home. Luckily flashing my recovery image works just fine, I'm just stumped why now it wants to cause me grief.
Click to expand...
Click to collapse
At the most, you should be wiping dalvik. You should not be wiping data when flashing a kernel. Doing so will result in the self-inflicted grief you're experiencing.

najaboy said:
You should not be wiping data when flashing a new kernel.
Click to expand...
Click to collapse
Sorry I just saw this post immediately after I replied. I thought wiping data applied for both flashing ROMS and kernels.

najaboy said:
At the most, you should be wiping dalvik. You should not be wiping data when flashing a kernel. Doing so will result in the self-inflicted grief you're experiencing.
Click to expand...
Click to collapse
^This. Only wipe dalvik, not data.

Ok I'll give it a shot while I'm here. I was flashing over to the new edition of Kings and it just became incredibly unstable when interacting with SetCPU, so I was just going to go back to the stock HTC one, that's when I got the first constant bootloop. I'll give it a shot and let you guys know what happens. Thanks for the feedback.

Yeah the reload worked this time, I don't know why it was giving me such an issue when I could have sworn it was working ok every other time I've done it before. Any reasons why I'd be getting such a hard time from Kings Kernel 6? I've seen so many rave reviews with it but everytime I have it on my phone it lasts me about ten minutes and then goes back to that same constant boot cycle.

Hypcrsy said:
Yeah the reload worked this time, I don't know why it was giving me such an issue when I could have sworn it was working ok every other time I've done it before. Any reasons why I'd be getting such a hard time from Kings Kernel 6? I've seen so many rave reviews with it but everytime I have it on my phone it lasts me about ten minutes and then goes back to that same constant boot cycle.
Click to expand...
Click to collapse
thats weird anyone else having that problem? haven't tried 6 yet
Sent from my ADR6300 using XDA App

You only need to wipe dalvik if going to and from one with HAVS, but it doesn't hurt to be safe.
Sent from my ADR6300 using XDA App

Thanks for the assistance everyone. I finally got the darn thing stable. But I'm still curious about the kings kernel 6. I was stoked to try it because I was hoping it would be stable. I was having that instability issue with 5. Anyone else know what I'm talking about???
Sent from my rooted Droid Incredible!!

Hypcrsy said:
Thanks for the assistance everyone. I finally got the darn thing stable. But I'm still curious about the kings kernel 6. I was stoked to try it because I was hoping it would be stable. I was having that instability issue with 5. Anyone else know what I'm talking about???
Sent from my rooted Droid Incredible!!
Click to expand...
Click to collapse
Not exactly. I was running 5 on SkyRaider 3.3.2 for a while, then all of a sudden I started having horrible lag while unlocking the phone and for about 7-10 seconds afterwards. Is this what you're referencing? When I switched to BFS6, I didn't have the problem. But the problem did kick in a while after install of 5 (few weeks), I didn't have 6 that long. 6 seemed pretty solid. Give 6 a shot, if you don't like it, just flash something else. Nandroid just to be safe, too.
Sent from my Droid Incredible running Myn's Warm Two Point Two RLS4.

Yeah I always nandroid just in case when I do any serious modification, but I was experiencing the same issue with 6 as I was with 5. Just checking the different limits with SetCPU, anytime I went over 1.1 for overclocking the phone would stay on for about 15-20 seconds and then reboot, get as far as the red eye and then reboot again. That was as far as I ever got with his kernels which is unfortunate.

When testing SetCPU and overclocking, make sure you don't have set on boot enabled.
Sent from my ADR6300 using XDA App

Thanks I'll give it a shot later on.

[Q] Gio won't start without being connected to the charger

Hi,
I've the following problem with my Gio. First, it didn't want to start. When I plugged it the charger, a symbol of the battery appeared on the screen with a yellow triangle, indicating that the temperature is too cold. And it wasn't cold. But I could start up the phone...until I removed the charger. My phone fell out directly.
I had a rooted version of the original firmware, so I tried to connect my phone to Kies. Didn't work. So I flashed a clean rom, 2.3.5 with Odin. My phone is working again, but I still have to connect it to the charger before I can start my phone. If I don't to it, a empty battery appears on the screen. But when the phone is started, I can remove it from the charger and it will still work. But now and than the phone falls out after a while.
At the moment, my phone isn't connected to the charger, but it still thinks that the charger is connected... Picture is attached.
Does anybody here had this problem too? Or do you people know a solution? The problem is, within 2 weeks I go to Sweden for 4 months, so I can't bring in my phone for repair...
Thanks in advance!

Anyone? Or any suggestions? I even can't read the battery gauge, also not in the settings menu. The graph is like a rollercoaster

Maybe you can go to recovery mode and do a wipe, maybe theres a problem with some files.. did you had root and modified something??
I think if you flash another stock rom, fresh, with a factory reset and sd card format, it may fix the problem.. but I havent seen this in xda before, so going to repair centre is good to, but you must be on stock rom and no root or unrooted
Sent from my GT-S5660 using xda premium

maybe you should try to do factory reset before flashing it again

Go to recovery and wipe battery stats and flash a rom with the usual dalvik and data wipes and see if that changes anything.Otherwise idk I never seen or heard anything like this
Sent from my LG-P350 using XDA premium

voetbalremco said:
Maybe you can go to recovery mode and do a wipe, maybe theres a problem with some files.. did you had root and modified something??
I think if you flash another stock rom, fresh, with a factory reset and sd card format, it may fix the problem.. but I havent seen this in xda before, so going to repair centre is good to, but you must be on stock rom and no root or unrooted
Sent from my GT-S5660 using xda premium
Click to expand...
Click to collapse
He can be rooted and on custom rom but then he cant use warranty.
Sent from my LG-P350 using XDA premium

I had this problem too about a month ago. You don't need to take it to repair center, install cwm (look in the gio big thread for help and dl), go to advanced menu, and wipe battery stats. If that doesnt help, do a wipe data/factory reset.
Btw, i had this too when it was about -15 celsius and i was outside. The Gio doesnt like cold :S
Sent from my GT-S5660

Thanks for the comments! I will try to wipe the battery stats. I'll keep you posted!

hsrars-d said:
I had this problem too about a month ago. You don't need to take it to repair center, install cwm (look in the gio big thread for help and dl), go to advanced menu, and wipe battery stats. If that doesnt help, do a wipe data/factory reset.
Btw, i had this too when it was about -15 celsius and i was outside. The Gio doesnt like cold :S
Sent from my GT-S5660
Click to expand...
Click to collapse
I installed CyangenMod 7.1, an did a wipe data. I also wiped the battery stats. No results. So I think that it is a hardware problem, with the battery... So I will bring my phone to a service center, no other option I think. And flash a stock firmware

Yeah that's probably the best thing to do.Good luck
Sent from my LG-P350 using XDA premium
http://www.danasoft.com/ sig/****yeah287168.jpg

Sorry for the dig guys but I'm facing a problem. I was running Gio Pro 1.4 on my phone with A2SD and I noticed the battery was draining fast and I saw the key lights were on even with the key lock so I shut the phone down. When I tried to start it again the phone didn't do anything. I took the battery off, tried downloading, recovery, ram dump mode and only the last one worked but after some time it stopped working also. I tried a friend's battery and nothing. I got home and connected the phone to the charger and everything was normal. I could start the phone, enter recovery, etc. Without the charger the phone was the same, didn't start. I tried a hard reset and nothing so I tried to flash to clockworkmod recovery and to cyanogen rom. The installation went good but I still had that problem. Then I tried to wipe the battery stats, dalvik cache, etc and still the same. I then tried to flash the clockworkmod recovery with odin and the same. I then flashed with an original firmware with every file (incluiding modem) and the phone was working good and I could start without the charger. Now I installed the cyanogen and cwm recovery again and the problem reappeared. Help please?
EDIT: Guys, reflashed with cyanogen and it is now working...Weird..

Just a little bump since the problem came back...
Already flashed to and ICS Rom, back to official rom and the problem's still there, even with the official rom. Any help guys? My battery's in good condition, already wiped everything...I can't find the solution...
EDIT: Sometimes it boots, sometimes it doens't...

the13thing said:
Just a little bump since the problem came back...
Already flashed to and ICS Rom, back to official rom and the problem's still there, even with the official rom. Any help guys? My battery's in good condition, already wiped everything...I can't find the solution...
EDIT: Sometimes it boots, sometimes it doens't...
Click to expand...
Click to collapse
what official rom do you use? try to avoid using KS2/KS5 baseband. they have bug when turning on the phone.

Ks5 doesnt
Sent from my GT-S5660 using xda premium

I fixed it mine
I had the same problem for several months now.. Yersteday i've got a new micro SD card, bigger, and i decided to reinstall to the latest stock ROM 2.3.6, i wiped data, cache partition, Dalvik Cache and Battery Stats and now my Gio is booting like a charm, whithout being connected to the cargher or USB cable. My guess is that the card was defective...

danyrolux said:
I had the same problem for several months now.. Yersteday i've got a new micro SD card, bigger, and i decided to reinstall to the latest stock ROM 2.3.6, i wiped data, cache partition, Dalvik Cache and Battery Stats and now my Gio is booting like a charm, whithout being connected to the cargher or USB cable. My guess is that the card was defective...
Click to expand...
Click to collapse
Hmmm maybe but I doubt that the card would cause such a problem...
Sent from my Optimus Me using xda premium

Back to the original problem of the yellow triangle and not charging. I googled over and over to find a solution, I came across some askme website that had over 30 people say that DROPPING the Samsung Gio from 2 feet will fix it. I decided NOT to do that but slam the phone slightly hard on a desk. It totally fixes this icon (remove the sim and micro sd before slamming it semi hard).
People were dropping it from 2 feet, but I found slamming it (not hard!) fixes it right away. Now the yellow charging icon is gone and my Samsung Gio GT-S5660!

yuprules said:
Back to the original problem of the yellow triangle and not charging. I googled over and over to find a solution, I came across some askme website that had over 30 people say that DROPPING the Samsung Gio from 2 feet will fix it. I decided NOT to do that but slam the phone slightly hard on a desk. It totally fixes this icon (remove the sim and micro sd before slamming it semi hard).
People were dropping it from 2 feet, but I found slamming it (not hard!) fixes it right away. Now the yellow charging icon is gone and my Samsung Gio GT-S5660!
Click to expand...
Click to collapse
This is rather interesting. It could point to a hardware problem. Anyway I also wouldn't recommended dropping it from 2 ft
Sent from my LG-P350 using xda premium

Unfixable boot loop... Help?

Hey everyone,
So this is my last ditch effort to attempt to save my device. I would really prefer not to perform another warranty exchange given that I am not under insurance, but I'm afraid I have no choice.
My phone was rooted and I was using Darkside without issues, as I had been for the past two weeks. I am always careful when I flash roms and I made sure to follow every possible protocol. That's the background information.
My battery life was running at approximately 6 percent yesterday and I sent a text message as normal, and it was stuck at sending. I tried turning wireless data off from the toggles in the pull-down and it was unresponsive. When I went to Wireless Network in the settings option, my phone rebooted. Once it started up again, my service would not come back, and the phone would continually bootloop once it got past the traditional "media scanner running", etc. My window of opportunity to do anything was really slim.
I charged my phone to see if it made a difference, but it didn't. Tried with my SIM card removed and it still bootlooped. I was able to get to CWM from the advanced power menu before it rebooted again and I fixed permissions and cleared cache and dalvik. Now the phone wouldn't even get past the boot animation before rebooting.
I put the phone into download mode and reverted back to stock using Odin. The phone now got past the boot animation in stock mode, but was unable to find service and after about 10 seconds fell into the same bootloop pattern. I tried removing the SD card but that didn't help either. Using Odin again, I reflashed recovery, followed by root and tried reinstalling a rom through CWM (I have only used regular CWM, not the touch version) with a superwipe to ensure a clean flash. Once again, it wouldn't make it past the boot animation before bootlooping. I reverted back to stock using Odin, and this is where I stand.
I have tried all traditional methods to salvage the phone and, for the life of me, I cannot understand what happened. The only thing I notice is that regardless of how long the phone stays on before rebooting, it is never able to find service. It's like the radio or modem broke and the phone has no other choice but to restart forever. But reflashing the stock UVKL1 should also reflash the proper modem and radio, right?
Has this ever happened to anyone? Any suggestions (aside from the typical reverting to stock) as to how I might be able to stop it? I searched but haven't been able to find a situation quite like this one. Thanks in advance for your help.

Really sorry to hear about your problem. Assuming the 2.3.6 stock image you flashed via Odin is the one provided by Przekret and that that didn't work, then I'd try one or both of these two longshots to try to clear possible corruption problems in either the kernel or modem spaces:
For each of the following wipe cache and Dalvik cache in CWM before flashing and again wipe Dalvik afterwards and also fix permissions:
1) Format system (do this 3x) under mounts & storage in CWM. Flash the standalone Darkside kernel X v1 final immediately after flashing, e.g., the current Darkside rom. (You'll need to wipe data, too, if not coming from a Darkside rom. Do not do any Superwipe - neither the standalone version nor using a flag.)
2) Flash the KID modem (do this 3x). Both Odin- and CWM-flashable versions are available. (You can always flash back to KL1 if the problem is fixed.)
Hope this is clear. It's late! These are both things that have helped get my phone out of troubles, though not as bad as yours. Good luck!
Sent from my SGH-T989 using XDA App

Also if u used the one from przekret then I'm almost positive that Odin package flashes the new radio too. If memory serves me right. Op let us know what happened

Thanks for your help. Unfortunately, nothing has worked. I'm on the phone with T-Mobile, I see no other solution but to get it exchanged under warranty and it's not getting here until March 15th, according to the representative. I suppose I'll just use a replacement phone in the meantime. It's just really weird and frustrating... I could understand a bad flash or something similar, but I followed every step accurately as I always have and everything was working just fine until it randomly decided to die without warning.

Well since you're getting another one anyways I would continue trying to fix this one, just in case you come up with a solution and for another worst case scenario for your new phone.
Powered by the SGSII....

I think your efs folder got corrupted. Its scary to see this happening so often. Many other users have also reported corrupted efs ....
Sent from my SGH-T989 using XDA

shehrammajid said:
I think your efs folder got corrupted. Its scary to see this happening so often. Many other users have also reported corrupted efs ....
Sent from my SGH-T989 using XDA
Click to expand...
Click to collapse
Forgive me for asking, but what is the EFS folder?

[Q] Random Reboots

Hello,
I am new to this forum, so If this is the wrong place I do apologize.
Ive recently purchased a new ET4G and decided to root it. I had another one rooted with no problems. Ive been using a couple different roms and this random reboot has became more frequent and has followed me with each ROM.
I have tried to ODIN back to a stock ICS build with Root and then flashing ROMS over again. I still received the same problem.
I am currently using FD26 stock with the addition of root. When the reboots happen. It seems to drain my battery drastically.
Example:This morning at 50% phone reboots and I am at 9% when it comes back on. After a couple reboots it becomes stuck and only a battery pull will allow it to reboot once again.
Anytime I flash a ROM I always follow the recommended flashing method. I do all the appropriate wipes. Id usually think It was the kernel, but even after trying different kernels the issue still happened.
If anyone could shed some light on what could be happening. I would be very appreciative.

do you do complete wipes prior to flashing?

Yes, I do. I usually wipe Davlik and then will run Caulkins format all zip before I flash any Rom. I always odin back to EL26 w/ CWM to flash through to avoid any conflicts with that.
I have no idea what to try next. I've went back to stock a couple times.

This same thing was happening to me honestly about 10 reboots a day and sometimes it would drain me down about 50% battery. I odined back to stock gingerbread using sfhubs latest method, reinstalled clockwork mod and have not had one reboot since. I think I may have heard though that the fd26 build has reboot issues so I would look into that as well. Though I see that you have tried what I have said not sure if you used sfhubs method or not but if so I would just take it back to sprint.

Have you tried flashing this? http://forum.xda-developers.com/showthread.php?t=1433101
I would flash the full restore and if it keeps rebooting unroot and return to Sprint for repair. In the meantime make sure you are not using a cheapo charger and even charge via usb only if its not too much trouble.

someguyatx said:
Have you tried flashing this? http://forum.xda-developers.com/showthread.php?t=1433101
I would flash the full restore and if it keeps rebooting unroot and return to Sprint for repair. In the meantime make sure you are not using a cheapo charger and even charge via usb only if its not too much trouble.
Click to expand...
Click to collapse
+1
Seriously, if you're having problems, to narrow it down you should not be on a leaked Android OS that is still in the testing stages. Always odin back to stock rooted to troubleshoot any issues, report back and we can get go from there.
Edit: If you need help getting back to stock rooted, please ask for help too.

Thanks for all the replies guys. I didn't try flashing the EL29 Restore, But I did try the EG30 and just OTA updated to EL29. It still didn't fix the reboot issue. Even when the phone wasn't rooted, it still would still power cycle. I just went ahead and restored it again and took it to sprint.
It happened about 10times while waiting to talk to a rep in the store. They didn't have a problem setting me up with a replacement. For now I will just use my old 3D. Thanks for the help though everyone.

I'm still stock EL29 till ICS comes out, but I get a reboot every couple days. It actually happened last night about 2AM and woke me up when the Sprint sound came on. Thought maybe there was some update (ICS?) that had caused it, but i didn't see any reason for it. It wasn't charging at the time and the battery was pretty full... Was hoping ICS update was going to fix this, but it doesn't sound promising.

RaheemA said:
Thanks for all the replies guys. I didn't try flashing the EL29 Restore, But I did try the EG30 and just OTA updated to EL29. It still didn't fix the reboot issue. Even when the phone wasn't rooted, it still would still power cycle. I just went ahead and restored it again and took it to sprint.
It happened about 10times while waiting to talk to a rep in the store. They didn't have a problem setting me up with a replacement. For now I will just use my old 3D. Thanks for the help though everyone.
Click to expand...
Click to collapse
On a previous phone (Samsung Moment) I had that issue and it turned out to be a bad battery. They let me borrow a battery in the store and it went away.

Reboots are ICS related.
Sent from my SPH-D710 using Tapatalk 2

revamper said:
Reboots are ICS related.
Sent from my SPH-D710 using Tapatalk 2
Click to expand...
Click to collapse
got reboots in GB as well so I don't think its solely ICS related... IMO

Yeah... I still was hitting the problem while on Complete stock GB. The phone could have honestly had the problem prior to rooting and flashing. I didn't keep it stock long enough to know for sure haha

Probably not related, but I was having reboot problems due issues with App2SD, so i figure it is worth mentioning just in case...
Issue 25563: OS keeps rebooting when lots of apps are moved to SDcard! HUGE BUG IN ANDROID OS 2.3.5 (and higher)!

[Q] HELP! my note 2 wont boot past samsung logo!

hey, new user here, don't know if this has come up before but i did a search and haven't found anything that has the same particulars as i do.
recently my phone hasn't been responding to power button or home button wake up, intermittently. freezes up sometimes and some apps force close more than usual. then the other day, my phone died on me (full battery discharge) and when i finally got around to charging it, it charged fully but it wouldn't turn on past the Samsung boot logo, and gets real hot while doing so.
Also, the samsung boot logo appears before the AT&T splash screen tone starts.
im running stock Rooted 4.1.2 with the latest perseus kernel version.
any suggestions? i havent made a nandroid in a couple weeks, so my preferred route would be without a data wipe.
i can still access CWM recovery, btw.

well damn wheres the help?

I would download the stock rom and flash it again. If that doesnt work, custom rom time. I honestly cant see this problem getting fixed without a data wipe though good luck and keep me posted.
Sent from my X501_USA_Cricket using Tapatalk 2

With the non-response issues you describe, and the fact that you are seeing multiple force closes on the device....start with a wipe of the cache and dalvik cache in recovery.
It sounds as if the device is having cache file management issues, and trouble within the file structure.
While I dont think you have any hardware issues, it does sound like the software is suffering for one reason or another, and a base cleaning of the caches may help.
If no improvement is seen after cache cleaning, then we move to the data next.
I realize you want to keep your data intact, but if corruption has occured, you will have no choice but to factory restore the device and test again.
Try the cache cleaning first, then boot and test....
Beyond that...as the above poster states...a fresh install may be needed....g

Before a data wipe try reinstalling the kernel, and also try dirty flashing the Rom.

Not sure I would recommend a dirty flash to him. Plenty of times the result for users has been bad. Though as stated above yours, It does appear to be a file system error. He is probably right and I should have thought about wiping the dalvic cache first.
Sent from my X501_USA_Cricket using Tapatalk 2

i was afraid this would happen....
tried wiping both caches with no new results.
ive read that dirty flash has had mixed results. if i can at least get the OS booted so that i could backup what i need to, that would be a good thing.
im thinking its a kernel issue, since the phone gets real hot while stuck on the samsung screen. could i be right?
thanks guys:good:

i also tried reinstalling the kernel through cwm recovery, nothing new

FIXED
did a data/factory reset from recovery. it kept everything! thank god for cloud backups. Google is the JOINT!! i even kept my kernel and root, and at&t backed up my texts and calls....thanks everybody for the help, i really appreciate it!
its still kinna hot though...turned it off to let it cool down and see what happens when i start it back up....will keep posted if anything

Great. Know I didnt help too much but glad you got it worked out. :thumbup:
Sent from my X501_USA_Cricket using Tapatalk 2

DroidOblivion said:
did a data/factory reset from recovery.
Click to expand...
Click to collapse
Great news ....
Data corruption is so very easy to get.
As we mix and match pieces of code, those issues do arise.
Sadly, the causes are often elusive.
But the plan "B" wipe generally does the trick, as is the case here.
Happy flashing....g