Database Users

New to Flashing, Want to install Eclipse [Note 3]

Hello everyone.
Is there a one true guide to installing a ROM on my Note 3? I'm running a T-Mobile N-900T. It seems that after browsing the web, I've seen so many different ways to install a ROM that I'm extremely hesitant to try one on the off-chance that it is no longer supported and may brick my device. This is a non-warrantied phone (bought it on Swappa) so I only get once chance if I end up Hard Bricking it, so my fear level is at the absolute highest.
I wanted to run Eclipse Note 3 TW Rom (found here: http://forum.xda-developers.com/showthread.php?t=2620723) because it's a nice simple ROM that retains S-Pen function and removes all the bloat and stuff. However, I noticed that it says "This is based off of 4.4.2 NC2 for Verizon Wireless." Does this mean it won't work with a T-Mobile Note 3?
This is as far as I got in towards the process before I stopped due to something unexpected:
1) TowelRoot. Rooted it and confirmed with the Root app that it was indeed rooted.
2) Downloaded SuperSU. I installed the binary using the Normal mode since I didn't have CWM or TWRM at the time. It asked me to disable KNOX and it looks like it was fine. I restarted it.
This is where I stopped. After I installed it, it asked me to confirm if I want to confirm allowing Freedom and SetCPU. I did and it continuously started spamming the notification that it was allowed for 20 minutes.
I went into the SuperSU program to see what's wrong and it then told me that the Binary could NOT be found and that I may have to flash my rom back to get it back to normal. It then gave me the error that something was wrong on my phone and that I might have to install something called Samsung Kies to make it better.
I pretty much freaked out at this point and de-installed SuperSU out of fear that I might screw up my phone. Now I'm extremely fearful to do anything without seeing some sort of de facto guide on what to do next.
If it helps, here's the phone information I have. I know that different ROM flashing methods are used for various kernels.
Model: SM-N900T
Android Version: 4.4.2
Baseband: N900TUVUCNB4
Kernel: 3.4.0-660648 | [email protected] #1 | Wed Feb 12 21:31:27 KST 2014
Build Number: KOT49H.N900TUVUCNB4
SE for Android Status: Enforcing | SEPF_SM-900T_4.4.2_0005 | WED FEB 12 21:31:01 2014
Security Software Version: MDF v1.0 Release 2
I have a 128GB Samsung SDXS MicroSD. The phone recognizes 119 GB of it which I know is normal.
Any help or direction would be most appreciated. The world of Flashing has so many roads that my head is spinning and my fear is that I will turn this phone into a $500 brick because I followed the wrong guide.
Thank you.

Best way of flashing a new rom is using "Odin".

dodoqq said:
Best way of flashing a new rom is using "Odin".
Click to expand...
Click to collapse
Thanks.
I do understand that and I have the program, but I can't find any SOLID documentation. I see all these different guides out there and I'm scared that I'm going to pick the wrong one. The ages vary as well, so I don't know if they are still relevant or not.
Not only that, I don't believe that just Odin is enough. There are also prerequisites that are required before I can just up and use Odin. That'st he part that I would hope a decent guide out there would provide me.

A bit early by a few minutes but, Bump for help.
Any information or leads would be terrific.
Thank you.

Nanaya Shiki said:
A bit early by a few minutes but, Bump for help.
Any information or leads would be terrific.
Thank you.
Click to expand...
Click to collapse
Contact me on Google+, I can help you with this and calm you down about it.
It's +NicholasPhilipChum

[Q] Towelroot no longer works... ideas?

