Database Info

[Q] Soft Bricked Nexus S 4G - Save the Baby Photos!

I've spent 4-6 hours researching and trying things and have become quite familiar with rooting, fastboot, adb, sideload, and various other tools and have many installed & working, so if I make a noob comment or mistake, go easy on me. I did my best to do my own due diligence.
Here's the situation:
Nexus S 4G - stock from Sprint
Android 4.1 as pushed from Sprint
Not Rooted
Debugging Mode not enabled
Launcher, UI, Settings, Apps, etc fail ("has stopped") if they use the UI
Things not requiring UI do start and run
Android boots up normally to the lock screen (I have pattern lock). Apps start up in background fine (Locale, Alarm Clock Extreme, etc). Upon unlocking, I get "Unfortunately, Launcher has stopped." Repeatedly. It won't let me click any apps. I can, however, bring down the notification window. Selecting anything in the notification window fails, with "____ has stopped," including Settings, Messaging, Google Play, etc. When I plug in USB, I see the green Android with the "Turn on USB storage" button, but I can't click it before "System UI has stopped."
Unfortunately, most solutions warn "this will wipe all user data," and I don't have backups of a hundred or more photos and videos of my daughter's first year. So wiping data will be my LAST resort...and even then I may try forensic recovery from a dd image (I work in Computing Security, so have a fairly good technical background).
What I've tried, and result:
Reboot into recovery - I get dead Android with red exclamation
Wipe cache & reboot - no improvement (tried 5-10 times)
Reboot into Safe Mode - no improvement
Push 3rd party launcher - installs, but upon unlocking and selecting Launcher / Go Launcher (.e.g), I get "Go Launcher has stopped."
Fastboot - I get device listed/connected, but most commands cause wipe, so I haven't ventured much further
Calling Sprint and having Jellybean re-pushed to my device - it appeared to push (I saw update status message), but when I rebooted, no apparent difference (maybe it didn't push?)
Add/Remove apps via Play Store - works fine. I can remove apps (and have removed nearly all) and add apps, and they uninstall or install successfully (notification window confirms). But I can't access any newly installed apps due to the "stopped working" window.
Suggestions I can't try:
adb backup/shell/pull etc - my debugging mode is not on and I can't turn it on.
USB backup - can't enable USB Mode, and I don't have an automount capability
fastboot oem unlock - wipes phone
I want to try adb sideload <image>, but I haven't been able to confirm whether this truly wipes the user partition or not. If anyone can confirm, let me know. My phone enters sideload mode via:
1) boot to fastboot (power + vol up from OFF)
2) select recovery
3) at dead android with red exclamation, again press power + vol up and release. Menu appears only after you release.
4) 2nd option is "Apply update from ADB" which puts phone into special adb mode where the ONLY command accepted from your PC is "adb sideload."
Any suggestions on how I may be able to retrieve my photos and videos given this completely borked OS?
Thanks.

You could try this. It's Beta and buggy but might work.
http://forum.xda-developers.com/showthread.php?p=36499906

jayjay3333 said:
You could try this. It's Beta and buggy but might work.
http://forum.xda-developers.com/showthread.php?p=36499906
Click to expand...
Click to collapse
Thanks for the suggestion, but that requires Debugging Mode enabled. It's essentially a GUI for "adb backup." Unfortunately, I can't get debugging mode enabled in any way known to me yet.
Is anyone out there familiar with the adb sideload command? I'm really curious if sideloading an image into user partition in any way wipes data.

