Help needed, 'Your device has failed a routine safety check and will not boot.' after relocking BL

Help needed, 'Your device has failed a routine safety check and will not boot.' after relocking BL - LG V40 Questions & Answers

Hello everyone,
so I'll try and explain step by step what I, inexperienced guy, did, because from what I see I did absolutely everything to brick my V40... BUT maybe someone know what can I do to avoid having beautiful red paperweight.
I wanted to get HavocOS 3.5 on my phone. Until today I had stock Android 10, flashed by LGUP.
So in order to get the Havoc, I unlocked the bootloader the official way, thru LG developers site. Then I tried to get TWRP working and it might be the problem (more on that later). So, in order to get TWRP one of the steps was to fastboot boot TWRP-judypn-boot.img. I did that but didn't know that to do next (cause when I did it the phone booted normally and I didn't fully understood what now), so I abandoned the idea and just loaded the backup from LG Mobile Switch. But, then I realized that with having unlocked bootloader I won't be able to use google pay, so after some reading I found out that Magisk might be the answer (it wasn't) so I managed to get Magisk root on my device. When I found out that it didn't help with google pay i tried to do what others on forum warned me not to - RElock the bootloader using 'fastboot oem lock'. And now it has locked bootloader. But also now of course the phone is rather bricked in a way that: I can enter both fastboot mode and download mode but: trying fastboot something I get the info that it is not possible in Lock State, and when trying to just flash kdz of that stock android 10 that I started with, the LGUP says error 'error 0x6004 crossDL' and below that it mentions 'judypn_lao_eea>@judypn_lao_co' so probably that first fastbooted img now prevents it from beign flashed. So now I cannot fastboot or flash anything, and trying to boot the phone gives me error "Your device has failed a routine safety check and will not boot." and also sometimes, below 'All slots are unbootable'.
I know that I screw up multiple times, first time not recognizing that unlocking BL would cut off a function crucial for me, but is there a way to fix all this?

