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
Related
Initially, I was going to just have a post for stock ED2, but I got a request for an ED1 update.zip as well, so this will be for CWM package for Stock ROMs, and I'll try to keep it up-to-date. These packages are fully stock, bloated, and Odexed.
Currently, we only have two system releases available (officially) and both are available here. As more updates come out, I'll update this post as I have time to create the package for said updates. If someone else can create it before I do, then I'll just edit the post and link to the download, giving the creator proper credit.
NOTE: The ED2 was packaged with the kernel from ED1, so flashing this may not necessarily restore OTA update functionality. Also, flashing any of these packages does not guarantee OTA functionality. The ED2 package should now have the ED2 stock kernel in with it
WARNING: If you are currently on a Voodoo Lagfix kernel and are running with the lagfix enabled, you will need to disable the lagfix fully before flashing any stock ROM package. Failure to do so will result in a non-booting phone and could also potentially lead to data corruption.
Installation
1. Download the zip file and place it on your SDCard.
2. Boot into CWM Recovery
3. Install ZIP that you downloaded.
4. Reboot and enjoy your bloated goodness.
Download - ED1
Download - ED2
Download - EE4
has anyone tried to get root shell with recovery on a stock unrooted device?
Thanks imnuts, I appreciate the work. One question, about OTA, if for some reason it doesn't restore OTA abilities, can we manually request an OTA or would it be gone completely.
For me stock is something I will do between ROM's or for repair purposes. Once the custom ROMS get a bit further along I will be on several. I need to collect all of my notes on what to do when and how so I don't mess up my phone, again.
Good to know that CWM will now allow us to disable Voodoo and restore FTW.
RaptorMD said:
Thanks imnuts, I appreciate the work. One question, about OTA, if for some reason it doesn't restore OTA abilities, can we manually request an OTA or would it be gone completely.
Click to expand...
Click to collapse
If needed, we can probably hack together a zip file that can be flashed in CWM to do incremental updates to various system files to return full OTA update-ability. If we ever get a full Odin image, that would also work.
Also, updated the title and OP. I'll just use this to post stock ROM zip files meant for flashing in CWM. Currently have ED1 and ED2 in the first post, will add more as we get updates.
This is great, now we can reboot into recovery, disable voodoo, use one of the two update.zip files and then use Odin to reflash the root/kernel/cwm package. Great work.
Will this effect clockwork
Sent from my SCH-I510 using XDA Premium App
papi92 said:
Will this effect clockwork
Sent from my SCH-I510 using XDA Premium App
Click to expand...
Click to collapse
Yes. No more CWM after flashing these. You will be back on stock kernel/recovery.
Hopefully no one tried to flash either of these. There was an error in the updater-script that I just fixed, so if you downloaded the files "just in case" before this post, delete and redownload.
Ed2 worked for me lol
Sent from my SCH-I510 using XDA Premium App
I flashed ed2 yesterday at 12am et and have had no problems
Sent from my SCH-I510 using XDA Premium App
papi92 said:
I flashed ed2 yesterday at 12am et and have had no problems
Sent from my SCH-I510 using XDA Premium App
Click to expand...
Click to collapse
Odd. I would still re-download just to be safe though.
Will do
Sent from my SCH-I510 using XDA Premium App
Thanks imnuts, I will redownload when I get to the office on Monday (faster connection).
Can I rename this to update.zip if I can't get past the stock recovery screen and do an update zip command line from stock recovery?
brabe1979 said:
Can I rename this to update.zip if I can't get past the stock recovery screen and do an update zip command line from stock recovery?
Click to expand...
Click to collapse
No, these packages have no signature, so stock recovery will not flash them.
Imnuts, are these rooted? or will you lose root by flashing?
Can some one help me how do i root my charge i see the one click but thats 4 ed1my phone say ed2
Sent from my SCH-I510 using XDA App
hoppermi said:
Imnuts, are these rooted? or will you lose root by flashing?
Click to expand...
Click to collapse
I believe that they are still rooted as I don't think I removed su/Superuser.apk/busybox from them before zipping them up.
If I want to go back to ED1 with the abillity to do OTA ED2, will flashing this ED1 package do it? (I am on pbj time and ED2 rooted/cwm).
I have disabled voodoo, so basically I'm asking if I should use the ED1 ODIN downgrade or this?
Ultimately I want to be completely stock, on ED1, stock kernel, stock recovery, with the ability to update to ED2.
Phone is currently: PBJ time Kernel (no lagfix), ED2/rooted/cwm
Got my answer in IRC. ODIN works for this problem
Ok, since EE4 came out, I needed to use these last night. Found that ED2 update package needs fixed, but I got the file I needed to fix it (stock ED2 kernel) and I'll do that as soon as I get a chance. ED2 is also rooted, but ED1 is completely stock, and there is now a stock EE4 package. Look for deodexed versions coming soon as well.
This is the Gingerbread KG4 leak + root.
This is completely stock and contains all bloat.
Instructions:
1. Odin Kd1 and KG4 Bootloaders(for Modded Recovery)
2. Boot into CWM recovery
3. Make sure mounts are correct
4. Flash via CWM
Let me know if any bugs are found.
Here is the Download
LINK
which odin file has the KG4 Bootloaders?
Infact,
Download and flash the leaked KG4.
It has the boot loaders.
Then flash Whitehawkx deodexed KD1.
You will now have the KG4 Bootloaders and the KD1 modded recovery.
Boot into recovery, load up CWM and flash. Let me know if you have any problems.
nice job flip ill have to tear it apart and lol do my majik
oh and if ur host gives issues let me know ill put it up on sourceforge for ya
Awesome! Is this the fixed root which does not break audio?
Sent from my SGH-T959V using Tapatalk
Hey,
Thanks guys.
I haven't tested it myself.
I hope its root works
it may not even have a working root.
For best results, I know ChainsDD has a flash able super user.
Use that after flashing.
For the audio, this should have working audio.
It will reinstall all the root stuff without causing kernel issues.
VICosPhi said:
Awesome! Is this the fixed root which does not break audio?
Sent from my SGH-T959V using Tapatalk
Click to expand...
Click to collapse
+1 on this too
I have working audio with the original root for gb not sure why you'res breaks
sent from my sgs4g 2.3.3, finally
airfluip1 said:
This is the Gingerbread KG4 leak + root.
This is completely stock and contains all bloat.
Instructions:
1. Odin Kd1 and KG4 Bootloaders(for Modded Recovery)
2. Boot into CWM recovery
3. Make sure mounts are correct
4. Flash via CWM
Let me know if any bugs are found.
Here is the Download
LINK
Click to expand...
Click to collapse
Nice! good job!!!
dsexton702 said:
I have working audio with the original root for gb not sure why you'res breaks
sent from my sgs4g 2.3.3, finally
Click to expand...
Click to collapse
+1 no audio problems here with original root method. Flashed both zimages using heimdall.
airfluip1 said:
Infact,
Download and flash the leaked KG4.
It has the boot loaders.
Then flash Whitehawkx deodexed KD1.
You will now have the KG4 Bootloaders and the KD1 modded recovery.
Boot into recovery, load up CWM and flash. Let me know if you have any problems.
Click to expand...
Click to collapse
I followed these steps but after i flashed it it got a boot loop... any idea?
It vibrates during the boot loops
I now pulled the battery and went to recovery but when it doesnt give me the option to reinstall packages and when i go to apply update from sdcard it says installation aborted
I will take a look tomorrow.
Sent from my SGH-T959V using XDA App
brandond15 said:
I followed these steps but after i flashed it it got a boot loop... any idea?
It vibrates during the boot loops
I now pulled the battery and went to recovery but when it doesnt give me the option to reinstall packages and when i go to apply update from sdcard it says installation aborted
Click to expand...
Click to collapse
+1 on this.. I get the exact same thing after flashing.
Ill just odin back to the leaked 2.3.4 until its working...if you need to test an updated one ill test it
kkoshko1 said:
+1 no audio problems here with original root method. Flashed both zimages using heimdall.
Click to expand...
Click to collapse
Audio works fine for me except during startup boot animation and also during wifi calling. Turning volume to 100% only gives you an effect of 15% volume for wifi calling and no audio for startup animation.
I don't think Whitehawkx ODIN KD1 has the modified recovery.. I flashed that rom a few times, and always had to push the modded recovery file into system\bin to get CWM.
I think that's why you guys are boot looping.
well one of his KD1's has it, I always flash it when need to go from GB to a CWM rom. It always works.
The file name is called PDA_KD1.tar
ah, maybe I'm thinking of KC1 then. Whitehawkx KD1 was stated to sometimes cause a bad file system though, which can affect future ROM flashes.
help
after flashing this ROM, my hpoone gt at blurred sbootanimation and it keeps on rebooting. it seems that it ruined my ROM, help me please.
hey airfluip1 thank you very much for making this but i as well get a boot loop do you think you could make a odin flashable version of this please that would help me out alot thanks again for everything.
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
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
Anyone know how to Root the new Gingerbread 2.3.6 stock leak that was posted? I am talking about UCLB3. I went to "Settings"- "Privacy" - "Factory data reset and was prepared to start over at Froyo. When the phone finished booting up my factory setting is now 2.3.6 UCLB3. I am not a noob but not real experienced either. I spent hours last night trying to root the phone. I want to put the rooted version from Dman on - I couldn't even use ODIN and Heimdall or GTG's unbrick versions to take me backwards. I am on 2.3.6 no matter what I do. Anyone care to help?
is ODIN not recognizing the phone or whats the situation ? Heimdall is for flashing stock 2.3.6 or cwm for froyo.
There is no way to root the new leak... you can flash a rooted kernel, then flash the stock kernel back and you'll retain root
Sent from my SAMSUNG-SGH-I997 using xda premium
dman3285 said:
There is no way to root the new leak... you can flash a rooted kernel, then flash the stock kernel back and you'll retain root
Sent from my SAMSUNG-SGH-I997 using xda premium
Click to expand...
Click to collapse
Thanks for your comment. I saw something about that in the UCKK3 stock rom post, I think. That`s an effective way to root the 2.3.6 leak/stock?
Is that the way to do it? odin>flash pda only with auto-reboot and f.reset time>flash again the stock kernel (pda only). Is this right?
Any way to install CWM kernel in between? I'll be very pleased with a right answer, thanks!!!
Rooting stock 2.3.6
Thanks to you guys who helped with my issue. I got the phone to recognize download mode and flashed a CWM Kernel and then the stock one and kept root. (Thanks DMan) Since I was busy I didn't get this done until Friday and then the Collective comes out with Revelation which after reading the posts I immediately flashed. Prior to Revelation my favorite ROM had been Caty 3.0 but I think Dman and the Collective have put out my new favorite now.