Database Develop

Unbricking "Service Required Code Corrupt"

If you use "xFSTK-SoC-Driver-Setup" and "unbrick.bat" to "Unbrick your phone, and you got the "Service code corrupt" error..., This method is untested but i think it is the problem...​You need This:
Original ICS FIRMWARE that come with your phone.
xFSTK-SoC-Driver-Setup Installed (read How Install "xFSTK-SoC-Driver-Setup")
Unbrick.bat and respective folders.
Motorola Handset USB Drivers (x86 or x64).
ADB/ FASTBOOT or SDK.
Steps to revive:
Extract Unbrick.zip in "C:\atomSOC"
Go to unbrick folder. "C:\atomSOC\unbrick"
Go to your firmware folder and copy this files (dnx; ifwi)
Replace this files in "C:\atomSOC\unbrick".
Press CAMERA button and Plug in the USB to your phone (MEDFIELD FLASH)
Run unbrick.bat in "C:\atomSOC"
How Install "xFSTK-SoC-Driver-Setup":
Run Setup
When Say "Intel Soc Is about to begin" Click OK
When Say "In Order to Complete (...) Will a device be attached (...)" Press Yes.
When Say "Step 1 (...)" Plug In your USB Cable to the pc. and click ok
When Say "Step 2 (...)" Press CAMERA button and Plug in the USB to your phone (MEDFIELD FLASH)
¿How know if my phone go to the medfield flash method?
release the camera button, your phone will stay in a black screen with the green led.
And your pc says "New hardware recognized"
Name of hardware: MEDFIELD
Before the driver install:
{
"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"
}
Downloads:
Unbrick.bat + xFSTK-SoC-Driver-Setup Download
If it works.. please, let me know​

Nope.
I just tried it, and it starts the download says a few numbers then carries on downloading.
Then the phone reboots and goes to the service required code corrupt screen

1994deano said:
I just tried it, and it starts the download says a few numbers then carries on downloading.
Then the phone reboots and goes to the service required code corrupt screen
Click to expand...
Click to collapse
Try again, your phone is not going to medfield flash mode correctly

I did not get the part - Go to your firmware folder and copy this files (dnx; ifwi)
How to go to firmware folder?,
I do not understand how to copy

i just re tried it and its got rid of the service required screen but now the screen is just black with the green led on

Me too samething, any sugestion?

gmpdri said:
Me too samething, any sugestion?
Click to expand...
Click to collapse
csn you boot to bootloader?? (power+vol.down)?

Nope
pangyaaaaaa said:
csn you boot to bootloader?? (power+vol.down)?
Click to expand...
Click to collapse
no that is why we are trying to use the medfield flash, as the bootloader is screwed up

1994deano said:
no that is why we are trying to use the medfield flash, as the bootloader is screwed up
Click to expand...
Click to collapse
I found some tools for intel lenovo pad, im trying to found how work, im think i can use it on razr i...

Boss442 said:
I found some tools for intel lenovo pad, im trying to found how work, im think i can use it on razr i...
Click to expand...
Click to collapse
ooh nice, let us know how you get on with it

S***, REALLY GOOD NEWS.....
RDS recognizes your phone on Medfield Mode...
Someone try to flash a firmware
Flashing Firmware dont work... ¿Maybe a custom XML Work?

HELP
For that ADB / Fastboot or SDK.?
Copying pro firmware?

saiko.sensei said:
For that ADB / Fastboot or SDK.?
Copying pro firmware?
Click to expand...
Click to collapse
if i found a way for bypass the "service required" error.. maybe you need fastboot... I am working with a lenovo pad (Intel SoC) maybe can use his flash tool to work (need fastboot). But dont recognize my phone, ¿Maybe need a custom driver? i am working in that

Yes, RSD lite recognises bricked phones, but it tries to enter fastboot mode to flash anything, so we're stuck...
Good luck!

Bricked while flashing JB Radio to ICS
hy,
i did the stupid error of flashing a jb radio fw to a ics phone, now also with this tool i only get the message "service required / code corrupt"
anny idea?
btw.: i found a gui tool that does the same thing, there you can not only upload the firmware but also an operating system (you need a fw dnx and ifwi file and a os dnx and image file) anny idea where we could get the os files? i suppose flashing both (fw and dns) would unbrick the phone in all bricking cases.
i know it has already been said, but turn off your phone and keep the camera button pressed while connecting it (if you get the service required error). if the screen stays black just run the tool.
in my case flashing an ics fw dnx leads to the device corrupt message, and flashing a jb fw dnx leads to the black screen.

Boss, you are a good man for trying to help other people. Getting something like this working in the community would be brilliant, as I've tried to communicate to others. The most help I got was from outside the RAZR i forum, most here just don't give a sh1t in helping others. I have created 2 help threads to guide people - information to help prevent further cases.
I have concluded the same - that 'unbrick.bat' fixes some problems and creates a far bigger one - the service required, code corrupt problem. I wasn't sure if I could say that directly but I've a lot of messages in my inbox about this and almost everyone arrived at that after using that unbrick. How that is still available is incredible, since it's the biggest brick-creator on here that I know.

mercurio. said:
hy,
i did the stupid error of flashing a jb radio fw to a ics phone, now also with this tool i only get the message "service required / code corrupt"
anny idea?
btw.: i found a gui tool that does the same thing, there you can not only upload the firmware but also an operating system (you need a fw dnx and ifwi file and a os dnx and image file) anny idea where we could get the os files? i suppose flashing both (fw and dns) would unbrick the phone in all bricking cases.
i know it has already been said, but turn off your phone and keep the camera button pressed while connecting it (if you get the service required error). if the screen stays black just run the tool.
in my case flashing an ics fw dnx leads to the device corrupt message, and flashing a jb fw dnx leads to the black screen.
Click to expand...
Click to collapse
You can found Ifwi and dnx in your firmware folder... download a rds firmware and you found the two files. Upload and send me the gui-tool please!
So.. You cannot downgrading ifwi and dnx, but if you use ifwi and dnx (JB) with a ICS system, you got the black screen... so the black screen brick and "service required"brick are the same brick
SharpnShiny said:
Boss, you are a good man for trying to help other people. Getting something like this working in the community would be brilliant, as I've tried to communicate to others. The most help I got was from outside the RAZR i forum, most here just don't give a sh1t in helping others. I have created 2 help threads to guide people - information to help prevent further cases.
I have concluded the same - that 'unbrick.bat' fixes some problems and creates a far bigger one - the service required, code corrupt problem. I wasn't sure if I could say that directly but I've a lot of messages in my inbox about this and almost everyone arrived at that after using that unbrick. How that is still available is incredible, since it's the biggest brick-creator on here that I know.
Is your phone bricked in this condition right now? If it is, feel free to PM me.
Click to expand...
Click to collapse
My phone isn't bricked, i know people that unbrick.bat work right, but some people brick your phone, so i know this is a "Most devices problem" (Firmware problem, work for people that IFWI and dnx are extracted from the same firmware that are using)
Unbrick.bat provides a tool can flash some files (IFWI & DNX) to the phone (These files are responsible for the brick) and i only im working with the same tool that can solve the problem, unbrick.bat (or xFSTK-Downloader) is a good tool, but the use brick the phone, example: if i solve my downgrading brick , and i upload my files (Unbrick.bat with ifwi and dnx) this work only for people with use my firmware (example: Orange ICS), for other people that uses other firmware (Claro Argentina) the phone bricks and show "Service required blah blah blah" im trying to go back to the original "ifwi and dnx" files, some people on other forums says that the phone dont show anymore the "service required" error... but the phone only shows a green led (same thing that downgrading brick).
xFSTK-Downloader is used to update the Orange sandiego (First Intel Atom android, dont use fastboot) and Ienovo pad (Use xFSTK-Downloader-GUI, and a "Flashtool").
xFSTK-Downloader is like a Odin for intel phones. sorry for my english but if you know spanish pm me and can explain more
I read 80 pages in modaco for intel san diego and 40 for Ienovo pad, and they uses xFSTK-Downloader to update the phones.

