Related
Following up on my ported Bali kernel, here's a "ROM" to use it with, even though this really isn't much of a ROM, but more of a base for other themers to work with. It's a deodexed version of our update, and includes Root, as well as my ported Bali kernel. Other than that, nothing should be different from the Stock ODIN update.
My test had a broken browser app, so I pulled the stock browser for KG1 and deodexed it.
-BaliKG1 port from Dr. Honk's original Bali kernel
-Deodexed and rooted
-Flash script from ayoteddy's roms
-Updated Market, and Voodoo Control app by Supercurio to make use of the Bali kernel.
This does include Bali, but the name isn't changed in settings, this will be an update to the Bali kernel when I get motivated to do it, as that is just an asthetic change, it doesn't make a difference to the actual functionality of the kernel.
Download: http://www.multiupload.com/7DH5QLGGGW
It work's great i pulled the stock browser from KG1 ROM & put it on this KG2 & it work's perfect .
sduvick said:
Following up on my ported Bali kernel, here's a "ROM" to use it with, even though this really isn't much of a ROM, but more of a base for other themers to work with. It's a deodexed version of our update, and includes Root, as well as my ported Bali kernel. Other than that, nothing should be different from the Stock ODIN update.
My test had a broken browser app, so I pulled the stock browser for KG1 and deodexed it.
-BaliKG1 port from Dr. Honk's original Bali kernel
-Deodexed and rooted
-Flash script from ayoteddy's roms
-Updated Market, and Voodoo Control app by Supercurio to make use of the Bali kernel.
This does include Bali, but the name isn't changed in settings, this will be an update to the Bali kernel when I get motivated to do it, as that is just an asthetic change, it doesn't make a difference to the actual functionality of the kernel.
Uploading now, and I will post the link when it gets uploaded.
Click to expand...
Click to collapse
Can this be flashed over a rooted KG1? I tried doing so and I softbricked. I'm in the process of ODINing to stock KG2.
Also, is it safe to restore the data from a KG1 nandroid?
This should work to flash from KG1, you may have softbricked because you didn't check your mounts before and after flashing? restoring data should be fine, make sure you wipe your dalvik-cache from the advanced menu in CWM after restoring your data so that it rebuilds.
Yea, I don't think I checked my mounts. I'm ODIN'ing to KG2, then I'll be rooting, CWM'ing, and then flashing this ROM. Thanks!
Let me know if you're still having problems, I'll do my best to help you out!
I got it to work. Thanks for giving me the heads up on the mounts. I'm sure that's what softbricked me. Thanks again!
Sent from my SGH-T839 using XDA App
So is this rom up to speed compared to Smooth Maximus GingerClone? I'm reading form T-Mobile support that it actually lags a lot more than stock rom. Can this be flashed from GingerClone? Or must I odin first?
This can be flashed from GingerClone, as it contains both the updated firmware and the updated kernel. This is not really intended to be a rom persay, but rather to be a base for other themers and devs to make roms with. There's no speed changes, other than the lagfix that comes from Bali.
I'm using it now. It is pretty good already with bali implemented. Other than Media Room becoming an active process periodically, the stock experience is going well. The disability of the track pad will be very helpful outdoors.
Also got a soft brick trying this. Goes to the boot screen, and the motor buzzes once, then twice in a row, pauses then does the buzzing again.
Double checked the mounts before doing it.
Can still get into recovery, but trying to reinstall packages gives an invalid signature error.
Ugh...
Then it didn't flash correctly. You would have red CWM if this flashed correctly. Odin back to stock and try again, as if you can't get into recovery correctly, you can't do anything from there. You may want to redownload to make sure that you get a good copy.
That's what I did. Odin to stoc kg2, rooted, added cwm recovery (orange) then used same copy i downloaded earlier to flash. Worked properly.
Might be worth a test, that this might not be cwm flashable over stock kd1. Thats 2 reports of it happening so far, and i am not a beginner in flashing or following directions. Just an annoyance really, odin was painless to use. (Now, having to reinstall windows on a old pc laptop, so much fun /sarcasm) ;P
I've done it before just fine, flashing on the SK4G is different from most phones, if you don't check your mounts before and after, then it will not work.
All ROMs here include a KD1 or KG2 specific kernel in addition to their specific systems, so as long as mounts are checked, everything is overwritten. /system is entirely wiped in the flashing process, and a new kernel is flashed. There is no possible way, given a correct flashing procedure and a ROM that includes a kernel (which as far as I know are all the ones here) that this would not work to flash KD1 over KG2 or vice versa.
So far, this is the fastest rom I've tried, thank you for creating it! Even if its stock.
This had serve me fantastically. Wish the same was available for kj2
You mean like this?
http://forum.xda-developers.com/showthread.php?t=1328698
sduvick said:
You mean like this?
http://forum.xda-developers.com/showthread.php?t=1328698
Click to expand...
Click to collapse
Sadly, it is Bali/Voodoo-less.
Download link for this doesn't work. States the file has been deleted.
Does anyone have this file still?
I am running de-bloated EP1W on droid charge, and i was wondering if i can install CWM recovery onto the phone with this 2.3.4
cause i tried earlier today, and i thought i bricked my phone, but after 1 hour of trying, i was able to install fresh copy of ep1w.
i tried to install CWM with odin 1.82
any suggestions how to make this happen?
[email protected] said:
I am running de-bloated EP1W on droid charge, and i was wondering if i can install CWM recovery onto the phone with this 2.3.4
cause i tried earlier today, and i thought i bricked my phone, but after 1 hour of trying, i was able to install fresh copy of ep1w.
i tried to install CWM with odin 1.82
any suggestions how to make this happen?
Click to expand...
Click to collapse
there shouldn't be a problem with that... put the CWM file in PDA, keep battery in and uncheck the 'auto reboot' and flash away but keep in mind it'll be one time use since there's no custom kernel
blazing through on my 4G Droid Charge
ep1w
ya when i finished the flash, i got into a bootloop on the SAMSUNG logo.
anoninja118 said:
there shouldn't be a problem with that... put the CWM file in PDA, keep battery in and uncheck the 'auto reboot' and flash away but keep in mind it'll be one time use since there's no custom kernel
blazing through on my 4G Droid Charge
Click to expand...
Click to collapse
imoseyon has a custom kernel with ext4 autoconversion and init.d scripting support posted over at rootzwiki. It doesn't have a lot of tweaking since we still don't have source, but I can verify that those two things definitely work.
[email protected] said:
ya when i finished the flash, i got into a bootloop on the SAMSUNG logo.
Click to expand...
Click to collapse
it bootloops right after you unplug it? flashing CWM shouldn't affect anything with how the phone boots
blazing through on my 4G Droid Charge
anoninja118 said:
it bootloops right after you unplug it? flashing CWM shouldn't affect anything with how the phone boots
blazing through on my 4G Droid Charge
Click to expand...
Click to collapse
yes, it bootlooped right after flashing CWM onto EP1W. and after it bootlooped, i tried flashing a fresh EP1W with Odin 1.82, and it didnt want to do it. I was finally able to flash EP1W with Odin 1.85.
2 questions,
1. is there a stock recovery available to flash if i run into this problem again?
2. off topic- is there a Samsung Media Hub APK available for the de-bloated version of EP1W.
LINK
shrike1978 said:
imoseyon has a custom kernel with ext4 autoconversion and init.d scripting support posted over at rootzwiki. It doesn't have a lot of tweaking since we still don't have source, but I can verify that those two things definitely work.
Click to expand...
Click to collapse
do you have a link?
Thanks.
[email protected] said:
do you have a link?
Thanks.
Click to expand...
Click to collapse
http://rootzwiki.com/showthread.php...rnel-(leaked-stock-repacked-v1.0.5ext4-9-6-11)
[email protected] said:
2. off topic- is there a Samsung Media Hub APK available for the de-bloated version of EP1W.
Click to expand...
Click to collapse
Media Hub for Fascinate from the Market has always worked in the past. I can't verify it for sure on EP1W and imoseyon 1.0.5 since my phone isn't on me, but it definitely worked on EP1Q.
Personally, I used Odin v1.83 to load EP1W and then I flashed the imunts CWM 08-17-11 version after that with no problems at all.
However, here is what I did:
After entering Download Mode on the phone, and before starting the flash, I put the battery back into the phone!
Also, I unchecked those two options (auto reboot and reset time)
When both Odin and the phone showed that flashing was completed, I removed the USB and then removed the battery.
I fully loaded EP1W using this method, then I booted up the phone and let it fully boot.
I shutdown the phone and put it back into Download Mode and did the CWM separately. I did not try to flash the EP1W and CWM at the same time.
ya, i didnt try flashing at the same time either, it was days apart, first EP1W, then CWM.
i already had EP1Q, but apparently when i flashed over from EP1Q to EP1W, my CMW was gone, thats why i wanted to flash it onto my phone again.
shrike1978 said:
Media Hub for Fascinate from the Market has always worked in the past. I can't verify it for sure on EP1W and imoseyon 1.0.5 since my phone isn't on me, but it definitely worked on EP1Q.
Click to expand...
Click to collapse
find Nitros Eclipse GB thread in development he has a download link in the OP
blazing through on my 4G Droid Charge
Okay ... So I am about to update to the latest pushed version. Am rolling back to EE4 now and have the update.zip on my card. What about CWM? Does my current version I've been using with my Gummy Charged 2.1 work with it? I have the Imosyn (sp) kernel on my card that I will apply after the update to 2.3.6 for root, as I understand it.
Are there any Gummy's or anything that are going to work after the 'official' update?
You don't use CWM with the update. You use stock recovery.
Gummy is EP1W. If you install it over the OTA, you'll bring yourself right back down to EP1, and the update will be pointless. You can get lagfix by running imoseyon kernel. It's EP4. It's slightly older EP4, but I haven't had any issues.
shrike1978 said:
You don't use CWM with the update. You use stock recovery.
Gummy is EP1W. If you install it over the OTA, you'll bring yourself right back down to EP1, and the update will be pointless. You can get lagfix by running imoseyon kernel. It's EP4. It's slightly older EP4, but I haven't had any issues.
Click to expand...
Click to collapse
Thank you sir! Phone is updating now. I will apply the imoseyon kernel after it's done. Lagfix is the main thing anyhow, I can nuke the bloatness with my Titanium.
now I'm confused .... I no longer have CWM recovery. How am I to apply the imoseyon kernel via stock recovery? Can I just rename it as update.zip?
By taking it back to stock EE4 and installing the update, one of the things it did was restore the default recovery environment.
Go back into ODIN and install CWM, don't use Auto-Reboot. When it's done flashing, turn the phone off and hold the button combinations to start the phone into CWM. Flash iMoseyOn's kernel and you're done at that point.
trparky said:
By taking it back to stock EE4 and installing the update, one of the things it did was restore the default recovery environment.
Go back into ODIN and install CWM, don't use Auto-Reboot. When it's done flashing, turn the phone off and hold the button combinations to start the phone into CWM. Flash iMoseyOn's kernel and you're done at that point.
Click to expand...
Click to collapse
Ahhhh.... it's @ the Sammy screen and she's talking to me! Looks like all is good while it re-writes the allocation tables. Thanx again, appreciate the heck out of the help.
hmmm .... I guess all is not well ... I installed the kernel but I don't have root. I installed superuser from the market and then Titanium and when opening Titanium I have no root .... what next?
Chopstix9 said:
hmmm .... I guess all is not well ... I installed the kernel but I don't have root. I installed superuser from the market and then Titanium and when opening Titanium I have no root .... what next?
Click to expand...
Click to collapse
You SHOULD have root since the kernel is your root method. Have you tried restarting?
Sent from my SCH-I510 using xda premium
Yeah I sure have. The kernel I used is imoseyon_kernel_charge_gb_4.0.0 ... not rooted .... guess I need to drop five yards and punt (do it all over)
Edit: The one thing I did not do prior to rolling back to EE4 was to do the big 3 wipe of data/cache/etc ..... maybe that's the problem?
Chopstix9 said:
Yeah I sure have. The kernel I used is imoseyon_kernel_charge_gb_4.0.0 ... not rooted .... guess I need to drop five yards and punt (do it all over)
Edit: The one thing I did not do prior to rolling back to EE4 was to do the big 3 wipe of data/cache/etc ..... maybe that's the problem?
Click to expand...
Click to collapse
Try installing Superuser from the Market? imosyeon kernel should have installed binary and apk, but maybe it missed part of it. If all else fails, flash the superuser zip from CWM.
http://www.toms-world.org/android/download/http/Superuser-3.0.7-efgh-signed.zip
Yes, I had installed SU from the market and didn't have root. I had an SU zip saved on my desktop .... su-2.3.6.3-efgh-signed .... I put that on the sd and installed it and I am rooted !!
Thanx Again
I love Lagfix and Voodoo Sound, but I'm currently running the stock kernel. I read in other forum discussion that Samsung designs their kernels to work with their OS revisions. People have said they're getting the best performance with the stock kernel.
Until IMoseyOn releases a new kernel based on the EP4D source that was released, I'm going to stick with stock.
Just some food for thought.
KarateExplosion6 said:
I love Lagfix and Voodoo Sound, but I'm currently running the stock kernel. I read in other forum discussion that Samsung designs their kernels to work with their OS revisions. People have said they're getting the best performance with the stock kernel.
Until IMoseyOn releases a new kernel based on the EP4D source that was released, I'm going to stick with stock.
Just some food for thought.
Click to expand...
Click to collapse
My concern was updating to 2.3.6 and having root. (on the road all day and need wireless tethering so outlook is open on laptop) Using the tad older imoseyon kernel gave me that, plus lagfix, which I have liked since this phone hit the market. I'm good for now, I can always update when the latest and greatest comes out.
Chopstix9 said:
My concern was updating to 2.3.6 and having root. (on the road all day and need wireless tethering so outlook is open on laptop) Using the tad older imoseyon kernel gave me that, plus lagfix, which I have liked since this phone hit the market. I'm good for now, I can always update when the latest and greatest comes out.
Click to expand...
Click to collapse
I have root on the stock kernel bro. Did a clean EE4 install, skipped as much set up as possible, ran update.zip in stock recovery, ODIN flashed imnuts' latest CWM recovery with auto-reboot disabled, booted directly into CWM recovery, flashed the latest SU zip, then ran setup as normal. Boom! Root.
Completely clean install, latest OS and kernel, root, plus tether works and everything.
Right now I'm just waiting on imnuts' TW4 theme to launch (he's estimating Sunday). Hopefully I can install that theme over a debloated and deodexed version of the latest OTA. It won't be long before IMoseyOn releases a kernel built from source that enables Lagfix. That's really all I'm missing, since Voodoo Control lets me load most of Voodoo Sound on top of the stock kernel.
What I'm REALLY looking forward to is an release of Liberty for the Charge or something AOSP if we ever get the 4G RIL sorted out... This things will take considerable time though.
It just doesn't matter ... In all honesty I liked the feel of the Gummy GBE 2.1 better than this stock ginger ... but again, it just doesn't matter to me. Functionality is all I care about, it's only a damn phone !!!
I loaded up the debloated/deodexed/rooted all-in one package danalo posted in development, flashed perfectly and after a wipe in CWM on first boot seems to be running fine except for the poop
sent from my Acer Iconia A500 beast of a tablet via XDA app
KarateExplosion6 said:
I have root on the stock kernel bro. Did a clean EE4 install, skipped as much set up as possible, ran update.zip in stock recovery, ODIN flashed imnuts' latest CWM recovery with auto-reboot disabled, booted directly into CWM recovery, flashed the latest SU zip, then ran setup as normal. Boom! Root.
Completely clean install, latest OS and kernel, root, plus tether works and everything.
Right now I'm just waiting on imnuts' TW4 theme to launch (he's estimating Sunday). Hopefully I can install that theme over a debloated and deodexed version of the latest OTA. It won't be long before IMoseyOn releases a kernel built from source that enables Lagfix. That's really all I'm missing, since Voodoo Control lets me load most of Voodoo Sound on top of the stock kernel.
What I'm REALLY looking forward to is an release of Liberty for the Charge or something AOSP if we ever get the 4G RIL sorted out... This things will take considerable time though.
Click to expand...
Click to collapse
Care to make a thread of what you done? Files used? I want to re-root my Charge, but want to keep the latest ota update and radios. Main question is the "update.zip" file?
iMoseyOn has stated that he's not going to be developing kernels anymore due to him having to turn in all of his phones to his old employer. He's taken up a new job and because of that he has to return his phones, including the Droid Charge.
trparky said:
iMoseyOn has stated that he's not going to be developing kernels anymore due to him having to turn in all of his phones to his old employer. He's taken up a new job and because of that he has to return his phones, including the Droid Charge.
Click to expand...
Click to collapse
Yeah, I read last night. Awful news. I hope someone can just get us full Voodoo and EXT4 support. I don't absolutely need OC/UV, but it'd be nice...
In other bad news, imnuts is getting a Galaxy Nexus and only pledging support for the Charge for "a few more months."
Let's hope JT and the gang can get this RIL figured out, so we can at least have Team Douche to continue development with CM 7.2 and CM 9...
Sent from my SCH-I510 using xda premium
Damn. And I thought it couldn't get any worse with iMoseyOn leaving. And now we have imnuts leaving too? It just went from bad to worse in a matter of 48 hours!
Guess I better get used to just using the stock kernel.
Inherited a Droid Charge running GummyCharged 2.1 from my housemate.
I want to switch to Eclipse 2.0. I know in order to run FP1 builds, you need to run stock kernel if you want wifi. Except, I also noticed that the PBJ kernel recently fixed the wifi issue.
I'm under the impression you're told to revert to stock, run OTA update, then flash your FP1 ROM so you have the latest stock kernel.
Or is there more to it than the kernel?
I'd rather skip the revert/flash/etc/etc, I updated to the latest CWM, made a backup, factory restored, wiped cache/dalvik, flashed ROM, flashed kernel, rebooted, everything seems fine (wifi working no issues). But... that doesn't mean that it is.
EDIT: Yeah, my baseband in About Phone shows i510.06 V.EE4 SCH-I510.EE1, which is what it was before. Can I get just the baseband?
Thanks!
By the way, I don't care about carrier signal at all, this phone got wet and no longer accepts SIM cards. The other functions still work, so I'm using it on wifi and I'm trying to re-purpose the device to be a portable offline GPS for hiking. But I did read that FP1 gets better GPS locks, which is part of why I want to run it.
U cant get the fp1 upgrade on a cstom rom. U have to go back to stock n get the ota upgrade. I suggest usin titanium to back up ur stuff then flash what u want. Stock fp1 or pjb 5/24 r both good, but u gta get back to factory first.
Sent from my SCH-I510 using XDA
Actually, I figured "what you do do well" and I decided to follow the suggested directions. I used ODIN, restored to stock EP4... and couldn't get past the main screen. Can't read SIM cards, so can't get past the activate screen. I then flashed back an FP1 rom, the latest PBJ kernel, and [attempted] to use the EP4 to FP1 patch, which hung and failed.
It looks like if I want to get my baseband to FP1, I'll have to jump through hoops (maybe flashing a stock EP4 pre-rooted ROM from ODIN? maybe?) Regardless, since the CDMA antenna in this thing is useless anyway, I'm just gonna skip it.
Thank you for your reply!
Well, now that you have borked your phone a bit, go and download the EP4 ODIN package and flash it (in ODIN or SamsungPST). Might not be a bad idea to flash the PIT while you're at it. You'll probably have to flash CWM, and then PBJ from within CWM (stock kernel overwrites it) Then go and try flashing your ROM of choice again (cough *tweaked* cough), either in ODIN (with the respective package) or CWM. (again with the proper package).
http://www.imnuts.org/odin-packages/
Sent from my SCH-I510 using xda premium
thanks kvswim, that's pretty much exactly what I did yesterday. I'm even running Tweaked 2.1
It's too bad, I really prefer the theme of Eclipse, but I just couldn't handle the lack of TSM Parts.
what is the latest modem that's out for the droid charge and does anyone have an odin file for it? i'd prefer to not have to reload my phone totally just to get the latest.. currently running eclipse rom 2.0
leaveone said:
what is the latest modem that's out for the droid charge and does anyone have an odin file for it? i'd prefer to not have to reload my phone totally just to get the latest.. currently running eclipse rom 2.0
Click to expand...
Click to collapse
FP5 stock only.
so there's no installable file for just the modem then? just gotta take the OTAs and go from there?
leaveone said:
so there's no installable file for just the modem then? just gotta take the OTAs and go from there?
Click to expand...
Click to collapse
hmm... not sure. I vaguely recall someone putting the modems out somewhere, but maybe that was for FP1. maybe someone a little more experienced can chime.
sorry I could not be of any more help.
I believe I remember a patch being posted. There are no full modems for anything newer than EP4. Also, if I'm not mistaken, your signal bars will not work if you are running FP5 modems with an FP1 rom, due to the differences in the way the signal is reported.
If you ODIN the EP4 modems, there are modem updater zips you can use (CWM flashable) to go from EP4 to FP1, and then FP1 to FP5. If you are an Eclipse 2, then you are likely on FP1 (maybe anyway) and all you need is the FP1 to FP5 modem updater. That being said, if you are an FP1 build (which Eclipse 2.0 is) the signal strength reporting will be wonky when using FP5 modems. From what I understand actual connectivity isn't affected, just how the system presents the strength of that connectivity. Here is a link to it (ironically it was in the OP of the Tweaked 3 thread).
EDIT: In other words - what shrike78 said
Yup, tried all combos myself. Good.
Sent from my SCH-I510 using xda premium
Thanks guys! I am on FP1 Eclipse Rom 2.0. Whichever modem I currently had was constantly going in and out so I reflashed the newest one that I had, which was EP4, so that's what I have now. Where is this modem updater to go from EP4 to FP1? If I can get to FP1, I'll likely just stay there to avoid the signal reporting issues on FP5.
leaveone said:
Thanks guys! I am on FP1 Eclipse Rom 2.0. Whichever modem I currently had was constantly going in and out so I reflashed the newest one that I had, which was EP4, so that's what I have now. Where is this modem updater to go from EP4 to FP1? If I can get to FP1, I'll likely just stay there to avoid the signal reporting issues on FP5.
Click to expand...
Click to collapse
I'm pretty sure this is what you're looking for - lemme know if there's a problem with it.
Thanks guys! I was able to update the modem to FP1 with the tool that dwitherell linked to. My phone still does drop signal from time to time.. maybe it's just an issue in the area I live or just that the phone has had a year of use on it..
leaveone said:
Thanks guys! I was able to update the modem to FP1 with the tool that dwitherell linked to. My phone still does drop signal from time to time.. maybe it's just an issue in the area I live or just that the phone has had a year of use on it..
Click to expand...
Click to collapse
then perhaps you'll need to up it to FP5...
You can nandroid, flash factory EP4D with Odin, take both OTA's, Odin Tweaked with recovery, then restore nandroid.
Just an option
Sent from my Nexus 7 using Tapatalk 2
I'm tired of dealing with this flash ep4 stock, then update twice. I don't know how it's going to work out, but I'm trying to figure out how to pull the FP5E modems off of it. So far, all I'm getting is the LTE portion, not the CDMA portion. But then, I'm not done screwing around with it just yet. Hopefully I can figure out an odin file.
edji-x said:
I'm tired of dealing with this flash ep4 stock, then update twice. I don't know how it's going to work out, but I'm trying to figure out how to pull the FP5E modems off of it. So far, all I'm getting is the LTE portion, not the CDMA portion. But then, I'm not done screwing around with it just yet. Hopefully I can figure out an odin file.
Click to expand...
Click to collapse
The CDMA portion isn't accessible. Thank Samsung for going with VIA.
The only way there were ever full flashable CDMA modems for the Charge were because there were sources for leaks. Those sources have dried up as people have moved on to other devices.