Description of problem: I had the Bionix 1.3 w/voodoo lagfix and OC kernel and then wanted to try the KIES v15 but it KEIS wouldn't recognize the kernel I assumed. I tried to revert to v14 through ODIN and everything went fine until it rebooted. Now it just gets stuck at the black screen after the boot animation.
I can boot into both recovery and download mode and have tried several other ODIN ROMS to see if one of those would work, but no go. Any ideas from anyone?
edit: Just tried doing the True Stock update to put it back to factory spec and same problem, still black screen after boot. The only way you even know that the phone is on is if you touch on of the soft buttons they will light up, just not do anything.
You need to install Froyo ~~~That does not Brick! Downgrading Is Fine first and then install whatever ROM you want after that.
Also, there is no such thing as v14 or v15 there is JI4 and JI5 (that's the letter "I" not a number "1"). Just FYI.
even though at the topin bold it says "Caution!!! You Must be on STOCK Vibrant Rom & NEVER Have Already Flashed the JP3 Froyo Image"?
Remember I had Bionix 1.3
Edit: No go, now I'm at the international Recovery Screen and can't go any further. The volume buttons are reversed and the power button doesn't select anything. The menu key does something, but I can't figure that out yet.
Bionix isn't Froyo, and neither is JI5, so flashing Eugene's Froyo through Odin should work... You might want to click "Re-Partition" when using Odin that might help.
Well, thanks anyway. What I did next was go back to the True Stock update after the Eugene Froyo you mentioned and it booted up just like normal. Thanks for pointing me in the right direction!
i had eugene373's vibrant9 installed running with JAC's OC and voodoo lagfix...
and i was having small issues with my phone freezing ( i was guessing it was cuz maybe my vibrant cant handle the OC) so i was just gonna go back to stock, well i brought up Odin and was gonna flash back to stock and put in the PIT and the PDA... but then it got stuck on the Zimage.. so i tried again and got stuck again... so i turned off my laptop and debatteried my phone and it still did it, so i tried to just go back to vibrant9 without overclock and now it gets stuck on cache.rfs
whats going on? what do i need to do?
EDIT: and it seems like everytime i mess my phone up thru ODIN, i always have to flash to "oc120_voodoo_b4.2" kernal and then it works again.. but i dont want to do it and mess up my phone.. cuz i dont know what problem is
It sounds like you didn't disable Voodoo before flashing the new Kernel...
To fix this you need to flash Eugene's FroYo that doesn't brick. Then flash stock JI6 with the "Repartition" box in Odin checked.
There's a more involved walkthrough if you use the "Search" feature. This thread is your friend.
Was originally typing this in the Nero thread but didnt wana add clutter..
Ok, so I've been running Nero with voodoo enabled for a little over a week with no issue. ROM was smooth and battery life was solid. Then yesterday for the sake of a little more battery life I disabled voodoo and flashed the Super IO kernel to see how it would be in this ROM. Everything was fine for a while but then they phone would freeze everytime I ran GPS Test Plus. Only thing it would respond to was hitting the power button to put it to sleep and from that it would not wake (sleep of death). I proceeded to pull the battery. Immediately after the phone fully booted I began getting endless force closes from what seemed like every single all on the phone. Pretty sure this was kernel panic yes?
So I reflashed the JL5 Voodoo kernel (posted in the Nero OP) thinking that would fix it. the force close storm stopped but the phone was still acting up freezing and still wouldnt wake from sleep. I decided then backup, factory reset, wipe cach and dalvik cache, and reflash Nero. I thought all was well but to my surprise after being on the charger all night I arrive to work to find that my battery was at 74% O_O. This is shocking due to the fact that the phone had only been off the charger for about 45 minutes and had not been used AT ALL during that time.
So my question is... Did I just have a bad flash or did flashing the Super IO kernel do some unseen damage? Checked the battery info in Spare Parts and nothing looked out of order.
I would recommend, going back to stock and reflashing nero 3 and retrying the Super IO kernel. Hope that fixes the problem.
Will do when I get home. I assume this will unroot me, right?
I remember a post from Eugene on his site that the super io kernel works best when it is flashed with a rom before that rom is booted for the first time. If you're going back to the super io kernel, you should flash your rom, then flash the kernel before your first boot. It was something about how the kernel syncs with the rom, flashing it as an after thought can cause issues.
Ginger Clone's of the World Unite! Via the XDA App
Thats weird because I flashed super io over R14 when he first released it and had no problem -_-
Same thing happens to me when i touch Eugenes work. Thought I was the only one
Sent from my SGH-T959 using XDA App
Br1cK'd said:
I remember a post from Eugene on his site that the super io kernel works best when it is flashed with a rom before that rom is booted for the first time. If you're going back to the super io kernel, you should flash your rom, then flash the kernel before your first boot. It was something about how the kernel syncs with the rom, flashing it as an after thought can cause issues.
Ginger Clone's of the World Unite! Via the XDA App
Click to expand...
Click to collapse
regP said:
Thats weird because I flashed super io over R14 when he first released it and had no problem -_-
Click to expand...
Click to collapse
I was only successful with Super IO when I flashed it after a clean rom install. It sucks, but........
This is interesting, I experienced the same type of battery loss upon flashing Nero V3 for the first time. But, I did not flash eugenes super io kernel. I just stuck with the JL5. Although, Once I did a good recondition on my battery, Things seem to be much better. I'm a stickler when it comes to battery life though lol. Whens the last time you reconditioned the battery and wiped the stats via recovery?
I wipe the stats after every flash. I don't recondition unless the battery meter is trippin because I use 3 different batteries. 2 of which are knockoffs but they last about the same as the original. I factory reset, wiped caches again and then flashed the latest Axura. To my surprise after flashes and restoring data I booted into recovery to find the jl5 voodoo kernel was still there.. so I flashed Eugene's eb-productions stock kernel and everything seems to be fine.
What happened with the fc storm WAS kernel panic right?
I spoke too soon. Battery is still draining like a mofo and now I know why. Checked spare parts battery history and it reports that the phone wont go to sleep. Ill have to try to Odin back to stock when I get home
I have a few questions though because I've never done this before.
1. I downloaded Eugene_E2_JK2 from the Bible. Is that one fine or should I flash back to a stock 2.1 ROM
?
2. Will this process unroot my phone?
3. How is flashing the stock rom with odin any different than doing a factory reset and flashing with clockwork? I'm just worried that since flashing in clockwork didn't work odin wont either.
Vibrant via XDA App
So I odin back to JK2 then flashed a fresh installation of the latest Axura. Everything went fine as far as the flashing but after first boot I went back into recovery and i think the voodoo kernel from nero was active because I had the red letters and an option to enable voodoo O_O. WTF? I disabled voodoo before i did odin. I'm pretty sure Axura doesnt come with the voodoo kernel so how it was there after i came from stock is beyond me. So I flashed the EB-Productions stock kernel which i have used on Macnut and Axura and gotten great battery life before going to Nero. The battery still seems to be draining faster. Spare Parts reports that the "time spend without sleep" is about 10 minutes less than the phones boot time. I havent touched the phone since it booted so i dont see how thats possible.
I have no idea whats going on... Any help would be greatly appreciated. Im about ready to pull my hair out..
Just ODIN back to shipping rom (remember to use pit file and check repartition) It is better to do that everytime you are changing roms with kernel......
What difference would odin to stock 2.1 make over stock 2.2..?
regP said:
What difference would odin to stock 2.1 make over stock 2.2..?
Click to expand...
Click to collapse
The stock 2.1 is the official t-mobile software as it came from the factory. Any 2.2 we have is leaked, there is no official 2.2 for us yet. Although the 2.2 you said you flashed is as close as we got to a stock froyo rom. Flashing one of the two should get you back to stock, but the 2.1 is accepted the official base by many to start from, square one so to speak. After flashing stock, before any other roms are applied, you shouldn't have the red voodoo cwm anymore.
If you do still have voodoo after flashing stock, search for Eugene's Froyo that doesn't Brick. Flash through odin with the 512 pit file, you will reboot to a recovery that doesn't work, pull your battery, set up odin with either stock 2.1 or leaked 2.2 and the pit file, boot back to download mode, and flash the stock rom, being sure this time to select the repartition check box in odin. This will remove voodoo, and is the fix for times when voodoo goes bad. After this you will be as stock as you can get, and if you need a link to the froyo that doesn't brick, let me know I'll post it.
Ginger Clone's of the World Unite! Via the XDA App
What's the difference between reconditioning and just wipeing the stats. I've wiped it through clockwork before however what's reconditioning?
Sent from my SGH-T959 using XDA App
Reconditioning is charging your battery fully then letting it run down until the phone turns off then charging it back up again. The purpose is to make the battery reading more accurate if it seems to be inaccurate.
In other news... I odin back to stock 2.2 AGAIN then reloaded Axura. All is well now. Still bugs me though that voodoo was still there after the first odin. Just dont see how that was even possible.
Thanks for all the help!
The latest axura rom comes with the voodoo kernel, so if you flashed it, you will have, or should have, voodoo recovery. That was my point about checking recovery after flashing stock to verify it was removed, if that was what you were trying to do.
Ginger Clone's of the World Unite! Via the XDA App
Sorry for the newbie question but I have searched all over the internet and can't find a solution. I am running superclean 2.9.2 novoodo odin package from android central with jt's CWM all and i am tring to load imnuts 50mv or 100mv UV nonvoodo kernel. I load the zip files through red CWM and when i reboot i'm stuck on the samsung logo then it reboots. It continued to do this for 30 minutes before i pulled the battery and reloaded the superclean 2.9.2 odin files then i loaded jt's CWM all. The phone is now operational but i can not load any kernels through CWM. Is it possible these UV kernels are not compatible with superclaen or am doing something wrong? This is the first time i have tried to laod a zip file through CWM so I may be missing something. Thanks for the help in advance.
I tried loading imnuts SV nonvoodoo and voodoo kernels and got stuck at the Samsung logo as well. Times_Infinity's worked for me though. But BLN doesn't actually blink anymore, using Blinky.
iMissLayups said:
I tried loading imnuts SV nonvoodoo and voodoo kernels and got stuck at the Samsung logo as well. Times_Infinity's worked for me though. But BLN doesn't actually blink anymore, using Blinky.
Click to expand...
Click to collapse
Thanks for the response. Are you using the nonvoodo kerenl? If so have you noticed any improvement in battery life and are there any down side of using the kernel?
I too could not get any of the non-Voodoo kernels to boot past the Samsung logo, but the 100 Voodoo did just fine. If you don't want to use Voodoo (which I didn't either), just go into the Voodoo menu IMMEDIATELY after installing the kernel (as in don't reboot - when the CWM menu returns, go into the Voodoo menu) and disable the lagfix. Nothing will be converted and you'll essentially be on a non-Voodoo kernel.
So far, battery life hasn't been stellar, but I've only been on that kernel for a day, and spent a decent amount of time on the phone, connected through Bluetooth to my car, so that was probably a fairly significant drain on the battery.
hi all,
hope someone can help with this.. i have some sort of CWM bug that is messing up the entire flashing system for me.
ill try not to be too long winded.
was on MIUI 1.10.14 with JT "stock" kernel and all was fine..although this had the "no boot to recovery" issue, so i couldnt get to CWM by the menu. i decided to try glitch kernel again. so on tuesday i downloaded glitch V12 ML from the thread and flashed it by using ROM MANAGER and selected "install from sd card" ..i noticed immediately that something was sketchy, since when it booted to CWM via RM, i got version 4.1.xxx ? not 5.0.xxx like glitch is supposed to show.. i flashed anyway and it flashed and everything peachy. figured rom manager knew what it was doing..
so today rolls around..and since RickS put out the fixed MIUI 1.10.21 i again used Rom manager to get to recovery, and now its a totally diffrerent color 4.0.xx something.. i figured "it'll work like last time" .. uhhh no..
boot loop hell..
so i come home and ODIN it back to ED05, and install the CWM 4.0 Fixed for CM7.tar that i have used before...so now, i go to flash and at the splash screen on boot (no matter what i flash, ive tried older miui, and CM7.1) at the kernel splash screen it will hang for a second, flip over to what looks like a CWM script running very quickly (have seen blue and yellow so far for colors) then will go to boot screen and boot loop on either the blue CM logo (if CM7.1) or on the MIUI "globe"..
what the heck did i do and how do i fix it? i have ODIN'd back to EDO5 and it still will not rid it of the "problem"
Ideas?
mrjake1970 said:
hi all,
hope someone can help with this.. i have some sort of CWM bug that is messing up the entire flashing system for me.
ill try not to be too long winded.
was on MIUI 1.10.14 with JT "stock" kernel and all was fine..although this had the "no boot to recovery" issue, so i couldnt get to CWM by the menu. i decided to try glitch kernel again. so on tuesday i downloaded glitch V12 ML from the thread and flashed it by using ROM MANAGER and selected "install from sd card" ..i noticed immediately that something was sketchy, since when it booted to CWM via RM, i got version 4.1.xxx ? not 5.0.xxx like glitch is supposed to show.. i flashed anyway and it flashed and everything peachy. figured rom manager knew what it was doing..
so today rolls around..and since RickS put out the fixed MIUI 1.10.21 i again used Rom manager to get to recovery, and now its a totally diffrerent color 4.0.xx something.. i figured "it'll work like last time" .. uhhh no..
boot loop hell..
so i come home and ODIN it back to ED05, and install the CWM 4.0 Fixed for CM7.tar that i have used before...so now, i go to flash and at the splash screen on boot (no matter what i flash, ive tried older miui, and CM7.1) at the kernel splash screen it will hang for a second, flip over to what looks like a CWM script running very quickly (have seen blue and yellow so far for colors) then will go to boot screen and boot loop on either the blue CM logo (if CM7.1) or on the MIUI "globe"..
what the heck did i do and how do i fix it? i have ODIN'd back to EDO5 and it still will not rid it of the "problem"
Ideas?
Click to expand...
Click to collapse
odin back to dl09 eclair, that should fix it. I had the same problem. You can find the files in my guide.
+1
your solution worked and got rid of the mess... thanks!