Somewhat Obscure Computing - User contributions [en]

ZTE Avid 4

2026-03-09T03:03:53Z

Chipmunk: oops

The '''ZTE Avid 4''' is an [[Android]] [[handset]] released by [[wikipedia:ZTE|ZTE Corporation]] in 2017. It includes the [[Qualcomm MSM8909]] chipset and has [[Android]] 7.0 preinstalled.


== EDL mode ==

[[Qualcomm EDL mode]] can be accessed on this phone easily using <code>adb reboot edl</code>. The phone uses EMMC storage, and its EDL loader can be obtained [https://github.com/programmer-collection/zte/blob/master/Z855/prog_emmc_firehose_8909.mbn here].

Be careful! Attempting to flash the phone using the EDL loader automatically detected by bkerler's client can result in a hard brick, requiring you to disassemble the phone to get back into EDL mode.


== Unlocking the bootloader ==

See [[Qualcomm EDL mode#Bootloader unlocking]]

ZTE Avid 4

2026-03-09T03:03:32Z

Chipmunk:

The '''ZTE Avid 4''' is an [[Android]] [[handset]] released by [[wikipedia:ZTE|ZTE Corporation]] in 2017. It includes the [[Qualcomm MSM8909]] chipset and has [[Android]] 7.0 preinstalled.


== EDL mode ==

[[Qualcomm EDL mode]] can be accessed on this phone easily using <code>adb reboot edl</code>. The phone uses EMMC storage, and its EDL loader can be obtained [https://github.com/programmer-collection/zte/blob/master/Z855/prog_emmc_firehose_8909.mbn here].

Be careful! Attempting to flash the phone using the EDL loader automatically detected by bkerler's client can result in a hard brick, requiring you to disassemble the phone to get back into EDL mode.



== Unlocking the bootloader ==

See [[Qualcomm EDL mode#Bootloader unlocking]]

Qualcomm EDL mode

2026-03-09T03:00:47Z

Chipmunk:

'''Qualcomm EDL mode''' is a boot mode implemented in the [[boot rom]] of devices using [[Qualcomm SoCs]], which includes features such as reading/writing partitions. It can be used for purposes such as unbricking hard-bricked devices, or flashing partitions on devices that lack [[fastboot]] mode or an equivalent.

Various clients for EDL exist, such as Qualcomm's own QFIL, [https://github.com/linux-msm/qdl qdl], or [https://github.com/bkerler/edl bkerler's 'edl']. Unless otherwise specified, the wiki will provide instructions using bkerler's client.

== Dumping the stock OS ==

The stock operating system of a device can be dumped with <code>edl rl backup --skip=userdata --genxml</code>. This will dump every partition other than <code>userdata</code> to a folder named <code>backup</code>, and generate an XML file.

''(command adapted from [[pmos:ZTE Axon 7 (zte-axon7)|here]])''

== Bootloader unlocking ==

Some devices' bootloaders can be unlocked using EDL mode, by editing the <code>devinfo</code> partition.

First of all, <code>devinfo</code> must be dumped with <code>edl r devinfo devinfo.bin</code>.

Afterwards, the resulting <code>devinfo.bin</code> should be opened in a hex editor. The partition should have the magic <code>ANDROID-BOOT!</code> at the beginning, and optionally at other locations. Where it occurs, replace this:
<pre>
41 4E 44 52 4F 49 44 2D 42 4F 4F 54 21 00 00 00
00|00 00 00 00 00 00 00|00|00 00 00 00 00 00 00
</pre>
With this:
<pre>
41 4E 44 52 4F 49 44 2D 42 4F 4F 54 21 00 00 00
01|00 00 00 00 00 00 00|01|00 00 00 00 00 00 00
</pre>

Lastly, save the file, and flash it with <code>edl w devinfo devinfo.bin</code>.

''(adapted from [[xda:bootloader-unlocking-on-older-qualcomm-zte-devices-devinfo-partition-modification.4100897/|this]] XDA thread)''

Qualcomm EDL mode

2026-03-09T03:00:04Z

Chipmunk: Show the modified octets

'''Qualcomm EDL mode''' is a boot mode implemented in the [[boot rom]] of devices using [[Qualcomm SoCs]], which includes features such as reading/writing partitions. It can be used for purposes such as unbricking hard-bricked devices, or flashing partitions on devices that lack [[fastboot]] mode or an equivalent.

Various clients for EDL exist, such as Qualcomm's own QFIL, [https://github.com/linux-msm/qdl qdl], or [https://github.com/bkerler/edl bkerler's 'edl']. Unless otherwise specified, the wiki will provide instructions using bkerler's client.

== Dumping stock ==

The stock operating system of a device can be dumped with <code>edl rl backup --skip=userdata --genxml</code>. This will dump every partition other than <code>userdata</code> to a folder named <code>backup</code>, and generate an XML file.

''(command adapted from [[pmos:ZTE Axon 7 (zte-axon7)|here]])''

== Bootloader unlocking ==

Some devices' bootloaders can be unlocked using EDL mode, by editing the <code>devinfo</code> partition.

First of all, <code>devinfo</code> must be dumped with <code>edl r devinfo devinfo.bin</code>.

Afterwards, the resulting <code>devinfo.bin</code> should be opened in a hex editor. The partition should have the magic <code>ANDROID-BOOT!</code> at the beginning, and optionally at other locations. Where it occurs, replace this:
<pre>
41 4E 44 52 4F 49 44 2D 42 4F 4F 54 21 00 00 00
00|00 00 00 00 00 00 00|00|00 00 00 00 00 00 00
</pre>
With this:
<pre>
41 4E 44 52 4F 49 44 2D 42 4F 4F 54 21 00 00 00
01|00 00 00 00 00 00 00|01|00 00 00 00 00 00 00
</pre>

Lastly, save the file, and flash it with <code>edl w devinfo devinfo.bin</code>.

''(adapted from [[xda:bootloader-unlocking-on-older-qualcomm-zte-devices-devinfo-partition-modification.4100897/|this]] XDA thread)''

User:Chipmunk

2026-03-09T02:55:00Z

Chipmunk:

Hello.

I created this wiki, originally as a place for me to document useful information I find about various hardware. This was actually going to be a personal wiki originally, however I realized the wiki would potentially be much more useful if others could add information. Who knows, maybe someday, it might document high amounts of devices.

Also, I am actually fairly new to the Android device hacking scene. I began looking into it in 2024, and have since learned many things. I am also still quite new to low-level programming and reverse engineering.

Some things I aim to do eventually:
* Reverse engineer Samsung's reactivation lock (<code>libterrier.so</code>?) and document it (that's where the 'obscure' in 'Somewhat Obscure Computing' comes from - I doubt this feature is well documented!) ''(some reversing work done)''.
* Use [https://i.blackhat.com/USA-20/Wednesday/us-20-Chao-Breaking-Samsungs-Root-Of-Trust-Exploiting-Samsung-Secure-Boot.pdf an exploit] to tethered unlock my Galaxy J3 Prime, Galaxy J7 Prime and/or my Galaxy J3 Orbit (if possible) (also document the <code>steady</code> partition on the wiki) ([https://code.chipmunk.land/chipmunkmc/osmium.git done] except for steady).
* Port an EFI implementation to an x86 phone (Asus Z00D).
* Write a tool to ''reliably'' exploit [[wikipedia:Dirty Cow|Dirty Cow]], preferably ''without'' touching <code>/system</code> and escalating to the ''init'' context (for legacy devices of course) (also, can I easily write process memory? I suppose I will find out).
* Look into unlock methods for various phones... (I own too many).

User:Chipmunk

2025-10-20T04:13:15Z

Chipmunk: Update info

Hello.

I created this wiki, originally as a place for me to document useful information I find about various hardware. This was actually going to be a personal wiki originally, however I realized the wiki would potentially be much more useful if others could add information. Who knows, maybe someday, it might document high amounts of devices.

Also, I am actually fairly new to the Android device hacking scene. I began looking into it in 2024, and have since learned many things. I am also still quite new to low-level programming and reverse engineering.

Some things I aim to do eventually:
* Port [https://github.com/oscardagrach/galaxy_s5_dev_tree_appended_bug galaxy_s5_dev_tree_appended_bug] to my AT&T Galaxy S5.
* Reverse engineer Samsung's reactivation lock (<code>libterrier.so</code>?) and document it (that's where the 'obscure' in 'Somewhat Obscure Computing' comes from - I doubt this feature is well documented!) ''(some reversing work done)''.
* Use [https://i.blackhat.com/USA-20/Wednesday/us-20-Chao-Breaking-Samsungs-Root-Of-Trust-Exploiting-Samsung-Secure-Boot.pdf an exploit] to tethered unlock my Galaxy J3 Prime, Galaxy J7 Prime and/or my Galaxy J3 Orbit (if possible) (also document the <code>steady</code> partition on the wiki) (making progress now!).
* Port an EFI implementation to an x86 phone (Asus Z00D).
* Write a tool to ''reliably'' exploit [[wikipedia:Dirty Cow|Dirty Cow]], preferably ''without'' touching <code>/system</code> and escalating to the ''init'' context (for legacy devices of course) (also, can I easily write process memory? I suppose I will find out...).
* Look into unlock methods for various phones... (I own too many).

User:Chipmunk

2025-06-30T04:46:10Z

Chipmunk:

Hello.

I created this wiki, originally as a place for me to document useful information I find about various hardware. This was actually going to be a personal wiki originally, however I realized the wiki would potentially be much more useful if others could add information. Who knows, maybe someday, it might document high amounts of devices.

Also, I am actually fairly new to the Android device hacking scene. I began looking into it in 2024, and have since learned many things. I am also still quite new to low-level programming and reverse engineering.

Some things I aim to do eventually:
* Port [https://github.com/oscardagrach/galaxy_s5_dev_tree_appended_bug galaxy_s5_dev_tree_appended_bug] to my AT&T Galaxy S5 (currently borrowed), and AT&T Samsung Gear S (vulnerability is questionable due to the different boot image format).
* Reverse engineer Samsung's reactivation lock (<code>libterrier.so</code>?) and document it (that's where the 'obscure' in 'Somewhat Obscure Computing' comes from - I doubt this feature is well documented!).
* Use [https://i.blackhat.com/USA-20/Wednesday/us-20-Chao-Breaking-Samsungs-Root-Of-Trust-Exploiting-Samsung-Secure-Boot.pdf an exploit] to tethered unlock my Galaxy J3 Prime, Galaxy J7 Prime and/or my Galaxy J3 Orbit (if possible) (also document the <code>steady</code> partition on the wiki).
* Port an EFI implementation to an x86 phone (Asus Z00D).
* Write a tool to ''reliably'' exploit [[wikipedia:Dirty Cow|Dirty Cow]], preferably ''without'' touching <code>/system</code> and escalating to the ''init'' context (for legacy devices of course) (also, can I easily write process memory? I suppose I will find out...).
* Look into unlock methods for various phones... (I own too many).

User:Chipmunk

2025-06-30T04:41:53Z

Chipmunk: the phone also checks for a value derived from the steady partition, which appears to be signed

Hello.

I created this wiki, originally as a place for me to document useful information I find about various hardware. This was actually going to be a personal wiki originally, however I realized the wiki would potentially be much more useful if others could add information. Who knows, maybe someday, it might document high amounts of devices.

Also, I am actually fairly new to the Android device hacking scene. I began looking into it in 2024, and have since learned many things. I am also still quite new to low-level programming and reverse engineering.

Some things I aim to do eventually:
* Port [https://github.com/oscardagrach/galaxy_s5_dev_tree_appended_bug galaxy_s5_dev_tree_appended_bug] to my AT&T Galaxy S5 (currently borrowed), and AT&T Samsung Gear S (vulnerability is questionable due to the different boot image format).
* Reverse engineer Samsung's reactivation lock (<code>libterrier.so</code>?) and document it (that's where the 'obscure' in 'Somewhat Obscure Computing' comes from - I doubt this feature is well documented!).
* Use [https://i.blackhat.com/USA-20/Wednesday/us-20-Chao-Breaking-Samsungs-Root-Of-Trust-Exploiting-Samsung-Secure-Boot.pdf an exploit] to tethered unlock my Galaxy J3 Prime and/or my Galaxy J3 Orbit (if possible) (also document the <code>steady</code> partition on the wiki).
* Port an EFI implementation to an x86 phone (Asus Z00D).
* Look into unlock methods for various phones... (I own too many).

User:Chipmunk

2025-06-28T18:30:59Z

Chipmunk: oops i meant persistent

Hello.

I created this wiki, originally as a place for me to document useful information I find about various hardware. This was actually going to be a personal wiki originally, however I realized the wiki would potentially be much more useful if others could add information. Who knows, maybe someday, it might document high amounts of devices.

Also, I am actually fairly new to the Android device hacking scene. I began looking into it in 2024, and have since learned many things. I am also still quite new to low-level programming and reverse engineering.

Some things I aim to do eventually:
* Port [https://github.com/oscardagrach/galaxy_s5_dev_tree_appended_bug galaxy_s5_dev_tree_appended_bug] to my AT&T Galaxy S5 (currently borrowed), and AT&T Samsung Gear S (vulnerability is questionable due to the different boot image format).
* Reverse engineer Samsung's reactivation lock (<code>libterrier.so</code>?) and document it (that's where the 'obscure' in 'Somewhat Obscure Computing' comes from - I doubt this feature is well documented!).
* Use [https://i.blackhat.com/USA-20/Wednesday/us-20-Chao-Breaking-Samsungs-Root-Of-Trust-Exploiting-Samsung-Secure-Boot.pdf an exploit] to unlock my Galaxy J3 Prime and/or my Galaxy J3 Orbit (if possible).
* Port an EFI implementation to an x86 phone (Asus Z00D).
* Look into unlock methods for various phones... (I own too many).

User:Chipmunk

2025-06-28T18:24:34Z

Chipmunk: sboot doesnt actually have symbols afaik, it just has lots of logging with format strings with function parameters... also j3 prime seems unlockable via param partition

Hello.

I created this wiki, originally as a place for me to document useful information I find about various hardware. This was actually going to be a personal wiki originally, however I realized the wiki would potentially be much more useful if others could add information. Who knows, maybe someday, it might document high amounts of devices.

Also, I am actually fairly new to the Android device hacking scene. I began looking into it in 2024, and have since learned many things. I am also still quite new to low-level programming and reverse engineering.

Some things I aim to do eventually:
* Port [https://github.com/oscardagrach/galaxy_s5_dev_tree_appended_bug galaxy_s5_dev_tree_appended_bug] to my AT&T Galaxy S5 (currently borrowed), and AT&T Samsung Gear S (vulnerability is questionable due to the different boot image format).
* Reverse engineer Samsung's reactivation lock (<code>libterrier.so</code>?) and document it (that's where the 'obscure' in 'Somewhat Obscure Computing' comes from - I doubt this feature is well documented!).
* Use [https://i.blackhat.com/USA-20/Wednesday/us-20-Chao-Breaking-Samsungs-Root-Of-Trust-Exploiting-Samsung-Secure-Boot.pdf an exploit] to unlock my Galaxy J3 Prime and/or my Galaxy J3 Orbit (if possible).
* Port an EFI implementation to an x86 phone (Asus Z00D).
* Look into unlock methods for various phones... (I own too many).

User:Chipmunk

2025-06-28T01:49:10Z

Chipmunk:

Hello.

I created this wiki, originally as a place for me to document useful information I find about various hardware. This was actually going to be a personal wiki originally, however I realized the wiki would potentially be much more useful if others could add information. Who knows, maybe someday, it might document high amounts of devices.

Also, I am actually fairly new to the Android device hacking scene. I began looking into it in 2024, and have since learned many things. I am also still quite new to low-level programming and reverse engineering.

Some things I aim to do eventually:
* Port [https://github.com/oscardagrach/galaxy_s5_dev_tree_appended_bug galaxy_s5_dev_tree_appended_bug] to my <s>Verizon Galaxy Core Prime</s> (probably not vulnerable!), AT&T Galaxy S5, and AT&T Samsung Gear S (vulnerability is questionable due to the different boot image format).
* Reverse engineer Samsung's reactivation lock (<code>libterrier.so</code>?) and document it (that's where the 'obscure' in 'Somewhat Obscure Computing' comes from - I doubt this feature is well documented!).
* Figure out the 'sboot' file format, and how the included symbols come into play
* Use [https://i.blackhat.com/USA-20/Wednesday/us-20-Chao-Breaking-Samsungs-Root-Of-Trust-Exploiting-Samsung-Secure-Boot.pdf an exploit] to unlock my Galaxy J3 Prime and/or my Galaxy J3 Orbit (if possible).
* Port an EFI implementation to an x86 phone (Asus Z00D).
* Look into unlock methods for various phones... (I own too many).

User:Chipmunk

2025-06-26T18:13:03Z

Chipmunk:

Hello.

I created this wiki, originally as a place for me to document useful information I find about various hardware. This was actually going to be a personal wiki originally, however I realized the wiki would potentially be much more useful if others could add information. Who knows, maybe someday, it might document high amounts of devices.

Also, I am actually fairly new to the Android device hacking scene. I began looking into it in 2024, and have since learned many things. I am also still quite new to low-level programming and reverse engineering.

Some things I aim to do eventually:
* Port [https://github.com/oscardagrach/galaxy_s5_dev_tree_appended_bug galaxy_s5_dev_tree_appended_bug] to my Verizon Galaxy Core Prime, AT&T Galaxy S5, and AT&T Samsung Gear S.
* Reverse engineer Samsung's reactivation lock (<code>libterrier.so</code>?) and document it (that's where the 'obscure' in 'Somewhat Obscure Computing' comes from - I doubt this feature is well documented!).
* Figure out the 'sboot' file format, and how the included symbols come into play
* Use a particular exploit (forgot the URL) to unlock my Galaxy J3 Prime and/or my Galaxy J3 Orbit (if possible).
* Port an EFI implementation to an x86 phone (Asus Z00D).
* Look into unlock methods for various phones... (I own too many).

User:Chipmunk

2025-06-26T14:49:04Z

Chipmunk: Created page with "Hello. I created this wiki, originally as a place for me to document useful information I find about various hardware. This was actually going to be a personal wiki originally, however I realized the wiki would potentially be much more useful if others could add information. Who knows, maybe someday, it might document high amounts of devices. Also, I am actually fairly new to the Android device hacking scene. I began looking into it in 2024<!-- as of writing this, last..."

edl

2025-06-26T14:06:39Z

Chipmunk: Redirected page to Qualcomm EDL mode

#REDIRECT [[Qualcomm EDL mode]]

ZTE Avid 4

2025-06-26T14:05:03Z

Chipmunk: lol oops

The '''ZTE Avid 4''' is an [[Android]] [[handset]] released by [[wikipedia:ZTE|ZTE Corporation]] in 2017. It includes the [[Qualcomm MSM8909]] chipset and has [[Android]] 7.0 preinstalled.


== EDL mode ==

[[Qualcomm EDL mode]] can be accessed on this phone easily using <code>adb reboot edl</code>. The phone uses EMMC storage, and its EDL loader can be obtained [https://github.com/programmer-collection/zte/blob/master/Z855/prog_emmc_firehose_8909.mbn here].


== Unlocking the bootloader ==

See [[Qualcomm EDL mode#Bootloader unlocking]]

Main Page

2025-06-26T14:01:50Z

Chipmunk:

This is a wiki focused on the [[wikipedia:Hacking of consumer_electronics|hacking of consumer electronics]], mostly on mobile computers such as Android handsets.

<s>There is no actual information here though... ''yet''</s> Now there is ''some''.

If enough people care about this wiki (in the future) an IRC channel might be created.

Qualcomm EDL mode

2025-06-26T13:59:06Z

Chipmunk:

'''Qualcomm EDL mode''' is a boot mode implemented in the [[boot rom]] of devices using [[Qualcomm SoCs]], which includes features such as reading/writing partitions. It can be used for purposes such as unbricking hard-bricked devices, or flashing partitions on devices that lack [[fastboot]] mode or an equivalent.

Various clients for EDL exist, such as Qualcomm's own QFIL, [https://github.com/linux-msm/qdl qdl], or [https://github.com/bkerler/edl bkerler's 'edl']. Unless otherwise specified, the wiki will provide instructions using bkerler's client.

== Dumping stock ==

The stock operating system of a device can be dumped with <code>edl rl backup --skip=userdata --genxml</code>. This will dump every partition other than <code>userdata</code> to a folder named <code>backup</code>, and generate an XML file.

''(command adapted from [[pmos:ZTE Axon 7 (zte-axon7)|here]])''

== Bootloader unlocking ==

Some devices' bootloaders can be unlocked using EDL mode, by editing the <code>devinfo</code> partition.

First of all, <code>devinfo</code> must be dumped with <code>edl r devinfo devinfo.bin</code>.

Afterwards, the resulting <code>devinfo.bin</code> should be opened in a hex editor. The partition should have the magic <code>ANDROID-BOOT!</code> at the beginning, and optionally at other locations. Where it occurs, replace this:
<pre>
41 4E 44 52 4F 49 44 2D 42 4F 4F 54 21 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
</pre>
With this:
<pre>
41 4E 44 52 4F 49 44 2D 42 4F 4F 54 21 00 00 00
01 00 00 00 00 00 00 00 01 00 00 00 00 00 00 00
</pre>

Lastly, save the file, and flash it with <code>edl w devinfo devinfo.bin</code>.

''(adapted from [[xda:bootloader-unlocking-on-older-qualcomm-zte-devices-devinfo-partition-modification.4100897/|this]] XDA thread)''

Qualcomm EDL mode

2025-06-26T13:50:23Z

Chipmunk:

'''Qualcomm EDL mode''' is a boot mode implemented in the [[boot rom]] of devices using [[Qualcomm SoCs]], which includes features such as reading/writing partitions. It can be used for purposes such as unbricking hard-bricked devices, or flashing partitions on devices that lack [[fastboot]] mode or an equivalent.

Various clients for EDL exist, such as Qualcomm's own QFIL, [https://github.com/linux-msm/qdl qdl], or [https://github.com/bkerler/edl bkerler's 'edl']. Unless otherwise specified, the wiki will provide instructions using bkerler's client.

== Dumping stock ==

The stock operating system of a device can be dumped with <code>edl rl backup --skip=userdata --genxml</code>. This will dump every partition other than <code>userdata</code> to a folder named <code>backup</code>, and generate an XML file.

''(command adapted from [[pmos:ZTE Axon 7 (zte-axon7)|here]])''

== Bootloader unlocking ==

Some devices' bootloaders can be unlocked using EDL mode, by editing the <code>devinfo</code> partition.

First of all, <code>devinfo</code> must be dumped with <code>edl r devinfo devinfo.bin</code>.

Afterwards, the resulting <code>devinfo.bin</code> should be opened in a hex editor. The partition should have the magic <code>ANDROID-BOOT!</code> at the beginning, and optionally at other locations. Where it occurs, replace this:
<pre>
41 4E 44 52 4F 49 44 2D 42 4F 4F 54 21 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
</pre>
With this:
<pre>
41 4E 44 52 4F 49 44 2D 42 4F 4F 54 21 00 00 00
01 00 00 00 00 00 00 00 01 00 00 00 00 00 00 00
</pre>

Lastly, save the file, and flash it with <code>edl w devinfo devinfo.bin</code>.

''(adapted from [https://xdaforums.com/t/bootloader-unlocking-on-older-qualcomm-zte-devices-devinfo-partition-modification.4100897/ this] XDA thread)''

Qualcomm EDL mode

2025-06-26T13:40:23Z

Chipmunk:

'''Qualcomm EDL mode''' is a boot mode implemented in the [[boot rom]] of devices using [[Qualcomm SoCs]], which includes features such as reading/writing partitions. It can be used for purposes such as unbricking hard-bricked devices, or flashing partitions on devices that lack [[fastboot]] mode or an equivalent.

Various clients for EDL exist, such as Qualcomm's own QFIL, [https://github.com/linux-msm/qdl qdl], or [https://github.com/bkerler/edl bkerler's 'edl']. Unless otherwise specified, the wiki will provide instructions using bkerler's client.

== Dumping stock ==

The stock operating system of a device can be dumped with <code>edl rl backup --skip=userdata --genxml</code>. This will dump every partition other than <code>userdata</code> to a folder named <code>backup</code>, and generate an XML file.

''(command adapted from [[pmOS:ZTE Axon 7 (zte-axon7)]])''

== Bootloader unlocking ==

Some devices' bootloaders can be unlocked using EDL mode, by editing the <code>devinfo</code> partition.

First of all, <code>devinfo</code> must be dumped with <code>edl r devinfo devinfo.bin</code>.

Afterwards, the resulting <code>devinfo.bin</code> should be opened in a hex editor. The partition should have the magic <code>ANDROID-BOOT!</code> at the beginning, and optionally at other locations. Where it occurs, replace this:
<pre>
41 4E 44 52 4F 49 44 2D 42 4F 4F 54 21 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
</pre>
With this:
<pre>
41 4E 44 52 4F 49 44 2D 42 4F 4F 54 21 00 00 00
01 00 00 00 00 00 00 00 01 00 00 00 00 00 00 00
</pre>

Lastly, save the file, and flash it with <code>edl w devinfo devinfo.bin</code>.

''(adapted from [https://xdaforums.com/t/bootloader-unlocking-on-older-qualcomm-zte-devices-devinfo-partition-modification.4100897/ this] XDA thread)''

ZTE Avid 4

2025-06-26T13:31:09Z

Chipmunk:

The '''ZTE Avid 4''' is an [[Android]] [[handset]] released by [[wikipedia:ZTE|ZTE Corporation]] in 2017. It includes the [[Qualcomm MSM8909]] chipset and has [[Android]] 7.0 preinstalled.


== EDL mode ==

[[Qualcomm EDL mode]] can be accessed on this phone easily using <code>adb reboot edl</code>. The phone uses EMMC storage, and its EDL loader can be obtained [https://github.com/programmer-collection/zte/blob/master/Z855/prog_emmc_firehose_8909.mbn here].


== Unlocking the bootloader ==

See [[Qualcomm EDL Mode#Bootloader unlocking]]

Main Page

2025-06-26T13:29:43Z

Chipmunk:

This is a wiki focused on the [[wikipedia:Hacking of consumer_electronics|hacking of consumer electronics]], mostly on mobile computers such as Android handsets.

<s>There is no actual information here though... yet</s> Now there is ''some''.

If enough people care about this wiki (in the future) an IRC channel might be created.

Qualcomm EDL mode

2025-06-26T13:27:22Z

Chipmunk:

'''Qualcomm EDL mode''' is a boot mode implemented in the [[boot rom]] of devices using [[Qualcomm SoCs]], which includes features such as reading/writing partitions. It can be used for purposes such as unbricking hard-bricked devices, or flashing partitions on devices that lack [[fastboot]] mode or an equivalent.

Various clients for EDL exist, such as Qualcomm's own QFIL, [https://github.com/linux-msm/qdl qdl], or [https://github.com/bkerler/edl bkerler's 'edl']. Unless otherwise specified, the wiki will provide instructions using bkerler's client.

== Bootloader unlocking ==

Some phones' bootloaders can be unlocked using EDL mode, by editing the <code>devinfo</code> partition.

First of all, <code>devinfo</code> must be dumped with <code>edl r devinfo devinfo.bin</code>.

Afterwards, the resulting <code>devinfo.bin</code> should be opened in a hex editor. The partition should have the magic <code>ANDROID-BOOT!</code> at the beginning, and optionally at other locations. Where it occurs, replace this:
<pre>
41 4E 44 52 4F 49 44 2D 42 4F 4F 54 21 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
</pre>
With this:
<pre>
41 4E 44 52 4F 49 44 2D 42 4F 4F 54 21 00 00 00
01 00 00 00 00 00 00 00 01 00 00 00 00 00 00 00
</pre>

Lastly, save the file, and flash it with <code>edl w devinfo devinfo.bin</code>.

[https://xdaforums.com/t/bootloader-unlocking-on-older-qualcomm-zte-devices-devinfo-partition-modification.4100897/ (adapted from this XDA thread)]

calbee

2025-06-26T13:23:00Z

Chipmunk: Redirected page to ZTE Avid 4

#REDIRECT [[ZTE Avid 4]]

Android

2025-06-26T03:39:51Z

Chipmunk: Created page with "Android is an operating system for various types of devices, most famously ARM-based handsets and tablets. It uses a patched version of the Linux kernel."

Android is an operating system for various types of devices, most famously ARM-based handsets and tablets. It uses a patched version of [[Linux|the Linux kernel]].

ZTE Avid 4

2025-06-26T03:33:34Z

Chipmunk:

The '''ZTE Avid 4''' is an [[Android]] [[handset]] released in 2017. It includes the [[Qualcomm MSM8909]] chipset and has [[Android]] 7.0 preinstalled.


== EDL mode ==

[[Qualcomm EDL mode]] can be accessed on this phone easily using <code>adb reboot edl</code>. The phone uses EMMC storage, and its EDL loader can be obtained [https://github.com/programmer-collection/zte/blob/master/Z855/prog_emmc_firehose_8909.mbn here].


== Unlocking the bootloader ==

See [[Qualcomm EDL Mode#Bootloader unlocking]]

Qualcomm EDL mode

2025-06-26T03:32:25Z

Chipmunk: Created page with "'''Qualcomm EDL mode''' is a boot mode implemented in the boot rom of devices using Qualcomm SoCs, which includes features such as reading/writing partitions. It can be used for purposes such as unbricking hard-bricked devices, or flashing partitions on devices that lack fastboot mode or an equivalent. Various clients for EDL exist, such as Qualcomm's own QFIL, [https://github.com/linux-msm/qdl qdl], or [https://github.com/bkerler/edl bkerler's 'edl']. Unles..."

'''Qualcomm EDL mode''' is a boot mode implemented in the [[boot rom]] of devices using [[Qualcomm SoCs]], which includes features such as reading/writing partitions. It can be used for purposes such as unbricking hard-bricked devices, or flashing partitions on devices that lack [[fastboot]] mode or an equivalent.

Various clients for EDL exist, such as Qualcomm's own QFIL, [https://github.com/linux-msm/qdl qdl], or [https://github.com/bkerler/edl bkerler's 'edl']. Unless otherwise specified, the wiki will provide instructions using bkerler's client.

== Bootloader unlocking ==

Some phones' bootloaders can be unlocked using EDL mode, by editing the <code>devinfo</code> partition.

First of all, <code>devinfo</code> must be dumped with <code>edl r devinfo devinfo.bin</code>.

Afterwards, the resulting <code>devinfo.bin</code> should be opened in a hex editor. The partition should have the magic <code>ANDROID-BOOT!</code> at the beginning, and optionally at other locations. Where it occurs, replace this:
<pre>
41 4E 44 52 4F 49 44 2D 42 4F 4F 54 21 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
</pre>
With this:
<pre>
41 4E 44 52 4F 49 44 2D 42 4F 4F 54 21 00 00 00
01 00 00 00 00 00 00 00 01 00 00 00 00 00 00 00
</pre>

Lastly, save the file, and flash it with <code>edl w devinfo devinfo.bin</code>

[https://xdaforums.com/t/bootloader-unlocking-on-older-qualcomm-zte-devices-devinfo-partition-modification.4100897/ (adapted from this XDA thread)]

ZTE Avid 4

2025-06-26T03:05:00Z

Chipmunk:

The ZTE Avid 4 is an [[Android]] [[handset]] released in 2017. It includes the [[Qualcomm MSM8909]] chipset and has [[Android]] 7.0 preinstalled.


== EDL mode ==

[[Qualcomm EDL mode]] can be accessed on this phone easily using <code>adb reboot edl</code>. The phone uses EMMC storage, and its EDL loader can be obtained [https://github.com/programmer-collection/zte/blob/master/Z855/prog_emmc_firehose_8909.mbn here].


== Unlocking the bootloader ==

See [[Qualcomm EDL Mode#Bootloader unlocking]]

ZTE Avid 4

2025-06-26T03:04:49Z

Chipmunk: Created page with "The ZTE Avid 4 is an Android handset released in 2017. It includes the Qualcomm MSM8909 chipset and has Android 7.0 preinstalled.  == EDL mode == Qualcomm EDL mode can be accessed on this phone easily using <code>adb reboot edl</code>. The phone uses EMMC storage, and its EDL loader can be obtained [https://github.com/programmer-collection/zte/blob/master/..."

The ZTE Avid 4 is an [[Android]] [[handset]] released in 2017. It includes the [[Qualcomm MSM8909]] chipset and has [[Android]] 7.0 preinstalled.


== EDL mode ==

[[Qualcomm EDL mode]] can be accessed on this phone easily using <code>adb reboot edl</code>. The phone uses EMMC storage, and its EDL loader can be obtained [https://github.com/programmer-collection/zte/blob/master/Z855/prog_emmc_firehose_8909.mbn here].



== Unlocking the bootloader ==

See [[Qualcomm EDL Mode#Bootloader unlocking]]

Main Page

2025-06-14T04:02:04Z

Chipmunk:

This is a wiki focused on the [[wikipedia:Hacking of consumer_electronics|hacking of consumer electronics]], mostly on mobile computers such as Android handsets.

There is no actual information here though... yet

If enough people care about this wiki (in the future) an IRC channel might be created.

Somewhat Obscure Computing:About

2025-06-14T04:01:41Z

Chipmunk:

This wiki aims to do document information relating to the [[wikipedia:Hacking of consumer electronics|hacking of consumer electronics]], particularly for mobile, embedded, or just unusual computers, in an organized way. This includes information from operating systems available for devices, to technical details on quirks specific to various devices, and even to unlocking bootloaders, bypassing bootloader signature checks, and/or escalating to root privileges on the preinstalled operating system.

I was originally planning on making this a personal wiki, but realized it would likely be more optimal to allow other users to edit its contents.

The name of this wiki is a backronym of SoC, which stands for [[wikipedia:System on a chip|system on a chip]]. This is because this wiki mainly aims to document devices that are based on systems on chips.

Although websites such as [https://xdaforums.com/ XDA Forums] and [https://wiki.postmarketos.org/wiki/Main_Page The postmarketOS Wiki] already serve a similar purpose, the first is forum rather than a wiki, and the second is focused on a specific operating system.

Somewhat Obscure Computing:About

2025-06-14T04:00:09Z

Chipmunk: Protected "Somewhat Obscure Computing:About" ([Edit=Allow only administrators] (indefinite) [Move=Allow only administrators] (indefinite))

This wiki aims to do document information relating to the [[wikipedia:Hacking of consumer electronics|hacking of consumer electronics]], particularly for mobile computers, in an organized way. This includes information from operating systems available for devices, to technical details on quirks specific to various devices, and even to unlocking bootloaders, bypassing bootloader signature checks, and/or escalating to root privileges on the preinstalled operating system.

The name of this wiki is a backronym of SoC, which stands for [[wikipedia:System on a chip|system on a chip]]. This is because this wiki mainly aims to document devices that are based on systems on chips.

Although websites such as [https://xdaforums.com/ XDA Forums] and [https://wiki.postmarketos.org/wiki/Main_Page The postmarketOS Wiki] already serve a similar purpose, the first is forum rather than a wiki, and the second is focused on a specific operating system.

Main Page

2025-06-14T03:59:49Z

Chipmunk: remove duplicate wording

This is a wiki focused on the [[wikipedia:Hacking of consumer_electronics|hacking of consumer electronics]], particularly mobile computers such as Android handsets.

There is no actual information here though... yet

If enough people care about this wiki (in the future) an IRC channel might be created.

Main Page

2025-06-13T04:39:05Z

Chipmunk:

Main Page

2025-06-13T04:36:50Z

Chipmunk:

Somewhat Obscure Computing:About

2025-06-13T04:33:52Z

Chipmunk: fix casing

Somewhat Obscure Computing:About

2025-06-13T04:33:14Z

Chipmunk: Created page with "This wiki aims to do document information relating to the hacking of consumer electronics, particularly for mobile computers, in an organized way. This includes information from operating systems available for devices, to technical details on quirks specific to various devices, and even to unlocking bootloaders, bypassing bootloader signature checks, and/or escalating to root privileges on the preinstalled operating system...."

This wiki aims to do document information relating to the [[wikipedia:Hacking of consumer electronics|hacking of consumer electronics]], particularly for mobile computers, in an organized way. This includes information from operating systems available for devices, to technical details on quirks specific to various devices, and even to unlocking bootloaders, bypassing bootloader signature checks, and/or escalating to root privileges on the preinstalled operating system.

The name of this wiki is a backronym of SoC, which stands for [[wikipedia:System on a chip|system on a chip]]. This is because this wiki mainly aims to document devices that are based on systems on chips.

Although websites such as [https://xdaforums.com/ XDA Forums] and [https://wiki.postmarketos.org/wiki/Main_Page The PostmarketOS Wiki] already serve a similar purpose, the first is forum rather than a wiki, and the second is focused on a specific operating system. The objective of this wiki is to

Main Page

2025-06-13T03:16:05Z

Chipmunk: Protected "Main Page" ([Edit=Allow only administrators] (indefinite) [Move=Allow only administrators] (indefinite))

MediaWiki has been installed.

Consult the [https://www.mediawiki.org/wiki/Special:MyLanguage/Help:Contents User's Guide] for information on using the wiki software.

== Getting started ==
* [https://www.mediawiki.org/wiki/Special:MyLanguage/Manual:Configuration_settings Configuration settings list]
* [https://www.mediawiki.org/wiki/Special:MyLanguage/Manual:FAQ MediaWiki FAQ]
* [https://lists.wikimedia.org/postorius/lists/mediawiki-announce.lists.wikimedia.org/ MediaWiki release mailing list]
* [https://www.mediawiki.org/wiki/Special:MyLanguage/Localisation#Translation_resources Localise MediaWiki for your language]
* [https://www.mediawiki.org/wiki/Special:MyLanguage/Manual:Combating_spam Learn how to combat spam on your wiki]