Develop Bugs

Secure Booting Error! Cause: boot certification verify

Hello all,
LG Optimus G Pro user here (LG-F240S). I recently rooted my phone, then used Gomdol's tool, which roots the phone and installs CWM recovery at the same time. I had initially thought that the application also unlocks the bootloader, but since then found out it doesn't.
Anyways, the first time rebooted into recovery, I flashed a ROM (specifically for F240S), which wasn't successful for some reason. Now, when I boot up the phone, it keeps saying "Secure Booting Error! Cause: boot certification verify"
I have tried everything, from the Volume down + Power + Home to erase everything and do the factory reset, but it doesn't work. I have also downloaded the stock firmware, and tried the KDZ_FW_UPD application to flash the stock firmware, which also did not work (Extract File Error). My last resort was using LGMobile Support Tool, but it keeps telling me to recharge my battery (my batter is currently recharged to 100%, and the USB is plugged in, so something is very wrong here).
I would really appreciate any help, It's been 3 days now without being able to use my phone and it sucks
Thanks!
J

Might wanna try this
ca12bon said:
Hello all,
LG Optimus G Pro user here (LG-F240S). I recently rooted my phone, then used Gomdol's tool, which roots the phone and installs CWM recovery at the same time. I had initially thought that the application also unlocks the bootloader, but since then found out it doesn't.
Anyways, the first time rebooted into recovery, I flashed a ROM (specifically for F240S), which wasn't successful for some reason. Now, when I boot up the phone, it keeps saying "Secure Booting Error! Cause: boot certification verify"
I have tried everything, from the Volume down + Power + Home to erase everything and do the factory reset, but it doesn't work. I have also downloaded the stock firmware, and tried the KDZ_FW_UPD application to flash the stock firmware, which also did not work (Extract File Error). My last resort was using LGMobile Support Tool, but it keeps telling me to recharge my battery (my batter is currently recharged to 100%, and the USB is plugged in, so something is very wrong here).
I would really appreciate any help, It's been 3 days now without being able to use my phone and it sucks
Thanks!
J
Click to expand...
Click to collapse
Hey mine did this i used the instruction in the thread below but i had the e980 so you might have to get your stock files but worth a try?
http://forum.xda-developers.com/showthread.php?t=2302660

Simply follow this method
http://forum.xda-developers.com/showthread.php?t=2396048

Hey man, I'm in the same boat, but I have the E988. What did you end up doing?

any idea?????
tase25 said:
Hey man, I'm in the same boat, but I have the E988. What did you end up doing?
Click to expand...
Click to collapse
i have the same problem here!! E975 when i dot the classic staff for custom rom i go to recovery i i see this in to my phone....boot certification verify
stock rom 4.4.2kk....what i mast do guys plz help

ca12bon said:
Hello all,
LG Optimus G Pro user here (LG-F240S). I recently rooted my phone, then used Gomdol's tool, which roots the phone and installs CWM recovery at the same time. I had initially thought that the application also unlocks the bootloader, but since then found out it doesn't.
Anyways, the first time rebooted into recovery, I flashed a ROM (specifically for F240S), which wasn't successful for some reason. Now, when I boot up the phone, it keeps saying "Secure Booting Error! Cause: boot certification verify"
I have tried everything, from the Volume down + Power + Home to erase everything and do the factory reset, but it doesn't work. I have also downloaded the stock firmware, and tried the KDZ_FW_UPD application to flash the stock firmware, which also did not work (Extract File Error). My last resort was using LGMobile Support Tool, but it keeps telling me to recharge my battery (my batter is currently recharged to 100%, and the USB is plugged in, so something is very wrong here).
F240S user here bro. I feel you
I would really appreciate any help, It's been 3 days now without being able to use my phone and it sucks
Thanks!
J
Click to expand...
Click to collapse
on your boot certification problem, I had that same problem before and made me panic for two days. I tried LG mobile support tool and worked for the first time. few weeks ago, I also encountered the same error on LG Mobile support tool (battery error,right?) I used I also used the KDZ_FW_UPD application and yes, extract error. but you know what the magical thing is? I found the G2 KDZ flasher from the G2 thread..
even if this was from G2 thread, it worked for my device.
here is the link and of course thanks to @hyelton for bringing this wonderful fix. now, I don't have to worry about bricking my phone again(except for hard bricking, of course).
http://forum.xda-developers.com/showthread.php?t=2432476
one more thing: make sure you download the KDZ. there is a thread here that links to that. but I think you have the right kdz now so just follow the steps. make sure you are in download mode press volume up and down (only the volume up and down. not the home or power) and then plug the cord.

