[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?
Related
Flashing stock ROM on LG L Fino
Since the device is pretty new and there is no other such guide for the Fino I decided to make one.
Flashing stock firmware on LG devices is universal (for the most part) so this guide will be pretty straight up.
This guide should be compatible with both the Dual Sim Fino and the regular one and all variants between them N/F/G etc.
I will try to make this as noob friendly as possible.
Click to expand...
Click to collapse
__________________
Flashing a stock ROM:
Can unbrick the device (only if softbricked)
Will remove root
Can Wipe user data
Can brick device (If done incorrectly)
__________________
STEPS:
STEP 1: Download and Install the LG DRIVER from here.
You might want to restart your computer after driver installation.
STEP 2: Download LG FLASH TOOL 2014 from here and extract it IN a NEW folder somewhere.
STEP 3: Download a KDZ firmware file from here
BE SURE YOU ARE DOWNLOADING THE RIGHT FIRMWARE FOR YOUR DEVICE (D290N, D295 and so on) OTHERWISE YOUR DEVICE MIGHT BECOME A HARD BRICK!!! LOOK FOR THE DEVICE MODEL BEHIND THE BATTERY!
Click to expand...
Click to collapse
STEP 4: Extract the FIRMWARE.KDZ file IN the same folder as the LG FLASHTOOL 2014.
STEP 5: Enter DOWNLOAD MODE on the device. You can do that by connecting a USB cable to the computer and then pressing and holding the VOLUME UP button while inserting the USB in to the phone.
STEP 6: Start LGFlashTool2014.exe. You should have something like this open:
{
"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"
}
STEP 7: In type ALLWAYS choose CDMA.
STEP 8: IN KDZ browse to the KDZ file you extracted earlier and select it.
STEP 9: Select Normal or CSE Flash
Normal Flash: Flash the ROM on top of the current one ( Good for updating firmware)
CSE Flash: Flash the ROM after WIPING EVERYTHING. (Good if testing new ROM or restoring a brick)
Click to expand...
Click to collapse
STEP 10: After selecting either you will be transferred to another screen with data on it. Don't edit anything and just click START
STEP 11: After that you will be yet again transferred to another screen like this:
Dont change or tick anything and just click OK
STEO 12: After that the process of FLASHING will begin.
THIS PROCESS CAN'T BE STOPPED SO BE SURE YOU HAVE EVERYTHING NEEDED TO WAIT FOR 5-20 MINUTES FOR IT TO COMPLETE.
DO NOT UNPLUG THE DEVICE UNTIL IT HAS FULLY BOOTED!
Click to expand...
Click to collapse
If you get an error saying something about failed downloads and whatnot DO NOT CLICK ON ANYTHING! and wait about 15 minutes. The program might just display these errors but the process will continue.
Do not worry if the program says disconnected or crashes at the end of the procedure. This is normal
STEP 13: Enjoy your reflashed device
__________________
By following this guide you agree that I TAKE NO RESPONSIBILITY FOR BRICKED OR DAMAGED DEVICES.
You and only you decided to follow these instructions.
Click to expand...
Click to collapse
Download the KDZ you need here: https://lg-firmwares.com/
johnwilliam_a_k_a_trash said:
Nice tutorial!
Click to expand...
Click to collapse
Thanks
Glad to help.
Does anyone experimented issues installing drivers? I've installed several versions and it still not detecting/recognizing the device and searching for drivers in windows update. (Windows7, D290n).
---------- Post added at 12:36 PM ---------- Previous post was at 12:05 PM ----------
carmeloamg said:
Does anyone experimented issues installing drivers? I've installed several versions and it still not detecting/recognizing the device and searching for drivers in windows update. (Windows7, D290n).
Click to expand...
Click to collapse
SOLVED: After disabling windows update, uninstalling every single driver version for the device, unplugging network connection and reinstalling drivers (4.0.3) it worked. Thanks and hope help if it is your case.
Ok so i tried to flash kdz file but on 60% it say "The phone is disconnected from PC" What should i do?
cyber808 said:
Ok so i tried to flash kdz file but on 60% it say "The phone is disconnected from PC" What should i do?
Click to expand...
Click to collapse
You can start over... But this time check that the USB connection is stable and the drivers are all updated
Lg l fino hardbricked!
Hi! i'm a newbie here, can you teach me to unbrick a hardbricked lg l fino? no download mode and it says boot security error, it has been days solving this problem ...
micoevil said:
Hi! i'm a newbie here, can you teach me to unbrick a hardbricked lg l fino? no download mode and it says boot security error, it has been days solving this problem ...
Click to expand...
Click to collapse
Deppends if it really is hard bricked. Can you enter download mode?
meganukebmp said:
STEP 5: Enter DOWNLOAD MODE on the device. You can do that by connecting a USB cable to the computer and then pressing and holding the VOLUME DOWN button while inserting the USB in to the phone.
__________________
Click to expand...
Click to collapse
I have LG L Fino D295. I cannot enter to Download Mode as there is error message "error boot certification verify" and then the device goes black. By removing the battery, put it back and press power button the phone goes normally. Any solution for cannot entering the Download Mode?
I found this thread: http://forum.xda-developers.com/showthread.php?t=2582142 but I couldn't find the files needed (sbl1.img, aboot.img, rpm.img, tz.img) which I assume the stock files for LG Fino L D295. And not really sure this will help me to enter the Download Mode.
Just as background: when I update the firmware via OTA, the system says that my phone is suspected to be rooted. since then my camera is not working. Clear cache and data didn't help.
Any suggestion would be appreciated.
thenks bro
Hello, I have a problem because after installing TWRP on Lg l'fino from time changed the android I changed not at all aboot on orginale and call me zbrickował
I wanted to install in new home Stock for lg flash tool because tele enters into download mode but as it starts to upload new stock becomes 2% percent and pops it failed Tele. 100% charged and detectable packages for Windows
Could anyone help ?? Thanks in advance: D
My English is poor
rohanekpl said:
Hello, I have a problem because after installing TWRP on Lg l'fino from time changed the android I changed not at all aboot on orginale and call me zbrickował
I wanted to install in new home Stock for lg flash tool because tele enters into download mode but as it starts to upload new stock becomes 2% percent and pops it failed Tele. 100% charged and detectable packages for Windows
Could anyone help ?? Thanks in advance: D
My English is poor
Click to expand...
Click to collapse
Try reinstalling LG driver and try plugging in another USB port on your PC.
So I tried to do some driver version I installed, each USB port podłanczałem and all the time is this problrm on your computer is at 2% and continue on your 0% and nothing happens, I wanted to also add that when I turn on the tele. normally it shows the logo lg and the phone vibrates at some time after 2 times,Lg phone detects a mobile phone but the phone installs the first time you connect it does not want to load up to the end,
maybe this is the problem that you have Windows 10 ?? Maybe it is going to change a recovery program ?? and not by the emulator
---------- Post added at 02:49 PM ---------- Previous post was at 02:27 PM ----------
proudlytm said:
Try reinstalling LG driver and try plugging in another USB port on your PC.
Click to expand...
Click to collapse
So I tried to do some driver version I installed, each USB port podłanczałem and all the time is this problrm on your computer is at 2% and continue on your 0% and nothing happens, I wanted to also add that when I turn on the tele. normally it shows the logo lg and the phone vibrates at some time after 2 times,Lg phone detects a mobile phone but the phone installs the first time you connect it does not want to load up to the end,
maybe this is the problem that you have Windows 10 ?? Maybe it is going to change a recovery program ?? and not by the emulator
I flashed my d290g with a d295 firmware to install a rom on it. Now I'm trying to flash the original firmware with the flash tool but I can't manage to flash it, I've tried adding the d290 unlocked bootloader but it's still not flashing. Is there anyway to force the flash tool to install the firmware without checking the model of it or to make a flasheable zip for TWRP with the d290g firmware?
LG L Fino Hard Bricked
Hi. Sorry for me english.
I have LG L Fino (D290N) and me phone hard bricked. when I instal TWPR with aboot.img and rashr application me phone reboot and I have purple screen with DBI Apps Watchdog Reset or black screen all time. No have logo LG, only black screen. No have download mode, recovery mode, fastboot mode. Cant reperair with LG Support tool because have error with me baterry not full charging.
What I must doo to unbricked my phone ? Please help me
To everyone that has hard bricked their phone:
There is no fix of hard bricked LG L Fino we are aware of as of now!
The only way out is to give your phone to warranty service and get it replaced or get its motherboard replaced!
Please, note that you should be very careful when typing these two commands, installing aboot and recovery!
You are doing this at your own risk!
D290 firmware link dead.. File not found... Please post another mirror link.. I need this firmware urgent.... D290
Abdul.wahid9001 said:
D290 firmware link dead.. File not found... Please post another mirror link.. I need this firmware urgent.... D290
Click to expand...
Click to collapse
Links are not dead. Just download for another region.
i can'tf find custom ROM for this device. How did you found?
Hiparci said:
i can'tf find custom ROM for this device. How did you found?
Click to expand...
Click to collapse
Me and my friends made it.
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!!!!
Hello everyone,
I bricked my Z2 Pro and after hours of searching and trying to fix it by flashing stock ROM via EDL I'm desperate so I would be grateful for any help.
My Z2 came with some custom ROM from shop with 1.9 version on it without OTA so I decided to flash it with different ROM. I unlocked the bootloader, flashed TWRP and SU, but flashing Gedeon ROM via TWRP ended with an error (error code 7 or 11 if I remember correctly). So I decided to flash stock ROM following
this guide.
QFIL recognized the device correctly as Qualcomm HS-USB QDLoader 9008, but I kept receiving this error:
02:20:14: ERROR: function: sahara_rx_data:194 Unable to read packet header. Only read 0 bytes.
02:20:14: ERROR: function: sahara_main:854 Sahara protocol error
02:20:14: ERROR: function: main:265 Uploading Image using Sahara protocol failed
Download Fail:Sahara Fail:QSaharaServer Failrocess fail
So I followed this guide that recommends to use MiFlash instead of QFIL.
After few unsuccessful updates (it wasn't able to open the port) it finally finished downloading the ROM (2.0.057 ST) with this message at the end: The operation completed successfully.(0x00000000: ApplyPatch sector NUM_DISK_SECTORS-1., offset 16, value CRC32(NUM_DISK_SECTORS-1.,92), size 4)
It took about 55s.
However after I unplugged Z2 from the USB cable and hit the power button, nothing happened. Since the update the screen is off, the LED light is off. Even if I hold the power off button for one minute.
When I plugged the phone back, it was still recognized as QDloader 9008, so it is apparently stuck in the EDL mode.
I tried all stock ROMs from here multiple times with the same result. Multiple times with the "successful update" message, but nothing happens.
EDIT: Now, after few tries the of the same process it is not even updating the ROM at all. It says "Open serial port failed" and afterwards "Missing hello packet, try to recover" (I waited about 5 min, but the message didn't change).
Please help
I hope for a solution without the need to unplug the battery, but if it will be necessary, I will do it.
Thank you!
Creshaw said:
Hello everyone,
I bricked my Z2 Pro and after hours of searching and trying to fix it by flashing stock ROM via EDL I'm desperate so I would be grateful for any help.
My Z2 came with some custom ROM from shop with 1.9 version on it without OTA so I decided to flash it with different ROM. I unlocked the bootloader, flashed TWRP and SU, but flashing Gedeon ROM via TWRP ended with an error (error code 7 or 11 if I remember correctly). So I decided to flash stock ROM following
this guide.
After few unsuccessful updates (although it recognized the device correctly as Qualcomm HS-USB QDLoader 9008, it wasn't able to access it via the relevant port) it finally updated the ROM (2.0.057 ST) with successful message at the end (the flash itself took about 55s). However after I unplugged Z2 from the USB cable and hit the power button, nothing happened. The screen is off, the LED light is off. Even if I hold the power off button for one minute.
When I plugged the phone back, it was still recognized as QDloader 9008, so it is apparently stuck in the EDL mode.
I tried all stock ROMs from here multiple times with the same result. Still successful update, but nothing happens.
Please help
I hope for a solution without the need to unplug the battery, but if it will be necessary, I would do it.
Thank you!
Click to expand...
Click to collapse
Can you verify if you followed step 1.1.2.
1.1.2 If you opend QFIL swich to the FireHoseConfiguration and enter the following settings:
syedtahir16 said:
Can you verify if you followed step 1.1.2.
1.1.2 If you opend QFIL swich to the FireHoseConfiguration and enter the following settings:
Click to expand...
Click to collapse
Yes, everything step by step. I even have the same version of QFIL (QPST is build 437 instead of suggested 434 - I suppose that won't be causing any problem). I tried to reboot my PC, different USB ports, reinstall drivers (as I previously had Lenovo USB driver and before the flash I installed the ZUK driver as well as without the ZUK drivers it wasn't recognized as QDLoader).
Zukfans.eu
Btw I'm unable to sign up to zukfans.eu to place my question there as well as. It asks for CAPTCHA verification, however there is no CAPTCHA shown, only the verification question "what zuk have you ?". I filled in there 'ZUK Z2 Pro', copied the question in there etc., used 4 different broswers on 2 devices and networks, no luck. And it is not possible to log in via FB as well.
I was working on it until 4AM last night and today I completely forgot to describe the important part about MiFlash
Please see in the original post.
Thanks for your your reply!
Creshaw said:
I was working on it until 4AM last night and today I completely forgot to describe the important part about MiFlash
Please see in the original post.
Thanks for your your reply!
Click to expand...
Click to collapse
I'm not sure about Miflash. I used QFIL.
Also, I wrote a small tutorial. See if that helps:
http://zukfans.eu/community/threads...rom-zuk-z2-pro-z2121-only.57/page-8#post-7282
If you are unable to use that link. Below is an extract:
"The QFIL zip contained the ROM twice. so you can load the contents.xml from the parent folder or the other folder within the zip too.
Make sure you extract the ROM in a short part i.e. "C:\Z2Pro\
1) Firstly, the tricky part having the tool recognize the qualcomm port.
Solution: Uninstall the tool, USB drivers (i.e. Zuk drivers), any existing qualcomm drivers.
Reboot.
Install Zuk drivers.
Install the tool. (According to the guide, the tool will also install the drivers for qualcomm, but for some reason it did not)
Install the qualcomm drivers.
2) Fortunately, my phone was not bricked. So I could easily get into edl mode using "adb reboot edl"
3) While trying to get this to work, some RELINK driver was installed instead of qualcomm. Uninstall that if you see that.
4) Anyway, back to our troubleshooting. So you would think that you are all set and your qualcomm port should be recognized, but no. It failed to recognize. So try this:
Reboot PC.
Reboot Phone.
5) Now Proceed. Hopefully by now you have see your qualcomm port. Great.
6) This is the trickiest part. You need to click on the "Download Content" "IMMEDIATELY" "AS SOON AS" you hit enter on "adb reboot edl".
[Image]
{
"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"
}
7) Yay. You see very nice progress in the little progress section on QFIL. You think you'ved nailed it.. But no, you could again end up getting another error. (Unfortunately I forgot to get a screenshot). Anyway, you would see this multiple times, that the "File access is very slow"; I'm not sure if only I received that error or if it is generic.
8) When you get an error at this point. Try a different port. Luckily, I got it to work on my second attempt on another attempt.
My review on the stock ROM:
Honestly, the custom ROM installed by the seller worked way better for me. This stock ROM had a lot of chinese apps (which of course I can uninstall). But somehow, the custom ROM from the seller felt better. Luckily I had a nandroid backup and I went back to it. The only drawback apart from OTA, being on the latest etc etc is that I cannot use the heartrate sensor (which is no big deal for me).
I guess I'll wait for another AOSP or another custom ROM or probably something with Android N before I upgrade again.
Hope this helps."
Thanks for getting back to me. I remember reading this before, however I cannot apply it to the current situation (but I tried anyway).
However there is an update to share. After some time I was able to go through the full download via MiFlash as before (with the 'successful' message) and moreover, flashing via QFIL finally started to produce something promising, however at the end it showed this message (no change to the state of the phone):
View attachment 131237287087498319.log
Next try showed the same error message as before:
View attachment 131237297946525488.log
SOLVED!
Hallelujah! After many many many tries (just doing the same over and over and over) the stock ROM (2.0.048) was finally uploaded (using QFIL)!
I was trying to hold power off and/or volume buttons while and after connecting to PC just to try different things and maybe that helped as well.
If someone will experience the same issue as me, I have one advice - don't loose your faith, don't give up!
And if you are thinking about flashing via MiFlash, simply just don't.
Creshaw said:
Hallelujah! After many many many tries (just doing the same over and over and over) the stock ROM (2.0.048) was finally uploaded (using QFIL)!
I was trying to hold power off and/or volume buttons while and after connecting to PC just to try different things and maybe that helped as well.
If someone will experience the same issue as me, I have one advice - don't loose your faith, don't give up!
And if you are thinking about flashing via MiFlash, simply just don't.
Click to expand...
Click to collapse
Glad you got it figured out! Enjoy your Z2 Pro
Hello there, I'm having a similar problem that the owner of this thread had, but the difference is that the adb doesn't detects my device.
I've tried to reinstall all the drivers, and downloaded the Android SDK tools, but still doesn't works...
Any idea about what to do? The device is with the screen in black, no led blinks or anything like that, and when connected to the PC, only detrects the Qualcomm 9008 port...
Thank you in advance.
Now after some research, I found out that the "ADB interface" is not showing in Windows device manager
I tried to install it manually, but can't find a way to get it working, and after the flash, USB debugging was set on, so can't figure out what could be happening...
Is it possible it's completely dead?
Any idea?
--
Thanks to valuable help from Emmaus and DanRO from zukfans.eu I managed to render my phone operable once more and now it runs flawlessly. This recovery is a life-saver for anyone experiencing bricking or malfunction issues:
https://yadi.sk/d/DfTYl-jz3Cxg76
_The first thing to do is to enter fastboot menu (pressing vol rockers will help)
_Then you will need to unlock bootloader with the dedicated commands:
fastboot -i 0x2b4c flash unlock unlock_bootloader.img
fastboot -i 0x2b4c oem unlock-go
For noobs or newcomers: Be informed that you will need the OEM bootloader image from ZUK website through giving your credential and phone's serial number for unlocking, you can see the instructions on the forum or by googling it.
_After unlocking your bootloader you should flash the aforementioned and link-given recovery with the following commands:
fastboot -i 0x2b4c flash recovery twrp_name.img
(Replace "twrp_name" with the name of the downloaded image and without quotes)
_Once you successfully enter TWRP Recovery menu, you can either flash a TWRP-flashable file or else, by tapping reboot button you can select EDL (9008) option to open 9008 port on QPST for being able to flash any official firmware.
_Check your internal storage on flashing TWRP-flashable ROMs. In my case, after I flashed recovery and then a CM-based ROM (AICP), I saw that the phone had only a 9GB-size as internal storage. If you happen to face the same issue, just flash an official firmware on QPST, as this problem occurs due to bad partitioning, at least that is what it seems.
Ask anything for any further details.
Thanks.
Can't power off....help!
Hi all.
My Z2 Plus is old 4 day! Buyed from Gearbest, i flashed the latest stock CN Firmware with QFIL, unlocked bootloader, installed CN TWRP and flashed GizRom 1.1 from Franck076,
After this, i backupped all from TWRP and flashed Francko76 Global v7 and Mokee Official 7.1.1 for test. To return to normal use, i restored the backup GizChina Rom 1.1 and i rebooted.
DISASTER!
My Zuk Z2 screen is black, no flashing led, it's vibrate every 25/30 seconds andt there's no way that i can power off! I read so many guides to unbrick, but all say that the phone is switched off. In every tested so it continues to vibrate...
Please, help me!
Also I am Now Bricked
When Z2Pro was hung up during QFIL connection with EDL mode, It cannot but wait until battery empty because it does not reaction to the reboot with the VOL PowerBtn's switch either.
if Disassemble the Z2pro then remove buttery,maybe re-QFIL.
Anyone,want you to tell me if you know the method for reboot z2pro.whthout Disassemble it.
maofedeli said:
Hi all.
My Z2 Plus is old 4 day! Buyed from Gearbest, i flashed the latest stock CN Firmware with QFIL, unlocked bootloader, installed CN TWRP and flashed GizRom 1.1 from Franck076,
After this, i backupped all from TWRP and flashed Francko76 Global v7 and Mokee Official 7.1.1 for test. To return to normal use, i restored the backup GizChina Rom 1.1 and i rebooted.
DISASTER!
My Zuk Z2 screen is black, no flashing led, it's vibrate every 25/30 seconds andt there's no way that i can power off! I read so many guides to unbrick, but all say that the phone is switched off. In every tested so it continues to vibrate...
Please, help me!
Click to expand...
Click to collapse
Have you figured out a way?
Hi all,
received a Z2 pro, flashed with multi language rom, without OTA upgrades. When sim inserted, there was no connection to the network. After several attempts, i decided to send it back.
Ordered from another shop a new 2 ro, ( i know, very stupid to try twice) and this time, when tried to flash it from multi language rom, with an official one, it was bricked. Deep flash trick and.....
Tried several times to open HS-USB QDloader 9008 and once every 20 times it was a success. But, Sahara error all the time in qfil and hallo packet error in miflash. I'm out of ideas,.... Do you hve any?
Guys,
My ZUK Z2 Pro (bootloader unlocked) after finish loading the entire system (android) and appear the home screen, it reboots itself. When its boot it connected to PC, it does not reboot and after 5s I can remove cable and use it without problems. If the cable is in charge adapter, it also has the same problem.
Summary: I always need to turn on it connected in PC (with drivers installed) and wait 5s after finished loading all OS + startup APPs to not reboot alone. I install TWRP for good but no change to install custom ROM as it comes in loop after loading bootloader. Only ROMs that are stock, installed using QFIL works.
Do you have any idea?
Btw: I was using Mokee Rom without problems but after starting somes Frameworks apps te rom bricked out.
No 9008
Hello, i am new here and posted a reply in a different place. I think the wrong thread, so i will write here too.
I have a Zuk Z2 Pro. Unlocked bootloader, TWRP (twrp-3.2.1-0-z2_row.img) and installed several roms to try out. Then i read about a new ZUI and wanted to flash it. But, i made a mistake and now my phone is bricked. I read all about unbricking and flashing wit QFIL, but (and like others) my pc does not recognize my phone anymore. I can not work with adb (windows commands) and in QFIL i can not get the needed 9008 port. I installed all the needed stuff, but nothing.
Can someone help me out please. I already followed all the stept in some tutorials, but i get stuck with this 9008, which will not appear.
Phone does not start up. Recovery is gone, only menu with fastboot, recovery etc. is there. And the ZUI screen (from the rom i wanted to install) but the screen does not respond anymore, so i can not begin with setting the phone.
Is there a solution so i can flash with QFIL?
Or another solution?
Thanks,
Alex
Update 18-03-2018
This worked for me to get the needed 9008 port for flashing with QFIL:
- Open QFIL
- Phone must be off
- Connect usb cable to pc (not to phone yet)
- press volume up + power button and immediately connect usb cable to phone
- phone will vibrate 3 time (screen stays black/off)
- pc recognizes phone (there is this familiar sound of your pc)
- In QFIL you wil see port 9008
- just flash and wait till it's done
Off course you must have drivers etc installed on your pc, all the needed stuff for flashing. Don't forget to charge you phone.
I bricked my lenovo z2 plus, it is not booting to ROM or fastboot, it only vibrates after I hold the power button, and keeps vibrating every 10 sec, can anybody help me??
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
Hi, my wife gifted me that Chopin phone form China, after a wrong "flash and lock" global firmware now my phone is stuck on bootloader.
According to this thread:
Redmi Note 10 Pro 5G brick
Redmi Note 10 Pro 5G Chinese version with fastboot unlocked. After unsuccessful firmware. At startup, it goes into fastboot, you can load it into recovery. Wipe doesn't help. When trying to flash through fastboot MiFlashPro "FAILED (remote: 'not...
forum.xda-developers.com
I have all the files needed to setup sp flash and try to put again the Rom in the phone, which is now not unlocked and no usb debugging on.
Can someone please give me a tutorial on how to use those files? My phone still not recognised in sp flash com port, I don't know how to do.
If anyone will help me it will be so appreciated, thanks!
If you need to disable authorisation, did you run the MTK Auth Bypass tool and get the message "Protection disabled"? That's what I had to do before SP Flash Tool would flash the phone (without disconnecting it or rebooting), and I also had to set the baud rate to 921600, although that was all under Linux, and the phone was still unlocked.
it's complicated. with phone locked fastboot commands don't work. with my hold mi a3 fastboot flashing unlock command work. but with miui and mtk chipset probably it's useless. but u can try. if u boot into bootloader with mediatek driver the pc should recognize your phone also if it's blocked
1: Unzip this attached file into a folder. run it.
2: select the unlock bootloader and start, then connect you phone via usb with all three buttons pressed. (Phone must be off before connect, )
{
"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"
}
3: Your bootloader will be unlocked.
4: Close the program and re-start again, this time, select auth bypass and start, then repeat the phone connection. after at the bottom line, it show bypass ok.
from here you may flash again rom via Miflash or SPflash.
P.S: I think the file size is too big, I can not attach it here. Sorry! P.M me if you wish.
Thanks for the help, the problem I'm facing it's Auth tool cont recognise the phone, when I open the shell keep saying waiting for the device.
Driver are mtk with Libus installed, dunno.
When I restart the phone immediately have the logo then, if volume up I can log mi assistant or with volume down the bootloader screen.
Bonscia said:
Thanks for the help, the problem I'm facing it's Auth tool cont recognise the phone, when I open the shell keep saying waiting for the device.
Driver are mtk with Libus installed, dunno.
When I restart the phone immediately have the logo then, if volume up I can log mi assistant or with volume down the bootloader screen.
Click to expand...
Click to collapse
1. Check your device driver for USB, suggest you re-install the MTK usb driver.
2. First run the program, select the Auth by pass then press start.
3. Make sure phone is in "power off" state, press Vol+, Vol- and power (all three at the same time), and don't release it, plug in USB cable and wait.... Don't release these three buttons until it is Auth by pass OK.
During this process, take a look at device manager, there must be one item like portable device - USB ( Com 3). keep flashing.
sure u add reinstall mtk driver
Tried many drivers, always same result:
Driver says the device can't start. Tried to install lisbus too but no changes.
Bonscia said:
Tried many drivers, always same result:
View attachment 5499127
View attachment 5499129
Driver says the device can't start. Tried to install lisbus too but no changes.
Click to expand...
Click to collapse
you "must" remove (uninstall) the driver first then re-install the MTK usb driver again.
kirinin said:
you "must" remove (uninstall) the driver first then re-install the MTK usb driver again.
Click to expand...
Click to collapse
I did that many times, with win 10 no drivers signed mode, with many different mtk drivers but nothing was working. I'll try clean my windows and then start again with the drivers.
Bonscia said:
I did that many times, with win 10 no drivers signed mode, with many different mtk drivers but nothing was working. I'll try clean my windows and then start again with the drivers.
Click to expand...
Click to collapse
is a win10 problem that i also haved. hard to solve. u can try windows 7 via virtualbox (solved a lot of my problems in the past) or format and install a modded version of win10 (but i dont suggest this)
Virtual box looks no longer available, I'll install a fresh copy of win 7 in another partition, never give up lol
virtualbox is available for all system. i have a win7 virtualized under my linux pc, and miflash works fine. no bugs. if my tips makes you happy dont try. is not my problem, i didnt bricked my phone. i dont make things without know what i'm doing. good look. u can buy a new phone if u prefere
wetito said:
virtualbox is available for all system. i have a win7 virtualized under my linux pc, and miflash works fine. no bugs. if my tips makes you happy dont try. is not my problem, i didnt bricked my phone. i dont make things without know what i'm doing. good look. u can buy a new phone if u prefere
Click to expand...
Click to collapse
? I've just told you I've tried to download virtual box for win 10 but it's not avaible now or server was temporarily down for the download, so my only way it's to set up a fresh copy on win 7 on my pc, I can't understand your hanger answer.
kirinin said:
1: Unzip this attached file into a folder. run it.
2: select the unlock bootloader and start, then connect you phone via usb with all three buttons pressed. (Phone must be off before connect, )
View attachment 5498521
3: Your bootloader will be unlocked.
4: Close the program and re-start again, this time, select auth bypass and start, then repeat the phone connection. after at the bottom line, it show bypass ok.
View attachment 5498523
from here you may flash again rom via Miflash or SPflash.
P.S: I think the file size is too big, I can not attach it here. Sorry! P.M me if you wish.
Click to expand...
Click to collapse
Hi, can you share this Zip file with link drive or mega?
Thanks in advance
Which zip file? I have only this one
https://forum.xda-developers.com/attachments/mtk_bypass_final-rar.5444529/I
finally flashed the Rom with so flash but now the phone reboot in assistance mode sayings "NV data corrupted" I'm about to cry
Hi, I've followed your instructions, I've finally flashed the Rom into the phone, but now phone bootloop into recovery, it says "nvdata is corrupted", I've took the scatter file from the Rom folder, how to fix that problem now? Thanks.
Link with files is this, I've seen other link don't work
Redmi Note 10 Pro 5G brick
Redmi Note 10 Pro 5G Chinese version with fastboot unlocked. After unsuccessful firmware. At startup, it goes into fastboot, you can load it into recovery. Wipe doesn't help. When trying to flash through fastboot MiFlashPro "FAILED (remote: 'not...
forum.xda-developers.com
Download MTK Universal Tool V5 | MediaTek All in One Tool Latest Free
MTK Universal V5 Tool is a small MediaTek All in One Tool designed to disable user locks, bypass FRP, Auth Bypass, Format Data (user data format),
www.gadgetsdr.com
Bonscia said:
Hi, I've followed your instructions, I've finally flashed the Rom into the phone, but now phone bootloop into recovery, it says "nvdata is corrupted", I've took the scatter file from the Rom folder, how to fix that problem now? Thanks.
Click to expand...
Click to collapse
try wipe data. also u can control the active slot. try change it and reboot
Hi, finally I can install the Recovery V12.5.16.0.RKPCNXM rom and the engineering rom but have no baseband and no IMEI. Tried many times to put my IMEI codes with no luck, looks I need the mt6893 modem file to use sn writer but no way to find them on net, can someone share those files please? Thanks