yashsingh1/xdaforums huggingface dataset:
[Android Q&A, Help & Troubleshooting] eleotk:
XP8800 imga is huge, you can extract all files directly from this file,

1. First you need to install QPST, and then confirm that there are 2 files in the QPST installation directory.

D:\Program Files (x86)\Qualcomm\QPST\bin

Fhloader.exe

QSaharaServer.exe

1

2

2. The device needs to switch to port 9008, and then execute the following command. The last COM4 is the corresponding port number of 9008.

QSaharaServer.exe -s 13:prog_emmc_ufs_firehose_Sdm660_ddr.elf -p \\.\COM4

D:\Program Files (x86)\Qualcomm\QPST\bin>QSaharaServer.exe -s 13:prog_emmc_ufs_firehose_Sdm660_ddr.elf -p \\.\COM4

3.dump terminal EMMC partition

Fh_loader.exe --memoryname=emmc --sendxml=rawprogram0.xml --convertprogram2read --port=\\.\COM4

1

If successful, there will be the following tips:

D:\Program Files (x86)\Qualcomm\QPST\bin>fh_loader.exe --memoryname=emmc --sendxml=rawprogram0_unsparse.xml --convertprogram2read --port=\\.\COM4

in addition

XP5S XP8800 link no resources available
[Android Q&A, Help & Troubleshooting] smokeyou:
If you were to pull the image it would not be wise to separate it into so many segments. That XML is supposed to go with a full image provided by Sonim to be applied by the XP8 flash tool. I was hoping you had the rest of this otherwise I would not recommend using that XML for backup or restore operations.

That ELF file is exactly what people were looking for though!!

Being said.. I did write a wrapper to help generate accurate xml files based on live GPT data. I'll get this posted to the main thread shortly as some of this conflicting data pulled from Chinese forums seems to be a primary issue when trying to understand requirements.
[Android Q&A, Help & Troubleshooting] eleotk:
XP8800 image I only have the Images_XP8A_USC-userdebug version here.
[Android Q&A, Help & Troubleshooting] smokeyou:
Dude no way.. Can you send me this? I modified the XP8 flash tool to eliminate server authentication - we can apply this with ease!

Userdebug is really the right way to achieve root :).

Magisk is cool depending on the case however I would personally rather keep su isolated to adb root. I managed to compile a partially working gsi-pie userdebug image however I couldn't manage to get the radio working so I abandoned that effort. This image of yours may just help to solve many things!!
[Android Q&A, Help & Troubleshooting] eleotk:
This is an old version link https://drive.google.com/file/d/1vTuis5V9vaIDqaazIUSucPRXqS2-RyOC/view

---------- Post added at 12:17 PM ---------- Previous post was at 12:12 PM ----------

XP5S image can be uploaded to google disk?BT Download No resources
[Android Q&A, Help & Troubleshooting] smokeyou:
It hasn't seeded out yet but should be available. My wimpy google drive is full. It should go once the servers have bandwidth. If not ill have to figure out another way to send it over after work here.

This is a great file set! I'll plan to review in greater detail as I believe this will allow others to unlock the bootloader. Unlocking is not not really required nor useful currently however it may help with some of the gsi efforts.

Sonim included a handy backdoor. If you have the XP8 flash tool for this file set then we can try the following..

1. Prevent server communication by adding a hosts file entry

sonimexperiance.com 127.0.0.1

2. Create testlogin.txt within the XP8 flash tool install directory

{"status":"success","message":"1 successfully logged in","name":"1","activetabs":["download_tool","qcn_backup_restore"],"carriers":["00"],"multi_carrier":true,"phone_model":["8A"],"edl_user":"Yes","emc":"Yes","carrier_list":{"00":"Generic","10":"AT&T","11":"Bell","12":"Telus","13":"Sasktel","14":"Harris","15":"Verizon","16":"Ecom","17":"NAM","18":"Rogers","19":"T-Mobile","20":"EU Generic","21":"MSI","22":"CISCO","23":"NAM Public Safety","24":"Vodafone Global","25":"Orange","26":"Southern Linc","27":"OPTIO","28":"India","29":"SPRINT","30":"JVCK","31":"AUSTRALIA","32":"ACG","33":"CSPHIRE","34":"US-Cellular","multi_carrier":"Multi Carrier"}}

