Database Users

Nexus 4 kitkat update error

So I just got my OTA for 4.4 and downloaded the update. So I hit the restart and install button. The installing process ran like it supposed to be until the end part of it. The screen showed the word "error" with the android logo laying down. Then the phone just stayed like that and the screen not changing. So I decided to turn off the phone. Then I booted up the phone again, the google screen shows normally, but after that it shows the screen showing "no command" and I am stuck with that screen now and cannot go in. So I researched about it and find out I need to go to recovery mode. Then I hit the vol up and power button, then hit the recovery mode. But still, it shows the no command screen again.
Please help me... Thanks

Same issue here. Nexus 4 (rooted) OTA update from 4.3 to 4.4 failed. "No command" error. Please help

It's not pressing then together, have you tried this: http://forum.xda-developers.com/showpost.php?p=44388152&postcount=13

eksasol said:
It's not pressing then together, have you tried this: http://forum.xda-developers.com/showpost.php?p=44388152&postcount=13
Click to expand...
Click to collapse
It worked, now what do I do? I don't want to wipe all my data ._.
Is there a way to get the update and install it ?

GIANTLIZARDMAN said:
It worked, now what do I do? I don't want to wipe all my data ._.
Is there a way to get the update and install it ?
Click to expand...
Click to collapse
Check in the general section, there are a ton of info on this. i'll give you the links this time.
Follow the Scenario #1 instruction from here:http://forum.xda-developers.com/showthread.php?t=2145848
Or qbking77 video: http://forum.xda-developers.com/showthread.php?t=2537410

eksasol said:
Check in the general section, there are a ton of info on this. i'll give you the links this time.
Follow the Scenario #1 instruction from here:http://forum.xda-developers.com/showthread.php?t=2145848
Or qbking77 video: http://forum.xda-developers.com/showthread.php?t=2537410
Click to expand...
Click to collapse
I really don't know what to do, since I can't turn on my phone and get into the settings to check the USB Debugging I can't do anything with my phone plugged into my computer.... so.... what should I do? ((((

GIANTLIZARDMAN said:
I really don't know what to do, since I can't turn on my phone and get into the settings to check the USB Debugging I can't do anything with my phone plugged into my computer.... so.... what should I do? ((((
Click to expand...
Click to collapse
Just watch the video and follow its instruction, you enabled the adb sideload command in the stock recovery. It has nothing to do with USB Debugging whatsoever.

eksasol said:
Just watch the video and follow its instruction, you enabled the adb sideload command in the stock recovery. It has nothing to do with USB Debugging whatsoever.
Click to expand...
Click to collapse
Followed the instructions shown in the video, but when I try to install the 4.4 update it gives me an error:
set_metadata_recursive: some changes failed
E:Error in /tmp/update.zip
(Status 7)
Installation aborted.
Once again.... please help me.

