Though I have some experience with rooting phones and flashing custom rooms, I still consider myself to be no more than a novice in this subject. I have a LG K20 PLUS, metro pcs, and I have it rooted running PBRP recovery and the unofficial lineage 14.1 rom. I have been trying different roms and just recently kernels. I was trying to get kali nethunter working and on here at xda two files that I could flash to install it. I will have to go and look to get the names right but one was something like kali nethunter generic rolling something and the other was a custom kernel to complement it. Both flashed without any errors. When I rebooted, after the LG logo I found myself with a kernel panic error.
Kernel crash!
DemiGod Handler : Kernel Crash!
If you want to get ram dump,
Please do following action.
1) Dload Mode. Please connect USB.
2) Get ram dump image using QPST Configuration.
Board Info : 6
rev. : 1.0, cx_pvs: 1 mx_pvs: 1
serial : aadd87fc0000000
secure boot : enabled
[ 4.000591 / 01-01 00:00:07.439][3] Kernel panic - not syncing: adsp_loader_do: pil get failed.
Jump to Bload Mode.
I am still able to enter revory mode and through recovery boot to bootloader. I had attempted reflashing the recovery to TWRP, which was successfull, but attempting reflashing kernels (though flashing without errors) has had no effect on the kernel panic issue. I have reflashed roms as well, it seems nothing that I know how to do will fix the problem. Surfing the web for answers... has only shined light on just how little I understand a lot of this stuff. Most information ℹ have been able to find (in a lot of cases I don't even know if it applies to my specific problem) is way beyond my technical ability to comprehend. I hope that someone here can guide me through this panic and help get my K20 plus functional again. :fingers-crossed:
You're gonna need a PC with LG Windows USB drivers, LG UP v1.14, as well as LG Uppercut 1.0 which is a modified version of LG UP, and a stock .kdz image to reflash your phone back to stock. You can find those links on this forums or other LG phones threads. I'm pressed for time so I can't link them all. I've had a similar issue with kernel panic where flashing any ROM or kernel couldn't fix the issue. The only thing I could do was flash a stock image so that the partitions could be overwritten and corrected. You can find the LG stock image here https://lg-firmwares.com/lg-mp260-firmwares/#tab=firmwares I suggest an older variant like 10j or 10v, though I've had success installing 11k and reverting to 10j but I'm not certain if the newer images have any code that makes it more difficult to modify bootloaders or revert to older stock versions. MTP is your ideal image. MTD is a Metro Demo and MTK are FRU (field replaceable unit) images with some capability of having special resizable partitions but that goes beyond my understanding and scope of this post.
There's a chance you'll find Download mode on your phone doesn't stick to more than 20 seconds or so, which isn't enough to flash an image without issues. I found the fix for this was to go into recovery and wipe everything you're allowed to wipe, recovery will caution there is no operating system installed. That's fine. Rebooting to system should lead to a similar warning on boot. Custom Recovery should still work but you won't need it. You'll need to get back to download mode, plug the phone to the computer, and be sure it is recognized by Device Manager along with a COM port number associated to it. LG UPPERCUT should then be able to see the phone model and COM port and launch, it won't launch otherwise. Once LG UP is running, load up the .kdz image and click UPGRADE. As long as your phone is able to remain in Download mode for more than 30 seconds you're good. If it continues to reboot short of that, give it another thorough wipe in custom recovery.
Once you have flashed stock, you can go back to adb or fastboot and reflash a custom recovery and root program as you did initially. Your bootloader should still remain unlocked after flashing stock so there's no need to run fastboot oem unlock commands again.
CabbyKing said:
Though I have some experience with rooting phones and flashing custom rooms, I still consider myself to be no more than a novice in this subject. I have a LG K20 PLUS, metro pcs, and I have it rooted running PBRP recovery and the unofficial lineage 14.1 rom. I have been trying different roms and just recently kernels. I was trying to get kali nethunter working and on here at xda two files that I could flash to install it. I will have to go and look to get the names right but one was something like kali nethunter generic rolling something and the other was a custom kernel to complement it. Both flashed without any errors. When I rebooted, after the LG logo I found myself with a kernel panic error.
Kernel crash!
DemiGod Handler : Kernel Crash!
If you want to get ram dump,
Please do following action.
1) Dload Mode. Please connect USB.
2) Get ram dump image using QPST Configuration.
Board Info : 6
rev. : 1.0, cx_pvs: 1 mx_pvs: 1
serial : aadd87fc0000000
secure boot : enabled
[ 4.000591 / 01-01 00:00:07.439][3] Kernel panic - not syncing: adsp_loader_do: pil get failed.
Jump to Bload Mode.
I am still able to enter revory mode and through recovery boot to bootloader. I had attempted reflashing the recovery to TWRP, which was successfull, but attempting reflashing kernels (though flashing without errors) has had no effect on the kernel panic issue. I have reflashed roms as well, it seems nothing that I know how to do will fix the problem. Surfing the web for answers... has only shined light on just how little I understand a lot of this stuff. Most information have been able to find (in a lot of cases I don't even know if it applies to my specific problem) is way beyond my technical ability to comprehend. I hope that someone here can guide me through this panic and help get my K20 plus functional again. :fingers-crossed:
Click to expand...
Click to collapse
Any updates? Were you able to get your phone up and running?
Related
Urgent help needed as I'm leaving the country at the end of the week o any help is appreciated!
Just successfully rooted my device:
Black, Unlocked, PRA-LX1, UK, Dual SIM
After doing so successfully, I attempted to flash LineageOS from the following link:
https://forum.xda-developers.com/p8lite/p8-lite-2017-development/rom-lineageos-15-1-hi6250-devices-t3811583
Although when I completed Step 6 on the Installation guide and rebooted the phone, I started seeing the message:
------------------
ERROR MODE
Attention!
Please update system again
(Green Android picture)
Error!
Func NO : 11 (recovery image)
Error NO : 2 (load failed!)
------------------
Despite this, I didn't receive a box with my phone due to being second hand, and I didn't see the model number on the receipt as it was from a reselling store. I didn't remember to note down the specific model number
It'd be extremely helpful if someone could possibly help just from the device description above as I'm not sure if it's safe for me to just attempt to flash every stock rom for every other LX1 device out there.
---------------------------------------------------------------
Update:
To restore this, I connected via fastboot with a working USB & flashed an original stock recovery in the video found here
(Just in case their download link ever goes down, I have uploaded the same copy to my MEGA, found here)
The recovery installed fine when using the command
fastboot flash recovery oeminfo.img
Click to expand...
Click to collapse
Whenever trying to flash any other recovery such as twrp before this fastboot stuck on a loading icon.
The stock recovery seems to be downloading the original firmware, too.
PRA-LX1C432B202 is presumably the model.
Both the bootloader and FRA were unlocked when everything else was inaccessible.
Looks like the custom ROM's recovery that you've flashed is not compatible with PRA-LX1. Try to flash stock recovery. If not working, then flash stock firmware.
Thanks @Botar230!
I didn't see your comment until just now after deciding to edit this post since I've gotten a step closer to restoring my device.
Your solution was the method I used although I didn't know my phone model, so I found a random solution which just worked for my device, and the eRecovery seems to be downloading the stock firmware anyways. Thanks again
Before flashing this lineage os you should update to EMUI8 to get treble support, i suppose you was running EMUI5, hence the error mode.
Alright so this has happened
I was all a happy guy on H915_10e rooted rom on my H910PR when I decided to my destruction, flash Lineage 15.1 with second screen support as well as trying out gamma kernel for second screen. Turned out xda's dl server crapped on me by refusing to letting me download the SS gamma kernel for LOS 15.1
I ended up flashing x86cpu's LOS15.1 and then after a day I only observed phone lasting me 6-8 hrs due to the greyed out NFC and no option to get the problem sorted out (seemingly I am the only one having this issue).
So all I had to do was flash stock kdz again and start from zero to dirtysanta H915 rom
I have sold my PC and thus am left with two laptops (both have USB 2.0 as well as USB 3.0 ports).
I first installed LG drivers WHQL v4.2.0
Then I installed LG UP v1.14.3
Then I extracted the patched LGUP in correct folder (double checked)
I put my phone to download mode and connected > it gets recognized in device manager.
Now when I try to run LGUP, it says unknown in device model and shows me H915_10e (surprisingly enough its running on lineage 15.1 H910 with gamma kernel). It doens't let me proceed further. Even after using uppercut
I tried the guide to unbrick in LG G5 forum which basically follows LG Flash tool route which failed for me too.
After that I looked if I could get to TWRP and yes I could, as well as the engineering boot is still there (fastboot commands work).
Now that I do have full flashable image of H910_10r from brian's guide to root, when I try to reboot after flashing TWRP gives me an error that no OS is installed and I get stuck at LG Logo (not even the warning screen).
I tried flashing Super V20 rom as well and ended up in the same den. I havent tried to flash LOS back but that's of no use to me (battery nightmares).
Whats the valid route here to get back to my H915 or H910PR rom ? LGUP isn't working for me despite being patched
-Thanks
Put that h910_10r zip along with Magisk onto an SD card. In TWRP, wipe everything / format data, then put the SD card into the phone, and flash that zip. Once flashed, flash Magisk.
Before you reboot, make sure that data and system are mounted, unmount them (uncheck them), and then mount them again.
-- Brian
runningnak3d said:
Put that h910_10r zip along with Magisk onto an SD card. In TWRP, wipe everything / format data, then put the SD card into the phone, and flash that zip. Once flashed, flash Magisk.
Before you reboot, make sure that data and system are mounted, unmount them (uncheck them), and then mount them again.
-- Brian
Click to expand...
Click to collapse
Did so, before rebooting TWRP asked me that there is no OS installed.
Surprisingly after every flash process I checked in download mode if there is any sign of identification.
I ended up flashing full stock H910 10q through TWRP, still the phone said there is no OS installed. The same error popped up when I flashed super v20 full stock H910 too.....
welp, now I'm with locked bootloader with Firmware update screen showing me "633A B50" in the information and stuck at 0%
LGUP still identifies as unknown device. Looks like I've ended up in the same basket as some of the fellows who got stuck with disfunctional download mode. I'll try tomorrow if I get to buy another Type-C cable although phone identifies correctly even in LG Flash tool (the identifier worked as H915 before, then changed to H910PR when I tried the H910PR kdz on provision of LGUPc.dll from extracting the kdzs.
I can't do anything except charge phone and if I try to power it on, its stuck on LG Logo (no warning screen whatsoever and there is no going back to TWRP as of now.
I even tried kdzwriter and it just remaining blank on the kdzwriter commands despite I could see kdzwriter in sbin directory and manually setting permissions to 755 through twrp file manager, still it did nothing.
Also, the bloody funny thing is, LGUP still recognizes as H91510e while LG Flash Tool recognizes phone as H91010q as well as shows LG-H910 on the phone firmware update status log. Something from full stock H91010q didn't erase that info as well
Wait, how do you know you still had the engineering bootloader other than the fact that you could boot to TWRP?
If you had no warning screen, then you probably didn't.
You may have bricked your phone, but we may be able to learn something.
Edit: FYI .. you still may not have bricked your phone yet if you still have download mode.
EDIT2: If you want to save your phone, don't do anything else for now.... read the laf development thread, not the lafsploit thread....
-- Brian
runningnak3d said:
Wait, how do you know you still had the engineering bootloader other than the fact that you could boot to TWRP?
If you had no warning screen, then you probably didn't.
You may have bricked your phone, but we may be able to learn something.
Edit: FYI .. you still may not have bricked your phone yet if you still have download mode.
EDIT2: If you want to save your phone, don't do anything else for now.... read the laf development thread, not the lafsploit thread....
-- Brian
Click to expand...
Click to collapse
When I had engg bootloader (which facilitated all fastboot commands we need to flash modem recovery blahblah etc) and TWRP, the phone sat on LG Logo all the time if I did a normal bootup or reboot through recovery.
The warning screen only poppped when I used the enter recovery combo.
Also H910_10m has something different than H910_10r.
The warning screen on 10r is perfectly crisp and clear but the warning screen on H910_10m firmware is distorted all accross the screen with parts of it horizontally distributed all over and wrapped around.
Rigth now:
I have working download mode and only way the phone talks a little bit (mamma papa of a baby maybe) is through LG Flash tool when I give the LGUP.dll and a kdz to flash to it. It says its an LG-H910 on download mode status screen and says two lines about H91010r and the next line as the line of the firmware I'm trying to flash, here in my case those are H91510e and H910PR10j.
I can even go to factory reset screen and the nice circle spins saying to me erasing but it reboots back at LG Logo
I have full dump of my H910PR but that's useless if LGUP doesn't recognize my phone.
TLDR as of Now: I'm going to install Windwos 7 on my older Lenovo x230 Laptop and start from scratch. I believe there is a bad driver footprint left somewhere in this windows 10 and I hate windows 10's communication trouble with third party devices.
Will keep you updated via this thread. I hope I do not annoy you too much with my post backs
Bump! No chance. Stuck in same situation but now I have only access to download mode or factory reset (since I'm on stock H910 10q firmware). LGUP says unknown with H91510e while LG flash tool says it's H91010q. Can't flash sh**.... I've ordered a replacement H910 motherboard and it's gonna arrive in 15 days give or take. Will see if I can swap connection Midway in LGUP and flash this one to stock H910PR
Hi everyone
I am posting this because I fail to flash TWRP on my LG G2 (D802, 30c); I would like to flash LineageOS. I have read many guides and posts - however, none worked. So I turn to you for advice -- would you help me, please?
I have managed to flash Cyanogen to my Samsung S2 a few years ago and TWRP and LineageOS to my LG G5 (H850) last year -- the S2 was easy, the G5 very tricky, but the G2 kills me. The G5 took a real effort because no guide worked for my phone, and I had to take a little from this guide, a little from that and add a bit of my own (let me know if anyone is interested in how I flashed LOS to my G5). I have tried the same with my G2 -- but I seem to have come to a dead end.
I am writing all that that to tell you that I have gone to great length before troubling you. Here is in summary what I have done so far and where I stand:
I have installed the sdk toolkit, adb and fastboot properly when I flashed my G5 last year.
Now I have started with the instructions from the LineageOS wiki (wiki.lineageos.org/devices/d802/install). I have activated USB debugging and rooted my phone using One Click root (Before One Click Root for the G2 was available, I could not even root my phone).
Then I flashed TWRP using "dd" as explained in the installation guide in the LineagOS wiki. I also tried it by flashing through the TWRP app (the app said it was flashed successfully). I tried TWRP 3.2.3.0 and 2.8.7.0 for the D802. The result always was as set out below.
After that I turned off my phone and started I by holding power + Volume down, releasing power briefly after the LG logo appeared. I went through factory reset (selected yes and yes), and here the problems begin (the same when I use “adb reboot recovery”). The phone should start into TWRP, but it does not. Instead the start screen with the LG logo appears, and in the upper left corner the following message appears:
ERROR: boot certification verify
[26480]------------------------------------- -
[26480]
[26520] Secure booting Error!
[26570] Cause: boot certification verify
[26620]
[26670]-------------------------------------- -
If the numbers in the square brackets make sense to you: They change every time I boot.
The next screen reads
------------------------------------------------- -
Critical Error!
------------------------------------------------- -
DemiGod Crash Handler : Critical Error!
Some information on how to reboot or access Download mode]
------------------------------------------------- -
Board Info Rev. : 1.1 speed.pvs : 1.3 serial : [...]
------------------------------------------------- -
I have tried many things, including several resets using LG FLash Tool 2014 to flash an entirely clean stock rom and starting fresh rooting and flashing. I also tried LG G2 D802 One Click Root Recovery V1.1, which even failed to root the phone.
My feeling is that the phone prevents me from properly installing TWRP. It does not allow me to boot into the bootloader using "adb reboot bootloader" (the command just restarts the phone). Therefore, I cannot put it into fastboot mode (I also tried the volume-up button method to put it into fastboot and failed), which may be crucial to properly install TWRP. In this regard, it may be relevant that the Developer Options show no option "OEM unlock"; that might be necessary to access the bootloader and fastboot mode…
What do you think? Do you have an idea how to solve the problem?
Thanks a lot and cheers!
Noob here: I need help with my Note 3 (SM-N900V).
I bought a used phone to replace a stolen one; it came with Android 4.0. A few years ago I successfully used Odin to flash TWRP 3.1.0.0 and the stock OF1 Android 5.0 rom, followed by a root with ArabicTool.
Phone works fine for everyday use, including root-requiring apps, but several apps are now requiring a more recent version of Android. Also, I can no longer boot into recovery mode; instead I get a message saying "System software not authorized by Verizon Wireless has been found on your phone".
I thus decided to try to flash the phone from scratch.
First I tried to use ADB and Fastboot to make sure the bootloader is unlocked. Unfortunately, while ADB worked fine, I was never able to get Fastboot to see the phone, despite following the advice of several web pages addressing this issue, and trying several different drivers.
Pressing on, I decided to try to install TWRP again. Booted phone with VolDown, Home, Power. First I tried using Heimdall 1.4, both with drivers from Samsung, and then with the MSM8960 drivers that came with Heimdall, using this command:
heimdall flash --RECOVERY twrp-3.3.1-0-hlte.img --no-reboot
In both cases, all I got was "ERROR: Failed to access device. libusb error: -12"
Therefore, decided to try it with Odin. Booted phone with VolDown, Home, Power. Run Odin 3.12.4_4, which immediately shows "Added". Load TWRP 3.3.1.0 with AP button, click Start...and get a red Fail flag within a few seconds. Log shows "FAIL! (Auth). Phone shows "SYS REV CHECK FAIL: No Version" and "SECURE MAGICCODE CHECK FAIL: recovery".
I didn't even bother trying to flash the LineageOS ROM.
Can someone please tell me what I'm doing wrong? Please don't assume I know anything about what I'm doing.
--
*not an expert*
Verify that you are using the correct build of twrp-3.3.1.
I am using the hlte build of 3.3.1 on my phone (SCL22)... but my gut tells me that you and I wouldn't share the same build.
Nope basic problem is that OP is in the wrong forum for a Verizon phone .
Assuming that download mode still works (if it is, lucky you); I'd suggest reflashing the stock firmware for your Verizon device.
Flashing a stock firmware would *hopefully* fix your recovery and download issues.
Perhaps the errors you described may have been caused by installing the wrong ROM/firmware.
So, NEVER INSTALL/FLASH a custom or stock ROM that is not tested to work on your device. The main reason is because different variants of the same device (N9000, N900A, N900V) use different chipsets, software and drivers. Also, flashing a wrong ROM/kernel/firmware may cause application errors, boot loops, broken recovery/download mode, or a hard brick.
While flashing pixel experience plus rom, the device did not boot up correctly causing a google loading screen which did not change even after an hour. At that time i realised that the rom didn’t flash correctly, or the rom might have some faults. So I rebooted my mobile in custom recovery mode to flash the stock rom, but it did not complete the flash, it generated error 7. So I tried to install havoc rom and I encountered the same problem. Not just that I have tried installing at least 5 rom which gives me the same problem. I can’t even flash my recovery rom. It generates the same errors which include error 7 and invalid zip file. So I tried solving this problem by unzip the rom and editing the assert script and re zipping the file, and I encounter the same errors. I have even tried using a different custom recovery like TWRP and red wolf (latest updated version), but I face the same errors. The mobile has no os installed and it doesn’t allow me to install any rom. It only allows me to install stock recovery and other custom recovery by using Fastboot mode. I have tried add sideload through the custom recovery and the mobile gets detected, but it gives the same errors.
So I tried using QFIL application as the mobile was a Qualcomm device. The mobile gets detected as 9008. And I tried to download the program files on the mobile, but then it gives me a Sahara fail error.
I have tried to do it multiple times and I end up getting the same error.
The device has a unlocked boot loader but it was never rooted.
Please help me.
Can’t post it in the developer forum for this device as I don’t meet the requirements for posting it
i.am.the.best said:
While flashing pixel experience plus rom, the device did not boot up correctly causing a google loading screen which did not change even after an hour. At that time i realised that the rom didn’t flash correctly, or the rom might have some faults. So I rebooted my mobile in custom recovery mode to flash the stock rom, but it did not complete the flash, it generated error 7. So I tried to install havoc rom and I encountered the same problem. Not just that I have tried installing at least 5 rom which gives me the same problem. I can’t even flash my recovery rom. It generates the same errors which include error 7 and invalid zip file. So I tried solving this problem by unzip the rom and editing the assert script and re zipping the file, and I encounter the same errors. I have even tried using a different custom recovery like TWRP and red wolf (latest updated version), but I face the same errors. The mobile has no os installed and it doesn’t allow me to install any rom. It only allows me to install stock recovery and other custom recovery by using Fastboot mode. I have tried add sideload through the custom recovery and the mobile gets detected, but it gives the same errors.
So I tried using QFIL application as the mobile was a Qualcomm device. The mobile gets detected as 9008. And I tried to download the program files on the mobile, but then it gives me a Sahara fail error.
I have tried to do it multiple times and I end up getting the same error.
The device has a unlocked boot loader but it was never rooted.
Please help me.
Click to expand...
Click to collapse
1. 1st try to flash fastboot rom,
after install fastboot rom if the phone stuck on asus logo or any other error then
2.Try to install Qfll file (select ww_no_fsg.xml file) after successful installation , boot your phone.
3. again connect your phone fastboot mode and flash fastboot rom
If every installation is successfully done then i am sure that your phone is boot properly in stock rom with lock bootloader.
because I faced same issue,
remember 1st try to install stock fastboot rom and then try to flash Qfil files
Wish you good luck :good:
Try flashing fw063 before flashing your custom rom.(that fixed for me)
if it didn't work try this (rooted):-
https://forum.xda-developers.com/showthread.php?t=2522762
Thanks bro. I have successfully unbricked my mobile