Database Users

initrd.gz problems

I am at a loss here. I am running CLK 1.5 PA 1.1a with tytung r3, however, the device gets icon flash similar to icecreamtosti, where the icons do not respond without a reboot.
I wanted to flash Dorimanx v6.9 or v7.2 HWA, and understand I need to place the ROMs initrd.gz file in the initrd-custom folder. I have tried this on Snow Leopard & XP to no avail using a variety of different compression programs including 7-zip. I unzip the kernel and the ROM, put the PA 1.1a initrd.gz in the correct folder and rezip it. Each time though, even after re-downloading the kernel and ROM, I get an error within CWM, which reads that the installation has been aborted. Why is this? Do I need to re-compile the kernel in Android Kitchen? (I do not know how to do this by the way) or what else am I doing incorrectly? I have trawled the XDA HD2 forum, but had no luck. Suggestions?

aldersonalex said:
I am at a loss here. I am running CLK 1.5 PA 1.1a with tytung r3, however, the device gets icon flash similar to icecreamtosti, where the icons do not respond without a reboot.
I wanted to flash Dorimanx v6.9 or v7.2 HWA, and understand I need to place the ROMs initrd.gz file in the initrd-custom folder. I have tried this on Snow Leopard & XP to no avail using a variety of different compression programs including 7-zip. I unzip the kernel and the ROM, put the PA 1.1a initrd.gz in the correct folder and rezip it. Each time though, even after re-downloading the kernel and ROM, I get an error within CWM, which reads that the installation has been aborted. Why is this? Do I need to re-compile the kernel in Android Kitchen? (I do not know how to do this by the way) or what else am I doing incorrectly? I have trawled the XDA HD2 forum, but had no luck. Suggestions?
Click to expand...
Click to collapse
You don't unzip the contents. By doing so you break the signing. What you wanna do is open your ROM zip using 7 zip then browse to the initrd.gz file copy to your desktop, close everything. Now open the kernel zip file browse to the initrd-custom folder open it. Now double click and drag the initrd.gz file from your desktop to the 7-zip window which has the kernel zip opened to the initrd-custom folder.
Sent from my GT-I9100 using Tapatalk

elesbb said:
You don't unzip the contents. By doing so you break the signing. What you wanna do is open your ROM zip using 7 zip then browse to the initrd.gz file copy to your desktop, close everything. Now open the kernel zip file browse to the initrd-custom folder open it. Now double click and drag the initrd.gz file from your desktop to the 7-zip window which has the kernel zip opened to the initrd-custom folder.
Click to expand...
Click to collapse
I did exactly as you said, but still the same end result :/

aldersonalex said:
I did exactly as you said, but still the same end result :/
Click to expand...
Click to collapse
Have you tried installing the kernel without adding the initrd.gz? I remember getting that error when the download was inturupted or something. So if you still get that error without editing the zip, then it most likely is the zip file and you need to redownload. Because if you did exactly as i said then it should be working. Im a long time user of his kernel's on almost every ROM out there and never once ran into any troubles. But we will surely figure this out
Can you post a link to the ROM you are using, and i'll download it and edit the kernel then repost it in this thread for you.
---------- Post added at 03:33 PM ---------- Previous post was at 02:43 PM ----------
Here it is i found the thread. its kernel 7.2 from DM.
Here

elesbb said:
Have you tried installing the kernel without adding the initrd.gz? I remember getting that error when the download was inturupted or something. So if you still get that error without editing the zip, then it most likely is the zip file and you need to redownload. Because if you did exactly as i said then it should be working. Im a long time user of his kernel's on almost every ROM out there and never once ran into any troubles. But we will surely figure this out
Can you post a link to the ROM you are using, and i'll download it and edit the kernel then repost it in this thread for you.
---------- Post added at 03:33 PM ---------- Previous post was at 02:43 PM ----------
Here it is i found the thread. its kernel 7.2 from DM.
Click to expand...
Click to collapse
Thank you so much, is this the HWA Kernel though?

aldersonalex said:
Thank you so much, is this the HWA Kernel though?
Click to expand...
Click to collapse
Yes 7.2 hwa from dorimanx
Sent from my GT-I9100 using Tapatalk

elesbb said:
Yes 7.2 hwa from dorimanx
Click to expand...
Click to collapse
Thank you so much, I wanted to experiment whether v6.9 is better than v7.2. Would it be possible to repack that kernel too?

aldersonalex said:
Thank you so much, I wanted to experiment whether v6.9 is better than v7.2. Would it be possible to repack that kernel too?
Click to expand...
Click to collapse
Haha yes I could, I personally preferred 7.2 over 6.9 but my favorite is 6.5D xP
Did you flash the zip yet?
Sent from my GT-I9100 using Tapatalk

elesbb said:
Haha yes I could, I personally preferred 7.2 over 6.9 but my favorite is 6.5D xP
Did you flash the zip yet?
Click to expand...
Click to collapse
I flashed it with success, but it doesn't feel as snappy as tytung r3, it takes a few seconds to unlock and load programs, even clocked at 1612mhz and experimenting with ZRAM on and off. Thank you though, I will probably stick with tytung's for the moment though, did you use 7-zip to transfer the initrd.gz file?

