Database Develop

FireTV Partial Bootloader Unlock

Well it's a little early for Christmas... but here is a special gift. This will allow the bootloader to load things from boot or recovery without them needing to be patched. This is not a full unlock and will not enable fastboot boot or fastboot flash. Obviously this will only work if you are rooted.
As usual, this WILL void your warranty and I am NOT responsible for anything you do with this. Using this tool won't brick your Fire TV, but doing stupid things afterwards might. I will stress here that flashing something bad to boot is a guaranteed way to brick because if the kernel can't boot you have no way to get back to recovery. For testing kernels, it's best to flash recovery to the boot partition and the new kernel to test to the recovery partition.
To use:
Downgrade: You must first downgrade to 51.1.0.2. If you already have CWM installed, you can skip this.
adb push aftv-unlock /data/local/tmp/
adb shell
chmod 755 /data/local/tmp/aftv-unlock
su
/data/local/tmp/aftv-unlock unlock
Afterwards you should see this message:
Code:
Attempting to unlock...
All done!
If not, something went wrong. If for whatever reason you want to relock the bootloader, you can use this command:
Code:
/data/local/tmp/aftv-unlock lock
You can download it here.

WOW, just WOW, awesome work rbox!
I was definitely not expecting this.

rbox said:
Well it's a little early for Christmas... but here is a special gift. This will allow the bootloader to load things from boot or recovery without them needing to be patched. This is not a full unlock and will not enable fastboot boot or fastboot flash. Obviously this will only work if you are rooted.
As usual, this WILL void your warranty and I am NOT responsible for anything you do with this. Using this tool won't brick your Fire TV, but doing stupid things afterwards might. I will stress here that flashing something bad to boot is a guaranteed way to brick because if the kernel can't boot you have no way to get back to recovery. For testing kernels, it's best to flash recovery to the boot partition and the new kernel to test to the recovery partition.
To use:
Downgrade: You must first downgrade to 51.1.0.2. If you already have CWM installed, you can skip this.
adb push aftv-unlock /data/local/tmp/
adb shell
chmod 755 /data/local/tmp/aftv-unlock
su
/data/local/tmp/aftv-unlock unlock
Afterwards you should see this message:
Code:
Attempting to unlock...
All done!
If not, something went wrong. If for whatever reason you want to relock the bootloader, you can use this command:
Code:
/data/local/tmp/aftv-unlock lock
You can download it here.
Click to expand...
Click to collapse
Congrats to you
And Merry Christmas to us FTV users!
BTW, could you please tell me the console messages for lock failure and unlock failure? (may they never occur)

..

JJ-KwiK said:
Awesome!
Thanks man!
Click to expand...
Click to collapse
maybe we can get some real mods for this device now. different roms and what not.
just ran the unlock and it worked like a charm

Rbox do you know if the bootloader can boot from usb?

Does this require a minimal CWM version of yours?
I installed your Recovery (CWM) - on all 4 of my AFTVs - when you first released it ..
I've not had any reason to upgrade to the latest versions.... I'm just using the heck outta the AFTV as it is built, with all the nice rooted options. I really don't need anything else yet, so ...
with that said " can I just install this unlock-lock feature? "

Truly amazing. Can't wait for full fledged android on this.

Nice to see this, but it doesn't help much when you have a Fire TV with a non-rootable firmware.

jmandawg said:
Rbox do you know if the bootloader can boot from usb?
Click to expand...
Click to collapse
The bootloader will only boot from the boot partition or the recovery partition on the mmc. But I'm working on a boot menu that will allow you to easily boot additional kernels which can then load your os from wherever you want.
toe-rag said:
I installed your Recovery (CWM) - on all 4 of my AFTVs - when you first released it ..
I've not had any reason to upgrade to the latest versions.... I'm just using the heck outta the AFTV as it is built, with all the nice rooted options. I really don't need anything else yet, so ...
with that said " can I just install this unlock-lock feature? "
Click to expand...
Click to collapse
Yes. This is independent of anything. The only dependence is the latest version of CWM requires it.

