Hello everyone this is the first time that slipping but it is much that I read the forum always finding a solution to my problems .. first of all I apologize for my english by the translator .. I ask you my problem. I have a smartphone Brondi Gladiator (a110 Micromax). Using Ubuntu by running the command lsusb I get:
Bus 001 Device 008: ID 0bb4:0c02 HTC (High Tech Computer Corp.) Dream / ADP1 / G1 / Magic / Tattoo (Debug)
Bus 001 Device 003: ID 058f:6362 Alcor Micro Corp. Flash Card Reader/Writer
Bus 003 Device 002: ID 046d:c018 Logitech, Inc. Optical Wheel Mouse
Bus 004 Device 022: ID 04b8:084d Seiko Epson Corp. Stylus SX115
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Click to expand...
Click to collapse
from the terminal command adb devices
List of devices attached
CC8906BF655E7FDA device
Click to expand...
Click to collapse
if you launch the command adb shell and su returns me
/system/bin/sh: su: not found
Click to expand...
Click to collapse
quando lancio RunMe.sh ottengo:
======================================================================
= This script will root your Android phone with adb restore function =
= Script by Bin4ry (thanks to Goroh_kun and tkymgr for the idea) =
= Idea for Tablet S from Fi01_IS01 =
= (13.10.2012) v15 =
= ported to Linux by Kamistral (15.09.2012), =
= updated by codeworkx (01.10.2012) =
======================================================================
Device type:
1) Normal
2) Special (for example: Sony Tablet S, Medion Lifetab)
x) Unroot
Make a choice:
1
Normal mode enabled!
Checking if i should run in Normal Mode or special Sony Mode
Please connect device with ADB-Debugging enabled now ...
./RunMe.sh: riga 60: ./stuff/adb: Permesso negato
./RunMe.sh: riga 62: ./stuff/adb: Permesso negato
./RunMe.sh: riga 70: ./stuff/adb: Permesso negato
Normal Mode enabled!
Please connect device with ADB-Debugging enabled now ...
./RunMe.sh: riga 86: ./stuff/adb: Permesso negato
Pushing busybox ...
./RunMe.sh: riga 91: ./stuff/adb: Permesso negato
Pushing su binary ...
./RunMe.sh: riga 93: ./stuff/adb: Permesso negato
Pushing Superuser app
./RunMe.sh: riga 95: ./stuff/adb: Permesso negato
Pushing ric
./RunMe.sh: riga 97: ./stuff/adb: Permesso negato
Making busybox runable ...
./RunMe.sh: riga 99: ./stuff/adb: Permesso negato
./RunMe.sh: riga 106: ./stuff/adb: Permesso negato
Please look at your device and click RESTORE!
If all is successful i will tell you, if not this shell will run forever.
Running ...
./RunMe.sh: riga 110: ./stuff/adb: Permesso negato
Successful, going to reboot your device!
./RunMe.sh: riga 112: ./stuff/adb: Permesso negato
Waiting for device to show up again ...
connect: Invalid argument
./RunMe.sh: riga 115: ./stuff/adb: Permesso negato
Copying files to it's place ...
./RunMe.sh: riga 149: ./stuff/adb: Permesso negato
You can close all open command-prompts now!
After reboot all is done! Have fun!
Bin4ry
Press key to exit ...
Click to expand...
Click to collapse
please help me to understand where I'm wrong.I apologize if I did something wrong
solved
Hi, i have the same problem.
Can you tell me how you have solved?
Related
So, I'm writing this post so that there is a unified "thing" for G2X and Linux. I just did this on mine, with information from a bunch of different places, so I'd like to make it easier some people (doing it with a guest Windows machine is not fun).
Thanks to jnichols595, and others.
The procedure itself is painless and quick. For me, everything worked from the first time.
1. ROOTING
* download http://forum.xda-developers.com/attachment.php?attachmentid=577906&d=1303754302
* extract it so it is a folder and cd into it with terminal.
* run the following 1 command:
Code:
$ [B]sudo ./root.command[/B]
There appears to be a permissions problem accessing your device
Press Y to try running adb with sudo or any other key to quit: Y
Checking for connected device...
Pushing temporary root exploint (psneuter) to device...
2635 KB/s (585731 bytes in 0.565s)
Running psneuter on device...
property service neutered.
killing adbd. (should restart in a second or two)
Waiting for device...
Remounting /system read/write...
remount succeeded
Pushing su to /system/bin/su...
580 KB/s (26324 bytes in 0.044s)
Pushing busybox to /system/bin/busybox...
1273 KB/s (1062992 bytes in 0.815s)
Installing Superuser.apk android application...
1134 KB/s (196521 bytes in 0.169s)
Removing psneuter from device...
Rebooting device...
Once device has rebooted you should be rooted.
Press Enter when you're ready to quit:
Done, rooted. How do you know? There should be a Pirate's icon in your app menu.
2. INSTALLING CLOCKWORKMOD
* get the nvflash scripts from http://mirror.dal.tdrevolution.net/ctso/g2x/nvflash-recovery.tgz and extract the folder.
* go into the folder and put http://mirrorbrain.cyanogenmod.com/cm/recoveries/recovery-clockwork-3.0.2.7-p999.img in there
* open flash-recovery.sh in that same folder with a text editor and modify the line to say
Code:
sudo ./nvflash --bct E1108_Hynix_512MB_H8TBR00U0MLR-0DM_300MHz_final_emmc_x8.bct --bl fastboot.bin --download 5 recovery-clockwork-3.0.2.7-p999.img
* now open terminal and cd into the folder
* remove the battery on the phone, and plug the cable while holding both VolUp and VolDown keys. Hold like that for 5sec and let go
* in the terminal you opened, execute the commans
Code:
lsusb
to make sure you see something like this:
Code:
Bus 002 Device 008: ID 0955:7f20 NVidia Corp.
* immediately after that, execute the script
Code:
./flash-recovery.sh
this is what I had
Code:
[email protected]:~/Desktop/nvflash$ [B]lsusb[/B]
Bus 003 Device 014: ID 0955:7f20 NVidia Corp.
Bus 003 Device 005: ID 046d:c526 Logitech, Inc. Nano Receiver
Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 002 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 021: ID 0489:e00f Foxconn / Hon Hai
Bus 001 Device 009: ID 064e:2100 Suyin Corp.
Bus 001 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
[email protected]:~/Desktop/nvflash$ [B]./flash-recovery.sh[/B]
Nvflash started
rcm version 0X20001
System Information:
chip name: unknown
chip id: 0x20 major: 1 minor: 3
chip sku: 0xf
chip uid: 0x038891c443c145d7
macrovision: disabled
hdcp: enabled
sbk burned: false
dk burned: false
boot device: emmc
operating mode: 3
device config strap: 0
device config fuse: 0
sdram config strap: 0
downloading bootloader -- load address: 0x108000 entry point: 0x108000
sending file: fastboot.bin
/ 1024992/1024992 bytes sent
fastboot.bin sent successfully
waiting for bootloader to initialize
bootloader downloaded successfully
sending file: recovery-clockwork-3.0.2.7-p999.img
\ 4308992/4308992 bytes sent
recovery-clockwork-3.0.2.7-p999.img sent successfully
[email protected]:~/Desktop/nvflash$
* as soon as some image appears on your phone saying it's updating, you can unplug the phone
Awesome we have the recovery now.
3. Installing the Custom ROM
This one is a video. It is done on a mac, but the computer system does not matter at this point. You just download it to your computer, and then put the zip on the SD card. Use Up/Down to move and Power to select when in recovery mode. This is the guide: http://theunlockr.com/2011/05/03/how-to-load-a-custom-rom-on-the-t-mobile-g2x/
Awesome. Now you can flash ROMs on your device.
***Credits and thanks go to the developers who came up with this, I just put it together!
aplsux said:
So, I'm writing this post so that there is a unified "thing" for G2X and Linux. I just did this on mine, with information from a bunch of different places, so I'd like to make it easier some people (doing it with a guest Windows machine is not fun).
Thanks to jnichols595, and others.
The procedure itself is painless and quick. For me, everything worked from the first time.
1. ROOTING
* download http://forum.xda-developers.com/attachment.php?attachmentid=577906&d=1303754302
* extract it so it is a folder and cd into it with terminal.
* run the following 1 command:
Code:
$ [B]sudo ./root.command[/B]
There appears to be a permissions problem accessing your device
Press Y to try running adb with sudo or any other key to quit: Y
Checking for connected device...
Pushing temporary root exploint (psneuter) to device...
2635 KB/s (585731 bytes in 0.565s)
Running psneuter on device...
property service neutered.
killing adbd. (should restart in a second or two)
Waiting for device...
Remounting /system read/write...
remount succeeded
Pushing su to /system/bin/su...
580 KB/s (26324 bytes in 0.044s)
Pushing busybox to /system/bin/busybox...
1273 KB/s (1062992 bytes in 0.815s)
Installing Superuser.apk android application...
1134 KB/s (196521 bytes in 0.169s)
Removing psneuter from device...
Rebooting device...
Once device has rebooted you should be rooted.
Press Enter when you're ready to quit:
Done, rooted. How do you know? There should be a Pirate's icon in your app menu.
2. INSTALLING CLOCKWORKMOD
* get the nvflash scripts from http://mirror.dal.tdrevolution.net/ctso/g2x/nvflash-recovery.tgz and extract the folder.
* go into the folder and put http://mirrorbrain.cyanogenmod.com/cm/recoveries/recovery-clockwork-3.0.2.7-p999.img in there
* open flash-recovery.sh in that same folder with a text editor and modify the line to say
Code:
sudo ./nvflash --bct E1108_Hynix_512MB_H8TBR00U0MLR-0DM_300MHz_final_emmc_x8.bct --bl fastboot.bin --download 5 recovery-clockwork-3.0.2.7-p999.img
* now open terminal and cd into the folder
* remove the battery on the phone, and plug the cable while holding both VolUp and VolDown keys. Hold like that for 5sec and let go
* in the terminal you opened, execute the commans
Code:
lsusb
to make sure you see something like this:
Code:
Bus 002 Device 008: ID 0955:7f20 NVidia Corp.
* immediately after that, execute the script
Code:
./flash-recovery.sh
this is what I had
Code:
[email protected]:~/Desktop/nvflash$ [B]lsusb[/B]
Bus 003 Device 014: ID 0955:7f20 NVidia Corp.
Bus 003 Device 005: ID 046d:c526 Logitech, Inc. Nano Receiver
Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 002 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 021: ID 0489:e00f Foxconn / Hon Hai
Bus 001 Device 009: ID 064e:2100 Suyin Corp.
Bus 001 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
[email protected]:~/Desktop/nvflash$ [B]./flash-recovery.sh[/B]
Nvflash started
rcm version 0X20001
System Information:
chip name: unknown
chip id: 0x20 major: 1 minor: 3
chip sku: 0xf
chip uid: 0x038891c443c145d7
macrovision: disabled
hdcp: enabled
sbk burned: false
dk burned: false
boot device: emmc
operating mode: 3
device config strap: 0
device config fuse: 0
sdram config strap: 0
downloading bootloader -- load address: 0x108000 entry point: 0x108000
sending file: fastboot.bin
/ 1024992/1024992 bytes sent
fastboot.bin sent successfully
waiting for bootloader to initialize
bootloader downloaded successfully
sending file: recovery-clockwork-3.0.2.7-p999.img
\ 4308992/4308992 bytes sent
recovery-clockwork-3.0.2.7-p999.img sent successfully
[email protected]:~/Desktop/nvflash$
* as soon as some image appears on your phone saying it's updating, you can unplug the phone
Awesome we have the recovery now.
3. Installing the Custom ROM
This one is a video. It is done on a mac, but the computer system does not matter at this point. You just download it to your computer, and then put the zip on the SD card. Use Up/Down to move and Power to select when in recovery mode. This is the guide: http://theunlockr.com/2011/05/03/how-to-load-a-custom-rom-on-the-t-mobile-g2x/
Awesome. Now you can flash ROMs on your device.
***Credits and thanks go to the developers who came up with this, I just put it together!
Click to expand...
Click to collapse
With the G2X as long as you get clockworkmod recovery on your phone you can flash any compatible rom. No need to root first.
And if you do want to root your existing rom, just get clockworkmod on your phone and then flash the root zip file that jboxer has posted in the development section. It issues the commands and installs su and superuser.apk for you, and sets the proper permissions for those files.
phburks said:
With the G2X as long as you get clockworkmod recovery on your phone you can flash any compatible rom. No need to root first.
Click to expand...
Click to collapse
Yes, as long as you are going to a custom ROM. However, if you don't want the whole thing, i.e. just root - easier and quicker.
phburks said:
And if you do want to root your existing rom, just get clockworkmod on your phone and then flash the root zip file that jboxer has posted in the development section. It issues the commands and installs su and superuser.apk for you, and sets the proper permissions for those files.
Click to expand...
Click to collapse
Awesome!
aplsux said:
Yes, as long as you are going to a custom ROM. However, if you don't want the whole thing, i.e. just root - easier and quicker.
Awesome!
Click to expand...
Click to collapse
Notice that that zip doesn't install busybox but it can be easily installed from the Market once you have root access.
Here's a link to the thread.
http://forum.xda-developers.com/showthread.php?t=1255214
Hallo,
i tryed to get root permission on my x10 mini pro using the rooted.sh script.
distro ubuntu 10.04
this is the output...
I also tryed to run the script with sudo user... but it's the same...
any help?
/ROOTer-Linux-v3$ sh ROOTer.sh
ROOTer for Linux by react2409.
Requirements and credits are listed in the README.txt file.
Please make sure requirements are met before continuing.
Remember by using this you understand the risks involved with doing so.
Is your phone already rooted? (y/n)n
Do you wish to continue with the ROOTing? (y/n)y
Is USB Debugging enabled on your phone? (y/n)y
Great lets start the process.
Starting ADB server.
ROOTer.sh: 49: ./adb/adb: Permission denied
Wait for phone to be ready.
ROOTer.sh: 53: ./adb/adb: Permission denied
Push the exploit to the phone.
ROOTer.sh: 57: ./adb/adb: Permission denied
ROOTer.sh: 58: ./adb/adb: Permission denied
Run the exploit. There may be a delay whilst this is happening.
ROOTer.sh: 62: ./adb/adb: Permission denied
ROOTer.sh: 63: ./adb/adb: Permission denied
Mount system as R/W.
ROOTer.sh: 67: ./adb/adb: Permission denied
Push su to phone.
ROOTer.sh: 71: ./adb/adb: Permission denied
Push Superuser.apk to phone.
ROOTer.sh: 73: ./adb/adb: Permission denied
Push busybox to phone.
ROOTer.sh: 75: ./adb/adb: Permission denied
Setting permissions for su.
ROOTer.sh: 79: ./adb/adb: Permission denied
Setting permissions for busybox.
ROOTer.sh: 81: ./adb/adb: Permission denied
Reboot phone.
ROOTer.sh: 85: ./adb/adb: Permission denied
Stopping ADB Server.
ROOTer.sh: 89: ./adb/adb: Permission denied
Your phone should now be ROOTed.
Has anyone found a working root method for the new Tab 10.1 model. It came with 4.0.4.
Sent from my SCH-I915 using xda premium
Also needing root for my sch-i915 any help would be great.
Explore the forums and try root methods for other devices. Just make sure you read read read and know what it's doing. That's what I had to do with the SCH-i705, finally found one that was compatible.
MrHyde03 said:
Explore the forums and try root methods for other devices. Just make sure you read read read and know what it's doing. That's what I had to do with the SCH-i705, finally found one that was compatible.
Click to expand...
Click to collapse
Thanks for the reply, I'll continue searching the forums.
jdn1979 said:
Thanks for the reply, I'll continue searching the forums.
Click to expand...
Click to collapse
Any luck? I too have been searching for this and came up with nothing.
Still no luck here, been searching and searching.
Sent from my unlocked SCH-I605 Running Jelly "beans" rom build 3
Root, or clockworkmod recovery
Any info on either a working root, or even just a working CWM recovery, for this Verizon Galaxy Tab 2 10.1 (a.k.a. SCH-I915) would surely be appreciated...
Has anyone tried making a signed update.zip with all the SU binaries? May not work because of signature check but definitely worth a shot.
Sent from my SCH-I535 using XDA Premium HD app
Hey yall,
I've been looking for an root method that will root the latest base for our vzw tab 2 lte tabs and I found one that works. Best part is, it should work for you! I unrooted my tab (the 7" vzw) with the latest base J1 which currently has no root method other than a prerooted image, and ran this on linux and it rooted it with no problem
Root_with_Restore_by_Bin4ry_v18.7z
Found it from here: http://forum.xda-developers.com/showthread.php?t=1886460
So here's what you do. Download the above zip and extract it.
Enable USB Debugging on your tab
Plug in USB
Go into the extracted folder, right click on 'RunMe.bat' and select 'Run as Administrator'
Select method 1, Normal
Follow the instructions.
Let me know if this worked for yall.
I tried this, both methods, but still no root access???
Sent from my ADR6425LVW using xda premium
What was the output of the script? Copy paste or take a screenshot
Sent from my SCH-I535 using XDA Premium HD app
MrHyde03 said:
What was the output of the script? Copy paste or take a screenshot
Sent from my SCH-I535 using XDA Premium HD app
Click to expand...
Click to collapse
Strange thing is that it removed all of the bloatware, but I dont have root access....
Device type:
1) Normal
2) Special (for example: Sony Tablet S, Medion Lifetab)
x) Unroot
Make a choice: 1
Checking if i should run in Normal Mode or special Sony Mode
Please connect your device with USB-Debugging enabled now
Waiting for device to shop up, if nothing happens please check if Windows ADB-dr
ivers are installed correctly!
remote object '/system/app/Backup-Restore.apk' does not exist
remote object '/system/bin/ric' does not exist
.
Pushing busybox....
2950 KB/s (1085140 bytes in 0.359s)
Pushing su binary ....
2876 KB/s (91980 bytes in 0.031s)
Pushing Superuser app
2710 KB/s (996704 bytes in 0.359s)
Making busybox runable ...
.
Please look at your device and click RESTORE!
If all is successful i will tell you, if not this shell will run forever.
Running ...
Successful, going to reboot your device in 10 seconds!
Waiting for device to show up again....
Going to copy files to it's place
mount: permission denied (are you root?)
You can close all open command-prompts now!
After reboot all is done! Have fun!
Bin4ry
Press any key to continue . . .
It seems like it should have worked. Did the device ever ask you to press the "Restore" button after unlocking the screen?
Yeah.
Sent from my ADR6425LVW using xda premium
The only thing that I noted was the failure to change the mount state, then the line asking are you root?
Sent from my ADR6425LVW using xda premium
Do you have access to a linux box you could run this on? Put the adb binary from the android sdk in your path so you can run it from anywhere. It gave me permissions problems at first but after doing the below it worked like a charm.
This is what I did on mine:
After extracing the contents of the downloaded package.
chmod 777 -R directory name
to give the entire directory permissions
I then opened up RunMe.sh and did a search replace
Search: ./stuff/adb
Replace With: adb
From Terminal:
sudo adb kill-server
sudo adb start-server (to start server as administrator)
Then from within the directory
chmod a+x RunMe.sh
To make it executable, then
./RunMe.sh
Thought it might work different on Windows running as admin, but maybe not.
Unfortunately, I don't have access to linux. I wonder if terminal emulator would work?
Sent from my SCH-I915 using XDA Premium HD app
I've been out of town for a while but just took a look through the forum and didn't see anything new regarding this. Does anyone know if there is a dev even working on the VZW Tab 2? I pm'd Codeworkx and Weltwon but unfortunately neither are doing anything with this device.
Sent from my SCH-I915 using Tapatalk HD
I got this same thing but mine doesn't seem to have removed any bloatware nor did it root successfully. No superuser
List of devices attached
501a1acd device
C:\Users\===\Downloads\Android Tab 2 10.1\Root With Restore>runme
======================================================================
= This script will root your Android phone with adb restore function =
= Script by Bin4ry (thanks to Goroh_kun and tkymgr for the idea) =
= Idea for Tablet S from Fi01_IS01 =
= (18.12.2012) v17 =
======================================================================
Device type:
1) Normal
2) Special (for example: Sony Tablet S, Medion Lifetab)
x) Unroot
Make a choice: 1
Checking if i should run in Normal Mode or special Sony Mode
Please connect your device with USB-Debugging enabled now
Waiting for device to shop up, if nothing happens please check if Windows ADB-dr
ivers are installed correctly!
remote object '/system/app/Backup-Restore.apk' does not exist
remote object '/system/bin/ric' does not exist
.
.
Normal Mode enabled!
.
Pushing busybox....
3567 KB/s (1085140 bytes in 0.297s)
Pushing su binary ....
2897 KB/s (91980 bytes in 0.031s)
Pushing Superuser app
4364 KB/s (996704 bytes in 0.223s)
Making busybox runable ...
.
Please look at your device and click RESTORE!
If all is successful i will tell you, if not this shell will run forever.
Running ...
Successful, going to reboot your device in 10 seconds!
Waiting for device to show up again....
Going to copy files to it's place
mount: permission denied (are you root?)
You can close all open command-prompts now!
After reboot all is done! Have fun!
Bin4ry
Press any key to continue . . .
-----------------------------------------------------------------------
Tried using number 2 instead of 1 for tablets and then it reset my phone to factory settings and I lost everything. The terminal window came up but crashed so I could never finish it.
======================================================================
= This script will root your Android phone with adb restore function =
= Script by Bin4ry (thanks to Goroh_kun and tkymgr for the idea) =
= Idea for Tablet S from Fi01_IS01 =
= (18.12.2012) v17 =
======================================================================
Device type:
1) Normal
2) Special (for example: Sony Tablet S, Medion Lifetab)
x) Unroot
Make a choice: 2
Special mode:
1) Root
2) Rollback
Make a choice: 1
Tablet S mode enabled!
2870 KB/s (314540 bytes in 0.107s)
pkg: /sdcard/tmp/Term.apk
Failure [INSTALL_FAILED_INSUFFICIENT_STORAGE]
4547 KB/s (1085140 bytes in 0.233s)
3454 KB/s (91980 bytes in 0.026s)
3672 KB/s (996704 bytes in 0.265s)
3374 KB/s (469980 bytes in 0.136s)
mkdevsh
onload.sh
onload2.sh
packages.xml.sed
remount.sh
VpnFaker.apk
_su
Please look at your device and click "Restore my data"
1st RESTORE OK, hit ENTER to continue.
Press any key to continue . . .
rm failed for /data/data/com.android.settings/a, Permission denied
Please look at your device and click "Restore my data"
Achieved! hit ENTER to continue.
Press any key to continue . . .
cp: can't stat '/data/system/sensors/settings': Permission denied
cp: can't open '/data/system/usagestats/usage-20130301': Permission denied
cp: can't open '/data/system/users/userlist.xml': Permission denied
cp: can't open '/data/system/users/0.xml': Permission denied
cp: can't open '/data/system/registered_services/android.accounts.AccountAuthent
icator.xml': Permission denied
cp: can't open '/data/system/registered_services/android.content.SyncAdapter.xml
': Permission denied
cp: can't open '/data/system/sync/accounts.xml': Permission denied
cp: can't open '/data/system/sync/status.bin': Permission denied
cp: can't open '/data/system/sync/pending.bin': Permission denied
cp: can't open '/data/system/sync/stats.bin': Permission denied
cp: can't open '/data/system/inputmethod/subtypes.xml': Permission denied
cp: can't open '/data/system/dropbox/[email protected]': Per
mission denied
cp: can't open '/data/system/dropbox/[email protected]': Permission
denied
cp: can't open '/data/system/dropbox/[email protected]': Permi
ssion denied
cp: can't open '/data/system/dropbox/[email protected]': Per
mission denied
cp: can't open '/data/system/dropbox/[email protected]': Per
mission denied
cp: can't open '/data/system/dropbox/[email protected]': Per
mission denied
cp: can't open '/data/system/dropbox/[email protected]': Per
mission denied
cp: can't open '/data/system/dropbox/[email protected]': Per
mission denied
cp: can't open '/data/system/dropbox/[email protected]': Per
mission denied
cp: can't open '/data/system/dropbox/[email protected]': Per
mission denied
cp: can't open '/data/system/dropbox/[email protected]': Per
mission denied
cp: can't open '/data/system/dropbox/[email protected]': Permission de
nied
cp: can't open '/data/system/dropbox/[email protected]': Per
mission denied
cp: can't open '/data/system/dropbox/[email protected]': Per
mission denied
cp: can't open '/data/system/dropbox/[email protected]': Permis
sion denied
cp: can't open '/data/system/dropbox/[email protected]': Permis
sion denied
cp: can't open '/data/system/dropbox/[email protected]': Permis
sion denied
cp: can't open '/data/system/dropbox/[email protected]': Permission de
nied
cp: can't open '/data/system/dropbox/[email protected]': Permission d
enied
cp: can't open '/data/system/dropbox/[email protected]': Permis
sion denied
cp: can't open '/data/system/dropbox/[email protected]': Permis
sion denied
cp: can't open '/data/system/dropbox/[email protected]': Permission
denied
cp: can't open '/data/system/dropbox/[email protected]': Permission de
nied
cp: can't open '/data/system/dropbox/[email protected]': Permission
denied
cp: can't open '/data/system/throttle/temp': Permission denied
cp: can't open '/data/system/throttle/1293543142': Permission denied
cp: can't open '/data/system/databases/drmdatabase.db': Permission denied
cp: can't open '/data/system/shared_prefs/log_files.xml': Permission denied
cp: can't open '/data/system/entropy.dat': Permission denied
cp: can't open '/data/system/batterystats.bin': Permission denied
cp: can't open '/data/system/accounts.db': Permission denied
cp: can't open '/data/system/accounts.db-journal': Permission denied
cp: can't open '/data/system/enterprise.db': Permission denied
cp: can't open '/data/system/dmappmgr.db': Permission denied
cp: can't open '/data/system/dmappmgr.db-journal': Permission denied
cp: can't open '/data/system/wifioffload.db': Permission denied
cp: can't open '/data/system/wifioffload.db-journal': Permission denied
cp: can't open '/data/system/called_pre_boots.dat': Permission denied
cp: can't open '/data/system/wallpaper_info.xml': Permission denied
cp: can't open '/data/system/appwidgets.xml': Permission denied
cp: can't open '/data/system/netpolicy.xml': Permission denied
failed on '/data/system' - Permission denied
failed on '/data/system2' - Permission denied
failed on '/data/app' - Permission denied
mkdir failed for /data/app, File exists
failed on '/data/local/tmp/VpnFaker.apk' - Permission denied
/system/bin/sh: cannot create /data/system/packages.xml: Permission denied
Need to reboot now!
Waiting for device to come up again....
Unlock your device, a Terminal will show now, type this 2 lines, after each line
press ENTER
/data/local/tmp/onload.sh
/data/local/tmp/onload2.sh
after this is done press a key here in this shell to continue!
If the shell on your device does not show please re-start the process!
Starting: Intent { cmp=com.android.vpndialogs/.Term }
Press any key to continue . . .
302 KB/s (1241 bytes in 0.004s)
/data/local/tmp/script1.sh[1]: /dev/sh: not found
/data/local/tmp/script1.sh[2]: /dev/sh: not found
/data/local/tmp/script1.sh[3]: /dev/sh: not found
/data/local/tmp/script1.sh[4]: /dev/sh: not found
/data/local/tmp/script1.sh[5]: /dev/sh: not found
/data/local/tmp/script1.sh[6]: /dev/sh: not found
/data/local/tmp/script1.sh[7]: /dev/sh: not found
/data/local/tmp/script1.sh[8]: /dev/sh: not found
/data/local/tmp/script1.sh[9]: /dev/sh: not found
/data/local/tmp/script1.sh[10]: /dev/sh: not found
/data/local/tmp/script1.sh[11]: /dev/sh: not found
/data/local/tmp/script1.sh[12]: /dev/sh: not found
/data/local/tmp/script1.sh[13]: /dev/sh: not found
/data/local/tmp/script1.sh[14]: /dev/sh: not found
/data/local/tmp/script1.sh[15]: /dev/sh: not found
/data/local/tmp/script1.sh[16]: /dev/sh: not found
/data/local/tmp/script1.sh[17]: /dev/sh: not found
/data/local/tmp/script1.sh[18]: /dev/sh: not found
/data/local/tmp/script1.sh[19]: /dev/sh: not found
Almost complete! Reboot and cleanup.
Waiting for device to come up again....
/system/bin/sh: su: not found
/system/bin/sh: su: not found
/system/bin/sh: su: not found
You can close all open command-prompts now!
After reboot all is done! Have fun!
Bin4ry
Press any key to continue . . .
Edit 2: I did the roll back for step 2, and then after doing a soft reset, all my data had come back. Thank God.
This doesn't work with SCH-i915 apparently =(
Well, let's hope that with the upgrade to 4.1.2 we will see some movement toward getting rooted. I never thought it would take this long to get. I love having a tablet with 4G connection so I don't have to tether my phone constantly, but it's disappointing not having root.
Dear XDA member,
I am new to rooting. My problem is that after I have install adb in Linux Mint 14 64bit system. The Sony Xperia Tipo Dual is still not rooted after following the instruction as per attach link. May I know which part is wrong? The phone details as below
Sony Tipo Dual
Android 4.0.4
Baseband Version
7x25_AM:2045.40.00.80.001.008_A:
2045.40.00.80.002.038
Kernel Version 3.0.perf
[email protected] # 1
Build No 11.0.A.6.8
Install adb drive for linux as per the link below. Terminal output as below confirming adb is install correct and device is detected.
http://androidonlinux.wordpress.com/2013/05/12/setting-up-adb-on-linux/
[email protected] ~/Desktop $ lsusb
Bus 002 Device 002: ID 0fce:6170 Sony Ericsson Mobile Communications AB
Bus 003 Device 002: ID 0518:0001 EzKEY Corp. USB to PS2 Adaptor v1.09
Bus 003 Device 003: ID 15d9:0a4d Trust International B.V. Optical Mouse
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 005 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 006 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 007 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 008 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
[email protected] ~/Desktop $
[email protected] ~/Desktop $ cd Android/sdk/platform-tools/
[email protected] ~/Desktop/Android/sdk/platform-tools $ ./adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
YT9004SVE4 device
[email protected] ~/Desktop/Android/sdk/platform-tools $
# ANDROID 3RD PARTY USB VENDOR ID LIST -- DO NOT EDIT.
# USE 'android update adb' TO GENERATE.
# 1 USB VENDOR ID PER LINE.
Ox0fce
Following below link to root Sony Xperia Tipo Dual
http://forum.xda-developers.com/showthread.php?t=1886460
[email protected] ~ $ cd Desktop
[email protected] ~/Desktop $ sh ./RunMe.sh
==================================================================================================
= This script will root your Android phone with adb restore function =
= Script by Bin4ry(converted to shell by jamcswain) (thanks to Goroh_kun and tkymgr for the idea) =
= Idea for Tablet S from Fi01_IS01 =
= (20.11.2013) v32 =
===================================================================================================
Device type:
0) Xperia Z1 14.1.G.1.534 Root by cubeundcube
1) Normal
2) Special (for example: Sony Tablet S, Medion Lifetab)
3) New Xperia Root by Goroh_kun
G) Google Glass Root (thx to Saurik for the ab file)
x) Unroot
Make a choice:
Please enter a valid number(1 to x):
1
Checking if I should run in Normal Mode or special Sony Mode
Please connect your device with USB-Debugging enabled now
Waiting for device to shop up, if nothing happens please check if Windows ADB-drivers are installed correctly!
./RunMe.sh: 39: ./RunMe.sh: ./stuff/adb: Permission denied
./RunMe.sh: 40: ./RunMe.sh: ./stuff/adb: Permission denied
./RunMe.sh: 41: ./RunMe.sh: ./stuff/adb: Permission denied
Normal Mode enabled!
./RunMe.sh: 196: ./RunMe.sh: ./stuff/adb: Permission denied
Pushing busybox....
./RunMe.sh: 201: ./RunMe.sh: ./stuff/adb: Permission denied
Pushing su binary ....
./RunMe.sh: 203: ./RunMe.sh: ./stuff/adb: Permission denied
Pushing Superuser app
./RunMe.sh: 205: ./RunMe.sh: ./stuff/adb: Permission denied
Making busybox runable ...
./RunMe.sh: 207: ./RunMe.sh: ./stuff/adb: Permission denied
./RunMe.sh: 216: ./RunMe.sh: ./stuff/adb: Permission denied
Please look at your device and click RESTORE!
If all is successful I will tell you, if not this shell will run forever.
Running ...
./RunMe.sh: 220: ./RunMe.sh: ./stuff/adb: Permission denied
Successful, going to reboot your device in 10 seconds!
./RunMe.sh: 223: ./RunMe.sh: ./stuff/adb: Permission denied
Waiting for device to show up again....
./RunMe.sh: 226: ./RunMe.sh: ./stuff/adb: Permission denied
Going to copy files to it's place
./RunMe.sh: 258: ./RunMe.sh: ./stuff/adb: Permission denied
You can close all open command-prompts now!
After reboot all is done! Have fun!
Bin4ry
./RunMe.sh: 191: read: Illegal option -n
[email protected] ~/Desktop $ ^C
[email protected] ~/Desktop $
Sony Tipo Dual not rooted after running the program.
May I know which part is wrong.
Thank you for help given
JQ
Dear XDA member,
Is there anyone can help out on the Sony Tipo Dual rooting?
blablabla
maybe you can use an virtual machine for linux, i dunno if there is an virtual machine for linux mint, bc I am using ubuntu, if you can download an virtual machine, like virtualbox, then you can use a windows OS , search for the program called "UnlockRoot" something like that, to root your xperia tipo dual ST21i2, that's the program I used to root my xperia st21i2, gud luck
gian20 said:
maybe you can use an virtual machine for linux, i dunno if there is an virtual machine for linux mint, bc I am using ubuntu, if you can download an virtual machine, like virtualbox, then you can use a windows OS , search for the program called "UnlockRoot" something like that, to root your xperia tipo dual ST21i2, that's the program I used to root my xperia st21i2, gud luck
Click to expand...
Click to collapse
Hi,
Thank you for your reply. Does that mean rooting is easier to be done on window machine than in linux?
Yes...rooting is easier in windows..
Sent from my C1604 using xda app-developers app
re
GJQ said:
Hi,
Thank you for your reply. Does that mean rooting is easier to be done on window machine than in linux?
Click to expand...
Click to collapse
yes , I think so
Today I just bought a A450 Android Smartphone ACCENT because I want to work with on a project.
Why ACCENT A450:
ACCENT is a Moroccan brand
ACCENT is sponsoring the event SFD Casablanca
ACCENT A450: not a bad configuration
So the first thing I should do is to connect the smartphone and have access via ADB, but I have not found a driver for it either in the official website or in the web is why I created a Windows via Linux.
Download 51-android.rules Linux ACCENT A450
Download Windows driver for ACCENT A450
Steps with which I have created this driver:
I- Linux:
1- Before connecting our Smartphone:
Code:
@ ws ws-Pro: ~ $ lsusb
Bus 002 Device 003: ID 1bcf: 2805 Sunplus Innovation Technology Inc.
Bus 002 Device 002: ID 8087: 0024 Intel Corp. Integrated Rate Matching Hub
Bus 002 Device 001: ID 1d6b: 0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b: 0003 Linux Foundation 3.0 root hub
Bus 003 Device 001: ID 1d6b: 0002 Linux Foundation 2.0 root hub
Bus 001 Device 003: ID 138a: 003C Validity Sensors, Inc. VFS471 Fingerprint Reader
Bus 001 Device 002: ID 8087: 0024 Intel Corp. Integrated Rate Matching Hub
Bus 001 Device 001: ID 1d6b: 0002 Linux Foundation 2.0 root hub
2-I connected my Smartphone:
Code:
@ ws ws-Pro: ~ $ lsusb
Bus 002 Device 003: ID 1bcf: 2805 Sunplus Innovation Technology Inc.
Bus 002 Device 005: ID 24e3: 9025
Bus 002 Device 002: ID 8087: 0024 Intel Corp. Integrated Rate Matching Hub
Bus 002 Device 001: ID 1d6b: 0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b: 0003 Linux Foundation 3.0 root hub
Bus 003 Device 001: ID 1d6b: 0002 Linux Foundation 2.0 root hub
Bus 001 Device 003: ID 138a: 003C Validity Sensors, Inc. VFS471 Fingerprint Reader
Bus 001 Device 002: ID 8087: 0024 Intel Corp. Integrated Rate Matching Hub
Bus 001 Device 001: ID 1d6b: 0002 Linux Foundation 2.0 root hub
NB:
Bus 002 Device 005: ID 24e3: 9025
This is our "idVendor = 24e3" and "idProduct = 9025"
3- I created with a 51-right root file android.rules
Code:
@ ws ws-Pro: ~ $ sudo gedit -w /etc/udev/rules.d/51-android.rules
4- I added this line; that contains our idVendor:
Code:
SUBSYSTEM == "usb", ATTR {idVendor} == "24e3", MODE = "0666", GROUP = "plugdev"
5- I restarted the service:
Code:
sudo restart udev Service
6- I unplugged and then plugged in again (my Smartphone):
Code:
@ ws ws-Pro: ~ $ adb devices
* Daemon not running. starting it now on 5037 port *
* Daemon started successfully *
List of devices attached
8888888 offline
7- A message appears on our smartphone, we have to accept and voila:
Code:
@ ws ws-Pro: ~ $ adb devices
List of devices attached
8888888 device
II- Windows:
1- I downloaded USB_Driver Google:
See: http://developer.android.com/sdk/win-usb.html
2- Then I added our idVendor and idProduct:
Code:
;Accent A450
%SingleAdbInterface% = USB_Install, USB\VID_24e3&PID_9025
%CompositeAdbInterface% = USB_Install, USB\VID_24e3&PID_9025&MI_01
3- To install is easy:
Download the file and then manually install (video demonstration of a manual installation: https://www.youtube.com/watch?v=6IEdJZGQVI4 )
Enjoy
s2dar said:
...
Click to expand...
Click to collapse
Good tutorial but it doesn't work!
A friend of mine own an Accent A500 which lacks drivers.
He wants me to root it for him. We tried your method but Windows failed installing drivers.
Nonta72 said:
Good tutorial but it doesn't work!
A friend of mine own an Accent A500 which lacks drivers.
He wants me to root it for him. We tried your method but Windows failed installing drivers.
Click to expand...
Click to collapse
I think it should work if you make small changes because it is not the same device see Technical Specifications.
A question:
When you connect your A500 Focus on Ubuntu and you run the command "lsusb" What is new line as you see
s2dar said:
I think it should work if you make small changes because it is not the same device see Technical Specifications.
A question:
When you connect your A500 Focus on Ubuntu and you run the command "lsusb" What is new line as you see
Click to expand...
Click to collapse
I'm not on Ubuntu atm.
But lemme try it there.
Here's the screenshot.
Anyways, I got it rooted using Kingo Root App but I'd still love getting the drivers working.
Nonta72 said:
Here's the screenshot.
Anyways, I got it rooted using Kingo Root App but I'd still love getting the drivers working.
Click to expand...
Click to collapse
can you try that ?
Linux:
$ sudo gedit -w /etc/udev/rules.d/51-android.rules
Code:
SUBSYSTEM == "usb", ATTR {idVendor} == "0a5c", MODE = "0666", GROUP = "plugdev"
$ sudo restart udev Service
$ adb devices
Windows :
Download Driver A500 Windows
s2dar said:
can you try that ?
Linux:
$ sudo gedit -w /etc/udev/rules.d/51-android.rules
Code:
SUBSYSTEM == "usb", ATTR {idVendor} == "0a5c", MODE = "0666", GROUP = "plugdev"
$ sudo restart udev Service
$ adb devices
Windows :
Download Driver A500 Windows
Click to expand...
Click to collapse
Thanks,
But error is still persistant on Windows LOL