Database Develop

Rooting the 7320

So I have a 7320 but there is no root for it...
Someone has knowledge on how to root devices from scratch...
Can someone point me in the right direction on how to go through the process of getting this sucker rooted?
While im not the most nix savvy, I know enough to get by. Happy to experiment on mine, as long as its not going to brick it
Even a decent blog post on how to try and do it would do me
Bout time I learnt a bit more about the workings of these, kinda been ignoring it since the old winmo 6.5x days

Do you have a stock firmware file?
Sent from my SAMSUNG-SGH-I727 using xda premium

Samfirmware release it just a moment ago..
And I post the link to development section..
http://forum.xda-developers.com/showthread.php?p=23429136#post23429136

Do you know adb at all? I would be interested in your partition layout. Do you have an external sd? Is the 7320 the exact same internals as the i957?
Sent from my SAMSUNG-SGH-I727 using xda premium

Here's some info from a GT-P7320 available in Poland.
Firmware: P7320XXLA3_POLKL3_XEO_Poland_Android_3.2
Not sure if this is what you need... Anyway, from what I read, rooting 7320 with the i957 method resulted in the internal memory not being accessible any more.
Code:
$ [B]df[/B]
Filesystem Size Used Free Blksize
/dev 374M 76K 374M 4096
/mnt/asec 374M 0K 374M 4096
/mnt/obb 374M 0K 374M 4096
/system 1G 664M 419M 4096
/data 11G 4G 7G 4096
/cache 412M 6M 405M 4096
/efs 9M 2M 7M 2048
/firmware 199M 21M 178M 4096
/system/etc/firmware/misc_mdm 199M 26M 173M 4096
/tombstones 126M 4M 122M 4096
/mnt/sdcard 11G 4G 7G 4096
Code:
$ [B]mount[/B]
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/mmcblk0p24 /system ext4 ro,relatime,barrier=0,data=ordered 0 0
/dev/block/mmcblk0p28 /data ext4 rw,nosuid,nodev,relatime,barrier=1,data=ordered,noauto_da_alloc 0 0
/dev/block/mmcblk0p25 /cache ext4 rw,nosuid,nodev,relatime,barrier=1,data=ordered 0 0
/dev/block/mmcblk0p21 /efs ext4 rw,nosuid,nodev,relatime,barrier=1,data=ordered 0 0
/dev/block/mmcblk0p13 /firmware vfat ro,relatime,fmask=0000,dmask=0000,allow_utime=0022,codepage=cp437,iocharset=iso8859-1,shortname=lower,errors=remount-ro 0 0
/dev/block/mmcblk0p17 /system/etc/firmware/misc_mdm vfat ro,relatime,fmask=0000,dmask=0000,allow_utime=0022,codepage=cp437,iocharset=iso8859-1,shortname=lower,errors=remount-ro 0 0
/dev/block/mmcblk0p26 /tombstones ext4 rw,nosuid,nodev,relatime,barrier=1,data=ordered 0 0
/dev/fuse /mnt/sdcard fuse rw,nosuid,nodev,relatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
Code:
$ [B]cat /proc/cpuinfo[/B]
Processor : ARMv7 Processor rev 2 (v7l)
processor : 0
BogoMIPS : 13.53
Features : swp half thumb fastmult vfp edsp neon vfpv3
CPU implementer : 0x51
CPU architecture: 7
CPU variant : 0x0
CPU part : 0x02d
CPU revision : 2
Hardware : Samsung P5 LTE
Revision : 0007
Serial : 4d121db41dfebe5e

looking at your code real quick, there are some differences:
/data
i957: mmcblk0p26
7320: mmcblk0p28
/tombstones
i957: mmcblk0p27
7320: mmcblk0p26
cpu info is the same
so, what this means is that CWM wont work because your data partition is different.
da_g's kernel also wont work because your data partition is different. honestly, i dont know what the tombstones partition is. i found this, but anyway:
Tombstone – When a file is copied it will land into the data partition on your primary drive, and over time it will be moved out to make space for new files. After being moved out a special pointer ("tombstone") is created in the data partition, pointing to the actual file in the storage pool.​
I dont remember what 3e recovery looks like. i dont think there is an install zip from sd card option is there? the second option is 'install update.zip', correct?
If so, I don't see why you couldnt flash the skyrocket update.zip via recovery. this is the update script it uses.
Code:
ui_print("***********************************************");
ui_print(" Superuser 3.0.5 for Android 2.0-3.2");
ui_print("***********************************************");
show_progress(1.000000, 0);
ui_print(" Mounting SYSTEM...");
run_program("/sbin/busybox", "mount", "/system");
set_progress(0.100000);
ui_print(" Deleting SYSTEM:bin/su...");
delete("/system/bin/su");
set_progress(0.200000);
ui_print(" Deleting SYSTEM:xbin/su...");
delete("/system/xbin/su");
set_progress(0.300000);
ui_print(" Extracting files to SYSTEM...");
package_extract_dir("system", "/system");
set_progress(0.400000);
ui_print(" Setting SYSTEM:bin/su permissions to 06755...");
set_perm(0, 0, 06755, "/system/bin/su");
set_progress(0.500000);
ui_print(" Creating SYSTEM:xbin/su symbolic link...");
symlink("/system/bin/su", "/system/xbin/su");
set_progress(0.600000);
ui_print(" Unmounting SYSTEM...");
unmount("/system");
set_progress(0.900000);
ui_print("Install complete. Enjoy!");
set_progress(1.000000);
If the device has the same internals, then the update binary should work as well. as far as i can tell, the only difference is the data and tombstones partitions.

so we basically just need recovery.fstab from the SGHI957 CWM changed to the following and compiled..
#/tmp ramdisk
/boot emmc /dev/block/mmcblk0p8
/cache ext4 /dev/block/mmcblk0p25
/data ext4 /dev/block/mmcblk0p28 <-- 7320
#/misc mtd misc
/recovery emmc /dev/block/mmcblk0p22
#/sdcard vfat /dev/block/mmcblk0p28 /dev/block/mmcblk0
/system ext4 /dev/block/mmcblk0p24
/efs ext4 /dev/block/mmcblk0p21
this should let CWM then see our Data partition and at least be able to backup the onboard rom..
Maybe one of the devs could compile this for us to test.

stripeyhorse said:
so we basically just need recovery.fstab from the SGHI957 CWM changed to the following and compiled..
#/tmp ramdisk
/boot emmc /dev/block/mmcblk0p8
/cache ext4 /dev/block/mmcblk0p25
/data ext4 /dev/block/mmcblk0p28 <-- 7320
#/misc mtd misc
/recovery emmc /dev/block/mmcblk0p22
#/sdcard vfat /dev/block/mmcblk0p28 /dev/block/mmcblk0
/system ext4 /dev/block/mmcblk0p24
/efs ext4 /dev/block/mmcblk0p21
this should let CWM then see our Data partition and at least be able to backup the onboard rom..
Maybe one of the devs could compile this for us to test.
Click to expand...
Click to collapse
utkanos is the one who made it for us. maybe he can help you out.

I've got an IT background, more on the infrastructure side than development, but if there's anything I can do to assist this process then please let me know.
Tim

