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] Q for Devs: Wiping 3x, flashing, and Odin

Can any of the devs give a technical explanation on why this is necessary?
I am coming from the Sprint Hero phone and it seems like that phone went through a similar phase early on.
Originally, wiping and flashing a ROM seemed to be somewhat hit or miss and sometimes wiping mulitiple times and then flashing twice before starting the ROM the first time seemed to get it through a rough spot.
Now with the Epic, when switching one ROM family to another, the devs are typically saying that an ODIN is needed to get on that ROM family, then normal wiping and flashing from CWM works as expected as long as you stay within that ROM family.
SOOOO.. my question is... Why is that? Is CWM still too green on this phone to properly clear everything that is needed? Does a flash not write to every memory address that is needed?
No griping on my part, just honest curiosity both for why it happens, what if anything is being done, and how it is even diagnosed.

<Bump> Please? I'm not asking to be smart. I'm asking to get smart. Educate me and hopefully others on the issues you are encountering. It would be interesting to hear.

Odin is only necessary to flash Modems when switching roms with different android versions (EC05 for Froyo, EF02 for Gingerbread etc.).
The reason for this is differences in how Samsung handles their Modem files vs other devices.

Wiping cache and dalvik is important because, when flashing a rom over another rom that's installed. The data from the previous installation tends to linger, which could cause some major issues. May even brick your device. Think of it as a bad kidney transplant. Incompatibility could brick your life. You figga dill me?
Sent from my SPH-D700 using XDA Premium App

And the reason for the 3X wipe was because the ported Clockwork Mod was not perfect and did not clean everything the first time. I believe that has been fixed in the newer version so that once is sufficient.
Sent from my SPH-D700 using XDA App

Can this be ported? Wipe 5x script

http://forum.xda-developers.com/showthread.php?p=23983384
Could this script be ported over? I'm not a dev by any means but I'd like this.
Sent from my Galaxy Nexus using XDA

It's not your butt. Wiping more than once doesn't do anything. Though, if someone can get me proof of a repeatable error that is only solved by wiping more than once before installing a ROM, I'll admit I'm wrong. As of right now, it's voodoo quackery from the people that insisted battery cache wiping was the sure way to double your battery life.
To clarify, this is distinct from wiping, flashing the ROM, and wiping again and re flashing the same ROM. Bad flashes seem to happen to me 10% of the time.

Just seems useful I personally wipe 2-3 times before a flash just to be safe. I've had bad flashes before I did haven't since.
Sent from my Galaxy Nexus using XDA

....
There is no possible thing that would change from wiping it once to wiping it 1000 times. A wipe wipes the data. Then it's gone. Wiping it again just wipes nothing. Remnants don't get left behind or anything. Have you ever tried deleting something twice? Same concept....
Peter

Its the same concept of a bad flash. You flash and have problems, yet re-wipe and flash again and it works fine. Sometimes when you do a wipe, for some reason or another every file doesnt get wiped. Its rare but it does happen. Wiping twice before flashing or just a safer practice. Sure if the file gets deleted, it cant be deleted again. But the issue at hand is that the file doesnt always get deleted. I used to sometimes have a bad flash with a ROM but ever since I started flashing twice before I install the ROM I havent had an issue. I dont think we get a bad flash because the ROM flashed bad, we get a bad flash cause files didnt get wiped and are left over from the old stuff.

EniGmA1987 said:
Its the same concept of a bad flash. You flash and have problems, yet re-wipe and flash again and it works fine. Sometimes when you do a wipe, for some reason or another every file doesnt get wiped. Its rare but it does happen. Wiping twice before flashing or just a safer practice. Sure if the file gets deleted, it cant be deleted again. But the issue at hand is that the file doesnt always get deleted. I used to sometimes have a bad flash with a ROM but ever since I started flashing twice before I install the ROM I havent had an issue. I dont think we get a bad flash because the ROM flashed bad, we get a bad flash cause files didnt get wiped and are left over from the old stuff.
Click to expand...
Click to collapse
Can you quantify this in any manner at all? Have you checked the partition to see what was left behind the first time and not the second? What was the file?

Out of curiosity, someone with a bit more android storage knowledge than me might be able to answer. Does wiping on android just 'uncatalogued' as most computer systems do and allow it to be written over, or is it an actually 'replace with 0'? Just kinda curious for my own knowledge.

My phone randomly freezes, and then thinks the battery completely drained...

My phone seems to freeze randomly when I'm using it and when I try to reboot it, it says the battery is completely drained even when it clearly isn't. I then have to boot it up plugged it in to a charger then it'll either charge quickly starting from 0% or it'll jump right back to the percentage it was at when it froze.
This started happening when I flashed from cm9 alpha 6 the cm10 ROM. I thought that the freezing was just caused from the ROM, so I put cm9 back on it, and it continued to do this. I flashed the beta 1 version hoping that would fix it, but the freezing still occurs. Has anyone else experienced something similar to this? Could it be caused by the kernel or modem that I have installed on my phone?

