Related
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
HTML:
[email protected]:/ # cat /proc/partitions
cat /proc/partitions
major minor #blocks name
253 0 1048576 vnswap0
179 0 15388672 mmcblk0
179 1 15360 mmcblk0p1
179 2 58816 mmcblk0p2
179 3 512 mmcblk0p3
179 4 64 mmcblk0p4
179 5 32 mmcblk0p5
179 6 2048 mmcblk0p6
179 7 512 mmcblk0p7
179 8 512 mmcblk0p8
179 9 3072 mmcblk0p9
179 10 7136 mmcblk0p10
179 11 10240 mmcblk0p11
179 12 14336 mmcblk0p12
179 13 3072 mmcblk0p13
179 14 3072 mmcblk0p14
179 15 13312 mmcblk0p15
179 16 15360 mmcblk0p16
179 17 13312 mmcblk0p17
179 18 7159 mmcblk0p18
179 19 1 mmcblk0p19
179 20 8 mmcblk0p20
179 21 8192 mmcblk0p21
179 22 9216 mmcblk0p22
179 23 2536448 mmcblk0p23
179 24 512000 mmcblk0p24
179 25 12150767 mmcblk0p25
179 32 512 mmcblk0rpmb
[email protected]:/ # cd /dev/block/platform/msm_sdcc.1
cd /dev/block/platform/msm_sdcc.1
[email protected]:/dev/block/platform/msm_sdcc.1 # ls -l by-name
ls -l by-name
lrwxrwxrwx root root 2014-01-01 09:08 aboot -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 2014-01-01 09:08 apnhlos -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 2014-01-01 09:08 backup -> /dev/block/mmcblk0p18
lrwxrwxrwx root root 2014-01-01 09:08 boot -> /dev/block/mmcblk0p15
lrwxrwxrwx root root 2014-01-01 09:08 cache -> /dev/block/mmcblk0p24
lrwxrwxrwx root root 2014-01-01 09:08 dbi -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 2014-01-01 09:08 ddr -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 2014-01-01 09:08 efs -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 2014-01-01 09:08 fota -> /dev/block/mmcblk0p17
lrwxrwxrwx root root 2014-01-01 09:08 fsc -> /dev/block/mmcblk0p19
lrwxrwxrwx root root 2014-01-01 09:08 fsg -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 2014-01-01 09:08 modem -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 2014-01-01 09:08 modemst1 -> /dev/block/mmcblk0p13
lrwxrwxrwx root root 2014-01-01 09:08 modemst2 -> /dev/block/mmcblk0p14
lrwxrwxrwx root root 2014-01-01 09:08 pad -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 2014-01-01 09:08 param -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 2014-01-01 09:08 persdata -> /dev/block/mmcblk0p22
lrwxrwxrwx root root 2014-01-01 09:08 persist -> /dev/block/mmcblk0p21
lrwxrwxrwx root root 2014-01-01 09:08 recovery -> /dev/block/mmcblk0p16
lrwxrwxrwx root root 2014-01-01 09:08 rpm -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 2014-01-01 09:08 sbl1 -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 2014-01-01 09:08 ssd -> /dev/block/mmcblk0p20
lrwxrwxrwx root root 2014-01-01 09:08 system -> /dev/block/mmcblk0p23
lrwxrwxrwx root root 2014-01-01 09:08 tz -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 2014-01-01 09:08 userdata -> /dev/block/mmcblk0p25
DUMP CODE
HTML:
adb shell su -c "dd if=/dev/block/mmcblk0p6 of=/sdcard/aboot"
adb shell su -c "dd if=/dev/block/mmcblk0p1 of=/sdcard/apnhlos"
adb shell su -c "dd if=/dev/block/mmcblk0p18 of=/sdcard/backup"
adb shell su -c "dd if=/dev/block/mmcblk0p15 of=/sdcard/boot"
adb shell su -c "dd if=/dev/block/mmcblk0p24 of=/sdcard/cache"
adb shell su -c "dd if=/dev/block/mmcblk0p4 of=/sdcard/dbi"
adb shell su -c "dd if=/dev/block/mmcblk0p5 of=/sdcard/ddr"
adb shell su -c "dd if=/dev/block/mmcblk0p12 of=/sdcard/efs"
adb shell su -c "dd if=/dev/block/mmcblk0p17 of=/sdcard/fota"
adb shell su -c "dd if=/dev/block/mmcblk0p19 of=/sdcard/fsc"
adb shell su -c "dd if=/dev/block/mmcblk0p9 of=/sdcard/fsg"
adb shell su -c "dd if=/dev/block/mmcblk0p2 of=/sdcard/modem"
adb shell su -c "dd if=/dev/block/mmcblk0p13 of=/sdcard/modemst1"
adb shell su -c "dd if=/dev/block/mmcblk0p14 of=/sdcard/modemst2"
adb shell su -c "dd if=/dev/block/mmcblk0p10 of=/sdcard/pad"
adb shell su -c "dd if=/dev/block/mmcblk0p11 of=/sdcard/param"
adb shell su -c "dd if=/dev/block/mmcblk0p22 of=/sdcard/persdata"
adb shell su -c "dd if=/dev/block/mmcblk0p21 of=/sdcard/persist"
adb shell su -c "dd if=/dev/block/mmcblk0p16 of=/sdcard/recovery"
adb shell su -c "dd if=/dev/block/mmcblk0p7 of=/sdcard/rpm"
adb shell su -c "dd if=/dev/block/mmcblk0p3 of=/sdcard/sbl1"
adb shell su -c "dd if=/dev/block/mmcblk0p20 of=/sdcard/ssd"
adb shell su -c "dd if=/dev/block/mmcblk0p23 of=/sdcard/system"
adb shell su -c "dd if=/dev/block/mmcblk0p8 of=/sdcard/tz"
adb shell su -c "dd if=/dev/block/mmcblk0 of=/sdcard/G900W8_1G bs=512 count=2097152"
all files download link: http://pan.baidu.com/s/1hquseiw password: wai9
Is it possible for you to upload the files other than the chinese site please? DropBox or something like Mega Upload?
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.
These are the partitions for the UnitedStates Cricket Desire 510 if anybody needs them
[email protected]_a11ul8x26:/ $ ls -al /dev/block/bootdevice/by-name
ls -al /dev/block/bootdevice/by-name
lrwxrwxrwx root root 2014-12-31 16:00 adsp -> /dev/block/mmcblk
0p16
lrwxrwxrwx root root 2014-12-31 16:00 board_info -> /dev/block/
mmcblk0p3
lrwxrwxrwx root root 2014-12-31 16:00 boot -> /dev/block/mmcblk
0p40
lrwxrwxrwx root root 2014-12-31 16:00 cache -> /dev/block/mmcbl
k0p42
lrwxrwxrwx root root 2014-12-31 16:00 carrier -> /dev/block/mmc
blk0p37
lrwxrwxrwx root root 2014-12-31 16:00 cdma_record -> /dev/block
/mmcblk0p33
lrwxrwxrwx root root 2014-12-31 16:00 control -> /dev/block/mmc
blk0p30
lrwxrwxrwx root root 2014-12-31 16:00 custdata -> /dev/block/mm
cblk0p22
lrwxrwxrwx root root 2014-12-31 16:00 ddr -> /dev/block/mmcblk0
p14
lrwxrwxrwx root root 2014-12-31 16:00 debug_config -> /dev/bloc
k/mmcblk0p28
lrwxrwxrwx root root 2014-12-31 16:00 devlog -> /dev/block/mmcb
lk0p38
lrwxrwxrwx root root 2014-12-31 16:00 dsps -> /dev/block/mmcblk
0p15
lrwxrwxrwx root root 2014-12-31 16:00 extra -> /dev/block/mmcbl
k0p32
lrwxrwxrwx root root 2014-12-31 16:00 fataldevlog -> /dev/block
/mmcblk0p27
lrwxrwxrwx root root 2014-12-31 16:00 fsc -> /dev/block/mmcblk0
p34
lrwxrwxrwx root root 2014-12-31 16:00 fsg -> /dev/block/mmcblk0
p19
lrwxrwxrwx root root 2014-12-31 16:00 hboot -> /dev/block/mmcbl
k0p11
lrwxrwxrwx root root 2014-12-31 16:00 local -> /dev/block/mmcbl
k0p31
lrwxrwxrwx root root 2014-12-31 16:00 mfg -> /dev/block/mmcblk0
p5
lrwxrwxrwx root root 2014-12-31 16:00 misc -> /dev/block/mmcblk
0p24
lrwxrwxrwx root root 2014-12-31 16:00 modem_st1 -> /dev/block/m
mcblk0p25
lrwxrwxrwx root root 2014-12-31 16:00 modem_st2 -> /dev/block/m
mcblk0p26
lrwxrwxrwx root root 2014-12-31 16:00 pdata -> /dev/block/mmcbl
k0p29
lrwxrwxrwx root root 2014-12-31 16:00 pg1fs -> /dev/block/mmcbl
k0p2
lrwxrwxrwx root root 2014-12-31 16:00 pg2fs -> /dev/block/mmcbl
k0p6
lrwxrwxrwx root root 2014-12-31 16:00 radio -> /dev/block/mmcbl
k0p20
lrwxrwxrwx root root 2014-12-31 16:00 radio_config -> /dev/bloc
k/mmcblk0p18
lrwxrwxrwx root root 2014-12-31 16:00 recovery -> /dev/block/mm
cblk0p41
lrwxrwxrwx root root 2014-12-31 16:00 reserve -> /dev/block/mmc
blk0p39
lrwxrwxrwx root root 2014-12-31 16:00 reserve_1 -> /dev/block/m
mcblk0p4
lrwxrwxrwx root root 2014-12-31 16:00 reserve_2 -> /dev/block/m
mcblk0p23
lrwxrwxrwx root root 2014-12-31 16:00 rpm -> /dev/block/mmcblk0
p8
lrwxrwxrwx root root 2014-12-31 16:00 sbl1 -> /dev/block/mmcblk
0p1
lrwxrwxrwx root root 2014-12-31 16:00 sbl1_update -> /dev/block
/mmcblk0p7
lrwxrwxrwx root root 2014-12-31 16:00 sdi -> /dev/block/mmcblk0
p10
lrwxrwxrwx root root 2014-12-31 16:00 skylink -> /dev/block/mmc
blk0p36
lrwxrwxrwx root root 2014-12-31 16:00 sp1 -> /dev/block/mmcblk0
p12
lrwxrwxrwx root root 2014-12-31 16:00 ssd -> /dev/block/mmcblk0
p35
lrwxrwxrwx root root 2014-12-31 16:00 system -> /dev/block/mmcb
lk0p43
lrwxrwxrwx root root 2014-12-31 16:00 tool_diag -> /dev/block/m
mcblk0p21
lrwxrwxrwx root root 2014-12-31 16:00 tz -> /dev/block/mmcblk0p
9
lrwxrwxrwx root root 2014-12-31 16:00 userdata -> /dev/block/mm
cblk0p44
lrwxrwxrwx root root 2014-12-31 16:00 wcnss -> /dev/block/mmcbl
k0p17
lrwxrwxrwx root root 2014-12-31 16:00 wifi -> /dev/block/mmcblk
0p13
[email protected]_a11ul8x26:/ $
Pretty sure the few 510 devs that we do have are already aware of this.
HampTheToker said:
Pretty sure the few 510 devs that we do have are already aware of this.
Click to expand...
Click to collapse
Yep, we sure are lol.. Regular users really wouldn't have a need for this type of information.
Yes i understand but there are people who build roms that donnot know how to do this i am a dev myself and didnt know how to do this when i first started building roms
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:/ #