You Need EDL Cable to Tweak Qualcomm driverto run EDL MODE do we should 1st turn usb debugging on? I have all the requiment tool to unbrick but my pc can't detect any new device connected even after i install the Qualcomm driver..
You Need EDL Cable to Tweak Qualcomm driverto run EDL MODE do we should 1st turn usb debugging on? I have all the requiment tool to unbrick but my pc can't detect any new device connected even after i install the Qualcomm driver..
Thanks Just now I downgrade from 11 to Android 10 .147 bcoz 11 has many bugs my Gmail ang Yahoo can't get notification appear in notification tray.List of RAW firmware (latest at the top)
— Android 11 RAWs —
18.0410.2106.138 : WW
18.0410.2105.133 : WW
— Android 10 RAWs —
17.0823.2104.147 : WW
17.0823.2102.143 : WW
17.0823.2012.131 : WW
17.0823.2012.122 : WW
17.0823.2009.99/100 : WW | CN
17.0823.2009.98 : WW | CN
17.0823.2008.78 : WW | CN
17.0823.2007.58 : WW | CN
17.0823.2007.47/48 : WW | CN
17.0823.2007.32 : WW | CN
How to resolve this issue and my self also facing same issueGetting this error:
C:\Users\himve\Downloads\Compressed\ROG_PHONE_3_ZS661KS_UNBRICK_EDL\.ImageE
Environment variable _COM not defined
FINDSTR: Cannot open .ImageE\qfile_emergency_dl.txt
""""""""""""""""""
"ERROR: FAILED: edl failed"
""""""""""""""""""
"Finished "
""""""""""""""""""
Thank you so much !!!Unbrick your ASUS ROG Phone 3 for free!!
Don't pay for this stuff anywhere, it's your device and you deserve the right to fix it yourself.
I noticed some people in the community charging upto 50$ for the firmware which should've been free from the start.
Code:#include <std_disclaimer.h> /* * I am not responsible for bricked devices, dead SD cards, * thermonuclear war, or you getting fired because the alarm app failed. * I'm not gonna tell you how to install drivers and other things and only[COLOR="RoyalBlue"][/COLOR] * proceed with this if you know what you're doing and please do some * research first. YOU are choosing to make these modifications, and if you * point the finger at me for messing up your device, I will laugh at you. */
NOTE - In case it's a Hard / Soft Brick
• For Hard Brick - Hard brick is when your device can only enter EDL mode and shows up as Qualcomm HS-USB QDLoader 9008 in device manager.
- Just follow from Step 1 to 3 to fix your device.
• For Soft Brick - Soft brick is when the system fails to boot but you can access fastboot mode.
- Just follow Step 3 to fix your device.
Prerequisites ►
• Windows PC
• Device fastboot drivers
• Qualcomm EDL drivers
• a bricked ROG 3 duh
Downloads ►
• EDL Unbrick tool - ROG_PHONE_3_ZS661KS_UNBRICK_EDL.7z
• RAW ROG 3 Firmware - Check the second post below
Instructions ►
Make sure you have device manager opened up to see if the device is connected.
1] Extract the EDL firmware
- Use the side port and connect device to PC
- Then run the file named 1ROG3_VFLASH_EDL.cmd
2] After you get an EDL SUCCESS message let the device boot within a minute or two into bootloader, use the device manager to
check if it's in EDL and if it's still there after a minute, press Power key + Volume down for about 12-13 seconds until
you don't see it in Device Manager, keep it plugged in and let it boot or try to power it on so it gets into the bootloader.
3] Once it's in bootloader flash any of the RAW firmware linked above depending on the device that you have, if its Tencent then flash CN, for global it's WW.
- Extract the RAW firmware and run the file zs661ks_raw_flashall.bat , have some patience and do not disconnect the device as this will take some time.
• That's all folks.
ROG 2/3 Telegram Groups & Channels ►
Global Discussion Group
Updates Channel
GCam Discussion
Will it work when the bootloader is locked?Unbrick your ASUS ROG Phone 3 for free!!
Don't pay for this stuff anywhere, it's your device and you deserve the right to fix it yourself.
I noticed some people in the community charging upto 50$ for the firmware which should've been free from the start.
Code:#include <std_disclaimer.h> /* * I am not responsible for bricked devices, dead SD cards, * thermonuclear war, or you getting fired because the alarm app failed. * I'm not gonna tell you how to install drivers and other things and only[COLOR="RoyalBlue"][/COLOR] * proceed with this if you know what you're doing and please do some * research first. YOU are choosing to make these modifications, and if you * point the finger at me for messing up your device, I will laugh at you. */
NOTE - In case it's a Hard / Soft Brick
• For Hard Brick - Hard brick is when your device can only enter EDL mode and shows up as Qualcomm HS-USB QDLoader 9008 in device manager.
- Just follow from Step 1 to 3 to fix your device.
• For Soft Brick - Soft brick is when the system fails to boot but you can access fastboot mode.
- Just follow Step 3 to fix your device.
Prerequisites ►
• Windows PC
• Device fastboot drivers
• Qualcomm EDL drivers
• a bricked ROG 3 duh
Downloads ►
• EDL Unbrick tool - ROG_PHONE_3_ZS661KS_UNBRICK_EDL.7z
• RAW ROG 3 Firmware - Check the second post below
Instructions ►
Make sure you have device manager opened up to see if the device is connected.
1] Extract the EDL firmware
- Use the side port and connect device to PC
- Then run the file named 1ROG3_VFLASH_EDL.cmd
2] After you get an EDL SUCCESS message let the device boot within a minute or two into bootloader, use the device manager to
check if it's in EDL and if it's still there after a minute, press Power key + Volume down for about 12-13 seconds until
you don't see it in Device Manager, keep it plugged in and let it boot or try to power it on so it gets into the bootloader.
3] Once it's in bootloader flash any of the RAW firmware linked above depending on the device that you have, if its Tencent then flash CN, for global it's WW.
- Extract the RAW firmware and run the file zs661ks_raw_flashall.bat , have some patience and do not disconnect the device as this will take some time.
• That's all folks.
ROG 2/3 Telegram Groups & Channels ►
Global Discussion Group
Updates Channel
GCam Discussion
I have the same problem when I flashed LOS 18.1 and wanted to go back to stock ROM.Have ran myself into a big problem. I had installed los 18.1 (after trying los 17.1 and omni.) on my Indian variant rog3. Later wanted to return to los 17.1.so as a first step flashed the stock raw firmware from this thread. Flash went without errors in the terminal. On. Rebooting was stuck on bootloop. Formating data from stock recovery didn't help. Trying to flash los 17.1 or omni also gave bootloop. But los 18.1 booted fine on flashing.
Later tried again to flash .99, .98 ,.58 raw firmware from here . all flashed without errors only to bootloop. Flashing full stock ROM zips from lineageos recovery also resulted in bootloop.
So now my phone only works with los 18.1 installed. Stock or other ROMs results in bootloop.
Please help.
How do I flash the 1.img persist?I was able to return to stock after flashing persist.img backup back. Seems some files in persist was changed on los installation. Followed this instruction from yidu for the restoration process https://forum.xda-developers.com/t/rom-unofficial-i003-obiwan-lineageos-18-1.4204665/post-84161965 . Aleasto merged my persist backup with yidus 1.img(which can be found 5 post above in the link given) and I flashed the resulting persist.img via adb. Flashing 1.img alone will stop bootloop on stock , but without your persist backup fingerprint may not work.
Try flashing latest RAW again (follow instructions correctly: ensure USB debugging enabled; RAW files extracted all in 1 folder; correct driver files installed; connect phone via side USB port; flash correct flash-all file)
I solved it but I don't know how... I made a thousand different attemptsCheck by "fastboot devices" command once USB attached with phone in fastboot mode, to confirm connection/ drivers installed correctly.
BroIf flashed correct RAW properly, should be back to stock Recovery (not TWRP) - likely something wrong with your RAW flashing process.......
Bro help me please to unbrick my deviceIf flashed correct RAW properly, should be back to stock Recovery (not TWRP) - likely something wrong with your RAW flashing process.......
#include <std_disclaimer.h>
/*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed.
* I'm not gonna tell you how to install drivers and other things and only[COLOR="RoyalBlue"][/COLOR]
* proceed with this if you know what you're doing and please do some
* research first. YOU are choosing to make these modifications, and if you
* point the finger at me for messing up your device, I will laugh at you.
*/