Root Kernel crash

[SavageRobot]

So randomly I got my phone out my pocket last night and it was off and wouldn't turn on. Battery pull turned on and I got a screen saying "kernel crash! Demigod crash handler....."
bunch of stuff after this. After rebooting, wiping data, flashing new kernel and reflashing RR I still keep getting this screen. If I restore last backup I have (Genysis) or reflash Genysis etc (and obviously wiping etc) I get a bootloop. Any thoughts?

 

[El Presidente]

What ROM/kernel combo were you using when it crashed? Also, the new Genysis needs the 20c bootloader and radio so that could be why you're bootlooping?

 

[SavageRobot]

I was using RR think dated about 21st. If I restore a Nandroid does it not replace the bootloader and radio with it? If not, how do I get those files to my phone without being able to connect to PC please?

 

[El Presidente]

If you can still get to recovery, you should be able to connect the phone to the PC and copy the zips over.

 

[SavageRobot]

OK I'll try that then thanks but I'm not holding my breath, I still have the full 20B boot, system, modem & bootloader on SD so I tried to completely revert it back to 20B stock and still bootlooped.

 

[SavageRobot]

Nope, tried Genysis 3.6 with 20C bootloader and modem and still bootloop. Any other suggestions? I don't understand with me still able to get into recovery CM=kernel crash, even with new kernel, stock based=bootloop.

 

[bberryhill0]

Fascinating...

 

[El Presidente]

Fascinating...

And annoying.

What happens if you try another AOSP/CM ROM? Blisspop or AICP for example?

 

[SavageRobot]

Don't know actually, I would imagine same thing but I'll try it shortly. I tried flashing another stock ROM from here in recovery and still bootloop. Then tried flashing kdz from here but phone won't stay in download mode long enough, goes to download mode, hangs for about 5 seconds then bootloops.
Downloading CandySix now, will give it a go and report back, but I'm not holding my breath.

 

[SavageRobot]

CandySix=Kernel Crash

 

[El Presidente]

All I can think of is your phone is goosed and it's not a software issue.

Does LGUP use download mode to flash? (I presume so)

 

[SavageRobot]

That's what I'm thinking another excess fee from EE then because of LGs faulty motherboard
Yes I believe it does use download mode, just weird it won't stay in it.

 

[El Presidente]

Well, that's interesting.

Guess what's just happened to me? Same ROM, same build.....

Thankfully, a battery pull sorted me.

Googling brings up a few hits, a couple from AF too: http://androidforums.com/threads/kernel-crash-at-boot-no-download-mode.887633/

@iowabowtech the fix you posted there, reckon it'd work for the G4 too?

 

[SavageRobot]

Oh that was lucky for you, wish mine was as simple as battery pull too :/
I guess this then means there is something CM ROMs aren't quite playing right with the G4 at the moment then seeing as I get bootloop on stock base.
I wonder if the other guy managed to fix then.
I'd be willing to have a go anyway seeing as my warranty is already void anyway with the BL unlock

 

[iowabowtech]

@iowabowtech the fix you posted there, reckon it'd work for the G4 too?

I think they've long since killed bulk mode @El Presidente. So that's likely out. Very strange that a stock rom won't boot unless there's some other smoke and mirrors going on with the CM flash that's also changing other partitions for example for compatibility purposes. I'm not sure what to suggest on that honestly as I haven't followed the nuances of the G4 very closely.

The kdz might be failing because in some cases, a custom rom will replace it's name into the device name field causing the the firmware flashing tools to fail. If you happen to have a tot for this device, you'd likely have more luck as there's some workarounds that can be had using LG Flash Tools instead.

That said, with root and custom recovery, there's a fix there. I'm just not sure yet what to suggest for the safest restore effort.

 

[SavageRobot]

Thanks @iowabowtech that's what I'm thinking with recovery there must surely be something I can do. I think I did dowload a tot when my last G4 bootlooped, I'll have a look on my drive tomorrow, however, the device doesn't stay in download mode for more than a few seconds so I don't think that will be an option

 

[iowabowtech]

OK I'll try that then thanks but I'm not holding my breath, I still have the full 20B boot, system, modem & bootloader on SD so I tried to completely revert it back to 20B stock and still bootlooped.

Nope, tried Genysis 3.6 with 20C bootloader and modem and still bootloop. Any other suggestions? I don't understand with me still able to get into recovery CM=kernel crash, even with new kernel, stock based=bootloop.

