LAF NUKER wipes your Download mode and let you use Fastboot instead.:
Do this on your own responsibility, if you bricked your phone in some weird way then don't look at me.
But with this simple thing you can't brick your phone only if you flashed the wrong zip which wasn't from me.
This is more meant for developers/testers.
Click to expand...
Click to collapse
I was getting irritated that my Fastboot mode dissapeared everytime when I flashed some lollipop stock based rom as those all included bootloader files, so I had to first attempt to get into the rom itself or recovery to wipe it again over and over. So I thought by myself why won't I make something easy and flashable?
This lightweight flashable zip from 2-4KB is tested by me multiple times so after you flashed it I HIGHLYsuggest that you need to test or you can enter download mode and see if it shows now fastboot. If so then everything succeeded like it should, it has an succes rate of 100% as nothing could actually go wrong with this.
This script/method should also work for the G3 and some other LG devices which have this partition:
Code:
/dev/block/platform/msm_sdcc.1/by-name/laf
For the one's who care the shell script is located in the update-binary, updater-script is just dummy.
If you want to revert back, just flash the jb/kk/lp bootloader files.
Download:
https://docs.google.com/uc?authuser=0&id=0B1u3mnq0nstfZVN1eVQ3bEw5ODQ&export=download
Mirror:
https://www.androidfilehost.com/?fid=23991606952610950
Credits:
Jackpotclavin for the method to get into fastboot mode
Chainfire for the shell updater-script method
osm0sis for the guide about the shell updater-script
wulsic said:
LAF NUKER wipes your Download mode and let you use Fastboot instead.:
I was getting irritated that my Fastboot mode disapeared everytime when I flashed some lollipop stock based rom as those all included bootloader files . . . .
Click to expand...
Click to collapse
My question is somewhat off-topic but I'm having a hard time understanding how bootloaders and ROMs work with the G3.
When I had a G2 I learned about the difference between Kitkat and Lollipop bootloaders the hard way when I tried to restore a Kitkat nandroid backup over stock lollipop and hard bricked the phone. My impression was that since the KK backup did not include a compatible bootloader I needed to flash one or restore to stock KK.
Now you are suggesting that ROMs for the G3 *include* bootloaders, which is news to me. Does this mean I can go back and forth between Kitkat and Lollipop ROMs without worrying about bootloaders? Or restore nandroid backups without the same concern? I don't want to have to downgrade to Kitkat every time I want to try a new ROM or restore a backup.
Thanks.
No most roms don't include bootloaders but some stock roms do, especially in the g2 community as I made this first for G2 but I also found out that it would also work on the G3. I guess g3 is the same as the G2 in terms of flashing. Lollipop stock roms need lollipop bootloader related files to properly boot but the bootloader is from kitkat with the g3 because else bump and flashing doesnt work. Only on the g3 tmobile version as that version has an unlocked bootloader. Just read the op's from the threads good and you will know what you need to flash here in the g3 community. But download mode might not always properly work as solution I have this laf nuker so you can flash the good kernel and or recovery if you softbricked your phone. If you hardbrick your G3 you can still fix it as far as I know so don't worry.
wulsic said:
. . . Only on the g3 tmobile version as that version has an unlocked bootloader. Just read the op's from the threads good and you will know what you need to flash here in the g3 community. But download mode might not always properly work as solution I have this laf nuker so you can flash the good kernel and or recovery if you softbricked your phone. If you hardbrick your G3 you can still fix it as far as I know so don't worry.
Click to expand...
Click to collapse
I have the T-Mobile version of the G3. How does that make things different?
It cost me $45 to fix a hard brick on a G2 which I later found out was still under financing with T-Mobile so I returned it. It was an expensive little device.
channeledbymodem said:
I have the T-Mobile version of the G3. How does that make things different?
It cost me $45 to fix a hard brick on a G2 which I later found out was still under financing with T-Mobile so I returned it. It was an expensive little device.
Click to expand...
Click to collapse
Well as far as I know the t mobile version has an unlocked bootloader so more freedom for flashers. I also hard bricked my G2 but before I hard bricked it there was a shortening method guide on how to hard unbrick your g2. Could also work on the g3 perhaps. Well that sucks that you needed to pay $45 lets just hope for you that it won't happen again.
If you want 100% clarification about the bootloader and different roms then you might want to ask it in the Q&A or a rom thread as I am a G2 user. But short story as far as I know. Lollipop bootloader related files for lollipop stock roms. And kitkat bootloader related files for custom aosp roms like euphoria cyanogenmod etc.
I don't know if the guy I paid (who fixed it the day he got it so it couldn't have been so hard for him) had to open it to short the pins but after watching a video showing it done I wasn't going to chance it. It was like repairing a watch. Plus I tried the sw method of viewing the borked partitions in Linux and then replacing them but I couldn't see them to replace so I paid for the repair. And I only had the damn phone for a month before I discovered the problem with T-Mobile and sent it back.
I must say the G2 was a *very* finicky device compared to the Optimus G Pro I had before. And that phone never worked properly with any AOSP ROM. I don't know why I'm so loyal to LG. Must be because the phones are cheaper and I really don't like Samsung any more.
Of course the Verizon Motorola Droid Ultra I bought for my wife used is even worse. It's completely locked down. You can't root Lollipop on it and you can't downgrade to Kitkat once you've taken the OTA update.
Until somebody can explain switching ROMs on the G3 to me like I'm five I think I'm just going to always go back to stock Kitkat, re-root and re-install TWRP. Seems the safest thing to do.
I have rooted many phones before without an issue, and during the root process for this phone, everything was going great, I flashed SuperSU zip in TWRP and rebooted, since it was the first boot I expected a decently long wait, after about 25 minutes I followed the guide's instructions for Verizon since it did say some Verizon users were experiencing long first boot times. I took the battery out like it said, put it back in, then proceeded to fastboot boot2.img, like the guide said. After letting it sit for an hour this time, I got the idea that something was obviously wrong. After multiple attempts with no success I tried to fix it myself. So far I have learned that on the fastboot screen it says my bootloader is locked again, even after unlocking it. I have tried flashing TWRP as a recovery, just to at least have a recovery boot, that does not work either unfortunately. So as of right now, all I have is a v20 that has no OS, a locked bootloader, no way of booting recovery, I can fastboot with no ADB, and its virtually a paperweight. If anyone has a solution to at least get back to Stock, I would greatly appreciate it! Thanks!
First off. It will say: Bootloader Unlocked: No
Thats normal. 2nd. you are not bricked. You have TWRP installed. You just need to redo some steps.
PM me. and I will help you.
Did you get it fixed?
frome901 said:
Did you get it fixed?
Click to expand...
Click to collapse
He has not responded to my pm
What roms can we use with dirty santa root?
me2151 said:
First off. It will say: Bootloader Unlocked: No
Thats normal. 2nd. you are not bricked. You have TWRP installed. You just need to redo some steps.
PM me. and I will help you.
Click to expand...
Click to collapse
Bricked 2 LG V20s this way any help would be appreciated lol what steps do I need to redo...
TheDantee said:
Bricked 2 LG V20s this way any help would be appreciated lol what steps do I need to redo...
Click to expand...
Click to collapse
In his case we needed to redo from step 3.
I managed to un-brick mines after returning sadly from the Sprint store.
First, get to the boot loader screen and try running thru the steps again, especially step 3. You need to make sure you have TWRP.
Use this link to make sure you can get into the different modes (Download mode, fastboot, etc) http://www.hardreset.info/devices/lg/lg-v20/
Once you can get TWRP to show up,then you are good. In the mean time I downloaded "LS997-deODEXd-signed"
When I got into TWRP, I transferred the file to my phone. Rebooted from TWRP back into TWRP and flashed the ROM.
During my reboots, I do get a message saying my phone is corrupt, blah blahblah, but I just wait a few seconds and it will boot up.
Hope this helps.
I had managed to brick mines only 3 hours after upgrading from my Note 4. It took me from 9pm to almost 2am to get it back up again. I can live with the message about my phone being unbootable until someone comes up with a work thru.
Bricked T-Mobile v20
I have rooted many phones before without an issue, and during the root process for this phone, everything was going great, I flashed SuperSU zip in TWRP and rebooted, since it was flash a new rom on it then i get boot loop with TWRP. so i decide to OEM LOCK again after that everything was stuck on my phone just boot loop with LG so any solutions please help me...... THx u for help me.
Kinda nerve wrecking to read about all these "bricked" phones popping up after trying this method lol.. Perhaps I'll just wait until a more tried and true way comes out...
Dirty Santa root is not for the average user who has a couple of experience in rooting.
You have to at least have background on Hard bricking phones to fully understand what you are getting yourself into
For anyone that isnt on sprint that has "bricked" their phone. There are kdz's that will allow you to reflash back to 'stock". Someone had an issue with the kdz, but it was an easy fix. If you failed the process, it can be restored. Just if it doesnt want to boot, just lock and unlock the bootloader...
If your phone doesnt have a kdz, I know TeamDev is working on a custom kdz for such phones. Don't bug him if it isn't finished as I type this.
Anyone that can't get into TWRP, or has failed the process. Either start back at step 3, or if you have TWRP installed but can't get to it, the manual way to get into TWRP is a pain.
Keep your back cover off and hold the volume down button for ease. Now press the power button and as soon as you see an LG logo, let go and repress the power button. Its tricky.... If you get the corrupted screen, pop your battery out and put it back in quick and repress volume down and power. Usually if Im quick enough the first LG logo will hang a lot longer than usual and that gives me time to enter TWRP. A factory reset screen will pop up. Hit Yes twice.
Please help urgent
lcovel said:
I managed to un-brick mines after returning sadly from the Sprint store.
First, get to the boot loader screen and try running thru the steps again, especially step 3. You need to make sure you have TWRP.
Use this link to make sure you can get into the different modes (Download mode, fastboot, etc)
Once you can get TWRP to show up,then you are good. In the mean time I downloaded "LS997-deODEXd-signed"
When I got into TWRP, I transferred the file to my phone. Rebooted from TWRP back into TWRP and flashed the ROM.
During my reboots, I do get a message saying my phone is corrupt, blah blahblah, but I just wait a few seconds and it will boot up.
Hope this helps.
I had managed to brick mines only 3 hours after upgrading from my Note 4. It took me from 9pm to almost 2am to get it back up again. I can live with the message about my phone being unbootable until someone comes up with a work thru.
Click to expand...
Click to collapse
Please can u help ke unbrick mine i bought this mobile in my country its expensive and has no support. I have tried all tools but still getting the error model unknown please help sir
Jaistah said:
Dirty Santa root is not for the average user who has a couple of experience in rooting.
You have to at least have background on Hard bricking phones to fully understand what you are getting yourself into
Click to expand...
Click to collapse
What does that mean? Not for the average user who has a couple of experiences in rooting.
I've only rooted 2 phones, this is my 3rd (maybe 4th). I am on Sprint. Instructions worked fine for me. I did have one hiccup, but it was my fault, and I was able to root just fine. I've been running for a few months now.
I have not flashed any custom ROM yet, I'm going to wait for the next major version of Android to come out. The only mods I've done so far are Titanium Backup install so I can remove Sprint crap.
yuppicide said:
What does that mean? Not for the average user who has a couple of experiences in rooting.
I've only rooted 2 phones, this is my 3rd (maybe 4th). I am on Sprint. Instructions worked fine for me. I did have one hiccup, but it was my fault, and I was able to root just fine. I've been running for a few months now.
I have not flashed any custom ROM yet, I'm going to wait for the next major version of Android to come out. The only mods I've done so far are Titanium Backup install so I can remove Sprint crap.
Click to expand...
Click to collapse
it means dirty santa root got a high posibility rate of bricking a device compared to other root methods for other devices and if you have no experience in bricking phones before then you're screwed if it happens to you
Actually, if you follow the directions, almost none of the problems create a true brick-- which means unrecoverable. For most of the cases, you might get a soft brick, meaning you have to back out, use a KDZ to repair it or reflash something else, or start over from scratch and try again-- but usually (maybe with some help from here) you can pull the phone back into a usable state.
I would hazard to guess for the vast majority the process works fine, maybe with a hiccup, but I've not seen many reports of a truly unrecoverable brick from this method. It's complicated, yes, and you need to be ready to read a LOT to understand what's going on, but it seems pretty difficult to end up with a $700 paperweight with this.
So i have been trying tonroot my sprint lg v20 and everytime i try and go to the phone on mobile terminal to enter id
Then enter the apply patch /system/bin/atd /storage/emulated/0/dirtysanta i get this message and i cant go to step 2 to boot into recovery
Any help would be appreciated: i have a sprint v20 and i wanted to know if i have to flash the stock sprint rom or can i just flash lineage rom following this guide? I have it running on AT&T and i want to keep it on AT&T...
can you please assist
Could you help out, please? I don't believe I have hard bricked my LG V20 H910. However, I have read and tried all of the unbrick info out. It seems my screw up is unique. I completed dirty Santa then went to flash a custom. in the boot between that. I get a black screen and cant do anything even download mode will not come up. My PC does make its usual noises when i connect or disconnect, but my phone does nothing.
Ok, I managed to brick mine too. It's a VS995, it was running stock 1AC. I used the LGUP tool to downgrade it to VS99512A, and then did Dirty Sanata and TWRP. After booting into TWRP I decided to try lineage OS with Android 8.0, I did not make a backup of the Stock ROM, which was very stupid. Lineage OS 15.1 flashed but I had no cell service so I panicked and instead of wiping it in TWRP and using the backup of stock I should have created, I just opened LGUP and tried to downgrade it back to stock VSS99512A. Well LGUP said it worked, but when it went to boot it would hang at the Verizon logo with 4 pastel dots. Device manager could see an ADB device and I could connect to it with ADB. So I did and read the logcat. I could see it was trying to update as part of the rollback, but it appeared that some components from Android 8x could not be "upgraded" to Andoird 7.x. There was a repeated error about failing to update SQLite instance version from 3 to 1.
The one feature that could fix this is if the refurbish function worked with any of the VS995 KDZ files we all have access to. But alas, none work instead we only get the upgrade function... or so I thought. Somewhere in my search for the past 2 weeks I found a modified LGUP https://forum.xda-developers.com/v20/how-to/guide-patch-lgup-to-unlock-features-t3652222
**Please be warned what I did was absolutely ****ing stupid, and it was sheer luck I didn't screw anything up.**
From what I can tell if you only flash ("LGUP Upgrade") the KDZ from the same model it never clears the partition it just adds to it. My problem was there was stuff from lineage OS 15 stuck on one of the partitions that was making the rollback to stock fail because it kept saying it couldn't update the SQLLite DB from 3 to 1. So no "upgrade" within LGUP would work because the upgrade function does not clear internal storage. But the link above is to a version someone modded so you can force a partition update from any KDZ onto the system. So I started playing around with forcing KDZs from other models onto my VS995, and I noticed when using the Partion DL function with non-VS995 KDZ files it would say something about the partition changing. All I can assume is that the partition layout is so different on each model and it forces LGUP to re-partition the storage.
**Again I state for the record this was stupid, and I'm only fortunate it worked.**
I forced Partion DL of H91510d_00_VTR_CA_OP_1110.kdz, then H990N10b_00_OPEN_HK_DS_OP_1017.kdz, then back to VS99512A_06_1114_ARB00.kdz, then when it booted it gave the Verizon hello, and moved on finally but the setting service kept crashing while it was trying to load the Secure Boot screen. So I yanked the battery and went into the boot menu and did the Factory Reset function, and it worked.
Lesson learned, always make a backup and don't be so hasty to use tools that aren't fully functional (LGUP).
Perhaps what I've done may help others, maybe I've found out how to reimage or unbrick our V20s. Or maybe I just got really stupid lucky.
Can i flash this H910PR10j_00_1205 firmware to my AT&T H910? Will it work?
ssgsunny said:
Can i flash this H910PR10j_00_1205 firmware to my AT&T H910? Will it work?
Click to expand...
Click to collapse
We need a link to actually see the file.
me2151 said:
We need a link to actually see the file.
Click to expand...
Click to collapse
https://lg-firmwares.com/lg-h910pr-firmwares/#more-4385
What is it for?
Wouldnt recommend unless you want to test risk it. Its a kdz so format is right but its not for the us region.
This is a nice way to brick.
Cross-flashing radios, and/or bootloaders = GG
me2151 said:
Wouldnt recommend unless you want to test risk it. Its a kdz so format is right but its not for the us region.
Click to expand...
Click to collapse
I tried it and now I am on a island by myself. I got service, made a phone call and got text. It run through about every service possible and then dropped them all!!! It was such a kick in the ballz. Come swim with me the water great!
h910pr
i can confirm i have flashed the h910pr rom to my att h910 and it worked fine for me. stuck on the claro software but its actually better than atts lol. maybe someone could work on this firmware version since we have a kdz of it.
@predheadtx I don't suppose you checked to see if someone was asleep at the wheel and left fastboot oem unlock wide open?
Not sure.
runningnak3d said:
@predheadtx I don't suppose you checked to see if someone was asleep at the wheel and left fastboot oem unlock wide open?
Click to expand...
Click to collapse
I was originally on the h910 att firmware, then used dirty santa to open the bootloader and root. I found a rom that i really like and ran fast as heck, but it wouldn't sync with my watch. I tried a factory reset with led me to a twrp boot loop and nothing i did would get me out of it. so i tried to reflash twrp and it led me to a bricked phone that wouldn't power on past the boot loader unlocked notification. After tons of research and a little tweaking to a few things i got lgup to recognize my phone and flash the h910pr kdz to my phone. if anyone needs i can make a zip of the tools i used and post it somewhere.
edit- uploading to mega right now. will post a link in a little bit to a zip with my lgup folder configured exactly as it needed. install lgup2016 and the lg drivers then copy the lgup from this zip over the lgup folder in your programfiles(x86). essentially all you really need here is the lgup_common.dll which is actually just the h918.dll with the name changed. i had read the fccid's on the h910,h910pr and the h918 were the same, which meant by a measurable standard they are the same hardware. so i took the assumption the dlls would be compatable. by pure blind luck with the folder layout as shown in the zip and the kdz included as well it took. i was a little worried because i had read someone tried this and could not get carrier service. i thought id at least make the phone usable in case a fix was found.my phone reports itself as an h910pr now but is connected to the att network with no issues, text, talk and web all work fine as well as att services.
I had checked a while back and saw that the h910 and h918 had the same FCC ID, which, as you stated, means they have to be the same hardware. I am using my h910 on T-Mobile, so now that I know (if it fails for some reason) that I can flash the h910pr KDZ, I am going to try the h918.
Sorry that you almost had a brick, but thanks so much for verifying that this works.
hi to everyone concerned, i have begun monitoring this thread;
https://forum.xda-developers.com/v20/help/lg-v20-h910-kdz-t3612524/page2#post72599368
please direct any inquiry's to my experience there. there is also a link and directions there to restore any bricked lgh910 to the h910pr version, as well as development on using the h915 and h918 firmware.
I soft bricked my phone a year ago, now I'm trying to bring it back from the dead.
The sticker on the case says that it's an H910 model; purchased refurbished I'm almost certain that the actual hardware is an H996.
In any case, I used LG UP to get a fresh KDZ install of the H915 image onto the phone. Sound, camera , and microphone, honestly I bet there is more there that doesn't work but for now that's all I can name.
I want to unlock the bootloader so this time around instead of using Dirty Santa I'm going the official route.
Problem is that in order to get the Device-ID I need to get into bootloader mode. For now it looks like I'm not able to do that.
Every time I run the
Code:
adb reboot bootloader
command I get the device to only restart.
Any general help is appreciated.:good::laugh:
Not sure where I'm going to go with this phone, honestly I need this thing to be more then a paper weight for me. Literally haven't had a working cellphone in more then a year and it's not working for me. I think I'm just going to keep a stock ROM with root, that's about it.
onedeathbyflame said:
I soft bricked my phone a year ago, now I'm trying to bring it back from the dead.
The sticker on the case says that it's an H910 model; purchased refurbished I'm almost certain that the actual hardware is an H996.
In any case, I used LG UP to get a fresh KDZ install of the H915 image onto the phone. Sound, camera , and microphone, honestly I bet there is more there that doesn't work but for now that's all I can name.
I want to unlock the bootloader so this time around instead of using Dirty Santa I'm going the official route.
Problem is that in order to get the Device-ID I need to get into bootloader mode. For now it looks like I'm not able to do that.
Every time I run the
Code:
adb reboot bootloader
command I get the device to only restart.
Any general help is appreciated.:good:[emoji23]
Not sure where I'm going to go with this phone, honestly I need this thing to be more then a paper weight for me. Literally haven't had a working cellphone in more then a year and it's not working for me. I think I'm just going to keep a stock ROM with root, that's about it.
Click to expand...
Click to collapse
Just follow the H910 root thread your phone will be fine
Sent from my LG-H910 using Tapatalk
So anyone who's rooted knows that the device will take longer to boot than normal. This seems to be largely down the unsecured boot warning screen. I've timed mine to be 30 seconds and I'm just wondering if there's a possibility of fixing this. My LG G5 shows the same screen just for at most 5 seconds.
Firstly would anyone know why this is. It would seem nothing is going on in the background rather there seems to be a timeout function keeping it alive for so long. Does everyone's last 30 seconds and if so is it also the case for the US996 usa version which has an official bootloader unlock method? I'm hoping the official doesn't last as long as it might indicate a workaround is possible.
Any info of your personal experience of this I'd appreciate.
I don't know the exact reason for the delay, so hopefully someone else can weigh in. So far, no one has been able to bypass it; you can only replace the warning image with something else while you wait.
From my observations (I have LS997, US996 USA, and H918 variants), the red triangle warning delay from all the models going through the Dirty Santa procedure is a bit longer, maybe twice as long as the yellow-orange triangle one seen on the US996 USA and H918.
C D said:
I don't know the exact reason for the delay, so hopefully someone else can weigh in. So far, no one has been able to bypass it; you can only replace the warning image with something else while you wait.
From my observations (I have LS997, US996 USA, and H918 variants), the red triangle warning delay from all the models going through the Dirty Santa procedure is a bit longer, maybe twice as long as the yellow-orange triangle one seen on the US996 USA and H918.
Click to expand...
Click to collapse
Been thinking about this again. I'm wondering If I took the aboot.img from an official us996_usa that has been officially unlocked and flashed it on dirty santa device would this make any difference to boot up time? I'm willing to be the guinea pig! It seems to me the hardware is exactly the same anyway and If anything goes wrong I could always restore with lgup patched.
I'm wondering if anyone would be so kind as to dump official unlocked aboot.img and pass it on to me. Preferably the us996 rather than the H918.
There is an app to do this. https://play.google.com/store/apps/details?id=ma.wanam.partitions&hl=en-GB that I've just tested. Select img format rather than the default zipped option.
If anyone could help with this I'd greatly appreciate it. I'm obvious just experimenting here I've no idea if if aboot has anything to do it with. Maybe if it does I'd need to apply unlock.bin too. Or maybe other partitions are involved I don't know. But I like to experiment.
ezzony said:
Been thinking about this again. I'm wondering If I took the aboot.img from an official us996_usa that has been officially unlocked and flashed it on dirty santa device would this make any difference to boot up time? I'm willing to be the guinea pig! It seems to me the hardware is exactly the same anyway and If anything goes wrong I could always restore with lgup patched.
I'm wondering if anyone would be so kind as to dump official unlocked aboot.img and pass it on to me. Preferably the us996 rather than the H918.
There is an app to do this. https://play.google.com/store/apps/details?id=ma.wanam.partitions&hl=en-GB that I've just tested. Select img format rather than the default zipped option.
If anyone could help with this I'd greatly appreciate it. I'm obvious just experimenting here I've no idea if if aboot has anything to do it with. Maybe if it does I'd need to apply unlock.bin too. Or maybe other partitions are involved I don't know. But I like to experiment.
Click to expand...
Click to collapse
Interesting idea. Sure, I'll have a look at my US996 later when I get home.
Update: I've attached it from my US996 USA. Hopefully, I did this correctly as I know nothing about this kind of stuff.