yashsingh1/xdaforums huggingface dataset:
[Note Edge Android Development] AlaskaLinuxUser:
PoochyX,

First and foremost, I do not accept any donations, I do this for fun!

As for the recents/headphones across all custom ROMs on this phone: we are using the great work of Mickey, Deadman, and OldDroid, who worked on this phone a year or two ago. I used their device trees as a base, and now am "pruning" these trees to be more functional. So for these initial builds, the problems that they had is problems that we have. However, it is my goal to work on and fix as many of these problems as I can, good Lord willing, and time allowing.

Currently I am working on the recent button.

Notice that the recent button does light when you press it? This screenshot shows that the kernel does know that the user pressed the button. So that is great news because the button does function, and is seen, just improperly mapped to a function.

While building, there is a file called sec_touchkey that specifically handles the two front touch buttons, so I have changed some of these values, and we shall see if that helps when I build again on Monday.

Hope that helps! :D
[Note Edge Android Development] Axelman8:
Hey dude

Whats wrong with Norma V6 /Aurora V3? Note7 all the way

But to the dev of this ROM.. good to have new roms to try.. thank you very much.

Do you recoment a specific kernel?

Regards

Axelman

Galaxy Note-Edge FY:

Mellowed, Xposed, Rooted and BlinkFeedtefied
[Note Edge Android Development] PoochyX:
Also on the pac man ROM if you try to make a 911 call the phone automatically reboots....
[Note Edge Android Development] PoochyX:
Alaska I stand corrected the fingerprint does work also in the unicorn build......Unlike the pacman build right on setup it works....

With unicorn straight from setup it doesn't register you have to go to finger print in settings and do it like 2 times for one print to register also the 911 issue is in this build also so I'm assuming it's a CM bug
[Note Edge Android Development] AlaskaLinuxUser:
I will look into it.

I don't think there are any other kernels that you can use at present, the modified stock kernels will likely not work, but you are welcome to try....

Really? Hope you didn't find that out the hard way.....
[Note Edge Android Development] PoochyX:
Alaska im okay......I was playing with my baby moms like she don't leave my crib I'm calling the cops and when I dialed it on her .....The phone rebooted so I reflashed your other bulid to see if it was a repetitive issue so I can report it to you
[Note Edge Android Development] AlaskaLinuxUser:
New build is up!

Praise God, a new build is up!

So, the OP has been updated with a new build. Not too many fixes yet, but you *should* be able to dirty flash this. I have tested the build, but as a clean flash, since I was jumping back and forth between other roms.

Change Log:

20161024:

-Built with Java 8.

-Added Kernel Adiutor and SELINUX plugin.

-Set kernel to SELINUX permissive by default. (You can use the SELINUX plugin to switch to enforce, if desired.)

Still working on the recent button. This change did not fix it, but hopefully we can get that resolved soon, as well as a few other things.

Also, adding some new Governors to the kernel as we speak!
[Note Edge Android Development] Aaren11:
Huzzah new Governors! Always a win in my book.

I've noticed an issue with no sound in-calls on my n915T region (Australia). I'm going to strip apart the radio fix over the next few days, and check to make sure it isn't a simple case of incrorrect / missing CSC codes.
[Note Edge Android Development] AlaskaLinuxUser:
While I have walked the Gold Coast, and had beets on my burger in Brisbane, I currently reside in a much colder place. However, my N915T has no issues with sound during calls.

Perhaps the N910G datafix file may help you? Or one of the other datazip files?
[Note Edge Android Development] AlaskaLinuxUser:
New build is up in the OP. Praise God! The Recents button is now working as a MENU button. See the OP for downloads.

Also, there are reports of occasional random reboots when playing intensive games and charging you phone at the same time. There may be other causes, please chime in if you can provide info on when it may happen. Logcats are always helpful. :D
[Note Edge Android Development] oscarmaldonado:
[MENTION=7026648]AlaskaLinuxUser[/MENTION], I just want to thank you for creating another masterpiece which is PACROM V2, everything is running pretty smooth, there was a big improvement with my battery, now it will last all day without a charge and everything else. Thanks again for expending a lot of your time, effort and for keeping our NOTE EDGE ALIVE( 915T ).
[Note Edge Android Development] AlaskaLinuxUser:
Hey all, I edited POST #3 with the following information about random reboot problems, if you experience this, then use these tricks to make them stop, or use the baseline kernel to ensure you don't have those problems ever again.

Random Reboot issues?

