Related
I have been trying like crazy to get voodoo injected into our stock kernel. Anyone else out there having problems like I am?
Nopcodex90 said:
I have been trying like crazy to get voodoo injected into our stock kernel. Anyone else out there having problems like I am?
Click to expand...
Click to collapse
I know gtg465x is making the attempt. Maybe he will chime in or send him a PM.
keitht said:
I know gtg465x is making the attempt. Maybe he will chime in or send him a PM.
Click to expand...
Click to collapse
I talked with Francois on it, he said he was working on something, but that was like 2-3 weeks ago... so not sure if he is continuing on it or what.... haven't pinged him again...
Figured give him awhile, but he was asking me to beta test once he has something..... just hopefully soon....
slider2828 said:
I talked with Francois on it, he said he was working on something, but that was like 2-3 weeks ago... so not sure if he is continuing on it or what.... haven't pinged him again...
Figured give him awhile, but he was asking me to beta test once he has something..... just hopefully soon....
Click to expand...
Click to collapse
Just a suggestion, but if everyone working on it would communicate with each other, we would get a more quality product in a shorter amount of time. Hopefully that is already being done behind the scenes.
keitht said:
Just a suggestion, but if everyone working on it would communicate with each other, we would get a more quality product in a shorter amount of time. Hopefully that is already being done behind the scenes.
Click to expand...
Click to collapse
Crossing my fingers too! I guess you can go to voodoo's github to get the source code.... GTG is definitely awesome though!
I built a voodoo kernel and it boots up fine, everything works, and it even creates the voodoo folder on the sd card, but it won't convert the partitions to ext4 on boot. The voodoo log is telling me df can't be run from system so there must be /system corruption. On Galaxy S devices that meant /system probably got corrupted by one of the old broken ultimate lagfix kernels, but obviously I haven't flashed an ultimate lagfix kernel so I don't know what the deal is.
gtg465x said:
I built a voodoo kernel and it boots up fine, everything works, and it even creates the voodoo folder on the sd card, but it won't convert the partitions to ext4 on boot. The voodoo log is telling me df can't be run from system so there must be /system corruption. On Galaxy S devices that meant /system probably got corrupted by one of the old broken ultimate lagfix kernels, but obviously I haven't flashed an ultimate lagfix kernel so I don't know what the deal is.
Click to expand...
Click to collapse
exciting though! Keep it up!
Voodoo
I am getting the same errors on my voodoo kernel. The only way I can get it to work, is by going in manually formating /system ext4 and moving files over. Boot it and then it works fine. I dunno.
are you guys building from source? if you are where did you get the initramfs?
Dani897 said:
are you guys building from source? if you are where did you get the initramfs?
Click to expand...
Click to collapse
Yes, pulled initramfs out of zImage from phone.
gtg465x said:
Yes, pulled initramfs out of zImage from phone.
Click to expand...
Click to collapse
ahh i couldnt find any information on how to do that. would it be too much trouble to explain?
Dani897 said:
ahh i couldnt find any information on how to do that. would it be too much trouble to explain?
Click to expand...
Click to collapse
This script works: http://forum.xda-developers.com/wiki/index.php?title=Extract_initramfs_from_zImage
that's what i like about this being a small comunity. you ask a question and get an answer. thanks!
This one works as well: https://github.com/mistadman/Extract-Kernel-Initramfs
Voodoo
Hey guys, between me and GTG well have this soon. We have the Voodoo Ramdisks in place, what we are both running into is RFS corruption. Due to the fact samsung mounts the /system with check=no option it gets corrupted. Hence why after about 3 or 4 days your phone is as slow as windows ME. I have been able to go in , manually format /system with Ext4 and then reboot. Voodoo converts and works flawlessly.( Yes nanabobo,my phone is now faster then yours)
But for the masses it wont work out like that. I also have been able to OC our phones pretty damn fast. If anyone gets a hold of SuperCurio, tell him to re-upload his RFS fixer scripts . Thats what we really need for the "masses".
I really miss ext4, it made my epic so much faster. It would be great for the infuse. I know its only a matter of time, and i wish that time was now....lol.
curses, Git's down for the moment, or I would also look into the voodoo script. There should be something in the script that we can mod.
Will hop over to #infuse4g after watching this week's Blue Exorcist....
Nopcodex90 said:
Hey guys, between me and GTG well have this soon. We have the Voodoo Ramdisks in place, what we are both running into is RFS corruption. Due to the fact samsung mounts the /system with check=no option it gets corrupted. Hence why after about 3 or 4 days your phone is as slow as windows ME. I have been able to go in , manually format /system with Ext4 and then reboot. Voodoo converts and works flawlessly.( Yes nanabobo,my phone is now faster then yours)
But for the masses it wont work out like that. I also have been able to OC our phones pretty damn fast. If anyone gets a hold of SuperCurio, tell him to re-upload his RFS fixer scripts . Thats what we really need for the "masses".
Click to expand...
Click to collapse
I sent him email.... crossing fingers he will respond!
Nopcodex90 said:
Hey guys, between me and GTG well have this soon. We have the Voodoo Ramdisks in place, what we are both running into is RFS corruption. Due to the fact samsung mounts the /system with check=no option it gets corrupted. Hence why after about 3 or 4 days your phone is as slow as windows ME. I have been able to go in , manually format /system with Ext4 and then reboot. Voodoo converts and works flawlessly.( Yes nanabobo,my phone is now faster then yours)
But for the masses it wont work out like that. I also have been able to OC our phones pretty damn fast. If anyone gets a hold of SuperCurio, tell him to re-upload his RFS fixer scripts . Thats what we really need for the "masses".
Click to expand...
Click to collapse
Thanks you both will be the dinamic duo of the Infuse
Sent from my SAMSUNG-SGH-I997 using XDA Premium App
Ok, figured out that the reason for the error is not because our /system partition is corrupt. The problem is just that the voodoo scripts are failing to mount anything. I will have to put some kind of debug print in the script to see exactly why it can't mount anything.
I am very close to completing my ext2 ROM... benchmarks are going very well...
I might as well add ext3 and ext4 support... But first ext2!
To do
testing
tweaking
Complete
searching everything what I might need
Feel free to donate to speed up the work!
ext2 is FULLY WORKING GUYS!!!!
Any chance to be beta tester?
Actually hmmm let me think
Do you know the right buttons to press to go into recovery mode and/or download mode ???
The process so far is:
1. Install CWM Recovery
2. reboot into CWM Recovery
3. Now connect phone to computer
4. adb shell (as superuser)
5. ... converting cache and data commands ...
6. Now put phone straight into Download mode
7. Connect phone to computer. And flash my tar file
Then your system will act very strange on first start... Like artifacts... But after that everything runs perfectly normal. I believe the system has to rebuild or something like that
Benchmark:
Stock rfs: 1085
ext2 data and ext2 cache: 1645
I am still working on the system partition though... Since that one has to be backed up and everything has to be put back afterwards. And loads of crappy permissions.
But what I got so far works... It's still very buggy. Specially the ext2 being detected as ext4 after a datawipe... So if you want ext2 you can't do a datawipe... Personally I don't find it worth the hassle... But still I am doing my best.
I hope someone more capable will take my job over or point me in the right directions. I have been asking guru's around here in hope they would help me. But they do get tired.
Bugs:
- Booting into CWM and mounting /cache and /data there will make the partitions being detected as ext4... However this is not an issue at this point but still it shouldn't be happening... It may cause problems
Features needed:
- An easier conversion process. This could be done if someone helps me with my init.rc file to be able to detect the filesystem and mount it using correct filesystem
Very nice progress so far m8. whis i could help but as i said except testing i aint of much use so far
You will be !I promise! The only disadvantage is I don't know what will happen in many cases. I have to work those things out first to make sure nothing bad can happen...
I need to make one change to the boot.img related to the file system check. After that I can release it to be used for normal rfs systems as well.
Any progress made recently? Really looking forward to this!
Sent from my GT-S5660 using xda premium
I am stuck...
I need to know how to mod recovery.img
+
+
in the boot.img:
- I need to do something in the init.rc file
- sbin/init.sh ???
- sbin/pre-init.sh ???
Let's say the ext2 works, but it's a long process and not so handy to get it work... Let's say you need to flash 3-4 times in odin before you have it work properly.
I am trying to make it simple. I need a professional developer to clear some things up for me... But they seem to look down or even to think I am not worth explaining... I know it's much to explain. But I want to learn.
If someone wants to help me that's more than welcome
djjonastybe said:
I am stuck...
I need to know how to mod recovery.img
+
+
in the boot.img:
- I need to do something in the init.rc file
- sbin/init.sh ???
- sbin/pre-init.sh ???
Let's say the ext2 works, but it's a long process and not so handy to get it work... Let's say you need to flash 3-4 times in odin before you have it work properly.
I am trying to make it simple. I need a professional developer to clear some things up for me... But they seem to look down or even to think I am not worth explaining... I know it's much to explain. But I want to learn.
If someone wants to help me that's more than welcome
Click to expand...
Click to collapse
Check your PM
You can use the files from galaxy ace roms with ext4 there is a big chance that this will help you out!
Project seems death! I will try to make everything ext2 tomorrow or so!
Sent from my GT-S5660 using xda premium
Does anyone have tips on extracting RFS images on a Linux box?
So far everything I've found on extracting RFS images indicated to either:
1) Use MagicISO/PowerISO - these are proprietary Windows tools, I'd prefer not to have to reboot or move to another machine
2) Mount it as a VFAT filesystem - this didn't work for me last time I tried it
Any other suggestions? It's not something I usually bother with as I'm almost always doing kernel work or working with already-extracted userland filesystems, but with all of the AT&T Gingerbread leaks coming out I'd like to be able to analyze these without waiting for someone to CWM it up.
Mount it as loop.
http://forum.xda-developers.com/showthread.php?t=751827
LinuxBozo said:
Mount it as loop.
http://forum.xda-developers.com/showthread.php?t=751827
Click to expand...
Click to collapse
That's what I tried before (see 2) above) - didn't work. Tried both autodetect and forcing vfat.
Maybe just that particular RFS image (was one of the ones from gtg's Ultimate Unbrick packages) was wonky... Will try again tonight with I3/I4.
Works Here (TM) ;-)
LinuxBozo said:
Works Here (TM) ;-)
Click to expand...
Click to collapse
Weird. Whatever RFS image I was trying to mess with last time around must've been mangled... UCKI3 mounts fine.
i missed this thread, i was messing with the kk1 leak and wanted to create a rooted package without flashing it rooting and dumping it, problem is i cant set permissions when i mount the image to a loop. i can read and write but i cant change the permissions of su to 6755 or antthin other than 0755 it just says operation not permitted. i tried to fdisk the loop and turn off dos compatibility mode which seemed to cause issues on my flash drive, though it might work but it wont stick.
any suggestions from the local gurus? im sure the fix is simple but from how much time ive spent on it it might make more sense to flash it root it and dd the rooted /system partition
Dani897 said:
i missed this thread, i was messing with the kk1 leak and wanted to create a rooted package without flashing it rooting and dumping it, problem is i cant set permissions when i mount the image to a loop. i can read and write but i cant change the permissions of su to 6755 or antthin other than 0755 it just says operation not permitted. i tried to fdisk the loop and turn off dos compatibility mode which seemed to cause issues on my flash drive, though it might work but it wont stick.
any suggestions from the local gurus? im sure the fix is simple but from how much time ive spent on it it might make more sense to flash it root it and dd the rooted /system partition
Click to expand...
Click to collapse
You can't really do anything but read only operations from vanilla linux because while RFS is VFAT under the covers, there are other things to it. Writing to it once mounted as loop will cause havoc. You would have to actually have RFS driver in the kernel to do anything other than read operations. Which means, mounting as loop on your phone, or getting RFS into your own linux kernel (not gonna happen, since it's closed source)
LinuxBozo said:
You can't really do anything but read only operations from vanilla linux because while RFS is VFAT under the covers, there are other things to it. Writing to it once mounted as loop will cause havoc. You would have to actually have RFS driver in the kernel to do anything other than read operations. Which means, mounting as loop on your phone, or getting RFS into your own linux kernel (not gonna happen, since it's closed source)
Click to expand...
Click to collapse
Ok so if I wanted to release an Odin package it would mean dumping it from my phone then. Gotcha!
Thanks.
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.
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>