[ROM][SM-T900] CyanogenMod for Tab Pro 12.2 SM-T900 (v2wifixx)

Search This thread

kb8no

Senior Member
Jan 29, 2012
1,213
301
Duluth MN
I finally rooted my t900 with the UE firmware. I'm preparing to install CM. I installed TWRP 2.8.7 tar wifixx from a TWRP download using Odin which worked fine. Then I tried to flash all three of the TWRP 3.0 versions and they all boot looped. Anybody else had this experience? Seems odd that the official TWRP builds don't work.
 

risant

Senior Member
Aug 6, 2016
294
31
T900

What'a the solution for random freeze on cm 12.1 I have tried all the solution but to no avail ...I reinstalled the Samsung 5,11 stock rom no random freeze ... please help
 

patt2k

Senior Member
Mar 22, 2009
3,390
546
My apologies if I didn't find what I was looking for. Is there a thread with instructions how to install TWRP on T900? I only found some videos of people already running it. Anyone willing to point me in right direction?
 

kb8no

Senior Member
Jan 29, 2012
1,213
301
Duluth MN
My apologies if I didn't find what I was looking for. Is there a thread with instructions how to install TWRP on T900? I only found some videos of people already running it. Anyone willing to point me in right direction?
I was struggling as well. See my post 2 above yours. I figured it out today. Most of what you can Google for rooting and installing the custom recovery TWRP is from ROM's before Lollipop and my device came from EBay already with the Lollipop OTA installed. This T900 unit is called v2wifi but there are 2 main firmware variants, v2wifiue (North America) with firmware T900UEUBOJ1 and v2wifixx (Europe) with firmware T900XXUBPA1. It makes a difference which firmware you have. Since my OTA came from the US my OTA had the UE firmware. I was able to use CF auto root with Odin for v2wifiue. However, TWRP only has a v2wifixx version. I found that 2.8.7.0-v2wifixx worked with UE even though it was the wrong version but that 3.0 boot looped. I could only recover from the bootloop by using Odin to install the UE firmware again.

Then I thought that maybe the problem is that UE is non-standard and that XX is the standard firmware. So I got back to UE with TWRP-v2wifixx 2.8.7.0 where I was before the boot loop. I did a complete wipe and used Odin to flash the XX firmware. Then I used CF auto root with ODIN for the v2wifixx. Everything worked so far. TWRP has a 2.8.7.0-wifixx offered as a tar (all the 3.0 are img onlly files). So I used Odin to flash 2.8.7.0-wifixx. I then booted into TWRP and used TWRP to flash the latest 3.0 img.

BAM. JOY. T900 with v2wifixx firmware, rooted with SuperSU, and with TWRP 3.0. Grab the firmware from Sammobile, TWRP from their download site, and CF auto root from his site. It goes without saying to have USB debugging enabled., never to allow TWRP to install Super User, and allow TWRP to modify the system.

Now, if someone could explain to me why we need a P900 TWRP to install P900 CM 13 I could be much smarter than I am now. I can't see why the T900 TWRP 3.0 v2wifixx version wouldn't flash P900 CM 13. I want to try CM 13 next. Anybody?
 
  • Like
Reactions: djd338

patt2k

Senior Member
Mar 22, 2009
3,390
546
I was struggling as well. See my post 2 above yours. I figured it out today. Most of what you can Google for rooting and installing the custom recovery TWRP is from ROM's before Lollipop and my device came from EBay already with the Lollipop OTA installed. This T900 unit is called v2wifi but there are 2 main firmware variants, v2wifiue (North America) with firmware T900UEUBOJ1 and v2wifixx (Europe) with firmware T900XXUBPA1. It makes a difference which firmware you have. Since my OTA came from the US my OTA had the UE firmware. I was able to use CF auto root with Odin for v2wifiue. However, TWRP only has a v2wifixx version. I found that 2.8.7.0-v2wifixx worked with UE even though it was the wrong version but that 3.0 boot looped. I could only recover from the bootloop by using Odin to install the UE firmware again.

Then I thought that maybe the problem is that UE is non-standard and that XX is the standard firmware. So I got back to UE with TWRP-v2wifixx 2.8.7.0 where I was before the boot loop. I did a complete wipe and used Odin to flash the XX firmware. Then I used CF auto root with ODIN for the v2wifixx. Everything worked so far. TWRP has a 2.8.7.0-wifixx offered as a tar (all the 3.0 are img onlly files). So I used Odin to flash 2.8.7.0-wifixx. I then booted into TWRP and used TWRP to flash the latest 3.0 img.

