Related
I will explain how to set the device tampered back to "false" on the Wileyfox Swift.
Required:
7z
WFS.7z (https://drive.google.com/file/d/0B6Ge199bCD5_NF9RWGhVLVhxajA/view?usp=sharing)
Windows 7 or 8
Driver Signature Enforcement disabled
Step 1: Brick the device on purpose
Hold Volume Up button+Volume Down button while plugging in USB
You should be see QHS_USB BULK in Device Manager
S
Step 2: Install Driver
Reboot with Driver Signature Enforcement disabled ( Google if you must)
Plug device in and make sure you see QHSUSB BULK in Device Manager
If you see Relink HS QDLoader 9008 uninstall it and delete driver software
Then refresh and you should see QHS USB BULK
Manually Update Driver software and navigate to driver folder extracted in WFS.7z
Step 3 : Install QPST provided in WFS.7z
I think its pretty straight forward
Step 4: Flash Firmware
Open QFil
Select Port and choose your device if not already chosen
Select Flat Build
Programmer Path must be prog_emmc_firehose_8916.mbn in the Maincode folder from WFS.7z
Build Path should automatically appear
Hit load XML.
Click rawprogram_upgrade.xml
Click patch0.xml
Click Download
Once done remove and reinsert battery
Step 5: Verify Tampered:False
boot into fastboot
type the following:
fastboot oem device-info
and it should say Device tampered : false and Device Unlock : False
NB: If you get a SaharaDownload fail or something just remove battery and USB for 5 seconds. Plug battery in. Then plug USB in.
NB: I do not accept any responsibility for damaged devices or anything. You point your finger at me and I will laugh at you
If it works don't hesitate to donate me a cup of coffee
PayPal : [email protected]
yasteellutch said:
Step 2: Install Driver
Reboot with Driver Signature Enforcement disabled ( Google if you must)
Plug device in and make sure you see QHSUSB BULK in Device Manager
If you see Relink HS QDLoader 9008 uninstall it and delete driver software
Then refresh and you should see QHS USB BULK
Manually Update Driver software and navigate to driver folder extracted in WFS.7z
Click to expand...
Click to collapse
This does not work for me, no matter wht I try, in the device manager I just get "Android" with a yello triangle.
No manual driver install / update (or update via windows update) solve that problem.
Try it on two Windows 7 PCs (x32 & x64) with Firewall, Antivirus and driver signature are disabled.
On a Windows 10 PC, the device connects as "Marshall London Device".
I don't think ur swift is bricked
when puting battery in jut get the screen "wileyfox"; recovery does not start (vol- and pwr) but fastboot mode ist working (vol+ and pwr). so it's not bricked?
so I repeat step 1 but still in windows 7 device manager having "Other Devices -> Android" with no yellow triangle.
I get SaharaDownload fail. Removing battary is useless. What else can i try? Thanks in advance
Now you get Sahara Fail. I think this is some sort of 'Lock Mode'. I fixed it by removing battery. Reinserting battery and immediately plugging in USB and hitting download
yasteellutch said:
Now you get Sahara Fail. I think this is some sort of 'Lock Mode'. I fixed it by removing battery. Reinserting battery and immediately plugging in USB and hitting download
Click to expand...
Click to collapse
I try and try do it again but i have only got sahara fail again and again.....
void2000 said:
I try and try do it again but i have only got sahara fail again and again.....
Click to expand...
Click to collapse
Upload a screenshot
yasteellutch said:
Upload a screenshot
Click to expand...
Click to collapse
Probably I have to use a special cable?
See it gets the SharaVersion right so I'm guessing that phone is in a correct state. The problem there could be that it didn't decompress properly. Maybe the integrity of your decompressed WFS.7z is not intact. Go to Android One(2nd Gen) dedicated page. I got help there. I guess all you need is to look there.
Maybe u didn't installQPSt right or the driver is a issue. I flashed stock like 3 days ago and it works perfectly
cyaneo said:
This does not work for me, no matter wht I try, in the device manager I just get "Android" with a yello triangle.
No manual driver install / update (or update via windows update) solve that problem.
Try it on two Windows 7 PCs (x32 & x64) with Firewall, Antivirus and driver signature are disabled.
On a Windows 10 PC, the device connects as "Marshall London Device".
Click to expand...
Click to collapse
Hey @cyaneo. If you still have the Yellow Android triangle this is because your drivers aren't installed correctly. I tried it. But that also means your fastboot is working.
Hi all,
Ive been a way from Android for a long time so I'm no expert but the method posted above failed for me. Like others, all my PC would recognise the phone as was "Marshall London Device" and essentially my phone was useless.
Can I ask why we need to erase and/or brick the phone?
Instead what worked for me was to reboot into fastboot mode, download Cyanogen OS signed zip, extract and run flash-radio.sh, then flash recovery and system manually. Reboot phone into working OS and then turn off OEM Unlock.
Once that's done I rebooted into fastboot and confirmed bootloader was locked and that tampered was false (as an official signed OS is installed I take it?).
Anyway as I say, I'm no expert but surely that's an easier and cleaner way than erasing/bricking a phone and only needs fastboot and the latest official signed rom from Cyanogen OS directly?
void2000 said:
Probably I have to use a special cable?
Click to expand...
Click to collapse
Hi,
This is my first post. (active lurker previously) hopefully its not too late.
In my experience on other device running 8916, a sahara failure can be overcame by holding the power button when entering download mode. (E.g: if you enter download mode by pressing and holding vol+/- simultaneously and plugging in usb cable, try holding the power button as well when you plug in the cable). This is normally a result of battery too low.
After bricking my Swift with some gymnastics around Android One firmware images, this tool worked flawlessly!
I was a bit confused when it came to the part of deleting/ manually reinstalling the driver. After the device was shown as "QHS_USB BULK", I manually installed the " Relink HS QDLoader 9008". Everything else went really smoothly. The device is good as new
For the adventurous ones with a Swift- this is one tough little phone. Hard-brick ain't a reason to stop
Pak0St said:
After bricking my Swift with some gymnastics around Android One firmware images, this tool worked flawlessly!
I was a bit confused when it came to the part of deleting/ manually reinstalling the driver. After the device was shown as "QHS_USB BULK", I manually installed the " Relink HS QDLoader 9008". Everything else went really smoothly. The device is good as new
For the adventurous ones with a Swift- this is one tough little phone. Hard-brick ain't a reason to stop
Click to expand...
Click to collapse
Lol I agree. This baby took some hits. I clocked it to 1.6 at stable. At 1.9 she became instable and started crashing #YeahITakeRisks
xfile087 said:
Hi all,
Ive been a way from Android for a long time so I'm no expert but the method posted above failed for me. Like others, all my PC would recognise the phone as was "Marshall London Device" and essentially my phone was useless.
Can I ask why we need to erase and/or brick the phone?
Instead what worked for me was to reboot into fastboot mode, download Cyanogen OS signed zip, extract and run flash-radio.sh, then flash recovery and system manually. Reboot phone into working OS and then turn off OEM Unlock.
Once that's done I rebooted into fastboot and confirmed bootloader was locked and that tampered was false (as an official signed OS is installed I take it?).
Anyway as I say, I'm no expert but surely that's an easier and cleaner way than erasing/bricking a phone and only needs fastboot and the latest official signed rom from Cyanogen OS directly?
Click to expand...
Click to collapse
Of course there is. Don't get me wrong I understand your point. But you need to remember there are log files and a bunch of other stuff lying around if you fastboot. When you use QFil it basically rewrites all the partitions thus no logs. I returned my first Swift with the IMEI issue and they gave me a new one in a week
Hi,
my Swift is also Bricked.... that means no bootloader boot or etc. i tried to flash the phone with this method but no success. my error with QFIL is this
COM Port number:20
Sahara Version:2
Start Sending Programmer
Download Fail:System.Exception: Unable to download Flash Programmer using Sahara Protocol
bei QC.QMSLPhone.Phone.QPHONEMS_SaharaArmPrgDownload(String sFileName)
bei QC.SwDownloadDLL.SwDownload.QPHONEMSSaharaDownloadArmPrg(UInt64& version, String armPrgPath)
Download Fail:Sahara FailSahara Fail
Finish Download
Click to expand...
Click to collapse
Thanks for response
Error
Download failded
Code:
Dowload fail:House fail failed to Upload the emmc images to phone using firehouse
vadimnew said:
Download failded
Code:
Dowload fail:House fail failed to Upload the emmc images to phone using firehouse
Click to expand...
Click to collapse
You made a mistake @vadimnew
I have an Xperia Play that I got off eBay (I know, I know, personal project - I do have another working one). Reported issue was that it wouldn't boot, but after messing with it, I found that it would 1/10 times if I pull the battery for a few seconds before trying. I was even able to flash a stock firmware again. However, the majority of the time, it won't boot into OS, fastboot, OR flash mode.
Here's why: QHSUSB_DLOAD
From my research, this basically means the bootloader is corrupt or somehow otherwise malfunctioning. When connected to a computer, it resolves to "Qualcomm HS-USB QDLoader 9008 (COM3)" or whatever COM port it lands on, and it does this in fastboot and flash mode. Except for those rare instances where it acts like a normal phone.
I've spent most of the past couple of days digging around in forums, Google, and the Wayback Machine, trying to find a solution. Unfortunately, beyond trying a different computer and reinstalling drivers (both of which I have), the only solutions given are to use Omnius or s1tool/s2tool. They both seem to require payment for unlocking phones, which I don't need, but as far as I can tell should work fine for repairing the s1 boot, which I think is what I need to do. I've been following different guides that all say to remove the battery, connect the test points, and plug in the USB, but I can't get Omnius or the s-tools to work.
Is there any hope for this device? Can anyone who has gone through this before offer some suggestions? Alternatively, is there maybe a way I can just deal with the problem while still being able to use the phone without needing to pull the battery a bunch of times? The Xperia Play is still a great portable gaming system, so I'm hoping we'll be able to figure something out, as I know many other people are starting to acquire these from eBay and try to get them working, and may also run into this issue.
#metoo
I'm also having the same issue.
found this thread [Q] [Hardbricked]Xperia Play lifeless
CamillaHinchcliffe said:
Here's my problem, I wanted to flash a new ROM into my R800a but when I plugged it into my computer it detected the phone as a device called "Qualcomm HS-USB QDloader 9008" and now it does not turn on anymore .
Searching around Google I found that it doesn't turn on because the "SEMCboot" or "Trim Area" is damaged, but I've no idea how to fix that on my own.
Click to expand...
Click to collapse
And this one [How-to] Repair Damaged Bootloader + Trim Area [Red Led][Unknown Device]
Alejandrissimo said:
Sometimes we can brick our devices by a bad unlock, flashing process, or simply bad luck.
The phone doesn't turn on and there is a Red Led Of Death when pressing power button. Even with a GREEN led when we plug the phone with back key pressed the computer detect the phone as "unknown device" so there is no chance to get fixed by Flashtool or SEUS/PC Companion.
Well this problem normally means that the bootloader is broken or damaged. So, in order to fix it we need to write a new SEMCboot and after this we were able to flash a full and fresh firmware with flashtool and unbrick our Xperia.
This process like unlocking process requires SETool dongle/box and a paperclip to make a testpoint to put the phone in flash mode and be able to write the SEMCBoot.
I can help to anyone with a bricked Xperia Arc/Play/Neo/Pro just make send me a PM.
Like unlocking process you will need this 3 programs:
SETool software for unlocking
USB Over network client for remote dongle
Teamviewer client for remote support and guide
THIS PROCESS IS FREE
anyway if you want me to buy a Dr. Peper just
Click to expand...
Click to collapse
And finally, I found this thread in the Xperia SP forum [Guide]Zeus Flash Or qhsusb_dload Solved!!!!!
Almas008 said:
Thanks to mr @the_laser!!!!
Now those who have their phones in qhsusb or zeus flash device can revive their xperia sp to life back....!!!!!
Download attachement and run s1tool and click flash...
select attached sin file set and folow instructions....
Click to expand...
Click to collapse
And also this thread S1 boot download driver.
Some of these fixes and threads are old/outdated, so I dont know what will work Ive already started to use some of the tips last night. I have found out that my phone does get detected as "Qualcomm HS-USB QDloader 9008" but that's as far as Ive gotten. Please read the threads and tell me what you find out, or try that works
I've already been through those threads, and several more like them. The immediate answer is to contact Alejandrissimo, but they've been MIA for years now. I shot them an email the other day, but I don't expect to hear back.
Things I've tried:
Xperia Companion (PC Companion) - doesn't recognize device
SEUS (Sony Ericsson Updater Service) - discontinued, can't connect to servers
S1tool testpoint method - doesn't recognize that a device is connected
Omnius - doesn't recognize that a device is connected
Flashing stock the one time I could get it to boot into flashmode
It looks like this method stands a good chance of working, but it requires an "APPSW .sin_file_set" file, which I haven't been able to acquire for the Xperia Play. From Googling around, it seems that's the blob file that gets downloaded when you get an OTA update or when using XperiFirm (which no longer gives Xperia Play as an option), but all I can find are recompiled *.ftf files. Those files do contain a bunch of *.sin files, but comparing the contents to what you find in a *.sin_file_set file, is too different; the latter has a different folder structure and a bunch of XML files that provide information to the phone. I'm not sure exactly just how necessary that structure is and I couldn't find a guide on recreating a *.sin_file_set file, just how to decrypt one to convert to FTF.
If you click that link to the tutorial for that process, you can download a *.sin_file_set for a different model of phone to see what it should look like.
Of course now I just stumbled on a guide to convert FTF back... I will have to try that.
EDIT: Okay, I grabbed the s1tool from that link and disabled my antivirus before using it. Did the testpoint procedure as described, and got this error:
llbug: [] open error: "The system cannot find the path specified"
Click to expand...
Click to collapse
That might be because the bootloader is still locked. If I can get it to let me into fastboot, I may be able to change that.
EDIT 2: Got it into fastboot, verified the bootloader is locked. Ran the unlock command, but it failed. Tried doing it through s1boot and got the same error as before. Guessing there isn't anything else I can do at this point.
EDIT 3: Forgot to mention the process I tried before was with an FTF, since I discovered S1tool will use those after all (I used the version from that website I linked to). I still need to recompile a sin_file_set version and try that. In the meantime, I did actually receive a response back from Alejandrissimo, so we'll see where that goes and I'll report back.
Hi, everybody
I had the brilliant idea to try to re-lock the bootloader after installing a custom ROM, now my Acquaris X Pro is bricked. ?
I realized that the only way to resurrect it is to use Qualcomm Flash Image Loader (QFIL) by loading the original firmware. The software starts and reveals the Qualcomm HS-USB Diagnostics 900E (COM3) interface and asks me to load the contents.xml file of the programmer.
I then downloaded the latest firmware from the official https://www.bq.com/en/support/aquaris-x-pro/support-sheet page and unpacked the archive, where I found the contents.xml file which I then uploaded to QFIL.
The status window indicates that the prog_emmc_firehose_8953_ddr.mbn file is missing and is trying to load from the BOOT.BF.3.3 folder, which clearly is not present. So I looked for this online and found the folder to download on a Git repository (https://git.szzt.com/yixing/ticai_src). I downloaded the folder and placed it in the path where QFIL expects to find it. I then reloaded the contents.xml file and it reports me the lack of an additional file: rawprogram_unsparse.xml belonging to a certain folder MSM8953.LA.3.0.1.
Unlike the first one, I can't find this last folder online. Can someone help me? ?
Hi @fede91it,
Sorry for the late answer - I have been quite inactive on xda recently
Unfortunately I don't have a solution for you right away, but I got a working X Pro with stock rom (+twrp and magisk) and a bit of experience with the "standard" tools like adb and fastboot. Never worked on such a low level like you though.
Does the tool you mentioned (QFIL) offer the possibility to grab contents from the phone instead of downloading it to it?
Maybe we can get the missing data from my phone?
Sorry for the dump/obvious question, but: What happens in the current bricked state when you turn the phone on? You can't enter fastboot and unlock..?
Another approach: have you tried contacting BQ? Maybe via their forum https://www.mibqyyo.com/. Possibly the missing files are device specific and you would need bqs help..
Thanks for your answer.
I have contacted BQ but they no longer deal with Android phones, I have no support from them.
As for you, thanks for your availability, but the files I'm looking for are for development and don't end up on my phone, so it's impossible to try to extract them from your phone.
By now I've changed phones and kept the Bq as a paperweight brick
fede91it said:
Thanks for your answer.
I have contacted BQ but they no longer deal with Android phones, I have no support from them.
As for you, thanks for your availability, but the files I'm looking for are for development and don't end up on my phone, so it's impossible to try to extract them from your phone.
By now I've changed phones and kept the Bq as a paperweight brick
Click to expand...
Click to collapse
Hey, did you recover your paperweight? I'm in the same situation but with the BQ X PRO
I could not solve it. There are some files missing for the compilation, and I can't find them
Have you tried this method by only using the firehose? forum.hovatek.com/thread-31505.html
Hey, did you recover? I made the same mistake as you. I managed to repair ...
What I did was:
- I removed the battery cable (I did not remove the battery completely)
- I pressed on VolDown button and connected the phone via usb to the pc and immediately went into fastboot mode
- I opened the BQ app on the pc, I loaded the rom and put it to install the rom. It asked to unlock the bootloader (which is what we want) ... The ROM could not be flashed, but it is not important ... As soon as you unlocked the bootloader, the phone started up without a problem
fede91it said:
Hi, everybody
I had the brilliant idea to try to re-lock the bootloader after installing a custom ROM, now my Acquaris X Pro is bricked. ?
I realized that the only way to resurrect it is to use Qualcomm Flash Image Loader (QFIL) by loading the original firmware. The software starts and reveals the Qualcomm HS-USB Diagnostics 900E (COM3) interface and asks me to load the contents.xml file of the programmer.
I then downloaded the latest firmware from the official https://www.bq.com/en/support/aquaris-x-pro/support-sheet page and unpacked the archive, where I found the contents.xml file which I then uploaded to QFIL.
The status window indicates that the prog_emmc_firehose_8953_ddr.mbn file is missing and is trying to load from the BOOT.BF.3.3 folder, which clearly is not present. So I looked for this online and found the folder to download on a Git repository (https://git.szzt.com/yixing/ticai_src). I downloaded the folder and placed it in the path where QFIL expects to find it. I then reloaded the contents.xml file and it reports me the lack of an additional file: rawprogram_unsparse.xml belonging to a certain folder MSM8953.LA.3.0.1.
Unlike the first one, I can't find this last folder online. Can someone help me? ?
Click to expand...
Click to collapse
Hello! Maybe it's too late, but I have the same problem as you and I found this post that talks about our mobile! In it you can find a lot of information, but also the links to download the stock ROMs and the flashing tool to get back to the factory Rom and unbrick the phone! I leave you the links below! Hope it also helps others with the same problem as we! Greeting
Post:
[HOW-TO] BQ Aquaris X Pro | [Stock-ROM] Unlock,Recovery,Root,Upgrade (TWRP/Magisk)
Hi everyone. :) This Post (post #1) shows the complete process of unlocking, flashing, rooting etc. in general, it may refer to old firmware and/or tool versions but the steps remain the same for newer versions. The chapters rely on each other...
forum.xda-developers.com
Link of stock ROMs and the flashing tool:
Support - Aquaris X Pro
web.archive.org
Hi,
Have you ever successfully got it to work again?
Thanks
rufus.wilson said:
Hi,
Have you ever successfully got it to work again?
Thanks
Click to expand...
Click to collapse
Hi,
I managed to get everything working properly.
I installed the Lineage OS custom rom and it works 5 *, with a custom rom you should not block the boot loader, it was the mistake I made.
The solution I used I described 2 comments above
MigSantosPT said:
Hi,
I managed to get everything working properly.
I installed the Lineage OS custom rom and it works 5 *, with a custom rom you should not block the boot loader, it was the mistake I made.
The solution I used I described 2 comments above
Click to expand...
Click to collapse
Hi,
Ah ok.
Just opened it, disconnected the battery. While pressing down VOL- button, I connected it to USB.
Nothing happens on the phone screen. I don't even see the blinking red light now.
Device manager shows it as 9008 COM port.
BQ flash tool doesn't recognise the phone.
I previously installed BQ drivers and rebooted.
Any other suggestions, before I close it back?
rufus.wilson said:
Hi,
Ah ok.
Just opened it, disconnected the battery. While pressing down VOL- button, I connected it to USB.
Nothing happens on the phone screen. I don't even see the blinking red light now.
Device manager shows it as 9008 COM port.
BQ flash tool doesn't recognise the phone.
I previously installed BQ drivers and rebooted.
Any other suggestions, before I close it back?
Click to expand...
Click to collapse
It is strange because it usually shows something on the screen right away ... Pressing the Power button also does not appear anything?
Did you install the ADB drivers? After the ADB drivers are installed, the BQ program recognizes the smartphone
and it also opens doors to use the command line to do almost anything.
rufus.wilson said:
Hi,
Ah ok.
Just opened it, disconnected the battery. While pressing down VOL- button, I connected it to USB.
Nothing happens on the phone screen. I don't even see the blinking red light now.
Device manager shows it as 9008 COM port.
BQ flash tool doesn't recognise the phone.
I previously installed BQ drivers and rebooted.
Any other suggestions, before I close it back?
Click to expand...
Click to collapse
the number 9008 sounds like the EDL mode and NOT the wanted fastboot mode which is required by the usual way of flashing via bq tool or fastboot/adb tools.
What is EDL Mode and How to Boot your Qualcomm Android Device into it
Android phones and tablets equipped with Qualcomm chipset contain a special boot mode which could be used force-flash firmware files for the purpose of unbricking or restoring the stock ROM.
www.thecustomdroid.com
sorry, no solution, only confirming..
Hello, and thanks in advance for for everyone's help (and patience if my post exasperates). This is my 4th OP phone and i've come to rely on MSM heavily as i tend to overflash ROMs etc. Although i've had issues (always evenutally resolved) in the past with getting MSM to restore, this is the first time i feel truly stymied. While playing around with TWRP i ended up having one of the A/B slots seemingly unrecoverable. Even during MSM it would get stuck on DSP.img. I eventually got fastboot to manually write that partition and i thought all was well. However during a flash of a custom ROM the phone crashed (i think t was an external event rather than related to my previous issues) in any event since that point the phone seems to be hard bricked. I can't get to the bootloader or the screen to come on at all. When plugged into Win 10 it is recognized and i can QDLoader 9008 to show up in the device manager. It even starts to work on MSM showing as connected when hitting enum. However after the initial "firehose download" it times out after 18-20 seconds. By unplug/replug etc i can sometimes get it go a bit father but then it stops at Param preload and will go no further.
Thoughts? Questions or detail i missed to help you help me?
re install the driver from device manager try dif port and cable.............
make sure no av shutting it down and good luck!
let me stress try a DIFFERENT PORT AND A DIFFERENT CABLE dunno how many times i can say that even if you got 3 cables go get a new one to rule it out also press hold power up 30 sec before you press hold to get in firehose
Install this on your pc Here. Add your device, use 8 PRO since 9 Pro isn't listed. Choose boot to EDL, and run MSM once your phone in EDL
Click the box to use lite firehose, then enum until it says connected, then start.
You said windows recognized it and so did msm
But I still gotta ask
Did you do the driver verification removal on the windows 10?
Also is it the right msm version/oos?
Use the original USB calbe, better if its a USB C TO A not to C as the C controllers on pcs are kind of weird with these kinda situations.
If you are using the same windows and drivers that worked on your old phones (Haven't formatted or uninstalled the drivers since) then nothing to be done here, but you have try to installing them with windows driver signature turned off. (Qualcomm drivers and oneplus drivers)
make sure the phone booted to EDL too.
These will solve 99% of msmtools problems usually.
try this
Hello, I need help with my LG, the cell phone ran out of battery while updating firmware, now I cannot enter download mode, nor fastboot, and the recovery does nothing, when I turn on the cell phone it always ends up in a black screen with a text of the type "CMD" putting a number and something of "udc_start" and that's it.
windows 10 makes the normal beep but does not recognize the model, in the device manager "android device" appears with the warning sign that there are no drivers.
LGUP does not recognize the device
The only way I had to "make windows recognize it" was with "QFIL" and touching the two pins on the motherboard, in the program it says:
"qualcomm hs-usb qdloader 9008 (com4)"
I have never flashed a cell phone bios or a bootloader if I misunderstand (I am relatively new to android), I have only flashed "the operating system" in this case a 1gb .kdz
I have no idea how to do this, if I don't misunderstand, I need a .mbn (I think it's the bios), which is compatible with QFIL, which I couldn't find in all of google.
I've come across other .mbn of "similar" g4 models, I wonder if it will work if I at least try them.
They may not work perfectly, but at least turn on.
What do you suggest? I feel lost in an ocean t-t
Wachecheiro said:
Hello, I need help with my LG, the cell phone ran out of battery while updating firmware, now I cannot enter download mode, nor fastboot, and the recovery does nothing, when I turn on the cell phone it always ends up in a black screen with a text of the type "CMD" putting a number and something of "udc_start" and that's it.
windows 10 makes the normal beep but does not recognize the model, in the device manager "android device" appears with the warning sign that there are no drivers.
LGUP does not recognize the device
The only way I had to "make windows recognize it" was with "QFIL" and touching the two pins on the motherboard, in the program it says:
"qualcomm hs-usb qdloader 9008 (com4)"
I have never flashed a cell phone bios or a bootloader if I misunderstand (I am relatively new to android), I have only flashed "the operating system" in this case a 1gb .kdz
I have no idea how to do this, if I don't misunderstand, I need a .mbn (I think it's the bios), which is compatible with QFIL, which I couldn't find in all of google.
I've come across other .mbn of "similar" g4 models, I wonder if it will work if I at least try them.
They may not work perfectly, but at least turn on.
What do you suggest? I feel lost in an ocean t-t
Click to expand...
Click to collapse
Check out this thread:
[GUIDE][9008][EDL|QDL][QUALCOMM ONLY] Unbrick via external sdcard (no QFIL!)The author is the definitive LG G4 hard-brick answer guy with possible solutions. You may be able to get some help there.
sdembiske said:
Check out this thread:
[GUIDE][9008][EDL|QDL][QUALCOMM ONLY] Unbrick via external sdcard (no QFIL!)The author is the definitive LG G4 hard-brick answer guy with possible solutions. You may be able to get some help there.
Click to expand...
Click to collapse
I'll take a look at it, thanks
Seems like a similar problem as I had, that's not gonna work though. The only way to fix it is to use a firehose which you can use a one from a Cyanogen MSM8939 device.