Was using Corn 7.0a kernel and Legend 5 ICS ROM without any issues. Earlier I decided to try out Corn Kernel 7.06 again just to see if maybe the first time was a bad flash, because that first time my phone suffered from random system halts that required a battery pull. I really wanted the full option list of that Corn Kernel, plus that 200mhz overclock. Same problem occurred.
I then decided to try out the Glitch kernel + CM9 ROM, installed both via CWM. Phone would go to some sort of android error log/screen after the ATT bootup screen and just restart over and over.
I then decided to use the Odin One-Click stock KK4 w/o Bootloader method to get the stock GB KK4 back on the phone. It stopped after "<ID:0/006> Set PIT file.." so I hadto close Odin, reboot the phone to get to the "Firmware Upgrade Fail" screen, re-open Odin, unplug/replug the phone and try again. It worked and my phone booted up to the stock GB KK4 software with no issues.
I then tried to flash the Semaphone kernel via Odin which apparently worked according to Odin, but it did a reboot loop just like Glitch did. I tried this because CM9 users that couldn't get glitch to work ended up using Semaphone apparently.
I then tried to use the Odin One-Click stock KK4 w/o Bootloader method again to go back to stock but this time the reboot doesn't do the trick. All it says on Odin is...
Code:
<ID:0/006> Added!!
<ID:0/006> Odin v.3 engine (ID:6)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Set PIT file..
<ID:0/006> DO NOT TURN OFF TARGET!!
I then tried the Gingerbread KK4 Easy Root to Corn 7.0a Kernel method but again my phone is stuck in the infinite boot loop.
Did I do something wrong when switching kernels earlier? What could have happened to cause these infinite boot loops, and why is Corn 7.0a kernel now doing it when it worked fine before?
ETA: I eventually got the Odin One-Click w/o Bootloader method to work, enabled USB debug mode, ran the Gingerbread KK4 Easy Root to Corn 7.0a Kernel method which worked. Now re-installing Legend 5 ICS ROM, Legend 5 Stainless theme, and TouchWiz 4.0 + all my apps.
Would still like to figure out what went wrong earlier, and why I'm unable to use other kernals and roms. It's not that I dislike Corn and/or L5, I just want to be able to try out other options.
U need to use regular Odin3 v1.83 or similar (or regular heimdall [not one click].) to flash the KK4 Corn Kernel back or Stock KK4 Kernel.
Semaphore is an ics kernel...
Sent from my SAMSUNG-SGH-I777 using xda premium
4-2ndtwin said:
U need to use regular Odin3 v1.83 or similar (or regular heimdall [not one click].) to flash the KK4 Corn Kernel back or Stock KK4 Kernel.
Semaphore is an ics kernel...
Sent from my SAMSUNG-SGH-I777 using xda premium
Click to expand...
Click to collapse
I eventually got the Odin One-Click stock KK4 w/o Bootloader method to work, enabled USB debug mode, ran the Gingerbread KK4 Easy Root to Corn 7.0a Kernel method which worked. Now re-installing Legend 5 ICS ROM, Legend 5 Stainless theme, and TouchWiz 4.0 + all my apps.
Would still like to figure out what went wrong earlier, and why I'm unable to use other kernals and roms. It's not that I dislike Corn and/or L5, I just want to be able to try out other options.
If u want to flash another kk4 rom and u have corn kernel, then all u have to do is put that rom.zip on ur internal sd and install it through the cwm recovery.
If u want to try cm7, miui, or ics roms then there is a specific install procedure for that as well, that must be followed, which should be in that particular rom's op.
U just can't go flashing incompatible kernels without issues...u must always flash the kernel that is designed for the base u r on (kk4, i897, i9000, ics, cm7, miui, etc.).
Sent from my SAMSUNG-SGH-I777 using xda premium
4-2ndtwin said:
If u want to flash another kk4 rom and u have corn kernel, then all u have to do is put that rom.zip on ur internal sd and install it through the cwm recovery.
If u want to try cm7, miui, or ics roms then there is a specific install procedure for that as well, that must be followed, which should be in that particular rom's op.
U just can't go flashing incompatible kernels without issues...u must always flash the kernel that is designef for the base u r on.
Sent from my SAMSUNG-SGH-I777 using xda premium
Click to expand...
Click to collapse
That was my problem then, it seems.
This is the kernel I originally wanted to try so I could go with the CyanogenMod 9 ROM...
http://forum.xda-developers.com/showthread.php?t=1459576
And here is the thread for the ROM...
http://forum.xda-developers.com/showthread.php?t=1592141
U have to install that cm9 based rom through the corn kernel cwm recovery 1st. Then once ur running that cm9 based rom u can flash that cm9 kernel. There should be some installation instructions in that cm9 rom's op.
And flashing that cm9 from corn's cwm recovery u will probably have to flash twice. -- Once from corn's cwm and then when whatever kernel that cm9 rom is using boots up, u will then have to install the rom from that cwm.
Sent from my SAMSUNG-SGH-I777 using xda premium
4-2ndtwin said:
U have to install that cm9 based rom through the corn kernel cwm recovery 1st. Then once ur running that cm9 based rom u can flash that cm9 kernel. There should be some installation instructions in that cm9 rom's op.
And flashing that cm9 from corn's cwm recovery u will probably have to fladh twice. -- Once from corn's cwm and then when whatever kernel that cm9 rom is using boots up, u will then have to install the rom fromthat cwm.
Sent from my SAMSUNG-SGH-I777 using xda premium
Click to expand...
Click to collapse
Ah ok. I was doing the kernel and then the ROM, didn't know I had to do the ROM first.
Related
ok so heres where im at, and im scared to do anything with out some help
did super one click root
installed cwm final
then i tried to update the bootloaders following this guide
http://forum.xda-developers.com/showthread.php?t=1215748
installed kg4 kernel with odin
KG4 - http://forum.xda-developers.com/show....php?t=1183413
then got to step 11 on the guide
flashed
ODIN version:
stock+Voodoo-T959VKG4.tar
http://forum.xda-developers.com/show....php?t=1194032
then phone rebooted into a colorful static screen and keeps rebooting
i then pulled the battery then put the phone back in download mode
what did i do wrong and how to i fix it
You need the GB bootloaders. That's the rainbow screen that you get for having Froyo bootloaders on a GB ROM.
Only the GB LEAKS have bootloaders. Be sure to get the ones from KG4 and higher.
Can I just flash I froyo rom straight from odin with where I'm at? If so which rom could I use?
Sent from my HTC Desire Z using XDA Premium App
Are looking to get froyo or gingerbread. I personally recommend gb.
Sent from my SGH-T959V using xda premium
hd2brick said:
Can I just flash I froyo rom straight from odin with where I'm at? If so which rom could I use?
Sent from my HTC Desire Z using XDA Premium App
Click to expand...
Click to collapse
Yes, you should be able to. But if you're trying to get to GB, go with http://forum.xda-developers.com/showthread.php?t=1183413 which is the KG4 link you posted earlier. When you open ODIN, put:
CODE_T959VUVKG4_CL385158_REV00_user_low_noship.tar.md5 into PDA
Hawk_Sidekick_VibrantPlus_831.pit into PIT
SGH-T959V-CSC-TMB-VIBRANTP.tar.md5 into CSC
t959vuvkg4-Phone-CL1037720.tar.md5 into PHONE
Leave the checkboxes alone; ODIN will check the correct ones. That should get you to a base GB build with the right bootloaders. From there you should be able to update to the latest GB ROM.
I've done this twice but tried to flash an updated kernal via odin and the result ends in a brick. I'm running Octane v2 and was flashing the KJ3 version. I can't remember what I was running before, but did the same thing as well. What gives?
Hard to say without more detail. You said you were trying to flash a kernel on top of Octane but, to my knowledge, no one has put a KJ3 kernel out there. You may be flashing a new ROM vs a kernel.
If you are trying to flash a new ROM (KJ3 in this case) to replace Octane, then you need to insure you don't have voodoo enabled when flashing a stock ROM as stock ROMs cannot read the ext4 filesystem.
If you've already flashed a stock KJ3 ROM, download drhonk's KJ1 kernel with root/cwm/voodoo, flash it via ODIN, let the phone boot, reboot into recovery, disable all voodoo, reboot the phone, then you should be in a good place to flash whatever GB ROM you want.
I meant KJ1 kernel. I already had octane flashed but flashing the kernel via Odin, it bricks. I don't want to flash thru cwm for fear of the same
Sent from my SGH-T959V using xda premium
Interesting. When you say it bricks, what exactly happens?
stephen_w said:
Interesting. When you say it bricks, what exactly happens?
Click to expand...
Click to collapse
I get no response from the screen, power button, or touch keys. It wont even respond to my JIG. It'll respond to the pc when I have odin open to let me know it's connected, but other than that, almost like a dead rock. When I odin it, It will flash with just the blue status bar.
If you're using Odin, could it be that you're flashing the kernel in the wrong slot?
It could also be a bad download.
I just flashed Octane v2.X two days ago, and I flashed the KI3 kernel through CWM. Everything worked fine for me.
bkoon1218 said:
If you're using Odin, could it be that you're flashing the kernel in the wrong slot?
It could also be a bad download.
I just flashed Octane v2.X two days ago, and I flashed the KI3 kernel through CWM. Everything worked fine for me.
Click to expand...
Click to collapse
Its supposed to go into the pda slot right?
Sent from my SGH-T959V using xda premium
Yes, it goes into PDA. As suggested it might be a bad download.
Sent from my SGH-T959V using XDA App
Ok so I flashed the Charge pit file, in imnuts thread, along with the EP4 rooted, deodexed leak. Everthing flashed successfully in Odin. Now when I reboot the phone it boots into the stock blue recovery and says "lfs done open fail" And under that it says "# MANUAL MODE #"
I have tried reflashing this way several times with no luck, anyone have any ideas? Should I try flashing the EE4 stock file? or the stock ep4 file? I was on gummycharged 2.1 before this, with imoseyons latest froyo voodoo kernel.
blown14psi said:
Ok so I flashed the Charge pit file, in imnuts thread, along with the EP4 rooted, deodexed leak. Everthing flashed successfully in Odin. Now when I reboot the phone it boots into the stock blue recovery and says "lfs done open fail" And under that it says "# MANUAL MODE #"
I have tried reflashing this way several times with no luck, anyone have any ideas? Should I try flashing the EE4 stock file? or the stock ep4 file? I was on gummycharged 2.1 before this, with imoseyons latest froyo voodoo kernel.
Click to expand...
Click to collapse
I see several glaring errors here that are most likely the culprits: first I'm gonna assume it was a typo and you meant latest GB voodoo kernel with Gummy 2.1, second more serious error is using the PIT file with EP4P... this is a bad idea, only use that with Froyo stock roms!!
I would suggest Odining back to EE4 with the PIT for a clean slate then Odin the EP4P rom of your choice by itself and you'll have no problems after that
blazing through on my 4G Droid Charge
I went back to ee4 and it worked. Thanks.
I believe flashing a new kernel like imoysen before first boot would stop the stock recovery from overwriting cwm
I assumed that the pit would work on any stock rom? I flashed it with the ep4 leak. Initially I tried to disable lag fix by creating a "disable_lagfix" file in the voodoo folder but I couldn't get it to work. It kept stalling at the samsung boot screen. Then I flashed the pit with the leak, still no go. It worked fine after going back to ee4, then flashing ep4.
I thought the ep4 rom included a new kernel?
Sent from my SCH-I510 using XDA App
blown14psi said:
I assumed that the pit would work on any stock rom? I flashed it with the ep4 leak. Initially I tried to disable lag fix by creating a "disable_lagfix" file in the voodoo folder but I couldn't get it to work. It kept stalling at the samsung boot screen. Then I flashed the pit with the leak, still no go. It worked fine after going back to ee4, then flashing ep4.
I thought the ep4 rom included a new kernel?
Sent from my SCH-I510 using XDA App
Click to expand...
Click to collapse
The PIT file we have stopped working with EP3. If you need to use it, use it with EE4, then flash EP4 without it.
Bump for two reasons
1. You will most likely see this if playing with ICS, since you go to an EXT4 FS. Going back for some reason is buggy right now.
2. USE THE FACTORY CABLE.
Shadowchasr said:
1. You will most likely see this if playing with ICS, since you go to an EXT4 FS. Going back for some reason is buggy right now.
2. USE THE FACTORY CABLE.
Click to expand...
Click to collapse
Holy dead thread batman!
Sent from my SCH-I510 using xda premium
I was running Infused 2.2.3 for the longest time and when I always went into recovery it was red.
Well, I was switching roms and got a hiccup in the install and had to revert back to stock using odin and gtg unbrick.
Once I was back to stock froyo, I rooted, replaced the recovery.bin file with the no sig file and then went into rom manager and got cwm, rebooted, reinstalled packages, etc...
Well I have cwm, but when I get into it, its green lettering...not red.
Only reason I ask is because just about everywhere I see, they say get into red.
Any ideas on how I can get red installed?
thanks
joho5 said:
I was running Infused 2.2.3 for the longest time and when I always went into recovery it was red.
Well, I was switching roms and got a hiccup in the install and had to revert back to stock using odin and gtg unbrick.
Once I was back to stock froyo, I rooted, replaced the recovery.bin file with the no sig file and then went into rom manager and got cwm, rebooted, reinstalled packages, etc...
Well I have cwm, but when I get into it, its green lettering...not red.
Only reason I ask is because just about everywhere I see, they say get into red.
Any ideas on how I can get red installed?
thanks
Click to expand...
Click to collapse
When in cwm, choose to install zip from SD card and go all the way to bottom and select "update.zip" and if it doesn't reboot, select reboot now and it should boot into Red CWM. That might do it i think
Froggys go ribbet
joho5 said:
I was running Infused 2.2.3 for the longest time and when I always went into recovery it was red.
Well, I was switching roms and got a hiccup in the install and had to revert back to stock using odin and gtg unbrick.
Once I was back to stock froyo, I rooted, replaced the recovery.bin file with the no sig file and then went into rom manager and got cwm, rebooted, reinstalled packages, etc...
Well I have cwm, but when I get into it, its green lettering...not red.
Only reason I ask is because just about everywhere I see, they say get into red.
Any ideas on how I can get red installed?
thanks
Click to expand...
Click to collapse
Flash Entropy's daily driver kernel. You'll get red CWM and voodoo lagfix. Great kernel by the way.
Sent from my SAMSUNG-SGH-I997 using xda premium
Kevinr678 said:
Flash Entropy's daily driver kernel. You'll get red CWM and voodoo lagfix. Great kernel by the way.
Sent from my SAMSUNG-SGH-I997 using xda premium
Click to expand...
Click to collapse
thanks, I will prob have a rom with a stock kernel...if thats the case, can I flash entropys kernel (which is my choice one on custom roms) through odin in the pda slot?
thanks for the help.
I will only want to flash a custom kernel to get root, then back to stock because the rom I will be running is based on one of the newer leaks, and I want video.
joho5 said:
thanks, I will prob have a rom with a stock kernel...if thats the case, can I flash entropys kernel (which is my choice one on custom roms) through odin in the pda slot?
thanks for the help.
I will only want to flash a custom kernel to get root, then back to stock because the rom I will be running is based on one of the newer leaks, and I want video.
Click to expand...
Click to collapse
Well you need to have a kernel with voodoo enabled like Entropy's or you can't get red cwm. The stock leaks HAVE to have a stock kernel for video to work however. Oh, and yes you can. You can do that or through SGS Kernel Flasher on the market. What do you need red for anyway?
Don't forget, if I helped you, hit thanks please
Sent from my SAMSUNG-SGH-I997 using xda premium
Hi,
Just wanted to sell my SGS 4g and flash it with valhalla 3.5 firmware.
I just flashed Teamacid 4.0.4 firmware and it worked nice for several days.
Then I wanted to flash KG4 via Odin, But it gave me some error after the flash in the yellow text base screen.Can't access to /system/csc/TMB/system/, But it managed to flash the rom.
I read in google it has something to do with the bootloader.
I tried afterward to flash KJ1 via ODIN, But although ODIN was successful - it didn't updated the rom to KJ1.
I needed to root the phone, So I used the zimage+root then the zimage patch with the red piranha fish and it got the phone rooted.
For some reason I couldn't flash the valhalla 3.5 rom to the machine. It said it was sucessful, but it didn't changed to valhalla after reboot.
I did managed to flash CM7.2, But I wanted the valhalla......
is it possible that the teamacid 4.0.4 rom changed some file/bootloader in a way I couldn't go back to 2.3.4 flawlessly ?
Do a Heimdall One-Click to KJ6. When the CSC error comes up, ignore it. It flashed fine. That warning is always present. Then do what you wish (install valhalla, etc.).
m4xm4n said:
Do a Heimdall One-Click to KJ6. When the CSC error comes up, ignore it. It flashed fine. That warning is always present. Then do what you wish (install valhalla, etc.).
Click to expand...
Click to collapse
Thanks Max,
Fish, that's just what I wrote you on iandroid - search for lumin30's sticky on One Click Heimdall.
Sent from my SGH-T959V using xda premium
itzik2sh said:
Thanks Max,
Fish, that's just what I wrote you on iandroid - search for lumin30's sticky on One Click Heimdall.
Sent from my SGH-T959V using xda premium
Click to expand...
Click to collapse
Thank you m4x and itzik.
I will do as you both suggested, and hopefully could flash the wanted rom in the end.