xdadev won't let me post this in lg g pad 7.0 forums (too new) so have to post here. Maybe similar on g pad 8.3
I created a custom boot.img (small edit, replaced /sbin/chargerlogo with /system/bin/reboot with Android Kitchen), but whenever I try to flash the boot.img (with Rashr, after correcting the permissions) and reboot, it sticks on the LG logo and there is an error at the top ("Error: boot verification failed"). Same issue using cofface's unpack/repacker for kernel.
I noticed the boot.img I create using any method is always less than half the file size of the stock image boot.img. Something isn't adding up, anyone know possible why?
I can boot up to TWRP and restore the boot, but anyone have a suggestion on why the boot.img might not be working?
Maybe I have to unlock the bootloader? Anyone know how to do that on this device?
I'm not sure I'm even asking the right questions here, any lead is greatly appreciated!
same exact thing
roleyus said:
xdadev won't let me post this in lg g pad 7.0 forums (too new) so have to post here. Maybe similar on g pad 8.3
I created a custom boot.img (small edit, replaced /sbin/chargerlogo with /system/bin/reboot with Android Kitchen), but whenever I try to flash the boot.img (with Rashr, after correcting the permissions) and reboot, it sticks on the LG logo and there is an error at the top ("Error: boot verification failed"). Same issue using cofface's unpack/repacker for kernel.
I noticed the boot.img I create using any method is always less than half the file size of the stock image boot.img. Something isn't adding up, anyone know possible why?
I can boot up to TWRP and restore the boot, but anyone have a suggestion on why the boot.img might not be working?
Maybe I have to unlock the bootloader? Anyone know how to do that on this device?
I'm not sure I'm even asking the right questions here, any lead is greatly appreciated!
Click to expand...
Click to collapse
i also have an lg glad 7.0 att v410 running 5.0.2 the only was i could root it was if i used root king and that was all i could do. I'm despretly trying to unlock the boot loader for days now and no success. SAME THING ERROR BOOT CERTIFICATION VERIFY. I DID FIND THAT IF I USE THE TWRP 2.8.5.0 FOR V400 NOT V410 FLASH TO RCOVORY VIA FLASHILY AND WHENI REBOOT ITS IN FASTBOOT MODE. SO I THINK THATS THE 1ST STEP IN ULOCKING THE BOOTLOADER NOT SURE THOUGHT I NEED HELP TO NAD NO ONE ON THE INTERNET KNOWS. sorry i guess i hit caps lol
Maybe you can help
Im probably digging in a graveyard here but i accidently flashed my boot instead of recovery in twrp. Well now im screwed i can still get into twrp with full functionality however i need the original boot.img or a boot.img that will boot up my Tablet. I have an Lg Gpad 7.0 LTE V410 but im assuming i need a new boot file to flash as i have screwed mine up. But please any help will be so appreciated as i can not do anything without it. I can get to twrp without an issue and download mode without an issue. Thank you in advance
Same here
Did you find a way to solve it?
Related
Please don't refer me to any more threads or forums........
I'm sure this has been done and done and talked about but I've been reading the **** out of forums and comments for a few hours now and trying to unroot my Sprint LG G2.
I had it running stock like a champ. rooted it. worked great. then I was attempting to flash lollipop and it required a recovery update (No Problem) I downloaded the correct files and bam! it says your phone is not rooted this requires a root (or something like that) I was already rooted SuperSU installed and root checker said I was fine. so what the hell I swipe to root while inside recovery and it goes to some black screen with tiny text saying fastboot: processing commands and won't leave the screen. I tried booting into recovery and same thing happens. Tried to reboot normal and I'm stuck on the LG logo with my led flashing between blue and green slowly. I CAN boot into download mode and I'm following this
http://pastebin.com/WTm1xFXz
and this
http://forum.xda-developers.com/showthread.php?t=2687929
to unbrick but having this error "Failed PreviousLoad()
Did I not get the right .dll file? I doubt it cause I only saw one...or is it the wrong .tot file? there was 3 or so
http://downloads.codefi.re/autoprime/LG/LG_G2/LS980/Stock_Firmware
Please help!
When i'm in download mode the phone does say I am rooted. is there a way to just re-flash recovery and restore from my backups I did before all this? if I have to wipe this thing clean and start over I don't really mind I just need to get my phone back haha this is the first time this has ever happened to me and I consider myself tech savvy so idk what I did here (except re rooting in recovery like an idiot) thanks so much!
First question, is the download mode you see with a small status bar or the big one?
If you have the big one, download mode should work. The f flash software will verify the tot file. If that goes through you should be golden.
When it asked you in TWRP to root, that is a message telling you system or ROM file did not take.
If you want cm12, use zv8 tot. Root, auto-rec, update TWRP with blastgator bumped TWRP 2.5.1. Flash cm ROM or aosp, then gapps. And go
Some questions about right way to get the Root for lg g pad 10.1 v700 ? & twrp & etc
hi
How to The right way to get the Root for lg g pad 10.1 v700 ?
How to reset the counter ? Maintaining the guarantee ؟
How to Recovery of the original system and Recover After install cyanogenmod and TWRP ؟
I'm sorry, I'm new in dealing with pad please help
this is my first look at this page about the V700. I'm messing with it today. I'm in the same boat as you.
I tried both LG one click, GUI and script. both follow through to completion but do not root. I will spend the day with it and see whats up.
Admittedly I have not read much yet, but I will.
LG Electronics E10 LGV700 10.1-Inch Tablet
yazan.om said:
hi
How to The right way to get the Root for lg g pad 10.1 v700 ?
How to reset the counter ? Maintaining the guarantee ؟
How to Recovery of the original system and Recover After install cyanogenmod and TWRP ؟
I'm sorry, I'm new in dealing with pad please help
Click to expand...
Click to collapse
to root try kingroot, another option would be to use lg flash tools (to enter in download mode while holding volume up connect it via usb to ur pc), flash KK kdz and root using towelroot.
there is a recovery, TWRP but only works on KK from what i understand.
cyanogenmod isnt available for it.
to go back to stock even with no flags saying u where rooted, just flash a kdz either KK or L (ur choice) and factory reset after.
C4SCA said:
to root try kingroot, another option would be to use lg flash tools (to enter in download mode while holding volume up connect it via usb to ur pc), flash KK kdz and root using towelroot.
there is a recovery, TWRP but only works on KK from what i understand.
cyanogenmod isnt available for it.
to go back to stock even with no flags saying u where rooted, just flash a kdz either KK or L (ur choice) and factory reset after.
Click to expand...
Click to collapse
thank you so much
Is it possible to reset the system counter to restore the waranty? and how ?
thank you for help me
yazan.om said:
thank you so much
Is it possible to reset the system counter to restore the waranty? and how ?
thank you for help me
Click to expand...
Click to collapse
Flashing a kdz via lgflash tools will reset the counter. U can check by going to download mode and it WONT say rooted in red
C4SCA said:
Flashing a kdz via lgflash tools will reset the counter. U can check by going to download mode and it WONT say rooted in red
Click to expand...
Click to collapse
Hi, not sure if this thread is the right place to post this, since device is: VK70023A B14.LGE.VK700.0 LG-Gpad 10.1" VK700.0 Lollipop 5.0.2, but rather than start another thread
I'll post it here and hope someone's looking! I'm trying to inject root using this method, so far I've managed to get a copy of the system image, root it, and push it back to the device no problem, lol well, more or less, no problem, but it took a bit of help . The method's for a G4, but I'm pretty sure it'll work for this one too, the last OTA unfortunately broke all the current root methods, tried all of the above and more and, nothing, so in desperation I figured I'd give the G4 method a shot (it's my own image so how bad could it be?). The problem I'm having now is that (and correct me if I'm wrong here, this is my first attempt at flashing this, or any, tablet), when I go back to Windows and run (from Send_Command.exe in download mode):
Code:
#/system/bin/toolbox dd if=/data/media/0/Download/rootedsystem.img bs=8192 seek=40960 count=351232 of=/dev/block/mmcblk0p32
#LEAVE
...the download progress goes to 100% immediately, (the dd params are correct for this tab) but the device just boots normal (shouldn't it be loading 'rootedsystem.img'? Would lgflash tools help here?), I've tried it with and without "seek" and "count" with same result, is there something else I need to be doing to get it to load? The person helping me (even adjusted the 'autoroot.sh' script to work with this device) in that thread doesn't have this device so can only go so far in helping if there's something totally different about the 10.1 that needs to be done. Hopefully that's enough info to go on, everything I've done so far is in that G4 thread but I can consolidate it all and post it here if need be, just let me know, at any rate, if I'm successful I'll probably make a thread with all that in it anyway in case anyone else is having the same problem, tho I don't see many with this model (not sure why). Any help's appreciated!
Thanks in advance
Is there a reason there is no development of this device? CM would be excellent.
I have been running in circles on rooting my LG gpad 7.0 and with a lot of trial and error. With that said, I came across the error : boot certification verify. and that's it. Wont load or go further than that. I think I broke my device, any thoughts or help?
Nocookiepuffs4u said:
I have been running in circles on rooting my LG gpad 7.0 and with a lot of trial and error. With that said, I came across the error : boot certification verify. and that's it. Wont load or go further than that. I think I broke my device, any thoughts or help?
Click to expand...
Click to collapse
That's the error you get when you try to boot with an unsiged boot image. I've gotten out of that by using cybojenix openbump script to sign boot images (only works for kitkat bootloader), and using TWRP flash a ROM with a bumped boot image or just restoring a working backup. However, since you're just getting rooted I'm guessing you don't have TWRP installed (if you do, fixing this would be way easier).
If you're on the lollipop generation bootloader and don't have TWRP, the only option I can think of is to use the kitkat kdz to reset your tablet. It sounds like a really long and involved process to get the internal storage back to normal following using it. Good luck.
I have a LG G3 US990. For the life of me I can not figure out how to get rid of that error. The phone boots fine after about a minute on the LG screen, with that error in the top left corner, but I would like to get rid of it, so the phone actually boots like normal. Any help would be greatly appreciated. I'm using CyanogenMod version 13, Android 6.0.1.
dang I have the same error on a d850, never figured out how to fix it, even tried the Mr_Bump zip file after a kernel flash, still no go
Secure booting error 1003 going to TWRP...
Hi! I'm having a similar issue. I successfully (I think!) rooted my Sprint LG G3 LS990 and installed TWRP 3.0.2-0. However, everytime to reboot to recovery, the "Secure booting error! Error code 1003" appears in the upper left corner for a few seconds, before booting into TWRP.
I want to flash to a custom ROM but am afraid to until I know whether I need to worry about the error or just ignore it. HELP???
Clem
cpatafio said:
Hi! I'm having a similar issue. I successfully (I think!) rooted my Sprint LG G3 LS990 and installed TWRP 3.0.2-0. However, everytime to reboot to recovery, the "Secure booting error! Error code 1003" appears in the upper left corner for a few seconds, before booting into TWRP.
I want to flash to a custom ROM but am afraid to until I know whether I need to worry about the error or just ignore it. HELP???
Clem
Click to expand...
Click to collapse
Hi Clem,
Same problem here. Did you ever figure it out?
Thanks.
Mechif said:
Hi Clem,
Same problem here. Did you ever figure it out?
Thanks.
Click to expand...
Click to collapse
Far as I know one needs to flash MR_bump to fix that error. You can download it from the first post in this thread...
https://forum.xda-developers.com/showthread.php?t=3813552
[RECOVERY][3.3.1][UNOFFICIAL] TWRP for LG G3
Moto G5s Plus XT1806, OmniROM 8.1.0, NanoDroid, MultiROM, XDA Legacy
marcdw said:
Far as I know one needs to flash MR_bump to fix that error. You can download it from the first post in this thread...
https://forum.xda-developers.com/showthread.php?t=3813552
[RECOVERY][3.3.1][UNOFFICIAL] TWRP for LG G3
Moto G5s Plus XT1806, OmniROM 8.1.0, NanoDroid, MultiROM, XDA Legacy
Click to expand...
Click to collapse
Thanks Marc.
I download and try installing bump from mega as you recommended. I then go to twrp recovery boot and install but it stops like when I try the install for cloudy. I am not wiping anything though before installing bump. Am I supposed to wipe the system etc prior to installing bump?
I also try to flash bump via the flashify app, it reboots into twrp recovery, says it’s finished but quickly it reboots into the lg logo and boots up the system normally. Where or how do I know if bump was installed? The secure boot error message stills exists.
The link you included also says the zip for the LS990 that I used through twrp app isn’t any good and there was a new zip file released in June 2019. I downloaded from mega and flashed through the twrp app. How do I know if actually updated the twrp recovery to this new flash?
Thank you.
---------- Post added at 05:54 PM ---------- Previous post was at 05:51 PM ----------
I’m thinking the boot loader isn’t unlocked and the bump isn’t loading properly. Maybe this is why the cloudy rom doesn’t flash. Too bad the phone companies make so many damn versions causing confusion for everyone.
Howdy all, hadn't done rooting/etc in a long time as my past several phones didn't have much support for them but got the LG G8 and was excited to possibly root it and also install a custom rom. Went with Arrow OS which seemed to run fine and I decided I wanted to get TWRP as a custom recovery instead of the one that comes with ARROW OS. I flashed it but now it get stuck on fastboot and constantly loops to it (and no longer shows the boot a/b.... which probably isn't a good sign). After leaving it alone for some time, I booted it up and now it gets beyond the the fastboot loop but I can either try to boot it up which only gets me the code red warning or go to download mode. I tried to use LG Bridge and download mode on my phone but the Bridge software doesn't detect the phone.
I realize some of this is probably because of my stupidity and I should've been more careful but anyone got any ideas on what could be done to get the phone back to a stable working state so that it can function again? I know there are some more "difficulties" because of the boot a/b partitions and having to handle that stuff properly. If it isn't possible, that sucks I guess but anyone who wants to chime in - thank you for your help!
JuSkoch said:
Howdy all, hadn't done rooting/etc in a long time as my past several phones didn't have much support for them but got the LG G8 and was excited to possibly root it and also install a custom rom. Went with Arrow OS which seemed to run fine and I decided I wanted to get TWRP as a custom recovery instead of the one that comes with ARROW OS. I flashed it but now it get stuck on fastboot and constantly loops to it (and no longer shows the boot a/b.... which probably isn't a good sign). After leaving it alone for some time, I booted it up and now it gets beyond the the fastboot loop but I can either try to boot it up which only gets me the code red warning or go to download mode. I tried to use LG Bridge and download mode on my phone but the Bridge software doesn't detect the phone.
I realize some of this is probably because of my stupidity and I should've been more careful but anyone got any ideas on what could be done to get the phone back to a stable working state so that it can function again? I know there are some more "difficulties" because of the boot a/b partitions and having to handle that stuff properly. If it isn't possible, that sucks I guess but anyone who wants to chime in - thank you for your help!
Click to expand...
Click to collapse
Sounds like you might just need to reverse what you did to try to get twrp. If you have the boot partition for Arrow flash that back, if you don't have it should be pretty easy to get it from someone.
If that doesn't work can always use qfil and flash the necessary partitions to get LGUP to work, then flash or crossflash to a kdz and start again with stock.
You're in good company. I went down the same path and have become adept at repeatedly bricking and un-bricking my G8. (LM-G820QM5) I picked up 2 tidbits of info that have been helpful. The first is that my G8 ThinQ will not boot Android when the engineering abl_a.bin has been flashed on to it to enable fastboot. Sure it will fastboot, and go into EDL or download mode, but in order to boot the OS, I have to put the normal abl_a.bin and abl_b.bin back.
The second lesson I learned the hard way is that sometime LGUP fails to flash when the phone is in download mode. I was searching around XDA and came across a very helpful post from starlyn1232. They posted a command line utility that has been successful in un-bricking my G8 when LGUP failed.
I downloaded the appropriate kdz from lg-firmwares.com and the starlyn1232's utility from https://forum.xda-developers.com/t/lgup-flash-utility-based-on-lgup-1-16-cmd-and-lgup-1-17-lgup_common-dll.4112121/
Well thankfully, i still had the original files from the unlocking thread in this forum and I also apparently did make a backup of my files right before I installed TWRP 3.4 or whatever and was able to get my phone working again - which is awesome! Also, what's the best way to back up everything on the phone (or at least the essentials) in case of flashing situations like this? I in the past would just use TWRP to do a backup/restore but since I flashed ARROWOS and it has its own recovery and doesn't seem to have a backup option - asking if any one has a recommendation. Thanks!
JuSkoch said:
Well thankfully, i still had the original files from the unlocking thread in this forum and I also apparently did make a backup of my files right before I installed TWRP 3.4 or whatever and was able to get my phone working again - which is awesome! Also, what's the best way to back up everything on the phone (or at least the essentials) in case of flashing situations like this? I in the past would just use TWRP to do a backup/restore but since I flashed ARROWOS and it has its own recovery and doesn't seem to have a backup option - asking if any one has a recommendation. Thanks!
Click to expand...
Click to collapse
I would highly recommend looking at bkerler edl utilities. You can easily find his git page which has the download option for an iso linux boot which has everything installed.
It's a bit involved / complicated figuring out the command line interface, but once done you can backup everything and it will create the xml files needed to reload it.
I would suggest this for everyone but especially for those with sprint or att devices, as there is no kdz available for them.
I've recovered from various issues too many times to count with backups I've made for v40, v35, and now G8 (2 of them).
cheers
Could you pass the tutorial on how to install TWRP?
Does anyone have rawprogram0.xml
Patch0.xml for lg g8
Ashfaq Ahmed spsc said:
Does anyone have rawprogram0.xml
Patch0.xml for lg g8
Click to expand...
Click to collapse
So the rawprogram xml will be for ea lun, and it will vary by which rom you're trying to flash, it will also vary by segment starting positions for the partitions. IE, there is no generic version of it.
2nd, you don't need a patch xml, just click cancel or skip for that entry. Note; the rawprogram xml is usually generated when a backup of the binaries is made, and it will be for that specific backup.
Hello there sorry to pop in unannounced I would like to interject briefly and please pardon my ignorance I'm still a noob.
I have a similar issue, but I'm a little bit confused as to what I should do. In my Case i have a SOFT brick.
(G8 ThinQ VERIZON LM-G820UM (Model) ---- G820UM20j (Software)).
I unlocked the bootloader and rooted with magisk successfully, Still running STOCK OS
Then I Flashed TWRP.zip and some version of Magisk.zip with the magisk app, Then I Rebooted to Recovery.
Inside TWRP i Wiped, Format and then I flashed Disable_Dm-Verity_ForceEncrypt_03.04.2020.zip
This process Finished without any errors, however, after I rebooted i now cannot go past the Verizon Logo and it's stuck there.
Fortunately, I have All the Original files backed up (abl_a.bin, abl_b.bin, boot_a.bin, boot_b.bin)
And TWRP also managed to create a Backup beforehand.
I can go easily into EDL mode and i also have the engineering abl_a file on hand.
i can also get to the built-in Stock factory reset / safe mode but I'm unsure if I should use it.
So my question is if i would be correct in loading ALL of the original Files using QFIL, or only the boot_a boot_b files ?
or if i should do something else like getting the firmware in my case?
thank you for your time in advance.
MR_ZenR0 said:
Hello there sorry to pop in unannounced I would like to interject briefly and please pardon my ignorance I'm still a noob.
I have a similar issue, but I'm a little bit confused as to what I should do. In my Case i have a SOFT brick.
(G8 ThinQ VERIZON LM-G820UM (Model) ---- G820UM20j (Software)).
I unlocked the bootloader and rooted with magisk successfully, Still running STOCK OS
Then I Flashed TWRP.zip and some version of Magisk.zip with the magisk app, Then I Rebooted to Recovery.
Inside TWRP i Wiped, Format and then I flashed Disable_Dm-Verity_ForceEncrypt_03.04.2020.zip
This process Finished without any errors, however, after I rebooted i now cannot go past the Verizon Logo and it's stuck there.
Fortunately, I have All the Original files backed up (abl_a.bin, abl_b.bin, boot_a.bin, boot_b.bin)
And TWRP also managed to create a Backup beforehand.
I can go easily into EDL mode and i also have the engineering abl_a file on hand.
i can also get to the built-in Stock factory reset / safe mode but I'm unsure if I should use it.
So my question is if i would be correct in loading ALL of the original Files using QFIL, or only the boot_a boot_b files ?
or if i should do something else like getting the firmware in my case?
thank you for your time in advance.
Click to expand...
Click to collapse
Hello, I Managed to Fix it by loading my backed-up original boot_a.bin and boot_b.bin using QFIL, I have successfully passed that Verizon logo now and should be able to go from here, not that anybody asked, I just thought someone in the future might have some use out of this information here. so if you are from the future and you read this, you are welcome and good luck