[ROM][STOCK][CWM] Stock Deodexed ROMs - Verizon Droid Charge

Not sure why anyone would really need these versus a debloated ROM, but here they are. These are the stock ROMs, just deodexed and zip aligned. They won't flash the kernel, only system.
Download - ED1
Download - ED2
Download - EE4

Updated OP with deodexed EE4

will you be releasing a debloated ee4?

asenduk said:
will you be releasing a debloated ee4?
Click to expand...
Click to collapse
Yes, slowly working on getting the debloated ROM updated.

Can I flash this in odin with lagfix enabled???? Rooted my charge last night worked great, woke up this morning and stuck on samsung logo
Sent from my SCH-I500 using XDA Premium App

No, these are meant to be flashed in CWM and you will want to have Voodoo disabled before flashing any of the packages here.

Ok im so glad you posted these, imnuts. These files basically got my baseband modems back.?
Sent from my SCH-I510 using XDA Premium App

Does the EE4 include the new Radio? Thanks!

Doing this gets rid of root?
This will put back to factory correct?

Jessberto said:
This will put back to factory correct?
Click to expand...
Click to collapse
Deodexed factory, which isn't stock. These are primarily for anyone looking to create a ROM, or looking for a particular file, or files, that aren't in a ROM. That, or someone who is fine with Stock, but would like to use a theme.

Jessberto said:
This will put back to factory correct?
Click to expand...
Click to collapse
No, you need the real stock ROMs here:
http://forum.xda-developers.com/showthread.php?t=1108115

Unfortunately, I have an issue with the EE4 deodexed ROM, and it is reproducible.
After installing it for the first time, I get an error in CWM stating "Can't mount /sdcard." Reflashing CWM with ODIN did not fix the issue. Note that on this install, I had installed the PBJ kernel prior to installing this deodexed ROM.
At this point, I had to restore the full stock ED2 and do the OTA to EE4. This time I installed this deodexed EE4 first, rather than installing the kernel first to see if that made a difference. After installing this deodexed EE4 once again, it went back to the default android recovery. After reinstalling CWM, I once again got the same error of "Can't mount /sdcard." This is a problem since I am no longer able to do any updates in CWM.
This EE4 deodexed ROM will boot, but I have problems accessing the SD card when hooked to the computer. It can't read many files, and won't write at all. I have no problems accessing the SD card outside of this ROM.
Any help or suggestions are greatly appreciated!

BeefJerky9 said:
Unfortunately, I have an issue with the EE4 deodexed ROM, and it is reproducible.
After installing it for the first time, I get an error in CWM stating "Can't mount /sdcard." Reflashing CWM with ODIN did not fix the issue. Note that on this install, I had installed the PBJ kernel prior to installing this deodexed ROM.
At this point, I had to restore the full stock ED2 and do the OTA to EE4. This time I installed this deodexed EE4 first, rather than installing the kernel first to see if that made a difference. After installing this deodexed EE4 once again, it went back to the default android recovery. After reinstalling CWM, I once again got the same error of "Can't mount /sdcard." This is a problem since I am no longer able to do any updates in CWM.
This EE4 deodexed ROM will boot, but I have problems accessing the SD card when hooked to the computer. It can't read many files, and won't write at all. I have no problems accessing the SD card outside of this ROM.
Any help or suggestions are greatly appreciated!
Click to expand...
Click to collapse
I have the same problem. Does anyone have a solution to this issue?

scamish76 said:
I have the same problem. Does anyone have a solution to this issue?
Click to expand...
Click to collapse
you could try mounting it manually in CWM under the mounts and storage option

unfortunately this didnt work. I decided to use imnuts debloated rom and then downloaded the deodexed rom for the apks that i wanted to install. This method seemed to fix the sdcard issue. I'm curious as to why flashing the deodexed rom would affect the scdard while the debloated rom works???
Thank you for helping anyway.

scamish76 said:
unfortunately this didnt work. I decided to use imnuts debloated rom and then downloaded the deodexed rom for the apks that i wanted to install. This method seemed to fix the sdcard issue. I'm curious as to why flashing the deodexed rom would affect the scdard while the debloated rom works???
Thank you for helping anyway.
Click to expand...
Click to collapse
if I'm not mistaken the deodexed roms were early packages that had an sd card write issue, the debloated one should include the fix, hence no issues
blazing through on my 4G Droid Charge

