Related
Hello, my friend tried to flash his E460 because his firmware was SIM locked but he used a wrong firmware and now the touchscreen and the 3 buttons on the bottom don't work.
I used LGMobile Support Tool and did an upgrade recovery, but the touchscreen still doesn't work.
Anyone have any solution? Thanks.
ptrVoid said:
Hello, my friend tried to flash his E460 because his firmware was SIM locked but he used a wrong firmware and now the touchscreen and the 3 buttons on the bottom don't work.
I used LGMobile Support Tool and did an upgrade recovery, but the touchscreen still doesn't work.
Anyone have any solution? Thanks.
Click to expand...
Click to collapse
you will be able to use kdz updater in attached link LG-RDTT_1.0.5.4 (needs included windows enabler for this version)
use THIS GUIDE to flash just skip the hosts file editing steps
and let us know
IGGYVIP said:
you will be able to use kdz updater in attached link LG-RDTT_1.0.5.4 (needs included windows enabler for this version)
use THIS GUIDE to flash just skip the hosts file editing steps
and let us know
Click to expand...
Click to collapse
I used this tutorial and successfully flashed the phone but the touchscreen still doesn't work. What should I do? Thanks.
maybe screen damaged by bad flash
ptrVoid said:
I used this tutorial and successfully flashed the phone but the touchscreen still doesn't work. What should I do? Thanks.
Click to expand...
Click to collapse
did buttons start working ?
did you flash kernel and/or recovery onto phone before ? <<<---that might have damaged hardware
did you open your phone at any time ?
IGGYVIP said:
did buttons start working ?
did you flash kernel and/or recovery onto phone before ? <<<---that might have damaged hardware
did you open your phone at any time ?
Click to expand...
Click to collapse
My friend tried to flash it and he used a wrong firmware for E455 instead of E460.
I don't think he did anything else because it doesn't have a custom recovery installed.
The buttons and touchscreen still don't work.
I think somehow the wrong firmware installed incorrect drivers for the touchscreen or something, but I thought the drivers are stored inside the ROM?
burn it
ptrVoid said:
My friend tried to flash it and he used a wrong firmware for E455 instead of E460.
I don't think he did anything else because it doesn't have a custom recovery installed.
The buttons and touchscreen still don't work.
I think somehow the wrong firmware installed incorrect drivers for the touchscreen or something, but I thought the drivers are stored inside the ROM?
Click to expand...
Click to collapse
You probably need to burn it with 10.000V or sell it and give 5 euros to buy new one. :good:
ptrVoid said:
My friend tried to flash it and he used a wrong firmware for E455 instead of E460.
I don't think he did anything else because it doesn't have a custom recovery installed.
The buttons and touchscreen still don't work.
I think somehow the wrong firmware installed incorrect drivers for the touchscreen or something, but I thought the drivers are stored inside the ROM?
Click to expand...
Click to collapse
Hi...
can't flash it again ???
x-jack said:
Hi...
can't flash it again ???
Click to expand...
Click to collapse
Hello, I flashed it with a correct firmware but the touchscreen/buttons still don't work. Is there a way to flash the drivers only?
ptrVoid said:
Hello, I flashed it with a correct firmware but the touchscreen/buttons still don't work. Is there a way to flash the drivers only?
Click to expand...
Click to collapse
it can be helpful :
https://www.lg.com/global/support/o...tegoryId=CAT00000001&osCategoryId=CAT00000002
ptrVoid said:
Hello, I flashed it with a correct firmware but the touchscreen/buttons still don't work. Is there a way to flash the drivers only?
Click to expand...
Click to collapse
Hi!
Did you manage to fix that?
no way to fix this? i have the same issue
I killed my touchscreen too. Is the phone killed forever?
Hello, same situation here,
I compiled LG E460 kernel from LG sources then I flashed into phone (it already had ultraslimrom), then phone did not boot anymore.
I reflashed ultraslimrom and noticed that touch screen was dead.
I have then reflashed various version of stocked rom with "LG flash tool 2014" but situation is the same: touch screen is dead
Can someone pls. help me. I have a rooted Lenovo IdeaTab A3000-H that accidentally got soft bricked after I edited build.prop on /system/build.prop
Info:
Model Number: Lenovo A3000-H
Android Version: 4.2.2
USB Debugging: Disabled
Currently Bootable To: Stock Recovery and Fastboot
(I could boot to ADB but it could only do sideload commands)
I have a recovery.img (CWM) that I can't flash since my PC can't detect my tablet while it's turned off
(And also if possible, can someone give me an original unmodded Lenovo A3000-H build.prop.bak and CWM flashable zip compatible for my tab.)
Hello,
Welcome to XDA.
If you can get in fastboot mode you should be able to flash a CWM recovery.img, no need for a CWM flashable zip.
You can also try adb pushing a copy of your original build.prop to replace the faulty one, you can extract it from your stock firmware if its available for download and use the extracted copy or you can extract the build.prop from whatever custom ROM you were on if you had Custom installed.
I'm not saying these are your definite fix, they are just some things for you to look into.
Droidriven said:
Hello,
Welcome to XDA.
If you can get in fastboot mode you should be able to flash a CWM recovery.img, no need for a CWM flashable zip.
You can also try adb pushing a copy of your original build.prop to replace the faulty one, you can extract it from your stock firmware if its available for download and use the extracted copy or you can extract the build.prop from whatever custom ROM you were on if you had Custom installed.
I'm not saying these are your definite fix, they are just some things for you to look into.
Click to expand...
Click to collapse
1) it says that my tablet doesnt support flashing partitions through flashboot
2) my backup for my build.prop is in my internal storage(phone storage). And that is why I'm asking if any of you guys have an original copy of build.prop.bak so that I could try to flash it using my stock recovery
3) whenever I try to do adb commands, I always get the error "error:closed"
PS: I only have stock recovery and I can't flash using SP Flash Tool because I don't have my USB Debugging turned on
BTW sorry if I sometimes/always reply late... It's because my timezone is different, because I live in the Eastern Countries...
CEDoromal said:
1) it says that my tablet doesnt support flashing partitions through flashboot
2) my backup for my build.prop is in my internal storage(phone storage). And that is why I'm asking if any of you guys have an original copy of build.prop.bak so that I could try to flash it using my stock recovery
3) whenever I try to do adb commands, I always get the error "error:closed"
PS: I only have stock recovery and I can't flash using SP Flash Tool because I don't have my USB Debugging turned on
BTW sorry if I sometimes/always reply late... It's because my timezone is different, because I live in the Eastern Countries...
Click to expand...
Click to collapse
If you can find your stock firmware and download it you can extract your build.prop from it and adb push it to your system folder.
Sent from my SCH-I535 using Tapatalk
Droidriven said:
If you can find your stock firmware and download it you can extract your build.prop from it and adb push it to your system folder.
Sent from my SCH-I535 using Tapatalk
Click to expand...
Click to collapse
I'm glad to know that... But I can't do any adb commands except for adb sideload because I always gets error:closed when I try to...
CEDoromal said:
I'm glad to know that... But I can't do any adb commands except for adb sideload because I always gets error:closed when I try to...
Click to expand...
Click to collapse
That's because you don't have USB debugging turned on, without that turned on your only option is to restore your device with your stock firmware. I don't think you are going to get much as far as answers here at XDA, you should take the device to a repair shop.
If you can boot to fastboot then you should be able to flash your stock firmware and restore the device.
Sent from my SCH-I535 using Tapatalk
Droidriven said:
That's because you don't have USB debugging turned on, without that turned on your only option is to restore your device with your stock firmware. I don't think you are going to get much as far as answers here at XDA, you should take the device to a repair shop.
If you can boot to fastboot then you should be able to flash your stock firmware and restore the device.
Sent from my SCH-I535 using Tapatalk
Click to expand...
Click to collapse
well... I think I could repair my device if someone gives me a CWM Recovery Zip compatible to Lenovo A3000-H that I could flash to my device using my Stock Recovery then use it so that my computer detects my device.... Or just an original copy of Lenovo A3000-H build.prop.bak or just build.prop.... Or a scatter file for my tab...
I could boot to fastboot but it says that it doesnt support flashing partitions using fastboot...
CEDoromal said:
well... I think I could repair my device if someone gives me a CWM Recovery Zip compatible to Lenovo A3000-H that I could flash to my device using my Stock Recovery then use it so that my computer detects my device.... Or just an original copy of Lenovo A3000-H build.prop.bak or just build.prop.... Or a scatter file for my tab...
I could boot to fastboot but it says that it doesnt support flashing partitions using fastboot...
Click to expand...
Click to collapse
I don't believe flashing a custom recovery through your stock recovery is even possible. You can't flash custom through stock recovery, you can only flash stock files and updates through stock recovery.
If you get the build.prop how do you plan to put it back where it goes? You said that USB debugging is not turned on so adb won't work, thats probably why fastboot isn't working either.
If you want to try the build.prop then download your stock firmware and extract the build.prop file from the firmware and use the extracted file.
Sent from my SCH-I535 using Tapatalk
Droidriven said:
I don't believe flashing a custom recovery through your stock recovery is even possible. You can't flash custom through stock recovery, you can only flash stock files and updates through stock recovery.
If you get the build.prop how do you plan to put it back where it goes? You said that USB debugging is not turned on so adb won't work, thats probably why fastboot isn't working either.
If you want to try the build.prop then download your stock firmware and extract the build.prop file from the firmware and use the extracted file.
Sent from my SCH-I535 using Tapatalk
Click to expand...
Click to collapse
Thanks for informing me...
Actually I'm planning to put that build.prop or build.prop.bak on a flashable Zip that I could flash to my /system....
and I'm not 100% sure if that's gonna work....
CEDoromal said:
Thanks for informing me...
Actually I'm planning to put that build.prop or build.prop.bak on a flashable Zip that I could flash to my /system....
and I'm not 100% sure if that's gonna work....
Click to expand...
Click to collapse
If you mean to flash it through stock recovery I doubt it will work, you can see if there are any stock updates in zip format for your model that can be flashed in stock recovery, if you were rooted it probably won't work though because you have to be unrooted and have an unmodified system partition to apply a stock update.
Your device isn't hard bricked yet so there should be something you can do, I just don't know the details of your model. You may have to take it to a repair shop.
Sent from my SCH-I535 using Tapatalk
Droidriven said:
If you mean to flash it through stock recovery I doubt it will work, you can see if there are any stock updates in zip format for your model that can be flashed in stock recovery, if you were rooted it probably won't work though because you have to be unrooted and have an unmodified system partition to apply a stock update.
Your device isn't hard bricked yet so there should be something you can do, I just don't know the details of your model. You nay have to take it to a repair shop.
Sent from my SCH-I535 using Tapatalk
Click to expand...
Click to collapse
Thanks for informing me again...
But I guess you won't achieve something unless you try...
BTW my friend is a community member here, and he said that it might work if I flashed build.prop.bak to the system. So I might as well try it....
I tried to use the SP Flash Tool to flash the recovery.img to my device but it got an error 3038 (I think), so I'm guessing it's the scatter file... (I Googled it )
CEDoromal said:
Thanks for informing me again...
But I guess you won't achieve something unless you try...
BTW my friend is a community member here, and he said that it might work if I flashed build.prop.bak to the system. So I might as well try it....
I tried to use the SP Flash Tool to flash the recovery.img to my device but it got an error 3038 (I think), so I'm guessing it's the scatter file... (I Googled it )
Click to expand...
Click to collapse
In your circumstances anything is worth trying.
Sent from my SCH-I535 using Tapatalk
Droidriven said:
In your circumstances anything is worth trying.
Sent from my SCH-I535 using Tapatalk
Click to expand...
Click to collapse
It won't Hard Brick my device right?
(warn me if it will make my problem worse.)
CEDoromal said:
It won't Hard Brick my device right?
(warn me if it will make my problem worse.)
Click to expand...
Click to collapse
I don't think so but don't quote me, it'll either flash an succeed or fail, I doubt it will make things worse.
Have you looked at the possibility of using an extsdcard and a debrick.IMG or its equivalent to boot from a bootable extsdcard the same as PC does with a bootable USB? If it works on your device like it does some other devices you can boot into system from extsd and then do what you need to do to fix your device then return the sdcard to normal use after you are going again on its own.
Sent from my SCH-I535 using Tapatalk
Droidriven said:
If you mean to flash it through stock recovery I doubt it will work, you can see if there are any stock updates in zip format for your model that can be flashed in stock recovery, if you were rooted it probably won't work though because you have to be unrooted and have an unmodified system partition to apply a stock update.
Your device isn't hard bricked yet so there should be something you can do, I just don't know the details of your model. You may have to take it to a repair shop.
Sent from my SCH-I535 using Tapatalk
Click to expand...
Click to collapse
Can you tell this to the admin just to see if he could help me...?
and also, do you know why my tablet keeps disconnecting to my pc after 3 seconds when I'm trying to flash?
CEDoromal said:
Can you tell this to the admin just to see if he could help me...?
and also, do you know why my tablet keeps disconnecting to my pc after 3 seconds when I'm trying to flash?
Click to expand...
Click to collapse
An admin won't be able to help you. All android devices are different, they vary drastically from one model to the next, no one here knows about every device, you are going to have to find other users with your device or you will have to find a developer that works on your device, they will know what you need, we aren't all experts with all devices, we each know the devices that we have personally owned and used.
The disconnecting every three seconds is because you are still in a bootloop, it boots to flash mode then loops and boots again, over and over, it can't find the right stuff to boot the way it needs to.
Sent from my SCH-I535 using Tapatalk
Droidriven said:
An admin won't be able to help you. All android devices are different, they vary drastically from one model to the next, no one here knows about every device, you are going to have to find other users with your device or you will have to find a developer that works on your device, they will know what you need, we aren't all experts with all devices, we each know the devices that we have personally owned and used.
The disconnecting every three seconds is because you are still in a bootloop, it boots to flash mode then loops and boots again, over and over, it can't find the right stuff to boot the way it needs to.
Sent from my SCH-I535 using Tapatalk
Click to expand...
Click to collapse
I think I just hard bricked my device....
I tried to install the recovery.img (said to be compatible to my device) using SP Flash Tool then it doesnt boot to anything now, but it is now detected on my pc even after 3 seconds.... (I got an error that is starting on a number 5 followed by three other numbers... sorry I forgot what it was...)
CEDoromal said:
I think I just hard bricked my device....
I tried to install the recovery.img (said to be compatible to my device) using SP Flash Tool then it doesnt boot to anything now, but it is now detected on my pc even after 3 seconds.... (I got an error that is starting on a number 5 followed by three other numbers... sorry I forgot what it was...)
Click to expand...
Click to collapse
Our purpose here at XDA Assist is to point you in the direction you need to look for your answers, we are not here to help you with every step until your device is fixed. I gave you suggestions for where you need to look for your answers because that is where you will most likely find your answers. If you do not find your answers where you were sent, that does not mean to come back here continuing to ask, I have done all that I can for you, I'm sorry that it is not helping you. Your device is unknown to me, the fact you are getting no answers in the forums means that the members in the forums also do not know your device, if they did then they would answer you. There is no guarantee that you will find your answer on XDA, we can only help with the devices we are familiar with. I don't think anyone here knows anything about your device because I did not find a lot of information about your device when I did a search of all the XDA forums because the information you need does not exist here in the forums, only another user that is experienced with your device can help you. You are going to have to find someone in the forums that also owns your device. Continuing to post here will not help you. Be patient and search through the forums by using your device model number in your searches here. If what you need is here then you will find it if you dig through all the threads that are associated to your device model number.
If you can not find an answer here then you will have to consider taking your device to a repair shop.
Droidriven said:
Our purpose here at XDA Assist is to point you in the direction you need to look for your answers, we are not here to help you with every step until your device is fixed. I gave you suggestions for where you need to look for your answers because that is where you will most likely find your answers. If you do not find your answers where you were sent, that does not mean to come back here continuing to ask, I have done all that I can for you, I'm sorry that it is not helping you. Your device is unknown to me, the fact you are getting no answers in the forums means that the members in the forums also do not know your device, if they did then they would answer you. There is no guarantee that you will find your answer on XDA, we can only help with the devices we are familiar with. I don't think anyone here knows anything about your device because I did not find a lot of information about your device when I did a search of all the XDA forums because the information you need does not exist here in the forums, only another user that is experienced with your device can help you. You are going to have to find someone in the forums that also owns your device. Continuing to post here will not help you. Be patient and search through the forums by using your device model number in your searches here. If what you need is here then you will find it if you dig through all the threads that are associated to your device model number.
If you can not find an answer here then you will have to consider taking your device to a repair shop.
Click to expand...
Click to collapse
I just fixed it using META mode without any help of XDA... >
Droidriven said:
Our purpose here at XDA Assist is to point you in the direction you need to look for your answers, we are not here to help you with every step until your device is fixed. I gave you suggestions for where you need to look for your answers because that is where you will most likely find your answers. If you do not find your answers where you were sent, that does not mean to come back here continuing to ask, I have done all that I can for you, I'm sorry that it is not helping you. Your device is unknown to me, the fact you are getting no answers in the forums means that the members in the forums also do not know your device, if they did then they would answer you. There is no guarantee that you will find your answer on XDA, we can only help with the devices we are familiar with. I don't think anyone here knows anything about your device because I did not find a lot of information about your device when I did a search of all the XDA forums because the information you need does not exist here in the forums, only another user that is experienced with your device can help you. You are going to have to find someone in the forums that also owns your device. Continuing to post here will not help you. Be patient and search through the forums by using your device model number in your searches here. If what you need is here then you will find it if you dig through all the threads that are associated to your device model number.
If you can not find an answer here then you will have to consider taking your device to a repair shop.
Click to expand...
Click to collapse
I just fixed it using META mode without any help of XDA or a repair shop... >
hello,
my phone is currently in a coma, the worst brick yet. But is detected as QHSUSB mode.
So far i have installed the drivers and got the software to debrick it. But for this i need a service rom for the phone.
this could be either factory image with MBN files or HEX files.
If you all can help me get these files i will be able to fix the phone.
Please help me find them.
Thank you
slytidar said:
hello,
my phone is currently in a coma, the worst brick yet. But is detected as QHSUSB mode.
So far i have installed the drivers and got the software to debrick it. But for this i need a service rom for the phone.
this could be either factory image with MBN files or HEX files.
If you all can help me get these files i will be able to fix the phone.
Please help me find them.
Thank you
Click to expand...
Click to collapse
hello
have you been able to get the service rom?
i need for my Asus device too, but i can't find it anywhere. maybe u know where to get it?
4llerbuntu said:
hello
have you been able to get the service rom?
i need for my Asus device too, but i can't find it anywhere. maybe u know where to get it?
Click to expand...
Click to collapse
No. I have stopped looking cause there is no service rom available.
Hey guys I am trying to find the stock recovery for the Z00TD model (KE551KL) version 1.17.40.1531. Any chance you guys can help me out.
My issue is that I want to update to the Android 6 but apparently my firmware is incorrect and I need this one to correct it.
Me too please!
Here you have it
https://mega.nz/#!w0EQlQrL!V00keDHV_pwS_cUKwSZuIjFb55oqE8exv0MPlbi262g
You glorious bastard thank you!
shakalaca said:
Here you have it
https://mega.nz/#!w0EQlQrL!V00keDHV_pwS_cUKwSZuIjFb55oqE8exv0MPlbi262g
Click to expand...
Click to collapse
do you have the same for UL-Z00T-WW-1.17.40.1234-user please?
Lookey at this gem guise...
http://forum.xda-developers.com/android/help/extract-dat-marshmallow-lollipop-easily-t3334117
I'll be honest I have actually no idea what this does lol. What is its purpose???
You should be able to use it to extract the contents of firmware packages and pull the recovery.img directly from it.
HampTheToker said:
You should be able to use it to extract the contents of firmware packages and pull the recovery.img directly from it.
Click to expand...
Click to collapse
This thing is impressive! Okay so I did it... but couldnt find the recovery
I'll check it out and reply back.
I had the same problem - I was on 1.16.xxxx
I followed these directions and I must tell you - it works perfectly:
http://forum.xda-developers.com/zenfone-2-laser/general/guide-how-to-flash-stock-rom-via-twrp-t3409768
Although, since I was so far back, I needed to flash all the 1.17.xx versions first, but it worked just fine.
Since none of these OTA roms included the recovery images (that I could find - they must somehow hide it from us) - there were no other way I could find to get the original factory recovery back, but it works great.
Now I need to find a way to re-root and re-TWRP - still working on that.
Good luck!
As the title says, there is no development for this device?, Thank you and forgive my bad english:good:
caedmonro said:
As the title says, there is no development for this device?, Thank you and forgive my bad english:good:
Click to expand...
Click to collapse
No, we can`t even flash twrp on the phone... i guess until then there is no chance to flash another rom at all.
I could not flash twrp and therefore boot rom cm14
Still there is apparently I try to port but I brickea, porte recovery twrp for lg k350h and experiencing I found a way to rootearlo at the beginning with the help of a friend but the steps were very long which was brickeaba easily now I saw that simplified it Thanks to a user of xda, thank you very much, after doing all that porte rom but was stuck in the logo, so far I could not flash twrp just boot because it is restored to the factory what I discovered is that the recovery is independent Of the menu that appears to be the recovery that shows two buttons if or not try in all possible ways but I have not succeeded
lineage 15.0 lg k8 android 8.0
caedmonro said:
As the title says, there is no development for this device?, Thank you and forgive my bad english:good:
Click to expand...
Click to collapse
There is one but I install it and the hard brike we go that I was left without mobile and neither doing the test point nor in mode meta a brick.
lineageosroms.org/forums/topic/lg-k8-lineage-os-15-android-oreo-ro
tattoosmistery said:
There is one but I install it and the hard brike we go that I was left without mobile and neither doing the test point nor in mode meta a brick.
lineageosroms.org/forums/topic/lg-k8-lineage-os-15-android-oreo-ro
Click to expand...
Click to collapse
Well, you shouldn't ever download anything from sites which have similar name to some ROM but it's not officiall site, in most cases that are sites who just want visits without actuall content. Also in ROM file name there is 64bit and AFAIK none of K8's have 64bit kernel. Next thing recovery they provided is over 16mb in size, that is a recipe for getting bricked in best case it will refuse to boot/flash, also kernel offset ramdisk offset are wrong according to my model (k350nds), that is also good recipe, I didn't check the kernel but I doubt it's right one, I'll unpack ROM just to see what is inside.
When you download ROM please use only trusted sites.
Edit: this is ROM for Tecno camon c7 its same chipset but it doesn't mean it is suitable for our phone. Whoever created this and said it's for k8 is an first class A-hole..
Professor Woland said:
Well, you shouldn't ever download anything from sites which have similar name to some ROM but it's not officiall site, in most cases that are sites who just want visits without actuall content. Also in ROM file name there is 64bit and AFAIK none of K8's have 64bit kernel. Next thing recovery they provided is over 16mb in size, that is a recipe for getting bricked in best case it will refuse to boot/flash, also kernel offset ramdisk offset are wrong according to my model (k350nds), that is also good recipe, I didn't check the kernel but I doubt it's right one, I'll unpack ROM just to see what is inside.
When you download ROM please use only trusted sites.
Edit: this is ROM for Tecno camon c7 its same chipset but it doesn't mean it is suitable for our phone. Whoever created this and said it's for k8 is an first class A-hole..
Click to expand...
Click to collapse
What do you mean, I got left without a phone or got an arrangement?
tattoosmistery said:
What do you mean, I got left without a phone or got an arrangement?
Click to expand...
Click to collapse
Sorry I don't understand what are you trying to say..
gottlasz said:
No, we can`t even flash twrp on the phone... i guess until then there is no chance to flash another rom at all.
Click to expand...
Click to collapse
if you flash recovery what happens ? it bootloops or it gets replaced by stock ? I have an idea on how to make it work ...
KevMetal said:
if you flash recovery what happens ? it bootloops or it gets replaced by stock ? I have an idea on how to make it work ...
Click to expand...
Click to collapse
If you flash it then the phone will not boot up just turn off after the warning message. Its becouse the recovery partition is checked during boot up so the lk (little kernel / bootloader) partition should be tweaked first to skip recovery checking...
gottlasz said:
If you flash it then the phone will not boot up just turn off after the warning message. Its becouse the recovery partition is checked during boot up so the lk (little kernel / bootloader) partition should be tweaked first to skip recovery checking...
Click to expand...
Click to collapse
have you tried flashing a no dm -verify .zip before booting
KevMetal said:
have you tried flashing a no dm -verify .zip before booting
Click to expand...
Click to collapse
Yes, but that zip only tweaks the boot image... (and it doesn't even work for our device)
then, first we need to get rid of the little kernel, so we can flash twrp and just then we can think in porting a lineageos rom for it?
SummonerArthur said:
then, first we need to get rid of the little kernel, so we can flash twrp and just then we can think in porting a lineageos rom for it?
Click to expand...
Click to collapse
Well if we get rid of it completely it will probably won't work at all, we need someone to alter function that checks if kernel or anything else is legitimate so that function always return true. If that is how it work.