Database Develop

How To Unbricked A Hard Bricked Phone [ Moto X ]

How To UnBrick A Hard Bricked Moto X​
Hii , First of all I wanna thanks to this awesome scrpit by @s5610 who brought my phone from dead to alive , I think i am the first guy to unbricked the hardbricked phone using this script lol , My phone was hardbricked because i was testing my kernel and entered wrong path in partition due to which i got hard bricked i was worried for my phone , Service Center was asking for 7k in Indian Rupees , i was hopeless then i gave a try to this method , followed all steps written here and then finally i entered to fastboot menu of 30.B7 Kitkat As i was using 30.B7 Bootloader earlier and then i flashed My gpt.bin and S-partition and flashed my stock rom voilla !! and my phone booted the aim was to share this post was this method was on page 42 and only less guys have seen this post , so i created a new thread regarding this
All Credits Goes to - @s5610​
s5610 said:
Unbricking Guide for any Moto X Gen 1 (wire trick)​
Download, and unpack supplied zip to any disk, C: or D:, in root folder. Install driver by launching Qusb.drv.inst.msi, then open Windows' Device Manager, and see if you got "Qualcomm HS-USB QDLoader 9008" device (it is "QHSUSB_DLOAD" without driver installed) located in "COM & LPT ports" section.
If yes, you see it, go to software part below. If it's not there, a full disassemble of the phone is needed to get close to back side of motherboard (google for "iFixit Teardown Moto X Guide" for step-by-step instruction).
So, when you are inside, disconnect the battery first. No need to pull it out, it's glued. Now get to back side of motherboard, and very very gently gain access to the lower left corner of ARM+DRAM shield (see picture). I've done it with Stanley knife. Also you can use miniature nippers - but very carefuly! Once you get access to inner space of shield, use tiny wire to short special pin to the ground (see picture), then connect USB cable, and in the moment when you see "QHSUSB_DLOAD" device (or "Qualcomm HS-USB QDLoader 9008" if driver is installed) pop out in Windows' Device Manager, quickly remove the wire. The goal is to have "Qualcomm HS-USB QDLoader 9008" in "COM & LPT ports" section of Device Manager. If it is achieved, we are done with hardware, and move on to soft part.
Now software part. Go to unzipped C:\Python27 folder, launch bat-file, and wait until finish:
RUN_blank_bootloader_flash.bat
(if you got error like "No data read from USB..." etc, just skip to next step)
Next launch either
- .Boot_KK_4.4.2_B4.exe,
or .Boot_KK_4.4.4_B7.exe,
or .Boot_LP_5.0.2_BC.exe,
or .Boot_LP_5.1.0_BD.exe,
or .Boot_LP_5.1.0_BE.exe
- depends on Android version your phone has last time. If you don't know what you need, begin with first one.
Wait 10 seconds, then launch next bat-file, and wait until finish:
RUN_moto_x_bootloader_flash.bat
Phone should go into fastboot mode! If it doesn't, repeat previous step trying higher version. But don't try to flash BC, BD, and BE, if you didn't install Lollipop on this phone!
OK. Disconnect the USB cable, connect the battery, connect again USB cable (fastboot don't work, if don't see battery). Launch next bat-file:
RUN_gpt.bin_flash.bat
The phone will get in fastboot, ready to be flashed by appropriate firmware. If it is official RSD (SBF), delete from xml strings consisting gpt.bin and motoboot.img for safe flashing.
...
Download link: http://www.mediafire.com/download/3e38rr3wy28s071/Moto.X.Unbrick.zip
This guide was brought to you by s5610
Links that this guide is based on (where I took files and general idea):
http://forum.xda-developers.com/droid-ultra/general/droid-ultra-maxx-brick-recovery-t2830806
http://forum.xda-developers.com/mot...-moto-x-t2629057[/url[/QUOTE][/QUOTE][/QUOTE]
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Click to expand...
Click to collapse

