Database Info

How to: universally manually update all LG leon varients

This Guide as the title suggest is universal & how we will be "manually" upgrading our LG leon OS from 5.0.x to 5.1.x is by flashing a kdz file.
YES, it's very simple & easy to do. I created a step by step guide written & also pictures will be available as well.
This guide is NOT just about upgrading as it can also be used to fix your bootloop/brick lg leon if need be. But if you flash a kdz file with a newer firmware it MAY or NOT be able to flash it back to its earlier version, BUT I haven't tested that theory out yet.
The reason why I'm making this guide is because to make a "one stop shop" & also to keep other threads free of cluttered up messages that probably are outdated now from my other crappy guide that I posted on such threads.
WARNINGS
I'm NOT responsible in ANY way if you brick, break, slap, crap, toss, or any damages to your LG leon device
By using this guide your lg leon WILL be reseted so you WILL lose your data so back it up before you try this method
REQUIREMENTS
A WINDOWS COMPUTER RUNNING WINDOWS 7, 8, OR 10
(PICTURES WILL SHOW A WINDOWS 10 PC)
TOOLS IN FIRST STEP
__________________________________________________________________________________________________
STEP 1: PLEASE DOWNLOAD & INSTALL THE FOLLOWING PROGRAMS & kdz file​
LG United Mobile Driver 3.14.1
LG Flash tool 2014 (build 03/07/2014)
PLEASE MAKE SURE TO DOWNLOAD THE CORRECT KDZ FILE FOR YOUR DEVICE
LG Leon variants kdz list
LG Leon 4g LTE Variants kdz list
STEP 2: After the tools are installed​
1. Remove the battery and put it back in.
2. Hold the Volume Up button (ONLY) while connecting to USB Cable
3. The Volume up button needs to be held until it reaches download mode
4. Open device manager and changed the LGE Mobile USB Serial port to COM 20
by right clicking on LGE mobile & select properties
click the tab named port settings & click advance
there is a drop down box called com port number....select com 20
{
"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 3: FLASHING IN DOWNLOAD MODE!​
1. Open the Flash Tool
2. Select Type: 3GQCT
3. PhoneMode: EMERGENCY
4. SELECT THE KDZ FILE THAT YOU DOWNLOADED
5. Click on Normal Flash
6. Click on Clear update registry
7. Country: different country
8. PLEASE CHOOSE YOUR LANGUAGE
9. Click okay and wait for the LG Mobile Support tool to recognize the device. It takes a minute or two but the tool will recognize it. The software starts the extraction and re-boots at %100. You can remove USB cable ONCE ITS RESTARTS & your device will boot normally, and the device is no longer stuck in a boot loop.
ALSO it has happen to me too often that the program WILL freeze & ask to be close
DON'T CLOSE IT OR STOP ITS PROCESS IN THE TASK MANAGER & IF YOU DO IT YOU WILL END UP WITH A LOVELY NEW PAPER WEIGHT!!!!
SIDE NOTE:
Please double check the kdz file that you are downloading from the firmware software version in about phone(software info) as the two will NEED to be different in order for you to upgrade your LG leon.

Hello! I have a 340n variant
In download section under most download there's a open Europe fw , is there a 5.1 or 5.0? There's no information about fw version. Thanks and sorry for my bad English
Inviato dal mio LG-D620 utilizzando Tapatalk

maxnta2 said:
Hello! I have a 340n variant
In download section under most download there's a open Europe fw , is there a 5.1 or 5.0? There's no information about fw version. Thanks and sorry for my bad English
Inviato dal mio LG-D620 utilizzando Tapatalk
Click to expand...
Click to collapse
Please double check the kdz file that you are downloading from the firmware software version in about phone(software info) as the two will NEED to be different in order for you to upgrade your LG leon....if the firmware is higher than "probably" it will be upgraded to 5.1 or 5.1.1 depending if a new kdz file was ever made for your device.

And here is the problem for me. IT WON'T GO INTO ******* DOWNLOAD MODE!!! IT SAYS SOMETHING LIKE BOOT SERTIFICATION ERROR! SO TO TAKE IT ALL IN, NO RECOVERY, NO FACTORY RESET, NO DOWNLOAD MODE, NO NOTHING!. sigh...... what should i do when i can't even flash a new kdz......

Megas18 said:
And here is the problem for me. IT WON'T GO INTO ******* DOWNLOAD MODE!!! IT SAYS SOMETHING LIKE BOOT SERTIFICATION ERROR! SO TO TAKE IT ALL IN, NO RECOVERY, NO FACTORY RESET, NO DOWNLOAD MODE, NO NOTHING!. sigh...... what should i do when i can't even flash a new kdz......
Click to expand...
Click to collapse
This is very late...I am sorry, but I dont received any notifications for my threads at all....
so were you able to boot into download mode before or you do not know how to?

i need help i run the tool and when it gets to upgrading the phone i get kicked out with error contact system admin i so lost i need my phone but every thing i try wont work its seams to have lost recovery

juggalodrew said:
i need help i run the tool and when it gets to upgrading the phone i get kicked out with error contact system admin i so lost i need my phone but every thing i try wont work its seams to have lost recovery
Click to expand...
Click to collapse
First tell which LG device you are using...so I can clarify specific steps
secondly...what are you trying to achieve in terms of using this guide: ie restoring to factory reset, down/up/grade?/etc/
thirdly....did you install a custom recovery or unlocked the bootloader?
fourth...did you follow the guide to the letter?
_____
Are you not able boot into recovery/download mode & which specific errors do you receive?

phone lgk7 no recovery download mode and it starts upgrading device then stops and tells me to contact system admin so i rooted with kingoroot then went to google play installed supersu updated the binary it ask to reboot so i did then the phone got stuck on the metro pcs screen wont boot also i used adb-fastboot to unlock bootloader i cant get stock recovery its like its not there i can get download mode but like i said it goes from downloading after checking windows to upgrading device for about a second then tells me to contact system admin

okay, i went through the same scenario too.
juggalodrew said:
phone lgk7 no recovery download mode and it starts upgrading device then stops and tells me to contact system admin so i rooted with kingoroot then went to google play installed supersu updated the binary it ask to reboot so i did then the phone got stuck on the metro pcs screen wont boot also i used adb-fastboot to unlock bootloader i cant get stock recovery its like its not there i can get download mode but like i said it goes from downloading after checking windows to upgrading device for about a second then tells me to contact system admin
Click to expand...
Click to collapse
0. I subscribed to my thread & you should too!
1. I need your PC info as the following steps requires a PC running windows 7/10(preferably 10)
2. download the following files:
LG Drivers
lgms330(K7/tribute 5 variant) kdz firmware
lg flash tool newer versions may/not work
LG mobile support tool
install all downloaded programs.
step 3. follow the tutorial completely & remember to Hold the Volume Up button (ONLY) while connecting to USB Cable
step 4. profit.

Xstar410 said:
0. I subscribed to my thread & you should too!
1. I need your PC info as the following steps requires a PC running windows 7/10(preferably 10)
2. download the following files:
LG Drivers
lgms330(K7/tribute 5 variant) kdz firmware
lg flash tool newer versions may/not work
LG mobile support tool
install all downloaded programs.
step 3. follow the tutorial completely & remember to Hold the Volume Up button (ONLY) while connecting to USB Cable
step 4. profit.
Click to expand...
Click to collapse
How come it says to contact system admin? I have done everything asked.

Hard bricked my OnePlus One by just rebooting it, help! [5$ REWARD]

I will be straightforward:
I bought an used OPO, I booted it up, configured the phone, took a photo and then decided to reboot it (turn off and then turn on), then my device simply hard bricked.
1. I already tried turning it on, the device does nothing (no vibration).
2. I already tried using Power + Vol Up and Power + Vol Down, nothing happens (no vibration).
3. Windows recognizes the device as "QHSUSB_BULK", I already tried installing the drivers and using ColorOS flashing tool from here http://forum.xda-developers.com/oneplus-one/general/guide-unbrick-oneplus-one-t3013732 , the device IS RECOGNIZED by the tool, but when I start flashing, it starts a loop when trying to flash the "8974_msimage.mbn" file (the progress bar goes until the end and then the process repeat in the same file).
Yes, the device has the bootloader unlocked, because the previous owner flashed a custom ROM, custom kernel and SuperSU.
No, the device isn't recognized by adb.
No, the device isn't recognized by fastboot.
I already tried searching on Google for this issue, everyone who had this issue never replied saying that they fixed the issue...
I never had any kind of soft/hard brick on my Moto G 2014 (and I flashed custom ROMs constantly on it)... so... can someone help me? Thanks!
I'm also willing to give 5$ on PayPal to someone who can fix this issue.

Also, if I try to use the ColorOS flashing tool, the device disconnects in the middle of the process, causing the infinite flash loop.

First, if you have a computer which installed Windows XP, just flash the ROM with COLOROS tool.
Second,if you a using Windows7 or later,,give me a photo of what the COLOROS tool showed.
Thanks for forgiving my poor English

sino1641 said:
First, if you have a computer which installed Windows XP, just flash the ROM with COLOROS tool.
Second,if you a using Windows7 or later,,give me a photo of what the COLOROS tool showed.
Thanks for forgiving my poor English
Click to expand...
Click to collapse
Nah, your english is fine, I could understand what you are saying.
{
"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"
}
After I clicked "Start"
Then the "device plugged in" sound plays and the process repeats...
It keeps doing this:
(If you can't view the images, click here:
http://lori.mrpowergamerbr.com/sharex/Msm8974DownloadTool_2016-07-22_10-39-42.png
http://lori.mrpowergamerbr.com/sharex/Msm8974DownloadTool_2016-07-22_10-40-18.png
http://lori.mrpowergamerbr.com/sharex/2016-07-22_10-41-05.gif
)

Morning,my friend.
I tried to brick my OPO for testing.
Here's the solution.
First,open Device Manager and checked this(dont know how to speak in English):
Second, open COLOROS tool,click start and it will show the situation like what happened to you.
NOW,check Device Manager again.
Has three ways.
1.shows 9006 and MMC storage.COLOROS tool wil continue later.
2.shows QHSUSB_BULK with a yellow ! before,means no driver.
3.shows unknown device,means not enough elec.
You should be the second way.
Third,Disable Signed Driver Enforcement in Windows 7 or later.
My laptop company's suggestion:
http://acer.custhelp.com/app/answer...windows-10:-disable-signed-driver-enforcement
After that, reinstall the bricked driver and everything will be in way 1.
At last,wait for the imgs downloading,unplug microUSB,press power and reboot twice,then you can unlock bootloader and do what you want.

sino1641 said:
Morning,my friend.
I tried to brick my OPO for testing.
Here's the solution.
First,open Device Manager and checked this(dont know how to speak in English):
Second, open COLOROS tool,click start and it will show the situation like what happened to you.
NOW,check Device Manager again.
Has three ways.
1.shows 9006 and MMC storage.COLOROS tool wil continue later.
2.shows QHSUSB_BULK with a yellow ! before,means no driver.
3.shows unknown device,means not enough elec.
You should be the second way.
Third,Disable Signed Driver Enforcement in Windows 7 or later.
My laptop company's suggestion:
http://acer.custhelp.com/app/answer...windows-10:-disable-signed-driver-enforcement
After that, reinstall the bricked driver and everything will be in way 1.
At last,wait for the imgs downloading,unplug microUSB,press power and reboot twice,then you can unlock bootloader and do what you want.
Click to expand...
Click to collapse
Thanks for replying!
Sadly, your suggestion didn't work, I plugged in the OPO, opened Msm8974DownloadTool.exe and clicked "Start", closed drivers manager and reopened it and nothing changed (It was like your first screenshot)
EDIT: And yes, I'm on Test Mode + Allow Unsigned Drivers

MrPowerGamerBR said:
Thanks for replying!
Sadly, your suggestion didn't work, I plugged in the OPO, opened Msm8974DownloadTool.exe and clicked "Start", closed drivers manager and reopened it and nothing changed (It was like your first screenshot)
EDIT: And yes, I'm on Test Mode + Allow Unsigned Drivers
Click to expand...
Click to collapse
Open Device Manager.
Press Power &Vol Up for about 10 seconds.
See if it will change between 9008 and 9006.

I have same thing did it work
I am just wondering if u managed to fix it.

I had the exact same issue. To stop the device from disconnecting, I needed to remove all existing drivers, let the phone charge, plug it into the PC. Hold volume up + power until the PC recognises it. Then I used the color OS flashing tool.
I had to run it as administrator, and it worked fine on Windows 10, without anything extra. However remember you'll lose all your stuff. Lucky for me I had a backup of my entire phone on my PC when I switched file system to F2FS.
This issue in itself has really baffled me. It happened to me when flashing sultans rom, and the phone completely bricked. However I'm using the rom now after fully recovering the device... I guess it's just down to bad luck?

mark1320 said:
I am just wondering if u managed to fix it.
Click to expand...
Click to collapse
Nope, never fixed it, I don't even have the device anymore (now rocking a Moto G Turbo)

mark1320 said:
I am just wondering if u managed to fix it.
Click to expand...
Click to collapse
Don't use "msm8974-download-manager" use qfil to recover the phone. Worked for me.
http://www.androidbrick.com/ultimate-qualcomm-snapdragon-unbrick-guide-snapdragons-are-unbrickable-qhsusb_dload_qpst_qfil/

Download 2012 qhs diagnostic driver and use xp machine.It will work just fine.

install a fresh windows either x32/x64 winxp/win 7 extract color OS and install the correct drivers

Nokia 1.4 TA-1322 Help

Hello everyone, I need some help.
On november 2021 I purchased Nokia 1.4 and that day when alarm was ringing my phone screen frozen/stopped. Screen sensor and the buttons stopped was not responding. I googled immediately and found the way to turn off forzen Nokia 1.4 by pressing Wolume up + Power off buttons same time (Source: https://www.nokia.com/phones/en_int...-reboot-my-smartphone-when-its-not-responding ).
When my phone turned on again I was happy till the next restarting of my phone. My nokia get Stucked in a Reboot Loop.
Screen lights and when Android GO Logo appears it turns off again and again.
I tried to flash my phone using QFIL Tool but there was unsolved issue of Android ADB Interface driver. The QFIL Tool couldn't detected my device. Mybe it needed different keys combination when connectiong it to PC to boot.
QFIL Tool source: https://androidmtk.com/download-qualcomm-flash-image-loader-qfil
Than I unlocked bootloader using this command:
Code:
fastboot oem unlock-go
I thought it was boot or recovery fail and by the reason I downloaded the firmware from alien9firmware
Source: https://alien9firmware.com/index.php?a=downloads&b=file&id=1325
Because QFIL Tool did not work I flashed boot and recovery via ADB. I moved these two .img files to disk C and ran the following commands
Code:
fastboot devices
fastboot reboot bootloader
fastboot flash recovery c:\recovery.img
fastboot flash boot c:\boot.img
fastboot reboot bootloader
fastboot erase cache
fastboot reboot
Disconnect device
You guess what do you think guys happen
My nokia was still stucked in reboot Loop.
Than I googled smartphones with same Core Qualcome QM 215 and downloaded Nokia 8 and Nokia 6.2 TWRPs from twrp official website.
Source: https://twrp.me/Devices/Nokia/
ADB thrown me an error when I tried to flash Nokia 8 TWRP. "The file is too large and blablabla..."
Then I tried to flashed twrp-3.6.0_9-0-SLD_sprout(nokia6.2) with no errors.
I have never seen anything like that. When I press to "Power button + Volume down" buttons my phone shows the stock recovery again which has no matter.
Then I gooled so many times I and I made a decision that every smartphone with Qualcomm QM215 core has absolutely same bugs.
There are smartphones with this terrible Processor:
Smartphones with Qualcomm Snapdragon 215 processor
List of smartphones that works with Qualcomm Snapdragon 215 processor inside.
www.kimovil.com
Than I found this video. In this video he used dryer and it worked. Unfortunately I have not dryer and... It may works on our devices too, Who knows...
Than someone told me to use MiFlash tool to boot my device. I faced another problem the firmware backup was missing the boot_lock.bat file. I had to download Xiaomi Kenzo global firmware to copy and modify the .bat files to my firmware backup. That trying became my night mare. I accidently erased Bootloader.
Today I was searching how connect How to a connect phone with erased bootloader to pc and I found this:
[guide] repair hard bricked devices with deleted bootloader (sboot)
I'm writing this in android development section because this is only section for both models, i hope this is not a problem. Also i want to say thanks to sataccount from gsmhosting, he found working map at the end. This guide is for hard bricked...
forum.xda-developers.com
Than I connected my phone to pc via usb and opened Device manager. There appeared QHSUSB_BULK device missing driver.
Then I found the driver here: https://fixfirmware.com/qhsusb-bulk-driver/
At least I managed to connect my device to pc again. And now QFIL Tool detects my phone.
Problems never ends. I downloaded 5 firmwares from different websites and the emmc filefouse prog_emmc_firehose *** ddr.mbn and Rawprogram .xml files missing in all of them.
Do someone know where can I fount the emmc Firehose and Rawprogram .xml files?

Oleg69 said:
Problems never ends. I downloaded 5 firmwares from different websites and the emmc filefouse prog_emmc_firehose *** ddr.mbn and Rawprogram .xml files missing in all of them.
Do someone know where can I fount the emmc Firehose and Rawprogram .xml files?
Click to expand...
Click to collapse
Try it

optimusodd said:
Try it
Click to expand...
Click to collapse
I have downloaded the firmware but there is not prog_emmc_firehose.mbn in the archive
{
"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"
}

Oleg69 said:
On november 2021 I purchased Nokia 1.4 and that day when alarm was ringing my phone screen frozen/stopped. Screen sensor and the buttons stopped was not responding. I googled immediately and found the way to turn off forzen Nokia 1.4 by pressing Wolume up + Power off buttons same time
Click to expand...
Click to collapse
When it's still under warranty ,why didn't you claim it ?

optimusodd said:
When it's still under warranty ,why didn't you claim it ?
Click to expand...
Click to collapse
It was gifted to me from abroad. You know...

S
Oleg69 said:
It was gifted to me from abroad. You know...O
Click to expand...
Click to collapse
So what was your end result because I'm currently in bootloop with an unlocked bootloader as well but not having much luck with many of the same avenues you spoke of.. anyone?

Absolutely no luck, you gotta take your phone to the service center or buy a new one as I did (another brand)

Absolutely not.. I refuse. If it's an android, there's a way. Thank God this is simply one of 8 phones I've currently got

Does unlocking the bootloader of this device put the device in boot loop. I want to unlock the bootloader coz I want to install custom ROM. Anyone tell me how to unlock the bootloader of this device without putting the device in boot loop.

[REQ] Unihertz Titan Stuck in Bootloop

Okay here's where all this started https://www.facebook.com/groups/130...61465&ref=notif&notif_t=group_comment_mention
Windows and Android Drivers are always a bothersome attempt at trying to get to work properly. Always with a hiccup.
I formated a new laptop with Windows 7 64 Bit Sp1
It still acts as though I don't have a bootloader, recovery menu or chinese mediatek diagnostics menu.
Phone is just constantly looping off and on, in SP Flash Tool it'll timeout. I let the battery drain yesterday and did get a full battery and the green circle.
Me and Nomi (the developer of the rom) tried everything yesterday and he even said he hasn't seen anything like it before, but had driver issues before too.
I'd believe it's still got USB Debugging and looks to still be OEM Bootloader Unlocked as I have the text on the bootscreen.
Just trying to think of anything else I can do, as unihertz hasn't answered my email since yesterday afternoon at 2.
But this seems to be a common problem as you'll see in this reddit:
https://www.reddit.com/r/UnihertzTitan/comments/i33me3
Help the poor UniHurtz TitanFALL!

DorkyDev said:
Okay here's where all this started https://www.facebook.com/groups/130...61465&ref=notif&notif_t=group_comment_mention
Windows and Android Drivers are always a bothersome attempt at trying to get to work properly. Always with a hiccup.
I formated a new laptop with Windows 7 64 Bit Sp1
It still acts as though I don't have a bootloader, recovery menu or chinese mediatek diagnostics menu.
Phone is just constantly looping off and on, in SP Flash Tool it'll timeout. I let the battery drain yesterday and did get a full battery and the green circle.
Me and Nomi (the developer of the rom) tried everything yesterday and he even said he hasn't seen anything like it before, but had driver issues before too.
I'd believe it's still got USB Debugging and looks to still be OEM Bootloader Unlocked as I have the text on the bootscreen.
Just trying to think of anything else I can do, as unihertz hasn't answered my email since yesterday afternoon at 2.
But this seems to be a common problem as you'll see in this reddit:
https://www.reddit.com/r/UnihertzTitan/comments/i33me3
Help the poor UniHurtz TitanFALL!
Click to expand...
Click to collapse
Are you needing help or you solved the bootloop?

I'll find out when I get home from work this morning Unihertz did finally reply to my email at 3am
I'm going to try in both Ubuntu and Windows as they have me tute's and files for both.
On that and the windows note can anyone recommend which driver version works best doesn't matter if it's 7 or 10, so long as it's 64Bit supported.

DorkyDev said:
I'll find out when I get home from work this morning Unihertz did finally reply to my email at 3am
I'm going to try in both Ubuntu and Windows as they have me tute's and files for both.
On that and the windows note can anyone recommend which driver version works best doesn't matter if it's 7 or 10, so long as it's 64Bit supported.
Click to expand...
Click to collapse
platform-tools-latest | drivers USB OEM | MTK USB driver
Obviusly you only need flash stock recovery.img as your device has A9.
For Custom Recovery like TWRP maybe I can ask my friend to help you. If - you still TWRP want?!

Where's the link for that I'll try and see as even with a reply from Unihertz and new files I'm still running into the same error. Where constant looping and when plugged in attempting to flash the factory firmware it times out with a red Download DA bar loading at 100% in seconds and then two minutes later timing out and giving me error code 0xXC0010005.
RN I don't think it'd be possible to get it to stay in bootloader or on long enough to fully do the ADB or Powershell twrp.img flash, interestingly enough I did find MTK Droid Tools v2.5.3B has a rewrite boot and recovery option and askes for the img before proceeding and I didn't do anything else after that though cause it wants a .prm as for a scatter file. Oh and it has ADB builtin to the program.
{
"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"
}

DorkyDev said:
Where's the link for that I'll try and see as even with a reply from Unihertz and new files I'm still running into the same error. Where constant looping and when plugged in attempting to flash the factory firmware it times out with a red Download DA bar loading at 100% in seconds and then two minutes later timing out and giving me error code 0xXC0010005.
RN I don't think it'd be possible to get it to stay in bootloader or on long enough to fully do the ADB or Powershell twrp.img flash, interestingly enough I did find MTK Droid Tools v2.5.3B has a rewrite boot and recovery option and askes for the img before proceeding and I didn't do anything else after that though cause it wants a .prm as for a scatter file. Oh and it has ADB builtin to the program.View attachment 5518101
Click to expand...
Click to collapse
Search in the internet How install MTK drivers, specially in the Win7. Better in Win10 and if you as that so the drivers [link] is much better, You can try installing that file but need reboot your computer. After try flash with SPFT.
Don't choose FORMAT+ALL or any option with FORMAT+........
Win7 need more effort to start drivers for Mediatek devices!
You can try pressing constantly the VOL - button when put USB for SPFT work.

The issue I keep running into here is no matter how charged the battery is, it won't stay power up long enough to even attempt to correctly install the drivers. (I think at least, still don't ever see a unknown device in other devices), if I could get that far I'd probably stand a chance of recovering it.

DorkyDev said:
The issue I keep running into here is no matter how charged the battery is, it won't stay power up long enough to even attempt to correctly install the drivers. (I think at least, still don't ever see a unknown device in other devices), if I could get that far I'd probably stand a chance of recovering it.
Click to expand...
Click to collapse
We often don't realize that certain errors are normal on our machine. So the question is to test in others computers.
But there are possibilities of company blocks or even something that has happened on the phone without it really should happen.
Some interesting cases:
1- I noticed with the image you showed about trying to flash all the firmware.
** So even if you have tried the Download only or Firmware Upgrade options, the question remains if you tried to flash only the recovery.img file? Obviously you can have the same error in SPFT?!
2- Cases of hardware vs software that match the use and characteristics found such as restarting the PC and trying to flash in a different USB port. Same problem?!: Drivers are resolved?!
The biggest case of suggesting something or thinking that this or that is a problem wastes precious time. Confirm the main steps!:
1- Driver correctly installed and working;
2- Driver works: Different USB PORT tested;
3- SPFT version must be tested. Mainly previous versions to confirm the error message that persists or may disappear;
4- Phone particularities: pressing the VOL buttons for a while can trigger the preloader that is responsible for the connection between the SPFT and your phone on the computer. Switching to VOL+ or Power or VOL- with VOL+ or VOL+ VOL - and Power may solve or confirm the non-solution.
Best way: Win10 with driver updates. Find the way to disable unsigned driver installations. But you can use this driver and you must restart your computer for it to take effect.
Make sure the USB port has a speed feature for the flashing process. Example: All USB ports are 2.0 only and SPFT asks for a USB 3.0 port to make the connection.
With everything confirmed the rest is something to question in relation to having the correct firmware file or the device itself having blocked the installation process due to a drastic change in the preloader or something that has changed and is blocking it.
Look previous posts about that so all depends on what you have and how you use it.
Unfortunately everyone (including me) who went through bad times like the one you have now, has a headache because it's a simple process and doesn't know what to do. But on the other hand, it's a huge learning experience when we solve it.
But there is still a choice without a headache: take it to a technical assistance and pay for it!