I Got This partition from /system/etc/recovery_mmc.fstab
Code:
# mount point fstype device [device2]
/boot emmc /dev/block/mmcblk0p8
/efs ext4 /dev/block/mmcblk0p21
/cache ext4 /dev/block/mmcblk0p25
/data ext4 /dev/block/mmcblk0p28 length=-16384
/misc mtd misc
/recovery emmc /dev/block/mmcblk0p22
/sdcard vfat /dev/block/mmcblk0p26 /dev/block/mmcblk0
/system ext4 /dev/block/mmcblk0p24
/preload ext4 /dev/block/mmcblk0p27
And this is from /system/etc/recovery.fstab
Code:
# mount point fstype device [device2]
/boot emmc /dev/block/mmcblk0p8
/efs ext4 /dev/block/mmcblk0p21
/cache ext4 /dev/block/mmcblk0p25
/data ext4 /dev/block/mmcblk0p26 length=-16384
/misc mtd misc
/recovery emmc /dev/block/mmcblk0p22
/sdcard vfat /dev/block/mmcblk0p28 /dev/block/mmcblk0
/system ext4 /dev/block/mmcblk0p24
Build prop
Code:
# begin build properties
# autogenerated by buildinfo.sh
ro.build.id=MASTER
ro.build.display.id=MASTER.DVLB2
ro.build.version.incremental=DVLB2
ro.build.version.sdk=13
ro.build.version.codename=REL
ro.build.version.release=3.2
ro.build.date=Thu Feb 9 22:56:48 KST 2012
ro.build.date.utc=1328795808
ro.build.type=user
ro.build.user=dpi
ro.build.host=DELL152
ro.build.tags=release-keys
ro.product.model=GT-P7320T
ro.product.brand=samsung
ro.product.name=GT-P7320T
ro.product.device=GT-P7320T
ro.product.board=MSM8660_SURF
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=msm8660
# ro.build.product is obsolete; use ro.product.device
ro.build.product=GT-P7320T
# Do not try to parse ro.build.description or .fingerprint
ro.build.description=GT-P7320T-user 3.2 MASTER DVLB2 release-keys
ro.build.fingerprint=samsung/GT-P7320T/GT-P7320T:3.2/MASTER/DVLB2:user/release-keys
ro.build.characteristics=tablet,nosdcard
# Samsung Specific Properties
ro.build.PDA=P7320TDVLB2
ro.build.hidden_ver=P7320TDVLB2
ro.build.changelist=627588
ro.build.buildtag=
# end build properties
#
# system.prop for surf
#
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.composition.type=dyn
debug.overlayui.enable=0
# 64MB dalvik heap size is gingerbread default, cannot be used here, refer to frameworks/base/build/tablet-dalvik-heap.mk
# dalvik.vm.heapsize=64m
dev.pm.dyn_samplingrate=1
#
# system props for the cne module
#
persist.cne.UseCne=vendor
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
ro.hdmi.enable=true
lpa.decode=true
#system props for the MM modules
media.stagefright.enable-player=true
media.stagefright.enable-http=true
media.stagefright.enable-fma2dp=true
media.enable-commonsource=true
#
# system props for the data modules
#
ro.use_data_netmgrd=true
#
# system props for SD card emulation of emmc partition
#
ro.emmc.sdcard.partition=28
#system props for time-services
persist.timed.enable=true
# System props for audio
persist.audio.fluence.mode=endfire
persist.audio.vr.enable=false
#
# system prop for opengles version
#
# 131072 is decimal for 0x20000 to report version 2
ro.opengles.version=131072
#
# system prop for Bluetooth Dialup Networking
#
# ro.qualcomm.bluetooth.dun=true
#
# system prop for Bluetooth Auto connect for remote initated connections
#
# ro.bluetooth.remote.autoconnect=true
#
# system prop for Bluetooth FTP profile
#
# ro.qualcomm.bluetooth.ftp=true
#
# system prop for sending power off request to RIL during phone shutdown
#
ro.ril.shutdown=true
# Samsung Tvout Service
ro.sectvout.enable=1
#
# system prop for Keyguard
#
keyguard.no_require_sim=yes
#Samung HWLCD Rotation
ro.sf.hwrotation=90
# system prop for forced Camera Shutter
ro.camera.sound.forced=1
# System property for SIM
persist.radio.apm_sim_not_pwdn=1
# System property for SMS
# persist.radio.sms_sync_sending=1
ro.vendor.extension_library=/system/lib/libqc-opt.so
#
# User Agent Profile for RTSP Streaming
#
net.streaming.rtsp.uaprof=http://wap.samsungmobile.com/uaprof/GT-P7320T.xml
#
# ADDITIONAL_BUILD_PROPERTIES
#
ro.config.ringtone=S_Over_the_horizon.ogg
ro.config.notification_sound=S_Sherbet.ogg
ro.config.alarm_alert=Good_Morning.ogg
dev.sfbootcomplete=0
drm.service.enabled=true
ro.secdevenc=true
dalvik.vm.heapstartsize=5m
dalvik.vm.heapgrowthlimit=64m
dalvik.vm.heapsize=288m
ro.setupwizard.mode=OPTIONAL
ro.setupwizard.enterprise_mode=1
ro.url.legal=http://www.google.com/intl/%s/mobile/android/basic/phone-legal.html
ro.url.legal.android_privacy=http://www.google.com/intl/%s/mobile/android/basic/privacy.html
ro.error.receiver.system.apps=com.google.android.feedback
ro.com.google.clientidbase=android-samsung
ro.com.google.gmsversion=3.2_r6
ro.error.receiver.default=com.samsung.receiver.error
dalvik.vm.dexopt-flags=m=y
net.bt.name=Android
dalvik.vm.stack-trace-file=/data/anr/traces.txt

