Database Info

[Q] Flashing images that are already EXT4 [NOT WORKING]

Is there anything restricting the images we flash to be in using the Samsung's RFS? Shouldn't we be able to pre-package everything in ext4 and then just flash it to the phone so we get a stock image in whatever format we want?
I've been doing some reading and I found a ruby script that converts RFS images into VFAT images, then it's just a matter of converting it to EXT4 and we've got ourselves a ROM that's fast from the getgo. It does take its sweet time though...
Just a thought. I'm hoping a few of the devs see this so we can get something good going!
EDIT:
Started messing with the RFS files in linux. Apparently nowadays they're just plain on VFAT so you can mount them using a loop device.
Code:
mount factoryfs.rfs mydirectory
Then you can just grab and edit as you please, as to trying to make this into ext4, I noticed you get a LOT of overhead (some 30 megabytes for an empty filesystem) so the images would grow considerably, but I think the phones would have enough space on em. Now I just have to test under to see if the phone will like getting an ext4 image flashed to it instead of the RFS images...

Alright just got done messing with this. I managed to successfully flash an EXT4 factoryfs image, BUT, it didn't work right. Tried running commands on the ADB shell and nothing except CD worked... Not even ls. Got a toolbox not found error. Not sure exactly what went wrong even though I used honk's ext4 kernel. Worth a shot though.

Thanks for testing it out at least. You got a few steps out the way.

Please post questions in general. That way it doesn't clutter this section.
sent from my not so stock SGS4G

Who wants to be a tester? (Valhalla Black OneClick)

I just repackaged Raver's latest valhalla black as a heimdall oneclick file. Should automatically convert your /system partition ext4 too!
If you want to test this out for me I'd be grateful. I already flashed it myself and it worked out fine. This should help whoever is having issues (most likely caused by not formatting their partitions before the flash)
TESTING DONE. Download link gone.

I'll try it later on,
but just a quick question though:
in the:"About the ROM" section it is listed as:
"Official KJ6 With bhudven's Kernel
Gingerbread 2.3.6"(which I guess comes from the firmware.xml file) - is that on purpose?
isn't it suppose to be Valhalla Black or something
Again 10x
Alon

Oh yes, that's not on purpose, I left it in the firmware.xml file and forgot to edit it, but I did place the correct (valhalla black) files into the oneclick.

FBis251 said:
I just repackaged Raver's latest valhalla black as a heimdall oneclick file. Should automatically convert your /system partition ext4 too!
If you want to test this out for me I'd be grateful. I already flashed it myself and it worked out fine. This should help whoever is having issues (most likely caused by not formatting their partitions before the flash)
http://sourceforge.net/projects/teamacid/files/fb/roms/one_clicks/valhalla-black-rc3.2-One-Click.jar
Click to expand...
Click to collapse
I'll give it a go this morning.
As soon as I update my TB backups and run a nand.
I'm not having any issues at the moment, well, none related to the phone/rom anyway... so not sure I'm a good test subject...
Did you add the gps fix in? or does it need flashed after?

Well it's just a repackaged version of 3.2, so it should work exactly the same, just need to make sure it installs correctly on other people's phones.
Nope, no gps fix in there.

Downloading now; will let you know as soon as I'm done.
-- Update --
I rebooted my phone into CWM & disabled voodoo
booted into download mode & ran the one-click without issue
Phone rebooted itself and immediately Linda began converting partitions
Linda said "Voodoo lagfix now disabled"
Standard recovery appeared:
* Successfully installed package.
* -- Deleting files...
* Successfully deleted files.
* -- Updating filesystem...
* verifying the filesystem. please wait.
* already updated filesystem. finished
* Successfully updated filesystem.
* -- Wiping cache...
* Formatting cache...
* E:format_volume: rfs format failed on /dev/block/stl11
* Cache wipe failed.
* -- Appling Multi-CSC...
* Installing Multi-CSC
* Can't access to '/system/csc/TMB/system/'.
* Successfully applied multi-CSC.
Selected 'reboot system now'
Waiting on it to boot, then waiting some more
-- Update #2 --
When it booted and it came up to the Google setup, I had no data connection. I had to set up wi-fi to get through the process. Seems the APN was missing.
-- Update #3 --
/system is mounted rfs, not ext4.
Maybe I did something goofy to make all of that happen? I've never had my APN disappear before.

