yashsingh1/xdaforums huggingface dataset:
[Huawei P9 Questions & Answers] Fybere:
First of all, get your bootloader unlock code. To get it google how to get it (I cant post link as I don't have enough posts to have privileges). If you can't on the English, make a new account on the chinese emui page and use google translate in chrome to navigate. (if the padlock button doesnt give you a form to fill out, clear your cache and cookies or open in incognito mode)

Once you have the code, find the "SRK Tool Huawei Bootloader/ROOT/Recovery/Backup/Utility" thread on XDA and download the latest stable build, should be around 700mb. Also in the thread, the guy posted a video on how to do it.

Step 1: Unlock bootloader

Step 2: install TWRP Recovery

Step 3: Root

These 3 steps are in the video.

Once you successfully rooted, open the tool again and in the Utilities menu (7) there is an option to flash OEMInfo. Select that and choose the OEM info you want. I needed C432. It will use the superuser app to flash it, reboot and you should be on it.

If you are asking how to use DC-Phoenix, again they have both written as well as a video with instructions on how to do it. You don't need an unlocked bootloader as it will use an exploit to circumvent it. Do Method 1, if it doesn't work, do Method 2.

Good luck mate

I got into this mess in the first place by flashing the B361 and my camera and keyboard didnt work after upgrading it. But now that i know how to fix it, I might give it a shot. Is there a thread with features and testing of the Nougat emui 5 for P9? I saw a lot of threads of people rolling back due to battery issues and other stuff. Don't want to update if its not the best.
[Huawei P9 Questions & Answers] mjcaballero:
Thanks

Thanks a lot for help, my phone is alive again, i use DC Phoenix to resurrect, and SRK for the update :D
[Huawei P9 Questions & Answers] mrabody911:
i have problem to

..

---------- Post added at 12:33 PM ---------- Previous post was at 12:27 PM ----------

please i try to install twrp but not work

---------- Post added at 12:38 PM ---------- Previous post was at 12:33 PM ----------

what you chose i dont know i buy buy the DC PH..
[Huawei P9 Questions & Answers] mrabody911:
HOW

---------- Post added at 02:38 PM ---------- Previous post was at 02:33 PM ----------

PLEASE

---------- Post added at 02:40 PM ---------- Previous post was at 02:38 PM ----------

i install tswp last but not work

---------- Post added at 02:44 PM ---------- Previous post was at 02:40 PM ----------

ppppplease

---------- Post added at 02:45 PM ---------- Previous post was at 02:44 PM ----------

oooooooo
[OnePlus 3T Questions & Answers] appro77:
Anyone finding that a build.prop edit causes the camera to crash? I've added this line:

ro.config.media_vol_steps=30

to my build.prop to get more media volume steps as suggested here:

https://www.xda-developers.com/how-to-add-more-steps-to-your-volume-slider-root/

but it causes the camera to crash immediately after taking a photo.

I then have to dirty flash 4.0.3 to fix the problem. I've tried it 3 times. As soon as I add the build.prop edit it borks the camera. Removing the edit from build.prop doesn't fix the issue. I have to dirty flash. It's as if build.prop is corrupted and only a dirty flash of the stock rom fixes it.
[OnePlus 3T Questions & Answers] knijntjes:
I'm having the exact same problem, i've also editted my build.prop and now my camera is crashing.

I found that when hdr is turned on, the camera doens't crash.

I'm curious what this has to do with the build.prop...

EDIT: turning on HQ mode doens't make the camera app crash, but gives me 'green' photo's.
[OnePlus 3T Questions & Answers] knijntjes:
I've found the solution!

The problem is the permissions. After you've editted your build.prop you have to set the following permissions:

Owner - read, write, execute

Group - read

Other - read

(Can be done in for example Es File Explorer, select build.prop, click the 3 dots and click properties, you can then change the permissions.)

I now have a editted build.prop with working camera!:)
[OnePlus 3T Questions & Answers] Intreeg:
Thanks

