Ubuntu partition dump from Stock Atrix - Atrix 4G Android Development

Ubuntu partition dump from Stock Atrix - Atrix 4G Android Development

The link below is a dump of the /dev/block/mmcblk0p13 partition.
It is the entire ubuntu "distribution". However, it is not an OS per say. It is just an environment compiled and setup to run on the "android linux". Everything just runs from a second X session started on top of the native Android Arm linux redirected to the HDMI display port.
The partition has about 800MB in size and is mounted under /osh once the system boots.
Something worth to note, is that the webtop X session does not consume any RAM or system resource at all till when the phone enters RM_SM_DOCKED mode. While the phone is on RM_SM_MOBILE mode, that X session is complete shutdown.
http://www.usk.bz/android/ubuntu.img.bz2
If you use a linux or MacOS, just uncompress the file with bzip2 -d , then mount like this:
mount -t ext3 -o loop,ro ubuntu.img /mnt/loop
Of course, make sure the directory /mnt/loop exists.
Also, some directories, like /etc will not be available or will look like bugged/corrupted, it's because they are actually just a "link" to the /etc from the root partition. I can provide a dump for that partition as well, if that will help with any development. Let me know.
Have fun and post us if you find anything special.

A bit further: There's a chroot involved! And the adas account password is randomly set!
... Buuuuuuuuut, Motorola was smart and got rid of telnetd, etc in this production script...
See /usr/local/sbin/webtop-product.sh.
It's the script that makes the "production" webtop - and removes the fun stuff via dpkg in the process.
But here's a hint - if you can run an app within Webtop, get it to run /usr/bin/.lxterminal - they HID the terminal app.
EDIT: Hm. /usr/local/share/motorola/fireboxmake/ has some interesting readmes... on what .sh does what in /usr/local/sbin.
EDIT2: Check out what's in the OSH_tools.tgz. Motorola left a bootloader BIN in there along with some interesting flashing scripts for both Webtop and the Android side... and some interesting config files in nvflash...
Also, can I get the root filesystem for /etc/?

I have not downloaded the archive yet but did a search for RM_SM_DOCKED on google and came up with a hit elsewhere.
I can't post the link to this directly due to it being one of my first posts. It's only one of 3/4 hits on google.
I am guessing it is in the archive you posted.
Code:
#
#
on property:dev.bootcomplete=1
#
setprop ro.webtop.boot 1
#
start loadpreinstalls
#
#
on property:ro.webtop.boot=1
#
exec /system/bin/logwrapper /ubuntu.sh
#
#
on property:sys.SystemMode=RM_SM_DOCKED
#
exec /osh/etc/init.d/startX.sh
#

uskr said:
The link below is a dump of the /dev/block/mmcblk0p13 partition.
It is the entire ubuntu "distribution". However, it is not an OS per say. It is just an environment compiled and setup to run on the "android linux". Everything just runs from a second X session started on top of the native Android Arm linux redirected to the HDMI display port.
The partition has about 800MB in size and is mounted under /osh once the system boots.
Something worth to note, is that the webtop X session does not consume any RAM or system resource at all till when the phone enters RM_SM_DOCKED mode. While the phone is on RM_SM_MOBILE mode, that X session is complete shutdown.
http://www.usk.bz/android/ubuntu.img.bz2
If you use a linux or MacOS, just uncompress the file with bzip2 -d , then mount like this:
mount -t ext3 -o loop,ro ubuntu.img /mnt/loop
Of course, make sure the directory /mnt/loop exists.
Also, some directories, like /etc will not be available or will look like bugged/corrupted, it's because they are actually just a "link" to the /etc from the root partition. I can provide a dump for that partition as well, if that will help with any development. Let me know.
Have fun and post us if you find anything special.
Click to expand...
Click to collapse
uskr,
Excellent work & post, have a Thanks.
It's a shame that the webtop will probably flop (and I sure as heck won't buy one for the price they're asking). Here's to hoping a dockless hack comes up.

uskr,
Great post, Thanks

labsONE said:
Also, can I get the root filesystem for /etc/?
Click to expand...
Click to collapse
http://www.usk.bz/android/etc.tar.bz2
You will notice some files are just links to /system/etc. You can find the /system dump on another thread on this forum. If you cant, let me know and I will get a link here.

Can someone take a good look at the contents of:
/usr/local/share/motorola/fireboxmake/OSH_tools.tgz
There's lots of interesting stuff in there & I am completely unfamiliar with tegra and Motorola cruft.

uskr said:
The link below is a dump of the /dev/block/mmcblk0p13 partition.
It is the entire ubuntu "distribution". However, it is not an OS per say. It is just an environment compiled and setup to run on the "android linux". Everything just runs from a second X session started on top of the native Android Arm linux redirected to the HDMI display port.
The partition has about 800MB in size and is mounted under /osh once the system boots.
Something worth to note, is that the webtop X session does not consume any RAM or system resource at all till when the phone enters RM_SM_DOCKED mode. While the phone is on RM_SM_MOBILE mode, that X session is complete shutdown.
If you use a linux or MacOS, just uncompress the file with bzip2 -d , then mount like this:
mount -t ext3 -o loop,ro ubuntu.img /mnt/loop
Of course, make sure the directory /mnt/loop exists.
Also, some directories, like /etc will not be available or will look like bugged/corrupted, it's because they are actually just a "link" to the /etc from the root partition. I can provide a dump for that partition as well, if that will help with any development. Let me know.
Have fun and post us if you find anything special.
Click to expand...
Click to collapse
uskr, appreciate if you could also get us the root partition dump