guys, this happens when installing custom rom with lg stock rom in it and your device is not fully unlock. to lessen the hassle of worrying trying to reflash to the stock rom and downloading those huge files..just download any custom pure android rom , slimkat, cm11, etc then flash to your recovery..it would boot again without that error on boot certification. only that your on pure android rom but that's ok

nuvkyl20 said:
guys, this happens when installing custom rom with lg stock rom in it and your device is not fully unlock. to lessen the hassle of worrying trying to reflash to the stock rom and downloading those huge files..just download any custom pure android rom , slimkat, cm11, etc then flash to your recovery..it would boot again without that error on boot certification. only that your on pure android rom but that's ok
Click to expand...
Click to collapse
How do i flash the rom when i cant get into recovery? I have the same issue om my rooted g pad whit stockrom. I want to flash cyagenmod.

HELP PLEASE! My Lg G Pro e988 stays forever on this "Secure booting error! Cause: boot certification verify! Can't get in download mode. I have tryed all sort of combination keys but everytime this error pops up. My phone was on stock rom, then an official update started to download and ask me to reboot. After reboot this error!
HELP!

You should be able to get in download mode by following these steps. First take out the battery for atleast 5seconds, put it back in, then press and hold both vol + and vol - and within 2seconds plug in the usb cable, your computer should make the sound of a new device connected, when you hear that let go of the volume keys. The screen should say download mode now.
Sent from my LG-E980 using XDA Free mobile app

ivoh95 said:
You should be able to get in download mode by following these steps. First take out the battery for atleast 5seconds, put it back in, then press and hold both vol + and vol - and within 2seconds plug in the usb cable, your computer should make the sound of a new device connected, when you hear that let go of the volume keys. The screen should say download mode now.
Sent from my LG-E980 using XDA Free mobile app
Click to expand...
Click to collapse
It doesn't work! I did exactly what you say. No sound on pc, just that error on phone screen and no download mode
What should I do?
Thanks

Try booting into recovery, hold power and vol -. Or try power and vol +
Sent from my LG-E980 using XDA Free mobile app

ivoh95 said:
Try booting into recovery, hold power and vol -. Or try power and vol +
Sent from my LG-E980 using XDA Free mobile app
Click to expand...
Click to collapse
I have sent it to warranty and they told me that the phone was rooted, they sent me a picture with the back of the phone showing the imei and serial number and a front picture showing me that the phone has the app SuperSu.
They told me that the phone need a new motherboard that cost ~340 $.
Why do they need a new motherboard ? because the phone was not hard bricked.
I will get my device back.
Is possible to get it back with some modifications? I mean if they managed to boot it and see the SuperSu app.
I know to work with LG Flash Tool, so all I need is to put it to download mode.
All the above key combination didn't work. Power and vol- or power and vol+ ......
I will contact you again when i'll have my device.
Thanks!

yackmaan said:
I have sent it to warranty and they told me that the phone was rooted, they sent me a picture with the back of the phone showing the imei and serial number and a front picture showing me that the phone has the app SuperSu.
They told me that the phone need a new motherboard that cost ~340 $.
Why do they need a new motherboard ? because the phone was not hard bricked.
I will get my device back.
Is possible to get it back with some modifications? I mean if they managed to boot it and see the SuperSu app.
I know to work with LG Flash Tool, so all I need is to put it to download mode.
All the above key combination didn't work. Power and vol- or power and vol+ ......
I will contact you again when i'll have my device.
Thanks!
Click to expand...
Click to collapse
Any updates?

