First off all:
I have < 10 posts, hence I cannot create this thread in the appropriate sub-forum. If a moderator wants to move this thread, that would be nice.
Brief intro:
I am a N7000 owner looking to make the switch to the 6.3. The only thing that's holding me back at this point is that so far there has been no confirmation on a working CWM. I noticed that development is a little slow regarding CWM, so i thought i'd "build" a recovery.
1. This was built using http://builder.clockworkmod.com/
2. This is based on recovery.img and recovery.fstab from this post.
3. The md5 of the original recovery is 13e64f3947318cba830992224d781389. You can compare the one from the thread with the one from the buildserver (inputrecovery.img) to verify this.
4.The build can be found here: http://jenkins.cyanogenmod.com/job/recovery/31839/
5. recovery.tar.md5 can be found here.
6. It was created the following way:
[email protected]:/archive# tar -H ustar -c recovery.img > recovery.tar
[email protected]:/archive# md5sum -t recovery.tar >> recovery.tar
[email protected]:/archive# mv recovery.tar recovery.tar.md5
7. This was built as a non-touch recovery. Trying to eliminate any potential point of failure.
8. Feel free to test it, but as always i take no responsibility.
ponglenis said:
First off all:
I have < 10 posts, hence I cannot create this thread in the appropriate sub-forum. If a moderator wants to move this thread, that would be nice.
Brief intro:
I am a N7000 owner looking to make the switch to the 6.3. The only thing that's holding me back at this point is that so far there has been no confirmation on a working CWM. I noticed that development is a little slow regarding CWM, so i thought i'd "build" a recovery.
1. This was built using http://builder.clockworkmod.com/
2. This is based on recovery.img and recovery.fstab from this post.
3. The md5 of the original recovery is 13e64f3947318cba830992224d781389. You can compare the one from the thread with the one from the buildserver (inputrecovery.img) to verify this.
4.The build can be found here: http://jenkins.cyanogenmod.com/job/recovery/31839/
5. recovery.tar.md5 can be found here.
6. It was created the following way:
[email protected]:/archive# tar -H ustar -c recovery.img > recovery.tar
[email protected]:/archive# md5sum -t recovery.tar >> recovery.tar
[email protected]:/archive# mv recovery.tar recovery.tar.md5
7. This was built as a non-touch recovery. Trying to eliminate any potential point of failure.
8. Feel free to test it, but as always i take no responsibility.
Click to expand...
Click to collapse
I haven't tried this but I have done the same set of steps and it didn't work. I will let someone else report on this version.
Sent from my GT-I9205 using Tapatalk 2
Kangburra said:
I haven't tried this but I have done the same set of steps and it didn't work. I will let someone else report on this version.
Sent from my GT-I9205 using Tapatalk 2
Click to expand...
Click to collapse
Well, thats too bad. Sadly i do not know very much about building CWM. You do have the option to include a custom graphics.c file for custom frame buffers, but since we have no recovery sources for the 6.3 i would not know where to start.
I was able to build a recovery using https :// github.com/CyanogenMod/android_bootable_recovery/blob/jellybean/minui/graphics.c?source=cc this graphics.c. This is of course not device specific.
Maybe someone who has root and a terminal emulator can post the results of this command:
ls -la /dev/graphics/
Thanks, lets not give up on this just yet
One more thing that would be helpful if someone could post what (the faulty) CWM logs after starting.
Perhaps someone with a faulty CWM installed who has root and a terminal emulator can post the results of the following command:
cat /cache/recovery/last_log
Thanks!
ponglenis said:
Well, thats too bad. Sadly i do not know very much about building CWM. You do have the option to include a custom graphics.c file for custom frame buffers, but since we have no recovery sources for the 6.3 i would not know where to start.
I was able to build a recovery using https :// github.com/CyanogenMod/android_bootable_recovery/blob/jellybean/minui/graphics.c?source=cc this graphics.c. This is of course not device specific.
Maybe someone who has root and a terminal emulator can post the results of this command:
ls -la /dev/graphics/
Thanks, lets not give up on this just yet
Click to expand...
Click to collapse
Here
Code:
1|[email protected]:/ $ ls -la /dev/graphics/
crw-rw---- system graphics 29, 0 2013-01-03 20:11 fb0
crw-rw---- system graphics 29, 1 2013-01-03 20:11 fb1
crw-rw---- system graphics 29, 2 2013-01-03 20:11 fb2
lrwxrwxrwx root root 2013-01-03 20:11 hdmi -> /dev/graphics/fb1
One more thing that would be helpful if someone could post what (the faulty) CWM logs after starting.
Perhaps someone with a faulty CWM installed who has root and a terminal emulator can post the results of the following command:
cat /cache/recovery/last_log
Thanks!
Click to expand...
Click to collapse
Code:
127|[email protected]:/ # cat /cache/recovery/last_log
Starting recovery on Tue Jan 1 00:58:03 2013
[collecting table information]
recovery filesystem table
=========================
0 '/tmp' 'ramdisk' '(null)' '(null)' 0
1 '/boot' 'emmc' '/dev/block/platform/msm_sdcc.1/by-name/boot' '(null)' 0
2 '/system' 'ext4' '/dev/block/platform/msm_sdcc.1/by-name/system' '(null)' 0
3 '/data' 'ext4' '/dev/block/platform/msm_sdcc.1/by-name/userdata' '(null)' -16384
4 '/cache' 'ext4' '/dev/block/platform/msm_sdcc.1/by-name/cache' '(null)' 0
5 '/recovery' 'emmc' '/dev/block/platform/msm_sdcc.1/by-name/recovery' '(null)' 0
6 '/sdcard' 'vfat' '/dev/block/mmcblk1p1' '/dev/block/mmcblk1' 0
7 '/efs' 'ext4' '/dev/block/platform/msm_sdcc.1/by-name/efs' '(null)' 0
8 '/modem' 'emmc' '/dev/block/platform/msm_sdcc.1/by-name/modem' '(null)' 0
9 '/preload' 'ext4' '/dev/block/platform/msm_sdcc.1/by-name/hidden' '(null)' 0
[initialize init-recovery]
#mount /system
stat() of /dev/block/platform/msm_sdcc.1/by-name/system succeeded on try 1
/system sucessfully mounted
#unmount /cache
/cache sucessfully unmounted
#exec -f /system/bin/e2fsck -v -y /dev/block/platform/msm_sdcc.1/by-name/cache
e2fsck 1.42.6 (21-Sep-2012)
/dev/block/platform/msm_sdcc.1/by-name/cache: clean, 14/12800 files, 9760/51200 blocks
#insmod -f -v /system/lib/modules/exfat_core.ko
/system/lib/modules/exfat_core.ko (76848) ''
initalized the '/system/lib/modules/exfat_core.ko' module
#insmod -f -v /system/lib/modules/exfat_fs.ko
/system/lib/modules/exfat_fs.ko (35764) ''
initalized the '/system/lib/modules/exfat_fs.ko' module
#lsmod
exfat_fs 18524 0 - Live 0xbf016000 (P)
exfat_core 62096 1 exfat_fs, Live 0xbf000000 (P)
#mount -f /cache
stat() of /dev/block/platform/msm_sdcc.1/by-name/cache succeeded on try 1
/cache sucessfully mounted
#cat -f --no-exist /cache/recovery/command > /cache/recovery/last_command
#ls /cache/recovery/
-rw-r--r-- root root 80 2013-05-16 14:34 command
-rw-r--r-- root root 32328230 2013-05-16 14:34 sec_csc.zip
-rw-r--r-- root root 80 2013-01-01 00:58 last_command
#mount /data
stat() of /dev/block/platform/msm_sdcc.1/by-name/userdata succeeded on try 1
failed to mount '/dev/block/platform/msm_sdcc.1/by-name/userdata' '/data'(ext4)(3076) -> Invalid argument
E :failed to mount /data (Invalid argument)
trace: __out_return: _do_mount :: can't mount '/data' (Invalid argument)
/system sucessfully unmounted
/cache sucessfully unmounted
running init-recovery time : 0.233s
[collecting command]
stat() of /dev/block/platform/msm_sdcc.1/by-name/cache succeeded on try 1
I:Got arguments from /cache/recovery/command
E :File Open error.
locale is [(null)]
[initialize ui and event]
initalized graphics for qualcomm.
pixel format -> GGL_PIXEL_FORMAT_RGBX_8888
return for qualcomm. double_buffering = 0
framebuffer: fd 4 (720 x 1280)
not turn off screen
installing_text: (1 x 1 @ 1896)
erasing_text: (1 x 1 @ 1599)
no_command_text: (1 x 1 @ 1599)
error_text: (1 x 1 @ 1599)
Command: "/sbin/recovery" "--update_package=CACHE:recovery/sec_csc.zip" "--carry_out=csc_factory" "--wipe_data"
previous_runs = 0
send_intent = (null)
update_package = CACHE:recovery/sec_csc.zip
att_fota_update = 0
tmo_fota_update = 0
wipe_data = 1, wipe_cache = 1,wipe_sdcard = 0,delete_data = 0,wipe_data_crypto = 0,wipe_carrier = 0,no_wipe_custom=0
wipe_hdd_secure = 0
show_ui_text = 0
update_factory_csc = 1, update_home_csc = 0, factory_fota = 0
carry_out = csc_factory
tima_kernal_recovery = 0
(replacing path "CACHE:recovery/sec_csc.zip" with "/cache/recovery/sec_csc.zip")
[property list]
ro.boot.hardware=qcom
ro.boot.debug_level=0x4f4c
ro.boot.cp_debug_level=0x55FF
ro.boot.emmc_checksum=3
ro.boot.bootloader=I9205XXUAMEA
ro.boot.nvdata_backup=0
ro.boot.boot_recovery=1
ro.boot.batt_check_recovery=1
ro.boot.emmc=true
ro.boot.serialno=06c760e6
ro.boot.baseband=msm
ro.serialno=06c760e6
ro.bootmode=unknown
ro.baseband=msm
ro.bootloader=I9205XXUAMEA
ro.debug_level=0x4f4c
ro.cp_debug_level=0x55FF
ro.emmc_checksum=3
ro.nvdata_backup=0
ro.boot_recovery=1
ro.emmc=true
ro.bootchg=unknown
ro.hardware=qcom
ro.revision=11
ro.factorytest=0
ro.secure=1
ro.allow.mock.location=0
ro.debuggable=0
ro.adb.secure=1
persist.sys.usb.config=mtp
ro.build.id=JDQ39
ro.build.display.id=JDQ39.I9205XXUAMEA
ro.build.version.incremental=I9205XXUAMEA
ro.build.version.sdk=17
ro.build.version.codename=REL
ro.build.version.release=4.2.2
ro.build.date=Thu May 16 23:53:36 KST 2013
ro.build.date.utc=1368716016
ro.build.type=user
ro.build.user=se.infra
ro.build.host=SEP-130
ro.build.tags=release-keys
ro.product.model=GT-I9205
ro.product.brand=samsung
ro.product.name=meliusltexx
ro.product.device=meliuslte
ro.product.board=MSM8960
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.manufacturer=samsung
ro.product.locale.language=en
ro.product.locale.region=GB
ro.wifi.channels=
ro.board.platform=msm8960
ro.build.product=meliuslte
ro.build.description=meliusltexx-user 4.2.2 JDQ39 I9205XXUAMEA release-keys
ro.build.fingerprint=samsung/meliusltexx/meliuslte:4.2.2/JDQ39/I9205XXUAMEA:user/release-keys
ro.build.characteristics=phone
ro.build.PDA=I9205XXUAMEA
ro.build.hidden_ver=I9205XXUAMEA
ro.build.changelist=651213
ro.product_ship=true
ro.chipname=MSM8930AB
rild.libpath=/system/lib/libril-qc-qmi-1.so
rild.libargs=-d /dev/smd0
persist.rild.nitz_plmn=
persist.rild.nitz_long_ons_0=
persist.rild.nitz_long_ons_1=
persist.rild.nitz_long_ons_2=
persist.rild.nitz_long_ons_3=
persist.rild.nitz_short_ons_0=
persist.rild.nitz_short_ons_1=
persist.rild.nitz_short_ons_2=
persist.rild.nitz_short_ons_3=
ril.subscription.types=NV,RUIM
DEVICE_PROVISIONED=1
debug.sf.hw=1
debug.egl.hw=1
debug.composition.type=c2d
debug.compbypass.enable=1
dalvik.vm.heapsize=256m
debug.enable.wl_log=1
persist.hwc.mdpcomp.enable=true
persist.cne.bat.range.low.med=30
persist.cne.bat.range.med.high=60
persist.cne.loc.policy.op=/system/etc/OperatorPolicy.xml
persist.cne.loc.policy.user=/system/etc/UserPolicy.xml
persist.cne.bwbased.rat.sel=false
persist.cne.snsr.based.rat.mgt=false
persist.cne.bat.based.rat.mgt=false
persist.cne.rat.acq.time.out=30000
persist.cne.rat.acq.retry.tout=0
persist.cne.feature=0
persist.sys.camera.connect=0
persist.sys.videomode=0
ro.hdmi.enable=true
ro.yas.enable=true
ro.yas_softiron.expressatt=true
ro.yas-selftest.enable=true
lpa.decode=true
lpa.use-stagefright=true
media.stagefright.enable-player=true
media.stagefright.enable-http=true
media.stagefright.enable-aac=true
media.stagefright.enable-qcp=true
media.stagefright.enable-fma2dp=true
media.stagefright.enable-scan=true
mmp.enable.3g2=true
ro.use_data_netmgrd=true
persist.timed.enable=true
persist.audio.fluence.mode=endfire
persist.audio.vr.enable=false
persist.audio.handset.mic=digital
af.resampler.quality=255
mpq.audio.decode=true
ro.opengles.version=131072
ro.bluetooth.hfp.ver=1.6
ro.qualcomm.bt.hci_transport=smd
ro.bluetooth.request.master=true
ro.bluetooth.remote.autoconnect=true
persist.gps.qmienabled=true
ro.qualcomm.cabl=0
ro.lcd_min_brightness=20
ro.lcd_brightness=120
ro.ril.transmitpower=true
persist.fuse_sdcard=true
ro.hwui.text_cache_width=2048
ro.warmboot.capability=1
ro.sf.lcd_density=240
persist.radio.apm_sim_not_pwdn=1
persist.sys.storage_preload=1
persist.radio.add_power_save=1
net.streaming.rtsp.uaprof=http://wap.samsungmobile.com/uaprof/
net.change=net.bt.name
ro.vendor.extension_library=/system/lib/libqc-opt.so
dalvik.vm.heapstartsize=8m
dalvik.vm.heapgrowthlimit=64m
dalvik.vm.heaptargetutilization=0.75
dalvik.vm.heapminfree=2m
dalvik.vm.heapmaxfree=8m
ro.sec.fle.encryption=true
ro.hdcp2.rx=tz
media.enable-commonsource=true
ro.secwvk=144
ro.config.ringtone=S_Over_the_horizon.ogg
ro.config.notification_sound=S_Whistle.ogg
ro.config.alarm_alert=Walk_in_the_forest.ogg
ro.config.media_sound=Media_preview_Touch_the_light.ogg
ro.monkey=0
ro.error.receiver.default=com.samsung.receiver.error
keyguard.no_require_sim=true
ro.com.android.dateformat=MM-dd-yyyy
ro.carrier=unknown
ro.com.google.clientidbase=android-samsung
ro.ril.hsxpa=1
ro.ril.gprsclass=10
ro.adb.qemud=1
ro.com.google.gmsversion=4.2_r2
net.bt.name=Android
dalvik.vm.stack-trace-file=/data/anr/traces.txt
ro.qc.sdk.izat.premium_enabled=0
persist.gps.qc_nlp_in_use=0
init.svc.ueventd=running
init.svc.recovery=running
stat() of /dev/block/platform/msm_sdcc.1/by-name/efs succeeded on try 1
[Installing package]
-- Installing package...
stat() of /dev/block/platform/msm_sdcc.1/by-name/system succeeded on try 1
Finding update package...
I:Update location: /cache/recovery/sec_csc.zip
stat() of /dev/block/platform/msm_sdcc.1/by-name/efs succeeded on try 1
Opening update package...
I:read key e=3
I:read key e=3
I:2 key(s) loaded from /res/keys
Verifying update package...
I:comment is 1796 bytes; signature 1778 bytes from end
signed len : 32326432
sha1 : 32326464
1ed1ab31 36cfac47 c1fa5ba e5bb793 c7ca1104
1e d1 ab 31 36 cf ac 47 0c 1f a5 ba 0e 5b b7 93 c7 ca 11 04
4e 00 4e 00 ef 18 00 00 1d 2a ed 01 80 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0f 6a 19 00
I:whole-file signature verified against key 1
I:verify_file returned 0
Installing update...
minzip: Extracted file "/system/CSCVersion.txt"
minzip: Extracted file "/system/SW_Configuration.xml"
minzip: Extracted file "/system/VODB/de_DE/checked"
minzip: Extracted file "/system/VODB/de_DE/de_DE-ak-cur.lite.res"
minzip: Extracted file "/system/VODB/de_DE/de_DE-lk-text.lite.res"
minzip: Extracted file "/system/VODB/de_DE/de_DE.lang"
minzip: Extracted file "/system/VODB/de_DE/files.txt"
minzip: Extracted file "/system/VODB/en_GB/checked"
minzip: Extracted file "/system/VODB/en_GB/en_GB-ak-cur.lite.res"
minzip: Extracted file "/system/VODB/en_GB/en_GB-lk-text.lite.res"
minzip: Extracted file "/system/VODB/en_GB/en_GB.lang"
minzip: Extracted file "/system/VODB/en_GB/files.txt"
minzip: Extracted file "/system/VODB/en_US/checked"
minzip: Extracted file "/system/VODB/en_US/en_US-ak-cur.lite.res"
minzip: Extracted file "/system/VODB/en_US/en_US-lk-text.lite.res"
minzip: Extracted file "/system/VODB/en_US/en_US.lang"
minzip: Extracted file "/system/VODB/en_US/files.txt"
minzip: Extracted file "/system/VODB/ko_KR/checked"
minzip: Extracted file "/system/VODB/ko_KR/files.txt"
minzip: Extracted file "/system/VODB/ko_KR/ko_KR.lang"
minzip: Extracted file "/system/VODB/ko_KR/ko_KR_johab-ak-cur.lite.res"
minzip: Extracted file "/system/VODB/ko_KR/ko_KR_johab-lk-text.lite.res"
minzip: Extracted file "/system/VODB/ko_KR/slang.res"
minzip: Extracted file "/system/VODB/lib/StylusWidget/libMyScriptEngine.so"
minzip: Extracted file "/system/VODB/lib/StylusWidget/libMyScriptHWR.so"
minzip: Extracted file "/system/VODB/lib/StylusWidget/libStylusCore.so"
minzip: Extracted file "/system/VODB/lib/ank-standard.res"
minzip: Extracted file "/system/VODB/lib/checked"
minzip: Extracted file "/system/VODB/lib/equation-ak.lite.res"
minzip: Extracted file "/system/VODB/lib/equation-grm-standard.res"
minzip: Extracted file "/system/VODB/lib/files.txt"
minzip: Extracted file "/system/VODB/lib/libMyScriptAnalyzer.so"
minzip: Extracted file "/system/VODB/lib/libMyScriptEngine.so"
minzip: Extracted file "/system/VODB/lib/libMyScriptEquation.so"
minzip: Extracted file "/system/VODB/lib/libMyScriptHWR.so"
minzip: Extracted file "/system/VODB/lib/libMyScriptInkSearch.so"
minzip: Extracted file "/system/VODB/lib/libMyScriptShape.so"
minzip: Extracted file "/system/VODB/lib/libStylusCore.so"
minzip: Extracted file "/system/VODB/lib/libvoim.so"
minzip: Extracted file "/system/VODB/lib/shk-analyzer.res"
minzip: Extracted file "/system/VODB/lib/shk-standard.res"
minzip: Extracted file "/system/VODB/mul/checked"
minzip: Extracted file "/system/VODB/mul/files.txt"
minzip: Extracted file "/system/VODB/mul/mul-lk-email.res"
minzip: Extracted file "/system/VODB/mul/mul-lk-gesture.res"
minzip: Extracted file "/system/VODB/mul/mul-lk-number.res"
minzip: Extracted file "/system/VODB/mul/mul-lk-number_decimal.res"
minzip: Extracted file "/system/VODB/mul/mul-lk-number_integer.res"
minzip: Extracted file "/system/VODB/mul/mul-lk-number_signed_decimal.res"
minzip: Extracted file "/system/VODB/mul/mul-lk-number_signed_integer.res"
minzip: Extracted file "/system/VODB/mul/mul-lk-phone_number.res"
minzip: Extracted file "/system/VODB/mul/mul-lk-uri.res"
minzip: Extracted file "/system/VODB/mul/mul-sk-email.res"
minzip: Extracted file "/system/VODB/mul/mul-sk-uri.res"
minzip: Extracted file "/system/VODB/resources.txt"
minzip: Extracted file "/system/app/Books.apk"
minzip: Extracted file "/system/app/Videos.apk"
minzip: Extracted file "/system/csc/contents.db"
minzip: Extracted file "/system/csc/customer.xml"
minzip: Extracted file "/system/csc/default_workspace.xml"
minzip: Extracted file "/system/csc/easylauncher_default_workspace.xml"
minzip: Extracted file "/system/csc/language.xml"
minzip: Extracted file "/system/csc/others.xml"
minzip: Extracted file "/system/csc/sales_code.dat"
minzip: Extracted file "/system/etc/csc_apks_list_DBT.txt"
minzip: Extracted file "/system/etc/csc_ringtones_list_DBT.txt"
minzip: Extracted file "/system/etc/hidden_apks_list_DBT.txt"
minzip: Extracted file "/system/etc/lteon_netlist.xml"
minzip: Extracted file "/system/etc/plmn_delta.bin"
minzip: Extracted file "/system/sipdb/de_DE.zip"
minzip: Extracted file "/system/sipdb/en_GB.zip"
minzip: Extracted file "/system/sipdb/en_US.zip"
minzip: Extracted file "/system/sipdb/ko_KR.zip"
package_extract_dir: 1
script result was [t]
Successfully installed package.
stat() of /dev/block/platform/msm_sdcc.1/by-name/system succeeded on try 1
stat() of /dev/block/platform/msm_sdcc.1/by-name/efs succeeded on try 1
read csc code = 'DBT'
just_reboot_after_update = 1
[installing media-csc]
running media-csc time : 0.000s
[Formatting data]
-- Wiping data...
Formatting /data...
Formatting /data...
Creating filesystem with parameters:
Size: 5322555392
Block size: 4096
Blocks per group: 32768
Inodes per group: 8128
Inode size: 256
Journal blocks: 20303
Label:
Blocks: 1299452
Block groups: 40
Reserved block group size: 319
Created filesystem with 11/325120 inodes and 43274/1299452 blocks
warning: wipe_block_device: Wipe via secure discard failed, used discard instead
complted format with ext4
/dev/block/platform/msm_sdcc.1/by-name/userdata is the encryptable partition?(1)
running time format /data time : 12.793s
running total wipe-data time : 12.823s
[installing multi-csc]
#echo
#echo -- Appling Multi-CSC...
-- Appling Multi-CSC...
#mount /system
stat() of /dev/block/platform/msm_sdcc.1/by-name/system succeeded on try 1
/system sucessfully mounted
#echo Applied the CSC-code : DBT
Applied the CSC-code : DBT
#cp -y -f -r -v /system/csc/common /
trace: __out_return: __scan_cp_dir :: cannot get src '/system/csc/common' (No such file or directory)
#unmount /system
/system sucessfully unmounted
#mount /system
stat() of /dev/block/platform/msm_sdcc.1/by-name/system succeeded on try 1
/system sucessfully mounted
#cmp -r /system/csc/common /
trace: __out_return: __scan_cmp_dir :: Can't open dir '/system/csc/common' .. skip (No such file or directory)
#cp -y -f -r -v /system/csc/DBT/system /system
trace: __out_return: __scan_cp_dir :: cannot get src '/system/csc/DBT/system' (No such file or directory)
#rm -v /system/csc_contents
#ln -v -s /system/csc/DBT/csc_contents /system/csc_contents
create symbolic '/system/csc/DBT/csc_contents' -> '/system/csc_contents'
#unmount /system
/system sucessfully unmounted
#mount /system
stat() of /dev/block/platform/msm_sdcc.1/by-name/system succeeded on try 1
/system sucessfully mounted
#cmp -r /system/csc/DBT/system /system
trace: __out_return: __scan_cmp_dir :: Can't open dir '/system/csc/DBT/system' .. skip (No such file or directory)
#rm -v --limited-file-size=0 /system/app/*
#echo Successfully applied multi-CSC.
Successfully applied multi-CSC.
/system sucessfully unmounted
running multi-csc time : 0.337s
[updated the factory mode]
#precondition define /preload
#echo -- Copying media files --
-- Copying media files --
#mount /preload
stat() of /dev/block/platform/msm_sdcc.1/by-name/hidden succeeded on try 1
/preload sucessfully mounted
#mount /data
stat() of /dev/block/platform/msm_sdcc.1/by-name/userdata succeeded on try 1
/data sucessfully mounted
#mkdir media_rw media_rw 0770 /data/media
#cp -y -r -v -f --with-fmode=0664 --with-dmode=0775 --with-owner=media_rw.media_rw /preload/INTERNAL_SDCARD/ /data/media/
the directory '/data/media/Samsung'
src : drwxr-xr-x root root 2013-05-16 14:34 Samsung
dst : drwxrwxr-x media_rw media_rw 2013-01-01 00:58 Samsung
the directory '/data/media/Samsung/Music'
src : drwxr-xr-x root root 2013-05-16 14:34 Music
dst : drwxrwxr-x media_rw media_rw 2013-01-01 00:58 Music
/preload/INTERNAL_SDCARD/Samsung/Music/Over_the_horizon.mp3 -> /data/media/Samsung/Music/Over_the_horizon.mp3 (2702919 bytes)
transferred in writed time : 0.055s closed time : 0.241s progressed with 46.87M byte/sec
src : -rw-r--r-- root root 2702919 2013-05-16 14:34 Over_the_horizon.mp3
dst : -rw-rw-r-- media_rw media_rw 2702919 2013-01-01 00:58 Over_the_horizon.mp3
#unmount /data
/data sucessfully unmounted
#mount /data
stat() of /dev/block/platform/msm_sdcc.1/by-name/userdata succeeded on try 1
/data sucessfully mounted
#cmp -r /preload/INTERNAL_SDCARD/ /data/media/
compare '/preload/INTERNAL_SDCARD/Samsung/Music/Over_the_horizon.mp3' '/data/media/Samsung/Music/Over_the_horizon.mp3' -> ok
/preload sucessfully unmounted
/data sucessfully unmounted
running factory-out time : 0.520s
Formatting /cache...
Formatting /cache...
Creating filesystem with parameters:
Size: 209715200
Block size: 4096
Blocks per group: 32768
Inodes per group: 6400
Inode size: 256
Journal blocks: 1024
Label:
Blocks: 51200
Block groups: 2
Reserved block group size: 15
Created filesystem with 11/12800 inodes and 1865/51200 blocks
warning: wipe_block_device: Wipe via secure discard failed, used discard instead
complted format with ext4
/dev/block/platform/msm_sdcc.1/by-name/cache is the encryptable partition?(0)
[installing post-recovery]
#mount /cache
stat() of /dev/block/platform/msm_sdcc.1/by-name/cache succeeded on try 1
/cache sucessfully mounted
#mkdir system cache 0775 /cache/recovery
#cp -y -f -v /tmp/recovery_backup.txt /cache/recovery/last_recovery
trace: __out_return: __scan_cp_dir :: cannot get src '/tmp/recovery_backup.txt' (No such file or directory)
#mount /data
stat() of /dev/block/platform/msm_sdcc.1/by-name/userdata succeeded on try 1
/data sucessfully mounted
#mkdir system log 0775 /data/log
#cp -y -f -v /tmp/recovery_backup.txt /data/log/recovery_log.txt
trace: __out_return: __scan_cp_dir :: cannot get src '/tmp/recovery_backup.txt' (No such file or directory)
/cache sucessfully unmounted
/data sucessfully unmounted
running post-recovery time : 0.147s
void copy_log_file(char const*, char const*, int) :: create recovery log file '/cache/recovery/log'
stat() of /dev/block/platform/msm_sdcc.1/by-name/cache succeeded on try 1
void copy_log_file(char const*, char const*, int) :: create recovery log file '/cache/recovery/last_log'
[email protected]:/ #
I hope i can help
Greetz
Thanks! That is helpful. I'm currently at work, will check back in a couple of hours.
thanks, but didn't work for me!
Well, i analyzed what we have and come to the following conclusions:
1. @locuter thanks for posting that information! I'm not sure if the posted log is actually a CWM log though. This date put me off:
Code:
Starting recovery on Tue Jan 1 00:58:03 2013
Also, it logs out this command, which looks like an update script:
Code:
Command: "/sbin/recovery" "--update_package=CACHE:recovery/sec_csc.zip" "--carry_out=csc_factory" "--wipe_data"
previous_runs = 0
send_intent = (null)
update_package = CACHE:recovery/sec_csc.zip
att_fota_update = 0
tmo_fota_update = 0
wipe_data = 1, wipe_cache = 1,wipe_sdcard = 0,delete_data = 0,wipe_data_crypto = 0,wipe_carrier = 0,no_wipe_custom=0
wipe_hdd_secure = 0
show_ui_text = 0
update_factory_csc = 1, update_home_csc = 0, factory_fota = 0
carry_out = csc_factory
tima_kernal_recovery = 0
(replacing path "CACHE:recovery/sec_csc.zip" with "/cache/recovery/sec_csc.zip")
And later proceeds to install the update:
Code:
Installing update...
minzip: Extracted file "/system/CSCVersion.txt"
minzip: Extracted file "/system/SW_Configuration.xml"
minzip: Extracted file "/system/VODB/de_DE/checked"
minzip: Extracted file "/system/VODB/de_DE/de_DE-ak-cur.lite.res"
minzip: Extracted file "/system/VODB/de_DE/de_DE-lk-text.lite.res"
minzip: Extracted file "/system/VODB/de_DE/de_DE.lang"
minzip: Extracted file "/system/VODB/de_DE/files.txt"
minzip: Extracted file "/system/VODB/en_GB/checked"
...
So my guess is this file was written by the stock recovery.
CWM *should* also write this file as soon as the recovery starts, or am I mistaken? I pulled the log from my N7000:
Code:
[email protected]:/cms_android/1_i9205/cwm_recovery_last_log$ cat last_log.n7000 | grep -A 20 Starting
Starting recovery on Tue Jun 4 18:18:00 2013
(GMT)framebuffer: fd 4 (800 x 1280)
PhilZ Touch 4
CWM Base version: 6.0.3.1
I:Build version: 4.93.6 - n7000
recovery filesystem table
=========================
0 /tmp ramdisk (null) (null) 0
1 /boot emmc /dev/block/mmcblk0p5 (null) 0
2 /recovery emmc /dev/block/mmcblk0p6 (null) 0
...
@locuter Did you flash CWM, enter the recovery, then cat the file? In any case, having the log file from the original recovery might still come in helpful, as it can give hints.
2. I looked through the last_log and tried to find anything that looks familiar to the graphics.c from the CM GitHub. The only thing referenced was this:
last_log:
Code:
[initialize ui and event]
initalized graphics for qualcomm.
pixel format -> GGL_PIXEL_FORMAT_RGBX_8888
return for qualcomm. double_buffering = 0
framebuffer: fd 4 (720 x 1280)
not turn off screen
In graphics.c, the value gets checked for when calling:
Code:
static int get_framebuffer(GGLSurface *fb)
Code:
else if (PIXEL_FORMAT == GGL_PIXEL_FORMAT_RGBX_8888) {
vi.red.offset = 24;
vi.red.length = 8;
vi.green.offset = 16;
vi.green.length = 8;
vi.blue.offset = 8;
vi.blue.length = 8;
vi.transp.offset = 0;
vi.transp.length = 8;
}
Well, that's all. I just wanted to do a little digging. Maybe someone who knows more about recoveries and/or how the framebuffer works (if it is even the problem) can look if the graphics.c from CM-Github can be modified and used for the 6.3.
One last thing:
If one of you guys do manage to pull a CWM recovery log, i'd be more than happy to check it out for clues.
Hi All!!
I have a Qmoible A5Classic and I want to develop its CWM Recovery. I want to fetch its recovery by
Code:
dd if=etc of=abc
but the problem is i cannot find which partition is my recovery partition.
Code:
cat proc/partitions
shows:
Code:
major minor #blocks name
7 0 1254 loop0
179 0 3815552 mmcblk0
179 1 1 mmcblk0p1
179 2 163840 mmcblk0p2
179 3 1064960 mmcblk0p3
179 4 2028784 mmcblk0p4
179 5 5120 mmcblk0p5
179 6 524288 mmcblk0p6
179 16 2048 mmcblk0boot1
179 8 2048 mmcblk0boot0
179 24 1949696 mmcblk1
179 25 1948672 mmcblk1p1
and
Code:
cat proc/mounts
show these:
Code:
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
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
tmpfs /mnt/obb tmpfs rw,relatime,mode=755,gid=1000 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
[email protected] /system ext4 rw,relatime,user_xattr,commit=1,barrier=1,data=ordered,noauto_da_alloc 0 0
/dev/block/loop0 /mnt/cd-rom iso9660 ro,relatime 0 0
[email protected] /data ext4 rw,nosuid,nodev,noatime,user_xattr,barrier=1,data=ordered,noauto_da_alloc 0 0
[email protected] /cache ext4 rw,nosuid,nodev,noatime,user_xattr,barrier=1,data=ordered,noauto_da_alloc 0 0
/dev/block/vold/179:4 /mnt/sdcard2 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/block/vold/179:25 /mnt/sdcard 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/block/vold/179:25 /mnt/secure/asec 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
tmpfs /mnt/sdcard/.android_secure tmpfs ro,relatime,size=0k,mode=000 0 0
Can anyone please point out the right partition?
PS: It is rooted.
Regards
ssm14293 said:
Hi All!!
Can anyone please point out the right partition?
PS: It is rooted.
Regards
Click to expand...
Click to collapse
I would recommend running the following command as root from terminal emulator:
Code:
cat /cache/recovery/last_log
This should tell you which partition is your recovery partition that you can then dump a copy of the stock recovery.img to your device. Let me know if you still have questions.
Sent from my SCH-I535 using xda premium
cmd says /recovery emmc recovery (null) 0
shimp208 said:
I would recommend running the following command as root from terminal emulator:
Code:
cat /cache/recovery/last_log
This should tell you which partition is your recovery partition that you can then dump a copy of the stock recovery.img to your device. Let me know if you still have questions.
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
This is what I get upon running your command:
Code:
Partition Information:
preloader 0x0000000000040000 0x0000000000000000 2 /dev/misc-sd
dsp_bl 0x00000000005c0000 0x0000000000040000 2 /dev/misc-sd
mbr 0x0000000000004000 0x0000000000000000 2 /dev/block/mmcblk0
ebr1 0x000000000005c000 0x0000000000004000 2 /dev/block/mmcblk0p1
pmt 0x0000000000400000 0x0000000000060000 2 /dev/block/mmcblk0
nvram 0x0000000000300000 0x0000000000460000 2 /dev/block/mmcblk0
seccfg 0x0000000000020000 0x0000000000760000 2 /dev/block/mmcblk0
uboot 0x0000000000060000 0x0000000000780000 2 /dev/block/mmcblk0
bootimg 0x0000000000600000 0x00000000007e0000 2 /dev/block/mmcblk0
recovery 0x0000000000600000 0x0000000000de0000 2 /dev/block/mmcblk0
sec_ro 0x0000000000600000 0x00000000013e0000 2 /dev/block/mmcblk0p5
misc 0x0000000000060000 0x00000000019e0000 2 /dev/block/mmcblk0
logo 0x0000000000300000 0x0000000001a40000 2 /dev/block/mmcblk0
expdb 0x00000000000a0000 0x0000000001d40000 2 /dev/block/mmcblk0
ebr2 0x0000000000004000 0x0000000001de0000 2 /dev/block/mmcblk0
android 0x0000000020100000 0x0000000001de4000 2 /dev/block/mmcblk0p6
cache 0x000000000a100000 0x0000000021ee4000 2 /dev/block/mmcblk0p2
usrdata 0x0000000041100000 0x000000002bfe4000 2 /dev/block/mmcblk0p3
fat 0x0000000000000001 0x000000006d0e4000 2 /dev/block/mmcblk0p4
bmtpool 0x000000007bafbfff 0xffffffffffa00000 2 /dev/block/mmcblk0
recovery filesystem table
=========================
0 /tmp ramdisk (null) (null) 0
1 /boot emmc boot (null) 0
2 /cache ext4 /dev/block/mmcblk0p2 (null) 0
3 /data ext4 /dev/block/mmcblk0p3 (null) 0
4 /misc emmc misc (null) 0
5 /recovery emmc recovery (null) 0
6 /sdcard vfat /dev/block/mmcblk1 /dev/block/mmcblk0p4 0
7 /sdcard2 vfat /dev/block/mmcblk0p4 (null) 0
8 /system ext4 /dev/block/mmcblk0p6 (null) 0
ssm14293 said:
This is what I get upon running your command:
Code:
Partition Information:
preloader 0x0000000000040000 0x0000000000000000 2 /dev/misc-sd
dsp_bl 0x00000000005c0000 0x0000000000040000 2 /dev/misc-sd
mbr 0x0000000000004000 0x0000000000000000 2 /dev/block/mmcblk0
ebr1 0x000000000005c000 0x0000000000004000 2 /dev/block/mmcblk0p1
pmt 0x0000000000400000 0x0000000000060000 2 /dev/block/mmcblk0
nvram 0x0000000000300000 0x0000000000460000 2 /dev/block/mmcblk0
seccfg 0x0000000000020000 0x0000000000760000 2 /dev/block/mmcblk0
uboot 0x0000000000060000 0x0000000000780000 2 /dev/block/mmcblk0
bootimg 0x0000000000600000 0x00000000007e0000 2 /dev/block/mmcblk0
recovery 0x0000000000600000 0x0000000000de0000 2 /dev/block/mmcblk0
sec_ro 0x0000000000600000 0x00000000013e0000 2 /dev/block/mmcblk0p5
misc 0x0000000000060000 0x00000000019e0000 2 /dev/block/mmcblk0
logo 0x0000000000300000 0x0000000001a40000 2 /dev/block/mmcblk0
expdb 0x00000000000a0000 0x0000000001d40000 2 /dev/block/mmcblk0
ebr2 0x0000000000004000 0x0000000001de0000 2 /dev/block/mmcblk0
android 0x0000000020100000 0x0000000001de4000 2 /dev/block/mmcblk0p6
cache 0x000000000a100000 0x0000000021ee4000 2 /dev/block/mmcblk0p2
usrdata 0x0000000041100000 0x000000002bfe4000 2 /dev/block/mmcblk0p3
fat 0x0000000000000001 0x000000006d0e4000 2 /dev/block/mmcblk0p4
bmtpool 0x000000007bafbfff 0xffffffffffa00000 2 /dev/block/mmcblk0
recovery filesystem table
=========================
0 /tmp ramdisk (null) (null) 0
1 /boot emmc boot (null) 0
2 /cache ext4 /dev/block/mmcblk0p2 (null) 0
3 /data ext4 /dev/block/mmcblk0p3 (null) 0
4 /misc emmc misc (null) 0
5 /recovery emmc recovery (null) 0
6 /sdcard vfat /dev/block/mmcblk1 /dev/block/mmcblk0p4 0
7 /sdcard2 vfat /dev/block/mmcblk0p4 (null) 0
8 /system ext4 /dev/block/mmcblk0p6 (null) 0
Click to expand...
Click to collapse
Very interesting from looking at your partition layout I can see that that /dev/block/mmcblk0 contains your recovery partition. However it appears /dev/block/mmcblk0 is a combined partition that also contains many critical parts of the phones file system such u-boot, /boot, and other bootloader related components. I would recommend running the following commands as root from either ADB shell:
Code:
cd /dev/block/platform
Then from the platform directory list the contents of the directory with the "ls" command. Once you have done that you should see a platform name (Or multiple platform names) for example on my Verizon Galaxy S3 it shows:
Code:
msm_sdcc.1
msm_sdcc.3
Cd into each of the platform directories (Or if there is only one platform directory "cd" into that) and list the contents of the platform directory using the "ls" command and look to see if it list a directory "by-name". If the platform directory your in contains the "by-name" folder run the following command:
Code:
ls -l /dev/block/platform/{platform directory name here}/by-name
If that command returns an output take note of the the block number that contains the recovery partition.
Another suggestion would be to run the following command to try and isolate the recovery.img from the larger /dev/block/mmcblk0 contents:
Code:
dd if=/dev/block/mmcblk0 of=mnt/sdcard/recovery.img bs=1 skip=6291456 count=8257536
Additionally you could try dumping the whole /dev/block/mmcblk0 partition using the command:
Code:
cat /dev/block/mmcblk0 > /mnt/sdcard/recovery.img
Let me know how the above commands work out for you .
shimp208 said:
[/HIDE]
Very interesting from looking at your partition layout I can see that that /dev/block/mmcblk0 contains your recovery partition. However it appears /dev/block/mmcblk0 is a combined partition that also contains many critical parts of the phones file system such u-boot, /boot, and other bootloader related components. I would recommend running the following commands as root from either ADB shell:
Code:
cd /dev/block/platform
Then from the platform directory list the contents of the directory with the "ls" command. Once you have done that you should see a platform name (Or multiple platform names) for example on my Verizon Galaxy S3 it shows:
Code:
msm_sdcc.1
msm_sdcc.3
Cd into each of the platform directories (Or if there is only one platform directory "cd" into that) and list the contents of the platform directory using the "ls" command and look to see if it list a directory "by-name". If the platform directory your in contains the "by-name" folder run the following command:
Code:
ls -l /dev/block/platform/{platform directory name here}/by-name
If that command returns an output take note of the the block number that contains the recovery partition.
Another suggestion would be to run the following command to try and isolate the recovery.img from the larger /dev/block/mmcblk0 contents:
Code:
dd if=/dev/block/mmcblk0 of=mnt/sdcard/recovery.img bs=1 skip=6291456 count=8257536
Additionally you could try dumping the whole /dev/block/mmcblk0 partition using the command:
Code:
cat /dev/block/mmcblk0 > /mnt/sdcard/recovery.img
Let me know how the above commands work out for you .
Click to expand...
Click to collapse
Jahan panha tussi great ho taufa qabul karo!
Click to expand...
Click to collapse
Translation: Dude!!!! Ur great!! please accept my humble gift :victory:
I dont have a by-name folder but only by-num, which really doesnt help. So now I will try your second method, extracting a part of the main image!! I'll tell you the result!!!
Regards
I did what you asked me to and it gave me a 7.87mb img file, but I cannot extract it using the unpack-mt65xx.pl. Invalid file. Can you please point me in the right direction please.
Regards
ssm14293 said:
I did what you asked me to and it gave me a 7.87mb img file, but I cannot extract it using the unpack-mt65xx.pl. Invalid file. Can you please point me in the right direction please.
Regards
Click to expand...
Click to collapse
In that case I would recommend trying to dump the whole /dev/block/mmcblk0 partition and seeing if you can unpack it then.
Some Luck with it...
shimp208 said:
In that case I would recommend trying to dump the whole /dev/block/mmcblk0 partition and seeing if you can unpack it then.
Click to expand...
Click to collapse
Hi I tried to extract the recovery.img created from your command using unmkboot in my Ubuntu VM. I got two files from it, a zImage file and an initramfs.cpio.gz files with this output:
Code:
unmkbootimg version 1.2 - Mikael Q Kuisma <[email protected]>
File ./images/recovery.img not a plain boot image, seeking for embedded image ... found!
Kernel size 3248084
Kernel address 0x10008000
Ramdisk size 506660
Ramdisk address 0x11000000
Secondary size 0
Secondary address 0x10f00000
Kernel tags address 0x10000100
Flash page size 2048
Board name is "1354555027"
Command line ""
This image is built using standard mkbootimg
Extracting kernel to file zImage ...
Extracting root filesystem to file initramfs.cpio.gz ...
All done.
---------------
To recompile this image, use:
mkbootimg --kernel zImage --ramdisk initramfs.cpio.gz --board '1354555027' -o new_boot.img
---------------
Now what can i do from here. I cannot extract the cpio.gz file, how will I do that.
Thanks for helping out!
I cannot dump the whole mmcblk0 because I dont have a memory card large enough for the dump, which is roughly 4gb.
Regards
Few Questions
shimp208 said:
In that case I would recommend trying to dump the whole /dev/block/mmcblk0 partition and seeing if you can unpack it then.
Click to expand...
Click to collapse
There is one thing I noted in the partition list. the stating point for boot, recovery and sec_ro is same i.e:
Code:
0x0000000000600000
but they end at different blocks, would that be a problem?
I think the over all partition type is ext4 which is supported by Ubuntu 13.04, can i do something to read the partition directly, like mount it in some way?
ssm14293 said:
Hi I tried to extract the recovery.img created from your command using unmkboot in my Ubuntu VM. I got two files from it, a zImage file and an initramfs.cpio.gz files with this output:
Code:
unmkbootimg version 1.2 - Mikael Q Kuisma <[email protected]>
File ./images/recovery.img not a plain boot image, seeking for embedded image ... found!
Kernel size 3248084
Kernel address 0x10008000
Ramdisk size 506660
Ramdisk address 0x11000000
Secondary size 0
Secondary address 0x10f00000
Kernel tags address 0x10000100
Flash page size 2048
Board name is "1354555027"
Command line ""
This image is built using standard mkbootimg
Extracting kernel to file zImage ...
Extracting root filesystem to file initramfs.cpio.gz ...
All done.
---------------
To recompile this image, use:
mkbootimg --kernel zImage --ramdisk initramfs.cpio.gz --board '1354555027' -o new_boot.img
---------------
Now what can i do from here. I cannot extract the cpio.gz file, how will I do that.
Thanks for helping out!
I cannot dump the whole mmcblk0 because I dont have a memory card large enough for the dump, which is roughly 4gb.
Regards
Click to expand...
Click to collapse
To unpack the cpio.gz file I would recommend downloading these Linux boot.img tools, they will allow you to unpack and repack the cpio.gz ramdisk file. Make sure after you download those tools you put them in your ~/bin folder and that the folder in your PATH or else the tools won't work as they rely on each other to function properly.
ssm14293 said:
There is one thing I noted in the partition list. the stating point for boot, recovery and sec_ro is same i.e:
Code:
0x0000000000600000
but they end at different blocks, would that be a problem?
I think the over all partition type is ext4 which is supported by Ubuntu 13.04, can i do something to read the partition directly, like mount it in some way?
Click to expand...
Click to collapse
I thought this offset for the partitions was very interesting, instead of going from one offset to another that would make it clear which parts of the /dev/block/mmcblk0 is recovery, boot, etc. they all seem to overlap. If you can find to dump the full partition and then transfer it to your computer you should be able to mount it in Ubuntu if it's ext4 and then read it's contents.
Found a way!
shimp208 said:
To unpack the cpio.gz file I would recommend downloading these Linux boot.img tools, they will allow you to unpack and repack the cpio.gz ramdisk file. Make sure after you download those tools you put them in your ~/bin folder and that the folder in your PATH or else the tools won't work as they rely on each other to function properly.
I thought this offset for the partitions was very interesting, instead of going from one offset to another that would make it clear which parts of the /dev/block/mmcblk0 is recovery, boot, etc. they all seem to overlap. If you can find to dump the full partition and then transfer it to your computer you should be able to mount it in Ubuntu if it's ext4 and then read it's contents.
Click to expand...
Click to collapse
Hi again!!
I just got myself an 8GB memory card. I also searched more about nandroid backups for non-CWM phones. I got across onandroid, it creates img files of all partitions. It was created by someone from XDA Forums, can't remember the name. So at the moment it is generating MD5 Checksum.
After this I will create my OWN Rom and CWM for this phone :victory: , well after my finals .
Thanks for your help! :highfive:
For all Qmobile Rooted users, use onandroid to create backups, but at your own risk. I can confirm for QMobiel A5 Classic
where to copy symphony CWM recovery.img using dd command
I am Moniruzzaman from Dhaka, Bangladesh...
Please forgive me for my weak English.
I have created a CWM recovery img (Latest Touch Version) for my rooted Symphony W85. My device partitions is similar to the Qmoible A5Classic. Now I have failed to copy it to the recovery partition as i could not figure out which is my recovery partition.
Partition Information:
preloader 0x0000000000040000 0x0000000000000000 2 /dev/misc-sd
dsp_bl 0x00000000005c0000 0x0000000000040000 2 /dev/misc-sd
mbr 0x0000000000004000 0x0000000000000000 2 /dev/block/mmcblk0
ebr1 0x000000000005c000 0x0000000000004000 2 /dev/block/mmcblk0p1
pmt 0x0000000000400000 0x0000000000060000 2 /dev/block/mmcblk0
nvram 0x0000000000300000 0x0000000000460000 2 /dev/block/mmcblk0
seccfg 0x0000000000020000 0x0000000000760000 2 /dev/block/mmcblk0
uboot 0x0000000000060000 0x0000000000780000 2 /dev/block/mmcblk0
bootimg 0x0000000000600000 0x00000000007e0000 2 /dev/block/mmcblk0
recovery 0x0000000000600000 0x0000000000de0000 2 /dev/block/mmcblk0
sec_ro 0x0000000000600000 0x00000000013e0000 2 /dev/block/mmcblk0p5
misc 0x0000000000060000 0x00000000019e0000 2 /dev/block/mmcblk0
logo 0x0000000000300000 0x0000000001a40000 2 /dev/block/mmcblk0
expdb 0x00000000000a0000 0x0000000001d40000 2 /dev/block/mmcblk0
ebr2 0x0000000000004000 0x0000000001de0000 2 /dev/block/mmcblk0
android 0x0000000020100000 0x0000000001de4000 2 /dev/block/mmcblk0p6
cache 0x000000000a100000 0x0000000021ee4000 2 /dev/block/mmcblk0p2
usrdata 0x0000000041100000 0x000000002bfe4000 2 /dev/block/mmcblk0p3
fat 0x0000000000000001 0x000000006d0e4000 2 /dev/block/mmcblk0p4
bmtpool 0x000000007bafbfff 0xffffffffffa00000 2 /dev/block/mmcblk0
recovery filesystem table
=========================
0 /tmp ramdisk (null) (null) 0
1 /boot emmc boot (null) 0
2 /cache ext4 /dev/block/mmcblk0p2 (null) 0
3 /data ext4 /dev/block/mmcblk0p3 (null) 0
4 /misc emmc misc (null) 0
5 /recovery emmc recovery (null) 0
6 /sdcard vfat /dev/block/mmcblk1 /dev/block/mmcblk0p4 0
7 /sdcard2 vfat /dev/block/mmcblk0p4 (null) 0
8 /system ext4 /dev/block/mmcblk0p6 (null) 0
I have flashed the recovery.img using dd if=mnt/sdcard/recovery.img of=/dev/recovery. Everything was fine except my gsm signal was gone.
Then I tried flashed stock recovery.img using dd if=mnt/sdcard/recovery.img of=/dev/recovery - everything works fine again.
I have come so far and now i can't fine the right partitions. I am very frustrated.
Can any one please help me how to flash my CWM recovery img (Latest Touch Version) to my device as it is combined partitions.
shimp208 said:
.
Click to expand...
Click to collapse
What about this: this is from Lenovo TAB S8-50 (USA/BestBuy) Wifi version....
Starting recovery on Thu Dec 4 03:55:45 2014
recovery filesystem table
=========================
0 /reserved hidden /dev/block/platform/intel/by-label/reserved 0
1 /ESP vfat /dev/block/platform/intel/by-label/ESP 0
2 /boot hidden /dev/block/platform/intel/by-label/boot 0
3 /recovery hidden /dev/block/platform/intel/by-label/recovery 0
4 /fastboot hidden /dev/block/platform/intel/by-label/fastboot 0
5 /reserved_1 hidden /dev/block/platform/intel/by-label/reserved_1 0
6 /panic raw /dev/block/platform/intel/by-label/panic 0
7 /factory ext4 /dev/block/platform/intel/by-label/factory 0
8 /misc emmc /dev/block/platform/intel/by-label/misc 0
9 /config ext4 /dev/block/platform/intel/by-label/config 0
10 /cache ext4 /dev/block/platform/intel/by-label/cache 0
11 /system ext4 /dev/block/platform/intel/by-label/system 0
12 /data ext4 /dev/block/platform/intel/by-label/data -16384
13 /sdcard vfat /dev/block/mmcblk1p1 0
14 /tmp ramdisk ramdisk 0
jazzespresso said:
What about this: this is from Lenovo TAB S8-50 (USA/BestBuy) Wifi version....
Starting recovery on Thu Dec 4 03:55:45 2014
recovery filesystem table
=========================
0 /reserved hidden /dev/block/platform/intel/by-label/reserved 0
1 /ESP vfat /dev/block/platform/intel/by-label/ESP 0
2 /boot hidden /dev/block/platform/intel/by-label/boot 0
3 /recovery hidden /dev/block/platform/intel/by-label/recovery 0
4 /fastboot hidden /dev/block/platform/intel/by-label/fastboot 0
5 /reserved_1 hidden /dev/block/platform/intel/by-label/reserved_1 0
6 /panic raw /dev/block/platform/intel/by-label/panic 0
7 /factory ext4 /dev/block/platform/intel/by-label/factory 0
8 /misc emmc /dev/block/platform/intel/by-label/misc 0
9 /config ext4 /dev/block/platform/intel/by-label/config 0
10 /cache ext4 /dev/block/platform/intel/by-label/cache 0
11 /system ext4 /dev/block/platform/intel/by-label/system 0
12 /data ext4 /dev/block/platform/intel/by-label/data -16384
13 /sdcard vfat /dev/block/mmcblk1p1 0
14 /tmp ramdisk ramdisk 0
Click to expand...
Click to collapse
I would recommend running the following command to dump your recovery partition:
Code:
cat /dev/block/platform/intel/by-label/recovery > /mnt/sdcard/recovery.img
Let me know if you still have questions, happy to help you out.
shimp208 said:
I would recommend running the following command to dump your recovery partition:
Code:
cat /dev/block/platform/intel/by-label/recovery > /mnt/sdcard/recovery.img
Let me know if you still have questions, happy to help you out.
Click to expand...
Click to collapse
thank you very much...what about boot.img?
jazzespresso said:
thank you very much...what about boot.img?
Click to expand...
Click to collapse
For boot you would run the command:
Code:
cat /dev/block/platform/intel/by-label/boot > /mnt/sdcard/boot.img
Hope this helps you!
Can anyone help me ? I ran the script bellow trying to expand my system partition to solve a problem and now I've lost my recoverymode. I get a 2 min blackscreen and then it starts.
COde that got me lost:
Code:
#!/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 1740MB
parted /dev/block/mmcblk0 mkpart primary 1740MB 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
fi
Follow info:
Code:
[email protected]:/ $ cat /proc/partitions
cat /proc/partitions
major minor #blocks name
179 0 30535680 mmcblk0
179 1 65536 mmcblk0p1
179 2 512 mmcblk0p2
179 3 512 mmcblk0p3
179 4 2048 mmcblk0p4
179 5 512 mmcblk0p5
179 6 512 mmcblk0p6
179 7 24576 mmcblk0p7
179 8 512 mmcblk0p8
179 9 1 mmcblk0p9
179 10 3072 mmcblk0p10
179 11 3072 mmcblk0p11
179 12 780 mmcblk0p12
179 13 780 mmcblk0p13
179 14 780 mmcblk0p14
179 15 8192 mmcblk0p15
179 16 8192 mmcblk0p16
179 17 8 mmcblk0p17
179 18 16384 mmcblk0p18
179 19 16384 mmcblk0p19
179 20 512 mmcblk0p20
179 21 512 mmcblk0p21
179 22 1556480 mmcblk0p22
179 23 819200 mmcblk0p23
179 24 26714112 mmcblk0p24
179 27 24576 mmcblk0p27
179 28 3072 mmcblk0p28
179 29 8 mmcblk0p29
179 30 32768 mmcblk0p30
179 31 32768 mmcblk0p31
259 0 512 mmcblk0p32
259 1 512 mmcblk0p33
259 2 16384 mmcblk0p34
259 3 879599 mmcblk0p35
[email protected]:/ $
Code:
[email protected]:/dev/block/platform/msm_sdcc.1/by-name # ls -l
ls -l
lrwxrwxrwx root root 2015-07-20 22:30 DDR -> /dev/block/mmcblk0p29
lrwxrwxrwx root root 2015-07-20 22:30 aboot -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 2015-07-20 22:30 boot -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 2015-07-20 22:30 cache -> /dev/block/mmcblk0p23
lrwxrwxrwx root root 2015-07-20 22:30 drm -> /dev/block/mmcblk0p15
lrwxrwxrwx root root 2015-07-20 22:30 eksst -> /dev/block/mmcblk0p21
lrwxrwxrwx root root 2015-07-20 22:30 encrypt -> /dev/block/mmcblk0p20
lrwxrwxrwx root root 2015-07-20 22:30 factory -> /dev/block/mmcblk0p19
lrwxrwxrwx root root 2015-07-20 22:30 fota -> /dev/block/mmcblk0p30
lrwxrwxrwx root root 2015-07-20 22:30 fsg -> /dev/block/mmcblk0p28
lrwxrwxrwx root root 2015-07-20 22:30 grow -> /dev/block/mmcblk0p35
lrwxrwxrwx root root 2015-07-20 22:30 m9kefs1 -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 2015-07-20 22:30 m9kefs2 -> /dev/block/mmcblk0p13
lrwxrwxrwx root root 2015-07-20 22:30 m9kefs3 -> /dev/block/mmcblk0p14
lrwxrwxrwx root root 2015-07-20 22:30 misc -> /dev/block/mmcblk0p18
lrwxrwxrwx root root 2015-07-20 22:30 modem -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 2015-07-20 22:30 modemst1 -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 2015-07-20 22:30 modemst2 -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 2015-07-20 22:30 mpt -> /dev/block/mmcblk0p31
lrwxrwxrwx root root 2015-07-20 22:30 pad -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 2015-07-20 22:30 recovery -> /dev/block/mmcblk0p27
lrwxrwxrwx root root 2015-07-20 22:30 reserved -> /dev/block/mmcblk0p34
lrwxrwxrwx root root 2015-07-20 22:30 rpm -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 2015-07-20 22:30 rpmbak -> /dev/block/mmcblk0p33
lrwxrwxrwx root root 2015-07-20 22:30 sbl1 -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 2015-07-20 22:30 sbl2 -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 2015-07-20 22:30 sbl3 -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 2015-07-20 22:30 sns -> /dev/block/mmcblk0p16
lrwxrwxrwx root root 2015-07-20 22:30 ssd -> /dev/block/mmcblk0p17
lrwxrwxrwx root root 2015-07-20 22:30 system -> /dev/block/mmcblk0p22
lrwxrwxrwx root root 2015-07-20 22:30 tz -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 2015-07-20 22:30 tzbak -> /dev/block/mmcblk0p32
lrwxrwxrwx root root 2015-07-20 22:30 userdata -> /dev/block/mmcblk0p24
[email protected]:/dev/block/platform/msm_sdcc.1/by-name #
Code:
[email protected]:/dev/block $ cat /proc/mounts
cat /proc/mounts
rootfs / rootfs ro,seclabel,relatime 0 0
tmpfs /dev tmpfs rw,seclabel,nosuid,relatime,mode=755 0 0
devpts /dev/pts devpts rw,seclabel,relatime,mode=600 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,seclabel,relatime 0 0
selinuxfs /sys/fs/selinux selinuxfs rw,relatime 0 0
debugfs /sys/kernel/debug debugfs rw,relatime 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
none /sys/fs/cgroup tmpfs rw,seclabel,relatime,mode=750,gid=1000 0 0
tmpfs /mnt/asec tmpfs rw,seclabel,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/obb tmpfs rw,seclabel,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/fuse tmpfs rw,seclabel,relatime,mode=775,gid=1000 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
/dev/block/platform/msm_sdcc.1/by-name/system /system ext4 ro,seclabel,relatime,
data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/cache /cache ext4 rw,seclabel,nosuid,node
v,noatime,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/userdata /data ext4 rw,seclabel,nosuid,no
dev,noatime,noauto_da_alloc,data=ordered 0 0
[email protected]:/dev/block $
dihhedessa said:
Can anyone help me ? I ran the script bellow trying to expand my system partition to solve a problem and now I've lost my recoverymode. I get a 2 min blackscreen and then it starts.
COde that got me lost:
Code:
#!/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 1740MB
parted /dev/block/mmcblk0 mkpart primary 1740MB 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
fi
Follow info:
Code:
[email protected]:/ $ cat /proc/partitions
cat /proc/partitions
major minor #blocks name
179 0 30535680 mmcblk0
179 1 65536 mmcblk0p1
179 2 512 mmcblk0p2
179 3 512 mmcblk0p3
179 4 2048 mmcblk0p4
179 5 512 mmcblk0p5
179 6 512 mmcblk0p6
179 7 24576 mmcblk0p7
179 8 512 mmcblk0p8
179 9 1 mmcblk0p9
179 10 3072 mmcblk0p10
179 11 3072 mmcblk0p11
179 12 780 mmcblk0p12
179 13 780 mmcblk0p13
179 14 780 mmcblk0p14
179 15 8192 mmcblk0p15
179 16 8192 mmcblk0p16
179 17 8 mmcblk0p17
179 18 16384 mmcblk0p18
179 19 16384 mmcblk0p19
179 20 512 mmcblk0p20
179 21 512 mmcblk0p21
179 22 1556480 mmcblk0p22
179 23 819200 mmcblk0p23
179 24 26714112 mmcblk0p24
179 27 24576 mmcblk0p27
179 28 3072 mmcblk0p28
179 29 8 mmcblk0p29
179 30 32768 mmcblk0p30
179 31 32768 mmcblk0p31
259 0 512 mmcblk0p32
259 1 512 mmcblk0p33
259 2 16384 mmcblk0p34
259 3 879599 mmcblk0p35
[email protected]:/ $
Code:
[email protected]:/dev/block/platform/msm_sdcc.1/by-name # ls -l
ls -l
lrwxrwxrwx root root 2015-07-20 22:30 DDR -> /dev/block/mmcblk0p29
lrwxrwxrwx root root 2015-07-20 22:30 aboot -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 2015-07-20 22:30 boot -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 2015-07-20 22:30 cache -> /dev/block/mmcblk0p23
lrwxrwxrwx root root 2015-07-20 22:30 drm -> /dev/block/mmcblk0p15
lrwxrwxrwx root root 2015-07-20 22:30 eksst -> /dev/block/mmcblk0p21
lrwxrwxrwx root root 2015-07-20 22:30 encrypt -> /dev/block/mmcblk0p20
lrwxrwxrwx root root 2015-07-20 22:30 factory -> /dev/block/mmcblk0p19
lrwxrwxrwx root root 2015-07-20 22:30 fota -> /dev/block/mmcblk0p30
lrwxrwxrwx root root 2015-07-20 22:30 fsg -> /dev/block/mmcblk0p28
lrwxrwxrwx root root 2015-07-20 22:30 grow -> /dev/block/mmcblk0p35
lrwxrwxrwx root root 2015-07-20 22:30 m9kefs1 -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 2015-07-20 22:30 m9kefs2 -> /dev/block/mmcblk0p13
lrwxrwxrwx root root 2015-07-20 22:30 m9kefs3 -> /dev/block/mmcblk0p14
lrwxrwxrwx root root 2015-07-20 22:30 misc -> /dev/block/mmcblk0p18
lrwxrwxrwx root root 2015-07-20 22:30 modem -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 2015-07-20 22:30 modemst1 -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 2015-07-20 22:30 modemst2 -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 2015-07-20 22:30 mpt -> /dev/block/mmcblk0p31
lrwxrwxrwx root root 2015-07-20 22:30 pad -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 2015-07-20 22:30 recovery -> /dev/block/mmcblk0p27
lrwxrwxrwx root root 2015-07-20 22:30 reserved -> /dev/block/mmcblk0p34
lrwxrwxrwx root root 2015-07-20 22:30 rpm -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 2015-07-20 22:30 rpmbak -> /dev/block/mmcblk0p33
lrwxrwxrwx root root 2015-07-20 22:30 sbl1 -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 2015-07-20 22:30 sbl2 -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 2015-07-20 22:30 sbl3 -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 2015-07-20 22:30 sns -> /dev/block/mmcblk0p16
lrwxrwxrwx root root 2015-07-20 22:30 ssd -> /dev/block/mmcblk0p17
lrwxrwxrwx root root 2015-07-20 22:30 system -> /dev/block/mmcblk0p22
lrwxrwxrwx root root 2015-07-20 22:30 tz -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 2015-07-20 22:30 tzbak -> /dev/block/mmcblk0p32
lrwxrwxrwx root root 2015-07-20 22:30 userdata -> /dev/block/mmcblk0p24
[email protected]:/dev/block/platform/msm_sdcc.1/by-name #
Code:
[email protected]:/dev/block $ cat /proc/mounts
cat /proc/mounts
rootfs / rootfs ro,seclabel,relatime 0 0
tmpfs /dev tmpfs rw,seclabel,nosuid,relatime,mode=755 0 0
devpts /dev/pts devpts rw,seclabel,relatime,mode=600 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,seclabel,relatime 0 0
selinuxfs /sys/fs/selinux selinuxfs rw,relatime 0 0
debugfs /sys/kernel/debug debugfs rw,relatime 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
none /sys/fs/cgroup tmpfs rw,seclabel,relatime,mode=750,gid=1000 0 0
tmpfs /mnt/asec tmpfs rw,seclabel,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/obb tmpfs rw,seclabel,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/fuse tmpfs rw,seclabel,relatime,mode=775,gid=1000 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
/dev/block/platform/msm_sdcc.1/by-name/system /system ext4 ro,seclabel,relatime,
data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/cache /cache ext4 rw,seclabel,nosuid,node
v,noatime,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/userdata /data ext4 rw,seclabel,nosuid,no
dev,noatime,noauto_da_alloc,data=ordered 0 0
[email protected]:/dev/block $
Click to expand...
Click to collapse
@shimp208 and @jazzespresso maybe you guys could please help me? I am desperate!
Hi there,
I've the same problem, recovery is in mmcblk0, someone can help me please ? I can't find any solutions.
AndroGeek
Partion info of a my 6735 rooted android device
How can I get "dumchar_info", or "Part_Name ,Size ,StartAddr,Type,Map,To" info with adb command of a rooted mt6735 device with 5.1 lollipop? Thanks a lot in anticipation.
So it's nothing new, but solutions like "Link2SD", "Folder Mount" seems to don't work.
When I install for example AcrobatReader, Link2SD tells me that about 100% is linked, but still internal storage was decreased about 20MB-30MB - so I think that doesn't work.
I make some tryings on my own, broke system on my phone, upload another, make another tryings and got some reboots etc...
I want to move whole data partition to SD. Maybe someone know ready to use ROM which have that? Maybe it's very bad idea, but why?
Here is some details about phone:
Xperia Neo V, cm-10-20131006-NIGHTLY-haida (but I'm not relevant to it), unlocked bootloader.
(I cant post pictures....)
mount
Code:
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
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
tmpfs /mnt/obb tmpfs rw,relatime,mode=755,gid=1000 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
/dev/block/mtdblock0 /system yaffs2 ro,relatime 0 0
/dev/block/mtdblock3 /data yaffs2 rw,nosuid,nodev,relatime 0 0
/dev/block/mtdblock2 /cache yaffs2 rw,nosuid,nodev,relatime 0 0
/dev/block/mmcblk0p2 /data/sdext2 ext2 rw,relatime,errors=continue 0 0
/sys/kernel/debug /sys/kernel/debug debugfs rw,relatime 0 0
/dev/block/vold/179:1 /storage/sdcard0 vfat rw,dirsync,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/block/vold/179:1 /mnt/secure/asec 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
tmpfs /storage/sdcard0/.android_secure tmpfs ro,relatime,size=0k,mode=000 0 0
df
Code:
Filesystem Size Used Free Blksize
/dev 179.4M 48K 179.4M 4096
/mnt/asec 179.4M 0K 179.4M 4096
/mnt/obb 179.4M 0K 179.4M 4096
/system 400M 360.6M 39.4M 4096
/data 420M 132.1M 287.9M 4096
/cache 101.5M 73.7M 27.8M 4096
/data/sdext2 1.4G 135.5M 1.3G 4096
/storage/sdcard0 377.2M 93.9M 283.3M 4096
/mnt/secure/asec 377.2M 93.9M 283.3M 4096
mtd
Code:
dev: size erasesize name
mtd0: 19000000 00020000 "system"
mtd1: 00600000 00020000 "appslog"
mtd2: 06580000 00020000 "cache"
mtd3: 1a400000 00020000 "userdata"
vold.fstab
Code:
## Vold 2.0 fstab for Mogami
#
## - San Mehat ([email protected])
##
#######################
## Regular device mount
##
## Format: dev_mount <label> <mount_point> <part> <sysfs_path1...>
## label - Label for the volume
## mount_point - Where the volume will be mounted
## part - Partition # (1 based), or 'auto' for first usable partition.
## <sysfs_path> - List of sysfs paths to source devices
######################
# Mounts the first usable partition of the specified device
dev_mount sdcard /storage/sdcard0 auto /devices/platform/msm_sdcc.4/mmc_host/mmc1
init.rc
Code:
# Copyright (C) 2012 The Android Open Source Project
#
# IMPORTANT: Do not create world writable files or directories.
# This is a common source of Android security bugs.
#
import /init.${ro.hardware}.rc
import /init.usb.rc
import /init.trace.rc
on early-init
# Set init and its forked children's oom_adj.
write /proc/1/oom_adj -16
start ueventd
# create mountpoints
mkdir /mnt 0775 root system
on init
sysclktz 0
loglevel 3
# setup the global environment
export PATH /sbin:/vendor/bin:/system/sbin:/system/bin:/system/xbin
export LD_LIBRARY_PATH /vendor/lib:/system/lib
export ANDROID_BOOTLOGO 1
export ANDROID_ROOT /system
export ANDROID_ASSETS /system/app
export ANDROID_DATA /data
export ASEC_MOUNTPOINT /mnt/asec
export LOOP_MOUNTPOINT /mnt/obb
export BOOTCLASSPATH /system/framework/core.jar:/system/framework/core-junit.jar:/system/framework/bouncycastle.jar:/system/framework/ext.jar:/system/framework/framework.jar:/system/framework/framework2.jar:/system/framework/android.policy.jar:/system/framework/services.jar:/system/framework/apache-xml.jar
# Backward compatibility
symlink /system/etc /etc
symlink /sys/kernel/debug /d
# Right now vendor lives on the same filesystem as system,
# but someday that may change.
symlink /system/vendor /vendor
# Create cgroup mount point for cpu accounting
mkdir /acct
mount cgroup none /acct cpuacct
mkdir /acct/uid
mkdir /system
mkdir /data 0771 system system
mkdir /cache 0771 system cache
mkdir /config 0500 root root
# Directory for putting things only root should see.
mkdir /mnt/secure 0700 root root
# Directory for staging bindmounts
mkdir /mnt/secure/staging 0700 root root
# Directory-target for where the secure container
# imagefile directory will be bind-mounted
mkdir /mnt/secure/asec 0700 root root
# Secure container public mount points.
mkdir /mnt/asec 0700 root system
mount tmpfs tmpfs /mnt/asec mode=0755,gid=1000
# Filesystem image public mount points.
mkdir /mnt/obb 0700 root system
mount tmpfs tmpfs /mnt/obb mode=0755,gid=1000
write /proc/sys/kernel/panic_on_oops 1
write /proc/sys/kernel/hung_task_timeout_secs 0
write /proc/cpu/alignment 4
write /proc/sys/kernel/sched_latency_ns 10000000
write /proc/sys/kernel/sched_wakeup_granularity_ns 2000000
write /proc/sys/kernel/sched_compat_yield 1
write /proc/sys/kernel/sched_child_runs_first 0
write /proc/sys/kernel/randomize_va_space 2
write /proc/sys/kernel/kptr_restrict 2
write /proc/sys/kernel/dmesg_restrict 1
write /proc/sys/vm/mmap_min_addr 32768
write /proc/sys/kernel/sched_rt_runtime_us 950000
write /proc/sys/kernel/sched_rt_period_us 1000000
# Create cgroup mount points for process groups
mkdir /dev/cpuctl
mount cgroup none /dev/cpuctl cpu
chown system system /dev/cpuctl
chown system system /dev/cpuctl/tasks
chmod 0660 /dev/cpuctl/tasks
write /dev/cpuctl/cpu.shares 1024
write /dev/cpuctl/cpu.rt_runtime_us 950000
write /dev/cpuctl/cpu.rt_period_us 1000000
mkdir /dev/cpuctl/apps
chown system system /dev/cpuctl/apps/tasks
chmod 0666 /dev/cpuctl/apps/tasks
write /dev/cpuctl/apps/cpu.shares 1024
write /dev/cpuctl/apps/cpu.rt_runtime_us 800000
write /dev/cpuctl/apps/cpu.rt_period_us 1000000
mkdir /dev/cpuctl/apps/bg_non_interactive
chown system system /dev/cpuctl/apps/bg_non_interactive/tasks
chmod 0666 /dev/cpuctl/apps/bg_non_interactive/tasks
# 5.0 %
write /dev/cpuctl/apps/bg_non_interactive/cpu.shares 52
write /dev/cpuctl/apps/bg_non_interactive/cpu.rt_runtime_us 700000
write /dev/cpuctl/apps/bg_non_interactive/cpu.rt_period_us 1000000
# Allow everybody to read the xt_qtaguid resource tracking misc dev.
# This is needed by any process that uses socket tagging.
chmod 0644 /dev/xt_qtaguid
on fs
# mount mtd partitions
# Mount /system rw first to give the filesystem a chance to save a checkpoint
mount yaffs2 [email protected] /system
mount yaffs2 [email protected] /system ro remount
mount yaffs2 [email protected] /data nosuid nodev
mount yaffs2 [email protected] /cache nosuid nodev
on post-fs
# once everything is setup, no need to modify /
mount rootfs rootfs / ro remount
# We chown/chmod /cache again so because mount is run as root + defaults
chown system cache /cache
chmod 0771 /cache
# This may have been created by the recovery system with odd permissions
chown system cache /cache/recovery
chmod 0770 /cache/recovery
#change permissions on vmallocinfo so we can grab it from bugreports
chown root log /proc/vmallocinfo
chmod 0440 /proc/vmallocinfo
#change permissions on kmsg & sysrq-trigger so bugreports can grab kthread stacks
chown root system /proc/kmsg
chmod 0440 /proc/kmsg
chown root system /proc/sysrq-trigger
chmod 0220 /proc/sysrq-trigger
# create the lost+found directories, so as to enforce our permissions
mkdir /cache/lost+found 0770 root root
on post-fs-data
# We chown/chmod /data again so because mount is run as root + defaults
chown system system /data
chmod 0771 /data
# Create dump dir and collect dumps.
# Do this before we mount cache so eventually we can use cache for
# storing dumps on platforms which do not have a dedicated dump partition.
mkdir /data/dontpanic 0750 root log
# Collect apanic data, free resources and re-arm trigger
copy /proc/apanic_console /data/dontpanic/apanic_console
chown root log /data/dontpanic/apanic_console
chmod 0640 /data/dontpanic/apanic_console
copy /proc/apanic_threads /data/dontpanic/apanic_threads
chown root log /data/dontpanic/apanic_threads
chmod 0640 /data/dontpanic/apanic_threads
write /proc/apanic_console 1
# create basic filesystem structure
mkdir /data/misc 01771 system misc
mkdir /data/misc/bluetoothd 0770 bluetooth bluetooth
mkdir /data/misc/bluetooth 0770 system system
mkdir /data/misc/keystore 0700 keystore keystore
mkdir /data/misc/keychain 0771 system system
mkdir /data/misc/vpn 0770 system vpn
mkdir /data/misc/systemkeys 0700 system system
# give system access to wpa_supplicant.conf for backup and restore
mkdir /data/misc/wifi 0770 wifi wifi
chmod 0660 /data/misc/wifi/wpa_supplicant.conf
mkdir /data/local 0751 root root
# For security reasons, /data/local/tmp should always be empty.
# Do not place files or directories in /data/local/tmp
mkdir /data/local/tmp 0771 shell shell
mkdir /data/data 0771 system system
mkdir /data/app-private 0771 system system
mkdir /data/app-asec 0700 root root
mkdir /data/app 0771 system system
mkdir /data/property 0700 root root
mkdir /data/ssh 0750 root shell
mkdir /data/ssh/empty 0700 root root
mkdir /data/radio 0770 radio radio
# create dalvik-cache and double-check the perms, so as to enforce our permissions
mkdir /data/dalvik-cache 0771 system system
chown system system /data/dalvik-cache
chmod 0771 /data/dalvik-cache
# create resource-cache and double-check the perms
mkdir /data/resource-cache 0771 system system
chown system system /data/resource-cache
chmod 0771 /data/resource-cache
# create the lost+found directories, so as to enforce our permissions
mkdir /data/lost+found 0770 root root
# create directory for DRM plug-ins - give drm the read/write access to
# the following directory.
mkdir /data/drm 0770 drm drm
# If there is no fs-post-data action in the init.<device>.rc file, you
# must uncomment this line, otherwise encrypted filesystems
# won't work.
# Set indication (checked by vold) that we have finished this action
#setprop vold.post_fs_data_done 1
# Include extra init file
import /init.cm.rc
on boot
# basic network init
ifup lo
hostname localhost
domainname localdomain
# set RLIMIT_NICE to allow priorities from 19 to -20
setrlimit 13 40 40
# Memory management. Basic kernel parameters, and allow the high
# level system server to be able to adjust the kernel OOM driver
# parameters to match how it is managing things.
write /proc/sys/vm/overcommit_memory 1
write /proc/sys/vm/min_free_order_shift 4
chown root system /sys/module/lowmemorykiller/parameters/adj
chmod 0664 /sys/module/lowmemorykiller/parameters/adj
chown root system /sys/module/lowmemorykiller/parameters/minfree
chmod 0664 /sys/module/lowmemorykiller/parameters/minfree
# Tweak background writeout
write /proc/sys/vm/dirty_expire_centisecs 200
write /proc/sys/vm/dirty_background_ratio 5
# Permissions for System Server and daemons.
chown radio system /sys/android_power/state
chown radio system /sys/android_power/request_state
chown radio system /sys/android_power/acquire_full_wake_lock
chown radio system /sys/android_power/acquire_partial_wake_lock
chown radio system /sys/android_power/release_wake_lock
chown system system /sys/power/state
chown system system /sys/power/wakeup_count
chown radio system /sys/power/wake_lock
chown radio system /sys/power/wake_unlock
chmod 0660 /sys/power/state
chmod 0660 /sys/power/wake_lock
chmod 0660 /sys/power/wake_unlock
chown system system /sys/devices/system/cpu/cpufreq/interactive/timer_rate
chmod 0660 /sys/devices/system/cpu/cpufreq/interactive/timer_rate
chown system system /sys/devices/system/cpu/cpufreq/interactive/min_sample_time
chmod 0660 /sys/devices/system/cpu/cpufreq/interactive/min_sample_time
chown system system /sys/devices/system/cpu/cpufreq/interactive/hispeed_freq
chmod 0660 /sys/devices/system/cpu/cpufreq/interactive/hispeed_freq
chown system system /sys/devices/system/cpu/cpufreq/interactive/go_hispeed_load
chmod 0660 /sys/devices/system/cpu/cpufreq/interactive/go_hispeed_load
chown system system /sys/devices/system/cpu/cpufreq/interactive/above_hispeed_delay
chmod 0660 /sys/devices/system/cpu/cpufreq/interactive/above_hispeed_delay
chown system system /sys/devices/system/cpu/cpufreq/interactive/boost
chmod 0660 /sys/devices/system/cpu/cpufreq/interactive/boost
chown system system /sys/devices/system/cpu/cpufreq/interactive/boostpulse
chown system system /sys/devices/system/cpu/cpufreq/interactive/input_boost
chmod 0660 /sys/devices/system/cpu/cpufreq/interactive/input_boost
# Assume SMP uses shared cpufreq policy for all CPUs
chown system system /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor
chmod 0664 /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor
chown system system /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq
chmod 0664 /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq
chown system system /sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq
chmod 0664 /sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq
chown system system /sys/class/timed_output/vibrator/enable
chown system system /sys/class/leds/keyboard-backlight/brightness
chown system system /sys/class/leds/lcd-backlight/brightness
chown system system /sys/class/leds/button-backlight/brightness
chown system system /sys/class/leds/jogball-backlight/brightness
chown system system /sys/class/leds/red/brightness
chown system system /sys/class/leds/green/brightness
chown system system /sys/class/leds/blue/brightness
chown system system /sys/class/leds/red/device/grpfreq
chown system system /sys/class/leds/red/device/grppwm
chown system system /sys/class/leds/red/device/blink
chown system system /sys/class/leds/red/brightness
chown system system /sys/class/leds/green/brightness
chown system system /sys/class/leds/blue/brightness
chown system system /sys/class/leds/red/device/grpfreq
chown system system /sys/class/leds/red/device/grppwm
chown system system /sys/class/leds/red/device/blink
chown system system /sys/class/timed_output/vibrator/enable
chown system system /sys/module/sco/parameters/disable_esco
chown system system /sys/kernel/ipv4/tcp_wmem_min
chown system system /sys/kernel/ipv4/tcp_wmem_def
chown system system /sys/kernel/ipv4/tcp_wmem_max
chown system system /sys/kernel/ipv4/tcp_rmem_min
chown system system /sys/kernel/ipv4/tcp_rmem_def
chown system system /sys/kernel/ipv4/tcp_rmem_max
chown root radio /proc/cmdline
# Define TCP buffer sizes for various networks
# ReadMin, ReadInitial, ReadMax, WriteMin, WriteInitial, WriteMax,
setprop net.tcp.buffersize.default 4096,87380,704512,4096,16384,110208
setprop net.tcp.buffersize.wifi 524288,1048576,2097152,262144,524288,1048576
setprop net.tcp.buffersize.lte 4096,87380,1220608,4096,16384,563200
setprop net.tcp.buffersize.umts 4096,87380,563200,4096,16384,110208
setprop net.tcp.buffersize.hspa 4096,87380,704512,4096,16384,110208
setprop net.tcp.buffersize.hsupa 4096,87380,704512,4096,16384,262144
setprop net.tcp.buffersize.hsdpa 4096,87380,704512,4096,16384,262144
setprop net.tcp.buffersize.hspap 4096,87380,1220608,4096,16384,393216
setprop net.tcp.buffersize.edge 4096,26280,35040,4096,16384,35040
setprop net.tcp.buffersize.gprs 4096,8760,11680,4096,8760,11680
setprop net.tcp.buffersize.evdo 4096,87380,563200,4096,16384,262144
setprop net.tcp.buffersize.evdo_b 4096,87380,704512,4096,16384,262144
# Set this property so surfaceflinger is not started by system_init
setprop system_init.startsurfaceflinger 0
# Run sysinit
exec /system/bin/sysinit
class_start core
class_start main
on nonencrypted
class_start late_start
on charger
class_start charger
on property:vold.decrypt=trigger_reset_main
class_reset main
on property:vold.decrypt=trigger_load_persist_props
load_persist_props
on property:vold.decrypt=trigger_post_fs_data
trigger post-fs-data
on property:vold.decrypt=trigger_restart_min_framework
class_start main
on property:vold.decrypt=trigger_restart_framework
class_start main
class_start late_start
on property:vold.decrypt=trigger_shutdown_framework
class_reset late_start
class_reset main
## Daemon processes to be run by init.
##
service ueventd /sbin/ueventd
class core
critical
service console /system/bin/sh
class core
console
disabled
user shell
group log
on property:ro.debuggable=1
start console
# adbd is controlled via property triggers in init.<platform>.usb.rc
service adbd /sbin/adbd
class core
disabled
# adbd on at boot in emulator
on property:ro.kernel.qemu=1
start adbd
service servicemanager /system/bin/servicemanager
class core
user system
group system
critical
onrestart restart zygote
onrestart restart media
onrestart restart surfaceflinger
onrestart restart drm
service vold /system/bin/vold
class core
socket vold stream 0660 root mount
ioprio be 2
service netd /system/bin/netd
class main
socket netd stream 0660 root system
socket dnsproxyd stream 0660 root inet
socket mdns stream 0660 root system
service debuggerd /system/bin/debuggerd
class main
service ril-daemon /system/bin/rild
class main
socket rild stream 660 root radio
socket rild-debug stream 660 radio system
user root
group radio cache inet misc audio sdcard_r sdcard_rw qcom_oncrpc qcom_diag log
service surfaceflinger /system/bin/surfaceflinger
class main
user system
group graphics
onrestart restart zygote
service zygote /system/bin/app_process -Xzygote /system/bin --zygote --start-system-server
class main
socket zygote stream 660 root system
onrestart write /sys/android_power/request_state wake
onrestart write /sys/power/state on
onrestart restart media
onrestart restart netd
service drm /system/bin/drmserver
class main
user drm
group drm system inet drmrpc sdcard_r
service media /system/bin/mediaserver
class main
user media
group audio camera inet net_bt net_bt_admin net_bw_acct drmrpc qcom_diag
ioprio rt 4
service bootanim /system/bin/bootanimation
class main
user graphics
group graphics
disabled
oneshot
service dbus /system/bin/dbus-daemon --system --nofork
class main
socket dbus stream 660 bluetooth bluetooth
user bluetooth
group bluetooth net_bt_admin
service bluetoothd /system/bin/bluetoothd -n
class main
socket bluetooth stream 660 bluetooth bluetooth
socket dbus_bluetooth stream 660 bluetooth bluetooth
# init.rc does not yet support applying capabilities, so run as root and
# let bluetoothd drop uid to bluetooth with the right linux capabilities
group bluetooth net_bt_admin misc
disabled
service installd /system/bin/installd
class main
socket installd stream 600 system system
service racoon /system/bin/racoon
class main
socket racoon stream 600 system system
# IKE uses UDP port 500. Racoon will setuid to vpn after binding the port.
group vpn net_admin inet
disabled
oneshot
service mtpd /system/bin/mtpd
class main
socket mtpd stream 600 system system
user vpn
group vpn net_admin inet net_raw
disabled
oneshot
service keystore /system/bin/keystore /data/misc/keystore
class main
user keystore
group keystore drmrpc
socket keystore stream 666
service dumpstate /system/bin/dumpstate -s
class main
socket dumpstate stream 0660 shell log
disabled
oneshot
service sshd /system/bin/start-ssh
class main
disabled
service mdnsd /system/bin/mdnsd
class main
user mdnsr
group inet net_raw
socket mdnsd stream 0660 mdnsr inet
disabled
oneshot
When I mount mmcblkp02 as /data "overwriting" existing one, there was much more free space in "storage" and in built-in application manager (bar at bottom of the screen), but most of apps crashes, or moment after that phone reboots.
Code:
mount -t ext2 -o rw,nosuid,nodev /dev/block/mmcblk0p2 /data
Also when I cd /data I was only seeing data from sd, and there wasn't data from internal memory. I try to copy internal data to sd cp /data/* /cache/jarek [jarek=mmcblk0p2 mount point]. but it still doesn't work after manual mount.
I read some posts and it's appear that I must change init.rc, which is overwrite on every shutdown, so to do that I need unpack recovery (boot.img), edit and repack, then upload. But than what? Probably there will problem with app's data that was in internal storage... ?
Questions:
1. is there any ready for use ROM with this feature?
2. is someone do something like this? is this work?
3. maybe it can't work and I shouldn't lose few more days on it, so tell me why? (technically only, I know I can just go buy new phone)
4. maybe I can extend existing /data with mmcblk0p2 instead swap this?
Jarek