SOLVED - how I saved the baby photos
I thought I'd give a quick post on how I actually was able to recover my baby's photos. I was at my last resort and decided I'd just try to do a dd image of the card after I did a "wipe and factory reset." My hope was that a "wipe" did not actually write 0s over the entire internal SD card, but just erased the FAT. In that case, I figured, if I took a dd image, I could use a tool like Forensic Toolkit or similar file carving tool to carve out .MP4, .3GP and .JPG files.
So I selected the wipe and factory reset, but had my Linux system ready to do the dd IMMEDIATELY upon reboot. I had ALREADY plugged my USB connector into the Linux system. When the factory reset completed, the system booted directly to the "Enable USB Mode?" prompt. I enabled it, and performed a ~14 GB dump. I know this only catches the user partition, but I didn't care about the system partition, and hoped it would be re-allocated in roughly same location as previously (not stomping on my user data). After the dd was complete (about 3 hrs or so), I bit the bullet and just signed into my Google account and had Google Backup "restore settings."
Later, I was using ES File Explorer and noticed all JPGs were still in my DCIM folder. When I browsed with Gallery ALL PHOTOS AND MOVIES were still present! :victory:
I did not have any backup/recovery software installed to the best of my knowledge, except for Google's "settings backup." So my best explanation is that the wipe & factory reset DID NOT wipe my user data. This may be a fluke, or due to me having USB connected during the wipe & reset. Not sure.
Just to be sure we're all talking about the same "Factory Reset," on my stock Nexus S 4G running Android 4.1.1:
- power off phone
- press Vol Up and Power at same time -- you'll get the Bootloader
- select Recovery -- you'll get dead android with red exclamation after a few seconds
- press Vol Up and Power at same time again -- you'll get a secondary menu
- select "wipe data/factory reset"
- select "Yes" from a long list of "No" with one randomly-placed "Yes"
Hope this helps someone down the road...
I also wanted to note about the "ADB sideload" command. It can only be used to push incremental updates to the device--not full images needed to recover from a corrupted OS. I successfully sideloaded the 4.1.1 update (re-applied the 4.1.1 that I was currently running), which included "launcher2.apk" and a couple other launcher components that gave me hope. But when the 4.1.1 sideload completed successfully and I rebooted, launcher was still hosed. The 4.1.2 incremental update hasn't been released by Sprint yet.

That was hell of a read. The Samsung toolbox program you can do a temp boot and mount your SD card. But I'm too late to tell you now sorry.
Sent from my Nexus S using xda app-developers app

A few minutes googling would have told you that adb is set in the build.prop
Code:
persist.sys.usb.config=adb
OR adb with mount external
persist.sys.usb.config=mass_storage,adb
OR adb with mtp, but you need a kernel
persist.sys.usb.config=mtp,adb

Hi Can you tell us the dd command that you have used to dump the data?

My Case was little different. My friend had tried unlocking screen pattern and it got locked.
Wifi was not on neither was it rooted nor usb debugging mode enabled.
Solution:
I did a factory reset with my phone connected to PC.
once this is done during reboot a prompt came up asking whether to enable USB debugging need to be enabled.
I enabled it and I could see all my data from my PC.
I copied everything and continued with booting.
Hope this will help someone

Pavankumarvijapur said:
My Case was little different. My friend had tried unlocking screen pattern and it got locked.
Wifi was not on neither was it rooted nor usb debugging mode enabled.
Solution:
I did a factory reset with my phone connected to PC.
once this is done during reboot a prompt came up asking whether to enable USB debugging need to be enabled.
I enabled it and I could see all my data from my PC.
I copied everything and continued with booting.
Hope this will help someone
Click to expand...
Click to collapse
I wonder if this will work with a Nexus 7 on 4.3-4.4 ota soft brick

This is why rooting unlocking and a custom recovery is so important.
Sent from my XT897 using XDA Premium 4 mobile app

[TUTORIAL]ByPass Pattern

