UPDATE: As you can see from the page 5 and some good trial and error, the port may be related to Chrome to Phone. Whew.
I am posting this as a separate thread as I do not know the extent to which my observation applies...
Recently I flashed the SkyRaider 2.2 Sense ROM (updated the radio, no extra apps etc.) and found the ROM to be great - everything worked.
As I am a Linux geek as well - Using the busybox utilities I checked for open ports on the phone. As with the stock ROMs, two TCP ports were open for dmagent and com.htc.bgp. However, there was also a UDP port (13010) that was open.
/system/xbin/netstat -p
did not identify the process that opened the port, although it did identify the processes that opened the TCP ports.
The reason netstat could not identify the process is because it could not map the inode of socket handle to a process listed under the /proc directory.
If you see an open port on your phone, then
cat /proc/net/udp
and you should see a line of information for the open port and an inode number (for me it was 104)
For running processes, there is an information directory under /proc/<pid> (e.g. /proc/2435) and below that and fd subdirectory with handle numbers for files and sockets. So for example if you
/system/xbin/ls -l /proc/<anypid>/fd
you may see something like
5 -> socket:[<inode>]
The problem with my ROM is that there is no process with a # -> socket:[104] in its fd directory. So I don't know what opened it, if it is still open or what would happen if I hit the port with a datagram.
So my question is - are other SkyRaider 2.2 Sense people seeing the same? Are other leaked Froyo derivatives seeing the same?
As I don't like to run around with apparently open and unidentified ports, I reverted back to stock.
P.S. I PMed the SkyRaider author and he replied that he did not know what the port was and I have not heard back - so I thought I should at least post what I have seen so that others can look into it. Maybe I'm just too paranoid.
This could be random, but it seems that port 13010 is used by a Trojan type virus.
Protocol Service Name
tcp *****Controller [trojan] *****Controller
tcp HackerBrasilHBR [trojan] Hacker Brasil - HBR
tcp HackerBrasil [trojan] Hacker Brasil - HBR
can somebody explain this in simpleton terms?
...cause it sounds like shizzle just got deep.
I in no way want to panic anyone - or even state for certain that this is any more than a weird oddity on my phone.
In simple terms - programs can open "listening" ports on their computer (or in this case the phone as it is Linux under the hood) so that external computers can connect and communicate. There are all sorts of protections that can be applied, firewalls, and binding open ports to certain interfaces,etc.
In my case I saw a port open that I could not identify to originator (process) that was bound to any interface and by default the iptables firewall is down - so it is open. The big difference between TCP and UDP is that TCP sets up a "pipe" between the computers whereas UDP accepts little messages one at time.
I'm only bringing this up to see if anyone else sees the same thing.
If not - I am honestly sorry for having brought it up. But for safety's sake I thought I should at least post what I saw.
Nic2112 said:
This could be random, but it seems that port 13010 is used by a Trojan type virus.
Protocol Service Name
tcp *****Controller [trojan] *****Controller
tcp HackerBrasilHBR [trojan] Hacker Brasil - HBR
tcp HackerBrasil [trojan] Hacker Brasil - HBR
Click to expand...
Click to collapse
I saw that too although it probably is unrelated to this (a Windows trojan for example). But the port number was ominous.
Im sure 90% of the ports on Windows are ran by trojans .. and I'm also positive that anyone that write in a Trojan for Android would pick a different port ... that being said I'm still interested to know what's goin on with this port
I have the same open port. But I'm not freaking out yet. I am on skyraider 2.2 sense, I use exchange, and 2 gmail accounts. All other sync'ing is turned off. We have the device security on, on our exchange servers (so they can remote wipe and whatnot).
When I do:
ls -l /proc/104/fd
It returns a bunch of entries (unless I did something wrong):
ls -l /proc/104/fd
lrwx------ system system 2010-08-10 13:10 0 -> /dev/null
lrwx------ system system 2010-08-10 13:10 1 -> /dev/null
lrwx------ system system 2010-08-10 13:10 2 -> /dev/null
l-wx------ system system 2010-08-10 13:10 3 -> /dev/log/main
l-wx------ system system 2010-08-10 13:10 4 -> /dev/log/radio
l-wx------ system system 2010-08-10 13:10 5 -> /dev/log/events
lr-x------ system system 2010-08-10 13:10 6 -> /dev/mmcblk0p1 (dele
ted)
lr-x------ system system 2010-08-10 13:10 7 -> /dev/mmcblk0p2 (dele
ted)
l-wx------ system system 2010-08-10 13:10 8 -> /dev/log/system
lr-x------ system system 2010-08-10 13:10 9 -> /system/framework/co
re.jar
lr-x------ system system 2010-08-10 13:10 10 -> /system/framework/e
xt.jar
lrwx------ system system 2010-08-10 13:10 11 -> /dev/ashmem
lrwx------ system system 2010-08-10 13:10 12 -> /dev/binder
lr-x------ system system 2010-08-10 13:10 13 -> /system/framework/f
ramework.jar
lr-x------ system system 2010-08-10 13:10 14 -> /system/framework/a
ndroid.policy.jar
lr-x------ system system 2010-08-10 13:10 15 -> /system/framework/s
ervices.jar
lr-x------ system system 2010-08-10 13:10 16 -> /system/framework/c
om.htc.framework.jar
lr-x------ system system 2010-08-10 13:10 17 -> /system/framework/c
om.htc.android.pimlib.jar
lr-x------ system system 2010-08-10 13:10 18 -> /system/framework/c
om.htc.android.easopen.jar
lr-x------ system system 2010-08-10 13:10 19 -> /system/framework/c
om.scalado.util.ScaladoUtil.jar
lr-x------ system system 2010-08-10 13:10 20 -> /system/framework/f
ramework.jar
lr-x------ system system 2010-08-10 13:10 21 -> /system/fonts/Droid
Sans.ttf
lr-x------ system system 2010-08-10 13:10 22 -> /system/framework/c
ore.jar
lr-x------ system system 2010-08-10 13:10 23 -> /dev/urandom
lr-x------ system system 2010-08-10 13:10 24 -> /system/framework/f
ramework-res.apk
lr-x------ system system 2010-08-10 13:10 25 -> /system/framework/c
om.htc.resources.apk
lrwx------ system system 2010-08-10 13:10 26 -> socket:[586]
lr-x------ system system 2010-08-10 13:10 27 -> pipe:[587]
l-wx------ system system 2010-08-10 13:10 28 -> pipe:[587]
lrwx------ system system 2010-08-10 13:10 29 -> /dev/ashmem
lrwx------ system system 2010-08-10 13:10 30 -> /dev/graphics/fb0
lrwx------ system system 2010-08-10 13:10 31 -> /dev/graphics/fb0
lrwx------ system system 2010-08-10 13:10 32 -> /dev/graphics/fb0
lrwx------ system system 2010-08-10 13:10 33 -> /dev/graphics/fb0
lrwx------ system system 2010-08-10 13:10 34 -> /dev/kgsl
lrwx------ system system 2010-08-10 13:10 35 -> /dev/ashmem
lr-x------ system system 2010-08-10 13:10 36 -> /dev/alarm
lrwx------ system system 2010-08-10 13:10 37 -> /dev/ashmem
lrwx------ system system 2010-08-10 13:10 38 -> /dev/pmem
lrwx------ system system 2010-08-10 13:10 39 -> /dev/ashmem
lrwx------ system system 2010-08-10 13:10 40 -> /dev/ashmem
lrwx------ system system 2010-08-10 13:10 41 -> socket:[753]
l-wx------ system system 2010-08-10 13:10 42 -> /dev/cpuctl/tasks
l-wx------ system system 2010-08-10 13:10 43 -> /dev/cpuctl/bg_non_
interactive/tasks
lr-x------ system system 2010-08-10 13:10 44 -> inotify
lrwx------ system system 2010-08-10 13:10 45 -> /dev/pmem
lr-x------ system system 2010-08-10 13:10 46 -> /system/fonts/Droid
SansMono.ttf
lrwx------ system system 2010-08-10 13:10 47 -> /data/data/com.andr
oid.providers.htcCheckin/databases/htcCheckin.db
lrwx------ system system 2010-08-10 13:10 48 -> /dev/ashmem
lrwx------ system system 2010-08-10 13:10 49 -> /dev/ashmem
lrwx------ system system 2010-08-10 13:10 50 -> socket:[1161]
lrwx------ system system 2010-08-10 13:10 51 -> socket:[1192]
lrwx------ system system 2010-08-10 13:10 52 -> /dev/ashmem
lrwx------ system system 2010-08-10 13:10 53 -> /dev/ashmem
lrwx------ system system 2010-08-10 13:10 54 -> /dev/ashmem
lrwx------ system system 2010-08-10 13:10 55 -> /data/system/accoun
ts.db
lrwx------ system system 2010-08-10 13:10 56 -> /dev/ashmem
lrwx------ system system 2010-08-10 13:10 57 -> /dev/ashmem
lrwx------ system system 2010-08-10 13:10 58 -> /dev/ashmem
lrwx------ system system 2010-08-10 13:10 59 -> /dev/pmem
lr-x------ system system 2010-08-10 13:10 60 -> /system/app/Setting
sProvider.apk
lr-x------ system system 2010-08-10 13:10 61 -> /system/app/Setting
sProvider.apk
lr-x------ system system 2010-08-10 13:10 62 -> /system/app/Setting
sProvider.apk
lrwx------ system system 2010-08-10 13:10 63 -> /data/data/com.andr
oid.providers.settings/databases/settings.db
lr-x------ system system 2010-08-10 13:10 64 -> /system/app/Checkin
Provider.apk
lr-x------ system system 2010-08-10 13:10 65 -> /system/app/Checkin
Provider.apk
lr-x------ system system 2010-08-10 13:10 66 -> /system/app/Checkin
Provider.apk
lrwx------ system system 2010-08-10 13:10 67 -> socket:[1090]
lrwx------ system system 2010-08-10 13:10 68 -> /dev/ashmem
lrwx------ system system 2010-08-10 13:10 69 -> /dev/alarm
lrwx------ system system 2010-08-10 13:10 70 -> /dev/ashmem
lrwx------ system system 2010-08-10 13:10 71 -> /sys/power/wake_loc
k
lrwx------ system system 2010-08-10 13:10 72 -> /sys/power/wake_unl
ock
lrwx------ system system 2010-08-10 13:10 73 -> /sys/power/state
lr-x------ system system 2010-08-10 13:10 74 -> inotify
lrwx------ system system 2010-08-10 13:10 75 -> /dev/ashmem
lrwx------ system system 2010-08-10 13:10 76 -> /dev/input/event9
lrwx------ system system 2010-08-10 13:10 77 -> /dev/input/event8
lrwx------ system system 2010-08-10 13:10 78 -> /dev/input/event7
lrwx------ system system 2010-08-10 13:10 79 -> /dev/input/event6
lrwx------ system system 2010-08-10 13:10 80 -> socket:[1133]
lrwx------ system system 2010-08-10 13:10 81 -> /dev/input/event5
lrwx------ system system 2010-08-10 13:10 82 -> /dev/input/event4
lrwx------ system system 2010-08-10 13:10 83 -> /dev/input/event3
lrwx------ system system 2010-08-10 13:10 84 -> /dev/input/event2
lrwx------ system system 2010-08-10 13:10 85 -> /dev/input/event1
lrwx------ system system 2010-08-10 13:10 86 -> /dev/input/event0
lrwx------ system system 2010-08-10 13:10 87 -> /dev/ashmem
lrwx------ system system 2010-08-10 13:10 88 -> /dev/ashmem
lrwx------ system system 2010-08-10 13:10 89 -> /dev/ashmem
lrwx------ system system 2010-08-10 13:10 90 -> /dev/ashmem
lrwx------ system system 2010-08-10 13:10 91 -> /dev/ashmem
lrwx------ system system 2010-08-10 13:10 92 -> /dev/ashmem
lrwx------ system system 2010-08-10 13:10 93 -> /dev/ashmem
lrwx------ system system 2010-08-10 13:10 94 -> /dev/pmem
lrwx------ system system 2010-08-10 13:10 95 -> /dev/ashmem
lr-x------ system system 2010-08-10 13:10 96 -> /system/app/HtcLock
Screen.apk
lr-x------ system system 2010-08-10 13:10 97 -> /system/app/HtcLock
Screen.apk
lr-x------ system system 2010-08-10 13:10 98 -> /system/app/HtcLock
Screen.apk
lrwx------ system system 2010-08-10 13:10 99 -> /dev/ashmem
lr-x------ system system 2010-08-10 13:10 100 -> /dev/cm3602
lr-x------ system system 2010-08-10 13:10 101 -> /dev/lightsensor
lrwx------ system system 2010-08-10 13:10 102 -> socket:[1285]
lrwx------ system system 2010-08-10 13:10 103 -> /dev/ashmem
lrwx------ system system 2010-08-10 13:10 104 -> /dev/ashmem
lr-x------ system system 2010-08-10 13:10 105 -> /sys/power/wait_fo
r_fb_wake
lrwx------ system system 2010-08-10 13:10 106 -> /dev/ashmem
lrwx------ system system 2010-08-10 13:10 107 -> /dev/ashmem
lrwx------ system system 2010-08-10 13:10 108 -> /dev/ashmem
lrwx------ system system 2010-08-10 13:10 109 -> /dev/ashmem
lrwx------ system system 2010-08-10 13:10 110 -> /dev/ashmem
lrwx------ system system 2010-08-10 13:10 111 -> /dev/ashmem
lrwx------ system system 2010-08-10 13:10 112 -> /dev/ashmem
lrwx------ system system 2010-08-10 13:10 113 -> /dev/pmem
lrwx------ system system 2010-08-10 13:10 114 -> /dev/ashmem
lrwx------ system system 2010-08-10 13:10 115 -> /dev/pmem
lrwx------ system system 2010-08-10 13:10 116 -> /dev/pmem
lr-x------ system system 2010-08-10 13:10 117 -> /system/fonts/Droi
dSans-Bold.ttf
lrwx------ system system 2010-08-10 13:10 118 -> /dev/ashmem
lrwx------ system system 2010-08-10 13:10 119 -> /dev/ashmem
lrwx------ system system 2010-08-10 13:10 120 -> /dev/ashmem
lrwx------ system system 2010-08-10 13:10 121 -> /dev/ashmem
lrwx------ system system 2010-08-10 13:10 122 -> /dev/ashmem
lrwx------ system system 2010-08-10 13:10 123 -> /dev/pmem
lrwx------ system system 2010-08-10 13:10 124 -> /dev/pmem
lrwx------ system system 2010-08-10 13:12 125 -> /dev/pmem
lrwx------ system system 2010-08-10 13:10 128 -> /dev/ashmem
lrwx------ system system 2010-08-10 13:10 130 -> /dev/ashmem
lrwx------ system system 2010-08-10 13:10 132 -> /dev/ashmem
lr-x------ system system 2010-08-10 13:10 133 -> /system/app/Networ
kLocation.apk
lr-x------ system system 2010-08-10 13:10 135 -> /system/app/Networ
kLocation.apk
lr-x------ system system 2010-08-10 13:10 136 -> /system/app/Networ
kLocation.apk
lrwx------ system system 2010-08-10 13:10 137 -> /dev/ashmem
lrwx------ system system 2010-08-10 13:10 139 -> /dev/ashmem
lr-x------ system system 2010-08-10 13:10 140 -> /system/app/PCSCII
.apk
lrwx------ system system 2010-08-10 13:10 144 -> /dev/ashmem
Is that possibly the port which Google uses to remotely shut down phones/apps/etc?
http://androidspin.com/2010/08/10/first-android-sms-trojan-released-into-the-wild/
maybe..
shamowfski said:
I have the same open port. But I'm not freaking out yet.
When I do:
ls -l /proc/104/fd
It returns a bunch of entries (unless I did something wrong):
ls -l /proc/104/fd
lrwx------ system system 2010-08-10 13:10 0 -> /dev/null
lrwx------ system system 2010-08-10 13:10 1 -> /dev/null
lrwx------ system system 2010-08-10 13:10 2 -> /dev/null
l-wx------ system system 2010-08-10 13:10 3 -> /dev/log/main
l-wx------ system system 2010-08-10 13:10 4 -> /dev/log/radio
l-wx------ system system 2010-08-10 13:10 5 -> /dev/log/events
lr-x------ system system 2010-08-10 13:10 6 -> /dev/mmcblk0p1 (dele
ted)
lr-x------ system system 2010-08-10 13:10 7 -> /dev/mmcblk0p2 (dele
ted)
l-wx------ system system 2010-08-10 13:10 8 -> /dev/log/system
lr-x------ system system 2010-08-10 13:10 9 -> /system/framework/co
re.jar
lr-x------ system system 2010-08-10 13:10 10 -> /system/framework/e
xt.jar
lrwx------ system system 2010-08-10 13:10 11 -> /dev/ashmem
lrwx------ system system 2010-08-10 13:10 12 -> /dev/binder
lr-x------ system system 2010-08-10 13:10 13 -> /system/framework/f
ramework.jar
lr-x------ system system 2010-08-10 13:10 14 -> /system/framework/a
ndroid.policy.jar
lr-x------ system system 2010-08-10 13:10 15 -> /system/framework/s
ervices.jar
lr-x------ system system 2010-08-10 13:10 16 -> /system/framework/c
om.htc.framework.jar
lr-x------ system system 2010-08-10 13:10 17 -> /system/framework/c
om.htc.android.pimlib.jar
lr-x------ system system 2010-08-10 13:10 18 -> /system/framework/c
om.htc.android.easopen.jar
lr-x------ system system 2010-08-10 13:10 19 -> /system/framework/c
om.scalado.util.ScaladoUtil.jar
lr-x------ system system 2010-08-10 13:10 20 -> /system/framework/f
ramework.jar
lr-x------ system system 2010-08-10 13:10 21 -> /system/fonts/Droid
Sans.ttf
lr-x------ system system 2010-08-10 13:10 22 -> /system/framework/c
ore.jar
lr-x------ system system 2010-08-10 13:10 23 -> /dev/urandom
lr-x------ system system 2010-08-10 13:10 24 -> /system/framework/f
ramework-res.apk
lr-x------ system system 2010-08-10 13:10 25 -> /system/framework/c
om.htc.resources.apk
lrwx------ system system 2010-08-10 13:10 26 -> socket:[586]
lr-x------ system system 2010-08-10 13:10 27 -> pipe:[587]
l-wx------ system system 2010-08-10 13:10 28 -> pipe:[587]
lrwx------ system system 2010-08-10 13:10 29 -> /dev/ashmem
lrwx------ system system 2010-08-10 13:10 30 -> /dev/graphics/fb0
lrwx------ system system 2010-08-10 13:10 31 -> /dev/graphics/fb0
lrwx------ system system 2010-08-10 13:10 32 -> /dev/graphics/fb0
lrwx------ system system 2010-08-10 13:10 33 -> /dev/graphics/fb0
lrwx------ system system 2010-08-10 13:10 34 -> /dev/kgsl
lrwx------ system system 2010-08-10 13:10 35 -> /dev/ashmem
lr-x------ system system 2010-08-10 13:10 36 -> /dev/alarm
lrwx------ system system 2010-08-10 13:10 37 -> /dev/ashmem
lrwx------ system system 2010-08-10 13:10 38 -> /dev/pmem
lrwx------ system system 2010-08-10 13:10 39 -> /dev/ashmem
lrwx------ system system 2010-08-10 13:10 40 -> /dev/ashmem
lrwx------ system system 2010-08-10 13:10 41 -> socket:[753]
l-wx------ system system 2010-08-10 13:10 42 -> /dev/cpuctl/tasks
l-wx------ system system 2010-08-10 13:10 43 -> /dev/cpuctl/bg_non_
interactive/tasks
lr-x------ system system 2010-08-10 13:10 44 -> inotify
lrwx------ system system 2010-08-10 13:10 45 -> /dev/pmem
lr-x------ system system 2010-08-10 13:10 46 -> /system/fonts/Droid
SansMono.ttf
lrwx------ system system 2010-08-10 13:10 47 -> /data/data/com.andr
oid.providers.htcCheckin/databases/htcCheckin.db
lrwx------ system system 2010-08-10 13:10 48 -> /dev/ashmem
lrwx------ system system 2010-08-10 13:10 49 -> /dev/ashmem
lrwx------ system system 2010-08-10 13:10 50 -> socket:[1161]
lrwx------ system system 2010-08-10 13:10 51 -> socket:[1192]
lrwx------ system system 2010-08-10 13:10 52 -> /dev/ashmem
lrwx------ system system 2010-08-10 13:10 53 -> /dev/ashmem
lrwx------ system system 2010-08-10 13:10 54 -> /dev/ashmem
lrwx------ system system 2010-08-10 13:10 55 -> /data/system/accoun
ts.db
lrwx------ system system 2010-08-10 13:10 56 -> /dev/ashmem
lrwx------ system system 2010-08-10 13:10 57 -> /dev/ashmem
lrwx------ system system 2010-08-10 13:10 58 -> /dev/ashmem
lrwx------ system system 2010-08-10 13:10 59 -> /dev/pmem
lr-x------ system system 2010-08-10 13:10 60 -> /system/app/Setting
sProvider.apk
lr-x------ system system 2010-08-10 13:10 61 -> /system/app/Setting
sProvider.apk
lr-x------ system system 2010-08-10 13:10 62 -> /system/app/Setting
sProvider.apk
lrwx------ system system 2010-08-10 13:10 63 -> /data/data/com.andr
oid.providers.settings/databases/settings.db
lr-x------ system system 2010-08-10 13:10 64 -> /system/app/Checkin
Provider.apk
lr-x------ system system 2010-08-10 13:10 65 -> /system/app/Checkin
Provider.apk
lr-x------ system system 2010-08-10 13:10 66 -> /system/app/Checkin
Provider.apk
lrwx------ system system 2010-08-10 13:10 67 -> socket:[1090]
lrwx------ system system 2010-08-10 13:10 68 -> /dev/ashmem
lrwx------ system system 2010-08-10 13:10 69 -> /dev/alarm
lrwx------ system system 2010-08-10 13:10 70 -> /dev/ashmem
lrwx------ system system 2010-08-10 13:10 71 -> /sys/power/wake_loc
k
lrwx------ system system 2010-08-10 13:10 72 -> /sys/power/wake_unl
ock
lrwx------ system system 2010-08-10 13:10 73 -> /sys/power/state
lr-x------ system system 2010-08-10 13:10 74 -> inotify
lrwx------ system system 2010-08-10 13:10 75 -> /dev/ashmem
lrwx------ system system 2010-08-10 13:10 76 -> /dev/input/event9
lrwx------ system system 2010-08-10 13:10 77 -> /dev/input/event8
lrwx------ system system 2010-08-10 13:10 78 -> /dev/input/event7
lrwx------ system system 2010-08-10 13:10 79 -> /dev/input/event6
lrwx------ system system 2010-08-10 13:10 80 -> socket:[1133]
lrwx------ system system 2010-08-10 13:10 81 -> /dev/input/event5
lrwx------ system system 2010-08-10 13:10 82 -> /dev/input/event4
lrwx------ system system 2010-08-10 13:10 83 -> /dev/input/event3
lrwx------ system system 2010-08-10 13:10 84 -> /dev/input/event2
lrwx------ system system 2010-08-10 13:10 85 -> /dev/input/event1
lrwx------ system system 2010-08-10 13:10 86 -> /dev/input/event0
lrwx------ system system 2010-08-10 13:10 87 -> /dev/ashmem
lrwx------ system system 2010-08-10 13:10 88 -> /dev/ashmem
lrwx------ system system 2010-08-10 13:10 89 -> /dev/ashmem
lrwx------ system system 2010-08-10 13:10 90 -> /dev/ashmem
lrwx------ system system 2010-08-10 13:10 91 -> /dev/ashmem
lrwx------ system system 2010-08-10 13:10 92 -> /dev/ashmem
lrwx------ system system 2010-08-10 13:10 93 -> /dev/ashmem
lrwx------ system system 2010-08-10 13:10 94 -> /dev/pmem
lrwx------ system system 2010-08-10 13:10 95 -> /dev/ashmem
lr-x------ system system 2010-08-10 13:10 96 -> /system/app/HtcLock
Screen.apk
lr-x------ system system 2010-08-10 13:10 97 -> /system/app/HtcLock
Screen.apk
lr-x------ system system 2010-08-10 13:10 98 -> /system/app/HtcLock
Screen.apk
lrwx------ system system 2010-08-10 13:10 99 -> /dev/ashmem
lr-x------ system system 2010-08-10 13:10 100 -> /dev/cm3602
lr-x------ system system 2010-08-10 13:10 101 -> /dev/lightsensor
lrwx------ system system 2010-08-10 13:10 102 -> socket:[1285]
lrwx------ system system 2010-08-10 13:10 103 -> /dev/ashmem
lrwx------ system system 2010-08-10 13:10 104 -> /dev/ashmem
lr-x------ system system 2010-08-10 13:10 105 -> /sys/power/wait_fo
r_fb_wake
lrwx------ system system 2010-08-10 13:10 106 -> /dev/ashmem
lrwx------ system system 2010-08-10 13:10 107 -> /dev/ashmem
lrwx------ system system 2010-08-10 13:10 108 -> /dev/ashmem
lrwx------ system system 2010-08-10 13:10 109 -> /dev/ashmem
lrwx------ system system 2010-08-10 13:10 110 -> /dev/ashmem
lrwx------ system system 2010-08-10 13:10 111 -> /dev/ashmem
lrwx------ system system 2010-08-10 13:10 112 -> /dev/ashmem
lrwx------ system system 2010-08-10 13:10 113 -> /dev/pmem
lrwx------ system system 2010-08-10 13:10 114 -> /dev/ashmem
lrwx------ system system 2010-08-10 13:10 115 -> /dev/pmem
lrwx------ system system 2010-08-10 13:10 116 -> /dev/pmem
lr-x------ system system 2010-08-10 13:10 117 -> /system/fonts/Droi
dSans-Bold.ttf
lrwx------ system system 2010-08-10 13:10 118 -> /dev/ashmem
lrwx------ system system 2010-08-10 13:10 119 -> /dev/ashmem
lrwx------ system system 2010-08-10 13:10 120 -> /dev/ashmem
lrwx------ system system 2010-08-10 13:10 121 -> /dev/ashmem
lrwx------ system system 2010-08-10 13:10 122 -> /dev/ashmem
lrwx------ system system 2010-08-10 13:10 123 -> /dev/pmem
lrwx------ system system 2010-08-10 13:10 124 -> /dev/pmem
lrwx------ system system 2010-08-10 13:12 125 -> /dev/pmem
lrwx------ system system 2010-08-10 13:10 128 -> /dev/ashmem
lrwx------ system system 2010-08-10 13:10 130 -> /dev/ashmem
lrwx------ system system 2010-08-10 13:10 132 -> /dev/ashmem
lr-x------ system system 2010-08-10 13:10 133 -> /system/app/Networ
kLocation.apk
lr-x------ system system 2010-08-10 13:10 135 -> /system/app/Networ
kLocation.apk
lr-x------ system system 2010-08-10 13:10 136 -> /system/app/Networ
kLocation.apk
lrwx------ system system 2010-08-10 13:10 137 -> /dev/ashmem
lrwx------ system system 2010-08-10 13:10 139 -> /dev/ashmem
lr-x------ system system 2010-08-10 13:10 140 -> /system/app/PCSCII
.apk
lrwx------ system system 2010-08-10 13:10 144 -> /dev/ashmem
Click to expand...
Click to collapse
Your search is under process 104. In this case, 104 means inode 104 (that is an entry in a file system table). The problem is that any of the (many) processes that are listed could reference this.
Try
/system/xbin/ls -lR /proc | grep 104
and or
/system/xbin/ls -lR /proc | grep socket
I saw a bunch of socket inode references to 104x, but not 104.
opcode1300 said:
http://androidspin.com/2010/08/10/first-android-sms-trojan-released-into-the-wild/
maybe..
Click to expand...
Click to collapse
I didn't install any media players.
Starfire-1 said:
Your search is under process 104. In this case, 104 means inode 104 (that is an entry in a file system table). The problem is that any of the (many) processes that are listed could reference this.
Try
/system/xbin/ls -lR /proc | grep 104
and or
/system/xbin/ls -lR /proc | grep socket
I saw a bunch of socket inode references to 104x, but not 104.
Click to expand...
Click to collapse
ls -l -R | grep 104
dr-xr-xr-x system system 2010-08-10 11:35 104
lrwx------ system system 2010-08-10 13:37 104 -> /dev/ashmem
-r-------- system system 0 2010-08-10 13:37 104
lrwx------ system system 2010-08-10 13:37 104 -> /dev/ashmem
-r-------- system system 0 2010-08-10 13:37 104
lrwx------ system system 2010-08-10 13:37 104 -> /dev/ashmem
-r-------- system system 0 2010-08-10 13:37 104
lrwx------ system system 2010-08-10 13:37 104 -> /dev/ashmem
-r-------- system system 0 2010-08-10 13:37 104
lrwx------ system system 2010-08-10 13:37 104 -> /dev/ashmem
-r-------- system system 0 2010-08-10 13:37 104
lrwx------ system system 2010-08-10 13:37 104 -> /dev/ashmem
-r-------- system system 0 2010-08-10 13:37 104
./98/task/104:
./98/task/104/fd:
lrwx------ system system 2010-08-10 13:37 104 -> /dev/ashmem
./98/task/104/fdinfo:
-r-------- system system 0 2010-08-10 13:37 104
lrwx------ system system 2010-08-10 13:37 104 -> /dev/ashmem
-r-------- system system 0 2010-08-10 13:37 104
lrwx------ system system 2010-08-10 13:37 104 -> /dev/ashmem
-r-------- system system 0 2010-08-10 13:37 104
lrwx------ system system 2010-08-10 13:37 104 -> /dev/ashmem
-r-------- system system 0 2010-08-10 13:37 104
lrwx------ system system 2010-08-10 13:37 104 -> /dev/ashmem
-r-------- system system 0 2010-08-10 13:37 104
lrwx------ system system 2010-08-10 13:37 104 -> /dev/ashmem
-r-------- system system 0 2010-08-10 13:37 104
lrwx------ system system 2010-08-10 13:37 104 -> /dev/ashmem
-r-------- system system 0 2010-08-10 13:37 104
lrwx------ system system 2010-08-10 13:37 104 -> /dev/ashmem
-r-------- system system 0 2010-08-10 13:37 104
lrwx------ system system 2010-08-10 13:37 104 -> /dev/ashmem
-r-------- system system 0 2010-08-10 13:37 104
lrwx------ system system 2010-08-10 13:37 104 -> /dev/ashmem
-r-------- system system 0 2010-08-10 13:37 104
lrwx------ system system 2010-08-10 13:37 104 -> /dev/ashmem
-r-------- system system 0 2010-08-10 13:37 104
lrwx------ system system 2010-08-10 13:37 104 -> /dev/ashmem
-r-------- system system 0 2010-08-10 13:37 104
lrwx------ system system 2010-08-10 13:37 104 -> /dev/ashmem
-r-------- system system 0 2010-08-10 13:37 104
lrwx------ system system 2010-08-10 13:37 104 -> /dev/ashmem
-r-------- system system 0 2010-08-10 13:37 104
lrwx------ system system 2010-08-10 13:37 104 -> /dev/ashmem
-r-------- system system 0 2010-08-10 13:37 104
lrwx------ system system 2010-08-10 13:37 104 -> /dev/ashmem
-r-------- system system 0 2010-08-10 13:37 104
lrwx------ system system 2010-08-10 13:37 104 -> /dev/ashmem
-r-------- system system 0 2010-08-10 13:37 104
lrwx------ system system 2010-08-10 13:37 104 -> /dev/ashmem
-r-------- system system 0 2010-08-10 13:37 104
lrwx------ system system 2010-08-10 13:37 104 -> /dev/ashmem
-r-------- system system 0 2010-08-10 13:37 104
lrwx------ system system 2010-08-10 13:37 104 -> /dev/ashmem
-r-------- system system 0 2010-08-10 13:37 104
lrwx------ system system 2010-08-10 13:37 104 -> /dev/ashmem
-r-------- system system 0 2010-08-10 13:37 104
lrwx------ system system 2010-08-10 13:37 104 -> /dev/ashmem
-r-------- system system 0 2010-08-10 13:37 104
lrwx------ system system 2010-08-10 13:37 104 -> /dev/ashmem
-r-------- system system 0 2010-08-10 13:37 104
lrwx------ system system 2010-08-10 13:37 104 -> /dev/ashmem
-r-------- system system 0 2010-08-10 13:37 104
lrwx------ system system 2010-08-10 13:37 104 -> /dev/ashmem
-r-------- system system 0 2010-08-10 13:37 104
lrwx------ system system 2010-08-10 13:37 104 -> /dev/ashmem
-r-------- system system 0 2010-08-10 13:37 104
lrwx------ system system 2010-08-10 13:37 104 -> /dev/ashmem
-r-------- system system 0 2010-08-10 13:37 104
lrwx------ system system 2010-08-10 13:37 104 -> /dev/ashmem
-r-------- system system 0 2010-08-10 13:37 104
lrwx------ system system 2010-08-10 13:37 104 -> /dev/ashmem
-r-------- system system 0 2010-08-10 13:37 104
lrwx------ system system 2010-08-10 13:37 104 -> /dev/ashmem
-r-------- system system 0 2010-08-10 13:37 104
lrwx------ system system 2010-08-10 13:37 104 -> /dev/ashmem
-r-------- system system 0 2010-08-10 13:37 104
lrwx------ system system 2010-08-10 13:37 104 -> /dev/ashmem
-r-------- system system 0 2010-08-10 13:37 104
lrwx------ system system 2010-08-10 13:37 104 -> /dev/ashmem
-r-------- system system 0 2010-08-10 13:37 104
lrwx------ system system 2010-08-10 13:37 104 -> /dev/ashmem
-r-------- system system 0 2010-08-10 13:37 104
lrwx------ system system 2010-08-10 13:37 104 -> /dev/ashmem
-r-------- system system 0 2010-08-10 13:37 104
lrwx------ system system 2010-08-10 13:37 104 -> /dev/ashmem
-r-------- system system 0 2010-08-10 13:37 104
lrwx------ system system 2010-08-10 13:37 104 -> /dev/ashmem
-r-------- system system 0 2010-08-10 13:37 104
lrwx------ system system 2010-08-10 13:37 104 -> /dev/ashmem
-r-------- system system 0 2010-08-10 13:37 104
lrwx------ system system 2010-08-10 13:37 104 -> /dev/ashmem
-r-------- system system 0 2010-08-10 13:37 104
lrwx------ system system 2010-08-10 13:37 104 -> /dev/ashmem
-r-------- system system 0 2010-08-10 13:37 104
lrwx------ system system 2010-08-10 13:37 104 -> /dev/ashmem
-r-------- system system 0 2010-08-10 13:37 104
lrwx------ system system 2010-08-10 13:37 104 -> /dev/ashmem
-r-------- system system 0 2010-08-10 13:37 104
lrwx------ system system 2010-08-10 13:37 104 -> /dev/ashmem
-r-------- system system 0 2010-08-10 13:37 104
lrwx------ system system 2010-08-10 13:37 104 -> /dev/ashmem
-r-------- system system 0 2010-08-10 13:37 104
lrwx------ system system 2010-08-10 13:37 104 -> /dev/ashmem
-r-------- system system 0 2010-08-10 13:37 104
lrwx------ system system 2010-08-10 13:37 104 -> /dev/ashmem
-r-------- system system 0 2010-08-10 13:37 104
lrwx------ system system 2010-08-10 13:37 104 -> /dev/ashmem
-r-------- system system 0 2010-08-10 13:37 104
lrwx------ system system 2010-08-10 13:37 104 -> /dev/ashmem
-r-------- system system 0 2010-08-10 13:37 104
lrwx------ system system 2010-08-10 13:37 104 -> /dev/ashmem
-r-------- system system 0 2010-08-10 13:37 104
lrwx------ system system 2010-08-10 13:37 104 -> /dev/ashmem
-r-------- system system 0 2010-08-10 13:37 104
lrwx------ system system 2010-08-10 13:37 104 -> /dev/ashmem
-r-------- system system 0 2010-08-10 13:37 104
lrwx------ system system 2010-08-10 13:37 104 -> /dev/ashmem
-r-------- system system 0 2010-08-10 13:37 104
lrwx------ system system 2010-08-10 13:37 104 -> /dev/ashmem
-r-------- system system 0 2010-08-10 13:37 104
lrwx------ system system 2010-08-10 13:37 104 -> /dev/ashmem
-r-------- system system 0 2010-08-10 13:37 104
lrwx------ system system 2010-08-10 13:37 104 -> /dev/ashmem
-r-------- system system 0 2010-08-10 13:37 104
lrwx------ system system 2010-08-10 13:37 104 -> /dev/ashmem
-r-------- system system 0 2010-08-10 13:37 104
lrwx------ system system 2010-08-10 13:37 104 -> /dev/ashmem
-r-------- system system 0 2010-08-10 13:37 104
lrwx------ system system 2010-08-10 13:37 104 -> /dev/ashmem
-r-------- system system 0 2010-08-10 13:37 104
lrwx------ system system 2010-08-10 13:37 104 -> /dev/ashmem
-r-------- system system 0 2010-08-10 13:37 104
lr-x------ nobody nobody 2010-08-10 13:37 104 -> /data/app/com.vzw.
hss.myverizon-1.apk
-r-------- nobody nobody 0 2010-08-10 13:37 104
lr-x------ nobody nobody 2010-08-10 13:37 104 -> /data/app/com.vzw.
hss.myverizon-1.apk
-r-------- nobody nobody 0 2010-08-10 13:37 104
lr-x------ nobody nobody 2010-08-10 13:37 104 -> /data/app/com.vzw.
hss.myverizon-1.apk
-r-------- nobody nobody 0 2010-08-10 13:37 104
lr-x------ nobody nobody 2010-08-10 13:37 104 -> /data/app/com.vzw.
hss.myverizon-1.apk
-r-------- nobody nobody 0 2010-08-10 13:37 104
lr-x------ nobody nobody 2010-08-10 13:37 104 -> /data/app/com.vzw.
hss.myverizon-1.apk
-r-------- nobody nobody 0 2010-08-10 13:37 104
lr-x------ nobody nobody 2010-08-10 13:37 104 -> /data/app/com.vzw.
hss.myverizon-1.apk
-r-------- nobody nobody 0 2010-08-10 13:37 104
lr-x------ nobody nobody 2010-08-10 13:37 104 -> /data/app/com.vzw.
hss.myverizon-1.apk
-r-------- nobody nobody 0 2010-08-10 13:37 104
lr-x------ nobody nobody 2010-08-10 13:37 104 -> /data/app/com.vzw.
hss.myverizon-1.apk
-r-------- nobody nobody 0 2010-08-10 13:37 104
lr-x------ nobody nobody 2010-08-10 13:37 104 -> /data/app/com.vzw.
hss.myverizon-1.apk
-r-------- nobody nobody 0 2010-08-10 13:37 104
lr-x------ nobody nobody 2010-08-10 13:37 104 -> /data/app/com.vzw.
hss.myverizon-1.apk
-r-------- nobody nobody 0 2010-08-10 13:37 104
lr-x------ nobody nobody 2010-08-10 13:37 104 -> /data/app/com.vzw.
hss.myverizon-1.apk
-r-------- nobody nobody 0 2010-08-10 13:37 104
lr-x------ nobody nobody 2010-08-10 13:37 104 -> /data/app/com.vzw.
hss.myverizon-1.apk
-r-------- nobody nobody 0 2010-08-10 13:37 104
lr-x------ nobody nobody 2010-08-10 13:37 104 -> /data/app/com.vzw.
hss.myverizon-1.apk
-r-------- nobody nobody 0 2010-08-10 13:37 104
lr-x------ nobody nobody 2010-08-10 13:37 104 -> /data/app/com.vzw.
hss.myverizon-1.apk
-r-------- nobody nobody 0 2010-08-10 13:37 104
lr-x------ nobody nobody 2010-08-10 13:37 104 -> /data/app/com.vzw.
hss.myverizon-1.apk
-r-------- nobody nobody 0 2010-08-10 13:37 104
lr-x------ nobody nobody 2010-08-10 13:37 104 -> /data/app/com.vzw.
hss.myverizon-1.apk
-r-------- nobody nobody 0 2010-08-10 13:37 104
#
Tried:
# ls -l -R | grep socket:[104]
ls -l -R | grep socket:[104]
No results.
# find -inum 104
find -inum 104
./sys/devices/platform/msm_serial.0/power/wakeup
#
No idea though why wakeup could use udp port for anything
wow.. this is interesting.. and I think we should thank the OP here for bringing it to light.. It raises a serious question.. since we are all blindly downloading custom ROMs made by people we do not know (in the real life)... how safe are these ROMs in terms of invading our privacy?
Jeez.. someone could easily roll a trojan along with a custom ROM and open up a port to squeeze out TONS of information.. I mean.. lots of people use apps on their android phone for banking etc.. not to mention our gmail user account and password.
How do we know all of this is safe and is not being siphoned off by the creators of these ROMs?
kriskmk said:
wow.. this is interesting.. and I think we should thank the OP here for bringing it to light.. It raises a serious question.. since we are all blindly downloading custom ROMs made by people we do not know (in the real life)... how safe are these ROMs in terms of invading our privacy?
Jeez.. someone could easily roll a trojan along with a custom ROM and open up a port to squeeze out TONS of information.. I mean.. lots of people use apps on their android phone for banking etc.. not to mention our gmail user account and password.
How do we know all of this is safe and is not being siphoned off by the creators of these ROMs?
Click to expand...
Click to collapse
Crud, you are on to me. I guess I will head for a non-extradition country once I am done siphoning the bank accounts of my rom users.
adrynalyne said:
Crud, you are on to me. I guess I will head for a non-extradition country once I am done siphoning the bank accounts of my rom users.
Click to expand...
Click to collapse
It's cool, I love your work. You can keep my 3 dollars.
figasse said:
# find -inum 104
find -inum 104
./sys/devices/platform/msm_serial.0/power/wakeup
#
No idea though why wakeup could use udp port for anything
Click to expand...
Click to collapse
Starfire-1 said:
(for me it was 104)
Click to expand...
Click to collapse
Was it 104 for you?
Asterdroid said:
It's cool, I love your work. You can keep my 3 dollars.
Click to expand...
Click to collapse
Awesome!
adrynalyne said:
Crud, you are on to me. I guess I will head for a non-extradition country once I am done siphoning the bank accounts of my rom users.
Click to expand...
Click to collapse
lol, that made me giggle
Related
I used the Vivid Toolkit for Noobs and unlocked the bootloader, flashed the recovery to CWM, flashed the kernel using the .IMG kernel file in Virtuous Inquisition v4.0.2.1, rooted, copied Virtuous Inquisition over to the phone, went to recovery, and...
wipe data/factory reset
wipe cache partition
install zip from sdcard
Virtuous Inquisition installed and I am using it now. However, if I go to SETTINGS > STORAGE something happens to where the phone goes back to the Home Screen and displays...
"Unfortunately, Settings has stopped."
I can press OK to close that message, but something isn't right.
If I enable USB Storage and look on my computer, I only have 8.82 GBs of storage? I realize some is locked by Android, but I would think I would be allowed more than 8.82 GBs.
I would like to repartition then reformat the phone and reinstall Virtuous Inquisition v4.0.2.1. What is the best and easiest way for a noob to do this?
Yeah something isn't right...
d:\Root\Data>adb shell
~ # parted /dev/block/mmcblk0
parted /dev/block/mmcblk0
GNU Parted 1.8.8.1.179-aef3
Using /dev/block/mmcblk0
Welcome to GNU Parted! Type 'help' to view a list of commands.
(parted) print
print
print
Error: Can't have overlapping partitions.
(parted)
(parted) quit
quit
quit
~ # fdisk -l /dev/block/mmcblk0
fdisk -l /dev/block/mmcblk0
Warning: deleting partitions after 60
Disk /dev/block/mmcblk0: 15.7 GB, 15758000128 bytes
1 heads, 16 sectors/track, 1923584 cylinders
Units = cylinders of 16 * 512 = 8192 bytes
Device Boot Start End Blocks Id System
/dev/block/mmcblk0p1 * 1 17 128 4d Unknown
Partition 1 does not end on cylinder boundary
/dev/block/mmcblk0p2 17 49 256 51 Unknown
Partition 2 does not end on cylinder boundary
/dev/block/mmcblk0p3 49 4094 32367 5d Unknown
Partition 3 does not end on cylinder boundary
/dev/block/mmcblk0p4 4094 1923584 15355920 5 Extended
Partition 4 does not end on cylinder boundary
/dev/block/mmcblk0p5 4095 4096 16 5a Unknown
/dev/block/mmcblk0p6 4097 4129 256 73 Unknown
/dev/block/mmcblk0p7 4129 6684 20442+ 5b Unknown
/dev/block/mmcblk0p8 6684 6716 256 5c Unknown
/dev/block/mmcblk0p9 6716 6844 1024 45 Unknown
/dev/block/mmcblk0p10 6844 6876 256 47 Unknown
/dev/block/mmcblk0p11 6876 7132 2048 46 Unknown
/dev/block/mmcblk0p12 7132 7260 1024 4c Unknown
/dev/block/mmcblk0p13 7260 7264 32 39 Unknown
/dev/block/mmcblk0p14 7264 8032 6144 34 Unknown
/dev/block/mmcblk0p15 8032 8160 1024 36 Unknown
/dev/block/mmcblk0p16 8161 8192 256 76 Unknown
/dev/block/mmcblk0p17 8193 13313 40960 77 Unknown
/dev/block/mmcblk0p18 13313 18433 40960 77 Unknown
/dev/block/mmcblk0p19 18433 19457 8191 74 Unknown
/dev/block/mmcblk0p20 19457 20480 8190+ 74 Unknown
/dev/block/mmcblk0p21 20481 24576 32768 7a Unknown
/dev/block/mmcblk0p22 24577 26625 16384 48 Unknown
/dev/block/mmcblk0p23 26625 28672 16383 71 Unknown
/dev/block/mmcblk0p24 28673 30720 16381+ 76 Unknown
/dev/block/mmcblk0p25 30720 31232 4096 4a Unknown
/dev/block/mmcblk0p26 31232 31744 4096 4b Unknown
/dev/block/mmcblk0p27 31744 32256 4096 59 Unknown
/dev/block/mmcblk0p28 32257 32768 4096 5a Unknown
/dev/block/mmcblk0p29 32769 163840 1048575+ 83 Linux
/dev/block/mmcblk0p30 163841 167902 32489+ 19 Unknown
/dev/block/mmcblk0p31 167902 167902 4 88 Unknown
/dev/block/mmcblk0p32 167902 167934 256 23 Unknown
/dev/block/mmcblk0p33 167934 167936 16 89 Unknown
/dev/block/mmcblk0p34 167937 692224 4194303+ 83 Linux
/dev/block/mmcblk0p35 692225 729088 294911+ 83 Linux
/dev/block/mmcblk0p36 729089 1887744 9269248 c Win95 FAT32 (LB
A)
/dev/block/mmcblk0p37 1887745 1887753 64 90 Unknown
/dev/block/mmcblk0p38 4095 4096 16 5a Unknown
/dev/block/mmcblk0p39 4097 4129 256 73 Unknown
/dev/block/mmcblk0p40 4129 6684 20442+ 5b Unknown
/dev/block/mmcblk0p41 6684 6716 256 5c Unknown
/dev/block/mmcblk0p42 6716 6844 1024 45 Unknown
/dev/block/mmcblk0p43 6844 6876 256 47 Unknown
/dev/block/mmcblk0p44 6876 7132 2048 46 Unknown
/dev/block/mmcblk0p45 7132 7260 1024 4c Unknown
/dev/block/mmcblk0p46 7260 7264 32 39 Unknown
/dev/block/mmcblk0p47 7264 8032 6144 34 Unknown
/dev/block/mmcblk0p48 8032 8160 1024 36 Unknown
/dev/block/mmcblk0p49 8161 8192 256 76 Unknown
/dev/block/mmcblk0p50 8193 13313 40960 77 Unknown
/dev/block/mmcblk0p51 13313 18433 40960 77 Unknown
/dev/block/mmcblk0p52 18433 19457 8191 74 Unknown
/dev/block/mmcblk0p53 19457 20480 8190+ 74 Unknown
/dev/block/mmcblk0p54 20481 24576 32768 7a Unknown
/dev/block/mmcblk0p55 24577 26625 16384 48 Unknown
/dev/block/mmcblk0p56 26625 28672 16383 71 Unknown
/dev/block/mmcblk0p57 28673 30720 16381+ 76 Unknown
/dev/block/mmcblk0p58 30720 31232 4096 4a Unknown
/dev/block/mmcblk0p59 31232 31744 4096 4b Unknown
/dev/block/mmcblk0p60 31744 32256 4096 59 Unknown
Partition table entries are not in disk order
~ #
Hello
Not sure if this is the right place, but I don't think development is the right thread either as I simply need a one time tester and there is already a dev thread for the tool in Optimus Black Forums.
I have developed a tool that extracts LG's bin firmware. I extended it to extract tot files as well. As some of you might know the tot files splits some partitions up into multiple files. I already managed to extract the tot file into their various part, but I have only recently added the ability to merge the parts to it's partition
I don't have enough bandwidth to download one of your firmware files to test it so can someone please test the tool.
Heres the dev thread : link
Heres the git : link
You'll have to compile it with gcc/mingw. The tools name must be BinExtractor(.exe) or it won't remove the first argument (usually the tool path and then it will keep on showing the usage no matter what)
Run it with
Code:
BinExtractor -daph Path/To/Tot/File/firmware.tot
and see if it displays the header info. If that succeeds please test the extraction
Code:
BinExtractor -extract Path/To/Tot/File/firmware.tot
It should prompt you that it detected data blocks with identical names and ask you if you want to merge them. And you want to merge them . After it extracted the files can you please check that the various partitions that it extracted are correct.
To check the system partition mount or extract the system partition in Linux and in Windows use a tool like ext2read to check it.
If it fails with an error please post the results from -daph (and -extract if it happened there) and the first meg of the tot file you used.
If the partitions aren't extracted properly (or merged properly) and -daph succeeded please post just the output from -daph and in what way the output is faulty.
Thanks in advance.
Wow it moved out of page 1 already.
Bump.
It was ignored because the Nexus 4 doesn't use LG .bin files, it uses standard .img files.
Rusty! said:
It was ignored because the Nexus 4 doesn't use LG .bin files, it uses standard .img files.
Click to expand...
Click to collapse
Thanks for responding, but according to this: [Stock] Stock ROMs Collection US/CA/EU/AU
These files are in TOT format
Click to expand...
Click to collapse
And theres a DL link that I presume contains a tot file
LGE960AT-00-V10c-NXS-XX-OCT-25-2012-JVP15Q-USER+0
Click to expand...
Click to collapse
Can you please explain since the info I have atm is a bit contradictory.
Thanks for this xonar. Much appreciated.
Would anyone be able to compile a Windows binary for me and upload it please? Thanks.
Sent from my Nexus 4 using Tapatalk 2
efrant said:
Thanks for this xonar. Much appreciated.
Would anyone be able to compile a Windows binary for me and upload it please? Thanks.
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
I just compiled it with mingw, but it's not behaving as it's Linux counterpart.
If j is 1024 why isn't the output file 512kB ?!? (Tested with P970 bin)
Code:
for(j = 0; j < tmp.pent_arr[i].file_size; j++)
{
/*DO 512 BLOCK*/
fread(buff, sizeof(char), 512, f);
fwrite(buff, sizeof(char), 512, out);
}
fclose(out);
EDIT: Had a facepalm moment
Windows needs to specify reading and writing in binary. I'll give you exe in a moment.
EDIT2: I attached a zip with the exe inside.
To get it working in Windows I changed read access to binary everywhere theres a fopen and I initialized some thing to 0 as Windows unlike Linux doesn't start you of with a nice clean slate.
I'll push changes to git tomorrow morning to make it work on Windows aswel and from now on I'll actually test the windows exe on windows and not through wine.
Hope it works. I'm going to bed now.
xonar_ said:
I just compiled it with mingw, but it's not behaving as it's Linux counterpart.
If j is 1024 why isn't the output file 512kB ?!? (Tested with P970 bin)
Code:
for(j = 0; j < tmp.pent_arr[i].file_size; j++)
{
/*DO 512 BLOCK*/
fread(buff, sizeof(char), 512, f);
fwrite(buff, sizeof(char), 512, out);
}
fclose(out);
EDIT: Had a facepalm moment
Windows needs to specify reading and writing in binary. I'll give you exe in a moment.
EDIT2: I attached a zip with the exe inside.
To get it working in Windows I changed read access to binary everywhere theres a fopen and I initialized some thing to 0 as Windows unlike Linux doesn't start you of with a nice clean slate.
I'll push changes to git tomorrow morning to make it work on Windows aswel and from now on I'll actually test the windows exe on windows and not through wine.
Hope it works. I'm going to bed now.
Click to expand...
Click to collapse
Thanks so much. I'll try to give it a shot tomorrow. If it doesn't work, I guess I could always use cygwin.
Sent from my Nexus 4 using Tapatalk 2
Doesn't seem to work on Bell Optimus G:
Code:
BinExtractor.exe -extract "LGE973AT-00-V10f-BELL-CA-OCT-24-2012+0.tot"
Reading AP Header...
Unknown Magic Number at 0x8 : AF 33 BF DE
Writing Files...
Finished
Running the info command:
GPT HEADER
----------
Signature 45 46 49 20 50 41 52 54
Revision 65536
Header Size 92
CRC32 of Header B2 64 10 F5
Current Header LBA 1
Backup Header LBA 61071359
First Usable LBA 34
Last Usable LBA 61071326
Disk GUID 32 1B 10 98 E2 BB F2 4B A0 6E 2B B3 3D 00 0C 20
Start of Partition Entries 2
Number of Partition Entries 36
Size of Partition Entries 128
CRC32 of Partition Array 71 79 32 B7
PARTITION ENTRIES
-----------------
PARTITION ENTRY
---------------
Partition Type GUID A2 A0 D0 EB E5 B9 33 44 87 C0 68 B6 B7 26 99 C7
Unique Partition GUID 7B 6F 3E CF 28 B7 86 F3 6A AE 46 69 B1 BC 9A 08
First LBA 16384
Last LBA 147455
Attributes 8
Partition Name modem
PARTITION ENTRY
---------------
Partition Type GUID 2C BA A0 DE DD CB 05 48 B4 F9 F4 28 25 1C 3E 98
Unique Partition GUID BC D0 5B BC 05 A5 44 30 8E 88 59 5C 87 19 A1 08
First LBA 147456
Last LBA 148479
Attributes 0
Partition Name sbl1
PARTITION ENTRY
---------------
....
zivan56 said:
Doesn't seem to work on Bell Optimus G:
Code:
Unknown Magic Number at 0x8 : AF 33 BF DE
Click to expand...
Click to collapse
The tool doesn't support Bell OG yet. I made a guess at what the format could be but I can't say for certain that it will work. I'll push changes in a moment.
Someone tested it on another OG firmware, but it fails to mount the image with:
Code:
mount: wrong fs type, bad option, bad superblock on /dev/loop0,
missing codepage or helper program, or other error
In some cases useful info is found in syslog - try
dmesg | tail or so
Code:
EXT4-fs (loop0): bad geometry: block count 389120 exceeds size of device (360576 blocks)
Click to expand...
Click to collapse
Can anyone give me the output from -dgpt with at&t OG or sprint OG?
or the first meg of the tot file of Nexus 4 or Bell OG along with -dgpt output?
EDIT: If possible use pastebin to display dgpt output as it might be fairly long.
I known what the problem is. Great thanks to SnowLeopardJB for testing and correspondence
The file that was being created doesn't have 'space' up until the end of the partitions. (It was left out since thats where it stops in the file) but on the actual disk still has 'space' after the last bit of data.
So it can be fixed with
Code:
#VAL is the value that is supposedly outside the device from the err msg
VAL=389120
#This will say already that size, but the file itself will change size
resize2fs system.img $VAL
#Not sure if this last step is then necessary
fsck.ext4 -f system.img
#Now you can mount is as any other partition :laugh:
I'll make the program add the 'space' and see if it produces a immediately mountable file.
I also totally changed the way it handles 44 DD 55 AA files for future flexibility and it's a step closer to being able to make it use predefined files as formats.
The latest version in git seems to extract the Bell Optimus G firmware properly now. I tried mounting the resulting radio image section and it worked fine, so I assume it knows the proper partition boundaries now.
Btw, I would recommend posting some instructions how to compile it. Not everyone is savvy enough to know how to use gcc.
Likewise, your program is hardcoded to look for its name when looking for parameters. Since there was no makefile it defaulted to a.out, which, the way it is coded, would never accept any parameters unless renamed to LGBinExtractor.
zivan56 said:
The latest version in git seems to extract the Bell Optimus G firmware properly now. I tried mounting the resulting radio image section and it worked fine, so I assume it knows the proper partition boundaries now.
Click to expand...
Click to collapse
Only merged partitions was affected by 'space' bug, plain extraction should have been correct for Bell OB after bb697c27e5. I haven't commited 'space' fix yet.
In retrospect using fseek to create 'space' between image parts might not have been such a good idea either and might also be causing problems.
zivan56 said:
Btw, I would recommend posting some instructions how to compile it. Not everyone is savvy enough to know how to use gcc.
Click to expand...
Click to collapse
Adding a makefile is on my todo list.
zivan56 said:
Likewise, your program is hardcoded to look for its name when looking for parameters. Since there was no makefile it defaulted to a.out, which, the way it is coded, would never accept any parameters unless renamed to LGBinExtractor.
Click to expand...
Click to collapse
Yea, not one of my better choices. I changed it to remove the first arg if it doesn't start with '-'.
Okay Merging partitions should work now. I'm waiting for confirmation then I'll ask mod to close the thread.
xonar_ said:
Okay Merging partitions should work now. I'm waiting for confirmation then I'll ask mod to close the thread.
Click to expand...
Click to collapse
Hello i'm try test with LG Optimus tag working:laugh:
Code:
AP HEADER
----------
Magic Number 44 DD 55 AA
Number of Partitions 32
PARTITION ENTRIES
-----------------
PARTITION ENTRY
------------
Data Block Name MODEM
Data Block ID 1
Size on File 47104
File Offset 0
Size on Disk 65537
Disk Offset 0
PARTITION ENTRY
------------
Data Block Name SBL1
Data Block ID 2
Size on File 1024
File Offset 47104
Size on Disk 2048
Disk Offset 65537
PARTITION ENTRY
------------
Data Block Name SBL2
Data Block ID 3
Size on File 1024
File Offset 48128
Size on Disk 2048
Disk Offset 67585
PARTITION ENTRY
------------
Data Block Name EXT
Data Block ID 4
Size on File 1024
File Offset 49152
Size on Disk 12287
Disk Offset 69633
PARTITION ENTRY
------------
Data Block Name RPM
Data Block ID 5
Size on File 1024
File Offset 50176
Size on Disk 16384
Disk Offset 81920
PARTITION ENTRY
------------
Data Block Name SBL3
Data Block ID 6
Size on File 2048
File Offset 51200
Size on Disk 16384
Disk Offset 98304
PARTITION ENTRY
------------
Data Block Name ABOOT
Data Block ID 7
Size on File 2048
File Offset 53248
Size on Disk 16384
Disk Offset 114688
PARTITION ENTRY
------------
Data Block Name BOOT
Data Block ID 8
Size on File 15360
File Offset 55296
Size on Disk 32768
Disk Offset 131072
PARTITION ENTRY
------------
Data Block Name TZ
Data Block ID 9
Size on File 1024
File Offset 70656
Size on Disk 16384
Disk Offset 163840
PARTITION ENTRY
------------
Data Block Name MODEM_ST1
Data Block ID 10
Size on File 0
File Offset 71680
Size on Disk 16384
Disk Offset 180224
PARTITION ENTRY
------------
Data Block Name MODEM_ST2
Data Block ID 11
Size on File 0
File Offset 71680
Size on Disk 16384
Disk Offset 196608
PARTITION ENTRY
------------
Data Block Name PERSIST
Data Block ID 12
Size on File 16384
File Offset 71680
Size on Disk 16384
Disk Offset 212992
PARTITION ENTRY
------------
Data Block Name RECOVERY
Data Block ID 13
Size on File 17408
File Offset 88064
Size on Disk 32768
Disk Offset 229376
PARTITION ENTRY
------------
Data Block Name MDM
Data Block ID 14
Size on File 57344
File Offset 105472
Size on Disk 65536
Disk Offset 262144
PARTITION ENTRY
------------
Data Block Name M9K_EFS1
Data Block ID 15
Size on File 0
File Offset 162816
Size on Disk 16384
Disk Offset 327680
PARTITION ENTRY
------------
Data Block Name M9K_EFS2
Data Block ID 16
Size on File 0
File Offset 162816
Size on Disk 16384
Disk Offset 344064
PARTITION ENTRY
------------
Data Block Name M9K_EFS3
Data Block ID 17
Size on File 0
File Offset 162816
Size on Disk 16384
Disk Offset 360448
PARTITION ENTRY
------------
Data Block Name FSG
Data Block ID 18
Size on File 0
File Offset 162816
Size on Disk 16384
Disk Offset 376832
PARTITION ENTRY
------------
Data Block Name SSD
Data Block ID 19
Size on File 0
File Offset 162816
Size on Disk 32768
Disk Offset 393216
PARTITION ENTRY
------------
Data Block Name BSP
Data Block ID 20
Size on File 0
File Offset 162816
Size on Disk 16384
Disk Offset 425984
PARTITION ENTRY
------------
Data Block Name BLB
Data Block ID 21
Size on File 0
File Offset 162816
Size on Disk 32768
Disk Offset 442368
PARTITION ENTRY
------------
Data Block Name TOMBSTONES
Data Block ID 22
Size on File 1024
File Offset 162816
Size on Disk 147456
Disk Offset 475136
PARTITION ENTRY
------------
Data Block Name DRM
Data Block ID 23
Size on File 0
File Offset 163840
Size on Disk 16384
Disk Offset 622592
PARTITION ENTRY
------------
Data Block Name FOTA
Data Block ID 24
Size on File 0
File Offset 163840
Size on Disk 49152
Disk Offset 638976
PARTITION ENTRY
------------
Data Block Name MISC
Data Block ID 25
Size on File 0
File Offset 163840
Size on Disk 16384
Disk Offset 688128
PARTITION ENTRY
------------
Data Block Name TZ_BKP
Data Block ID 26
Size on File 0
File Offset 163840
Size on Disk 16384
Disk Offset 704512
PARTITION ENTRY
------------
Data Block Name SYSTEM
Data Block ID 27
Size on File 1720320
File Offset 163840
Size on Disk 1720320
Disk Offset 720896
PARTITION ENTRY
------------
Data Block Name CACHE
Data Block ID 28
Size on File 0
File Offset 1884160
Size on Disk 655360
Disk Offset 2441216
PARTITION ENTRY
------------
Data Block Name WALLPAPER
Data Block ID 29
Size on File 0
File Offset 1884160
Size on Disk 16384
Disk Offset 3096576
PARTITION ENTRY
------------
Data Block Name USERDATA
Data Block ID 30
Size on File 0
File Offset 1884160
Size on Disk 4587520
Disk Offset 3112960
PARTITION ENTRY
------------
Data Block Name MPT
Data Block ID 31
Size on File 0
File Offset 1884160
Size on Disk 32768
Disk Offset 7700480
PARTITION ENTRY
------------
Data Block Name GROW
Data Block ID 32
Size on File 20480
File Offset 1884160
Size on Disk 21000000
Disk Offset 7733248
Code:
Reading AP Header...
Writing Files...
Writing File : 1-MODEM.img -- DONE --
Writing File : 2-SBL1.img -- DONE --
Writing File : 3-SBL2.img -- DONE --
Writing File : 4-EXT.img -- DONE --
Writing File : 5-RPM.img -- DONE --
Writing File : 6-SBL3.img -- DONE --
Writing File : 7-ABOOT.img -- DONE --
Writing File : 8-BOOT.img -- DONE --
Writing File : 9-TZ.img -- DONE --
Writing File : 10-MODEM_ST1.img -- DONE --
Writing File : 11-MODEM_ST2.img -- DONE --
Writing File : 12-PERSIST.img -- DONE --
Writing File : 13-RECOVERY.img -- DONE --
Writing File : 14-MDM.img -- DONE --
Writing File : 15-M9K_EFS1.img -- DONE --
Writing File : 16-M9K_EFS2.img -- DONE --
Writing File : 17-M9K_EFS3.img -- DONE --
Writing File : 18-FSG.img -- DONE --
Writing File : 19-SSD.img -- DONE --
Writing File : 20-BSP.img -- DONE --
Writing File : 21-BLB.img -- DONE --
Writing File : 22-TOMBSTONES.img -- DONE --
Writing File : 23-DRM.img -- DONE --
Writing File : 24-FOTA.img -- DONE --
Writing File : 25-MISC.img -- DONE --
Writing File : 26-TZ_BKP.img -- DONE --
Writing File : 27-SYSTEM.img -- DONE --
Writing File : 28-CACHE.img -- DONE --
Writing File : 29-WALLPAPER.img -- DONE --
Writing File : 30-USERDATA.img -- DONE --
Writing File : 31-MPT.img -- DONE --
Writing File : 32-GROW.img -- DONE --
Finished
PS : @xonar_ If you need any flash file LG pm me i have all files LG
---------- Post added at 01:25 AM ---------- Previous post was at 12:25 AM ----------
LG Optimus LTE2 F160 working
Code:
GPT HEADER
----------
Signature 45 46 49 20 50 41 52 54
Revision 65536
Header Size 92
CRC32 of Header 93 23 A2 52
Current Header LBA 1
Backup Header LBA 30535679
First Usable LBA 34
Last Usable LBA 30535646
Disk GUID 32 1B 10 98 E2 BB F2 4B A0 6E 2B B3 3D 00 0C 20
Start of Partition Entries 2
Number of Partition Entries 32
Size of Partition Entries 128
CRC32 of Partition Array 2A A9 B7 BD
PARTITION ENTRIES
-----------------
PARTITION ENTRY
---------------
Partition Type GUID A2 A0 D0 EB E5 B9 33 44 87 C0 68 B6 B7 26 99 C7
Unique Partition GUID 72 05 1F 0E 0C 89 89 B5 F4 D4 0E 5D 04 65 52 1E
First LBA 16384
Last LBA 147455
Attributes 8
Partition Name modem
PARTITION ENTRY
---------------
Partition Type GUID 2C BA A0 DE DD CB 05 48 B4 F9 F4 28 25 1C 3E 98
Unique Partition GUID 9A 00 DF 9C DE F9 95 65 62 3C 0F 15 D6 1A 75 6B
First LBA 147456
Last LBA 148479
Attributes 0
Partition Name sbl1
PARTITION ENTRY
---------------
Partition Type GUID AD 52 6B 8C 9E 8A 98 43 AD 09 AE 91 6E 53 AE 2D
Unique Partition GUID F1 EC 20 B2 C4 FA 8B FC 06 D2 4F 33 72 B6 0F D2
First LBA 148480
Last LBA 149503
Attributes 0
Partition Name sbl2
PARTITION ENTRY
---------------
Partition Type GUID DF 44 E0 05 F1 92 25 43 B6 9E 37 4A 82 E9 7D 6E
Unique Partition GUID A8 87 F8 53 B8 47 22 FA A9 2B 91 26 94 F6 19 2B
First LBA 149504
Last LBA 151551
Attributes 0
Partition Name sbl3
PARTITION ENTRY
---------------
Partition Type GUID CD FD 0F 40 E0 22 E7 47 9A 23 F1 6E D9 38 23 88
Unique Partition GUID 2A D1 EA 8A 29 76 F5 14 50 CD FA D5 2D 9F 41 26
First LBA 151552
Last LBA 152575
Attributes 0
Partition Name aboot
PARTITION ENTRY
---------------
Partition Type GUID 93 F7 8D 09 12 D7 3D 41 9D 4E 89 D7 11 77 22 28
Unique Partition GUID F7 5A 4B 53 B7 53 FB FF 4C F1 26 3A AD 9D C9 12
First LBA 152576
Last LBA 153599
Attributes 0
Partition Name rpm
PARTITION ENTRY
---------------
Partition Type GUID 86 7F 11 20 85 E9 57 43 B9 EE 37 4B C1 D8 48 7D
Unique Partition GUID 7A C9 D2 E5 B5 2A 04 6C BE 24 C7 AE 35 55 01 B2
First LBA 163840
Last LBA 188415
Attributes 8
Partition Name boot
PARTITION ENTRY
---------------
Partition Type GUID 7F AA 53 A0 B8 40 1C 4B BA 08 2F 68 AC 71 A4 F4
Unique Partition GUID F9 09 61 B9 4F 99 AF 89 FF C3 F3 16 99 B0 E3 A9
First LBA 196608
Last LBA 197631
Attributes 0
Partition Name tz
PARTITION ENTRY
---------------
Partition Type GUID 38 68 4A 00 2A 06 DF 44 81 52 4F 34 0C 05 22 5D
Unique Partition GUID BC 83 9C AC D5 BF F4 36 1C 0F D4 63 6F AD 23 07
First LBA 197632
Last LBA 197633
Attributes 0
Partition Name pad
PARTITION ENTRY
---------------
Partition Type GUID 3E 37 13 20 C4 1A 31 41 B0 F8 91 58 F9 65 4F 4F
Unique Partition GUID 46 F4 88 C2 2C 7A 4A AD 17 28 DD 70 10 8B BD AD
First LBA 197634
Last LBA 203777
Attributes 0
Partition Name modemst1
PARTITION ENTRY
---------------
Partition Type GUID 3E 37 13 20 C4 1A 31 41 B0 F8 91 58 F9 65 4F 4F
Unique Partition GUID 0A E8 2B 7F B8 CF 52 3E C2 7E 52 26 3E 03 B5 35
First LBA 203778
Last LBA 209921
Attributes 0
Partition Name modemst2
PARTITION ENTRY
---------------
Partition Type GUID AF 3D C6 0F 83 84 72 47 8E 79 3D 69 D8 47 7D E4
Unique Partition GUID 85 78 29 24 17 62 3D 36 A4 4B E9 47 10 87 AD 67
First LBA 212992
Last LBA 229375
Attributes 8
Partition Name sns
PARTITION ENTRY
---------------
Partition Type GUID 54 05 D3 6C 5D 5F EF 40 82 FE 10 92 35 9F 92 EE
Unique Partition GUID DC BF D4 C1 2E 63 5D 16 3F 45 88 4F 2A 36 86 3C
First LBA 229376
Last LBA 262143
Attributes 0
Partition Name misc
PARTITION ENTRY
---------------
Partition Type GUID AF 3D C6 0F 83 84 72 47 8E 79 3D 69 D8 47 7D E4
Unique Partition GUID 8E C6 02 A3 3F DC 79 98 12 7F 02 BE 38 F7 D4 6B
First LBA 262144
Last LBA 2359295
Attributes 8
Partition Name system
PARTITION ENTRY
---------------
Partition Type GUID AF 3D C6 0F 83 84 72 47 8E 79 3D 69 D8 47 7D E4
Unique Partition GUID E2 F2 D0 8D 3E D2 D0 90 E9 45 09 EA 7E 8F 2C 97
First LBA 2359296
Last LBA 29589503
Attributes 8
Partition Name userdata
PARTITION ENTRY
---------------
Partition Type GUID AF 3D C6 0F 83 84 72 47 8E 79 3D 69 D8 47 7D E4
Unique Partition GUID F7 2D 03 28 16 E8 78 07 D0 84 1B 08 6F 5B 6D 39
First LBA 29589504
Last LBA 29605887
Attributes 8
Partition Name persist
PARTITION ENTRY
---------------
Partition Type GUID AF 3D C6 0F 83 84 72 47 8E 79 3D 69 D8 47 7D E4
Unique Partition GUID 21 6C AF DC 30 3D D9 D9 3F AE 56 42 4C 0F 66 AC
First LBA 29605888
Last LBA 30146559
Attributes 8
Partition Name cache
PARTITION ENTRY
---------------
Partition Type GUID AF 3D C6 0F 83 84 72 47 8E 79 3D 69 D8 47 7D E4
Unique Partition GUID 26 4F D8 D1 AC 24 CC CA EA 7F E1 F0 E5 6C FD 61
First LBA 30146560
Last LBA 30294015
Attributes 0
Partition Name tombstones
PARTITION ENTRY
---------------
Partition Type GUID 86 7F 11 20 85 E9 57 43 B9 EE 37 4B C1 D8 48 7D
Unique Partition GUID BB 74 76 DD 1D 6B 07 56 23 FB 94 96 7A 52 0A DC
First LBA 30294016
Last LBA 30318591
Attributes 8
Partition Name recovery
PARTITION ENTRY
---------------
Partition Type GUID 3E 37 13 20 C4 1A 31 41 B0 F8 91 58 F9 65 4F 4F
Unique Partition GUID 7C 48 3D 02 F0 90 E3 39 F7 14 BA D1 D9 BD 76 C8
First LBA 30318592
Last LBA 30324735
Attributes 8
Partition Name fsg
PARTITION ENTRY
---------------
Partition Type GUID 42 E7 86 2C 5E 74 DD 4F BF D8 B6 A7 AC 63 87 72
Unique Partition GUID 9B 2F 13 2B 51 11 1E C2 30 66 A0 E7 08 BC BF DF
First LBA 30324736
Last LBA 30324751
Attributes 8
Partition Name ssd
PARTITION ENTRY
---------------
Partition Type GUID AF 3D C6 0F 83 84 72 47 8E 79 3D 69 D8 47 7D E4
Unique Partition GUID 75 44 C3 7D E2 05 C3 88 22 1B 8A 2D D1 D9 E4 FA
First LBA 30326784
Last LBA 30343167
Attributes 0
Partition Name drm
PARTITION ENTRY
---------------
Partition Type GUID AC 9C 14 00 9B ED 01 48 9A E9 6D F9 60 3A 18 27
Unique Partition GUID 55 D9 D2 33 14 1A 58 56 F8 47 15 23 E1 B9 A4 07
First LBA 30343168
Last LBA 30408703
Attributes 0
Partition Name fota
PARTITION ENTRY
---------------
Partition Type GUID AF 3D C6 0F 83 84 72 47 8E 79 3D 69 D8 47 7D E4
Unique Partition GUID 38 9D 3B B9 01 35 EA F7 BA 61 44 35 4F AE 2C 73
First LBA 30408704
Last LBA 30474239
Attributes 0
Partition Name mpt
PARTITION ENTRY
---------------
Partition Type GUID BB 51 9C 73 F9 7A 0A 45 88 49 FF 4F 3D 94 CC AF
Unique Partition GUID EB 58 E9 92 44 82 6E A3 9C 07 F8 60 1D 46 AB 8E
First LBA 30474240
Last LBA 30475263
Attributes 0
Partition Name tzbak
PARTITION ENTRY
---------------
Partition Type GUID 11 84 CC 6A A5 68 18 41 BA B0 07 FA 12 72 B4 9B
Unique Partition GUID 8C 02 6E 7C 87 46 63 0D 71 93 68 7C 2A 4A D8 73
First LBA 30475264
Last LBA 30476287
Attributes 0
Partition Name rpmbak
PARTITION ENTRY
---------------
Partition Type GUID 95 F5 3E 32 7A AF FA 4A 80 60 97 BE 72 84 1B B9
Unique Partition GUID 47 79 8A 0B 52 C4 79 9B 2A 90 81 4E FC A8 E0 77
First LBA 30476288
Last LBA 30477311
Attributes 0
Partition Name encrypt
PARTITION ENTRY
---------------
Partition Type GUID 73 75 D2 A7 3C A5 E7 4C 87 BC 4D 35 12 FF C8 64
Unique Partition GUID 96 9C 90 E9 54 25 10 09 5A B6 CB 7E D3 1E 79 1D
First LBA 30490624
Last LBA 30523391
Attributes 8
Partition Name reserved
PARTITION ENTRY
---------------
Partition Type GUID AF 3D C6 0F 83 84 72 47 8E 79 3D 69 D8 47 7D E4
Unique Partition GUID 88 8D 1A E1 EF BF 80 A7 58 89 13 B3 AF AD 5E A3
First LBA 30523392
Last LBA 30535646
Attributes 0
Partition Name grow
Q:\LG\LG-F160L>
Not work on my G
it forceclose when i try to use -daph
KhmerHacker said:
it forceclose when i try to use -daph
Click to expand...
Click to collapse
What firmware did you try it on?
Succes with your tools
Thanks xonar. with your tools, I successed with Optimus Vu F100L rom: F100L29j_00.kdz. But the tools ext2read you metioned cannot see the ext4 26-SYSTEM.img, but I mount in linux and get the right result as below
mkdir
mount -t ext4 -o loop 26-SYSTEM.img /tmp
thanks very, a question:
after I make change to the img file, how can I repacked the img to tot file? need a change the wdb dll wdh file also?
anyone can give help is wellcome.
flyhigher76 said:
Thanks xonar. with your tools, I successed with Optimus Vu F100L rom: F100L29j_00.kdz. But the tools ext2read you metioned cannot see the ext4 26-SYSTEM.img, but I mount in linux and get the right result as below
mkdir
mount -t ext4 -o loop 26-SYSTEM.img /tmp
Click to expand...
Click to collapse
Not sure why ext2read don't work
,but if it works in Linux it should be correct.
flyhigher76 said:
thanks very, a question:
after I make change to the img file, how can I repacked the img to tot file? need a change the wdb dll wdh file also?
anyone can give help is wellcome.
Click to expand...
Click to collapse
It's possible to recreate the tot file from the extracted partitions,but a mistake can make your phone Hard Bricked. I wouldn't recommend doing that.
change Optimus Vu Languge
xonar_ said:
Not sure why ext2read don't work
,but if it works in Linux it should be correct.
It's possible to recreate the tot file from the extracted partitions,but a mistake can make your phone Hard Bricked. I wouldn't recommend doing that.
Click to expand...
Click to collapse
I like the Optimus Vu very much, fot it's unique size and it's first-class panel display attract me. But unfortunately, it is not in Chinese, also when I make a call I must choose to call local or call Korea. I'm tired of this, so I want to have a custom system for my own. The difficult is that I cannot get control the /system for root fails many times, so I cannot change any apk and jar in /system. I hope I can modify the rom as I have do with galaxy note, and forturely find this thread.
I know tot format file since I own this optimus Vu, so I have no idea about this format. Can you give me some information about this format, like some website?
vmt.
flyhigher76 said:
I know tot format file since I own this optimus Vu, so I have no idea about this format. Can you give me some information about this format, like some website?
vmt.
Click to expand...
Click to collapse
Theres the source code of my tool.
In case anyone need it
Code:
ADF -> /dev/block/mmcblk0p61
APD -> /dev/block/mmcblk0p60
abl -> /dev/block/mmcblk0p27
ablbak -> /dev/block/mmcblk0p28
apdp -> /dev/block/mmcblk0p31
asdf -> /dev/block/mmcblk0p62
asusfw -> /dev/block/mmcblk0p51
bluetooth -> /dev/block/mmcblk0p40
bluetoothbak -> /dev/block/mmcblk0p41
boot -> /dev/block/mmcblk0p12
cache -> /dev/block/mmcblk0p58
cmnlib -> /dev/block/mmcblk0p17
cmnlib64 -> /dev/block/mmcblk0p18
cmnlib64bak -> /dev/block/mmcblk0p20
cmnlibbak -> /dev/block/mmcblk0p19
ddr -> /dev/block/mmcblk0p38
devcfg -> /dev/block/mmcblk0p49
devcfgbak -> /dev/block/mmcblk0p50
devinfo -> /dev/block/mmcblk0p30
dip -> /dev/block/mmcblk0p29
dpo -> /dev/block/mmcblk0p33
dsp -> /dev/block/mmcblk0p26
factory -> /dev/block/mmcblk0p64
frp -> /dev/block/mmcblk0p52
fsc -> /dev/block/mmcblk0p42
fsg -> /dev/block/mmcblk0p11
hyp -> /dev/block/mmcblk0p7
hypbak -> /dev/block/mmcblk0p8
keymaster -> /dev/block/mmcblk0p15
keymasterbak -> /dev/block/mmcblk0p16
keystore -> /dev/block/mmcblk0p48
limits -> /dev/block/mmcblk0p35
logdump -> /dev/block/mmcblk0p53
logfs -> /dev/block/mmcblk0p37
mdtp -> /dev/block/mmcblk0p23
mdtpbak -> /dev/block/mmcblk0p24
mdtpsecapp -> /dev/block/mmcblk0p21
mdtpsecappbak -> /dev/block/mmcblk0p22
misc -> /dev/block/mmcblk0p47
modem -> /dev/block/mmcblk0p25
modemst1 -> /dev/block/mmcblk0p44
modemst2 -> /dev/block/mmcblk0p45
msadp -> /dev/block/mmcblk0p32
persist -> /dev/block/mmcblk0p46
pmic -> /dev/block/mmcblk0p9
pmicbak -> /dev/block/mmcblk0p10
priv -> /dev/block/mmcblk0p63
rawdump -> /dev/block/mmcblk0p56
recovery -> /dev/block/mmcblk0p59
rpm -> /dev/block/mmcblk0p5
rpmbak -> /dev/block/mmcblk0p6
sec -> /dev/block/mmcblk0p39
splash -> /dev/block/mmcblk0p34
ssd -> /dev/block/mmcblk0p43
sti -> /dev/block/mmcblk0p54
storsec -> /dev/block/mmcblk0p55
system -> /dev/block/mmcblk0p13
toolsfv -> /dev/block/mmcblk0p36
tz -> /dev/block/mmcblk0p3
tzbak -> /dev/block/mmcblk0p4
userdata -> /dev/block/mmcblk0p66
vbmeta -> /dev/block/mmcblk0p57
vendor -> /dev/block/mmcblk0p14
version -> /dev/block/mmcblk0p65
xbl -> /dev/block/mmcblk0p1
xblbak -> /dev/block/mmcblk0p2
Code:
Number Start End Size File system Name Flags
1 67.1MB 79.7MB 12.6MB xbl
2 79.7MB 92.3MB 12.6MB xblbak
3 92.3MB 96.5MB 4194kB tz
4 96.5MB 101MB 4194kB tzbak
5 101MB 101MB 524kB rpm
6 101MB 102MB 524kB rpmbak
7 102MB 102MB 524kB hyp
8 102MB 103MB 524kB hypbak
9 103MB 103MB 524kB pmic
10 103MB 104MB 524kB pmicbak
11 104MB 106MB 2097kB fsg
12 134MB 201MB 67.1MB boot
13 201MB 4496MB 4295MB ext4 system
14 4496MB 5335MB 839MB ext4 vendor
15 5335MB 5336MB 1049kB keymaster
16 5336MB 5337MB 1049kB keymasterbak
17 5337MB 5338MB 1049kB cmnlib
18 5338MB 5339MB 1049kB cmnlib64
19 5339MB 5340MB 1049kB cmnlibbak
20 5340MB 5341MB 1049kB cmnlib64bak
21 5341MB 5346MB 4194kB mdtpsecapp
22 5346MB 5350MB 4194kB mdtpsecappbak
23 5350MB 5383MB 33.6MB mdtp
24 5383MB 5417MB 33.6MB mdtpbak
25 5417MB 5532MB 115MB fat16 modem
26 5532MB 5549MB 16.8MB ext4 dsp
27 5549MB 5550MB 1049kB abl
28 5550MB 5551MB 1049kB ablbak
29 5551MB 5552MB 1049kB dip
30 5552MB 5552MB 4096B devinfo
31 5552MB 5552MB 262kB apdp
32 5552MB 5553MB 262kB msadp
33 5553MB 5553MB 1024B dpo
34 5553MB 5587MB 34.2MB splash
35 5587MB 5587MB 4096B limits
36 5587MB 5588MB 1049kB toolsfv
37 5637MB 5646MB 8389kB logfs
38 5704MB 5705MB 1049kB ddr
39 5705MB 5705MB 16.4kB sec
40 5705MB 5706MB 1049kB bluetooth
41 5706MB 5707MB 1049kB bluetoothbak
42 5771MB 5771MB 1024B fsc
43 5771MB 5771MB 8192B ssd
44 5771MB 5773MB 2097kB modemst1
45 5773MB 5776MB 2097kB modemst2
46 5776MB 5809MB 33.6MB ext4 persist
47 5809MB 5810MB 1049kB misc
48 5810MB 5811MB 524kB keystore
49 5811MB 5812MB 1049kB devcfg
50 5812MB 5813MB 1049kB devcfgbak
51 5813MB 5880MB 67.1MB ext4 asusfw
52 5880MB 5880MB 524kB frp
53 5880MB 5948MB 67.1MB logdump
54 5948MB 5950MB 2097kB sti
55 5973MB 5973MB 131kB storsec
56 6040MB 6174MB 134MB rawdump
57 6174MB 6174MB 65.5kB vbmeta
58 6174MB 6541MB 367MB ext4 cache
59 6541MB 6608MB 67.1MB recovery
60 6644MB 6853MB 210MB ext4 APD
61 6853MB 6898MB 44.0MB ext4 ADF
62 6898MB 6931MB 33.6MB ext4 asdf
63 6931MB 6932MB 524kB priv
64 6932MB 6942MB 10.5MB ext4 factory
65 6979MB 6979MB 131kB version
66 7046MB 62.5GB 55.5GB ext4 userdata
Code:
1 0 8192 ram0
1 1 8192 ram1
1 2 8192 ram2
1 3 8192 ram3
1 4 8192 ram4
1 5 8192 ram5
1 6 8192 ram6
1 7 8192 ram7
1 8 8192 ram8
1 9 8192 ram9
1 10 8192 ram10
1 11 8192 ram11
1 12 8192 ram12
1 13 8192 ram13
1 14 8192 ram14
1 15 8192 ram15
179 0 61071360 mmcblk0
179 1 12288 mmcblk0p1
179 2 12288 mmcblk0p2
179 3 4096 mmcblk0p3
179 4 4096 mmcblk0p4
179 5 512 mmcblk0p5
179 6 512 mmcblk0p6
179 7 512 mmcblk0p7
179 8 512 mmcblk0p8
179 9 512 mmcblk0p9
179 10 512 mmcblk0p10
179 11 2048 mmcblk0p11
179 12 65536 mmcblk0p12
179 13 4194304 mmcblk0p13
179 14 819200 mmcblk0p14
179 15 1024 mmcblk0p15
179 16 1024 mmcblk0p16
179 17 1024 mmcblk0p17
179 18 1024 mmcblk0p18
179 19 1024 mmcblk0p19
179 20 1024 mmcblk0p20
179 21 4096 mmcblk0p21
179 22 4096 mmcblk0p22
179 23 32768 mmcblk0p23
179 24 32768 mmcblk0p24
179 25 112640 mmcblk0p25
179 26 16384 mmcblk0p26
179 27 1024 mmcblk0p27
179 28 1024 mmcblk0p28
179 29 1024 mmcblk0p29
179 30 4 mmcblk0p30
179 31 256 mmcblk0p31
259 0 256 mmcblk0p32
259 1 1 mmcblk0p33
259 2 33424 mmcblk0p34
259 3 4 mmcblk0p35
259 4 1024 mmcblk0p36
259 5 8192 mmcblk0p37
259 6 1024 mmcblk0p38
259 7 16 mmcblk0p39
259 8 1024 mmcblk0p40
259 9 1024 mmcblk0p41
259 10 1 mmcblk0p42
259 11 8 mmcblk0p43
259 12 2048 mmcblk0p44
259 13 2048 mmcblk0p45
259 14 32768 mmcblk0p46
259 15 1024 mmcblk0p47
259 16 512 mmcblk0p48
259 17 1024 mmcblk0p49
259 18 1024 mmcblk0p50
259 19 65536 mmcblk0p51
259 20 512 mmcblk0p52
259 21 65536 mmcblk0p53
259 22 2048 mmcblk0p54
259 23 128 mmcblk0p55
259 24 131072 mmcblk0p56
259 25 64 mmcblk0p57
259 26 358400 mmcblk0p58
259 27 65536 mmcblk0p59
259 28 204800 mmcblk0p60
259 29 43008 mmcblk0p61
259 30 32768 mmcblk0p62
259 31 512 mmcblk0p63
259 32 10240 mmcblk0p64
259 33 128 mmcblk0p65
259 34 54190063 mmcblk0p66
179 32 4096 mmcblk0rpmb
Hi guys, i going to publish partition tables for our Redmi Note 8 Global (ginkgo variant).
This Thread is based on this thread.
The goal is to know partition table of our Redmi Note 8.
Code:
General Device Name: Redmi Note 8 Global
Manufacturer Product Name: M1908C3JH
Processor: Snapdragon 665
AOS version: Android P PKQ1.190616.001
Radio FW version: MPSS.AT.4.3.1-00270-NICOBAR_GEN_PACK-1.262213.1.269084.1
System FW version: Miui Global 11.0.9 (PCOMIXM)
Service Provider/ Branding: Unlocked
Country: Global
Output of command:
Code:
# parted /dev/block/mmcblk0 print
Code:
Model: MMC S0J9K9 (sd/mmc)
Disk /dev/block/mmcblk0: 125GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Number Start End Size File system Name Flags
1 20.5kB 28.7kB 8192B switch
2 28.7kB 36.9kB 8192B ssd
3 36.9kB 69.6kB 32.8kB secdata
4 69.6kB 102kB 32.8kB limits
5 102kB 135kB 32.8kB multiimgoem
6 135kB 168kB 32.8kB multiimgqti
7 168kB 233kB 65.5kB qupfw
8 233kB 299kB 65.5kB qupfwbak
9 299kB 365kB 65.5kB vbmeta
10 365kB 430kB 65.5kB vbmetabak
11 430kB 561kB 131kB xbl_config
12 561kB 692kB 131kB xbl_configbak
13 692kB 823kB 131kB devcfg
14 823kB 954kB 131kB devcfgbak
15 954kB 1049kB 94.2kB bk0
16 1049kB 1180kB 131kB storsec
17 1180kB 1311kB 131kB fsc
18 1311kB 1573kB 262kB apdp
19 1573kB 2097kB 524kB rpm
20 2097kB 2621kB 524kB rpmbak
21 2621kB 3146kB 524kB hyp
22 3146kB 3670kB 524kB hypbak
23 3670kB 4194kB 524kB keymaster
24 4194kB 4719kB 524kB keymasterbak
25 4719kB 5243kB 524kB cmnlib
26 5243kB 5767kB 524kB cmnlib64
27 5767kB 6291kB 524kB cmnlibbak
28 6291kB 6816kB 524kB cmnlib64bak
29 6816kB 7340kB 524kB keystore
30 7340kB 7864kB 524kB frp
31 7864kB 8389kB 524kB catefv
32 8389kB 8913kB 524kB uefivarstore
33 8913kB 9961kB 1049kB abl
34 9961kB 11.0MB 1049kB ablbak
35 11.0MB 12.1MB 1049kB ddr
36 12.1MB 13.1MB 1049kB bluetooth
37 13.1MB 14.2MB 1049kB bluetoothbak
38 14.2MB 15.2MB 1049kB misc
39 15.2MB 16.3MB 1049kB dip
40 16.3MB 17.3MB 1049kB toolsfv
41 17.3MB 18.4MB 1049kB catecontentfv
42 18.4MB 20.4MB 2097kB imagefv hidden
43 20.4MB 22.5MB 2097kB imagefvbak hidden
44 22.5MB 24.6MB 2097kB uefisecapp
45 24.6MB 26.7MB 2097kB uefisecappbak
46 26.7MB 28.8MB 2097kB cateloader
47 28.8MB 30.9MB 2097kB modemst1
48 30.9MB 33.0MB 2097kB modemst2
49 33.0MB 36.7MB 3670kB xbl
50 36.7MB 40.4MB 3670kB xblbak
51 40.4MB 44.6MB 4194kB tz
52 44.6MB 48.8MB 4194kB tzbak
53 48.8MB 53.0MB 4194kB mdtpsecapp
54 53.0MB 57.1MB 4194kB mdtpsecappbak
55 57.1MB 65.5MB 8389kB spunvm
56 65.5MB 67.1MB 1573kB bk1
57 67.1MB 83.9MB 16.8MB devinfo
58 83.9MB 92.3MB 8389kB logfs
59 92.3MB 103MB 10.5MB fsg
60 103MB 120MB 16.8MB ext4 metadata
61 120MB 134MB 14.7MB bk2
62 134MB 151MB 16.8MB oops
63 151MB 176MB 25.2MB dtbo
64 176MB 201MB 25.2MB dtbobak
65 201MB 235MB 33.6MB mdtp
66 235MB 268MB 33.6MB mdtpbak
67 268MB 302MB 33.6MB ext4 dsp
68 302MB 336MB 33.6MB ext4 dspbak
69 336MB 403MB 67.1MB ext4 persist
70 403MB 470MB 67.1MB ext4 persistbak
71 470MB 503MB 33.6MB logo
72 503MB 570MB 67.1MB boot
73 570MB 638MB 67.1MB bootbak
74 638MB 705MB 67.1MB splash
75 705MB 772MB 67.1MB logdump
76 772MB 839MB 67.1MB recovery
77 839MB 973MB 134MB rawdump
78 973MB 1107MB 134MB minidump
79 1107MB 1510MB 403MB exaid
80 1510MB 1778MB 268MB fat16 modem
81 1778MB 2047MB 268MB fat16 modembak
82 2047MB 2449MB 403MB ext4 cache
83 2449MB 2466MB 16.8MB gsort
84 2466MB 3540MB 1074MB ext4 cust
85 3540MB 5151MB 1611MB ext2 vendor
86 5151MB 9982MB 4832MB ext2 system
87 9982MB 125GB 115GB userdata
Output of command:
Code:
# gdisk /dev/block/mmcblk0
# p
Code:
Disk /dev/block/mmcblk0: 244285440 sectors, 116.5 GiB
Sector size (logical/physical): 512/512 bytes
Disk identifier (GUID): 4DAE07C7-651E-FE9A-E8E4-46303B32888B
Partition table holds up to 88 entries
Main partition table begins at sector 2 and ends at sector 23
First usable sector is 34, last usable sector is 244285406
Partitions will be aligned on 8-sector boundaries
Total free space is 6 sectors (3.0 KiB)
Number Start (sector) End (sector) Size Code Name
1 40 55 8.0 KiB FFFF switch
2 56 71 8.0 KiB FFFF ssd
3 72 135 32.0 KiB FFFF secdata
4 136 199 32.0 KiB FFFF limits
5 200 263 32.0 KiB FFFF multiimgoem
6 264 327 32.0 KiB FFFF multiimgqti
7 328 455 64.0 KiB FFFF qupfw
8 456 583 64.0 KiB FFFF qupfwbak
9 584 711 64.0 KiB FFFF vbmeta
10 712 839 64.0 KiB FFFF vbmetabak
11 840 1095 128.0 KiB FFFF xbl_config
12 1096 1351 128.0 KiB FFFF xbl_configbak
13 1352 1607 128.0 KiB FFFF devcfg
14 1608 1863 128.0 KiB FFFF devcfgbak
15 1864 2047 92.0 KiB FFFF bk0
16 2048 2303 128.0 KiB FFFF storsec
17 2304 2559 128.0 KiB FFFF fsc
18 2560 3071 256.0 KiB FFFF apdp
19 3072 4095 512.0 KiB FFFF rpm
20 4096 5119 512.0 KiB FFFF rpmbak
21 5120 6143 512.0 KiB FFFF hyp
22 6144 7167 512.0 KiB FFFF hypbak
23 7168 8191 512.0 KiB FFFF keymaster
24 8192 9215 512.0 KiB FFFF keymasterbak
25 9216 10239 512.0 KiB FFFF cmnlib
26 10240 11263 512.0 KiB FFFF cmnlib64
27 11264 12287 512.0 KiB FFFF cmnlibbak
28 12288 13311 512.0 KiB FFFF cmnlib64bak
29 13312 14335 512.0 KiB FFFF keystore
30 14336 15359 512.0 KiB FFFF frp
31 15360 16383 512.0 KiB FFFF catefv
32 16384 17407 512.0 KiB FFFF uefivarstore
33 17408 19455 1024.0 KiB FFFF abl
34 19456 21503 1024.0 KiB FFFF ablbak
35 21504 23551 1024.0 KiB FFFF ddr
36 23552 25599 1024.0 KiB FFFF bluetooth
37 25600 27647 1024.0 KiB FFFF bluetoothbak
38 27648 29695 1024.0 KiB FFFF misc
39 29696 31743 1024.0 KiB FFFF dip
40 31744 33791 1024.0 KiB FFFF toolsfv
41 33792 35839 1024.0 KiB FFFF catecontentfv
42 35840 39935 2.0 MiB FFFF imagefv
43 39936 44031 2.0 MiB FFFF imagefvbak
44 44032 48127 2.0 MiB FFFF uefisecapp
45 48128 52223 2.0 MiB FFFF uefisecappbak
46 52224 56319 2.0 MiB FFFF cateloader
47 56320 60415 2.0 MiB FFFF modemst1
48 60416 64511 2.0 MiB FFFF modemst2
49 64512 71679 3.5 MiB FFFF xbl
50 71680 78847 3.5 MiB FFFF xblbak
51 78848 87039 4.0 MiB FFFF tz
52 87040 95231 4.0 MiB FFFF tzbak
53 95232 103423 4.0 MiB FFFF mdtpsecapp
54 103424 111615 4.0 MiB FFFF mdtpsecappbak
55 111616 127999 8.0 MiB FFFF spunvm
56 128000 131071 1.5 MiB FFFF bk1
57 131072 163839 16.0 MiB FFFF devinfo
58 163840 180223 8.0 MiB FFFF logfs
59 180224 200703 10.0 MiB FFFF fsg
60 200704 233471 16.0 MiB FFFF metadata
61 233472 262143 14.0 MiB FFFF bk2
62 262144 294911 16.0 MiB FFFF oops
63 294912 344063 24.0 MiB FFFF dtbo
64 344064 393215 24.0 MiB FFFF dtbobak
65 393216 458751 32.0 MiB FFFF mdtp
66 458752 524287 32.0 MiB FFFF mdtpbak
67 524288 589823 32.0 MiB FFFF dsp
68 589824 655359 32.0 MiB FFFF dspbak
69 655360 786431 64.0 MiB FFFF persist
70 786432 917503 64.0 MiB FFFF persistbak
71 917504 983039 32.0 MiB 8300 logo
72 983040 1114111 64.0 MiB FFFF boot
73 1114112 1245183 64.0 MiB FFFF bootbak
74 1245184 1376255 64.0 MiB FFFF splash
75 1376256 1507327 64.0 MiB FFFF logdump
76 1507328 1638399 64.0 MiB FFFF recovery
77 1638400 1900543 128.0 MiB FFFF rawdump
78 1900544 2162687 128.0 MiB FFFF minidump
79 2162688 2949119 384.0 MiB FFFF exaid
80 2949120 3473407 256.0 MiB 0700 modem
81 3473408 3997695 256.0 MiB FFFF modembak
82 3997696 4784127 384.0 MiB FFFF cache
83 4784128 4816895 16.0 MiB FFFF gsort
84 4816896 6914047 1024.0 MiB 8300 cust
85 6914048 10059775 1.5 GiB FFFF vendor
86 10059776 19496959 4.5 GiB FFFF system
87 19496960 244285406 107.2 GiB FFFF userdata
Some Filenames that refers to this corresponding partitions:
(according to Xioami flash_all.sh)
Code:
-qupfw(qupv3fw.elf)
-qupfwbak(qupv3fw.elf)
-vbmeta(vbmeta.img)
-vbmetabak(vbmeta.img)
-xbl_config(xbl_config.elf)
-xbl_configbak(xbl_config.elf)
-devcfg(devcfg.mbn)
-devcfgbak(devcfg.mbn)
-storsec(storsec.mbn)
-rpm(rpm.mbn)
-rpmbak(rpm.mbn)
-hyp(hyp.mbn)
-hypbak(hyp.mbn)
-keymaster(km4.mbn)
-keymasterbak(km4.mbn)
-cmnlib(cmnlib.mbn)
-cmnlib64(cmnlib64.mbn)
-cmnlibbak(cmnlib.mbn)
-cmnlib64bak(cmnlib64.mbn)
-abl(abl.elf)
-ablbak(abl.elf)
-bluetooth(BTFM.bin)
-bluetoothbak(BTFM.bin)
-imagefv(imagefv.elf)
-imagefvbak(imagefv.elf)
-uefisecapp(uefi_sec.mbn)
-uefisecappbak(uefi_sec.mbn)
-xbl(xbl.elf)
-xblbak(xbl.elf)
-tz(tz.mbn)
-tzbak(tz.mbn)
-logfs(logfs_ufs_8mb.bin)
-metadata(metadata.img)
-dtbo(dtbo.img)
-dtbobak(dtbo.img)
-dsp(dspso.bin)
-dspbak(dspso.bin)
-boot(boot.img)
-bootbak(boot.img)
-recovery(recovery.img)
-modem(NON-HLOS.bin)
-modembak(NON-HLOS.bin)
-cache(cache.img)
-cust(cust.img)
-vendor(vendor.img)
-system(system.img)
-userdata(userdata.img)
Partitions With By-name:
Code:
# ls -lsah /dev/block/bootdevice/by-name/
Code:
0 lrwxrwxrwx 1 root root 21 1970-07-11 22:12 abl -> /dev/block/mmcblk0p33
0 lrwxrwxrwx 1 root root 21 1970-07-11 22:12 ablbak -> /dev/block/mmcblk0p34
0 lrwxrwxrwx 1 root root 21 1970-07-11 22:12 apdp -> /dev/block/mmcblk0p18
0 lrwxrwxrwx 1 root root 21 1970-07-11 22:12 bk0 -> /dev/block/mmcblk0p15
0 lrwxrwxrwx 1 root root 21 1970-07-11 22:12 bk1 -> /dev/block/mmcblk0p56
0 lrwxrwxrwx 1 root root 21 1970-07-11 22:12 bk2 -> /dev/block/mmcblk0p61
0 lrwxrwxrwx 1 root root 21 1970-07-11 22:12 bluetooth -> /dev/block/mmcblk0p36
0 lrwxrwxrwx 1 root root 21 1970-07-11 22:12 bluetoothbak -> /dev/block/mmcblk0p37
0 lrwxrwxrwx 1 root root 21 1970-07-11 22:12 boot -> /dev/block/mmcblk0p72
0 lrwxrwxrwx 1 root root 21 1970-07-11 22:12 bootbak -> /dev/block/mmcblk0p73
0 lrwxrwxrwx 1 root root 21 1970-07-11 22:12 cache -> /dev/block/mmcblk0p82
0 lrwxrwxrwx 1 root root 21 1970-07-11 22:12 catecontentfv -> /dev/block/mmcblk0p41
0 lrwxrwxrwx 1 root root 21 1970-07-11 22:12 catefv -> /dev/block/mmcblk0p31
0 lrwxrwxrwx 1 root root 21 1970-07-11 22:12 cateloader -> /dev/block/mmcblk0p46
0 lrwxrwxrwx 1 root root 21 1970-07-11 22:12 cmnlib -> /dev/block/mmcblk0p25
0 lrwxrwxrwx 1 root root 21 1970-07-11 22:12 cmnlib64 -> /dev/block/mmcblk0p26
0 lrwxrwxrwx 1 root root 21 1970-07-11 22:12 cmnlib64bak -> /dev/block/mmcblk0p28
0 lrwxrwxrwx 1 root root 21 1970-07-11 22:12 cmnlibbak -> /dev/block/mmcblk0p27
0 lrwxrwxrwx 1 root root 21 1970-07-11 22:12 cust -> /dev/block/mmcblk0p84
0 lrwxrwxrwx 1 root root 21 1970-07-11 22:12 ddr -> /dev/block/mmcblk0p35
0 lrwxrwxrwx 1 root root 21 1970-07-11 22:12 devcfg -> /dev/block/mmcblk0p13
0 lrwxrwxrwx 1 root root 21 1970-07-11 22:12 devcfgbak -> /dev/block/mmcblk0p14
0 lrwxrwxrwx 1 root root 21 1970-07-11 22:12 devinfo -> /dev/block/mmcblk0p57
0 lrwxrwxrwx 1 root root 21 1970-07-11 22:12 dip -> /dev/block/mmcblk0p39
0 lrwxrwxrwx 1 root root 21 1970-07-11 22:12 dsp -> /dev/block/mmcblk0p67
0 lrwxrwxrwx 1 root root 21 1970-07-11 22:12 dspbak -> /dev/block/mmcblk0p68
0 lrwxrwxrwx 1 root root 21 1970-07-11 22:12 dtbo -> /dev/block/mmcblk0p63
0 lrwxrwxrwx 1 root root 21 1970-07-11 22:12 dtbobak -> /dev/block/mmcblk0p64
0 lrwxrwxrwx 1 root root 21 1970-07-11 22:12 exaid -> /dev/block/mmcblk0p79
0 lrwxrwxrwx 1 root root 21 1970-07-11 22:12 frp -> /dev/block/mmcblk0p30
0 lrwxrwxrwx 1 root root 21 1970-07-11 22:12 fsc -> /dev/block/mmcblk0p17
0 lrwxrwxrwx 1 root root 21 1970-07-11 22:12 fsg -> /dev/block/mmcblk0p59
0 lrwxrwxrwx 1 root root 21 1970-07-11 22:12 gsort -> /dev/block/mmcblk0p83
0 lrwxrwxrwx 1 root root 21 1970-07-11 22:12 hyp -> /dev/block/mmcblk0p21
0 lrwxrwxrwx 1 root root 21 1970-07-11 22:12 hypbak -> /dev/block/mmcblk0p22
0 lrwxrwxrwx 1 root root 21 1970-07-11 22:12 imagefv -> /dev/block/mmcblk0p42
0 lrwxrwxrwx 1 root root 21 1970-07-11 22:12 imagefvbak -> /dev/block/mmcblk0p43
0 lrwxrwxrwx 1 root root 21 1970-07-11 22:12 keymaster -> /dev/block/mmcblk0p23
0 lrwxrwxrwx 1 root root 21 1970-07-11 22:12 keymasterbak -> /dev/block/mmcblk0p24
0 lrwxrwxrwx 1 root root 21 1970-07-11 22:12 keystore -> /dev/block/mmcblk0p29
0 lrwxrwxrwx 1 root root 20 1970-07-11 22:12 limits -> /dev/block/mmcblk0p4
0 lrwxrwxrwx 1 root root 21 1970-07-11 22:12 logdump -> /dev/block/mmcblk0p75
0 lrwxrwxrwx 1 root root 21 1970-07-11 22:12 logfs -> /dev/block/mmcblk0p58
0 lrwxrwxrwx 1 root root 21 1970-07-11 22:12 logo -> /dev/block/mmcblk0p71
0 lrwxrwxrwx 1 root root 21 1970-07-11 22:12 mdtp -> /dev/block/mmcblk0p65
0 lrwxrwxrwx 1 root root 21 1970-07-11 22:12 mdtpbak -> /dev/block/mmcblk0p66
0 lrwxrwxrwx 1 root root 21 1970-07-11 22:12 mdtpsecapp -> /dev/block/mmcblk0p53
0 lrwxrwxrwx 1 root root 21 1970-07-11 22:12 mdtpsecappbak -> /dev/block/mmcblk0p54
0 lrwxrwxrwx 1 root root 21 1970-07-11 22:12 metadata -> /dev/block/mmcblk0p60
0 lrwxrwxrwx 1 root root 21 1970-07-11 22:12 minidump -> /dev/block/mmcblk0p78
0 lrwxrwxrwx 1 root root 21 1970-07-11 22:12 misc -> /dev/block/mmcblk0p38
0 lrwxrwxrwx 1 root root 21 1970-07-11 22:12 modem -> /dev/block/mmcblk0p80
0 lrwxrwxrwx 1 root root 21 1970-07-11 22:12 modembak -> /dev/block/mmcblk0p81
0 lrwxrwxrwx 1 root root 21 1970-07-11 22:12 modemst1 -> /dev/block/mmcblk0p47
0 lrwxrwxrwx 1 root root 21 1970-07-11 22:12 modemst2 -> /dev/block/mmcblk0p48
0 lrwxrwxrwx 1 root root 20 1970-07-11 22:12 multiimgoem -> /dev/block/mmcblk0p5
0 lrwxrwxrwx 1 root root 20 1970-07-11 22:12 multiimgqti -> /dev/block/mmcblk0p6
0 lrwxrwxrwx 1 root root 21 1970-07-11 22:12 oops -> /dev/block/mmcblk0p62
0 lrwxrwxrwx 1 root root 21 1970-07-11 22:12 persist -> /dev/block/mmcblk0p69
0 lrwxrwxrwx 1 root root 21 1970-07-11 22:12 persistbak -> /dev/block/mmcblk0p70
0 lrwxrwxrwx 1 root root 20 1970-07-11 22:12 qupfw -> /dev/block/mmcblk0p7
0 lrwxrwxrwx 1 root root 20 1970-07-11 22:12 qupfwbak -> /dev/block/mmcblk0p8
0 lrwxrwxrwx 1 root root 21 1970-07-11 22:12 rawdump -> /dev/block/mmcblk0p77
0 lrwxrwxrwx 1 root root 21 1970-07-11 22:12 recovery -> /dev/block/mmcblk0p76
0 lrwxrwxrwx 1 root root 21 1970-07-11 22:12 rpm -> /dev/block/mmcblk0p19
0 lrwxrwxrwx 1 root root 21 1970-07-11 22:12 rpmbak -> /dev/block/mmcblk0p20
0 lrwxrwxrwx 1 root root 20 1970-07-11 22:12 secdata -> /dev/block/mmcblk0p3
0 lrwxrwxrwx 1 root root 21 1970-07-11 22:12 splash -> /dev/block/mmcblk0p74
0 lrwxrwxrwx 1 root root 21 1970-07-11 22:12 spunvm -> /dev/block/mmcblk0p55
0 lrwxrwxrwx 1 root root 20 1970-07-11 22:12 ssd -> /dev/block/mmcblk0p2
0 lrwxrwxrwx 1 root root 21 1970-07-11 22:12 storsec -> /dev/block/mmcblk0p16
0 lrwxrwxrwx 1 root root 20 1970-07-11 22:12 switch -> /dev/block/mmcblk0p1
0 lrwxrwxrwx 1 root root 21 1970-07-11 22:12 system -> /dev/block/mmcblk0p86
0 lrwxrwxrwx 1 root root 21 1970-07-11 22:12 toolsfv -> /dev/block/mmcblk0p40
0 lrwxrwxrwx 1 root root 21 1970-07-11 22:12 tz -> /dev/block/mmcblk0p51
0 lrwxrwxrwx 1 root root 21 1970-07-11 22:12 tzbak -> /dev/block/mmcblk0p52
0 lrwxrwxrwx 1 root root 21 1970-07-11 22:12 uefisecapp -> /dev/block/mmcblk0p44
0 lrwxrwxrwx 1 root root 21 1970-07-11 22:12 uefisecappbak -> /dev/block/mmcblk0p45
0 lrwxrwxrwx 1 root root 21 1970-07-11 22:12 uefivarstore -> /dev/block/mmcblk0p32
0 lrwxrwxrwx 1 root root 21 1970-07-11 22:12 userdata -> /dev/block/mmcblk0p87
0 lrwxrwxrwx 1 root root 20 1970-07-11 22:12 vbmeta -> /dev/block/mmcblk0p9
0 lrwxrwxrwx 1 root root 21 1970-07-11 22:12 vbmetabak -> /dev/block/mmcblk0p10
0 lrwxrwxrwx 1 root root 21 1970-07-11 22:12 vendor -> /dev/block/mmcblk0p85
0 lrwxrwxrwx 1 root root 21 1970-07-11 22:12 xbl -> /dev/block/mmcblk0p49
0 lrwxrwxrwx 1 root root 21 1970-07-11 22:12 xbl_config -> /dev/block/mmcblk0p11
0 lrwxrwxrwx 1 root root 21 1970-07-11 22:12 xbl_configbak -> /dev/block/mmcblk0p12
0 lrwxrwxrwx 1 root root 21 1970-07-11 22:12 xblbak -> /dev/block/mmcblk0p50
Partitions With By-Block:
Code:
# ls -lsah /dev/block/ | grep mmcblk0
Code:
0 brw------- 1 root root 179, 0 1970-07-11 22:12 mmcblk0
0 brw------- 1 root root 179, 1 1970-07-11 22:12 mmcblk0p1
0 brw------- 1 root root 179, 10 1970-07-11 22:12 mmcblk0p10
0 brw------- 1 root root 179, 11 1970-07-11 22:12 mmcblk0p11
0 brw------- 1 root root 179, 12 1970-07-11 22:12 mmcblk0p12
0 brw------- 1 root root 179, 13 1970-07-11 22:12 mmcblk0p13
0 brw------- 1 root root 179, 14 1970-07-11 22:12 mmcblk0p14
0 brw------- 1 root root 179, 15 1970-07-11 22:12 mmcblk0p15
0 brw------- 1 root root 179, 16 1970-07-11 22:12 mmcblk0p16
0 brw------- 1 root root 179, 17 1970-07-11 22:12 mmcblk0p17
0 brw------- 1 root root 179, 18 1970-07-11 22:12 mmcblk0p18
0 brw------- 1 root root 179, 19 1970-07-11 22:12 mmcblk0p19
0 brw------- 1 root root 179, 2 1970-07-11 22:12 mmcblk0p2
0 brw------- 1 root root 179, 20 1970-07-11 22:12 mmcblk0p20
0 brw------- 1 root root 179, 21 1970-07-11 22:12 mmcblk0p21
0 brw------- 1 root root 179, 22 1970-07-11 22:12 mmcblk0p22
0 brw------- 1 root root 179, 23 1970-07-11 22:12 mmcblk0p23
0 brw------- 1 root root 179, 24 1970-07-11 22:12 mmcblk0p24
0 brw------- 1 root root 179, 25 1970-07-11 22:12 mmcblk0p25
0 brw------- 1 root root 179, 26 1970-07-11 22:12 mmcblk0p26
0 brw------- 1 root root 179, 27 1970-07-11 22:12 mmcblk0p27
0 brw------- 1 root root 179, 28 1970-07-11 22:12 mmcblk0p28
0 brw------- 1 root root 179, 29 1970-07-11 22:12 mmcblk0p29
0 brw------- 1 root root 179, 3 1970-07-11 22:12 mmcblk0p3
0 brw------- 1 system system 179, 30 1970-07-11 22:12 mmcblk0p30
0 brw------- 1 root root 179, 31 1970-07-11 22:12 mmcblk0p31
0 brw------- 1 root root 259, 0 1970-07-11 22:12 mmcblk0p32
0 brw------- 1 root root 259, 1 1970-07-11 22:12 mmcblk0p33
0 brw------- 1 root root 259, 2 1970-07-11 22:12 mmcblk0p34
0 brw------- 1 root root 259, 3 1970-07-11 22:12 mmcblk0p35
0 brw------- 1 root root 259, 4 1970-07-11 22:12 mmcblk0p36
0 brw------- 1 root root 259, 5 1970-07-11 22:12 mmcblk0p37
0 brw------- 1 root root 259, 6 2020-07-19 01:28 mmcblk0p38
0 brw------- 1 root root 259, 7 1970-07-11 22:12 mmcblk0p39
0 brw------- 1 root root 179, 4 1970-07-11 22:12 mmcblk0p4
0 brw------- 1 root root 259, 8 1970-07-11 22:12 mmcblk0p40
0 brw------- 1 root root 259, 9 1970-07-11 22:12 mmcblk0p41
0 brw------- 1 root root 259, 10 1970-07-11 22:12 mmcblk0p42
0 brw------- 1 root root 259, 11 1970-07-11 22:12 mmcblk0p43
0 brw------- 1 root root 259, 12 1970-07-11 22:12 mmcblk0p44
0 brw------- 1 root root 259, 13 1970-07-11 22:12 mmcblk0p45
0 brw------- 1 root root 259, 14 1970-07-11 22:12 mmcblk0p46
0 brw------- 1 root root 259, 15 1970-07-11 22:12 mmcblk0p47
0 brw------- 1 root root 259, 16 1970-07-11 22:12 mmcblk0p48
0 brw------- 1 root root 259, 17 1970-07-11 22:12 mmcblk0p49
0 brw------- 1 root root 179, 5 1970-07-11 22:12 mmcblk0p5
0 brw------- 1 root root 259, 18 1970-07-11 22:12 mmcblk0p50
0 brw------- 1 root root 259, 19 1970-07-11 22:12 mmcblk0p51
0 brw------- 1 root root 259, 20 1970-07-11 22:12 mmcblk0p52
0 brw------- 1 root root 259, 21 1970-07-11 22:12 mmcblk0p53
0 brw------- 1 root root 259, 22 1970-07-11 22:12 mmcblk0p54
0 brw------- 1 root root 259, 23 1970-07-11 22:12 mmcblk0p55
0 brw------- 1 root root 259, 24 1970-07-11 22:12 mmcblk0p56
0 brw------- 1 root root 259, 25 1970-07-11 22:12 mmcblk0p57
0 brw------- 1 root root 259, 26 1970-07-11 22:12 mmcblk0p58
0 brw------- 1 root root 259, 27 1970-07-11 22:12 mmcblk0p59
0 brw------- 1 root root 179, 6 1970-07-11 22:12 mmcblk0p6
0 brw------- 1 root root 259, 28 1970-07-11 22:12 mmcblk0p60
0 brw------- 1 root root 259, 29 1970-07-11 22:12 mmcblk0p61
0 brw------- 1 root root 259, 30 1970-07-11 22:12 mmcblk0p62
0 brw------- 1 root root 259, 31 1970-07-11 22:12 mmcblk0p63
0 brw------- 1 root root 259, 32 1970-07-11 22:12 mmcblk0p64
0 brw------- 1 root root 259, 33 1970-07-11 22:12 mmcblk0p65
0 brw------- 1 root root 259, 34 1970-07-11 22:12 mmcblk0p66
0 brw------- 1 root root 259, 35 1970-07-11 22:12 mmcblk0p67
0 brw------- 1 root root 259, 36 1970-07-11 22:12 mmcblk0p68
0 brw------- 1 root root 259, 37 1970-07-11 22:12 mmcblk0p69
0 brw------- 1 root root 179, 7 1970-07-11 22:12 mmcblk0p7
0 brw------- 1 root root 259, 38 1970-07-11 22:12 mmcblk0p70
0 brw------- 1 root root 259, 39 1970-07-11 22:12 mmcblk0p71
0 brw------- 1 root root 259, 40 1970-07-11 22:12 mmcblk0p72
0 brw------- 1 root root 259, 41 1970-07-11 22:12 mmcblk0p73
0 brw------- 1 root root 259, 42 1970-07-11 22:12 mmcblk0p74
0 brw------- 1 root root 259, 43 1970-07-11 22:12 mmcblk0p75
0 brw------- 1 root root 259, 44 1970-07-11 22:12 mmcblk0p76
0 brw------- 1 root root 259, 45 1970-07-11 22:12 mmcblk0p77
0 brw------- 1 root root 259, 46 1970-07-11 22:12 mmcblk0p78
0 brw------- 1 root root 259, 47 1970-07-11 22:12 mmcblk0p79
0 brw------- 1 root root 179, 8 1970-07-11 22:12 mmcblk0p8
0 brw------- 1 root root 259, 48 1970-07-11 22:12 mmcblk0p80
0 brw------- 1 root root 259, 49 1970-07-11 22:12 mmcblk0p81
0 brw------- 1 root root 259, 50 1970-07-11 22:12 mmcblk0p82
0 brw------- 1 root root 259, 51 1970-07-11 22:12 mmcblk0p83
0 brw------- 1 root root 259, 52 1970-07-11 22:12 mmcblk0p84
0 brw------- 1 root root 259, 53 1970-07-11 22:12 mmcblk0p85
0 brw------- 1 root root 259, 54 1970-07-11 22:12 mmcblk0p86
0 brw------- 1 root root 259, 55 1970-07-11 22:12 mmcblk0p87
0 brw------- 1 root root 179, 9 1970-07-11 22:12 mmcblk0p9
0 brw------- 1 root root 179, 32 1970-07-11 22:12 mmcblk0rpmb
Output of:
Code:
# fastboot get_var anti
Code:
1
Hope this info helps for development reasons and you will find this beneficial.
PD: Sorry for my bad english. I'm live on Venezuela.
Guess you must be using special version of QC Qfil to flash the device or typical MSM.
In EDL mode I was in current SaharaMode been able to get infos from the firehose :
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
We have SN, MSM HWID and two OEM Hash
Don't forget that OEM SecondBootLoader have it's version also.
From normal QFil :
Code:
16:45:48: INFO: Sending <configure>
16:45:48: INFO: TARGET SAID: 'INFO: Binary build date: Dec 19 2019 @ 20:53:50'
16:45:48: INFO: TARGET SAID: 'INFO: Binary build date: Dec 19 2019 @ 20:53:50
'
16:45:48: INFO: TARGET SAID: 'INFO: Chip serial num: Not shown (0xNot Shown)'
16:45:48: INFO: TARGET SAID: 'ERROR: Verifying signature failed with 3'
16:45:48: INFO: TARGET SAID: 'ERROR: Authentication of signed hash failed 0'
Code:
16:45:48: INFO: fh.attrs.MaxPayloadSizeToTargetInBytes = 49152
16:45:48: INFO: fh.attrs.MaxPayloadSizeToTargetInBytesSupported = 1048576
16:45:48: INFO: Something failed. The target rejected your <configure>. Please inspect log for more information
Ok. Here is the deal new start from the MSM :
It creates files in C:\temp\MsmDownloadTool\
(Further analysis : https://www.joesandbox.com/analysis/372003/0/pdf)
What is interesting is autoedl.exe (It's an agent to send the phone with connected adb to EDL).
Secondary secrecy auto unlocker (SecrecyAutoUnlocker.exe 1.1) Don't know why this is integrated here (OK, for OPPO like https://www.allaboutflashing.com/oppo-a3s-network-unlock/ ), but guess no command lines are available ... (Guess). But will come back if needed that ...
DramScreenTool.exe is interesting ... No feedback ....
Available ERROR strings :
ERROR(Please enter for example. DramScreenTool.exe DRAM/EMMC/UFS CID1 CID2 ... )
DRAM.ERROR(CID size)
FAIL.EMMC.UFS.PASS
Mingw runtime failure
VirtualQuery failed for %d bytes at address %p
Unknown pseudo relocation protocol version %d
Unknown pseudo relocation bit size %d
glob-1.0-mingw32
So this is guess the utility to set the writting position for DRAM or EMMMC or UFS, need CID 1 and or CID 2
CID 1 or DID 2 could be - noticable like handshake in Sahara mode when using correct programmer :
Also HWID for QLM MSM is also noticable !
For now the SaharaMode is still not documented enought to post quick answers :
Some of the logs with implemented QFIL :
Code:
17:40:40: DEBUG: The command completed successfully.
17:40:40: DEBUG:
17:40:40: DEBUG: User set MaxPayloadSizeToTargetInBytes to 49152
17:40:40: DEBUG: User wants FIREHOSE VERBOSE - Target will log much of what it is doing
17:40:40: DEBUG: User set ZLPAWAREHOST to 1
17:40:40: DEBUG: User wants verify_programming
17:40:40: INFO: User wants to talk to port '\\.\COM3'
17:40:40: DEBUG: port_fd=0xC4
17:40:40: INFO: Took 0.00000000 seconds to open port
17:40:40: INFO: Sorting TAGS to ensure order is <configure>,<erase>, others, <patch>,<power>
17:40:40: INFO: Sending <configure>
17:40:40: DEBUG: CHANNEL DATA (P0000) (H00202) ( 225 bytes) - HOST TO TARGET -->
===========================================================================================================
<?xml version="1.0" encoding="UTF-8" ?>
<data>
<configure MemoryName="ufs" Verbose="1" AlwaysValidate="0" MaxDigestTableSizeInBytes="8192" MaxPayloadSizeToTargetInBytes="49152" ZlpAwareHost="1" SkipStorageInit="0" />
</data>
============================================================================================================
17:40:40: DEBUG: CharsInBuffer=0 Trying to read from USB 8192 bytes
17:40:40: DEBUG: CHANNEL DATA (775 bytes) <-- TARGET to HOST
17:40:40: DEBUG: CharsInBuffer = 775
17:40:40: DEBUG: printBuffer:6017 PRETTYPRINT Buffer is 775 bytes
17:40:40: DEBUG: printBuffer:6094 3C 3F 78 6D 6C 20 76 65 72 73 69 6F 6E 3D 22 31 <?xml version="1
17:40:40: DEBUG: printBuffer:6094 2E 30 22 20 65 6E 63 6F 64 69 6E 67 3D 22 55 54 .0" encoding="UT
17:40:40: DEBUG: printBuffer:6094 46 2D 38 22 20 3F 3E 0A 3C 64 61 74 61 3E 0A 3C F-8" ?>.<data>.<
17:40:40: DEBUG: printBuffer:6094 6C 6F 67 20 76 61 6C 75 65 3D 22 49 4E 46 4F 3A log value="INFO:
17:40:40: DEBUG: printBuffer:6094 20 42 69 6E 61 72 79 20 62 75 69 6C 64 20 64 61 Binary build da
17:40:40: DEBUG: printBuffer:6094 74 65 3A 20 44 65 63 20 31 39 20 32 30 31 39 20 te: Dec 19 2019
17:40:40: DEBUG: printBuffer:6094 40 20 32 30 3A 35 33 3A 35 30 22 20 2F 3E 3C 2F @ 20:53:50" /></
17:40:40: DEBUG: printBuffer:6094 64 61 74 61 3E 3C 3F 78 6D 6C 20 76 65 72 73 69 data><?xml versi
17:40:40: DEBUG: printBuffer:6094 6F 6E 3D 22 31 2E 30 22 20 65 6E 63 6F 64 69 6E on="1.0" encodin
17:40:40: DEBUG: printBuffer:6094 67 3D 22 55 54 46 2D 38 22 20 3F 3E 0A 3C 64 61 g="UTF-8" ?>.<da
17:40:40: DEBUG: printBuffer:6094 74 61 3E 0A 3C 6C 6F 67 20 76 61 6C 75 65 3D 22 ta>.<log value="
17:40:40: DEBUG: printBuffer:6094 49 4E 46 4F 3A 20 42 69 6E 61 72 79 20 62 75 69 INFO: Binary bui
17:40:40: DEBUG: printBuffer:6094 6C 64 20 64 61 74 65 3A 20 44 65 63 20 31 39 20 ld date: Dec 19
17:40:40: DEBUG: printBuffer:6094 32 30 31 39 20 40 20 32 30 3A 35 33 3A 35 30 0A 2019 @ 20:53:50.
17:40:40: DEBUG: printBuffer:6094 22 20 2F 3E 3C 2F 64 61 74 61 3E 3C 3F 78 6D 6C " /></data><?xml
17:40:40: DEBUG: printBuffer:6094 20 76 65 72 73 69 6F 6E 3D 22 31 2E 30 22 20 65 version="1.0" e
17:40:40: DEBUG: printBuffer:6094 6E 63 6F 64 69 6E 67 3D 22 55 54 46 2D 38 22 20 ncoding="UTF-8"
17:40:40: DEBUG: printBuffer:6094 3F 3E 0A 3C 64 61 74 61 3E 0A 3C 6C 6F 67 20 76 ?>.<data>.<log v
17:40:40: DEBUG: printBuffer:6094 61 6C 75 65 3D 22 49 4E 46 4F 3A 20 43 68 69 70 alue="INFO: Chip
17:40:40: DEBUG: printBuffer:6094 20 73 65 72 69 61 6C 20 6E 75 6D 3A 20 39 38 31 serial num: 000
17:40:40: DEBUG: printBuffer:6094 38 38 32 32 35 37 20 28 30 78 33 61 38 36 35 35 882000 (0x3xxxxx
17:40:40: DEBUG: printBuffer:6094 39 31 29 22 20 2F 3E 3C 2F 64 61 74 61 3E 3C 3F 91)" /></data><?
17:40:40: DEBUG: printBuffer:6094 78 6D 6C 20 76 65 72 73 69 6F 6E 3D 22 31 2E 30 xml version="1.0
17:40:40: DEBUG: printBuffer:6094 22 20 65 6E 63 6F 64 69 6E 67 3D 22 55 54 46 2D " encoding="UTF-
17:40:40: DEBUG: printBuffer:6094 38 22 20 3F 3E 0A 3C 64 61 74 61 3E 0A 3C 6C 6F 8" ?>.<data>.<lo
17:40:40: DEBUG: printBuffer:6094 67 20 76 61 6C 75 65 3D 22 45 52 52 4F 52 3A 20 g value="ERROR:
17:40:40: DEBUG: printBuffer:6094 56 65 72 69 66 79 69 6E 67 20 73 69 67 6E 61 74 Verifying signat
17:40:40: DEBUG: printBuffer:6094 75 72 65 20 66 61 69 6C 65 64 20 77 69 74 68 20 ure failed with
17:40:40: DEBUG: printBuffer:6094 33 22 20 2F 3E 3C 2F 64 61 74 61 3E 3C 3F 78 6D 3" /></data><?xm
17:40:40: DEBUG: printBuffer:6094 6C 20 76 65 72 73 69 6F 6E 3D 22 31 2E 30 22 20 l version="1.0"
17:40:40: DEBUG: printBuffer:6094 65 6E 63 6F 64 69 6E 67 3D 22 55 54 46 2D 38 22 encoding="UTF-8"
17:40:40: DEBUG: printBuffer:6094 20 3F 3E 0A 3C 64 61 74 61 3E 0A 3C 6C 6F 67 20 ?>.<data>.<log
17:40:40: DEBUG: printBuffer:6094 76 61 6C 75 65 3D 22 45 52 52 4F 52 3A 20 41 75 value="ERROR: Au
17:40:40: DEBUG: printBuffer:6094 74 68 65 6E 74 69 63 61 74 69 6F 6E 20 6F 66 20 thentication of
17:40:40: DEBUG: printBuffer:6094 73 69 67 6E 65 64 20 68 61 73 68 20 66 61 69 6C signed hash fail
17:40:40: DEBUG: printBuffer:6094 65 64 20 30 22 20 2F 3E 3C 2F 64 61 74 61 3E 3C ed 0" /></data><
17:40:40: DEBUG: printBuffer:6094 3F 78 6D 6C 20 76 65 72 73 69 6F 6E 3D 22 31 2E ?xml version="1.
17:40:40: DEBUG: printBuffer:6094 30 22 20 65 6E 63 6F 64 69 6E 67 3D 22 55 54 46 0" encoding="UTF
17:40:40: DEBUG: printBuffer:6094 2D 38 22 20 3F 3E 0A 3C 64 61 74 61 3E 0A 3C 72 -8" ?>.<data>.<r
17:40:40: DEBUG: printBuffer:6094 65 73 70 6F 6E 73 65 20 76 61 6C 75 65 3D 22 4E esponse value="N
17:40:40: DEBUG: printBuffer:6094 41 4B 22 20 72 61 77 6D 6F 64 65 3D 22 66 61 6C AK" rawmode="fal
17:40:40: DEBUG: printBuffer:6094 73 65 22 20 2F 3E 3C 2F 64 61 74 61 3E 3C 3F 78 se" /></data><?x
17:40:40: DEBUG: printBuffer:6094 6D 6C 20 76 65 72 73 69 6F 6E 3D 22 31 2E 30 22 ml version="1.0"
17:40:40: DEBUG: printBuffer:6094 20 65 6E 63 6F 64 69 6E 67 3D 22 55 54 46 2D 38 encoding="UTF-8
17:40:40: DEBUG: printBuffer:6094 22 20 3F 3E 0A 3C 64 61 74 61 3E 0A 3C 6C 6F 67 " ?>.<data>.<log
17:40:40: DEBUG: printBuffer:6094 20 76 61 6C 75 65 3D 22 45 52 52 4F 52 3A 20 46 value="ERROR: F
17:40:40: DEBUG: printBuffer:6094 61 69 6C 65 64 20 74 6F 20 72 65 61 64 20 58 4D ailed to read XM
17:40:40: DEBUG: printBuffer:6094 4C 20 63 6F 6D 6D 61 6E 64 20 2D 31 22 20 2F 3E L command -1" />
17:40:40: DEBUG: printBuffer:6094 3C 2F 64 61 74 61 3E </data>
17:40:40: DEBUG: printBuffer:6107
17:40:40: DEBUG: XML FILE (117 bytes): CharsInBuffer=775-117=658
-------------------------------------------------------------------------------------------
<?xml version="1.0" encoding="UTF-8" ?>
<data>
<log value="INFO: Binary build date: Dec 19 2019 @ 20:53:50" /></data>
-------------------------------------------------------------------------------------------
17:40:40: INFO: TARGET SAID: 'INFO: Binary build date: Dec 19 2019 @ 20:53:50'
17:40:40: DEBUG: XML FILE (118 bytes): CharsInBuffer=658-118=540
-------------------------------------------------------------------------------------------
<?xml version="1.0" encoding="UTF-8" ?>
<data>
<log value="INFO: Binary build date: Dec 19 2019 @ 20:53:50
" /></data>
-------------------------------------------------------------------------------------------
17:40:40: INFO: TARGET SAID: 'INFO: Binary build date: Dec 19 2019 @ 20:53:50
17:40:40: DEBUG: XML FILE (115 bytes): CharsInBuffer=540-115=425
-------------------------------------------------------------------------------------------
<?xml version="1.0" encoding="UTF-8" ?>
<data>
<log value="INFO: Chip serial num: 9xxxxxx (0xxxxxxxx)" /></data>
-------------------------------------------------------------------------------------------
17:40:40: INFO: TARGET SAID: 'INFO: Chip serial num: 9srgrg7 (0xrhrhrh)'
17:40:40: DEBUG: XML FILE (110 bytes): CharsInBuffer=425-110=315
-------------------------------------------------------------------------------------------
<?xml version="1.0" encoding="UTF-8" ?>
<data>
<log value="ERROR: Verifying signature failed with 3" /></data>
-------------------------------------------------------------------------------------------
17:40:40: INFO: TARGET SAID: 'ERROR: Verifying signature failed with 3'
17:40:40: DEBUG: XML FILE (115 bytes): CharsInBuffer=315-115=200
-------------------------------------------------------------------------------------------
<?xml version="1.0" encoding="UTF-8" ?>
<data>
<log value="ERROR: Authentication of signed hash failed 0" /></data>
-------------------------------------------------------------------------------------------
17:40:40: INFO: TARGET SAID: 'ERROR: Authentication of signed hash failed 0'
17:40:40: DEBUG: XML FILE (94 bytes): CharsInBuffer=200-94=106
-------------------------------------------------------------------------------------------
<?xml version="1.0" encoding="UTF-8" ?>
<data>
<response value="NAK" rawmode="false" /></data>
-------------------------------------------------------------------------------------------
17:40:40: INFO: IGNORING UNRECOGNIZED Attribute 'rawmode' with value 'false'
17:40:40: DEBUG: Response was 'NAK'
17:40:40: INFO: fh.attrs.MaxPayloadSizeToTargetInBytes = 49152
17:40:40: INFO: fh.attrs.MaxPayloadSizeToTargetInBytesSupported = 1048576
17:40:40: INFO: Something failed. The target rejected your <configure>. Please inspect log for more information
For now reading the Chinese pdf also in MSM temp : MSMDownloadToolSpecificationCHS.pdf
Because have seen the Qualcomm HS-USB Diagnostics 9006 driver and this could be the key for the correct Sahara/Firehose implementation and handshake protocol.
Qualcomm download device (Qualcomm HS-USB QDLoader 9008,
Qualcomm HS-USB Diagnostics 9006) corresponding serial port numbers are increasing
Open the hidden device in the device manager as follows:
① Create a new environment variable, the name is devmgr_show_nonpresent_devices, the value is 1, and then open the device manager;
② Device Manager—View—Display hidden devices;
③ Manually delete one by one or use USBDeview.exe to delete selected device drivers in batches.
Till then ...
For now the only thing to bother is usage of the MSM (pure official) as only flashable program without any dongle.
As seen on the test executables the problem is in the executable program in MSM the DRAM_Screen_Tool_v2.0 or emmcdl.
The second thing is flash boot programmer end provisioning options.
Also the Sahara Download mode.
Been able to do some magic with emmcdl, but cannot get the correct loader and Sahara mode Configuration from phone like SN but vere unable to get HASHES and HWID's.
But after the boot of the flash programmer the device goes into non recognisable mode.
For now the problems are with ERRORS :
Verifying signature failed with 3 and Authentication of signed hash failed 0.
With Qfil and QsaharaServer I'm out of possibilities, when It would be able to prepare the stuff with one all other could be possible.
Some feedback to share :
Code:
emmcdl -p COM4 -f prog_firehose_ddr.elf -info
Version 2.15
Downloading flash programmer: prog_firehose_ddr.elf
Successfully open flash programmer to write: prog_firehose_ddr.elf
Waiting for flash programmer to boot
Failed to write hello response back to device
Did not receive Sahara hello packet from device
Status: 6 The handle is invalid.
Code:
emmcdl -p COM4 -SkipWrite -SkipStorageInit -f prog_firehose_ddr.elf -x memory_configure.xml
Version 2.15
Downloading flash programmer: prog_firehose_ddr.elf
Successfully open flash programmer to write: prog_firehose_ddr.elf
Waiting for flash programmer to boot
<?xml version="1.0" encoding="UTF-8" ?>
<data>
<log value="INFO: Binary build date: Dec 19 2019 @ 20:53:50" /></data><?xml version="1.0" encoding="UTF-8" ?>
<data>
<log value="INFO: Binary build date: Dec 19 2019 @ 20:53:50
" /></data><?xml version="1.0" encoding="UTF-8" ?>
<data>
<log value="INFO: Chip serial num: not shown (0xnot shown)" /></data>
Programming device using SECTOR_SIZE=512
<?xml version = "1.0" ?><data><configure MemoryName="emmc" ZLPAwareHost="1" SkipStorageInit="1" SkipWrite="1" MaxPayloadSizeToTargetInBytes="1048576"/></data>
<?xml version="1.0" encoding="UTF-8" ?>
<data>
<log value="ERROR: Verifying signature failed with 3" /></data>
<?xml version="1.0" encoding="UTF-8" ?>
<data>
<log value="ERROR: Authentication of signed hash failed 0" /></data>
<?xml version="1.0" encoding="UTF-8" ?>
<data>
<response value="NAK" rawmode="false" /></data>
---Target returned NAK---
<?xml version="1.0" encoding="UTF-8" ?>
<data>
<log value="ERROR: Failed to read XML command -1" /></data>
ERROR: No response to configure packet
Status: 21 The device is not ready.
So the configuration is needed and preservation of QSahara mode for the successfull flash/diagnostics.