i searched and cant seem to find anything on my problem....i connect via mass storage mode , it detects the phone, but for some reason it doesnt let me access the files on the card....in other words ,i cant open them...any help ????
try opening the sd card with root access.
Open the terminal and type:
Code:
sudo nautilus /media/
Then just select one of your sd cards.
If this works to access them then you need to change the permissions to allow ubuntu to access them with read and write without root.
I am using it just fine on Ubuntu 10.4
I connect my phone and it is mounted automagically, and I can move the files from/to the phone.
Do you have se_linux installed?
It also works just fine for me. It may have to do with permissions on the folders when mounted. From a cli you may try running this command with the phone not connected:
sudo chown -R user:user /media
Just replace "user" with your username.
Then connect the phone and see what happens.
thanks, I'll give this a try, let you guys know tomorrow...
Gotta say it works on Ubuntu better then does on Windows XP. You may have some permissions fudged somewhere. Do as the guys above said and let us know.
the3dman said:
try opening the sd card with root access.
Open the terminal and type:
Code:
sudo nautilus /media/
Then just select one of your sd cards.
If this works to access them then you need to change the permissions to allow ubuntu to access them with read and write without root.
Click to expand...
Click to collapse
this is not working for me
aksoutherland said:
It also works just fine for me. It may have to do with permissions on the folders when mounted. From a cli you may try running this command with the phone not connected:
sudo chown -R user:user /media
Just replace "user" with your username.
Then connect the phone and see what happens.
Click to expand...
Click to collapse
nothign when i enter command
In the phone's USB settings what do you have it set to?
Run
tail -f /var/log/messages
while connecting your phone, and when connected
ls -ltra /media
Post here and we will take a closer look
lqaddict said:
In the phone's USB settings what do you have it set to?
Run
tail -f /var/log/messages
while connecting your phone, and when connected
ls -ltra /media
Post here and we will take a closer look
Click to expand...
Click to collapse
nothing again.....i have it set to ask on connection, then i swithced to mass storage mode....... what else should i do?
error message : "could not display" "the file location is not a folder "
Install android-sdk for linux, enable USB debugging under Development settings, try connecting with adb
Code:
/path/to/android-sdk/tools/adb shell
It will drop you to $ prompt
Post here the output of
mount -a
Use
Code:
tags.
lqaddict said:
Install android-sdk for linux, enable USB debugging under Development settings, try connecting with adb
Code:
/path/to/android-sdk/tools/adb shell
It will drop you to $ prompt
Post here the output of
mount -a
Use
Code:
tags.[/QUOTE]
thanks, I appreciate the help, I will give this a try in the morning
Click to expand...
Click to collapse
Related
Update 1: Thank you all the members for making this thread more simpler.
I will do some more edits as instructed by others to make it more understandable.
As we all know it, this guide is no more "easiest".
First of all, thank you to all the members for the Pre-Rooted ROM's, Tutorials, Ideas etc.
I have just made it simpler for the newbies to understand what the devs are doing to get a rooted-Eclair phone.
It has been discussed many times that the current guides are very difficult for newbies to understand.
So I will tell you step-by-step how to do the stuff.
Though it needs many downloads, bit of thinking, but in the end you will be successful!
Make sure to put the phone in USB Debugging Mode everytime.
For that go to -Settings>Applications>Development>USB Debugging(Tick the option)
And maximize the Screen Timeout Limit.
Settings>Sound & Display>Screen Timeout(Set it to 30 minutes).
Update: Many people don't know what "Flashmode" is,
For this you need to unplug the phone from PC, take out phone battery for 5-10 seconds, after that put the battery back, keep holding the Back button and plug the phone back(the notification light will turn Green).
First of all Flash Android 1.6 Link and Root it Link.
Download the files required-
(1) Download the latest Firmware files by propc.
Link 1
Link 2
(2) Download newx8rooted.yaffs.7z Link
(3) Extract newx8rooted.unyaffs.7z to the root of your sdcard(there should be 3 files- (i) newx8rooted.yaffs.img
(ii) busybox
(iii) unyaffs)
(4) Download install.sh.zip(see the attachments)
How to get in the ADB Shell-
(1) First of all we need the ADB files. I have put the files in the folder. See the attachments please.
(2) Extract the files and save them in C: drive.
(3) Now open cmd(Command Prompt).
(4) Type-
cd C:\android
Click to expand...
Click to collapse
Hit Enter.
(5) Now type-
adb shell
Click to expand...
Click to collapse
(6) Remember you must be having Rooted Android 1.6 and 4 files(install.sh, newx8rooted.yaffs.img, busybox, unyaffs) in your SD card at this stage.
After this step the command prompt should be something like this-
C:\android>adb shell
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
$
Click to expand...
Click to collapse
(7) Now type-
su
Click to expand...
Click to collapse
**NOW HAVE A LOOK AT PHONE SCREEN, SUPERUSER MUST BE ASKING FOR PERMISSION, CLICK ON "Allow".(And yes, maximize the Screen timeout time for no spoilling.)**
**NOW THERE SHOULD BE A "#" SIGN IN COMMAND PROMPT.
Sometimes the command takes some time to execute so you need to wait for the "#" prompt before typing next command.**
(8) Now type
cd /sdcard
Click to expand...
Click to collapse
(9) Now type
sh install.sh
Click to expand...
Click to collapse
Update: Many people are facing the problem saying-
# sh install.sh
sh install.sh
sh: Can't open install.sh
#
Click to expand...
Click to collapse
For this, you need to take care of few things.
First of all that you don't miss any commands.
Secondly you must have the drivers installed on your PC. If you don't have please see the attachments, and install it via Device Manager.
Thirdly, make sure that the phone is in USB Debugging Mode.
The phone storage should be turned off.
Sometimes if the error repeats itself, it is always advisable to either Restart both PC and device, or try it on another PC.
There should be a lot of line scrolling, Now sit for sometime and relax!
After all this, it should say-
Reboot phone!
Flash 2.1 now, but remove system.sin
Click to expand...
Click to collapse
Now just Flash Android 2.1 Flasher by Bin4ry works well! and REMEMBER TO REMOVE "system.sin" from the folder of the firmware!!!
Sit back and relax!!
Now just reboot the phone(1st Reboot will take 5-10 mins.).
And you are done!
Hope that I am helpful!
Edit:Many people don't know what "Root of SD Card is"
This means that the files should be on your SD Card directly, do not put these files in any Folder, simply paste them in you SD Card.
Any suggestions and queries are welcomed.
Update 2:
Guys it is really very difficult to know exactly what the problem is. Because it is working for many and not for few, it is hard to know the
exact mistake.
So I advice you people to please repeat the process again, or try it on another PC, if you dont mind that, I am not a pro, I am here just to sort out few problems.
I am sorry but i really ain't able to get solution for random problems.
Can any other "Senior" help this out?
Special Thanks to-
propc
Bin4ry
a-k-t-w
pullpoff2
You can always appreciate my work by just clicking "Thanks"!
Cheers!
you don't need the Android SDK. ADB shell is already in superoneclick.
thanks for instruction
Botoxopfer said:
you don't need the Android SDK. ADB shell is already in superoneclick.
Click to expand...
Click to collapse
I didn't noticed that!!
God! I need to edit it!!
mohakrastogi said:
I didn't noticed that!!
God! I need to edit it!!
Click to expand...
Click to collapse
Also change it to , Copy and paste the three adb files into the /system32 folder, that way adb shell can be accessed without cding, (makes it even simpler )
timk1764 said:
Also change it to , Copy and paste the three adb files into the /system32 folder, that way adb shell can be accessed without cding, (makes it even simpler )
Click to expand...
Click to collapse
Thank you for the suggestion!
Now that you've put the "$" sign after adb shell, you can also put the "#" sign after su, so they will know when to type again. Sometimes the command takes some time to execute so tell them you need to wait for the "#" prompt before typing next command.
Special thanks for this, it's done.
Now i have rooted 2.1 and Gingerbread Theme.
What I'm doing wrong ?
# sh install.sh
sh install.sh
sh: Can't open install.sh
#
Arkaeris said:
What I'm doing wrong ?
# sh install.sh
sh install.sh
sh: Can't open install.sh
#
Click to expand...
Click to collapse
Code:
cd /sdcard
sh install.sh
and make sure your sdcard is not mounted. turn off usb storage on your PC
This guide is great...
But after the last step, flashing 2.1 without system.sin.. My X8 is stuck on "Sony Ericsson" without the logo...
"turn off usb storage on your PC"
sorry, but how to do that ?
Arkaeris said:
"turn off usb storage on your PC"
sorry, but how to do that ?
Click to expand...
Click to collapse
ops, turn off USB storage on your phone. drag down the status bar, press Turn off USB storage. press turn off
I have unmount sd card, I have turn off usb storage but..
C:\android>adb shell
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
error: device not found
C:\android>
Arkaeris said:
I have unmount sd card, I have turn off usb storage but..
C:\android>adb shell
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
error: device not found
C:\android>
Click to expand...
Click to collapse
Install Update Service and PC companion. or download X8 driver at http://developer.sonyericsson.com/
propc said:
Install Update Service and PC companion. or download X8 driver at http://developer.sonyericsson.com/
Click to expand...
Click to collapse
okey I have install update service and reinstall pc companion and download x8 drivers.
C:\android>adb shell
$ su
su
# cd /sdcard
cd /sdcard
# sh install.sh
sh install.sh
sh: Can't open install.sh
#
I don't understand where I go wrong.....
Arkaeris said:
okey I have install update service and reinstall pc companion and download x8 drivers.
C:\android>adb shell
$ su
su
# cd /sdcard
cd /sdcard
# sh install.sh
sh install.sh
sh: Can't open install.sh
#
I don't understand where I go wrong.....
Click to expand...
Click to collapse
check that you had turn off USB storage, check that you copied the files to the root of your sdcard
propc said:
check that you had turn off USB storage, check that you copied the files to the root of your sdcard
Click to expand...
Click to collapse
what does it mean "to the root of your sdcard" ?
is folder name or something like that ?
Maybe my computer has some windows problems ?
Root of SD-Card means that u only put it into the sdcard into no folder. Just click on the sdcard and copy the file in it.
[email protected] said:
Root of SD-Card means that u only put it into the sdcard into no folder. Just click on the sdcard and copy the file in it.
Click to expand...
Click to collapse
I'm doing just you said but.. It still Can't open install.sh
Hello there,
i m new on xda and (sorry for it) completely noob.
i just got a European HOX+ and i would like to mount usb storage just like older phones, MTB is realy disapointing me on any OS (XP, Debian)
i already have unlocked my bootloader, will it possible to remove the MTP to mount a classical usb storage ?
thx to all
Th!baut said:
Hello there,
i m new on xda and (sorry for it) completely noob.
i just got a European HOX+ and i would like to mount usb storage just like older phones, MTB is realy disapointing me on any OS (XP, Debian)
i already have unlocked my bootloader, will it possible to remove the MTP to mount a classical usb storage ?
thx to all
Click to expand...
Click to collapse
no, it's MTP or nothing, also questions > Q&A
Lloir said:
no, it's MTP or nothing, also questions > Q&A
Click to expand...
Click to collapse
Ok, so i wont be able tu acces my data on a Linux PC ?, some people are talking about a "mount usb storage" option in a CWM Recovery, what does it do ?
all this is really disapointing
Th!baut said:
Ok, so i wont be able tu acces my data on a Linux PC ?, some people are talking about a "mount usb storage" option in a CWM Recovery, what does it do ?
all this is really disapointing
Click to expand...
Click to collapse
yes you can:
- Install MTP and its tools:
sudo apt-get install mtpfs mtp-tools
- Create a mountpoint:
sudo mkdir -p -m 777 /mnt/hox
- Plugin your hox
- Mount the device manually:
mtpfs /mnt/hox
- Open your favourite file manager, go to /mnt/hox and transfer files from/to the device
- When finished, don't forget to dismount the device:
sudo umount /mnt/hox
you might also need libmtp
Lloir said:
yes you can:
- Install MTP and its tools:
sudo apt-get install mtpfs mtp-tools
- Create a mountpoint:
sudo mkdir -p -m 777 /mnt/hox
- Plugin your hox
- Mount the device manually:
mtpfs /mnt/hox
- Open your favourite file manager, go to /mnt/hox and transfer files from/to the device
- When finished, don't forget to dismount the device:
sudo umount /mnt/hox
you might also need libmtp
Click to expand...
Click to collapse
Okay thanks, i did what you said but when i mount /mnt/hox the dirrectory disapers, and it reapears when i unmount...
tell me if i am doing it wrong but, i must mount /mnt/hox and copy my files into it ?
Th!baut said:
Okay thanks, i did what you said but when i mount /mnt/hox the dirrectory disapers, and it reapears when i unmount...
tell me if i am doing it wrong but, i must mount /mnt/hox and copy my files into it ?
Click to expand...
Click to collapse
you might have to google for debian specific help, look for help on the galaxy nexus as that's well documented and has MTP
Hi,
Did a search and someone said they were able to root with thecubed method on Mac via Terminal, but I've had no luck so far. Are there any other options for us Mac users?
Thanks
BTW I did see some instructions but it only applies to Verizon. I have the international version D802.
Any help would be greatly appreciated.
use virtual machine and use windows?
I haven't found any easy way to do it, other that running bootcamp and windows on the mac..
You can do it via adb just fine on osx (I'm on snow leopard). You can check which commands to run by opening the Windows script as a text document. It's easy to follow what's going on and has sections for each device
xdabbeb said:
You can do it via adb just fine on osx (I'm on snow leopard). You can check which commands to run by opening the Windows script as a text document. It's easy to follow what's going on and has sections for each device
Click to expand...
Click to collapse
I opened root.bat as a text file but as far as how to input the commands I'm not sure what to do as it seems to differs from the video. Sorry I'm not that familiar working with Terminal.
If you could help out that would be great.
Thanks
xdabbeb said:
You can do it via adb just fine on osx (I'm on snow leopard). You can check which commands to run by opening the Windows script as a text document. It's easy to follow what's going on and has sections for each device
Click to expand...
Click to collapse
Ahhhhh! You know Mavericks is free, right? UPGRADE THAT THING!
On another note... same issue w/ me. I ended up rooting it via my PC, but after that you can use Android File Transfer to manage files and load roms and stuff via OSX.
sell ur POS apple and get a pc...?
digitard said:
Ahhhhh! You know Mavericks is free, right? UPGRADE THAT THING!
On another note... same issue w/ me. I ended up rooting it via my PC, but after that you can use Android File Transfer to manage files and load roms and stuff via OSX.
Click to expand...
Click to collapse
Ha! I haven't upgraded because I still feel snow leopard is the best. I don't like how they've integrated so much ios in the last two, and SL is lean/efficient.
If I have some time I'll write down the commands in a reply. Do you have adb already set up?
xdabbeb said:
Ha! I haven't upgraded because I still feel snow leopard is the best. I don't like how they've integrated so much ios in the last two, and SL is lean/efficient.
If I have some time I'll write down the commands in a reply. Do you have adb already set up?
Click to expand...
Click to collapse
Yes already have adb set up. Thanks for this. Really appreciate it.
No problem. What version of the G2 do you have?
---------- Post added at 11:49 PM ---------- Previous post was at 11:48 PM ----------
Ignore that, I just saw you mentioned the international version
OK, here you go:
1) Go here here and here and thank them both for their work...and read their disclaimers about breaking your phone. The same applies here.
2) Download the attached archive and extract the contents into whatever folder you want...for the purposes of this I'll assume you did so to a directory called ~/D802_OSXroot. If you chose a different directory, modify the steps below accordingly. The archive I attached only contains the appropriate file for the international (D802) LG G2, and I used Chainfire's SuperSU instead of the older ChainsDD su binary and apk. While you're at it, go here and thank him.
3) Make sure USB Debugging is enabled on your phone in Settings>Developer Options
4) Connect your phone via usb cable. You'll get the popup asking what type of connection on your phone. Select Internet connection and then Ethernet when asked. You should see the debugging icon in the status bar of your phone
5) Open terminal on your mac
6) To verify that you are properly connected run the following command:
Code:
adb shell "ls -a /"
you should see the contents of the root of your phone...inlcuding a number of init files. If you do, proceed. If you don't, you have an adb/connection problem.
7) Execute the following in the terminal window to go to the directory where the archive has been extracted on your mac:
Code:
cd ~/D802_OSXroot
8) Execute the following to push the loki exploit file to your phone
Code:
adb push ./g2_security /sdcard/g2_security
9) Unplug your usb cable from the phone
10) On your phone go to Settings>Developer Options and disable USB Debugging
11) Re-enable USB Debugging
12) Plug in your USB cable (follow step 4)
13) Verify adb connectivity (follow step 6)
14) Go back to your terminal window, make sure you are still in the same directory with the files from the archive and execute the following commands in order:
Code:
adb shell "mount -o remount,rw /system"
Code:
adb push ./su /system/xbin/su
Code:
adb shell "chown 0.0 /system/xbin/su;chmod 06755 /system/xbin/su;sync;mount -o remount,ro /system"
Code:
adb install superuser.apk
15) Launch the SuperSU app on your phone. It will likely prompt you to update the su binary...let it do so and then reboot your phone. You should be rooted now.
Good luck!
xdabbeb said:
OK, here you go:
1) Go here here and here and thank them both for their work...and read their disclaimers about breaking your phone. The same applies here.
2) Download the attached archive and extract the contents into whatever folder you want...for the purposes of this I'll assume you did so to a directory called ~/D802_OSXroot. If you chose a different directory, modify the steps below accordingly. The archive I attached only contains the appropriate file for the international (D802) LG G2, and I used Chainfire's SuperSU instead of the older ChainsDD su binary and apk. While you're at it, go here and thank him.
3) Make sure USB Debugging is enabled on your phone in Settings>Developer Options
4) Connect your phone via usb cable. You'll get the popup asking what type of connection on your phone. Select Internet connection and then Ethernet when asked. You should see the debugging icon in the status bar of your phone
5) Open terminal on your mac
6) To verify that you are properly connected run the following command:
Code:
adb shell "ls -a /"
you should see the contents of the root of your phone...inlcuding a number of init files. If you do, proceed. If you don't, you have an adb/connection problem.
7) Execute the following in the terminal window to go to the directory where the archive has been extracted on your mac:
Code:
cd ~/D802_OSXroot
8) Execute the following to push the loki exploit file to your phone
Code:
adb push ./g2_security /sdcard/g2_security
9) Unplug your usb cable from the phone
10) On your phone go to Settings>Developer Options and disable USB Debugging
11) Re-enable USB Debugging
12) Plug in your USB cable (follow step 4)
13) Verify adb connectivity (follow step 6)
14) Go back to your terminal window, make sure you are still in the same directory with the files from the archive and execute the following commands in order:
Code:
adb shell "mount -o remount,rw /system"
Code:
adb push ./su /system/xbin/su
Code:
adb shell "chown 0.0 /system/xbin/su;chmod 06755 /system/xbin/su;sync;mount -o remount,ro /system"
Code:
adb install superuser.apk
15) Launch the SuperSU app on your phone. It will likely prompt you to update the su binary...let it do so and then reboot your phone. You should be rooted now.
Good luck!
Click to expand...
Click to collapse
Has anyone tried this method?
Sent from my LG-D802 using Tapatalk
xdabbeb said:
OK, here you go:
1) Go here here and here and thank them both for their work...and read their disclaimers about breaking your phone. The same applies here.
2) Download the attached archive and extract the contents into whatever folder you want...for the purposes of this I'll assume you did so to a directory called ~/D802_OSXroot. If you chose a different directory, modify the steps below accordingly. The archive I attached only contains the appropriate file for the international (D802) LG G2, and I used Chainfire's SuperSU instead of the older ChainsDD su binary and apk. While you're at it, go here and thank him.
3) Make sure USB Debugging is enabled on your phone in Settings>Developer Options
4) Connect your phone via usb cable. You'll get the popup asking what type of connection on your phone. Select Internet connection and then Ethernet when asked. You should see the debugging icon in the status bar of your phone
5) Open terminal on your mac
6) To verify that you are properly connected run the following command:
Code:
adb shell "ls -a /"
you should see the contents of the root of your phone...inlcuding a number of init files. If you do, proceed. If you don't, you have an adb/connection problem.
7) Execute the following in the terminal window to go to the directory where the archive has been extracted on your mac:
Code:
cd ~/D802_OSXroot
8) Execute the following to push the loki exploit file to your phone
Code:
adb push ./g2_security /sdcard/g2_security
9) Unplug your usb cable from the phone
10) On your phone go to Settings>Developer Options and disable USB Debugging
11) Re-enable USB Debugging
12) Plug in your USB cable (follow step 4)
13) Verify adb connectivity (follow step 6)
14) Go back to your terminal window, make sure you are still in the same directory with the files from the archive and execute the following commands in order:
Code:
adb shell "mount -o remount,rw /system"
Code:
adb push ./su /system/xbin/su
Code:
adb shell "chown 0.0 /system/xbin/su;chmod 06755 /system/xbin/su;sync;mount -o remount,ro /system"
Code:
adb install superuser.apk
15) Launch the SuperSU app on your phone. It will likely prompt you to update the su binary...let it do so and then reboot your phone. You should be rooted now.
Good luck!
Click to expand...
Click to collapse
Thanks for this. I'm having an issue at the first step. I have tested adb when I downloaded the SDK and if I direct the command ./adb devices to that specific folder it can read my phone, but just going into terminal and entering adb shell "ls -a /" al I get is -bash: adb: command not found
Also when I connect my phone to the mac I get options on the G2 but none are internet then ethernet. I get: Charge Phone, Media Sync, Tethering, LG Software, Send Images. The Mac does not ask me what connection I want.
ck37 said:
Thanks for this. I'm having an issue at the first step. I have tested adb when I downloaded the SDK and if I direct the command ./adb devices to that specific folder it can read my phone, but just going into terminal and entering adb shell "ls -a /" al I get is -bash: adb: command not found
Also when I connect my phone to the mac I get options on the G2 but none are internet then ethernet. I get: Charge Phone, Media Sync, Tethering, LG Software, Send Images. The Mac does not ask me what connection I want.
Click to expand...
Click to collapse
It sounds like the first issue may just be due to you not having adb set up properly. If you execute "echo $PATH" in terminal and don't see the android/tools and android/platform-tools directories there, that's the problem. You can either set your path variable to include those directories or just edit the commands I listed accordingly.
The second issue may be due to a difference in the D802 rom vs the VS980. The important thing is that USB Debugging is enabled and that you can access your phone via adb. The 802 may not prompt you in the same way, but if you fix your adb setup the commands will work the same. The rooting method listed (which is the same as thecubed method) is predicated on that working properly.
xdabbeb said:
It sounds like the first issue may just be due to you not having adb set up properly. If you execute "echo $PATH" in terminal and don't see the android/tools and android/platform-tools directories there, that's the problem. You can either set your path variable to include those directories or just edit the commands I listed accordingly.
The second issue may be due to a difference in the D802 rom vs the VS980. The important thing is that USB Debugging is enabled and that you can access your phone via adb. The 802 may not prompt you in the same way, but if you fix your adb setup the commands will work the same. The rooting method listed (which is the same as thecubed method) is predicated on that working properly.
Click to expand...
Click to collapse
I think I figured it out. What I did was transfer the ADB icon from my SDK folder into this one. From there I was able to get access to adb inside the D802 folder. I did have to enter the ./adb as opposed to adb though.
As for the LG I selected tethering as that seemed to be the option similar to the internet/ ethernet choice you mentioned.
All other commands worked accordingly.
Binaries updated for SuperUser as well. At this point how do I get into recovery to upload ROMS etc?
ck37 said:
I think I figured it out. What I did was transfer the ADB icon from my SDK folder into this one. From there I was able to get access to adb inside the D802 folder. I did have to enter the ./adb as opposed to adb though.
As for the LG I selected tethering as that seemed to be the option similar to the internet/ ethernet choice you mentioned.
All other commands worked accordingly.
Binaries updated for SuperUser as well. At this point how do I get into recovery to upload ROMS etc?
Click to expand...
Click to collapse
What I did was installed flashify from the market. This app allows you to backup and then flash a new recovery. Make sure you dl the right one for your device!
Sent from my LG-VS980 using Tapatalk
Has anyone had a successful root on a plt7602g. I have tried a couple different methods.
Rooting the PLT7602G
sallanm said:
Has anyone had a successful root on a plt7602g. I have tried a couple different methods.
Click to expand...
Click to collapse
Here is a procedure to root the Curtis Proscan PLT7602G tablet (Build number PLT7602G-ANDROID4.2.2-v1.0.0).
1. Install adb on your computer and enable adb on the tablet. http://developer.android.com/tools/help/adb.html
2. Enable ADB on the tablet:
Settings > About Tablet > tap build number 7 times until it says "You are now a developer!"
Developer options > switch On > OK
Check "USB Debugging" > OK
3. Connect USB and wait for ADB drivers to load on the PC. Using the Google drivers installed with ADB, your system may need manual help to find the right drivers: Go into Windows device manager > Update Driver Software > browse My Computer for driver software > 'Let me pick from a list of devices drivers...' > Pick Android ADB Interface from the model list.
4. You will see a notification "USB Debugging Connected" on the tablet.
5. If this is the first time, you will next see a dialog on the tablet asking "Allow USB debugging?" Check "Always allow from this computer" and click OK.
6. At the command prompt on the computer enter "adb devices". You should see the device listed. If not, reboot the PC and repeat steps 1 through 5 as necessary to get everything working together.
C:\Users\entropy>adb devices
List of devices attached
CD1LBROR50 device
C:\Users\entropy>7. Download pwn.zip here: http://forum.xda-developers.com/showpost.php?p=53407127
8. Unzip "pwn" from the zip file to your windows current directory
9. At the command prompt on the computer enter the following sequence of commands:
C:\Users\entropy> adb push pwn /data/local/tmp/pwn
C:\Users\entropy> adb shell chmod 755 /data/local/tmp/pwn
C:\Users\entropy> adb shell /data/local/tmp/pwn
Beaups and jcase were here
donations may go here, pleaes say what it was for -> [email protected]
10. After a few seconds, you should hear the USB disconnect sound, followed by the USB connection sound again.
11. At the command prompt, enter “adb devices” and ensure the device is listed as before. If not, wait a few seconds and then repeat this step.
C:\Users\entropy> adb devices
12. At the command prompt, enter:
C:\Users\entropy> adb shell
7. At the shell prompt, enter "su". You should now have a root prompt.
[email protected]:/ $ su
[email protected]:/ #
8. Exit back out to the command prompt:
[email protected]:/ # exit
[email protected]:/ $ exit
C:\Users\entropy>
9. On the tablet, go to the play store, download and install the latest SuperSU, or use the Google Play link in this thread: http://forum.xda-developers.com/show....php?t=1538053
10. Open the SuperSU that you just installed. SuperSU will prompt you to install a newer su binary when you run it, so click “Continue” do that, then “Normal”, then “OK”.
11. Reboot the tablet.
The tablet should now be fully rooted. Please let me know if you find any errors or if anything is unclear. I hope you find this useful!
I've downloaded the "Unrevoked" USB driver but the device is not being installed...
Marco Dufal said:
I've downloaded the "Unrevoked" USB driver but the device is not being installed...
Click to expand...
Click to collapse
It has been a while since I got this working and I honestly don't remember exactly what I did to make it work.
Try this... install the official Google driver and reboot:
http://developer.android.com/sdk/win-usb.html
If i still doesn't work, download the adb_usb.ini from here and replace the adb_usb.ini in c:\users\<yourusername>\.android\adb_usb.ini with this one, then reboot and try again. I verified that this adb_usb.ini contains the necessary device ID, so that should definitely do the trick.
https://github.com/apkudo/adbusbini
If you get it working, please post here so others can benefit.
Sice I had already installed the official Google drivers I proceeded with the adb_usb.ini method, but even after rebooting my pc it didn't work... What worked for me was:
Going into window device manager -> Update Driver Software -> browse my computer for driver software -> 'let me pick from a list of devices drivers...' -> Picked Android ADB Interface (from the model list).
I don't get why it did't install it automatically since the driver is actually compatible; did the same thing with another device (Sony experia E1). I got two of them, the first one got recognized while I had to do this process for the second one... Maybe it's my pc fault..
Anyway thank you very much for your replies and the guide. Am I risking to brick the device by following it ?
P.S.
For those who have android studio installed, to run the guide prompt commands you can set an environment variable called 'adb' with this value 'C:\Users\{USERNAME}\AppData\Local\Android\sdk\platform-tools\adb.exe' and easily replacing 'adb' with '%adb%' .
For example : 'C:\Users\{any directory}>%adb% devices'
Marco Dufal said:
Sice I had already installed the official Google drivers I proceeded with the adb_usb.ini method, but even after rebooting my pc it didn't work... What worked for me was:
Going into window device manager -> Update Driver Software -> browse my computer for driver software -> 'let me pick from a list of devices drivers...' -> Picked Android ADB Interface (from the model list).
I don't get why it did't install it automatically since the driver is actually compatible; did the same thing with another device (Sony experia E1). I got two of them, the first one got recognized while I had to do this process for the second one... Maybe it's my pc fault..
Anyway thank you very much for your replies and the guide. Am I risking to brick the device by following it ?
P.S.
For those who have android studio installed, to run the guide prompt commands you can set an environment variable called 'adb' with this value 'C:\Users\{USERNAME}\AppData\Local\Android\sdk\platform-tools\adb.exe' and easily replacing 'adb' with '%adb%' .
For example : 'C:\Users\{any directory}>%adb% devices'
Click to expand...
Click to collapse
I'm glad you got ADB working. Thanks for the additional tips, I'm sure they will be useful to others.
I don't think there is any significant risk of bricking unless you make a horrible mistake, like deleting everything in /system instead of shifting the new file into place. Anything else, like accidentally picking the wrong su binary to install, should be easily recoverable by just rebooting if necessary and then trying again.
maximumentropy said:
I'm glad you got ADB working. Thanks for the additional tips, I'm sure they will be useful to others.
I don't think there is any significant risk of bricking unless you make a horrible mistake, like deleting everything in /system instead of shifting the new file into place. Anything else, like accidentally picking the wrong su binary to install, should be easily recoverable by just rebooting if necessary and then trying again.
Click to expand...
Click to collapse
Quick info. I am rooting because of the low storage. Currently this is my storage situation :
total 4GB
Firmware 2.04GB
---------------------
Total space 1.96GB
197MB Available
232MB Apps
few KB Cached data & Misc.
There must be something wrong... Anyway my question is. Should I flash a custom rom to free some of the firmware allocated memory ? How is the external card going to be used (can I install app on it) ?
EDIT
I get
`su: not found`
Marco Dufal said:
Quick info. I am rooting because of the low storage. Currently this is my storage situation :
total 4GB
Firmware 2.04GB
---------------------
Total space 1.96GB
197MB Available
232MB Apps
few KB Cached data & Misc.
There must be something wrong... Anyway my question is. Should I flash a custom rom to free some of the firmware allocated memory ? How is the external card going to be used (can I install app on it) ?
Click to expand...
Click to collapse
I haven't found any custom ROMs for this tablet. If you know of some, please speak up. You could try reflashing the original ROM but that might be overkill. You can use an app like DiskUsage to help you identify what's eating the most space.
Marco Dufal said:
EDIT
I get
`su: not found`
Click to expand...
Click to collapse
I can't help you if you give me an error message but no hint of what you entered that caused the message.
maximumentropy said:
I haven't found any custom ROMs for this tablet. If you know of some, please speak up. You could try reflashing the original ROM but that might be overkill. You can use an app like DiskUsage to help you identify what's eating the most space.
Click to expand...
Click to collapse
Thanks I will check it up.
maximumentropy said:
I can't help you if you give me an error message but no hint of what you entered that caused the message.
Click to expand...
Click to collapse
C:\Users\Marco\AppData\Local\Android\sdk\platform-tools>adb shell
[email protected]:/ $ su
su
/system/bin/sh: su: not found
127|[email protected]:/ $
Marco Dufal said:
Thanks I will check it up.
C:\Users\Marco\AppData\Local\Android\sdk\platform-tools>adb shell
[email protected]:/ $ su
su
/system/bin/sh: su: not found
127|[email protected]:/ $
Click to expand...
Click to collapse
Please try entering it with full path:
[email protected]:/ $ /system/xbin/su
maximumentropy said:
Please try entering it with full path:
[email protected]:/ $ /system/xbin/su
Click to expand...
Click to collapse
Still negative result :
[email protected]:/ $ /system/xbin/su
/system/xbin/su
/system/bin/sh: /system/xbin/su: not found
127|[email protected]:/ $ ls /system/xbin/
ls /system/xbin/
dexdump
io
[email protected]:/ $
Marco Dufal said:
Still negative result :
Click to expand...
Click to collapse
What is your build number in Settings > About Tablet?
maximumentropy said:
What is your build number in Settings > About Tablet?
Click to expand...
Click to collapse
PLT7602G-ANDROID4.2.2-v1.0.0
Marco Dufal said:
PLT7602G-ANDROID4.2.2-v1.0.0
Click to expand...
Click to collapse
Well, I apologize for being an idiot. That's what I get for trying to document a root procedure I did last year, from memory. I have several similar cheap tablets and I misremembered this one as being pre-rooted as I described.
I just re-flashed from stock and re-rooted it. Fortunately, I had left enough breadcrumbs on my computer that I was able to reconstruct the right procedure.
I will do another full run-through within the next few days as soon as I have some time, to make sure I have everything 100% straight, and will clean this up to update the OP. Meanwhile, if you're feeling brave, here's the notes I took as I did it:
Settings > About Tablet > tap build number until it says you are a developer
Developer options > switch On > OK
USB Debugging > OK
Connect USB
see "USB Debugging Connected" notification
Wait for "Allow USB debugging?" dialog, check "Always allow from this computer" and click OK
adb devices
Download pwn.zip here: http://forum.xda-developers.com/showpost.php?p=53407127
Unzip "pwn" from the zip file to your windows current directory
adb push pwn /data/local/tmp/pwn
adb shell chmod 755 /data/local/tmp/pwn
adb shell /data/local/tmp/pwn
Hear USB disconnect sound
Wait about 1 minute (may or may not need to disconnect and reconnect USB cable)
adb wait-for-device
adb shell
su (should give a root shell)
exit
Install SuperSU from Play Store
Run it
The SU binary needs to be updated. Continue?
Continue > Normal > OK
Reboot
Don't worry it's ok.. Anyway I am not felling brave at all so I think that I will wait for now...
Marco Dufal said:
Don't worry it's ok.. Anyway I am not felling brave at all so I think that I will wait for now...
Click to expand...
Click to collapse
No guts, no glory!
I updated the instructions in post #2 and did another trial run through. Give it a shot at let me know if you run into any trouble. You already have ADB functioning, so you can just skip to step 6 and go from there.
http://forum.xda-developers.com/showpost.php?p=59530490&postcount=2
maximumentropy said:
No guts, no glory!
Click to expand...
Click to collapse
Just did it and every thing worked ! It was fast and clear... Now I wonder, how many devices can I root with the same procedure ?
Marco Dufal said:
Just did it and every thing worked ! It was fast and clear... Now I wonder, how many devices can I root with the same procedure ?
Click to expand...
Click to collapse
Great, I'm glad it worked for you!
The pwn exploit will work with many JellyBean devices. Many of the cheap Chinese tablets don't even need it though, as they will either give you a root prompt immediately when you connect using ADB, or after entering "su" to ADB. The trick then is just to use that access to install an "su" from SuperSU or another full SU package, so that you get full root from the user interface as well as from ADB. You could still use the pwn method on such a device, but I personally prefer to use the least invasive method to get the required access.
maximumentropy said:
Great, I'm glad it worked for you!
The pwn exploit will work with many JellyBean devices. Many of the cheap Chinese tablets don't even need it though, as they will either give you a root prompt immediately when you connect using ADB, or after entering "su" to ADB. The trick then is just to use that access to install an "su" from SuperSU or another full SU package, so that you get full root from the user interface as well as from ADB. You could still use the pwn method on such a device, but I personally prefer to use the least invasive method to get the required access.
Click to expand...
Click to collapse
Sorry if this is a newb question but can this be done if your microusb port is broken? I can get the file on the tablet via sd card but I can't seem to perform the steps with Terminal Emulator like I had hoped. This is using the same ProScan PLT7602G as in the OP.
Thanks
Ian1331 said:
Sorry if this is a newb question but can this be done if your microusb port is broken? I can get the file on the tablet via sd card but I can't seem to perform the steps with Terminal Emulator like I had hoped. This is using the same ProScan PLT7602G as in the OP.
Thanks
Click to expand...
Click to collapse
I don't think it will work in a terminal emulator because you need to run with uid 2000 (shell) for permission on the /data/local/tmp directory.
I was experiencing the wifi+bluetooth ship failure that I fixed once, twice, ..., but the fix didn't last
My last attemp to fix that resulted in a flex cable ribbon damage (bad move)
Power button and touch screen are now broken
Sounds like it's time to change phone :crying: I'm not willing to repair this time
I'm trying to access internal storage but I am stuck:
I can:
- access bootloader options (buy plug-in power or usb cable)
- go into recovery, but I can't validate my selection (no power button)
- go into fastboot, but it seems that mounting is not a fastboot possibility
- go into rom (fastboot reboot), but I need to touch screen to activate usb mount
Any idea ?
cailloup said:
I was experiencing the wifi+bluetooth ship failure that I fixed once, twice, ..., but the fix didn't last
My last attemp to fix that resulted in a flex cable ribbon damage (bad move)
Power button and touch screen are now broken
Sounds like it's time to change phone :crying: I'm not willing to repair this time
I'm trying to access internal storage but I am stuck:
I can:
- access bootloader options (buy plug-in power or usb cable)
- go into recovery, but I can't validate my selection (no power button)
- go into fastboot, but it seems that mounting is not a fastboot possibility
- go into rom (fastboot reboot), but I need to touch screen to activate usb mount
Any idea ?
Click to expand...
Click to collapse
Try this http://droid-at-screen.ribomation.com/installation/
Use a desktop window to access your phone. A long time back when my screen went off, i used this to access my phone.
guruzen said:
Try this http://droid-at-screen.ribomation.com/installation/
Use a desktop window to access your phone. A long time back when my screen went off, i used this to access my phone.
Click to expand...
Click to collapse
Thanks, one problem: USB debugging is not activated (what a noob I am not to have USB debugging check lol)
Do you have a custom recovery? If so, you should be able to access the shell through adb and USB while in recovery.
cailloup said:
Thanks, one problem: USB debugging is not activated (what a noob I am not to have USB debugging check lol)
Click to expand...
Click to collapse
If ravilov method works, write an android program that registers for onBootReceiver. In onReceive() have this code
Settings.Secure.putInt(context.getContentResolver(), Settings.Secure.ADB_ENABLED, 1)
Put the apk under /system/app and change the permission to rw-r-r
Restart your phone, the above app must run onBoot and u will have usb debugging enabled.
Lets see how things go.
ravilov said:
Do you have a custom recovery? If so, you should be able to access the shell through adb and USB while in recovery.
Click to expand...
Click to collapse
I have big part recovery V3 from Zn7mkUKzN1r8aCIV
So accessing shell would let me mount storage ?
How do I use adb from recovery ?
guruzen said:
If ravilov method works, write an android program that registers for onBootReceiver. In onReceive() have this code
Settings.Secure.putInt(context.getContentResolver(), Settings.Secure.ADB_ENABLED, 1)
Put the apk under /system/app and change the permission to rw-r-r
Restart your phone, the above app must run onBoot and u will have usb debugging enabled.
Lets see how things go.
Click to expand...
Click to collapse
So I won't be able to mount storage from shell, but I can write lines that will enable usb debugging so that I can use your first post ?
I
cailloup said:
I have big part recovery V3 from Zn7mkUKzN1r8aCIV
So accessing shell would let me mount storage ?
How do I use adb from recovery ?
So I won't be able to mount storage from shell, but I can write lines that will enable usb debugging so that I can use your first post ?
I
Click to expand...
Click to collapse
Looks like u cannot mount sdcard. I found something about adb enabling in init.rc that u can retrieve. Put your phone in recovery and connect to the system and do adb shell
You must be in # prompt. Pull out init.rc using the command "adb pull /init.rc ."
I am attaching my init.rc. diff it and you should find differences wrt to adb. Try replacing the adb differences and ensure the chmod is done for init.rc (initial permissions)
guruzen said:
Looks like u cannot mount sdcard. I found something about adb enabling in init.rc that u can retrieve. Put your phone in recovery and connect to the system and do adb shell
You must be in # prompt. Pull out init.rc using the command "adb pull /init.rc ."
I am attaching my init.rc. diff it and you should find differences wrt to adb. Try replacing the adb differences and ensure the chmod is done for init.rc (initial permissions)
Click to expand...
Click to collapse
adb device is ok
I got the init.rc with adb pull, it is exactly the same as yours
I tried adb pull emmc
pull sdcard
pull scard0
pull scard1
pull storage
etc
Some don't work, some work but I got only files from "sys" folder
I tried this
http://forum.xda-developers.com/showthread.php?t=2339530
Same folder issue
I tried adb shell su mount but I don't know what to do with it ^^
Since our init.rc are similar, I also tried [email protected] but I have nothing in the device list (while phone is on)
If you enabled root for adb inside the rom, you can use the following command in adb to mount the internal storage:
echo /dev/block/vold/179:97 > /sys/devices/virtual/android_usb/android0/f_mass_storage/lun0/file
That will mount internal storage as usb storage and you will be able to access the files from a computer.
Edit: I just read that you don't have it enabled >.< Another way would be to use "input tap x y" which does not require root but as you don't have it enable, something has to be done through recovery.
Second edit: Try this inside recovery:
adb shell
mkdir sdcard0
mount /dev/block/mmcblk0p18 sdcard0
Now that the internal storage is mounted on sdcard0, exit adb shell and use the following command:
adb pull /sdcard0 sdcard
This should copy all the files from the internal storage to a new folder called sdcard in your computer.
Reiki21 said:
Second edit: Try this inside recovery:
adb shell
mkdir sdcard0
mount /dev/block/mmcblk0p18 sdcard0
Now that the internal storage is mounted on sdcard0, exit adb shell and use the following command:
adb pull /sdcard0 sdcard
This should copy all the files from the internal storage to a new folder called sdcard in your computer.
Click to expand...
Click to collapse
Yeah that worked!
currently pulling everything, it's going to be long
Thanks all for help
Problem solved