Database Users

[Official] [4.2.2] [GT-N5120] Galaxy Note 8.0 LTE Update [N5120XXCMH1]

Update for Galaxy Note 8.0 LTE (GT-N5120) are out today
Model: GT-N5120
Country: United Kingdom
Version: Android 4.2.2
Changelist: 1210063
Build date: Thu, 01 Aug 2013 12:21:19 +0000
Product Code: BTU
PDA: N5120XXCMH1
CSC: N5120BTUCMH1
MODEM: N5120XXCMG7
Get it Here
Changelist is the same as the former UK 4.2.2 release, so no idea what changed really.
Will download, update and report back

Slipurson said:
Update for Galaxy Note 8.0 LTE (GT-N5120) are out today
Model: GT-N5120
Country: United Kingdom
Version: Android 4.2.2
Changelist: 1210063
Build date: Thu, 01 Aug 2013 12:21:19 +0000
Product Code: BTU
PDA: N5120XXCMH1
CSC: N5120BTUCMH1
MODEM: N5120XXCMG7
Get it Here
Changelist is the same as the former UK 4.2.2 release, so no idea what changed really.
Will download, update and report back
Click to expand...
Click to collapse
Any update on what the differance is over the previous release?

If this ROM causes the S-Pen to have an offset, please let us know here:
4.2.2 Update S-Pen Inaccuracy Thread

KTM690 said:
Any update on what the differance is over the previous release?
Click to expand...
Click to collapse
I cant find any differences at all actually, the offset for the S-Pen is there still and everything else works just as it did with the previous 4.2.2
CafeKampuchia said:
If this ROM causes the S-Pen to have an offset, please let us know here:
4.2.2 Update S-Pen Inaccuracy Thread
Click to expand...
Click to collapse
Ill post my findings in the thread.

I am assuming you are talking about the browser bug? That was an issue with chrome's zoom being inaccurate on, frankly, every Galaxy Note up until now. They fixed it recently.
Sent from my SAMSUNG-SGH-I467 using xda premium

'H+' vs 'H' Icon
Hi
Just flashed this ROM on my HK Note N5120 LTE (CSC Was TGY). The device came from Panamoz.com as I was struggling to buy the LTE version sim free in the UK for reasonable money, and Kies was not offering to upgrade the stock 4.1.2 firmware to 4.2.2.
Used this method: http://forum.xda-developers.com/showpost.php?p=44241666&postcount=4
All worked fine, Answered 'No' when asked about making CWM recovery permanent. The CSC became BTU (UK) after the flash. CWM recovery was replaced with stock during the flash.
Since I am in the UK, I flashed the modem files that came with the ROM, and still get 4G. I have the same issue as everyone else regarding the S-Pen offset - probably not bad enough to flash back to 4.1.2 for me, but hopefully Samsung will fix.
My main issue is that compared to 4.1.2, I hardly ever see the device show 'H+', only 'H'. I travel the same route on the train daily, and now, I see 'H+' 10% of the time rather than 90% of the time. My other device on the same network still shows H+.
Maybe others have seen my 'H' vs 'H+' issue?
Does this device support DC-HSPA?? I recall that with the S3 and Note2, one gained DC-HSPA+42 (so called 3.75G theoretical max 42Mbps), when one bought the LTE version of the phone. The non LTE versions only had HSPA+21. Reason I am asking is I am wondering if the 'H+' now only shows for DC-HSPA rather than for HSPA+21 ??
Tempted to flash the old modem files again, see if my H+ returns to normal operation - and of course to see if its any faster.
My device is still rooted with the flash counter == 2, and It does still appear to be recognized by kies when connected to the PC. Time will tell whether I will get updates via Kies still. If not then maybe I will need to use Triangle to reset the flash counter, and then do a full unroot.
Nigel

