yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy S III] duarian:
This one boots up fine for me.

KT. You should go show manta some love. My N10 is itching for an updated kernel of yours :)
[Verizon Samsung Galaxy S III] ktoonsez:
Been so busy with work that I havent had time to spend on that one at all, barely have enough time to build this one for you guys and building blind on this makes it even more difficult.
[Verizon Samsung Galaxy S III] Setco:
Stupid question...how do you turn the led off? Great kernel by the way...it's my one and only! Awesome job...
[Verizon Samsung Galaxy S III] SlimSnoopOS:
Thanks KT! This booted and has been running great the last two hours on SlimKat 3.2 build.
[Verizon Samsung Galaxy S III] xbiker321:
Lol. My led is flashing blue too.

I installed two different kernels since then. Both other kernels don't get rid of the flashing blue led. Guess im stuck with it for now.

EDIT: It finally stopped, works properly now.
[Verizon Samsung Galaxy S III] Prack:
Blue flashing has been added to the CM kernel so it will probably end up in a lot of kernels. It only does it during boot and I think it looks kind of cool anyway.
[Verizon Samsung Galaxy S III] Setco:
So mine continues to blink even after my phone has completely booted... Is this normal?
[Verizon Samsung Galaxy S III] Prack:
That would not be normal, after booting is finished it should stop (after all your start up apps are done booting)
[Verizon Samsung Galaxy S III] deuce237bblock:
My LED has been flashing on and off non-stop since the 2-20 build. I finally gave up and reflashed my ROM, it was really annoying me.

Sent by me.
[Verizon Samsung Galaxy S III] LuigiBull23:
All you had to do was plug then unplug your charger to get rid of it.
[Verizon Samsung Galaxy S III] deuce237bblock:
Wow, that whole time I didn't need to charge my phone. I guess I can blame my Lemon Juice for that.

Sent by me.
[Verizon Samsung Galaxy S III] Setco:
OMG do I feel like an idiot!! Lol
[Verizon Samsung Galaxy S III] Det0natoR:
No issues here with the LED on after boot on carbon. Quite a few night lies back I had that issue, but it has since been corrected.
[Verizon Samsung Galaxy S III] Jdelta9889:
On beanstalk.4.4.240. With ktoonz 1-28. Get errors when flashing to latest ktoonz.. Should I be flashing stock kernel before updating kernel?
[Verizon Samsung Galaxy S III] Jdelta9889:
Forgot to attach for reference
[Verizon Samsung Galaxy S III] Det0natoR:
Try reflashing the ROM, wipe cache/dalvik, fix permissions, flash kernel, re-wipe, fix permissions, then boot. I used to have to do that on beanstalk and the older carbon nightlies, but haven't had to do that on the newer carbon and kernel. Now I just have to flash the kernel, wipe, fix permissions then boot. Probably don't even have to wipe and fix permissions, but ktoonz recommends it.
[Verizon Samsung Galaxy S III] Aali1011:
So question ladies and gentlemen, I know this is due to my settings and was hoping to get some help but every time I receive a phone call it takes a solid 5 secs if not a little longer for the phone to wake up. It seems like a process too, the phone will vibrate or ring indicating the incoming call and then the back light on the buttons will come up and then the screen. Is there a specific setting I should shoot to first to resolve this?
[Verizon Samsung Galaxy S III] Jdelta9889:
That Got it

I had to wipe dalvik / cache, then flash existing ROM, then flash latest Kernel, then wiped again just to make sure! Thanks. Anybody know why this is necessarY?? I have never had to do this before.
[Verizon Samsung Galaxy S III] Casper34:
I have had this same issue. I figured it was ROM related, never tried cm11 without kt747..... now I think about it, I haven't tried any ROM without kt747.

Sent from my ghost white SGS3!
[Verizon Samsung Galaxy S III] Maphack:
Not sure if I had much of a problem beforehand.. But after I used android tuner to change my build.prop the calls I receive are pretty quick. Maybe not instant, but far faster than 5 seconds

Sent from my SCH-I535

:thumbup:
[Verizon Samsung Galaxy S III] Casper34:
What did you change in your build prop?

