How to unlock your ROG2 phone via EDL mode!

vygneys_vyg

Senior Member
Dec 20, 2018
72
26
0
If you can't get your phone to connect while in fastboot mode, try connecting to the side USB port.
Yes I was using the side port. But not entering fastboot wasn't the main issue. That command itself doesnt work and I can get a glimpse of "Error" in CMD when I run it. Tried reinstalling drivers, restarting PC. Did it work for you?
 

dennis96411

Senior Member
Dec 9, 2011
1,099
496
113
¬_¬
Yes I was using the side port. But not entering fastboot wasn't the main issue. That command itself doesnt work and I can get a glimpse of "Error" in CMD when I run it. Tried reinstalling drivers, restarting PC. Did it work for you?
Yeah I think it might be a driver issue. Try running "fastboot devices" and see if your device shows up. Also try running the commands in the batch file manually so you can see what's happening.
 
  • Like
Reactions: vygneys_vyg

moudy

Member
Dec 31, 2007
27
9
0
So I did this and now my headphones jack isn't working. Has this happened to anyone else?

Update: The current workaround is to use the headphone jack of the included cooling fan.

Update 2: So it may have something to do with the bootloader that was flashed during the EDL unlocking process, which seems to be a generic SD855 bootloader. I came to this conclusion after I noticed that I was being limited to 70% battery charge. I flashed the WW 1910.35 OTA from ASUS' site and the battery now charges to 100%, but the headphone jack still remains broken. I will try to flash the WW 1910.44 update through fastboot when I get home, which I'm hoping will have whatever partition that was overwritten during the unlocking process.

Update 3: I figured it out. After using "fastboot flash boot TWRP.img" to boot into TWRP initially, I didn't flash the stock boot image again. This broke the headphone jack. So after booting into TWRP using that command, I had to flash the stock boot image first, then flash the TWRP and Magisk installers in that order. Hope this helps someone.
Hi I'm also having this problem. I'm currently on 1910.35
My model is a 512g WW original. I only rooted then ran into same exact problem as you have (AUX & battery charge capped) I did your fix but I'm still without aux sound and capped at 70% battery charge. I'd truly appreciate it
 
Last edited:

dennis96411

Senior Member
Dec 9, 2011
1,099
496
113
¬_¬
Hi I'm also having this problem. I'm currently on 1910.35
My model is a 512g WW original. I only rooted then ran into same exact problem as you have (AUX & battery charge capped) I did your fix but I'm still without aux sound and capped at 70% battery charge. I'd truly appreciate it
I ended up redoing those steps I mentioned and also wiping data. I found out the issue with my data partition after I backed it up with TWRP, wiped it, tested headphone jack and battery charging, then restoring the backup. For some reason whatever was on my data partition was causing the headphone jack to not work, so I had to wipe it and start fresh.

