Develop Bugs

[Guide]A much simple way of unbricking and rooting Nitro HD, P930

I know there is a guide already here a long time ago, but Its step is kind of complicated. So, I figure it out another way, no need to set up a HTTP server to trick LG's update software.
I have tested it on V20f, everything works perfect. But remember, whatever you do, you do at your own risk and responsibility for your actions rests solely on you.
Unbricking part:
1. Install LG's cell phone driver, of cause.
2. Install B2CAppSetup.exe from kdz-flash.rar （download）
3. Open test-version-upTest_EX folder, Run Windows Enabler.exe as Administrator‘s authorization and turn it on by single click the icon of windows's tray.
4. Switch the phone to Download mode:
Turn off the phone, if you have not turned off.
Disconnect the USB cable from the phone if connected.
Hold down Volume Up and connect the USB cable to the phone.
Hold Volume Up until the screen: Download mode.
5. Open the folder test-version-upTest_EX and run the program UpTestEX_original.exe
6. Click on the folder icon in the row "Select kdz file" and select the file V20F_00.kdz
7. Click on "CSE web upgrade test".
8. In the window that appears, click on "Upgrade Start".
9. In the next window that appears, you will be prompted to select country and language, which will use the program.
10. The program will begin to flash update file V20F_00.kdz on your phone.
Rooting your P93x:
1.Copy LG_SystemBackupTest.apk from ROOT.rar to your phone's sdcard and intall it, run it.(download)
2.Enable USB debug mode, and connect your phone with computer by usb cable, then run root_P930.bat in your computer, then, let your PC do the rest. then you can get a rooted V20f firmware. alse, this method can root V20e, And maybe other's version firmware can be rooted by it too.

is this works in SU640 korean version?

jeonaztigz said:
is this works in SU640 korean version?
Click to expand...
Click to collapse
Use the guide I link to; it flashes a SU640 KDZ instead of the P93x.
http://forum.xda-developers.com/showthread.php?t=1784709

your files have errors & can not be extracted - can u post different file links that work

kdz-flash have virus
brianlili said:
I know there is a guide already here a long time ago, but Its step is kind of complicated. So, I figure it out another way, no need to set up a HTTP server to trick LG's update software.
I have tested it on V20f, everything works perfect. But remember, whatever you do, you do at your own risk and responsibility for your actions rests solely on you.
Unbricking part:
1. Install LG's cell phone driver, of cause.
2. Install B2CAppSetup.exe from kdz-flash.rar （download）
3. Open test-version-upTest_EX folder, Run Windows Enabler.exe as Administrator‘s authorization and turn it on by single click the icon of windows's tray.
4. Switch the phone to Download mode:
Turn off the phone, if you have not turned off.
Disconnect the USB cable from the phone if connected.
Hold down Volume Up and connect the USB cable to the phone.
Hold Volume Up until the screen: Download mode.
5. Open the folder test-version-upTest_EX and run the program UpTestEX_original.exe
6. Click on the folder icon in the row "Select kdz file" and select the file V20F_00.kdz
7. Click on "CSE web upgrade test".
8. In the window that appears, click on "Upgrade Start".
9. In the next window that appears, you will be prompted to select country and language, which will use the program.
10. The program will begin to flash update file V20F_00.kdz on your phone.
Rooting your P93x:
1.Copy LG_SystemBackupTest.apk from ROOT.rar to your phone's sdcard and intall it, run it.(download)
2.Enable USB debug mode, and connect your phone with computer by usb cable, then run root_P930.bat in your computer, then, let your PC do the rest. then you can get a rooted V20f firmware. alse, this method can root V20e, And maybe other's version firmware can be rooted by it too.
Click to expand...
Click to collapse
The file kdz-flash have virus, can you update that? tvm.

How to set device tampered back to false?

