Database Develop

[ODIN][N8013] Prerooted UEALH2 Firmware Package

This post contains a complete firmware update package for N8013 UEALH2. It is based off the Kies images dumped by http://forum.xda-developers.com/showthread.php?t=1847706
It was rooted and the system image rebuilt using the guide at http://forum.xda-developers.com/showthread.php?t=1081239 - FYI partition size for N8013 is 1400M
The package is at http://d-h.st/8v0
This will give you a complete restore to stock UEALH2 plus root, without triggering the flash counter.
By complete, I mean EVERYTHING: Kernel, recovery, system, hidden/preload, cache will be returned to the same configuration as if you flashed UEALH2 via KIES - the only difference is root.
Use Odin to flash it.

Entropy will this my issues? Can you go take a look at my help thread and general and look at my picture of my download mode saying custom?
Sent from a Baked Black Jelly Belly

Entropy, will this work on my note even though i'm already running UEALH2? Got my update OTA last night before I had a chance to root it.
Also, if I'm able to use this and I root my device should I be wary about OTA in the future causing device malfunctions? In other words, what kind of update path should I follow in the future?
Sorry for the newb question. New to Samsung. Used to rooting and flashing and updating my old droid 2 global. Never did anything with my prime before I exchanged it for this and haven't done anything with my RAZR yet. I've kind of been flash cracker dormant for a while.
Sent from my GT-N8013 using xda premium

davidrules7778 said:
Entropy will this my issues? Can you go take a look at my help thread and general and look at my picture of my download mode saying custom?
Sent from a Baked Black Jelly Belly
Click to expand...
Click to collapse
Probably, however to reset DL mode to not be custom you'll need my TriangleAway support kernel (for now - Chainfire is going to integrate support into his app by including a compatible kernel for temp-flashing to reset). Flash it, run TA, then flash this and you should be on bone-stock except root.
BTW, this is a COMPLETE package including stock kernel and recovery. Once Mobile Odin supports this device (I gave Chainfire the info he needs to support N80xx) you can flash CWM and any kernel you want from rooted stock like this.
As to OTAs - In the past, many OTAs could be deployed safely to rooted devices as long as you weren't using CWM. However, Samsung seems to have switched to special incremental OTAs that patch the current binaries, so if even one of them is modified in any way, the update will fail. Happened to a lot of users with the last OTA.
Eventually you'll probably see custom firmwares that are deodexed and have the update-related APKs removed so you won't get OTAs.

OK so flash the kernel via Odin ? I am on the old injected rooted tar will it be ok?
Sent from a Baked Black Jelly Belly
---------- Post added at 04:20 PM ---------- Previous post was at 04:20 PM ----------
davidrules7778 said:
OK so flash the kernel via Odin ? I am on the old injected rooted tar will it be ok?
Then flash this?
Sent from a Baked Black Jelly Belly
Click to expand...
Click to collapse
Sent from a Baked Black Jelly Belly

Another newb question... will this wipe my data? And where can I download Odin for this device? Thanks
Sent from my GT-N8013 using xda premium

I hope it wipes my data and system! I feel like I need a wipe to get my pen working!!
Sent from a Baked Black Jelly Belly

Entropy512 said:
Probably, however to reset DL mode to not be custom you'll need my TriangleAway support kernel (for now - Chainfire is going to integrate support into his app by including a compatible kernel for temp-flashing to reset). Flash it, run TA, then flash this and you should be on bone-stock except root.
BTW, this is a COMPLETE package including stock kernel and recovery. Once Mobile Odin supports this device (I gave Chainfire the info he needs to support N80xx) you can flash CWM and any kernel you want from rooted stock like this.
As to OTAs - In the past, many OTAs could be deployed safely to rooted devices as long as you weren't using CWM. However, Samsung seems to have switched to special incremental OTAs that patch the current binaries, so if even one of them is modified in any way, the update will fail. Happened to a lot of users with the last OTA.
Eventually you'll probably see custom firmwares that are deodexed and have the update-related APKs removed so you won't get OTAs.
Click to expand...
Click to collapse
Hmm, if this fixes the S Pen on my tablet I'll be pleasantly surprised. If it's based on the image from jaaka, and ODINing that didn't fix the S Pen for me, would this be any different? I have the same issue as David, tried to root after taking the OTA and after installing CWM and rooting the S Pen stopped working. I've flashed the root injected stock image from zedo multiple times to no avail, and also the UEALH2 one from jaaka, as well as trying to update via Kies after installing the root injected stock image. Formatted data/cache and system too once, although flashing in ODIN should overwrite system completely, right?
Also, can we flash this in Heimdall? Or would you recommend against that?

iofthestorm said:
Hmm, if this fixes the S Pen on my tablet I'll be pleasantly surprised. If it's based on the image from jaaka, and ODINing that didn't fix the S Pen for me, would this be any different? I have the same issue as David, tried to root after taking the OTA and after installing CWM and rooting the S Pen stopped working. I've flashed the root injected stock image from zedo multiple times to no avail, and also the UEALH2 one from jaaka, as well as trying to update via Kies after installing the root injected stock image. Formatted data/cache and system too once, although flashing in ODIN should overwrite system completely, right?
Also, can we flash this in Heimdall? Or would you recommend against that?
Click to expand...
Click to collapse
I had weird issues when flashing with heimdall.
Try flashing this, wiping with STOCK recovery, and don't **** around with CWM until you're sure it's working.
Warning: I believe stock recovery is a full 100% wipe, including /sdcard (which is actually /data/media) - CWM takes measure to protect /data/media that might result in unclean wipes sometimes. This is why pershoot would always tell people to wipe in stock recovery if they had problems for example.

Entropy512 said:
I had weird issues when flashing with heimdall.
Try flashing this, wiping with STOCK recovery, and don't **** around with CWM until you're sure it's working.
Warning: I believe stock recovery is a full 100% wipe, including /sdcard (which is actually /data/media) - CWM takes measure to protect /data/media that might result in unclean wipes sometimes. This is why pershoot would always tell people to wipe in stock recovery if they had problems for example.
Click to expand...
Click to collapse
Wipe in stock recovery 1st? Also when I am on the rooted old firmware, the recovery reboot option doesn't work for me I have to old down power to reboot
Sent from a Baked Black Jelly Belly

