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
Related
{
"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.
So you want the latest Lollipop image for the 2012 Wifi Nexus 7, but no root and no TiBu is holding you back?
You can root the 2012 WiFi Nexus using WUGS Root Tool kit. Get it here -> http://www.wugfresh.com/nrt/
It's real easy to use and it walks you through what you need to do once it's installed. It will download the correct root kernel, boot image, recovery and root.
Once rooted, you can go to Play Store and download the latest TiBu. As of 11/14/2014, it has been updated to work with Lollipop. No need for the Beta version anymore.
It works. I just restored all my users apps from KK with this. Works like a charm. No issues so far.
Here's your Lollipop!
{
"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"
}
https://api.soundcloud.com/tracks/78714022/download?client_id=b45b1aa10f1ac2941910a7f0d10f8e28
4.4.4 ?
Does this work with 4.4.4 ?
Thanks
---------- Post added at 03:01 AM ---------- Previous post was at 02:43 AM ----------
Oops, never mind.
Stuck on 'Searching application data .... ' forever.. :/
I flashed factory images yesterday, so my device is unlocked and I'm attempting to root it.
I've downloaded the cf-auto-root-grouper-nakasi-nexus7.zip, rebooted into bootloader, did fastboot boot the .img, it does its thing and reboots. superSU is there but no binariers :/
I've tried it several times. At one point it kept rebooting to TWRP recovery, so re-flashed boot and system.img, boots up fine, all my stuff is still there along with SuperSU but still no binaries....
Hold on, let me try again with stock recovery.
update: Having TWRP recovery flashed was causing the issue. Reflashed stock recovery in bootloader, rebooted bootloader, booted the auto root image and rebooted. SuperSU is not complaining about missing binary.
Now I'm having difficulties with Busybox. At first it said devices wasn't properly rooted. So I downloaded root checker and it said device is rooted. reopened Busybox, granted it root permissions, hit install and gave me an error about improper root installation.
Tried again and now it's saying "can't verify the integrity of the binary selected to be installed" and requesting i exit and try again.
Great! Root work on Nexus 7 wifi 2012 and android 5.0. Thanks!
Used this method last night and it installed without a hitch but I am very disappointed on how slow, Laggy and darn right unusable 5.0 is. I will wipe and go again to see if it improves but if not I will be happy to stay on KK
Eddster3000 said:
Used this method last night and it installed without a hitch but I am very disappointed on how slow, Laggy and darn right unusable 5.0 is. I will wipe and go again to see if it improves but if not I will be happy to stay on KK
Click to expand...
Click to collapse
I went and did a full wipe and that seems to have helped. Also, after the setup, are you allowing it to reinstall apps from the cloud? That can cause it to be laggy until it's done.
Remember, we are also under ART now. Under Dalvik, applications, after initially installed, would have to be "recompiled" to cache them to the Dalvik cache. This occurred when the app was launched for the first time since being installed.
Under ART, it recompiles the apps once they are installed rather than waiting for them to be launched. So, if you are having a lot of apps being reinstalled, you'll notice it might take longer to install them, and hence, since it recompiles them after install, it could slow down your device, causing it to be laggy.
thanks for the guide, it did install supersu and busybox on my nexus 7 2012 with lollipop, however, titanium backup and others apps that require root aren't working, supersu is prompting to give permission on those but they cannot execute xbin/su command
gnrsenpai said:
thanks for the guide, it did install supersu and busybox on my nexus 7 2012 with lollipop, however, titanium backup and others apps that require root aren't working, supersu is prompting to give permission on those but they cannot execute xbin/su command
Click to expand...
Click to collapse
Did you launch SuperSU after rooting? Also, you to launch Busybox and actually tell it to install.
Did you enable USB debugging in developer options? TiBu won't work without that being enabled.
If you don't see developer options in your settings, then you need to go to the About Tablet section in system settings, and then tap on Build Number seven times.
After that, then the Dev Options will show up and you can enable USB Debugging there.
After that, you'll need to go back into TiBu and then restart it (or reboot).
iBolski said:
Did you launch SuperSU after rooting? Also, you to launch Busybox and actually tell it to install.
Did you enable USB debugging in developer options? TiBu won't work without that being enabled.
If you don't see developer options in your settings, then you need to go to the About Tablet section in system settings, and then tap on Build Number seven times.
After that, then the Dev Options will show up and you can enable USB Debugging there.
After that, you'll need to go back into TiBu and then restart it (or reboot).
Click to expand...
Click to collapse
hello, the first thing i did after flashing lollipop was enabling usb debugging and then rooted with the op's recommended tool, i left it that way untill now, i really don't know what could be the cause.
Sent from my GT-I9300 using Tapatalk
gnrsenpai said:
hello, the first thing i did after flashing lollipop was enabling usb debugging and then rooted with the op's recommended tool, i left it that way untill now, i really don't know what could be the cause.
Sent from my GT-I9300 using Tapatalk
Click to expand...
Click to collapse
After using WUGs toolkit to root, it tells you to first launch SuperSU and then install Busybox and ensure it's installed in /system/xbin. What they mean by that is actually launching the Busybox app and then installing all the links for the commands and such via the app itself. WUGs is just installing the apk itself but that doesn't set up Busybox. You have to actually launch the Busybox app and then tell it to install everything. That's probably why it can't find su.
Supersu just provides a way to prevent rogue apps from gaining root access without your permission. The actual "su" command is installed by Busybox.
Launch the Busybox app, tell it to install and then try again.
iBolski said:
After using WUGs toolkit to root, it tells you to first launch SuperSU and then install Busybox and ensure it's installed in /system/xbin. What they mean by that is actually launching the Busybox app and then installing all the links for the commands and such via the app itself. WUGs is just installing the apk itself but that doesn't set up Busybox. You have to actually launch the Busybox app and then tell it to install everything. That's probably why it can't find su.
Supersu just provides a way to prevent rogue apps from gaining root access without your permission. The actual "su" command is installed by Busybox.
Launch the Busybox app, tell it to install and then try again.
Click to expand...
Click to collapse
yes, i've also did install all the scripts provided by busybox, it's not the first time i've done it, that's why is really strange, maybe busybox is not correctly installing the su script (i marked the xbin folder instead of bin in busybox).
Sent from my GT-I9300 using Tapatalk
gnrsenpai said:
yes, i've also did install all the scripts provided by busybox, it's not the first time i've done it, that's why is really strange, maybe busybox is not correctly installing the su script (i marked the xbin folder instead of bin in busybox).
Sent from my GT-I9300 using Tapatalk
Click to expand...
Click to collapse
Then I'm at a loss. It worked the first the time I did it and then again when I decided to do a full wipe of my device. Not sure what is going on.
You did this via WUGs correct? And, when it asked what device you had, you chose Nexus 7 2012 with the Lollipop image, correct?
Just trying to make sure you didn't miss something.
iBolski said:
Then I'm at a loss. It worked the first the time I did it and then again when I decided to do a full wipe of my device. Not sure what is going on.
You did this via WUGs correct? And, when it asked what device you had, you chose Nexus 7 2012 with the Lollipop image, correct?
Just trying to make sure you didn't miss something.
Click to expand...
Click to collapse
yeah, furthermore i reflashed lollipop twice and redo the process all over again with no luck, nevertheless, thanks for your input ?
Sent from my GT-I9300 using Tapatalk
gnrsenpai said:
yeah, furthermore i reflashed lollipop twice and redo the process all over again with no luck, nevertheless, thanks for your input ?
Sent from my GT-I9300 using Tapatalk
Click to expand...
Click to collapse
Ok. Sorry I couldn't help. Hopefully, you can get it figured out.
You DO have the bootloader unlocked, correct?
iBolski said:
Ok. Sorry I couldn't help. Hopefully, you can get it figured out.
You DO have the bootloader unlocked, correct?
Click to expand...
Click to collapse
indeed, i can see the unlocked padlock when the device boots, before flashing lollipop i had a kitkat custom rom (forgot the name), so i did have to unlock the bootloader. the only thing i'm missing is the su command and i don't see it in the busybox checklist of scripts to install.
Sent from my GT-I9300 using Tapatalk
iBolski said:
After using WUGs toolkit to root, it tells you to first launch SuperSU and then install Busybox and ensure it's installed in /system/xbin. What they mean by that is actually launching the Busybox app and then installing all the links for the commands and such via the app itself. WUGs is just installing the apk itself but that doesn't set up Busybox. You have to actually launch the Busybox app and then tell it to install everything. That's probably why it can't find su.
Supersu just provides a way to prevent rogue apps from gaining root access without your permission. The actual "su" command is installed by Busybox.
Launch the Busybox app, tell it to install and then try again.
Click to expand...
Click to collapse
Wut? No, su is on the system by default. It is REPLACED by the supersu zip, with the supersu.apk to control it in Android.
Busybox has nothing to do with su.
khaytsus said:
Wut? No, su is on the system by default. It is REPLACED by the supersu zip, with the supersu.apk to control it in Android.
Busybox has nothing to do with su.
Click to expand...
Click to collapse
DOH! Don't know what I was saying there. My bad. :silly: Chalk it up to a long night last night with little sleep.
I followed the directions and everything worked. only thing now is that windows doesn't see the nexus7 so i can't copy the tibu backups over...do i need to install any additional drivers?
Storage space
Haven't seen this mentioned anywhere or maybe I'm not searching properly. I have the 16GB model and my storage is now down to 6GB, is there anything I can do to fix that? I used Wugs toolkit to install twrp but I can't find the folder in my internal storage.
I know you guys have waited FOREVER for somebody to pick this project up.... I have, and today I preset to you...ROOT
WARNNG: THIS DOES USE A CUSTOM KERNEL
Steps:
Unlock bootloader using this TUTORIAL:
http://forum.xda-developers.com/desire-510/help/qa-bootloader-unlock-htc-desire-510-t2911491
DO NOT FLASH RECOVERY FROM THAT THREAD
Grab boot.img from here:
http://goo.gl/AlaZpI
Old Versions:
http://goo.gl/dzQ3Wi
Load boot.img into fastboot folder
run this command:
"fastboot flash boot HTC-Desire-510-64bit-Root.img"
Install SuperSU from Play Store. Select cancel everytime it asks to update. It WON'T work
VigiDroid said:
Okay first things first let's get a couple things straight. SuperSU is the APPLICATION that allows for other applications to gain root access. When you first run SuperSU it will complain that the SU BINARIES are out of date. This is not important. It claims that you need a custom recovery (typically TWRP or CWM) to install the BINARIES, or you can try install it without it. This does not work, but it doesn't matter, since the out dated BINARIES still function correctly.
It is important to identify the difference between those two to avoid confusion though. SuperSU is the APPLICATION that allows root, and SU is the BINARIES which allow SuperSU to have root access.
I had trouble at first, but after a couple of initial reboots, SuperSU functioned correctly and granted root applications access. Once you have rebooted a few times, try download "root access checker" and run it to see if it works.
Click to expand...
Click to collapse
Good job rbheromax
thanks!
Thank you soo much
---------- Post added at 05:59 PM ---------- Previous post was at 05:32 PM ----------
I have started my phone succesfully with this kernel,but no root access (i have installed supersu alredy)
(I dont have recovery on my phone)
Sorry for my english.
I'm not a programmer or expert android but by unpacking the file boot.img, there are necessary files to root
{
"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"
}
I only checked to make sure that root could be accessed by shell. I'll upload another version with it having universal access
Sent from my XT1028 using XDA Free mobile app
rbheromax said:
I only checked to make sure that root could be accessed by shell. I'll upload another version with it having universal access
Sent from my XT1028 using XDA Free mobile app
Click to expand...
Click to collapse
Alright,thanks.
this will install su to /system as well as remove write protection
http://tempsend.com/33CE45F61D
rbheromax said:
this will install su to /system as well as remove write protection
http://tempsend.com/33CE45F61D
Click to expand...
Click to collapse
You gave me this file in private message,i have tried it and not worked,i had same problem
Edit: Its say there is no SU Binaries installed and SuperSu not installable......(i use SuperSU Free from google play)
Can anyone post a video which shows the process (and success!) of root the HTC Desire 510 64bit (EU)
Thanks
GianniDarkos said:
Can anyone post a video which shows the process (and success!) of root the HTC Desire 510 64bit (EU)
Thanks
Click to expand...
Click to collapse
Fix for root is coming soon,please be patient.
Ops ok, sorry
(I did not understand, I can not read english well)
http://goo.gl/AlaZpI
link updated in OP
it IS rooted, but you cannot update in-app using SuperSU. for some unknown reason, it wont work
use any other root managing app and you should be ok. try using koush's superuser app
Change Screen Size
Guys,
If you wanna be normaly screen size (not original sh.. screen sizes) than download this apk to your phone:
https://play.google.com/store/apps/details?id=com.nomone.resolution_changer&hl=hu
NOMone Resolution Changer (its free)
Open the app and you see
"Width" "Height" "DPI"
Change Width to 720
Change Height to 1280
Change DPI to 312
and click on apply
Or second way:
Open the app
Click on "Select device template"
and choose Motorola Moto X or Htc One X
Click on apply and you done
If you dont like this sizes,dont worry,apk will restore stock sizes after 10 sec and after 1 minutes too.
Good Luck to all.
rbheromax said:
http://goo.gl/AlaZpI
link updated in OP
it IS rooted, but you cannot update in-app using SuperSU. for some unknown reason, it wont work
use any other root managing app and you should be ok. try using koush's superuser app
Click to expand...
Click to collapse
Have you got a link please. I can't seem to find that one in particular
Burtrum57 said:
Have you got a link please. I can't seem to find that one in particular
Click to expand...
Click to collapse
Check the link in the OP? Hit the big blue download button on it and follow the instructions from the OP. In case you missed it, you have to use FASTBOOT to FLASH the KERNEL. So in other words, use this command: fastboot flash boot HTC-Desire-510-64-Bit-Root.img
VigiDroid said:
Check the link in the OP? Hit the big blue download button on it and follow the instructions from the OP. In case you missed it, you have to use FASTBOOT to FLASH the KERNEL. So in other words, use this command: fastboot flash boot HTC-Desire-510-64-Bit-Root.img
Click to expand...
Click to collapse
I've downloaded the kernal, fastboot flashed it and rebooted the phone and all is going well. Your correct supersu won't install without twrp or cwm. I have busybox installed and it is ok but a couple other apps complain that things aren't right.
Burtrum57 said:
I've downloaded the kernal, fastboot flashed it and rebooted the phone and all is going well. Your correct supersu won't install without twrp or cwm. I have busybox installed and it is ok but a couple other apps complain that things aren't right.
Click to expand...
Click to collapse
Okay first things first let's get a couple things straight. SuperSU is the APPLICATION that allows for other applications to gain root access. When you first run SuperSU it will complain that the SU BINARIES are out of date. This is not important. It claims that you need a custom recovery (typically TWRP or CWM) to install the BINARIES, or you can try install it without it. This does not work, but it doesn't matter, since the out dated BINARIES still function correctly.
It is important to identify the difference between those two to avoid confusion though. SuperSU is the APPLICATION that allows root, and SU is the BINARIES which allow SuperSU to have root access.
I had trouble at first, but after a couple of initial reboots, SuperSU functioned correctly and granted root applications access. Once you have rebooted a few times, try download "root access checker" and run it to see if it works.
You are right. All seems to be correct, I have root access, can copy, delete and move files with no problems. A couple apps do complain but if ignore them all still works well. Thank you so much. It may be a small step but it is a huge leap for what can now be done with this phone
/system/build.prop for Europe
Could someone on a European 510 please post their /system/build.prop file?
adb shell
su
cat /system/build.prop
...and since you're at it, could you post a stock (or not) TWRP backup? I know I am asking a lot, but after all I did help (in a very small way) @rbheromax in achieving root for you guys.
Thanks very much!
FINALLY Lenovo Yoga Tab 2 Pro 13.3" +Lollipop UPDATE NOV 2015 (for non root device)
This is the first somewhat official release of lollipop for the 1380F ::: Lenovo Yoga Tablet 2 Pro Android with Projector ::: avoid flashing this if your device is rooted
This update (as to my knowledge) was first released to some region and then perhaps pulled off. I'm I Japan and I did not receive this update
The original poster ionioni shared a download link in the lenovo forums
https://storage.rcs-rds.ro/links/9e7a1ddd-8aa9-4a47-a995-89b0a75fc25d
I have uploaded the same file to my rapidgator account
http://rg.to/file/5dfad2ef864bc65ac477139da26aa559
If any dev out there with androidfilehost.com cares to upload it there to would be great.
To install >>>>> if you never rooted <<<<
::: go to settings :: update :: upper right hand corner :: tool kit :: select downloaded zip
== so far so good, perhaps its a beta release but the word is so far that its better ==
**** you 99.999% might not be able to downgrade to KitKat ***
If it is a rooted device
By user ionioni
you should NEVER take an [ota] update AFTER you root. the rooting process modifies your system partition files and this is a problem because an update process will patch or replace files (and since Android 5.0 Google recomends the patch to be made against the whole system partition as a block patch, but it's not the YT2 case as they still use file patches), so if the files are modified by rooting, and they are, your update will fail and some of the files will be patched while others will not be and this will bring unexpected results: from minor ones to a complete hang.
so if you take an update always UNROOT before you take-it and reroot AFTER the update. that's no longer your case because you already screwed the system partition files, and the easiest way is to flash a stock rom (which ofcourse includes your system partition files among others) and this way you will restore the device.
but the problem (in your case) is that the stock rom you flash MUST match the bios version (KitKat rom matches an IA32 bios, while Lollipop matches an x64 one) and YOU HAVE after the Lollipop upgrade a Lollipop bios (x64) and you cannot just try to flash (as you did) a KitKat rom as this will fail (the files from your stock kitkat involved in the flashing process will fail to load because the bios is a x64 one and it wont accept files made for the IA32 architecture)
you have two solutions:
1. flash a stock Lollipop rom (but this is not yet made available by Lenovo, in general takes one or two months since the OTA before they release a complete updated rom)
2. return to KitKat bios and only AFTER you have downgraded the bios try and flash the kitkat (and after ofcourse you can re-take the Lollipop OTA). in this case again be careful, the one solution publicly available for returning to kitkat bios form lollipop is a 830/1050F and NOT a 1380F one (and i think noboy has tried yet a complete kitkat return). also be careful because the bios is not your mmc or sdcard drive, if you wrongly write it (with for wxample an incompatible version) you will HARD BRICK (and you will have no other solution but to send your tab to lenovo for fixing, it will be completely dead, no longer starting no lights nothing!).
MAJOR NOTES :::: IMPORTANT PLEASE READ ::::
by ionioni (original poster of the update)
Remember: if you have NO REGION configured when you do the Lollipop OTA update it will FAIL at the end and your tab will have errand behavior after the update (fails to boot, EFI shell, BIOS screen only, stuff like that) so remember to CHECK that you have a region configured BEFORE updating to Lollipop and if you don't have then set one. you most likely don't have one if you flashed back the stock kitkat rom at some point and didn't configuret one after.
check region: input in contacts the code ####59930# it should show a (your) region, if it shows Unknown you need to set a region
set (or modify) region: input in contacts the code ####6020# then chose your region, it will reboot and update (deleting your user data too so backup if required) after rebootyou can check region again and take the OTA
Little Notes
Your basic bloatware comes with the installation pacakge and that green security hd app is replaced by McFee, good news it is uninstallalbe.
The "downside" if any to this update is :: bottom drag up quick settings menu is gone and still uncertain if multiwindows is available. lenovo scratchpad works even better now.
Screenshots for the unbeliebers
{
"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"
}
Quick Tutorial to remove bloat **** Requires Root *** by ionioni
you install your rom or your ota and only afterwards you modify your os. from within a shell use pm command to first disable/block unwanted apps for testing first (so you can pm enable/unblock them if you do something wrong) and if ok you can pm uninstall them. be carefule as the tool will allow you to basically disable any app (system ones included) so you should pay attention, start with the more easier ones (for eg among others i disabled com.lenovo.videoplayer as i instaled mxplayer, com.lenovo.email i don't need it i have gmail app etc)
google for "Android package manager pm" for more info on what is and how to use the tool. root required ofcourse.
Are you running this? Is it stable?
grumpyrussian said:
Are you running this? Is it stable?
Click to expand...
Click to collapse
Yes I am. I have been running it for the past two hours. Others in the lenovo forum have been on it for more than a day or two. General feeling it is good.
Projector works fine, it seems like it is a pure android experience with their bloatware, most of it uninstallable.
I installed it as a ota update. It took some time but no errors or anything problematic. None of my installed apps or files were deleted.
With the KitKat version Firefox would crash and auto rotate function had major flaws.
I still have to see if Firefox crashes and if certain addons are available now.
I use rotate app by Fame It to solve my rotating issues. Since it remained after the update I will most likely not uninstall it.
Keyboard is google keyboard which is nicer.
The quick menu from the bottom drawer is no longer there, slightly sad but I don't care.
Everything seems faster too.
I will post updates if I notice anything strange.
ichiai said:
Yes I am. I have been running it for the past two hours. Others in the lenovo forum have been on it for more than a day or two. General feeling it is good.
Projector works fine, it seems like it is a pure android experience with their bloatware, most of it uninstallable.
I installed it as a ota update. It took some time but no errors or anything problematic. None of my installed apps or files were deleted.
With the KitKat version Firefox would crash and auto rotate function had major flaws.
I still have to see if Firefox crashes and if certain addons are available now.
I use rotate app by Fame It to solve my rotating issues. Since it remained after the update I will most likely not uninstall it.
Keyboard is google keyboard which is nicer.
The quick menu from the bottom drawer is no longer there, slightly sad but I don't care.
Everything seems faster too.
I will post updates if I notice anything strange.
Click to expand...
Click to collapse
That's good to hear, I think im going to give it a try.
grumpyrussian said:
That's good to hear, I think im going to give it a try.
Click to expand...
Click to collapse
If you having been wanting the lollipop I think its a must.
Another change is that now you have McFee antivirus app thing instead of the previous one, and this too is uninstallable
ichiai said:
If you having been wanting the lollipop I think its a must.
Another change is that now you have McFee antivirus app thing instead of the previous one, and this too is uninstallable
Click to expand...
Click to collapse
Oh great I just love bloatware.
grumpyrussian said:
Oh great I just love bloatware.
Click to expand...
Click to collapse
Lol
I wish there was Android development for this. I know this would be a killer tablet if it we could flash asop ROMs like cyanogen or dirty unicorns. I would install black Gapps and my world would be close to perfection.
ichiai said:
Lol
I wish there was Android development for this. I know this would be a killer tablet if it we could flash asop ROMs like cyanogen or dirty unicorns. I would install black Gapps and my world would be close to perfection.
Click to expand...
Click to collapse
Yes this, or even something like remix os: http://www.jide.com/en/remixos
That looks pretty sweet
copy/paste from another (mine) post in official lenovo forums
to remember: if you have NO REGION configured when you do the Lollipop OTA update it will FAIL at the end and your tab will have errand behavior after the update (fails to boot, EFI shell, BIOS screen only, stuff like that) so remember to CHECK that you have a region configured BEFORE updating to Lollipop and if you don't have then set one. you most likely don't have one if you flashed back the stock kitkat rom at some point and didn't configuret one after.
check region: input in contacts the code ####59930# it should show a (your) region, if it shows Unknown you need to set a region
set (or modify) region: input in contacts the code ####6020# then chose your region, it will reboot and update (deleting your user data too so backup if required) after rebootyou can check region again and take the OTA
thanks for sharing. ive been banned from lenovo forrums for three days. anyway, have you produced any roms for 1380F?
ichiai said:
thanks for sharing. ive been banned from lenovo forrums for three days. anyway, have you produced any roms for 1380F?
Click to expand...
Click to collapse
i'm happy with my android+linux combo, the extra a custom rom could bring is not worth the effort and i already have that extra plus more in linux. also the ui/bloatware can be easily tweaked to one's needs by removing the unwanted apk
so the short answer is no (at least for now)
ionioni said:
i'm happy with my android+linux combo, the extra a custom rom could bring is not worth the effort and i already have that extra plus more in linux. also the ui/bloatware can be easily tweaked to one's needs by removing the unwanted apk
so the short answer is no (at least for now)
Click to expand...
Click to collapse
Damn that's pro == "that extra plus more in Linux" ==
:: I just unpacked the zip and feel too n00b. Could I hardbrick if I delete an apk that I'm not supposed to delete? I have a feeling the answer is yes.
ichiai said:
Damn that's pro == "that extra plus more in Linux" ==
:: so to confirm, if I unpack the zip and delete the apks and repack it will all be good?
Click to expand...
Click to collapse
you install your rom or your ota and only afterwards you modify your os. from within a shell use pm command to first disable/block unwanted apps for testing first (so you can pm enable/unblock them if you do something wrong) and if ok you can pm uninstall them. be carefule as the tool will allow you to basically disable any app (system ones included) so you should pay attention, start with the more easier ones (for eg among others i disabled com.lenovo.videoplayer as i instaled mxplayer, com.lenovo.email i don't need it i have gmail app etc)
google for "Android package manager pm" for more info on what is and how to use the tool. root required ofcourse.
ionioni said:
you install your rom or your ota and only afterwards you modify your os. from within a shell use pm command to first disable/block unwanted apps for testing first (so you can pm enable/unblock them if you do something wrong) and if ok you can pm uninstall them. be carefule as the tool will allow you to basically disable any app (system ones included) so you should pay attention, start with the more easier ones (for eg among others i disabled com.lenovo.videoplayer as i instaled mxplayer, com.lenovo.email i don't need it i have gmail app etc)
google for "Android package manager pm" for more info on what is and how to use the tool. root required ofcourse.
Click to expand...
Click to collapse
Thanks for the quick tutorial. I'm glad I asked. I was about to just unpack delete apks and the repack and flash.
I don't have root and I feel challenged to follow your advice. Will add this info.
and this is a list of my disabled packages (their names are self-explanatory), of course you can add remove from the list, it's just what i don't use, don't need
com.google.android.apps.books
com.google.android.apps.docs
com.google.android.apps.genie.geniewidget
com.google.android.apps.magazines
com.google.android.apps.messaging
com.google.android.music
com.google.android.play.games
com.google.android.talk
com.google.android.youtube
com.lenovo.anyshare.gps
com.lenovo.deskclock
com.lenovo.email
com.lenovo.fingerpaint
com.lenovo.lenovodaydream
com.lenovo.lps.cloud.sync.row
com.lenovo.paperdisplay
com.lenovo.smartswitch
com.lenovo.videoplayer
com.lenovo.weather.theme.dreamlandPad
you can disable with pm disable package_name
or enable with pm enable _package_name
this is from a pm i had with an 1380F owner. moral of the story ALWAYS UN-ROOT before you take an update
Re: Yoga 2 Pro Update
Originally Posted by USERNAME_DELETED
I asked somebody to borrow me a Micro SD Adapter, so I can format my SD card to fat32 on windows 10 today.
I copied your small update file on the SD Card and flashed it under 5.0.1 recovery and it seemed fine. Unfortunately, my Yoga just would NOT boot up ever after. I thought maybe the problem is I rooted it after upgraded it to 5.0.1
Unfortunately, I spent over 8 hours keep flashing it back to KitKat stock rom after having a problem of booting up right after flashing your small update file and it just didn't work at all.
so, what can I do now ? can I just flash it back to 5.0.1 ? or do I have to do it under KitKat ??
if so, how can I flash it back to KitKat then ? any idea ??
Click to expand...
Click to collapse
yes, as you said, the problem is that you should NEVER take an update AFTER you root. the rooting process modifies your system partition files and this is a problem because an update process will patch or replace files (and since Android 5.0 Google recomends the patch to be made against the whole system partition as a block patch, but it's not the YT2 case as they still use file patches), so if the files are modified by rooting, and they are, your update will fail and some of the files will be patched while others will not be and this will bring unexpected results: from minor ones to a complete hang.
so if you take an update always UNROOT before you take-it and reroot AFTER the update. that's no longer your case because you already screwed the system partition files, and the easiest way is to flash a stock rom (which ofcourse includes your system partition files among others) and this way you will restore the device.
but the problem (in your case) is that the stock rom you flash MUST match the bios version (KitKat rom matches an IA32 bios, while Lollipop matches an x64 one) and YOU HAVE after the Lollipop upgrade a Lollipop bios (x64) and you cannot just try to flash (as you did) a KitKat rom as this will fail (the files from your stock kitkat involved in the flashing process will fail to load because the bios is a x64 one and it wont accept files made for the IA32 architecture)
you have two solutions:
1. flash a stock Lollipop rom (but this is not yet made available by Lenovo, in general takes one or two months since the OTA before they release a complete updated rom)
2. return to KitKat bios and only AFTER you have downgraded the bios try and flash the kitkat (and after ofcourse you can re-take the Lollipop OTA). in this case again be careful, the one solution publicly available for returning to kitkat bios form lollipop is a 830/1050F and NOT a 1380F one (and i think noboy has tried yet a complete kitkat return). also be careful because the bios is not your mmc or sdcard drive, if you wrongly write it (with for wxample an incompatible version) you will HARD BRICK (and you will have no other solution but to send your tab to lenovo for fixing, it will be completely dead, no longer starting no lights nothing!)
sure thing a solution must exist for a 1380f Lollipop bricked, but it takes some time (a few things to test again)...
update: done testing http://forum.xda-developers.com/thinkpad-tablet/general/yoga-tab-2-830-1050-1380-to-kitkat-t3240487
yes lollipop and next..
okiiiii lenovo tab 2 1380f turn with lollipop 5.0.1...
root mmmm ok...
but il i try to install xposed ...bad news blank screen on boot ... and reset bootloader..install K.K. etc etc (soft brick..but easy to reset)
Someone success to install xposed on 5.0.1 for 1380f ?
an idea ? it's sdk21 for x86 i suppose...
thanks a lot
fab
help yoga 1380f
I have a setup error "install failure" how to fix it?
rafal9426 said:
I have a setup error "install failure" how to fix it?
Click to expand...
Click to collapse
I am getting the same error.. Fully unrootedd and changed the language to u.s
Sent from my YOGA Tablet 2 Pro-1380F using Tapatalk
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