[jcase]

Samsung made these devices a bit more secure than normal (this is a good thing), by making adbd ignore ro.kernel.qemu/ro.secure/ro.debuggable.

However some people prefer an unsecured boot image that runs adbd as root, so here you go. These are stock with ro.secure=0 set, and with a standard AOSP adbd, please match them with your firmware (do not flash to other firmwares)

IML74K_P3113UEALCB
http://goo.im/devs/jcase/IML74K_P3113UEALCB_boot.zip
f16b0fdcba6988b9cfbdc1eb084b4a6b IML74K_P3113UEALCB_boot.zip

IML74K_P3113UEALD3
http://goo.im/devs/jcase/IML74K_P3113UEALD3_boot.zip
ba434a9112b293f93111d6266ca22c6d IML74K_P3113UEALD3_boot.zip

Flash from Clockwork recovery.

Again, only flash these to corresponding firmwares/devices.

 

[fattire]

I don't have one of these things, but I'm curious where the source is? I don't see it at https://opensource.samsung.com

I think the part number is GT-P3113TSYXAR for the 8gb. Has anyone made a request who has the device?

 

[termleech]

I don't have one of these things, but I'm curious where the source is? I don't see it at https://opensource.samsung.com

I think the part number is GT-P3113TSYXAR for the 8gb. Has anyone made a request who has the device?

As far as I know they have not yet released source. Knowing Samsung it will be a while. I highly recommend everyone go request them to release the source.

Sent from my Galaxy Nexus using Tapatalk 2

 

[jcase]

As far as I know they have not yet released source. Knowing Samsung it will be a while. I highly recommend everyone go request them to release the source.

Sent from my Galaxy Nexus using Tapatalk 2

I'm not sure how you figure a while, everytime I have requested source they have delivered within the week.

 

[GRZLA]

I'm not sure how you figure a while, everytime I have requested source they have delivered within the week.

I requested it three days ago.

 

[fattire]

I don't have one of these devices, but can someone post the output of these commands:

# uname -a
# df
# cat /proc/partitions
# cat /proc/mounts
# ls -l /dev/block/platform/mmci-omap-hs.1/by-name/ (or something similar)

Thx!

 

[jcase]

I requested it three days ago.

Long as you requested it in a proper manor, then just sit back and wait.

 

[jcase]

From IML74K_P3113UEALCB

Linux localhost 3.0.8-292098-user #1 SMP PREEMPT Sat Mar 24 16:56:38 KST 2012 armv7l GNU/Linux

Filesystem Size Used Free Blksize
/dev 343M 76K 343M 4096
/mnt/asec 343M 0K 343M 4096
/mnt/obb 343M 0K 343M 4096
/system 1G 988M 389M 4096
/data 4G 553M 4G 4096
/cache 688M 11M 677M 4096
/efs 19M 4M 15M 4096
/mnt/sdcard 4G 553M 4G 4096
/mnt/extSdCard 29G 16G 13G 16384

major minor #blocks name

179 0 7634944 mmcblk0
179 1 20480 mmcblk0p1
179 2 2048 mmcblk0p2
179 3 2048 mmcblk0p3
179 4 8192 mmcblk0p4
179 5 8192 mmcblk0p5
179 6 8192 mmcblk0p6
179 7 716800 mmcblk0p7
259 0 20480 mmcblk0p8
259 1 1433600 mmcblk0p9
259 2 4886511 mmcblk0p10
259 3 524288 mmcblk0p11
179 16 2048 mmcblk0boot1
179 8 2048 mmcblk0boot0
179 24 31166976 mmcblk1
179 25 31165952 mmcblk1p1

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/platform/omap/omap_hsmmc.1/by-name/FACTORYFS /system ext4 ro,relatime,barrier=1,data=ordered 0 0
/dev/block/platform/omap/omap_hsmmc.1/by-name/DATAFS /data ext4 rw,nosuid,nodev,noatime,barrier=1,data=ordered,noauto_da_alloc,discard 0 0
/dev/block/platform/omap/omap_hsmmc.1/by-name/CACHE /cache ext4 rw,nosuid,nodev,noatime,errors=panic,barrier=1,nomblk_io_submit,data=ordered 0 0
/dev/block/platform/omap/omap_hsmmc.1/by-name/EFS /efs ext4 rw,relatime,barrier=1,data=ordered 0 0
/sys/kernel/debug /sys/kernel/debug debugfs rw,relatime 0 0
/dev/fuse /mnt/sdcard fuse rw,nosuid,nodev,relatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
/dev/block/vold/179:25 /mnt/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

ls -l /dev/block/platform/omap/omap_hsmmc.1/by-name
lrwxrwxrwx root root 2012-04-30 20:52 CACHE -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 2012-04-30 20:52 DATAFS -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 2012-04-30 20:52 EFS -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 2012-04-30 20:52 FACTORYFS -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 2012-04-30 20:52 HIDDEN -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 2012-04-30 20:52 KERNEL -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 2012-04-30 20:52 MODEM -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 2012-04-30 20:52 PARAM -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 2012-04-30 20:52 RECOVERY -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 2012-04-30 20:52 SBL1 -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 2012-04-30 20:52 SBL2 -> /dev/block/mmcblk0p3