No on drivers when it goes to do the typical windows installation with the installation boxes in the upper left corner, I keep getting red x's.
I'm letting it charge some more and tomorrow trying again on my windows 7 laptop, as I think I'm also getting hung up on disabling driver signatures on windows 10 laptop. IDK if it's cause I'm dual booting JingOS 0.9 and that cancels out F7 or what the hang up is on that part.

In all honesty I think you'll end up finding that the only way to recover it is by removing and reprogramming the nand in a proper programmer.

shivadow said:
In all honesty I think you'll end up finding that the only way to recover it is by removing and reprogramming the nand in a proper programmer.
Click to expand...
Click to collapse
Would that also be done in SP Flash Tool or another software? I've also got these MTK tools.

Okay a little bit of progress and interesting discovery of errors...
Upon extracting a rom from wherever in zip format, in at least 7zip it gets as far as boot.img and then has an error extracting that.
I discovered this by finding Miracle Flash Tool and clicked on Android tab, loaded the scatter file and it took and accepted it and then said boot.img missing please load and pulled up a selection window.
IDK SP Flash Tool never said that. I got drivers to work once and then rebooted now can't get them to work again keeps saying unrecognized usb device. At least it's a bit of progress.

DorkyDev said:
Okay a little bit of progress and interesting discovery of errors...
Upon extracting a rom from wherever in zip format, in at least 7zip it gets as far as boot.img and then has an error extracting that.
I discovered this by finding Miracle Flash Tool and clicked on Android tab, loaded the scatter file and it took and accepted it and then said boot.img missing please load and pulled up a selection window.
IDK SP Flash Tool never said that. I got drivers to work once and then rebooted now can't get them to work again keeps saying unrecognized usb device. At least it's a bit of progress.
Click to expand...
Click to collapse
If you have more drivers for others phones like samsumg, motorola, lg, etc so remove that's and reboot computer. Install again MTK Drivers, UAC permissions and reboot computer. Test SPFT.
But here a good video to see and may be can fix - confirm driver issue in Win7:
Drivers: https://drive.google.com/file/d/1V2FducGB4pNpbkJWVmk2sfRJpf4Q5Bth/view
DorkyDev said:
Okay a little bit of progress and interesting discovery of errors...
Upon extracting a rom from wherever in zip format, in at least 7zip it gets as far as boot.img and then has an error extracting that.
Click to expand...
Click to collapse
Maybe corrupted zip file?

