yashsingh1/xdaforums huggingface dataset:
[OnePlus X General] SebiderSushi:
I wouldn't give up just yet. The actual rule for entering EDL mode on the OnePlus X is:

- The device must be powered off at the beginning

- The Volume Up button must be in pressed state when connecting it to the computer

Edit 2022-09-04: I was wrong about this. It is also possible to hold Power+Vol Up while connected to the PC until the device shows up in dmesg -w

Everything else, like waiting few seconds here and there is mostly safeties to ensure each state is entered or recognized cleanly.

I mostly had my phone running fresh from the last flashing process, which means that qdl had turned it off cleanly for me. So i definitely had good conditions to enter EDL mode.

I don't know what's going on with your notification LED since i didn't notice this on my device or payed any attention to it - but it might indicate that your phone could be in a not cleanly powered off state.

You can still try pressing the power button for a longer time (maybe about 10 to 30 seconds) to see if that switches off your device the right way before you retry entering EDL mode.

Or do any other experiments pressing buttons or try with different cables.

When was the last time you could successfully connect your device in any mode and which mode was it?
[OnePlus X General] SebiderSushi:
The symptoms you described about black screen, no vibrations or any reaction to button presses were also present on my device as well so this is i'd guess it's just normal for the state.
[OnePlus X General] SebiderSushi:
If you get it back to a booting state you should be able to install the official OxygenOS right from the stock recovery, or flash a compatible TWRP image using qdl or fastboot and copy any remaining data that you want to keep.
[OnePlus X General] ze7zez:
@SebiderSushi, could you please take a look at >this post< and hint if anything else can be done using edl on linux?
[OnePlus X General] ze7zez:
This onyx is recycled. I do not care about the data.

edl doesn't much want to read either.

user@livedvd:/opt/edl$ ./edl r recovery dump_recovery.img
Qualcomm Sahara / Firehose Client V3.60 (c) B.Kerler 2018-2022.
main - Trying with no loader given ...
main - Waiting for the device
main - Device detected :)
sahara - Protocol version: 2.1
main - Mode detected: sahara
sahara -
------------------------
HWID: 0x007bc0e100000000 (MSM_ID:0x007bc0e1,OEM_ID:0x0000,MODEL_ID:0x0000)
CPU detected: "MSM8974ABv3"
PK_HASH: 0xcc3153a80293939b90d02d3bf8b23e0292e452fef662c74998421adad42a380f
Serial: 0x0e24123e

sahara - Possibly unfused device detected, so any loader should be fine...
sahara - Trying loader: /opt/edl/edlclient/../Loaders/qualcomm/factory/msm8974abv3/007bc0e100000000_cc3153a80293939b_fhprg_oneplusone_peek.bin
sahara - Protocol version: 2.1
sahara - Uploading loader /opt/edl/edlclient/../Loaders/qualcomm/factory/msm8974abv3/007bc0e100000000_cc3153a80293939b_fhprg_oneplusone_peek.bin ...
sahara
sahara - [LIB]: [Errno 5] Input/output error
[OnePlus X General] SebiderSushi:
@ze7zez Hmmm. You could try an older version: git checkout 3.52.1

I am unable to get edl working on the master branch at commit 069b9d1e293d9c5259e8e6bed10f8caf5ffe5293 but i'm getting different error messages. git tag 3.52.1 works for everything i did on my oneplus x. just note that the script was still called edl.py at that point.

also, if the installer didn't care to put edl somewhere in your PATH directories you might want to sudo ln -sT /opt/edl/edl /usr/bin/edl so you can cd to the directory you actually want to work in and dump your files to while being able to just have edl in your $PATH. alternatively, skip the installation step and run mkdir -p ~/.local/bin && ln -srT ./edl.py ~/.local/bin/edl && export PATH=~/.local/bin:$PATH from the the git repository folder instead. if you want this to stick around multiple terminal sessions add a line with export PATH=~/.local/bin:$PATH to the .bashrc file in your home directory.
[OnePlus X General] ze7zez:
I did not toil too much, but I downloaded Sytemback Live based on xubuntu from the site you provided in post #21.

After launching Linux, there is a full working environment for edl prepared in the terminal.

I checked that it is possible to create a /opt/edl directory file, so I executed as above.

Can version 3.52.1 be downloaded and run from Live USB?
[OnePlus X General] SebiderSushi:
Okay in that case what you should be able to do is follow the installation instrucations for Linux. On an Ubuntu based distribution it might be necessary to launch "Software & Updates" and put a checkmark at 'Community-maintained free and open-source software (universe)' to make all dependencies available.

