Requirements:
Bricked Nexus 5
EMMC should not be fried
Image files: 16GB (mirror) and 32GB (mirror)
BoardDiag (mirror) tool for Nexus 5
Windows XP - 7 - 8 - 8.1 (Virutal Box or VMware good too)
Let's start!
Connect the phone to your PC
Open Device Manager
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
1: Find Qualcomm HS-USB QDLoader 9008 device under Ports (COM & LPT) and note the COMxy port (in my case it is COM3).
If you dont see Qualcomm HS-USB QDLoader 9008 click on the CLICK TO SHOW CONTENT button bellow, otherwise don't and follow the guide.
1: If you see LG Android USB Device under Other devices or LGE AndroidNet USB Serial Port under Ports (COM & LPT), then press VOLUME_UP+VOLUME_DOWN+POWER keys until you see QHSUSB_BULK under Other devices or Qualcomm HS-USB QDLoader 9008 device under Ports (COM & LPT).
1: If you see QHSUSB_BULK under Other devices, then you have to install drivers (mirror). Just click on Next, Next... and Finish.
You have to turn off driver signature enforcement if you are using Windows 8 or Windows 8.1 to make the drivers work.
Extract the downloaded images 16GB.rar or 32GB.rar to get the image files
Start BoardDiag
1: Select Nexus5 (MSM8974_HammerHead).
2: Select the Com Port you see in Device manager (in my case it is COM3).
3: Select the 16GB or 32GB folder.
4: Select AP check.
5: Select RESTORE BOOT IMG.
1: Click on START.
If you were successful you should see Boot images download completed.
Your phone should turn on, but it may stuck at Google logo. If it is stucked at Google logo you have to reflash a stock rom. You can use either LG FlashTool or fastboot method. You can also flash custom rom from custom recovery if it didn't get replaced by the stock recovery, otherwise flash custom recovery from fastboot.
Extra fun
bitdomo said:
OP updated.
I want to make a little comment about this boarddiag tool, and how it works.
Emmc test:
Erase: erase the whole emmc. Even if you select a partition from the dropdown menu,
Read only: Only reads random blocks from the emmc. If you check DUMP it will read back the amount of blocks of a the chosen partition given in the partition.txt
Write only: writes dummy data to the emmc (55AA hex values and some other other random writes on the actual partition).
Read/Write: writes dummy data to the emmc (55AA hex values and some other other random writes on the actual partition) and then verify them by reading it back
SDRAM test:
I think this test the memory. There is a Level option for it. I dont know what is the differance between the two.
PIMC ON:
No idea, but in some LG documentations it is for only APQ8064 chipset.
Restore boot img:
Restores the images.
How it know which partitions have to be restored?
There is a rawprogram0.xml in model\Nexus5 (MSM8974_HammerHead)\boot_partition_info folder.
The partitions declared here will be flashed to the device if you select nothing in the partititon dropdown menu or in the restore boot img dropdown menu
Boarddiag only cares about the "label" value (have to be tha same as in partition.txt) from rawprogram0.xml. The rest info like startblock, files size and file name will be acquired from the partition.txt.
Partition.txt is a binary file:
0x00-0x03: start block
0x04-0x07: file size in block numbers ( 1 block = 512 byte)
0x08-0x0F: always zero
0x10-0x2F: partition name (must be the same as the label value in rawprogram0.xml)
0x30-0x4F: file name
and the pattern goes on.I wrote a little program which converts this binary partition.txt to an actual txt. You can get it from here
Copy the partition.txt to the same folder where the bin2txt and txt2bin exes are. Run bin2txt then it will create a readable_partition.txt file. Edit it with notepad++. The start block is in HEX and the file size is in bytes (must be multiple of 512). Partition entries is the number of partition declared in the partition.txt. If you done with the editing then run txt2bin and it will create a new_partition.txt file.
Click to expand...
Click to collapse
Old OP
Requirements:
Bricked Nexus 5
EMMC should not be fried
Firmware file: D820 and D821
BoardDiag tool for Nexus 5
Windows XP - 7 - 8 - 8.1 (Virutal Box or VMware good too)
Let's start!
Connect the phone to your PC
Open Device Manager
1: Find Qualcomm HS-USB QDLoader 9008 device under Ports (COM & LPT) and note the COMxy port (in my case it is COM3).
If you dont see Qualcomm HS-USB QDLoader 9008 click on the CLICK TO SHOW CONTENT button bellow, otherwise don't and follow the guide.
1: If you see LG Android USB Device under Other devices or LGE AndroidNet USB Serial Port under Ports (COM & LPT), then press VOLUME_UP+VOLUME_DOWN+POWER keys until you see QHSUSB_BULK under Other devices or Qualcomm HS-USB QDLoader 9008 device under Ports (COM & LPT).
1: If you see QHSUSB_BULK under Other devices, then you have to install drivers. Just click on Next, Next... and Finish.
You have to turn off driver signature enforcement if you are using Windows 8 or Windows 8.1 to make the drivers work.
Extract the downloaded firmware .zip to get the .tot file
Start BoardDiag
1: Select .tot file.
2: Select a directory where to extract .tot file.
3: Click on Extract.
It may hangs on extracting system and cache. Just let it finish.
1: Click OK.
1: Select Nexus5 (MSM8974_HammerHead).
2: Select the Com Port you see in Device manager (in my case it is COM3).
3: Select the directory where you extracted the .tot file.
4: Select AP check.
5: Select RESTORE BOOT IMG.
1: Click on START.
If you were successful you should see Boot images download completed.
Your phone should turn on, but it may stuck at Google logo. If it is stucked at Google logo you have to reflash a stock rom. You can use either LG FlashTool or fastboot method. You can also flash custom rom from custom recovery if it didn't get replaced by the stock recovery, otherwise flash custom recovery from fastboot.
Thanks @jd1639 once again for the GPT partition table of the 32GB variant.
Superb tutorial...its like recovering semi hardbricked phone..
Great job!! ?
@bitdomo Nice, once again.
Added this thread to the Sticky Roll-Up thread.
Lethargy said:
@bitdomo Nice, once again.
Added this thread to the Sticky Roll-Up thread.
Click to expand...
Click to collapse
---------------------------------------------------------------------------
The tool is working. I tested on my nexus 5. I dd zeroed out the sbl1 partition. The phone refused to turn on no matter what I do. I did that what is shown in my first post and now the phone is working again. I also tried to help a guy, but it turned out the emmc of his phone has an I/O error. I used the EMMC TEST option to check the emmc for bad sectors.
I am also summoning @rootSU to let him know what a cool stuff nexus 5 has.
bitdomo said:
I am also summoning @rootSU to let him know what a cool stuff nexus 5 has.
Click to expand...
Click to collapse
Meh, I have a nexus 6. One hit to the bridge of the nose can kill a man before his head hits the floor.
---------- Post added at 07:36 PM ---------- Previous post was at 07:29 PM ----------
Superb work though, really!
bitdomo said:
I tested on my nexus 5. I dd zeroed out the sbl1 partition..
Click to expand...
Click to collapse
Now that is dedication. Welcome back man.
Maybe this could work or be adapted for Nexus 4? I ask for personal curiosity
Inviato dal mio Nexus 4 con Tapatalk 2
jacomail95 said:
Maybe this could work or be adapted for Nexus 4? I ask for personal curiosity
Inviato dal mio Nexus 4 con Tapatalk 2
Click to expand...
Click to collapse
It could be if we would have the flash programmer hex for nexus 4. I have some for some LG phone, but I have no idea are they working or they are for which phone. If you have a bricked nexus 4 or you know somebody who has I could try check the remaining flash programmers. Maybe 1 works for nexus 4.
@jacomail95 it looks like we already have the files for nexus 4 check this post http://forum.xda-developers.com/showthread.php?p=57004657
Thanks for your patience and information Have a nice week
Inviato dal mio Nexus 4 con Tapatalk 2
help please
failed to open partition from EMMC
sahouli31 said:
help please
failed to open partition from EMMC
Click to expand...
Click to collapse
What variant of nexus 5 you have? D820 or D821, 16GB or 32GB? Which .tot file are you using?
Select EMMC TEST and SDRAM TEST then click start. What happens?
Sent from my Nexus 5 using XDA Free mobile app
bitdomo said:
What variant of nexus 5 you have? D820 or D821, 16GB or 32GB? Which .tot file are you using?
Select EMMC TEST and SDRAM TEST then click start. What happens?
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
i am using d821 - 32GB and i used d821 -32go.tot
when i click start always the same pb : failed to open partition of EMMC
sahouli31 said:
i am using d821 - 32GB and i used d821 -32go.tot
when i click start always the same pb : failed to open partition of EMMC
Click to expand...
Click to collapse
Then your eMMC is dead. You have to buy a new motherboard.
Not to rain on your parade, but are you sure you didn't use this thread in any way? (posted one day before you expressed interest in unbricking n5)
http://forum.xda-developers.com/lg-g2/general/fix-unbrick-lg-g2-stuck-qualcomm-hs-usb-t2933830
This brings back memories, though. 3 years ago we were trying to unbrick Sensations/Evos and succeeded: http://forum.xda-developers.com/showthread.php?t=1522351 The really smart guys went as far as being able to unlock bootloaders on various Qualcomm-based phones after that... Those were the days.
RussianBear said:
Not to rain on your parade, but are you sure you didn't use this thread in any way? (posted one day before you expressed interest in unbricking n5)
http://forum.xda-developers.com/lg-g2/general/fix-unbrick-lg-g2-stuck-qualcomm-hs-usb-t2933830
This brings back memories, though. 3 years ago we were trying to unbrick Sensations/Evos and succeeded: http://forum.xda-developers.com/showthread.php?t=1522351 The really smart guys went as far as being able to unlock bootloaders on various Qualcomm-based phones after that... Those were the days.
Click to expand...
Click to collapse
I expressed my interest there 2 month before.
I have to admit that thread inspired me, but that tools shared on that thread never worked because the 2nd_loader.hex files were incomplete or for wrong device. That is why I dont want to give credits., and also the version of this tool is different than the two posted there. The version I use was never posted here on xda. I was searching for the correct 2nd_loader.hex for nexus 5 for 2 months until I found a way to get them. The only things which are similar is the title of thread and we are talking about the same tool.
It is like somebody made a guide to flash stock rom for nexus 4 in fastboot mode and you make a guide to do the same for nexus 5. It is impossible to write not the same instructions. You will find similarities.
Not sure if you're still bricked, but maybe this would work for your N5 @franciscofranco
Awesome sauce @bitdomo this is a legendary thread!
bitdomo said:
I expressed my interest there 2 month before.
I have to admit that thread inspired me, but that tools shared on that thread never worked because the 2nd_loader.hex files were incomplete or for wrong device. That is why I dont want to give credits., and also the version of this tool is different than the two posted there. The version I use was never posted here on xda. I was searching for the correct 2nd_loader.hex for nexus 5 for 2 months until I found a way to get them. The only things which are similar is the title of thread and we are talking about the same tool.
It is like somebody made a guide to flash stock rom for nexus 4 in fastboot mode and you make a guide to do the same for nexus 5. It is impossible to write not the same instructions. You will find similarities.
Click to expand...
Click to collapse
Gotcha. Just looking out, man. Good stuff!
Please I'm stuck with my NEXUS 5 I've done everything and I'm stuck at the end when i have to start the boot flash it says . serial port open FAILED..
I'm using windows 8.1 under parallels desktop on my mac and i have x64 bit qhsusb_bulk drivers PLEASE HELP !!!
Related
I already posted this guide in another thread, but to make sure others read it before asking questions that has been asked 10 times before I descided to repost it in a new thread. Enjoy!
As requested - here is a guide on how to install Windows 7 to the HTC Shift.
First of all you need an external DVD drive or a memory stick with 4GB minimum.
READ THIS GUIDE CAREFULLY BEFORE INSTALLING WINDOWS 7.
The information contained in this guide was collected from posts in this thread and I cannot guarantee that everything will work perfect for you!
• Download the beta image
USB-install:
1 - Open Iso file with winrar, and extract all file into folder C:\WINDOWS7\
2 - Open command prompt in administrator mode (start - all programs - accessories - command prompt - right click - run as administrator)
3 - Then type this commands :
- type CD\
- type DISKPART
- type LIST DISK
- type SELECT DISK X (where X is the memory stick disk number you got from LIST DISK)
- type CLEAN (CAUTION; THIS WILL ERASE ALL THE CONTENTS OF THE SELECTED DISK)
- type CREATE PARTITION PRIMARY
- type SELECT PARTITION 1
- type ACTIVE
- type FORMAT FS=FAT32 QUICK
- type ASSIGN
- type EXIT
- type XCOPY C:\WINDOWS7\*.* /S /E /F E:\ (E: \ is the name of usb stick, if your key has an other letter, of course put your) (after *.* and after each letter preceded by / there's a space!)
Reboot, at startup push FN+F10, and choose your usb key.
This will not affect your HTC SHIFT Vista recovery partition.
Thanks killer_t
DVD-install
• Burn the image to a DVD
• If you want to dualboot Windows 7 and Vista you need to partition your harddrive before starting the installation. Use a suitable partition manager such as Paragon Partition Manager and shrink c:/ to approximately 15-17 GB. Create a new partition in the free space.
• Connect the USB DVD drive to your shift
• Press fn+0 (F10) after turning on your shift – select the DVD drive
• Follow the steps for installing Windows. Remember to select partition 2 as target partition if you want to dualboot with Vista. If not you can safely format the existing partition. This will not affect the recovery partition.
____________________________________________________________________________
• Download the shift drivers from HTC
• When you install the drivers – beware that you have to install them with Vista Compatibility mode enabled and run as Administrator. Right-click the driver setup file – click the Compatibility tab – select Windows Vista and mark “run this file as Administrator”
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
• Install all the drivers in the order below and restart your computer when asked to:
a. VistaECDrvV1[1].0.1.10
b. TouchScreen(1[1].1.0.2)
c. Realtek Audio Driver R197(6[1].0.1.5653)
d. Marvell WiFi driver(8[1].114.123.139)
e. Vitakey _AC5023_Fingerprint AP v5[1].0.2.0 and Driver v7.10.1.0 *
f. Extension Kit USBLanDriver(3[1].8.3.7) (Note: you have to install this through driver update in device manager)
g. Shagctrl_1[1].2.6.122-control center - Note that you have to disable aero to get the 1024x600 interpolated resolution working. Right click on dektop -> personalize -> and choose the first "easy of access" Theme.
h. Synaptics MicroPad(10[1].0.11.1)
• - VISTA_INTEL Chipset Driver v8[1].3.0.1014 You can use Windows Update for this one.
• Now that control center is working in Win7 there is no need to liberate your snapvue (if you haven't already done it). 3G,WLAN and BT works out of the box.
Guide for removing the "Evaluation copy. Build 7057.winamin.090305-2000" watermark in Win7 build 7057:
1. Download this patch.
2. Run the patch, command window will open.
3. Y for yes. Press Enter, then Enter again to exit.
4. Reboot. Watermark is gone.
• Finally, if you encounter any problems – READ this thread before asking questions. Remember that “search” is your friend
Thanks for this nice manual!!
I received my Shift 3 days ago and I'm currently installing Windows 7.
I'll let you know if I managed to install it succesfully.
johanromijn said:
Thanks for this nice manual!!
I received my Shift 3 days ago and I'm currently installing Windows 7.
I'll let you know if I managed to install it succesfully.
Click to expand...
Click to collapse
You're welcome
Hope it works out for you...
deadnex said:
You're welcome
Hope it works out for you...
Click to expand...
Click to collapse
Can you please tell me where I can find HSECT2 and CYGWIN?
johanromijn said:
Can you please tell me where I can find HSECT2 and CYGWIN?
Click to expand...
Click to collapse
I've updated the guide with download info
deadnex said:
Both HSECT2 and CYGWIN can be found in this archive
[Mirror]
Click to expand...
Click to collapse
Thanks for the help, mate!
I feel like a bit of a noob now.
I really have no experience with my Shift yet, sorry for that.
Windows 7 runs great btw!
------------
EDIT: Sorry, but I cannot find the needed files in this archive.
EDIT: Found HSECT2 HERE
please, someone can tell me if touch screen works in win7??
Ciauz
nion said:
please, someone can tell me if touch screen works in win7??
Ciauz
Click to expand...
Click to collapse
yes it works, but you should follow the instruction correctly...follow the steps in the step-by-step guide and it will works like a charm
nion said:
please, someone can tell me if touch screen works in win7??
Ciauz
Click to expand...
Click to collapse
Everything works fine in Win7 except Control Center. However, 3G connection and enable/disable BT/WIFI can be done through HSECT2 and CYGWIN. Read my guide for details.
deadnex said:
b. Intel VGA driver(7[1].14.10.1461)
Click to expand...
Click to collapse
this one is not working for me... BSOD again and again... I think that it is better to keep the default one.
what do you think?
out of curiosity - does the recovery partition still boot after this by pressing Fn+F3?
Cause the last laptop (HP) that i installed windows 7 beta to could no longer boot from the recovery partition thereafter. - I suspect that with the HP's it has to have a specific boot sector of HDD for the F12 recovery to work; same as my acer?
Thanks
Kris
i00 said:
out of curiosity - does the recovery partition still boot after this by pressing Fn+F3?
Cause the last laptop (HP) that i installed windows 7 beta to could no longer boot from the recovery partition thereafter. - I suspect that with the HP's it has to have a specific boot sector of HDD for the F12 recovery to work; same as my acer?
Thanks
Kris
Click to expand...
Click to collapse
haven't tried but it should yes.. because it's not part of the partition of Vista... I guess that in vista you CAN'T remove the thing to restore partition.. but in your HP laptop you could and you may have removed it.
koala996 said:
haven't tried but it should yes.. because it's not part of the partition of Vista... I guess that in vista you CAN'T remove the thing to restore partition.. but in your HP laptop you could and you may have removed it.
Click to expand...
Click to collapse
on my hp the recovery partition is defiantly still intact and I can still recover by marking the recovery partition active from vista but when it says press F12 to recover it now does nothing - so I think it must also need its "special" boot sector
kris
i00 said:
on my hp the recovery partition is defiantly still intact and I can still recover by marking the recovery partition active from vista but when it says press F12 to recover it now does nothing - so I think it must also need its "special" boot sector
kris
Click to expand...
Click to collapse
yeah maybe... I think in the shift it is not part of the HDD (not sure about it).
I will try to restore vista soon, because I want to try things today (to have Win7 and WinVista on 2HDDs working on the shift.. Win7 on main HDD and Vista in external one).
edit1 : well ... recovery done no problem for recovery after installing windows 7 !! I save everything on vista side... activate bluetooth and wifi ... and then installing back Vista on another drive and then Windows 7 on main DD
edit2 : arf.. impossible to install windows on a usb drive ... sad ^^ .. well I will feedback Microsoft about it , it would be a GREAT addition to Win7. well.. reinstalling win 7 now !
koala996 said:
Originally Posted by deadnex
b. Intel VGA driver(7[1].14.10.1461) one is not working for me... BSOD again and again... I think that it is better to keep the default one.
what do you think?
Click to expand...
Click to collapse
I have the same problem and the step by step of cygwin installation is not correct how can I turn off/on bt and wi fi?
siriokeliang said:
I have the same problem and the step by step of cygwin installation is not correct how can I turn off/on bt and wi fi?
Click to expand...
Click to collapse
mmh.. I have recovered vista and reinstalled w7 to get wifi and bt working... shame on me ^^
koala996 said:
mmh.. I have recovered vista and reinstalled w7 to get wifi and bt working... shame on me ^^
Click to expand...
Click to collapse
.....me too and now how can I turn off the bt or wi fi? it's too difficult for me......ok fn F3 back to business it's the only solution
siriokeliang said:
.....me too and now how can I turn off the bt or wi fi? it's too difficult for me......ok fn F3 back to business it's the only solution
Click to expand...
Click to collapse
you can disable them ... but I'm not sure if it is "totally" disabled.
for bluetooth .. I have disable in the "device manager".
for wifi.. I have not disabled it again..but you can through "windows mobility center" (not windows mobile device center).
I'm working on Win7 to make everything usable.. if you need somedays... I think I will have some goods news ! the 2 buttons (shag control and resolution switcher) are responding... but I need to make them work
koala996 said:
this one is not working for me... BSOD again and again... I think that it is better to keep the default one.
what do you think?
Click to expand...
Click to collapse
When windows is booting, press F8, select low resolution mode. Then disable Aero in Win7. After that 1024x600 resolution should work
siriokeliang said:
I have the same problem and the step by step of cygwin installation is not correct how can I turn off/on bt and wi fi?
Click to expand...
Click to collapse
Search the forum or check out Pof's blog for more info on HSECT2 and CYGWIN.
It should work, but I haven't tested it myself yet
Only you are the responsible if you brick your device. I tried the whole method a few times and no problems so far, but random things could happen.
What is LG Flashtool?
LG Flashtool is used by LG to flash firmwares to phones.
What are the advantages of using LG Flashtool?
The flashing process is faster than the fastboot flashing process.
[*]You don't need unlocked bootloader to flash.
[*]It locks bootloader and resets tamper flag.
What are the disadvantages of using LG Flashtool?
Your battery level must be over 10%.
[*]It changes the device factory version. If your phone had KFS78N version of android initially and you flash a KRT16M firmware, then the device factory version is going to change from KFS78N to KRT16M.
[*]LGD821AT-00-V10a-NXS-XX-OCT-01-2013-KFS78N-USER-16G+0 ==> LGD821AT-00-V10b-NXS-XX-OCT-31-2013-KRT16M-USER-16G+0
[*]This info stored on the misc partition at the 0x00008800 offset. You can change it back to the original one if it bothers you.
[*]To get your original device factory version then just open the log file in the LOG folder which is created at the location of the DLL and TOT file and search for "device factory version" text.
[*]I made a flashable zip (mirror) which bacups the device factory version to /sdcard/version.txt. After the backup just copy the txt to your PC. Then here is the restore zip (mirror). Just place the version.txt to /sdcard and flash the zip to restore.
Preparation (you have to do it only for the first time)
Download LG drivers (mirror)and install it.
Download LG Flashtool (mirror)and install it.
Create a folder where you put the DLL and the Firmware file.
Download DLL: D820 (mirror) (North American version) D821 (mirror) (Global version). Place the DLL to the created folder.
Download firmware: D820 (mirror) (North American version) D821 (mirror) (Global version) Place the TOT file to the created folder.
Turn off the phone.
Hold down volume_up key then connect USB cable.
If you see these screens bellow then the phone is in Download Mode and you are on the right path:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Let windows to install the drivers for the new devices.
Change the port number to 41:
Open Device Manager.
Right click on LGE Mobile USB Serial Port (COMxx) (where xx is the port number).
Click on Properties.
Select Port Settings tab
Click on Advance...
Change COM Port Number to COM41
If you don't want to flash any firmware yet just hold down the power key for 10-15 secs then your phone turns on.
Flashing the firmware
Enter your phone to Download Mode.
Start LG flash tool.
If Model Config window does not start, then click on the sign with two cogwheels.
Place a tick next at Select Manual Mode
Click on "..." and select the DLL file for your device.
Click on Add to add the TOT file.
Click OK.
Click on the yellow arrow sign to start flashing.
If you see READY!!, then reconnect your phone. Then "Waiting for Connection" text will appear in the COM41 window.
At 80% the phone will shut off, don't be scared.
DONE! The LED on the phone is starts blinking green. Just remove the usb cable wait until the blinking stops then turn on your device.
Restore device factory version (optional)
Create a new txt file called "version.txt" and open it.
Paste your device factory version from the log file located in the LOG folder where the DLL and TOT file are. Search for "device factory version" text in the log file
Copy version.txt to the root of the sdcard (/sdcard).
Download the restore_device_factory_version.zip (mirror).
Flash restore_device_factory_version.zip in recovery.
Videos
LG Flashtool:
Restore device factory version:
Credits
All the guys from [REF] [TOT] Stock Firmware Collection for Nexus 5 (D820 & D821) thread.
Code:
In PDF ([URL="https://mega.co.nz/#!584SzYbC!hSiymZnhn1SVBqwjOY7qsXB4PvgPnYDwYRnMIid9pfE"].docx for translate[/URL]):
[URL="https://mega.co.nz/#!koRHkIYa!L6esc81aRvQ3PdbklRgdrQZTIu-vbhhbfC6mam4gIzo"]English-English_LGFlashtool.pdf[/URL]
[URL="https://mega.co.nz/#!lwZxhDLa!9L9HE0qjGZ3iIxi01m6nm1EYt23zllri8K9s__5Nmcw"]Magyar-Hungarian_LGFlashtool.pdf[/URL]
How is this quicker than fastboot?
Sent from my Nexus 5
pepdavies said:
How is this quicker than fastboot?
Sent from my Nexus 5
Click to expand...
Click to collapse
Fastboot: Phone restarts twice. Send the images to the phone memory, after the whole image has been sent, then the phone write it to the emmc from the memory.
LG flashtool: writes the images directly to the emmc.
I've never really thought of Fastboot as slow by any means. Writing a system.IMG can take a few seconds, but everything else is generally done within a couple of seconds. Writing to memory sounds safer to me as well. If it ain't broke, as they say.
This is awesome! People its not only that it is REALLY faster and secure to flash with this, but think of it in this way, my phone got screwed up, my flash memory died there for I tried to RMA it, the fact that the bootloader was unlocked was a problem and since there was no way to fix it I had to battle for a while, I RECOMMEND THIS WAY OF FLASHING GREATLY in case something happens to your phone you can be sure your warranty will be still there!:good:
does this wipe all internal storage including "internal sdcard"?
cnstarz said:
does this wipe all internal storage including "internal sdcard"?
Click to expand...
Click to collapse
Full system, sdcard inclosed.
This close bootloader and flash full phone (exception imei partition)
cnstarz said:
does this wipe all internal storage including "internal sdcard"?
Click to expand...
Click to collapse
David_Vaz said:
Full system, sdcard inclosed.
This close bootloader and flash full phone (exception imei partition)
Click to expand...
Click to collapse
and also resets tamperflag
Hi, Can you help me please.I have downloaded everything and set up the drivers as instructed but when I click on start Lg flash tool to start the process I get a message saying LG USB/Parallel lock key is not detected and then a login box pops up which has the country set as Republic of Korea in the first box and then it wants an ID and password entered. SOLVED
Great work @bitdomo on putting this together!
pepdavies said:
How is this quicker than fastboot?
Sent from my Nexus 5
Click to expand...
Click to collapse
funky_snowman said:
I've never really thought of Fastboot as slow by any means. Writing a system.IMG can take a few seconds, but everything else is generally done within a couple of seconds. Writing to memory sounds safer to me as well. If it ain't broke, as they say.
Click to expand...
Click to collapse
I think one of the main advantages that bitdomo may have forgot to mention is that this will work even if fastboot won't (in most cases). For example, say you had a bad bootloader flash, and now you cannot access the bootloader. Consequently, you are not able to flash images using fastboot. However, using LG Flash Tool (or LGNPST) should still allow you to flash your device and get back to a stock state.
Now, the one thing that remains is to figure out how to flash the device using QPST...
bitdomo said:
and also resets tamperflag
Click to expand...
Click to collapse
Yes
Enviado desde mi Nexus 5 mediante Tapatalk
efrant said:
Great work @bitdomo on putting this together!
I think one of the main advantages that bitdomo may have forgot to mention is that this will work even if fastboot won't (in most cases). For example, say you had a bad bootloader flash, and now you cannot access the bootloader. Consequently, you are not able to flash images using fastboot. However, using LG Flash Tool (or LGNPST) should still allow you to flash your device and get back to a stock state.
Now, the one thing that remains is to figure out how to flash the device using QPST...
Click to expand...
Click to collapse
Yes I forgot to say that .
People who killed their bootloaders get Qualcomm HS-USB QDloader 9008 device (without drivers it is QHSUSB_BULK) when they connect their devices to the PC. If they try to enter Download mode they get a black screen as well, but on the pc LGE androidnet serial usb port device comes up. Atleast two out of two people's phone do these symptoms. I don't know what's with the others. LGE androidnet serial usb port device is used to setup CDMA networks on nexus 5, there is a thread about it somewhere. So in short LGE androidnet serial usb port is useless for LG flashtool.
I started an investigation on LGE androidnet serial usb port device to figure out why this comes up for that two people. I found out when you try to enter to Download mode then the phone boots up the LAF image, which is a kernel image like recovery.img or boot.img. I extracted the ramdisk of the LAF (it is on the laf partition) and I found this file init.laf.usb.rc.
Code:
# init.laf.usb.rc
# it can run as user cable
on property:ro.boot.laf=USER
wait /sys/class/android_usb/android0/enable
write /sys/class/android_usb/android0/enable 0
write /sys/class/android_usb/android0/idVendor 1004
write /sys/class/android_usb/android0/idProduct 6000
write /sys/class/android_usb/android0/bDeviceClass 2
write /sys/class/android_usb/android0/bDeviceSubClass 0
write /sys/class/android_usb/android0/bDeviceProtocol 0
write /sys/class/android_usb/android0/f_acm/acm_transports tty
write /sys/class/android_usb/android0/f_diag/clients diag
write /sys/class/android_usb/android0/functions acm,laf
write /sys/class/android_usb/android0/enable 1
# it can run as user cable for PID of verizon
on property:ro.boot.laf=VUSER
wait /sys/class/android_usb/android0/enable
write /sys/class/android_usb/android0/enable 0
write /sys/class/android_usb/android0/idVendor 1004
write /sys/class/android_usb/android0/idProduct 6246
write /sys/class/android_usb/android0/bDeviceClass 239
write /sys/class/android_usb/android0/bDeviceSubClass 2
write /sys/class/android_usb/android0/bDeviceProtocol 1
write /sys/class/android_usb/android0/f_acm/acm_transports tty
write /sys/class/android_usb/android0/f_diag/clients diag
write /sys/class/android_usb/android0/functions acm,laf,ecm
write /sys/class/android_usb/android0/enable 1
# it can run as factory cable(910K USB cable)
on property:ro.boot.laf=910K
wait /sys/class/android_usb/android0/enable
write /sys/class/android_usb/android0/enable 0
write /sys/class/android_usb/android0/idVendor 1004
write /sys/class/android_usb/android0/idProduct 6000
write /sys/class/android_usb/android0/bDeviceClass 2
write /sys/class/android_usb/android0/bDeviceSubClass 0
write /sys/class/android_usb/android0/bDeviceProtocol 0
write /sys/class/android_usb/android0/f_acm/acm_transports tty
write /sys/class/android_usb/android0/f_diag/clients diag
write /sys/class/android_usb/android0/functions acm,laf
write /sys/class/android_usb/android0/enable 1
# it can run as factory cable(56K USB cable)
on property:ro.boot.laf=56K
wait /sys/class/android_usb/android0/enable
write /sys/class/android_usb/android0/enable 0
write /sys/class/android_usb/android0/idVendor 1004
write /sys/class/android_usb/android0/idProduct 6000
write /sys/class/android_usb/android0/bDeviceClass 2
write /sys/class/android_usb/android0/bDeviceSubClass 0
write /sys/class/android_usb/android0/bDeviceProtocol 0
write /sys/class/android_usb/android0/f_acm/acm_transports tty
write /sys/class/android_usb/android0/f_diag/clients diag
write /sys/class/android_usb/android0/functions acm,laf
write /sys/class/android_usb/android0/enable 1
# it can run as factory cable(130K USB cable)
on property:ro.boot.laf=130K
wait /sys/class/android_usb/android0/enable
write /sys/class/android_usb/android0/enable 0
write /sys/class/android_usb/android0/idVendor 1004
write /sys/class/android_usb/android0/idProduct 6000
write /sys/class/android_usb/android0/bDeviceClass 2
write /sys/class/android_usb/android0/bDeviceSubClass 0
write /sys/class/android_usb/android0/bDeviceProtocol 0
write /sys/class/android_usb/android0/f_acm/acm_transports tty
write /sys/class/android_usb/android0/f_diag/clients diag
write /sys/class/android_usb/android0/functions acm,laf
write /sys/class/android_usb/android0/enable 1
# it can run as user cable for QCT PID
on property:ro.boot.laf=QCOM
wait /sys/class/android_usb/android0/enable
write /sys/class/android_usb/android0/enable 0
write /sys/class/android_usb/android0/idVendor 05C6
write /sys/class/android_usb/android0/idProduct 903A
write /sys/class/android_usb/android0/f_acm/acm_transports tty
write /sys/class/android_usb/android0/f_diag/clients diag
write /sys/class/android_usb/android0/functions mtp,laf
write /sys/class/android_usb/android0/enable 1
So, for some reasone for those two guys the laf runs the "on property:ro.boot.laf=QCOM" lines and not the "on property:ro.boot.laf=USER" lines. In the comments you can see both of this mode triggered by "user" cable. I think "user" cable means the normal usb cable. There are 3 more "modes" for 56k, 130k, 910k cables all of these three are identical with "on property:ro.boot.laf=USER" settings. Maybe if that two people get or make one of those cable then they can avoid to get the "on property:ro.boot.laf=QCOM" lines run.
I attached the ramdisk to this post.
bitdomo said:
[/I]
[/LIST]
[/CODE]
Click to expand...
Click to collapse
Hi as I was on the image link on mega the one that is named as the same as the one installed on my phone...you have the folder marked "Converted"
How is the image Converted/modified?
Thanks in advance
P.S. Could you also Please post the md5 chksums for all of the files, save a brick!
RoxAbout said:
Hi as I was on the image link on mega the one that is named as the same as the one installed on my phone...you have the folder marked "Converted"
How is the image Converted/modified?
Thanks in advance
P.S. Could you also Please post the md5 chksums for all of the files, save a brick!
Click to expand...
Click to collapse
Converted means it is from the other nexus 5 variant. I just changed a text from D820 to D821 and vice-versa, since all nexus 5 the same, using tot images from the other variant cant cause problem. To test out my theory i flashed the d820 kfs78n rom to my d821 and no problem. Here read this: http://forum.xda-developers.com/showpost.php?p=51651325&postcount=82
Tot files has crc check, but if you feel it safer i can make the md5 sums.
Tapatalk-kal küldve az én Nexus 5-el
OP Update
Update:
I made device factory version backup and restore zips
I Added md5 check sum files to every rom file.
I updated the .docx and pdfs.
Hey. I tried this method because I want to go back 2 stock & reset the tamperflag
But I got this (check the screenshot). I used both files (oct/dec)/ It's the 16GB version (europe/821).
Wrong driver?
The device had LGD821AT-00-V10d-NXS-XX-DEC-11-2013-KOT49H-USER-16G+0 on it.
Cuxx said:
Hey. I tried this method because I want to go back 2 stock & reset the tamperflag
But I got this (check the screenshot). I used both files (oct/dec)/ It's the 16GB version (europe/821).
Wrong driver?
The device had LGD821AT-00-V10d-NXS-XX-DEC-11-2013-KOT49H-USER-16G+0 on it.
Click to expand...
Click to collapse
It should work. you get those screens on your phone what I posted in the OP? If it is that case then it must be a driver issue. The device name in the device manager seems okay.
Tapatalk-kal küldve az én Nexus 5-el
Now it works. I think it was an USB3 Port. Now @ the USB2 Port it works.
Cuxx said:
Now it works. I think it was an USB3 Port. Now @ the USB2 Port it works.
Click to expand...
Click to collapse
Oh . I should have know. Happy flashing!
Tapatalk-kal küldve az én Nexus 5-el
Interesting tool. Thanks for sharing and for your explanations.
Requirements:
*) Phone with unlocked boot loader.
*) Windows PC (preferable win7)
*) IMEI and S/N writer tool
*) Drivers of CND and our mobile drivers installed
1. EXTRACT IMEI_FILES AND IMEI TOOLS ON THE DESKTOP OF UR PC
2. NOW OPEN IMEI TOOL ( IMEI&SN Writer.exe)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
3. NOW IN PLATFORM SELECT SMARTPHONE AND SELECT USB (SEE BELOW PLATFORM IN TOOL)
4. IN WRITE TOOL TICK IMEI 1 AND IMEI 2 AND WRITE THERE BOTH UR IMEI
5. NOW CLICK ON SELECT DB AND BROWSE TO THE FOLDER DATABASE AS DIRECTED IN STEP 2
6. SELECT THE FILE WHICH IS IN DATABASE FOLDER AND AGAIN IT ASK U TO SELECT AP FILE
7. THEN SELECT FILE WHICH IS IN AP FOLDER AND CLICK ON START
8. NOW SWITCH OFF UR CELL AND CONNECT
9. NOW GO TO DEVICE MANAGER ( BY RIGHT CLICK ON MY COMPUTER ICON AND CLICK ON PROPERTY ,AFTER OPENING WINDOW CLICK ON DEVICE MANAGER FROM SIDE BAR IN WIN 7 AND ABOVE...
10. AFTER OPENING OF DEVICE MANAGER ,GO TO CDC DRIVER WHICH WILL SHOW RED OR YELLOW CROSS SIGN ,NOW RIGHT CLICK ON AND CLICK ON UPDATE DRIVER .
11. NOW EXTRACT THE CDC DRIVER IN NEW FOLDER ANYWHERE AND BROWSER TO THE CDC DRIVER LOCATION AMD SELECT FOLDER AND CLICK OK TO UPDATE THE CDC DRIVER.. AFTER SUCCESSFULLY DONE
12. AGAIN CLICK ON START AND CONNECT UR PHONE ....MAKE SURE YOU SELECT PROPER COM PORT. CHECK IT IN YOUR DEVICE MANGER. MY COMPUTER-->PROPERTIES-->DEVICE MANAGER-->PORTS AND COMS. NOW IT WILL WRITE IMEI PERMANENTLY
13. AFTER PROCESS FINISH REBOOT AND ENJOY.....
Download All in One Zip
Reserved
Sent from my Micromax AQ4501 using XDA Free mobile app
Shrihari007 said:
Requirements:
*) Phone with unlocked boot loader.
*) Windows PC (preferable win7)
*) IMEI and S/N writer tool
*) Drivers of CND and our mobile drivers installed
1. EXTRACT IMEI_FILES AND IMEI TOOLS ON THE DESKTOP OF UR PC
2. NOW OPEN IMEI TOOL ( IMEI&SN Writer.exe)
3. NOW IN PLATFORM SELECT SMARTPHONE AND SELECT USB (SEE BELOW PLATFORM IN TOOL)
4. IN WRITE TOOL TICK IMEI 1 AND IMEI 2 AND WRITE THERE BOTH UR IMEI
5. NOW CLICK ON SELECT DB AND BROWSE TO THE FOLDER DATABASE AS DIRECTED IN STEP 2
6. SELECT THE FILE WHICH IS IN DATABASE FOLDER AND AGAIN IT ASK U TO SELECT AP FILE
7. THEN SELECT FILE WHICH IS IN AP FOLDER AND CLICK ON START
8. NOW SWITCH OFF UR CELL AND CONNECT
9. NOW GO TO DEVICE MANAGER ( BY RIGHT CLICK ON MY COMPUTER ICON AND CLICK ON PROPERTY ,AFTER OPENING WINDOW CLICK ON DEVICE MANAGER FROM SIDE BAR IN WIN 7 AND ABOVE...
10. AFTER OPENING OF DEVICE MANAGER ,GO TO CDC DRIVER WHICH WILL SHOW RED OR YELLOW CROSS SIGN ,NOW RIGHT CLICK ON AND CLICK ON UPDATE DRIVER .
11. NOW EXTRACT THE CDC DRIVER IN NEW FOLDER ANYWHERE AND BROWSER TO THE CDC DRIVER LOCATION AMD SELECT FOLDER AND CLICK OK TO UPDATE THE CDC DRIVER.. AFTER SUCCESSFULLY DONE
12. AGAIN CLICK ON START AND CONNECT UR PHONE ....MAKE SURE YOU SELECT PROPER COM PORT. CHECK IT IN YOUR DEVICE MANGER. MY COMPUTER-->PROPERTIES-->DEVICE MANAGER-->PORTS AND COMS. NOW IT WILL WRITE IMEI PERMANENTLY
13. AFTER PROCESS FINISH REBOOT AND ENJOY.....
Download All in One Zip
Click to expand...
Click to collapse
What's CND
Sent from my A1 using XDA Free mobile app
Error while installing Cds Drivers
Error = the third party INS does not contain digital signatures or something like that Plz help OS = 8.1
For windows 8.1/8.1 Disable driver signature enforcement checking....
How to here :
https://learn.sparkfun.com/tutorial...abling-signed-driver-enforcement-on-windows-8
Now on Window 7 it says enter meta mode failed
Hi
i Switched form 8.1 to window 7:crying: just for this method but in window 7 i installed every driver but when i connect my device the imei writter says enter meta mode failed:crying::crying::crying::crying::crying: and there is mmx logo on my A1
what to do bro guid plz!
Select correct com port
Sent from my Micromax AQ4501 using XDA Free mobile app
Code:
Steps:
1,Please power off the phone
2,Then plug in the USB cable
USB Bootup
Meta_DB Init Start:
Meta_DB Init PASS
Enter to ModemMeta Start:
Enter to ModemMeta Fail:
It is over !!
Error Message : Falied to enter meta mode.
Other than that CDC driver does not show up in the device manager either.
Any help please?
Please Help Mine Same Problem
mine too same problem what can i do
if you"ve fixed this problem plz tell me please help..!!!!!!!! I Am ****ed Up
PLEASE HELP................!!!!!!!!!!!!!!!!!!!!!!!!!!
please.!!!! reply:crying::crying::crying::crying:
:crying::crying:
Saatvik Shukla said:
Code:
Steps:
1,Please power off the phone
2,Then plug in the USB cable
USB Bootup
Meta_DB Init Start:
Meta_DB Init PASS
Enter to ModemMeta Start:
Enter to ModemMeta Fail:
It is over !!
Error Message : Falied to enter meta mode.
Other than that CDC driver does not show up in the device manager either.
Any help please?
Click to expand...
Click to collapse
Me too had same problem..... All you need to do is select proper com port
Sent from my Micromax AQ4501 using XDA Free mobile app
Shrihari007 said:
Requirements:
*) Phone with unlocked boot loader.
*) Windows PC (preferable win7)
*) IMEI and S/N writer tool
*) Drivers of CND and our mobile drivers installed
1. EXTRACT IMEI_FILES AND IMEI TOOLS ON THE DESKTOP OF UR PC
2. NOW OPEN IMEI TOOL ( IMEI&SN Writer.exe)
3. NOW IN PLATFORM SELECT SMARTPHONE AND SELECT USB (SEE BELOW PLATFORM IN TOOL)
4. IN WRITE TOOL TICK IMEI 1 AND IMEI 2 AND WRITE THERE BOTH UR IMEI
5. NOW CLICK ON SELECT DB AND BROWSE TO THE FOLDER DATABASE AS DIRECTED IN STEP 2
6. SELECT THE FILE WHICH IS IN DATABASE FOLDER AND AGAIN IT ASK U TO SELECT AP FILE
7. THEN SELECT FILE WHICH IS IN AP FOLDER AND CLICK ON START
8. NOW SWITCH OFF UR CELL AND CONNECT
9. NOW GO TO DEVICE MANAGER ( BY RIGHT CLICK ON MY COMPUTER ICON AND CLICK ON PROPERTY ,AFTER OPENING WINDOW CLICK ON DEVICE MANAGER FROM SIDE BAR IN WIN 7 AND ABOVE...
10. AFTER OPENING OF DEVICE MANAGER ,GO TO CDC DRIVER WHICH WILL SHOW RED OR YELLOW CROSS SIGN ,NOW RIGHT CLICK ON AND CLICK ON UPDATE DRIVER .
11. NOW EXTRACT THE CDC DRIVER IN NEW FOLDER ANYWHERE AND BROWSER TO THE CDC DRIVER LOCATION AMD SELECT FOLDER AND CLICK OK TO UPDATE THE CDC DRIVER.. AFTER SUCCESSFULLY DONE
12. AGAIN CLICK ON START AND CONNECT UR PHONE ....MAKE SURE YOU SELECT PROPER COM PORT. CHECK IT IN YOUR DEVICE MANGER. MY COMPUTER-->PROPERTIES-->DEVICE MANAGER-->PORTS AND COMS. NOW IT WILL WRITE IMEI PERMANENTLY
13. AFTER PROCESS FINISH REBOOT AND ENJOY.....
Download All in One Zip
Click to expand...
Click to collapse
whether it can be done to overcome Invalid IMEI on Samsung Galaxy Note 2, bro?
No its only for mediatek devices
what are the ways that a imei number can get damaged?
hi all.
just asking this question to take care of not to do such things.
how can a imei number get damaged?
How to?? How to select proper driver
And How TO Do That?? please Explain i am in big trouble
Shrihari007 said:
Me too had same problem..... All you need to do is select proper com port
Sent from my Micromax AQ4501 using XDA Free mobile app
Click to expand...
Click to collapse
Does this work on every android phone?
Mine is galaxy note 10.1 n8000, with gnabo rom 4.4.2 running on it.
Sent from my Xperia Acro S using Tapatalk
Araragi said:
Does this work on every android phone? Mine is galaxy note 10.1 n8000, with gnabo rom 4.4.2 running on it.
Click to expand...
Click to collapse
the answer is here.
why he is not replying????
I am in invalid imei
Why the thread maker is not replying instead you check this video on YouTube for repair the another way
https://youtu.be/8DT-32tPbMY
Sagar Kapasi said:
And How TO Do That?? please Explain i am in big trouble
Click to expand...
Click to collapse
Enter to ModemMeta Fail
Now what to Do ? I install the CDC Driver but it still says failed to enter meta mode ? i am on win7 32bit! is this only for 64 bit ?
I have lost my imei, wifi Mac Address, and Serial Number ?
I am in a Big Trouble ...PLZ help me!
srikantrn said:
Enter to ModemMeta Fail
Now what to Do ? I install the CDC Driver but it still says failed to enter meta mode ? i am on win7 32bit! is this only for 64 bit ?
I have lost my imei, wifi Mac Address, and Serial Number ?
I am in a Big Trouble ...PLZ help me!
Click to expand...
Click to collapse
Read the thread carefully!
Flash the stock ROM via SP flash tools.
Sent from my Sparkle V
Hi all!
I am trying to flash QFIL file to my Nokia 7 plus (TA-1046), but with no success because the Qualcomm driver is not installed automatically.
I have the 1.0 Qualcomm driver collection installed, but when I plugin my phone in download mode, I see it appear in device manager under "other devices" as "Android". I can update the driver to any other Qualcomm driver, but I don't know which one to choose. I tried the "QDLoader 9008" and it installs fine, but in QFIL.exe I can't flash my phone. I still get sahara errors.
What driver (type number) do I need to install to connect my phone's interface (download mode)?
EDIT:
Forgot to mention the obvious, it's Windows 7...
sbsoft said:
Hi all!
I am trying to flash QFIL file to my Nokia 7 plus (TA-1046), but with no success because the Qualcomm driver is not installed automatically.
I have the 1.0 Qualcomm driver collection installed, but when I plugin my phone in download mode, I see it appear in device manager under "other devices" as "Android". I can update the driver to any other Qualcomm driver, but I don't know which one to choose. I tried the "QDLoader 9008" and it installs fine, but in QFIL.exe I can't flash my phone. I still get sahara errors.
What driver (type number) do I need to install to connect my phone's interface (download mode)?
EDIT:
Forgot to mention the obvious, it's Windows 7...
Click to expand...
Click to collapse
When you install QPST Too,l all qualcomm drivers are installed to your pc. if your device is not detected by your pc try restarting your pc. if restart not working the. open device manager and search for unknown device then install driver manually.
sarath medithi said:
When you install QPST Too,l all qualcomm drivers are installed to your pc. if your device is not detected by your pc try restarting your pc. if restart not working the. open device manager and search for unknown device then install driver manually.
Click to expand...
Click to collapse
Thanks for your reply!
I did all you said (incl installing QPST tool), but still see "Android" under "Unknown devices". It is not recognized at all by Windows.
I want to install manually, but don't know which driver to choose from. I see a list of about 50 Qualcomm port drivers (MSM xxxx, QDLoader xxxx, Diagnostics xxxx), so which one is the correct one? What do you see under your "Ports (COM and LPT)" in device manager when you connect your phone in download mode?
QFIL Flashing Procedure
sbsoft said:
Thanks for your reply!
I did all you said (incl installing QPST tool), but still see "Android" under "Unknown devices". It is not recognized at all by Windows.
I want to install manually, but don't know which driver to choose from. I see a list of about 50 Qualcomm port drivers (MSM xxxx, QDLoader xxxx, Diagnostics xxxx), so which one is the correct one? What do you see under your "Ports (COM and LPT)" in device manager when you connect your phone in download mode?
Click to expand...
Click to collapse
Please confirm your qfil version.
Tool frome here:
https://aiomobilestuff.com/download-...st-flash-tool/
Drivers from here:
http://www.mediafire.com/file/j3g88d...r+V1.1.0.0.rar
Steps to flash the phone
Step1: To use QPST, some drivers need to be installed on your Computer.
Note: While installing driver avoid using cable for successful installation.
When Drivers installed, Attach Phone to PC via USB cable.
While connecting to PC, phone should be switched off and press volume up & down as boot key.
If it Create Qualcomm HS-USB QDLoader 9008 port in device manager , then driver has been successfully installed.
Once driver installation is complete, follow the instructions below to flash the MBN firmware file to your Qualcomm device.
Step 2. Make sure your device is charged to at least 30%.
Step 3. Run QFIL tool.
Step 4. Now Browse under the Programmer path to Chose the B2N-0-132E-prog_emmc_ufs_firehose_Sdm660_ddr.elf File.
Step 5. As soon as the elf file is selected, Select Build will automatically select the Update or Stock ROM.
Step 6. Next Go To Load XML, selectB2N-0-132E-rawprogram0.xml and Select B2N-0-132E-patch0.xml
Step 7. Turn off the Phone and Attach it to PC by pressing Vol up & down button.
Step 8. Click on Select Port and choose the port.
Step 9. Click on Download to start flashing.
Step 10. Disconnect device from USB cable once Finish Download appears.
That’s all!
Hit thanks button if you find this helpful
Happy flashing
Note: If you get the Sahara Errors Place Firmware folder in QFIL\Bin folder. Check whether programmer file is available in your firmware folder. It is an elf file (B2N-0-132E-prog_emmc_ufs_firehose_Sdm660_ddr.elf). Use recent version of QPST. earler versions cant flash .elf programmers.
sarath medithi said:
Please confirm your qfil version.
Tool frome here:
https://aiomobilestuff.com/download-...st-flash-tool/
Drivers from here:
http://www.mediafire.com/file/j3g88d...r+V1.1.0.0.rar
Steps to flash the phone
Step1: To use QPST, some drivers need to be installed on your Computer.
Note: While installing driver avoid using cable for successful installation.
When Drivers installed, Attach Phone to PC via USB cable.
While connecting to PC, phone should be switched off and press volume up & down as boot key.
If it Create Qualcomm HS-USB QDLoader 9008 port in device manager , then driver has been successfully installed.
Once driver installation is complete, follow the instructions below to flash the MBN firmware file to your Qualcomm device.
Step 2. Make sure your device is charged to at least 30%.
Step 3. Run QFIL tool.
Step 4. Now Browse under the Programmer path to Chose the B2N-0-132E-prog_emmc_ufs_firehose_Sdm660_ddr.elf File.
Step 5. As soon as the elf file is selected, Select Build will automatically select the Update or Stock ROM.
Step 6. Next Go To Load XML, selectB2N-0-132E-rawprogram0.xml and Select B2N-0-132E-patch0.xml
Step 7. Turn off the Phone and Attach it to PC by pressing Vol up & down button.
Step 8. Click on Select Port and choose the port.
Step 9. Click on Download to start flashing.
Step 10. Disconnect device from USB cable once Finish Download appears.
That’s all!
Hit thanks button if you find this helpful
Happy flashing
Note: If you get the Sahara Errors Place Firmware folder in QFIL\Bin folder. Check whether programmer file is available in your firmware folder. It is an elf file (B2N-0-132E-prog_emmc_ufs_firehose_Sdm660_ddr.elf). Use recent version of QPST. earler versions cant flash .elf programmers.
Click to expand...
Click to collapse
Thanks for your replay!
I did all you said and I think the driver is now installed correctly. Only problem that remains is the locked bootloader, which is preventing flashing.
I have tried to disable it by "fastboot oem unlock", but no success, because access is denied. (I have enabled OEM unlock in dev options).
QFIL keeps reporting me "100 Unable to connect to port". Sahara is not an issue anymore (I guess).
Do I really need to unlock bootloader to flash the elf?
EDIT: I've read another article on XDA that states that Nokia devices cannot be flashed???
sbsoft said:
Thanks for your replay!
I did all you said and I think the driver is now installed correctly. Only problem that remains is the locked bootloader, which is preventing flashing.
I have tried to disable it by "fastboot oem unlock", but no success, because access is denied. (I have enabled OEM unlock in dev options).
QFIL keeps reporting me "100 Unable to connect to port". Sahara is not an issue anymore (I guess).
Do I really need to unlock bootloader to flash the elf?
EDIT: I've read another article on XDA that states that Nokia devices cannot be flashed???
Click to expand...
Click to collapse
QFIL don't need unlocked bootloader as it uses EDL Mode for flashing. I suggest you to change the usb port and try with another data cable.
---------- Post added at 12:13 PM ---------- Previous post was at 12:12 PM ----------
sbsoft said:
Thanks for your replay!
I did all you said and I think the driver is now installed correctly. Only problem that remains is the locked bootloader, which is preventing flashing.
I have tried to disable it by "fastboot oem unlock", but no success, because access is denied. (I have enabled OEM unlock in dev options).
QFIL keeps reporting me "100 Unable to connect to port". Sahara is not an issue anymore (I guess).
Do I really need to unlock bootloader to flash the elf?
EDIT: I've read another article on XDA that states that Nokia devices cannot be flashed???
Click to expand...
Click to collapse
can you share the qfil log or screenshot
sarath medithi said:
QFIL don't need unlocked bootloader as it uses EDL Mode for flashing. I suggest you to change the usb port and try with another data cable.
---------- Post added at 12:13 PM ---------- Previous post was at 12:12 PM ----------
can you share the qfil log or screenshot
Click to expand...
Click to collapse
Here we go:
(I have Dutch language version of Windows 7, so no English in some pictures)
1. The driver is installed correctly and working fine. (I need to boot Windows in testsigning mode with no driver signature checking, because the driver is not signed correctly?)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Phone is in Download mode.
When I click Download in QFIL, this is the output and nothing happens.
The configuration of QFIL looks like this:
Is this enough for you? If not, please let me know. I am starting to get headaches of this problem...
Thanks!
sbsoft said:
Here we go:
(I have Dutch language version of Windows 7, so no English in some pictures)
1. The driver is installed correctly and working fine. (I need to boot Windows in testsigning mode with no driver signature checking, because the driver is not signed correctly?)
Phone is in Download mode.
When I click Download in QFIL, this is the output and nothing happens.
The configuration of QFIL looks like this:
Is this enough for you? If not, please let me know. I am starting to get headaches of this problem...
Thanks!
Click to expand...
Click to collapse
Try to update your QFIL.i think there is a new version available. update it and try again. may be it is giving an error due to the programmer file which is an elf file. earlier it is .mbn or .bin file. hope you understand.
Did you succede in using QFIL ? @sbsoft
SOLVED:
The reason Device was not detected in Fastbootmode was due to my new ryzen 3000 system, I tried it on my much older quad core 46XXk(?) Intel system and it gave me no problems whatsoever finding the device in fastboot mode in my first try! wtf amd!
The second Set of problems came with flashing 16.0631.1910.64. It gave me a ton of errors and it was on an infinite boot loop, nothing I tried fixed it, my device was a worthless brick in that state, but fastboot Power+Volume up > 16.0631.1910.64 worked perfectly.
I decided to instead try 16.0631.1910.35, but once I flashed it everything worked perfectly! I am in the latest version of android 10 atm and can acess banks, play nintendo games, etc with the rooted device.
Hi, I bought this phone (Rog 2) mostly Intended as a donation for a friend that was complaining on facebook that he's probably going to be homeless due to covid and didnt even have his phone since he cracked the screen. While I cant help with housing I can help with a measly phone and I heard for gaming this is one of the best.
I got the tencent version not knowing what the heck I was getting myself into ( I thought all ROG 2 were the same and didn't even think to look it up). Been googling for days, I am trying to make this a full WW variant and basically as hassle free as possible for him, it seems that it has an obscure version of "pkq1.190414.001.ww_phone-16.0622.1906.19-0 " Rom, but according to HWInfo the fingerprint is CN.
Problem is I tried following this guide, I unlocked the bootloader with the ROG phone unlock tool, but on step 2 I load into fastboot, click flashall_AFT but all I see is a cmd with the message [command] : fastboot.exe flash all WW_ZS660KL_16.0631.1910.35_M3.13.33.30-ASUS_1.1.207_Phone-user.raw and nothing happens.
I noticed that on the cmd of the minimal adb devices and fastboot folder, the "adb devices" gives my device , the "adb reboot bootloader" works by taking me to the bootloader, but the "fastboot devices" does not give me anything at all once im in bootloader. In fact when using adb reboot bootloader I hear the windows beep as if the cellphone is disconecting. Any ideas what is going on?
TeknoViking- said:
Hi, I bought this phone (Rog 2) mostly Intended as a donation for a friend that was complaining on facebook that he's probably going to be homeless due to covid and didnt even have his phone since he cracked the screen. While I cant help with housing I can help with a measly phone and I heard for gaming this is one of the best.
I got the tencent version not knowing what the heck I was getting myself into ( I thought all ROG 2 were the same and didn't even think to look it up). Been googling for days, I am trying to make this a full WW variant and basically as hassle free as possible for him, it seems that it has an obscure version of "pkq1.190414.001.ww_phone-16.0622.1906.19-0 " Rom, but according to HWInfo the fingerprint is CN.
Problem is I tried following this guide, I unlocked the bootloader with the ROG phone unlock tool, but on step 2 I load into fastboot, click flashall_AFT but all I see is a cmd with the message [command] : fastboot.exe flash all WW_ZS660KL_16.0631.1910.35_M3.13.33.30-ASUS_1.1.207_Phone-user.raw and nothing happens.
I noticed that on the cmd of the minimal adb devices and fastboot folder, the "adb devices" gives my device , the "adb reboot bootloader" works by taking me to the bootloader, but the "fastboot devices" does not give me anything at all once im in bootloader. In fact when using adb reboot bootloader I hear the windows beep as if the cellphone is disconecting. Any ideas what is going on?
Click to expand...
Click to collapse
Have you installed adb drivers https://github.com/koush/UniversalAdbDriver
Also, just checking the obvious, you are using the side port of the phone, not the bottom, right?
reg66 said:
Have you installed adb drivers https://github.com/koush/UniversalAdbDriver
Also, just checking the obvious, you are using the side port of the phone, not the bottom, right?
Click to expand...
Click to collapse
Hi! Yeah, I have the exact same driver you mentioned as well as Minimal ADB and Fastboot and using the black sideport.
It seems when I connect it during the fastboot(Green arrow menu) I do hear the "USB Device plugged" sound so there's that.
flashall_AFT still just gives me a black page with: [command] : fastboot.exe flash all WW_ZS660KL_16.0631.1910.35_M3.13.33.30-ASUS_1.1.207_Phone-user.raw
TeknoViking- said:
Hi! Yeah, I have the exact same driver you mentioned as well as Minimal ADB and Fastboot and using the black sideport.
It seems when I connect it during the fastboot(Green arrow menu) I do hear the "USB Device plugged" sound so there's that.
flashall_AFT still just gives me a black page with: [command] : fastboot.exe flash all WW_ZS660KL_16.0631.1910.35_M3.13.33.30-ASUS_1.1.207_Phone-user.raw
Click to expand...
Click to collapse
Before running flashall_AFT.cmd, when you hear the device connect, have you tried entering 'fastboot devices' before doing anything else? See if it gives you a serial. If it does.
Then have you removed the original zip file from the extracted folder that contains the raw img? Once you click flashall_AFT.cmd, the cmd window should stay open for around 5 minutes while the flash takes place, then the phone will reboot once done
reg66 said:
Before running flashall_AFT.cmd, when you hear the device connect, have you tried entering 'fastboot devices' before doing anything else? See if it gives you a serial. If it does.
Then have you removed the original zip file from the extracted folder that contains the raw img? Once you click flashall_AFT.cmd, the cmd window should stay open for around 5 minutes while the flash takes place, then the phone will reboot once done
Click to expand...
Click to collapse
Top left image is from using the "fastboot devices" command, as you can see I type it it doesn't show or seem to do anything really. The right image is from clicking flashall_AFT, both inside bootloader on my rog 2 and outside give the same result.
The Zip file? As in the 2.7 one I downloaded? Yeah that content of that is in a folder in root of C drive, the zip is in a completely different drive so they are not sharing a directory . I did not modify anything inside the extracted file though.
For reference I am following the steps here: https://forum.xda-developers.com/t/...rom-cn-to-ww-with-latest-1910-35-raw.4002279/
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
TeknoViking- said:
Top left image is from using the "fastboot devices" command, as you can see I type it it doesn't show or seem to do anything really. The right image is from clicking flashall_AFT, both inside bootloader on my rog 2 and outside give the same result.
The Zip file? As in the 2.7 one I downloaded? Yeah that content of that is in a folder in root of C drive, the zip is in a completely different drive so they are not sharing a directory . I did not modify anything inside the extracted file though.
For reference I am following the steps here: https://forum.xda-developers.com/t/...rom-cn-to-ww-with-latest-1910-35-raw.4002279/
View attachment 5173971
Click to expand...
Click to collapse
Ok, try unpacking the attached zip to root of C, like the other adb folder. Then click on 'cmd-here.exe' to launch cmd window and then try 'fastboot devices'. (that's assuming the drivers of the original install are working). Let me know if you get a serial response.
reg66 said:
Ok, try unpacking the attached zip to root of C, like the other adb folder. Then click on 'cmd-here.exe' to launch cmd window and then try 'fastboot devices'. (that's assuming the drivers of the original install are working). Let me know if you get a serial response.
Click to expand...
Click to collapse
Done, nothing happens, did it multiple times here's what I get:
TeknoViking- said:
Done, nothing happens, did it multiple times here's what I get:
Click to expand...
Click to collapse
Ok, what a pain! Try uninstall minimal adb drivers and I'll see if I can find ano version for you....
reg66 said:
Ok, what a pain! Try uninstall minimal adb drivers and I'll see if I can find ano version for you....
Click to expand...
Click to collapse
Will do! ty
TeknoViking- said:
Will do! ty
Click to expand...
Click to collapse
try this version, after installing the drivers you could also try that folder with the cmd-here file in combination. Also, try booting into android os and enable developer options (click on 'build' 7 or so times in settings/system/about phone/software information/build number), then go to developer options and enable USB debugging - might make a difference...
Also, check your pm, I sent you modified instructions for using the other guide that'll take you straight to last Android 9 version before you can update to Android 10 (1910.64). You could always be downloading that newer RAW + root img while tinkering with getting the damn thing recognised by your pc!!
Tried the 1910.64 you sent me and its the same problem unfortunately, still stuck on step 2. I already had USB debugging with the "USB debugging" option ticked on when I created the topic.
I take it doing number 4 Is a bad idea if can't get past 2? "4) Download the root&bootstockww191035.zip "rootww191064" and extract it to the Minimal ADB and Fastboot Folder (C:\Program Files (x86)\Minimal ADB and Fastboot) from here "
TeknoViking- said:
Tried the 1910.64 you sent me and its the same problem unfortunately, still stuck on step 2. I already had USB debugging with the "USB debugging" option ticked on when I created the topic.
I take it doing number 4 Is a bad idea if can't get past 2? "4) Download the root&bootstockww191035.zip "rootww191064" and extract it to the Minimal ADB and Fastboot Folder (C:\Program Files (x86)\Minimal ADB and Fastboot) from here "
Click to expand...
Click to collapse
Yeah, there's no point continuing until you can get fastboot devices to at least show your device. Do you have another pc/laptop you could try on? Are you using an AMD based system, pretty sure I read somewhere that can give issues, along with the system used! Sorry that's a bit vague...
TeknoViking- said:
Tried the 1910.64 you sent me and its the same problem unfortunately, still stuck on step 2. I already had USB debugging with the "USB debugging" option ticked on when I created the topic.
I take it doing number 4 Is a bad idea if can't get past 2? "4) Download the root&bootstockww191035.zip "rootww191064" and extract it to the Minimal ADB and Fastboot Folder (C:\Program Files (x86)\Minimal ADB and Fastboot) from here "
Click to expand...
Click to collapse
Oh sorry, you meant try flashing the root img, NO, definitely not. The root img MUST only flashed after successful flashing of RAW - both rom and boot/root boot img's must match. (But either way, if your device isn't recognised by fastboot it just won't flash, just an FYI)
See this thread for info on Ryzen issues, if that is what you're running. The OP says he used an external USB hub as a solution
reg66 said:
Yeah, there's no point continuing until you can get fastboot devices to at least show your device. Do you have another pc/laptop you could try on? Are you using an AMD based system, pretty sure I read somewhere that can give issues, along with the system used! Sorry that's a bit vague...
Click to expand...
Click to collapse
Ok I tried this on my intel system and it detected it!! "fastboot devices" gave me the serial. So when I tried to do step 2 and I used ADB_FASTBOOT to run flashall_AFT from the 1910.64 it failed and it it seems to be on a loop in bootloader "The boot loader is unlocked and software integrity cannot be guaranteed..) etc screen.
I attached the image. This is with the 1910.64 on step two.
Also I got this from continually trying to boot:
TeknoViking- said:
Ok I tried this on my intel system and it detected it!! "fastboot devices" gave me the serial. So when I tried to do step 2 and I used ADB_FASTBOOT to run flashall_AFT from the 1910.64 it failed and it it seems to be on a loop in bootloader "The boot loader is unlocked and software integrity cannot be guaranteed..) etc screen.
I attached the image. This is with the 1910.64 on step two.
Click to expand...
Click to collapse
Hmm, this phone is troublesome. Sorry dude, I've not seen that before. The bootloader unlock tool definitely worked, right? What about if you try using the original 1910.35 RAW - same error?
TeknoViking- said:
Also I got this from continually trying to boot:
Click to expand...
Click to collapse
Do you have above 50% charge? If not, definitely make sure to have enough charge for the whole process. I was always of the understanding, as a rule of thumb, to have devices above 50% before performing flashing of custom roms etc
reg66 said:
Do you have above 50% charge? If not, definitely make sure to have enough charge for the whole process. I was always of the understanding, as a rule of thumb, to have devices above 50% before performing flashing of custom roms etc
Click to expand...
Click to collapse
Yeah the charge is over 90 percent, anything I can do for that error? when I connect to the intel pc it doesn't even beep any more. I still can access the boot screen though.
EDIT: OOPS, noticed I had it plugged on the bottom, nvm intel system still detects the device. I did perform everything on the side port usb but I took it out to try and check back on the ryzen system.