Had the same problem running stock ROM Moto G5 Plus after adding a tethering enable line to my build prop. Rooted via magisk v16 bty. Your fixed worked for me. You're a life savior. ?
[Verizon Samsung Galaxy Note5] Alonso2019.2019:
Mod Edit
[Verizon Samsung Galaxy Note5] TheHunterOfShadows:
So this is BS right? I've been out of the phone rooting game for a bit.
[Verizon Samsung Galaxy Note5] MrMike2182:
Mod Edit
[Verizon Samsung Galaxy Note5] HypostaticOnion:
Lol at the if you see SuperSU you're rooted. I mean, if the CF auto works cool, but I'm gonna wait to see how many people don't read first and try to flash this.
[Verizon Samsung Galaxy Note5] MrMike2182:
LOL there isn't even a CF auto root for the N920V!! He seriously just took the same one we already have for console root and renamed it! They're even the same exact size, haha. Besides, where does he think the SuperSU app is coming from? It sure ain't from the file he has posted because that's just the console root kernel and that doesn't install/ flash SuperSU it only flashes the boot.img..
[Verizon Samsung Galaxy Note5] MrMike2182:
There's to many inexperienced people claiming root and cluttering the hell out the forums!! Even on the easy-firmware website he posted this same exact thing and when a user asked him a question he didn't even know the answer and told the user to flash and report back with his findings.. This thread is totally not needed at all!!
[Verizon Samsung Galaxy Note5] Websyn:
Stuck in the boot interface
[Verizon Samsung Galaxy Note5] MrMike2182:
Well there goes 1 who didn't read first lol.
[Verizon Samsung Galaxy Note5] thaifani:
please remove this threade Please .

it's worng from inexperienced someone
[Verizon Samsung Galaxy Note5] droidvoider:
I know this website, easy firm ware listed above, to be a scam site. I've seen a lot of different angles they've tried INCLUDING a download manager quote unquote that is supposed to help you finish downloading. But this is a trojan app. While I never fired it up I can tell you it doesn't look like something a windows user should execute on their system. I use linux.

(mods I promise I know this site is a scam site I've watched them work over the past couple months as I researched my studies)

Regards to root. If you are patched for dirtycow good luck getting root on this phone. (see below for dirtycow patch details) The AT&T / Verizon variants of the Note 5 are extremely well coded you can't get root on them without a powerful exploit. With dirtycow available the days are numbered for any phones not patched, of course not patching your phone in the meantime means you are very vulnerable to a nasty exploit.

So how long right? I dunno but it could be awhile.

Patch details:

Google says the fix is called CVE-2016-5195 patched 11-05-2016, however my security patch level is Nov 1st, 2016. The Samsung SVE-2016-7504 is stated to be included in November's patches and there are 14 patches in that set. AT&T N920AUCS4CPK1 has a note about 14 patches from Samsung, the exact number. (so I seem to be patched if I follow the logic even though Google responded on 11/05/2016 but I dunno how to confirm what's in this Nov 1 2016 security patch in the PK1 firmware.)
[Verizon Samsung Galaxy Note5] Turbine1991:
It doesn't really matter if they've patched it, you can still downgrade your firmware and security level - even on this variant. I used to go between Marshmallow and Lollipop, as it was required by the ps3 controller app.
[Verizon Samsung Galaxy Note5] MrMike2182:
Which part are you saying you can downgrade? You can't take the Lollipop firmware and flash it if you're currently on the latest firmware update. It will just fall in odin.
[Verizon Samsung Galaxy Note5] Turbine1991:
That's just not true. The Verizon model can be flashed in Odin, I've done it a few times myself. Here's someone elses word: https://xdaforums.com/verizon-galaxy-note5/general/downgrade-to-lollipop-5-1-1-verizon-t3368250

It's not impossible, you just need to use an official firmware and may need to downgrade the bootloader.
[Verizon Samsung Galaxy Note5] MrMike2182:
Uh, Sir, the link you just posted.. *I* am the original poster of that and I'm telling you with official firmware you still CANNOT go from the latest firmware update of Marshmallow back to Lollipop! I even stated in my OP that it's not going to once you accept the BPI3 firmware update you're done and stuck on Marshmallow with no way to go back not even if you follow my original instructions it won't work!! The bootloader is no longer downgradeable thanks to Verizon!
[Verizon Samsung Galaxy Note5] Turbine1991:
Dirty cow or not is irrelevant. We can upgrade or downgrade and we're able to root this phone just like any other variant.

