Stuck in fastboot after rom install? 49% on LG Tool? Fixed! - G2 Q&A, Help & Troubleshooting

Ok guys, recently I bricked my G2 after installing PA 4.0 for my vs980. This issue could and probably is on my part but here is how to get out of it:
Stuck on fastboot turn off device (all the way, hold power button down for 5-10 seconds) and then hold down POWER+VOLUME DOWN and when you see the LG screen let go and then hold down POWER+VOLUME DOWN again. This should bring you to reset mode where you follow the prompts and reset device. This will boot you back into recovery! I had a backup and installed that but if you do not try pushing alternative rom to device using fastboot?...idk never tried and didn't need to. Good luck and hopefully I am the only one with this problem or if not hope this helped
Press thanks if this helped!
Links (resources I used):
http://forum.xda-developers.com/showthread.php?t=2477595 If your download mode is broken for whatever reason
http://www.lg-phones.org/how-to-flash-unbrick-lg-g2-back-to-stock.html Un-brick method that I used. Got stuck at 49% every try.
Any questions just ask. Happy to help
Thank you +dylan heyl for my post comment on G+!!!

ME TOO Iam very sad

THANKS!!!!
Finally!!!!! Your method worked!!!!!! I was starting to give up.

femotely said:
Finally!!!!! Your method worked!!!!!! I was starting to give up.
Click to expand...
Click to collapse
tell us what you did!
my phone is working but i want to get back to original and it get stucked on 49% when i flash the kdz.

rafaelsartori said:
tell us what you did!
my phone is working but i want to get back to original and it get stucked on 49% when i flash the kdz.
Click to expand...
Click to collapse
I was able to get back into recovery, and just restored from an earlier backup, after that I stopped trying the FlashTool, my backup was from a few hours ago, sorry I couldn't help further.

ohh ****, i could use that, but my backup was messed up. its on the directory but i get error when try to restore it.
im ok using PA 4.4, but i really want to get back to stock. its not a death case, but i want it.

finally manage to fix this sh*t.
if you stucked like i was for 5 days, you can try this
http://forum.xda-developers.com/showpost.php?p=48266517&postcount=1046

The solution for me was very simple. I just install other custom rom 4.3 and i pass the 49% error.

rokko74 said:
The solution for me was very simple. I just install other custom rom 4.3 and i pass the 49% error.
Click to expand...
Click to collapse
For me it was the same...Stuck at 49% but flash an other custom ROM (CM 11) and done the process for flash stock rom again, I passed the 49% error too,
Thanks for the tips.

I couldn't go to anywhere expect fastboot mode. In addition, I got an error when I tried to install CM12, the partition couldn't be found.

Related

[Q] Please HELP!!! L7-P705 keeps rebooting after unlocking bootloader