Sent from my ghost white SGS3!
[Verizon Samsung Galaxy S III] Aali1011:
Yes please do elaborate on this. i think I have been to lazy to actually set the kernel to default or another settings filer and tinker with the lower clock speeds and voltages. I can only assume it is that. Maybe the scheduler but i am doubtful of that.
[Verizon Samsung Galaxy S III] 4catalyst2cI:
Provided log to vanir as well. installation of 2\25 kt747 on latest vanir builds causes phone process to stop would love for this to be fixed just hoping to get some info from both sides . thanks here's the log :

https://www.dropbox.com/s/qhqoti7ha7w4cs6/name
[Verizon Samsung Galaxy S III] darkknight1812:
Did you try updating the ramdisk in the kernel with the one from the rom?
[Verizon Samsung Galaxy S III] 4catalyst2cI:
No I have not. Perhaps you could pm me an explanation of how I can do this?tia.
[Verizon Samsung Galaxy S III] Shallow_1:
Can I get a PM about that also please?:tia
[Verizon Samsung Galaxy S III] tprophit:
Finally getting around to upgrading from 4.2 (carbon 1.8), to 4.4. Will my preferred kt settings work with the upgrade?

Thank you.
[Verizon Samsung Galaxy S III] ktoonsez:
Change Log 03.09.2014

1. Update Ramdisk for CMs new framework file to fix phone FC

2. A bunch of interactive governor updates

3. A bunch of ondemand governor updates

4. Lots of zcache updates/patches

5. remove extraneous loop in apexq camera driver

ENJOY !!!!!!!!!!! :D
[Verizon Samsung Galaxy S III] tihsllub:
Can somebody help me. Its recovery related.
[Verizon Samsung Galaxy S III] Maphack:
Dang, no go on PAC 3/8.

Rule of thumb, don't install a kernel with a release date any later than your ROM?

Sent from my SCH-I535

:thumbup:
[Verizon Samsung Galaxy S III] cheekoo:
Really? I am on an older slimkat rom and the latest build runs like a champ.
[Verizon Samsung Galaxy S III] Maphack:
Idk it stops at "loading apps" (I think that's what it's called) for both 3/9 and 2/25. Something might be sketchy with PAC though.. Problems varying from phone to phone, it seems.

Sent from my SCH-I535

:thumbup:
[Verizon Samsung Galaxy S III] cheekoo:
2/25 never worked for me, but 2/20 and the latest one are great. But yeah definitely could be decide specific.
[Verizon Samsung Galaxy S III] tprophit:
Get installation aborted message. Have downloaded twice, aborts with both downloads. Running carbon 03/03 nightly.

Suggestions?

Thanks.
[Verizon Samsung Galaxy S III] SlimSnoopOS:
Flashed fine for me using TWRP 2.7 and 03/09 SlimKat 3.6 weekly!
[Verizon Samsung Galaxy S III] tprophit:
Last one flashed fine for me too. Using CWM, as I have for years...
[Verizon Samsung Galaxy S III] tihsllub:
I need an older kernel. I am on the LS 3/9/14 build. The latest KT hangs on boot.

---------- Post added at 01:26 PM ---------- Previous post was at 12:51 PM ----------

The kernel build on my version of liquid is 3.4.78 lean kernel version. I like all the options with KT.
[Verizon Samsung Galaxy S III] SlimSnoopOS:
Since KT doesn't post frequently, search for his name in this thread. His last release was on 2/25 and I think the release prior to that was 2/09 or somewhere around that date.
[Verizon Samsung Galaxy S III] mikejr83:
Try clearing cache before installing. I think KT's install script doesn't use tmp so the last install's files are still hanging out.
[Verizon Samsung Galaxy S III] tprophit:
Thanks. That worked.
[Verizon Samsung Galaxy S III] Maphack:
So some people are getting this to work with PAC 4.4?

Sent from my SCH-I535

:thumbup:
[Verizon Samsung Galaxy S III] swift2989:
Well guys I'm going to leave this right here for your pleasure.http://xdaforums.com/showthread.php?t=2681909 Hope you guys enjoy. I ran kt kernel 03-09 and it works perfect with this rom
[Verizon Samsung Galaxy S III] bmeek:
Here's a potential issue you might want to look into...

http://xdaforums.com/showthread.ph...icture.
[Verizon Samsung Galaxy S III] JFam5:
Doesn't work for me on pacrom 4.4.2 either.