Long story with guys at warranty. I asked them to prove that the phone in those pictures is mine. From the picture showing my imei, yes is mine. But from the picture showing supersu app....they don't convince me. Every phone could have installed supersu app without being rooted. So i asked them to provide me another picture that will show the google account that was registered on phone and another with all my apps installed. They didn't send me such photos.
If they managed to revive my device and showing me there is a supersu app, that means they don't need to change the motherboard.
Am i right?
So i get my phone back working and they cut my warranty.
I tried vol+ and vol- and usb cable and download mode appeared.
Thankd!

yackmaan said:
Long story with guys at warranty. I asked them to prove that the phone in those pictures is mine. From the picture showing my imei, yes is mine. But from the picture showing supersu app....they don't convince me. Every phone could have installed supersu app without being rooted. So i asked them to provide me another picture that will show the google account that was registered on phone and another with all my apps installed. They didn't send me such photos.
If they managed to revive my device and showing me there is a supersu app, that means they don't need to change the motherboard.
Am i right?
So i get my phone back working and they cut my warranty.
I tried vol+ and vol- and usb cable and download mode appeared.
Thankd!
Click to expand...
Click to collapse
I smell something weird about LG. They probably put SuperSU on there or they got the wrong phone. Anyway i'm sure the community will help Don't lose faith/hope yet

About the warranty, its very complicated.
The store from which the phone was buyed, took it and send it to another warranty dealer authorized by LG, i guess, which was not named LG.
At last, I sold the phone, i own an lg g2 now and recently flash official lollipop.

Gladly and after some fails and always getting the secure boot certification error, i managed to access the download mode and with LG Flash Tool installed the stock .kdz on my LG L90 D405n.. thx for all the hints..

Before of this secure boot my e988 was working but no download mode. I've encountered this on a LG G2, so after some search i've found out that I must downgrade the bootloader. So, I rooted my device and installed autorec.apk from here http://forum.xda-developers.com/showthread.php?t=2715496 that fixes the " no download mode " .
I don't know how to skip the secure boot error. If someone managed please share with us!

Boot : Error Certification Verify
Hi. I am new to this thread although i had used this thread many times with issues i have had. There is this one issue im having that i can't seem to figure out which im usually good at doing by following forums or threads.
A couple weeks ago i had rooted my LG G Pad 7.0 V410 LTE tablet from AT&T. I had TWRP downloaded into it and i had flashed Candy5 it worked perfectly i just didn't like how it looked so i tryed to flash it back to original stock OS. But now when i boot my tablet up it goes to the LG screen and at the top left it says Boot : Error Certification Error. This has me dumbfounded on what i should do. when i connect the tablet to the computer nothing pops up no tablet connects to the computer. I tryed downloading the drivers and everything but nothing seemed to work. I need help with this issue please!!
I didn't know where else to post this issue due to being new!!!

Stuck in Boot loop after weeks of normal usage

Hi.
I have a problem with my D855. My phone is rooted and runs the fulmics ROM. Everything was working fine, , on Fulmics 5.3, except than one day, I was using my phone normally and then it crashed. I saw the phone rebooting, but for some reason it got stuck. The phone tried to boot unsuccessfully until the "firmware update" went through, after what it reboots again (unsuccessfully) and so on.
At that time, I was able to access twrp, do some backup, and flash properly with a downgraded version of fulmics (from 5.3 to 4.1).
It was able to boot again and use my phone like before. Yet, after one month of usage, the same problem happened on version 4.1. The phone crashed and now cannot boot.
Any idea of where it is coming from? Should I go back to stock? Should I contact customer service?

What did you do before the phone crashes ?
I think you probably should flash the stock ROM and wait for an other crash... or not.