new to samsung devices...
working on a rooted system image.....
su works =)
but there are some issues to be solved. =(.... I have trouble creating a working image..... adb access works, but system doesnt boot up fully......
will report any progress.

ok. time to ask for help..
Anyone want to give me tips on how to compile the CWM... with our slight changes..
im sure the kernel for the US version would also work if we pointed the data directory to the right place...
Im willing to donate for a compiled CWM for the 7320.....

if you are familiar with mirc you can join #utkanos on freenode

stripeyhorse said:
ok. time to ask for help..
Anyone want to give me tips on how to compile the CWM... with our slight changes..
im sure the kernel for the US version would also work if we pointed the data directory to the right place...
Im willing to donate for a compiled CWM for the 7320.....
Click to expand...
Click to collapse
Definitely don't have the skills myself, but yeah, am happy to donate some $$ if it will help.
Tim

I've created a rooted system.img based on the firmware [gt-p7320-telstra]p7320tdvlb2-australia from suwandiapr.
Works perfectly on my GT-P730T.
I've only added su binary to /system/bin/ and Superuser.apk (both taken from Chainfire's Superuser-3.0.7-efghi-signed.zip).
You can flash it with Odin3 1.85 without increasing your "custom download" counter. You leave the options as they are (auto reboot and reset timer checked, EVERYTHING ELSE IS UNCHECKED). click on "PDA" and choose 7320T_system_root.tar.md5. happy flashing...
Also reflashing the stock image does not increase the counter.
Busybox is not installed - you can download it from the market afterwards. (Busybox Installer Free from Stericson worked for me.)
One thing: I had problems downloading from the Market. Removing my google account and adding it again, followed by a restart solved it for me. (Settings->Accounts and sync->click on your google account->"remove account" and add it again.
And another thing: you will have a changed bootanimation (Samsung original). Do not know why yet.
you can find the image here, but this is more a development release, so only do it if you know what you are doing here......
http : / / hotfile.com/dl/149432015/0f6e58b/7320T_system_root.zip.001.html
http : / / hotfile.com/dl/149432188/4e7a77e/7320T_system_root.zip.002.html
(not allowed to post links yet... maybe someone can post it in the dev section for this rom...)
cheers,
glitschi

Wow things moved fast in a few days :O Thanks glitschi667, I'm downloading the system.img stuff now, will take awhile to test though :S
Just for reference:
Build.prop
Code:
# begin build properties
# autogenerated by buildinfo.sh
ro.build.id=MASTER
ro.build.display.id=MASTER.DVLB2
ro.build.version.incremental=DVLB2
ro.build.version.sdk=13
ro.build.version.codename=REL
ro.build.version.release=3.2
ro.build.date=Thu Feb 9 22:56:48 KST 2012
ro.build.date.utc=1328795808
ro.build.type=user
ro.build.user=dpi
ro.build.host=DELL152
ro.build.tags=release-keys
ro.product.model=GT-P7320T
ro.product.brand=samsung
ro.product.name=GT-P7320T
ro.product.device=GT-P7320T
ro.product.board=MSM8660_SURF
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=msm8660
# ro.build.product is obsolete; use ro.product.device
ro.build.product=GT-P7320T
# Do not try to parse ro.build.description or .fingerprint
ro.build.description=GT-P7320T-user 3.2 MASTER DVLB2 release-keys
ro.build.fingerprint=samsung/GT-P7320T/GT-P7320T:3.2/MASTER/DVLB2:user/release-keys
ro.build.characteristics=tablet,nosdcard
# Samsung Specific Properties
ro.build.PDA=P7320TDVLB2
ro.build.hidden_ver=P7320TDVLB2
ro.build.changelist=627588
ro.build.buildtag=
# end build properties
#
# system.prop for surf
#
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.composition.type=dyn
debug.overlayui.enable=0
# 64MB dalvik heap size is gingerbread default, cannot be used here, refer to frameworks/base/build/tablet-dalvik-heap.mk
# dalvik.vm.heapsize=64m
dev.pm.dyn_samplingrate=1
#
# system props for the cne module
#
persist.cne.UseCne=vendor
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
ro.hdmi.enable=true
lpa.decode=true
#system props for the MM modules
media.stagefright.enable-player=true
media.stagefright.enable-http=true
media.stagefright.enable-fma2dp=true
media.enable-commonsource=true
#
# system props for the data modules
#
ro.use_data_netmgrd=true
#
# system props for SD card emulation of emmc partition
#
ro.emmc.sdcard.partition=28
#system props for time-services
persist.timed.enable=true
# System props for audio
persist.audio.fluence.mode=endfire
persist.audio.vr.enable=false
#
# system prop for opengles version
#
# 131072 is decimal for 0x20000 to report version 2
ro.opengles.version=131072
#
# system prop for Bluetooth Dialup Networking
#
# ro.qualcomm.bluetooth.dun=true
#
# system prop for Bluetooth Auto connect for remote initated connections
#
# ro.bluetooth.remote.autoconnect=true
#
# system prop for Bluetooth FTP profile
#
# ro.qualcomm.bluetooth.ftp=true
#
# system prop for sending power off request to RIL during phone shutdown
#
ro.ril.shutdown=true
# Samsung Tvout Service
ro.sectvout.enable=1
#
# system prop for Keyguard
#
keyguard.no_require_sim=yes
#Samung HWLCD Rotation
ro.sf.hwrotation=90
# system prop for forced Camera Shutter
ro.camera.sound.forced=1
# System property for SIM
persist.radio.apm_sim_not_pwdn=1
# System property for SMS
# persist.radio.sms_sync_sending=1
ro.vendor.extension_library=/system/lib/libqc-opt.so
#
# User Agent Profile for RTSP Streaming
#
net.streaming.rtsp.uaprof=http://wap.samsungmobile.com/uaprof/GT-P7320T.xml
#
# ADDITIONAL_BUILD_PROPERTIES
#
ro.config.ringtone=S_Over_the_horizon.ogg
ro.config.notification_sound=S_Sherbet.ogg
ro.config.alarm_alert=Good_Morning.ogg
dev.sfbootcomplete=0
drm.service.enabled=true
ro.secdevenc=true
dalvik.vm.heapstartsize=5m
dalvik.vm.heapgrowthlimit=64m
dalvik.vm.heapsize=288m
ro.setupwizard.mode=OPTIONAL
ro.setupwizard.enterprise_mode=1
ro.url.legal=http://www.google.com/intl/%s/mobile/android/basic/phone-legal.html
ro.url.legal.android_privacy=http://www.google.com/intl/%s/mobile/android/basic/privacy.html
ro.error.receiver.system.apps=com.google.android.feedback
ro.com.google.clientidbase=android-samsung
ro.com.google.gmsversion=3.2_r6
ro.error.receiver.default=com.samsung.receiver.error
dalvik.vm.dexopt-flags=m=y
net.bt.name=Android
dalvik.vm.stack-trace-file=/data/anr/traces.txt
Cpu info
Code:
Processor : ARMv7 Processor rev 2 (v7l)
processor : 0
BogoMIPS : 13.54
Features : swp half thumb fastmult vfp edsp neon vfpv3
CPU implementer : 0x51
CPU architecture: 7
CPU variant : 0x0
CPU part : 0x02d
CPU revision : 2
Hardware : Samsung P5 LTE
Revision : 0008
Serial : 4d1258e67a4dbed2
df
Code:
Filesystem Size Used Free Blksize
/dev 374M 76K 374M 4096
/mnt/asec 374M 0K 374M 4096
/mnt/obb 374M 0K 374M 4096
/system 1G 692M 392M 4096
/data 11G 867M 10G 4096
/cache 412M 6M 405M 4096
/efs 9M 2M 7M 2048
/firmware 199M 21M 178M 4096
/system/etc/firmware/misc_mdm 199M 26M 173M 4096
/tombstones 126M 4M 122M 4096
/mnt/sdcard 11G 867M 10G 4096
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/mmcblk0p24 /system ext4 ro,relatime,barrier=0,data=ordered 0 0
/dev/block/mmcblk0p28 /data ext4 rw,nosuid,nodev,relatime,barrier=1,data=ordered,noauto_da_alloc 0 0
/dev/block/mmcblk0p25 /cache ext4 rw,nosuid,nodev,relatime,barrier=1,data=ordered 0 0
/dev/block/mmcblk0p21 /efs ext4 rw,nosuid,nodev,relatime,barrier=1,data=ordered 0 0
/dev/block/mmcblk0p13 /firmware vfat ro,relatime,fmask=0000,dmask=0000,allow_utime=0022,codepage=cp437,iocharset=iso8859-1,shortname=lower,errors=remount-ro 0 0
/dev/block/mmcblk0p17 /system/etc/firmware/misc_mdm vfat ro,relatime,fmask=0000,dmask=0000,allow_utime=0022,codepage=cp437,iocharset=iso8859-1,shortname=lower,errors=remount-ro 0 0
/dev/block/mmcblk0p26 /tombstones ext4 rw,nosuid,nodev,relatime,barrier=1,data=ordered 0 0
/dev/fuse /mnt/sdcard fuse rw,nosuid,nodev,relatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
recovery.fstab
Code:
# mount point fstype device [device2]
/boot emmc /dev/block/mmcblk0p8
/efs ext4 /dev/block/mmcblk0p21
/cache ext4 /dev/block/mmcblk0p25
/data ext4 /dev/block/mmcblk0p26 length=-16384
/misc mtd misc
/recovery emmc /dev/block/mmcblk0p22
/sdcard vfat /dev/block/mmcblk0p28 /dev/block/mmcblk0
/system ext4 /dev/block/mmcblk0p24
recovery_mmc.fstab
Code:
# mount point fstype device [device2]
/boot emmc /dev/block/mmcblk0p8
/efs ext4 /dev/block/mmcblk0p21
/cache ext4 /dev/block/mmcblk0p25
/data ext4 /dev/block/mmcblk0p28 length=-16384
/misc mtd misc
/recovery emmc /dev/block/mmcblk0p22
/sdcard vfat /dev/block/mmcblk0p26 /dev/block/mmcblk0
/system ext4 /dev/block/mmcblk0p24
/preload ext4 /dev/block/mmcblk0p27

Before I do something silly.. thought I'd double check....
Opened up the root_original.zip from http://forum.xda-developers.com/showthread.php?t=1287205
In the META-INF\com\google\android folder is a file called updater-script that looks like
Code:
mount("ext4", "EMMC", "/dev/block/mmcblk0p4", "/system");
package_extract_dir("system", "/system");
ui_print("ÉÉÉÉÉÉÉÉÉÉÉÉÉÉÉÉÉÉÉÉÉ");
ui_print("Credit to @_mrbirdman_ @Drod2169");
ui_print(" @Rainabba & @b16a2smith");
ui_print("ÉÉÉÉÉÉÉÉÉÉÉÉÉÉÉÉÉÉÉÉÉ");
ui_print("I only have one speed:");
ui_print("ÉÉÉÉÉÉÉÉÉÉÉÉÉÉÉÉÉÉÉÉÉ");
ui_print("ÉÉÉÉÉÉÉÉÉÉÉÉÉÉÉÉÉÉÉÉÉ");
ui_print(" GGGGGGG OOOOOO !!");
ui_print("G G O O !!");
ui_print("G O O !!");
ui_print("G GGG O O !!");
ui_print("G G O O ");
ui_print(" GGGGGG OOOOOO !!");
set_perm(0, 0, 6755, "/system/bin/su");
unmount("/system");
Would changing
Code:
mount("ext4", "EMMC", "/dev/block/mmcblk0p4", "/system");
to
Code:
mount("ext4", "EMMC", "/dev/block/mmcblk0p24", "/system");
Not do what we are after?
Only reason why I haven't just gone off and run it already is the update-binary files that is in there as well. Not sure what that does?

I've tried installing Chainfire's Superuser-3.0.7-efghi-signed.zip via recovery some days ago. output was "installation aborted. signature check failed" or something.
Would be interesting to know if this file works.... and if it does... why!? =)..and if its really signed, changing it would break it.... most probably..... and isn't system already mounted because of recovery.fstab?
I think we need cwm recovery.... started working on this yesterday but have several problems to fix before I can start a first try....
If you want I can try to install the zip file tomorrow. I have mine opened up, so I'm not so afraid of experiments... =)
edit: update-binary shouldn't be a problem..... it only executes the script... says the internet.....

