Develop Bugs

[Q] 【data2sd】i have some troubles~~~555

there're some troubles while data2sd, and it doesn't work.....
please help me！
my G7's infomation:
S-OFF, AlphaRev N1Table HBOOT, SdCard:6.8G+1.2G FATA32
Process：
E:\android-sdk\tools>adb shell
/ # mount /system
mount /system
/ # mount /data
mount /data
/ # mount /sdcard
mount /sdcard
/ # exit
exit
E:\android-sdk\tools>adb push c:\01data /system/etc/init.d
32 KB/s (394 bytes in 0.011s)
E:\android-sdk\tools>adb push c:\busybox-armv6l /system/xbin/busybox
1771 KB/s (1062992 bytes in 0.585s)
E:\android-sdk\tools>adb shell
/ # chmod 755 /system/etc/init.d/01data
chmod 755 /system/etc/init.d/01data
/ # chmod 777 /system/xbin/busybox
chmod 777 /system/xbin/busybox
/ # cd /
cd /
/ # mount /dev/block/mmcblk0p2 /sd-ext
mount /dev/block/mmcblk0p2 /sd-ext
/ # dd if=/dev/zero of=/sd-ext/ext2 bs=1048576
dd if=/dev/zero of=/sd-ext/ext2 bs=1048576
dd: writing '/sd-ext/ext2': No space left on device
1199+0 records in
1197+1 records out
/ # /system/xbin/busybox mke2fs -F -L userdata /sd-ext/ext2
/system/xbin/busybox mke2fs -F -L userdata /sd-ext/ext2
Filesystem label=userdata
OS type: Linux
Block size=4096 (log=2)
Fragment size=4096 (log=2)
76800 inodes, 306639 blocks
15331 blocks (5%) reserved for the super user
First data block=0
Maximum filesystem blocks=4194304
10 block groups
32768 blocks per group, 32768 fragments per group
7680 inodes per group
Superblock backups stored on blocks:
32768, 98304, 163840, 229376, 294912
/ # mkdir /sd
mkdir /sd
/ # /system/xbin/busybox mount -o loop /sd-ext/ext2 /sd
/system/xbin/busybox mount -o loop /sd-ext/ext2 /sd
/ # cd /data
cd /data
/data # cp -a * /sd
cp -a * /sd
/data # cd /
cd /
/ # /system/xbin/busybox umount /sd
/system/xbin/busybox umount /sd
/ # exit
exit
E:\android-sdk\tools>adb reboot
error: closed
BTW,when i reboot the phone,i found the second partition on sdcard is 100% full,why?where is the mistake?

help！help！help！help！help！

This is a question and belongs in q&a, not development.
Sent from my Evil Lair using Doomsday Device

It actually belongs in the Data2SD thread, which in turn IS in ROM Development

Why you don't use Androhero tutorial that I reported on post number five??
It's very simple fast and secure.
Don't fails with it
sent from the future

thx，i'll try

Btw I suggest to use the default mtd structure.
sent from the future

E:\android-sdk\tools>adb reboot
error: closed
this problem may cause by usb drives or recovery?
the drives are all installed ok...

mattiadj said:
Why you don't use Androhero tutorial that I reported on post number five??
It's very simple fast and secure.
Don't fails with it
sent from the future
Click to expand...
Click to collapse
i have a question,in your tutorial, don't need this file busybox?

Busibox may be included in ROM.
Try to install recovery driver from root thread.
sent from the future

[Q] Help Recreate All Partitions?

Hi all,
I am trying to repair an Incredible, that I *think* has missing or corrupt partitions. Can anyone assist me with manually fixing / recreating them? Here is what I've got:
HBOOT 1.02, Unlocked via HtcDev.com
CWM Recovery 5.0.2.0
ADB access
parted command pushed to the device
As soon as I launch CWM, I get the following errors:
E:Can't mount /cache/recovery/command
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/log
E:Can't mount /cache/recovery/last_log
E:Can't open/cache/recovery/last_log
When trying to mount the following partitions, I get these errors:
E:failed to find "datadata" partition to mount at "/datata"
Error mounting /datadata!
Error mounting /cache!
Error mounting /sd-ext! <----- and thus I have no SD Card access, can't install zip files from SD
Error mounting /emmc!
Error mounting /sdcard!
E:Unable to write to ums lunfile (No such file or directory)
I do seem to have a boot, system, and data partition, though I am unsure if they are proper size, format, or location. In adb shell, here are some of the commands I know (and have gleaned from other threads).
/dev/block # ls
loop0 loop3 loop6 mmcblk0p1 mtdblock2 mtdblock5
loop1 loop4 loop7 mtdblock0 mtdblock3 mtdblock6
loop2 loop5 mmcblk0 mtdblock1 mtdblock4 platform
/dev/block # parted mmcblk0
parted mmcblk0
GNU Parted 1.8.8.1.179-aef3
Using /dev/block/mmcblk0
Welcome to GNU Parted! Type 'help' to view a list of commands.
(parted) print
print
print
Model: SD 00000 (sd/mmc)
Disk /dev/block/mmcblk0: 2003MB
Sector size (logical/physical): 512B/512B
Partition Table: msdos
Number Start End Size Type File system Flags
1 1049kB 2003MB 2002MB primary ext3 boot
/dev/block # parted mmcblk0p1
parted mmcblk0p1
GNU Parted 1.8.8.1.179-aef3
Using /dev/block/mmcblk0p1
Welcome to GNU Parted! Type 'help' to view a list of commands.
(parted) print
print
print
Model: Unknown (unknown)
Disk /dev/block/mmcblk0p1: 2002MB
Sector size (logical/physical): 512B/512B
Partition Table: loop
Number Start End Size File system Flags
1 0.00B 2002MB 2002MB ext3
/dev/block # parted mtdblock0
parted mtdblock0
GNU Parted 1.8.8.1.179-aef3
Using /dev/block/mtdblock0
Welcome to GNU Parted! Type 'help' to view a list of commands.
(parted) print
print
print
Error: /dev/block/mtdblock0: unrecognised disk label
...Same result through all 6 mtdblocks
/dev/block # mount -a
mount -a
mount: mounting /dev/block/mmcblk0p2 on /cache failed: No such file or directory
mount: mounting /dev/block/mmcblk1p1 on /sdcard failed: No such file or directory
mount: mounting /dev/block/mmcblk1p2 on /sd-ext failed: No such file or directory
Anyone know what's going on here, and able to help guide me through recreating the proper partition structure?
Thanks in advance!

