Database Info

Question Unable to unlock bootloader, Tencent edition preloaded with global

Hi, I have the cn Tencent edition preloaded with ww rom
I was able to update to the latest 18.830 by copying the firmware to the phone itbauto recognized it.
I installed the unlock tool. Go through the steps the phone reboots back to the same state. No reset or format.
Help pls

Remove lock screen password
Try this
https://dlcdnets.asus.com/pub/ASUS/ZenFone/ZS673KS/AsusUnlock_1.0.0.7_210127_fulldpi.apk

sorankira said:
Remove lock screen password
Try this
https://dlcdnets.asus.com/pub/ASUS/ZenFone/ZS673KS/AsusUnlock_1.0.0.7_210127_fulldpi.apk
Click to expand...
Click to collapse
i did try this,
and tried fastboot.
none worked.
the issue as i understood from asus rog phones owners, is that tencent editions have 1 time unlock relock counter. and it was used when converted the frimware to global.
hence why unlock is troublesome.
i also heard that the same issue happened with ROG 3, and the had to wait to EDL firmware.

for visibility

Hey m8822,
Is this issue creating any problems for you?
For example, does this conversion from Tenscent to Global block the phone from receiving future OTAs?
I'd really appreciate your input because I am considering buying the ROG 5 from Aliexpress.

Same issue. Just can't root until someone drops some EDL firmware sadly.

do you know how to use edl firmware?. any link to detailed guide is appreciated

Psych0t1c20 said:
Same issue. Just can't root until someone drops some EDL firmware sadly.
Click to expand...
Click to collapse
Yes but even with this EDL firmware you need a the EDL tool to flash it, so you can`t flash yourself or am I wrong?

Hank87 said:
Yes but even with this EDL firmware you need a the EDL tool to flash it, so you can`t flash yourself or am I wrong?
Click to expand...
Click to collapse
Correct. Hopefully a tool is made sooner rather than later.

