Good info, glad it worked for you. The FTM has been mentioned for other reasons, like getting serial number back and also, importantly, to be able to use the key combo to get to recovery and to fastboot. Never heard of it being used, the original, to get correct (now) model number.
My stock one works. But thanks bro ( :refer to this one mate it helps me a lot
* I'm not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the alarm app failed (like it did for me...). * YOU are choosing to make these modifications, and if you point the finger at me for messing...forum.xda-developers.com
There's GCams that have all three cameras. You'll have to do some searching to see which works best.
Okay thanks.. i will try.There's GCams that have all three cameras. You'll have to do some searching to see which works best.
I mean just backup your stuff and try it out yourself. You're going to spend more time asking every single question you have instead of figuring it out with the resources in this thread (this thread answers every single question you have).
Make sure you CAREFULLY read the tutorial and backup everything you can. I skipped a few steps and did things wrong and added a good 24 hours to my journey, but on the bright side I know how to fix most things that go wrong now...lol
No, there's no conflict. It's understandable to imagine there would be, but there are some partitions (ftm is one) that don't seem to change with the android version.
After I restore, do I restart the phone just holding the power, or do I need some key combination for the phone to restart in the firmware?No, there's no conflict. It's understandable to imagine there would be, but there are some partitions (ftm is one) that don't seem to change with the android version.
Restoring the original ftm will also give you access to fastboot and recovery by using the key combo's. Most don't realize ftm controls that, it was a shock to me, had no idea.
Hey, thanks, what's up with you ^_^@netmsm Hey what's up. I finally managed to flash LG K71 Android 12 firmware onto my Stylo 6. I had to first delete OP_a and OP_b in BROM mode, get the phone to download mode right after, then I had to use the "Board DL" option in LGUP to flash the kdz, or else it would not properly flash and the phone would get soft bricked.View attachment 5722597
Hi bro, I have a question and I would be very grateful if you can help me.LG K31 Crossflashing:
To crossflash LG K31 go to this guide. Thanks to @Wish39.
LG Stylo 6 Crossflashing:
To crossflash LG Stylo 6 using LG K71 Android 12 firmware see this. Thanks to @Wish39.
LG V50 Crossflashing:
I had two LG V50 (LMV450) to which I flashed Korean Andorid 12 using the method mentioned in the first post. I cannot guarantee that it will work on every V50. After corssflashing I found out that one of them had the problem of draining battery due to not getting into deep sleep mode. To overcome the issue, I reflashed it via "Chip Erase" this time, and then again reflashed it but in the same way mentioned for crossflashing in the first post. Of course, I had created backup and at the end I restored LUN5 partitions.
Hi bro =)
This is the thread I found: https://forum.xda-developers.com/t/getting-access-to-recovery-combination-ftm-mod.4220523/
Thanks, netmsm and kt-froggy for the guides.First off, big THANKS to the OP (netmsm) and other people who contributed to this thread and made this guide very clear and useful!
So, after perusing this thread for a long time, trying to understand the ins and outs of the process and any possible snafus, I decided to take the plunge after the Open_CA A12 (40a) got released recently, and to flash it onto my G8 originally from US Cellular. The crossflash went smoothly with no issues at all. A nice surprise was that the BL remained unlocked - I was prepared to go through the whole unlocking process again before rooting, but didn't have to. I got the empty S/N (easy fix), and the infamous NT-Code error. This is where I got stuck for a while. I tried fixing it by editing the cust_path_mapping.cfg file as suggested in the thread. The problem is that I couldn't save the changes in that stupid file by using ANY root explorer/editor! Tried half a dozen different apps with no luck at all. BTW, anyone has any ideas what I may have been doing wrong?? Yes, I am properly rooted with Magisk.
Anyway... Everything worked fine on the phone, but that lame error was really getting under my skin - I could have ignored it, but I hated not being able to get rid of it. So... After more reading, I came across some info on hex-editing the FTM partition (in a totally unrelated topic). The NT-Code in FTM binary is stored at the offset 00014000. My error message was referring to the code "FFFFFF,85". The original cust_path_mapping.cfg file (which I couldn't edit) had a line referring to "FFFFFF,82". So, having all backups available, I decided, just for the heck of it, to change the last digits of the NT-Code in the FTM partition to match the "82" listed in the file. What could go wrong? I can always restore a backup... After flashing the edited FTM in QFIL, rebooted the phone, and - bingo! The NT-Code error was gone, and the phone was still fully functional. This was my happy face after spending a good hour and a half trying to get rid of it, and finally succeeding:
Cheers, and thanks again for all the info!
I do not understand what your problem is, sorry.Im getting error 0x6004
I tried Edit: I backed up and erased these partitions in addition: boot_a, boot_b, vendor_a, vendor_b, product_a, product_b and it seemed to work afterwards. this too still didnt work
what I had happened to me, I unlocked the bootloader first then I got twrp with magisk running then I wanted to upgrade to 12 and now I can;t do it
by mistake I also flashed verizon kdz on it too, since mine is sprint, please help
1. Make a backup of LUN5 partitions.I bought this LG v50 and it is a Sprint phone I use the guide to root and unlock the bootloader for the TWRP and magisk while running on Android 11
On telegram I found Android 13 running rom I was told to upgrade to Android 12 and then flash the rom because it will not work with Android 11
I found your post and I was trying to cross flash from Android 11 to 12 using your method but I could not do it because I was getting that 0x60004 error about on your same post people suggest if I erase boot vendor product partition as well that I will not come I try that too and it didn't work I was still getting that same error I try different LG up
Someone told me on the telegram group just flash Android 12 kdz on it since I could not cross flash from 11:00 to 12:00 using your method
Without realizing that I had Sprint I used Verizon Android 12 kdz using LG up
Now when I try to boot up it just flashed lgv 50 logo and goes into the boot loop
I can still go into edl mode also I can go to download mode and I try to use unbrick guide to flash those files manually and after doing that phone does the same thing it would not boot just goes to the boot loop
So this is the situation I'm in