[INFO][DEV][DISCUSSION] All in one Androidone discussion thread for development - Android One (First-Generation) Cross-Device Genera

[INFO][DEV][DISCUSSION] All in one Androidone discussion thread for development - Android One (First-Generation) Cross-Device Genera

hi friends
Today i got my hands on Spice Dream Uno android one handset.
here is what i found for that device.
May be this info is common to all other android one devices that is why i am posting it in this section.
1. build.prop
Code:
#
# PRODUCT_OEM_PROPERTIES
#
import /oem/oem.prop ro.product.device
import /oem/oem.prop ro.product.name
import /oem/oem.prop ro.product.manufacturer
import /oem/oem.prop ro.product.model
import /oem/oem.prop ro.product.locale.language
import /oem/oem.prop ro.product.locale.region
import /oem/oem.prop ro.config.ringtone
import /oem/oem.prop ro.config.notification_sound
import /oem/oem.prop ro.config.alarm_alert
import /oem/oem.prop ro.config.wallpaper
import /oem/oem.prop ro.config.wallpaper_component
import /oem/oem.prop ro.oem.*
import /oem/oem.prop oem.*
# begin build properties
# autogenerated by buildinfo.sh
ro.build.id=KPW53
ro.build.display.id=KPW53
ro.build.version.incremental=1379542
ro.build.version.sdk=19
ro.build.version.codename=REL
ro.build.version.release=4.4.4
ro.build.date=Fri Aug 22 22:49:18 UTC 2014
ro.build.date.utc=1408747758
ro.build.type=user
ro.build.user=android-build
ro.build.host=wpds12.hot.corp.google.com
ro.build.tags=release-keys
ro.product.brand=google
ro.product.board=
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.locale.language=en
ro.product.locale.region=US
ro.wifi.channels=
ro.board.platform=mt6582
# ro.build.product is obsolete; use ro.product.device
ro.build.product=sprout
# Do not try to parse description, fingerprint, or thumbprint
ro.build.description=sprout-user 4.4.4 KPW53 1379542 release-keys
ro.build.thumbprint=4.4.4/KPW53/1379542:user/release-keys
ro.build.characteristics=default
# end build properties
#
# from device/mediatek/sprout/sprout/system.prop
#
#
# system.prop for generic sdk
#
rild.libpath=/system/lib/mtk-ril.so
rild.libargs=-d /dev/ttyC0
# MTK, Infinity, 20090720 {
wifi.interface=wlan0
# MTK, Infinity, 20090720 }
# MTK, mtk03034, 20101210 {
ro.mediatek.wlan.wsc=1
# MTK, mtk03034 20101210}
# MTK, mtk03034, 20110318 {
ro.mediatek.wlan.p2p=1
# MTK, mtk03034 20110318}
# MTK, mtk03034, 20101213 {
mediatek.wlan.ctia=0
# MTK, mtk03034 20101213}
#
wifi.tethering.interface=ap0
#
ro.sf.lcd_density=240
ro.opengles.version=131072
wifi.direct.interface=p2p0
dalvik.vm.heapgrowthlimit=96m
dalvik.vm.heapsize=128m
# USB MTP WHQL
ro.sys.usb.mtp.whql.enable=0
# Power off opt in IPO
sys.ipo.pwrdncap=2
ro.sys.usb.storage.type=mtp,mass_storage
# USB BICR function
ro.sys.usb.bicr=yes
# USB Charge only function
ro.sys.usb.charging.only=yes
# audio
ro.camera.sound.forced=0
ro.audio.silent=0
ro.zygote.preload.enable=0
ro.kernel.zio=38,108,105,16
#ro.kernel.qemu=1
#ro.kernel.qemu.gles=0
ro.boot.selinux=disable
# Disable dirty region for Mali
debug.hwui.render_dirty_regions=false
#
# ADDITIONAL_BUILD_PROPERTIES
#
ro.config.ringtone=Titania.ogg
ro.config.notification_sound=Tethys.ogg
ro.config.alarm_alert=Oxygen.ogg
ro.com.android.dateformat=MM-dd-yyyy
ro.com.android.dataroaming=false
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.carrier=unknown
ro.com.android.wifi-watchlist=GoogleGuest
ro.error.receiver.system.apps=com.google.android.gms
ro.setupwizard.enterprise_mode=1
dalvik.vm.heapgrowthlimit=96m
dalvik.vm.heapsize=128m
ro.mediatek.chip_ver=S01
ro.mediatek.version.release=ALPS.W10.24.p0
ro.mediatek.platform=MT6582
ro.mediatek.version.sdk=1
ro.telephony.sim.count=2
persist.radio.default.sim=0
persist.radio.multisim.config=dsds
ro.telephony.default_network=0,1
persist.gemini.sim_num=2
ro.gemini.smart_3g_switch=1
ril.specific.sm_cause=0
bgw.current3gband=0
ril.external.md=0
ro.sf.hwrotation=0
ril.current.share_modem=2
curlockscreen=1
ro.mediatek.gemini_support=true
persist.radio.fd.counter=15
persist.radio.fd.off.counter=5
persist.radio.fd.r8.counter=15
persist.radio.fd.off.r8.counter=5
persist.mtk.wcn.combo.chipid=-1
drm.service.enabled=true
fmradio.driver.enable=0
ril.first.md=1
ril.flightmode.poweroffMD=1
ril.telephony.mode=0
dalvik.vm.mtk-stack-trace-file=/data/anr/mtk_traces.txt
ril.radiooff.poweroffMD=0
dalvik.vm.heapstartsize=8m
dalvik.vm.heaptargetutilization=0.75
dalvik.vm.heapminfree=512k
dalvik.vm.heapmaxfree=8m
ro.mediatek.version.branch=KK.AOSP
keyguard.no_require_sim=true
ro.facelock.black_timeout=400
ro.facelock.det_timeout=1500
ro.facelock.rec_timeout=2500
ro.facelock.lively_timeout=2500
ro.facelock.est_max_time=600
ro.facelock.use_intro_anim=false
persist.sys.dalvik.vm.lib=libdvm.so
net.bt.name=Android
dalvik.vm.stack-trace-file=/data/anr/traces.txt
2.Partition layout
Code:
adb shell
Code:
127|[email protected]_sprout:/ $ cat proc/partitions
major minor #blocks name
179 0 3817472 mmcblk0
179 1 3072 mmcblk0p1
179 2 5120 mmcblk0p2
179 3 10240 mmcblk0p3
179 4 10240 mmcblk0p4
179 5 256 mmcblk0p5
179 6 384 mmcblk0p6
179 7 10240 mmcblk0p7
179 8 10240 mmcblk0p8
179 9 6144 mmcblk0p9
179 10 512 mmcblk0p10
179 11 8192 mmcblk0p11
179 12 65536 mmcblk0p12
179 13 16768 mmcblk0p13
179 14 1024000 mmcblk0p14
179 15 131072 mmcblk0p15
179 16 2416640 mmcblk0p16
179 17 32768 mmcblk0p17
179 18 65024 mmcblk0p18
179 64 4096 mmcblk0boot1
179 32 4096 mmcblk0boot0
179 96 7782400 mmcblk1
179 97 7781376 mmcblk1p1
and
Code:
[email protected]_sprout:/ $ ls -l /dev/block/platform/mtk-msdc.0/by-name
lrwxrwxrwx root root 2010-01-01 05:30 boot -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 2010-01-01 05:30 bootloader -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 2010-01-01 05:30 cache -> /dev/block/mmcblk0p15
lrwxrwxrwx root root 2010-01-01 05:30 expdb -> /dev/block/mmcblk0p13
lrwxrwxrwx root root 2010-01-01 05:30 gen -> /dev/block/mmcblk0p18
lrwxrwxrwx root root 2010-01-01 05:30 logo -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 2010-01-01 05:30 metadata -> /dev/block/mmcblk0p17
lrwxrwxrwx root root 2010-01-01 05:30 nvram -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 2010-01-01 05:30 oem -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 2010-01-01 05:30 para -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 2010-01-01 05:30 proinfo -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 2010-01-01 05:30 protect1 -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 2010-01-01 05:30 protect2 -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 2010-01-01 05:30 recovery -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 2010-01-01 05:30 seccfg -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 2010-01-01 05:30 secro -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 2010-01-01 05:30 system -> /dev/block/mmcblk0p14
lrwxrwxrwx root root 2010-01-01 05:30 userdata -> /dev/block/mmcblk0p16
3.Mount points
Code:
adb shell
Code:
[email protected]_sprout:/ $ 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
none /acct cgroup rw,relatime,cpuacct 0 0
none /sys/fs/cgroup tmpfs rw,seclabel,relatime,mode=750,gid=1000 0 0
none /sys/fs/cgroup/memory cgroup rw,relatime,memory 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
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
/dev/block/platform/mtk-msdc.0/by-name/system /system ext4 ro,seclabel,relatime,data=ordered 0 0
/dev/block/platform/mtk-msdc.0/by-name/userdata /data ext4 rw,seclabel,nosuid,nodev,noatime,discard,noauto_da_alloc,data=ordered 0 0
/dev/block/platform/mtk-msdc.0/by-name/cache /cache ext4 rw,seclabel,nosuid,nodev,noatime,discard,noauto_da_alloc,data=ordered 0 0
/dev/block/platform/mtk-msdc.0/by-name/protect1 /protect_f ext4 rw,seclabel,nosuid,nodev,noatime,nodelalloc,noauto_da_alloc,commit=1,data=ordered 0 0
/dev/block/platform/mtk-msdc.0/by-name/protect2 /protect_s ext4 rw,seclabel,nosuid,nodev,noatime,nodelalloc,noauto_da_alloc,commit=1,data=ordered 0 0
/dev/block/platform/mtk-msdc.0/by-name/oem /oem ext4 ro,context=u:object_r:oemfs:s0,nosuid,nodev,relatime,data=ordered 0 0
adb /dev/usb-ffs/adb functionfs rw,relatime 0 0
/sys/kernel/debug /sys/kernel/debug debugfs rw,relatime 0 0
/dev/block/vold/179:97 /mnt/media_rw/sdcard0 vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1023,gid=1023,fmask=0007,dmask=0007,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/vold/179:97 /mnt/secure/asec vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1023,gid=1023,fmask=0007,dmask=0007,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/fuse /storage/sdcard0 fuse rw,nosuid,nodev,relatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
4.fastboot
yes this device has fastboot.
Unlocking bootloader via fastboot
***reboot into fastboot mode
2ways
a] switch off the phone>>press volume up + power at same time>>boot menu should appear>>go to fastboot menu with volume up and then select by pressing volume down.
OR
b]connect phone to PC(i use linux i dont need to install any drivers or adb or fastboot packages).>>enable usb debugging mode (developer options)>>adb reboot bootloader
this will boot into fastboot directly.
***connect phone to the PC
***open terminal>>fastboot oem unlock>>press volume down to select fastboot again>>fastboot format cache>>fastboot format userdata>>fastboot reboot
now you have unloicked bootloader.
5. Recovery
when
adb reboot recovery
Click to expand...
Click to collapse
given >>it boot into recovery screen where only some chinese picture of recovery is present.
On chinese recovery screen, if you press volume up and power button you will get apply zip from sideload and sdcard.
6.there is no valid fstab present at the root
7. init rc files are seem to be hidden out or symlinked somewhere else.
if you try to open them they open as only a blank text file.
8. Build version in build.prop is KPW53.
i dont know which version of kitkat is that.
9. baseband version
WR8.W1412.MD.WG.GMP.SP.W14.26.P3,2014/08/15 11.39
10. KERNEL version
3.4.67 [email protected]#1 Wed Aug 20 14:13:29 PDT 2014
11. SELINUX is disabled in build.prop
13. SAR value is 0.641 W/Kg (1g)
14. oem.prop for spice dream uno mi-498
Code:
ro.product.device=Mi-498_sprout
ro.product.name=Mi-498
ro.product.manufacturer=Spice
ro.product.model=Spice Mi-498
ro.product.locale.language=en
ro.product.locale.region=IN
ro.config.wallpaper=/oem/media/Default.jpg
15. partition layout proc/dumchar type(this does not exist on our phone but this info may be useful to create scatter file for sp flash tool)
Code:
partno: start_sect nr_sects partition_name
emmc_p1: 00000400 00001800 "proinfo"
emmc_p2: 00001c00 00002800 "nvram"
emmc_p3: 00004400 00005000 "protect1"
emmc_p4: 00009400 00005000 "protect2"
emmc_p5: 0000e400 00000200 "seccfg"
emmc_p6: 0000e600 00000300 "bootloader"
emmc_p7: 0000e900 00005000 "boot"
emmc_p8: 00013900 00005000 "recovery"
emmc_p9: 00018900 00003000 "secro"
emmc_p10: 0001b900 00000400 "para"
emmc_p11: 0001bd00 00004000 "logo"
emmc_p12: 0001fd00 00020000 "oem"
emmc_p13: 0003fd00 00008300 "expdb"
emmc_p14: 00048000 001f4000 "system"
emmc_p15: 0023c000 00040000 "cache"
emmc_p16: 0027c000 0049c000 "userdata"
emmc_p17: 00718000 00010000 "metadata"
emmc_p18: 00728000 0001fc00 "gen"
16. more info for the android one partitions and bootloader and preloader methods
Code:
(bootloader) max-download-size: 0x8000000
(bootloader) partition-size:gen: 3f80000
(bootloader) partition-type:gen: raw data
(bootloader) partition-size:metadata: 2000000
(bootloader) partition-type:metadata: raw data
(bootloader) partition-size:userdata: 93800000
(bootloader) partition-type:userdata: ext4
(bootloader) partition-size:cache: 8000000
(bootloader) partition-type:cache: ext4
(bootloader) partition-size:system: 3e800000
(bootloader) partition-type:system: ext4
(bootloader) partition-size:expdb: 1060000
(bootloader) partition-type:expdb: raw data
(bootloader) partition-size:oem: 4000000
(bootloader) partition-type:oem: ext4
(bootloader) partition-size:logo: 800000
(bootloader) partition-type:logo: raw data
(bootloader) partition-size:para: 80000
(bootloader) partition-type:para: raw data
(bootloader) partition-size:secro: 600000
(bootloader) partition-type:secro: ext4
(bootloader) partition-size:recovery: a00000
(bootloader) partition-type:recovery: raw data
(bootloader) partition-size:boot: a00000
(bootloader) partition-type:boot: raw data
(bootloader) partition-size:bootloader: 60000
(bootloader) partition-type:bootloader: raw data
(bootloader) partition-size:seccfg: 40000
(bootloader) partition-type:seccfg: raw data
(bootloader) partition-size:protect2: a00000
(bootloader) partition-type:protect2: ext4
(bootloader) partition-size:protect1: a00000
(bootloader) partition-type:protect1: ext4
(bootloader) partition-size:nvram: 500000
(bootloader) partition-type:nvram: raw data
(bootloader) partition-size:proinfo: 300000
(bootloader) partition-type:proinfo: raw data
(bootloader) partition-size:preloader: 40000
(bootloader) partition-type:preloader: raw data
(bootloader) off-mode-charge: 1
(bootloader) warranty: no
(bootloader) unlocked: yes
(bootloader) secure: no
(bootloader) version-baseband: MOLY
(bootloader) kernel: lk
(bootloader) product: sprout
(bootloader) version-preloader: 0.1.02
(bootloader) version-bootloader: 0.5.17
17. how to access preloader
The preloader does exist and can be accessed.
Remove and replace the battery and keep the volume down button with the phone connected to activate it.
thanks to @joshuab227

reserved1

@k2wl
Can you send me output of
Code:
cat /proc/cmdline
Also check if you have adb access in the Chinese recovery.

