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
Related
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!!!!
[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?
This Guide will explain how to unlock your LG V40 (Every variant except T-Mobile)
Unlock Prerequisites:
Make sure you have "Enable OEM Unlock" enabled in developer options, along with adb debugging. Very important. You'll be stuck with the red triangle otherwise. If you don't have the "Enable OEM Unlock" option in developer options, you'll have to flash frp with the v35 engineering bootloader. The frp image will be provided in the attachments section.
QPST Download:
It turns out the reason QFIL is failing is because it's missing quite a bit of stuff. I'm providing the zip to QPST (It's actually required) to install. QPST includes QFIL. My fault, I'm all over the place with this... Here it is (GDrive): QPST
Booting into EDL:
Note: This can be done while booted!
1. Plug in your Phone to your PC
2. Press and hold Power and Volume Down
3. As soon as your screen blanks, rapidly start pressing volume up.
4. If you've successfully booted into EDL, your screen will be completely blank and the device manager will show (Under COM Ports): Qualcomm HS-USB QDLoader 9008
{
"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"
}
Using QFIL to Unlock Your Bootloader
QPST should be installed, and your in 9008 plugged into your PC.
Setting up QFIL:
1. Launch QFIL and set your storage type to UFS. This is located at the bottom right corner of the window The LG V40 has UFS storage. The leaked loader is a loader for LG SD845 UFS devices. If you try to send the loader with your storage set to emmc, it will NOT work. By default, it is set to emmc.
2. Select the port. Click select port and select the one that says "Qualcomm HS-USB QDLoader 9008 (COM #)" That is your phone. After it is highlighted, press OK.
3. Under select programmer, click browse, find the loader and select it.
4. Your screen should now look like this (Minus the Flat Build Stuff, that is for total unbrick purposes):
QFIL is now all setup and ready for flashing.
Flashing the Engineering Bootloader
1. In the upper left hand corner of the Window, click on Tools > Partition Manager from the drop down menu
2. When the Partition Manager window comes up, find "abl_a" > click on it > right click and select Manage Partition Data.
3. When the "Raw Data Manager" window comes up, there are four options to choose from (I'll tell you what each of them does):
Erase: Wipes the specified partition clean
Read Data...: Backs up the partition. It will tell you where it saved it in the log output in the main window
Load Image: Flashes a .img file of your choice to the specified partition
Close: Brings you back to the Partition Manager
You'll be using the load image function to flash the V35 Engineering bootloader to your device.
4. Click load image then select the V35 engineering bootloader. It will flash the image to your device.
Unlocking Your Device:
Now that the V35 Engineering Bootloader has been flashed to your device:
1. Press and hold the Power and Volume Down buttons until your device reboots out of 9008. When you hear the disconnect sound, immediately hold volume down (only volume down) to enter fastboot right away (this is required for both methods, my apologies).
2. When you've entered fastboot, execute this command:
Code:
fastboot oem unlock
Userdata will be wiped as a security measure as with all android devices.
3. While you're still in the v35 engineering bootloader flash back the stock pie bootloader (If originally on pie firmware) with:
Code:
fastboot flash abl_a path/to/ablpiestock.img
The V35 Engineering bootloader is OREO only. Some people have managed to boot with this on pie firmware. But generally, you WON'T be able to boot with this flashed if you're on PIE firmware. If you're on Oreo firmware, you can leave this flashed
4. For devices without the "Enable OEM Unlock" option, you'll need to flash frp! You can do so with (While still in V35 Bootloader):
Code:
fastboot flash frp path/to/frp
4a. Reboot right back into fastboot (hold volume down after rebooting) and run:
Code:
fastboot oem unlock
The reason you can't unlock your T-Mobile device is because no other bootloader/firmware will work with T-Mobile devices. Only T-Mobile firmware will work on it. If you're looking for root, avoid V405TA (T-Mobile) phones. Any other model will work for this.
For some reason, the status says Download Fail:Fail to find QDLoader port after switch when I try to go to the partition manager.
Crap, I completely forgot an important detail. If you are using 9008 mode for the first time, you'll need to update the driver in Device Manager. Then select the port. My fault, I'll update that now.
It should say: Qualcomm HS-USB QDLoader 9008
Xsavi said:
Crap, I completely forgot an important detail. If you are using 9008 mode for the first time, you'll need to update the driver in Device Manager. Then select the port. My fault, I'll update that now.
It should say: Qualcomm HS-USB QDLoader 9008
Click to expand...
Click to collapse
That would do it???. I'll try doing that
@Xsavi This is Awesome! I might get a V40 later in the year
Btw a small point, the title says: Unlock your LG V40 (Via 9008) Root ONLY for T-Mobile variants.
while guide says: his Guide will explain how to unlock your LG V40 (Every variant except T-Mobile)
Title probably needs to be corrected
tech_infinity said:
@Xsavi This is Awesome! I might get a V40 later in the year
Btw a small point, the title says: Unlock your LG V40 (Via 9008) Root ONLY for T-Mobile variants.
while guide says: his Guide will explain how to unlock your LG V40 (Every variant except T-Mobile)
Title probably needs to be corrected
Click to expand...
Click to collapse
Title and guide has been corrected. Thank you for the much needed suggestion!
Also getting a Download Fail, but mine reads "Download Fail:Sahara Fail:QSaharaServer Failrocess fail". My port is showing as Qualcomm HS-USB QDLoader 9008 (COM7). I was sure to try to update the driver in device manager, and am prompted that "The best drivers for your device are already installed".
toddyskates said:
Also getting a Download Fail, but mine reads "Download Fail:Sahara Fail:QSaharaServer Failrocess fail". My port is showing as Qualcomm HS-USB QDLoader 9008 (COM7). I was sure to try to update the driver in device manager, and am prompted that "The best drivers for your device are already installed".
Click to expand...
Click to collapse
The culprit is QFIL being by itself instead of being installed with QPST.
Is that a full, permanent unlock V30-style? So that means that I could now go ahead and buy a North American LG V40 safely as long as it isn't T-Mobile?
WaseemAlkurdi said:
Is that a full, permanent unlock V30-style? So that means that I could now go ahead and buy a North American LG V40 safely as long as it isn't T-Mobile?
Click to expand...
Click to collapse
With 9008 and this firehose, you have complete access to your phone and can flash anything you want with no restrictions.
As long as it isn't T-Mobile, you're fine. The firehose works on those models, but any other firmware/bootloader won't work, so you can't really unlock on T-Mobile models.
How to enter edl mode?
I can't wait to try this!
I'm holding pwr & - vol until the phone resets. While holding pwr & - vol down, I am tapping + vol. I can't get to the blank screen, the phone just restarts normally. Any advice?
clutterking said:
I can't wait to try this!
I'm holding pwr & - vol until the phone resets. While holding pwr & - vol down, I am tapping + vol. I can't get to the blank screen, the phone just restarts normally. Any advice?
Click to expand...
Click to collapse
You have to start pressing volume up as soon as the screen blanks. It's an extremely small window. It'll take a few tries though. Plug in your device, and as soon as you hear the disconnect sound, start pressing volume up. It helps a little for me.
Confirmed working for Korean model LM-V490N!
Xsavi said:
With 9008 and this firehose, you have complete access to your phone and can flash anything you want with no restrictions.
As long as it isn't T-Mobile, you're fine. The firehose works on those models, but any other firmware/bootloader won't work, so you can't really unlock on T-Mobile models.
Click to expand...
Click to collapse
Awesome! You guys are brilliant!
So do we expect a kickstart in development (like the V30's dev scene) now that an unlock is available for everybody?
And one last question: does this mean that we can unlock a (network) locked phone this way? I know that the usual answer is 'no', but from what I've seen around here, there's something called 'cross-flashing' of US unlocked firmware. Perhaps that means an unlock?
If not, do online unlock services work? (I do not want any names - I just want to know whether any service at all works).
I do apologize if my questions are stupid - it's only that with the overwhelming amount of (sometimes contradictory) posts here, I just want to make sure I'm doing everything correctly! :laugh:
WaseemAlkurdi said:
Awesome! You guys are brilliant!
So do we expect a kickstart in development (like the V30's dev scene) now that an unlock is available for everybody?
And one last question: does this mean that we can unlock a (network) locked phone this way? I know that the usual answer is 'no', but from what I've seen around here, there's something called 'cross-flashing' of US unlocked firmware. Perhaps that means an unlock?
If not, do online unlock services work? (I do not want any names - I just want to know whether any service at all works).
I do apologize if my questions are stupid - it's only that with the overwhelming amount of (sometimes contradictory) posts here, I just want to make sure I'm doing everything correctly! :laugh:
Click to expand...
Click to collapse
Your questions aren't stupid.
Unfortunately, you can't sim unlock using this method. I'm hoping this will kickstart development for this device also, I already have a few ROMs made I have yet to release to XDA. Any 3rd party online unlock services are scams. Nowadays, everything is done server side when it comes to SIM unlocking your phone.
No problem dude! If you have any other questions, feel free to reach out to me. I'm super active in the V40 telegram group. I'm becoming more active here too (I need to. LoL).
Fantastic!!! Really appreciate all the hard work.
Sent from my LM-V405 using Tapatalk
TheLinuxMan02 said:
Note: If on Pie firmware, boot back into 9008 and flash the latest TWRP, along with the stock ABL so you can boot back into your firmware. With the engineering bootloader, you can't boot pie firmware. Only oreo.
Click to expand...
Click to collapse
Hey, thanks so much for this method. A damned shame we got to go through this just to get fastboot on these damn phones, but you're the all-stars we need to get it going.
Question. How are we flashing TWRP and ABL? Using fastboot or QFIL? Also, do you have a link to the latest TWRP? I know there's a thread in this forum for TWRP by SGCMarkus. Is that the TWRP version you recommend?
copota said:
Hey, thanks so much for this method. A damned shame we got to go through this just to get fastboot on these damn phones, but you're the all-stars we need to get it going.
Question. How are we flashing TWRP and ABL? Using fastboot or QFIL? Also, do you have a link to the latest TWRP? I know there's a thread in this forum for TWRP by SGCMarkus. Is that the TWRP version you recommend?
Click to expand...
Click to collapse
You can use either method to flash twrp and abl. If in QFIL, just follow the steps above but choose boot_a or boot_b for TWRP, and abl_a and abl_b for stock abl.
I can't get my phone into 9008 mode. Would it be because I crossflashed my phone? Here's my crossflashing history...
edit: Never mind, when I plugged my phone into a power source, then tried it, I was able to get into 9008 mode.
Is this something that could be blocked in a further update? Is there something LG could do to block it?
Thanks again
Hi all, dumbass me was so excited to get a new phone, I went around Redmi Note 10 ROMs on my Note 10 5G and bricked it... It won't boot into fastboot or recovery. When I boot it up holding the up/power buttons, the screen lights up and phone gets briefly recognized by my computer before rebooting. I've done some digging around and tried to find edl point? of this phone but couldn't get far. Any help would be appreciated!
{
"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"
}
assistance... you have lost warranty. anyway you can try this metod (work with my old mia3 but have a qualcomm chipset)
first: CLOSE YOUR PHONE!
install mi pro flash tool https://www.androidfilehost.com/?fid=14943124697586360238
PRESS power+ vol up+vold -
connet to pc via USB
OPEN MIflash tool pro
if your phone will be recognized you can flash stock firmware
with miflash pro you can install all drivers you need (but i'm not sure, test by yourself)
good luck.
if this procedure don't work go to an assistance point. you have damaged the bootloader
before mod devices with a/b partitions is very important read guides with attention. if you don't want trash a new device
you can also try sp flash tool, specific for mtk devices
How-to flash or install Stock ROM (Firmware) using SP Flash Tool
Step-by-Step guidelines to flash or install Stock ROM (Scatter Firmware) on Mediatek devices using the SP Flash Tool.
androidmtk.com
tannedcan said:
Hi all, dumbass me was so excited to get a new phone, I went around Redmi Note 10 ROMs on my Note 10 5G and bricked it... It won't boot into fastboot or recovery. When I boot it up holding the up/power buttons, the screen lights up and phone gets briefly recognized by my computer before rebooting. I've done some digging around and tried to find edl point? of this phone but couldn't get far. Any help would be appreciated! View attachment 5431881
Click to expand...
Click to collapse
did you even open it? tannedcan in every single post where there are instructions how to root/unlock/change rom
there is a DISCLAIMER for a reason.
that msg remark that you can brick your device if you dont know what you are doing or if you have doubts!
most of times things can be recovered but NEVER open a device in warranty.
simika said:
did you even open it? tannedcan in every single post where there are instructions how to root/unlock/change rom
there is a DISCLAIMER for a reason.
that msg remark that you can brick your device if you dont know what you are doing or if you have doubts!
most of times things can be recovered but NEVER open a device in warranty.
Click to expand...
Click to collapse
yes, i'm 100% agree with you
tannedcan said:
Hi all, dumbass me was so excited to get a new phone, I went around Redmi Note 10 ROMs on my Note 10 5G and bricked it... It won't boot into fastboot or recovery. When I boot it up holding the up/power buttons, the screen lights up and phone gets briefly recognized by my computer before rebooting. I've done some digging around and tried to find edl point? of this phone but couldn't get far. Any help would be appreciated! View attachment 5431881
Click to expand...
Click to collapse
I was exactly in same trouble, use This guide that solve the issue.
How to flash an MTK secure boot device without a custom DAThis is a step by step guide showing how to flash a Mediatek (MTK) secure boot device without using a custom download agent (DA). A little history Secure Boot M
forum.hovatek.com
Press mobile three buttons and connect cable to pc (use USB 2.0) to enter BROM mode (are like ERL mode in Snapdragon models). Because mtk models don't have test point. So don't need to disarm mobile.
Did you find the solution?
please any solution? i am into same problem. need stock rom for
Redmi Note 10 5G choppin
Zaiserr2 said:
I was exactly in same trouble, use This guide that solve the issue.
How to flash an MTK secure boot device without a custom DAThis is a step by step guide showing how to flash a Mediatek (MTK) secure boot device without using a custom download agent (DA). A little history Secure Boot M
forum.hovatek.com
Press mobile three buttons and connect cable to pc (use USB 2.0) to enter BROM mode (are like ERL mode in Snapdragon models). Because mtk models don't have test point. So don't need to disarm mobile.
Click to expand...
Click to collapse
this really helped, thanks but only with usb 3.0
tannedcan said:
Hi all, dumbass me was so excited to get a new phone, I went around Redmi Note 10 ROMs on my Note 10 5G and bricked it... It won't boot into fastboot or recovery. When I boot it up holding the up/power buttons, the screen lights up and phone gets briefly recognized by my computer before rebooting. I've done some digging around and tried to find edl point? of this phone but couldn't get far. Any help would be appreciated! View attachment 5431881
Click to expand...
Click to collapse
same issue sir my device show handshake failed during flashing
wetito said:
assistance... you have lost warranty. anyway you can try this metod (work with my old mia3 but have a qualcomm chipset)
first: CLOSE YOUR PHONE!
install mi pro flash tool https://www.androidfilehost.com/?fid=14943124697586360238
PRESS power+ vol up+vold -
connet to pc via USB
OPEN MIflash tool pro
if your phone will be recognized you can flash stock firmware
with miflash pro you can install all drivers you need (but i'm not sure, test by yourself)
good luck.
if this procedure don't work go to an assistance point. you have damaged the bootloader
before mod devices with a/b partitions is very important read guides with attention. if you don't want trash a new device
you can also try sp flash tool, specific for mtk devices
How-to flash or install Stock ROM (Firmware) using SP Flash Tool
Step-by-Step guidelines to flash or install Stock ROM (Scatter Firmware) on Mediatek devices using the SP Flash Tool.
androidmtk.com
Click to expand...
Click to collapse
is it okey or I'm the only one whose phone just keeps getting recognized and unrecognized by the PC every 5-10 sec ????
even though i have tried same with diffrent PCs and diffrent cables
PLEEEEEEEEEEEEASE HELP because this is by far the biggest obstacle I had in this precedure
It is not OK, you are the only one
Start from BROM mode and proceed from there.
viktak said:
It is not OK, you are the only one
Start from BROM mode and proceed from there.
Click to expand...
Click to collapse
I appreciate your response but
i did it all
i already have python the last version
i downloaded the MTK driver
i pressed the whole 3 buttons in the phone connected to PC (the phone didn't give any output at all)
i did set it up (which does appear and dissapear in every 5secs so I had to be quick)
then for the main.py file didn't capture the phone (obviously because I constantly hear the devices get recognized and unrecognized and nor the cable nor the PC are the cause
the theeere I am, stuck in the very 1st step.
please I would be so thankful if you could diagnose the problem just for me to know what to do.
personally I don't think it's a phone hardware problem because back in the days lol i unlocked bootloader and installed recovery, all was very functional and everything responded smoothly
if you wanted to know any other detail i would be so pleasured to tell you
I don't have the time now. Earliest I can help you is on Monday. Send me a PM to arrange for it.
viktak said:
I don't have the time now. Earliest I can help you is on Monday. Send me a PM to arrange for it.
Click to expand...
Click to collapse
alright, appreciate it
thank you
pardon my abbreviations knowledge but I really don't know what a PM is
Did anyone found the way to back the phone to life???
If anyone can respond me quickly I will apreciate it.
Yes, it's quite easy. Just follow my guide on my blog. DM for details.
viktak said:
Yes, it's quite easy. Just follow my guide on my blog. DM for details.
Click to expand...
Click to collapse
Ok, I will see
viktak said:
Yes, it's quite easy. Just follow my guide on my blog. DM for details.
Click to expand...
Click to collapse
I have a problem, I can't make it work, not even the fastboot or MTK tools
viktak said:
Yes, it's quite easy. Just follow my guide on my blog. DM for details.
Click to expand...
Click to collapse
post a link to your blog
viktak said:
I don't have the time now. Earliest I can help you is on Monday. Send me a PM to arrange for it.
Click to expand...
Click to collapse
i need help on this very issue pls help meee
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?