Database Develop

[GUIDE] Unbrick Tool for OnePlus 5 with OOS 9.0.9 & OOS 9.0.11 (Untouched full stock)

[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?

HELP! I can boot into DOWNLOAD mode only, how to re-flash to oero?

STORY: My TA-1004 autoupdate to Android Pie on 22Dec after I turn off my phone to charge battery.
and I follow this " https://forum.xda-developers.com/nokia-8/development/android-9-0-pie-patched-boot-img-t3875977 " to try flash "fastboot flash boot "NB-01-551-b05-Magisk-TWRP" for flash TWRP and magisk to my TA-1004 pie. and I stuck on "nokia logo" after flash, someone said "Factory reset" , I try to use "wipe>format data" in TWRP, until now, I can boot in to download mode only.
I also try this "https://forum.xda-developers.com/nokia-8/how-to/guide-restore-nokia-to-stock-t3867646 "
to restore to oreo and stuck on "Next is greyed out, click on "Edit Phone Information", you will get an error message after a while, clik on OK, BUT Next is still greyed" . Can anyone help me please?

Please check that you have the correct fastboot drivers installed. Open Windows Device manager, and check the properties of your Fastboot device. Do you see HMD Global as the manufacturer? If not, the drivers may not be correct and you should install the Nokia drivers.

singhnsk said:
Please check that you have the correct fastboot drivers installed. Open Windows Device manager, and check the properties of your Fastboot device. Do you see HMD Global as the manufacturer? If not, the drivers may not be correct and you should install the Nokia drivers.
Click to expand...
Click to collapse
thx for reply first,
I can check "Fastboot Device" in Windows Device manager , HMD Global as the manufacturer.
I can check "fastboot devices" by adb/fastboot.exe

kelvin31 said:
thx for reply first,
I can check "Fastboot Device" in Windows Device manager , HMD Global as the manufacturer.
I can check "fastboot devices" by adb/fastboot.exe
Click to expand...
Click to collapse
It should work in that case. Give a try to the NOST tool shared in the Nokia 8 forums itself.

singhnsk said:
It should work in that case. Give a try to the NOST tool shared in the Nokia 8 forums itself.
Click to expand...
Click to collapse
NOST is it means Nokia OST (Online Service Tool) latest version and I need download android pie rom first?

kelvin31 said:
NOST is it means Nokia OST (Online Service Tool) latest version and I need download android pie rom first?
Click to expand...
Click to collapse
NOST" - short for "No Service Tool"
https://forum.xda-developers.com/no...t-improved-version-ost-la-6-0-4-v0-4-t3875574
You should use the existing NB0 which you have for the Nokia 8. I think it is on Oreo only. I hope you do have it.

singhnsk said:
It should work in that case. Give a try to the NOST tool shared in the Nokia 8 forums itself.
Click to expand...
Click to collapse
singhnsk said:
NOST" - short for "No Service Tool"
https://forum.xda-developers.com/no...t-improved-version-ost-la-6-0-4-v0-4-t3875574
You should use the existing NB0 which you have for the Nokia 8. I think it is on Oreo only. I hope you do have it.
Click to expand...
Click to collapse
THx
let me study it first,
thank you very much

singhnsk said:
NOST" - short for "No Service Tool"
https://forum.xda-developers.com/no...t-improved-version-ost-la-6-0-4-v0-4-t3875574
You should use the existing NB0 which you have for the Nokia 8. I think it is on Oreo only. I hope you do have it.
Click to expand...
Click to collapse
hello, I m stuck on unlock_critical, do you have any idea?
{
"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"
}

kelvin31 said:
hello, I m stuck on unlock_critical, do you have any idea?
Click to expand...
Click to collapse
You need to be flashing the actual unlock.bin file you used to unlock the Nokia 8. As you see in your CMD window, the command did not work out.
Make sure you're CMDing in the directory of your unlock file. Then send the command
Code:
fastboot flash unlock UnlockFile.bin
Remember to replace UnlockFile.bin with the name of actual unlock file in your PC.

singhnsk said:
You need to be flashing the actual unlock.bin file you used to unlock the Nokia 8. As you see in your CMD window, the command did not work out.
Make sure you're CMDing in the directory of your unlock file. Then send the command
Code:
fastboot flash unlock UnlockFile.bin
Remember to replace UnlockFile.bin with the name of actual unlock file in your PC.
Click to expand...
Click to collapse
unlock.bin is it provide by HMD that one?
I have receive my nokia 8 unlock bootloader file before by HMD,
name called unlock.key
is it this one? should I rename it to unlock.bin ?
thank you

kelvin31 said:
You need to be flashing the actual unlock.bin file you used to unlock the Nokia 8. As you see in your CMD window, the command did not work out.
Make sure you're CMDing in the directory of your unlock file. Then send the command
unlock.bin is it provide by HMD that one?
I have receive my nokia 8 unlock bootloader file before by HMD,
name called unlock.key
is it this one? should I rename it to unlock.bin ?
thank you
Click to expand...
Click to collapse
Yes, that's the one. You don't have to rename it. Just pass it the way you did earlier.
fastboot flash unlock unlock.key
When it gets accepted, then run:
fastboot flashing unlock_critical

singhnsk said:
Yes, that's the one. You don't have to rename it. Just pass it the way you did earlier.
fastboot flash unlock unlock.key
When it gets accepted, then run:
fastboot flashing unlock_critical
Click to expand...
Click to collapse
its work,
I need to flash unlock.key again even I unlocked my bootloader in september.
but I need flash again after auto update..
I also fastboot flashing unlock_critical, work too.
but got another problem.....
NOST tool error code: 0xa24b
ERROR= BATTERY_VOLTAGE_TOO_LOW_FAIL (0xA24B).
I can't charge or very very slow maybe.
I charge it over 1 hour still lower than NOST tool requirement(30%)...
my TA-1004 can not power off since first flash fail....
I keep saw "download mode" over light and I can't power off...
I did try volup + power, it turn off 2 sec and auto start again boot into download mode...
how can I force power off it?
thank you

kelvin31 said:
its work,
I need to flash unlock.key again even I unlocked my bootloader in september.
but I need flash again after auto update..
I also fastboot flashing unlock_critical, work too.
but got another problem.....
NOST tool error code: 0xa24b
ERROR= BATTERY_VOLTAGE_TOO_LOW_FAIL (0xA24B).
I can't charge or very very slow maybe.
I charge it over 1 hour still lower than NOST tool requirement(30%)...
my TA-1004 can not power off since first flash fail....
I keep saw "download mode" over light and I can't power off...
I did try volup + power, it turn off 2 sec and auto start again boot into download mode...
how can I force power off it?
thank you
Click to expand...
Click to collapse
You can power off the phone from the stock recovery or TWRP. That is, if you are able to boot into any of them. If you have the stock recovery file, then flash it to the phone. After that force reboot it and continue to hold the keys and it should go into recovery mode. The phone will essentially start faster in recovery mode. Or you can also choose the "Power off" option in recovery to power off the phone.
If you cannot get into recovery, then you cannot power it off. And in that case you will have to bear this slow charge only. Just plug it into a wall charger and leave it for a few hours. You can then check the battery capacity after connecting to the PC and sending the following command:
Code:
fastboot oem battery getcapacity
Start NOST and flash the phone if it is higher than the required

singhnsk said:
You can power off the phone from the stock recovery or TWRP. That is, if you are able to boot into any of them. If you have the stock recovery file, then flash it to the phone. After that force reboot it and continue to hold the keys and it should go into recovery mode. The phone will essentially start faster in recovery mode. Or you can also choose the "Power off" option in recovery to power off the phone.
If you cannot get into recovery, then you cannot power it off. And in that case you will have to bear this slow charge only. Just plug it into a wall charger and leave it for a few hours. You can then check the battery capacity after connecting to the PC and sending the following command:
Code:
fastboot oem battery getcapacity
Start NOST and flash the phone if it is higher than the required
Click to expand...
Click to collapse
THanks for help.
I charge it over 10 hrs, I did, I can flash NB1-488B Oreo 8.1 back, I can use my phone right now, thank you very much

[GUIDE] Unlock your LG V40 via 9008 mode (Every Variant except T-Mobile)

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

Question How to setup spflash for the soft bricked phone

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

Question [SOLVED] RN10 5G Hard-bricked after installing GSI

Hello fellas,
The other night I got frustrated over some bugs on MIUI 13 on my RN10 5G and decided to install MIUI 12.5. I did everything right and the FW downloaded from miuirom.com. It's EU, It's the correct, but it wouldn't boot.
Decided to flash PE, because I've used it and it was cool and all, but when it finished, I did the usual - Recovery-Wipe Data-Reboot.
Here's the problem - it took more than 15s on the Redmi boot screen (before it took less than 10s) and after that it restarted. OK, maybe something went wrong. After restarting it boots to a black screen, stays on it for about 3-5s and restarts again. Cool, it's in boot loop. But it doesn't display the boot screen, can't access recovery and holding for recovery immediately halts the phone and it turns off.
My question - other than getting a new phone, is there a way to... like, un-brick the phone?
Something a bit useful might be, that I've used a VNDKLite version of PE, and if I understood right, it partitions the phone in some weird way, to keep the vendor's data and the OS separately. Maybe this is causing it? I don't know.
P.S. If there is something with solidering, like changing the Flash Memory chip, I'm out...

Here are some steps you can take to try to fix your phone:
Try to enter recovery mode: Depending on your phone model, you can try to enter recovery mode by holding down a combination of buttons. Once in recovery mode, you may be able to reset your phone to factory settings, which can help fix the issue.
Contact the manufacturer: If your phone is still under warranty, contact the manufacturer for support. They may be able to provide a solution or offer a repair or replacement
Seek help from the developer community: If you installed PixelExperience through a custom ROM, try seeking help from the developer community on forums or social media. They may have experience with similar issues and be able to provide assistance.
Consider professional repair: If none of the above options work, you may need to take your phone to a professional repair service. They may be able to diagnose and fix the issue, but be aware that this can be expensive.
In any case, it's important to be cautious when installing custom ROMs on your phone, as they can potentially cause issues if not installed correctly. Make sure to research thoroughly and follow instructions carefully to minimize the risk of bricking your phone.

@timjohnson2584 Thanks for the help! That's also a quick update.
So, the first one, I literally cant enter recovery nor fastboot. Acidentally I've entered a secret menu, that gave me the option between Recovery, Fastboot and normal. VolUp to change choice and VolDown for confirm. I wasn't able to access it again, but it doesn't matter, because when I was in it, i chose fastboot and it restarted into the same boot loop. Second - the phone is unlocked, re-flashed with, i dont even know what anymore, and I've disassemble it to change the screen, so the warranty is no no. The 3rd - nothing personal, but "...that's why I'm here". Fourth - I don't really have the finances for a technician and just want to repair it @ home, sooo...
Thanks anyways

Again, a quick update!
I found out that the menu i have accessed may have been the weirdass BROM menu, because after some search I've found out how to enter it. When the screen lights up, hold PWR and VolUp, till the screen turns off, and then immediately hold VolUp and VolDown. When screen lights up, no matter what it enters the mode. Sadly, just hanging there doesn't give me access trough adb nor fastboot and if i choose fastboot it restarts. But if it's normal or recovery, it vibrates, freezes, disappear and halts.

Hey guys, another quick update that might frustrate some people. I've left it for the night to boot-loop reboot and stuff and today when I tried powering it up, it wouldn't show signs of life. When connected to this PC, from which I'm sending this, and hold any combination of buttons, it shows in the Comp Mgmt for a brief second as COM3 Serial Port. That's cool, at least its recognizing it, but if before there was at least backlight on the screen, this time it's fully blank - no picture, no backlight, no sh*t. If someone asks, the weirdass way Xiaomi did it is the phone's daughterboard for charging is connected to the screen, AND THEN it all connects to the mainboard. If it chargin', then it ain't disconnected - that's how I look at the situation. :/
P.S. Also, I don't think it's a problem, but I've disconnected the speaker and vibrator motor, so I can sleep peacefully.

someone here has had a similiar issue with you but differently recovered without using brom
anyways, i took a glance at your issue, seems like you are still in brom right?
install MiFlashPro, you will need it to fill the Download-Agent in sp tool (see what the spaces means below)
then, download any miui rom from any website (my favorite is mifirm.net, it downloads faster)
extract the rom folder. now open sp tool.
now you will need to fill out 3 spaces:
download-agent (DA for short), scatter-loading file & authentication file.
DA is to have access to the devices internal storage, scatter-loading shows you the mapping of the partitions it will flash on the mtk & authentication is just MTK protection for newer mtk devices that you need to be able to flash (its also used to successfully flash, but you still need to bypass it somehow, as you require a Mi Account able to do BROM flashing, see below as you follow the thread)
to find the DA, it is always in the MiFlashPro installation location, so ...\MiFlashPro\. Access that folder, open up "\SP_Flash_Tool_V5" folder, and you will find a file named "MTK_AllInOne_DA.bin", use it as the DA.
to find the authentication file, its located in the same path of the DA, so ...\MiFlashPro\SP_Flash_Tool_V5\, and you will find a file named "auth_sv5.auth", use it as the authentication file.
finally, to find the scatter-loading file, it is in the rom folder you extracted, so ...\camellian_xx_xxxx_images_VXX.X.X.X.xxxxx_XXXXXXXX.XXXX.XX_XX.X_xxxxxl\ (the X's represent your MIUI version you downloaded). the scatter-loading file is always located in the folder "images", so \camellian...\images\, and you will find a text file named "MT6833_Android_scatter.txt", use it as the scatter-loading file.
Now, you need to edit the "MT6833_Android_scatter.txt", or else when you use to flash you will get this error:
{
"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"
}
Open it (located at your MIUI ROM folder at \images), then use the locate tool to find "combo_partsize_check: true". You will probably find a few lines set as true, just replace every one with false (if it doesnt find it, just put "combo_partsize_check", but you will waste more time finding those that are set to true)
Alright, we finished our sp tool settings. now we have to bypass MTK Auth protection.
(Dont close sp tool yet!)
Ive annexed the tool below (mtkauthbypass.zip), download it and extract it.
It looks like this:
After you are ready, press the "Disable Auth" button, get your hands on the phone and press at the same time the VOL+, VOL- & POWER button, till you see prompts appearing in the blank (i dont have a screenshot to show how it looks like, sorry)
After it is finished and was successful, now go back to sp tool, and click "Download" asap.
Now wait for it to flash, maybe 5-15 minutes, and some time to boot, and done, your phone is alive again.
if anything didnt work post about it asap so i can help
(ps: if you get this, its a easy procedure to repair your bricked mtk, and you will get used to it quickly)

OK, thanks, I'll try that. But just to ask, do I have to stay in this BROM mode with options on blank screen while doing this, or select fastboot, recovery, normal first?

bg0169 said:
OK, thanks, I'll try that. But just to ask, do I have to stay in this BROM mode with options on blank screen while doing this, or select fastboot, recovery, normal first?
Click to expand...
Click to collapse
well, not necessarily. only when you get to the bypassing, because brom will automatically restart if theres no command taken in a few seconds

OK, now I have a problem. All my programs are ready, the phone is in BROM mode, but the PC is not recognizing it. It's not from the cable and it doesn't appear in Device Manager.

bg0169 said:
OK, now I have a problem. All my programs are ready, the phone is in BROM mode, but the PC is not recognizing it. It's not from the cable and it doesn't appear in Device Manager.
Click to expand...
Click to collapse
Wait a few moments, i think i have the mtk brom drivers for it, sorry for the wait

No problem, have your time

bg0169 said:
No problem, have your time
Click to expand...
Click to collapse
There you go its attached, try them. Should work

OK, update again, again, again... Now I even have a picture on my phone in BROM mode and what's happening even with the drivers from above:
Down there is the phone and on the screen is SP flash ready in the background and the MTK bypass tool. Also, PLEASE don't question the webcam, I know

Also here is what the Dev Mgmt sees. It's not showing even as serial port (the COM3 port from which it showed during the bootloop)

bg0169 said:
OK, update again, again, again... Now I even have a picture on my phone in BROM mode and what's happening even with the drivers from above:
View attachment 5860261
Down there is the phone and on the screen is SP flash ready in the background and the MTK bypass tool. Also, PLEASE don't question the webcam, I know
Click to expand...
Click to collapse
BROM mode is not that!
BROM is accessed by pressing down VOL+, VOL- & POWER all at the same time when device is turned off or rebooting, while connecting it to the pc, and BROM does not display anything, not even the LCD lights up, you just got to know whenever it is in BROM by your computer
Let the device reboot (select any mode from the list), and right as it reboots, press down all of the buttons, and connect the phone simultaneously.

OK, so when I plug the phone into my laptop and start holding all the buttons for eternity, it just connects and disconnects in 1sec.
I managed to capture it while doing it and:
, yeeaaahhhh, no,
I think it's entering BROM mode from what you've said, but that's what is happening. It recognizes it, but doesn't stay in. If i let go on the buttons, the phone just starts restarting again.

bg0169 said:
OK, so when I plug the phone into my laptop and start holding all the buttons for eternity, it just connects and disconnects in 1sec.
I managed to capture it while doing it and:
View attachment 5860273, yeeaaahhhh, no,
I think it's entering BROM mode from what you've said, but that's what is happening. It recognizes it, but doesn't stay in. If i let go on the buttons, the phone just starts restarting again.
Click to expand...
Click to collapse
press the "disable auth" button, and then connect it into BROM again, then it will bypass normally
it restarts because its not receiving any command, its normal

OK, I'll try it out in a moment... Thanks!

OK, even if u want, I have a screen capture. I open the tool, click bypass, connect the phone, and hold all the buttons. BUUUT it just keeps connecting and disconnecting. Always! Even with the drivers! Restarted my PC, same s**t! Now I'm pissed off a lot! Are you sure this is the only way, am I doing something wrong? I saw your "How to Guide" thread and followed everything and it's the same.

bg0169 said:
OK, even if u want, I have a screen capture. I open the tool, click bypass, connect the phone, and hold all the buttons. BUUUT it just keeps connecting and disconnecting. Always! Even with the drivers! Restarted my PC, same s**t! Now I'm pissed off a lot! Are you sure this is the only way, am I doing something wrong? I saw your "How to Guide" thread and followed everything and it's the same.
Click to expand...
Click to collapse
i see the problem
its the driver. well, not exactly the driver
it seems like its a issue from the phone's side. but its normal! it also happens to me every time i try to bypass it
bg0169 said:
OK, so when I plug the phone into my laptop and start holding all the buttons for eternity, it just connects and disconnects in 1sec.
I managed to capture it while doing it and:
View attachment 5860273, yeeaaahhhh, no,
I think it's entering BROM mode from what you've said, but that's what is happening. It recognizes it, but doesn't stay in. If i let go on the buttons, the phone just starts restarting again.
Click to expand...
Click to collapse
just like you show here, the port is not working (error symbol), so clearly it cant detect the phone to be able to do any commands
i tried bypassing to see just now, and yes, it also shows the same problem as you, the error symbol, however if you have the patience to retry lots of times, trying to bypass it, then its the solution for it.
what you can try is just keep bypassing lots of times till you get it.. thats it, i hope