Related
IF THIS HAS BEEN SOLVED SOMEWHERE PLEASE TELL ME ASAP
sorry this is first post. Cheers
Hello XDA!
man ive nervous to post..
BUT i have come a null/null IMEI reading after a CM10.1 bootloop issue and trying to flash a new CM.
I have been a XDA follower for about 9 months but I have never needed to post for anything, as you have carried all of the lords answers. :angel:
I have done, stock firmware reset, Param bin, wiped all done it again. etc etc.
Many a conclusion has led me to probably a service repair centre.
I believe one option will still work for my IMEI restore but my phone comes up with a command that makes no sense.
Any help would be appreciated.
I am currently using QPST Configuration to write my IMEI back to my phone.
I have got these programs http://forum.xda-developers.com/showthread.php?t=1804117
Aswell as another handy IMEI converter to make sure my IMEI HEX conversion correct. (sorry cannot link. cannot find)
I have been using QPST and can follow all steps, except my phone WILL not show on on active phones.
I have reinstalled drivers and followed all necessary steps.
I have tried it in recovery mode also in QPST and no active phone still.
I believe i can get this to work, just need it to recognize my phone, and ill write the IMEI and hopefully..
Voila.. i can call the GF and tell her to chill. :good:
IS RNDIS different to RNMET? (how big of an impact will this play on the process)
In qualcomm settings i get "RNDIS + DM + MODEM" but i do not get "RNMET + "
SOLVED:FLASH PERSEUS KERNEL AND CALL GIRLFRIEND
samsung i9305
Unitized said:
IF THIS HAS BEEN SOLVED SOMEWHERE PLEASE TELL ME ASAP
sorry this is first post. Cheers
Hello XDA!
man ive nervous to post..
BUT i have come a null/null IMEI reading after a CM10.1 bootloop issue and trying to flash a new CM.
I have been a XDA follower for about 9 months but I have never needed to post for anything, as you have carried all of the lords answers. :angel:
I have done, stock firmware reset, Param bin, wiped all done it again. etc etc.
Many a conclusion has led me to probably a service repair centre.
I believe one option will still work for my IMEI restore but my phone comes up with a command that makes no sense.
Any help would be appreciated.
I am currently using QPST Configuration to write my IMEI back to my phone.
I have got these programs http://forum.xda-developers.com/showthread.php?t=1804117
Aswell as another handy IMEI converter to make sure my IMEI HEX conversion correct. (sorry cannot link. cannot find)
I have been using QPST and can follow all steps, except my phone WILL not show on on active phones.
I have reinstalled drivers and followed all necessary steps.
I have tried it in recovery mode also in QPST and no active phone still.
I believe i can get this to work, just need it to recognize my phone, and ill write the IMEI and hopefully..
Voila.. i can call the GF and tell her to chill. :good:
IS RNDIS different to RNMET? (how big of an impact will this play on the process)
In qualcomm settings i get "RNDIS + DM + MODEM" but i do not get "RNMET + "
SOLVED:FLASH PERSEUS KERNEL AND CALL GIRLFRIEND
Click to expand...
Click to collapse
which rom u flash i having i have been googling for and tried all th steps and solution can u help me it would kindful
Before I start, please take your time and read all of this. I would be very grateful if someone can help. Ok, so I made a post on 15th November - http://forum.xda-developers.com/lg-l90/help/d405n-completely-hard-bricked-t3249565 asking for help, going in detail asking how I could fix my phone. Seems like it's a mess, so here is a cleaned version.
Information about my phone:
LG D405n L90
Root
Lollipop 5.0.2
Android version (I forgot, 4.0.4 I think)
Carrier (Who I have a contract with) is Virgin Media (Service is Virgin Mobile)
Screen only shows if the battery while on 0% (Just about to die) or if the phone is plugged into the charger or PC without the battery in.
Notice: I didn't have a computer available at the time to do all of the below, so I tried it all via phone.
I wanted Cyanogen 12 ROM. I apparently needed a custom recovery to flash it. So I tried TWRP (I forgot which version). I tried installing it but kept getting an error after rebooting, but I could turn my phone off and back on and it'd be back to normal. The error said something about wiping the SD and gave me an email address to email a code. I Googled it and saw that my bootloader was apparently blocking it. I followed an XDA tutorial stating it could unblock the bootloader. I followed it correctly which claimed it was for all LG L90 variants. This is what bricked my phone.
Download Mode, Recovery Mode and normal boot don't work. When I plug my phone into the computer, it says 20.4MB free of 63.9MB. Now that's wrong. I believe my phone is 4GB of internal storage. There is 2 folders. "verinfo" and "image". Inside "verinfo" is a text document named "ver_info" with "M8626AAAAANLYD1338.1" inside it. Inside "image" is 76 random files.
In Device Manager, under Ports (COM & LPT) is my phone, "LGE AndroidNet USB Serial Port (COM3)". I do have the recovery.img and kernel.img files before it was bricked. I tried LG Flash Tool 2014, I leave "Select Type" as "CDMA", "Phone Mode" as "DIAG", and "Reset Time" as "33000". I select the Lollipop 5.0.2 KDZ file, and select "CSE Flash". It goes to the third step, "Upgrading Your Phone", and freezes at 4% "S/W Upgrade is in progress".
The last thing I want to do it send it into repairs, or even JTAG it. If anyone can help any further, I will not be able thank you enough.
Did you try this step by step? Worked fine for me
http://forum.xda-developers.com/showpost.php?p=61808443&postcount=9
Im experiencing just the same problem, except for that, the LG TOOL freezes at 15% with "Problem with Connection between PC and Phone" . It still reacts like OP said, can anyone help please? I think im lost.
Mpidemie said:
Did you try this step by step? Worked fine for me
http://forum.xda-developers.com/showpost.php?p=61808443&postcount=9
Click to expand...
Click to collapse
Thank you for the referral. It worked.
My phone was bricked and I restored it following this tut ( http://forum.xda-developers.com/showpost.php?p=62405939&postcount=138 ). Now the phone is turned on normally, but I have this strange thing:
My phone number
Unknown
IMEI
0
IMEI SV
00
I have also this warning: Current version is not available for user. Can't find matched cust for NT-code mcc/mnc, subset.
How to fix?
BlackStorm94 said:
My phone was bricked and I restored it following this tut ( http://forum.xda-developers.com/showpost.php?p=62405939&postcount=138 ). Now the phone is turned on normally, but I have this strange thing:
My phone number
Unknown
IMEI
0
IMEI SV
00
I have also this warning: Current version is not available for user. Can't find matched cust for NT-code mcc/mnc, subset.
How to fix?
Click to expand...
Click to collapse
Same thing happened to me after I unbricked my device using the exact same tutorial. However, even with IMEI 0 I can still make and receive calls and text messages. But I'm not sure if I should leave my device like this. If someone has any solution to provide I would be very grateful! I hope it doesn't involve flashing any ROM again cause I'm really afraid that I may brick my phone again ...
Hey guys, I had exactly the same problem. I tried different things including flashing various Roms and Bootstack, but nothing seemed to work. Since I’ve been searching for a solution quite a while, I now have the honor to help you out and everyone with an L90, who stumbles upon the same issue.
First of all, I made a backup of my EFS, so that I could restore the state my phone was in (IMEI=0, but working baseband). You can do that easily with TWRP (thx to shoxxy . By the way, this is something which we all should have done beforehand. It would have been much easier to restore our IMEIs.
But don’t worry, if you follow the instructions in this video (https://www.youtube.com/watch?v=nwzgs1Cmr9k) you should be able to get your IMEI working again. For those, who feel more comfortable following written instructions I copied the following procedure using this thread (http://forum.xda-developers.com/showthread.php?t=1960918) as a model and edited them a little to the way it just worked for me.
Do this on your own responsibility! And better double-check with the video our other threads.
Before you start:
Download this package (http://www.mediafire.com/download/figdbxb75j5kyry/package.rar), it belongs to the user who made the video on youtube (PremiumRepair).
Make sure your phone is rooted and USB-Debugging is enabled (http://forum.xda-developers.com/lg-g3/general/guide-root-lg-firmwares-kitkat-lollipop-t3056951)
Procedure :
Install Drivers. Either you use LG Support Tool or download them directly. For me the LGUnitedMobileDriver+3.14.1_ML_WHQL.exe worked just fine. Don’t forget to uninstall old drivers or you could run into problems.
Install QPST v2.7.378. Microsoft Visual C++ 2005 Redistributable is a prerequisite, just confirm it.
Plug your device into your PC (USB port)
Run QPST Configuration from your Windows Start menu. Switch to the second tab ("Ports") and choose "Add new port" (bottom left button). You should see a COM port associated with "USB/QD Diagnostic". Select it, then press Ok. You can close the QPST Configuration window now.
Open Windows Explorer and browse to "C:\Program Files\Qualcomm\QPST\bin" (or wherever you installed QPST) and launch RF_NV_Manager.exe. In RF NV Manager, Go to "Settings / Comport". You should see your COM port in the dropdown box. Select it, then press OK.
Go to "File" and choose "Read from phone". RF NV Manager will read all NV items from the phone. Now if you see item #550, you will be able to alter it (see below). If you can’t find it, go to “File” and choose “Read supported RF NV Items”. If you still can't find it, there is a way to create it. Take a look at the thread I linked to.
Now comes the critical step of altering the IMEI. Select item #550 and you'll see 9 boxes on the right, a "Write NV" button and an "Hex" checkbox. Check the "Hex" checkbox.
Now, you'll have to enter the IMEI in the 9 boxes in a very specific way. The easiest way is to use the IMEI converter (for other method see linked thread). Put your IMEI in, convert it and put the digits in the boxes (two number per box).
Now you can then press "Write NV" to write the IMEI value to your phone.
Once done, unplug the device, and reboot it. Now you IMEI should be changed. If it’s not your number, take a look at the step seven again and check the video.
Please give a feedback, if it worked for you (incl. Details about your device, ROM, etc.) so that other users can profit from it. Thanks
Edit: @ BlackStorm94 - Don't worry about the warning. It will vanish if you install a different ROM.
I'm stuck at step 6. When I click Read From Phone, I get an error which says that my phone is not present. Also, on QPST Configuration, even tho I have set the Port to the one my phone appears, under Phone it says No Phone ... I guess my phone isn't recognized for some reason. Do I need to root it before I do this? I hope not because I don't really want to mess with it after the hard brick
Lazgeor said:
I'm stuck at step 6. When I click Read From Phone, I get an error which says that my phone is not present. Also, on QPST Configuration, even tho I have set the Port to the one my phone appears, under Phone it says No Phone ... I guess my phone isn't recognized for some reason. Do I need to root it before I do this? I hope not because I don't really want to mess with it after the hard brick
Click to expand...
Click to collapse
Yes, your phone needs to be rooted. This solution for rooting works great for me: http://forum.xda-developers.com/lg-g3/general/guide-root-lg-firmwares-kitkat-lollipop-t3056951
mhikel said:
Yes, your phone needs to be rooted. This solution for rooting works great for me: http://forum.xda-developers.com/lg-g3/general/guide-root-lg-firmwares-kitkat-lollipop-t3056951
Click to expand...
Click to collapse
So, I rooted the phone successfully, but the phone is still not recognized by QPST Configuration or RF NV Manager. My pc recognizes the phone and I can do everything properly, but these programs say that there is No Phone ... I don't know what to do ...
mhh, that sounds like a problem with the drivers. Did you uninstall all the drivers (incl. Qualcomm drivers) from your PC? And have you installed the official LG drivers for our devices (for example from the link in this post: http://forum.xda-developers.com/showpost.php?p=62405939&postcount=138) Try another PC if it still doesn't work
mhikel said:
mhh, that sounds like a problem with the drivers. Did you uninstall all the drivers (incl. Qualcomm drivers) from your PC? And have you installed the official LG drivers for our devices (for example from the link in this post: http://forum.xda-developers.com/showpost.php?p=62405939&postcount=138) Try another PC if it still doesn't work
Click to expand...
Click to collapse
I'm going to try on a new computer tomorrow afternoon and I'll let you know how it went. I uninstalled all drivers associated with my phone on my computer and after reinstalling them I still got no results. I guess I may have confused it So that's why I'll try on a new one. Thanks for your help
Hello, sorry for the late reply. I just wanted you to know that even though I tried with another computer, my phone was still not recognizable. It doesn't really matter tho, cause even with the IMEI 0 I still have service and it works normaly for about a month now. If you have any solution then I would like to try it, but if not then it's okay. Thanks for your time
No worries! You do have USB-Debugging enabled, have you!? I mean you probably needed to do this for rooting. But if you haven't done it yet, that's probably the problem. Enable USB-Debugging like this (Go to Settings > General > About phone > Software information, tap Build number seven times and then go to Settings > Developer options and turn on Usb debugging) (copied from http://forum.xda-developers.com/lg-g3/general/guide-root-lg-firmwares-kitkat-lollipop-t3056951)
[/COLOR]
mhikel said:
No worries! You do have USB-Debugging enabled, have you!? I mean you probably needed to do this for rooting. But if you haven't done it yet, that's probably the problem. Enable USB-Debugging like this (Go to Settings > General > About phone > Software information, tap Build number seven times and then go to Settings > Developer options and turn on Usb debugging) (copied from http://forum.xda-developers.com/lg-g3/general/guide-root-lg-firmwares-kitkat-lollipop-t3056951)
Click to expand...
Click to collapse
Yeah yeah, I had USB Debugging enabled every time I plugged my phone into both of my PCs. But I don't think that's the reason this tutorial isn't working on my phone. When I unbricked the device, I had to use the L90 D405 loader.img in order to reflash the bootloader and recovery. But my phone is the d405n model, and that's the ROM I installed to it. So the phone now thinks that it is the D405 but the ROM I have installed is the one for d405n. I hope you understood this cause I know it's a bit weird I see options to activate NFC but I never use it so I can't tell you if it works. However I can activate it properly. Anyway, about the IMEI, as I told you, it basically works without problems even with 0 because I think that my service provider doesn't block anybody except someone reports the device as stolen. If you have any further solutions then let me know but if not the don't worry, I'm okay!
Lazgeor said:
But my phone is the d405n model, and that's the ROM I installed to it. So the phone now thinks that it is the D405 but the ROM I have installed is the one for d405n.
Click to expand...
Click to collapse
Ah, that makes sense. Flashing the right bootstack as described here (http://forum.xda-developers.com/lg-l90/development/bootstack-kk-l-l90-t3118632) could maybe help you (I haven't tried the one for D405n myself but it's supposed to stable). On the other hand: You probably installed a .kdz (ROM) with the correct Bootstack for your D405n included. ...So I don't think it'll bring back the IMEI or change anything. I'm running out of ideas, sry!
mhikel said:
Ah, that makes sense. Flashing the right bootstack as described here (http://forum.xda-developers.com/lg-l90/development/bootstack-kk-l-l90-t3118632) could maybe help you (I haven't tried the one for D405n myself but it's supposed to stable). On the other hand: You probably installed a .kdz (ROM) with the correct Bootstack for your D405n included. ...So I don't think it'll bring back the IMEI or change anything. I'm running out of ideas, sry!
Click to expand...
Click to collapse
It's okay I don't want to bother you any further. I'll buy a new phone soon anyways and since I'll give this one to my small brother, I don't think he'll really worry if his IMEI is 0 If at some point this device gets blocked by a service provider then I'll start searching for ways to fix it again. That bootstack page you mentioned seems useful. I'll try that if I do have any problems. Thank you very much for your help
That sounds reasonable! You are really welcome If you still need help just post here again. Although I have no other ideas at the moment someone else might. If you felt supported here I'd really appreciate the thanks! button. Yeah, you are right, the bootstacks supplied by Xemidra are of great value for our LG L90.
mhikel said:
That sounds reasonable! You are really welcome If you still need help just post here again. Although I have no other ideas at the moment someone else might. If you felt supported here I'd really appreciate the thanks! button. Yeah, you are right, the bootstacks supplied by Xemidra are of great value for our LG L90.
Click to expand...
Click to collapse
Update: I actually fixed it I know I told you that I would leave it as it is for now, but today I had nothing to do, so I decided to try my best and fix it. What I did was, as the post you told me said, I had to install the Kit Kat bootstack and the easiest way to do that is by flashing the Kit Kat rom. So I downgraded to android 4.4.2 using the stock rom I found on another post, and then I used your tutorial on the Kit Kat version. This time I was able to pass step 6 because my phone was getting recognized properly. I also didn't needed root access after all, since the new rom was just installed and it worked. After finishing the tutorial and restarting the phone, my IMEI was back! Then I upgrated my phone to the lollipop version, and when the upgrade finished, my IMEI was still there. So now I'm in lollipop with a working IMEI. I'm so thankful to you now, thank you very much for helping me and providing me these useful tutorials. I really appreciate it
Wow, that's just great!=) congratulations, you can be proud! Happy for you, that was quite an issue. You are welcome=) Well, someone from this forum helped me out, when I seeked for help and I am happy to give something back. Thank you for sharing your solution! That should be helpful for the next one stumbling over this problem. Enjoy your completely restored phone!=)
Like the topic says, my ZB551KL Zenfone Go won't register network operators and i suspect it's because the IMEI of the phone is 0 after applying official update. I've tried to Root the phone by downgrading to version WW_V13.2.8.13 and installing KingRoot and using Xposed IMEI modules but this fuxed up the phone and sent it into a bootloop. So i reinstalled the WW_V13.2.8.13 firmware again (the only firmware that KingRoot will work on, so basically the only way to root the phone) and rooted the phone again and tried to open the diagnostics port through adb shell, but when i execute the command: "setprop sys.usb.config diag,adb" it says setprop: not found.....so i am guessing i can't open the diagnostics port this way. And Xposed IMEI changer won't work cause Xposed fux up my phone into a bootloop.
So if anyone has any idea how i could change my IMEI back to what it originally was i am all ears. I was reading something about using a HEX editor, but i don't know how to get the IMEI files out of the phone or how to write them back into the phone.
And yes i've tried installing every official firmware, factory reset many times etc.... IMEI is 0 until i somehow change it myself. And when i do my SIM cards will be able to register on the network again. So any help is very much appreciated.
Honestly, they should just ship android with rooting options. Rooting newer devices is a huge pain in the neck right now.
This device is just downgrade as someone posted before and use kingroot, the problem is to enable diag port.
How we can root zb551kl
same problem here.. pls help
dbfonseca said:
This device is just downgrade as someone posted before and use kingroot, the problem is to enable diag port.
Click to expand...
Click to collapse
yep enable diag port take the hell out of me
i enabled diagnotic mode
eyobaaa said:
yep enable diag port take the hell out of me
Click to expand...
Click to collapse
how to recover imei from zero ?? i enabled diagnostic mode on this device
Basically you have to boot to fastboot then flash CSC firmware (also called RAW firmware) to enable qualcomm diag port.
Note that there are 2 kinds of this: 1 is the kind that connects via QDLoader 9008/QFIL to recover from hardbrick, and one that installs a very raw form of android and enables the diag port. You need the latter. Since I don't have the files anymore, you basically run this bat script file that connects via fastboot and hot-boots its own kernel that allows the diag port.
Then use this program called FactoryTool_WriteIMEI_v1.0.2 (Factory_tool_wingtech_v1.0.2.0.exe) to write the IMEI (since official qpst dont support dual Sim). You may need to fire up QPST/QFIL to get a proper com port for the software to work. Then flash first old firmware and you're good to prevent it getting corrupt again.
---
Problem is that this seems to be a symptom of a failing board since ever since the LCD started to flicker when in battery mode and OK when USB is plugged in. Baseband and IMEI becomes corrupt again when you update your system. Also periodically phone shuts down and becomes a 9008 device (hardbrick) but also comes back. Left it alone for days and it was fine after but problem came back after trying a game (solder cracks?) Will try to reflow the motherboard.
May I ask if you changed your LCD? This started happening to mine when I installed a system update after replacing the LCD+digitizer. It seems the phone is downloading the Chinese software update since it detects the (chinese?) panel and installs an incompatible Chinese modem baseband firmware. Upgrading to latest downloadable firmware also corrupts the IMEI slowly (Sim 1 first then Sim 2).
Hello guys, I'll try to explain what happened giving just a few context that may help give me some right direction to recover the user data that were in the phone.
As this thread got longer than I expected, summarising:
Moto G XT1033 drained battery, got into bootloop, only fastboot was working, couldn't get into recovery mode ("boot up failed"). When I tried to replace battery, after power on it's now bricked (as "qhsusb_bulk" in PC). My main goal, save user data (whatsapp folder mainly), to flash and restore Android.
Whole situation detailed, what happened:
I have a Motorola Moto G 16GB Music Edition Dual SIM XT1033 (Music edition) 2014, sold in Brazil. It was working for all these years fine, avoided upgrading Android KitKat from 4.4 because it just worked fine. In past months I noticed the battery holding less and less charge, but as I intended to buy a new phone soon I didn't care.
Unfortunately, couple days ago I heard the sound of notification "low battery... powering off". Then I plugged the charger cable and waited some time, after that, I thought it would just boot up normally, it showed "M" loading screen, with the animation etc, but it went to black screen and loop to loading screen again and again.
I tried to hold power and volume down, it went to fastboot, and when I tried start "recovery mode" but it would just say "boot up failed".
I searched for threads and people who had issue like mine and in fact, I found someone who described exactly the same problem I had, user named @ravibhat here: https://forum.xda-developers.com/moto-g/help/moto-g-bootup-problem-recovery-mode-t3122492
While he didn't say he was able to fully flash his smartphone and get it back working, he said he was able to recover all his user data. I was really trying to follow his steps to at least, recover all user data, BUT, before that, my Moto G got hard bricked.
As I have another Moto G XT 1033, the exact same model as this one, but with a working battery, I thought it would be plausible to replace the battery so I could have more safety when fixing the phone, but it didn't work as that. Instead, after I disconnect and reconnect the battery, the Moto G is now hard bricked, as it doesn't boot up anymore, not even holding power + volume buttons, holding for 60s or 120s, none, nada. Rarely, the LED light blink once, nothing more. I connected to PC and it recognized as "qhsusb_bulk", after disconnecting and connecting the phone back to Windows 7, it automatically tried to install drivers and now it would just show "Qualcomm HS-USB QDLoader...." in device manager .
Now I have two issues, first, make it come back to state where I could open fastboot. Second, try to dump/save all user data, to then make a total flash/factory reset to see if I can get it working again.
After searching for hard brick and "qhsusb_bulk", I found this thread (https://forum.xda-developers.com/moto-g/help/how-to-revive-hard-bricked-moto-g-t2833798) and this (https://forum.xda-developers.com/moto-g/general/guidy-to-unbrick-hard-bricked-moto-g-t3875035) that says it will recover from it, but it didn't mention IF IT WILL compromise or delete all user data. Will it?
I don't want to just go and try a bunch of (possible danger) commands and guides without having some experienced people giving advices on how to perform actions, or even if it's possible to "make some backup" of current situation, "copying whole partition", etc, before installing and flashing anything.
Device INFO:
Android version was 4.4. No Root. Bootloader is LOCKED. No customizations.
ADB Debugging state is unknown, probably it was just the default value.
What I want:
I want to get a copy of all my internal storage data, eg: WhatsApp folder, etc. Better if I could get whole storage image and just flash OS and boot loader to get back as it was...
Trying to flash it in any way that causes data loss would be my last option, but @ravibhat who had same issue few years ago couldn't even get it back working again.
What @ravibhat found out:
He thought bootloader UNLOCK would wipe all internal memory user data, but he did it and still could get all files using TWRP 2.8.x.x.
"To root the phone, I’ll have to UNLOCK the Bootloader."
"ADB can be used to backup using PUSH, PULL (may or may not require Android USB Debugging enabled)": he couldn't get it to work using adb push/pull.
Please, I would really appreciate any help from anybody, also from following users @ravibhat , @lost101 , @Teddy Lo , @Kamin4ri , @oversleeper , @jdawc7 , @sd_shadow , @SahilTech , @liveroy , @bouba148 , @bejunk , @Wolfcity, @skad00sh, @FabioSan.
After searching for hard brick and "qhsusb_bulk", I found this thread (https://forum.xda-developers.com/mot...oto-g-t2833798) and this (https://forum.xda-developers.com/mot...oto-g-t3875035) that says it will recover from it, but it didn't mention IF IT WILL compromise or delete all user data. Will it?
Click to expand...
Click to collapse
It should not delete the user data. I'm saying this out of logic though, I've never tested it.
Technically the Motorola qboot utility will ripristinate the bootloader only, without modifying any other area of the memory.
oversleeper said:
It should not delete the user data. I'm saying this out of logic though, I've never tested it.
Technically the Motorola qboot utility will ripristinate the bootloader only, without modifying any other area of the memory.
Click to expand...
Click to collapse
Thanks @oversleeper, I was a bit afraid because of the "blank-flash.bat" name.. but as I don't know of any other method of beginning this recovery other than unbricking using this qboot bat script, I will end up giving it a chance.
As I said before, Windows 7 auto installed the "Qualcomm HS-USB QLoader 9008" driver as soon as it recognized the "qhsusb_bulk". Do you think I should try to uninstall it and start from step 1 on this guide (https://forum.xda-developers.com/moto-g/help/how-to-revive-hard-bricked-moto-g-t2833798) installing the "Riff BOX JTAG drivers + Driver Signature Enforcement Overrider"?
Yes, I suggest that you install the driver's as advised in that old thread. Also, you will need to use the right qboot utility, for the right model and version of the bootloader that you have or it won't work. Unfortunately I can't help with that, you will need to search the internet and may luck be with you.