Boss442 said:
You can found Ifwi and dnx in your firmware folder... download a rds firmware and you found the two files. Upload and send me the gui-tool please!
So.. You cannot downgrading ifwi and dnx, but if you use ifwi and dnx (JB) with a ICS system, you got the black screen... so the black screen brick and "service required"brick are the same brick
My phone isn't bricked, i know people that unbrick.bat work right, but some people brick your phone, so i know this is a "Most devices problem" (Firmware problem, work for people that IFWI and dnx are extracted from the same firmware that are using)
Unbrick.bat provides a tool can flash some files (IFWI & DNX) to the phone (These files are responsible for the brick) and i only im working with the same tool that can solve the problem, unbrick.bat (or xFSTK-Downloader) is a good tool, but the use brick the phone, example: if i solve my downgrading brick , and i upload my files (Unbrick.bat with ifwi and dnx) this work only for people with use my firmware (example: Orange ICS), for other people that uses other firmware (Claro Argentina) the phone bricks and show "Service required blah blah blah" im trying to go back to the original "ifwi and dnx" files, some people on other forums says that the phone dont show anymore the "service required" error... but the phone only shows a green led (same thing that downgrading brick).
xFSTK-Downloader is used to update the Orange sandiego (First Intel Atom android, dont use fastboot) and Ienovo pad (Use xFSTK-Downloader-GUI, and a "Flashtool").
xFSTK-Downloader is like a Odin for intel phones. sorry for my english but if you know spanish pm me and can explain more
I read 80 pages in modaco for intel san diego and 40 for Ienovo pad, and they uses xFSTK-Downloader to update the phones.
Click to expand...
Click to collapse
I found out that the tool I ment is the xFSTK-Downloader ( rghost.net/44421368 ) that was alreaddy linked here at xda by U1138 in: http://forum.xda-developers.com/showthread.php?t=2184877
And yes, i suppose the black screen only and the service required brick are the same. they probably are due to a not working combination of firmware (ifwi & dnx) and flashed OS (i suppose the fastboot, no idea how where to get the dnx file needed for flashing it). you can try different ifwi and dnx files and get different results (so far i think there are only two types, the ones for JB fw and the others for ICS).
If you flash your rom with RSD going from JB to ICS you also flash the ifwi & dnx files, but not the bootloader. Therefore you end up with a non working combination of firmware (ifwi) and OS (fastboot) => nothing starts at all.
This problem was easy to fix for me flashing the appropriate JB firmware.
Then I did the mistake of flashing the JB radio before flashing a JB rom. This lead to a situation where neither the JB (leads to service required warning) nor the ICS (black screen, green led on) firmware works anymore and I have no idea how i could change the situation.
Anyone has some ideas how to flash the fastboot with the xFSTK-Downloader?

mercurio. said:
Anyone has some ideas how to flash the fastboot with the xFSTK-Downloader?
Click to expand...
Click to collapse
+ 1
Everything else I was try with U 1138`s help - without result

St.Noigel said:
+ 1
Everything else I was try with U 1138`s help - without result
Click to expand...
Click to collapse
I read more than 120 pages in forums, and... NOTHING!
But i'm triyng to port a "flash tool" from lenovo pad... :silly:

V20c-EUR-XXX-OCT-07-2014 LG 4x official ROM

Hi guys i need someone to upload latest official V20C rom (open euro ita or ger) because i cant download it from LG Firmware site and the one i have when i flash it auto brightness isnt working (i checked everything is ok with hardwer just software problem prob bad copy or whatever).Thanks

Please Check HERE
These are only .kdz
Direct download ITALY
(Please refresh direct link, If download does not start OR click on link and press Enter Key)

Salman Al-Badgail said:
Please Check HERE
These are only .kdz
Direct download ITALY
(Please refresh direct link, If download does not start OR click on link and press Enter Key)
Click to expand...
Click to collapse
Thank you trick with enter helped me

dimi89 said:
Thank you trick with enter helped me
Click to expand...
Click to collapse
great :good:

InterrtuptoR said:
Unfortunately u didnt tag me xD i made a mistake when i created my name so im not interruptor xD
Iam now on v20c and things didnt change much on cm11, ril droped and nfc is buggy, nfc isnt a problem that much after a couple of restarts it works it just freezes device for less then a minute and then works, but after one reboot it worked better, it switched on/of faster, but ril dropped... i need stable ril now so im back to stock where everything works fine...
{
"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"
}
Sent from my LG-P880 using Tapatalk
Click to expand...
Click to collapse
Phil_Smith said:
Oh, nevermind: Thanks @Salman Al-Badgail
Click to expand...
Click to collapse
Salman Al-Badgail said:
great :good:
Click to expand...
Click to collapse
OK..., take time to check : LGExtract.exe -kdz V20C_00.kdz
Then just open resulting cab for .dz_verification: "LGP880AT-00-V20c-EUR-XXX-OCT-07-2014+0.dz"
If needed I can upload it.

oF2pks said:
OK..., take time to check : LGExtract.exe -kdz V20C_00.kdz
Then just open resulting cab for .dz_verification: "LGP880AT-00-V20c-EUR-XXX-OCT-07-2014+0.dz"
If needed I can upload it.
Click to expand...
Click to collapse
So you think i dont have the right v20c?
Where can i find the lgextract.exe?

InterrtuptoR said:
So you think i dont have the right v20c?
Where can i find the lgextract.exe?
Click to expand...
Click to collapse
Check here for LGExtract.exe
I am not sure if this help you or not.

oF2pks said:
OK..., take time to check : LGExtract.exe -kdz V20C_00.kdz
Then just open resulting cab for .dz_verification: "LGP880AT-00-V20c-EUR-XXX-OCT-07-2014+0.dz"
If needed I can upload it.
Click to expand...
Click to collapse
I have the same dz...