aldersonalex said:
I flashed it with success, but it doesn't feel as snappy as tytung r3, it takes a few seconds to unlock and load programs, even clocked at 1612mhz and experimenting with ZRAM on and off. Thank you though, I will probably stick with tytung's for the moment though, did you use 7-zip to transfer the initrd.gz file?
Click to expand...
Click to collapse
Hmm i wonder if its cause i took the initrd.gz from an older version of Paranoidandroid. I have version .6 on my computer thats why i used it. I'll redownload the latest and try with that. I might even flash it myself and test it out. Maybe the lib files need to be transfered as well. Dorimanx has by far been the best kernel for myself, but i dont really care for ICS yet but when i was testing the waters i used DM kernel and i loved it. Snappy responsive and pretty awesome. It just lacks a boat load of features i rely on in CM7. CM9 claimed they will re add the features once they iron kinks out so once they release a better build i will most likely convert

elesbb said:
...but i dont really care for ICS yet but when i was testing the waters i used DM kernel and i loved it. Snappy responsive and pretty awesome. It just lacks a boat load of features i rely on in CM7. CM9 claimed they will re add the features once they iron kinks out so once they release a better build i will most likely convert
Click to expand...
Click to collapse
Very curious by this statement, and admittedly, my own android experience is limited... I've used ACA SD android for a number of months, and have switched over to ICS. Currently with ICT & DM's 6.9 kernel, but love the UI in hybrid mode of PA... and so, am really curious what you meant when you alluded to 'missing features' that were in CM7, but not CM9. What was lost? What am I missing? (sincere question) Thanks, -Rob

RobE. said:
Very curious by this statement, and admittedly, my own android experience is limited... I've used ACA SD android for a number of months, and have switched over to ICS. Currently with ICT & DM's 6.9 kernel, but love the UI in hybrid mode of PA... and so, am really curious what you meant when you alluded to 'missing features' that were in CM7, but not CM9. What was lost? What am I missing? (sincere question) Thanks, -Rob
Click to expand...
Click to collapse
Well, there are two that i pretty much LOVE and cannot live without xD
Those are,
1. Disable full screen (status bar remains visible no matter the app, has a "hide" button if you wish to use full screen in a game or app, then you can unhide by pressing home key(my choice))
2. Really big one, lockscreen gestures. I love being able to draw a 'C' on my lockscreen and open the phone whitout having a custom app slot being taken up. Plus, gestures allow for an app to run while still displaying the lockscreen.
THose are the only two big ones i will miss, there are a few more small ones but i dont remember without flashing CM9 and checking And its been awhile since ive tested the waters, so i might download the latest AOKP and CM9 to see where they are at. But they both are good and pretty cool. CM7 is just perfect for me. No issues what so ever.

elesbb said:
Hmm i wonder if its cause i took the initrd.gz from an older version of Paranoidandroid. I have version .6 on my computer thats why i used it. I'll redownload the latest and try with that. I might even flash it myself and test it out. Maybe the lib files need to be transferred as well.
Click to expand...
Click to collapse
It would be brilliant if you could test out the kernel with the initrd.gz from 1.1a PA, that might explain why it felt slow when I tested the original.

[KERNEL][I8200N] Baroni-Kernel Alpha