It worked great on O&S TW4.3 but not for PacRom 4.4.2. It won't boot regardless of clearing caches first or after kernel flash. I'm making due though.

Comments on PacMans G+ page says that it has to due with the ram disk. I'm reading on how to build my own kernel but I'm a newb at this level.
[Verizon Samsung Galaxy S III] 4catalyst2cI:
KT is working excellent here ( vanir 4.4.2 3\15 nightly build) thanks again [MENTION=4325945]ktoonsez[/MENTION]!
[Verizon Samsung Galaxy S III] PWn3R:
This kernel doesn't work -- i have tried to flash it with carbon rom, pacrom, cm, slim. Always fails to flash completely. You get the app but not the kernel. I tried two versions of CWM and TWRP 2.6.3.1 and 2.7.0.0. I don't know what's wrong but none of the versions of this kernel have worked for me since sometime in december. Every time i try to flash it gives an assert error around extracting the boot.img.
[Verizon Samsung Galaxy S III] SlimSnoopOS:
Hmm, worked fine for me on SlimKat 3.4 which I reported upon release. Flashed fine on TWRP 2.6.3.1 and each KT release has worked since this version of TWRP was available for me.

Edit: I meant SlimKat 3.6
[Verizon Samsung Galaxy S III] tprophit:
I had a problem first two times I tried, then went to 3/9 Carbon nightly, and it has worked fine ever since, also on 3/11 and 3/14 Carbon.

Using latest CWM recovery..
[Verizon Samsung Galaxy S III] Casper34:
Try clearing your caches. I have to every time I install it due to ROM nightlies.

Sent from my ghost white SGS3!
[Verizon Samsung Galaxy S III] Mystique:
How do I start with a blank config?

I have made some changes to a governor that I want to change back to defaults.. but I want to keep things like the voltages (using the slider(s) is/are very difficult to get right..)

and how do you set the defaults for the governor back?

Thanks in advance
[Verizon Samsung Galaxy S III] ktoonsez:
Dont set ktweaker to set things on boot. Then reboot and answer no to all questions.
[Verizon Samsung Galaxy S III] Maphack:
Can't you just change the governor to something else, then change it back and it starts with default settings?

On a semi-related note, my I/O scheduler settings don't seem to stick and periodically I have to open up ktweaker and it will ask me and I hit yes. My ktoonservative settings stick, though.. Bfq scheduler, if that matters.

Sent from my SCH-I535

:thumbup:
[Verizon Samsung Galaxy S III] Mystique:
Also looks as if there is no hot plug tuning.. Or is it in something that I'm missing?

Thanks in advance.
[Verizon Samsung Galaxy S III] sweeds:
Ktoonz is running really well on SlimKat 3.8. Noticeably faster. And KT has a long track record for reliability with the v2vzw.

However one bug. The LED is constantly blinking blue. Even with the ROMs LED settings all off.

If I receive a notification that uses the LED, that resets it and it works fine from here one out. Or if I plug/unplug, which uses the LED, it works from then on. When I reboot my phone, the bug is back and same things happen.

Any advice? I tried rolling back to KT 02-25-14. Other Kernels don't have same prob, but could be tied into the ROM I'm using.
[Verizon Samsung Galaxy S III] Matt1024:
I had the same problem and it finally quit. I'm not sure if it'll come back but I even tried using gravity box. What profile are you using?
[Verizon Samsung Galaxy S III] sweeds:
I was using the default profile.

Installing the Lightflow app has patched the blinking led problem. It must have overridden the bug.
[Verizon Samsung Galaxy S III] Matt1024:
I just rebooted mine to see if it would flash again and it did for about a minute and then quit. I still have gravity box set to do the same.
[Verizon Samsung Galaxy S III] Kreeker:
This is probably the wrong place to ask this, but does anyone have a solution for wlan_wake kernel wakelock that keeps my phone awake? My phone is awake 75% of the time.
[Verizon Samsung Galaxy S III] sweeds:
You could try turning off WiFi more often when not in use.

You're right, a better place to ask this kind of question is to search for the xda thread on BetterBatteryStats and do some true debugging.
[Verizon Samsung Galaxy S III] Casper34:
Menu/wifi.... hit your menu button, turn off scan wifi when wifi is off.

Our phones will scan wifi to know where your at. Even if you turn wifi off.