that must be it. Thank you for responding.

Related

DI18 update for non-stock files/kernels - *now with deodexed ROM!*

For those who removed stock files/apps and can't update with the normal update, here's a modified version that will work for you.
This update will not trash your recovery or root. You do not need a stock kernel for this update.
It will restore the required stock files/apps and update your modem from DI07 to DI18.
Update to DI18 - flashes new DI18 kernel
md5: ebfe0a1d4e59819a1fa35ff115f2b1b2
Update to DI18 - keeps existing kernel
md5: c686afd641f502bc88fc79796500592c
It's been tested on my phone and a few others and confirmed to be working. This also removes mobileAP i9000 modifications fully and restores stock build.prop (so you won't get the fingerprint assert).
DEODEXED ROM BELOW
Stock DI18 Deodexed FULL ROM update v3
This is a FULLY STOCK deodexed DI18 ROM update.zip! Flash with clockworkmod and you will get the -full- DI18, kernel and modem from DI18. It is not pre-rooted.
md5: f23c9fce3304145f0e8665a97dd1b863
Stock DI18 Deodexed FULL ROM update v3 *no kernel or modem*
md5: a54036b554b4ae8df20e5f685a88fcbd
Changes:
v3 - fix phone and camera FCs (thanks noobnl!)
v2 - removes existing .odex files and clears your dalvik-cache to solve FCs with various apps. If you flashed v1, you can fix it without reflashing
v1 - initial release
Use One click root 2.2.5 to root this ROM (w/ superuser support). I may post a pre-rooted ROM later.
*Additional Notes*
If you're on a fully stock ROM, then you don't need my update and can use the official Samsung DI18 update
Standalone DI18 modem updater, works regardless of what modem/baseband you have installed - md5: 4f897cf5a82d11926be68bd2594d0cf3
Standalone DI18 kernel updater, will flash stock DI18 kernel - md5: bb057a476af2e236cc34224c8b537226
Bluetooth will break if using non-DI18-based kernels. Upload speeds will not improve without a DI18-based kernel.
Just what I need thanks bro
Sent from my SPH-D700 using Tapatalk
I can personally attest to this working. Still retained root. Still have Bose v2 and mixup running. Everything is exactly the same before the update. Thank you!!!!
Sent from my SPH-D700 using XDA App
Dude your awesome. This worked great and only added email and mobile ap. Didnt add anything else. Question tho can i still use noobnls rom with this new update or do i have to wait for a compatible one?
U need a donate button i would give u a few bucks for this. Now i expect a update like this every ota update lol jk. Great work bro.
Works like a charm. However, speeds didn't improve for me, and now it says my build is Tha Boss Rom - MixUp kernel. Even though I've never installed/flashed Boss. Nice work either way.
Thank you, this worked perfectly!
Does it work with themed roms?
Just installed the update, and everything seems to be working fine. Is the Firmware version still supposed to read "2.1-update1"?
id_twin said:
Works like a charm. However, speeds didn't improve for me, and now it says my build is Tha Boss Rom - MixUp kernel. Even though I've never installed/flashed Boss. Nice work either way.
Click to expand...
Click to collapse
Installing just the MixUp kernel will make it read that - the kernel was made custom for that ROM.
Thanks ragnarokx, good to know.
ragnarokx said:
Just installed the update, and everything seems to be working fine. Is the Firmware version still supposed to read "2.1-update1"?
Click to expand...
Click to collapse
Firmware hasn't changed.
I'm gonna make a second version that also updates your kernel, since this update did actually bring a new kernel. But many of you probably wanna stick with your custom kernel, so I'll just offer both up.
id_twin said:
Thanks ragnarokx, good to know.
Click to expand...
Click to collapse
np.
also, i just noticed this update breaks the vanilla lockscreen mod i even tried reinstalling it.
Worked like a charm. Thanks!
Awesome, Thanks!
Firon said:
Firmware hasn't changed.
I'm gonna make a second version that also updates your kernel, since this update did actually bring a new kernel. But many of you probably wanna stick with your custom kernel, so I'll just offer both up.
Click to expand...
Click to collapse
Yep sticking with the fluff kernal its treat me well.
@Firon Do u know if i can still use noobnls andomedia rom with this new update, since its based off the d107?
Sorry to be a noobish bother, but am having a bit of trouble with this update. When I use the stock recovery mode to update, I get an error "E:signature verification failed Installation aborted."
What can I do to correct this? My phone is just rooted, no custom roms or kernels.
you have to use clockwork to flash it
hookerforjesus said:
Sorry to be a noobish bother, but am having a bit of trouble with this update. When I use the stock recovery mode to update, I get an error "E:signature verification failed Installation aborted."
What can I do to correct this? My phone is just rooted, no custom roms or kernels.
Click to expand...
Click to collapse
Try the zip from the first post in this thread:
http://forum.xda-developers.com/showthread.php?t=796885
I was like you, rooted but no other changes. I just renamed that file to update.zip put it on my sd card and did a stock recovery. Worked perfectly and didn't affect root.
hookerforjesus said:
Sorry to be a noobish bother, but am having a bit of trouble with this update. When I use the stock recovery mode to update, I get an error "E:signature verification failed Installation aborted."
What can I do to correct this? My phone is just rooted, no custom roms or kernels.
Click to expand...
Click to collapse
for the stock recovery u have to rename the zip to update.zip.
Well, this really sucks. I installed and now my stock music app wont open. It keeps force closing on launch..
I had music mod installed before i updated, and now i cant get it to run even after reinstalling.
Bluetooth not turning on after this flash..anyone else?