veletron said:
Hi
Just flashed this ROM on my HK Note N5120 LTE (CSC Was TGY). The device came from Panamoz.com as I was struggling to buy the LTE version sim free in the UK for reasonable money, and Kies was not offering to upgrade the stock 4.1.2 firmware to 4.2.2.
Used this method: http://forum.xda-developers.com/showpost.php?p=44241666&postcount=4
All worked fine, Answered 'No' when asked about making CWM recovery permanent. The CSC became BTU (UK) after the flash. CWM recovery was replaced with stock during the flash.
Since I am in the UK, I flashed the modem files that came with the ROM, and still get 4G. I have the same issue as everyone else regarding the S-Pen offset - probably not bad enough to flash back to 4.1.2 for me, but hopefully Samsung will fix.
My main issue is that compared to 4.1.2, I hardly ever see the device show 'H+', only 'H'. I travel the same route on the train daily, and now, I see 'H+' 10% of the time rather than 90% of the time. My other device on the same network still shows H+.
Maybe others have seen my 'H' vs 'H+' issue?
Does this device support DC-HSPA?? I recall that with the S3 and Note2, one gained DC-HSPA+42 (so called 3.75G theoretical max 42Mbps), when one bought the LTE version of the phone. The non LTE versions only had HSPA+21. Reason I am asking is I am wondering if the 'H+' now only shows for DC-HSPA rather than for HSPA+21 ??
Tempted to flash the old modem files again, see if my H+ returns to normal operation - and of course to see if its any faster.
My device is still rooted with the flash counter == 2, and It does still appear to be recognized by kies when connected to the PC. Time will tell whether I will get updates via Kies still. If not then maybe I will need to use Triangle to reset the flash counter, and then do a full unroot.
Nigel
Click to expand...
Click to collapse
Just got mine from the same place. Your post has helped me with some questions I had. Thanks.:good:

No OTA For me
So, the next stage was to run Triangle away, which worked fine (counter reset to 'No'). Just be brave and accept the big red warning.
Following on from that, I unrooted using the unroot option in Super User app that was installed by chainfire's 'auto root'.
This worked too, and I confirmed root gone. After a reboot, I reconnected to Kies, to check that it recognized the firmware on the device as the 'latest'. It was.
I then tried the 'Software Update' option under Settings->about device, unfortunately, this no longer works it just says 'connecting to server' forever and eventually comes up with a message: 'your device has been modified, software updates are not available'. So No OTA for me.
Any idea how to get OTA working again??
Here is the screenshot from the downloading screen, showing 'official' for all the firmwares on the device. Could it have something to do with the CSC? (TGY on 4.1.2 and BTU on 4.2.2) ?
http://photos.veletron.com/index.php/album151/P1070688
If I goto Settings-->About Device-->Status, and wait an age while the 'Device Status' field updates, it reports 'custom'. I guess this is why, but how come given that the 'download' screen reports as per the above screen shot?!
Prior to running Triangle Away, and unrooting, the OTA check on the device, span for a while before reporting no new updates available.
Nigel

veletron said:
Hi
Just flashed this ROM on my HK Note N5120 LTE (CSC Was TGY). The device came from Panamoz.com as I was struggling to buy the LTE version sim free in the UK for reasonable money, and Kies was not offering to upgrade the stock 4.1.2 firmware to 4.2.2.
Used this method: http://forum.xda-developers.com/showpost.php?p=44241666&postcount=4
All worked fine, Answered 'No' when asked about making CWM recovery permanent. The CSC became BTU (UK) after the flash. CWM recovery was replaced with stock during the flash.
Since I am in the UK, I flashed the modem files that came with the ROM, and still get 4G. I have the same issue as everyone else regarding the S-Pen offset - probably not bad enough to flash back to 4.1.2 for me, but hopefully Samsung will fix.
My main issue is that compared to 4.1.2, I hardly ever see the device show 'H+', only 'H'. I travel the same route on the train daily, and now, I see 'H+' 10% of the time rather than 90% of the time. My other device on the same network still shows H+.
Maybe others have seen my 'H' vs 'H+' issue?
Does this device support DC-HSPA?? I recall that with the S3 and Note2, one gained DC-HSPA+42 (so called 3.75G theoretical max 42Mbps), when one bought the LTE version of the phone. The non LTE versions only had HSPA+21. Reason I am asking is I am wondering if the 'H+' now only shows for DC-HSPA rather than for HSPA+21 ??
Tempted to flash the old modem files again, see if my H+ returns to normal operation - and of course to see if its any faster.
My device is still rooted with the flash counter == 2, and It does still appear to be recognized by kies when connected to the PC. Time will tell whether I will get updates via Kies still. If not then maybe I will need to use Triangle to reset the flash counter, and then do a full unroot.
Nigel
Click to expand...
Click to collapse
I can not say anything about the OTAupdates since I never use Kies to update, but as for the modem, I am running the "old" 4.1.2 modem and it is working well for me, tho I have not compared my note now and before in regards to how ofteni see H+ or just H, most often I see the 4G icon where I usually hang out.
But I would try the 4.1.2 modem for your region and see if it changes anything.
Sent from Galaxy no. N5120 via the LTE-network