The only issue is the bootloader's signature checking.
[Verizon Samsung Galaxy Note5] invaluable:
so this is crap, thanks for the further investigation
[Verizon Samsung Galaxy Note5] droidvoider:
There's a simply check for a value that they are calling a binary number. What is that? Certain versions will work together but past a certain point something changes. (most often the security storage binaries) .. So the bootloader checks to see if binary # >= current firmware binaries ... If you are on S3 binary and you attempt to flash S2 binaries the bootloader newly rejects this.

I can and have written a tool to over come this problem but there is one catch. system.img is too large for me to hack into place in this way. If I can't rewrite system.img then we are still stuck. ;*(

So what am I doing? I need root so I can just dd write system.img from /sdcard/ to the partition. that's it..

Stop listening to people who are not spending all their free time looking at the Note 5.. I already have too much access for the Note 5 to survive now.. It's going down, it is not the super secure device that will refuse to boot 'ever again' if you modify stuff that Samsung tried to claim.. that was lies and nonsense (don't hack BOTA0 or BOTA1 though)... I haven't tested changes to this partitions, all others have suffered a beating from me. (if you disable certain packages without disabling other packages it will refuse to boot, no wiping will help, reflash time)
[Verizon Samsung Galaxy Note5] MrMike2182:
I tried to tell everyone that this was straight up BS back when I was asking for help and no one wanted to risk it nor did they believe me.. Instead they chose to believe this instead of me..

http://www.idigitaltimes.com/samsung-galaxy-note-5-galaxy-s6-edge-specs-and-features-att-and-verizon-models-wont-468357
[Verizon Samsung Galaxy Note5] droidzer1:
Would flashing the tar file in the OP give me the ability with ADB to delete, rename or change the bootsamsung.qmg and bootsamsungloop.qmg files? All I want to do is swap those out for another set. Would I then need to flash something else to bring it back to normal?
[Verizon Samsung Galaxy Note5] ashyx:
You seem to have a good grasp on the situation and seem to talk sense, so I'll just ask a question. I'm only passing through because I needed some info, but got interested in the thread.

It seems you have the eng boot for the device, but not able to get system to mount rw? Strange because I have checked it and it is a bonafide eng boot.

Anyway I don't own this device, but I thought I'd just share some info that allowed others to get root on a few recent ATT devices with locked bootloaders on MM.

Using Kingroot on the said devices would not work, no matter how many times or which version was used. However flashing the eng boot from the combination firmware (so not even full eng boot as no root shell with adb) and then using Kingroot, Kingroot was able to successfully root these devices even though with some it took several tries. Kingroot was then used to convert to Supersu.

This may have been tried already, but I couldn't see it. Someone tried it with stock, but not using the eng binary.

The combination eng binary allows the device to boot in permissive mode with no dm-verity, but doesn't have a root shell or any write access with adb. The full eng boot you have should do the same obviously with the addition of adb root shell.

It's just for info and I'm not claiming it will work on Verizon devices, but it seems to be pretty successful on ATT and Tracfone devices.
[Verizon Samsung Galaxy Note5] MrMike2182:
Which combination firmware are you referring to? I don't necessarily want to purchase more combination files or eng root files because to many of these places selling them are just ripping everyone off by claiming they have a file you need and then you buy it and realize it's totally not what it was supposed to be.. I managed to get the S6 Edge and the S6 Edge Plus root on the Verizon models. So far the Note 5 is eluding me.
[Verizon Samsung Galaxy Note5] ashyx:
I'm not referring to any particular combination firmware, the eng boot you have should be enough. Just ensure the device is in permissive mode before using Kingroot.
[Verizon Samsung Galaxy Note5] MrMike2182:
Unfortunately the eng root I have is not enough apparently because it doesn't set permissive upon boot but I can set it to permissive but that doesn't help since it's needed during boot up and not after.. I haven't found any eng root kernel that's set to insecure boot.. Have you?
[Verizon Samsung Galaxy Note5] ashyx:
Yes I was aware that was the case, however my point was that Kingroot has a greater success if the device is running in permissive mode first.

Not sure it matters if it's set during or after booting as long as it's before Kingroot is run.

Also just to note, the eng boot from combination firmware boots as permissive on all the ones I have come across.
[Verizon Samsung Galaxy Note5] MrMike2182:
Yeah I got kingroot to work no problem there... The problem was that if you had to reboot the phone for any reason it would all be undone and returned back to stock after the reboot and you would no longer have root and I would have to redo the kingroot and all the bloatware I wanted gone was right back on there and I know it's because of the kernel not being set as write permissive.
[Verizon Samsung Galaxy Note5] ashyx:
So you're saying you can actually get root with Kingroot on this device?