Sorry to beat a dead horse, bout to go insane

Ok, so i have had a samsung captivate since last summer. I just did the official froyo update the other day and it was successful with kies mini. I then decided to root it using super1click which also worked successfully. I have superuser, titanium backup with busybox installed, and super manager and terminal emulator. I also successfully got clockworkmod flashed and working.
My problem is that ive got the new cognition rom on my internal sd card, but when i try to flash it with cwm, i get the 3e recovery failure message. Ive been reading various sites today on how to fix this problem, but every site seems to tell me something different. I ask this question here, because it seems to be the most knowledgeable site to go to.
How do i get my rooted captivate, with all the above installed and running, to allow me to flash a new rom and possible a new kernal down the road? Im about to go insane trying to decipher through all the info all the different sites have said. Sorry to write such a novel on a tired subject, but im going crazy. Any help will be GREATLY appreciated. Thanks.
trontheman said:
Ok, so i have had a samsung captivate since last summer. I just did the official froyo update the other day and it was successful with kies mini. I then decided to root it using super1click which also worked successfully. I have superuser, titanium backup with busybox installed, and super manager and terminal emulator. I also successfully got clockworkmod flashed and working.
My problem is that ive got the new cognition rom on my internal sd card, but when i try to flash it with cwm, i get the 3e recovery failure message. Ive been reading various sites today on how to fix this problem, but every site seems to tell me something different. I ask this question here, because it seems to be the most knowledgeable site to go to.
How do i get my rooted captivate, with all the above installed and running, to allow me to flash a new rom and possible a new kernal down the road? Im about to go insane trying to decipher through all the info all the different sites have said. Sorry to write such a novel on a tired subject, but im going crazy. Any help will be GREATLY appreciated. Thanks.
Click to expand...
Click to collapse
If you would have done a search here then you would have found that you need to do one of 2 things.
1. Flash back to 2.1
2. Replace the 3e recovery with one that doesnt check for the sig.
I dont know how to replace the 3e recovery. I think ill go with flashing back to 2.1. Once i dl Odin and flash back to 2.1, then i can flash a new rom or a new kernel? Will it undo everything i've done so far? Thanks for the help.
trontheman said:
I dont know how to replace the 3e recovery. I think ill go with flashing back to 2.1. Once i dl Odin and flash back to 2.1, then i can flash a new rom or a new kernel? Will it undo everything i've done so far? Thanks for the help.
Click to expand...
Click to collapse
Here is a link to the replacement recovery.
Make sure you have the right odin and that your 3 button works right.
Yesh doing this will wipe out everything. Make sure to back up. Do not back up system data at all as when you restore it, it can lead to major issues. Once done with a custom rom it will be wiped clean. You will have to redo contacts, email, and all other settings
Thanks. Would it be okay to just flash a new kernel like speedmod kernal and just use the stock rom? Is that possible to do while im on rooted 2.2? I like the rom just fine, i just want it faster mainly. Thanks again.
trontheman said:
Thanks. Would it be okay to just flash a new kernel like speedmod kernal and just use the stock rom? Is that possible to do while im on rooted 2.2? I like the rom just fine, i just want it faster mainly. Thanks again.
Click to expand...
Click to collapse
To be honest I am not sure. I only had the stock on for a few hours as it was just not that great compared to the 2.2.1 rom that I have been used to running. I need BT voice dial and the added exchange options so 2.2 was not really for me. If you want a stock feel but faster then I would go with COG or one of the other roms based on the kb1 rom.
So I've come to the conclusion that I should just flash back to 2.1 and go from there. I have odin downloaded, but I'm not certain how to use it. Do you guys think I should flash a custom rom from stock, or just flash a kernel with lag fix and delete the bloatware? Thanks.
first flash 2.1 stock to get rid of the damn 3e. custom roms dont replace that always. also most custom roms dont flash with odin.
get a stock rom. read the instructions, flash
trontheman said:
So I've come to the conclusion that I should just flash back to 2.1 and go from there. I have odin downloaded, but I'm not certain how to use it. Do you guys think I should flash a custom rom from stock, or just flash a kernel with lag fix and delete the bloatware? Thanks.
Click to expand...
Click to collapse
If you are getting .zip signature errors when trying to flash a rom (because you are using 3e recovery) you will not be able to flash a kernel.
Supercurio did make a KB1 kernel that is installable via Odin. If you install that, you will also get CWM recovery. Then you can flash anything you want.
Either way you will need an Odin program. Either Odin One Click to flash back to stock 2.1 or Odin v1.7 to flash the Supercurio KB1 Kernel .tar file.
trontheman said:
Thanks. Would it be okay to just flash a new kernel like speedmod kernal and just use the stock rom? Is that possible to do while im on rooted 2.2? I like the rom just fine, i just want it faster mainly. Thanks again.
Click to expand...
Click to collapse
Correct me if i'm wrong but I think the speedmod kernal is i9000 based which would cause a major headache/bootloop on the stock rom.
Sent from my SAMSUNG-SGH-I897 using XDA App
Johnnie5000 said:
Correct me if i'm wrong but I think the speedmod kernal is i9000 based which would cause a major headache/bootloop on the stock rom.
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
....it works fine on stock 2.2, as does any other 2.2/2.2.1 kernel
Pirateghost said:
....it works fine on stock 2.2, as does any other 2.2/2.2.1 kernel
Click to expand...
Click to collapse
The problem is, the OP has no idea what he's doing. It sounds like he's wanting to flash to 2.1, then add a I9000 kernel. Since he's all over the place, it's hard to decipher what he's thinking.
To the OP. I'd HIGHLY suggest you look for the stickied "how to" video's by Connexxion. They will tell you what you need to do and show you EXACTLY how to do it. Invaluable info for the noobs.
Here is the link your looking for, download the installer zip file at the bottom of the first post. Extract to your fancy, use the install.bat file once extracted. Be sure to have the phone connect to the pc (DO NOT MOUNT) and have USB Debugging on.
Modded 3e recovery that works like 2e
trontheman said:
Ok, so i have had a samsung captivate since last summer. I just did the official froyo update the other day and it was successful with kies mini. I then decided to root it using super1click which also worked successfully. I have superuser, titanium backup with busybox installed, and super manager and terminal emulator. I also successfully got clockworkmod flashed and working.
My problem is that ive got the new cognition rom on my internal sd card, but when i try to flash it with cwm, i get the 3e recovery failure message. Ive been reading various sites today on how to fix this problem, but every site seems to tell me something different. I ask this question here, because it seems to be the most knowledgeable site to go to.
How do i get my rooted captivate, with all the above installed and running, to allow me to flash a new rom and possible a new kernal down the road? Im about to go insane trying to decipher through all the info all the different sites have said. Sorry to write such a novel on a tired subject, but im going crazy. Any help will be GREATLY appreciated. Thanks.
Click to expand...
Click to collapse
I am wanting to flash back to 2.1 and go from there. I have the drivers installed and I have odin downloaded. I tried it last night, but I couldn't get it to work. I got it to download mode, but still nothing. What could the problem be? Thanks.
I tried odin one click again today, but still nothing. All i want to do is flash back to 2.1, root, then flash a rom or custom kernel. Im losing my mind, any more help is greatly appreciated. Thanks.
Bump. Thanks.
trontheman said:
I tried odin one click again today, but still nothing. All i want to do is flash back to 2.1, root, then flash a rom or custom kernel. Im losing my mind, any more help is greatly appreciated. Thanks.
Click to expand...
Click to collapse
ok no need to flash 2.1
get neldars kernel flashing app from the market
get a kernel for froyo without 3e recovery in the dev section. this one is great
http://forum.xda-developers.com/attachment.php?attachmentid=547852&d=1300708475
use neldars app (edit) "sgs kernel flasher" or something to that effect. to flash this kernel
then flash cognition
you can also use odin3 but not the oneclick downloader without the .pit file and flash the same kernel placed in the pda slot.
when you installed keis mini, it installed new WRONG drivers (for odin)
reinstall the original other drivers.
BUT. in your OP all you wanted was to be able to flash COG or something.
ALL you have to do is fix your 3e recovery, SEVERAL people including myself have told you how to fix it. then CWM will work! you dont need a computer to fix 3e if you have root explorer (google it $) .
if you are going to flash a custom rom anyway dont bother going back to 2.1.
if you are going to stay stock, 2.2 is better anyway. (aside from 3e but staying stock dont matter)
you can also use odin3 but not the oneclick downloader without the .pit file and the same kernel placed in the pda slot.
Click to expand...
Click to collapse
@ dani - dude read the thread. odin doesn't recognize his phone.!! try to catch up before butting in...
well that doesn't make my whole post irrelivent. if he is rooted and has busy box he can use neldars kernel flasher. sorry if i over looked something.
Ok, well i got the aio toolbox, and i flashed back to stock. Now im running 2.1-update1. How do i go about rooting now? I cant seem to find a root file. Thanks.