For the battery charging fix, the indicator for whether you performed the fix correctly is whether you see extra information in bootloader/fastboot mode. The EDL unlocking process flashed a generic SD855 bootloader (I'm assuming) with a bunch of debugging information on screen (like an unlock indicator). You should have the special ROG Phone 2 bootloader with only reboot choices on your screen.
 

moudy

Member
Dec 31, 2007
27
9
0
I ended up redoing those steps I mentioned and also wiping data. I found out the issue with my data partition after I backed it up with TWRP, wiped it, tested headphone jack and battery charging, then restoring the backup. For some reason whatever was on my data partition was causing the headphone jack to not work, so I had to wipe it and start fresh.

For the battery charging fix, the indicator for whether you performed the fix correctly is whether you see extra information in bootloader/fastboot mode. The EDL unlocking process flashed a generic SD855 bootloader (I'm assuming) with a bunch of debugging information on screen (like an unlock indicator). You should have the special ROG Phone 2 bootloader with only reboot choices on your screen.
Thanks for your help. So if I'm not mistaken I will be redoing the EDL process followed by a factory wipe? FYI I never restored anything after a wipe besides what is backed up by Google.

1. Factory wipe
2. EDL unlock
3. Then the flashing of stock boot.img, twrp, magisk
Followed by a factory wipe?

As for the bootloader it doesn't show me anything different from what I have been seeing. Besides serial number, model, rom version, secure boot. Etc
 

dennis96411

Senior Member
Dec 9, 2011
1,099
496
113
¬_¬
Thanks for your help. So if I'm not mistaken I will be redoing the EDL process followed by a factory wipe? FYI I never restored anything after a wipe besides what is backed up by Google.

1. Factory wipe
2. EDL unlock
3. Then the flashing of stock boot.img, twrp, magisk
Followed by a factory wipe?

As for the bootloader it doesn't show me anything different from what I have been seeing. Besides serial number, model, rom version, secure boot. Etc
That bootloader you just described is the generic one. The ASUS one shows pretty much nothing. Just the big banner that tells you what your reboot options are.

Also, you don't have to do anything in EDL now. You just need to flash a full OTA zip from ASUS' site using TWRP (or fastboot but I haven't tried that). This should restore your bootloader to the ASUS one (but you'll still be unlocked).

After you flash the OTA, stay inside TWRP. At this point, flash a stock boot image (such as this one), flash TWRP, flash Magisk, then wipe the data partition.

Good luck!
 

vygneys_vyg

Senior Member
Dec 20, 2018
72
26
0
Yeah I think it might be a driver issue. Try running "fastboot devices" and see if your device shows up. Also try running the commands in the batch file manually so you can see what's happening.
Fastboot devices shows my device, no probs. I tried reinstalling all drivers, even adb and general qualcomm drivers. I can see a brief of Error message when executing 1.update_image_EDL.bat . I tried executing line by line but I didnt know which ones to execute. Tried from the first line but it just stops and cannot execute more lines. Tried recording the screen with a camera and found this:

ERROR: Failed to open com port '\\.\COM3'

Edit: I updated the driver from device manager and this error was resolved, but another error appeared:
_____
| ___|
| |__ _ __ _ __ ___ _ __
| __| '__| '__/ _ \| '__|
| |__| | | | | (_) | |
\____/_| |_| \___/|_|


12:39:30: {ERROR: DetermineTag:6236 XML not formed correctly. Expected a < character at loc 0


_____
| ___|
| |__ _ __ _ __ ___ _ __
| __| '__| '__/ _ \| '__|
| |__| | | | | (_) | |
\____/_| |_| \___/|_|


12:39:30: {ERROR: GetNextPacket:7310 3. TAG not found or recognized


_____
| ___|
| |__ _ __ _ __ ___ _ __
| __| '__| '__/ _ \| '__|
| |__| | | | | (_) | |
\____/_| |_| \___/|_|


12:39:30: {ERROR: GetNextPacket:7320

There is a chance your target is in SAHARA mode!!
There is a chance your target is in SAHARA mode!!
There is a chance your target is in SAHARA mode!!

This can mean
1. You forgot to send DeviceProgrammer first (i.e. QSaharaServer.exe -s 13: prog_emmc_firehose_8994_lite.mbn)
2. OR, you did send DeviceProgrammer, but it has crashed and/or is not correct for this target

Regardless this program speaks FIREHOSE protocol and your target is speaking SAHARA protcol, so this will not work
 
Last edited:

dennis96411

Senior Member
Dec 9, 2011
1,099
496
113
¬_¬
I read somewhere that you must start the EDL unlocking process as soon as you run the fastboot command to boot it into EDL mode. It wouldn't run correctly for me at first, but then I rebooted into fastboot, ran the enter dload command, then immediately ran the unlocker (or if it fails because your device hasn't entered EDL mode just yet, keep spamming it).

I have no idea why that's the case but it worked for me.
 
  • Like
Reactions: vygneys_vyg

moudy

Member
Dec 31, 2007
27
9
0
That bootloader you just described is the generic one. The ASUS one shows pretty much nothing. Just the big banner that tells you what your reboot options are.

Also, you don't have to do anything in EDL now. You just need to flash a full OTA zip from ASUS' site using TWRP (or fastboot but I haven't tried that). This should restore your bootloader to the ASUS one (but you'll still be unlocked).

After you flash the OTA, stay inside TWRP. At this point, flash a stock boot image (such as this one), flash TWRP, flash Magisk, then wipe the data partition.

Good luck!
I'm really sorry to bother you again. I didn't have much free time to try but I just did. I tried to flash the fota ota file within twrp and the one from Asus website (2g) but both failed. I flashed that stock boot image then flashed twrp then magisk and I'm in to same position I was in. I don't know how to correctly flash ota from twrp. If you can help I'd appreciate it. Thanks
 

dennis96411

Senior Member
Dec 9, 2011
1,099
496
113
¬_¬
I'm really sorry to bother you again. I didn't have much free time to try but I just did. I tried to flash the fota ota file within twrp and the one from Asus website (2g) but both failed. I flashed that stock boot image then flashed twrp then magisk and I'm in to same position I was in. I don't know how to correctly flash ota from twrp. If you can help I'd appreciate it. Thanks
For what it's worth, I flashed "UL-ASUS_I001_1-ASUS-16.0631.1910.35-1.1.207-user.zip". Is your bootloader still showing unlock status? If so, then you're still on the generic one.

Try doing this. Flash the full firmware, wipe data, then directly boot into the OS. There might be some odd thing going on where the bootloader gets replaced after the first boot. If your headphone jack works after the reboot, then do the steps I mentioned.
 
Last edited:
  • Like
Reactions: moudy

vygneys_vyg

Senior Member
Dec 20, 2018
72
26
0
I read somewhere that you must start the EDL unlocking process as soon as you run the fastboot command to boot it into EDL mode. It wouldn't run correctly for me at first, but then I rebooted into fastboot, ran the enter dload command, then immediately ran the unlocker (or if it fails because your device hasn't entered EDL mode just yet, keep spamming it).

I have no idea why that's the case but it worked for me.
Dude you're a life saver! Infinite thanks. Followed everything you said and perfectly worked. Thanks again Dennis!
 

reg66

Senior Member
Jan 7, 2007
1,987
515
133
The second step doesn't seem to do anything can you help me? (The step after going in to EDL mode)
You need the Qualcom drivers installed, if you haven't already go here for them

Also, this post may be of some use to you, might wanna read the rest of the thread too for tips...
'I read somewhere that you must start the EDL unlocking process as soon as you run the fastboot command to boot it into EDL mode. It wouldn't run correctly for me at first, but then I rebooted into fastboot, ran the enter dload command, then immediately ran the unlocker (or if it fails because your device hasn't entered EDL mode just yet, keep spamming it).

I have no idea why that's the case but it worked for me.'
 

moudy

Member
Dec 31, 2007
27
9
0
Thanks to Dennis96411 I finally got my battery back to 100% and fully updated. :) Unfortunately my journey isn't over :( I then did the flash twrp.img from there I flashed twrp installer then magisk. I lost all sound and unable to watch videos. Also YouTube was uninstalled. Got YouTube back by removing vanced from magisk modules but still no video or sound :)

Ok ok ok. I figured it out. I redid the flashing while in twrp

1. flash rootboot.img (totally forgot to do this :laugh:)

2. Flash twrp installer

3. Flash magisk

Not my idea credit goes to Dennis96411

Update: I lost YouTube weird right. So I installed from playstore, then I installed venced YouTube from magisk and guess what.....YOUTUBE DISAPPEARED! No venced no YouTube lol. Fun stuff but I figured out what caused it. I had magisk and was rooted and all my fav add-on where there. When I updated my phone I reinstalled twrp and magisk but because I never removed my add-ons they created a bug lol. So to correct this fun problem you need to remove all modules then flash all that stuff and blamo ugly advertising YouTube restored. Hope my conquest as a noob helps anyone in similar situation. :laugh:

Next chapter: duel boot....to be continued :silly:
 
Last edited:

EfeKamil

Member
Dec 19, 2019
12
0
0
reg66 thanks for help but that doesn't seem to help. 1.update_image_EDL only runs for a second then closes down. And I dont know how to flash bat files with MiFlash can you help me?
 
Our Apps
Get our official app!
The best way to access XDA on your phone
Nav Gestures
Add swipe gestures to any Android
One Handed Mode
Eases uses one hand with your phone