That's common for it to be temporary, but that's all you need.

The next step is to convert to Supersu system root to have permanent root. Either use Super-SUME or the Kingroot to Supersu removal script.

I have a guide how to do it with the script, but the Super-SUME route is simpler.
[Verizon Samsung Galaxy Note5] MrMike2182:
I have a script for that and after I did it, it refused to boot past the Verizon boot screen and upon going into recovery I got a verity failure which is why it refused to boot and everything I tried to do would fail the only way to fix it was a full system flash and then it worked again.. I'm rather annoyed with the constant factory resetting or starting over again and again!!
[Verizon Samsung Galaxy Note5] ashyx:
If that's the case then it seems the eng boot you have is not disabling system integrity checks IE. Dm-verity, which is surprising.

Things required for system root to be successful:

A patched sepolicy or a permissive kernel at boot. Patched sepolicy is out of the question on a bootloader locked devices, so it has to be a permissive kernel.

Dm-verity disabled.

All of the combination firmware binaries I have come across are permissive at boot and disable dm-verity, this is how we achieve full system root on bootloader locked devices.

So I suggest a procedure:

1. Gain root with Kingroot

2. Convert to Supersu

3. Install the eng boot binary from the combination firmware.

Unfortunately I can only source the combination binary for 5.1, but not 6.0.1. Without downgrading I'm unsure if the kernel would boot on MM, likely not?

On another note regarding having to start over if something fails. Once you have root with Supersu you can either use Flashfire to backup the /data partition or Titanium backup to backup all apps and settings.

If your device fails to boot, simply flash stock, re-root and restore your backup.

However all that should be necessary is to flash stock, not factory reset.

Only the system partition is compromised with system root, dm-verity doesn't care about the data partition, so there shouldn't be any need to factory reset.
[Verizon Samsung Galaxy Note5] MrMike2182:
The eng boot for 5.1 won't be able to boot on MM tried that before and since I cannot go backwards to downgrade to 5.1 I'm at a loss really.. When I had the dm-verity error I flashed the system image alone but it still didn't boot up.. I think it might be my fault though because my script replaces recovery.sh and that's a no no with the locked bootloader.. I suppose I will try something else later.
[Verizon Samsung Galaxy Note5] Maleko48:
Just finished catching up on this thread. Had a few questions.

1.) Has anyone tried searching Chinese, Russian, Korean, etc websites / forums / fan bases of android and using Google Translate to convert to rough english translations enough so that we might come up with something useful?

2.) What special or hard-to-find files you are hunting for exactly?

3.) Would it be possible to find whatever 5.1.1 information you need from an old phone dump or something posted to the web previously?
[Verizon Samsung Galaxy Note5] hunsinger89:
There is a bounty thread JUST for this model. If someone can actually create a post in the following thread, detailing exactly how they did it, and wait for someone to confirm it using their method, then you can claim a nice chunk of change https://xdaforums.com/note5/general/bounty-verizon-samsung-galaxy-note5-sm-t3191974
[Verizon Samsung Galaxy Note5] faaaaq:
That thread means nothing today as far as incentive. The "pledges" are almost all from a year and a half ago, they are non-binding, most pledgers likely dont even own a Note 5 anymore, and even if someone tried to claim the pledges after gaining full root, per the terms of the OP the person claiming the pledges has to take it upon themselves to PM every single person that pledged money, one by one, asking for them to send the money they pledged...which at best means each person that pledged money then has to go back to the original thread, find the proof of root, probably try it themselves to verify, then eventually get around to sending the money...and at worst, they will ignore the person PM'ing them for money that was pledged a year and a half earlier. Every possibility between those two cases are negative ones in which the person that was the first to gain root ends up with little to no money.
[Verizon Samsung Galaxy Note5] ramiss:
The reason for a developer to achieve root is not for bounty money. It's for notoriety and bragging rights, like it has been for hackers since the beginning. Bounty threads are only useful to get devs to bump something up as priority, which obviously didn't work in this case, so the bounty is useless for that reason alone.

If it is ever possible to root the Verizon Note 5 and someone does achieve it, many would be very impressed, and quite a few of us went back to it after the Note 7 C4 variety.
[Verizon Samsung Galaxy Note5] GalaxyFan5:
Please Root