I can give ABSOLUTLEY no gurantee!! All you do with your phone will be on your own. I'm not responsible if your phone will brick or whatever...
Attation! This kernel is for the I8200 variant ONLY... the I8190 is absolutley not compatible !!!
Kernel should be work also for I8200/I8200Q/I8200L-Variants, but can not be gurateed as the basis was I8200! If it works then a notice will be fine!
If you are not sure about the process, the data are important on your phone or you need it as a daily phone, then LET IT BEE, and wait for the messages that it is safe to use. Its important at the beginning that users with knowledge tried it at first !
Changelog:
12.02.2016: Long time ago, but now after a lot of investigating some new things comes up. Check what was done
05.01.2014: I try to work on the kernel over x-mas in my free time, but I must say that the source of samsung which was provided on opensource.samsung.com is not really funny stuff... there are so many coding errors, which was. not able for me to solve directly. So now I started to examine other kernel sources, and will try to port a more main.tained source to the i8200. From My point of view this will be the only way to produce an more accurate kernel for our device, and get the possibility to include also selinux what is needed for a kitkat-rom. Nevertheless, it is not easy to work on that stuff, because I'm not an expert on kernel work (but I learn every day more , so if you know someone with more kernel experiences, it would be very helpful to get a contact...
Baroni-V0.1 contains:
Basis of opensource from Samsung with some bugfixing
fixed recovery-boot-loop with a config-setting which must be used special in the Recovery zImage
Loglevel pushed down to minimum
Uber-Toolchain 4.9
set onDemand-Governor to standart. just to check how that works
start implementing SmartAssV2-Gonernor, but leave it inactive, due to some compile-errors.
bringing SELinux to work for future kernel releases if needed for > 4.4
Planned:
new govenors at the moment not established (will come later)
more other stuff (depending on learning-curve
Installation:
Install a recovery for safetyreasons (I prefer TWRP https://www.dropbox.com/s/d3rnfp3vabz9ee8/twrp_i8200_corrected.7z?dl=0
Read carefully the hints of the usage in the following firts post: http://forum.xda-developers.com/galaxy-s3-mini/general/s-iii-mini-ve-i8200-n-t2826565 (There also the needed Odin (3.09) can be get)
Make backups of the complete phone, and be sure that you know what you do!
Download the right Firmware for your phone from http://www.sammobile.com/firmwares/ (just to have a other safety fallback in your hand!)
Download the file, start odin as usual (all kies-tasks closed!)
extract the file, and put it to AP
put the phone in Downloadmode (Vol-down,Home-key and powerbutton), and connect the phone with PC
flash the kernel, and let the phone reboot
pray
If things go wrong, please give everytime the following information's:
what you did before
what exactly happened (its not easy to help if you say: it did not work )
which rom in which version, which recovery and which version of my Kernel you use
try to get a /proc/last_kmsg (if a unknowen reboot appears) and/or Logcat, Build prop, CPU info, Sysctl, Kmsg, Dmesg and send it to me (or as a attachment to the post) for further analyse (you can use that tool for it: https://play.google.com/store/apps/details?id=com.bassel.andylog )
Attention: First checks seem to be that I8200 (without N or L or Q) did not work atm.
Download:
kernel_i8200n-Baroni:
https://www.androidfilehost.com/?w=files&flid=47763
kernel_i8200n-Stock.7z (to getting back to stock kernel via Odin):
https://www.dropbox.com/s/xfhufcpxl5kxmue/kernel_i8200n-Stock.7z?dl=0
Recoverys (with fixed recovery boot loop):
https://www.androidfilehost.com/?w=files&flid=49834

There was a mistake in the initramfs. was corrected now. If you download the V0.7 yesterday, please dont use it... Try V0.8.

One question.
SolarPlexus said:
There was a mistake in the initramfs. was corrected now. If you download the V0.7 yesterday, please dont use it... Try V0.8.
Click to expand...
Click to collapse
My Friend.
Yesterday I tried to install its kernel but my phone did not start properly.
I wanted to do a restore from a backup that had done, but the recovery (TRWP) did not restore the data partition.
Is there any chance that I happen again the same with this version?

Danh23 said:
My Friend.
Yesterday I tried to install its kernel but my phone did not start properly.
I wanted to do a restore from a backup that had done, but the recovery (TRWP) did not restore the data partition.
Is there any chance that I happen again the same with this version?
Click to expand...
Click to collapse
Attention with TWRP-Recovery. Data-Partition restore seems to be not right. At the moment please did not use it, because it can delete your data-partition. We have to investigate it further! Other partitions seems to be ok, but its a good Idea if you copy your important data also manually to a other storage (like PC) while you trying things of this thread.

i install the kernel ans stuck into samsung logo.if i flash the stock kernel i will fix it?
stock kernel?can you upload it?

KwstPap said:
i install the kernel ans stuck into samsung logo.if i flash the stock kernel i will fix it?
stock kernel?can you upload it?
Click to expand...
Click to collapse
Did you made a backup with twrp (as described)? If yes, then make a restore only with boot marked in the list.
Otherwise, which version did you have? Plain n/l/q? Than I can make a package for Odin...
send with my Oneplus One (bacon) SlimKat Tapatalk

About the data recovery, use aroma FM to restore. Out worked for me

hahhhahaha i forgot it to take a backup hahaha .i reflashing the stock firmware... i Have i8200N
but why the kernel doesnt work on me?

KwstPap said:
hahhhahaha i forgot it to take a backup hahaha .i reflashing the stock firmware... i Have i8200N
but why the kernel doesnt work on me?
Click to expand...
Click to collapse
You are a funny guy... Flasching things without reading the guide is something like a other guy I know from kentucky fried movie (Danger-seeker)
Nevertheless, I added in first thread the stock kernel for i8200n to flash with odin.

SolarPlexus said:
You are a funny guy... Flasching things without reading the guide is something like a other guy I know from kentucky fried movie (Danger-seeker)
Nevertheless, I added in first thread the stock kernel for i8200n to flash with odin.
Click to expand...
Click to collapse
hahahahaha always forget to take a backup .but i am very stypid .i had a backup on my pc.hahah in one weak i have reflashing the stock formware 5 times and the root recovery and other staff again hahaha
thanks for the stok kernel

SolarPlexus said:
You are a funny guy... Flasching things without reading the guide is something like a other guy I know from kentucky fried movie (Danger-seeker)
Nevertheless, I added in first thread the stock kernel for i8200n to flash with odin.
Click to expand...
Click to collapse
¿which brings benefits to install this kernel?

RodsonBorja said:
¿which brings benefits to install this kernel?
Click to expand...
Click to collapse
Atm nothing... Its alpha and not working. Unfortunately I'm a little bit blocked by illness and x-mas and was not able to work on it... Maybe next week...
send with my Oneplus One (bacon) SlimKat Tapatalk

Hi to all followers of this thread.
Just to give an update: I try to work on the kernel over x-mas in my free time, but I must say that the source of samsung which was provided on opensource.samsung.com is not really funny stuff... there are so many coding errors, which was not able for me to solve directly. So now I started to examine other kernel sources, and will try to port a more maintained source to the i8200. From My point of view this will be the only way to produce an more accurate kernel for our device, and get the possebility to include also selinux what is needed for a kitkat-rom...
Nevertheless, it is not easy to work on that stuff, because I'm not an expert on kernel work (but I learn every day more , so if you know someone with more kernel experiences, it would be very helpful to invite him/her. To ask in forums (also in xda) is something what I do, but unfortunately the responding are not every time safe...
So I wish you all a happy new year, and lets work together to bring our device a little bit forward
SolarPlexus

Ask @dtrail1 he know how the kernel thing work.
Maybe he'll support you

VallNAr said:
Ask @dtrail1 he know how the kernel thing work.
Maybe he'll support you
Click to expand...
Click to collapse
Ask MARDON he made the kernel for Galaxy Ace - maybe he support Your work.

Any progress on the kernel? Is it on github?

Why does this not suport usb flash drives or can the function be ported
Gershy353

I think it must be activated on both sides. Kernel and ROM...
send with my Oneplus One (bacon) SlimKat Tapatalk

SolarPlexus said:
I think it must be activated on both sides. Kernel and ROM...
send with my Oneplus One (bacon) SlimKat Tapatalk
Click to expand...
Click to collapse
How is this done i have the sandisk dual flash drive but its useless on my device
Gershy353

Ah, you mean otg support, not sdcard seen as USB instead of mtp?
send with my Oneplus One (bacon) SlimKat Tapatalk

[ROM][OFFICIAL][5.0] Android Lollipop Alpha

https://forums.oneplus.net/threads/rom-official-5-0-android-lollipop-alpha.223252/
ALPHA STAGE GUYS, EXPECT BUGS, MAKE A BACKUP IN RECOVERY BEFORE FLASHING!!
THIS ROM IS MADE BY ONEPLUS, NOT ME.
Here we go, official L for the oneplus one (made by oneplus) is here, there are a few bugs which can be found in the main link above.
Happy flashing!
And Happy new year!
All credit goes to oneplus. I'm just sharing the link!

It's not cyanogen mod though!It's an alpha build but no one at the OPO thread hasen't installed it yet!
Sent from USS Intrepid NCC-1631
---------- Post added at 07:22 PM ---------- Previous post was at 07:21 PM ----------
At least they are building their own rom!And happy new year guys!
Sent from USS Intrepid NCC-1631

I tried it but had an error about updater script. When i time i will try again

störte said:
I tried it but had an error about updater script. When i time i will try again
Click to expand...
Click to collapse
I haven't tested it yet, I'm not sure that I will. Cause of the bugs I am seeing on the OPO thread.

guys you need to unmount system before you flash otherwise the updater script will fail.

Great will retry

I'm using it right now. No real problems noticed so far except for a couple of crashes at first boot. It's really smooth. Pure AOSP.

Yes very pure.
Strange cant get into recovery anymore

Does anyone know if they're using the same sources as Cyanogen? (It had a weird name. CM started to suck when they started using it.)
Or is it PURE AOSP?

dugzino said:
Does anyone know if they're using the same sources as Cyanogen? (It had a weird name. CM started to suck when they started using it.)
Or is it PURE AOSP?
Click to expand...
Click to collapse
Pure CAF AOSP.

I can only recommend not to use it. My Recovery was deleted and i cant get into any Recovery anymore. I get only a chinese fastboot.. Tried to flash my Recovery via adb. On first boot it worked but then not anymore. So be very carefull

störte said:
I can only recommend not to use it. My Recovery was replaced and i cant get into any Recovery anymore. I get only a chinese fastboot.. Tried to flash my Recovery via adb. On firsat boot it worked but then not anymore. So be very carefull
Click to expand...
Click to collapse
Works perfect for me.

Thats strange. Anyway i flashed a recovery and deleted the system in order to restore a backup. It looks nice but the Recovery Problem must be solved in order for me to try again.
BUt i like the Wallpaper

störte said:
Thats strange. Anyway i flashed a recovery and deleted the system in order to restore a backup. It looks nice but the Recovery Problem must be solved in order for me to try again.
BUt i like the Wallpaper
Click to expand...
Click to collapse
I think you need to reflash recovery when you install it, which is easy to do from fastboot.

I did that. But even then i was not able to enter recovery

very very different modem, compared it against all the five I've got here (not all the previous modems) and can't see anything like it.
sha1 DD7A19EA09FF60485A6D8469F25C750A9AE627AE
md5 BA7C0A93BB63955408459ACA88BAAFFC

TeChNoC4AzY said:
I think you need to reflash recovery when you install it, which is easy to do from fastboot.
Click to expand...
Click to collapse
You would be correct. In fact, they specifically mention that in the instructions directly before Step 1.
This build does not have a built-in recovery
Click to expand...
Click to collapse

Well consider that it's build from their own source it's normal that it's asop-like but gonna give it a try tomorrow. Of course hope they will merge latest 5.0.3 that will come in these week and all other feature of cyanogenmod11S

confed said:
You would be correct. In fact, they specifically mention that in the instructions directly before Step 1.
Click to expand...
Click to collapse

rudi_j7 said:
guys you need to unmount system before you flash otherwise the updater script will fail.
Click to expand...
Click to collapse
How is that done?

Nemesis Rom patch for GSM N910P

This thread is dead! Please delete!

aaron74 said:
I tried posting this other night but xda started maintenance that night. And I just started new job and van broke down tonight. So I'm late. But anyhow this is what I wrote that night.
After seeing last few post(pg 85) of Nemesis Rom. I decided to put a patch together for you guys installing on GSM 910P (should also work for N910T also). This is how i installed this on my device and works.
Because this is aroma Rom I didn't want to flash fixes after Rom.(I wasn't sure if it'd cause a problem). So this will help you integrate. This patch already has T Mobile data patch inside and also works for Sprint gsm users like me.(personally cause I use gsm, I prefer it This way). Sorry Sprint users i can't help.
This patch also includes RamV2 kernel for Sprint. But there's also 2 empty folders one for N910T and one that's called Custom. That's where you put your boot.img.
If you need to edit build.prop further for your data it's in there but works for me as is.
Also note I left the 2csc files (features.xml & others.xml) untouched.
Pretty much all I did was add the aurora data fix minus csc edits. Plus options for kernel. I also added Flipboard cause i like it over upday.
How to use.
1. Unpack Rom.
2. Unzip my patch twice (I double zipped it so noobs can't try installing in twrp)
3. Put your boot.img in folder you want.( In /nemesis/kernel/your device)(already has Ram V2 in N910P)
4. Copy all files over to root of Rom zip.
5. Repack Rom and flash.
Choices will be in aroma for your kernel.
Enjoy!
https://mega.nz/#!I1EzQbIJ!LX_bXLwg50WZ9xFmHVmnhbssm3QduZyvEld37KHkl88
Click to expand...
Click to collapse
@aaron74 if I'm able to do this successfully I'll press the thanks button anytime you post anything anywhere.
Just quote my name and it"ll will be done
Fingers crossed

natibongo said:
@aaron74 if I'm able to do this successfully I'll press the thanks button anytime you post anything anywhere.
Just quote my name and it"ll will be done
Fingers crossed
Click to expand...
Click to collapse
Thanks , just let me know if any problems. I work all day so I check in more at night.

aaron74 said:
Thanks , just let me know if any problems. I work all day so I check in more at night.
Click to expand...
Click to collapse
Unfortunately I couldn't get it to work on my N910P
Aroma ROM didn't recognise my kernel.
It showed kernel for only N910F and N910G
I later put my boot.img into in both folders on two different times but ended in bootloop and intermittent vibrations.
Thanks again for your guide
I'm grateful

natibongo said:
Unfortunately I couldn't get it to work on my N910P
Aroma ROM didn't recognise my kernel.
It showed kernel for only N910F and N910G
I later put my boot.img into in both folders on two different times but ended in bootloop and intermittent vibrations.
Thanks again for your guide
I'm grateful
Click to expand...
Click to collapse
I installed mine this way and worked. But when I made script to share I added the other options. So let me check, maybe i typo in my script.

natibongo said:
Unfortunately I couldn't get it to work on my N910P
Aroma ROM didn't recognise my kernel.
It showed kernel for only N910F and N910G
I later put my boot.img into in both folders on two different times but ended in bootloop and intermittent vibrations.
Thanks again for your guide
I'm grateful
Click to expand...
Click to collapse
So sorry for that. When I built the patch I put the wrong build.prop in it. I was testing different settings on my device and that was a bad one. :crying:
I fixed link and updated post. Everything should be fine now. It is identical to the Rom I packed that I installed. :good:
Haste makes waste!

aaron74 said:
So sorry for that. When I built the patch I put the wrong build.prop in it. I was testing different settings on my device and that was a bad one. :crying:
I fixed link and updated post. Everything should be fine now. It is identical to the Rom I packed that I installed. :good:
Haste makes waste!
Click to expand...
Click to collapse
Ok @aaron74 I'm going to give one more try.
But can you give a detalid guide as to the kind of files to be copied to which destination?
The last time I copied only the boot.img file to the nemesis/device name folder in the original Rom.
I see META-INF in your patch, do I have to copy that as well and overwrite it since folders with same name are found in the original Rom?
Thanks

aaron74 said:
So sorry for that. When I built the patch I put the wrong build.prop in it. I was testing different settings on my device and that was a bad one. :crying:
I fixed link and updated post. Everything should be fine now. It is identical to the Rom I packed that I installed. :good:
Haste makes waste!
Click to expand...
Click to collapse
@aaron74 I have finally got it working on my N910P.
Maybe you can ask @anggara08 to update his post so that other N910P users could also benefit from it.
You are a genius!

natibongo said:
@aaron74 I have finally got it working on my N910P.
Maybe you can ask @anggara08 to update his post so that other N910P users could also benefit from it.
You are a genius!
Click to expand...
Click to collapse
Sorry but my time is limited to a few hours at night, to get on here. I use to get on all the time, was self employed, but now working for someone.
But you copy the whole folders over to root of Rom. But you obviously got it working.
I made a post already on devs thread. Told him he could post it there if he wants. I didn't post it there cause it's just for our device and didn't want to disrupt his thread.
Glad you got it going. I love this Rom. Runs good, good battery, awesome Rom control app. Other N7 ports run alright to but I hate that bright white boot up screen they have, plus I have to mod them a lot to get running right.
I just hope this dev stays with the project.
And no, I am not a genius. I've just retained a lot of knowledge from tinkering and from all the dev and modders here on xda. But thanks for the vote of confidence. :laugh:

natibongo said:
!
Click to expand...
Click to collapse
Also, Do you use Sprint service? (Cdma)
Or GSM service?

Battery usage.
I've been running Rom for 3 days now. So battery stats should be calibrated ok by now.
Below are some pics of my battery usage. I've been working a lot so you can see I don't have much screen on time. But I think the battery usage of this Rom is very good, especially with the Ram kernel.

Do you have to resign zip for success?
Edit: After having issues attempting to install the rom with this patch, I did the following to successfully install:
1. Unzip Rom
2. Unzip patch twice
3. Take the folders inside of the Nemesis-patch folder and copy them to the inside of the NEMESIS_V2_NOTE7_PORT_N4_SNAPDRAGON folder.
4. Select everything inside of the NEMESIS_V2_NOTE7_PORT_N4_SNAPDRAGON folder and zip it up as NEMESIS_V2_NOTE7_PORT_N4_SNAPDRAGON_PACKED
5. Transfer NEMESIS_V2_NOTE7_PORT_N4_SNAPDRAGON_PACKED to the root of your sd card
6. Flash packed zip.
Thanks for the patch @aaron74 and thanks for the rom @anggara08

aaron74 said:
Also, Do you use Sprint service? (Cdma)
Or GSM service?
Click to expand...
Click to collapse
I use GSM.
You are a genius because you made it possible for me to install a ROM that I wanted so badly
Only problem is the ambient light sensor.
It doesn't work properly
The screen goes very low even in bright environment.
To get it working I always have to pretend to make a call and put the phone close to my ear and back before it works
But for that and the fingerprint, everything works flawlessly.

natibongo said:
I use GSM.
You are a genius because you made it possible for me to install a ROM that I wanted so badly
Only problem is the ambient light sensor.
It doesn't work properly
The screen goes very low even in bright environment.
To get it working I always have to pretend to make a call and put the phone close to my ear and back before it works
But for that and the fingerprint, everything works flawlessly.
Click to expand...
Click to collapse
That's from AOD. It's buggy on all these N7 ports. Either turn it off. Or what seems to help me, if your screen opens up dark, just relock phone pushing power button, and immediately push it again to unlock it.
It's been working for me, and only takes 5 extra seconds. AOD also flashes for me, which I haven't found a cure for yet.

aaron74 said:
That's from AOD. It's buggy on all these N7 ports. Either turn it off. Or what seems to help me, if your screen opens up dark, just relock phone pushing power button, and immediately push it again to unlock it.
It's been working for me, and only takes 5 extra seconds. AOD also flashes for me, which I haven't found a cure for yet.
Click to expand...
Click to collapse
OK
I'll try your method too and see

reekotubbs said:
Do you have to resign zip for success?
Edit: After having issues attempting to install the rom with this patch, I did the following to successfully install:
1. Unzip Rom
2. Unzip patch twice
3. Take the folders inside of the Nemesis-patch folder and copy them to the inside of the NEMESIS_V2_NOTE7_PORT_N4_SNAPDRAGON folder.
4. Select everything inside of the NEMESIS_V2_NOTE7_PORT_N4_SNAPDRAGON folder and zip it up as NEMESIS_V2_NOTE7_PORT_N4_SNAPDRAGON_PACKED
5. Transfer NEMESIS_V2_NOTE7_PORT_N4_SNAPDRAGON_PACKED to the root of your sd card
6. Flash packed zip.
Thanks for the patch @aaron74 and thanks for the rom @anggara08
Click to expand...
Click to collapse
No, you don't need to resign.
Did you download my current link? When I first posted this, I had wrong build.prop file in zip. And I just fixed it a couple days ago.
What program are you using to zip with? Also are you using Sprint phone with gsm?

aaron74 said:
No, you don't need to resign.
Did you download my current link? When I first posted this, I had wrong build.prop file in zip. And I just fixed it a couple days ago.
What program are you using to zip with? Also are you using Sprint phone with gsm?
Click to expand...
Click to collapse
I figured that you didn't have to zip. And yes, I was working with your newest build.prop. I am on a Sprint phone with gsm for freedompop, but about to use tmobile.
I am seeing some issues with the rom though that I didn't see in Norma v10.
1. NFC is missing
2. Rom Control is different
3. I am unable to titanium backup restore many things which causes FC's all over the place.
4. AOD is horrible.
Is there any way to grab AOD, NFC and Rom Control from Norma v10, since they are fixed on that rom?

reekotubbs said:
I figured that you didn't have to zip. And yes, I was working with your newest build.prop. I am on a Sprint phone with gsm for freedompop, but about to use tmobile.
I am seeing some issues with the rom though that I didn't see in Norma v10.
1. NFC is missing
2. Rom Control is different
3. I am unable to titanium backup restore many things which causes FC's all over the place.
4. AOD is horrible.
Is there any way to grab AOD, NFC and Rom Control from Norma v10, since they are fixed on that rom?
Click to expand...
Click to collapse
You probably can swap. It's just figuring out exactly what to swap and erase. I was gonna look into some of this. But I've been too busy with work.
Good luck!

---------- Post added at 12:28 AM ---------- Previous post was at 12:26 AM ----------
[/COLOR]Please, I'm a little shy in this, I did what I say in the thread, but the truth is I do not understand the process well, there's a way I can explain it easier. Or images. Thank you and good work, greetings from Dominican Republic!

Tsmra said:
---------- Post added at 12:28 AM ---------- Previous post was at 12:26 AM ----------
[/COLOR]Please, I'm a little shy in this, I did what I say in the thread, but the truth is I do not understand the process well, there's a way I can explain it easier. Or images. Thank you and good work, greetings from Dominican Republic!
Click to expand...
Click to collapse
Sorry bud. I haven't had much time to get on here.
Yes I wrote the thread a lil vague, more for people that are use to this stuff.
When I get some time, I can try to walk you through this and make a lil better guide.
This is just bad timing. I got so many things going at once. Just started new job, fuel pump went out on car, just bought a new ssd for my laptop trying to get time to install fresh Linux. Just put new 128gb sd in this phone and all my files are gone. Between all that and Christmas stuff with kids.
I use to be on here hours at a time down to hours per week.
I actually just seen new Ram V3 kernel for our device and was gonna update. I'll get back with ya. :fingers-crossed:

forced 4K boot.img for stock?

I know there are a few kernels/boot.img to force native 4K all the time on AOSP based ROMs, but are there any for Stock or Stock based ROMS?
*Dang! Thought I was in the Q&A and just realized I posted this in the wrong section and can't delete or move it.

You might be able to remove the 1080p configuration in the copyleft archive just like in the aosp kernel to get a 4k stock kernel. I haven't looked at it so I don't know if it will work for sure, but its worth a try.
Edit: Looks like it might have worked.

Sepo190 said:
You might be able to remove the 1080p configuration in the copyleft archive just like in the aosp kernel to get a 4k stock kernel. I haven't looked at it so I don't know if it will work for sure, but its worth a try.
Edit: Looks like it might have worked.
Click to expand...
Click to collapse
Could You share the Image with us?:angel:

Miustone said:
Could You share the Image with us?:angel:
Click to expand...
Click to collapse
Yeah, sure. This is a .235 kernel that has been working surprisingly well for me. I used the ramdisk from shoey63's kernel repack here https://forum.xda-developers.com/xz-premium/development/kernel-repository-t3801795, so you need to flash that drmfix.zip too.
A couple of things I have run into though. The finish button wasn't showing up at the end of the setup wizard, so you have to go through that on the stock kernel and then flash this modified one. You might be able to fix it by changing the dpi, but I haven't tried that. You also cant set up any lock screen security until you flash the kernel or it will boot loop when flashed. So, the process that worked for me was:
1) flash stock .235
2) go through setup wizard NOT setting lock screen/fingerprint security
3) flash this kernel, drm fix and magisk
4) reboot
5) setup fingerprint/lockscreen security
You can change the screen dpi by using the wm density command or changing ro.sf.lcd_density in your build.prop.
https://mega.nz/#!o5FjxYwZ!zDS8DRaTnpER7e8YQOyyLjg_hY970geF9QaZajx5oO8
Does anyone know what changes the drmfix requires other than adding "export LD_PRELOAD drmfix.so:drm****.so" to the init.environ.rc in the ramdisk?