Question Read Flash unbrick unlock bypass FRP & More

Hello Everyone.. here is the Instructions for OnePlus Nord CE 2-
Note:
backup Internal storage, contact message etc before process
In case, even after flashing completed successfully but some time device does not boot, only black screen, no charging sign either then don't panic, device has entered into emergency download mode, if you face the same then it's time to flash preloader.bin file.
1. Reading Firmware from Device
we download Require files USBDK Driver, Mediatek Driver & The Program
We Install both USBDK and Mediatek driver on our computer
disable windows defender and extract Program
Run Program
Select 'Firmware reader' Option and Mark The Full Firmware Option and Click 'Start Button'
{
"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"
}
turn Phone off, Press Volume up and down key and Insert USB
Reading Process Started. it will take around 15Min, once done we collect Firmware in Out Directory (it will Include nvram too)
unlocking bootloader:
there is a fastboot access issue on this device, you can try exploit method which is located Mediatek/service section...
bypass FRP lock:
From the very first Screen we Select FRP bypass Option and click 'START' Button
turn Phone off press volume up and down key and then insert usb
once done we disconnect device
Flashing Firmware:
we Go to Mediatek/Firmware Flashing Option
Select second Method 'write all partition' locate the firmware folder
click 'flash' button
turn phone off Press Volume up & down key and then inset usb
wait until success. done