Not sure if additional thread is necessary )
UPDATED
The best resurrection method for Moto X is here.

Can Someone re-upload that file? Thanx!

Please upload the mediafire link...
Plz plz.. I have bricked my phone. It seems that this procedure will work for me. Please upload and save my life.

even i have bricked my moto x...need a working download link..please.

https://drive.google.com/file/d/0B3EDzuzDCakzdWxHa2RWVDJhRXc/view?usp=sharing

Cannot install qsub.drv.inst.msi on my windows 10...says failed to attribute and failed to delete qcusbser.sys.

Thanks

Can we write the full firmware through Qload 9008 mode ???

HI I have a question. I bricked my gf's phone while trying to unlock the bootloader and I am not able to turn the phone on. Only positive feedback is that when I plug it in to the computer, I can hear a notification on my computer. I followed your guide. I can see the "Qualcomm HS-USB QDLoader 9008" device (it is "QHSUSB_DLOAD" without driver installed) located in "COM & LPT ports" section.
Then I followed your software instructions. When I run the RUN_blank_bootloader_flash.bat, I get the following
Code:
Starting qflash!
Executing command qflash.exe -com3 -ramload MPRG8960.hex -mbn 33 MSM8960_bootloa
der_singleimage.bin -v -o
Motorola qflash Utility version 1.3
qflash - com3 is an invalid port
Invalid COM port enteredBlank flashing successful
Device will now enumerate in fastboot mode
Then, I followed the rest of the instructions by trying each .Boot .exe and waitng 10 seconds and finally with RUN_moto_x_bootloader_flash
but I am getting the following error.
Code:
C:\Users\cxx\Desktop\Python27>python qdload.py MPRG8960.bin -ptf _boot\partiti
ons.txt -pt
QDLoad utility version 1.2 (c) VBlack 2014
Found TTY port: com3
Traceback (most recent call last):
File "qdload.py", line 815, in <module>
main()
File "qdload.py", line 762, in main
tty = openTTY(args.ttyPort)
File "qdload.py", line 174, in openTTY
tty = serial.Serial(port=tty_path, baudrate=115200)
File "C:\Python27\lib\site-packages\serial\serialwin32.py", line 38, in __init
__
SerialBase.__init__(self, *args, **kwargs)
File "C:\Python27\lib\site-packages\serial\serialutil.py", line 282, in __init
__
self.open()
File "C:\Python27\lib\site-packages\serial\serialwin32.py", line 66, in open
raise SerialException("could not open port %r: %r" % (self.portstr, ctypes.W
inError()))
serial.serialutil.SerialException: could not open port 'com3': WindowsError(2, '
The system cannot find the file specified.')
C:\Users\cxx\Desktop\Python27>pause
Press any key to continue . . .
please help.
Thanks.

Device Shows As USB Input
Hey all,
I'm having trouble getting my Windows 7 machine to recognize my XT862 as a QHSUSB device. Windows does recognize it, just as a "USB Input Device" -- very generic, I know -- so I don't think I have to do any motherboard hacks (and I sure hope not!). However, as it won't let me update the driver either, so I can't do anything. Also, when I plug it into my Mac, it does pop up as a Qualcomm Composite Device. Since something's obviously still ticking, where did I go wrong?
Thanks

shengslogar said:
Hey all,
I'm having trouble getting my Windows 7 machine to recognize my XT862 as a QHSUSB device. Windows does recognize it, just as a "USB Input Device" -- very generic, I know -- so I don't think I have to do any motherboard hacks (and I sure hope not!). However, as it won't let me update the driver either, so I can't do anything. Also, when I plug it into my Mac, it does pop up as a Qualcomm Composite Device. Since something's obviously still ticking, where did I go wrong?
Thanks
Click to expand...
Click to collapse
Put it on a charger for 5-6 hrs and see if that will help.I had this same problem but on a Moto G and charging it up helped.

liveroy said:
Put it on a charger for 5-6 hrs and see if that will help.I had this same problem but on a Moto G and charging it up helped.
Click to expand...
Click to collapse
Will do! I think I did try charging it awhile ago, but I'll give it another shot.

can my phone be unbricked?? here is the error log:
RAMLOADER VERSION: PBL_DloadVER2.0
------------------------------------------------------
DEVICE INFORMATION:
------------------------------------------------------
Version : 0x8
Min Version : 0x1
Max Write Size: 0x600
Model : 0x90
Device Size : 0
Description : Intel 28F400BX-TL or Intel 28F400BV-TL
------------------------------------------------------
Using passed in packet size, changing from 0x600 -> 0x600
EXTENDED_LINEAR_ADDRESS_REC @ 0x2a000000
Write 65536 bytes @ 0x2a000000
100EXTENDED_LINEAR_ADDRESS_REC @ 0x2a010000
Write 11840 bytes @ 0x2a010000
100START_LINEAR_ADDRESS_REC @ 0x2a000000
EOF_REC
Sleeping for 3s
sdl_hello() - Invalid response: 7e030003331b7e
sdl_hello() - This is a NAK response from ROM code, which means the device has
een reset back to blank flash mode. Usually this is caused by power supply issu
s. Please try again with battery eliminator if it persists
Unexpected target reset, bailing out after 2 retries

I am trying to install the drivers and it will show up as qhsusb_dload for about 5 seconds then reverts back to Relink HS USB QDloader 9008. Should i try the wire trick? It will say that the Qhsusb drivers are installed but always changes.

[GUIDE] Mega Unbrick Guide for A Hard Bricked OnePlus 5

Hello Everyone !!​
=>A hard bricked OP5 has nothing but a black screen (nothing ever comes on the screen, not even a boot logo), it might vibrate when a power button is pressed and held for 20 seconds, has no Recovery partition, no adb mode, and no fastboot partition (It might be a flickering OnePlus logo). The device might be detected in Linux and you might be able to even send commands to it. In Windows, the bricked OP5 should be detected as QHUSB_BULK,Unknown Device,Qualcomm something. You might have a bricked OP5 as a result of flashing a kernel meant for a different device (or a ROM meant for another device that included a kernel), tinkering with the boot logo or bootloader, or your attempt of unlocking the bootloader resulted in corrupting the boot partition. Most of the times, it is needed because OEM Unlocking is disabled, and phone can't boot and no recovery.
=>The solution for OP5 hardbrick is similar to OP3,OP3T- you just need a Qualcomm driver and a recovery package.it'll help to get out from one of the most weird state of the phone.(file is exact file from OnePlus)
METHOD​
This method is easy to use and flashes OxygenOS 4.5.10 on your phone. It wipes all your data and restores all partitions to stock. It will work in any condition unless it is a hardware damage.
Step 1 :- DOWNLOADS :- https://drive.google.com/drive/folders/0B7PMif5jp70BRmpSX1Nzb2JhRGs?usp=sharing
Step 2 :- Extract Drivers and Recovery Tool files on Desktop.
Step 3 :- If you are using Windows other than Windows XP,turn off Driver Signature Enforcement.To do so,follow this guide :- http://www.howtogeek.com/167723/how-...igned-drivers/
Step 4 :- Press the power button for 40 seconds to turn off the phone.
Step 5 :- Press only volume up button for 10 seconds and while keeping it pressed,connect your phone to PC.Keep volume up pressed till your device shows in device manager as [Unknown Device,QHUSB_BULK (under Unknown Devices) or Qualcomm HS USB ...... (under COMs and Ports)].
Step 6 :- Right Click on your device in the device manager and select Update Device Software. Choose the .inf file manually from x86 or x64 folder as the case implies and select Qualcomm 9008 from the listed devices.If you are unable to see 9008,see the end of post for various other methods to show Qualcomm 9008.
Step 7 :- When the device shows as Qualcomm 9008 ,go to the extracted Recovery Package and run the MSM Download Tool as administrator.
Step 8 :- Click start at top left corner and wait for it to finish (green text will come).
Step 9 :- Disconnect phone from PC and boot into system.
How to Make the device show as Qualcomm 9008​
1.) Make sure driver signature enforcement is disabled.
2.) Try these drivers,one of them might work too :-
https://www.androidfilehost.com/?fid=24052804347799753
https://www.androidfilehost.com/?fid=24269982086990168
https://www.androidfilehost.com/?fid=24349802275800175
https://www.androidfilehost.com/?fid=24349802275800173
https://www.androidfilehost.com/?fid=24349802275800171
3.)Download this :- http://www.mediafire.com/download/4a...6wc67/Qualcomm 1.00.11.rar
Keep phone disconnected from PC.
Open the folder "qc" and install the Test Certificate in the following Stores: Trusted Root, Trusted Publisher, Third-Party Root and Personal
Run the Qualcomm setup wizard (also located in the qc folder)
When completed, restart your PC again with Driver Signature Disabled. (Optional but preferred)
The driver should now automatically install. If not, go to device manager and right click "Unknown Device" and click "Update Driver" Search up the QC folder and press ok. The driver should now install.
Click thanks IF i helped you

