Database Users

551ml Bricked after updating to new offical MM build. (help pls)

Hello guys, I noticed this morning that MM was officially released today. I followed the steps on to update my phone. I downloaded the rom for 551ml put it on my root of my internal storage, after that a pop up showed that there was a system update. I did the update and now my phone wont turn on now. It vibes twice and nothing comes on the screen. I have no idea how to fix it. I was on the latest firmware that system update would give me (184). If someone isn't busy could they possibly help me out. thx..

Same issue here, have you found a solution yet?

arturocr said:
Same issue here, have you found a solution yet?
Click to expand...
Click to collapse
tyring a guide atm but links seem to be outdated. I managed to get in fastboot or whatever its called when you can boot in to recovery. but from there I cant do anything.

You cant get into recovery after fastboot?
Sent from my ASUS_Z00AD using XDA Premium HD app

same problem ,
so im from cm 13 lastest build , and then i wipe data from twrp , after that i directly flash MM offical rom and its done without any problem. the problem start after i reboot system. my phone just vibrating twice with no lights led on , no screen on , no asus logo , can't go to recovery nor fastboot just keep restarting i guess because after a couple minute it vibrate again.
when i charge it wont show charging battrey , only stuck at battrey logo with zap with no charging animation.
don't have any clue. can anyone help ?
try to connect to pc but only show "moorefield" with (?).
sorry for my bad english.

Same for me...

baonxxx said:
same problem ,
so im from cm 13 lastest build , and then i wipe data from twrp , after that i directly flash MM offical rom and its done without any problem. the problem start after i reboot system. my phone just vibrating twice with no lights led on , no screen on , no asus logo , can't go to recovery nor fastboot just keep restarting i guess because after a couple minute it vibrate again.
when i charge it wont show charging battrey , only stuck at battrey logo with zap with no charging animation.
don't have any clue. can anyone help ?
try to connect to pc but only show "moorefield" with (?).
sorry for my bad english.
Click to expand...
Click to collapse
I think mm system.img boot.img splashcreen.img need mm bootloder to run and at the moment twrp doesnt work with it, if you install mm via twrp you only updating these img and bootloader still lp that causes your phone cant boot. (Correct me if im wrong)
So now you need xfstk downloader to recover your fastboot and then flash .194 raw firmware using asus flash tool then adb sideload mm firmware from stock .194 recovery, theres guide how to do that in here but im forget where
Sorry my english are bad too..

miku1024 said:
I think mm system.img boot.img splashcreen.img need mm bootloder to run and at the moment twrp doesnt work with it, if you install mm via twrp you only updating these img and bootloader still lp that causes your phone cant boot. (Correct me if im wrong)
So now you need xfstk downloader to recover your fastboot and then flash .194 raw firmware using asus flash tool then adb sideload mm firmware from stock .194 recovery, theres guide how to to that in here but im forget where
Sorry my english are bad too..
Click to expand...
Click to collapse
how does make xfstk work ? don't have idea how. it just show nothing after i open xfstk , have a reference link ?

baonxxx said:
same problem ,
so im from cm 13 lastest build , and then i wipe data from twrp , after that i directly flash MM offical rom and its done without any problem. the problem start after i reboot system. my phone just vibrating twice with no lights led on , no screen on , no asus logo , can't go to recovery nor fastboot just keep restarting i guess because after a couple minute it vibrate again.
when i charge it wont show charging battrey , only stuck at battrey logo with zap with no charging animation.
don't have any clue. can anyone help ?
try to connect to pc but only show "moorefield" with (?).
sorry for my bad english.
Click to expand...
Click to collapse
baonxxx said:
how does make xfstk work ? don't have idea how. it just show nothing after i open xfstk , have a reference link ?
Click to expand...
Click to collapse
I found the link!
You need You need asus usb and intel soc drivers
Heres
http://forum.xda-developers.com/zenfone2/general/guide-fix-bricked-ze550ml-ze551ml-usb-t3405840

Try this: http://forum.xda-developers.com/zenfone2/general/guide-how-to-update-to-official-mm-t3452082

