Database Users

[Q][9001]Telephone can't power on

....

What do you mean with "I've locked my screen on my sgs+ with CM9 by arco".
Explain what you did.
Have you flashed his recovery.img before you tried to install the zip within CWM? If so, which command did you use?
What was the last thing you did/saw on your phone?

——

VinceBoxx said:
the rom was ok.. I've put the new recovery with cwm. The last think that I've done with my telephone is lock the screen... Whent I've pressed the hold button to use the telephone and the screen don't respose. So I've tryed to remove and reinsert the battery and power on, but it don't do anything
Click to expand...
Click to collapse
Try to connect your phone with your computer with your usb cable. Does it recognize your phone / does it charge?
If not pull your battery out/put in again and try again.
Some people already explained that they phone would suddenly reboot or shutdown when beeing too long in standby but they can turn on their phoone normally.
I'm afraid your phone is bricked when nothing helps.
Please describe every step you did.
Which ROM and recovery did you use before flashing Arco's Recovery.img?
How did you installed the Recovery.img, did you use Adb shell or the Odin package?
Did you wiped your data and cache?
Have you tried to restore something from your GB ROM with eg Titanium backup?
And so on.
Edit:
I'm pretty sure Arco isn't reading this forum section. Please gather all information and post your detailed problem in
http://forum.xda-developers.com/showthread.php?t=1336253&page=126

——-

VinceBoxx said:
I've flashed recovery with a cwm packege posted in the cyanogenmod porting 3rd.
Click to expand...
Click to collapse
So you installed the recovery.img (CWM package) through Feamod Recovery? Was that CWM package uploaded by Arco?
It's always your risk to flash a custom ROM and you should lose your warranty officially (at least that's what they say and want u to believe). Give them the information that this problem appeared while flashing an official update with KIES.

—/

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.

P8 Lite strange brick

