yashsingh1/xdaforums huggingface dataset:
[Galaxy Tab Pro 12.2, 10.1, 8.4 Android Development] namlas:
Trying to upgrade from cm12.1, but I keep getting a black screen after the initial Samsung logo shows. I flashed the lollipop bootloader, and I'm on the latest TWRP from the official site. I tried full wipe, factory reset, etc.

Tried one of the Feb releases, and latest available.

Also seeing black screen with 13.0 rom.

Has anyone else run into this?
[Galaxy Tab Pro 12.2, 10.1, 8.4 Android Development] guidol:
How long did you leave the black screen work?

After the full wipe do you flash CM14.1 + Open GApps + SuperSU 2.79?

With the latest CM14.1 LineageOS you have the problem with the initial Google-Account Setup.

Feb-Release should be OK.

Are you sure you got a Samsung SM-T900 and not a SM-P900?

After reflash with SuperSU there are 1-2 Minutes of Black screen while rooting (after the Samsung Logo)

You could also try the TWRP-Recovery-Imagge from ThomPatry which should be available in the first posts of this thread.

see:

3 ----I have built a new version of TWRP with the MM kernel. MTP, Vibations, ADB now work and there are performance increases. Link

https://drive.google.com/drive/folders/0BxqoBZiUYroBZ0tmbXg2ampBb1U?usp=sharing
[Galaxy Tab Pro 12.2, 10.1, 8.4 Android Development] namlas:
Yes, it's an SM-T900. I checked again just now to make sure. I had let the tablet sit around overnight after the LOS14.1 install, yesterday.

I was not installing supersu -- I will try that now. I usually do the rom, supersu, and gapps separately to make sure the device is booting up after each step.
[Galaxy Tab Pro 12.2, 10.1, 8.4 Android Development] guidol:
Your actual TWRP (for v2awifi) is 3.0.2.0 from

https://eu.dl.twrp.me/v2awifi/ ? Or from the first page of this thread?

Did you try to check the ROM against the mdm5 checksum or using the mdm5 checksum while flashing the rom?

Are there any error-messages while flashing?

Are you completely sure that the Lollipop-Bootloader is flashes correctly?

I had to flash him twice - therefore I also got a bootloop with a black screen - and Iam wasnt the only one.

So firstly retry to reflash the Lollipop Bootloader (with Odin)

from thr first page: "You need to make sure you have a Lollipop bootloader installed or else your device won't boot."
[Galaxy Tab Pro 12.2, 10.1, 8.4 Android Development] namlas:
I tried the recovery from the first page here, as well as the main twrp site. Another strangeness I noticed is that if I let the device sit in recovery, it seems to crash and restart on its own and goes back into recovery; whether there's an operation going or not. This happens with twrp 3.1, and 3.0.x; 2.80 works fine. All saved twrp settings also seem to get lost, occasionally.

The only errors which I saw during flash was after a full device erase (system, data, dalvik, user data); the error message complained about some log command not being found.

Just so I'm not being dumb, is v2awifi the same device as v2wifixx? This is the rom that I was using before: "cm-12.1-20150808-UNOFFICIAL-v2wifixx.zip", and reflashing that still works fine. Device booted up, I went through the setup, etc., and everything was normal. I tried a google search, and also did a search in this thread, and it appears that sm-t900 is referred to as v2awifi. My bootup Samsung logo also shows SM-T900 on it.

Flashing the lineage 13.1, or 14.1 rom still just gives me a blank screen. I've tried twrp 3.1, and 3.0.2 both, but the end result is still the same. It doesn't even get far enough into the boot process to show the lineage logo, or allow me to gather any logs, so I'm quite lost and stuck.

And, I tried to flash the bootloader a few times through Odin. No errors on any attempt. Write completed successfully, and unit rebooted after.
[Galaxy Tab Pro 12.2, 10.1, 8.4 Android Development] namlas:
Okay - finally it's working. I'm not sure what exactly was broken internally, but here's what I had to do, in case anyone else runs into the issue:

1) Flashed back to stock 5.1.1 image from samsung; installed via odin. For me, even stock image was not booting. I'd get the initial samsung logo at device power on, and then nothing.