varun.chitre15 said:
@k2wl
Can you send me output of
Code:
cat /proc/cmdline
Also check if you have adb access in the Chinese recovery.
Click to expand...
Click to collapse
cat proc/cmdline
Click to expand...
Click to collapse
permission denied.
and there is no adb access in chinese recovery

k2wl said:
permission denied.
and there is no adb access in chinese recovery
Click to expand...
Click to collapse
Hmm... and none of the exploits look to be working, Google has patched them all. Even if I had the command line I could have build up a recovery which could have opened all these barriers.
The factory images just like the Nexus line are likely to be posted by Google soon.

Is any reason adb not being available in recovery?
varun.chitre15 said:
Hmm... and none of the exploits look to be working, Google has patched them all. Even if I had the command line I could have build up a recovery which could have opened all these barriers.
The factory images just like the Nexus line are likely to be posted by Google soon.
Click to expand...
Click to collapse

varun.chitre15 said:
Hmm... and none of the exploits look to be working, Google has patched them all. Even if I had the command line I could have build up a recovery which could have opened all these barriers.
The factory images just like the Nexus line are likely to be posted by Google soon.
Click to expand...
Click to collapse
oh you need that for recovery build.
then here it is
console=tty0 console=ttyMT3,921600n1 root=/dev/ram vmalloc=496M slub_max_order=0 slub_debug=O androidboot.hardware=sprout
Click to expand...
Click to collapse
hope this helps!!

k2wl said:
oh you need that for recovery build.
then here it is
hope this helps!!
Click to expand...
Click to collapse
Try flashing this new recovery
https://s.basketbuild.com/filedl/devs?dev=varun.chitre15&dl=varun.chitre15/A1/recovery.img
fastboot flash recovery path/to/recovery.img
Check if it boots.
P.s: You will lose that Chinese recovery after this, it isn't of any use anyway.

varun.chitre15 said:
Try flashing this new recovery
https://s.basketbuild.com/filedl/devs?dev=varun.chitre15&dl=varun.chitre15/A1/recovery.img
fastboot flash recovery path/to/recovery.img
Check if it boots.
P.s: You will lose that Chinese recovery after this, it isn't of any use anyway.
Click to expand...
Click to collapse
recovery doesnt boot.
it stays on spice logo
saying recovery mode in the bottom and after a while it shows oem unlock and phone reboots.

k2wl said:
recovery doesnt boot.
it stays on spice logo
saying recovery mode in the bottom and after a while it shows oem unlock and phone reboots.
Click to expand...
Click to collapse
I have uploaded a new image at the same link. Check with that.

varun.chitre15 said:
I have uploaded a new image at the same link. Check with that.
Click to expand...
Click to collapse
this recovery does not boot.
spice mobile screen with recovery mode for 1 min. then spice screen with oem unlocked for 10-15 sec then phone reboots.

k2wl said:
this recovery does not boot.
spice mobile screen with recovery mode for 1 min. then spice screen with oem unlocked for 10-15 sec then phone reboots.
Click to expand...
Click to collapse
OK I have ordered the Micromax variant, will be able to experiment myself after that.

guys try this to gain root http://www.mgyun.com/en/getvroot

varunrocks17 said:
guys try this to gain root http://www.mgyun.com/en/getvroot
Click to expand...
Click to collapse
man it doesnt work. plz stop posting it on every android 1 thread. the phones have same everything internal.

can upload a backup of the system and boot?

walkman-star said:
can upload a backup of the system and boot?
Click to expand...
Click to collapse
no root access till now so no boot.img
but system dump can be taken.

System dump
Find system dump here http://dropjar.com/#YazLGa6
k2wl said:
no root access till now so no boot.img
but system dump can be taken.
Click to expand...
Click to collapse

sheldroid said:
Find system dump here
Click to expand...
Click to collapse
boot.img can upload ?

No root available so can't take boot image
Sent from my Spice Mi-498

k2wl said:
no root access till now...
Click to expand...
Click to collapse
So there are no exploits reported to working as of now?
How about towelroot? (BTW I've seen many devices with kernel build date greater than JUN 2014 and towelroot working) If it doesn't work, you can try to play with modstrings.

Related

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.....

How I fixed my bricked Nexus 5 (corrupted userdata, bootlooping)

Hi everyone,
First of all - apologies if this is in the wrong forum. First time I post something, so not too sure if this is the right place.
I've been struggling with my Nexus 5 for the past 3 days after I attempted a factory reset. After trying everything I could find, I managed to combine some strategies from different threads, and got some help from a friend who is a linux specialist. As it has been REALLY HARD for me to fix this, I thought I would post the solution in case anyone is seeing the same issue.
Summary of my issue:
I attempted a factory reset to cleanup the phone. That was really all I intended to do.
The factory reset got stuck on "erasing". After 30 minutes waiting, I forced the phone to reboot. Then everything went downhill.
My Nexus 5 started bootlooping. It wouldn't even get in recovery mode.
I've flashed ClockWorkMod Recovery, and tried to format everything and start again. The processes to wipe partitions would fail.
Flashing stock also failed, as things would hang on "erasing cache".
I found references on multiple threads about things to try - from flashing other ROMs, to formatting the file system manually, and basically trying every step of a flashing a stock installation manually.
The bottom line is everything would hang because the system could not mount the /data partition.
When I tried to use "e2fsck" to check /userdata partition, it would give me an error about the file system being corrupted, and suggesting to use a different superblock.
Some threads here in XDA suggested to use CWM and TWRP to format the partition, as that would usually fix the problem. It didn't work in my case.
The system would basically hang when trying to format /data, with any method I tried.
When using the "dmesg" command, I would also see lots of errors with superblocks when trying to mount "/data".
I considered it could be a hardware issue, but I was not seeing problems with the other partitions (/cache, /system, /recovery, and so on).
Solution:
I fixed the problem by removing the partition, recreating it with "ext2" file system, then upgrading to "ext4" manually, and finally flashing the system images again WITHOUT flashing userdata.
Every time I flash "userdata", the partition just gets corrupted.
This is the step by step on how I did it:
1) Start the phone on bootloader by holding power button + volume down. Flash CWM recovery through fastboot.
Download CWM recovery from here: https://clockworkmod.com/rommanager
I'm using windows, so I opened a command prompt on the "Android SDK\platform-tools" folder.
run: "fastboot flash recovery <CWM_Recovery_Folder>\recovery-clockwork-6.0.4.5-hammerhead.img"
2) Reboot in recovery mode, so that it would load ADB. In the command prompt I ran "adb shell" so I could use the linux tools
Use "parted /dev/block/mmcblk0" to open the parted tool for the mmc block.
Use command "print" to list all partitions. You should see something like this:
Number Start End Size File system Name Flags
1 524kB 67.6MB 67.1MB fat16 modem
2 67.6MB 68.7MB 1049kB sbl1
3 68.7MB 69.2MB 524kB rpm
4 69.2MB 69.7MB 524kB tz
5 69.7MB 70.3MB 524kB sdi
6 70.3MB 70.8MB 524kB aboot
7 70.8MB 72.9MB 2097kB pad
8 72.9MB 73.9MB 1049kB sbl1b
9 73.9MB 74.4MB 524kB tzb
10 74.4MB 75.0MB 524kB rpmb
11 75.0MB 75.5MB 524kB abootb
12 75.5MB 78.6MB 3146kB modemst1
13 78.6MB 81.8MB 3146kB modemst2
14 81.8MB 82.3MB 524kB metadata
15 82.3MB 99.1MB 16.8MB misc
16 99.1MB 116MB 16.8MB ext4 persist
17 116MB 119MB 3146kB imgdata
18 119MB 142MB 23.1MB laf
19 142MB 165MB 23.1MB boot
20 165MB 188MB 23.1MB recovery
21 188MB 191MB 3146kB fsg
22 191MB 192MB 524kB fsc
23 192MB 192MB 524kB ssd
24 192MB 193MB 524kB DDR
25 193MB 1267MB 1074MB ext4 system
26 1267MB 1298MB 31.5MB crypto
27 1298MB 2032MB 734MB ext4 cache
28 2032MB 31.3GB 29.2GB ext4 userdata
29 31.3GB 31.3GB 5632B grow
Click to expand...
Click to collapse
3) Remove the existing data partition by running command "rm 28" .
4) Recreate the partition and the file system with "mkpartfs". I didn't use all parameters at once, but just informed the proper values as requested by the tool:
(parted) mkpartfs
mkpartfs
mkpartfs
Partition name? []? userdate
userdate
userdate
File system type? [ext2]? ext2
ext2
ext2
Start? 2032MB
2032MB
2032MB
End? 31.3GB
31.3GB
31.3GB
Click to expand...
Click to collapse
5) The partition should now be recreated as "ext2" file system. I've set the partition name with:
(parted) name 28 userdata
name 28 userdata
name 28 userdata
Click to expand...
Click to collapse
If you print again, you should see the new partition as ext2 file system:
(...)
28 2032MB 31.3GB 29.2GB ext2 userdata
(...)
Click to expand...
Click to collapse
6) Upgrade the FS from ext2 to ext4 by using make_ext4fs:
make_ext4fs -l 29236371456 -b 4096 -g 32768 -i 8192 -I 256 -j 32768 -L msdos -a /data /dev/block/mmcblk0p28
Now here is the interesting part. When I tried to run "flash-all" from the google stock image, this is what I would see when it ran the format script on the userdata partition:
OKAY [ 13.186s]
formatting 'userdata' partition...
Creating filesystem with parameters:
Size: 29236371456
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 32768
Label:
Blocks: 7137786
Block groups: 218
Reserved block group size: 1024
Created filesystem with 11/1785856 inodes and 156120/7137786 blocks
sending 'userdata' (139109 KB)...
writing 'userdata'...
OKAY [ 16.625s]
finished. total time: 29.811s
Click to expand...
Click to collapse
When I manually ran the make_ext4fs, the only difference was I added a label "msdos" and this was the result:
Creating filesystem with parameters:
Size: 29236371456
Block size: 4096
Blocks per group: 32768
Inodes per group: 48
Inode size: 256
Journal blocks: 32768
Label: msdos
Blocks: 7137786
Block groups: 218
Reserved block group size: 1024
Click to expand...
Click to collapse
Almost the same thing, but with a difference in "Inodes per group": stock script shows 8192, and running manually it shows 48.
I have no idea why is that. Honestly I know very little about linux and its file systems, so I don't know what that means.
After I did this, I was FINALLY able to mount the "/data" partition.
8) Checked the file system with e2fsck. It now worked fine:
~ # e2fsck /dev/block/mmcblk0p28
e2fsck /dev/block/mmcblk0p28
e2fsck 1.41.14 (22-Dec-2010)
msdos: clean, 11/10464 files, 45158/7137786 blocks
~ #
9) Manually flash google stock system, cache, boot, and bootloader.
I was using this image: hammerhead-ktu84p-factory-35ea0277.tgz
I uncompressed this to a folder, and also uncompressed the image-hammerhead-ktu84p.zip.
So I ran:
fastboot flash system system.img
fastboot flash cache cache.img
fastboot flash boot boot.img
After this, I rebooted the system and it loaded, after loooooong 3 days reading through everything I could on XDA!
These were some of the threads that helped me in one way or another to get to this solution:
http://forum.xda-developers.com/showpost.php?p=26285877&postcount=12
http://forum.xda-developers.com/google-nexus-5/help/help-nexus-5-bricked-clearing-cache-t2564509
http://forum.xda-developers.com/google-nexus-5/help/stuck-erasing-doing-factory-reset-t2530342
http://forum.xda-developers.com/google-nexus-5/orig-development/nexus-5-f2fs-t2668486
http://forum.xda-developers.com/goo...o-repairing-corrupted-data-partition-t2577447
http://forum.xda-developers.com/showthread.php?t=1441928
http://forum.xda-developers.com/google-nexus-5/help/help-nexus-5-bricked-clearing-cache-t2564509
http://forum.xda-developers.com/google-nexus-5/help/help-stuck-bootloop-t2515338
http://forum.xda-developers.com/google-nexus-5/help/stuck-google-logo-recovery-mode-t2898337
I really hope no one else had the same "luck" as I did, since this problem has been a nightmare.
But in case you unfortunately do... hope this helps!

Great guide. Might become handy for other users. It should be stickied

Why would you force reboot while factory resetting in the first place lol
Sent from my Nexus 5

Good guide but a bricked phone is rendered useless, hence the name 'bricked.' If your phone can still power on, it is not bricked. You said your self you got it out of a bootloop. That's essentially all you had, a bootloop, and you were able to figure out what was wrong with it.
Just a heads up so we don't throw that term around loosely since a lot of people do so.
You can't bring a phone back from a brick. I think JTAG is an option but its for Samsung phones only. (Feel free to correct me if I'm wrong.)

dicecuber said:
Why would you force reboot while factory resetting in the first place lol
Sent from my Nexus 5
Click to expand...
Click to collapse
Yeap, I know it sounds stupid but the factory reset was hanging, lol.
I tried multiple times and it would hang every time. I left it running for more than 3h once and nothing happened.

jayRokk said:
Good guide but a bricked phone is rendered useless, hence the name 'bricked.' If your phone can still power on, it is not bricked. You said your self you got it out of a bootloop. That's essentially all you had, a bootloop, and you were able to figure out what was wrong with it.
Just a heads up so we don't throw that term around loosely since a lot of people do so.
You can't bring a phone back from a brick. I think JTAG is an option but its for Samsung phones only. (Feel free to correct me if I'm wrong.)
Click to expand...
Click to collapse
Thanks for clarifying! I thought bricked also meant "the phone is about to go useless, but there is a tiny hope", lol.
Is there a way to correct the thread name?
You're right - it was only bootlooping.

There's soft-brick and hard-brick.
Wysłane z mojego Nexus 5

rm 28
3) Remove the existing data partition by running command "rm 28": im getting a error on this step .
need help..

How did the phone become bricked? What was the phone doing before trying to unbrick?

audit13 said:
How did the phone become bricked? What was the phone doing before trying to unbrick?
Click to expand...
Click to collapse
dont know how it got bricked..in morning when i wake up its suddenly start showing the boot only for hours. I've tried flashig it.evertime got flash write failure for bootloader and other images except boot.img .i've checked for emmc its fine and showing the device partion.
I'm using nexus 5 16gb device.pls anyone help

I assume the bootloader is unlocked since you are able to flash the boot.img. Try this: re-lock the bootloader, reboot to fastboot and see if the bootloader remains locked. If the bootloader unlocks itself, this is an indication that the memory chip is damaged. Also try flashing the older stock ROM available.