@InterrtuptoR now your main problem is about ril and nfc ??? Please confirm. Please change firmware to v20A and give a shot and let us know, also try changing SIM so that we can come to conclusion

Salman Al-Badgail said:
@InterrtuptoR now your main problem is about ril and nfc ??? Please confirm
Click to expand...
Click to collapse
Mainly ril, i dont use nfc that much...
Im on stock now and everything is fine...
Sent from my LG-P880 using Tapatalk

@InterrtuptoR For RIL you can change firmware to either v20b or v20a and also try changing sim card and please check. For bad network some time sim card that too old might create a problem, anyway give a shot and please do report so that we can see what else we can do for you. For now I am sleeping its already late. will get back to you after next 12-14hr
Thanks

Salman Al-Badgail said:
@InterrtuptoR For RIL you can change firmware to either v20b or v20a and also try changing sim card and please check. For bad network some time sim card that too old might create a problem, anyway give a shot and please do report so that we can see what else we can do for you.
Thanks
Click to expand...
Click to collapse
I was on 20b, now on 20c, will try 20a and change sim, but i think its not the hardware cause all works on stock...
If it was the sim it wouldnt work on stock, right? I dont have time now to try all that, but will report when i try...
Sent from my LG-P880 using Tapatalk

@InterrtuptoR sure give a try, Thanks