glitschi667 said:
I've tried installing Chainfire's Superuser-3.0.7-efghi-signed.zip via recovery some days ago. output was "installation aborted. signature check failed" or something.
Would be interesting to know if this file works.... and if it does... why!? =)..and if its really signed, changing it would break it.... most probably..... and isn't system already mounted because of recovery.fstab?
I think we need cwm recovery.... started working on this yesterday but have several problems to fix before I can start a first try....
If you want I can try to install the zip file tomorrow. I have mine opened up, so I'm not so afraid of experiments... =)
edit: update-binary shouldn't be a problem..... it only executes the script... says the internet.....
Click to expand...
Click to collapse
According to this article: http://fokke.org/site/content/howto-create-android-updatezip-package
You can resign the package using java...
When you say "I have mine opened up" what do you mean? Are you talking about the System.img thing you created?

I know about the possibility to sign things, but I think the problem is the "key" you use to sign something....
the superuser.zip I tried was also signed. but maybe I do not understand the process correctly...
with "opened up" I meant my P7320T... look for "galaxy tab 8.9 disassemble". just removed the back and disconnected the battery...
flashed the wrong kernel.....

[Q] What the hell is going on? (SOLVED)

I'm trying to load a new CM ROM but I keep getting an abortion message. Here's the log. Can anyone tell me what I'm doing wrong? I'm using rom manager with clockwork.
Starting recovery on Thu May 31 12:03:15 2012
can't open /dev/tty0: No such file or directory
framebuffer: fd 3 (480 x 800)
ClockworkMod Recovery v5.0.2.0
recovery filesystem table
=========================
0 /tmp ramdisk (null) (null)
1 /boot mtd boot (null)
2 /cache yaffs2 cache (null)
3 /data yaffs2 userdata (null)
4 /misc mtd misc (null)
5 /recovery mtd recovery (null)
6 /sdcard vfat /dev/block/mmcblk0p1 /dev/block/mmcblk0
7 /system yaffs2 system (null)
8 /sd-ext ext4 /dev/block/mmcblk0p2 (null)
I:Completed outputting fstab.
Irocessing arguments.
Fixing execute permissions for /cache
mtd: successfully wrote block at 0
I:Set boot command "boot-recovery"
I:Checking arguments.
I:device_recovery_start()
Command: "/sbin/recovery"
ro.secure=0
ro.allow.mock.location=1
ro.debuggable=1
persist.service.adb.enable=1
ro.build.id=GRJ22
ro.build.display.id=GRJ90
ro.build.version.incremental=eng.koush.20110905.103150
ro.build.version.sdk=10
ro.build.version.codename=REL
ro.build.version.release=2.3.5
ro.build.date=Mon Sep 5 10:32:20 PDT 2011
ro.build.date.utc=0
ro.build.type=eng
ro.build.user=koush
ro.build.host=Koushik-Lion.local
ro.build.tags=test-keys
ro.product.model=Nexus One
ro.product.brand=google
ro.product.name=passion
ro.product.device=passion
ro.product.board=mahimahi
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.manufacturer=HTC
ro.product.locale.language=en
ro.product.locale.region=US
ro.wifi.channels=
ro.board.platform=qsd8k
ro.build.product=passion
ro.build.description=passion-user 2.3.4 GRJ22 121341 release-keys
ro.build.fingerprint=google/passion/passion:2.3.4/GRJ22/121341:user/release-keys
keyguard.no_require_sim=true
ro.sf.lcd_density=240
rild.libpath=/system/lib/libhtc_ril.so
wifi.interface=eth0
wifi.supplicant_scan_interval=15
ro.ril.hsxpa=2
ro.ril.gprsclass=10
ro.telephony.default_network=0
ro.opengles.version=131072
dalvik.vm.heapsize=32m
media.a1026.nsForVoiceRec=0
media.a1026.enableA1026=1
ro.rommanager.developerid=cyanogenmod
ro.url.legal=http://www.google.com/intl/%s/mobile/android/basic/phone-legal.html
ro.url.legal.android_privacy=http://www.google.com/intl/%s/mobile/android/basic/privacy.html
ro.com.google.clientidbase=android-google
ro.com.android.wifi-watchlist=GoogleGuest
ro.setupwizard.enterprise_mode=1
ro.com.android.dateformat=MM-dd-yyyy
ro.com.android.dataroaming=false
ro.config.ringtone=Playa.ogg
ro.config.notification_sound=regulus.ogg
ro.config.alarm_alert=Alarm_Beep_03.ogg
ro.ril.enable.managed.roaming=1
ro.ril.oem.nosim.ecclist=911,112,999,000,08,118,120,122,110,119,995
ro.ril.emc.mode=2
ro.modversion=CyanogenMod-7.1.0-RC1-N1-KANG
ro.kernel.android.checkjni=1
ro.setupwizard.mode=OPTIONAL
dalvik.vm.dexopt-flags=m=y
net.bt.name=Android
net.change=net.bt.name
dalvik.vm.stack-trace-file=/data/anr/traces.txt
ro.factorytest=0
ro.serialno=HT0CJP801701
ro.bootmode=recovery
ro.baseband=5.08.00.04
ro.carrier=GOOGLE
ro.bootloader=0.35.0017
ro.hardware=mahimahi
ro.revision=132
init.svc.recovery=running
init.svc.adbd=running
I:Checking for extendedcommand...
I:Running extendedcommand...
Waiting for SD Card to mount (20s)
SD Card mounted...
Verifying SD Card marker...
f532ff99d0b616d54bd1fec6e4b345de
f532ff99d0b616d54bd1fec6e4b345de
I:Running script:
I:
ui_print("ROM Manager Version 5.0.0.7");
ui_print("May 31, 2012");
ui_print("Preparing to install ROM...");
run_program("/cache/dowipedalvikcache.sh");
format("/cache");
format("/data");
format("/sd-ext");
assert(install_zip("/sdcard/update-cm-7.2.0-RC3-p500-signed.zip"));
parse returned 0; 0 errors encountered
ROM Manager Version 5.0.0.7
May 31, 2012
Preparing to install ROM...
about to run program [/cache/dowipedalvikcache.sh] with 1 args
mount: mounting /dev/block/mtdblock4 on /cache failed: Device or resource busy
mount: mounting /dev/block/mmcblk0p2 on /sd-ext failed: No such file or directory
umount: can't umount /sd-ext: Invalid argument
run_program: child exited with status 1
Formatting /cache...
mtd: not erasing bad block at 0x01360000
mtd: not erasing bad block at 0x020e0000
mtd: not erasing bad block at 0x03600000
Formatting /data...
mtd: not erasing bad block at 0x00b00000
mtd: not erasing bad block at 0x02220000
mtd: not erasing bad block at 0x067e0000
mtd: not erasing bad block at 0x0af80000
mtd: not erasing bad block at 0x0b7e0000
Formatting /sd-ext...
Need size of filesystem
E:format_volume: make_extf4fs failed on /dev/block/mmcblk0p2
-- Installing: /sdcard/update-cm-7.2.0-RC3-p500-signed.zip
mtd: successfully wrote block at 0
I:Set boot command "boot-recovery"
Finding update package...
I:Update location: /sdcard/update-cm-7.2.0-RC3-p500-signed.zip
Opening update package...
Installing update...
script aborted: assert failed: getprop("ro.product.device") == "thunderg" || getprop("ro.build.product") == "thunderg" || getprop("ro.product.board") == "thunderg" ||
getprop("ro.product.device") == "p500" || getprop("ro.build.product") == "p500" || getprop("ro.product.board") == "p500"
assert failed: getprop("ro.product.device") == "thunderg" || getprop("ro.build.product") == "thunderg" || getprop("ro.product.board") == "thunderg" || getprop("ro.product.device") == "p500" || getprop("ro.build.product") == "p500" || getprop("ro.product.board") == "p500"
E:Error in /sdcard/update-cm-7.2.0-RC3-p500-signed.zip
(Status 7)
Installation aborted.
result was NULL, message is: assert failed: install_zip("/sdcard/update-cm-7.2.0-RC3-p500-signed.zip")