BAM. JOY. T900 with v2wifixx firmware, rooted with SuperSU, and with TWRP 3.0. Grab the firmware from Sammobile, TWRP from their download site, and CF auto root from his site. It goes without saying to have USB debugging enabled., never to allow TWRP to install Super User, and allow TWRP to modify the system.

Now, if someone could explain to me why we need a P900 TWRP to install P900 CM 13 I could be much smarter than I am now. I can't see why the T900 TWRP 3.0 v2wifixx version wouldn't flash P900 CM 13. I want to try CM 13 next. Anybody?

the tablet is on 5.1.1 with build number: LMY47X.T900UEUBOJ1. I am assuming it's running EU firmware.

EDIT: when I flash TWRP and then I enter recovery mode it always goes to stock recovery for some reason. I'll try CF AUTO root then flash recovery w/ root and TWRP app.
 
Last edited:

kb8no

Senior Member
Jan 29, 2012
1,213
301
Duluth MN
the tablet is on 5.1.1 with build number: LMY47X.T900UEUBOJ1. I am assuming it's running EU firmware.

EDIT: when I flash TWRP and then I enter recovery mode it always goes to stock recovery for some reason. I'll try CF AUTO root then flash recovery w/ root and TWRP app.

No. UE is the North America firmware as I said in my post. You need the XX European firmware. If you are not rooted you cannot install a custom recovery (TWRP). You must use the correct CF auto root for your firmware. I advise you Odin the XX firmware and then Odin the v2wifixx CF auto root. Then you can install TWRP 3.0 for v2wifixx however you want to do it. Read my post carefully.

BTW, I'm now using Tapatalk on CM12 to type this message on my T900. Autorotate is working fine, I was expecting a problem. I have had a few crashes with reboots as people have described but it seems to be leveling out and I haven't had enough to figure out what triggers them. I'm pretty excited.
 

patt2k

Senior Member
Mar 22, 2009
3,390
546
No. UE is the North America firmware as I said in my post. You need the XX European firmware. If you are not rooted you cannot install a custom recovery (TWRP). You must use the correct CF auto root for your firmware. I advise you Odin the XX firmware and then Odin the v2wifixx CF auto root. Then you can install TWRP 3.0 for v2wifixx however you want to do it. Read my post carefully.

BTW, I'm now using Tapatalk on CM12 to type this message on my T900. Autorotate is working fine, I was expecting a problem. I have had a few crashes with reboots as people have described but it seems to be leveling out and I haven't had enough to figure out what triggers them. I'm pretty excited.

This is the way I did install TWRP. Use CF Auto Root and then flash TWRP. But it's giving me error executing update binary in zip.

is TWRP 3.0 needed to flash? i installed 2.8.7.1 but i'll try 3.0 now.
 

kb8no

Senior Member
Jan 29, 2012
1,213
301
Duluth MN
This is the way I did install TWRP. Use CF Auto Root and then flash TWRP. But it's giving me error executing update binary in zip.

is TWRP 3.0 needed to flash? i installed 2.8.7.1 but i'll try 3.0 now.
humm... 2.8.7.1 works. You don't need 3.0 (but you want it) so don't mess with it now. Did you Odin flash the XX firmware from Sammobile? Where do you get the execute binary error, in Odin? I did one thing at a time and then booted into ROM. 1. flash XX firmware 2. flash CF auto root. Get that to work first. Open SuperSU after you booted from CF auto root. Do you now have a rooted ROM? (Worry about TWRP after you have these accomplished.)
 

patt2k

Senior Member
Mar 22, 2009
3,390
546
humm... 2.8.7.1 works. You don't need 3.0 (but you want it) so don't mess with it now. Did you Odin flash the XX firmware from Sammobile? Where do you get the execute binary error, in Odin? I did one thing at a time and then booted into ROM. 1. flash XX firmware 2. flash CF auto root. Get that to work first. Open SuperSU after you booted from CF auto root. Do you now have a rooted ROM? (Worry about TWRP after you have these accomplished.)

I get that in TWRP when trying to flash the rom. And no I didn't install the EU rom. I just did it the current one (yea I know I read what you wrote) if TWRP 3.0 won't work i'll do that, you mind giving me link to the firmware that you used from sammobile?
 