If you are having random reboot issues with the new kernel, you can adjust the settings as follows:

CPU max freq. 2496 MHz

GPU max freq. 500 MHz

CPU governor interactive

GPU governor msm-adreno-tz

I/O scheduler CFQ

That should solve your issue with the kernel. If you want, you may also flash this baseline kernel:

http://www.mediafire.com/file/h9b68aaon1yvr11/aokp_pac-mm-kernel-baseline.zip

This baseline kernel will always work just fine, however the battery life and performance are not as good as the AKLU kernel.
[Note Edge Android Development] AlaskaLinuxUser:
The OP has been updated!

For the group, I am planning to change the way the OP lists the release in the Downloads section of the post.

I have a released a build entitled "BASELINE". This BASELINE edition has the original kernel, with everything working as it stands. That way, any who want the modified kernel can grab it from the kernel thread, and not have to worry about it being built into the rom.

So, if you have any problems with the rom, give the BASELINE edition a try. It is really rock solid. The other releases will have other kernels and possibly other options in the future.
[Note Edge Android Development] miguelr4720:
WiFi Not Working Please Fix

Can you Tell Me Please How To Fix The WiFi Problem This Is So Annoying i unrooted and re-rooted the N915T

And Erase The System And Data and i install your rom

and WiFI is Still Not Working do you have any fix for this i have the N915TUVS2DPK2_N915TTMB2DPK2

Please Fix :crying::crying::crying::crying::crying::crying::crying::crying::crying:

I Really Like This Rom and its terrible without WiFI

and For Some Reason Stetting Keeps Crashing and Stops Working Please Fix :crying::crying::crying:
[Note Edge Android Development] AlaskaLinuxUser:
Miguel,

This is because you are using a 6.0.1 bootloader and modem. If you download the 5.1.1 stock ROM and flash it, then you can flash this ROM. Here is a link to the downloads:

https://samsung-firmware.org

Or, if you look in this forum mickey387 has mad a new nougat version of Red Remix, 5.8.0, that works with the 6.0.1 bootloader and modem that you have.

Here is a link to Mickey's ROM:

https://xdaforums.com/showpost.php?p=70401623&postcount=30

Hope that helps!

-AlaskaLinuxUser
[Note Edge Android Development] miguelr4720:
!!Alert PacMan Rom Setting Has Stopped Working

:confused: No i did not install nothing else all i did everything you told me to do i install the Data Fix For The T-Mobile and i Install and the

xposed-v87.1-sdk23-arm-custom-build-by-wanam-20161125.zip

That is the Only Thing i install extra did i use the wrong Xposed Module Please Leet me know.

The Issue With The Setting has Stoped Working Only Happens When i Restart the Phone. i send you a screen shot of the error for you could see it please leet me know how can i fix this everything else works fine. when i open setting i dont have any problem only when i restart the phone or am using it thats when the Setting Has Stoped Working Error Pop Up? so i dont understand neither and for some reason is showing Unknown for the Device Model is this because of a bug or its normal that the device model comes Unknown. :confused: Leet me know if i done anything in correct and if you found a fix for the setting has stoped working problem. because i am running the correct TW Recovery i install the one that you provided to me so the problem seems to be with the pacman rom the setting bug. i clean david cache and clear the cache on recovery still doing the same thing setting has stoped working. and setting still opens with no issue. :(
[Note Edge Android Development] AlaskaLinuxUser:
Hmmm... I don't know if that is the right xposed or not, I don't use xposed myself. Does that error happen if you don't have xposed?

As for the "unknown", look at post #3 of this thread, it shows how T-Mobile users can change that to read correctly.

If you like PAC, and want to use xposed, you may like AOKP, and want to try that instead. I don't have that error when I test it, so it may be the xposed module causing a conflict.
[Note Edge Android Development] darazor:
ALU

This custom wanam version of Xposed is the correct unofficial one.

Two things;

1. I would not install the xposed module until after I had tested the rom to see if everything works correctly

2. I would use the official version from rovo89 on this page http://dl-xda.xposed.info/framework/sdk23/arm/

Also, the xposed apk must be installed in order to use Xposed. https://xdaforums.com/showthread.php?t=3034811

Hope this helps. D
[Note Edge Android Development] miguelr4720:
Miguel Liked Your Post Think You Should Try to Focus On 7.1.1 Rom akop :)

MIGUELR4720

Liked Your Post :good:

I Think You Should Try And Take Your Time On 7.1.1 Rom For N915T Please :) :D