I never tried the Live ISO for edl but as it seems, most of the steps should not be necessary on the live iso since it's prepared but repeating them won't hurt either. Some of the dependencies from the installation instructions might not be preinstalled on the Live ISO if they are only needed for building edl. You should be able to install any missing dependencies in a live environment as long as it's connected to the internet. The limiting factor is your PCs memory since the live ISO will use it as a virtual harddisk for the duration of your live session.

This is what you want to get working after following the first portions of the installation instructions to cover the dependencies on your Linux Distribution. I just tested this on the official Ubuntu 22.04 ISO and with my OnePlus X.

# Change to the home directory
cd
# Clone the Source code repository and Loaders subrepository
git clone https://github.com/bkerler/edl.git
cd edl
git submodule update --init --recursive
sudo cp Drivers/51-edl.rules /etc/udev/rules.d
sudo cp Drivers/50-android.rules /etc/udev/rules.d
# A git repository contains all of the code history, this command tells git
# to write the revision that got tagged "3.52.1" to the working directory.
git checkout 3.52.1
# To make sure that all required python modules are installed
pip install -r requirements.txt
# Since Python is an interpreted scripting language, it is possible to just run it without compiling anything
./edl.py
# To override the 'edl' command
mkdir -p ~/.local/bin &&
ln -srT ./edl.py ~/.local/bin/edl
export PATH=~/.local/bin:$PATH
printf '\nexport PATH=~/.local/bin:$PATH\n' >> ~/.bashrc
# Running 'edl' should now execute 'edl.py' straight from the git repository, using the checked-out version or revision.
mkdir -p ~/onyx_brick_workdir/ && cd ~/onyx_brick_workdir/
edl printgpt
edl r recovery recovery_bricked_test.img

Spoiler content hidden.
[OnePlus X General] ze7zez:
Your instructions are almost perfect. 🚀

There was no git and pip, but ubuntu helps how to install.

I can read the phone memory! 🕺

Spoiler content hidden.
[OnePlus X General] SebiderSushi:
That's great! I hope you can now go back to the instructions from the original post of this thread together with post#21 and get a stock recovery running to do the regular unlock process or, if that still won't work, do some tests and find out if your flash is actually dead.

The best part is that now that you have edl running you'll be able to take a dump of your storage once everything works again using edl rl <output directory> (as described in post#21)

whenever you need to unbrick your device again you'll be able to use that dump to restore every partition, not just the ones that are provided with the unbrick tool. this includes any possible device-specific information and the bootloader unlock state for this specific device.
[OnePlus X General] ze7zez:
It went fast with

edl rl dump_onyx_bricked --genxml --skip=grow,boot,system,cache,userdata

I'm doing

edl rf dump_onyx_full_brokengpt.img

and there's a lot of it.

I don't want to move anything, but I need to mount the notebook drive to dump the whole system on it.

edit 1

=====

The downloaded recovery_bricked_test.img has a different checksum than OPX_recovery.img and OPX_MM_recovery.img.

edit 2

=====

Writing to the phone failed.

Spoiler content hidden.

edit 3

=====

It's a bit strange, because writing recovery_bricked_test.img is correct and on top of that at a remarkably high speed of 18.77 MB/s versus 0.06 MB/s for OPX_recovery.img or OPX_MM_recovery.img.

Spoiler content hidden.
[OnePlus X General] SebiderSushi:
edl rl dump_onyx_bricked --genxml --skip=grow,boot,system,cache,userdata is supposed to be fast since it does not dump the big/empty partitions you usually don't care about or which you can just reflash with the next ROM. but edl must be able to read the partition table to do so (and in your case it looked very much intact). edl rf <filename> takes a long time because it dumps the whole internal storage which is the easy alternative if the partition table is broken and you want a backup before trying to write anything to the flash storage at all. but you don't need this method if the first command gives you intact and reproducible dumps.

any edl r <partition> <file> dump will always be of a full partition, that is 16MiB for the OnePlus X recovery. The recovery images are usually smaller since they only contain the amount of data that's required.

you can compare these with cmp -l <file 1> <file 2>

cmp will compare the files byte by byte and print any difference. if cmp only complains that the recovery image you tried to flash is shorter than the dump you took afterwards they are identical for our intents and purposes.

i would definitely try to flash one version of the OPX_recovery.img and try to boot it regardless of error messages. if that still does not work retry with OPX_MM_recovery.img

