Related
After switching to linux, my phone no longer recognizes my computer and doesnt give the option to go to disc mode, sorry if its a dumb question but could someone tell me what i need to do to get it working again? Im not familiar with the os yet so im clueless.
you can't use mass storage mode?
it doesnt do anything when i plug it in but charge i have it set to ask what i want it to do when i plug it in
Justjusten said:
it doesnt do anything when i plug it in but charge i have it set to ask what i want it to do when i plug it in
Click to expand...
Click to collapse
Do you have debug turned on on the phone?
Thats because Linux doesnt see your phone. You need to setup UDEV to recognize your Hero. Follow this tutorial. And when I say "Follow" I MEAN FOLLOW. No skipping.
http://forum.xda-developers.com/showthread.php?t=537508
do i have to reinstall linux to do this ?
Justjusten said:
do i have to reinstall linux to do this ?
Click to expand...
Click to collapse
What flavor do you have?
im using mint i think its based on ubuntu
So, did you follow directions? Should work with any flavor of Linux.
im trying but i dont have a .bashrc file so i made one and when i put this code (sudo /etc/init.d/udev restart) into the terminal i get
(Rather than invoking init scripts through /etc/init.d, use the service(8)
utility, e.g. service udev restart
Since the script you are attempting to invoke has been converted to an
Upstart job, you may also use the restart(8) utility, e.g. restart udev
udev start/running, process 2427)
Justjusten said:
do i have to reinstall linux to do this ?
Click to expand...
Click to collapse
No, you don't have to reinstall Linux.
Justjusten said:
im using mint i think its based on ubuntu
Click to expand...
Click to collapse
Mint is a derivative of Ubuntu, so yes, it's based off of it.
Justjusten said:
im trying but i dont have a .bashrc file so i made one and when i put this code (sudo /etc/init.d/udev restart) into the terminal i get
(Rather than invoking init scripts through /etc/init.d, use the service(8)
utility, e.g. service udev restart
Since the script you are attempting to invoke has been converted to an
Upstart job, you may also use the restart(8) utility, e.g. restart udev
udev start/running, process 2427)
Click to expand...
Click to collapse
You don't need to create the .bashrc file... it's already there. The period in front of the bashrc indicates that the file is hidden.
To see hidden files, run this command:
Code:
[B]ls -a[/B]
This will show you hidden files, any files with a period in front of it, will always be hidden.
Or navigate to the folder that it says that it is in and press ctrl + h
This will show you all the hidden files inside of the folder. Without having to use the terminal.
Justjusten said:
it doesnt do anything when i plug it in but charge i have it set to ask what i want it to do when i plug it in
Click to expand...
Click to collapse
Did you try pulling down the status bar and clicking on Charge Only to set it to disk mode?
If all else fails you can reboot to recovery and USB-MS toggle. If that doesn't work then something is messed up in your distro. Test if mounting works while in recovery and report your results.
I already did the control + h to show hidden folders and there isnt a .bashrc there is one under etc except it is bash.bashrc and i cant edit it , and i already tried the usb-ms toggle in recovery and nothing happened. Thanks for all the help so far guys, and if there is something wrong with my distro i dont mind getting a new one, does anyone have and suggestions on what to go with though?
Justjusten said:
I already did the control + h to show hidden folders and there isnt a .bashrc there is one under etc except it is bash.bashrc and i cant edit it , and i already tried the usb-ms toggle in recovery and nothing happened. Thanks for all the help so far guys, and if there is something wrong with my distro i dont mind getting a new one, does anyone have and suggestions on what to go with though?
Click to expand...
Click to collapse
There shouldnt be anything wrong with your Distro. Mint is built off Ubuntu so in essence it should work. Maybe download Ubuntu.
i think ill make a live disc of ubuntu and see if my phone is recognized at that point and if not then i wont install it
You cant edit it because you have to have root access. You should try typing in terminal sudo chmod permissions to give you root access. Im definitely not that good at linux but i figured out a majority of it.
make a file in /etc/udev/rules.d/ called 51-android.rules
here is mine.
Code:
SUBSYSTEMS=="usb", ATTRS{idVendor}=="0bb4", MODE="0666" , GROUP="plugdev"
Make sure you belong to the plugdev group, you probably already are. I can execute adb commands without being root user.
Justjusten said:
i think ill make a live disc of ubuntu and see if my phone is recognized at that point and if not then i wont install it
Click to expand...
Click to collapse
just stick to what works and that's windows 7, i hate linux on a pc.
fixxxer2008 said:
just stick to what works and that's windows 7, i hate linux on a pc.
Click to expand...
Click to collapse
Well that is a debate topic for another place. For me I've formatted the drive on my last 4 new laptops and have not looked back.
Hello,
I need beta testers running Mac OS X to test a new application.
This application is for people who are either uncomfortable or unwilling to use Terminal and ./adb for pushing files to their device.
This first beta version is just to test how it works on different computers. It pushes the file to the sdcard of the phone using ./adb. The only input needed from the user is to select the file.
Later releases will let the user choose which folder on the device to copy to, but the next release will probably just involve pushing .apk to the /system/app folder.
Please let me know the results.
http://derekcwilkinson.com/PushFile.zip
Beta 2:
http://derekcwilkinson.com/Push_File_Beta_2.zip
Change Log:
Added option to choose the location that the file is to be pushed to.
Added Recovery application
Added Reboot application.
Planned Updates:
Pull File - Ready
Device Backup - PM me if you know a good way to backup with ./adb (mine is taking too long)
Device Backup w/SD - PM me if you know a good way to backup with ./adb (mine is taking too long)
Install .apk - testing
Uninstall .apk - testing
Restore Backup - going to take awhile (need to get device backup working first)
Restore Backup w/SD - going to take awhile (need to get device backup working first)
Flash ROM - testing
is this an actual program or a script?
Works fine for me
mrchu001 said:
is this an actual program or a script?
Click to expand...
Click to collapse
It's a program that runs a script
It's just a test to see how it works, I will turn it into a more "real" application later.
I've updated it to Beta 2
I'm copied/pasted the android folder into /User/document but when i run "Push File With Location" show this error message -->
( iMac Snow Leopard v.10.6.3 build 10D573
@rainbow
same thing happening to me!
rainbow2112 said:
I'm copied/pasted the android folder into /User/document but when i run "Push File With Location" show this error message -->
( iMac Snow Leopard v.10.6.3 build 10D573
Click to expand...
Click to collapse
Hmm, strange, I haven't had any beta testers have this issue.
Is the phone connected with USB debugging?
derekwilkinson said:
Is the phone connected with USB debugging?
Click to expand...
Click to collapse
Yes, I have always flag on debugging USB mode.
rainbow2112 said:
Yes, I have always flag on debugging USB mode.
Click to expand...
Click to collapse
Try this, and tell me where the error comes up.
http://derekcwilkinson.com/PushFileSource.zip
derekwilkinson said:
Try this, and tell me where the error comes up.
http://derekcwilkinson.com/PushFileSource.zip
Click to expand...
Click to collapse
When run this, automator show this windows ...
rainbow2112 said:
When run this, automator show this windows ...
Click to expand...
Click to collapse
Ah, you're using a different language. That could be the problem. Is the folder path still /Documents/Android/SDK/tools on your computer?
Also, when you run it in Automator, where does the error occur?
derekwilkinson said:
Ah, you're using a different language. That could be the problem. Is the folder path still /Documents/Android/SDK/tools on your computer?
Also, when you run it in Automator, where does the error occur?
Click to expand...
Click to collapse
The folder path in my iMac is /Users/Rainbow/Documents/Android/SDK/tools
the error occur after a few seconds after click OK after choosing the file to be sent to MemoryCard
Okay, if it doesn't occur until then, that means it sees the device and android SDK. Is the SD card mounted on the computer? are you copying to /sdcard/ as the file path?
derekwilkinson said:
Okay, if it doesn't occur until then, that means it sees the device and android SDK. Is the SD card mounted on the computer? are you copying to /sdcard/ as the file path?
Click to expand...
Click to collapse
No, sdcard no is mounted.
i don't understand this_ " are you copying to /sdcard/ as the file path?" sorry
When that window pops up (the one in your screenshot) are you putting /sdcard/ in the text box?
im going to try your app out =]
excited.
Sick of windows..
I am so sick of using a windows computer to do anything on my Hero so as soon as I get home tomorrow I will be trying this out on my system. SL 10.6.4 and I will be so happy to do it..
404 File not found. I'd love to help test this - can someone please re-upload the zip?
Edited 1/16/11
I'm using root explorer so this isn't really necessary for me anymore.
cloudstrife7 said:
404 File not found. I'd love to help test this - can someone please re-upload the zip?
Edited 1/16/11
I'm using root explorer so this isn't really necessary for me anymore.
Click to expand...
Click to collapse
I'm a bit confused--PushFile is for pushing files from your Mac to phone (in other words, a computer-side application), while Root Explorer is a file manager for the phone (a phone side app), that, unless I've missed something, does not replicate the functionality that PushFile attempted to provide. Am I missing some cool new feature of Root Explorer that lets you easily transfer files from your Mac to your phone?
There was an application called instantroot that roots HTC hero running 1.5 but until the software was upgraded nothing was done for the instantroot application. Do you have information about that? Is the developer still working on it?
rapsass said:
There was an application called instantroot that roots HTC hero running 1.5 but until the software was upgraded nothing was done for the instantroot application. Do you have information about that? Is the developer still working on it?
Click to expand...
Click to collapse
Not heard of it for a while, but this method at http://forum.xda-developers.com/showthread.php?t=726118 works on 2.1 fine with little issues.
Thanks but I'm still looking for a very easy way to do the root. I don't know why(may be I'm afraid) but I still hesitate to root my hero. I'll think about it again, thank again.
Following that link pulser gave will give the easiest way to root your hero.
Its thanks to that I'm able to root it with no problems whatsoever.
Good Luck!! Don't let yourself stay unrooted!!!
Ok. I'll try later as the villainrom web site is not reachable now.
rapsass said:
Ok. I'll try later as the villainrom web site is not reachable now.
Click to expand...
Click to collapse
Hmm. Are you having trouble too getting onto the site?
Here's the instructions as posted.
Hi all,
I believe I have managed to find a way to root the 2.1 RUU for GSM Hero, completely using the work of wag3slav3 over at XDA (http://forum.xda-developers.com/showthread.php?t=724741), so thanks to him
I took his Droid Eris root and used the correct files for our Hero, and thanks to daentech on IRC, we tested the process and it worked. Here are the conditions used in the test:
1) GSM HTC Hero installed with the 2.1 ROM based on RUU (on this occasion an update.zip was used, as the user involved didn't want to lose root obviously). That zip is unrooted and stock, taken straight from the RUU and converted to update.zip.
2) Booted into ROM, and enabled USB debugging. ADB was installed and set up on this machine, as per this guide - http://www.villainrom.co.uk/viewtopic.php?f=46&t=1735
3) Then downloaded this file: http://www.villainrom.co.uk/uploads/GSMRoot.zip
4) Extract it to a folder on your computer. Open the command prompt using Start > Run > cmd.exe (and press enter)
5) use cd to get into the folder you stored the extracted files.
6) Run the command "runindos.bat"
(If you use linux, put adb in your path folder, and then download this shell script: http://www.villainrom.co.uk/uploads/runinlinuxadb.sh and execute it as normal. Rest will be same as in windows. )
7) Ideally, the phone should sit there for a bit, with some things appearing on screen like
Files copied and permissions set, rebooting HTC Andriod 2.1
Your phone will now reboot into normal mode, then reboot into recovery mode
If it does not reboot the second time, wait 10 minutes and manually reboot and begin again
Your phone is now rebooting in Rooted Recovery mode, do a backup and load yourROMs
Click to expand...
Click to collapse
And it will reboot a couple of times. You will hopefully end up sitting in recovery with a blue 'care bear' in the background
If so, you now have a custom recovery installed. Do a nandroid, and flash a custom ROM like VillainROM 12 or whatever. You should now have root.
8) To further enhance the usefulness of recovery flash VR 12 from here: http://villainrom.co.uk/viewtopic.php?f=95&t=1807 which includes a modified recovery that wipes better than the stock Amon-Ra
If you don't get it to work, please post any errors or details of what happens, and copy and paste your entire command prompt window contents into a
Code:
[/quote] box in the forum window so we can see what's happening.
Hope this works
[size=3]PS. Here are some ROM links for you.
http://villainrom.co.uk/viewtopic.php?f=95&t=1807 - VillainROM 12 (Full Sense 2.1 ROM)
http://www.villainrom.co.uk/viewtopic.php?f=45&t=2844 - FroydVillain 1.1.0 (Vanilla 2.2 Froyo ROM)[/size]
[/quote]
If you can't download the file, get it from http://dl.dropbox.com/u/7618177/GSMRoot.zip
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Oh man thank you. I wonder if I must install ADB to root my phone. I ask this because I still can't reach villainrom web site to check this guide http://www.villainrom.co.uk/viewtopic.php?f=46&t=1735
rapsass said:
Oh man thank you. I wonder if I must install ADB to root my phone. I ask this because I still can't reach villainrom web site to check this guide http://www.villainrom.co.uk/viewtopic.php?f=46&t=1735
Click to expand...
Click to collapse
If you find the user btdag, his signature has the same guide, as he wrote it on both sites. I just use that link as it's easier to find.
pulser_g2 said:
If you find the user btdag, his signature has the same guide, as he wrote it on both sites. I just use that link as it's easier to find.
Click to expand...
Click to collapse
I would love to take credit for that guide but the user ante0 created it (such a simple method I overlooked). Here is it quoted. It is missing pictures but should make enough sense (i hope). It is highly recommended to have the latest HTC Sync installed (link in my sig) for this guide.
Tools needed:
Android SDK (Links below)
HTC Sync (Links below)
Winrar - to extract Android's SDK files.
Patience and time.
1. Getting ADB (Android Debug Bridge)
Okay. You now need to get ADB, which is a part of android's SDK. It can be obtained here http://developer.android.com/sdk/downlo ... indows.zip
or if it's updated when you read this you can go here http://developer.android.com/sdk/index.html and download it. Get the Windows version if you use a windows PC.
Next we need to "install" it. This is done by simply extracting it to your harddrive (Install WinRar, then rightclick on the zip file). I chose C:\android-sdk-windows\. (Actually I chose C:\, the folder in the zip is named android-sdk-windows, so it goes there by default.)
After that is done we are now done with the "installing" part.
2. Setting up environment variables (access adb from outside of \sdk\tools directory.)
Now that we have extracted all files we need to set up environment variables to make our lives easier.
I always do this, because if you don't you need to be in the sdk\tools folder at all times...
Okay, so here we go...
Windows XP:
Rightclick on "My computer" and select "Properties".
click on the "Advanced" tab in the box that appears, looks like the pic below.
Image
Click on the button named "Environment Variables".
Now, doubleclick on the text entry named "Path" in the lower list box.
at the end of it, enter "might\have\other\entries\before\;C:\Path\To\SDK\Tools".
In my "path" it looks like this ";C:\android-sdk-windows\tools\".
(";" is required at the start so windows knows it's a new entry.)
Click on OK to exit out of the dialog, then OK again to get out of My computer's properties.
Now we have it set up.
Windows 7/Vista:
This is similar to Windows XP's setup of environment variables.
Rightclick on "My computer" and select Properties.
In the System window that appears click on "Advanced System settings" located in the left list.
Click on the Advanced tab in the box that appears, then on the "environment variables" button.
Same thing here. Doubleclick on "Path" located in the lower list box.
At the end of it, enter "might\have\other\entries\before\;C:\Path\To\SDK\Tools".
In my "path" it looks like this ";C:\android-sdk-windows\tools\".
(";" is required at the start so windows knows it's a new entry.)
Now click on OK, then OK again to exit.
Alright, all set up!
3. Making sure USB works...
Use this guide: viewtopic.php?f=15&t=379
4. Using ADB
I won't list all commands you can use here. I will only list some examples...
Remember to plug your phone in your usb cable (I've forgotten sometimes... lol)
Start by opening a command prompt.
This is done by opening up the startmenu then click on "Run..." (Alternative way: Windowskey + R).
In the "Run..." box, enter "cmd" without quotes.
If you have some knowledge of using a cmd prompt you don't need to read the next part.
To navigate you mainly use the commands CD and DIR.
Here's an image of what it looks like
Image
C:\Documents and settings\jwork> tells you what your current working folder is.
To get out of it, use the command "cd ..".
This will go back one folder, so your new location will be C:\Documents and settings>
One more "cd .." will take you to C:\.
Now, lets say you have a folder named Images in C:\. To enter it you use "cd Images".
If you want to list all files in that folder, enter the command "dir".
Now you might have a image named image01.jpg in that folder, that you want to get to your phone.
Use the command adb push image01.jpg /sdcard/
It should notify you now if the push was successful.
You can check if the image is on your sdcard by using the command "adb shell ls /sdcard/".
That should conclude this guide...
One more thing, if you just enter "adb" it will show a list of all commands with descriptions.
Click to expand...
Click to collapse
Have you ever heard of Universal Androot? It is only one click away to root your hero2.1.
It's working on my hero.
Universal Androot? Never heard of it. But it looks great and easy. Can I also install another firmware after I root my device with it?
Can I install another firmware like FroydVillain 1.2.2 OTA on my hero after rooted it with this application?
If it installs a custom recovery image then yes you should be able to. If not try installing ClockworkMod and then installing AmonRA - once you have root.
You are the best. Thank you.
Application thread in the Nexus forum. Worked on my Hero 2.1 for instant root.
http://forum.xda-developers.com/showthread.php?t=747598
I've tried this twice already with a factory reset in between each try, and it's worked both times!
Attached is a bunch of files you will need to make this work.
Download the attached Zip file and extrat the contents to your desktop
Mount your G and upload the "G Tablet" folder to your G's internal SD card
Using AndRootFile or any other file manager that supports root access, mount as R/W, and copy the contents of G Tablet\permissions to System\etc\permissions.
Copy the contents of G Tablet\framework to System\Framework
Copy the contents of G Tablet\lib to System\lib
Copy all the APK's found inside G Tablet\APK into your system\app folder.
Install them in this order:
GoogleServicesFramework.apk
OneTimeInitializer.apk
SetupWizard.apk
Talk.apk
Vending.apk
Gmail.apk
Maps.apk
Make sure you remount it as R/O when you're done!
Restart your G, Connect to Wifi, then launch Market.
Follow the standard Google Account setup procedure and enjoy your newly installed Market.
PROOF THAT IT WORKS (the guide might be broken at some point though, see explanation below): http://www.youtube.com/watch?v=3dm2Kax8RQM
Someone please test this and let me know if you have any problems. Factory resetting doesn't delete any files I might have moved into the system folder so I might be missing something in this guide.
Feel free to donate to my beer fund if this helped you
Copying the following over from my thread over at Overclock.net (best computer enthusiast community, ever!)
Guides:
Setting Up ADB:
The ADB drivers do not recognize the Tegra hardware by default. You need to modify the USB inf file in order for it to recognize it and install the proper hardware.
Go to the usb_driver folder inside your Android SDK folder
Open up android_winusb.inf
Add the following under [Google.NTx86] and save (or if you prefer, download my pre-modified android_winusb.inf attached to the bottom of this post, and replace your existing android_winusb.inf with mine).
Code:
;NVIDIA Tegra
%SingleAdbInterface% = USB_Install, USB\VID_0955&PID_7000
%CompositeAdbInterface% = USB_Install, USB\VID_0955&PID_7100&MI_01
If you are running a 64 bit version of Windows, you need to add that code to the [Google.NTamd64] section as well.
Next, open a command prompt and type
Code:
echo 0x955 >> "%USERPROFILE%\.android\adb_usb.ini"
On your G, go to Settings -> Applications -> Development, and check "USB Debugging"
Plug in your USB cable, it will tell you that some drivers were not installed. That's okay! Point it to your usb_driver folder and it'll install the proper drivers.
Make sure ADB is working by opening a command prompt, navigating to your android sdk "tools" folder, and typing
Code:
adb devices
You should see a bunch of numbers if everything is set up correctly.
Click to expand...
Click to collapse
Rooting:
You need to have ADB fully working before proceeding. The easiest way to root is by using CLShortFuse's SuperOneClick. If you can spare the money, consider donating a buck or two to his beer fund
Connect your G and make sure USB debugging is enabled/ADB is working.
Extract the contents of SuperOneClickv1.5.2-ShortFuse.zip to a folder of your choice.
Run SuperOneClick.exe and click on Root. Wait for the process to finish, and you're rooted! Easy as pie.
Click to expand...
Click to collapse
Installing Launcher Pro/ADW:
It's actually really easy.
Download the Launcher Pro APK from here: http://www.launcherpro.com/apk/LauncherPro-0.8.1.1.apk
Connect your G and move the Launcher APK over to your Tablet's internal/external SD card.
Using whatever file manager you prefer (on your G), execute the Launcher Pro APK and install it.
Upon completion, hit the Home button and choose LauncherPro as your default launcher.
Reboot and feel the speed!
Click to expand...
Click to collapse
Fixes:
Wifi Fix:
If your Wifi "errors" upon enabling, try one of the following methods
Method 1:
Reboot. Seriously, it fixes the problem a large portion of the time.
Click to expand...
Click to collapse
Method 2:
Download Wefi from here: http://www.wefi.com/download/android/
Install the APK on your G.
Run WeFi, hit the menu button (button between back and home), and hit Settings
Make sure Automatic Startup is checked. Click on "Wi-Fi on WeFi start" and choose "Always Turn On"
Restart your G and pray.
Click to expand...
Click to collapse
Method 3: Master Reset (you will lose all your apps)
Go to settings -> Security and do a Factory Wipe.
This works only SOMETIMES, but is not a guaranteed fix, so only use this as a last ditch resort
Click to expand...
Click to collapse
nicely done, sir
Awesome job. OCN FTW
Fantastic.. worked like a champ!
Thanks!
Where did you find the USB drivers to mount the device?
Can i also include the contacts, mail, and calendar gapps?
mattmanion said:
Where did you find the USB drivers to mount the device?
Click to expand...
Click to collapse
By mounting I mean connect the USB cable, then under the Notification Icon, Tap "USB Connected, Select to copy files to/from your computer"
insight3fl said:
Can i also include the contacts, mail, and calendar gapps?
Click to expand...
Click to collapse
Go for it, let us know what you find
r34p3rex said:
By mounting I mean connect the USB cable, then under the Notification Icon, Tap "USB Connected, Select to copy files to/from your computer"
Click to expand...
Click to collapse
Do you know if there is a tutorial out there for installing the Root Explorer or Astro file manager on this thing? Sorry, I'm a newbie.
VERY NICE WORK!
FYI I reposted this on the slatedroid.com forum gave you credit and linked back to this thread. If you don't want it on there let me know and I will take it down.
by the way.. All I did to get this working was install the apk's in order and reboot. I do have a problem .. I can't find some apps on the market.. for example winamp doesnt show up..just the winamp 3rd party app.
Anyone else?
Does anyone know why live wallpapers aren't available?
tri0xinn said:
by the way.. All I did to get this working was install the apk's in order and reboot. I do have a problem .. I can't find some apps on the market.. for example winamp doesnt show up..just the winamp 3rd party app.
Anyone else?
Click to expand...
Click to collapse
I will look into that. The most likely reason is the lack of a unique Android ID.
does the regular nullsoft winamp show up for you?
great work man. Just saw the video.
I'm still trying to get adb access. First thing I did was modded the usb files but not the 64bit cuz I didn't see it. Guess I didn't look hard enough. Modded the 32bit one and added the Nvidia tegra info. Then tried adb and the oneclickroot and it didn't work. I then went in and found the amd64 area and added the lines to that portion of the usb.ini file also.
I don't have adb working to root. I'm on Win 7 64bit. any idea's. Then I'll try your guide.
xguntherc said:
great work man. Just saw the video.
I'm still trying to get adb access. First thing I did was modded the usb files but not the 64bit cuz I didn't see it. Guess I didn't look hard enough. Modded the 32bit one and added the Nvidia tegra info. Then tried adb and the oneclickroot and it didn't work. I then went in and found the amd64 area and added the lines to that portion of the usb.ini file also.
I don't have adb working to root. I'm on Win 7 64bit. any idea's. Then I'll try your guide.
Click to expand...
Click to collapse
Gunth you want me to help over Teamviewer?
My files are in place, but the APK files are not "installing" on boot and the tablet sets up normaly and gmail app is not there. I have tried going back in and changing R/O in root explorer, but still not go.. what am I missing? Can these files be pushed to the tablet via adb or do you have to use root explorer? Seems I had the same problem when I did this with my Odroid T.. I tried root explorer but ended up pushing with adb.
Thanks for your work on this
hmmm... it says "install"... I need to launch them from explorer and actualy "install" them? then reboot?
insight3fl said:
My files are in place, but the APK files are not "installing" on boot and the tablet sets up normaly and gmail app is not there. I have tried going back in and changing R/O in root explorer, but still not go.. what am I missing? Can these files be pushed to the tablet via adb or do you have to use root explorer? Seems I had the same problem when I did this with my Odroid T.. I tried root explorer but ended up pushing with adb.
Thanks for your work on this
hmmm... it says "install"... I need to launch them from explorer and actualy "install" them? then reboot?
Click to expand...
Click to collapse
You need to run each APK manually through Root Explorer (or any package installer of your choice). Placing them there does not do anything
xguntherc said:
great work man. Just saw the video.
I'm still trying to get adb access. First thing I did was modded the usb files but not the 64bit cuz I didn't see it. Guess I didn't look hard enough. Modded the 32bit one and added the Nvidia tegra info. Then tried adb and the oneclickroot and it didn't work. I then went in and found the amd64 area and added the lines to that portion of the usb.ini file also.
I don't have adb working to root. I'm on Win 7 64bit. any idea's. Then I'll try your guide.
Click to expand...
Click to collapse
I'm having the same issue Gunth so when you get it working let me know
Just finished up installing the apks. Got a problem though. Now my home and search buttons don't work. Also lost Airplane mode when powering off.
*EDIT* Just watched your video. I don't think that's a finicky button. I think this hack causes the problem.
*EDIT 2* Just did a reset. Home button and search work again. So, it's got to be the hack.
Doc
This is for those on ICS only. If you have upgraded to jellybean, this will not work.
There have been other posts, and this one is nothing new, in fact it's a remake of DebugfsRoot so that author gets all credit. I just made a couple of tweaks to help those that might be having a fuss with it. First, this is assuming you are using a windows PC. I don't work on MACs. Next, make sure you have ADB working properly on your PC. To do this:
Go to your start menu and open a command prompt, usually by typing "cmd" in the run blank.
Type adb
If you don't get a whole heap of feedback of how to use adb returned to you, and instead get an error, you don't have it set right. If you're sure you installed the development kit and you have ADB on your PC, do the following:
FIND IT... and add it to your system path variable. adb.exe comes with the root extract, so if you don't have the kit installed, you can use that instead, but seriously, if you want to root and enjoy this hobby to its fullest, install the android kit. The most common location is "C:\Program Files (x86)\Android\android-sdk-windows\platform-tools" - but hey, get this, did you know the asus sync software available from their site also includes it? I just now found that out haha...
To add whichever absolute path to your system path variable, start menu > control panel > system > advanced system settings > environment variables button > In the system variables window, scroll down to path, click it, click EDIT > move your cursor to the very end and add ; again that's (semi-colon) - you'll see other entries there which show you, just follow the pattern. Remember, you only need to do this if your original attempt at typing adb didn't work. Save your settings, return to that command window, and try adb again, you should have better results this time.
Now then, download the root package here:
https://dl.dropbox.com/u/33560221/DebugfsRoot_v1.8.exe
This is the original software with slight enhancements by me...those enhancements are all to the BAT file, and are as follows:
The EXE file is a self-extracting archive which will extract the contents to C:\tabletroot Please don't change this install location. You'll see why in a moment. the RootDebugfs.bat was edited as follows:
Within each push command, I preceeded the file name with C:\tabletroot so it knows exactly where to find what it needs. I found if you just pushed without it, it didn't like it too much.
Last, after each "wait-for-device" command, I added TIMEOUT 120 This forces the batch file to sleep for 2 minutes allowing plenty of time for your tablet to reboot. I found if you didn't do this, it would try to do the next commands way too soon causing failure. This should give enough time for you to get to your desktop before the next command is issued. If you find it's too long and you're ready to go, just press a key and that will kill the clock. If not long enough, edit the batch file with any text editor, and increase the timeout time.
All other files are what was originally found. I didn't update any of the apks or edit any other file than the main batch file. That's it. I used these exact files to root my tf300t on firmware version .30 with no issue of any kind. I hope this helps someone. If you run into trouble, not sure how much help I can be. I'm simply posting exactly what I did. I didn't author anything other than the edits mentioned above. Good luck.
Did the your_path thing and it didn't work.
Could you describe just a bit more which part you're having trouble with and what happened?
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
I added ;<your_path> at the end of the path and it did not change anything in the CMD window after imputing adb, when nothing happened before.
I'm sure it's something that I did not do that went wrong.
The your path thing was just a descriptor. You need to replace that with the location of your adb.exe file so it would look like ;c:\program files\ ... and so on. I gave a sample path of where mine is but it could vary between systems.
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
Well if my previous answer doesn't prove I've never rooted anything...
Where do you DL the adb file from?
Couple Choices
10010110 said:
Well if my previous answer doesn't prove I've never rooted anything...
Where do you DL the adb file from?
Click to expand...
Click to collapse
OK, I will assume you do not have the android development kit installed, so you still have a couple of choices here:
ADB comes with the archive I directed you to download, so if you download it and run the EXE, you'll find ADB inside the newly created folder I mentioned, so using this method, you would add... ;C:\tabletroot
ADB also comes with the ASUS sync software found on the ASUS website. If you have / will download and install this software, the ADB file will be located here: C:\Program Files (x86)\ASUS\ASUS Sync or it might be in C:\Program Files\ASUS\ASUS Sync just depends on the type of system you have. I have a 64-bit OS, so I have a Program Files and a Program Files (x86) folder (the x86 is for 32-bit programs) - in this situation, you would want to add ;C:\Program Files (x86)\ASUS\ASUS Sync or ;C:\Program Files\ASUS\ASUS Sync
Remember if you go with option one, download the archive I provided and run it before you add / test to your path variable, because that's what puts ADB in place. Once you have that all done, just go run the BAT file - after you connect your tablet and can see it on your PC as a media device that is
Clarification
So using this method do we need the blob files or was that just for downgrading, and since we don't need to downgrade using this method, everything that we need is in that self extracting exe file? I'm not interested to unlock bootloader -for now-...just want a few tweaks and to install a few root apps
Sorry, I only have experience rooting a couple HTC devices and they were both 1 touch and rooted.
I hear you, and they are legit questions. This is for rooting only. This procedure doesn't unlock your bootloader, which is why i used it. All you need is in the archive.
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
Another question, do you have to put the tablet into any special mode in order for the batch file to work? If I remember correctly, the phones just had to be on, plugged in via usb (duh) and the batch files did the rest. The batch file has the 120 second pause, but it seems like it does the first part with -
1. waiting for device to be detected
2. daemon not started
3. daemon started successfully
then it just sits there, and its been longer than 2 minutes...what am I missing?
Only mode i know of is to put it in media mode mentioned above. Also I've read to turn off asus sync found in the sync section of settings.
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
HandicapFailure said:
Another question, do you have to put the tablet into any special mode in order for the batch file to work? If I remember correctly, the phones just had to be on, plugged in via usb (duh) and the batch files did the rest. The batch file has the 120 second pause, but it seems like it does the first part with -
1. waiting for device to be detected
2. daemon not started
3. daemon started successfully
then it just sits there, and its been longer than 2 minutes...what am I missing?
Click to expand...
Click to collapse
Either unknown sources, or USB debugging might need to be on.
Ah yes forgot those. I'd do both thankya.
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
FYI the batch file does not work with windows xp, I searched and seems timeout is not supported. Sucks having an old OS..
I ran the commands manually and the root worked, so thanks anyway!
rickc3k said:
FYI the batch file does not work with windows xp, I searched and seems timeout is not supported. Sucks having an old OS..
I ran the commands manually and the root worked, so thanks anyway!
Click to expand...
Click to collapse
Wow, I didn't know that. Thanks for the tip.
Sent from my ASUS Transformer Pad TF300T using xda app-developers app