AnDevil said:
Hello everyone,
so I'll try and explain step by step what I, inexperienced guy, did, because from what I see I did absolutely everything to brick my V40... BUT maybe someone know what can I do to avoid having beautiful red paperweight.
I wanted to get HavocOS 3.5 on my phone. Until today I had stock Android 10, flashed by LGUP.
So in order to get the Havoc, I unlocked the bootloader the official way, thru L<brevity>imes, first time not recognizing that unlocking BL would cut off a function crucial for me, but is there a way to fix all this?
Click to expand...
Click to collapse
Sounds kind of messy. Two things to know; 1) u most certainly can have google pay working on v40 w/10. I just added it on my (orig at&t) korean 10 30e / rooted / magisk / twrp. And 2) u should never ever try to relock the bootloader unless you just flashed a stock kdz to the device (completely unmodified, don't even choose language when it boots).
So the prob is what to do now. I'd first try to use fastboot to switch slots and see if the other side boots? And if that doesn't work / achieve what you want, then use lgup with dll version 1.14 to do the 'cross flash' (the 1.16 version doesn't work for that). Be sure to do a part DL (if u do the crossflash), then do a refurbish with the same kdz just after the part DL (of course you let the part DL complete, just shut it off after it boots all the way), then do refurb.
Ideally, what are u trying to accomplish?
cheers

Well, for now I would want to have bootloader locked, stock Android 10 on there. I'm probably going to leave the modding cause of the mess I've made - especially that I don't have much free time to tinker with phone when things go bad (and also as You can see I don't have enough experience to do so).
Right, so back to the point. How do you switch slots in fastboot? If by 'fastboot set_active a' (or b), then the result is 'not possible in lock state'. And for the other part (with LGUP and crossflashing), can You provide some kind of idiot-proof tutorial for that? Which files should I download and try to flash on the phone?

OK, i *think* that I partly know what to do. Unlike You wrote, the 1.14 LGUP doesn't let me do anything with phone, saying that it needs at least 1.16 to work. When I downloaded 1.16 (the one with which I flashed the android 10 back in september, from the topic https://forum.xda-developers.com/t/guide-lgup-for-all-no-root-needed.3967858/unread) I click on the 'PARTITION DL' option and after 4% it asks me to select a partition. And here I don't know that to select, because there are so many options and I'm afraid to move with any of them to not screw things up even more.
Oh, and the file which I try to flash is stock european android 10, 30b.

AnDevil said:
OK, i *think* that I partly know what to do. Unlike You wrote, the 1.14 LGUP doesn't let me do anything with phone, saying that it needs at least 1.16 to work. When I downloaded 1.16 (the one with which I flashed the android 10 back in september, from the topic https://forum.xda-developers.com/t/guide-lgup-for-all-no-root-needed.3967858/unread) I click on the 'PARTITION DL' option and after 4% it asks me to select a partition. And here I don't know that to select, because there are so many options and I'm afraid to move with any of them to not screw things up even more.
Oh, and the file which I try to flash is stock european android 10, 30b.
Click to expand...
Click to collapse
Okay, just so that it's clear, you do want to use 1.14 when going from 8 or 9 to 10. 1.16 won't recognize the older OS.
But, if you'd have done 1.16 Part DL from the beginning, it would have worked, as you've discovered. When the pop up for which Parts? shows up, select them all (unless you have a very good reason for omitting one or more of them).
Because you want to flash ebw 30b, there shouldn't be any reason to select all partitions. But I'd suggest (again), after doing the part DL, let the phone reboot of course, to complete. Then just shut it off and go back to LGUP and do a refurbish this time of the exact same kdz.
good luck

Ok, now I'm confused
I always used the 1.16, never the 1.14. And before I had tinker with phone I already had Android 10 installed (which I installed via 1.16). I Think that someone made a patch for 1.16 to work with Android 9 when I made that transition.
Ok so You wrote that
"When the pop up for which Parts? shows up, select them all (unless you have a very good reason for omitting one or more of them)"
and below that You wrote
"there shouldn't be any reason to select all partitions"
so that part I don't understand.
Is it:
1. Connect phone in download mode to LGUP 1.16
2. Choose 'partition DL' And select all of them
3. Let it finish and the phone will reboot
4. Right when it boots to welcome screen shut it off
5. Enter download mode once again
6. Flash with 'refurbish' the 30b software
Are these steps correct?

AnDevil said:
Ok, now I'm confused
I always used the 1.16, never the 1.14. And before I had tinker with phone I already had Android 10 installed (which I installed via 1.16). I Think that someone made a patch for 1.16 to work with Android 9 when I made that transition.
Ok so You wrote that
"When the pop up for which Parts? shows up, select them all (unless you have a very good reason for omitting one or more of them)"
and below that You wrote
"there shouldn't be any reason to select all partitions"
so that part I don't understand.
Is it:
1. Connect phone in download mode to LGUP 1.16
2. Choose 'partition DL' And select all of them
3. Let it finish and the phone will reboot
4. Right when it boots to welcome screen shut it off
5. Enter download mode once again
6. Flash with 'refurbish' the 30b software
Are these steps correct?
Click to expand...
Click to collapse
Sorry yes, that should have been 'there shouldn't be any reason NOT to select all partitions' (I think that's what the 'context' of the whole comment implied').
Yes, those steps are correct.
I think the confusion about lgup is around this; 1.14 is used if u need to 'cross flash' (going to diff OS). If you're not cross flashing then 1.16 will work. I think most people are cross flashing due to desire to get rid of bloatware and / or wanting to move to A10 when their OS doesn't have it or the kdz is unavailable.
you are in a somewhat unusual circumstance, having the only version of v40 that lg actually allows legit unlocking. So you never cross flashed (had to re read to realize that, it's that uncommon).
good luck

OK, so unfortunately it didn't help, giving the same error as when I try to 'refurbish'.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
So it has to do something with me fastbooting the TWRP img (it's indicated by the name of it).
Seems to me that I should change the img for a stock one (if there is one that's stock) but then again, fastboot probably will end in error 'not possible in lock state' as I tried to fastboot other img's and it gave me that error.

AnDevil said:
OK, so unfortunately it didn't help, giving the same error as when I try to 'refurbish'.
View attachment 5190441
So it has to do something with me fastbooting the TWRP img (it's indicated by the name of it).
Seems to me that I should change the img for a stock one (if there is one that's stock) but then again, fastboot probably will end in error 'not possible in lock state' as I tried to fastboot other img's and it gave me that error.
Click to expand...
Click to collapse
So here's what I'd suggest, because you have an ebw version, which I believe has dual sim, and many many have had issues with those and losing the dual sim capability (very frustrating and difficult to get back).
Go to the v40 rom forum and Markus (los developer), put in the first post of his lineage rom an invite to the lgv40 tele gram group. Use that and join tele group and there are a lot of international users there, they can guide you with this problem (they have and use that specific device, among others).
If you want to do more reading on this, follow this link. It's the lg firmware dl page and do a search from the top for 'judy'. You'll see others have had the same error you're getting, and used lgup 1.15 command line to get around it.
I don't think it's because of what u flashed with fastboot (twrp), judypn is the name of the device, not specific to twrp.
So join the tele group and also (here on xda) look in the thread about 'unlocking all devices - except t-mo'. Not to unlock it, but to learn to use qfil. You will probably need that.
cheers

Ok, definitely will do that. Thank You very much for Your help

Related

Bricked phone.

Hello, i was given a blu R1 HD prime phone that was bricked by one of my relatives, according to him, he tried to do a format all + download on this phone, which as far as im aware, is a death flag, so i have here this bricked phone, i installed mrmazak's prime 6.1 no nv.zip file on this phone, but it still gives me the TOOL DL IMAGE FAIL, error i've heard a lot about, i also saw him saying "THIS IS NOT THE PACKAGE YOU NEED" in which case i can do nothing but ask, whats the correct package to get this bad boy up and running again? thanks beforehand.
PS: The phone is 8gb/1gb ram ver. was on ver 6.1, amazon before the brick, no OTA's.

Shinnazuka0411 said:
Hello, i was given a blu R1 HD prime phone that was bricked by one of my relatives, according to him, he tried to do a format all + download on this phone, which as far as im aware, is a death flag, so i have here this bricked phone, i installed mrmazak's prime 6.1 no nv.zip file on this phone, but it still gives me the TOOL DL IMAGE FAIL, error i've heard a lot about, i also saw him saying "THIS IS NOT THE PACKAGE YOU NEED" in which case i can do nothing but ask, whats the correct package to get this bad boy up and running again? thanks beforehand.
PS: The phone is 8gb/1gb ram ver. was on ver 6.1, amazon before the brick, no OTA's.
Click to expand...
Click to collapse
For a device that was format all. Will need more partitions than are in that package you tried. Also I have tried to work with someone else who had the 8gb size device, we could not get past that error.
I do recall that the last last person got a new board for his phone and pulled the images from it to share. There is a link in the main thread somewhere. But , well even when he tried to restore his own backup from good device to the one with do error, it did not work.
NVM
I remembered it wrong. He tried to pull it, but could not do it.
Look through this thread. Maybe you can try to follow the advice I gave him, and it may work for you.
https://forum.xda-developers.com/r1...-blu-r1-hd-t3440261/post76482224#post76482224

Well, from this mess in english, i can kind of attempt to understand that he tried to install v17 backup, and it didnt work due to the PMT CHANGED FOR THIS ROM, then he somewhere got a .bin backup for miracle?, and then silence, i dont know what else you tried suggesting to him since his english was so bad, i cant follow the steps, on another note, got that .bin backup? maybe ill try flashing it with miracle tool and praying that it'll work. Also, which V17 should i use, NVRAM or NONV

Shinnazuka0411 said:
Well, from this mess in english, i can kind of attempt to understand that he tried to install v17 backup, and it didnt work due to the PMT CHANGED FOR THIS ROM, then he somewhere got a .bin backup for miracle?, and then silence, i dont know what else you tried suggesting to him since his english was so bad, i cant follow the steps, on another note, got that .bin backup? maybe ill try flashing it with miracle tool and praying that it'll work. Also, which V17 should i use, NVRAM or NONV
Click to expand...
Click to collapse
There is now a "repair rom" listed in an mtk support group I try to follow. I have not checked it out yet, but maybe it will help. Let me open this on PC to search for the link
this one was labled v6.4 firmware http://www.mediafire.com/file/6kys9896445l5sm/SP_Flash_Tool_BLU_R0010UU_V6.4_Firmware.zip/file
this is labled as a repair firmware http://www.mediafire.com/file/il54pxuvpkargtr/BLU_R1_HD_R0030UU_REPAIR_MT6735.rar/file
I would have you look at those , first i suppose.
if it does not work I do have backups made from miricle-box, but they are not uploaded anywhere right now.

Real appreciated, will keep you updated, if anything works ill post it here.

Alright, i tried the 6.4 rom, it didnt work, i had it already, i also tried to install the "repair firmware" but in the v5.1628.00.000 version of my SPFT it shows me "SP FLASH TOOL ERROR: (8417) THE LOAD SCATTER FILE IS INVALID", then i try on another version (v5.1744 & v5.1804), then tells me STATUS_SCATTER_FILE_INVALID (0xC00300001), i tried the fix copypasting the hashtags and general settings on top for both cases but that didnt work, i noticed the scatter file looks really weird, not like most of the ones posted here or elsewhere, its just a bunch of rows and not organized in the slightest, maybe i need to try using the scatter for my 8gb/1gb ram? since R0030UU is the 16gb/2gb ram's model code
---------------------------------------------------------------------------------------------------------------------------------------------------------------EDIT: Tried mixed and matching the every file from the MT6735 repair firmware with the ones it didnt have from the prime 6.1 rom whilist using said 6.1 scatter, still on TOOL DL IMAGE FAIL

Shinnazuka0411 said:
Alright, i tried the 6.4 rom, it didnt work, i had it already, i also tried to install the "repair firmware" but in the v5.1628.00.000 version of my SPFT it shows me "SP FLASH TOOL ERROR: (8417) THE LOAD SCATTER FILE IS INVALID", then i try on another version (v5.1744 & v5.1804), then tells me STATUS_SCATTER_FILE_INVALID (0xC00300001), i tried the fix copypasting the hashtags and general settings on top for both cases but that didnt work, i noticed the scatter file looks really weird, not like most of the ones posted here or elsewhere, its just a bunch of rows and not organized in the slightest, maybe i need to try using the scatter for my 8gb/1gb ram? since R0030UU is the 16gb/2gb ram's model code
---------------------------------------------------------------------------------------------------------------------------------------------------------------EDIT: Tried mixed and matching the every file from the MT6735 repair firmware with the ones it didnt have from the prime 6.1 rom whilist using said 6.1 scatter, still on TOOL DL IMAGE FAIL
Click to expand...
Click to collapse
all I can do is share the backup from miricle-box that I have.
https://www.androidfilehost.com/?fid=5862345805528042536

Just trying to catch up, so bricked phone that wont format correct? Do you have twrp on it?

mrmazak said:
all I can do is share the backup from miricle-box that I have.
androidfilehost/?fid=5862345805528042536
Click to expand...
Click to collapse
Hi, this work on BLU R0030UU 2GB/16GB or R0010UU??

TavoStyle said:
Hi, this work on BLU R0030UU 2GB/16GB or R0010UU??
Click to expand...
Click to collapse
This is from 16gb so the R0030uu

mrmazak said:
This is from 16gb so the R0030uu
Click to expand...
Click to collapse
Hi!, I am from Venezuela, I apologize for my English, I am using the Google translator ...
I tried to put the software but the following error appears
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

TavoStyle said:
Hi!, I am from Venezuela, I apologize for my English, I am using the Google translator ...
I tried to put the software but the following error appears
Click to expand...
Click to collapse
Hello,
two issues.
first, the backup has scatter file formatted for use in miracle box, not sp flash tool.
next, The preloader on any updated phone has been changed and does not work to flash anymore.
So, what is / was version on your phone , so I can know if it should be able to work or not?
\

mrmazak said:
Hello,
two issues.
first, the backup has scatter file formatted for use in miracle box, not sp flash tool.
next, The preloader on any updated phone has been changed and does not work to flash anymore.
So, what is / was version on your phone , so I can know if it should be able to work or not?
\
Click to expand...
Click to collapse
First: If I use Miracle Box Crack 2.27A, can it work? (Would I have to disconnect and connect the battery to start the phone again?)
Next: I unchecked the Preloader because once I leave a brick as a phone to leave marked that option
Version: (Screen OLD, Now is in BLU Screen) (Ohhh I never UPDATE the software, I never use ROOT, I never use debloat...)

TavoStyle said:
First: If I use Miracle Box Crack 2.27A, can it work? (Would I have to disconnect and connect the battery to start the phone again?)
Next: I unchecked the Preloader because once I leave a brick as a phone to leave marked that option
Version: (Screen OLD, Now is in BLU Screen) (Ohhh I never UPDATE the software, I never use ROOT, I never use debloat...)
Click to expand...
Click to collapse
Most important part (custom build number) is missing from screen shot.

mrmazak said:
Most important part (custom build number) is missing from screen shot.
Click to expand...
Click to collapse
I just discovered something very crazy, I do not understand anything
In the recovery logs...
https://youtu.be/-sMubZoduig

TavoStyle said:
I just discovered something very crazy, I do not understand anything
In the recovery logs...
https://youtu.be/-sMubZoduig
Click to expand...
Click to collapse
so your build number is 6.6
you may be able to unlock.
But is phone still alive?

mrmazak said:
so your build number is 6.6
you may be able to unlock.
But is phone still alive?
Click to expand...
Click to collapse
My phone is stuck in the BLU logo

TavoStyle said:
My phone is stuck in the BLU logo
Click to expand...
Click to collapse
if it is still locked bootloader, and stock recovery fails to wipe data and / or cache. I do not have idea how to fix.\

Bricked BLU R1 HD
mrmazak said:
if it is still locked bootloader, and stock recovery fails to wipe data and / or cache. I do not have idea how to fix.\
Click to expand...
Click to collapse
Hi Mr Mazak
I had purchased non prime version of BLU R1 HD. I updated to the latest version via OTA. I had my phone rooted with super su and now wanted to try Magisk. After the reboot I had reinstalled the twrp recovery and did a format of all data on my phone. I am trying to install twrp but when I power on my device it is stuck on the boot loading screen. I have tried hold power button and volume down simultaneously and it reboots but gets stuck on the logo.
I tried using the sp flash tool to restore my phone to stock but it did not work. Get error S_BROM_DOWNLOAD_FAIL. 7d
My bootloader is unlocked.
Tried using adb commands but when I connect to the phone and run adb commands it says no authorisation.
If I can install twrp on the device then I will be able to install the rom from rootjunky, not sure if you require more info.
Awaiting your ananlys
Kind Regards

ismailf007 said:
Hi Mr Mazak
I had purchased non prime version of BLU R1 HD. I updated to the latest version via OTA.
Click to expand...
Click to collapse
The latest ota blocks the use of sp flash tool. And the kernel exploit used previouls. But now there is new exploit. But you cannot boot so that is mutt point now
ismailf007 said:
I had my phone rooted with super su and now wanted to try Magisk. After the reboot I had reinstalled the twrp recovery and did a format of all data on my phone.
Click to expand...
Click to collapse
Did you only format the data partition or whole device.?
ismailf007 said:
I am trying to install twrp but when I power on my device it is stuck on the boot loading screen.
Click to expand...
Click to collapse
This confuses me. You just said you had twrp already. Now you have trouble to I stall it.
ismailf007 said:
I have tried hold power button and volume down simultaneously and it reboots but gets stuck on the logo.
Click to expand...
Click to collapse
Did you use / try volume up?
ismailf007 said:
I tried using the sp flash tool to restore my phone to stock but it did not work. Get error S_BROM_DOWNLOAD_FAIL. 7d
My bootloader is unlocked.
Click to expand...
Click to collapse
From what you say.
1. You had working phone with SU root.
2. You have twrp installed
3. You wiped / formated with twrp
4. You now only boot to a logo screen. No recovery, or bootloader?

[ROM][STOCK] Stock Firmware Packages (For Expanded EDL Tools)

Stock Firmware Packages
Yes, they are finally here! This thread is for stock firmware packages.
These packages are specifically made to be installed with this EDL tool: https://forum.xda-developers.com/ax...n-10-pro-5g-expanded-edl-tools-fixes-t4174667
READ THE WARNINGS IN THAT THREAD BEFORE USING THE TOOLS
These packages are UNOFFICIAL unless marked otherwise. ZTE has not released stock firmware packages for most phones and versions.
How to install an EDL firmware package:
Note: These packages are specifically made for the EDL tools, not MiFlash or anything else.
1. Install the latest version of the EDL tools (in this thread)
2. Download a firmware package from this thread.
3. Unpack the firmware archive into the tool directory "Firmware_Package_Restore"
Make sure you unpack the firmware into Firmware_Package_Restore directory like this -Just for example - the script would be located in:"...\Axon10_(More)_EDL_Tools_v1_1b\Firmware_Package_Restore\Write Firmware v1.10 to A.ps1"And the firmware files would be in:"...\Axon10_(More)_EDL_Tools_v1_1b\Firmware_Package_Restore\firmware_1_10\"4. Put phone in EDL mode and run Load Programmer
5. Run a backup of your phone! Even if it isn't booting.
6. Run whichever "Write Firmware vX to Y.ps1" you want (X = firmware version, Y = A or B partition) (If you don't know which partition is currently booting, just install both.)
7. Wait for the install to finish ("done")
8. Start the phone (hold the power button until it resets, or run the Reset script)
9. You might see a few bootloops and then the phone ask you to do a factory reset / system wipe.
10. If the phone does not boot - look in the tools thread for how to use the Fix Bootable tool and try that.
11. Done.
Firmware Package Downloads:
~~~ A2020U (US Version) (Non-5G) ~~~
Firmware Version: 1.10 (GEN_NA_A2020U_PROV1.10)
Android: 9 (Pie)
Source: UNOFFICIAL (bobthenormal)
Download: Axon10Pro A2020U EDL Firmware v1.10(A9)
(If you downloaded this firmware before 12/9/2020 the script had an error, re-download the firmware or simply replace the script files with these ones: Firmware 1.10 Script Fix)
Thanks:
@djkuz for the original EDL tool for Axon 7
@Unjustified Dev for his port of the tool and tons of other work
@rafyvitto for a ton of ROMs and his stock B12 backup
and @eKeith for requesting the firmware enough times I finally bothered to make it =P

Please keep issues with the firmware here, and issues with the EDL tools in that thread.
I will upload firmware versions for A2020U: 1.11, 1.13, 2.09 (A10) (locked and unlocked). I just need to get time to actually test these out to make sure they work.
I didn't test the 1.10 version either but it should work and some people are stuck on A10 without it so I'm trying to post it quickly.
If anyone can wants the tools or firmware packages like these for their phone version (EU, CN, whatever non-A2020U Non-5G) and can volunteer their phone/time, PM me - I can't do them myself as I don't have those phones, but I can give safe instructions on what to do so that I can change make a version of the tools for those phones.

Hi i want the Firmware for zte axon 10 pro 5g 6ram
Details in photo
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Axon 10 Pro (Non-5G) EDL Tool - Flash / Backup / Restore/ Bootloader Unlock
Axon 10 EDL Tool BAT-program for Flash / Backup / Restore/ Bootloader Unlock Qualcomm HS-USB QDLoader 9008 (COM ...) !!! Whatever you do, you do at your own risk !!!" !!! If you are not sure of yourself do not use this program !!! Special...
forum.xda-developers.com
My post

amooor said:
Hi i want the Firmware for zte axon 10 pro 5g 6ram
Details in photo
View attachment 5146295
Axon 10 Pro (Non-5G) EDL Tool - Flash / Backup / Restore/ Bootloader Unlock
Axon 10 EDL Tool BAT-program for Flash / Backup / Restore/ Bootloader Unlock Qualcomm HS-USB QDLoader 9008 (COM ...) !!! Whatever you do, you do at your own risk !!!" !!! If you are not sure of yourself do not use this program !!! Special...
forum.xda-developers.com
My post
Click to expand...
Click to collapse
I'd suggesta new thread. I haven't seen anyone with that phone or a firmware package for it. If you can find someone that has your phone with stock firmware who is willing to do a little work, I'll tell them what to do to make it.

bobthenormal said:
I'd suggesta new thread. I haven't seen anyone with that phone or a firmware package for it. If you can find someone that has your phone with stock firmware who is willing to do a little work, I'll tell them what to do to make it.
Click to expand...
Click to collapse
Am sure 100% the problem is Firmware.
Do you know why because the holder tray for your ZTE Axon 10 Pro 5g in my phone is making for 1 sim like oneplus 7t in t-mobile if you unlocked and change the holder tray to hybrid dual sim it will work

Hello, I tried to use your tools to restore my phone since its on the European version and my sim card doesn't work (its US). The Write Firmware v1.10 to A tells me that COMPort is not found even though I already launched the load programmer script and see a COMPort file in the folder. Any ideas on what I can do? Thank you for your time!

los95 said:
Hello, I tried to use your tools to restore my phone since its on the European version and my sim card doesn't work (its US). The Write Firmware v1.10 to A tells me that COMPort is not found even though I already launched the load programmer script and see a COMPort file in the folder. Any ideas on what I can do? Thank you for your time!
Click to expand...
Click to collapse
Make sure you unpack the firmware into Firmware_Package_Restore directory like this -
Just for example - the script would be located in:
"...\Axon10_(More)_EDL_Tools_v1_1b\Firmware_Package_Restore\Write Firmware v1.10 to A.ps1"
And the firmware files would be in:
"...\Axon10_(More)_EDL_Tools_v1_1b\Firmware_Package_Restore\firmware_1_10\"

bobthenormal said:
Make sure you unpack the firmware into Firmware_Package_Restore directory like this -
Just for example - the script would be located in:
"...\Axon10_(More)_EDL_Tools_v1_1b\Firmware_Package_Restore\Write Firmware v1.10 to A.ps1"
And the firmware files would be in:
"...\Axon10_(More)_EDL_Tools_v1_1b\Firmware_Package_Restore\firmware_1_10\"
Click to expand...
Click to collapse
Thanks for the response! I will try it on Tuesday as I have finals. Will update to see what happens.

Okay I tried it again with the steps and now its giving me this.
https://pastebin.com/LwbK3vf7
It tells me that it can't find the files even though I have put the folder in that directory. Sorry for being ignorant I thought this wouldn't be too bad since I used to root Samsung devices.
Update:
I downloaded the new version of the edl tools and it still can't find the firmware files. Here is the log.
https://pastebin.com/LRuXEx0y
Another Update:
Sorry for the updates just wanted to see if I can fix it but I figured out why it didn't find the files.
For some reason, it would try to find the files inside the Firmware_Package_Restore instead of its own folder.
Now, I am getting another error that is says that my device is not on the port although I put it in edl mode. Perhaps I am doing something wrong? Here is another log with this error.
https://pastebin.com/ZtXwhUB0

los95 said:
Okay I tried it again with the steps and now its giving me this.
https://pastebin.com/LwbK3vf7
It tells me that it can't find the files even though I have put the folder in that directory. Sorry for being ignorant I thought this wouldn't be too bad since I used to root Samsung devices.
Update:
I downloaded the new version of the edl tools and it still can't find the firmware files. Here is the log.
https://pastebin.com/LRuXEx0y
Another Update:
Sorry for the updates just wanted to see if I can fix it but I figured out why it didn't find the files.
For some reason, it would try to find the files inside the Firmware_Package_Restore instead of its own folder.
View attachment 5152479
Now, I am getting another error that is says that my device is not on the port although I put it in edl mode. Perhaps I am doing something wrong? Here is another log with this error.
https://pastebin.com/ZtXwhUB0
Click to expand...
Click to collapse
Hey! Thanks for attaching the log, that was perfect for finding the issue right away. The script is building the search_path incorrectly, here's corrected copies of the scripts. I'll update and re-upload the full firmware zip file as soon as I get a chance, but just replace the ones you have with these.
EDIT: Ah, yes hold on I'll take a look at the second issue. Sorry about that, didn't have a chance to test these.
So, the new problem appears to be something with the COM port communication. I have to get going in a minute but a few suggestions to try:
Reboot your phone into EDL then run the loader/firmware scripts right away. Sometimes the ports kind of time out.
Open Device Manager in windows and open the "Ports" list and make sure you see your phone on there. Edit the COMPort file to have the right one, or delete it to force the script to re-check if it's trying to connect to the wrong one.
Check the drivers - the tools have the stock A2020U drivers included, might need to reinstall them especially if you install drivers for other phones.
See if any of those help, let me know how it goes.

bobthenormal said:
Hey! Thanks for attaching the log, that was perfect for finding the issue right away. The script is building the search_path incorrectly, here's corrected copies of the scripts. I'll update and re-upload the full firmware zip file as soon as I get a chance, but just replace the ones you have with these.
EDIT: Ah, yes hold on I'll take a look at the second issue. Sorry about that, didn't have a chance to test these.
So, the new problem appears to be something with the COM port communication. I have to get going in a minute but a few suggestions to try:
Reboot your phone into EDL then run the loader/firmware scripts right away. Sometimes the ports kind of time out.
Open Device Manager in windows and open the "Ports" list and make sure you see your phone on there. Edit the COMPort file to have the right one, or delete it to force the script to re-check if it's trying to connect to the wrong one.
Check the drivers - the tools have the stock A2020U drivers included, might need to reinstall them especially if you install drivers for other phones.
See if any of those help, let me know how it goes.
Click to expand...
Click to collapse
Thanks I will try this.
Edit:
I ended up deleting the com port file, ran Load Programmer, and the scripted worked. However, when it finished and I go back to boot my phone (I had to use the other edl tool and asked it to unlock the google FRP since I don't know another method to boot it back to normal) it boot back to the old rom it had. Its like it didn't write anything to the phone although the script did show me it was doing its job and end with a success. Any ideas? Here is my phone with the same firmware still installed after using the script.
Update:
I decided to use the write firmware to b instead and now it is American. Thank you for all the hard work I thought I had to carry two phones with me everywhere lol. Now I have another question. When I reboot my phone, a message pops up saying that the phone is unlocked and to either press the power button to pause or continue. I read in the threads that this means that fast boot is disabled. Is there anyway I can get fast boot back?

los95 said:
Thanks I will try this.
Edit:
I ended up deleting the com port file, ran Load Programmer, and the scripted worked. However, when it finished and I go back to boot my phone (I had to use the other edl tool and asked it to unlock the google FRP since I don't know another method to boot it back to normal) it boot back to the old rom it had. Its like it didn't write anything to the phone although the script did show me it was doing its job and end with a success. Any ideas? Here is my phone with the same firmware still installed after using the script.
View attachment 5153355
Update:
I decided to use the write firmware to b instead and now it is American. Thank you for all the hard work I thought I had to carry two phones with me everywhere lol. Now I have another question. When I reboot my phone, a message pops up saying that the phone is unlocked and to either press the power button to pause or continue. I read in the threads that this means that fast boot is disabled. Is there anyway I can get fast boot back?
Click to expand...
Click to collapse
Nice! Super glad that it worked.
That A/B issue is why I considered just making the script automatically install it to both A and B. The only way I can tell which side is booting is to go into fastboot, which I find annoying. But if you install a ROM to A while you're booting from B, you won't see it obviously, so I generally just flash both sides at the same time since I always have full backups of both anyway.
As for that message, it sort-of means fastboot is disabled - it pops up when:
1. the bootloader is unlocked
AND
2. the stock bootloader is installed
So to get rid of the message you can either re-lock the phone OR install Unjustified Dev's patched bootloader. And since the stock bootloader does not have fastboot, the only way to have it is to install the unlocked bootloader.
You can do that either through the old tool ("unlock" the phone again), or through mine by running "write_UD-bootloader.ps1" in the Write_Unlocked_Bootloader_and_FRP folder.

bobthenormal said:
Nice! Super glad that it worked.
That A/B issue is why I considered just making the script automatically install it to both A and B. The only way I can tell which side is booting is to go into fastboot, which I find annoying. But if you install a ROM to A while you're booting from B, you won't see it obviously, so I generally just flash both sides at the same time since I always have full backups of both anyway.
As for that message, it sort-of means fastboot is disabled - it pops up when:
1. the bootloader is unlocked
AND
2. the stock bootloader is installed
So to get rid of the message you can either re-lock the phone OR install Unjustified Dev's patched bootloader. And since the stock bootloader does not have fastboot, the only way to have it is to install the unlocked bootloader.
You can do that either through the old tool ("unlock" the phone again), or through mine by running "write_UD-bootloader.ps1" in the Write_Unlocked_Bootloader_and_FRP folder.
Click to expand...
Click to collapse
Thanks for the great help. Now I have installed twrp and will most likely just put magisk and keep the stock rom as I am now terrified on installing a custom rom since it lead to me to a lot of trouble. Maybe I will touch lineage later on but for now I will just have twrp and root.

los95 said:
Thanks for the great help. Now I have installed twrp and will most likely just put magisk and keep the stock rom as I am now terrified on installing a custom rom since it lead to me to a lot of trouble. Maybe I will touch lineage later on but for now I will just have twrp and root.
Click to expand...
Click to collapse
You're welcome!
I wouldn't be afraid of doing custom roms once you do a full backup of your working phone with my tools! If you have the 256gb phone you can add the userdata backup to that and really have everything including settings, apps, and data. Then if anything goes wrong you just do a full restore back to exactly where you were.
I haven't been trying custom ROMs because I just don't have the hours to spend trying them out and re-configuring each one to find out which I want to use, otherwise I definitely would. The stock ROM is really kinda poop (I'm on A10).
Also, if you try flashing a custom ROM and it doesn't boot after you install it - before assuming it didn't work and restoring, FIRST try the "Fix bootable" tool. Some ROMs get installed to a different partition than they were made from, so they have that flag for which partition they think they are installed on. When it doesn't match it won't boot. Good luck!

bobthenormal said:
You're welcome!
I wouldn't be afraid of doing custom roms once you do a full backup of your working phone with my tools! If you have the 256gb phone you can add the userdata backup to that and really have everything including settings, apps, and data. Then if anything goes wrong you just do a full restore back to exactly where you were.
I haven't been trying custom ROMs because I just don't have the hours to spend trying them out and re-configuring each one to find out which I want to use, otherwise I definitely would. The stock ROM is really kinda poop (I'm on A10).
Also, if you try flashing a custom ROM and it doesn't boot after you install it - before assuming it didn't work and restoring, FIRST try the "Fix bootable" tool. Some ROMs get installed to a different partition than they were made from, so they have that flag for which partition they think they are installed on. When it doesn't match it won't boot. Good luck!
Click to expand...
Click to collapse
Thanks for the tip! I forgot to mention something strange about the reset from edl tool. When I was turning my phone back to American, I tried to use that and it gave me an error saying this
{ERROR: Command line argument 'reset=' is not recognized as a valid option}
On the shell window it shows different options and there is one that says reset but without = sign. I'm not sure if its some typo but wanted to let you know.

los95 said:
Thanks for the tip! I forgot to mention something strange about the reset from edl tool. When I was turning my phone back to American, I tried to use that and it gave me an error saying this
{ERROR: Command line argument 'reset=' is not recognized as a valid option}
On the shell window it shows different options and there is one that says reset but without = sign. I'm not sure if its some typo but wanted to let you know.
Click to expand...
Click to collapse
Ah that is weird! I must have forgot to save some changes to that script, it's supposed to use the XML file. Fixed that and threw on a script with a long delay ( version 1.1d now)
Thanks for pointing that out.. my quality control guy is slacking! (I'm the quality control guy...)
Lemme know if you find any other ones.

bobthenormal said:
Ah that is weird! I must have forgot to save some changes to that script, it's supposed to use the XML file. Fixed that and threw on a script with a long delay ( version 1.1d now)
Thanks for pointing that out.. my quality control guy is slacking! (I'm the quality control guy...)
Lemme know if you find any other ones.
Click to expand...
Click to collapse
Sorry for all the replies I just want to be sure everything is fine with the backup tool. I did the full back up and it looks like it worked but I was getting warnings that the files it was looking for returned as null. Is that supposed to happen? Here is the link with the log.
backup_all log - Pastebin.com

los95 said:
Sorry for all the replies I just want to be sure everything is fine with the backup tool. I did the full back up and it looks like it worked but I was getting warnings that the files it was looking for returned as null. Is that supposed to happen? Here is the link with the log.
backup_all log - Pastebin.com
Click to expand...
Click to collapse
Oh whew, you scared me if there was a problem with backup_all
That's the one I was especially careful about since I got burned by the original EDL backup tool.
No worries about bringing up potential issues, I can't guarantee the tools don't mess up anyone's phone but I'd still feel terrible if they did so I appreciate the "bug testing".
The warnings there are all good even though they look scary.
If you look in the log, you see the files are attempt to read (and returned NULL) first, then once it has gone through all of them it repeats the list. The way the EDL interface works is kind of odd. It doesn't take a "read" command, it takes a "write" command "reversed", so it executes it like a write command sort of. That means it looks for the files to "write" first to prepare, even though it doesn't actually use them (except to overwrite them if they do exist).
It makes sense from a programming perspective, efficient and saves ROM.

Hi, I am back again. Magisk had an update and after it was installed, the phone wouldn't boot up anymore. It just stayed at the bootloader and I had to wipe it and installed the original firmware as for some unknown reason, my backup is not there. I tried using the restore tool and it couldn't find my back up. I checked the specific files folders to see if the backup was there and nothing was found. The good thing is that the phone can be brought back life even if I have to start fresh ( I don't mind it to be honest since I don't use a lot of apps). This inspired me to install lineage but the link on that thread is broken. Someone asked the OP of the thread about it but I think he hasn't been active for a while. Do you by any chance have the lineage rom file? Sorry for asking but I don't know where to look. Thanks for reading!

los95 said:
Hi, I am back again. Magisk had an update and after it was installed, the phone wouldn't boot up anymore. It just stayed at the bootloader and I had to wipe it and installed the original firmware as for some unknown reason, my backup is not there. I tried using the restore tool and it couldn't find my back up. I checked the specific files folders to see if the backup was there and nothing was found. The good thing is that the phone can be brought back life even if I have to start fresh ( I don't mind it to be honest since I don't use a lot of apps). This inspired me to install lineage but the link on that thread is broken. Someone asked the OP of the thread about it but I think he hasn't been active for a while. Do you by any chance have the lineage rom file? Sorry for asking but I don't know where to look. Thanks for reading!
Click to expand...
Click to collapse
Damn that's not good. You checked in the Backup tool folder for the backups?
They would be named "backup_all-critical-(date/time)" and "backup_all-non-critical-(date/time)"
The Restore tool doesn't automatically try to find backups, you have to move the backup files you want to restore into the restore directories (critical to critical, non-critical to non-critical).
It's not super user friendly, but it's a ton of extra work to make it search for backups and pop up a menu and such. Hopefully that's the issue, but if not I'd like to know if you figure out why the backups aren't there.
I *think* I have the lineage ROM... but I can't upload it right now, on slow internet! Might be a few weeks before I get back, if rafy hasn't uploaded it by then I'll upload it.
Also, the magisk update - I've had that happen on several phones too where it tries to update itself and bricks, so I'm really careful about when I do updates. Not sure if there's a safe method, maybe uninstalling magisk and reinstalling the new version.

Question [CLOSED] Pls help to fix: dm-verify corruption

For my Redmi Note 10 5G bought from Vodafone UK, initially I used Xiaomi Tool V2 (https://www.xiaomitool.com/V2/) to install the ROM, but it failed with error. After that any power on/reboot shows this error:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Then I went into Fastboot and used MiFlash tool to install a ROM, that installed successfully. But each time I reboot (or fresh power on) I get the above error and the phone switches off itself. But if I press the power on within the 5 seconds, it will power on and then the phone works fine.
Although the phone works fine, any reboot doesn't work automatically, I need to press power button within 5 seconds for it to work.
Now my question is how to fix the error in the screenshot?

fm663 said:
For my Redmi Note 10 5G bought from Vodafone UK, initially I used Xiaomi Tool V2 (https://www.xiaomitool.com/V2/) to install the ROM, but it failed with error. After that any power on/reboot shows this error:
View attachment 5458547
Then I went into Fastboot and used MiFlash tool to install a ROM, that installed successfully. But each time I reboot (or fresh power on) I get the above error and the phone switches off itself. But if I press the power on within the 5 seconds, it will power on and then the phone works fine.
Although the phone works fine, any reboot doesn't work automatically, I need to press power button within 5 seconds for it to work.
Now my question is how to fix the error in the screenshot?
Click to expand...
Click to collapse
Try with:
adb disable-verity
or flashing blank/null vbmeta:
fastboot --disable-verity flash vbmeta vbmeta.img or:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
fastboot flash vbmeta vbmeta.img

@SubwayChamp Thank you for help. However I am getting this error:
adb disable-verity
verity cannot be disabled/enabled - USER build
If I were do do the fastboot commands, will it wipe out the ROM+data in the phone (Note I have already been using it for last 1-2 weeks)? Also where to get the vbmeta.img file?

fm663 said:
@SubwayChamp Thank you for help. However I am getting this error:
adb disable-verity
verity cannot be disabled/enabled - USER build
If I were do do the fastboot commands, will it wipe out the ROM+data in the phone (Note I have already been using it for last 1-2 weeks)? Also where to get the vbmeta.img file?
Click to expand...
Click to collapse
This vbmeta will work https://forum.xda-developers.com/attachments/vbmeta-tar.5065875/ (unzip it) not sure if this solves it, but it is worth the try. And not, flashing the vbmeta won't wipe your data.
I guess your device is unlocked, or maybe you did try to flash something unofficial on it being locked?, what happened prior to this appear?

SubwayChamp said:
This vbmeta will work https://forum.xda-developers.com/attachments/vbmeta-tar.5065875/ (unzip it) not sure if this solves it, but it is worth the try. And not, flashing the vbmeta won't wipe your data.
I guess your device is unlocked, or maybe you did try to flash something unofficial on it being locked?, what happened prior to this appear?
Click to expand...
Click to collapse
Initially I unlocked the phone, then installed Indonesian ROM from Xiaomi website and locked it back.
Does the phone need to be unlocked again?

fm663 said:
Initially I unlocked the phone, then installed Indonesian ROM from Xiaomi website and locked it back.
Does the phone need to be unlocked again?
Click to expand...
Click to collapse
Yes, of course, this is why the warning message is appearing. In the other hand you were lucky to not brick your device, be careful not all the firmwares are interchangeable, specifically the Chinese, to be locked.
I mean, if you only are interested in this message to disappear, you should install again the same ROM that your device was in, but the Indonesian ROM is more attractive over the Global ROM despite the bloatware that can be uninstalled easily.

SubwayChamp said:
Yes, of course, this is why the warning message is appearing. In the other hand you were lucky to not brick your device, be careful not all the firmwares are interchangeable, specifically the Chinese, to be locked.
I mean, if you only are interested in this message to disappear, you should install again the same ROM that your device was in, but the Indonesian ROM is more attractive over the Global ROM despite the bloatware that can be uninstalled easily.
Click to expand...
Click to collapse
Yes, it is the best ROM for my requirements, except I couldn't get Dual Apps to work in it. Do you know how to?
As I want to use Google Pay + NFC, thus I need it locked.
Problem now is I'll loose all data and its time consuming to install everything all over again.
Maybe I'll leave with this error as is for now, unless I find an easier way

fm663 said:
Yes, it is the best ROM for my requirements, except I couldn't get Dual Apps to work in it. Do you know how to?
As I want to use Google Pay + NFC, thus I need it locked.
Problem now is I'll loose all data and its time consuming to install everything all over again.
Maybe I'll leave with this error as is for now, unless I find an easier way
Click to expand...
Click to collapse
Strange, I used Dual apps in my RN8 exactly in Indonesian ROM (I switched from global because of the absence of Phone and Message native apps) although you are fear to, probably you need to format data in order that can work.
There are some workarounds in the Magisk thread to use GPay and NFC, although rooted.
I don't think there is an easy way because of locked bootloader.

SubwayChamp said:
Strange, I used Dual apps in my RN8 exactly in Indonesian ROM (I switched from global because of the absence of Phone and Message native apps) although you are fear to, probably you need to format data in order that can work.
There are some workarounds in the Magisk thread to use GPay and NFC, although rooted.
I don't think there is an easy way because of locked bootloader.
Click to expand...
Click to collapse
I did not know it is possible to get GPay+NFC to work while rooted. Do you not get CTS Profile mismatch error this way?

fm663 said:
I did not know it is possible to get GPay+NFC to work while rooted. Do you not get CTS Profile mismatch error this way?
Click to expand...
Click to collapse
actually all you have been asking has been discussed already, we are all busy but at least spend 10 minutes searching, vbmeta, dm-verity, nfc+Google pay all well discussed already, please spend 10 minutes by searching

simika said:
actually all you have been asking has been discussed already, we are all busy but at least spend 10 minutes searching, vbmeta, dm-verity, nfc+Google pay all well discussed already, please spend 10 minutes by searching
Click to expand...
Click to collapse
Thank you for the tips.
Maybe I am not good at searching. I have many days of searching over the last few months and did not find the answers. I have another phone Mi Mix 2 that is unlocked and few things don't work in it due to CTS Profile issue. I would like to get that fixed too. Can you point to me specific pages please? Thank you

fm663 said:
Thank you for the tips.
Maybe I am not good at searching. I have many days of searching over the last few months and did not find the answers. I have another phone Mi Mix 2 that is unlocked and few things don't work in it due to CTS Profile issue. I would like to get that fixed too. Can you point to me specific pages please? Thank you
Click to expand...
Click to collapse
sure:
ROOT GAINED !!!!
THIS METHOD WORKS on both: POCO M3 Pro / Redmi Note 10 5G hey guys.. wonderful news.. been trying here and there and IT WORKS FINALLY i gained root of POCO m3 Pro 5G ! i'll write in steps how it works and post all files i've been using...
forum.xda-developers.com
here you'll find answers about root, dm-verity and much more, always related to poco m3 pro and redmi note

fm663 said:
I did not know it is possible to get GPay+NFC to work while rooted. Do you not get CTS Profile mismatch error this way?
Click to expand...
Click to collapse
If you want to stay locked no way to disable this warning message but if you decide to unlock your device and root it, it is pretty easy to fix it, one of the methods available is what I indicated, flashing a blank/null vbmeta through specific fastboot commands, there are other methods though, but this is the most universal and easy to use.
In regard to the CTS issue, I don't use GPay, so I can't tell you, but no better place that the Magisk Discussion Thread, it is the appropriate thread where you can find all the info from all the members affected on that, in the meantime you also can take a read on this https://droidholic.com/fix-safetynet-failed-cts-profile-false/

1. Hello friends, there are two ways to fix this problem. First, you need Root, and after using Root, you need to download any file manager and give Root permission. You need to backup your baseband, nvram nvdata nvcfg after backup Save, you also need an MTK Bypass You can search for MTK Auth Bypass Tool through Google. To download, you also need to use SP Flash to flash the machine. You need to download the official firmware package. You can download it through xiaomirom.com, download the corresponding version, and use SP Flash to read your firmware package, after the reading is completed, choose to format all and download, wait for the completion, press the power button after completion, you will find that the error has disappeared, but the baseband is lost, but you have backed up. Boot through fastboot to unlock the BL lock, and proceed fastboot flash nvram ....... fastboot flash nvdata ....... fastboot flash nvcfg ....... Fastboot reboot reboot. congratulations your baseband is back, i am a newbie and my instructions are very Not comprehensive, such as where is the baseband position, but I have too many characters, I will list the baseband position. 2. Replace a new motherboard, all mobile phone problems are solved.
Hope to help you.

THREAD LOCKED
As per the Forum Rules:
5. Create a thread topic or post a message only once, this includes external links & streaming media.
-snip-
-snip-
Duplicate threads and posts will be removed
Always post in an existing thread if a topic already exists, before creating a new thread.
-snip-
Click to expand...
Click to collapse
Please search the forum for existing/similar threads before posting a new thread. For continuing discussion, kindly use the existing thread: https://forum.xda-developers.com/t/how-to-get-rid-of-dm-verity-corruption-on-boot.4290677/
Regards,
shadowstep
Forum Moderator

General [CLOSED] --

USE UPDATED POST, HERE!
THIS POST IS NOW ONLY REFERENCE ONLY - WILL BE DELETED SOON.
Well I figured I'd make a quick How-To on how I successfully Carrier/Sim unlocked my Samsung Galaxy S21 Ultra 5G running the NEWEST Android update on bootloader 5 (USQU5BULJ)released in January of 2022.
***This does NOT trip Know and does NOT require a root or a paid service. ***
****Also Note - This is the process I took, you may find some of these steps are not needed but for the purpose or recreating my results, I'll be posting my exact process.
****This has ONLY BEEN TESTED ON SNAPDRAGON BASED SAMSUNG GALAXY S21 ULTRA 5G SM-G998 U & U1, if you try it on a different model or phone you may (and likely will) receive different results!!!!
Here's what you'll need:
•ANY (activated or not) Sim from the carrier you wish to switch too.(or a way to replicate the carriers cert from one)
•A computer
•Patched Odin
•BOTH the NEWEST U & U1 ROMs/Firmware - theres a full post on these and how to flash them here on XDA (Reminder for myself or mod to link it) or visit SamFW.com, it has both Odin and the ROM/Firmware files you will need.
•Android ADB platform tools (You can find them on the official Android Developers page here or use any ADB software of your choice, fastboot is not required or used in this process.(Google "Android Developer Platform Tools" to get them from the official Android devs page. )
STEP 1:
So let's presume you have a Verizon or T-Mobile carrier locked phone, if you look at your baseband, which you can find in Settings > About > Software Info, you should see this "SM-G998Uxxxxxxx"
*****IF YOU SEE "SM-G998U1xxxxxxx" STOP - Skip to step 2******
Head over to your preferred site to get stock Samsung Roms (Refer to link above if you don't know where to find) and download the U1 XAA rom and the U rom of the CARRIER YOU WISH TO USE. IMPORTANT! MAKE SURE YOU DOWNLOAD THE "U" ROM FOR BOTH THE CARRIER YOU WISH TO SWITCH TO AND THE U1 UNLOCKED ROM.
Put you device in download mode (Hold Vol up and Vol down and plug in the USB, which should be connected to your PC and now your phone at this point.)
Flash the U1 XAA Rom, place appropriate files in appropriate places in Odin, when you get to CSC, DO NOT use the "HOME_CSC" use the other.
Leave the rest of Odin settings alone and hit Start, wait for it to finish and reboot.
Step 2:
Once the phone boots, return to Settings>About>Software and confirm you are using the XAA rom by looking at Service Provider Software Version and it should say something like "SM-G998U1_XAA blah blah blah" you just want to see the U1 and XAA.
Now put in the Sim from the carrier you desire. A pop-up should appear prompting you to restart your device. Follow the prompt.
!MOST IMPORTANT STEP!
BEFORE the device fully restarts, force it into RECOVERY MODE, I was able to achieve this by holding the power and Vol Down buttons at the same time, starting to hold the directly after the "Samsung" Logo fades away upon initial restart. If you have trouble getting into recovery please comment below.
Once in recovery, use the volume keys to navigate to "Clear Cache" select and execute. Now go to Factory Data Reset/Wipe, select and execute. It should be the option directly above "Clear cache".
Once done, go up to "Reboot to Bootloader", Select, Execute.
AGAIN, Very Important step,you MUST interrupt the boot process again and force the phone BACK into download mode this time, so once the phone attempts to reboot, you need to hold the Vol Down and Vol Up buttons at the same time and the USB MUST be already plugged in.
We should now be back in download mode and be on the U1 rom. We have verified all of this in the steps above.
STEP 3:
Now it's time to flash the ROM from the carrier you wish to use. Make SURE you have a Sim from that carrier inserted during this process. It doesn't need to be a working or activated Sim, just simply one from the carrier you wish to have your S21 work on.
Flash all items as you did earlier, but using the "U" ROM for your desired carrier as described above. Same deal with CSC, DO NOT use the "Home_CSC"
BE SURE that you use the USERDATA file if there is one for your carrier. Very important to have the phone working properly.
Start the Odin flashing process.
Phone will Auto-Reboot.
Done!
You should now be on the carrier you wish to use. This can be (in theory, test at own risk) replicated for ANY carrier supported by Samsung, and, I should soon find out if it will lead to what my original goal was, a bootloader unlock on the QualComm SnapDragon variant of the S21 and future Galaxy devices.
If you have any issues please comment below.
PoC, results after doing above process.
Good luck.
-k0mrade
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

There are some parts of my tutorial that are not well expressed and may be misleading. Please don't hesitate to post in comments if you need clarity.

IMPORTANT!!! I LEFT OUT ONE MAJOR STEP! ************ ----- BETWEEN STEP ONE AND STEP 2 - After you do the factory data reset/Wipe cache -> reboot to Bootloader -> force into download, you need to flash the U1 rom BEFORE putting in your desirced carriers SIM, then reboot, let phone fully boot, THEN insert your desired carriers SIM -> restart phone-> interrupt boot by forcing into recovery and repeat factory data wipe and cache wipe and reboot bootloader -> interrupt Boot Process again, but into Download Mode -> Flash your desired "U" carrier Firmware (must be same carrier as the SIM you put in as described above). -> Done.

And when/where does one need to use the required ADB-Tools?

tested and work only on S21 ULTRA 5G SM-G998 U & U1
thank you

OnnoJ said:
And when/where does one need to use the required ADB-Tools?
Click to expand...
Click to collapse
Lol this is likely one of those steps thats unneeded. i cant remeber off the top of my head why exactly i added that in. But it wont hurt to have the drivers, thats for sure.

Ive made a (Slightly) more clear post, hopefully better detailing this, Here. Mods may close this thread as they feel free but i will leave it up as a resource for the time being.

How many different devices have you tested this on?

iBowToAndroid said:
How many different devices have you tested this on?
Click to expand...
Click to collapse
ive just finished doing it on my 6th one device, 4 were Verizon 1 was Tmobile and 1 was ATT. I seem to be able to replicate this process over and over again so far with no issues so far, but i am making sure to update each device manually via odin 1st to latest u1 Firmware first as described above.

K0mraid3 said:
ive just finished doing it on my 6th one device, 4 were Verizon 1 was Tmobile and 1 was ATT. I seem to be able to replicate this process over and over again so far with no issues so far, but i am making sure to update each device manually via odin 1st to latest u1 Firmware first as described above.
Click to expand...
Click to collapse
And for each device, did you personally verify that it was not already unlocked before starting?
Because normally you can't get that restart popup prompt on U1 firmware unless the device is already unlocked

iBowToAndroid said:
And for each device, did you personally verify that it was not already unlocked before starting?
Because normally you can't get that restart popup prompt on U1 firmware unless the device is already unlocked
Click to expand...
Click to collapse
thats essentially the point of going from u to u1 then back to u after you booted atleast once into u1 with the desired carriers sim, somewhere along in the process of interrupting the bootloader and flashing the carriers U Firmware its overwriting the system policy. Theres a hole in here somewhere im positive. still trying to pin point exactly where this weakness lies.

iBowToAndroid said:
And for each device, did you personally verify that it was not already unlocked before starting?
Because normally you can't get that restart popup prompt on U1 firmware unless the device is already unlocked
Click to expand...
Click to collapse
End Game is to find a BL exploit to force enable OEM Unlocking on these qcomm s21s.

K0mraid3 said:
End Game is to find a BL exploit to force enable OEM Unlocking on these qcomm s21s.
Click to expand...
Click to collapse
You're definitely not going to find that, as that's not related to SIM unlocking whatsoever

iBowToAndroid said:
And for each device, did you personally verify that it was not already unlocked before starting?
Because normally you can't get that restart popup prompt on U1 firmware unless the device is already unlocked
Click to expand...
Click to collapse
And sorry to answer your initial question, yes, verfied carrier lock, getting errors like this, see attached.

iBowToAndroid said:
You're definitely not going to find that, as that's not related to SIM unlocking whatsoever
Click to expand...
Click to collapse
I like a challenge

This "temporary" thread is now closed. Main thread is here.

Question Cannot register a new fingerprint in OnePlus 10 PRO

Hi
I bought a new OnePlus 10 PRO from Aliexpress. Its a CH version that the seller installed on it a global rom.
In the first setup of the phone, When I get to setting the fingerprint, I am unable to set it. I get the following:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I tried updating the phone, I tried factory reset... its always the same.
Any idea?
Thanks !

Are you sure that he installed the global rom? With model is yours NE2213 ? I bought from them also but I don't have this issue.
Anyway, you can try to use Oxygen Updater, to check if there is an update for your device or since your device is reseted, you can install ColorOS back

Hi,
I am on NE2215. Using Oxygen Updater I see that I have the most up to date version.
Not sure exactly how to install ColorOS.. I do want to have the regular OS that I would have as if I bought the global version (which i guess this is what the global rom mean..)

Right, I agree with you. I recommended to install the coloros just to check if it's a compability issue.
You can try to reinstall you version and see what happens, just download it and flash it again.

ok, and now for someone that have no idea how to do it?

If yours is NE2215 A13 you can download the ota file from this link: https://android.googleapis.com/packages/ota-api/package/7548d30abac02bde85a403bcc3a218df868e1910.zip
Then put it in your phone root and from your device Settings -> About the device -> Click on the option to check for the update -> 3 dots menu -> local installation and chose this package. It will start the installation.

Thank you for your help !
Downloaded and copied into my device files.
However - When I go to "About device" and click on the "up to date" button to search for updates, it just tells me I have no updates and i see no 3 dots to go for local installation:
What am I missing?

I think it's obvious that something went wrong during the region change, this issue was prevalent on the 8 pro and was extremely difficult to fix.
Check out the 8 pro threads you'll be sure to see it. It's a partition iirc and if it's borked then it simply will not work..
I can't remember the name of it off hand but have a look and I'm sure you can get an idea of what may be wrong, specifically that partition.
Overall it's difficult to say as you've got a region changed phone, have you asked the seller what they did? If it is indeed as difficult as it was on the 8 pro to fix and seeing as you may be the only person experiencing this (far as I know) then I'd consider returning it.
You could re-flash the entire OS via fastboot enhance but that would also bring with it inherent problem's, if it's new then I guess the question you need to ask yourself is it worth it?
Did you save much money getting that converted variant?

dkaro said:
Thank you for your help !
Downloaded and copied into my device files.
However - When I go to "About device" and click on the "up to date" button to search for updates, it just tells me I have no updates and i see no 3 dots to go for local installation:
View attachment 5624305
What am I missing?
Click to expand...
Click to collapse
This page is from android play services. You need to click on the first banner

@dladz TBH I bought it for around 70% of the price I would pay locally.. So yea, it was much cheaper. I also had before OP9 global rom and had no issues with it.
Maybe indeed as last step its worth trying to reinstall everything again.. I'm just not sure how to do it. I cannot find the local upgrade option as advised above, and after googling a bit how to do it using ADB, when i try to run fastboot oem unlock - the CMD will just show me forever "< waiting for any device >" (and this is although I was able to communicate with my device using "adb devices" and I got back my device id.
@zopostyle I did click on that banner you're showing and I got to the page I showed you before..
I'm clueless

If that is the page showing I'm assuming you're on a gsi ROM and not oxygen os.
Now it's better to reinstall OxygenOS completely because it doesn't seem to be the ROM you're running.
Search here on xda to unlock your bootloader and then you need to find the zip with the full ROM for you device and install it from fastboot as mentioned.

OK, i'm trying to unlock my bootloader but as I mentioned:
dkaro said:
and after googling a bit how to do it using ADB, when i try to run fastboot oem unlock - the CMD will just show me forever "< waiting for any device >" (and this is although I was able to communicate with my device using "adb devices" and I got back my device id.
Click to expand...
Click to collapse
Any idea what am I doing wrong?
I tried several tutorials online and so far I found no tutorial that will actually give me step by step that each step is actually working..

Maybe it's missing the drivers. Try this https://gsmusbdriver.com/oneplus-10-pro

dkaro said:
@dladz TBH I bought it for around 70% of the price I would pay locally.. So yea, it was much cheaper. I also had before OP9 global rom and had no issues with it.
Maybe indeed as last step its worth trying to reinstall everything again.. I'm just not sure how to do it. I cannot find the local upgrade option as advised above, and after googling a bit how to do it using ADB, when i try to run fastboot oem unlock - the CMD will just show me forever "< waiting for any device >" (and this is although I was able to communicate with my device using "adb devices" and I got back my device id.
@zopostyle I did click on that banner you're showing and I got to the page I showed you before..
I'm clueless
Click to expand...
Click to collapse
I feel you buddy.
You can use the app in my Magisk guide to do local installs.
Unlocking the bootloader you need to type fastboot flashing unlock
I haven't had to change region myself, but I did make a thread for someone else where the process was listed, think I called it changing Chinese firmware iirc.
If it's just a case of a re-flash of the firmware you're on, it's not that difficult.
Just use oxygen updater and grab the full firmware then do the local update using the app I mentioned above (listed in my Magisk/root guide)
I've never done this when not having the bootloader unlocked personally, but you can unlock and that'll wipe your phone with the recovery already on your device.
Only issue I have going down these routes is what else is missing? Do any of these processes stand up if we can't rely on the integrity of the OS that someone has put on and made a balls of it?
Sorry I know you may not agree but 30% is a small price to pay to avoid a brick and bring stability..
But that's me

zopostyle said:
Right, I agree with you. I recommended to install the coloros just to check if it's a compability issue.
You can try to reinstall you version and see what happens, just download it and flash it again.
Click to expand...
Click to collapse
That is a seriously good shout and would explain the fingerprint.

Hi guys, thank you again for helping me.
I tried installing again the uSB drivers, and ran again "fastboot flashing unlock" - it still telling me:
As far as I understand I have to unlock it for next step, right? (either for resetting back to colorOS or reinstalling oxygen)
I will try later tonight the other method (this magisk thing) - is this the link you're talking about?
Can you please also give me a link to download the full most up to date global Oxygen version and the CH Color one? i'll try both
Thanks !

For OxygenOS there is no A13 full yet...so you have to download A12 from this link: https://gauss-componentotacostmanua...22/03/24/a9f9e7ec682744c2ba606a366df587ac.zip
Source: https://www.xda-developers.com/oneplus-oxygenos-12-android-12-update-tracker/#oneplus10pro
The chinese one is hard to find, if I find it I post the link here...
Also this thread might help you: https://forum.xda-developers.com/t/oneplus-10-pro-ne2215-rooted.4431585

zopostyle said:
For OxygenOS there is no A13 full yet...so you have to download A12 from this link: https://gauss-componentotacostmanua...22/03/24/a9f9e7ec682744c2ba606a366df587ac.zip
Source: https://www.xda-developers.com/oneplus-oxygenos-12-android-12-update-tracker/#oneplus10pro
The chinese one is hard to find, if I find it I post the link here...
Also this thread might help you: https://forum.xda-developers.com/t/oneplus-10-pro-ne2215-rooted.4431585
Click to expand...
Click to collapse
Really is odd about them not being full... They're massive compared to conventional incremental updates. 4.05GB that's a hell of an incremental.
Haven't had to do it myself and it's sightly off topic but is the full version you'd use to recover a phone albeit without a functional MSM?
So fastboot flashing?
Cheers

Hi again,
So, i'm trying to follow the tutorial here. I got stuck already in the first step - I cannot extract the boot file using Fastboot Enhance:
This is although in this link I have downloaded a full version (EU version (NE2213_11.A.13)).
What should I do next please?

dkaro said:
Hi again,
So, i'm trying to follow the tutorial here. I got stuck already in the first step - I cannot extract the boot file using Fastboot Enhance:
View attachment 5624521
This is although in this link I have downloaded a full version (EU version (NE2213_11.A.13)).
What should I do next please?
Click to expand...
Click to collapse
As @zopostyle said earlier.. you'd need to use 12 mate. As that's the only full version available...13 won't cut it...you can extract the images using the button that says allow incremental, that's useful for extracting boot images for rooting.
But there's a reason why that's there, it's so you don't go ahead and flash it.... According to @zopostyle 12 is the only full version so that's what you would need.
Again I've not done this myself so perhaps wait for someone else to chime in what to do next.

Database Develop

welcome