Sepo190 said:
A couple of things I have run into though. The finish button wasn't showing up at the end of the setup wizard, so you have to go through that on the stock kernel and then flash this modified one. You might be able to fix it by changing the dpi, but I haven't tried that. You also cant set up any lock screen security until you flash the kernel or it will boot loop when flashed. So, the process that worked for me was:
1) flash stock .235
2) go through setup wizard NOT setting lock screen/fingerprint security
3) flash this kernel, drm fix and magisk
4) reboot
5) setup fingerprint/lockscreen security
You can change the screen dpi by using the wm density command or changing ro.sf.lcd_density in your build.prop.
https://mega.nz/#!o5FjxYwZ!zDS8DRaTnpER7e8YQOyyLjg_hY970geF9QaZajx5oO8
Click to expand...
Click to collapse
If I'm currently on 235, basically all I need to do is flash your kernel + drmfix, right? Or is a fresh install really needed? Btw, do you pass safetynet on your kernel?

iArvee said:
If I'm currently on 235, basically all I need to do is flash your kernel + drmfix, right? Or is a fresh install really needed? Btw, do you pass safetynet on your kernel?
Click to expand...
Click to collapse
I'm pretty sure you're going to need to do a fresh install. You can try without, but I have a feeling you are going to bootloop. It doesn't pass safteynet, but I can probably add the patch in for you. I'll take a look at it later tonight or tomorrow. Now that .270 CE1 is out I was going to move to that, but I can do the .235 one too if you want.