kb8no

Senior Member
Jan 29, 2012
1,213
301
Duluth MN
I get that in TWRP when trying to flash the rom. And no I didn't install the EU rom. I just did it the current one (yea I know I read what you wrote) if TWRP 3.0 won't work i'll do that, you mind giving me link to the firmware that you used from sammobile?
Well, to the best of my weak abilities, if you don't care about TWRP 3.0, the TWRP 2.7 should work even you are installing a v2wifixx TWRP on a v2wifiue ROM. I'm thinking these two ROM's have slightly different kernels which is why they need different TWRP and CF auto root (as close as they are). I did not try go install CM12 until I figured out the XX ROM and installed it and then rooted it with the CF for XX and installed TWRP for XX so I can only guess at your problem. Just Google sammobile, it's the first hit. You have to register for an "account" for free and free takes an hour but the price is right.

I'm like you, since the TWRP 2.7 for xx doesn't boot loop and appears to work it should be able to flash CM12. Heck, the guys are using a TWRP from from the P900. But I can only tell you what worked for me and make assumptions. I do not find any of this discussion we are having anywhere so I hope somebody else reads this and benefits and adds some knowledge.

I do assume you booted the ROM and opened SuperSU before you tried to flash CM 12 and you wiped in TWRP before you installed.
 

patt2k

Senior Member
Mar 22, 2009
3,390
546
Well, to the best of my weak abilities, if you don't care about TWRP 3.0, the TWRP 2.7 should work even you are installing a v2wifixx TWRP on a v2wifiue ROM. I'm thinking these two ROM's have slightly different kernels which is why they need different TWRP and CF auto root (as close as they are). I did not try go install CM12 until I figured out the XX ROM and installed it and then rooted it with the CF for XX and installed TWRP for XX so I can only guess at your problem. Just Google sammobile, it's the first hit. You have to register for an "account" for free and free takes an hour but the price is right.

I'm like you, since the TWRP 2.7 for xx doesn't boot loop and appears to work it should be able to flash CM12. Heck, the guys are using a TWRP from from the P900. But I can only tell you what worked for me and make assumptions. I do not find any of this discussion we are having anywhere so I hope somebody else reads this and benefits and adds some knowledge.

I do assume you booted the ROM and opened SuperSU before you tried to flash CM 12 and you wiped in TWRP before you installed.

Hmm yea i'll play around with maybe a TW modded rom and see what happens. I will also try TWRP 3.0 and let you know how it goes.

Thanks for your time! i'll get back at you.
 

jomar_uk

Senior Member
Apologies in advance if a tad off topic.

My Tab Pro 12.2 developed screen flickering when at 60 - 65%, took to Samsung support site who after 10 days told me it was a screen problem, more worrying they said they had no replacement parts to fix now or in future & I was offered a refund of purchase price or another model (I choose the new 813 tab 2) which is great *but* really miss my 12.2 screen, has anyone else heard of no more 12.2 screens being made or available please?

Shalom & many thanks, john

Sent from my SM-T813 using XDA-Developers mobile app
 
Well, to the best of my weak abilities, if you don't care about TWRP 3.0, the TWRP 2.7 should work even you are installing a v2wifixx TWRP on a v2wifiue ROM. I'm thinking these two ROM's have slightly different kernels which is why they need different TWRP and CF auto root (as close as they are). I did not try go install CM12 until I figured out the XX ROM and installed it and then rooted it with the CF for XX and installed TWRP for XX so I can only guess at your problem. Just Google sammobile, it's the first hit. You have to register for an "account" for free and free takes an hour but the price is right.

I'm like you, since the TWRP 2.7 for xx doesn't boot loop and appears to work it should be able to flash CM12. Heck, the guys are using a TWRP from from the P900. But I can only tell you what worked for me and make assumptions. I do not find any of this discussion we are having anywhere so I hope somebody else reads this and benefits and adds some knowledge.

I do assume you booted the ROM and opened SuperSU before you tried to flash CM 12 and you wiped in TWRP before you installed.

you don't need a twrp from the note to install the note rom on the tab. all that needs to be done is to edit the updater script in the note rom so it doesn't check the device to see if it is a note and fail bc it is not the correct device...
 
  • Like
Reactions: kb8no

netjetman

