Related
Hi i recently tried to install a recovery from rom manager, but it installed one for g2x so then nothing could mount in recovery and when i tried to flash, something failed and now my device is bricked. I then found this guide http://forum.xda-developers.com/showthread.php?t=1229407&page=5 which i was able to recognise my device as a NVIDIA usb boot recovery drive but every time i press flash-recovery.bat and chose the partition, it says nvflash is not recognised as a command.... and whenever i press nvflash.exe itself, the cmd window appears for one second and it disappears. The package has all the drivers for nvflash but it doesnt friggin work. HELP
You need to flash an entire rom with nvflash, because you messed up the partition table (p990 and p999 have different partitions). With this guide you'll flash only the recovery...
After that you need to flash a proper baseband
Have you a g2x or an o2x?
iliatay said:
and whenever i press nvflash.exe itself, the cmd window appears for one second and it disappears. The package has all the drivers for nvflash but it doesnt friggin work. HELP
Click to expand...
Click to collapse
I have the same problem as him. Anyhelp?
I think you may try to reflash your device with the original firmware (KDZ file) which you can download from LG. Whole process is described in here:
http://forum.xda-developers.com/showpost.php?p=18946763
Please note that recently LG has changed something in their tools and now you have to "fool" them to do what you want them to. Please see this thread for details:
http://forum.xda-developers.com/showthread.php?t=1473781
Hope this will help you.
if it says that nvflash is not a recognised command, then edit the .bat to point to your nvflash.exe instead of just saying nvflash. (C:\path\to\your\nvflash.exe)
langhaardack said:
if it says that nvflash is not a recognised command, then edit the .bat to point to your nvflash.exe instead of just saying nvflash. (C:\path\to\your\nvflash.exe)
Click to expand...
Click to collapse
u can try this http://forum.xda-developers.com/showthread.php?t=1498021
i have tryed to ease the things to understand.
i had the same problem.
i downloaded these files:
http://uploaded.to/file/dkq74mlh
http://uploaded.to/file/2azotnvs
unpacked the files (important is that you put all files from the driver zip in one folder)
click volume + and volume - while connecting to your computer and it will recognize it
You go to device manager, right click on the apx ,update driversoftware, search on the computer for driver software, choose the folder you've put the driver files
then you can start flash.bat
Warning: Use this at your own risk. I’m not responsible for any damages that may happen due to using this guide.
Problem:
LG L90 stuck at LG Boot Logo;
Cannot enter download mode;
Stuck at factory reset screen (factory reset processing) and cannot enter recovery;
Cannot enter fastboot mode;
Cannot enter qhsusb mode, or Qualcomm 9008 mode;
Attention: All the unbricking process is made WITHOUT the battery in the phone.
If your device is recognized in device manager as qhsusb_bulk or Qualcomm HS-USB QDloader 9008 jump to part 2.
Part 1 – Put the phone in qhsusb mode:
1.1 Disassembly the phone: Vídeo
1.2 Find the Test Point;
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
(Compatible whith the folloing models: D400h, D400hn, D405, D405h, D405n, D405tr, D410, D410h, D410hn, D415, D415rd)
1.3 Connect the usb cable to the device (don’t connect it to pc yet);
1.4 Prepare the Test Point wires;
(I personally use an usb extension)
1.5 Short the phone resistor;
1.6 Connect the usb cable to pc;
1.7 Wait until Windows to recognize the device;
1.8 Disconnect the Test Point;
Now you should have the phone in qhsusb mode (Device Manager shows “QHSUSB_BULK” or “Qualcomm HS-USB QDloader 9008”).
If the phone doesn’t get recognized repeat this steps again.
If you see “Qualcomm HS-USB QDloader 9008” in Device Manager jump to the part 2;
If you see “QHSUSB_BULK” in Device Manager follow the next steps:
1.1.1 Download L90_Drivers.zip; (https://3r0xub.s.cld.pt)
1.1.2 Install the DriverL90;
1.1.3 If Windows can’t install it properly, restart the pc and press F8 repeatedly, a boot menu will appear, select "Disable Driver Signature Enforcement". Then you need to repeat everything from the beginning (Step 1.1);
1.1.4 Even if you can’t install it properly, try to install the AlternativeDriver. Then you need to repeat the whole process from the beginning (Step 1.1);
Part 2 – Restore Phone files:
2.1 Unzip L90_Hardbrick.zip; (https://ntqyw2.s.cld.pt)
2.2 Start boarddiag (b2b.exe);
2.3 Choose “W7 G2MDS (MSM8226)” Chipset;
2.4 Choose Port according to the port you see in the Device Manager;
2.5 Select your “Target Dir”;
2.6 Check “AP check”;
2.7 Check “EMMC”;
2.8 Press “START” button;
2.9 After some time you should see “PASS” in AP and EMMC. Then you just need to check “RESTORE BOOT IMG” and flash the files in this order:
1- aboot;
2- BackupGPT;
3- boot;
4- laf;
5- PrimaryGPT;
6- recovery;
7- rpm;
8- tz;
9- sbl1;
After flashing all the files remove the usb cable, put the phone back together, and turn it on. Now you should have the phone working again.
If you get "device was not found in dload trying flash programmer" error, go to Device Manager, expand the COM ports section, right click on the QDloader 9008 device, select Update Driver Software, follow the steps and point to the DriverL90. Reboot your PC and try the steps again. (Thanks @krusli)
If the phone hangs on LG Boot Logo, do a factory reset.
Factory Reset
1. Turn off the device;
2. Press and hold Volume Down key + Power Key;
3. Release Power key when LG logo appear;
4. Press and hold Power key again;
5. Release all keys when Factory Data Reset menu appears;
After that, you have to offline flash a stock KDZ for your L90 variant
Sources:
4pda (http://4pda.ru/forum/lofiversion/index.php?t575959-4560.html)
Credits to @TreQUS
This is probably the last resort for those that cannot get into any mode or get their phone recognized in PC.
Too bad a complete disassembly is necessary since the test points are in the front of the motherboard.
Hi, help me pls
Hi, i am beginner and i don't know how i can connect 'this point' to GND in first picture and when i should 'disconnect' it. Pls help coz i reallly need it
Anyway thanks for this guide it's my problem coz when i upgrade kitkat 4.4.2 to lollipop on lg l90 it's stop in 2/2 steps (7% and 'blue screen' with some bad parts) and i can't go to recovery,download,s/w mode
justM4gic said:
Hi, i am beginner and i don't know how i can connect 'this point' to GND in first picture and when i should 'disconnect' it. Pls help coz i reallly need it
Anyway thanks for this guide it's my problem coz when i upgrade kitkat 4.4.2 to lollipop on lg l90 it's stop in 2/2 steps (7% and 'blue screen' with some bad parts) and i can't go to recovery,download,s/w mode
Click to expand...
Click to collapse
For me, the easiest way to connect 'this point' to GND is as I show in the third picture, you can also get a piece of wire and connect the GND to the resistor, something like this:
Atention, be carefull to not connect the wire anywhere else than those two points.
To know when you should disconnect the wire, just turn on your computer speakers, when you hear a sound like when you attach a flash drive, it's time to disconnect the wire.
Thanks it's work now all good i can see qualcomm, but It's not my problem coz when i start phone its still the same problem i mean when LG logo dissapear automatically running android update 2/2 part and after several seconds i have error on black screen. I think i need format but i don t know how to do it, i saw yestarday i can go into s/w mode but lg flash tool don t help too with installing new android, on computer i have 4.4.2 and lollipop for lg l90 and i just can see after installing 4.4.2 in s/w mode i have rooted device but nothing more it s still the same problem with update. I think error say something about fonts.
Edit:
I install 4.4.2 drivers in lollipop from this hardbrick.zip and that s why perhaps its not working, i install drivers from lollipop and now i don t see update but just logo and i can t get into recovery, i try install now original KDZ
Drivers i mean it s just what we see in RESTORE BOOT IMG and i changed these file to lollipop
This Works But...
This Works but now in "About Phone" shows V120b-OP1-HQ.
Formerly V20b-SCA-XXX and now the frontal camera doesn't work!
How to Fix this?
Thi_Memoria said:
This Works but now in "About Phone" shows V120b-OP1-HQ.
Formerly V20b-SCA-XXX and now the frontal camera doesn't work!
How to Fix this?
Click to expand...
Click to collapse
I think you used the recovery images from a different model to launch download mode. The hardbrick file is nothing more than the partition tables and partitions images backups until the laf mmcblk0p15 of an unknown L90 variant (probably D410 dual-SIM without NFC). I believe you are able to fix this by rooting, unlocking the bootloader and flashing the whole bootstack from you model. When I say whole, I mean all partitions you'll find inside the KDZ of your model (except for GPT tables of course). A TWRP flashable zip can be easily setup for this task. Many people can face this problem but I think this is the solution, the hardbrick file is a good start so you can launch download mode and after flash the proper images of your exact model.
I'm not sure this will solve your problem, but I believe this is the cause. :good:
Tanks
F. Gacrux said:
I think you used the recovery images from a different model to launch download mode. The hardbrick file is nothing more than the partition tables and partitions images backups until the laf mmcblk0p15 of an unknown L90 variant (probably D410 dual-SIM without NFC). I believe you are able to fix this by rooting, unlocking the bootloader and flashing the whole bootstack from you model. When I say whole, I mean all partitions you'll find inside the KDZ of your model (except for GPT tables of course). A TWRP flashable zip can be easily setup for this task. Many people can face this problem but I think this is the solution, the hardbrick file is a good start so you can launch download mode and after flash the proper images of your exact model.
I'm not sure this will solve your problem, but I believe this is the cause. :good:
Click to expand...
Click to collapse
Ok, I have the KDZ my unpacked device. and it contains these files; aboot abootb BackupGPT boot cust factory laf modem persist PrimaryGPT rct recovery rpm rpmb SBL1 sbl1b sDI system tz TZB all accompanied with a numbering system and divided 17 part example: system_933888 system_1197064 system_1201176 tz_150528 tzb_157696 etc ... What should I do?
Whats your variant and what kdz you are trying to flash (kk or ll)? If your bootloader is unlocked and you have TWRP installed, I can arrange the flashable zip for you, all you'll have to do it's to drag and drop the files into the zip.
The multiple system binaries can be merged in the LG Firmware Extract, there is a button to merge all in a single img file, this one can also be used to flash your system partition.
Tanks again
F. Gacrux said:
I think you used the recovery images from a different model to launch download mode. The hardbrick file is nothing more than the partition tables and partitions images backups until the laf mmcblk0p15 of an unknown L90 variant (probably D410 dual-SIM without NFC). I believe you are able to fix this by rooting, unlocking the bootloader and flashing the whole bootstack from you model. When I say whole, I mean all partitions you'll find inside the KDZ of your model (except for GPT tables of course). A TWRP flashable zip can be easily setup for this task. Many people can face this problem but I think this is the solution, the hardbrick file is a good start so you can launch download mode and after flash the proper images of your exact model.
I'm not sure this will solve your problem, but I believe this is the cause. :good:
Click to expand...
Click to collapse
So... I flash all available partitions KDZ and yet this V20b - OP1 -HQ the only partition that I found in KDZ was the " MISC " would be the problem ? I take this partition and flashing by fastboot ? I have unlocked bootloader and TWRP recovery and fastboot mode too!
I have another D410hn! Maybe i make backup the misc partition and flash on my device!
---------- Post added at 03:59 AM ---------- Previous post was at 03:51 AM ----------
F. Gacrux said:
Whats your variant and what kdz you are trying to flash (kk or ll)? If your bootloader is unlocked and you have TWRP installed, I can arrange the flashable zip for you, all you'll have to do it's to drag and drop the files into the zip.
The multiple system binaries can be merged in the LG Firmware Extract, there is a button to merge all in a single img file, this one can also be used to flash your system partition.
Click to expand...
Click to collapse
So... My variant is D410hn Brazil V20b Lollipop! Here the link to my kdz: csmgdl.lgmobile. com/dn/downloader.dev?fileKey=FW6332R032URAYPC7CBB62W/D410hn20b_00.kdz
Thi_Memoria said:
So... I flash all available partitions KDZ and yet this V20b - OP1 -HQ the only partition that I found in KDZ was the " MISC " would be the problem ? I take this partition and flashing by fastboot ? I have unlocked bootloader and TWRP recovery and fastboot mode too!
I have another D410hn! Maybe i make backup the misc partition and flash on my device!
---------- Post added at 03:59 AM ---------- Previous post was at 03:51 AM ----------
So... My variant is D410hn Brazil V20b Lollipop! Here the link to my kdz: csmgdl.lgmobile. com/dn/downloader.dev?fileKey=FW6332R032URAYPC7CBB62W/D410hn20b_00.kdz
Click to expand...
Click to collapse
Hi @Thi_Memoria sorry , I've been a little busy , and so I've not been able to watch this thread as much as I wanted.
Now that you have the phone working you have to flash (offline) the KDZ suitable for your device.
Here you can see how to flash your kdz: http://forum.xda-developers.com/lg-l90/general/guide-flash-stock-kdz-offline-lg-l90-t2803479
Thi_Memoria said:
So... I flash all available partitions KDZ and yet this V20b - OP1 -HQ the only partition that I found in KDZ was the " MISC " would be the problem ? I take this partition and flashing by fastboot ? I have unlocked bootloader and TWRP recovery and fastboot mode too!
I have another D410hn! Maybe i make backup the misc partition and flash on my device!
---------- Post added at 03:59 AM ---------- Previous post was at 03:51 AM ----------
So... My variant is D410hn Brazil V20b Lollipop! Here the link to my kdz: csmgdl.lgmobile. com/dn/downloader.dev?fileKey=FW6332R032URAYPC7CBB62W/D410hn20b_00.kdz
Click to expand...
Click to collapse
Mine is also the brazilian variant D410hn.
The files you flashed to get access to download mode are from the Asian CIS D410 (dual-SIM without NFC).
I unlocked the actual D410hn bootloader and made the proper bootstack for our version.
Make sure to be using TWRP 2.8.7.0, I didn't tested in older versions or CWM.
Bootstack - this flashes all D410hn partitions, except system: http://www.mediafire.com/download/mzc4qt5a7r79rcl/Bootstack_D410hn_Lollipop_v20b.zip
If you are willing to return to Lollipop (boot/system). This is the flashable android zip to install system without KDZ: http://www.mediafire.com/download/i2ijgbwa07o2ugf/Flashable_D410hn_Stock_Lollipop_v20b.zip
Before flashing the big lollipop (second zip), wipe data/cache/dalvik/system, since it's a huge file, It takes around 10 minutes to flash. Also, after that flash SuperSU: http://download.chainfire.eu/696/SuperSU/UPDATE-SuperSU-v2.46.zip then reboot and check if everything is back to normal.
Solved?!
neverdies said:
Hi @Thi_Memoria sorry , I've been a little busy , and so I've not been able to watch this thread as much as I wanted.
Now that you have the phone working you have to flash (offline) the KDZ suitable for your device.
Here you can see how to flash your kdz: http://forum.xda-developers.com/lg-l90/general/guide-flash-stock-kdz-offline-lg-l90-t2803479
Click to expand...
Click to collapse
Ok I know about Flash KDZ Updater and I found out where the problem is! he is in MISC partition and CUST partition, I edited files CUST partition with Root Explorer and now is normal and front camera working now! I edited these files: cust.prop cust_grup_mapping.cfg and cust.prop of open_sca folder. Tanks for All!:good:
The flashable bootstacks I made for D410hn also flash CUST partitions, this would have solved your problem too. In fact flashes all partitions in kdz, except boot and system that are in another different zip. With those two files you can flash everything in TWRP just like lg kdz would do if you have your partition table ok.
Help
F. Gacrux said:
The flashable bootstacks I made for D410hn also flash CUST and MISC partitions, this would have solved your problem too. In fact flashes all partitions in kdz, except boot and system that are in another different zip. With those two files you can flash everything in TWRP just like lg kdz would do if you have your partition table ok.
Click to expand...
Click to collapse
So... I flash this Bootstack_D410hn_Lollipop_v20b and my imei is now "0"
i'm downloading the big zip now
Thi_Memoria said:
So... I flash this Bootstack_D410hn_Lollipop_v20b and my imei is now "0"
i'm downloading the big zip now
Click to expand...
Click to collapse
Weird, because I flashed kk and ll bootstack multiple times between kk, ll, cm11 and cm 12.1 flashes and my imei remains the same. Try to flash system and boot of the big zip.
Edit: Sorry for the wrong info, it doesn't flash misc partition since it do not exist in kdz, I see you modified some files in misc partition, this might be the cause for your lost imei.
For reference, my cust.prop at cust root folder is
# Define cupss root dir from NT Code or BUYER
ro.lge.capp_cupss.rootdir=/cust
# Define CUPSS group in SWOV
ro.lge.cupssgroup=OP1-HQ
# Define Google Client ID
ro.com.google.clientidbase=android-om-lge
ro.com.google.clientidbase.ms=android-om-lge
ro.com.google.clientidbase.am=android-om-lge
ro.com.google.clientidbase.gmm=android-om-lge
ro.com.google.clientidbase.yt=android-om-lge
ro.lge.callduration=1
cust_group_mapping.cfg
ro.lge.cupssgroup=OP1-HQ
cust.prop at open_sca folder:
# Define cupss root dir from NT Code or BUYER
ro.lge.capp_cupss.rootdir=/cust/OPEN_SCA
# Define target operator/country/region
ro.build.target_operator=OPEN
ro.build.target_country=SCA
ro.build.target_region=SCA
# Default language
ro.product.locale.region=BR
ro.product.locale.language=pt
ro.build.default_country=BR
# Define Google Client ID
ro.com.google.clientidbase=android-om-lge
ro.com.google.clientidbase.ms=android-om-lge
ro.com.google.clientidbase.am=android-om-lge
ro.com.google.clientidbase.gmm=android-om-lge
ro.com.google.clientidbase.yt=android-om-lge
# Define SWV from CUPSS : Important for releasing Event Version
# Define swversion property when release official version
ro.lge.swversion=D41020b
ro.lge.swversion_short=V20b
ro.lge.swversion_rev=0
#ro.lge.swversion_svn=0
# Define swv_date property when the version date need to fix as the specific date
#ro.lge.swv_date=DEC-05-2013
ro.lge.opensw=SCA-XXX
# Define CUPSS group in SWOV
ro.lge.cupssgroup=OP1-HQ
# Define call duration feature
ro.lge.callduration=1
# Define handwriting
ime_handwriting_apply=false
ime_trace_apply=false
ime_trace_menu=false
# Define cust language set
ro.lge.custLanguageSet=true
# Cell Broadcast scenario
persist.sys.cust.cbinfo_not_bar=true
# Enable MLT at SetupWizard
persist.sys.mlt_swupdt=1
If nothing works, try to flash the foreign d410 lollipop bootstack: http://forum.xda-developers.com/lg-l90/development/bootstack-kk-l-l90-t3118632 you flashed another variant unbrick images I believe some "unique" partitions were overwritten by this flash and your phone no longer is a d410hn anymore at software level.
Nothing...
F. Gacrux said:
Weird, because I flashed kk and ll bootstack multiple times between kk, ll, cm11 and cm 12.1 flashes and my imei remains the same. Try to flash system and boot of the big zip.
Edit: Sorry for the wrong info, it doesn't flash misc partition since it do not exist in kdz, I see you modified some files in misc partition, this might be the cause for your lost imei.
For reference, my cust.prop at cust root folder is
# Define cupss root dir from NT Code or BUYER
ro.lge.capp_cupss.rootdir=/cust
# Define CUPSS group in SWOV
ro.lge.cupssgroup=OP1-HQ
# Define Google Client ID
ro.com.google.clientidbase=android-om-lge
ro.com.google.clientidbase.ms=android-om-lge
ro.com.google.clientidbase.am=android-om-lge
ro.com.google.clientidbase.gmm=android-om-lge
ro.com.google.clientidbase.yt=android-om-lge
ro.lge.callduration=1
cust_group_mapping.cfg
ro.lge.cupssgroup=OP1-HQ
cust.prop at open_sca folder:
# Define cupss root dir from NT Code or BUYER
ro.lge.capp_cupss.rootdir=/cust/OPEN_SCA
# Define target operator/country/region
ro.build.target_operator=OPEN
ro.build.target_country=SCA
ro.build.target_region=SCA
# Default language
ro.product.locale.region=BR
ro.product.locale.language=pt
ro.build.default_country=BR
# Define Google Client ID
ro.com.google.clientidbase=android-om-lge
ro.com.google.clientidbase.ms=android-om-lge
ro.com.google.clientidbase.am=android-om-lge
ro.com.google.clientidbase.gmm=android-om-lge
ro.com.google.clientidbase.yt=android-om-lge
# Define SWV from CUPSS : Important for releasing Event Version
# Define swversion property when release official version
ro.lge.swversion=D41020b
ro.lge.swversion_short=V20b
ro.lge.swversion_rev=0
#ro.lge.swversion_svn=0
# Define swv_date property when the version date need to fix as the specific date
#ro.lge.swv_date=DEC-05-2013
ro.lge.opensw=SCA-XXX
# Define CUPSS group in SWOV
ro.lge.cupssgroup=OP1-HQ
# Define call duration feature
ro.lge.callduration=1
# Define handwriting
ime_handwriting_apply=false
ime_trace_apply=false
ime_trace_menu=false
# Define cust language set
ro.lge.custLanguageSet=true
# Cell Broadcast scenario
persist.sys.cust.cbinfo_not_bar=true
# Enable MLT at SetupWizard
persist.sys.mlt_swupdt=1
If nothing works, try to flash the foreign d410 lollipop bootstack: http://forum.xda-developers.com/lg-l90/development/bootstack-kk-l-l90-t3118632 you flashed another variant unbrick images I believe some "unique" partitions were overwritten by this flash and your phone no longer is a d410hn anymore at software level.
Click to expand...
Click to collapse
Nothing work... imei=0 imeisv=0
Thi_Memoria said:
Nothing work... imei=0 imeisv=0
Click to expand...
Click to collapse
I took a look into the unbrick images you used and I could identify that they came from the D410 (dual sim no nfc) v10d kitkat. I would try this two things:
1 - Flash D410 (dual sim no nfc) kitkat bootstack and CM11 (since it's a smaller file, just to test and see if you have you imei back).
If it don't work:
2 - Return stock lg recovery and flash KDZ via LG Flash Tools in emergency mode.
You can extract the binary from the KDZ (LG Firmware Extract, extrack kdz, then dz and extract the recovery_numbers.bin), name it recovery.bin, put in the root of your microSD and flash in terminal or adb with:
dd if=/storage/external_SD/recovery.bin of=/dev/block/platform/msm_sdcc.1/by-name/recovery
Or use Jrummy ROM Installer.
Then follow this guide: http://forum.xda-developers.com/lg-l90/general/guide-flash-stock-kdz-offline-lg-l90-t2803479
I have 2 L90 with the unlocked bootloader I made, I flashed the bootstacks hundred times to go between almost all custom roms available here in xda and stock and never faced this problem, probably something changed when you got the hard brick and flashed the d410 l90 variant unbrick images so you can never change your bootstack to d410hn again, I never flashed other variant files in my two L90 and they both are ok.
If nothing more works, unfortunately, I believe the only way is to make the test point again and redo the whole process :crying:
OK
F. Gacrux said:
I took a look into the unbrick images you used and I could identify that they came from the D410 (dual sim no nfc) v10d kitkat. I would try this two things:
1 - Flash D410 (dual sim no nfc) kitkat bootstack and CM11 (since it's a smaller file, just to test and see if you have you imei back).
If it don't work:
2 - Return stock lg recovery and flash KDZ via LG Flash Tools in emergency mode.
You can extract the binary from the KDZ (LG Firmware Extract, extrack kdz, then dz and extract the recovery_numbers.bin), name it recovery.bin, put in the root of your microSD and flash in terminal or adb with:
dd if=/storage/external_SD/recovery.bin of=/dev/block/platform/msm_sdcc.1/by-name/recovery
Or use Jrummy ROM Installer.
Then follow this guide: http://forum.xda-developers.com/lg-l90/general/guide-flash-stock-kdz-offline-lg-l90-t2803479
I have 2 L90 with the unlocked bootloader I made, I flashed the bootstacks hundred times to go between almost all custom roms available here in xda and stock and never faced this problem, probably something changed when you got the hard brick and flashed the d410 l90 variant unbrick images so you can never change your bootstack to d410hn again, I never flashed other variant files in my two L90 and they both are ok.
Click to expand...
Click to collapse
OK i am download this now and i have the cm11 installed on my device!
Thi_Memoria said:
OK i am download this now and i have the cm11 installed on my device!
Click to expand...
Click to collapse
Make sure to flash kitkat recovery if you are using kitkat bootstack.
hi to all guys, I would like to draw your attention to what happened to me, and possibly know how to restore.
I am owner of a lg l90 model d405n, wanting to unlock the bootloader I used an application that I would have to just unlock the bootloader and install a modified recovery.
Actually 'cell after this hack is pretty much dead, he would not turn either.
I started looking for various tools and various programs in vain, the cell showed no signs of life.
Then, now giving it up for lost, I tried to go for broke, I low-level formatted, and then with an application (umbrick) I could flesciare boot and everything else. Now the cell was lit and was also in mode 'upgrade download.
I downloaded the firmware of KDZ 405 and I tried to use flash tool but the procedure is always blocked to 2%, giving an error.
With the tool of 'LG blatantly that I discovered the phone was identified as d410, exhausted by the various trials do not go into port I wanted to download the KDZ model 410d and, as if by magic, flash tool worked! I installed the latest version and the phone works wonders!
So now I have a cell phone with firmware that is not his (among other things the 410d is also dual sim).
I would like to restore its system orifginale, that of the 405, but I'm afraid to do other **** ....
I hope someone can help me out
sebasrul21 said:
hi to all guys, I would like to draw your attention to what happened to me, and possibly know how to restore.
I am owner of a lg l90 model d405n, wanting to unlock the bootloader I used an application that I would have to just unlock the bootloader and install a modified recovery.
Actually 'cell after this hack is pretty much dead, he would not turn either.
I started looking for various tools and various programs in vain, the cell showed no signs of life.
Then, now giving it up for lost, I tried to go for broke, I low-level formatted, and then with an application (umbrick) I could flesciare boot and everything else. Now the cell was lit and was also in mode 'upgrade download.
I downloaded the firmware of KDZ 405 and I tried to use flash tool but the procedure is always blocked to 2%, giving an error.
With the tool of 'LG blatantly that I discovered the phone was identified as d410, exhausted by the various trials do not go into port I wanted to download the KDZ model 410d and, as if by magic, flash tool worked! I installed the latest version and the phone works wonders!
So now I have a cell phone with firmware that is not his (among other things the 410d is also dual sim).
I would like to restore its system orifginale, that of the 405, but I'm afraid to do other **** ....
I hope someone can help me out
Click to expand...
Click to collapse
Did you still have your stock bootloader backup?
neverdies said:
Did you still have your stock bootloader backup?
Click to expand...
Click to collapse
unfortunately no
Stock bootloader (aboot and abootb) can be retrieved from your model KDZ. Every partition, except modemst1 & 2 can be re-flashed from the KDZ.
But the bootloader alone won't do anything, you must flash the entire bootstack of D405n, enter in Donwload Mode again and LG Flash Tool will allow you to flash the entire KDZ again in Emergency Mode without errors.
If you IMEI was lost or changed, it can be restored with other programs after.
F. Gacrux said:
Stock bootloader (aboot and abootb) can be retrieved from your model KDZ. Every partition, except modemst1 & 2 can be re-flashed from the KDZ.
But the bootloader alone won't do anything, you must flash the entire bootstack of D405n, enter in Donwload Mode again and LG Flash Tool will allow you to flash the entire KDZ again in Emergency Mode without errors.
If you IMEI was lost or changed, it can be restored with other programs after.
Click to expand...
Click to collapse
I thank you for the reply but unfortunately being very inexperienced I would need a guide more ' detailed . Excuse my English ( Google translation )
sebasrul21 said:
I thank you for the reply but unfortunately being very inexperienced I would need a guide more ' detailed . Excuse my English ( Google translation )
Click to expand...
Click to collapse
the premise that no sd card , I have to flash aboot ? adb push aboot.bin ? what are the steps for not briccarlo again ?
sebasrul21 said:
I thank you for the reply but unfortunately being very inexperienced I would need a guide more ' detailed . Excuse my English ( Google translation )
Click to expand...
Click to collapse
Answer so I can give you the proper response :
- Rooted?
- Unlocked bootloader?
- Custom recovery (twrp)?
- Variant model and country.
- Carrier model (if yes, which carrier)?
F. Gacrux said:
Answer so I can give you the proper response :
- Rooted?
- Unlocked bootloader?
- Custom recovery (twrp)?
- Variant model and country.
- Carrier model (if yes, which carrier)?
Click to expand...
Click to collapse
rooted yes
unlock bootloader I think not , how does a SEE?
custom recovery no
the phone is a lg d405n but now has become lg d410 dual sim version sw v20 - op1 - hq version Android 5.0.2 Italy no carrier
There is no way to know if the bootloader is unlocked, unless you make aboot partition image and hash check to compare with the original bootloader.
You have first to flash the hacked bootloader (aboot), since you don't know if it's unlocked, it won't hurt to flash again.
First enable USB debugging, at this point I assume you know how to do this.
Download the hacked aboot for D405n v20a:
http://www.mediafire.com/download/bn39rz7ojtosqm3/D405n_v20a_patched_aboot.zip (taken from this thread: http://forum.xda-developers.com/lg-l90/development/recovery-twrp2-7-1-0lgl90w7xxshoxx-t2826150)
Extract the zip and copy aboot.bin to the root of your sdcard. Open android terminal ou adb, take su permission and allow it on your phone screen, flash the hacked bootloader with:
If you copied to the external microSD: dd if=/storage/external_SD/aboot.bin of=/dev/block/platform/msm_sdcc.1/by-name/aboot
If you copied to the internal sd: dd if=/sdcard/aboot.bin of=/dev/block/platform/msm_sdcc.1/by-name/aboot
Now flash custom recovery. Download http://forum.xda-developers.com/devdb/project/dl/?id=13334 (taken from the same thread).
Copy TWRP_2.8.7.0_270615_L90.img to the root of your sdcard. To make things easier, rename it to recovery.img. Take su permission and flash with adb or android terminal with:
If you copied to the external microSD: dd if=/storage/external_SD/recovery.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery
If you copied to the internal sd: dd if=/sdcard/recovery.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery
Now reboot into twrp custom recovery, you can either send reboot recovery command in adb shell or terminal, or with your phone off, hold VOL - and PWR button, when lg logo appears, release and hold PWR button again until a blank screen appears, select YES twice (navigate with VOL buttons and PWR to select). Since now you are on custom recovery, twrp will boot instead a factory reset routine.
Download your D405n bootstack: https://www.androidfilehost.com/?fid=24052804347759484 (taken from this thread: http://forum.xda-developers.com/lg-l90/development/bootstack-kk-l-l90-t3118632)
Copy to your sdcard (do not extract the file). In TWRP recovery, select INSTALL and flash the zip.
Download your italy D405n v20a lollipop kdz: http://csmgdl.lgmobile.com/dn/downloader.dev?fileKey=FW932KU032N9A1T29B55QPQ/D405n20a_00.kdz
Follow this thread to flash with LG Flash Tool (if you already have usb drivers installed, start at step 5): http://forum.xda-developers.com/lg-l90/general/guide-flash-stock-kdz-offline-lg-l90-t2803479
If you face force closes after the first boot, do a factory reset (VOL- and PWR button, like I described before, but since now you are all stock, factory reset will be applied).
Now you are 100% on your italy d405n v20a lollipop.
F. Gacrux said:
There is no way to know if the bootloader is unlocked, unless you make aboot partition image and hash check to compare with the original bootloader.
You have first to flash the hacked bootloader (aboot), since you don't know if it's unlocked, it won't hurt to flash again.
First enable USB debugging, at this point I assume you know how to do this.
Download the hacked aboot for D405n v20a:
http://www.mediafire.com/download/bn39rz7ojtosqm3/D405n_v20a_patched_aboot.zip (taken from this thread: http://forum.xda-developers.com/lg-l90/development/recovery-twrp2-7-1-0lgl90w7xxshoxx-t2826150)
Extract the zip and copy aboot.bin to the root of your sdcard. Open android terminal ou adb, take su permission and allow it on your phone screen, flash the hacked bootloader with:
If you copied to the external microSD: dd if=/storage/external_SD/aboot.bin of=/dev/block/platform/msm_sdcc.1/by-name/aboot
If you copied to the internal sd: dd if=/sdcard/aboot.bin of=/dev/block/platform/msm_sdcc.1/by-name/aboot
Now flash custom recovery. Download http://forum.xda-developers.com/devdb/project/dl/?id=13334 (taken from the same thread).
Copy TWRP_2.8.7.0_270615_L90.img to the root of your sdcard. To make things easier, rename it to recovery.img. Take su permission and flash with adb or android terminal with:
If you copied to the external microSD: dd if=/storage/external_SD/recovery.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery
If you copied to the internal sd: dd if=/sdcard/recovery.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery
Now reboot into twrp custom recovery, you can either send reboot recovery command in adb shell or terminal, or with your phone off, hold VOL - and PWR button, when lg logo appears, release and hold PWR button again until a blank screen appears, select YES twice (navigate with VOL buttons and PWR to select). Since now you are on custom recovery, twrp will boot instead a factory reset routine.
Download your D405n bootstack: https://www.androidfilehost.com/?fid=24052804347759484 (taken from this thread: http://forum.xda-developers.com/lg-l90/development/bootstack-kk-l-l90-t3118632)
Copy to your sdcard (do not extract the file). In TWRP recovery, select INSTALL and flash the zip.
Download your italy D405n v20a lollipop kdz: http://csmgdl.lgmobile.com/dn/downloader.dev?fileKey=FW932KU032N9A1T29B55QPQ/D405n20a_00.kdz
Follow this thread to flash with LG Flash Tool (if you already have usb drivers installed, start at step 5): http://forum.xda-developers.com/lg-l90/general/guide-flash-stock-kdz-offline-lg-l90-t2803479
If you face force closes after the first boot, do a factory reset (VOL- and PWR button, like I described before, but since now you are all stock, factory reset will be applied).
Now you are 100% on your italy d405n v20a lollipop.
Click to expand...
Click to collapse
thank you so much I immediately start work hoping to do no harm
sebasrul21 said:
thank you so much I immediately start work hoping to do no harm
Click to expand...
Click to collapse
perdona un altra cosa, io in questo momento non uso schede microsd, come cambia questa: "if you copied to the external microSD: dd if=/storage/external_SD/aboot.bin of=/dev/block/platform/msm_sdcc.1/by-name/aboot
If you copied to the internal sd: dd if=/sdcard/aboot.bin of=/dev/block/platform/msm_sdcc.1/by-name/aboot"
sebasrul21 said:
perdona un altra cosa, io in questo momento non uso schede microsd, come cambia questa: "if you copied to the external microSD: dd if=/storage/external_SD/aboot.bin of=/dev/block/platform/msm_sdcc.1/by-name/aboot
If you copied to the internal sd: dd if=/sdcard/aboot.bin of=/dev/block/platform/msm_sdcc.1/by-name/aboot"
Click to expand...
Click to collapse
forgive one other thing , I do not at this time use cards microSD , as changes this
I gave you the two options, to copy the necessary files to microSD or internal memory, and what part you didn't understand?
If you don't use microSD, you must use the internal SD command (If you copied to the internal sd: dd if=/sdcard/... etc).
In android, both storage is called SD, the internal one that comes with the phone is the internal SD (sdcard0, media, sdcard, etc), the other one that you stick in the phone is the external SD (external_SD).
sebasrul21 said:
thank you so much I immediately start work hoping to do no harm
Click to expand...
Click to collapse
I run everything perfectly but in the end , When I go to run the flash tool gives me Error
"upgrade because of error ...
lg mobile support tool detects : sw : D41020A LG V500 version sw : V50020F are AVAILABLE agggiornamenti :crying:
sebasrul21 said:
I run everything perfectly but in the end , When I go to run the flash tool gives me Error
"upgrade because of error ...
lg mobile support tool detects : sw : D41020A LG V500 version sw : V50020F are AVAILABLE agggiornamenti :crying:
Click to expand...
Click to collapse
flash tool: Wait until software extraction is complete. stop
sebasrul21 said:
flash tool: Wait until software extraction is complete. stop
Click to expand...
Click to collapse
continues to be invecie 410 of 405
upgrade stopped due to an error
This is not possible. If you flashed D405n bootstack, there is no way LG Flash Tool recognize your phone as D410.
Are you running the LG Flash Tool mod or the official LG Mobile Support Tool? Are you using Download Mode set to Emergency?
On Read Phone Information, you don't need to run it (sometimes it hangs), and click on Clear phone Software update Registry on Select Country % Language Window.
Also check if the KDZ you downloaded is not corrupted. It's a common error the flash tool fail because the kdz is corrupted.
F. Gacrux said:
This is not possible. If you flashed D405n bootstack, there is no way LG Flash Tool recognize your phone as D410.
Are you running the LG Flash Tool mod or the official LG Mobile Support Tool? Are you using Download Mode set to Emergency?
On Read Phone Information, you don't need to run it (sometimes it hangs), and click on Clear phone Software update Registry on Select Country % Language Window.
Also check if the KDZ you downloaded is not corrupted. It's a common error the flash tool fail because the kdz is corrupted.
Click to expand...
Click to collapse
unfortunately so I assure you , I used the flash tool set to emergency and it always fails with the KDZ 405 , invecie loading the KDZ 410 installs easily
sebasrul21 said:
unfortunately so I assure you , I used the flash tool set to emergency and it always fails with the KDZ 405 , invecie loading the KDZ 410 installs easily
Click to expand...
Click to collapse
I followed step by step your guide, a KDZ files are not corrupt , I have tried several of the 405 does not work and no one , instead the KDZ 410 works .
The IMEI is zero
hello everybody
i've rooted my moto E4 plus, using this guide:
https://forum.xda-developers.com/moto-e4-plus/how-to/moto-e4-plus-guide-to-rooting-mediatek-t3668753
and everything worked well.. however - i would like to update my phone software, and i do not know what spell to cast now..
what is the best way to go now?
thanks
Restore stock firmware, that includes stock recovery.
ATTACK said:
Restore stock firmware, that includes stock recovery.
Click to expand...
Click to collapse
hi ATTACK, thanks for reply.
i've tried to restore scattered file (bunch of bin-s) using miracle box, but without success. it seams that miracle is not able to restore these files as phones firmware - or i am doing something wrong.
procedure:
i run miracle box, i choose adequate mtk version, i pick write mode, and select .txt (scatter file). in the same dir there are many .bin files..
what should i do?
thanks
vladimirnikolic said:
hi ATTACK, thanks for reply.
i've tried to restore scattered file (bunch of bin-s) using miracle box, but without success. it seams that miracle is not able to restore these files as phones firmware - or i am doing something wrong.
procedure:
i run miracle box, i choose adequate mtk version, i pick write mode, and select .txt (scatter file). in the same dir there are many .bin files..
what should i do?
thanks
Click to expand...
Click to collapse
i get messages:
Waiting for USB Port...
Set MediaTek PreLoader USB VCOM Port (COM7)
Please Hold "ON" to connect with the phone...
Connected to Phone.
CPU: MT6735 SW:0000 Ver: CB00
Downloading Boot8 ...
EMMC Size: 0x03A3E00000
Flash Type: EMMC
INT/EXT RAM Size: 0x0+0x0
Writing(Nand/eMMC)...
>>Error1: no 5A
.. update - i've tried with sp flash tool as well - but it seems that it cannot recognize the scattered file format. the software crashes when i try to load .txt file
Use fastboot to flash the .IMG files. There should be a guide somewhere. It's either here or in the Moto E4 fourm.
sp tools works fine form me.
Hi there
Thanks to all other guys here who have made helpful development to tame this beautiful =)
To crossflash models other than LG G8 please read post 3.
Before asking any question please read the troubleshooting section at the bottom of the page.
If you still need some specific help I would appreciate if you bring it up just in the thread instead of sending direct messages.
LG has made things difficult in flashing custom and even stock roms by this new OPID thing! It prevents us from crossflashing but we have been able to use TWRP and change the system and some other partitions to have a different rom. We had to make some changes into OP partition using HxD editor.
But now, through this tutorial, we're able to flash any rom without the need to change OPID in OP partition. Also, there is no need to root or unlock boot-loader.
I was successful to do this on some G8 (LMG820UM) but I AM NOT RESPONSIBLE FOR ANY HARM TO YOUR PHONE!
By continuing to read the following instructions you are actually accepting the risk.
IMPORTANT!
first, MAKE A FULL BACKUP OF ALL PARTITIONS; and I mean it!!!
at least, for your sake, make a backup of "modemst1, modemst2, fsg, fsc, ftm" partitions, for emergency.
Requirements
QPST and Qualcomm USB Driver (get)
LGE SM8150 Firehose (get)
LGUP 1.16.0.3 (get)
LGUP_Common.dll (get)
UI_Config.lgl (get)
LG Mobile Driver 4.4.2 (get)
Preparation
1. Install QPST and Qualcomm USB Driver.
2. Install LGUP.
3. Find the folder named "model" in the installation directory of LGUP, then Create a folder named "common" in the "model" folder.
4. Move "LGUP_Common.dll" and "UI_Config.lgl" into "common" folder. Change the attribute of "UI_Config.lgl" to read only.
5. Install LG Mobile Driver 4.4.2.
Steps
A)
1. Open QFIL.
2. Change "Storage Type" to UFS.
3. Select "Flat Build".
4. Browse for "LGE SM8150 Firehose" and pick it.
5. Now, connect the phone to PC and boot into EDL mode.
6. Open "Select Port" and select the phone, press OK.
7. In "Tools" open the "Partition Manager".
B)
!!!BE CAREFUL TO DO EXACTLY AS THE INSTRUCTIONS SAY OR YOU WILL BRICK THE PHONE!!!
1. Make a backup of and erase these 7 partitions: FTM, Modem_A, Modem_B, SID_A, SID_B, OP_A, OP_B.
1.1. You have to left-click on a partition then right-click on it and select "Manage Partition Data".
1.2. In the pop-up window, you have 4 choices: I. Erase (to erase data on the partition), II. Read Data (to dump or back up the partition), III. Load Image (to restore the partition), IV. Close (to close the window).
1.3. First dump/back up the partition by choosing "Read Data" then Erase it.
2. Close the "Partition Manager" window.
3. Wait for 5 seconds then press Vol- and Power until it restarts.
3.1. Immediately after rebooting, Release the Vol- and Power buttons and press Vol+ to get into Download Mode.
Note: Do not let the phone to begin to boot! If it begins to boot, it may regenerate the SID and FTM partitions data and so you need to redo the whole step B.
C)
1. Open LGUP.
2. Pick your favorite KDZ.
3. Select "PARTITION DL".
4. Press Start. And a pop-up window will appear. In this window you can select which partitions to be flashed.
5. Here, uncheck these partitions: SID_A and SID_B. It will make it able to bypass the OPID Mismatched Error.
6. If you are in Sprint or other platforms you will get the message whether to change the model or not. Of course you know what to do =)
after completing the process it will boot up in some minutes and before starting the customization it will do one restart. just be patient.
ERRORS, QUESTIONS, TROUBLESHOOTING
1. Can I crossflash V50, V60, G8X or other LG devices using this method?
I did it on V50. Maybe it'll work on your devices maybe won't. There's one way to find out; make backup and give it a try.
2. SN is gone, zero, etc.
Restore your original FTM.
3. I can't get into recovery.
Restore the original FTM.
4. I got NT-Code error.
It's been discussed many times in the thread and some solutions have been presented (such as this one, thanks to @animo214 and this, thanks to @kt-Froggy as well as this one, thanks to @StvOchi ). However, you can ignore it if the phone got network.
Note: You need to disable verity on the phone in advance otherwise changes in cust_path_mapping.cfg won't be saved.
5. IMEI is lost, zero, null etc.
Restore LUN5 partitions. If you have no backup it should be repaired using Octopus box. Go to 16.
6. I got "permanently locked" error.
This is because of IMPL lock and you have to restore LUN5 partitions. In case of having no backup you should use Octopus box.
7. All partitions are deleted accidentally.
Follow this instructions.
8. I need to get into PDM mode.
Unzip and restore the attached PDM to FTM partition. Remember, you need to restore your FTM to get into OS.
9. Can I use another phone's LUN5 backup?
NO.
10. Can I use another phone's FTM backup?
Yes. All partitions can be restored from another phone's backup except LUN5 partitions.
11. My phone is stuck in boot-loop.
Restore the original FTM and if it doesn't help redo the whole crossflash process and use a different KDZ this time.
12. Which KDZ is the best (for any matter of use)?
I do not know.
13. Can I crossflash from any source variant to Korean variant or vice versa?
Yes it is possible but you may get error on opening stock camera application because of hardware differences. There are some methods to solve the issue which you can search and find them.
14. Can I downgrade using this method?
Yes.
15. I erased partitions (ftm, op_a, op_b, modem_a, modem_b, sid_a, sid_b) but it still does not let me to crossflash.
Redo the whole process and this time make backup of and erase these partitions too, on both sides A and B: vendor, product, system, boot and userdata. Do not make backup of userdata partition.
16. How can I write IMEI?
A) Dump modem_a and create a copy of it. Then open it in UltraISO and remove IMEIPROT files from image folder. Save and restore it in place of modem_a and modem_b partitions.
B) Make backup of FTM and then flash or restore the PDM file (attached) into your ftm partition. Restart the phone; you'll get into PDM mode.
C) Open Tutty (attached). Select "Serial" in protocol and the proper port of your phone's modem driver. Click open. To test if you have selected the proper port number type "at" and hit enter it should respond"ok". Type the code at%imei=# (replace # with your IMEI) and hit enter. It doesn't matter you get "error" or "ok" after that, just check if IMEI is written via this code at%imei=?. If IMEI is written so you'll have the right MEID and ESN too.
D) Restore the original ftm and modem_a in place of modem_a and modem_b. Restart the phone.
I've already tested this method on V30, V50 and G8. Remember, if the phone has IMPL lock it'll throw "perm. locked" error even if you have written the IMEI.
17. I have lost GPT files of my LG G8, G8X, G8S, V50, etc. and Qfil partition manager does not show anything in the list.
You need to flash GPT files to your device with fh_loader (see this, part C). For that matter use KDZ_Tools to Extract DZ from a KDZ of your device. Then extract the DZ using -c at the end of extracting command. For example: unkdz -f FILE_NAME.kdz -c. It will extract all files besides all GPTs.
18. Which are the LUN5 partitions?
SM8150 has 7 physical partitions known as LUNs which are numbered from 0 to 6. Each LUN is split into several partitions. In Qfil Partition Manager you can see all partitions except those of LUN3 and LUN6 which are hidden. The number of LUNs are shown under the first column named LUN. Therefore, all partitions in front of number 5 are LUN5 partitions.
Some pictures of flashing my LMG820UM, unlocked from Sprint, into OPEN_CA 20j. In normal mode you cannot flash SPR_US to OPEN_CA which is shown in the pictures. But using this thread instruction it allows to flash, even it asks to change the model from SPR_US to OPEN_CA
Until performing the instructions, it shows the "id: 2(SPR_US)" on the Download Mode screen, but after that it cannot recognize the phone model id and shows "id: 0()"
Have fun ^_^
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.
Hey nice! It's great to have options. I'm currently using us Open OP on my Sprint device (of course totc changed). It's working fine and not sure of any reason to change.
Although, if we do get a11 firmware available, that will change things for sure.
Thanks, nice work!
great, thank you
netmsm said:
Some pictures of flashing my LMG820UM, unlocked from Sprint, into OPEN_CA 20j. In normal mode you cannot flash SPR_US to OPEN_CA which is shown in the pictures. But using this thread instruction it allows to flash, even it asks to change the model from SPR_US to OPEN_CA
Until performing the instructions, it shows the "id: 2(SPR_US)" on the Download Mode screen, but after that it cannot recognize the phone model id and shows "id: 0()"
Have fun ^_^
Click to expand...
Click to collapse
Idk when i opened lgup it's only have 3 option refurbished, upgrade n fota update
Azs5165 said:
Idk when i opened lgup it's only have 3 option refurbished, upgrade n fota update
Click to expand...
Click to collapse
You didnt follow preparation correctly I guess?
netmsm said:
Some pictures of flashing my LMG820UM, unlocked from Sprint, into OPEN_CA 20j. In normal mode you cannot flash SPR_US to OPEN_CA which is shown in the pictures. But using this thread instruction it allows to flash, even it asks to change the model from SPR_US to OPEN_CA
Until performing the instructions, it shows the "id: 2(SPR_US)" on the Download Mode screen, but after that it cannot recognize the phone model id and shows "id: 0()"
Have fun ^_^
Click to expand...
Click to collapse
What OPID does it get assigned once you boot the device? OPEN_CA?
AsItLies said:
Hey nice! It's great to have options. I'm currently using us Open OP on my Sprint device (of course totc changed). It's working fine and not sure of any reason to change.
Although, if we do get a11 firmware available, that will change things for sure.
Thanks, nice work!
Click to expand...
Click to collapse
Like the a11 korean one?
cloud1250000 said:
You didnt follow preparation correctly I guess?
Click to expand...
Click to collapse
I had tried with my lmg850um9 sprint,i accidentally erase entire flash before but i successfull flash with other g8x em kdz but get opid missmatched
Azs5165 said:
Idk when i opened lgup it's only have 3 option refurbished, upgrade n fota update
Click to expand...
Click to collapse
i got the same problem, just 3 options
Just did this successfully, thanks OP. If yer only getting partial options on lgup, remember from the OP, you HAVE to change the UI file to be READ ONLY (do it in properties).
I didn't get the 'change model' pop up, but still worked, although device is still seen as 'um' not 'qm'. My serial # is missing (that's a simple edit in ftm), but the imei is there.
Definitely worked though, now have us op with april security patch.
Will take a few mins to get a root explorer to see what totc says... that should be interesting
AsItLies said:
Just did this successfully, thanks OP. If yer only getting partial options on lgup, remember from the OP, you HAVE to change the UI file to be READ ONLY (do it in properties).
I didn't get the 'change model' pop up, but still worked, although device is still seen as 'um' not 'qm'. My serial # is missing (that's a simple edit in ftm), but the imei is there.
Definitely worked though, now have us op with april security patch.
Will take a few mins to get a root explorer to see what totc says... that should be interesting
Click to expand...
Click to collapse
How to make it?srry i cant understand
alright, G8x Sprint succesfully crossflashed to OPEN CA
Azs5165 said:
Idk when i opened lgup it's only have 3 option refurbished, upgrade n fota update
Click to expand...
Click to collapse
Sebastian Thiago said:
i got the same problem, just 3 options
Click to expand...
Click to collapse
Azs5165 said:
How to make it?srry i cant understand
Click to expand...
Click to collapse
Follow preparation.
cloud1250000 said:
What OPID does it get assigned once you boot the device? OPEN_CA?
Click to expand...
Click to collapse
AsItLies said:
Will take a few mins to get a root explorer to see what totc says... that should be interesting
Click to expand...
Click to collapse
Actually it doesn't change OPID. By not flashing SID partitions we can bypass checking OPID and hence the error.
I checked it now it was OPEN_CA.
Azs5165 said:
I had tried with my lmg850um9 sprint,i accidentally erase entire flash before but i successfull flash with other g8x em kdz but get opid missmatched
Click to expand...
Click to collapse
Follow the steps in part C.
netmsm said:
Actually it doesn't change OPID. By not flashing SID partitions we can bypass checking OPID and hence the error.
I checked it now it was OPEN_CA.
Click to expand...
Click to collapse
curious how the sprint v50 will react to this.. I`ll try this guide when korean A11 gets release.. I'll let you know..
Also.. if it doesn`t change OPID you would get OPID mismatched error on boot.. so..
cloud1250000 said:
Also.. if it doesn`t change OPID you would get OPID mismatched error on boot.. so..
Click to expand...
Click to collapse
If SID partitions are flashed then yes it will throw OPID Mismatched Error. This is why we suggest using "Partition DL" flashing method, unchecking SID partitions.
netmsm said:
If SID partitions are flashed then yes it will throw OPID Mismatched Error. This is why we suggest using "Partition DL" flashing method, unchecking SID partitions.
Click to expand...
Click to collapse
yes but it has to generate new one with proper OPID no? when you load download mode now, does it still says id: 0? i doubt that
cloud1250000 said:
yes but it has to generate new one with proper OPID no? when you load download mode now, does it still says id: 0? i doubt that
Click to expand...
Click to collapse
That's right it generates the original OPID in download mode.
It is probable that some or all data related to OPID are stored in Modemsts partitions to which the SID partition bridges the OPID check function, in boot process. All that we do is to destroy the bridge.
netmsm said:
That's right it generates the original OPID in download mode.
It is probable that some or all data related to OPID are stored in Modemsts partitions to which the SID partition bridges the OPID check function, in boot process. All that we do is to destroy the bridge.
Click to expand...
Click to collapse
can you check which mcfg is used? (field test > mcfg status)