Hello i'm a new user of this forum and i'm italian so sorry for my bad english. I'm an enthusiast android user.
now i have a perfectly working p9 lite but 1 year ago i had bricked my old p8 lite and today i returned to work on it but the problem are the same as before.
1 year ago the android 5 lollipop was the latest for the p8 lite and i rooted with no problem with random root application unfortunally maybe kingroot...... but all was ok for months. after i updated my p8 lite to android 6 mm and i tried to root, after many tryes i sucsessfull root my device, but the xda framework didnt work at all at that time the mm version was too new. so i tried to rollback to android 5, but i didn t know about a correct rollback update, so i flashed android 5's boot, cust, recovery and system.img via fastboot. i saw that the sim didn't recognised and so i discovered that the imei was lost........ And believe it or not, this is not entirely the problem.... after that i was in panic and i went to assistance and there they tell me that the motherboard was to replace.... so for the cost of the entire phone i decided to not pay. after i tried to follow so many guides my friend, you not even any ideas.... but one guide seems to work, i had to flash b049 or b52 (don not remember) and after my b190 but at the b49/b52 it give balong problem, after i fixed with a vendor little flash but the imei was completely gone in every versions..... i was sad... but while a flash and another thi biggest problem born.......... the phone bootloop, but NOT a normal bootloop, it starts correctly every versions but after 10 seconds of a working os ( i can go in settings, start application ec but it give up and restart totally not explayned.... i've formatted 1000 times and the force update fail or bootloop itself at 10 or 11% (10seconds....) same with recovery... only in rescue/fastboot mode it do not restart after 10 seconds and in the twrp 3.0.2 that i tried to flash every modded firmware in zip and at system flash it restart (seems like the 10 second stuff). now the imei problem is not a request because now i've the p9 lite and i dont need the phone things but the system.... its unplayble with the 10 secodns restart loop.... please is hard but HELP.

Franseven said:
Hello i'm a new user of this forum and i'm italian so sorry for my bad english. I'm an enthusiast android user.
now i have a perfectly working p9 lite but 1 year ago i had bricked my old p8 lite and today i returned to work on it but the problem are the same as before.
1 year ago the android 5 lollipop was the latest for the p8 lite and i rooted with no problem with random root application unfortunally maybe kingroot...... but all was ok for months. after i updated my p8 lite to android 6 mm and i tried to root, after many tryes i sucsessfull root my device, but the xda framework didnt work at all at that time the mm version was too new. so i tried to rollback to android 5, but i didn t know about a correct rollback update, so i flashed android 5's boot, cust, recovery and system.img via fastboot. i saw that the sim didn't recognised and so i discovered that the imei was lost........ And believe it or not, this is not entirely the problem.... after that i was in panic and i went to assistance and there they tell me that the motherboard was to replace.... so for the cost of the entire phone i decided to not pay. after i tried to follow so many guides my friend, you not even any ideas.... but one guide seems to work, i had to flash b049 or b52 (don not remember) and after my b190 but at the b49/b52 it give balong problem, after i fixed with a vendor little flash but the imei was completely gone in every versions..... i was sad... but while a flash and another thi biggest problem born.......... the phone bootloop, but NOT a normal bootloop, it starts correctly every versions but after 10 seconds of a working os ( i can go in settings, start application ec but it give up and restart totally not explayned.... i've formatted 1000 times and the force update fail or bootloop itself at 10 or 11% (10seconds....) same with recovery... only in rescue/fastboot mode it do not restart after 10 seconds and in the twrp 3.0.2 that i tried to flash every modded firmware in zip and at system flash it restart (seems like the 10 second stuff). now the imei problem is not a request because now i've the p9 lite and i dont need the phone things but the system.... its unplayble with the 10 secodns restart loop.... please is hard but HELP.
Click to expand...
Click to collapse
Do you have access to rescue mode/fastboot? Maybe flashing TWRP would help
P.S.-- DON'T EVER RUN KINGROOT ON P8LITE; MAYBE IT WILL SUCCESS, BUT YOUR DEVICE WILL BE MESSED UP

XTutorials said:
Do you have access to rescue mode/fastboot? Maybe flashing TWRP would help
Click to expand...
Click to collapse
yes, Maybe I was not clear but rescue mode is the only one where no automatic restart occurs. I twrp it and tried it but it did not help. If you are expert please give me more advice

Franseven said:
yes, Maybe I was not clear but rescue mode is the only one where no automatic restart occurs. I twrp it and tried it but it did not help. If you are expert please give me more advice
Click to expand...
Click to collapse
I have some questions:
1. What means"I twrp it" ? I know you're italian but please more details; did you flashed it succesfully?
More, I want a response to this question first

XTutorials said:
I have some questions:
1. What means"I twrp it" ? I know you're italian but please more details; did you flashed it succesfully?
More, I want a response to this question first
Click to expand...
Click to collapse
I successfully flashed the twrp recovery and trying to flash the zip while the firmware reboots while flashing the system

Franseven said:
I successfully flashed the twrp recovery and trying to flash the zip while the firmware reboots while flashing the system
Click to expand...
Click to collapse
Try here it might work

cristi.blidariu said:
Try here it might work
Click to expand...
Click to collapse
in fastboot mode hicare don't see my device, If you think that this particular version b132 changes something I try but I think it will restart every 10 seconds as the others ..

Franseven said:
I successfully flashed the twrp recovery and trying to flash the zip while the firmware reboots while flashing the system
Click to expand...
Click to collapse
For this fix, you should have and sd card
Download sokkoban's emui 4.0.3 B596, copy to sd card, erase everything in TWRP (cache, dalvik, data, system, internal storage), then flash the .zip you copied to the sd card.

XTutorials said:
For this fix, you should have and sd card
Download sokkoban's emui 4.0.3 B596, copy to sd card, erase everything in TWRP (cache, dalvik, data, system, internal storage), then flash the .zip you copied to the sd card.
Click to expand...
Click to collapse
Also by deleting everything in the twrp recovery the other .zip phones will restart as twrp is copying system, with b596 should not happen?

Franseven said:
Also by deleting everything in the twrp recovery the other .zip phones will restart as twrp is copying system, with b596 should not happen?
Click to expand...
Click to collapse
Maybe, try

XTutorials said:
Maybe, try
Click to expand...
Click to collapse
nope.. i've tried right now and it do same thing

Franseven said:
nope.. i've tried right now and it do same thing
Click to expand...
Click to collapse
Try to erase everything in twrp -->>advanced wipe-->> tick everything and click wipe.
Then flash latest TWRP (3.1.0-1) And try again flashing B596

XTutorials said:
Try to erase everything in twrp -->>advanced wipe-->> tick everything and click wipe.
Then flash latest TWRP (3.1.0-1) And try again flashing B596
Click to expand...
Click to collapse
ok done.
install zip
successful
but down i see
E:unknown command [errno]
dalvik wiped
now reboot
and....splash logo ok...reboot.......splash... again.. yes bootloop, but now seems normal
my initiative , i m going to hard resetnow
factory reset done
reboot
bootloop again my friend.
EDIT:
tried again, after 3 bootloop emui show to load but restart again. after that emui load and while the language selection it shutdown automatically, this time don't restart. we see tomorrow

Franseven said:
ok done.
install zip
successful
but down i see
E:unknown command [errno]
dalvik wiped
now reboot
and....splash logo ok...reboot.......splash... again.. yes bootloop, but now seems normal
my initiative , i m going to hard resetnow
factory reset done
reboot
bootloop again my friend.
EDIT:
tried again, after 3 bootloop emui show to load but restart again. after that emui load and while the language selection it shutdown automatically, this time don't restart. we see tomorrow
Click to expand...
Click to collapse
Oh my god.... that error is just a log, everything works, don't panic so again.
Go to twrp-- wipe-- advanced wipe-- tick(check) all and clikc wipe
reflash twrp 3.1.0-1,
flash again zip, and don't care about that error, that means it succesfully flashed the rom

XTutorials said:
Oh my god.... that error is just a log, everything works, don't panic so again.
Go to twrp-- wipe-- advanced wipe-- tick(check) all and clikc wipe
reflash twrp 3.1.0-1,
flash again zip, and don't care about that error, that means it succesfully flashed the rom
Click to expand...
Click to collapse
i've done what your saying, and the result is that when the device reach the boot logo starts a sort of timer, and after 10 seconds the os crash in every case with every firmware... thats not help

Franseven said:
i've done what your saying, and the result is that when the device reach the boot logo starts a sort of timer, and after 10 seconds the os crash in every case with every firmware... thats not help
Click to expand...
Click to collapse
Then I'm done... I don't know man other fixes. I've read os kinda same type of hard brick that if you disconnect the battery and plug it in back does something

XTutorials said:
Then I'm done... I don't know man other fixes. I've read os kinda same type of hard brick that if you disconnect the battery and plug it in back does something
Click to expand...
Click to collapse
in the p8 lite the battery is unremovible, i must try with deassemble tutorial?
but have you ear of this type of bootloop? with this strange timer crash?
EDIT:
i just followed a guide for battery sostitution, i've unplagged and replugged and the "timer boot loop/ os timer crash" continue.
now i m trying to unplug for 5 mins to do safe.
Ok done. same bad result.. please if you can't help, make this post still alive invite if you have expert friend, i'm going mad.

I think it's problem with the hardware, that the power button pressed continuously.
Because in our phone if you keep pressing it for 10 seconds it will force restart.
Actually I don't know about twrp flashing problem, if it also do the same or not...
you may check the power button..

salembream said:
I think it's problem with the hardware, that the power button pressed continuously.
Because in our phone if you keep pressing it for 10 seconds it will force restart.
Actually I don't know about twrp flashing problem, if it also do the same or not...
you may check the power button..
Click to expand...
Click to collapse
oh i thought that... i can try to dissassemble but i hope to not damage the device..
wait a minute... but when i click the power button i can hear sonor "clak" don't seems to be pressed costantly..
EDIT:
its definetely not a power button problem, i dissassembled, i replug the battery, so pressed power button, while booting i unplugged the contact of the power button and volume +- so i cant even seems pressed. same happened after 10 seconds it restart. sorry bad english

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

LG G3 D850 Flashtool 94% fail issue

Hello,
I have an LG G3 D850
it was in Factory reset 2 status when it came to me and started the mess.
I googled and Explored XDA for the solutions and they were pretty straightforward, I followed the guides that were there to use TOT files and LG flash tools to make it work. I followed every step and at 94% my mobile restated and started boot looping. I waited a bit to make sure that I was not messing thing up in panic but nothing. it was persistently giving me different errors at 94%, sometimes "mini os boot fail" and sometimes fail to open USB port
after that, I explored more and found some KDZ methods but nothing...
is there anyone who can help me to restore the phone and make it a healthy phone again.
:crying:

nauman ahmed said:
Hello,
I have an LG G3 D850
it was in Factory reset 2 status when it came to me and started the mess.
I googled and Explored XDA for the solutions and they were pretty straightforward, I followed the guides that were there to use TOT files and LG flash tools to make it work. I followed every step and at 94% my mobile restated and started boot looping. I waited a bit to make sure that I was not messing thing up in panic but nothing. it was persistently giving me different errors at 94%, sometimes "mini os boot fail" and sometimes fail to open USB port
after that, I explored more and found some KDZ methods but nothing...
is there anyone who can help me to restore the phone and make it a healthy phone again.
:crying:
Click to expand...
Click to collapse
First and foremost anything after 85% it’s done flashing. It will almost always fail after that it’s NORMAL as I’ve stated in the back to stock guide here. So it “failing” at 94% is completely normal.
Did you flash it choose the board_dl option? On the screen you choose the tot file?
Also I hope you didn’t try the kdz method.. there are no kdz files for the D850 if you tried flashing you tried flashing a wrong model which can perm brick your device.
If you tried flashing choose the board_dl option and there is still bootloop is could be possible that it has a bad battery which will cause the G3 to bootloop
Sent from my iPhone using Tapatalk

hyelton said:
First and foremost anything after 85% it’s done flashing. It will almost always fail after that it’s NORMAL as I’ve stated in the back to stock guide here. So it “failing” at 94% is completely normal.
Did you flash it choose the board_dl option? On the screen you choose the tot file?
Also I hope you didn’t try the kdz method.. there are no kdz files for the D850 if you tried flashing you tried flashing a wrong model which can perm brick your device.
If you tried flashing choose the board_dl option and there is still bootloop is could be possible that it has a bad battery which will cause the G3 to bootloop
Sent from my iPhone using Tapatalk
Click to expand...
Click to collapse
to my bad luck, I did try flashing KDZ but it is still boot looping means its good to go and es I have flashed choosing the option you mentioned but after boot loop I tries to go into Factory reset screen and then again into bootloop let me give it a try with new battery and yes I was hoping that you would come to help. and thanks a bunch

nauman ahmed said:
to my bad luck, I did try flashing KDZ but it is still boot looping means its good to go and es I have flashed choosing the option you mentioned but after boot loop I tries to go into Factory reset screen and then again into bootloop let me give it a try with new battery and yes I was hoping that you would come to help. and thanks a bunch
Click to expand...
Click to collapse
is it not even going to get into Factory reset mood?

nauman ahmed said:
to my bad luck, I did try flashing KDZ but it is still boot looping means its good to go and es I have flashed choosing the option you mentioned but after boot loop I tries to go into Factory reset screen and then again into bootloop let me give it a try with new battery and yes I was hoping that you would come to help. and thanks a bunch
Click to expand...
Click to collapse
What KDZ did you flash? That could of perm destroyed the phone if the flash went through.
Next step would be a battery if boot loop continues after choosing board_dl