Jb-kun said:
What did you do before the phone crashes ?
I think you probably should flash the stock ROM and wait for an other crash... or not.
Click to expand...
Click to collapse
I haven't done anything special. I think that the first time I was playing on candy crush. The second time I was just looking at pictures in my gallery.
I was using the ROM without any tweaks or extra modules such as Xposed. Just regular use.
Update on my situation: I switched back to stock ROM and it seems to work OK for now (it has been 4 days). So I will wait and see if new problems happen. By the way, it was extremely difficult for me to get back to Stock directly from fulmics ROM. I tried several methods that I have found on xda based on LGUP or LG Flash tool without success. For some reason I was not able to connect the phone to my PC in download mode.
The only way that I found was to use a nandroid backup that I did just after rooting the phone and that was based on stock ROM.

shewshain said:
I haven't done anything special. I think that the first time I was playing on candy crush. The second time I was just looking at pictures in my gallery.
I was using the ROM without any tweaks or extra modules such as Xposed. Just regular use.
Update on my situation: I switched back to stock ROM and it seems to work OK for now (it has been 4 days). So I will wait and see if new problems happen. By the way, it was extremely difficult for me to get back to Stock directly from fulmics ROM. I tried several methods that I have found on xda based on LGUP or LG Flash tool without success. For some reason I was not able to connect the phone to my PC in download mode.
The only way that I found was to use a nandroid backup that I did just after rooting the phone and that was based on stock ROM.
Click to expand...
Click to collapse
You can also use the Stock rom flashable from twrp. So you can wipe the system partition and get a "better situation" than a nandroid backup that should be with an old version.
Or use this that has also root and other improvements.

shewshain said:
Hi.
I have a problem with my D855. My phone is rooted and runs the fulmics ROM. Everything was working fine, , on Fulmics 5.3, except than one day, I was using my phone normally and then it crashed. I saw the phone rebooting, but for some reason it got stuck. The phone tried to boot unsuccessfully until the "firmware update" went through, after what it reboots again (unsuccessfully) and so on.
At that time, I was able to access twrp, do some backup, and flash properly with a downgraded version of fulmics (from 5.3 to 4.1).
It was able to boot again and use my phone like before. Yet, after one month of usage, the same problem happened on version 4.1. The phone crashed and now cannot boot.
Any idea of where it is coming from? Should I go back to stock? Should I contact customer service?
Click to expand...
Click to collapse
Same problem here. Normal usage suddenly started to reboot and now it's stuck in boot loop

Coming from Fulmics too - stopped working one fine day.
Now, continues to boot-loop at the initial LG screen. Trying to get into the recovery shows me the the 'Factory Reset' screen, but beyond that leads to boot-loops again. Even the Download mode loops!
I'm at my wits end without a solution in sight.

Blysterk said:
You can also use the Stock rom flashable from twrp. So you can wipe the system partition and get a "better situation" than a nandroid backup that should be with an old version.
Or use this that has also root and other improvements.
Click to expand...
Click to collapse
Thank you for this advice. I was able to update my stock ROM after the Nandroid backup through LGUP, but your method would have been faster.
But anyway, I am waiting to see if I am stuck with bootloops again, using non-root stock version, so I can send it to customer service if this happen again.
AhmadAlmousa said:
Same problem here. Normal usage suddenly started to reboot and now it's stuck in boot loop
Click to expand...
Click to collapse
abourdeau said:
I have the exact same problem, I even bought a second battery with no success.
Click to expand...
Click to collapse
Are you using Fulmics ROM as well? Can you have access to TWRP? I was able to connect to a PC in the recovery mode and to transfer files before flashing, in case you need some basic backup...

prakhargr8 said:
Coming from Fulmics too - stopped working one fine day.
Now, continues to boot-loop at the initial LG screen. Trying to get into the recovery shows me the the 'Factory Reset' screen, but beyond that leads to boot-loops again. Even the Download mode loops!
I'm at my wits end without a solution in sight.
Click to expand...
Click to collapse
Silly question, but are you sure that you selected "Yes" when the screen asks you about factory reset? you have to press "volume down" and the "power button", since the default answer is no.