@Phil_Smith @InterrtuptoR , after many readings:
http://forum.xda-developers.com/search/thread/2780274?query=02.1233
http://forum.xda-developers.com/showthread.php?t=2329768
it looks logical that your AboutPhone/screen indicates a v20c/01.1233 firmware different from last kdz flashed...; if not : it means you used a "tricky" method to upgrade to v20c_00.kdz...
FIRST (lucky? ) remove your battery for few and reboot back to check changes in AboutPhone/screen for KitKat minimum;
CHECK BEST: http://forum.xda-developers.com/optimus-4x-hd/general/lg-p880-firmware-flash-upgrade-t2919195
(I remember I used odd ref http://forum.xda-developers.com/showthread.php?t=2069723 with v20d/02.1216.01)
@dimi89 can you upgrade this thread/title with cleared ref V20c-EUR-XXX-OCT-07-2014
Download mirror for official LG2014 v20c_00.kdz (zipped) & P880-Flashtools.rar : https://www.androidfilehost.com/?w=files&flid=128886

@oF2pks Appreciate Man for uploading .kdz This might help many users. Also upload any v10xyz for ICS stock user like a complete package.
Thanks again

oF2pks said:
@Phil_Smith @InterrtuptoR , after many readings:
http://forum.xda-developers.com/search/thread/2780274?query=02.1233
http://forum.xda-developers.com/showthread.php?t=2329768
it looks logical that your AboutPhone/screen indicates a v20c/01.1233 firmware different from last kdz flashed...; if not : it means you used a "tricky" method to upgrade to v20c_00.kdz...
FIRST (lucky? ) remove your battery for few and reboot back to check changes in AboutPhone/screen for KitKat minimum;
CHECK BEST: http://forum.xda-developers.com/optimus-4x-hd/general/lg-p880-firmware-flash-upgrade-t2919195
(I remember I used odd ref http://forum.xda-developers.com/showthread.php?t=2069723 with v20d/02.1216.01)
@dimi89 can you upgrade this thread/title with cleared ref V20c-EUR-XXX-OCT-07-2014
Download mirror for official LG2014 v20c_00.kdz (zipped) & P880-Flashtools.rar : https://www.androidfilehost.com/?w=files&flid=128886
Click to expand...
Click to collapse
First of all thanks for all your research and help!
Sadly the LG Mobile Support Tool always stops saying "Upgrade stopped due to an error".
Anything I can do?
Edit: And thinking that it might have to do with Windows version (running Windows 10 x64), I tried using a virtual machine emulating Win 7 x64, but here it says "Cannot connect to server"...

(usual at your own risks...)
Phil_Smith said:
First of all thanks for all your research and help!
Sadly the LG Mobile Support Tool always stops saying "Upgrade stopped due to an error".
Anything I can do?
Edit: And thinking that it might have to do with Windows version (running Windows 10 x64), I tried using a virtual machine emulating Win 7 x64, but here it says "Cannot connect to server"...
Click to expand...
Click to collapse
( @InterrtuptoR )
Remember that .kdz is LG' file_support for upgrade/init firmware; the good is that the Win dll/flash is included in the .kdz (better option than tricky .dz flash): check whole thread http://forum.xda-developers.com/optimus-4x-hd/general/lg-p880-firmware-flash-upgrade-t2919195
- use CSE flash with custom rom
(- OR restore a JB nandroid and then use NORMAL flash for an upgrade on JB)
If trouble :
-FIRST (lucky ?) : try another usb cable
-HARD : format via cwm and proceed http://forum.xda-developers.com/showthread.php?t=2069723
I'm pretty sure @dimi89 just went threw this; he is an early p880' user and will help for steps or different way (?)
Once done, you need to flash cwm and a custom rom to check that AboutPhone/baseband is showing exact kdz :"LGP880AT-00-V20c-EUR-XXX-OCT-07-2014" and not the version firmware 02.1233, ie a different kdz origin.
(Under resulting LG JB, the AboutPhone/os firmware indication is always the rom in use, not the original kdz, so it always looks good even if not...like old 2013 V20C or remix... )

oF2pks said:
( @InterrtuptoR )
Remember that .kdz is LG' file_support for upgrade/init firmware; the good is that the Win dll/flash is included in the .kdz (better option than tricky .dz flash): check whole thread http://forum.xda-developers.com/optimus-4x-hd/general/lg-p880-firmware-flash-upgrade-t2919195
- use CSE flash with custom rom
(- OR restore a JB nandroid and then use NORMAL flash for an upgrade on JB)
If trouble :
-FIRST (lucky ?) : try another usb cable
-HARD : format via cwm and proceed http://forum.xda-developers.com/showthread.php?t=2069723
I'm pretty sure @dimi89 just went threw this; he is an early p880' user and will help for steps or different way (?)
Once done, you need to flash cwm and a custom rom to check that AboutPhone/baseband is showing exact kdz :"LGP880AT-00-V20c-EUR-XXX-OCT-07-2014" and not the version firmware 02.1233, ie a different kdz origin.
(Under resulting LG JB, the AboutPhone/os firmware indication is always the rom in use, not the original kdz, so it always looks good even if not...like old 2013 V20C or remix... )
Click to expand...
Click to collapse
Thanks for your response!
"-FIRST (lucky ?) : try another usb cable"
Tried another one, but the errors stay the same. I also know that the cable I use worked for data transfer before.
"-HARD : format via cwm and proceed http://forum.xda-developers.com/showthread.php?t=2069723"
I tried that, but the LG software update tool keeps saying "phone not found"... Tried an 2.0 usb port at the back of my PC and also here tried a different cable - the error persists.

Phil_Smith said:
Thanks for your response!
"-FIRST (lucky ?) : try another usb cable"
Tried another one, but the errors stay the same. I also know that the cable I use worked for data transfer before.
"-HARD : format via cwm and proceed http://forum.xda-developers.com/showthread.php?t=2069723"
I tried that, but the LG software update tool keeps saying "phone not found"... Tried an 2.0 usb port at the back of my PC and also here tried a different cable - the error persists.
Click to expand...
Click to collapse
Okay, I tried it on a PC that natively runs Windows 7 and of course again the Windows version caused the mess... On that 7 machine everything went smoothly (although the "Cannot connect to server" error persisted, I was able to ignore it, as the program proceeded in the background).
Really to all of you having issues with upgrading LG software and running Windows 8 or higher:
Do not waste hours and simply try on a Windows 7 machine!
I remember having had troubles likes that before on win 8.1 , where the only solution in the end had been the same... it can drive you mad, so just please skip that!
Now I'm on cm11 nightly and "about phone" still shows L6260_MODEM_SIC_02.1233.00 under Baseband-Verison ...

Phil_Smith said:
Okay, I tried it on a PC that natively runs Windows 7 and of course again the Windows version caused the mess... On that 7 machine everything went smoothly (although the "Cannot connect to server" error persisted, I was able to ignore it, as the program proceeded in the background).
Really to all of you having issues with upgrading LG software and running Windows 8 or higher:
Do not waste hours and simply try on a Windows 7 machine!
I remember having had troubles likes that before on win 8.1 , where the only solution in the end had been the same... it can drive you mad, so just please skip that!
Now I'm on cm11 nightly and "about phone" still shows L6260_MODEM_SIC_02.1233.00 under Baseband-Verison ...
Click to expand...
Click to collapse
I'm now on @csk1jw 's new 7.1 ROM where my baseband version now shows the correct "LGP880AT-00-V20c-EUR-XXX-OCT-07-2014" which seems to be good, right?
GetRIL though still says "unknown RIL", but I'm not sure if that's just normal.

[ROM][STOCK] Stock Firmware Packages (For Expanded EDL Tools)

Stock Firmware Packages
Yes, they are finally here! This thread is for stock firmware packages.
These packages are specifically made to be installed with this EDL tool: https://forum.xda-developers.com/ax...n-10-pro-5g-expanded-edl-tools-fixes-t4174667
READ THE WARNINGS IN THAT THREAD BEFORE USING THE TOOLS
These packages are UNOFFICIAL unless marked otherwise. ZTE has not released stock firmware packages for most phones and versions.​
How to install an EDL firmware package:
Note: These packages are specifically made for the EDL tools, not MiFlash or anything else.
1. Install the latest version of the EDL tools (in this thread)
2. Download a firmware package from this thread.
3. Unpack the firmware archive into the tool directory "Firmware_Package_Restore"
Make sure you unpack the firmware into Firmware_Package_Restore directory like this -​Just for example - the script would be located in:​"...\Axon10_(More)_EDL_Tools_v1_1b\Firmware_Package_Restore\Write Firmware v1.10 to A.ps1"​And the firmware files would be in:​"...\Axon10_(More)_EDL_Tools_v1_1b\Firmware_Package_Restore\firmware_1_10\"​4. Put phone in EDL mode and run Load Programmer
5. Run a backup of your phone! Even if it isn't booting.
6. Run whichever "Write Firmware vX to Y.ps1" you want (X = firmware version, Y = A or B partition) (If you don't know which partition is currently booting, just install both.)
7. Wait for the install to finish ("done")
8. Start the phone (hold the power button until it resets, or run the Reset script)
9. You might see a few bootloops and then the phone ask you to do a factory reset / system wipe.
10. If the phone does not boot - look in the tools thread for how to use the Fix Bootable tool and try that.
11. Done.
Firmware Package Downloads:
~~~ A2020U (US Version) (Non-5G) ~~~
Firmware Version: 1.10 (GEN_NA_A2020U_PROV1.10)
Android: 9 (Pie)
Source: UNOFFICIAL (bobthenormal)
Download: Axon10Pro A2020U EDL Firmware v1.10(A9)
(If you downloaded this firmware before 12/9/2020 the script had an error, re-download the firmware or simply replace the script files with these ones: Firmware 1.10 Script Fix)
Thanks:
@djkuz for the original EDL tool for Axon 7
@Unjustified Dev for his port of the tool and tons of other work
@rafyvitto for a ton of ROMs and his stock B12 backup
and @eKeith for requesting the firmware enough times I finally bothered to make it =P

Please keep issues with the firmware here, and issues with the EDL tools in that thread.
I will upload firmware versions for A2020U: 1.11, 1.13, 2.09 (A10) (locked and unlocked). I just need to get time to actually test these out to make sure they work.
I didn't test the 1.10 version either but it should work and some people are stuck on A10 without it so I'm trying to post it quickly.
If anyone can wants the tools or firmware packages like these for their phone version (EU, CN, whatever non-A2020U Non-5G) and can volunteer their phone/time, PM me - I can't do them myself as I don't have those phones, but I can give safe instructions on what to do so that I can change make a version of the tools for those phones.

Hi i want the Firmware for zte axon 10 pro 5g 6ram
Details in photo
{
"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"
}
Axon 10 Pro (Non-5G) EDL Tool - Flash / Backup / Restore/ Bootloader Unlock
Axon 10 EDL Tool BAT-program for Flash / Backup / Restore/ Bootloader Unlock Qualcomm HS-USB QDLoader 9008 (COM ...) !!! Whatever you do, you do at your own risk !!!" !!! If you are not sure of yourself do not use this program !!! Special...
forum.xda-developers.com
My post

amooor said:
Hi i want the Firmware for zte axon 10 pro 5g 6ram
Details in photo
View attachment 5146295
Axon 10 Pro (Non-5G) EDL Tool - Flash / Backup / Restore/ Bootloader Unlock
Axon 10 EDL Tool BAT-program for Flash / Backup / Restore/ Bootloader Unlock Qualcomm HS-USB QDLoader 9008 (COM ...) !!! Whatever you do, you do at your own risk !!!" !!! If you are not sure of yourself do not use this program !!! Special...
forum.xda-developers.com
My post
Click to expand...
Click to collapse
I'd suggesta new thread. I haven't seen anyone with that phone or a firmware package for it. If you can find someone that has your phone with stock firmware who is willing to do a little work, I'll tell them what to do to make it.

bobthenormal said:
I'd suggesta new thread. I haven't seen anyone with that phone or a firmware package for it. If you can find someone that has your phone with stock firmware who is willing to do a little work, I'll tell them what to do to make it.
Click to expand...
Click to collapse
Am sure 100% the problem is Firmware.
Do you know why because the holder tray for your ZTE Axon 10 Pro 5g in my phone is making for 1 sim like oneplus 7t in t-mobile if you unlocked and change the holder tray to hybrid dual sim it will work

Hello, I tried to use your tools to restore my phone since its on the European version and my sim card doesn't work (its US). The Write Firmware v1.10 to A tells me that COMPort is not found even though I already launched the load programmer script and see a COMPort file in the folder. Any ideas on what I can do? Thank you for your time!

los95 said:
Hello, I tried to use your tools to restore my phone since its on the European version and my sim card doesn't work (its US). The Write Firmware v1.10 to A tells me that COMPort is not found even though I already launched the load programmer script and see a COMPort file in the folder. Any ideas on what I can do? Thank you for your time!
Click to expand...
Click to collapse
Make sure you unpack the firmware into Firmware_Package_Restore directory like this -
Just for example - the script would be located in:
"...\Axon10_(More)_EDL_Tools_v1_1b\Firmware_Package_Restore\Write Firmware v1.10 to A.ps1"
And the firmware files would be in:
"...\Axon10_(More)_EDL_Tools_v1_1b\Firmware_Package_Restore\firmware_1_10\"

bobthenormal said:
Make sure you unpack the firmware into Firmware_Package_Restore directory like this -
Just for example - the script would be located in:
"...\Axon10_(More)_EDL_Tools_v1_1b\Firmware_Package_Restore\Write Firmware v1.10 to A.ps1"
And the firmware files would be in:
"...\Axon10_(More)_EDL_Tools_v1_1b\Firmware_Package_Restore\firmware_1_10\"
Click to expand...
Click to collapse
Thanks for the response! I will try it on Tuesday as I have finals. Will update to see what happens.

Okay I tried it again with the steps and now its giving me this.
https://pastebin.com/LwbK3vf7
It tells me that it can't find the files even though I have put the folder in that directory. Sorry for being ignorant I thought this wouldn't be too bad since I used to root Samsung devices.
Update:
I downloaded the new version of the edl tools and it still can't find the firmware files. Here is the log.
https://pastebin.com/LRuXEx0y
Another Update:
Sorry for the updates just wanted to see if I can fix it but I figured out why it didn't find the files.
For some reason, it would try to find the files inside the Firmware_Package_Restore instead of its own folder.
Now, I am getting another error that is says that my device is not on the port although I put it in edl mode. Perhaps I am doing something wrong? Here is another log with this error.
https://pastebin.com/ZtXwhUB0

los95 said:
Okay I tried it again with the steps and now its giving me this.
https://pastebin.com/LwbK3vf7
It tells me that it can't find the files even though I have put the folder in that directory. Sorry for being ignorant I thought this wouldn't be too bad since I used to root Samsung devices.
Update:
I downloaded the new version of the edl tools and it still can't find the firmware files. Here is the log.
https://pastebin.com/LRuXEx0y
Another Update:
Sorry for the updates just wanted to see if I can fix it but I figured out why it didn't find the files.
For some reason, it would try to find the files inside the Firmware_Package_Restore instead of its own folder.
View attachment 5152479
Now, I am getting another error that is says that my device is not on the port although I put it in edl mode. Perhaps I am doing something wrong? Here is another log with this error.
https://pastebin.com/ZtXwhUB0
Click to expand...
Click to collapse
Hey! Thanks for attaching the log, that was perfect for finding the issue right away. The script is building the search_path incorrectly, here's corrected copies of the scripts. I'll update and re-upload the full firmware zip file as soon as I get a chance, but just replace the ones you have with these.
EDIT: Ah, yes hold on I'll take a look at the second issue. Sorry about that, didn't have a chance to test these.
So, the new problem appears to be something with the COM port communication. I have to get going in a minute but a few suggestions to try:
Reboot your phone into EDL then run the loader/firmware scripts right away. Sometimes the ports kind of time out.
Open Device Manager in windows and open the "Ports" list and make sure you see your phone on there. Edit the COMPort file to have the right one, or delete it to force the script to re-check if it's trying to connect to the wrong one.
Check the drivers - the tools have the stock A2020U drivers included, might need to reinstall them especially if you install drivers for other phones.
See if any of those help, let me know how it goes.

bobthenormal said:
Hey! Thanks for attaching the log, that was perfect for finding the issue right away. The script is building the search_path incorrectly, here's corrected copies of the scripts. I'll update and re-upload the full firmware zip file as soon as I get a chance, but just replace the ones you have with these.
EDIT: Ah, yes hold on I'll take a look at the second issue. Sorry about that, didn't have a chance to test these.
So, the new problem appears to be something with the COM port communication. I have to get going in a minute but a few suggestions to try:
Reboot your phone into EDL then run the loader/firmware scripts right away. Sometimes the ports kind of time out.
Open Device Manager in windows and open the "Ports" list and make sure you see your phone on there. Edit the COMPort file to have the right one, or delete it to force the script to re-check if it's trying to connect to the wrong one.
Check the drivers - the tools have the stock A2020U drivers included, might need to reinstall them especially if you install drivers for other phones.
See if any of those help, let me know how it goes.
Click to expand...
Click to collapse
Thanks I will try this.
Edit:
I ended up deleting the com port file, ran Load Programmer, and the scripted worked. However, when it finished and I go back to boot my phone (I had to use the other edl tool and asked it to unlock the google FRP since I don't know another method to boot it back to normal) it boot back to the old rom it had. Its like it didn't write anything to the phone although the script did show me it was doing its job and end with a success. Any ideas? Here is my phone with the same firmware still installed after using the script.
Update:
I decided to use the write firmware to b instead and now it is American. Thank you for all the hard work I thought I had to carry two phones with me everywhere lol. Now I have another question. When I reboot my phone, a message pops up saying that the phone is unlocked and to either press the power button to pause or continue. I read in the threads that this means that fast boot is disabled. Is there anyway I can get fast boot back?

los95 said:
Thanks I will try this.
Edit:
I ended up deleting the com port file, ran Load Programmer, and the scripted worked. However, when it finished and I go back to boot my phone (I had to use the other edl tool and asked it to unlock the google FRP since I don't know another method to boot it back to normal) it boot back to the old rom it had. Its like it didn't write anything to the phone although the script did show me it was doing its job and end with a success. Any ideas? Here is my phone with the same firmware still installed after using the script.
View attachment 5153355
Update:
I decided to use the write firmware to b instead and now it is American. Thank you for all the hard work I thought I had to carry two phones with me everywhere lol. Now I have another question. When I reboot my phone, a message pops up saying that the phone is unlocked and to either press the power button to pause or continue. I read in the threads that this means that fast boot is disabled. Is there anyway I can get fast boot back?
Click to expand...
Click to collapse
Nice! Super glad that it worked.
That A/B issue is why I considered just making the script automatically install it to both A and B. The only way I can tell which side is booting is to go into fastboot, which I find annoying. But if you install a ROM to A while you're booting from B, you won't see it obviously, so I generally just flash both sides at the same time since I always have full backups of both anyway.
As for that message, it sort-of means fastboot is disabled - it pops up when:
1. the bootloader is unlocked
AND
2. the stock bootloader is installed
So to get rid of the message you can either re-lock the phone OR install Unjustified Dev's patched bootloader. And since the stock bootloader does not have fastboot, the only way to have it is to install the unlocked bootloader.
You can do that either through the old tool ("unlock" the phone again), or through mine by running "write_UD-bootloader.ps1" in the Write_Unlocked_Bootloader_and_FRP folder.

bobthenormal said:
Nice! Super glad that it worked.
That A/B issue is why I considered just making the script automatically install it to both A and B. The only way I can tell which side is booting is to go into fastboot, which I find annoying. But if you install a ROM to A while you're booting from B, you won't see it obviously, so I generally just flash both sides at the same time since I always have full backups of both anyway.
As for that message, it sort-of means fastboot is disabled - it pops up when:
1. the bootloader is unlocked
AND
2. the stock bootloader is installed
So to get rid of the message you can either re-lock the phone OR install Unjustified Dev's patched bootloader. And since the stock bootloader does not have fastboot, the only way to have it is to install the unlocked bootloader.
You can do that either through the old tool ("unlock" the phone again), or through mine by running "write_UD-bootloader.ps1" in the Write_Unlocked_Bootloader_and_FRP folder.
Click to expand...
Click to collapse
Thanks for the great help. Now I have installed twrp and will most likely just put magisk and keep the stock rom as I am now terrified on installing a custom rom since it lead to me to a lot of trouble. Maybe I will touch lineage later on but for now I will just have twrp and root.

los95 said:
Thanks for the great help. Now I have installed twrp and will most likely just put magisk and keep the stock rom as I am now terrified on installing a custom rom since it lead to me to a lot of trouble. Maybe I will touch lineage later on but for now I will just have twrp and root.
Click to expand...
Click to collapse
You're welcome!
I wouldn't be afraid of doing custom roms once you do a full backup of your working phone with my tools! If you have the 256gb phone you can add the userdata backup to that and really have everything including settings, apps, and data. Then if anything goes wrong you just do a full restore back to exactly where you were.
I haven't been trying custom ROMs because I just don't have the hours to spend trying them out and re-configuring each one to find out which I want to use, otherwise I definitely would. The stock ROM is really kinda poop (I'm on A10).
Also, if you try flashing a custom ROM and it doesn't boot after you install it - before assuming it didn't work and restoring, FIRST try the "Fix bootable" tool. Some ROMs get installed to a different partition than they were made from, so they have that flag for which partition they think they are installed on. When it doesn't match it won't boot. Good luck!

bobthenormal said:
You're welcome!
I wouldn't be afraid of doing custom roms once you do a full backup of your working phone with my tools! If you have the 256gb phone you can add the userdata backup to that and really have everything including settings, apps, and data. Then if anything goes wrong you just do a full restore back to exactly where you were.
I haven't been trying custom ROMs because I just don't have the hours to spend trying them out and re-configuring each one to find out which I want to use, otherwise I definitely would. The stock ROM is really kinda poop (I'm on A10).
Also, if you try flashing a custom ROM and it doesn't boot after you install it - before assuming it didn't work and restoring, FIRST try the "Fix bootable" tool. Some ROMs get installed to a different partition than they were made from, so they have that flag for which partition they think they are installed on. When it doesn't match it won't boot. Good luck!
Click to expand...
Click to collapse
Thanks for the tip! I forgot to mention something strange about the reset from edl tool. When I was turning my phone back to American, I tried to use that and it gave me an error saying this
{ERROR: Command line argument 'reset=' is not recognized as a valid option}
On the shell window it shows different options and there is one that says reset but without = sign. I'm not sure if its some typo but wanted to let you know.

los95 said:
Thanks for the tip! I forgot to mention something strange about the reset from edl tool. When I was turning my phone back to American, I tried to use that and it gave me an error saying this
{ERROR: Command line argument 'reset=' is not recognized as a valid option}
On the shell window it shows different options and there is one that says reset but without = sign. I'm not sure if its some typo but wanted to let you know.
Click to expand...
Click to collapse
Ah that is weird! I must have forgot to save some changes to that script, it's supposed to use the XML file. Fixed that and threw on a script with a long delay ( version 1.1d now)
Thanks for pointing that out.. my quality control guy is slacking! (I'm the quality control guy...)
Lemme know if you find any other ones.

bobthenormal said:
Ah that is weird! I must have forgot to save some changes to that script, it's supposed to use the XML file. Fixed that and threw on a script with a long delay ( version 1.1d now)
Thanks for pointing that out.. my quality control guy is slacking! (I'm the quality control guy...)
Lemme know if you find any other ones.
Click to expand...
Click to collapse
Sorry for all the replies I just want to be sure everything is fine with the backup tool. I did the full back up and it looks like it worked but I was getting warnings that the files it was looking for returned as null. Is that supposed to happen? Here is the link with the log.
backup_all log - Pastebin.com

los95 said:
Sorry for all the replies I just want to be sure everything is fine with the backup tool. I did the full back up and it looks like it worked but I was getting warnings that the files it was looking for returned as null. Is that supposed to happen? Here is the link with the log.
backup_all log - Pastebin.com
Click to expand...
Click to collapse
Oh whew, you scared me if there was a problem with backup_all
That's the one I was especially careful about since I got burned by the original EDL backup tool.
No worries about bringing up potential issues, I can't guarantee the tools don't mess up anyone's phone but I'd still feel terrible if they did so I appreciate the "bug testing".
The warnings there are all good even though they look scary.
If you look in the log, you see the files are attempt to read (and returned NULL) first, then once it has gone through all of them it repeats the list. The way the EDL interface works is kind of odd. It doesn't take a "read" command, it takes a "write" command "reversed", so it executes it like a write command sort of. That means it looks for the files to "write" first to prepare, even though it doesn't actually use them (except to overwrite them if they do exist).
It makes sense from a programming perspective, efficient and saves ROM.

Hi, I am back again. Magisk had an update and after it was installed, the phone wouldn't boot up anymore. It just stayed at the bootloader and I had to wipe it and installed the original firmware as for some unknown reason, my backup is not there. I tried using the restore tool and it couldn't find my back up. I checked the specific files folders to see if the backup was there and nothing was found. The good thing is that the phone can be brought back life even if I have to start fresh ( I don't mind it to be honest since I don't use a lot of apps). This inspired me to install lineage but the link on that thread is broken. Someone asked the OP of the thread about it but I think he hasn't been active for a while. Do you by any chance have the lineage rom file? Sorry for asking but I don't know where to look. Thanks for reading!

los95 said:
Hi, I am back again. Magisk had an update and after it was installed, the phone wouldn't boot up anymore. It just stayed at the bootloader and I had to wipe it and installed the original firmware as for some unknown reason, my backup is not there. I tried using the restore tool and it couldn't find my back up. I checked the specific files folders to see if the backup was there and nothing was found. The good thing is that the phone can be brought back life even if I have to start fresh ( I don't mind it to be honest since I don't use a lot of apps). This inspired me to install lineage but the link on that thread is broken. Someone asked the OP of the thread about it but I think he hasn't been active for a while. Do you by any chance have the lineage rom file? Sorry for asking but I don't know where to look. Thanks for reading!
Click to expand...
Click to collapse
Damn that's not good. You checked in the Backup tool folder for the backups?
They would be named "backup_all-critical-(date/time)" and "backup_all-non-critical-(date/time)"
The Restore tool doesn't automatically try to find backups, you have to move the backup files you want to restore into the restore directories (critical to critical, non-critical to non-critical).
It's not super user friendly, but it's a ton of extra work to make it search for backups and pop up a menu and such. Hopefully that's the issue, but if not I'd like to know if you figure out why the backups aren't there.
I *think* I have the lineage ROM... but I can't upload it right now, on slow internet! Might be a few weeks before I get back, if rafy hasn't uploaded it by then I'll upload it.
Also, the magisk update - I've had that happen on several phones too where it tries to update itself and bricks, so I'm really careful about when I do updates. Not sure if there's a safe method, maybe uninstalling magisk and reinstalling the new version.

.

[GUIDE] Unlock bootloader of Lenovo Tab 4 10 with OEM unlock "greyed out" (TB-X304F/L and other Qcom tablets)

WARNING: DO THIS AT YOUR OWN RISK !!!!
I AM NOT RESPONSIBLE IF YOU START CRYING INTO YOUR BRICKED TABLET
This guide is only for devices with "OEM Unlocking" option greyed out !!!
Others can follow the simpler procedure mentioned in the TWRP thread...
Prerequisites:
QDLoader_HS_USB_Driver (Google it and find)
Hex Editor (eg. HxD)
PC and some brain to understand....
Procedure:
Install the drivers and hex editor.
Clone this repo to PC - https://github.com/Naveen3Singh/BLUnlocker (Thanks to the dev )
Extract the firehose file from stock rom. (eg. "prog_emmc_firehose_8917_ddr.mbn" for TB-X304)
Boot into edl mode using key combo
or using adb
Code:
adb reboot edl
Check the port number in device manager and run " dump_devinfo.bat ".
Mention port number and full path to "*.mbn" file (eg. D:\where\every\it\is\prog_emmc_firehose_8917_ddr.mbn)
A file named " devinfo.img " will be dumped to the working dir. Edit it using an HEX editor as shown below.
{
"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"
}
Save the devinfo.img after editing and run " unlock.bat "
Reboot after success message.
Voila !! You have Successful unlocked the bootloader. Reboot to system by holding the power button.
EDIT (13/01/2020): After unlocking bootloader and restarting, if it asks for password, Reboot to recovery and format data...
Flash TWRP and Enjoy rooting...
PS: The same procedure can be done using QFIL tools (QPST)
Attached:
Firehose file of TB-X304F and TB-X304L (DONT USE ON OTHER DEVICES!!!)
Credits:
Thanks to the dev who wrote the code ( https://github.com/Naveen3Singh )
@hk96 (Myself)
Hit thanks if this helped....

Reserved !!!

Thank you very much! It worked perfectly!

Firehose file for X304L if anyone needs it

Hb20032003 said:
Thank you very much! It worked perfectly!
Click to expand...
Click to collapse
Great! I also have this problem...
Does unlocking in this way factory resets the tablet?
Is the "firehose" file version sensitive (i.e., if I use the S001016 file in a S001014 TB-X304F will I have any kind of trouble?)
Thanks!

njascgil said:
Great! I also have this problem...
Does unlocking in this way factory resets the tablet?
Is the "firehose" file version sensitive (i.e., if I use the S001016 file in a S001014 TB-X304F will I have any kind of trouble?)
Thanks!
Click to expand...
Click to collapse
After unlocking, when u Boot into system it asks for a password, even if u didn't set one to start with (atleast in my case).
So you need Boot into recovery and wipe data.
Short answer: yes, factory reset is necessary.
Regarding file version, I hav no idea... May be u can give it a try...

Hb20032003 said:
Firehose file for X304L if anyone needs it
Click to expand...
Click to collapse
Thanks...
Let me add this to OP, so that it is easier for others.

Can you please make a video tutorial? i am new to rooting and am unable to understand the instructions properly.

Chhayank_Sharma said:
Can you please make a video tutorial? i am new to rooting and am unable to understand the instructions properly.
Click to expand...
Click to collapse
May do it when i find time....
But there are many videos on the same procedure for other Qcom phones, you can get some hint from that.
If you are very new to this, i suggest you not to do, unless your are confident.

hk96 said:
May do it when i find time....
But there are many videos on the same procedure for other Qcom phones, you can get some hint from that.
If you are very new to this, i suggest you not to do, unless your are confident.
Click to expand...
Click to collapse
ok thanks.

hk96 said:
Regarding file version, I hav no idea... May be u can give it a try...
Click to expand...
Click to collapse
I was going to try it, but it's my daughter's tablet and she didn't let me do it... She is afraid of loosing some games' progress...

Nothing work for me

Eagle-no1 said:
Nothing work for me
Click to expand...
Click to collapse
May be you would have missed something....
This seems to work for most people.

hk96 said:
May be you would have missed something....
This seems to work for most people.
Click to expand...
Click to collapse
I got to work now, I had an old bad cable in use. Thank you.

hk96 said:
PS: The same procedure can be done using QFIL tools (QPST)
Click to expand...
Click to collapse
How? I watched a video and I can load the mbn but I don't know what to put in the xml thing box. I tried doing the method steps but it says Failed to write hello response back to device Did not receive Sahara hello packet from device

Nevermind I got it. As you can see by my signature I haven't done anything like this in many years.

Jakeup96 said:
Nevermind I got it. As you can see by my signature I haven't done anything like this in many years.
Click to expand...
Click to collapse
could you explain how you did it pleasssee

Jakeup96 said:
Nevermind I got it. As you can see by my signature I haven't done anything like this in many years.
Click to expand...
Click to collapse
Haha... Everything happens gradually...
rustyrust said:
could you explain how you did it pleasssee
Click to expand...
Click to collapse
I think, the instructions are crisp and clear as possible...
Can u tell where u got stuck ??

Work! You're GENIUS

hello,
I already root some device but here I'm stuck because I don't find the port number in device manager :-( drivers installed and "lenovo tab4 10" displayed in device manager. in properties I have : port_#0002.hub_#0005
I tried use 0002 or 0005 as port number but the .bat script failed each time. do I have correct port number ?
[EDIT] I have "failed to write hello response back to device" message and my tablet is in FFBM Mode.
[EDIT] in FFBM mode, my device is recognized in device manager (but i'm not sure to find the correct port and the script don't work) and in FastBoot Mode (first menu), my device seems to be not recognized in device manager. I guess that the script must be launched in this mode but I miss a driver. I install "adb drivers" + QDLoader-HS-USB_Driver_64bit_Setup drivers. What do I miss ?

Question OnePlus 10 Pro - QDLoader HS-USB - EDL Test Point [9008] MSM

Hello
The test point on this phone was shared by me for the first time on the internet. But there is no software available to install it. So my phone is still dead.
9008 usb Requirements to establish a connection:
- Disconnect the battery
- Plug your cable into the phone
- Connect the other end of the cable to the computer when short-circuiting the marked area.
- If the drivers are installed, the connection will be successful.
{
"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"
}
OnePlus 10 Pro EDL Test Point HS-USB QDLoader 9008
This guide will make you aware of the EDL Test Point on your OnePlus 10 Pro that could be used to boot your device to EDL Mode for unbrick.
www.droidwin.com

I found drivers on net. check if it may helpful.but it was described for OP9
QDLoader HS-USB Driver_64bit.exe | by Droidwin for Misc. Software & Hardware Resources
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
androidfilehost.com

Metromas said:
Hello
The test point on this phone was shared by me for the first time on the internet. But there is no software available to install it. So my phone is still dead.
9008 usb Requirements to establish a connection:
- Disconnect the battery
- Plug your cable into the phone
- Connect the other end of the cable to the computer when short-circuiting the marked area.
- If the drivers are installed, the connection will be successful.
View attachment 5649009
Click to expand...
Click to collapse
contct me i will fix your phone if software problem +992919474848 whatsapp only

mustafa.faiz said:
contct me i will fix your phone if software problem +992919474848 whatsapp only
Click to expand...
Click to collapse
How do you plan to solve it? Share it here. no msm tool available for gen 1 processor yet not available in the market. any box device is not working either.

Metromas said:
How do you plan to solve it? Share it here. no msm tool available for gen 1 processor yet not available in the market. any box device is not working either.
Click to expand...
Click to collapse
Post in thread 'MSM TOOLS' https://forum.xda-developers.com/t/msm-tools.4465229/post-87119213

Metromas said:
How do you plan to solve it? Share it here. no msm tool available for gen 1 processor yet not available in the market. any box device is not working either.
Click to expand...
Click to collapse
You are wrong. There are msm tool. You just cannot use it since you don't have a OnePlus login

g96818 said:
You are wrong. There are msm tool. You just cannot use it since you don't have a OnePlus login
Click to expand...
Click to collapse
Yes, the reason I can't revive my phone is because we can't log in.

Metromas said:
Yes, the reason I can't revive my phone is because we can't log in.
Click to expand...
Click to collapse
Can't log in is different than it is not available. It IS available, but you aren't allowed to use it.

g96818 said:
Can't log in is different than it is not available. It IS available, but you aren't allowed to use it.
Click to expand...
Click to collapse
I wonder when there will be a solution to this damn issue. I had to open a device that I never wanted to open..

This friend ran the software and recovered the phone but it does not give any information.
@rohit41u

Mod Edit: Quoted Post Deleted
You're referring to the MSM tool and a techs log in? If you're a OnePlus tech you're going to get fired, if you're not then what exactly are you selling??? It's a free tool, you've just keylogger stolen the details, nothing more.. trying to make money off people ?? That's shocking behaviour, genuinely awful..

{Mod Edit: Quoted Post Deleted}
Either way buddy, you can't sell usage of a free tool, certainly not promote it... You also made it sound like you were the one selling it as a "service"
Perhaps be more specific when you explain things...
To be clear, anybody selling the use of the MSM tool is a tool themselves.

So, there's only one guy who's selling the Msm login info it seems.
I wonder how oneplus would react if they found out. Wonder if an email over there would do anything about this fool.... But probably not.

Metromas said:
Hello
The test point on this phone was shared by me for the first time on the internet. But there is no software available to install it. So my phone is still dead.
9008 usb Requirements to establish a connection:
- Disconnect the battery
- Plug your cable into the phone
- Connect the other end of the cable to the computer when short-circuiting the marked area.
- If the drivers are installed, the connection will be successful.
View attachment 5649009
Click to expand...
Click to collapse
Hi, how did you figure out the test point? My Realme GT 2 PRO is dead bricked too, but i am not sure which are the correct test points:

Only the msm tool login will not do the trick. For the MSM Tool to work it need a file with the extension .ops, currently I could only find the .ofp file for oneplus 10 pro.
So I'm only wating for that to bring back my device.

ColorOS MSM tools always require internal account to log in. As OnePlus moves to ColorOS as its codebase since Android 12, free MSM tool (like with pure OxygenOS before) no longer exists I'm afraid.
I cannot find any free OxygenOS 12 MSM tool for any devices

nguyenlucky said:
ColorOS MSM tools always require internal account to log in. As OnePlus moves to ColorOS as its codebase since Android 12, free MSM tool (like with pure OxygenOS before) no longer exists I'm afraid.
I cannot find any free OxygenOS 12 MSM tool for any devices
Click to expand...
Click to collapse
And your won't make. They've locked that down.
Unless you run
a keylogger and take it!

dladz said:
And your won't make. They've locked that down.
Unless you run
a keylogger and take it!
Click to expand...
Click to collapse
I took a brief look into it over the weekend, some stuff is tied to the login like important setup files get streamed in to the tool. But it all looks like, if someone had a login, they could cache that info and crack it that way. Just needs the setup/flashing instructions from server basically. Would take longer to manually reverse their proprietary format.

Alright then, maybe we should look at this a different way. How would we be able to get a remote session with oneplus/ a technician?
Clearly it's possible as that one loser did it. It's just how he did it.

Ph0nysk1nk said:
Alright then, maybe we should look at this a different way. How would we be able to get a remote session with oneplus/ a technician?
Clearly it's possible as that one loser did it. It's just how he did it.
Click to expand...
Click to collapse
The easiest way used to be to reach out to support and tell them that your phone did an update and it won't boot into the system anymore. Then they would set up a remote session to flash your phone. The more difficult part at that point was you needed to set up a keylogger on your computer and run it when they do it and then disconnect before they can delete the files. If you feel comfortable doing that, then no problem. I wouldn't want to set up a keylogger on my own computer, so would have to either run a VM that I can actually get into EDL with or a clean set up just for that purpose. Either way, it's possible and hopefully someone is able to do it. The good part is we have the MSM for each device already, just need to crack it so we can freely use it as needed.