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
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
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
https://yadi.sk/d/aDqvPskH3EaeFX
Based on the 3.10 kernel... (for the first revision, Android 5.1) Beta-try, chase, complain, correct.))
The same Resurrection Remix with the system settings
Features and changes:
Very fast firmware in the likeness of Resurrection Remix
The latest source code for AOSP/LOS
Combines various features from LOS, RR, Paranoid Android, SlimRoms, OmniRom, etc.
Support Substratum Theme Engine
There is a good feature called LTE. It disables only voice calls and WIFI works.Not to be confused with airplane mode
Fixed Offline charging
Root is built-in is enabled in developer options
Gapps sewn.
So this is android 5.1 or 7.1 ? I'm willing to try it on my elephone M2.
NLSteve said:
So this is android 5.1 or 7.1 ? I'm willing to try it on my elephone M2.
Click to expand...
Click to collapse
7.1.1.
I have a problem installing this.
Update: I think the problem is I encrypted phone before installing this using 9x9 grid. I will decrypt phone and try again.
I used TWRP 2.8.7.3 (megthebest) -> install crDroidAndroid-7.1.1-20170223.zip
FAILED
Updating partition details...
...done
" E:Resource (image)-(background) failed to load "
E:Error executing updater binary in zip '/external_sd/crDroidAndroid-7.1.1-20170223.zip
Click to expand...
Click to collapse
Error flashing zip '/external_sd/crDroidAndroid-7.1.1-20170223.zip'
Updating partition details...
...done
NLSteve said:
I have a problem installing this.
Update: I think the problem is I encrypted phone before installing this using 9x9 grid. I will decrypt phone and try again.
I used TWRP 2.8.7.3 (megthebest) -> install crDroidAndroid-7.1.1-20170223.zip
FAILED
Error flashing zip '/external_sd/crDroidAndroid-7.1.1-20170223.zip'
Updating partition details...
...done
Click to expand...
Click to collapse
TWRP 3.0 It is necessary to use
update:
Listed: 02/25/2016 11:30 pm
ROM Version: TWRP M2 3.0.0
http://www.needrom.com/wp-content/uploads/2016/02/TWRP-3.0.0-Elephone-M2-megthebest.rar
NLSteve said:
update:
Listed: 02/25/2016 11:30 pm
ROM Version: TWRP M2 3.0.0
http://www.needrom.com/wp-content/uploads/2016/02/TWRP-3.0.0-Elephone-M2-megthebest.rar
Click to expand...
Click to collapse
What is it?
NLSteve said:
update:
Listed: 02/25/2016 11:30 pm
ROM Version: TWRP M2 3.0.0
http://www.needrom.com/wp-content/uploads/2016/02/TWRP-3.0.0-Elephone-M2-megthebest.rar
Click to expand...
Click to collapse
You tried to link to
duffi200000 said:
You tried to link to
Click to expand...
Click to collapse
yes. This is working download link for TWRP 3.0
---------- Post added at 01:53 PM ---------- Previous post was at 01:14 PM ----------
To get working Wi-Fi set country Wi-Fi region code to Europe or Germany that did the trick.
So far so good. Nice OS you have here. All good still runnning.
I'm noticing this OS is faster compared to cyanogen
Android 7.1.1 has issues with:
- Gboard keyboard disappearing when typing.
Solution: Install keyboard app like swiftkey.
- File transfers USB: files to Windows or Mac (MTP) does not work.
Solution: use transfer photo (PTP) and copy files to DCIM folder, later move files with an explorer app on the phone.
- No support for Xposed framework as of yet. Read latest post by Rovo89
NLSteve said:
yes. This is working download link for TWRP 3.0
---------- Post added at 01:53 PM ---------- Previous post was at 01:14 PM ----------
To get working Wi-Fi set country Wi-Fi region code to Europe or Germany that did the trick.
So far so good. Nice OS you have here. All good still runnning.
I'm noticing this OS is faster compared to cyanogen
Android 7.1.1 has issues with:56
- Gboard keyboard disappearing when typing.
Solution: Install keyboard app like swiftkey.
- File transfers USB: files to Windows or Mac (MTP) does not work.
Solution: use transfer photo (PTP) and copy files to DCIM folder, later move files with an explorer app on the phone.
- No support for Xposed framework as of yet. Read latest post by Rovo89
Click to expand...
Click to collapse
http://4pda.ru/forum/index.php?showtopic=678045&st=5240#entry52552870
Try that, that's what I was able to set the phone to the computer, everything works fine. And Yes the firmware is still a test, but she's really smart, the problem with the camera can't decide
Thank you, I will try that for usb connection to computer.
This is a nice rom overall. @duffi : Did you find 56 issues? i see you added this to my text "Android 7.1.1 has issues with:56 "
If anyone needs advice or a step-by-step guide to install on elephone M2, feel free to ask!
Hi NLSteve,
can I get a step by step guide for install 7.1.1 on M2? I use 5.1 latest rom and I have root on the prhone.
How To Install CrDrooid Android 7.1 on Elephone M2
Make sure you save your contacts and essential info to SD card or computer.
If for any reason your phone is encrypted, change the unlock code to pin 4 numbers! if you use pattern larger than 3x3 or more complex pin you're screwed XD
For this guide, you will need:
Sp-flash-tool-v5-1648 (latest version)
TWRP M2 3.0 (megthebest)
CrDrooid Android 7.1
SR3-SuperSU-v2.79-SR3 (latest version)
Copy the ROM and supersu to External SD Card.
TWRP flashing with SP Flash Tool
1. Shut down your phone and Disconnect usb cable from pc.
3. Run SP Flash Tool and navigate to 3rd tab Download, load download agent MTK_AllInOne_DA.bin and load MT6753_Android_scatter-TWRP3.txt for your phone.
4. Only have recovery checked and keep the option Download Only.
5. Click Download button and connect your phone (which is off) with PC via USB cable. Process should start. After process (60 seconds or more) is finished you will see green circle on screen again. Unplug USB from phone.
6. Turn on by pressing Power and Volume +, hold for 10-20 seconds until boot into TWRP recovery mode.
Installing ROM
1. Go to Wipe. Go to Advanced Wipe. From here, tick the boxes next to Dalvik Cache, System, Data and Cache, then swipe the slider at the bottom to perform a full wipe.
2. Go back to Install and browse to the location where you saved the file and select the crDroidAndroid-7.1.1-20170223.zip file
3. When done tap Reboot to boot into Android.
4. After system done, shut down to recovery and install supersu.zip by browsing to the location of Supersu.zip and choose install.
This is it for now. Good luck!
Hi NLSteve, it works, Antutu 39965 Points. But camera is not working, Fingerprint is not working and Bluetooth is also not working, its flaky. Phone M2 works faster then stock ROM 5.1. What I do missing is the function for updates next time. Great work. Hall Sensor is also not working. Thx.
Hi @volobobo, sorry to hear to hear you miss many functions. For me the camera and bluetooth is working though. :S
Hall effect sensor is used to detect flip covers? I just use close proximity sensor on camera to turn off screen.
@NLSteve
NLSteve said:
Hi @volobobo, sorry to hear to hear you miss many functions. For me the camera and bluetooth is working though. :S
Hall effect sensor is used to detect flip covers? I just use close proximity sensor on camera to turn off screen.
Click to expand...
Click to collapse
Hi NLSteve, camera is really working? Bluetooth is also really working? I have paired with my bluetooth headphones. If so I will keep it a new try. Hall sensor was a misstake on M2, we have one proximity sensor.
Is SIM card working? My ports for other Phone works except sim card recognition.. Bad thing.. therefore I ask.. good to read that you make roms for the M2, which is not a current phone.
Gesendet von meinem SM-G900F mit Tapatalk
Ehy what about making an updated version?
What suprise - M2 isnt dead
Hi all,
since eragon give up because his broken phone, nothing is going forward with our M2,
always stuck on the old Android 5.
Now, we could make a jump to 7.1.
Only a test version by now, but nice to see, there are more options with this hardware.
Unfortunally, my camera changed from an resolution from 13 MP to 5,3 MP. The focus doesnt function (sharpness) in short distance under 50 centimeter.
I tried several camera apps in the last view days. But no one solved that problem.
I looked in the build.prop, but have really no idea, what i can do do rechange to 13 MP.
So, the camera is like dead, i cant get any acceptable pictures by now. :crying:
Have anybody an solution for this problem?
Thanks to all, spending so much time and energy, to keep this phone alive. :good:
Please anyone re-upload link.
I have ported EFIDroid (developed by @m11kkaa) to the Snapdragon variants of the Samsung Galaxy Note 4/Note Edge.
@m11kkaa's original EFIDroid thread here: https://forum.xda-developers.com/android/software-hacking/efidroid-t3447466.
This is an unofficial port of beta software. I am not responsible for anything that may happen to your device. Use at your own risk.
Note: This has been tested with Samsung stock ROM, EmotionOS 7.1.1, and TWRP 3.0.2-0 on an SM-N910V/trltevzw. All other configurations are untested by me, but should work.
Confirmed working on:
- SM-N910V (trltevzw) (my device)
- SM-N910T (trltetmo) (thanks @viewsfromthepi)
- SM-N910G (trltedt) (thanks @Preet Juneja)
- SM-N910P (trltespr) (thanks @carlosggb)
- SM-N910W8 (trltecan) (thanks @d3multimedia)
- SM-N910F (trltexx) (thanks @cod_r) (possibly some issues with multiboot)
- SM-N915FY (tbltebtu) (thanks @jpearn)
- SM-N915F (tbltexx) (thanks @Juank2007)
I believe this works on all Snapdragon variants. If you're willing to test a variant not listed above, follow the instructions below, and post below if you had success, or if you encountered any issues.
Warning: There have been reports of the app failing to backup the boot/recovery partitions on other devices, leaving the device unable to boot to the OS and/or recovery. I have no way of testing whether this happens on the Note 4, so be ready with a working recovery/boot img on your computer...
I believe this issue does not affect the Note 4, as there have been successful installs with the app. However, I am leaving the related info on how to recover below, just in case this happens to one of you.
Installation
Install the attached EFIDroid Manager apk. Since this is an unofficial port, the EFIDroid Manager app from the Play Store won't work.
Open the EFIDroid Manager app, open the menu (at the top left), and click "Install/Update".
Click the big orange Install button.
And voila, you're done in 3 easy steps! Reboot to see your new 2nd-stage bootloader!
Post below with your variant/installed ROM if you have success.
To update EFIDroid, just repeat step 2, and the click the big orange Update button.
The app won't automatically check for updates, so I'll post an announcement on this thread whenever an important update is available.
Multibooting
You can use EFIDroid as a multiboot manager. To add a multiboot ROM, do the following:
Open the EFIDroid Manager app. Press the plus button at the bottom right side of the screen to start adding a multiboot slot.
Under "Location", there should be a couple paths. Select the one containing "/data/media/0" if you want the new slot to reside on the internal SD card (recommended for speed). Select the one containing "/mnt/media_rw/" if you want the new slot to reside on the external SD card.
You can give the slot a name/description by using the appropriate fields.
Press the checkmark at the top right side of the screen to create the multiboot slot.
Reboot. When EFIDroid comes up, select TWRP, then select the newly created slot.
Go to the "Wipe > Advanced Wipe" menu. Select "System", then swipe to wipe.
Install all the zips you want on that slot.
Reboot, and when EFIDroid comes up, your new slot should automatically be selected. Press the power button to boot, and enjoy!
Migrating from Dual Boot Patcher
Coming soon!
Troubleshooting
If you are unable to boot the OS/recovery from EFIDroid, do the following (you do have a working boot.img and recovery.img, right?)
This assumes you have fastboot properly setup.
In EFIDroid, use the volume keys to navigate to "Fastboot", the press the power key to select it.
There should only be one entry in the Fastboot menu. Press the power key to select it.
Connect your phone to your computer with a USB cable. Run the following (on the computer), one line at a time:
Code:
fastboot flash boot <path/to/boot.img>
fastboot flash recovery <path/to/recovery.img>
fastboot oem exit
In EFIDroid, use the volume keys to navigate to the back button at the top of the screen. Press the power key to select.
Use the volume keys to navigate to "Reboot", then press the power key to select.
If Maintenance Mode comes up, press the home button to reboot.
You should be able to boot the installed OS/recovery now. If this doesn't work, you can always Odin a TWRP tar, and then flash your original boot.img from inside TWRP, to get back up and running again.
Known Bugs
Aroma installers in TWRP may flicker, rendering them unusable.
Again, all credit goes to @m11kkaa for doing all the hard work in developing EFIDroid.
XDA:DevDB Information
EFIDroid, Kernel for the Verizon Samsung Galaxy Note 4
Contributors
abraha2d, m11kkaa
Source Code: https://github.com/efidroid
Kernel Special Features: UEFI, MultiBoot
Version Information
Status: Beta
Current Beta Version: 0.1
Beta Release Date: 2017-03-18
Created 2017-03-19
Last Updated 2017-07-03
I have the Sprint model. Is it safe to try?
Anyone try this yet.?
aaron74 said:
I have the Sprint model. Is it safe to try?
Anyone try this yet.?
Click to expand...
Click to collapse
I believe the Sprint variant is similar enough hardware-wise to the Verizon variant.
As with everything, make sure you backup, and store the backup somewhere other than your phone.
That being said, I believe there are no risks, other than possibly an hour or so of downtime (if something goes wrong with the installation). Since EFIDroid only modifies the boot and recovery partitions, if something goes wrong, you can always flash TWRP via Odin, and then in TWRP flash the boot.img from whichever ROM you're currently running to get back up and running.
If you're willing to wait, I have a friend who has volunteered to test this out on his Sprint variant in a week or two (when he gets his daily driver back).
There is my error now ... what boot and recovery img are you talking about??
Neuken69 said:
There is my error now ... what boot and recovery img are you talking about??
Click to expand...
Click to collapse
Trying clearing the data of the EFIDroid Manager app.
abraha2d said:
Trying clearing the data of the EFIDroid Manager app.
Click to expand...
Click to collapse
Same error
---------- Post added at 10:54 PM ---------- Previous post was at 10:16 PM ----------
im runnng aurora ROM now and i swap between that and Noble ROM not sure if that plays into the error
---------- Post added at 10:55 PM ---------- Previous post was at 10:54 PM ----------
im runnng aurora ROM now and i swap between that and Noble ROM not sure if that plays into the error
---------- Post added at 11:14 PM ---------- Previous post was at 10:55 PM ----------
If you have devices.json in that folder and your running a n910v ... can you share that file?
Neuken69 said:
Same error
---------- Post added at 10:54 PM ---------- Previous post was at 10:16 PM ----------
im runnng aurora ROM now and i swap between that and Noble ROM not sure if that plays into the error
---------- Post added at 10:55 PM ---------- Previous post was at 10:54 PM ----------
im runnng aurora ROM now and i swap between that and Noble ROM not sure if that plays into the error
---------- Post added at 11:14 PM ---------- Previous post was at 10:55 PM ----------
If you have devices.json in that folder and your running a n910v ... can you share that file?
Click to expand...
Click to collapse
Is Noble ROM or Aurora ROM a Note 5/7 port? Because that may be the issue. The app might be getting confused.
I have another user who's having the same issue, with a Note 7 port ROM... I'll have to debug on my end, and see what the problem is... The app is supposed to be downloading that file from the OTA server...
abraha2d said:
Is Noble ROM or Aurora ROM a Note 5/7 port? Because that may be the issue. The app might be getting confused.
I have another user who's having the same issue, with a Note 7 port ROM... I'll have to debug on my end, and see what the problem is... The app is supposed to be downloading that file from the OTA server...
Click to expand...
Click to collapse
Being on Note 7 port, as you said I've changed product code.
I'm really sorry that I can't test right now by flashing stock firmware but I promise I'll do it sooner.
If anybody else is on stock, please report!
Im downloading paulpizz stock rom ... will be testing within 45 min
Neuken69 said:
Same error
---------- Post added at 10:54 PM ---------- Previous post was at 10:16 PM ----------
im runnng aurora ROM now and i swap between that and Noble ROM not sure if that plays into the error
---------- Post added at 10:55 PM ---------- Previous post was at 10:54 PM ----------
im runnng aurora ROM now and i swap between that and Noble ROM not sure if that plays into the error
---------- Post added at 11:14 PM ---------- Previous post was at 10:55 PM ----------
If you have devices.json in that folder and your running a n910v ... can you share that file?
Click to expand...
Click to collapse
Preet Juneja said:
Being on Note 7 port, as you said I've changed product code.
I'm really sorry that I can't test right now by flashing stock firmware but I promise I'll do it sooner.
If anybody else is on stock, please report!
Click to expand...
Click to collapse
Guys, can you install the attached debug apk, clear data, grant storage permission, and then try again? If it still errors, can you send me a logcat?
@Preet Juneja There's a way to get logcat without a computer, using the Matlog app from the Play Store. See this for details:
https://www.xda-developers.com/guide-sending-a-logcat-to-help-debug-your-favorite-app/
You don't need to do the adb part if you're rooted...
abraha2d said:
Guys, can you install the attached debug apk, clear data, grant storage permission, and then try again? If it still errors, can you send me a logcat?
@Preet Juneja There's a way to get logcat without a computer, using the Matlog app from the Play Store. See this for details:
https://www.xda-developers.com/guide-sending-a-logcat-to-help-debug-your-favorite-app/
You don't need to do the adb part if you're rooted...
Click to expand...
Click to collapse
All logs related to EFIDroid attached:
Preet Juneja said:
All logs related to EFIDroid attached:
Click to expand...
Click to collapse
Did you just search for all lines containing EFIDroid, or did you actually filter by app? Because these logs seem incomplete...
Sent from my Samsung Galaxy Note 4 using XDA Labs
abraha2d said:
Did you just search for all lines containing EFIDroid, or did you actually filter by app? Because these logs seem incomplete...
Click to expand...
Click to collapse
Logs: (From launching EFIDroid app to pausing logs on Matlog app)
Preet Juneja said:
Logs: (From launching efidroid app to pausing logs on matlog app)
Click to expand...
Click to collapse
Did you put anything into the "Override OTA Server" dialog? From the logs, either there's something wrong with the app, or you put "samsung/trltevzw" into the dialog...
abraha2d said:
Did you put anything into the "Override OTA Server" dialog? From the logs, either there's something wrong with the app, or you put "samsung/trltevzw" into the dialog...
Click to expand...
Click to collapse
Oh. I put it when I didn't edit build.prop (when it was Noblelte). I already tried clearing data due to which it should've removed. Well if it didn't, how can I remove it?
I'm sure it's problem from my side and not yours... it's all because I'm using custom ROM.
UPDATE:
YES IT OPENED!
I emptied that override OTA server and the app finally asked for Root access!
Thank you so much, I'll sooner report what will be the next.
Preet Juneja said:
Oh. I put it when I didn't edit build.prop (when it was Noblelte). I already tried clearing data due to which it should've removed. Well if it didn't, how can I remove it?
I'm sure it's problem from my side and not yours... it's all because I'm using custom ROM.
Click to expand...
Click to collapse
No problem, it should probably be clearer. That dialog is for entering a different URL for the OTA server, not a different device codename. Just remove what's in there, and press Ok. That will clear it. :good:
EDIT: Just saw your edit. Nice to hear it's working.
abraha2d said:
No problem, it should probably be clearer. That dialog is for entering a different URL for the OTA server, not a different device codename. Just remove what's in there, and press Ok. That will clear it. :good:
Click to expand...
Click to collapse
Thank you so much.
Will update you soon.
Ok now what???
Neuken69 said:
Ok now what???
Click to expand...
Click to collapse
Just reboot your device to see changes!
Perfectly working, please add N910G support as 'confirmed' in 1st post.
Also, you can add instructions for custom ROM user to edit build.prop as required.
I was able to boot into TWRP and ROM without use of fastboot.
abraha2d said:
I believe the Sprint variant is similar enough hardware-wise to the Verizon variant.
As with everything, make sure you backup, and store the backup somewhere other than your phone.
That being said, I believe there are no risks, other than possibly an hour or so of downtime (if something goes wrong with the installation). Since EFIDroid only modifies the boot and recovery partitions, if something goes wrong, you can always flash TWRP via Odin, and then in TWRP flash the boot.img from whichever ROM you're currently running to get back up and running.
If you're willing to wait, I have a friend who has volunteered to test this out on his Sprint variant in a week or two (when he gets his daily driver back).
Click to expand...
Click to collapse
Thanks! So this allows you to dual boot 2 different roms?
One is primary installed as normal, i take. Now the second one, how is it installed? How is it saved?
Thank you. I'm just curious. This sounds convenient to have your daily driver as primary, and be able to test other roms without constantly backing up and restoring. Am i correct in thinking this way?
{
"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"
}
Code:
/*
* I'm not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the alarm app failed (like it did for me...).
* Please do some research if you have any concerns about features included in the products you find here before flashing it!
* YOU are choosing to make these modifications, and if you point the finger at me for messing up your device, I will laugh at you.
* Your warranty will be void if you tamper with any part of your device / software.
* Same statement for XDA.
*/
LineageOS is a free, community built, aftermarket firmware distribution of Android 8.1 (Oreo), which is designed to increase performance and reliability over stock Android for your device.
LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for LineageOS is available in the LineageOS Github repo. And if you would like to contribute to LineageOS, please visit out Gerrit Code Review.
What works:
Wifi
Bluetooth
Audio
LED
USB
RIL
Encryption
Fingerprint
Camera (partly)
Broken
Camera (autofocus & hdr)
Hall sensor
Selinux Enforcing
Source code:
device: https://github.com/yener90/android_device_lenovo_TBX704
kernel: https://github.com/yener90/android_kernel_lenovo_msm8953
vendor: https://github.com/yener90/android_vendor_lenovo_TBX704
Important
If you are using this ROM first time, wipe data. Wipe data completely. I mean the option where you need to enter "yes". Use this option and then flash the rom.
This ROM only works with the TWRP I added.
If you want to use GAPPS, flash it directly after flashing ROM. Don't let the ROM boot. Otherwise your device will not get certification, so you will not have Google Access.
Instructions (thx @matshias, just changed few lines to get ROM flashing working)
Put your ROM (and GApps) onto your sdcard (sdcard must be exfat or fat32, NTFS not supported)
Install fastboot and adb on your PC, e.g. from here
Enable developer options and in there select to unlock your bootloader by enabling OEM unlock and enable USB debugging
Connect your PC to your tablet and run
Code:
adb reboot bootloader
using adb on command line. The tablet will reboot into bootloader mode where you will only see the Lenovo logo. Now you use
Code:
fastboot oem unlock-go
to unlock. This will factory reset your device
Don't setup, cause you will need to format your tablet later again. Shutdown tablet. Hold volume up and power button to start to bootloader
Then run
Code:
fastboot flash recovery twrp-3.2.3-0-<your-filename>.img
to flash TWRP
Select with volume buttons "Recovery Mode" and press power button
Select to write to system, otherwise you can't flash ROM
Backup at least system and boot partitions to your sdcard cause you will wipe data in next step. Choose "System Image" for the system partition backup.
Format data using this tutorial
Flash ROM
Optionally flash SuperSU or Magisk in TWRP which should install system less. Keep OEM unlock enabled if you flash or modify anything
Restart
Download
2019-04-08
• changes to fingerprint
• changes to sdcard (careful those who are using sd card as internal)
• security updates: 2019-04-05
• updated TB-X704L fix file for fingerprint support
ROM
TB-X704L fix
TWRP
Older downloads
2019-04-05
• partly fixed camera (autofocus & hdr dont work), use Open Camera
• some debugging features disabled, should improve performance
ROM
2019-03-30
• fixed fingerprint
• first attemps fixing camera (will take longer than expected...)
ROM
2019-03-27
• intital release
ROM
Optional downloads
Dolby Digital Plus (use the TWRP one)
GAPPS (use 8.1 arm64; I suggest using pico variant)
Thanks
@highwaystar_ru (he gave me the important hint, also used his sources and his thread )
@LumenReaper (for his work with CM14.1, where I took big part of his device tree :fingers-crossed
@Flowah123 for the TB-X704L files :fingers-crossed:
Donations
For donations you can click here
Thanks to @rorzer, @Preyer11, @Tschumi, @MrMagic, @max_work & 5 x anonymous
Please don't support Lenovo and buy their tablets
Code:
[I]Updates vary depending on the model where our tablets receive Android and security updates after the introduction.
We announced Tab 4 10 Plus in February 2017 and since then it has received seven OTA updates.
However, this model has reached the end of its update cycle and will not receive any more updates in the future.
- Lenovo (2018-05-11)[/I]
Just seven updates and not even one major upgrade, please don't support them.
Reporting bugs
Please tell what mods you are using and what tablet variant (TB-X704F or L or ABCDEFGH..)
If your tablet doesnt start:
go to TWRP. use file manager, go to sys/fs/pstore, copy the files and upload it here.
if your tablet starts and bug appears later:
go to TWRP. use file manager, go to sys/fs/pstore, copy the files
start your tablet normal, let the bug appear, enter adb root
use adb logcat and adb shell dmesg, copy the content to a text file and upload here
XDA:DevDB Information
[ROM][UNOFFICIAL][8.1.0][TB-X704F] LineageOS 15.1 for Lenovo Tab4 10 Plus, ROM for the Lenovo Thinkpad Tablet
Contributors
yener90
ROM OS Version: 8.x Oreo
Version Information
Status: Testing
Created 2019-03-27
Last Updated 2019-05-13
The system itself runs very well. Also TWRP is very nice in landscape.
Maybe some notes after a short test phase, because your post is not so detailed yet.
Works:
- Encryption (forceencrypt is enabled)
- Clearly better audio quality than in Lineage 14.1 (Yener has already made me aware of my mistake)
- Significantly newer kernel (3.18.115 instead of 3.18.31)
Broken:
- Hall sensor
- selinux (for completeness only)
All in all very good rom. Thank you Yener!
Great work guys! I am waiting for the fingerprint to get fixed and then installing asap.
ROM loaded and running with no problems so far so thanks to @yener90, also thanks to @LumenReaper for starting the whole ball rolling. one thing I noticed is after doing Format data and wiping system, data and the caches i'm re-encrypted, it's not a major problem though, when i do another update in the future i'll format data again and see if encryption goes away
---------- Post added at 04:38 PM ---------- Previous post was at 04:38 PM ----------
ROM loaded and running with no problems so far so thanks to @yener90, also thanks to @LumenReaper for starting the whole ball rolling. one thing I noticed is after doing Format data and wiping system, data and the caches i'm re-encrypted, it's not a major problem though, when i do another update in the future i'll format data again and see if encryption goes away
peterCR56 said:
ROM loaded and running with no problems so far so thanks to @yener90, also thanks to @LumenReaper for starting the whole ball rolling. one thing I noticed is after doing Format data and wiping system, data and the caches i'm re-encrypted, it's not a major problem though, when i do another update in the future i'll format data again and see if encryption goes away
Click to expand...
Click to collapse
This rom has force encrypt enabled, so it will not go away
LumenReaper said:
This rom has force encrypt enabled, so it will not go away
Click to expand...
Click to collapse
good to know, i thought i missed something
:victory: finally
Thank you for doing this!!!
Thank you for working on this device!!! I thought the Tab 4 10 Plus I imported for Korea was never going to see another update after I read the news awhile back. I took the plunge and installed TWRP and rooted my device tonight. I can't wait to get Oreo or even Pie installed on my tablet in the future!
First off, very well done @yener90 and @LumenReaper, thank you.
Am I correct in thinking that if I flash this to my TB-X704V it should work except for the SIM functions ?
Also are Gapps included?
TIA
Sparkrite said:
First off, very well done @yener90 and @LumenReaper, thank you.
Am I correct in thinking that if I flash this to my TB-X704V it should work except for the SIM functions ?
Also are Gapps included?
Click to expand...
Click to collapse
I'm not sure, if X704V works. Try to boot from the recovery, I uploaded, from your pc.
For this switch to bootloader mode and enter fastboot boot twrp.img
If you get on your screen an error like: no dtb found, than your device requires special fix.
Don't try it out then.
yener90 said:
I'm not sure, if X704V works. Try to boot from the recovery, I uploaded, from your pc.
For this switch to bootloader mode and enter fastboot boot twrp.img
If you get on your screen an error like: no dtb found, than your device requires special fix.
Don't try it out then.
Click to expand...
Click to collapse
Cheers, for fast reply.
I'll certainly try that out later today and let you know.
EDIT:
Just tried it and booted to your TWRP just fine, nice landscape view BTW.
All appears OK, but while it "saw" the ext SD I couldn't explore it but I could the explore the internal SD.
Just one thing, when I went to exit by rebooting to system, it crashed and just hung there.
Sparkrite said:
Cheers, for fast reply.
I'll certainly try that out later today and let you know.
EDIT:
Just tried it and booted to your TWRP just fine, nice landscape view BTW.
All appears OK, but while it "saw" the ext SD I couldn't explore it but I could the explore the internal SD.
Just one thing, when I went to exit by rebooting to system, it crashed and just hung there.
Click to expand...
Click to collapse
Thats normal. Install twrp and boot to recovery. There it will never freeze.
Try it out. Before you do copy your system files to your pc. Maybe for your device some files are required.
Just one more thing, as I said, does the ROM have Gapps already installed?
TIA
Sparkrite said:
Just one more thing, as I said, does the ROM have Gapps already installed?
TIA
Click to expand...
Click to collapse
Nope
UPDATE
Download
2019-03-30
• fixed fingerprint
• first attemps fixing camera (will take longer than expected...)
ROM Download
I'm thinking on buying this tablet, but I've heard that the 5ghz wifi has some dropouts. Have anyone test it out with this rom with iperf? (Wifi Speed Test app for example)
Also I'm interested to know what issues have been found with the fingerprint. (1 minute before the dev solved it)
MiSSigNNo said:
I'm thinking on buying this tablet, but I've heard that the 5ghz wifi has some dropouts. Have anyone test it out with this rom with iperf? (Wifi Speed Test app for example)
Also I'm interested to know what issues have been found with the fingerprint.
Click to expand...
Click to collapse
Don't buy it please.
Don't support Lenovo. That ******* dont care about their customers.
I just developed that rom, to show that ****** that its not hard to build an Oreo ROM for this nice tablet.
yener90 said:
Don't buy it please.
Don't support Lenovo. That ******* dont care about their customers.
I just developed that rom, to show that ****** that its not hard to build an Oreo ROM for this nice tablet.
Click to expand...
Click to collapse
What would you recommend instead?
I come from a CHUWI Hipad that was a complete disaster: really hard to even create a TWRP
I've been looking for other alternatives and essentially we have:
Huawei and Kirin: 0% development with closed Kirin processors
Samsung/LG/Asus/Xiaomi: The cheapest with 3Gb goes for over $250 (there aren't many brands with cheap tablets in fact)
Chuwi, Teclast, ... all are **** brands with Mediatek processors that are even worse than Kirin for dev purposes.
So essentially for under $200 with 3Gb+ RAM there is only one Snapdragon tablet called Lenovo Tab4 10 Plus
But the only issue I've found so far reading reviews are the dropouts with 5Ghz WIFI AC band.
MiSSigNNo said:
What would you recommend instead?
I come from a CHUWI Hipad that was a complete disaster: really hard to even create a TWRP
I've been looking for other alternatives and essentially we have:
Huawei and Kirin: 0% development with closed Kirin processors
Samsung: The cheapest with 3Gb goes for over $250
Chuwi, Teclast, ... all are **** brands with Mediatek processors that are even worse than Kirin for dev purposes.
So essentially for under $200 with 3Gb+ RAM there is only one Snapdragon tablet called Lenobo Tab4 10 Plus
But the only issue I've found so far reading reviews are the dropouts with 5Ghz WIFI AC band.
Click to expand...
Click to collapse
Hehehe I also had a Chuwi Tablet and was a disaster . 5GHz was solved with latest update.
Xiaomi Mi Pad 4 Plus sounds nice for me. Xiaomi also has a much better support. It came out after my Lenovo Tablet. If that would be available than, I would buy Xiaomi.
Thanks for this. Great job.
Can we have R/W system? AdAway freezes when trying to overwrite system hosts file. Basically I would be happy with your first release supporting hosts file linked to other path either even without fingerprint or camera support.
yener90 said:
Hehehe I also had a Chuwi Tablet and was a disaster . 5GHz was solved with latest update.
Xiaomi Mi Pad 4 Plus sounds nice for me. Xiaomi also has a much better support. It came out after my Lenovo Tablet. If that would be available than, I would buy Xiaomi.
Click to expand...
Click to collapse
Yeah, I like Xiaomi Mi Pad 4 Plus, the problem is that the cheapest in my country is for $400, if I buy in Aliexpress it goes for nearly $300... and I found this tablet for just $180 (half the price!) in Amazon
I understand that most brand OS support is **** (including Samsung), and I definitely have a Xiaomi Pocophone F1 because they have a really great support not only in ROM dev, but good prices for replacements (screens and all that).
But If they have solved the 5Ghz issue, then I believe that we should even try in the future to go for official Lineage 16 as they did on the oldie Yoga Tab 3 Plus