Related
This is an unofficial build of TeamBAKED Blackbean 6 for the new Jelly Bean bootloader for the Transformer Prime.
Unlike the current TeamBaked Jelly Bean builds, this uses a modified version of my Jellybean CM device & vendor tree... including the new 3.1 Jelly Bean kernel and the new Jelly Bean drivers and proprietary files. THIS REQUIRES THE NEW JELLY BEAN BOOTLOADER. I will not release many builds for this unless there are issues or enhancements. This will remain in line with the TeamBAKED official releases, until I merge this to the TeamBAKED repo.
Highlights of this ROM:
1) Android Jelly Bean 4.1.2 JZO54K
2) Built using the latest TeamBAKED Blackbean 6 changes as of 30 Oct 2012 (GitHub) which is a combination of CM10 & AOKP features for the most case
3) Uses the latest a modified version of my TF201 device, vendor and kernel trees (based on the AndroidRoot trees) with the Jelly Bean 10.4.2.15 kernel (3.1) and proprietary files & drivers with some changes and additions by me (GitHub)
4) Needs the new Jelly Bean 10.4.2.15 bootloader [IMPORTANT: Flashing over an incorrect bootloader can permanently brick you device.]
5) HDMI audio/video streaming and bluetooth audio streaming (AVRCP 1.3 ready)
6) Camera and microphone
7) 4-way reboot menu (Reboot, Recovery, Fastboot & APX)
8) Includes all the files and changes need for the Google Widevine DRM [untested!!]
9) CIFS and NTFS (read-only) support
10) Fully functional dock and dock battery display
11) Configurable Navigation Bar, Expanded Desktop, CM & AOKP toggles
11) Removed TeamBAKED OTAUpdater
12) All other features of TeamBAKED Blackbean 6 and Jelly Bean (full hardware acceleration, Project Butter, HD video, customisable notification toggles & many more)
13) Some custom addons and feature ports by me (see the individual build changelogs)...
New in Oct 30 2012 build:
1) BFQ v5, SIO & V(R) I/O schedulers. SIO set as default
2) Lulzactive & Pegasusq CPU frequency governors.
3) Standardise CPU frequency tables' values & disable Asus system mode CPU speed restrictions
4) Enabled zRam/Compcache & KSM (Kernel SamePage Merging) support
5) Fixed model number & LCD density
6) Several device overlay updates and cleanups (bunch of updates for JB)
7) Auto-brightness turned off by default
8) Cleaned-up & updated release tools script (this creates the zip packages)
9) Set correct permission for BtService.sh (Bluetooth DUN) script
10) Force NV_FPS_LIMIT to 60 for all performance modes
11) Device Advanced setting menu to set Asus performance modes (defaulted to Balanced). This is not for the CPU speed, rather the Tegra performance setting (cpuX.sh like functionality)
12) Fixed Torch
13) Updated device power profile based on official JB release
Known issues:
1) Key layouts for certain regional keyboard may not work
2) Auto-brightness is funky [Use the app Lux for auto-brightness]
3) NTFS support is read-only
4) exFAT is not supported
Important:
1) Wipe data/factory reset if coming from any other ROM (icnluding the official TeamBAKED Blackbean ROMs)
2) Wipe cache/dalvik cache for every update
3) After flashing a build, it is a good idea to wait for 5-10 mins after bootup to allows everything to settle in
4) If you have not upgraded to the official Jelly Bean ROM yet, you will need to a JB ROM with the new bootloader first, and then you may flash the latest build here.
5) Once you upgrade to this ROM, you will no longer be able to use the official TeamBAKED Blackbean ROMs till the new Jelly Bean changes are merged
6) Make sure you use a recovery compatible with the new Jelly Bean bootloader after flashing this ROM.
The usual 9 yards:
1) Have you read this post properly. Read it again!!
2) You need to have an unlocked bootloader
3) You need to have a custom recovery (CWM or TWRP)
4) It is a good idea to have enabled nvFlash (thanks to AndroidRoot) so that you can recover from almost any brick
5) Neither I, nor the TeakBAKED team, nor the AndroidRoot team take any responsibility if anythings goes wrong. Use at your own risk
6) Always make sure you create nandroid backups regularly
baked_tf201_blackbean-6-jbbl.zip [IMPORTANT: You need to upgrade to the JB bootloader before flashing this]
Inverted Google Apps Pack - 20121016
OR
Regular Google Apps Pack - 20121011
GitHub Sources:
Device Tree
Kernel
Vendor Tree
Tweaks & Mods:
1. GPS Config Tweaks (Multi-Region):
This has various regionally optimized GPS configuration tweaks to inprove GPS locking.
Download tf201-GPSTweaks.zip and flash using TWRP recovery
tf201-GPSTweaks.zip - Dev-Host
tf201-GPSTweaks.zip - Goo.Im
2. SysCtl And DNS Tweaks:
This has a set of SysCtl tweaks to improve multi-tasking and overall performance as well as makes use of the Google DNS servers which are generally faster.
Download tf201-SysCtlAndDNSTweaks.zip and flash using TWRP recovery
tf201-SysCtlAndDNSTweaks.zip - Dev-Host
tf201-SysCtlAndDNSTweaks.zip - Goo.Im
3. Build.Prop Tweaks:
A compilation of build.prop tweaks tested on the TF201
Read here
4. EXT4 Journaling Tweaks: (Advanced Users Only. Manual Steps Involved)
If you don't understand these commands, you probably should lean more about them before using these tweaks.
Read here
Useful threads:
TF201 NVFlash
TF201 nvFlash General Users Guide [Unbrick/Recover/Downgrade/Upgrade]
[ADB/FB/APX Driver] Universal Naked Driver
TWRP Recovery For JB Bootloader
Support the project:
Donate to TeamBAKED
Donate to CyanogenMod
Donate to AOKP
Donate to AndroidRoot
Donate to me (craigacgomez)
Credits:
TeamBAKED, CyanogenMod Team & Contributors, AOKP Team & Contributors, AndroidRoot Team, TeamWin
Google, Asus, nVidia
Goo.im, Dev-Host
Me!!
Reserved for me!
first! this is awesome. downloading now. maybe i wont have anymore random reboots in the keyboard dock... your test build 2 was the most stable for me of all the JB roms (least amount of random reboots). I cant tell if its apps I have installed or the KB dock but i am usual in the dock.
Will report back.
:laugh:
Hi Craig,
What's the best way to install this rom or your cm10 build with data2microsd?
Sent from my Transformer Prime TF201 using xda app-developers app
This is fantastic... but now I have to choose... this ROM or CM10 unofficial? What are the tradeoffs? Feature set vs. performance? Which will you be supporting for longer, Craig?
Where can I donate when PayPal *****es at me with "Sorry — your last action could not be completed"?
bonstio said:
This is fantastic... but now I have to choose... this ROM or CM10 unofficial? What are the tradeoffs? Feature set vs. performance? Which will you be supporting for longer, Craig?
Where can I donate when PayPal *****es at me with "Sorry — your last action could not be completed"?
Click to expand...
Click to collapse
CM10 unofficial)) this has inverted interface that I can't stand)
bonstio said:
This is fantastic... but now I have to choose... this ROM or CM10 unofficial? What are the tradeoffs? Feature set vs. performance? Which will you be supporting for longer, Craig?
Where can I donate when PayPal *****es at me with "Sorry — your last action could not be completed"?
Click to expand...
Click to collapse
This is a mix of CM10 and AOKP... this is not released as frequently as CM10 or AOKP, but I may release a few updates to add some things... as long as I have this tablet, I will support all 3 ROMs...
is there a CWM recovery available for roms with a JB bootloader?
every time I flash using TWRP I get stuck at the asus boot screen...
I tried to flash this twice so far and keep getting stuck.
Just installed with twrp. All is well so far. Thanks for this ROM
Sent from my PC36100 using Tapatalk 2
knucklehead_11 said:
Just installed with twrp. All is well so far. Thanks for this ROM
Sent from my PC36100 using Tapatalk 2
Click to expand...
Click to collapse
what version of TWRP did you use?
I'm using TWRP 2.2.1. I just have not upgraded yet. If you are having problems with the install, check your md5 sum and make sure that you have a proper ROM download.
So far no force closes or any problems with games or video.
Sent from my Transformer Prime TF201 using Tapatalk 2
Hey Craig i really like this rom, but the only thing keeping me from using it is my GPS isnt working on it or any of your other unofficial ports. I tried flashing. The gps tweaks for the dongle wich i use and and doesn't seeme to make a diff. So i have to keep going back to the hairy been rom wich gps works in. I read that you said you were just starting out but maybe you could pull the gps stuff from HB or something if thats aloud. Also anyone else reading this hows your gps on JB roms(besides HB1.3) with the dongle? Thanks for your work ive flashed all your roms for my tf201 and given you thanks.
why am i getting stuck at the logo screen again....? i was only able to boot in aokp with disabled wifi. CM10 and this rom, i always get stuck at the loading screen
godlyitem said:
why am i getting stuck at the logo screen again....? i was only able to boot in aokp with disabled wifi. CM10 and this rom, i always get stuck at the loading screen
Click to expand...
Click to collapse
Probably a kernel problem, aokp has not the same kernel than the two others.
godlyitem said:
why am i getting stuck at the logo screen again....? i was only able to boot in aokp with disabled wifi. CM10 and this rom, i always get stuck at the loading screen
Click to expand...
Click to collapse
When met with this (as I constantly am while attempting to install HairyBean) I have to re-flash stock ROM, then recovery, then custom ROM. I didn't unlock and NVflash before jellybean so I can't go that route.
Sent from my HTC Vision using xda premium
screen keeps rotating constantly when I long-press to remove an icon or widget...
fully wiped 3 times (factory reset & system)....anyone else having any issues?
broad_st_bully said:
screen keeps rotating constantly when I long-press to remove an icon or widget...
fully wiped 3 times (factory reset & system)....anyone else having any issues?
Click to expand...
Click to collapse
Not having that problem but I'm using Nova launcher.
Very nice rom. Fast , stable and no reboots or hick upps so far.
Only usb ethernet doesnt work.
Man, I just can't find a rom that works with my keyboard that has an sd card in it. When I have a card in the dock, and go to settings/storage, it keeps FC'ing. If I take the card out, I have no problem with settings/storage.
kix08 said:
Hey Craig i really like this rom, but the only thing keeping me from using it is my GPS isnt working on it or any of your other unofficial ports. I tried flashing. The gps tweaks for the dongle wich i use and and doesn't seeme to make a diff. So i have to keep going back to the hairy been rom wich gps works in. I read that you said you were just starting out but maybe you could pull the gps stuff from HB or something if thats aloud. Also anyone else reading this hows your gps on JB roms(besides HB1.3) with the dongle? Thanks for your work ive flashed all your roms for my tf201 and given you thanks.
Click to expand...
Click to collapse
Well, I get very little GPS performance without the dongle even in a stock rom, and that was with UCS. JB stock gives pretty reasonable gps performance with the dongle in, at least if you're on the highway were there are plenty of satellites overhead.
I'm about to flash this and see how it goes. I'll update and let you know how my GPS does.
EDIT: tested GPS, I'm getting the same functionality as in both the ICS and JB stock roms. Which is to say "good enough". It can usually lock on at least 3 satellites.
Hi guys,
here is my boot.img extracted from my phone for 9100P NFC users.
It's a Siyah-Dorinmanx-V7.38 kernel with I9100PBULP3 radio.
It has the original stock boot screen logo,
now the most important thing, using
CM ROM
http://get.cm/get/jenkins/18028/cm-10.1-20130116-NIGHTLY-i9100.zip (CM for i9100)
+
http://forum.xda-developers.com/showpost.php?p=29960634 (NFC support for JB by jthatch12)
It will get you full support of NFC, no bugs finded yet, it works perfectly even has the original icons!
I tryed other custom roms claiming of having NFC support, but none of them had this level of support (no icons, bugs with turning NFC on/off etc.)
This is not my work! I only combined rom with kernel and NFC mod!
Thanks to the Dorinmanx and the CM team for doing such a great job and jthatch12 for his implementation of NFC in our devices.
I was very disappointed with the support of 9100P and was desperately changing roms to find something fully working, the best result I get is using this combination above.
Cheers for the great 9100P!
I DO NOT OWN THE ROM.
The developer of this rom is kumajaya on MIUI forum and thanks to him for his work.
MISSION:
Embarrass Xiaomi because refuse to release Redmi 2 kernel source
BUG:
Before you install this ROM, check your device magnetic sensor. Currently YAS537 not supported!
Still under development, built from sources, no hidden sources, not a binary dirty hack ROM
The following will not be supported in this thread:
- Custom Kernels
- Mods, including CPU management mod or any strawberry mod
- Modified system files
- Xposed
If you reuse even a part of my work here, a proper credit is a must, keep it open source also a must
Download:
Cyanogen and TWRP recovery: https://goo.gl/cDJQXI
CyanogenMod 12.1 ROM: https://goo.gl/zhGZjQ and https://goo.gl/5sqZGp
For better Google experience, install TK GApps Nano: http://forum.xda-developers.com/android/software/tk-gapps-t3116347
Don't create any mirror without a permission!
Cyanogen recovery above just like a standard AOSP recovery without a lot of features compared to TWRP, but you can temporary boot it using "fastboot boot cyanogen-recovery-wt88047.img" command to check if CyanogenMod 12.1 ROM possibly working on your device variant.
Don't even try this ROM on Redmi 2A variant!
Sources:
CyanogenMod source tree: [url]https://github.com/CyanogenMod[/URL]
Kernel source: https://github.com/kumajaya/android_kernel_cyanogen_msm8916
Device specific source: https://github.com/kumajaya/android_device_wingtech_wt88047
Vendor binaries: https://github.com/kumajaya/proprietary_vendor_wingtech
Changelog:
Device specific source: https://github.com/kumajaya/android_device_wingtech_wt88047/commits/cm-12.1
Kernel source: https://github.com/kumajaya/android_kernel_cyanogen_msm8916/commits/cm-12.1-amss-1.0.2-wt88047
Vendor binaries: https://github.com/kumajaya/proprietary_vendor_wingtech/commits/cm-12.1
Credits:
Google, AOSP, Cyanogen, CyanogenMod community, Qualcomm's CodeAurora @balika011, @zwliew, @Flour_Mo
Introducing me: XDA Recognized Developer, CyanogenMod contributor
My wife, she always believed I could restore back her device in minutes
Some tools: Kate (text editor), Kompare (diff viewer and generator), qgit (git GUI)
Smarfren Indonesia for Andromax Q source code
Micromax India for Yuphoria and Yureka source code
Current status:
Boot to Android, this is my first ROM that really boot on the first try
Touchscreen works, all hardware button mapped correctly
No screen flicker, fluid graphics
Voice call and SMS works, data over WiFi and GSM works (radio config in build.prop fix previous GSM issue)
Vibration and screen rotation works
All sensors seem works including GPS and compass but light sensor still need a fine tuning
Both camera working, the author found a super clean solution
No boot animation (fixed, kernel issue) Disable splash screen break Android boot animation but if I enable it, Cyanogen recovery covered by Tux the penguin logo in the center. The workaround solution, move Tux to the top right of the screen
No sound (fixed, kernel and user space issue) This also fix slow boot because of logcat flooding. BUG: Speaker output ignore headset jack insertion, sound out from both speaker and headset
Bluetooth file transfer fail (~42MB zip, failed at 17%) WiFi file transfer way faster
FM radio works
WiFi hotspot works
YouTube and local video 720p works
LED driver working great, multi color and blink
Remember, no contribution from Xiaomi yet. That's the reason why I try to avoid "Xiaomi" string in my source as possible but Wingtech.
I use CyanogenMod resources as much as possible, including common MSM8916 device tree and kernel. Maintain device source tree and leave common part to CyanogenMod community. I'll strictly follow CyanogenMod coding style and source structure. This is about source code quality.
AGAIN, I DO NOT OWN THE ROM.
Will try it soon. And I hope Xiaomi will release the kernel like Redmi 1s.
kumajaya and zwliew are the most stable CM12.1 roms for our phone. I hope they reach 100% full working version in near future.
Thank you both!
Can you upload the changelog for the latest [30/09/15] build. Also is the YAS537 supported
How about some screenshots?
What is the point of this thread when the original poster already has one on XDA?
Sent from my Nexus 7 using Tapatalk
crzlloid said:
Can you upload the changelog for the latest [30/09/15] build. Also is the YAS537 supported
Click to expand...
Click to collapse
There is a link in my post about the changelog and the YAS537 is still not yet supported.
zwliew said:
What is the point of this thread when the original poster already has one on XDA?
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
Sorry, but I have already talk to kumajaya about it. Then he ask me to help him on requesting an official sub-forum for our device. Anyways, if anyone here oppose me about posting this thread, then maybe I should delete this.
wow, using this in 2020, 5 years later.
Hi
well I have no experience with Custom-ROMs, so can someonePlease explain to me
where exactlythe difference between Official ROMs and Unofficial ROMs is ?
What would you recommend in terms of stability
thanks
This is what I believe it means, using CyanogenMod as an example (https://en.wikipedia.org/wiki/CyanogenMod).
AFAIK the CyanogenMod team develop their custom rom for a generic platform. They then select a number of devices and customize the generic version so it can be applied and used on these selected devices.
An official CyanogenMod ROM is when the CyanogenMod team have selected the device and done the extra work for the custom ROM to work on that device themselves.
Unofficial means that the extra work to tailor the custom CyanogenMod ROM for the device is done by other developers, who use the generic base which CyanogenMod provide.
To my understanding its more like sub-beta, directed mainly for flash freaks (count me in).
Regarding stability some official ROMs are far from stable, while some unofficial are ages in front.
Thanks guys for the great explanation....appreciate it...
well , During my search for a good ROM software I have often read that the 2 Roms was s always recommended
1. Temasek
2. LiquidSmooth
i mean are both roms really good and stable on s3?
or would you recommend something else
thanks
I would recommend CM12.1 as a daily driver. Is clean and fast. It works way better than stock Samsung ROMs and is very stable thanks to @JustArchi. It also drain less battery and has a good power save feature.
http://forum.xda-developers.com/galaxy-s3/development/rom-cyanogenmod-12-1-i9300-t3254215
My current setup is this:
Recovery: TWRP
ROM: CM12.1
Kernel: Boeffla
And never been happier with my i9300
Hi
I have the latest version temasek's UNOFFICIAL CM12.1 v18.0 flashed + PA-GOOGLE APPS Plus GOOGLE STOCK PACKAGE
and I must say it really makes a great impression, everything seems stable so far.....
well the only thing that bothers me is the (ugly white background in Android Lollipop)but its just a matter of taste :silly:
Plus the newer builds of CM12.1 have OTA updater working.
How would you estimate the stability and performance of CM12.1 ROM's compared to official CM11 nightlies?
Flashed official CM11 once. Within 30 minutes of testing a had plenty of crashes and several Cannot connect to camera.
Lot of people here say that there is no need to move to Lolipop, because Kitkat is far more stable.. However I wouldn't agree.
As official Gapps was released, more Pie based custom ROMs were released with dfferent built-in kernels.
But: do you know about any custom kernels - mainly overclocked ones - for Pie?
I know, I have to wait patiently, I'm just curios about the options because I found a great ROM with minimal bugs, the only problem is the kernel they use, I got used to much faster performance.