Database Info

[HOW TO] Root Nextbook8 Premium (and install market app) [UPDATED 1-17-12]

PLEASE BE ADVISED: THE AUTHOR OF THIS POST NO LONGER PROVIDES SUPPORT FOR THIS THREAD. HOWEVER YOU ARE MORE THAN WELCOMED TO CONTINUE USING THE FILES AND METHODS AT YOUR OWN DISCRETION. GOOD LUCK!!
INTRO: For all those searching the internet trying to find answers as to how to gain root on your Nextbook8 Premium and also gain access to the wonderful android market from which we were greatly deprived (as is the case with many low-priced tablets these days), the wait is over thanks to a certain someone who goes by the name of DEVMONKEY. Of course I take absolutely NO CREDIT for this and only took the liberty to re-write it thus adding a little more detail to the process. Enjoy!!!
DISCLAIMER​***I HAVE NOT TESTED THIS PARTICULAR ROM WITH MY N8 WHEN I HAD IT BUT AS THE PROCEDURE TO FLASH IS STILL THE SAME ALL SHOULD GO WELL. HOWEVER, I AM NOT RESPONSIBLE FOR WHAT MAY OR MAY NOT HAPPEN IF YOU USE THIS AND DAMAGE YOUR DEVICE. PLEASE FOLLOW ALL STEPS CAREFULLY***​
[HOW TO] Root and install Market on your Nextbook8 Premium​
UPDATE: This is post has been updated with a new rom to replace old one. Method of flashing is still the same so no worries. All those who want to upgrade to this rom from the one I previously posted in this guide when I first wrote it can just repeat the steps over again with the new rom package.​
This rom is based on Samhain's release: SamDroid v1.13
Modifications (mostly GUI / cosmetic tweaks):
1.) cifs.ko / slow-work.ko / nls_utf8.ko are in /system/lib/modules and can be loaded using Mount Manager app from the market. This will let you mount CIFS/SMB shares to the device.
2.) Honeycomb-like launcher and updated GUI icons. (you can change it to any Launcher you want)
A couple of things to note once you have installed the rom:
- It starts up in Italian, so open Android settings "Impostazioni" and go to the "Lingua e tastiera" setting, and change the "Seleziona lingua" to your preffered language.
- I've put a few wallpapers in /system/media that you can set full screen by going into Live Wallpapers and using the "Multipicture Live Wallpaper" set them to the screen.
- There are a few things (widgets) on the homescreen that don't work after initial boot, just remove them and add back whatever you want to the homescreen.
- Sleep of death issues seem to be fixed, and the camera works (Camera app works, but Skype and Fring don't work yet...).
- You can also grab Adobe Flash 11 from the market and it'll work correctly.
- This release boots MUCH faster, and is even more responsive than before.
- There is a cell standby issue that drains the battery more in theory so if you feel like that is happening with you just delete the Phone.apk and TelephonyProvider.apk from /system/app. You can use ADB or you can use Root Explorer to do so. You will likely have to force a reboot because you'll start getting repetitive force closes once you do so, but it won't hurt anything. Once you reboot, all is well.
VERY IMPORTANT: After installing custom roms that also flash a custom recovery your N8 may reboot into the custom recovery. If this happens hit reboot system and only reboot system.
​Download new rom from HERE and extract (using winRAR preferably) to your desktop or anywhere you choose. Location doesn't really matter for this guide to work.
NOTE: If you have anything you care about (like apps, notes etc.) on your N8 make sure you back it up now.
Step 1: Turn your N8 off.
Step 2: Press both Volume buttons down and plug the USB cord into the N8.
NOTE: On your screen you should see a bubble pop up in the lower-right corner saying "Installing drivers". Most likely it will say it can't find the drivers. This is normal. Continue following the steps to install the missing drivers.
Step 3: Open the Device manager by typing mmc devmgmt.msc into your "Run" box on XP or search box in start menu on Windows 7 and hitting enter (you can also find Device Manager in your Control Panel options in Windows 7).
Step 4: With your N8 still in an off state and plugged in via USB you should see a yellow exclamation symbol somewhere next to "Unknown Device" in the list of devices in the Device Manager. Right click on it and select "Update driver software".
Step 5: Now it will prompt you to choose how you want to search for it. Select "Browse my computer for driver software" and it will bring up a window for you to navigate manually to the driver location which is in the "drivers" sub-folder in the NEXTBOOK8ROOT folder. Select which ever system you have (32bit or 64bit) and then hit "OK". You might go thru one or two prompts before it actually installs. Just "OK" everything and you should be fine.
Step 6: Once the drivers are installed you are ready to flash. Go into the root of the NEXTBOOK8ROOT folder and select RK29update.exe (right-click for Win7 users and Run as Admin).
Step 7: Now you should be at the interface of the program and at the bottom in bold words it should say "FOUND RKAndroid rock usb" (if it doesn't then it mean the drivers probably weren't installed correctly). This part is VERY IMPORTANT!! Make sure all of the boxes on the left are checked (should look like the pic below). The one at top is the one usually missing a check and would need to be checked by you.
{
"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"
}
Step 8: Once all boxes on the left are checked you are going to click on "EraseIDB" at the bottom and let it complete. Once that finishes click on "Run" and you will see a series of commands running in the right window pane (see pics below). Give it some time as it will probably take a few minutes. When it's done it should look like the second pic below.
Once the process is finished your NEXTBOOK should reboot into the recovery and reflash the OS. Congratulations!!! You now have an affordable rooted tablet with access to the Android Market!!
OTHER ROMS YOU CAN FLASH INSTEAD OF THE ONE IN THE ABOVE GUIDE:
Pisteone - [SDK 2.1] EXT4 Bluetooth 3G Root [Basic FW 1.0.21] ICS Style - LINK
Fintadroid - [FULL ROOT & EXT4] [BT & 3G] [FW.1.0.21 PRESTIGE] - LINK
ALL ROMS FOR NEXTBOOK8 - LINK (Be very careful and read before you flash)

Thanks! worked great.

I signed up, so i can say thank you. this worked perfectly.. i was skeptical and scared i'd ruin this tablet, as i got it as a gift, and was obviously disappointed to see no market on it, but this worked. thank you.

How about Nextbook Premium 7?

Thank you!
This worked great, I was able to get the android market installed and working.

Android version?
What version of Android does this install?
Cheers, Greg.

It's work, your are wonderful,thank you Sunnyboy167

Great job! Good to have root and Market working. But anyone else get FC when opening Camera app?

Perfect! I have rooted many Android devices and this is one of the easiest ones. Just read the directions carefully and you'll do fine.
Hopefully someone will release an ICS update for this device soon..after using my Galaxy Nexus, Gingerbread seems so...obsolete.

I'm glad you enjoyed this info just as much as i did
To everyone YOU ARE WELCOME but please....the best way to thank me is by hitting the thank button at the bottom right of my post. Thanks!
@xxProphecyxx - here is a link for the nextbook7 http://gunnersbarn.wordpress.com/2011/11/04/how-to-install-android-market-to-nextbook-premium-7/ I don't see any root method listed on the site but im sure there is one out there if you want to root it too. Or you can even take a chance if youre brave and use a one click root based on the android version you have.
@ghi07 - All this method does is re-install the OS (which is Gingerbread to answer your question) with market and superuser.
@dalerious - I'm sorry but I don't have a Nextbook anymore but if I did I would definitely try my best to help you. Try doing the entire process over and see if that works. Good luck!

THANK YOU!!!!
I was about to throw this tablet out the window!!! Followed the instructions and it works perfectly!!!! Thanks SO SO much!!!

Thanks to you I had a very Merry Christmas haha thank button has been pushed repeatedly!

Hi Sunnyboy,
Just want to say a big thank you for the detail post. I was about to give up on on this tablet when I came across your post.
Chris

help help!!!
hi sunny boy,
i just got my nextbook8 yesterday... come across this website and trying to root my nextbook last night at home...
I encounter this problem...when i plug in my nextbook into the PC USB ..it turn on from the off mode. and the pc started to scan the driver and it actually install successfully. I am running on win7. after that i cant install the driver required.. can anyone help me out here cos i try to run exe. file. it cant root my nextbook... i am helpless now...

I am also having problem with the camera. I'll have this error:
The application Camera (process com.android.camera) has stopped unexpectedly. Please try again.

HELP HELP HELP...not able to on the device after updated the driver....PC shows device found after plug in USB, which shows the device is working but just cannot on it.. a total IT dummy and not sure what's going on..someone said the ROM is damaged which cause this.....any way to recover the tablet..i just bought it for less than a week. HELP HELP HELP!!!!!! (tried reset but still no response)

Sunnyboy167 said:
To everyone YOU ARE WELCOME but please....the best way to thank me is by hitting the thank button at the bottom right of my post. Thanks!
@xxProphecyxx - here is a link for the nextbook7 http://gunnersbarn.wordpress.com/2011/11/04/how-to-install-android-market-to-nextbook-premium-7/ I don't see any root method listed on the site but im sure there is one out there if you want to root it too. Or you can even take a chance if youre brave and use a one click root based on the android version you have.
@ghi07 - All this method does is re-install the OS (which is Gingerbread to answer your question) with market and superuser.
@dalerious - I'm sorry but I don't have a Nextbook anymore but if I did I would definitely try my best to help you. Try doing the entire process over and see if that works. Good luck!
Click to expand...
Click to collapse
I have already been to this website and successfully added the market to my Next7. I do want to root it and flash a custom ROM, but I have not found anything useful. Thanks though.

Rooted fine, thx a mil. Installed GOLAUNCHER EX and the icons were too big. Dl'd LCD resolution from market and decreased res from 160 to 140. To apply changes app reboots tablet. When it came back up, nextbook stuck on launch screen and I can't even turn it off!! This was my gf's xmas present from her parents!!! Any suggestions??

eybarra2 said:
Rooted fine, thx a mil. Installed GOLAUNCHER EX and the icons were too big. Dl'd LCD resolution from market and decreased res from 160 to 140. To apply changes app reboots tablet. When it came back up, nextbook stuck on launch screen and I can't even turn it off!! This was my gf's xmas present from her parents!!! Any suggestions??
Click to expand...
Click to collapse
u can reboot the device by using a paperclip and press in the reset button.
---------- Post added at 10:44 AM ---------- Previous post was at 10:39 AM ----------
Thanks for the detailed guide Sunnyboy167~ Anyway devmonkey just release a newer mod which works better than the previous. Do check it out

hi all,
I rooted my new nextbook8 ...and it works just nice...
just need some help on whether possible to use my iphone as a modem for my nextbook? as i realized it cant detect my wifi network from my iphone. While my colleague 's motorola zoom works fine with my iphone...any solution on this?
Caduser from singapore...

[TOOL][NABIXD] NabiRootXD Root, Gapps, Recovery

NabiRootXD v2​
{
"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"
}
This is a tool for rooting, installing Gapps(Play Store, etc), and adding custom TWRP recovery on Nabi XD. It's written as a windows command line batch file, and is based off NabiLab I made for Nabi2.
It was an adventure to say the least. I include some of the hurdles for those that want to duplicate the root process or just to place my thoughts "on paper" because of the 100's of posts I read from those that posted detailed information and allowed me to gain useful insight in how I could adapt things for the XD, and explain in one swoop to the many PM's I have received about "when will we see root on the XD" why it took so freaking long. Those that just want the program can continue to the Overview section.
What started as an interesting avenue was TWRP using the Nabi2 kernel was booting the NabiXD to TWRP without video. I thought it possible to dd the recovery, or boot kernel. Unfortunately it was unable to recognize internal storage as a block device and that ended that. Like a few devices on Android 4.1.1 and above the standard once click program using Bin4ry's ADB restore exploit doesn't work. It doesn't work for a couple of reasons, when restoring fakebackup.ab in locks up writing the first file, and even if it did work placing ro.kernel.qemu=1 in local.prop doesn't work because Jelly Bean doesn't parse any property files to set the ownership of adb daemon. Searching the file system I found su2 in the xbin directory. This was promising as it is the su program but renamed, also unfortunate was its permissions had no setuid bit set and while it was executable it would not change uid to 0. I then foolishly went down the path of nvflash(forced recovery). I attempted a few different avenues here to try and possibly get the SBK to unlock nvflash, that proved uneventful, especially without root access. I tried extracting what "could" be the key from the Nabi2 it hope it was reused. That lead no where, it would be awesome to have access to it for many other reasons but it turned out to be an exercise in learning but ultimately a waste of time. Then on to other Android exploits... Tried Samba, debugfs, and vfat exploit. All of those are either patched or I'm not skilled enough. I finally returned to looking at the ADB restore exploit.
The "tabletS" exploitation showed promise as it takes the avenue of installing /dev/sh vs ro.kernel. A side effect of the failed ADB restore bug was leaving a directory with full permissions. Bads3ctor had an interesting fakebackup.ab that was more reliable at making a directory or file that you simlinked have full permissions. Now you can step through the tabletS script more effectively where you couldn't before by manually setting permissions for files/directories you need by doing the restore for each file and directory you need. The script installs VPNfaker and backs up the /data/app directory, then creates a new app directory. This however will cause the NabiXD to rerun the initial kidsmode setup and breaks everything. You can dance around that by not rebooting, and VPN faker will still give you a Term app with system uid. From there you can't symlink the sysfs links properly to data/property but that can be worked around by moving and then removing files. Finally you can makedev /dev/sh and run su from /data/local/tmp. The end result is that the exploits and bugs found by others are adequate when strung together in the right order on the NabiXD just not the one click solutions provided on the forums, they needed some modifications and done by hand to figure out for the NabiXD
Here is a nice publication I found in my searches that is more layman terms for older root methods. http://www.sourceconference.com/publications/bos12pubs/android-modding-source.pdf
Overview
Video Overview of NabiRootXD - a video tutorial of the use of NabiRootXD.
-Root the Nabi XD
-Install Gapps(Play Store, etc)
-Make a stock backup of unrooted device
-Install stock, or TWRP recovery
-NabiLab patching system to install updates to this program
Version 2
-Fixed scripting error causing early exit
-Added 7z for patching system
Download
Read the installation section below to determine which version you want.
File names:
NabiRootXD.zip 96MB (Version 2)
Download
Download Mirror
Installation
NEW INSTALLS
1) Download NabiRootXD
NabiRootXD.zip 96MB
2) Extract the zip files to a location of your choosing. Run the NabiRootXD.bat file.
Prerequisites
1) Script is for Windows
2) ADB enabled in Android. Enter Mommy/Daddy mode. Open settings->developer options->put a check mark in USB debugging.
3) ADB and Fastboot driver. Most popular are the PDAnet drivers. You can get them here: PDAnet drivers
Usage
Obviously using this script on your NabiXD voids the warranty and I take no responsibility for the damage you cause.
MENU 1 - Root, Gapps, Recovery​
Menu Option 1 - Install Root, Recovery and Gapps
This option is best used if you have a brand new Nabi. At this point you should have met the prerequisites of enabling ADB in Android. Follow directions, most sticking points are pressing the volume + and then pressing the volume - button twice and making sure recovery kernel is the one highlighted. After its complete you should have a rooted Nabi, with Gapps and a backup of your unmodified Nabi in the folder TWRP/BACKUPS/YOURSERIAL/stockunrooted on your device. Not a bad idea to copy this off the Nabi to your computer if you need to free space or have it in a second location.
Menu Option 2 - Install Root and Recovery
Same as above but doesn't install Gapps. Some people have trouble with option 1 taking the Gapps install, I personally have never experienced it but the option is this one, or I guess if you are an elite hacker that just wants root.
Menu Option 3 - Install Gapps
Same Gapps installed in the Option 1. Useful for re-installing Gapps. This is Jelly Bean Gapps dated 10/11/2012 without Google Search. This makes NO backup of you Nabi. You will have to already have installed TWRP.
Menu Option 4 - Install Root
Installs root. Nothing fancy here, and likely unneeded but here for completeness if you find yourself in a strange situation. One that comes to mind is that you have a stock backup which you restored and don't want to do another backup so you would just run this and the gapps install. It makes NO backup. You will have to already have installed TWRP.
MENU 2 - Install Recoveries​
Menu Option 1 - Install TWRP 2.3.3.0 for Nabi Version 1.2.3
Installs TWRP 2.4.4.0. This is the latest at this time. It has a screen timeout, if the screen goes black touch the screen to wake the screen, it's not locked up.
Menu Option 2 - Install Stock Recovery
Installs stock recovery. This is useful for taking an OTA, or completely returning Nabi to stock.
Notes: TWRP installs are based off my work in this thread if you want to read more.
MENU 3 - Patch NabiLab​
Menu Option 1 - Install Patch
For any updates to NabiRootXD this is where you can automatically load them. Basically you will download NabiPatchXD.zip and place the entire zip in the patch folder. No unzipping just the single file. Then run this option.
Credits - If you see these guys buy them a beer.
jzmtaylor - Original Nabi2 script that this is based off of.
Bin4ry, Bads3ctor, HEXcube, drjbliss - all the bugs/exploits needed to accomplish root
Dees_Troy - TWRP build tutorial
Eric Karz - TWRP Theming and rooting assistance
TeamWin - They are the guys that make TWRP possible