Sent from my ghost white SGS3!
[Verizon Samsung Galaxy S III] Wh1t3Rose:
You gotta love it when someone says they have a fix for something and then does not post the solution. Not sure if troll or....
[Verizon Samsung Galaxy S III] Maphack:
It was a preset using Android tuner. I meant to reset my build.prop and figure out exactly which, but became lazy and forgot...

I think it's

ro.telephony.call_ring.delay to 800

I'm pretty positive the default value is 0.

Hope it helps.

That or

ro.lge.proximity.delay to 25

If the first one doesn't work.

I don't think I use the second one, though.

Gl.

Edit: I have killjoy installed and after restoring my build.prop, back to normal, before checking what the single preset changed, the 2nd option is just gone... The first one remains.

Sent from my SCH-I535

:thumbup:
[Verizon Samsung Galaxy S III] Maphack:
Did this build.prop change help anyone?

Sent from my SCH-I535

:thumbup:
[Verizon Samsung Galaxy S III] BrUhNiGGs:
Hey KT hope you can update the kernel soon with the latest cm commits as of 3/24. It contains a fix for the camera in which I was dying to get fixed for the last year or so. Thanks
[Verizon Samsung Galaxy S III] Mystique:
sec_stor.mdt

Has anyone been able to figure this out?

Is this anything to be concerned with?

http://pastebin.com/84dNDjbr

...

8< -- SNIP -- >8

E/QSEECOMAPI: (17278): Error::Cannot open the file /firmware/image//sec_stor.mdt

8< -- SNIP -- >8

...
[Verizon Samsung Galaxy S III] ktoonsez:
Change Log 3.24.2014

1. Some ramdisk updates

2. Complete sync with CM as of the commits from 3.22
[Verizon Samsung Galaxy S III] Wh1t3Rose:
Update broke Wifi for me. Just hangs and never actually turns on. On Omni ROM
[Verizon Samsung Galaxy S III] BrUhNiGGs:
WiFi works fine for me. On CM nightly
[Verizon Samsung Galaxy S III] Wh1t3Rose:
I'll make a logcat.

Edit: he only needs the dmesg right? Because nothing WiFi related shows in dmesg after enabling Wi-Fi

Edit2: went back to an older build of KT747 and Wi-Fi works again.
[Verizon Samsung Galaxy S III] vlucchetti:
Likewise on CarbonRom 3/24 d2vzw version
[Verizon Samsung Galaxy S III] DADER:
I am on slim rom & I flashed this kernel but one flow appears after each restart that the blue led of booting keeps blinking for a long time & only goes off when the led is used for other things eg; notifications or battery plug in.

Any one knows a solution for that ?

Thanks
[Verizon Samsung Galaxy S III] Deliquified:
Dirty flashed 3/24 d2vzw and new kt kernel. Wiped cache/dalvik. Wifi works fine.
[Verizon Samsung Galaxy S III] vlucchetti:
I'll try this again. I did the cache/davlik fix permissions thing last time, see what happens this time.

No go, same thing.

As an aside, when I tried to flash the 3/9 kt over this, got an error in cwm. This is why we nanroid!
[Verizon Samsung Galaxy S III] Deliquified:
You can try carbon 3/19 d2lte, turn wifi on and get it working, reboot to recovery, flash 3/24 d2vzw, boot, back to recovery, flash kt latest, wipe cache/dalvik
[Verizon Samsung Galaxy S III] vlucchetti:
Thanks. I have the 3/24 d2vzw working with wifi on kt 3/9. Did all that good stuff a couple of times after flashing the 3/24 kt with the same results, ie nothing. Sees no wifi networks at all, so I'll wait on the kt update.
[Verizon Samsung Galaxy S III] tprophit:
Is it still recommended to disable mpdecision?

Thanks.
[Verizon Samsung Galaxy S III] sweeds:
Same thing here. I installed Lightflow, an app for controlling LED notifications, and it overrides whatever bug in SK+KT that makes the LED blink.
[Verizon Samsung Galaxy S III] Mystique:
SLP Governor..

https://github.com/ktoonsez/KT747-JB/blob/tw4.3/drivers/cpufreq/cpufreq_slp.c

https://github.com/ktoonsez/KT747-JB/blob/tw4.3/drivers/cpufreq/cpufreq_pegasusq.c

Just so it gets confirmed..

