Recovering Moto g4 plus XT1643 from HardBrick !!! - Moto G4 Plus Questions & Answers

Recovering Moto g4 plus XT1643 from HardBrick !!!! Its possible. I recovered my moto g4 plus.
NO fastboot, No recovery, just black screen, white led blinks when connected to charger or laptop.
My moto device did not turn on after system update. No reaction was there when i pressed the power button. I also tried to press power button for 2 mins , vol down + power button for 2 mins but there was no reaction. Then only i found that my device has hardbricked. I given the mobile to Service center but they advised to change the board.
I searched in internet and found some recover method for a hardbricked device.
To recover the device you need the following
Bricked device
USB cable
PC
Internet Connection
Connect your mobile to PC and open device manager in PC, you should see your mobile is detected as QBULK in unknown device or as qualcomm hs-usb qdloader 9008 in COM port.
If your mobile is not detected try pressing power button and volume button for somtime.
If your mobile is detected as qbulk, you should install qualcomm driver in pc. (Link to download is at the bottom)
Download all the files given at the bottom link.
Run "testing_mode.bat" file with administrator rights. After that restart you PC.
You should see "testing mode" at the bottom right corner of the desktop.
Ensure that mobile is detected as qualcomm loader in Device manager. Then run the Blankflash.bat file. I have given four blankflash files try one by one. One of which supported for me. If it says waiting for device then press and hold power and vol - button and then run the blank flash file. Try many times, it may not work in the first time.
If the file execution completes successfully then your phone must boot into fastboot mode.
Thats it your device is recovered. Connect your phone to pc in fastboot mode and flash the rom. There are many tutorials in internet for flashing rom through fastboot.
In some cases there is no need to flash the rom.
Try to boot into system if it says partition tables corrupted. Flash only the gpt.bin, bootloader.img, logo.bin. Then your phone should boot into system. If it does'nt then you have to flash the full rom.
Fastboot flashing procedure:
1. Connect your phone to PC in fastboot mode.
2. Extract fastboot.zip Open the folder Fastboot.
3. Then run flash.bat.
If it completes successfully, thats all.
If this does'nt solve you need to flash the full rom.
Hope it might be helpfull for some one.
Download links:
Blankflash files URL ( drive.google.com/open?id=0B7g8t64wbC7BRV9FalZKb09Gc2s )
Fastboot URL ( drive.google.com/open?id=0B7g8t64wbC7BVU5RanF5Q29yTVE )
Testing_mode file URL ( drive.google.com/open?id=0B7g8t64wbC7BeEFwMVhkVENib00 )
Qualcomm driver URL ( drive.google.com/open?id=0B7g8t64wbC7Bbll5WF9HbU9jblk )
Password for zip files is 886842

If you make a guide, don't miss to mention for what rom release version it is. Otherwise you receive some negative feedback. Did you realize that there's a guide for the actual June security patch already if your guide is for the same rom https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-hardbrick-solved-guide-t3657761 ?

Thread Closed - Duplicate
Previously posted thread HERE

Related

[Guide] Un-brick both (Soft/Hard) bricked Zenfone 2 ze550ml/ze551ml.

