Hello everyone!
I am (until recently) happy user of a Galaxy Note II N7105. And because it already did everything I needed, I never rooted it, installed CWN/TWRP or flashed a custom ROM. It is 4.1.2 (Hong Kong) version and had only OTA updates until now.
Problem description:
At some point I ran out of internal storage about which the system notified me. I deleted some stuff and rebooted - and then it got stuck in a boot loop. That is after the initial splash screen, it repeats the pretty blue/purple swoosh animation with SAMSUNG indefinitely (at least 20min, battery pulled after that).
As for now, I can get into RECOVERY MODE and DOWNLOAD MODE. Because I still have important data on the internal sd, I don't want to wipe the data/factory reset it. My goal now is just to access the internal storage and extract the data stored on it.
What I have tried:
After installing the drivers I could connect my phone with my laptop. From there I could access my phone via adb
Code:
>adb devices
List of devices attached
42f71b0bf29aaf97 recovery
where I entered the shell (no root --> no su rights) to access all the data and, if possible, use adb pull to copy it to my laptop. But somehow, the two folders sdcard and sdcard1 are empty:
Code:
>adb shell
[email protected]:/ $ ls
ls
cache
data
default.prop
dev
efs
etc
fstab.smdk4x12
init
init.rc
lib
lpm.rc
preload
proc
res
root
sbin
sdcard
sdcard1
sys
system
tmp
ueventd.goldfish.rc
ueventd.rc
ueventd.smdk4x12.rc
[email protected]:/ $ cd sdcard
cd sdcard
[email protected]:/sdcard $ ls
ls
[email protected]:/sdcard $ cd ../sdcard1
cd ../sdcard1
[email protected]:/sdcard1 $ ls
ls
[email protected]:/sdcard1 $
So I was wondering if the internal sdcard (suspect it should be /sdcard) needed to be mounted first, but I could not find a mount point to do so:
Code:
[email protected]:/sdcard1 $ mount
mount
rootfs / rootfs rw 0 0
tmpfs /dev tmpfs rw,nosuid,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
/dev/block/mmcblk0p12 /cache ext4 rw,nodev,noatime,nodiratime,barrier=1,data=ord
ered 0 0
/dev/block/mmcblk0p13 /system ext4 rw,nodev,noatime,nodiratime,barrier=1,data=or
dered 0 0
==> Is there a way to mount/access the internal sd card from recovery?I also tried to simple use the command adb pull so that it would copy everything. sadly, it only copied the two folders /sys and /system which are no use to me.
What I have also tried:
Install stock ROMS of 4.1.2 and 4.3 from external sd, via ODIN and adb sideload
GT-N7105_TGY_1_20121026091349_N7105ZHALJ4.zip
NEE-N7105XXUEMK5-20131119111744.zip
(and several others, accidentally also ones for N7100 which also didn't work)but it resulted in E: signature verification failed
Install CWM and TWRP from external sd and ODIN but both also ended up in E: signature verification failed
Kies: But this somehow always entails a factory reset/wipe data which I want to avoid
==> Where can I get an original 4.1.2 stock ROM that is signed by Samsung?
I'm open to whatever approaches to get the data.
My thought is: Once it is connected to the laptop, can't I access it as an external hard drive? Any program to do that?
Any help is greatly appreciated!
mrmuhkuh
In reference to the new storage configuration scheme mentioned in this thread
http://forum.xda-developers.com/showpost.php?p=54537828&postcount=677
I would like to create a new discussion for people who already implemented the re-partitioning of their phones following this method
http://forum.xda-developers.com/wiki/Fairphone_Fairphone/Guides#How_to_partition_your_Fairphone
Please share your experience and confirm if the re-partitioning needs to be reverted prior to implementing the new storage scheme which uses fuse.
Donat.Callens said:
I would like to create a new discussion for people who already implemented the re-partitioning of their phones following this method
http://forum.xda-developers.com/wiki/Fairphone_Fairphone/Guides#How_to_partition_your_Fairphone
Please share your experience and confirm if the re-partitioning needs to be reverted prior to implementing the new storage scheme which uses fuse.
Click to expand...
Click to collapse
Used that method, worked like a charm. Since I'm using AOSP and there have been zero updates for it, I probably won't reformat unless Fairphone starts updating their AOSP OS as well. Will update this post when/if they do.
to repartition or not to repartition
How about people with a repartitioned phone that applied the new storage scheme? Should we revert back to 1GB for the /data partition beforehand?
Donat.Callens said:
How about people with a repartitioned phone that applied the new storage scheme? Should we revert back to 1GB for the /data partition beforehand?
Click to expand...
Click to collapse
Hello, The partition upgrader rewrites MBR/EBR1/EBR2 *after* performing the update to the /system partition. It assumes the /system partition is not altered. I have not tried modifying the partition layout using the methods discussed on this forum (modifying the extended master boot record). As a result of the upgrade EBR2 is no longer used but remains present. MBR is not altered so only EBR2 and the PMT partition are modified before the cache and data partition are formatted. If only /data and the FAT partition are modified you should be fine. These are at the "end" of the disk.
I previously tried to download the APK from the link on the WIKI bellow but ended up downloading the wrong file(addware from the hosting company?) this is where I gave up.
http://forum.xda-developers.com/wiki/Fairphone_Fairphone/Guides#How_to_partition_your_Fairphone
download the repartitioning tool
_keesj said:
I previously tried to download the APK from the link on the WIKI bellow but ended up downloading the wrong file(addware from the hosting company?) this is where I gave up.
http://forum.xda-developers.com/wiki/Fairphone_Fairphone/Guides#How_to_partition_your_Fairphone
Click to expand...
Click to collapse
Here is the original thread with the tool:
http://www.movilesdualsim.com/tema/...ilmente-data-apps-com-4gb-8gb-16gb-rom.31769/
This site refers to another download links to the same file:
http://www.china-devices.com/Thread-Tool-App-for-repartitioning-MTK-6589-Memory
As sear for Meteos MTK6589 will pop up many sites where it is to be found.
Donat.Callens said:
Here is the original thread with the tool:
http://www.movilesdualsim.com/tema/...ilmente-data-apps-com-4gb-8gb-16gb-rom.31769/
Click to expand...
Click to collapse
The original thread explains that you should perform a backup of EBR1 and EBR2 for safety. I assume this means only those two are modified. Could this mean we can apply the new cherry partitioning scheme on a re-partitioned phone without prior modification?
Note: hereby the mentionned commands for the backup
su
dd if=/dev/ebr1 of=/sdcard/EBR1 bs=512 count=1
dd if=/dev/ebr2 of=/sdcard/EBR2 bs=512 count=1
Donat.Callens said:
The original thread explains that you should perform a backup of EBR1 and EBR2 for safety. I assume this means only those two are modified. Could this mean we can apply the new cherry partitioning scheme on a re-partitioned phone without prior modification?
Note: hereby the mentionned commands for the backup
su
dd if=/dev/ebr1 of=/sdcard/EBR1 bs=512 count=1
dd if=/dev/ebr2 of=/sdcard/EBR2 bs=512 count=1
Click to expand...
Click to collapse
I changed my partition using the above tool and was able to perform a 1.3 -> 1.6 -> 1.6 FUSE update afterwards. This is not an endorsement but it does seam to work.
it did not seem to work for me
_keesj said:
I changed my partition using the above tool and was able to perform a 1.3 -> 1.6 -> 1.6 FUSE update afterwards. This is not an endorsement but it does seam to work.
Click to expand...
Click to collapse
I'm afraid I must report otherwise from my personal experience. I had previously re-partitioned my phone with a 4GB internal space storage. When applying the new FP partitioning schema, I did not loose my data as I should have. I am now stuck with bizarre values for the partition sizes. I will post the output of these commands here in my next post: df and mount. Please inform me if other information is required or if an official FP support request is preferable.
Donat.Callens said:
I will post the output of these commands here in my next post: df and mount.
Click to expand...
Click to collapse
$ df
Filesystem Size Used Free Blksize
/dev 487M 52K 487M 4096
/mnt/secure 487M 0K 487M 4096
/mnt/asec 487M 0K 487M 4096
/mnt/asec/com.camsam.plus-1 22M 19M 2M 4096
/mnt/asec/com.nuance.swype.dtc-1 36M 32M 3M 4096
/mnt/asec/com.koushikdutta.backup.license-1 1M 280K 1M 4096
/mnt/asec/ginlemon.flowerpro-1 5M 3M 1M 4096
/mnt/obb 487M 0K 487M 4096
/system 639M 351M 288M 4096
/data 3G 1G 2G 4096
/cache 124M 4M 119M 4096
/mnt/cd-rom 1M 1M 0K 2048
/protect_f 8M 4M 4M 4096
/protect_s 8M 4M 4M 4096
/storage/emulated 487M 0K 487M 4096
/storage/sdcard1 7G 6G 425M 32768
/storage/emulated/0 3G 1G 2G 4096
/storage/emulated/0/Android/obb 3G 1G 2G 4096
/storage/emulated/legacy 3G 1G 2G 4096
/storage/emulated/legacy/Android/obb 3G 1G 2G 4096
$ mount
rootfs / rootfs ro,relatime 0 0
tmpfs /dev tmpfs rw,nosuid,relatime,mode=755 0 0
devpts /dev/pts devpts rw,relatime,mode=600 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 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/secure tmpfs rw,relatime,mode=700 0 0
tmpfs /mnt/asec tmpfs rw,relatime,mode=755,gid=1000 0 0
/dev/block/dm-0 /mnt/asec/com.camsam.plus-1 ext4 ro,dirsync,nosuid,nodev,noatime 0 0
/dev/block/dm-1 /mnt/asec/com.nuance.swype.dtc-1 ext4 ro,dirsync,nosuid,nodev,noatime 0 0
/dev/block/dm-2 /mnt/asec/com.koushikdutta.backup.license-1 ext4 ro,dirsync,nosuid,nodev,noatime 0 0
/dev/block/dm-3 /mnt/asec/ginlemon.flowerpro-1 ext4 ro,dirsync,nosuid,nodev,noatime 0 0
tmpfs /mnt/obb tmpfs rw,relatime,mode=755,gid=1000 0 0
/[email protected] /system ext4 ro,noatime,noauto_da_alloc,commit=1,data=ordered 0 0
/[email protected] /data ext4 rw,nosuid,nodev,noatime,discard,noauto_da_alloc,data=ordered 0 0
/[email protected] /cache ext4 rw,nosuid,nodev,noatime,discard,noauto_da_alloc,data=ordered 0 0
/dev/block/loop0 /mnt/cd-rom iso9660 ro,relatime 0 0
/[email protected]_f /protect_f ext4 rw,nosuid,nodev,noatime,nodelalloc,noauto_da_alloc,commit=1,data=ordered 0 0
/[email protected]_s /protect_s ext4 rw,nosuid,nodev,noatime,nodelalloc,noauto_da_alloc,commit=1,data=ordered 0 0
/dev/fuse /mnt/shell/emulated fuse rw,nosuid,nodev,relatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
tmpfs /storage/emulated tmpfs rw,nosuid,nodev,relatime,mode=050,gid=1028 0 0
/dev/block/vold/179:97 /storage/sdcard1 vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/fuse /storage/emulated/0 fuse rw,nosuid,nodev,relatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
/dev/fuse /storage/emulated/0/Android/obb fuse rw,nosuid,nodev,relatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
/dev/fuse /storage/emulated/legacy fuse rw,nosuid,nodev,relatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
/dev/fuse /storage/emulated/legacy/Android/obb fuse rw,nosuid,nodev,relatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
Donat.Callens said:
I'm afraid I must report otherwise from my personal experience. I had previously re-partitioned my phone with a 4GB internal space storage. When applying the new FP partitioning schema, I did not loose my data as I should have. I am now stuck with bizarre values for the partition sizes. I will post the output of these commands here in my next post: df and mount. Please inform me if other information is required or if an official FP support request is preferable.
Click to expand...
Click to collapse
Can you please execute the following (as root e.g. adb shell ; su) and paste the result?
/system/bin/fp_part -r -f /dev/pmt | grep FAT; echo $?
_keesj said:
/system/bin/fp_part -r -f /dev/pmt | grep FAT; echo $?
Click to expand...
Click to collapse
__NODL_FAT,0x74F80000,0x33F3A0000,0x00000000
0
Donat.Callens said:
__NODL_FAT,0x74F80000,0x33F3A0000,0x00000000
0
Click to expand...
Click to collapse
Only the first part of the uprade has happend. The first part replaces the root file system, recovery and some other system partitions.
The second part of the upgrade is launched on the next boot in /system/etc/install-recovery.sh (itself copied from /system/bin/fp1_partition_upgrade ).
It checks if the partition upgrade has happened and if not perform the upgrade.
This step is not working on your phone/layout and to understand why you need to get the kernel messages (dmesg or logcat) while doing the upgrade.
/system/bin/fp1_partition_upgrade
Code:
#!/system/bin/sh
#
# Upgrade the partition layout from FP1 to FP1U
#
#
# dump pmt to see if the upgrade has happend
if /system/bin/fp_part -r -f /dev/pmt | grep FAT > /dev/null
then
echo Starting partition upgrade
cp /system/bin/fs_upgrade.bin /proc/sd_upgrade
echo "--wipe_data" > /cache/recovery/command
reboot recovery
fi
logcat
_keesj said:
This step is not working on your phone/layout and to understand why you need to get the kernel messages (dmesg or logcat) while doing the upgrade.
Click to expand...
Click to collapse
I restarted the partition updater and attach the corresponding logcat
$ logcat -v long
Donat.Callens said:
I restarted the partition updater and attach the corresponding logcat
$ logcat -v long
Click to expand...
Click to collapse
Can you please also provide the dmesg output, possibly using a private message? (the logcat does contains the info I am looking for an might contain private data)
custom recovery might be the source of the problem
_keesj said:
Donat.Callens said:
_keesj said:
The partition upgrdate is not happening, there should be lines containins SD_UPGRADE something like
Click to expand...
Click to collapse
could it be because I have a custom recovery installed?
Click to expand...
Click to collapse
This is an interesting idea.
-The sd_upgrade command is executed when not on the recovery so this is not probable.
-I think the recovery will also be replace back to "original" because we need a diifferent kernel.
Did you run the command and does the device reboot afterwards? A different recovery might not perform the factory reset?
Click to expand...
Click to collapse
I did not run the command, I merely started the FairPhone updater's partition upgrade tool. It displays a progress window like the first time, so I guess it is at least trying.
After the progress window, I get
ROM may flash stock recovery on boot. Fix?
Click to expand...
Click to collapse
I then reply
Yes - Disable recovery flash
Click to expand...
Click to collapse
I can try to let it install the stock recovery and run the partition updater after that to see if it solves the problem.
Donat.Callens said:
I did not run the command, I merely started the FairPhone updater's partition upgrade tool. It displays a progress window like the first time, so I guess it is at least trying.
After the progress window, I getI then replyI can try to let it install the stock recovery and run the partition updater after that to see if it solves the problem.
Click to expand...
Click to collapse
Post partition upgrade:
-The zip files downloaded have a different scattter file (a file describing the partition layout) that gets checked by the normal recovery.
-The zip are signed with a different key
This does not apply to the partition upgrader itself but might impact custom recovery users. The upgrader also replaces the recovery.
_keesj said:
Post partition upgrade:
-The zip files downloaded have a different scattter file (a file describing the partition layout) that gets checked by the normal recovery.
-The zip are signed with a different key
This does not apply to the partition upgrader itself but might impact custom recovery users. The upgrader also replaces the recovery.
Click to expand...
Click to collapse
I replied No to the question: ROM may flash stock recovery on boot. Fix?
This solved the issue. The installer completed and now my phone is back to factory default. I have 13.37 GB total space . I will restore my backups. Thank you for your support _keesj.
Please ensure user are informed they have to let the installer replace the existing custom recovery with the factory one for the partition upgrader to work correctly. You can always restore your custom recovery afterwards
I hereby confirm that, in my case, the partition upgrader worked with a modified partition scheme. For reference, I had changed the internal storage space to 4GB in the past.
Awesome guys!
This is why I like xda-developers and Fairphone and its community accompanied development so much. Not only I can follow the rapid conversations on problems and solutions that I could even run into, I also learn a lot about related techniques, background and the challenges in throwing a fair phone on the market.
I definitely appreciate the work of the xda developers, keejs and joemier - and of course all the others that stand behind that all. KUDOS!
But will all my apps still work, if I do backup the two partitions and then after the upgrade put everything on the one remaining partition? I guess quite a few apps might still "look" for their data on the no longer existing second partition, won't they?
Steps for "fiixing" your upgrade
Some user have repartitioned the partition of their FP1U using tool mentioned in on this forum. FP1U does not need this as the new layout is perfectly fine.
I think the following steps *should* work to get their phone back to "normal"
#get the partition upgrader
wget http://storage.googleapis.com/updat...G13G_partitionUpgrade_v1_6_OTA_2014-07-31.zip
#unzip it
unzip FP1_Fairphone_OS_1G13G_partitionUpgrade_v1_6_OTA_2014-07-31.zip
#attach your device to your pc and make sure adb works
#after that push the new partition layout to your device
adb push system/bin/fs_upgrade.bin /mnt/sdcard/
#the rest of the command need to run as root
adb shell
su.
# tell the kernel to perform the upgrade
cp /system/bin/fs_upgrade.bin /proc/sd_upgrade
#reboot and wipe the data
echo "--wipe_data" > /cache/recovery/command
reboot recovery
Since Lollipop, I can no longer access hboot via /dev/block/mmcblk0p11, and when I do # mount | grep blk, it shows:
/dev/block/mmcblk0p45 /system ext4 ro,seclabel,noatime,data=ordered 0 0
/dev/block/mmcblk0p46 /cache ext4 rw,seclabel,nosuid,nodev,relatime,data=ordered 0 0
/dev/block/mmcblk0p39 /devlog ext4 rw,seclabel,nosuid,nodev,relatime,errors=continue,data=ordered 0 0
/dev/block/mmcblk0p27 /fataldevlog ext4 rw,seclabel,nosuid,nodev,relatime,errors=continue,data=ordered 0 0
/dev/block/mmcblk0p37 /carrier ext4 rw,seclabel,nosuid,nodev,noatime,grpid,data=ordered 0 0
/dev/block/mmcblk0p22 /custdata ext4 ro,seclabel,nosuid,nodev,relatime,data=ordered 0 0
During 4.4.x, I was able to access hboot via mmcblk0p22 but it was gone since 5.0.x. I wanna take away those annoying red text, can anyone point me to the right direction?
You can get it from here:
http://forum.xda-developers.com/showthread.php?t=2710503
Hi everyone!
I've got this phone Asus ZenFone2 UL-Z00T-CN and i whant to make it WW
Making it WW grants me the posibility to use every custom ROM
I think I've read on every article about it and I came to the conclusion I cant change it
I think the problem with this CN phone seems to be the system partition wich is partitioned a little smaller than the WW version
C:\Users\Andrew>fastboot flash system D:\WW\system.img
target reported max download size of 268435456 bytes
erasing 'system'...
OKAY [ 0.431s]
sending sparse 'system' 1/12 (259338 KB)...
OKAY [ 12.131s]
writing 'system' 1/12...
FAILED (remote: size too large)
finished. total time: 12.570s
Can you tell me how are your partitions fitted inside your phones to get some ideas about them?
I dont know how to use those commands in this busybox of mine but i tried after some research and a little study and i came to some results and i hope are a little useful for me and for you too.
Here are some things i discovered....
~ # [6ndf -a -h (all partitions listed human)
Filesystem Size Used Available Use% Mounted on
tmpfs 1.3G 16.0K 1.3G 0% /dev
devpts 0 0 0 0% /dev/pts
proc 0 0 0 0% /proc
sysfs 0 0 0 0% /sys
selinuxfs 0 0 0 0% /sys/fs/selinux
tmpfs 1.3G 20.0K 1.3G 0% /tmp
pstore 0 0 0 0% /sys/fs/pstore
adb 0 0 0 0% /dev/usb-ffs/adb
/dev/block/mmcblk0p46
25.7G 155.9M 25.5G 1% /data
/dev/block/mmcblk0p46
25.7G 155.9M 25.5G 1% /sdcard
/dev/block/mmcblk0p44
27.5M 180.0K 26.7M 1% /cache
/dev/block/mmcblk1p1 7.4G 3.1G 4.3G 42% /sdcard1 (this is my 8Gig SDcard)
-------------------------------------------------------------------------------------------------------
~ # [6ndf -h (all mounted partitions listed human)
Filesystem Size Used Available Use% Mounted on
tmpfs 1.3G 16.0K 1.3G 0% /dev
tmpfs 1.3G 20.0K 1.3G 0% /tmp
/dev/block/mmcblk0p46
25.7G 144.5M 25.5G 1% /data
/dev/block/mmcblk0p46
25.7G 144.5M 25.5G 1% /sdcard
/dev/block/mmcblk0p44
27.5M 468.0K 26.4M 2% /cache
-------------------------------------------------------------------------------------------------------
mount
rootfs on / type rootfs (rw,seclabel)
tmpfs on /dev type tmpfs (rw,seclabel,nosuid,relatime,size=1403968k,nr_inodes=350992,mode=755)
tmpfs on /tmp type tmpfs (rw,seclabel,relatime,size=1403968k,nr_inodes=350992)
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)
pstore on /sys/fs/pstore type pstore (rw,seclabel,relatime)
adb on /dev/usb-ffs/adb type functionfs (rw,relatime)
/dev/block/mmcblk0p46 on /data type ext4 (rw,seclabel,relatime,data=ordered)
/dev/block/mmcblk0p46 on /sdcard type ext4 (rw,seclabel,relatime,data=ordered)
/dev/block/mmcblk0p44 on /cache type ext4 (rw,seclabel,relatime,data=ordered)
-------------------------------------------------------------------------------------------------------
du -h (Display the total size of all the files in a given directory and its subdirectories)
/
./sdcard (internal storage partition showed on computer as a drive)
4.0K ./sdcard/ASUS/Calllog/Backup (4.0K Backup each empty directory)
8.0K ./sdcard/ASUS/Calllog (4.0K empty directory inside of the + 4.0K Calllog = 8.0K)
12.0K ./sdcard/ASUS (4.0K empty directory inside of the + 4.0K Calllog = 8.0K + 4.0K ASUS)
etc.
0 ./usb-otg (empty 0KB)
0 ./sdcard1 (MMC memory card partition showed on computer after restart as drive when flash is inserted)
0 ./persist
0 ./firmware
0 ./factory
4.0K ./asdf
0 ./sideload
4.0K ./cache
0 ./recovery
0 ./boot
48.0K ./vendor
1.4M ./twres
20.0K ./tmp
0 ./system
0 ./sys/fs/f2fs
0 ./sys/fs/ext4/features
0 ./sys/fs/ext4/mmcblk0p44
0 ./sys/fs/ext4/mmcblk0p46
0 ./sys/fs/ext4
0 ./sys/fs/fuse/connections
0 ./sys/fs/fuse
0 ./sys/fs/selinux/policy_capabilities
etc.
0 ./sys/fs/selinux
0 ./sys/fs/cgroup
0 ./sys/fs/pstore
0 ./sys/fs
etc.
0 ./sys/bus/cpu
0 ./sys/bus/cpu
etc.
0 ./sys/bus/iio/drivers
0 ./sys/bus/iio
0 ./sys/bus/mmc/devices
0 ./sys/bus/mmc/drivers/mmcblk
0 ./sys/bus/mmc/drivers
0 ./sys/bus/mmc
0 ./sys/bus/soc/devices
etc.
0 ./sys
460.0K ./supersu
11.5M ./sbin
0 ./res/images
4.0K ./res
0 ./proc/msm_otg
0 ./proc/uid_stat
etc.
0 ./proc
0 ./oem
4.0K ./license/openaes
4.0K ./license
12.0K ./etc
4.0K ./data/lost+found
etc.
54.6M ./data/data
4.0K ./data/dalvik-cache/profiles
33.0M ./data/dalvik-cache/arm
6.3M ./data/dalvik-cache/arm64
39.2M ./data/dalvik-cache
etc.
4.0K ./data/system/job
2.2M ./data/system
4.0K ./data/shared
4.0K ./data/fota
4.0K ./data/hostapd
44.0K ./data/time
4.0K ./data/audio
4.0K ./data/camera
4.0K ./data/nfc/param
8.0K ./data/nfc
4.0K ./data/tombstones/modem
etc.
100.3M ./data
0 ./root
16.0K ./dev
115.6M .
-------------------------------------------------------------------------------------------------------
i found a script about how to partitioning but is for other phone I think Samsung
#!/sbin/sh
OUTFD=$2
ui_print() {
echo -n -e "ui_print $1\n" > /proc/self/fd/$OUTFD
echo -n -e "ui_print\n" > /proc/self/fd/$OUTFD
}
ui_print ""
ui_print "###########################"
ui_print "# audahadi #"
ui_print "# modded from forumber2's #"
ui_print "# Repartition script #"
ui_print "# Mi 3W /system 1.2G #"
ui_print "# only! #"
ui_print "###########################"
ui_print ""
ui_print "Unmounting systems partiton..."
umount -l /system
umount -l /system1
umount -l /dev/block/mmcblk0p25
umount -l /dev/block/mmcblk0p26
ui_print ""
ui_print "WARNING! System is ready, repartitioning will start in 2 seconds"
sleep 2
ui_print ""
ui_print "Removing partitions..."
parted /dev/block/mmcblk0 rm 25
parted /dev/block/mmcblk0 rm 26
ui_print "Removing partitions...COMPLETED"
ui_print ""
ui_print "Creating new partitions..."
parted /dev/block/mmcblk0 mkpart primary 403MB 1074MB
parted /dev/block/mmcblk0 mkpart primary 1074MB 1745MB
parted /dev/block/mmcblk0 name 25 system
parted /dev/block/mmcblk0 name 26 system1
ui_print "Creating new partitions...COMPLETED"
ui_print ""
ui_print "Unmounting systems partitions again..."
umount -l /system
umount -l /system1
umount -l /dev/block/mmcblk0p25
umount -l /dev/block/mmcblk0p26
ui_print "Unmounting systems partitions again...COMPLETED"
ui_print ""
ui_print "Formatting new partitions..."
mke2fs -b 4096 -T ext4 /dev/block/mmcblk0p25
mke2fs -b 4096 -T ext4 /dev/block/mmcblk0p26
ui_print "Formatting new partitions...COMPLETED."
ui_print ""
ui_print "ALL DONE!..."
ui_print ""
ui_print "Rebooting to recovery in 5 seconds..."
ui_print "Thanks to forumber2 for his original GT-i9300 repartition script"
sleep 5
reboot recovery
SO in conclusion I want to redistribute partitions so i can install any ROM or WW IMG I want NOT the CN version. Is there a way to do that?
Can you help me?
If this chalanging problem is solved I would like to make it sticky if it's possible
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?