audit13 said:
I assume the bootloader is unlocked since you are able to flash the boot.img. Try this: re-lock the bootloader, reboot to fastboot and see if the bootloader remains locked. If the bootloader unlocks itself, this is an indication that the memory chip is damaged. Also try flashing the older stock ROM available.
Click to expand...
Click to collapse
havn't tried to lock the bootloader but tried all these after reading too many posts but dont't what the issue is?...pls have a look into this..
_____________________________________________
C:\Program Files (x86)\WugFresh Development\Nexus Root Toolkit\data>adb shell
~ # list users
/sbin/sh: list: not found
~ # df
Filesystem 1K-blocks Used Available Use% Mounted on
tmpfs 949780 128 949652 0% /dev
tmpfs 949780 0 949780 0% /storage
tmpfs 949780 0 949780 0% /mnt/secure
tmpfs 949780 0 949780 0% /mnt/fuse
~ # cat /proc/partitions
major minor #blocks name
179 0 15388672 mmcblk0
179 1 65536 mmcblk0p1
179 2 1024 mmcblk0p2
179 3 512 mmcblk0p3
179 4 512 mmcblk0p4
179 5 512 mmcblk0p5
179 6 512 mmcblk0p6
179 7 2048 mmcblk0p7
179 8 1024 mmcblk0p8
179 9 512 mmcblk0p9
179 10 512 mmcblk0p10
179 11 512 mmcblk0p11
179 12 3072 mmcblk0p12
179 13 3072 mmcblk0p13
179 14 512 mmcblk0p14
179 15 16384 mmcblk0p15
179 16 16384 mmcblk0p16
179 17 3072 mmcblk0p17
179 18 22528 mmcblk0p18
179 19 22528 mmcblk0p19
179 20 22528 mmcblk0p20
179 21 3072 mmcblk0p21
179 22 512 mmcblk0p22
179 23 512 mmcblk0p23
179 24 512 mmcblk0p24
179 25 1048576 mmcblk0p25
179 26 30720 mmcblk0p26
179 27 716800 mmcblk0p27
179 28 13404138 mmcblk0p28
179 29 5 mmcblk0p29
179 32 4096 mmcblk0rpmb
~ # mount
rootfs on / type rootfs (rw)
tmpfs on /dev type tmpfs (rw,seclabel,nosuid,relatime,mode=755)
devpts on /dev/pts type devpts (rw,seclabel,relatime,mode=600)
proc on /proc type proc (rw,relatime)
sysfs on /sys type sysfs (rw,seclabel,relatime)
selinuxfs on /sys/fs/selinux type selinuxfs (rw,relatime)
tmpfs on /storage type tmpfs (rw,seclabel,relatime,mode=050,gid=1028)
tmpfs on /mnt/secure type tmpfs (rw,seclabel,relatime,mode=700)
tmpfs on /mnt/fuse type tmpfs (rw,seclabel,relatime,mode=775,gid=1000)
~ # mount -o,rw /system
~ # mount
rootfs on / type rootfs (rw)
tmpfs on /dev type tmpfs (rw,seclabel,nosuid,relatime,mode=755)
devpts on /dev/pts type devpts (rw,seclabel,relatime,mode=600)
proc on /proc type proc (rw,relatime)
sysfs on /sys type sysfs (rw,seclabel,relatime)
selinuxfs on /sys/fs/selinux type selinuxfs (rw,relatime)
tmpfs on /storage type tmpfs (rw,seclabel,relatime,mode=050,gid=1028)
tmpfs on /mnt/secure type tmpfs (rw,seclabel,relatime,mode=700)
tmpfs on /mnt/fuse type tmpfs (rw,seclabel,relatime,mode=775,gid=1000)
/dev/block/platform/msm_sdcc.1/by-name/system on /system type ext4 (rw,seclabel,
relatime,data=ordered)
~ # moutn -o,rw /cah←[J
/sbin/sh: moutn: not found
~ # mount -o,rw /cache
mount: mounting /dev/block/platform/msm_sdcc.1/by-name/cache on /cache failed: I
nvalid argument
~ # mount -o,rw /data
mount: mounting /dev/block/platform/msm_sdcc.1/by-name/userdata on /data failed:
Invalid argument
~ # mount -o,rw /sdcard
mount: can't find /sdcard in /etc/fstab
~ # ls -l
drwxr-xr-x 2 root root 0 Jan 1 09:39 boot
drwxr-xr-x 2 root root 0 Jan 1 09:39 cache
-rwxr-x--- 1 root root 288392 Jan 1 00:00 charger
drwxr-xr-x 3 root root 0 Jan 1 09:39 data
drwxr-xr-x 2 root root 0 Jan 1 09:39 datadata
-rw-r--r-- 1 root root 3976 Jan 1 00:00 default.prop
drwxr-xr-x 10 root root 4480 Jan 1 09:39 dev
drwxr-xr-x 2 root root 0 Jan 1 09:39 emmc
drwxr-xr-x 2 root root 0 Jan 1 09:39 etc
drwxr-xr-x 2 root root 0 Jan 1 09:39 external_sd
-rw-r--r-- 1 root root 9375 Jan 1 00:00 file_contexts
-rw-r----- 1 root root 953 Jan 1 00:00 fstab.goldfish
-rw-r----- 1 root root 2653 Jan 1 00:00 fstab.hammerhead
-rwxr-x--- 1 root root 179556 Jan 1 00:00 init
-rwxr-x--- 1 root root 2708 Jan 1 00:00 init.rc
drwxr-xr-x 2 root root 0 Jan 1 09:39 internal_sd
drwxrwxr-x 5 root system 0 Jan 1 09:39 mnt
dr-xr-xr-x 127 root root 0 Jan 1 00:00 proc
-rw-r--r-- 1 root root 2161 Jan 1 00:00 property_contexts
drwxr-xr-x 2 root root 0 Jan 1 09:39 recovery
drwxr-xr-x 3 root root 0 Jan 1 00:00 res
drwx------ 2 root root 0 Dec 1 2013 root
drwxr-x--- 2 root root 0 Jan 1 00:00 sbin
drwxr-xr-x 2 root root 0 Jan 1 09:39 sd-ext
lrwxrwxrwx 1 root root 11 Jan 1 09:39 sdcard -> /data/media
-rw-r--r-- 1 root root 711 Jan 1 00:00 seapp_contexts
-rw-r--r-- 1 root root 74942 Jan 1 00:00 sepolicy
d---r-x--- 2 root sdcard_r 40 Jan 1 09:39 storage
dr-xr-xr-x 12 root root 0 Jan 1 09:39 sys
drwxr-xr-x 14 root root 4096 Jan 1 00:00 system
drwxrwxr-x 2 root shell 0 Jan 1 09:39 tmp
-rw-r--r-- 1 root root 272 Jan 1 00:00 ueventd.goldfish.rc
-rw-r--r-- 1 root root 2204 Jan 1 00:00 ueventd.hammerhead.rc
-rw-r--r-- 1 root root 5897 Jan 1 00:00 ueventd.rc
~ # cat recovery.fstab
cat: can't open 'recovery.fstab': No such file or directory
~ # cat recovery.fstab.bak
cat: can't open 'recovery.fstab.bak': No such file or directory
~ # system /bin
/sbin/sh: system: not found
~ # system/bin
/sbin/sh: system/bin: Permission denied
~ # e2fsck
Usage: e2fsck [-panyrcdfvtDFV] [-b superblock] [-B blocksize]
[-I inode_buffer_blocks] [-P process_inode_size]
[-l|-L bad_blocks_file] [-C fd] [-j external_journal]
[-E extended-options] device
Emergency help:
-p Automatic repair (no questions)
-n Make no changes to the filesystem
-y Assume "yes" to all questions
-c Check for bad blocks and add them to the badblock list
-f Force checking even if filesystem is marked clean
-v Be verbose
-b superblock Use alternative superblock
-B blocksize Force blocksize when looking for superblock
-j external_journal Set location of the external journal
-l bad_blocks_file Add to badblocks list
-L bad_blocks_file Set badblocks list
~ # -p
/sbin/sh: -p: not found
~ # p
/sbin/sh: p: not found
~ # e2fsck -p
Usage: e2fsck [-panyrcdfvtDFV] [-b superblock] [-B blocksize]
[-I inode_buffer_blocks] [-P process_inode_size]
[-l|-L bad_blocks_file] [-C fd] [-j external_journal]
[-E extended-options] device
Emergency help:
-p Automatic repair (no questions)
-n Make no changes to the filesystem
-y Assume "yes" to all questions
-c Check for bad blocks and add them to the badblock list
-f Force checking even if filesystem is marked clean
-v Be verbose
-b superblock Use alternative superblock
-B blocksize Force blocksize when looking for superblock
-j external_journal Set location of the external journal
-l bad_blocks_file Add to badblocks list
-L bad_blocks_file Set badblocks list
~ # c
/sbin/sh: c: not found
~ # e2fsckc
/sbin/sh: e2fsckc: not found
~ # e2fsck c
e2fsck 1.41.14 (22-Dec-2010)
e2fsck: No such file or directory while trying to open c
Possibly non-existent device?
~ # e2fsck -c
Usage: e2fsck [-panyrcdfvtDFV] [-b superblock] [-B blocksize]
[-I inode_buffer_blocks] [-P process_inode_size]
[-l|-L bad_blocks_file] [-C fd] [-j external_journal]
[-E extended-options] device
Emergency help:
-p Automatic repair (no questions)
-n Make no changes to the filesystem
-y Assume "yes" to all questions
-c Check for bad blocks and add them to the badblock list
-f Force checking even if filesystem is marked clean
-v Be verbose
-b superblock Use alternative superblock
-B blocksize Force blocksize when looking for superblock
-j external_journal Set location of the external journal
-l bad_blocks_file Add to badblocks list
-L bad_blocks_file Set badblocks list
~ # e2fsck -y /dev/block/platform/msm_sdcc.1/by-name/persist
e2fsck 1.41.14 (22-Dec-2010)
/dev/block/platform/msm_sdcc.1/by-name/persist: recovering journal
Superblock needs_recovery flag is clear, but journal has data.
Run journal anyway? yes
e2fsck: unable to set superblock flags on /dev/block/platform/msm_sdcc.1/by-name
/persist
~ # cat /proc/partitions
major minor #blocks name
179 0 15388672 mmcblk0
179 1 65536 mmcblk0p1
179 2 1024 mmcblk0p2
179 3 512 mmcblk0p3
179 4 512 mmcblk0p4
179 5 512 mmcblk0p5
179 6 512 mmcblk0p6
179 7 2048 mmcblk0p7
179 8 1024 mmcblk0p8
179 9 512 mmcblk0p9
179 10 512 mmcblk0p10
179 11 512 mmcblk0p11
179 12 3072 mmcblk0p12
179 13 3072 mmcblk0p13
179 14 512 mmcblk0p14
179 15 16384 mmcblk0p15
179 16 16384 mmcblk0p16
179 17 3072 mmcblk0p17
179 18 22528 mmcblk0p18
179 19 22528 mmcblk0p19
179 20 22528 mmcblk0p20
179 21 3072 mmcblk0p21
179 22 512 mmcblk0p22
179 23 512 mmcblk0p23
179 24 512 mmcblk0p24
179 25 1048576 mmcblk0p25
179 26 30720 mmcblk0p26
179 27 716800 mmcblk0p27
179 28 13404138 mmcblk0p28
179 29 5 mmcblk0p29
179 32 4096 mmcblk0rpmb
~ # df
Filesystem 1K-blocks Used Available Use% Mounted on
tmpfs 949780 128 949652 0% /dev
tmpfs 949780 0 949780 0% /storage
tmpfs 949780 0 949780 0% /mnt/secure
tmpfs 949780 0 949780 0% /mnt/fuse
/dev/block/platform/msm_sdcc.1/by-name/system
1033516 1020920 12596 99% /system
~ #
C:\Program Files (x86)\WugFresh Development\Nexus Root Toolkit\data>fastboot dev
ices
034dd8de828dd06c fastboot
C:\Program Files (x86)\WugFresh Development\Nexus Root Toolkit\data>fastboot for
mat system
Creating filesystem with parameters:
Size: 1073741824
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 4096
Label:
Blocks: 262144
Block groups: 8
Reserved block group size: 63
Created filesystem with 11/65536 inodes and 8536/262144 blocks
target reported max download size of 1073741824 bytes
erasing 'system'...
OKAY [ 0.187s]
sending 'system' (18800 KB)...
OKAY [ 0.813s]
writing 'system'...
FAILED (remote: flash write failure)
finished. total time: 1.188s
C:\Program Files (x86)\WugFresh Development\Nexus Root Toolkit\data>fastboot for
mat cache
Creating filesystem with parameters:
Size: 734003200
Block size: 4096
Blocks per group: 32768
Inodes per group: 7472
Inode size: 256
Journal blocks: 2800
Label:
Blocks: 179200
Block groups: 6
Reserved block group size: 47
Created filesystem with 11/44832 inodes and 5813/179200 blocks
target reported max download size of 1073741824 bytes
erasing 'cache'...
FAILED (remote: failed to erase partition)
finished. total time: 0.219s
C:\Program Files (x86)\WugFresh Development\Nexus Root Toolkit\data>fastboot for
mat bootloader
Formatting is not supported for file system with type ''.
_______________________________________________________

Try the suggestion about relocking there bootloader and checking to see if it stays locked. If it doesn't stay locked, I would replace the motherboard.

When trying to delete partition 28, I get:
Error: Input/output error during write on /dev/block/mmcblk0
Anybody else got this and found a way to solve it?

audit13 said:
I assume the bootloader is unlocked since you are able to flash the boot.img. Try this: re-lock the bootloader, reboot to fastboot and see if the bootloader remains locked. If the bootloader unlocks itself, this is an indication that the memory chip is damaged. Also try flashing the older stock ROM available.
Click to expand...
Click to collapse
Thanks, I've been reading for quite some time looking for a solution to fix my Nexus 5 (I bought it brick just to fix it), and it does exactly what you mention here in your post. It recognize fastboot, it lock the bootloader but when the phone reboot, it display bootloader unlock. It doesn't let me flash the recovery img. by computer.
Thanks

The motherboard's flash memory is defective which means you'll need to replace the motherboard to have functional phone.

[Request] Nexus 6 Partition table

Some how I borked my Nexus 6 and lost my IEMI. Im working on restoring it but im having some issues. What I think happened is the partition that holds the IEMI got wiped. Can some one post their full partition table so I can compare and contrast. Im trying to avoid sending my phone to RMA
This is what I have
Device Partition List:
----------------------
modem /dev/block/mmcblk0p1
metadata /dev/block/mmcblk0p2
sbl1 /dev/block/mmcblk0p3
sdi /dev/block/mmcblk0p4
sec /dev/block/mmcblk0p5
ddr /dev/block/mmcblk0p6
aboot /dev/block/mmcblk0p7
rpm /dev/block/mmcblk0p8
utags /dev/block/mmcblk0p9
tz /dev/block/mmcblk0p10
pada /dev/block/mmcblk0p11
sbl1bak /dev/block/mmcblk0p12
abootbackup /dev/block/mmcblk0p13
rpmbackup /dev/block/mmcblk0p14
utagsbackup /dev/block/mmcblk0p15
tzbackup /dev/block/mmcblk0p16
versions /dev/block/mmcblk0p17
frp /dev/block/mmcblk0p18
mdm1m9kefs1 /dev/block/mmcblk0p19
mdm1m9kefs2 /dev/block/mmcblk0p20
mdm1m9kefs3 /dev/block/mmcblk0p21
padb /dev/block/mmcblk0p22
sp /dev/block/mmcblk0p23
keystore /dev/block/mmcblk0p24
logs /dev/block/mmcblk0p25
persist /dev/block/mmcblk0p26
mdm1hob /dev/block/mmcblk0p27
mdm1dhob /dev/block/mmcblk0p28
cid /dev/block/mmcblk0p29
logo /dev/block/mmcblk0p30
misc /dev/block/mmcblk0p31
padd /dev/block/mmcblk0p32
mdm1m9kefsc /dev/block/mmcblk0p33
ssd /dev/block/mmcblk0p34
recovery /dev/block/mmcblk0p35
kpan /dev/block/mmcblk0p36
boot /dev/block/mmcblk0p37
cache /dev/block/mmcblk0p38
oem /dev/block/mmcblk0p39
padc /dev/block/mmcblk0p40
system /dev/block/mmcblk0p41
userdata /dev/block/mmcblk0p42