Sry for the following stupid questions but:
-) How do I start the program in win64?
-) Can I use this to dump the current android rom of my phone and get boot.img+vbmeta.img thus being able to root the phone using magisk?

trohn_javolta said:
Sry for the following stupid questions but:
-) How do I start the program in win64?
-) Can I use this to dump the current android rom of my phone and get boot.img+vbmeta.img thus being able to root the phone using magisk?
Click to expand...
Click to collapse
Extract zip, run rom2box.exe
yes you can dump current ROM, Mediatek/firmware-reader

mark332 said:
Extract zip, run rom2box.exe
yes you can dump current ROM, Mediatek/firmware-reader
Click to expand...
Click to collapse
Turns out my work laptops antivirus instantly removed the .exe

Does the bootloader need to be locked to get into this preload mode and to dump the rom? I already unlocked it before.
Now if I hold up and down volume and plug in the phone Rom2box says "..handshake failed..". Rebooted after installing mediatek and usbdk drivers and I also tried different usb ports.

trohn_javolta said:
Does the bootloader need to be locked to get into this preload mode and to dump the rom? I already unlocked it before.
Now if I hold up and down volume and plug in the phone Rom2box says "..handshake failed..". Rebooted after installing mediatek and usbdk drivers and I also tried different usb ports.
Click to expand...
Click to collapse
The same story for me, the phone can't be put in preload or download mode or whatever they call it. I know one thing it is my last Oneplus phone if they're all going to be pain in the arse like this one. I guess it's back to my old 6t for another while then.