Weeee more Easter goodies haha.
thanks aicjofs

Sir can i use this tool for installing Gapps for unrooted Galaxy Tab 7.0+ (wifi)? bcoz i updated my tablet for Honeycomb to Ice creamsandwich (China Firmware), everything is fine except that i cant open google playstore...

first of huge thank-you.. who do i send a bear donation to as a thank-you
there is a possible bug or its just me when pressing the menu button it will pull up a search, or say Google with a white back ground only way to get out isto press home if a menu appears then pressing back produces the same results

srgsng25 said:
first of huge thank-you.. who do i send a bear donation to as a thank-you
there is a possible bug or its just me when pressing the menu button it will pull up a search, or say Google with a white back ground only way to get out isto press home if a menu appears then pressing back produces the same results
Click to expand...
Click to collapse
The gapps removes the problem in system/app/quicksearchbox.apk you can rename it toquicksearchbox.bak
only other way I can think of is some how playstore added it to data/app
rename com.google.android.googlequicksearchbox.apk to com.google.android.googlequicksearchbox.bak
hth
ps: thank the op he spent hours and hours to make this happen = sacrificed his free time

Thanks for the feedback.
Perhaps we should have used the 7/26/2012 gapps? http://goo.im/gapps/gapps-jb-20120726-signed.zip 10/11/2012 is suppose to be 4.1.1 backward compatible, but perhaps there are some bugs with it on XD. Flash over the top of the current one. It will leave behind /system/app/thinkfree.apk, /system/app/microbes.apk and /system/lib/libmicrobes_jni.so, which you could remove manually. Wipe caches.
How about GPS stuff? Is that working?