[Odin]EE4 various packages Read Carfully

Warning!!!! Do not flash these if
A. You dont know what you are doing
B. you have not already done a manual update to EE4
C. you do not understand what they are for
XDA, any developer, or myself are NOT responsible for anything you do to your phone.​
All packages are compressed in .rar form they need to be extracted and flashed with odin. If you are a developer and just want the deodex system...well you know what to do. Also Notice Using a custome kernel on EE4 is required for root but this also write protects your sdcard for some reason so just be aware.
First package:Fully stock kernel, recovery and system(this will come in handy)
www.androphiles.com/files/android/EE4stock_DXC.tar.rar
Second package: Deodexed system, imnuts modded CWM , stock kernel (not rooted)
www.androphiles.com/files/android/EE4deodx_DXC.tar.rar
Warning having a Custom kernel Write protects your sdcard when trying to mount to your PC otherwise everything works
Third package: Deodexed system, imnuts modded CWM, jt voodoo kernel (Rooted)
www.androphiles.com/files/android/EE4dxvodo_DXC.tar.rar
Again if you need instructions on how to flash these just hold off till we can mess with this build some more.
Awesome, but, definitely holding off on this.
So we're supposed to update to EE4 before installing any of these packages?
Sweeeet. Thanks driodxcon!
Dammit, you never figured out the sdcard problem?
Sent from my SCH-I510 using XDA Premium App
Sweet thanks as always.
Kinda curious tho if we are already running your AB build with a custom kernel with Voodoo and lagfix how will we go about updating to EE4 so we don't mess up and loose root access in the process. Thanks in advance for any input.
will2live said:
Kinda curious tho if we are already running your AB build with a custom kernel with Voodoo and lagfix how will we go about updating to EE4 so we don't mess up and loose root access in the process.
Click to expand...
Click to collapse
Kind of a tedious process, but here is what I did:
1) I disabled the lagfix (create a folder called 'disable-lagfix' in /sdcard/Voodoo)
2) rebooted the phone to disable the voodoo lagfix
3) ran the stock rooted ED1 ODIN file (which I created )
4) took the OTA ED2 update and lost root
5) downloaded the EE4 update file (http://goo.gl/XTDA9) and renamed it 'update.zip' and put it on my sdcard
6) booted into recovery and applied update.zip and then let it boot
7) flashed JTs rooted voodoo kernel and his CWM in ODIN (you should probably delete the disable-lagfix folder after step 6)
NOTE: I didn't wipe at all during this process.
I have EE4 and JTs voodoo kernel and I've confirmed that I have root access.
Now it's time to get rid of this orange and brown crap... again :/
wynalazca said:
Kind of a tedious process, but here is what I did:
1) I disabled the lagfix (create a folder called 'disable-lagfix' in /sdcard/Voodoo)
2) rebooted the phone to disable the voodoo lagfix
3) ran the stock rooted ED1 ODIN file (which I created )
4) took the OTA ED2 update and lost root
5) downloaded the EE4 update file (http://goo.gl/XTDA9) and renamed it 'update.zip' and put it on my sdcard
6) booted into recovery and applied update.zip and then let it boot
7) flashed JTs rooted voodoo kernel and his CWM in ODIN (you should probably delete the disable-lagfix folder after step 6)
NOTE: I didn't wipe at all during this process.
I have EE4 and JTs voodoo kernel and I've confirmed that I have root access.
Now it's time to get rid of this orange and brown crap... again :/
Click to expand...
Click to collapse
are you able to move files onto your sdcard?
DroidXcon said:
are you able to move files onto your sdcard?
Click to expand...
Click to collapse
Yup. What stuff do you want a dump of? Just the system?
The change log
Sounds great but I'm going to wait until it's a full CWM rom.
wynalazca said:
Kind of a tedious process, but here is what I did:
1) I disabled the lagfix (create a folder called 'disable-lagfix' in /sdcard/Voodoo)
2) rebooted the phone to disable the voodoo lagfix
3) ran the stock rooted ED1 ODIN file (which I created )
4) took the OTA ED2 update and lost root
5) downloaded the EE4 update file and renamed it 'update.zip' and put it on my sdcard
6) booted into recovery and applied update.zip and then let it boot
7) flashed JTs rooted voodoo kernel and his CWM in ODIN (you should probably delete the disable-lagfix folder after step 6)
NOTE: I didn't wipe at all during this process.
I have EE4 and JTs voodoo kernel and I've confirmed that I have root access.
Now it's time to get rid of this orange and brown crap... again :/
Click to expand...
Click to collapse
so after the whole 9 yard process of getting it back to stock and then updating all the way up to EE4, when you flashed JT's voodoo kernel, you still maintained all the capabilities of the EE4 update? currently, i believe it seems that flashing a ROM like altered beast (after you've updated to EE4 from stock), makes the functions of the EE4 update disappear?
khanfuze said:
The change log
Sounds great but I'm going to wait until it's a full CWM rom.
Click to expand...
Click to collapse
You may want to reconsider as I don't believe you will get the radio/baseband update if you do not take the OTA update.
Thanks for the info folks. Guess I have some work to do this evening once I get home from work.
EE4, what is it good for?
Anyone have a changelog between ED2 and EE4? Anything mind-blowing?
cshorter said:
Anyone have a changelog between ED2 and EE4? Anything mind-blowing?
Click to expand...
Click to collapse
Dude it's literally like 6 posts above your post.
teddykgb715 said:
Dude it's literally like 6 posts above your post.
Click to expand...
Click to collapse
what fail to read through the thread. /sigh
wynalazca said:
Kind of a tedious process, but here is what I did:
1) I disabled the lagfix (create a folder called 'disable-lagfix' in /sdcard/Voodoo)
2) rebooted the phone to disable the voodoo lagfix
3) ran the stock rooted ED1 ODIN file (which I created )
4) took the OTA ED2 update and lost root
5) downloaded the EE4 update file (http://goo.gl/XTDA9) and renamed it 'update.zip' and put it on my sdcard
6) booted into recovery and applied update.zip and then let it boot
7) flashed JTs rooted voodoo kernel and his CWM in ODIN (you should probably delete the disable-lagfix folder after step 6)
NOTE: I didn't wipe at all during this process.
I have EE4 and JTs voodoo kernel and I've confirmed that I have root access.
Now it's time to get rid of this orange and brown crap... again :/
Click to expand...
Click to collapse
Is booting into stock recovery the same 3 button combo as booting to CWM?
Wynalazca....
The link for the EE4 Update is labeled E2 update. Is this the correct file?
Sent from my voodoo Droid Charge ED2
Well I followed the process outlined above, but I lost root. Oh well.
will2live said:
You may want to reconsider as I don't believe you will get the radio/baseband update if you do not take the OTA update.
Thanks for the info folks. Guess I have some work to do this evening once I get home from work.
Click to expand...
Click to collapse
So a radio cannot be flashed?
khanfuze said:
So a radio cannot be flashed?
Click to expand...
Click to collapse
Currently I don't believe so but I am new to Samsung stuff. However I'm sure it wil lget worked out sooner or later tho.
teddykgb715 said:
Is booting into stock recovery the same 3 button combo as booting to CWM?
Click to expand...
Click to collapse
Yes.
Keighles said:
Wynalazca....
The link for the EE4 Update is labeled E2 update. Is this the correct file?
Sent from my voodoo Droid Charge ED2
Click to expand...
Click to collapse
Yes.