I'm pretty new to the Android phones. I bought a Samsung Galaxy Note 8 tablet about a year ago, and I absolutely love it -- which was the only reason why I considered an Android phone when it came time to upgrade. That might have been a mistake.
The phone I chose was a Galaxy S5 from AT&T.
For many reasons I won't go into (and that many of you probably know) Kitkat is awful. Removing SD card access removed one of the most important reasons that I bought the phone. So, I decided to root the thing.
I read a bunch of info on how to root, and, eventually downloaded and tried to use towelroot only to discover that AT&T/Google have blocked all functionality of that program. My build is, unfortunately, the latest build -- July 22 2014 (or there abouts).
Now, I'm not sure if the phone was given to me with that update -- I only got the thing on Sunday. Maybe it was, maybe not. Dunno. So I have a couple of questions.
If I were to factory reset the phone, would that roll back these "Security" OTA updates that were pushed onto the phone? I'm pretty sure there was at least one after I got the thing. I've spent a fair amount of time setting the phone up, but I'll do it again if a factory reset would allow me to root the phone and return the SD card functions.
Is there a way to push an earlier version of the ROM onto the phone. I'm guessing not, since I think I read that AT&T helpfully locked the bootloader.
Finally, does anyone know of any way to root this device if neither of the two paths I presented above will work?
Thanks for any help. If I can't restore the SD card functionality, I'll probably just return the phone. That would be a bummer because I was really excited about it.

CKR83 said:
I'm pretty new to the Android phones. I bought a Samsung Galaxy Note 8 tablet about a year ago, and I absolutely love it -- which was the only reason why I considered an Android phone when it came time to upgrade. That might have been a mistake.
The phone I chose was a Galaxy S5 from AT&T.
For many reasons I won't go into (and that many of you probably know) Kitkat is awful. Removing SD card access removed one of the most important reasons that I bought the phone. So, I decided to root the thing.
I read a bunch of info on how to root, and, eventually downloaded and tried to use towelroot only to discover that AT&T/Google have blocked all functionality of that program. My build is, unfortunately, the latest build -- July 22 2014 (or there abouts).
Now, I'm not sure if the phone was given to me with that update -- I only got the thing on Sunday. Maybe it was, maybe not. Dunno. So I have a couple of questions.
If I were to factory reset the phone, would that roll back these "Security" OTA updates that were pushed onto the phone? I'm pretty sure there was at least one after I got the thing. I've spent a fair amount of time setting the phone up, but I'll do it again if a factory reset would allow me to root the phone and return the SD card functions.
Is there a way to push an earlier version of the ROM onto the phone. I'm guessing not, since I think I read that AT&T helpfully locked the bootloader.
Finally, does anyone know of any way to root this device if neither of the two paths I presented above will work?
Thanks for any help. If I can't restore the SD card functionality, I'll probably just return the phone. That would be a bummer because I was really excited about it.
Click to expand...
Click to collapse
For rooting, go there http://forum.xda-developers.com/showthread.php?t=2696537
or there http://forum.xda-developers.com/showthread.php?t=1980683
Follow tuto or ask here.
You have to give more info (S5 model, firmware...)
Good luck
Franky

Rooting Help?
fgth90 said:
For rooting, go there http://forum.xda-developers.com/showthread.php?t=2696537
or there http://forum.xda-developers.com/showthread.php?t=1980683
Follow tuto or ask here.
You have to give more info (S5 model, firmware...)
Good luck
Franky
Click to expand...
Click to collapse
I see that there are tutes here, and am wading through the 50+ pages of forum posts to find what I need. However, my worry is that none of this stuff will work because of the new firmware. Here is all the info that I have on my phone:
Galaxy S5 AT&T US version (SAMSUNG-SM-900A)
Android 4.4.2
kernel version 3.4.0-2178781 [email protected] #1 Tuesday July 22
Build # KOT49H.G900AUCU2ANG3
SE for Android Status
Enforcing SEPF_SAMSUNG-SM-G900A_4.4.2_0018 Tuesday July 22
Security Software version:
MDF v1.0 Release 3
VPN v1.4 Release 1
Thanks all the pertinent info, I think.
Because the update was so new, I don't think there's a way to root this anymore. People keep telling me to use ODIN and to download an earlier ROM (and I now have ODIN and an earlier ROM -- hopefully from a good source, but I have no idea if it is), but my impression is that this latest AT&T "security" update keeps you from reflashing the ROM because of the bootloader lockout.
Any further help would be appreciated.
Thanks