Unbrick Zenfone 2 ze550ml/ze551ml​Tutorial how unbrick (save) a cable suspended Zenfone 2 (lost bootloader) absolutely can not use or connect ADB recovery, fastboot to perform the operating system reload. Have to say this is the measure of last resort that you can perform with the Zenfone his second before the machine is required to submit to ASUS support.
How to know that your Zenfone 2 is bricked ?
>> Device can not start, only logo ASUS quite awhile now off. If you use keyboard shortcuts to access cluster bootloader (droidboot), display the cable connection icon which is usually called "the hanging cable."
Device can not connect to your computer regardless of whether in any mode (including ADB, fastboot), this leads to not be able to use ADB fastboot.
Cause: Loss bootloader
Damaged in a bootable partition.
-Most Of the cases are droidboot.img can flash the wrong file by other files as boot.img, recovery.img or get confused by any other machine on the line.
-Case Rare than natural bootable partition defective (not by you impact) or in some cases droidboot.img flash file into the machine suddenly collapsed sources can also occur.
The issue of "hanging cable screen" on Zenfone 2:
-Not Like Zenfone front lines, as his son Zenfone 6 was holding here, he was not sure the cable hanging screens you skipped bootloader, I can still access the bootloader, normal recovery. While on Zenfone 2, once encountered this phenomenon, make sure the machine's bootloader has been lost, this time ADB and fastboot recovery is meaningless.
How to unbrick?
This section explains how unbrick, you do not need sports references may skip and go to parts made right. You are using the Zen series (fone / pad) platform using Intel chips may also refer to similar application for its line, of course, will not be quite the same.
-When Your units with brick Zenfone 2, meaning lost bootloader (in this case), you can not lead to any use fastboot mode to flash the ROM file anymore. Typically, in this case, then one would have to use some special tools to be able to load directly into memory (memory) of the lower level as the bootloader using box, the second in the testpoint or the second machine sprung straight into memory ... However, for the mobile Intel chips sales are done with relatively simple parts, they provide a driver called IntelSocUSB available, when necessary Equipment using bootloader, you could still lose the connection with your computer via lower IntelSoc mode for use in emergencies.
IntelSoc edge-side connection, you also need to use additional software xFSTK Downloader, the tool support is simply loaded bootloader instead of using complex command lines. Unlike the methods used img file, which is when you already have a bootloader, as available "basis" can thus use only 1 img file. In contrast when used xFSTK Downloader you must have 2 file dnx_fwr.bin and ifwi.bin firmware, bootloader file same file simultaneously in the form of a new bin can be loaded into the device.
-Once You have successfully loaded bootloader can easily use tools like ADB fastboot nap ROM or ASUS FlashTool to bring "life" to return to the their Zen2 then.
Perform:
You must perform sequential follow the steps indicated below, a process steps will include many small, you also need to do before the next turn. Since there are many different levels and its brick is just so normal users can not list them all the way, I will try to extend to all cases that may occur, you just follow the sequence guidance, if encountered other problems please cmt for further discussion.
Step 1: Install the driver and connect mode IntelSocUSB IntelSoc
-This Is the driver help with a computer connected to your Zen2 IntelSoc mode as mentioned above. Because of this special driver, on some machines running windows 8 / 8.1 / 10 you can not install the normal way is that to add a little more tricks, not too hard, I'll complete list Under.
1.1 - Install IntelSocUSB
-First, Please disconnect the machine Zenfone your 2.
-Download Driver IntelSocUSB here:
drive.google.com/file/d/0B2oMRhweQ4CHbURUNk1ZTHI2Mjg/view?usp=sharing
If you're using Windows 7:
Right-click the file -Click iSocUSB-Driver-Setup-1.2.0 choose "Run as Administrator".
-Make The installation steps as usual until you see a small window "Windows Security" requires authentication settings then click on the "install this driver software anyway"
-After This step, the driver installation is finished, continue to section 1.2 for connecting IntelSoc regime.
If you're using Windows 8 / 8.1:
-On Keyboard press Windows + I to show charm bar bar in the right corner, click on the item setting.
Choose "Change PC Settings" to enter the PC Settings.
Choose the General tab and navigate to Advanced Startup section, continue click Restart now.
This force will reboot windows and allows you access to the advanced mode, in turn selected the following items: Troubleshoot - -Startup Settings Advanced Options and then click the Restart button to restart the computer.
-Continue Press 7 on the keypad to access the installation mode allows drivers.
Right-click the file -Click iSocUSB-Driver-Setup-1.2.0 choose "Run as Administrator".
-Make The installation steps as usual until you see a small window "Windows Security" requires authentication settings then click on the "install this driver software anyway"
-After This step, the driver installation is finished, continue to section 1.2 for connecting IntelSoc regime.
If you're using Windows 10:
-On Keyboard press Windows + I or click Start, select Settings.
-In The Settings window, select the Update & security.
-Continue Choose recovery and click "Restart now".
-When The computer has access to the Advanced screen, how similar startup with Windows 8 above.
-After This step, the driver installation is finished, continue to section 1.2 for connecting IntelSoc regime.
1.2 Connect with computer IntelSoc Zenfone 2:
After driver installation step above 1.1 as successful you are in a window like this, do not click Next yet. Now you must complete step IntelSoc connection before installing xfstk downloader.
-The Device manager: right-click the Computer icon, select Manager, find the device manager.
-In Device manager, to IntelSOC, click the down side, you only see the present only one item is Intel SoC driver.
Ash back to the Zenfone 2, shutdown, press simultaneously the key "source" + "volume +", of course you will see a screen hanging cables.
-Connect to your computer via USB cable, to standard Intel SOC driver position, wait a few seconds if the current add an item immediately below another MOOREFIELD new devices is successful.
-If You have not been, the test performed as follows: turn off the machine, plug the cable into the computer, press the power button until the device vibrates slightly, then release.
-This Is a required step to complete before performing next.
Ash back window IntelSOC earlier installation, click Next and Finish.
1.3 Installing xfstk-downloader:
Download xFSTK Downloader v1.7 here:
drive.google.com/file/d/0B2oMRhweQ4CHbDNQdy1jVUJFcEE/view?usp=sharing
-Download And install with a setup similar to IntelSoc Driver guided above is, simple installation process does deserve to be noted.
-That's It step 1.
Step 2: Use the Downloader to reload the bootloader xFSTK
This is a tool to support the new bootloader loaded into memory chip straight soc IntelSoc mode.
XFSTK load Downloader v1.7:
drive.google.com/file/d/0B2oMRhweQ4CHbDNQdy1jVUJFcEE/view?usp=sharing
-The Necessary files:
ZE551ML: drive.google.com/file/d/0B2oMRhweQ4CHR21YaDdXdUNlOGs/view? Usp = sharing
ZE550ML: drive.google.com/file/d/0B2oMRhweQ4CHcHg4WXJQckFGOTA/view? Usp = sharing
After downloading the necessary files extract to a separate folder 3 file dnx_fwr.bin, ifwi.bin, bootloader.
-Open XFSTK Downloader, first passed MRD tab A0 / B0 + A0 + CRC as shown Moor.
-Then Go to Options to change the value in the Value section Override Flag GP 0x80000807. Click OK is complete initial preparation.
This force remains connected to the phone cable.
Begin the process of loading the bootloader:
+ First in turn selected item Firmware FW 2 cells and IFWI DNX 2 dnx_fwr.bin and ifwi.bin file.
+ Section IFWI: skip the first box, in the box looking to file droidboot_dnx.img.POS_sign.bin Image OS, here is our bootloader files.
Now let's go to the Device Status section below, this section shows the number of connected IntelSoc, you need at least one device is connected. If in step 1 you do succeed, make sure xFSTK Downloader also get equipment, if not retry the connection cable.
Just click on the download button to start Begin implementation.
-Here You may see error faild continuity however kept calm to software performance. Until now informed SUCCESS as shown below, then congratulate you, our problem is almost solved.
The process is loaded bootloader successful restart when you will not see another familiar ASUS screen but instead is a 4 color, just like some TV stations stop broadcasting on TV.
Shortcuts in bootloader test can not yet see. Now you can load the ROM via fastboot mode / droidboot and know.
-If Not know how to do this, see step 4. If the flash ROM or flash via fastboot not finished still not on the operating system, your computer would be heavier than normal, continue to step 3.
-Note: Hanging cable phenomenon will appear again if you are not successful flash ROM. Each drawing shows the cable hanging out, you need to perform this step 2.
Step 3 (if applicable): Using ASUS FlashTool reloaded raw files.
Here's how to load ROM via fastboot mode is considered as the most supportive.
Download ASUS FlashTool 1.0.0.14: the previous version can not support Zenfone 2.
https://drive.google.com/open?id=0B4uMV7GwfDAEYm5RWTFydXZWOTQ
Download firmware for ZE551ML 2.20.40.194 raw format here:
https://drive.google.com/file/d/0B0v_vGzEh1G5WU1QTzlTOExIekU/view
Version for ZE550ML 2.20.40.155 raw format here: https://yadi.sk/d/XAUyR8eRtuKdA
Installing ASUS FlashTool resembles IntelSoc describes how to install the above, you also need to fully implement the steps before the installation on your Windows 7.8.10 will not repeat again.
-To Phone droidboot mode / fastboot, connected computer, enable ASUS FlashTool.
ASUS FlashTool -On screen, in the model of your selected device (ZE551ML / ZE550ML). Part wipe data option. Click the button next to wipe data section to find raw files downloaded above.
Below current frame connected devices, if not try to wait for a few minutes, plug in the cord, if not you are required to reinstall the driver IntelUSB (this does not lead his popularity and link again).
-Click Select your device and press the Start button to begin implementation.
Firmware loading process long-range 5 to 10 minutes. Then the machine will automatically boot into the operating system, if successful, congratulations to you.
Note: It is possible at this stage you will not succeed with the process of loading raw files, the software itself runs completely without any notice. If this process occurs too 30p then your job is forced to withdraw cable.
-Mark Whether the file import process may not succeed but at least Flash Tool ASUS sent commands resize partitions, if the command is successful, then the partition on the device has been fixed and you was able to load the ROM type fastboot okay, do the next step 4 preview successful offline.
Step 4: Use a rechargeable Fastboot img file.
The last pitch to bring life back to the two of you here Zenfone.
-There Bootloader means you can use fastboot to flash ROM img format already.
Img -Download the latest ROM for Zenfone 2 here:
-Choose The appropriate ROM version (ZE551ML / ZE550ML) and download all the files in that directory, links to download: mega.nz/#F! K4MHiAgL! DVuOKeH3eokcwPSNI79ffw! Xwc0BJrY
-Use Manager winrar or any unzip the archive file will be system.img system.zip
-Copy Boot.img, droidboot.img, recovery.img, system.img in the folder C: \ adb adb install directory or your.
-file SplashImage here:
fshare.vn/file/2KIL3GQ1NZN2
General similarity copied to the folder with the other files.
Open ADB made the following statement:
Code:
fastboot flash splashimage splashimage.img
fastboot fastboot flash droidboot.img
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot reboot
Added to index, thanks for your work!
cmendonc2 said:
Added to index, thanks for your work!
Click to expand...
Click to collapse
My another Guide to Recover Fastboot of bricked Zenfone 2 ze551ml
http://forum.xda-developers.com/zenfone2/general/guide-recover-fastboot-bricked-zenfone-t3284337
Thank u very much for this tutorial
Z008
Raw firmware link added for ze550ml users
is it normal for my "MOOREFIELD" to appear temporarily?
Should i continue despite my detect = 0 since it appear temporarily?
I have a few corrections that I have to figure out myself in order to get through, I hope these are a translation problems and can be solved easily.
First of all, the links for Z008 (raw image) is misspelled and contains bad characters (the "*"s). And the Fastboot image link is misspelled too or broken, either of them, therefore, I had to look in the index for those.
Then, The Asus Flash Tool AFT the version provided is 1.0.0.7 which is very old and doesn't support our phones, then I had to look up for the newest one (or even compatible) which is 1.0.0.14. Then the flashing instructions in xFSTK are confusing because there are 3 files to flash (explained better on the other post) FW DnX is the Dnx, IFWI is IFWI, OS DnX is blank and OS Image is the droidboot. That is much simpler.
The part of the explanation of how to use the AFT is almost unredeable. It's just simple as choosing the model, choose to Wipe Data (yes), look for the raw image, selecting the phone with its serial number (btw, the installation of the drivers was a little messy since the AFT Install couldn't install them).
Don't misunderstand this reply, this guide was very useful to me, but I correct this for the ones that encounters this problem. I succeed unbricking my zenfone after it went to the USB Logo by itself (I still don't know why would this happens since I didn't touch the fastboot, but it clearly shows that this cases could happen to anyone).
nanofives said:
I have a few corrections that I have to figure out myself in order to get through, I hope these are a translation problems and can be solved easily.
First of all, the links for Z008 (raw image) is misspelled and contains bad characters (the "*"s). And the Fastboot image link is misspelled too or broken, either of them, therefore, I had to look in the index for those.
Then, The Asus Flash Tool AFT the version provided is 1.0.0.7 which is very old and doesn't support our phones, then I had to look up for the newest one (or even compatible) which is 1.0.0.14. Then the flashing instructions in xFSTK are confusing because there are 3 files to flash (explained better on the other post) FW DnX is the Dnx, IFWI is IFWI, OS DnX is blank and OS Image is the droidboot. That is much simpler.
The part of the explanation of how to use the AFT is almost unredeable. It's just simple as choosing the model, choose to Wipe Data (yes), look for the raw image, selecting the phone with its serial number (btw, the installation of the drivers was a little messy since the AFT Install couldn't install them).
Don't misunderstand this reply, this guide was very useful to me, but I correct this for the ones that encounters this problem. I succeed unbricking my zenfone after it went to the USB Logo by itself (I still don't know why would this happens since I didn't touch the fastboot, but it clearly shows that this cases could happen to anyone).
Click to expand...
Click to collapse
I will try to update all the links and make my post more clear as soon as possible .
Thanks for doing corrections in my post .
Unfortunately, I've encountered some other issues after I succesfully unrbricked my Zenfone. I must say that I quite step away from some of the steps since after I flashed the RAW Image file on the AFT I successfully boot into system. That means I skipped the flashing of the other img droidboot, boot, recovery and system images provided. Then, when I tried to flash TWRP back again, I noticed that even though the flash was succeed, trying to boot in recovery mode lead me back to fastboot mode, pointing out that recovery partition is still damaged. Maybe I need to flash the RAW again to repartition, but since the phone works now I don't want to touch anything again. I can still flash things through fastboot though, the Xposed, the root image, etc. But it seems like I don't have a recovery functional.
The sources for this are still very poor and we need to bring it all the things that the Russian, Vietnam and Chinese forums were posting all this time about the ubrick thing, maybe there's something that I've missed.
Did anyone try to download the system images from that Mega page? I found the link somewhere but the compressed files seems to be corrupted (for the Z008), I would appreciate if anyone else can confirm this.
issue with serial no.
AFT fail to flash coz of serial don't match with actual serial no. of phone
any solution
aniruddha007 said:
issue with serial no.
AFT fail to flash coz of serial don't match with actual serial no. of phone
any solution
Click to expand...
Click to collapse
Which version of AFT are you using?
Explain what do you mean with "doesn't match" I didn't have to check the serial number at any point.
http://mega.nz/#F! K4MHiAgL! DVuOKeH3eokcwPSNI79ffw! Xwc0BJrY
Link dead, new link pls
nanofives said:
Which version of AFT are you using?
Explain what do you mean with "doesn't match" I didn't have to check the serial number at any point.
Click to expand...
Click to collapse
it checks for serial no. of device n fails
so i tried to flash twrp.img using fastboot but got an error "flash_cmds error!"
plz help me guys
As this is an error that was not reported when I was reading through all the foreign forums, I have to state the obvious since I don't have a particular answer.
I assume at this point that you have all the proper drivers, therefore the AFT shouldn't recognise the device. So... what I think is, is your phone in fastboot mode? (I mean the fastboot mode with the 4 colours instead of the ASUS Logo). Maybe there could be a failure in the process of unbricking with the xFSTK downloader.
Add source
please add source bro, this's my tut
amtech. vn/threads/un-hard-brick-zenfone-2-giai-phap-cuu-may-cuoi-cung-truoc-khi-den-trung-tam.370362/
remove blank after "."
---------- Post added at 07:48 PM ---------- Previous post was at 07:44 PM ----------
And thanks for translating :angel:
---------- Post added at 07:58 PM ---------- Previous post was at 07:48 PM ----------
aniruddha007 said:
it checks for serial no. of device n fails
so i tried to flash twrp.img using fastboot but got an error "flash_cmds error!"
plz help me guys
Click to expand...
Click to collapse
you can't use fastboot to flash img file because some partitions still have error.
You must use AFT, try check your cable and run AFT as Admin.
---------- Post added at 08:02 PM ---------- Previous post was at 07:58 PM ----------
@nanofives
it show the 4 colours because it have no splashimage
yes its in fastboot mode
nanofives said:
As this is an error that was not reported when I was reading through all the foreign forums, I have to state the obvious since I don't have a particular answer.
I assume at this point that you have all the proper drivers, therefore the AFT shouldn't recognise the device. So... what I think is, is your phone in fastboot mode? (I mean the fastboot mode with the 4 colours instead of the ASUS Logo). Maybe there could be a failure in the process of unbricking with the xFSTK downloader.
Click to expand...
Click to collapse
oh yes its in fastboot with 4 colour
I have problems in 4-color screen.
Everything I do ok.
I need help from you ...
Thank you very much
What are you trying to do? The process is stuck somewhere?
Enviado desde mi ASUS_Z008 mediante Tapatalk
@salsav3i
Bro i didn't knew that this is your guide , i got this guide in Vietnamese language from my friend who lives in Vietnam
Hi, does this lock my bootloader?

