Pewdeadcake
Senior Member
hi, i faced the error in root explorer saying that read only file, any solution
hi, i faced the error in root explorer saying that read only file, any solution
You need to flash the engineering abl via QFIL, then enter fastboot and write the fastboot --disable-verity --disable-verification flash vbmeta_a vbmeta.imghi, i faced the error in root explorer saying that read only file, any solution
I tried all the steps, flashing was going well and it did allowed me to change the model from sprint to korean A11, but after reboot it says OPID mismatch!... what's wrong with this? anyone have sprint 20j kdz?
sure I had unchecked sid_a and sid_b
Hello netmsm, I wanted to try this on my g8x but I keep having this error message about a "sahara" protocol failed. Can you please help me and tell what I'm doing wrong? I share with you a ss of the message.
hola soy nuevo en esto y escribo español, podrias ayudarme mi celular es atyt g850um pero la version es g850um10o quiero actualizar ya sea android 10 o 11, me podrias ayudar de como lo lograste.El mío tampoco funciona.
Intento cambiar de AT&T a Open Canada.
Antes de esto, eliminé todos los archivos que mencionaste en QFIL y desmarqué sid_a y sid_b en LGUP.
Hola
Gracias a todos los demás chicos aquí que han hecho un desarrollo útil para domar esta hermosa =)
LG ha hecho las cosas difíciles al flashear roms personalizadas e incluso en stock con esta nueva cosa OPID. Nos evita el parpadeo cruzado, pero hemos podido usar TWRP y cambiar el sistema y algunas otras particiones para tener una rom diferente. Tuvimos que hacer algunos cambios en la partición OP usando el editor HxD.
Pero ahora, a través de este tutorial, podemos actualizar cualquier rom sin la necesidad de cambiar OPID en la partición OP. Además, no es necesario rootear o desbloquear el cargador de arranque.
Tuve éxito al hacer esto en algunos G8 (LMG820UM), ¡pero NO SOY RESPONSABLE DE NINGÚN DAÑO A SU TELÉFONO!
Si continúa leyendo las siguientes instrucciones, realmente acepta el riesgo.
Change the attribute of "UI_Config.lgl" to read only for the first issue.I initially had all options on LGUP but at some point had only 3 (refurbish. Upgrade and FOTA upgrade) I just went ahead and hit the start button and it went through no mismatch error or something....but the most issue I got is device blinking on and off for a whole while in between the first greet message of "LG V50 Thinq"
no way changed attributes to read-only yet I still have 3 options to choose fromChange the attribute of "UI_Config.lgl" to read only for the first issue.
I had no V50 and also I didn't do this on G8 but you can try to flash "vbmeta" on both sides, a and b using the below code (supposed your vbmeta has .bin extension). It may help!
Remember to use engineering bootloader. And, you can dump vbmeta from your phone.fastboot --disable-verity --disable-verification flash vbmeta_a vbmeta_a.bin
fastboot --disable-verity --disable-verification flash vbmeta_b vbmeta_a.bin
Download "UI_Config.lgl" from requirement and follow preparation then before running LGUP change the attrib.no way changed attributes to read-only yet I still have 3 options to choose from
Hi. I am using LG V500N LgU+ with imei 0 and ntcode 0. I fixed imei 0 according to the instructions of bro netmsm, now only ntcode 0 so no mobile signal. I changed the vbmeta file for both partitions a and b in mode 9008 but could not overwrite another cust_path_mapping.cfg file.You need to flash the engineering abl via QFIL, then enter fastboot and write the fastboot --disable-verity --disable-verification flash vbmeta_a vbmeta.img
and
fastboot --disable-verity --disable-verification flash vbmeta_b vbmeta.img
or try to flash my Vbmeta already patched. As I said, I have lg v500n lgu +
do not forget to make a backup of the native abl. you must restore it after you finish working in fastboot
Someone has been successful to modify NT-Code this way: Flash Korean A11. Dial *#546368#*500#. Go to SVC Menu > MID Info and change NT-Code.Hi. I am using LG V500N LgU+ with imei 0 and ntcode 0. I fixed imei 0 according to the instructions of bro netmsm, now only ntcode 0 so no mobile signal. I changed the vbmeta file for both partitions a and b in mode 9008 but could not overwrite another cust_path_mapping.cfg file.
Do you have a telegram? Help me. Thank you very much.
Sorry, I used google translate to answer you because my english is bad.
I tried changing in MID info but only IMEI can be changed but not NTCODE. So I'm just trying to follow your guide marahuan. If you do it your way marahuan and fix the mobile signal, that would be great.Someone has been successful to modify NT-Code this way: Flash Korean A11. Dial *#546368#*500#. Go to SVC Menu > MID Info and change NT-Code.
I finally got it working but device is bricked I think just keeps blinking on and off on the LG V50 logo and does nothing repeatedly. I've tried using stock ROM to flash no way about four of them any help on thisDownload "UI_Config.lgl" from requirement and follow preparation then before running LGUP change the attrib.
This is my isssue as of now... i tried the crossflash followed all instructions laid out but ended up bricking my device its a V500N30c-SKT-KR I tried using a V500N30b file to cross flash though I didn't get the option for PARTITION.DL so I just used the refurbish. i finally got all options on LGUP to work (which you gave) and I tried redoing the steps no way still stuck on a blicking screen someone suggested the file is bad and I should flash original rom with same region and code which I did no way (somehow I think the file got corrupted while I downloaded) am getting an A10 file with same region. i pray this works and downgrade me else am F*CKED. plx advice anyone on how to get my device back to live (still got download and EDL mode working) got the firmware from https://lgrom.com/firmware/LMV500N/SKT/V500N30C_00/9310 (hope am not breaking anything posting a direct link)
Try Korean A9.I finally got it working but device is bricked I think just keeps blinking on and off on the LG V50 logo and does nothing repeatedly. I've tried using stock ROM to flash no way about four of them any help on this
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!
Hey good for you, so the Open a11 must be the Kor version right? Either way, could u do a big favor and try to get to recovery? Of course don't erase anything, but just verify you can get to the recovery screen?
thnx!