I Understand Your Work Has Been Extremely Hard but dont quit You Have Done and Excelent Job and I Am So Happy About This

I Review The Binary On The 7.1.1 Aokp Rom and Its Not So Hard To Fix The Minor Bugs that are Left. so dont quit please i will Promise you

a Good Donation For The Hard Work And I Love The New Project 7.1.1 Please Keep it up dont Quit i Know Fixing Bugs on a Rom It Can Take Several Hours To Fix so Please Keep Up The Good Work Congrats :) Thank You You Are The Best Person Man :):cool:
[Note Edge Android Development] AlaskaLinuxUser:
Thanks for the kind words, but I do not accept donations.
[Note Edge Android Development] miguelr4720:
No problem and sure keep up the hard work ill be patient for the new update aokp Rom 7.1.1 :) and when its ok and more stable to use thank you keep up the hard work ;)
[Google Pixel XL Questions & Answers] bigbabys:
This is probably a dumb question, but if I buy some USB-C -> USB cables, can I use my old Nexus 6 charging bricks and still get fast charge on my Pixel? I have a couple of them from my Nexus 6, and I'd hate for them to be useless now.
[Google Pixel XL Questions & Answers] yankeesfan714:
Don't take my word for gospel but the OEM Nexus 6 charging block has the same output voltage as the pixels block.
[Google Pixel XL Questions & Answers] mtran13:
I used the USB cable that came with the XL with my N6 charger last night. Seems to work just fine.
[Google Pixel XL Questions & Answers] Robert_W:
You absolutely can. Just make sure you have a Benson approved cable.

Also, it won't charge as fast as the OEM charger.

The N6 Charger Specs:

Nexus 6 battery is 3220mAh Turbo charger rates:

12v@1.2A=14.4W (Turbo 2)

9v@1.6A=14.4W (Turbo 1)

5v@1.6A =9W (Standard output)

You will only get standard output since the Type-C standard is 5v only. So you will charge at approximately 1.6A rather than the approximate 3A from the Pixel Charger
[Google Pixel XL Questions & Answers] old_fart:
Did you guys ( gals too . . . ) see the www.fixit.com tear down ?

.

wtf ! there were the qualcom qc 3.0 chips soldered onto the main board . . .
[Google Pixel XL Questions & Answers] droidiac13:
What do those do for us?
[Google Pixel XL Questions & Answers] 2real2141:
This may be helpful.

Below is a quote from a Google engineer from another forum.

"Will it be safe to use my nexus 6p USB-C charger with the pixel/XL?

I would advise against it. Please use the charger that comes in the Pixel box with it.?* The Nexus 6P charger will technically work with the cord it comes with, but if you use a USB-IF certified USB3.1 cord, the Nexus 6P charger behaves badly.

You do not want to risk a $800 phone on a $10 charger. If you use the OEM 18W Pixel charger, warranty will cover any problems you encounter.

Also, will it be safe to use any qualcomm Quickcharge charger?

Is the Qualcomm QuickCharge charger USB Type-A (square plug) or Type-C (round plug)?

Type-A (square plug) QC chargers: it depend on the manufacturer. Some make good chargers, others make bad. It depends on the maker.

Type-C (round plug) QC chargers: these are bad and go against the spec. I do not recommend using any Type-C Qualcomm QuickCharge chargers.

also, according to the processor spec, it does support quickcharge 3.0

No. The Pixel does not support QC at all. It uses USB-PD (PowerDelivery) at 5v@3a and 9v@2a levels. You need a USB-PD power supply with those levels or greater.

will there be any harm or advantage if i use a quick-charge 3.0 certified charger?

You need to speak to QualComm. I have personally tested "QualComm Certified" chargers that are bad. I have data to prove this. However there are many "good" QC3.0 chargers as well.

There will be no harm (if the charger is good). There is no advantage (if the charger is good). A QC Type-A charger will work like any other USB-A port and charge at 1.5A maximum. (It remains to be seen if the Pixel will recognize Apple 2.4A charging.)."

-Nathan K.

Link to said forum. Hopefully it's ok to paste here.

https://productforums.google.com/forum/m/#!topic/phone-by-google/jxhe1y4GRaU

