Develop Bugs

[MOD] Hulu Hack 10.3/GB

Ok guys, so I absolutely love Hulu and other legit TV sites, some of which prohibit mobile devices based on a "flash id" similar to what you have with a User Agent string for the browser. It is based on this ID that it prohibits mobile phones from accessing content such as hulu and HBO (I think?). With this mod your phone will appear as though it is a PC running flash and I believe it also modifies your version number to be something like 99.9.999.99 for sites that try and check the version number. I also must make sure to give credit where credit is due. Credit goes to imneveral0ne who posted the modified lib files in the Thunderbolt forums http://forum.xda-developers.com/showthread.php?p=12433036#post12433036.
His mod stopped working because Gingerbread (and 10.3) copies the lib files from the APK itself back into the lib folder (/data/data/com.adobe.flashplayer/lib/) on boot, thus require the mod be redone every reboot. I simply took his mod, wrote a simple script that installs the hacked lib files to /data/flash/ at first for storage, modifies permission of /data/data/com.adobe.flashplayer/lib/ so that it can be written to by the script, and also installs a "run on boot" script at /system/etc/init.d/01-fixflash.sh which will copy the hacked lib files from /data/flash to /data/data/com.adobe.flashplayer/lib/. It also adds Hulu Bookmark app (1.0) to /data/app.
For whatever reason, I've been having trouble replicating a "start from stock, flash, and you're good" situation. Something about my setup isn't quite perfect yet (this is my first "mod"/script, and first flashable zip so any suggestions would be greatly appreciated), as I've had some issues getting it to run on its own the first time. That being said my launcher pro also force closes on every reboot so the leaked EF02 and nagging (ef10 to ef02) downgrade screen may be responsible. The GOOD news is that it does seem to work like clockwork once the script has been run manually for the first time. Enough explaining why, now to the how:
REQUIREMENTS:
Kernel with init.d support (most custom kernels with root support) and root
Busybox (for running the copy commands. If you don’t have it, install ‘busybox installer’ from the market once you are rooted)
Root explorer (recommended, not required)
NOTE: I have developed this file FOR gingerbread, however I BELIEVE it should also work on froyo. Please let me know if it does/doesn’t work on Froyo. If it doesn’t work and needs troubleshooting let me know and I’ll downgrade again to see if I can get it worked out.
INSTRUCTIONS:
EDIT: I'm such a moron, I almost forgot:
Install latest flash player (10.3.185.25) from the market FIRST and be sure to uncheck automatic updates (and don't manually either)
Make sure busybox is installed. One way to test this is to type cp –help in ADB and see if it can run the command. If it does, you’re good to go.
Next, simply flash gbflash.zip. Wipe cache/dalvik if you want (I don’t believe it’s necessary, although again, this is my first time and for whatever reason the script doesn’t seem to want to run on its own the first time)
Upon first reboot, you MAY be lucky enough that it simply just works and you’re all set. I was not this lucky, either due to my semi-lockup (FC of launcher pro) on boot and/or the EF10->EF02 downgrade screen. Anyways, if you still get the "Hulu not available for your platform" error, simply use either root explorer or adb to run the script for the first time manually. In root explorer, navigate to /system/etc/init.d, tap on S98fixflash and select "execute". In ADB, navigate to /system/etc/init.d and type "sh S98fixflash". Wait a sec for it to run, then try Hulu again. It should be working immediately (without a reboot required) AND the script should then run correctly on subsequent reboots.
Like I said this is my first "product" I've been able to make available to the community and am more than open to suggestions, criticisms and ideas of how I can make this script better. Enjoy guys!
EDIT: If you do have issues with the script not running on every reboot, simply install "Script Manager" from the market, navigate to /system/etc/init.d, select S98fixflash and check the "run on boot" checkbox.
NOTE: I believe this hack is EXCLUSIVE to Gingerbread (and maybe Honeycomb). Froyo will not work
http://www.multiupload.com/E9GP7V1QJ1 - update 10/4//2011 for 11.0.1.152 AND hopefully fixed data mounting issues on certain devices so it works easily on CWM on more devices
NOTE: Latest update includes a brand new flashplayer.so files freshly edited, so no more issues with youtube in the browser, and uses TRUE flash 11.0.1.152 libraries for increased performance (no longer based on 10.2) (LOL, flash 11 was only released 4 hours ago, hehe
{
"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"
}
)
Note: after more feedback it seems using busybox installer from the market helps if running the script, even manually does nothing.

Cool
Sent from the Drivers Seat of my Suby txting and Driving doing 100MPH+ in a school zone! Ha.

Wait I'm a little confused...are you saying that your launcher pro FCs and EF10 downgrade are indepenent of this, or is this script causing those problems?
As of right now, Launcher Pro has never FCed on me on EF02, and the downgrade prompt never pops up (it used to but it stopped for some reason).
Jus trying to get all the info before I flash this.
Btw, I assume that simply deleting the .sh file would uninstall this mod, thereby preventing anything from being done at boot? If not, what would be the proper way to uninstall this?
Sent from my SPH-D700 using XDA Premium App

You are correct on uninstall procedure. Delete 01-fixflash.sh from /system/etc/init.d. It also places a 'flash' folder in /data that can be deleted. It also modifies permissions for /data/data/com.adobe.com/libs to make it writable (shouldn't cause any issues if left) but can be undone by uninstalling and reinstalling flash. Yes my launcher pro fcs because of the ef10->ef02 downgrade question (I think). Hope to check again on official release. Please let me know if this a) works b) doesn't or c) (like me) mostly works on most reboots, but script aways work when run by hand.
Another option is to install script manager because you can then tell script manager to run 01-fixflash.sh on boot, and then it should DEFINATELY work, although I know most people prefer not to install additonl appliations...
EDIT: I believe my launcher pro FCs INDEPENDENT of this script (ie it happens whether or not the script is installed) Also, Launcher Pro works, just FCs once on boot, then works like a charm the rest of the time
Sent from my SPH-D700 using XDA App

The flashable zip did not work. It flashed but did not successfully write anything usable to phone. However, the apk on the original posting worked great!

Yes, the APK I pulled from should work UNTIL you upgrade to gingerbread (correct me if I'm wrong). Did you happen to try the script manager trick? Sometimes the script won't run on boot on its own (particularly if you have a stock kernetl). This will probably be of more use to GB users who really require the boot script.

Ran the script, but the file is not in the init.d directory.....
In root explorer, navigate to /system/etc/init.d, tap on 01-fixflash.sh and select “execute”.

tazman19 said:
Ran the script, but the file is not in the init.d directory.....
In root explorer, navigate to /system/etc/init.d, tap on 01-fixflash.sh and select “execute”.
Click to expand...
Click to collapse
There will only be 1 file in /system/etc/init.d, 01-fixflash.sh. It copies files from /data/flash to /data/data/com.adobe.flashplayer/lib/. When you execute it, then visit Hulu In dolphin, set to desktop it still doesn't work?
Are you saying the 01-fixflash.sh doesn't exist? Or that's the only file you see in there. Also note you must install flash from the market first. It should Always work when being run by hand. How about running the script, choosing execute, then the hulu app? Sorry, trying to figure out what the issue is.
Also, I'm on EF02 odex (stock), ef02 plus kernel, cwm 3.1.0.1. U same?

compuw22c said:
There will only be 1 file in /system/etc/init.d, 01-fixflash.sh. It copies files from /data/flash to /data/data/com.adobe.flashplayer/lib/. When you execute it, then visit Hulu In dolphin, set to desktop it still doesn't work?
Are you saying the 01-fixflash.sh doesn't exist? Or that's the only file you see in there. Also note you must install flash from the market first. It should Always work when being run by hand. How about running the script, choosing execute, then the hulu app? Sorry, trying to figure out what the issue is.
Also, I'm on EF02 odex (stock), ef02 plus kernel, cwm 3.1.0.1. U same?
Click to expand...
Click to collapse
Same as your setup, can't get it to work, still getting unsupported device message on hulu.com. The apk won't work for me either since it wants to find com.adobe.flash (or whatever it's called), and the one that exists on my phone has number "1" attached at the end. And I do have the latest flash, I just installed it for this very reason.
One question though, the stock browser doesn't seem to have an option to turn off mobile view?
EDIT: one difference I just noticed is that I'm deodexed, not odexed. I wouldn't think that would matter though...
Sent from my SPH-D700 using XDA Premium App

LoO
squshy 7 said:
Same as your setup, can't get it to work, still getting unsupported device message on hulu.com. The apk won't work for me either since it wants to find com.adobe.flash (or whatever it's called), and the one that exists on my phone has number "1" attached at the end. And I do have the latest flash, I just installed it for this very reason.
One question though, the stock browser doesn't seem to have an option to turn off mobile view?
EDIT: one difference I just noticed is that I'm deodexed, not odexed. I wouldn't think that would matter though...
Sent from my SPH-D700 using XDA Premium App
Click to expand...
Click to collapse
You could change the script if you can't find that file. So your libflashplayer.so file is located where, /data/data/com.adobe.flashplayer-1/lib ? Also are you on ef02 or ec05? Have you tried running the script via adb to see what errors it gives? You may need to run busybox installer from market to make sure the cp (copy) command itself works.
Edit: Also, I know there's an apk with -1 at the end, this is different. Its a folder with lib files in it. I may need to downgrade back to froyo to dbl check but I believe they're in the same place. Deodexed should't make any difference I don't think... thanks for hangin in there, I'd love to get this figured out so others can actually benefit from my aggrivation with it lol
And no, stock browser has no option to disable mobile view.
Sent from my SPH-D700 using XDA App

Updated to latest flash and fixed script file a bit* (gb only)
Sent from my SPH-D700 using XDA App

Just flashed. everything opens and runs. But when show loads it says not supported on this device... Ran the root explorer command and still the same. feels like I'm close. Any ideas? Running ef02 plus
Grapes

Kif420 said:
Just flashed. everything opens and runs. But when show loads it says not supported on this device... Ran the root explorer command and still the same. feels like I'm close. Any ideas? Running ef02 plus
Grapes
Click to expand...
Click to collapse
Double check /data/flash/ exists and has 4 files. Make sure you have installed flash 10.3.185.25 from market and uncheck auto updates. Install busy box installer, and run to install IF and only if it still isn't working at that point.

You are the man! Thought I had busy box installed but.... I didn't.... Installed, ran the script, bam! Hulu! big thanks compuw22c. I owe u a fatty!
Grapes

Thanks! It worked after I rebooted it. Hulu app and Hulu.com working (dolphin in desktop mode)

Awesome! Just glad to hear it finally working for people. I actually just got a gsII but will try to continue posting here as well as we all know the epic needs all the help it can get! btw this should work on any gingerbread its with root (which usually comes with init.d support)

After running this I have a Lego looking block with a ? in it like flash is not installed. Verified in my browser with other flash sites that this is the same. Any Idea as whats going on?

formula84 said:
After running this I have a Lego looking block with a ? in it like flash is not installed. Verified in my browser with other flash sites that this is the same. Any Idea as whats going on?
Click to expand...
Click to collapse
Never mind, it was because i use titanium backup to integrate system app updates into ROM, this saves space...
I had to restore an old backup of.24 then do the market update (did not integrate this time) booted into CWM and flashed worked great.
My only issue now is when i do fullscreen from hulu app its off center, half screen is just white (left) and part of the video is on the right?
Anyway to fix this or maybe an app update?

Its basically just a browser, tap and drag or pinch and zoom. Also, install Dolphin HD, set it to desktop user agent and tap full screen button as on a desktop.
Gone on vacation for two weeks*

I got this working on AA i3 with script manager.
It Does not make Hulu Plus app work.
It does play nicely in default web browser if you change the user agent to desktop. The full screen button works properly as well.
-Roger

[Q] Help Rooting 2.2.1 - I've tried that edition.

I, for the life of me, being a compute tech since the mid 90's, can't root this mytouch g3 slide. I have android 2.2.1 installed, I know I know, I hate it when people don't RTFM, I have tried the following:
(USB Deugging is on, charge mode only when plugged in, full android SDK kit installed and working. PDAnet drivers installed, I have superoneclick 1.9 computer see the phone fine, Goldcard works perfectly.)
1. I've tried Cyanogenmod's instructions (wiki.cyanogenmod.com/wiki/TMobile_myTouch_Slide:_Full_Update_Guide)
-Nothing happens after 2nd to last command line of step 8
{
"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"
}
2. I have tried this "New way to downgrade from 2.2 to 2.1" (http://forum.xda-developers.com/showthread.php?t=1108316)
-4a. , It does not give me the option to "hit vol up to update"esrpimg" just flashes error no image found error messages:
3/ I have tried ULTRA EASY ROOTER (http://forum.xda-developers.com/showthread.php?t=999121)
same problem as #2's problem, just error messages.
4. And I have tried this: "How-To [Root][NewLinks] The myTouch 3GS if you updated to Offical 2.2.1 and lost root" (http://forum.xda-developers.com/showthread.php?t=1025336)
-Everything goes smooth until I type in this line "chmod 04755 *" which I get a bank carraige return, and I can type to my hearts content, nothing happens, can't exit, etc, have to CRTL + C to get out out of it. similar problem as #1's problem. I have tried again and again and again.
Help.

Make a goldcard and install the img from the bootloader.
Then try again.
sent from my MT3GS running CM7 nightly

thanks for the reply poormanq45. I did make a goldcard, maybe it doesn't like my MicroSD card? Which image do you want me to install from the bootloader? Which instructions should I be following?
Which set of instructions talk about having a swap partition as your 3rd partition on the SD card?
poormanq45 said:
Make a goldcard and install the img from the bootloader.
Then try again.
sent from my MT3GS running CM7 nightly
Click to expand...
Click to collapse

I don't remember which img I used. IIRC there are three different ones. Just try each one until one works.
It's possible that your MicroSD card isn't capable of being a goldcard. I had to try two different ones
sent from my MT3GS running CM7 nightly

My Stock 2.2.1 Process
My warranty replacement came with stock 2.2 and all of the tutorials here and elsewhere fell short. I did notice a lot of the other guides were based on "if you upgraded to 2.2"; that did not completely apply in my situation. I to am an industry professional with 14 years experience and am a stickler for detail. I had the gold card created on a SanDisk 2gb micro sd acquired from Walgreen's. I had followed all the steps in order, but the update on the first reboot never happened, it never asked and selecting the update.zip failed signature verification. I knew S-ON was set (which is the whole problem) but the guides I saw to disable it required you already be rooted (which I wasn't).
This past week I did something different. Using the official HTC MyTouch 3G Slide Froyo installer (not selecting anything just having RUU opened) I copied the folder structure (a crazy GUID looking thing) that was in my %TEMP% directory to another location. I closed out of the installer and went to that copied folder. I moved the existing "rom" file and copied the 2.1 "ESPRIMG" image there and renamed it to rom.zip. I then executed the RUU from that folder. It being an HTC official rom did allow the RUU to complete and the slide was officially downgraded to 2.1. After the reboot I verified the ROM was the older version and went ahead with what I was used to.
After that; some of my previous attempts to root were evident because I already had the "#" prompt in the adb shell. Regardless, I did repeat some of the documented steps (just in case my eyes deceived me) from the exploid method (what I used on my previous phone that was an original build). I originally flashed the CM 7.03 while the goldcard (2gb) sd was still in there. I then installed my 32GB card, then hit a nightly, then hit a few more older CM builds (had issues with sd-ext, couldn't find the original guide i used to set it up - new card as well). I did format boot, data, system, sd-ext, and the cache from the clockworkmod recovery screen before settling on CM 7.1 RC 1
If you find it necessary to create the sd-ext partition, format the fat partition in windows, format the other two in the shell. I do not recommend logging (app sync) on the first rom. Build the sd-ext first; re-rom, before doing all the account/app setup. While the phone is USB debugging mode you can use DriodExplorer to shortcut some things (especially if u have all your apks in a backup folder on your computer). I do not recommend using certain busy-box commands from the DriodExplorer terminal. The output can be out of sync at times. I have a 32gb SD and have about 29.3G on FAT, 896MB on SD-EXT (ext3 file system), and the rest on cache. After that Simple2Ext will allow for you to tell CM7 to use the SD-EXT. I do not use .android secure (the froyo apps2sd) because that causes issues when using the fat partition as disk in windows and you have something like a theme installed. Because of themes, games, and other apps I am now using 62% of the sd-ext partition. And an earlier comment I saw on the thread is right. The partition order is FAT, SD-EXT, CACHE. Where the guide is I don't recall.
Also note: If you are doing ADB commands and notice it often says the process is stale; uninstall the HTC sync (this does not affect the drivers, drivers are installed as a pre-req before HTC Sync is installed).
My only outstanding issue is the radio version might have been affected; it's not showing a version number on my info app. So I need to find a guide on verifying/upgrading the radio (one that does not involve installing the htc froyo rom).

Stuck... help.
First of all, sorry I can't past in links to the images, because I need a minimum of eight posts.
-----
Okay, I have made sure my phone has 25MB free. (it told me I needed this)
I have Turn USB Debugging on.
The phone is set to charge mode only.
The phone is plugged in and drivers installed. PDANet is not running.
I've tried it with a goldcard in it and out of it.
tagr.org/ScreenShot084.jpg
I Downloaded "T-Mobile_myTouch_3G_Slide_Software_Update_2.15.531.3.exe" from here the website, (I can't post the links)
I ran setup, and left it open while I went to the temp folder and copied it all out to another location.
I went to the NEW location and deleted "rom.zip" and replaced it with the 140 MB "ESPRIMG.zip" into that folder and renamed it rom.zip
In the new folder, I ran "ARUWizard.exe", agree, agree, okay, etc.
All goes okay, I get to this screen:
tagr.org/ScreenShot091.jpg
I say next, About two minutes into it, the phone reboots, put the HTC logo on it. Then on the computer, I get to this screen:
tagr.org/ScreenShot089.jpg
The phone is stuck on the "HTC" logo when the USB is plugged in. When USB is unplugged, the screen turns to this:
tagr.org/ScreenShot090.jpg
Stuck meaning, can't reboot, turn off, etc. So I have to pull the battery. When it turns on, all seems okay, it's still at 2.2.1 though.
Thoughts?

What the... why could I post pics my first post, but not my third...new policy?
eckre said:
First of all, sorry I can't past in links to the images, because I need a minimum of eight posts.
Click to expand...
Click to collapse

Okay I've figured it out and wrote up a NEW Guide: http://forum.xda-developers.com/showthread.php?t=1189485
No goldcard is needed, no console typing ADB shell etc. blah blah blah, so easy now.

My adventures with my ZenWatch over the weekend

I spent a lot of the weekend trying to root my Zenwatch (on 4.4.2w), or get a custom recovery working. Here's what I have tried and found out so far. They locked it down pretty damn well.
Unlocking bootloader and accessing recovery
Go to Settings -> About -> Press Build Number 7 times -> Swipe right, Developer Options now shows under About.
Theres a few different options including an Asus utility to check sensors and such.
To get into recovery or fastboot, you need to active ADB Debugging, unplug the watch than plug it back in, then run "adb reboot recovery" or "adb reboot fastboot"
To unlock bootloader, you need to push the reset button on the back to select.
In recovery, swipe right to left to show screen, up and down to select, and left to right to select.
My Findings so far
The kernel source and ROM source are not available anywhere.
There is no way that I can find to get root. I even went as far as loading towelroot onto the watch through adb install, but it just hangs and eventually closes.
There is no way I have found to build a custom recovery with CWM or TWRP.
There is no way I have found to dump the boot or recovery partitions.
There is no su binary preinstalled. Attempting to link a su binary has come up null.
dump_image binary is not installed, nor can you get it to install.
Trying to install any packages through stock recovery gives signature error.
Trying to use dd command to dump boot or recovery ends with "permission denied"
Trying to use "fastboot oem saveprt2sd recovery -n recovery.img -a" ends with "invalid page size". Same with trying to dump boot in this fashion.
Trying to boot either the LG G Watch or Samsung Gear Live unsecured boot images comes back with "(remote) dtb not found" (No surprise here, but it was worth a shot)
fstab is root only.
/dev tree is root only.
all init.asus scripts are root only.
You can install packages with "adb install" but all the standard root gaining apps stall or force close. Towelroot seems to try, but locks up after hitting "make it r4in." trying to change the modstring on v3 (with triple tap title) does not provide a field to change.
Kernel command line is root only.
I browsed EVERY file on my watch hoping to find a hole that I could build off of, but alas, I had failed.
Even trying to do "adb backup" results in "Confirm on Device," and closes immediately afterwards, with no confirm.
I believe that unless they release either the kernel source or the full ROM source, we are unable to root or modify any options.
Which really sucks, because the "OK Google" screen is REALLY F****** BRIGHT.
if anyone has success, please share

I thought I'd try installing one of my own apps and see what happened. It installs okay, but it crashes immediately. I'm guessing it's because I'm using something that's not supported, probably sound or Webkit (the app displays an HTML tutorial the first time it's run). I haven't had time yet to run it from the debugger and see what's going wrong.

I haven't bothered to even watch the video yet but presumably this shows how to root Wear devices and includes links to a Wear compatible supersu, although no custom recovery for the Zenwatch yet. There are links to TWRP for other major watches so I'm guessing it's just a matter of time.
http://www.xda-developers.com/android/root-android-wear-5-0-1-xdatv/

dgjenkins said:
I haven't bothered to even watch the video yet but presumably this shows how to root Wear devices and includes links to a Wear compatible supersu, although no custom recovery for the Zenwatch yet. There are links to TWRP for other major watches so I'm guessing it's just a matter of time.
http://www.xda-developers.com/android/root-android-wear-5-0-1-xdatv/
Click to expand...
Click to collapse
To build a custom recovery, you need to pull the existing recovery or boot partition off of the device and pull partition information (fstab, which is not readable by user on this device) and the build.config information (which is also not readable by user), or pull the fstab.anithias and build.config from the running system (which again is not accessible to the standard user account).
Without that information, you can't build a custom recovery. I've been attempt this for almost 2 weeks now, and its locked down pretty well. The G Watch and Gear Live allowed access to the needed files, but Asus did not with the ZenWatch.
If anyone is willing to risk bricking their watch (by getting past the dtb error when trying to boot the LG G Watch or Samsung Live recovery images, which is a long shot in itself) to get the openRecovery/CWM/TWRP to install and work to the point of getting ADB working through recovery mode, I can do the rest to build the recovery.
I just dont want to risk bricking mine quite yet, as the google play store was out of stock the last time I checked to purchase a "testing" watch.

@z3nful - I just found this. Is it useful?
http://dlcdnet.asus.com/pub/ASUS/Wearable/ASUS_ZenWatch/kernel_3_13_0_10.zip

CSX321 said:
@z3nful - I just found this. Is it useful?
http://dlcdnet.asus.com/pub/ASUS/Wearable/ASUS_ZenWatch/kernel_3_13_0_10.zip
Click to expand...
Click to collapse
Kernel source code
Sent from my SM-G900P

@z3nful And an ota? Would it be usefull?
OTA LWX48S

I haven't had a chance the last week to work on this with the holiday season going on and having to run my store. When I get a chance to get back to it, I'll let you guys know what I come up with

I started trying to build the kernel yesterday, but I'm not getting far yet. I've been a developer for over 30 years, but most of my Linux/other UNIX experience was over 10 years ago, and I've forgotten a lot.
I've tried a couple of different compiler versions, but I'm pretty quickly running into different issues with either one. I'm not sure what version Asus used, but it's apparently not either of the ones I've tried. Also not entirely sure what configuration to use. I'm using the 8226 configuration now, because there's no 8026 configuration in the source archive. I don't know if that's suitable or not.
All-in-all, I may not be out of my depth, but I'm out of my area of experience, at least. Any tips, @z3nful?
Edit...Is there any useful information in the OTA zip file? It's available. Partition info or a boot image or something?

@z3nful and @CSX321 - Any luck moving forward on this? I'm not a programmer, but I'd be glad to offer any assistance if needed!

btonetbone said:
Any luck moving forward on this?
Click to expand...
Click to collapse
No progress here, I'm afraid. I think I just don't know enough about this environment to do it, without devoting a lot more time to learning.
I've also lost some motivation, because there doesn't really seem to be anything I need root for on the watch. About the only thing I would do if I had it is delete a couple of apps, but since Mini Launcher lets me hide apps, I don't care so much about actually deleting them.

Has anyone had success with adb push? It seems the system is read only and doesn't allow for pushing files. Is root required?

Asus is good at locking down their devices, requiring you to register it with them to get an app to unlock it (you also acknowledge that by downloading the app you are voiding your warranty). I really wouldn't be surprised if they did the same thing with this watch and just haven't released the unlock app yet.
I am kinda disappointed to see this sort of thing from a device licensed by Google. It's like the exact opposite of the Nexus line.

@z3nful Just some helpful links, thought I could help a wear user out (I have the G Watch)
Kernel --> https://android.googlesource.com/kernel/msm/+/android-msm-anthias-3.10-lollipop-wear-release
Also, Gohma ROM for gwatch includes a boot img that auto roots android wear. (http://forum.xda-developers.com/g-watch/development/rom-gohma-2-0-12-15-2014-t2974052) Named rboot.img, I think it might be worth a shot to run "fastboot boot rboot.img" to see if it does anything.

Has anybody been brave enough to try booting rboot.IMG like frap129 suggested?
-Andy
Sent from my Etch a Sketch.

I tried, no luck.. Gave the same "dtb not found" error.
Here is a thread related to DTB in boot images: XDA Topic 2428117
Attached is the rboot.img if anyone wants to see if they can modify it to pass whatever DTB issue is making it fail, if that's even possible. I will dig a little bit deeper once I get out of the office.
The error message:
{
"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"
}
rboot.img, zipped:
View attachment rboot.zip
Ignore my sig, it is several years out of date
Regards,
weasel5i2
Doc Ames said:
Has anybody been brave enough to try booting rboot.IMG like frap129 suggested?
-Andy
Sent from my Etch a Sketch.
Click to expand...
Click to collapse

TMobile GPad F 8.0 (V496) Info

For those that picked up a TMobile GPad F 8.0 recently, here's a good thread to ask questions until we either get a separate forum or get enough info to move over to the General.
Root
Kingroot works well following the instructions here: All you need for LG GPad 8.0 [LG v490] thread. Once rooted, replace it with SuperSu using this method.
It is best to use KingRoot 4.1 or earlier to root, replacing it as soon as possible. 4.5 is very difficult to uninstall, although you can purchase SuperSUMe on Google Play to attempt it.
OS
Stock OS is the only option at the moment. There is a system update available which fixes the stagefright bug. It can still be rooted.
Recovery
Thanks to @Rashed97 and @KAsp3rd a beta TWRP is available here. This is not a zip, so use Flashify, TWRP Manager or equivalent to flash zips. Hooking up a USB mouse also works well for in-recovery navigation.
Kernel
Similar to LG stock ROM on their phones, the kernel has some adjustable features accessible through Kernel Aduitor or Trickster.
Xposed
Xposed installs and runs well. G3TweakBox has the ability to adjust some extra settings.

ADB driver
I got one as part of the Father's Day promotion as I needed to upgrade my mobile internet hotspot. I would like to migrate from a Nexus 7 2013 and needed the ADB driver for restore using Helium. Has anyone come across a working ADB driver for this GPad?

I was able to root with Kingroot 4.1 and then replace Kinguser and su binaries to SuperSU using this method:
http://forum.xda-developers.com/showpost.php?p=60669196&postcount=1&nocache=1&z=4065499287098646
---------- Post added at 11:45 AM ---------- Previous post was at 11:39 AM ----------
These are the USB drivers I used . Got them from this thread: http://forum.xda-developers.com/lg-g3/general/guide-root-lg-firmwares-kitkat-lollipop-t3056951

nicknc said:
Anyone else had performance issues without rooting?
Click to expand...
Click to collapse
There are performance issues without root as well.

FYI I just unlocked this tablet. Doesn't give 4G LTE on AT&T though, only HSPDA+
To Unlock this model, access the Hidden Menu:
1) From Home screen,Touch the “ Contact”
2) Touch the “ Search Contact
3) You can see the “Keyboard” after Touch the “ Search Contact”
4) Touch the “＋ “ icon after Dialer 2945#*496#
5) Touch Network Lock, you only have 3 attempts to enter the correct Unlock Code which you can get from any online vendors.
6) Press Unlock

Rooted with Kingroot & replaced it with SuperSu using this script. No computer required just make sure you have Terminal Emulator installed!
Download the file attached and extract it
Put the mrw folder on the root of the sd card
Open Terminal Emulator and type:
Code:
su
grant terminal emulator root access
Next type:
Code:
sh /sdcard/mrw/root.sh
The script should then run and work it's magic. After it's completed SuperSU should open up and prompt you to update the binaries. Update the "Normal" way and reboot afterwards.
And that's it! :good:

Post 1000, hooray.
VRAM seems to be on by default and is eating up about 256K according to Kernel Aduitor. Disabling that helped performance some after I did a factory reset. The LTE radio is stronger than my G3, but that might just be a longer antenna.

the 'replace kingroot...' script didn't work for me. Anybody having issues with root not working after reboot? i have to re-root with kingroot every time. going to try the adb method now

sinshiva said:
the 'replace kingroot...' script didn't work for me. Anybody having issues with root not working after reboot? i have to re-root with kingroot every time. going to try the adb method now
Click to expand...
Click to collapse
Which KingRoot version did you use?

nicknc said:
Which KingRoot version did you use?
Click to expand...
Click to collapse
KingRoot-4.1.0.524.apk
[edit/]
I think they must have updated something on their end because now the same kingroot apk is working - root correctly persisting across reboots

You Are The Man {Works Like A Charm}
xoxo_xdagirl91 said:
Rooted with Kingroot & replaced it with SuperSu using this script. No computer required just make sure you have Terminal Emulator installed!
Download the file attached and extract it
Put the mrw folder on the root of the sd card
Open Terminal Emulator and type:
Code:
su
grant terminal emulator root access
Next type:
Code:
sh /sdcard/mrw/root.sh
The script should then run and work it's magic. After it's completed SuperSU should open up and prompt you to update the binaries. Update the "Normal" way and reboot afterwards.
And that's it! :good:
Click to expand...
Click to collapse
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I followed your instructions to the "T"! Your method for rooting with Kingsroot 4.1 English version, and replaced it with SuperSu
works like a charm! My suggestion to everybody, do everything in the internal storage area! Don't use your external SD Card using the above instructions! I'm making phone calls on this baby to via WiFi and LTE, sweet!

now just need to get roms
kinda makes me want to try and make my own.. I've never developed before. lol!

Which custom recovery we use?

Rican2008 said:
Which custom recovery we use?
Click to expand...
Click to collapse
Nothing out there yet that I've seen. It'll come-- the v500 has had TWRP for about 9 months now. This one has only been out a couple of weeks.

Rican2008 said:
Which custom recovery we use?
Click to expand...
Click to collapse
I got a CM recovery to build using the stock kernel source from LG, but I'm super hesitant to flash it, until I can verify the LG Updater software works for me. I don't have a Windows box ATM, so it'll take a bit more effort. I'll post here with results once I'm willing to flash.

Now that we have the root, has anyone tried to adjust the color of a panel? It is way too warm compared to my other devices (viewing my DSLR pics almost makes me think thr wirte balance was off).

northantara said:
I got a CM recovery to build using the stock kernel source from LG, but I'm super hesitant to flash it, until I can verify the LG Updater software works for me. I don't have a Windows box ATM, so it'll take a bit more effort. I'll post here with results once I'm willing to flash.
Click to expand...
Click to collapse
Well, I flashed it, and things went, err, poorly. I'm done trying. Turns out, it's not actually possible to recover from download mode with LGMobile Support Tool, at least until an update is made available online.

Thanks for trying. I assume the bootloader is locked on this too, meaning we will need to bump any flashable zips anyway.

The step to replace KingRoot with Supersu failed half way for me. Apparently there's a typo in the script >.< Now KingRoot thinks that the tablet is rooted even though it isn't... stuck with broken root...

That is not good news, if this baby has a locked boot loader I am taking it back. Left AT&T for locking the boot loaders of their devices.

Busybox fails to install

Accidentally installed the wrong busy box apk but cleared data and uninstalled then i tried installing the correct version of stericson busybox free and I'm greeted by this message
"There was a problem opening a shell with root access. this is either cause by supersu or by a device that is improperly rooted..."
It then goes on to say i should change permissions in supersu then reinstall. Of course I can't do this because our supersu does not have a settings menu.
I'm looking for help. Is there a way to resolve this over adb and change the su settings? Or can i reinstall supersu?--would that give me the popup i need to grant permissions (if that is in fact the issue...)
I'm not certain i can just run towel root again and reinstall supersu. I have the latest prerooted firmware installed.
BTW--I'm curious as to what happened. thinking the wrong busy box app is still causing issues because i did the same thing on my other fire tv and could easily install busy box again. Thanks.

You should be able to open the settingsmenu (or the apps list) of SuperSU in the FireTV system settings menu -> installed apps tab. Just start the SuperSU app for that.

Calibaan said:
You should be able to open the settingsmenu (or the apps list) of SuperSU in the FireTV system settings menu -> installed apps tab. Just start the SuperSU app for that.
Click to expand...
Click to collapse
Unless I'm misunderstanding, you can't do that with our supersu (think its just the way rbox designed it that supersu can't be opened). Go to applications and try it. I assume your setup is the same as mine--cwm & and prerooted firmware.
I'm thinking I'll just uninstall/reinstall supersu, but not even sure that will resolve the busybox issue.

No, I have not a rooted aTV (those for the german market were never deliverered with a rootable firmware, hope this changes with stagefright vulnaribilty). I assumed you´re running the regular SuperSU from Chainfire which does acts as a Superuser access management tool:
{
"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"
}
It should be possible to call this superuser app from the apps tab within the system menu like every other sideloaded app. Of course when you´re running another supersu app this probably won´t work.

Calibaan said:
No, I have not a rooted aTV (those for the german market were never deliverered with a rootable firmware, hope this changes with stagefright vulnaribilty). I assumed you´re running the regular SuperSU from Chainfire which does acts as a Superuser access management tool:
It should be possible to call this superuser app from the apps tab within the system menu like every other sideloaded app. Of course when you´re running another supersu app this probably won´t work.
Click to expand...
Click to collapse
Thanks. I have read in other thread people talking about using superuser app to access those settings we can't get with supersu on AFTV. That was a long time ago and don't think there was much feedback on how it worked.
I messed things up more than I thought. None of my root apps are working (ROM manager, titanium backup, samba file sharing, etc.
Wondering if just reinstalling the ROM.zip will fix everything? Only thing about that is it doesn't ask to regrant su for my installed apps normally. Not sure if it'll be different because root isn't functioning properly...

So maybe someone can confirm this? If I wipe factory reset in cwm will supersu reinstall and reset su settings? (Actually pretty sure it will) But really rather not do that because I'm forward thinking enough to install titanium backup but not smart enough to backup apps and data (always put it off then forgot) Now of course I can't use titanium.
So if that's my only option I'll do it but hoping there's a simpler way like flashing supersu zip in recovery. AND if that's an option should I first remove supersu apk in system/app?

I've had issues with the Busybox installer, too. It claims you can begin installing right away, but it's a good idea to wait until it finishes its scan to do the install.

Sizzlechest said:
I've had issues with the Busybox installer, too. It claims you can begin installing right away, but it's a good idea to wait until it finishes its scan to do the install.
Click to expand...
Click to collapse
Well I didn't actually want busybox installer. I wanted busybox free by stericson. I'm not even sure if the installer is by stericson. So did you try to run that installer program again and let it complete? Or were you actually talking about busybox free which is what I've always used on AFTV (its the recomended version we all are probably using). But not paying attention I installed the wrong apk. Now none of my root apps work which I don't understand. Busybox having trouble makes sense but pretty sure I've run other root apps without busybox in the past.
Its looking like I need to wipe it but not in a huge hurry. The AFTV functions OK without root so I'll hang around for a better solution.

KLit75 said:
Well I didn't actually want busybox installer. I wanted busybox free by stericson. I'm not even sure if the installer is by stericson. So did you try to run that installer program again and let it complete? Or were you actually talking about busybox free which is what I've always used on AFTV (its the recomended version we all are probably using). But not paying attention I installed the wrong apk. Now none of my root apps work which I don't understand. Busybox having trouble makes sense but pretty sure I've run other root apps without busybox in the past.
Its looking like I need to wipe it but not in a huge hurry. The AFTV functions OK without root so I'll hang around for a better solution.
Click to expand...
Click to collapse
This is what I was referring to: https://play.google.com/store/apps/details?id=stericson.busybox&hl=en
Can you connect to your Fire TV using adb and do a "su" command to see if you get root? Did you fully unlock your bootloader?

Sizzlechest said:
This is what I was referring to: https://play.google.com/store/apps/details?id=stericson.busybox&hl=en
Can you connect to your Fire TV using adb and do a "su" command to see if you get root? Did you fully unlock your bootloader?
Click to expand...
Click to collapse
That's the one that won't install. Yes. I can connect adb, reboot recovery and bootloader fully unlocked. I can't access everything in es file explorer because the root explorer option won't work without su permissions. But adb shell will get the # sign.