Accessing it by way of Recovery mode is also broken. To try it yourself, boot in to Recovery, connect your phone to your computer with usb-c cable. Multi-tap version number, it will eventually ask you if you want download mode and you click yes. It will attempt reboot into download mode, fail and then will `normal` boot phone.

trohn_javolta said:
Turns out my work laptops antivirus instantly removed the .exe
Click to expand...
Click to collapse
fixed a clean version + code available in public https://forum.xda-developers.com/t/tool-rom2box-all-in-one-frp-flashing-unlocking-tool.4477349/

Hi, I just tried ROM2box 2.5. I got five of these messages then kicked into recovery `Preloader - [LIB]: [31mStatus: Handshake failed, retrying...[0m`

Quaicheist said:
Hi, I just tried ROM2box 2.5. I got five of these messages then kicked into recovery `Preloader - [LIB]: [31mStatus: Handshake failed, retrying...[0m`
Click to expand...
Click to collapse
connect in Proper way= install Latest usbdk and mtk driver, start process turn Phone off press volume up & down key and then Insert USB, once the Phone is detected release keys

Thanks for the info, though I have been doing that setup all along. I dual windoze and Linux. My windows is a custom minimal version of windows 10 with feck all on it. I upgraded this phone to stock 12 beta yesterday and ROM2Box for a wonder is happily doing a dump of that. It should be interesting when I downgrade to stock 11 and try to do a dump of that.