I don't have one of these devices, but can someone post the output of these commands:

# uname -a
# df
# cat /proc/partitions
# cat /proc/mounts
# ls -l /dev/block/platform/mmci-omap-hs.1/by-name/ (or something similar)

Thx!

 

[machx0r]

pwd
/dev/block/platform/omap/omap_hsmmc.1/by-name
[email protected]:/dev/block/platform/omap/omap_hsmmc.1/by-name # ls -l
ls -l
lrwxrwxrwx root root 2012-04-30 20:41 CACHE -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 2012-04-30 20:41 DATAFS -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 2012-04-30 20:41 EFS -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 2012-04-30 20:41 FACTORYFS -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 2012-04-30 20:41 HIDDEN -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 2012-04-30 20:41 KERNEL -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 2012-04-30 20:41 MODEM -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 2012-04-30 20:41 PARAM -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 2012-04-30 20:41 RECOVERY -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 2012-04-30 20:41 SBL1 -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 2012-04-30 20:41 SBL2 -> /dev/block/mmcblk0p3
[email protected]:/dev/block/platform/omap/omap_hsmmc.1/by-name #

 

[machx0r]

It's been a while but is there a shell login script somewhere on these devices? I'm getting sick of all the java apps (ie: pm, am, etc...) segfaulting in a su shell unless I add LD_LIBRARY_PATH=/vendor/lib:/system/lib ...

 

[Tucstwo]

I'm kind of a noob when it comes to this kind of stuff. My last 3 android devices were all Motorolla and they're all locked down. What does having this boot image afford me?

/noobness

 

[GRZLA]

I'm kind of a noob when it comes to this kind of stuff. My last 3 android devices were all Motorolla and they're all locked down. What does having this boot image afford me?

/noobness

It helps restore your device to stoc, just in case you brick or anything like that.

 

[Tucstwo]

It helps restore your device to stoc, just in case you brick or anything like that.

Holy crap, that's amazing. I don't know if anyone has any experience with any Moto devices with locked bootloaders, but you have to jump through a million hoops to do what this essentials does. What is the difference between this unsecured file and the other thread with the stock images? So this will flash back the stock Recovery and remove root, etc? This also wipes data I assume?

 

[bark777]

From post # one by OP.

"Samsung made these devices a bit more secure than normal (this is a good thing), by making adbd ignore ro.kernel.qemu/ro.secure/ro.debuggable.

However some people prefer an unsecured boot image that runs adbd as root, so here you go. These are stock with ro.secure=0 set, and with a standard AOSP adbd, please match them with your firmware (do not flash to other firmwares)"

These files allow you to run adbd as root.

Use this thread for restore to stock with CWM.
http://rootzwiki.com...es-and-updates/

To enter recovery or download from off, (do not connect cable until download mode is entered) hold the Power and up volume or down volume Keys until the first Samsung goes away then let go of them and wait. After you have root install "Quick boot" to make it easier to enter recovery.

 

[dsb9938]

Do we know the differences between these? Is one just newer? Can you upgrade, or is there some imcompatability?

D

.

 

[Tucstwo]

From post # one by OP.

"Samsung made these devices a bit more secure than normal (this is a good thing), by making adbd ignore ro.kernel.qemu/ro.secure/ro.debuggable.

However some people prefer an unsecured boot image that runs adbd as root, so here you go. These are stock with ro.secure=0 set, and with a standard AOSP adbd, please match them with your firmware (do not flash to other firmwares)"

These files allow you to run adbd as root.

Use this thread for restore to stock with CWM.
http://rootzwiki.com...es-and-updates/

To enter recovery or download from off, (do not connect cable until download mode is entered) hold the Power and up volume or down volume Keys until the first Samsung goes away then let go of them and wait. After you have root install "Quick boot" to make it easier to enter recovery.

I was able to run adb as root without flashing this??

 

[machx0r]

I was able to run adb as root without flashing this??

You will be able to run 'adb shell' and then 'su' without these changes. The settings mentioned and the adbd allow you to run 'adb root' and login shell (and do other things) without needing to 'su'.

 

[jcase]

You will be able to run 'adb shell' and then 'su' without these changes. The settings mentioned and the adbd allow you to run 'adb root' and login shell (and do other things) without needing to 'su'.

Actually, adbd runs as root "out of the box" with these.

These have standard aosp adbd instead of the modified samsung one. That, and setting ro.secure=0 are the only differences.

Personally, I don't use them.

 

[APPLE]

Hi, I'm having a problem,I rooted using odin and it went well had root and cwm installed then I got an update to ueald3 now I have no root or cwm. I have heimdall installed but have no clue how to use it. Would someone be willing to do team viewer with me and get root and cwm back for me? Or aleast walk me through the process? Thanks in advance.

N/M.... figured it out.

 

[ruff97]

hello all
need some help [background=rgb(245, 245, 245)]flash to firmwares -> [/background]IML74K_P3113UEALD3. how do i do it. i pickup heimdall-suite-1.3.2-win32 but i get a error 'The file selected was not a vaild PIT file" the file i have is a .img i do have the file extract but what file do i use to do the flash