Actually, sorry for not posting this before. But right after I posted the first dump I noticed that pretty much everything on the root partition is just a link to /osh, like you can see here:
Code:
lrwxrwxrwx root root 2011-02-22 23:54 lib -> /osh/lib
lrwxrwxrwx root root 2011-02-22 23:54 etc -> /osh/etc
lrwxrwxrwx root root 2011-02-22 23:54 thumb2 -> /osh/thumb2
lrwxrwxrwx root root 2011-02-22 23:54 srv -> /osh/srv
lrwxrwxrwx root root 2011-02-22 23:54 usr -> /osh/usr
lrwxrwxrwx root root 2011-02-22 23:54 media -> /osh/media
lrwxrwxrwx root root 2011-02-22 23:54 upath.sh -> /osh/upath.sh
lrwxrwxrwx root root 2011-02-22 23:54 boot -> /osh/boot
lrwxrwxrwx root root 2011-02-22 23:54 sbin -> /osh/sbin
lrwxrwxrwx root root 2011-02-22 23:54 var -> /osh/var
lrwxrwxrwx root root 2011-02-22 23:54 root -> /osh/root
lrwxrwxrwx root root 2011-02-22 23:54 apath.sh -> /osh/apath.sh
lrwxrwxrwx root root 2011-02-22 23:54 bin -> /osh/bin
lrwxrwxrwx root root 2011-02-22 23:54 opt -> /osh/opt
lrwxrwxrwx root root 2011-02-22 23:54 selinux -> /osh/selinux
lrwxrwxrwx root root 2011-02-22 23:54 ubuntu.sh -> /osh/ubuntu.sh
lrwxrwxrwx root root 2011-02-22 23:54 lost+found -> /osh/lost+found
lrwxrwxrwx root root 2011-02-22 23:54 home -> /data/home
dr-x------ root root 2011-02-22 23:54 config
drwxrwx--- system misc 2011-02-22 23:54 misc
drwxrwx--- system cache 2011-02-23 00:58 cache
drwxr-xr-x root root 2011-01-30 05:54 pds
lrwxrwxrwx root root 2011-02-22 23:54 sdcard-ext -> /mnt/sdcard-ext
lrwxrwxrwx root root 2011-02-22 23:54 sdcard -> /mnt/sdcard
drwxr-xr-x root root 2011-02-22 23:54 acct
lrwxrwxrwx root root 2011-02-22 23:54 tmp -> /data/tmp
drwxr-xr-x root root 2010-12-22 17:39 preinstall
drwxr-xr-x root root 2011-01-20 21:49 osh
drwxrwxr-x root system 2011-02-22 23:54 mnt
lrwxrwxrwx root root 2011-02-22 23:54 d -> /sys/kernel/debug
drwxr-xr-x root root 2011-02-05 05:07 system
drwxr-xr-x root root 1969-12-31 19:00 sys
dr-xr-xr-x root root 1969-12-31 19:00 proc
-rwxr-x--- root root 32498 1969-12-31 19:00 init.rc
-rwxr-x--- root root 1954 1969-12-31 19:00 init.goldfish.rc
-rwxr-x--- root root 118156 1969-12-31 19:00 init
-rw-r--r-- root root 153 1969-12-31 19:00 default.prop
drwxrwx--x system system 2011-02-22 23:54 data
drwxr-xr-x root root 2011-02-22 23:54 dev
But for some reason when I dump the /osh partition, a couple of those folders come corrupted. Let me know if any of the folders you are interested are damaged on the dump and I will post a tar.bz2 like I did with /etc

Related

[Q] Droid Bionic's Android and /osh

In debugging a problem with a cross-compiled binary crashing on someone elses Droid Bionic, I noticed that a bunch of dirs in / are sym-linked into /osh:
Code:
/# [B]ls -l /[/B]
...
lrwxrwxrwx root root 2011-11-06 09:38 etc -> /osh/etc
lrwxrwxrwx root root 2011-11-06 09:38 lib -> /osh/lib
lrwxrwxrwx root root 2011-11-06 09:38 sbin -> /osh/sbin
lrwxrwxrwx root root 2011-11-06 09:38 usr -> /osh/usr
...
Is it 'normal' for stock Droid Bionic Androids to sym-link this stuff in the root dir to /osh, or is it the result of some customisation (Havent seen this on other devices, and dont have hands-on a Bionic to check further ... ) ?
- jc

Problem with efs folder content