Sepo190 said:
I'm pretty sure you're going to need to do a fresh install. You can try without, but I have a feeling you are going to bootloop. It doesn't pass safteynet, but I can probably add the patch in for you. I'll take a look at it later tonight or tomorrow. Now that .270 CE1 is out I was going to move to that, but I can do the .235 one too if you want.
Click to expand...
Click to collapse
If it's not too much trouble, can you do the .235? I'm most likely not going to be updating to 270 any time soon. Willing to try it out without a fresh install.

This is Awesome! Thanks!
However, drmfix.zip is error 404. Can you post it?
Were you thinking to do one of these for .270?

gaijin1% said:
This is Awesome! Thanks!
However, drmfix.zip is error 404. Can you post it?
Were you thinking to do one of these for .270?
Click to expand...
Click to collapse
https://mega.nz/#!JhtF0bCJ!G0zOmqZYoNeFwSvLQnh5GAMh3_E--XQWAYjzrm4buC0
Yeah. I'll do one for .270, but it might be a week or so. I just got really busy.

Sepo190 said:
https://mega.nz/#!JhtF0bCJ!G0zOmqZYoNeFwSvLQnh5GAMh3_E--XQWAYjzrm4buC0
Yeah. I'll do one for .270, but it might be a week or so. I just got really busy.
Click to expand...
Click to collapse
That sounds great! I'm having trouble with .235, so I'll wait for the .270. MUCH appreciated