miku1024 said:
I think mm system.img boot.img splashcreen.img need mm bootloder to run and at the moment twrp doesnt work with it, if you install mm via twrp you only updating these img and bootloader still lp that causes your phone cant boot. (Correct me if im wrong)
So now you need xfstk downloader to recover your fastboot and then flash .194 raw firmware using asus flash tool then adb sideload mm firmware from stock .194 recovery, theres guide how to do that in here but im forget where
Sorry my english are bad too..
Click to expand...
Click to collapse
I used XFSTK to upload firmware etc... but after upload firmware, the phone will vibrate twice and download of OS will not start... the soft will try 20 attemps to connect with the phone and the OS part can't be download on the phone... I'm stick at this point.

Hello guys, i'm trying to unbrick my phone, i'm following this guide http://forum.xda-developers.com/zenf...l-usb-t3405840 but when i get to the end of te install of intelSoC my device is detected as Moorefield for like 4-5 seconds and then it disappears. I've been trying to solve this for like 4 hours now, a little help would be much appreciated.

quarterbreed said:
tyring a guide atm but links seem to be outdated. I managed to get in fastboot or whatever its called when you can boot in to recovery. but from there I cant do anything.
Click to expand...
Click to collapse
try this if you unable to flash
http://forum.xda-developers.com/zenfone2/help/thead-bricked-phone-updating-to-mm-tips-t3452785

sukhwant717 said:
try this if you unable to flash
http://forum.xda-developers.com/zenfone2/help/thead-bricked-phone-updating-to-mm-tips-t3452785
Click to expand...
Click to collapse
I did this morning and it worked. Im on 6.0.1 now, I guess the cause of my brick was that I had TWRP installed. Now I know next time to remove it before updating lol.

quarterbreed said:
I did this morning and it worked. Im on 6.0.1 now, I guess the cause of my brick was that I had TWRP installed. Now I know next time to remove it before updating lol.
Click to expand...
Click to collapse
glad to know that it worked. but sad to know that despite that you didn't hit thanks

quarterbreed said:
I did this morning and it worked. Im on 6.0.1 now, I guess the cause of my brick was that I had TWRP installed. Now I know next time to remove it before updating lol.
Click to expand...
Click to collapse
If you don't need to use twrp everyday (maybe just a backup from time to time) you'd better keep stock recovery and whenever you need something from twrp, you just boot into it without flashing with the usual "fastboot boot twrp.img" command. That way if you ever upgrade again you don't have to remember whether you removed twrp before. But that's just an opinion, since if done that way, you'd need to have yor phione hooked to a computer to get into twrp, an that's not always possible.

thanks
quarterbreed said:
I did this morning and it worked. Im on 6.0.1 now, I guess the cause of my brick was that I had TWRP installed. Now I know next time to remove it before updating lol.
Click to expand...
Click to collapse
sukhwant717 said:
try this if you unable to flash
http://forum.xda-developers.com/zenfone2/help/thead-bricked-phone-updating-to-mm-tips-t3452785
Click to expand...
Click to collapse
that link saved my phone, thanks man

sukhwant717 said:
glad to know that it worked. but sad to know that despite that you didn't hit thanks
Click to expand...
Click to collapse
I just hit thanks now, I was at my limit of 8 at the time.

Mi Flash Error Discussion

Discussion on problems faced by Miflash tool.
*So when used for the first time I was able to unlock phone without any problem.
*But after that when I used it for second time to unbrick my phone I was constantly getting errors like not enough memory,some errors like x800000 blah blah...
*I almost went through every solutions mentioned in miui forum and XDA...But I was unable to get it working...
So if anyone faced any problem like that comment your problem below..
Aftef a lot of research I was able to find a solution for that..
Hopefully it will be shared with you all as soon as possible. I have to finish touching up some final things..
As soon as I finish the work I will be releasing alpha version..
Will update the thread when I release it

Waiting for the solution.
https://chat.whatsapp.com/H3jQvVgU5MZCRrlOFqSlIG
My Redmi Note 3 Qualcomm Whatsapp Group