Hank87 said:
Yes but even with this EDL firmware you need a the EDL tool to flash it, so you can`t flash yourself or am I wrong?
Click to expand...
Click to collapse
the frimware has cmd scripts , so it seems flashing it is as simple as running the scripts
i tried with raw firmware and it was simple. no real action form user

m8822 said:
the frimware has cmd scripts , so it seems flashing it is as simple as running the scripts
i tried with raw firmware and it was simple. no real action form user
Click to expand...
Click to collapse
Link to the edl firmware?
Edit: Got it.

m8822 said:
the frimware has cmd scripts , so it seems flashing it is as simple as running the scripts
i tried with raw firmware and it was simple. no real action form user
Click to expand...
Click to collapse
Have you tried flashing this and then trying the unlock tool again?

Psych0t1c20 said:
Have you tried flashing this and then trying the unlock tool again?
Click to expand...
Click to collapse
no, i haven't tried.
i flashed edl firmware, got into a problem. i lost imei numbers.
also unlock is not working
im gonna try and fix that

Whats news? I also have a problem with the asus unlock utility

PesterevYasha said:
Whats news? I also have a problem with the asus unlock utility
Click to expand...
Click to collapse
unfortunately no news.

Guys maybe is like Asus rog phone 3 i managed to unlock bootloader when I boot into edl mode flash edl unbrink tool to rebuild bootloader flash raw cn Rom use unlock tool from Asus and bootloader unlock successful! So must wait for someone create the same tool for rog phone 5.
Sorry for bad English.

xaloundros said:
Guys maybe is like Asus rog phone 3 i managed to unlock bootloader when I boot into edl mode flash edl unbrink tool to rebuild bootloader flash raw cn Rom use unlock tool from Asus and bootloader unlock successful! So must wait for someone create the same tool for rog phone 5.
Sorry for bad English.
Click to expand...
Click to collapse
You have cn raw file for edl flash ? And this trick work?

TESxHUNTER said:
You have cn raw file for edl flash ? And this trick work?
Click to expand...
Click to collapse
to clarify this trick works for Asus Rog phone 3 and I don't have Rog 5 to test it.
Because when the sellers unlock and relock the phone after ww rom they mess up bootloader. Then when I flash the unbrink tool in edl mode after that the phone reboot into fastboot mode flash cn raw image phone start in original state. So after that unlock tool from Asus works normal. And then you can flash ww raw image again from fastboot mode. Maybe can happent for Rog 5.
But if your bootloader isn't mess up like mine you can easily flash raw cn rom(from faatboot mode) and try unlock tool..
I hope I helped.

Question Help restoring ROG Phone 5 to factory after root/bootloader unlock

Hey everyone
I have an ROG Phone 5 Tencent version that I purchased on eBay that has the WW ROM installed. I read after the fact that I shouldn't have bought one like this, but I'm stuck with it now.
I've rooted the phone and unlocked the bootloader, but now I want to put it back to the way it was by relocking the bootloader and installing the default raw WW image. Is there an easy way to undo everything I did and get it back to the way it was when I got it?
Thanks!

Hope everyone is staying safe!

Massonite said:
Hope everyone is staying safe!
Click to expand...
Click to collapse
Hi, thanks , hope you are safe as well.
in my humble inexperienced view
you should do the following.
1- backup everything.
2- download Raw firmware.
3- flash Raw firmware (Removes root)
4- relock the bootloader via adb/fastboot commands (you may not get another chance to unlock straightforwardly, there are shady ways but nothing on the surface as of yet)
here is this guy who has gone through the whole process.
he also has provided the raw files. I have flashed them my self so they should be fine.
Part 1 , Part 2
Stay safe.

m8822 said:
Hi, thanks , hope you are safe as well.
in my humble inexperienced view
you should do the following.
1- backup everything.
2- download Raw firmware.
3- flash Raw firmware (Removes root)
4- relock the bootloader via adb/fastboot commands (you may not get another chance to unlock straightforwardly, there are shady ways but nothing on the surface as of yet)
here is this guy who has gone through the whole process.
he also has provided the raw files. I have flashed them my self so they should be fine.
Part 1 , Part 2
Stay safe.
Click to expand...
Click to collapse
hey
i have make a mistake u have rog have and have a root i lock the bootloader after that the phone not working i know the wrong but i do what i can do now
when i try to flash boot write filed cant writing on lock bootloader
can help me

I was able to re-lock the phone. Please see here : https://forum.xda-developers.com/t/bootloader-rog-5.4265159/#post-84910571

jano83 said:
hey
i have make a mistake u have rog have and have a root i lock the bootloader after that the phone not working i know the wrong but i do what i can do now
when i try to flash boot write filed cant writing on lock bootloader
can help me
Click to expand...
Click to collapse
use raw firmware. in fastboot. if ou can not boot into fastboot you need edl unbrick. which is nt eyt available
File on MEGA
mega.nz
in fastboot open this file. flash_raw_and_wipe_data.cmd.
it should install ra firmware and format the device.

[SOLVED] Does Anyone Have a working rawprogram .xml and patch .xml to fix a hard bricked V500N?

EDIT: I don't need this anymore since I've fixed the problem
Mine stuck in EDL mode after I accidentally erased my partitions. I have followed this tutorial for LG G7, but I was unable to generate xml files required to flash the unpacked .dz firmware. I tried to search similar topic in this forum and G8 forum but it's a dead end.

Hi , how did you fix it , please help I'm in the same situation now

Bronnel said:
Hi , how did you fix it , please help I'm in the same situation now
Click to expand...
Click to collapse
wait I will make a tutorial later. What variant of V50 do you have? If it's the sprint variant you can just use this file https://forum.xda-developers.com/t/lg-v50-lost-sn-after-unbrick.4321877/post-85564585
if it's not, you have to extract your .KDZ with KDZtools from the Chinese forum to get the compatible .bin partitions.
Now I need a blank .qcn file to restore my IMEI because my .qcn backup file seems to be corrupted.

I have Sprint V50 unlocked , V450pm
I did use that file and flashed all partitions one by one but still stuck in EDL mode , I cannot reboot to system, I contacted paid service they claim that they can fix my device remotely , it costs 20+ USD , I'm not sure if can trust them
did you use rawprogram and patch xml, can you please show me how to do that?

Bronnel said:
I have Sprint V50 unlocked , V450pm
I did use that file and flashed all partitions one by one but still stuck in EDL mode , I cannot reboot to system, I contacted paid service they claim that they can fix my device remotely , it costs 20+ USD , I'm not sure if can trust them
did you use rawprogram and patch xml, can you please show me how to do that?
Click to expand...
Click to collapse
I only use the rawprogram0.xml - 6.xml in QFIL. Then, it will be in a boot loop condition, but you can access the download mode. Now you have to flash your stock .kdz firmware in the PARTITION DL mode, since the refurbish mode won't work. Though, I'm not sure if the KDZ of your variant is available, as I couldn't find them.

You are right KDZ not available for sprint , and I used rawprogram0.xml - 6.xml but only 0 and 4 are working others are not working it give sahara fail error

Bronnel said:
You are right KDZ not available for sprint , and I used rawprogram0.xml - 6.xml but only 0 and 4 are working others are not working it give sahara fail error
Click to expand...
Click to collapse
I think the Sahara failure is an error of USB connection than an error of the rawprogram files. Usually, if that happens, you need to restart the EDL mode. Maybe you can try flashing other V450 .kdz. For example, V450VM for Verizon.

you saved my life , you are right it was usb connection issue , my device boots to system without issue , but now volume buttons are not working

Bronnel said:
you saved my life , you are right it was usb connection issue , my device boots to system without issue , but now volume buttons are not working
Click to expand...
Click to collapse
you need to find a way to upgrade/downgrade the stock firmware.
If you happen to find a dummy .qcn backup from someone, please notify me. I have a hard time recovering my IMEI.

wibigdog said:
you need to find a way to upgrade/downgrade the stock firmware.
If you happen to find a dummy .qcn backup from someone, please notify me. I have a hard time recovering my IMEI.
Click to expand...
Click to collapse
My V50 is completely restored like new , IMEI is still there. so thank you for your guidance.
There is a trusted service that can restore your IMEI , I contacted them yesterday ,they are very good , they will restore your IMEI if you want , I will PM you their detail

wibigdog said:
wait I will make a tutorial later. What variant of V50 do you have? If it's the sprint variant you can just use this file https://forum.xda-developers.com/t/lg-v50-lost-sn-after-unbrick.4321877/post-85564585
if it's not, you have to extract your .KDZ with KDZtools from the Chinese forum to get the compatible .bin partitions.
Now I need a blank .qcn file to restore my IMEI because my .qcn backup file seems to be corrupted.
Click to expand...
Click to collapse
Pls help i cant find the compatible bin as almost every thread has only for sprint, my phone is korean variant

LawreNczzze said:
Pls help i cant find the compatible bin as almost every thread has only for sprint, my phone is korean variant
Click to expand...
Click to collapse
1. download the Korean KDZ
2. get the rawprogram.xml from the sprint backup
3. download the .exe version of KZDtool here: https://bbs.lge.fun/thread-69.htm. Btw, the link in the tutorial has been outdated, I found the correct URL using Google: https://www.lanzoux.com/ia1u5ub
4. follow the tutorial using google translate to get most of the .img files
5. follow this tutorial https://bbs.lge.fun/thread-75.htm to get the OP.img, because KDZtool won't work for this OP img. You'll need a hex editor.
6. Drag and replace everything in the original Sprint backup with the Korean .img files
7. Flash in QFIL with firehose and the rawprogram files from the Sprint backup
8. You'll finally be able to go into the download mode
9. Now flash the Korean KDZ in PARTITION DL mode, since the refurbish or upgrade mode won't work

wibigdog said:
1. download the Korean KDZ
2. get the rawprogram.xml from the sprint backup
3. download the .exe version of KZDtool here: https://bbs.lge.fun/thread-69.htm. Btw, the link in the tutorial has been outdated, I found the correct URL using Google: https://www.lanzoux.com/ia1u5ub
4. follow the tutorial using google translate to get most of the .img files
5. follow this tutorial https://bbs.lge.fun/thread-75.htm to get the OP.img, because KDZtool won't work for this OP img. You'll need a hex editor.
6. Drag and replace everything in the original Sprint backup with the Korean .img files
7. Flash in QFIL with firehose and the rawprogram files from the Sprint backup
8. You'll finally be able to go into the download mode
9. Now flash the Korean KDZ in PARTITION DL mode, since the refurbish or upgrade mode won't work
Click to expand...
Click to collapse
May i ask where did you get the correct lgup version and v50 dll so i can proceed. Thank you very much for the quick reply

wibigdog said:
1. download the Korean KDZ
2. get the rawprogram.xml from the sprint backup
3. download the .exe version of KZDtool here: https://bbs.lge.fun/thread-69.htm. Btw, the link in the tutorial has been outdated, I found the correct URL using Google: https://www.lanzoux.com/ia1u5ub
4. follow the tutorial using google translate to get most of the .img files
5. follow this tutorial https://bbs.lge.fun/thread-75.htm to get the OP.img, because KDZtool won't work for this OP img. You'll need a hex editor.
6. Drag and replace everything in the original Sprint backup with the Korean .img files
7. Flash in QFIL with firehose and the rawprogram files from the Sprint backup
8. You'll finally be able to go into the download mode
9. Now flash the Korean KDZ in PARTITION DL mode, since the refurbish or upgrade mode won't work
Click to expand...
Click to collapse
Or can you send me the whole process on how you revive your phone? I'm actually a noob and doesnt really know much about anything in here, I'm just hoping to see if I could still use the phone

You guys are fighting a really tough battle. If you’ve unlock your boot loader then android 12 GUI RC is the way to go! Just put your phone in fast boot mode and two flashes and your done.

hooutoo said:
You guys are fighting a really tough battle. If you’ve unlock your boot loader then android 12 GUI RC is the way to go! Just put your phone in fast boot mode and two flashes and your done.
Click to expand...
Click to collapse
Do you have more information? because I would like to flash android 12 release candidate instead of fighting with this phone any further. Thank you.

i delete all partition, i was reboot, but imei 0, can i fix this

hello i have a sprint v50 variant but i don't have recovery or fastboot mode i have unlocked bootloader

Question L2117 - Bootloop after successful MSMDownloadTool flash - Now what?

I have a T-Mobile OP9 that I just purchased used. The bootloader was unlocked and I received the file along with the phone. The phone was originally on A11 L2115 (but still showed L2117 in Settings / About). I rooted and grabbed the modemst1, modemst2, and persist.img files with Partition Backup before anything else. I then subsequently updated officially to A13 through an update via local storage then through the OTA updater and it was then fully seen as L2115. I then realized that the rom I wanted needed A12 firmware so I went back to A11 then unlocked bootloader again and attempted to update firmware only off the CrDroid A12L update page. I chose not to flash the modem during that flash and then afterwards my service stopped working. It read the IMEI and baseband and would recognize that it was T-Mobile but no calls/text/data. I then got the bright idea to go back to Tmobile A11 through MSM then unlock bootloader, root, and use Partition Backup to restore the modems and persist imgs. After that, even though I can successfully flash the full Tmo MSMDownload Tool ops file, it only bootloops. If the MSM tool can't fix it - is it done for?

es0tericcha0s said:
I have a T-Mobile OP9 that I just purchased used. The bootloader was unlocked and I received the file along with the phone. The phone was originally on A11 L2115 (but still showed L2117 in Settings / About). I rooted and grabbed the modemst1, modemst2, and persist.img files with Partition Backup before anything else. I then subsequently updated officially to A13 through an update via local storage then through the OTA updater and it was then fully seen as L2115. I then realized that the rom I wanted needed A12 firmware so I went back to A11 then unlocked bootloader again and attempted to update firmware only off the CrDroid A12L update page. I chose not to flash the modem during that flash and then afterwards my service stopped working. It read the IMEI and baseband and would recognize that it was T-Mobile but no calls/text/data. I then got the bright idea to go back to Tmobile A11 through MSM then unlock bootloader, root, and use Partition Backup to restore the modems and persist imgs. After that, even though I can successfully flash the full Tmo MSMDownload Tool ops file, it only bootloops. If the MSM tool can't fix it - is it done for?
Click to expand...
Click to collapse
Sounds like it's not factory resetting when running MSM tool. Boot into recovery and wipe device. Then it will boot.

Regrettably, I've already tried with and without wipes in recovery. I've successfully flashed the recommended T-mobile firmware and there seems to literally only be one option to try for this variant I've seen anywhere. I know the file, Downloader, drivers and USB cable work as I used it to successfully go back a couple of times before the reflashing of the modems and persist files. It also passes still without error but it'll reboot after it sets on the T-mobile boot up for a couple of minutes.
mattie_49 said:
Sounds like it's not factory resetting when running MSM tool. Boot into recovery and wipe device. Then it will boot.
Click to expand...
Click to collapse

es0tericcha0s said:
Regrettably, I've already tried with and without wipes in recovery. I've successfully flashed the recommended T-mobile firmware and there seems to literally only be one option to try for this variant I've seen anywhere. I know the file, Downloader, drivers and USB cable work as I used it to successfully go back a couple of times before the reflashing of the modems and persist files. It also passes still without error but it'll reboot after it sets on the T-mobile boot up for a couple of minutes.
Click to expand...
Click to collapse
U can fix ur bricked device anytime with op 9 pro india msm but i would say if u want try global u shuld try msm conversion without unocking bootloader if problem exist flash 2115 a11 with fastboot enhance u will be out of bootloop i have been there solved it this way

Thanks so much for the reply. I downloaded an Indian 9 Pro firmware but I couldn't get it to flash. Is there a specific one? I used the one recommended in the main thread for unbricking, I thought but I've been trying so many things at this point its blurring together.
Is it possible to fastbootd flash when locked to a different model's firmware?
rizzmughal said:
U can fix ur bricked device anytime with op 9 pro india msm but i would say if u want try global u shuld try msm conversion without unocking bootloader if problem exist flash 2115 a11 with fastboot enhance u will be out of bootloop i have been there solved it this way
Click to expand...
Click to collapse

I was able to recover with the Indian version - thanks! Still don't have my baseband or IMEI though.

es0tericcha0s said:
I was able to recover with the Indian version - thanks! Still don't have my baseband or IMEI though.
Click to expand...
Click to collapse
Flash modded tmo msm with target id india

rizzmughal said:
Flash modded tmo msm with target id india
Click to expand...
Click to collapse
I did try this last night. I am able to flash this successfully, but it sends me into a bootloop.
Same as the original Tmo MSM did before I flashed the Indian 9 Pro MSM (I haven't had luck changing the Target back to something that will work with the original Tmo MSM file yet). With or without factory data reset, I get a bootloop on a Tmobile version of the MSM. Boots up fine with Indian 9 Pro.
I can also switch to global firmware with the official 1+ zip after it boots with the Indian MSM either via temp custom recovery or via local storage updates but it still leaves me with null IMEI and no baseband. I've tried to flash just the Tmo NON-HLOS.bin file in fastbootd while on the Indian firmware and just got a bootloop too. It definitely seems related to the me screwing up the baseband / radio situation but seems odd that the normal fixes aren't sticking. At least I got it to boot to something, but it's still unuseable.

es0tericcha0s said:
I did try this last night. I am able to flash this successfully, but it sends me into a bootloop.
Same as the original Tmo MSM did before I flashed the Indian 9 Pro MSM (I haven't had luck changing the Target back to something that will work with the original Tmo MSM file yet). With or without factory data reset, I get a bootloop on a Tmobile version of the MSM. Boots up fine with Indian 9 Pro.
I can also switch to global firmware with the official 1+ zip after it boots with the Indian MSM either via temp custom recovery or via local storage updates but it still leaves me with null IMEI and no baseband. I've tried to flash just the Tmo NON-HLOS.bin file in fastbootd while on the Indian firmware and just got a bootloop too. It definitely seems related to the me screwing up the baseband / radio situation but seems odd that the normal fixes aren't sticking. At least I got it to boot to something, but it's still unuseable.
Click to expand...
Click to collapse
U cannot flash modem or anything thru fastboot without unlock bootloader

rizzmughal said:
U cannot flash modem or anything thru fastboot without unlock bootloader
Click to expand...
Click to collapse
Right, but I can go back to the Indian 9 Pro MSM then unlock. I just re-attempted the flash for the Tmobile MSM target IN and same - bootloop. It flashes everything successfully with no errors. I have tried with and without all of the boxes checked. It won't work with either Lite Firehose or SHA256 checked. Have flashed, reset, then flashed again. Doesn't seem to make much sense that one version will work but the actual one for my phone will not. I really, really dislike the T-Mobile variants of the past few 1+ phones. It really limits them and makes it a huge hassle to run anything custom.
I believe it is my EFS partition that is corrupted when I attempted to restore the modemst1 and modemst2 files through Partition Manager.

Update: I've fixed my baseband issues by fastboot wiping the modemst1 and 2 partitions. This has allowed me to now successfully flash and boot the Tmo firmware via the modded MSM for target IN. Now I am just left with repairing the IMEI which now reads 0.
Update 2: Was able to restore IMEI once I got the bootloader unlocked and reflashed my modemst1 and 2 with Fastboot Enhance.
Whew. Thanks for all the help!

es0tericcha0s said:
Right, but I can go back to the Indian 9 Pro MSM then unlock. I just re-attempted the flash for the Tmobile MSM target IN and same - bootloop. It flashes everything successfully with no errors. I have tried with and without all of the boxes checked. It won't work with either Lite Firehose or SHA256 checked. Have flashed, reset, then flashed again. Doesn't seem to make much sense that one version will work but the actual one for my phone will not. I really, really dislike the T-Mobile variants of the past few 1+ phones. It really limits them and makes it a huge hassle to run anything custom.
I believe it is my EFS partition that is corrupted when I attempted to restore the modemst1 and modemst2 files through Partition Manager.
Click to expand...
Click to collapse
That might be possible u shuld go for bootloader unlock first of all everything great to hear that u got it fixed

Question Need help no matter paid

So The device was perfect in le2115 mode but i flash os12 ota files by Fastbootd mode and device stuck on 9008
Then i realized The ota was le2120
Now i try flash GLO/IN/EU all MSM file's but its not take anyfile its giving me device image Not match error
In op9p IN can flash device & able to recover but in op9 this trick not work
I need to know is there anyway to unpack and edit details And flash device?
I mean it'll Not check any image but just flash?
If anyone able to help i can happily $ donate
Regards
Daniha

Have you tried reloading the phone using MSM?

wizardknight said:
Have you tried reloading the phone using MSM?
Click to expand...
Click to collapse
Reloading? You can explain It little bit more?

Daniha said:
Reloading? You can explain It little bit more?
Click to expand...
Click to collapse
OnePlus Community
Introducing our new OnePlus Community experience, with a completely revamped structure, built from the ground-up.
community.oneplus.com

Daniha said:
So The device was perfect in le2115 mode but i flash os12 ota files by Fastbootd mode and device stuck on 9008
Then i realized The ota was le2120
Now i try flash GLO/IN/EU all MSM file's but its not take anyfile its giving me device image Not match error
In op9p IN can flash device & able to recover but in op9 this trick not work
I need to know is there anyway to unpack and edit details And flash device?
I mean it'll Not check any image but just flash?
If anyone able to help i can happily $ donate
Regards
Daniha
Click to expand...
Click to collapse
Did you try unchecking (or checking) sha256 and unchecking (or checking) use lite firehose on msm tool options, top right?
(By the way, I dunno if you are aware but someone has solved the problem for OP9P IN target problem after using Indian MSM tool to recover device. They flashed a param img from stock Target phone and were able to use the original Target (Tmo in this case) msm tool to get out of IN target and back to original)