Redmi 3 Pro Considerations - Flash global ROM with BOOTLOADER LOCKED

I've tried some things on my Xiaomi Redmi 3 Pro and I want to share them if helpful for someone.
I've done all this with Xiaomi.eu Rom and SMIUI
///// I'm not accountable for any problem on your phone, do it at your own risk! \\\\\​
1 - Button combinations (unplugged from pc):
vol+ & vol- & power = force shutdown if in fastboot or download mode, if powered-on it's a restart
vol- & power = from switched-off phone goes in fastboot (from there you can launch another combination: vol+&vol- while launche cmd: fastboot.exe reboot)
vol+ & power = preload\ bootload mode (the yellow screen where to choose recovery\ fastboot\ download mode)
2 - For any type of problem \brick \ bootloop be sure before about this:
A) if you run the phone in fastboot mode, check if you can see it in fastboot command line from pc (cmd: fastboot devices)
B) if you run the phone in download mode, check if you can see it from miflash
If these point are ok this means the pc is ready to see the phone if you softbrick it or it goes in bootloop.
You will be always able to run it in fastboot mode, then download mode, an flash any rom to the phone that works.
3 - What you need?
Install last version of MiFlash, here a guide: http://en.miui.com/thread-272376-1-1.html
Install MiPCSuite in english, here the link: http://pcsuite.mi.com/
If you have problems with ADB, install ADB drivers, here the link: http://forum.xda-developers.com/showthread.php?p=48915118#post48915118 or http://forum.xda-developers.com/showthread.php?t=2317790
If you have problems with hs-usb qdloader 9008 driver, try to install from here: http://www.androidbrick.com/download/qdloader-hs-usb-driver/
Download and upack Android.Image.Kitchen for Windows, from here: https://mega.nz/#!McAj2SZT!E4XS7II27BjkjSHS2vcBnE6Tgvl8IZBhCD2wEKBchpA
Download TWRP 3.0.2.0 for MiFlash: https://mega.nz/#!cF4VVQiY!zrq2DTQRBX3UHRPOXN1dDNWiTn5tnoPxUfrHF_Rsnq4
Download ROM from different links:
http://en.miui.com/a-234.html (miui china stock, BL Locked)
https://www.androidfilehost.com/?w=files&flid=36337 (Xiaomi.eu with Gapps, no Bloatware, BL unlocked)
http://smiui.net/kitchen.php(Xiaomi.eu + other stuff)
Install Notepad++
4 - Prepare ROM:
As suggested by the user Jack0190 there are ROMS where is not needed to mod this files, like for "Xiaomi redmi3 pro locked multilanguage" roms.
Searching on web you can find them quickly, just be aware that there are some roms that have problems with SIM recognize. This comes from an old Thai \ Indian MIUI.
I've seen first this thread on en.miui, http://en.miui.com/thread-276565-1-1.html , where explains how to modify ROM to change the bootloader check. The guide explains very good how to modify the "boot.img" file of roms.
So just follow those steps.
I've seen that you can do it for both types of rom, for Recovery and MiFlash too.
For the recovery ROM, you have a file to open in 7Zip, copy the "boot.img" from it, modify it as explained in the guide, and re-copy in the zip file again.
While for the one for Miflash, it's easier; extract the rom, copy the "boot.img" file from \image folder, modify it with, and change it in the original folder. Then flash it with Miflash.
5 - Connect phone in Fastboot with pc:
One thing that always will save you is the ability to connect phone in fastboot mode.
Before start the phone in fastboot mode with cable unplugged (point 1).
Once you've installed Miflash, go on it's directory folder (C:\Program Files\Xiaomi\MiPhone\), and run cmd from there (shift+right mouse click).
Connect phone to pc.
Then run command "fastboot.exe devices" and if the result under the line on left is a code, the phone is recognized
6 - Force Download Mode from fastboot:
To force the phone to go in dowload mode, first run it in fastboot (point 5), check if it's recognized (point 2-A), then type but don't run command "fastboot.exe reboot".
Now push vol+ & vol- in the same time, and now run the command.
If it runs in the right mode, you can see it's connected by device manager under "Ports (COM &LPT)" section.
You will see "qdloader 9008 driver" with a COM port installed. The same port you will see in Miflash if you run it and push the "refresh button".
7 - Flash Job:
A) First you need to flash the recovery, TWRP, and to do this you should already have done this things:
Install Miflash, MiPcSuit
Your phone is right seen in fastboot and in Miflash in download mode.
You have downloaded the right versione of TWRP for MiFlash.
B) Flash TWRP with Miflash
Select in Miflash the button "Browse" and go to the folder "\Image"where you have extracted the TWRP zip
Click "Refresh"
Click "Flash"
Wait to complete (If it fails sending hello packets, it's because it's too much time the phone is in download mode, in this case, switch it off, e restart in Download mode and re-do all )
C) Copy modified ROM:
Now, I've done this step by OTG connection but there are more ways to do it:
Connec and mount an USB Drive in OTG
Push it by ADB
Copy it by SD card
If the old ROM still works, copy it in MTP connection
if none of this options is available, flash the Rom with Miflash, flash again TWRP recovery, run recovery, wipe cache and dalvik (factory reset option under "Wipe") and try to run system, it should run last system flashed.
D) Flash modified rom by recovery
E) Restart in system (It could take long time, even 10 minutes, so just wait for it)
Thanks to all users\ people helped me with different guides from XDA and other forums.
I' m sorry for no image, but it's not an official guide.
If something is wrong I'll change it asap, but don't blame me, these are just advices.
If it's not enough clear, search it on web.
If there are grammar errors, the Image verification confirms "I'm not a robot"
If you don't find the answer, then it's 42.
After mod, i can flash rom update from recovery?
Inviato dal mio GT-I9505 utilizzando Tapatalk
Just wanted to say thank you - This guide works. I tried it with a new redmi 3 pro with locked bootloader. You can skip step 4 if you want to, because there are some prepared images available (search for "xiaomi redmi3 pro locked multilanguage" and you will find them).
Also to note: The first boot of the new system took some long time (~ 10-minutes), so don't get frustrated. As long as there's the android logo with the three dots wandering around, everything should work fine.
- Jack
RuLe89 said:
After mod, i can flash rom update from recovery?
Inviato dal mio GT-I9505 utilizzando Tapatalk
Click to expand...
Click to collapse
not sure about this, I've flashed the last version available, so i don't have updates for now to test.
But i think that it could overwrite files modified.
This is what in some guides tells.
Jack0190 said:
Just wanted to say thank you - This guide works. I tried it with a new redmi 3 pro with locked bootloader. You can skip step 4 if you want to, because there are some prepared images available (search for "xiaomi redmi3 pro locked multilanguage" and you will find them).
Also to note: The first boot of the new system took some long time (~ 10-minutes), so don't get frustrated. As long as there's the android logo with the three dots wandering around, everything should work fine.
- Jack
Click to expand...
Click to collapse
Thanks to you, I've updated with what told. I've tried some of ROMs for locked bootloader, but was an Indian \ Thai version, and I had issues with SIM, no recognize.
That's why it was needed for me to use other rom for unlocked bootloader.
Hi, thanks for the guide. It seems like it'd be the only decent I could come across for my problem.
The only thing is that everytime I try to flash any ROM/image through MiFlash, I get the error:
Code:
Error loading type libary/DLL.(0x80029c4a: wait port ready to use <time in seconds>)
So far I haven't found anything or anyone that could help me with this. Can any of you help me out here? That'd be much appreciated.
Thanks~
----------------------------------
::Edit::
Alright, turns out I just had to do this:
1. Uninstall the Qualcomm drivers
2. Reboot Windows into "test mode"/Disabled driver signature enforcement
3. Reinstall the Qualcomm drivers
4. Flash device (phone in download mode)
5. Be very pacient. Waiting through the phone's boot phase
(took about 10 minutes; if it takes more than 15 minutes, then something is probably wrong. Try to enter download mode and flash it again.)
6. Redmi 3 working again
Okay, so, this worked for me, it doesn't mean it'll necessarily work for you!
This was done with a locked bootloader and MiFlash 2015.10.28.0