Murshad007 said:
Waiting for the solution.
https://chat.whatsapp.com/H3jQvVgU5MZCRrlOFqSlIG
My Redmi Note 3 Qualcomm Whatsapp Group
Click to expand...
Click to collapse
Hopefully I was able to make alpha version of the software...worked fine for me on fastboot mode..want some testers
Edit..was able to boot up successfully..once confirmed by some testers I will release stable one

I experienced that "Not enough memory" thing. What I did was I used the latest MiFlash tool (restarted my PC first).

exce1ia said:
I experienced that "Not enough memory" thing. What I did was I used the latest MiFlash tool (restarted my PC first).
Click to expand...
Click to collapse
Yeah I faced it many time...not enough memory, buffer size0000 error blah blah blah...hopefully I was able to develop an app for to unbrick via fastboot... tried by me 2 times worked smooth but need some testers

Mi Flash & Nougat
Hi, if you want I'm ready to test your alpha version!
I have a dead Mi5 Pro (updated to xiaomi.eu Nougat rom) that my pc only reads as Qualcomm_9008.
I already tried many many posted potential solutions but my phone is still dead!
At this point, I HOPE that the problem is that latest MiFlash (30.aug.2016) is not so compatible with Nougat and I can't flash any ROM!
Waiting for your news!
Thank you very much

cleo1986 said:
Hi, if you want I'm ready to test your alpha version!
I have a dead Mi5 Pro (updated to xiaomi.eu Nougat rom) that my pc only reads as Qualcomm_9008.
I already tried many many posted potential solutions but my phone is still dead!
At this point, I HOPE that the problem is that latest MiFlash (30.aug.2016) is not so compatible with Nougat and I can't flash any ROM!
Waiting for your news!
Thank you very much
Click to expand...
Click to collapse
https://forum.xda-developers.com/redmi-note-3/development/mi-fastboot-unbrick-tool-2-0-t3538614
Already released...
Edit use manual method..

No fastboot
adithyan25 said:
https://forum.xda-developers.com/redmi-note-3/development/mi-fastboot-unbrick-tool-2-0-t3538614
Already released...
Edit use manual method..
Click to expand...
Click to collapse
Thanks mate, but NOWAY to Fastboot here! My Mi5 is completely dead and I think in EDL because my pc can recognize it as Qualcomm device.

cleo1986 said:
Thanks mate, but NOWAY to Fastboot here! My Mi5 is completely dead and I think in EDL because my pc can
recognize it as Qualcomm device.
Click to expand...
Click to collapse
Try pressing vol down+pwr... If you see light blinking while connected to PC,that means you are in edl..
We are working on a tool that can flash through edl, the last tool was for fastboot unbrick...
In order to make sure you are in edl.connect phone to PC,open miflashtool and click refers..
If it shows something like COMXX (XX will be num) its in edl..u can flash stock rom via flashtool then

Already TRIED
adithyan25 said:
Try pressing vol down+pwr... If you see light blinking while connected to PC,that means you are in edl..
We are working on a tool that can flash through edl, the last tool was for fastboot unbrick...
In order to make sure you are in edl.connect phone to PC,open miflashtool and click refers..
If it shows something like COMXX (XX will be num) its in edl..u can flash stock rom via flashtool then
Click to expand...
Click to collapse
I already tried many times to flash in EDL via miflash but I have error 0x000..., hello packet, etc etc
PLEASE LET ME KNOW WHEN YOU HAVE EDL Tool!
Thank you very much

Ok so I have managed to brick my device pretty good (recovery seems gone), but I can get to FASTBOOT, and from there, followed a guide to get to EDL..
So now I got the mi flash tool to flash the 7.25 image as described by this guide :
https://forum.xda-developers.com/redmi-note-3/how-to/unlock-bootloader-twrp-root-7-2-3-t3359492
No errors, but I don't think it worked because when the device reboots, it still can't seem to try and load a kernel (it goes black real quick). I am hoping it that the other unmentioned fields need populating etc..
Are there instructions on how to do a complete flash from EDL anywhere ?