shewshain said:
Silly question, but are you sure that you selected "Yes" when the screen asks you about factory reset? you have to press "volume down" and the "power button", since the default answer is no.
Click to expand...
Click to collapse
Yes, of course I was able to access TWRP successfully earlier.
Curiously enough, the phone boot-loops in regular startup, Download mode and trying to get to recovery. However, it doesn't restart itself and fall into a loop, while on the Factory Reset menu. Am I correct in assuming that the battery could not be the root cause of the overall problem? Because if it was, it would likely loop even on this Factory Reset menu as well as far as I understand.
Unfortunately, the phone restarts as soon as it lands in the Download mode so I cannot even restore to stock.
EDIT: Okay, weirdly enough it just booted and reached the homescreen before restarting again. What I did was let it charge to a 100% and tried booting while plugged in. Could it be the battery after all? Though this exact set of steps hasn't been helpful before.

Phone no longer bricked (yay!), but not fastboot

The backstory: I have no experience with rooting and or flashing custom ROMs. Prior to today my ze551ml was completely stock, running on the official android M update. I had a need to do a factory reset, but the phone would simply reboot. I assumed this was a problem with the update so I download and attempted to install the downgrade to l. Naturally it crashed mid downgrade and I thought it to be bricked. So, I started Googling and realized I was able to get into fastboot mode, but not recovery. Following a guide I located I attempted to flash the preroot ROM located at the link below:
http://forum.xda-developers.com/zenfone2/development/rom-pre-root-img-t3079590
Well, it appeared to have worked, but now the phone refused to boot at all after being turned off. So, more Googling and I proceeded to follow the full unbricking guide below:
http://forum.xda-developers.com/zenfone2/help/thead-bricked-phone-updating-to-mm-tips-t3452785
Partway through step 1.3 the phone restarted itself and booted right up into Android L! Success I thought to myself, but it was not to be. I proceeded to download the FOTA L update and it downloaded fine, but when I clicked to install it simply rebooted the phone. Tried a couple of other times with the same result. I realized that Supersu was installed so I did the full unroot assuming that was the problem, but to no avail. It appears that the updates can't install because the phone is incapable of entering fastboot or recover mode. Anytime I attempt to enter fastboot via hard key or through adb the phone hangs on the ASUS logo. Adb detects the phone when it's connected via USB, but of course fastboot can't because I can't get it into fastboot mode at all.
Any tips on how to get fastboot operational again so I can start applying updates again? Every guide I've located has started with "boot into fastboot/recovery" which simply isn't an option. Any help is appreciated.
Edit: Well, I think I've reached the end of the internet trying to google for a solution. The phone works, but it looks like it's stuck on build 2.13.40.13 until the end of its life. If anybody has any ideas I'm still hoping for a solution, but I can't find anything describing how to restore fastboot if the OS is intact.

kidnova said:
The backstory: I have no experience with rooting and or flashing custom ROMs. Prior to today my ze551ml was completely stock, running on the official android M update. I had a need to do a factory reset, but the phone would simply reboot. I assumed this was a problem with the update so I download and attempted to install the downgrade to l. Naturally it crashed mid downgrade and I thought it to be bricked. So, I started Googling and realized I was able to get into fastboot mode, but not recovery. Following a guide I located I attempted to flash the preroot ROM located at the link below:
http://forum.xda-developers.com/zenfone2/development/rom-pre-root-img-t3079590
Well, it appeared to have worked, but now the phone refused to boot at all after being turned off. So, more Googling and I proceeded to follow the full unbricking guide below:
http://forum.xda-developers.com/zenfone2/help/thead-bricked-phone-updating-to-mm-tips-t3452785
Partway through step 1.3 the phone restarted itself and booted right up into Android L! Success I thought to myself, but it was not to be. I proceeded to download the FOTA L update and it downloaded fine, but when I clicked to install it simply rebooted the phone. Tried a couple of other times with the same result. I realized that Supersu was installed so I did the full unroot assuming that was the problem, but to no avail. It appears that the updates can't install because the phone is incapable of entering fastboot or recover mode. Anytime I attempt to enter fastboot via hard key or through adb the phone hangs on the ASUS logo. Adb detects the phone when it's connected via USB, but of course fastboot can't because I can't get it into fastboot mode at all.
Any tips on how to get fastboot operational again so I can start applying updates again? Every guide I've located has started with "boot into fastboot/recovery" which simply isn't an option. Any help is appreciated.
Edit: Well, I think I've reached the end of the internet trying to google for a solution. The phone works, but it looks like it's stuck on build 2.13.40.13 until the end of its life. If anybody has any ideas I'm still hoping for a solution, but I can't find anything describing how to restore fastboot if the OS is intact.
Click to expand...
Click to collapse
You have to use full unbrick method(xfstk + raw) to restore ur device fully
xfstk will restore ur fastboot image

