Urgent help needed + QFIL - Oppo F1

Hi guys,
As mentioned in a previous thread, my F1 is soft bricked, only with the Oppo logo, no fastboot or recovery. I need to flash it again with a soft called QFIL (soft for Qualcomm devices). But it can't be done with the ordinary stock roms, I need a specific rom compatible with QFIL, like the ones used in the service centers. Is there anyone who can provide me with such a rom, or a link to download one in order to save my device?
Thank you

Can someone owning a Oppo f1 use QFIL to extract all the necessary files in order to flash them to my phone? I would be very grateful.

I have the, flashing tool and rom needed to unbrick the f1 from any softbricked state.
Let me know if you still need it, and I'll upload it somewhere and write a quick guide.
Worked for me even after I killed the bootloader.

tb303lava said:
I have the, flashing tool and rom needed to unbrick the f1 from any softbricked state.
Let me know if you still need it, and I'll upload it somewhere and write a quick guide.
Worked for me even after I killed the bootloader.
Click to expand...
Click to collapse
Hi, good news, I would be glad and would appreciate if you could send them to me.
Thanks in advance.

QDLoader Flasher Drivers and Firmware.
This will unbrick the Oppo F1f even if bootloader has been corrupted.
How to:
Download and extract this archive.
Install the QDLoader driver found in the DRIVER directory of the extracted archive.
Switch phone off, hold Vol-Up and connect USB cable between phone Pc .
Run Msm8x39DownloadTool.exe (in F1EX_11_A.05_160128 directory) as Administrator.
Select phone type (16GB or 32GB)
Choose the port your phone is connected to from the list. (It will be the one which says Com Device as Device Type.
Tick "Reset when .."
Click Start.
Let it do its thing, and bam! working stock F1f.
warning this will delete all user data.
Any questions PM me.
Al

tb303lava said:
QDLoader Flasher Drivers and Firmware.
This will unbrick the Oppo F1f even if bootloader has been corrupted.
How to:
Download and extract this archive.
Install the QDLoader driver found in the DRIVER directory of the extracted archive.
Switch phone off, hold Vol-Up and connect USB cable between phone Pc .
Run Msm8x39DownloadTool.exe (in F1EX_11_A.05_160128 directory) as Administrator.
Select phone type (16GB or 32GB)
Choose the port your phone is connected to from the list. (It will be the one which says Com Device as Device Type.
Tick "Reset when .."
Click Start.
Let it do its thing, and bam! working stock F1f.
warning this will delete all user data.
Any questions PM me.
Al
Click to expand...
Click to collapse
Hi, I downloaded the zip, followed your steps and...my phone is alive and everything works perfectly. Thank you so much for your help. Couldn't have been done without you.

How to choose the port?? I am not able to choose the port. When i connect it to pc whole holding volume up button it doesn't show anything.

sir is your file is from optus australia
tb303lava said:
QDLoader Flasher Drivers and Firmware.
This will unbrick the Oppo F1f even if bootloader has been corrupted.
How to:
Download and extract this
Install the QDLoader driver found in the DRIVER directory of the extracted archive.
Switch phone off, hold Vol-Up and connect USB cable between phone Pc .
Run Msm8x39DownloadTool.exe (in F1EX_11_A.05_160128 directory) as Administrator.
Select phone type (16GB or 32GB)
Choose the port your phone is connected to from the list. (It will be the one which says Com Device as Device Type.
Tick "Reset when .."
Click Start.
Let it do its thing, and bam! working stock F1f.
warning this will delete all user data.
Any questions PM me.
Al
Click to expand...
Click to collapse
oppo f1f from optus australia need qfill firmware
i m from india set come to me for sim unlock
i follow this guide (How To unlock Oppo F1f - Guide unlock network Oppo mobile F1f from youtube) to flash modified firmware
but at the first step i flashed magictricks.zip & set goes to qdloader 9008 mode after reboot
so i need optus australia firmware,thanks in advance

Need some help - Msm8x39DownloadTool.exe not finding phone
Qualcomm HS-USB QSLoader9008 on COM3, according to Device Manager, yet Msm8x39DownloadTool.exe doesn't want to find it at all - Device not connected.
Any help would be really appreciated.
Edit: I have made some progress with some steps not included above.
1) Disable 'Driver Signature Enforcement' in Windows (Google is your friend)
2) Before installing the provided drivers, hold the Volume Up button on your phone, and insert USB from PC > Phone. This places the phone into QHSUSB mode and will be found in Device Manager, under Ports (The Android Bootloader Interface (fastboot) device has an ID of '18D1-D00D', while the QHSUSB device ID is '05C6-9008'.. bingo!).
3) Install the driver as directed. This will change the device from QHSUSB mode to HS-USB QDLoader 9008 on COM3.
Continue with the rest of the guide.
Stock recovery will be returned (v1.2 Rooted - I don't remember this). From here you can install Project Spectrum again, and return back to ColorOS after that.
Hopefully this helps.

tb303lava said:
QDLoader Flasher Drivers and Firmware.
This will unbrick the Oppo F1f even if bootloader has been corrupted.
How to:
Download and extract this archive.
Install the QDLoader driver found in the DRIVER directory of the extracted archive.
Switch phone off, hold Vol-Up and connect USB cable between phone Pc .
Run Msm8x39DownloadTool.exe (in F1EX_11_A.05_160128 directory) as Administrator.
Select phone type (16GB or 32GB)
Choose the port your phone is connected to from the list. (It will be the one which says Com Device as Device Type.
Tick "Reset when .."
Click Start.
Let it do its thing, and bam! working stock F1f.
warning this will delete all user data.
Any questions PM me.
Al
Click to expand...
Click to collapse
I tried this my phone has no Fastboot but recovery says V1.2(Rooted)
I tried this multiple times without luck.

As you still have access to stock recovery, you dont need to use download mode.
Simply put a stock rom zip on your sdcard and flash via the stock recovery. (might have to wipe data also if flashing a different version of the rom).
That will fix your phone.
To get access to fastboot (should you need to flash TWRP recovery), flash magictricks.zip via recovery.
If your phone is so busted you no longer have access to fastboot and recovery it will automatically default to QDloader mode (download mode).
If you want to access download mode while your recovery is still ok, switch phone off, hold Vol-Up (or Vol-down, can't recall) and plug in the usb cable.
AS LONG AS YOU HAVE ACCESS TO RECOVERY, USE THAT TO FLASH A STOCK FIRMWARE, GETTING THE QDLOADER DRIVERS CORRECTLY INSTALLED ON WINDOWS CAN BE RATHER TRICKY.

tb303lava said:
I have the, flashing tool and rom needed to unbrick the f1 from any softbricked state.
Let me know if you still need it, and I'll upload it somewhere and write a quick guide.
Worked for me even after I killed the bootloader.
Click to expand...
Click to collapse
Hey man can you help I've soft bricked my oppo, please need flashing tool and rom

phaw16 said:
I tried this my phone has no Fastboot but recovery says V1.2(Rooted)
I tried this multiple times without luck.
Click to expand...
Click to collapse
HEY BRO HOW DID YOU FIX YOUR F1f SAME PROBLEM HERE I TRY THE STEPS ABOVE BOT INSTALLATION FAILED WHEN FLASHING A ROM please HElp me ver 1.2(rooted)

after flashing my f1f just going to RECOVERY then its auto turn ON and recovery again. bootloop to recovery any fix?

tb303lava said:
QDLoader Flasher Drivers and Firmware.
This will unbrick the Oppo F1f even if bootloader has been corrupted.
How to:
Download and extract this
Install the QDLoader driver found in the DRIVER directory of the extracted archive.
Switch phone off, hold Vol-Up and connect USB cable between phone Pc .
Run Msm8x39DownloadTool.exe (in F1EX_11_A.05_160128 directory) as Administrator.
Select phone type (16GB or 32GB)
Choose the port your phone is connected to from the list. (It will be the one which says Com Device as Device Type.
Tick "Reset when .."
Click Start.
Let it do its thing, and bam! working stock F1f.
warning this will delete all user data.
Any questions PM me.
Al
Click to expand...
Click to collapse
thanks sir, its work
Edabigael said:
after flashing my f1f just going to RECOVERY then its auto turn ON and recovery again. bootloop to recovery any fix?
Click to expand...
Click to collapse
u neeed to flash OTA firmware from recovery, that what i did.. i use F1EX_11_OTA_002_all_201601170010.. put on your sd card and install

Related

Unable to unlock my Nexus 5 :(

Hi guys,
Need URGENT help. I have a Nexus 5 running android 5.0.1. Today morning it was working fine. After that I changed the pin lock and it has stopped working since then. Every time I enter the new password it says wrong password.
1. I tried using Android device manager but it says 'No active devices' linked to my account.
2. I tried using cerberus but it is also of no use as it says 'you are not connected to google servers'.
Can anyone help me unlock the phone or bypass the lock screen.
Much needed help
Did you already tried a factory reset? Boot into recovery mode and make a factory reset. That should help you. You a have a lot of guides showing how to do this .
nunojsa said:
Did you already tried a factory reset? Boot into recovery mode and make a factory reset. That should help you. You a have a lot of guides showing how to do this .
Click to expand...
Click to collapse
Is there a way by which I'll be able to save my data. I guess factory reset will wipe out all the data.
Contact the support of Google. They may be able to fix your account and link it to the device .
gauravshaan said:
Is there a way by which I'll be able to save my data. I guess factory reset will wipe out all the data.
Click to expand...
Click to collapse
You only have screen lock and you haven't encrypted the phone, right? If that is true I can flash a custom recovery to your phone even if the bootloader is locked. Maybe from the custom recovery I could remove the screen lock (never done that before). If I fail to do that then atleast we could save files from the internal storage.
bitdomo said:
You only have screen lock and you haven't encrypted the phone, right? If that is true I can flash a custom recovery to your phone even if the bootloader is locked. Maybe from the custom recovery I could remove the screen lock (never done that before). If I fail to do that then atleast we could save files from the internal storage.
Click to expand...
Click to collapse
I have not encrypted the phone. Can you please let me know how can I install custom recovery without unlocking the bootloader. Sorry for the trouble but I'm a noob at this.
gauravshaan said:
I have not encrypted the phone. Can you please let me know how can I install custom recovery without unlocking the bootloader. Sorry for the trouble but I'm a noob at this.
Click to expand...
Click to collapse
Well you have to download this
Extract it.
Run it.
Select Nexus5 in AP Chipset
Select the img folder as Target Dir
Check AP check
Check RESTORE BOOT IMG and select recovery
Make sure your phone is turned on
Connect USB cable
Open device manager
Start pressing volume_up+volume_down+power keys until a new device appears
Wait for windows to install drivers
Expand Ports (COM & LPT) in device manager
Check the COM number after Qualcomm QHS-USB QDLoader 9008 device
In boarddiag tool set the same com port what you saw in device manager.
Click on start.
After the process finishes the phone restarts and you have to avoid to get the phone booting to android because it will replace TWRP recovery with the stock one. So when you click on start keep pressing the volume_down key for the whole time until you are in fastboot mode. Then select recovery mode. Then follow the instructions here http://forum.xda-developers.com/showthread.php?t=1409304 I have no idea will it work on lollipop, but it worth a try.
bitdomo said:
Well you have to download this
Extract it.
Run it.
Select Nexus5 in AP Chipset
Select the img folder as Target Dir
Check AP check
Check RESTORE BOOT IMG and select recovery
Make sure your phone is turned on
Connect USB cable
Open device manager
Start pressing volume_up+volume_down+power keys until a new device appears
Wait for windows to install drivers
Expand Ports (COM & LPT) in device manager
Check the COM number after Qualcomm QHS-USB QDLoader 9008 device
In boarddiag tool set the same com port what you saw in device manager.
Click on start.
After the process finishes the phone restarts and you have to avoid to get the phone booting to android because it will replace TWRP recovery with the stock one. So when you click on start keep pressing the volume_down key for the whole time until you are in fastboot mode. Then select recovery mode. Then follow the instructions here http://forum.xda-developers.com/showthread.php?t=1409304 I have no idea will it work on lollipop, but it worth a try.
Click to expand...
Click to collapse
Can this method be used to access data when GUI is unaccessible?
Description of the problem is in "[Q] "Unfortunately, System UI has stopped." after OTA to LRY47I" thread.

[Guide] Meizu M3 & M3s Unbrick

After experiencing help from the fantastic meizu community i have decided to make a guide for unbricking this device. This guide is aimed to help people with M3 or M3s that cannot boot. Please only follow these steps to unbrick your device
I am not responsible for bricked devices and exploding phones due to following these steps.
By following these steps you agree that it is you, yourself that chose to follow these steps and I will not take any responsibility for your loss.
Before Starting
1. Can you boot ?
No. Go to Question 2.
Yes. You have came to the wrong place, but feel free to finish reading.​2. Do you see the flyme logo when you boot?
Yes. Goto Stuck on Flyme Logo
No. Go to Question 3​3. Do you see the Meizu Logo and phone reboots over and over
Yes. Go to Testing
No. You flashed a wrong or damaged preloader, chances of unbricking LOW, Go to Sp Flash Tool​
Testing
1. Shutdown your phone by holding power button (if you can)
2. Turn on phone with power + volume up until vibrates
I see a flyme logo & recovery options, Goto Stuck on Flyme Logo
Still rebooting, Continue​
3. Turn on phone with power + volume down until vibrates
I see the words 'fastboot' at bottom, Go to Sp Flash Tool
I see nothing, your preloader is dead, I cannot help you :crying:.​
Sp Flash Tool
Requirements
Micro USB cable (plug phone to pc)
Computer (prefer windows)
Internet to download​
1. Download SP_Flash_Tool Link below
2. Download Firmware for your device (latest)
M3 Link https://downloads.meizufans.eu/?dir=m3/firmware/stable
M3s Link https://downloads.meizufans.eu/?dir=m3s/firmware/stable​3. Download scatter file 'MT6750_android_scatter.txt' Link below
4. Use sp_flashtool (flashtool.exe)
A. Uncompress SP_Flash_Tool.zip into pc
B. Uncompress 'update.zip' (the firmware)
C. Copy downloaded scatter file 'MT6750_android_scatter.txt' to update folder
D. 'Run as Administrator' flash_tool.exe file
E. Go to the menu Options -> connection - > usb full speed with battery
F. For download agent select DA_PL.BIN from the same folder
G. Load the downloaded scatter file 'MT6750_android_scatter.txt' in update folder
H. Select the 'download only' option (don't press download yet)
I. Untick all the ROM at the bottom.
J. Suggest to select and flash one ROM at a time (except userdata and boot)
recovery
m1img
md1dsp
md1arm7
md3img
lk
lk2
tee1
tee2​WARNING do NOT flash 'preloader'
K. Flash by clicking download
L. Turn on and connect phone to computer when vibrate
M. Wait for download to complete, with a green tick.
N. After flashing all ROM, now flash boot.​5. Power on your phone.
6. Did it work?
No, Still in reboot cycle, Retry from the top, or use different update.zip
Yes, i have boot to flyme logo but stuck in boot logo, goto Stuck on Flyme Logo
Yes, i have boot to flyme logo and my phone is back, Congrats.​
Links
Scatter File: https://drive.google.com/file/d/0B3pRT6ewL6tqeWZhQThFRGVwbE0/view?usp=sharing
SP Flash Tool.zip:
https://drive.google.com/file/d/0B3pRT6ewL6tqSW8tNTQ1OFY2eXc/view?usp=sharing​
Stuck on Flyme Logo
You see the flyme logo, and the logo spins couple every couple of sec and waited for over 30 min and still does not boot.
Get in recovery mode, two ways choose one.
Method one (easy)
1. Turn off Phone (Force by holding power button)
2. Turn on Phone with power + volume
If it does not work go to Sp Flash Tool or Method two
Yes, my devices is now in recovery mode, continue the steps, skip Method two​
Method two (need computer and harder)
1. Turn on the Phone where the logo spins
2. install adb on computer (link http://forum.xda-developers.com/showthread.php?t=2588979)
3. Plug phone into computer and get drivers for adb
4. Type 'adb devices' in cmd
5. If you get a device in the list continue by Typing 'adb reboot recovery'
'adb devices' not displaying devices (try method one or install driver)
'adb reboot recovery' reboots phone but not to recovery, this confirms that the recovery partition is damaged follow the steps in Sp Flash Tool
Yes, my devices is now in recovery mode, continue the steps​Download Firmware for your device (latest)
M3 Link https://downloads.meizufans.eu/?dir=m3/firmware/stable
M3s Link https://downloads.meizufans.eu/?dir=m3s/firmware/stable​
Plug Phone (in recovery mode) to computer. Copy the downloaded file 'update.zip' into the removable device named 'recovery' (do not unzip)
Tick the top option (system upgrade) and click 'start'
Wait be patient.:fingers-crossed:
Special Thanks
Kokotonix, this is a build up of Kokotonix's post link here: https://forum.meizufans.eu/topic/65...om-bootloop-meizu-logo-and-constant-reboot/11
Meizufans, thanks for this website and everyone in it, where i got most of the information from.
Questions & Answers
Q. Why is my phone unrepairable if i can get to fastboot?
A. By not being able to access fastboot means the preloader partition is damaged and SP Flash Tool will not work.​Q. Why is my phones not bootable.
A. It could be caused by many factors but mainly caused by failure in updating firmware due to no battery or incorrect flashing of ROM.​Q. Why is it so hard to recover meizu phones
A. Meizu phone uses the new mt67xx which is not supported by MTK droid tool causing problems for users to obtain the scatter file, and also the locked bootloader leading the users not being able to recover the devices the traditionally using fastboot.​Q. I have a m3 note can i use this method?
A. Yes if anyone gets there hands on the mt6755 scatter file for meizu. But if not No​Q. HELP ME IT'S NOT WORKING!!!
A. Calm down, follow the steps again, if not comment below.​Q. How do i brick my device
A. Get root and flashify and flash a random .img as the kernel. (it works i tried)​
Thank you for Reading and wish you for the best on this device.
Comment below for help and also share you success.
reserved
phone is dead(
More info? You lost your preloader
Sent from my M3s using XDA-Developers mobile app
bluecub1st said:
More info? You lost your preloader
Sent from my M3s using XDA-Developers mobile app
Click to expand...
Click to collapse
after installing damaged rom its completely dont turn on only when you plug it to pc it recognize it like MTK Usb Port
logirus said:
after installing damaged rom its completely dont turn on only when you plug it to pc it recognize it like MTK Usb Port
Click to expand...
Click to collapse
Any display? or just black?
What rom did you install? If official you might be able to get a replacement through warranty.
Try SP Flash Tools, instruction in the first post. Chances are low but test if it detects after pressing download.
bluecub1st said:
Any display? or just black?
What rom did you install? If official you might be able to get a replacement through warranty.
Try SP Flash Tools, instruction in the first post. Chances are low but test if it detects after pressing download.
Click to expand...
Click to collapse
i installed from official firmware after installing it rebooted and never turn on no vibration nothing(no warranty i bought it from china on aliexpres) and please look at error ive got sp flash tool
Wrong download agent use the one I used in guide DA_PL.BIN
Sent from my M3s using XDA-Developers mobile app
Looks like it detects it phone u have hope
Sent from my M3s using XDA-Developers mobile app
bluecub1st said:
Wrong download agent use the one I used in guide DA_PL.BIN
Sent from my M3s using XDA-Developers mobile app
Click to expand...
Click to collapse
i used DA_PL.BIN and got the same error, maybe bootloader is locked thats why this error?
The error shows when your device started before the software can flash anything. SP flash tools works with locked bootloader, maybe your preloader is 100% dead
Sent from my M3s using XDA-Developers mobile app
bluecub1st said:
The error shows when your device started before the software can flash anything. SP flash tools works with locked bootloader, maybe your preloader is 100% dead
Sent from my M3s using XDA-Developers mobile app
Click to expand...
Click to collapse
and no way to repair it?:crying: i think im gonna trash this chinese cellphone away and never buy meizu again
No recovery, Fastboot mode is working. What should I do with this error?
Is there a way to work on me with meizu m3 max
Hi,
SPFlashtools fails to connect dead bricked Meizu M3S
Connecting to USB system recognizes as
MediaTek DA USB VCOM Port (COM7)
But other ports including Preloader are not
Do I have any hope to recover phone?
After following these steps, one by one, no matter if all went OK, my phone (m3s) won’t boot and it seems it is completely dead now. It can’t turn on. Power button looks unresponsive. What should I do? Is there any help?
many thanks for this guide @bluecub1st . The problem I have with my M3s is that it boots perfectly fine and works well, i just cannot enter recovery by using Volume + and power, and flashing a new firmware from inside Flyme OS just reboots the phone. I can enter fastboot though no problem, but i tried to do the SP Flash tool method listed and I just get this error message:
ERROR : S_TIMEOUT (0x412)
Any ideas how to fix this and get my recovery back? Really need some help so i can flash flyme 6...
i got error from sp_flashtool
ERROR : STATUS_SEC_DL_FORBIDDEN (0X0020004)
help me please sir
ERROR : STATUS_SEC_WRITE_DATA_NOT_ALLOWED
what to do ?
phone dead... thnks

Nokia 3 Preloader Bricked

Hello XDA-Team and all others who read this.
I got an Nokia 3 from Friend who killed Device trying to Flash TWRP and Root Phone ...
The Phone can only be "Powered On" by pressing Vol Up & Power for a few seconds. After this the phone will only vibrate after each 10 seconds - i think its trying to boot but fails and then try again ... until battery will powered down and needs recharge (with no displaying charging status)
Under Windows - Device Manager - the conected phone will change in each loop cycle between the following stats :
1. PreLoader USB VCOM Port (COM3) - 2. MTK USB Port (COM4) - 3. MTK USB Port (COM4) - and then vibrate and start again
... so i think the PreLoader is bricked - first because i've read that these PreLoader will loaded first after PowerOn - like a BIOS on any Mainboard
I've tryed any solution i found on the web - mostly on xda - incl. OST LA Tool, SP Flash Tool and others ... so i've noticed some "error messages" from SP Flash Tool and also that an trying to Flash with SP Flash Tool stops the boot-vibrate-loop
Is there any solution to manually Reflash original Firmware or repair the PreLoader ???
I know older Nokia Phones can be "Reflashed" by using an self builded USB-OTG "Y-Cable" with the following configuration: Side A : USB-A plug to connect to usb power plug (or computer) - Side B: micro-USB Plug to connect phone - Side C: USB-A female to connect USB-Stick with the needed Firmware Image File (on older nokia phones it will be an NB0-File i know) ... i also know you must first put the USB-Stick with File via the cable to the OFF-POWERED Phone and then put the USB-A plug into Power and wait until the "Update Procedure" will be finished - most under 30 minutes
So, if the will be an idea or solution to fix this "Error" PLZ HELP
M4RCJO said:
Hello XDA-Team and all others who read this.
I got an Nokia 3 from Friend who killed Device trying to Flash TWRP and Root Phone ...
The Phone can only be "Powered On" by pressing Vol Up & Power for a few seconds. After this the phone will only vibrate after each 10 seconds - i think its trying to boot but fails and then try again ... until battery will powered down and needs recharge (with no displaying charging status)
Under Windows - Device Manager - the conected phone will change in each loop cycle between the following stats :
1. PreLoader USB VCOM Port (COM3) - 2. MTK USB Port (COM4) - 3. MTK USB Port (COM4) - and then vibrate and start again
... so i think the PreLoader is bricked - first because i've read that these PreLoader will loaded first after PowerOn - like a BIOS on any Mainboard
I've tryed any solution i found on the web - mostly on xda - incl. OST LA Tool, SP Flash Tool and others ... so i've noticed some "error messages" from SP Flash Tool and also that an trying to Flash with SP Flash Tool stops the boot-vibrate-loop
Is there any solution to manually Reflash original Firmware or repair the PreLoader ???
I know older Nokia Phones can be "Reflashed" by using an self builded USB-OTG "Y-Cable" with the following configuration: Side A : USB-A plug to connect to usb power plug (or computer) - Side B: micro-USB Plug to connect phone - Side C: USB-A female to connect USB-Stick with the needed Firmware Image File (on older nokia phones it will be an NB0-File i know) ... i also know you must first put the USB-Stick with File via the cable to the OFF-POWERED Phone and then put the USB-A plug into Power and wait until the "Update Procedure" will be finished - most under 30 minutes
So, if the will be an idea or solution to fix this "Error" PLZ HELP
Click to expand...
Click to collapse
OST LA is easiest method to flash firmware. Can it boot to fastboot mode?
SkaboXD said:
OST LA is easiest method to flash firmware. Can it boot to fastboot mode?
Click to expand...
Click to collapse
Nope ... it will only vibrate at each 10 seconds ... display are still blank / black / noting happens on it :/
M4RCJO said:
Nope ... it will only vibrate at each 10 seconds ... display are still blank / black / noting happens on it :/
Click to expand...
Click to collapse
Daymm, idk then, that's a big problem
cant run nokia 3
I have the same problem just that vibrate each 5 seconde witha black screen any help please
I have the same Problem. Unresponsive, black screen, vibrating every ~10 seconds. No button presses lead to a change in behaviour
Same to you ,caz I erased the preloader partition,so now got the only vibrating phone,XD, yeah, it's hard bricked.
Sent from my SM-G950F using Tapatalk
---------- Post added at 08:02 PM ---------- Previous post was at 08:00 PM ----------
haumich_blau said:
I have the same Problem. Unresponsive, black screen, vibrating every ~10 seconds. No button presses lead to a change in behaviour
Click to expand...
Click to collapse
Hard bricked
Sent from my SM-G950F using Tapatalk
---------- Post added at 08:03 PM ---------- Previous post was at 08:02 PM ----------
mediafire007 said:
Same to you ,caz I erased the preloader partition,so now got the only vibrating phone,XD, yeah, it's hard bricked.
Sent from my SM-G950F using Tapatalk
---------- Post added at 08:02 PM ---------- Previous post was at 08:00 PM ----------
Hard bricked
Sent from my SM-G950F using Tapatalk
Click to expand...
Click to collapse
Do not erase the preloader, it's very important or you will kill the phone.
Sent from my SM-G950F using Tapatalk
i extracted preloader.bin from 7.1.1 december security patch, is it there a way to somehow flash it?
Hi there, I don't have much time to explain in details now, but Ive been able to unbrick my Nokia 3 from this state by using SF flashtool with emergency mode and a rom version that I found around. It gave it life back.
After that I've been able to boot into fastboot mode and I flashed the boot.img and system.img (and not sure for the cache.img) using the fastboot commands. These IMG files were taken from a full rom update.zip (android 7.0 that I found around). I t removed root and if I well remember, the bootloader was relocked (not quite sure). After that, I could get the OTA updates (even Oreo beta).
I'll try to give more details (links to the correct ROMs, exact commands) later if you still struggle.
Hope this help anyway!
Cheers
Seem problem here, keeps vibration every now and then. But nothing shows up even ost la doen't recognise phone anymore.
Todrak, if you do have more details. I guess where all happy to hear it..
Loaded scatter file. Opened SP Flash Tools. Clicked download. Entered meta mode by pressing vol up + vol down + power on at the same time. Tried auth file, but it doesn't work.
So we stucked until we get proper auth file.
Guys, I UNBRICKED MY DEVICE! First you need to unpack stock nb0 rom with nb0 unpacker:
https://forum.xda-developers.com/android/general/nb0-unpacker-packer-tool-t3699464
tnx to @heineken78
then you'll got all files that you need to flash with SP Flash Tool including scatter file. Load scatter file on SP Flash Tools and choose all partitions to flash (don't change, rename or move files from unpacked Stock ROM folder because SP Flash Tool will not recognize files).
then do this:
Max brackenz said:
# Download Nokia 3 supported Download agent file
# Now put it to the sp flashtool folder (replace with DA_SWSEC_CRYPTO20.bin)
# Run flash_tool.exe with administrator, and choose the Download-Agent I give you
# DONE
Download Agent https://mega.nz/#!xd8B3AJQ!PW82IpLzMzyNQk55BdwMnRMPlKQA0Yzj_8k_xN5r9XM
Click to expand...
Click to collapse
tnx to @Max brackenz
You don't need auth file. It requests auth file when you press all 3 buttons but if you enter meta mode propely, it will not ask for auth file.
You will have 3 options for flashing: Format All + Download, Firmware Upgrade and Download. Choose Download option.
Here you need to be fast.
Connect phone to computer. Click Download on SP Flash Tool. Disconnect USB cable. Enter META mode by pressing power on + volume up and quickly connect USB to PC at the same time.
Video example:
at 2:29
tnx to autor of this video.
Then it should start flashing process with red bar first (shortly) then with purple bar (shortly) and then with yellow bar. Wait for it to flash. Green circle/tick mark will appear if it's flashed successfully. It failed on 60 % for me but most importantly it flashed preloader.
Now reflash ROM with OST if you failed in half of process like me and you're good to go.
If it fails, try again. It didn't worked for me at first try.
SkaboXD said:
Guys, I UNBRICKED MY DEVICE! First you need to unpack stock nb0 rom with nb0 unpacker:
https://forum.xda-developers.com/android/general/nb0-unpacker-packer-tool-t3699464
tnx to @heineken78
then you'll got all files that you need to flash with SP Flash Tool including scatter file. Load scatter file on SP Flash Tools and choose all partitions to flash (don't change, rename or move files from unpacked Stock ROM folder because SP Flash Tool will not recognize files).
then do this:
tnx to @Max brackenz
You don't need auth file. It requests auth file when you press all 3 buttons but if you enter meta mode propely, it will not ask for auth file.
You will have 3 options for flashing: Format All + Download, Firmware Upgrade and Download. Choose Download option.
Here you need to be fast.
Connect phone to computer. Click Download on SP Flash Tool. Disconnect USB cable. Enter META mode by pressing power on + volume up and quickly connect USB to PC at the same time.
Video example:
at 2:29
tnx to autor of this video.
Then it should start flashing process with red bar first (shortly) then with purple bar (shortly) and then with yellow bar. Wait for it to flash. Green circle/tick mark will appear if it's flashed successfully. It failed on 60 % for me but most importantly it flashed preloader.
Now reflash ROM with OST if you failed in half of process like me and you're good to go.
If it fails, try again. It didn't worked for me at first try.
Click to expand...
Click to collapse
you save my phone thnx bro you are really BOSS ♥
Riadh300 said:
you save my phone thnx bro you are really BOSS ♥
Click to expand...
Click to collapse
np bro, I'm always willing to help
SkaboXD said:
Guys, I UNBRICKED MY DEVICE! First you need to unpack stock nb0 rom with nb0 unpacker:
https://forum.xda-developers.com/android/general/nb0-unpacker-packer-tool-t3699464
tnx to @heineken78
then you'll got all files that you need to flash with SP Flash Tool including scatter file. Load scatter file on SP Flash Tools and choose all partitions to flash (don't change, rename or move files from unpacked Stock ROM folder because SP Flash Tool will not recognize files).
then do this:
tnx to @Max brackenz
You don't need auth file. It requests auth file when you press all 3 buttons but if you enter meta mode propely, it will not ask for auth file.
You will have 3 options for flashing: Format All + Download, Firmware Upgrade and Download. Choose Download option.
Here you need to be fast.
Connect phone to computer. Click Download on SP Flash Tool. Disconnect USB cable. Enter META mode by pressing power on + volume up and quickly connect USB to PC at the same time.
Video example:
at 2:29
tnx to autor of this video.
Then it should start flashing process with red bar first (shortly) then with purple bar (shortly) and then with yellow bar. Wait for it to flash. Green circle/tick mark will appear if it's flashed successfully. It failed on 60 % for me but most importantly it flashed preloader.
Now reflash ROM with OST if you failed in half of process like me and you're good to go.
If it fails, try again. It didn't worked for me at first try.
Click to expand...
Click to collapse
Nice to hear:fingers-crossed:
SkaboXD said:
Guys, I UNBRICKED MY DEVICE! First you need to unpack stock nb0 rom with nb0 unpacker:
https://forum.xda-developers.com/android/general/nb0-unpacker-packer-tool-t3699464
tnx to @heineken78
then you'll got all files that you need to flash with SP Flash Tool including scatter file. Load scatter file on SP Flash Tools and choose all partitions to flash (don't change, rename or move files from unpacked Stock ROM folder because SP Flash Tool will not recognize files).
then do this:
tnx to @Max brackenz
You don't need auth file. It requests auth file when you press all 3 buttons but if you enter meta mode propely, it will not ask for auth file.
You will have 3 options for flashing: Format All + Download, Firmware Upgrade and Download. Choose Download option.
Here you need to be fast.
Connect phone to computer. Click Download on SP Flash Tool. Disconnect USB cable. Enter META mode by pressing power on + volume up and quickly connect USB to PC at the same time.
Video example:
at 2:29
tnx to autor of this video.
Then it should start flashing process with red bar first (shortly) then with purple bar (shortly) and then with yellow bar. Wait for it to flash. Green circle/tick mark will appear if it's flashed successfully. It failed on 60 % for me but most importantly it flashed preloader.
Now reflash ROM with OST if you failed in half of process like me and you're good to go.
If it fails, try again. It didn't worked for me at first try.
Click to expand...
Click to collapse
thanks, you saved my phone, that works 100%.
please hellppp
Krahmati said:
thanks, you saved my phone, that works 100%.
Click to expand...
Click to collapse
i tried the manipulation it ask me authentification file pleaseeeee helllppp
f0lcan said:
i tried the manipulation it ask me authentification file pleaseeeee helllppp
Click to expand...
Click to collapse
hold power on + volume up buttons. If it asks asks for auth file try again
Hi, i dont know how, but guide from SkaboXD works... I unbrick my vibrate device and phone start works. Bud i had problem with bootloader and unlock him with fastboot... (when i confirm yes i´ll open the bootloader it was error 0x7000 or something like that. So, i started try another roms and flash. In some rom after failed download and format flash with SP Tool is brick to harder... When i connected now phone into computer isnt vibrate only it show in device manager (Mediatek Preloader USB VCOM port (COM6)) and now if i try to flash (only download) with SP TOOL it show error 5000 (auth file) or error 2005. While i write this. I dont think so, that its possible to unbrick my device but if somebody buy this phone to the root isnt right choise... Its problem phone... If somebody have some suggestion how can fix this i would like...
dont flash any nokia 3 mobile with sp flash tool it totally brick your phone. please give it to a phone shop if you want to change the version or any other problem. i bricked my phone with sp flash tool. it is harder to save my phone. now i gave it to a shop for repair i don't know they can fix problem or not.....

Recovering hardbricked phone from Qualcomm QS-Loader 9008 state [Z010DD/Z010D]

Since a lot of people flashed the wrong firmware (thanks to Asus for launching multiple devices under the same name ) on their Max, I've come across multiple threads here regarding Hardbricke and Qualcomm QD-loader 9008 state. I too have been a victim of the same issue and my phone was dead for around a year, before managing to get it to work again. I'm going to list out the procedure and relevant links here.
ps: I've tested this method on my Z010DD device. This should work with Z010D devices as well.
1. Download and install QPST from the link given https://androidmtk.com/download-qpst-flash-tool
2. Install Qualcomm drivers from here https://gsmusbdrivers.com/download/android-qualcomm-usb-driver/
3. Download the QFIL, QCN and RAW firmware for your device (Snapdragon 410 - MSM8916 and Snapdragon 615 - MSM8939) from here https://www.firmware27.com/2017/10/asus-zenfone-max-z010d-zc550kl-firmware.html and unzip both of them in separate directories
4. Open QFIL from the start menu and connect you dead phone to PC (Make sure your phone is detected as Qualcomm QD-Loader 9008. If not, uninstall Qualcomm drivers, reboot PC, reinstall and try again until you succeed)
5. Select 'Flat build' as Build type. Select prog_emmc_firehose_8936.mbn (or prog_emmc_firehose_8939.mbn) from the QFIL firmware directory as 'Programmer path'. Click on 'Load XML' and select 'rawprogram0.xml' and 'patch0.xml'.
6. Click on download and wait for the flashing process to complete ( takes some time. If you encounter sahara fail error, the uninstall and reinstall driers as stated in step 4)
7. Phone will reboot to service firmware (which is aosp and in chinese). Enable usb debugging and rebot to bootloader
8. Flash TWRP for your device and flash magisk
9. Reboot to fastboot and flash the files NON-HLOS.bin and NON-HLOS_IN.bin from your stock rom zip(available on Asus official Website) using command
Code:
fastboot flash modem NON-HLOS.bin
fastboot flash modem NON-HLOS_IN
10. Reboot to system and add your original imei using the tool here https://drive.google.com/open?id=1OBAp69EA4KGHdYXA5DrwMLCIuAqNYMu4
11. Reboot phone and reset your serial number as instructed below
Code:
You need to root your phone and download Terminal Emulator and type the following command:-
1. su
2. dd if=/dev/block/bootdevice/by-name/factorybak of=/sdcard/factory
Wait a sec...
3. dd if=/sdcard/factory of=/dev/block/bootdevice/by-name/factory
reboot
12. Verify serial number and IMEI are present in your device. If yes, open QFIL->Tools->QCN backup restore. Select the QCN file for your device downloaded in step 3 and restore.
13. The device should reboot. If it fails, try restoring again (took me 8 tries).
14. Your phone should be getting network signals now. If now, try QCN restore again
15. Flash RAW firmware for your device
16. Boot to stock rom, setup everything and verify if you are getting signal. If yes, congratulations:fingers-crossed::fingers-crossed::fingers-crossed:
If any step so far failed and nothing is working for you, then you can revert to QD-Loader 9008 mode by using code
Code:
adb reboot edl
and start over from beginning
Nb: If you are not able to unlock bootloader after getting everything else working, verify if your serial number is present. It is the main reason unlocking is not working
Huge thanks to all people who helped me
@amanksinghhh @SakilMondal @audahadi @ShadowReaper1 @dark wiz @Saktis_STi @rashidhabib and the many people whose xda pofile names I don't know.
buddy the link to the firmware file that u have given is not working. I have tried downloading it on multiple occasions but till today i haven't been able to download either of the files. Kindly if u can provide me any other link to these file from where i can download them it would be of a lot of help. My phone is dead from pas t 7 days and have been trying to revive it but to no success. Kindly help please.
Hey Man. I'm currently working on my phone. I already tried removing the battery but I'm still getting the error:
Download Fail: Switch to EDL Fail.
hopes are going narrow. Now I don't know what to do.
Restore to normal mode from factory mode.
Thanks a lot for the detailed procedure. Restored my phone back to start. However my phone is stuck on factory mode and i'm unable to restore it back to normal mode. Also tried the Exit factory mode file given in the link of firmware download section. However whenver i try to write it with the help of QIFL it says sahara fail error and my phone's stuck in factory mode still. And also haven't been able to receive any network signal in the phone after inserting sim in the phone. Kindly help.
sree27 said:
Since a lot of people flashed the wrong firmware (thanks to Asus for launching multiple devices under the same name ) on their Max, I've come across multiple threads here regarding Hardbricke and Qualcomm QD-loader 9008 state. I too have been a victim of the same issue and my phone was dead for around a year, before managing to get it to work again. I'm going to list out the procedure and relevant links here.
ps: I've tested this method on my Z010DD device. This should work with Z010D devices as well.
1. Download and install QPST from the link given https://androidmtk.com/download-qpst-flash-tool
2. Install Qualcomm drivers from here https://gsmusbdrivers.com/download/android-qualcomm-usb-driver/
3. Download the QFIL, QCN and RAW firmware for your device (Snapdragon 410 - MSM8916 and Snapdragon 615 - MSM8939) from here https://www.firmware27.com/2017/10/asus-zenfone-max-z010d-zc550kl-firmware.html and unzip both of them in separate directories
4. Open QFIL from the start menu and connect you dead phone to PC (Make sure your phone is detected as Qualcomm QD-Loader 9008. If not, uninstall Qualcomm drivers, reboot PC, reinstall and try again until you succeed)
5. Select 'Flat build' as Build type. Select prog_emmc_firehose_8936.mbn (or prog_emmc_firehose_8939.mbn) from the QFIL firmware directory as 'Programmer path'. Click on 'Load XML' and select 'rawprogram0.xml' and 'patch0.xml'.
6. Click on download and wait for the flashing process to complete ( takes some time. If you encounter sahara fail error, the uninstall and reinstall driers as stated in step 4)
7. Phone will reboot to service firmware (which is aosp and in chinese). Enable usb debugging and rebot to bootloader
8. Flash TWRP for your device and flash magisk
9. Reboot to fastboot and flash the files NON-HLOS.bin and NON-HLOS_IN.bin from your stock rom zip(available on Asus official Website) using command
Code:
fastboot flash modem NON-HLOS.bin
fastboot flash modem NON-HLOS_IN
10. Reboot to system and add your original imei using the tool here https://drive.google.com/open?id=1OBAp69EA4KGHdYXA5DrwMLCIuAqNYMu4
11. Reboot phone and reset your serial number as instructed below
Code:
You need to root your phone and download Terminal Emulator and type the following command:-
1. su
2. dd if=/dev/block/bootdevice/by-name/factorybak of=/sdcard/factory
Wait a sec...
3. dd if=/sdcard/factory of=/dev/block/bootdevice/by-name/factory
reboot
12. Verify serial number and IMEI are present in your device. If yes, open QFIL->Tools->QCN backup restore. Select the QCN file for your device downloaded in step 3 and restore.
13. The device should reboot. If it fails, try restoring again (took me 8 tries).
14. Your phone should be getting network signals now. If now, try QCN restore again
15. Flash RAW firmware for your device
16. Boot to stock rom, setup everything and verify if you are getting signal. If yes, congratulations:fingers-crossed::fingers-crossed::fingers-crossed:
If any step so far failed and nothing is working for you, then you can revert to QD-Loader 9008 mode by using code
Code:
adb reboot edl
and start over from beginning
Nb: If you are not able to unlock bootloader after getting everything else working, verify if your serial number is present. It is the main reason unlocking is not working
Huge thanks to all people who helped me
@amanksinghhh @SakilMondal @audahadi @ShadowReaper1 @dark wiz @Saktis_STi @rashidhabib and the many people whose xda pofile names I don't know.
Click to expand...
Click to collapse
kool.shwetank12345 said:
Thanks a lot for the detailed procedure. Restored my phone back to start. However my phone is stuck on factory mode and i'm unable to restore it back to normal mode. Also tried the Exit factory mode file given in the link of firmware download section. However whenver i try to write it with the help of QIFL it says sahara fail error and my phone's stuck in factory mode still. And also haven't been able to receive any network signal in the phone after inserting sim in the phone. Kindly help.
Click to expand...
Click to collapse
There is a tool which is used to switch from factory mode to normal mode. But QCN should be flashed and serial number should be restored before switching to normal mode. QCN restore is hard but it'll work in a few tries. Uninstall drivers and QFIL and retry. That's the only solution I can recommend
Link to factory mode changer : https://drive.google.com/file/d/1U6CbCrteFbEMgME_kfn37XTOo7Yqz9Ct/view
Hy guys!!! I have the 410 version but my windows won't detect Qualcomm QD-loader 9008 it detects it like Qualcomm QD-loader 9006.
Is there a way to fix this?
kool.shwetank12345 said:
buddy the link to the firmware file that u have given is not working. I have tried downloading it on multiple occasions but till today i haven't been able to download either of the files. Kindly if u can provide me any other link to these file from where i can download them it would be of a lot of help. My phone is dead from pas t 7 days and have been trying to revive it but to no success. Kindly help please.
Click to expand...
Click to collapse
This is a really late reply and I apologise for that. Hope I'm not too late
https://drive.google.com/file/d/1raOSoIsfSBAQuofLPpsAZczJStZNqbkN/view
Help please
Kindly please help me and give your telegram id

I need urgent help :(

Hey there... I was trying to get my OnePlus 7 -That I just bought - to a rooted Android 10, updating was the easy part but while trying to "fastboot flash boot twrp.img" I think I somehow got myself stuck making the bootloader (aka fastboot mode ) as my main thing the phone load into and now when I turn on the phone it goes straight to fastboot mode I go and try to "fastboot flash boot twrp.img" it says OKAY twice but I can't load into recovery it takws me back to the fast boot again.... Idk what to do... Help
More into:
I got to the twrp before once during the process and idk why dumb me rebooted when I couldn't access my phone files from pc I wanted to put the image of OOS on a flash drive and via OTG but once I restarted by mistake after that whatever choice I make on the fastboot screen will quickly restart and get back to the same screen, so I can do "fastboot flash boot twrp.img" successfully but I can't load to it I hit reboot to recover or Start or Reboot Bootloader nothing takes me to twrp,
Also when I try "fastboot flash recovery twrp.img"
It says sending recovery okay, writing recovery failed, (remote: (recovery_b) no such partition)
I hope to get any help and I'm sorry if it's an obvious thing I couldn't notice, I'm not the sharpest between my brothers. Momma says. ? with me. I'll appreciate it I promise.
Have you tried this Fastboot ROMS?
Use this:
https://forum.xda-developers.com/oneplus-7/how-to/unbrick-tool-oneplus-7-msmtool-hydrogen-t3953240
After that just put offical Rom zip for your region on internal memory and after that install update. voila
Unbrick tool also available for OxygenOS pie https://forum.xda-developers.com/oneplus-7/how-to/op7-unbrick-tool-to-restore-device-to-t3954325 :good:
Help
same issue with me...whenever i try to recover using fastboot method,it gives an error like product name is sdm845 and required is msmnile
and when i use the msm tool , it gives an error of sahara server....
any help is highly appreciated.
sourabhone said:
same issue with me...whenever i try to recover using fastboot method,it gives an error like product name is sdm845 and required is msmnile
and when i use the msm tool , it gives an error of sahara server....
any help is highly appreciated.
Click to expand...
Click to collapse
"sahara server" problem : disable driver signature / update drivers
https://www.howtogeek.com/167723/ho...8.1-so-that-you-can-install-unsigned-drivers/
Qualcomm dr: https://gsmusbdrivers.com/download/android-qualcomm-usb-driver/
you must to press power button at the same time you plug in usb cable.....keep trying and your computer will start installing drivers for Port 9008
(you can use Google Search for more Info about "sahara" problem)
First of all twrp.img is a recovery image. You would normally use fastboot flash recovery twrp.img.
Secondly, you aren't supposed to flash twrp.img but use fastboot boot twrp.img and then boot to twrp and flash the twrp installer. If you can boot into fastboot, type fastboot boot twrp.img(twrp.70 for android q) and then flash twrp installer and oos. And if you can't boot into recovery you will have to use the msm tool.
daitalos said:
"sahara server" problem : disable driver signature / update drivers
Qualcomm dr:
you must to press power button at the same time you plug in usb cable.....keep trying and your computer will start installing drivers for Port 9008
(you can use Google Search for more Info about "sahara" problem)
Click to expand...
Click to collapse
Thanks daitalos for the reply..
the drivers for 9008 are installed as visible in device manager...
the msm tool shows the phone as connected, when i start the process, it waits for loading firehose binary and waits there for 10 sec.....after that throws error of sahara communication failed (FH:258)
i again tried the volume up + power button combo but to no avail...
also there is no red led light on the phone while charging
sourabhone said:
Thanks daitalos for the reply..
the drivers for 9008 are installed as visible in device manager...
the msm tool shows the phone as connected, when i start the process, it waits for loading firehose binary and waits there for 10 sec.....after that throws error of sahara communication failed (FH:258)
i again tried the volume up + power button combo but to no avail...
also there is no red led light on the phone while charging
Click to expand...
Click to collapse
In device manager you can see "Qualcomm HS -USB QDLoader 9008 (com3 for example) ?
You tried another usb port (?)
in windows 10 it is better for the computer to have the "developer mode" enabled
Close any antivirus temporarily..
Run msm tool as Administrator ofcourse..
(I don't know but If you try with msm tool from here : https://forum.xda-developers.com/oneplus-7/how-to/op7-unbrick-tool-to-restore-device-to-t3954325
you should see the models it supports (GM1900, GM1901, GM1903, GM1905)
_I think the problem is on the computer and the communication with the device...
sry for english
Thanks
daitalos said:
In device manager you can see "Qualcomm HS -USB QDLoader 9008 (com3 for example) ?
You tried another usb port (?)
in windows 10 it is better for the computer to have the "developer mode" enabled
Close any antivirus temporarily..
Run msm tool as Administrator ofcourse..
(I don't know but If you try with msm tool from here : h t tp s: // forum . xda-developers . com/oneplus-7/how-to/op7-unbrick-tool-to-restore-device-to-t3954325
you should see the models it supports (GM1900, GM1901, GM1903, GM1905)
_I think the problem is on the computer and the communication with the device...
sry for english
Click to expand...
Click to collapse
Thank you so much daitalos.
At last i was able to recover my phone from being a paperweight.Used my other laptop and it worked perfectly first time.Maybe my 1st laptop was having some issues.

Categories

Resources