freeze issue
htb723 said:
My phone seems to freeze randomly when I'm using it and when I try to reboot it, it says the battery is completely drained even when it clearly isn't. I then have to boot it up plugged it in to a charger then it'll either charge quickly starting from 0% or it'll jump right back to the percentage it was at when it froze.
This started happening when I flashed from cm9 alpha 6 the cm10 ROM. I thought that the freezing was just caused from the ROM, so I put cm9 back on it, and it continued to do this. I flashed the beta 1 version hoping that would fix it, but the freezing still occurs. Has anyone else experienced something similar to this? Could it be caused by the kernel or modem that I have installed on my phone?
Click to expand...
Click to collapse
Did you do a clean install? I.e. factory reset/wipe all or agats format all then wipe d catche and catche. Then flash cm10 then gaps? Are you using op gaps?

emottau said:
Did you do a clean install? I.e. factory reset/wipe all or agats format all then wipe d catche and catche. Then flash cm10 then gaps? Are you using op gaps?
Click to expand...
Click to collapse
Yes, clean install. Didn't use agats format all though. Wiped both cache. Then flashed the ROM then gapps. Yes, I'm using the op gapps. The ICS ones didn't cause any issues before my phone started freezing up on me.
I'm not running any tweaks or mods. I just load up the ROM for the first time after a fresh install, and it freezes right away.

Just a cache wipe would certainly leave lots behind.
sent from my BAD A$$ Epic touch

That's the ics power save mode, while phones frozen you don't use any battery. Now that's genius .
Pp. .....LoL.
Sent from my ginger infused Mayan calculator.

Odin back to el26 and then flash CM10 with an unlocked recovery. Just make sure to fully wipe when switching roms
Sent from my SPH-D710 using XDA

patrao_n said:
Just a cache wipe would certainly leave lots behind.
sent from my BAD A$$ Epic touch
Click to expand...
Click to collapse
I formatted /data as well...Is this not enough? Is there a more proper way to wipe the phone?
J_Whit85 said:
Odin back to el26 and then flash CM10 with an unlocked recovery. Just make sure to fully wipe when switching roms
Sent from my SPH-D710 using XDA
Click to expand...
Click to collapse
Does a full wipe consist of more than formatting data, cache and d cache?
I've used calk's format all and it is still freezing up on me.

htb723 said:
My phone seems to freeze randomly when I'm using it and when I try to reboot it, it says the battery is completely drained even when it clearly isn't. I then have to boot it up plugged it in to a charger then it'll either charge quickly starting from 0% or it'll jump right back to the percentage it was at when it froze.
This started happening when I flashed from cm9 alpha 6 the cm10 ROM. I thought that the freezing was just caused from the ROM, so I put cm9 back on it, and it continued to do this. I flashed the beta 1 version hoping that would fix it, but the freezing still occurs. Has anyone else experienced something similar to this? Could it be caused by the kernel or modem that I have installed on my phone?
Click to expand...
Click to collapse
Hi htb,
I replied to your post in the CM10 thread with the following:
I had the exact same issue and it happened about the time I tried a new ROM. For me it was a bad battery. It was physically swollen and obviously bad. My nearest Sprint store have me a new one free.
If you're able, ODIN back to stock and take it in.
If not, a new battery is about $12 on Amazon.
Take out your battery and set in on a flat table. If it's bulged out at all, it's probably bad. It shouldn't spin like a top.
What you're describing is the exact same problem I had. I've tried two other batteries now and the problem seem fixed. No issues with ICS whatsoever. Good Luck!

MoMatt said:
Hi htb,
I replied to your post in the CM10 thread with the following:
I had the exact same issue and it happened about the time I tried a new ROM. For me it was a bad battery. It was physically swollen and obviously bad. My nearest Sprint store have me a new one free.
If you're able, ODIN back to stock and take it in.
If not, a new battery is about $12 on Amazon.
Take out your battery and set in on a flat table. If it's bulged out at all, it's probably bad. It shouldn't spin like a top.
What you're describing is the exact same problem I had. I've tried two other batteries now and the problem seem fixed. No issues with ICS whatsoever. Good Luck!
Click to expand...
Click to collapse
This was going to be my next step. I've got to complete stock and back, and I still get the freezing. Thanks for the advice, I'll definitely do that today. Hopefully this is the cause, because I don't know what else it could be.

htb723 said:
I formatted /data as well...Is this not enough? Is there a more proper way to wipe the phone?
Does a full wipe consist of more than formatting data, cache and d cache?
I've used calk's format all and it is still freezing up on me.
Click to expand...
Click to collapse
Wipe it manual through the recovery then flash calks format all then there is no question if it got wiped or not
Sent from my SPH-D710 using XDA

Sorry I only saw you said you wiped cache. Yes the battery is bad from my understanding.
sent from my BAD A$$ Epic touch

[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