Hello,
I tried to install CWM and bricked the phone
Model: LG L90 D410
It appeared the error:
ERROR Boot Certification Verify, and Logo LG.
So I tried using the download mode to use KDZ,
when I enter the Download Mode, the error persists (see printscreen) and the screen turns off.
LGFlashTool and windows device manager does not recognize the phone, all drives have been updated.
plz help.
Additional information:
Hard reset works, but after doing the reset, the problem is the same. Boot error and Download Mode with Secure Boot Error (attached image) .
PC is still not recognizing the phone and nothing i can do.
Sorry my English
Read: http://forum.xda-developers.com/lg-l90/help/secure-boot-error-boot-certification-t2895538
F. Gacrux said:
Read: http://forum.xda-developers.com/lg-l90/help/secure-boot-error-boot-certification-t2895538
Click to expand...
Click to collapse
For me does not work because I can't flash KDZ, I do not have access to the Download Mode for this (see image).
And I can't do this http://forum.xda-developers.com/lg-l90/general/guide-fastboot-l90-d415-t2827825 because I don't have access to the phone (does not appear connected to PC).
Maybe this: http://forum.xda-developers.com/lg-l90/help/bricked-d410-t3094018/post61741908
Or this: http://forum.xda-developers.com/showthread.php?t=2582142
Make sure to use the right sbl1, aboot, rpm, tz and recoveryimages of your model. If you don't find those files, maybe someone can backup the partitions for you, I own a different model D410HN
F. Gacrux said:
Maybe this: http://forum.xda-developers.com/lg-l90/help/bricked-d410-t3094018/post61741908
Or this: http://forum.xda-developers.com/showthread.php?t=2582142
Make sure to use the right sbl1, aboot, rpm, tz and recoveryimages of your model. If you don't find those files, maybe someone can backup the partitions for you, I own a different model D410HN
Click to expand...
Click to collapse
Thanks for your attention! My phone is the same.
But as said, the computer (Linux or Windows) did not recognize the phone, COM, Modem, Unknown device, nothing...
Hard Disk Low Level Format Tool only appears my HD, so i am stuck in step 3.
niquelfer said:
Thanks for your attention! My phone is the same.
But as said, the computer (Linux or Windows) did not recognize the phone, COM, Modem, Unknown device, nothing...
Hard Disk Low Level Format Tool only appears my HD, so i am stuck in step 3.
Click to expand...
Click to collapse
In this case the right binaries can be retrieved from the dz inside the kdz with LG Firmware Extract.
Regard your device not being recognized, can you please run USBDeview (run as admin, download: http://www.nirsoft.net/utils/usb_devices_view.html), plug the USB cable in your device, refresh and see if something popup in the connected devices list? Your need the qhsusb_bulk to show up in device manager. Maybe removing not connected devices in usbdeview to clear drivers and rebooting your PC can work.
This Tutorial worked very well. Thanks all.
http://forum.xda-developers.com/lg-...ick-hard-bricked-l90-variants-t3173429/page15
D410
F. Gacrux said:
Maybe this: http://forum.xda-developers.com/lg-l90/help/bricked-d410-t3094018/post61741908
Or this: http://forum.xda-developers.com/showthread.php?t=2582142
Make sure to use the right sbl1, aboot, rpm, tz and recoveryimages of your model. If you don't find those files, maybe someone can backup the partitions for you, I own a different model D410HN
Click to expand...
Click to collapse
Hey. I need these img files sbl1, aboot, rpm, tz for my LG l90 dual D410. Please help
Jaimil said:
Hey. I need these img files sbl1, aboot, rpm, tz for my LG l90 dual D410. Please help
Click to expand...
Click to collapse
Extract from your KDZ file.
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.
Guys i found a unbrick way for redmi 9c nfc , the phone has secretly the fastboot files in its download folder , but when the file manager booster deletes them and then you cant do it so we need someone to zip the folder and upload it somewhere like mediafire , then its possible to unbrick it with sp flash tool with no infinite red box / DA loading 100%
(Folder is called "angelican" like the codename and and fw info)
(File size gonna be +6 gb so i recommend it first to transfer to pc)
Remember your redmi 9c nfc must be unbricked
I looking for this folder but i can't find it you know more about that
mysteriouscat said:
Guys i found a unbrick way for redmi 9c nfc , the phone has secretly the fastboot files in its download folder , but when the file manager booster deletes them and then you cant do it so we need someone to zip the folder and upload it somewhere like mediafire , then its possible to unbrick it with sp flash tool with no infinite red box / DA loading 100%
(Folder is called "angelican" like the codename and and fw info)
(File size gonna be +6 gb so i recommend it first to transfer to pc)
Remember your redmi 9c nfc must be unbricked
Click to expand...
Click to collapse
Can you explain better what exactly you mean? I have a bricked R9a so MTP is inaccessible as of now, no sign of life at all, beside its detected at Preloader or USB VCOM, and SPFT keeps getting that error DA loading 100%, also mtk-client gives "sending EMI data error" permanently.