Having protection and security on your Android device is one essential thing you should take into consideration, especially if there are people who tend to snoop around your device without your permission. The possibility of actually forgetting the pattern you’ve set to unlock your device is not that high, but it may happen. What’s worse, your friend may have messed around with your Android device and set a completely different unlock pattern, leaving you stumped when you try to unlock your device.
In situations like that, you could lose all hope and start bickering with the perpetrator (either your friend or yourself), not realizing that there is a way to go around that misfortune. Thanks to XDA Developers member m.sabra, an easy way to regain access to your locked device has been made for your perusal.
This guide will work on any Android device, rooted or not. It uses the Android Debug Bridge or ADB. If you are having a hard time recalling what ADB is or you don’t know what it is, check our article about how to install the Android SDK (Software Development Kit) and how to setup and use ADB (Android Debug Bridge).
In this guide, learn how to bypass the security pattern lock on your Android device.
Warning
The instructions in this guide reportedly work for both rooted and non-rooted devices. Root privileges, however, make this guide work in most cases. Several users have reported that the guide does not work in certain non-rooted devices.
The information in this guide is provided for instructional and educational purposes only. There is no guarantee that these instructions will work under your specific and unique circumstances.
Use these instructions at your own risk. We shall not hold any responsibility or liability for whatever happens to you or your device arising from your use of the info in this guide.
Read and understand the whole guide first before actually performing the instructions.
Requirements
Any Android device with USB Debugging enabled, preferably rooted; or, if not rooted, the device must be running a kernel that grants root access to the adb shell.
To enable USB Debugging on devices running Android 4.0 and up, go to Settings > Developer Options. Check the box beside the USB Debugging option.
For devices running on older versions of Android, go to Settings > Applications > Development. Check the box beside the USB Debugging option.
A computer with ADB installed
For help in setting up ADB on your computer, check our article about how to setup and use ADB (Android Debug Bridge)
Your device’s USB cable
Make sure your device’s battery is charged 75% or more to avoid interruptions during the process.
Backup all personal data on your phone to make sure you have a copy of your personal data (e.g., contacts, SMS, MMS, Internet settings, Wi-Fi passwords, and the like) in case the procedure in this guide erases such data.
For backup tips, check our guides on how to sync your data to the cloud and how to create local backups of your mobile data.
Instructions
Connect your device to your PC using the USB cable.
On your computer, open a terminal window (or command prompt on Windows-based machines).
Type in the following commands at the terminal or command prompt window. Press Enter after every line:
Code:
adb shell
The prompt should display a # rather than a $. Otherwise, enter su to switch to the root user.
Code:
cd /data/data/com.android.providers.settings/databases
sqlite3 settings.db
update system set value=0 where name='lock_pattern_autolock';
update system set value=0 where name='lockscreen.lockedoutpermanently';
.quit
exit
adb reboot
After your device has rebooted, enter the following commands at the terminal:
Code:
adb shell
The prompt should display a # rather than a $. Otherwise, enter su to switch to the root user.
Code:
rm /data/system/gesture.key
exit
adb reboot
Your device will reboot. After it reboots and asks for a security pattern, you can use any pattern and the device will still unlock.
Once you regain access to your device, make sure to change the system security settings to re-select another unlock pattern.
Congratulations! You have successfully bypassed the pattern unlock on your device. You don’t need to panic anymore because you now know that there is a way back into your phone after you’ve been locked out.
Click to expand...
Click to collapse
Credits
 @m.sabra

Another security bug highlighted and now shared with the world. Won't be using pattern unlock in future. ....
Sent from my GT-I9505 using Tapatalk 4 Beta

ardsar said:
Another security bug highlighted and now shared with the world. Won't be using pattern unlock in future. ....
Sent from my GT-I9505 using Tapatalk 4 Beta
Click to expand...
Click to collapse
I use pattern lock and I am rooted. But I make sure the USB de-bugging mode under Developer options is never ticked (I only turn it on specifically when required and then switch it off). My phone is also encrypted using the stock settings options. These 2 things will render the above technique useless and make your phone a much secure object.

Still it can be cracked even if you are not rooted and USB Debugging is turned off, by Aroma File Manager

[GUIDE] TVPad 4 Master Guide [Unbrick/Restore/Root/ADB/Apps]