@mark332 thanks for the advice, phone happily did dump with the OxygenOS 12 Open Beta 1 but refused point blank to do a dump with OxygenOS 11 Build number: IV2201_11_A13. Is there any difference in your phone setup to my own - bootloader unlocked?

Quaicheist said:
@mark332 thanks for the advice, phone happily did dump with the OxygenOS 12 Open Beta 1 but refused point blank to do a dump with OxygenOS 11 Build number: IV2201_11_A13. Is there any difference in your phone setup to my own - bootloader unlocked?
Click to expand...
Click to collapse
Nice, May be BROM is disabled on stable version so you are not able to dump OxygenOS 11

mark332 said:
Nice, May be BROM is disabled on stable version so you are not able to dump OxygenOS 11
Click to expand...
Click to collapse
Hi @mark332, sorry I wasn't able to get to you sooner about this. Coredump was only possible with OxygenOS 12.1 beta, BROM was definitely locked down in 11. I succeeded with 12 but 'out' folder looks incomplete, files like ''preloader' which is in the beta package are missing from the dump. I don't think I would be able return to stock with ROM2box, maybe manually with fastboot commands.

Well downgrading this phone from OxygenOS 12 beta 1 to OxygenOS 11 has left it without a working touch screen in the normal mode or recovery so it is now a dust collector unless Oneplus / Oppo are willing to fix it.

Quaicheist said:
Well downgrading this phone from OxygenOS 12 beta 1 to OxygenOS 11 has left it without a working touch screen in the normal mode or recovery so it is now a dust collector unless Oneplus / Oppo are willing to fix it.
Click to expand...
Click to collapse
I'm just curious how did you downgrade?

mark332 said:
Nice, May be BROM is disabled on stable version so you are not able to dump OxygenOS 11
Click to expand...
Click to collapse
Brom is enabled on A11 I've reflashed my device recovery partition when i was stuck

ko_hi said:
I'm just curious how did you downgrade?
Click to expand...
Click to collapse
I guess I used OnePlus's rollback guide once too often besides it is a beta, I was bound to get bitten in the arse evenually; https://community.oneplus.com/thread?id=1110424001643544581

Quaicheist said:
I guess I used OnePlus's rollback guide once too often besides it is a beta, I was bound to get bitten in the arse evenually; https://community.oneplus.com/thread?id=1110424001643544581
Click to expand...
Click to collapse
I guess if BROM mode works, use the bypass method to flash back to A11.v

Ah you see, the fecking phone managed to rollback to 11 but the touch screen driver is broken I guess. Physical buttons work but touch is broken. So I have contacted Oneplus tech support so we'll see what response I get tomorrow.