yashsingh1/xdaforums huggingface dataset:
[Galaxy Note5 General] PatelCartel:
This is my first time rooting too! And yes I used the root file for the build number which ended in PD4 (nobleltextc) while my phone was PG3. I used it because it had the same model number and the Android version as my Note. And I installed TWRP so I'm not sure how to check the Knox counter but a long time ago before I successfully got root I was trying to install TWRP and I believe it tripped the Knox counter. So if you're trying to preserve your warranty I don't recommend rooting or installing TWRP. I didn't have to worry about warranty so I did it. If you have any further questions just reply to this post. I'll he happy to help if I can!

---------- Post added at 03:36 PM ---------- Previous post was at 03:23 PM ----------

Hey Hairulnuzams! So to add TWRP without root you use the same tutorial that the original poster of this thread gave at the end of his first post after the rooting instructions. That method does not require root but you will have to download Odin separately since you won't be downloading the root file. A WORD OF CAUTION: DO NOT DO THIS IF YOU DON'T WANT TO TRIP YOUR KNOX COUNTER! AND THERE'S NO GUARANTEE THIS WILL WORK! I tried to do this after checking out many tutorials but it did not work for me. However after getting root it worked perfectly. So it's up to you to take the risk if you choose to.

Here's the XDA Developers page for getting TWRP: http://www.xda-developers.com/how-to-install-twrp/

and here's another non-XDA page for using Odin: http://androiding.how/how-to-install-twrp-recovery-using-odin/ ( I personally turned on OEM Unlock AND USB Debugging)
[Galaxy Note5 General] smeth_90:
jyeahhh...thx for this guild method bro..ur the man..i already root my samsung SM N9208 that i follow ur instruction and also download link..be sure all need to read carefully and use searching any forum to not wrong install that can brick phone. I also already brick my phone 1st time that try to root on lollipop..i upgrade to marchmallow and try to root and yeah done and already install TWRP and custom kernel SICKNESS...baterry almost very2 save use SICKNESS kernel.. +1 ur reputation bro..

sorry im from malaysia and this method work on me..

Buildnumber

N9208XXU2BPF1

Android Version

6.0.1
[Galaxy Note5 General] PatelCartel:
No problem! I'm glad to help!
[Galaxy Note5 General] smeth_90:
Btw thanks again bro..hurmm i need suggestion bro..seems after i root my device and done with custom recovery install also kernal install at my device..when i try to play my game KRITIKA name..the game detect illigel program hack detected?can u advice how to hide root or any command can edit?because i already done with super su,hide root,set to prompt and clear play store cache,reboot and play the game but not success..i not want loose root with success this method to safe battery life with MM android..thanks in advance..
[Galaxy Note5 General] PatelCartel:
I would love to help but unfortunately I'm not familiar with how to do that. However someone is bound to reply to your post and if not you should post this question in another forum on XDA more suited to this question. Meanwhile you can check out this web page: http://www.makeuseof.com/tag/trick-apps-android-rooted/ I haven't tried any of these methods so I'm not responsible if they don't work or damage your phone. I recommend you research more into these methods and be careful! I hope I helped!
[Galaxy Note5 General] smeth_90:
Wow thanks in advance..alright i will try to more research..[emoji3]
[Galaxy Note5 General] denclaud:
I cant root this always happens:

<ID:0/004> Added!!

<OSM> Enter CS for MD5..

<OSM> Check MD5.. Do not unplug the cable..

<OSM> Please wait..

<OSM> CF-Auto-Root-noblelte-nobleltextc-smn9208.tar.md5 is valid.

<OSM> Checking MD5 finished Sucessfully..

<OSM> Leave CS..

<ID:0/004> Odin engine v(ID:3.1005)..

<ID:0/004> File analysis..

<ID:0/004> SetupConnection..

<ID:0/004> Initialzation..

<ID:0/004> Get PIT for mapping..

<ID:0/004> Firmware update start..

<ID:0/004> SingleDownload.

<ID:0/004> recovery.img

<ID:0/004> NAND Write Start!!

<ID:0/004> cache.img

<ID:0/004> FAIL!

<ID:0/004>

<ID:0/004> Complete(Write) operation failed.

<OSM> All threads completed. (succeed 0 / failed 1)
[Galaxy Note5 General] smeth_90:
Flash new firmware bro..but wait what firmware ver you using?i also have this problem before..

---------- Post added at 02:32 AM ---------- Previous post was at 02:27 AM ----------