[Q] Can't mount SD card in CWM?

I've searched........extensively.
I've spent hours here with my end goal being to go from EE4 stock to EE4 rooted with Voodoo lagfix (imnuts). When I got the phone originally I had rooted ED1 using the gingersnap method, from there I OTA'ed to EE4, losing root.
Tonight i've ODIN'ed CWM, then flashed voodoo lagfix via CWM. Everything went great, the only problem being that I couldn't get root access for apps, but verified that lagfix was enabled using the Quadrant benchmark app. I'm guessing it was an SU issue. After trying a few suggestions from the board and still being in the same position, I flashed the stock EE4 ROM zip via CWM posted by imnuts, with the idea that i'd re-try the process from the beginning. Everything still great. Reflashed CWM via ODIN, and that worked with no problem. But the problem i'm having is that when I attempt to reflash the Voodoo lagfix zip via CWM, it says that it can't mount the SD card. The SD card is perfectly readable when the phone is booted into the OS. Even manually mounting the SD in CWM yields nothing. I've tried reflashing CWM 3 times, flashes fine, but still getting the SD card mounting error. I could technically stay on EE4 stock, but i'd really like to have root access.
Any assistance anyone could offer would be greatly appreciated.
I forgot to add, if I boot into CWM directly after flashing it, it works, but if I boot the phone into the OS, then attempt to power off and boot into CWM, it boots into the blue Samsung recovery screen. Every time.
I spoke too soon, I guess I hadn't actually tried everything. In any case, if anyone else ever has the problem, the fix went like this:
Flash back to stockrootedED1-20110517.tar.md5 via ODIN > OTA to EE4 > Flash CWM via ODIN > Flash PBJ Voodoo lagfix via CWM and end up at EE4 with root access and a very stealthy Voodoo lagfix kernal (thanks imnuts!).
If anyone is inclined to answer though, there is one question...is it wise to avoid the update that Market is now telling me I need for Superuser? Or is it ok to install said update? TIA
kgbeezr1 said:
If anyone is inclined to answer though, there is one question...is it wise to avoid the update that Market is now telling me I need for Superuser? Or is it ok to install said update? TIA
Click to expand...
Click to collapse
Go ahead and update. No problems with me when I did.
Never hurts to have a TiBu backup of your apps before updating, just in case...

