gpl | abyss kernel 2.00 | B170/B180/NCS/fRomFuture

andreas5232

Senior Member
Feb 13, 2013
158
246
0
Munich
dev.erhard.cc
For NCS 2.0 and B180 Official Build, you need B180 boot.img instead of B170 boot.img :)
Where do I get B180?
My P9 says "No Updates" when I open the updater app from the settings.

The previous build I had tried "abyss-caf-eva-stock-20160825.img" was working with B170, except the SuperSU features.

I'll try to get to the bottom of this.
Thanks for all your efforts! :good:
I am sure, together we can get this sorted out! :)
 
  • Like
Reactions: adinkwok

Sebastiaanlabr

Senior Member
May 12, 2011
228
65
48
Dordrecht
Hello, i tried to use your kernel. But it did not succeed. My phone staying at the Huawei logo. I have the EVA-L09 running stock rom with root and xposed. When I flash the stock boot.img again my phone boots successfully.

Edit: I see it's do to the B80 update.
 
  • Like
Reactions: adinkwok

adinkwok

Retired Forum Moderator / Inactive Recognized Deve
May 28, 2013
2,712
10,116
0
6ix
adin.dev
fRomFuture users! I will be uploading a test build (twrp zip).

Here's what went wrong (may or may not solve boot issues)
- always remember that dirty coding is bad, make sure everything is organized!
- if you want to take a look, look here at this change
1. I accidentally committed a bunch of random stuff by accident, only the stuff declared in the title was supposed to be a part of that change
2. I realized that I forgot to add a line (mkbootimg_tools/mkboot ramdisk_future zip_folder/boot.img), so the fRomFuture kernel actually uses the ncs 1.2 ramdisk :/

I will have the build up very soon, hang tight guys! Refresh this post as I will edit it this with the link.

edit so turns out, the fRomFuture version didn't even have a ramdisk in the boot.img! :silly:

abyss-kernel-eva-future-2.00.zip
 
Last edited:

andreas5232

Senior Member
Feb 13, 2013
158
246
0
Munich
dev.erhard.cc
I am so confused right now :crying:
Hooray! :D :D :D
Running the updated abyss stock 2.00 version on EVA-L09 with B170 now. :good:
Will take it as my daily driver and report back, how it performs.
MD5: 26ff340a9d3c017642d61ae01a96f2f5

What I have tested so far:
  • Camera
  • WiFi/LTE
  • SuperSU (root)
  • New CPU governor (Intelliactive)
  • Fingerprint
  • Calls
 
Last edited:
  • Like
Reactions: kep2008

xvir

Member
Sep 12, 2012
38
3
0
Hooray! :D :D :D
Running the abyss stock 2.0 version on EVA-L09 with B170 now. :good:
Will take it as my daily driver and report back, how it performs.

What I have tested:
  • Camera
  • WiFi/LTE
  • SuperSU (root)
  • New CPU governor (Intelliactive)
  • Fingerprint
congrats! how? :) thanks
 

smohanv

Senior Member
Nov 5, 2006
2,108
639
183
Slough
Boot loops with updated B180 (stock). I had my stock backup via TWRP before trying this kernel. Returned to stock.

---------- Post added at 12:46 PM ---------- Previous post was at 12:40 PM ----------

Hooray! :D :D :D
Running the updated abyss stock 2.00 version on EVA-L09 with B170 now. :good:
Will take it as my daily driver and report back, how it performs.
MD5: 26ff340a9d3c017642d61ae01a96f2f5

What I have tested so far:
  • Camera
  • WiFi/LTE
  • SuperSU (root)
  • New CPU governor (Intelliactive)
  • Fingerprint
I noticed from your signature that you have pre-ordered Saygus V². I did two years ago. Finally had to cancel few months ago. Have you got one now? Have they lined up dispatches?
 
Last edited:

smohanv

Senior Member
Nov 5, 2006
2,108
639
183
Slough
That's probably because the Kernel image is based on B170's boot.img.
Maybe you can upload B180's boot.img somewhere, so @kwoktopus can add it to his build script.

Is B180 ROM running stable?
Didn't receive it via OTA yet, but I'll see if I can update it tonight.

Regarding Saygus: You got a PM, it's too much OT here.
I have extracted model and boot related img files and uploaded to multiupload.biz

Here is the link: http://www.multiupfile.com/f/e0bf6c74b8

Dropbox link: https://www.dropbox.com/s/jayl68g41ato5sb/B180 extracted.7z?dl=0

Edit: By the way, i forgot to mention that B180 is very stable and causing no issues. After I flashed (fresh) I unlocked bootloader, flashed TWRP and wiped data as well. This helped me to remove all bloatware installed in data partition.

A common issue in MM (whether it is EMUI or stock), phone dialer do not work properly after evey restart. On some restart phone dialer do not work and the fix require another restart. People who have not noticed this issue are missing calls. I do not see this issue discussed anywhere. Many of my friends using Nexus 5X also experiencing this issue.
 
Last edited:
  • Like
Reactions: adinkwok

adinkwok

Retired Forum Moderator / Inactive Recognized Deve
May 28, 2013
2,712
10,116
0
6ix
adin.dev
I have extracted model and boot related img files and uploaded to multiupload.biz

Here is the link: http://www.multiupfile.com/f/e0bf6c74b8

Dropbox link: https://www.dropbox.com/s/jayl68g41ato5sb/B180 extracted.7z?dl=0

Edit: By the way, i forgot to mention that B180 is very stable and causing no issues. After I flashed (fresh) I unlocked bootloader, flashed TWRP and wiped data as well. This helped me to remove all bloatware installed in data partition.

A common issue in MM (whether it is EMUI or stock), phone dialer do not work properly after evey restart. On some restart phone dialer do not work and the fix require another restart. People who have not noticed this issue are missing calls. I do not see this issue discussed anywhere. Many of my friends using Nexus 5X also experiencing this issue.
B180 version coming soon once I get to school :cool:
 
  • Like
Reactions: darthkir