Rapalax said:
Ok so I have managed to brick my device pretty good (recovery seems gone), but I can get to FASTBOOT, and from there, followed a guide to get to EDL..
So now I got the mi flash tool to flash the 7.25 image as described by this guide :
https://forum.xda-developers.com/redmi-note-3/how-to/unlock-bootloader-twrp-root-7-2-3-t3359492
No errors, but I don't think it worked because when the device reboots, it still can't seem to try and load a kernel (it goes black real quick). I am hoping it that the other unmentioned fields need populating etc..
Are there instructions on how to do a complete flash from EDL anywhere ?
Click to expand...
Click to collapse
https://forum.xda-developers.com/redmi-note-3/how-to/fix-bootloop-redmi-note-3-recovery-edl-t3521297
This will work for a complete clean flash via edl

Yep.. I managed to do something similar with a newer FB ROM and the modded twrp so there is less chance to relock my BL.
Thanks for providing the post.. it makes me feel more comfortable knowing that this info is available in case I need it again

Temporary Fix for LG G4 bootloop issue(lengthens life)

Hello everyone.
You all might have read in the xda news that @XCnathan32 fixed the Nexus 6p and now also the Nexus 5 bootloop issue (same as on our G4s) by disabling the big faulty cores and running the phone on only the small ones. Now our beloved dev @steadfasterX has come up with a similar fix for our G4.
it works by flashing modified boot and TWRP image onto the LG G4 so that it only works on the small four cores
UPDATE: Tested and found working by @the_naxhoo on his H815
Requirements
An unlocked G4
@steadfasterX 's FWUL for ease and required tools (lglaf)
Patience and prayers (optional though)
NOTE: the attached files are only for the T-Mobile variant which had 20o software before boot looping and the International H815 (BGR) variant which had 20g software before bootlooping
Guide:​
(A)For unlocked devices that can access Fastboot
Access Fastboot mode by using the following method:
Pull out battery then connect usb cable, press volume down, put battery back while keeping volume down pressed
Click to expand...
Click to collapse
If you just reached the Fastboot mode, Congrats. Now execute the following commands in fastboot
Code:
fastboot flash boot boot.img
fastboot flash recovery twrp_4cores_3.1.1-1-g4.img
Now you have a kernel and twrp with max 4 CPUs and the faulty CPUs disabled. Enjoy your resurrected phone.
(B)For Devices that can not acess Fastboot(unlocked only)
For a backup of your existing data you need an external SD Card big enough for a full backup of your device (64 GB if you want to backup the /data partition - otherwise you will be fine with 8 GB) best is to format the SD card with ext4 !! fat32 will fail for backup
For just flashing a boot image any SD card will fit..
1)extract both files you downloaded(see attached files) and put them on the SD card
2)boot FWUL and login
3)put the external SD card in your phone
4)boot phone to download mode and connect it to your PC with FWUL running
5)in FWUL find the folder LG on the desktop and open it
double click on the lglaf (auth) icon
6)you should see the lglaf shell now. Type in the command:
Code:
uname -a
(it should print out the line with your current kernel version which just indicates that you're connected)
7)mount external SD:
Code:
mount -t ext4 /dev/block/mmcblk1p1 /storage/external_SD
8)Now backup first (recommended but optional):
Update regarding backing up:
Check out the new guide here: https://tinyurl.com/dlbackup
9)Now flash:
Code:
dd if=/storage/external_SD/boot.img of=/dev/block/mmcblk0 seek=491520 bs=512
Code:
dd if=/storage/external_SD/twrp_4cores_3.1.1-1-g4.img of=/dev/block/mmcblk0 seek=573440 bs=512
Now you have a kernel and twrp with max 4 CPUs and the faulty CPUs disabled. Enjoy your resurrected phone.
Please test and leave comments
Support / IRC Channel
IRC means Internet Relay Chat and you will get best support there only.
Choose how to get in:
PC (HexChat and Pidgin are only 2 of them! This list is not complete!)
Android (Yaaic, AndChat, HoloIRC, AndroIRC are only a few of them! This list is not complete!)
Web (KiwiIRC-Web,FreenodeWebchat])
When you have to choose a channel it is: #Carbon-user
When you be asked for a server network choose: freenode
Update: File for h815 20i is here: https://forum.xda-developers.com/g4/general/fix-lg-g4-bootloop-issue-t3647538/post73282829
File for h815 20p is here: https://forum.xda-developers.com/g4/general/fix-lg-g4-bootloop-issue-t3647538/post73610856
File for H811 20r is here: https://forum.xda-developers.com/g4/general/fix-lg-g4-bootloop-issue-t3647538/post73636261