CKR83 said:
...
Any further help would be appreciated.
Thanks
Click to expand...
Click to collapse
Hello,
As I told you, the only method working for me (because of towelroot non working) is cf auto root.
Check periodicaly here http://autoroot.chainfire.eu/ to see if your model is listed.
I had just a look and it's not listed yet.
If it is, flash by odin and look if root works.
If not, you've got to flash by odin the same rom again (keep your original file on pc), you'll loose nothing, and report this fails on chainfire to test other solution.
Good luck
Franky

CKR83 said:
Here is all the info that I have on my phone:
Galaxy S5 AT&T US version (SAMSUNG-SM-900A)
Android 4.4.2
kernel version 3.4.0-2178781 [email protected] #1 Tuesday July 22
Build # KOT49H.G900AUCU2ANG3
SE for Android Status
Enforcing SEPF_SAMSUNG-SM-G900A_4.4.2_0018 Tuesday July 22
Security Software version:
MDF v1.0 Release 3
VPN v1.4 Release 1
Click to expand...
Click to collapse
Not only build number and kernel version, you need to check your Bootloader version with Phone INFO ★Samsung★ app (in the FIRMWARE INFO section).
Bootloader version is one of the important info to check when you are going to root or flashing custom rom.

vndnguyen said:
Not only build number and kernel version, you need to check your Bootloader version with (in the FIRMWARE INFO section).
Bootloader version is one of the important info to check when you are going to root or flashing custom rom.
Click to expand...
Click to collapse
Hey that looks like a great utility. Thanks! The bootloader is G900AUCU2ANG3
Does that help any? People keep telling me I need to use ODIN and flash this, that or the other thing. Those comments would probably be more helpful if I knew more about this stuff, but my reading has lead me to believe that ODIN won't work with certain version of the bootloader. Or is that wrong?

CKR83 said:
Hey that looks like a great utility. Thanks! The bootloader is G900AUCU2ANG3
Did you every get your post July 2014 AT&T GS5 rooted?
If so, please drop me an email.
Thanks
TPG
Click to expand...
Click to collapse

No unfortunately not....
Sent from my SAMSUNG-SM-G870A using XDA Free mobile app

SM-G9208 root on 5.1.1

After a whole week of searching and tripping knox i finally done it:
SM-G9208 root
After using CROM service and unlocking the CROM using ODIN to flash the attached file.
The source is this:
http://apk.tw/thread-704730-1-1.html
http://pan.baidu.com/s/1ntu1gjn
No credit to me
Here is my uploaded copy:
http://farzad.devbro.com/SM-9208_root_0902.tar

Dude, you saved my life
Was about to sell my s6 when I saw this man. Thank you so much
Edit: By any chance can you reupload the file here? Takes so long to download because it throttles at 25 kbps for me :/
Edit 2: Nvm got it to download fast haha FINALLY ROOT ACCESS!!

u root without tripping knox ?

ham4ever said:
u root without tripping knox ?
Click to expand...
Click to collapse
My knox was tripped before hand. Not sure if it does or not.

JoeCatarata said:
Was about to sell my s6 when I saw this man. Thank you so much
Edit: By any chance can you reupload the file here? Takes so long to download because it throttles at 25 kbps for me :/
Edit 2: Nvm got it to download fast haha FINALLY ROOT ACCESS!!
Click to expand...
Click to collapse
What is your Knox status?

Is it also for g920f with coh2? Knox?

devbro said:
What is your Knox status?
Click to expand...
Click to collapse
Don't really know how to check lol haha

JoeCatarata said:
Don't really know how to check lol haha
Click to expand...
Click to collapse
my knox is tripped.

After following this method I get a bootloop, any idea why and how to correct it?, already tried a factory reset but it doesn´t work, I had to flash stock rom again.
Edit: It happens because I upgraded to the latest 5.1.1 version available last week:
Model SM-G9208
Model name GALAXY S6
Country Taiwan
Version Android 5.1.1
Changelist 5683207
Build date Tue, 06 Oct 2015 11:54:52 +0000
Product code BRI
PDA G9208ZTU2COJ2
CSC G9208ZZT2COJ2
So if you get the update alert in your phone DON´T do it, there is no known way to ROOT this new version.
It was not possible to install a previous 5.1.1 version either (G9208ZTU1BOH2), when I try to flash it with ODIN, the phone just displays an error message “SW REV CHECK FAIL DEVICE 2 BINARY 1”.
Any Ideas are appreciated.
EDIT:
Finally rooted with xiao1u root method!

