yashsingh1/xdaforums huggingface dataset:
[Android Q&A, Help & Troubleshooting] thenatti:
yes with a imei editor and used sonim software updater to push imei both are working to my knowledge but havent tested both slots since i only have one sim card
[Android Q&A, Help & Troubleshooting] thenatti:
has tested verizon android 10 doesnt accpet TWRP from research i think they changed the location of the recovery which no longer sits in boot.img when i flash i get android corrupted wont boot and the programs ive used to port twrp to the boot image fail on recompiling
[Android Q&A, Help & Troubleshooting] thenatti:
do you have the raw program0 file for this and the patch0 im trying to port twrp to android 10 not having success with VZW build even tho it states oem unlock in settings bootloader still locked , fastboot unlock commands fail
[Android Q&A, Help & Troubleshooting] glhydroco:
I do not have the patch0 as I pulled this backup with the instructions on the first page. There should be a rawprogram0.xml file in the package but NO patch0. I am not sure how to get / create that. I can confirm that this does work for ATT phones but the phone needs to be unlocked from the network.
[Android Q&A, Help & Troubleshooting] thenatti:
both phones are unlocked it for some reason bootloops on both phones , but it shows my bootloader unlock even tho all the commands fail
[Android Q&A, Help & Troubleshooting] glhydroco:
I have had some issues with the fastboot commands failing, I resolved this issue with a different usb cable. as for the "unlocked" I am referencing the ATT network lock pin not the bootloader lock, I have been able to do this carrier changing with the bootloader locked and unlocked using QFIL.
[Android Q&A, Help & Troubleshooting] thenatti:
im following , both phones are unlocked the VZW android 10 claims the bootloader is locked even tho its unlocked on both phones im working on porting a android 10 twrp
[Android Q&A, Help & Troubleshooting] thenatti:
We have success just have to figure out how to edit the mount points but I have tarp 3.7 up and running , still can’t flash system via fast boot working on doing so with tarp so we have a chance at running at least android Q GSI’s
[Android Q&A, Help & Troubleshooting] thenatti:
0mb is letting me know it’s not mounting properly will compare the original Twrp to this one
[Android Q&A, Help & Troubleshooting] thenatti:
does anyone have another android 10 variant ? to test the recovery works ( flashes/mounts system ) but wont boot on VZW build ( gives the cant be trusted phone wont boot error ) , it boots on the canada bell but never goes past recovery
[Android Q&A, Help & Troubleshooting] thenatti:
bricked flashing bell canada removed ( 0's ) from the end of files can only boot 7.1.1 lol this phone is weird af trying to install VZW keeps giving device is corrupted cant be trusted errror
[Android Q&A, Help & Troubleshooting] thenatti:
this saved my life ( so discovery ) if your phone bootloops after flashing load this - tested with the VZW android 10 Build - currently flashing android 8.1 userdebug will upload the twrp 3.7 build later have to figure out how to add the a/b slot option , but the OG Twrp ive posted works fine will add some fixes like enabling adb,mtp
[Android Q&A, Help & Troubleshooting] thenatti:
Im working on a Flashable.Zip via Twrp created the rom in Super R's Kitchen as a test no modifications but need someone to help me fix the updater-script ( keeps throwing error 7 ) some mount point flags can upload the zip for testing if anyone has resources and knowledge
[Android Q&A, Help & Troubleshooting] thenatti:
i think you made a post a while back about compiling android 9 for this devices , could you tell me more about how you accomplished this and what do i need tool wise if so i might be able to assist in porting roms i have ubuntu on my macbook and windows 10 on my alienware , can send you the flashable zip i created i couldnt get passed an error 7 but the structure seemed like it would pass TWRP script check
[Android Q&A, Help & Troubleshooting] eleotk:
Four. Qualcomm QCN

1. The most original qcn file of the project is to select a RF card driver that is close to the project motherboard from the Qualcomm original code (similar GPIO configuration and frequency band configuration), and use the QCN corresponding to the RF card driver as the basic QCN file. After adding the static radio frequency NV item and frequency band configuration, it can be used as a QCN configuration file, and the corresponding NV modification of the subsequent software can be modified through QXDM and then backed up from the mobile phone to QCN.

2. QCN tar package production process:

2.1 First define and open the macro FEATURE_EFS_ENABLE_FACTORY_IMAGE_SECURITY_HOLE in the modem code and compile the modem.

2.2 Take a machine and use the fastboot erase command to erase the existing qnc data in the mobile phone, use the QPST tool to burn the prepared QCN file, connect the mobile phone to the computer to open the diag port, and enter the modem side modem_proc/core/storage on the PC command terminal In the /tools directory, execute the perl efsreadimage.pl -z command, which will generate fs_image.tar.gz in the current directory, and copy fs_image.tar.gz to the modem_proc/core/storage/tools/qdst directory, in linux Execute python QDSTMBN.py fs_image.tar.gz in the environment. After completion, the fs_image.tar.gz.mbn file will be generated in the same directory.

2.3 Create a new folder create_efs locally on the PC side, and put the modem_proc\build\ms\bin\AAAAANAZ\efs_image_meta.bin file, fs_image.tar.gz.mbn file and \modem_proc\core\bsp\efs_image_header\tools\ on the modem side Copy all files to create_efs, execute efs_image_create.py efs_image_meta.bin fs_image.tar.gz.mbn in the windows command window, and the final QCN Tar package fs_image.tar.gz.mbn.img file will be generated in this directory if the command is executed successfully .

3. After executing the modem image file unpacking script when compiling the software version, add the prepared QCN tar package fs_image.tar.gz.mbn.img to the fsg partition in the generated download partition file rawprogram0.xml, so that Burn the QCN file by downloading the software.
[Android Q&A, Help & Troubleshooting] eleotk:
How to fix IMEI,QCN error causes lock CDMA network how to fix, Where is the ,IMEI editor
[Android Q&A, Help & Troubleshooting] Xdadhutsc:
Hi, this thread has been super helpful so far. I am working on rooting my XP5s via EDL following the instructions from this thread. I have an ATT and a Verizon version both came with Android 8.

I am always getting stuck after starting the Sahara server using the instructions on page 1.

I tried so many things

- Use an old PC with USB2

- Try with the ATT and the Verizon device

- Use different USB cables (they all work with ADB so I think they are fine)

- Enable OEM unlocking in the developer settings

- Running QSahara as admin

- Make sure there's no spaces in the path to QSahara

- Disable the internet connection

- Use different versions of Windows

- Disable defender/firewall

- Use different versions of the Qualcomm driver

- Find an alternative version of prog_emmc_firehose_8920.mbn (I found two through and they have the same md5)

- Try with and without battery in the phone

- Try to go into edl through adb reboot edl or through pressing volume buttons and power

- Start the QSahara program right when the led starts blinking red

- Use the open source variant here: https://github.com/bkerler/edl (stuck after uploading binary as well)

I think I am missing something. Or maybe I do have the wrong loader. Does anybody have an idea what else I could try? Thanks.

loader md5
[Android Q&A, Help & Troubleshooting] Xdadhutsc:
Thank you so much @eleot!. I had the wrong loader. Works without an issue now. I am ready to brick some devices :)
[Android Q&A, Help & Troubleshooting] eleotk:
Do you have XP5 with dual card working mode?
[Android Q&A, Help & Troubleshooting] Xdadhutsc:
Not yet. But I will try to get that working and let you know.
[Android Q&A, Help & Troubleshooting] Xombiex:
What do You want to do on your device bro?
[Android Q&A, Help & Troubleshooting] Xdadhutsc:
I want to root it to as I have a device that has a mdm service running that can't be removed without root. Also I'd like to see what I can enable in the build.props with root. I have a verizon and ATT device. The ATT has hotspot disabled, the verizon one wifi calling and VOLTE. Both of them have the 2nd sim disabled.
[Android Q&A, Help & Troubleshooting] Xdadhutsc:
I was able to extract the boot image. I patched it with the Magisk Android app. Interestingly the image is quite a bit smaller after applying Magisk. I assume Magisk applies more compression. I decide to first erease the partition and then apply the image. When I do that I end up in a boot loop.

