Related
Hi, so I was trying to follow this guide (I know that it's for I9305, but the procedure should work for I9300), but when I connect my phone to my PC, I get the message "USB device not recognized".
The devices manager lists the phone as "Unknown Device", the device status is "Windows has stopped this device because it has reported problems. (Code 43)" and the hardware Id is "USB\CONFIG_DESCRIPTOR_FAILURE".
I only have this problem when I put the phone in diagnostic mode ("RNDIS + DM + MODEM", "RMNET + DM + MODEM" or "DM + MODEM +ADB"). It works fine if I use the other modes.
I tried with various Samsung USB Driver versions (1.4.6, 1.5.09, 1.5.18 and 1.5.25) and roms (stock, omega and cyanogenmod, currently with stock 4.1.2), all with the same result. I'm using Windows 8 x64.
So, I wan't to use QPST but I can't, so any help would be greatly appreciated. If you need any more info just ask please.
Whatever you are trying to do that is for qualcom cpu
Basics read first.
http://forum.xda-developers.com/showthread.php?t=2344125
Critical you read the first two posts
JJEgan said:
Whatever you are trying to do that is for qualcom cpu
Basics read first.
http://forum.xda-developers.com/showthread.php?t=2344125
Critical you read the first two posts
Click to expand...
Click to collapse
Thanks so much, I didn't realize that my processor wasn't a Qualcomm.
Please, how did you solve this problem? I'm trying for hours and still is unknown device in diag mode! Help!
Unknown device (i9300 with 4.3 original rooted)
I'm in the same situation after I select: rmnet+dm+modem
Install and reinstall several version of usb driver, cable, port etc.. but when I select rmnet+dm+modem or option under my pc doesnt't install driver for it because it sees an unknown device
WHY?!?!?
Why are there no REAL helpful answers to these questions? Everyone is just saying "read this, or see that post..." but no real specific answers for fixes!!! I have been all over Google looking for a solution for this problem! I can get to the USBSettings menu on my 9300 by dialing *#0808#, but when I select RMNET+DM+MODEM, my computer no longer recognizes the device! Installing Samsung drivers did not help...my question is, does anyone know what drivers I need for Windows to recognize the phone?
Thanks!
~Jim
You are looking for an instant easy answer to a varied and complex problem, made worse by people who don't read or understand before they break things.
This long dead thread you resurrected is a case in point, just read the first two posts to understand how a situation is made worse by impatience.
Please Really Help
Same exact problem I am having I just dont seem to get what to do now.
I have a NOTE 2
jmaher1023 said:
Why are there no REAL helpful answers to these questions? Everyone is just saying "read this, or see that post..." but no real specific answers for fixes!!! I have been all over Google looking for a solution for this problem! I can get to the USBSettings menu on my 9300 by dialing *#0808#, but when I select RMNET+DM+MODEM, my computer no longer recognizes the device! Installing Samsung drivers did not help...my question is, does anyone know what drivers I need for Windows to recognize the phone?
Thanks!
~Jim
Click to expand...
Click to collapse
Hey Jmaher, did you ever get to solve this? Seems getting these RMNET+DM+MODEM Diagnostic usb settings recognized on PC COM Port is one hell of a job! Trying to get Note 3to work with QPST. Kindly respond bro...
I never did! I pretty much gave up. It was a customer's phone I was working on, so I just gave it back and told him we couldn't fix the issue.
Sent from my SM-N9005 using Tapatalk
thought id through my thoughts and troubles into the bag ...
ive got a troublesome phone, is a I9300 (so the international version) had the s5 sensation rom on it..
went odd, wouldnt run/install any apps etc (errors out with -54 i think it was) then week or so passed (as not got round to fixing it as it stillworked as a phone)
and after it went through a stage of switched it self off...
the batt went flat, and then hung on samsung logo...
after trying to sort it out, reflashing a backup, and then back to original ODIN files etc .. still hung, but would go to download and recovery with many compliants ..
after goose chasing them, got it down to just complaining about the /EFS
so after trying to fix this one, an nowt worked, i formatted /efs ... and yeah ! all boots !
so ive now got a "blank" efs, but a booting phone ! (but no network)
ok so in pretty much 100% of all tutorials in fixing a imei/efs problem it stems on putting phone into "diag or diagnostic" mode
which EFS Pro will do for you, or you can *#0808#
BUT i to get the "unkown" device too ..
and like the posters here all other options of modes work/install, but the programs for imei repair etc need diag mode
and from what ive read (the posts linked on the first couple posts here, and whats actually in those links)
suggest that either to "take it for repair" or talks about imei repair progs in diag mode with CDMA qualcomm devices, and CDMA devices are US devices
so i am lead to believe that as the I9300 being international version, doesnt actually have a "DIAG" mode, only CDMA US versions ? ! ? is THIS what your all hinting at but not saying ???
so thus no drivers work for it, and thus "unkown device"
and the only way is for a appropriate "box" that im thinking emulates, or works like diag mode !?
is there a way to force/flash diag mode for international s3's ?
am i even correct in these assumptions ??!!
---------- Post added at 06:31 PM ---------- Previous post was at 06:11 PM ----------
OmniSliver said:
Thanks so much, I didn't realize that my processor wasn't a Qualcomm.
Click to expand...
Click to collapse
thers NOTHING about qualcomm, and what it is and what isnt in phones in any of the quoted links
or anything related to CDMA
but am i presuming right what i said above, that the international version doesnt "have" a " diag" mode due to the type of processor used ?
miniminus said:
am i presuming right what i said above, that the international version (non qualcomm) doesny "have" a " diag" mode due to the type of processor used ?
Click to expand...
Click to collapse
I couldn't find any diag mode that worked. I had to send my phone to a repair shop that charged me around 20 USD.
Also, QPST (Qualcomm Product Support Tool) works only for phones with a Qualcomm processor.
not qualcomm
Im stuck at RMNET+DM+MODEM "Device not recognized", seems i need the driver for it. what can be done if the device is not a qualcomm CPU?
Model : GT-I9300T
jmaher1023 said:
Why are there no REAL helpful answers to these questions? Everyone is just saying "read this, or see that post..." but no real specific answers for fixes!!! I have been all over Google looking for a solution for this problem! I can get to the USBSettings menu on my 9300 by dialing *#0808#, but when I select RMNET+DM+MODEM, my computer no longer recognizes the device! Installing Samsung drivers did not help...my question is, does anyone know what drivers I need for Windows to recognize the phone?
Thanks!
~Jim
Click to expand...
Click to collapse
enable cp logging in recovery ....
volkan.akbulut said:
enable cp logging in recovery ....
Click to expand...
Click to collapse
you are the man. thanks, that worked like a charm.
sharky481232 said:
you are the man. thanks, that worked like a charm.[/QUOTE
please how did you enable cp logging in recovery
I currently use philz recovery
Click to expand...
Click to collapse
elprinz said:
sharky481232 said:
you are the man. thanks, that worked like a charm.[/QUOTE
please how did you enable cp logging in recovery
I currently use philz recovery
Click to expand...
Click to collapse
stock recovery had that option
Click to expand...
Click to collapse
95
sharky481232 said:
elprinz said:
stock recovery had that option
Click to expand...
Click to collapse
So what would be the solution for the custom roms? I have been looking all over the web, but noting so far.
I have gt-i9505 with Imperium LL Rom v13.0.
Click to expand...
Click to collapse
volkan.akbulut gave the solution. Follow these steps:
1. Turn off the phone
2. Enter Recovery Mode by holding Vol Up + Home + Power
Release the buttons when you see "Recovery booting" on the left-top corner.3. Use Vol Down button to select Enable cp logging and press Power
Now try to connect. Drivers will be installed.
Good luck.
volkan.akbulut said:
enable cp logging in recovery ....
Click to expand...
Click to collapse
THANK YOU... holy $%^&* i wish this was referenced in the OP on the front page (missed it on page 2 days ago).
S4 i9505 on win7 64, samsung driver 1.5.59.0 for use with QXDM
Hello Everyone,
I have a questions and hopefully some one can help me out here. My son has bricked my phone and I believe it is a soft brick... could be wrong. However, I need to find away too unbrick it.
I can get into hard reset with out issues. however with everything I do, I can't get into recovery what's so ever. The phone just hangs at the loading screen. I have talked to my son in order to find out what he did and this is exactly what he told me
He installed king root and attempted to replace-kinguser-with-supersu. However when he installed the application, it asked to reboot the phone. Well he rebooted the phone and now it is stuck at the loading screen and wont go any further than that. He also told me that he did not remove kingroot prior too the reboot. Please help! as I need my phone for work.
I am out of options on what too do. I would post the guide he used but I am limited due too the spamming regulations of the board.
Any one have an idea on how to unsoft brick this phone? I am all out of options as the only two options I have are hard boot and download mode.
Lunarman01 said:
Any one have an idea on how to unsoft brick this phone? I am all out of options as the only two options I have are hard boot and download mode.
Click to expand...
Click to collapse
According to the good people here on this thread http://forum.xda-developers.com/general/general/qa-metro-pcs-lg-k7-lgms330-t3331678 there is only a paid solution at the moment.
http://lg-firmware-rom.com/download...330-dll-for-lg-up-unbrick-lg-k330-with-lg-up/
if it is a lg k7 k330 (tmo) i followed this guide http://www.repairshopusa.com/phone/lg-k7-k330-unbrick-method/
Thank you for the information. However the lgup application does not recognize my phone. Indicates that the model is "Unknown"
Guess i am out of luck lol
Not uncommon. Sometimes you need to unplug and replug the device back in or close and reopen the program.
Thank you for the information. Does the USB debugging option need to be enabled because if it does, I don't think it is as the my computer does not recognize my device at all. Under computer, it shows as k7. However when I got into the device manager it indicated "LGE Android MTP device".
No. USB Debugging only works while booted into the system or recovery. You must be in Download Mode for the LG Up tool.
At this time, I am really frustrated as nothing is currently working at this time. Possibly because the phone just went under a hard reset. I have changed the port too 41 and ran the flash tool and that was not able too pick up my phone either. Also, I can't seem to get the lgup to work correctly as it's still not working correctly.
I have uninstalled the applications belonging too lg, rebooted and then reinstalled them and I still get the same thing. I have attached screen shots below. lgup does indicate the firmware I need, however I can't get too it lol
Message me I can fix your phone
Sent from my LG-K330 using XDA-Developers mobile app
Lunarman01 said:
At this time, I am really frustrated as nothing is currently working at this time. Possibly because the phone just went under a hard reset. I have changed the port too 41 and ran the flash tool and that was not able too pick up my phone either. Also, I can't seem to get the lgup to work correctly as it's still not working correctly.
I have uninstalled the applications belonging too lg, rebooted and then reinstalled them and I still get the same thing. I have attached screen shots below. lgup does indicate the firmware I need, however I can't get too it lol
Click to expand...
Click to collapse
If I remember right, you have to make it search for *.kdz otherwise it's looking for .tot files, which is why it's probably not seeing the firmware you need.
es0tericcha0s said:
If I remember right, you have to make it search for *.kdz otherwise it's looking for .tot files, which is why it's probably not seeing the firmware you need.
Click to expand...
Click to collapse
Yes you are correct. However the file that I have downloaded from the link below doesn't actually provide you with a kdz file. The file provided you the files that have been extracted from the kdz file, which are the (LGK330.dz) file
Ah, weird. Never worked on an LG that didn't use .tot, .kdz, or .bin files. I guess just search for *.dz and it should load according to the link the other guy put up.
peteypete206 said:
Message me I can fix your phone
Sent from my LG-K330 using XDA-Developers mobile app
Click to expand...
Click to collapse
Thank you peteypete206. You have really save my phone. This issue has been resolved.
Lunarman01 said:
Thank you peteypete206. You have really save my phone. This issue has been resolved.
Click to expand...
Click to collapse
i'm having same problem in device manager , LGE android mtp device (yellow triangle with exclamation) & LGUP says device unknown.
The phone is able to go in download mode. any help will be appreciated.
I have a hard bricked k7 (k330) CHIPSET MSM8909 qdload 9008 with no partition, the solution I found here was for LG G2 & G3 because the diag program has those chipsets, please I need help with this
peteypete206 said:
Message me I can fix your phone
Click to expand...
Click to collapse
How's it going man, I need your help I have a ms330 stuck in 9008 mode with an unlocked bootloader. Everything I've tried has failed and I'm stuck. I only owned this phone for 6hrs before I screwed it up any help will be appreciated!!
Hi guys!
I think I did something stupid while updating my XT1650-03 to Nougat.
What I did was manually flash stock nougat ROM (retbr) through fastboot, following the instructions within flashfile.xml, but, as I've read some bad things about the updated bootloader I stupidly decided not to flash it. The result is that it won't power up, even though I've tried: pressing power+vol. down; power; plugging the charger; fastboot commmands ( I was hoping it was just the screen that was off); to no avail.
I've noticed that when I plug the usb cable to the computer it plays that sound of connected devices.
Any suggestions? I'm probably going to have to take my device to authorised repair (off warranty, I know), but they usually take weeks to fix anything, so you guys are my best bet for now.
Thanks in advance!
martonto said:
Hi guys!
I think I did something stupid while updating my XT1650-03 to Nougat.
What I did was manually flash stock nougat ROM (retbr) through fastboot, following the instructions within flashfile.xml, but, as I've read some bad things about the updated bootloader I stupidly decided not to flash it. The result is that it won't power up, even though I've tried: pressing power+vol. down; power; plugging the charger; fastboot commmands ( I was hoping it was just the screen that was off); to no avail.
I've noticed that when I plug the usb cable to the computer it plays that sound of connected devices.
Any suggestions? I'm probably going to have to take my device to authorised repair (off warranty, I know), but they usually take weeks to fix anything, so you guys are my best bet for now.
Thanks in advance!
Click to expand...
Click to collapse
Don't even bother going to the service center. The same happened with my device and they refused to give me the warranty. Motorola voids it the moment you get the unlock code. So my device was dead for 3 months. And I fixed it few days back. The good news is that your PC is detecting the device.
I will post the solution with a new thread in few minutes.
Manish54 said:
Don't even bother going to the service center. The same happened with my device and they refused to give me the warranty. Motorola voids it the moment you get the unlock code. So my device was dead for 3 months. And I fixed it few days back. The good news is that your PC is detecting the device.
I will post the solution with a new thread in few minutes.
Click to expand...
Click to collapse
Thank you so much for your reply, it's very much appreciated! I didn't think anyone would reply that soon
I'll wait for your thread!
There ya go
https://forum.xda-developers.com/moto-z/how-to/guide-how-to-unbrick-moto-z-hardbricked-t3590133
So, I'm totally lost.
As I posted in the thread above, even though Manish54 has been very kind to help, that solution did not work for me, so I've been trying to find another way. The thing is, this issue is beyond my comprehension. I'm not new to flashing and stuff, but I am new to moto Z. I understand that I should've been more careful and also have read a bit more before starting to mess with a new device, so feel free to judge me .
For instance, I don't know what fsg.mbm, adspso.bin, BTFM.bin and oem.img are for, since my old phone didn't have those (or at least I didn't need to mess with those), and I also don't know it they're relevant to my problem. If anyone could point me to some info on that, it'd be greatly helpfull.
Besides that, I've found mentions to tools like qualcomm's BoardDiag and QPST QFIL, but I'm not really sure if they apply for my situation, or even if I can manage to adapt the guides I've found to work on the Moto Z.
Any help is very much appreciated!
Thank you!
Solved!
I managed to unbrick my phone.
If anyone needs it, the details are in the thread made by Manish54.
https://forum.xda-developers.com/mo...rick-moto-z-hardbricked-t3590133#post71876064
Is there any way to solve it ?
Hillterpty said:
Is there any way to solve it ?
Click to expand...
Click to collapse
Did you even read the posts?
Ajuda
martonto said:
I managed to unbrick my phone.
If anyone needs it, the details are in the thread made by Manish54.
https://forum.xda-developers.com/mo...rick-moto-z-hardbricked-t3590133#post71876064
Click to expand...
Click to collapse
Amigo tb estou com o meu morto, me ajuda, qual o modelo do seu.
https://uploaddeimagens.com.br/imagens/sem_titulo-jpg--9130
hard brick moto z
Manish54 said:
There ya go
https://forum.xda-developers.com/moto-z/how-to/guide-how-to-unbrick-moto-z-hardbricked-t3590133
Click to expand...
Click to collapse
hello friends, I'm with hard brick on the moto z xt1650-3
due to an update via ota, when my bootloader was unlocked I was in the android oreo (8.0), however I went back to 7.0, due to an update via ota, the device did not call anymore, I tried several blankflash and nothing, I am very annoyed at this, thinking of dropping my hand, I took some assists nobody can solve, I hope someone here can help me, at least inform me something that is useful to recover my cell phone.
my cell phone is still recognized as "qualcomm hs-usb qdloader 9008 (com3)
please join the telegram group:
https://t.me/motozz
Hey, my phone was dead two (brazilian xt1650-03), i spent three days struggling until i could bring him back. Thanks to the help in this forum. Your phone probably has the latest update opls27-76-51-7-july, so it must work:
first, you have to bankflash it with blankflash_OPL_27.76-51, its in the 30+ page topic tutorial here in this forum. Very important, must be in windows 7 or 8, with usb2.0
second, use this rom opls27-76-51-7-july-moto-z. it must work because its the last one. Its not brazilian, evething works fine but the netflix app didnt , but hey, at least our phone is alive again.
The secret is in the version of the firmware instaled before the brick, it must be the rom installed or latest to work
Not sure how to proceed here. I had a very recent twrp installed, flashed a new ota firmware update as I have successfully a couple of times, phone restarted to twrp, I decrypted, it flashed the firmware fine then went to restart.
And that's it, completely dead, battery was at least 50% charged.
I can't enter recovery, power button held for one minute does nothing, vol+ and power, nothing, vol- and power, nothing, vol+ and vol- nothing.
Plugging in my charger, nothing, plugging into a laptop and pc, nothing. Took the back off and disconnected the battery and left it over night, nothing.
Bootloader was unlocked and usb debugging enabled.
Anyone have any other ideas what I can try here?
Also tried bridging the contacts for edl mode with battery disconnected and plugged it into USB but nothing.
Very tricky to do this though as you need 4 hands and it's possible I'm not making contact on both pins, purchased a cheap edl/deep flash cable as a last resort, if that doesn't work then I think it is toast.
Does your device have a file you’d an flash in edl (Eg. Firehose)?
Arealhooman said:
Does your device have a file you’d an flash in edl (Eg. Firehose)?
Click to expand...
Click to collapse
I may have found a couple of resources but I'm unsure of the procedure, is there any chance you could provide me with some information, I'm stumped on how to proceed.
Johnnio said:
I may have found a couple of resources but I'm unsure of the procedure, is there any chance you could provide me with some information, I'm stumped on how to proceed.
Click to expand...
Click to collapse
From what I gathered you need to find a special “firehose” or like file that allows yout o flash it in edl. You seem to have gotten very very lucky because from a simple Google search, I found firehose files. They may or may not work.
https://support.hiunlock.com/index.php?a=downloads&b=file&id=1133 I found this, but I think it may cost money (I don’t want to make a acc, but from browsing the website, it seems it costs 20 dollars, which is a barbain for a device). You are lucky it exists at all though. I do not vouch for the file or site though. You should o research on how trusted it is.
Arealhooman said:
https://support.hiunlock.com/index.php?a=downloads&b=file&id=1133 I found this, but I think it may cost money (I don’t want to make a acc, but from browsing the website, it seems it costs 20 dollars, which is a barbain for a device). You are lucky it exists at all though. I do not vouch for the file or site though. You should o research on how trusted it is.
Click to expand...
Click to collapse
Thank you, I will have a good read and look at other sources.
I'd love to know how the hell this happened, had the device for years now and flashing with zero issues.
Johnnio said:
Thank you, I will have a good read and look at other sources.
I'd love to know how the hell this happened, had the device for years now and flashing with zero issues.
Click to expand...
Click to collapse
Yeah, must have amde a small mistake, or ahd a corrupt file
“EDL is an interface of Qualcomm chipsets, used to flash fastboot ROMs. It is used for unbricking purposes so it is allowed on many phones but it's been locked down on most recent Android models.
The screen will appear black and it will appear that the device is turned off, but to verify that this is not the case, we need the tools in EDL mode. The most famous is QFIL (Qualcomm Flash Image Loader), a proprietary software, but on GitHub there are many alternative open source projects.”
https://www.thecustomdroid.com/qualcomm-edl-mode-guide/ the beginning of this article explains edl mode very well
Arealhooman said:
https://www.thecustomdroid.com/qualcomm-edl-mode-guide/ the beginning of this article explains edl mode very well
Click to expand...
Click to collapse
Excellent, thanks again for your input.
Johnnio said:
Excellent, thanks again for your input.
Click to expand...
Click to collapse
Yep, reach out if you have more questions, and keep me updated with if you managed to save your device.
Arealhooman said:
Yep, reach out if you have more questions, and keep me updated with if you managed to save your device.
Click to expand...
Click to collapse
Will do
I am late here, but just want to add i also had same issue
And edl can be fix with xiaomi third party tools with little fee to provide you authorized rom flash to boot phone from edl
Hello! I have a bricked OnePlus Nord N200 5G with me, and I'm pretty sure I have tried everything at this point.
I mistakenly downloaded the N100 firmware files, namely XBL, ABOOT, and TZ and flashed them through fastboot, and came back to a nice looking brick on reboot.
MSM Download Tool or EDL should be able to save the phone, in theory, but even with the correct programmer, it won't take a flash of any kind. I have tried the global firmware, the T-Mobile firmware, tried Windows and Linux with QPST and EDL respectively, and can't get the phone to do anything.
Almost as if it is crashing halfway through firehose upload?
Would it be possible to short UFS through the board perhaps, maybe it's trying to crosscheck N200 files with N100? But PBL being in bootROM should take a flash with the correct programmer, right?
To be upfront about it too, if this phone is perma-dead, so be it. I have a lot of free time on my hands at the moment and wanted to try and revive it if possible. I'd appreciate anyone chiming in. Thanks!
do you have a screenshot of what the phone driver looks like in device manager when in EDL mode?
do you have a screenshot of what MSM download tool status looks like right before you click START?
AiM2LeaRn said:
do you have a screenshot of what the phone driver looks like in device manager when in EDL mode?
do you have a screenshot of what MSM download tool status looks like right before you click START?
Click to expand...
Click to collapse
I don't have any screenshots, however I installed the drivers correctly, phone on Windows shows up as Qualcomm 9008 COM Port. As for MSM Tool, I have tried messing with the SHA and lite and reboot options, to no avail.
I currently run Arch Linux, and bum family's Windows PC for flashing.
If you need any Linux screenshots, I have those.
have you tried a different USB cable?
different USB port?
and/or different computer?
AiM2LeaRn said:
have you tried a different USB cable?
different USB port?
and/or different computer?
Click to expand...
Click to collapse
Yeah, I have tried an Intel based Linux machine and a Ryzen based Windows machine, tried different cables, even made a DIY EDL cable where I short DAT+ with GND.
yea sounds like you been doing the right things, well im sorry but thats beyond my knowledge, sounds like you really did something unusual and changed up the wrong boot files, usually MSM download tools works. Good luck.
AiM2LeaRn said:
yea sounds like you been doing the right things, well im sorry but thats beyond my knowledge, sounds like you really did something unusual and changed up the wrong boot files, usually MSM download tools works. Good luck.
Click to expand...
Click to collapse
Thanks for the help either way. Maybe someone who has messed with EDL more than I will come across this with some new info...
DaKillaz98 said:
Thanks for the help either way. Maybe someone who has messed with EDL more than I will come across this with some new info...
Click to expand...
Click to collapse
out of curosity in windows devie manager is is EXACTLY saying "Qualcomm HS-USB QDLoader 9008 (COM)" or is it just saying exactly "Qualcomm 9008"?
another question: when you are in EDL mode what is showing on the phone screen?
It says Qualcomm HS-USB QDLoader 9008 (COM) exactly, I just couldn't think of how to type it off the top of my head.
Phone shows nothing, no vibrate, no screen. Doesn't boot or show any signs of life.
DaKillaz98 said:
It says Qualcomm HS-USB QDLoader 9008 (COM) exactly, I just couldn't think of how to type it off the top of my head.
Phone shows nothing, no vibrate, no screen. Doesn't boot or show any signs of life.
Click to expand...
Click to collapse
sounds like you pulled a number on it, good luck!
DaKillaz98 said:
It says Qualcomm HS-USB QDLoader 9008 (COM) exactly, I just couldn't think of how to type it off the top of my head.
Phone shows nothing, no vibrate, no screen. Doesn't boot or show any signs of life.
Click to expand...
Click to collapse
try this: https://github.com/bkerler/edl
it's an universal blankflash tool that allows you to flash every single partition individually.
WoKoschekk said:
try this: https://github.com/bkerler/edl
it's an universal blankflash tool that allows you to flash every single partition individually.
Click to expand...
Click to collapse
I've tried this tool,
Code:
edl --memory=ufs --debugmode --loader='/home/austen/Desktop/Phone Repair/0000000000515152_07b00c8737956b3d_fhprg_dre8t.bin' qfil '/home/austen/Desktop/Phone Repair/Firmware/extract/rawprogram0.xml' '/home/austen/Desktop/Phone Repair/Firmware/extract/patch0.xml' '/home/austen/Desktop/Phone Repair/Firmware/extract'
showed me that it is crashing halfway through the programmer upload. I get "Cannot receive number of program headers." when I send a bad programmer, as expected.
I made my own rawprogram0.xml and patch0.xml using the settings.xml to flash XBL and such, but didn't even get that far.
I'm going to try a clean Windows 10 VM, just to make sure this isn't a Windows 11 issue maybe.
DaKillaz98 said:
I've tried this tool,
Code:
edl --memory=ufs --debugmode --loader='/home/austen/Desktop/Phone Repair/0000000000515152_07b00c8737956b3d_fhprg_dre8t.bin' qfil '/home/austen/Desktop/Phone Repair/Firmware/extract/rawprogram0.xml' '/home/austen/Desktop/Phone Repair/Firmware/extract/patch0.xml' '/home/austen/Desktop/Phone Repair/Firmware/extract'
showed me that it is crashing halfway through the programmer upload. I get "Cannot receive number of program headers." when I send a bad programmer, as expected.
I made my own rawprogram0.xml and patch0.xml using the settings.xml to flash XBL and such, but didn't even get that far.
I'm going to try a clean Windows 10 VM, just to make sure this isn't a Windows 11 issue maybe.
Click to expand...
Click to collapse
you can also try a loader provided by the tool. it helped me to recover my Moto phone.
WoKoschekk said:
you can also try a loader provided by the tool. it helped me to recover my Moto phone.
Click to expand...
Click to collapse
That's the loader I used at first actually, I also tried one extracted from stock firmware, but no dice, trying a windows vm soon.