devbro said:
After a whole week of searching and tripping knox i finally done it:
SM-G9208 root
After using CROM service and unlocking the CROM using ODIN to flash the attached file.
The source is this:
http://apk.tw/thread-704730-1-1.html
http://pan.baidu.com/s/1ntu1gjn
No credit to me
Here is my uploaded copy:
http://farzad.devbro.com/SM-9208_root_0902.tar
Click to expand...
Click to collapse
Root works perfectly, but has anybody got TWRP working on 5.1? I've always had unusable touchscreen issues on it so stayed back on 5.0.2 until somebody devs a working build.

Dissmeister said:
Root works perfectly, but has anybody got TWRP working on 5.1? I've always had unusable touchscreen issues on it so stayed back on 5.0.2 until somebody devs a working build.
Click to expand...
Click to collapse
no go. i used the TWRP app to flash all new files.

devbro said:
no go. i used the TWRP app to flash all new files.
Click to expand...
Click to collapse
So your twrp works perfectly on 5.1 base? If so, could you share it with me?
I've been looking for a twrp that worked on 5.1 without the touchscreen not working. Thanks man

Definitely no luck rooting my phone,
Product code BRI
PDA G9208ZTU2COJ2
CSC G9208ZZT2COJ2
The file on first post didn´t work, and 3 days after I rooted (and everything was working perfectly) using this file:
http://pan.baidu.com/wap/album/file...26914354&fsid=128909912720545&adapt=pc&fr=ftw
I get the following error message every time i need root access:
"There is no SU binary installed, and SuperSU cannot install it. This is problem! If you upgraded to Android 5.0, you will need to manually re-root - consult the relevant forums for your device!"
If the phone is restarted or turned off after getting this error message the phone is death, it doesn´t start again.
I tried reflashing the root file, but it didn´t work.
I had to reinstall the stock ROM agan, and waiting for any effective root method for 5.1.1 OJ2 ROM.

0ptimus82 said:
After following this method I get a bootloop, any idea why and how to correct it?, already tried a factory reset but it doesn´t work, I had to flash stock rom again.
Edit: It happens because I upgraded to the latest 5.1.1 version available last week:
Model SM-G9208
Model name GALAXY S6
Country Taiwan
Version Android 5.1.1
Changelist 5683207
Build date Tue, 06 Oct 2015 11:54:52 +0000
Product code BRI
PDA G9208ZTU2COJ2
CSC G9208ZZT2COJ2
So if you get the update alert in your phone DON´T do it, there is no known way to ROOT this new version.
It was not possible to install a previous 5.1.1 version either (G9208ZTU1BOH2), when I try to flash it with ODIN, the phone just displays an error message “SW REV CHECK FAIL DEVICE 2 BINARY 1”.
Any Ideas are appreciated.
EDIT:
Finally rooted with xiao1u root method!
Click to expand...
Click to collapse
Hey, the same thing happened to me, I was stupid enough to not read this before. I tried the xiao1u method and it works, but it breaks mobile data. Did you get that issue?

Dissmeister said:
Hey, the same thing happened to me, I was stupid enough to not read this before. I tried the xiao1u method and it works, but it breaks mobile data. Did you get that issue?
Click to expand...
Click to collapse
Not in my case, my data was working perfectly, but problems started to show up 3 days after I rooted it, in the end it didn´t start again.
I haven´t found any other way to root this build yet and I´m still looking for a custom rom with no success.
If you want to give another try to xiao1u file try to disable the setting for "allow Google to regularly check device activity for security problems or warn about potential harm" after a clean ROM install, you can do it going to the GOOGLE SETTINGS app > SECURITY > VERIFY APPS & uncheck Scan For Security Threats.
Please keep us updated, I´ll post if I find any way to solve it.