2) Boot into stock recovery, and do a factory reset, and erase cache partition (basically, erase/format everything you have an option for)

3) Reflash stock 5.1.1 image via odin

4) Reboot device and verify OS starts

5) Flash latest twrp via odin (was 3.1 as of this night)

6) Flash the lineage 14.1 ROM from first page

7) Wipe dalvik/cache

8) Reboot

Booted up fine after this.
[Galaxy Tab Pro 12.2, 10.1, 8.4 Android Development] guidol:
Thats fine :) Thank you also for the informations about the install steps!
[Galaxy Tab Pro 12.2, 10.1, 8.4 Android Development] Theshowx:
Can someone please help me create lineage os for the samsung sm-t670n its stuck on 5.1.1 it need major help id pay to get up and im sure others would be willing to if the thread gets put up ill pledge 20 dollars to start it os 14 would be nice. Someone started os 13 but closed the thread. They couldnt get wifi working. Please maybe [MENTION=3203856]thompa[/MENTION]ntry could help him. Anybody please.
[Galaxy Tab Pro 12.2, 10.1, 8.4 Android Development] c19932:
I am currently on the latest build. I notice that whenever I have auto brightness on, when I first turn on the screen, it always starts at very low brightness and takes 1-2 sec to readjust to the appropriate brightness. Is anybody else experiencing this? Thank you
[Galaxy Tab Pro 12.2, 10.1, 8.4 Android Development] pl_blaze:
I've created TWRP 3.1.1-0 image (using omni android-7.1 branch with default kernel that i slimmed down due to size constraints of the recovery partition) with f2fs filesystem support and have successfully used f2fs mounted on /cache for now in my test rom. I had to modify the fstab flags to get it working. If anyone is interested in testing the twrp image i could share it....just let me know.
[Galaxy Tab Pro 12.2, 10.1, 8.4 Android Development] TheArtfulPenguin:
Yes I noticed the saMe thing.
[Galaxy Tab Pro 12.2, 10.1, 8.4 Android Development] seeker9:
Latest Device Builds link is dead.

Edit: its back up now.
[Galaxy Tab Pro 12.2, 10.1, 8.4 Android Development] guidol:
with the LineageOS build from the 20.05.2017 and the "new" flashable .zip of SuperSU V2.81 the root function doesnt work in the FileManager EFS.

I didnt get the problem with V2.79 of SuperSU - so back to V2.79
[Galaxy Tab Pro 12.2, 10.1, 8.4 Android Development] kb8no:
[MENTION=3630898]guidol[/MENTION] or anyone. Anyone have experience with addonSU from LOS on this ROM? There is a download link on the OP suggesting endorsement. As I understand it, it was initially glitchy and people bypassed it for SuperSU. I think it has been refined now. I used it on my HTC One and it worked fine. An advantage is that it sticks and you don't have to flash addonSU every time you flash an update ROM.

---------- Post added at 07:25 AM ---------- Previous post was at 07:01 AM ----------

On 20.05.2017 I had already updated to 2.81 on Play Store. My super user is working fine on Root Explorer, Deathlyaudiotor, and Titanium. Reading on the Play Store documentation they said that 2.80 lost root and hence the release of 2.81 to fix the regression.

---------- Post added at 07:40 AM ---------- Previous post was at 07:25 AM ----------

Addendum: addonSU from Lineage is working just fine on this ROM. I have been happy with it before so I think I will stick with this for now.
[Galaxy Tab Pro 12.2, 10.1, 8.4 Android Development] guidol:
Some time in the past I did try the addonSU - but at this time it didnt work. After that I did use SuperSU without no problems.... so I didnt checked for a new version of addonSU - because I didnt read about a successful usage of this.

Now I can test it....

DiId you use https://mirrorbits.lineageos.org/su/addonsu-arm-signed.zip