reserved

@vasu97
We already have a dedicated thread on the same topic.

what can i edit so it won't relock the bootloader? or does it relock it?

vasu97 said:
Hello Everyone !!​
=>A hard bricked OP5 has nothing but a black screen (nothing ever comes on the screen, not even a boot logo), it might vibrate when a power button is pressed and held for 20 seconds, has no Recovery partition, no adb mode, and no fastboot partition (It might be a flickering OnePlus logo). The device might be detected in Linux and you might be able to even send commands to it. In Windows, the bricked OP5 should be detected as QHUSB_BULK,Unknown Device,Qualcomm something. You might have a bricked OP5 as a result of flashing a kernel meant for a different device (or a ROM meant for another device that included a kernel), tinkering with the boot logo or bootloader, or your attempt of unlocking the bootloader resulted in corrupting the boot partition. Most of the times, it is needed because OEM Unlocking is disabled, and phone can't boot and no recovery.
=>The solution for OP5 hardbrick is similar to OP3,OP3T- you just need a Qualcomm driver and a recovery package.it'll help to get out from one of the most weird state of the phone.(file is exact file from OnePlus)
METHOD​
This method is easy to use and flashes OxygenOS 4.5.10 on your phone. It wipes all your data and restores all partitions to stock. It will work in any condition unless it is a hardware damage.
Step 1 :- DOWNLOADS :- https://drive.google.com/drive/folders/0B7PMif5jp70BRmpSX1Nzb2JhRGs?usp=sharing
Step 2 :- Extract Drivers and Recovery Tool files on Desktop.
Step 3 :- If you are using Windows other than Windows XP,turn off Driver Signature Enforcement.To do so,follow this guide :- http://www.howtogeek.com/167723/how-...igned-drivers/
Step 4 :- Press the power button for 40 seconds to turn off the phone.
Step 5 :- Press only volume up button for 10 seconds and while keeping it pressed,connect your phone to PC.Keep volume up pressed till your device shows in device manager as [Unknown Device,QHUSB_BULK (under Unknown Devices) or Qualcomm HS USB ...... (under COMs and Ports)].
Step 6 :- Right Click on your device in the device manager and select Update Device Software. Choose the .inf file manually from x86 or x64 folder as the case implies and select Qualcomm 9008 from the listed devices.If you are unable to see 9008,see the end of post for various other methods to show Qualcomm 9008.
Step 7 :- When the device shows as Qualcomm 9008 ,go to the extracted Recovery Package and run the MSM Download Tool as administrator.
Step 8 :- Click start at top left corner and wait for it to finish (green text will come).
Step 9 :- Disconnect phone from PC and boot into system.
How to Make the device show as Qualcomm 9008​
1.) Make sure driver signature enforcement is disabled.
2.) Try these drivers,one of them might work too :-
https://www.androidfilehost.com/?fid=24052804347799753
https://www.androidfilehost.com/?fid=24269982086990168
https://www.androidfilehost.com/?fid=24349802275800175
https://www.androidfilehost.com/?fid=24349802275800173
https://www.androidfilehost.com/?fid=24349802275800171
3.)Download this :- http://www.mediafire.com/download/4a...6wc67/Qualcomm 1.00.11.rar
Keep phone disconnected from PC.
Open the folder "qc" and install the Test Certificate in the following Stores: Trusted Root, Trusted Publisher, Third-Party Root and Personal
Run the Qualcomm setup wizard (also located in the qc folder)
When completed, restart your PC again with Driver Signature Disabled. (Optional but preferred)
The driver should now automatically install. If not, go to device manager and right click "Unknown Device" and click "Update Driver" Search up the QC folder and press ok. The driver should now install.
Click thanks IF i helped you
Click to expand...
Click to collapse
Holy crap! I literally spent the last 12 hours trying to get my phone fixed. This was the only solution. Thank you so much!!!