GIANTLIZARDMAN said:
Followed the instructions shown in the video, but when I try to install the 4.4 update it gives me an error:
set_metadata_recursive: some changes failed
E:Error in /tmp/update.zip
(Status 7)
Installation aborted.
Once again.... please help me.
Click to expand...
Click to collapse
Status 7 usually means something wrong with the package (or your recovery version isn't compatible, which is not the case in this scenario). So either your file is corrupt or you downloaded the wrong package to update. What package you use depends on what version you come from. You can either use:
4.4-KRT16S-from-JWR66Y
4.4-KRT16S-from-KRT16O
If you are unsure, try the first one, then the other. It's most likely the first though or your package is corrupt, so redownload it: http://forum.xda-developers.com/showthread.php?t=2145848
Also try using wipe cache' option in the recovery to see if it help. (The factory reset option will wipe all your data.)

eksasol said:
Status 7 usually means something wrong with the package (or your recovery version isn't compatible, which is not the case in this scenario). So either your file is corrupt or you downloaded the wrong package to update. What package you use depends on what version you come from. You can either use:
4.4-KRT16S-from-JWR66Y
4.4-KRT16S-from-KRT16O
If you are unsure, try the first one, then the other. It's most likely the first though or your package is corrupt, so redownload it: http://forum.xda-developers.com/showthread.php?t=2145848
Also try using wipe cache' option in the recovery to see if it help. (The factory reset option will wipe all your data.)
Click to expand...
Click to collapse
Hi, I have tried both packages twice and re-downloaded them, and also wipe cache. I'm still getting the error status 7 installation aborted. I dont know what to do now. Please help im stuck.

I got it with the method in your sig. Flash factory image without wiping data (a different method) (short, if bootloader already unlocked). Thanks!

eksasol said:
Status 7 usually means something wrong with the package (or your recovery version isn't compatible, which is not the case in this scenario). So either your file is corrupt or you downloaded the wrong package to update. What package you use depends on what version you come from. You can either use:
4.4-KRT16S-from-JWR66Y
4.4-KRT16S-from-KRT16O
If you are unsure, try the first one, then the other. It's most likely the first though or your package is corrupt, so redownload it: http://forum.xda-developers.com/showthread.php?t=2145848
Also try using wipe cache' option in the recovery to see if it help. (The factory reset option will wipe all your data.)
Click to expand...
Click to collapse
tippingvan said:
Hi, I have tried both packages twice and re-downloaded them, and also wipe cache. I'm still getting the error status 7 installation aborted. I dont know what to do now. Please help im stuck.
Click to expand...
Click to collapse
GIANTLIZARDMAN said:
I really don't know what to do, since I can't turn on my phone and get into the settings to check the USB Debugging I can't do anything with my phone plugged into my computer.... so.... what should I do? ((((
Click to expand...
Click to collapse
I'm having the same problem.
I had 4.2 stock (JOP40C).
I used NRT to unlock and root.
I then got an OTA update for 4.3 (JWR66Y, I believe) and lost root.
I was going to re-root, but received another OTA for 4.4, so I figured I'd install it before re-rooting.
Unfortuntately, I didn't re-enable USB debugging, which may be my current issue.
The install encountered an error (Android on his back and little red triangle).
Now I can't get past Recovery.
I tried installing 4.4 from JWR66Ymanually via adb using methods described here and get the status 7 message shown above.
If I try installing 4.4 from KRT160 I get an error indicating my device has the wrong keys (seems to imply not the right starting version for the upgrade).
I've also tried flashing the factory JWR66Y ROM from the Google site using adb. When I do that, I get a "signature verification failed" message.
It looks like there may be a way around this if a flash a different recovery. Can I do that with adb?
I can't connect with NRT anymore. I ahve some backups I made with NRT, but am not sure how to load them without using NRT.
I can sideload with adb, but can't do much else. "fastboot devices" doesn't return anything.
Help!
Thanks!

[Q] Did I brick my phone?

Hello,
I have a LG G2 (D802). I was busy flashing the stock KDZ, when I got an error. The progress on my phone stopped, and nothing happened anymore. I wanted to try again, so I turned my phone off. Now, when I boot my phone, it gives the LG logo, and then nothing. When I connect it to my pc, I get a lot of format pop-ups.
I followed this tutorial: http://forum.xda-developers.com/showthread.php?t=2432476
The KDZ I used: Netherlands Open 16GB KitKat D80220D
Furthermore, also while connected to the pc, I only see a folder called "image".
Can someone help me with getting my phone back to stock? It doesn't matter if everything gets wiped, I already backed up everything.
Thanks in advance!

If lots of drives still pop up when you connect your phone to the PC,then follow this guide:https://www.youtube.com/watch?v=hQVTc2m6U-I
I did it,and it fixed my download mode,and I could finally access Download Mode.
If your Download Mode still works,try the TOT method,it worked for me,since the KDZ method would be stuck at 2% every time(in my case).
So,after,or if your download mode works,do try the TOT method.

The Marionette said:
If lots of drives still pop up when you connect your phone to the PC,then follow this guide:https://www.youtube.com/watch?v=hQVTc2m6U-I
I did it,and it fixed my download mode,and I could finally access Download Mode.
If your Download Mode still works,try the TOT method,it worked for me,since the KDZ method would be stuck at 2% every time(in my case).
So,after,or if your download mode works,do try the TOT method.
Click to expand...
Click to collapse
Thanks for your reply, but unfortunately, I even can't get the phone into fastboot mode.
Here are some pictures to show what's inside the "image" folder in the first local disk (= first partition?): 1: http://i.imgur.com/InFoiXA.png 2: http://i.imgur.com/YzjXOmQ.png 3: http://i.imgur.com/JDEnUfa.png

MistaahD said:
Thanks for your reply, but unfortunately, I even can't get the phone into fastboot mode.
Here are some pictures to show what's inside the "image" folder in the first local disk (= first partition?): 1: http://i.imgur.com/InFoiXA.png 2: http://i.imgur.com/YzjXOmQ.png 3: http://i.imgur.com/JDEnUfa.png
Click to expand...
Click to collapse
So you basically cant access the recovery,fastboot nor the Download Mode,right?
Try asking for help on this thread:http://forum.xda-developers.com/showthread.php?t=2432476
People there really know how to help,they helped me there too
Just dont panic,even if your phone is in a "hard brick" state(doubtfully),there is a fix for it too.
I suggest you do not do anything without consulting with other members.
You just have to be patient.
EDIT
Oh,and go to the Device Manager and tell me what name your G2 has when connected to the PC.

The Marionette said:
So you basically cant access the recovery,fastboot nor the Download Mode,right?
Try asking for help on this thread:http://forum.xda-developers.com/showthread.php?t=2432476
People there really know how to help,they helped me there too
Just dont panic,even if your phone is in a "hard brick" state(doubtfully),there is a fix for it too.
I suggest you do not do anything without consulting with other members.
You just have to be patient.
EDIT
Oh,and go to the Device Manager and tell me what name your G2 has when connected to the PC.
Click to expand...
Click to collapse
Indeed, there's really no mode that I can use...
Thanks, I'll ask for help there too! And my phone is being recognized as "QHSUSB_BULK".

MistaahD said:
Indeed, there's really no mode that I can use...
Thanks, I'll ask for help there too! And my phone is being recognized as "QHSUSB_BULK".
Click to expand...
Click to collapse
Hmm,QHSUSB_BULK and no drives popping out?
EDIT
And are you sure you have the LG USB Drivers installed?
EDIT#2
And did you try to install the drivers to another PC and connecting your phone to that PC?

The Marionette said:
Hmm,QHSUSB_BULK and no drives popping out?
EDIT
And are you sure you have the LG USB Drivers installed?
EDIT#2
And did you try to install the drivers to another PC and connecting your phone to that PC?
Click to expand...
Click to collapse
Yep, drivers are installed.
And there are also a lot of drives popping out! See this screenshot: http://i.imgur.com/RcMrAYv.png
Edit: I will try connecting it to another pc now.

MistaahD said:
Yep, drivers are installed.
And there are also a lot of drives popping out! See this screenshot: http://i.imgur.com/RcMrAYv.png
Click to expand...
Click to collapse
Ugh thank god
those drives SHOULD be popping out
Right click on My Computer and select "Manage"
Then,on the left part of that window,you will see the "Disk Management" option. Click it
Then,you should see a certain Disk which is separated into tons of parts.
This part is crucial!
To me,my PCs Hard Drive was "Disk 0",and my fastboot G2 was "Disk 1"
Please tell me which "Disk _" your g2 is.
You can folow this videowithout my help(I could do it by myself in 3 A.M.,so you can do it too! ),I am basically helping you with the same method.
If you want me to proceed with helping you,do tell.

The Marionette said:
Ugh thank god
those drives SHOULD be popping out
Right click on My Computer and select "Manage"
Then,on the left part of that window,you will see the "Disk Management" option. Click it
Then,you should see a certain Disk which is separated into tons of parts.
This part is crucial!
To me,my PCs Hard Drive was "Disk 0",and my fastboot G2 was "Disk 1"
Please tell me which "Disk _" your g2 is.
You can folow this videowithout my help(I could do it by myself in 3 A.M.,so you can do it too! ),I am basically helping you with the same method.
If you want me to proceed with helping you,do tell.
Click to expand...
Click to collapse
My phone is on Disk2. I am now trying to follow this guide, I'll let you know how it worked out.
Edit: wow! I now get the firmware update screen!! What should I do now? What to flash?

MistaahD said:
My phone is on Disk2. I am now trying to follow this guide, I'll let you know how it worked out.
Edit: wow! I now get the firmware update screen!! What should I do now? What to flash?
Click to expand...
Click to collapse
Download the kdz suitable for your model and flash it with LG Flash Tool.
Follow the "Back to stock" guide which you mentioned in the OP.
There will be a link to the KDZ archive for various models,and make sure that you select the kdz for the 32 GB variant if you have a 32 GB variant. Because it will be dangerous if you flash a 16gb variant kdz on a 32 gb phone.
Sent from my LG-D802 using XDA Forums Pro.
EDIT
And if the same thing happens when flashing,fix it again(if it won't access the download mode) and try to flash while using another PC.

Mate, you are the freakin' best!!!! Mah phone works again!!! Now I'm going to install CloudyG2_3.3. What are the steps I need to perform in order to NOT(!!!) brick my phone again?
That'll be my last question, I can't thank you enough!

MistaahD said:
Mate, you are the freakin' best!!!! Mah phone works again!!! Now I'm going to install CloudyG2_3.3. What are the steps I need to perform in order to NOT(!!!) brick my phone again?
That'll be my last question, I can't thank you enough!
Click to expand...
Click to collapse
So the kdz flash worked,and the stock rom boots?
Sent from my LG-D802 using XDA Forums Pro.

Yea it works! I used the stock KK rom though, since Cloudy requires the KK bootloader. I did it right here yes?

MistaahD said:
Yea it works! I used the stock KK rom though, since Cloudy requires the KK bootloader. I did it right here yes?
Click to expand...
Click to collapse
Yes,excellent job.
To root,download "Towelroot" to your phone,install it and press the "Make it rain" button,then install SuperSU,then look for "AutoRec" and make sure you get the version for your variant.
That is just halfway,I will tell you the rest tomorrow,it is 00:26 and I have to get up at 07:00. xD
Sent from my LG-D802 using XDA Forums Pro.

Haha cheers! I think I got it from there, it's just that I don't want to do it in a wrong order haha ;P
And thanks a lot, again! Get your deserved sleep, I should do that too.. Gotta go up at 06:45 hah!! I WIN! xD

Okay,moving on.
Download the BUMPED TWRP from this thread:http://forum.xda-developers.com/lg-g2/development/twrp-twrp-2-8-0-0-kernel-f2fs-tools-t2898705
It is in a flashable zip,so just flash it with the TWRP which was installed by AutoRec.
You must have the bumped version of TWRP!!
After you flashed the BUMP TWRP,reboot recovery.
Here is a bootloader changer,AROMA edition:http://forum.xda-developers.com/lg-g2/general/d802-bootloader-changer-1-1-jb-kk-lp-t3104380
1.Wipe data/factory reset
2.Flash the Bootloader Changer,in AROMA choose the KK bootloader,and install.
3.Flash CloudyG2 3.3
4.Reboot

The Marionette said:
Okay,moving on.
Download the BUMPED TWRP from this thread:http://forum.xda-developers.com/lg-g2/development/twrp-twrp-2-8-0-0-kernel-f2fs-tools-t2898705
It is in a flashable zip,so just flash it with the TWRP which was installed by AutoRec.
You must have the bumped version of TWRP!!
After you flashed the BUMP TWRP,reboot recovery.
Here is a bootloader changer,AROMA edition:http://forum.xda-developers.com/lg-g2/general/d802-bootloader-changer-1-1-jb-kk-lp-t3104380
1.Wipe data/factory reset
2.Flash the Bootloader Changer,in AROMA choose the KK bootloader,and install.
3.Flash CloudyG2 3.3
4.Reboot
Click to expand...
Click to collapse
Hey man,
I noticed that Towelroot doesn't work for LG G2 Lollipop. Any idea how to fix this?
Edit: trying it with another root.
Edit 2: rooted. Going to flash now.

Alright it works, thanks! Can you tell me why I need the bumped version? Just curious

MistaahD said:
Alright it works, thanks! Can you tell me why I need the bumped version? Just curious
Click to expand...
Click to collapse
It is complicated,just do it. XD
I was asking the same thing like you.I ignored others,rushed with roms,didnt use the BUMPED TWRP and my phone was bricked.
Basically the TWRP you get with AutoRec is just capable of flashing partitions for the bootloader,not the system partition(the rom is in the system partition).
The BUMPED TWRP has a certain type of an exploit,and lets us install those system partitions.
Shortly:You can't install roms without the BUMPED TWRP.
Sent from my LG-D802 using XDA Forums Pro.

I'm guessing my phone is refurbished?
I bought a D802 from a third-party, with:
- 32GB ROM
- 4.4.2 D80220b firmware
- 2G, 3G, 4G working
- The csmg.lgmobile.com website said that according to my IMEI, my model is the UAE 32GB D802 and gave me the D80230a firmware for manual flash via LG Flash tool.
I used the phone for a while, rooted it and used Xposed. Never got recovery so no backup(wish I'd seen the SRK tool before). Then I downloaded the firmware from the csmg.lgmobile.com website. I flashed it via the Flash tool and everything seemed fine. Then it booted:
- Touchscreen was erratic. Ghost touches, dead spots, phantom touches, whatever.
- The Baseband Version and IMEI in About Phone both say Unknown
- ROM has converted to a 16GB version
- Download mode is fine along with every other feature of the phone
After that I looked around and found a UAE D80220c firmware and flashed that. It flashed fine but all the above issues remained the same.
I browsed around extensively here and found out:
- Refurbished phones have their back cover and firmware changed to imitate D802's.
- My phone is probably some other G2 model with D802 firmware and an altered IMEI
- The actual model of my device is UNDER the motherboard. Which, apparently, I must get hold of so I can flash the appropriate stock kdz. This gets a bit too hardware-y for me.
So, basically, my phone is no more useful than a brick at the moment. Any expert help would be appreciated but here are the main questions that I'd really like answered:
A. Should I try various flashing the kdz files from different models mentioned in the link I gave up ^there until one clicks and then try to do something about the IMEI?
B. Is there any chance that my phone is beyond repair forever?
C. Should I stop messing around with my mediocre knowledge and take it to a repair shop?

Le pro 3 x720 brick?

Hi, since yesterday I have a big problem with my le pro 3, while charging the phone suddenly turned off. The system did not want to turn on, so I went into recovery (TWRP) and tried to format and upload a new rom, unfortunately during the flashing, a blue screen appeared. When changing the kernel, the flashing of the rom was done, but with the installation of the gapps it hung. I tried to install another rom, but it also spilled, with this addition, that I can not enter recovery, because artifacts appear or reboots.. Only fastboot works. With it, I tried to flash the kernel, recovery, but it did not do anything. I also used (TOOL ALL in ONE) and uploaded the stock rom, but the phone still does not work. Do you know what else could help, or is buying a new phone? Thanks for help

If you can use fast boot, your phone is not hard bricked. A brick is when you can not do anything , you will have a black screen and a red blinking light if a usb cable is connected.
Try pushing Twrp ( newest version) to the phone. If that is successful boot to recovery, fully wipe your phone, reboot to recovery and install you Rom> Gapps, and Magisk. I would suggest initially flashing Lineage 15.1. Once your phone is restored, flash whatever you would like.
If it doesn't work try another cable, or another port, or another computer. Computer needs to be up to date and you may need to temporarily disable antivirus, if the All in One tool isn't working its likely that your computer is blocking the install. especially if you are using Windows 10. All the program to be open within your firewall settings. Make sure its up to date and use AIO to update android drivers and adb.

I'm not giving anything, I still can't get into recovery

miichus said:
I'm not giving anything, I still can't get into recovery
Click to expand...
Click to collapse
Click reply to the person you are talking to otherwise, they will not receive a notification of your response.
Next, if you expect some help, be courteous, to people spending their own limited free time to help with your self created issue by clicking the thank you button.
Finally read this link: https://forum.xda-developers.com/showpost.php?p=76947769&postcount=4

tsongming said:
Click reply to the person you are talking to otherwise, they will not receive a notification of your response.
Next, if you expect some help, be courteous, to people spending their own limited free time to help with your self created issue by clicking the thank you button.
Finally read this link: https://forum.xda-developers.com/showpost.php?p=76947769&postcount=4
Click to expand...
Click to collapse
The operation in flashone goes well, but it still does not help. System and recovery does not boot, only fastboot

miichus said:
The operation in flashone goes well, but it still does not help. System and recovery does not boot, only fastboot
Click to expand...
Click to collapse
What does the log say?
if you are getting no errors at at and can only boot to fastboot try the All in One tool or use the QPST method to unbrick. Also, some posted versions of Qfil are corrupted. Did you use the version that I provided a link for?

tsongming said:
What does the log say?
if you are getting no errors at at and can only boot to fastboot try the All in One tool or use the QPST method to unbrick. Also, some posted versions of Qfil are corrupted. Did you use the version that I provided a link for?
Click to expand...
Click to collapse
For the second time I tried to use flashOne and the phone started up. When entering the pin code, the phone was stuck again. When I wanted to reboot, I could only enter fastboot again.

miichus said:
For the second time I tried to use flashOne and the phone started up. When entering the pin code, the phone was stuck again. When I wanted to reboot, I could only enter fastboot again.
Click to expand...
Click to collapse
For the second time I tried to use flashOne
Click to expand...
Click to collapse
Okay sure, I provided you with a link to the correct files to use. I.E Flash 2.0 and le_zl1_qfil_ufs_fix.zip
Twice you have mentioned that you are using flash One, when you should be using flash 2.0
What Pin code?
Your pin error sounds like you are either using the old Qfil ( its corrupted, and never worked for anyone. ) Or the technician repair rom did not complete. There will be a log file on the PC from Flash 2, not the phone, is port 9008 open in device manager?
There should be no pin code, if qfil was installed, all of your data would be wiped, did you encrypt the phone with 3rd party software?
Are also using the wrong version of Qfil?
Review these additional steps
https://forum.xda-developers.com/showpost.php?p=76100899&postcount=121

tsongming said:
Okay sure, I provided you with a link to the correct files to use. I.E Flash 2.0 and le_zl1_qfil_ufs_fix.zip
Twice you have mentioned that you are using flash One, when you should be using flash 2.0
What Pin code?
Your pin error sounds like you are either using the old Qfil ( its corrupted, and never worked for anyone. ) Or the technician repair rom did not complete. There will be a log file on the PC from Flash 2, not the phone, is port 9008 open in device manager?
There should be no pin code, if qfil was installed, all of your data would be wiped, did you encrypt the phone with 3rd party software?
Are also using the wrong version of Qfil?
Review these additional steps
https://forum.xda-developers.com/showpost.php?p=76100899&postcount=121
Click to expand...
Click to collapse
I am using flashone 2.0 and flashing from your link, the file "le_zl1_qfil_ufs_fix.zip". Port 9008 is open. After three flash in 2.0 flash, I could enter recovery, but when flashing custom rom, a blue screen appeared.

Not enough information, did you follow all of the steps? You can't just flash a Rom after unbricking.
To be clear
You restored the phone, booted into the system, turned on developer options, checked oem unlocking, booted into recovery, and did a factory reset to repair the storage as outlined in my instructions link?
Then booted into the system again, turned on developer options, checked oem unlocking, checked that storage is accurate?
From this point you start over, if your storage issue isn't fixed you will get a blue screen.
After you have perform those steps you should be able to use the all in one tool to check that the bootloader is unlocked, install the latest TWRP, compatible Rom, Gapps and latest magisk.
If you still have issues after all of that. No doubt, its hardware related. It could be one part or several parts. Time to buy a new phone.
Sent from my Pixel XL using XDA Labs

tsongming said:
Not enough information, did you follow all of the steps? You can't just flash a Rom after unbricking.
To be clear
You restored the phone, booted into the system, turned on developer options, checked oem unlocking, booted into recovery, and did a factory reset to repair the storage as outlined in my instructions link?
Then booted into the system again, turned on developer options, checked oem unlocking, checked that storage is accurate?
From this point you start over, if your storage issue isn't fixed you will get a blue screen.
After you have perform those steps you should be able to use the all in one tool to check that the bootloader is unlocked, install the latest TWRP, compatible Rom, Gapps and latest magisk.
If you still have issues after all of that. No doubt, its hardware related. It could be one part or several parts. Time to buy a new phone.
Sent from my Pixel XL using XDA Labs
Click to expand...
Click to collapse
Once we managed to load the system, which hung up after 3 seconds and the whole situation started again. Failed to reload the system or enter recovery. I did all the steps in turn. After the system startup I did not even manage to enter the settings, because it has already hung up and restarted.

miichus said:
Once we managed to load the system, which hung up after 3 seconds and the whole situation started again. Failed to reload the system or enter recovery. I did all the steps in turn. After the system startup I did not even manage to enter the settings, because it has already hung up and restarted.
Click to expand...
Click to collapse
That sucks!
Its either that the partitions are inaccurate or you have hardware problems.
If its partitions, its not something that I have experience with. However, I did find this link; which has instructions for resolving partition issues using the MiniTool Partition Wizard and HDD Raw Copy Tool. https://www.leakite.com/2016/06/revised-how-to-unbrick-qualcomm-android.html

tsongming said:
That sucks!
Its either that the partitions are inaccurate or you have hardware problems.
If its partitions, its not something that I have experience with. However, I did find this link; which has instructions for resolving partition issues using the MiniTool Partition Wizard and HDD Raw Copy Tool. https://www.leakite.com/2016/06/revised-how-to-unbrick-qualcomm-android.html
Click to expand...
Click to collapse
Hi tsongming Where do I get this files ???
* prog_emmc_firehose_8936.mbn (I think for our x720 has to be prog_emmc_firehose_8916.mbn)
* rawprogram0.xml
* patch0.xml
I have seen this procedure on different sites but none of them provide this files
I hope you can help me
Thanks in advance

mavelino said:
Hi tsongming Where do I get this files ???
* prog_emmc_firehose_8936.mbn (I think for our x720 has to be prog_emmc_firehose_8916.mbn)
* rawprogram0.xml
* patch0.xml
I have seen this procedure on different sites but none of them provide this files
I hope you can help me
Thanks in advance
Click to expand...
Click to collapse
They should download automatically, if you follow the instructions on those previous Links . The instructions should show which folders the files are located in.
Luckily, I saved these files the last time I de-bricked someones phone.
Here is the link to my Google Drive: https://drive.google.com/open?id=1mjvi_FR4Xh9QfSg6imMLduQ6p3zP2e_u
See the Thanks button: Click it, send cash or both.

tsongming said:
They should download automatically, if you follow the instructions on those previous Links . The instructions should show which folders the files are located in.
Luckily, I saved these files the last time I de-bricked someones phone.
Here is the link to my Google Drive: https://drive.google.com/open?id=1mjvi_FR4Xh9QfSg6imMLduQ6p3zP2e_u
See the Thanks button: Click it, send cash or both.
Click to expand...
Click to collapse
Noup they do not download automatically (I followed the instructions), I tried flashone tool procedure in a windows 7 computer and did not work (I already tried this a lot of times on to differente laptops with windows 10), I have not tried the qfil procedure because I do not have the files I mentioned before. Please if you have them upload them (* prog_emmc_firehose_8996.mbn* rawprogram0.xml* patch0.xml)
Thanks in advance

mavelino said:
Noup they do not download automatically (I followed the instructions), I tried flashone tool procedure in a windows 7 computer and did not work (I already tried this a lot of times on to differente laptops with windows 10), I have not tried the qfil procedure because I do not have the files I mentioned before. Please if you have them upload them (* prog_emmc_firehose_8996.mbn* rawprogram0.xml* patch0.xml)
Thanks in advance
Click to expand...
Click to collapse
All I have is in the link you just responded to.
if that doesn't work try unpacking the Qfil and and see if you can just extract them.
I will look further when I get back home.

i also have an bricked LEX 3 Pro . i bought it as an X722 but of cause iam not shure . could also be an X720. i can not find the difference.
so Phone has only fastboot.
when i plug in usb cable it just reboot every 10 sec . no charging sreen appears
i flash Qfil, but not helped it stay the same

[Help] MLA-L03 No OS, no Backup, Black Screen need help.

I've probably messed this thing up just about as badly as I can.
Here's what I can tell you:
Update: I just figured out that you are supposed to put dload onto a separate sd card, So i'll be trying that when the phone comes out of it's coma XD anything else you can suggest is very welcome.
- The phone currently isn't turning on after messing around in twrp(tried to restart into bootloader)
- While trying to get it working, it is now showing up as CAN-L11(likely from trying some backups of others)
- I was unable to use ANY roms I tried. full update files didn't work. always error 7
- It seems in twrp that I'd often get this error: mountencrypt failed to mount /data, despite wiping /data many times
- I've tried using iso files extracted from some update.app, and using that to get system and data on there, as well as recovery too
- I was switching between twrp and default recovery to transfer files and then use dload to try to recover the system, never let me do it though. got to 5% then told me something like: "Getting package info failed". it would do this in the download and recover mode as well when I would hook up to the internet and it would also give me that error.
You are free to ask me any questions about the device.
I think I just need to drain the battery then I should be able to at least get something out of it, but until then, if anyone has any recommendations after it's functional again let me know. Any help is appreciated.

TheProgrammerEX said:
I've probably messed this thing up just about as badly as I can.
Here's what I can tell you:
- The phone currently isn't turning on after messing around in twrp(tried to restart into bootloader)
Click to expand...
Click to collapse
It isn't even charging?
- While trying to get it working, it is now showing up as CAN-L11(likely from trying some backups of others)
Click to expand...
Click to collapse
Yeah, that's why. The model name can be changed in build.prop, but you're still using a CAN-L11 ROM though.
- I was unable to use ANY roms I tried. full update files didn't work. always error 7
Click to expand...
Click to collapse
You haven't flashed the TWRP mentioned in the first post of their thread, hence you've got that error which is basically telling you that you're trying to flash the ROM on an unsupported device (the phone's codename / model is mentioned in TWRP and ROM checks for it), but actually it's working on all models.
- It seems in twrp that I'd often get this error: mountencrypt failed to mount /data, despite wiping /data many times
Click to expand...
Click to collapse
That occurs because TWRP doesn't support decryption. You have to format data, not wipe. You can format it from TWRP > Wipe > Format data.
- I've tried using iso files extracted from some update.app, and using that to get system and data on there, as well as recovery too
Click to expand...
Click to collapse
What happened after you've tried that?
- I was switching between twrp and default recovery to transfer files and then use dload to try to recover the system, never let me do it though. got to 5% then told me something like: "Getting package info failed". it would do this in the download and recover mode as well when I would hook up to the internet and it would also give me that error.
Click to expand...
Click to collapse
Try to unplug the cable from PC. Also, note that I've read in past somewhere that the firmwares from Firmware Finder has to be approved by Huawei and if it isn't, then the stock recovery will fail to flash it. Other Huawei phones has modified / patched stock recovery which allows to flash unapproved firmwares though.
You are free to ask me any questions about the device.
Click to expand...
Click to collapse
How do you guys end up like this? xD
Update: I just figured out that you are supposed to put dload onto a separate sd card, So i'll be trying that when the phone comes out of it's coma XD anything else you can suggest is very welcome.
Click to expand...
Click to collapse
Hah, here's the answer to the above question: not reading xD. Try to slap the phone to wake it from the coma ahahahah xD. When did it get into coma though?

Device not detecting in Adb devices but gets detect in fastboot devices

Hi, everyone I tried to flash a new recovery on X00T but before I did this I Wiped all the data except internal storage. I Flashed the new recovery (completely forget about there being no OS) I rebooted to recovery and ignored the no OS message as the device rebooted I came on a black screen even the fast boot mode screen was black. I had no idea what to do so I tried to install the old TWRP from power shell/Adl so I could have a recovery and then install Custom rom again from recovery.
But there when I try to flash a file with command
-> Fastboot flash Recovery ....(..= file name)
It is shown completed on pc but on android even after rebooting I can't get anything except the black screen. This is what I get when I enter the following commands
-> fastboot devices
My devices number is shown
but if I type.
-> adl devices
My device is not shown.
But when I press the recovery buttons on device adl devices Is able to recognise device as a recovery screen device.
And the extra bonus on this is when I try to flash rom or fimware from adl. It says unable to read zip file.
So can anyone tell me if there is a way to fix this unable to read zip file problem. (I have tried uninstalling and reinstalling drivers from device manager & tried installing 64 bit files also)
Is there a command to flash rom from recovery. Or any way to fix this black screen
Thanks to everyone for reading any advice would be really helpful at this time.

Try using Asus Flash Tool to flash stock ROM

Tianhe said:
Try using Asus Flash Tool to flash stock ROM
Click to expand...
Click to collapse
Thanks for helping, Will surely try it. Can you please provide the link from where i can download flash tool?

Xda user 101 said:
Thanks for helping, Will surely try it. Can you please provide the link from where i can download flash tool?
Click to expand...
Click to collapse
I am not sure if posting external links (except hosting sites) is permitted. A simple google search or search within XDA will give you the results. In case you face difficulty, PM me.

Try to use this adb
If it still doesn't get detected, maybe use usb hub.
I wrote a thread guiding people on how to install stuff and my experience (issues) that is similar to yours. Not sure if my thread will help ya though

Vysair said:
Try to use this adb
If it still doesn't get detected, maybe use usb hub.
I wrote a thread guiding people on how to install stuff and my experience (issues) that is similar to yours. Not sure if my thread will help ya though
Click to expand...
Click to collapse
Bro tried as you said but didn't worked but finally found a solution. Now device is on and working again.

If anyone else face this issue I followed this thread https://forum.xda-developers.com/as...uide-revert-to-stock-rom-lock-t3798420/page46
It worked on my phone it is on again. Will have to root again but learned my lesson will never try new twrp when there is no os installed. :laugh:

thanks you Tianhe and Vysair for your advice for solving the issue.