3. Launch flash tool and login with Username=1 / Password=1

The flashtool seems to be a UI front end for invoking methods defined within Qualcomm library's. It's very basic essentially so I have been avoiding it until now but it may be a good option for this debug image so I wanted to share what I know so far.
[Android Q&A, Help & Troubleshooting] eleotk:
SONIM xp8 upgrade tool I am always looking for

XP8 image download tool QPST can be used directly, I have been using QPST to download to XP5 XP7 XP8

Hi XP5S XP8800 link no resources available

QPST can also unlock mobile radio via QCN

The segmented graphics that are pulled out can be generated by XML after a total file is parsed and then modified by the decomposition tool. After the new file is segmented by XML, QPST can be downloaded.

Can XP5S elf XML four files be uploaded?
[Android Q&A, Help & Troubleshooting] eleotk:
Did that XP5s download ever kick off for you?[/QUOTE]

XP5s link still has no resources for one day
[Android Q&A, Help & Troubleshooting] eleotk:
XP5s link still has no resources for one day

QFlashTool.9.1.6 https://www.mediafire.com/file/lsce3h0i6rta8h8/QFlashTool.9.1.6.rar/file
[Android Q&A, Help & Troubleshooting] smokeyou:
You are just full of treasures for the community :).

I'll gladly share images and even my own janky c# but I get hesitant when it comes to this stuff.. Greatly appreciate you helping to cover the gaps!
[Android Q&A, Help & Troubleshooting] eleotk:
The download is successful, it is not the image I want. I used to have an XP5S image and the data is lost.
[Android Q&A, Help & Troubleshooting] smokeyou:
That is a full XP5s system image.. If you were looking for a debug image then I'm not sure if I can help unfortunately.
[Android Q&A, Help & Troubleshooting] eleotk:
Yes, full image, Firehose = prog_emmc_firehose_8917_ddr.mbn

Program = rawprogram0_unsparse_upgrade.xml

Patch = patch0.xml
[Android Q&A, Help & Troubleshooting] jochu38@hotmail.com:
What makes this userdebug version so special? With it being AT&T, would most of its contents still work with my telus version?
[Android Q&A, Help & Troubleshooting] smokeyou:
It's not really all that special given the age as it's a very early 7.1 release. Generally the idea is native SU binary, verity control, & unlock capability.. This debug image is not AT&T though, it's USC that appears to be a generic US Carrier image.

I believe any carrier firmware will work since the modem implementation is probably about the same aside from branding. A Telus image will likely include Telus apps that may be desirable if you have Telus service. Or in other words it should work but you likely have a better experience currently.
[Android Q&A, Help & Troubleshooting] albert.r:
userdebug firmware for Xp8

I would also appreciate a userdebug firmware build for Xp8. Please share it if you can.

-albertr
[Android Q&A, Help & Troubleshooting] eleotk:
Unlock fastboot

Step 1, open the developer mode

Go to “Settings” → “About Phone” and click “Version Number” 7 times to open Developer mode.

Step 2, open oemlock

Go to “Settings” → “Other Settings” → “Developer Mode” and open the OEM to unlock;

3 START mode

fastboot flashing unlock
[Android Q&A, Help & Troubleshooting] albert.r:
[MENTION=5803027]eleotk[/MENTION], thanks! When I try to download it from mega.nz, it ask for a decryption key (screenshot attached)...

Do you know what is it?

Thanks,

-albertr
[Android Q&A, Help & Troubleshooting] eleotk:
https://mega.nz/#!anZmXCAZ!fEuFYIXOAFTRV032oUfJK1lXIwLTU4g8Siqg0ECSHxg
[Android Q&A, Help & Troubleshooting] albert.r:
Thanks again! Is it a userdebug build or just a regular build for AT&T?