the Version for LineageOS 14.1 from the 26.01.2017?
[Galaxy Tab Pro 12.2, 10.1, 8.4 Android Development] kb8no:
My file is not dated so I am not sure. What I am sure about is that I just clicked on the link on the OP and that takes you to the LOS download page which is the latest version, whatever that may be. It works just fine and I'll stick with it. As I said, you only need to flash it once so the next time you update a nightly all you need to do is flash the ROM.
[Galaxy Tab Pro 12.2, 10.1, 8.4 Android Development] guidol:
The version which I did wrote in the last post is the latest version today for normal ARM (non 64bit) and LOS 14.1 and is the original download-link from the page which the OP told us.

I did test it now on my SM-T900 and it works now - also with the EFS as root-Explorer :)

Many Thanks for that information!

EDIT:

I was a bit confused, because I got a Samsung Note2 GT-N7100 with LineageOS and there SU is integrated because the Development/Device-Tree seems different and addonSU isnt working (so the author is integrated) - later if it would work with the Note2 then addonSU will be used.

And my Nexus 10 does use PureNexus so only SuperSU (Pro version integrated) will work there and not addonSU. So for my devices it will only work on the SM-T900.
[Galaxy Tab Pro 12.2, 10.1, 8.4 Android Development] kb8no:
My official LineageOS Nougat for my HTC One M8 uses addonSU. I have unofficial LineageOS Nougat on my Samsung tab3 which is unusual because it is Intel Atom x86. But, same thing there, SU remains integrated like CM. OP intends to mainstream this unofficial ROM into official Lineage and will eventually use addonSU when he makes the move.
[Galaxy Tab Pro 12.2, 10.1, 8.4 Android Development] LegendAssassinF:
Does anyone have better instructions? This is my first time flashing a device and instructions that say "Flash Lineage" don't really help a new person who has no clue how to do that.
[Galaxy Tab Pro 12.2, 10.1, 8.4 Android Development] AchillesTheGod:
Still having this issue
[Galaxy Tab Pro 12.2, 10.1, 8.4 Android Development] c19932:
don't really have the time to give you detailed instructions, but here are the general steps:

1) unlock your bootloader (is this part necessary for samsung devices? i forgot)

2) install TWRP (I believe you have to do this through Odin; TWRP is a custom recovery)

