i got bootlooped when i flash the kernel though fastboot, and when i try to just boot from it (instead of flashing) it also bootloops. how do i fix that?
[Kernel] (ver 041) Mako KK 4.4 (UV/OTG/CPU/GPU OC/Hybrid Linux 3.4+) [08-02-14]
- Thread starter faux123
- Start date
did that, doesnt work. I have no idea what is wrong, i fastboot flash franco's kernals and it works fine. so weird
My suggestions to be added, if you could:
Screen off profiling, governor and max-clock speed during screen off.
Touch Booster, disable or set to a different value
Yeah
, those two would be great.
Maybe individual volt controls
Screen off profiling, governor and max-clock speed during screen off.
Touch Booster, disable or set to a different value
Yeah
, those two would be great.Maybe individual volt controls
Just a cautionary word to everyone
Since this is an overclockable kernel, I imagine many of the folks trying it would want to use Antutu/Quadrant to see how it measures up to the stock, which is what I tried to do, but ended up getting some serious issues. I OC'd to 1.6GHz and tried Antutu (was running AOKP.) The phone crashed and wouldn't boot. I flashed the stock image via fastboot (the bootloader loads, but nothing else) and same problem: not booting. It's not turning on at all without the charger plugged in, and when it does, it loops after the Google logo. (The battery isn't dead.) So I'm on the phone with Google and they're sending me another.
So, it may just be that I've got a defective device (but I've seen a few other people describe the same problem.) This is a testing/beta kernel and of course I use it at my own risk, but I just wanted to give a heads up to folks using it.
Since this is an overclockable kernel, I imagine many of the folks trying it would want to use Antutu/Quadrant to see how it measures up to the stock, which is what I tried to do, but ended up getting some serious issues. I OC'd to 1.6GHz and tried Antutu (was running AOKP.) The phone crashed and wouldn't boot. I flashed the stock image via fastboot (the bootloader loads, but nothing else) and same problem: not booting. It's not turning on at all without the charger plugged in, and when it does, it loops after the Google logo. (The battery isn't dead.) So I'm on the phone with Google and they're sending me another.
So, it may just be that I've got a defective device (but I've seen a few other people describe the same problem.) This is a testing/beta kernel and of course I use it at my own risk, but I just wanted to give a heads up to folks using it.
You can revive it by:
when it bootlooped, press vol up+down at the same time, it will bring you to bootloader mode, then select recovery, then from within recovery select reboot, then it should be fine. Nexus 4 is almost unbrickable
Like I mentioned, I can get into the bootloader, but nothing else. When I select recovery, the phone actually has to reboot into recovery--which doesn't happen. It loops at any 'automated' boot even if I select reboot bootloader, it loops. The only way I can actually get into the bootloader, is by manually pressing the vol down + power.You can revive it by:
when it bootlooped, press vol up+down at the same time, it will bring you to bootloader mode, then select recovery, then from within recovery select reboot, then it should be fine. Nexus 4 is almost unbrickable
No faux it happened to me too. And it could not be revived with any button combo or IMG flashed in fast boot. All I got was a blinking ted light when connecting USB. I was running same setup exactly as other guy. I oced the kernel went into antutu on aokp. Phone shutoff. Only thing I could get into was a download mode I've never seen before not like Samsung's.... (Made a thread on it) no big deal because you know what you get yourself into 1 doing this so it is okay and I am NOT mad besides you make the best kernels . who knows what it really was it could have been anything but it's definitely happen and there was no reviving it and I am pretty tech savvyYou can revive it by:
when it bootlooped, press vol up+down at the same time, it will bring you to bootloader mode, then select recovery, then from within recovery select reboot, then it should be fine. Nexus 4 is almost unbrickable
Are you still trying to fix it? Or you gonna give up and call Google like I did? lol If so, brace yourself for a 30min wait time.
It's great to see that Faux is developing for the N4, but it's unfortunate that I won't be able to use any Mods for a while.
And does anyone know if these kernels have Conservative, Smartass, or Interactive available?
And does anyone know if these kernels have Conservative, Smartass, or Interactive available?
Not sure i have only tried the kernel on CM. I am sure it should work on Stock.
got mine at T Mobile I already went to the store this morning I have my new device right now thankfully I was able to relock bootloader and everything
I think he already got a replacement unit in his other thread with all of the troll bltchers. And I don't think it was the kernel because this phone will protect itself against heat due to the throttling, and if it's not heat what else from the kernel would cause it? It was simply a defective device. I've had no problems with this kernel and have done plenty with it. After running a few benchmarks you notice the scores will go down considerably because of the throttling too. Not sure what problem what you had. Sounds weird though.
Yo bro are u running this with aokp? Cuz stock ROM I was good. IDK some weird sh#t
THE ONLY ROM THIS KERNEL IS GOOD FOR AT THE MOMENT IS STOCK ROM.
I also experienced the issues stated in this thread with other Roms that weren't stock.
Sent from my Nexus 4 using xda app-developers app
I also experienced the issues stated in this thread with other Roms that weren't stock.
Sent from my Nexus 4 using xda app-developers app
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.
Our Apps
Get our official app!
The best way to access XDA on your phone
Nav Gestures
Add swipe gestures to any Android
One Handed Mode
Eases uses one hand with your phone