If anyone had problems with the MSM tool "Sahara communication failed," unplug your phone. Turn it off by holding the power button for a while. Hold the power up for 10 seconds, then keep holding the volume up and plug your phone in to the PC. The MSM tool should automatically detect and restore your phone.

vasu97 said:
reserved
Click to expand...
Click to collapse
thank you so much

I've tried all the steps on multiple ports and different computers but I got always the errno 258 while loading the cache.img. Don't know what else to do...

How to correctly connect Moto X4 as Qualcomm HS-USB QDLoader device (To backup QCN)

My intention is to backup QCN of my Moto X4 (XT1900-1). Currently I installed Motorola latest USB drivers and installed Qualcomm HS-USB QDLoader.
Device is booted with BP mode and Windows (7) shows three other devices called "moto x4" with a device called "RmNet". I select the first device then right click -> update driver -> let me pick from the list -> Motorola "USB QC diag" and force install it.
However when I launch QPST (2.7.472) at the port's tab COM15 appears however at "phone" column it shows "?(0)". When I try to backup the QCN I'm only getting 4kb of data and QPST shows "memory error"
I tried QFIL also, it's backup/restore buttons are getting disabled when I choose that specific port.
I tried the same sequence in two other Windwos PCs (Win 10) same results.
Did anyone successfully backed up QCN before? can you share the details. Thanks