-albertr
[Android Q&A, Help & Troubleshooting] eleotk:
AT&T
[Android Q&A, Help & Troubleshooting] albert.r:
[MENTION=5803027]eleotk[/MENTION],

Thanks, however I'm looking for the userdebug build (for AT&T carrier or any other GSM carriers in North America region).

If you can share it, it would be much appreciated!

-albertr
[Android Q&A, Help & Troubleshooting] albert.r:
Since userdebug XP8 firmware build is out in the wild and floating around, I would appreciate if anyone can share it with me. [MENTION=1444903]smokeyou[/MENTION], I assume you have it already (hint, hint)?

-albertr
[Android Q&A, Help & Troubleshooting] eleotk:
https://mega.nz/#!qjBxEC5L!9THbhbe7m2lYDnW6GTPKeEbrQpkAOsQlCF5miIhgkyE
[Android Q&A, Help & Troubleshooting] albert.r:
Thanks man! Appreciate it and I owe you a beer ;)

-albertr
[Android Q&A, Help & Troubleshooting] smokeyou:
Looks like he beat me to it.

As previously confirmed, this is not AT&T..

Also does not include DM-Verity (this makes it hard to switch back to AT&T / other current firmware).

It's good for research but probably not something we would want to use in a day to day situation. The security patch level is far outdated and will never update on the Debug image. We gain the value of having fastboot unlocked but that does not really do much for us on the XP8 currently anyways.

It would probably be better to flash only ABL + XBL that will allow the same unlock method on a current carrier firmware variant. This comes with a risk though because any future OTA's could brick the device.

And he edited his first post.. I feel horrible for anyone who see's page 1 here looking for root and ends up with this debug image :(.. Take caution as I will not be able to help you when you brick your device or end up stuck on 7.1 firmware.

Edit.. So the post he edited on page 1 is ASG.. That other post later in the thread is USC. Beyond assumptions I cant say what these acronyms mean but I can at least definitively say they are not AT&T. Full carrier code listing below.

None = 0,
ATT = 10, // 0x0000000A
Bell = 11, // 0x0000000B
Telus = 12, // 0x0000000C
Sasktel = 13, // 0x0000000D
Harris = 14, // 0x0000000E
Verizon = 15, // 0x0000000F
Ecom = 16, // 0x00000010
NAM = 17, // 0x00000011
Rogers = 18, // 0x00000012
T_Mobile = 19, // 0x00000013
EU_Generic = 20, // 0x00000014
MSI = 21, // 0x00000015
CISCO = 22, // 0x00000016
NAM_Public_Safety = 23, // 0x00000017
Vodafone_Global = 24, // 0x00000018
Orange = 25, // 0x00000019
Southern_Linc = 26, // 0x0000001A
OPTIO = 27, // 0x0000001B
India = 28, // 0x0000001C
SPRINT = 29, // 0x0000001D
JVCK = 30, // 0x0000001E
AUS = 31, // 0x0000001F
ACG = 32, // 0x00000020
CSPIRE = 33, // 0x00000021
USC = 34, // 0x00000022
SB = 35, // 0x00000023
Multi = 99, // 0x00000063

8A.0.0-00-7.1.1-32.00.12 = ACG

8A.0.0-00-7.1.1-34.00.10 = USC

8A.0.5-11-8.1.0-10.54.00 = ATT
[Android Q&A, Help & Troubleshooting] eleotk:
ACG-userdebug

8A.0.0-00-7.1.1-32.00.12

ATT-userdebug

8A.0.0-00-7.1.1-10.00.10

USC-userdebug

8A.0.0-00-7.1.1-34.00.10

Att version(extract)

