How to Voodoo
As long as you have the new CWM for all ROM's these instructions should work for 2.1 AND 2.2.
New CWM for all ROM's:
http://forum.xda-developers.com/showthread.php?t=942021
Thank JT1134 for this.
Make sure to thank Adrynalyne, Jt1134, times_infinity, imnuts and nemesis2all for the great kernels we have.
If you flash a ROM that has a voodoo kernel built in to the .zip, flash that ROM and skip to step 5.
I thought it was time I stopped saying “Stay away from voodoo!!!!”. While I still think noobs should stay away, at least until they gain experience and confidence with their phones, I no longer hate voodoo. In fact I will admit, very grudgingly, I do notice a little, not much, but a little extra zip in my phone. It actually isn’t that hard to figure out as long as you follow some simple rules:
1. Don’t panic. I seriously doubt you can screw up your phone worse than I have screwed up mine. Everything is un-screw-able.
2. Don’t flash a non-voodoo kernel over a voodoo kernel. If you do stupid crap will happen to your phone. It won’t boot for one, and you will break CWM.
Voodoo is a kernel replacement. Our phones use a proprietary RFS file system built as a legacy FAT, adding indexing and POSIX permission on the internal 2gb SD card. There is nothing wrong with RFS, but it’s slow. From what I understand it indexes everything. This takes time, causing lag. Voodoo reformats the internal SD card with standard Linux EXT4. EXT4 is a faster. This filing system is what is reffered to as the lag fix.
Voodoo also makes the screen sharper, and has some improvemnets to sound quality as well. These have nothing to do with the lag fix portion of voodoo.
Note: Voodoo screen and sound enhancements are now available in Froyo as we have the source code.
To utilize Voodoo sound enhancement you need to download Voodoo Control from the market.
To utilize BLN you need to download BLN control from the market.
Voodoo color is passive, however you the brightness needs to be set to 100% and auto brightness turned off.
This is step by step what I did. I will assume you have an intermediate understanding of how to root and mess around with your phone. You will need to know how to use Odin, flash back to stock, hot to boot into recovery and how to put your phone into download mode. If you are not completely comfortable with ALL of these procedures, DO NOT TRY THIS!!
1. I wanted to start with out of the box new. So I formatted my SD card and flashed back to stock. I flashed to stock DJ05, but this should work for DL09 and DI01 as well DL30 and EB01.
NOTE: It is not nessicarry to start from stock, it jsut the place i picked so all steps would be covered.
2. Now that we are back to stock we need to root. I used the “Gunnermike53 lazy root” method. I dropped Superdark ROM v1 for DJ05 and Test 6 Low voltage voodoo from Adrynalyne (you can use whatever ROM and kernel you want) on my SD Card. I put the phone into download mode and flashed CWM Red.
NOTE: If you already have the new RED CWM it is not nessicarry to flash CWM again.
3. Boot into recovery. You will go straight to CWM Red, no blue. Clear your data and cache. Then select “install zip from sdcard”. Select “choose zip from sdcard”. Select your ROM then hit yes. When it’s finished you will be back at the second menu page again. If you restart your phone at this point you will have a fully rooted phone, with a stock kernel. But don’t reboot.
4. Next you will select “choose zip from sdcard”, select your kernel and then yes.
5. When it’s done, press the menu soft button on the bottom left of the phone. This will take you back to the first page.
Go down and select voodoo. Then you will select “enable lag fix”.
6. When that’s done, press the soft menu button and then reboot.
7. Wait.
8. Wait.
9. Wait.
10. Seriously, it takes anywhere 2 to 15 minutes. During this time you will hear a female robot (or perhaps, a female android ) talking.
11. Once the phone restarts you are done!
It’s that easy. The key to all the simple-ness is Red CWM.
Thanks to Adrynalyne for the kernel and bringing our attention to the Red CWM, and to Thatdudebutch for superdark, and I don’t know who to thank for Red CWM, somebody help me out here. Let me know if I missed anything or got something wrong and I will fix it.
How to UnVoodoo
How to UnVoodoo
The key to uninstalling voodoo is Red CWM. To be specific you don’t uninstall voodoo, you disable the lag fix. Once that’s done you can flash a new non-voodoo kernel.
1. Boot into recovery. You should be in Red CWM.
2. Select “voodoo”.
3. Select “disable lag fix”.
4. Press soft menu button.
5. Select “reboot system now”
6. Wait.
7. Wait.
8. Wait.
9. Wait. Just like during the install, this will take 2-15 minutes, while its reformatting your internal SD card.
10. Your phone will then restart. At this point you still have a voodoo kernel, the lag fix has just been disabled. Red CWM is now broke. No biggie.
11. Re-flash Red CWM with Odin.
12. Reboot into recovery.
13. Flash non-voodoo kernel of your choice.
Note: If you are flashing from one voodoo kernel to another, you do not need to disable lag fix.
Just a couple notes to the first timers: (The credit for this clairifacation goes to GizmoDroid)
1.Most ROM's currently are bundled with a kernel. For example, SuperClean installs CWM, kernel, and system image all in one flash, so no need to flash a separate kernel or CWM after flashing the ROM.
2.Currently, in the newest RED CWM, there are two enable options in the voodoo menu:
•"enable lagfix" - this converts all rfs partitions to ext4 except your "system" partition
•"/system lagfix" - this converts your "system" rfs partition to ext4
You will need to hit both of them for full optimization.
After selecting "enable lagfix", the text at the bottom will change to:
Code:
Voodoo lagfix is actually: disabled
next boot: enabled
Options:
/system lagfix conversion: yes
debug mode: no
Unfortunately, the current CWM has a little glitch that can be confusing. After rebooting, "Voodoo lagfix is actually:" is supposed to change to "enabled" but it will always say "disabled". Rest assured though, it is enabled.
Hopefully this will get fixed when a new version comes along.
OOPS!!!!
Trouble Shooting.
In order to trouble shoot i had to create some trouble to shoot. So i decided to break the rules.
Rule # 1. Dont panic. I started with rule number one because that seemed the logical place to start. However i had nothing to panic about, so i just looked silly. We wont talk about that.
Rule # 2. Dont flash a non voodoo kernel over a voodoo kernel without disableing the lag fix first. I got some results out of this. I bricked my phone. As I have done this 5000000000 times before, I still had no luck with rule number one. My phone how would no longer boot past the Samsung screen. so i rebooted into recovery, and got blue CWM. I tried to apply update.zip and got E:fail blah blah blah.
The reason for this is the filing system is still EXT4. A non voodoo kernel does not know how to talk EXT4, it only speaks RFS. In order to fix the brick we have to do the missing step, disable lag fix.
1. Put the phone in download mode and flash Red CWM.
2. Reboot into recovery. You should now have Red CWM.
3. Select "voodoo"
4. Select "disable lag fix"
5. When you return to the menu, press the menu soft button
6. Reboot. Again this will take 2-15 minutes as the filing system is converted from EXT4 to RFS.
Thats it. That is the only problem I could make happen related to voodoo. I am having a hard time believing its that easy, but it is.
It is often asked "How do I know if I have voodoo?" The simplest way is to run an app called Quadrent. Quadrent is a benchmark app. Scores above 1000 means you have voodoo. Quadrent is not the proper way to check. The more I think about this, the more I think you should learn the proper way. It will give you a greater understanding of what is going on with your phone.
The proper way is to use a terminal emulator and type "mount".
You will see this:
Code:
mount
rootfs / rootfs rw 0 0
proc /proc proc rw,relatime 0 0
sys /sys sysfs rw,relatime 0 0
/dev/block/stl9 /system ext4 rw,relatime,barrier=0,data=writeback,noauto_da_alloc 0 0
/dev/block/stl11 /cache ext4 rw,noatime,barrier=0,data=writeback,noauto_da_alloc 0 0
/dev/block/stl10 /dbdata ext4 rw,noatime,barrier=0,nodelalloc,data=ordered,noauto_da_alloc 0 0
/dev/block/mmcblk0p1 /data ext4 rw,noatime,barrier=1,data=ordered,noauto_da_alloc
the ext4 is what you are looking for. If you see RFS in any of the 4 locations you dont have voodoo or just one of the partitions has voodoo.
Wow, good job spelling this out. I'm not on voodoo yet but when I feel I'm ready I'll be heading to this thread to make sure I don't screw anything up.
Zacisblack said:
Wow, good job spelling this out. I'm not on voodoo yet but when I feel I'm ready I'll be heading to this thread to make sure I don't screw anything up.
Click to expand...
Click to collapse
hope it helps. just ask if yuou have questions.
You did a really GOOD JOB in spelling out voodoo / non voodoo.
Thanks
I was under the impression that the new versions of Voodoo only had the lagfix for EB01 and DL30 because we didn't have a source kernel from Samsung for the Fascinate. I know I haven't been able to access voodoo sound yet and am really anticipating that feature, but if I'm behind or missing something that I can do to get that feature PLEASE let me know.
I made a note regaurding that. When I get to a computer I will make it bold.
Sent from my SCH-I500 using XDA App
Whenever I boot the phone I get the electronic female voice telling me "Convert data partition: System not available. Convert system partition: System not available." What am I doing wrong?
Never mind. It wasn't working under SC 2.7.1, but after flashing to 2.8 it converted and seems to be working.
gunnermike said:
4. Next you will select “choose zip from sdcard”, select your kernel and then yes.
5. When it’s done, press the menu soft button on the bottom left of the phone. This will take you back to the first page.
Go down and select voodoo. Then you will select “enable lag fix”.
6. When that’s done, press the soft menu button and then reboot.
Click to expand...
Click to collapse
Just a couple notes to the first timers:
Most ROM's currently are bundled with a kernel. For example, SuperClean installs CWM, kernel, and system image all in one flash, so no need to flash a separate kernel or CWM after flashing the ROM.
Currently, in the newest RED CWM, there are two enable options in the voodoo menu:
"enable lagfix" - this converts all rfs partitions to ext4 except your "system" partition
"/system lagfix" - this converts your "system" rfs partition to ext4
You will need to hit both of them for full optimization.
After selecting "enable lagfix", the text at the bottom will change to:
Code:
Voodoo lagfix is actually: disabled
next boot: enabled
Options:
/system lagfix conversion: yes
debug mode: no
Unfortunately, the current CWM has a little glitch that can be confusing. After rebooting, "Voodoo lagfix is actually:" is supposed to change to "enabled" but it will always say "disabled". Rest assured though, it is enabled.
Hopefully this will get fixed when a new version comes along.
GizmoDroid said:
Just a couple notes to the first timers:
Most ROM's currently are bundled with a kernel. For example, SuperClean installs CWM, kernel, and system image all in one flash, so no need to flash a separate kernel or CWM after flashing the ROM.
Currently, in the newest RED CWM, there are two enable options in the voodoo menu:
"enable lagfix" - this converts all rfs partitions to ext4 except your "system" partition
"/system lagfix" - this converts your "system" rfs partition to ext4
You will need to hit both of them for full optimization.
After selecting "enable lagfix", the text at the bottom will change to:
Code:
Voodoo lagfix is actually: disabled
next boot: enabled
Options:
/system lagfix conversion: yes
debug mode: no
Unfortunately, the current CWM has a little glitch that can be confusing. After rebooting, "Voodoo lagfix is actually:" is supposed to change to "enabled" but it will always say "disabled". Rest assured though, it is enabled.
Hopefully this will get fixed when a new version comes along.
Click to expand...
Click to collapse
Thanks for the clairification. i will update the OP as soon as i get back back from fixing this ladies internet and replaceing a DVR.
good job explaining voodoo. i love the extra it gives i have been using voodoo for months since i got this phone. this would have been helpful then cuz man i cant tell you how many times i cranked up odin because of voodoo. but i have to say i wont be without voodoo on my phone.
I just upgraded to from non-voodoo SuperClean to voodoo SC2.8 with eb01 radio. I've enabled voodoo/lagfix several times from clockwork but only get Quadrant scores in the 900's. Any idea if something is wrong?
harpdoc said:
I just upgraded to from non-voodoo SuperClean to voodoo SC2.8 with eb01 radio. I've enabled voodoo/lagfix several times from clockwork but only get Quadrant scores in the 900's. Any idea if something is wrong?
Click to expand...
Click to collapse
which cwm are you using?
The latest Red one
harpdoc said:
The latest Red one
Click to expand...
Click to collapse
ok. first are you sure that you dl'ed the the voodoo version?
if so reflash the rom. restart the phone. reboot to recovery. enable lag fix.
It's called super_frankenclean_2_8v_final.zip, so I think it's the right one. I reflashed it but no change. Just to be safe I'm re-downloading the rom and will try again. Strange.
I didn't hear a females voice. I went from 2.8nv to 2.8 V following this verbatim, with the exception of the blue CWM, instead of red, but I fixed that. I scored a 926. I'm a little nervous to do much, because my phones my internet. I brick it, I wait....
thanks for any advice
EDIT: 2nd try, i get quadrant score at 946, but the phone feels a lot faster. took about 2 mins to reboot and still no female voice.
For those that didn't hear a robot voice, and getting low quadrant scores: I'm sorry but you haven't successfully activated the lagfix... but it might not be your fault (maybe ).
Right now, there seems to be something not working for some people. I haven't had any problems myself, but several are not able to trigger the data conversion. Adrynalyne has posted the EB01 voodoo kernel to flash after sc2.8, if you are having problems.
The actual way to test to see if you have the lagfix enabled is not quadrant, but to open up adb or a terminal emulator and type "mount".
This is what a successful lagfix enabled system looks like:
Code:
mount
rootfs / rootfs rw 0 0
proc /proc proc rw,relatime 0 0
sys /sys sysfs rw,relatime 0 0
/dev/block/stl9 /system [COLOR="Red"][B]ext4 [/B][/COLOR]rw,relatime,barrier=0,data=writeback,noauto_da_alloc 0 0
/dev/block/stl11 /cache [COLOR="Red"][B]ext4 [/B][/COLOR]rw,noatime,barrier=0,data=writeback,noauto_da_alloc 0 0
/dev/block/stl10 /dbdata [COLOR="Red"][B]ext4 [/B][/COLOR]rw,noatime,barrier=0,nodelalloc,data=ordered,noauto_da_alloc 0 0
/dev/block/mmcblk0p1 /data [COLOR="Red"][B]ext4 [/B][/COLOR]rw,noatime,barrier=1,data=ordered,noauto_da_alloc 0 0
tmpfs /dev tmpfs rw,relatime,mode=755 0 0
devpts /dev/pts devpts rw,relatime,mode=600 0 0
/dev/block/stl6 /mnt/.lfs j4fs rw,relatime 0 0
tmpfs /mnt/asec tmpfs rw,relatime,mode=755,gid=1000 0 0
tmpfs /sqlite_stmt_journals tmpfs rw,relatime,size=4096k 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
/dev/block/mmcblk0p2 /data/fota rfs rw,nosuid,nodev,relatime,vfat,llw,check=no,gid/uid/rwx,iocharset=utf8 0 0
/dev/block/mmcblk0p3 /preinstall rfs rw,nosuid,nodev,relatime,vfat,llw,check=no,gid/uid/rwx,iocharset=utf8 0 0
/dev/block/vold/179:9 /mnt/sdcard vfat rw,dirsync,nosuid,nodev,noexec,noatime,nodiratime,uid=1000,gid=1015,fmask=0002,dmask=0002,allow_utime=0020,code
page=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/vold/179:9 /mnt/secure/asec vfat rw,dirsync,nosuid,nodev,noexec,noatime,nodiratime,uid=1000,gid=1015,fmask=0002,dmask=0002,allow_utime=0020
,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
tmpfs /mnt/sdcard/.android_secure tmpfs ro,relatime,size=0k,mode=000 0 0
If you run "mount" and it says "rfs" where the red is above, then you do not have voodoo lagfix successfully enabled.
I just reflashed the EB01 Voodoo kernel, enabled lagfix, and rebooted. Wallah, I have the lady robot voice! I can't wait for my phone to reboot and get my first taste of Voodoo! Thanks to everyone for the help!
Related
hi, i recieved a eris from a friend of mine with the intentions on fixing it and using it. when i power it on there's just a black backlit screen.. no splash, nothing. if i plug usb in it goes to a htc screen with 4 triangles in the corners. i've tried the ruu update and it gives an 110 error at the end saying something about files not found, i unhooked the usb and it went to a white screen with hboot 1.49 , n s-on n all that stuff.. and it showed info from the ruu, and it showed that the system and boot(or recovery, i cant remember exactly) failed and they were red. i can connect with fastboot but not with adb.. is there anything i can do to atleast get the phone working.. fastboot oem boot doesnt work for me, it just gives a long list of errors
fastboot will do nothing useful for you if you have the 1.49.0000 S-ON bootloader.
The basic definition of a brick for the Eris is this:
1.49.0000 S-ON bootloader + no recovery + non-booting OS = brick
So, let's review.
1) You have 1.49.0000 S-ON. There is no PB00IMG.zip available to you that can change that using Hboot (without performing some magic with a custom recovery first), and fastboot is worthless with S-ON. So, no go there.
2) You didn't mention (or your description was lacking detail) what happens when you try to go into the Hboot menu (cold start with Vol-Down+End). From there you might be able use the menu to try to launch the recovery boot, to see whether (a) it is the stock recovery, (b) it is a custom recovery, or (c) it fails to start. You should try that next.
If that doesn't work, try a cold start with Vol-Up + End. (You need to keep holding both the buttons down until the screen lights up). That is an alternate way to get to the recovery (when a 1.49.xxxx bootloader is on the phone).
If you have a "stock" recovery, you will see a splash screen with an image of the phone and a triangle with an exclamation point in it. (Pressing Vol-Up+End after you see that splash screen will show a blue menu). If you have Amon_RA's custom recovery, you will see a green menu.
3) If your kernel boots, but the OS is "hanging", there is a remote possibility that you can initiate a factory reset from the "hung" OS. This is a long shot, but you power up the phone normally and then press together Vol-Up+Send+End after waiting a couple of minutes. This might make it bootable. (As I said, "long shot". The fact that you have 1.49.0000 on the phone suggests that the prior owner tried some things - and apparently failed at it.)
bftb0
thanks for the response
i tried all of that just now and all i get is a black backlit screen unless i connect usb which gives me a black screen with HTC n four exclamation point triangles in the corners. and there isnt anything i can do from that screen and its bricked huh?
SoSicWiTiT said:
thanks for the response
i tried all of that just now and all i get is a black backlit screen unless i connect usb which gives me a black screen with HTC n four exclamation point triangles in the corners. and there isnt anything i can do from that screen and its bricked huh?
Click to expand...
Click to collapse
That's not a very good sign. I will say, however, that it is very strange that you can get the phone into RUU mode but not have a working bootloader - those two observations are mutually exclusive.
For grins, you could check to see if perhaps your Vol-Up/Vol-Down keys are broken by doing the following:
- Cold start the phone by pressing Send + End simultaneously (make sure to press Send first so that you are not initiating a normal boot; hold both keys down until the screen lights up). Make sure you pull the battery and have the USB cable disconnected when you pull the battery before you try this (to insure that the phone is "really" off).
If that works, the phone will be in Fastboot mode. You might be able to get into Hboot (but not recovery if your Vol-Up/Vol-down keys are broken) at that point with the command
Code:
fastboot reboot-bootloader
from a USB-connected PC.
Under normal circumstances, you can navigate from Fastboot Mode to Hboot and then from there to the Recovery boot - but this requires working Vol-Up or Vol-Down keys.
There is a very, very slim chance that if you can get Hboot launched this way (that is "fastboot reboot-bootloader")... and try to apply the Leak-V3 "PB00IMG.zip" file. If I recall correctly, you don't need Vol-Up/Vol-Down to apply an HTC PB00IMG.zip file - just the trackball press.
I'm not optimistic though - I think that the Leak-V3 (and all other Leak PB00IMG.zip) files probably will just fail with "Main Version is Older Messages".
As for other avenues of approach, there are no publicly known exploits of the RUU mode (= oem-78 mode).
Good luck
well
actually after staying up n working at it for 48 hours, i'm halfway done with a solution...and maybe the first ruu exploit.
i decided to run the 2.1 RUU and after it does its install wizard thing, i navigated to the temp folder where it installed all the files. i took the root rom (pb00img.zip) n renamed it to "rom.zip" then over wrote the version in the temp folder and started the ruu (clicked next and what not).. it failed as usual with error 110.. but afterward i noticed my phone says
pb00100 xc ENG S-OFF
HBOOT-1.49.2000
and before i did the file swap and ruu it said
pb00100 XC ENG S-ON
HBOOT-1.49.0000
so now i might be able to flash a custom recovery thru fastboot since i have s-off now
if not.. still.. its progress
Hmmm, interesting.
Whether or not that qualifies as new behavior sort of depends on what your "friend" did to the phone prior to getting it into the nearly bricked state. If they had previously run the jcase "Flash any RUU" method, then the Root ROM would have "taken" with the Hboot method... although in your case, since you "couldn't get there from here", my hat's off to you for a clever way of making the best of what you have!
Since you have the S-off bootloader, you might be tempted to direct-boot Amon_Ra without even bothering to flash it:
Code:
fastboot boot recovery-RA-Eris-v1.6.2.img
to see if your phone springs to life... congrats if you see a menu!
bftb0 said:
Since you have the S-off bootloader, you might be tempted to direct-boot Amon_Ra without even bothering to flash it:
Code:
fastboot boot recovery-RA-Eris-v1.6.2.img
to see if your phone springs to life... congrats if you see a menu!
Click to expand...
Click to collapse
i did that right after i seen it say "S-OFF". i get to the menu but when i try to flash a rom it gives me an error after formatting system.
Code:
E:Can't symlink /system/xbin/arp
E:Failure at line 65:
symlink /system/xbin/busybox SYS
TEM:xbin/arp
and after hours or more reading, everything is pointing to the boot and system partitions being corrupted by a bad flash of some sort.
i think i might have hit the end of the road..
EDIT
i managed to somehow get all the regular hboot, fastboot, n recovery to work and flashed amon_ra and can get to it from volup+power.. even got the 3 skateboarding droids on normal power on..
but cant flash any roms , from amon's ( gives the error above )or pb00img from hboot (at the end has "failed-PU" next to system..)
any idea's?
I have a couple ideas (still typing them up) ... in the meantime, if you boot Amon_RA and then open up a shell from the PC ("adb shell") and then
- check the output of "dmesg" to insure that the MTD partition table is still intact; you should see something like this towards the beginning of the boot log:
Code:
NAND_EBI2_ECC_BUF_CFG: 1ff
flash_id: 5501bcec size 20000000
Creating 6 MTD partitions on "msm_nand":
0x00001ff60000-0x000020000000 : "misc"
0x000002c60000-0x000003160000 : "recovery"
0x000003160000-0x0000033e0000 : "boot"
0x0000033e0000-0x00000dde0000 : "system"
0x00000dde0000-0x000015fe0000 : "cache"
0x000015fe0000-0x00001ff60000 : "userdata"
- try mounting (in turn) each of /system, /data, /sdcard, e.g.:
Code:
mount /sdcard
mount /data
mount /system
/cache should already be mounted.
Which mounts fail?
bftb0
The scenario you describe has come up before - or at least very similar symptoms.
Note that Nandroid restore will fail because it uses standard Unix tools such as "rm" to clear filesystems, so if a partition will not mount because of a corruption issue, nandroid will fail. I suppose that the same thing is true of the /sbin/recovery utility running underneath the booted recovery kernel (but I have not read the source code to verify that it is attempting to "mount" the filesystems first - if it didn't do that, it would need to understand the raw format details of yaffs2, and I think that is a stretch).
Unfortunately the filesystem formatting tools provided by Amon_RA do not include tools for repairing the mtd (NAND flash) - they are for the SD card/ extN filesystems. It is my impression, however, that the "yaffs2" filesystem is "format free" - meaning that a clean (Flash memory) "yaffs2" filesystem is simply a bunch of zero'ed pages - no superblocks, or Inode lists, - none of that. This suggests that the equivalent of "dd if=/dev/zero of=/dev/mtd/mtdNNN bs=..." could "repair" a yaffs2 file system by simply wiping it... but let's try something a little less crude than that (see below).
I had one of the file systems in my phone in this state at one time and I was able to repair the problem by reflashing the Root ROM - otoh, XDA user "stick" tried this and it seemed to produce a permanent brick in his case, so I am reluctant to recommend you do that. (You might, however, want to perform the jcase "Flash any RUU" hack to the "misc" partition so that you have flexibility to apply any PB00IMG.zip file)
Because the "flash_image" tool (in /sbin/flash_image in Amon_RA) writes both boot images and yaffs2 image files to arbitrary mtd partitions (and raw binary files to "misc"!), there is a chance that it is merely the equivalent of "dd for the MTD device" - so that you could "repair" a corrupted yaffs2 filesystem by simply overwriting it with a valid yaffs2 image file. The repair strategy here would be to:
- Unpack any PB00IMG.zip file and move the contents to a folder on the SD card. (Verify the md5sums of the files on the SD card before you use them - use this reference)
- Use "flash_image" from Amon_RA to flash the corresponding image file for the offending ("won't mount") partition, e.g.
Code:
flash_image system /sdcard/unpacked-PB00IMG/system.img
If this succeeds, see if you can "mount /system".
bftb0
PS Don't try flashing "system.img" using fastboot. However it is engineered (by the HTC bootloader) it will fail due to space issues. It is possible that the HTC bootloader uses the /cache partition to temporarily stage the file, which is only 130 MB compared to 159.5 MB for the /system partition - but whatever the explanation, the experimental result is that that on the Eris, you can not flash /system from fastboot. All the other partitions, no problem - but not the /system partition.
thanks,
i tried what you suggested and it let me mount all 3 of those partitions, and i tried using flash_image to flash the system.img i extracted and in return got a million and one errors..
starting with mtd: ECC error soft 0 hard 1 (continuing until about a hundred something)
then
mtd: not writing bad block at (basically the entire /system hex range)
then finally
error writing system: no space left on device
SoSicWiTiT said:
thanks,
i tried what you suggested and it let me mount all 3 of those partitions, and i tried using flash_image to flash the system.img i extracted and in return got a million and one errors..
starting with mtd: ECC error soft 0 hard 1 (continuing until about a hundred something)
then
mtd: not writing bad block at (basically the entire /system hex range)
then finally
error writing system: no space left on device
Click to expand...
Click to collapse
Was the partition table information correct? (I have seen innocuous "write error" messages on my phone, but they only occurred on regular block boundaries - not for every page; but in that case I don't think I ever saw an "out of space" message. Assuming everything was performed correctly, your phone is behaving as if large blocks of flash memory are being skipped due to "bad blocks")
Did you unmount the filesystems prior to doing the writes?
That is very mystifying.
If you can mount /system, or /data, what happens when you go in and do a
Code:
mount /system
cd /system
rm -rf /system/*
mount /data
cd /data
rm -rf /data/*
cd /
If those succeed, unmount everything
Code:
cd /
for x in /system /data /sdcard ; do
umount $x
done
Run an Amon_RA "wipe data/factory reset", and try and flash a ROM.
???
bftb0
One other thing you could try - I have never used it, so I don't know what effect it will have - is to use fastboot mode to erase the "system" and "data" partitions, and see if that has any effect on your ability to flash a ROM.
In fastboot (boot w/ Send+End) mode:
Code:
fastboot erase system
fastboot erase data
And then afterward boot into Amon_RA and try flashing a ROM.
I suppose you could also erase the boot partition this way, but you probably ought to do them one at a time just to minimize erase operations - and then if an operation fails in Amon_RA, examine the log file at
Code:
adb shell cat /cache/recovery/log
to see if it provides further elaboration on the nature of the error(s).
bftb0
Something else to try:
The symptoms you have (esp. since it appears that /system and /data will mount correctly) appear as if you "run out of space" when flashing ROMs to NAND. I suppose that could occur if somehow a bunch of pages in flash memory got (erroneously) marked invalid. Unless there is some means to clear flash memory so that bad page indicators are cleared, there is no way to reclaim those pages. (It is my impression that brand new NAND flash chips are already programmed with bad pages pre-marked)
It would be nice if the partition erase function of fastboot actually performed the page reclaim/retesting/re-marking operation - but there is no way to know whether that happens, as the HTC bootloader acts as the interpreter of "fastboot commands" passed over the wire (USB). It is free to implement whatever bad page management strategy that HTC desires - and frankly, a "never reclaim bad pages" policy is fairly reasonable when you consider that most consumer phones are flashed perhaps only 3 or 4 times in their lifetime - if that.
Something to try: if you perform a manual wipe of either /system or /data (after mounting them), do a "df" to see how much free space the kernel thinks they have - for a normal phone, that should be pretty darn close to the partition size. E.G.
Code:
> adb shell
# mount /system
# df /system
# mount /data
# df /data
# umount /system
# umount /data
# exit
>
If it seems "short" by a substantial amount, try installing a "small footprint" ROM, such as CELBFroyo 3.2 - it only uses about 100216 KB (97.9 MB).
Just a thought; I realize this is grasping at straws, but there is little for you to lose (which you knew right from the get-go).
bftb0
wow seriously i appreciate all the help you've provided , you need a donate button lol.
the system partition is 66% used (bad blocks im guessing) after a format leaving 59,648 useable
but the data partition is fine with 1% used. and 162,176 usable
but i havent lost all hope yet and this is entertaining me.
custom mtd maybe..swap /data to mtdblock3 (the bad one, system) and and /system to mtdblock5 (where data currently is).. or use a memory card idk?
here's where i got the idea
http://forum.xda-developers.com/showthread.php?t=717874
SoSicWiTiT said:
the system partition is 66% used (bad blocks im guessing) after a format leaving 59,648 useable
Click to expand...
Click to collapse
Holy crap!
For grins, could you do a "cat /proc/yaffs" and post up the section for the "system" partition? (You need /system to be mounted when you run that command).
Here's what mine looks like after performing an erase with fastboot, booting into Amon_RA, and then mounting it:
Code:
Device 1 "system"
startBlock......... 0
endBlock........... 1359
totalBytesPerChunk. 2048
nDataBytesPerChunk. 2048
chunkGroupBits..... 0
chunkGroupSize..... 1
nErasedBlocks...... 1359
nReservedBlocks.... 5
blocksInCheckpoint. 0
nTnodesCreated..... 0
nFreeTnodes........ 0
nObjectsCreated.... 200
nFreeObjects....... 96
nFreeChunks........ 86976
nPageWrites........ 0
nPageReads......... 0
nBlockErasures..... 0
nGCCopies.......... 0
garbageCollections. 0
passiveGCs......... 0
nRetriedWrites..... 0
nShortOpCaches..... 10
nRetireBlocks...... 0
eccFixed........... 0
eccUnfixed......... 0
tagsEccFixed....... 0
tagsEccUnfixed..... 0
cacheHits.......... 0
nDeletedFiles...... 0
nUnlinkedFiles..... 0
nBackgroudDeletions 0
useNANDECC......... 1
isYaffs2........... 1
inbandTags......... 0
I wonder what your "nRetireBlocks" count is.
I only poked around in the HTC "msm_7k" kernel code a little while ago for some clues, so I'm no expert. There does not seem to be any useful knobs to turn by using mount options.
Because Flash filesystems have to deal with new bad pages as they develop, I'll bet the phone could be completely fixed if there was a way to clear the bad pages - ( if they were actually bad, then on the first write use the write would fail, the pages would be marked bad, and the FS driver would recover gracefully - just as normally happens).
But as you say, that would probably require a custom kernel at the minimum with patches to the mtd driver. I do wonder if the kernel driver for the MTD device exposes any hooks (ioctls, etc) that would let you write a (privileged) userspace app which could wipe the raw pages status info.
This YAFFs doc suggests that certain tuning operations can be performed by writing options to /proc/yaffs, including control of tracing. One of the things that seems possible to control is the number of write attempts per page.
I'll have a look at your URL; no promises, though.
bftb0
[ Edit ] PS - do you have any idea what your friend did to get the phone in this state? Maybe flashing a ROM with really, really low battery? It seems hard to believe that an actual hardware problem occurred - moreover, this is not the first phone where very similar symptoms were exhibited.
I'm wondering if a busybox with mtd-utils compiled in might be of some assistance; in particular the "flash_eraseall" tool. (Perhaps use it with the "-N" option?)
lookit recent versions of the "flash_erase.c" code (excerpted from above Git link):
Code:
static void display_help (void)
{
printf("Usage: %s [options] MTD_DEVICE <start block> <block count>\n"
"Erase blocks of the specified MTD device.\n"
"Specify a count of 0 to erase to end of device.\n"
"\n"
" -j, --jffs2 format the device for jffs2\n"
[COLOR=green][B] " -N, --noskipbad don't skip bad blocks\n"[/B][/COLOR]
" -u, --unlock unlock sectors before erasing\n"
" -q, --quiet display progress messages\n"
" --silent same as --quiet\n"
" --help display this help and exit\n"
" --version output version information and exit\n",
PROGRAM_NAME);
}
(I don't have that version of busybox - I see references made to it in a few posts here on XDA, but I don't know it's origin or where to get it)
bftb0
[ Edit ] looked around for a bit and couldn't find anything pre-built; looks like you might have to build mtd-utils using the NDK for Android. Time for bed for me; here's the link to the mtd-utils project.
i found out that my friend installed rom manager n clockwork recovery and did a flash that failed then ran the 2.1 ruu thinking it would fix it. and that's how the phone got to the state i started with.
i actually got a rom to flash (kinda) with some info from that link i posted. i patched my recovery with files from that link which gave it a custom mtd (table) , i shrunk cache and used the extra space to make up for the bad blocks in system and bind mounted cache to and ext partition on my sd card... and all would be great BUT i realized that the boot partition is corrupt too.. ( which makes sense, since clockwork is known to corrupt both)
so my solution was to flash boot.img to recovery and just boot normally with volup+powerand use amon ra by "fastboot boot " if i need to.
but i cant flash the zip file that patches the kernel to boot using the custom mtd because it's script copies,unpacks,patches then repacks boot.img from /boot but my boot.img is on recovery so im either going to have to edit the .sh in the zip or have someone do the whole custom mtd thing and use the same mtdpartmap.txt and have them nandbackup then give me the boot.img from the backup folder so i can flash it to recovery.
OR have someone manually patch my boot.img file... but i highly doubt i'm going to be able to figure that out or find anyone todo it.
and i'll post the system section of that command in a second.
SoSicWiTiT said:
i found out that my friend installed rom manager n clockwork recovery and did a flash that failed then ran the 2.1 ruu thinking it would fix it. and that's how the phone got to the state i started with.
i actually got a rom to flash (kinda) with some info from that link i posted. i patched my recovery with files from that link which gave it a custom mtd (table) , i shrunk cache and used the extra space to make up for the bad blocks in system and bind mounted cache to and ext partition on my sd card... and all would be great BUT i realized that the boot partition is corrupt too.. ( which makes sense, since clockwork is known to corrupt both)
so my solution was to flash boot.img to recovery and just boot normally with volup+powerand use amon ra by "fastboot boot " if i need to.
but i cant flash the zip file that patches the kernel to boot using the custom mtd because it's script copies,unpacks,patches then repacks boot.img from /boot but my boot.img is on recovery so im either going to have to edit the .sh in the zip or have someone do the whole custom mtd thing and use the same mtdpartmap.txt and have them nandbackup then give me the boot.img from the backup folder so i can flash it to recovery.
OR have someone manually patch my boot.img file... but i highly doubt i'm going to be able to figure that out or find anyone todo it.
and i'll post the system section of that command in a second.
Click to expand...
Click to collapse
I was going to say, holy crap that's a lot of work - but then I've been struggling for a couple hours trying to build mtd-utils (or at least "flash_erase"). I've got all the Makefiles happy (by dropping non-essential parts of the build that require "libuuid"), but now I'm struggling with the linker/toolchain issues to try to avoid the hassles of dynamic link libraries for Amon_RA.
I still think that whatever it is that Clockwork does to get all those flash pages marked as if they are bad is a software error or some sort - so that if you can get
flash_eraseall -N
to do its thing on mtd3, you will recover all those "bad" pages in the system partition. (It is hard to believe that massive physical damage to eeprom would only show up in one or two logical partitions).
Cheers.
bftb0
FWIW,
SoSicWiTiT said:
OR have someone manually patch my boot.img file... but i highly doubt i'm going to be able to figure that out or find anyone todo it.
Click to expand...
Click to collapse
Have a look at this android-dls.com tutorial if you haven't already seen it. Use "split_bootimg.pl" to split apart the boot image into the kernel and compressed ramdisk, and then the ramdisk is just a gzipp'ed "cpio" archive.
The hardest bit about this is finding a verstion of "mkbootimg" - there are some floating around on XDA, or you can build it from the github sources.
It's not too bad, the only secret sauce is the load address for the Eris, which is 0x11200000
This is an excerpt from a shell script I use for repacking boot images - it's the essential part (everything else in the script is just glue).
Code:
mkbootimg --kernel ${_KFIL} --ramdisk new-${_RAMDGZ} --cmdline 'no_console_suspend=1 console=null' --base 0x11200000 --output new-${_BNAM}
i edited the shell script thats supposed to patch it to the best of my abilities (changed all boot.img txt to recovery.img) and it has mkbootimg and everything it needs in the zip, so im going to replace the script in the zip and try flashing it...
and something weird just happened.. i forgot i put boot.img for my rom on /recovery . so in shell just now, i typed reboot recovery expecting amon RA and the phone booted into the os???
even though i patched amon ra with custom mtd to install the rom ( system :300,000 - enough to skip bad blocks, cache: 30,000 ) my boot.img is mtd is set to see 176,000 right?
EDIT
i think i flashed that zip with my version of the script earlier to see what happened and i guess it worked..
Code:
C:\droid\tools>adb shell
sh-3.2# df /system
df /system
Filesystem 1K-blocks Used Available Use% Mounted on
/dev/block/mtdblock3 307200 229296 77904 75% /system
sh-3.2# df /cache
df /cache
Filesystem 1K-blocks Used Available Use% Mounted on
/dev/block/mtdblock4 61440 36500 24940 59% /cache
sh-3.2# df /data
df /data
Filesystem 1K-blocks Used Available Use% Mounted on
/dev/block/mtdblock5 101888 2608 99280 3% /data
sh-3.2#
If anybody here doesn't mind testing, could you check out the following thread and test the new z4mod app on your Fascinate? I only have an I9000, but the app (and lagfix) should work fine on the Fascinate as well. Let me know please!
http://forum.xda-developers.com/showthread.php?p=9307467#post9307467
I'm looking at z4zipgen.sh..
I see this..
Code:
sed -i 's|run_program("/sbin/z4mod".*|run_program("/sbin/z4mod", "data", "mmcblk0p2", "'$1'");|g' "${script}"
which makes me think that i9000 data is on mmcblk0p2? Because that is our data/fota...
This is mount from our devices.
Code:
mount
rootfs / rootfs rw 0 0
tmpfs /dev tmpfs rw,mode=755 0 0
devpts /dev/pts devpts rw,mode=600 0 0
proc /proc proc rw 0 0
sysfs /sys sysfs rw 0 0
/dev/block/stl6 /mnt/.lfs j4fs rw 0 0
tmpfs /sqlite_stmt_journals tmpfs rw,size=4096k 0 0
none /dev/cpuctl cgroup rw,cpu 0 0
/dev/block/stl9 /system rfs rw,vfat,llw,check=no,gid/uid/rwx,iocharset=utf8 0 0
/dev/block/mmcblk0p1 /data rfs rw,nosuid,nodev,vfat,llw,check=no,gid/uid/rwx,ioc
harset=utf8 0 0
/dev/block/stl10 /dbdata rfs rw,nosuid,nodev,vfat,llw,check=no,gid/uid/rwx,iocha
rset=utf8 0 0
/dev/block/mmcblk0p2 /data/fota rfs rw,nosuid,nodev,vfat,llw,check=no,gid/uid/rw
x,iocharset=utf8 0 0
/dev/block/mmcblk0p3 /preinstall rfs rw,nosuid,nodev,vfat,llw,check=no,gid/uid/r
wx,iocharset=utf8 0 0
/dev/block/stl11 /cache rfs rw,nosuid,nodev,vfat,llw,check=no,gid/uid/rwx,iochar
set=utf8 0 0
/dev/block//vold/179:9 /sdcard vfat rw,dirsync,nosuid,nodev,noexec,uid=1000,gid=
1015,fmask=0002,dmask=0002,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,s
hortname=mixed,utf8,errors=remount-ro 0 0
RyanZA said:
If anybody here doesn't mind testing, could you check out the following thread and test the new z4mod app on your Fascinate? I only have an I9000, but the app (and lagfix) should work fine on the Fascinate as well. Let me know please!
http://forum.xda-developers.com/showthread.php?p=9307467#post9307467
Click to expand...
Click to collapse
Tried, No such luck
Should I be running a stock kernal?
Doesn't matter, really. z4mod doesn't use the correct mountpoints for us.
I used it with no problems. It installed clockworkmod for me.
jeffbeagley said:
I used it with no problems. It installed clockworkmod for me.
Click to expand...
Click to collapse
What are your quadrant scores?
If it roots and installs clockwork, it is already an easier root than the manual method.
Frankly, it would be less useful to me if it installed voodoo...
Sent from my stupidfast blackish hole...
I am fairly new to Android (just switched from iPhone). Will rooting a phone break the ability to receive OTA updates?
Is stupidfast compatible with this I tried patching but it failed
Chuban7 said:
Is stupidfast compatible with this I tried patching but it failed
Click to expand...
Click to collapse
This is an un root method from what I understand. If you're using an alternate kernel, you are already un rooted.
eriknokc said:
I am fairly new to Android (just switched from iPhone). Will rooting a phone break the ability to receive OTA updates?
Click to expand...
Click to collapse
Root just means to 'gain root access' to your phone, usually by having a 'su' (superuser) binary in your bin/xbin directory, and by having a Superuser.apk (Superuser App) that uses this binary when an app wants Superuser permissions. (in other words, you can delete system files, do things with the hardware that the original manufacturer did not intend, etc etc).
Unrooting technically just involves deleting the 'su' binary and uninstalling/deleting the Superuser App.
NOW
If you install a custom Recovery (it's a separate partition on your phone - basically like a second hard drive on your computer) which you can boot up from, such as ClockworkMod, you can install custom ROMs (such as the ones you'll see in this development section), and SOME of those may or may not have OTA updates disabled.
Typically developers will set up ROMs with all of the latest OTA fixes and things anyway, or the ROMs will be based on the latest OTA builds. So not having OTA updates is virtually meaningless if you keep your ROM up to date. Once in a while OTA updates will do what Apple's iOS updates do - which means fixing a security hole that allowed Rooting.
So in short, just having root access does NOTHING to OTA updates. Installing a custom ROM that has OTA updates disabled, and/or going into whatever directories necessary to delete the OTA Certs file by using your root access CAN disable OTA updates.
Chuban7 said:
Is stupidfast compatible with this I tried patching but it failed
Click to expand...
Click to collapse
did you flash clockworkmod recovery through odin first? lastest stupidfast 1.5.4 test version should work on stock kernel but you'll lose haptic feedback, unless you have DJ05 handy.
I just got a white fascinate from bestbuy on Friday. For only $1 I thought it was time to upgrade from the original Droid. I have experience with rooting, my Droid was rooted since day one. I don't consider myself a noob but I also wouldn't consider myself a master at it. I've been reading all the root methods but they require a PC, which I don't currently have access to. So I found z4root and fired it up. Got root and it seemed simple. Installed busybox and super user.
I attempted to install clockwork through rom manager and it said it was successful so I downloaded super clean rom. Rebooted into recovery to find it didn't install, researched and found an update.zip to access clockwork and that didnt work. Got a signature verification error.
Downloaded root explorer to apply the 3g speed fix. Went to remount system as r/w but can not do that. Root explorer has super user permissions but I can not change folders or files to r/w access.
I'm not sure if its a problem with z4root or if having a white fascinate is to blame? Any input is grately appreciated. Thanks!
ms262c said:
I just got a white fascinate from bestbuy on Friday. For only $1 I thought it was time to upgrade from the original Droid. I have experience with rooting, my Droid was rooted since day one. I don't consider myself a noob but I also wouldn't consider myself a master at it. I've been reading all the root methods but they require a PC, which I don't currently have access to. So I found z4root and fired it up. Got root and it seemed simple. Installed busybox and super user.
I attempted to install clockwork through rom manager and it said it was successful so I downloaded super clean rom. Rebooted into recovery to find it didn't install, researched and found an update.zip to access clockwork and that didnt work. Got a signature verification error.
Downloaded root explorer to apply the 3g speed fix. Went to remount system as r/w but can not do that. Root explorer has super user permissions but I can not change folders or files to r/w access.
I'm not sure if its a problem with z4root or if having a white fascinate is to blame? Any input is grately appreciated. Thanks!
Click to expand...
Click to collapse
You have to flash CWM through Odin my friend.http://forum.xda-developers.com/showthread.php?t=788099
z4root makes no different.
good luck
Need help unrooting!
How do I unroot my phone to take it back to stock? I have tried the unroot option in Z4root, but it doesn't seem to have done anything. Any suggestions? Thank you.
slvrevoix said:
You have to flash CWM through Odin my friend.http://forum.xda-developers.com/showthread.php?t=788099
z4root makes no different.
good luck
Click to expand...
Click to collapse
Thanks for letting me know that! My only other problem is no r/w access to the system files. Any suggestions?
ms262c said:
Thanks for letting me know that! My only other problem is no r/w access to the system files. Any suggestions?
Click to expand...
Click to collapse
are you using root explorer? does it give you the option to set r/w? i just used z4root from the market and it seems to work fine for me. completed and got asked for superuser access when i loaded up root explorer
Im missing clockwork recovery, i think its a wonderfull tool. And i think life on the Folio would be much easier with it. I dont have the skills my self to make it happen. I dont even know if its possible. But i thought i put the question out there to see if something happens. And i must say we all own Dexter a big thanks, because he seams to be the only one with any rom cooking skills for the Folio. Ican say that its only because of him that i bought the Folio. I also saw in the Tnt0.4 thread a question about Cyanogen and if we wanted it, HELL YEEAAAH!!!! I know tthat GTab have a beta for it. And also read that GTab and Folio are very close hardware wise so maybe a port is possible. But again i dont have the skills
No one? Am i the only one wanting these things? I thougt if we could get a thread going on the matter we might inspire someone with the skills to do a Cyanogen port for the folio. Cyanogen is almost ready to start the nightlies on CM7 so maybe we could have Gingerbread.
Clockwork recovery would be nice to have its alot easyer to do things with it, im still waiting for stable CyanogenMod on my galaxy s to be able to say if i want it on my tablet i have no idea how to get clockwork to work though and if its even possible
i'm sure its possible, but reading the Gtab thread on Cyanogen i'm waiting for a stable release before i would consider wasting time on it, and currently my "compiling" environment is still VMWare based, and i simply dont like compiling in it, since it takes like 30x the time i got on my debian..(will be ubuntu very soon)
It sounds promissing that you keep track on the development of the Cyanogen rom for Gtab. There seams to be some more work being done over Irc on freenode. Its a beta 6.2 thats been released there, but it seams to have some issues. But for sure Cyanogen would be exellent. Im currently running Gridlocks "Crackflashers" CM7-Rc0 on my Desire HD, and Gingerbread is so smooth and it runs so well. And Koush has a guide on how to get clockwork recovery on to new devices on his site. But hey, i dont got the skills. I just enjoy all the Devs work and try to help out with some beta testing if needed.
nickwarn said:
And Koush has a guide on how to get clockwork recovery on to new devices on his site. But hey, i dont got the skills. I just enjoy all the Devs work and try to help out with some beta testing if needed.
Click to expand...
Click to collapse
i was considering testing the Gtab edition, and modify the parts that point to wrong partitions and make it folio compatible.. thats probably the easy one..
but maybe i should check that site? you got a link? or should google help?
Dexter_nlb said:
i was considering testing the Gtab edition, and modify the parts that point to wrong partitions and make it folio compatible.. thats probably the easy one..
but maybe i should check that site? you got a link? or should google help?
Click to expand...
Click to collapse
Yes its "Koushikdutta.com" he has a guide its called "Porting clockwork recovery to new devices" Its a little hard to find. Just go to bottom on the site and click on 2010 articles and scroll down and there it isorting Clockwork Recovery to New Devices
I pasted the begining of the guide:
It is difficult for me to port recovery for a device I don’t have. So, people can attempt to port it using this guide. However, if you want it done properly, and probably quicker, you can loan the device to me personally at:
Koushik Dutta
2721 1st Ave 507
Seattle, WA 98121
The package must include:
The rooted phone.
A return packing slip to your address.
A signed statement saying: “I, <your name here>, am lending this device, <name of device>, to Koushik Dutta so that he can try to port Clockwork Recovery to the device. I understand that rooting a phone voids the warranty and tampering with the software may render the device nonfunctional. I realize and accept that the phone may not be functional when it is returned. Koushik Dutta is not liable for any damages to the device.”
And so on, have a look.
The folio seem to be very close to the Gtab, what about Advent Vega? because the guys in Gtab thread are using Vega rom and it also has a clockwork recovery. I dont know , but maybe having a look at that would help. If looking aat the differrent parts of recovery.img and where they differ one can see where changes need to be made? I dont know, just trying to help. I really want this clockwork rec, i think we all and the folio would take a step forward. And maybe have a look at VeganTab rom, if possible to port?
I've used clockworkmod recovery since G1 era and it has saved my b*tt several times. The built-in nandroid support, permission fixing, unsigned zip flashing, etc are very useful and user-friendly.
http://www.koushikdutta.com/2010/10/porting-clockwork-recovery-to-new.html
nickwarn said:
Yes its "Koushikdutta.com"
Click to expand...
Click to collapse
ok, will check it out this weekend.
That would be great dexterr
I just read in the Avent Vega forum that Apache14 maid a port of GTab cyanogen for them and it seems to work ok. And he also said that he is now concentrating on Gingerbread, proberly that means CM7. And judging from the work Apache14 has done for us with Desire HD, Z, G2. This sounds really promising
Hi,
I'm trying to port ClockworkMod Recovery v3.0.0.5.
For now it's partially working. I can't mount some part.
This is my recovery.fstab :
Code:
# mount point fstype device [device2]
/boot auto /dev/block/mmcblk0p5
/cache auto /dev/block/mmcblk0p2
/data auto /dev/block/mmcblk0p6
/misc auto /dev/block/mmcblk0p3
/recovery auto /dev/block/mmcblk0p7
/sdcard vfat /dev/block/mmcblk1p1 /dev/block/mmcblk0p8
/system auto /dev/block/mmcblk0p1
/sd-ext auto /dev/block/mmcblk1p2
/boot and /recovery don't mount.
any idea is welcome
wolfx said:
/boot auto /dev/block/mmcblk0p5
/recovery auto /dev/block/mmcblk0p7
/boot and /recovery don't mount.
Click to expand...
Click to collapse
you should not mess with 5 and 7, those are in a stock rom boot and recovery images, not a filesystem. so they cannot be mounted.
wolfx said:
Hi,
I'm trying to port ClockworkMod Recovery v3.0.0.5.
For now it's partially working. I can't mount some part.
This is my recovery.fstab :
Code:
# mount point fstype device [device2]
/boot auto /dev/block/mmcblk0p5
/cache auto /dev/block/mmcblk0p2
/data auto /dev/block/mmcblk0p6
/misc auto /dev/block/mmcblk0p3
/recovery auto /dev/block/mmcblk0p7
/sdcard vfat /dev/block/mmcblk1p1 /dev/block/mmcblk0p8
/system auto /dev/block/mmcblk0p1
/sd-ext auto /dev/block/mmcblk1p2
/boot and /recovery don't mount.
any idea is welcome
Click to expand...
Click to collapse
I dont know, but im glad someone taking the first step. Maybe you could mail Koush, its a link in the guide for porting clockwork recovery. I dont know how much support he does. But writes that one can send ones device to him and he will port it, so i think if hes willing to that kind of work, he probably answers some question. I wish you the best of luck and i will follow your progress with great interest
My port of the ClockworkMod recovery is about fully working.
update from .zip, wipe, backup and restore ... are working but i still have some minor issue.
Partitions don't automatically mount and actually backup of boot part don't work.
I'm asking if bootloader could be the problem.
wolfx said:
My port of the ClockworkMod recovery is about fully working.
update from .zip, wipe, backup and restore ... are working but i still have some minor issue.
Partitions don't automatically mount and actually backup of boot part don't work.
I'm asking if bootloader could be the problem.
Click to expand...
Click to collapse
yes, according to DerArtem, you cannot see the partitions which contain that information its located outside of the mmc.
but sounds great you got it running, alot will appreciate it...
Rom cooking
moved.............
Maybe I'll make a stupid question ... but .. not really for serving or clockwork recovery that can help.
Can anyone explain to me that extra utility of this tool?
thanks
i just started hacking my Legend some time ago and got the liking of RomManager. my friend have a as100 rooted and flashed rom manually. Clockwork port to this device will be great on the go.
Hello everybody, I'm Dejan and I could use some help please.
I have Samsung Galaxy SII GT 9100 with broken screen and I have some very important stuff in it. Screen is totally broken and I cant see a thing. Long story short i used Fuzzy Meep's app but I'm stuck deep in the mud so thats off. I booted phone in my custom recovery , installed ADB on PC and managed to connect to the device. But I can't make my way thru the sdcard. Here is what I did:
G:\ADB>adb.exe shell
~ # cd etc
cd etc
/etc # ls
ls
recovery.fstab
/etc # cat recovery.fstab
cat recovery.fstab
# Android fstab file.
#<src> <mnt_point> <type> <mnt_flags and options
> <fs_mgr_flags>
# The filesystem that contains the filesystem checker binary (typically /system) cannot
# specify MF_CHECK, and must come before any filesystems that do specify MF_CHECK
# data partition must be located at the bottom for supporting device encryption
/dev/block/mmcblk0p9 /system ext4 ro,noatime
wait
/dev/block/mmcblk0p7 /cache ext4 noatime,nosuid,nodev,j
ournal_async_commit,errors=panic wait,check_spo
/dev/block/mmcblk0p1 /efs ext4 noatime,nosuid,nodev,j
ournal_async_commit,errors=panic wait,check_spo
/dev/block/mmcblk0p10 /data ext4 noatime,nosuid,nodev,d
iscard,noauto_da_alloc,journal_async_commit,errors=panic wait,check_spo,encryptable=/efs/metadata
/dev/block/mmcblk0p12 /preload ext4 noatime,nosuid,nodev,j
ournal_async_commit wait
# vold-managed volumes ("block device" is actually a sysfs devpath)
/devices/platform/dw_mmc/mmc_host/mmc0/mmc0 auto auto defaults voldmanaged=sdcard0:
11,nonremovable,noemulatedsd
/devices/platform/s3c-sdhci.2/mmc_host/mmc1 auto auto defaults voldmanaged=sdcard1:
auto
/devices/platform/s3c_otghcd/usb auto auto defaults voldmanaged=usbdisk0
:auto
# recovery
/dev/block/mmcblk0p5 /boot emmc defaults recovery
only
/dev/block/mmcblk0p6 /recovery emmc defaults recovery
only
How do i mount internal memory and pull out my data? Any help is appreciated. Thanks
It's a CM LInaro Kitkat 4.4.2 with custom kernel. With older versions of Android I was able to do what I was attempting to do but I've read somewhere about certain change when mounting storage on 4.4.2.
Thanks in advance.
Noone? Reallu? At least some info about device reading out data directly from the storage chip?
denkodenko said:
Noone? Reallu? At least some info about device reading out data directly from the storage chip?
Click to expand...
Click to collapse
That isn't even remotely possible for an end user. The only people who might be able to do that is a company which specialises in recovery of data from dead HDDs'. If it is possible, expect it to be very very expensive. I've never seen a single person post here in 2.5 yrs saying they've had this done successfully. Even if this is was possible, fixing your screen would be cheaper.
Very few people here have attempted to do what you're doing with ADB (me included; frankly, if the data was that important to me, I'd pay $120 for a new screen to save myself hassles, but I wouldn't be in that situation to begin with because I back stuff up). Unfortunately, you're going to be in for a rather long wait if you don't manage to work this out on your own, many people who may have been able to help you don't post here anymore, they've moved onto other phones given it's been 3 yrs since this phone was released.
MistahBungle said:
That isn't even remotely possible for an end user. The only people who might be able to do that is a company which specialises in recovery of data from dead HDDs'. If it is possible, expect it to be very very expensive. I've never seen a single person post here in 2.5 yrs saying they've had this done successfully. Even if this is was possible, fixing your screen would be cheaper.
Very few people here have attempted to do what you're doing with ADB (me included; frankly, if the data was that important to me, I'd pay $120 for a new screen to save myself hassles, but I wouldn't be in that situation to begin with because I back stuff up). Unfortunately, you're going to be in for a rather long wait if you don't manage to work this out on your own, many people who may have been able to help you don't post here anymore, they've moved onto other phones given it's been 3 yrs since this phone was released.
Click to expand...
Click to collapse
Well at least I gave it a shot but yeah... you are probably right I shouldn't have bothered posting and I was pretty sure someone somewhere might have asked the exact same question unfortunately I couldn't find it. I know how annoying these questions can be and I'm very sorry if I made someone angry. Long story short - I managed to get my pictures and videos back, as well as contacts. I do back those stuff up. however I had some .bin files for work that I lost but I've been living with that. It just might take some time browsing on the Internet finding them again but I'd rather do that than trying to do anything with the phone. I bought it $100 last year, the screen alone is that much, there's no point in fixing it. And at last but not least, thanksfor the reply.
Nah, they're not annoying It's just a very unusual situation, and as I said, if you want help with that sort of stuff with this phone on here, because so many people have moved on, you need to be really patient, that's all.
Same story
Shortly broken display no touch input. I had custom KitKat rom.
I had almost given up trying to mount the internal sd card with ADB, following numerios forum post instructions
here is my solution using windows pc and ADB
I rebooted in recovery (I think it was 6,0xx)
Using command prompt (you also need adb.exe) :
adb remount
adb root
adb usb
Those 3 command somehow mounted the internal storage and I was able to use the "adb pull" comand to copy the whole internal sd card to my hard drive
After that I went with "adb shell" to check how the sd card was mounted and here is what I found:
"
/dev/block/vold/259:3 on /storage/sdcard0 type vfat (rw,dirsync,nosuid,nodev,noe
xec,relatime,uid=1023,gid=1023,fmask=0007,dmask=0007,allow_utime=0020,codepage=c
p437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro)
/dev/block/mmcblk0p11 on /emmc type vfat (rw,dirsync,relatime,uid=1023,gid=1023,
fmask=0007,dmask=0007,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortn
ame=mixed,utf8,errors=remount-ro)
"
Ive been searching for a while for a forum that explains how to root the new nabi 24" BIG TAB HD. trying to install clockworkmod on the tablet.. if anyone can point me in the direction of what I'm looking for that would be greatly appreciated.
jmmac said:
Ive been searching for a while for a forum that explains how to root the new nabi 24" BIG TAB HD. trying to install clockworkmod on the tablet.. if anyone can point me in the direction of what I'm looking for that would be greatly appreciated.
Click to expand...
Click to collapse
As far as I know nobody has talked about it on here except you.
Depending on what kernel patches or android security fixes it has you might be able to try some root programs. There certainly will not be a clockworkmod or TWRP for it yet.
If none of the root methods work it might be possible to use the Dreamtab TWRP.(http://forum.xda-developers.com/android/development/recovery-twrp-2-7-1-0-nabi-dreamtab-hd8-t2813917) If it's like the previous Nabi tablets the bootloader will be unlocked, and you could try booting from that TWRP. The screen and the landscape/portrait might be messed up but it could work. In the last software update to the dreamtab they locked the bootloader so the BIG TAB might be as well. It could be unlocked by
Code:
fastboot oem unlock
^^^ This will ERASE all the data on the tablet.
If you want to try the TWRP way let me know but of course there are dangers involved.
If you try it alone be aware that if you try the dreamtab TWRP load it by
Code:
fastboot boot recovery.img
and NOT
Code:
[STRIKE]fastboot flash recovery recovery.img[/STRIKE]
or you will overwrite your current stock recovery.
also interested! any further info would be great!
schlager said:
also interested! any further info would be great!
Click to expand...
Click to collapse
Do either of you have one? Or just asking?
aicjofs said:
Do either of you have one? Or just asking?
Click to expand...
Click to collapse
i plan to buy one in the next few weeks. mainly need it so i can have two sheets of music in front of me. if there is another tablet that can do that, let me know.
aic, I got one for the kids for Xmas. The Nabi2's have been good but wont last forever, I liked the multi user option and big ass screen on the big tab. Well see how it works out! Once they open and spend time with it I'll be interested in rooting for adaway and such.
codest3r said:
aic, I got one for the kids for Xmas. The Nabi2's have been good but wont last forever, I liked the multi user option and big ass screen on the big tab. Well see how it works out! Once they open and spend time with it I'll be interested in rooting for adaway and such.
Click to expand...
Click to collapse
I have no idea about the BigTab but if it's like the DreamTab it will update when you boot it up. It's hard to get around it. If it does it will likely patch a lot of the more recent exploits that can gain you root. There is the option to try the dream tab recovery like I said above but be really careful with that.
Also one of the Dreamtab updates locked the bootloader. This isn't a big deal as it was unlockable via fastboot. However, if you let the kiddoz, or you start installing a whole bunch of stuff, when you unlock the bootloader you will wipe the tablet back to factory(normal behavior). Best to unlock it as soon as possible.
I own the big tab 20" was able to root using http://forum.xda-developers.com/showthread.php?t=2473747
I did have to unlock the bootloader and tried booting the dream tab recovery from fastboot no dice there so wasn't gonna risk flashing it.
The process took about 20 mins maybe less fully automated it froze at some point so I reset the big tab and tried again at which point kingo program told me I was already rooted download SU was able to update the binary's normal method and been good to go since. Word of warning it does preform a factory reset when you unlock the bootloader so be prepared for that.
I have been working on compiling CWM for the Nabi big tab 20" I'm close but I can't seem to figure out the path for the sdcard currently the recovery boots but can't back anything up with out the correct path entered into the recovery.fstab. This particular tablet does not have a real sdcard nor does it have a slot for an external one. Any help on this would be appreciated when I get it sorted out will add a link for the recovery.
this is what I currently have in my recovery.fstab.
# Android fstab file.
#<src> <mnt_point> <type> <mnt_flags> <fs_mgr_flags>
# The filesystem that contains the filesystem checker binary (typically /system) cannot
# specify MF_CHECK, and must come before any filesystems that do specify MF_CHECK
/dev/block/platform/sdhci-tegra.3/by-name/SOS /recovery emmc defaults defaults
/dev/block/platform/sdhci-tegra.3/by-name/LNX /boot emmc defaults defaults
/dev/block/platform/sdhci-tegra.3/by-name/APP /system ext4 ro wait
/dev/block/platform/sdhci-tegra.3/by-name/CAC /cache ext4 noatime,nosuid,nodev,data=writeback,nodelalloc,errors=panic wait
/dev/block/platform/sdhci-tegra.3/by-name/MSC /misc emmc defaults defaults
/dev/block/platform/sdhci-tegra.3/by-name/USP /staging emmc defaults defaults
/dev/block/platform/sdhci-tegra.3/by-name/MDA /metadata emmc defaults defaults
/dev/block/platform/sdhci-tegra.3/by-name/UDA /data ext4 noatime,nosuid,nodev,data=ordered,noauto_da_alloc,errors=panic wait,encryptable=/dev/block/platform/sdhci-tegra.3/by-name/MDA
/dev/block/platform/sdhci-tegra.3/by-name/TRD /app ext4 defaults wait
/dev/block/sda1 /sdcard vfat defaults voldmanaged=sdcard:auto
When I boot into recovery and attempt to perform a backup to sdcard I get E:Can't mount backup path.
You could download and try a rooting apk like towelroot framaroot or z4root if it has a low android firmware like 2.3.6 or something but only for z4root
I already got it rooted using Kingo root, these tablets are new on the market running kitkat 4.4.4, the end goal I am trying to achieve is making a custom rom but a neassacery first step is to get a working custom recovery so I can backup my stock rom just in case I blow up my tablet =)
lmortal said:
I have been working on compiling CWM for the Nabi big tab 20" I'm close but I can't seem to figure out the path for the sdcard currently the recovery boots but can't back anything up with out the correct path entered into the recovery.fstab. This particular tablet does not have a real sdcard nor does it have a slot for an external one. Any help on this would be appreciated when I get it sorted out will add a link for the recovery.
this is what I currently have in my recovery.fstab.
# Android fstab file.
#<src> <mnt_point> <type> <mnt_flags> <fs_mgr_flags>
# The filesystem that contains the filesystem checker binary (typically /system) cannot
# specify MF_CHECK, and must come before any filesystems that do specify MF_CHECK
/dev/block/platform/sdhci-tegra.3/by-name/SOS /recovery emmc defaults defaults
/dev/block/platform/sdhci-tegra.3/by-name/LNX /boot emmc defaults defaults
/dev/block/platform/sdhci-tegra.3/by-name/APP /system ext4 ro wait
/dev/block/platform/sdhci-tegra.3/by-name/CAC /cache ext4 noatime,nosuid,nodev,data=writeback,nodelalloc,errors=panic wait
/dev/block/platform/sdhci-tegra.3/by-name/MSC /misc emmc defaults defaults
/dev/block/platform/sdhci-tegra.3/by-name/USP /staging emmc defaults defaults
/dev/block/platform/sdhci-tegra.3/by-name/MDA /metadata emmc defaults defaults
/dev/block/platform/sdhci-tegra.3/by-name/UDA /data ext4 noatime,nosuid,nodev,data=ordered,noauto_da_alloc,errors=panic wait,encryptable=/dev/block/platform/sdhci-tegra.3/by-name/MDA
/dev/block/platform/sdhci-tegra.3/by-name/TRD /app ext4 defaults wait
/dev/block/sda1 /sdcard vfat defaults voldmanaged=sdcard:auto
When I boot into recovery and attempt to perform a backup to sdcard I get E:Can't mount backup path.
Click to expand...
Click to collapse
Did you get that from pulling the stock recovery and extracting the recovery.fstab from the ramdisk?
The internal is likely on /data/media, or data/media/0 if it's like all the other Nabi's. Pretty sure /dev/block/sda1 to mount sdcard is not going to work. I'm not as knowledgeable at CWM as I enjoy TWRP so I'm not sure if there is a boardconfig.mk change you can do or if you need to symlink it in an init.rc file.
aicjofs said:
Did you get that from pulling the stock recovery and extracting the recovery.fstab from the ramdisk?
The internal is likely on /data/media, or data/media/0 if it's like all the other Nabi's. Pretty sure /dev/block/sda1 to mount sdcard is not going to work. I'm not as knowledgeable at CWM as I enjoy TWRP so I'm not sure if there is a boardconfig.mk change you can do or if you need to symlink it in an init.rc file.
Click to expand...
Click to collapse
There was something else there originaly but it didn't work either so I ended up using the following from cat /proc/mounts:
/dev/fuse/mnt/shell/emulated /sdcard fuse rw,nosuid,nodev,realtime,user_id=1023,group_id=1023,default_permisions,allow_other nonremovable
Using the above line in the recovery.fstab allowed cwm to see the sdcard but was still unable to mount it. I have been playing around with different things but I am fairly new to this so my knowledge is limited.
lmortal said:
There was something else there originaly but it didn't work either so I ended up using the following from cat /proc/mounts:
/dev/fuse/mnt/shell/emulated /sdcard fuse rw,nosuid,nodev,realtime,user_id=1023,group_id=1023,default_permisions,allow_other nonremovable
Using the above line in the recovery.fstab allowed cwm to see the sdcard but was still unable to mount it. I have been playing around with different things but I am fairly new to this so my knowledge is limited.
Click to expand...
Click to collapse
I'm not really sure without seeing any of your code(device tree), finished recovery or any of the stock recovery.
I haven't made CWM in so long. Something like?
/dev/null /sdcard datamedia defaults recoveryonly
dd the mmcblock0pX for the recovery and boot and we can make something work. How much space is the recovery partition?
aicjofs said:
I'm not really sure without seeing any of your code(device tree), finished recovery or any of the stock recovery.
I haven't made CWM in so long. Something like?
/dev/null /sdcard datamedia defaults recoveryonly
dd the mmcblock0pX for the recovery and boot and we can make something work. How much space is the recovery partition?
Click to expand...
Click to collapse
I sent you a pm with a drop box link with my files in the mean time gonna try compiling with your suggestion and see what happens.
---------- Post added at 04:17 PM ---------- Previous post was at 03:36 PM ----------
I tried compiling with:
#<src> <mnt_point> <type> <mnt_flags> <fs_mgr_flags>
/dev/null /sdcard fuse datamedia,recoveryonly defaults
It compiled successfully and I was able to flash it, the sdcard showed up in the mount menu but was not mountable still.
---------- Post added at 05:10 PM ---------- Previous post was at 04:17 PM ----------
Okay so my latest build using:
/dev/block/sda1 sdcard fuse defaults nonremovable
Allowed backup to the sdcard of everything with the exception of /data got "Error while making a backup image of /data!"
Also still unable to mount sdcard under the mounts and storage menu.
I believe the reason for the error while backing up data was due to available space when I restarted the tablet there was only 99.59MB available and I think the data would have needed more space then that.
I kept running into problems with CWM recovery but with the help of aicjofs I was able to compile a working TWRP with usb drive support, I don't yet have enough post to make an outside link so if some one can pm me I can give the link to be posted here with the recovery I made.
Working TWRP 2.8.1.0 for Nabi BigTab 20
Here is a TWRP recovery 2.8.1.0 for the Nabi BigTab 20" model
TWRP 2.8.1.0 for NV20A(BigTab20)
Built by @lmortal. We spent a lot of our Sunday sorting all the issue so click the thanks button for Imortal in the post above this one!
aicjofs said:
Here is a TWRP recovery 2.8.1.0 for the Nabi BigTab 20" model
TWRP 2.8.1.0 for NV20A(BigTab20)
Built by @lmortal. We spent a lot of our Sunday sorting all the issue so click the thanks button for Imortal in the post above this one!
Click to expand...
Click to collapse
Fixed an error where /addon was not mounting. re uploaded recovery image to the above link.
I can't unlock my bootloader.
lmortal said:
I own the big tab 20" was able to root using http://forum.xda-developers.com/showthread.php?t=2473747
I did have to unlock the bootloader and tried booting the dream tab recovery from fastboot no dice there so wasn't gonna risk flashing it.
The process took about 20 mins maybe less fully automated it froze at some point so I reset the big tab and tried again at which point kingo program told me I was already rooted download SU was able to update the binary's normal method and been good to go since. Word of warning it does preform a factory reset when you unlock the bootloader so be prepared for that.
Click to expand...
Click to collapse
I've ben trying to root my Big Tab 24". You said you had to unlock the bootloader. I can't get it into bootlad mode or unlock the bootloader. I tried fastboot. I tried every button combination I could think of. (not too many considering it only has three physical buttons) I tried rooting it with Kingo without unlocking the bootloader. Nothing is working. Please help. What am I doing wrong or not doing right?
Fastboot is the boot loader make sure you have USB debugging enabled and connect the tab to a PC you can then use the command "adb reboot-bootloader" the command to unlock is "fastboot OEM unlock"