0ptimus82 said:
Not in my case, my data was working perfectly, but problems started to show up 3 days after I rooted it, in the end it didn´t start again.
I haven´t found any other way to root this build yet and I´m still looking for a custom rom with no success.
If you want to give another try to xiao1u file try to disable the setting for "allow Google to regularly check device activity for security problems or warn about potential harm" after a clean ROM install, you can do it going to the GOOGLE SETTINGS app > SECURITY > VERIFY APPS & uncheck Scan For Security Threats.
Please keep us updated, I´ll post if I find any way to solve it.
Click to expand...
Click to collapse
Ok you may know this already but I'll post just to let you everybody else know.
DONT UPDATE TO THE LATEST 5.1 OTA. It adds rollback protection to your bootloader, which makes it impossible for you to odin to another build, unless its the same or a future update.
http://forum.xda-developers.com/tmobile-galaxy-s6-edge/general/psa-odin-5-1-1-t3136151
As for our case, mate, I tried everything so far, the root method given by the OP bootloops on the latest OTA (previous 5.1 firmware on Sammobile is fine) and xiao1u method breaks mobile data for me although root does work perfectly. Funny thing is that if you tried the root by the OP and it got bricked, flashing the xiao1u method on top of it will get it working again, because its just the boot partition.
Atm, I just got sick of Samsung and their cr*p, had the same issues with my old Galaxy S4 with their Exynos. Got the Nexus 6P today and absolutely loving it.
I'll try to work it out sometime soon, if I do manage to get it working (mobile data for me) I'll post the fix here. This device is next to DOA for us as we've just got a couple of few blessed asian devs on it (all thanks to them). Unfortunately it may never be enough. I never got the issue you had, though it was just for last night, can you get into download mode? If so, odin the same firmware again. I used the 5.1 OTA on Sammobile, Taiwan. This is only for us who are already stuck in the new bootloader. You wont have root but at least your phone will work.
Cheers mate, all the best. Will update if I find a fix.

Dissmeister said:
Ok you may know this already but I'll post just to let you everybody else know.
DONT UPDATE TO THE LATEST 5.1 OTA. It adds rollback protection to your bootloader, which makes it impossible for you to odin to another build, unless its the same or a future update.
http://forum.xda-developers.com/tmobile-galaxy-s6-edge/general/psa-odin-5-1-1-t3136151
As for our case, mate, I tried everything so far, the root method given by the OP bootloops on the latest OTA (previous 5.1 firmware on Sammobile is fine) and xiao1u method breaks mobile data for me although root does work perfectly. Funny thing is that if you tried the root by the OP and it got bricked, flashing the xiao1u method on top of it will get it working again, because its just the boot partition.
Atm, I just got sick of Samsung and their cr*p, had the same issues with my old Galaxy S4 with their Exynos. Got the Nexus 6P today and absolutely loving it.
I'll try to work it out sometime soon, if I do manage to get it working (mobile data for me) I'll post the fix here. This device is next to DOA for us as we've just got a couple of few blessed asian devs on it (all thanks to them). Unfortunately it may never be enough. I never got the issue you had, though it was just for last night, can you get into download mode? If so, odin the same firmware again. I used the 5.1 OTA on Sammobile, Taiwan. This is only for us who are already stuck in the new bootloader. You wont have root but at least your phone will work.
Cheers mate, all the best. Will update if I find a fix.
Click to expand...
Click to collapse
The results of my attempt to root is not very consistent or stable since 5.02 to 5.1.1 on different updates of the Taiwan variant (G9208).
Since first 5.1.1 update, I used xiaolu method and succeed for few days, I don't know what do you mean " xiao1u method breaks mobile data", my 4G signal was fine. With xposed hooked, I also observed the much more boot time of previous rooted phone, sometimes a smaller bootloop (3 or 4 repeated loops).
But after a very recent "samsung security policy update", the root has "gone" an re-root became impossible no matter by xiaolu's or chainfire UPDATE-SuperSU-v2.46, most time they will cause bootloop and I can use odin to get back to initial status. Does that mean I don't have hope to root again?