3) download this rom. put the zip file into your internal storage. boot into TWRP and flash this rom. (on way to boot into your custom recovery is to turn on your device while holding down the hardware home + volume up (or down....it's one or the other ) buttons)

4) flash the gapp package if you would like (gapp package contains all the google apps like google play, google maps, hangouts, etc)

I am assuming that this is your first time flashing custom roms so you would probably have to google how to do each individual step above. But trust me. this rom is well worth it. On this device, Nougat is 2x faster than the stock rom or any previous versions of android. This rom makes my tab 12.2 feels like a new device, especially after overclocking
[Galaxy Tab Pro 12.2, 10.1, 8.4 Android Development] kb8no:
Anybody else notice increasing drops / flashes in the in the screen. Turns black and flickers about the speed of a blink of the eye. It is very annoying. The flashes don't last long enough to interfere with it being functional. I'm using 5/27 weekly but I have been noticing this for some time but seemingly worse with this version.
[Galaxy Tab Pro 12.2, 10.1, 8.4 Android Development] guidol:
the 2-3 last releases I did some some black bit-striped lines sometimes - but also only for "the speed a blink of the eye".

I dont know if it is on a special moment of use...

I got 5/27 since yesterday and didnt see since then such a stripe....but I didnt get it very often with the releases before the 5/27.

I would say I did see it less than 0,5% as of my daily use - but some monts ago it wasnt there.
[Galaxy Tab Pro 12.2, 10.1, 8.4 Android Development] Young Gunna:
Does this happen mainly at night or in a dark room? Could it be your screen starting to fail and flicker.
[Galaxy Tab Pro 12.2, 10.1, 8.4 Android Development] kb8no:
Great question. It is intermittent. Seemed worse with Chrome. I installed and re-installed it twice and it began to behave. It was on battery and resolved when plugged in. I need some time to get my head around it.
[Galaxy Tab Pro 12.2, 10.1, 8.4 Android Development] kb8no:
I seem to have fixed this and some other seemingly unassociated issues by a full wipe and clean flash.
[Galaxy Tab Pro 12.2, 10.1, 8.4 Android Development] godrick15:
What adiutor settings is everyone using? I need recommendations.

I mostly browse with Chrome, 10 or more tabs opened ,YouTube monster. I do not game at all. I enjoy watching live streams and movies. I want snappy speed and im not concerned too much about battery
[Galaxy Tab Pro 12.2, 10.1, 8.4 Android Development] JCordero31:
could someone please post the pit file for me? My wife bricked her tab pro trying to install twrp and checked re partition. TY anyone who does.
[Galaxy Tab Pro 12.2, 10.1, 8.4 Android Development] TheArtfulPenguin:
Updated to latest build and now the back button and recent apps buttons dont light up. Just for my tablet or everyone?
[Galaxy Tab Pro 12.2, 10.1, 8.4 Android Development] guidol:
Now as you did wrote it - YES they doesnt light up on my Tablet with the latest build 20170603
[Galaxy Tab Pro 12.2, 10.1, 8.4 Android Development] enefes:
Hi, how could we transfer data from PC to the tablet or to the SD?
[Galaxy Tab Pro 12.2, 10.1, 8.4 Android Development] toolhas4degrees:
try turning off dubugging in dev options before connecting to pc
[Galaxy Tab Pro 12.2, 10.1, 8.4 Android Development] qasq:
SOLVED - use 3.0.2.0 - flash with ODIN or TWRP, doesn't matter.

Hello, I need help with recovery installation, on similar model 12.2 but Note Pro, not Tab Pro. I belive things are simmilar, and maybe you could help me out, as that device is quite old now, and people on that forum are almost "not there" anymore, so I'm stuck with the issue, but would like to move on..

Here's my post :

Hi,

I bought almost not used, 12.2 for 200$, LTE, 32GB.

It's on 5.0.2

I have experience with many Samsung phones, but this gives me a headache.

I was able to root with chainfire, I have SuperSU installed and working.

I was able to flash old TWRP, number 2.8.0.0

__________________________________________________ ___________

I can't flash anything newer than 2.8.0.0 as it enters "entering recovery" bootloop.

I can't flash update to 3.0.0.0 as it doesn't come with *.zip file so I could do it in recovery.

I can't flash 2.8.7.0 zip from recovery, as I get "Failed"

Do I have to update bootloader for newer TWRP to work with?

How can I install Lineage, as flashing it fails also from 2.8.0.0 (I belive this twrp is too old, partition details are wrong or some permissions)

I now own S7Edge, I was using Galaxy: S, S2, S3, Note, Note 3, Note 4, S6Edge+... Never had such issues. Maybe it's that P905 is a device from Note 3 era, and my current knowledge is on pair with S7? Maybe back then we were doing things diffrently and I forgot? Please be so kind to help me out here.

Best regards!

____________

edit:

So I thought to myself, why not to try and flash via odin, some newer versions of TWRP.

I was able to flash 2.8.4 and than 2.8.5.

I was still able to boot into recovery, so I went out and flashed 3.1.1, but last one is no go.

I than reflashed 2.8.7.

So this one is my current, and top one I can boot into. What is diffrent with 3.0? Im not sure, but assistance is needed !

For now it doesn't matter if I flash 3.0 from Odin or from "TWRP android manager", it will enter bootloop, and I have to go back into Download mode and than flash 2.8.7 as only that one works.... What can that be?
[Galaxy Tab Pro 12.2, 10.1, 8.4 Android Development] guidol:
Hmm.... the Samsung Galaxy 12.2 Note Pro seems to be the P905.

For the P905 there is a own Thread, which seems quite alive:

https://xdaforums.com/galaxy-note-p...-cyanogenmod-14-0-android-7-0-nougat-t3476335

Latest Build

LineageOS Builds:

13: 20170606: june security patch

Last Message from the 07.06.2017

TWRP for SM-905

https://twrp.me/devices/samsunggalaxynotepro122qcom.html

https://dl.twrp.me/viennaltexx/

https://dl.twrp.me/viennaltexx/twrp-3.1.1-0-viennaltexx.img

Did you try to install the latest TWRP via a older TWRP?

Go to install, right lower corner, install Image (.img) then select twrpxxxx.img and select recovery to select in the recovery partition.

Or did you ever install TWRP via .zip only?

If you got root on your device you could also use the App "Flashify" which can also upgrade your TWRP to the latest version (did use this sometimes)
[Galaxy Tab Pro 12.2, 10.1, 8.4 Android Development] kb8no:
Here is a note for any of you who have been caught TWRP sleeping like me. Our original Tab Pro TWRP 3.0.2-0 was made by thompatry. He is now the official TWRP maintainer. I looked today and 3.1.1-0 by thompatry is available on the TWRP download page if you want to upgrade. Using 3.1 will get rid of the red "unknown" error message when you flash a Nougat ROM.

I could not get our original TWRP 3.0.2-0 to flash the 3.1.1-0 img file. Some error message about this is "not a directory". It flashed just fine using the tar file with Odin. I then tried to re-flash the img file using the new TWRP and it flashed fine so it must be a bug in the old one.

Also, a reminder that the SU from Lineage addonsu works fine now. I like it because it sticks and you do not need to flash it with every upgrade. I upgraded today with the 2017-06-10 by simply flashing the ROM. No wipe, no gapps, and no SU flash were needed. I like that.
[Galaxy Tab Pro 12.2, 10.1, 8.4 Android Development] JCordero31:
could anybody please do me the favor of posting the PIT File please and thank you. for the t900
[Galaxy Tab Pro 12.2, 10.1, 8.4 Android Development] guidol:
The file at the TWRP download-page is from the 18.05.2017. Is this the version from thompatry? Because this version I did already install.

https://dl.twrp.me/v2awifi/twrp-3.1.1-0-v2awifi.img
[Galaxy Tab Pro 12.2, 10.1, 8.4 Android Development] kb8no:
Yes. You have been more observant than me. This is the same one. If you read the TWRP page it says Thompatry is the maintainer. I have been watching the OP and failed to check the TWRP site for the latest TWRP.
[Galaxy Tab Pro 12.2, 10.1, 8.4 Android Development] guidol:
Ahh - yes - there it is ;)