Got mine updated to 4.2.2 yesterday.

Not sure why but my battery life seemed to have taken a hit since upgrading.
On 4.1.2 i used to be able to last a day easily with about 30 - 40% left each day (7am till 9pm). after updating to 4.2.2 I am down to 30% in 5 hrs. Tab gets hotter too. Anyone experience the same issue?
I am back on 4.1.2 for now. Everything's good again.

thanks man for update.

Just for info
After the update to 4.2.2 Mh1 by flashing the firmware here, I never got OTA again (says device status custom). Stock rom and flash counter zero. I was however able to update to MH2 via kies. I am still told device status custom!
No difference for me re pen pointer offset on MH1/MH2 not sure Samsung will ever bother to fix this.
My device now BTU but it started as Hong Kong. I suspect this is why it reckons it's "custom".
Nigel

veletron said:
Just for info
After the update to 4.2.2 Mh1 by flashing the firmware here, I never got OTA again (says device status custom). Stock rom and flash counter zero. I was however able to update to MH2 via kies. I am still told device status custom!
No difference for me re pen pointer offset on MH1/MH2 not sure Samsung will ever bother to fix this.
My device now BTU but it started as Hong Kong. I suspect this is why it reckons it's "custom".
Nigel
Click to expand...
Click to collapse
I have the same device but not the same problem. I also updated to MH2 via Odin and my status is normal. The offset for me is much better than previous, and I have no problem with the battery lasting more than a day using WiFi and push mail along with the normal use. However although recognized by Kies it would not update, I recon because of the CSC.

craylim said:
Not sure why but my battery life seemed to have taken a hit since upgrading.
On 4.1.2 i used to be able to last a day easily with about 30 - 40% left each day (7am till 9pm). after updating to 4.2.2 I am down to 30% in 5 hrs. Tab gets hotter too. Anyone experience the same issue?
I am back on 4.1.2 for now. Everything's good again.
Click to expand...
Click to collapse
Sent from my GT-N5120 using XDA Premium HD app
Battery seem to drain faster since I upgraded to 4.2.2

Multi Window
Hey,
I've update my rom on my 5120 to the MH2 and still having problem with multi window greyed out in the setting>display
Has anybody else have this problem?
Is they any way to fix it?
I upgraded the rom using the odin version 1.85 had the tick in auto reboot and F. Rest time and I ticked PDA and put the md5 file on the pda line where I placed the tick is that all correct or should I've used a different version?
Please can anybody help me.
Thanks
Gigino