https://plus.google.com/102612254593917101378/posts/1PJZT2g61Ag
[Google Pixel XL Questions & Answers] neyenlives:
My Nexus 6 Motorola Turbo Charger charges faster than my included Pixel charger...
[Google Pixel XL Questions & Answers] uploder:
Thats weird because it shouldn't
[Google Pixel XL Questions & Answers] neyenlives:
Yeah I'm just saying based on how long it is saying it will take to charge to full on the lockscreen, when the phone is at the same level.
[Google Pixel XL Questions & Answers] biggiestuff:
Anyone have experience with micro USB to USB c adapters? I'd rather use that and carry around just a few cables
[Google Pixel XL Questions & Answers] bigbabys:
Awesome, thanks for the reply! So from what I am understanding, the cable is more important than the charging brick? I charge my phone every night, and I want to avoid fast charging in that scenario since I've heard that Fast Charges create more wear and tear on the battery than a standard charge. That being the case I'd like to use an old standard charging brick (like a samsung one) and then use a certified USB - USB-C cable to charge the phone.
[Google Pixel XL Questions & Answers] yankeesfan714:
My Nexus 6 block and pixel USB cable does not say charging quickly. It just says charging.
[Google Pixel XL Questions & Answers] Robert_W:
Wait till the battery is lower, then try again

Google Pixel XL Stop Motion Unboxing Video
​
[Google Pixel XL Questions & Answers] p4ck3ts3nd3r:
Sometimes those estimations vary quite a bit. Reinserting the plug resets this, and can sometimes change the estimation by a few hours.
[Security Discussion] kennonk:
Just wondering if the new Dirty Cow exploit means all those previously unrootable phones can now (or very soon) be rooted.

http://www.cyberciti.biz/faq/dirtyc...local-privilege-escalation-vulnerability-fix/
[Security Discussion] SimLynks:
Based upon the early research into this, YES it would appear that this also has widespread affect into the Android Linux Kernel

https://www.nowsecure.com/blog/2016/10/21/dirty-cow-vulnerability-mobile-impact/

https://www.theguardian.com/technol...ow-linux-vulnerability-found-after-nine-years

(Bottom of Article Google confirms Android is susceptible)

PoC Code which would probably need to be slightly refactored for use in Android, but still highly relevant

https://github.com/dirtycow/dirtycow.github.io/wiki/PoCs
[Security Discussion] Scorpius666:
The bug affects the Android Linux kernel. I already tested it, and yes, you can change any file owned by root to whatever you want.

But that doesn't mean you can actually root the phone (that is, gain root access). Maybe it is possible, but I don't think is trivial. The thing is: you can modify root owned files, yes. But you need that some process owned by root executes your file, so you can gain root access. Editing init scripts won't work since they are recreated every time you boot your phone, and after the phone boots, as far as I know, nothing else is executed by root.

I don't mean that it can't be done, maybe there's some file that is executed by root after boot out there that you can modify, but I wouldn't know which one.
[Security Discussion] KillahKiwi:
Doesn't that mean you can install a custom su binary and just execute that as any user? :confused:
[Security Discussion] a___:
This exploit only allows you to replace the content of existing files with their existing mode/permissions, and the way su operates you need the setuid (set-user-ID) bit set in the mode, and from a brief look at the system I wanted to get root on, android doesn't seem to have any setuid binaries.

I'm thinking replacing something like wpa_supplicant could let us execute the payload as root, just disable and re-enable wifi, but I can't seem to get the exploit itself to work at the moment.

On further inspection (at least on this device), wpa_supplicant isn't readable by non-root (which I think the exploit requires). app_process is, but that's an executable I'd prefer not to mess with

Update:

Got the exploit itself working.

Tried replacing /system/bin/fsck_msdos's content to trigger it to be run as root by inserting a microSD card,

but something on this device (Amazon Fire 5th gen) keeps rebooting and restoring the system partition if any file is changed.
[Security Discussion] DP FH:
Not true. This code executes su as root, spawning a root shell. It can be modified to run a script that installs su in/system etc..

The counterside is that the kernel crashes/freezes after some seconds.

https://gist.github.com/scumjr/17d91f20f73157c722ba2aea702985d2

I'd like to port that to an apk using the ndk, but my pc is too old.
[Security Discussion] julianwi:
The /system partition is mounted read only by default. Because of this, you can't overwrite them. But I saw a exploit which used /sys/kernel/uevent_helper to execute a shell script as root. This would probably also work with the dirty cow exploit.
[Security Discussion] Scorpius666:
You can't create a new file. You can modify an existing file. The su binary needs the setuid bit and there are no files in the Android filesystem with that bit set.

The only way to root a phone with this bug is to modify an executable that will change the owner of the su binary to root and set the setuid bit on this file. This part is trivial and very easy.