Someone please help!
I have a LG Optimus L7 P705g, on v10C stock rom, rooted according to http://forum.xda-developers.com/showthread.php?t=1906133
Then I tried to unlock bootloader and install cwm recovery following http://forum.xda-developers.com/showthread.php?t=1664322
I tried both v1 and v2 of the L7CWM archive. But the phone keeps rebooting about 2 minutes after power on.
No matter I boot normally, or boot into cwm recovery, it still restarts about 2 minutes in.
It's driving me crazy. Can somebody give me some pointer in how to resolve this constant reboot situation?
I believe I followed all the instructions provided with the above threads, and tried flashing both v1 and v2 a few times.
Thanks in advance!
ecapella said:
Someone please help!
I have a LG Optimus L7 P705g, on v10C stock rom, rooted according to http://forum.xda-developers.com/showthread.php?t=1906133
Then I tried to unlock bootloader and install cwm recovery following http://forum.xda-developers.com/showthread.php?t=1664322
I tried both v1 and v2 of the L7CWM archive. But the phone keeps rebooting about 2 minutes after power on.
No matter I boot normally, or boot into cwm recovery, it still restarts about 2 minutes in.
It's driving me crazy. Can somebody give me some pointer in how to resolve this constant reboot situation?
I believe I followed all the instructions provided with the above threads, and tried flashing both v1 and v2 a few times.
Thanks in advance!
Click to expand...
Click to collapse
ok, you need to do this.
First, follow this tutorial http://forum.xda-developers.com/showpost.php?p=31828740&postcount=1191 to flash the ROM from this post http://forum.xda-developers.com/showthread.php?t=2176430 this rom is already rooted, and includes CWM and unlocked bootloader, so you shouldn't have any problems to flash any other ROM after that one.
and second, you need to learn to search on the forum, and read more before asking already solved issues.
good luck
vashminted said:
ok, you need to do this.
First, follow this tutorial http://forum.xda-developers.com/showpost.php?p=31828740&postcount=1191 to flash the ROM from this post http://forum.xda-developers.com/showthread.php?t=2176430 this rom is already rooted, and includes CWM and unlocked bootloader, so you shouldn't have any problems to flash any other ROM after that one.
and second, you need to learn to search on the forum, and read more before asking already solved issues.
good luck
Click to expand...
Click to collapse
Thanks for your quick reply! Actually, I'm a little hesitant to use kdz updater, as I've read some posts saying that even after they flash the stock kdz, the phone was in an even worse situation.
Since I can still boot into cwm recovery (I have a 2-minute time frame before the phone restarts itself), should I do a wipe cache or something? Will it help?
Flashing the whole thing is my last resort.
ecapella said:
Thanks for your quick reply! Actually, I'm a little hesitant to use kdz updater, as I've read some posts saying that even after they flash the stock kdz, the phone was in an even worse situation.
Since I can still boot into cwm recovery (I have a 2-minute time frame before the phone restarts itself), should I do a wipe cache or something? Will it help?
Flashing the whole thing is my last resort.
Click to expand...
Click to collapse
yes, I've also read that some people have problems after flashin kdz....but i dont know why, KDZ flashing is usually the best way to make sure your phone is back to a "perfect" working state, since it restores everything to the way it should be, and in most situations is the only way to unbrick the phone.
I can't tell you how many times I had to use KDZ updater to restore my phone after messing with it, im not a developer but i do a lot of experiments with my phone trying to make it work better, and most of the times it end totally bricked, and every time KDZ updater saves my ass. Some time ago i was trying to modify the stock rom myself, and I used to flash via KDZ my phone at least twice a day....so for me is pretty safe to use
vashminted said:
yes, I've also read that some people have problems after flashin kdz....but i dont know why, KDZ flashing is usually the best way to make sure your phone is back to a "perfect" working state, since it restores everything to the way it should be, and in most situations is the only way to unbrick the phone.
I can't tell you how many times I had to use KDZ updater to restore my phone after messing with it, im not a developer but i do a lot of experiments with my phone trying to make it work better, and most of the times it end totally bricked, and every time KDZ updater saves my ass. Some time ago i was trying to modify the stock rom myself, and I used to flash via KDZ my phone at least twice a day....so for me is pretty safe to use
Click to expand...
Click to collapse
I tried to read as many posts as possible about using the L7CWM archive to unlock bootloader and CWM recovery before actually doing it. People with P700 and P705 both reported success. I don't know what I did wrong. I am so frustrated...
The ROM you pointed me to get is for P700, does it matter? (Mine is P705). Or should I use my stock rom kdz to test it out first?
Also the two links that you gave me have different phone mode setting in the KDZ updater, one set as EMERGENCY, the other one set as DIAG. Which one should I use?
Thanks again!
Hope there is an easier way than using the KDZ updater... :fingers-crossed:
ecapella said:
I tried to read as many posts as possible about using the L7CWM archive to unlock bootloader and CWM recovery before actually doing it. People with P700 and P705 both reported success. I don't know what I did wrong. I am so frustrated...
The ROM you pointed me to get is for P700, does it matter? (Mine is P705). Or should I use my stock rom kdz to test it out first?
Also the two links that you gave me have different phone mode setting in the KDZ updater, one set as EMERGENCY, the other one set as DIAG. Which one should I use?
Thanks again!
Hope there is an easier way than using the KDZ updater... :fingers-crossed:
Click to expand...
Click to collapse
yep, it's for P700, but other than NFC, there's no difference...i dont recomend to use that rom for every day because it will drain your battery because of the NFC. but since it comes already rooted and unlocked, its an excelent base to make sure everything is well installed, after that you should be able to enter into recovery without problems, and then you can flash a ROM for P705. Personally I suggest you to try this one http://forum.xda-developers.com/showthread.php?t=2472479 it's working very good for me, and have specific kernel to p705
Of course you can try with stock kdz for p705, but hen you will have to repeat the process with L7CWM and chances are that something goes wrong again.
And I gave you the link that use EMERGENCY because it is the way I use to flash a KDZ, you can try to follow tutorial with DIAG option, but I haven't test it myself, and I would never recommend something I haven't tested before. Also because you said your phone reboots every two minutes, and I think DIAG option needs the phone to be ON while flashing, in EMERGENCY option, the phone will never turn off untill you unplug the cable.
vashminted said:
yep, it's for P700, but other than NFC, there's no difference...i dont recomend to use that rom for every day because it will drain your battery because of the NFC. but since it comes already rooted and unlocked, its an excelent base to make sure everything is well installed, after that you should be able to enter into recovery without problems, and then you can flash a ROM for P705. Personally I suggest you to try this one http://forum.xda-developers.com/showthread.php?t=2472479 it's working very good for me, and have specific kernel to p705
Of course you can try with stock kdz for p705, but hen you will have to repeat the process with L7CWM and chances are that something goes wrong again.
And I gave you the link that use EMERGENCY because it is the way I use to flash a KDZ, you can try to follow tutorial with DIAG option, but I haven't test it myself, and I would never recommend something I haven't tested before. Also because you said your phone reboots every two minutes, and I think DIAG option needs the phone to be ON while flashing, in EMERGENCY option, the phone will never turn off untill you unplug the cable.
Click to expand...
Click to collapse
I read another post about flashing the Homero's v10K rooted KDZ that you mentioned into a North American P705, and that made the phone unbootable.
But fortunately, I managed to get a stock bootloader from a friend's North American P705 and push it into my phone. This did the trick, my phone didn't have the boot loop anymore.
Then, I upgraded the stock firmware to v20A via LG's mobile support tool. At this version (JB as opposed to ICS), I tried to push the cracked bootloader into the phone again. This time, everything was all right, no boot loop! So I flashed the CWM recovery, and everything was good.
I just tested out Szymel's modded stock rom v20E with OC 1305Mhz, seems pretty good!
Now I have a lot of ROM choices to test out. :laugh:
Anyway, thanks so much for your help and suggestions!
HELP
ecapella said:
I read another post about flashing the Homero's v10K rooted KDZ that you mentioned into a North American P705, and that made the phone unbootable.
But fortunately, I managed to get a stock bootloader from a friend's North American P705 and push it into my phone. This did the trick, my phone didn't have the boot loop anymore.
Then, I upgraded the stock firmware to v20A via LG's mobile support tool. At this version (JB as opposed to ICS), I tried to push the cracked bootloader into the phone again. This time, everything was all right, no boot loop! So I flashed the CWM recovery, and everything was good.
I just tested out Szymel's modded stock rom v20E with OC 1305Mhz, seems pretty good!
Now I have a lot of ROM choices to test out. :laugh:
Anyway, thanks so much for your help and suggestions!
Click to expand...
Click to collapse
i have the same problem with my l7 p705 i rooted it and then i installed CWM and then it started restarting every 2 minutes. so i thought maybe unrooting it would help but it didn't. please give me all the steps that you did so i can stop my phone from booting every 2 minutes.!!!
LG P705
My Phones says secure booting error Cause:boot certification verify i`m a newbie help me please ,
Lg Optimus L7 P705 Secure booting Error!
Hello everyone,
I'm from Turkey.
I have LG Optimus L7 P705.
My problem, to take root and Cyanogenmod. But phone is brick.
I have seen the error screen :
-Secure booting Error!
-Cause : boot certification verify
Help me !
Mail Adress 7/24 : [email protected]

Secure Boot Error F320S!

Hello! I have a problem which I don't know how to fix, so I need some help! I'm running stock android 4.4 (20a) and have flashed CWM through Flashify, but every time I try to boot into recovery, I get this message:
"Secure booting error
Error: Boot Certification Verify!"
Recovery worked in android 4.2 (11g), but I messed my phone up, and flashed the latest .kdz-file for my phone. It was after that the recovery-problem appeard.
I've read some places about people with D802 who has this problem, but the fixes they've got only works for D802 and D800. So, how can I fix my F320S? I guess there are more people with the korean version who has stumbled upon this problem, so if you got a fix, please post it!
Excuse my typos if there are any!
Thank you!
LG G2 F320S
Put phone in download mode, and flash the stock KDZ.
If you cannot do this, then you are hard bricked. I had an LG Optimus G which I got a Secure Boot Error after flashing a compatible ROM using TWRP, and although it could get into download mode, it would never be seen as a COM Port in the computer again to it couldn't be seen by the Flash Tools software to restore KDZ.
But it is a stock image I've flashed... What causes the problem!?
Edit: I tried to put it in Download-mode, but the secure-boot error apeard there too... But the phone can't be bricked, as it's booting to Android and everything works...
Would this fix it if the developer made a version based on my aboot?
http://forum.xda-developers.com/showthread.php?t=2500441
Edit no.2: I pressed the wrong button-combination, so yes, I was able to access Download-mode, and it works like a charm!
Send with my LG G2 F320S!
Secure Boot Error D802
2minuutes said:
But it is a stock image I've flashed... What causes the problem!?
Edit: I tried to put it in Download-mode, but the secure-boot error apeard there too... But the phone can't be bricked, as it's booting to Android and everything works...
Would this fix it if the developer made a version based on my aboot?
http://forum.xda-developers.com/showthread.php?t=2500441
Edit no.2: I pressed the wrong button-combination, so yes, I was able to access Download-mode, and it works like a charm!
Send with my LG G2 F320S!
Click to expand...
Click to collapse
Did you ever fix this, and how? I just stumbled on to the same problem the same way. I've got a D802 international. Recovery is corrupted with the same error as yours. That was nonsense about being bricked above. I hate that when people give wrong info. Any help definitely appreciated.
notanymore said:
Did you ever fix this, and how? I just stumbled on to the same problem the same way. I've got a D802 international. Recovery is corrupted with the same error as yours. That was nonsense about being bricked above. I hate that when people give wrong info. Any help definitely appreciated.
Click to expand...
Click to collapse
I did not, but I've read a place where devs managed to roll back just the bootloader and in that way access recovery!
Secure Boot Error D802
2minuutes said:
I did not, but I've read a place where devs managed to roll back just the bootloader and in that way access recovery!
Click to expand...
Click to collapse
I'm wondering what happens if I do a factory reset? Trying to get up the nerve to do it. If not then I think the next best option is to wait for 4.4.3 or higher.
notanymore said:
I'm wondering what happens if I do a factory reset? Trying to get up the nerve to do it. If not then I think the next best option is to wait for 4.4.3 or higher.
Click to expand...
Click to collapse
I don't think a reset will fix it as it's not fixing any corrupt data. The problem lays in the bootloader. It's not able to boot into the recovery installed as if it was an earlier build. It looks like this is what you are looking for to be able to install a recovery the right way. I haven't tried it yet, tho.
Secure Boot Error D802
2minuutes said:
I don't think a reset will fix it as it's not fixing any corrupt data. The problem lays in the bootloader. It's not able to boot into the recovery installed as if it was an earlier build. It looks like this is what you are looking for to be able to install a recovery the right way. I haven't tried it yet, tho.
Click to expand...
Click to collapse
Ok thanks!
Secure Boot Error D802
2minuutes said:
I don't think a reset will fix it as it's not fixing any corrupt data. The problem lays in the bootloader. It's not able to boot into the recovery installed as if it was an earlier build. It looks like this is what you are looking for to be able to install a recovery the right way. I haven't tried it yet, tho.
Click to expand...
Click to collapse
It worked! I took the plunge and it worked immediately. I've got TWRP. I already had root so did not have to use the iroot. I just ran the autorec.apk and problem solved.
Dear sir
My lg f320L and in this phone i have cloudyG2_3.3 version
i wana flash my phone F320L30D
when i flashd 2 % it stop
i have security error in my phole
please HELP
sorry my english poor

[Q] LG G2 bricked and can't flash stock firmware!

So I'm really into Android developing, I'm always flashing and installing etc, but I got a problem now.
Phone information​
LG G2 D802
Rooted
TWRP Recovery 2.7.0.0
Was running 4.4.2, found a kdz file on the internet and flashed it (no regular update from my phone)
What happened​I actually did something stupid, I received an application update from the LG Download Center (or whatever it's called) on my phone and clicked on it. I was planning on flashing Android 4.4.2 again because my firmware was not stable, and I thought this update could help me.
But no, after it finished downloading, I automatically booted into recovery.
What I did​So I tried to reboot and enter my OS, but unfortunately, I was stuck in recovery.
I did everything I could, wiping (Dalvik) cache, factory reset, flashed a new rom, restored Nandroid backup, but no, every time I booted, I got back into recovery again.
I only saw 1 option left, booting into download mode and flashing a new firmware.
I found the Netherlands 16GB kdz file for Android 4.4.2 (because I had a French one first), the one I was looking for.
Looked all over the internet, and all guides pointed me to this guide.
Tried it, but I got multiple errors, one of them was that my phone was not connected while I was at 15% of the flash process.
What happened​After that first flashing process, I booted up, but got a Security Error. After the Security Error was showing for 5 seconds, my phone shut down. This is happening every time I try to boot up.
I couldn't access my recovery anymore, nothing. Edit: I can access my recovery right now, and I tried this, but when I boot up I get the Security Error again.
The big problem right now is the Security Error! How do I bypass that?
So can someone please help me out!
Several phones/tablets of mine bricked and I always found a way to get out of it, but not this time, unfortunately...
Have you tried this
Sent from LG-G2 D800 on AEONFLEX 4.4.2
XxZombiePikachu said:
Have you tried this
Sent from LG-G2 D800 on AEONFLEX 4.4.2
Click to expand...
Click to collapse
Yes, I actually have. Didn't mention it, but after I did that I booted and got an LG logo and below it was a text that said 'Security Error' After like 5 seconds the security error goes away and my phone shuts down. I can only enter download mode right now.
I'll edit my first post with this info.
Thanks for the help though!
Edit: I find a way to access my recovery again because at first I couldn't but I figured out that the code in the thread you linked was a bit different than the code I entered at first.
So I used the code you gave me, but now I get the Security Error again!
Hi mate, just like you i downloaded that damn OTA today and messed up my phone, but in my case was because i had totally forgotten it was rooted and had custom recovery installed :silly::silly::silly::silly:
I followed this tutorial to fix the boot secure error http://forum.xda-developers.com/showthread.php?t=2582142 and it worked like a charm except for download mode wasn't working at all.
After doing some research i found this post http://forums.androidcentral.com/ge...ricked-lg-g2-stuck-twrp-no-download-mode.html and got download mode (apparently) working again but Windows didn't recognize it at all so i couldn't use it to flash the .kdz stock firmware.
In the end i just flashed a custom aosp rom and got my phone back to life but the download mode issue it's still there and it's bothering me quite a lot.
Any suggestion is welcome.
EDIT: Don't download the recovery from the post, instead look for the latest version (2.7.0.0) because the one posted there (2.6.3.2) might corrupt your partitions
evilruck said:
Hi mate, just like you i downloaded that damn OTA today and messed up my phone, but in my case was because i had totally forgotten it was rooted and had custom recovery installed :silly::silly::silly::silly:
I followed this tutorial to fix the boot secure error http://forum.xda-developers.com/showthread.php?t=2582142 and it worked like a charm except for download mode wasn't working at all.
After doing some research i found this post http://forums.androidcentral.com/ge...ricked-lg-g2-stuck-twrp-no-download-mode.html and got download mode (apparently) working again but Windows didn't recognize it at all so i couldn't use it to flash the .kdz stock firmware.
In the end i just flashed a custom aosp rom and got my phone back to life but the download mode issue it's still there and it's bothering me quite a lot.
Any suggestion is welcome.
EDIT: Don't download the recovery from the post, instead look for the latest version (2.7.0.0) because the one posted there (2.6.3.2) might corrupt your partitions
Click to expand...
Click to collapse
Thanks! But does my internal storage get whiped? Will all my pictures etc. be gone?
And the first thred removes the security error right? And after that I can just boot into recovery mode (I can boot in recovery btw) and flash a new rom? Just wanted to know this so I don't go through all that trouble for nothing
Edit: You know I can enter both download and recovery mode right?
Ibrahim9999 said:
Thanks! But does my internal storage get whiped? Will all my pictures etc. be gone?
And the first thred removes the security error right? And after that I can just boot into recovery mode (I can boot in recovery btw) and flash a new rom? Just wanted to know this so I don't go through all that trouble for nothing
Edit: You know I can enter both download and recovery mode right?
Click to expand...
Click to collapse
Nope internal SD remains intact, basically what you'll be doing is pushing the right files into the system partitions and yes, in theory you should be able to flash a new rom.
Even if you can boot into recovery you should do it if you're getting that error, and after that you can just push a ROM file to flash (i'll assume you know how to do it) and btw let me know if you decide to flash a stock based rom instead of an aosp like i did.
Good luck with that :good:
evilruck said:
Nope internal SD remains intact, basically what you'll be doing is pushing the right files into the system partitions and yes, in theory you should be able to flash a new rom.
Even if you can boot into recovery you should do it if you're getting that error, and after that you can just push a ROM file to flash (i'll assume you know how to do it) and btw let me know if you decide to flash a stock based rom instead of an aosp like i did.
Good luck with that :good:
Click to expand...
Click to collapse
Thanks man! I'm probably going to save money because of you, awesome!
Ibrahim9999 said:
Thanks man! I'm probably going to save money because of you, awesome!
Click to expand...
Click to collapse
I hope so!
Let me know if you fix the thing :laugh:
evilruck said:
I hope so!
Let me know if you fix the thing :laugh:
Click to expand...
Click to collapse
I just managed to fix it! Thank you so much man!
Can someone help me plz I got flashily got CWM instead of the TWRP and got and lg update it updated and now it's stuck in recovery mode it won't go into download mode it only goes to recovery mode and my computer won't recognize my phone so if any one knows how to fix it can you plz help me out
my pc don't recognize the lg g2 in download mode!
i installed the drivers and the USB is connected but the pc don;t even say that the device is connected . and nothing in device manager at all
Perhaps you might consider sending it in to lg if you still have warranty. But I'd you don't, there are services on eBay/ Craigslist that can help you.
Sent from my LG-D800 using XDA Free mobile app

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.

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

Categories

Resources