https://twrp.me/devices/samsunggalaxytabpro122exynoswifi.html

Status:
Support Status: Current
Maintainer: thompatry
Code Name: v2awifi
[Galaxy Tab Pro 12.2, 10.1, 8.4 Android Development] c19932:
I was wondering if anybody is able to get miracast / casting working? I tried it with 2 of my TVs (samsung and hisense) and neither worked. It would try to connect but never actually establish a connection. Sometimes a prompt would pop up on the tab asking if I wanna connect, but pressing yes does nothing.
[Galaxy Tab Pro 12.2, 10.1, 8.4 Android Development] TheArtfulPenguin:
This is now working in the lineage-14.1-20170610-UNOFFICIAL-v2awifi.zip build.

---------- Post added at 01:05 AM ---------- Previous post was at 12:53 AM ----------

Do you have a VPN running. I use a couple different casting apps. In most the TVs and my chrome cast show up even with my VPN up, but they won't connect until I exit the VPN.
[Galaxy Tab Pro 12.2, 10.1, 8.4 Android Development] Theshowx1:
Could anybody please post the pit file for this device? T900
[Galaxy Tab Pro 12.2, 10.1, 8.4 Android Development] kb8no:
I extracted it. Can't upload this file type on XDA. If you still want it I guess let me know here and then pm me.
[Galaxy Tab Pro 12.2, 10.1, 8.4 Android Development] Theshowx1:
I private messaged for it.
[Galaxy Tab Pro 12.2, 10.1, 8.4 Android Development] JCDinPGH:
Wow. It is very nice to see love for this tablet. I will definitely be trying this out when I have some time.

Has anyone tried installing any apps that check for root and then will not install or will exit with an error if root is detected?

Anyone tried Magisk to mask apps so they will run if root is enabled?

The one app that seems very problematic is Mario Run but I am sure there are others also. I tried Magisk on my tablet with the latest stock rooted firmware but if I remember correctly, the OS level was too old for Magisk to work.