Dissmeister said:
So your twrp works perfectly on 5.1 base? If so, could you share it with me?
I've been looking for a twrp that worked on 5.1 without the touchscreen not working. Thanks man
Click to expand...
Click to collapse
This works on my Taiwan variant G9208 on stock 5.1.1,
Go on TWRP repository of dl.twrp.me/zeroflte, seek two .tar files as below and inject them stepwisely with different method
1st (Odin via USB). Twrp-2.8.7.2-zeroflte.img.tar
2nd(use that TWRP -2.8.7.2, operate via an "OTG linked usb mouse" since touch not working...) . to flash Twrp-2.8.7.0-zerofltespr.img (but it's actually 2.8.7.1)
now you have a touchable TWRP.
But I can't get root now, even with xiaolu method, any one with luck, please note me

ttyy121 said:
The results of my attempt to root is not very consistent or stable since 5.02 to 5.1.1 on different updates of the Taiwan variant (G9208).
Since first 5.1.1 update, I used xiaolu method and succeed for few days, I don't know what do you mean " xiao1u method breaks mobile data", my 4G signal was fine. With xposed hooked, I also observed the much more boot time of previous rooted phone, sometimes a smaller bootloop (3 or 4 repeated loops).
But after a very recent "samsung security policy update", the root has "gone" an re-root became impossible no matter by xiaolu's or chainfire UPDATE-SuperSU-v2.46, most time they will cause bootloop and I can use odin to get back to initial status. Does that mean I don't have hope to root again?
Click to expand...
Click to collapse
It happened the same way with my phone, no hope so far.
Has anybody tried arter97 kernel?, G9208 support was added in the last beta but the problem is OJ2 particular release.
http://forum.xda-developers.com/showpost.php?p=63345352&postcount=2080

What is possible with this model?

The truth behind Samsung Galaxy Note N920F and how to update it

TLDR: Samsung N920F seems to be a N920T, and you can flush ROM from N920T.
Recently my friends asked to help them with their Galaxy Note 5 which was bought somewhere in China. It was stuck at Android 6, with last updates from 2016, and seemed to have some malware (factory reset did not help).
It was really strange to see model N920F - I checked many threads here, and everyone says that there should be no such version as N920F:
https://forum.xda-developers.com/note5/help/note-5-n920f-n920t-t3310411
https://forum.xda-developers.com/note5/help/settings-sm-n920f-boot-loader-sm-n920p-t3776224
https://forum.xda-developers.com/note5/help/note-5-sm-n920f-eu-variant-please-help-t3527449
https://forum.xda-developers.com/note5/help/sm-n920f-stock-roms-t3482405
https://forum.xda-developers.com/note5/help/note-5-european-version-sale-sm-n920f-t3190929
Unfortunately, not even one of those topics found any reason for this or solution for updating. So I tried to find out the true and update phone myself.
At first, I booted to recovery. And there I saw that it model name was nobleltetmo - same as for N920T.
So I tried to install TWRP from N920T via Odin. TWRP successfully installed but phone stopped booting and TWRP only booted but did not work - it told me about bootloader version mismatch. So I found out that phone's bootloader version was N920TUVU4DPK6. So I tried to find a working firmware for this bootloader version and found it on xda: https://forum.xda-developers.com/tm...eral/stock-n920t-stock-n920tuvu4dpk6-t3518252
Fortunately, I could enter download mode and flush it with Odin. After it, phone worked fine, and now it was officially N920T. But even better things awaited - after updating it managed to fetch fresh updates! So I downloaded and installed them. Phone updated... And found new updates... And about 10 times again like this. Finally, I got the latest official Samsung Firmware with Android 7.0 - and it works flawlessly. Even Googe Play, NFC and banking services. I suppose that after this I could flush TWRP again because bootloader version also updated - but official firmware was quite okay so I didn't want to set up Lineage OS.
By the way, I think that I could find latest firmware and flush it with Odin in one go - but I didn't succeed in finding it.
Please beware that this N920F turned to be N920T - but your one can be another (N920V or N920P, for example)!
Now I am pretty sure that F in model version stands for "F***ed up".
So check bootloader version and be accurate.

jehy_rus said:
TLDR: Samsung N920F seems to be a N920T, and you can flush ROM from N920T.
Recently my friends asked to help them with their Galaxy Note 5 which was bought somewhere in China. It was stuck at Android 6, with last updates from 2016, and seemed to have some malware (factory reset did not help).
It was really strange to see model N920F - I checked many threads here, and everyone says that there should be no such version as N920F:
https://forum.xda-developers.com/note5/help/note-5-n920f-n920t-t3310411
https://forum.xda-developers.com/note5/help/settings-sm-n920f-boot-loader-sm-n920p-t3776224
https://forum.xda-developers.com/note5/help/note-5-sm-n920f-eu-variant-please-help-t3527449
https://forum.xda-developers.com/note5/help/sm-n920f-stock-roms-t3482405
https://forum.xda-developers.com/note5/help/note-5-european-version-sale-sm-n920f-t3190929
Unfortunately, not even one of those topics found any reason for this or solution for updating. So I tried to find out the true and update phone myself.
At first, I booted to recovery. And there I saw that it model name was nobleltetmo - same as for N920T.
So I tried to install TWRP from N920T via Odin. TWRP successfully installed but phone stopped booting and TWRP only booted but did not work - it told me about bootloader version mismatch. So I found out that phone's bootloader version was N920TUVU4DPK6. So I tried to find a working firmware for this bootloader version and found it on xda: https://forum.xda-developers.com/tm...eral/stock-n920t-stock-n920tuvu4dpk6-t3518252
Fortunately, I could enter download mode and flush it with Odin. After it, phone worked fine, and now it was officially N920T. But even better things awaited - after updating it managed to fetch fresh updates! So I downloaded and installed them. Phone updated... And found new updates... And about 10 times again like this. Finally, I got the latest official Samsung Firmware with Android 7.0 - and it works flawlessly. Even Googe Play, NFC and banking services. I suppose that after this I could flush TWRP again because bootloader version also updated - but official firmware was quite okay so I didn't want to set up Lineage OS.
By the way, I think that I could find latest firmware and flush it with Odin in one go - but I didn't succeed in finding it.
Please beware that this N920F turned to be N920T - but your one can be another (N920V or N920P, for example)!
Now I am pretty sure that F in model version stands for "F***ed up".
So check bootloader version and be accurate.
Click to expand...
Click to collapse
Same prob here malware and pops up ads in N920F. And device cannot be registered for updating. And odin says its N920K. If you have any link help me.

Mynouddin said:
Same prob here malware and pops up ads in N920F. And device cannot be registered for updating. And odin says its N920K. If you have any link help me.
Click to expand...
Click to collapse
I think you can try this rom: https://forum.xda-developers.com/note5/general/rom-lineageos-15-1-note-5-android-8-1-t3737405
If it is not compatible, you can enter rescue mode and check bootloader version.

jehy_rus said:
I think you can try this rom: https://forum.xda-developers.com/note5/general/rom-lineageos-15-1-note-5-android-8-1-t3737405
If it is not compatible, you can enter rescue mode and check bootloader version.
Click to expand...
Click to collapse
Thread closed

I need your help.
I am very glad to find your article because i ve the n920f and am really ****ed up.
How can i find my recovery code to know which model am on. I will be very glad if you can help me out. Thanks

Nanakwameampong said:
I am very glad to find your article because i ve the n920f and am really ****ed up.
How can i find my recovery code to know which model am on. I will be very glad if you can help me out. Thanks
Click to expand...
Click to collapse
Download this app it will show you your correct software and model.
https://play.google.com/store/apps/details?id=org.vndnguyen.phoneinfo

root G930VVRUACSF2 firmware

i updated my phone to the latest firmware. i had root before i took the update through odin. i was on like two firmwares older then the latest one. not sure what the build was. i used this link to get root. https://forum.xda-developers.com/ve...reo-nougat-t3819616/post79522881#post79522881
it worked good but i wanted to update so i noticed the link or thread provided only works up to bootloader version 9. this new update updated the number to 10 so i get a fail in odin now. can someone update the V9 kernel in the link to V10 or is it more complicated then that? any input is welcome. thanks

Also in the same boat.. would appreciate any help

Also recently got this, would love a fix. Thanks!

Any updates on the latest G930VVRUACSF2 firmware? I tried root, but failed.

I agree. Any update on g930vvruacsf2?