I recently rooted my phone. That worked no problem. I then tried to install CyangenMod through BobZhome ROM's. I can't post the link but it's easily found on google. I tried installing his CM11. I used the CWM file he included and used the app he suggested. I loaded the file on to my SD Card and click on reboot to recovery in the app. My phone said Security Error under the LG symbol as it's booting. I've read many people that have the same problem. But my phone isn't able to do even the basic things they tried. I tried hard resetting it. It showed up with the logo and Security Error. I can't even put my phone into S/W mode. It just loads up the same logo and Security Error screen. I don't know what else to do.
You need to install fastboot and flash the uboot and xloader for your phone model, and whatever version of android your phone shipped with(If you don't remember, use ICS).
http://forum.xda-developers.com/showthread.php?t=2119090
Then once that is finished, you need to download a version of android for your model.
http://forum.xda-developers.com/showthread.php?t=2107971
Finally "Offline flash" the kdz file you downloaded.
http://forum.xda-developers.com/showthread.php?t=2085344
The reason this happened is that you have a locked bootloader, this needs to be unlocked in order to flash custom roms. It is especially hard for this phone.
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've searched through the forums, but haven't found an answer, so I'm starting a new thread.
I received a G Watch as a gift last weekend, and it had a problem on the initial configuration. It wasn't able to connect and download any updates, so I manually flashed the updated firmware. Everything is working fine, and I'm on build LDZ22D. I was able to use G Watch Restore Tools V9 to flash system and recovery (and, in fact, boot, although that didn't seem to do anything), which got my watch up to an earlier version.
I then tried LG G Watch Return to Stock LDZ22D to get to my current build. However, I'm notified that there's an update available, but I'm not able to install it. When I try to install it through the regular user interface, it boots to recovery.
I've tried using the stock recovery, but had no luck with getting anything other than the android with the sore tummy appearing. I've used TWRP to try to flash update.zip (the stock downloaded update) and also tried this image.
When I try to apply update.zip through TWRP recovery, it gives me an error.
E: Error executing updater binary in zip '/cache/update.zip'
Package expects build fingerprint of lge/platina/dory:5.1.1/LDZ22D/19259530:user/release-keys or lge/platina/dory:5.1.1/LCA43/2160025:user/release-keys; this device has lge/cm_dory/dory:4.4.2/KVT9L/561735d166:eng/test-keys
It looks like the release keys are set to a nexus 7 build number (I don't understand how that's even possible). Is there a way to rewrite those keys? I understand they're part of the digital signing process, but I'm not sure why they didn't reset when I used the return to stock tool to flash my current image, which is the actual LDZ22D build. I appear to have a key mismatch. I've tried reflashing boot.img, system.img, and recovery.img manually (the ones included in the return to stock download), but they don't seem to work.
I get the same error when I try to flash the update I downloaded through ADB sideload. I'm frustrated, since my watch gives me this error, then after I reboot, it goes ahead and downloads the update.zip again, killing my cell data plan.
I'd love any help or insight into this. Is there a way to turn off the verification of the keys, or write the actual keys associated with my build? I'm new to working with a watch, and I've got limited experience working with phones/tablets through custom recovery. I'm not interested in a custom rom for my watch - I just wanted to get it to run properly on the stock image, and had a whack at getting it set up through developer options instead of letting it error out when I first got it.
Thanks in advance!
Still working on it
Okay, after quite a bit more research, it appears that my recovery.img doesn't match the rest of the build. I've tried the LDZ22D recovery.img, but it doesn't respond to any user input.
I'm now trying the factory image files from this post.
It seems there are a few people having problems getting to LCA43 recently. If you have an unlocked bootloader by now, you can try this method (TWRP restore from my LCA43 system+boot backup).
Hope this helps.
Hi experts!
Is there an available factory image of the latest firmware for griffin xt1650-03 for download? I unlocked my boot loader and tried to flash custom firmware now I am stuck in boot loop. My phone was nougat and updated via OTA last week before I decided to unlock boot loader. I tried loading the latest image I got from firmware.center but I am getting Downgrade version and verification failed when flashing stock partition and not loader. Please help
Note: I did this my wifi became unusable after my last OTA (mac 02:00:00:00) and thought using custom firmware would help
And I did not make a back up
Get it in fastboot mode, flash TWRP and root it. That might work.
I am in exactly the same position as OP, although I have successfully installed TWRP and have open bootloader from which I can boot into TWRP no probs. I didnt do a backup (will never again make this error!!)
The problem arises when I try to flash (any) files over to device I get the "Downgrade version and verification failed" like OP when flashing stock Telus rom (telus phone) or any other rom/files.
Rebooting brings me back to the moto unlocked bootloader page (horrible!) and the only way out is to get key combo or fastboot into bootloader/recovery etc.
Tried flashing multiple images as whole or bit by bit, always get the same bad validation message. Finding it hard to believe this 700dollar phone is a brick after literally following MotoS own 'unlock your bootloader' instructions. Never had issues like this on OPO, S6, S7, LG etc.
PC shows android device connected, nothing in the two empty folders that appear. TWRP confirms I have no OS installed and throws me back to bootloader.Wondering if locking bootloader again will allow me to install 'stock' ROM or at least recovery? I have reached my android knowledge limit and am not sure where to go from here, any help much appreciated!
OK. This happened to me. The way that I solved it was by flashing the RETUS NPL86.25.15 and then flashing the OTA 25.17-3-3 through twrp. Although I think I could've saved the headache if the original instructions included flashing the OEM.bin but anyways. That's what I did. Hope it helps.
Thanks. I did try flashing the oem.bin but got partition name error.
Can you link to the files you mention I think it's a kernel and then an OTA image? Thanks again in advance.
What I mean is that when I first started flashing the RETUS rom the instructions skipped that part so I ended up flashing most of the file system without something so it would never boot but it wouldn't loop it'd just hang. So basically you flash everything and then include the OEM.bin after you do the system chunks
I have the T mobile H901 Like just about everyone else. I got it with android 6.0 and I wanted to root it. Now i didn't really know what to do, so I tried following some guides on here. I got my bootloader unlocked, but TWRP would not install, and I kept getting some "unknown command" error. So I installed this via LGUP: https://forum.xda-developers.com/tmobile-lg-v10/general/root-android-6-0-h901-t3382819
That gave me twrp, but I could no longer boot into system. From there I tried installing stock 6.0 .zip files, Installing .kdz files through LGUP, but nothing was working.
So then I tried this thread: https://forum.xda-developers.com/tmobile-lg-v10/development/rom-v10h901v20estock-customized-t3360240
I installed the V10_H901_V20L_Update_P1.zip, then the V10_H901_V20J_Stock_Custom_2e_FULL-signed.zip both though TWRP 3.0, and followed the rest of the instructions until I got to: "Once in Fastboot type this command "fastboot oem unlock"" BUT my phone already WAS unlocked. So I (not really thinking) typed "fastboot oem lock" and then it said "erasing data" like it was supposed to. But after that, I can do longer get into my recovery, Boot to system, and If I don't enter fastboot OR download mode, It stays in a bootloop where it says: "boot verification fail!! - Cause : MISMATCH_SIG_LEN
Please if anyone could help I would be so happy.
EDIT: I should also mention that when I try and flash the stock 6.0 rom with LGUP (The "H90120e_00_0316") It gets to 9% and fails with the error: Error Code - 0x2000, TOT antirollback version is smaller than device version.
OK I fixed my phone by using LG Bridge firmware update while my phone was in download mode. The only problem is NOW I can't root. I hope someone can get a Nougat root working.
BuildMineSurvive said:
OK I fixed my phone by using LG Bridge firmware update while my phone was in download mode. The only problem is NOW I can't root. I hope someone can get a Nougat root working.
Click to expand...
Click to collapse
Working with some Korean friends on that now. No promises but early testing is progressing well. Hopefully it works for 20 & possibly 30
After successfully unlocking my device's bootloader, rooting and installing TWRP - by following this guide - I decided to flash LineageOS14.1 - or at least attempt to. I didn't flash the no-verity-opt-encrypt.zip file, but everything seemed to be working OK, until I booted into LineageOS, where it demanded a password I've got no damn idea about (nor do I remember ever setting - hell, I had just disabled the secure startup option). Since I could actually browse my SD card, I tried rebooting into recovery, which didn't help, as did my attempt at flashing no-verity-opt-encrypt.zip regardless if I selected to keep the system write only (I assume because the DRM thing already got triggered?).
I then attempted to flash a KDZ file (it was either H85020D or H85020A from here) which gave me an error (I don't remember the exact code - I'll update later). And so I managed to get myself stuck on download mode. Pulling the battery doesn't help, Every time I try to use LGUP it comes back with the same error. I tried reflashing twrp and unlock.bin but I still can't get past download mode.
Garfoth said:
After successfully unlocking my device's bootloader, rooting and installing TWRP - by following this guide - I decided to flash LineageOS14.1 - or at least attempt to. I didn't flash the no-verity-opt-encrypt.zip file, but everything seemed to be working OK, until I booted into LineageOS, where it demanded a password I've got no damn idea about (nor do I remember ever setting - hell, I had just disabled the secure startup option). Since I could actually browse my SD card, I tried rebooting into recovery, which didn't help, as did my attempt at flashing no-verity-opt-encrypt.zip regardless if I selected to keep the system write only (I assume because the DRM thing already got triggered?).
I then attempted to flash a KDZ file (it was either H85020D or H85020A from here) which gave me an error (I don't remember the exact code - I'll update later). And so I managed to get myself stuck on download mode. Pulling the battery doesn't help, Every time I try to use LGUP it comes back with the same error. I tried reflashing twrp and unlock.bin but I still can't get past download mode.
Click to expand...
Click to collapse
If you can get into TWRP still, I would try wiping the system and data. Then instead of LGUP, use uppercut (I'll link you to that if you need me to) to flash a KDZ to go back to stock