I will explain how to set the device tampered back to "false" on the Wileyfox Swift.
Required:
7z
WFS.7z (https://drive.google.com/file/d/0B6Ge199bCD5_NF9RWGhVLVhxajA/view?usp=sharing)
Windows 7 or 8
Driver Signature Enforcement disabled
Step 1: Brick the device on purpose
Hold Volume Up button+Volume Down button while plugging in USB
You should be see QHS_USB BULK in Device Manager
S
Step 2: Install Driver
Reboot with Driver Signature Enforcement disabled ( Google if you must)
Plug device in and make sure you see QHSUSB BULK in Device Manager
If you see Relink HS QDLoader 9008 uninstall it and delete driver software
Then refresh and you should see QHS USB BULK
Manually Update Driver software and navigate to driver folder extracted in WFS.7z
Step 3 : Install QPST provided in WFS.7z
I think its pretty straight forward
Step 4: Flash Firmware
Open QFil
Select Port and choose your device if not already chosen
Select Flat Build
Programmer Path must be prog_emmc_firehose_8916.mbn in the Maincode folder from WFS.7z
Build Path should automatically appear
Hit load XML.
Click rawprogram_upgrade.xml
Click patch0.xml
Click Download
Once done remove and reinsert battery
Step 5: Verify Tampered:False
boot into fastboot
type the following:
fastboot oem device-info
and it should say Device tampered : false and Device Unlock : False
NB: If you get a SaharaDownload fail or something just remove battery and USB for 5 seconds. Plug battery in. Then plug USB in.
NB: I do not accept any responsibility for damaged devices or anything. You point your finger at me and I will laugh at you
If it works don't hesitate to donate me a cup of coffee
PayPal : [email protected]

yasteellutch said:
Step 2: Install Driver
Reboot with Driver Signature Enforcement disabled ( Google if you must)
Plug device in and make sure you see QHSUSB BULK in Device Manager
If you see Relink HS QDLoader 9008 uninstall it and delete driver software
Then refresh and you should see QHS USB BULK
Manually Update Driver software and navigate to driver folder extracted in WFS.7z
Click to expand...
Click to collapse
This does not work for me, no matter wht I try, in the device manager I just get "Android" with a yello triangle.
No manual driver install / update (or update via windows update) solve that problem.
Try it on two Windows 7 PCs (x32 & x64) with Firewall, Antivirus and driver signature are disabled.
On a Windows 10 PC, the device connects as "Marshall London Device".

I don't think ur swift is bricked

when puting battery in jut get the screen "wileyfox"; recovery does not start (vol- and pwr) but fastboot mode ist working (vol+ and pwr). so it's not bricked?
so I repeat step 1 but still in windows 7 device manager having "Other Devices -> Android" with no yellow triangle.

I get SaharaDownload fail. Removing battary is useless. What else can i try? Thanks in advance

Now you get Sahara Fail. I think this is some sort of 'Lock Mode'. I fixed it by removing battery. Reinserting battery and immediately plugging in USB and hitting download

yasteellutch said:
Now you get Sahara Fail. I think this is some sort of 'Lock Mode'. I fixed it by removing battery. Reinserting battery and immediately plugging in USB and hitting download
Click to expand...
Click to collapse
I try and try do it again but i have only got sahara fail again and again.....

void2000 said:
I try and try do it again but i have only got sahara fail again and again.....
Click to expand...
Click to collapse
Upload a screenshot

yasteellutch said:
Upload a screenshot
Click to expand...
Click to collapse
Probably I have to use a special cable?

See it gets the SharaVersion right so I'm guessing that phone is in a correct state. The problem there could be that it didn't decompress properly. Maybe the integrity of your decompressed WFS.7z is not intact. Go to Android One(2nd Gen) dedicated page. I got help there. I guess all you need is to look there.

Maybe u didn't installQPSt right or the driver is a issue. I flashed stock like 3 days ago and it works perfectly

cyaneo said:
This does not work for me, no matter wht I try, in the device manager I just get "Android" with a yello triangle.
No manual driver install / update (or update via windows update) solve that problem.
Try it on two Windows 7 PCs (x32 & x64) with Firewall, Antivirus and driver signature are disabled.
On a Windows 10 PC, the device connects as "Marshall London Device".
Click to expand...
Click to collapse
Hey @cyaneo. If you still have the Yellow Android triangle this is because your drivers aren't installed correctly. I tried it. But that also means your fastboot is working.

Hi all,
Ive been a way from Android for a long time so I'm no expert but the method posted above failed for me. Like others, all my PC would recognise the phone as was "Marshall London Device" and essentially my phone was useless.
Can I ask why we need to erase and/or brick the phone?
Instead what worked for me was to reboot into fastboot mode, download Cyanogen OS signed zip, extract and run flash-radio.sh, then flash recovery and system manually. Reboot phone into working OS and then turn off OEM Unlock.
Once that's done I rebooted into fastboot and confirmed bootloader was locked and that tampered was false (as an official signed OS is installed I take it?).
Anyway as I say, I'm no expert but surely that's an easier and cleaner way than erasing/bricking a phone and only needs fastboot and the latest official signed rom from Cyanogen OS directly?

void2000 said:
Probably I have to use a special cable?
Click to expand...
Click to collapse
Hi,
This is my first post. (active lurker previously) hopefully its not too late.
In my experience on other device running 8916, a sahara failure can be overcame by holding the power button when entering download mode. (E.g: if you enter download mode by pressing and holding vol+/- simultaneously and plugging in usb cable, try holding the power button as well when you plug in the cable). This is normally a result of battery too low.

After bricking my Swift with some gymnastics around Android One firmware images, this tool worked flawlessly!
I was a bit confused when it came to the part of deleting/ manually reinstalling the driver. After the device was shown as "QHS_USB BULK", I manually installed the " Relink HS QDLoader 9008". Everything else went really smoothly. The device is good as new
For the adventurous ones with a Swift- this is one tough little phone. Hard-brick ain't a reason to stop

Pak0St said:
After bricking my Swift with some gymnastics around Android One firmware images, this tool worked flawlessly!
I was a bit confused when it came to the part of deleting/ manually reinstalling the driver. After the device was shown as "QHS_USB BULK", I manually installed the " Relink HS QDLoader 9008". Everything else went really smoothly. The device is good as new
For the adventurous ones with a Swift- this is one tough little phone. Hard-brick ain't a reason to stop
Click to expand...
Click to collapse
Lol I agree. This baby took some hits. I clocked it to 1.6 at stable. At 1.9 she became instable and started crashing #YeahITakeRisks

xfile087 said:
Hi all,
Ive been a way from Android for a long time so I'm no expert but the method posted above failed for me. Like others, all my PC would recognise the phone as was "Marshall London Device" and essentially my phone was useless.
Can I ask why we need to erase and/or brick the phone?
Instead what worked for me was to reboot into fastboot mode, download Cyanogen OS signed zip, extract and run flash-radio.sh, then flash recovery and system manually. Reboot phone into working OS and then turn off OEM Unlock.
Once that's done I rebooted into fastboot and confirmed bootloader was locked and that tampered was false (as an official signed OS is installed I take it?).
Anyway as I say, I'm no expert but surely that's an easier and cleaner way than erasing/bricking a phone and only needs fastboot and the latest official signed rom from Cyanogen OS directly?
Click to expand...
Click to collapse
Of course there is. Don't get me wrong I understand your point. But you need to remember there are log files and a bunch of other stuff lying around if you fastboot. When you use QFil it basically rewrites all the partitions thus no logs. I returned my first Swift with the IMEI issue and they gave me a new one in a week

Hi,
my Swift is also Bricked.... that means no bootloader boot or etc. i tried to flash the phone with this method but no success. my error with QFIL is this
COM Port number:20
Sahara Version:2
Start Sending Programmer
Download Fail:System.Exception: Unable to download Flash Programmer using Sahara Protocol
bei QC.QMSLPhone.Phone.QPHONEMS_SaharaArmPrgDownload(String sFileName)
bei QC.SwDownloadDLL.SwDownload.QPHONEMSSaharaDownloadArmPrg(UInt64& version, String armPrgPath)
Download Fail:Sahara FailSahara Fail
Finish Download
Click to expand...
Click to collapse
Thanks for response

Error
Download failded
Code:
Dowload fail:House fail failed to Upload the emmc images to phone using firehouse

vadimnew said:
Download failded
Code:
Dowload fail:House fail failed to Upload the emmc images to phone using firehouse
Click to expand...
Click to collapse
You made a mistake @vadimnew

[Solution] Those Having problem with flashing Stock ROM using SP Flash tool

If you are reading this I am guessing your device is in bootloop or soft bricked. In my case it was bootloop and my volume down button was broken so couldn't get into recovery. Then had go through many places to get the phone running again. Here is how.
>>>>>>>>>>>>>>>This is for windows only.<<<<<<<<<<<<<<<
First you will need to install the MTK 65XX preloader driver installed on your PC.
Download the driver from here and extract it.
Note that if you are using windows 8 you will need to disable enforced driver signature checking. Here is how.
Now turn off your mobile and remove the battery. Now right click on My Computer and click manage. There open device manager tab.
now press and hold the volume up button and while holding the button Connect the device to PC using USB cable.
your PC will beep. Now you will see MTK 65XX Preloader driver being not installed right click on it and Click on update driver. Now choose Browse. Then navigate where you downloaded and extracted your driver. Then choose the folder of XP/Vista/7(8-10) accordingly.
Once you have installed the driver now you are ready to go.
Download the necessary files from here
This link has both SP flash tool including the Stock ROM.
Now open the SP flash tool SP_Flash_Tool_v5.1352.01/flash_tool.exe/ and then click on scatter file and choose the file from the directory Software\UsbUpgradePackage/MTK6592_Android_scatter.txt
now press download.
now pull off the battery from the device if connected and after a few seconds connect it again but do not turn on. Now connect the phone to PC using USB cable and you will see a red bar down on the FLASH TOOL.. Well done. Now seat back and relax.
when the process is done fire up the device.
Here is the video where I got the flashing process part. Give him a thumbs up. And if my post helps I am glad.
Stock ROM and SP tools link is also from his video.
Don't hesitate to comment. I am not a dev but I will try to help.
I am a new user so aparantly XDA doesn't want me to post with links.. However Links are in the 1st reply. Cheers.

I am sorry
I can't even reply with LINKS so leave me a PM (personal message I will be in touch.

shafimehedi said:
I can't even reply with LINKS so leave me a PM (personal message I will be in touch.
Click to expand...
Click to collapse
it will help if error 5069 i have?

problem install driver MOOREFIELD

Hi everyone,
My zenfone 2 ZE551ML is bricked, so i followed this guide http://forum.xda-developers.com/zenfone2/general/guide-brick-soft-hard-bricked-zenfone-2-t3284256
The problem comes when i arrived to the step of IntelSoc:
I install it, no problem until here, i got IntelSoc driver in my device manager .
But when i want to have the MOOREFIELD driver, I cant get it. Following this perfectly
Ash back to the Zenfone 2, shutdown, press simultaneously the key "source" + "volume +", of course you will see a screen hanging cables( I don't have hanging cables though, I just have the Logo Asus and write on the top in blue Fastboot mod !!!).
-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.
If you have an idea can you help me please. I think this is the only thing who blocks me in repairing my phone...
Thank you

Yea that problem also persists with my zenfone 2,cant install moorefield 'cause pc cant recognize my phone. Somebody please help us out.

Anagh21 said:
Yea that problem also persists with my zenfone 2,cant install moorefield 'cause pc cant recognize my phone. Somebody please help us out.
Click to expand...
Click to collapse
it is clearly instructed in that thread you mentioned. just keep few things in mind.. uninstall every mobile related driver before installing isoc. uninstall xFSTK tool if you already installed it before installing isoc. third as you are concerned about the line you mentioned morefield under intel soc. well during soc install you will see windows like attached below. at this stage you need to power cycle your device . ( turn off your device holding power button for 10 sec. then connect to pc and turn on. leave connected to pc and turn off again and turn on second time to make sure so driver are installed) don't worry if you don't see morefield under soc now. just go ahead and install xFSTK. now your concern that your device don't stays in morefield download stage ( i mean it appears in device manager and disapear) . after installing xFSTK. run it as administrator and load files. and change gp flag value. also change device detection timeout to 120. now click begin download it will start waiting for device. now turn off your device completely and connect to pc and turn on. xFSTK will force it to stay in required mode. if download do not starts. just power cycle the device while being connected to the tool.
( note: it is strongly recomended that you install isoc and connect mobile before installing. if you have already installed xFSTK then plz uninstall it and install it after performing above said steps. remove all other mobile related drivers also and if you are using windows 8 or 10 disable driver signature enforcement again even if you did it earlier)

The problem with asus flash tool solved
Solution : Open device manager i.r. Windows + X .... if your phone is not being detected... switch it on and off ... there will be ( other devices menu ) that will show your phone there..
right click on the phone , click update drivers, ofcoarse no drivers online, locate the drivers manually , wherever your bootloader file is i.e. the 1 gb file you download or the raw file as we can speak ... i didn't pin pointed it ... my file was on the desktop so I just chose desktop and it searched it and installed it.
After that the phone was successfully in the computer and being detected by the flash tool.

Oneplus 3 bricked

I bricked my op3 and tried this guide https://forums.oneplus.com/threads/guide-mega-unbrick-guide-for-a-hard-bricked-oneplus-3.452634/ but at step 5 my phone is not under device manager. Neither unknown device or QHUSB_BULK .

xxxfuq said:
I bricked my op3 and tried this guide https://forums.oneplus.com/threads/guide-mega-unbrick-guide-for-a-hard-bricked-oneplus-3.452634/ but at step 5 my phone is not under device manager. Neither unknown device or QHUSB_BULK .
Click to expand...
Click to collapse
Can you enter in fastboot mode ? If yes try with command fastboot oem edl
If not you must turn off your phone ( press for 40 seconds power button - yes 40 seconds ) . Then press volume down button and connect your phone with pc . Now if you've installed drivers properly you should be in edl mode and it should show Qualcomm HS-USB QDLoader 9008 in device manager .

mar.ur said:
Can you enter in fastboot mode ? If yes try with command fastboot oem edl
If not you must turn off your phone ( press for 40 seconds power button - yes 40 seconds ) . Then press volume down button and connect your phone with pc . Now if you've installed drivers properly you should be in edl mode and it should show Qualcomm HS-USB QDLoader 9008 in device manager .
Click to expand...
Click to collapse
I cant enter fastmode. I get this but not exactly https://forums.oneplus.com/attachments/img_0387-jpg.452451/
I tried this with volume down but nothing happens in device manager. I installed the qualcomm driver but can you send me other drivers if necessary maybe thats why it wont show.

xxxfuq said:
I cant enter fastmode. I get this but not exactly https://forums.oneplus.com/attachments/img_0387-jpg.452451/
I tried this with volume down but nothing happens in device manager. I installed the qualcomm driver but can you send me other drivers if necessary maybe thats why it wont show.
Click to expand...
Click to collapse
I've installed Qualcomm drivers with miflash . Try this one from zuk z2 pro
https://androidfilehost.com/?fid=24659325368664618
Remember , you must disable drivers verification if you have windows 8 and above

mar.ur said:
I've installed Qualcomm drivers with miflash . Try this one from zuk z2 pro
https://androidfilehost.com/?fid=24659325368664618
Remember , you must disable drivers verification if you have windows 8 and above
Click to expand...
Click to collapse
didnt work

xxxfuq said:
didnt work
Click to expand...
Click to collapse
Did you disable drivers verification before you start install it ? It works on all Qualcomm devices . If you've installed drivers properly it must works. Maybe your phone is not turn off . Try to press power button longer than 40 s .
Edit @xxxfuq Sorry , my fault
Press volume up and connect with pc to enter in edl mode

mar.ur said:
Did you disable drivers verification before you start install it ? It works on all Qualcomm devices . If you've installed drivers properly it must works. Maybe your phone is not turn off . Try to press power button longer than 40 s .
Edit @xxxfuq Sorry , my fault
Press volume up and connect with pc to enter in edl mode
Click to expand...
Click to collapse
Yes i disabled drivers verification. My phone is turned off. I press 10 sec volume up and connect but in device manager my phone wont show.

xxxfuq said:
Yes i disabled drivers verification. My phone is turned off. I press 10 sec volume up and connect but in device manager my phone wont show.
Click to expand...
Click to collapse
Are you sure ? It is under ports ( com & lpt )

mar.ur said:
Are you sure ? It is under ports ( com & lpt )
Click to expand...
Click to collapse
So now I changed the usb hub and it shows now under Qualcomm HS-USB QDLoader 9008 (COM6) but there is a yellow symbol. I tried to update the driver manually with the inf file but it says that the file is damaged.

xxxfuq said:
So now I changed the usb hub and it shows now under Qualcomm HS-USB QDLoader 9008 (COM6) but there is a yellow symbol. I tried to update the driver manually with the inf file but it says that the file is damaged.
Click to expand...
Click to collapse
Hmm, it is diagnostic mode . I usually switch from 900e to 9008 with deepflash cable or with testpoints method . But I don't know if it works with OnePlus 3 .Try to restart phone an pc and repeat all ones again .

mar.ur said:
Hmm, it is diagnostic mode . I usually switch from 900e to 9008 with deepflash cable or with testpoints method . But I don't know if it works with OnePlus 3 .Try to restart phone an pc and repeat all ones again .
Click to expand...
Click to collapse
So finally after many hours I was able to install the driver. Thank you for your help!!

xxxfuq said:
I bricked my op3 and tried this guide https://forums.oneplus.com/threads/guide-mega-unbrick-guide-for-a-hard-bricked-oneplus-3.452634/ but at step 5 my phone is not under device manager. Neither unknown device or QHUSB_BULK .
Click to expand...
Click to collapse
It means that the proper drivers are not installed. Are you running Win 10?
If you follow that guide and use Method 2, any bricked OP3 can be revived. You may have to repeat some steps till it starts working. I restored mine with the same guide in XDA just three days back. Ensure that you have the latest ADB and other files since some of the files linked in that guide may have become outdated.
Edit: Sorry, didn't notice the subsequent posts.