Hi,
I got a tablet from a friend of mine with broken software. So i tried to flash te original firmware with Odin, but something went wrong when I tried to flash it. I don't know what went wrong it just said FAIL. Now when I connect the tablet it only shows CLOVERVIEW in device manager without the correct driver. I googled a little and found something from an Asus zenfone driver installation and now I've got 2 devices when I connect it: CloverviewPlus Device and Intel Soc USB driver. I suppose this has to do something with the Intel processor in the tablet. I downloaded a program xFSTK-downloader and can find the tablet in the program, but I don't have the correct files to flash anything on the tablet. The program ask for FW Dnx, IFWI, OS DnX, OS Image. Where can I get these files or is there another way to restore the tablet?
Sorry for the bad English and greetings from Holland
I've put it in the wrong section, can someone delete this thread? Thanks
Related
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...???
Hi,
I got a tablet from a friend of mine with broken software. So i tried to flash te original firmware with Odin, but something went wrong when I tried to flash it. I don't know what went wrong it just said FAIL. Now when I connect the tablet it only shows CLOVERVIEW in device manager without the correct driver. I googled a little and found something from an Asus zenfone driver installation and now I've got 2 devices when I connect it: CloverviewPlus Device and Intel Soc USB driver. I suppose this has to do something with the Intel processor in the tablet. I downloaded a program xFSTK-downloader and can find the tablet in the program, but I don't have the correct files to flash anything on the tablet. The program ask for FW Dnx, IFWI, OS DnX, OS Image. Where can I get these files or is there another way to restore the tablet?
Sorry for the bad English and greetings from Holland
stefanschoemaker said:
Hi,
I got a tablet from a friend of mine with broken software. So i tried to flash te original firmware with Odin, but something went wrong when I tried to flash it. I don't know what went wrong it just said FAIL. Now when I connect the tablet it only shows CLOVERVIEW in device manager without the correct driver. I googled a little and found something from an Asus zenfone driver installation and now I've got 2 devices when I connect it: CloverviewPlus Device and Intel Soc USB driver. I suppose this has to do something with the Intel processor in the tablet. I downloaded a program xFSTK-downloader and can find the tablet in the program, but I don't have the correct files to flash anything on the tablet. The program ask for FW Dnx, IFWI, OS DnX, OS Image. Where can I get these files or is there another way to restore the tablet?
Sorry for the bad English and greetings from Holland
Click to expand...
Click to collapse
In BL file but is not working.
Anyone has a solution?
So what someone has done is flashed Asus firmware on the device. You can put it into download mode and flash it's original stock firmware from sammobile. Or if you can get into recovery mode try and wipe everything from there and see if it will boot
No download, only cloverviewplus and gets error when flashing
---------- Post added at 10:44 AM ---------- Previous post was at 10:41 AM ----------
I cant upload images in tapatalk. U can see in this thread:
https://forum.gsmhosting.com/vbb/showthread.php?p=12783614
My little brother have a Rockchip based Tablet which is more than 3 years old. It named Symphony and device name on about the device have a different name of K11+. running JB 4.2.2. I never found it's origin and all other details on the internet. But I pulled its firmware with some tool and I have a backup of it. And successfully managed to perform its firmware updation many times. But, Yesterday I stuck on an error. That when I performed a wipe using the tool (I always makes it before the firmware installation) where it called "Erase NAND (IDB). Then my Laptop got error that USB device not recogonized. I tried many ways to overcome this error, even tried to re-install ADB, Driver etc... But nothing happened... So, Is there any hope of getting back ? All others even my smart phones were also works on same port and USB cable. Hope that someone can help me out...
https://drive.google.com/file/d/1mg8BDBCaoCS_LXE0TBSd5TdKV81YUsCM/view?usp=sharing[/IMG]
Hi guys,
i need some help unbricking my d722.
what went wrong?
I tried to flash twrp with flashify and i ended up in demigodmode.
from there i connected the phone to my computer and like 10 portable drives showed up asking to be formatted. I formatted all except one drive because it was protected from.
After i formatted the drives my phone was dead with only a black screen left.
Since i can't find any .tot firmware files for this model i tried to use the .tot firmware for a g3 in BoardDiag.
but when i want to use the extracted .tot firmware files on my phone it says this:
no response from device, check pmic first and if still boot problem replace ap
i think i have managed to install qualcomm driver and the phone is recognized as a qualcomm when plugged in.
But i did not shortwire the motherboard because i can't find the GND
can anyone please help me fix my phone thank you so much!
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..