Related
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
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 happenedI 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 didSo 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 happenedAfter 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
Well my journey started because i wanted to install the latest stock nougat on my device "7.1.1" and i had bad boyz rom installed on my device so the update wasn't showing up so i follow this this THREAD and i downloaded all the tools needed in order to flash my device so when i tried it at first it showed me a bad format error "HERE'S THE PIC" after that error i unpluged my phone off the pc and tried to turn it on but i had no luck and now it's stuck in a black screen and every time i plugged it in to my pc it shows up as qloader 9008 but apparently miflash cannot flash it or any other tooland it says it cannot retrive the hello packet "HERE'S THE PIC", my bootloader was unlocked and the device was also root, i also tried calling their RMA but they didn't do much since my bootloader was unlocked :C
I couldn't make the youtube thinggy work lol but here's the link in case you guys wanna know what's going on with my piece of brick lol
https://www.youtube.com/watch?v=xX8_RgSS5x0
J0nhy said:
Well my journey started because i wanted to install the latest stock nougat on my device "7.1.1" and i had bad boyz rom installed on my device so the update wasn't showing up so i follow this this THREAD and i downloaded all the tools needed in order to flash my device so when i tried it at first it showed me a bad format error "HERE'S THE PIC" after that error i unpluged my phone off the pc and tried to turn it on but i had no luck and now it's stuck in a black screen and every time i plugged it in to my pc it shows up as qloader 9008 but apparently miflash cannot flash it or any other tooland it says it cannot retrive the hello packet "HERE'S THE PIC", my bootloader was unlocked and the device was also root, i also tried calling their RMA but they didn't do much since my bootloader was unlocked :C
Click to expand...
Click to collapse
There are a whole bunch of problems with this version of MiFlash. Try this version: http://xiaomiflashtool.com/download/xiaomi-flash-tool-20160401
J0nhy said:
Well my journey started because i wanted to install the latest stock nougat on my device "7.1.1" and i had bad boyz rom installed on my device so the update wasn't showing up so i follow this this THREAD and i downloaded all the tools needed in order to flash my device so when i tried it at first it showed me a bad format error "HERE'S THE PIC" after that error i unpluged my phone off the pc and tried to turn it on but i had no luck and now it's stuck in a black screen and every time i plugged it in to my pc it shows up as qloader 9008 but apparently miflash cannot flash it or any other tooland it says it cannot retrive the hello packet "HERE'S THE PIC", my bootloader was unlocked and the device was also root, i also tried calling their RMA but they didn't do much since my bootloader was unlocked :C
Click to expand...
Click to collapse
Run into the same problem with "Miflash cannot read helloL". Here the fix:
Flash with the package: the "B15-NEW_FULL (Nougat)"
Still in the thread https://forum.xda-developers.com/axon-7/development/edl-emergency-dl-mode-twrp-unlock-t3553514
bkores said:
There are a whole bunch of problems with this version of MiFlash. Try this version: http://xiaomiflashtool.com/download/xiaomi-flash-tool-20160401
Click to expand...
Click to collapse
Thanks man i tried that one too no luck :C
tamahouse02 said:
Run into the same problem with "Miflash cannot read helloL". Here the fix:
Flash with the package: the "B15-NEW_FULL (Nougat)"
Still in the thread https://forum.xda-developers.com/axon-7/development/edl-emergency-dl-mode-twrp-unlock-t3553514
Click to expand...
Click to collapse
Yes man i tried it but i had no luck :C, thanks
Unzip and flash the file inside. Also you must reboot edl after any failed attempt.
J0nhy said:
Yes man i tried it but i had no luck :C, thanks
Click to expand...
Click to collapse
Use this driver
Restart - enter EDL again
Flash "B15-NEW_FULL (Nougat)" (the full one, not the twrp one)
lafester said:
Unzip and flash the file inside. Also you must reboot edl after any failed attempt.
Click to expand...
Click to collapse
Cannot turn off or on my device i cannot not do anything the only thing it does is a sound every time i plug it in to my pc
Keep trying. It is hard to tell with the black screen. Just watch device manager to see it reboot.
lafester said:
Keep trying. It is hard to tell with the black screen. Just watch device manager to see it reboot.
Click to expand...
Click to collapse
Hahahahaha got it working mate thanks, so i tried a samsung cable with the adapter and it worked lol thanks mate
tamahouse02 said:
Run into the same problem with "Miflash cannot read helloL". Here the fix:
Flash with the package: the "B15-NEW_FULL (Nougat)"
Still in the thread https://forum.xda-developers.com/axon-7/development/edl-emergency-dl-mode-twrp-unlock-t3553514
Click to expand...
Click to collapse
Thanks. I kept getting partition type errors. The link you posted kept having network errors and dropping. It wasn't till after midnight pst that I got a stable connection and downloaded the whole thing. It flashed great and my phone is up and running. I was thinking I would have to send my phone in.
J0nhy said:
Hahahahaha got it working mate thanks, so i tried a samsung cable with the adapter and it worked lol thanks mate
Click to expand...
Click to collapse
Yeah that's the kind of errors that suck /real/ bad. Good on you for not giving up. Now you know and you'll help spread the gospel of "keep trying until you can prove that it's actually an issue".
This is for those of you that have a S8+ that only boots into Upload Mode and nothing else. When you connect it to the computer it may should say Qualcomm HS-USB QDLoader 9008. Others may have even told you theres nothing that can be done to fix it and that its bricked! Yes, yes, I believed too. I sent to Samsung who sent back the phone and a 850$ option for replacing the board.
I work at Northrop Grumman, they make B2s and stuff, and they happen to have a partnership with Qualcomm so I set up an account with them, downloaded official and latest QPST, QXDM, and QUD. I was able to provision the device using QFIL (unsure if required), but I was unable to flash anything with QFIL. My phone has been useless for 3 months now. I randomly try again here and there, with repeated failure and lost hope. UNTIL TODAY.
Craziest thing ever, and trust me, I know, it does not look remotely close to legit. IT IS.
basically, you do the captcha thing, it takes you to a MEGA download site, you download a zip folder that is named G955U2. Connect the phone to the computer while the screen is black and not on upload mode. The device manager should show the QDLoader 9008 in the Port section. Unzip the downloaded file. Open the folder. DOUBLE CLICK G955U2_Recovery.Bat. Do not run as admin, mine didn't work that way, only double clicking. Wait about a minute, when it says finished, boot the phone into Download mode by holding vol down + Bixby+Power. Not done yet though. SO you should have Download Mode on. Now you need to flash the Odin files, which I am currently doing myself. I have noticed a few issues but I have gotten almost there. I can only suggest flashing a BL first of your firmware and then after that's done do the AP. Once that is done you will be where I am at, and I will update once I am able to fully flash a complete firmware.
Downloads Mod edits am not sure who created that tool, where it came from, or who to thank. Alls I know is it works and is a freakin masterpiece.
Update: I have my phone up and running. On official Oreo firmware I am unable to get any network signals (wireless or mobile). On PartyCyborgRom I am able to get wifi but anytime I put a SIM card in it tells me to reboot, and does the same thing upon boot. I believe that my EFS folder is corrupt/formatted/missing. I have read that formatting the EFS folder to EXT4 can help and that it is mmcblk0p* with the * being a number. The EFS thing is the only issue I am having though. If TWRP were able to be installed on the S8+ for Sprint I would install it and format the folder through it but with the bootloader locked I am not sure its possible. Possibly thinking about completely resetting the phone back to the QDLoader and starting from complete scratch and seeing if I can format the EFS folder before flashing a firmware. Anyone know how to fix the EFS thing?
After flashing first the BL and then the AP separately I was able to flash AP+CP+CSC+BL all at once. I have now fully booted. At first, it will go into recovery and then say failed due to something about mounting an efl folder or something. What I did was mount the system and then factory reset. Then rebooted to phone, and voila. I am not sure if wifi is working just yet or what else may not work. I do know I have booted and am further than I have been before and should be much easier to fix now. I'll keep updated.
Would've been better if you posted the Mega link instead of having to jump through hoops.
https://mega.nz/#!8nQCSZCA!MOGy_httgg1VOYxVLgsPh8cBuSOTBHzfKXZAIydu_kM
droseofc,
Interesting info/find/fix!
gamer765 said:
Would've been better if you posted the Mega link instead of having to jump through hoops.
https://mega.nz/#!8nQCSZCA!MOGy_httgg1VOYxVLgsPh8cBuSOTBHzfKXZAIydu_kM
Click to expand...
Click to collapse
I didn't want to overstep the original poster/possibly creator feet. I figured if they wanted the captcha then they should get the captcha because I would've never found it directly to the mega link, nor would have you.
droseofc said:
After flashing first the BL and then the AP separately I was able to flash AP+CP+CSC+BL all at once. I have now fully booted. At first, it will go into recovery and then say failed due to something about mounting an efl folder or something. What I did was mount the system and then factory reset. Then rebooted to phone, and voila. I am not sure if wifi is working just yet or what else may not work. I do know I have booted and am further than I have been before and should be much easier to fix now. I'll keep updated.
Click to expand...
Click to collapse
droseofc said:
This is for those of you that have a S8+ that only boots into Upload Mode and nothing else. When you connect it to the computer it may should say Qualcomm HS-USB QDLoader 9008. Others may have even told you theres nothing that can be done to fix it and that its bricked! Yes, yes, I believed too. I sent to Samsung who sent back the phone and a 850$ option for replacing the board.
I work at Northrop Grumman, they make B2s and stuff, and they happen to have a partnership with Qualcomm so I set up an account with them, downloaded official and latest QPST, QXDM, and QUD. I was able to provision the device using QFIL (unsure if required), but I was unable to flash anything with QFIL. My phone has been useless for 3 months now. I randomly try again here and there, with repeated failure and lost hope. UNTIL TODAY.
Craziest thing ever, and trust me, I know, it does not look remotely close to legit. IT IS. basically, you do the captcha thing, it takes you to a MEGA download site, you download a zip folder that is named G955U2. Connect the phone to the computer while the screen is black and not on upload mode. The device manager should show the QDLoader 9008 in the Port section. Unzip the downloaded file. Open the folder. DOUBLE CLICK G955U2_Recovery.Bat. Do not run as admin, mine didn't work that way, only double clicking. Wait about a minute, when it says finished, boot the phone into Download mode by holding vol down + Bixby+Power. Not done yet though. SO you should have Download Mode on. Now you need to flash the Odin files, which I am currently doing myself. I have noticed a few issues but I have gotten almost there. I can only suggest flashing a BL first of your firmware and then after that's done do the AP. Once that is done you will be where I am at, and I will update once I am able to fully flash a complete firmware.
Downloads I am not sure who created that tool, where it came from, or who to thank. Alls I know is it works and is a freakin masterpiece.
Update: I have my phone up and running. On official Oreo firmware I am unable to get any network signals (wireless or mobile). On PartyCyborgRom I am able to get wifi but anytime I put a SIM card in it tells me to reboot, and does the same thing upon boot. I believe that my EFS folder is corrupt/formatted/missing. I have read that formatting the EFS folder to EXT4 can help and that it is mmcblk0p* with the * being a number. The EFS thing is the only issue I am having though. If TWRP were able to be installed on the S8+ for Sprint I would install it and format the folder through it but with the bootloader locked I am not sure its possible. Possibly thinking about completely resetting the phone back to the QDLoader and starting from complete scratch and seeing if I can format the EFS folder before flashing a firmware. Anyone know how to fix the EFS thing?
Click to expand...
Click to collapse
there are adb codes to zero it out i just went through a corupted efs but had a backup i made in Flashfire a while back
@elliwigy might be able to help on this to as I know he has done some edl stuff
i can tell you one thing you should NOT do is mess with your efs partition.. itstores lots of information such as imei information which you shouldnt "wipe" unless you have backups and a way to restore it
try flashing a full combination firmware then back to full rom..
try flashing cp and csc files from stock firmware etc
9008 mode is EDL mode. those files are nothing new, in fact i havethe same exact files and more.. if u dont know what youre doing i wouldnt use edl more than u have to as you can do moredamagethan harm and maybe harm even edl cant recover from (yes, i bricked a hard brick in edl and had to replace the whole device)
elliwigy said:
i can tell you one thing you should NOT do is mess with your efs partition.. itstores lots of information such as imei information which you shouldnt "wipe" unless you have backups and a way to restore it
try flashing a full combination firmware then back to full rom..
try flashing cp and csc files from stock firmware etc
9008 mode is EDL mode. those files are nothing new, in fact i havethe same exact files and more.. if u dont know what youre doing i wouldnt use edl more than u have to as you can do moredamagethan harm and maybe harm even edl cant recover from (yes, i bricked a hard brick in edl and had to replace the whole device)
Click to expand...
Click to collapse
These files are what got me out of a brick. I was in EDL from flashing a bootloader with Flashfire. Could not get the device to do anything but get into upload mode or the qdloader mode. That's what these files were for, for those who could not get out of the QDLoader thing. And I tried everything from Combo Factory Binary to qualfast, flash image loader, snapdragon flash tool, qcomm, heimdall, qcom, efs professional, DFU, DFS, Samsung PST SW DLL, CDMA Workshop, CHMC PST, Gtran, PSTlite, CDMA universal, VK Mobile, Symbian Flashing Tool, QFIL, QPST, emmc. Nothing got me out of the EDL except that link. And it was just as simple as two clicks.
As for the EFS folder, I was able to reformat the EFS so that in recovery it no longer said "unable to mount /efs" and I could do a factory reset without any mount warnings. I tried restoring a backup of another s8+, doing the erase everything but two folders in the EFS folder and flashing a combo in the AP slot and then a official firmware, nothing was able to bring back an IMEI as it displayed all 0s. There may be a way, I tried programming the IMEI with various tools. I ended up talking to sprint to have them attempt to reactivate the device on my account, while doing that I added TEP (protection plan), in the midst of trying to activate they became aware that I had 0s for my IMEI and advised I take it into a store. I did just that and it would of been a free replacement but I had a teeny unrelated smidge of a crack on the top right corner so I have to pay 140$ for a replacement/repair. I'm sure it'll be a replacement because as you said, without a backup of the EFS its pretty tough to get it back.
if u read my post i said i wouldnt use edl more than u have to if u dont kno wat ur doing.. if ur stuck in edl mode then u had no other choice..
that is what edl mode is used for, to recover from bricks..
however, u clearly wiped ur efs in the process andtheres no way to recover that so not sure y ur still trying to wipe it or recover it lol.. theresno way to recover efs if u never backed it up in the first place.. flashing random files will not magically repopulate it unfortunately
https://www.theandroidsoul.com/fix-...fibluetooth-issues-restoring-twrp-backup/amp/ there are numerous other methods for rebuilding efs folder.
droseofc said:
This is for those of you that have a S8+ that only boots into Upload Mode and nothing else. When you connect it to the computer it may should say Qualcomm HS-USB QDLoader 9008. Others may have even told you theres nothing that can be done to fix it and that its bricked! Yes, yes, I believed too. I sent to Samsung who sent back the phone and a 850$ option for replacing the board.
I work at Northrop Grumman, they make B2s and stuff, and they happen to have a partnership with Qualcomm so I set up an account with them, downloaded official and latest QPST, QXDM, and QUD. I was able to provision the device using QFIL (unsure if required), but I was unable to flash anything with QFIL. My phone has been useless for 3 months now. I randomly try again here and there, with repeated failure and lost hope. UNTIL TODAY.
Craziest thing ever, and trust me, I know, it does not look remotely close to legit. IT IS.
basically, you do the captcha thing, it takes you to a MEGA download site, you download a zip folder that is named G955U2. Connect the phone to the computer while the screen is black and not on upload mode. The device manager should show the QDLoader 9008 in the Port section. Unzip the downloaded file. Open the folder. DOUBLE CLICK G955U2_Recovery.Bat. Do not run as admin, mine didn't work that way, only double clicking. Wait about a minute, when it says finished, boot the phone into Download mode by holding vol down + Bixby+Power. Not done yet though. SO you should have Download Mode on. Now you need to flash the Odin files, which I am currently doing myself. I have noticed a few issues but I have gotten almost there. I can only suggest flashing a BL first of your firmware and then after that's done do the AP. Once that is done you will be where I am at, and I will update once I am able to fully flash a complete firmware.
Downloads Mod edits am not sure who created that tool, where it came from, or who to thank. Alls I know is it works and is a freakin masterpiece.
Update: I have my phone up and running. On official Oreo firmware I am unable to get any network signals (wireless or mobile). On PartyCyborgRom I am able to get wifi but anytime I put a SIM card in it tells me to reboot, and does the same thing upon boot. I believe that my EFS folder is corrupt/formatted/missing. I have read that formatting the EFS folder to EXT4 can help and that it is mmcblk0p* with the * being a number. The EFS thing is the only issue I am having though. If TWRP were able to be installed on the S8+ for Sprint I would install it and format the folder through it but with the bootloader locked I am not sure its possible. Possibly thinking about completely resetting the phone back to the QDLoader and starting from complete scratch and seeing if I can format the EFS folder before flashing a firmware. Anyone know how to fix the EFS thing?
Click to expand...
Click to collapse
OP edited pay per click links not allowed
will this method work on Binary 5 firmware?
Can you please let me know what the fix is for this? I have an S8 like this.
I suggest you go thru the post and read from begining, thoroughly... its elaborate enough, ive not tried but i'm going thru it for knowledge sake
droseofc said:
This is for those of you that have a S8+ that only boots into Upload Mode and nothing else. When you connect it to the computer it may should say Qualcomm HS-USB QDLoader 9008. Others may have even told you theres nothing that can be done to fix it and that its bricked! Yes, yes, I believed too. I sent to Samsung who sent back the phone and a 850$ option for replacing the board.
I work at Northrop Grumman, they make B2s and stuff, and they happen to have a partnership with Qualcomm so I set up an account with them, downloaded official and latest QPST, QXDM, and QUD. I was able to provision the device using QFIL (unsure if required), but I was unable to flash anything with QFIL. My phone has been useless for 3 months now. I randomly try again here and there, with repeated failure and lost hope. UNTIL TODAY.
Craziest thing ever, and trust me, I know, it does not look remotely close to legit. IT IS.
basically, you do the captcha thing, it takes you to a MEGA download site, you download a zip folder that is named G955U2. Connect the phone to the computer while the screen is black and not on upload mode. The device manager should show the QDLoader 9008 in the Port section. Unzip the downloaded file. Open the folder. DOUBLE CLICK G955U2_Recovery.Bat. Do not run as admin, mine didn't work that way, only double clicking. Wait about a minute, when it says finished, boot the phone into Download mode by holding vol down + Bixby+Power. Not done yet though. SO you should have Download Mode on. Now you need to flash the Odin files, which I am currently doing myself. I have noticed a few issues but I have gotten almost there. I can only suggest flashing a BL first of your firmware and then after that's done do the AP. Once that is done you will be where I am at, and I will update once I am able to fully flash a complete firmware.
Downloads Mod edits am not sure who created that tool, where it came from, or who to thank. Alls I know is it works and is a freakin masterpiece.
Update: I have my phone up and running. On official Oreo firmware I am unable to get any network signals (wireless or mobile). On PartyCyborgRom I am able to get wifi but anytime I put a SIM card in it tells me to reboot, and does the same thing upon boot. I believe that my EFS folder is corrupt/formatted/missing. I have read that formatting the EFS folder to EXT4 can help and that it is mmcblk0p* with the * being a number. The EFS thing is the only issue I am having though. If TWRP were able to be installed on the S8+ for Sprint I would install it and format the folder through it but with the bootloader locked I am not sure its possible. Possibly thinking about completely resetting the phone back to the QDLoader and starting from complete scratch and seeing if I can format the EFS folder before flashing a firmware. Anyone know how to fix the EFS thing?
Click to expand...
Click to collapse
Can you please help me out with my Samsung Galaxy S4 VZW (i545) I'm on hard brick too. I don't know what to do now to debrick phone, I've got debrick files, USB-JIT, trying to flashing with Qualcomm qpst, Qfil, if you have program like that as yours to debrick phone I'll be thankful..
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