yakub234go said:
You have to use full unbrick method(xfstk + raw) to restore ur device fully
xfstk will restore ur fastboot image
Click to expand...
Click to collapse
Thanks for the response. I've tried this a dozen times, but unfortunately (this is going to sound weird) since it's not completely bricked it is only detected as Moorefield for a few seconds when started. This allows the xfstk tool to detect it and begin the download, but not long enough to complete the process so it times out. The only development access I have to the phone now is via adb, but since I don't have root I'm very limited in what I can do via command line. Since I can't access fastboot I can't achieve root. It's just a comedy of errors now.

kidnova said:
The backstory: I have no experience with rooting and or flashing custom ROMs. Prior to today my ze551ml was completely stock, running on the official android M update. I had a need to do a factory reset, but the phone would simply reboot. I assumed this was a problem with the update so I download and attempted to install the downgrade to l. Naturally it crashed mid downgrade and I thought it to be bricked. So, I started Googling and realized I was able to get into fastboot mode, but not recovery. Following a guide I located I attempted to flash the preroot ROM located at the link below:
http://forum.xda-developers.com/zenfone2/development/rom-pre-root-img-t3079590
Well, it appeared to have worked, but now the phone refused to boot at all after being turned off. So, more Googling and I proceeded to follow the full unbricking guide below:
http://forum.xda-developers.com/zenfone2/help/thead-bricked-phone-updating-to-mm-tips-t3452785
Partway through step 1.3 the phone restarted itself and booted right up into Android L! Success I thought to myself, but it was not to be. I proceeded to download the FOTA L update and it downloaded fine, but when I clicked to install it simply rebooted the phone. Tried a couple of other times with the same result. I realized that Supersu was installed so I did the full unroot assuming that was the problem, but to no avail. It appears that the updates can't install because the phone is incapable of entering fastboot or recover mode. Anytime I attempt to enter fastboot via hard key or through adb the phone hangs on the ASUS logo. Adb detects the phone when it's connected via USB, but of course fastboot can't because I can't get it into fastboot mode at all.
Any tips on how to get fastboot operational again so I can start applying updates again? Every guide I've located has started with "boot into fastboot/recovery" which simply isn't an option. Any help is appreciated.
Edit: Well, I think I've reached the end of the internet trying to google for a solution. The phone works, but it looks like it's stuck on build 2.13.40.13 until the end of its life. If anybody has any ideas I'm still hoping for a solution, but I can't find anything describing how to restore fastboot if the OS is intact.
Click to expand...
Click to collapse
seems like you did not install droidboot.bin correctly... only way is use xFSTK again.i have updated the link to latest raw firmware 2.20.40.194 and use the same guide and commands..

sukhwant717 said:
seems like you did not install droidboot.bin correctly... only way is use xFSTK again.i have updated the link to latest raw firmware 2.20.40.194 and use the same guide and commands..
Click to expand...
Click to collapse
The problem is that it's only recognized as Moorefield for a few seconds which isn't enough time for xFSTK to complete the install. Do you know of a way to force the device to stay connected as Moorefield?

kidnova said:
The problem is that it's only recognized as Moorefield for a few seconds which isn't enough time for xFSTK to complete the install. Do you know of a way to force the device to stay connected as Moorefield?
Click to expand...
Click to collapse
Plug the phone to the PC, be sure the phone is completely off and then hold power + vol- for a few seconds. You must see the "Moorefield" driver permanent in the device manager.
Btw... I got the same problem (four lines, not bootloader, not OS; xFSTK FW+OS failed) and I'm stuck in this step :/