the error log you sent should, in fact, not appear. it could be a sign that your flash storage does have an issue. you can try writing to other partitions like cache as i mentioned to do some read write testing. but that is all i can think of at this point. you will basically have to decide for yourself how to set up these tests, when to give up and what conclusions to draw at the end. in any case, i wish you the best of luck!

another tip: when dealing with these large files you can run fallocate --dig-holes <file>. if the filesystem supports it, this will replace all file segments that only consist of zeroes with a descriptor that stores how long this segment of zeroes is supposed to be and the data no longer needs to be stored on disk. the file will have the same size but will effectively use less storage space. this concept is called a "sparse file" and is supported on most Linux filesystems.
[OnePlus X General] ze7zez:
After writting OPX_recovery.img/ OPX_MM_recovery.img there is the same effect of booting into recovery mode: booloop (vibration, oneplus logo and so on and so forth).
[OnePlus X General] SebiderSushi:
Okay so you could try to just go through the whole regular guide in post#1. You'd want to "flash everything from the unbrick tool" according to the instructions given. The only difference would be that you don't have to set up QDL and can use edl instead. Just substitute the call to qdl with edl qfil rawprogram0.xml patch0.xml ./

yeah indeed. the fact that you can restore the recovery dump without errors is extremely strange and i have absolutely no explanation for that at this point.
[OnePlus X General] ze7zez:
Thanks, I will try it tomorrow late afternoon.
[OnePlus X General] ze7zez:
Today I will not try to save the partitions.

I am thinking about why there are divergent similarities between partitions ( marked in colors).

I have 4 Onyx. The comparison in the appendix.
[OnePlus X General] SebiderSushi:
Some partitions are specific to each device, some might be the same for all but there are usually multiple versions for each component.

Here is an overview of common partitions on android devices. You can also have a look in the UnBrick tool and what firmware it contains or into a OxygenOS OTA zip and check the update-script to understand which partitions are flashed during a system upgrade. And, like i said with regards to cmp, keep in mind that partition dumps are always complete while flashing to them may only affect used space, leaving the contents of unused remaining space completely undefined. Comparing checksums across devices or between raw files and device dumps has very limited use.
[OnePlus X General] ze7zez:
All files uploaded correctly.

Unfortunately the phone behaves the same as before,

Now I know for sure that my onyx is a hard brick.

Thank you SebiderSushi for the interesting experience with edl on Linux.

Spoiler content hidden.
[OnePlus X General] SebiderSushi:
Welp, that's a bummer. Apart from that i was glad to help, maybe your experience could come in handy another time.
[OnePlus X General] Scalp4:
Warning : This message concern a OnePlus6 phone, i post message here by mistake.

Hello @SebiderSushi,

first of all, happy new year :)

for no reason my OnePlus6 doesn't work anymore and displays the screen "QUALCOMM Crash Dump mode" without any other information.

I got this screen after the OP logo is displayed, the result is the same when trying to go through recovery mode / fastboot mode.

I'm on Ubuntu so I tried to follow your tutorial.

Firstly, i tried with QDL method on your first post, but whatever my attempt i got :

➜ workingdirectory qdl prog_emmc_firehose_8974.mbn rawprogram0.xml patch0.xml
Waiting for EDL device
HELLO version: 0x2 compatible: 0x1 max_len: 1024 mode: 0
READ64 image: 13 offset: 0x0 length: 0x40
END OF IMAGE image: 13 status: 20
received non-successful result

i tried with

- OPX_MM_recovery.img

- OPX_recovery.img

but same result.

Then i following your post and did backup :

Spoiler content hidden.

Then i did this command : edl qfil rawprogram0.xml patch0.xml ./

But i cant remember which recover.img was used for it.

Spoiler content hidden.

After that my phone didnt boot anymore, when i try to push the power button i stay on black screen without any vibration.

Then i tried again with OPX_recovery.img and it seems to work, but a lot of "[LIB]: 'NoneType' object has no attribute 'totalsectors'" appears in the logs.

Spoiler content hidden.

but spoiler alert, still black screen.

Before play edl qfil commands i also tried edl r recovery, but i got this error :

Spoiler content hidden.

I don't know what else to try, I don't need to get my data back, I just want to be able to start from a factory version and restart my OP..

Thank you A LOT in advance for your help.
[OnePlus X General] ze7zez:
OPX* files are for the Oneplus X, not the Oneplus 6.
[OnePlus X General] Scalp4:
Warning : This message concern a OnePlus6 phone, i post message here by mistake.

oh... sorry, but i've the same result with IMG