8A.0.5-11-8.1.0-10.54.00
[Android Q&A, Help & Troubleshooting] albert.r:
Thanks for sharing AT&T userdebug build, it's much appreciated! I'm on GSM AT&T here in the USA and I think both US Cellular (USC) and Associated Carrier Group (ACG) are CDMA, not sure if they have different modem code/parameters. I'll try to flash AT&T userdebug this weekend.

-albertr
[Android Q&A, Help & Troubleshooting] eleotk:
It is not recommended to refresh the userdebug version. This version is older. You can use the EIF file to completely back up your original version. You can refresh the QCN.
[Android Q&A, Help & Troubleshooting] eleotk:
The thread is closed,
[Android Q&A, Help & Troubleshooting] smokeyou:
Hey guys, been a while and I'm glad to share some updates with the community!

Main post here has been updated according to the progress made in the previous posts. Much thanks to everyone for providing early debug images, files, and knowledge!

Updates

- Torrent file hosting moved to Android FIle Host

- Current 8.1.0 AT&T Debug image uploaded

- 8.1.0 Debug image verified to retain dm-verity! At least on current AT&T builds.

- Additional factory images uploaded

- All basic flash tools, elf files, drivers, and GPTConsole executable uploaded

- More images will be uploaded in the following days. Ran out of time to upload everything tonight.

Full Android File Host Repository - Here

We continue to welcome new images for the file collection.
[Android Q&A, Help & Troubleshooting] smokeyou:
Are you getting the boot warning during power up? Does the Magisk app show an option to flash directly now?

I do recall having a couple extra steps within the Magisk app after flashing however it prompted me and seemed automated.

It looks like you applied everything correctly though so we can't far off.
[Android Q&A, Help & Troubleshooting] uberdude420:
i get nothing on boot. ive moved magisk to inernal storage off of sd card and granted all permissions.. ive re compiled the boot after doing that and re flashed it aswell. still just booting normal after that.. also majisk is just the same as efore. same prompts . no root shows it as not being installed and only prompts to download zip or patch file
[Android Q&A, Help & Troubleshooting] smokeyou:
I wonder if your active on slot b then possibly. Can we check? We can find out with fastboot getvar all.
[Android Q&A, Help & Troubleshooting] uberdude420:
my bootloader is locked and i have no fastboot
[Android Q&A, Help & Troubleshooting] smokeyou:
You have fastboot. It's just flashing that's locked. Power + Vol Down should get you into the Fastboot menu.

getvar works in either a locked or unlocked state.
[Android Q&A, Help & Troubleshooting] uberdude420:
i dont seem to have it.. even adb reboot fastboot... just reboots my device. unless there is a way to do it in terminal on the phone itself ... adb reboot recovery gives me what looks like download mode but no selection menu that should be there :/ im wondering if i did something before while trying to root this using other methods .. i dont remember doing anything pemanent
[Android Q&A, Help & Troubleshooting] smokeyou:
That seems odd. Your a step ahead of me as adb reboot fastboot would have been the other method I could suggest :).

What build are you running currently?

We can try to patch boot_b as well just to see. For that we can change the XML data as reflected below.

<program filename="boot_b.img" label="boot_b" num_partition_sectors="131072" partofsingleimage="false" physical_partition_number="0" readbackverify="false" sparse="false" start_sector="393216" file_sector_offset="0" SECTOR_SIZE_IN_BYTES="512"/>
[Android Q&A, Help & Troubleshooting] smokeyou:
You got it! Yeah after the pull we need to patch and re-flash. Removing --convertprogram2read from the command line.
[Android Q&A, Help & Troubleshooting] smokeyou:
That looks like we re-flashed the original boot_b?
[Android Q&A, Help & Troubleshooting] smokeyou:
I thought we had validated the Telus images. Or we did have 1 success reported however I'm not sure what build version the guy was running.

This seems to be an issue on the return side. If Telus used a different GPT layout for example then Magisk manager would fail patching - so we know it's a valid image at least.

We can try to erase boot_a & boot_b before flash back. If that fails I would probably ask if you could send over an image backup for testing.

