[Kernel] (ver 041) Mako KK 4.4 (UV/OTG/CPU/GPU OC/Hybrid Linux 3.4+) [08-02-14]

faux123

Senior Member
Dec 16, 2010
8,536
34,426
113
West Los Angeles
www.canonspike.com
I got into many red LED situations, I was able to come out of it everytime by using the procedure I posted above (that post was from pure experience I had).

red led bootloop unbrick procedure

1. plug phone into USB cable connected to computer
2. wait for it to go into charge animation
3. unplug, then press power button to boot, immediately press vol up + vol down.
4. hopefully you booted into bootloader mode (rinse and repeat steps 1~4 if you can't get to this point)
5. chose recovery (if your recovery is corrupted, repeat steps 1~4 and do fastboot flash recovery cwmxxx.img)
6. from recovery choose restart system

if you can't get to step 2, because N4 has a bug with battery capacity, plug your phone into AC charge and let it charge for a few mins. then restart from step 1...
 

raycaster3

Senior Member
Apr 17, 2011
3,888
1,202
0
S.Ogden
It also bricked my phone when I flashed on Dax's rom. I flashed via fastboot, typed fastboot reboot and that was it for me, it never came back on, just went straight to the red flashing LED. I could get into fastboot, but like the other users if I chose any option it rebooted and I ended up with red flashing LED again.
Hmm I have not used fastboot once though I've been making flashables for all of the betas I've flashed and had no problems.

Thanks for the instructions faux. That oughtta help some pretty freaked out folks get back into the game. :D

DARKSIDE
 
Last edited:

abnormalreply

Senior Member
Sep 1, 2012
498
234
0
New York City
I got into many red LED situations, I was able to come out of it everytime by using the procedure I posted above (that post was from pure experience I had).

red led bootloop unbrick procedure

1. plug phone into USB cable connected to computer
2. wait for it to go into charge animation
3. unplug, then press power button to boot, immediately press vol up + vol down.
4. hopefully you booted into bootloader mode (rinse and repeat steps 1~4 if you can't get to this point)
5. chose recovery (if your recovery is corrupted, repeat steps 1~4 and do fastboot flash recovery cwmxxx.img)
6. from recovery choose restart system

if you can't get to step 2, because N4 has a bug with battery capacity, plug your phone into AC charge and let it charge for a few mins. then restart from step 1...
Steps 1-3 do not work to get into the bootloader. However, I can get in by just doing vol down + power. Selecting recovery causes a reboot but it does not boot into recovery, it just loops the Google logo after the reboot. With some help from another user, I deduced that this is a problem with the battery not supplying the CPU or motherboard with current. This is confirmed by: 1. Unplugging the charger while it's in the bootloader, shuts the phone off, and 2. Doing "fastboot getvar battery-voltage" does not give an output, meaning my overclocking (to 1.6Ghz) fried something involved in the battery communicating with the motherboard. Furthermore, I cannot boot up into Android because the charger doesn't supply power to the phone through the entire boot process--the battery -must- be able to supply at least a little bit of power before the ROM can boot up. So, during the boot process, when the phone tries to use power from the battery, it automatically shuts off and loops because the battery is not able to supply any power.
 
  • Like
Reactions: yyz71 and h00py

sarni84

Senior Member
May 17, 2011
3,068
676
0
Levittown, PA
I got into many red LED situations, I was able to come out of it everytime by using the procedure I posted above (that post was from pure experience I had).

red led bootloop unbrick procedure

1. plug phone into USB cable connected to computer
2. wait for it to go into charge animation
3. unplug, then press power button to boot, immediately press vol up + vol down.
4. hopefully you booted into bootloader mode (rinse and repeat steps 1~4 if you can't get to this point)
5. chose recovery (if your recovery is corrupted, repeat steps 1~4 and do fastboot flash recovery cwmxxx.img)
6. from recovery choose restart system

if you can't get to step 2, because N4 has a bug with battery capacity, plug your phone into AC charge and let it charge for a few mins. then restart from step 1...
Yea but that was Samsung not lg I have gotten into those situations too. Thing is it wouldn't even show a charging animation at all. I got into fast boot by holding power. Plugging phone in then holding the normal fast boot button combo.....then if I unplugged it in anyway fast boot would go off . it not supposed to do that. Only time I seen blinking red light was when phone was on charger or hooked up to comp....reminds me of the Xbox red light of death. There is something more to this and this situation I was not able to get out of. Basically putting the phone to 1.8 in CPU master free then hitting apply caused it screen flashed for a sec then nothing. Usually phone will reboot when something like that happens...idk could have been the oc app could have been anything. But I will say I tried your procedure and every other one available. The fact that that I got into fast boot the way I did was weird . it wouldn't do it the normal way (power and volume down
 
Last edited:

raycaster3

Senior Member
Apr 17, 2011
3,888
1,202
0
S.Ogden
That's scary ****. Weird too since I've been running mine at 1.8 with faux's app and have been just fine. Hmm strange indeed. We may need to be a lot more careful with this device than others. I had a weird situation where I hit reboot with quickboot and the splash screen showed then faded away into a blood red screen with a faded black strip in the middle it was faint and holding power and vol down got me out of it but I **** myself to be sure.

DARKSIDE
 

raycaster3

Senior Member
Apr 17, 2011
3,888
1,202
0
S.Ogden
My apologies for the profanity. Some good news to report is I've been running 003 all day and had nothing but smooth flowing battery friendly goodness. :D

DARKSIDE
 

abnormalreply

Senior Member
Sep 1, 2012
498
234
0
New York City
That's scary ****. Weird too since I've been running mine at 1.8 with faux's app and have been just fine. Hmm strange indeed. We may need to be a lot more careful with this device than others. I had a weird situation where I hit reboot with quickboot and the splash screen showed then faded away into a blood red screen with a faded black strip in the middle it was faint and holding power and vol down got me out of it but I **** myself to be sure.

DARKSIDE
The phone will rarely ever stay at 1.8 for a significant amount of time, but if you try to run a benchmark software (which most of us do), it pins the processor at 1.8 which can lead to disastrous results. That said, even if you're not running a benchmark, you never know when a random app will decide to start eating up processor speed and you will have unsuspectingly be pinning your phone at 1.8 anyways. So, that's something to watch out for I guess.
 

raycaster3

Senior Member
Apr 17, 2011
3,888
1,202
0
S.Ogden
The phone will rarely ever stay at 1.8 for a significant amount of time, but if you try to run a benchmark software (which most of us do), it pins the processor at 1.8 which can lead to disastrous results. That said, even if you're not running a benchmark, you never know when a random app will decide to start eating up processor speed and you will have unsuspectingly be pinning your phone at 1.8 anyways. So, that's something to watch out for I guess.
Indeed. I never run benchmarks unless a dev specifically asks me to. Hence I have not run one on this kernel as of yet and well I'm not on too big of a hurry. Besides we're about to see an update worth intellidemand shortly according to @faux123 on Twitter.

DARKSIDE
 

BravoMotorola

Senior Member
Oct 17, 2010
1,597
385
0
Can you upload a mirror for the 003 image? The link he provided doesn't work for me.

Sent from my Nexus 4 using xda premium
If nobody does by the next half hour I will since I'll be home by then. BTW wow, F that mod! He's pathetic and immature! Just another looser trying to control people on the internet. Probably neglected in real life...
 

sarni84

Senior Member
May 17, 2011
3,068
676
0
Levittown, PA
If nobody does by the next half hour I will since I'll be home by then. BTW wow, F that mod! He's pathetic and immature! Just another looser trying to control people on the internet. Probably neglected in real life...
Yes I had a bad few days myself he gave me an infraction because I was defending myself Cuz everyone jumped on me when explaining my situation granted I did use profanity a few times tho so I guess I deserved it . oh well new phones here so raycaster u running aokp with fauxs newest and his oc app and everything is good? Kind of scared:
 

raycaster3

Senior Member
Apr 17, 2011
3,888
1,202
0
S.Ogden
Yes I had a bad few days myself he gave me an infraction because I was defending myself Cuz everyone jumped on me when explaining my situation granted I did use profanity a few times tho so I guess I deserved it . oh well new phones here so raycaster u running aokp with fauxs newest and his oc app and everything is good? Kind of scared:
Yep. Been running it all day. Perfectly fine.

DARKSIDE

---------- Post added at 03:43 AM ---------- Previous post was at 03:41 AM ----------

Can you upload a mirror for the 003 image? The link he provided doesn't work for me.

Sent from my Nexus 4 using xda premium
Check pm.

DARKSIDE
 

raycaster3

Senior Member
Apr 17, 2011
3,888
1,202
0
S.Ogden