After so many trial and error, I've finally saved the latest version of my system with TWRP backup. I want to share this personal setup with you guys since it required a lot of work to debloat, install add-ons, apps, kernels and tweaks. This is a single package that contains many modifications from other threads made for simple, one-time installation. I tried to keep it close to Android TV (Nougat) exprience. However, I kept some of the Amazon software that I use like Alexa and Amazon Appstore.
Guides I found and used for this rom:
[UNLOCK][ROOT][TWRP][UNBRICK] Fire TV Stick 4K (mantis)
[Magisk][Module] FireTV 4K Stick Add-Ons
[Magisk][Module] Google Play Market, Services and TV Search for FireOS 6
[KERNEL][FireTV Stick 4K] Custom Kernel For AFTV 4k - 6.2.7.7
Customizing the Fire TV Stick 4K (mantis) - Debloat - Replace launcher and Testing
Fire TV Stick 4K Tweaks (Need Root, Need Keyboard) Works On Any Firmware
!!Please read these threads before you begin!!!!All credit goes to those developers!!!!Do at your own risk!!
Some Info:
Android Version: 7.1.2Fire OS Version: 6.2.7.6Working TWRP Version: 3.3.1-0Installed Magisk Version: 20.4Installed launcher: Google Leanback LauncherAvailable Internal Storage after installition: 3.15 GB
Screenshots:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Contains:
FireTV 4K Stick Add-Ons from @tsynik
Google Play Market, Services and TV Search from @tsynik
Custom Kernel For AFTV 4k from @Pretoriano80
Fire TV Stick 4K Tweaks from @Skel40
==========================================================================================
Working:
Alexa
Voice Input of Amazon keyboard. (need to enable FireTV IME Keyboard from settings) (long press menu button for quick switch)
Amazon Settings
Fire TV Remote App (I highly suggest this app. Works perfect for navigation and keyboard input)
Amazon Appstore (You can install your previous paid apps from here. Search function in amazon appstore only works with alexa)
Google Play Store and Services
Magisk
Xposed
Recommendations on launcher
Widevine DRM (Netflix, PrimeVideo etc. works fine)
Kodi Audio Passthrough
Android Screen Cast
Not working:
Google Assistant
Google Voice Search
==========================================================================================
Some useful apps that I installed (all can be uninstalled):
FX (file manager with root access)
Link2SD (app manager with root access. It lets you uninstall, freeze system apps or convert them to user apps and vice versa)
Xposed Edge (simple alternative to tasker or key mapper with root access. I've mapped long-press of back button to kill foreground app)
LeanKey Keyboard Pro (came with tsynik's magisk module and I loved it)
Smart Youtube TV (modded youtube app that enables dozens of options. I'm using it to increase the playback speed of videos)
MX and VLC Player (to play local or online streams)
Aerial Dream TV (really nice screensaver that uses Apple TV visuals)
Prime Video, Netflix, Spotify (not to make the launcher look empty)
Installed magisk modules:
Xposed Framework (rovo89)
Google TV Apps for FireOS 6 (tsynik)
FireTV4k Selinux Fix (Pretoriano80)
Installed xposed modules:
Xposed Edge
AFTV-XM (tsynik)
AFTV-GAPPS-XM (tsynik)
==========================================================================================
Requirements:
OTG Adapter
USB Keyboard/Mouse
USB Stick Formatted Fat32
TV or Monitor
Firestick 4K
How to install:
Be aware that your warranty will be void.
Backup your files.
Unlock bootloader and install twrp using this guide.
Download and extract Firestick 4K Android TV TWRP Backup.rar to TWRP backups path on USB stick; TWRP > BACKUPS > G070VM0984752N1Q
Do a factory reset via TWRP (use otg adapter and keyboard/mouse to navigate)
Restore from TWRP backup that you prepared.
Reboot to system.
Connect to wifi and log in to your amazon account. (still using keyboard or mouse to navigate)
Go to Settings > Fire OS > Controllers and Bluetooth Devices and pair your Fire TV remote. (now you can ditch the keyboard)
Enjoy.
Mirror:
Google Drive
Additional Notes:
Developer options and USB debugging enabled.
OTA updates disabled.
Disable "Stay Awake" option in developer settings if you want the screensaver to start.
Long-press to back button kills the foreground app. It makes quitting activities easier.
Long-press to menu button opens fast keyboard switching window. It helps to switch to amazon keyboard when I use voice input.
You can change the launcher to whatever you want. I'm happy with Leanback Launcher. I didn't try but there's this.
Important: Never install magisk updates from magisk. Use TWRP.
If you want to create TWRP backup, select "System Image" and "Vendor Image" insted of system and vendor.
Suggestion: FX Web Access makes it easier to tranfer files.
Suggestion: I think keyboard from FireTV remote app and alexa's speech to text input are the most efficient input methods if you don't have physical keyboard.
Important:
tsynik said:
Play Store downloads not fully compatible with Amazon download manager. In case apps won't install from Play Store - uninstall Play Sore updates from ATV Settings.
NOTE:
You need to remove and readd Google account after module update.
Click to expand...
Click to collapse
Installed Netflix and Spotify apps are compatible with alexa.
I couldn't make my dualshock 4 controller work with this device. Even with the stock system. Help would be appreciated.
Reddit Posts Of This Guide: Here and Here
==========================================================================================
Big thanks to:
@k4y0z and @xyz` for unlocking the bootloader.
@tsynik for building those life-saving magisk modules which is basicly the key of this build.
@Pretoriano80 for creating a kernel which supports SDCARDFS, exFAT, F2FS, Wireguard, Advanced TCP options, CIFS and NFS, Insecure ADB.
@bnevets27 for debloating script.
@Skel40 for build.prop tweaks to increase performance.
@Bertonumber1 for testing the rom.
Excellent work , a lot of time and effort paid off m8 .
Well done
just a small question.... another member had mac issues after restore , I imagine this is same case scenario to his case given it is a restore from another 4k via twrp ?
Has this been tested on other 4K sometimes it csn be problem different devices but should be okay
Bertonumber1 said:
Excellent work , a lot of time and effort paid off m8 .
Well done
just a small question i saw another member do a restore from one 4k stick to another just a few weeks ago , the result wasnt too good.
I imagine this is same case scenario to his case given it is a restore from another 4k via twrp .
Has this been tested cross-device ?
As i have a spare stick there i can do testing if need be in respect of Wifi Mac,Serial info remaining intact ?
Click to expand...
Click to collapse
No I didn't tried with another device, unfortunately I have only one . I would be appreciated if you test it. Thank you very much. Also can you please share the thread that you mentioned?
Yeah sure heres some information here , not sure if this is different from your technique but sounds similar .....
Unbrick Fire TV Stick 4K. Help!
Hello! I was trying to clone one Fire TV Stick 4K to another. I've backup with TWRP from one FireTV Stick 4K next partitions: System, System Image, Vendor, Vendor Image, Data, Boot. Then was trying to restore all of them on another stick with...
forum.xda-developers.com
Ok my friend i can confirm we are good to go .
Everything intact remote paired , wifi /ethernet bluetooth all good smooth operation
Thank you , again excellent work
Bertonumber1 said:
Ok my friend i can confirm we are good to go .
Everything intact remote paired , wifi /ethernet bluetooth all good smooth operation
Thank you , again excellent work
Click to expand...
Click to collapse
Thank you very much. What a relief. You're the first beta tester much appreciated.
I got this working on 2 FireTV 4k.
I used the YouTube but I could never get the Amazon voice search to work with it. Do you know how to set it up correclty?
Is there a way to make the Backward Play and Forward button to work with YouTUbe?
story said:
Is there a way to make the Backward Play and Forward button to work with YouTUbe?
Click to expand...
Click to collapse
I don't know about backwards/forward button or voice search on youtube. Maybe you can try installing original youtube app from amazon store or google play.
Just a word to the wise as of recent events it is strongly advised members disable OTA updates on Mantis should they wish to continue modifications such as #root, launchers , adb pm commands etc etc . Update bin 6.2.7.7 has a 2nd "system updates" part to it that contains the boogeyman and is breaking things like adb commands etcetera .
Bertonumber1 said:
Just a word to the wise as of recent events it is strongly advised members disable OTA updates on Mantis should they wish to continue modifications such as #root, launchers , adb pm commands etc etc . Update bin 6.2.7.7 has a 2nd "system updates" part to it that contains the boogeyman and is breaking things like adb commands etcetera .
Click to expand...
Click to collapse
It is possible to downgrade anytime with twrp backup right? I might try to build the same setup for the new versions later.
burcbuluklu said:
It is possible to downgrade anytime with twrp backup right? I might try to build the same setup for the new versions later.
Click to expand...
Click to collapse
Yeah ofc , should be able to do this tgrough
burcbuluklu said:
It is possible to downgrade anytime with twrp backup right? I might try to build the same setup for the new versions later.
Click to expand...
Click to collapse
Should be , should be enough to :
Disable addons (xposed )
boot to twrp and wipe /system , dalvik, cache
Leave data alone
Then after previous firmware has been flashed from twrp
Reboot and enable xposed , addons again , maybe another reboot ? IDK
Bertonumber1 said:
Yeah ofc , should be able to do this tgrough
Should be , should be enough to :
Disable addons (xposed )
boot to twrp and wipe /system , dalvik, cache
Leave data alone
Then after previous firmware has been flashed from twrp
Reboot and enable xposed , addons again , maybe another reboot ? IDK
Click to expand...
Click to collapse
Ok thanks
The lastest update breaks kodis "audio passthrough" under certain conditions too. DTS has been disabled by Amazon.
Just wanted to say thanks! My Fire Stick became a mess and this was a breeze to install. Not sure if the following behaviour is intended, but one thing I found annoying was that when you stream something via a streaming service, the video continues to play in the background when you press the home button (you can still hear the audio). I solved this by changing the home button behaviour to "kill current foreground app".
Velcro31 said:
Just wanted to say thanks! My Fire Stick became a mess and this was a breeze to install. Not sure if the following behaviour is intended, but one thing I found annoying was that when you stream something via a streaming service, the video continues to play in the background when you press the home button (you can still hear the audio). I solved this by changing the home button behaviour to "kill current foreground app".
Click to expand...
Click to collapse
Hi try this app , should kill all background processes and free up some memory also
Fast Task Killer 3.1.0 | TechDoctorUK
www.techdoctoruk.com
Thanks to tduk
I use YouTube a lot so that's the only perspective I can give. I am using the same YouTube apk.
The boot time is significantly longer than FireOS. I hook mine up to the TV USB so it cold boot every time. I would say it's double the amount of time to boot your rom.
1. The remote works beautifully on FireOS. It allows skipping without that shadow thing coming and interrupting and dedicated buttons for play/pause is essential.
2. FireOS using the same APK doesn't support backward on LIVE stream.
I will be switching back it was fun hacking this. It's been a while.
Anybody experiencing not being able to delete anything from priv-app folder on 6.2.7
6 and above ? Trying to delete manually in file explorer . When i try to mount system rw it returns a device/resource busy /dev/block/soc/11230000/by-name 》sytem - system Error .
Ive disabled most of the junk but theres a lot that can be removed permanently .
Try in twrp. I allways use twrp for that.
Boot twrp
adb shell "mount -o rw /system"
0815hoffi said:
Try in twrp. I allways use twrp for that.
Boot twrp
adb shell "mount -o rw /system"
Click to expand...
Click to collapse
Still the same in Twrp mate , same error.
adb shell "mount -o rw /system"
Error : mounting /dev/block/mmcblk0p11 on /system failed : device or resource busy.....WTF?
Is this a new thing with newer os ? Ive never had this before
Related
This is a Rom based on stock Amazon 8.3.0 With ROOT, Tweaks, many Amazon stuff removed, And Go Launcher EX
**** Use at your Own Risk! I take no responsibility for any damages and or Deaths to you, your Kindle, or anything else, remotely related to the installing, usage, or Testing Of this!!*******
8.9StariROM is Only for the Kindle HD 8.9!!
For any TWRP info go to Hashcodes posts Here for latest version
and here for install if any issues with TWRPhttp://forum.xda-developers.com/showthread.php?t=2128175
Thanks alot to Hashcode for everything you have done for the Kindle, and TWRP!!!!!!!!!!!!
Red is for things changed!
Update:
Added stock Launcher to view Kindle books from default viewer!
Added a few other stock amazon stuff!
App store should work better and so should books!
Apps Preinstalled:
Android News and Weather app
Go Launcher EX
Go Locker! (select go locker as default launcher at boot up)
Google Chrome
ES File Explorer
Gallery (stock ICS)
Google Now!!!!!! Link to XDA Post
Google Keep
Greenify
KFHD xsettings Link to XDA Post
LMT Launcher (provides Black home settings and search replacing stock soft key bar) Link to XDA Post
Button Savior
Market Helper Link to info
Play Store Updated!!!
Sidebar Lite
SuperSU
WallChanger (use to set wallpaper)
YouTube
Widget Picker
Plus a few Widgets: for Calculator, Calendar, and clock
Tweaks: Pimp my rom did to it (not APK)Link to XDA Post
Amazon stuff still left in:
Amazon MP3's
Amazon Video
Amazon Appstore (can search and add your apps you one but cant find a list of them)
Email
Calander
Kindle Docs
People
Anything else you want like Kindle you can get from the Google Play Store.
OTA should be blocked! (Hope it worked)
Installation:
Step1:
Deregister your kindle before restarting under settings My account
Update**
Step2:
Download these 3 files
1.Installer
2.Image File
3.Data File to be restored in TWRP after fastboot Image
Step3:
Extract File installer file to c:\ (so should have C:\Root then all the files extracted their)
And extract image file in that folder
Step3.5:
Extract Data file on your computer and copy to in its own file SDCard\TWRP\Backup\0000
Step4:
Click on 8.9StariROM_Installer.bat Fallow Directions Given!
Step5:
If you already have TWRP go to step 6:
After reboot if you get Red Screen means you dont have TWRP then run FixRedScreen.bat that is in the Root folder
Step6:
Restart Kindle and go into TWRP by Holding Up button When the Blue Kindle Fire is showing at boot
Step7:
Click Wipe Then Factory Reset
Step8:
Go Home to TWRP and restore Restore the Folder you Extracted to your Kindle
SDCARD\TWRP\BACKUP\000000\8.9StariROM_Data
Step9:
Reboot System
Step10:
once Started Click check box and click on GO Locker
Step11:
Setup your wifi, Time zone, Amazon account, Email accounts. and Google account!
Screen Shots!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Thank you for this awesome rom!
I'm very new on Kindle now, just have it as stock as shipped.
Can I just use this installation without anything?
You just mentioned "no rooting needed" but how about bootloader and recovery?
In theory yes but my Kindle has twrp already installed so it is not tested yet. The most important thing is to have the drivers installed correctly.
If the drivers not working right it won't go into fastboot.
Copy anything from your Kindle to your computer if you want to save it as it will wipe everything.
Give it a try and see how it works for you! Thanks
Thank you!
I will try that, and post the result later!
Seams it may give you a Red Screen on boot working on a script to correct this! (shouldn't give red screen if you have TWRP already installed).
Lots of features that I like. A bit if a struggle with pie controls with Amazon native menus at times. Appstore crashes on launch every time. Any solution for that? Also, when entering the app manager it claims that too many devices are registered. Any ideas? Deactivated 10 and still end up with the error.
Thanks for your work
Ray
Reborn627 said:
Lots of features that I like. A bit if a struggle with pie controls with Amazon native menus at times. Appstore crashes on launch every time. Any solution for that? Also, when entering the app manager it claims that too many devices are registered. Any ideas? Deactivated 10 and still end up with the error.
Thanks for your work
Ray
Click to expand...
Click to collapse
If you dont like LMT launcher you can download Button Savoir from the playstore and dissable LMT, perhaps that would help you with amazon native menus also. Im not sure why your appstore is crashing mine is working, perhaps you can uninstall it with titanium backup then go to amazons webpage and download the app? Not really sure about your problem with too many devices registered, I did have that a while back and I removed some (before my kindle) and wasn't a problem and hasn't been a problem since.
Maybe I should add deactivate your device before installing.
lizzord30 said:
Seams it may give you a Red Screen on boot working on a script to correct this! (shouldn't give red screen if you have TWRP already installed).
Click to expand...
Click to collapse
Oh my, I should have checked your comment!
I got exactly what you said, (red screen on boot, and freeze)
For fix it, I got into fastboot mode, flashed TWRP, got into recovery, use adb push comment for copying a custom rom into internal sdcard, and reflashed the rom.
Now it works, and I will try other roms
rhplusa10 said:
Oh my, I should have checked your comment!
I got exactly what you said, (red screen on boot, and freeze)
For fix it, I got into fastboot mode, flashed TWRP, got into recovery, use adb push comment for copying a custom rom into internal sdcard, and reflashed the rom.
Now it works, and I will try other roms
Click to expand...
Click to collapse
So if i get this right you skiped steps 1-4.5 and went right to step 5 and it worked after flashing my rom from fastboot?
Steps from this post
lizzord30 said:
So if i get this right you skiped steps 1-4.5 and went right to step 5 and it worked after flashing my rom from fastboot?
Steps from this post
Click to expand...
Click to collapse
Yes correct.
I skipped step 1 ~ 4.5(the rom is already broken as red screen, so I do not need to back it up), and just install 2nd bootloader + TWRP (step 5).
I downloaded your rom from another thread, which is RAR file contains TWRP backups.
I pushed them into my sdcard, and restore them. WORKS!
I did not used this "clean install" version.
Uploaded a new version!!!!!!!!!!!!!
Updates:
Go Launcher EX
Go Locker (Need to setup it and activate it as admin and set as default Home button)
Removed CPU Master since stock without is more responsive and you can install your own cpu controlling app
Removed a few things (cant remember off hand)
Added Button Savoir (Still have LMT you can use whatever one you want but BS starts automaticly)
Added Widget Picker so can add widgets on Go Launcher
Added bat file to fix Red Screen and install TWRP if you dont have it (but you must have Run my installer first)
Added bat file to do a complete Wipe SDCARD and all Data(shouldn't really need it)
OP Download is updated!
Now should be able to install on a bone stock 8.3.0 KFHD 8.9 without root or TWRP!! But need someone to test it for me. Should give you root my rom plus TWRP 2.4.4.0!!!
Hi, thanks for your job.
I have pb with download
Erreur 310 (net::ERR_TOO_MANY_REDIRECTS) :
Jahwol
---------- Post added at 02:25 PM ---------- Previous post was at 02:12 PM ----------
Sorry, it's due to Chrome, work fine with IE
Jahwol
Added TWRP flashable zip to the OP will add in original launcher and kindle app store should fix problems with reading kindle books and app store. The stock launcher is more or less the book app from what i can tell. Hope this fix any problems with that!!
Updated the Rom! Should have working Stock Amazon Kindle Reader using stock launcher!
A little confused......is one of the files in the downloads a file that I can just flash in TWRP as a "restore nandroid backup"?? If so then which one - one file is like 550mb and the other is around 180mb or something. Larger one seems like a complete rom and cant figure out what the other one would be - not quite big enough for a complete rom but maybe big enough for gapps and other apps!?
It's my girlfriend tablet so don't want to screw it up even though i backed up the blobs! Left my laptop at a friends and honestly don't feel like setting up the drivers, fastboot and adb on hers.
Have had the second bootloader and TWRP installed for while. Whats safe to skip???
Sent from my ASUS Transformer Pad TF700T using xda premium
---------- Post added at 06:39 PM ---------- Previous post was at 06:33 PM ----------
Mike3.14159 said:
Have had the second bootloader and TWRP installed for while. Whats safe to skip???
Sent from my ASUS Transformer Pad TF700T using xda premium
Click to expand...
Click to collapse
And it is already running on StariROM_1.0 that I download from the other thread!!
Sent from my SCH-I535 using xda app-developers app
Mike3.14159 said:
A little confused......is one of the files in the downloads a file that I can just flash in TWRP as a "restore nandroid backup"?? If so then which one - one file is like 550mb and the other is around 180mb or something. Larger one seems like a complete rom and cant figure out what the other one would be - not quite big enough for a complete rom but maybe big enough for gapps and other apps!?
It's my girlfriend tablet so don't want to screw it up even though i backed up the blobs! Left my laptop at a friends and honestly don't feel like setting up the drivers, fastboot and adb on hers.
Have had the second bootloader and TWRP installed for while. Whats safe to skip???
Sent from my ASUS Transformer Pad TF700T using xda premium
---------- Post added at 06:39 PM ---------- Previous post was at 06:33 PM ----------
And it is already running on StariROM_1.0 that I download from the other thread!!
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
The one file is a complete system image, the second part is Data to restored in TWRP. To update you Just Run the installer from fastboot then do the restore after that. It wont run the TWRP install unless you run the fixredscreen bat file.
By adding a image with the TWRP stuff already done to it you dont need to do that stuff in adb before installing TWRP recovory. Meaning you dont need root before installing this!
lizzord30 said:
By adding a image with the TWRP stuff already done to it you dont need to do that stuff in adb before installing TWRP recovory. Meaning you dont need root before installing this!
Click to expand...
Click to collapse
I'm rooted already but haven't yet taken the step of TWRP. I want to go to CM eventually when Bluetooth is working but have been put off by the issues people have had installing the second bootloader. I am on 8.3.0 - can I just run your files and I will be re-rooted and TWRP installed (with the new ROM)? Is it really that easy?!
apd said:
I'm rooted already but haven't yet taken the step of TWRP. I want to go to CM eventually when Bluetooth is working but have been put off by the issues people have had installing the second bootloader. I am on 8.3.0 - can I just run your files and I will be re-rooted and TWRP installed (with the new ROM)? Is it really that easy?!
Click to expand...
Click to collapse
Yep! If you run the first installer and you get a Red screen dont worry just Hold power till it turns off while still connected to your computer, then run the fixredscreen.bat once its started should tell you to turn on your device and should get you in fastboot if your fastboot drivers are working (of course you couldn't get this far without your fastboot drivers working).
I thought this would be alot more populer making it easy to go from a non rooted device to a TWRP with root. Plus has a way to fix the red screen problem that is common. But seams everyone just wants CM10.1 With i can understand as once the bugs are out I for sure will run! It seams faster but still my rom isnt very slow IMO.
Would love to hear more feedback on this!
PS: for anyone that got unrooted from 8.3.1 this will drop you back to 8.3.0 with root and so far I have not got a update so my update blocker seams to be working!
Fantastic, thanks. I will do this on Saturday
Update: left my 8.9 alone for a couple of hours and found it had upgraded itself to 8.3.1 (even though I had installed it a protection from kindle free) . How annoying - root and some apps gone. Will be installing this rom tomorrow!
Sent from my GT-N7100 using Tapatalk 2
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
IMPORTANT NOTE: Need to be on 1.2.858 in order to install this properly.
------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
How to Install
Follow the install instructions for CWM from here
Push the patch to /sdcard/ ( use adb push, copy it over via usb, etc.... )
Install the patch
Reboot!
Click to expand...
Click to collapse
------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Post-Install
Go to MAKE -> Software -> Superuser, it'll prompt you to install. Accept.
Go to Xposed Installer ( same place as Superuser ) and under Framework click Install/Update, afterward go to
Modules section and make sure to check "Play Store Mode For Ouya [1.0]". Go back and reboot.
After reboot you should be able to setup Play Store and everything else should be setup and good to go!
Click to expand...
Click to collapse
------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Changelog
|=========|
|-02.13.2014-|----- 1.2.858 RC1
|=========|
User definable wallpapers and updates are added
Features from StockPlus rom like Init.d Superuser/Su, BusyBox, CIFSManager and Google Play Store added to patcher
A bit more proper CIFS support now
Click to expand...
Click to collapse
------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Download
Download here:
SPP_1.2.858_RC1
------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Credits
rovo89 for Xposed framework
WonderEkin for PlayStore fix
...and anyone who I missed ( including the many in #ouya and #whouya who's helped :good: )
Click to expand...
Click to collapse
------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Finally do not hold me responsible for damaging, bricking, your cat getting electrocuted and anything else.
If you enjoy this patch and feel mighty gifty then buy me my next drink!
-=FAQ=-
How do I mount my shares? ( or how to not get error messages or empty folders )
Click to expand...
Click to collapse
You'll need to set the option "unc=\\\\put.ip.address.here\\name,noperm" without quotation marks.
Google Play Services randomly FC's while not open.
Click to expand...
Click to collapse
OUYA doesn't like apps running in the background so it kills them to reduce issues with games you may be playing.
I keep getting "This module does not provide a user interface" error.
Click to expand...
Click to collapse
Using the touchpad on the OUYA, hover over the checkbox and tap it to "check" the module.
How do I change the wallpaper?
Click to expand...
Click to collapse
Copy the wallpaper you wish to use to "/sdcard/CONFIG/" ( or use a direct link image... see bellow )
Open the file "THEME" found in "/sdcard/CONFIG/" with a text editor of choice
Replace the name of the .jpg ( or .png ) to the one that you copied over to "/sdcard/CONFIG/"
For example... if I copied over a wallpaper called "wallpaperformyouya.png" the line would change to look like this:
Code:
"background":"http://localhost/wallpaperformyouya.png"
Alternatively you can also use a direct link like an imgur link...
Code:
"background":"http://i.imgur.com/Gs16J2V.png"
Save it back to the OUYA and reboot.
Hey man. Thanks for that
But I have two questions:
- Are all mods from your awesome StockPlus ROM integrated here? I'm asking especially because of PS3 Controller support.
- The patch is for the Stock ROM, right? Could you provide a few instructions how to install Stock ROM over StockPlus?
Thanks in advance and again:
Awesome work man
- Are all mods from your awesome StockPlus ROM integrated here? I'm asking especially because of PS3 Controller support.
Click to expand...
Click to collapse
Yes, the only one that's not included is xtheme engine because I'd need to remake the theme since there's quite a lot of changes.
- The patch is for the Stock ROM, right? Could you provide a few instructions how to install Stock ROM over StockPlus?
Click to expand...
Click to collapse
It is... the easiest method of upgrading would be to download 1.2.858 from here and copy it to /sdcard/
Once in /sdcard/ reboot into cwm -> install zip from sdcard -> choose "RC-OUYA-1.2.858-r1_ota.zip" and flash it. Then go back into install zip from sdcard and install "SPP_1.2.858_RC1.zip" over it.
IncognitoMan said:
Yes, the only one that's not included is xtheme engine because I'd need to remake the theme since there's quite a lot of changes.
Click to expand...
Click to collapse
Not a problem for me, haven't used it before
IncognitoMan said:
It is... the easiest method of upgrading would be to download 1.2.858 from here and copy it to /sdcard/
Once in /sdcard/ reboot into cwm -> install zip from sdcard -> choose "RC-OUYA-1.2.858-r1_ota.zip" and flash it. Then go back into install zip from sdcard and install "SPP_1.2.858_RC1.zip" over it.
Click to expand...
Click to collapse
That's easy man. I thought the OTA update would overwrite the recovery or something.
And what about further OTA updates? Will OUYA automatically perform updates or is that disabled by your patch?
I don't want to accidentally lose your Plus-Features, because of new OUYA ota update.
yeahimdukenukem said:
Not a problem for me, haven't used it before
That's easy man. I thought the OTA update would overwrite the recovery or something.
And what about further OTA updates? Will OUYA automatically perform updates or is that disabled by your patch?
I don't want to accidentally lose your Plus-Features, because of new OUYA ota update.
Click to expand...
Click to collapse
Ahh that's right... you'll need to reflash cwm after applying the OTA update. My apologies as I forgot about that. ( maybe I'll add cwm to the patch so even if you apply an OTA it'll reinstall cwm. )
In terms of updating it's now user controllable... lets say an update comes out and it's one you want to move to and don't mind loosing any features... you can switch to using their update by changing whats in "UPDATE" to represent the latest info. By default though it's setup to not update.
IncognitoMan said:
Ahh that's right... you'll need to reflash cwm after applying the OTA update. My apologies as I forgot about that. ( maybe I'll add cwm to the patch so even if you apply an OTA it'll reinstall cwm. )
Click to expand...
Click to collapse
Mmh, isn't the recovery on a special recovery partition?
I don't think it's flashable via a zip file, as normally you flash the whole img.
Anyways it's not a problem for me to fastboot flash cwm again after installing ota. So thanks again.
EDIT: Well, just read it IS possible to flash via zip, sry sry sry.
IncognitoMan said:
In terms of updating it's now user controllable... lets say an update comes out and it's one you want to move to and don't mind loosing any features... you can switch to using their update by changing whats in "UPDATE" to represent the latest info. By default though it's setup to not update.
Click to expand...
Click to collapse
Great, that's what I want
Can't wait to get home for flashing, hehe
This is working great. Thanks!
Sent from my SAMSUNG-SGH-I747 using XDA Premium 4 mobile app
Thx man, its working flawlessly exceot for sudden fcs of google services when i download from the ouya store, other than that...amazing job!
BadWolff23 said:
Thx man, its working flawlessly exceot for sudden fcs of google services when i download from the ouya store, other than that...amazing job!
Click to expand...
Click to collapse
Is that after you activated the playstore xposed module?
prophetjinn said:
Is that after you activated the playstore xposed module?
Click to expand...
Click to collapse
It was at the very begining, now after couple reboots its alrite
IncognitoMan said:
Yes, the only one that's not included is xtheme engine because I'd need to remake the theme since there's quite a lot of changes.
It is... the easiest method of upgrading would be to download 1.2.858 from here and copy it to /sdcard/
Once in /sdcard/ reboot into cwm -> install zip from sdcard -> choose "RC-OUYA-1.2.858-r1_ota.zip" and flash it. Then go back into install zip from sdcard and install "SPP_1.2.858_RC1.zip" over it.
Click to expand...
Click to collapse
How do you get Netflix to stream in good quality without the HDMI external display option that was available on the old ROM?
evaporic said:
How do you get Netflix to stream in good quality without the HDMI external display option that was available on the old ROM?
Click to expand...
Click to collapse
Netflix outputs in good resolution after a while, it looks pretty bad because it takes no time buffering as opossed in a pc or smart tv.
Great work IncognitoMan....we owe you.
One question through: what changed that the icons in "Make/software" look so ****ty? Is it the theme?
did a complete wipe.
installed ouya stock rom, then installed patch.
no ethernet or wifi, even though the connection is made.
just no access to internet.
formatted once more.
installed stock ouya rom back.
no patch this time.
internet connection works.
any ideas?
Careless_ said:
did a complete wipe.
installed ouya stock rom, then installed patch.
no ethernet or wifi, even though the connection is made.
just no access to internet.
formatted once more.
installed stock ouya rom back.
no patch this time.
internet connection works.
any ideas?
Click to expand...
Click to collapse
In CWM when you select reboot and get prompted "ROM may flash stock recovery on boot. FIX?" did you make sure to select no? As it sounds like you are selecting yes which actually kills what I'm hooking into... ( which would explain the issues with that )
Ipse_Tase said:
Great work IncognitoMan....we owe you.
One question through: what changed that the icons in "Make/software" look so ****ty? Is it the theme?
Click to expand...
Click to collapse
Look at team ouya on that.... don't know why they did the whole "stretch to fit" but I'll look into it at some point once I get my machine back up...
-------------------------
Been busy and my old laptops GPU died ( RIP T61p ) so im pulling together parts from it and putting them into another T61... hence my inactivity.
IncognitoMan said:
Look at team ouya on that.... don't know why they did the whole "stretch to fit" but I'll look into it at some point once I get my machine back up...
Click to expand...
Click to collapse
It's not like I'm spending a lot of time in that screen
Quick question for you: I remember reading somewhere that Ouya will never get past JB 4.1 as it would break the BT controller functionality (I'm sketchy on details). Is that still true?
The only reason I care is because of the way Netflix handles DRM and as long as we're stuck below 4.3 we won't get HD.
It's sad to see I was able to upgrade my ancient Xoom to KitKat (used as a news reader and Sudoku machine by my GF) and even my Galaxy S (now an mp3 player) got SlimKat.
Google Play games
Has anyone been able to get the Google Play games service working on this ROM. I am getting errors trying to connect inside of games.
IncognitoMan said:
In CWM when you select reboot and get prompted "ROM may flash stock recovery on boot. FIX?" did you make sure to select no? As it sounds like you are selecting yes which actually kills what I'm hooking into... ( which would explain the issues with that )
Click to expand...
Click to collapse
I selected whatever option it gave me to prevent it from reflashing. So if it said "press yes to prevent", then that's what I pressed. I can't remember what the question was for certain, but I selected the preventative option.
So is it nothing to worry about, and should I just press the opposite?
ragregory said:
Has anyone been able to get the Google Play games service working on this ROM. I am getting errors trying to connect inside of games.
Click to expand...
Click to collapse
Known issue... haven't really looked into getting it to work either.
Careless_ said:
I selected whatever option it gave me to prevent it from reflashing. So if it said "press yes to prevent", then that's what I pressed. I can't remember what the question was for certain, but I selected the preventative option.
So is it nothing to worry about, and should I just press the opposite?
Click to expand...
Click to collapse
Correct... when it asks select "No" and all should work then.
suhide-lite is an experimental (and officially unsupported) mod for SuperSU that can selectively hide root (the su binary) from other applications. It can also toggle visibility of packages (such as SuperSU).
SafetyNet verified passing on 2017.08.10.
This is ultimately a losing game (see the next post). suhide may stop working at any time.
Requirements
- SuperSU v2.82 SR2 or newer (link)
- SuperSU installed in SBIN mode (default on O+)
- Android 6.0 or newer
- TWRP (3.0.2 or newer with access to /data), FlashFire is not (yet) supported.
Xposed
Not supported.
CyanogenMod/LineageOS
Not currently tested or supported. Might work, might not.
Custom kernels/ROMs
If they changed build props, they will probably fail SafetyNet check (for now).
Installation
First make sure you are using SuperSU in SBIN mode on Android 6.x and 7.x
- Boot into TWRP
--- adb shell: echo "BINDSBIN=true">/data/.supersu
--- OR: flash SuperSU Config and select Systemless SBIN mode
- Reflash SuperSU v2.82 SR2 or newer
- Reboot into Android at least once
With SuperSU in SBIN mode
- Flash the suhide ZIP in TWRP
- Reboot into Android
If your TWRP does not fully decrypt /data, reflashing the SuperSU ZIP and immediately flashing the suhide ZIP without rebooting in between may sometimes allow suhide to be installed as well where it would otherwise throw an error.
Usage
The suhide GUI available from your app drawer should be fairly self-explanatory. The About tab lists further instructions.
Advanced usage
You can manually add/remove/list entries to suhide's blacklist by using these commands:
/sbin/supersu/suhide/add UID-or-processname
/sbin/supersu/suhide/rm UID-or-processname
/sbin/supersu/suhide/list
App package names are usually the same as the process name, but not always. Using the UID is safer. You can find the UID by running 'ps -n' (6.x/7.x) or 'ps -An' (8.x). The UID is the first column, and is a 5-digit number starting with 10: 10xxx.
Uninstall
Remove /data/adb/su/suhide folder in TWRP's file manager. You can uninstall the suhide app through Android's settings.
Download
UPDATE-suhide-v1.09-20171001222116.zip
In case that bootloops, try the old v1.00 version, and let me know your device and firmware:
UPDATE-suhide-v1.00-20170809130405.zip
Sauce @ https://github.com/Chainfire/suhide-lite
Hiding root: a losing game - rant du jour
Quoting myself from the OP of the old suhide thread:
Chainfire said:
Most apps that detect root fall into the payment, banking/investing, corporate security, or (anit cheating) gaming category.
While a lot of apps have their custom root detection routines, with the introduction of SafetyNet the situation for power users has become worse, as developers of those apps can now use a single API to check if the device is not obviously compromised.
SafetyNet is of course developed by Google, which means they can do some tricks that others may not be able to easily do, as they have better platform access and control. In its current incarnation, ultimately the detection routines still run as an unprivileged user and do not yet use information from expected-to-be-secure components such as the bootloader or TPM. In other words, even though they have slightly more access than a 3rd party app, they still have less access than a root app does.
Following from this is that as long as there is someone who is willing to put in the time and effort - and this can become very complex and time consuming very quickly - and SafetyNet keeps their detection routines in the same class, there will in theory always be a way to beat these detections.
While reading that may initially make some of you rejoice, this is in truth a bad thing. As an Android security engineer in Google's employ has stated, they need to "make sure that Android Pay is running on a device that has a well documented set of API’s and a well understood security model".
The problem is that with a rooted device, it is ultimately not possible to guarantee said security model with the current class of SafetyNet tamper detection routines. The cat and mouse game currently being played out - SafetyNet detecting root, someone bypassing it, SafetyNet detecting it again, repeat - only serves to emphasize this point. The more we push this, the more obvious this becomes to all players involved, and the quicker SafetyNet (and similar solutions) will grow beyond their current limitations.
Ultimately, information will be provided and verified by bootloaders/TrustZone/SecureBoot/TIMA/TEE/TPM etc. (Samsung is already doing this with their KNOX/TIMA solutions). Parts of the device we cannot easily reach or patch, and thus there will come a time when these detection bypasses may no longer viable. This will happen regardless of our efforts, as you can be sure malware authors are working on this as well. What we power-users do may well influence the time-frame, however. If a bypass attains critical mass, it will be patched quickly.
More security requires more locking down. Ultimately these security features are about money - unbelievably large amounts of money. This while our precious unlocked bootloaders and root solutions are more of a developer and enthusiast thing. While we're all generally fond of shaking our fists at the likes of Google, Samsung, HTC, etc, it should be noted that there are people in all these companies actively lobbying to keep unlocked/unlockable devices available for us to play with, with the only limitation being that some financial/corporate stuff may not work if we play too hard.
It would be much easier (and safer from their perspective) for all these parties to simply plug that hole and fully lock down the platform (beyond 3rd party apps using only the normal APIs). Bypassing root checks en masse is nothing less than poking the bear.
Nevertheless, users want to hide their roots (so do malware authors...) and at least this implementation of suhide is a simple one. I still think it's a bad idea to do it. Then again, I think it's a bad idea to do anything financial related on Android smartphone that isn't completely clean, but that's just me.
Note that I have intentionally left out any debate on whether SafetyNet/AndroidPay/etc need to be this perfectly secure (most people do their banking on virus ridden Windows installations after all), who should get to decide which risk is worth taking, or even if Google and cohorts would be able to design the systems more robustly so the main app processor would not need to be trusted at all. (the latter could be done for Android Pay, but wouldn't necessarily solve anything for Random Banking App). While those are very interesting discussion points, ultimately it is Google who decides how they want this system to work, regardless of our opinions on the matter - and they want to secure it.
Click to expand...
Click to collapse
I still stand behind this statement I made a year ago.
I will add to this another concern that I've posted before: on the A/B layout devices such as the Google Pixel (XL), it is possible to detect the device is rooted with a handful of lines of code, and I do not see any way to beat this detection aside from custom kernels. As soon as this detection is added to SafetyNet, it is pretty much game over. Frankly I'm surprised it hasn't been added yet.
The new suhide-lite vs the old suhide
The old suhide was completely different under the hood. It proxied zygote and created two different process trees for the real zygote and descendants (apps), one with root and one without, and multiplexed app instantiation calls between them. The new suhide-lite uses a completely different mechanism to achieve a similar outcome (some apps with and some apps without root).
One thing the old suhide had and the new suhide-lite version does not, is full binder interception. It could listen to and change most API calls and responses between apps and the Android system dynamically. While this may not sound like a big deal to some, from a malware-perspective this is almost a holy-grail class hack. suhide only used it to hide application packages (such as SuperSU) from apps selectively, so for example the launcher could still find it, but to some games it was completely invisible.
The binder interception code was the part that really interested me and the desire to get that working was the driving force behind the old suhide implementation. The security measures in Android's November 2016 security update blocked the old mechanism and with it the binder interceptor. Of course, I have actually written the code to bypass those (naive) protections in turn, but since that implementation of suhide was possible to detect in other ways, I kept that patch private. It may still prove useful in other projects, so it didn't make any sense to burn those work-arounds.
It may be possible to port the interceptor to the new mechanism, but it would be a lot of work and I don't think I'll be doing it any time soon, if ever. The lack of this intercepter is what makes the new suhide lite. The new suhide is able to hide packages such as SuperSU from other apps and games, but it does so via a toggle mechanism (3x alternating volup/voldown) that hides and unhides them, rather than handling the whole thing transparently.
Changelogs
2017.10.01 - v1.09
- Remove ODM and OEM mounts
- Setpropex: set multiple properties
- Cleanup: remove /boot
2017.08.15 - v1.08
- Fix a process freeze issue
- Fix framework restart survival (stop && start)
- Fix double free crash
2017.08.11 - v1.07
- Startup: Fix parallelism
2017.08.10 - v1.06
- Startup: Disable parallelism (temporary?), causes things to break sometimes
2017.08.10 - v1.05
- GUI: Synchronize changing items with the same UID
- GUI: Hide system apps (UID < 10000)
- GUI: Fix UID / package display line to ellipsize instead of wrap
- Properties: Adjust various build, adb, debug and security properties
- Startup: Improve performance by running operations in parallel
- ZIP: Allow flashing directly after SuperSU switch from image to SBIN mode, without reboot in between
2017.08.09 - v1.00
- Initial release of new code
- For old code, see https://forum.xda-developers.com/apps/supersu/suhide-t3450396
FIRST! new suhide yay. My 6p is currently running N 7.1.2. STOCK ANDROID, NO customisation whatsoever. Will 2.82 SR2 automatically update the root to sbin mode? If yes is the echo command still needed then?
Sent from my Nexus 6P with Tapatalk
Ch3vr0n said:
FIRST! new suhide yay. My 6p is currently running N 7.1.2. will 2.82 SR2 automatically update the root to sbin mode? If yes is the echo command still needed then?
Sent from my Nexus 6P with Tapatalk
Click to expand...
Click to collapse
Sbin mode is only activated by default on O (as per OP). Everything else requires the echo command.
Cool. I was avoiding using Magisk so far and was without root to be able to use certain apps like Netflix. I have a Pixel XL. Will SuperSU 2.82 SR2 alongwith suhide-lite work on my phone? Will I have to give the commands in TWRP as given in op? I intend to flash August security patch and try this during that update process. Currently I am stock (no root) with ElementalX kernel which I intend to continue using to be able to hide bootloader unlocked status.
Wow.. this works!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Shamusent
@Chainfire
hi,
maybe you can do something about this :crying:
i'm on nougat 7.1.2 (July security patch) been trying for long time to get this to work on citrix secure hub (by zenprise- formally known as worx)
attaching my logs and pics.
this is what i found from the logs attached:
Code:
"com.citrix.work.MAM.PolicyCheck:Found an APK requiring rooted device: eu.chainfire.supersu"
"com.citrix.work.MAM.PolicyCheck:BuildTag Test advisory ----- > is probably rooted"
SuperUser APKs Test advisory ---- > is probably rooted
the only one thing it didnt find:
Code:
D/"SecureHub"(16939): su In Path Test --- > is NOT rooted
i manged to pass safety net as you can see.
please if you can help.
Hi all and Chainfire. Thank you for this app! I tested it with a search if the Netflix app in the Playstore, but it wasn't found. I hided Playstore app in the list. Is there something I have overseen?
Otherwise I am also passing Safety Net. Thank you Chainfire!
rocky78 said:
@Chainfire
hi,
maybe you can do something about this :crying:
i'm on nougat 7.1.2 (July security patch) been trying for long time to get this to work on citrix secure hub (by zenprise- formally known as worx)
attaching my logs and pics.
this is what i found from the logs attached:
Code:
"com.citrix.work.MAM.PolicyCheck:Found an APK requiring rooted device: eu.chainfire.supersu"
"com.citrix.work.MAM.PolicyCheck:BuildTag Test advisory ----- > is probably rooted"
SuperUser APKs Test advisory ---- > is probably rooted
the only one thing it didnt find:
Code:
D/"SecureHub"(16939): su In Path Test --- > is NOT rooted
i manged to pass safety net as you can see.
please if you can help.
Click to expand...
Click to collapse
Does citrix secure hub run constantly in the background, or do you just need it now and then ?
Have you read the instructions in the About screen as stated ?
Have you tried hiding the SuperSU GUI ? (3x volup/voldown alternate) Because that is what it's detecting.
It's not detecting the su binary, I assume you already hid root from the hub ?
TR2N said:
Hi all and Chainfire. Thank you for this app! I tested it with a search if the Netflix app in the Playstore, but it wasn't found. I hided Playstore app in the list. Is there something I have overseen?
Otherwise I am also passing Safety Net. Thank you Chainfire!
Click to expand...
Click to collapse
Try clear Google Play Store and Google Play Services app data.
Netflix shows for me on a freshly installed device.
Chainfire said:
Does citrix secure hub run constantly in the background, or do you just need it now and then ?
Have you read the instructions in the About screen as stated ?
Have you tried hiding the SuperSU GUI ? (3x volup/voldown alternate) Because that is what it's detecting.
It's not detecting the su binary, I assume you already hid root from the hub ?
Click to expand...
Click to collapse
1. i can use it how ever i want (background or now and then). this is an email from my company.
2. yes. tried that.
3. yes i did. i attached a pic for you to see in the previous replay.
rocky78 said:
1. i can use it how ever i want (background or now and then). this is an email from my company.
2. yes. tried that.
3. yes i did. i attached a pic for you to see in the previous replay.
Click to expand...
Click to collapse
But is SuperSU still available from the app drawer? Did you actually press the volume button as instructed? The screenshot does not (can cannot) show that.
Chainfire said:
But is SuperSU still available from the app drawer? Did you actually press the volume button as instructed? The screenshot does not (can cannot) show that.
Click to expand...
Click to collapse
no.
When im pressing in the right order its hidden from app drawer. Also some other apps gets hidden.
p.s.
from the log i uploaded before it looks like "they" are running a search of supersu.apk in my device and mannage to find that.
is there a way to hide/stop that?
rocky78 said:
no.
When im pressing in the right order its hidden from app drawer. Also some other apps gets hidden.
p.s.
from the log i uploaded before it looks like "they" are running a search of supersu.apk in my device and mannage to find that.
is there a way to hide/stop that?
Click to expand...
Click to collapse
In that case I don't know what's going on. They shouldn't be able to iterate over APKs either. But it's all just guess work on my end at this point.
EDIT: actually I do know of a way they could still detect this even when hidden... but really the only way around that is to uninstall the SuperSU APK.
TR2N said:
... I tested it with a search if the Netflix app in the Playstore, but it wasn't found....
Click to expand...
Click to collapse
I think Safetynet is a server side check.Wait till tomorrow with su hided and check again.
Chainfire said:
In that case I don't know what's going on. They shouldn't be able to iterate over APKs either. But it's all just guess work on my end at this point.
EDIT: actually I do know of a way they could still detect this even when hidden... but really the only way around that is to uninstall the SuperSU APK.
Click to expand...
Click to collapse
do you mean if i clean flash my rom (custom) without root i will be able to use it?
And if so... Wft? No way! The hell with them.
rocky78 said:
do you mean if i clean flash my rom (custom) without root i will be able to use it?
And if so... Wft? No way! The hell with them.
Click to expand...
Click to collapse
No, just uninstall the SuperSU app from Android settings. Your apps will still have root access, you just wont have any way to manage it.
Chainfire said:
No, just uninstall the SuperSU app from Android settings. Your apps will still have root access, you just wont have any way to manage it.
Click to expand...
Click to collapse
look at this....
Do you see in the log-pic? After hiding from app drawer took a log file and suhide worked.
Only one more thing left to hide.
wtf is build tag? is it related to ro.build.tags in props?
rocky78 said:
look at this....
Do you see in the log-pic? After hiding from app drawer took a log file and suhide worked.
Only one more thing left to hide.
wtf is build tag? is it related to ro.build.tags in props?
Click to expand...
Click to collapse
Only citrix knows
Code:
getprop | grep build
may show some obvious problems.
Updated version of this ROM: [ROM][TMOBILE][S7_SM-G930T][Oreo 8.0 Rooted][WifiCalling]G930TUVU4CRI2
ROM last updated: 10/30/2018
Introduction:
HUGE thanks to the guys that got this going like root & figuring out hybrid stocks! This ROM is a complete rewrite of my ROM [ROM][TMOBILE][S7_SM-G930T][Oreo Rooted] That ROM doesnt have WifiCalling & I couldn't get it to work for the life of me, so I rewrote it. I started with stock, and slowly stepped back making changes, reinstalling each time, confirming it still worked. About 200 installs later & 1000s of changes, this is the result. Yes, it took a LONG time. Hope you enjoy it! Don't forget to say Thanks so I know it is actually helpful to others, and continue doing this!
Description:
Stock Tmobile Oreo 8.0 modified (G930TUVU4CRF1)
EXTREMELY debloated! Nearly bare minimum, while still retaining hardware functionality. Eg, Samsung Gallery & Camera exist so we get 4k recording, and there aren't errors when we pull up the Gallery to edit, etc. Yes, this means NO Samsung or Android Pay. There could be more apps to debloat but Im out of time for now! (Please provide suggestions if interested)
Everything possible I replace Samsung with Google
Solid ROM. It was actually kind of slow for me, but I'm curious how this works for others.
Xposed is part of the guide, which will give you infinite customization & tweak-ability
If you hate Samsung SW and just want a solid working ROM with very few install options to get you up and running this is for you.
This will delete all of your data on the phone! (Not external SD card) This is the only way so don't ask. Backup your data!
Features:
Tmobile Wifi Calling works, along with Visual Voicemail & Mobile Hotspot
Many Aroma Installer app options
(Optional) KevinsFavorites option in Aroma. I'm not sure I'd recommend it due to my tastes. If you're looking for some good common apps tho, it includes: Amazon, AmazonMusic, AquaMail, Gmail, GoogleDrive, GoogleKeep, GooglePhoto, Hangouts, IFTTT, Pandora, RootBrowserClassic, TitaniumBackup, Uber, & Wink (If you install these and want to remove them later, use TitaniumBackup (or similiar) to uninstall
Root Features: See Downloads->Recommended Root Zip & say Thanks!
Debloated
De-Knoxed
Decrypted /data/ partition
OTAs disabled
Speed & Build Prop Tweaks
Dual speaker
Ruthless Launcher
Apps
AdAway
AOD Clock Face Themes
CPUSpy
DisableService
Kernel Adiutor
Samsung Video Editor and Trimmer
Xposed
Many more...
Download Links:
Base.7z & Oreo_Kevin71246Modded_v3.#.#.zip
Installation:
This will delete all of your data! If you continue, you acknowledge that the Author is NOT responsible for anything that happens to your phone!
Summary (for Pros)
Flash Oreo stock
Root
Flashfire
Oreo_Kevin71246Modded_v3.1.##, Auto-mount, Mount /system read/write Option
Go through Aroma setup. When finished, it should boot to Recovery (if not do this). Do a "Wipe data/factory reset"->Reboot
Detailed Steps
Install Stock Oreo:
Download mode & Setup
Make sure you have latest device drivers setup on your PC
Enable USB Debugging on phone in Developer Settings
Boot phone into Download Mode:
Turn off your device
Press and hold Volume Down + Home + Power button
When you see the warning screen, release buttons & press Vol UP. Phone should say "Downloading..."
Download and unzip Base.7z to PC (This contains stock Oreo, ODIN, & root)
ODIN
Open ODIN on PC (\Base\Odin_313.exe)
Connect USB from PC to phone. ID:COM in Odin should turn Blue with a COM port
Select AP, BL, CP and CSC files from the \Oreo_Stock\Base\ folder for corresponding files
Select HERO2QLTE_USA_VZW.pit
Select Start
Finished: Phone will reboot & show Carrier screen for 3-5mins. Wait until Setup screen & go through quickly (bare minimum) since you'll wipe it again. Once in Android, go to Settings->Display->Screen resolution->WQHD->Apply
Root Instructions: (+Flashfire, SuperSU)
Reboot phone into Download mode
Odin
AP: Select \Base\Root\AP_SM_G930_OREO_ENG_BOOT.tar
Start-> Wait for phone to boot to Android OS
Root
Double-click \Base\Root\cmd-here.exe & Type: root.bat [enter]
Option: 1 (Install Root No tweaks) (Or pick whatever you want)
*Note: With this system root, do not update su binary. Disable notifications for SuperSU app. Don't flash any superuser zips in recovery that are not made by jrkruse
Install Custom Hybrid ROM & Xposed
Download & copy Oreo_Kevin71246Modded_v##.zip to phone
Flashfire
Open Flashfire on phone
Red + symbol->Flash Zip or OTA->Oreo_Kevin71246Modded_v#, Auto-mount, Mount /system read/write Option->Check mark
Click Lighting bolt at bottom-> OK
Phone will reboot to Aroma. Go through setup. (See above for what's in KevinsFavorites)
When finished, allow Aroma to exit.
It should reboot into Recovery (If not, do this: immediately hold Vol-Up btn+Home btn until you see recovery on screen. If you missed it, try again: hold Vol-Down+Pwr btn ~10sec until phone restarts & immediately hold Vol-Up btn+Home btn until you see recovery on screen.)
In recovery: Factory Reset->Yes->Restart phone
*Wait 5-10min on loading screens
Go thru Android setup. Ignore "Xposed Installer has stopped" error
Followup-Steps:
Set Dialer: Phone Settings->Apps->Menu->Default Apps->Calling App->Select Phone
Recommendations:
Xposed
Setup Xposed: Xposed Installer app:Install framework option & restart phone
Xposed Installer app: Settings button (3 lines)->Download->Search "GravityBox [O]"->Click it->Versions tab->Download->Install->Back arrow (upper left)->Settings->Modules->Check box next to GravityBox [O]->Restart phone
GravityBox [O] Tweaks: (Open GravityBox app)
Battery indicator: Statusbar tweaks->Battery settings->Turn on Master switch->Battery indicatory style: None->Battery percent text...->Back
Clock: Statusbar tweaks->Clock settings->Turn on Master switch->Center clock...
Firefds Kit [O] Tweaks: (Install same way as Gravity box)
This is a supplement to Gravitybox. Things of note: Advanced power menu, call recording, & disable bluetooth toggle popup, etc
Known Issues:
Visual Voicemail may fail to register, but restart phone and give it a few hours. It works eventually.
RCS (Rich Communication Services/AdvancedMessages/Chat) texts don't show up in Android Messages & Textra, etc apps (This is an issue on stock as well!!)
Fix: (Use Samsung Messages)
How to Install Samsung Messages via ADB (Easiest way though is just reinstall!):
Download Messaging_SEP81.zip, unzip, & manually copy apk to phone via usb/Windows My Computer
adb shell (Get into shell to run beow commands)
su (Run as root)
mount -o rw,remount /system (Mount system read/write since default it read-only)
chmod 755 /system/priv-app/Messaging_SEP81 (Set permissions on folder)
chmod -R 644 /system/priv-app/Messaging_SEP81 (Set permissions on apk file)
ls -l /system/priv-app/Messaging_SEP81 (Check permissions - Should be: -rw-r--r-- 1 root root - not sure what 1 & 2 is)
ls -l /system/priv-app | grep "Messaging" (Check permissions - Should be: drwxr-xr-x 2 root root)
reboot (Reboot device)
Changelog:
Version 3.1.32: First stable build
Ver 3.1.36:
-Disabled encryption on /data/ partition to resolve "Bluetooth paired devices deleted after reboot" issue & so mods play nicer with ROM
-Fixed "Device not supported" error on Google Phone app
Ver 3.1.37:
-Added most of the apps I replaced or added as options in Aroma Installer now
Credits:
- @jrkruse & @klabit87 for Root
- @partcyborg for helping jrkruse
- @jrkruse for his similar ROMs as guides & help
- @Lanc-City for assistance in ROM modding
- @gustco for eng boot.img
- @Raymonf for modified odin
- @amarullz for Aroma Installer
- @Chainfire for FlashFire & SuperSU
- @rovo89 for Xposed
- @JaeKar99 for the cool & colorful boot animation
- @mrRobinson for AdAway ADAway.org
- Brandon Valosek for CPUSpy
- WangQi for DisableService
- Willi Ye for Kernel Adiutor
- @shubby for Ruthless Launcher
- @Craz Basics for Dual Speaker Mod
...
- Please PM me if you were forgotten!
Some screenies:
Saved2
Saved3
Well nice job!
jrkruse said:
Well nice job!
Click to expand...
Click to collapse
...but your'e the best! (You & I both know I couldnt have done it without all your other work!)
Once I FINALLY got WifiCalling to work, I thought... Imagine ALL the S7 XDA members out there with crappy Tmobile signal across Rural America that could TOTALLY use Wifi Calling!!! Haha, but seriously!! & that thought was the birth of this thread
kevin71246 said:
...but your'e the best! (You & I both know I couldnt have done it without all your other work!)
Once I FINALLY got WifiCalling to work, I thought... Imagine ALL the S7 XDA members out there with crappy Tmobile signal across Rural America that could TOTALLY use Wifi Calling!!! Haha, but seriously!! & that thought was the birth of this thread
Click to expand...
Click to collapse
Is this Ufirm firmware?
jrkruse said:
Is this Ufirm firmware?
Click to expand...
Click to collapse
I have so many FW packages on my PC at this point, from so many places that I used while trying to get this to work, but I think it might be a package from one of your threads(?) Since I'm not exactly sure what you're asking regarding "Ufirm FW", I'll elaborate hoping that answers your question. (Tho I'm thinking you mean the U variation/unlocked. So based on these stock files below I guess the answer is no.) If you're question is really, "is it possible to get tmobile wifi calling to work on a U model #", then I'd have to really think about that. But at this point I don't have an answer. I can tell you a million dependencies about it tho! (I seriously have hundreds of revisions I made while testing, & notes. The symbolic & meta links in Aroma initially broke it, as I found out after a week or so of testing - wish I knew a bit more about them, and why they're all there, then I'd know what was wrong about them...)
High-level process:
1)Flash Base/Stock/Oreo Rom:
- AP_G930TUVU4CRF1.tar
- BL_G930TUVU4CRF1.tar
- CP_G930TUVU4CRF1.tar
- CSC_TMB_G930TTMB4CRF1.tar
- HEROQLTE_USA_VZW.pit
2)Root with your method
3)Flash Xposed framework & my ROM (it's a "start with stock then remove what we don't want" type of Aroma/Edify script)
jrkruse said:
Is this Ufirm firmware?
Click to expand...
Click to collapse
BTW, any idea how to prevent the "verification failed" error I mention in the OP steps, after flashing Xposed framework? I tried flashing dm-noverity but no luck. At least my guide covers it at this point tho... Thanks again
kevin71246 said:
BTW, any idea how to prevent the "verification failed" error I mention in the OP steps, after flashing Xposed framework? I tried flashing dm-noverity but no luck. At least my guide covers it at this point tho... Thanks again
Click to expand...
Click to collapse
If you choose the keep safestrap option during root the it will flash the system/vendor/etc/ fstab.qcom that totally removes data encryption but when that fstab.qcom is flashed it also requires a data wipe for phone to boot then when you install xposed you won’t see that error but either way you end up wiping data so your choice
Sent using some kind of device I modified
It works perfectly!!
I have not had any problems so far, here I leave you for the link to download and try those who are interested in VIPER4ANDROID: https://drive.google.com/file/d/1572ORe6TOrsRBuxWWBChH-WMnxkvcUjH/view?usp=drivesdk
You just have to flash it with Flashfire, but if you do not pull them, let me know Thank you very much !!! Kevin for the effort!
---------- Post added at 10:17 PM ---------- Previous post was at 10:15 PM ----------
I have not had any problems so far, here I leave you for the link to download and try those who are interested in VIPER4ANDROID: https://drive.google.com/file/d/1572ORe6TOrsRBuxWWBChH-WMnxkvcUjH/view?usp=drivesdk
You just have to flash it with Flashfire, but if you do not pull them, let me know Thank you very much !!! Kevin for the effort!
First, I want to thank you so much kevin71246. I tried your previous version as I was sick and tired of how sluggish my phone felt after the last two T-Mobile OTA updates. So far the experience on the phone has been great but I wanted to post about an issue I had with that version to see if anyone else has come across it or can figure out what is going on. The reason I am making this a reply in this thread instead of your other is because I will be flashing this update shortly but I want to get the ball rolling on the issue first.
I went through the whole process, installing the minimum with Google Apps, though I did restore everything previously installed once I log in with my Goggle Account. I am unsure if this contributed to the problem but I will not be restoring apps on the next try. It seems no matter what process I attempt to connect my Ticwatch E to my S7 the Wear OS app will not recognize it which causes the watch to get stuck in the setup phase, making it useless. This was after multiple and different connection attempts, resets, reboots and factory (watch only) restores. The watch will show up under bluetooth and create the initial connection but it will not stay connected. Anyone have any idea? Is this ROM missing something?
Edit: Mid way through the install, I wanted to note that I checked for the issue after doing the "Install Stock Oreo" but before Root and everything worked as it should. Wear OS sees the watch instantly and Bluetooth connects fine.
Edit: So I am a day into using the ROM and I am still having issues. While it will connect and work perfectly fine now, when ever I do a reboot of the phone the watch no longer connects. I will just get constant Bluetooth Connection Requests, every single time the watch tries to get data, and it never actually connects. To fix this I need to do a complete reset of the watch and do the whole setup process again. As you can imagine this is no good, expecting to wipe my watch every time my phone reboots makes it still almost useless.
charredchar said:
First, I want to thank you so much kevin71246. I tried your previous version as I was sick and tired of how sluggish my phone felt after the last two T-Mobile OTA updates. So far the experience on the phone has been great but I wanted to post about an issue I had with that version to see if anyone else has come across it or can figure out what is going on. The reason I am making this a reply in this thread instead of your other is because I will be flashing this update shortly but I want to get the ball rolling on the issue first.
I went through the whole process, installing the minimum with Google Apps, though I did restore everything previously installed once I log in with my Goggle Account. I am unsure if this contributed to the problem but I will not be restoring apps on the next try. It seems no matter what process I attempt to connect my Ticwatch E to my S7 the Wear OS app will not recognize it which causes the watch to get stuck in the setup phase, making it useless. This was after multiple and different connection attempts, resets, reboots and factory (watch only) restores. The watch will show up under bluetooth and create the initial connection but it will not stay connected. Anyone have any idea? Is this ROM missing something?
Edit: Mid way through the install, I wanted to note that I checked for the issue after doing the "Install Stock Oreo" but before Root and everything worked as it should. Wear OS sees the watch instantly and Bluetooth connects fine.
Edit: So I am a day into using the ROM and I am still having issues. While it will connect and work perfectly fine now, when ever I do a reboot of the phone the watch no longer connects. I will just get constant Bluetooth Connection Requests, every single time the watch tries to get data, and it never actually connects. To fix this I need to do a complete reset of the watch and do the whole setup process again. As you can imagine this is no good, expecting to wipe my watch every time my phone reboots makes it still almost useless.
Click to expand...
Click to collapse
I believe I know what the issue is, I'm testing a fix (for THIS ROM) as we speak. Stay tuned. Maybe tomorrow if I have time and it works I'll update the OP. BTW, this ROM and my other ROM are TOTALLY different. Thanks for the feedback!
FranMLG said:
I have not had any problems so far, here I leave you for the link to download and try those who are interested in VIPER4ANDROID: https://drive.google.com/file/d/1572ORe6TOrsRBuxWWBChH-WMnxkvcUjH/view?usp=drivesdk
You just have to flash it with Flashfire, but if you do not pull them, let me know Thank you very much !!! Kevin for the effort!
Click to expand...
Click to collapse
What do you mean by this? "but if you do not pull them, let me know"
And tell me more about Viper4Android, and if it works solid for you on this ROM...then I'll consider adding it. Thanks!
New version, see change log in OP for details.
Yeah i.a give this a shot in a little. Do I need to root phone or can I just flash through Odin. Sorry not used to this locked bootloader crap..... s8crj1 are the last 6 digits of the software I'm on. I did receive the latest update will this effect me installing this. Sorry as I said not used to this locked bootloader crap.
jrkruse said:
If you choose the keep safestrap option during root the it will flash the system/vendor/etc/ fstab.qcom that totally removes data encryption but when that fstab.qcom is flashed it also requires a data wipe for phone to boot then when you install xposed you won’t see that error but either way you end up wiping data so your choice
Sent using some kind of device I modified
Click to expand...
Click to collapse
Hi, why you have to flash this - HEROQLTE_USA_VZW.pit on 930t, is it ROM specified? if I do and don't then what are pro and cons?
---------- Post added at 01:36 PM ---------- Previous post was at 01:26 PM ----------
josh2020glacier said:
Yeah i.a give this a shot in a little. Do I need to root phone or can I just flash through Odin. Sorry not used to this locked bootloader crap..... s8crj1 are the last 6 digits of the software I'm on. I did receive the latest update will this effect me installing this. Sorry as I said not used to this locked bootloader crap.
Click to expand...
Click to collapse
since bootloader is locked you can't use TWRP so you have to use Flashfire to install this ROM, as you know flashfire required root so you have to setup the base per OP and then root the base then install the ROM and then root it again, read the first page I don't think you will get a instructions more detailed then his
Okay so I just realised I was posting comments on the old thread, my bad. Coming back to the question, can the boot animation be changed? I've messed with the qmg files in an attempt to replace the weird, nauseating rainbow animation but even after overwriting the latter, it persists. Looking forward to a reply kek
Alkan3 said:
Okay so I just realised I was posting comments on the old thread, my bad. Coming back to the question, can the boot animation be changed? I've messed with the qmg files in an attempt to replace the weird, nauseating rainbow animation but even after overwriting the latter, it persists. Looking forward to a reply kek
Click to expand...
Click to collapse
Nauseating rainbow? LOL. Sorry. This is much more of a general question though, that wouldn't exactly pertain to this ROM specifically. And given I don't have an answer, I'd try searching BootAnimation How-Tos to get this customized. The ONLY thing I did regarding this was replaced the existing files with the rainbow ones. That's it. Apologies in advance.
Just discovered an issue: RCS (Rich Communication Services / Chat) texts don't show up in Android Messages app. See "Known Issues" in OP for a solution. BTW I posted a new ROM version a few days back that allows many choices in Aroma Installer. Make sure to pick Samsung Messages (instead of Google), so you get RCS chat text messages!
Android Open Source Project 7.1
Nougat
for
Ouya
Install Ouya Boot Menu before using this ROM. If you are not using Ouya Boot Menu then your device will be bricked. Dead forever.
Introduction:
The Ouya system partition is too small for Android 7 Nougat. The system partition is 512MB. The cache partitions is 768MB. The cache partition is large enough for Android 7. This ROM switches the two partitions. It installs the OS on the cache partition. It uses the system partition as cache.
The custom TWRP also switches the system and cache partition. The physical cache partition is mounted to the /system directory. The physical system partition is mounted to the /cache directory. I've named the TWRP version with "-SxC" to denote the "System / Cache switch".
Ouya Boot Menu looks for the boot.img on the physical (512MB) system partition. This ROM is installed on the physical (768MB) cache partition. If you ever need to wipe the /cache directory in TWRP SxC then the physical 512MB system partition is wiped. You must copy "/system/boot.img" to the physical (512MB) system partition which is mounted at "/cache". This can be done with the TWRP file manager in Advanced > File Manager.
Recovery:
TWRP-3.2.3-SxC is a modified recovery which does not support other ROMS because of the system/cache partition switch. Use CWM for other ROMS.
Remember: Use Ouya Boot Menu or risk bricking the device.
Installation:
Install Ouya Boot Menu
Install and boot TWRP-3.2.3-0-SxC
Wipe System, Cache, Data
Install the ROM
Install UNOFFICIAL-Magisk-v19.1-ouya.zip
Optional: Install Open Gapps
Downloads
Donate
Change log:
Code:
20190510
- Enable adoptable storage.
- Try to set resolutions by default.
Source:
https://github.com/Decatf/android_kernel_boxer8_ouya
XDA:DevDB Information
Android 7.1 Nougat, ROM for the Ouya
Contributors
decatf
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.1.x
ROM Firmware Required: Ouya Boot Menu
Based On: AOSP
Version Information
Status: Testing
Created 2019-05-06
Last Updated 2019-05-10
Display Resolution:
This ROM should be able to run at any resolution that a display panel reports to the Ouya. Some display panels don't report their resolutions properly. There is no way to add more resolutions.
This ROM (like AOSP 5.0 for Ouya) uses the closed source Nexus 7 display drivers. The stock Ouya drivers are too old, buggy, and don't work right on Android 7.
To set a display resolution on this ROM, use the persist.ouya.resolution system property. This must be set in /system/build.prop. Reboot the device to use the new resolution. Some of the display and resolution system properties that were used on older Ouya ROMs don't work on this driver.
Find out what resolutions a display panel is reporting to the Ouya:
Install Terminal Emulator for Android
Type cat /sys/class/graphics/fb0/modes
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Take note of which resolutions are supported by your display.
Edit the build.prop:
Install BuildProp Editor
Click the edit button
Change persist.ouya.resolution to a resolution supported by your display.
Click the save button.
Some display panels don't report their resolutions properly. The example I've shown is from a 1920x1200 DVI display panel but it doesn't report all of its resolutions properly. There is no way to add more resolutions.
Display resolution system properties:
Use this:
Code:
persist.ouya.resolution
Do not use these. They don't work:
Code:
persist.tegra.hdmi.resolution
persist.sys.hdmi.overscan
persist.sys.hdmi.overscan.val
There is code to handle bcm4334 wifi for the Anthracite model. It is untested because I don't have one. Let me know if it works.
Can't get this installed, tried cwm trying mlq boot menu won't install fails on 2 different zip, then installs in twrp but doesn't launch all I get is a black screen can you step by step exactly the guide to this please been waiting forever to get 6+ on ouya now we have 7.1 and I can't load it?
Ok got it running but the picture is tiny I have a 1920x1080 50" Panasonic TV don't understand if not rooted how I edit this build prop please help???
Find out what resolutions a display panel is reporting to the Ouya:
Install Terminal Emulator for Android
Type cat /sys/class/graphics/fb0/modes
Take note of which resolutions are supported by your display.
Edit the build.prop:
Install BuildProp Editor
Click the edit button
Change persist.ouya.resolution to a resolution supported by your display.
Click the save button.
Thanks for this got to recipe it now via sideload in twrp, then build off the official ouya root it flash Cwm then boot menu then the os, got my work cut out although have the ouya update in platform tools now so that bits easy.
Let you know how I get on but a big thanks for the guide mate. ?
Ok so back in android 7.1 got terminal produce max of 1920x1080p 60hz but I get no root message in build prop editor and it doesn't show me a option to access persist.ouya resolution I've searched in build prop editor as shown but doesn't exist, so assuming it's due to no root yet???
Any idea how to root and what to do next please.
---------- Post added at 10:28 PM ---------- Previous post was at 10:26 PM ----------
---------- Post added at 10:30 PM ---------- Previous post was at 10:28 PM ----------
---------- Post added at 10:37 PM ---------- Previous post was at 10:30 PM ----------
Ok figured it out but need root to edit it please, other question is do I add 60 after 1920x1080 to make it 60hz or simply put 1920x1080?
The main thing is getting root as lingo doesn't work for it on 7.1 so could you upload the zip if there is one to root the ouya on 7.1 Android please
Was able to adb pull but not adb push the build.prop file after editing in notepad++ in windows 10, it states read only file system, meaning has to be rooted i assume going around in circles waiting bricked it once rebuilt it 2-3 times allready trying 3 failed su zips online just can't understand it on a level to root it my self without a guide.
I think it's good had to load magisk after the 7.1 rom is allready installed not during install, basically load everything on get into the os, go back into the twrp recovery and reflash the provided ouya unofficial magisk zip and it is then in your apps it works as the root tool basically for those not knowing what it's for.
The prob is that it's still windowed in a tiny screen though after telling it to go 1920x1080 I'll try 1280x720 next and go through a lot I changed the dpi successfully though to 320 and writing is legable for now
UPDATE: changed the lot all different ways used changer apps to nothing modifies the screen size at all it's a panasonic tx-p50x50b 50 inch plasma 600hz with support for 720p and 1080p
Lowered the dpi again changed to 720p but still the same size screen it's not changing the resolution well frame size any way? May try a screen changer app hope it won't brick it?
So yeah I can change the density but not the resolution???????
---------- Post added at 02:48 AM ---------- Previous post was at 01:55 AM ----------
Then there was light, I finally figured it out, all I did was remove the # from line 57 before the word persist then placed the the cursor you write with that flashes behind the word persist hit delete until the word persist aligned to the hash above it in line 56 like this
And the finished result is awesome 1080p 60hz on a 50 inch tv, I'm getting a screen capture device soon hopefully so will then review it. For now I will be testing it as I'll be using it 24hrs a day pretty much it's cheap to run and now has full android 7.1.1 os wicked or what, it's been a long time coming and can't wait to test the functionality and compatability of the apps and games on it now, so for now peace out. Thanks to the op for all the help and making this possible.
Well I'm reinstalling ouya on it because I bricked it running xposed installer and the biggest problem no adoptive storage I can't install any games to internal storage not even dead trigger 2 it's too small storage, we need axposed to use any storage as internal via USB drives etc this has to be done before it's useable to be able to even install a game there needs to be some kind of work around for installation of large files sorry but as yet it's more or less unusable as a daily os for that one annoying reason, if you fix it can you let me well all of us know please.
I enabled it in developer options to install to external but every attempted install says no space available.
Uploaded a new version (aosp-7.1-ouya-20190510)
- Enables adoptable storage
- By default it will now try to pick a resolution so you probably don't need to set the system property anymore.
PHYSC-1 said:
Ok so back in android 7.1 got terminal produce max of 1920x1080p 60hz but I get no root message in build prop editor and it doesn't show me a option to access persist.ouya resolution I've searched in build prop editor as shown but doesn't exist, so assuming it's due to no root yet???
Any idea how to root and what to do next please.
---------- Post added at 10:28 PM ---------- Previous post was at 10:26 PM ----------
---------- Post added at 10:30 PM ---------- Previous post was at 10:28 PM ----------
---------- Post added at 10:37 PM ---------- Previous post was at 10:30 PM ----------
Ok figured it out but need root to edit it please, other question is do I add 60 after 1920x1080 to make it 60hz or simply put 1920x1080?
The main thing is getting root as lingo doesn't work for it on 7.1 so could you upload the zip if there is one to root the ouya on 7.1 Android please
Was able to adb pull but not adb push the build.prop file after editing in notepad++ in windows 10, it states read only file system, meaning has to be rooted i assume going around in circles waiting bricked it once rebuilt it 2-3 times allready trying 3 failed su zips online just can't understand it on a level to root it my self without a guide.
Click to expand...
Click to collapse
decatf said:
Uploaded a new version (aosp-7.1-ouya-20190510)
- Enables adoptable storage
- By default it will now try to pick a resolution so you probably don't need to set the system property anymore.
Click to expand...
Click to collapse
WOW!!! your amazing putting it on right now I'll be getting that screen capture device, I might tweak it with classicboy as been researching it all, add some favourite apks take some less required ones for me out and I'll drop it, might try making some custom backgrounds and that sort of thing it may take me a while I'll use some canva tweaks to do it with let you have the link when done, but major thanks for this everyone should have 7.1 ouya's soon then lol. Over the moon mate. :angel:
---------- Post added at 12:27 AM ---------- Previous post was at 12:23 AM ----------
I ironically just went to attempt adding apks to it like xposed etc and found it wondered what it was and came here to find the followup, so what I'll do is make it a little more custom none basic android looking if I can make some canva images for backgrounds and add in some games and so on in the apps folder and so on and so forth see if I can make an app after to link to the ouya games available onine I'll make that simple. that's if I can knock one up it will be a seriously grueling task finding multiple game links and cataloging them in the app but it's on the cards now.
It should help keep the games for ouya available free online to be archived and added to as a list of page links, not sure how to make it so intricate but I will find a way I usually do.
Just found it's .da new folder not the normal type any idea or link to a extraction tool for windows to add apps and change the backgrounds etc then repack it please?
I'm getting MTP host hass stopped and MTP Host Keeps Crashing messages, it won't format on 2 differnt drive with two different caddies?
It only seems to be with hdd caddy's it does it over a usb hub
Ok now it works to the point of moving the data adoptively and say not enough space with any hard drive used?
" 6. Optional: Install Open Gapps"
Where GAPPS for this rom? All Gapps I put is writing a ERROR
PS: Sorry for my English
Romanych said:
" 6. Optional: Install Open Gapps"
Where GAPPS for this rom? All Gapps I put is writing a ERROR
PS: Sorry for my English
Click to expand...
Click to collapse
go to https://opengapps.org/
Choose
Platform: "ARM"
Android: "7.1"
Variant: Well as you prefer it, i prefer "Nano"
Worked fine for me
Good Luck
Wow, that's great. Any hope for Android TV Launcher? Does Kodi and/or Plex client work?
BTW, Ouya's services are going down soon. Just got a notification from them.
Hi,
First of all, thank you for your work! I am very happy to see OUYA being kept alive by the community!
In your ROM, is it necessary to make the flash ouya-keylayouts.zip that is used in the version of LineageOS KitKat?
Ok, I installed this ROM.
Apparently everything was right, but I had two problems:
1 - Bluetooth starts off at every boot and I need to use a mouse to turn it on before using the OUYA controller.
2 - The controller of OUYA is, as I say, very unstable. If I try to move the cursor using the d-pad, it keeps moving to the right. I installed Kodi 18.2 and can not choose the options using the driver. I switched to another bluetooth controller, an Ipega-9028, but the problem persisted.
I've installed the ROM and it seems to work pretty well but has anyone got Kodi working with this? I can get it installed and I try to play a movie and it just freezes every time which is driving me crazy any ideas?
Cheers
Ok so I have now tried Netflix and it froze and required a hard power off to get it back so I don't think it is me doing something wrong, is there any chance this is something you are aware of as it would be great to be able to use Netflix and Kodi on this device again?
I am also suffering from the Bluetooth not enabled on start-up. Everything else works just fine.
Netflix and Kodi both work for me, maybe try and wipe/reinstall the rom?
swindillon said:
I am also suffering from the Bluetooth not enabled on start-up. Everything else works just fine.
Netflix and Kodi both work for me, maybe try and wipe/reinstall the rom?
Click to expand...
Click to collapse
Well I can try but I have tried this on Two different Ouya's and it seems to have done the same thing, I will give it another go.
Cheers