QPST with QFIL Flashing Sahara Error Solution

the solution of this error is simple.
just install proper qualcomm drivers from latest qpst setup . cause it includes the drivers too.
now just short the name of firmware folder to short form.
now open qpst or qfil, select firmware folder and select
rawprog_emmc_ufs_firehose_Sdm660_ddr.elf
then rawprogram unspare no nfc no fsg.xml '
then patch0. xml file
after that this is the main thing.
press vol + and vol- buttons together and put it into edl mode
and now connect it to the pc with cable . don't do anything till qpst or qfil not recognize it byself.
it took 30 sec to recogniz for my time.
it will take more for you may be. now download button will become available .
just click on it and now flashing will start without any error .
i was getting this error cause i was putting the device edl mode and connecting it to pc before opening of qfil or qpst.
you had to connect it after opening the qfil or qpst then you will not get any shara errror.
and have to wait at least 30 sec don't do anything till then . and after that windows will sound of connecting and that's it.
start flashing without shara error.
another solution:-
Copy firmware folder (imges) into
cdrive/programmer files/qualcomm/QPST/bin
2- Than open QFIl Select Programme Files .mbn
then both .xml Files From Cdrive where U copy
3- Now Close QFIL
4- Now Connect Handset Into Quacomm Mode (hs-usb , edl , download etc )
5- Open QFIL Again
Already Post Selected
6- Now Press Download
SUCCESS
latest qpst download from this site:-https://androidmtk.com/download-qpst-flash-tool
also try this in offline mode like remove all internet connection or wifi disable or enable airplane mode on your pc or lapto

