Related
What is the advantage having a kernel that has Voodoo in it, and other kernels that come with the roms.
Voodoo convert your /data to Ext4 which is a much faster and reliable file system than RFS.
However, because it changes your file system, when you flash anything, I meant ANYTHING, you need to disable it first. Otherwise, you will soft brick.
There's a new lag fix that's rising. It's call zMod, and it convert /data /dbcache and some other path I don't remember. But it is a full phone conversion besides /system. Look it up in the dev forum. I am not sure about all its details.
I am actually reading up on it now. It should be realised later on tonight, or tomorrow. So i should wait for that and don't bother with Voodoo at this point.
PaiPiePia said:
Voodoo convert your /data to Ext4 which is a much faster and reliable file system than RFS.
However, because it changes your file system, when you flash anything, I meant ANYTHING, you need to disable it first. Otherwise, you will soft brick.
There's a new lag fix that's rising. It's call zMod, and it convert /data /dbcache and some other path I don't remember. But it is a full phone conversion besides /system. Look it up in the dev forum. I am not sure about all its details.
Click to expand...
Click to collapse
Ahh thanks for the info.
I was hesitant to root my Vibrant but the lag has gotten Extreme and I am about to give up on Samsung and Froyo. After messing with a PSP for years you get tired of having to hack things, but Samsung really has failed with this file system and I just cant keep letting it slug along.
PaiPiePia said:
Voodoo convert your /data to Ext4 which is a much faster and reliable file system than RFS.
However, because it changes your file system, when you flash anything, I meant ANYTHING, you need to disable it first. Otherwise, you will soft brick.
There's a new lag fix that's rising. It's call zMod, and it convert /data /dbcache and some other path I don't remember. But it is a full phone conversion besides /system. Look it up in the dev forum. I am not sure about all its details.
Click to expand...
Click to collapse
z4mod converts
/data to ext4
/dbdata to ext4
/cache to ext2
And if you want
/system to ext4 or ext2
So it converts all of those. You just have to add system to the update script. You can also choose which ext you want to use by editing the update script. So it could be /data to ext2 if you'd like. My current set up is the one above but /system is ext4 for me.
Sent from my SGH-T959 using XDA App
Im using zmod right now and it works really well. Just make sure you get the zip that converts the file system back to rfs when you flash a new rom.
Samsung Vibrant using Bionix Final w/ z4mod
Anyone having this issue with ANY of the voodoo kernels? It enabled and converted everything to EXT4, but errors out when trying to convert back to RFS. ANy suggestions? Tried the flashable disable voodoo and attempted to disable in CWM, all Try to convert back but fails (see below)
Thanks for your help!
EDIT: Discovered issue was due to a non-existent file, fat.format, in custom builds. Flash the attached zip file, and Voodoo should be able to convert back to RFS.
Hope it helps!
Code:
2010-12-09 06:34:23 filesystem detection on system:
2010-12-09 06:34:24 Ext4 on /dev/block/stl9
2010-12-09 06:34:24 filesystem detection on dbdata:
2010-12-09 06:34:24 Ext4 on /dev/block/stl10
2010-12-09 06:34:24 filesystem detection on cache:
2010-12-09 06:34:24 Ext4 on /dev/block/stl11
2010-12-09 06:34:24 filesystem detection on data:
2010-12-09 06:34:24 Ext4 on /dev/block/mmcblk0p2
2010-12-09 06:34:24 convert cache (/dev/block/stl11) from ext4 to rfs
2010-12-09 06:34:24 ERROR: unable to call fat.format: cancel conversion
2010-12-09 06:34:24 convert dbdata (/dev/block/stl10) from ext4 to rfs
2010-12-09 06:34:24 ERROR: unable to call fat.format: cancel conversion
2010-12-09 06:34:24 convert data (/dev/block/mmcblk0p2) from ext4 to rfs
2010-12-09 06:34:26 ERROR: unable to call fat.format: cancel conversion
2010-12-09 06:34:26 convert system (/dev/block/stl9) from ext4 to rfs
2010-12-09 06:34:29 ERROR: unable to call fat.format: cancel conversion
known issue. supercurio pointed towards a modified fat.format as causing this to happen when running a non-stock rom, as i believe he used the purely stock kernel, and most of us are running modified kernels and roms. not a biggie, just can't disable it, to go back to rfs or flash another rom, you have to odin using the froyo that does not brick method.
Br1cK'd said:
known issue. supercurio pointed towards a modified fat.format as causing this to happen when running a non-stock rom, as i believe he used the purely stock kernel, and most of us are running modified kernels and roms. not a biggie, just can't disable it, to go back to rfs or flash another rom, you have to odin using the froyo that does not brick method.
Click to expand...
Click to collapse
What you mean is to odin back to T959UVJFD with repartition? Will odin wihout disable voodoo birck the phone?
Br1cK'd said:
known issue. supercurio pointed towards a modified fat.format as causing this to happen when running a non-stock rom, as i believe he used the purely stock kernel, and most of us are running modified kernels and roms. not a biggie, just can't disable it, to go back to rfs or flash another rom, you have to odin using the froyo that does not brick method.
Click to expand...
Click to collapse
Mna, was hoping for an easier method. Anyone have the stock fat.format available that can be pushed to /system/bin? Wonder if it would work. Anyone else w/ a better solution? Thanks again for your help!
Odin without disable is fine
I had this same issue. I was able to Odin to eugene's froyo that doesn't brick and then move on to other roms from there. The process was easy.
smartmind said:
What you mean is to odin back to T959UVJFD with repartition? Will odin wihout disable voodoo birck the phone?
Click to expand...
Click to collapse
Odin without disabling voodoo will not brick the phone, if you search for, follow, and use the Froyo That Does Not brick method, that fixes bricks, and will bring you back to stock with rfs.
zimphishmonger said:
Mna, was hoping for an easier method. Anyone have the stock fat.format available that can be pushed to /system/bin? Wonder if it would work. Anyone else w/ a better solution? Thanks again for your help!
Click to expand...
Click to collapse
not sure if pushing the stock fat.format would do it, or cause issues with the rom you're on. thats above my pay grade here. i don't think there is any way to truly remove the voodoo'd partitions and convert them back to rfs, besides the disable method that doesn't work on custom roms, or using odin.
i do think if the voodoo kernel were written into the rom, it may work, but thats just a theory, and i'm no chef.
supercurio did put out the source he used for the voodoo kernel, and i believe also has posted an injection method to inject voodoo into other kernels, however again, above my pay grade (and current knowledge level to actually make it happen)
What is strange is Im using Morific's i9000-based Voodoo kernel, which is made for TW's Nero and I ran into this issue. Guess im stuck on Voodoo for a bit. If anyone would be nice enough to upload a stock fat.format from a JK6\JL1 build, that would be much appreciated (and Ill be able to attempt that idea of pushing a stock fat.format, and attempting to convert back to RFS).
Thanks!
Just odin jk2 with repartion checked. No need for froyo that doesn't brick
Sent from my SGH-T959 using XDA App
zimphishmonger said:
What is strange is Im using Morific's i9000-based Voodoo kernel, which is made for TW's Nero and I ran into this issue. Guess im stuck on Voodoo for a bit. If anyone would be nice enough to upload a stock fat.format from a JK6\JL1 build, that would be much appreciated (and Ill be able to attempt that idea of pushing a stock fat.format, and attempting to convert back to RFS).
Thanks!
Click to expand...
Click to collapse
morific's kernel, was that built from the voodoo 5 beta or the newly released voodoo stable?
again the thought of writing it into a rom was mere speculation on my part. very interesting, i am curious to hear your results of pushing a stock fat.format and attempting a disable, please post your results if you're able to get and push the file.
stephenj37826 said:
Just odin jk2 with repartion checked. No need for froyo that doesn't brick
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
thanks for the heads up, one step that doesn't have to be stepped, i guess old practices die hard.
Okay, fixed it, and I wanted to share w/ everyone else so you can benefit from my PITA.
Voodoo does not like the (or cannot find) fat.format from custom ROMs (like Nero, Macnut, etc). The conversion to EXT4 is fine, but when it comes time to convert back to RFS for whatever reason, it errors out (if you enable debug and look at the log). Ive had suggestions of using ODIN, but I knew there had to be an easier way. Supercurio mentioned that a stock fat.format should fix the issue, and magically it did
pushed a stock fat.format to my /system/bin/, attempted a conversion back to RFS and magic! It worked.
Instructions
Unzip attached file (only for the NON-flashable version, attached to this post)
Push to /system/bin or copy\paste using Root Manager or SUFBS
Attempt conversion back to RFS
Grab some coffee
To ROM Devs, could you please include a PROPER, unmodified fat.format in all your builds to avoid issues like this in the future. Thanks!
Hope this helps!
I have searched the threads, but Eugene has dropped support for this forum, Could anyone kindly tell me where I can find the rom froyo that doesn't brick?
zimphishmonger said:
Okay, fixed it, and I wanted to share to everyone else can benefit from my PITA.
Voodoo does not like the fat.format from custom ROMs (like Nero, Macnut, etc). The conversion to EXT4 is fine, but when it comes time to convert back to RFS for whatever reason, it errors out (if you enable debug and look at the log). Ive had suggestions of using ODIN, but I knew there had to be an easier way. Supercurio mentioned that a stock fat.format should fix the issue, and magically it did
pushed a stock fat.format to my /system/bin/, attempted a conversion back to RFS and magic! It worked.
Instructions
Unzip attached file
Push to /system/bin or copy\paste using Root Manager or SUFBS
Attempt conversion back to RFS
Grab some coffee
To ROM Devs, could you please include a PROPER, unmodified fat.format in all your builds to avoid issues like this in the future. Thanks!
Hope this helps!
Click to expand...
Click to collapse
thanks for being the guinea pig, gonna push this over myself and test it out!
smartmind said:
I have searched the threads, but Eugene has dropped support for this forum, Could anyone kindly tell me where I can find the rom froyo that doesn't brick?
Click to expand...
Click to collapse
http://eb-productions.proboards.com/index.cgi?board=samsungsgs&action=display&thread=8
i would try pushing the fat.format that zimphishmonger posted a few posts back, will be a lot less effort that going with odin.
Hey Zimphishmonger, what version of Nero and which Voodoo kernel were you running when this happened?
Moved of: Samsung Vibrant > Vibrant Android Development
To: Samsung Vibrant > Vibrant Q&A
Please put your questions to: Vibrant Q&A
I can confirm pushing that fat.format zim posted to the /system/bin directory will let you disable voodoo.
Sent from my Black Froyo'd, Voodoo'd Vibrant with a gooey Macnut center
Mods, thanks for moving the thread.
I wanted to clarify, as there seems to be some confusion. I was using the Voodoo-modified CWM kernel from Morfic at 1.4Ghz (the one with the "voodoo" red Clockwork Recovery built-in).
I am using Nero b3, no other lagfixes or tweaks to the file system. The key was the error logs that pointed out that fat.format couldnt be executed, because "Linda" actually says "converting system, converting data, etc" but if you check in terminal or via adb, you will still see your partitions mounted as /ext4 (Voodoo Enabled).
Right after pushing the stock fat.format and attempting a conversion back to RFS, it completed the process, AND gave a time estimate (something it didnt do when it errored out). I hope this helps people.
I have attached a FLASHABLE version of fat.format to make things easier for everyone. It just puts the correct file in /system/bin/ so you dont have to work in terminal or adb
zimphishmonger said:
Okay, fixed it, and I wanted to share to everyone else can benefit from my PITA.
Voodoo does not like the fat.format from custom ROMs (like Nero, Macnut, etc). The conversion to EXT4 is fine, but when it comes time to convert back to RFS for whatever reason, it errors out (if you enable debug and look at the log). Ive had suggestions of using ODIN, but I knew there had to be an easier way. Supercurio mentioned that a stock fat.format should fix the issue, and magically it did
pushed a stock fat.format to my /system/bin/, attempted a conversion back to RFS and magic! It worked.
Instructions
Unzip attached file
Push to /system/bin or copy\paste using Root Manager or SUFBS
Attempt conversion back to RFS
Grab some coffee
To ROM Devs, could you please include a PROPER, unmodified fat.format in all your builds to avoid issues like this in the future. Thanks!
Hope this helps!
Click to expand...
Click to collapse
Thanks, Zimp! This type of solution research is of great value to the community!
BruceElliott said:
Thanks, Zimp! This type of solution research is of great value to the community!
Click to expand...
Click to collapse
NP, glad to share....
OP updated with flashable version (for laziness\ convenience)
zimphishmonger said:
Okay, fixed it, and I wanted to share w/ everyone else so you can benefit from my PITA.
Voodoo does not like the (or cannot find) fat.format from custom ROMs (like Nero, Macnut, etc). The conversion to EXT4 is fine, but when it comes time to convert back to RFS for whatever reason, it errors out (if you enable debug and look at the log). Ive had suggestions of using ODIN, but I knew there had to be an easier way. Supercurio mentioned that a stock fat.format should fix the issue, and magically it did
pushed a stock fat.format to my /system/bin/, attempted a conversion back to RFS and magic! It worked.
Instructions
Unzip attached file (only for the NON-flashable version, attached to this post)
Push to /system/bin or copy\paste using Root Manager or SUFBS
Attempt conversion back to RFS
Grab some coffee
To ROM Devs, could you please include a PROPER, unmodified fat.format in all your builds to avoid issues like this in the future. Thanks!
Hope this helps!
Click to expand...
Click to collapse
How did you try to convert back to RFS and what does RFS mean? Sorry for the noob questions. I have just never ran into this problem but you seemed to have saved my phone. I hope lol
I'd like to dump the /system partition of a stock CDMA (Sprint) Galaxy Tab 7, mounted at /dev/block/stl9 -- but I don't have root. Thus no permission to read
I'm wondering if it would be possible to do an edify script in an update.zip that would:
dd if=/dev/block/stl9 of=/sdcard/image.img
Any help appreciated, thanks!
edit:
I tried the code below in an updater-script, but it failed with a signature error. So I guess this is a no go?
Code:
run_program("/system/bin/dd", "if=/dev/block/stl9 of=/data/local/image.img");
jocala said:
I'd like to dump the /system partition of a stock CDMA (Sprint) Galaxy Tab 7, mounted at /dev/block/stl9 -- but I don't have root. Thus no permission to read
I'm wondering if it would be possible to do an edify script in an update.zip that would:
dd if=/dev/block/stl9 of=/sdcard/image.img
Any help appreciated, thanks!
edit:
I tried the code below in an updater-script, but it failed with a signature error. So I guess this is a no go?
Code:
run_program("/system/bin/dd", "if=/dev/block/stl9 of=/data/local/image.img");
Click to expand...
Click to collapse
Greetings,
While I realize this thread is old. I thought I'd chime in anyway.
If I understand you correctly. Your problem is likely that your Zip file was not signed.
There are several apps available that will sign your zip files for you -- ZipSigner, for example.
Hope this helps you, or others.
Please press the Thanks button, if it did.
--Chris
Hello all,
I'm working on porting CWM to our beloved Galaxy Player 5.0 US edition. I'm loosely following the guide here. I cannot promise that I'll be able to port it successfully, but I can promise that I'll brick my device at least once.
tl;dr : This post says some guy is working on CWM. Woot!
-apapousek
Your sending it to the people are you? And good luck, I only wish I knew how to do this
Apapouseck-
Are you a dev? PM me and give me your email address please. I have a question.
Sent from my Galaxy Nexus using xda premium
azoller1 said:
Your sending it to the people are you? And good luck, I only wish I knew how to do this
Click to expand...
Click to collapse
Of course I'm distributing it. Once I get a working copy, it's being thrown on github, or my own server, and given freely, open source, blah blah blah. No proprietary crap, except maybe enough drivers to get it up and running. But sources for those, too.
cramjammer said:
Apapouseck-
Are you a dev? PM me and give me your email address please. I have a question.
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
Well, technically not a dev. I just like taking software, messing around with it, seeing what it can do. My email address is [email protected]
Can't wait
Sent from my YP-G70 using Xparent Blue Tapatalk
That post, as it says, doesn't cover Samsung devices. It turns out that a while back, Koush made a commit to mkvendor.sh that allows it to operate without an example boot.img.
However, the problem is that there's a remaining bug in mkvendor.sh that TMPDIR is not set in the code path that is triggered when you don't specify boot.img
Right now I'm at a state where CWM starts and runs, but somehow it is treating the tilt sensor as volup/voldn input - so the thing scrolls eternally.
Entropy512 said:
That post, as it says, doesn't cover Samsung devices. It turns out that a while back, Koush made a commit to mkvendor.sh that allows it to operate without an example boot.img.
However, the problem is that there's a remaining bug in mkvendor.sh that TMPDIR is not set in the code path that is triggered when you don't specify boot.img
Right now I'm at a state where CWM starts and runs, but somehow it is treating the tilt sensor as volup/voldn input - so the thing scrolls eternally.
Click to expand...
Click to collapse
Maybe you need the s3c-keypad file to correct this or changing somewhere in the source /dev/input/eventX to another one.
Looks like I need to figure out how to filter out /dev/input/event1, and only pay attention to event4 and event5 (or just event4)
I've got something that seems to be working... Needs a lot more testing. Recovery is important, and if it's broken, can really **** up someone's device.
Also, the way I got it working seems to be a massive hackjob, I need to chat with Koush if there's a better way to do things. Either that or a LOT of CWM porters have done source code modifications without publishing them (Which, while not ideal is allowed for CWM since it is Apache-licensed not GPL.)
Entropy512 said:
I've got something that seems to be working... Needs a lot more testing. Recovery is important, and if it's broken, can really **** up someone's device.
Also, the way I got it working seems to be a massive hackjob, I need to chat with Koush if there's a better way to do things. Either that or a LOT of CWM porters have done source code modifications without publishing them (Which, while not ideal is allowed for CWM since it is Apache-licensed not GPL.)
Click to expand...
Click to collapse
I'm glad you got a clockworkmod which seems to work. Let us know what koush says and if it'll be official support to CWM on our devices.
Yup.
Main things you need to consider when building:
1) The recovery.fstab for Samsung devices isn't appropriate for CWM. One appropriate for CWM has just three entries:
mount point, filesystem, device
The filesystem format options (fourth and fifth columns) seen in stock recovery.fstab will screw up CWM
2) /dev/input/event1 MUST be filtered on SGP5 US devices (and probably international too) - the accelerometer spams keystrokes. This is in ev_init() in minui/events.c
3) Recovery.fstab can't be in /etc - but this path is hardcoded in CWM so you must change the path in roots.c - SGSII seems to use /misc instead of /etc - this is in load_volume_table() in roots.c
Entropy512 said:
Yup.
Main things you need to consider when building:
1) The recovery.fstab for Samsung devices isn't appropriate for CWM. One appropriate for CWM has just three entries:
mount point, filesystem, device
The filesystem format options (fourth and fifth columns) seen in stock recovery.fstab will screw up CWM
2) /dev/input/event1 MUST be filtered on SGP5 US devices (and probably international too) - the accelerometer spams keystrokes. This is in ev_init() in minui/events.c
3) Recovery.fstab can't be in /etc - but this path is hardcoded in CWM so you must change the path in roots.c - SGSII seems to use /misc instead of /etc - this is in load_volume_table() in roots.c
Click to expand...
Click to collapse
Koush put this up at rootzwiki.
apapousek said:
Koush put this up at rootzwiki.
Click to expand...
Click to collapse
I've seen it - if you read it, it's just some "best practices" document that says what you should do after you've managed to compile a working CWM recovery binary - however, I have not seen a single kernel that integrated CWM the way he says, even ones coming from very talented developers (like codeworkx)
Entropy512 said:
I've got something that seems to be working... Needs a lot more testing. Recovery is important, and if it's broken, can really **** up someone's device.
Also, the way I got it working seems to be a massive hackjob, I need to chat with Koush if there's a better way to do things. Either that or a LOT of CWM porters have done source code modifications without publishing them (Which, while not ideal is allowed for CWM since it is Apache-licensed not GPL.)
Click to expand...
Click to collapse
Could you post how you achieved this partial state? I'm busy downloading cm, which is just fun
I'll try to when I have some time... next few days are going to be busy.
Very quick summary:
Need to fix mkvendor.sh so TMPDIR is set when you don't provide a bootimage argument, otherwise the device tree doesn't get created properly
Need to pull recovery.fstab from the device and make it CWM-compatible (Only three columns: mount point, fstype, mount device) by removing all the Samsung-specific cruft - look at the SGSII recovery.fstab for an example of what it should look like
Put in the partition sizes and such in BoardConfig.mk
Need to do the source edits to CWM I mention a few posts above - both are oneliners. I'll try to post a patch when I have the time
Once you build by "make recoveryzip" you need to manually go and copy the recovery binary and all its symlinks into the initramfs - it's in out/target/product/samsung/yourdevicenamehere/ somewhere
dammit...
Something is not working right. Nandroid restores aren't restoring properly... The restores always seem to get corrupted.
****ing RFS... I hate it.
Somehow restored directories are FUBAR:
Code:
ls: ./tts: No such file or directory
ls: ./bin: No such file or directory
ls: ./app: No such file or directory
ls: ./xbin: No such file or directory
ls: ./vendor: No such file or directory
ls: ./firmware: No such file or directory
ls: ./usr: No such file or directory
ls: ./fonts: No such file or directory
ls: ./lib: No such file or directory
ls: ./media: No such file or directory
ls: ./modules: No such file or directory
ls: ./vsc: No such file or directory
-rw-r--r-- 1 root root 2437 Sep 16 21:35 build.prop
drwxr-xr-x 1 root root 0 Jan 9 23:24 cameradata
-rw-r--r-- 1 root root 44 Sep 16 21:35 default.prop
drwxr-xr-x 1 root root 0 Jan 9 23:24 etc
drwxr-xr-x 1 root root 0 Jan 9 23:24 framework
Entropy512 said:
I'll try to when I have some time... next few days are going to be busy.
Very quick summary:
Need to fix mkvendor.sh so TMPDIR is set when you don't provide a bootimage argument, otherwise the device tree doesn't get created properly
Need to pull recovery.fstab from the device and make it CWM-compatible (Only three columns: mount point, fstype, mount device) by removing all the Samsung-specific cruft - look at the SGSII recovery.fstab for an example of what it should look like
Put in the partition sizes and such in BoardConfig.mk
Need to do the source edits to CWM I mention a few posts above - both are oneliners. I'll try to post a patch when I have the time
Once you build by "make recoveryzip" you need to manually go and copy the recovery binary and all its symlinks into the initramfs - it's in out/target/product/samsung/yourdevicenamehere/ somewhere
Click to expand...
Click to collapse
Can you post the patch with the modifications in the source? Thanks!
Attached patch and my current recovery.fstab - remove the .txt extensions
Still not exactly working... RFS formatting seems busted.
Figured out the formatting problems - a few services running from /system were preventing it from unmounting properly.
I did a successful Nandroid restore - things are close now. I may just need to tweak recovery.fstab a bit more to have RFS format/restore/backup fully working.
Voodoo Lagfix - whole other story...
Entropy512 said:
Figured out the formatting problems - a few services running from /system were preventing it from unmounting properly.
I did a successful Nandroid restore - things are close now. I may just need to tweak recovery.fstab a bit more to have RFS format/restore/backup fully working.
Voodoo Lagfix - whole other story...
Click to expand...
Click to collapse
It's a step closer and a BIG advance if we got CWM working on our devices. Really thank you.
Recently purchased Xolo A500, I have been trying to build CWM in builder.clockworkmod.com, but nothing works.
I have tried three times but none works.
Provided with a custom recovery.fstab but still wont work.
So can anyone help me out here.
I can provide the stock recovery.img
BTW, in recovery.fstab provided in builder.clockworkmod.com after it has finished the build the list is
# mount points fstype device [device2]
/boot mtd boot
/cache yaffs2 cache
/data yaffs2 userdata length=-16384
/misc mtd misc
/recovery mtd recovery
/sdcard vfat /dev/block/mmcblk0p1 /dev/block/mmcblk0
/system yaffs2 system
Sdcard location is wrong. It is mmcblk1p1
And mtd file in /proc/ is completely blank so I have no idea from where to get the partitions.
But I have researched enough and understand partitions and after analysing the partitions file I have extracted most of the blocks from the phone.
So now I have dumped the recovery and system partitions.
So I modified the recovery.fstab file like this
# mount points fstype device [device2]
/boot emmc /dev/block/mmcblk0p8
/cache ext4 /dev/block/mmcblk0p15
/data ext4 /dev/block/mmcblk0p13 length=-16384
/misc emmc /dev/block/mmcblk0p19
/recovery emmc /dev/block/mmcblk0p16
/sdcard vfat /dev/block/mmcblk1p1 /dev/block/mmcblk1
/system ext4 /dev/block/mmcblk0p12
/sys_boot vfat /dev/block/mmcblk0p3
/FOTA emmc /dev/block/mmcblk0p17
Has my recovery.fstab got any errors???
The online CWM builder doesn't work???
So Can Anyone Build For Me A CWM Recovery????
did u got any success
even I am waiting for same if you get any sucess please help
Thanks
kank_fraud said:
Recently purchased Xolo A500, I have been trying to build CWM in builder.clockworkmod.com, but nothing works.
I have tried three times but none works.
Provided with a custom recovery.fstab but still wont work.
So can anyone help me out here.
I can provide the stock recovery.img
BTW, in recovery.fstab provided in builder.clockworkmod.com after it has finished the build the list is
# mount points fstype device [device2]
/boot mtd boot
/cache yaffs2 cache
/data yaffs2 userdata length=-16384
/misc mtd misc
/recovery mtd recovery
/sdcard vfat /dev/block/mmcblk0p1 /dev/block/mmcblk0
/system yaffs2 system
Sdcard location is wrong. It is mmcblk1p1
And mtd file in /proc/ is completely blank so I have no idea from where to get the partitions.
But I have researched enough and understand partitions and after analysing the partitions file I have extracted most of the blocks from the phone.
So now I have dumped the recovery and system partitions.
So I modified the recovery.fstab file like this
# mount points fstype device [device2]
/boot mtd boot
/cache yaffs2 /dev/block/mmcblk0p15
/data yaffs2 /dev/block/mmcblk0p13
/misc mtd misc
/recovery mtd /dev/block/mmcblk0p16
/sdcard vfat /dev/block/mmcblk1p1 /dev/block/mmcblk1
/system yaffs2 /dev/block/mmcblk0p12
Out of this I don't have any info abt the /boot partition and /misc partition
Although I think /boot partition can be at /dev/block/mmcblk0p8
I have already dumped that partition but I don't know how to analyse any of these files in a windows machine.
Has my recovery.fstab got any errors???
The online CWM builder doesn't work???
So Can Anyone Build For Me A CWM Recovery????
Click to expand...
Click to collapse
Please help
mithani said:
even I am waiting for same if you get any sucess please help
Thanks
Click to expand...
Click to collapse
Dear Sir,
Please help me, i done rooting of Xolo A500, but i done one mistake yesterday, i have done Factory Reset to it, after dt my device is showing that
not rooted, bt still showing Superuser.apk, n i've tried to root again,but it shows error "system/bin/sh : chmod not found", n my wifi is also not working, please help me Sir..:crying:
If you have been able to root the phone, the first thing you should have done is backup all the partitions necessary.
boot is mmcblk0p8
system is mmcblk0p12
recovery is mmcblk0p16
The first thing I done with the phone I recieved after 5mins is root the phone.
I didn't check it before that
So can you guys tell me how did you find the performance of the phone.
Cuz mine, everything is crashing
Phone, messeging, apps, launcher, etc...
I regret actually buying this phone.
Well the first thing I would say anyone should do is backup there boot, recovery, system partitions and whatever else you want to after you root.
I can upload the boot and recovery partitions but i am very sorry I won't be able to upload my system partition.
I backed it up when I was actually using the phone and my persona; data is there i presume.
I totally forgot how I backed up the partitions right now.
I'll post the method I used once I can remember again.
I gave up on building CWM cuz I have failed so many times that I am completely fed up of it.
I am totally new to working in linux and first I need to figure that out.
Usually you use 'cat proc/mtd' to view the partitions, but its empty in our case.
So use 'cat proc/partitions' instead
But you will only get a list of the partitions without any labels.
Out of that,
/boot mmcblk0p8
/cache mmcblk0p15
/data mmcblk0p13
/misc mmcblk0p19
/recovery mmcblk0p16
/sdcard mmcblk1p1
/system mmcblk0p12
/SYS_boot mmcblk0p3
/FOTA mmcblk0p17
/emmc mmcblk0p18
/persist mmcblk0p14
And lots more partitions are there.
I made an image of the whole NAND chip by using mmcblk0 only.
And also the other partitions individually
You can use this command to back up your partitions.
dd if=/dev/block/mmcblk0p16 of=/sdcard/recovery.img bs=4096
And change the names and partitions accordingly I have mentioned.
It should work.
It only works for rooted phones btw.
I have reset my phone a couple of times after I rooted and I didn't loose root.
And please can anyone confirm me about the performance of the phone.
I am having nightmares personally
I wish I could port Gingerbread instead.
Please ppl, reply.
And if anyone can upload there freshly rooted system.img partition, I'll be glad.
Maybe I recieved a phone with a very unstable ROM
Flash the recovery with
fastboot flash recovery XoloA500_Recovery_Original.img
And before you flash any new recovery, try this command
fastboot boot recovery.img
Replace recovery.img with the name you have for your recovery
If it hangs or reboots, that means the recovery is most probably won't work for you.
If still you want to try, flash it
If it doesn't work, flash the stock back
Same can be done for a boot.img you want to try.
Somebody please use the above method and dump a clean stock rooted system.img.
I used to believe backup is useless, but when you have a device that is not supported by any developer, its better to backup before you mess with it urself.
EDIT: DD command might not work for the system partition
I am not quite sure as I haven't tried to restore the backup
So please be cautious.
I am not to be blamed if any mishap happens to you or your phone.
Currently I am out of station to try anything.
I don't use laptops cuz I find it inconvenient.
Research and post your findings
I have also used this 'http://android.podtwo.com/romdump/' to dump my ROM
Use all available methods and backup your ROM in all the various methods possible.
Afterall no one is supporting our device yet.
Require Xolo A500 system.img Pleaseeee
:crying: Please somebody upload system.img of Xolo A500, please its a request to you friends.....Please :crying:
---------- Post added at 07:20 PM ---------- Previous post was at 07:04 PM ----------
kank_fraud said:
Well the first thing I would say anyone should do is backup there boot, recovery, system partitions and whatever else you want to after you root.
I can upload the boot and recovery partitions but i am very sorry I won't be able to upload my system partition.
I backed it up when I was actually using the phone and my persona; data is there i presume.
I totally forgot how I backed up the partitions right now.
I'll post the method I used once I can remember again.
I gave up on building CWM cuz I have failed so many times that I am completely fed up of it.
I am totally new to working in linux and first I need to figure that out.
Usually you use 'cat proc/mtd' to view the partitions, but its empty in our case.
So use 'cat proc/partitions' instead
But you will only get a list of the partitions without any labels.
Out of that,
/boot mmcblk0p8
/cache mmcblk0p15
/data mmcblk0p13
/misc mmcblk0p19
/recovery mmcblk0p16
/sdcard mmcblk1p1
/system mmcblk0p12
/SYS_boot mmcblk0p3
/FOTA mmcblk0p17
/emmc mmcblk0p18
/persist mmcblk0p14
And lots more partitions are there.
I made an image of the whole NAND chip by using mmcblk0 only.
And also the other partitions individually
You can use this command to back up your partitions.
dd if=/dev/block/mmcblk0p16 of=/sdcard/recovery.img bs=4096
And change the names and partitions accordingly I have mentioned.
It should work.
It only works for rooted phones btw.
I have reset my phone a couple of times after I rooted and I didn't loose root.
And please can anyone confirm me about the performance of the phone.
I am having nightmares personally
I wish I could port Gingerbread instead.
Please ppl, reply.
And if anyone can upload there freshly rooted system.img partition, I'll be glad.
Maybe I recieved a phone with a very unstable ROM
Flash the recovery with
fastboot flash recovery XoloA500_Recovery_Original.img
And before you flash any new recovery, try this command
fastboot boot recovery.img
Replace recovery.img with the name you have for your recovery
If it hangs or reboots, that means the recovery is most probably won't work for you.
If still you want to try, flash it
If it doesn't work, flash the stock back
Same can be done for a boot.img you want to try.
Click to expand...
Click to collapse
------------------------
Sir,
Please upload system.img, bcz nobody is given any response, i'm totally depends on ur help.
please sir, bcz my handset was in service center before some days, n again... my dad will kill me.
Please sir kindly use moborobo for backup ur personal data, Sir Please help me Sir please :crying::crying::crying:
Why don't you people research a day or 2 before hanging your phone to death.
And kid, system.img, how the hell do you plan to restore that???
I have just made a fluke backup, not necessary that it will work.
You need an update.zip, which I don't have and I don't know or currently have any resource to make one.
You shouldn't have messed with things you don't know.
Specially a phone that has no developer support currently.
You better send it for service.
I can't help you.
Neither do I have any source, nor do I have the full knowledge.
I have not tried ever to build a ROM before.
And as we don't have CWM for our phone, I am not willing to risk it just for the sake of fun.
And the moment I return station, I personally am gonna send the phone for service as I am sick and tired of it.
Its a headache to use this phone.
Why don't you people research a day or 2 before hanging your phone to death.
And kid, system.img, how the hell do you plan to restore that???
I have just made a fluke backup, not necessary that it will work.
You need an update.zip, which I don't have and I don't know or currently have any resource to make one.
You shouldn't have messed with things you don't know.
Specially a phone that has no developer support currently.
You better send it for service.
I can't help you.
Neither do I have any source, nor do I have the full knowledge.
I have not tried ever to build a ROM before.
And as we don't have CWM for our phone, I am not willing to risk it just for the sake of fun.
And the moment I return station, I personally am gonna send the phone for service as I am sick and tired of it.
Its a headache to use this phone.
Anyone want to knock yourself out by flashing my stock rooted system.img, knock yourself out
http://www.mediafire.com/?3vs68fl1lpsoc9u
If you break your precious phone, I am not responsible
fastboot flash system system.img
CWM for Xolo A500
Well by luck I found a CWM that boots but it doesn't backup
After a bit of modification, I have been able to successfully create a nandroid backup.
But sadly its chinese and I have no idea on how to translate to english, so please ask someone else.
http://www.mediafire.com/download.php?i40cuwc8dp7xd5y
It is originally for the GreenOrange M2S mobile and it also works with the Videocon A30
After a bit of modification, it seems to be working for our Xolo A500
Its in chinese so figure it out yourself.
For now I all I can say is if you want to backup, do not flash
Use this command 'fastboot boot cwm1.img'
Your phone will boot to CWM and from there, select the 3rd option from the bottom and select the first option you see that has 'SD' written on it.
This will back up your current ROM to your microsd along with the stock recovery, I think
Please reset your phone before you backup
And reset your phone after restore
Now you can try flashing this CWM and see what else you can figure out.
Please post your findings.
If nobody would share, we would all be dumb and mentally handicapped
Seems to me this is CWM 6
Many more options I see which I can't figure out just by guessing
These are newly introduced or what, even I have no Idea.
Well hope somebody now can develop a ROM for our phones
CWM6 has incremental backups, no more system.img
As far as I can say
On the main menu
- reboot
- install zip from sdcard
- wipe data/factory reset
- wipe cache partition
- backup and restore
- mounts and storage
- advanced
My phone's performance is really good, no force close or anything, but my phone is just a rebranded Lava XOLO A500, but I think the ROM is still the same, because inside the phone, I can still signs of XOLO A500, so I'd like to help
EDIT:
Thanks for the partition info! I'll try and help you make CWM for our phone
Are you talking about the Cherry Mobile Burst.
If your ROM is stable, can you use the CWM I posted in here and take a backup and upload it.
I'd like to try.
For partitions unpack stock recovery and find the file recovery.fstab and if you also have like the A500 a recovery_mmc.fstab. This is where the real partition Table is, But its missing the emmc partition. EMMC partition in the A500 is mmcblk0p18
kank_fraud said:
Are you talking about the Cherry Mobile Burst.
If your ROM is stable, can you use the CWM I posted in here and take a backup and upload it.
I'd like to try.
For partitions unpack stock recovery and find the file recovery.fstab and if you also have like the A500 a recovery_mmc.fstab. This is where the real partition Table is, But its missing the emmc partition. EMMC partition in the A500 is mmcblk0p18
Click to expand...
Click to collapse
I flashed this CWM and it works.. I even have my nandroid back up.. now I'm looking for custom rom for xolo a500/cherry mobile burst..
hit thanks!
If anybody want a CWM flashable stock ROM the download this and flash away
http://www.mediafire.com/?u1oxl5suz7tsuz2
Perform a factory reset if you desire
Download this CWM http://www.mediafire.com/download.php?i40cuwc8dp7xd5y
Its chinese so becareful while pushing the buttons.
Its rooted but install superuser from Play Store and update su binary
Has a few build.prop tweaks otherwise a full stock
Break a Leg!!!
kank_fraud said:
If anybody want a CWM flashable stock ROM the download this and flash away
http://www.mediafire.com/?u1oxl5suz7tsuz2
Perform a factory reset if you desire
Download this CWM http://www.mediafire.com/download.php?i40cuwc8dp7xd5y
Its chinese so becareful while pushing the buttons.
Its rooted but install superuser from Play Store and update su binary
Has a few build.prop tweaks otherwise a full stock
Break a Leg!!!
Click to expand...
Click to collapse
hey man!! I need your help.. I tried to make my own splash image using terminal emulator and I ended messing up my /dev/block/
now, my phone doesnt have wifi, the icon is gone. my phone cant detect my sim card, and the signal icon is gone..
is there a way to restore this?? please help!! thanks!!
If you have installed cwm. Then just restore your backups if you have other just download a stock rom for your android phone and simply flash it
Nyk Sharma
Can someone help me build twrp recovery for HTC desire 620 dual sim.
Brand: htc
Model: desire 620 dual sim
Root: no
Able to flash img:yes
S-off:no
Recovery:stock