You're trying to install CM for Optimus One, not for Nexus One. No wonder it fails while checking the type of device.

That's the one I got right from CyanogenMod for my particular phone.

dieselfiend said:
That's the one I got right from CyanogenMod for my particular phone.
Click to expand...
Click to collapse
sometime it does that your best bet is use aroma 1st if that fails then use 4ext recovery

Hmm, what are you doing in Nexus One forums, asking questions about Optimus One?
In any case, your recovery (whatever it is) doesn't like the variables in your build.prop, of your current ROM. To force it to install, you can change updater-script to disable the assertion that fails, or change the build.prop for the assertion to pass.

Jack_R1 said:
Hmm, what are you doing in Nexus One forums, asking questions about Optimus One?
In any case, your recovery (whatever it is) doesn't like the variables in your build.prop, of your current ROM. To force it to install, you can change updater-script to disable the assertion that fails, or change the build.prop for the assertion to pass.
Click to expand...
Click to collapse
hahaha what he said

Man, I admire your knowledge level on this. Can you put in dummy terms?
Sent from my GT-I9100 using Tapatalk 2

I'll try to explain:
There is a file in your current ROM, as in any Android ROM. It's called build.prop, and it sits under /system, as in: /system/build.prop.
This file holds many variables' values, useful for Android boot-up and operation.
3 values interest you:
ro.product.device
ro.build.product
ro.product.board
"Assertion" = some part of the update script of the ROM that runs when you're trying to flash it. This part is checking the variables above, looking for specific values.
If assertion doesn't find the values it's looking for - it errors out and stops the update.
So, 2 ways to deal with it:
1) Change the file /system/build.prop, edit the values of those variables to something that won't trigger assertion failure.
2) Remove the assertion from the update script that is in your ROM.
Given that you have root, the first way should be easier. Just edit the values of those variables, find them in the file, add if some are missing (unlikely), and set all of them to "p500".

I got it to work. I was actually trying to install a ROM for another phone. I didn't realize that I clicked a link that was for a bunch of different phones rather than just mine. I downloaded the right ROM for my phone and all is well. It installed perfectly. Thanks for all the help!

Problem updating from one CyanogenMod nightly build to another.