Also, I am not familiar with the fstab file, but I found the command while researching, and here is the output:
/dev/block # cat /etc/fstab
cat /etc/fstab
/dev/block/mmcblk0p2 /cache auto rw
/dev/block/mmcblk0p1 /data auto rw
/dev/block/mmcblk0p1 /datadata yaffs2 rw
/dev/block/mtdblock3 /system yaffs2 rw
/dev/block/mmcblk1p1 /sdcard vfat rw
/dev/block/mmcblk1p2 /sd-ext auto rw
The "mmcblk1p1" and "mmcblk1p2" don't appear in the /dev/block directory??
/dev/block # ls
ls
loop0 loop3 loop6 mmcblk0p1 mtdblock2 mtdblock5
loop1 loop4 loop7 mtdblock0 mtdblock3 mtdblock6
loop2 loop5 mmcblk0 mtdblock1 mtdblock4 platform

While reading through this post, http://forum.xda-developers.com/showthread.php?t=1819095&page=3, I see a similar behavior in my phone. If I am reading this correctly, my *regular* fstab file needs to be adjusted to include all of the entries that show up in the recovery fstab file? Do I have that right?
Code:
~ # ls /etc/*fstab*
ls /etc/*fstab*
/etc/fstab /etc/recovery.fstab
~ # cat /etc/fstab
cat /etc/fstab
/dev/block/mmcblk0p2 /cache auto rw
/dev/block/mmcblk0p1 /data auto rw
/dev/block/mmcblk0p1 /datadata yaffs2 rw
/dev/block/mtdblock3 /system yaffs2 rw
/dev/block/mmcblk1p1 /sdcard vfat rw
/dev/block/mmcblk1p2 /sd-ext auto rw
~ # cat /etc/recovery.fstab
cat /etc/recovery.fstab
# mount point fstype device [device2]
/misc mtd misc
/recovery mtd recovery
/boot mtd boot
/system yaffs2 system
/datadata yaffs2 datadata
/data ext4 /dev/block/mmcblk0p1 NULL
ext3
/cache ext4 /dev/block/mmcblk0p2 NULL
ext3
/emmc vfat /dev/block/mmcblk0p3
/sdcard vfat /dev/block/mmcblk1p1 /dev/block/mmcblk1
/sd-ext ext4 /dev/block/mmcblk1p2 NULL
ext3
~ # cat /proc/partitions
cat /proc/partitions
major minor #blocks name
31 0 640 mtdblock0
31 1 4608 mtdblock1
31 2 3072 mtdblock2
31 3 253952 mtdblock3
31 4 640 mtdblock4
31 5 40960 mtdblock5
31 6 152576 mtdblock6
179 0 1955840 mmcblk0
179 1 1954816 mmcblk0p1
~ # mount
mount
rootfs on / type rootfs (rw)
tmpfs on /dev type tmpfs (rw,relatime,mode=755)
devpts on /dev/pts type devpts (rw,relatime,mode=600)
proc on /proc type proc (rw,relatime)
sysfs on /sys type sysfs (rw,relatime)
Anyone able to point me in the right direction here?

I'd say flash ruu. You have missing partitions. Whoever had the phone before you messed it up. Mtdblock0 isn't a block device and cannot be managed with parted. Once you try the ruu first (may need s-off to do it) let me know what happens next.
I wouldnt even bother messing with the fstab. The post your talking about is related to swapping the internal and external storage.
Sent from my HTC One using Tapatalk 4

tiny4579 said:
I'd say flash ruu. You have missing partitions. Whoever had the phone before you messed it up. Mtdblock0 isn't a block device and cannot be managed with parted. Once you try the ruu first (may need s-off to do it) let me know what happens next.
I wouldnt even bother messing with the fstab. The post your talking about is related to swapping the internal and external storage.
Sent from my HTC One using Tapatalk 4
Click to expand...
Click to collapse
Hi Tiny, thanks for the assistance. I've been using your Cyanogen 10.1 on my own Dinc and love it. Thanks for your awesome work!
I did try flashing the most recent RUU yesterday from here: shipped-roms.com/index.php?category=android&model=Incredible -- 4.08.605.2, and it went through the motions as if it was working (completed without any errors), but it didnt actually do anything (oddly, it didn't create a log file in the ruu_lof directory either) that I noticed. I tried it one more time right now though, just to be safe, and it failed. This time, it log, and the last entry is <T182509><DEBUG><OUT>FAILED (remote: 99 unknown fail)</OUT>
</DEBUG></T182509>
I didn't think S-OFF would make much difference with the unlocked bootloader, but I'll read up on how to do it. In the meantime, any other ideas? And, again, thanks a lot, I appreciate it greatly.

Lifted this command from another thread as well:
Code:
~ # e2fsck -fy /dev/block/mmcblk0p1
e2fsck -fy /dev/block/mmcblk0p1
e2fsck 1.41.6 (30-May-2009)
/dev/block/mmcblk0p1: recovering journal
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
/dev/block/mmcblk0p1: ***** FILE SYSTEM WAS MODIFIED *****
/dev/block/mmcblk0p1: 14/122400 files (0.0% non-contiguous), 15903/488704 blocks
~ # e2fsck -fy /dev/block/mmcblk0
e2fsck -fy /dev/block/mmcblk0
e2fsck 1.41.6 (30-May-2009)
e2fsck: Superblock invalid, trying backup blocks...
e2fsck: Bad magic number in super-block while trying to open /dev/block/mmcblk0
The superblock could not be read or does not describe a correct ext2
filesystem. If the device is valid and it really contains an ext2
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock:
e2fsck -b 8193 <device>
~ # quit

DavidPhx said:
Hi Tiny, thanks for the assistance. I've been using your Cyanogen 10.1 on my own Dinc and love it. Thanks for your awesome work!
I did try flashing the most recent RUU yesterday from here: shipped-roms.com/index.php?category=android&model=Incredible -- 4.08.605.2, and it went through the motions as if it was working (completed without any errors), but it didnt actually do anything (oddly, it didn't create a log file in the ruu_lof directory either) that I noticed. I tried it one more time right now though, just to be safe, and it failed. This time, it log, and the last entry is <T182509><DEBUG><OUT>FAILED (remote: 99 unknown fail)</OUT>
</DEBUG></T182509>
I didn't think S-OFF would make much difference with the unlocked bootloader, but I'll read up on how to do it. In the meantime, any other ideas? And, again, thanks a lot, I appreciate it greatly.
Click to expand...
Click to collapse
Youll need s-off to flash a downgrade ruu. If your ruu is an upgrade it should work without s-off though I recommend it anyway to make resolving the issue simpler.
Sent from my HTC One using Tapatalk 4

tiny4579 said:
Youll need s-off to flash a downgrade ruu. If your ruu is an upgrade it should work without s-off though I recommend it anyway to make resolving the issue simpler.
Sent from my HTC One using Tapatalk 4
Click to expand...
Click to collapse
Tiny, to achieve S-OFF, I am following Scotty's instructions here: http://androidforums.com/incredible...ot-unlock-downgrade-achieve-s-off-htcdev.html
I am having some difficulty on Step 4, getting an error regarding "is a directory". I noticed if I leave off the trailing slash can get the command to work and adb will push the file, but even so it fails in the next step. I will keep reading to thread to see if anyone else had similar troubles.
Code:
C:\Users\David\Downloads\ADB-Tools>adb push flash_image /data/local/
failed to copy 'flash_image' to '/data/local/': Is a directory
C:\Users\David\Downloads\ADB-Tools>adb push flash_image /data/local
1105 KB/s (76044 bytes in 0.067s)
C:\Users\David\Downloads\ADB-Tools>adb push mtd0.img /sdcard/
1556 KB/s (655360 bytes in 0.411s)
C:\Users\David\Downloads\ADB-Tools>adb shell
~ # chmod 0755 /data/local/flash_image
chmod 0755 /data/local/flash_image
chmod: /data/local/flash_image: Not a directory
C:\Users\David\Downloads\ADB-Tools>adb shell
~ # cd /data/local
cd /data/local
/sbin/sh: cd: can't cd to /data/local
~ # cd /data
cd /data
/data # ls
ls
local
/data # cd local
cd local
/sbin/sh: cd: can't cd to local
/data # ls
ls
local
Any ideas on how to proceed?

Try adb shell mkdir /data/local though that folder should exist. If you do just adb shell do you get a # or $ prompt?
Sent from my Nexus 7 using Tapatalk 4

tiny4579 said:
Try adb shell mkdir /data/local though that folder should exist. If you do just adb shell do you get a # or $ prompt?
Sent from my Nexus 7 using Tapatalk 4
Click to expand...
Click to collapse
The mkdir command executed without any errors, and I do have a # sign...indicating phone is rooted and has su perms if I understand correctly?
Code:
C:\Users\David\Downloads\ADB-Tools>adb shell mkdir /data/local
C:\Users\David\Downloads\ADB-Tools>adb shell
~ #

After issueing that mkdir command like you suggested, I tried again where I left off in step 4, and was able to proceed with the rest of the instructions in step 4 and get Froyo loaded and running. Making good progress here, thanks Tiny!
The writing of the PB31IMG.zip file:
Code:
C:\Users\David\Downloads\ADB-Tools>fastboot flash zip PB31IMG.zip
sending 'zip' (176625 KB)...
OKAY [ 25.167s]
writing 'zip'...
(bootloader) adopting the signature contained in this image...
(bootloader) signature checking...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
(bootloader) checking custom ID...
(bootloader) checking main version...
(bootloader) start image[hboot] unzipping for pre-update check...
(bootloader) start image[hboot] unzipping & flushing...
(bootloader) [RUU]UZ,hboot,0
(bootloader) [RUU]UZ,hboot,100
(bootloader) start image[radio] unzipping & flushing...
(bootloader) [RUU]UZ,radio,0
(bootloader) [RUU]UZ,radio,9
(bootloader) [RUU]UZ,radio,18
(bootloader) [RUU]UZ,radio,23
(bootloader) [RUU]UZ,radio,32
(bootloader) [RUU]UZ,radio,41
(bootloader) [RUU]UZ,radio,46
(bootloader) [RUU]UZ,radio,51
(bootloader) [RUU]UZ,radio,60
(bootloader) [RUU]UZ,radio,69
(bootloader) [RUU]UZ,radio,78
(bootloader) [RUU]UZ,radio,87
(bootloader) [RUU]UZ,radio,97
(bootloader) [RUU]UZ,radio,100
(bootloader) [RUU]WP,radio,0
(bootloader) [RUU]WP,radio,7
(bootloader) [RUU]WP,radio,16
(bootloader) [RUU]WP,radio,21
(bootloader) [RUU]WP,radio,26
(bootloader) [RUU]WP,radio,35
(bootloader) [RUU]WP,radio,40
(bootloader) [RUU]WP,radio,45
(bootloader) [RUU]WP,radio,50
(bootloader) [RUU]WP,radio,100
(bootloader) start image[boot] unzipping & flushing...
(bootloader) [RUU]UZ,boot,0
(bootloader) [RUU]UZ,boot,43
(bootloader) [RUU]UZ,boot,83
(bootloader) [RUU]UZ,boot,100
(bootloader) [RUU]WP,boot,0
(bootloader) [RUU]WP,boot,42
(bootloader) [RUU]WP,boot,85
(bootloader) [RUU]WP,boot,100
(bootloader) start image[recovery] unzipping & flushing...
(bootloader) [RUU]UZ,recovery,0
(bootloader) [RUU]UZ,recovery,20
(bootloader) [RUU]UZ,recovery,43
(bootloader) [RUU]UZ,recovery,73
(bootloader) [RUU]UZ,recovery,99
(bootloader) [RUU]UZ,recovery,100
(bootloader) [RUU]WP,recovery,0
(bootloader) [RUU]WP,recovery,20
(bootloader) [RUU]WP,recovery,40
(bootloader) [RUU]WP,recovery,60
(bootloader) [RUU]WP,recovery,80
(bootloader) [RUU]WP,recovery,100
(bootloader) start image[system] unzipping & flushing...
(bootloader) [RUU]UZ,system,0
(bootloader) [RUU]UZ,system,6
(bootloader) [RUU]UZ,system,12
(bootloader) [RUU]UZ,system,19
(bootloader) [RUU]UZ,system,25
(bootloader) [RUU]UZ,system,32
(bootloader) [RUU]UZ,system,39
(bootloader) [RUU]UZ,system,45
(bootloader) [RUU]UZ,system,51
(bootloader) [RUU]UZ,system,58
(bootloader) [RUU]UZ,system,64
(bootloader) [RUU]UZ,system,71
(bootloader) [RUU]UZ,system,78
(bootloader) [RUU]UZ,system,84
(bootloader) [RUU]UZ,system,89
(bootloader) [RUU]WP,system,0
(bootloader) [RUU]WP,system,89
(bootloader) [RUU]UZ,system,89
(bootloader) [RUU]UZ,system,89
(bootloader) [RUU]UZ,system,90
(bootloader) [RUU]UZ,system,91
(bootloader) [RUU]UZ,system,92
(bootloader) [RUU]UZ,system,93
(bootloader) [RUU]UZ,system,94
(bootloader) [RUU]UZ,system,94
(bootloader) [RUU]UZ,system,96
(bootloader) [RUU]UZ,system,96
(bootloader) [RUU]UZ,system,97
(bootloader) [RUU]UZ,system,98
(bootloader) [RUU]UZ,system,99
(bootloader) [RUU]UZ,system,100
(bootloader) [RUU]WP,system,89
(bootloader) [RUU]WP,system,89
(bootloader) [RUU]WP,system,90
(bootloader) [RUU]WP,system,91
(bootloader) [RUU]WP,system,92
(bootloader) [RUU]WP,system,93
(bootloader) [RUU]WP,system,94
(bootloader) [RUU]WP,system,94
(bootloader) [RUU]WP,system,95
(bootloader) [RUU]WP,system,96
(bootloader) [RUU]WP,system,97
(bootloader) [RUU]WP,system,98
(bootloader) [RUU]WP,system,99
(bootloader) [RUU]WP,system,100
(bootloader) start image[sp1] unzipping & flushing...
(bootloader) [RUU]UZ,sp1,0
(bootloader) [RUU]UZ,sp1,100
(bootloader) [RUU]WP,sp1,0
(bootloader) [RUU]WP,sp1,100
OKAY [153.388s]
finished. total time: 178.557s
C:\Users\David\Downloads\ADB-Tools>
C:\Users\David\Downloads\ADB-Tools>fastboot reboot
rebooting...
finished. total time: 0.097s
C:\Users\David\Downloads\ADB-Tools>

Made it through Steps 5 and 6 successfully, and on to Step 7...However, here we run into problems once again. I copied the Superuser and Unrevoked-Forever zip files to my sd card (which I know is good, because my laptop recognized it immediately and I can see all of the default folders the phone itself created), placed it in the phone, and booted to recovery.
CWM starts up, but launching it I am immediately greeted by the same set of errors as before:
E:Can't mount /cache/recovery/command
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/log
E:Can't mount /cache/recovery/last_log
E:Can't open/cache/recovery/last_log
Choosing "install zip from sd card --> choose zip from sdcard" gives me an error that states: "E:Can't mount /sdcard/". "choose zip from internal sdcard" gives me an error that states "E:Can't mount /emmc/"
I still have adb access, so do you know if there is a way to install the Unrevoked Forever zip file through an adb command instead perhaps?

DavidPhx said:
Made it through Steps 5 and 6 successfully, and on to Step 7...However, here we run into problems once again. I copied the Superuser and Unrevoked-Forever zip files to my sd card (which I know is good, because my laptop recognized it immediately and I can see all of the default folders the phone itself created), placed it in the phone, and booted to recovery.
CWM starts up, but launching it I am immediately greeted by the same set of errors as before:
E:Can't mount /cache/recovery/command
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/log
E:Can't mount /cache/recovery/last_log
E:Can't open/cache/recovery/last_log
Choosing "install zip from sd card --> choose zip from sdcard" gives me an error that states: "E:Can't mount /sdcard/". "choose zip from internal sdcard" gives me an error that states "E:Can't mount /emmc/"
I still have adb access, so do you know if there is a way to install the Unrevoked Forever zip file through an adb command instead perhaps?
Click to expand...
Click to collapse
There isn't a way to sideload AFAIK with the clockworkmod recovery version you have. Do you have a MicroSD card laying around? If you do you can push it to your device. That's how I'd recommend pushing it to your device. If you check around the dev forums there should be a clockworkmod 6 version that supports sideload though. The next step once S-OFFing will be to manually partition your system as in your first or second post I saw a 2GB single partition which isn't correct. Let me know when you're ready for that.

So this is what parted /dev/block/mmcblk0 (your main mmc partition with /cache /data and /emmc) should look like:
Code:
~ # parted /dev/block/mmcblk0
GNU Parted 1.8.8.1.179-aef3
Using /dev/block/mmcblk0
Welcome to GNU Parted! Type 'help' to view a list of commands.
(parted) print
print
Model: MMC HYNIX (sd/mmc)
Disk /dev/block/mmcblk0: 8095MB
Sector size (logical/physical): 512B/512B
Partition Table: msdos
Number Start End Size Type File system Flags
1 8192B 797MB 797MB primary ext3
2 797MB 1007MB 210MB primary ext3
3 1007MB 8095MB 7088MB primary fat32 lba
Also. error mounting /sd-ext is fine. You don't have an ext2 or ext3 sdcard partition. That is fine. Error mounting /sdcard is different.
I'd suggest reading up on parted. If I find a helpful thread on parted and Android I'll let you know but it just takes a bit of searching which it sounds like you're quite capable of doing already.

tiny4579 said:
There isn't a way to sideload AFAIK with the clockworkmod recovery version you have. Do you have a MicroSD card laying around? If you do you can push it to your device. That's how I'd recommend pushing it to your device. If you check around the dev forums there should be a clockworkmod 6 version that supports sideload though. The next step once S-OFFing will be to manually partition your system as in your first or second post I saw a 2GB single partition which isn't correct. Let me know when you're ready for that.
Click to expand...
Click to collapse
Alright, I found the CWM 6 build you were referring to in the Dev forum, flashed it, booted to recovery, and attempted a sideload of unrevoked-forever.zip. Unfortunately, it was a no go, and generated errors:
C:\Users\David\Downloads\adb1031>adb sideload unrevoked-forever.zip
adb server is out of date. killing...
* daemon started successfully *
sending: 'unrevoked-forever.zip' 100%
Code:
failed to open device control: No such file or directory
E:Can't mount /cache/recovery/last_install
E:failed to open last_install: No such file or directory
Finding update package...
Opening update package...
Installing update...
E:Error in /tmp/update.zip
(Status 0)
Installation aborted
I'll do my homework and research the errors.
Meanwhile, you asked if I have a microSD card around...I have one in the phone, but Recovery won't mount it or read it. Interestingly, the phone will mount and read it when in Froyo.

Hey, go to the HBOOT menu and check if it has S-OFF. It might have it already. To get there hold volume down while turning on the phone. It will say S-OFF if it's S-OFF in the upper left of the screen.
That status 0 error is likely related to the update-binary in the zip. You're actually going to be best flashing that with the former recovery. After checking if you have S-OFF, we should try to fix the partitions next.
You never did mention the symptoms of your partition issues. If you can boot into a ROM, let me know the output of the mount command from a terminal emulator or mount from an adb shell.

tiny4579 said:
Hey, go to the HBOOT menu and check if it has S-OFF. It might have it already. To get there hold volume down while turning on the phone. It will say S-OFF if it's S-OFF in the upper left of the screen.
That status 0 error is likely related to the update-binary in the zip. You're actually going to be best flashing that with the former recovery. After checking if you have S-OFF, we should try to fix the partitions next.
You never did mention the symptoms of your partition issues. If you can boot into a ROM, let me know the output of the mount command from a terminal emulator or mount from an adb shell.
Click to expand...
Click to collapse
Tiny, I apologize if I missed some information along the way that was important. I thought I was including all pertinent info, but without a firm grasp on the problem I may have missed some.
In HBOOT, the phone still shows S-ON. I can go back down to CWM 5.0.2.0, but that version does not have Sideload capability. Since I can't get the phone to read from the internal memory or external micro sd card while in Recovery, that was the reason for going up to CWM 6 and attempting to load unrevoked-forever.zip via Sideload.
When I get home, I will install Terminal Emulator, boot to Froyo, and let you know the results of the 'mount' command.
In the meantime, I will begin doing my research and learning about parted.

DavidPhx said:
Tiny, I apologize if I missed some information along the way that was important. I thought I was including all pertinent info, but without a firm grasp on the problem I may have missed some.
In HBOOT, the phone still shows S-ON. I can go back down to CWM 5.0.2.0, but that version does not have Sideload capability. Since I can't get the phone to read from the internal memory or external micro sd card while in Recovery, that was the reason for going up to CWM 6 and attempting to load unrevoked-forever.zip via Sideload.
When I get home, I will install Terminal Emulator, boot to Froyo, and let you know the results of the 'mount' command.
In the meantime, I will begin doing my research and learning about parted.
Click to expand...
Click to collapse
In Froyo, here is the output from a 'mount' command:
$ mount
mount
rootfs / rootfs ro,relatime 0 0
tmpfs /dev tmpfs rw,relatime,mode=755 0 0
devpts /dev/pts devpts rw,relatime,mode=600 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,relatime 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
tmpfs /mnt/asec tmpfs rw,relatime,mode=755,gid=1000 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
/dev/block/mtdblock3 /system yaffs2 ro,relatime 0 0
/dev/block/mtdblock6 /data yaffs2 rw,nosuid,noatime,nodiratime 0 0
/dev/block/mtdblock5 /cache yaffs2 rw,nosuid,nodev,noatime,nodiratime 0 0
tmpfs /app-cache tmpfs rw,relatime,size=8192k 0 0
/dev/block/vold/179:1 /mnt/sdcard vfat rw,dirsync,nosuid,nodev,noexec,relatime,u
id=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,iocharset
=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/vold/179:1 /mnt/secure/asec vfat rw,dirsync,nosuid,nodev,noexec,relat
ime,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,ioch
arset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
tmpfs /mnt/sdcard/.android_secure tmpfs ro,relatime,size=0k,mode=000 0 0
This varies significantly from the 'mount' command run from Recovery:
~ # mount
mount
rootfs on / type rootfs (rw)
tmpfs on /dev type tmpfs (rw,relatime,mode=755)
devpts on /dev/pts type devpts (rw,relatime,mode=600)
proc on /proc type proc (rw,relatime)
sysfs on /sys type sysfs (rw,relatime)

Ok, comparing the two, and some research on the 'mount' command led to me to the following:
Code:
~ # mount /dev/block/mtdblock5 /cache
mount /dev/block/mtdblock5 /cache
~ # cd dev/block
cd dev/block
/dev/block # ls
ls
loop0 loop3 loop6 mmcblk0p1 mtdblock2 mtdblock5
loop1 loop4 loop7 mtdblock0 mtdblock3 mtdblock6
loop2 loop5 mmcblk0 mtdblock1 mtdblock4 platform
/dev/block # mount /dev/block/mmcblk0p1 /sdcard
mount /dev/block/mmcblk0p1 /sdcard
/dev/block #
I was able to successfully mount the cache and sdcard partitions! This cleared up the CWM errors, and I was able to use the "Install zip from sdcard" option in CWM to finally load the superuser.zip and unrevoked-forever.zip files. Rebooted to hboot, and I am now S-OFF!

DavidPhx said:
Ok, comparing the two, and some research on the 'mount' command led to me to the following:
Code:
~ # mount /dev/block/mtdblock5 /cache
mount /dev/block/mtdblock5 /cache
~ # cd dev/block
cd dev/block
/dev/block # ls
ls
loop0 loop3 loop6 mmcblk0p1 mtdblock2 mtdblock5
loop1 loop4 loop7 mtdblock0 mtdblock3 mtdblock6
loop2 loop5 mmcblk0 mtdblock1 mtdblock4 platform
/dev/block # mount /dev/block/mmcblk0p1 /sdcard
mount /dev/block/mmcblk0p1 /sdcard
/dev/block #
I was able to successfully mount the cache and sdcard partitions! This cleared up the CWM errors, and I was able to use the "Install zip from sdcard" option in CWM to finally load the superuser.zip and unrevoked-forever.zip files. Rebooted to hboot, and I am now S-OFF!
Click to expand...
Click to collapse
Awesome, time to parted. Clearly from your information above I can tell a few things. 1. You have only one partition in mmcblk0. You should have 3. One for /data, one for /cache and one for /emmc. That will need to be fixed with parted. Secondly, the system seems to be falling back to the mtdblock partitions for /data and /cache. mtd should be /data/data and /system with /cache on mmcblk. Also, it doesn't seem to be recognizing your sdcard at all as that shows up as mmcblk1p1. Your sdcard is formatted as FAT or FAT32 correct?
Anyway, in recovery do the following
Code:
#parted /dev/block/mmcblk0
(parted) print
That should show you what partitions you have. Take note of the value for end for the last listed partition (you will only have one) What you'll want to do now is delete it.
Code:
(parted) rm 1
If prompted type i for ignore.
Now time to re-create them
Code:
(parted) mkpartfs primary ext3 8192B 797MB
(parted) mkpartfs primary ext3 797MB 1007MB
(parted) mkpartfs primary fat32 1007MB "end-size from the print step" - without the quotes
If you're unsure or confused, hold off on the rm and mkpartfs steps or do them one at a time with a print in between to list the current setup.

nexus with broken file system, cannot wipe

Hi everybody,
I'm in deep troubles with my nexus (maguro).
Yesterday, it started to reboot after showing for about 5-10 seconds the lock screen.
the phone is rooted, Iand the last rom (cyanogenmod) was running stable in the last 6 months.
twrp 2.8.0.1 was installed, so I Rebooted to fastboot to flash the 2.8.6.0.
And then the weird part begins:
it's like every partition is read only, but from the mount command it doesn't look like it.
flashing the new recovery is a success, but after reboot the 2.8.0.1 is still there.
factory reset successful, and everything is like before.
wiping sdcard, nothing happens.
if I try to create a backup in twrp, it fails after 20 seconds or so. (I've copied everything to the pc using the pull command in adb).
Try to fix or to change the partitions filesystem in twrp doesn't change anything.
I tried also to change the file system in parted, through the adb shell,this happens:
Code:
~ # ←[6nparted /dev/block/mmcblk0p12 mkfs ext2
parted /dev/block/mmcblk0p12 mkfs ext2
Warning: The existing file system will be destroyed and all data on the
partition will be lost. Do you want to continue?
parted: invalid token: ext2
Yes/No? yes
yes
yes
Partition number? 1
1
1
File system type? [ext2]?
Error: File system was not cleanly unmounted! You should run e2fsck. Modifying
an unclean file system could cause severe corruption.
Ignore/Cancel? i
i
i
Error: File system has an incompatible feature enabled. Compatible features are
has_journal, dir_index, filetype, sparse_super and large_file. Use tune2fs or
debugfs to remove features.
You found a bug in GNU Parted! Here's what you have to do:
Don't panic! The bug has most likely not affected any of your data.
Help us to fix this bug by doing the following:
Check whether the bug has already been fixed by checking
the last version of GNU Parted that you can find at:
...
Please check this version prior to bug reporting.
If this has not been fixed yet or if you don't know how to check,
please visit the GNU Parted website:
...
for further information.
Your report should contain the version of this release (1.8.8.1.179-aef3)
along with the error message below, the output of
parted DEVICE unit co print unit s print
and the following history of commands you entered.
Also include any additional information about your setup you
consider important.
Error: SEGV_MAPERR (Address not mapped to object)
Aborted
and of course nothing changes.
so, I have access to adb in recovery and to fastboot, there is a way to wipe completely the filesystem and start from scratch, or load a different kernel, that would help?
If I send with adb push a new rom to the sdcard, twrp fails and at the next reboot the files disappear.
this is my mount result:
Code:
~ # ←[6nmount
mount
rootfs on / type rootfs (rw)
tmpfs on /dev type tmpfs (rw,seclabel,nosuid,relatime,mode=755)
devpts on /dev/pts type devpts (rw,seclabel,relatime,mode=600)
proc on /proc type proc (rw,relatime)
sysfs on /sys type sysfs (rw,seclabel,relatime)
selinuxfs on /sys/fs/selinux type selinuxfs (rw,relatime)
tmpfs on /tmp type tmpfs (rw,seclabel,relatime)
/dev/block/mmcblk0p11 on /cache type ext4 (rw,seclabel,relatime,user_xattr,barri
er=1,data=ordered)
/dev/block/mmcblk0p12 on /data type ext4 (rw,seclabel,relatime,user_xattr,barrie
r=1,data=writeback)
/dev/block/mmcblk0p12 on /sdcard type ext4 (rw,seclabel,relatime,user_xattr,barr
ier=1,data=writeback)
/dev/block/mmcblk0p10 on /system type ext4 (rw,seclabel,relatime,user_xattr,barr
ier=1,data=ordered)
and remounting in rw the partitions has no effect.
Even the parted, e2fsck, etc files disappear from /sbin after each reboot.
thank you
edit:
Having a second nexus, I could take a look at the partitions, and the difference seems to be the data=writeback options.
I'm looking for a procedure to make them "ordered" as the other phone.
edit2:
Code:
/tmp # ←[6ntune2fs -l /dev/block/mmcblk0p12 | grep features
tune2fs -l /dev/block/mmcblk0p12 | grep features
__bionic_open_tzdata: couldn't find any tzdata when looking for localtime!
__bionic_open_tzdata: couldn't find any tzdata when looking for GMT!
__bionic_open_tzdata: couldn't find any tzdata when looking for posixrules!
Filesystem features: has_journal ext_attr resize_inode filetype needs_recov
ery extent sparse_super large_file
/tmp # ←[6ne2fsck -f /dev/block/mmcblk0p12
e2fsck -f /dev/block/mmcblk0p12
e2fsck 1.42.9 (28-Dec-2013)
/dev/block/mmcblk0p12: recovering journal
Superblock needs_recovery flag is clear, but journal has data.
Run journal anyway<y>? y
y
yes
e2fsck: unable to set superblock flags on /dev/block/mmcblk0p12
/dev/block/mmcblk0p12: ********** WARNING: Filesystem still has errors *********
*
/tmp #
/tmp # ←[6ntune2fs -O ^has_journal /dev/block/mmcblk0p12
tune2fs -O ^has_journal /dev/block/mmcblk0p12
tune2fs 1.42.9 (28-Dec-2013)
The needs_recovery flag is set. Please run e2fsck before clearing
the has_journal flag.
Stuck here at the moment, cannot set superblock flags..
edit3:
Tested every possible superblock position, no luck.
I'm starting to think that the internal memory could be dead, but the phone in fastboot and recovery mode works fine.
I forgot to say that I've tried also the fastboot -w command, it works a lot (about 270 seconds) but no effect.

Unbricking my Fonepad7 k00e with a currupted partition.

Here are the facts:
my tablet was throwing errors about google app and google search box crashing. I restarted the tablet and it got stuck at boot loop.
K00E with firmware,UL-K00E-WW-7.6.0.0-user, not rooted.
what I've tried:
factory reset under droidboot:
Code:
E:failed to mount /cache (Invalid argument)
unable to mount /cache! we skip check debricking
SD download of the latest RAW file under under droidboot:
again
Code:
E:failed to mount /cache (Invalid argument)
unable to mount /cache!
Installing the firmware zip file using custom recovery:
I used this to run CWM. I cleared cache, user data, factory reset and then tried to install using external SD zip file.
Code:
failed to mount /dev/block/mmcblk0p8 at /system: Invalid argument
trying to re partition the internal SD:
from here
I tried to run parted to fix it but I am getting this
Code:
~ # parted
parted
/sbin/parted: line 1: syntax error: unexpected word (expecting ")")
~ #
I added no arguments to parted, and still it is giving me this error. I even tried pushing another copy of parted and chmodding it to execute it, still the same thing occurs.
I also tried this
on running th second command I have
Code:
~ # tune2fs -O extents,uninit_bg,dir_index -C 1 /dev/block/mmcblk0p8
tune2fs -O extents,uninit_bg,dir_index -C 1 /dev/block/mmcblk0p8
tune2fs 1.41.11 (14-Mar-2010)
tune2fs: Bad magic number in super-block while trying to open /dev/block/mmcblk0
p8
Couldn't find valid filesystem superblock.
~ #
any ideas how to move forward?

change system partition from read-only to read-write

Dear to all, I have a samsung galaxy s9 g9600/ds (snapdragon) with last official firmware android 10 and rooted with magisk and with custom kernel of klabit87. Even if the device is rooted, system partition it's read-only (seems that is related to Android 10) but if I try to install and execute systemrw ( https://www.systemrw.com/ ), I 've message "Fatal error! No super partition detected". But if I run "cat /vendor/etc/*fstab*" I'll get the following outputs
Code:
:/ # cat /vendor/etc/*fstab*
# Android fstab file.
# 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
#TODO: Add 'check' as fs_mgr_flags with data partition.
# Currently we dont have e2fsck compiled. So fs check would failed.
#<src> <mnt_point> <type> <mnt_flags and options> <fs_mgr_flags>
/dev/block/bootdevice/by-name/system /system ext4 ro,errors=panic wait
/dev/block/bootdevice/by-name/userdata /data ext4 noatime,nosuid,nodev,noauto_da_alloc,discard,journal_checksum,data=ordered,errors=panic wait,check,encryptable=footer,quota,reservedsize=128M
#/dev/block/bootdevice/by-name/vendor /vendor ext4 ro,barrier=1,discard wait
/dev/block/bootdevice/by-name/persist /mnt/vendor/persistext4 noatime,nosuid,nodev,noauto_da_alloc,discard,journal_checksum,data=ordered,errors=panic wait,check
/dev/block/bootdevice/by-name/cache /cache ext4 noatime,nosuid,nodev,noauto_da_alloc,discard,journal_checksum,data=ordered,errors=panic wait,check
/dev/block/bootdevice/by-name/apnhlos /vendor/firmware_mnt vfat ro,context=u:object_r:firmware_file:s0,shortname=lower,uid=0,gid=1000,dmask=227,fmask=337 wait
/dev/block/bootdevice/by-name/modem /vendor/firmware-modem vfat ro,context=u:object_r:firmware_file:s0,shortname=lower,uid=0,gid=1000,dmask=227,fmask=337 wait
/dev/block/bootdevice/by-name/dsp /vendor/dsp ext4 ro,nosuid,nodev,barrier=1 wait
/dev/block/bootdevice/by-name/efs /mnt/vendor/efs extnoatime,nosuid,nodev,noauto_da_alloc,discard,journal_checksum,data=ordered,errors=panic wait,check
/dev/block/bootdevice/by-name/dqmdbg /mnt/vendor/dqmdbg ext4 noatime,nosuid,nodev,noauto_da_alloc,discard,journal_checksum,data=ordered,errors=panic wait,check
/dev/block/bootdevice/by-name/carrier /carrier extnoatime,nosuid,nodev,noauto_da_alloc,discard,journal_checksum,data=ordered,errors=panic defaults,nofail,check
#
# Need to have this entry in here even though the mount point itself is no longer needed.
# The update_engine code looks for this entry in order to determine the boot device address
# and fails if it does not find it.
/dev/block/bootdevice/by-name/misc /misc emmc defaults defaults
# /dev/block/bootdevice/by-name/nad_refer /nad_refer ext4 noatime,nosuid,nodev,noauto_da_alloc,discard,journal_checksum,data=ordered,errors=panic wait,check,formattable,factoryuse
# VOLD :: fstab.qcom
/dev/block/bootdevice/by-name/hidden /preload extnoatime,nosuid,nodev,noauto_da_alloc,discard,journal_checksum,data=ordered,errors=panic voldmanaged=preload:auto,check
/devices/platform/soc/8804000.sdhci/mmc_host/mmc* auto vfat defaults voldmanaged=sdcard:auto
/devices/platform/soc/a600000.ssusb/a600000.dwc3/xhci-hcd.0.auto/usb* auto auto defaults voldmanaged=usb:auto
# TODO: Needs to be checked by memory part
# /dev/block/zram0 none swap defaults zramsize=1073741824
:/ #
so system partition is read-only and I can't use app debloat or Link2SD app. Somebody have found a solution to this problem ?
p.s.: the same utility throw error message about dm-verity and dm-verification: "ERROR: Data from 'vbmeta' does not look like a vbmeta header" ... so I can know if verity and verification are disabled ?
In the install of the firmware and root I have made the followings steps:
in download mode: Odin install Android 10 stock firmware G9600ZHS9FVA4 from here https://samfw.com/firmware/SM-G9600/TGY
check and disable oembootloader
Reboot
in downlaod mode Odin install TWRP
Reboot into TWRP (recovery mode)
Install multidisabler-samsung-2.2_klabit
Install forceencrypt_remover_Q
Format data partition
reboot to recovery
Install g9600_klabit_q_v6.3
Install Magisk-v26.1
reboot to system
there is something that I have wrong?