1) erase boot with the xml below

<?xml version="1.0"?>
<data>
<erase SECTOR_SIZE_IN_BYTES="512" file_sector_offset="0" start_sector="790528" sparse="false" readbackverify="false" physical_partition_number="0" partofsingleimage="false" num_partition_sectors="131072" label="boot" />
</data>

2) flash Magisk boot image with the image below

<?xml version="1.0"?>
<data>
<program SECTOR_SIZE_IN_BYTES="512" file_sector_offset="0" start_sector="790528" sparse="false" readbackverify="false" physical_partition_number="0" partofsingleimage="false" num_partition_sectors="131072" label="boot" filename="magisk_patched-25200_xGJA0.img" />
</data>

3) boot loop

4) flash back the original boot image

5) phone starts up

Does anybody see what I am doing wrong?

(XP5800)
[Android Q&A, Help & Troubleshooting] Xdadhutsc:
Looks like I found my problem. Have to check "Preserve AVB 2.0/dm-verity" when patching the boot image with Magisk.
[Android Q&A, Help & Troubleshooting] eleotk:
Using Magisk-v23.0
[Android Q&A, Help & Troubleshooting] Xdadhutsc:
APPS​

I was able to remove apps that automatically install on startup by removing the app installer. I had to remove the system app with the terminal debloater Magisk module (https://github.com/Magisk-Modules-Repo/terminal_debloater). There was a user installed version as well so I deleted that too. After that I could uninstall other apps.

VoLTE​

I also tried to change some build.props.

persist.vendor.radio.voice_on_lte=1
persist.vendor.radio.lte_vrte_ltd=1

Seems to gives me an option to enable video in calls. VoLTE seems to be working on Verizon with that option as I also had a HD indication on calls.

Dual SIM​

persist.radio.multisim.config=dsds

I changed the multisim build props config to "dsds" with Magisk (https://github.com/Magisk-Modules-Repo/MagiskHidePropsConf). It did not work. It even disabled some options on the first SIM. I am not sure if "dsds" is the wrong option to enable dual SIM.

(XP5800)
[Android Q&A, Help & Troubleshooting] eleotk:
persist.radio.multisim.config=dsds or persist.radio.multisim.config=dsda No service after modification
[Android Q&A, Help & Troubleshooting] Xdadhutsc:
Yea, it makes sense. The modem firmware probably does not support dual SIM. That would make sense as there's no provider in the US that sells those phones with dual SIM enabled. I won't flash any EU modem images as I am for sure going to break something else.
[Android Q&A, Help & Troubleshooting] eleotk:
do you have a eu modem image，I want to refresh and try
[Android Q&A, Help & Troubleshooting] Xdadhutsc:
No, I don't have an eu image.
[Android Q&A, Help & Troubleshooting] eleotk:
Dual SIM​
[Android Q&A, Help & Troubleshooting] eleotk:
Does anyone know the Unlock Bootloader command, this is the picture I found on the Internet
[Android Q&A, Help & Troubleshooting] glhydroco:
fastboot flashing unlock
[Android Q&A, Help & Troubleshooting] eleotk:
Turn on OEM unlocking

Unlock failed

...

FAILED (remote: unknown command)

finished. total time: 0.004s
[Android Q&A, Help & Troubleshooting] glhydroco:
I have had this happen and changed usb cables and it went through.
[Android Q&A, Help & Troubleshooting] eleotk:
changed usb cables

fastboot flashing unlock

FAILED (remote: 'unknown command')

Finished. Total time: 0.000s

fastboot version 28.0.1-4986621
[Android Q&A, Help & Troubleshooting] glhydroco:
so after looking into this issue I can confirm that the unlocking of the bootloader for me can only be done on the ATT dubug image. I have attached a screenshot of the fastboot. This is all done with adb fastboot minimal and the versions are shown in the image. I am not sure why this does not work with an other firmware someone with more knowledge regarding this can chime in.
[Android Q&A, Help & Troubleshooting] albert.r:
Thanks, [MENTION=1444903]smokeyou[/MENTION]. I guess it looks like Sonim decided to not prevent XP8800 from booting when secure boot chain fails verification. Interesting....

-albertr
[Android Q&A, Help & Troubleshooting] smokeyou:
Or a better way to look at it is that Magisk appears to falls under either embedded or user-settable root of trust. I'm sure Sonim just followed whatever documentation Qualcomm gave them as this is all pretty much the same as anything else.

https://source.android.com/security/verifiedboot/boot-flow
[Android Q&A, Help & Troubleshooting] smokeyou:
AT&T at least. Hopefully others as well?

Possibly related.. Systems images, OTA files, and other minor updates have been applied to the main post.
[Android Q&A, Help & Troubleshooting] jochu38@hotmail.com:
Im on Telus. Phone says an update is available, Telus says there isn't one
[Android Q&A, Help & Troubleshooting] albert.r:
[MENTION=1444903]smokeyou[/MENTION], how can I boot XP8 into EDL mode in case it goes into boot loop or if I'll have to pull out its battery? Is there any hardware key combination to cold boot it right into EDL mode? (I'm only aware of `adb reboot edl` command, but that requires the phone to be fully operational).

---------- Post added at 12:17 PM ---------- Previous post was at 11:39 AM ----------

[MENTION=1444903]smokeyou[/MENTION], did you disable dm-verify after rooting your Xp8? Or magisk did it for you?

-albertr
[Android Q&A, Help & Troubleshooting] jochu38@hotmail.com:
Vol up vol down power
[Android Q&A, Help & Troubleshooting] albert.r:
I believe vol-up + vol-down + power will make it to boot into fastboot mode, no?

I'm looking for EDL mode.

-albertr
[Android Q&A, Help & Troubleshooting] smokeyou:
Vol Up + Vol Down + Power to enter eDL mode. Screen will flash Sonim briefly before going blank.

To disable dm-verity I just removed the default preservation option within Magisk manager. I haven't tested this on a locked bootloader though. I was meaning to but I haven't had time in the past few days.
[Android Q&A, Help & Troubleshooting] albert.r:
Great, thanks. How can I boot XP8 into fasboot (bootloader) mode with hardware key combination?

-albertr
[Android Q&A, Help & Troubleshooting] smokeyou:
If not Vol Up + Vol Down then 'adb reboot edl' should also be an option.
[Android Q&A, Help & Troubleshooting] albert.r:
I mean if there any hardware key combo to boot into fastboot mode? The mode where I can use fastboot cmd utility?

-albertr
[Android Q&A, Help & Troubleshooting] albert.r:
Ok, I bit the bullet and tried it. Flashing went fine, however after reboot I got stuck with a screen that says "To start Android, enter your password".

I din't have pin set up to unlock this phone, only had fingerprints and swipe. This screen doesn't show swipe pattern and fingerprint scanner doesn't seem to work either. Not sure if it's related to encryption, since this phone had its filesystem encrypted. BTW, I would rather prefer to not have filesystem encrypted, but I don't know how to turn it off. After every factory reset (and I've tried many), it was booting into recovery and was encrypting filesystem automatically. So, basically I have two questions:

1. Is there any was to turn off filesystem encryption on XP8? I don't care about any data on this phone, can wipe it clean if needed.

2. How I can get past this "To start Android, enter your password" screen? I guess I can get it into EDL mode and flash stock boot.img, but I'd rather prefer to have it rooted with Magisk.

If anyone has any ideas, let me know.

-albertr
[Android Q&A, Help & Troubleshooting] smokeyou:
I had this issue also under about the same scenario. Never set a boot password before and got a prompt after flashing.

To resolve we just need to boot into recovery (Vol Up + Power). At the "No command" screen hold power and tap vol up to access the full recovery menu. Then we just need to wipe the data partition.

I have a feeling that this would not be an issue if we set a password ahead of time. Same issue after applying an OTA also.
[Android Q&A, Help & Troubleshooting] albert.r:
Thanks, [MENTION=1444903]smokeyou[/MENTION]. Is there a way to force boot into recovery from EDL mode? Cold booting the phone with Vol-Up+Power buttons either bootloops after flashing that Nag screen or (if I release the buttons before and during the Nag screen) boots normally into Android...

It looks like that Nag screen is interfering with hardware buttons and doesn't allow to boot into recovery.

Of course, I can try to flash it back with original stock boot image, but I'd rather prefer to step forward rather than backward ;)