Need some help after messing up my Lineage OS installation on A2017U

My phone has no OS. Factory reset is unavailable to my knowledge (attempted volume up and power).
I can go into fastboot and TWRP, but I can't seem to install the stock OS nor Lineage OS. In fastbootmode, I see the following
Product name - AILSA_II
Variant - MTP eMMC
Bootloader version -
Baseband Version -
Serial Number 9e28c2da
Secure Boot - enabled
Device State - unlocked
Click to expand...
Click to collapse
I cannot use ADB commands. My phone isn't listed under ADB devices. EDL does not work. However in Fastboot mode, MiFlash recognizes a device 9e28c2da. Whenever I try to flash a full EDL however, miflash brings up errors saying it cannot find script and it cannot find file.
When attempting to install in TWRP, I get the respective errors "Invalid zip file format!" for "A2017U_B19-NOUGAT_FULL-EDL.zip" when I try to install the stock. When I try to install Lineage, I get "E3004L This package is for device: ailsa_ii,axon7; this device is ."
I am able to successful install A7LOSv1_UniversalBootStack.zip as well as the UniversalBootstack by DrakenFX. I then install OreoModem.zip after that, but the phone won't let me install any OS afterwards.
Am I trying to install the wrong arrangement of files? What can I do to get an OS back on my phone?
Firstly it sounds like the drivers need an update.
Try updating the USB drivers and try Zadig drivers as well.
Your PC/laptop should see your phone as ...
"Qualcomm HS-USB QDLoader 9008"
In the device manager on Windows. If you are using Miflash it should see it as Com 4 or similar.
Make sure you have the correct Edl package for your phone eg: A2017G, A2017U or A2017.
Extract the Edl package using WinZip or Winrar and take note of the folder name and location.
Boot your phone into Edl mode, via button, adb command or using the Edl tool by @djkuz
Open Miflash tap refresh, if it sees com4 or similar you are good to go.
Tap the browse button and pick the Edl package location on your PC/laptop and then tap flash.
The flash will take a few minutes and when done you will get a green flash success.
Unplug your phone and press and hold the power button till it boots.
Hope this helps
If you get stuck,
I have an Edl help page here >
https://forum.xda-developers.com/axon-7/help/bad-flash-help-page-axon-7-t3839700
There are many others on XDA too

