Okay. so I have this Problem: I tried to install an incompatible Rom and im getting secure boot error boot certification verify. Normally would not be a problem. I have twrp installed and all the roms and files I would need to fix it. Here's the catch. The power button is broken so I have no access to the recovery menu. Just to turn it on I have to battery pop. Any help on getting into recovery through some back door? Can't get it to connect to ADB because I cant get past the secure boot error lol
Also I can get into download mode, but that still doesnt make the computer recognise it to connect with adb
From download mode you can use LGUP I think. You should be able to flash back to stock just to get it working again, and then go from there.
http://forum.xda-developers.com/showpost.php?p=64624324&postcount=2
However, I don't know what conflicts exist with doing that with a custom recovery or anything.
There's no conflict with custom recovery when flashing the official stock KDZ or TOT because either one will overwrite everything with the stock partitions. Personally, I recommend flashing the 10B TOT. TOTs flash more partitions than KDZs and can fix problems KDZs sometimes can't. In my one try of using LGUp on the VS985 I didn't have any luck, so I stick with the old tools.
Also, in the future, please post questions in the Q&A section. I'll ask a moderator to move this thread.
Hey guys. Was able to finally get it fixed by flashing to 12b using the kdz method. Had issues installing twrp and had to use flashify premium. Finally got it all running and hooked up with cloudy g3 thanks for the advices
Related
Hi! I've managed to brick my device (d610ar) badly, i think
the device doesn't boot normally (message "Secure booting error! Cause: boot certification verify.", and i am stuck there), can't charge it with the wall charger, and the only thing that works is download mode; but flashing a kdz with LG FlashTool (the way i went back to stock a few times) says flashing and at 2% (or 3% sometimes) it says that doesn't find the device, that i have pull out the battery to reconnect my device again and when i do that it does the same thing on a loop, asking to do it again later..
the funny thing is that it appears on device manager on windows, on com port 11 for example, but the FlashTool doesn't recognize it..
so, i can't flash any kdz and doesn't boot.. i've read around here in xda to enter fastboot to fix it, but.. can this device enter fastboot? i couldn't do it, tried adb too and couldn't make the device visible..
i, before this happened, had multirom installed, rebooted to recovery and deleted secondary roms to install in primary rom cm12.1.. there started to happen strange things when rebooted normally to configure it..
after a while trying to boot found around here in xda too that i could enter twrp recovery via hardware keys to reinstall again, so got into it and installed a flashable zip to come back to stock KitKat directly, that have worked for me before..
after that rebooted and i can't do anything else than download mode..
i kinda figured that the problem must be that multirom injected the boot sector after installing the stock flashable zip, and when i did that restored the stock aboot and abootb (these, modified carefully, allowed us to unlock bootloader and flash recoveries, etc, etc.. ; by the way, many thanks to the devs that discovered it and made the guides!)..
now i have read the instructions for flash via fastboot the stock boot.img and so pass the security verification, but i can't enter it..
so, what do you think that could be the next step? or is it really hard bricked and i should forget about it? i'm really hoping to recover it but i don't know what else to do..
sorry for the bad english, not my primary language
thanks for reading and i am hoping to hear some suggestions!
He is not hard bricked you need to flash stock boot and reunlock bootloader if you have custom recovery still installed, but go first with the eazy way search xda about lg flash tool stuck at 2% there some guides to help you get kdz flashed
Thank you very much!
numpea said:
He is not hard bricked you need to flash stock boot and reunlock bootloader if you have custom recovery still installed, but go first with the eazy way search xda about lg flash tool stuck at 2% there some guides to help you get kdz flashed
Click to expand...
Click to collapse
Thank you very much! You made me realize why wasn't working..
Because of you, i started to search threads related with the "flashtool stuck at 2%" and one of the things to look at was a txt file to see what was the problem.. there i found out that the lg FlashTool recognized my device as LGD618..
That's when i realized that i must've messed up when i flashed a lollipop flashable zip for the D618(a while ago), "converting" my cellphone on that model.. so when i connected on download mode and put the LGD610 kdz the comparison of cellphone model and binary model didn't match..
Solution was to flash LGD618 kdz, boot up normally, install towelroot, install supersu, edit a line on build.prop
from persist.multisim.config=dsds to persist.multisim.config=none
rebooted and that's it.. everything works perfectly now! i won't be doing stuff to it for a while
probably will stay stock like that, because now i will be using an OnePlus One in a few days and the G2 mini will be used by my mother, i think..
Thanks again! You saved my device for being bricked forever
i glad i could helped you :good:
I tried installing kitkat having installed lollipop and did not work, also I tried installing lollipop and nothing. Well I think this update lollipop are adding some kind of lock to disallow downgrade or upgrade by KDZ. I try other methods, unlocking bootloader, and install a aboot.img, bricked my phone. I recommend that you do not attempt to unlock the bootloader and install any system image that is not official, or may end up with a dead device.
I am trying to flash TWRP on 10B (was running 23C and did KDZ flash back to 10B). Rooted via Stump, installed BusyBox, TWRP Mananger and Official TWRP App. Since TWRP didn't appear to install TWRP I did some more research I read people had success with 'Partitions Backup' to backup stock recovery partition and then use 'Flashify' to install TWRP. So I downloaded the twrp-3.0.2-0-vs985.img and installed that to recovery after backing up stock. Next reboot takes me into TWRP. If I then boot normally and then shutdown and enter recovery again I'm back in stock recovery. So it's like the flash is temporary.
Anybody care to educate me about what I am doing wrong. I'm sure this was easier in the days of the 'all-in-one' root/TWRP installer but can't download that anymore and I'm tired of the updates and poor performance so want to try custom ROM's.
Any help would be appreciated. I am thinking maybe I need to install recovery again when booted into TWRP? Not sure.
I am wondering if the flash doesn't work because I flashed a TWRP img without the "bump" designation? I am beginning to think the best way to install reliably is using the 'dd' command from adb over remote PC connection (or via su in a terminal shell if advisable)? Any thoughts on using this method and whether I can go right to the latest version of TWRP for the vs985 (twrp-3.0.2-0-vs985.img).
skay said:
I am wondering if the flash doesn't work because I flashed a TWRP img without the "bump" designation? I am beginning to think the best way to install reliably is using the 'dd' command from adb over remote PC connection (or via su in a terminal shell if advisable)? Any thoughts on using this method and whether I can go right to the latest version of TWRP for the vs985 (twrp-3.0.2-0-vs985.img).
Click to expand...
Click to collapse
I think you might have solved your own problem! You can't use just any TWRP image. It has to be specifically bumped for the G3.
iBolski said:
I think you might have solved your own problem! You can't use just any TWRP image. It has to be specifically bumped for the G3.
Click to expand...
Click to collapse
Thanks for the reply iB. I only tried flashing with the VS985 img files. But I didn't start with one that specifically had the "bump" or "bumped" designation in the filename. I am wondering if the later version that I used doesn't actually install bump to recovery but it intended to be installed as an updated version of TWRP on a previously "bumped" recovery image? Sorry for getting into the weeds here but I actually just stayed rooted on 23C for quite a while until I couldn't take it anymore. I looked at moving up to G4, G5, V10 and V20 but it seems like the G3 is the best value LG phone for custom ROMs and hardware is still not bad overall.
Anyone know of a way to determine if recovery has been flashed with TWRP img before attempting 'factory reset' option? I based my questions thus far on the assumption that if it flashed successfully I would see only the 'factory reset' and 'reboot' options in the new recovery, but I see all 5 options as before flashing TWRP.
skay said:
Anyone know of a way to determine if recovery has been flashed with TWRP img before attempting 'factory reset' option? I based my questions thus far on the assumption that if it flashed successfully I would see only the 'factory reset' and 'reboot' options in the new recovery, but I see all 5 options as before flashing TWRP.
Click to expand...
Click to collapse
It's been a long time (over a year) since I last used TWRP on my G3 (which is now in the cell phone cemetery as it died last December), but I believe if you boot normally, hook your phone to your PC and use adb reboot-recovery, it SHOULD go straight into TWRP, but I could be wrong. Otherwise, factory reset is the only way to get to it. The normal "recovery" screen shows up first, from what I remember and you have to go that route to get to TWRP. You should always, always back up your phone whenever doing things like this anyways. I don't know if there is a way to "verify" that it is installed, so once again, backup everything first. Just in case.
Thanks for the help and the confirmation that the standard recovery is expected once it's installed. Based on videos I expected something different. But I tried it after backing up and it works fine. Now time to flash!!
So I rooted my device and life was good than I made something a system app and then I deleted it. :facepalm: Next thing I know I reboot and it comes to the unable to test corruption screen and the led light keeps flashing blue. I still have TWRP. Can it be saved?
I have access to fastboot via the bootloader screen. Can I flash from there?
Edit: and I a guess as soon as you start in twrp adp is activated . So I only need the kdz?
You can try the KDZ because that's basically fool proof, but you can also try to manually flash the partition image for the one that's broken. I think that's the system partition in your case.
PleaseHelpMe12 said:
I have access to fastboot via the bootloader screen. Can I flash from there?
Edit: and I a guess as soon as you start in twrp adp is activated . So I only need the kdz?
Click to expand...
Click to collapse
You're best bet would be to put it in download mode and flash the latest kdz using LGUP or uppercut. I've always used the original LGUP but seems like most now use uppercut and seems like uppercut is probably a better choice. You will have to reflash TWRP after you get back up and running and root as well as using the kdz will replace TWRP.
Sweet. It's alive again, but I can't access bootloader via adb reboot bootloader.
Edit: nevermind. I didn't update.
My attempt to root my H930 went very wrong... So I started by unlocking the bootloader and flashing TWRP. After that I didn't manage to get in to TWRP. Instead it started to boot, but froze eventually. Now I can't get it to boot (It gets stuck on initial LG V30 screen), and I can't power it off. I can get into stock recovery (apparently it got far enough to replace TWRP) and download mode with hardware button combinations. But the download mode seems to be different from fastboot mode (looks different on phone, and fastboot can't find it) so I can't try to flash TWRP again. I also managed to get it into a check IMEI + S/N mode by holding all buttons at once...
I've tried flashing H93010f_00_OPEN_EU_OP_0925.kdz with LG UP/Uppercut (since I can get to download mode). It went fine but the situation is the same - no boot, no way to power off.
A factory reset from stock recovery doesn't help either.
Please advice..
Alright, I acually got in to fastboot mode even though I'm not quite sure how.. I basically first went in to download mode, and then pressed vol down + power to reboot, and ended up in fastboot mode. From there I flashed twrp again. And this time I managed to get in to TWRP. Since I didn't have a working ROM I went ahead and wiped all but external sdcard and tried flashing Boombox. It resulted in an "Error: 1"..
So I tried flashing H93010f_00_OPEN_EU_OP_0925.kdz from LGUP again, and now I'm back to a device that doesn't boot again.
Which root are you trying to flash? TWRP also is in alpha at the very best at this point. Can you extract the KDZ and use fastboot to flash the .img files inside, assuming they have .img files inside of the KDZ?
jcsww said:
Which root are you trying to flash? TWRP also is in alpha at the very best at this point. Can you extract the KDZ and use fastboot to flash the .img files inside, assuming they have .img files inside of the KDZ?
Click to expand...
Click to collapse
I'm not trying to flash any root. I was planning on flashing Magisk but never got that far. At this point I'm just trying to get a working phone. I read about extracing img files from kdz but the tool didn't work in my virtual WinXP machine so I'm trying to fire up a Win10 machine now (I'm on mac).
Meanwhile I tried flashing boot and system from "LGH930GAT-00-V10c-222-01-OCT-12-2017+0.zip" but that resulted in the phone automatically booting into TWRP... That can't be good.
egendomligt said:
I'm not trying to flash any root. I was planning on flashing Magisk but never got that far. At this point I'm just trying to get a working phone. I read about extracing img files from kdz but the tool didn't work in my virtual WinXP machine so I'm trying to fire up a Win10 machine now (I'm on mac).
Meanwhile I tried flashing boot and system from "LGH930GAT-00-V10c-222-01-OCT-12-2017+0.zip" but that resulted in the phone automatically booting into TWRP... That can't be good.
Click to expand...
Click to collapse
With some other phones, like Nexus devices. Flashing older boot images can cause bootloops. I don't know if this is the case with your device but it might be something to consider. Have you tried flashing the complete latest factory image to see if that solves the bootloop?
jcsww said:
With some other phones, like Nexus devices. Flashing older boot images can cause bootloops. I don't know if this is the case with your device but it might be something to consider. Have you tried flashing the complete latest factory image to see if that solves the bootloop?
Click to expand...
Click to collapse
Unfortunately I haven't been able to get able to get a hold of a KDZ other than for 10f. I'd like to try 10v.
I got the extraction tool working in a Win10 box now, and I'm trying to extract boot and system images from the 10f KDZ...
egendomligt said:
Unfortunately I haven't been able to get able to get a hold of a KDZ other than for 10f. I'd like to try 10v.
I got the extraction tool working in a Win10 box now, and I'm trying to extract boot and system images from the 10f KDZ...
Click to expand...
Click to collapse
Best of luck!
Nope, that didn't work either. fastboot threw an error telling me the system image was too big for the partition.. At least the system image from the 10c dump fit properly..
So I guess my best bets right now are to either get a hold of a 10v KDZ, or wait for something flashable through TWRP.. :/
Is there like a lastlog for system boot that would be reachable from TWRP/adb..? It would sure be nice to see whats going wrong...
egendomligt said:
Nope, that didn't work either. fastboot threw an error telling me the system image was too big for the partition.. At least the system image from the 10c dump fit properly..
So I guess my best bets right now are to either get a hold of a 10v KDZ, or wait for something flashable through TWRP.. :/
Is there like a lastlog for system boot that would be reachable from TWRP/adb..? It would sure be nice to see whats going wrong...
Click to expand...
Click to collapse
No clue!
Ok, I got it to boot again!
* I formatted data (not wiped) inTWRP - Not sure if this step was relevant
* Flashed stock recovery/boot/system from a KDZ dump called "LGH930GAT-00-V10c-222-01-OCT-12-2017+0" - found the link in some other thread here
* Rebooted and watched it boot - went in to "Android is upgrading..."-screen - rebooted - then booted normally.
Thanks for the help and a special thanks to @Perkash who helped me out through PM.
i've been tinkering with custom ROMs today and in the process i ended up breaking the wifi, so i couldn't proceed with the setup on any custom ROMs i tried to download. i've been attempting to open download mode but it won't open, probably because i wiped everything in TWRP and did not make a backup beforehand which was stupid of me.
have i bricked my device or is there some way to reflash the stock firmware and all of its partitions without the use of LGUP? i read somewhere that you could manually extract bins from the KDZ file and flash each partition one by one via fastboot, and if this is possible i do have all of the BINs with me since i extracted them from the KDZ, but i am not sure how exactly i would go about doing this properly.
thanks in advance