OnePlus6Oxygen_22_OTA_025_all_1809150101_boot.img

or

OnePlus6Oxygen_22_OTA_027_all_1810260000_boot.img

:(
[OnePlus X General] Scalp4:
Warning : This message concern a OnePlus6 phone, i post message here by mistake.

Unfortunately i cant find a file like "UnBrick tool mini" but for OP6, any idea ?
[OnePlus X General] SebiderSushi:
Just like ze7zez pointed out this guide and all files referenced in it are specific to the OnePlus X. This is what the read disclaimer at the start of the section on EDL is supposed to convey. Please do let me know if there is any way to misunderstand that after reading it.

At least you took a backup, hopefully it is complete! I don't own any modern device so i am not at all familiar with more recent storage types and how they are partitioned so i cannot comment or assist on that, sorry.

Best bet is for you to restore the backup you made, then try any of the recommended unbricking instructions you can find. Familiarize yourself with the capabilities of the EDL tool so you can find out on your own how to make the specific guides you find work on a linux machine. Any unbrick guide that utilizes the "MSM Download Tool" should also be doable with QDL or the EDL tool.

You might have more luck by going to the XDA subsection dedicated to the OnePlus 6, then search for the term "unbrick" and make sure to select "This forum" from the dropdown before clicking the blue search button.

It is probably a good idea to search the web for the terms "QUALCOMM Crash Dump mode" together with "OnePlus 6" specifically because it sounds specific enough that there might be guides out there that directly address this scenario.

If you still can't find anything you can trust or work with you might have some luck with downloading the latest OTA zip for your device directly from OnePlus and flashing the files in there to your device. You should be able to figure out which file belongs to which partition name by having a look at the META-INF/com/google/android/updater-script file inside the OTA zip. This method assumes that you have a working backup which serves as a controllable starting point for anything you try and to which you can return to after any human error. Again, refer to the EDL manual and any information you can find about your specific device to find out what constitutes a complete backup and how to create & restore it. Also, make sure that you have a backup of your partition table, otherwise you will have to find a working UnBrick guide, these usually re-create the partition table as well.

Good luck!
[OnePlus X General] Scalp4:
Warning : This message concern a OnePlus6 phone, i post message here by mistake.

Thank you for your answer @SebiderSushi

I post now on the good thread, here : https://xdaforums.com/t/guide-mega-unbrick-guide-for-a-hard-bricked-oneplus-6.3796051/page-12

Yesterday i restore all the dump with this command duplicated on each bin file : edl wf lun4/mdtpsecapp_b.bin --memory=ufs --lun=4

but nothing change, black screen

i also tried what it's explained on this Twitter thread :

https://twitter.com/i/web/status/1423088813702795269

but nothing change, black screen

and the following is on the OP6 thread, after tries on Windows, printgpt evolves but still black screen, i you have any idea, thank you in advance.

@ze7zez i saw your message, once i fix it or resign myself i will clean my post on this thread, sorry for the inconvenience
[OnePlus X General] SebiderSushi:
I hope you find the assistance you need! The twitter thread looks like a very good find. It should at least help you work with factory images regardless of where you end up finding a working one.

The command you posted tells edl to write the file lun4/mdtpsecapp_b.bin straight to lun number 4. The issue is that the file contains the contents of one specific partition that is located on lun4 - it is not a full dump of the whole lun. It needs to be written to the correct location on lun 4 while the other partitions need to be restored from their respective files in the dump.

Since you used the "edl rl" command to create the dump you'll need the "edl wl" command to restore it as opposed to the "edl wf" command. Refer to the manual or "edl --help" on how to use these. When restoring, check the output and make sure that all files for all the luns on your device get restored.

There's no need to clean up your messages unless you want to have them removed. Also obviously read manuals and do your own research first but don't apologize if you need to ask for help if the resources are hard to find or if you're not yet familiar enough to make sense of them. I hope you can end up bringing your device back to life and get a good experience out of this and maybe even learn something useful along the way.
[OnePlus X General] Scalp4:
So I'm not going to clean up my posts in hopes that it will help someone else on how to use these tools.

I have however added this message to each of my posts.

Warning : This message concern a OnePlus6 phone, i post message here by mistake.

I will continue here : https://xdaforums.com/t/guide-mega-unbrick-guide-for-a-hard-bricked-oneplus-6.3796051/page-12
[Samsung Galaxy Note 10+ Questions & Answers] genhao3:
Network environment: 802.11AX and LAN

Device: AX88U

NOTE10: OS Samsung official

The normal LAN speed of the mobile phone is as follows:

When the mobile phone is watching a movie on the local area network and continues to fast forward, when the mobile phone slightly heats up. WIFI speed is severely reduced.

It only takes a short continuous fast forward of 3 to 5 minutes, and the WIFI speed will be reduced by 10 times, which directly leads to the failure to watch movies normally.

At this time, the WIFI speed of the mobile phone is as follows:

The reason why this is said is because the previous NOTE8 (8895) did not have this situation

Turning the phone on in high-performance mode and turning off battery optimization will not solve the above problem. Is there a way to solve this problem.
[Samsung Galaxy Note 10+ Questions & Answers] winol:
Just watch movies as they are intended to, at normal speed, Qhy would you watch a movie by fast forwarding for so long?
[Samsung Galaxy Note 10+ Questions & Answers] genhao3:
Because some movies do not need to be viewed at normal speed, such as those without clothes, I can watch dozens of such movies in one night
[Samsung Galaxy Note 10+ Questions & Answers] genhao3:
Is there no solution?
[P3600 General] filjoa:
Hi

some know if have an software for mak tracking with WM6?

regards
[P3600 General] djfuego:
Good ones

If you have your phone stolen "Mobile Justice" (the phone has to be on)

And mobilejustice is querky to get running. There is a sim lock feature too so you can lock it to your sims.

You sms your phone for it's gps location.

http://sourceforge.net/projects/mjustice

Satnav "TomTom"

or hiking "chtiGPS"

http://www.pocketpcfreewares.com/en/index.php?soft=1546

Lots of GPS apps here

http://www.pocketpcfreewares.com/en/index.php?cat=30&sortby=
[Xperia Z5 Premium Android Development] Joel16:
LineageOS is a free and open-source operating system for various devices, based on the Android mobile platform.

Disclaimer:

It is your decision to install this software on your device. Neither LineageOS developers nor I take any responsibility for any damage that may occur from installing this software on your device.

[IMG="Screenshot 1"]https://i.imgur.com/2Cyho2a.png[/IMG] [IMG="Screenshot 2"]https://i.imgur.com/hUHuAMz.png[/IMG]​

Notes:

This rom does not come pre-rooted or bundled with any modifications or apps. The device tree is heavily based off of Sumire's officical lineageOS repo with only the necessary modifications required for Satsuki (Z5 Premium).

Download:

Android File Host: ROM

Prerequisites:

- Make sure you're coming from firmware 32.4.A.1.54 before flashing this rom.

- Bootloader needs to be unlocked.

- Ensure that you have TWRP recovery from here.

Install:

1) Reboot into TWRP Recovery.