Can post a link of QPST that you used

DJ AJB said:
Can post a link of QPST that you used
Click to expand...
Click to collapse
still getting shara error which version of winodws you using
if using windows 10 disable driver signature enforcement first then install qualcomm drivers perfectly included in qpst
after that open qfil or qpst now select all files and after that boot device in edl mode and connect it now to the pc rember dont connect with pc before qfill or qpst open now with usb cable wait for atleast 40 sec if it get recognize . download button will become available ,just click on it and start flashing

Thanks a lot it has successfully finished

When I do this I always receive:
2021-07-13 14:27:51.932 Download Fail:FireHose Fail:FHLoader Fail: process fail
Can someone give me any advice?
I also included my log.file

I waited for long, i had to selec the port as it says
im lost

Question Redmi note 10S not recognized MiUnlock

I own a Redmi note 10S having the MIUI EEA 13.0.5.0 installed on it.
I need or to downgrade toward the 12 or to upgrade with a Global 13.0.8.0.
To do that I have to unlock the bootloader.
I have tried to unlock my phone following the Guide
"Complete Guide to Unlocking the Bootloader: Announcement, Troubleshoot and Tips"
Xiaomi Community
new.c.mi.com
Completely performed the "Step 1: Phone" phase
But I am stuck into "Step 2: PC" phase
I downloaded and launched the "Mi unlock" program, version 6.5.406.31
Updated the driver with settings option --> "click the button to install the drive"
Obtained the confirmation
"Mi USB driver installation
Installed drivers successfully"
But the program is still locked into
"Not connected to the phone" screen.
Note: With Phone into Fastboot mode the OS Windows 10, under device manager identify the phone with the icon
"Other device" --> "Andorid" with the Yellow Triangle with Exclamation Point inside
In addition with the Phone in Fastboot mode there is a continous OS disconnect and reconnect sound of the system.
An attempt has been made to solve the problem following the indication in
Mi unlock/USB keeps connecting/disconnecting
I was wondering if anyone experience the same. I want to unlock my bootloader but everything I connect my phone (in fastboot) to PC I hear windows connecting and 2 seconds after that disconnecting in loop. Mi unlock therefore doesn't see my...
forum.xda-developers.com
* Disabled the signature enforcement --> Achieved by enabling the operating system Test Mode through Power Shell
* Download and installed the driver Redmi Note 10S - Mediatek Driver
without improvement
NOTE: the verification has been performed with both Intel and AMD systems.
Then the following attemp has been performed:
(following the information reported in
)
Installed --> adb-setup-1.4.3
With the smartphone normally running, it is identified with its numbering by means of
PowerShell --> "adb device" command
But anyway, after swith into Fastboot mode the phone is still not recognized by the software.
Thanks for any help you can give me

wrong drivers
https://dl.google.com/android/repository/usb_driver_r13-windows.zip --> install those with device manager once "android" appears

Thnanks for your help, but it does not working
Smartphone in fastboot mode, connected to pc by usb, open device manager
Select "Android" under "other device", Right click, update driver, find driver into pc
Select the folder "usb_driver_r13-windows"
but the system provide the error on the installation phase: Unable to install Android - Cannot find drivers for your device

quite odd, surely you are using the wrong versions of drivers

Yeah I know that the installed (and the driver that I try to install) are the wrong one.
But I cannot understand which is the correct one.

[TOOL][WINDOWS] ADB & Fastboot++ | February 2023
NFO: • Versions: Installer, Portable & ADBKit • Android Debug Bridge & Fastboot updated to latest v1.0.41 (Version 34.0.0-9570255, February 2023) Features: • Installation Folder chooseable (Installer) • Desktop & Start Menu Shortcuts (Installer)...
forum.xda-developers.com

Thanks, now it is recognized in fastboot mode

Deleted