Did you update bootloader and modem with a flashable zip or other method? Just trying to discern what exactly you have right now. I can try to look into compatibility issues if you don't uncover any such info.

And yeah if you can't stay in download mode, the tot won't help in this case. Almost think this has to be a case of needing a matching bootstack and perhaps you have something out of order on that.

 

[SavageRobot]

All with flashable zips in TWRP. I have on my SD the full 20B from here also a couple of Genysis ROM Nandroids (20B and a 20C I think) and all the files needed for Resurrection Remix and now also CandySix. I have also tried flashing another kernel GoogyMax with the RR Rom, havent tried it on the stock, don't suppose that would make any difference would it?

 

[El Presidente]

Googymax is for stock based ROMS I think, no harm in giving it a go at the moment.

I just noticed the 2nd post here

Based on what IBT posted above, is there anything in the "cust" folder that could be tricking the phone in to thinking the software version/bootstack isn't what it is? You should be able to navigate the files on your device from twrp.

Also, there are 20D Flashable zips available now, if you want to try those?

http://forum.xda-developers.com/g4/development/stock-h815-20d-images-kdz-flashable-t3301366

 

[SavageRobot]

Well I just booted into recovery and only got 22% so charging back up through laptop for a while now before I try anything again.
Looking in the file manager though can't see cust folder. I have boot, cache, data, dev...could that be the problem, has a necessary file somehow deleted itself?
I may try 20D later thanks.

 

[iowabowtech]

Man, it's tough to find a stock rom for this thing. But near the bottom of the RR thread's OP, there appear to be stock roms for V20A and V20B. Have you tried either of those? If not, that would be my recommendation. Just to make sure those were TWRP flashable zips and not firmware packages, I downloaded and checked it out. You can see the contents of the 20B zip, noting the presence of the updater script:

http://imgur.com/Lu33cCc

That appears to contain everything to get to a fully stock setup. Basically akin to a kdz via custom recovery, if you will.

 

[SavageRobot]

Yea, I tried flashing the complete stock. First link in my reply after your last post...I'm assuming since that still bootlooped I'm knackered
Does it matter that I can't see a "cust" folder for some reason? Would that flash with new ROMs and backups too? Or does that stay untouched?

 

[iowabowtech]

Yea, I tried flashing the complete stock. First link in my reply after your last post...I'm assuming since that still bootlooped I'm knackered
Does it matter that I can't see a "cust" folder for some reason? Would that flash with new ROMs and backups too? Or does that stay untouched?

Forgive me if I haven't caught up yet but I'm not seeing where you've linked the stock rom I'm talking about. I see that you flashed a stock rooted setup back in post 9 using THESE instructs and files. I'm not recommending that. Instead, the stock rom at the end of the original post in the RR thread link to larger, complete 20B rom. Note the size differences. The one from the tutorial you linked is 832 MB. That is just the rom itself, changing system basically. The full stock rom for 20B is 1.4 GB in size because it contains not only the rom but also the full bootstack and system.

It appears you'd lose root with this method however as su is not included in that rom. But since stock recovery was left out of the zip (see again the screenshot in my most recent post of zip contents), you should keep TWRP and since you have an unlocked bootloader at the moment, you should be able to get root back. I assume this is the intention of that zip being posted there especially since it's flashable in custom recovery but if you or anyone else has reason to disagree, please do.

 

[SavageRobot]

Downloading, thank God for Fiber Optic at work
However, I'm wondering if this is just the same as flashing these which I've already tried seeing as that too is 1.4GB
Should be able to update in 20 mins or so...hopefully with good news.

 

[iowabowtech]

Yeah, the only thing that makes me slightly nervous is that the zip flashes the bootloader and I don't know which bootloader it's flashing though I assume it's 20B as advertised. So with that being said, with your currently unlocked bootloader and TWRP as your recovery...will that cause any sort of upset? Will the bootloader get relocked? And if so, it may not like that considering you have a custom recovery installed which typically isn't a legit action with a locked bootloader. Whoever made this zip may have taken all that into account, I'm just not sure having not been close to the dev community on this device.

So if you want to be super safe, ask around the G4 community and make sure this is a legit way to update an already rooted and unlocked G4 such as your own. I don't want to be the cause of your ending up in a QDLoader 9008 situation, which there's currently not a fix for on the G4 last time I checked.