mrperalta said:
Plug the phone to the PC, be sure the phone is completely off and then hold power + vol- for a few seconds. You must see the "Moorefield" driver permanent in the device manager.
Btw... I got the same problem (four lines, not bootloader, not OS; xFSTK FW+OS failed) and I'm stuck in this step :/
Click to expand...
Click to collapse
I've tried this many times, but it only shows Moorefield for a few seconds. I'm assuming this is because it has a fully operational OS so it doesn't stay in the generic USB device mode.
EDIT: I misread your original post. Holding power and volume DOWN does keep connect it in Moorefield. Thanks so much for that. The problem now is that once xFSTK gets to downloading the OS it reboots the phone which takes it out of USB mode and disconnects the tool. I'm still stuck where I was before, but that's a little progress. Any other thoughts?

New update. I'm able to get to the point of loading the OS from xFSTK by skipping the FW part, however it continuously fails. My assumption is because it can't overwrite the existing OS. Any other ideas?

kidnova said:
New update. I'm able to get to the point of loading the OS from xFSTK by skipping the FW part, however it continuously fails. My assumption is because it can't overwrite the existing OS. Any other ideas?
Click to expand...
Click to collapse
Kidnova, reading this post I could fixed my problem. The "issue" was in the xFSTK where you put the flag (0x800000807). A guy on the threat said to put "0x80000807" instead of "0x800000807" (note that there is "0" from difference).
"those who are not able to keep device connected. take care of few steps
1. in xFSTK option menu change the flag override value to 0x80000807 not 0x800000807 ( don't forget to click gp value over ride)
2. while connecting to xFSTK attach usb to computer. hold power button for 20 seconds to make sure it power downs completely. then hold the power button down and click power button. wait till device vibrate or computer makes detection sound. leave power button but keep holding the volume button for few seconds"
Click to expand...
Click to collapse
-sukhwant717

mrperalta said:
Kidnova, reading this post I could fixed my problem. The "issue" was in the xFSTK where you put the flag (0x800000807). A guy on the threat said to put "0x80000807" instead of "0x800000807" (note that there is "0" from difference).
-sukhwant717
Click to expand...
Click to collapse
You guys are lifesavers! I've got fast boot again. Now to see if I can continue without screwing it up.
FINAL EDIT: I have a 100% functional stock Zenfone 2. Thanks everybody for your help.

kidnova said:
You guys are lifesavers! I've got fast boot again. Now to see if I can continue without screwing it up.
FINAL EDIT: I have a 100% functional stock Zenfone 2. Thanks everybody for your help.
Click to expand...
Click to collapse
Hi, got the same issues, I've read many posts. Tried all of the million options. What was your final way of doing it, do you remember?

One Plus 5T dead?

Hey guys, I've given up. For every step I make it gets worse.
I had rooted my OP with Magisk, and one night i decided to update my OP. I woke up and tried to turn on my OP, it went to 1+ screen as usual but then the LED went white and the screen totally blank.. I couldn't do a thing.. I decided to wipe everything on my OP with TWRP recovery mode, but it made it worse. Now when i turn it on it starts a bootloop. Recovery mode is totally gone from the phone, and my computer and ADB can't detect my OP. The only things I can do now is going into bootloader or turning it into an endless bootloop.
Can you guide me through this?

Kastholm9fem said:
Hey guys, I've given up. For every step I make it gets worse.
I had rooted my OP with Magisk, and one night i decided to update my OP. I woke up and tried to turn on my OP, it went to 1+ screen as usual but then the LED went white and the screen totally blank.. I couldn't do a thing.. I decided to wipe everything on my OP with TWRP recovery mode, but it made it worse. Now when i turn it on it starts a bootloop. Recovery mode is totally gone from the phone, and my computer and ADB can't detect my OP. The only things I can do now is going into bootloader or turning it into an endless bootloop.
Can you guide me through this?
Click to expand...
Click to collapse
Look here: https://forum.xda-developers.com/on...bricking-tool-confirmation-t3733012?nocache=1

ADB doesn't work while in the bootloader...
Might still be possible to use fastboot in bootloader mode to flash TWRP, boot to recovery, connect to a computer, transfer over a full OTA zip and flash that.
If nothing else though, the unbrick tool likely works...

Didgeridoohan said:
ADB doesn't work while in the bootloader...
Might still be possible to use fastboot in bootloader mode to flash TWRP, boot to recovery, connect to a computer, transfer over a full OTA zip and flash that.
If nothing else though, the unbrick tool likely works...
Click to expand...
Click to collapse
Probably exactly what the unbrick tool would do, except it would more than likely use stock recovery instead of TWRP.

dabistduja said:
Look here: https://forum.xda-developers.com/on...bricking-tool-confirmation-t3733012?nocache=1
Click to expand...
Click to collapse
Use this tool, it's damn easy making your OP back to original FW out of the box.

l3ones said:
Probably exactly what the unbrick tool would do, except it would more than likely use stock recovery instead of TWRP.
Click to expand...
Click to collapse
So, in other words it'd be less work using fastboot, because you'd have TWRP from the start and could put whatever ROM version you'd want on there straight away... :laugh:

Weird bootloop with locked bootloader

Long story short, I ended up with a classic bootloop (shows boot animation continuously) from messing around with Magisk modules, so I did a wipe from recovery, still bootloop, so I tried reverting completely to stock with the OEM downloads. I tried flash_all_except_storage.bat, and flash_all.bat, but this time it was a different bootloop. The phone shows the Android One logo, the screen flickers like it's going to the boot animation, but then it just goes back to the Unlocked Bootloader Warning Screen, then the Android One logo, and loops like that. I dumbly thought locking the bootloader, reflashing everything, and starting over like it were a new phone would fix the issue, so I did flash_all_lock.bat, but now I'm just stuck with this weird bootloop and a locked bootloader. Trying to unlock the bootloader with fastboot just gives me "oem unlock is not allowed", so I'm at a loss here.
Does anyone know of anything else I could do, or is this a hard brick?

With a locked bootloader EDL flash probably is your last chance.
Maybe this thread helps:
https://forum.xda-developers.com/mi-a2-lite/help/hard-bricked-mi-a2-lite-help-to-enter-t3862648

thorin0815 said:
With a locked bootloader EDL flash probably is your last chance.
Maybe this thread helps:
https://forum.xda-developers.com/mi-a2-lite/help/hard-bricked-mi-a2-lite-help-to-enter-t3862648
Click to expand...
Click to collapse
I got stuck with a similar problem and that was the only option, to boot into EDL mode you will need to partially dissasemble your device and flash the image via fastboot or via MiFlash (download the latest version as I had problems with an older one). Since that incident I kept the bootloader unlocked just in case something happens.

I had the phone booted into EDL mode and attempted to flash the stock ROM (10.0.3.0) with MiFlash, but it errored out with an ERROR_UNSUPPORTED_TYPE. I tried with the previous version, 10.0.2.0 and it worked for some reason. That fixed it though, so thanks! I've been lightly tinkering with rooting android phones a few years now, but until encountering this issue, I'd never heard of EDL mode. You learn something new every day? ?

I have the same issue with my nephew 's mi a2 lite which has the bootloader locked.
It only shows the android one logo.
I cannot go to recovery mode, but I can go in fastboot.
Changing from "a" to "b" doesn't solve anything and being the bootloader locked is not possible to flash anything from fastboot.
So I've opened the device and I've short circuited the edl pinpoint to be able to flash with MiTool (I've used an old version since more recent ones gave errors when flashing).
I was able to flash both the latest official ROM and the oldest one which I've found ( daisy_global_images_V11.0.14.0.QDLMIXM_10.0 and daisy_global_images_V9.6.4.0.ODLMIFF_8.1 respectively).
In both cases the device still is "frozen" with the android one logo when I've tried to turn it on after the flashing procedures gave me a successful status.
What else can I do?