-albertr
[Android Q&A, Help & Troubleshooting] smokeyou:
Does fastboot work? We also have an option to switch to recovery from within FastBoot if you can access that (Vol Down + Power).

An alternative method would be to erase userdata from within eDL mode. This can be done with the XML data below.

<?xml version="1.0"?>
<data>
<erase SECTOR_SIZE_IN_BYTES="512" num_partition_sectors="96714719" start_sector="25427968" physical_partition_number="0" label="userdata"/>
</data>
[Android Q&A, Help & Troubleshooting] albert.r:
[MENTION=1444903]smokeyou[/MENTION], thanks again! Once this nasty nag screen about "different operating system" is flashing, I cannot seem to get into either recovery or fastboot mode. I think this screen is somehow interfering with hardware buttons. Maybe it's a timing race condition, I've tried many times with variable timing on pressing/releasing buttons, but all I was able to get to is either boot loop or normal boot.

So I did flash stock boot image back, and was able to get into Android and set up PIN. Also, every time I reset the phone or reformat userdata partition from recovery, XP8 boots into recovery and encrypts it back without asking me. So, now when stock image boots up, I can enter the PIN and get into Android. Flashed back magisk's patched boot image, and it says "Wrong PIN" (for the same PIN, obviously). I've tried Migisk advanced option when patching the boot image, but to no avail. So here's my thinking:

- to use Magisk patched boot image, it looks like we need to have unencrypted userdata partition on XP8. Now I do remember that with 7.1.1 installed originally, it was not encrypted. It's got encrypted somehow after I upgraded to 8.1.0. And I cannot figure out how to disable encryption. Tried many times, but it always encrypts it back after formatting. Any ideas?

-albertr
[Android Q&A, Help & Troubleshooting] smokeyou:
Seems odd to me. Or I have not seen that personally at least. I did run into the encryption issue but I was able to use recovery without a problem also - this was in either case with both a locked and unlocked bootloader. It was also the case when I applied the 8.0 OTA update without encryption before hand - same exact issue where after the OTA I had to clear data in recovery - so it seems to be common.

It's hardware backed encryption thats on by default even if you don't have a password set. It probably wouldn't be great practice to disable even if we had a way.

In your case it may be better to erase after flashing by sending a second xml as noted above.. Or if you have already reverted.. Just wipe the data partition before flashing next time you try.

It's really simple to access the menus. No timing tricks or anything. Just start from a fully off state then hold vol up, vol down, or vol up + down after tapping power. You technically do not even need to hold power, this is mostly a point to ensure your holding the other (volume buttons) during a power on operation.. It loads during ABL initialization ~1-3 seconds after power on.
[Android Q&A, Help & Troubleshooting] jochu38@hotmail.com:
Worked no probem on my Telus Xp8 at 7.1. Asked for a pin after flashing the patched boot, and my old one didnt work so I booted into Recovery, held power and tap vol up at no command screen and then entered Recovery Menu. Selected Factory Reset/wipe Data after i selected mount system option, screen flashed "encrypting phone", then restarted and loaded google account setup screen. reinstalled magisk manager apk and it recognized the patch was installed and allowed me to root. Currently no problems yet, except fail to ota upgrade to android 8, but before root it wouldnt even say i had an update available. Prob some telus bs.
[Android Q&A, Help & Troubleshooting] albert.r:
Thanks alot for your help! I figured out hardware keys, I guess I was holding power key for too long. Once I started to release it right after phone vibration on boot, I was able to get into recovery.