I installed ccm when you first released it then upgraded to the latest firmware the other night. Thanks a lot btw! But, can I assume (as a novice) this is not something I need to do right now. What I mean is is this just for people that want to experiment with new kernels or is there some advantage I'm missing? Thanks again and sorry if my question is a little too basic for this thread. I'm just genuinely curious.

KLit75 said:
I installed ccm when you first released it then upgraded to the latest firmware the other night. Thanks a lot btw! But, can I assume (as a novice) this is not something I need to do right now. What I mean is is this just for people that want to experiment with new kernels or is there some advantage I'm missing? Thanks again and sorry if my question is a little too basic for this thread. I'm just genuinely curious.
Click to expand...
Click to collapse
If you don't care about updating your CWM version, or using any of the other cool things I'll release in the future that needs it, then no. You don't need to do this.

Thanks for the response. I did, in fact just update cwm and am running your latest fw update. I guess "need" isn't the right word. But if I unlock it tonight the cool stuff is still forthcoming.
Sorry just 2 questions:
1. Unlocking and keeping it unlocked indefinetly is ok?
And here's one that s on a slightly different subject...
2. I noticed updating with your fw saves my settings. Is there a safe way to factory restore using cwm without the risk of losing root?
That's actually the one I'm most interested in now. My aftv has been having issues that are hard to troubleshoot. An option to factory restore would be great. I mostly use it for xbmc so the only thing I care about losing is root. Thanks.

KLit75 said:
Thanks for the response. I did, in fact just update cwm and am running your latest fw update. I guess "need" isn't the right word. But if I unlock it tonight the cool stuff is still forthcoming.
Sorry just 2 questions:
1. Unlocking and keeping it unlocked indefinetly is ok?
And here's one that s on a slightly different subject...
2. I noticed updating with your fw saves my settings. Is there a safe way to factory restore using cwm without the risk of losing root?
That's actually the one I'm most interested in now. My aftv has been having issues that are hard to troubleshoot. An option to factory restore would be great. I mostly use it for xbmc so the only thing I care about losing is root. Thanks.
Click to expand...
Click to collapse
Of course keeping it locked is fine... i wouldn't have released the tool if it wasn't.
As I've stated in MANY OTHER THREADS... factory reset in CWM is perfectly fine and has nothing to do with root.

rbox said:
If you don't care about updating your CWM version, or using any of the other cool things I'll release in the future that needs it, then no. You don't need to do this.
Click to expand...
Click to collapse
That's great. Thanks again

Thanks for this! Was very happy that the AFTV i ordered from eBay was rootable.
at the risk of being "that guy", can someone explain to a relative dummy like me the future potential with an unlocked bootloader? are we talking maybe an Android TV rom down the road? .. Apologies in advance

Hi, I unlocked the bootloader and it was successfully. Thank you rbox

barrist said:
Thanks for this! Was very happy that the AFTV i ordered from eBay was rootable.
at the risk of being "that guy", can someone explain to a relative dummy like me the future potential with an unlocked bootloader? are we talking maybe an Android TV rom down the road? .. Apologies in advance
Click to expand...
Click to collapse
Nothing that people couldn't already do with my old CWM. Custom ROMs and whatnot has been possible for a while. This just makes things a little easier because kernels don't need to be patched.

Yea! Install failed yesterday. I've had SU problems I think. Couldn't get the # prompt. Reinstalled latest ROM and SL'd SU from the store. The Unlock finally took. Thanks.

nice, thanks rbox, you rock.

Nexus Build Number (Google Images vs.. on device)

I got notification just now that there was a 191M update to Android 5.0 on my Nexus 6. I wasn't thinking about TWRP when I tapped ok to install and of course it wouldn't since it's not the stock recovery. I flashed the stock recovery and tried to repeat the install but now the handset tells me I'm up to date.
I look at the factory image for the N6 (Shamu) and the build on Google's dev site is LRX21O but the build on the handset is LNX07M.
TWRP couldn't side load it with interaction and since the stock bootloader wasn't there .. anyone have a clue why the factory image and the installed image differ in build?
Very odd and I see nothing about an update in any thread here.
-Ben