Entropy512 said:
I had weird issues when flashing with heimdall.
Try flashing this, wiping with STOCK recovery, and don't **** around with CWM until you're sure it's working.
Warning: I believe stock recovery is a full 100% wipe, including /sdcard (which is actually /data/media) - CWM takes measure to protect /data/media that might result in unclean wipes sometimes. This is why pershoot would always tell people to wipe in stock recovery if they had problems for example.
Click to expand...
Click to collapse
Alright, will do that then. Still waiting for it to finish downloading, seems like dev-host is not that fast unfortunately (or maybe I'm just spoiled by university internet and 4G). I did wipe with stock recovery once during my couple hours of trying to fix my tablet and it didn't seem to help. I probably won't try flashing CWM or rooting again for a while until I can get confirmation from others that it doesn't break the S Pen again. The thing I wanted to try (Screencast) worked but was somewhat unimpressive in terms of quality so I don't need to show it to the person I wanted to show it to (plus without S Pen it's less useful for my specific use case).

iofthestorm said:
Alright, will do that then. Still waiting for it to finish downloading, seems like dev-host is not that fast unfortunately (or maybe I'm just spoiled by university internet and 4G). I did wipe with stock recovery once during my couple hours of trying to fix my tablet and it didn't seem to help. I probably won't try flashing CWM or rooting again for a while until I can get confirmation from others that it doesn't break the S Pen again. The thing I wanted to try (Screencast) worked but was somewhat unimpressive in terms of quality so I don't need to show it to the person I wanted to show it to (plus without S Pen it's less useful for my specific use case).
Click to expand...
Click to collapse
i know it is slow, we need a torrent LOL or on that other site that the other firmware was on,
Entropy do u mind if i mirror it on another site like the previous one? I have a pretty fast upload stream

davidrules7778 said:
i know it is slow, we need a torrent LOL or on that other site that the other firmware was on,
Entropy do u mind if i mirror it on another site like the previous one? I have a pretty fast upload stream
Click to expand...
Click to collapse
Do you have the whole thing downloaded? My download died at about 70% . Trying to download it from an EC2 instance now too, I'll see what happens I guess.

iofthestorm said:
Do you have the whole thing downloaded? My download died at about 70% . Trying to download it from an EC2 instance now too, I'll see what happens I guess.
Click to expand...
Click to collapse
I just started downloading it lol
Sent from a Baked Black Jelly Belly

Looking forward to trying this. Getting the same issue on downloading though. First attempt showed finished, but was corrupt when I tried to open. I have 50Meg service but can only get about 33KB/sec download grabbing this thing. Lol.

will have to try later when not over loaded or whatever. Annoying!!! Need a better site!!

I hate the post-MegaUpload era...

Entropy512 said:
I hate the post-MegaUpload era...
Click to expand...
Click to collapse
Ya lol, i really want to try this..
I can always seem to get touchscreen working again after installing your stock recovery/kernel but no pen, I am hoping this will fix my issue cause i have tried it all
i put clockwork on and tried wiping and nada question in order to wipe do u have to mount first in clockwork? I am use to twrp.
if that is the case i will give that a shot.

Entropy512 said:
I hate the post-MegaUpload era...
Click to expand...
Click to collapse
I think I've tried 5 times and each one failed partway through. Do sites like goo.im not let you upload files that big?
What about the site that the other guy used, http://www.peejeshare.com/ ?

ya i tried a lot too,
I also have tried every method in getting the pen to work, and always either get no touch screen or no pen.
I have tried wiping, different orders, flashing clockwork and wiping all in there.
NADA no pen
Shoulda of just waited to root til this came out officially.
I might have to throw in the towel if this tar doesn't work and and send it back after clearing the binary count.
Unless someone has another idea?

[Q] Having trouble upgrading to 4.4.2 stock on Verizon