Any chance of getting this for international H815 version with H81520g firmware?
Sent from my iPad using Tapatalk

Stransky said:
Any chance of getting this for international H815 version with H81520g firmware?
Click to expand...
Click to collapse
sure I'll update the OP with it soon

Stransky said:
Any chance of getting this for international H815 version with H81520g firmware?
Click to expand...
Click to collapse
please give me the link to the v20g kdz firmware

XeniX_Force said:
please give me the link to the v20g kdz firmware
Click to expand...
Click to collapse
hi,
Here you find it all:
https://lg-firmwares.com/lg-h815-firmwares/
ist there a way to disable the big cores on any rom (original/custom) for all time?

skdubg said:
hi,
Here you find it all:
https://lg-firmwares.com/lg-h815-firmwares/
ist there a way to disable the big cores on any rom (original/custom) for all time?
Click to expand...
Click to collapse
there might be @steadfasterX is currently working on this. he'll tell you after that hopefully

XeniX_Force said:
please give me the link to the v20g kdz firmware
Click to expand...
Click to collapse
As posted by (skdubg) and select GBR version.

skdubg said:
hi,
Here you find it all:
https://lg-firmwares.com/lg-h815-firmwares/
ist there a way to disable the big cores on any rom (original/custom) for all time?
Click to expand...
Click to collapse
Atm the method is ROM specific. That means I need a direct link or the EXACT file name to the used kdz. E.g. H815 has several country versions.
Disabling the cores on any ROM means modifying aboot which is not an option because even when your device is unlocked the try may soft or hard brick.
Instead once I have the time I will make a flashable TWRP zip for this which patches the boot image after flashing a ROM but this is a manual task everytime after flashing a ROM.
Stransky said:
As posted by (skdubg) and select GBR version.
Click to expand...
Click to collapse
Perfect thx.
Sent from my LG-H815 using XDA Labs

Anyone with an bootlooped H811 who can try this?
The file for h815 will be uploaded soon

Stransky said:
As posted by (skdubg) and select GBR version.
Click to expand...
Click to collapse
find attached the patched boot image for your ROM version.
just to mention it again: the modded twrp image is highly recommended to flash as well bc TWRP will make use of all cores it can find when backing up/restore
when your device is unlocked AND you have fastboot access you can just do a
Code:
[COLOR="Blue"]fastboot flash boot boot_4cores.img
fastboot flash recovery twrp_4cores.img[/COLOR]
The download mode way I described in the OP is required when you cannot access fastboot and for locked devices. I will try to create a KDZ out of this but atm this is the way to go then.
I cannot say for sure that this way will soft brick locked devices or not. it should not but i cannot test it..!!
It mainly depends on the fact if the whole boot image gets verified or just the kernel + initrd.
afaik its not the whole boot partition... so it should work with the download mode way even on locked devices.
@XeniX_Force : attach the file and fastboot cmds to the OP as well pls.
.

Stransky said:
Any chance of getting this for international H815 version with H81520g firmware?
Click to expand...
Click to collapse
The OP has been edited with a fastboot method. you can either use it or the download mode method to try and revive your G4 your requested file has been attached please try and report to us as soon as possible

The only fix for a G4 rebooting is the remove the LPDDR3, reball and replace it.

rustybronnco said:
The only fix for a G4 rebooting is the remove the LPDDR3, reball and replace it.
Click to expand...
Click to collapse
not necessarily. the problem is with the bigger cores. why replace ram?

The issue is failed solder joints between the SOC and the LPDDR3. Disabling cores will not keep it from occurring.

rustybronnco said:
The issue is failed solder joints between the SOC and the LPDDR3. Disabling cores will not keep it from occurring.
Click to expand...
Click to collapse
but we tested on the_naxhoo's bootlooped phone and it's back to working