aergern said:
I got notification just now that there was a 191M update to Android 5.0 on my Nexus 6. I wasn't thinking about TWRP when I tapped ok to install and of course it wouldn't since it's not the stock recovery. I flashed the stock recovery and tried to repeat the install but now the handset tells me I'm up to date.
I look at the factory image for the N6 (Shamu) and the build on Google's dev site is LRX21O but the build on the handset is LNX07M.
TWRP couldn't side load it with interaction and since the stock bootloader wasn't there .. anyone have a clue why the factory image and the installed image differ in build?
Very odd and I see nothing about an update in any thread here.
-Ben
Click to expand...
Click to collapse
An update hit mine the moment I took it out of the box (had to charge it). Did yours? I seem to remember it being around that size and I'm on LRX210 with mine. Yours probably just hadn't had the "day 1" update yet so you probably need that.

youareme7 said:
An update hit mine the moment I took it out of the box (had to charge it). Did yours? I seem to remember it being around that size and I'm on LRX210 with mine. Yours probably just hadn't had the "day 1" update yet so you probably need that.
Click to expand...
Click to collapse
I more or less have the same issue, my update didn't show up though until after i had unlocked/rooted/TWRP. So now i have a update noti that wont go away because i cant actually update it. I am just going to wait for a flashable ZIP for TWRP to be posted though

youareme7 said:
An update hit mine the moment I took it out of the box (had to charge it). Did yours? I seem to remember it being around that size and I'm on LRX210 with mine. Yours probably just hadn't had the "day 1" update yet so you probably need that.
Click to expand...
Click to collapse
I'll just flash the img files individually to the current Factory and reroot.
Thanks!

TacoLord187 said:
I more or less have the same issue, my update didn't show up though until after i had unlocked/rooted/TWRP. So now i have a update noti that wont go away because i cant actually update it. I am just going to wait for a flashable ZIP for TWRP to be posted though
Click to expand...
Click to collapse
I just booted into the bootloader and did the following ... and it all worked fine.
/usr/local/android/platform-tools/fastboot flash bootloader bootloader-shamu-moto-apq8084-71.05.img
/usr/local/android/platform-tools/fastboot flash radio radio-shamu-d4.0-9625-02.55.03a.img
/usr/local/android/platform-tools/fastboot flash boot boot.img
/usr/local/android/platform-tools/fastboot erase system
/usr/local/android/platform-tools/fastboot flash system system.img
./fastboot boot CF-Auto-Root-shamu-shamu-nexus6.img
The proper commands are in the 2 very short shell scripts included with the factory tarball. It was easy. It took maybe 10 minutes. The above .imgs are all you need. Do not do cache.img or userdata.img if you want to keep your apps and their data. The list above is correct in order that they need to be flash in and the commands are there. Have at it.

but this all still doesn't answer the op's original question...what is LNX07M? this is a new build different from the factory image just posted...

indianajonze said:
but this all still doesn't answer the op's original question...what is LNX07M? this is a new build different from the factory image just posted...
Click to expand...
Click to collapse
A quick google would suggest that LNX07M is the lollipop developer preview

so he was just pushed to his retail device the developer preview build?

Sounds like his phone came with the developer preview installed, and the initial update just took a few days to appear for him which he didn't manage to install so is still on the preview.

aergern said:
I just booted into the bootloader and did the following ... and it all worked fine.
/usr/local/android/platform-tools/fastboot flash bootloader bootloader-shamu-moto-apq8084-71.05.img
/usr/local/android/platform-tools/fastboot flash radio radio-shamu-d4.0-9625-02.55.03a.img
/usr/local/android/platform-tools/fastboot flash boot boot.img
/usr/local/android/platform-tools/fastboot erase system
/usr/local/android/platform-tools/fastboot flash system system.img
./fastboot boot CF-Auto-Root-shamu-shamu-nexus6.img
The proper commands are in the 2 very short shell scripts included with the factory tarball. It was easy. It took maybe 10 minutes. The above .imgs are all you need. Do not do cache.img or userdata.img if you want to keep your apps and their data. The list above is correct in order that they need to be flash in and the commands are there. Have at it.
Click to expand...
Click to collapse
Thanks! Im not great with ADB commands, but I gave it a shot. After the first line, I got "cannot open 'bootloader-shamu-moto-apq8084-71.05.img'"
Any suggestions on that! Really appreciated!