I would love to see an exploit for this model. PLEASE.
[Verizon Samsung Galaxy Note5] ashyx:
Temp root with kingroot is possible on MM then you'll have to convert to supersu. See this thread.
[Verizon Samsung Galaxy Note5] GalaxyFan5:
Temp root?

I searched for Temp root. I didn't get much if you mean counsel root I think I have tried King root while being counsel rooted.

I know that my phone keeps warning me that unauthorised activity has been detected and the phone needs restart. I haven't followed that warning but have restarted for other reasons and the warning staysdisplayed.
[Verizon Samsung Galaxy Note5] ashyx:
It's literally in this thread. :eek:

What's counsel root? :confused:
[Verizon Samsung Galaxy Note5] Medo00o:
Wrong root

hello, it seems like you understand what's going on lol

I've done this root by using Odin and the mensioned file above but unfortunately failed on my note 5 and now the phone loses the wifi passwords when i restart it. and i guess it will lose the mobile data configuration as well but so far it doesn't have sim card. I need t fix it before using a sim card :(

Thanks
[Verizon Samsung Galaxy Note5] MrMike2182:
The reason you're losing the Wi-Fi password is because it did work. It flashed the ENG kernel and the phone can not keep the passwords with that kernel.. To see that you have the ENG kernel go to settings and then about phone and look for the kernel version.. You just need to change the kernel back to your stock kernel.. The one you were using before you flashed this one and everything will work again.
[Verizon Samsung Galaxy Note5] droidzer1:
See my post #159 here: https://xdaforums.com/verizon-galaxy-note5/general/root-n920v-t3538192/page30#post80732207

Root I have :cool: :D on my SM-920V - might not be quite what you think but check out my post in the link above.
[Verizon Samsung Galaxy Note5] gigahurts:
Hey there,

I'm on 6.0.1, I'm using mobilego, I get temp root, but not permanent. Would like some help making it permanent. I can use temp root for AA Stream, for android auto and it works. That was the goal, but I can't reboot, or else I loose root.

any ideas?
[Verizon Samsung Galaxy Note5] ashyx:
If you have temp root you can use the methods posted previously by me in this thread. However this will only really work on lollipop as you need the eng boot image from the combo firmware to be able to boot with supersu.

What is your current firmware build?
[Verizon Samsung Galaxy Note5] gigahurts:
Hi there,

I'm on VVRS3BPI1. So no going back to 5.1 I've flashed the eng 5.1 boot IMG via Odin, won't boot, get Verizon warning about software has malfunctioned or something like that. Root works with mobilego, but I can't use flashfire to flash safestrap because the app won't completely load, it crashes right before displaying the menu. My phone reboots anytime the system is mounted by any app with root. So I can't get a permanent root and I can't go back to 5.1

Oh well. Thanks for the response.
[Verizon Samsung Galaxy Note5] ashyx:
Not necessarily. While the bootloader cannot be downgraded it doesn't mean system can't be. Often higher revision bootloaders are backwards compatible with earlier kernels and system images.

If you can flash just the AP part of the lollipop firmware then it may boot.
[Verizon Samsung Galaxy Note5] bladez:
Is there any way to get even just a temp root for 7.0? Or only if I go back to older versions of Android?
[Verizon Samsung Galaxy Note5] gigahurts:
Hey bladez,

Ive tried everything to get 7.0 rooted, couldn't get it to work, so u downgraded to 6.0.1, works with mobilego, but it's very temporary, can work for hours, or 5 min. I just wanted aastream to work for Android auto, which it does, even in new mode. If I loose root aastream still works, I just loose touch functionality. I haven't tried a 7.0.1 so, keeping the 6.0.1 bootloader, if it works I'll let you know.
[Verizon Samsung Galaxy Note5] droidzer1:
'mobilego' by Wondershare ? I don't trust Wondershare products much but where in the App can you root a phone. I don't see any function to root a phone in the apk.

OK - I see it is their PC version that claims to root. It installs all sorts of garbage and it still doesn't seem to be able to gain root. Rebooted my phone enough times that I wondered if it was bootlooped. Did the process take a long time? Looking at at least 10 reboots so far. Looks like it finally gave up. Another not so wonderful Wondershare program IMO. At least I installed in with Shadow Defender so a quick reboot of the PC eliminates all the garbage it installed.