Watching gravure will be so much more satisfy ing, thanks

gaijin1% said:
That sounds great! I'm having trouble with .235, so I'll wait for the .270. MUCH appreciated
Click to expand...
Click to collapse
What issue are you having with the .235 one? I can't seem to get the drm fix to work on the .270 kernel as of right now, but I'll look more soon.

Sepo190 said:
What issue are you having with the .235 one? I can't seem to get the drm fix to work on the .270 kernel as of right now, but I'll look more soon.
Click to expand...
Click to collapse
I actually got it set up with 235, but for some reason I can't get it to root. Magisk installs fine, but nothing can get root permission. What version of Magisk did you use?

gaijin1% said:
I actually got it set up with 235, but for some reason I can't get it to root. Magisk installs fine, but nothing can get root permission. What version of Magisk did you use?
Click to expand...
Click to collapse
I used 16.7 and it worked fine for me. Did you try going in the magisk app and granting permission there?

Sepo190 said:
Yeah, sure. This is a .235 kernel that has been working surprisingly well for me. I used the ramdisk from shoey63's kernel repack here https://forum.xda-developers.com/xz-premium/development/kernel-repository-t3801795, so you need to flash that drmfix.zip too.
A couple of things I have run into though. The finish button wasn't showing up at the end of the setup wizard, so you have to go through that on the stock kernel and then flash this modified one. You might be able to fix it by changing the dpi, but I haven't tried that. You also cant set up any lock screen security until you flash the kernel or it will boot loop when flashed. So, the process that worked for me was:
1) flash stock .235
2) go through setup wizard NOT setting lock screen/fingerprint security
3) flash this kernel, drm fix and magisk
4) reboot
5) setup fingerprint/lockscreen security
You can change the screen dpi by using the wm density command or changing ro.sf.lcd_density in your build.prop.
https://mega.nz/#!o5FjxYwZ!zDS8DRaTnpER7e8YQOyyLjg_hY970geF9QaZajx5oO8
Does anyone know what changes the drmfix requires other than adding "export LD_PRELOAD drmfix.so:drm****.so" to the init.environ.rc in the ramdisk?
Click to expand...
Click to collapse
So if this actual 4k?? Like native 4k?? How's battery life/performance??