THANK YOU! THANK YOU! THAAAAAAAANK YOOOOOOOU! (if it didn't look and/or feel weird, I'd kiss you! *LOL* I wouldn't it was a joke)
BUT you saved my stupid self from self pity. You see, I didn't realize - until too late - that there were 3 versions of this device, and attempted to install a 5110 ROM. That caused me 5 DAYS of hell until I cam across this, and voila! I got my tablet back. So again - TANK YOU THANK YOU THANK YOU!
One Note: Baseband I467MVLAMG2 and Build Number: JDQ39.N5120XXCMH2 (not 1)

_Allan_ said:
THANK YOU! THANK YOU! THAAAAAAAANK YOOOOOOOU! (if it didn't look and/or feel weird, I'd kiss you! *LOL* I wouldn't it was a joke)
BUT you saved my stupid self from self pity. You see, I didn't realize - until too late - that there were 3 versions of this device, and attempted to install a 5110 ROM. That caused me 5 DAYS of hell until I cam across this, and voila! I got my tablet back. So again - TANK YOU THANK YOU THANK YOU!
One Note: Baseband I467MVLAMG2 and Build Number: JDQ39.N5120XXCMH2 (not 1)
Click to expand...
Click to collapse
Great post. I feel your joy

THere is a newer version. Does anyone know how we can go from JDQ39.N5120XXCMH2 to the new JDQ39.N5120XXCMI2 version?
My phone also says custom like Nigels problem above, I am having same problem that he was having when he first went to 4.2.2 from 4.2.1... I'm currently on 4.2.2 trying to go to the new CMI2.

CCJ22 said:
THere is a newer version. Does anyone know how we can go from JDQ39.N5120XXCMH2 to the new JDQ39.N5120XXCMI2 version?
My phone also says custom like Nigels problem above, I am having same problem.
Click to expand...
Click to collapse
I downloaded the CMI2 version from samsmobile site. It was a KIES file extracted the file and using mobile odin flashed it to my device. All working fine.:good:

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?

i got nougat update for T715 today

hello XDA members
I have the samsung tab s2 T715 from Emirates
I did manually check for an update today and got this in the picture
Have fun

Cool hoping 815 follows
Sent from my SM-G935F using XDA-Developers Legacy app

Hello.
I have a German unbranded device.
Since I did not want to wait for Samsung I installed the update myself by getting the already released version they seed in Italy since a few days.
Almost the same. Lte and German Sim card working, everything like if is supposed to. I think installing the Italian update is not a problem.
Works like a charm. Much faster then before. Some screens are following. I can recommend it to everyone that doesn't want to longer. St least for me there's is no problem.

StilleWaesser said:
Hello.
I have a German unbranded device.
Since I did not want to wait for Samsung I installed the update myself by getting the already released version they seed in Italy since a few days.
Almost the same. Lte and German Sim card working, everything like if is supposed to. I think installing the Italian update is not a problem.
Works like a charm. Much faster then before. Some screens are following. I can recommend it to everyone that doesn't want to longer. St least for me there's is no problem.
Click to expand...
Click to collapse
Is a factory reset needed? Or can you keep all your apps and settings?

Slurm said:
Is a factory reset needed? Or can you keep all your apps and settings?
Click to expand...
Click to collapse
All kept like normal update OTA. Just in download mode, installed update, took less then 5 Minutes and everything like before, except new Android version. Pretty smooth.

StilleWaesser said:
All kept like normal update OTA. Just in download mode, installed update, took less then 5 Minutes and everything like before, except new Android version. Pretty smooth.
Click to expand...
Click to collapse
Great, I think I'll update too!

Some more pictures

StilleWaesser said:
Hello.
I have a German unbranded device.
Since I did not want to wait for Samsung I installed the update myself by getting the already released version they seed in Italy since a few days.
Almost the same. Lte and German Sim card working, everything like if is supposed to. I think installing the Italian update is not a problem.
Works like a charm. Much faster then before. Some screens are following. I can recommend it to everyone that doesn't want to longer. St least for me there's is no problem.
Click to expand...
Click to collapse
Is your device a T715 or T715Y? Does it even make any difference? I have a T715Y (imported from China, I think) and have downloaded the Nougat ROM (which is noted as being for T715 (but not specifically fore the T715Y) from Sammobile and tried installing it using Odin 3.12 but it fails. I also tried using Odin 3.11 which also fails. Both ran as Administrator.
Current ROM Build Number is T715YDXU2BPJ1
Can anyone give me some idea of where I might be going wrong?

GrandMasterPlank said:
Is your device a T715 or T715Y? Does it even make any difference? I have a T715Y (imported from China, I think) and have downloaded the Nougat ROM (which is noted as being for T715 (but not specifically fore the T715Y) from Sammobile and tried installing it using Odin 3.12 but it fails. I also tried using Odin 3.11 which also fails. Both ran as Administrator.
Current ROM Build Number is T715YDXU2BPJ1
Can anyone give me some idea of where I might be going wrong?
Click to expand...
Click to collapse
I think you need a rom for your device (https://www.sammobile.com/firmwares/database/SM-T715Y/).
For me the update with the italian version worked great and I now have a german-austrian-italian S2 :laugh:

I have sm t 715 without y. Differences between the both devices I don't know but I'd suggest you wait until the proper firmware is release for your device. As far as I see there is no android 7 rolled out four your device.

Any ETA on Android 7.0 for the real SM-T715Y? Does anybody know anything?
I got the SM-T710 XSA Nougat update some time ago now. But I bought the 4G version off Gumtree and it is still stuck with 6.0.1 which means the lowlife carriers are probably halting the updates.
It is disgusting. With carrierless Samsung Galaxy smartphones, Samsung waits for the carriers in XSA region to start to release their crapware, before they release the official Samsung firmware. I do not know if this occurs in other regions.
FYI, the SM-T715Y is the real Tab S2. The SM-T715 has very few firmware regions and was probably made for dodgy countries with outdated cell towers. Look them up on sammobile.com/firmwares
Thanks people!

LineageOS 14.1 Q&A

XDA:DevDB Information
LineageOS 14.1 Q&A, ROM for the Samsung Galaxy Note 4
Contributors
jef_00, _mone, ripee
ROM OS Version: 7.x Nougat
Version Information
Status: Stable
Created 2017-04-22
Last Updated 2017-04-22

Just flashed "lineage-14.1-20170227-UNOFFICIAL-trltetmo.zip" on my N910T, already installed root via TWRP, and restored my apps with TitaniumBU, and my phone keeps flashing error messages like: "com.android.phone has stopped" or "android.process.media keeps stoping", what can I do?
P.S. I come from a Note 7 6.0.1. ported rom, if that helps

Juan_Jaime98 said:
Just flashed "lineage-14.1-20170227-UNOFFICIAL-trltetmo.zip" on my N910T, already installed root via TWRP, and restored my apps with TitaniumBU, and my phone keeps flashing error messages like: "com.android.phone has stopped" or "android.process.media keeps stoping", what can I do?
P.S. I come from a Note 7 6.0.1. ported rom, if that helps
Click to expand...
Click to collapse
WipeTelephonyProviderData.zip
Flash this in TWRP.

First, thanks tremendously guys for all this hard work you do for us so we can have the latest and greatest Android system.
Okay, so on to my issue. Last night I flashed cm-14.1-20161204-UNOFFICIAL-treltexx over my N910CXXS2DQB3_N910COLB2DPE3_THL sammobile stock, and as so many have posted, it looks quite nice, but the No SIM error is too big of an issue to use on my only device. This, of course, put me into many hours researching if there has been a fix to which I have found nothing definitive. As a decades-long user of XDA I came across this post showing trltetmo.zip (T-Mobile) Snapdragon, and the treltexx (Exynos) version by jef_00. Following the posted instructions to the letter, TWRP continues to return the error "this device is treltexx but the ROM is treltexx,tredl" and stops dead with error 1. As I live in Asia, we only get the Exynos Octa-core mobiles here, so every ROM update/change I've made represents the difference between the Americas and pretty much the rest of the world, so I know the correct Exynos ROM was used last night, and it pretty much ran for many hours giving only the No SIM issue. It did turn to molasses trying to get anything to do something, but I figured I'd work that part out in time.
So now I'm using ODIN to put sammobile's latest stock release N910CXXU2DQC2_N910COLB2DPE3_N910CXXU1DPE3_HOME.tar, then root it with TWRP as I've done for many years and will try jef_00's latest release lineage-14.1-20170507-UNOFFICIAL-trltexx in hopes it will recognize the Exynos version once again. If it does, I'll then use the Bootloader/Modem combo Bootloader+Modem_N910CXXS2DQA1_6.0.1 to see if it will recognize my SIM card and allow me to use my mobile phone again.
Have any of you noticed either your Snapdragon or Exynos recognizing the ROMs incorrectly? Additionally, did/does this Bootloader/Modem combo fix the SIM issue?
Thanks for anything you can tell me.
Regards,
Cole

Does anyone know of a sound mod that works well with this ROM? Every one that I flash either has no effect or stops people from being able to hear me on a phone call.

no way of getting magisk to work for snapchat access ?

Hi everybody !
I've got a N910F and flash the 20170605 version by ripee. Baseband : N910FXXS1DQD1
I'm coming from Samsung stock version.
I connect my phone to my car (Peugeot 208) via Bluetooth. My car doesn't display titles of song from Deezer or YouTube anymore.
It display just the name of the phone.
Does anyone have the same issue ? (streaming is working)

Is there a rom for Lineage OS for my canadian note 4? (trltecan)

LedHendrix said:
Is there a rom for Lineage OS for my canadian note 4? (trltecan)
Click to expand...
Click to collapse
trltetmo, link in my signature.

ripee said:
trltetmo, link in my signature.
Click to expand...
Click to collapse
So flashing the Tmo version lets me use my phone regularly? Do I need to do anything else?

LedHendrix said:
So flashing the Tmo version lets me use my phone regularly? Do I need to do anything else?
Click to expand...
Click to collapse
Flash gapps and the latest W8 bootloader and modem in my signature, for best signal stability. You can change trltetmo to trltecan in the build.prop if you want your apps to think your phone is in fact the W8 not the T, but it's hardly important.

Vortell said:
What does creeper aroma extras do? Does it work with 910v? I'm trying to figure out how to get 4g working.
Click to expand...
Click to collapse
They are a custom aroma gapps package for the Note 4 because the Open GApps aroma package doesn't work. Are you using hsbadr's lineage on your N910V? The latest build is kinda old which is why you may be having problems with 4G.

Any chance of getting official build version?

Issues with battery life
Hi! First of all, thanks to all developers, this wouldn't be possible without you, I've been using this rom quite a while, and it's amazing, just a few questions, the battery optimization isn't as great as I wish it would be, is there any kernel to increase battery life? If there's any i would be more than happy to try it, i've been in love with this rom, it's simply brilliant, Thanks for your support and your hard work... Cheers

Hello,
I just flashed LOS 14.1, works great!
I'm trying to update my modem (as recommended by ripee), but my baseband is n910w8vlu1dpe2. I did find a file for n910w8vlu1dpi2, but no 'PE2.
It's a SM-N910W8 from Rogers in Canada.
What modem firmware should I use?
Thanks!

jaylimo84 said:
Hello,
I just flashed LOS 14.1, works great!
I'm trying to update my modem (as recommended by ripee), but my baseband is n910w8vlu1dpe2. I did find a file for n910w8vlu1dpi2, but no 'PE2.
It's a SM-N910W8 from Rogers in Canada.
What modem firmware should I use?
Thanks!
Click to expand...
Click to collapse
The only one labelled as N910W8 in my BL_CP folder.

Da_Mak said:
Hi everybody !
I've got a N910F and flash the 20170605 version by ripee. Baseband : N910FXXS1DQD1
I'm coming from Samsung stock version.
I connect my phone to my car (Peugeot 208) via Bluetooth. My car doesn't display titles of song from Deezer or YouTube anymore.
It display just the name of the phone.
Does anyone have the same issue ? (streaming is working)
Click to expand...
Click to collapse
Just to say that the Bluetooth works well now with new versions. Thank you developpers.

Flashed 20170226 trtlevzw and it wont recognize my SIM card. Then tried Resurrection Remix and same thing, shows no SIM card. Cant find any solutions anywhere and need some guidance.

azreark1 said:
Flashed 20170226 trtlevzw and it wont recognize my SIM card. Then tried Resurrection Remix and same thing, shows no SIM card. Cant find any solutions anywhere and need some guidance.
Click to expand...
Click to collapse
Flash this in TWRP either before or after flashing the rom zip, it doesn't matter: WipeTelephonyProviderData.zip

I don't ask for ETAs and my intention is not to force any release but will officiall lineage OS for the Note 4 will come in general some day?

Good News Guys >>>>Official T-Mobile Galaxy J7 Android 7.1.1 Nougat update released

Good News Guys >>>>Official T-Mobile Galaxy J7 Android 7.1.1 Nougat update released
We reported recently that the Galaxy J7 might soon receive the Nougat update. The handset was spotted at the Wi-Fi Alliance running a Nougat build. It was a big indication that the company was planning on rolling out the update soon.
T-Mobile has now started rolling out the Android 7.1.1 Nougat update for the Galaxy J7. It’s one of the few devices that Samsung has updated straight to version 7.1.1 from Marshmallow.
T-Mobile Galaxy J7 Android 7.1.1 Nougat Update
T-Mobile has started rolling out the Nougat update for the Galaxy J7 over-the-air. However, the company’s support document for this handset is all over the place. It assigns version number Android 6.0.1, Android 7.0 and Android 7.1.1 to one single firmware version, J700TUVU3BQI5.
This is obviously not possible. Clearly, there are clerical issues with the document. That doesn’t mean the T-Mobile Galaxy J7 Android 7.1.1 Nougat update isn’t rolling out. Those who own this handset on T-Mobile will soon receive an update notification if they haven’t already.
This firmware is also available for download from our firmware section where the Android version is accurately mentioned as Android 7.1.1 Nougat. Despite the fact that this update has been released in October, it comes with the August security patch.
Galaxy J7 owners on T-Mobile can either wait for the update to go live in their region or simply download the firmware from our website.
Download 7.1.1 here and happy flashing J700TUVU3BQI5 - Galaxy J7 SM-J700T TMB USA (T-Mobile)
Click here
Source :- SamMobile

Tmobile received the update from samsung on 8/28. They filled it with their garbage and sent it last thursday, most of us flashed aqf1 stock and got it ota friday morning.i dont see any clerical errors or anything like that at all. And ive been digging through the build for a week. Im running it now. All internation j7 roms flash with this builds kernel, but reboot in the setup wiz, so once we get a good base there will be a ton of ports in this community. Also, we have found, edge screen, blf, high performance mode, and aod hidden but inactive in the phone. This build is something amazing folks.
Btw, sammobile is a useless, slow dinosaur. Updato via playstore is the best source for firmware.

fullofhell said:
Tmobile received the update from samsung on 8/28. They filled it with their garbage and sent it last thursday, most of us flashed aqf1 stock and got it ota friday morning.i dont see any clerical errors or anything like that at all. And ive been digging through the build for a week. Im running it now. All internation j7 roms flash with this builds kernel, but reboot in the setup wiz, so once we get a good base there will be a ton of ports in this community. Also, we have found, edge screen, blf, high performance mode, and aod hidden but inactive in the phone. This build is something amazing folks.
Btw, sammobile is a useless, slow dinosaur. Updato via playstore is the best source for firmware.
Click to expand...
Click to collapse
I would like to have the edge screen without installing a Rom you think is possible?.

carlosbalbuena_ said:
I would like to have the edge screen without installing a Rom you think is possible?.
Click to expand...
Click to collapse
Not sure. It isnt working yet.

Will this work for the metro pcs variant ( SM-J700T1) as well?

hightech316 said:
Will this work for the metro pcs variant ( SM-J700T1) as well?
Click to expand...
Click to collapse
I think so..i got edge lighting to work. Im writing each csc tweak down and will include them in our next build.see photo,.this is native in the stock firmware

Has anyone flashed this update on their metro J7?
Does this update contain t-mobile bloat?

hightech316 said:
Has anyone flashed this update on their metro J7?
Does this update contain t-mobile bloat?
Click to expand...
Click to collapse
flash the aqf1 metro firmware, then take update to 7.1.1 ota. Then u will have metro nougat

fullofhell said:
Not sure. It isnt working yet.
Click to expand...
Click to collapse
And the Performance mode got it by installing some application or what?

carlosbalbuena_ said:
And the Performance mode got it by installing some application or what?
Click to expand...
Click to collapse
Download csc editor by wanam via playstore its in one of those...u look thru and change each item to "true" then reboot. Its called performance tuning

fullofhell said:
Download csc editor by wanam via playstore its in one of those...u look thru and change each item to "true" then reboot. Its called performance tuning
Click to expand...
Click to collapse
Ok bro I'm going to try and the edge lighting like it did

I got the stock ROM deodex and services jar modded but when I connect it to my lab top it don't come up unless I go and turn off USB debugging

mario1634 said:
I got the stock ROM deodex and services jar modded but when I connect it to my lab top it don't come up unless I go and turn off USB debugging
Click to expand...
Click to collapse
This firmware is being a arsehat for me too.

When I flashed the original boot img. Now my lab top able to see my phone. It crazy because I can still pull and push but programs like assayyed don't see it until I flash stock boot img

mario1634 said:
When I flashed the original boot img. Now my lab top able to see my phone. It crazy because I can still pull and push but programs like assayyed don't see it until I flash stock boot img
Click to expand...
Click to collapse
Weird af

fullofhell said:
flash the aqf1 metro firmware, then take update to 7.1.1 ota. Then u will have metro nougat
Click to expand...
Click to collapse
Great, thanks!
Once I have time I'll upload a rooted nandroid

Safe to flash through TWRP while rooted with xposed? Or should I disable xposed and uninstall root? Also, should I wipe when flashing or does it matter

phoen1x74 said:
Safe to flash through TWRP while rooted with xposed? Or should I disable xposed and uninstall root? Also, should I wipe when flashing or does it matter
Click to expand...
Click to collapse
U cannot in any capacity flash a stock firmware with twrp.u have to wipe your whole phone and go to download mode and flash the firmware via odin. Dont forget to unzip the file first so u have the unzipped form of it loaded in the ap slot

Aight I'm chill (no way at all to update without wiping my phone?) Like what if I don't wipe and flash in odin; will that lead to problems?

phoen1x74 said:
Aight I'm chill (no way at all to update without wiping my phone?) Like what if I don't wipe and flash in odin; will that lead to problems?
Click to expand...
Click to collapse
U could if u werent rooted or had twrp installed..if u dont wipe before odin, it will prob fail until u wipe it honestly.