TacoLord187 said:
Thanks! Im not great with ADB commands, but I gave it a shot. After the first line, I got "cannot open 'bootloader-shamu-moto-apq8084-71.05.img'"
Any suggestions on that! Really appreciated!
Click to expand...
Click to collapse
It's a pathing issue most likely. I put all .img's into the same directory as the fastboot binary.
Sorry if I wasn't clear. I sometimes forget I've been doing ops like this since 2008.

TacoLord187 said:
Thanks! Im not great with ADB commands, but I gave it a shot. After the first line, I got "cannot open 'bootloader-shamu-moto-apq8084-71.05.img'"
Any suggestions on that! Really appreciated!
Click to expand...
Click to collapse
Phantom Shadow said:
A quick google would suggest that LNX07M is the lollipop developer preview
Click to expand...
Click to collapse
Searched Google for that build # .. I got a lot of references to the Nexus 5 which my tired brain refused to click on. I would have never imagined a dev. preview would ship on a prod new handset. I usually am pretty good at GTMFing.

aergern said:
It's a pathing issue most likely. I put all .img's into the same directory as the fastboot binary.
Sorry if I wasn't clear. I sometimes forget I've been doing ops like this since 2008.
Click to expand...
Click to collapse
Mind if I send a PM? Would rather not feel like im cluttering things!
(I have never actually updated this way before, haha)

TacoLord187 said:
Mind if I send a PM? Would rather not feel like im cluttering things!
(I have never actually updated this way before, haha)
Click to expand...
Click to collapse
Sure.
Hit me up. :good:

aergern said:
Sure.
Hit me up. :good:
Click to expand...
Click to collapse
It doesn't look like my messages went through (at least they are not showing up in my sent mail)
So just incase,
1. Where are the downloaded .img files stored
2. Where is the folder that I need to move them too?
3. EDITED OUT. Misread something
Thank you so much for your help!

Answers inline.
TacoLord187 said:
It doesn't look like my messages went through (at least they are not showing up in my sent mail)
So just incase,
1. Where are the downloaded .img files stored
You download the factory image tarball from Google's Android dev site. You then untar it wherever you like. I would probably untar it as root in /tmp/ then you can just mv the files to where you need them.
2. Where is the folder that I need to move them too?
The SDK is a zip file. You can unzip it wherever you like. I do this in /usr/local/ and then do a softlink to the directory it makes.
example: ln -s /usr/local/android <sdk directory>
I then cd into the tools directory and do this .. ./android which starts the UI so you can download the rest of the SDK. Do not bother with anything older than 4.4.4 packages.
I then move the img files from the factory image directory in /tmp to /usr/local/android/platform-tools/
You can then use the commands from the other post.
You can cat the install scripts for any syntax you might need but I think you'll find the commands I put in the other post to work for you.
3. Do I need to reroot/TWRP after? I can if needed, just want to be prepared!
Indeed you do. You can also move the CF img to the platform-tools directory. I would keep the tgz of the factory image somewhere else than /tmp in case you need it again.
Click to expand...
Click to collapse

aergern said:
Answers inline.
Click to expand...
Click to collapse
Looks like I got it all (rebooting now)! It just wasn't liking the paths as you said.
Thanks so much for your help!

TacoLord187 said:
Looks like I got it all (rebooting now)! It just wasn't liking the paths as you said.
Thanks so much for your help!
Click to expand...
Click to collapse
Awesome.
Well, with your ability to unzip the SDK and untar the factory image wherever you like ... I figured it was a pathing issue.

aergern said:
Awesome.
Well, with your ability to unzip the SDK and untar the factory image wherever you like ... I figured it was a pathing issue.
Click to expand...
Click to collapse
I have my adb set so I dont have to type the paths always. It just reads from a folder called android on my desktop (im on a mac). It normally works, but it wanted the paths for this one. Oh well. No big deal! Its updated and working!
Thanks again