<?xml version="1.0"?>
<data>
<erase SECTOR_SIZE_IN_BYTES="512" num_partition_sectors="131072" start_sector="262144" physical_partition_number="0" label="boot_a"/>
<erase SECTOR_SIZE_IN_BYTES="512" num_partition_sectors="131072" start_sector="393216" physical_partition_number="0" label="boot_b"/>
</data>
[Android Q&A, Help & Troubleshooting] eleotk:
No XP5S Debug Images? XP8 battery baffle is too broken
[Android Q&A, Help & Troubleshooting] smokeyou:
I have not seen any debug images for the XP5s myself. Magisk patching works for a root option but that's all I have found so far.
[Android Q&A, Help & Troubleshooting] albert.r:
[MENTION=1444903]smokeyou[/MENTION], thank you for sharing AT&T android 8.1.0 userdebug build. I have my phone now flashed with AT&T 7.1.1 userdebug build and testing it. Android 8.1.0 gave me alot of grieve, since many customizations I got used to don't work anymore and developers don;t have any desire to port them to Oreo.

-albertr
[Android Q&A, Help & Troubleshooting] smokeyou:
There we go!! I haven't done much testing on that early AT&T image so this is good news.

I wont try to talk you out of running on such an old security patch level :). It's good that your making a contentious decision between vulnerabilities and customization even if not recommended.
[Android Q&A, Help & Troubleshooting] albert.r:
So what would be a "good" way to install SuperSU on top of userdebug build?

Should I use magisk to massage the boot image and then flash it back via fastboot?

adb reboot bootloader

fastboot flash boot magisk_patched.img

fastboot reboot

I'm on 7.1.1, so I don't think I have dual boot partitions...

-albertr
[Android Q&A, Help & Troubleshooting] smokeyou:
The tested way is essentially the same as applying magisk to a standard user image. It feels like we would give up main the benefits of having userdebug though because userdebug contains native su binaries tied to adb root.

Fastboot may work also if your unlocked. I personally had mixed results where some would flash and some would fail. You can also move back to a user build and retain the unlock.
[Android Q&A, Help & Troubleshooting] uberdude420:
well it flashed.... but.......

now i seem to be hanging on loading the firehose to re install boots :/ c:\flashtools>QSaharaServer.exe -p \\.\COM11 -s 13:prog_emmc_ufs_firehose_Sdm660_ddr.elf

Binary build date: Jul 28 2017 @ 18:09:01

QSAHARASERVER CALLED LIKE THIS: 'QSaharaServer.ex'Current working dir: c:\flashtools

Sahara mappings:

2: amss.mbn

6: apps.mbn

8: dsp1.mbn

10: dbl.mbn

11: osbl.mbn

12: dsp2.mbn

16: efs1.mbn

17: efs2.mbn

20: efs3.mbn

21: sbl1.mbn

22: sbl2.mbn

23: rpm.mbn

25: tz.mbn

28: dsp3.mbn

29: acdb.mbn

30: wdt.mbn

31: mba.mbn

13: prog_emmc_ufs_firehose_Sdm660_ddr.elf

23:45:22: ERROR: function: sahara_rx_data:237 Unable to read packet header. Only read 0 bytes.

23:45:22: ERROR: function: sahara_main:924 Sahara protocol error

23:45:22: ERROR: function: main:303 Uploading Image using Sahara protocol failed