After erasing userdata partition, I can finally boot into Android without it asking me for a PIN ;)

I will keep encryption (not sure if it ever can be turned off on this phone) and dm-verify for now. Back to exploring this phone now...

Thank you again for the help!

-albertr
[Android Q&A, Help & Troubleshooting] smokeyou:
What's going on Telus updates I wonder yeah. The OTA's work on AT&T after rooting however you do loose root after moving from 7.1 to 8.0 as the boot.img needs to be re-patched.

If it's saying an update is available then I it should let you download and apply? Maybe if we catch a logcat during an update check so we can try to manually download the OTA from Telus servers?

I had a theory that Telus, SouthernLink, and possibly others used standard Sonim firmware but I could be wrong.. The best firmware to use would be from a device purchased from Sonim directly however there does not seem to be many of these in the wild unfortunately. What is the Build ID listed as under Telus?
[Android Q&A, Help & Troubleshooting] eleotk:
I think ATT dubug image bootloader allows unlocking, other user bootloaders do not support unlocking
[Android Q&A, Help & Troubleshooting] eleotk:
sonim xp3800 USERDEBUG image who has, I want to unlock bootloader by USERDEBUG image
[Android Q&A, Help & Troubleshooting] Xombiex:
i have solution but only with jtag
[Android Q&A, Help & Troubleshooting] Xombiex:
im looking for unlock software , sonim tool doesnt work to loggin , i have solution for unlock but need other software unbranded, i face this error on xp8 too and fix with and european firmware
[Android Q&A, Help & Troubleshooting] eleotk:
I need to unlock XP3800 unlock bootloader.Only the XP3 software can’t log in, but the XP8 software can log in. Unlocking requires an unlock code. I don’t know how to get it.。
[Android Q&A, Help & Troubleshooting] eleotk:
XP8A_ATT-userdebug-8A.0.5-11-8.1.0-10.54.00 Why OEM unlock is greyed out，ATT version needs to be reset after flashing
[Android Q&A, Help & Troubleshooting] eleotk:
After modifying the system of ROOT xp3800, the factory reset cannot be started. Does anyone know where the problem lies?
[Android Q&A, Help & Troubleshooting] eleotk:
XP8800 unlocked
[Android Q&A, Help & Troubleshooting] glhydroco:
How do you get the "unlock CE" 8 digits? Is this something that can be found within each phones firmware or is this only provided by phone carriers like ATT, Bell, Verizon. I have a locked phone that ATT will not provide code for and I would like to get it unlocked. I have the sim unlock tab on sonim software update tool but do not have unlock code. Please advice
[Android Q&A, Help & Troubleshooting] eleotk:
QPST back up your QCN and send it to me to help you find it
[Android Q&A, Help & Troubleshooting] glhydroco:
I have sent you both XQCN and QCN from QPST. Thanks for offering to help!!
[Android Q&A, Help & Troubleshooting] eleotk:
CK code receive letter​
[Android Q&A, Help & Troubleshooting] eleotk:
How to sign the modified system application. Preserving the original signature does not seem to be valid, verification using a third-party signature fails