i was looking at gapps-jb-20120810-JRO03C-Formula84-Custom
it has some things that sort of work like maps/local/ latitude /
I don't think gps is working
Even in the productions test it fails .
could it be a permissions problem ? I have not tried 20120726 .

Eric Karz said:
i was looking at gapps-jb-20120810-JRO03C-Formula84-Custom
it has some things that sort of work like maps/local/ latitude /
I don't think gps is working
Even in the productions test it fails .
could it be a permissions problem ? I have not tried 20120726 .
Click to expand...
Click to collapse
Do we know that the GPS works at all?

aicjofs said:
Do we know that the GPS works at all?
Click to expand...
Click to collapse
with gapps installed it doesn't seem to work .
maybe we are going to need a edited gapps ?

I'm just going to remove Google Search for now. That is highly annoying, I was messing around with ways to fix it, and got it to open in apps when you press the settings button, I was previously only getting it when pressing back button.. I updated the downloads. Until we figure out the fix, it's just too troublesome.

cool that did the trick renaming the file i do have a really stupid question is there a hiden proxy setting that makes the tablet able to bypass our DNS security filters with open dns just curious

srgsng25 said:
cool that did the trick renaming the file i do have a really stupid question is there a hiden proxy setting that makes the tablet able to bypass our DNS security filters with open dns just curious
Click to expand...
Click to collapse
I don't know if there is a hidden proxy. I'm not sure of your question. You could try going to settings-wifi. Long press the name of the network and a pop up will come up. Modify network, show advanced options. There is the proxy and DNS, for DNS you have to be static. I think there is 4.4.4.4 in there by default, plus what your router gives out.
If you are talking about something more underground I think you could use a getprop in adb shell or term.apk. I know I have seen stuff in there for DNS, something like dhcp.wlan0.dns there is stuff in there about "change" too. Should be able to set if you "su" and do a setprop. That would only be good until reboot, but could help you trouble shoot. I think it's set here /system/etc/dhcpcd/dhcpcd-hooks/20-dns.conf, maybe not in Jellybean. Anyway those are places to look if it's more then in settings that you are looking for.