Seems SLP is just a version of pegasusq that does not accept changes..
[Verizon Samsung Galaxy S III] ktoonsez:
Do you guys want me to remove the CM LED code?
[Verizon Samsung Galaxy S III] Prack:
No!
[Verizon Samsung Galaxy S III] sweeds:
Appreciate your response kt.

Would ROM settings or Lightflow app still be able to control the LED?

I personally like the functionality, just a slight annoyance that the LED always blinks blue on startup until another noti comes in and overrides.

Not a game changer worth stripping out the functionality completely IMO. Thx.
[Verizon Samsung Galaxy S III] ktoonsez:
Lol, we will see what others say I guess. The last 15 pages is just nothing but LED whinning :eek:
[Verizon Samsung Galaxy S III] Prack:
The pretty blue light blinking during boot makes me feel safe. Do not remove.
[Verizon Samsung Galaxy S III] tprophit:
The blinking during boot doesn't matter to me one way or another. But, if it Congo after boot (it doesn't), it would annoy me.
[Verizon Samsung Galaxy S III] vlucchetti:
No, No, No!
[Verizon Samsung Galaxy S III] Casper34:
The only time I blink cyan blue is on boot. I like it. It shows me something is happening. I vote to keep it. :)

Sent from my ghost white SGS3!
[Verizon Samsung Galaxy S III] DADER:
Make a poll for that :P
[Verizon Samsung Galaxy S III] ktoonsez:
I think everybody wants it in so I will keep it :good:
[Verizon Samsung Galaxy S III] ktoonsez:
Change Log 3.28.2014

1. Linux 3.4.83

2. Linux 3.4.84

3. CM sync

4. Ramdisk sync with CM
[Verizon Samsung Galaxy S III] Wh1t3Rose:
The last two updates have not worked for me. I'm on Omni ROM 23rd Build. Your last update broke Wi-Fi for me and this new one won't even flash. I'm on the latest TWRP.
[Verizon Samsung Galaxy S III] BHermes21:
No problems here. I'm on beanstalk. I was on an older ROM and it broke WiFi but once I updated the ROM i tried again and no problems
[Verizon Samsung Galaxy S III] brandoncarlson33:
How is everyone flashing this? Every time I do it installs fine but when I boot in to recovery I keep getting errs grrr......
[Verizon Samsung Galaxy S III] Shallow_1:
Have you updated your recovery?
[Verizon Samsung Galaxy S III] th3taman:
So based on the comments above, your kernel updates Wifi and Bluetooth drivers. A nandroid will restore how they were before flashing the kernel. Will flashing a new ROM or updated version of a ROM create problems in the future if your kernel isn't also flashed?

Was going to flash your kernel, but after seeing this...just want to understand a little more. I've flashed kernels on other devices with minimal issues, so not overly concerned. Just more curious. :D
[Verizon Samsung Galaxy S III] jgrimberg1979:
Flashing a new rom will restore the wifi drivers. There is no need to be concerned. If you want to go back to stock just flash a stock rom. And the answer to your last question is no it wont cause problems. I have never had any issues
[Verizon Samsung Galaxy S III] th3taman:
Thanks, that was my assumption from previous personal experience. Conversation just threw me off a little I guess.
[Verizon Samsung Galaxy S III] ktoonsez:
The issue was people were making kernels without including there modules, so a kernel was getting flashed and keeping my drivers. It was mostly in the beginning of the S3 forum.
[Verizon Samsung Galaxy S III] th3taman:
Thanks, feel more comfortable flashing now. :D
[Verizon Samsung Galaxy S III] jgrimberg1979:
Back in the kexec days. Man in don't miss those days at all
[Verizon Samsung Galaxy S III] xXJay_RXx:
If you look back, look at what KToonz quoted and look at what the guy originally posted. He edited his post lol
[Verizon Samsung Galaxy S III] maurogg84:
Is anybody having problems with screen off profiles, whenever I turn the screen back on it stays at the same screen off speed?
[Verizon Samsung Galaxy S III] jgrimberg1979:
I would avoid using screen off.profiles via ktweaker. Ktoonsez has said that in the beginning although he may have fixed ir since then. Regardless I never use it and my battery life is still excellent
[Verizon Samsung Galaxy S III] ktoonsez:
Are you on 9-10? There is just no way its still doing that on 9-10. Did you fix permissions in recovery? Did you clear app data for KTweaker?
[Verizon Samsung Galaxy S III] maurogg84:
I did everything except clear the app data, let me try to see if that works, I'll get back to you. I'm on 9/10.
[Verizon Samsung Galaxy S III] unboostedzc:
paranoidandroid 2.10 port - 9/9 nightly build