Code:
[email protected]:/ $ su
[email protected]:/ # df
Filesystem Size Used Free Blksize
/dev 1.4G 48.0K 1.4G 4096
/sys/fs/cgroup 1.4G 12.0K 1.4G 4096
/mnt/asec 1.4G 0.0K 1.4G 4096
/mnt/obb 1.4G 0.0K 1.4G 4096
/system 1.9G 764.6M 1.2G 4096
/data 54.6G 39.6G 15.1G 4096
/cache 248.0M 192.0K 247.8M 4096
/firmware 106.2M 60.1M 46.1M 4096
/persist 928.0K 236.0K 692.0K 4096
/fsg 783.0K 779.0K 4.0K 1024
/mnt/shell/emulated 54.6G 39.6G 15.1G 4096
/storage/emulated 1.4G 0.0K 1.4G 4096
/storage/emulated/0 54.6G 39.6G 15.1G 4096
/storage/emulated/0/Android/obb 54.6G 39.6G 15.1G 4096
/storage/emulated/legacy 54.6G 39.6G 15.1G 4096
/storage/emulated/legacy/Android/obb 54.6G 39.6G 15.1G 4096
[email protected]:/ # cat /proc/partitions
major minor #blocks name
179 0 61071360 mmcblk0
179 1 114688 mmcblk0p1
179 2 16384 mmcblk0p2
179 3 384 mmcblk0p3
179 4 56 mmcblk0p4
179 5 16 mmcblk0p5
179 6 32 mmcblk0p6
179 7 1024 mmcblk0p7
179 8 256 mmcblk0p8
179 9 512 mmcblk0p9
179 10 500 mmcblk0p10
179 11 4156 mmcblk0p11
179 12 384 mmcblk0p12
179 13 1024 mmcblk0p13
179 14 256 mmcblk0p14
179 15 512 mmcblk0p15
179 16 500 mmcblk0p16
179 17 4 mmcblk0p17
179 18 512 mmcblk0p18
179 19 1024 mmcblk0p19
179 20 1024 mmcblk0p20
179 21 1024 mmcblk0p21
179 22 1024 mmcblk0p22
179 23 16384 mmcblk0p23
179 24 16384 mmcblk0p24
179 25 2048 mmcblk0p25
179 26 32768 mmcblk0p26
179 27 256 mmcblk0p27
179 28 32 mmcblk0p28
179 29 128 mmcblk0p29
179 30 8192 mmcblk0p30
179 31 1024 mmcblk0p31
259 0 2528 mmcblk0p32
259 1 1 mmcblk0p33
259 2 8 mmcblk0p34
259 3 16400 mmcblk0p35
259 4 9088 mmcblk0p36
259 5 16384 mmcblk0p37
259 6 262144 mmcblk0p38
259 7 65536 mmcblk0p39
259 8 1024 mmcblk0p40
259 9 2097152 mmcblk0p41
259 10 58343296 mmcblk0p42
179 32 4096 mmcblk0rpmb
[email protected]:/ # mount
rootfs / rootfs ro,seclabel,relatime 0 0
tmpfs /dev tmpfs rw,seclabel,nosuid,relatime,size=1503876k,nr_inodes=171088,mode=755 0 0
devpts /dev/pts devpts rw,seclabel,relatime,mode=600 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
adb /dev/usb-ffs/adb functionfs rw,relatime 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,seclabel,relatime 0 0
none /sys/fs/cgroup tmpfs rw,seclabel,relatime,size=1503876k,nr_inodes=171088,mode=750,gid=1000 0 0
pstore /sys/fs/pstore pstore rw,seclabel,relatime 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
tmpfs /mnt/asec tmpfs rw,seclabel,relatime,size=1503876k,nr_inodes=171088,mode=755,gid=1000 0 0
tmpfs /mnt/obb tmpfs rw,seclabel,relatime,size=1503876k,nr_inodes=171088,mode=755,gid=1000 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/userdata /data ext4 rw,seclabel,nosuid,nodev,noatime,nodiratime,nobarrier,noauto_da_alloc,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/cache /cache ext4 rw,seclabel,nosuid,nodev,noatime,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/modem /firmware ext4 ro,context=u:object_r:firmware_file:s0,relatime,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/persist /persist ext4 rw,seclabel,nosuid,nodev,relatime,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/mdm1m9kefs3 /fsg ext4 ro,context=u:object_r:fsg_file:s0,nosuid,nodev,relatime 0 0
/dev/fuse /mnt/shell/emulated fuse rw,nosuid,nodev,noexec,relatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
tmpfs /storage/emulated tmpfs rw,seclabel,nosuid,nodev,relatime,size=1503876k,nr_inodes=171088,mode=050,gid=1028 0 0
/dev/fuse /storage/emulated/0 fuse rw,nosuid,nodev,noexec,relatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
/dev/fuse /storage/emulated/0/Android/obb fuse rw,nosuid,nodev,noexec,relatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
/dev/fuse /storage/emulated/legacy fuse rw,nosuid,nodev,noexec,relatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
/dev/fuse /storage/emulated/legacy/Android/obb fuse rw,nosuid,nodev,noexec,relatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
1|[email protected]:/ # ls -l /dev/block/platform/msm_sdcc.1/by-name/
lrwxrwxrwx root root 1970-01-03 12:58 aboot -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 1970-01-03 12:58 abootBackup -> /dev/block/mmcblk0p13
lrwxrwxrwx root root 1970-01-03 12:58 boot -> /dev/block/mmcblk0p37
lrwxrwxrwx root root 1970-01-03 12:58 cache -> /dev/block/mmcblk0p38
lrwxrwxrwx root root 1970-01-03 12:58 cid -> /dev/block/mmcblk0p29
lrwxrwxrwx root root 1970-01-03 12:58 ddr -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 1970-01-03 12:58 frp -> /dev/block/mmcblk0p18
lrwxrwxrwx root root 1970-01-03 12:58 keystore -> /dev/block/mmcblk0p24
lrwxrwxrwx root root 1970-01-03 12:58 kpan -> /dev/block/mmcblk0p36
lrwxrwxrwx root root 1970-01-03 12:58 logo -> /dev/block/mmcblk0p30
lrwxrwxrwx root root 1970-01-03 12:58 logs -> /dev/block/mmcblk0p25
lrwxrwxrwx root root 1970-01-03 12:58 mdm1dhob -> /dev/block/mmcblk0p28
lrwxrwxrwx root root 1970-01-03 12:58 mdm1hob -> /dev/block/mmcblk0p27
lrwxrwxrwx root root 1970-01-03 12:58 mdm1m9kefs1 -> /dev/block/mmcblk0p19
lrwxrwxrwx root root 1970-01-03 12:58 mdm1m9kefs2 -> /dev/block/mmcblk0p20
lrwxrwxrwx root root 1970-01-03 12:58 mdm1m9kefs3 -> /dev/block/mmcblk0p21
lrwxrwxrwx root root 1970-01-03 12:58 mdm1m9kefsc -> /dev/block/mmcblk0p33
lrwxrwxrwx root root 1970-01-03 12:58 metadata -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 1970-01-03 12:58 misc -> /dev/block/mmcblk0p31
lrwxrwxrwx root root 1970-01-03 12:58 modem -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 1970-01-03 12:58 oem -> /dev/block/mmcblk0p39
lrwxrwxrwx root root 1970-01-03 12:58 padA -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 1970-01-03 12:58 padB -> /dev/block/mmcblk0p22
lrwxrwxrwx root root 1970-01-03 12:58 padC -> /dev/block/mmcblk0p40
lrwxrwxrwx root root 1970-01-03 12:58 padD -> /dev/block/mmcblk0p32
lrwxrwxrwx root root 1970-01-03 12:58 persist -> /dev/block/mmcblk0p26
lrwxrwxrwx root root 1970-01-03 12:58 recovery -> /dev/block/mmcblk0p35
lrwxrwxrwx root root 1970-01-03 12:58 rpm -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 1970-01-03 12:58 rpmBackup -> /dev/block/mmcblk0p14
lrwxrwxrwx root root 1970-01-03 12:58 sbl1 -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 1970-01-03 12:58 sbl1bak -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 1970-01-03 12:58 sdi -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 1970-01-03 12:58 sec -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 1970-01-03 12:58 sp -> /dev/block/mmcblk0p23
lrwxrwxrwx root root 1970-01-03 12:58 ssd -> /dev/block/mmcblk0p34
lrwxrwxrwx root root 1970-01-03 12:58 system -> /dev/block/mmcblk0p41
lrwxrwxrwx root root 1970-01-03 12:58 tz -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 1970-01-03 12:58 tzBackup -> /dev/block/mmcblk0p16
lrwxrwxrwx root root 1970-01-03 12:58 userdata -> /dev/block/mmcblk0p42
lrwxrwxrwx root root 1970-01-03 12:58 utags -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 1970-01-03 12:58 utagsBackup -> /dev/block/mmcblk0p15
lrwxrwxrwx root root 1970-01-03 12:58 versions -> /dev/block/mmcblk0p17

danarama said:
Code:
[email protected]:/ $ su
[email protected]:/ # df
Filesystem Size Used Free Blksize
/dev 1.4G 48.0K 1.4G 4096
/sys/fs/cgroup 1.4G 12.0K 1.4G 4096
/mnt/asec 1.4G 0.0K 1.4G 4096
/mnt/obb 1.4G 0.0K 1.4G 4096
/system 1.9G 764.6M 1.2G 4096
/data 54.6G 39.6G 15.1G 4096
/cache 248.0M 192.0K 247.8M 4096
/firmware 106.2M 60.1M 46.1M 4096
/persist 928.0K 236.0K 692.0K 4096
/fsg 783.0K 779.0K 4.0K 1024
/mnt/shell/emulated 54.6G 39.6G 15.1G 4096
/storage/emulated 1.4G 0.0K 1.4G 4096
/storage/emulated/0 54.6G 39.6G 15.1G 4096
/storage/emulated/0/Android/obb 54.6G 39.6G 15.1G 4096
/storage/emulated/legacy 54.6G 39.6G 15.1G 4096
/storage/emulated/legacy/Android/obb 54.6G 39.6G 15.1G 4096
[email protected]:/ # cat /proc/partitions
major minor #blocks name
179 0 61071360 mmcblk0
179 1 114688 mmcblk0p1
179 2 16384 mmcblk0p2
179 3 384 mmcblk0p3
179 4 56 mmcblk0p4
179 5 16 mmcblk0p5
179 6 32 mmcblk0p6
179 7 1024 mmcblk0p7
179 8 256 mmcblk0p8
179 9 512 mmcblk0p9
179 10 500 mmcblk0p10
179 11 4156 mmcblk0p11
179 12 384 mmcblk0p12
179 13 1024 mmcblk0p13
179 14 256 mmcblk0p14
179 15 512 mmcblk0p15
179 16 500 mmcblk0p16
179 17 4 mmcblk0p17
179 18 512 mmcblk0p18
179 19 1024 mmcblk0p19
179 20 1024 mmcblk0p20
179 21 1024 mmcblk0p21
179 22 1024 mmcblk0p22
179 23 16384 mmcblk0p23
179 24 16384 mmcblk0p24
179 25 2048 mmcblk0p25
179 26 32768 mmcblk0p26
179 27 256 mmcblk0p27
179 28 32 mmcblk0p28
179 29 128 mmcblk0p29
179 30 8192 mmcblk0p30
179 31 1024 mmcblk0p31
259 0 2528 mmcblk0p32
259 1 1 mmcblk0p33
259 2 8 mmcblk0p34
259 3 16400 mmcblk0p35
259 4 9088 mmcblk0p36
259 5 16384 mmcblk0p37
259 6 262144 mmcblk0p38
259 7 65536 mmcblk0p39
259 8 1024 mmcblk0p40
259 9 2097152 mmcblk0p41
259 10 58343296 mmcblk0p42
179 32 4096 mmcblk0rpmb
[email protected]:/ # mount
rootfs / rootfs ro,seclabel,relatime 0 0
tmpfs /dev tmpfs rw,seclabel,nosuid,relatime,size=1503876k,nr_inodes=171088,mode=755 0 0
devpts /dev/pts devpts rw,seclabel,relatime,mode=600 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
adb /dev/usb-ffs/adb functionfs rw,relatime 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,seclabel,relatime 0 0
none /sys/fs/cgroup tmpfs rw,seclabel,relatime,size=1503876k,nr_inodes=171088,mode=750,gid=1000 0 0
pstore /sys/fs/pstore pstore rw,seclabel,relatime 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
tmpfs /mnt/asec tmpfs rw,seclabel,relatime,size=1503876k,nr_inodes=171088,mode=755,gid=1000 0 0
tmpfs /mnt/obb tmpfs rw,seclabel,relatime,size=1503876k,nr_inodes=171088,mode=755,gid=1000 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/userdata /data ext4 rw,seclabel,nosuid,nodev,noatime,nodiratime,nobarrier,noauto_da_alloc,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/cache /cache ext4 rw,seclabel,nosuid,nodev,noatime,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/modem /firmware ext4 ro,context=u:object_r:firmware_file:s0,relatime,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/persist /persist ext4 rw,seclabel,nosuid,nodev,relatime,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/mdm1m9kefs3 /fsg ext4 ro,context=u:object_r:fsg_file:s0,nosuid,nodev,relatime 0 0
/dev/fuse /mnt/shell/emulated fuse rw,nosuid,nodev,noexec,relatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
tmpfs /storage/emulated tmpfs rw,seclabel,nosuid,nodev,relatime,size=1503876k,nr_inodes=171088,mode=050,gid=1028 0 0
/dev/fuse /storage/emulated/0 fuse rw,nosuid,nodev,noexec,relatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
/dev/fuse /storage/emulated/0/Android/obb fuse rw,nosuid,nodev,noexec,relatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
/dev/fuse /storage/emulated/legacy fuse rw,nosuid,nodev,noexec,relatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
/dev/fuse /storage/emulated/legacy/Android/obb fuse rw,nosuid,nodev,noexec,relatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
1|[email protected]:/ # ls -l /dev/block/platform/msm_sdcc.1/by-name/
lrwxrwxrwx root root 1970-01-03 12:58 aboot -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 1970-01-03 12:58 abootBackup -> /dev/block/mmcblk0p13
lrwxrwxrwx root root 1970-01-03 12:58 boot -> /dev/block/mmcblk0p37
lrwxrwxrwx root root 1970-01-03 12:58 cache -> /dev/block/mmcblk0p38
lrwxrwxrwx root root 1970-01-03 12:58 cid -> /dev/block/mmcblk0p29
lrwxrwxrwx root root 1970-01-03 12:58 ddr -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 1970-01-03 12:58 frp -> /dev/block/mmcblk0p18
lrwxrwxrwx root root 1970-01-03 12:58 keystore -> /dev/block/mmcblk0p24
lrwxrwxrwx root root 1970-01-03 12:58 kpan -> /dev/block/mmcblk0p36
lrwxrwxrwx root root 1970-01-03 12:58 logo -> /dev/block/mmcblk0p30
lrwxrwxrwx root root 1970-01-03 12:58 logs -> /dev/block/mmcblk0p25
lrwxrwxrwx root root 1970-01-03 12:58 mdm1dhob -> /dev/block/mmcblk0p28
lrwxrwxrwx root root 1970-01-03 12:58 mdm1hob -> /dev/block/mmcblk0p27
lrwxrwxrwx root root 1970-01-03 12:58 mdm1m9kefs1 -> /dev/block/mmcblk0p19
lrwxrwxrwx root root 1970-01-03 12:58 mdm1m9kefs2 -> /dev/block/mmcblk0p20
lrwxrwxrwx root root 1970-01-03 12:58 mdm1m9kefs3 -> /dev/block/mmcblk0p21
lrwxrwxrwx root root 1970-01-03 12:58 mdm1m9kefsc -> /dev/block/mmcblk0p33
lrwxrwxrwx root root 1970-01-03 12:58 metadata -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 1970-01-03 12:58 misc -> /dev/block/mmcblk0p31
lrwxrwxrwx root root 1970-01-03 12:58 modem -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 1970-01-03 12:58 oem -> /dev/block/mmcblk0p39
lrwxrwxrwx root root 1970-01-03 12:58 padA -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 1970-01-03 12:58 padB -> /dev/block/mmcblk0p22
lrwxrwxrwx root root 1970-01-03 12:58 padC -> /dev/block/mmcblk0p40
lrwxrwxrwx root root 1970-01-03 12:58 padD -> /dev/block/mmcblk0p32
lrwxrwxrwx root root 1970-01-03 12:58 persist -> /dev/block/mmcblk0p26
lrwxrwxrwx root root 1970-01-03 12:58 recovery -> /dev/block/mmcblk0p35
lrwxrwxrwx root root 1970-01-03 12:58 rpm -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 1970-01-03 12:58 rpmBackup -> /dev/block/mmcblk0p14
lrwxrwxrwx root root 1970-01-03 12:58 sbl1 -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 1970-01-03 12:58 sbl1bak -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 1970-01-03 12:58 sdi -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 1970-01-03 12:58 sec -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 1970-01-03 12:58 sp -> /dev/block/mmcblk0p23
lrwxrwxrwx root root 1970-01-03 12:58 ssd -> /dev/block/mmcblk0p34
lrwxrwxrwx root root 1970-01-03 12:58 system -> /dev/block/mmcblk0p41
lrwxrwxrwx root root 1970-01-03 12:58 tz -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 1970-01-03 12:58 tzBackup -> /dev/block/mmcblk0p16
lrwxrwxrwx root root 1970-01-03 12:58 userdata -> /dev/block/mmcblk0p42
lrwxrwxrwx root root 1970-01-03 12:58 utags -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 1970-01-03 12:58 utagsBackup -> /dev/block/mmcblk0p15
lrwxrwxrwx root root 1970-01-03 12:58 versions -> /dev/block/mmcblk0p17
Click to expand...
Click to collapse
Thanks! But this still sucks, according to your layout I have all the partitions and the correct permissions, yet when i try to write the IMEI back I get an error using efs professional, and QXDM just sits there. Something is fishy