I have a Moto X Developer Edition rooted on Verizon with TWRP 2.6.3.1 and stock Android 4.4 on it. I have been trying to upgrade to 4.4.2 without doing the OTA, and without having to reflash TWRP.
So far, I have been unsuccessful.
I have tried Blur_Version.140.45.5.ghost_verizon.Verizon.en.US.zip (approximate file size 150MB) from multiple sources as all the posts I read keep saying that is what works. I have also tried a ~650MB version I found somewhere. In addition, I tried the upgrade located here: sbf.droid-developers.org/phone.php?device=0 which is called VZW_XT1060_4.4.2-KXA20.16-1.25.2_CFC_1FF.xml.zip (It's the 4.4.2 upgrade listed under Verizon US).
All of these fail. In TWRP, about 2-3 steps after it verified md5, it simply says "Failed" with no explanation as to why.
Here is my question:
How can I upgrade to 4.4.2 without a data wipe, and without having to reflash TWRP?
I have no interest in going to a ROM, I want to stay stock, and if I must, I will reflash the recovery if I have to, but I *really* don't want to.

Flash stock recovery, take the OTA, flash TWRP again.
It's so simple, so painless, so quick and it will not wipe your data.

tcrews said:
Flash stock recovery, take the OTA, flash TWRP again.
It's so simple, so painless, so quick and it will not wipe your data.
Click to expand...
Click to collapse
I was hoping to avoid that (Yep, I really am that lazy...) but that's what I was going to do tonight if I couldn't get my hands on a .zip to flash.
Ironically, I bought the Dev Edition specifically so things like this would be easy.

It is easy.....just need to do it.
I support my sister, her husband and my wife (as well as my own) who all have Moto X's. 2 seconds to flash recovery, however long it takes for the OTA to install and reboot and then 2 seconds to flash TWRP again. Heck...I'd just leave the stock recovery in place since it's not needed if you don't plan on flashing any ROMs. The OTA doesn't even remove root.

tcrews said:
It is easy.....just need to do it.
I support my sister, her husband and my wife (as well as my own) who all have Moto X's. 2 seconds to flash recovery, however long it takes for the OTA to install and reboot and then 2 seconds to flash TWRP again. Heck...I'd just leave the stock recovery in place since it's not needed if you don't plan on flashing any ROMs. The OTA doesn't even remove root.
Click to expand...
Click to collapse
Oh, that last bit is good to know! Well, I think even if it did remove root, getting it back is easy on the DE.
I think you're right though, I probably won't install TWRP again, I specifically got the Moto X because I was tired of messing around with stuff when I all I want is a rooted, stock Android experience.

So, after several hours of messing with this, and thinking the stock recovery had gotten messed up because the instructions I had for getting in to it were wrong, I finally got the OTA installing...
and it fails.
I don't know why, I haven't seen the error (I'm not looking at the phone when it fails).
So... Awesome.

Taegost said:
So, after several hours of messing with this, and thinking the stock recovery had gotten messed up because the instructions I had for getting in to it were wrong, I finally got the OTA installing...
and it fails.
I don't know why, I haven't seen the error (I'm not looking at the phone when it fails).
So... Awesome.
Click to expand...
Click to collapse
Are there files out so you can just flash 4.4.2 with mfastboot? Would be easiest.

kj2112 said:
Are there files out so you can just flash 4.4.2 with mfastboot? Would be easiest.
Click to expand...
Click to collapse
I assume so, but I haven't found any instructions specifically saying how to do that, except for the ones that tell you how to return to stock without using RSD Lite.
Unfortunately, I don't know enough about how all this stuff works to be able to figure out which bits and pieces to put together to get upgraded without wiping my data.
What really pisses me off is that I specifically bought this phone so I wouldn't have issues like this, and here I am...
BTW: The only thing the error says is "Error". That's it, nothing else.

Taegost said:
I assume so, but I haven't found any instructions specifically saying how to do that, except for the ones that tell you how to return to stock without using RSD Lite.
Unfortunately, I don't know enough about how all this stuff works to be able to figure out which bits and pieces to put together to get upgraded without wiping my data.
What really pisses me off is that I specifically bought this phone so I wouldn't have issues like this, and here I am...
BTW: The only thing the error says is "Error". That's it, nothing else.
Click to expand...
Click to collapse
This guide has a return to stock section. It will tell you how to flash the stock firmware.
http://forum.xda-developers.com/showthread.php?t=2603358
Unfortunately the moto x is not a simple phone for tinkering with, like say a nexus, even the dev edition.
It can be easier once you do fully understand everything. Just gotta know what applies to you...meaning mostly the locked versus unlocked methods for everything.
After owning an s2, a moto x and now an n5 (n7 too...but I don't tinker with it really....its a family device) I've come to the mind set that for flashers and rooters.....nothing at all beats owning a nexus. Every other device has some limitations that a nexus won't have.

kj2112 said:
This guide has a return to stock section. It will tell you how to flash the stock firmware.
http://forum.xda-developers.com/showthread.php?t=2603358
Unfortunately the moto x is not a simple phone for tinkering with, like say a nexus, even the dev edition.
It can be easier once you do fully understand everything. Just gotta know what applies to you...meaning mostly the locked versus unlocked methods for everything.
After owning an s2, a moto x and now an n5 (n7 too...but I don't tinker with it really....its a family device) I've come to the mind set that for flashers and rooters.....nothing at all beats owning a nexus. Every other device has some limitations that a nexus won't have.
Click to expand...
Click to collapse
Yeah, that's the page I was talking about when I said I found the full instructions...
I specifically bought this phone because I didn't want to mess around with it like this, I just wanted to root it so I could use Titantium Backup and be done with it... and now I'm stuck at a halfway point.... Again...
I'll probably end up just doing the full wipe and manually flash to 4.4.2 (RSD Lite doesn't see my device... yay), since I have gone from my mute button not working (with 4.2.2), to a really bad echo for whomever I'm talking to when it's on speakerphone (Even when speakerphone is muted... THAT made for a fun conference call...).

Taegost said:
Yeah, that's the page I was talking about when I said I found the full instructions...
I specifically bought this phone because I didn't want to mess around with it like this, I just wanted to root it so I could use Titantium Backup and be done with it... and now I'm stuck at a halfway point.... Again...
I'll probably end up just doing the full wipe and manually flash to 4.4.2 (RSD Lite doesn't see my device... yay), since I have gone from my mute button not working (with 4.2.2), to a really bad echo for whomever I'm talking to when it's on speakerphone (Even when speakerphone is muted... THAT made for a fun conference call...).
Click to expand...
Click to collapse
Flashing stock and rooting on an unlocked Moto x is basically the same as a nexus. It really is simple, once you are familiar with fastboot.
I guess there are toolkits that automate everything....like Samsung's Odin, and there's a few for nexus....but it really doesn't help anyone learn. And that's kinda what this hobby is all about.
But, I am sorry you're having trouble. Not sure what else to add. The guides are there, and they work. Usually. I can't think of anything to add to whats already been said.
Hope it works out for you!

kj2112 said:
Flashing stock and rooting on an unlocked Moto x is basically the same as a nexus. It really is simple, once you are familiar with fastboot.
I guess there are toolkits that automate everything....like Samsung's Odin, and there's a few for nexus....but it really doesn't help anyone learn. And that's kinda what this hobby is all about.
But, I am sorry you're having trouble. Not sure what else to add. The guides are there, and they work. Usually. I can't think of anything to add to whats already been said.
Hope it works out for you!
Click to expand...
Click to collapse
I don't think I'm articulating my issue properly. I understand how to do everything in the guides you mentioned, they're a piece of cake. That doesn't solve my problem.
My problem is that I want to get to 4.4.2 WITHOUT wiping my data, but can't do the update via OTA or flashing in recovery. RSD Lite doesn't work either.
The ONLY option I have available to me is to manually push the update with fastboot, which I can definitely do with the instructions provided... But those instructions require me to wipe my data.
I know it's possible to apply the update with fastboot without requiring me to wipe my data, but I don't know enough about the inner workings to know which steps to skip, and which need to be modified, in order to make that happen.

Taegost said:
I don't think I'm articulating my issue properly. I understand how to do everything in the guides you mentioned, they're a piece of cake. That doesn't solve my problem.
My problem is that I want to get to 4.4.2 WITHOUT wiping my data, but can't do the update via OTA or flashing in recovery. RSD Lite doesn't work either.
The ONLY option I have available to me is to manually push the update with fastboot, which I can definitely do with the instructions provided... But those instructions require me to wipe my data.
I know it's possible to apply the update with fastboot without requiring me to wipe my data, but I don't know enough about the inner workings to know which steps to skip, and which need to be modified, in order to make that happen.
Click to expand...
Click to collapse
It says right at the bottom of the return to stock section in the guide I linked too.....you can skip
Fastboot erase user data
fastboot erase cache
Though if you have any problems after, you might have to do it again and do erase those, before spending time trying to figure out what's wrong.

kj2112 said:
It says right at the bottom of the return to stock section in the guide I linked too.....you can skip
Fastboot erase user data
fastboot erase cache
Though if you have any problems after, you might have to do it again and do erase those, before spending time trying to figure out what's wrong.
Click to expand...
Click to collapse
Wow... Attention to detail -5
Sorry about that, when I looked through that article, I skimmed through and saw that the "Return to Stock" section was (almost) identical to the other instructions I was reading...But I missed that last paragraph when I looked at the link you provided, the directions I was using referenced that article but did not include that last bit...
Thank you for your patients, I feel like a dumbass now *sheepish grin*

Taegost said:
Wow... Attention to detail -5
Sorry about that, when I looked through that article, I skimmed through and saw that the "Return to Stock" section was (almost) identical to the other instructions I was reading...But I missed that last paragraph when I looked at the link you provided, the directions I was using referenced that article but did not include that last bit...
Thank you for your patients, I feel like a dumbass now *sheepish grin*
Click to expand...
Click to collapse
No worries!! .
And sorry, its userdata. My keyboard split the words up.
---------- Post added at 11:16 AM ---------- Previous post was at 11:15 AM ----------
And, you may very well have issues doing that way. But its worth a shot first. If you do have issues, then you can erase those and repeat the process.

if using fastboot/mfastboot, I would still erase cache, as it doesn't touch your data/apps/config.
Another tip, use this mfastboot -> http://mark.cdmaforums.com/X-STUFF/Mfastboot-4.4.zip
or you can use RSDlite to flash the SBF, but there is a corresponding line for "erase data"
Two helpful links that will help explain what you saw...
Taking the OTA -> http://mark.cdmaforums.com/MotoX-OTA.html
various ways to Return to stock -> http://mark.cdmaforums.com/MotoX-ReturnToStock.html

kj2112 said:
No worries!! .
And sorry, its userdata. My keyboard split the words up.
---------- Post added at 11:16 AM ---------- Previous post was at 11:15 AM ----------
And, you may very well have issues doing that way. But its worth a shot first. If you do have issues, then you can erase those and repeat the process.
Click to expand...
Click to collapse
Alrighty, well I was able to successfully flash to 4.4.2 using the Fastboot instructions. Flashed TWRP afterwards and got root right back. Now that I know, this won't be a trial in the future (fingers crossed!)
Thanks for your help and patience

[Q&A] VS980 Resources - Bootstacks/Modems/Unofficial FW/Manual OTA/etc

Q&A for VS980 Resources - Bootstacks/Modems/Unofficial FW/Manual OTA/etc
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for VS980 Resources - Bootstacks/Modems/Unofficial FW/Manual OTA/etc. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!

MicroMod777 said:
Sweet. Did you post you tried the bumped twrp on the 39a and it didn't work. Last time I remember they had to rebuild twrp based on 26a. It might need to be rebuild on 39a sources.
Click to expand...
Click to collapse
xdabbeb said:
Nope. No idea what the point of that is.
Click to expand...
Click to collapse
Following the links, it looks like there's a new root exploit using download mode for a number of LG devices - http://forum.xda-developers.com/android/development/guide-root-method-lg-devices-t3049772

Help
With these zip files. Are we able to use twrp and jump back and forth between boot loader versions or once you go past a certain boot loader you have to revert back to stock or use a special process to down grade.

protfire said:
With these zip files. Are we able to use twrp and jump back and forth between boot loader versions or once you go past a certain boot loader you have to revert back to stock or use a special process to down grade.
Click to expand...
Click to collapse
You can, but when switching between different based roms you'll often need to flash stock to get your sensors working again.
Sent from my LG-VS980 using XDA Free mobile app

Looking for some guidance
Having some issues with getting setup to flash VS982.5
Had a replacement phone sent from Verizon because of a dead digitizer. The phone shipped with 27A. I was able to get it rooted and got recovery installed, but then started running into issues. From there, I used the 11A tot. Got rooted, used Autorec for recovery and then tried flashing 28A, but am now getting a secure boot error.
Anyone have any advice?
@xdabbeb ???

noob question
Ok been flashing for a while nexus 7 - nexus 7 2013 and nexus 10 but this lg is a diiferent animal so im on broadbase 26a and can flash all cloudys roms but cant get lollipop roms to flash tried flashing the 39a and it rebooted but no data so went back to 26a broadbaseand all worked again so my question is can i flash 39a with the 26a modem and make flashing lollipop Possibly. Im on the verizon vs 980 model. Thanks in advance

Help please!
Sorry - I've not had to ask for help much, but I may have flashed the bootstack incorrectly.
I was on xdabbeb's VS980 v2.3.0 (26A), and I wanted to update to his VS982.5 1.2.0. I thought I could just go into my TWRP and flashed the new bootstack.
Ooops - now I'm getting that secure booting error. Anyone know how to fix this?
---------- Post added at 04:37 AM ---------- Previous post was at 04:27 AM ----------
Sorry - I've not had to ask for help much, but I may have flashed the bootstack incorrectly.
I was on xdabbeb's VS980 v2.3.0 (26A), and I wanted to update to his VS982.5 1.2.0. I thought I could just go into my TWRP and flashed the new bootstack.
Ooops - now I'm getting that secure booting error. Anyone know how to fix this?

kongo101 said:
Sorry - I've not had to ask for help much, but I may have flashed the bootstack incorrectly.
I was on xdabbeb's VS980 v2.3.0 (26A), and I wanted to update to his VS982.5 1.2.0. I thought I could just go into my TWRP and flashed the new bootstack.
Ooops - now I'm getting that secure booting error. Anyone know how to fix this?
Click to expand...
Click to collapse
So, after 3 hours of fiddling around, I figured it out.
1. I was in the process of using the unbrick method where you hop onto Linux and dd those 5 files to fix the error and unbrick your phone from the loop. However, I realized that method is for folks who actually still have a ROM installed. I had just wiped to install the XDABBEB's 482.5 FW and there was no other FW installed. Stupid.
However, I still had my internal SD card stuff (photos, Titanium backups, etc) that were on the phone somewhere.
2. Somewhere along the line of frustration, I thought that the only way was to get a replacement (insurance) phone, which would mean losing all my data anyways. During that time, I somehow got into fastboot mode. Then I tried flashing the stock 11A FW. Somehow, it worked! (I lost all my internal SD data though, sadly).
3. I took all the OTA updates to 28A. Then I rooted with IOroot, installed TWRP with AutoRec. Then I flashed XDABBEB's 28A bootstack and on the restart, I got that same stupid secure boot error and black screen. I was VERY upset at that point.
4. I did the Vol Down + Power button hold to get into recovery, and when it asked me if I wanted to factory reset, I simply said yes, and it brought me back to TWRP. I flashed XDABBEB's ROM and on the reboot, everything was fine
I'm sure most of this stuff just sounds dumb. I probably could have just got into recovery from the very beginning (step 4) and just flashed XDA's Rom and all of this would have been unnecessary. However, as soon as I saw the "secure boot error" I freaked out and started browsing XDA and jumped the gun. Lesson learned.
Thanks still, for the XDA resources so that I could eventually figure this out on my own, even the long way.
Thanks,
David.

kongo101 said:
So, after 3 hours of fiddling around, I figured it out.
1. I was in the process of using the unbrick method where you hop onto Linux and dd those 5 files to fix the error and unbrick your phone from the loop. However, I realized that method is for folks who actually still have a ROM installed. I had just wiped to install the XDABBEB's 482.5 FW and there was no other FW installed. Stupid.
However, I still had my internal SD card stuff (photos, Titanium backups, etc) that were on the phone somewhere.
2. Somewhere along the line of frustration, I thought that the only way was to get a replacement (insurance) phone, which would mean losing all my data anyways. During that time, I somehow got into fastboot mode. Then I tried flashing the stock 11A FW. Somehow, it worked! (I lost all my internal SD data though, sadly).
3. I took all the OTA updates to 28A. Then I rooted with IOroot, installed TWRP with AutoRec. Then I flashed XDABBEB's 28A bootstack and on the restart, I got that same stupid secure boot error and black screen. I was VERY upset at that point.
4. I did the Vol Down + Power button hold to get into recovery, and when it asked me if I wanted to factory reset, I simply said yes, and it brought me back to TWRP. I flashed XDABBEB's ROM and on the reboot, everything was fine
I'm sure most of this stuff just sounds dumb. I probably could have just got into recovery from the very beginning (step 4) and just flashed XDA's Rom and all of this would have been unnecessary. However, as soon as I saw the "secure boot error" I freaked out and started browsing XDA and jumped the gun. Lesson learned.
Thanks still, for the XDA resources so that I could eventually figure this out on my own, even the long way.
Thanks,
David.
Click to expand...
Click to collapse
The answer was to simply rebooting into recovery after flashing the bootstack, rather that rebooting the system. That would have prevented the secure boot error. Lesson learned the hard way.

Hey, tryna get my head to stop spinning after the loads of info I just memorized trying to figure all this stuff out. I'm trying to flash a CM12 official nightly on stock 5.02 and TWRP 2.8.5.1. I just used bouchigo's little guide to get the 28A aboot and bumped boot and recovery to see if that would let me flash CM12/the updated TWRP 2.8.6.0 and neither worked (I'm assuming because it's not 12b still). So now I'm about to try to use the 39A zip in here and then flash the 12b bootloader, but I'm not sure exactly how to do it. Do I just flash both in TWRP and then do the reboot to recovery? I tried to flash the new TWRP (2.8.6.0) in TWRP and it gave me the same loki error as CM12 did so not sure it will work that way with this? Also will it mess anything up with the bouchigo images I have installed/should i flash my stock backup before I flash the 39A? And once I install the boot stack can I just flash 12b boot loader and be good to go to install CM12?
Also is there anything major to be concerned about while messing with this boot stack stuff or will it mostly be recoverable problems where you can just flash your backup? Sorry for the general question. You don't have to go into too much detail or anything, just tryna make sure there's not something you would be more likely to do (like rebooting to system instead of recovery) trying to configure the boot stack to work for your needs. Thought it may be helpful for others also as I haven't seen too many (more specific and/or general) caution tips in the threads I've visited in the last few days, especially in the OP's. No offense to any of you developers or anything, just something I thought might be helpful in future posts (especially for semi-casual's and noob's like me lol). With that said I'm very grateful for all the information on this site and the devs for their time. Keep up the amazing work. And thank you in advance for the knowledge!

I'm confused with an issue I'm facing with my Vs980 on Tmobile, so might as well ask this here before I mess up the phone any further.
After flashing 39a kdz I was able to get LTE connectivity, but battery lifetime was kinda poor. A few posts reported improvements with a factory reset ... so I did just that. Battery lifetime was even worse ... so why not another factory reset? I did just that and LTE wouldn't come back on. The phone starts, shows full network, and 4G for a second ... then network connectivity becomes glitchy going on/off constantly. The only way to get a stable network connection was to go into the settings and change the network connectivity to UMTS/HSPA instead of the LTE/3GPP .
I tried flashing 27a kdz, but the same issue keeps on happening. Now I'm debating whether I should be flashing just the 39a modem from this post after a clean 39a kdz flash ... but I can't make much sense out of this thought.
Any ideas on what could be done to resolve this problem?

It works perfectly. Congrats!!!!

I have a question.. I'm on stock rooted 39a..do I need to flash bootstacks or can I just flash roms?
Sent from my VS980 4G using Tapatalk

Kilroy245 said:
I have a question.. I'm on stock rooted 39a..do I need to flash bootstacks or can I just flash roms?
Sent from my VS980 4G using Tapatalk
Click to expand...
Click to collapse
I flashed the rom without bootstacks but in twrp, if it goes into sleep, i get a dead screen with lines which I need to reset with adb command
adb reboot
On 39A rooted and twrp

vs980 39a Bootstack lollipop no cell signal or service
i have this lg g2 vs980, i was running an old xdabbeb 24a bootstack with a KK lg g2 rom on cricket service everything worked good besides bluetooth. (rooted&twrp recovery)
since then i have flashed twrp 2.8.6.3 bump-blastgator. i followed xdabbeb instructions for flashing 39a bootstack and xdabbeb_vs980_312.zip but i have no cell signal. i also tried LP-TMO-Extreme rom with a t-mobile simcard and apn and it didn’t work either. i was wondering if someone here can help, i tried flashing this rom and bootstack in every combination i could imagine, and still no signal.
i also flashed the 24a bootstack back and KK rom back and now still no signal. can someone please help me, I’m out of ideas.
thanks in advance!

Error loki-ifying
Hello, following your directions at http://forum.xda-developers.com/verizon-g2/development/vs98039a-stock-fw-t3051560, I was trying to flash the 39a bootstack zip from CWM on a VS980 10B. After the extractions, I got this message:
Code:
Finished!
script succeeded: result was [Finished]Checki
ng if loki-fying is needed/dev/block/platform/
msm_sdcc.1/by-name/boot needs lokifying.
[-] Failed to find function to patch.
Error loki-ifying the boot image.
I'm confused because it both says the script succeeded and that there was an error.
When I rebooted, I went into a bootloop. I got back into recovery. My recovery is now TWRP. I went ahead and flashed the 38A firmware, and everything seems to have worked out just fine.
Do I need to worry about the error I got flashing the bootstack?

ZV6 Update Discussion

Well, the ZV6 should hit anytime now, Sprint & LG updated links. The changelog seems lacking though
LG Open Source LS991::
http://opensource.lge.com/osSch/list?types=ALL&search=ls991
Sprint Changelog LS991:
http://support.sprint.com/support/a...ServiceAdvisory_542_GKB86631-dvc8970002prd#!/
* If anyone receives the update and is rooted, please capture / copy the update file to your SDCARD and post for us to download
.

Agimax said:
Well, the ZV6 should hit anytime now, Sprint & LG updated links. The changelog seems lacking though
LG Open Source LS991::
http://opensource.lge.com/osSch/list?types=ALL&search=ls991
Sprint Changelog LS991:
http://support.sprint.com/support/a...ServiceAdvisory_542_GKB86631-dvc8970002prd#!/
* If anyone receives the update and is rooted, please capture / copy the update file to your SDCARD and post for us to download
.
Click to expand...
Click to collapse
Will the old root method still work?

SantinoInc said:
Will the old root method still work?
Click to expand...
Click to collapse
The factory reset protection has me curious. I think the better question is can then somehow block TOT flashing.
We won't know if the old root method will mess things up. I would just wait for a v6 image to be released. Someone did make a post as a how-to root the image yourself if you can get it off the phone. I would just wait.

someone needs to capture the OTA and get it to me so I can check it out.
I'd suggest holding off on actually applying the update until we know what's what.
Thx in advance.

Let me know when you have it
https://dl.dropboxusercontent.com/u/49870189/LS991_ZV6_OTA_Stock_update.zip

Much thanks to you guys! Work some magic for us!

mswlogo said:
Let me know when you have it
https://dl.dropboxusercontent.com/u/49870189/LS991_ZV6_OTA_Stock_update.zip
Click to expand...
Click to collapse
sent you a PM as well but I'll say it in here just in case you check here first. got it.. thanks again!
so.. after some poking around I can confirm...
ZV6 updates the anti-rollback version yet again, this time to "v2". If you flash this update or any part of the zv6 bootstack or zv6 modem it will update parts of your phone you will never be able to downgrade. This would also stop the ZV5 TOT from working... but to be specific.. ZV5 TOT will flash.. but your phone will be BRICKED after.
ZV6 does not seem to unlock the bootloader. I'm about 90% on this after initial code review. Perhaps some poor soul will take the OTA and be able to confirm this without a doubt... but it looks like the "Factory Reset Protection update" (related to oem unlock in development settings) has nothing to do with unlock status itself.
If a ZV6 TOT is somehow acquired in the future... the system and boot partitions could be extracted and used on the ZV5 bootstack... possibly ZV4 as well. Basically... boot.img and system.img would not blow any qfuses to permanently set a "version".
Bootloader/bootstack consists of aboot, sbl1, sec, rpm, tz, hyp, pmic, sdi... and then theres the modem. Flashing any ZV6 partition mentioned in the prior sentence will blow your fuse to "v2".
As for root... it's hard to tell without the device in hand to be honest... but I would assume it's still able to be rooted. So taking the OTA would not be the end of the world... you'd still have root. But you'd lose the ability to flash the ZV5 TOT without bricking... and it once again updates your bootloader version which may be blocking previous holes in a v0 or v1 bootloader we have not yet found.
I am not sure why LG and the US carriers have done this. I could understand the v1 update.. as that would separate USA from the rest of the world and make bootloader unlocking harder. To update it to v2 just doesn't add up... not yet anyway.
tl;dr
If you want to stay on a v0 (ZV4) or v1 (ZV5) bootloader version.. don't update.
If you couldnt care less about the bootloader and only want root... ZV6 should still allow that.. but the ZV5 TOT would no longer be able to be used.

mswlogo said:
Let me know when you have it
https://dl.dropboxusercontent.com/u/49870189/LS991_ZV6_OTA_Stock_update.zip
Click to expand...
Click to collapse
So I can install this in the stock recovery (I am not rooted) because there is an option?
(I am doing it now but it seems to be stuck on "patching system files", uh oh)
edit: I am fine now, it installed fine. Was a little un-patient
I notice now the icons at the top are more stock android like with the "!" point if there is no internet. Pictures
Also the phone "feels" faster, I hope we can uncover what is under this update.
I hope this doesn't fix my free hotspot trick.

So if the OTA pops up, I can download and install it and still have root? Or has that been undetermined to to this point?

autoprime said:
sent you a PM as well but I'll say it in here just in case you check here first. got it.. thanks again!
so.. after some poking around I can confirm...
ZV6 updates the anti-rollback version yet again, this time to "v2". If you flash this update or any part of the zv6 bootstack or zv6 modem it will update parts of your phone you will never be able to downgrade. This would also stop the ZV5 TOT from working... but to be specific.. ZV5 TOT will flash.. but your phone will be BRICKED after.
ZV6 does not seem to unlock the bootloader. I'm about 90% on this after initial code review. Perhaps some poor soul will take the OTA and be able to confirm this without a doubt... but it looks like the "Factory Reset Protection update" (related to oem unlock in development settings) has nothing to do with unlock status itself.
If a ZV6 TOT is somehow acquired in the future... the system and boot partitions could be extracted and used on the ZV5 bootstack... possibly ZV4 as well. Basically... boot.img and system.img would not blow any qfuses to permanently set a "version".
Bootloader/bootstack consists of aboot, sbl1, sec, rpm, tz, hyp, pmic, sdi... and then theres the modem. Flashing any ZV6 partition mentioned in the prior sentence will blow your fuse to "v2".
As for root... it's hard to tell without the device in hand to be honest... but I would assume it's still able to be rooted. So taking the OTA would not be the end of the world... you'd still have root. But you'd lose the ability to flash the ZV5 TOT without bricking... and it once again updates your bootloader version which may be blocking previous holes in a v0 or v1 bootloader we have not yet found.
I am not sure why LG and the US carriers have done this. I could understand the v1 update.. as that would separate USA from the rest of the world and make bootloader unlocking harder. To update it to v2 just doesn't add up... not yet anyway.
tl;dr
If you want to stay on a v0 (ZV4) or v1 (ZV5) bootloader version.. don't update.
If you couldnt care less about the bootloader and only want root... ZV6 should still allow that.. but the ZV5 TOT would no longer be able to be used.
Click to expand...
Click to collapse
Thanks for poking around and seeing what's what. If I were inclined to update my rooted ZV5 to ZV6 (understanding the current TOT restore would brick my phone) how exactly would I keep root?

SantinoInc said:
Thanks for poking around and seeing what's what. If I were inclined to update my rooted ZV5 to ZV6 (understanding the current TOT restore would brick my phone) how exactly would I keep root?
Click to expand...
Click to collapse
I dont think you'd be able to keep it. You'd most likely have to re-root with a ZV6 rooted system.img... same way you rooted ZV5.

How did you manually install the update? I've looked up guides online but they say you need to install the Android SDK and LGFlashTool and such, which I messed around with but I can't really grasp on how to install this. Putting my G4 into download mode and trying to detect it via CMD did nothing (USB Debugging is checked).
Sorry, maybe somebody can lead me in the right direction, as I really want to try out this update and I'm also very impatient lol

argh2000 said:
I est gues is that the game is not meant for VGA screen
Click to expand...
Click to collapse
How do you create a ZV6 rooted boot image?

KillerDisturbed said:
How did you manually install the update? I've looked up guides online but they say you need to install the Android SDK and LGFlashTool and such, which I messed around with but I can't really grasp on how to install this. Putting my G4 into download mode and trying to detect it via CMD did nothing (USB Debugging is checked).
Sorry, maybe you can lead me in the right direction, as I really want to try out this update and I'm also very impatient lol
I have Skype also if that's something that you could do, cause I'd really appreciate the help
Click to expand...
Click to collapse
It requires an sd card..copy the file to the root of the sd card then power off the phone. Hold down volume down then power till you see "recovery mode" then release. Once stock recovery loads use the volume down to the last option, something like install update and press power. This will bring up the directory from the sd card. Select your file with volume down and press power.
Sent from my LGLS991 using Tapatalk

Swetnes said:
It requires an sd card..copy the file to the root of the sd card then power off the phone. Hold down volume down then power till you see "recovery mode" then release. Once stock recovery loads use the volume down to the last option, something like install update and press power. This will bring up the directory from the sd card. Select your file with volume down and press power.
Sent from my LGLS991 using Tapatalk
Click to expand...
Click to collapse
OH MY GOD
Thank you.! I'm installing it right now.
It's funny too, cause I saw people go into their recoveries on the LG G4 and assumed it was the same for all carriers and the International Version (I saw the generic locked recovery that only said "Are you sure you wanna delete all data?" or something, basically your only option was a factory reset). I thought it was that locked down on our phone, so I didn't even bother going into the recovery.
Thank you very much dude, wow...I feel dumb. And I used to run a GS3 with CM12 and CWM, and the stock recovery has some pretty good features on it too. Not too bad lol
*facepalm*

SantinoInc said:
How do you create a ZV6 rooted boot image?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?p=62369954
Sent from my LGLS991 using Tapatalk
---------- Post added at 11:36 PM ---------- Previous post was at 11:33 PM ----------
This update does include the Stagefright fix.
Sent from my LGLS991 using Tapatalk

KillerDisturbed said:
OH MY GOD
Thank you.! I'm installing it right now.
It's funny too, cause I saw people go into their recoveries on the LG G4 and assumed it was the same for all carriers and the International Version (I saw the generic locked recovery that only said "Are you sure you wanna delete all data?" or something, basically your only option was a factory reset). I thought it was that locked down on our phone, so I didn't even bother going into the recovery.
Thank you very much dude, wow...I feel dumb. And I used to run a GS3 with CM12 and CWM, and the stock recovery has some pretty good features on it too. Not too bad lol
*facepalm*
Click to expand...
Click to collapse
Can this be done even on rooted ZV5?

Probably. I installed the update and have noticed a few small touches in the UI, but notably a more responsive keyboard and overall faster phone. Knock code is also a bit more consistent and snappier for me as well, so I'll probably be using that from now on. Great update from the looks of it so far.
Sent from my LGLS991 using XDA Free mobile app

KillerDisturbed said:
OH MY GOD
Thank you.! I'm installing it right now.
It's funny too, cause I saw people go into their recoveries on the LG G4 and assumed it was the same for all carriers and the International Version (I saw the generic locked recovery that only said "Are you sure you wanna delete all data?" or something, basically your only option was a factory reset). I thought it was that locked down on our phone, so I didn't even bother going into the recovery.
Thank you very much dude, wow...I feel dumb. And I used to run a GS3 with CM12 and CWM, and the stock recovery has some pretty good features on it too. Not too bad lol
*facepalm*
Click to expand...
Click to collapse
Tried a few times to do this but it won't read my sd card..any ideas?
Sent from my LGLS991 using Tapatalk

stam27 said:
Tried a few times to do this but it won't read my sd card..any ideas?
Sent from my LGLS991 using Tapatalk
Click to expand...
Click to collapse
You may need to pull the card out and put it on a computer and format it using SD CARD FORMATER. If you Google it you will find it. I know with other phones I've had that solved recovery being able to read it. You are copying to the "external" sd card?
Sent from my LGLS991 using Tapatalk

Possible to Downgrade LM-V405QA From Pie to Oreo?

Just got a new in the box unit. It was made in 7/2019 and it arrived with Pie installed even though these originally came with Oreo. Is there any way to downgrade mine and, if so, how to do it and were to get a firmware file? Thanks for your help.

Unless I'm mistaken, this thread will tell you how: https://forum.xda-developers.com/lg-v40/how-to/guide-lgup-root-t3967858
and this thread contains the links to the KDZs (LG speak for stock ROMs): https://forum.xda-developers.com/lg-v40/development/v40-firmware-links-ainzooalgown-t3940600
[NG]Owner

NGOwner said:
Unless I'm mistaken, this thread will tell you how: https://forum.xda-developers.com/lg-v40/how-to/guide-lgup-root-t3967858
and this thread contains the links to the KDZs (LG speak for stock ROMs): https://forum.xda-developers.com/lg-v40/development/v40-firmware-links-ainzooalgown-t3940600
[NG]Owner
Click to expand...
Click to collapse
Thanks. I do see those threads and those definitely help. But I am still not clear if I can downgrade. Perhaps it is because I am new to LG phones from Samsung and I know that on some Samsung devices, once you go forward you may not be able to go back. So I am just wondering about all that (along with if I can unlock the bootloader, install TWRP, and root on the model 405QA that I have). Cheers!

Using LGUP 1.14 on DEV mode will let you downgrade, matter is flashing cause phones themselves seem not have any issues by downgrading. Personally I've downgraded both my v40 and my older g7 a couple of times, no probs.

smariob said:
Using LGUP 1.14 on DEV mode will let you downgrade, matter is flashing cause phones themselves seem not have any issues by downgrading. Personally I've downgraded both my v40 and my older g7 a couple of times, no probs.
Click to expand...
Click to collapse
Thanks so much for your time and help. I have downloaded LGUP and installed according to this thread <https://forum.xda-developers.com/lg-v40/how-to/guide-lgup-root-t3967858>. When I try to run it, Win10 asks if it is ok, I say yes, and then nothing else happens. Hmmm. I believe this is LGUP 1.16.0.3. No idea what's up. I have the phone attached and in download mode as described here <https://droidrecovery.com/lg-v40-thinq-recovery-mode/>. Grrr.

Try this LG UP version https://forum.xda-developers.com/showpost.php?p=76995781&postcount=26 set the DLL on DEV mode.
As for unlock bootloader question on your other thread, yep so far it's the easiest method to do it. ADVICE: If you haven't touched anything yet I suggest take a bakup of your partitions via QFIL. So if you mess up something (most likely not but you never know) you will be able to restore everything as it was when you got the phone.

smariob said:
Try this LG UP version https://forum.xda-developers.com/showpost.php?p=76995781&postcount=26 set the DLL on DEV mode.
As for unlock bootloader question on your other thread, yep so far it's the easiest method to do it. ADVICE: If you haven't touched anything yet I suggest take a bakup of your partitions via QFIL. So if you mess up something (most likely not but you never know) you will be able to restore everything as it was when you got the phone.
Click to expand...
Click to collapse
Oh thanks so much! That version of LGUP seems to work (after I manually did some file copying that had permission problems from the scripts). I presume that to downgrade - assuming I have a compatible .KDZ - is to use the FOTA upgrade option?
I will look into the backup as you suggest. As a newbie on these devices, there is alot to learn. Cheers

smariob said:
Try this LG UP version https://forum.xda-developers.com/showpost.php?p=76995781&postcount=26 set the DLL on DEV mode.
As for unlock bootloader question on your other thread, yep so far it's the easiest method to do it. ADVICE: If you haven't touched anything yet I suggest take a bakup of your partitions via QFIL. So if you mess up something (most likely not but you never know) you will be able to restore everything as it was when you got the phone.
Click to expand...
Click to collapse
Ok, I see the phone in QFIL. Under the tools menu, I see QCN Backup/Restore. Is this the backup to which you refer? I don't see anything else that looks promising. Sorry for all of my newbie questions.

So, if you are going to do the back up use this guide: https://forum.xda-developers.com/lg-g7-thinq/how-to/how-to-partitions-flash-abl-t-mo-t4051249
Follow steps 1 to 10, Backing up _a partitions will do the job _b patitions will be mirrored from those when restore. Data is not mandatory to back up as it will take much time to read the whole partition. Another tip, rename your backed up files so you can identify them properly later.
Then when you are ready you can play with LG UP most of the time you will like to use Partition DL. Use refurbish only to go stock. FOTA is for updating between versions without losing data (nice if you crossflash/loss the ability to OTA on the phone)

smariob said:
So, if you are going to do the back up use this guide: https://forum.xda-developers.com/lg-g7-thinq/how-to/how-to-partitions-flash-abl-t-mo-t4051249
Follow steps 1 to 10, Backing up _a partitions will do the job _b patitions will be mirrored from those when restore. Data is not mandatory to back up as it will take much time to read the whole partition. Another tip, rename your backed up files so you can identify them properly later.
Then when you are ready you can play with LG UP most of the time you will like to use Partition DL. Use refurbish only to go stock. FOTA is for updating between versions without losing data (nice if you crossflash/loss the ability to OTA on the phone)
Click to expand...
Click to collapse
I cannot thank you enough for your time and help. I will read up on all this and continue tomorrow morning. Cheers.

smariob said:
So, if you are going to do the back up use this guide: https://forum.xda-developers.com/lg-g7-thinq/how-to/how-to-partitions-flash-abl-t-mo-t4051249
Follow steps 1 to 10, Backing up _a partitions will do the job _b patitions will be mirrored from those when restore. Data is not mandatory to back up as it will take much time to read the whole partition. Another tip, rename your backed up files so you can identify them properly later.
Then when you are ready you can play with LG UP most of the time you will like to use Partition DL. Use refurbish only to go stock. FOTA is for updating between versions without losing data (nice if you crossflash/loss the ability to OTA on the phone)
Click to expand...
Click to collapse
Wow! That is alot of partitions and a lengthy backup chore - even without including the _b partitions. You were 100% correct that renaming each file as you go makes this easier. I used the LUN#_the partition-label.bin as I discovered that some labels were re-used in different LUN.
I never would have figured this out without your help. Thanks.
After a brief rest I will move on and try to unlock the bootloader as described here <https://forum.xda-developers.com/lg-v40/development/unlock-lg-v40-via-9008-root-t-mobile-t4042207>.

It's great to know that, once you've done that UL BL would be a piece of a cake.

smariob said:
It's great to know that, once you've done that UL BL would be a piece of a cake.
Click to expand...
Click to collapse
Thanks so much! You might note I have posted in the other thread about troubles getting unlocked. I seem to have successfully sent the v35 bootloader to the phone. I have the QFIL log showing that. But when I go to fastboot mode and try the unlock command, it fails with unknown command. After restoring/sending the backup of the original partition, I tried issuing the same unlock command (not expecting it to work since I should have been back to the original pie bootloader) and I get the exact same error. This makes me wonder if the v35 bootloader is actually getting installed properly. The phone is on the most recent Pie (QA20e) and seems to boot and run fine - even right after I send the v35 bootloader. There were comments that using this bootloader with Pie might have problems and I have never had any so far. So again, I am wondering if the v35 is actually getting into place. A real mystery to me. Thanks!

whitedavidp said:
Wow! That is alot of partitions and a lengthy backup chore - even without including the _b partitions. You were 100% correct that renaming each file as you go makes this easier. I used the LUN#_the partition-label.bin as I discovered that some labels were re-used in different LUN.
I never would have figured this out without your help. Thanks.
After a brief rest I will move on and try to unlock the bootloader as described here <https://forum.xda-developers.com/lg-v40/development/unlock-lg-v40-via-9008-root-t-mobile-t4042207>.
Click to expand...
Click to collapse
In my case, it turned out that the phone was active on the B slot. So I took backups of those partitions as well, flashed the V35 bootloader into B, performed the unlock, re-flashed the Pie bootloader. When I reboot into normal mode, I now see an unlocked warning and it took a very long time for the phone to get started and prompt me to start all over with my Android install. Before I do that I am trying to restore the backup I made of the userdata partition to see if that spares me the whole setup thing. Thanks to all.

Yeah you've made it at least. Good one on figure out B slot was active. Now you're able to go custom roms or just go root.

smariob said:
Yeah you've made it at least. Good one on figure out B slot was active. Now you're able to go custom roms or just go root.
Click to expand...
Click to collapse
Again, thanks so much for all of you help and encouragement. From my pre-purchase research I had anticipated that I could do a dev unlock of the bootloader quite easily. I have rooted with Magisk now and am moving on to see what I can do. Cheers.

smariob said:
Using LGUP 1.14 on DEV mode will let you downgrade, matter is flashing cause phones themselves seem not have any issues by downgrading. Personally I've downgraded both my v40 and my older g7 a couple of times, no probs.
Click to expand...
Click to collapse
Thanks for all of your help and sorry for all the questions.
I am just wondering if you are able to use TWRP/Magisk root on the downgraded v40? In the TWRP thread it indicates that it requires Pie firmware be installed. If I cannot use TWRP/Magisk root on Oreo, then I will not bother trying to downgrade.
Again, thanks so much!

Now that you mention it. V40 TWRP is meant to use with pie... Will not boot on Oreo. I think there are workarounds for that if it's mandatory for you to be in Oreo, but not personally tested'em.

smariob said:
Now that you mention it. V40 TWRP is meant to use with pie... Will not boot on Oreo. I think there are workarounds for that if it's mandatory for you to be in Oreo, but not personally tested'em.
Click to expand...
Click to collapse
Thanks. Certainly not mandatory. So will stick with Pie for now anyway. Again, thanks so much.