Hi,
This is a modified Super Wipe script from ARHD.It will wipe cache ,data and system.
These are mount points used:
For U,P,Sola:
/dev/block/mmcblk0p10 system
/dev/block/mmcblk0p11 data
/dev/block/mmcblk0p12 cache
For S,Acro S:
/dev/block/mmcblk0p12 system
/dev/block/mmcblk0p14 data
/dev/block/mmcblk0p13 cache
If it is different for your device do not use this!
Download:
Super_Wipe_NXT_U_P_Sola.zip
Super_Wipe_NXT_S_acroS
Install this through CWM.
Use at your own risk!
Do you know the mount points for Xperia S ?
rampage2020 said:
Do you the mount points for Xperia S ?
Click to expand...
Click to collapse
No it's not FOr Xperia S it should be the same as acro S :
Code:
/cache ext4 /dev/block/mmcblk0p13
/data ext4 /dev/block/mmcblk0p14
/system ext4 /dev/block/mmcblk0p12
/sdcard vfat /dev/block/mmcblk0p15
Pims83 said:
No it's not FOr Xperia S it should be the same as acro S :
Code:
/cache ext4 /dev/block/mmcblk0p13
/data ext4 /dev/block/mmcblk0p14
/system ext4 /dev/block/mmcblk0p12
/sdcard vfat /dev/block/mmcblk0p15
Click to expand...
Click to collapse
Thank you,added for S and acro S.
neectron said:
Thank you,added for S and acro S.
Click to expand...
Click to collapse
Just for information, i found this line in recovery.tar for XPERIA S and Acro S that i use and work for me, so i hope that the good one
Pims83 said:
No it's not FOr Xperia S it should be the same as acro S :
Code:
/cache ext4 /dev/block/mmcblk0p13
/data ext4 /dev/block/mmcblk0p14
/system ext4 /dev/block/mmcblk0p12
/sdcard vfat /dev/block/mmcblk0p15
Click to expand...
Click to collapse
mount point for boot??
Can you make a wipe data/system/dalvik/battery/cache ?
Its for do a clean zip install!!
GEKTHEBOSS said:
Can you make a wipe data/system/dalvik/battery/cache ?
Its for do a clean zip install!!
Click to expand...
Click to collapse
data,system,cache already done.And dalvik,battery is inside data.So already done.
Related
looks like my SGS2 corrupted it's /system and /data ext4 partitions so now they're read-only:
/dev/block/mmcblk0p9 /system ext4 ro,relatime,barrier=1,data=ordered 0 0
/dev/block/mmcblk0p10 /data ext4 ro,nosuid,nodev,noatime,barrier=1,data=ordered,noauto_da_alloc,discard 0 0
so now it's pretty much unusable.
how can I force fsck of those partitions or otherwise remount them as read-write?
borism3000 said:
looks like my SGS2 corrupted it's /system and /data ext4 partitions so now they're read-only:
/dev/block/mmcblk0p9 /system ext4 ro,relatime,barrier=1,data=ordered 0 0
/dev/block/mmcblk0p10 /data ext4 ro,nosuid,nodev,noatime,barrier=1,data=ordered,noauto_da_alloc,discard 0 0
so now it's pretty much unusable.
how can I force fsck of those partitions or otherwise remount them as read-write?
Click to expand...
Click to collapse
Hmm ... let me guess ...
You have a real problem, if you want to keep the information in those partitions.
I would recommend to make a factory reset and flash the ROM you want to have with pit file and re-partion option in Odin.
Good luck !
I have same problem,
So there is no solutions at all?
What about booting into recovery then using a adb shell to run fsck on the partitions.
Note system is supposed to be read only but it couldn't hurt to check it.
Here is the recovery.fstab for the atrix
# mount point fstype device [device2]
/boot emmc /dev/block/mmcblk0p11
/cache ext4 /dev/block/mmcblk0p15 NULL ext3
/data ext4 /dev/block/mmcblk0p16 NULL ext3
/sdcard vfat /dev/block/mmcblk1p1
/emmc vfat /dev/block/mmcblk0p18
/system ext4 /dev/block/mmcblk0p12 NULL ext3
/recovery emmc /dev/block/mmcblk0p10
/osh ext3 /dev/block/mmcblk0p13
/preinstall ext3 /dev/block/mmcblk0p17
And here the dx2
# mount point fstype device
/sdcard vfat /dev/block/mmcblk1p1 /dev/block/mmcblk1
/system auto /dev/block/mmcblk0p12
/cache ext3 /dev/block/mmcblk0p15
/data ext3 /dev/block/mmcblk0p16
#/misc mtd misc
#/boot mtd boot
#/recovery mtd recovery
/pds ext3 /dev/block/mmcblk0p3
#/preinstall ext3 /dev/block/mmcblk0p17
/emmc vfat /dev/block/mmcblk0p18
I am trying to find the err in the mongrel cwr. More: log from this: cwr 5025 + oly recovery(sbin) + oly etc( recovery.fstab ). See thread cwr hacking.
It backsup but adv restore fails.
Do you mean you can make a backup nandRoid but it wont restore it?
---------- Post added at 09:37 PM ---------- Previous post was at 09:35 PM ----------
Cuz Dragonz made it that far before... Restore fails because /system can't unmount because there is processes using it...
Yes here is my latest mongrel cwr.
But the full restore will never untill we get a UL boot loader so use adv restore for testing or find a work around.
I already get the recovery.fstab as following
# mount point fstype device [device2]
/boot emmc boot
/cache ext4 cache
/data ext4 userdata
/misc emmc misc
/recovery emmc recovery
/sdcard vfat /dev/block/mmcblk1p1 /dev/block/mmcblk1
/system ext4 system
/devlog ext4 devlog
/internal_sdcard vfat /dev/block/mmcblk0p35
to add new device create file in edify_defs with the same of device, as above listed mount point how can I edit the new file
Thanks for help
Saw this posted inside another thread, but I think it's important enough to warrant it's own thread.
All credits for the info to @JoshBeach in this post.
Here are the important ones for rom/recovery development:
Code:
[b]boot[/b]: /dev/block/mmcblk0p14
[b]cache[/b]: /dev/block/mmcblk0p24
[b]recovery[/b]: /dev/block/mmcblk0p15
[b]system[/b]: /dev/block/mmcblk0p23
[b]userdata[/b]: /dev/block/mmcblk0p26
And here are all of them.
Code:
[b]aboot[/b]: /dev/block/mmcblk0p6
[b]apnhlos[/b]: /dev/block/mmcblk0p1
[b]backup[/b]: /dev/block/mmcblk0p17
[b]boot[/b]: /dev/block/mmcblk0p14
[b]cache[/b]: /dev/block/mmcblk0p24
[b]carrier[/b]: /dev/block/mmcblk0p25
[b]dbi[/b]: /dev/block/mmcblk0p4
[b]ddr[/b]: /dev/block/mmcblk0p5
[b]efs[/b]: /dev/block/mmcblk0p11
[b]fota[/b]: /dev/block/mmcblk0p16
[b]fsc[/b]: /dev/block/mmcblk0p19
[b]modem[/b]: /dev/block/mmcblk0p2
[b]modemst1[/b]: /dev/block/mmcblk0p12
[b]pad[/b]: /dev/block/mmcblk0p9
[b]param[/b]: /dev/block/mmcblk0p10
[b]persdata[/b]: /dev/block/mmcblk0p22
[b]persist[/b]: /dev/block/mmcblk0p21
[b]recovery[/b]: /dev/block/mmcblk0p15
[b]rpm[/b]: /dev/block/mmcblk0p7
[b]sbl1[/b]: /dev/block/mmcblk0p3
[b]ssd[/b]: /dev/block/mmcblk0p20
[b]system[/b]: /dev/block/mmcblk0p23
[b]tz[/b]: /dev/block/mmcblk0p8
[b]userdata[/b]: /dev/block/mmcblk0p26
why use mmcblk's?
/dev/block/platform/msm_sdcc.1/by-name/system
/dev/block/platform/msm_sdcc.1/by-name/boot
/dev/block/platform/msm_sdcc.1/by-name/recovery
/dev/block/platform/msm_sdcc.1/by-name/data
/dev/block/platform/msm_sdcc.1/by-name/cache
there are the big ones. using mmcblk's means that you are flashing to that block where teh by name it figures out where to put it for you. so flashable zips become a lot more universal as in they will should flash on the sgs3, sgs4, note 3 and many more devices.
this is about what the stock fstab looked like https://github.com/OUDhs/android_device_samsung_hltespr/blob/cm-10.2/recovery.fstab
Not really necessary to do that when if you want to make it universal you can just mount the partitions using a tool like busybox.
But yes, that works too of course
are the same also for N9005?
luigimak said:
are the same also for N9005?
Click to expand...
Click to collapse
Download parted for ARM and print the partition table yourself to make sure.
CNexus said:
Download parted for ARM and print the partition table yourself to make sure.
Click to expand...
Click to collapse
can you pass me the link?
luigimak said:
can you pass me the link?
Click to expand...
Click to collapse
https://github.com/CyanogenMod/android_bootable_recovery/blob/cm-10.2/utilities/parted?raw=true
Move that to /system/bin, set permissions to 755 and then in a terminal window run this:
Code:
parted
Welcome to GNU parted! (and other output like that)
print
(Select ignore on all warning messages you get)
[Partition table will print here]
Hello all,
I'm new to the world of ROMS and custom recoveries, I've rooted my phone and for educational purposes, I wanted to build CWM 6 but I have trouble with my recovery.fstab or something because I only get a blank screen flashing periodically.
Here's the stock recovery.fstab of the recovery.img
Code:
/dev/block/platform/sprd-sdhci.0/mmcblk1p1 /sdcard vfat default recoveryonly
/dev/block/platform/sprd-sdhci.3/by-name/system /system ext4 default recoveryonly
/dev/block/platform/sprd-sdhci.3/by-name/HIDDEN /preload ext4 default recoveryonly
/dev/block/platform/sprd-sdhci.3/by-name/userdata /data ext4 default wait,length=-16384
/dev/block/platform/sprd-sdhci.3/by-name/CSC /cache ext4 default recoveryonly
/dev/block/platform/sprd-sdhci.3/by-name/efs /efs ext4 default recoveryonly
/dev/block/platform/sprd-sdhci.3/by-name/PRODNV /productinfo ext4 default recoveryonly
/dev/block/platform/sprd-sdhci.3/by-name/KERNEL /boot emmc default recoveryonly
/dev/block/platform/sprd-sdhci.3/by-name/RECOVERY /recovery emmc default recoveryonly
/dev/block/platform/sprd-sdhci.3/by-name/modem /modem emmc default recoveryonly
/dev/block/platform/sprd-sdhci.3/by-name/DSP /modem2 emmc default recoveryonly
I've also tried this version (after changing the names with partitions)
Code:
# mount point fstype device
/system ext4 /dev/block/mmcblk0p18
/preload ext4 /dev/block/mmcblk0p19
/data ext4 /dev/block/mmcblk0p20
/cache ext4 /dev/block/mmcblk0p17
/efs ext4 /dev/block/mmcblk0p7
/productinfo ext4 /dev/block/mmcblk0p5
/boot emmc /dev/block/mmcblk0p11
/recovery emmc /dev/block/mmcblk0p12
/modem emmc /dev/block/mmcblk0p13
/modem2 emmc /dev/block/mmcblk0p14
/sdcard vfat /dev/block/platform/sprd-sdhci.0/mmcblk1p1
but to no avail, the only result that I got was when I used the fstab of the boot.img
Code:
# 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
# <src> <mnt_point> <type> <mnt_flags and options> <fs_mgr_flags>
#/dev/block/platform/sprd-sdhci.3/by-name/system /system ext4 ro,barrier=1 wait
#/dev/block/platform/sprd-sdhci.3/by-name/userdata /data ext4 noatime,nosuid,nodev,nomblk_io_submit wait,encryptable=footer,check
#/dev/block/platform/sprd-sdhci.3/by-name/cache /cache ext4 noatime,nosuid,nodev,nomblk_io_submit wait,check
#/dev/block/platform/sprd-sdhci.3/by-name/prodnv /productinfo ext4 noatime,nosuid,nodev,nomblk_io_submit wait,check
/dev/block/platform/sprd-sdhci.3/by-name/system /system ext4 ro,noatime,errors=panic wait
/dev/block/platform/sprd-sdhci.3/by-name/userdata /data ext4 nosuid,nodev,noatime,noauto_da_alloc,discard,journal_async_commit,errors=panic wait,check,encryptable=footer
/dev/block/platform/sprd-sdhci.3/by-name/CSC /cache ext4 nosuid,nodev,noatime,noauto_da_alloc,discard,journal_async_commit,errors=panic wait,check
/dev/block/platform/sprd-sdhci.3/by-name/efs /efs ext4 nosuid,nodev,noatime,noauto_da_alloc,discard,journal_async_commit,errors=panic wait,check
/dev/block/platform/sprd-sdhci.3/by-name/PRODNV /productinfo ext4 nosuid,nodev,noatime,noauto_da_alloc,discard,journal_async_commit,errors=panic wait,check
/devices/platform/sprd-sdhci.0/mmc_host/mmc1 auto vfat defaults voldmanaged=extSdCard:auto,noemulatedsd
would you please tell me what I'm missing here ?
Just want to know
Could you tell me how you got root for this phone..? Been searching all over with no luck