2) Select Wipe -> Swipe to factory reset -> Advanced Wipe -> Dalvik /ART Cache, System, Cache and Data -> Swipe to Wipe.

3) Go back to TWRP's main menu -> Select Install -> Locate and choose lineage-14.1-20200507-UNOFFICIAL-satsuki.zip file -> Swipe to confirm flash.

GApps/Root:

- Flash Gapps arm64 7.1 for Google Apps.

- Flash Magisk for root.

Sources:

Kernel

Device Tree (Satsuki | kitakami-common)

Bugs:

Please let me know about any bugs you encounter, I will look into them ASAP. Personally I haven't found any but I've tested the basic features such as brightness, camera, flash, sim detection, WiFi, Bluetooth, fingerprint, sound etc. which are all working fine on my device (E6853).

XDA:DevDB Information

LineageOS 14.1, ROM for the Sony Xperia Z5 Premium

Contributors

Joel16

ROM OS Version: 7.x Nougat

ROM Kernel: Linux 3.10.x

Version Information

Status: Stable

Current Stable Version: 2020-05-07

Stable Release Date: 2019-12-12

Created 2019-12-11

Last Updated 2020-05-07
[Xperia Z5 Premium Android Development] Joel16:
Change-logs:

2019-12-12

- Initial Release

2019-12-23

- Updated security patch to December.

- Fix some missing proprietary blobs. (camera, nfc and qti-iop)

- Add support for aanc tuning mixer controls.

- Updated outdated config files to the ones from 32.4.A.1.54.

- SD Card detection fix on dual sim devices by kv123.

2020-02-16

- Updated Android security patches to Feb 2020.

2020-04-14

- Updated Android security patches to March 2020.

- arm: DT: Satsuki: Lower backlight init value

2020-05-07

- Updated Android security patches to April 2020.

- Fixed NFC toggle.

- Fixed WiFi tethering.

- Fixed SD card not being accessible on dual-sim variants.