aergern said:
Searched Google for that build # .. I got a lot of references to the Nexus 5 which my tired brain refused to click on. I would have never imagined a dev. preview would ship on a prod new handset. I usually am pretty good at GTMFing.
Click to expand...
Click to collapse
His phone might have been shipped that way as some people phones where shipped with Android 4.4.4.

[Q] Stock Rooted Rom

Any way to get a stock rooted flashable zip? Even if it doesn't contain root. I am not sure how they are created.

nhpctech said:
Any way to get a stock rooted flashable zip? Even if it doesn't contain root. I am not sure how they are created.
Click to expand...
Click to collapse
take a few minutes and root your device. you fastboot unlock your bootloader, fastboot oem device. then you flash a recovery, then flash the supersu binaries in that recovery, then boot up. thats it. now you have a stock rooted rom.

simms22 said:
take a few minutes and root your device. you fastboot unlock your bootloader, fastboot oem device. then you flash a recovery, then flash the supersu binaries in that recovery, then boot up. thats it. now you have a stock rooted rom.
Click to expand...
Click to collapse
I know how to root, unlock bootloader and flash roms. Im looking to create a flashable zip of the stock rom. Not only have a stock rooted device.

bump...

There is no flashable zip of the stock ROM.
Take simms22's advice.

zephiK said:
There is no flashable zip of the stock ROM.
Take simms22's advice.
Click to expand...
Click to collapse
Is there a reason for this? Is it just the amount of time the phone has been out? It just seems that I used to see Stock Rom .zip's for Stock everywhere on every device i've owned that had an unlocked bootloader except for this phone so far.

nhpctech said:
Any way to get a stock rooted flashable zip? Even if it doesn't contain root. I am not sure how they are created.
Click to expand...
Click to collapse
I think this is what you're looking for:
http://forum.xda-developers.com/nexus-6/development/rom-stock-rooted-5-1-lmy47e-root-t3057902

Nameless crowd face said:
I think this is what you're looking for:
http://forum.xda-developers.com/nexus-6/development/rom-stock-rooted-5-1-lmy47e-root-t3057902
Click to expand...
Click to collapse
I think you're only 8months late.
sent from my nexus

crashercarlton said:
Is there a reason for this? Is it just the amount of time the phone has been out? It just seems that I used to see Stock Rom .zip's for Stock everywhere on every device i've owned that had an unlocked bootloader except for this phone so far.
Click to expand...
Click to collapse
Primarily because, factory images are provided by Google and flashed with fastboot. In the same fastboot session, you can install custom recovery. Then boot to recovery and flash SuperSU zip.
Takes less than 5 minutes.

The_Merovingian said:
Primarily because, factory images are provided by Google and flashed with fastboot. In the same fastboot session, you can install custom recovery. Then boot to recovery and flash SuperSU zip.
Takes less than 5 minutes.
Click to expand...
Click to collapse
less than 2 minutes :angel:

Roobwz said:
I think you're only 8months late.
sent from my nexus
Click to expand...
Click to collapse
Had to throw that in there, huh...Why do some ppl love responding to posts not directed at them, knowing they aren't contributing anything of value. Should be a name for ppl who do that.. Oh wait, there is...

Nameless crowd face said:
Had to throw that in there, huh...Why do some ppl love responding to posts not directed at them, knowing they aren't contributing anything of value. Should be a name for ppl who do that.. Oh wait, there is...
Click to expand...
Click to collapse
This thread is old. At the time, there were no rooted stock roms. There are many by now and everyone can see them all in the android development forum. Generally, digging up old threads doesn't serve any purpose becuase the questions are no longer valid, thus answering them is superfluous and just adds to forum clutter

simms22 said:
less than 2 minutes :angel:
Click to expand...
Click to collapse
Two minutes! Ha! If only! Rebuilding the dalvic cache (is it still called that?) on first boot takes my phone like 5 minutes alone...
My problem with flashing factory images is having my /sdcard/ wiped. Is there a way around it? Like a way to flash /data/ without touching /sdcard/?
Backing everything up, transferring it to my laptop, flashing the image and twrp, booting, transferring everything back and restoring my TiBu takes waaaaaayyyy longer than just flashing a zip and restoring TiBu

