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..
Related
Hi all,
I'm getting crazy and tired about this KS20.
I tried everything on this mobile but nothing worked and now emergency mode is only mode I can turn on the thing: not even the hard reset works anymore (booting stucks on vodafone logo).
Corona drivers never worked: reading inf file they are for product ID 6061, but my mobile when connected is product ID 6000 and only LGE usb drivers (downloaded thru the LG update agent) are correctly working.
And LGMDP can see the device but not flash procedure can be initialized on it.
Someone could help me with that please?????
Come guys!
Give me suggestions please!
Hello,
Your message is somewhat confusing that we can help you, otherwise there is already post on this type of problem you should first browse the forum looking for info more precise. The first goal is the flash in emergency mode, after everything is possible ...
By.
rickou26 said:
Hello,
Your message is somewhat confusing that we can help you, otherwise there is already post on this type of problem you should first browse the forum looking for info more precise. The first goal is the flash in emergency mode, after everything is possible ...
By.
Click to expand...
Click to collapse
I searched the forum and googled everything but nothing related to that.
As I wrote in my first post I could not install Corona drivers because, weird enough, device is not recognized by them. I had to install LGE usb drivers thru LG Agent update wizard.
So I can not flash thru LMPD.
Thanks for your reply anyway.
What OS do you use? Do you have administrator rights!
I do have administrator rights.
I do confirm anyway that only LGE USB drivers (they are directly from LG, Product ID 6000) are working fine when in emergency mode.... but they are not Corona drivers (ones signed for Product ID 6061) and LDMP is not working because of that.
Do I have a chance to install rom if I'm not using Corona drivers?
No !
What OS do you use?
Windows xp sp2
I can imagine that none had to deal with this firmware version.
I guess I had to throw away this mobile... such a wate!
Thanks anyway.
delphilip said:
I can imagine that none had to deal with this firmware version.
I guess I had to throw away this mobile... such a wate!
Thanks anyway.
Click to expand...
Click to collapse
Try to gain access to a computer with Windows 7 or Vista, the work better with Corona drivers.
Install the drivers first, restart just to play safe, connect your phone in emergency mode (make sure the green LED is on) and wait for driver detection and installation to finish. If the second driver takes too long to install, then just disconnect the phone and reconnect again. Flash in emergency mode as usual.
In case you have lost your IMEI, use the IMEI restoration tool to generate a new .nv2 file.
Keep updating us on how things work out for you.
If you haven't seen it already, try and have a look at this guide: http://forum.xda-developers.com/showthread.php?t=548447
The part about disabling and enabling the LG driver in Device Manager got my computer to recognize the device in emergency mode so I could flash rickou26's newest ROM on there (and by the way, thanks for the ROM, rickou )
Thanks guys ... i will try your suggestions as soon as I'll be at home again (next week)!
MTM said:
If you haven't seen it already, try and have a look at this guide: http://forum.xda-developers.com/showthread.php?t=548447
The part about disabling and enabling the LG driver in Device Manager got my computer to recognize the device in emergency mode so I could flash rickou26's newest ROM on there (and by the way, thanks for the ROM, rickou )
Click to expand...
Click to collapse
I tried the guide last week but it didn't work for me.
I guess this V08h firmware (not seen anywhere on the web) is a lost cause!
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 was trying to go back to stock os from cm11 on the Amazon fire phone. Downloaded a stock rom and tried to install using safestrap.
After I pressed reboot the phone turned off but didn't turn back on. It's not responding to anything , not even goes into recovery , but when I connect it to computer by cable , six partitions show up , five of which it says are in need of format , and one contains a folder named image , which has a lot of files.
I'm new to this , got cm by following a simple guide , help pls
Hi to you all!
I have exactly the same issue.
If I connect the Fire Phone to the Pc there are six partitions that show up. So ADB sideload is not possible any more. Ialready disconected the battery- did not work out
Does any of you have any idea?
Thanks
How come no one answered to this issue since 2016
Good day everyone,
I wonder why this issue was not replied to since 2016 on a professional forum. Is it because its not fixable?
I just bought an Amazon Fire Phone 64GB, the AT&T version. I already knew the phone was a complete disaster, but I still bought due to my low budget. Its the SnapDragon 800 series processor which I considered for such a small budget phone. Anyways, I rooted it via KingRoot, installed Safestrap-Kodiak-4.0.1-B01. I then downloaded the Unlocked version of the Fire phone Fireware "update-kindle-35.4.6.6_user_466000820" (since I wanted to avoid AT&T bloatware. I reside outside the States so cant use AT&T, so no use keeping it running all the time and sacrifice my battery) and flashed that. It flashed alright but got stuck after the welcome screen after selecting English (United Sates or UK). I then thought of of reverting it back to its original state Fire OS Ver 3.5, so downloaded "update-fire-phone-121_1.0.1_user_101012120" and now it has no life what so ever. Now it in the same state as mentioned by 2 others on this thread. It shows total 6 partitions with only 1 partition with an "Image" named Dir and a few files around 53MB or so residing in it.
I have snapshots of the Image folder files and the "QHSUSB_Bulk" status shown in Device manager, but I cant seem to find an option here to attach my jpg's here. Gosh! It doesnt get dumber than this.
Requesting help from someone who can help me out with anything at all, links, text, vdo's.
I've already downloaded the following files, but dont have a clue what to do with any one of them
QPST.2.7.460
Qualcomm_Flash_Image_Loader_v1.0.0.3
SRKtool_2.1_droidth
Qualcomm HS-USB QDLoader 9008 Driver Qualcomm HS-USB QDLoader 9008 Driver2.1.0.4
Qualcomm HS-USB QDLoader 9008 Driver Ver8.5
Have you tried going into adb sideload, installing adb drivers and sideloading the stock rom?
Now deleted the 29 partitions of the phone.
After experimenting with it, i deleted the 29 partitions of the phone, now its not even showing Qualcomm eMMC USB Storage in device manager.:crying:. Is there anyone who can help me out here. I'd really be grateful.
No life in the phone except for QDLoader 9008 (COM4)
Android# said:
Have you tried going into adb sideload, installing adb drivers and sideloading the stock rom?
Click to expand...
Click to collapse
Its not powering up, going into stock recovery even so i cant get into sideload, if my understanding is correct.
SohailAzeem said:
Its not powering up, going into stock recovery even so i cant get into sideload, if my understanding is correct.
Click to expand...
Click to collapse
*****Sorry, just realized that you can't get into stock recovery anymore please disregard the following as obviously that would only help if you could enter recovery*****
I am sure you already tried but what i meant to say was if you tried power + volume up button, you end up in stock recovery and that's where you gotta go, and select "apply update from ADB" from the recovery menu.
But even before all this, first make a new folder on your desktop, then download the ADB drivers for windows from here: https://developer.android.com/studio/releases/platform-tools.html
Extract the ADB drivers into the new folder you just made. Now, go to https://www.amazon.com/gp/help/customer/display.html?nodeId=201607550 and download the 4.6.6.1 bin file for Amazon Fire Phone, either version will work with AT&T phone, and also put the bin file in the new folder you made earlier. Rename the bin file to just 'fire' or something short and easy. Now on an empty space in that folder press Shift + Right Click together, and select 'open command prompt or windows powershell from here' depending on your computer OS.
Now make sure your phone is powered off, then press power + volume up together to get into stock recovery, and you will see option "apply update from ADB", select that and when phone is ready, connect it to the computer via usb cable. In the command prompt window on the computer, type 'adb devices' and press enter. It should show the amazon phone in adb devices list. Next, type 'adb sideload fire.bin'. If you named the bin file something else make sure you replace 'fire' with that. It will take about 5-10 minutes and once done it should be able to boot normally. You can use kingroot 4.1 and then replace the kinguser with SuperSU using the supersume app. You can download supersume app by searching online or from google appstore, either one works. Hope this helps.
SohailAzeem said:
After experimenting with it, i deleted the 29 partitions of the phone, now its not even showing Qualcomm eMMC USB Storage in device manager.:crying:. Is there anyone who can help me out here. I'd really be grateful.
Click to expand...
Click to collapse
No you bricked it good and proper now.
I have bricked 3 now
It seems while you still have QDLoader 9008 showing up the device is repairable and any Official repairer would be able to restore the phone easily with the correct software and recovery firmware package.
I was in this exact same situation and was unable to get out of this mode even after using "dd" to send the stock recovery and my backed up .img's
Once you Kill the phone in this mode (As I did) it's un fixable and Amazon will send you a new or replacement phone if it still has any manufacture warranty time left.
They will be unable to prove you tampered with it since they cant revive them :laugh:
Just tell them it bricked during a adb side load of the official firmware.
bigrammy said:
No you bricked it good and proper now.
I have bricked 3 now
It seems while you still have QDLoader 9008 showing up the device is repairable and any Official repairer would be able to restore the phone easily with the correct software and recovery firmware package.
I was in this exact same situation and was unable to get out of this mode even after using "dd" to send the stock recovery and my backed up .img's
Once you Kill the phone in this mode (As I did) it's un fixable and Amazon will send you a new or replacement phone if it still has any manufacture warranty time left.
They will be unable to prove you tampered with it since they cant revive them :laugh:
Just tell them it bricked during a adb side load of the official firmware.
Click to expand...
Click to collapse
Wow! That very sad. That was a new phone. Didnt even have a chance to use it. I thought android phones were unbrickable. What brands give away there firmware to be flashed, or in other words Phones which are unbrickable.
SohailAzeem said:
Wow! That very sad. That was a new phone. Didnt even have a chance to use it. I thought android phones were unbrickable. What brands give away there firmware to be flashed, or in other words Phones which are unbrickable.
Click to expand...
Click to collapse
If your able just return the phone as said then they will likely send you a replacement or refund. :good:
Nearly all phones are brickable if you try hard enough but this fire phone is very very easy to brick :laugh:
(In My Opinion only) If you want a cheap almost unbrickable phone then go with the cheap china brands using the MediaTek CPU's. Stay away from the flag ship brands like sony htc lg samsung which use MediaTek CPU's as these manufacturers locked their devices down by removing the MediaTek flashing method and installing their own.
SPFlashTool is the PC software and the Swiss Army knife used for MediaTek so ensure you research :good:
Team MAD (MediaTek Android Developers) Have quite a few devices they support so choose any of those depending on your budget and it will ensure you get some decent updates and running the Latest Android Version. :good:
Do your research by reading the associated threads before you choose.
https://github.com/MediatekAndroidDevelopers
i think you don't read carefully what the Problem is.
Hi to you all!
I have exactly the same issue.
If I connect the Fire Phone to the Pc there are six partitions that show up. So ADB sideload is not possible any more. The Phone is not working not getting ON. The phone is in Dead Condition but if you Connect with PC it shows its Memory Partations. if any phone not getting ON than how can enter to ADB Mode...???
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.
It was only a matter of time before my first brick with this phone. Earlier this evening I tried to factory reset from TWRP and clean flash latest OOS, but it spewed out a whole bunch of partition errors. After various efforts, here's the current status: It won't boot to the OS from either slot. TWRP says no OS installed. On Slot A, it won't boot to recovery either, and the only thing I can get to is fastboot. On Slot B, I can get to TWRP recovery, but all storage is gone (and I've since done a full wipe so there's nothing on it anyway). Any attempts to do adb push or sideload result in the error "adb: error: failed to get feature set: no devices/emulators found", so I can't install anything unless there's another way I'm not aware of.
I'm trying to get into EDL by powering off the phone, then holding down both volume buttons while I plug in the USB cable. It shows up in Device Manager for about 2-3 seconds as "Qualcomm QDLOADER 9008" and then disappears for a second before going directly into fastboot. I've rebooted my computer to disable device driver signing and install the latest Qualcomm drivers per this guide, but the latest drivers are already installed. I've tried a different USB cable and a different USB port.
1) Is there another way to get into EDL mode?
2) Is there anything else I can try from TWRP, adb, or fastboot?
terlynn4 said:
1) Is there another way to get into EDL mode?
2) Is there anything else I can try from TWRP, adb, or fastboot?
Click to expand...
Click to collapse
Was in the same situation few days ago on my 8 Pro not the 9 Pro. Couple of things you could try:
1. The new TWRP had a "Reboot to EDL" option in the advanced section for the first time. Check if the 9 Pro TWRP has the same.
2. My device was only going into fastboot & could boot TWRP, with the same QUALCOMM crashdump error. It would auto power-up the second a cable is inserted, I had to try many reboot-to-EDL programs out there but none worked as the device was playing up. Keep trying MSM.
3. This is weird, but it's what worked with me. The 11.0.4.4 MSM for 8 Pro failed to recognise my device altogether, it's 11.0.3.3 one that worked. With that one, it didn't read the device until maybe the 10th trial. So see if different MSM versions are available for the 9 Pro, and again keep trying MSM.
Good luck.
Fishawy said:
Was in the same situation few days ago on my 8 Pro not the 9 Pro. Couple of things you could try:
1. The new TWRP had a "Reboot to EDL" option in the advanced section for the first time. Check if the 9 Pro TWRP has the same.
2. My device was only going into fastboot & could boot TWRP, with the same QUALCOMM crashdump error. It would auto power-up the second a cable is inserted, I had to try many reboot-to-EDL programs out there but none worked as the device was playing up. Keep trying MSM.
3. This is weird, but it's what worked with me. The 11.0.4.4 MSM for 8 Pro failed to recognise my device altogether, it's 11.0.3.3 one that worked. With that one, it didn't read the device until maybe the 10th trial. So see if different MSM versions are available for the 9 Pro, and again keep trying MSM.
Good luck.
Click to expand...
Click to collapse
Thanks for the suggestions. I did try the "Reboot to EDL" option but it didn't work for me. And I think we only have one MSM version for this model so far. I'll keep trying till it works or I figure something else out.
terlynn4 said:
Thanks for the suggestions. I did try the "Reboot to EDL" option but it didn't work for me. And I think we only have one MSM version for this model so far. I'll keep trying till it works or I figure something else out.
Click to expand...
Click to collapse
You don't have to stick to one model. You can use MSM of 11.2.2.2 EU or 11.2.4.4 India for example, then flash the stock update of a different region, as long as it's an upgrade not the same version.
I did upgrade from 11.0.6.6 AA to 11.0.8.8 EU locally on my 8 Pro. I would imagine it's the same, haven't tested it on my 9 Pro yet though.
I finally got it flashed back to OOS via TWRP and booting normally again. However, it concerns me that I couldn't ever get EDL working, in case I ever really need it. I'll have to keep working on that "just in case".
After trying several things in various orders, I reformatted /data, after which adb push started working. I was able to push the latest full .zip and after a couple more errors I was able to flash it to both slots and reinstall TWRP. I did get an error when I went to reboot that said something like "No OS installed... are you sure you want to reboot?" however it booted into the OS that time.
Anyway, thanks to those who offered suggestions. I'll update again if I ever figure out what's wrong with EDL.
Use All in One tools. Working really good as far as I can see. Choose Oneples 8 pro device since not updted for Oneplus 9 / Pro. There is an option to reboot to EDL thru this tool.
Steve0007 said:
Use All in One tools. Working really good as far as I can see. Choose Oneples 8 pro device since not updted for Oneplus 9 / Pro. There is an option to reboot to EDL thru this tool.
Click to expand...
Click to collapse
Seems like a great tool... however, I just tried it and get the same behavior when I use the Reboot to EDL option. It shows up as a Qualcomm device in Device Manager for a couple of seconds and then reboots to system (now that I have a functional OS). It never shows up in MSM Tool.
terlynn4 said:
Seems like a great tool... however, I just tried it and get the same behavior when I use the Reboot to EDL option. It shows up as a Qualcomm device in Device Manager for a couple of seconds and then reboots to system (now that I have a functional OS). It never shows up in MSM Tool.
Click to expand...
Click to collapse
Hi, I noticed when using the 64 version of Qualcomm driver, my phone would auto boot out of EDL as soon as it would enter it. I had to use a nother version I believe is 32 bit version. That fixed the problem for me. Also usually it's the boot that is messed up when something goes wrong and replacing that will usually fix and if not; replacing correct boot and then wiping data is what worked for me.
Samuel Holland said:
Hi, I noticed when using the 64 version of Qualcomm driver, my phone would auto boot out of EDL as soon as it would enter it. I had to use a nother version I believe is 32 bit version. That fixed the problem for me. Also usually it's the boot that is messed up when something goes wrong and replacing that will usually fix and if not; replacing correct boot and then wiping data is what worked for me.
Click to expand...
Click to collapse
Well, you're definitely onto something, but there's still a missing piece. After installing 32-bit drivers I'm able to get the phone into EDL mode... screen is blank and "Qualcomm QDLoader 9008" shows up in device manager, and it actually stays there without the phone trying to boot on its own. However, the phone still doesn't show up in MSM. In device manager it has a yellow triangle and says the driver isn't signed, even though I installed it after doing the advanced reboot to allow unsigned drivers.
Where do you download the latest version of the 32-bit driver from? Maybe the one I found isn't the latest?
terlynn4 said:
Well, you're definitely onto something, but there's still a missing piece. After installing 32-bit drivers I'm able to get the phone into EDL mode... screen is blank and "Qualcomm QDLoader 9008" shows up in device manager, and it actually stays there without the phone trying to boot on its own. However, the phone still doesn't show up in MSM. In device manager it has a yellow triangle and says the driver isn't signed, even though I installed it after doing the advanced reboot to allow unsigned drivers.
Where do you download the latest version of the 32-bit driver from? Maybe the one I found isn't the latest?
Click to expand...
Click to collapse
I can't remember where I got it from , I believe from 8t forum? I've had it on my Google drive for quite some time. If you would like me to share it I could. I don't remember if I added to the name originally. The name on the file is
Qualcomm_USB_Host_Drivers_1.00.53_20180705_w7_w10(8t_link).exe
Samuel Holland said:
I can't remember where I got it from , I believe from 8t forum? I've had it on my Google drive for quite some time. If you would like me to share it I could. I don't remember if I added to the name originally. The name on the file is
Qualcomm_USB_Host_Drivers_1.00.53_20180705_w7_w10(8t_link).exe
Click to expand...
Click to collapse
I didn't find that version, but I did find a [presumably] newer version 2.1.0.3 32-bit driver that appears to work. The device now shows up in MSM Tool. Thanks for the help!
terlynn4 said:
I didn't find that version, but I did find a [presumably] newer version 2.1.0.3 32-bit driver that appears to work. The device now shows up in MSM Tool. Thanks for the help!
Click to expand...
Click to collapse
Can you share a link for that updated 32-bit driver?
If what Samuel Holland suggested is valid in my case as well, that would get rid of the auto-boot issue we struggled with.
Fishawy said:
Can you share a link for that updated 32-bit driver?
If what Samuel Holland suggested is valid in my case as well, that would get rid of the auto-boot issue we struggled with.
Click to expand...
Click to collapse
The one that worked for me was the 32-bit setup.exe file from this guide. I uninstalled the existing driver I had installed, rebooted, installed this driver, and then EDL worked right away.