Related
I've searched around and couldn't find anything.
I'm on 2.3.3 on 78C, and the update continually fails. Can anyone give me and hints as to why?
I tried it while using the 2.3.2 netarchy 1.2.5 kernel, as well as 100% stock android 2.3.2 with no luck.
I realize that 2.3.3 has screen issues but i'd still like to get a hold of it for the 1.2.7 netarchy kernel.
Any and all help is appreciated.
SpartusTana said:
I've searched around and couldn't find anything.
I'm on 2.3.3 on 78C, and the update continually fails. Can anyone give me and hints as to why?
I tried it while using the 2.3.2 netarchy 1.2.5 kernel, as well as 100% stock android 2.3.2 with no luck.
I realize that 2.3.3 has screen issues but i'd still like to get a hold of it for the 1.2.7 netarchy kernel.
Any and all help is appreciated.
Click to expand...
Click to collapse
Are you sure your Android was really 100% stock when you tried the update that way? If you had installed netarchy kernel prior to that, be advised that netarchy replaces the file bcm4329.ko in the /system/modules folder, and that this will cause the update to fail since it doesn't match the crc check of the file.
The netarchy kernel just by itself will cause a failure because it makes the boot.img partition not match the crc in the update scripts.
You need to make sure that EVERY file that the updater-script file in the OTA looks at is actually a 2.3.2 version. That means if you've flashed a custom kernel that replaces modules, or replaced /system/apps like Gmail with something themed, you have to undo all those changes.
In your case, assuming you were really 100% stock, then flashed netarchy, then went back to stock by just flashing a nandroid of the boot.img, I'd say if you just replace the bcm4329.ko file with one I posted in another thread this morning that you'll probaby be able to update.
If not, the script usually shows some text on the screen about what failed.
Your other option is to apply the full 94mb update that OVERWRITES your /system instead of patching it. I don't think that will cause any data loss, but don't hold me to that. I'd be sure to have a current nandroid and titanium backup in case something goes wrong.
The other option is to get the 2.3.3 pre-rooted nandroid from the development section and just flash it with clockwork.
Good luck.
ah, very good. thank you for the reply. I'll probably just grab that nandroid backup with 2.3.3 and root. i appreciate the help and thank you again.
This stuff is not for the faint of heart !! Bricking a $300.00 phone is stressfull !!
Okay ... after much trial and error, this is what I did and I have what looks to me to be a stock rooted EE4. I am sure it is not stock as I used imnuts' debloated tar but that's fine, it is working and not trying to send me an update.
Okay, regardless of what I went thru to get to this point, these are the steps I took to have the phone updated to EE4 and rooted.
via Odin 3 I rolled the phone back to ED1 using the [ODIN] Stock Rooted ED1 (downgrade from ED2) [2011.05.18] file found in the Dev forum.
The phone re-booted and was again a stock rooted ED1 and it was trying to push me the EE4 update. I DID NOT update the phone OTA.
I immediately took the battery back out and went back into Odin and flashed imnuts' debloated ee4 file found at [ROM][06-10-2011] EE4 Debloated V4.2.1 in the dev forum.
When re-booting after this flash, the Samsung logo stayed on the screen for what must have been a good 8+ minutes. There was a sexy female voice that would occasionally talk to me and soothe my nerves during this process. The phone rebooted !!
After flashing I rebooted and the phone was trying to push the ee4 update to me. I went into 'about phone' and checked and what it showed was
Baseband Version
i510.06.V.EE4
SCH-I510.EE1
Build number
SCH-I510.ED1
I then went into the build.prop editor using SGS Tools and changed all instances of ED1 to EE4. I believe there are 5 of them to change.
After saving the changes I rebooted the phone. Upon re-start, I went back in and checked the build number and it is
SCH-I510.EE4
The phone is not attempting to send any system updates and it IS rooted.
I then went into it with Titanium and deleted a lot of the useless pre-installed apps.
So far so good. It looks to me like it's where I wanted it.
Dude, that's complicated. But if it works, then it works. Cant complain against that, huh?
Here is what I did.
Flash back to stock ED1 rooted. Take the OTA update, flash droidxcon's ee4 package 3, flash kejar's sdcard fix, flash imnuts debloated v4.2.1, and boom. You're rooted EE4 with EE4 basebands.
After that, I flashed Gummy.
LOL... I think it's actually less complicated than I am wordy !!!
Rollback to ED1
Flash imnuts debloated EE4
Edit build.prop
That's all there really was to it.
That gives EE4 Basebands and EE4 Build
The rest of the book was just me explaining the process I took in checking everything.
But like ya said, it's the end result that matters !!
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?
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.
Hi guys and gals hopefully someone can help me out here. I'm new to android and the language so forgive me for any mistakes I've made haha. So I put voodoo lagfix plus voodoo sound kernel on my phone. It was for 2.2 and I am on 2.3.4. I don't have enough posts to insert links nut if you Google easy lag fix mesmerize its the one on android authority. Anyhow I did not use sgs flasher I just did the cwm recovery apply from SD after wiping cache and dalvik. Rebooted and it was great quadrant was at 2200 and everything was smooth. Then later that day I was curious as to see what my CPU was running so I went to SetCPU to see. It just went to a black screen that could be exited by hitting home. I checked all my root access apps and they did the same thing except for nandroid browser and root checker. Root checker says system running slow and never reaches a conclusion. So I disabled lagfix in cwm recovery and rebooted. It went through and disabled it and started back but apps all behave the same. I do have full access to superuser. What could cause this? Would removing voodoo fix this and if so could someone give or point me to a step by step tut?
Would flashing a new kernel remove the voodoo kernel?
Just to clarify if you haven't already solved your problem.
1.What phone are you using?
2. what Rom or Radio are you on?
3. and which kernel.did you flash?
My Mesmerize is running Awesome Sauce 10.5 & there are a handful of compatable Kernels (I use KGB kernel w/ app).
Sent from my Sauced Mesmerize using the XDA developers app!