Senior Member
Jul 9, 2007
170
37
Apologies in advance if a tad off topic.

My Tab Pro 12.2 developed screen flickering when at 60 - 65%, took to Samsung support site who after 10 days told me it was a screen problem, more worrying they said they had no replacement parts to fix now or in future & I was offered a refund of purchase price or another model (I choose the new 813 tab 2) which is great *but* really miss my 12.2 screen, has anyone else heard of no more 12.2 screens being made or available please?

Shalom & many thanks, john

Sent from my SM-T813 using XDA-Developers mobile app

sounds to me like you have the battery connection problem. search around the site and you'll find a potential fix.
 

jomar_uk

Senior Member
sounds to me like you have the battery connection problem. search around the site and you'll find a potential fix.
Many thanks but too late for me. They kept it and as I said gave me a brand new T813 as a replacement, just a tad concerned they claim to have no spares to repair the screening my 12.2 Pro (they claim was the problem).

Many thanks anyway.

Shalom my friend, john

Sent from my SM-T813 using Tapatalk
 
This explains a lot. Thank you. How exactly do you find and modify the updater script?

open rom in 7 zip go to meta/google/look for updater script pull to your desktop. get notepad++ and open is look for a line with device check ex p900 and delete the whole line. save the updated script then delete the current one in the open 7 zip of the rom and then drag your edited one there.
 

risant

Senior Member
Aug 6, 2016
294
31
plz help how to resolve random freeze on samsung t900 using t900 cm12.1....all variants.... if i used the stock rom 5.1.1 no random freeze
 