My phone is stuck on the fastboot screen

PLeaseeee help me I have a rooted oneplus 6t. I performed a backup and wipe in hope to clear a problem and am now stuck in fastboot mode (tried to restart,power off everything). Im pretty sure as I tried to reboot it said no os detected, and then I got stuck. I have tried to install the latest oxygen os by manualling flashing 4 files. all tutorials i read have bootloader and other files while i just have - system_matrix , system_manifest , vendor_matrix, vendor_menifest (XML files by the way). I have flashed these files and rebooted only to go back to the fastboot screen. There is also a payload.bin file when i try flash that i get a FAILED (remote: Error flashing partition : Volume Full) error.
Erick Rajan said:
PLeaseeee help me I have a rooted oneplus 6t. I performed a backup and wipe in hope to clear a problem and am now stuck in fastboot mode (tried to restart,power off everything). Im pretty sure as I tried to reboot it said no os detected, and then I got stuck. I have tried to install the latest oxygen os by manualling flashing 4 files. all tutorials i read have bootloader and other files while i just have - system_matrix , system_manifest , vendor_matrix, vendor_menifest (XML files by the way). I have flashed these files and rebooted only to go back to the fastboot screen. There is also a payload.bin file when i try flash that i get a FAILED (remote: Error flashing partition : Volume Full) error.
Click to expand...
Click to collapse
Use MSMtool to unbrick your device.
You can search to find the link..
indian84 said:
Use MSMtool to unbrick your device.
You can search to find the link..
Click to expand...
Click to collapse
Thanks followed some tutorials on MSMtool and go it unbricked ! really appreciate it
For anyone running into a similar problem these are the steps I used
1. Download and extract files
a. Qualcomm drivers
b. MSM Oneplus 6t download Tool
2. Disable Driver Signature Enforcement by restarting your pc whilst holding shift, Choose trouble shoot, then going into more recovery ,select Advanced Options > Startup Settings > and then click on Restart.
3. Now PC will restart and Now you will see a list of startup settings that you can change. Select option 7 ‘Disable Driver Signature Enforcement’ by clicking f7
4. Now switch off your phone (by navigating through fast boot options)
5. While switched off hold both vol up + down for 5secs before connecting to your pc. *Your pc should recognise a phone is connected however nothing will be displayed on your phone*
6. Open device manager from start- Under Other devices there should be your phone (although it will be called smthn else), right click that and select update drivers
7. Browse computer for driver software and select folder with extracted QUALCOMM drivers (for me it was called unbrick).
8. The open the MSM application (run as admin tho) it should say device connected
9. Press start and you download should start- if error occurs or download stops unplug, power on, power off and the plug it again, now it should be fine.
10. Wait for download to finish and then your phone should be rebooted
Erick Rajan said:
Thanks followed some tutorials on MSMtool and go it unbricked ! really appreciate it
For anyone running into a similar problem these are the steps I used
1. Download and extract files
a. Qualcomm drivers
b. MSM Oneplus 6t download Tool
2. Disable Driver Signature Enforcement by restarting your pc whilst holding shift, Choose trouble shoot, then going into more recovery ,select Advanced Options > Startup Settings > and then click on Restart.
3. Now PC will restart and Now you will see a list of startup settings that you can change. Select option 7 ‘Disable Driver Signature Enforcement’ by clicking f7
4. Now switch off your phone (by navigating through fast boot options)
5. While switched off hold both vol up + down for 5secs before connecting to your pc. *Your pc should recognise a phone is connected however nothing will be displayed on your phone*
6. Open device manager from start- Under Other devices there should be your phone (although it will be called smthn else), right click that and select update drivers
7. Browse computer for driver software and select folder with extracted QUALCOMM drivers (for me it was called unbrick).
8. The open the MSM application (run as admin tho) it should say device connected
9. Press start and you download should start- if error occurs or download stops unplug, power on, power off and the plug it again, now it should be fine.
10. Wait for download to finish and then your phone should be rebooted
Click to expand...
Click to collapse
Glad to help.
And thank you for the steps. Hopefully someone with a brick will find it helpful.