zikronix said:
Thanks! But this still sucks, according to your layout I have all the partitions and the correct permissions, yet when i try to write the IMEI back I get an error using efs professional, and QXDM just sits there. Something is fishy
Click to expand...
Click to collapse
Dunno. Can't help you. We're not to discuss methods of writing imei's on this forum.

danarama said:
Dunno. Can't help you. We're not to discuss methods of writing imei's on this forum.
Click to expand...
Click to collapse
yes I am aware. so thats why im on my own. I found the repair threads. but thank you very much for the part tables!

danarama said:
Code:
[email protected]:/ $ su
[email protected]:/ # df
Filesystem Size Used Free Blksize
/dev 1.4G 48.0K 1.4G 4096
/sys/fs/cgroup 1.4G 12.0K 1.4G 4096
/mnt/asec 1.4G 0.0K 1.4G 4096
/mnt/obb 1.4G 0.0K 1.4G 4096
/system 1.9G 764.6M 1.2G 4096
/data 54.6G 39.6G 15.1G 4096
/cache 248.0M 192.0K 247.8M 4096
/firmware 106.2M 60.1M 46.1M 4096
/persist 928.0K 236.0K 692.0K 4096
/fsg 783.0K 779.0K 4.0K 1024
/mnt/shell/emulated 54.6G 39.6G 15.1G 4096
/storage/emulated 1.4G 0.0K 1.4G 4096
/storage/emulated/0 54.6G 39.6G 15.1G 4096
/storage/emulated/0/Android/obb 54.6G 39.6G 15.1G 4096
/storage/emulated/legacy 54.6G 39.6G 15.1G 4096
/storage/emulated/legacy/Android/obb 54.6G 39.6G 15.1G 4096
[email protected]:/ # cat /proc/partitions
major minor #blocks name
179 0 61071360 mmcblk0
179 1 114688 mmcblk0p1
179 2 16384 mmcblk0p2
179 3 384 mmcblk0p3
179 4 56 mmcblk0p4
179 5 16 mmcblk0p5
179 6 32 mmcblk0p6
179 7 1024 mmcblk0p7
179 8 256 mmcblk0p8
179 9 512 mmcblk0p9
179 10 500 mmcblk0p10
179 11 4156 mmcblk0p11
179 12 384 mmcblk0p12
179 13 1024 mmcblk0p13
179 14 256 mmcblk0p14
179 15 512 mmcblk0p15
179 16 500 mmcblk0p16
179 17 4 mmcblk0p17
179 18 512 mmcblk0p18
179 19 1024 mmcblk0p19
179 20 1024 mmcblk0p20
179 21 1024 mmcblk0p21
179 22 1024 mmcblk0p22
179 23 16384 mmcblk0p23
179 24 16384 mmcblk0p24
179 25 2048 mmcblk0p25
179 26 32768 mmcblk0p26
179 27 256 mmcblk0p27
179 28 32 mmcblk0p28
179 29 128 mmcblk0p29
179 30 8192 mmcblk0p30
179 31 1024 mmcblk0p31
259 0 2528 mmcblk0p32
259 1 1 mmcblk0p33
259 2 8 mmcblk0p34
259 3 16400 mmcblk0p35
259 4 9088 mmcblk0p36
259 5 16384 mmcblk0p37
259 6 262144 mmcblk0p38
259 7 65536 mmcblk0p39
259 8 1024 mmcblk0p40
259 9 2097152 mmcblk0p41
259 10 58343296 mmcblk0p42
179 32 4096 mmcblk0rpmb
[email protected]:/ # mount
rootfs / rootfs ro,seclabel,relatime 0 0
tmpfs /dev tmpfs rw,seclabel,nosuid,relatime,size=1503876k,nr_inodes=171088,mode=755 0 0
devpts /dev/pts devpts rw,seclabel,relatime,mode=600 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
adb /dev/usb-ffs/adb functionfs rw,relatime 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,seclabel,relatime 0 0
none /sys/fs/cgroup tmpfs rw,seclabel,relatime,size=1503876k,nr_inodes=171088,mode=750,gid=1000 0 0
pstore /sys/fs/pstore pstore rw,seclabel,relatime 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
tmpfs /mnt/asec tmpfs rw,seclabel,relatime,size=1503876k,nr_inodes=171088,mode=755,gid=1000 0 0
tmpfs /mnt/obb tmpfs rw,seclabel,relatime,size=1503876k,nr_inodes=171088,mode=755,gid=1000 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/userdata /data ext4 rw,seclabel,nosuid,nodev,noatime,nodiratime,nobarrier,noauto_da_alloc,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/cache /cache ext4 rw,seclabel,nosuid,nodev,noatime,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/modem /firmware ext4 ro,context=u:object_r:firmware_file:s0,relatime,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/persist /persist ext4 rw,seclabel,nosuid,nodev,relatime,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/mdm1m9kefs3 /fsg ext4 ro,context=u:object_r:fsg_file:s0,nosuid,nodev,relatime 0 0
/dev/fuse /mnt/shell/emulated fuse rw,nosuid,nodev,noexec,relatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
tmpfs /storage/emulated tmpfs rw,seclabel,nosuid,nodev,relatime,size=1503876k,nr_inodes=171088,mode=050,gid=1028 0 0
/dev/fuse /storage/emulated/0 fuse rw,nosuid,nodev,noexec,relatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
/dev/fuse /storage/emulated/0/Android/obb fuse rw,nosuid,nodev,noexec,relatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
/dev/fuse /storage/emulated/legacy fuse rw,nosuid,nodev,noexec,relatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
/dev/fuse /storage/emulated/legacy/Android/obb fuse rw,nosuid,nodev,noexec,relatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
1|[email protected]:/ # ls -l /dev/block/platform/msm_sdcc.1/by-name/
lrwxrwxrwx root root 1970-01-03 12:58 aboot -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 1970-01-03 12:58 abootBackup -> /dev/block/mmcblk0p13
lrwxrwxrwx root root 1970-01-03 12:58 boot -> /dev/block/mmcblk0p37
lrwxrwxrwx root root 1970-01-03 12:58 cache -> /dev/block/mmcblk0p38
lrwxrwxrwx root root 1970-01-03 12:58 cid -> /dev/block/mmcblk0p29
lrwxrwxrwx root root 1970-01-03 12:58 ddr -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 1970-01-03 12:58 frp -> /dev/block/mmcblk0p18
lrwxrwxrwx root root 1970-01-03 12:58 keystore -> /dev/block/mmcblk0p24
lrwxrwxrwx root root 1970-01-03 12:58 kpan -> /dev/block/mmcblk0p36
lrwxrwxrwx root root 1970-01-03 12:58 logo -> /dev/block/mmcblk0p30
lrwxrwxrwx root root 1970-01-03 12:58 logs -> /dev/block/mmcblk0p25
lrwxrwxrwx root root 1970-01-03 12:58 mdm1dhob -> /dev/block/mmcblk0p28
lrwxrwxrwx root root 1970-01-03 12:58 mdm1hob -> /dev/block/mmcblk0p27
lrwxrwxrwx root root 1970-01-03 12:58 mdm1m9kefs1 -> /dev/block/mmcblk0p19
lrwxrwxrwx root root 1970-01-03 12:58 mdm1m9kefs2 -> /dev/block/mmcblk0p20
lrwxrwxrwx root root 1970-01-03 12:58 mdm1m9kefs3 -> /dev/block/mmcblk0p21
lrwxrwxrwx root root 1970-01-03 12:58 mdm1m9kefsc -> /dev/block/mmcblk0p33
lrwxrwxrwx root root 1970-01-03 12:58 metadata -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 1970-01-03 12:58 misc -> /dev/block/mmcblk0p31
lrwxrwxrwx root root 1970-01-03 12:58 modem -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 1970-01-03 12:58 oem -> /dev/block/mmcblk0p39
lrwxrwxrwx root root 1970-01-03 12:58 padA -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 1970-01-03 12:58 padB -> /dev/block/mmcblk0p22
lrwxrwxrwx root root 1970-01-03 12:58 padC -> /dev/block/mmcblk0p40
lrwxrwxrwx root root 1970-01-03 12:58 padD -> /dev/block/mmcblk0p32
lrwxrwxrwx root root 1970-01-03 12:58 persist -> /dev/block/mmcblk0p26
lrwxrwxrwx root root 1970-01-03 12:58 recovery -> /dev/block/mmcblk0p35
lrwxrwxrwx root root 1970-01-03 12:58 rpm -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 1970-01-03 12:58 rpmBackup -> /dev/block/mmcblk0p14
lrwxrwxrwx root root 1970-01-03 12:58 sbl1 -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 1970-01-03 12:58 sbl1bak -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 1970-01-03 12:58 sdi -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 1970-01-03 12:58 sec -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 1970-01-03 12:58 sp -> /dev/block/mmcblk0p23
lrwxrwxrwx root root 1970-01-03 12:58 ssd -> /dev/block/mmcblk0p34
lrwxrwxrwx root root 1970-01-03 12:58 system -> /dev/block/mmcblk0p41
lrwxrwxrwx root root 1970-01-03 12:58 tz -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 1970-01-03 12:58 tzBackup -> /dev/block/mmcblk0p16
lrwxrwxrwx root root 1970-01-03 12:58 userdata -> /dev/block/mmcblk0p42
lrwxrwxrwx root root 1970-01-03 12:58 utags -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 1970-01-03 12:58 utagsBackup -> /dev/block/mmcblk0p15
lrwxrwxrwx root root 1970-01-03 12:58 versions -> /dev/block/mmcblk0p17
Click to expand...
Click to collapse
I have some problems with my phone and I believe that it is a software issue (I tried to ask for help in this thread http://forum.xda-developers.com/nexus-6/help/strange-device-behavior-believe-t3159186 but without a luck. I have even send it to the service but as nexus are not selling in my country they couldn't repair it.). I was thinking that there is some problem in partitions. Bellow you can see output of the commands on my phone. There are some differencies but I believe that they are because you have unencripted internal memory. What is the most strange to me is a persist partition which is 30MB on my phone and it is using just 52kB. Can you please help me to repair it.
Code:
[email protected]:/ $ su
[email protected]:/ # df
Filesystem Size Used Free Blksize
/dev 1.4G 64.0K 1.4G 4096
/sys/fs/cgroup 1.4G 12.0K 1.4G 4096
/mnt 1.4G 0.0K 1.4G 4096
/mnt/runtime/default/emulated 26.0G 4.6G 21.4G 4096
/mnt/runtime/read/emulated 26.0G 4.6G 21.4G 4096
/mnt/runtime/write/emulated 26.0G 4.6G 21.4G 4096
/system 1.9G 1.9G 16.1M 4096
/cache 248.0M 200.0K 247.8M 4096
/firmware 106.2M 60.1M 46.1M 4096
/persist 30.0M 52.0K 29.9M 1024
/fsg 784.0K 780.0K 4.0K 1024
/storage 1.4G 0.0K 1.4G 4096
/storage/emulated 26.0G 4.6G 21.4G 4096
/data 26.0G 4.6G 21.4G 4096
[email protected]:/ # cat /proc/partitions
major minor #blocks name
179 0 30535680 mmcblk0
179 1 114688 mmcblk0p1
179 2 16384 mmcblk0p2
179 3 384 mmcblk0p3
179 4 56 mmcblk0p4
179 5 16 mmcblk0p5
179 6 32 mmcblk0p6
179 7 1024 mmcblk0p7
179 8 256 mmcblk0p8
179 9 512 mmcblk0p9
179 10 500 mmcblk0p10
179 11 4156 mmcblk0p11
179 12 384 mmcblk0p12
179 13 1024 mmcblk0p13
179 14 256 mmcblk0p14
179 15 512 mmcblk0p15
179 16 500 mmcblk0p16
179 17 4 mmcblk0p17
179 18 512 mmcblk0p18
179 19 1024 mmcblk0p19
179 20 1024 mmcblk0p20
179 21 1024 mmcblk0p21
179 22 1024 mmcblk0p22
179 23 16384 mmcblk0p23
179 24 16384 mmcblk0p24
179 25 2048 mmcblk0p25
179 26 32768 mmcblk0p26
179 27 256 mmcblk0p27
179 28 32 mmcblk0p28
179 29 128 mmcblk0p29
179 30 8192 mmcblk0p30
179 31 1024 mmcblk0p31
259 0 2528 mmcblk0p32
259 1 1 mmcblk0p33
259 2 8 mmcblk0p34
259 3 16400 mmcblk0p35
259 4 9088 mmcblk0p36
259 5 16384 mmcblk0p37
259 6 262144 mmcblk0p38
259 7 65536 mmcblk0p39
259 8 1024 mmcblk0p40
259 9 2097152 mmcblk0p41
259 10 27840495 mmcblk0p42
179 32 4096 mmcblk0rpmb
254 0 27840495 dm-0
[email protected]:/ # mount
rootfs / rootfs ro,seclabel,relatime 0 0
tmpfs /dev tmpfs rw,seclabel,nosuid,relatime,size=1503692k,nr_inodes=170997,mode=755 0 0
devpts /dev/pts devpts rw,seclabel,relatime,mode=600 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
adb /dev/usb-ffs/adb functionfs rw,relatime 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,seclabel,relatime 0 0
none /sys/fs/cgroup tmpfs rw,seclabel,relatime,size=1503692k,nr_inodes=170997,mode=750,gid=1000 0 0
pstore /sys/fs/pstore pstore rw,seclabel,relatime 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
tmpfs /mnt tmpfs rw,seclabel,relatime,size=1503692k,nr_inodes=170997,mode=755,gid=1000 0 0
/dev/fuse /mnt/runtime/default/emulated fuse rw,nosuid,nodev,noexec,noatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
/dev/fuse /mnt/runtime/read/emulated fuse rw,nosuid,nodev,noexec,noatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
/dev/fuse /mnt/runtime/write/emulated fuse rw,nosuid,nodev,noexec,noatime,user_id=1023,group_id=1023,default_permissions,allow_other 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,nodev,noatime,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/modem /firmware ext4 ro,context=u:object_r:firmware_file:s0,relatime,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/persist /persist ext4 rw,seclabel,nosuid,nodev,relatime 0 0
/dev/block/platform/msm_sdcc.1/by-name/mdm1m9kefs3 /fsg ext4 ro,context=u:object_r:fsg_file:s0,nosuid,nodev,relatime 0 0
tmpfs /storage tmpfs rw,seclabel,relatime,size=1503692k,nr_inodes=170997,mode=755,gid=1000 0 0
/dev/fuse /storage/emulated fuse rw,nosuid,nodev,noexec,noatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
/dev/block/dm-0 /data ext4 rw,seclabel,nosuid,nodev,noatime,nodiratime,nobarrier,noauto_da_alloc,data=ordered 0 0
[email protected]:/ # ls -l /dev/block/platform/msm_sdcc.1/by-name/
lrwxrwxrwx root root 1970-01-01 15:11 aboot -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 1970-01-01 15:11 abootBackup -> /dev/block/mmcblk0p13
lrwxrwxrwx root root 1970-01-01 15:11 boot -> /dev/block/mmcblk0p37
lrwxrwxrwx root root 1970-01-01 15:11 cache -> /dev/block/mmcblk0p38
lrwxrwxrwx root root 1970-01-01 15:11 cid -> /dev/block/mmcblk0p29
lrwxrwxrwx root root 1970-01-01 15:11 ddr -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 1970-01-01 15:11 frp -> /dev/block/mmcblk0p18
lrwxrwxrwx root root 1970-01-01 15:11 keystore -> /dev/block/mmcblk0p24
lrwxrwxrwx root root 1970-01-01 15:11 kpan -> /dev/block/mmcblk0p36
lrwxrwxrwx root root 1970-01-01 15:11 logo -> /dev/block/mmcblk0p30
lrwxrwxrwx root root 1970-01-01 15:11 logs -> /dev/block/mmcblk0p25
lrwxrwxrwx root root 1970-01-01 15:11 mdm1dhob -> /dev/block/mmcblk0p28
lrwxrwxrwx root root 1970-01-01 15:11 mdm1hob -> /dev/block/mmcblk0p27
lrwxrwxrwx root root 1970-01-01 15:11 mdm1m9kefs1 -> /dev/block/mmcblk0p19
lrwxrwxrwx root root 1970-01-01 15:11 mdm1m9kefs2 -> /dev/block/mmcblk0p20
lrwxrwxrwx root root 1970-01-01 15:11 mdm1m9kefs3 -> /dev/block/mmcblk0p21
lrwxrwxrwx root root 1970-01-01 15:11 mdm1m9kefsc -> /dev/block/mmcblk0p33
lrwxrwxrwx root root 1970-01-01 15:11 metadata -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 1970-01-01 15:11 misc -> /dev/block/mmcblk0p31
lrwxrwxrwx root root 1970-01-01 15:11 modem -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 1970-01-01 15:11 oem -> /dev/block/mmcblk0p39
lrwxrwxrwx root root 1970-01-01 15:11 padA -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 1970-01-01 15:11 padB -> /dev/block/mmcblk0p22
lrwxrwxrwx root root 1970-01-01 15:11 padC -> /dev/block/mmcblk0p40
lrwxrwxrwx root root 1970-01-01 15:11 padD -> /dev/block/mmcblk0p32
lrwxrwxrwx root root 1970-01-01 15:11 persist -> /dev/block/mmcblk0p26
lrwxrwxrwx root root 1970-01-01 15:11 recovery -> /dev/block/mmcblk0p35
lrwxrwxrwx root root 1970-01-01 15:11 rpm -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 1970-01-01 15:11 rpmBackup -> /dev/block/mmcblk0p14
lrwxrwxrwx root root 1970-01-01 15:11 sbl1 -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 1970-01-01 15:11 sbl1bak -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 1970-01-01 15:11 sdi -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 1970-01-01 15:11 sec -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 1970-01-01 15:11 sp -> /dev/block/mmcblk0p23
lrwxrwxrwx root root 1970-01-01 15:11 ssd -> /dev/block/mmcblk0p34
lrwxrwxrwx root root 1970-01-01 15:11 system -> /dev/block/mmcblk0p41
lrwxrwxrwx root root 1970-01-01 15:11 tz -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 1970-01-01 15:11 tzBackup -> /dev/block/mmcblk0p16
lrwxrwxrwx root root 1970-01-01 15:11 userdata -> /dev/block/mmcblk0p42
lrwxrwxrwx root root 1970-01-01 15:11 utags -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 1970-01-01 15:11 utagsBackup -> /dev/block/mmcblk0p15
lrwxrwxrwx root root 1970-01-01 15:11 versions -> /dev/block/mmcblk0p17
[email protected]:/#

[ROOT] SM-S975L (Straight Talk variant) - OF4 FIRMWARE!

OF4 Firmware root!
Obtained by Team D3mons
Savage says Hi. Love LoopyD.
We've (or I've) obtained root on the Samsung Galaxy S4 Straight Talk variant OF4 firmware, which was thought not possible due to new Knox security updates preventing even the installation of a kernel. Here's my screenshots.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Original dev thread where I was editing and tinkering.
http://forum.xda-developers.com/galaxy-s4/devs-only/s975l-tricking-knox-flash-t3279741
This was done by a hex edit hack available in Odin flashable form heree -> OneDrive link. Flash with Odin 3.07.
(My folder is a mess, do let me know if I uploaded the right one).
This Odin flash will flash to NB1 kernel hex-edit disguised as OF4, so the flash does not fai from download model, then apply towelroot I succeeded with its generic mod strings. Tap 3 times on towelroot to enable them, then simply press "Make it ra1n".
TWRP that works on this phone I haven't tested yet, but appearently jfttmo works.
Thanks:
Geohot, Chainfire, SAMMobile, and me! (Press Thanks when and if it worked and buy me a pop )
Disclaimer: This trips Knox. Your warranty is now void (who cares, it's Straight Talk!) I'll see if Triangle Away I can make work once I get the money, I'll see about applying a lucky patch or something to get it to force-do our phone. Hopefully without a brick. But SuperSU will disable the KNOX notifications and security check.
Original dev thread where I was editing and tinkering:
http://forum.xda-developers.com/galaxy-s4/devs-only/s975l-tricking-knox-flash-t3279741
Dev links:
Developer files:
PIT File for OF4
Vold.fstab for OF4
Dev important information
Code:
SM-S975L OF4 FIRMWARE MOUNT LOCATIONS AND ATTRIBUTES
[email protected]:/ # cat /proc/mounts
---------------------------------------------
rootfs / rootfs ro,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
none /dev/cpuctl cgroup rw,relatime,cpu 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
/sys/kernel/debug /sys/kernel/debug debugfs rw,relatime 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
tmpfs /mnt/secure tmpfs rw,seclabel,relatime,mode=700 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
/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/userdata /data ext4 rw,seclabel,nosuid,nodev,noatime,discard,journal_checksum,journal_async_commit,noauto_da_alloc,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/cache /cache ext4 rw,seclabel,nosuid,nodev,noatime,discard,journal_checksum,journal_async_commit,noauto_da_alloc,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/apnhlos /firmware vfat ro,relatime,uid=1000,gid=1000,fmask=0337,dmask=0227,codepage=cp437,iocharset=iso8859-1,shortname=lower,errors=remount-ro 0 0
/dev/block/platform/msm_sdcc.1/by-name/mdm /firmware-mdm vfat ro,relatime,uid=1000,gid=1000,fmask=0337,dmask=0227,codepage=cp437,iocharset=iso8859-1,shortname=lower,errors=remount-ro 0 0
/dev/block/platform/msm_sdcc.1/by-name/efs /efs ext4 rw,seclabel,nosuid,nodev,noatime,discard,journal_checksum,journal_async_commit,noauto_da_alloc,errors=panic,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/persdata /persdata/absolute ext4 rw,seclabel,nosuid,nodev,relatime,data=ordered 0 0
/data/container /mnt/shell/container sdcardfs rw,nosuid,nodev,relatime,uid=1000,gid=1000 0 0
/data/media /mnt/shell/emulated sdcardfs rw,nosuid,nodev,relatime,uid=1023,gid=1023 0 0
tmpfs /storage/emulated tmpfs rw,seclabel,nosuid,nodev,relatime,mode=050,gid=1028 0 0
/dev/block/vold/179:33 /storage/extSdCard vfat rw,dirsync,nosuid,nodev,noexec,noatime,nodiratime,uid=1000,gid=1023,fmask=0002,dmask=0002,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
tmpfs /storage/extSdCard/.android_secure tmpfs ro,seclabel,relatime,size=0k,mode=000 0 0
/data/media /storage/emulated/0 sdcardfs rw,nosuid,nodev,relatime,uid=1023,gid=1023 0 0
/data/media /storage/emulated/0/Android/obb sdcardfs rw,nosuid,nodev,relatime,uid=1023,gid=1023 0 0
/data/media /storage/emulated/legacy sdcardfs rw,nosuid,nodev,relatime,uid=1023,gid=1023 0 0
/data/media /storage/emulated/legacy/Android/obb sdcardfs rw,nosuid,nodev,relatime,uid=1023,gid=1023 0 0
---------------------------------------------
SM-S975L OF4 FIRMARE PARTITION LIST FOR CHECK AND IDENTIFICATION
[email protected]:/ # cat /proc/partitions
major minor #blocks name
253 0 512000 zram0
179 0 15388672 mmcblk0
179 1 12772 mmcblk0p1
179 2 52764 mmcblk0p2
179 3 128 mmcblk0p3
179 4 256 mmcblk0p4
179 5 512 mmcblk0p5
179 6 2048 mmcblk0p6
179 7 512 mmcblk0p7
179 8 512 mmcblk0p8
179 9 16896 mmcblk0p9
179 10 13952 mmcblk0p10
179 11 3072 mmcblk0p11
179 12 3072 mmcblk0p12
179 13 780 mmcblk0p13
179 14 780 mmcblk0p14
179 15 780 mmcblk0p15
179 16 2826240 mmcblk0p16
179 17 8192 mmcblk0p17
179 18 2119680 mmcblk0p18
179 19 6144 mmcblk0p19
179 20 10240 mmcblk0p20
179 21 10240 mmcblk0p21
179 22 10240 mmcblk0p22
179 23 6144 mmcblk0p23
179 24 3072 mmcblk0p24
179 25 8 mmcblk0p25
179 26 9216 mmcblk0p26
179 27 20480 mmcblk0p27
179 28 20480 mmcblk0p28
179 29 10219520 mmcblk0p29
179 32 1943552 mmcblk1
179 33 1942528 mmcblk1p1
---------------------------------------------
SM-S975L OF4 FIRMWARE MOUNT BLOCK POINTS (SYSTEM)
[email protected]:/ # ls -l /dev/block/platform/msm_sdcc.1/by-name/
---------------------------------------------
lrwxrwxrwx root root 1970-04-30 23:54 aboot -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 1970-04-30 23:54 apnhlos -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 1970-04-30 23:54 backup -> /dev/block/mmcblk0p23
lrwxrwxrwx root root 1970-04-30 23:54 boot -> /dev/block/mmcblk0p20
lrwxrwxrwx root root 1970-04-30 23:54 cache -> /dev/block/mmcblk0p18
lrwxrwxrwx root root 1970-04-30 23:54 carrier -> /dev/block/mmcblk0p28
lrwxrwxrwx root root 1970-04-30 23:54 efs -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 1970-04-30 23:54 fota -> /dev/block/mmcblk0p22
lrwxrwxrwx root root 1970-04-30 23:54 fsg -> /dev/block/mmcblk0p24
lrwxrwxrwx root root 1970-04-30 23:54 hidden -> /dev/block/mmcblk0p27
lrwxrwxrwx root root 1970-04-30 23:54 m9kefs1 -> /dev/block/mmcblk0p13
lrwxrwxrwx root root 1970-04-30 23:54 m9kefs2 -> /dev/block/mmcblk0p14
lrwxrwxrwx root root 1970-04-30 23:54 m9kefs3 -> /dev/block/mmcblk0p15
lrwxrwxrwx root root 1970-04-30 23:54 mdm -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 1970-04-30 23:54 modemst1 -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 1970-04-30 23:54 modemst2 -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 1970-04-30 23:54 pad -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 1970-04-30 23:54 param -> /dev/block/mmcblk0p19
lrwxrwxrwx root root 1970-04-30 23:54 persdata -> /dev/block/mmcblk0p26
lrwxrwxrwx root root 1970-04-30 23:54 persist -> /dev/block/mmcblk0p17
lrwxrwxrwx root root 1970-04-30 23:54 recovery -> /dev/block/mmcblk0p21
lrwxrwxrwx root root 1970-04-30 23:54 rpm -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 1970-04-30 23:54 sbl1 -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 1970-04-30 23:54 sbl2 -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 1970-04-30 23:54 sbl3 -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 1970-04-30 23:54 ssd -> /dev/block/mmcblk0p25
lrwxrwxrwx root root 1970-04-30 23:54 system -> /dev/block/mmcblk0p16
lrwxrwxrwx root root 1970-04-30 23:54 tz -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 1970-04-30 23:54 userdata -> /dev/block/mmcblk0p2
---------------------------------------------
I hope all this helps. More info available upon request. I'll pull as much as needed for a cyanogen or autoroot build, since towelroot works. I don't have a linux system nor can spend the time building. I have school.

Update: Added PIT file for flashing and fstab for the devs. + Partition information

LupineDream said:
Update: Added PIT file for flashing and fstab for the devs. + Partition information
Click to expand...
Click to collapse
I've got a galaxy s4 at&t variant which has been on nb1 for the longest time. From what I'm getting this method doesn't flash a new aboot? Can this method be used to flash the rom from the nexus version of the s4?

SM-S975L OF4 to custom recovery and rom:
http://forum.xda-developers.com/showpost.php?p=64604828&postcount=98

I've really been wanting to root this phone for a while now. Great work! I'd really like to try this but I'm having some trouble understanding some of your technical terms. Could you maybe dumb it down for me?.. I understand meaning behind flashing software but I'm not familiar with Oden and you lost me completely at mod strings..

this needs a sticky its simple great work thank YOU

Sorry but does anybody have a copy of the pit file the link is dead

LupineDream said:
OF4 Firmware root!
Obtained by Team D3mons
Savage says Hi. Love LoopyD.
We've (or I've) obtained root on the Samsung Galaxy S4 Straight Talk variant OF4 firmware, which was thought not possible due to new Knox security updates preventing even the installation of a kernel. Here's my screenshots.
Original dev thread where I was editing and tinkering.
http://forum.xda-developers.com/galaxy-s4/devs-only/s975l-tricking-knox-flash-t3279741
This was done by a hex edit hack available in Odin flashable form heree -> OneDrive link. Flash with Odin 3.07.
(My folder is a mess, do let me know if I uploaded the right one).
This Odin flash will flash to NB1 kernel hex-edit disguised as OF4, so the flash does not fai from download model, then apply towelroot I succeeded with its generic mod strings. Tap 3 times on towelroot to enable them, then simply press "Make it ra1n".
TWRP that works on this phone I haven't tested yet, but appearently jfttmo works.
Thanks:
Geohot, Chainfire, SAMMobile, and me! (Press Thanks when and if it worked and buy me a pop )
Disclaimer: This trips Knox. Your warranty is now void (who cares, it's Straight Talk!) I'll see if Triangle Away I can make work once I get the money, I'll see about applying a lucky patch or something to get it to force-do our phone. Hopefully without a brick. But SuperSU will disable the KNOX notifications and security check.
Original dev thread where I was editing and tinkering:
http://forum.xda-developers.com/galaxy-s4/devs-only/s975l-tricking-knox-flash-t3279741
Dev links:
Developer files:
PIT File for OF4
Vold.fstab for OF4
Dev important information
Code:
SM-S975L OF4 FIRMWARE MOUNT LOCATIONS AND ATTRIBUTES
[email protected]:/ # cat /proc/mounts
---------------------------------------------
rootfs / rootfs ro,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
none /dev/cpuctl cgroup rw,relatime,cpu 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
/sys/kernel/debug /sys/kernel/debug debugfs rw,relatime 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
tmpfs /mnt/secure tmpfs rw,seclabel,relatime,mode=700 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
/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/userdata /data ext4 rw,seclabel,nosuid,nodev,noatime,discard,journal_checksum,journal_async_commit,noauto_da_alloc,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/cache /cache ext4 rw,seclabel,nosuid,nodev,noatime,discard,journal_checksum,journal_async_commit,noauto_da_alloc,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/apnhlos /firmware vfat ro,relatime,uid=1000,gid=1000,fmask=0337,dmask=0227,codepage=cp437,iocharset=iso8859-1,shortname=lower,errors=remount-ro 0 0
/dev/block/platform/msm_sdcc.1/by-name/mdm /firmware-mdm vfat ro,relatime,uid=1000,gid=1000,fmask=0337,dmask=0227,codepage=cp437,iocharset=iso8859-1,shortname=lower,errors=remount-ro 0 0
/dev/block/platform/msm_sdcc.1/by-name/efs /efs ext4 rw,seclabel,nosuid,nodev,noatime,discard,journal_checksum,journal_async_commit,noauto_da_alloc,errors=panic,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/persdata /persdata/absolute ext4 rw,seclabel,nosuid,nodev,relatime,data=ordered 0 0
/data/container /mnt/shell/container sdcardfs rw,nosuid,nodev,relatime,uid=1000,gid=1000 0 0
/data/media /mnt/shell/emulated sdcardfs rw,nosuid,nodev,relatime,uid=1023,gid=1023 0 0
tmpfs /storage/emulated tmpfs rw,seclabel,nosuid,nodev,relatime,mode=050,gid=1028 0 0
/dev/block/vold/179:33 /storage/extSdCard vfat rw,dirsync,nosuid,nodev,noexec,noatime,nodiratime,uid=1000,gid=1023,fmask=0002,dmask=0002,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
tmpfs /storage/extSdCard/.android_secure tmpfs ro,seclabel,relatime,size=0k,mode=000 0 0
/data/media /storage/emulated/0 sdcardfs rw,nosuid,nodev,relatime,uid=1023,gid=1023 0 0
/data/media /storage/emulated/0/Android/obb sdcardfs rw,nosuid,nodev,relatime,uid=1023,gid=1023 0 0
/data/media /storage/emulated/legacy sdcardfs rw,nosuid,nodev,relatime,uid=1023,gid=1023 0 0
/data/media /storage/emulated/legacy/Android/obb sdcardfs rw,nosuid,nodev,relatime,uid=1023,gid=1023 0 0
---------------------------------------------
SM-S975L OF4 FIRMARE PARTITION LIST FOR CHECK AND IDENTIFICATION
[email protected]:/ # cat /proc/partitions
major minor #blocks name
253 0 512000 zram0
179 0 15388672 mmcblk0
179 1 12772 mmcblk0p1
179 2 52764 mmcblk0p2
179 3 128 mmcblk0p3
179 4 256 mmcblk0p4
179 5 512 mmcblk0p5
179 6 2048 mmcblk0p6
179 7 512 mmcblk0p7
179 8 512 mmcblk0p8
179 9 16896 mmcblk0p9
179 10 13952 mmcblk0p10
179 11 3072 mmcblk0p11
179 12 3072 mmcblk0p12
179 13 780 mmcblk0p13
179 14 780 mmcblk0p14
179 15 780 mmcblk0p15
179 16 2826240 mmcblk0p16
179 17 8192 mmcblk0p17
179 18 2119680 mmcblk0p18
179 19 6144 mmcblk0p19
179 20 10240 mmcblk0p20
179 21 10240 mmcblk0p21
179 22 10240 mmcblk0p22
179 23 6144 mmcblk0p23
179 24 3072 mmcblk0p24
179 25 8 mmcblk0p25
179 26 9216 mmcblk0p26
179 27 20480 mmcblk0p27
179 28 20480 mmcblk0p28
179 29 10219520 mmcblk0p29
179 32 1943552 mmcblk1
179 33 1942528 mmcblk1p1
---------------------------------------------
SM-S975L OF4 FIRMWARE MOUNT BLOCK POINTS (SYSTEM)
[email protected]:/ # ls -l /dev/block/platform/msm_sdcc.1/by-name/
---------------------------------------------
lrwxrwxrwx root root 1970-04-30 23:54 aboot -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 1970-04-30 23:54 apnhlos -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 1970-04-30 23:54 backup -> /dev/block/mmcblk0p23
lrwxrwxrwx root root 1970-04-30 23:54 boot -> /dev/block/mmcblk0p20
lrwxrwxrwx root root 1970-04-30 23:54 cache -> /dev/block/mmcblk0p18
lrwxrwxrwx root root 1970-04-30 23:54 carrier -> /dev/block/mmcblk0p28
lrwxrwxrwx root root 1970-04-30 23:54 efs -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 1970-04-30 23:54 fota -> /dev/block/mmcblk0p22
lrwxrwxrwx root root 1970-04-30 23:54 fsg -> /dev/block/mmcblk0p24
lrwxrwxrwx root root 1970-04-30 23:54 hidden -> /dev/block/mmcblk0p27
lrwxrwxrwx root root 1970-04-30 23:54 m9kefs1 -> /dev/block/mmcblk0p13
lrwxrwxrwx root root 1970-04-30 23:54 m9kefs2 -> /dev/block/mmcblk0p14
lrwxrwxrwx root root 1970-04-30 23:54 m9kefs3 -> /dev/block/mmcblk0p15
lrwxrwxrwx root root 1970-04-30 23:54 mdm -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 1970-04-30 23:54 modemst1 -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 1970-04-30 23:54 modemst2 -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 1970-04-30 23:54 pad -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 1970-04-30 23:54 param -> /dev/block/mmcblk0p19
lrwxrwxrwx root root 1970-04-30 23:54 persdata -> /dev/block/mmcblk0p26
lrwxrwxrwx root root 1970-04-30 23:54 persist -> /dev/block/mmcblk0p17
lrwxrwxrwx root root 1970-04-30 23:54 recovery -> /dev/block/mmcblk0p21
lrwxrwxrwx root root 1970-04-30 23:54 rpm -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 1970-04-30 23:54 sbl1 -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 1970-04-30 23:54 sbl2 -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 1970-04-30 23:54 sbl3 -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 1970-04-30 23:54 ssd -> /dev/block/mmcblk0p25
lrwxrwxrwx root root 1970-04-30 23:54 system -> /dev/block/mmcblk0p16
lrwxrwxrwx root root 1970-04-30 23:54 tz -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 1970-04-30 23:54 userdata -> /dev/block/mmcblk0p2
---------------------------------------------
I hope all this helps. More info available upon request. I'll pull as much as needed for a cyanogen or autoroot build, since towelroot works. I don't have a linux system nor can spend the time building. I have school.
Click to expand...
Click to collapse
Help! The OneDrive link is dead.

Help - accidentally deleted system, userdata, and radios partitions on my Nexus 6

When Magisk Manager put my Nexus 6 (AOSP 7.1.1) into an endless bootloop, I fired up ADB, went into TWRP, and tried to set thing right.
It only kinda worked. My phone would boot to the desktop, but all kinds of things just weren't right. (For instance, I couldn't use the rectangle icon to bring up a list of windows. It just didn't do anything, period.)
After wrestling with it for 6 hours or so, I finally accepted the fact that I was going to have to reinstall the OS, and redo all my customizations. Unfortunately, instead of doing a factory reset from the bootloader, I chose to wipe the system, radio, and userdata partitions from the wipe menu in TWRP.
Yes, it was stupid of me. I was tired, frustrated, angry at the broken Magisk Manager update, and badly sleep-deprived (the latter is due to a chronic medical condition, and is now, unfortunately, my default state).
Of course, TWRP warned me it would wipe my OS - but I assumed that meant it would wipe the contents of those partitions. Instead, it deleted the partitions themselves.
I can boot the phone to the bootloader, and TWRP is still present in the recovery partition, but I can't get it to install the OS from a zipfile (I have a USB-OTG cardreader, which it can see), because THE NECESSARY PARTITIONS ARE GONE, so it errors out. The same thing happens with partition image files from within the factory zip (which I also extracted to the sdcard from which I tried to install the zip).
Although I have developer options enabled, and I long ago unlocked the bootloader, ADB doesn't work (even to sideload files, despite my having started the TWRP sideload daemon). It does see the device in sideload mode, but it doesn't actually copy any files. Nor does it see the phone when I list devices. (Windows 10 reports that it doesn't recognize the USB-connected device, btw.) Naturally, fastboot doesn't work, either, apparently for the same reason.
So, somehow I need to recreate the system, userdata, cache, and radio partitions in order to install the factory zip, and get my phone to return from its undead state. The thing is, despite obvious evidence to the contrary, I'm not entirely stupid. I do not know how to create and name the necessary partitions, nor do I know what sizes they should be - and I'm unwilling to experiment with terminal commands until I'm certain I understand both things well enough to proceed.
If someone who knows what they're talking about would be kind enough to supply me with the above information, or to point me at existing resources that:
a. explain in detail how to use the terminal to create, size, and name the missing partitions (in stepwise fashion, if possible), and
b. supply me with the sizes of the partitions in question EXACTLY as whatever tool I have to use needs them to be specified,
I would be exceedingly grateful.
Thanks in advance for any help you can render.

If you go to recovery -> advanced -> terminal and enter the command "mount" do you get anything like the following?
Code:
rootfs on / type rootfs (rw,seclabel)
tmpfs on /dev type tmpfs (rw,seclabel,nosuid,relatime,size=1507196k,nr_inodes=172748,mode=755)
devpts on /dev/pts type devpts (rw,seclabel,relatime,mode=600)
proc on /proc type proc (rw,relatime)
sysfs on /sys type sysfs (rw,seclabel,relatime)
selinuxfs on /sys/fs/selinux type selinuxfs (rw,relatime)
tmpfs on /tmp type tmpfs (rw,seclabel,relatime,size=1507196k,nr_inodes=172748)
pstore on /sys/fs/pstore type pstore (rw,relatime)
adb on /dev/usb-ffs/adb type functionfs (rw,relatime)
/dev/block/mmcblk0p38 on /cache type ext4 (rw,seclabel,relatime,data=ordered)
/dev/block/mmcblk0p42 on /data type ext4 (rw,seclabel,relatime,data=ordered)
/dev/block/mmcblk0p42 on /sdcard type ext4 (rw,seclabel,relatime,data=ordered)
"find somebody that you think is undeserving of your compassion and give it to them" - Christian Picciolini

ktmom said:
If you go to recovery -> advanced -> terminal and enter the command "mount" do you get anything like the following?
Code:
rootfs on / type rootfs (rw,seclabel)
tmpfs on /dev type tmpfs (rw,seclabel,nosuid,relatime,size=1507196k,nr_inodes=172748,mode=755)
devpts on /dev/pts type devpts (rw,seclabel,relatime,mode=600)
proc on /proc type proc (rw,relatime)
sysfs on /sys type sysfs (rw,seclabel,relatime)
selinuxfs on /sys/fs/selinux type selinuxfs (rw,relatime)
tmpfs on /tmp type tmpfs (rw,seclabel,relatime,size=1507196k,nr_inodes=172748)
pstore on /sys/fs/pstore type pstore (rw,relatime)
adb on /dev/usb-ffs/adb type functionfs (rw,relatime)
/dev/block/mmcblk0p38 on /cache type ext4 (rw,seclabel,relatime,data=ordered)
/dev/block/mmcblk0p42 on /data type ext4 (rw,seclabel,relatime,data=ordered)
/dev/block/mmcblk0p42 on /sdcard type ext4 (rw,seclabel,relatime,data=ordered)
What I get is identical to the above, EXCEPT the last two lines. They read as follows:
Code:
/dev/block/dm-0 on /data type ext4 (rw,seclabel,relatime,data=ordered)
/dev/block/dm-0 on /sdcard type ext4 (rw,seclabel,relatime,data=ordered)
As you can see, the difference in both cases is "dm-0" in place of the volume designator.
As I said, those partitions are missing. The mount menu in TWRP won't allow them to be selected, and my attempts to flash the factory zip from an sdcard via USB-OTG fail with error messages indicating the partitions don't exist, so the images didn't flash. (This also happens when I attempt to flash the individual images.)
So, again, it's extremely clear to me that I need to create those partitions - and the radio and cache partitions - before I have any possibility of flashing a working OS, whether it's the factory shamu one, or a third-party firmware like Revolution/Remix.
BTW - Thank you for your substantive response. I very much appreciate your willingness to help!
Best regards,
Thom Stark
Click to expand...
Click to collapse

Try listing the partition table with this command:
fdisk -l /dev/block/mmcblk0

I’m going to information dump here for you. This is all of the relevant information from my device. Maybe it will help you recover.
I’m not sure enough of my knowledge to give you any suggestions on fixing this, but if all else fails, android stack exchange might be a resource.
Good Luck!
Code:
fdisk -l /dev/block/mmcblk0
Found valid GPT with protective MBR; using GPT
Disk /dev/block/mmcblk0: 61071360 sectors, 1148M
Logical sector size: 512
Disk identifier (GUID): 98101b32-bbe2-4bf2-a06e-2bb33d000c20
Partition table holds up to 42 entries
First usable sector is 34, last usable sector is 61071326
Number Start (sector) End (sector) Size Code Name
1 256 229631 112M 0700 modem
2 229632 262399 16.0M 0700 metadata
3 262400 263167 384K 0700 sbl1
4 263424 263535 57344 0700 sdi
5 263936 263967 16384 0700 sec
6 263968 264031 32768 0700 ddr
7 264192 266239 1024K 0700 aboot
8 267192 267703 256K 0700 rpm
9 268192 269215 512K 0700 utags
10 269216 270215 500K 0700 tz
11 270216 278527 4156K 0700 padA
12 278528 279295 384K 0700 sbl1bak
13 279552 281599 1024K 0700 abootBackup
14 282552 283063 256K 0700 rpmBackup
15 283552 284575 512K 0700 utagsBackup
16 284576 285575 500K 0700 tzBackup
17 285576 285583 4096 0700 versions
18 285696 286719 512K 0700 frp
19 286720 288767 1024K 0700 mdm1m9kefs1
20 288768 290815 1024K 0700 mdm1m9kefs2
21 290816 292863 1024K 0700 mdm1m9kefs3
22 292864 294911 1024K 0700 padB
23 294912 327679 16.0M 0700 sp
24 327680 360447 16.0M 0700 keystore
25 360448 364543 2048K 0700 logs
26 364544 430079 32.0M 0700 persist
27 430080 430591 256K 0700 mdm1hob
28 430592 430655 32768 0700 mdm1dhob
29 430656 430911 128K 0700 cid
30 430912 447295 8192K 0700 logo
31 447296 449343 1024K 0700 misc
32 449344 454399 2528K 0700 padD
33 454400 454401 1024 0700 mdm1m9kefsc
34 454402 454417 8192 0700 ssd
35 454656 487455 16.0M 0700 recovery
36 487680 505855 9088K 0700 kpan
37 505856 538623 16.0M 0700 boot
38 538624 1062911 256M 0700 cache
39 1062912 1193983 64.0M 0700 oem
40 1193984 1196031 1024K 0700 padC
41 1196032 5390335 2048M 0700 system
42 5390336 61005567 26.5G 0700 userdata
Code:
df
Filesystem 1K-blocks Used Available Use% Mounted on
tmpfs 1510044 504 1509540 1% /dev
/dev/block/platform/msm_sdcc.1/by-name/system 2031440 1485728 529328 74% /system
tmpfs 1510044 0 1510044 0% /system/xbin
/sbin/.core/block/loop08 60400 1772 57320 3% /system/xbin/mcs
tmpfs 1510044 0 1510044 0% /mnt
/dev/block/platform/msm_sdcc.1/by-name/cache 253920 316 248364 1% /cache
/dev/block/platform/msm_sdcc.1/by-name/modem 78756 78696 0 100% /firmware
/dev/block/platform/msm_sdcc.1/by-name/mdm1m9kefs3 744 743 0 100% /fsg
/dev/block/platform/msm_sdcc.1/by-name/userdata 27240188 13256268 13967536 49% /data
tmpfs 1510044 448 1509596 1% /sbin
/data/media 27240188 13256268 13967536 49% /storage/emulated
Code:
cat /proc/mounts
rootfs / rootfs ro,seclabel 0 0 tmpfs /dev tmpfs
rw,seclabel,nosuid,relatime,size=1510044k,nr_inodes=160860,mode=755 0 0
devpts /dev/pts devpts rw,seclabel,relatime,mode=600 0 0 none /dev/memcg
cgroup rw,relatime,memory 0 0 none /dev/cpuctl cgroup rw,relatime,cpu 0
0 none /dev/cpuset cgroup
rw,relatime,cpuset,noprefix,release_agent=/sbin/cpuset_release_agent 0 0
none /dev/bfqio cgroup rw,relatime,bfqio 0 0 adb /dev/usb-ffs/adb
functionfs rw,relatime 0 0 proc /proc proc
rw,relatime,gid=3009,hidepid=2 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,seclabel,relatime 0 0 pstore /sys/fs/pstore
pstore rw,seclabel,relatime 0 0
/dev/block/platform/msm_sdcc.1/by-name/system /system ext4
ro,seclabel,relatime,data=ordered 0 0 tmpfs /system/xbin tmpfs
rw,seclabel,relatime,size=1510044k,nr_inodes=160860 0 0
/sbin/.core/block/loop08 /system/xbin/mcs ext4
rw,seclabel,relatime,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/system /system/xbin/7z ext4
ro,seclabel,relatime,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/system /system/xbin/anrd ext4
ro,seclabel,relatime,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/system /system/xbin/bash ext4
ro,seclabel,relatime,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/system /system/xbin/cpustats ext4
ro,seclabel,relatime,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/system /system/xbin/dhdutil ext4
ro,seclabel,relatime,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/system /system/xbin/dnschk ext4
ro,seclabel,relatime,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/system /system/xbin/dumpcache
ext4 ro,seclabel,relatime,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/system /system/xbin/htop ext4
ro,seclabel,relatime,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/system /system/xbin/httpurl ext4
ro,seclabel,relatime,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/system /system/xbin/ioshark_bench
ext4 ro,seclabel,relatime,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/system /system/xbin/ksminfo ext4
ro,seclabel,relatime,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/system /system/xbin/latencytop
ext4 ro,seclabel,relatime,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/system /system/xbin/librank ext4
ro,seclabel,relatime,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/system /system/xbin/micro_bench
ext4 ro,seclabel,relatime,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/system
/system/xbin/micro_bench_static ext4 ro,seclabel,relatime,data=ordered 0
0 /dev/block/platform/msm_sdcc.1/by-name/system /system/xbin/mmc_utils
ext4 ro,seclabel,relatime,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/system /system/xbin/nano ext4
ro,seclabel,relatime,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/system /system/xbin/pigz ext4
ro,seclabel,relatime,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/system /system/xbin/powertop ext4
ro,seclabel,relatime,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/system /system/xbin/procmem ext4
ro,seclabel,relatime,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/system /system/xbin/procrank ext4
ro,seclabel,relatime,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/system /system/xbin/puncture_fs
ext4 ro,seclabel,relatime,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/system /system/xbin/rawbu ext4
ro,seclabel,relatime,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/system /system/xbin/rsync ext4
ro,seclabel,relatime,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/system /system/xbin/runconuid
ext4 ro,seclabel,relatime,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/system
/system/xbin/sane_schedstat ext4 ro,seclabel,relatime,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/system /system/xbin/showmap ext4
ro,seclabel,relatime,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/system /system/xbin/showslab ext4
ro,seclabel,relatime,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/system /system/xbin/simpleperf
ext4 ro,seclabel,relatime,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/system /system/xbin/strace ext4
ro,seclabel,relatime,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/system /system/xbin/taskstats
ext4 ro,seclabel,relatime,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/system /system/xbin/tcpdump ext4
ro,seclabel,relatime,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/system /system/xbin/unrar ext4
ro,seclabel,relatime,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/system /system/xbin/vim ext4
ro,seclabel,relatime,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/system /system/xbin/zip ext4
ro,seclabel,relatime,data=ordered 0 0 /sbin/.core/block/loop08
/system/etc/hosts ext4 rw,seclabel,relatime,data=ordered 0 0 none /acct
cgroup rw,relatime,cpuacct 0 0 tmpfs /mnt tmpfs
rw,seclabel,relatime,size=1510044k,nr_inodes=160860,mode=755,gid=1000 0
0 /data/media /mnt/runtime/default/emulated sdcardfs
rw,nosuid,nodev,noexec,noatime,fsuid=1023,fsgid=1023,gid=1015,multiuser,mask=6,derive_gid
0 0 /data/media /mnt/runtime/read/emulated sdcardfs
rw,nosuid,nodev,noexec,noatime,fsuid=1023,fsgid=1023,gid=9997,multiuser,mask=23,derive_gid
0 0 /data/media /mnt/runtime/write/emulated sdcardfs
rw,nosuid,nodev,noexec,noatime,fsuid=1023,fsgid=1023,gid=9997,multiuser,mask=7,derive_gid
0 0 none /config configfs rw,relatime 0 0
/dev/block/platform/msm_sdcc.1/by-name/cache /cache ext4
rw,seclabel,nosuid,nodev,noatime,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/modem /firmware ext4
ro,context=u:object_r:firmware_file:s0,relatime,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/persist /persist ext4
rw,seclabel,nosuid,nodev,relatime,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/mdm1m9kefs3 /fsg ext4
ro,context=u:object_r:fsg_file:s0,nosuid,nodev,relatime 0 0
/dev/block/platform/msm_sdcc.1/by-name/userdata /data ext4
rw,seclabel,nosuid,nodev,noatime,nodiratime,nobarrier,noauto_da_alloc,data=ordered
0 0 tmpfs /sbin tmpfs
rw,seclabel,relatime,size=1510044k,nr_inodes=160860 0 0
/dev/block/platform/msm_sdcc.1/by-name/system /sbin/.core/mirror/system
ext4 ro,seclabel,relatime,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/userdata /sbin/.core/mirror/bin
ext4
rw,seclabel,nosuid,nodev,noatime,nodiratime,nobarrier,noauto_da_alloc,data=ordered
0 0 /sbin/.core/block/loop08 /sbin/.core/img ext4
rw,seclabel,relatime,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/userdata
/sbin/.core/db-0/magisk.db ext4
rw,seclabel,nosuid,nodev,noatime,nodiratime,nobarrier,noauto_da_alloc,data=ordered
0 0 tmpfs /storage tmpfs
rw,seclabel,relatime,size=1510044k,nr_inodes=160860,mode=755,gid=1000 0
0 /data/media /storage/emulated sdcardfs
rw,nosuid,nodev,noexec,noatime,fsuid=1023,fsgid=1023,gid=9997,multiuser,mask=7,derive_gid
0 0 tmpfs /storage/self tmpfs
rw,seclabel,relatime,size=1510044k,nr_inodes=160860,mode=755,gid=1000 0
0
Code:
cat /proc/partitions
major minor #blocks name
179 0 30535680 mmcblk0
179 1 114688 mmcblk0p1
179 2 16384 mmcblk0p2
179 3 384 mmcblk0p3
179 4 56 mmcblk0p4
179 5 16 mmcblk0p5
179 6 32 mmcblk0p6
179 7 1024 mmcblk0p7
179 8 256 mmcblk0p8
179 9 512 mmcblk0p9
179 10 500 mmcblk0p10
179 11 4156 mmcblk0p11
179 12 384 mmcblk0p12
179 13 1024 mmcblk0p13
179 14 256 mmcblk0p14
179 15 512 mmcblk0p15
179 16 500 mmcblk0p16
179 17 4 mmcblk0p17
179 18 512 mmcblk0p18
179 19 1024 mmcblk0p19
179 20 1024 mmcblk0p20
179 21 1024 mmcblk0p21
179 22 1024 mmcblk0p22
179 23 16384 mmcblk0p23
179 24 16384 mmcblk0p24
179 25 2048 mmcblk0p25
179 26 32768 mmcblk0p26
179 27 256 mmcblk0p27
179 28 32 mmcblk0p28
179 29 128 mmcblk0p29
179 30 8192 mmcblk0p30
179 31 1024 mmcblk0p31
259 0 2528 mmcblk0p32
259 1 1 mmcblk0p33
259 2 8 mmcblk0p34
259 3 16400 mmcblk0p35
259 4 9088 mmcblk0p36
259 5 16384 mmcblk0p37
259 6 262144 mmcblk0p38
259 7 65536 mmcblk0p39
259 8 1024 mmcblk0p40
259 9 2097152 mmcblk0p41
259 10 27807616 mmcblk0p42
179 32 4096 mmcblk0rpmb
7 64 65536 loop64
Code:
ls -al /dev/block/platform/msm_sdcc.1/by-name
total 0
drwxr-xr-x 2 root root 880 1970-01-21 18:47 .
drwxr-xr-x 4 root root 960 1970-01-21 18:47 ..
lrwxrwxrwx 1 root root 20 1970-01-21 18:47 aboot -> /dev/block/mmcblk0p7
lrwxrwxrwx 1 root root 21 1970-01-21 18:47 abootBackup -> /dev/block/mmcblk0p13
lrwxrwxrwx 1 root root 21 1970-01-21 18:47 boot -> /dev/block/mmcblk0p37
lrwxrwxrwx 1 root root 21 1970-01-21 18:47 cache -> /dev/block/mmcblk0p38
lrwxrwxrwx 1 root root 21 1970-01-21 18:47 cid -> /dev/block/mmcblk0p29
lrwxrwxrwx 1 root root 20 1970-01-21 18:47 ddr -> /dev/block/mmcblk0p6
lrwxrwxrwx 1 root root 21 1970-01-21 18:47 frp -> /dev/block/mmcblk0p18
lrwxrwxrwx 1 root root 21 1970-01-21 18:47 keystore -> /dev/block/mmcblk0p24
lrwxrwxrwx 1 root root 21 1970-01-21 18:47 kpan -> /dev/block/mmcblk0p36
lrwxrwxrwx 1 root root 21 1970-01-21 18:47 logo -> /dev/block/mmcblk0p30
lrwxrwxrwx 1 root root 21 1970-01-21 18:47 logs -> /dev/block/mmcblk0p25
lrwxrwxrwx 1 root root 21 1970-01-21 18:47 mdm1dhob -> /dev/block/mmcblk0p28
lrwxrwxrwx 1 root root 21 1970-01-21 18:47 mdm1hob -> /dev/block/mmcblk0p27
lrwxrwxrwx 1 root root 21 1970-01-21 18:47 mdm1m9kefs1 -> /dev/block/mmcblk0p19
lrwxrwxrwx 1 root root 21 1970-01-21 18:47 mdm1m9kefs2 -> /dev/block/mmcblk0p20
lrwxrwxrwx 1 root root 21 1970-01-21 18:47 mdm1m9kefs3 -> /dev/block/mmcblk0p21
lrwxrwxrwx 1 root root 21 1970-01-21 18:47 mdm1m9kefsc -> /dev/block/mmcblk0p33
lrwxrwxrwx 1 root root 20 1970-01-21 18:47 metadata -> /dev/block/mmcblk0p2
lrwxrwxrwx 1 root root 21 1970-01-21 18:47 misc -> /dev/block/mmcblk0p31
lrwxrwxrwx 1 root root 20 1970-01-21 18:47 modem -> /dev/block/mmcblk0p1
lrwxrwxrwx 1 root root 21 1970-01-21 18:47 oem -> /dev/block/mmcblk0p39
lrwxrwxrwx 1 root root 21 1970-01-21 18:47 padA -> /dev/block/mmcblk0p11
lrwxrwxrwx 1 root root 21 1970-01-21 18:47 padB -> /dev/block/mmcblk0p22
lrwxrwxrwx 1 root root 21 1970-01-21 18:47 padC -> /dev/block/mmcblk0p40
lrwxrwxrwx 1 root root 21 1970-01-21 18:47 padD -> /dev/block/mmcblk0p32
lrwxrwxrwx 1 root root 21 1970-01-21 18:47 persist -> /dev/block/mmcblk0p26
lrwxrwxrwx 1 root root 21 1970-01-21 18:47 recovery -> /dev/block/mmcblk0p35
lrwxrwxrwx 1 root root 20 1970-01-21 18:47 rpm -> /dev/block/mmcblk0p8
lrwxrwxrwx 1 root root 21 1970-01-21 18:47 rpmBackup -> /dev/block/mmcblk0p14
lrwxrwxrwx 1 root root 20 1970-01-21 18:47 sbl1 -> /dev/block/mmcblk0p3
lrwxrwxrwx 1 root root 21 1970-01-21 18:47 sbl1bak -> /dev/block/mmcblk0p12
lrwxrwxrwx 1 root root 20 1970-01-21 18:47 sdi -> /dev/block/mmcblk0p4
lrwxrwxrwx 1 root root 20 1970-01-21 18:47 sec -> /dev/block/mmcblk0p5
lrwxrwxrwx 1 root root 21 1970-01-21 18:47 sp -> /dev/block/mmcblk0p23
lrwxrwxrwx 1 root root 21 1970-01-21 18:47 ssd -> /dev/block/mmcblk0p34
lrwxrwxrwx 1 root root 21 1970-01-21 18:47 system -> /dev/block/mmcblk0p41
lrwxrwxrwx 1 root root 21 1970-01-21 18:47 tz -> /dev/block/mmcblk0p10
lrwxrwxrwx 1 root root 21 1970-01-21 18:47 tzBackup -> /dev/block/mmcblk0p16
lrwxrwxrwx 1 root root 21 1970-01-21 18:47 userdata -> /dev/block/mmcblk0p42
lrwxrwxrwx 1 root root 20 1970-01-21 18:47 utags -> /dev/block/mmcblk0p9
lrwxrwxrwx 1 root root 21 1970-01-21 18:47 utagsBackup -> /dev/block/mmcblk0p15
lrwxrwxrwx 1 root root 21 1970-01-21 18:47 versions -> /dev/block/mmcblk0p17

Have you tried to download the factory image and flash from bootloader. The flash all script.

camcory said:
Have you tried to download the factory image and flash from bootloader. The flash all script.
Click to expand...
Click to collapse
He said that he can't make the PC recognize the device in Fastboot or ADB after the accident.
"find somebody that you think is undeserving of your compassion and give it to them" - Christian Picciolini

Thank you, ktmom.
ktmom said:
"find somebody that you think is undeserving of your compassion and give it to them" - Christian Picciolini
Click to expand...
Click to collapse
Thank you for the data dump, ktmom. I very much appreciate it.
Sorry it took so long for me to reply. I've been unwell.
(BTW - I like your .sig a lot. I wish more of us had Mr. Picciolini's attitude ... )
Best regards,
Thom Stark

Database Develop

welcome