It's been released in Europe for quite some time and from what I'm hearing it's about to hit the American market as well. Doen't seem to get any love yet on XDA.
Lovely little thing, from my three days with it. S625/64GB/4GB RAM/SD Slot/LTE. Comes with Android 7.1.1 stock.
Looks likes something that could finally replace the N7 2013, provided the community picks it up. I'm honestly surprised there's been little to no chatter about it whatsoever.
Did anyone manage to compile TWRP for it yet or root it otherwise?
wonderfulme said:
It's been released in Europe for quite some time and from what I'm hearing it's about to hit the American market as well. Doen't seem to get any love yet on XDA.
Lovely little thing, from my three days with it. S625/64GB/4GB RAM/SD Slot/LTE. Comes with Android 7.1.1 stock.
Looks likes something that could finally replace the N7 2013, provided the community picks it up. I'm honestly surprised there's been little to no chatter about it whatsoever.
Did anyone manage to compile TWRP for it yet or root it otherwise?
Click to expand...
Click to collapse
I don't own the device so I cannot help you there. But what you can check is if the device can be bootloader unlocked in developer settings. That's a requirement for TWRP and also what you need is a kernel/boot image to build TRWP. Since there don't seem to be factory images available for this yet it will be difficult to retrieve a boot image from the device. Also Lenovo hasn't released any source code for this yet even though they are obliged to do so. Shame on them! I suggest you complain in the Lenovo forums about it. It's clearly a GPL violation.
matshias said:
I don't own the device so I cannot help you there. But what you can check is if the device can be bootloader unlocked in developer settings. That's a requirement for TWRP and also what you need is a kernel/boot image to build TRWP. Since there don't seem to be factory images available for this yet it will be difficult to retrieve a boot image from the device. Also Lenovo hasn't released any source code for this yet even though they are obliged to do so. Shame on them! I suggest you complain in the Lenovo forums about it. It's clearly a GPL violation.
Click to expand...
Click to collapse
Thanks, I actualy did just that - asked about the kernel source on their official forum. Don't expect any major breakthroughts though (see https://forum.xda-developers.com/showthread.php?t=1555099, for instance).
As for whether the bootloader is locked or not, I have honestly no idea. Neither the "long phone number" method nor the "fastboot oem device-info" works. I have Android SDK installed and it works just fine when I plug in my N7 2003. The USB debugging is enabled and allowed for my desktop. Still, zero results. The Lenovo one doesn't even show up when running "fastboot devices".
Yet the "Lenovo Moto Smart Assistant" whatever it's supposed to do identifies the tablet when connected with USB just fine.
So I guess it's a safe bet to say that we're a long way from rooting this one. Or, more likely, I'm doing something wrong. Never had adb/fastboot issues with N7 though.
I'll just sit and wait till it hits the US market and generates some deserved interest because on the surface it's not a bad tablet at all. The battery life, the screen, the price/performance ratio, the SD slot and LTE capability all make that for a good web browser/book reader. It's not that bad looking either. Although I have yet to find a proper case unless resorting to Alibaba or something. It's even got a half-decent camera.
Overall, it's totally worth the $300 or whatever you end up paying. Comes with next to no bloatware, doesn't overheat. Even has that Dolby thing and a fingerprint scanner for some reason. Only wish it could be rooted and ran LineageOS or something.
wonderfulme said:
Thanks, I actualy did just that - asked about the kernel source on their official forum. Don't expect any major breakthroughts though (see https://forum.xda-developers.com/showthread.php?t=1555099, for instance).
As for whether the bootloader is locked or not, I have honestly no idea. Neither the "long phone number" method nor the "fastboot oem device-info" works. I have Android SDK installed and it works just fine when I plug in my N7 2003. The USB debugging is enabled and allowed for my desktop. Still, zero results. The Lenovo one doesn't even show up when running "fastboot devices".
Yet the "Lenovo Moto Smart Assistant" whatever it's supposed to do identifies the tablet when connected with USB just fine.
So I guess it's a safe bet to say that we're a long way from rooting this one. Or, more likely, I'm doing something wrong. Never had adb/fastboot issues with N7 though.
I'll just sit and wait till it hits the US market and generates some deserved interest because on the surface it's not a bad tablet at all. The battery life, the screen, the price/performance ratio, the SD slot and LTE capability all make that for a good web browser/book reader. It's not that bad looking either. Although I have yet to find a proper case unless resorting to Alibaba or something. It's even got a half-decent camera.
Overall, it's totally worth the $300 or whatever you end up paying. Comes with next to no bloatware, doesn't overheat. Even has that Dolby thing and a fingerprint scanner for some reason. Only wish it could be rooted and ran LineageOS or something.
Click to expand...
Click to collapse
Are you sure you are in fastboot mode? Can you try adb reboot bootloader and then connect with fastboot again?
Also you should check that in developer settings you have an option OEM unlock.
Well you don't need the kernel source for TWRP. What you need is the following:
* kernel image somehow extracted
* partition layout. If cat /proc/partitions works via adb then this is sufficient.
* extracted /system/build.prop and output of mount command
This should be enough to get it booting. Decrypting the data partition is another step, but for root it's not needed.
Extracting the kernel image is the hard part as long as there is no factory image available. But first check if the tablet can be unlocked otherwise it's not worth the effort.
matshias said:
Are you sure you are in fastboot mode? Can you try adb reboot bootloader and then connect with fastboot again?
Also you should check that in developer settings you have an option OEM unlock.
Well you don't need the kernel source for TWRP. What you need is the following:
* kernel image somehow extracted
* partition layout. If cat /proc/partitions works via adb then this is sufficient.
* extracted /system/build.prop and output of mount command
This should be enough to get it booting. Decrypting the data partition is another step, but for root it's not needed.
Extracting the kernel image is the hard part as long as there is no factory image available. But first check if the tablet can be unlocked otherwise it's not worth the effort.
Click to expand...
Click to collapse
There was indeed an option for "OEM unlock" in dev settings which I somehow missed. Works as intended now.
So here's the output of fastboot:
Code:
F:\AndroidSDK\platform-tools>fastboot oem device-info
...
(bootloader) Device tampered: false
(bootloader) Device unlocked: false
(bootloader) Device critical unlocked: false
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
OKAY [ 0.054s]
finished. total time: 0.054s
Guess we're out of luck here?
I also did an "adb shell" and /proc/partitions as well as /system/build.prop are readable, "mount" works, however I have no idea where the kernel is stored. There's a "/firmware" dir but it's unaccessible, I'm thinking maybe that's where:
Code:
2|TB-8704X:/ $ uname -a
Linux localhost 3.18.31-perf-g40dd5c6-dirty #1 SMP PREEMPT Fri Jul 7 02:02:41 CST 2017 aarch64
TB-8704X:/ $ id
uid=2000(shell) gid=2000(shell) groups=2000(shell),1004(input),1007(log),1011(adb),1015(sdcard_rw),1028(sdcard_r),3001(net_bt_admin),3002(net_bt),3003(inet),3006(net_bw_stats),3009(readproc) context=u:r:shell:s0
TB-8704X:/ $ ls -ld firmware
dr-xr-x--- 4 system system 16384 1970-01-01 03:00 firmware
TB-8704X:/ $ cd firmware
/system/bin/sh: cd: /firmware: Permission denied
Also, FWIW, here's a list of files/dirs in / in case I missed something of note. I'm not really comfortable with Android internals.
Code:
130|TB-8704X:/ $ ls -l
total 4232
dr-xr-xr-x 61 root root 0 1970-03-08 03:34 acct
drwxr-xr-x 2 root root 40 1970-01-01 03:00 bt_firmware
drwxrwx--- 7 system cache 4096 2017-08-10 16:42 cache
lrwxrwxrwx 1 root root 13 1970-01-01 03:00 charger -> /sbin/healthd
drwxr-xr-x 2 root root 0 1970-03-08 03:34 config
lrwxrwxrwx 1 root root 17 1970-01-01 03:00 d -> /sys/kernel/debug
drwxrwx--x 43 system system 4096 1970-03-08 03:34 data
-rw-r--r-- 1 root root 995 1970-01-01 03:00 default.prop
drwxr-xr-x 15 root root 3500 1970-03-08 03:34 dev
drwxr-xr-x 3 root root 4096 1970-01-01 03:00 dsp
lrwxrwxrwx 1 root root 11 1970-01-01 03:00 etc -> /system/etc
-rw-r--r-- 1 root root 186677 1970-01-01 03:00 file_contexts.bin
dr-xr-x--- 4 system system 16384 1970-01-01 03:00 firmware
-rw-r----- 1 root root 1578 1970-01-01 03:00 fstab.qcom
-rwxr-x--- 1 root root 1246704 1970-01-01 03:00 init
-rwxr-x--- 1 root root 1846 1970-01-01 03:00 init.carrier.rc
-rwxr-x--- 1 root root 3295 1970-01-01 03:00 init.class_main.sh
-rwxr-x--- 1 root root 1156 1970-01-01 03:00 init.environ.rc
-rwxr-x--- 1 root root 1730 1970-01-01 03:00 init.mdm.sh
-rwxr-x--- 1 root root 29161 1970-01-01 03:00 init.msm.usb.configfs.rc
-rwxr-x--- 1 root root 7054 1970-01-01 03:00 init.qcom.class_core.sh
-rwxr-x--- 1 root root 12035 1970-01-01 03:00 init.qcom.early_boot.sh
-rwxr-x--- 1 root root 3775 1970-01-01 03:00 init.qcom.factory.rc
-rwxr-x--- 1 root root 37960 1970-01-01 03:00 init.qcom.rc
-rwxr-x--- 1 root root 2029 1970-01-01 03:00 init.qcom.sensors.sh
-rwxr-x--- 1 root root 12173 1970-01-01 03:00 init.qcom.sh
-rwxr-x--- 1 root root 2962 1970-01-01 03:00 init.qcom.syspart_fixup.sh
-rwxr-x--- 1 root root 97623 1970-01-01 03:00 init.qcom.usb.rc
-rwxr-x--- 1 root root 10950 1970-01-01 03:00 init.qcom.usb.sh
-rwxr-x--- 1 root root 26676 1970-01-01 03:00 init.rc
-rwxr-x--- 1 root root 9584 1970-01-01 03:00 init.target.rc
-rwxr-x--- 1 root root 12058 1970-01-01 03:00 init.usb.configfs.rc
-rwxr-x--- 1 root root 5715 1970-01-01 03:00 init.usb.rc
-rwxr-x--- 1 root root 411 1970-01-01 03:00 init.zygote32.rc
-rwxr-x--- 1 root root 684 1970-01-01 03:00 init.zygote64_32.rc
drwxr-xr-x 10 root system 220 1970-03-08 03:34 mnt
drwxr-xr-x 2 root root 40 1970-01-01 03:00 oem
drwxrwx--x 13 root system 4096 1970-01-01 03:00 persist
dr-xr-xr-x 518 root root 0 1970-01-01 03:00 proc
-rw-r--r-- 1 root root 11549 1970-01-01 03:00 property_contexts
drwxr-xr-x 3 root root 60 1970-01-01 03:00 res
drwx------ 2 root root 40 2017-07-06 21:00 root
drwxr-x--- 2 root root 160 1970-01-01 03:00 sbin
lrwxrwxrwx 1 root root 21 1970-01-01 03:00 sdcard -> /storage/self/primary
-rw-r--r-- 1 root root 1957 1970-01-01 03:00 seapp_contexts
-rw-r--r-- 1 root root 90 1970-01-01 03:00 selinux_version
-rw-r--r-- 1 root root 285602 1970-01-01 03:00 sepolicy
-rw-r--r-- 1 root root 17999 1970-01-01 03:00 service_contexts
drwxr-xr-x 4 root root 80 2017-08-12 15:57 storage
dr-xr-xr-x 16 root root 0 1970-03-08 03:34 sys
drwxr-xr-x 21 root root 4096 1970-01-01 03:00 system
lrwxrwxrwx 1 root root 16 1970-03-08 03:34 tombstones -> /data/tombstones
-rw-r--r-- 1 root root 14131 1970-01-01 03:00 ueventd.qcom.rc
-rw-r--r-- 1 root root 4857 1970-01-01 03:00 ueventd.rc
lrwxrwxrwx 1 root root 14 1970-01-01 03:00 vendor -> /system/vendor
-rw-r--r-- 1 root root 524 1970-01-01 03:00 verity_key
So are we out of options yet unless a new Linux kernel exploit eventually comes along OR Lenovo decides to release the firmware? I don't believe dirtycow would work here, considering July 2017 security updates have been applied.
That's quite sad.
Just got it and been playing with it for a couple days now. Device itself seems to be fine, but not having root is PITA.
wonderfulme said:
So are we out of options yet unless a new Linux kernel exploit eventually comes along OR Lenovo decides to release the firmware? I don't believe dirtycow would work here, considering July 2017 security updates have been applied.
Click to expand...
Click to collapse
The firmwares just showed up on the Russian Lenovo forums. So we can build TWRP if you post all the prerequisites mentioned a few posts earlier (partition layout, mount output, ...)
matshias said:
The firmwares just showed up on the Russian Lenovo forums. So we can build TWRP if you post all the prerequisites mentioned a few posts earlier (partition layout, mount output, ...)
Click to expand...
Click to collapse
Here's the output for the TB-8704X LTE version.
Mount points:
Code:
TB-8704X:/ $ mount
rootfs on / type rootfs (ro,seclabel,size=1705664k,nr_inodes=426416)
tmpfs on /dev type tmpfs (rw,seclabel,nosuid,relatime,size=1811380k,nr_inodes=452845,mode=755)
devpts on /dev/pts type devpts (rw,seclabel,relatime,mode=600)
proc on /proc type proc (rw,relatime,gid=3009,hidepid=2)
sysfs on /sys type sysfs (rw,seclabel,relatime)
selinuxfs on /sys/fs/selinux type selinuxfs (rw,relatime)
debugfs on /sys/kernel/debug type debugfs (rw,seclabel,relatime)
none on /acct type cgroup (rw,relatime,cpuacct)
tmpfs on /mnt type tmpfs (rw,seclabel,relatime,size=1811380k,nr_inodes=452845,mode=755,gid=1000)
none on /config type configfs (rw,relatime)
none on /dev/cpuctl type cgroup (rw,relatime,cpu)
/dev/block/dm-0 on /system type ext4 (ro,seclabel,relatime,discard,data=ordered)
/dev/block/bootdevice/by-name/cache on /cache type ext4 (rw,seclabel,nosuid,nodev,relatime,data=ordered)
/dev/block/bootdevice/by-name/persist on /persist type ext4 (rw,seclabel,nosuid,nodev,relatime,data=ordered)
/dev/block/bootdevice/by-name/dsp on /dsp type ext4 (ro,seclabel,nosuid,nodev,relatime,data=ordered)
/dev/block/bootdevice/by-name/modem on /firmware type vfat (ro,context=u:object_r:firmware_file:s0,relatime,uid=1000,gid=1000,fmask=0337,dmask=0227,codepage=437,iocharset=iso8859-1,shortname=lower,errors=remount-ro)
tmpfs on /storage type tmpfs (rw,seclabel,relatime,size=1811380k,nr_inodes=452845,mode=755,gid=1000)
adb on /dev/usb-ffs/adb type functionfs (rw,relatime)
/dev/block/dm-1 on /data type ext4 (rw,seclabel,nosuid,nodev,relatime,discard,noauto_da_alloc,data=ordered)
/dev/fuse on /mnt/runtime/default/emulated type fuse (rw,nosuid,nodev,noexec,noatime,user_id=1023,group_id=1023,default_permissions,allow_other)
/dev/fuse on /storage/emulated type fuse (rw,nosuid,nodev,noexec,noatime,user_id=1023,group_id=1023,default_permissions,allow_other)
/dev/fuse on /mnt/runtime/read/emulated type fuse (rw,nosuid,nodev,noexec,noatime,user_id=1023,group_id=1023,default_permissions,allow_other)
/dev/fuse on /mnt/runtime/write/emulated type fuse (rw,nosuid,nodev,noexec,noatime,user_id=1023,group_id=1023,default_permissions,allow_other)
Partitions:
Code:
TB-8704X:/etc $ df -h
Filesystem Size Used Avail Use% Mounted on
rootfs 1.6G 4.7M 1.6G 1% /
tmpfs 1.7G 652K 1.7G 1% /dev
tmpfs 1.7G 0 1.7G 0% /mnt
/dev/block/dm-0 3.6G 3.2G 336M 91% /system
/dev/block/bootdevice/by-name/cache 248M 744K 242M 1% /cache
/dev/block/bootdevice/by-name/persist 27M 512K 26M 2% /persist
/dev/block/bootdevice/by-name/dsp 12M 4.9M 6.4M 44% /dsp
/dev/block/bootdevice/by-name/modem 84M 74M 10M 88% /firmware
tmpfs 1.7G 0 1.7G 0% /storage
/dev/block/dm-1 52G 14G 38G 27% /data
/dev/fuse 52G 14G 38G 27% /storage/emulated
TB-8704X:/ $ cat /proc/partitions
major minor #blocks name
254 0 524288 zram0
179 0 61071360 mmcblk0
179 1 86016 mmcblk0p1
179 2 1 mmcblk0p2
179 3 8 mmcblk0p3
179 4 512 mmcblk0p4
179 5 512 mmcblk0p5
179 6 512 mmcblk0p6
179 7 512 mmcblk0p7
179 8 2048 mmcblk0p8
179 9 2048 mmcblk0p9
179 10 256 mmcblk0p10
179 11 256 mmcblk0p11
179 12 16384 mmcblk0p12
179 13 1536 mmcblk0p13
179 14 1536 mmcblk0p14
179 15 32 mmcblk0p15
179 16 32 mmcblk0p16
179 17 1536 mmcblk0p17
179 18 16 mmcblk0p18
179 19 15360 mmcblk0p19
179 20 1024 mmcblk0p20
179 21 1024 mmcblk0p21
179 22 65536 mmcblk0p22
179 23 65536 mmcblk0p23
179 24 1024 mmcblk0p24
179 25 3984588 mmcblk0p25
179 26 262144 mmcblk0p26
179 27 32768 mmcblk0p27
179 28 1024 mmcblk0p28
179 29 512 mmcblk0p29
179 30 32 mmcblk0p30
179 31 262144 mmcblk0p31
259 0 32 mmcblk0p32
259 1 512 mmcblk0p33
259 2 1024 mmcblk0p34
259 3 32768 mmcblk0p35
259 4 512 mmcblk0p36
259 5 4096 mmcblk0p37
259 6 128 mmcblk0p38
259 7 128 mmcblk0p39
259 8 256 mmcblk0p40
259 9 256 mmcblk0p41
259 10 256 mmcblk0p42
259 11 256 mmcblk0p43
259 12 256 mmcblk0p44
259 13 256 mmcblk0p45
259 14 256 mmcblk0p46
259 15 256 mmcblk0p47
259 16 8 mmcblk0p48
259 17 65536 mmcblk0p49
259 18 204800 mmcblk0p50
259 19 55492071 mmcblk0p51
179 32 4096 mmcblk0rpmb
253 0 3922408 dm-0
253 1 55492055 dm-1
/system/build.prop, just in case: https://pastebin.com/raw/jQn9N8nc
Kindly let me know if I missed anything.
Also, that Russian site lists the model number as TB-8704X_S000026_170707_ROW_QFIL, while my version of build.prop contains TB-8704X_S000026_170707_ROW (withot the "QFIL"). I'm not entirely up to date on Lenovo's naming conventions, but could that possibly suggest a slightly different model or should we disregard it altogether?
Edit: Nevermind, QFIL seems to be the name of the Qualcomm firmware update software.
Thanks!
I also hope that rooting or later a LineageOS will be available. I bought my one from Amazon in Germany 64GB/4GB/WiFi and it has following build number TB-8704F_S000024_170706_ROW. I came from Nexus 7 (2012).
Bought mine via Lenovo in the UK for £280 and loving it. I've been looking for a decent 8" tablet which wasn't stupidly expensive and this ticks all the boxes.
4GB /64GB + SD card
1920x1080 screen
Good audio with those front facing speakers
Decent battery life so far
Would love to be able to root and install Lineage as I use on my OPO as well, that would be perfect.
Love it so much I've ordered one for my old man as well.
wonderfulme said:
Thanks, I actualy did just that - asked about the kernel source on their official forum. Don't expect any major breakthroughts though (see https://forum.xda-developers.com/showthread.php?t=1555099, for instance).
As for whether the bootloader is locked or not, I have honestly no idea. Neither the "long phone number" method nor the "fastboot oem device-info" works. I have Android SDK installed and it works just fine when I plug in my N7 2003. The USB debugging is enabled and allowed for my desktop. Still, zero results. The Lenovo one doesn't even show up when running "fastboot devices".
Yet the "Lenovo Moto Smart Assistant" whatever it's supposed to do identifies the tablet when connected with USB just fine.
So I guess it's a safe bet to say that we're a long way from rooting this one. Or, more likely, I'm doing something wrong. Never had adb/fastboot issues with N7 though.
I'll just sit and wait till it hits the US market and generates some deserved interest because on the surface it's not a bad tablet at all. The battery life, the screen, the price/performance ratio, the SD slot and LTE capability all make that for a good web browser/book reader. It's not that bad looking either. Although I have yet to find a proper case unless resorting to Alibaba or something. It's even got a half-decent camera.
Overall, it's totally worth the $300 or whatever you end up paying. Comes with next to no bloatware, doesn't overheat. Even has that Dolby thing and a fingerprint scanner for some reason. Only wish it could be rooted and ran LineageOS or something.
Click to expand...
Click to collapse
I have the tab 4 8" and you can unlock the boooader know developer mode.
Anonwatch said:
I have the tab 4 8" and you can unlock the boooader know developer mode.
Click to expand...
Click to collapse
Already figured as much. You might want to take a look at matshias's thread at https://forum.xda-developers.com/thinkpad-tablet/general/twrp-root-tab-4-plus-tb-x704l-f-tb-t3664407
He's got TWRP working on both 8 and 10+.
Hey guys. I own Lenovo tab 3 8 plus (TB-8703F) and there are ads popping out everywhere when I open playstore or chrome etc? How to get rid of this?
Vicky khan said:
Hey guys. I own Lenovo tab 3 8 plus (TB-8703F) and there are ads popping out everywhere when I open playstore or chrome etc? How to get rid of this?
Click to expand...
Click to collapse
Wrong thread for your device - but install an ad-blocker
Many thanks for your great work. Everything has worked as described and I am super happy with this new tablet, replacing my Nexus 7.
I am surprised that there is so little activity around the Tab 4 here on XDA, but I am confident that once people understand that this is a really cool tablet and practically the only one with modern specs that comes close to the N7, there will be Custom ROMs and more. It's a beautiful piece of hardware and even without Custom ROM, the Lenovo Android is surprisingly lean and without bloatware (except for Microsoft Office).
Hi,guys!Just bought it from Amazon for $118(16GBROM)!
It's wonderful and I speak Russian, Macedonian, Bulgarian,German,a bit Serbian!
If you need help for Russian, just message me!:
Just had my memory card (128GB Samsung Pro) 'eaten' by my tablet - while on holiday with no computer access and it had my videos and music on it.
I've seen reports of this on other sites as well, and am fuming right now as this is an almighty ****-up if it's a regular occurrence, makes the tablet basically useless to me.
Edit: Took the card out of the tablet and stuck it in my Honor 9, no errors and all files work perfectly. Put it back in the Lenovo, so corrupt and won't let me do anything other than format it. Bloody Lenovo
jimmy19742 said:
Hi,guys!Just bought it from Amazon for $118(16GBROM)!
It's wonderful and I speak Russian, Macedonian, Bulgarian,German,a bit Serbian!
If you need help for Russian, just message me!:
Click to expand...
Click to collapse
Hate to say it, but sounds like you bought the Tab 4 8 and not the Tab 4 8 Plus. If it is the Plus, you got a steal!
magoo5289 said:
Hate to say it, but sounds like you bought the Tab 4 8 and not the Tab 4 8 Plus. If it is the Plus, you got a steal!
Click to expand...
Click to collapse
Yup 8504X not 8704X!
I saw this but am skeptical by nature and don't read Russian.
http://proshivkis.ru/?p=lenovo-tab-4-8-plus-wifi-lineageos-14-1
Related
Code:
su
ls -lR /dev
Code:
/dev/block:
brw------- root root 7, 0 2013-07-04 18:28 loop0
brw------- root root 7, 1 2013-07-04 18:28 loop1
brw------- root root 7, 2 2013-07-04 18:28 loop2
brw------- root root 7, 3 2013-07-04 18:28 loop3
brw------- root root 7, 4 2013-07-04 18:28 loop4
brw------- root root 7, 5 2013-07-04 18:28 loop5
brw------- root root 7, 6 2013-07-04 18:28 loop6
brw------- root root 7, 7 2013-07-04 18:28 loop7
brw------- root root 179, 0 2013-07-04 18:28 mmcblk0
brw------- root root 179, 1 2013-07-04 18:28 mmcblk0p1
brw------- root root 179, 10 2013-07-04 18:28 mmcblk0p10
brw------- root root 179, 11 2013-07-04 18:28 mmcblk0p11
brw------- root root 179, 12 2013-07-04 18:28 mmcblk0p12
brw------- root root 179, 2 2013-07-04 18:28 mmcblk0p2
brw------- root root 179, 3 2013-07-04 18:28 mmcblk0p3
brw-rw---- system system 179, 4 2013-07-04 18:31 mmcblk0p4
brw------- root root 179, 5 2013-07-04 18:28 mmcblk0p5
brw------- root root 179, 6 2013-07-04 18:28 mmcblk0p6
brw-rw---- system radio 179, 7 2013-07-04 18:28 mmcblk0p7
brw------- root root 179, 8 2013-07-04 18:28 mmcblk0p8
brw------- root root 179, 9 2013-07-04 18:28 mmcblk0p9
brw------- root root 179, 16 2013-07-04 18:28 mmcblk1
brw------- root root 179, 17 2013-07-04 18:28 mmcblk1p1
lrwxrwxrwx root root 2013-07-04 18:28 param -> /dev/block/mmcblk0p4
drwxr-xr-x root root 2013-07-04 18:28 platform
brw------- root root 1, 0 2013-07-04 18:28 ram0
brw------- root root 1, 1 2013-07-04 18:28 ram1
brw------- root root 1, 10 2013-07-04 18:28 ram10
brw------- root root 1, 11 2013-07-04 18:28 ram11
brw------- root root 1, 12 2013-07-04 18:28 ram12
brw------- root root 1, 13 2013-07-04 18:28 ram13
brw------- root root 1, 14 2013-07-04 18:28 ram14
brw------- root root 1, 15 2013-07-04 18:28 ram15
brw------- root root 1, 2 2013-07-04 18:28 ram2
brw------- root root 1, 3 2013-07-04 18:28 ram3
brw------- root root 1, 4 2013-07-04 18:28 ram4
brw------- root root 1, 5 2013-07-04 18:28 ram5
brw------- root root 1, 6 2013-07-04 18:28 ram6
brw------- root root 1, 7 2013-07-04 18:28 ram7
brw------- root root 1, 8 2013-07-04 18:28 ram8
brw------- root root 1, 9 2013-07-04 18:28 ram9
drwx------ root root 2013-07-04 18:28 vold
brw------- root root 253, 0 2013-07-04 18:28 zram0
/dev/block/platform:
drwxr-xr-x root root 2013-07-04 18:28 dw_mmc
drwxr-xr-x root root 2013-07-04 18:28 s3c-sdhci.2
/dev/block/platform/dw_mmc:
drwxr-xr-x root root 2013-07-04 18:28 by-name
drwxr-xr-x root root 2013-07-04 18:28 by-num
lrwxrwxrwx root root 2013-07-04 18:28 mmcblk0 -> /dev/block/mmcblk0
lrwxrwxrwx root root 2013-07-04 18:28 mmcblk0p1 -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 2013-07-04 18:28 mmcblk0p10 -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 2013-07-04 18:28 mmcblk0p11 -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 2013-07-04 18:28 mmcblk0p12 -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 2013-07-04 18:28 mmcblk0p2 -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 2013-07-04 18:28 mmcblk0p3 -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 2013-07-04 18:28 mmcblk0p4 -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 2013-07-04 18:28 mmcblk0p5 -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 2013-07-04 18:28 mmcblk0p6 -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 2013-07-04 18:28 mmcblk0p7 -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 2013-07-04 18:28 mmcblk0p8 -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 2013-07-04 18:28 mmcblk0p9 -> /dev/block/mmcblk0p9
/dev/block/platform/dw_mmc/by-name:
lrwxrwxrwx root root 2013-07-04 18:28 BOOT -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 2013-07-04 18:28 BOTA0 -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 2013-07-04 18:28 BOTA1 -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 2013-07-04 18:28 CACHE -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 2013-07-04 18:28 EFS -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 2013-07-04 18:28 HIDDEN -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 2013-07-04 18:28 OTA -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 2013-07-04 18:28 PARAM -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 2013-07-04 18:28 RADIO -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 2013-07-04 18:28 RECOVERY -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 2013-07-04 18:28 SYSTEM -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 2013-07-04 18:28 USERDATA -> /dev/block/mmcblk0p12
/dev/block/platform/dw_mmc/by-num:
lrwxrwxrwx root root 2013-07-04 18:28 p1 -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 2013-07-04 18:28 p10 -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 2013-07-04 18:28 p11 -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 2013-07-04 18:28 p12 -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 2013-07-04 18:28 p2 -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 2013-07-04 18:28 p3 -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 2013-07-04 18:28 p4 -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 2013-07-04 18:28 p5 -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 2013-07-04 18:28 p6 -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 2013-07-04 18:28 p7 -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 2013-07-04 18:28 p8 -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 2013-07-04 18:28 p9 -> /dev/block/mmcblk0p9
/dev/block/platform/s3c-sdhci.2:
drwxr-xr-x root root 2013-07-04 18:28 by-num
lrwxrwxrwx root root 2013-07-04 18:28 mmcblk1 -> /dev/block/mmcblk1
lrwxrwxrwx root root 2013-07-04 18:28 mmcblk1p1 -> /dev/block/mmcblk1p1
/dev/block/platform/s3c-sdhci.2/by-num:
lrwxrwxrwx root root 2013-07-04 18:28 p1 -> /dev/block/mmcblk1p1
/dev/block/vold:
brw------- root root 179, 16 2013-07-04 18:28 179:16
brw------- root root 179, 17 2013-07-04 18:28 179:17
--------------------------------------------------------------
Code:
su
df
Code:
Filesystem Size Used Free Blksize
/dev 414M 80.0K 414M 4096
/mnt/secure 414M 0.00K 414M 4096
/mnt/asec 414M 0.00K 414M 4096
/mnt/obb 414M 0.00K 414M 4096
/system 1.48G 1.15G 337M 4096
/efs 19.7M 8.36M 11.3M 4096
/cache 1007M 17.4M 990M 4096
/data 11.4G 10.9G 462M 4096
/mnt/shell/emulated 11.3G 10.9G 362M 4096
/preload 551M 9.22M 541M 4096
/storage/extSdCard 1.83G 398M 1.44G 32768
/mnt/secure/asec 1.83G 398M 1.44G 32768
--------------------------------------------------------------
Code:
su
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/secure tmpfs rw,relatime,mode=700 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/mmcblk0p9 /system ext4 ro,noatime,errors=panic,barrier=1,data=ordered 0 0
/dev/block/mmcblk0p3 /efs ext4 rw,nosuid,nodev,noatime,barrier=1,journal_async_commit,data=ordered,noauto_da_alloc,discard 0 0
/dev/block/mmcblk0p8 /cache ext4 rw,nosuid,nodev,noatime,errors=panic,barrier=1,journal_async_commit,data=ordered,noauto_da_alloc,discard 0 0
/dev/block/mmcblk0p12 /data ext4 rw,nosuid,nodev,noatime,barrier=1,journal_async_commit,data=ordered,noauto_da_alloc,discard 0 0
/sys/kernel/debug /sys/kernel/debug debugfs rw,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
none /dev/memcgrp cgroup rw,relatime,memory 0 0
/dev/block/mmcblk0p10 /preload ext4 ro,nosuid,nodev,noatime,barrier=1,data=ordered 0 0
/dev/block/vold/179:17 /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
/dev/block/vold/179:17 /mnt/secure/asec 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,relatime,size=0k,mode=000 0 0
Additional links:
[GUIDE] Making Dump Files Out of Android Device Partitions
Code:
su
find /dev/block/platform/ -name 'mmc*' -exec fdisk -l {} \;
Code:
Disk /dev/block/platform/s3c-sdhci.2/mmcblk1p1: 1966 MB, 1966080000 bytes
4 heads, 16 sectors/track, 60000 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Device Boot Start End Blocks Id System
Disk /dev/block/platform/s3c-sdhci.2/mmcblk1: 1967 MB, 1967128576 bytes
256 heads, 63 sectors/track, 238 cylinders
Units = cylinders of 16128 * 512 = 8257536 bytes
Device Boot Start End Blocks Id System
/dev/block/platform/s3c-sdhci.2/mmcblk1p1 * 1 239 1920000 c Win95 FAT32 (LBA)
Partition 1 has different physical/logical beginnings (non-Linux?):
phys=(1023, 255, 63) logical=(0, 32, 33)
Partition 1 has different physical/logical endings:
phys=(1023, 255, 63) logical=(238, 56, 56)
Disk /dev/block/platform/dw_mmc/mmcblk0p12: 12.3 GB, 12381585408 bytes
4 heads, 16 sectors/track, 377856 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Disk /dev/block/platform/dw_mmc/mmcblk0p12 doesn't contain a valid partition table
Disk /dev/block/platform/dw_mmc/mmcblk0p11: 8 MB, 8388608 bytes
4 heads, 16 sectors/track, 256 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Disk /dev/block/platform/dw_mmc/mmcblk0p11 doesn't contain a valid partition table
Disk /dev/block/platform/dw_mmc/mmcblk0p10: 587 MB, 587202560 bytes
4 heads, 16 sectors/track, 17920 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Disk /dev/block/platform/dw_mmc/mmcblk0p10 doesn't contain a valid partition table
Disk /dev/block/platform/dw_mmc/mmcblk0p9: 1610 MB, 1610612736 bytes
4 heads, 16 sectors/track, 49152 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Disk /dev/block/platform/dw_mmc/mmcblk0p9 doesn't contain a valid partition table
Disk /dev/block/platform/dw_mmc/mmcblk0p8: 1073 MB, 1073741824 bytes
4 heads, 16 sectors/track, 32768 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Disk /dev/block/platform/dw_mmc/mmcblk0p8 doesn't contain a valid partition table
Disk /dev/block/platform/dw_mmc/mmcblk0p7: 33 MB, 33554432 bytes
4 heads, 16 sectors/track, 1024 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Disk /dev/block/platform/dw_mmc/mmcblk0p7 doesn't contain a valid partition table
Disk /dev/block/platform/dw_mmc/mmcblk0p6: 8 MB, 8388608 bytes
4 heads, 16 sectors/track, 256 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Disk /dev/block/platform/dw_mmc/mmcblk0p6 doesn't contain a valid partition table
Disk /dev/block/platform/dw_mmc/mmcblk0p5: 8 MB, 8388608 bytes
4 heads, 16 sectors/track, 256 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Disk /dev/block/platform/dw_mmc/mmcblk0p5 doesn't contain a valid partition table
Disk /dev/block/platform/dw_mmc/mmcblk0p4: 8 MB, 8388608 bytes
4 heads, 16 sectors/track, 256 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Disk /dev/block/platform/dw_mmc/mmcblk0p4 doesn't contain a valid partition table
Disk /dev/block/platform/dw_mmc/mmcblk0p3: 20 MB, 20971520 bytes
4 heads, 16 sectors/track, 640 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Disk /dev/block/platform/dw_mmc/mmcblk0p3 doesn't contain a valid partition table
Disk /dev/block/platform/dw_mmc/mmcblk0p2: 4 MB, 4194304 bytes
4 heads, 16 sectors/track, 128 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Disk /dev/block/platform/dw_mmc/mmcblk0p2 doesn't contain a valid partition table
Disk /dev/block/platform/dw_mmc/mmcblk0p1: 4 MB, 4194304 bytes
4 heads, 16 sectors/track, 128 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Disk /dev/block/platform/dw_mmc/mmcblk0p1 doesn't contain a valid partition table
Disk /dev/block/platform/dw_mmc/mmcblk0: 15.7 GB, 15758000128 bytes
1 heads, 16 sectors/track, 1923584 cylinders
Units = cylinders of 16 * 512 = 8192 bytes
Device Boot Start End Blocks Id System
/dev/block/platform/dw_mmc/mmcblk0p1 1 1923584 15388671+ ee EFI GPT
Partition 1 does not end on cylinder boundary
scandiun said:
Code:
su
ls -lR /dev
...
Click to expand...
Click to collapse
Is partition RADIO where the modem goes when you flash a new one? What about the CSC files?
I'm just curious. I've upgrade to Sammy 4.3 to get the new modem/EFS and just reverted to a CM11 nandroid backup I had done *before* the upgrade. EFS is not backed up by CWM for sure. I don't know about the modem, but I guess it won't go into the /system folder.
Thanks!
Each device had it's own partition layout which says where radio goes.
Changing csc code wipes your device.
I managed to get the system folder. Via http://forum.xda-developers.com/showthread.php?t=1578099
CWM
Instructions and discussion available here
Click to expand...
Click to collapse
CWM Flashable Recovery
Both have been tested by me
Stock Recovery
CWM 6.0.3.6 by Unjustified Dev
Click to expand...
Click to collapse
DOWNLOAD:
System.img (/dev/block/mmcblk0p22)
Boot.img (/dev/block/mmcblk0p20)
Recovery.img (/dev/block/mmcblk0p21)
Modem.img - T599UVAMB5 (/dev/block/mmcblk0p12)
modem.bin (/dev/block/mmcblk0p16)
param.lfs (/dev/block/mmcblk0p19)
Preload.img (/dev/block/mmcblk0p24)
efs.img (/dev/block/mmcblk0p11)
Click to expand...
Click to collapse
Hmmm... can you explain me what is that? Thx
Feyerabend said:
Hmmm... can you explain me what is that? Thx
Click to expand...
Click to collapse
It is for development purposes. It is basically the stock firmware minus the kernel and recovery.
goldfingerfif said:
I uploaded the system tar its almost 1GB I cannot pull the Kernel though.
I managed to get the system folder. Via http://forum.xda-developers.com/showthread.php?t=1578099
If someone can assist with getting the kernel without root I would be forever grateful. If it is unpossible then please let me know as well as I cannot find a root method that works.
Click to expand...
Click to collapse
So, what you basicly need is someone with linux who can make a system.img from this, and add supersu and su binary?
And then someone who makes a factoryreset and flash it in odin I guess..
That person might then be able to extract recovery.img and boot.img. Am I right?
tys0n said:
So, what you basicly need is someone with linux who can make a system.img from this, and add supersu and su binary?
And then someone who makes a factoryreset and flash it in odin I guess..
That person might then be able to extract recovery.img and boot.img. Am I right?
Click to expand...
Click to collapse
You don’t NEED linux, you can use Cygwin with windows, but yes someone can then make system.img or system.tar.md5 with supersu and su.
From there if a root shell is obtained recovery and boot partitions should be able to be extracted from the phone.
Then insecure kernel and custom recovery can be installed.
I’ve done something like this with the T989 but this phone is for someone at my work and so bricking is an issue unlike if it was a personal phone as well there is less motivation to do it if it isn’t mine.
goldfingerfif said:
You don’t NEED linux, you can use Cygwin with windows, but yes someone can then make system.img or system.tar.md5 with supersu and su.
From there if a root shell is obtained recovery and boot partitions should be able to be extracted from the phone.
Then insecure kernel and custom recovery can be installed.
I’ve done something like this with the T989 but this phone is for someone at my work and so bricking is an issue unlike if it was a personal phone as well there is less motivation to do it if it isn’t mine.
Click to expand...
Click to collapse
Somethimg like this I guess? http://forum.xda-developers.com/showthread.php?t=1081239&highlight=odin
tys0n said:
Somethimg like this I guess? http://forum.xda-developers.com/showthread.php?t=1081239&highlight=odin
Click to expand...
Click to collapse
Yes just like that minus the need to unpack it because it is just a tarball so 7zip or whatever should open it fine. I am at work but I believe my home computer has either a linux vm installed or Cygwin with dsixda’s kitchen.
I should be able to manually or through dsixda’s kitchen add supersu and su convert to a odin img and flash.
If it successfully roots so I can at least get a rooted shell so I can dd if=/dev/block/….. of=/sdcard/…img to get a recovery.img and boot.img then carefully cook up a TWRP or CWM recovery to flash then make a “custom” or modified stock rom to flash with insecured kernel.
Anything new on how this is going?
thecasual01 said:
Anything new on how this is going?
Click to expand...
Click to collapse
I added SuperSU.apk and su binary.
Scared to flash it without a known good working factory image. Need to read up on a couple things a little more like triple check I can flash just the system partition without boot, etc.
goldfingerfif said:
I added SuperSU.apk and su binary.
Scared to flash it without a known good working factory image. Need to read up on a couple things a little more like triple check I can flash just the system partition without boot, etc.
Click to expand...
Click to collapse
Excuse me if this may come across as stupid or ignorant, but to my understanding the SGH-T599 seems to be an alternative version of the S3 Mini , I think the main difference is the screen size? That being said, can you not use the current existing kernel, boot.img of the S3 mini? I'm basing this off the fact that I had soft-bricked my phone by attempting to flash CWM Recovery but it didn't work, and I couldn't get myself the stock recovery.img file so in an attempt to revive my phone, I substituted that with the S3 mini's and it worked. Although at first every time i turned on and off the phone it displayed noise (TV Static) but it no longer does so.
I would offer being a test monkey, but this is my only phone and I do not have any other phones that I could use in the scenario it does get bricked.
goldfingerfif said:
I added SuperSU.apk and su binary.
Scared to flash it without a known good working factory image. Need to read up on a couple things a little more like triple check I can flash just the system partition without boot, etc.
Click to expand...
Click to collapse
I think it will be fine to flash system.img only as long as you don't use any pit and repartition. Factory reset first to prevent bootloops.
tamil.soljahz said:
Excuse me if this may come across as stupid or ignorant, but to my understanding the SGH-T599 seems to be an alternative version of the S3 Mini , I think the main difference is the screen size? That being said, can you not use the current existing kernel, boot.img of the S3 mini? I'm basing this off the fact that I had soft-bricked my phone by attempting to flash CWM Recovery but it didn't work, and I couldn't get myself the stock recovery.img file so in an attempt to revive my phone, I substituted that with the S3 mini's and it worked. Although at first every time i turned on and off the phone it displayed noise (TV Static) but it no longer does so.
I would offer being a test monkey, but this is my only phone and I do not have any other phones that I could use in the scenario it does get bricked.
Click to expand...
Click to collapse
Are you saying you used a boot.img from s3 mini?
tamil.soljahz said:
Excuse me if this may come across as stupid or ignorant, but to my understanding the SGH-T599 seems to be an alternative version of the S3 Mini , I think the main difference is the screen size? That being said, can you not use the current existing kernel, boot.img of the S3 mini? I'm basing this off the fact that I had soft-bricked my phone by attempting to flash CWM Recovery but it didn't work, and I couldn't get myself the stock recovery.img file so in an attempt to revive my phone, I substituted that with the S3 mini's and it worked. Although at first every time i turned on and off the phone it displayed noise (TV Static) but it no longer does so.
I would offer being a test monkey, but this is my only phone and I do not have any other phones that I could use in the scenario it does get bricked.
Click to expand...
Click to collapse
What exactly did you use to get it up and running, just the recovery.img, system.img, or boot.img (kernel) you flashed or some combo?
Looks like processor, screen and possibly bluetooth are different
T-599 vs i8190
goldfingerfif said:
What exactly did you use to get it up and running, just the recovery.img, system.img, or boot.img (kernel) you flashed or some combo?
Looks like processor, screen and possibly bluetooth are different
T-599 vs i8190
Click to expand...
Click to collapse
I just flashed the recovery.img, and (incorrectly) came to the assumption that the boot.img and system.img would work on the phone as well. In fact, I realize I can't access recovery. I was asking whether that the S3 mini's boot.img would work on the T599V as well.
Also, according to this link: http://www.sammobile.com/2012/11/24/review-samsung-galaxy-s-iii-mini-gt-i8190-2/
it says the S3 mini uses the U8420 chipset as well, which is why I thought the phones were similar.
tamil.soljahz said:
I just flashed the recovery.img, and (incorrectly) came to the assumption that the boot.img and system.img would work on the phone as well. In fact, I realize I can't access recovery. I was asking whether that the S3 mini's boot.img would work on the T599V as well.
Also, according to this link: http://www.sammobile.com/2012/11/24/review-samsung-galaxy-s-iii-mini-gt-i8190-2/
it says the S3 mini uses the U8420 chipset as well, which is why I thought the phones were similar.
Click to expand...
Click to collapse
The site you linked doesn't mention the SGH-T599 just the GT-8190 and the GT-i9300, did you send the right link?
According to http://www.gsmchoice.com/en/catalogue/samsung/galaxyexhibit/ it's built on same board. ST-Ericsson U8420.
It' same for i8190, some sites say U8500 others say U8420.
The Cydia Impactor root method works on the T599, I just did it to mine. Stays rooted on reboot.
marksalot said:
The Cydia Impactor root method works on the T599, I just did it to mine. Stays rooted on reboot.
Click to expand...
Click to collapse
Cool
So, first guy who "dd" will be hero of the day
If partition layout is the same as i8190 it should look like this.
Code:
GT-I8190 PARTITION LAYOUT
Official Name * Fs * Mount point * Known as * Contents
/efs * ext4 * /dev/block/mmcblk0p11 * Efs folder *Device IMEI,mac address etc
/modemfs * ext4 * /dev/block/mmcblk0p12 * Radio *
/SdCcard * vfat * /dev/block/mmcblk1 /dev/block/mmcblk1p1 * Internal sd * Your stuff
/boot * emmc * /dev/block/mmcblk0p20 * kernel/zimage * Drivers etc
/recovery * emmc * /dev/block/mmcblk0p21 * Recovery partion * ??????
/system * ext4 * /dev/block/mmcblk0p22 * System folder * The operation system
/cache * ext4 * /dev/block/mmcblk0p23 * Cache partition * Update.zips csc,samsung and carriers customizations
/preload * ext4 * /dev/block/mmcblk0p24 * Hidden partition * Media files,apks etc from Samsung/carriers
/.lfs * j4fs * /dev/block/mmcblk0p19 * param.lfs ## * splash screen,charging animation download mode pngs, etc
/data * ext4 * /dev/block/mmcblk0p25 length=-16384 * data folder * Your download apps, current device and use, settings
/temp * ? * /dev/block/mmcblk0p5 * nedded to load *
* * * psccd and CSPSA *
* * * when reset is *
* * * triggered *
* * * *
* * * *
* *
* * * *
I guess boot, recovery, and param is most wanted
Here is the content of /proc/partitions
Code:
major minor #blocks name
7 0 5229 loop0
179 0 3866624 mmcblk0
179 1 128 mmcblk0p1
179 2 384 mmcblk0p2
179 3 1024 mmcblk0p3
179 4 1024 mmcblk0p4
179 5 512 mmcblk0p5
179 6 512 mmcblk0p6
179 7 512 mmcblk0p7
179 8 512 mmcblk0p8
179 9 1024 mmcblk0p9
179 10 1024 mmcblk0p10
179 11 16384 mmcblk0p11
179 12 16384 mmcblk0p12
179 13 16384 mmcblk0p13
179 14 51200 mmcblk0p14
179 15 64 mmcblk0p15
179 16 14336 mmcblk0p16
179 17 2048 mmcblk0p17
179 18 2048 mmcblk0p18
179 19 16384 mmcblk0p19
179 20 16384 mmcblk0p20
179 21 16384 mmcblk0p21
179 22 1228800 mmcblk0p22
179 23 737280 mmcblk0p23
179 24 102400 mmcblk0p24
179 25 1535983 mmcblk0p25
179 64 2048 mmcblk0boot1
179 32 2048 mmcblk0boot0
179 96 15637504 mmcblk1
179 97 15633408 mmcblk1p1
254 0 5229 dm-0
Here is the output of busybox df -h
I have a 16GB SD Card, apparently Maverick (GPS map app I installed) creates it's own partition.
Code:
busybox df -h
Filesystem Size Used Available Use% Mounted on
tmpfs 402.1M 112.0K 401.9M 0% /dev
tmpfs 402.1M 0 402.1M 0% /mnt/asec
tmpfs 402.1M 0 402.1M 0% /mnt/obb
tmpfs 402.1M 0 402.1M 0% /dev/shm
/dev/block/mmcblk0p22
1.2G 965.4M 215.7M 82% /system
/dev/block/mmcblk0p12
15.7M 4.3M 11.4M 28% /modemfs
/dev/block/mmcblk0p23
708.7M 12.0M 696.7M 2% /cache
/dev/block/mmcblk0p11
15.7M 4.5M 11.2M 29% /efs
/dev/block/mmcblk0p24
98.4M 11.6M 86.8M 12% /preload
/dev/block/mmcblk0p25
1.4G 1.3G 173.7M 88% /data
df: /mnt/.lfs: Function not implemented
/dev/fuse 1.3G 1.3G 73.7M 95% /storage/sdcard0
/dev/block/dm-0 5.0M 2.9M 2.1M 57% /mnt/asec/com.codesector.maverick.full-1
/dev/block/vold/179:97
14.9G 10.1G 4.8G 68% /storage/extSdCard
cat /proc/partitions gives me in I8190.
Code:
major minor #blocks name
7 0 16664 loop0
7 1 2111 loop1
7 2 5229 loop2
7 3 2111 loop3
7 4 2111 loop4
7 5 2111 loop5
7 6 2111 loop6
7 7 17703 loop7
179 0 7634944 mmcblk0
179 1 128 mmcblk0p1
179 2 384 mmcblk0p2
179 3 1024 mmcblk0p3
179 4 1024 mmcblk0p4
179 5 512 mmcblk0p5
179 6 512 mmcblk0p6
179 7 512 mmcblk0p7
179 8 512 mmcblk0p8
179 9 1024 mmcblk0p9
179 10 1024 mmcblk0p10
179 11 16384 mmcblk0p11
179 12 16384 mmcblk0p12
179 13 16384 mmcblk0p13
179 14 51200 mmcblk0p14
179 15 64 mmcblk0p15
179 16 14336 mmcblk0p16
179 17 2048 mmcblk0p17
179 18 2048 mmcblk0p18
179 19 16384 mmcblk0p19
179 20 16384 mmcblk0p20
179 21 16384 mmcblk0p21
179 22 1228800 mmcblk0p22
179 23 860160 mmcblk0p23
179 24 327680 mmcblk0p24
179 25 4945920 mmcblk0p25
179 64 2048 mmcblk0boot1
179 32 2048 mmcblk0boot0
179 96 15558144 mmcblk1
179 97 13473792 mmcblk1p1
179 98 2075648 mmcblk1p2
254 0 16663 dm-0
254 1 2110 dm-1
254 2 5229 dm-2
254 3 2110 dm-3
254 4 2110 dm-4
254 5 2110 dm-5
254 6 2110 dm-6
254 7 17703 dm-7
7 8 2111 loop8
254 8 2110 dm-8
7 9 26019 loop9
254 9 26019 dm-9
Looks like it matches pretty well
So, I used the Online Nandroid app, it detects the T599 as "codinatmo" and doesn't have a patch available.
Manually chose the "Samsung Galaxy S III mini GT-l8190" patch and installed.
Was able to back up boot.img and recovery.img, both 16MB.
Wheres the roms? This thing is finally rooted with recovery, are there any known working roms?
Sent from my VK810 4G using XDA Premium HD app
Chance77 said:
Wheres the roms? This thing is finally rooted with recovery, are there any known working roms?
Sent from my VK810 4G using XDA Premium HD app
Click to expand...
Click to collapse
Give it time, grasshopper. These things take time. There are just enough differences between the 500/501 and 810 and the dev's need time to mod the kernel, build and find testers.
Also, as far as I know, we don't have source for the VK810 yet so that may slow things down a bit.
Believe me, i'm also waiting on an AOSP / GPE experience to make this thing perfect.
LG already released source. https://www.lg.com/global/support/opensource/opensourceList?types=ALL&search=vk810
edgemaster191 said:
Give it time, grasshopper. These things take time. There are just enough differences between the 500/501 and 810 and the dev's need time to mod the kernel, build and find testers.
Also, as far as I know, we don't have source for the VK810 yet so that may slow things down a bit.
Believe me, i'm also waiting on an AOSP / GPE experience to make this thing perfect.
Click to expand...
Click to collapse
I wish I shared your optimism. I hope I'm wrong but it isn't looking good. The only reason we got TWRP support is because someone that has the other device helped with the 810. There seems to be next to no momentum on the 810 side. There just doesn't seem to be a lot of developers who have that device.
prana22 said:
I wish I shared your optimism. I hope I'm wrong but it isn't looking good. The only reason we got TWRP support is because someone that has the other device helped with the 810. There seems to be next to no momentum on the 810 side. There just doesn't seem to be a lot of developers who have that device.
Click to expand...
Click to collapse
I would do something but I have never even compiled CM11 let alone tweaked it to work with a new device. I can work with a developer who doesn't have one, but I don't know enough to do it on my own.
That is where I am as well. I know just enough to get myself in trouble.
Sent from my VK810 4G using XDA Free mobile app
anyone care to share a system dump of the VK810?
boot.img and system partition would be useful
my local verizon store refuses to sell it to me without a contract............ sigh
probably going to get it from amazon
Sure, how do I do that? <-- I am a noob
popezaphod said:
Sure, how do I do that? <-- I am a noob
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2450045
info about the various partitions,good reading: http://www.all-things-android.com/content/review-android-partition-layout
if you have the custom recovery installed, you could do a backup of the device from recovery and share the files
don't share your EFS partition because it contains your unique IMEI/ESN number, and sometimes devices break if you flash someone else's EFS partition. don't share your userdata partition obviously
(if you can't figure out which is the EFS partition from the WAY #2 image, or how to do a system dump, I just need the following partitions and partition layout)
What I need:
1) Following partitions
BOOT - contains ramdisk info necessary to compile a working boot image
RECOVERY - not that necessary, but more info is useful
SYSTEM - probably contains modem libraries not present in the v500 system partition
2) Partition Layout
needed to compile a working ROM
more info is better... so a complete system dump (minus EFS and userdata) would be great
thanks for helping...
Good Amount of Info
ro.product
Code:
[ro.product.board]: [MSM8960]
[ro.product.brand]: [lge]
[ro.product.cpu.abi2]: [armeabi]
[ro.product.cpu.abi]: [armeabi-v7a]
[ro.product.device]: [altev]
[ro.product.locale.language]: [en]
[ro.product.locale.region]: [US]
[ro.product.manufacturer]: [LGE]
[ro.product.model]: [VK810 4G]
[ro.product.name]: [altev_vzw]
[email protected]:/ # getprop | grep ro.build.
ro.build
Code:
[ro.build.characteristics]: [tablet]
[ro.build.date.utc]: [1392900914]
[ro.build.date]: [Thu Feb 20 21:55:14 KST 2014]
[ro.build.description]: [altev_vzw-user 4.2.2 JDQ39B VK81010C.1392900840 release
-keys]
[ro.build.display.id]: [JDQ39B]
[ro.build.fingerprint]: [lge/altev_vzw/altev:4.2.2/JDQ39B/VK81010C.1392900840:us
er/release-keys]
[ro.build.host]: [LGEARND9B11]
[ro.build.id]: [JDQ39B]
[ro.build.product]: [altev]
[ro.build.tags]: [release-keys]
[ro.build.target_country]: [US]
[ro.build.target_operator]: [VZW]
[ro.build.target_region]: [US]
[ro.build.type]: [user]
[ro.build.user]: [hyungjin.yoo]
[ro.build.version.codename]: [REL]
[ro.build.version.incremental]: [VK81010C.1392900840]
[ro.build.version.release]: [4.2.2]
[ro.build.version.sdk]: [17]
Stock aBoot img
https://www.dropbox.com/s/kf3fysyhvlyw8l0/aboot.img
Boot IMG w/ TWRP Installed(Not sure if that matters or not)
https://www.dropbox.com/s/egm0rp381cahbeo/boot.img
TWRP Recovory
https://www.dropbox.com/s/ypwreq1c07yj36v/VK810_twrp_2.7.0.1.zip
Recovory IMG w/ TWRP Installed
https://www.dropbox.com/s/23xy2o8qydqsunu/recovery.img
Stock build.prop
https://www.dropbox.com/s/4rqciye90mhp1cj/build.prop
Partitions
Code:
7 0 5229 loop0
7 1 22901 loop1
179 0 15388672 mmcblk0
179 1 65536 mmcblk0p1
179 2 512 mmcblk0p2
179 3 512 mmcblk0p3
179 4 2048 mmcblk0p4
179 5 2048 mmcblk0p5
179 6 512 mmcblk0p6
179 7 24576 mmcblk0p7
179 8 512 mmcblk0p8
179 9 1 mmcblk0p9
179 10 3072 mmcblk0p10
179 11 3072 mmcblk0p11
179 12 780 mmcblk0p12
179 13 780 mmcblk0p13
179 14 780 mmcblk0p14
179 15 8192 mmcblk0p15
179 16 8192 mmcblk0p16
179 17 8 mmcblk0p17
179 18 16384 mmcblk0p18
179 19 16384 mmcblk0p19
179 20 8192 mmcblk0p20
179 21 512 mmcblk0p21
179 22 512 mmcblk0p22
179 23 2195456 mmcblk0p23
179 24 1392640 mmcblk0p24
179 25 8192 mmcblk0p25
179 26 262144 mmcblk0p26
179 27 24576 mmcblk0p27
179 28 3072 mmcblk0p28
179 29 8 mmcblk0p29
179 30 32768 mmcblk0p30
179 31 512 mmcblk0p31
259 0 512 mmcblk0p32
259 1 8 mmcblk0p33
259 2 16384 mmcblk0p34
259 3 11247616 mmcblk0p35
259 4 4079 mmcblk0p36
254 0 5229 dm-0
254 1 22900 dm-1
lrwxrwxrwx root root 1970-01-13 12:13 DDR -> /dev/block/mmcblk0p29
lrwxrwxrwx root root 1970-01-13 12:13 aboot -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 1970-01-13 12:13 bnr -> /dev/block/mmcblk0p20
lrwxrwxrwx root root 1970-01-13 12:13 boot -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 1970-01-13 12:13 cache -> /dev/block/mmcblk0p24
lrwxrwxrwx root root 1970-01-13 12:13 drm -> /dev/block/mmcblk0p15
lrwxrwxrwx root root 1970-01-13 12:13 eksst -> /dev/block/mmcblk0p22
lrwxrwxrwx root root 1970-01-13 12:13 encrypt -> /dev/block/mmcblk0p21
lrwxrwxrwx root root 1970-01-13 12:13 factory -> /dev/block/mmcblk0p19
lrwxrwxrwx root root 1970-01-13 12:13 fota -> /dev/block/mmcblk0p30
lrwxrwxrwx root root 1970-01-13 12:13 fsg -> /dev/block/mmcblk0p28
lrwxrwxrwx root root 1970-01-13 12:13 grow -> /dev/block/mmcblk0p36
lrwxrwxrwx root root 1970-01-13 12:13 m9kefs1 -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 1970-01-13 12:13 m9kefs2 -> /dev/block/mmcblk0p13
lrwxrwxrwx root root 1970-01-13 12:13 m9kefs3 -> /dev/block/mmcblk0p14
lrwxrwxrwx root root 1970-01-13 12:13 misc -> /dev/block/mmcblk0p18
lrwxrwxrwx root root 1970-01-13 12:13 modem -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 1970-01-13 12:13 modemst1 -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 1970-01-13 12:13 modemst2 -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 1970-01-13 12:13 pad -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 1970-01-13 12:13 persist -> /dev/block/mmcblk0p25
lrwxrwxrwx root root 1970-01-13 12:13 rct -> /dev/block/mmcblk0p33
lrwxrwxrwx root root 1970-01-13 12:13 recovery -> /dev/block/mmcblk0p27
lrwxrwxrwx root root 1970-01-13 12:13 reserved -> /dev/block/mmcblk0p34
lrwxrwxrwx root root 1970-01-13 12:13 rpm -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 1970-01-13 12:13 rpmbak -> /dev/block/mmcblk0p32
lrwxrwxrwx root root 1970-01-13 12:13 sbl1 -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 1970-01-13 12:13 sbl2 -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 1970-01-13 12:13 sbl3 -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 1970-01-13 12:13 sns -> /dev/block/mmcblk0p16
lrwxrwxrwx root root 1970-01-13 12:13 ssd -> /dev/block/mmcblk0p17
lrwxrwxrwx root root 1970-01-13 12:13 system -> /dev/block/mmcblk0p23
lrwxrwxrwx root root 1970-01-13 12:13 tombstones -> /dev/block/mmcblk0p26
lrwxrwxrwx root root 1970-01-13 12:13 tz -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 1970-01-13 12:13 tzbak -> /dev/block/mmcblk0p31
lrwxrwxrwx root root 1970-01-13 12:13 userdata -> /dev/block/mmcblk0p35
Right now I have a lot of stuff removed from my rom but I do have a stock backup so later I will revert back and and post partition images.
As for stock recovery.img and stock boot.img, I do not have that so maybe someone else can grab that for us that didn't install TWRP yet(Didn't even think of getting it before I installed it and would be nice to have to go back to stock for warranty exchange)
Also let me know of anything else I can do to help you. Thank You
NICG said:
Right now I have a lot of stuff removed from my rom but I do have a stock backup so later I will revert back and and post partition images.
As for stock recovery.img and stock boot.img, I do not have that so maybe someone else can grab that for us that didn't install TWRP yet(Didn't even think of getting it before I installed it and would be nice to have to go back to stock for warranty exchange)
Also let me know of anything else I can do to help you. Thank You
Click to expand...
Click to collapse
Thanks for posting....
Slightly strange values...
VK810 (LTE):
Code:
BOARD_BOOTIMAGE_PARTITION_SIZE := 25165824 # 24M
BOARD_RECOVERYIMAGE_PARTITION_SIZE := 25165824 # 24M
BOARD_SYSTEMIMAGE_PARTITION_SIZE := 2248146944 # 2114M
BOARD_USERDATAIMAGE_PARTITION_SIZE := 11517558784 #10984
BOARD_FLASH_BLOCK_SIZE := 131072 # (BOARD_KERNEL_PAGESIZE * 64)
V500 (wifi):
Code:
BOARD_BOOTIMAGE_PARTITION_SIZE := 23068672 # 22M
BOARD_RECOVERYIMAGE_PARTITION_SIZE := 23068672 # 22M
BOARD_SYSTEMIMAGE_PARTITION_SIZE := 880803840 # 840M
BOARD_USERDATAIMAGE_PARTITION_SIZE := 6189744128 # 5.9G
BOARD_FLASH_BLOCK_SIZE := 131072 # (BOARD_KERNEL_PAGESIZE * 64)
can you post the output of the below command? Want to verify the BOARD_FLASH_BLOCK_SIZE settings
cat /proc/mtd
EDIT1:
Who wants to be a guinea pig for my first cm-11.0 build? (requires you to have TWRP recovery)
0) Post here saying that you are testing the ROM. If someone else posted, then wait and see what happens
1) Perform a backup in TWRP recovery
2) Did I say to perform a backup?
3) Flash the cm-11 zip file in TWRP recovery. the boot.img is already LOKI patched
<removed>
4) Reboot
See if the device starts up properly.
If it doesn't, then go back to TWRP recovery and restore your backup
Risky? Maybe. If you are afraid, then don't flash it and wait for someone else to do it.....
I tested the download and it seems there is a device name mismatch somewhere:
installing '/extenal_sd/cm-11-20140512-UNOFFICIAL-vk810_loki.zip'
checking for MD5 file...
skipping MD5 check no MD5 file found
This package is for "vk810" devices; this is a "altev"
E: Error executing updater binary in zip
error flashing zip
failed
traccdma said:
I tested the download and it seems there is a device name mismatch somewhere:
installing '/extenal_sd/cm-11-20140512-UNOFFICIAL-vk810_loki.zip'
checking for MD5 file...
skipping MD5 check no MD5 file found
This package is for "vk810" devices; this is a "altev"
E: Error executing updater binary in zip
error flashing zip
failed
Click to expand...
Click to collapse
probably.... vk810 is the device name, altev is the model/board/product name... probably a mismatch somewhere.....
I'll recompile when I get home
(v500 = awifi = wifi only version, v510 = palman = GPE version)
paperWastage said:
probably.... vk810 is the device name, altev is the model/board/product name... probably a mismatch somewhere.....
I'll recompile when I get home
(v500 = awifi = wifi only version, v510 = palman = GPE version)
Click to expand...
Click to collapse
i think we should stick with v500/v510/vk810 convention.....
http://forum.xda-developers.com/showpost.php?p=48103469&postcount=22
from this, it looks like the recovery image needs to be fixed...
http://forum.xda-developers.com/showpost.php?p=48331517&postcount=10
for now, I've manually edited the META-INF/com/google/android/updater-script to include "altev" as part of the check
0) Post here saying that you are testing the ROM. If someone else posted, then wait and see what happens
1) Perform a backup in TWRP recovery
2) Did I say to perform a backup?
3) Flash the cm-11 zip file in TWRP recovery. the boot.img will be LOKI-patched during the flash (which means don't use my previous upload where I pre-patched the boot.img)
http://d-h.st/tAq
4) Reboot
See if the device starts up properly.
If it doesn't, then go back to TWRP recovery and restore your backup
Risky? Maybe. If you are afraid, then don't flash it and wait for someone else to do it.....
with cm-11-20140513-unofficial-vk810.zip:
set_metadata_recursive: some changes failed
E: error executing updater binary in zip
error flashing zip
updating partition details...
tried booting it anyway and it brings up LG logo once, powers off/back on, and boots up to recovery (TWRP) on its own
traccdma said:
with cm-11-20140513-unofficial-vk810.zip:
set_metadata_recursive: some changes failed
E: error executing updater binary in zip
error flashing zip
updating partition details...
tried booting it anyway and it brings up LG logo once, powers off/back on, and boots up to recovery (TWRP) on its own
Click to expand...
Click to collapse
http://www.xda-developers.com/android/how-to-fix-a-broken-rom-flash-in-certain-kitkat-roms/
hmm, not sure why TWRP is complaining. need to investigate tomorrow. if the update_script failed, then the boot.img wasn't patched, so the new boot image won't boot at all.
were you able to restore from nandroid backup?
you also try replacing the update-binary in the ROM with this
http://forum.xda-developers.com/showthread.php?t=2532300
that got much further and even booted into CyanogenMod 11 with the VZW Gpad V810!!
After unzipping your file, overwriting the update-binary file in meta-inf\com\google\android with the file from the thread you posted, it said successful. Rebooted once while it said Android is updating app xxx of xxx, then Welcome to CyanogenMod
Seems to be missing drivers though. First boot seemed stable except it didn't recognize Verizon mobile data (or SIM card). I was in there at least 10 minutes. In settings, I used the slider to try and turn on wifi, but it never turned blue and a few seconds later it reverted back off. I slid bluetooth on, and it did the same thing and went into a boot loop. It gets to the android desktop for about 5 seconds then reboots. I wiped cache and dalvik cache and it got no further.
traccdma said:
with cm-11-20140513-unofficial-vk810.zip:
set_metadata_recursive: some changes failed
E: error executing updater binary in zip
error flashing zip
updating partition details...
tried booting it anyway and it brings up LG logo once, powers off/back on, and boots up to recovery (TWRP) on its own
Click to expand...
Click to collapse
whenever that happens get a recovery log, They are very helpful
traccdma said:
that got much further and even booted into CyanogenMod 11 with the VZW Gpad V810!!
After unzipping your file, overwriting the update-binary file in meta-inf\com\google\android with the file from the thread you posted, it said successful. Rebooted once while it said Android is updating app xxx of xxx, then Welcome to CyanogenMod
Seems to be missing drivers though. First boot seemed stable except it didn't recognize Verizon mobile data (or SIM card). I was in there at least 10 minutes. In settings, I used the slider to try and turn on wifi, but it never turned blue and a few seconds later it reverted back off. I slid bluetooth on, and it did the same thing and went into a boot loop. It gets to the android desktop for about 5 seconds then reboots. I wiped cache and dalvik cache and it got no further.
Click to expand...
Click to collapse
good to hear...
need two things:
system dump of stock ROM.
The proprietary libs I'm using right now is from v500 which probably doesn't have the radio libs. maybe wifi/bt driver is different too
logs
As Drgravy said, logs are helpful. Recovery log, /proc/last_kmsg from kernel boot, ...
Sorry been a little busy but here you go.
Stock Rooted System IMG
https://www.dropbox.com/s/rpxmbp1lgb5a4k9/system.img
Hi all,
I successfuly root my samsung tab 4 7.0 sm-t231 8GB.
Next step i want to backup my efs.img, nvm.img and modem.img from android terminal emulator
[email protected]:/ $ su
[email protected]:/ # ls -al /dev/block/platform/soc.2/by-name
lrwxrwxrwx root root 2014-07-13 03:44 CACHE -> /dev/block/mmcblk0p14
lrwxrwxrwx root root 2014-07-13 03:44 EFS -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 2014-07-13 03:44 HIDDEN -> /dev/block/mmcblk0p13
lrwxrwxrwx root root 2014-07-13 03:44 KERNEL -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 2014-07-13 03:44 LOKE1ST -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 2014-07-13 03:44 LOKE2ND -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 2014-07-13 03:44 MEP2 -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 2014-07-13 03:44 MODEM -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 2014-07-13 03:44 MRD -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 2014-07-13 03:44 MRD_BK -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 2014-07-13 03:44 NVM -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 2014-07-13 03:44 PARAM -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 2014-07-13 03:44 RECOVERY -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 2014-07-13 03:44 RESERVE -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 2014-07-13 03:44 SYSTEM -> /dev/block/mmcblk0p15
lrwxrwxrwx root root 2014-07-13 03:44 USER -> /dev/block/mmcblk0p16
[email protected]:/ # cat /proc/partitions
major minor #blocks name
179 0 7634944 mmcblk0
179 1 2048 mmcblk0p1
179 2 2048 mmcblk0p2
179 3 2048 mmcblk0p3
179 4 20480 mmcblk0p4
179 5 14336 mmcblk0p5
179 6 1536 mmcblk0p6
179 7 1536 mmcblk0p7
179 8 16384 mmcblk0p8
179 9 16384 mmcblk0p9
179 10 16384 mmcblk0p10
179 11 24576 mmcblk0p11
179 12 16384 mmcblk0p12
179 13 51200 mmcblk0p13
179 14 204800 mmcblk0p14
179 15 2024448 mmcblk0p15
179 16 5214208 mmcblk0p16
179 72 4096 mmcblk0rpmb
179 48 4096 mmcblk0boot1
179 24 4096 mmcblk0boot0
253 0 512000 zram0
179 120 15558144 mmcblk1
179 121 15557120 mmcblk1p1
then in ATE i type this for backup:
dd if=/dev/block/mmcblk0p4 of=/mnt/extSdCard/EFS.img
dd if=/dev/block/mmcblk0p11 of=/mnt/extSdCard/MODEM.img
dd if=/dev/block/mmcblk0p12 of=/mnt/extSdCard/NVM.img
next i want to backup samsung sm-t231 8GB pit file then i type this in ATE
dd if=/dev/block/mmcblk0 of=/mnt/extSdCard/out.pit bs=8 count=481 skip=2176
my question
anyone can confirm PIT parameters for bs, count and skip for galaxy tab 4 7.0 sm-t231 8GB
was right?
Can you please tell me how you rooted your tab?? I have tried a lot of methods but none of them seem to work.i have the samsung tab 4 7.0 sm-t231 8GB.
Hi
This thread is for cm13 on j700p testers to test the builds and report bugs , i don't test any of those builds posted here as i don't own a j700p device .
Download :
Alpha 1:
https://www.mediafire.com/download/a4w8sdezzs8umti
Alpha 2 :
http://forum.xda-developers.com/showpost.php?p=68886823&postcount=6
Alpha 3 :
http://forum.xda-developers.com/showpost.php?p=69014807&postcount=31
How to report bugs :
-Type a list of the bugs u have
- attach a logcat using syslog app [ download from here https://play.google.com/store/apps/details?id=com.tortel.syslog ]
Regards
I will test it out when i can get a copy of the EFS partition.
kernel is not seandroid enforcing
and that's it
stuck on samsung galaxy j7 logo
minz1 said:
kernel is not seandroid enforcing
and that's it
stuck on samsung galaxy j7 logo
Click to expand...
Click to collapse
Ok thank you for reporting , the kernel need some work. ..
minz1 said:
I will test it out when i can get a copy of the EFS partition.
Click to expand...
Click to collapse
You have ril broken ?
Alpha 2
https://www.mediafire.com/download/wh59bpspwlh9cbu
Changelog :
Force permissive selinux
Some cm patches
trying it out now messi
---------- Post added at 01:57 AM ---------- Previous post was at 01:31 AM ----------
didnt work even on the alpha build it stays at the j7 screen I used TWRP to flash it
Starchild2k said:
trying it out now messi
---------- Post added at 01:57 AM ---------- Previous post was at 01:31 AM ----------
didnt work even on the alpha build it stays at the j7 screen I used TWRP to flash it
Click to expand...
Click to collapse
Maybe it's a problem with the partitions size , you can check it by running :
cat /proc/mtd
And
cat /proc/partitions in adb
And post the results here
messi2050 said:
Maybe it's a problem with the partitions size , you can check it by running :
cat /proc/mtd
And
cat /proc/partitions in adb
And post the results here
Click to expand...
Click to collapse
179 0 15388672 mmcblk0
179 1 15360 mmcblk0p1
179 2 58816 mmcblk0p2
179 3 512 mmcblk0p3
179 4 32 mmcblk0p4
179 5 2048 mmcblk0p5
179 6 512 mmcblk0p6
179 7 768 mmcblk0p7
179 8 512 mmcblk0p8
179 9 3072 mmcblk0p9
179 10 16 mmcblk0p10
179 11 10512 mmcblk0p11
179 12 10240 mmcblk0p12
179 13 14336 mmcblk0p13
179 14 3072 mmcblk0p14
179 15 3072 mmcblk0p15
179 16 13312 mmcblk0p16
179 17 15360 mmcblk0p17
179 18 12289 mmcblk0p18
179 19 7159 mmcblk0p19
179 20 3072 mmcblk0p20
179 21 8 mmcblk0p21
179 22 8192 mmcblk0p22
179 23 1024 mmcblk0p23
179 24 9216 mmcblk0p24
179 25 3217408 mmcblk0p25
179 26 307200 mmcblk0p26
179 27 46080 mmcblk0p27
179 28 11621356 mmcblk0p28
179 32 4096 mmcblk0rpmb
252 0 1048576 vnswap0
179 64 62533632 mmcblk1
179 65 62532608 mmcblk1p1
this is from the original firmware
Starchild2k said:
179 0 15388672 mmcblk0
179 1 15360 mmcblk0p1
179 2 58816 mmcblk0p2
179 3 512 mmcblk0p3
179 4 32 mmcblk0p4
179 5 2048 mmcblk0p5
179 6 512 mmcblk0p6
179 7 768 mmcblk0p7
179 8 512 mmcblk0p8
179 9 3072 mmcblk0p9
179 10 16 mmcblk0p10
179 11 10512 mmcblk0p11
179 12 10240 mmcblk0p12
179 13 14336 mmcblk0p13
179 14 3072 mmcblk0p14
179 15 3072 mmcblk0p15
179 16 13312 mmcblk0p16
179 17 15360 mmcblk0p17
179 18 12289 mmcblk0p18
179 19 7159 mmcblk0p19
179 20 3072 mmcblk0p20
179 21 8 mmcblk0p21
179 22 8192 mmcblk0p22
179 23 1024 mmcblk0p23
179 24 9216 mmcblk0p24
179 25 3217408 mmcblk0p25
179 26 307200 mmcblk0p26
179 27 46080 mmcblk0p27
179 28 11621356 mmcblk0p28
179 32 4096 mmcblk0rpmb
252 0 1048576 vnswap0
179 64 62533632 mmcblk1
179 65 62532608 mmcblk1p1
this is from the original firmware
Click to expand...
Click to collapse
I need you to run this command too
ls -al /dev/block/bootdevice/by-name
messi2050 said:
I need you to run this command too
ls -al /dev/block/bootdevice/by-name
Click to expand...
Click to collapse
lrwxrwxrwx 1 root root 20 Jan 1 14:31 aboot -> /dev/block/mmcblk0p5
lrwxrwxrwx 1 root root 20 Jan 1 14:31 apnhlos -> /dev/block/mmcblk0p1
lrwxrwxrwx 1 root root 21 Jan 1 14:31 backup -> /dev/block/mmcblk0p19
lrwxrwxrwx 1 root root 21 Jan 1 14:31 boot -> /dev/block/mmcblk0p16
lrwxrwxrwx 1 root root 21 Jan 1 14:31 cache -> /dev/block/mmcblk0p26
lrwxrwxrwx 1 root root 21 Jan 1 14:31 carrier -> /dev/block/mmcblk0p27
lrwxrwxrwx 1 root root 20 Jan 1 14:31 ddr -> /dev/block/mmcblk0p4
lrwxrwxrwx 1 root root 21 Jan 1 14:31 efs -> /dev/block/mmcblk0p13
lrwxrwxrwx 1 root root 21 Jan 1 14:31 fota -> /dev/block/mmcblk0p18
lrwxrwxrwx 1 root root 21 Jan 1 14:31 fsc -> /dev/block/mmcblk0p20
lrwxrwxrwx 1 root root 20 Jan 1 14:31 fsg -> /dev/block/mmcblk0p9
lrwxrwxrwx 1 root root 20 Jan 1 14:31 modem -> /dev/block/mmcblk0p2
lrwxrwxrwx 1 root root 21 Jan 1 14:31 modemst1 -> /dev/block/mmcblk0p14
lrwxrwxrwx 1 root root 21 Jan 1 14:31 modemst2 -> /dev/block/mmcblk0p15
lrwxrwxrwx 1 root root 21 Jan 1 14:31 pad -> /dev/block/mmcblk0p11
lrwxrwxrwx 1 root root 21 Jan 1 14:31 param -> /dev/block/mmcblk0p12
lrwxrwxrwx 1 root root 21 Jan 1 14:31 persdata -> /dev/block/mmcblk0p24
lrwxrwxrwx 1 root root 21 Jan 1 14:31 persist -> /dev/block/mmcblk0p22
lrwxrwxrwx 1 root root 21 Jan 1 14:31 persistent -> /dev/block/mmcblk0p23
lrwxrwxrwx 1 root root 20 Jan 1 14:31 qhee -> /dev/block/mmcblk0p8
lrwxrwxrwx 1 root root 20 Jan 1 14:31 qsee -> /dev/block/mmcblk0p7
lrwxrwxrwx 1 root root 21 Jan 1 14:31 recovery -> /dev/block/mmcblk0p17
lrwxrwxrwx 1 root root 20 Jan 1 14:31 rpm -> /dev/block/mmcblk0p6
lrwxrwxrwx 1 root root 20 Jan 1 14:31 sbl1 -> /dev/block/mmcblk0p3
lrwxrwxrwx 1 root root 21 Jan 1 14:31 sec -> /dev/block/mmcblk0p10
lrwxrwxrwx 1 root root 21 Jan 1 14:31 ssd -> /dev/block/mmcblk0p21
lrwxrwxrwx 1 root root 21 Jan 1 14:31 system -> /dev/block/mmcblk0p25
lrwxrwxrwx 1 root root 21 Jan 1 14:31 userdata -> /dev/block/mmcblk0p28
When you get the phone to boot into android I'd be more than happy to beta/alpha test, but with this being my daily driver (duh) I kinda wanna keep my buddy awake when I'm at school, but if it gets really rough then I'll pitch in, but yea same error here
"KERNAL IS NOT SEANDROID ENFORCING"
I would donate but I have no job and alas no money.
Good luck though! Can't wait to see CM13 running on the J700P, shoulda gone with Verizon, lol.
LexignisOfficial said:
When you get the phone to boot into android I'd be more than happy to beta/alpha test, but with this being my daily driver (duh) I kinda wanna keep my buddy awake when I'm at school, but if it gets really rough then I'll pitch in, but yea same error here
"KERNAL IS NOT SEANDROID ENFORCING"
I would donate but I have no job and alas no money.
Good luck though! Can't wait to see CM13 running on the J700P, shoulda gone with Verizon, lol.
Click to expand...
Click to collapse
Look at Xiaomi for your next phone. IIRC they have CDMA bands.
minz1 said:
Look at Xiaomi for your next phone. IIRC they have CDMA bands.
Click to expand...
Click to collapse
I want a more popular/mainstream phone I'd love a nexus but I'm thinking I might have a wider selection of roms if I went Galaxy.
Thanks for the suggestion though, I'll look into it, it's gonna be a while before I cut myself off from Virgin Mobile (can't stand the signal though).
LexignisOfficial said:
I want a more popular/mainstream phone I'd love a nexus but I'm thinking I might have a wider selection of roms if I went Galaxy.
Thanks for the suggestion though, I'll look into it, it's gonna be a while before I cut myself off from Virgin Mobile (can't stand the signal though).
Click to expand...
Click to collapse
nononononononononono
if you like roms, don't get a samsung phone. xiaomi has more rom selection than samsung. pls pls pls don't get a galaxy in general if you like your experience on xda
minz1 said:
nononononononononono
if you like roms, don't get a samsung phone. xiaomi has more rom selection than samsung. pls pls pls don't get a galaxy in general if you like your experience on xda
Click to expand...
Click to collapse
Well its gonna be a while and ive done 0 research so calm yourself
Sent from my SM-J700P using Tapatalk
---------- Post added at 03:49 AM ---------- Previous post was at 03:22 AM ----------
minz1 said:
nononononononononono
if you like roms, don't get a samsung phone. xiaomi has more rom selection than samsung. pls pls pls don't get a galaxy in general if you like your experience on xda
Click to expand...
Click to collapse
Also you still need that efs partition? I replied to a week old thread and dunno if its still relevent
Sent from my SM-J700P using Tapatalk
LexignisOfficial said:
Well its gonna be a while and ive done 0 research so calm yourself
Sent from my SM-J700P using Tapatalk
---------- Post added at 03:49 AM ---------- Previous post was at 03:22 AM ----------
Also you still need that efs partition? I replied to a week old thread and dunno if its still relevent
Sent from my SM-J700P using Tapatalk
Click to expand...
Click to collapse
Oh no, I'm just going to replace this phone. If you want to send it I'll try using it to fix my phone, but I'm set on a new one.
minz1 said:
Oh no, I'm just going to replace this phone. If you want to send it I'll try using it to fix my phone, but I'm set on a new one.
Click to expand...
Click to collapse
Why not? If you ever decide to pickup again you'll be glad it's alive and it doesn't take to long to backup w/ TWRP
How about keeping this thread clean for tester posts only... Btw Ill be buying an iphone soon afterwards if this project is still going ill donate this phone to the cause and use it for testing. (I hop back and forth between boost mobile phones)
Sent from my SM-J700P using Tapatalk
Synz86 said:
How about keeping this thread clean for tester posts only... Btw Ill be buying an iphone soon afterwards if this project is still going ill donate this phone to the cause and use it for testing. (I hop back and forth between boost mobile phones)
Sent from my SM-J700P using Tapatalk
Click to expand...
Click to collapse
+1 for this , guys please take your conversations to the pm , I'm busy with my college those days but i will try to create a bootable build in the next days and will share it here to test