ok it seems that this might be a work around to the quick search problem
edit the buildprop and change
ro.sf.lcd_density=160
to
ro.sf.lcd_density=145
I tried 149,150,59 and 120
120 does seem to fix it also but the screen makes every thing look smaller and some may not like that .(I do)
also I had to install BusyBox in order to get a few things to work including
build prop Editor by Nathan Campos (this tool seems to be a good test app to see if you have proper permissions)
note that the swipe screen will be a bit smaller under 160
maybe some one can use this info to edit quick search box we wouldn't have to change anything?

i am trying to get this tablet to use my network opendns settings and web filters

Can someone direct me to where I can get a Vista MTP driver for the Navi XD? I installed PdaNet as instructed but the tool wont connect, and I have a yellow exclamation mark by MTP Device. Can't seem to find anything else online.
EDIT: After rebooting a few times, then disabling my firewall, the tool connected. Thanks for the awesome tool.

Looks like an OTA was released for the Nabi XD today that bumbs the Nabi XD up to version 1.3.5. I tried doing the stock recovery option but the NabiRootXD app just closes out after selecting it. I looked into the NabiRootXD.bat file and I noticed on line 483 that it says to "GOTO Install_4" which doesn't seem to exist. I believe it should actually say "GOTO Install_2".
After making this change I was able to restore to the stock recovery to perform the OTA.
Now once I tried to install the OTA it appeared to atart the installs and then fails with the dead android symbol about a third of the way through. No idea what the problem is now so I'll just wait for others to try this and see what their results are.

yup getting the dead droid

Reinstall TWRP and "Install" this to update. Have a backup. Should work if you have made no system modifications, except what NabiRootXD did.
Download
TWRP may or may not ask you to reinstall superuser.
Also working on a patch to fix the exiting error in script.
EDIT: New links for a version 2. Fixed scripting error and patch system error. Easier to just download the whole program again then for me to explain fixing the patching system manually.

OTA procedure
srgsng25 said:
yup getting the dead droid [
BOOT into TWRP and perform and system restore to pre-root image
reboot
download and install the OTA
reapply root and gapps
Click to expand...
Click to collapse

aicjofs said:
Reinstall TWRP and "Install" this to update. Have a backup. Should work if you have made no system modifications, except what NabiRootXD did.
Download
TWRP may or may not ask you to reinstall superuser.
Also working on a patch to fix the exiting error in script.
EDIT: New links for a version 2. Fixed scripting error and patch system error. Easier to just download the whole program again then for me to explain fixing the patching system manually.
Click to expand...
Click to collapse
Thanks for the update aicjofs! I'll test this out shortly and let you know how everything goes.

[TOOL][WIN]Gstreamer emergency toolbox, for devices with broken lcd or digitizer ;)