Hi,
I bought a brand new samsung galaxy s plus GT-I9001 in Poland (locked to Orange network) and I 'm trying to unlock the phone, but I can't because my phone does not contain the nv_data.bin file in the efs folder.
I have rooted the phone using the tutorial posted in
http://forum.xda-developers.com/wiki/Samsung_Galaxy_S_Plus/GT-I9001#Rooting
I got root access and found that in efs folder I got these files
Code:
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
$ su
su
# pwd
pwd
/
# ls -l -a
ls -l -a
drwxrwx--x system system 2012-10-09 15:39 efs
dr-x------ root root 2012-10-10 13:27 config
drwxrwx--- system cache 2012-10-10 13:29 cache
drwxrwx--x system system 1980-01-06 01:00 persist
lrwxrwxrwx root root 2012-10-10 13:27 sdcard -> /mnt/sdcard
drwxr-xr-x root root 2012-10-10 13:27 acct
drwxrwxr-x root system 2012-10-10 13:27 mnt
lrwxrwxrwx root root 2012-10-10 13:27 vendor -> /system/vendor
lrwxrwxrwx root root 2012-10-10 13:27 d -> /sys/kernel/debug
lrwxrwxrwx root root 2012-10-10 13:27 etc -> /system/etc
-rw-r--r-- root root 5610 1970-01-01 01:00 ueventd.rc
-rw-r--r-- root root 0 1970-01-01 01:00 ueventd.goldfish.rc
drwxr-xr-x root root 2012-10-10 12:15 system
drwxr-xr-x root root 2012-10-10 13:27 sys
drwxr-x--- root root 1970-01-01 01:00 sbin
-rw-r--r-- root root 339852 1970-01-01 01:00 recovery
dr-xr-xr-x root root 1970-01-01 01:00 proc
-rw-r--r-- root root 2011 1970-01-01 01:00 lpm.rc
drwxr-xr-x root root 1970-01-01 01:00 lib
-rwxr-x--- root root 24620 1970-01-01 01:00 initlogo.rle
-rwxr-x--- root root 30518 1970-01-01 01:00 init.rc
-rwxr-x--- root root 6900 1970-01-01 01:00 init.qcom.sh
-rwxr-x--- root root 8590 1970-01-01 01:00 init.qcom.rc
-rwxr-x--- root root 1677 1970-01-01 01:00 init.goldfish.rc
-rwxr-x--- root root 106780 1970-01-01 01:00 init
-rw-r--r-- root root 118 1970-01-01 01:00 default.prop
drwxrwx--x system system 2012-10-10 13:27 data
-rw-r--r-- root root 38528 1970-01-01 01:00 charging.rle
-rw-r--r-- root root 22268 1970-01-01 01:00 ARIESVE.rle
drwx------ root root 2011-12-19 08:31 root
drwxr-xr-x root root 2012-10-10 13:35 dev
# cd efs
cd efs
# ls -l -a
ls -l -a
-rw-r--r-- system system 9 2012-10-09 15:39 cryptprop_applied_result
-rw-r--r-- root root 5 2012-10-10 10:51 cryptprop_onetimeboot
-rw-r--r-- system system 1 2012-10-09 15:39 cryptprop_essiv
drwx------ root root 1980-01-06 01:01 lost+found
drwxrwxr-x root root 1980-01-06 01:09 .files
-rw-r--r-- root root 3 2012-10-10 10:51 cryptprop_securewipedata
# cd .files
cd .files
# ls -l -a
ls -l -a
drwxrwxr-x media system 1980-01-06 01:01 .ssh01
-rw-rw-rw- radio radio 2 1980-01-06 01:09 keystr
drwxrwxr-x media system 1980-01-06 01:01 .jck12
drwxrwxr-x media system 1980-01-06 01:01 .dj550
as you can see the efs folder contain cryptprop files which are very small.
The phone works normally, it has its IMEI and connects to GSM network and WiFi network as well. (*#06# returns value 352377055840629)
I'm trying to unlock the phone myself but without nv_data.bin I'm getting nowhere...
Could someone please help me?
PS:
I have changed the stock rom (orange) to XEO rom (I9001XXKPU 2.3.6 and I9001XXKI2 2.3.4) but efs folder is the same each time.

I have checked the init.rc file in the root... ht file looks like this:
Line 56:
mkdir /efs 0771 system system
Line 131 - 135:
mount ext4 /dev/block/mmcblk0p27 /efs nosuid nodev barrier=0
insmod /lib/modules/sec_param.ko
Line 160 - 165:
#efs
chown system system /efs
chmod 0771 /efs
mkdir /efs/.files 0775
# Added for testing DIVX DRM
mkdir /efs/.files/.ssh01 0775
mkdir /efs/.files/.jck12 0775
mkdir /efs/.files/.dj550 0775
chown media system /efs/.files/.ssh01
chown media system /efs/.files/.jck12
chown media system /efs/.files/.dj550
chmod 0775 /efs/.files/.ssh01
chmod 0775 /efs/.files/.jck12
chmod 0775 /efs/.files/.dj550
This init.rc does not create the folders WiFi or Bluetooth like in other device (I checked in a galaxy SII)
The init.rc file is attached.

fcornejo said:
I 'm trying to unlock the phone,
Click to expand...
Click to collapse
It might be easier to use an app or tool from My Android Collections to unlock phone

xsenman said:
It might be easier to use an app or tool from My Android Collections to unlock phone
Click to expand...
Click to collapse
Well thanx, but all the aps and methods require the nv_data.bin file...

fcornejo said:
Well thanx, but all the aps and methods require the nv_data.bin file...
Click to expand...
Click to collapse
have a look at /persist folder.

xsenman said:
have a look at /persist folder.
Click to expand...
Click to collapse
There are files:
Code:
#
# cd persist
cd persist
# ls -l -a
ls -l -a
-rw-r--r-- root root 3468 2011-08-29 00:40 WCN1314_qcom_wlan_nv.bi
-rw-r--r-- root root 3 2011-08-29 00:40 efs_info.bin
drwxr-xr-x root root 2011-09-08 10:14 qcom
-rw-r--r-- root root 1656 2011-08-29 00:40 qcom_wlan_nv.bin
-rw-rw-rw- root root 2 2012-10-10 13:27 sd_det.bin
-rw-rw-rw- root root 1 2012-10-10 12:08 usb_sel.bin
drwxrwxr-x root root 1980-01-06 01:00 .files
-rw-rw-rw- root root 1 1980-01-06 01:00 movinand_checksum_pass
-rw-rw-rw- root root 1 1980-01-06 01:00 movinand_checksum_done

[Q] Troubles with dumping Recovery Image

Hi everybody
I'm following his tutorial in order to port CWM for the samsung galaxy s3 mini I-8200 that has not been ported yet.
I've done:
Code:
$ adb shell
[email protected]:/ $ ls -al /dev/block/platform/sdhci-pxav3.2/by-name
ls -al /dev/block/platform/sdhci-pxav3.2/by-name
lrwxrwxrwx root root 2014-09-24 17:15 CACHE -> /dev/block/mmcblk0p14
lrwxrwxrwx root root 2014-09-24 17:15 EFS -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 2014-09-24 17:15 HIDDEN -> /dev/block/mmcblk0p13
lrwxrwxrwx root root 2014-09-24 17:15 KERNEL -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 2014-09-24 17:15 LOKE -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 2014-09-24 17:15 MEP2 -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 2014-09-24 17:15 MODEM -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 2014-09-24 17:15 MRD -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 2014-09-24 17:15 NVM -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 2014-09-24 17:15 PARAM -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 2014-09-24 17:15 RECOVERY -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 2014-09-24 17:15 Reserved -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 2014-09-24 17:15 SYSTEM -> /dev/block/mmcblk0p15
lrwxrwxrwx root root 2014-09-24 17:15 USER -> /dev/block/mmcblk0p16
And then I tried:
Code:
$ adb shell adb shell
[email protected]:/ $ su
su
[email protected]:/ # dd if=/dev/block/mmcblk0p9 of=/sdcard/recovery.img
dd if=/dev/block/mmcblk0p9 of=/sdcard/recovery.img
32768+0 records in
32768+0 records out
16777216 bytes transferred in 4.414 secs (3800909 bytes/sec)
[email protected]:/ # ^C
$ adb pull /sdcard/recovery.img
And then if I open it with Linux Readers it says
Can't Open C:/Users/Me/Recovery.img. Please check the disk and try again.
Click to expand...
Click to collapse
Thank in advance for your help guys

[FIX] Restoring G900A after attempting to flash modified recovery [10 Dec 2014]

I know --- the bootloader is locked. But I still had to prove it to myself. And the info provided here may be useful to developers as well as to end-users.
Here is my story:
Running stock KK 4.4.2 (NCE) on my G900A, I successfully rooted using GeoHot’s towelroot https://towelroot.com/.
Then I froze the AT&T software updater app via Titanium Backup Pro --- since there is presently no way to re-root after updating.
Then I modified the stock recovery image to enable “adbd” (Android Debug Bridge daemon). Here’s a brief description of the process:
Running ADB with root and busybox installed, I created directory: /sdcard/Boot and did this:
Code:
dd if=/dev/block/mmcblk0p16 of=/sdcard/Boot/recovery.img
Then on Windows, I unpacked recovery.img to kernel and /ramdisk and modified the /ramdisk/init.rc script as follows:
Code:
service recovery /sbin/recovery
service adbd /sbin/adbd recovery
[COLOR="Blue"]
# se[email protected] (09 Dec 2014)
# disabled
# [email protected] (09 Dec 2014)
[/COLOR]
socket adbd stream 660 system system
##++ Security R&D Group
service qrngd /system/bin/qrngd -f
class load_ode_env
user root
group root
oneshot
Then I repacked kernel and modified /ramdisk to recovery-repack.img, dropped it into /sdcard/Boot and flashed it to the recovery partition from 4.4.2 via ADB:
Code:
dd if=/sdcard/Boot/recovery-repack.img of=/dev/block/mmcblk0p16
When I rebooted, my phone returned an error message and rebooted again, this time to download mode. Oh well, I was really hoping to sneak this one past AT&T.
Somewhat nervous, I scoured the web for two days in search of a decent stock NCE build to recover my G900A. But all of the links were slow, flaky, costly and/or plagued with ads --- except for this one…
NCE Stock TAR with md5: http://www.rwilco12.com/forum/showthread.php?tid=883
Odin versions (esp. v1.85 --- considered the most stable):
http://www.rwilco12.com/forum/showthread.php?tid=101
So I downloaded the 1.5GB zip, decompressed to: “G900AUCU1ANCE_G900AATT1ANCE_G900AUCU1ANCE_HOME.tar.md5”
and ran Odin v1.85 with:
“\{Path-to}\G900AUCU1ANCE_G900AATT1ANCE_G900AUCU1ANCE_HOME.tar.md5”
in the PDA slot with Auto Reboot and F. Reset Time checked and no others checked except for PDA. Execution was flawless (ref. image below) and my G900A gracefully rebooted to stock KK 4.4.2--- with all of my installed apps, data and settings intact. And I quickly recovered root by re-launching the towelroot APK.
Of course I did lose busybox since it installs under /system/xbin. No problem, I just went to the BB app I had installed earlier and reinstalled BB from there.
Note: When I stripped off the .md5 suffix and opened the resulting .tar file with 7zip, an error message was returned but the file listing was still shown:
Note the absence of a data image --- a good thing if you have installed apps etc.
Something else I found helpful is the G900A partition map. Navigating to /dev/block/platform/msm_sdcc.1/by-name …
Code:
cd /dev/block/platform/msm_sdcc.1/by-name
[email protected]:/dev/block/platform/msm_sdcc.1/by-name # ls -ld *
ls -ld *
lrwxrwxrwx root root 2014-01-02 11:49 aboot -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 2014-01-02 11:49 apnhlos -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 2014-01-02 11:49 backup -> /dev/block/mmcblk0p18
lrwxrwxrwx root root 2014-01-02 11:49 boot -> /dev/block/mmcblk0p15
lrwxrwxrwx root root 2014-01-02 11:49 cache -> /dev/block/mmcblk0p24
lrwxrwxrwx root root 2014-01-02 11:49 dbi -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 2014-01-02 11:49 ddr -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 2014-01-02 11:49 efs -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 2014-01-02 11:49 fota -> /dev/block/mmcblk0p17
lrwxrwxrwx root root 2014-01-02 11:49 fsc -> /dev/block/mmcblk0p19
lrwxrwxrwx root root 2014-01-02 11:49 fsg -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 2014-01-02 11:49 modem -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 2014-01-02 11:49 modemst1 -> /dev/block/mmcblk0p13
lrwxrwxrwx root root 2014-01-02 11:49 modemst2 -> /dev/block/mmcblk0p14
lrwxrwxrwx root root 2014-01-02 11:49 pad -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 2014-01-02 11:49 param -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 2014-01-02 11:49 persdata -> /dev/block/mmcblk0p22
lrwxrwxrwx root root 2014-01-02 11:49 persist -> /dev/block/mmcblk0p21
lrwxrwxrwx root root 2014-01-02 11:49 recovery -> /dev/block/mmcblk0p16
lrwxrwxrwx root root 2014-01-02 11:49 rpm -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 2014-01-02 11:49 sbl1 -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 2014-01-02 11:49 ssd -> /dev/block/mmcblk0p20
lrwxrwxrwx root root 2014-01-02 11:49 system -> /dev/block/mmcblk0p23
lrwxrwxrwx root root 2014-01-02 11:49 tz -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 2014-01-02 11:49 userdata -> /dev/block/mmcblk0p25
[email protected]:/dev/block/platform/msm_sdcc.1/by-name #
Note especially the boot, recovery, system, data and cache partitions…
Code:
lrwxrwxrwx root root 2014-01-02 11:49 aboot -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 2014-01-02 11:49 boot -> /dev/block/mmcblk0p15
lrwxrwxrwx root root 2014-01-02 11:49 cache -> /dev/block/mmcblk0p24
lrwxrwxrwx root root 2014-01-02 11:49 persdata -> /dev/block/mmcblk0p22
lrwxrwxrwx root root 2014-01-02 11:49 recovery -> /dev/block/mmcblk0p16
lrwxrwxrwx root root 2014-01-02 11:49 system -> /dev/block/mmcblk0p23
lrwxrwxrwx root root 2014-01-02 11:49 userdata -> /dev/block/mmcblk0p25
Many thanks to Rwilco12 for SGS5 support: http://www.rwilco12.com/
Also thanks to Krang for consolidating Rwilco12’s SGS5 links: http://www.rwilco12.com/forum/member.php?action=profile&uid=450

sendust7 said:
I know --- the bootloader is locked. But I still had to prove it to myself. And the info provided here may be useful to developers as well as to end-users.
Here is my story:
Running stock KK 4.4.2 (NCE) on my G900A, I successfully rooted using GeoHot’s towelroot https://towelroot.com/.
Then I froze the AT&T software updater app via Titanium Backup Pro --- since there is presently no way to re-root after updating.
Then I modified the stock recovery image to enable “adbd” (Android Debug Bridge daemon). Here’s a brief description of the process:
Running ADB with root and busybox installed, I created directory: /sdcard/Boot and did this:
Code:
dd if=/dev/block/mmcblk0p16 of=/sdcard/Boot/recovery.img
Then on Windows, I unpacked recovery.img to kernel and /ramdisk and modified the /ramdisk/init.rc script as follows:
Code:
service recovery /sbin/recovery
service adbd /sbin/adbd recovery
[COLOR="Blue"]
# [email protected] (09 Dec 2014)
# disabled
# [email protected] (09 Dec 2014)
[/COLOR]
socket adbd stream 660 system system
##++ Security R&D Group
service qrngd /system/bin/qrngd -f
class load_ode_env
user root
group root
oneshot
Then I repacked kernel and modified /ramdisk to recovery-repack.img, dropped it into /sdcard/Boot and flashed it to the recovery partition from 4.4.2 via ADB:
Code:
dd if=/sdcard/Boot/recovery-repack.img of=/dev/block/mmcblk0p16
When I rebooted, my phone returned an error message and rebooted again, this time to download mode. Oh well, I was really hoping to sneak this one past AT&T.
Somewhat nervous, I scoured the web for two days in search of a decent stock NCE build to recover my G900A. But all of the links were slow, flaky, costly and/or plagued with ads --- except for this one…
NCE Stock TAR with md5: http://www.rwilco12.com/forum/showthread.php?tid=883
Odin versions (esp. v1.85 --- considered the most stable):
http://www.rwilco12.com/forum/showthread.php?tid=101
So I downloaded the 1.5GB zip, decompressed to: “G900AUCU1ANCE_G900AATT1ANCE_G900AUCU1ANCE_HOME.tar.md5”
and ran Odin v1.85 with:
“\{Path-to}\G900AUCU1ANCE_G900AATT1ANCE_G900AUCU1ANCE_HOME.tar.md5”
in the PDA slot with Auto Reboot and F. Reset Time checked and no others checked except for PDA. Execution was flawless (ref. image below) and my G900A gracefully rebooted to stock KK 4.4.2--- with all of my installed apps, data and settings intact. And I quickly recovered root by re-launching the towelroot APK.
Of course I did lose busybox since it installs under /system/xbin. No problem, I just went to the BB app I had installed earlier and reinstalled BB from there.
Note: When I stripped off the .md5 suffix and opened the resulting .tar file with 7zip, an error message was returned but the file listing was still shown:
Note the absence of a data image --- a good thing if you have installed apps etc.
Something else I found helpful is the G900A partition map. Navigating to /dev/block/platform/msm_sdcc.1/by-name …
Code:
cd /dev/block/platform/msm_sdcc.1/by-name
[email protected]:/dev/block/platform/msm_sdcc.1/by-name # ls -ld *
ls -ld *
lrwxrwxrwx root root 2014-01-02 11:49 aboot -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 2014-01-02 11:49 apnhlos -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 2014-01-02 11:49 backup -> /dev/block/mmcblk0p18
lrwxrwxrwx root root 2014-01-02 11:49 boot -> /dev/block/mmcblk0p15
lrwxrwxrwx root root 2014-01-02 11:49 cache -> /dev/block/mmcblk0p24
lrwxrwxrwx root root 2014-01-02 11:49 dbi -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 2014-01-02 11:49 ddr -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 2014-01-02 11:49 efs -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 2014-01-02 11:49 fota -> /dev/block/mmcblk0p17
lrwxrwxrwx root root 2014-01-02 11:49 fsc -> /dev/block/mmcblk0p19
lrwxrwxrwx root root 2014-01-02 11:49 fsg -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 2014-01-02 11:49 modem -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 2014-01-02 11:49 modemst1 -> /dev/block/mmcblk0p13
lrwxrwxrwx root root 2014-01-02 11:49 modemst2 -> /dev/block/mmcblk0p14
lrwxrwxrwx root root 2014-01-02 11:49 pad -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 2014-01-02 11:49 param -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 2014-01-02 11:49 persdata -> /dev/block/mmcblk0p22
lrwxrwxrwx root root 2014-01-02 11:49 persist -> /dev/block/mmcblk0p21
lrwxrwxrwx root root 2014-01-02 11:49 recovery -> /dev/block/mmcblk0p16
lrwxrwxrwx root root 2014-01-02 11:49 rpm -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 2014-01-02 11:49 sbl1 -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 2014-01-02 11:49 ssd -> /dev/block/mmcblk0p20
lrwxrwxrwx root root 2014-01-02 11:49 system -> /dev/block/mmcblk0p23
lrwxrwxrwx root root 2014-01-02 11:49 tz -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 2014-01-02 11:49 userdata -> /dev/block/mmcblk0p25
[email protected]:/dev/block/platform/msm_sdcc.1/by-name #
Note especially the boot, recovery, system, data and cache partitions…
Code:
lrwxrwxrwx root root 2014-01-02 11:49 aboot -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 2014-01-02 11:49 boot -> /dev/block/mmcblk0p15
lrwxrwxrwx root root 2014-01-02 11:49 cache -> /dev/block/mmcblk0p24
lrwxrwxrwx root root 2014-01-02 11:49 persdata -> /dev/block/mmcblk0p22
lrwxrwxrwx root root 2014-01-02 11:49 recovery -> /dev/block/mmcblk0p16
lrwxrwxrwx root root 2014-01-02 11:49 system -> /dev/block/mmcblk0p23
lrwxrwxrwx root root 2014-01-02 11:49 userdata -> /dev/block/mmcblk0p25
Many thanks to Rwilco12 for SGS5 support: http://www.rwilco12.com/
Also thanks to Krang for consolidating Rwilco12’s SGS5 links: http://www.rwilco12.com/forum/member.php?action=profile&uid=450
Click to expand...
Click to collapse
Actually a little searching on the forums and you'll find a very simple painless way to reroot after the update, also odin 3.09 or 3.10 is the current version. And if you also search for safestrap in the forums you'll find recovery. You have provided a lot of info here thanks for that but could have saved yourself a lot of grief and time by searching first
Sent from my SAMSUNG-SM-G900A using XDA Free mobile app

Question, did this return the phone to stock completely? Removing root and safestrap?

can not locate
cstayton said:
Actually a little searching on the forums and you'll find a very simple painless way to reroot after the update, also odin 3.09 or 3.10 is the current version. And if you also search for safestrap in the forums you'll find recovery. You have provided a lot of info here thanks for that but could have saved yourself a lot of grief and time by searching first
Sent from my SAMSUNG-SM-G900A using XDA Free mobile app
Click to expand...
Click to collapse
Safestrap is not available for the SM-G900A? i can not find any.

ZD551KL/ZE550KL/ZE551KL/ZE600KL/ZE601KL official bootloader unlock

Released on asus website 14/12/2015:
Marshmallow:
http://dlcdnet.asus.com/pub/ASUS/ZenFone/ZE551KL/UnlockTool_ASUS_AndroidM20160928_Singed.zip
Lollipop:
http://dlcdnet.asus.com/pub/ASUS/ZenFone/ZE600KL/ZE600KL_UnlockApp.zip
The APKs for each are binary identical, so it is not really important which unlock utility you download.
Frequently asked questions:
Q: will this work on ZE500KG / ZE500KL / ASUS_Z00RD / ASUS_Z00RD_5 / ASUS_Z00RD_7 / ASUS_Z00ED / ASUS_Z00EDB / ASUS_Z00E_1 / ASUS_Z00E_2 / ASUS_Z00E_3
A: we do not think so, but we do not know if anyone has tried it.
Q: can I relock bootloader?
A: we do not have a way of re-locking bootloader right now. Hopefully it will be possible using a backup of some partition to restore original bootloader, but we have not found it yet.
Q: can I restore my warranty by re-locking the bootloader?
A: we believe that ASUS records the serial number of the device through the unlock utility, so it will not be possible to make a warranty claim even if you do manage to re-lock the bootloader.
Q: can I still receive OTA updates?
A: we do not know, because no updates have been released since the unlock utility was released.
Q: can I still update firmware manually?
A: yes, definitely. fetch the new firmware zip from ASUS website and flash in stock recovery or transfer to root of sd-card and boot the phone normally (it will find the update zip file and prompt you).
Download notes from the site:
Unlock Device App: Unlock boot loader
Notice:
1. Update your software image to V1.15.40.771 or latest version
2. Before you download, install, and use the Unlock Device App you acknowledge and assume complete risk to the quality and performance of this App, including but not limited to the following: once you activate the App you will not be able to recover your ASUS product (“Original Product”) back to original locked conditions; the Original Product with the activated App will not be deemed the Original Product; the Revised Product will no longer be covered under the warranty of the Original Product; the software of Revised Product will no longer be deemed the software of the Original Product and can no longer receive ASUS software updates; your purchased digital content may also be affected.
You also acknowledge ASUS does not guarantee service satisfaction to any Revised Product, including events involving paid service requested by you to be performed to the Revised Product.
Furthermore, such repaired Revised Product will not be covered under the warranty of the Original Product; the software of the repaired Revised Product will not be deemed the software of the Original Product and will not receive ASUS software updates.
It is strongly advised that you avoid activating this App unless you fully understand and accept the risks that may arise.
Click to expand...
Click to collapse

Do you think this would work on the US 551KL? If so thatd be great

* edit *
firmware v1.15.40.771 now released for ZE600KL, so I will try to flash now on ZE550KL and then unlock
http://dlcdnet.asus.com/pub/ASUS/ZenFone/ZE600KL/UL-Z00L-WW-1.15.40.771-user.zip

Please note, I have ZE550KL-1A025TW version, Snapdragon 615, 2GB RAM (ASUS_Z00LD / ASUS_Z00L_93)
I updated my ZE550KL to firmware v1.15.40.771:
http://dlcdnet.asus.com/pub/ASUS/ZenFone/ZE600KL/UL-Z00L-WW-1.15.40.771-user.zip
then ran the ZE600KL unlock utility.
Unlock utility runs without errors, phone reboots, no errors, everything still working fine.
Confirmed unlock successful
Code:
C:\adb>fastboot oem device-info
...
(bootloader) Device unlocked: true
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
OKAY [ 0.010s]
finished. total time: 0.010s

Let me get this straight, you flashed ZE600KL firmware on your ZE550KL and it worked? Not something I would recommend.

Yeh i did, in the source code they seem to be built with identical makefiles so i just figured i would experiment
Sent from my GT-I9195 using Tapatalk

You can test your bootloader status, if you type in fastboot mode "fastboot oem device-info"

Can someone please paste the output on a rooted ZE550KL in adb shell:
Code:
ls -al /dev/block/platform/dw_mmc/by-name
I already compiled a cm recovery, but i am not sure about the block names...

destilant said:
Can someone please paste the output on a rooted ZE550KL in adb shell:
I already compiled a cm recovery, but i am not sure about the block names...
Click to expand...
Click to collapse
Would the recovery also work for a 551KL? I can get you that, if i can help. And also test the recovery

wickedpygmy said:
Yeh i did, in the source code they seem to be built with identical makefiles so i just figured i would experiment
Sent from my GT-I9195 using Tapatalk
Click to expand...
Click to collapse
fair enough. How do it look? The 600KL is a 6" phone and the 5500KL a 5.5". Does it appear to overlap or anything?

capeorigins said:
Would the recovery also work for a 551KL? I can get you that, if i can help. And also test the recovery
Click to expand...
Click to collapse
Nope, the ZE551KL is shipped with a Snapdragon 615 MSM8939, the ZE550KL with a 610 MSM8916, so it wont work...

destilant said:
You can test your bootloader status, if you type in fastboot mode "fastboot oem device-info"
Click to expand...
Click to collapse
Code:
C:\adb>adb devices
List of devices attached
F8AZCY01P722 device
C:\adb>adb reboot bootloader
C:\adb>fastboot oem device-info
...
(bootloader) Device unlocked: true
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
OKAY [ 0.010s]
finished. total time: 0.010s
C:\adb>

destilant said:
Can someone please paste the output on a rooted ZE550KL in adb shell:
Code:
ls -al /dev/block/platform/dw_mmc/by-name
I already compiled a cm recovery, but i am not sure about the block names...
Click to expand...
Click to collapse
Moreover, can somebody please upload raw backups of the 'aboot' (& 'abootbak' if present) partition before & after unlocking the bootloader? You need root access & can use something like this one.

destilant said:
You can test your bootloader status, if you type in fastboot mode "fastboot oem device-info"
Click to expand...
Click to collapse
heywheelie said:
fair enough. How do it look? The 600KL is a 6" phone and the 5500KL a 5.5". Does it appear to overlap or anything?
Click to expand...
Click to collapse
looks normal, both have same resolution. I think both phones use the same firmware since the kernel is identical and Asus don't release Z00m firmware but use Z00L for both models.

Titokhan said:
Moreover, can somebody please upload raw backups of the 'aboot' (& 'abootbak' if present) partition before & after unlocking the bootloader? You need root access & can use something like this one.
Click to expand...
Click to collapse
@Titokhan must be too late for me to do this, since I already unlocked and have no way to get back?
attached is aboot and abootbak after unlocking, maybe @heywheelie can upload the before?

destilant said:
Nope, the ZE551KL is shipped with a Snapdragon 615 MSM8939, the ZE550KL with a 610 MSM8916, so it wont work...
Click to expand...
Click to collapse
the ZE550KL has a snapdragon 615 not 610

destilant said:
Can someone please paste the output on a rooted ZE550KL in adb shell:
Code:
ls -al /dev/block/platform/dw_mmc/by-name
I already compiled a cm recovery, but i am not sure about the block names...
Click to expand...
Click to collapse
doesnt look like folder exists.
Code:
[email protected]_Z00L_93:/ # ls -al /dev/block/platform/
drwxr-xr-x root root 1970-05-15 01:49 7824900.sdhci
[email protected]_Z00L_93:/ #

heywheelie said:
the ZE550KL has a snapdragon 615 not 610
Click to expand...
Click to collapse
init! i wish people would stop polluting the version/hardware topic, especially since its so confusing already

wickedpygmy said:
looks normal, both have same resolution. I think both phones use the same firmware since the kernel is identical and Asus don't release Z00m firmware but use Z00L for both models.
Click to expand...
Click to collapse
might be same firmware but specs do differ slightly
https://www.asus.com/Phone/ZenFone-2-Laser-ZE550KL/specifications/
https://www.asus.com/Phone/ZenFone-2-Laser-ZE600KL/specifications/
WLAN bands differ, bluetooth is 4.0 on 550 and 4.1 on 6.0. Nothing dramatic but different

destilant said:
Can someone please paste the output on a rooted ZE550KL in adb shell:
Code:
ls -al /dev/block/platform/dw_mmc/by-name
I already compiled a cm recovery, but i am not sure about the block names...
Click to expand...
Click to collapse
This any use?
Code:
[email protected]_Z00L_93:/ # ls -al /dev/block/platform/7824900.sdhci/by-name
lrwxrwxrwx root root 1970-05-15 01:49 ADF -> /dev/block/mmcblk0p42
lrwxrwxrwx root root 1970-05-15 01:49 APD -> /dev/block/mmcblk0p43
lrwxrwxrwx root root 1970-05-15 01:49 DDR -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 1970-05-15 01:49 aboot -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 1970-05-15 01:49 abootbak -> /dev/block/mmcblk0p13
lrwxrwxrwx root root 1970-05-15 01:49 abootdebug -> /dev/block/mmcblk0p34
lrwxrwxrwx root root 1970-05-15 01:49 asdf -> /dev/block/mmcblk0p33
lrwxrwxrwx root root 1970-05-15 01:49 asusfw -> /dev/block/mmcblk0p40
lrwxrwxrwx root root 1970-05-15 01:49 asusgpt -> /dev/block/mmcblk0p27
lrwxrwxrwx root root 1970-05-15 01:49 asusgpt1 -> /dev/block/mmcblk0p28
lrwxrwxrwx root root 1970-05-15 01:49 asusgpt2 -> /dev/block/mmcblk0p29
lrwxrwxrwx root root 1970-05-15 01:49 asuskey -> /dev/block/mmcblk0p22
lrwxrwxrwx root root 1970-05-15 01:49 asuskey2 -> /dev/block/mmcblk0p23
lrwxrwxrwx root root 1970-05-15 01:49 asuskey3 -> /dev/block/mmcblk0p24
lrwxrwxrwx root root 1970-05-15 01:49 asuskey4 -> /dev/block/mmcblk0p25
lrwxrwxrwx root root 1970-05-15 01:49 asuskey5 -> /dev/block/mmcblk0p26
lrwxrwxrwx root root 1970-05-15 01:49 boot -> /dev/block/mmcblk0p37
lrwxrwxrwx root root 1970-05-15 01:49 cache -> /dev/block/mmcblk0p44
lrwxrwxrwx root root 1970-05-15 01:49 config -> /dev/block/mmcblk0p32
lrwxrwxrwx root root 1970-05-15 01:49 devinfo -> /dev/block/mmcblk0p15
lrwxrwxrwx root root 1970-05-15 01:49 factory -> /dev/block/mmcblk0p20
lrwxrwxrwx root root 1970-05-15 01:49 factorybak -> /dev/block/mmcblk0p21
lrwxrwxrwx root root 1970-05-15 01:49 fsc -> /dev/block/mmcblk0p17
lrwxrwxrwx root root 1970-05-15 01:49 fsg -> /dev/block/mmcblk0p16
lrwxrwxrwx root root 1970-05-15 01:49 hyp -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 1970-05-15 01:49 hypbak -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 1970-05-15 01:49 keystore -> /dev/block/mmcblk0p31
lrwxrwxrwx root root 1970-05-15 01:49 misc -> /dev/block/mmcblk0p30
lrwxrwxrwx root root 1970-05-15 01:49 modem -> /dev/block/mmcblk0p41
lrwxrwxrwx root root 1970-05-15 01:49 modemst1 -> /dev/block/mmcblk0p18
lrwxrwxrwx root root 1970-05-15 01:49 modemst2 -> /dev/block/mmcblk0p19
lrwxrwxrwx root root 1970-05-15 01:49 oem -> /dev/block/mmcblk0p36
lrwxrwxrwx root root 1970-05-15 01:49 persist -> /dev/block/mmcblk0p39
lrwxrwxrwx root root 1970-05-15 01:49 persistent -> /dev/block/mmcblk0p35
lrwxrwxrwx root root 1970-05-15 01:49 recovery -> /dev/block/mmcblk0p38
lrwxrwxrwx root root 1970-05-15 01:49 rpm -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 1970-05-15 01:49 rpmbak -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 1970-05-15 01:49 sbl1 -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 1970-05-15 01:49 sbl1bak -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 1970-05-15 01:49 sec -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 1970-05-15 01:49 splash -> /dev/block/mmcblk0p14
lrwxrwxrwx root root 1970-05-15 01:49 ssd -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 1970-05-15 01:49 system -> /dev/block/mmcblk0p45
lrwxrwxrwx root root 1970-05-15 01:49 tz -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 1970-05-15 01:49 tzbak -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 1970-05-15 01:49 userdata -> /dev/block/mmcblk0p46
[email protected]_Z00L_93:/ #

Database Develop

welcome