Here are the Steps I took to convert the data folder to ext 2. I'm sure we can do more folders but I'm unable to write (anyone?) the update scripts.
Start with a fresh install of Team Whiskey's Rom
Goto to the I9000 thread and follow the instruction on uploading a kernel to be repacked.
I selected all the check marks before re packing and downloaded the new kernel.
Download the ext2 update zip from the thread. Rename the zip file to update.zip.
Grab the kernel(tar file) you downloaded from the site and use odin to install.
After booting back up rename the z4mod.ext2.update zip file to update.zip.
Reboot into clockwork and apply update.zip
After booting back up your data file should now be ext2.
To check use terminal emulator our adb and type mount. The data line should now say ext2 instead of rfs.
Note: When I tryed to use the ext2 update zip file without renaming to update.zip it did not work. I continuously recieved SD mount errors.
I can't stress enough to read the topic in the I9000 development thread titled z4mod breaking free from rfs(link below) so you understand what you are doing and the process that is required.
My instruction does not detail that whole process. I'm not responsible for you or what you do by following this brief instruction.
Very Snappy after this mod. Absolutely no issues for me.
Quadrant = 1700
Enjoy!!!
Credit goes to RyanZA and the z4ziggy ; not me.
Source: [z4mod] Breaking free from RFS [Stage II - version 0.3 Alpha - With online patcher!]
Files I used to get this to work.
zImage.tar (The Zimage I used to repack was taken out of Obsidian V2. (DO NOT USE THIS FOR IMAGE FOR ANY OTHER ROM THAN OBSIDIAN V2)
Also, XDA does not allow uploads of tar files so I compressed the tar into a zip format. Make sure you extract this file and use the .tar file within Odin.
Update.zip - This file was downloaded from the I9000 Z4Mod Thread entitled z4mod.ext2.update.zip. All I did was renamed to update.zip which for some reason allows this conversion process to take place.
Sent from my SGH-T959 using XDA App
I would highly suggest posting links to the threads you refer to as well as any files you have available. Good post though, I plan on using this.
Sent from my SGH-T959 using XDA App
Thanks - 1632 Quadrant on Onyx 2.2
Does your kernel have the stock or clockwork recovery? Easy way to check is do adb reboot recovery. If it goes into clockwork then the stock recovery was replaced.
The file you attached is ready to use or do we need to repack?
Greenarcher707 said:
The file you attached is ready to use or do we need to repack?
Click to expand...
Click to collapse
Ready to use.
Sent from my SGH-T959 using XDA App
Ashex1 said:
Does your kernel have the stock or clockwork recovery? Easy way to check is do adb reboot recovery. If it goes into clockwork then the stock recovery was replaced.
Click to expand...
Click to collapse
I'm using cwm. But I could not use "select zip option" you can try it though.
Sent from my SGH-T959 using XDA App
Bugger, from what I know ClockworkMod has some compatibility issues with JK2 unless the version that z4build uses is compatible.
Great, this broke busybox. Now I'm in 2.2 w/o root...
Xencer said:
Great, this broke busybox. Now I'm in 2.2 w/o root...
Click to expand...
Click to collapse
Use Titanium Backup to fix busybox.
Is there one for ext4?
funkyu00 said:
Is there one for ext4?
Click to expand...
Click to collapse
Seconded. It'd be great to get /dbdata, /cache, /system onto ext4 too (I thought that was the main benefit of z4mod?)
jamesyl said:
Seconded. It'd be great to get /dbdata, /cache, /system onto ext4 too (I thought that was the main benefit of z4mod?)
Click to expand...
Click to collapse
Unlikely as the kernel does not support Ext4.
Also, to anyone who has tried this: Is the kernel from the op already patched? I tried throwing it into the the online patcher and the patcher just spit out a message informing me that what I uploaded was already patch. However, when I jump into recovery, I get recovery 2e and not clockwork, which leads me to believe otherwise.
Perhaps odin did not actually install it?
how did u boot into clockwork? 3 button or through rom manger? it doesnt work for me with three button still says can not mount
hoipefully someone adds to the script so it can convert more partitions.
How did you get into Clockwork recovery if you replaced the update.zip file the stock recovery uses to get into it?
I booted through RomManager. It gave the little green Android dude with the download box and got right into recovery. Working great so far.
RobBull69 said:
I booted through RomManager. It gave the little green Android dude with the download box and got right into recovery. Working great so far.
Click to expand...
Click to collapse
Yes, I figured out that the Z4 patch kernel replaces the stock recovery with clockwork.
kangxi said:
How did you get into Clockwork recovery if you replaced the update.zip file the stock recovery uses to get into it?
Click to expand...
Click to collapse
the way this phone is set up has the recovery image packaged with the kernel in the file called zImage. when u use the z4mod to modify that zImage file, the website unpacks the whole zImage file, does its thing with the kernel modding, and now (i say now because this is a newer feature) replaces the standard 2e recovery with clockwork recovery. when you flash the zImage, whether repackaged in a rom or as a tar in odin, the new clockwork recovery is flashed to '/system/bin/recovery' replacing the 2e recovery. i have confirmed this by running the command 'recovery' from terminal while booted after flashing a z4modded kernel. i do not recommend trying to run recovery while booted as the phones display started going crazy.
the problem with having clockwork mod as the primary recovery is the fact that there is a major issue with mounting both the internal sd and external sd (even one at a time as well as both together) as clcokwork mod reports it doesnt recognize device at 'mmcblk0' or 1 when clockworkmod recovery is the primary recovery.
jmart211in said:
the problem with having clockwork mod as the primary recovery is the fact that there is a major issue with mounting both the internal sd and external sd (even one at a time as well as both together) as clcokwork mod reports it doesnt recognize device at 'mmcblk0' or 1 when clockworkmod recovery is the primary recovery.
Click to expand...
Click to collapse
That's why I backed out of it and went back to the stock kernel - that and the fact there was a weird flicker at the top of the screen when booting.
Related
there are a number of problems with the recovery in the just leaked
Froyo ROM.
1. signature checking
2. passing API version 3 to the updater binary
3. forced wipe after installing an update.zip
the attached zip has a 3e recovery modified to disable signature checking
report API version 2 for backwards compatibility with clockwork mod recovery
and disable the forced wipe after installing any update.
I don't know of any reason to run this version over 2e but it
might be useful to someone.
Installing:
1. turn on USB debugging
2. plug into computer
3. run script and follow on screen prompts.
UPDATED 01/23/2011
fixed path error when space in user name
UPDATED 01/22/2011
compressed the rageagainstthecage resource to prevent anti-virus detection
new anti-virus report
http://virscan.org/report/8e83f338fd7b8631c6b0bc0679efbd29.html
the /system file system is full on the newer ROM's
use the attached update.zip to root then install clockwork
Nice
Sent from my SGH-T959 using XDA App
ummmm... what attached zip?
kuhan said:
ummmm... what attached zip?
Click to expand...
Click to collapse
forgot to upload it.
kuhan said:
ummmm... what attached zip?
Click to expand...
Click to collapse
The one attached to the message(?)
fearmonkey said:
The one attached to the message(?)
Click to expand...
Click to collapse
yeah, he attached it after that post lol
how do you use this?
ok i wil bite. how do you use/flash this it cw is not accesible?
rename to update.zip i assume...... i mean thats how u flash everythign thats zip file if u cant get into clockwork.....
you cant flash this you will have to put the files on the internal sdcard
then use root explorer or adb to move the files into place, recovery goes to
/system/bin and the keys to /efs, update.zip is the clockwork recovery and
stays on the sdcard.
when you boot into recovery and choose re-install packages clockwork will
be able to do its thing.
I do like the sig verification but it's a PITA and may disable it, this is a temp
fix until I can finish hacking on recovery there is very little clues as to where
the functions are so it may be a few days.
forgot to mention to you also have to remount /system rw
mount -o rw,remount /dev/block/stl9 /system
Be-ware. Doing so on the ODIN 2E version will break Recovery all together.
Fine to replace on the Stock 2.2 ..
Ps.
Another Awesome Job untermensch
Not to sound like a total noob, but what benefit does this have over the current 2e recovery?
option94 said:
Not to sound like a total noob, but what benefit does this have over the current 2e recovery?
Click to expand...
Click to collapse
I haven't tried just replacing 3e with 2e, I doubt there is any advantage to
3e, to us anyway. but it is always worth while to find ways around these
things.
EDIT:
just replacing 3e with 2e did not work cant find the update.zip
Im suprised more people havent commented. I downloaded the first Stock version of JK2 and i tether so redownloading is not really what i wanted to do...plus i have a Mac so Id have to borrow my buddys pc again...anyway
This workedvgreat! For thise who might need it:
Place all files on the root of SD internal memory card
Copy keys file to /efs
Copy recovery file to /system/bin/ (backup old on first)
Leave all other files on SD internal
Reboot into stock recovery and select Reinstall Packages
itll do its thing and reboot into stock recovery again. From there youre set...just select reinstall packages each time.
Youre a life saver...thank you sir!
TJD319 said:
Im suprised more people havent commented. I downloaded the first Stock version of JK2 and i tether so redownloading is not really what i wanted to do...plus i have a Mac so Id have to borrow my buddys pc again...anyway
This workedvgreat! For thise who might need it:
Place all files on the root of SD internal memory card
Copy keys file to /efs
Copy recovery file to /system/bin/ (backup old on first)
Leave all other files on SD internal
Reboot into stock recovery and select Reinstall Packages
itll do its thing and reboot into stock recovery again. From there youre set...just select reinstall packages each time.
Youre a life saver...thank you sir!
Click to expand...
Click to collapse
thanks...
just updated the first post with a new version.
whats new
Code:
dissables forced post install wipe, dissables signature checking, and reports
API version 2 for backwards compatability with clockwork mod recovery.
Thanks man i rreally appreciate this like i said before. Working perfect snd no issues. Loving being able to CWM again ha. Anyway thank you again sir keep it up!
TJD319 said:
Im suprised more people havent commented. I downloaded the first Stock version of JK2 and i tether so redownloading is not really what i wanted to do...plus i have a Mac so Id have to borrow my buddys pc again...anyway
This workedvgreat! For thise who might need it:
Place all files on the root of SD internal memory card
Copy keys file to /efs
Copy recovery file to /system/bin/ (backup old on first)
Leave all other files on SD internal
Reboot into stock recovery and select Reinstall Packages
itll do its thing and reboot into stock recovery again. From there youre set...just select reinstall packages each time.
Youre a life saver...thank you sir!
Click to expand...
Click to collapse
Thanks untermensch for your work and thanks to the TJD319 for the clear step by step instructions.
Getting can't mount partition after I select a zip file to flash. I can get to cwr fine and it sees the sdcard (internal) fine since I can navigate and select the file I want. The error comes when I try flash. All the files in the zip are in the root of the sd internal, except for recovery and keys that are in the directory /system/bin and /efs respectively. Any advice?
untermensch said:
thanks...
just updated the first post with a new version.
whats new
Code:
dissables forced post install wipe, dissables signature checking, and reports
API version 2 for backwards compatability with clockwork mod recovery.
Click to expand...
Click to collapse
I personally want to say Thanks for Working on this... I Honestly like this version better than the 2e due to being able to wipe the SD-card now..
Thanks for everything.
eugene373 said:
I personally want to say Thanks for Working on this... I Honestly like this version better than the 2e due to being able to wipe the SD-card now..
Thanks for everything.
Click to expand...
Click to collapse
Thanks for the support Eugene....
updated the no sig check version again, too fix the issue that even though the key
is never used, recovery still looked for the existence of the file and would error out if not found.
untermensch said:
Thanks for the support Eugene....
updated the no sig check version again, too fix the issue that even though the key
is never used, recovery still looked for the existence of the file and would error out if not found.
Click to expand...
Click to collapse
Yo man i really appreciate your work. Froyos been great to me Stock 2.2 and this is perfect man. Working flawlessly for me and Im just happy to be able to nandroid.
hey guys right now im using darchstar's godspeed recovery.. but whats the most recommended recovery mode that everyone uses?
My personal favorite is Clockwork Mod Recovery. You can find the latest for our phone in the Andorid Development section, on the first page of the aospGBmod thread. Should be easy to find as it is right on top 99% of the time due to popularity.
DARCH All the way if your running GB then clockwork because I've read people have had problems with Darch's recovery with GB but if your running CM6 then stick with Darch
Root-Hack-Mod-Always™
laie1472 said:
DARCH All the way if your running GB then clockwork because I've read people have had problems with Darch's recovery with GB but if your running CM6 then stick with Darch
Root-Hack-Mod-Always™
Click to expand...
Click to collapse
Anyone Have The Apk. Or Zip File For Darch's Recovery?
Sent from my HERO200 using XDA App
PMGRANDS said:
Anyone Have The Apk. Or Zip File For Darch's Recovery?
Sent from my HERO200 using XDA App
Click to expand...
Click to collapse
I got it off of darch's website but it's been down as far as I know for a little while now.. Luckily I backed it up on my dropbox when I first downloaded it
I attached it so it'll be on XDA for everyone
Download the Darchstar_ra.zip and extract it onto the root of your sdcard.
Boot up into your rom
Open up terminal emulator and enter the following:
Code:
su
flash_image recovery /sdcard/darchdroid_ra.img
reboot
2 questions will this restore previous RA nandroids and also can this do the complete wipe like clockwork?
kyouko said:
I got it off of darch's website but it's been down as far as I know for a little while now.. Luckily I backed it up on my dropbox when I first downloaded it
I attached it so it'll be on XDA for everyone
Download the Darchstar_ra.zip and extract it onto the root of your sdcard.
Boot up into your rom
Open up terminal emulator and enter the following:
Code:
su
flash_image recovery /sdcard/RA-Darchstar.img
reboot
Click to expand...
Click to collapse
sent from my twopointtwo themed hero
thoughtlesskyle said:
2 questions will this restore previous RA nandroids and also can this do the complete wipe like clockwork?
sent from my twopointtwo themed hero
Click to expand...
Click to collapse
I don't see why it would have problems restoring older nandroids, I've never had problems after updating.
And yes, you can wipe data/cache, cache, davlik-cache, battery stats, and rotation settings in the wipe menu.
I currently use ClockworkMod Recovery 2.5.0.1 for recovery mode.
Specs of my Sprint HTC Hero/APA6277 are...
Android version: AOSP
Baseband version 2.42.02.10.29,
Kernel version 2.6.29.6-aospMD [email protected] #1
Mode version: aospMOD-0.9.9.2
Build number: FRG83
I plan on flashing the AOSP GB Mod to my device as soon as a stable version of it becomes available.
kyouko said:
I don't see why it would have problems restoring older nandroids, I've never had problems after updating.
And yes, you can wipe data/cache, cache, davlik-cache, battery stats, and rotation settings in the wipe menu.
Click to expand...
Click to collapse
have you had any issues with wiping and flashing gingerbread because i didnt at first but lately it seems like its not a full wipe, then again im using a really old version of RA
kyouko said:
I got it off of darch's website but it's been down as far as I know for a little while now.. Luckily I backed it up on my dropbox when I first downloaded it
I attached it so it'll be on XDA for everyone
Download the Darchstar_ra.zip and extract it onto the root of your sdcard.
Boot up into your rom
Open up terminal emulator and enter the following:
Code:
su
flash_image recovery /sdcard/RA-Darchstar.img
reboot
Click to expand...
Click to collapse
Thanx A lot Kyouko!!
I Downloaded It....
But I Wanted To Pick Your Brain A Bit, Before I Flashed It.... Lol!
As I'm Sure You Know,
*Rom Manager* Has The Option "Flash Alternate Recovery" Which Switches The Users Recovery From Clockwork, To Amon_Ra, Right?
So I Guess My Question To You Is, What's The Difference Between This Recovery & The Other Two?
Is There More Features??
Oh, One More Thing.... Sorry!!
I Have A **** Load Of Backups From *Rom Manager* Will The Still Be Compatible, Since I Made'em With Clockwork?
Sent from my HERO200 using XDA App
thoughtlesskyle said:
have you had any issues with wiping and flashing gingerbread because i didnt at first but lately it seems like its not a full wipe, then again im using a really old version of RA
Click to expand...
Click to collapse
That issue was fixed in the newer RA versions (which includes this one and godspeed)
There was a problem wiping with the older RA after the cache location got moved in newer rom versions or something along those lines
PMGRANDS said:
As I'm Sure You Know,
*Rom Manager* Has The Option "Flash Alternate Recovery" Which Switches The Users Recovery From Clockwork, To Amon_Ra, Right?
So I Guess My Question To You Is, What's The Difference Between This Recovery & The Other Two?
Is There More Features??
Oh, One More Thing.... Sorry!!
I Have A **** Load Of Backups From *Rom Manager* Will The Still Be Compatible, Since I Made'em With Clockwork?
Click to expand...
Click to collapse
I'm not sure what the "flash alternate recovery" does because I only tried clockwork once and flashed over the recovery using terminal
As for features I took screens of each menu on the recovery
And I don't know what kind of backups rom manager does. If they're structured like nandroids it might work You may have to create a folder named "nandroid" and inside that folder create another and throw the backups in there. It'd be structured something like this:
/sdcard/nandroid/oldbackups/*folders go here*
And worst case scenario if they don't work but you really want all of them back you can just flash clockwork back to restore them.
kyouko said:
That issue was fixed in the newer RA versions (which includes this one and godspeed)
There was a problem wiping with the older RA after the cache location got moved in newer rom versions or something along those lines
I'm not sure what the "flash alternate recovery" does because I only tried clockwork once and flashed over the recovery using terminal
As for features I took screens of each menu on the recovery
And I don't know what kind of backups rom manager does. If they're structured like nandroids it might work You may have to create a folder named "nandroid" and inside that folder create another and throw the backups in there. It'd be structured something like this:
/sdcard/nandroid/oldbackups/*folders go here*
And worst case scenario if they don't work but you really want all of them back you can just flash clockwork back to restore them.
Click to expand...
Click to collapse
Darch's Recovery is an overclocked version of AmonRa with EXT4 Support. See here for more info
kyouko said:
That issue was fixed in the newer RA versions (which includes this one and godspeed)
There was a problem wiping with the older RA after the cache location got moved in newer rom versions or something along those lines
I'm not sure what the "flash alternate recovery" does because I only tried clockwork once and flashed over the recovery using terminal
As for features I took screens of each menu on the recovery
And I don't know what kind of backups rom manager does. If they're structured like nandroids it might work You may have to create a folder named "nandroid" and inside that folder create another and throw the backups in there. It'd be structured something like this:
/sdcard/nandroid/oldbackups/*folders go here*
And worst case scenario if they don't work but you really want all of them back you can just flash clockwork back to restore them.
Click to expand...
Click to collapse
Thanx For The Screenshots,
Now I'm Curious! And I Already Like The Way It Looks Better Than Clockwork! But To Be Honest Im A Little Nervous About Using ADB. Or Terminal Emulator!
Is It Easy/Hard?
I Heard You Can Brick Your Phone If You Enter A Command Wrong, Is That True?
Sent from my HERO200 using XDA App
PMGRANDS said:
Thanx For The Screenshots,
Now I'm Curious! And I Already Like The Way It Looks Better Than Clockwork! But To Be Honest Im A Little Nervous About Using ADB. Or Terminal Emulator!
Is It Easy/Hard?
I Heard You Can Brick Your Phone If You Enter A Command Wrong, Is That True?
Sent from my HERO200 using XDA App
Click to expand...
Click to collapse
As long as you don't put "flash_image (BOOT or any other partition here)" you should be fine.
If you input it incorrectly it won't flash,
example: flashimage recovery /sdcard/darchdroid_ra.img
How to flash it via ADB:
Code:
adb shell
su
flash_image recovery /sdcard/darchdroid_ra.img
reboot
kyouko said:
As long as you don't put "flash_image (BOOT or any other partition here)" you should be fine.
If you input it incorrectly it won't flash,
example: flashimage recovery /sdcard/darchdroid_ra.img
How to flash it via ADB:
Code:
adb shell
su
flash_image recovery /sdcard/darchdroid_ra.img
reboot
Click to expand...
Click to collapse
followed the code lines for terminal emu and adb both times got Flash_img: not found even tried entering Darchstar_ra.img same error
thoughtlesskyle said:
followed the code lines for terminal emu and adb both times got Flash_img: not found even tried entering Darchstar_ra.img same error
Click to expand...
Click to collapse
Weird.. Do this for me, open up terminal emulator and type:
Code:
su
flash_image
you should get a return line saying:
Code:
usage: flash_image partition file.img
*see attached picture for example*
Make sure you're inputing it exactly the way I had it in the previous post - underscores and all. If the recovery.img name is different make sure whatever you type is exactly what the img is called.
If it's not in the /sdcard/ directory enter the correct one.
Example) /sdcard/downloads/oldrecovery.img
On my second attached picture you can see that the command worked, but since I already have that recovery flashed it aborts.
thoughtlesskyle said:
have you had any issues with wiping and flashing gingerbread because i didnt at first but lately it seems like its not a full wipe, then again im using a really old version of RA
Click to expand...
Click to collapse
I'd just use CW for Gingerbread, RA doesn't wipe boot or system I believe.
Does anyone know if you are able to Wipe Data/cache/dalvik from adb shell?
just making a script to automate the process.
anyone know the commands?
thanks
I just rooted and got everything up and running again. I have ClockworkMod installed and I am trying to do a backup now, but I get an error. Here is what it says during/after the backup:
SD Card Space free: 7568MB
.
Backing up Boot.....
.
Backing up Recovery.....
.
E:FAILED to mount /recovery ( Block device required )
.
Can't mount /recovery!
.
END
What could this mean and what can I do to fix it ? I dont even see a /recovery mount point.
Please advise !
Did you do it using IOMonster's root pack and install CWM using his zip? If so, you can try flashing CWM through ROM Manager. I'm having the exact same issue and nothing is working for me, but most seem to be able to flash CWM through RM and it's fixed.
eyecrispy said:
Did you do it using IOMonster's root pack and install CWM using his zip? If so, you can try flashing CWM through ROM Manager. I'm having the exact same issue and nothing is working for me, but most seem to be able to flash CWM through RM and it's fixed.
Click to expand...
Click to collapse
Yes I used his CWM zip. I have tried via Rom Manager and get the same result's. The only thing that is different is that IOMonster's recovery is using 3.0.0.5 and When I installed Rom Manager it downloaded 3.0.0.7 but then when I tried a backup via CWM the recovery changed back from 3.0.0.7 to 3.0.0.5 Not sure what thats about, but I dont see any reason why it cant find or mount the restore dir.
Im lost :O( I need to make a ROM backup !
I am in the exact same place you are. IOMonster says he's uploading a new version of his root pack tonight that will include a new flashable CWM. I'm hoping it'll work for me. If not, i'm going back to stock and rooting with autonooter to see if that fixes it. Did you root with IOMonster's root.zip? Or just his CWM?
eyecrispy said:
I am in the exact same place you are. IOMonster says he's uploading a new version of his root pack tonight that will include a new flashable CWM. I'm hoping it'll work for me. If not, i'm going back to stock and rooting with autonooter to see if that fixes it. Did you root with IOMonster's root.zip? Or just his CWM?
Click to expand...
Click to collapse
I rooted with IOMonster's root.zip I also used his gapps and block1.1 script's ... then I installed his CWM.
I wish someone can help us ! please let me know if you find a solution.
Hi. I successfully installed CWM and flashed stock+voodoo UCKB1 kernel (as CWM indicates voodoo lag-fix is active and Quadrant score is 1528). However, I have a few n00b questions before I jack up my successful install... here's the story:
i897 Captivate
Build: FROYO.UCKB1
Kernel: was 2.6.32.9, now 2.6.32.9 with voodoo lag-fix
Updated to official 2.2 UCKB1 on 2/25, then rooted with SuperOneClick v1.7. All perfect... regularly could access Titanium BU, RootExplorer, etc so SU permission was enabled. I've been wanted to add the voodoo lag-fix, so followed various threads regarding 3e recovery + lagfix. I tried running an "Install.bat" file which was supposed to put a modified 3e recovery file on my phone... but that failed during ADB transfer (script stated "update failed!"). So quickly bailed out and went another route: using RootExplorer, I renamed my stock 3e recovery to "xxx_recovery" and copied the "modified 3e" recovery to /system/bin (renaming it to "recovery"). Rebooted, then rebooted into Recovery hoping to see a "modified 3e" recovery... but alas, was still the blue KB1 3e Recovery. (not sure if I was supposed to see anything different between stock 3e and modified 3e recovery). I think at this point I selected "Reinstall Packages" and rebooted... but still had blue 3e recovery. In any event, I pushed forward... installed ROM Manager... flashed ClockworkMod Recovery, rebooted... then rebooted again into Recovery. I now had the GREEN CWM... so 3e must have been modified to allow CWM recovery to be installed. Then, copied "stock+voodoo-Froyo-I897-UCKB1-unsigned-update.zip" to /sdcard root. Shut phone off, removed external SD, and did the 3-button boot into Recovery. Got the GREEN CWM, and did the "Apply zip from SD card", selected the voodoo zip, and applied. When I rebooted, Voodoo was enabled and life was good... However, now for my questions:
1) It seems I now have 2 CWM recoveries... GREEN v2.5.1.2 which shows in ROM Manager, and RED v2.5.1.3 when I now boot to recovery via 3-button method. So question is: should ROM Manager show v2.5.1.2 or v2.5.1.3 ? Since I have voodoo lag-fix active, should I only reboot to recovery via 3-button and never using ROM Manager?
2) I noticed I now have an "update.zip" file in /sdcard root. I'm not sure which event put it there. Was it when I hit "reinstall packages" from BLUE 3e recovery... or was this created by the CWM voodoo lag-fix flash?
3) Is there a way to determine what this generic "update.zip" file is and should I remove it? (as it might be the modified 3e recovery I no longer need since I have RED CWM).
Sorry for being long-winded... just want to capture all the steps I performed.
Thanks!
Anyone who has Voodoo Lag-Fix have 2 CWM recoveries?
bumping.... where's the love?
Anyone who has installed Voodoo lag-fix on 2.2... if so, in summary have 3 questions:
1. do you have multiple CWM Recoveries? GREEN v2.5.1.2 vis ROM Manager and RED v2.5.1.3 via voodoo kernel.
2. Can/should I delete v2.5.1.2?
3. How can I tell what the "update.zip" package is on my /sdcard root? Did ROM Manager CWM v2.5.1.2 put it there? Can/should it be removed?
Thx.
leave update.zip on the sdcard. its useful for if you go back to a stock kernel that does not have recovery
stop using ROM manager
Pirateghost said:
leave update.zip on the sdcard. its useful for if you go back to a stock kernel that does not have recovery
stop using ROM manager
Click to expand...
Click to collapse
+1
10 char
if I was you I would odin back to stock and then unstall a custom rom much better than official 2.2 just keep your update zip. Its real easy to flash recovery pm me if you need help
sent from cappy with di11i rom
Thanks for the replies. Question: if I keep the "update.zip" on root, then sometime later while in CWM recovery I inadvertently hit "apply sdcard: update.zip", what will happen? I think this update.zip is the ROM Manager CWM v2.5.1.2 (Green Recovery). Will it overwrite my CWM v2.5.1.3 (RED Recovery) which I got from Voodoo kernel? Don't want to jack this up as I need RED for voodoo lag fix. Thx.
DoctorQMM said:
Thanks for the replies. Question: if I keep the "update.zip" on root, then sometime later while in CWM recovery I inadvertently hit "apply sdcard: update.zip", what will happen? I think this update.zip is the ROM Manager CWM v2.5.1.2 (Green Recovery). Will it overwrite my CWM v2.5.1.3 (RED Recovery) which I got from Voodoo kernel? Don't want to jack this up as I need RED for voodoo lag fix. Thx.
Click to expand...
Click to collapse
CWM makes it a tad difficult to "inadvertently" select a feature. Just like when performing brain science or rocket surgery you need to be very careful with your tool of choice.
Even if you do re-flash the update.zip file - no big deal - you already have the contents on your device. No harm, no foul.
2.5.12 will not be overwritten by 2.5.1.3. Supercurio designed the Red version to run with not overwrite it.
Peace-
Liv33viL
Liv33viL said:
Even if you do re-flash the update.zip file - no big deal - you already have the contents on your device. No harm, no foul.
2.5.12 will not be overwritten by 2.5.1.3. Supercurio designed the Red version to run with not overwrite it.
Peace-
Liv33viL
Click to expand...
Click to collapse
Good to know... thanks for your input!
Hello
I've tried installing guestekrnL on WIUI. When installing guestekrnL, the only thing I've ticked extra that was other than defaults was:
"Activate init.d functionality and convert file system to EXT4?
- yes
select if init.d is not working yet or if you don't know"
Well, after reboot WIUI was screaming that my sd card is broken and format may help. It formatted it, but it still didn't work. So I've rebooted to recovery via option in power dialog in order to restore old firmware. However there's a problem now: CWM Touch says that it can't write logs to /cache. Mounting /cache, /data or /emmc from recovery doesn't work, only /system and /sdcard are mounting correctly. I've tried BackToExt3 with no luck. I've tried wiping it many times, with no luck. My phone only boots now to CWM. I can't flash stock via APX mode, because I have broken USB port in my phone. What can I do?
Does restoring a backup, flashing a zip file or wiping work?
Ok, I was searching for almost whole hour now and it seems it's a problem with partition table. Fixing can be done via zip, but I need some dumps. First one from "cat /proc/mounts" and second from "parted".
Here's the zip for nook color if someone wants to do that for me: http://forum.xda-developers.com/showthread.php?t=1759558
exinepl said:
Ok, I was searching for almost whole hour now and it seems it's a problem with partition table. Fixing can be done via zip, but I need some dumps. First one from "cat /proc/mounts" and second from "parted".
Here's the zip for nook color if someone wants to do that for me: http://forum.xda-developers.com/showthread.php?t=1759558
Click to expand...
Click to collapse
the Touch CWM might be the issue......most of the times it is found as the source of some unknown issues for some or intermittent issues.
I use the non-touch one always
Hope it helps
Well, how do I flash new recovery from CWM using zip then?
exinepl said:
Well, how do I flash new recovery from CWM using zip then?
Click to expand...
Click to collapse
check for the CWM thread by Rusty....you have the instructions and process in it.
THERE YOU GO>>>SEE HERE
Hope it helps
Unfortunately, it needs USB. I need to flash it via existing recovery.
Mounting problems occur on some zips using touch recovery . Change cwm to non touch 5.0.2.8. But hey, did you flash a stock kernel on wiui ? you need another kernel, like etana, symbiosis.....or just use the one shipped with rom