Sepo190 said:
What issue are you having with the .235 one? I can't seem to get the drm fix to work on the .270 kernel as of right now, but I'll look more soon.
Click to expand...
Click to collapse
I tried several things but couldn't get 235 to root for the life of me.
Now I really want the new ROM [O][8141/8142][.270] M-ROM: Xposed, Daydream compatible so I hope that a .270 based 4K kernel will work with it. Really want that Daydream in 4K. I wonder if your .235 kernel will work with it or if your .270 version will get the drm fix using the Kernel Patch from JanJan.

Sepo190 said:
I used 16.7 and it worked fine for me. Did you try going in the magisk app and granting permission there?
Click to expand...
Click to collapse
Hi man, sorry to interrupt your business, but are there any updates? Could you share with us how exactly you implement the 4k in the kernel? Maybe we could use the manual you're following, and do the work by ourselves.
I'm really curious. More and people are joining in

saved-j said:
Hi man, sorry to interrupt your business, but are there any updates? Could you share with us how exactly you implement the 4k in the kernel? Maybe we could use the manual you're following, and do the work by ourselves.
I'm really curious. More and people are joining in
Click to expand...
Click to collapse
Sorry I haven't given an update in a while. I haven't been on here in a while. I had an unexpected move, so my server wasn't hooked up and then I didn't have internet for a while. Just got it hooked up today actually. I have one with the drm fix working for the newest update using the ramdisk from JanJan's kernel. I can take another look at .270 probably this weekend if you want. I don't have a manual or anything, I'm just removing the 1080p configs from the dts file. I don't remember the file path off the top of my head and I'm not home right now.

It's not possible to enable 4k just édit build prop?
Envoyé de mon G8141 en utilisant Tapatalk

16.20 kernel
Here is a 4k 16.20 kernel that has been working for me for the past week if anyone wants it. I used the ramdisk from JanJan's kernel. Flash it and then everything in his drm-patching zip. The file I have been editing is dsi-panel-maple.dtsi btw, since someone asked earlier.
https://mega.nz/#!R5UhhKjA!U2kp2Zl4gYGddiSIkpJMaOlVYuAcakb514CwHq3jEH4