TVPad 4 is fourth in a series of Android-based IPTV settop boxes targeting the worldwide Chinese communities at large, although it seems to work well as a basic Android TV box. Support for all its predecessors (TVPad 1-3) have been discontinued. This guide will only focus on TVPad 4, model M418. Also this device have been banned from US and upgrading it may "brick" it - more on this later.
The method I used below is gathered from various sources elsewhere but not much on rooting and ADB. This is a compilation of all the most important info in one place. I am not sure if its bootloader is locked or not, but the Android 4.4 kernel sources can be found at openlinux.amlogic.com.
Physical specs:
AmLogic S805 SoC: ARM Cortex-A5, quad-core 1.5Ghz, Mali450 graphics, 1080p H.265 support
~1GB RAM
microSD card slot
HDMI out
USB-A port
Hardware needed:
To fully complete the process you'll need:
Monitor/TV with HDMI port
USB hub
microSD card
USB drive (optional)
USB keyboard
USB mouse
The remote that came with your box
Files needed:
* TVPad 4 5.054 firmware + TWRP 2.8.1.0: https://tvpadtalk.ca/discussion/1071/downgrading-tvpad-4-to-5-054/p1
The TWRP seems to be the modified from the one for AmLogic k200. Only the one from above work; the one from TWRP themselves do not.
* TVPad 4 5.066 OTA update: http://www.phoneunlock.com/forum/viewtopic.php?f=5&t=590
If you have this box and are in the US, do NOT do 5.066 update; your box is going to be banned. Might as well go all out and repurpose it into a general purpose Android TV box; but for the rest of the world, this update directs your box to different servers where it's mostly business as usual. You should be able to go direct from 5.054 to 5.066 following this guide, despite what others say.
* Root zip: http://www.freak-tab.de/finless/s89_root_update.zip
* APK install hint file:
Create a file named batchinstall.banana with contents below:
Code:
directory=
checkapp=no
Preparation
1. Download the 5.054 firmware and unzip into root of your microSD card. You should have recovery.img and TWRP folder. They are the TWRP recovery and a 5.054 TWRP backup respectively. Devices boots from recovery.img on root of microSD card if detected.
2. NON-US ONLY: Download the 5.066 OTA update to microSD root.
3. Download root zip to microSD root.
4. Put batchinstall.banana and any APKs you want to install on your USB drive or microSD. There is a APK pack of 23 apps for Cantonese speakers or 29 apps for Manadarin speakers available out there, but I haven't bothered. I included an updated SuperSU, ES File Explorer (preferably an older version; I used 4.0.4.9; newer ones are heavily loaded with ads), VLC, Firefox, AdAway, Terminal Emulator (by Jack Palevich). The last 4 being open source should also be available from F-Droid. Substitutions can be made to taste but Terminal Emulator is required to enable ADB (see below).
Enter Recovery
You will need to use stock recovery for OTA update AND TWRP for 5.054 firmware and root.
1. Connect HDMI monitor and USB hub to device. Connect USB keyboard and mouse to the hub. Leave power disconnected.
2. Look for a hole on the underside. If you have one, stick an iPhone/iPad SIM ejector pin in it and feel for a button. If able, this is the recovery button and you may skip to step 6.
3. Pull off the 4 rubber feet on the bottom and remove 4 screws under them.
4. Pry around the seams and lift the bottom cover off.
5. You either have a recovery button on the PCB or an empty spot for it. If no button, you'll have to short the bottom two contacts where the button is supposed to be (with all ports on the top edge).
6. Insert microSD card into "TF" slot. IMPORTANT: Leave popped out to enter stock recovery; fully insert to enter TWRP.
7. Press and hold the recovery button (or short the contacts) while plugging it in. Keep it pressed (or contacts shorted) until the recovery or TWRP appears.
8. Operate stock recovery with keyboard and TWRP with mouse.
Re-flash 5.054 - Downgrade/Unbrick
People do this to recover from "use restricted" or some other server errors after this thing is sued out of the States. I have also used it to recover from a soft brick situation.
1. Fully insert microSD card. Enter TWRP.
2. Select Restore. Choose External SD for storage.
3. Select the only available package to restore.
4. Swipe to Restore.
5. When complete, do not reboot yet. Return to main menu and select Wipe. Swipe to Factory Reset.
6. US ONLY: Remain in TWRP and proceed to step 2 of rooting.
7. NON-US ONLY: Return to main menu and select Reboot, Recovery. Immediately after screen go blank, push the microSD card again to eject it. It will pop out half way. Leave it hanging there. Proceed to update 5.066 next.
Update to 5.066 - NON-US ONLY! New server and Play Store support.
1. Enter stock recovery.
2. Fully insert microSD card.
3. Select Apply update from EXT and press Enter.
4. Select your 5.066 update file and press Enter.
5. When update complete, unplug power. Proceed to rooting.
Rooting
This is too easy with TWRP.
1. Fully insert microSD card. Enter TWRP.
2. Select Install, then the root zip file. Swipe to install.
3. Reboot into system and proceed with initial setup.
Kingroot also works but leaves some very persistent crap and questionable apps on the system so I do not recommend rooting using it.
Sideload apps
Plug the USB drive with your apps and batchinstall.banana file into the device or hub. Batch installer will appear. Select Batch Install and check that all apps you are installing are there and checked, then select Install.
Enable ADB
TVPad 4 does not have a USB slave port so ADB is only through TCP/IP. Steps below assume you have adb working on your computer.
1. Connect a USB mouse if not already.
2. Move mouse to right half of top of screen then drag down. Click on the gear to enter regular Android Settings app.
3. Enable Developer Options - About Mediabox, click Build Number 7 times.
4. Enable USB Debugging in Developer Options.
5. Open Terminal Emulator (sideload it if you haven't already).
6. Type in the following:
Code:
$ su
(Grant root if prompted)
# setprop service.adb.tcp.port 5555
# mount -o remount,rw /system
(Make the same setprop change in /system/build.prop - uncomment or add the line)
# stop adbd
# start adbd
7. Find the IP address of your TVPad from its own over-simplified settings page.
8. Open a command prompt/terminal on your computer and do this:
Code:
> adb connect <TVPAD IP ADDRESS>
(Authorize your computer on the TVPad.)
> adb devices
(confirm its IP is listed and not "unauthorized")
> adb shell
$ su
(grant root if prompted)
#
(success!)
# chmod 660 /data/misc/adb/adb_keys
(Double check permissions the public key file of authorized ADB clients)
9. Reboot and check that the change stays.
You're done! Now you have full control of this little TV box even after its server go under for good.
Additional apps
Kodi 15.2 seems to work on this box. 16.1 is untested. 17.x will not work since it requires Lollipop. Download from kodi.tv.
If all you want out of TVPad is TVB programming, the official app TVBAnywhere works on this box. About US$100/yr subscription for its own original programming only. Oh and it doesn't serve the States either. Go figure.
The gapps framework added with 5.066 is very minimal and doesn't work for eg. maps. You'll need to get it from apkpure. Use version 11.0.38-030-155006848.
I'm still looking for a decent launcher.
Credits:
https://www.youtube.com/watch?v=6evvWebosnU
https://www.youtube.com/watch?v=ZtY_qdYzmPs
https://www.youtube.com/watch?v=W2heIbUdZVE

can we flash any other rom on TVPad 4 since we can install TWRP??

I rooted easily with kingroot apk. to get shell, I just used my laptop as proxy between wifi and lan, created a meterpreter reverse_tcp metaploit payload, connected back to my laptop, shell and then su...

3vilhomer said:
can we flash any other rom on TVPad 4 since we can install TWRP??
Click to expand...
Click to collapse
To be honest, I'm more interested in if we can get Lollipop on this thing, for that is required for Kodi 17.

For whatever reason I can't boot into the TWRP. I have all the recovery.img and TWRP folder located in the root directory of the SDcard and my SDcard is FAT32 formatted. What did I do wrong?

Suppport has been officially terminated for this box so, it will only be a normal TVbox.
I'm kinda wondering if the SoC supports at least lollipop. A custom rom would be cool to run Leanback apps with a few modifications

ya, is there anything we can do with this box now since most live tv apps doesnt work on it anymore

Do you know where I can grab the file for TVPAD1? I am not sure which model I have, is only written TVPAD on top and there is no 2S, Plus or anything else.

TvChina, a subsidiary pay TV app after TvPad 4 ceased operating on June 1st. TvPad, the parent company, together with its Blue TV etc, have gone bust due to lack of funds from global dwindling sales. Now that the box is useless, can someone upload a root file so we can wipe then reuse it for other purposes? Found a related message on Google but it's has been blocked. Thanks in advance. Wonder if someone can get hold of firmwares for UnBlock or evPad etc so we can tune this into other sites.

did anyone ever put a different android OS on this and got the IR blaster to work too??

3vilhomer said:
did anyone ever put a different android OS on this and got the IR blaster to work too??
Click to expand...
Click to collapse
They were able to upgrade to android lollipop here:
tvpad.ca/discussion/1993/tvpad4-upgrade-to-android-lollipop-5-1

The root file "s89_root_update.zip" link is not working anymore. Does anyone has a copy > please post it here.

Samsung Luna StraightTalk S120VL FRP Bypass

Samsung Luna StraightTalk S120VL FRP Bypass
In Model Number usually..
BL = Tracfone
VL = Straight Talk
(Both the same company but there are differences in ways used to do FRP removal depending on certain devices so I always list accordingly)
Tested on U2 firmware APJ2 so not sure if this works on U1. If the U2 firmware is wanted I will host and post it here.. It can be found by searching google too.)
Security Patch: (October 1, 2016) and.. should work fine on any other.
I had a stack of these phones gave to me for FRP Removal and these days I usually use Uni Android Tools, OctoPlus, or Z3X boxes for SamSung work. I tried while knowing this would most likely not be possible with this handset model. Success = 0. Tried a multitude of other operations and still nothing. Upgraded Firmware to the latest U2 because i had it, couldn't find a (free) combo in the time i looked and thought maybe it would allow something different.. I might be right. This is the first one in the stack I have done this on. So I will edit / post about U1 (Binary 1) models once this one is finished off. I know the methods work below just getting this write up done first. Anywho..
Whats needed? (each will depend on method taken below)
1) Bluetooth EarPiece
2) Old sim card (Verizon best for this way)
3) ADB Installed (Install this anyway as it's handy to have!) - Here is a link to a super quick and easy installer that will do it and while making ADB systemwide. Thanks to XDA user @Snoop05
Link for basic info - https://www.xda-developers.com/15-s...ng-fast-adb-fastboot-and-driver-installation/
Link to Thread for dicussion - https://forum.xda-developers.com/showthread.php?t=2588979
DIRECT DOWNLOAD LINK - https://forum.xda-developers.com/attachment.php?attachmentid=4623157&d=1540039037
4) ADB FRP Removal Application
Lots of ways past this initial point.. Here are 3 i know of that will work for this $20 old pocket buddy.
1) Preperation - First start off by hard resetting your Samsung Luna S120VL
Next find a sim card. I used an older used Verizon sim card. No longer in service. Put it in.
Boot phone. Goto Emergency Dialer. Dial 112 and instead of taking you to 911 (good yeh?) you'll get a voice greeting by Verizon. While this happens pair your bluetooth. (best if you have it in pair mode before dialing)
2) Removal - Three ways to do this. 2 more possibilities to do at the bottom of this post.
a. Connect to WiFi with Bluetooth. -> [Will do this when i get time]
b. Stay offline and use Bluetooth to open Calculator. Type in Calculator (+30012012732+ Now DRParser will open. Type now.. *#0808#. USB Settings will open now select the last one that says DM + Modem + ADB. Select reboot and watch your phones screen when you reboot. Enable when you get the authentication popup. Stay on the very first page of the setup wizard.
-
Now open CMD prompt type
Code:
adb devices
and make sure your device shows something like this -
List of devices attached
8e60d4bf device
Yeah? Ok now copy the following code and paste it into the CMD window and press enter.
Code:
adb shell content insert --uri content://settings/secure --bind name:s:user_setup_complete --bind value:s:1
Follow through the Setup Wizard which will quickly drop you onto your home screen and now you are done!
If the above command does not work in your case you can try the following command below. This will take you to login screen and then you can enter you Google account.
Code:
adb shell am start -n com.google.android.gsf.login/
If both previous commands do not work then try this.
Code:
adb shell am start -n com.google.android.gsf.login.LoginActivity
c. Stay offline and use Bluetooth to open Calculator. Type in Calculator (+30012012732+. Now DRParser will open. Type now.. *#0808#. USB Settings will open now select the last one that says DM + Modem + ADB. Select reboot and watch your phones screen when you reboot. Enable when you get the authentication popup.
-
Now use one of the many apps out there to remove FRP now that ADB is enabled. I will ask the moderators about posting but not sure it is allowed. Also the one that is easiest to use and that I recommend will trigger a false positive on Anti Virus. IF ok to post I will update this thread with a download.
----
Other Methods?
Accessibility Mode Method - When i get time (if it's possible.. as a quick check on U2 APJ2 didn't allow much)
ADB enabled boot IMG - Found one and these can be made as well but the one i have found (free) is from the Factory Engineering Firmware I believe. I just don't have much more time to fool with these luna phones. You'd just need to flash this then no need for bluetooth.. Again when i get a minute and remember I will put it up here.
Enjoy!
-noidodroid

Thanks

Question [TB-J706F] Restore Netflix L1 on the ROW rom.

As many of you probably know, recently the L1 netflix support for the this tablet dropped to L3.
We tried to restore it for a while without success, because the preinstalled app cannot be uninstalled normally and lower netlfix versions cannot be intalled in the top ot it (at least not from android itself).
But it seems that I finally found a way to do it sucessfully by forcing it through adb, here is the complete guide;
- Enable usb debugging on the tablet
- Get the latest android plateform tools including adb and android usb drivers and install it somewhere (shorter path is better).
- Download the 7.80 version of netflix in the usual place, and save it in the same folder as adb
- Open up a windows command prompt in that folder
- Input
adb install -r -d netlfix.apk (change the package name to whatever you named it)
- Allow the adb access on your tablet if needed
- Completely clear the app data (very important!)
- Disable auto update of that app in google play
- Done!
Please tell me if that worked for you, I might test out other versions to see until which version it does work and which breaks it.