Hi,
I'm currently running a nightly build of CyanogenMod 9 (9-20120618-NIGHTLY-p3) on my Galaxy Tab 10.1v, and I am trying to update to a newer build.
I've downloaded '9-29120712-NIGHTLY-p3' and saved the zip on my SD card. I reboot into clockwork mod recovery and, after clearing the cache, I try to apply the update zip. I also tried installing it using the ROM Manager, but it still fails. I don't understand why it won't work. Please help!!!!
This is log:
---------------
Starting recovery on Sun Jul 14 05:39:43 2019
framebuffer: fd 4 (1280 x 800)
ClockworkMod Recovery v5.8.3.1
recovery filesystem table
=========================
0 /tmp ramdisk (null) (null) 0
1 /efs ext4 /dev/block/mmcblk0p1 (null) 0
2 /recovery emmc /dev/block/mmcblk0p2 (null) 0
3 /boot emmc /dev/block/mmcblk0p3 (null) 0
4 /system ext4 /dev/block/mmcblk0p4 (null) 0
5 /cache ext4 /dev/block/mmcblk0p5 (null) 0
6 /data ext4 /dev/block/mmcblk0p8 (null) 0
7 /preload ext4 /dev/block/mmcblk0p10 (null) 0
W:Unable to get recovery.fstab info for /datadata during fstab generation!
W:Unable to get recovery.fstab info for /emmc during fstab generation!
W:Unable to get recovery.fstab info for /sdcard during fstab generation!
W:Unable to get recovery.fstab info for /sd-ext during fstab generation!
I:Completed outputting fstab.
Irocessing arguments.
I:Checking arguments.
I:device_recovery_start()
Command: "/sbin/recovery"
ro.secure=1
ro.allow.mock.location=0
ro.debuggable=1
persist.sys.usb.config=adb
ro.build.id=IMM76D
ro.build.display.id=IMM76D
ro.build.version.incremental=eng.koush.20120428.005633
ro.build.version.sdk=15
ro.build.version.codename=REL
ro.build.version.release=4.0.4
ro.build.date=Sat Apr 28 00:57:05 PDT 2012
ro.build.date.utc=0
ro.build.type=userdebug
ro.build.user=koush
ro.build.host=Koushik-Lion.local
ro.build.tags=test-keys
ro.product.model=GT-P7510
ro.product.brand=samsung
ro.product.name=GT-P7510
ro.product.device=p4wifi
ro.product.board=p3
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.manufacturer=samsung
ro.product.locale.language=en
ro.product.locale.region=US
ro.wifi.channels=
ro.board.platform=tegra
ro.build.product=p4wifi
ro.build.description=GT-P7510-user 3.2 HTJ85B UEKMM release-keys
ro.build.fingerprint=samsung/GT-P7510/GT-P7510:3.2/HTJ85B/UEKMM:user/release-keys
ro.build.characteristics=tablet,nosdcard
ro.cm.device=p4wifi
ro.opengles.version=131072
wifi.interface=eth0
rild.libpath=/system/lib/libsec-ril-apalone.so
rild.libargs=-d /dev/ttys0
keyguard.no_require_sim=true
ro.com.android.dateformat=MM-dd-yyyy
wifi.supplicant_scan_interval=15
dalvik.vm.heapstartsize=5m
dalvik.vm.heapgrowthlimit=48m
dalvik.vm.heapsize=256m
ro.rommanager.developerid=cyanogenmod
ro.url.legal=http://www.google.com/intl/%s/mobile/android/basic/phone-legal.html
ro.url.legal.android_privacy=http://www.google.com/intl/%s/mobile/android/basic/privacy.html
ro.com.google.clientidbase=android-google
ro.com.android.wifi-watchlist=GoogleGuest
ro.setupwizard.enterprise_mode=1
ro.com.android.dataroaming=false
ro.cm.version=9.0.0-RC0-p4wifi-UNOFFICIAL
ro.modversion=9.0.0-RC0-p4wifi-UNOFFICIAL
ro.config.ringtone=CyanTone.ogg
ro.config.notification_sound=CyanMessage.ogg
ro.config.alarm_alert=CyanAlarm.ogg
dalvik.vm.lockprof.threshold=500
dalvik.vm.dexopt-flags=m=y
net.bt.name=Android
net.change=net.bt.name
dalvik.vm.stack-trace-file=/data/anr/traces.txt
ro.factorytest=0
ro.serialno=2884143423F4557
ro.bootmode=unknown
ro.baseband=207_DB120215
ro.carrier=unknown
ro.bootloader=P7100BUKC8
ro.hardware=p3
ro.revision=14
ro.emmc=0
init.svc.recovery=running
init.svc.adbd=stopping
sys.usb.state=adb
service.adb.root=1
ro.cwm.prefer_tar=true
I:Checking for extendedcommand...
I:Running extendedcommand...
Waiting for SD Card to mount (20s)
I:using /data/media, no /sdcard found.
SD Card mounted...
Verifying SD Card marker...
a684e0f33ac9a63ea2f20f2798d687fa
I:Running script:
I:
ui_print("ROM Manager Version 5.0.0.8");
ui_print("July 13, 2012");
ui_print("Preparing to install ROM...");
run_program("/cache/dowipedalvikcache.sh");
assert(install_zip("/sdcard/Download/cm-9-20120712-NIGHTLY-p3.zip"));
parse returned 0; 0 errors encountered
ROM Manager Version 5.0.0.8
July 13, 2012
Preparing to install ROM...
about to run program [/cache/dowipedalvikcache.sh] with 1 args
mount: mounting /dev/block/mmcblk0p8 on /data failed: Device or resource busy
mount: mounting /dev/block/mmcblk0p5 on /cache failed: Device or resource busy
mount: can't find /sd-ext in /etc/fstab
umount: can't umount /sd-ext: Invalid argument
run_program: child exited with status 1
-- Installing: /sdcard/Download/cm-9-20120712-NIGHTLY-p3.zip
Finding update package...
I:Update location: /sdcard/Download/cm-9-20120712-NIGHTLY-p3.zip
I:using /data/media, no /sdcard found.
Opening update package...
Installing update...
script aborted: assert failed: getprop("ro.product.device") == "p3" || getprop("ro.build.product") == "p3"
assert failed: getprop("ro.product.device") == "p3" || getprop("ro.build.product") == "p3"
E:Error in /sdcard/Download/cm-9-20120712-NIGHTLY-p3.zip
(Status 7)
Installation aborted.
result was NULL, message is: assert failed: install_zip("/sdcard/Download/cm-9-20120712-NIGHTLY-p3.zip")
I:using /data/media, no /sdcard found.

OH YES! Don't worry, I figured it out. I needed to use the Recovery from here: http://droidbasement.com/db-blog/?p=2487, flashed with Odin.

use flash .zip from sdcard instead
BTW you can always flash it using the option "flash .zip from sdcard " insstead.It has never given me problems so far
p.s. I am a p4 user.

[Q] can't install cm9 errror [GT-I9000]