Lenovo TB-X304L Bricked

Hello to all.
I have big problem with my tablet Lenovo Tab 4 10.
The phone is on constantly on bootloop.
I can only enter in fastboot mode.
Recovery mode and OS are not booting.
On my fastboot screen says Device state: locked
When i run command fastboot devices the devices is showed. I cant find solution and a way how to flash stock ROM. I download stock ROM with Lenovo Rescue and Smart Assistant. And tried with LMSA but program says cannot read all information from the phone. Is there anyone with same problem or with a solution
musicalen89 said:
Hello to all.
I have big problem with my tablet Lenovo Tab 4 10.
The phone is on constantly on bootloop.
I can only enter in fastboot mode.
Recovery mode and OS are not booting.
On my fastboot screen says Device state: locked
When i run command fastboot devices the devices is showed. I cant find solution and a way how to flash stock ROM. I download stock ROM with Lenovo Rescue and Smart Assistant. And tried with LMSA but program says cannot read all information from the phone. Is there anyone with same problem or with a solution
Click to expand...
Click to collapse
See don't panic I was in the exactly same condition a week before. I can feel you but thats what I can suggest you, to don't panic.
Just follow these steps-
1- Open lmsa and then go to downloaded section , there you can see the downloaded firmware , at below of the screen you can see a option of changing file location of the downloaded firmware,
Change the firmware location to the desktop for your easier access.
2- After that install the mi flash tool from the internet, and extract it in the pc desktop for easy access.
3- Open mi flash tool and select the downloaded firmware , you can select it by click on load firmware.
It can might say that the downloaded file is not a fastboot rom but you can ignore it.
4- Now click on the configurations option in the mi flash and there you can see a option of loading patch xml and raw xml , both of these files will be showed you have to just click on them.
5-Now , insert usb cable into your pc and then press both vol +,- simultaneously and insert the micro usb cable while keep pressing it .
6- Click on refresh and when you will see your device , just hit flash.
And it will be flashed in less than 5 min.
And you will have your device working again

Categories

Resources