I just wondered if toggling root in the developer options would enable apps that detect root to run correctly. I will try on my own also and post back once I actually install this ROM.
[Galaxy Tab Pro 12.2, 10.1, 8.4 Android Development] JCDinPGH:
I installed and it works flawlessly. I disabled root in the developer options and was hoping it would allow apps with root detection to run but no luck. Still very happy with a great new ROM.
[Galaxy Tab Pro 12.2, 10.1, 8.4 Android Development] JCDinPGH:
Anyone had any luck getting this ROM to pass safetynet? I keep getting "CTS Profile mismatch". I've tried magisk and phh supersu.
[Galaxy Tab Pro 12.2, 10.1, 8.4 Android Development] JCDinPGH:
After a lot of reading and some trial and error, I was able to get Super Mario Run to work correctly which means it correctly is bypassing safetynet. I had to completely uninstall supersu and then install the lastest beta (v13) of Magisk and then use Magisk Manager to hide Super Mario Run. I highly suggest you make a good TWRP backup before trying any of this though.
[Galaxy Tab Pro 12.2, 10.1, 8.4 Android Development] Faz1980:
Do Lineage ROMs have working ethernet over USB?
[Galaxy Tab Pro 12.2, 10.1, 8.4 Android Development] mrhds:
The download link isn't working (download.exynos5420.com). [MENTION=4817899]thompatry[/MENTION] would have a chance to look into it? Or post a new link to the latest v2awifi ROM? Thanks!
[Galaxy Tab Pro 12.2, 10.1, 8.4 Android Development] RedWingsFanEd:
Working now with latest update. I installed with no problems.
[Galaxy Tab Pro 12.2, 10.1, 8.4 Android Development] mbl1979:
Do we need to reflash gapps when we update?
[Galaxy Tab Pro 12.2, 10.1, 8.4 Android Development] MP2005:
No
[Galaxy Tab Pro 12.2, 10.1, 8.4 Android Development] blanquitoman1984:
How to update

I am running Lineage OS on my Nexus 5, I can manually check and install updates via the update tab. I would like to do it also on my Pro 12.2. I get a error "The update check failed. Please check your internet connection and try again later". I know the Wifi is working, the only strange thing I see is the last checked update date is December 31, 1969. Any help or suggestions would be truly appreciated. I'm sorry if this question has been asked before, Thank you in advance for your help.
[Galaxy Tab Pro 12.2, 10.1, 8.4 Android Development] floppo:
I have this problem again with the builds 20170624 and 20170701.
[Galaxy Tab Pro 12.2, 10.1, 8.4 Android Development] shima_momy:
Anyone else having issue with the Night mode from LiveDisplay?? I have set it to Automatic and it doesn't seem to work.
[Galaxy Tab Pro 12.2, 10.1, 8.4 Android Development] nutpants:
Does this rom support v2wifi?

My sm-t900 fails to flash saying v2wifi wrong device..

In getting confused over device names that have the same model number
[Galaxy Tab Pro 12.2, 10.1, 8.4 Android Development] toolhas4degrees:
should be v2wifixx if you were on the latest lollipop build before going custom
[Galaxy Tab Pro 12.2, 10.1, 8.4 Android Development] nutpants:
I was on kit Kat last..

Did they change the name in lollipop?
[Galaxy Tab Pro 12.2, 10.1, 8.4 Android Development] kb8no:
They did indeed change the name. It is convoluted.
[Galaxy Tab Pro 12.2, 10.1, 8.4 Android Development] guidol:
Here also the same with 20170701....
[Galaxy Tab Pro 12.2, 10.1, 8.4 Android Development] kb8no:
Same problem here, the lights on the buttons don't light up.
[Galaxy Tab Pro 12.2, 10.1, 8.4 Android Development] TheArtfulPenguin:
I wonder if it is a build.prop setting.
[Galaxy Tab Pro 12.2, 10.1, 8.4 Android Development] TheArtfulPenguin:
Not a build.prop issue. I saved the before, back & recent app buttons light working, and then saved a version after where they did not light up. Did a Diff-merge to compare the two. No setting differences. Only differences were a few version numbers.

---------- Post added at 10:12 AM ---------- Previous post was at 10:09 AM ----------

Also someone said I wouldn't have to re-run the root zip installer in TWRP. I still had to. Did I read wrong?