Hello ived tried countless times to try and get CM9 working on my Samsung Galaxy S (GT-I9000) With no success it used to work but isn't anymore and i dont know what the problem is.
Starting recovery on Sun Jan 6 19:21:24 2013
framebuffer: fd 4 (480 x 800)
CWM-based Recovery v6.0.1.2
recovery filesystem table
=========================
0 /tmp ramdisk (null) (null) 0
1 /recovery mtd recovery (null) 0
2 /boot mtd boot (null) 0
3 /radio mtd radio (null) 0
4 /system yaffs2 system (null) 0
5 /cache yaffs2 cache (null) 0
6 /datadata yaffs2 datadata (null) 0
7 /sdcard vfat /dev/block/mmcblk0p1 (null) 0
8 /data ext4 /dev/block/mmcblk0p2 (null) 0
9 /emmc vfat /dev/block/mmcblk1p1 (null) 0
W:Unable to get recovery.fstab info for /sd-ext during fstab generation!
I:Completed outputting fstab.
Irocessing arguments.
I:Checking arguments.
I:device_recovery_start()
Command: "/sbin/recovery"
ro.secure=1
ro.allow.mock.location=0
ro.debuggable=1
persist.sys.usb.config=mass_storage,adb
persist.sys.vold.switchexternal=1
ro.build.id=IMM76L
ro.build.display.id=cm_galaxysmtd-userdebug 4.0.4 IMM76L eng..20120828.152451 test-keys
ro.build.version.incremental=eng..20120828.152451
ro.build.version.sdk=15
ro.build.version.codename=REL
ro.build.version.release=4.0.4
ro.build.date=Tue Aug 28 15:25:08 PDT 2012
ro.build.date.utc=0
ro.build.type=userdebug
ro.build.user=
ro.build.host=cyanogenmod
ro.build.tags=test-keys
ro.product.model=GT-I9000
ro.product.brand=samsung
ro.product.name=GT-I9000
ro.product.device=GT-I9000
ro.product.board=aries
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.manufacturer=samsung
ro.product.locale.language=en
ro.product.locale.region=US
ro.wifi.channels=
ro.board.platform=s5pc110
ro.build.product=GT-I9000
ro.build.description=GT-I9000-user 2.3.5 GINGERBREAD XXJVT release-keys
ro.build.fingerprint=samsung/GT-I9000/GT-I9000:2.3.5/GINGERBREAD/XXJVT:user/release-keys
ro.build.characteristics=default
ro.cm.device=galaxysmtd
rild.libpath=/system/lib/libsec-ril.so
rild.libargs=-d /dev/ttyS0
ro.sf.lcd_density=240
ro.rommanager.developerid=cyanogenmod
keyguard.no_require_sim=true
ro.url.legal=
ro.url.legal.android_privacy=
ro.com.google.clientidbase=android-google
ro.com.android.wifi-watchlist=GoogleGuest
ro.setupwizard.enterprise_mode=1
ro.com.android.dateformat=MM-dd-yyyy
ro.com.android.dataroaming=false
ro.cm.version=9.1.0-galaxysmtd
ro.modversion=9.1.0-galaxysmtd
ro.config.ringtone=CyanTone.ogg
ro.config.notification_sound=CyanMessage.ogg
ro.config.alarm_alert=CyanAlarm.ogg
ro.opengles.version=131072
wifi.interface=wlan0
ro.telephony.ril_class=SamsungRIL
ro.telephony.ril.v3=icccardstatus,datacall,signalstrength,facilitylock
mobiledata.interfaces=pdp0,eth0,gprs,ppp0
ro.vold.switchablepair=/mnt/emmc,/mnt/sdcard
ro.com.google.locationfeatures=1
ro.com.google.networklocation=1
ro.kernel.android.checkjni=0
dalvik.vm.checkjni=false
ro.vold.umsdirtyratio=20
dalvik.vm.dexopt-data-only=1
dalvik.vm.heapstartsize=5m
dalvik.vm.heapgrowthlimit=48m
dalvik.vm.heapsize=128m
ro.ril.hsxpa=1
ro.ril.gprsclass=10
ro.adb.qemud=1
dalvik.vm.lockprof.threshold=500
dalvik.vm.dexopt-flags=m=y
net.bt.name=Android
net.change=net.tcp.buffersize.gprs
dalvik.vm.stack-trace-file=/data/anr/traces.txt
ro.factorytest=0
ro.serialno=383046E3BDDC00EC
ro.bootmode=unknown
ro.baseband=unknown
ro.carrier=unknown
ro.bootloader=unknown
ro.hardware=aries
ro.revision=48
ro.emmc=0
net.tcp.buffersize.default=4096,87380,110208,4096,16384,110208
net.tcp.buffersize.wifi=4095,87380,110208,4096,16384,110208
net.tcp.buffersize.umts=4094,87380,110208,4096,16384,110208
net.tcp.buffersize.edge=4093,26280,35040,4096,16384,35040
net.tcp.buffersize.gprs=4092,8760,11680,4096,8760,11680
init.svc.recovery=running
sys.usb.config=mass_storage,adb
service.adb.root=1
init.svc.adbd=stopping
sys.usb.state=mass_storage,adb
I:Checking for extendedcommand...
I:Skipping execution of extendedcommand, file not found...
I:Can't partition unsafe device: /dev/block/mmcblk0p1
I:Can't format unknown volume: /external_sd
I:Can't partition unsafe device: /dev/block/mmcblk1p1
Come on People i really need your help.

efs issue?

