Hello Everyone !!
A hard bricked OP3 has nothing but a black screen (nothing ever comes on the screen, not even a boot logo), it might vibrate when a power button is pressed and held for 20 seconds, has no Recovery partition, no adb mode, and no fastboot partition (It might be a flickering OnePlus logo). The device might be detected in Linux and you might be able to even send commands to it. In Windows, the bricked OP3 should be detected as QHUSB_BULK,Unknown Device,Qualcomm something. You might have a bricked OP3 as a result of flashing a kernel meant for a different device (or a ROM meant for another device that included a kernel), tinkering with the boot logo or bootloader, or your attempt of unlocking the bootloader resulted in corrupting the boot partition. Most of the times, it is needed because OEM Unlocking is disabled, and phone can't boot and no recovery.
The solution for OP3 hardbrick is similar to OPO - you just need a Qualcomm driver and a recovery package. A very very big thanks to some guys at XDA who got these files (don't know how) (I have modified the method 1 file though the method 2 file is exact file from OnePlus) and helped all of us to get out from one of the most weird state of the phone. Thanks guys. ( @CyberCROC and 1 more)
METHOD 1This method is the best method and will not wipe your data at all and will give you stock recovery+latest OxygenOS (or the ROM you were on) and bootloader will remain in the state it was earlier.It *might* not work if some other partitions were also corrupted.
Step 1 :- DOWNLOADS :-
1.) Drivers :- https://www.androidfilehost.com/?fid=24052804347799753
2.) Recovery Tool :- https://www.androidfilehost.com/?fid=24591000424942611
3.) [OPTIONAL :- Will be required only if you don't have a working system] Latest OxygenOS :- https://www.androidfilehost.com/?fid=24591020540821926
Step 2 :- Extract Drivers and Recovery Tool files on Desktop.
Step 3 :- If you are using Windows other than Windows XP,turn off Driver Signature Enforcement.To do so,follow this guide :- http://www.howtogeek.com/167723/how...8.1-so-that-you-can-install-unsigned-drivers/
Step 4 :- Press the power button for 40 seconds to turn off the phone.
Step 5 :- Press only volume up button for 10 seconds and while keeping it pressed,connect your phone to PC.Keep volume up pressed till your device shows in device manager as [Unknown Device,QHUSB_BULK (under Unknown Devices) or Qualcomm HS USB ...... (under COMs and Ports)].
Step 6 :- Right Click on your device in the device manager and select Update Device Software. Choose the .inf file manually from x86 or x64 folder as the case implies and select Qualcomm 9008 from the listed devices.If you are unable to see 9008,see the end of post for various other methods to show Qualcomm 9008.
Step 7 :- When the device shows as Qualcomm 9008 ,go to the extracted Recovery Package and run the MSM Download Tool as administrator.
Step 8 :- Click start at top left corner and wait for it to finish (green text will come).
Step 9 :- Disconnect phone from PC and boot into system.
........................NEXT STEPS ARE TO BE FOLLOWED ONLY IF YOUR OP3 DOESN'T BOOT INTO SYSTEM STILL BUT IS STUCK ON ONEPLUS LOGO..............................
Step 10 :- Boot your phone into recovery (Power+Volume Down).
Step 11 :- Click on Install Update.
Step 12 :- Install adb for windows system-wide if not already installed :- http://forum.xda-developers.com/showthread.php?p=48915118
Step 13 :- Navigate to the folder containing Latest OxygenOS Zip. Shift+Right Click anywhere in the folder and Open Command Window.
Step 14 :- In the command window,type :-
Code:
OnePlus3Oxygen_16_OTA_008_all_1606122244_e0cfc5ffc8bf411a.zip
and wait for it to finish.Then reboot into system.
METHOD 2This method is easy to use and flashes OxygenOS 3.1.2 on your phone. It wipes all your data (See end of post on how to not wipe data) and restores all partitions to stock. It will work in any condition unless it is a hardware damage.
Step 1 :- DOWNLOADS :-
1.) Drivers :- https://www.androidfilehost.com/?fid=24052804347799753
2.) Recovery Tool :- https://www.androidfilehost.com/?fid=24591000424942573
------------------Follow Step 2 to Step 9 from Method 1 --------------------
How to Prevent Data Wipe in Method 2
Step 1 :- Extract the Recovery Tool.
Step 2 :- Open all rawprogram...........xml through Notepad++
Step 3 :- Delete all userdata........ lines from the xml file.
DONE !!!
How to Make the device show as Qualcomm 9008
1.) Make sure driver signature enforcement is disabled.
2.) Try these drivers,one of them might work too :-
https://www.androidfilehost.com/?fid=24052804347799753
https://www.androidfilehost.com/?fid=24269982086990168
https://www.androidfilehost.com/?fid=24349802275800175
https://www.androidfilehost.com/?fid=24349802275800173
https://www.androidfilehost.com/?fid=24349802275800171
3.)
Download this :- http://www.mediafire.com/download/4aqwyi3g1d6wc67/Qualcomm 1.00.11.rar
Keep phone disconnected from PC.
Open the folder "qc" and install the Test Certificate in the following Stores: Trusted Root, Trusted Publisher, Third-Party Root and Personal
Run the Qualcomm setup wizard (also located in the qc folder)
When completed, restart your PC again with Driver Signature Disabled. (Optional but preferred)
The driver should now automatically install. If not, go to device manager and right click "Unknown Device" and click "Update Driver" Search up the QC folder and press ok. The driver should now install.
Thanks for this, it's very helpful (What is OP2 tho? )
Phone is now completely bricked and won't even go to Fastboot after following this guide. No lights, nada.
cepheid46e2 said:
Phone is now completely bricked and won't even go to Fastboot after following this guide. No lights, nada.
Click to expand...
Click to collapse
Definitely not possible. I have tested it myself on a friend's device. What was the status of the phone before ?
Sent from my OnePlus2 using XDA Labs
Phone booted into fastboot previously but could not boot to recovery. You can say what you like but my phone does not respond now. Going to continue working on it but all steps were followed.
cepheid46e2 said:
Phone booted into fastboot previously but could not boot to recovery. You can say what you like but my phone does not respond now. Going to continue working on it but all steps were followed.
Click to expand...
Click to collapse
Can you please try once again ? In no way can it damage the phone . The method 2 file is the complete one, it is almost uploaded. So, you can try that after. But, method 1 file should definitely work.
Sent from my OnePlus2 using XDA Labs
Naman Bhalla said:
Can you please try once again ? In no way can it damage the phone . The method 2 file is the complete one, it is almost uploaded. So, you can try that after. But, method 1 file should definitely work.
Sent from my OnePlus2 using XDA Labs
Click to expand...
Click to collapse
I have tried it 8 times now using both drivers from Method 1 & 2. The phone now has no response. I get to the MsmDownloadTool and click start and I get 2 errors in red popping up after a few minutes of downloading. The phone now has no response, no vibration or lights. Screen won't even come on.
A screenshot of the errors please.
Sent from my OnePlus2 using XDA Labs
Ok, OPO Tech Support just fixed my problem with a login. I'm not sure if it's a different driver or the device signatures but they got it working.
No need. We found the issue. It will be issue for those who also got system partition corrupt. For those guys with corrupt system partitons too, use Method 2. The file has almost been uploaded.
Sent from my OnePlus2 using XDA Labs
Naman Bhalla said:
A screenshot of the errors please.
Sent from my OnePlus2 using XDA Labs
Click to expand...
Click to collapse
I followed the steps exactly and was working great until I get the following error message....
View attachment 3794468
My device is now unusable (Screen won't come on, no lights, no sound and no vibration)
The only positive is that it appears/disappears from device manager as Qualcomm 9008 when I plug/unplug it from my PC
{
"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"
}
davidjones141 said:
I followed the steps exactly and was working great until I get the following error message....
My device is now unusable (Screen won't come on, no lights, no sound and no vibration)
The only positive is that it appears/disappears from device manager as Qualcomm 9008 when I plug/unplug it from my PC
Click to expand...
Click to collapse
Thanks for the screenshots. I told the reason already. Another file is being uploaded.
Sent from my OnePlus2 using XDA Labs
Naman Bhalla said:
Thanks for the screenshots. I told the reason already. Another file is being uploaded.
Thanks! I'll give it a go once it has finished uploading
Click to expand...
Click to collapse
Full tool is up ! Uploading the mini tool again. Sorry for the issue. Fixed.
_MartyMan_ said:
Thanks for this, it's very helpful (What is OP2 tho? )
Click to expand...
Click to collapse
Hehe. Just realised that. Fixed.
davidjones141 said:
I followed the steps exactly and was working great until I get the following error message....
View attachment 3794468
My device is now unusable (Screen won't come on, no lights, no sound and no vibration)
The only positive is that it appears/disappears from device manager as Qualcomm 9008 when I plug/unplug it from my PC
View attachment 3794469
Click to expand...
Click to collapse
A fixed mini tool is up. Please try that. There was a missing file that caused the issue as it wasn't removed from rawprogram.
Thanks.
Naman Bhalla said:
Hehe. Just realised that. Fixed.
A fixed mini tool is up. Please try that. There was a missing file that caused the issue as it wasn't removed from rawprogram.
Thanks.
Click to expand...
Click to collapse
I just re-followed Method 2 and it worked flawlessly with the new upload
Thanks!
davidjones141 said:
I just re-followed Method 2 and it worked flawlessly with the new upload
Thanks!
Click to expand...
Click to collapse
Good to know .
Would be great if someone can confirm new method 1 to also work. The missing loop has been added. It should work, but, who knows .
EDIT :- Confirmed that it works by another guy. So, we are all set now.
Sent from my OnePlus2 using XDA Labs
Naman Bhalla said:
Full tool is up ! Uploading the mini tool again. Sorry for the issue. Fixed.
Click to expand...
Click to collapse
Hey Naman , you are a human 2 or not a issue is normal,you make a great job for the one+.
I want to say a great thanks to you!
You are the men.
Thanx,Danke,grazie...
Gesendet von meinem ONEPLUS A3003 mit Tapatalk
Jakkomo77 said:
Hey Naman , you are a human 2 or not a issue is normal,you make a great job for the one+.
I want to say a great thanks to you!
You are the men.
Thanx,Danke,grazie...
Gesendet von meinem ONEPLUS A3003 mit Tapatalk
Click to expand...
Click to collapse
Thanks a lot.
Sent from my OnePlus2 using XDA Labs
my device is not being recognized in the MSM tool, I am running as admin.
in device manager under "PORTS" my device says "RELINK HS-USB QDLoader 9008 (COM5)....should it say this or something else? I understand the COM port could be different, though.
driver signature is turned off as well..
update: hold on, it may be working now....in the MSM tool under "Communication Status" it is downloading various system files now
---------- Post added at 11:01 AM ---------- Previous post was at 10:42 AM ----------
coolness, all is well now. Device is now booted up and I am going through the setup, right now. Thanks a lot!!!!
Related
{
"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"
}
This is my first walkthrough so I will do my best to do this properly. The Honor Note 8 does not have a forum yet, and this is the third thread for this phone. Hopefully we can get a forum up soon.
PLEASE NOTE THAT UNLOCKING BOOTLOADER WILL WIPE YOUR DEVICE AND POSSIBLY VOID YOUR WARRENTY!!!
I'M NOT RESPONSIBLE IF SOMETHING DOESN'T WORK.
Unlock Bootloader
Follow the steps here to begin the Bootloader Unlock process:
https://www.dc-unlocker.com/how-to-read-huawei-bootloader-unlock-code
1. a) Install the application
1. b) Follow the steps on the above page to put phone into "Manufacture Mode"
1. c) Under "Select Manufacturer", choose "Huawei Phones" and under "Select Model", choose the model of your phone
1. d) Click on "Buy Credits". You should end up being emailed a username and password, return to the Unlocker Client, and input those two
1. e) The Unlocker Client should return the bootloader unlock code
2. a) Enable Developer Options by clicking on the build number multiple times
2. b) Turn on USB Debugging
3. Prepare TWRP custom recovery before preceeding further. You can get it from here: https://drive.google.com/open?id=0B4xzs81XsmURVTRnUDJHdl9CQlE
3. Prepare and install ADB and Fastboot tools. I used this one http://forum.xda-developers.com/showthread.php?t=2588979
4. Go into the folder with your recovery and open a CMD (if you used system-wide ADB as linked above, otherwise place recovery in your ADB folder)
5. Put the phone into Bootloader mode with:
Code:
adb reboot bootloader
. This will take you to the bootloader mode (white screen with some small text)
6. Now type:
Code:
fastboot oem unlock <UNLOCK_CODE>
where
Code:
<UNLOCK_CODE>
is the bootloader code that the Unlocker Client gave you
Loading TWRP Custom Recovery
7. Your phone may reboot when the process is complete. We want to go back into Bootloader mode, so follow Step 5 again to go back to bootloader mode
8. Now type:
Code:
fastboot flash recovery <NAME_OF_YOUR_RECOVERY.img>
The recovery will flash over to your device. We want to reboot into the recovery mode.
9. Now type:
Code:
fastboot reboot
but just before you hit ENTER on that command, start holding VOLup and VOLdown at the same time (as explained below)
This phone has two recoveries on it, which is great since it makes it really hard to brick. In order to access custom recovery, you need to hold down both VOL buttons during boot process (from the very beginning) in order to access the custom recovery.
Once you have entered TWRP, you will most likely notice that it is in CHINESE. If you don't read chinese, follow the steps below to change to English UI in TWRP:
Change to English UI in TWRP
10. TWRP has two columns of 4 buttons, 8 buttons total. I have labeled the buttons as per their position as below:
1 2
3 4
5 6
7 8
11. Click button 6 to go to the Settings, then click on the "Globe" icon, then switch to english and click the button in the bottom right corner.
BACKUP!!
12. I highly recommend you now do a TWRP backup and place the backup on an External SD card (not the internal memory). This will save your ass if you mess anything up or it doesn't work for you. Do a full backup (select ALL of the options).
Installing Xposed
Grab the Installer APK here: http://forum.xda-developers.com/showthread.php?t=3034811
and the Framework zip here: http://dl-xda.xposed.info/framework/sdk23/arm64/
Put both files onto your SD card.
13. Boot into your rom, install the APK file (you may need to enable "unknown sources")
14. Then boot back into TWRP. Do this by restarting the phone, and just as the screen goes black, hold down both VOL buttons until you see text on the screen.
15. Install the framework, wipe cache/dalvik and reboot the phone
ROMs
There are several roms, all of which can be found here: http://forum.xda-developers.com/general/general/huawei-honor-note-8-roms-t3487575
I will try to update this post with instructions on how to install them once I have the process down properly.
Thanks to:
@benmeroff for his posting of all of those ROMs and his work on the original thread.
The link to the xposed installer is dead
jdantow said:
Installing Xposed
Grab the Installer APK here: http://forum.xda-developers.com/show....php?t=3034811
Click to expand...
Click to collapse
Just another small reminder this Xposed apk link is broken. Could I just download any Xposed apk or was this link for a specific version for the Note 8?
Thanks
remix435 said:
The link to the xposed installer is dead
Click to expand...
Click to collapse
Thank you! I updated the link, can you confirm it is working now from your end? Thanks so much!
The thread ID is 3034811 so if you take
Code:
http://forum.xda-developers.com/showthread.php
and add
Code:
?t=3034811
it should work for you
jlomein said:
Just another small reminder this Xposed apk link is broken. Could I just download any Xposed apk or was this link for a specific version for the Note 8?
Thanks
Click to expand...
Click to collapse
Thank you! I updated the link, can you confirm it is working now from your end? Thanks so much!
The thread ID is 3034811 so if you take
Code:
http://forum.xda-developers.com/showthread.php
and add
Code:
?t=3034811
it should work for you
Hopefully either a camera port or a camera hack can come about from developing. Anybody know about possible camera hack thats the only thing (IMO) this phone needs
jdantow said:
Thank you! I updated the link, can you confirm it is working now from your end? Thanks so much!
Click to expand...
Click to collapse
Thanks, downloaded Xposed 3.1.1 apk from that link now.
Cheers
hi
after i flashed trwp and did back up i stuck in bootloop
tried to flash kingvip rom - no luck. tried to recover from back up but stil in boot loop.
can anyone help me, please
Anyone happen to have the img for the modem? I believe mine may be corrupted.
hi i will my boodloader unlock my Note 8. The phone will not unlock. I have the ulock key. I hvae the Build Nummber B027.
Hi guys, a question...
The is no way I can install this drivers that are required... if I click the setup icons nothing happens at all, and if i try manually all i get is 4x "Android device" in the device manager, and locating drivers in the designated folders does not help, it still says "windows did not find the driver for your device...."
Anyone maybe had a similar problem/solution?
Thanksss
Bubreg said:
Hi guys, a question...
The is no way I can install this drivers that are required... if I click the setup icons nothing happens at all, and if i try manually all i get is 4x "Android device" in the device manager, and locating drivers in the designated folders does not help, it still says "windows did not find the driver for your device...."
Anyone maybe had a similar problem/solution?
Thanksss
Click to expand...
Click to collapse
Just google huawei drivers.... I had the same question but when i installed HiSuite the drivers was inside - it work fine, but it will always pop up when you connecting phone...
falc1 said:
Just google huawei drivers.... I had the same question but when i installed HiSuite the drivers was inside - it work fine, but it will always pop up when you connecting phone...
Click to expand...
Click to collapse
Thank you man, worked like a charm! I got the bootloader code... but since it's gonna wipe everything if I unlock it, I'm gonna wait until the next weekend most probably, too busy these days.
Hi guys,
i was able to unlock the bootloader but i can't flash the recovery and every time i try it display "remote: command not allowed".
Good morning.
I hope for Christmas to be a holder of Honor Note 8.
To unlock the bootloader you need to pay 4 euro through dc-unlocker.com program?
Thank you
m3sari0 said:
Hi guys,
i was able to unlock the bootloader but i can't flash the recovery and every time i try it display "remote: command not allowed".
Click to expand...
Click to collapse
Same thing happend to me
I relocked the bootloader then unlock it again and it works
player1990 said:
Same thing happend to me
I relocked the bootloader then unlock it again and it works
Click to expand...
Click to collapse
thanks man it worked.
TWRP - changing language
OP - thank you for this thread. Was able to follow the steps and get most of the things accomplished.
One thing that i am having trouble with is - changing the TWRP language from Chinese to English. In button #6, the globe icon is not even clickable. All others are, but that one is not. Any ideas? Thanks!
EDIT: I got it to work. It seems some icons in the corners of the screen can be a little hard or slow to respond... if you (a future reader) are having the same issue - try kind of mini swiping in circles over that icon and it will eventually respond.
Hi,
I requested the unlock code on the Huawei site but I get this error:
The Huawei ID used to apply for the unlock code has not been used on the device for more than 14 days.
How can I do?
Some might apply to me
MarkAndroid said:
Hi,
I requested the unlock code on the Huawei site but I get this error:
The Huawei ID used to apply for the unlock code has not been used on the device for more than 14 days.
How can I do?
Some might apply to me
Click to expand...
Click to collapse
You have to wait 14 days or pay for the credits on DC-unlocker app
[GUIDE] Unbrick Tool for OnePlus 5 with OOS 9.0.9 & OOS 9.0.11 (Untouched full stock)
Hello Everyone !!
=>A hard bricked OP5 has nothing but a black screen (nothing ever comes on the screen, not even a boot logo), it might vibrate when a power button is pressed and held for 20 seconds, has no Recovery partition, no adb mode, and no fastboot partition (It might be a flickering OnePlus logo). The device might be detected in Linux and you might be able to even send commands to it. In Windows, the bricked OP5 should be detected as QHUSB_BULK,Unknown Device,Qualcomm something. You might have a bricked OP5 as a result of flashing a kernel meant for a different device (or a ROM meant for another device that included a kernel), tinkering with the boot logo or bootloader, or your attempt of unlocking the bootloader resulted in corrupting the boot partition. Most of the times, it is needed because OEM Unlocking is disabled, and phone can't boot and no recovery.
=>The solution for OP5 hardbrick is similar to OP3,OP3T- you just need a Qualcomm driver and a recovery package.it'll help to get out from one of the most weird state of the phone.(file is exact file from OnePlus)
METHOD
This method is easy to use and flashes OxygenOS 5.1.7 and OxygenOS 9.0.9 on your phone. It wipes all your data and restores all partitions to stock. It will work in any condition unless it is a hardware damage.
Step 1 :- DOWNLOADS :-
OOS 9.0.9: https://mega.nz/file/O4dGFI4b#mbqq8VqUiPwoN85ajTV-H2pDNccD58-ccejQnTQHIBE
OOS 9.0.11:https://mega.nz/file/ekUURaII#FPoezmYL1hPJUkb2Hf90ZqW07iEaCza6etnTPSKJOos
Step 2 :- Extract Drivers and Recovery Tool files on Desktop.
Step 3 :- If you are using Windows other than Windows XP,turn off Driver Signature Enforcement.To do so,follow this guide :- http://www.howtogeek.com/167723/how-...igned-drivers/
Step 4 :- Press the power button for 40 seconds to turn off the phone.
Step 5 :- Press only volume up button for 10 seconds and while keeping it pressed,connect your phone to PC.Keep volume up pressed till your device shows in device manager as [Unknown Device,QHUSB_BULK (under Unknown Devices) or Qualcomm HS USB ...... (under COMs and Ports)].
Step 6 :- Right Click on your device in the device manager and select Update Device Software. Choose the .inf file manually from x86 or x64 folder as the case implies and select Qualcomm 9008 from the listed devices.If you are unable to see 9008,see the end of post for various other methods to show Qualcomm 9008.
Step 7 :- When the device shows as Qualcomm 9008 ,go to the extracted Recovery Package and run the MSM Download Tool as administrator.
Step 8 :- Click start at top left corner and wait for it to finish (green text will come).
Step 9 :- Disconnect phone from PC and boot into system.
How to Make the device show as Qualcomm 9008
1.) Make sure driver signature enforcement is disabled.
2.) Try these drivers,one of them might work too :-
https://www.androidfilehost.com/?fid=24052804347799753
https://www.androidfilehost.com/?fid=24269982086990168
https://www.androidfilehost.com/?fid=24349802275800175
https://www.androidfilehost.com/?fid=24349802275800173
https://www.androidfilehost.com/?fid=24349802275800171
3.)Download this :- http://www.mediafire.com/file/4aqwyi3g1d6wc67/Qualcomm+1.00.11.rar
Keep phone disconnected from PC.
Open the folder "qc" and install the Test Certificate in the following Stores: Trusted Root, Trusted Publisher, Third-Party Root and Personal
Run the Qualcomm setup wizard (also located in the qc folder)
When completed, restart your PC again with Driver Signature Disabled. (Optional but preferred)
The driver should now automatically install. If not, go to device manager and right click "Unknown Device" and click "Update Driver" Search up the QC folder and press ok. The driver should now install.
P.S.: I found the fix for bootloader menu which was changing after flashing through this tool. Just flash the zip in the recovery from the link below after flashing the rom through this tool, and you are good to go.
Please boot your device, set it up then go back to recovery and flash this file.
https://mega.nz/file/n10kkKCQ#LmCm_TDDyZ9cdZPf2pk0mSSV1bgvZflENQG0ubl15SY
NOTE: When the tool gives the "Sahara error", DON'T DISCONNECT THE PHONE from your PC, and press vol up and power button. It maybe seem stupid as a fix but generally it works.
IMP NOTE: There is a quick update, recently I also got stuck at param processing while flashing my device. So uploading the tool which works well. Here is the link. https://mega.nz/file/C1Nw3Cyb#znHfATPuRN4rAy1ZnDO4kMcftEkQ1P6enGxRGSiBh2E
IMP NOTE: There is a quick update, the tool is updated with latest TREBLE OS.
CREDITS @vasu97 - for helping and motivating me to create this thread
@Mar-cel - for bootloader fix zip
Click thanks IF i helped you
Where did you get this file, after I restored it, the bootblock unlock menu changed, is that normal?
Yes it is normal, mine also changed. May be they changed something in latest tool
Hi! First of all, thx for this post. I am getting Error 258 when i execute the tool. I am getting " Qualcomm HS-USB QDLoader 9008" in device manager, is that right? When i'm executing the program, he begins to download cache.img, and then stop and shows me this error :T Gonna send some pics to better ilustrate it.
{
"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"
}
Can you help me? Thx again.
EDIT: I forgot to mention that my cellphone turns on the led, in color green, when the tool starts to running.
cidsantiago said:
Hi! First of all, thx for this post. I am getting Error 258 when i execute the tool. I am getting " Qualcomm HS-USB QDLoader 9008" in device manager, is that right? When i'm executing the program, he begins to download cache.img, and then stop and shows me this error :T Gonna send some pics to better ilustrate it.
Can you help me? Thx again.
EDIT: I forgot to mention that my cellphone turns on the led, in color green, when the tool starts to running.
Click to expand...
Click to collapse
hv u tried running this tool as administrator abd ur fone shud not turn on any of the led while flashing.. if u r on twrp try format data .. and then try flashing it thru tool.. or may be its bad download at ur side. redownload again.. and try
cidsantiago said:
Hi! First of all, thx for this post. I am getting Error 258 when i execute the tool. I am getting " Qualcomm HS-USB QDLoader 9008" in device manager, is that right? When i'm executing the program, he begins to download cache.img, and then stop and shows me this error :T Gonna send some pics to better ilustrate it.
View attachment 4445915
View attachment 4445916
Can you help me? Thx again.
EDIT: I forgot to mention that my cellphone turns on the led, in color green, when the tool starts to running.
Click to expand...
Click to collapse
Don't worry about green led light while flashing with tool its normal behavior, and about error...maybe because of bad download for sure,try attaching your phone again or check the drivers again...and look at the firs comment - seems like tool is working fine.
djnim said:
hv u tried running this tool as administrator abd ur fone shud not turn on any of the led while flashing.. if u r on twrp try format data .. and then try flashing it thru tool.. or may be its bad download at ur side. redownload again.. and try
Click to expand...
Click to collapse
Yes, i ran it as administrator. M phone was totally bricked, i only got signal in him when i connected at the PC. But i always had this error :T I downloaded it at least 5 times, and got always the same results.
vasu97 said:
Don't worry about green led light while flashing with tool its normal behavior, and about error...maybe because of bad download for sure,try attaching your phone again or check the drivers again...and look at the firs comment - seems like tool is working fine.
Click to expand...
Click to collapse
I did it all, believe me. Reinstalled the drivers multiples times, differents PCS, differents USB ports... I think it was a hardware problem.
I already sent my phone to RMA, so i think it was solved, one way or another But thanks for your replies
cidsantiago said:
Yes, i ran it as administrator. M phone was totally bricked, i only got signal in him when i connected at the PC. But i always had this error :T I downloaded it at least 5 times, and got always the same results.
I did it all, believe me. Reinstalled the drivers multiples times, differents PCS, differents USB ports... I think it was a hardware problem.
I already sent my phone to RMA, so i think it was solved, one way or another But thanks for your replies
Click to expand...
Click to collapse
ohh.. i got tensed as it is my very first thread .
best method to return sotck complete
Thanks for the clear instructions, you have just saved my phone
Dude, thanks for the guide. But kindly check your links in the post. Some are dead ( especially : the mediafire link you gave at last )
Hi
Thank you so much !
AnDrOiDnEoV said:
Dude, thanks for the guide. But kindly check your links in the post. Some are dead ( especially : the mediafire link you gave at last )
Click to expand...
Click to collapse
That's correct. The right link is this: http://www.mediafire.com/file/4aqwyi3g1d6wc67/Qualcomm+1.00.11.rar
Hi, thanks for making this guide with such clear instructions!
I've done every step according to the guide, but I keep facing this issue:
Just to clarify I did run it as administrator.
Are you going to update (5.1.2)?
esedix02 said:
Are you going to update (5.1.2)?
Click to expand...
Click to collapse
If i Get it then yes for sure
Op updated with the bootloader fix, which helps to revert to old bootloader menu.
Op updated with new tool which includes OOS 5.1.2.
Mate she worked a charm! I wasn't bricked but wanted to restore to full stock after issues with open beta rims, firmware and AOSP roms. Was the simplest way to achieve a fresh start
it downloads the ROM while flashing? Or ROM is included in given link by OP?
Sorry for my poor English, I'm a Taiwanese
Let's talk about something that bricking and unbricking this device...
I've got a Zenfone 5Z (ZS620KL) at version 80.30.96.111 and want to unlock the bootloader but get a error while using official unlock app.
And I found some article saying that it will only work at older version e.g. 80.11.37.49.
Thus, I tried to downgrade to version 80.10.8.54 and follow the guide from here.
https://forum.xda-developers.com/zenfone-5z/how-to/guide-zenfone-5z-how-to-root-downgrade-t3815877
Guess what? I totally bricked this device and get black screen, with vol down + power button get vibrate only.
So, I went to ASUS official repair store and they want charge me about USD $300 to replace the motherboard, but I said no and told them I will try to revive this device by myself.
I made a special USB TYPE-C cable (as xiaomi edl usb cable) to let device boot into Qualcomm 9008 mode and follow this guide to revive this device.
https://www.firmware27.com/2018/05/firmware-asus-zs620kl.html (Draco_ZS620KL_QMSCT_download.pdf (Tutorial Flashing))
Here is the detail that unbricking this device
1. Download "WW_ZS620KL_80.30.96.111_MR2_20180921002943_release-user.raw.zip"
2. Download "CSC-ZS620KL-80.02.237.70-FAC-eng-20180810191100-factory.zip"
3. Unzip "WW_ZS620KL_80.30.96.111_MR2_20180921002943_release-user.raw.zip"
4. Install python 2.7
5. Goto directory /WW_ZS620KL_80.30.96.111_MR2_20180921002943_release-user.raw/factory_for_QMSCT
6. Execute "unparse_img.bat"
7. Extract "fs_image.tar.gz.mbn.img" from "CSC-ZS620KL-80.02.237.70-FAC-eng-20180810191100-factory.zip" to "WW_ZS620KL_80.30.96.111_MR2_20180921002943_release-user.raw" folder
8. Run QMSCT and follow the steps in "Draco_ZS620KL_QMSCT_download.pdf"
9. If success, hold vold down + power button to reboot, it will show the splash screen
10. Reboot to bootloader and use AFT v1.0.0.71 to flash "WW_ZS620KL_80.30.96.111_MR2_20180921002943_release-user.raw.zip" again
11. Reboot and get a fully functional device back
Conclusion: DO NOT DOWNGRADE TO 80.10.8.54 TO PREVENT THIS
The gallery
https://imgur.com/a/7oyswfC
{
"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"
}
Does your guide relocks the bootloader back?
Sent from my ASUS_Z01RD using Tapatalk
I wants to relock bootloader
sabpprook said:
Sorry for my poor English, I'm a Taiwanese
Let's talk about something that bricking and unbricking this device...
I've got a Zenfone 5Z (ZS620KL) at version 80.30.96.111 and want to unlock the bootloader but get a error while using official unlock app.
And I found some article saying that it will only work at older version e.g. 80.11.37.49.
Thus, I tried to downgrade to version 80.10.8.54 and follow the guide from here.
https://forum.xda-developers.com/zenfone-5z/how-to/guide-zenfone-5z-how-to-root-downgrade-t3815877
Guess what? I totally bricked this device and get black screen, with vol down + power button get vibrate only.
So, I went to ASUS official repair store and they want charge me about USD $300 to replace the motherboard, but I said no and told them I will try to revive this device by myself.
I made a special USB TYPE-C cable (as xiaomi edl usb cable) to let device boot into Qualcomm 9008 mode and follow this guide to revive this device.
https://www.firmware27.com/2018/05/firmware-asus-zs620kl.html (Draco_ZS620KL_QMSCT_download.pdf (Tutorial Flashing))
Here is the detail that unbricking this device
1. Download "WW_ZS620KL_80.30.96.111_MR2_20180921002943_release-user.raw.zip"
2. Download "CSC-ZS620KL-80.02.237.70-FAC-eng-20180810191100-factory.zip"
3. Unzip "WW_ZS620KL_80.30.96.111_MR2_20180921002943_release-user.raw.zip"
4. Install python 2.7
5. Goto directory /WW_ZS620KL_80.30.96.111_MR2_20180921002943_release-user.raw/factory_for_QMSCT
6. Execute "unparse_img.bat"
7. Extract "fs_image.tar.gz.mbn.img" from "CSC-ZS620KL-80.02.237.70-FAC-eng-20180810191100-factory.zip" to "WW_ZS620KL_80.30.96.111_MR2_20180921002943_release-user.raw" folder
8. Run QMSCT and follow the steps in "Draco_ZS620KL_QMSCT_download.pdf"
9. If success, hold vold down + power button to reboot, it will show the splash screen
10. Reboot to bootloader and use AFT v1.0.0.71 to flash "WW_ZS620KL_80.30.96.111_MR2_20180921002943_release-user.raw.zip" again
11. Reboot and get a fully functional device back
Conclusion: DO NOT DOWNGRADE TO 80.10.8.54 TO PREVENT THIS
The gallery
https://imgur.com/a/7oyswfC
Click to expand...
Click to collapse
Please sir i help me i wants to relock i will pay some for that
Does it relock bootloader
Relock bootloader
Where i can find your flashtool version? Mine don't see ZS620KL
Thanks a lot for this informative guide. You have been an angel to all the 5z users.
God bless you.!!
Finally, you wants to flash it
sabpprook said:
Sorry for my poor English, I'm a Taiwanese
Let's talk about something that bricking and unbricking this device...
I've got a Zenfone 5Z (ZS620KL) at version 80.30.96.111 and want to unlock the bootloader but get a error while using official unlock app.
And I found some article saying that it will only work at older version e.g. 80.11.37.49.
Thus, I tried to downgrade to version 80.10.8.54 and follow the guide from here.
https://forum.xda-developers.com/zenfone-5z/how-to/guide-zenfone-5z-how-to-root-downgrade-t3815877
Guess what? I totally bricked this device and get black screen, with vol down + power button get vibrate only.
So, I went to ASUS official repair store and they want charge me about USD $300 to replace the motherboard, but I said no and told them I will try to revive this device by myself.
I made a special USB TYPE-C cable (as xiaomi edl usb cable) to let device boot into Qualcomm 9008 mode and follow this guide to revive this device.
https://www.firmware27.com/2018/05/firmware-asus-zs620kl.html (Draco_ZS620KL_QMSCT_download.pdf (Tutorial Flashing))
Here is the detail that unbricking this device
1. Download "WW_ZS620KL_80.30.96.111_MR2_20180921002943_release-user.raw.zip"
2. Download "CSC-ZS620KL-80.02.237.70-FAC-eng-20180810191100-factory.zip"
3. Unzip "WW_ZS620KL_80.30.96.111_MR2_20180921002943_release-user.raw.zip"
4. Install python 2.7
5. Goto directory /WW_ZS620KL_80.30.96.111_MR2_20180921002943_release-user.raw/factory_for_QMSCT
6. Execute "unparse_img.bat"
7. Extract "fs_image.tar.gz.mbn.img" from "CSC-ZS620KL-80.02.237.70-FAC-eng-20180810191100-factory.zip" to "WW_ZS620KL_80.30.96.111_MR2_20180921002943_release-user.raw" folder
8. Run QMSCT and follow the steps in "Draco_ZS620KL_QMSCT_download.pdf"
9. If success, hold vold down + power button to reboot, it will show the splash screen
10. Reboot to bootloader and use AFT v1.0.0.71 to flash "WW_ZS620KL_80.30.96.111_MR2_20180921002943_release-user.raw.zip" again
11. Reboot and get a fully functional device back
Conclusion: DO NOT DOWNGRADE TO 80.10.8.54 TO PREVENT THIS
The gallery
https://imgur.com/a/7oyswfC
Click to expand...
Click to collapse
Haaaa,thess steps are ridiculously because at the end you flash your device with files which yoy build yourself, why not you chose raw image instead that , that file be around 2gb, it will be easy for flashing,
Cheeda212 said:
Haaaa,thess steps are ridiculously because at the end you flash your device with files which yoy build yourself, why not you chose raw image instead that , that file be around 2gb, it will be easy for flashing,
Click to expand...
Click to collapse
It is able to flash raw firmware while device under qualcomm 9008?
MystikMan97130 said:
Where i can find your flashtool version? Mine don't see ZS620KL
Click to expand...
Click to collapse
Here you are
https://drive.google.com/open?id=1kBuHSmAahsslDe8m2rKRkC-Qj_23yFTh
sabpprook said:
Here you are
https://drive.google.com/open?id=1kBuHSmAahsslDe8m2rKRkC-Qj_23yFTh
Click to expand...
Click to collapse
Thanks Man
sabpprook
Can U put all files Your used in one place ?
Saharaa fail error
Cheeda212 said:
Please sir i help me i wants to relock i will pay some for that
Click to expand...
Click to collapse
I got sahara fail error when i use qmpct
---------- Post added at 05:09 AM ---------- Previous post was at 05:08 AM ----------
sabpprook said:
Sorry for my poor English, I'm a Taiwanese
Let's talk about something that bricking and unbricking this device...
I've got a Zenfone 5Z (ZS620KL) at version 80.30.96.111 and want to unlock the bootloader but get a error while using official unlock app.
And I found some article saying that it will only work at older version e.g. 80.11.37.49.
Thus, I tried to downgrade to version 80.10.8.54 and follow the guide from here.
https://forum.xda-developers.com/zenfone-5z/how-to/guide-zenfone-5z-how-to-root-downgrade-t3815877
Guess what? I totally bricked this device and get black screen, with vol down + power button get vibrate only.
So, I went to ASUS official repair store and they want charge me about USD $300 to replace the motherboard, but I said no and told them I will try to revive this device by myself.
I made a special USB TYPE-C cable (as xiaomi edl usb cable) to let device boot into Qualcomm 9008 mode and follow this guide to revive this device.
https://www.firmware27.com/2018/05/firmware-asus-zs620kl.html (Draco_ZS620KL_QMSCT_download.pdf (Tutorial Flashing))
Here is the detail that unbricking this device
1. Download "WW_ZS620KL_80.30.96.111_MR2_20180921002943_release-user.raw.zip"
2. Download "CSC-ZS620KL-80.02.237.70-FAC-eng-20180810191100-factory.zip"
3. Unzip "WW_ZS620KL_80.30.96.111_MR2_20180921002943_release-user.raw.zip"
4. Install python 2.7
5. Goto directory /WW_ZS620KL_80.30.96.111_MR2_20180921002943_release-user.raw/factory_for_QMSCT
6. Execute "unparse_img.bat"
7. Extract "fs_image.tar.gz.mbn.img" from "CSC-ZS620KL-80.02.237.70-FAC-eng-20180810191100-factory.zip" to "WW_ZS620KL_80.30.96.111_MR2_20180921002943_release-user.raw" folder
8. Run QMSCT and follow the steps in "Draco_ZS620KL_QMSCT_download.pdf"
9. If success, hold vold down + power button to reboot, it will show the splash screen
10. Reboot to bootloader and use AFT v1.0.0.71 to flash "WW_ZS620KL_80.30.96.111_MR2_20180921002943_release-user.raw.zip" again
11. Reboot and get a fully functional device back
Conclusion: DO NOT DOWNGRADE TO 80.10.8.54 TO PREVENT THIS
The gallery
https://imgur.com/a/7oyswfC
Click to expand...
Click to collapse
Sahara fail error
"Draco_ZS620KL_QMSCT_download.pdf" can not download.
QMSCT can not download.
help me.:crying:
Just flash fastboot rom
Sorry for my poor English. I am Japanese.
fastboot does not work.
It was broken while introducing twrp.
Power does not come on.
I can connect to a PC.
It is recognized as "qualcomm hs-usb qdloader 9008".
special USB TYPE-C cable (as xiaomi edl usb cable) ← Created.
:crying:
Anyone here has a own copy of 80.10.54 firmware for 5z? SKU WW. Thanks
Team845z said:
Anyone here has a own copy of 80.10.54 firmware for 5z? SKU WW. Thanks
Click to expand...
Click to collapse
you can get it from asus website
Sent from my Asus Zenfone 5Z using XDA Labs
---------- Post added at 06:48 PM ---------- Previous post was at 06:47 PM ----------
coffeejp said:
Sorry for my poor English. I am Japanese.
fastboot does not work.
It was broken while introducing twrp.
Power does not come on.
I can connect to a PC.
It is recognized as "qualcomm hs-usb qdloader 9008".
special USB TYPE-C cable (as xiaomi edl usb cable) ← Created.
:crying:
Click to expand...
Click to collapse
did you changed your slot in fastboot mode... before installing twrp
Sent from my Asus Zenfone 5Z using XDA Labs
ajbash007 said:
you can get it from asus website
Sent from my Asus Zenfone 5Z using XDA Labs
---------- Post added at 06:48 PM ---------- Previous post was at 06:47 PM ----------
did you changed your slot in fastboot mode... before installing twrp
Click to expand...
Click to collapse
The version that I'm looking for downgrade is not available in asus website
Asus ruined my life.
I don't know how i got your tutorial totally wrong, my zenfone 5z is now running version WW_eng-8.02 , although fastboot still alive but neither raw firmware, nor SMSCT is working, am not even able to boot into Bootloader emergency, it goes into infinite boot loop. It won't flash TWRP or any boot image. Asus Flash Tool version> 1.45 not working at all, they check and say update your version. Is there any chance to debrick? My device wasn't passing Google safety check test and my private data was being shared, so all i was trying to do is relock the bootloader. Asus totally suck man, no support from ASUS End , all they did is provided us tool to unlock bootloader so that they can burn our pocket, there's no support as well from XDA dev. I don't know what to do now. The device ain't worth spending single penny on support. Big no no to any Asus product, I'll totally go I-Phone way. Among all devices i purchased till now, this one was the most powerful but most disappointing at the same time with totally negative support from day 1.
amusing_ankesh said:
I don't know how i got your tutorial totally wrong, my zenfone 5z is now running version WW_eng-8.02 , although fastboot still alive but neither raw firmware, nor SMSCT is working, am not even able to boot into Bootloader emergency, it goes into infinite boot loop. It won't flash TWRP or any boot image. Asus Flash Tool version> 1.45 not working at all, they check and say update your version. Is there any chance to debrick? My device wasn't passing Google safety check test and my private data was being shared, so all i was trying to do is relock the bootloader. Asus totally suck man, no support from ASUS End , all they did is provided us tool to unlock bootloader so that they can burn our pocket, there's no support as well from XDA dev. I don't know what to do now. The device ain't worth spending single penny on support. Big no no to any Asus product, I'll totally go I-Phone way. Among all devices i purchased till now, this one was the most powerful but most disappointing at the same time with totally negative support from day 1.
Click to expand...
Click to collapse
Why your device is running version WW_eng-8.02, didn't you follow the tutorial to unbrick?
Anyway, here is the AFT 1.0.0.71 (update bypassed) to flash raw.zip
https://drive.google.com/file/d/13xZlvJ4gXZodzQW_GD8P5gKV0jCmbTGP/view?usp=sharing
[READ BEFORE USE]
1st Disclaimer: This tool is exploring a known security flaw to unlock the device. THEREFORE IT IS NOT CONSIDERED SAFE TO USE, IF YOU USE IT, YOU'RE DOING AT YOUR OWN RISK. Nor me or the tool's creator are responsible for what you do with this tool or it's consequences. Your warranty is null and void.
You've been warned.
Click to expand...
Click to collapse
2nd Disclaimer: I'm not this tool's creator. All credits goes to them, I'm just posting it here for convenience.
Click to expand...
Click to collapse
We usually have to wait 7 days to unlock the bootloader of Xiaomi devices, right? Well, with this tool, you can cut off that timer on MTK devices, such as Poco M3 Pro/Redmi Note 10 5G.
How to Use:
1st: Download and unpack the 7zip file.
2nd: Install the drivers inside, both mtk drivers AND USB DK (x86 for 32-bit OS and x64 for 64-bit OS)
3rd: Reboot PC and turn off the device to be unlocked.
4th: Run UnlockBootloader.bat, it'll keep attempting to link, that's normal
5th: Connect your device. Either on pre-loader mode (completely off) or BROM mode (Hold Vol- while connecting the cable)
6th: Upon estabilishing a successful link, the tool will unlock your phone.
And voila, quick-unlocked.
In case of dm-verity corruption, just do this:
fastboot reboot fastboot
fastboot --disable-verity --disable-verification flash vbmeta_a [insert the vbmeta's path here]\vbmeta.img
fastboot --disable-verity --disable-verification flash vbmeta_b [insert the vbmeta's path here]\vbmeta.img
Click to expand...
Click to collapse
Unlock bootloader.bat is just opens and closes immediately....anything I'm missing here ?
nanchilanto said:
Unlock bootloader.bat is just opens and closes immediately....anything I'm missing here ?
Click to expand...
Click to collapse
Have you installed usbdk for your PC?
Gio1906 said:
Have you installed usbdk for your PC?
Click to expand...
Click to collapse
Yep , I installed the drivers , restarted the laptop. Tat unlock.bat is just opening and closing.
nanchilanto said:
Yep , I installed the drivers , restarted the laptop. Tat unlock.bat is just opening and closing.
Click to expand...
Click to collapse
Phyton installed as well?
Gio1906 said:
Phyton installed as well?
Click to expand...
Click to collapse
Yep I tried tat too.... But no luck , anyways thanks mate. I appreciate it
Hi, I' ve just tested it now and here what I have :
{
"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"
}
Anyone know how to solve that ?
Thank in advance
asen26 said:
Hi, I' ve just tested it now and here what I have :
View attachment 5624033
Anyone know how to solve that ?
Thank in advance
Click to expand...
Click to collapse
I should have added: Phyton is needed as well.
nanchilanto said:
Yep I tried tat too.... But no luck , anyways thanks mate. I appreciate it
Click to expand...
Click to collapse
As for you, I forgot to reply, my apologies... So, let's recap: mtk drivers, usbdk, phyton... I suppose libusb libraries and device hook are installed as well, right?
nanchilanto said:
Yep I tried tat too.... But no luck , anyways thanks mate. I appreciate it
Click to expand...
Click to collapse
As for you, I forgot to reply, my apologies... let's recap: mtk drivers, usbdk, phyton... I suppose libusb libraries and device hook are installed as well, right?
Gio1906 said:
As for you, I forgot to reply, my apologies... let's recap: mtk drivers, usbdk, phyton... I suppose libusb libraries and device hook are installed as well, right?
Click to expand...
Click to collapse
Everything installed , i read another article about unblocking mtk devices and followed the detailed steps by installing python etc.. Problem from my side is tat .bat file just opens and closes it's not stable at all... Anyways thanks again I have already unblocked my device through miui unlock ..
How to unlock Mediatek bootloader using mtkclient
This guide will explain how to unlock a Mediatek device's bootloader using MTKclient. This will come in handy for those who can't unlock bootloader using fastboot . This was tested on the LG K51 Warni
www.hovatek.com
wetito said:
How to unlock Mediatek bootloader using mtkclient
This guide will explain how to unlock a Mediatek device's bootloader using MTKclient. This will come in handy for those who can't unlock bootloader using fastboot . This was tested on the LG K51 Warni
www.hovatek.com
Click to expand...
Click to collapse
MY HERO!!! thank you so much!!!!
Here, i also using this tools when unlock or locked back bootloader
Hi everyone, so is it possible to unlock the bootleader without ereasing personal data using this method?
Yes, no need erase personal data.
But i see in the guide linked by @wetito that one of the steps is
python mtk e metadata,userdata,md_udc
Isn't this going to delete user data? Can i just skip thiis step?
use the tools I pinned above.
Saracawalk said:
Here, i also using this tools when unlock or locked back bootloader
Click to expand...
Click to collapse
Requirements :
• pc/laptop
• Windows 10/11 (8/8.1 possible but not tested) 64bit
• Internet connection
Material :
• mtkclient-gui + driver (fix all errors)
Steps:
1. Download the material above
2. Extract the driver
3. Go to the extracted driver folder
4. Right click android_winusb.inf and select install, then restart your pc
5. After restarting extract mtclient-gui
6. Go to the extracted folder mtkclient-gui
7. Double click on start.bat
8. turn off the cellphone
9. back to the laptop, select Unlock bootloader
10. Type y, then enter
11. press and hold vol up + vol down (approximately 5 seconds then connect to pc (still hold down the volume button)
12. release if the cellphone has been detected in cmd
13. wait for it to finish
berttest123123 said:
But i see in the guide linked by @wetito that one of the steps is
python mtk e metadata,userdata,md_udc
Isn't this going to delete user data? Can i just skip thiis step?
Click to expand...
Click to collapse
Both the tools I and wetito posted require userdata wipe. Saracawalk's one doesn't require it.
Few things to keep in mind before starting the process:
If you are on ColorOS12 make sure you are flashing OxygenOS12 and NOT OxygenOS 13; similarly if you are ColorOS13 you will have to use OxygenOS13 zip.
You must ALWAYS use OxygenOS newer than the ColorOS you have currently installed.
[English] Written Instructions:
(Note this is for 10pro, steps are the same but DON'T use any firmwares mentioned there)
How to Install Indian ROM on Chinese OnePlus 10 Pro
In this comprehensive tutorial, we will show you the detailed steps to install the Indian ROM on the Chinese OnePlus 10 Pro.
www.droidwin.com
[Chinese] Written Instructions:
关于一加ACE如何优雅的刷入氧OS12.1这件事 来自 天伞桜 - 酷安
Video Tutorial:
Downloads Links:
80W_C.15_OOS_Android13
150W_C.15_OOS_Android13
You can also follow the same instructions if you wish to convert to ColorOS. Just make sure you use ColorOS zip in that case.
Download link for ColorOS:
150W_ColorOS_C.17_Android13
I flashed OxygenOS into my new china OnePlus ACE (model PGKM10) recently. I'd like to share my experience here.
Note:
Be careful about each step, any small mistake might make your device hard bricked. If so, you have to contact the official service center to send your phone, or search for a random people who have the official internal tools to help you.
Don't simply reboot your phone if some error happened in fastboot mode, otherwise it might hard bricked.
Don't mess android version. For example use OxygenOS Android 13 and ColorOS Android 12, It will hard bricked.
Read it all before you touch your phone and PC!
Steps:
Prepare Fastboot Enhance (windows only), an OxygenOS rom.
Boot into your OnePlus ACE, enter developer mode, and enable oem unlocking and USB debugging.
Try to connect your phone with your PC. If you are using Windows 10 or newer, it would install OnePlus driver. It's necessary, otherwise you PC might not recognize your phone after enter fastboot mode. If you are using other OS, it's not required.
Turn off your device, enter fastboot mode. Note the fastboot interface looks like normal boot interface, but with some tiny text in the middle that says it's in fastboot mode.
Run fastboot flashing unlock to unlock partitions for flashing.
Prepare Fastboot Enhance, note it's windows only. If you are using other OS, you need to use fastboot command line tool, do it manually, and it has high risk. I failed once at the fastboot commands, and hard bricked.
Open fastboot enhance, click Partitions button, press Flash payload.bin, select the payload.bin file in the oxygenOS rom, and start. Some tutorials says to remove *-cow partitions, but I didn't find these partitions. That's fine.
If everything success, you can reboot your phone and enjoy!
Troubleshooting:
Myphone is not recognized by PC.
That's because your Windows PC needs OnePlus driver, try step 3.
If you completed step 3, but still got this problem. Just search it, you will get a lot of solutions. They are basically install winusb driver manually with the existing driver on PC.
My phone is hardbricked.
Don't worry.
Don't waste your time to try to solve by yourself. For example, mtk-client don't work. As the author mentioned at issue 577, Mediatek has locked it (dimencity 8100) down completely. The only way as I know is to use the official OPPO internal tools (Qualcomm 9008 mode), it requires internet and an internal employee account. Though its name, it works also for Mediatek dimencity 8100.
One way is to contact the official service center, and send your device to them. I didn't try it, but I think they can solve your issue.
Another way is to find a person who has the official internal tools, and pay for the service. The pros of this way is the whole process is online, and fast. I found NC Phone on youtube, and solved my issue. Note in this way, a Windows 64-bit, teamviewer and internet is required.
I
6cdh said:
I flashed OxygenOS into my new china OnePlus ACE (model PGKM10) recently. I'd like to share my experience here.
Note:
Be careful about each step, any small mistake might make your device hard bricked. If so, you have to contact the official service center to send your phone, or search for a random people who have the official internal tools to help you.
Don't simply reboot your phone if some error happened in fastboot mode, otherwise it might hard bricked.
Don't mess android version. For example use OxygenOS Android 13 and ColorOS Android 12, It will hard bricked.
Read it all before you touch your phone and PC!
Steps:
Prepare Fastboot Enhance (windows only), an OxygenOS rom.
Boot into your OnePlus ACE, enter developer mode, and enable oem unlocking and USB debugging.
Try to connect your phone with your PC. If you are using Windows 10 or newer, it would install OnePlus driver. It's necessary, otherwise you PC might not recognize your phone after enter fastboot mode. If you are using other OS, it's not required.
Turn off your device, enter fastboot mode. Note the fastboot interface looks like normal boot interface, but with some tiny text in the middle that says it's in fastboot mode.
Run fastboot flashing unlock to unlock partitions for flashing.
Prepare Fastboot Enhance, note it's windows only. If you are using other OS, you need to use fastboot command line tool, do it manually, and it has high risk. I failed once at the fastboot commands, and hard bricked.
Open fastboot enhance, click Partitions button, press Flash payload.bin, select the payload.bin file in the oxygenOS rom, and start. Some tutorials says to remove *-com partitions, but I didn't find these partitions. That's fine.
If everything success, you can reboot your phone and enjoy!
Troubleshooting:
Myphone is not recognized by PC.
That's because your Windows PC needs OnePlus driver, try step 2.
If you completed step 2, but still got this problem. Just search it, you will get a lot of solutions. They are basically install winusb driver manually with the existing driver on PC.
My phone is hardbricked.
Don't worry.
Don't waste your time to try to solve by yourself. For example, mtk-client don't work. As the author mentioned at issue 577, Mediatek has locked it (dimencity 8100) down completely. The only way as I know is to use the official OPPO internal tools (Qualcomm 9008 mode), it requires internet and an internal employee account. Though its name, it works also for Mediatek dimencity 8100.
One way is to contact the official service center, and send your device to them. I didn't try it, but I think they can solve your issue.
Another way is to find a person who has the official internal tools, and pay for the service. The pros of this way is the whole process is online, and fast. I found NC Phone on youtube, and solved my issue. Note in this way, a Windows 64-bit, teamviewer and internet is required.
Click to expand...
Click to collapse
In the Step #7, it should be *-cow partitions, No?
yashaswee1708 said:
I
In the Step #7, it should be *-cow partitions, No?
Click to expand...
Click to collapse
Ah, yes, it's a typo. edited.
I using color os c18 version. Can I flash oxygenOs c15 version? Both using android 13.
{
"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"
}
sSjBlueVN197 said:
I using color os c18 version. Can I flash oxygenOs c15 version? Both using android 13.View attachment 5876919
Click to expand...
Click to collapse
Better use OxygenOS13 C.18
https://gauss-componentotacostmanual-in.allawnofs.com/remove-e7d2bf870d4f18a40c740c8e51f95561/component-ota/23/02/17/2e75056f9c944c9e83dbeee99dca4734.zip
yashaswee1708 said:
Better use OxygenOS13 C.18
https://gauss-componentotacostmanual-in.allawnofs.com/remove-e7d2bf870d4f18a40c740c8e51f95561/component-ota/23/02/17/2e75056f9c944c9e83dbeee99dca4734.zip
Click to expand...
Click to collapse
are you sent to me 150w version? I flashed that version then my phone are not working, boot into OS then reboot.....
sSjBlueVN197 said:
are you sent to me 150w version? I flashed that version then my phone are not working, boot into OS then reboot.....
Click to expand...
Click to collapse
Yes it's for 150W. What you said shouldn't happen! It has worked for others.
Are you able to boot into fastboot?
(Try all key combinations)
yashaswee1708 said:
Yes it's for 150W. What you said shouldn't happen! It has worked for others.
Are you able to boot into fastboot?
(Try all key combinations)
Click to expand...
Click to collapse
I can boot into fastboot. T have done according above steps. But in step #7, i can't find *cow file so after flashed, i reboot the system but it not working normaly
Launcher not working, It just display black screen and battert percent always display 0%. After 2~3 minute, my phone auto reboot system, and I can't factory reset in settings
sSjBlueVN197 said:
Launcher not working, It just display black screen and battert percent always display 0%. After 2~3 minute, my phone auto reboot system, and I can't factory reset in settings
Click to expand...
Click to collapse
Try factory reset from recovery?
sSjBlueVN197 said:
I can boot into fastboot. T have done according above steps. But in step #7, i can't find *cow file so after flashed, i reboot the system but it not working normaly
Click to expand...
Click to collapse
If you can boot in fastboot do the process again. I'll share the zip once again
oh, I'm trying factory from recovery, it can be done. Thanks you very much ^^!
after flashed OOS, can I re-lock bootloader?
sSjBlueVN197 said:
oh, I'm trying factory from recovery, it can be done. Thanks you very much ^^!
Click to expand...
Click to collapse
Let me know if the issues are fixed
sSjBlueVN197 said:
after flashed OOS, can I re-lock bootloader?
Click to expand...
Click to collapse
You can but the process is a bit complicated, on recent updates some time the phone is bricking when we run the query fastboot flashing lock.
So I won't recommend it. Until we can find a easier way.
yashaswee1708 said:
Let me know if the issues are fixed
Click to expand...
Click to collapse
oh yeah, Issue occur when flash without format data, only format data from recovery to resolve this issue ^^
sSjBlueVN197 said:
oh yeah, Issue occur when flash without format data, only format data from recovery to resolve this issue ^^
Click to expand...
Click to collapse
So currently everything is okay?
yashaswee1708 said:
So currently everything is okay?
Click to expand...
Click to collapse
yup, everything is OK
80W_C.15_OOS_Android13 it's for Ace racing bro?