Which firmware you using MM or lolipop?dont download wrong root package..because this file CF autoroot is two file for MM and lolipop ver firmware..also read carefully OP(orginal post) thread..dont forget to enable OEM LOCK AND USB DEBUGGING..[emoji106]
[Galaxy Note5 General] denclaud:
Ohh I missed that OEM unlock.

I think its good right

<ID:0/004> Added!!

<OSM> Enter CS for MD5..

<OSM> Check MD5.. Do not unplug the cable..

<OSM> Please wait..

<OSM> CF-Auto-Root-noblelte-nobleltextc-smn9208.tar.md5 is valid.

<OSM> Checking MD5 finished Sucessfully..

<OSM> Leave CS..

<ID:0/004> Odin engine v(ID:3.1005)..

<ID:0/004> File analysis..

<ID:0/004> SetupConnection..

<ID:0/004> Initialzation..

<ID:0/004> Get PIT for mapping..

<ID:0/004> Firmware update start..

<ID:0/004> SingleDownload.

<ID:0/004> recovery.img

<ID:0/004> NAND Write Start!!

<ID:0/004> cache.img

<ID:0/004> RQT_CLOSE !!

<ID:0/004> RES OK !!

<ID:0/004> Removed!!

Currently rebooting. thanks a lot bro!
[Galaxy Note5 General] smeth_90:
Jyeah!!!huh..nice..good job bro..i just try to help if i can..that y i also have same problem with you before this time bro..heee
[Galaxy Note5 General] ryez88:
can i use this on my n9208 bpf3?

if yes which file i should get..tyvm
[Galaxy Note5 General] ryez88:
no prob..fixed myselft with other method root n use twrp here
[Galaxy Note5 General] kelok622:
Root

which method did you use to root ur n9208?
[Galaxy Note5 General] ryez88:
i just flash CF-Auto-Root-noblelte-…208.tar.md5 file from other chinese web..srry alrdy frgot the web name coz its chinese
[Galaxy Note5 General] smeth_90:
Kelok622..what u mean method to root SM N9208?what ver firmware u use?MM or lolipop?if MM..this thred is the right choice to root..download tar file here..see u model phone..and choose lolipop or MM of the CF auto root..

https://autoroot.chainfire.eu/

---------- Post added at 09:17 AM ---------- Previous post was at 09:10 AM ----------
[Galaxy Note5 General] rajnathr:
hi, I tried this method but iam not able to boot stuck up at the Samsung Galaxy note 5 screen,

Any help please
[Galaxy Note5 General] ryez88:
try flash this..https://mega.nz/#!sMlGyBbL!tukBsdNWBFq4HOXXWZPh4_3kKaqUGYxTe5Yam8dicII
[Galaxy Note5 General] rajnathr:
Thanks for the help, but the link says the file dosenot exist or has been removed,

I am getting a message kernal is not seaandroid enforceing

and is stuck at the galaxy note 5 screen

Please can you provide any link.
[Galaxy Note5 General] ryez88:
https://mega.nz/#!oIk0QYLY!tukBsdNWBFq4HOXXWZPh4_3kKaqUGYxTe5Yam8dicII try this..no need to extract..just download n flash..that file work for me after got same prob bfore..let me know how its work for u
[Galaxy Note5 General] PatelCartel:
Hi! I was trying to root also and I guess I was using a different root file than the one for my phone so I got a slightly different message saying "recovery not seandroid enforcing". I got scared but after some research I found that for the message I got, the solution was to download your phone's stock firmware off sammobile.com (BIG thanks to this site for having files with the latest build numbers) and flashing it with Odin. You should get the file off sammobile that has the same build number/PDA as yours. This method worked for me but your message is slightly different than mine so I'm not sure. A simple Google search for "kernel is not seandroid enforcing" should give you a plethora of solutions. Hope I helped. Any other questions let me know!!

---------- Post added at 02:05 AM ---------- Previous post was at 01:23 AM ----------