hi, i had my s6500d soft bricked
was in bootloop and no recovery access, only download mode
afther flashing multiple firmwares and boot images i managed to fix the it but there are still some big issues
afther odin changes status to PASSED, phone reboots and fails to mount /efs partition to update multi-CSC ( Phone imei exists and with sim is ok )
every time i enter in recovery its says:
not need checksum confirmation already executed!!...
and tries to update the multi-csc info, like was the first time it runs this process.
tried to root the phone so i installed: clockworkmod-jena.5.2.0.8.tar.md5 via odin
in cwm every file i try to install results as (BAD) tried root / gapps / different versions of android
even the android acts weird, the slide unlock is missing and this never happend before
cwm log:
Starting recovery on Sat Feb 8 11:44:28 2014
framebuffer: fd 4 (320 x 480)
CWM-based Recovery v5.0.2.8
recovery filesystem table
=========================
0 /tmp ramdisk (null) (null)
1 /boot emmc /dev/block/mmcblk0p8 (null)
2 /recovery emmc /dev/block/mmcblk0p12 (null)
3 /system ext4 /dev/block/mmcblk0p16 (null)
4 /cache ext4 /dev/block/mmcblk0p17 (null)
5 /data ext4 /dev/block/mmcblk0p18 (null)
6 /efs ext4 /dev/block/mmcblk0p19 (null)
7 /emmc vfat /dev/block/mmcblk0p23 (null)
8 /sdcard vfat /dev/block/mmcblk1p1 (null)
W:Unable to get recovery.fstab info for /datadata during fstab generation!
W:Unable to get recovery.fstab info for /sd-ext during fstab generation!
I:Completed outputting fstab.
Irocessing arguments.
I:Checking arguments.
I:device_recovery_start()
Command: "/sbin/recovery"
ro.secure=0
ro.allow.mock.location=1
ro.debuggable=1
persist.service.adb.enable=1
ro.build.id=GRI40
ro.build.display.id=GWK74
ro.build.version.incremental=eng.squadzone.20120709.222956
ro.build.version.sdk=10
ro.build.version.codename=REL
ro.build.version.release=2.3.7
ro.build.date=Mon Jul 9 22:31:00 WIT 2012
ro.build.date.utc=0
ro.build.type=eng
ro.build.user=squadzone
ro.build.host=squadzone-MXC062
ro.build.tags=test-keys
ro.product.model=GT-S6500
ro.product.brand=samsung_jena
ro.product.name=GT-S6500
ro.product.device=jena
ro.product.board=jena
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.manufacturer=samsung
ro.product.locale.language=en
ro.product.locale.region=US
ro.wifi.channels=
ro.board.platform=msm7k
ro.build.product=jena
ro.build.description=GT-S6500-user 2.3.6 GINGERBREAD DXLD1 release-keys
ro.build.fingerprint=samsung/GT-S6500/GT-S6500:2.3.6/GINGERBREAD/DXLD1:user/release-keys
ro.cm.device=jena
rild.libpath=/system/lib/libsec-ril.so
rild.libargs=-d /dev/smd0
keyguard.no_require_sim=true
ro.com.android.dateformat=dd-MM-yyyy
DEVICE_PROVISIONED=1
ro.sf.lcd_density=160
qemu.sf.lcd_density=160
hw.keyboards.0.devname=qwerty
mobiledata.interfaces=pdp0,wlan0,gprs,ppp0
ro.telephony.ril_class=samsung
wifi.interface=wlan0
wifi.supplicant_scan_interval=60
ro.com.android.dataroaming=false
ro.config.hw_menu_unlockscreen=false
ro.media.enc.jpeg.quality=100
ro.media.dec.jpeg.memcap=8000000
ddebug.composition.type=gpu
persist.sys.composition.type=gpu
persist.sys.ui.hw=true
ro.com.google.locationfeatures=1
ro.com.google.networklocation=1
ro.setupwizard.enable_bypass=1
dalvik.vm.lockprof.threshold=500
dalvik.vm.dexopt-flags=m=y
dalvik.vm.heapsize=64m
dalvik.vm.execution-mode=int:jit
dalvik.vm.dexopt-data-only=1
ro.opengles.version=131072
ro.rommanager.developerid=cyanogenmodnightly
ro.url.legal=http://www.google.com/intl/%s/mobile/android/basic/phone-legal.html
ro.url.legal.android_privacy=http://www.google.com/intl/%s/mobile/android/basic/privacy.html
ro.com.google.clientidbase=android-google
ro.com.android.wifi-watchlist=GoogleGuest
ro.setupwizard.enterprise_mode=1
ro.config.ringtone=CyanTone.ogg
ro.config.notification_sound=CyanMessage.ogg
ro.config.alarm_alert=CyanAlarm.ogg
ro.modversion=CyanogenMod-7.2.0-RC1-jena-UNOFFICIAL
ro.kernel.android.checkjni=1
ro.setupwizard.mode=OPTIONAL
net.bt.name=Android
net.change=net.bt.name
dalvik.vm.stack-trace-file=/data/anr/traces.txt
ro.factorytest=0
ro.serialno=60e7dd9
ro.bootmode=unknown
ro.baseband=msm
ro.carrier=unknown
ro.bootloader=unknown
ro.hardware=qcom
ro.revision=0
ro.emmc=1
ro.product.t_carrier2=OPEN
ro.build.PDA=S6500DXXMK1
ro.build.Phone=S6500DXXMK1
ro.build.HW=REV 0.1
ro.build.hidden_ver=S6500DXXMK1
ro.build.changelist=1248583
ro.camera.sound.forced=1
ro.build.FTAswver=
ro.build.FTAhwver=
ril.subscription.types=NV,RUIM
debug.sf.hw=1
debug.composition.7x27A.type=mdp
debug.composition.7x25A.type=mdp
persist.cne.UseCne=none
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.fmc.mode=false
persist.cne.fmc.init.time.out=30
persist.cne.fmc.comm.time.out=130
persist.cne.fmc.retry=false
media.stagefright.enable-player=true
media.stagefright.enable-meta=false
media.stagefright.enable-scan=true
media.stagefright.enable-http=true
media.stagefright.enable-fma2dp=true
media.stagefright.enable-aac=true
media.stagefright.enable-qcp=true
ro.use_data_netmgrd=true
persist.data.ds_fmc_app.mode=0
persist.ims.regmanager.mode=0
ro.bluetooth.request.master=false
ro.qualcomm.bluetooth.ftp=false
ro.qualcomm.bluetooth.sap=false
ro.bluetooth.remote.autoconnect=true
debug.bt.discoverable_time=-1
persist.omh.enabled=1
ro.config.ehrpd=true
ro.qualcomm.cabl=1
ro.fm.analogpath.supported=true
ro.fm.transmitter=false
ro.fm.mulinst.recording.support=false
ro.hw_plat=7x27a
net.streaming.rtsp.uaprof=http://wap.samsungmobile.com/uaprof/GT-S6500D.xml
ro.kernel.qemu=0
ro.config.media_sound=over_the_horizon_preview.ogg
dev.sfbootcomplete=0
ro.com.google.gmsversion=2.3_r11
ro.error.receiver.default=com.samsung.receiver.error
init.svc.recovery=running
init.svc.adbd=running
I:Checking for extendedcommand...
I:Skipping execution of extendedcommand, file not found...
W:failed to mount /dev/block/mmcblk0p19 (Invalid argument)
Error mounting /efs!
Click to expand...
Click to collapse

My advice: Reflash Stock , Flash latest cwm (that would be 6.0.3.2) and then wipe data/factory reset ( if you can't get to recovery, go to download mode, disagree with terms(vol - ) then press Vol+ , Vol- , home all together very fast.) good luck.

CoX26 said:
My advice: Reflash Stock , Flash latest cwm (that would be 6.0.3.2) and then wipe data/factory reset ( if you can't get to recovery, go to download mode, disagree with terms(vol - ) then press Vol+ , Vol- , home all together very fast.) good luck.
Click to expand...
Click to collapse
flashed 6.0.3.2 via odin managed to install the root from cwm,
installing cm-10.1-201312227-unofficial-jenad.zip
E:can't open /sdcard/cm-10.1-201312227-unofficial-jenad.zip (bad) install aborded
edit: tring to use EFS Professional, i get no partion info.. none... does this tool works with s6500d ?
edit 2:
downloaded gaps and cm-11 from your footer ( CyanogenMod 11 By TheWhisp )
status 7 - installation aborted

does any one knows how to regain access/writes to EFS partition ? i think it still exists as long as my phone works fine
why when installing a stock firmware i get no wizard ?

cwm 6.0.3.2 is the latest "standalone" version , flashing the newest ROM's will require you to install the cwm updates (the 6.0.4.5 should be enough , here is the link from thewhisp's goo.im file http://goo.im/devs/thewhisp/jena-recovery/update-cwm-6.0.4.5-jena.zip )
That would solve most errors like status 7 and others..
One more thing: The updates are .zip and need to be installed from cwm.