If anyone wants to develop the program further, I have made it publicly available here.
https://github.com/rainman74/FireTV-Settings/releases
I hereby discontinue support for my Fire TV Guides and Apps. I've been a big fan of Fire TV devices for the last 2-3 years, but Amazon has now with each firmware further limited the possibilities of a configurable Android environment and even destroyed standard Android commands. This goes too far for me now.
I can recommend the following devices to anyone who wants to have a reasonable and much better Android TV experience, which I now use myself and am enthusiastic about:
Mi Box
Mi Box S
Sony Android TV (ATV3 platform, eg. XF7, XF8, XF9 or higher)
Awesome, thanks for sharing this! Will be using this on my ‘Playing With Fire’ Leanback Launcher configuration!
Are there any activities missing that could still be included in the conFIREator?
Ideas?
@rainman74
can you add this function:
-Restart Device
-ADB Debugging
-USB Debugging
-Apps from Unknown Sources
-Network Info (to look ip address from device)
-System Info (to look Software version from device)
droidpaine said:
@rainman74
can you add this function:
-Restart Device
-ADB Debugging
-USB Debugging
-Apps from Unknown Sources
-Network Info (to look ip address from device)
-System Info (to look Software version from device)
Click to expand...
Click to collapse
Thanks for the ideas. But this is not only possible with activities, you need a modified settings app for these commands (except for restarting, you need root privileges for this, or a corresponding authorized app).
Okay, let's see:
Restart Device -> Simple Reboot
turn on ADB/USB -> you have to install modified settings app from PlayFire as system app
Network Info (to look ip address from device) -> you have to install modified settings app from PlayFire as system app
System Info (to look Software version from device) -> you have to install modified settings app from PlayFire as system app
turn on unknown sources -> you have to install modified settings app from PlayFire as system app
ok thanks for the explanation
restart with the app works
rainman74 said:
Thanks for the ideas. But this is not only possible with activities, you need a modified settings app for these commands (except for restarting, you need root privileges for this, or a corresponding authorized app).
Okay, let's see:
Restart Device -> Simple Reboot
turn on ADB/USB -> you have to install modified settings app from PlayFire as system app
Network Info (to look ip address from device) -> you have to install modified settings app from PlayFire as system app
System Info (to look Software version from device) -> you have to install modified settings app from PlayFire as system app
turn on unknown sources -> you have to install modified settings app from PlayFire as system app
Click to expand...
Click to collapse
Is there a tutorial on how to install an app as a system app? Or can you point me in the right direction.
BRICK0044 said:
Is there a tutorial on how to install an app as a system app? Or can you point me in the right direction.
Click to expand...
Click to collapse
For this you need root rights!
First you have to download the modified Android TV Settings app from PlayFire:
View attachment TvSettings.apk
Then copy the app into the system app folder and MUST restart your Fire TV to install it automatically.
Code:
adb push C:\TvSettings.apk /sdcard/
adb shell su -c mount -o remount,rw /system
adb shell su -c mkdir /system/priv-app/TvSettings
adb shell su -c chmod 755 /system/priv-app/TvSettings
adb shell su -c cp /sdcard/TvSettings.apk /system/priv-app/TvSettings/TvSettings.apk
adb shell su -c chmod 644 /system/priv-app/TvSettings/TvSettings.apk
adb shell su -c chown root:root /system/priv-app/TvSettings/TvSettings.apk
adb shell su -c mount -o remount,ro /system
adb shell su -c rm /sdcard/TvSettings.apk
rainman74 said:
For this you need root rights!
First you have to download the modified Android TV Settings app from PlayFire:
View attachment 4475903
Then copy the app into the system app folder and MUST restart your Fire TV to install it automatically.
Code:
adb push C:\TvSettings.apk /sdcard/
adb shell su -c mount -o remount,rw /system
adb shell su -c mkdir /system/priv-app/TvSettings
adb shell su -c chmod 755 /system/priv-app/TvSettings
adb shell su -c cp /sdcard/TvSettings.apk /system/priv-app/TvSettings/TvSettings.apk
adb shell su -c chmod 644 /system/priv-app/TvSettings/TvSettings.apk
adb shell su -c chown root:root /system/priv-app/TvSettings/TvSettings.apk
adb shell su -c mount -o remount,ro /system
adb shell su -c rm /sdcard/TvSettings.apk
Click to expand...
Click to collapse
Thanks again worked great!
Updated app in first post (Access to SuperSU Settings)
Updated app in first post (Access to Xposed and VMLite VNC Server)
Also added Google Play Store, Android Terminal, Mouse Toogle and Reboot
Updated app in first post
If you use XInstaller, other basic Amazon activities can be called up (which are normally only possible with the Amazon TV Launcher) and I will include them in an upcoming version of conFIREator, e.g. screen and sound settings, sdcard menu, Fire TV info, etc.
This allows you to access all Amazon settings even if Amazon Launcher is disabled.
Updated app in first post with two versions: 1) possible settings without root and 2) really all settings with root & Xinstaller
New version added which removed access to notifications, because they no longer work with the Leanback Launcher.
If you still need it, please continue to use version 2.1.
All new version of Fire TV Settings
@rainman74 hello, first of all thank you for your work. i have an fire tv stick 2nd using halauncher and amazon launcher removed. no root. i want to acces display&sound is it posibile ? i want the overscan option. thks
xhostluv said:
@rainman74 hello, first of all thank you for your work. i have an fire tv stick 2nd using halauncher and amazon launcher removed. no root. i want to acces display&sound is it posibile ? i want the overscan option. thks
Click to expand...
Click to collapse
No that's not possible, you need root privileges and Xposed/XInstaller and you can't get them on a Fire TV Stick 2.
rainman74 said:
No that's not possible, you need root privileges and Xposed/XInstaller and you can't get them on a Fire TV Stick 2.
Click to expand...
Click to collapse
Did you use the Magisk xposed or the standalone xposed. I understand everything has to be flashed in twrp. thanks
Related
Get superuser whitelist. I pulled mine off a rooted Galaxy Tab:
Code:
linux$ adb pull /system/app/Superuser.apk
linux$ adb pull /system/bin/su
From a machine with ADB working, and communicating with your Nook:
Install Superuser.apk, and copy the su binary to /data/local:
Code:
linux$ adb install Superuser.apk
linux$ adb push su /data/local/
Shell into the Nook, remount the system partition read/write, and install the su utility to /system/bin:
Code:
linux$ adb shell
# cd /system/bin
# mount -o remount,rw /dev/block/mmcblk0p5 /system
# cat /data/local/su > su
# chmod 6755 su
# ls -l su
-rwsr-sr-x root root 26264 2010-12-01 10:27 su
#
reboot Nook Color to get Superuser to show up in "extras." Now, you can get root from inside the Better Terminal Emulator Pro shell.
Thanks for the info. Just a quick note that on Cyanogenmod 6.1 RC2 (Nexus One), the su binary is actualy at /system/xbin/su rather than /system/bin/su
hharte said:
Get superuser whitelist. I pulled mine off a rooted Galaxy Tab:
Code:
linux$ adb pull /system/app/Superuser.apk
linux$ adb pull /system/bin/su
From a machine with ADB working, and communicating with your Nook:
Install Superuser.apk, and copy the su binary to /data/local:
Code:
linux$ adb install Superuser.apk
linux$ adb push su /data/local/
Shell into the Nook, remount the system partition read/write, and install the su utility to /system/bin:
Code:
linux$ adb shell
# cd /system/bin
# mount -o remount,rw /dev/block/mmcblk0p5 /system
# cat /data/local/su > su
# chmod 6755 su
# ls -l su
-rwsr-sr-x root root 26264 2010-12-01 10:27 su
#
reboot Nook Color to get Superuser to show up in "extras." Now, you can get root from inside the Better Terminal Emulator Pro shell.
Click to expand...
Click to collapse
Thank you, very useful instruction!
Couple of questions though:
1. Any public repo where the working in NC Superuser.apk could be downloaded from? Not everyone out of NC owners owns Galaxy Tab.
2. More elaboration on "whitelist", please
3. If possible, show some example why someone might need this. I'd rather try to edit build.prop: pixel density, whatever, plus changing stock system Droid Sans into, say, much more beautifil Segoe WP. But it's just me though.
Thank you
aludal said:
Thank you, very useful instruction!
Couple of questions though:
1. Any public repo where the working in NC Superuser.apk could be downloaded from? Not everyone out of NC owners owns Galaxy Tab.
2. More elaboration on "whitelist", please
3. If possible, show some example why someone might need this. I'd rather try to edit build.prop: pixel density, whatever, plus changing stock system Droid Sans into, say, much more beautifil Segoe WP. But it's just me though.
Thank you
Click to expand...
Click to collapse
For #3, somebody may want to replace system fonts to support other languages than English. I have done that to Android 2.1 phones too.
aludal said:
Thank you, very useful instruction!
Couple of questions though:
1. Any public repo where the working in NC Superuser.apk could be downloaded from? Not everyone out of NC owners owns Galaxy Tab.
Thank you
Click to expand...
Click to collapse
Here you go: http://forum.xda-developers.com/showthread.php?t=665974
hharte said:
Get superuser whitelist. I pulled mine off a rooted Galaxy Tab:
linux$ adb pull /system/bin/su
Click to expand...
Click to collapse
Thanks Man, this was the part i didn't get and it's working now
PTzero said:
Here you go: http://forum.xda-developers.com/showthread.php?t=665974
Click to expand...
Click to collapse
So I installed this version of the Superuser apk but it seems to be an old version (2.0.3) with the ninja icon.
The latest version is 2.3.6.1 but I can't seem to get it to install (INSTALL_FAILED_UPDATE_INCOMPATIBLE).
Which is the latest version of Superuser apk that works with nC that has the 'Android Skull and Crossbones' icon and does anyone have the apk?
califrag said:
So I installed this version of the Superuser apk but it seems to be an old version (2.0.3) with the ninja icon.
The latest version is 2.3.6.1 but I can't seem to get it to install (INSTALL_FAILED_UPDATE_INCOMPATIBLE).
Which is the latest version of Superuser apk that works with nC that has the 'Android Skull and Crossbones' icon and does anyone have the apk?
Click to expand...
Click to collapse
That's odd. I was able to install 2.3.6.1 with no problem. I pulled it the apk off my Nexus One.
dark79 said:
That's odd. I was able to install 2.3.6.1 with no problem. I pulled it the apk off my Nexus One.
Click to expand...
Click to collapse
Could you pull and post your Superuser apk and your /system/bin/su file? I don't have a nexus one and when I tried using the Superuser apk and su file from the cyanogen 6.0 Nexus ROM it didn't seem to work either
EDIT:
Nevermind I got it working using the files attached (latest version 2.3.6.1)
(from here: http://forum.xda-developers.com/showthread.php?t=682828)
I also noticed that it had to grant itself Superuser permissions when I hit the "settings" tab. Under the settings tab I also noticed my 'su' version was 'original' and there was an update available which changed it to version '2.3.1-ef'. Not sure if this needs to be done for it to work right or not but thought I should mention it.
Will this work on just linux or windows?
You can do it on windows using ADB
califrag said:
Could you pull and post your Superuser apk and your /system/bin/su file? I don't have a nexus one and when I tried using the Superuser apk and su file from the cyanogen 6.0 Nexus ROM it didn't seem to work either
EDIT:
Nevermind I got it working using the files attached (latest version 2.3.6.1)
(from here: http://forum.xda-developers.com/showthread.php?t=682828)
I also noticed that it had to grant itself Superuser permissions when I hit the "settings" tab. Under the settings tab I also noticed my 'su' version was 'original' and there was an update available which changed it to version '2.3.1-ef'. Not sure if this needs to be done for it to work right or not but thought I should mention it.
Click to expand...
Click to collapse
What did you do to get this? I tried installing using ADB and Android Commander. I get the same error that says INCOMPATIBLE. This is the only program giving me issues.
sminker said:
What did you do to get this? I tried installing using ADB and Android Commander. I get the same error that says INCOMPATIBLE. This is the only program giving me issues.
Click to expand...
Click to collapse
Make sure to download the 'eclair\froyo' version.
this is the file im using
su-2.3.6.1-ef-signed
i did have it installed once and uninstalled, but now i cant reinstall it
sminker said:
this is the file im using
su-2.3.6.1-ef-signed
i did have it installed once and uninstalled, but now i cant reinstall it
Click to expand...
Click to collapse
use adb shell and go into /data/data and do an 'ls'
remove any directory there that looks like 'com.noshofou'
i was able to use z4root to get it installed
when I do:
cat /data/local/su > su
I get:
Cannot create su: remote access failed
Is there a Windows tutorial for how to install Super User on the NC or an apk that does the same thing?
Is there any advantage to put the binary into xbin versus bin
discourse said:
Is there a Windows tutorial for how to install Super User on the NC or an apk that does the same thing?
Click to expand...
Click to collapse
I would like a windows walkthrough also
UPDATE: See my other thread for a much easier solution that does all the hard work for you...
This assumes a factory fresh nook and a mac that hasn't previously been used. I just reset mine again (Hold Power until you get prompted, pick power off, then when it's off, press N and then turn it back on) and went through this. Works reliably.
On the NOOK
Browse to this:
http://www.launcherpro.com/apk/LauncherPro-0.8.6.apk
When it's done, click on notifications center
Press on downloaded apk file
Complete action using package installer
It should say "install blocked"
Press settings
Tick unknown sources (press ok)
Pick Development
Tick USB debugging (press ok)
Tick the other USB debugging further down
Uncheck Automount
Back/Back
On the MAC
Download Android SDK http://developer.android.com/sdk/index.html
Unzip it
Start a shell
Cd to the dir where you unzipped it
cd to tools directory
run ./android - android sdk manager launches
Tick Android SDK platform tools
Click install 6 packages - wait until it's all done. "done loading packages"
Open a new shell
See if there is .android directory in your home directory, if not "mkdir -p ~/.android" in your home directory
echo 0x2080 > ~/.android/adb_usb.ini
adb kill-server
Connect the Nook via MicroUSB to your Mac
The nook should show you notification saying usb debugging connected. If not something's wrong with the settings in the menu earlier
Download http://dl.dropbox.com/u/15069134/Nook&Zergy.zip
unzip that file
Adjust your PATH variable to include the directory containing the adb binary from the sdk, eg:
export PATH=$PATH:YOURDOWNLOADDIR/android-sdk-macosx/platform-tools/
Type which adb
This should show you the full path to the adb binary, if not your path is set wrong, assuming that is right
adb devices
You should see:
List of devices attached
[YOUR NOOKCOLOR SN] device
adb push zergrush /data/local/zergy
adb shell "chmod 755 /data/local/zergy;cd /data/local/;./zergy"
adb wait-for-device install Superuser.apk
adb remount
adb push su /data/local/tmp/
adb shell "cd /data/local/tmp;chmod 777 su;cd /;mount -o remount,rw -t rootfs rootfs /"
adb push su /system/bin/su
adb shell chmod 4755 /system/bin/su
Download http://goo-inside.me/gapps/gapps-gb-20110828-signed.zip
Unzip this file.
cd gapps-gb-20110828-signed/system/app/
rm SetupWizard.apk
adb push GoogleServicesFramework.apk /system/app
adb push Vending.apk /system/app
adb push CarHomeGoogle.apk /system/app
adb push FOTAKill.apk /system/app
adb push GenieWidget.apk /system/app
adb push GoogleBackupTransport.apk /system/app
adb push GoogleCalendarSyncAdapter.apk /system/app
adb push GoogleContactsSyncAdapter.apk /system/app
adb push GoogleFeedback.apk /system app
adb push GoogleFeedback.apk /system app
adb push GoogleFeedback.apk /system/app
adb push GooglePartnerSetup.apk /system/app
adb push GoogleQuickSearchBox.apk /system/app
adb push LatinImeTutorial.apk /system/app
adb push MarketUpdater.apk /system/app
adb push MediaUploader.apk /system/app
adb push NetworkLocation.apk /system/app
adb push Talk.apk /system/app
adb push OneTimeInitializer.apk /system/app
adb shell chmod 644 /system/app/*
Click on Notification center again, and press on the Golancher Icon again. Install the Goauncher
Reboot
After reboot, slide to unlock and it should ask "complete action using..". Pick LauncherPRO
Open Marketplace which should be on the launcher screen
Sign in with your google credentials, attach the device to your account
Install button savior from the Marketplace.
Browse to www.amazon.com/app-email
Click notifications and watch for Amazon appstore apk download
Click and install.
You should now be live with Android Market & Amazon Market.
My word I hope these kind of instructions get captured in a wiki somewhere...
Just what I was looking for, worked perfect first try. My frustrations are out the window, not my Nook Tablet!!!
Sweet. One person helped, my debt is repaid the community
Sweet Indeedie!
Thanks @t-r-i-c-k - you just helped yet another.
Note to others - I did have a problem getting my device listed with adb, I re-ran the tgps_launcher app for the debug settings and un-checked and re-checked USB Debugging lines (2 of them) and that seem to do it. I also re-plugged the USB cable a one point so that may have been part of the trick as well - not real sure. You may have to fiddle a bit.
EDIT: ok running tgps_launcher, it is the first USB Debugging checkbox to un-check then re-check.
---------- Post added at 05:48 AM ---------- Previous post was at 05:09 AM ----------
Ok, just had a bit of a scare after rooting...
I had left the NT in terminal, su'd to root and the display timed out. NOTHING would bring it back to life!! EXCEPT plugging in the USB cable and running 'adb devices' ... and it powered on!! Whew!!!!
(before this I held the power button for a good 30 seconds and tried a repower to no avail)
I tried to replicate but always got my unlock back on no matter what I did?!
Ok so here is where I am getting stuck.
t-r-i-c-k said:
See if there is .android directory in your home directory, if not "mkdir -p ~/.android" in your home directory
echo 0x2080 > ~/.android/adb_usb.ini
adb kill-server
Click to expand...
Click to collapse
I'm pasting the "mkdir -p ~/.android" command into the terminal and it doesn't seem to do anything. No such directory is created.
Perhaps I'm missing something. I'm not as used to using the terminal on my Mac as I am on Linux.
MonkeysInACan said:
Ok so here is where I am getting stuck.
I'm pasting the "mkdir -p ~/.android" command into the terminal and it doesn't seem to do anything. No such directory is created.
Perhaps I'm missing something. I'm not as used to using the terminal on my Mac as I am on Linux.
Click to expand...
Click to collapse
Nope - not the your Nook terminal - do it on your Mac
...assuming you are doing it on your mac...
if you use 'cd' (and [Enter] of course) and you'll be in your home folder ("~")
if mkdir returns an error then it probably already exists - try 'ls -a' and see if you see it.
if it exists then use the echo command again - there is no visible output - it used by adb
MonkeysInACan said:
Ok so here is where I am getting stuck.
I'm pasting the "mkdir -p ~/.android" command into the terminal and it doesn't seem to do anything. No such directory is created.
Perhaps I'm missing something. I'm not as used to using the terminal on my Mac as I am on Linux.
Click to expand...
Click to collapse
It makes a hidden directory in your home directory. ls -lart ~ to see it
Yay!!! It works!!!! It took a bit of tweaking, and a few extra steps (making sure all the directories were right) but it worked. Thanks a lot!
It all seemed to work really well except I got a force close on the google framework when I rebooted. Not sure if I should start from scratch or not. One thing I can't figure out how to do is erase apps that install from the market. Clicking settings brings up the Nook settings which doesn't have any record of the apps I installed via market.
Also, is there any way to enable USB debugging after the reboot? When I plugged in the usb cable again to try to repush the framework I just get usb storage.
Ok, I found a link to the app that lets me toggle USB debugging though I'm getting a permissions error when I try to push. Also figured out that I can uninstall apps through the market app itself.
Thanks very much for the instructions you've posted here.. very helpful!
viniosity said:
It all seemed to work really well except I got a force close on the google framework when I rebooted. Not sure if I should start from scratch or not. One thing I can't figure out how to do is erase apps that install from the market. Clicking settings brings up the Nook settings which doesn't have any record of the apps I installed via market.
Also, is there any way to enable USB debugging after the reboot? When I plugged in the usb cable again to try to repush the framework I just get usb storage.
Ok, I found a link to the app that lets me toggle USB debugging though I'm getting a permissions error when I try to push. Also figured out that I can uninstall apps through the market app itself.
Thanks very much for the instructions you've posted here.. very helpful!
Click to expand...
Click to collapse
I have seen that google services framework crash once too. I just ignored it and everything seems fine. I did notice at least one other person in the main thread who reported the same. I may wipe my device and try the process again, this time with another Launcher too. I also noticed the app store doesnt show everything either. Notably facebook seems missing. If you go right to it from a link you get a "this is not compatible with your device" at the top. Going to play around more after work. On the whole though, this is awesome!
Sent from my BNTV250 using Tapatalk
I've gotten to this spot:
adb devices
You should see:
List of devices attached
[YOUR NOOKCOLOR SN] device
I can see the serial number, but I can't get any farther. This is the error I get: cannot stat 'zergrush': No such file or directory
Any ideas people? I'm brand spanking new to terminal and commands and stuff like this. Thanks for your help.
beatlesfan01 said:
I've gotten to this spot:
adb devices
You should see:
List of devices attached
[YOUR NOOKCOLOR SN] device
I can see the serial number, but I can't get any farther. This is the error I get: cannot stat 'zergrush': No such file or directory
Any ideas people? I'm brand spanking new to terminal and commands and stuff like this. Thanks for your help.
Click to expand...
Click to collapse
You need to be in the directory where you unzipped the zip from dropbox . Do ls -l and you should see the zergrush file, su etc
Sent from my BNTV250 using Tapatalk
Ok I renamed the folder from dropbox "Nookroot" This is what I get. I'm copy pasting "adb push zergrush /data/local/zergy" from first post.
MYNAME-iMac-2:Nookroot emt1052$ ls -l
total 4048
-rwxr-xr-x 1 emt1052 staff 96256 Sep 20 2010 AdbWinApi.dll
-rwxr-xr-x 1 emt1052 staff 60928 Sep 20 2010 AdbWinUsbApi.dll
-rwxr-xr-x 1 emt1052 staff 4229 Nov 21 14:38 NookandZergy.bat
-rwxr-xr-x 1 emt1052 staff 843503 Feb 29 2008 Superuser.apk
-rwxr-xr-x 1 emt1052 staff 578611 Sep 20 2010 adb.exe
-rwxr-xr-x 1 emt1052 staff 413129 Nov 20 21:55 busyboxinstall.apk
-rwxr-xr-x 1 emt1052 staff 14175 Nov 20 13:52 debug.apk
-rwxr-xr-x 1 emt1052 staff 22228 Feb 29 2008 su
drwxr-xr-x 6 emt1052 staff 204 Nov 20 15:57 system
-rwxr-xr-x 1 emt1052 staff 23056 Nov 16 09:09 zergRush
MYNAME-iMac-2:Nookroot emt1052$ adb push zergrush /data/local/zergy
-bash: desktop/android-sdk-macosx/platform-tools/adb: No such file or directory
Sorry if I'm making some dumb mistake, and thanks for your help.
Try this
beatlesfan01 said:
...
MYNAME-iMac-2:Nookroot emt1052$ adb push zergrush /data/local/zergy
-bash: desktop/android-sdk-macosx/platform-tools/adb: No such file or directory
...
Click to expand...
Click to collapse
@beatlesfan01: I wonder if /data/local doesn't exist on your NT - or you don't have permissions...
maybe try (from your Mac shell)
Code:
mac-osx$ adb shell
$ ls /data/local
a) you should get the single '$ ' prompt after the adb cmd - this is the NT's shell
b) you should get no error from 'ls /data/local
If you get errors for /data/local, then try this (while still in the 'adb shell'):
Code:
$ mkdir /data/local
$ chmod 777 /data/local
If you get an error on the 'mkdir' do the 'chmod' anyway - actually the 'chmod ...' may be the only thing you need.
Then try stuff again.
I did the first part and got this:
MYNAME-iMac-2:~ emt1052$ adb shell
$ ls /data/local
tmp
$
beatlesfan01 said:
I did the first part and got this:
MYNAME-iMac-2:~ emt1052$ adb shell
$ ls /data/local
tmp
$
Click to expand...
Click to collapse
*** NOTE EDIT ***
Ok, try 'ls -l /data' and look for 'local'
the permissions should look like '-rwxrwxrwx' - if not try 'chmod 777 /data/local' and try your adb push cmd again.
Got this:
ls -l /data/local
drwxrwx--x shell shell 2011-11-21 16:06 tmp
$ chmod 777 /data/local
$ adb push zergrush /data/local/zergy
adb: permission denied
$
I DO appreciate your help with this.
Based on your last post - you are issuing the adb push command on the Nook.
It has to be issued on the Mac...
beatlesfan01 said:
Got this:
ls -l /data/local
drwxrwx--x shell shell 2011-11-21 16:06 tmp
$ chmod 777 /data/local
$ adb push zergrush /data/local/zergy
adb: permission denied
$
I DO appreciate your help with this.
Click to expand...
Click to collapse
Ok - weird. I did mis type and edited my previous post BUT the chmod should have looked after the permission issue anyway...
Try 'chmod 777 /data' - can you do that without an error - using the 'adb shell'?
EDIT: @rmm200 - thanks - I didn't notice that one
Just in case someone is
This page details how to root the Fujitsu Arrows TAB F-01D.
http://arrowstab-f01d.blogspot.com/2012/03/easy-rooting-toolkit-for-arrows-tab-f.html
it works.
Now if only somebody can post the firmware updates..
English instructions
Well, with some help from Google Translate and some creative interpretations, I managed to do this and thought I'd provide some English instructions for others (with some added comments)
DISCLAIMER: AS USUAL, YOU SHOULD KNOW THAT FOLLOWING THESE ACTIONS (AND ESPECIALLY FOLLOWING THEM INCORRECTLY) CAN BRICK YOUR DEVICE (I.E. YOUR DEVICE WILL STOP WORKING, POSSIBLY PERMANENTLY). I AM NOT RESPONSIBLE FOR ANY DAMAGES THAT MAY ARISE FROM YOU FOLLOWING THESE INSTRUCTIONS, YOU DO SO AT YOUR OWN RISK.
Downloads
1. Windows -- the Arrows TAB USB driver Download.
2. Easy rooting toolkit (ERT) for Arrows Tab F-01D (ver 1.0) Download
3. goroh_kun's lsm_disabler.ko Download
Info
4. A su binary, such as the one found in DooMLoRD_v3_ROOT-zergRush-busybox-su.zip
5. Android SDK platform tools. adb(.exe) (and in Windows, specifically: AdbWinApi.dll, AdbWinUsbApi.dll)
Preparation
1. Unzip ert4F01D.zip, and in the subdirectory 'files' place:
* adb.exe (Windows only, from step 4 above)
* AdbWinApi.dll (Windows only, from step 4 above)
* AdbWinUsbApi.dll (Windows only, from step 4 above)
* lsm_disabler.ko (from step 3 above)
* su (from step 5 above)
2. Before connecting the USB, in Settings -> Applications -> Development:
* Check (tick) USB debugging ("Debug mode when USB is connected")
* Check (tick) Stay awake ("Screen will never sleep while charging")
3. Set up the USB drivers and Android Development stuff if you haven't already. I don't use Windows so can't help with this.
The Dirty Work
At this stage, you can run the batch file. Since I don't use Windows, I did the steps by hand, so you'll have to correlate your actions appropriately (I can't read Japanese either, so your guess is as good as mine ).
1. On your PC:
adb shell "mv /data/local/calib.dat /data/local/calib.dat_"
adb shell "ln -s /data/local.prop /data/local/calib.dat"
2. On the tablet, go into Google Maps, touch the GPS icon ("locate me" icon) on the top right hand corner, and then touch the BACK key to exit.
3. On your PC:
adb shell "echo ro.kernel.qemu=1 > /data/local.prop"
adb shell "rm /data/local/calib.dat"
adb shell "mv /data/local/calib.dat_ /data/local/calib.dat"
adb reboot
5. Once the device has fully rebooted, on your PC:
adb shell "mkdir /data/local/lib"
adb push files\lsm_disabler.ko /data/local/lib/
adb shell "insmod /data/local/lib/lsm_disabler.ko"
adb shell "mkdir /data/local/bin"
adb shell "echo '#!/system/bin/sh' > /data/local/bin/autoexec.sh"
adb shell "echo '/system/xbin/soff' >> /data/local/bin/autoexec.sh"
adb shell "chmod 755 /data/local/bin/autoexec.sh"
adb shell "mount -o rw,remount /system /system"
adb shell "ln -s /data/local/bin/autoexec.sh /system/etc/install-recovery.sh"
adb push files\su /system/xbin/
adb shell "chown root.root /system/xbin/su"
adb shell "chmod 06755 /system/xbin/su"
adb shell "echo insmod /data/local/lib/lsm_disabler.ko > /system/xbin/soff"
adb shell "chmod 755 /system/xbin/soff"
adb shell "mount -o ro,remount /system /system"
adb shell "echo > /data/local.prop"
6. I think at this point I was just meant to exit the lock screen.
7. adb reboot
8. Congratulations. You're now rooted. Go to the Play Store and download "Superuser" (by ChainsDD) and "BusyBox" (by Stericson). If you decide to buy BusyBox Pro, do not check the "symlinks" option in version 8.0, otherwise it's game over (no wifi, no adb shell, no root, no remount). It's a pain, but not impossible to repair this situation, see http://forum.xda-developers.com/showthread.php?p=26964465. I've emailed the author and I hope future versions won't trash the system so easily.
After all this, I'd suggest download Titanium Backup for Root users, backing everything up, and uninstall the all the bloatware that came with the device. Read up elsewhere about Titanium Backup.
Let me know if this helped you! Not sure how many other English speakers are using this device
Thank you for this wonderful post! A few questions:
1.) I use the F-01D but I don't live in Japan. One of the gripes I've been having about this tablet is that there doesn't seem to be anyway for me to get firmware updates unless I go there. Once rooted am I able to use Market Enabler to fake a carrier and update my tablet?
2.) This is slightly off on a tangent but since I can't find much English material about this tablet anway I might as well ask here. Another one of my gripes about the tablet is it doesn't seem to handle video very well. even 720p video doesn't play smoothly on it. On most of the software I download, it seems hardware acceleration is not enabled? Is this a hardware issue, or is it blocked by the software. And if the latter would rooting the tablet help resolve this issue; or is there any other solution? From what I've read the OMAP processor in this thing should easily be able to handle 1080p video right?
Many thanks! :good:
Kinslayer81 said:
Well, with some help from Google Translate and some creative interpretations, I managed to do this and thought I'd provide some English instructions for others (with some added comments)
DISCLAIMER: AS USUAL, YOU SHOULD KNOW THAT FOLLOWING THESE ACTIONS (AND ESPECIALLY FOLLOWING THEM INCORRECTLY) CAN BRICK YOUR DEVICE (I.E. YOUR DEVICE WILL STOP WORKING, POSSIBLY PERMANENTLY). I AM NOT RESPONSIBLE FOR ANY DAMAGES THAT MAY ARISE FROM YOU FOLLOWING THESE INSTRUCTIONS, YOU DO SO AT YOUR OWN RISK.
Downloads
1. Windows -- the Arrows TAB USB driver Download.
2. Easy rooting toolkit (ERT) for Arrows Tab F-01D (ver 1.0) Download
3. goroh_kun's lsm_disabler.ko Download
Info
4. A su binary, such as the one found in DooMLoRD_v3_ROOT-zergRush-busybox-su.zip
5. Android SDK platform tools. adb(.exe) (and in Windows, specifically: AdbWinApi.dll, AdbWinUsbApi.dll)
Preparation
1. Unzip ert4F01D.zip, and in the subdirectory 'files' place:
* adb.exe (Windows only, from step 4 above)
* AdbWinApi.dll (Windows only, from step 4 above)
* AdbWinUsbApi.dll (Windows only, from step 4 above)
* lsm_disabler.ko (from step 3 above)
* su (from step 5 above)
2. Before connecting the USB, in Settings -> Applications -> Development:
* Check (tick) USB debugging ("Debug mode when USB is connected")
* Check (tick) Stay awake ("Screen will never sleep while charging")
3. Set up the USB drivers and Android Development stuff if you haven't already. I don't use Windows so can't help with this.
The Dirty Work
At this stage, you can run the batch file. Since I don't use Windows, I did the steps by hand, so you'll have to correlate your actions appropriately (I can't read Japanese either, so your guess is as good as mine ).
1. On your PC:
adb shell "mv /data/local/calib.dat /data/local/calib.dat_"
adb shell "ln -s /data/local.prop /data/local/calib.dat"
2. On the tablet, go into Google Maps, touch the GPS icon ("locate me" icon) on the top right hand corner, and then touch the BACK key to exit.
3. On your PC:
adb shell "echo ro.kernel.qemu=1 > /data/local.prop"
adb shell "rm /data/local/calib.dat"
adb shell "mv /data/local/calib.dat_ /data/local/calib.dat"
adb reboot
5. Once the device has fully rebooted, on your PC:
adb shell "mkdir /data/local/lib"
adb push files\lsm_disabler.ko /data/local/lib/
adb shell "insmod /data/local/lib/lsm_disabler.ko"
adb shell "mkdir /data/local/bin"
adb shell "echo '#!/system/bin/sh' > /data/local/bin/autoexec.sh"
adb shell "echo '/system/xbin/soff' >> /data/local/bin/autoexec.sh"
adb shell "chmod 755 /data/local/bin/autoexec.sh"
adb shell "mount -o rw,remount /system /system"
adb shell "ln -s /data/local/bin/autoexec.sh /system/etc/install-recovery.sh"
adb push files\su /system/xbin/
adb shell "chown root.root /system/xbin/su"
adb shell "chmod 06755 /system/xbin/su"
adb shell "echo insmod /data/local/lib/lsm_disabler.ko > /system/xbin/soff"
adb shell "chmod 755 /system/xbin/soff"
adb shell "mount -o ro,remount /system /system"
adb shell "echo > /data/local.prop"
6. I think at this point I was just meant to exit the lock screen.
7. adb reboot
8. Congratulations. You're now rooted. Go to the Play Store and download "Superuser" (by ChainsDD) and "BusyBox" (by Stericson). If you decide to buy BusyBox Pro, do not check the "symlinks" option in version 8.0, otherwise it's game over (no wifi, no adb shell, no root, no remount). It's a pain, but not impossible to repair this situation, see http://forum.xda-developers.com/showthread.php?p=26964465. I've emailed the author and I hope future versions won't trash the system so easily.
After all this, I'd suggest download Titanium Backup for Root users, backing everything up, and uninstall the all the bloatware that came with the device. Read up elsewhere about Titanium Backup.
Let me know if this helped you! Not sure how many other English speakers are using this device
Click to expand...
Click to collapse
Just wanted to say thank you again. The rooting worked perfectly, though it took me a while to manually type in all the commands. For people who want to try this, you do need to install busybox before any other programs such as rootchecker will properly verify that your device is actually rooted.
And just for anyone wondering - rooting and using MarketEnabler has NOT been able to resolve the issue of not being able to update the software overseas...
Hey, sorry for the late reply, busy times :>
Glad the post helped you! I know I was super amped to finally get rood and get rid of all the bloatware I couldn't even understand. Things have definitely been a lot smoother since then (but far from perfect, also dying for an ICS upgrade). As for your questions:
simzhewei said:
1.) I use the F-01D but I don't live in Japan. One of the gripes I've been having about this tablet is that there doesn't seem to be anyway for me to get firmware updates unless I go there. Once rooted am I able to use Market Enabler to fake a carrier and update my tablet?
Click to expand...
Click to collapse
From playing around, the requirements seem to imply that you *have to* upgrade via cellular data from a Docomo SIM card, and it can't be done via roaming, so yeah, it seems like you have to physically go to Japan to upgrade Your market enabler idea was a good one, but since you tried that (I'm assuming using the Docomo info), I guess the upgrade app is using a different source to check where you're at. Ultimately we need to somehow get hold of an update.zip (or other file) that can be run through the Recovery system (which does exist!).
2.) This is slightly off on a tangent but since I can't find much English material about this tablet anway I might as well ask here. Another one of my gripes about the tablet is it doesn't seem to handle video very well. even 720p video doesn't play smoothly on it. On most of the software I download, it seems hardware acceleration is not enabled? Is this a hardware issue, or is it blocked by the software. And if the latter would rooting the tablet help resolve this issue; or is there any other solution? From what I've read the OMAP processor in this thing should easily be able to handle 1080p video right?
Click to expand...
Click to collapse
Haven't tried 1080p, but after some tinkering I did get 720p playing. I use MX Player, and although they said it would download needed hardware decoders automatically, it didn't, and things improved a lot after I downloaded the MX Player ARMv7 codec. Video plays great, but to get sound, I had to run the sound through the software decoder (just tap the music note icon, and choose "Track #1 (S/W decoder)".
On the other hand, I found the hardware decoding often gets stuck (relaunching MX player just gives you a waiting indicator forever)... and the only way to fix it is a reboot. Since this happens quite often, it's incredibly annoying, and I'm hoping an upgrade will fix it. Let me know if this doesn't happen to you. Also have some very intermittent wifi issues, some things work fine (speedtest, etc) but apps like streaming radio, some work fine (spotify) and others don't work at all (di radio). Some things work fine for a while after a reboot.
---------- Post added at 10:02 AM ---------- Previous post was at 10:00 AM ----------
Incidentally, here's what happens if I try update via recovery (with no update files). Maybe it will help someone. Googling most of the stuff came up with nothing. The ** in the middle somewhere is stuff I couldn't read, guess I should go back and do it again but this is from quite a while ago.
Code:
C_L1_043
2.6.35.7
V19R36D
=======================
SD Downloader
=======================
Device SW Downloading...
Don't remove
the SD Card & the Battery.
checking battery
eMMC SD mount complete.
microSD mount complete.
Firm name :
Firm name :
Target:
Check eMMC(SD).
Firm name :
Update GANG file not found
File open error!
**ddl Touch Firm Write start
Firm name :
/external_sd/I2C_HSSP_Bridge_Parallel.cyacd file not found
firm name :
/sdcard/I2C_HSSP_Bridge_Parallel.cyacd file not found
#sddl touch firm not found ret: 1
SKIP sddl launch firm write end ret: 1
SD : SdFgldfirmwrite -------
firm name :
BAC_H_19.enc =
firm name :
BAC_H_1.9.enc =
error
SKIP sddl fgic firm write end ret: 1
end
****************************
****************************
****
All firmware not found!
****
Interesting situation...
First off...Kinslayer81, thanks for posting this. I found the original in Japanese, and was not eager to try to translate it. Thanks for putting in the work.
For everyone (especially if you got this to work) - when I went through the step, I keep getting a "permissions denied" message. Whether it's the ERT4F01D batch file, or typing the commands in... I get "permissions denied".
Did you guys encounter this?
Glad it helped you On which step are you getting the error? Any strange output on any of the preceding steps?
Every step is important, to be done in the exact same order, e.g. loading google maps and pressing the 'my location' icon, etc.
Dakedo_Baby said:
First off...Kinslayer81, thanks for posting this. I found the original in Japanese, and was not eager to try to translate it. Thanks for putting in the work.
For everyone (especially if you got this to work) - when I went through the step, I keep getting a "permissions denied" message. Whether it's the ERT4F01D batch file, or typing the commands in... I get "permissions denied".
Did you guys encounter this?
Click to expand...
Click to collapse
Permission denied
Oh I know... I'm not new to the game. I've stalked these boards for a while now... This is my first tablet though.
I've tried running both the ERT4F01D batch... and the manual input.
I get it from the batch file, as soon as I tell it to "RUN"... "Permissions Denied"
From manual input - LINE 2: adb shell "ln -s /data/local.prop /data/local/calib.dat" = "Permissions Denied"
Like there's some additional admin privilege I don't have. Hmmmmm....
And here's an additional kicker... the tablet auto-reboots each and every time. I've tried it a number of times (started over from the top), same result each time.
Kinslayer81 said:
Glad it helped you On which step are you getting the error? Any strange output on any of the preceding steps?
Every step is important, to be done in the exact same order, e.g. loading google maps and pressing the 'my location' icon, etc.
Click to expand...
Click to collapse
I must admit, I don't have any great ideas.
So you can move the file in the first step no problem, and just the attempt to symlink gives you the error?
What is the output of "adb shell ls -la /data/local/".
When does the auto reboot occur?
Dakedo_Baby said:
Oh I know... I'm not new to the game. I've stalked these boards for a while now... This is my first tablet though.
I've tried running both the ERT4F01D batch... and the manual input.
I get it from the batch file, as soon as I tell it to "RUN"... "Permissions Denied"
From manual input - LINE 2: adb shell "ln -s /data/local.prop /data/local/calib.dat" = "Permissions Denied"
Like there's some additional admin privilege I don't have. Hmmmmm....
And here's an additional kicker... the tablet auto-reboots each and every time. I've tried it a number of times (started over from the top), same result each time.
Click to expand...
Click to collapse
I'm stumped too...
Well... this is getting a little interesting...
LS command - no problem (included image)
Decided to have another shot at it... and I was able to get a little further. Still encountered a problem
Now, the INSMOD command failed... "Operation not permitted"
Kinslayer81 said:
I must admit, I don't have any great ideas.
So you can move the file in the first step no problem, and just the attempt to symlink gives you the error?
What is the output of "adb shell ls -la /data/local/".
When does the auto reboot occur?
Click to expand...
Click to collapse
file system set to READ-only...
My file systems are set to Read-only... that explains quite a bit....
Dakedo_Baby said:
Well... this is getting a little interesting...
LS command - no problem (included image)
Decided to have another shot at it... and I was able to get a little further. Still encountered a problem
Now, the INSMOD command failed... "Operation not permitted"
Click to expand...
Click to collapse
Dakedo_Baby said:
My file systems are set to Read-only... that explains quite a bit....
Click to expand...
Click to collapse
Do you mind me asking, how did you set your file system to read-write? I have the same error as you were seeing but it's not allowing me to remount as read-write...
Can you confirm what command you used please?
thanks
Sorry again for late reply
Dakedo_Baby, I've looked at your stuff a few times and it's not obvious to me where things are going wrong. I again need some more info to try get a better idea of what's going on:
1) Before the first reboot, let me know the output of: adb shell "cat /data/local.prop"
2) After the reboot, let me know the output of: adb shell id
As for the file systems, well, /data should be already mounted rw, and /system should be mounted ro until you remount it. You can see how each is mounted with just "adb mount".
histrix said:
Do you mind me asking, how did you set your file system to read-write? I have the same error as you were seeing but it's not allowing me to remount as read-write...
Can you confirm what command you used please?
thanks
Click to expand...
Click to collapse
The command to remount the /system partition as read-write is: adb shell "mount -o rw,remount /system /system"
Of course, you should only be executing that step as part of the given sequence and in the correct order. You won't be able to execute the command until after your first reboot in the instructions, after which adb should still be running as root.
Any good Custom ICS roms you guys recommend after rooting the Arrows Tab?
ICS..Hurray!!!
Just found this out in Fujitsu site:
http://spf.fmworld.net/fujitsu/c/update/nttdocomo/f-01d/update1/top/index.html
There is a 4.0.3 download available. Click the 3rd Button (Green) downloads the zip package.
The 2nd link has howto from PC.
Still not sure if this will work, but trying out.
Also may lose root..and whatever else..So keeping my fingers crossed.
Google translation link
http://translate.google.com/transla...update/nttdocomo/f-01d/update1/top/index.html
Will post how it goes.
I made a new thread for this, since it's a different topic and you'll lose root too
http://forum.xda-developers.com/showthread.php?p=32200671
insmod lsm-disabler.so to remount /system rw
Back to the original topic... what I maybe didn't notice before is that the stock kernel blocks even root users from remounting /system as rw. So in case you ever need rw access to /system again, obviously you'll first have to be root, and afterwards you'll need to "insmod lsm-disabler.so" (as per the original instructions) before you can "busybox mount -o remount,rw /system" (or run any root app that remounts the system partition).
locked F-01d
Kinslayer81 said:
Well, with some help from Google Translate and some creative interpretations, I managed to do this and thought I'd provide some English instructions for others (with some added comments)
DISCLAIMER: AS USUAL, YOU SHOULD KNOW THAT FOLLOWING THESE ACTIONS (AND ESPECIALLY FOLLOWING THEM INCORRECTLY) CAN BRICK YOUR DEVICE (I.E. YOUR DEVICE WILL STOP WORKING, POSSIBLY PERMANENTLY). I AM NOT RESPONSIBLE FOR ANY DAMAGES THAT MAY ARISE FROM YOU FOLLOWING THESE INSTRUCTIONS, YOU DO SO AT YOUR OWN RISK.
Downloads
1. Windows -- the Arrows TAB USB driver Download.
2. Easy rooting toolkit (ERT) for Arrows Tab F-01D (ver 1.0) Download
3. goroh_kun's lsm_disabler.ko Download
Info
4. A su binary, such as the one found in DooMLoRD_v3_ROOT-zergRush-busybox-su.zip
5. Android SDK platform tools. adb(.exe) (and in Windows, specifically: AdbWinApi.dll, AdbWinUsbApi.dll)
Preparation
1. Unzip ert4F01D.zip, and in the subdirectory 'files' place:
* adb.exe (Windows only, from step 4 above)
* AdbWinApi.dll (Windows only, from step 4 above)
* AdbWinUsbApi.dll (Windows only, from step 4 above)
* lsm_disabler.ko (from step 3 above)
* su (from step 5 above)
2. Before connecting the USB, in Settings -> Applications -> Development:
* Check (tick) USB debugging ("Debug mode when USB is connected")
* Check (tick) Stay awake ("Screen will never sleep while charging")
3. Set up the USB drivers and Android Development stuff if you haven't already. I don't use Windows so can't help with this.
The Dirty Work
At this stage, you can run the batch file. Since I don't use Windows, I did the steps by hand, so you'll have to correlate your actions appropriately (I can't read Japanese either, so your guess is as good as mine ).
1. On your PC:
adb shell "mv /data/local/calib.dat /data/local/calib.dat_"
adb shell "ln -s /data/local.prop /data/local/calib.dat"
2. On the tablet, go into Google Maps, touch the GPS icon ("locate me" icon) on the top right hand corner, and then touch the BACK key to exit.
3. On your PC:
adb shell "echo ro.kernel.qemu=1 > /data/local.prop"
adb shell "rm /data/local/calib.dat"
adb shell "mv /data/local/calib.dat_ /data/local/calib.dat"
adb reboot
5. Once the device has fully rebooted, on your PC:
adb shell "mkdir /data/local/lib"
adb push files\lsm_disabler.ko /data/local/lib/
adb shell "insmod /data/local/lib/lsm_disabler.ko"
adb shell "mkdir /data/local/bin"
adb shell "echo '#!/system/bin/sh' > /data/local/bin/autoexec.sh"
adb shell "echo '/system/xbin/soff' >> /data/local/bin/autoexec.sh"
adb shell "chmod 755 /data/local/bin/autoexec.sh"
adb shell "mount -o rw,remount /system /system"
adb shell "ln -s /data/local/bin/autoexec.sh /system/etc/install-recovery.sh"
adb push files\su /system/xbin/
adb shell "chown root.root /system/xbin/su"
adb shell "chmod 06755 /system/xbin/su"
adb shell "echo insmod /data/local/lib/lsm_disabler.ko > /system/xbin/soff"
adb shell "chmod 755 /system/xbin/soff"
adb shell "mount -o ro,remount /system /system"
adb shell "echo > /data/local.prop"
6. I think at this point I was just meant to exit the lock screen.
7. adb reboot
8. Congratulations. You're now rooted. Go to the Play Store and download "Superuser" (by ChainsDD) and "BusyBox" (by Stericson). If you decide to buy BusyBox Pro, do not check the "symlinks" option in version 8.0, otherwise it's game over (no wifi, no adb shell, no root, no remount). It's a pain, but not impossible to repair this situation, see http://forum.xda-developers.com/showthread.php?p=26964465. I've emailed the author and I hope future versions won't trash the system so easily.
After all this, I'd suggest download Titanium Backup for Root users, backing everything up, and uninstall the all the bloatware that came with the device. Read up elsewhere about Titanium Backup.
Let me know if this helped you! Not sure how many other English speakers are using this device
Click to expand...
Click to collapse
thanks for the rooting tutorial but mine is also locked to ntt DOCOMO,,,ANY WAY TO UNLOCK IT
how to unlock the network
please help me how to unlock this tablet i got this tablet from my japan friend but it is network locked please help me to unlock this
Hi friends. I have bought a HCL me U1 tab : 7" display, 512 mb ram, running android 4.0.3 ICS on it. But it does not supports Google play on it and I am pretty upset. Tried to root it with z4root, gingerbreak but nothing works.. Please help.
yup, Im stuck with this tab too, its good tab though.
IT lacks gapps and has few bugs, I hope we get a way to root it soon, or a custom rom will be much better
somebody ..help us
Have you tried SuperOneClick and/or Unlock Root? Both tools are capable of rooting a vast number of devices, so it's worth a shot.
One click ==> yes, will try another one soon. One click doesnt seem to work though. Any help here would be much appreciated
---------- Post added at 01:58 PM ---------- Previous post was at 01:31 PM ----------
ok unlock root gets stuck on 'try to get shell root permissions'. It recognizes the device and all, but gets stuck here
This tablet can be rooted.
Follow this link
http://crazyfreakgamers.com/hclme/viewtopic.php?f=2&t=60
follow below steps to root your HCL Tab U!
********* i am not responsible for any mess with your device do this on your own risk *****************
-Install android SDK and set up under program files (the path will be like C:\Program files/android/android-sdk/platform-tools/adb
-open SDK manager (under android-SDK Folder)
-WHen the list appear, scroll down and download Google USB driver and install it. Then scroll above and download Android 4.0.3 repositories
__-Now turn USB debugging ON in settings
-Download Superuser file from "downloads.androidsu.com/superuser/Superuser-3.0.7-efghi-signed.zip" then extract the zip file to desktop and you will see 2 folder as "System" and "Meta-INF"
-Connect your Tab via USB
-Open CMD with administrator rights (search CMD then right click on it and select run as administrator)
-Type the following line of code
>cd..
>cd..
>cd..
>cd program files
>cd android
>cd android-sdk
>cd platform-tools
>adb
-While tab is connected to PC, Restart tablet into recovery mode by pressing start and vol+ button at the same time
>adb devices
>adb shell
>adb root (you will see a message "adb is already running as a root")
-Restart the tablet
-Wait till system opens till its home screen appears
>adb devices (you should see your device number)
>adb shell getprop ro.secure (output should be 0)
>adb shell mount -oremount,rw /dev/block/system /system
>adb push c:\users/"username"/desktop/system/bin/su /system/bin/
>adb push c:\users/"username"/desktop/system/bin/su /system/_install/bin/
>adb shell chmod 4777 /system/bin/su
>adb shell mount -oremount,ro /dev/block/system /system
-Download superuser app from market or anyother site and install it. Just open it once
-Download Yaffs explorer from market or anyother site and install it.
-Open the app and Click the drag down button on top and select "/".
-open the 2nd option which will be bin> /system/_install/bin
-Scroll down to and search for SU and you should be able to see that
-Click and hold and it will open up a pop up menu so in that select execute, then tick "As root" option and click Go button
-Superuser dialog box will open adn you have to accept it and you will be permitted to root level access.
-Now download any app which require root permission and use it and you will get a dialog box telleing you "this app requires Superuser permission" then click Yes. Now you should have definatly been granted SU permission.
Enjoy
originally by
Milen Balchandra
Superb_user said:
********* i am not responsible for any mess with your device do this on your own risk *****************
-Install android SDK and set up under program files (the path will be like C:\Program files/android/android-sdk/platform-tools/adb
-open SDK manager (under android-SDK Folder)
-WHen the list appear, scroll down and download Google USB driver and install it. Then scroll above and download Android 4.0.3 repositories
__-Now turn USB debugging ON in settings
-Download Superuser file from "downloads.androidsu.com/superuser/Superuser-3.0.7-efghi-signed.zip" then extract the zip file to desktop and you will see 2 folder as "System" and "Meta-INF"
-Connect your Tab via USB
-Open CMD with administrator rights (search CMD then right click on it and select run as administrator)
-Type the following line of code
>cd..
>cd..
>cd..
>cd program files
>cd android
>cd android-sdk
>cd platform-tools
>adb
-While tab is connected to PC, Restart tablet into recovery mode by pressing start and vol+ button at the same time
>adb devices
>adb shell
>adb root (you will see a message "adb is already running as a root")
-Restart the tablet
-Wait till system opens till its home screen appears
>adb devices (you should see your device number)
>adb shell getprop ro.secure (output should be 0)
>adb shell mount -oremount,rw /dev/block/system /system
>adb push c:\users/"username"/desktop/system/bin/su /system/bin/
>adb push c:\users/"username"/desktop/system/bin/su /system/_install/bin/
>adb shell chmod 4777 /system/bin/su
>adb shell mount -oremount,ro /dev/block/system /system
-Download superuser app from market or anyother site and install it. Just open it once
-Download Yaffs explorer from market or anyother site and install it.
-Open the app and Click the drag down button on top and select "/".
-open the 2nd option which will be bin> /system/_install/bin
-Scroll down to and search for SU and you should be able to see that
-Click and hold and it will open up a pop up menu so in that select execute, then tick "As root" option and click Go button
-Superuser dialog box will open adn you have to accept it and you will be permitted to root level access.
-Now download any app which require root permission and use it and you will get a dialog box telleing you "this app requires Superuser permission" then click Yes. Now you should have definatly been granted SU permission.
Enjoy
originally by
Milen Balchandra
Click to expand...
Click to collapse
after doing the whole process
when i try to execute su as root (YAFFS EXPLORER)
Super user not asks to allow root access
Nothing happens when i select to run su as root pls help
Can any make cwmflashable zip for dhis tab??? Pleeeesssssee
Sent from my GT-S5360 using xda premium
HCL U1 Help
Anybody having the stock rom of HCL u1 .ftf file???? I desperately need the original stock files...please...atleast gimme the link for it...
Can't find superuser and yaffs explorer
Superb_user said:
********* i am not responsible for any mess with your device do this on your own risk *****************
-Install android SDK and set up under program files (the path will be like C:\Program files/android/android-sdk/platform-tools/adb
-open SDK manager (under android-SDK Folder)
-WHen the list appear, scroll down and download Google USB driver and install it. Then scroll above and download Android 4.0.3 repositories
__-Now turn USB debugging ON in settings
-Download Superuser file from "downloads.androidsu.com/superuser/Superuser-3.0.7-efghi-signed.zip" then extract the zip file to desktop and you will see 2 folder as "System" and "Meta-INF"
-Connect your Tab via USB
-Open CMD with administrator rights (search CMD then right click on it and select run as administrator)
-Type the following line of code
>cd..
>cd..
>cd..
>cd program files
>cd android
>cd android-sdk
>cd platform-tools
>adb
-While tab is connected to PC, Restart tablet into recovery mode by pressing start and vol+ button at the same time
>adb devices
>adb shell
>adb root (you will see a message "adb is already running as a root")
-Restart the tablet
-Wait till system opens till its home screen appears
>adb devices (you should see your device number)
>adb shell getprop ro.secure (output should be 0)
>adb shell mount -oremount,rw /dev/block/system /system
>adb push c:\users/"username"/desktop/system/bin/su /system/bin/
>adb push c:\users/"username"/desktop/system/bin/su /system/_install/bin/
>adb shell chmod 4777 /system/bin/su
>adb shell mount -oremount,ro /dev/block/system /system
-Download superuser app from market or anyother site and install it. Just open it once
-Download Yaffs explorer from market or anyother site and install it.
-Open the app and Click the drag down button on top and select "/".
-open the 2nd option which will be bin> /system/_install/bin
-Scroll down to and search for SU and you should be able to see that
-Click and hold and it will open up a pop up menu so in that select execute, then tick "As root" option and click Go button
-Superuser dialog box will open adn you have to accept it and you will be permitted to root level access.
-Now download any app which require root permission and use it and you will get a dialog box telleing you "this app requires Superuser permission" then click Yes. Now you should have definatly been granted SU permission.
Enjoy
originally by
Milen Balchandra
Click to expand...
Click to collapse
Where do I download the Superuser app from? Do I have to download it in my PC and then somehow install it into my U1? Or Do I download and install it directly into my U1??
I'm stuck at the superuser app part... And couldn't find yaffs explorer in the HCL ME market... There's no other Market in my tablet yet!
I'm pretty new to such things, It would be great if you help me out!
Thanks!
Rooted HCL ME U1
KingTodi said:
Where do I download the Superuser app from? Do I have to download it in my PC and then somehow install it into my U1? Or Do I download and install it directly into my U1??
I'm stuck at the superuser app part... And couldn't find yaffs explorer in the HCL ME market... There's no other Market in my tablet yet!
I'm pretty new to such things, It would be great if you help me out!
Thanks!
Click to expand...
Click to collapse
This guide is successfully tested by me.
1. You need a 32 bit OS. (I have used 7 Pro x86).
2. Turn USB debugging ‘ON’ in settings of the tablet.
3. Download Superuser hear
Then extract the zip file to desktop:\ & you will see 2 folders as
“System” and “Meta-INF”.
4. Download the drivers. Then connect the tablet & install the drivers
using device manager.
5. Download SuperOneClick!. Extract the archive, go to the folder
named ADB. Open an elevated command prompt download that first
6. CONTINUE WITH THE FOLLOWING COMMANDS.
>adb root (you will see a message “adb is already running as a root”)
>adb devices (you should see your device number)
>adb shell (adb shell will run and daemon tool will also run if this message is not see then close elevated command prompt and restart tablet and continue with following commands)
7. NOW RESTART THE TABLET AND WAIT TILL THE HOME SCREEN APPEARS.NOW
CONTINUE WITH FOLLOWING COMMANDS.
>adb shell getprop ro.secure (output should be 0)
>adb shell mount -oremount,rw /dev/block/system /system
>adb push c:\users/”username”/desktop/system/bin/su /system/bin/
>adb push c:\users/”username”/desktop/system/bin/su /system/_install/bin/
>adb shell chmod 4777 /system/bin/su
>adb shell mount -oremount,ro /dev/block/system /system
8. install busybox first and then check root status with root checker
superuser app,Yaffs explorer,Root Checker can be downloaded from any other site.
Custom Rom HCL ME U1 Tablet
Try this link to Install CWM recovery on HCl ME U1 and also Root The HCl ME U1 tablet
Link: http://tabletkinghcl007.blogspot.in/
jjv007 said:
This guide is successfully tested by me.
1. You need a 32 bit OS. (I have used 7 Pro x86).
2. Turn USB debugging ‘ON’ in settings of the tablet.
3. Download Superuser hear
Then extract the zip file to desktop:\ & you will see 2 folders as
“System” and “Meta-INF”.
4. Download the drivers. Then connect the tablet & install the drivers
using device manager.
5. Download SuperOneClick!. Extract the archive, go to the folder
named ADB. Open an elevated command prompt download that first
6. CONTINUE WITH THE FOLLOWING COMMANDS.
>adb root (you will see a message “adb is already running as a root”)
>adb devices (you should see your device number)
>adb shell (adb shell will run and daemon tool will also run if this message is not see then close elevated command prompt and restart tablet and continue with following commands)
7. NOW RESTART THE TABLET AND WAIT TILL THE HOME SCREEN APPEARS.NOW
CONTINUE WITH FOLLOWING COMMANDS.
>adb shell getprop ro.secure (output should be 0)
>adb shell mount -oremount,rw /dev/block/system /system
>adb push c:\users/”username”/desktop/system/bin/su /system/bin/
>adb push c:\users/”username”/desktop/system/bin/su /system/_install/bin/
>adb shell chmod 4777 /system/bin/su
>adb shell mount -oremount,ro /dev/block/system /system
8. install busybox first and then check root status with root checker
superuser app,Yaffs explorer,Root Checker can be downloaded from any other site.
Click to expand...
Click to collapse
hey can i use 64 bit os?? any other method for 64 bit os??
Hi guys
I've imported the SH-06D from Japan and the phone is running great, however I'd like to remove some system apps etc to help speed up the phone (it's still on 2.3.5) and obviously tweak it as well.
I know there is an existing thread on the SH-01D (predecessor to the SH-06D) but I'm wondering if anyone has successfully rooted the SH-06D and if so, is there an (easy) process to do this?
Another reason I want to root, is to install the UI from the upcoming Evangelion Nerv edition of the SH-06D that is due to be released in a few days.
ICS for the SH-06D is just around the corner (due to be released in July) but I'd realy appreciate any help, assistance or tips in rooting the phone as it is now.
Cheers! :fingers-crossed:
Anyone?
:-(
here is a link to root the sh-06d :
http://itsuki.ddo.jp/gadget/index.php?SH-06D
THANK YOU!
Have you tried this method and does it work? Can you assist me in following those directions?
Cheers
interfreak said:
THANK YOU!
Have you tried this method and does it work? Can you assist me in following those directions?
Cheers
Click to expand...
Click to collapse
i haven't tried since i don't have this phone.
i can try to help you if you want.
testnumero said:
i haven't tried since i don't have this phone.
i can try to help you if you want.
Click to expand...
Click to collapse
Thanks mate!
I'm fumbling through the process now - it's a little hard when you are using google translate lol!
OK, I've run through all the steps but..
When I get to the end of the process:
C:\Users\interfreak\Desktop
$ su
su
su: permission denied
:-(
interfreak said:
OK, I've run through all the steps but..
When I get to the end of the process:
C:\Users\interfreak\Desktop
$ su
su
su: permission denied
:-(
Click to expand...
Click to collapse
i don't know what is the problem, try to do steps again.
Tried, same result. :-(
interfreak said:
Tried, same result. :-(
Click to expand...
Click to collapse
i'll ask to translate it
Thanks mate!!! :highfive:
I want to know untill now has SH-06D been rooted?
I wish someone could dump ROM or launcher from SH-06 NERV version:fingers-crossed:
I'm working on the translation for root on Sharp Aquos SH-06D.
Please give me one or two more days!
That is highly impossible, having full root in J Phone are hard enough. Unlocking the bootloader is a wet dream for almost everyone who likes J phone
lightout said:
I want to know untill now has SH-06D been rooted?
I wish someone could dump ROM or launcher from SH-06 NERV version:fingers-crossed:
Click to expand...
Click to collapse
I'm trying to hard reset my SH-06D, but I can't do it via settings-privacy. I can select to wipe, but nothing happens.
Any suggestions?
I got the Nerv edition
Hey man, how did the rooting go? I ordered the Nerv edition of this phone, and I want to root it (mainly to pair my sixaxis controller for psx emulation) but wanted to consult with you first as a precaution.
Here is the a rough translation of the root guide found here:
http://itsuki.ddo.jp/gadget/index.php?SH-06D
Big thanks to testnumero for the help!
Please don't ask me directly for help. I don't own this phone.
A quick look at root
• With root you can freeze preinstalled bloatware and backup application settings and game save data.
• 3D content from /system can be played on other devices and 3DTVs.
Unresponsive apps can be frozen which will help the device run smoother and have a longer battery life.
Applications which are frozen disappear from your drawer making the device look cleaner and keeping your mind at ease.
• The process is similar to the one used for SH-01D.
• If an update patch is released or the Android 4.0 summer update is released then this guide will no longer be of help.
(Make sure your device is the following: Android Ver. 2.3.5 Build No. 01.00.03)
• If your device becomes a paperweight I won’t be held responsible.
• Follow this guide at your own risk.
↑
Preparations – Before you begin
• Install Android SDK and SHARP ADB USB drivers and make to use ADB.
• 「Settings」→「Applications」→「Development」→「USB Debugging」 checked.
• SH-06D and micro USB cable to connect to your PC
↑
Required Files
• Download "shdisphook" from the following link and extract.
http://goo.gl/Bs6Iq
• Download shsdgetroot-omap4.zip from the following link and extract.
http://www1.axfc.net/uploader/File/so/78144
• Download shbootgetroot-su.lzh from the following link and extract.
http://www.mediafire.com/?6i0n32jlwbxe8cp
• Keep all extracted files in the same folder.
↑
Creating files
• Create a file named "shdisphook.bat" in the folder with the extracted files.
Copy and paste the following and save.
adb push onload.sh /data/local/
adb push libsdservice_jni.so /data/local/
adb push shdisphook /data/local/
adb shell chmod 755 /data/local/onload.sh
adb shell chmod 755 /data/local/shdisphook
adb reboot
adb wait-for-device shell /data/local/shdisphook
pause
• Create a file named "oncmd.sh" and put the following in the description.
(Save the line break as LF)
chmod 777 /cache
chmod 666 /cache/recovery
• Replace the contents of the file "installfile.cmd" with the following and save.
adb shell /data/local/shsdgetroot-omap4 -c "/system/bin/mount -o rw,remount -t rootfs rootfs /"
adb shell /data/local/shsdgetroot-omap4 -c "/system/bin/chmod 777 /sbin"
adb push su /sbin
adb push busybox /sbin
adb shell /data/local/shsdgetroot-omap4 -c "/system/bin/chown 0.0 /sbin/su"
adb shell /data/local/shsdgetroot-omap4 -c "/system/bin/chown 0.0 /sbin/busybox"
adb shell /data/local/shsdgetroot-omap4 -c "/system/bin/chmod 6755 /sbin/su"
adb shell /data/local/shsdgetroot-omap4 -c "/system/bin/chmod 755 /sbin/busybox"
adb shell /data/local/shsdgetroot-omap4 -c "/sbin/busybox --install -s /sbin"
adb shell /data/local/shsdgetroot-omap4 -c "/system/bin/chmod 755 /sbin"
adb shell /data/local/shsdgetroot-omap4 -c "/system/bin/mount -o ro,remount -t rootfs rootfs /"
adb push Superuser.apk /data/local/
adb shell /system/bin/pm install -t -f -r /data/local/Superuser.apk
adb shell /system/bin/rm /data/local/Superuser.apk
exit /b
↑
Step 1
• Open command prompt to the folder with the extracted files and navigate to "shdisphook".
Execute "shdisphook.bat". (You can also just double click on the .bat file)
• The device will reboot so just wait for the [Press any key to continue] message to appear.
If more than a few minutes have passed and nothing has appeared then, force close and execute "shdisphook.bat" again.
(When you fail your PC will reboot or your SH-06D WiFi will start. There is a high rate of success when you immediately unlock the lock screen for your device when it goes to sleep.)
↑
Step 2
• Open command prompt and send oncmd.sh to SH-06D to change permissions
adb push oncmd.sh /data/local/oncmd.sh
adb shell chmod 755 /data/local/oncmd.sh
• 「Settings」→「microSD and device storage」→「Unmount microSD」 This will execute the file "oncmd.sh" , which was sent to the device earlier.
(Cancel the message for 「Unmount microSD」)
• Enter the following commands.
adb shell mv /cache/recovery /cache/recovery_
adb shell ln -s /dev/shsd /cache/recovery
• Execute the following adb shell ls -l /cache and if you see the following message you have succeed.
drwxrwx--- root root 2011-11-11 03:39 lost+found
drw-rw-rw- system cache 2012-01-24 10:48 recovery_
lrwxrwxrwx shell shell 2012-03-02 13:24 recovery -> /dev/shsd
• Next execute adb shell ls -l /dev/shsd you should get the following message if you were successful.
crw-rw-rw- system cache 231, 0 2012-04-23 02:01 shsd
↑
Step 3
• Execute adb push shsdgetroot-omap4 /data/local
• Execute adb shell /system/bin/chmod 755 /data/local/shsdgetroot-omap4
• Execute adb shell /data/local/shsdgetroot-omap4 -v -m -u
• The “# “mark will appear there will be no response. Close command prompt for now.
• Execute installfile.cmd
• Check if you have root with the following adb shell→su
↑
After you reboot
• After you reboot you will lose root rights so execute shdisphook.bat→Cancel Unmount microSD →execute installfile.cmd and you should have root again.
The reason why you cannot do a clean wipe or nothing happen is because the recovery section has been move out into another location, causing it to not loading the recovery correctly.
Check with SH-01d part, I have asked similar question there and I revert the recovery in order to wipe the phone..
You need to rearrange the following section like on the sh-01d when you hit this part:
(Following is Original command that you relocated the recovery for root)
adb shell mv /cache/recovery /cache/recovery_
adb shell ln -s /dev/shsd /cache/recovery
And replace with the revert command found on sh-01d thread. You will need to redo all the steps from step 1 to step 2 and STOP AFTER YOU REVERT the RECOVERY.
You should be able to do a full wipe with no issue then. DO NOT POWER DOWN or RESET!!! You will have to REDO it again as it REQUIRES SHDSIHOOK to input shell command.
Hope it helps
waiting！！！！！！！！！！