https://en.wikipedia.org/wiki/LG_smartphone_bootloop_issues
When officially acknowledging the bootloop issues with the G4, LG stated that it was caused by a "loose contact between components";
Click to expand...
Click to collapse
---------- Post added at 02:41 PM ---------- Previous post was at 02:35 PM ----------
XeniX_Force said:
but we tested on the_naxhoo's bootlooped phone and it's back to working
Click to expand...
Click to collapse
Applying pressure to the chip may also bring it back to a non-boot loop condition.
My G3 has a credit card 'shim' between the LPDDR3 and the housing. It cured? the fad out to black for a period of time. They also blue or green screened as well. On the G4 it shows up as a boot looping or stop (stuck) booting condition. My G4 is currently at LG awaiting a motherboard.

rustybronnco said:
https://en.wikipedia.org/wiki/LG_smartphone_bootloop_issues
---------- Post added at 02:41 PM ---------- Previous post was at 02:35 PM ----------
Applying pressure to the chip may also bring it back to a non-boot loop condition.
My G3 has a credit card 'shim' between the LPDDR3 and the housing. It cured? the fad out to black for a period of time. They also blue or green screened as well. On the G4 it shows up as a boot looping or stop (stuck) booting condition. My G4 is currently at LG awaiting a motherboard.
Click to expand...
Click to collapse
understood
the thread has been renamed
our phone is hopeless

Don't get me wrong, this may help extend the life of certain units. But as they say, it might be just a matter of time before the problem rears its ugly head once again.
https://www.reddit.com/r/lgg4/comme...boot_looping_g4_replaced_for/#bottom-comments

XeniX_Force said:
The OP has been edited with a fastboot metho,chave d. you can either use it or the download mode method to try and revive your G4 your requested file has been attached please try and report to us as soon as possible
Click to expand...
Click to collapse
Hi
Thanks for the files. Have a new problem in that my G4 has stopped bootlooping, in fact it is not doing anything now.
Have tried another battery but no response, Was on the Lifes Good screen and it suddenly
went blank and it will not boot to anything. Tried spare battery and connected to charger but nothing.
Any ideas?

Stransky said:
Hi
Thanks for the files. Have a new problem in that my G4 has stopped bootlooping, in fact it is not doing anything now.
Have tried another battery but no response, Was on the Lifes Good screen and it suddenly
went blank and it will not boot to anything. Tried spare battery and connected to charger but nothing.
Any ideas?
Click to expand...
Click to collapse
yea bootloop is the first stage. next one is what u describe. send it to repair.
there are good chances that it went into QDL 9008 mode. Just connect it to your PC and watch unknown devices in your device manager (or type lsusb on linux) and see what happens.
.
.

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

SOLVED:Stuck at PIN input, then reboots

Well, I f*cked up.
Fastboot works, I can flash stock rom via Xiaomi Flash. Flashing completes without any problems. A notification about encypting phone shows up, at 3% it jumps to 100% and resumes boot. Now after each boot, phone freezes at "input your sim pin" and reboots. Over and over again. What can I try, please help :

edited

twister26 said:
There is an reward for whoever helps me solve this issue
Click to expand...
Click to collapse
u try put your sim on other phone and remove the pin from them , maybe the boot skip that part and dont get freeze

dfranco51207 said:
u try put your sim on other phone and remove the pin from them , maybe the boot skip that part and dont get freeze
Click to expand...
Click to collapse
no luck, removed sim and now it reboots as soon as android one text is displayed
I've also tried wiping cache in default recovery, no luck

twister26 said:
no luck, removed sim and now it reboots as soon as android one text is displayed
I've also tried wiping cache in default recovery, no luck
Click to expand...
Click to collapse
Try to format data in twrp or stock recovery.
If it does not work flash an android 8.0 or Nougat ROM. Do not lock the bootloader.

Let me guess. From Pie to Oreo or Nougat?

Mercoory said:
Let me guess. From Pie to Oreo or Nougat?
Click to expand...
Click to collapse
yes, exactly is there a thread already open somewhere here and i missed? last time TWRP was working, I even got a message "your system has been destroyed" or something like that.
sipollo said:
Try to format data in twrp or stock recovery.
If it does not work flash an android 8.0 or Nougat ROM. Do not lock the bootloader.
Click to expand...
Click to collapse
will try!