Any help is greatly appreciated. I have a Note 5 with a Build # ending in PG3 which I rooted a couple weeks ago with the PD4 root file and surprisingly it worked. I updated on September 7th with Smart Switch and it removed the root. Tried to re-root with the same file but the file disappeared and was replaced with another one on autoroot.chainfire.eu. Tried the new one but it soft-bricked my phone (probably because it was a different root file and my build number might have changed) . Had to flash stock firmware to un-brick it. So my question is, what chainfire root file can I use now thats compatible with my current build number ending in S3BPI3? If not chainfire what other method can I use to root my Note 5? Thank you so much for reading!!
[Galaxy Note5 General] Jefjefy88:
will this method work on my SM-N9208 Duos Taiwan Variant, PDA N9208ZTS3BPI2 (Latest MM update for my variant)
[Galaxy Note5 General] rajnathr:
Thanks for your Help, Did the same and got back the phone to boot and working.
[Galaxy Note5 General] Adriangbba6:
can you re-upload those file sir? Thanks :good:
[Galaxy Note5 General] tung_pvn:
Sure, yr phone boot n back to normal. Yesterday I try to root my N9208 TW BPJ1 but nothing happen, my phone has bootlop wz SS logo. Then I've to reflash thru Odin wz stock fw. And now I'm looking for a root to my phone. Any helps? Thks all
[Galaxy Note5 General] jamkirbs:
Cannot proceed to boot or to recovery :(

Hi. This is my story.

I want to root my note 5. I search from some steps. I got careless and proceed to the rooting part, without knowing some important notes when rooting. it didn't came to my mind that I need the build Number of my phone/OS.

I follow this guide, http://xdaforums.com/note5/general/guide-root-recovery-sm-n9208-t3382399 , downloaded from chainfire website the firmware, but due to my clumsiness, i didnt notice the build number. and after flashing the firmware it gave me a bootloop. Im stuck with the samsung logo. and a red text appear at the upper left, "RECOVER IS NOT SEANDROID ENFORCING" error. I also read that one solution is the wipe my phone's data. But unfortunately, i cannot enter recovery mode.

I dont know what to do, pls help me.
[Galaxy Note5 General] markzenenpanganiban:
Please reupload. Thanks.
[Galaxy Note5 General] wickedsatan:
Dear readers so i rooted by n9208 n also did skyhigh kernel... i dont know what or where i did something and now i dont get 4G/LTE anymore.. i tried to reset to factory but still no lte...

Kindly help if you can
[Galaxy Note5 General] hadisufi:
not working for build number MMB29K.N9208XXS3BQA6,

can someone help me ?
[HTC Startrek] BetaChris:
I tried flashing my 3125 to the latest official ROM via the nbh from RUU_STAR100_4.1.502.5_02.79.30_CWS_SHIP.exe in bootloader mode.

It gets as far as the "Update SD image?" screen, I press the button to start the update process, and I receive an "SD FAT Update failed !!!" error.

What am I doing wrong? Have I bricked my phone?

Any help would be MUCH appreciated...
[HTC Startrek] raskell:
Sounds like your SD card is not formatted with FAT32. Verify that it is, or just reformat it and make sure the file is correctly named, resides in the root directory and is the only thing on the card. Reply back on what you find.
[HTC Startrek] BetaChris:
I reformatted the card to Fat32, downloaded the RUU again, and extracted the nbh file it to the root directory of my microsd card, as STARIMG.nbh, and still got the same SD FAT update failed error.

(I did not use a volume label, and double checked that my card was in fact formatted in Fat32, which it was)
[HTC Startrek] nevermind:
Is your microSD card from Sandisk? My girlfriend was experienced the same problem (well, I was messing with her cellphone, don't tell her LOL), untill I tried my Kingston card. No idea what is the difference, both cards were with NO errors at all...

Try using few different microSD cards. And format them with the Panasonic SDFormatter only.
[HTC Startrek] BetaChris:
Thanks for the suggestion, but I'm almost certain it's a problem with my phone, and not the microsd card.

I tried using the same card to flash a different 3125, and was able to do so without incident - so, I've pretty much concluded that my other phone is shot.

(Oh, and for the record, it's not a sandisk card, it's an AData one)
[HTC Startrek] Erofich:
[remove this msg]
[One (M8) Q&A, Help & Troubleshooting] LitvinWright:
Bought an m8 last week. I've tried to download the OTA from settings-About phone but it says that my phone is up to date. I know some people are running marshmallow and I want to update. The phone isn't rooted. Can someone please help me?
[X Style (Pure) Q&A, Help & Troubleshooting] MHB1638:
Last night my crazy wife took my phone (we're divorcing) in an attmpt to piss me off, which of course it did. So I went to Google Android manager and locked/wiped phone. One it became useless to her she returned it. Now I can't access it because I don't know the lock code i used last night. I've tried all the videos for the bypass trick, but my phone wont allow me to click the build to enable the developers options. I've tried to "google keyboard help and share thing" that didn't work. Is there ANYTHING I can do? Google chat this mornign said its for security and sorry. I got made and said I bet your ass if any board member or the CEO had this, that phone would be unlocked instantly.
[X Style (Pure) Q&A, Help & Troubleshooting] lafester:
Flash stock image. How do you not know your own code?
[X Style (Pure) Q&A, Help & Troubleshooting] MHB1638:
it's not my gmail password or lockscreen password...its a password i created (drinking too lol) to lock my phone from the device manager. I don't recal lit perfectly, I'm close. But Google customer service states the phone is locked for 24-72 hours due to their strong security measures, which is fking stupid to not have a backdoor or recovery method. I told them this too...not right to lock a phone for this time period without any way to recover.
[Samsung Galaxy Star] Nikit:
u have 64 bit linux system ?
[Samsung Galaxy Star] Hicham03:
No, 32bit Linux system. 'Cause I tried to install Ubuntu x64, but always lags and crashed (2GB RAM only)
[Samsung Galaxy Star] Nikit:
install ubuntu 64 bit with 2GB swap partition
[Samsung Galaxy Star] Hicham03:
OK, thanks for your reply
[Xperia Z3 General] Me Gusta:
MOD EDIT by [MENTION=3843529]gregbradley[/MENTION]. I did not see the need for the expletive in the title, so i took it out for you.

So here's a little rant.

Read it if you'd like to, don't read if you don't like to.

Let's start with a little introduction. I've bought my Z3 about a year ago. I wanted to go with the z3+, but the Snapdragon 810 seemed to cause some issues. I still wanted the Sony batterylife after coming from a Galaxy S4 (which doesn't have the best battery life). I found online that Sony shares AOSP source code, so building a custom rom shouldn't be too hard.

Recently I have thought about unlocking my bootloader, but reading further into it, I found there to be NO upsides to unlocking your bootloader.

- There's a possibility of losing your DRM Keys when unlocking bootloader.

- You can not lock your bootloader again, so you're forever excluded from any OTA's.. Sony supports AOSP source code, you know.. to be developer friendly. But locking your bootloader again is not possible. This makes unlocking it very unappealing.. and very developer unfriendly.

- You cannot flash a recovery through fastboot, because Sony doesn't use conventional recoveries. Very developer friendly!

- Fine, Sony decides to release Android MM concept. Great, I was excited for this! But, the actual MM final firmware is nothing like the concept firmware and still a lot like the actual Sony themed firmware. (In my opinion this is disappointing, but that might be just me). When asked about why there are differences between the concept and the final firmware, the concept team replies that it has nothing to do with the final firmware. Then what's the point of a concept firmware??

Maybe I'm just nitpicking, but this seems very hypocritical from Sony..

C'mon Sony, your mobile department isn't doing too well, and this sure as hell doesn't make it better.

Now I know there are maybe only several thousand people actually wanting to run AOSP on their Sony, but I sure as hell am not buying another Sony phone until this policy changes.

Thanks.

Joost
[Xperia Z3 General] cazuniq:
Im still trying to figure out which part you unhappy about lol ?????

I have the Z3 rooted with Android 6.0.1 Slim1.6 Rom LB

And its the best ever with longest battery life ive experienced no issues fast and smooth

I dont want any other phone right now what more could you want?
[Xperia Z3 General] Me Gusta:
My issue?

On one hand Sony releases AOSP code, while on the other hand they make it a real damn pain in the ass to even run an AOSP rom. There have been several developers out there to try and build an AOSP rom. None of them managed to make a fully working one, because Sony made it so damn hard. I find this hypocritical and unjust.

What I want is for Sony to make it actually possible to run an AOSP rom, and stop pretenting like it's possible.
[Xperia Z3 General] savo83:
You can use TA Backup to restore your DRM keys as long as you back them up before unlocking the bootloader ('m just about to do it)

You can install a custom recovery via fastboot (I used TWRP to replace cyanogen recovery).

Not really sure your points to be honest.
[Xperia Z3 General] Me Gusta:
Sure, you can restore DRM.. but is it really convenient? My point is that Sony basically promotes AOSP roms by releasing source code, but on the other hand they make it impossible to enjoy a fully working AOSP rom because of DRM, camera's never working, etc..

Oh, and if you could explain to me how you flashed TWRP, and which file exactly, that'd be great :D . I've literally already spent 6 hours today trying to figure **** out after unlocking my bootloader..

Thanks in advance!
[Xperia Z3 General] Evokkimus:
I totally agree with you. Building an AOSP ROM for Z3 seems to be difficult (Tried cm too but extracting proprietary blobs did not work). The way how recovery works here is pretty stupid, seeing that we dont have a recovery on N for example, so I need to be on it without root (i dont blame developers here, but again, Sony's implementation). Also I haven't been able to work around the radio or camera thing in AOSP, even though I have only been able to build the ROM like once some weeks ago :D

---------- Post added at 06:00 AM ---------- Previous post was at 05:55 AM ----------

Also the recovery thing. Just download the .img from Nailyk's thread and put it in ADB folder. Then go to fastboot and type fastboot flash FOTAKernel . Then boot to recovery by pressing power and volume down button, releasing power when phone vibrates and volume when sony logo appears.
[Xperia Z3 General] doomed151:
That is true and disappointing. However, there is a way to backup the keys and restore whenever the need arises.

fastboot oem lock or restoring the DRM keys should relock the bootloader.

Sure it works, you just need to run 23.4.A.1.264 firmware or newer. I use fastboot flash recovery something.img all the time.

I think the Concept software is for those who don't need Sony enhancements (X-Reality, ClearAudio+, etc.) and want something that is close to stock.
[Xperia Z3 General] CedArctic:
So:

-You can backup and restore DRM functions even with an unlocked BL.

-You can relock BL again (haven't tried it myself but I think it's possible, if you check out DRM restoration guides I think they also show how to relock the BL)

-The new Sony BL allows fastbooting recoveries, the older ones support FOTA recoveries (I've used both with no problems)

-The MM concept project is still live, you can install it and continue using it, it gets updated regularly and is very close to AOSP.

-True Sony is kind of shady with their sources but you can build AOSP, there are AOSP builds for the Z3 here: http://fxpblog.co/ they get released whenever Sony releases new sources but you can also make builds yourself. The only true issue with sources comes out on certain AOSP functions and that we don't have (yet) fully working CM13 builds. As for the concept firmware it's exactly what you said, Sony is giving it out to people who are interested in having a close AOSP experience with support from the vendor while giving feedback to further improve it. Sony is making moves and is becoming more developer friendly by the month, other than new and constantly updated sources, proof of this is the Xperia Z3 is the only non-Nexus device that gets to run the Android N preview officially given from the vendor.

The Z3 is a great device, I personally haven't regreted the purchase, the only thing that bugs me is that neither I nor anyone else has managed to build a fully functional CM13 build (kudos to infected btw).

---------- Post added at 09:02 AM ---------- Previous post was at 08:58 AM ----------

As I said fxp has some builds, I haven't tested them but I think they work (http://fxpblog.co/)
[Xperia Z3 General] Evokkimus:
I was eager to try out FXP's aosp ROM, due to 3.10 kernel and such, but I got an error about updater-script in META-INF, didn't read further. I have my suspicions that it was a bad download, but their current site is so slow to download from (about 2 hours to download, and only a +20kb/s faster if you register), and i'm not going to pay for that site. If it helps any, i just wiped data, system and caches and tried flashing the ROM.

---------- Post added at 12:14 PM ---------- Previous post was at 11:56 AM ----------

I also tried building CM but stuck on proprietary blobs part. Couldn't pull them from the device for some reason, even though i was on CM rom at the time. (I did it because breakfast ended up in some vendor errors and Z3 didnt show up on the list either)
[Xperia Z3 General] nailyk:
Weird, I build CM12.1/CM13.0/twrp 3 with theMuppet repo without a glitch. Can you paste your compilation error in a pastebin or something like this? Maybe I can help you a little (I'm a compilation newbie) :o
[Xperia Z3 General] Evokkimus:
Basically the error I get is with extract-files.sh. When I run "./extract-files.sh" while phone is plugged in, I get permission denied. The other option for me is to run it with sudo, but then I get "line XX adb: command not found" (many lines of this error). Someone suggested chmod or opening a terminal window inside the folder where extract-files.sh is located. There shouldn't be any errors with my AndroidSDK path, even though some suggest the error is with this.

Also the reason I'm trying to pull these blobs, is because the CM tutorial told me so :D

[IMG="CM's advice"]https://i.imgur.com/cLb8duQ.png[/IMG]

https://wiki.cyanogenmod.org/w/Build_for_z3

------------------------------------------------------------

Also the reason I'm building CM is because I still don't know how to get radio working, even though a person has told how to get it working, I don't know how to exactly do it. But firstly I would like this CM thing to work. Thanks for your help.
[Xperia Z3 General] nailyk:
No worries.

So it may be a little more complicated.... If you just need a functional self build CM, try to include themuppet repo. If your device variant is not currently officially supported it can be more complicated.

I suggest you to open (or find) a dedicated thread and quote me, or join #cyanogenmod-dev@freenode.

Otherwise I'm following this thread because I found some point really interesting. I'm currently in trouble with Sony, that's why I subscribe.

Sorry for off-topic answers.
[Xperia Z3 General] arminbih:
sorry did not see the date
[Xperia Z3 General] nailyk:
;) Customer service troubles. They didn't respect law about unlocked bootloader into my country and refused to fix my device.