stephen_w said:
Downloading now; will let you know as soon as I'm done.
Click to expand...
Click to collapse
Yea... what he said...
---------- Post added at 12:48 PM ---------- Previous post was at 12:33 PM ----------
FBis251 said:
Well it's just a repackaged version of 3.2, so it should work exactly the same, just need to make sure it installs correctly on other people's phones.
Nope, no gps fix in there.
Click to expand...
Click to collapse
Ran okay, heard Linda zapping things...
then it booted into stock recovery
got the following:
installing update...
Successfully installed package.
--Deleting files..
Successfully deleted files.
--Updating filesystem
E:failed to mount /data (invalid argument)
E:discard_filesystem_for_rfs:Can't mount /data
--Wiping cache...
Formatting /cache...
E:format_volume: rfs format failed on /dev/block/stl11
Cache wipe failed.
Appling Multi-CSC (Note that's not a typo on my part, it says Appling)
Installing Multi-CSC
Can't access to '/system/csc/TMB/system'.
Successfully applied multi-CSC
Click to expand...
Click to collapse
Rebooting now, it didn't boot itself.
Update: No data connection
Booted back to CWM recovery, Mounts were UUUU -couldn't change them
W

Hmm odd. Well thanks for testing I'll take down the link since Raver posted the latest version now. I'll probably look into this again once he releases a final.

FBis251 said:
Hmm odd. Well thanks for testing I'll take down the link since Raver posted the latest version now. I'll probably look into this again once he releases a final.
Click to expand...
Click to collapse
No problem... I ended up jumping through a few hoops and just flashed rc3.3.
Was going to make sure it was good and then rerun the one-click...
This is the first one-click I have had any issues with, didn't get a chance to log any of it though... I'm at the office, so limited on what I can get my hands on directly...

Core618 said:
No problem... I ended up jumping through a few hoops and just flashed rc3.3.
Was going to make sure it was good and then rerun the one-click...
This is the first one-click I have had any issues with, didn't get a chance to log any of it though... I'm at the office, so limited on what I can get my hands on directly...
Click to expand...
Click to collapse
I kinda threw it together. I dumped the /system partition and threw that in with the rest of the KJ6 stock Odin files into a Heimdall package. Technically it should work even though the partition itself was dumped as ext4 not the traditional rfs that is used in Odin packages.

FBis251 said:
I kinda threw it together. I dumped the /system partition and threw that in with the rest of the KJ6 stock Odin files into a Heimdall package. Technically it should work even though the partition itself was dumped as ext4 not the traditional rfs that is used in Odin packages.
Click to expand...
Click to collapse
Weirdness. I appreciate your continuing efforts into making things easier to do and manage with this phone.

FBis251 said:
I kinda threw it together. I dumped the /system partition and threw that in with the rest of the KJ6 stock Odin files into a Heimdall package. Technically it should work even though the partition itself was dumped as ext4 not the traditional rfs that is used in Odin packages.
Click to expand...
Click to collapse
why didn't you factory reset, clear cache, clear dalvik, and dump all of it?
Sent from my SGH-T959V using XDA App

Bassmanjames said:
why didn't you factory reset, clear cache, clear dalvik, and dump all of it?
Sent from my SGH-T959V using XDA App
Click to expand...
Click to collapse
There's no need to dump /cache or /data since they get formatted when you do a factory reset anyway. It's only the /system partition that matters.

FBis251 said:
There's no need to dump /cache or /data since they get formatted when you do a factory reset anyway. It's only the /system partition that matters.
Click to expand...
Click to collapse
Exactly my point. couldn't you use the "empty image". I have extracted the stock images for data and cache and both contain files. I would think that with all the tw dependencies that raver has removed it is somehow interfering.
Sent from my SGH-T959V using XDA App

Bassmanjames said:
Exactly my point. couldn't you use the "empty image". I have extracted the stock images for data and cache and both contain files. I would think that with all the tw dependencies that raver has removed it is somehow interfering.
Sent from my SGH-T959V using XDA App
Click to expand...
Click to collapse
I'll keep that in mind when I make the next one. Gonna wait until a stable version is out. Very possible to make it happen though since we could just fill up the partitions with a huge file from /dev/zero just to zero out the blocks and make the images compress well.

I have a personal backup that I made and I converted to rfs before the dump. If I use it and my system was rfs it auto converts to ext4 on first boot. I think it is because the kernel is set to ext4 by default. Something else to keep in mind.
Sent from my SGH-T959V using XDA App

Bassmanjames said:
I have a personal backup that I made and I converted to rfs before the dump. If I use it and my system was rfs it auto converts to ext4 on first boot. I think it is because the kernel is set to ext4 by default. Something else to keep in mind.
Sent from my SGH-T959V using XDA App
Click to expand...
Click to collapse
There's a a directory /sdcard/Voodoo/ that has files that tells the kernel to convert.

[Q] CWM unable to mount /system

This has been mentioned elsewhere, even by me but I think it has fallen through the cracks. It may be an unrelated problem but when trying to use CWM to do a backup it fails saying that /system cannot be mounted.
The issue it may be related to is that CWM on boot installed via either method fails to stick past the initial reboot. It looks to me that it is restoring an image on start up each time undoing any changes. It must not be changing everything because the root sticks. I have made sure init.d support has been installed. The phone is an AT&T branded MB865, has been rooted and is running stock 2.3.6 firmware.
Any pointers will be appreciated and I come from an embedded Linux background so I'm willing to help out, but why re-invent the wheel if this has already been solved.

cdlees said:
This has been mentioned elsewhere, even by me but I think it has fallen through the cracks. It may be an unrelated problem but when trying to use CWM to do a backup it fails saying that /system cannot be mounted.
The issue it may be related to is that CWM on boot installed via either method fails to stick past the initial reboot. It looks to me that it is restoring an image on start up each time undoing any changes. It must not be changing everything because the root sticks. I have made sure init.d support has been installed. The phone is an AT&T branded MB865, has been rooted and is running stock 2.3.6 firmware.
Any pointers will be appreciated and I come from an embedded Linux background so I'm willing to help out, but why re-invent the wheel if this has already been solved.
Click to expand...
Click to collapse
Update your busybox .

I had thought of that, running BusyBox 1.20, 1.20.1 fails to install. As 1.20 is fairly recent I doubt this is the problem. The initial install of CWM via Power Boost works, so busybox is installed correctly. An old version of busy box wouldn't explain the not being able to mount /system as as far as I know it isn't used by CWM for this purpose, but I could be wrong. But it could explain the CWM not sticking problem.

Further investigation shows that the system partition does not change between doing a PowerBoost CWM install and after a reboot meaning that there is nothing screwy going on like the boot sequence over writing files in system so that CWM isn't persistent. Can anyone enlighten me on the boot sequence so I can take a look to see if anything is getting over written?
This of course gets me no closer on why CWM can't mount system but it is just one of two problems.

cdlees said:
Further investigation shows that the system partition does not change between doing a PowerBoost CWM install and after a reboot meaning that there is nothing screwy going on like the boot sequence over writing files in system so that CWM isn't persistent. Can anyone enlighten me on the boot sequence so I can take a look to see if anything is getting over written?
This of course gets me no closer on why CWM can't mount system but it is just one of two problems.
Click to expand...
Click to collapse
Have you tried "fix permissions" in cwm?.then reboot and see if it still gives you that error when you go back into cwm
Sent from my MB865 using xda premium

I'm pretty sure I had already tried all that, but just to be sure I did it all again, here is what happened
PowerBoost CWM install
Reboot into CWM
CWM Fix permissions
CWM recovery restart
CWM backup
Failed due to not being able to mount /system
Power cycled, didn't boot into CWM
Since permissions may have changed once CWM Fix permissions had been run
PowerBoost CWM install
Reboot
Enters CWM
Reboot
Didn't boot into CWM
Surely I'm not the only one seeing this problem?

cdlees said:
I'm pretty sure I had already tried all that, but just to be sure I did it all again, here is what happened
PowerBoost CWM install
Reboot into CWM
CWM Fix permissions
CWM recovery restart
CWM backup
Failed due to not being able to mount /system
Power cycled, didn't boot into CWM
Since permissions may have changed once CWM Fix permissions had been run
PowerBoost CWM install
Reboot
Enters CWM
Reboot
Didn't boot into CWM
Surely I'm not the only one seeing this problem?
Click to expand...
Click to collapse
Well once u reboot your phone it goes into cwm. When u reboot from cwm its suppose to go into rom not cwm again.
Sent from my MB865 using xda premium

Have u tried manually mounting system in cwm and see what happens?
Also what version of busybox do u have installed? . Should be 19.4. Nothing higher.
Sent from my MB865 using xda premium

rdavisct said:
Well once u reboot your phone it goes into cwm. When u reboot from cwm its suppose to go into rom not cwm again.
Click to expand...
Click to collapse
I realise this but I was under the impression that if the phone is power cycled or reboot from Android then it will go into CWM on restart.
Still doesn't explain the inability to mount /system

rdavisct said:
Have u tried manually mounting system in cwm and see what happens?
Also what version of busybox do u have installed? . Should be 19.4. Nothing higher.
Click to expand...
Click to collapse
I'm running BusyBox 1.19.4. I just tried to manually mount /system from CWM, same problem. Just to make sure that mounting works I mounted a few other things that were not already mounted.

cdlees said:
I'm running BusyBox 1.19.4. I just tried to manually mount /system from CWM, same problem. Just to make sure that mounting works I mounted a few other things that were not already mounted.
Click to expand...
Click to collapse
Id say rsd flash 2.3.5 . Root. Install atrix bootstrapper. And see if problem persists.
Sent from my MB865 using xda premium

Ok, reflashed back to 2.3.5, rooted, Bootstraped, tried to mount /system from CWM, no luck, same error. Tried to install CWM on boot using the zip from CWM, didn't seem to work. Tried the fix permissions script from CWM, still doesn't work.
There is something up with this phone, is it possible that Motorola has decided to be extra evil.

I till haven't gotten very far with this but I have some more information on what may be the issue. I can get it to update the system partition by flashing a zip. I decided to give it a go with SCV6 as I was sure I'd be able to recover if it failed. It flashed just fine but on reboot it dropped out to the fastboot screen. This is where I decided to get creative, I mounted the system.img file from from the stock fimware, deleted its contents and replaced it with what is in the SCV6 zip system directory, after all this is what CWM will be doing as far as I could tell. I then flashed this file using moto-fastboot. It failed on boot dropping out at fastboot again.
Running out of time for the day I decide to just restore it back to stock, I have a Linux script to automate the process, on completion, same failure. What had happened is I had mounted the system.img file to look inside and then unmounted it, and this may have changed a signature or checksum in the filesystem so it failed to boot. Re-extracting the system.img file and flashing again worked fine.
Are there different versions of the bootloader that do different things? Mine just being a total pain and not allowing much at all.

Just realised the install script puts in a whole pile of symlinks, not having them would cause a boot failure on creating the image the way I did. It will be possible to create an image with said symlinks.
This though fails to explain while mounting and then unmounting the system.img makes it fail.

I may just be talking to myself here but I have some relevant information relating to the original problem of not being able to mount /system which is why flashing doesn't work as well as the flashing scripts don't actually check to see if the system partition is mounted, they just assume it is.
In CWM if you try to mount /system then look at the log it says
mount: mounting /dev/block/mmcblk1p20 on /system failed: Invalid argument
Now the question is, what is the mount line it is trying to execute and which argument is invalid? Can someone with a working phone go into CWM, unmount /system if its mounted by default and then mount it, look at the log and tell me what it says regarding the mounting of system.
Here is the really interesting part, once the phone has booted and checking what is actually mounted on /system its /dev/block/mmcblk1p21, so CWM is trying to mount the wrong partition

I worked out the problem, I was using the Razr bootstrap which obviously mounts a different partition as system, I had followed some instructions that I read somewhere that the Razr version worked and gave a link to said package. Once I swapped to the atrix 2 version it all works, I'll attempt to install SCV6 tomorrow night when I have some time.

can't mount /system!
[/COLOR]
cdlees said:
I till haven't gotten very far with this but I have some more information on what may be the issue. I can get it to update the system partition by flashing a zip. I decided to give it a go with SCV6 as I was sure I'd be able to recover if it failed. It flashed just fine but on reboot it dropped out to the fastboot screen. This is where I decided to get creative, I mounted the system.img file from from the stock fimware, deleted its contents and replaced it with what is in the SCV6 zip system directory, after all this is what CWM will be doing as far as I could tell. I then flashed this file using moto-fastboot. It failed on boot dropping out at fastboot again.
Running out of time for the day I decide to just restore it back to stock, I have a Linux script to automate the process, on completion, same failure. What had happened is I had mounted the system.img file to look inside and then unmounted it, and this may have changed a signature or checksum in the filesystem so it failed to boot. Re-extracting the system.img file and flashing again worked fine.
Are there different versions of the bootloader that do different things? Mine just being a total pain and not allowing much at all.
Click to expand...
Click to collapse
Can you please post the link/s, i have the same problem as you

[RECOVERY] CWM TOUCH (Touch is working)

Hi Guys
I got CWM Touch 5.8.1.5 working on Infuse complete with working touch. Someone will have to build into kernel until we get flashable recovery going. I should mention that recovery.fstab mounts to mtd block so this probably won't work on bml roms. I might do a bml version if enough people want it, but someone would have to get me a bml mount list as I am running jellybean.
Installation
Flash the zip the same way you would any rom zip or you can rename zip to update.zip and place at /sdcard/, then in cwm apply /sdcard/update.zip. Will disappear on reboot, so keep the zip. Still trying to figure out how to flash permanently.
Bugs
10/2 Build: All of the mounts that can work now do. JT confirmed for me that the ones that don't work at this point aren't mountable (boot, recovery, and efs). Will try to take those out of the menu later, but for now this is ready to go. Same install process for now. ROM dev could build this build into a rom's boot.img now though it all works.
Download
CWM Touch 5.8.1.5 10/2 Build

blscallions said:
Hi Guys
I got CWM Touch 5.8.1.5 working on Infuse complete with working touch. Will upload in a few minutes as flashable zip. Someone will have to build into kernel until we get flashable recovery going.
Installation
Flash the zip the same way you would any rom zip or you can rename zip to update.zip and place at /sdcard/, then in cwm apply /sdcard/update.zip. Will disappear on reboot, so keep the zip. Still trying to figure out how to flash permanently.
Bugs
A few of the mounts are not working right now, need to update recovery.fstab to point to correct mount. Will upload new version once I get mounts fixed.
Download
CWM Touch 5.8.1.5
Click to expand...
Click to collapse
man thats super cool!!!!!!
could you use the TWRP injection script that those guys have going?
it strips out the old recovery from the kernel image and injects a new one...
also 5.x works fine with jb right?

hazard66 said:
man thats super cool!!!!!!
could you use the TWRP injection script that those guys have going?
it strips out the old recovery from the kernel image and injects a new one...
also 5.x works fine with jb right?
Click to expand...
Click to collapse
twrp doesn't work with jellybean so i can't use that injection method. MG and I are working on fixing it though. Yes 5.x is working with jellybean, but like I mentioned under bugs some mounts aren't acting right, such as /emmc and /efs, not sure why, might not even be necessary cause I was able to flash paranoid without those mounted.

blscallions said:
twrp doesn't work with jellybean so i can't use that injection method. MG and I are working on fixing it though. Yes 5.x is working with jellybean, but like I mentioned under bugs some mounts aren't acting right, such as /emmc and /efs, not sure why, might not even be necessary cause I was able to flash paranoid without those mounted.
Click to expand...
Click to collapse
iirc /emmc never mounted right on the infuse in 5.x -- at least, i have not experienced it
i remember installing 6 and being like "wow i can see my sdcard!"
maybe other ppl have had different experiences heh
twrp is pretty nice ive never used cwm touch on the ol infuser

hazard66 said:
iirc /emmc never mounted right on the infuse in 5.x -- at least, i have not experienced it
i remember installing 6 and being like "wow i can see my sdcard!"
maybe other ppl have had different experiences heh
twrp is pretty nice ive never used cwm touch on the ol infuser
Click to expand...
Click to collapse
Dude! Thank You, you just reminded me why i can't find /emmc in mounts. i took out my external card out when i flashed paranoid. still you might be right about 5.x problem with external, but at least now i can find the mount location lol. almost had a dumb blonde moment

blscallions said:
Dude! Thank You, you just reminded me why i can't find /emmc in mounts. i took out my external card out when i flashed paranoid. still you might be right about 5.x problem with external, but at least now i can find the mount location lol. almost had a dumb blonde moment
Click to expand...
Click to collapse
ahh found your problems. maybe.... all the mtd blocks are yaff2 not ext4, change that. only /data is ext4 on mtd. also some modification of recovery might be needed to get the /emmc working since it is a symlink on the infuse. the actual mount point for emmc is /storage/sdcard1 the volume name is emmc and the device path can be a number of different things (linux is weird)... this will take some experimentation or research to fix. the /emmc symlink just points anything looking for /emmc to /storage/sdcard1.
if you use the right device path for the external sdcard you might still have a prblem using /emmc as a mount pont since it is a special file not an empty folder.. if you change the mount point i don't know if the recovery menu will know to look for it. if there is a config file for the menu it may also need editing.
edit, i don't see any other config files, so you might maybe need the source code to fix the external sdcard mounting.... but maybe just maybe it simply uses recovery.fstab to find the list of mount points to list in the menu in the first place. all i can say is try changing /emmc to /storage/scard1 and see if the menu changes.

Dani897 said:
ahh found your problems. maybe.... all the mtd blocks are yaff2 not ext4, change that. only /data is ext4 on mtd. also some modification of recovery might be needed to get the /emmc working since it is a symlink on the infuse. the actual mount point for emmc is /storage/sdcard1 the volume name is emmc and the device path can be a number of different things (linux is weird)... this will take some experimentation or research to fix. the /emmc symlink just points anything looking for /emmc to /storage/sdcard1.
if you use the right device path for the external sdcard you might still have a prblem using /emmc as a mount pont since it is a special file not an empty folder.. if you change the mount point i don't know if the recovery menu will know to look for it. if there is a config file for the menu it may also need editing.
edit, i don't see any other config files, so you might maybe need the source code to fix the external sdcard mounting.... but maybe just maybe it simply uses recovery.fstab to find the list of mount points to list in the menu in the first place. all i can say is try changing /emmc to /storage/scard1 and see if the menu changes.
Click to expand...
Click to collapse
yeah in my most current build (not the one on here, not complete yet so not uploaded) I have changed the blocks to yaffs2 except data is ext4. gonna work on emmc today and might take your advice and contact jt about efs problem.
recovery.fstab is in the etc/ folder in the zip. i've got most of the mounts working now. just the two bad ones now so i am getting there.
i have been playing with the idea of using flash_image to flash recovery.img, but i'm not sure yet where recovery.img is located in our mtd structure. i posted that question in Q&A. i don't think the old method of flashing recovery is ever gonna work on mtd. no matter how you pull boot.img from the system cwm still says that boot.img does not contain ramdisk.
Edit: I tried mounting emmc to /storage/sdcard1, and that's not the right path. internal sdcard mounts to /dev/block/mmcblk0p1 and that path i'm sure works (tested myself) so i think maybe external might use one of these mmcblk too? Put my external back in this morning gonna run mount command and see if she shows me where she hides.

Yahtzee! Found /emmc, proper mount should point to /dev/block/mmcblk1p1. All I'm lacking now is /efs, which does show in mount command but when it tries to mount it says it cant find the block to mount it, perhaps this is a permision problem? I'm also lacking the option to mount boot and recovery, but i don't think those options are gonna be doable on infuse, not much good to us anyway since we cant write directly to those blocks that i know of.

Just a tidbit of info on mounts... you've got your terminology mixed up. /emmc doesn't point to /dev/whatever, it's the other way around. The /dev/whatever file is actually a device/block file which means it's just a fake file that allows you to access the hardware on the system via kernel drivers. You then mount that to a path on the system with a file system type (ie, through a fs driver) to store/access the data.
Just in case you were mixed up (might help you with any future problems, etc...)!

10/2 Build
Got a new build out there for you. All the mounts that can work do. Will try to take boot, recovery, and efs out of the mounts menu later. Download link in OP has been updated. For now work for me has stopped; hard-bricked my infuse, no power or download mode. Tried a recovery install procedure that was a bad idea. Hopefully ATT will replace.

blscallions said:
Hi Guys
I got CWM Touch 5.8.1.5 working on Infuse complete with working touch. Someone will have to build into kernel until we get flashable recovery going. I should mention that recovery.fstab mounts to mtd block so this probably won't work on bml roms. I might do a bml version if enough people want it, but someone would have to get me a bml mount list as I am running jellybean.
Installation
Flash the zip the same way you would any rom zip or you can rename zip to update.zip and place at /sdcard/, then in cwm apply /sdcard/update.zip. Will disappear on reboot, so keep the zip. Still trying to figure out how to flash permanently.
Bugs
10/2 Build: All of the mounts that can work now do. JT confirmed for me that the ones that don't work at this point aren't mountable (boot, recovery, and efs). Will try to take those out of the menu later, but for now this is ready to go. Same install process for now. ROM dev could build this build into a rom's boot.img now though it all works.
Download
CWM Touch 5.8.1.5 10/2 Build
Click to expand...
Click to collapse
Prolly gonna sound like a complete ass but....when I click on the link it shows a series of folders....as if I unzipped the file. So where do I download the actual .zip file from?
---------- Post added at 10:19 PM ---------- Previous post was at 09:40 PM ----------
I'm an idiot.....nvm thank you

KFlannigan5 said:
Prolly gonna sound like a complete ass but....when I click on the link it shows a series of folders....as if I unzipped the file. So where do I download the actual .zip file from?
---------- Post added at 10:19 PM ---------- Previous post was at 09:40 PM ----------
I'm an idiot.....nvm thank you
Click to expand...
Click to collapse
Docs is confusing that way... in a "desktop" browser, top left corner will be a file menu type thing where you can select download. Not very noticeable at all... don't feel dumb, I've been using computers for over 20 years and had the same wtf moment you had - took me a while to notice it!

j.smith said:
Docs is confusing that way... in a "desktop" browser, top left corner will be a file menu type thing where you can select download. Not very noticeable at all... don't feel dumb, I've been using computers for over 20 years and had the same wtf moment you had - took me a while to notice it!
Click to expand...
Click to collapse
Yeah I saw the "file" button .......the recovery works awesome. Wishing for a permanent solution. Anyone know of a good kernel? Takes me forever to charge and the battery life is atrocious. Thanks in advance.

There is s big bug with cache not being wipeable
Sent from my SGH-I997 using XDA Premium HD app

nobody wants to update this. :~(
<TheJackofClubs> http://forum.xda-developers.com/showthread.php?t=1908609 <- add touch to cwm <3
<Araemo> TheJackofClubs: no
<TheJackofClubs> aw
<Araemo>

Question about recovery in twrp.

Have a question about the mount settings in my recovery. I know that target box means it is mounted/RW and untagged is unmounted/Ro. But my /system partition keeps getting set to Ro and when i need to flash things it needs to be on RW. Is that bc my device is Samsung and thereforth has protected bootloader set? I'v been reading trough script files and think i can adjust some of them so they mount as RW instead of Ro. I know that /system is set to RO bc of safe against accidental alteration/removement. But it would be much easier to flash or install updates/programs/apps/etc that way. Hope anyone can give some advice for me.
P.S. i use the ROM Toolbox Lite Scripter bc it has a lot standard scripts already and changing them is easy. And u can just copy that script into an Terminal Emulgator thats rooted and then run it to alter/install it so u can read back whats been changed?

A. Nieveen said:
Have a question about the mount settings in my recovery. I know that target box means it is mounted/RW and untagged is unmounted/Ro. But my /system partition keeps getting set to Ro and when i need to flash things it needs to be on RW. Is that bc my device is Samsung and thereforth has protected bootloader set? I'v been reading trough script files and think i can adjust some of them so they mount as RW instead of Ro. I know that /system is set to RO bc of safe against accidental alteration/removement. But it would be much easier to flash or install updates/programs/apps/etc that way. Hope anyone can give some advice for me.
P.S. i use the ROM Toolbox Lite Scripter bc it has a lot standard scripts already and changing them is easy. And u can just copy that script into an Terminal Emulgator thats rooted and then run it to alter/install it so u can read back whats been changed
Click to expand...
Click to collapse
Usually, the ROM updater script will mount/unmount system. I do not know if that is the case here.