http://xdaforums.com/showthread.php?t=1858298
[Verizon Samsung Galaxy S III] jgrimberg1979:
Ktoonsez

Donation $15 sent

Transaction ID: 1F3645939N055223J.

Thanks for working on the vibration adjustment setting!
[Verizon Samsung Galaxy S III] ktoonsez:
Thanks buddy :D :highfive: :good:

Hope you saw my second response for the vibration feedback. Here it is just in case:

Good news I found it. I will add it under "Extras" in the KTweaker for next release. Valid values will be from 5 - 126
[Verizon Samsung Galaxy S III] jgrimberg1979:
Yes I did thanks !
[Verizon Samsung Galaxy S III] JCSIII:
The App for this keeps force closing, not sure what to do
[Verizon Samsung Galaxy S III] enomele:
I had that problem once, are you using a newish CM10 (or based off of) nightly and have tried fixing permissions and or clearing app data? Sounds obvious but I forgot how I got it working. I think I had switched ROMs so it didn't matter.
[Verizon Samsung Galaxy S III] JCSIII:
It is the September 5th version of CM10 and I installed it and wiped cache and davlick and fix permission. It was working but all of sudden it started force closing

---------- Post added at 10:02 PM ---------- Previous post was at 10:00 PM ----------

I cleared data and it works now thanks
[Verizon Samsung Galaxy S III] maurogg84:
I'm loving your kernel, running all day with minimum at 384 to max 2106, been lowering voltage on all steps simultaneously without a problem. I don't use the steps below 384 because of flickering on slim bean, I think is Rom related.
[Verizon Samsung Galaxy S III] maurogg84:
Some screenshots
[Verizon Samsung Galaxy S III] brandoncarlson33:
Ya everything is good no issues until I boot in to recovery for something then the err comes up don't seem to hurt anything just annoying as I used this kernel forever I even odened back to stock and started from scratch
[Verizon Samsung Galaxy S III] Shallow_1:
CWM or TWRP?
[Verizon Samsung Galaxy S III] brandoncarlson33:
Cwm 6045
[Verizon Samsung Galaxy S III] Shallow_1:
I'm using Phil's 6047
[Verizon Samsung Galaxy S III] brandoncarlson33:
I'll try it but I was using that b4 I odened back to stock
[Verizon Samsung Galaxy S III] Shallow_1:
Crazy....then I don't have much to offer ya....sorry....I'll keep thinking on it though:(
[Verizon Samsung Galaxy S III] tprophit:
Tried, twice, (2 separate downloads), with Carbon 3/29. Sticks at KT boot animation.
[Verizon Samsung Galaxy S III] Maphack:
Working good with AICP 3/28 and running AICP gapps

Sent from my SCH-I535

:thumbup:
[Verizon Samsung Galaxy S III] MorphiousGX:
While I know it may not make sense. But any chance you can retrofit the old 4.2 kernel with the new ktweaker?? Or maybe I can download the new ktweaker apk?
[Verizon Samsung Galaxy S III] Casper34:
I experienced the same issue. Thanks [MENTION=4325945]ktoonsez[/MENTION] for leaving in the led control. It never got that far into loading, so I knew exactly what was wrong.

Cm11 2/27 nightly. That's the Last nightly that worked flawlessly for me.

Sent from my ghost white SGS3!
[Verizon Samsung Galaxy S III] Kreeker:
I just flashed 3.28.2014 and my touch input is not working. Touching the screen does nothing. I'm on the latest PA.
[Verizon Samsung Galaxy S III] Prack:
Looks like text/camera issues are fixed in CM11 4/2/14 build. If you could sync it up with 4/2 I'd greatly appreciate it.
[Verizon Samsung Galaxy S III] ktoonsez:
Change Log 04.02.2014

1. Linux 3.4.85

2. Cm sync from last 2 days of commits

3. Revert "input: touchscreen: d2_fw: Update firmware", which was causing the boot issue and no touch for some people