Firstly thanks in advance for any individual kind enough to help me or point me in the right direction. Here is a brief synopsis of what has taken place
- Purchased a Tencent Rog 2 off eBay, it appeared to already have a WW image (didn't take note of the version) but the signature was not Chinese. So stupid me assumed I could simply change the fingerprint file (nothing else) and my Google pay etc would work in my region.
- I followed this a Youtube guide fairly accurately (I believed) from around the 5 minutes in section ...
"Guide for Asus Rog 2 Tencent Edition to Full Global Rom Conversion, enable Themes, pass SafetyNet" from youtube
ignoring the first 5-minute section regarding changing to the WW image as I thought there was not much point as I already had a WW image. I remember I changed my fingerprint file, changed my bootloader rooted the device then backed out the changes and as soon as I relocked the bootloader I got ....
"Slot _a is unbootable"
I assume I'm screwed? I now get errors if I try to change the bootloader again and I also get
wildstallionuk said:
Firstly thanks in advance for any individual kind enough to help me or point me in the right direction. Here is a brief synopsis of what has taken place
- Purchased a Tencent Rog 2 off eBay, it appeared to already have a WW image (didn't take note of the version) but the signature was not Chinese. So stupid me assumed I could simply change the fingerprint file (nothing else) and my Google pay etc would work in my region.
- I followed this a Youtube guide fairly accurately (I believed) from around the 5 minutes in section ...
"Guide for Asus Rog 2 Tencent Edition to Full Global Rom Conversion, enable Themes, pass SafetyNet" from youtube
ignoring the first 5-minute section regarding changing to the WW image as I thought there was not much point as I already had a WW image. I remember I changed my fingerprint file, changed my bootloader rooted the device then backed out the changes and as soon as I relocked the bootloader I got ....
"Slot _a is unbootable"
I assume I'm screwed? I now get errors if I try to change the bootloader again and I also get
Click to expand...
Click to collapse
Similar to this guys issue but mine references Slot A rather than B?
https://forum.xda-developers.com/rog-phone-2/help/bicked-slot-b-unbootable-t3991287
Just flash the RAW fw.
VZTech said:
Just flash the RAW fw.
Click to expand...
Click to collapse
Chinses buddy? But bootloader is locked again is that of relevance?
wildstallionuk said:
Chinses buddy? But bootloader is locked again is that of relevance?
Click to expand...
Click to collapse
Using this command again presumably mate..
"flashall_AFT.cmd"
ensuring only the RAW is on the same directory, I thought I had tried that but I might have extracted it. Will report back with results ...
wildstallionuk said:
Chinses buddy? But bootloader is locked again is that of relevance?
Click to expand...
Click to collapse
Flash whatever version raw you want to end up on. Bl doesn't matter.
VZTech said:
Flash whatever version raw you want to end up on. Bl doesn't matter.
Click to expand...
Click to collapse
Don't seem to be having any luck Am I being a noob somehow ...
##################################################################
####################### FLASH RAW FILE ########################
##################################################################
## RAW: CN_ZS660KL_16.0631.1908.12_M3.13.33.28-ASUS_1.1.161_Phone-user.raw.zip
## ERASE DATA: 0
## SSN:
==================================================================
fastboot: usage: unknown command version
[command] : fastboot.exe flash all CN_ZS660KL_16.0631.1908.12_M3.13.33.28-ASUS_1.1.161_Phone-user.raw.zip
"FAILED, fastboot.exe flash all CN_ZS660KL_16.0631.1908.12_M3.13.33.28-ASUS_1.1.161_Phone-user.raw.zip failure, EXIT!"
c:\>
you can repair your phone without EDL mode! https://forum.xda-developers.com/rog-phone-2/how-to/repair-rog2-phone-edl-modeofficial-t4012175
Related
Dear everyone, i'm just a newbie on Phone and stuffs like coding or decoding.
Let me explain clearly what happen to my phone recently and why i have open this thread for asking for seriously help.
From the very beginning i have follow instruction from this thread:
https://forum.xda-developers.com/rog-phone-2/how-to/asus-rog2-cn-phone-flash-ww-root-t4008229
It said we could change the vendor code from CN to WW by edit COUNTRY from persist in 9008 mode (mnt/vendor/persist) or lately called persist.img without Root or unlock bootloader the device (which lately breached the fuse by using command fastboot oem check-fuse in fastboot).
Anything not gone wrong until i reach the step called "1.ReadPersist.bat" and it return the "persist.img" with not correct size of the file;
less than 32.768 Kb, but i didn't recognize until finish using Ultra Edit (hex edit) and write back persist.img (which has wrong size of package).
That make my device show not correct serial number as is: C4ATAS00000
Also recognize that the device is triggered Widevine Security from L1 to L3, Device is not certified in Google Playstore and other annoying problems.
My phone is not rooted and not unlocked bootloader then i have no reason why they show me L3 widevine even i have reflash raw firmware, unlock and relock bootloader.
After get contact with other Asus ROG phone 2 user, i have able to get a new persist.img and start to looking deep down what has contain inside persist.img
First effort, i have identified that in persist.img contains:
1. IMEI (second imei) (able to find it via command fastboot oem device-info)
2. Serial number (SSN) (able to find it via command fastboot oem device-info)
3. ISN (able to find it via command fastboot oem device-info)
4. Wifi MAC Address pool (able to find it via command fastboot oem system-info)
5. Bluetooth MAC Address. (not able to find it anywhere )
Use the same way as before, entering 9008 mode, edit new persist.img to match with items 1,2,3 above; then write back file persist.img to my device.
My phone now has gained back Serial Number, able to unlock bootloader via Official Asus apk on Homepage, resolve some major issue such Device is certified...etc
I also have tried to unlock - relock bootloader to perform root or so on but no luck to restore widevine L1.
A lot of people in my country has same problem as mine, i will be very thanks if anyone has any idea what has triggered widevine from L1 to L3 when we flashed wrong persist.img into Device.
If anyone concern about my persist.img which has L3 widevine security and L1 could contact direct to me via inbox/pm.
Thanks.
Anyone? Please?
tuannghia1985 said:
Anyone? Please?
Click to expand...
Click to collapse
I don't think you can get the widevine back because you have changed your system. I did a similar guide and now I don't have signal.
You can try this guide here
https://forum.xda-developers.com/ro...-l3-issues-t4049411/post81742183#post81742183
I would really appreciate it if you could send me yours so I can get my signal back
Sk1t said:
I don't think you can get the widevine back because you have changed your system. I did a similar guide and now I don't have a signal.
You can try this guide here
https://forum.xda-developers.com/ro...-l3-issues-t4049411/post81742183#post81742183
I would really appreciate it if you could send me yours so I can get my signal back
Click to expand...
Click to collapse
Many people have lost signal due to flash raw ROM via QFILs, I and my friend is working on this problem and try best to work it out. We have Qcn backup right now and try to edit, convert it to correct imei/meid. No signal right now. For EFS, both of us is not rooted/unlocked bootloader yet (it takes us a lot of time for backup and restore those 40Gb data on phone - during day works) then please wait until we get new things.
tuannghia1985 said:
Many people have lost signal due to flash raw ROM via QFILs, I and my friend is working on this problem and try best to work it out. We have Qcn backup right now and try to edit, convert it to correct imei/meid. No signal right now. For EFS, both of us is not rooted/unlocked bootloader yet (it takes us a lot of time for backup and restore those 40Gb data on phone - during day works) then please wait until we get new things.
Click to expand...
Click to collapse
Yes I believe I followed this guide here.
https://forum.xda-developers.com/rog-phone-2/how-to/guide-restoring-imei-efs-erasing-t4071159
I mounted the persist image in this and it's basically empty with no actual files. I don't know enough about this and don't want to go pointing fingers but I suspect that is where I messed it up.
Sk1t said:
Yes I believe I followed this guide here.
https://forum.xda-developers.com/rog-phone-2/how-to/guide-restoring-imei-efs-erasing-t4071159
I mounted the persist image in this and it's basically empty with no actual files. I don't know enough about this and don't want to go pointing fingers but I suspect that is where I messed it up.
Click to expand...
Click to collapse
thanks for sending me a guide, I will follow that instruction. for persist.img you could use mine for find and editing by ultraedit.
https://drive.google.com/drive/folders/1k8EbD_mdLoIifauW9WORVVA6VIMupmmP?usp=sharing
tuannghia1985 said:
thanks for sending me a guide, I will follow that instruction. for persist.img you could use mine for find and editing by ultraedit.
https://drive.google.com/drive/folders/1k8EbD_mdLoIifauW9WORVVA6VIMupmmP?usp=sharing
Click to expand...
Click to collapse
https://forum.xda-developers.com/rog-phone-2/how-to/rog2-android10-twrp-wzsx150-t4027313
Thank you very much sir! I've tried this while this does contain more files than my current persist which is just empty folders it has not fixed my signal issue.
https://forum.xda-developers.com/rog-phone-2/how-to/rog2-android10-twrp-wzsx150-t4027313
This TWRP tool has more backup partitions and I think it could be useful in your quest.
I'm not sure which partitons I need but I suspect efs is one of them.
ALSO:
I assume you edited the persist image and edited some things as I the SSN number I put my own one in. It still has no signal , was there anything else you have changed?. I have and cannot power on the phone's modem with the phone code *#4636#*.
Help me sir, i cant update dan unlock my bootloader since my phone show wrong serial number C4ATAS00000
I also did the tutorial for this topic 9008, serial number lost asus tool gave widevine L3 network error persist all changed.
I was already trying to fix it for 2 months. I went back to CN ww for many times without counting the raw RAW wink countless times, several versions and nothing.
Until I found your topic that really saved me and I believe it will help many because in that period I saw many reports of people trying to use the Asus unlocking tool and reporting a network error as well as me this occurs when I lose Rog's serial number .C4ATAS00000.
I recovered the serial number, IMEi, ISN. And it was even converted from CN to WW.
Grateful friend for your effort.
hi i have the same problem with my asus rog phone zs600kl
tuannghia1985 said:
Dear everyone, i'm just a newbie on Phone and stuffs like coding or decoding.
Let me explain clearly what happen to my phone recently and why i have open this thread for asking for seriously help.
From the very beginning i have follow instruction from this thread:
https://forum.xda-developers.com/rog-phone-2/how-to/asus-rog2-cn-phone-flash-ww-root-t4008229
It said we could change the vendor code from CN to WW by edit COUNTRY from persist in 9008 mode (mnt/vendor/persist) or lately called persist.img without Root or unlock bootloader the device (which lately breached the fuse by using command fastboot oem check-fuse in fastboot).
Anything not gone wrong until i reach the step called "1.ReadPersist.bat" and it return the "persist.img" with not correct size of the file;
less than 32.768 Kb, but i didn't recognize until finish using Ultra Edit (hex edit) and write back persist.img (which has wrong size of package).
That make my device show not correct serial number as is: C4ATAS00000
Also recognize that the device is triggered Widevine Security from L1 to L3, Device is not certified in Google Playstore and other annoying problems.
My phone is not rooted and not unlocked bootloader then i have no reason why they show me L3 widevine even i have reflash raw firmware, unlock and relock bootloader.
After get contact with other Asus ROG phone 2 user, i have able to get a new persist.img and start to looking deep down what has contain inside persist.img
First effort, i have identified that in persist.img contains:
1. IMEI (second imei) (able to find it via command fastboot oem device-info)
2. Serial number (SSN) (able to find it via command fastboot oem device-info)
3. ISN (able to find it via command fastboot oem device-info)
4. Wifi MAC Address pool (able to find it via command fastboot oem system-info)
5. Bluetooth MAC Address. (not able to find it anywhere )
Use the same way as before, entering 9008 mode, edit new persist.img to match with items 1,2,3 above; then write back file persist.img to my device.
My phone now has gained back Serial Number, able to unlock bootloader via Official Asus apk on Homepage, resolve some major issue such Device is certified...etc
I also have tried to unlock - relock bootloader to perform root or so on but no luck to restore widevine L1.
A lot of people in my country has same problem as mine, i will be very thanks if anyone has any idea what has triggered widevine from L1 to L3 when we flashed wrong persist.img into Device.
If anyone concern about my persist.img which has L3 widevine security and L1 could contact direct to me via inbox/pm.
Thanks.
Click to expand...
Click to collapse
hi i flash me rog phone zs600kl afther flash with Qfil me serial and imei has chanced serial is now c4atas000000 i need to restore it back too JCAZGV040926299 i dont have root and no bootloader unlocked cant unlock help me how i can get me seral back to restore i dont know howto edit persist
Serial number wrong
Hi
My device was flashed via a third party supplier and the serial number is wrong, so i cannoy unlock the bootloader. Can you please explain what steps do I need to take to amend the serial number?
Thanks
tuannghia1985 said:
Dear everyone, i'm just a newbie on Phone and stuffs like coding or decoding.
Let me explain clearly what happen to my phone recently and why i have open this thread for asking for seriously help.
From the very beginning i have follow instruction from this thread:
https://forum.xda-developers.com/rog-phone-2/how-to/asus-rog2-cn-phone-flash-ww-root-t4008229
It said we could change the vendor code from CN to WW by edit COUNTRY from persist in 9008 mode (mnt/vendor/persist) or lately called persist.img without Root or unlock bootloader the device (which lately breached the fuse by using command fastboot oem check-fuse in fastboot).
Anything not gone wrong until i reach the step called "1.ReadPersist.bat" and it return the "persist.img" with not correct size of the file;
less than 32.768 Kb, but i didn't recognize until finish using Ultra Edit (hex edit) and write back persist.img (which has wrong size of package).
That make my device show not correct serial number as is: C4ATAS00000
Also recognize that the device is triggered Widevine Security from L1 to L3, Device is not certified in Google Playstore and other annoying problems.
My phone is not rooted and not unlocked bootloader then i have no reason why they show me L3 widevine even i have reflash raw firmware, unlock and relock bootloader.
After get contact with other Asus ROG phone 2 user, i have able to get a new persist.img and start to looking deep down what has contain inside persist.img
First effort, i have identified that in persist.img contains:
1. IMEI (second imei) (able to find it via command fastboot oem device-info)
2. Serial number (SSN) (able to find it via command fastboot oem device-info)
3. ISN (able to find it via command fastboot oem device-info)
4. Wifi MAC Address pool (able to find it via command fastboot oem system-info)
5. Bluetooth MAC Address. (not able to find it anywhere )
Use the same way as before, entering 9008 mode, edit new persist.img to match with items 1,2,3 above; then write back file persist.img to my device.
My phone now has gained back Serial Number, able to unlock bootloader via Official Asus apk on Homepage, resolve some major issue such Device is certified...etc
I also have tried to unlock - relock bootloader to perform root or so on but no luck to restore widevine L1.
A lot of people in my country has same problem as mine, i will be very thanks if anyone has any idea what has triggered widevine from L1 to L3 when we flashed wrong persist.img into Device.
If anyone concern about my persist.img which has L3 widevine security and L1 could contact direct to me via inbox/pm.
Thanks.
Click to expand...
Click to collapse
How do you edit persist.img and where's the position of the imei and others in persist.img? Because I tried to open persist.img using Hex editor, but I'm confuse because I don't know where's the imei, ssn, isn, wifi and bt. I lost baseband, imei and wifi.
can someone please help me ? my ROG2 is dead, but lineage and omni roms boot the phone but no sim card and no touch screen, i have to connect OTG mouse !!! so i think it's caused by a corrupted persist file, and when i write : fastboot oem device-info the phone returns random numbers !!!
$ fastboot oem device-info
(bootloader) Verity mode: true
(bootloader) Device unlocked: true
(bootloader) Device critical unlocked: true
(bootloader) Charger screen enabled: true
(bootloader) Device authorized: false
(bootloader) Device authorized2: false
(bootloader) ABL : CS1.2(00125)-8-WW-user
(bootloader) SSN : 111111111111111
(bootloader) ISN : FFAABBCC123456789
(bootloader) IMEI : 111111111111111
(bootloader) CID : ASUS
(bootloader) Project : ZS660KL_L
(bootloader) DT ID : 91
(bootloader) CPU ID : 0 (12LAYER)
(bootloader) Feature ID : 6 (AC_12LAYER)
(bootloader) JTAG ID : 5 (0x300A50E1)
(bootloader) SB=Y
(bootloader) TotalDMCounter : 14
(bootloader) DMCounter : 4
(bootloader) SlotARetryCounter : 68
(bootloader) SlotAUnbootableCounter : 4
(bootloader) SlotBRetryCounter : 15
(bootloader) SlotBUnbootableCounter : 1
(bootloader) BOOT_COUNT : 2478
(bootloader) LOCK_COUNT : 4
(bootloader) Check_APDP : 0
(bootloader) Check_MSADP : 0
(bootloader) rawdump_en : false
(bootloader) Current Slot : a
(bootloader) Slot_a bootable : Bootable
(bootloader) AVB Verity : Enable
(bootloader) Verify vbmeta ret : 5
(bootloader) CN Low Cost Tar Status : false
(bootloader) UART ON : false
OKAY [ 0.146s]
can someone please provide a clean persist file, and tell me where i can find SSN ISN and IMEI numbers other than this command ??
Please refresh the persist.img link if you can, i have the same problem
tuannghia1985 said:
thanks for sending me a guide, I will follow that instruction. for persist.img you could use mine for find and editing by ultraedit.
https://drive.google.com/drive/folders/1k8EbD_mdLoIifauW9WORVVA6VIMupmmP?usp=sharing
Click to expand...
Click to collapse
Can you re upload the persist.img? My phone still got issue no imei, no wifi and no baseband thanks
Hi,
This is gonna be very short :
As you can see, flashing custom roms/firmwares on (all) Xiaomi devices (after introducing project treble by Google) became a high risky business especially for noobs.
So here is some advice to avoid problems :
1- before flashing any firmware/custom rom : make sure you never choose relock bootloader in MiFlashTools (to avoid hard brick)
2- if you want to relock your bootloader : for example, if your device was shipped with a chinese firmware and you already have unlocked your bootloader, make sure you flash the same regional firmware (chinese one) before relocking it again. Any region mixing = hard brick ! (common error)
3- Mixing firmwares : if your device was shipped with a global/eea firmware and you want to flash a chinese firmware (for a specific rom) or vice versa, use fastboot one but again "don't relock your bootloader" (otherwise = hard brick)
4- tips : before using MiFlashTools, delete .bat files with relock and factory (if you want to keep your bootloader unlocked)
5- never buy a device with unlocked bootloader !
*********
About Anti-Rollback :
Mi 9 Lite / CC9 is not an anti-rollback enabled device, so here you can downgrade from a higher firmware version (10:Q) to the lower one (9ie) ... However, you can't relock your bootloader even if you use a firmware for the same region !
=> Downgrade = possible / Relocking the bootloader is not allowed for a lower android version +++
Conclusion :
NEVER RELOCK YOUR BOOTLOADER IN ALL CASES !
Thank you, very helpful! Can you provide a source about Mi 9 Lite/CC9 definitely NOT having anti-rollback enabled?
.M.D. said:
Thank you, very helpful! Can you provide a source about Mi 9 Lite/CC9 definitely NOT having anti-rollback enabled?
Click to expand...
Click to collapse
fastboot getvar anti
anti : 1 means anti-rollback disabled
read here
gringo80 said:
Mi 9 Lite / CC9 is not an anti-rollback enabled device, so here you can downgrade from a higher firmware version (10:Q) to the lower one (9ie) ... However, you can't relock your bootloader even if you use a firmware for the same region !
Click to expand...
Click to collapse
Are you sure about that? I just asked similar question (downgrading 11.3.9.0 -> 11.3.5.0) a few days ago, and people here stated that this is possible with relocking, and even without unlocking at all.
obiwanbartek said:
Are you sure about that? I just asked similar question (downgrading 11.3.9.0 -> 11.3.5.0) a few days ago, and people here stated that this is possible with relocking, and even without unlocking at all.
Click to expand...
Click to collapse
They are both 9ie !
Downgrade means from a higher android version to a lower one.
gringo80 said:
They are both 9ie !
Downgrade means from a higher android version to a lower one.
Click to expand...
Click to collapse
OK. So downgrading within one major android version is possible without relock, but going down with major android version requires unlock, right?
I have successfully downgraded from 10 to 9 without re-locking. so its possible
kingofmb said:
I have successfully downgraded from 10 to 9 without re-locking. so its possible
Click to expand...
Click to collapse
Ok, but did you unlocked it first? Or was it locked all the time?
obiwanbartek said:
OK. So downgrading within one major android version is possible without relock, but going down with major android version requires unlock, right?
Click to expand...
Click to collapse
Always Unlock your bootloader before taking any action in your device !
Flashing = Bootloader unlocked (always for your safety)
Staying always locked = Staying in Official MIUI (for your safety)
Read again the OP for more information.
gringo80 said:
4- tips : before using MiFlashTools, delete .bat files with relock and factory (if you want to keep your bootloader unlocked)
NEVER RELOCK YOUR BOOTLOADER IN ALL CASES !
Click to expand...
Click to collapse
this saved my xiaomi life, after few attempts i got some errors, then i rerun miflashtool, selected IMG and everything and as I forgot that i reran miflashtool it stayed on default "Clean all and lock" and i pressed flash, few seconds of mini hearth attacks as I realised my Xiaomi is now dead, luckily before starting anything I deleted all lock files from image rom folder and it said error: "could not find flash_all_relock.bat"
thanks once again, really best advice since u can forget to tick clean all and when you rerun MiFlashTool it goes back to default which is clean all and lock!
Hi, is the november 2018 version the latest version of MiFlashTools?
Any work-around?
Was purchased with WW ROM.
Switching between CN/ WW not an issue (via flashing RAW).
Also can upgrade/ downgrade within the CN or WW firmwares. Copying an older FW .zip into Internal Storage but renaming it to a newer FW name (same naming format) allows 'system update' to downgrade CN to CN/ WW to WW (may need a re-start to detect the FW .zip file).
OEM unlocking option is completely missing under Developer Options.
I assume OEM unlocking option is still there (even if greyed out) in Global variant ROG 3??
No luck unlocking Bootloader (and therefore getting Root access) via:
- ASUS Unlock tool --> App looks to work fine but restarts system with BL untouched/ remains unlocked.
- Tool_All_in_One by mauronofrio --> ROG 3 not listed in supported device list; device seems to be recognised by this tool; unlock BL attempt results in failure/ proprietary lock message.
- fastboot oem asus-lock (or asus-unlock ?) --> fails as not authorised/ unlock token missing.
- Flashing RAW 'open ROM' (inside EDL unbrick tool folder) --> allows OEM unlocking but cannot switch to CN/ WW ROM; nor allows BL unlock as per above methods. Needed to flash RAW CN/ WW to get back to normal FW.
Is it possible to get modified WW FW or RAW with patched Boot.img injected in?
Or any other work-around for unlocking BL or Root? (besides returning the device!!)
=================================================================
UPDATE
Tencent (CN) ROG 3 with WW ROM pre-loaded @ point of purchase as new --> definitely able to unlock Bootloader and Root the phone.
I managed to do it after flashing the latest CN .zip version (at the time = 0.78). Other people have done it after flashing latest WW .zip ROM.
Used the official ASUS unlock tool to unlock Bootloader (may take several repeat attempts). I then flashed (from CN) to latest WW .zip (no need if already on WW).
There will be no "OEM unlocking" option under developer options (no need).
elmor0 said:
- Flashing RAW 'open ROM' (inside EDL unbrick tool folder) --> allows OEM unlocking but cannot switch to CN/ WW ROM; nor allows BL unlock as per above methods. Needed to flash RAW CN/ WW to get back to normal FW. )
Click to expand...
Click to collapse
Can you OEM Unlock and boot loader unlock with flashin by EDL? Or I don’t understand very well
afcasasfranco said:
Can you OEM Unlock and boot loader unlock with flashin by EDL? Or I don’t understand very well
Click to expand...
Click to collapse
There's a RAW file in EDL folder - flashing this results in an 'open ROM' (looks like a pre-release/ developer testing ROM)
--> booting into this ROM gives option of OEM unlock which can be toggled to on (as well as USB debugging)
--> however still cannot Bootloader unlock using the methods I listed above.
The only solution is to unlock using third parties , there is a guy who unlock for 50 usd a greedy chineese , he is legit but he is a jerk ,my friend unlocked 3 devices using him .
Pm : for his telegram but you have to negociate for the price .
yes, you guys, here use Ark with this 100% unlocked, I unlocked my tencent strix, I advise you to try to download from the off site just for strix tencent !!! further link here >>>>>https://www.asus.com/Phone/ROG-Phone-3-Strix-Edition/HelpDesk_Download/
bouyhy01 said:
The only solution is to unlock using third parties , there is a guy who unlock for 50 usd a greedy chineese , he is legit but he is a jerk ,my friend unlocked 3 devices using him .
Pm : for his telegram but you have to negociate for the price .
Click to expand...
Click to collapse
If unofficial way exists to unlock Bootloader (on Tencent variant that came with WW), I'd rather await XDA help.
Thanks for letting me know anyways.
Gayrat1999 said:
yes, you guys, here use Ark with this 100% unlocked, I unlocked my tencent strix, I advise you to try to download from the off site just for strix tencent !!! further link here >>>>>https://www.asus.com/Phone/ROG-Phone-3-Strix-Edition/HelpDesk_Download/
Click to expand...
Click to collapse
What's Ark?
I've already tried this tool - did not unlock BL for tencent variant with WW (it was non-strix though).
Gayrat1999 said:
yes, you guys, here use Ark with this 100% unlocked, I unlocked my tencent strix, I advise you to try to download from the off site just for strix tencent !!! further link here >>>>>https://www.asus.com/Phone/ROG-Phone-3-Strix-Edition/HelpDesk_Download/
Click to expand...
Click to collapse
You are the man! My Tencent phone with latest WW firmware now shows the bootloader is unlocked! I'm going through the initial setup due to the phone getting wiped, and will to try rooting later.
dutchguy7 said:
You are the man! My Tencent phone with latest WW firmware now shows the bootloader is unlocked! I'm going through the initial setup due to the phone getting wiped, and will to try rooting later.
Click to expand...
Click to collapse
Your Tencent is Strix or non-Strix?
Did it already have "OEM unlocking" toggle option under Developer Options?
Gayrat1999 said:
yes, you guys, here use Ark with this 100% unlocked, I unlocked my tencent strix, I advise you to try to download from the off site just for strix tencent !!! further link here >>>>>https://www.asus.com/Phone/ROG-Phone-3-Strix-Edition/HelpDesk_Download/
Click to expand...
Click to collapse
elmor0 said:
Your Tencent is Strix or non-Strix?
Did it already have "OEM unlocking" toggle option under Developer Options?
Click to expand...
Click to collapse
It's the non-strix and it did not even have the oem unlocking toggle on, oddly enough it still doesn't.
dutchguy7 said:
It's the non-strix and it did not even have the oem unlocking toggle on, oddly enough it still doesn't.
Click to expand...
Click to collapse
That's interesting - I thought my OEM was missing all along because of Tencent with WW (therefore Bootloader relocked).
Which version of WW firmware were you on when you BL unlocked?
Did you use the link above for the (Strix) Asus unlock tool? Do you get a "PIN password missing" pop-up message when you press the unlock icon using this tool?
How did you know BL unlock was successful? Did you confirm that BL is unlocked?
elmor0 said:
That's interesting - I thought my OEM was missing all along because of Tencent with WW (therefore Bootloader relocked).
Which version of WW firmware were you on when you BL unlocked?
Did you use the link above for the (Strix) Asus unlock tool? Do you get a "PIN password missing" pop-up message when you press the unlock icon using this tool?
How did you know BL unlock was successful? Did you confirm that BL is unlocked?
Click to expand...
Click to collapse
I'm on the latest firmware 9/30 which I got from here https://www.asus.com/Phone/ROG-Phone-3/HelpDesk_BIOS/ and I used the tool provided from Gayrat1999. I get the warning that the bootloader is unlocked when restarting the phone and I confirmed with the All in One tool from here https://forum.xda-developers.com/as...sus-rog-phone-3-zs661ks-files-unlock-t4154141 (I had to delect ROG Phone 2)
dutchguy7 said:
I'm on the latest firmware 9/30 which I got from here https://www.asus.com/Phone/ROG-Phone-3/HelpDesk_BIOS/ and I used the tool provided from Gayrat1999. I get the warning that the bootloader is unlocked when restarting the phone and I confirmed with the All in One tool from here https://forum.xda-developers.com/as...sus-rog-phone-3-zs661ks-files-unlock-t4154141 (I had to delect ROG Phone 2)
Click to expand...
Click to collapse
I think the issue was the FW(?) as needed the latest one (or Asus have managed to sort the issue out @ their end) --> I have just now managed to finally (yes!) unlock my bootloader.
After several attempts, I managed to do it on latest CN (.78) with the CN Asus unlock tool.
(Looking at Asus unlock tool names/ versions on CN/ Global websites including the Strix version - They all seem to be the same ones).
The BL unlock sticks when I flash back to WW (latest @ .78).
Will be rooting now!
Looks like Tencent variant (with pre-flashed WW at point of purchase) is BL unlockable & Root-able indeed!!
Confirmed.
elmor0 said:
I think the issue was the FW(?) as needed the latest one --> I have just now managed to finally (yes!) unlock my bootloader.
After several attempts, I managed to do it on latest CN (.78) with the CN Asus unlock tool.
(Looking at Asus unlock tool names/ versions on CN/ Global websites including the Strix version - They all seem to be the same ones).
I the BL unlock sticks when I flash back to WW (latest @ .78).
Will be rooting now!
Looks like Tencent variant (with pre-flashed WW at point of purchase) is BL unlockable & Root-able indeed!!
Confirmed.
Click to expand...
Click to collapse
I'm glad it worked for you too! I just successfully rooted mine, cheers!
dutchguy7 said:
I'm glad it worked for you too! I just successfully rooted mine, cheers!
Click to expand...
Click to collapse
Happy rooting/ modding.
Hoping for Viper4Arise module to utilise potential of the excellent stereo speakers.
Hi, I also have the tencent version with latest ww firmware. I was also able to use the asus unlocker to unlock my bootloader. I've been out of the android rooting scene for a while though and was wondering if I could have some help with root. What root method did you use? I used Magisk and was able to create a modified boot img, but when I flashed it (and it confirmed the flash was successful, this was after a failed attempt before using asus unlocker where it said device was still locked) but checking with root checker, the device still seems to be unrooted. Did I miss a step, or should I use a different method altogether? Thanks.
Nevermind I figured it out. Flashed in TWRP, used that to install magisk zip, then installed magisk manager, done. Disregard.
Gayrat1999 said:
yes, you guys, here use Ark with this 100% unlocked, I unlocked my tencent strix, I advise you to try to download from the off site just for strix tencent !!! further link here >>>>>https://www.asus.com/Phone/ROG-Phone-3-Strix-Edition/HelpDesk_Download/
Click to expand...
Click to collapse
there are no downloads on that page, bro.
Try here:
https://www.asus.com/ca-en/Phone/ROG-Phone-3/HelpDesk_BIOS/
@elmor0 i'm on .100 firmware tencent... can i flash a RAW WW .78 firmware to convert into global at the same time downgrade?
if yes, i'll just have to change .78 to .101 right?
or do i have to downgrade CN .100 to CN .78 by changing the .78 to .101 and put it on internal storage.then flash WW .78 to convert my device to global?
I completely uninstalled magisk, now I don't know how to delete twrp and relock bootloader. Is it safe? Will it erase all my data?
Not true bencozzy. I've already locked and unlocked bootloader second time. Locking bootloader did not wipe my phone.
As for twrp you're right. Just place zip file of your firmware in root folder of storage. If you have latest firmware it won't trigger update so change name of your file to a higher one. Like.. 147—user.zip to 148 and so on.
bencozzy said:
WW version?
Click to expand...
Click to collapse
Yep. CN Converted. I got it with closed bootloader and ww firmware. As I've never played with custom roms etc first two weeks were crazy for me. Can't remember how many times I've reinstalled firmware but opened and closed bootloader at least two times.
One time got wiped after closing but I had stock firmware rooted and after closing bootloader it wouldn't load so had to wipe using recovery.
bencozzy said:
You can only unlock the bootloader once on the rog 3 so it's better to leave it unlocked. Just flash a full firmware it will overwrite TWRP.
Click to expand...
Click to collapse
That's false, I've been able to lock and unlock multiple times.
!N.B.:: Be careful with info regarding being able to lock/unlock multiple times. There is possibly a difference in native CN vs WW models when it comes to the bootloader lock. Native WW (not CN converted to WW) can be locked/unlocked indefiniely - but the native CN versions may (for unknown reasons) be restricted to a one time only unlock.
Andrologic said:
!N.B.:: Be careful with info regarding being able to lock/unlock multiple times. There is possibly a difference in native CN vs WW models when it comes to the bootloader lock. Native WW (not CN converted to WW) can be locked/unlocked indefiniely - but the native CN versions may (for unknown reasons) be restricted to a one time only unlock.
Click to expand...
Click to collapse
Not true either! My one is CN converted to ww and I unlocked it twice already!
Attached, there's the official Bootloader Unlock Utility APK from Asus's HelpDesk Support Website, in case anyone needs to unlock their bootloader.
RAW firmware images (V18.1030.2106.112):
WW RAW image
CN RAW image
You can also download the kernel source of "V18.1050.2109.163" here (found the link here): https://dlcdnets.asus.com/pub/ASUS/ZenFone/ZS675KW/ASUS_I007_1-18.1050.2109.163-kernel-src.tar.gz
Apparently, it worked for some people, not for others. You need a lucky serial number in the server unlock database, it seems as though Asus engineering didn't know this model wasn't supposed to be unlockable hence the flip flop. Asus now claims it was a mistake that this tool was ever published and won't support unlocking. It failed to unlock for me so I RMAed the phone back to Asus.
Thanks Qualcomm for producing an overpriced phone with bad specs, and not even letting me access the overpriced hardware I bought with my own money.
The Pixel 6 pro is looking tempting with it's high end specs, dual SIM support, and it's Google so I won't have to worry about the bootloader.
CoinsClassic said:
Attached, there's the official Bootloader Unlock Utility APK from Asus's HelpDesk Support Website, in case anyone needs to unlock their bootloader.
RAW firmware images (V18.1030.2106.112):
WW RAW image
CN RAW image
You can also download the kernel source of "V18.1050.2109.163" here (found the link here): https://dlcdnets.asus.com/pub/ASUS/ZenFone/ZS675KW/ASUS_I007_1-18.1050.2109.163-kernel-src.tar.gz
Click to expand...
Click to collapse
Are there any instructions for manually flashing WW RAW firmware/Kernal via Fastboot or other means?
Thanks
rasseru16 said:
Are there any instructions for manually flashing WW RAW firmware/Kernal via Fastboot or other means?
Thanks
Click to expand...
Click to collapse
Extract the raw firmware zip file, boot smartphone into fastboot mode, execute flash_raw.cmd or .sh depending on your PC OS. That should be it.
Cool how it works i,m stupid loll
CoinsClassic -Do you have this UnBrick file..?
QFIL_FUSE_AND_LOCK_UFS_Factory_ZS675KW.zip
AzimBahar said:
CoinsClassic-Do you have this UnBrick file..?
QFIL_FUSE_AND_LOCK_UFS_Factory_ZS675KW.zip
Click to expand...
Click to collapse
QFIL_FUSE_AND_LOCK_UFS_Factory_ZS675KW.zip | Rom Developers
romdevelopers.com