The difficult part is to find a binary that will be executed as root after you have booted. If somebody knows any file in /system/bin for example that will be executed as root doing some action on the phone tell me and the phone will be rooted in seconds.

---------- Post added at 11:32 AM ---------- Previous post was at 11:28 AM ----------

I copied the su binary in /data/local/tmp. I can modify files in /system/bin for example and the phone does not reboot, but i don't have fsck_msdos in my phone.

---------- Post added at 11:35 AM ---------- Previous post was at 11:32 AM ----------

I'm compiling on the phone using UXTerm, then apt install clang, and then using gcc. It's the quickest way to compile a single .c file on it.
[Security Discussion] DP FH:
I'd like to create a standard Android app that uses jni to run exploit and then roots the device. I can't test on my real phone because I need warranty and Knox counter to 0.
[Security Discussion] Scorpius666:
At first try doesn't work for me:

shell@victara:/data/local/tmp $ ./dirtyc0w-mem b6dc0000 b6dc1000

[*] range: b6dc0000-b6dc1000]

[*] getuid = b6f79b18

[*] mmap 0xb6dd5000

[*] exploiting (patch)
./dirtyc0w-mem: failed to execute "su": Permission denied

[*] exploiting (unpatch)

[*] unpatched: uid=2000 (madviseThread)

[*] unpatched: uid=2000 (procselfmemThread)

But I'll modify a little bit to see if I can get it to work.
[Security Discussion] DP FH:
I don't think you have su on the phone ????

By the way I'm trying to install some emulator on my pc so I can try
[Security Discussion] Scorpius666:
I do have the su, in /data/local/tmp, with users permission. The idea is to do a chown root:root and a chmod 4755.

But I know what the problem is. The SHELLCODE in the file is for x86, which seems to be a XOR AX, AX and a RET. I have to do the same for an ARM v7L in THUMB I think...
[Security Discussion] a___:
Well that assumes we have a setuid su already, this variant of the exploit won't help us.

Somehow it did manage to overwrite it, but maybe the reboot and reset are caused by it being read-only and not actually writing the changes to persistent storage.

Will look into /sys/kernel/uevent_helper though, thanks

Just about any would work, you probably have some other fsck or mkfs utility you could do it with, then trying to format an SD card should run mkfs
[Security Discussion] Scorpius666:
The thing is all my fsck* files are not readable, only by root, at least in my device. The exploit needs a readable file.
[Security Discussion] DP FH:
Nope. The su command is executed as root, and when you execute su as root it gives you a root shell. Try to execute sh instead of su.
[Security Discussion] a___:
No, it merely makes libc report that the user is root even though it isn't, it needs su to already have setuid to switch to the real root, and then running the shell. In this case (simplified) the exploit just bypasses the password prompt.
[Security Discussion] Scorpius666:
I just noticed that. Using sh instead of su, the dirtycow-mem works in the phone and it spawns a shell, but with the same privileges than the user that executed it. So it's useless at least with that libc approach.
[Security Discussion] DP FH:
Strange, on normal x86 works like a charm so something needs to be fixed
[Security Discussion] Scorpius666:
Of course it works on x86. If you read the code you'll see that it changes the function getuid() of libc (that is already loaded in memory) to return 0. The x86 su binary uses getuid() to know if it should ask for a password or not. Since getuid() is patched, it doesn't ask a password and spawn a root shell.

So basically for dirtycow-mem to work you need:

A su binary with setuid root

That su binary should ask for a password

The Android su binary doesn't ask for a password and doesn't have the setuid root so this exploit won't work.
[Security Discussion] ajusacav:
hey there

did anyone try the dirtycow-vdso exploit? it works on SELinux (which AOSP uses) and doesn't require a SUID see

github . com/scumjr/dirtycow-vdso
[Security Discussion] Geofferey:
Thanks I've been monitoring that thread but there is TOO much going on in there. I was playing with Android.mk and familiarizing myself a bit so I'll try that tomorrow when I wake up.

Theres still a lot of work to be done and there will probably be differences in devices that wont allow it to be %100 universal. If you're lucky and have a device that people care about its likely you'll see a solution.
[Security Discussion] christianrodher:
that means you have to wait till kingxteam implement universal dirtycow root into kingroot one click apk.

or for that github group to test and test till a proper method is found and binaries are compiled for all systems.
[Security Discussion] christianrodher:
the correct libs are provided by him aswell https://github.com/jcadduono/android_external_libbootimg

im trying to compile them