danarama said:
This thread is old. At the time, there were no rooted stock roms. There are many by now and everyone can see them all in the android development forum. Generally, digging up old threads doesn't serve any purpose becuase the questions are no longer valid, thus answering them is superfluous and just adds to forum clutter
Click to expand...
Click to collapse
(Polite) point taken. I should've looked at dates. My apologies

Morganmachine91 said:
Two minutes! Ha! If only! Rebuilding the dalvic cache (is it still called that?) on first boot takes my phone like 5 minutes alone...
My problem with flashing factory images is having my /sdcard/ wiped. Is there a way around it? Like a way to flash /data/ without touching /sdcard/?
Backing everything up, transferring it to my laptop, flashing the image and twrp, booting, transferring everything back and restoring my TiBu takes waaaaaayyyy longer than just flashing a zip and restoring TiBu
Click to expand...
Click to collapse
Yes. If you're simply updating, just flash the system image and boot image if it's updated. Same goes for bootloader and radio. If you don't flash userdata, you won't lose data.

Nameless crowd face said:
(Polite) point taken. I should've looked at dates. My apologies
Click to expand...
Click to collapse
Not the end of the world

Updating rooted Nexus 6 (Marshmallow) + OTA

So I have a Nexus 6 stock room rooted (Systemless root). I have been a cm user ever since my Evo supersonic. I am unfamiliar with the correct way to apply the OTA that came out recently.
I have read that all that is needed is to flash system.img from the new archive. Is this true? Keep in mind I want to update without wiping my apps and data. I have been asking myself if I can give up phone-wide adblocking, and I'm going to give it a shot. The reason I've been asking this is because as I understand it, updating will remove twrp. This I don't really understand... Why would flashing system wipe recovery? Aren't they in different partitions?
I have done a lot of searching over a stupidly long period of time and have not found satisfactory answers.
Can I simply :
fastboot flash system system.img
or is there more to it than that?
Could someone please lay it all out for me?
Thanks

And yes I did see this thread: http://forum.xda-developers.com/nexus-6/general/easily-apply-ota-update-to-rooted-nexus-t3204018
And this one as well: http://forum.xda-developers.com/nexus-6/general/using-image-to-update-nexus-6-data-loss-t3053158
There are unanswered questions with both.
On the first link, why the hell would I erase the system partition? Wouldn't that be like doing a factory reset???
On the second one, why the hell would I flash the bootloader? Would it have changed from version to version and why would it matter if it had?
Why do I need anything other than to flash system.img over what is already there and flash the new radio?

So, erasing system before flashing is not really necessary, but it doesn't hurt, and definitely it's not factory reset. Erasing only makes sure that while flashing erases all files before flashing a partition, you want to be extremely sure.
And no, erasing system is not factory reset. Factory reset is erasing the data partition where the application data is stored, even for the system and private system apps. Actually TWRP only deletes the /data/data folder and some Android folders and leaves your other files safe when performing "factory reset".
You might need the boot.img, because it contains the kernel itself, so as these updated are security updates, it's probable they have patched some security hole in the kernel itself.
Finally the radio might have changed, but it usually doesn't. In fact AFAIK it hasn't changed since after the M previews, and the bootloader is the same as in the M previews. But if you don't have the previous factory images to do quick file diffs, it won't hurt to update them anyway.
So you need to flash boot and system, the re-flash SuperSu, and that"s that. If you want to make sure you won't have some system apps FC-ing in TWRP delete cache and dalvik. And if it'S TWRP prior to 3.0 don't let it modify your system partition.
And that's that.

Thank you

Forboding Angel said:
And yes I did see this thread: http://forum.xda-developers.com/nexus-6/general/easily-apply-ota-update-to-rooted-nexus-t3204018
And this one as well: http://forum.xda-developers.com/nexus-6/general/using-image-to-update-nexus-6-data-loss-t3053158
Click to expand...
Click to collapse
Did you also take a look at this one: http://forum.xda-developers.com/nexus-6/help/how-security-update-ota-twrp-t3307409 ? Post #23 in that thread may answer your question as to why TWRP might get replaced with stock recovery.

Ahhhh ok that explains a lot. I think I'm going to try going straight stock with adblock browser and no root and see if I can put up with it.

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.