https://forum.xda-developers.com/mi-a1/how-to/tutorial-downgrade-9-0-to-8-1-edl-imei-t3879624

ccalixtro said:
https://forum.xda-developers.com/mi-a1/how-to/tutorial-downgrade-9-0-to-8-1-edl-imei-t3879624
Click to expand...
Click to collapse
will give it a read, it it works, I'll PM you and you'll give me your paypal address. Fair is fair.
can't unlock OEM, because I can't boot up to developer tools. great, just great. will try to fix that first.

if you can boot to fastboot try to flash stock pie 10.0.4.0 with miflash, after that your device should be able to boot, than unlock OEM and bootloader and downgrade to what version you want

fdc77 said:
if you can boot to fastboot try to flash stock pie 10.0.4.0 with miflash, after that your device should be able to boot, than unlock OEM and bootloader and downgrade to what version you want
Click to expand...
Click to collapse
I can get to fastboot yeah, but MiFlash tool says that remote oem unlock is not allowed. So I'll probably have to open it up for EDL. Reboot to edl isn't working. Thanks for the advice tho.

twister26 said:
I can get to fastboot yeah, but MiFlash tool says that remote oem unlock is not allowed. So I'll probably have to open it up for EDL. Reboot to edl isn't working. Thanks for the advice tho.
Click to expand...
Click to collapse
i had a problem like yours, but i have flashed stock rom in non EDL mode and everything had start to work apart LTE band missing that i restored with qualcomm's tools
which stock rom have you try to flash? are you downgrading from oreo? bootloop on android one logo after downgrading is a common issue due to ARB (anti rollback protection)

twister26 said:
Whoever saves my precious Mi A1 gets 10$ on his paypal.
Click to expand...
Click to collapse
This is ****
This is not XDA spirit
You can get help without to pay
Please cancel the reward, do it. For all the people on this community.

tropbel said:
This is ****
This is not XDA spirit
You can get help without to pay
Please cancel the reward, do it. For all the people on this community.
Click to expand...
Click to collapse
reward is cancelled from this point on i will reward the one who helped me so far tho. still working on solving the problem so winner has not been decided yet.

you don't understand.
There are no winners and no loosers.
You are free to donate to anyone you want, but your post boost and encourages a bad attitude.
If people start to solve only paid problems, the spirit of the community will be destroyed.

The problem is with the Pie specific partition table
I write the whole guide from memory, so it can differ a bit.... I skipped some steps ( erasing, reboot, fastboot mode, TWRP loading via fastboot, OEM unlock )
From previous writings I think you can know the skipped steps.
Keep in mind: It is dangerous, you can loose your IMEI ( it will only work again with Pie - or there are some writings at forum how can you manually change it. ).
Steps:
1 - Backup with TWRP (fastboot) efs,persist,modem & make copy to your computer and or to your cloud provider.
2 - Create a new folder in Internal Storage -> TWRP -> BACKUP -> With a new date directory ( the backup already made one, make a new folder, with different date )
3 - Download someone's older TWRP backup from xda (I cheated, I copied the following links ) :
(I'm still a new user, so can't directly write url's )
Mediafire : https COLON SLASH SLASH bit.ly SLASH 2QU5NtC
Mirror: Google Drive : https COLON SLASH SLASH bit.ly SLASH 2UN1DTo
4 - Unpack, and copy EFS to the folder created 2 point
5 - Fastboot TWRP -> Restore EFS
6 - Flash the Official latest firmware from en.miui.com ( If you want to make sure go with EDL mode )
7 - Now, the IMEI & Mac addresses are missing. Don't panic! Download update with System Updates.
8 - When you are on Pie again, restore your first TWRP (fastboot) persist partition
9 - One more System restore
At this time, you will have IMEI & Mac addressees, and hopefully a working phone.
Hope this helps. The same thing happened with me 2 weeks ago. This is how I solves it.

Thank you, I solved it yesterday. Hopefully this post will come in handy for other people!