Hi all, i passed trough the bad experience of a phone with a broken screen, all my data was trapped inside the device and i couldn't see nothing on the screen :crying:
So i decided to develop a little app, in order to be able to break into my phone again and save the more stuff i could.
Gstreamer (aka Ghost streamer) is able to let you see your device screen once again (that was the primary purpose...) and deal with it by clicking and swiping with your mousepointer on your phone screen picture (yes, it's slow but it gets the job done )but without the need to install softwares like VNC and similars (Gstreamer only allows you to gain access your files in a way or another and try to save it),.
If your dead phone was rooted and with a custom recovery, then yur life will be easy in case of broken screen , but if not , then the music changes a lot, that's why i thought my software could help other people to solve theproblems i meet during my data rescue attempts.
No matter the device screensize, it will adapt to your device screensize and will make your life easier if you broken your phone screen.
I'm still adding features to it, and planning to organize it in a better way, correcting some bugs, testing it on different phones and android versions,but it's actually working and improving day by day
if someone is interested in testing it with me, and report then the experience i'd be happy to cooperate.
at the moment this is the pre-alpha stage for me , but this is how it looks now
{
"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"
}
if you are having bad times with your phone screen this may help you :fingers-crossed: just contact me if interested
use at your own risk it's still experimental, download it from the link below
http://www.filedropper.com/gstreamerv1000release

open for feature requests here , if you want me to add special functions, just ask here and i will see if it can be embedded or not.
get the latest nightly build on my git, just click on the "Download ZIP" button. (link below)
any advice is appreciated, thank you.
changelog!
new release, now the Apk operations are ok , now you can list, uninstall, pull, install apk from your PC.
always get the latest release from my git
https://github.com/TheBrainBooster/Gstreamer/archive/master.zip

BrainBooster said:
open for feature requests here , if you want me to add special functions, just ask here and i will see if it can be embedded or not.
get the latest nightly build here https://github.com/TheBrainBooster/Gstreamer just click on the "Download ZIP" button.
any advice is appreciated, thank you.
changelog!
new release, now the Apk operations are ok , now you can list, uninstall, pull, install apk from your PC.
always get the latest release from my git
https://github.com/TheBrainBooster/Gstreamer/archive/master.zip
Click to expand...
Click to collapse
new changelog! V1.2.1.0 release
added dpad navigation buttons
minor bugfixes
redesigned main panel
new changelog! V1.2.2 is available for the download
added swipe buttons
added memory info
minor bugfixex
check it out and let me know testers are welcome
01/02/2016
new changelog!
minur bug fixes
added file push , pull and sideload functions
...sadly i don't have feedback so i can't be sure it will work with all the android versions

...many changes heve been done, stay tuned for the next release

Hello,
tried you app, but it does not recognize my phone, because it has not debugging mode activated. I tried even "RSA ADB key inejection and..." but with no luck. For anther device, which has debugging mode active, I was able to get its data, but for the one with broken display and no debugging mode, it doesn't.
Any hints?
Regards,

can you provide some more informations about your device?
maybe you could try to repeat the procedure but in recovery mode

Hello,
Thanks for your time. So far you're the only one who gave me something as an information, or tip/hint.
My phone is an Samsung i9300i, with stock rom, only recently when trying to get the data through ADB, I have installed via ODIN an image named "CWM Recovery v6.0.3.6.tar", but still no effect in ADB.
Before replying to you I have tried recovery mode as well (power button, home, volume - and after 5 seconds volume up- as those were the steps required for my model to get into download mode). But I cannot get your up to recognize my phone. I tried with another one (HTC One M8s), with debugging mode on and the app recognize it in a flash. But with the broken one, no luck.
Are there necessary some custom drivers? Do you think some print screens could help?

a screenshot could help for sure
installing the proper adb drivers too, try with this --> http://forum.xda-developers.com/showpost.php?p=50008343&postcount=486
also installing the official kies software by samsung may help
whas the phone rooted?
can it boot normally?
do you see something on the screen?
what is the damage on you phone?
android version?

Hello and good morning (for me it's still morning),
No, the phone was not rooted, was "untouched". I gave up the idea I can retrieve data via software and I was thinking to try to open it and have a display temporary put, but it's time consuming and I'm short on time to recover the data (some business information for my boss).
I'll try the drivers you have wrote and I'll came back with screen shots as well.
Regards,

sorry for the late post edit, but it came to my mind after i wrote
by the way... are you sure you booted into recovery mode?
my software shoud see the phone anyway when you hit the test conection button

Hello and good morning (for me it's still morning),
No, the phone was not rooted, was "untouched". I gave up the idea I can retrieve data via software and I was thinking to try to open it and have a display temporary put, but it's time consuming and I'm short on time to recover the data (some business information for my boss).
I'll try the drivers you have wrote and I'll came back with screen shots as well.
LE: Yes, I'm booting in download/recovery mode (combination of pow+volume minus + home buttons and volume up after 5 -7 seconds - steps specific for Sam i9300i phones)
Regards,

miborion said:
Hello and good morning (for me it's still morning),
No, the phone was not rooted, was "untouched". I gave up the idea I can retrieve data via software and I was thinking to try to open it and have a display temporary put, but it's time consuming and I'm short on time to recover the data (some business information for my boss).
I'll try the drivers you have wrote and I'll came back with screen shots as well.
LE: Yes, I'm booting in download/recovery mode (combination of pow+volume minus + home buttons and volume up after 5 -7 seconds - steps specific for Sam i9300i phones)
Regards,
Click to expand...
Click to collapse
so you shoud see the phone connected maybe it will say: device-12345abcdefyourphoneID-(recovery) but if you have the drivers installed it should appear in the log window, moreover you said maybe you have a CWM recovery installed...
remember to reboot your pc ater the drivers setup

BrainBooster said:
so you shoud see the phone connected maybe it will say: device-12345abcdefyourphoneID-(recovery) but if you have the drivers installed it should appear in the log window, moreover you said maybe you have a CWM recovery installed...
remember to reboot your pc ater the drivers setup
Click to expand...
Click to collapse
Indeed I have had installed CWM (if by that you are referring to "CWM Recovery v6.0.3.6.tar" file - which I did, using ODIN (v.307)), as I thought the debugging mode would be activated, but it seem it doesn't. Please can you give me more details about what did you want to say by " moreover you said maybe you have a CWM recovery installed..."? Is it a bad thing? Should I flash to a stock rom?
And no, it does not show any devices like device-1234afsadsasdasd.
Regards,

what i mean is, if you installed a custom recovery and you also have your phone drivers properly installed you should have an adbd server running on the phone(provided by the custom recovery environment) and an adb client running on the pc, so they should see each other

BrainBooster said:
what i mean is, if you installed a custom recovery and you also have your phone drivers properly installed you should have an adbd server running on the phone(provided by the custom recovery environment) and an adb client running on the pc, so they should see each other
Click to expand...
Click to collapse
Ok, now I understand what is the purpose for that img.
So, bottom line is I cannot seem to install proper drivers. I'll try different combinations of uninstall plus install drivers from your link (i had used the ones from Samsung site, released this year), plus computer reboot, as so far I wasn't able to have ADB listener list my device (or your application).
Regards,

Root it! everything will be much more easy
http://androidmtk.com/root-samsung-galaxy-s3-neo-gt-i9300i

BrainBooster said:
Root it! everything will be much more easy
http://androidmtk.com/root-samsung-galaxy-s3-neo-gt-i9300i
Click to expand...
Click to collapse
I'll try, but, I'm not able to check what is my build number. As far as I know, I have only the stock image (exactly as the phone came with) and am sure it hasn't have the 4.4.4 version, but something like 4.3 something...I have a colleague, back at work which has some same device (Sam I9300i) and I could check the version on that terminal and try my luck.
Thanks again for your time and insight

miborion said:
I'll try, but, I'm not able to check what is my build number. As far as I know, I have only the stock image (exactly as the phone came with) and am sure it hasn't have the 4.4.4 version, but something like 4.3 something...I have a colleague, back at work which has some same device (Sam I9300i) and I could check the version on that terminal and try my luck.
Thanks again for your time and insight
Click to expand...
Click to collapse
anytime
if you need further help , just ask

BrainBooster said:
anytime
if you need further help , just ask
Click to expand...
Click to collapse
Hello,
I've just finished all leads meaning I have successfully rooted the phone by using your link; I got PASS message in ODIN using the exact image as the tutorial indicated. But, still I cannot connect to the phone with ADB, or by using your app.
If I boot normally I can hear the sound, see the top buttons lid and have the popup message in windows which tells me I can browse the mobile phone's content (onStdBoot.jpg).
If I boot in recovery mode (can see COM0 used in ODIN and can flash successfully) I get the devices on the second print screen (BootInDownloadMode.jpg) but cannot access it.
Could you please advise if there is anything else I can try?
Regards,

if you successfully rooted your device, booting it in recovery mode should make it show in my software

[ROM][6.0.1][CM13][UNOFFICIAL] Cyanogenmod 13 for Lenovo A760

DISCLAIMER: I do not own/build this ROM, This is not my work. I am posting this thread to help other Lenovo A760 users.
How to Install CM13 (Cyanogenmod 13) UNOFFICIAL 6.0.1 Marshmallow on Lenovo A760​
***** Android Rooting/Modifying Disclaimer *****
You are making these modifications to your device. I am not responsible for whatever happens to your phone, shall this process fail. You understand that I cannot be held responsible if you do not follow directions and brick your device. You are the only person responsible if you brick your device, as you are the one choosing to modify your device. You are voiding your warranty by rooting, making modifications, and install custom roms. I encourage you to READ CAREFULLY before following along and continuing to void your warranty. A fair knowledge of ADB and ROM flashing might be needed . You have been warned! Not following directions CAN result in a soft or hard brick. Thank you for if you read all of this!
Screenshots:​
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Known Bugs:​
- No FM Radio
- Screen Recorder app causing phone to reboot (please do not use the app)
(All the links for download will be available at the end of these steps)
Step 1
Download cm-13.0-20160502-UNOFFICIAL-audi.zip and A-GAPPS 6.0.1.zip and save it under root directory in your phone's SD Card.
WARNING!! Step 4 to Step 9 will erase your Internal Storage. PLEASE BACKUP of all your files in Internal Storage (NOT SD Card) before proceed further!!
Step 2
Download the Qualcomm QPST zip, and install it on your Computer. (You may restart the computer after finished installation to make sure the driver is in effect)
Step 3
Power off your phone, take the battery out. Connect it with USB cable to the computer.
Step 4
Press & Hold (Vol +), (Vol -) & (Power Button) while its connected to your computer until you feel its vibrate 2x times. (check at the computer taskbar and see if device called Qualcomm CDMA Technologies MSM connected) DO NOT press FORMAT/ERASE drive if your computer prompt it. Just click cancel if the message appear.
Step 5
Download the HDD Raw Copy Tool and double click it to execute the application. You can now see 'Qualcomm MMC Storage' shown in the software.
Step 6
Download Lenovo_A760.imgc. Under the 'Qualcomm MMC Storage' line, there is another 'FILE' line, double click the line and select your downloaded Lenovo_A760.imgc
Step 7
Once your Lenovo_A760.imgc selected, it will display 'Please select TARGET' message. Click the 'Qualcomm MMC Storage' line and click the Continue>> button
Step 8
Click START and confirm to continue the process. This will take up to 20minutes.
Step 9
Once it shows 100% complete, you may remove the phone from USB cable, and insert back the battery. DO NOT power it on yet.
Step 10
Press & Hold (Vol +), (Vol -) & (Power Button) to go to Recovery Mode. Once you are in TWRP recovery, press ‘Wipe’, and swipe to proceed wipe/factory reset.
Step 11
Press 'Install' and select your cm-13.0-20160502-UNOFFICIAL-audi.zip.
Swipe to Install your zip. Press ‘Reboot system’ at the bottom.
Voila! you will be greeted with Cyanogenmod Boot Animation. Please proceed with the necessary steps to setup your phone for first time.
Step 13
Once booted up, go to Settings, scroll down until ‘About phone’. Tap on ‘Build Number’ for few times until a message appear: ‘You have enabled development settings!’.
Step 14
Go back once, and tap on ‘Developer options’. Turn on ‘Advanced reboot’ in Developer options, and scroll down a bit to set ‘Root access’ to ‘Apps and ADB’.
The following steps are only for those of you who want to install Google Apps:
Step 15
Press & Hold the Power button, select Reboot, and then select ‘Recovery’
Step 16
In the Recovery, press 'Install' and select your A-GAPPS 6.0.1.zip. Swipe to Install your zip. Once finished, just Press the ‘Wipe dalvik/cache’ button at bottom. After that, press ‘Reboot system’ again.
If your google Contacts does not sync, download the 'Google Contact Sync 6.0.1' apk and install & replace the current version in your phone.
Click to expand...
Click to collapse
If you are facing the ‘Unfortunately Setup Wizard Has Stopped’ or ‘Unfortunately Google Play Services Has Stopped’ errors, you may follow this steps:
For Setup Wizard, go settings, scroll down to ‘Memory’ > ‘Memory used by apps’ > ‘Setup Wizard’ > (Press i in the circle) > ‘Permissions’ > Turn on the options for ‘Contacts’ & “Phone’
For Google Play services, go settings, scroll down to ‘Memory’ > ‘Memory used by apps’ > ‘Google Play services’ > (Press i in the circle) > ‘Permissions’ > Turn on all the options
Download links
Qualcomm QPST: http://www.x-drivers.com/catalog/flash/mobile_phones/companies/qualcomm/models/qpst/12051
HDD Raw Copy Tool: http://viid.me/q0YITi
Lenovo_A760.imgc: http://viid.me/q0YH1w
Download CM13 Unofficial: http://viid.me/q0I8UI
Google Apps for Android 6.0: http://viid.me/q0I6nC
Google Contact Sync 6.0.1: http://viid.me/q0HCDh
--------- PLEASE SUBSCRIBE TO MY YOUTUBE ---------
Please Subscribe: https://goo.gl/Mr3YMF
Visit my website: http://tekmastah.blogspot.com
Credits
• Vlad Den from Youtube for HDD RAW Copy flash guide: https://goo.gl/i6bK9k
• Weritos from 4pda.ru forum for Cyanogenmod 13 UNOFFICIAL Rom: https://goo.gl/NdYfuS
• A-TEAM from XDA developers forum for Gapps: https://goo.gl/7A6kyX
• ZENELKA MILKO from Lenovo A706 Indonesia FB Group: https://goo.gl/wFKOsZ
• APKMirror for Google Contact Sync: https://goo.gl/mRJH8y

Hi mellomade,
Thanks for this ... I'm using another phone now running Lollipop, but still have the A760 running unofficial CM11.0. as a backup, I've downloaded all files, and will give it a go at a later date ... I'm between cataracts eye operations right one fixed, left should be done soon, I can't get new reading glasses until then, so I'm struggling with anything close-up right now. ...Jack

jachol said:
Hi mellomade,
Thanks for this ... I'm using another phone now running Lollipop, but still have the A760 running unofficial CM11.0. as a backup, I've downloaded all files, and will give it a go at a later date ... I'm between cataracts eye operations right one fixed, left should be done soon, I can't get new reading glasses until then, so I'm struggling with anything close-up right now. ...Jack
Click to expand...
Click to collapse
Hi Jachol. Good to hear some of us are still hang on to A760. No worries, do post here if you have any questions about the installation process. Get well soon!

mellomade said:
Hi Jachol. Good to hear some of us are still hang on to A760. No worries, do post here if you have any questions about the installation process. Get well soon!
Click to expand...
Click to collapse
mellomade ... The A760 has always worked well for me, I wouldn't scrap it, I only have the newer one because it came as a present ( so far it's been equally as good).
I've been studying the instructions, and guess steps 1-9 install the new TWRP recovery, the new ROM installation is then normal TWRP procedure.
I do have TWRP recovery v.2.6.3.0 already installed, but I'm sure it isn't compatible with latest android versions, so no chance of an install via that
It will be interesting to see if others from the old thread pick up your link.Thanks again. .. Jack

jachol said:
mellomade ... The A760 has always worked well for me, I wouldn't scrap it, I only have the newer one because it came as a present ( so far it's been equally as good).
I've been studying the instructions, and guess steps 1-9 install the new TWRP recovery, the new ROM installation is then normal TWRP procedure.
I do have TWRP recovery v.2.6.3.0 already installed, but I'm sure it isn't compatible with latest android versions, so no chance of an install via that
It will be interesting to see if others from the old thread pick up your link.Thanks again. .. Jack
Click to expand...
Click to collapse
Great! Actually, Starting from lollipop, rom installs require larger internal space. Since we barely have sufficient space for system on our A760, the internal storage needs to be repartition (done by HDD Raw copy tool). Luckily the provided image 'Lenovo_A760.imgc' will automatically install the updated recovery TWRP 2.8.7 (compatible for the rom install) so we dont have to.
I do think others from the old thread already shifted to other phones

The QPST link given is no more. Any chance you have another download link? Preferably one without malware, as there seems to be some of them floating around.
Thanks

astudent said:
The QPST link given is no more. Any chance you have another download link? Preferably one without malware, as there seems to be some of them floating around.
Thanks
Click to expand...
Click to collapse
I have updated with new download link (now its working). Sorry for the ads. You can click the 'Skip the ad' button after waiting for 5 seconds, or you can Google Qualcomm QPST if you prefer not to click it.

GM mellomade,
I have CM13 flashed OK now + the updated recovery, I'm finding heavy it on battery consumption,
mine loses 25% overnight with no additional apps installed as yet.
This is much higher than the unofficial CM11 Rom I have been using,
I've restricted some of google services in Privacy guard, this has helped a little
but I see no other way of reducing battery drain.
How do you find yours ?, and any suggestions please ?. ... J.

jachol said:
GM mellomade,
I have CM13 flashed OK now + the updated recovery, I'm finding heavy it on battery consumption,
mine loses 25% overnight with no additional apps installed as yet.
This is much higher than the unofficial CM11 Rom I have been using,
I've restricted some of google services in Privacy guard, this has helped a little
but I see no other way of reducing battery drain.
How do you find yours ?, and any suggestions please ?. ... J.
Click to expand...
Click to collapse
I was having the same experience too. I use Greenify App from play store, and put ALL apps into hibernation, except the one I required their notification to be alive (e.g; WhatsApp). That helps too. I guess that is one of disadvantages having an unofficial build, because it is not natively supported for our phone. Hence the high battery drain issue. On the bright side, we get to experience the latest (even though not updated) ROM :victory:

mellomade said:
I was having the same experience too. I use Greenify App from play store, and put ALL apps into hibernation, except the one I required their notification to be alive (e.g; WhatsApp). That helps too. I guess that is one of disadvantages having an unofficial build, because it is not natively supported for our phone. Hence the high battery drain issue. On the bright side, we get to experience the latest (even though not updated) ROM :victory:
Click to expand...
Click to collapse
OK, Thought I may have a problem with ROM download, I did try a reflash which didn't help any. I'll try Greenify later, one thing I like about this ROM is the minimal system apps used (no bloatware).
My present phone (X-BO 06) running Lollipop, has a setting which allows the phone to switch off/on automatically overnight which is great for battery saving, I must see if i can find an app that does the same. Thanks again for the info. ... J. :highfive:

jachol said:
OK, Thought I may have a problem with ROM download, I did try a reflash which didn't help any. I'll try Greenify later, one thing I like about this ROM is the minimal system apps used (no bloatware).
My present phone (X-BO 06) running Lollipop, has a setting which allows the phone to switch off/on automatically overnight which is great for battery saving, I must see if i can find an app that does the same. Thanks again for the info. ... J. :highfive:
Click to expand...
Click to collapse
aah.. we do have that auto start & shutdown setting on our official rom (4.1.2). Im guessing you want that functionality without installing any new apps right? If not, you may look into Phone Schedule from play store. It support android 6.0. No prob

mellomade said:
aah.. we do have that auto start & shutdown setting on our official rom (4.1.2). Im guessing you want that functionality without installing any new apps right? If not, you may look into Phone Schedule from play store. It support android 6.0. No prob
Click to expand...
Click to collapse
mellomade,
Are you saying that we do have the Off/On option with this lollipop ROM ?, if so I haven't found that it in settings, I will take another look, it does make a big difference to battery saving. ... J.

jachol said:
mellomade,
Are you saying that we do have the Off/On option with this lollipop ROM ?, if so I haven't found that it in settings, I will take another look, it does make a big difference to battery saving. ... J.
Click to expand...
Click to collapse
No no no. I think you may have misinterpreted my message there. I did mention, on our official rom, which is 4.1.2, the A760_1_A_2_0057_130828 updates from Lenovo. Sadly not on this unofficial cm build. However you can check out greenify, it does makes a lot difference if you hibernate unused apps. Hence, if this is your secondary phone, you may even hibernate all apps (which can significantly reduce battery consumption) without have to worry about any incoming notifications, am I right.

mellomade said:
No no no. I think you may have misinterpreted my message there. I did mention, on our official rom, which is 4.1.2, the A760_1_A_2_0057_130828 updates from Lenovo. Sadly not on this unofficial cm build. However you can check out greenify, it does makes a lot difference if you hibernate unused apps. Hence, if this is your secondary phone, you may even hibernate all apps (which can significantly reduce battery consumption) without have to worry about any incoming notifications, am I right.
Click to expand...
Click to collapse
Ah yes !, gotcha now ... total misunderstanding this end, and yes I've installed greenify, it helps a lot. Thanks again. ... J.

Can you please give a device tree of this rom.I really need it.

[OFFICIAL/UNOFFICIAL] LineageOS 19.1 for Amlogic G12*/SM1 Family Devices

{
"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"
}
Amlogic G12*/SM1 Family Devices
Code:
- Your warranty is now void.
- You have been warned.
- Use at your own risk.
Introduction:
This is the Official Lineage OS 19.1 thread for the Amlogic G12*/SM1 SoC family of devices.
Downloads:
Please follow the install instructions in your device's Wiki page linked below exactly, and make sure your device's firmware matches the required firmware listed:
Official Builds:
deadpool - Google ADT-3
wade - Dynalink TV Box (4K)
Disclaimer: My unofficial builds have full Android TV Google Apps and some other goodies included. OTA's roll roughly once a month. Support not guaranteed or implied.
Unofficial Builds:
deadpool - Google ADT-3
dopinder - Walmart Onn UHD Box
sabrina - Chromecast with Google TV
wade - Dynalink TV Box (4K)
We also support a few development boards, but at least (for now, until we have time to write up instructions), you're on your own to figure out the install process and set things up:
m5 - Banana Pi M5
odroidc4 - Odroid C4
radxa0 - Rock Pi Radxa Zero
EDIT: The development boards don't boot on LineageOS 19.1 at the moment for some reason, we're looking into it.
If you don't follow these instructions, or use 3rd party add-ons (like Magisk) please don't expect support here.
Known Bugs:
Recent apps/Multitasking menu doesn't launch.
(sabrina only) The remote firmware sometimes gets hung up, you can reboot to solve this issue.
(dopinder/sabrina) L1 is currently broken, this is what is holding up official builds for these devices.
Notes:
GApps are baked in on Unofficial builds - No, I will not be building without GApps included for this device. These builds are built, packaged, and signed by me, and not affiliated with LineageOS whatsoever.
Firmware is shipped in the ROM package for this device, so you'll end up on the newest version of compatible firmware after install. Please don't touch firmware partitions after install.
On the unofficial OTA is provided the same way officials would have them.
Find any more on an official build? Report them according to this guide.
FAQ:
Does L1 Widevine DRM break when I unlock my bootloader?
Nope, it works fine. L1 certificates, and the mechanism that reports is all still exist and work as expected.
Can I haz Netflix?
Yup! Play Store has it for you. Unless you're on dopinder or sabrina, but that will be fixed soon hopefully.
Is this Android TV or Google TV?
Android TV, with some of the better components of Google TV.
Can I go back to stock and relock the bootloader?
Yeah, grab the factory image for your device and flash it just like you would for a Pixel device, you can find the factory images here. Don't know it I'd relock though, consider that process largely untested on these device. Especially on sabrina, where you can't necessarily re-unlock should you ever want to.
Are these the stock codenames for these devices?
Astute observation, no, they are not. The ADT-3 is actaully `adt3`, but earlier in production is was `deadpool`, which is much cooler. The Dynalink box internally is extremely similar to the ADT-3, so we coined it `wade` after Wade Wilson, AKA deadpool. The Onn box is in the same family, but different enough to coin it `dopinder`, after, well, go watch Deadpool the movie I guess. sabrina is actually the codename given by Google - no clue as to the reason.
Does it pass SafetyNet?
Maybe - the only sure fire way it Magisk, as our boot loader is unlocked and can't be relocked safely.
Does the stock remote work?
Yup, just like it would on stock, in-remote-microphone and all! If it's an IR remote like wade's, it will even work in recovery!
Can we we support higher resolution than 4K, higher FPS, or HDR on non-certified screens?
Nope.
I have a very similar device! Can I install these builds and use them?
No. Please don't do that. You will brick your device, as we include firmware and bootloader images.
If you're a developer looking to help port to a new device, contact me.
Kernel Source: https://github.com/LineageOS/android_kernel_amlogic_linux-4.9
Contributors:
npjohnson
bgcngm
stricted
webgeek1234
deadman96385
trautamaki
luca020400
aleasto

i probably will write up install instructions for the `BananaPi-M5` and `Odroid C4` Soon™
its a bit more complicated than just booting into recovery and flashing it unfortunately

I managed to install this on the onn 4k tv box (I used a usb keyboard and flash drive in the recovery) and everything went fine while installing but now I'm just stuck at the boot animation. I've left it on for at least 30 minutes and it never goes anywhere. Here's the serial log: https://paste.ee/p/7PAxS
It pretty much just stops there except for the occasional healthd battery message.

Do these builds support Signature Spoofing to replace GApps with MicroG?

Big Dumb Object said:
Do these builds support Signature Spoofing to replace GApps with MicroG?
Click to expand...
Click to collapse
No, as MicroG doesn't emulate what Android TV needs. Different GMSCore.

lmore377 said:
I managed to install this on the onn 4k tv box (I used a usb keyboard and flash drive in the recovery) and everything went fine while installing but now I'm just stuck at the boot animation. I've left it on for at least 30 minutes and it never goes anywhere. Here's the serial log: https://paste.ee/p/7PAxS
It pretty much just stops there except for the occasional healthd battery message.
Click to expand...
Click to collapse
yeah, aware of the issue, it's video firmware not loading, building new builds now.
But for what it's worth, you don't need a keyboard or drive - you can adb sideload it over usb - easiest method, just like the wiki describes.

npjohnson said:
No, as MicroG doesn't emulate what Android TV needs. Different GMSCore.
Click to expand...
Click to collapse
Sad. I vaguely recalled something about that, but couldn't find any concrete proof when asked.
Please consider releasing the full Android as it was with Shield TV. I believe it will be in demand, given the negative attitude of a lot of power users towards Android TV.

Big Dumb Object said:
Sad. I vaguely recalled something about that, but couldn't find any concrete proof when asked.
Please consider releasing the full Android as it was with Shield TV. I believe it will be in demand, given the negative attitude of a lot of power users towards Android TV.
Click to expand...
Click to collapse
Eh, maybe once we're in a more functional state (eg. Hardware OMX gets fixed).

npjohnson said:
yeah, aware of the issue, it's video firmware not loading, building new builds now.
But for what it's worth, you don't need a keyboard or drive - you can adb sideload it over usb - easiest method, just like the wiki describes.
Click to expand...
Click to collapse
I couldn't figure out how to navigate the recovery menu. I tried the button on the side like in the stock recovery but pressing it did nothing and holding it would change the highlight color to green but it didn't actually run the option that was highlighted. It was detecting the button presses (there were keyevents in the serial log) so it isn't just a broken button. I tried doing adb sideload without selecting the option but I just got `adb: sideload connection failed: closed`

lmore377 said:
I couldn't figure out how to navigate the recovery menu. I tried the button on the side like in the stock recovery but pressing it did nothing and holding it would change the highlight color to green but it didn't actually run the option that was highlighted. It was detecting the button presses (there were keyevents in the serial log) so it isn't just a broken button. I tried doing adb sideload without selecting the option but I just got `adb: sideload connection failed: closed`
Click to expand...
Click to collapse
okay, figured it out, you need to hand flash DTB before booting recovery, will update instructions

npjohnson said:
okay, figured it out, you need to hand flash DTB before booting recovery, will update instructions
Click to expand...
Click to collapse
Sounds good. One more question, is this build using a 64-bit kernel? I'd like to use the app for my drone on a big screen and this box would've been perfect if the stock kernel wasn't 32-bit.

lmore377 said:
Sounds good. One more question, is this build using a 64-bit kernel? I'd like to use the app for my drone on a big screen and this box would've been perfect if the stock kernel wasn't 32-bit.
Click to expand...
Click to collapse
64-bit kernel, 32-bit userspace - aiming to do 64 bit userspace someday.

Do you have an ETA for when the next builds will be done?

lmore377 said:
Do you have an ETA for when the next builds will be done?
Click to expand...
Click to collapse
they're uploaded now - sorry, got caught up putting out fires at work all day today lol

npjohnson said:
they're uploaded now - sorry, got caught up putting out fires at work all day today lol
Click to expand...
Click to collapse
I'll try it and flashing dtb for the button in recovery in a bit

lmore377 said:
I'll try it and flashing dtb for the button in recovery in a bit
Click to expand...
Click to collapse
DTBO/DTB - they need to be in sync.

npjohnson said:
DTBO/DTB - they need to be in sync.
Click to expand...
Click to collapse
I flashed the two (I got them from here) and now the button and usb otg don't work at all. I tried to flash back to stock but the box got stuck on the can't load android system screen and it was ignoring all my attempts at interacting with it (it was even ignoring Ctrl+C in uboot), but luckily I managed to boot into the lineage os recovery by putting it on a flash drive and holding down the button then wiping /misc thru the serial console.

lmore377 said:
I flashed the two (I got them from here) and now the button and usb otg don't work at all. I tried to flash back to stock but the box got stuck on the can't load android system screen and it was ignoring all my attempts at interacting with it (it was even ignoring Ctrl+C in uboot), but luckily I managed to boot into the lineage os recovery by putting it on a flash drive and holding down the button then wiping /misc thru the serial console.
Click to expand...
Click to collapse
I'll look into this... Can you try flashing the newest build through lineage recovery and wipe data?

npjohnson said:
I'll look into this... Can you try flashing the newest build through lineage recovery and wipe data?
Click to expand...
Click to collapse
Is there any way to activate sideload mode through adb shell or the serial console? Again, since the button isn't working (still works in uboot so it isn't a hardware issue) with the new dtb I can't navigate through the recovery menu.

lmore377 said:
Is there any way to activate sideload mode through adb shell or the serial console? Again, since the button isn't working (still works in uboot so it isn't a hardware issue) with the new dtb I can't navigate through the recovery menu.
Click to expand...
Click to collapse
Adb reboot sideload works, maybe just reboot sideload?
I'll go grab an Onn box at Walmart tmrw afternoon.
I know it works as 3 of our developers have and use it.
Just a matter of install process it seems...