[Q] CWM and stock recovery

Hello -- I'm new to the Charge but have a little experience rooting/flashing ROMS with Motorola devices. At this point all I want is a rooted device and everything else stock (2.2.1 firmware / EE4). To achieve this I placed the Superuser app zipfile onto my sd card, flashed CWM with Odin, booted into recovery and applied the zip update. Everything went smoothly, my device is now rooted and works fine. However, when I boot back into recovery I find that CWM is still installed, I was under the impression that this procedure would overwrite CWM with stock recovery when I rebooted. I don't really mind having CWM, just wondering if the fact that it wasn't overwritten is indicative of some other problem that is likely to bite me in the a** down the road.
Also, if all I have done is rooted and kept the kernel untouched, will I be able to receive the gingerbread OTA when it is released (if ever)? Or will I have to flash back to a stock Froyo ROM?
Thank you thank you thank you in advance.
talbot27 said:
Hello -- I'm new to the Charge but have a little experience rooting/flashing ROMS with Motorola devices. At this point all I want is a rooted device and everything else stock (2.2.1 firmware / EE4). To achieve this I placed the Superuser app zipfile onto my sd card, flashed CWM with Odin, booted into recovery and applied the zip update. Everything went smoothly, my device is now rooted and works fine. However, when I boot back into recovery I find that CWM is still installed, I was under the impression that this procedure would overwrite CWM with stock recovery when I rebooted. I don't really mind having CWM, just wondering if the fact that it wasn't overwritten is indicative of some other problem that is likely to bite me in the a** down the road.
Also, if all I have done is rooted and kept the kernel untouched, will I be able to receive the gingerbread OTA when it is released (if ever)? Or will I have to flash back to a stock Froyo ROM?
Thank you thank you thank you in advance.
Click to expand...
Click to collapse
What zip did you apply IN CWM?
Sounds like you applied a kernel too. Having CWM is not normal if you just flashed the superuser zip.
You will likely need to flash back to stock prior to updating with the GB OTA whenever it comes out.
_____________________________
Bloat frozen EE4 / Stock Kernel
V6 SuperCharger / Loopy Smoothness Tweak
Thank you for the reply.
The only zip I applied was the su-2.3.6.3-efgh-signed file downloaded here.
For CWM I flashed 0817_charge_recovery.tar.md5 found here.
Again I am now rooted but can still boot into CWM. After flashing the CWM file and disconnecting my phone, I initially fat-fingered it trying to boot into recovery and it rebooted. I then powered off and booted successfully into CWM to apply the zip file.
Any thoughts?
Ok, the main difference I see between my config and yours is that I may have used a different version of the superuser package.
The one at the link that you provided is superuser/su-3.0-d-signed.zip.
The one that I used is the su-2.3.6.3-efgh-signed.zip from here
You did start out from stock correct?
What is the kernel version in Settings->About phone->Kernel version?
Actually when I downloaded the Superuser zip file from the site I referenced it was su-2.3.6.3-efgh-signed.zip. This was a few weeks ago -- before version 3.0 was added.
My phone was absolutely stock when I got it 2 weeks ago and I have done no other messing with it. The Kernel version as it reads right now is:
2.6.32.9
[email protected] #1
talbot27 said:
Actually when I downloaded the Superuser zip file from the site I referenced it was su-2.3.6.3-efgh-signed.zip. This was a few weeks ago -- before version 3.0 was added.
My phone was absolutely stock when I got it 2 weeks ago and I have done no other messing with it. The Kernel version as it reads right now is:
2.6.32.9
[email protected] #1
Click to expand...
Click to collapse
Looks like you did the same steps that I did other than your extra boot into CWM. Usually, the stock init will check for the proper recovery, file systems, etc and then "fix" that which isn't right.
I have never seen it not do that before (I have had to reflash CWM several times before due to botching the 3 button bit)
_____________________________
Bloat frozen EE4 / PBJT Voodoo 0730
V6 SuperCharger / Loopy Smoothness Tweak
You cannot apply the OTA if you have CWM recovery. It will fail. Usually you need to have a fully bloated stock rom w/ stock recovery. Root is ok but you will lose it w/ the update
hoppermi said:
You cannot apply the OTA if you have CWM recovery. It will fail. Usually you need to have a fully bloated stock rom w/ stock recovery. Root is ok but you will lose it w/ the update
Click to expand...
Click to collapse
That's kind of why I chose this method to root, thinking that CWM would get overwritten when I rebooted -- but it didn't. Oh well.
talbot27 said:
That's kind of why I chose this method to root, thinking that CWM would get overwritten when I rebooted -- but it didn't. Oh well.
Click to expand...
Click to collapse
Enjoy it. I like CWM much better than stock recovery ;-)
_____________________________
Rooted and Bloat frozen Stock EE4
V6 SuperCharger

Categories

Resources