Top Liked Posts

  • There are no posts matching your filters.
  • 57
    CyanogenMod Rom for Samsung Galaxy Tab Pro 12.2, SM-T900 (v2wifixx)

    NEW VERSION CyanogenMod 12.1, "Lollipop" version 5.1.1
    CM 12.1 compiled for the SM-T900 from source code

    These are unofficial releases of CyanogenMod for the Samsung Tab Pro 12.2 SM-T900 (v2wifixx). CyanogenMod is an aftermarket firmware for phones and tablets based on the open-source Android operating system. It offers features not found in the official Android based firmwares of vendors. These ROM's are compiled from CM sources, and based on CM ports by crpalmer for the Tab Pro 10.1 (SM-T520), he deserves the credit, this would not be possible without his work. I also want to thank Valera1978 for his work on our sister tablet, the SM-P900.

    WARNING: This is released without warranty of any kind. Use of this software could damage or destroy your tablet. Use at your own risk.

    How to install:

    1. Root device
    2. Download Rom and Gapps
    3. Install custom recovery, recommend TWRP Tab Pro 12.2 (v2wifixx), can be flashed with Odin or from existing recovery.
    You may also use Clockwork Recovery, a custom recovery img file can be installed using dd and Terminal Emulator. First download to /sdcard, and install to /dev/block/mmcblk0p10.
    Code:
    su
    dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p10

    4. Backup stock with custom recovery.
    5. Flash Rom and Gapps.
    6. Enjoy

    Downloads
    CyanogenMod 12.1 "cm-12.1-20150808-UNOFFICIAL-v2wifixx.zip"
    https://www.androidfilehost.com/?fid=24052804347790353

    CyanogenMod 12.1 "cm-12.1-20150730-UNOFFICIAL-v2wifixx.zip"
    https://www.androidfilehost.com/?fid=24052804347783830

    Gapps for CyanogenMod 12.1 Lollipop 5.1.1
    https://www.androidfilehost.com/?fid=24052804347783826
    17
    Source files for CyanogenMod for the Samsung Tab Pro 12.2 SM-T900 (v2wifixx) on Github

    Building CyanogenMod 12.1 for the SM-T900 from source is not too difficult. You do need basic computer knowledge especially with linux. CyanogenMod has wikis on how to compile for different devices. If you setup for picassowifi, just add the local manifest under .repo, then
    Code:
    repo sync
    and the kernel, vendor and device files will automatically download from Github. Then
    Code:
    source build/envsetup.sh
    and
    Code:
    brunch v2wifixx

    Good luck and have fun.

    Local Manifest
    https://github.com/Pentahex/android_repo_local_manifests_v2wifixx

    Device source:
    https://github.com/Pentahex/android_device_samsung_v2wifixx.git

    Vendor source:
    https://github.com/Pentahex/android_vendor_samsung_v2wifixx.git

    Kernel source:
    https://github.com/Pentahex/android_kernel_samsung_v2wifixx.git

    Again, source files are a fork from crpalmer and Valera1978, many thanks for their efforts.
    17
    New version uploaded. Please see opening post. Enjoy.
    15
    New Version CyanogenMod 12.1 compiled from source for the Samsung Tab Pro 12.2, SM-T900 posted in the OP, enjoy!
    12
    Thank you chhaggerty. This CM11 built directly from the cyanogen source code is very smooth and reactive. It's runs better than the predecessors, as it is created directly from cm11 source code and adapted to the SM-T900 instead of being a direct port from another device. I have fortunate to run this version in beta for 5 or 6 days now and I have not seen any issues in this release, but from the screen rotation that only seem to react if the app has a default setting. You can use the Set Orientation, or the Ultimate Rotation Control app to pick the rotation you desire.

    This list of functions, based on weaknesses in other builds and ports for the Tab/Note family, have been tested without any issues:
    - mtp - to activate go to Settings/About tablet/ and tap 8 times on Build number - The menu will now have Settings/{ } Developer options/ activated. Check mark USB debugging notify.
    - adb
    - External SD - I used JRummy's SD KitKat Fixer to allow my apps to write to the removable card (common w. all cm ROM's)
    - USB OTG including USB storage
    - Off-mode charging
    -----------------------------------------
    - Lid sensor is working, and no SOD's has been observed
    - IR blaster is working, i've used IR2.0
    - OC settings - located in Settings/Performance/
    - Advanced reboot - to activate go to Settings/About tablet/ and tap 8 times on Build number - The menu will now have Settings/{ } Developer options/ activated. Check mark Advanced reboot.
    -----------------------------------------
    - Play Store
    - Google Play movies download and playback
    - Google Play streaming Movies & TV
    - DRM - tested with Audible, Google Books and Amazon Kindle
    -----------------------------------------
    - Zona
    - Popcorn Time - need upgrade to latest version 2.3 beta, includes built-in VPN and Chromecast support with subtitles, earlier version timed out
    - YouTube 720p playback - 1020p possible with small hack, 1440p will work w. v5.9.0.12
    - Netflix
    -----------------------------------------
    - Chromecast with #MirrorEnabler hack, allowing for screen cast
    - MHL connector
    - Miracast
    -----------------------------------------
    - Capacitive lights - I assume this is the backlights for the capacitive buttons
    - Capacitive keys
    - Home button - correct function performed
    - Brightness manual + auto
    - Vibrator
    -----------------------------------------
    - GPS lock and voice directed navigation
    - WiFi both 2.4 GHz & 5 GHz are working
    - Bluetooth
    - Microphone
    - Audio on both speakers
    - Headphones
    -----------------------------------------
    - Camera
    - Torch
    - Camera Sensors
    -----------------------------------------
    - Xposed Framework and modules - need re-initialization after each boot (common to all cm ROM's)
    - Superuser
    - Hangouts Dialer phone calls via Hangouts
    -----------------------------------------
    The following are standard limitations and options for cm11:
    If you need write access to your external SD-card i suggest to d/l JRummy's SD KitKat Fixer and if you need init.d support d/l Uni-init by Ryuinferno. If you think to much heat is building up use Performance/Profile set to Power save, Performance/Processor/CPU governor/ set to ondemand, in addition to increase battery time you can set Wi-Fi/Advanced/Keep Wi-Fi on during sleep/ to Only when plugged in and make sure the Wi-Fi/Advanced/Wi-Fi optimization/ is checked and reduce Display/Sleep/ to below 1 minute. You can also use some apps to improve battery eg Easy Battery Saver, or the more sophisticated AutoCon+ Save Battery & Data and and to put hanging apps to hibernation Greenify that I believe require Xposed Installer. To improve charging time, you can use an app eg Faster Charger. Finally, I have also used PurePerformances in order to further improve the performances and VIPER4AndroidFX to allow for louder speaker sound and enhanced listening experience.

    I would love to see someone building an AOSP kernel containing eg fast charge, and OC, cifs etc. as these will never be part of a true cm11 kernel.
    bonuzzz has an overclocked kernel with source code for the P-900 TouchWiz, but it runs just as well on the T-900, that could be used as a base for conversion into AOSP, if someone is willing to give it a try.