no boot :(

edit

i got it restored from my origonal full backup... should i send you that? if so wich img files are needed or do you need my whole backup folder zipped?

also i tried flashing the magisk boot. one at a time on each partition... both times i came up un able to boot with a boot warning of system being corrupted and nothing passed it. :(
[Android Q&A, Help & Troubleshooting] smokeyou:
Pretty much everything aside from userdata. The files produced are large as they include all free space however they should zip up to a fairly reasonable size.

Typically we would provide all XML's in a single command or incrementally without rebooting until all actions are complete. For example "--sendxml=erase.xml,rawprogram0.xml".

Generally speaking it's not a good idea to leave EDL without having all critical partitions populated. I'm glad we were able to restore!!
[Android Q&A, Help & Troubleshooting] Profy_X:
smokeyou coud you make a video tutorial for rooting xp8 will be very appreciate
[Android Q&A, Help & Troubleshooting] uberdude420:
following the edl backup. tutorial in the threads here.. i dont have a user data. just alot of img files and xmls and such in my flashtools folder as it was my working directory

should i zip and send that folder? or is there another backup method i should use eg adb backup... if so.. any chance you could send the proper command for the right type of bakup lol.. im still noobish with the terminal. :p
[Android Q&A, Help & Troubleshooting] smokeyou:
Hey there Profy_X!

That's a tough one for me. I'm just a developer - Not even a good developer :).

I wanted to share root with others since the topic was pending on XDA for about a year when I happened to randomly acquire a couple used XP8's that were included in the same box with an S660 dev kit I got from a local auction. Rooting the XP8 was really a side effect as I needed something to do one night while waiting for a GSI build (for a different device) to compile.

Typically I don't encourage blindly modifying devices though. Research and education is a great thing however video tutorials usually leave out critical points allowing for modifications without holding a valid understanding of the greater topic including any underlying requirements. When it comes to content creation around rooting the focus is primarily on the aspect of easily replicating steps as this is good way to generate traffic(/revenue). The down side is that only leads to more people bricking their device and that would make me feel pretty horrible.

I would be supportive if someone else wanted to do this however I would not want to be the person to do it.

Perfect!! If you copied it from me then it should exclude user data already yeah. Google drive or anything that works for you should be fine for transfer. The image files are the main items needed for testing but feel free to capture the whole folder as that is probably easier then sifting through all the files.

There is a lot of images that are actually empty however it can be difficult to sift through them to get everything sorted. If it gave you all the .img files then it sounds like you gave it the right command already :).
[Android Q&A, Help & Troubleshooting] uberdude420:
dude to me... your a top notch developer lol... nobody has done **** with this phone...and for a guy like me.. its an ultimate phone.. the only thing it lacked was root for a few things. lol. love my viper audio... drive droid.. a few other goodies and you my friend.. are the one finally getting a ball rolling on this phone lol. so again.. ty .
[Android Q&A, Help & Troubleshooting] Goofee691:
So I got my XP8 from ebay with android 7 still on it. Today I managed to get a ATT sim(its the ATT branded phone) and updated it to android 8. Before getting the sim I tried to update via android recovery and the downloaded OTA updates but android recovery would fail to mount a partition so it would not update via sideload or sd card.

I had hoped that the newer version of android would actually allow both sim cards to function correctly but I was wrong.

I also tried to use the backup method before getting the ATT sim card but it was also failing, I was able to backup just the boot image but not the full system image.

Before I start trying to dig into the userdebug images does anyone know if they offer the true dual standby of the sim slots as it appears maybe only the european version supports?

I say maybe as looking at all the user guides the Euro Generic user guide is the only one to reference 2 sims active and shows a VoLTE symbol on page 17

Page 15 also indicates the settings page I would see on my LG v20 to select sim cards

I use T-mobile as my primary carrier but with the wal mart plan that only gives you 100min of voice, I also have xfinity mobile which this phone also seems to support as it actually connected to the network unlike on LG V20 dual sim phone. My ultimate goal is to setup this phone to use T-mobile for data and xfinity/verizon for voice.
[Android Q&A, Help & Troubleshooting] CuongDang:
Hi smokeyou

I have just got an AT&T Sonim XP8, I'm not live in US.

I followed your bellow guide and my Sonim can start XP8A_ATT_user_8A.0.5-11-8.1.0-10.54.00

But I am having a big problem now, the mobile network does not work anymore. *#06# doesn't work => Phone has stopped and It doesn't recognize my sim. Android OS cant read IMEI!

I don't know what to do next! could you help me?