[Q] Why second adb.exe starts when i begin rooting process - Xperia Arc Q&A, Help & Troubleshooting

Hello guys,
I am new here not too familiar with all this stuff but i can handle them, the last two days i am trying to root my phone with doomlord's tool kit but no luck, i have tried everything but in the command window it stuck in the first commands
"--- STARTING ----
--- WAITING FOR DEVICE
* daemon not running. starting it now *
* daemon started successfully *"
Then in i go and see my running programms i see 2 adb.exe if i delete the one who "works" the most i get the error, "error: More than one device or emulator" and if i delete the other .exe(A little observation: i think that 2nd adb.exe it's not stable it stops and it beggins again and again) i get the error "error: Device offiline" Despite my phone's build number says .587 it's .562
Do you have any idea what is wrong?
Thanks in advance.

your phone is connected and with usb debugging on? use the tool and wait a bit..it should reboot itself and then its rooted....but at this time why you dont unlock your bootloader?
that way you can flash custom kernel and custom roms easier..

Do you have Flashtool or any other Android-related app running in the background? If yes, close it.
Also, questions must be posted in Q&A.

No nothing is running in the back. Is it normal that a 2nd adb.exe runs too?

What if you try to close both of them and then run the app?
This issue happens when one instance of adb.exe is already running.

Someguyfromhell said:
What if you try to close both of them and then run the app?
This issue happens when one instance of adb.exe is already running.
Click to expand...
Click to collapse
One question, is there any problem if i am connecting my usb cable into USB3 port?
edit: the thing is that if i connect in in a normal usb the proccess goes on but in the end fails
failed to copy 'files\su' to '/system/bin/su': Read-only file system
--- correcting ownership
Unable to chmod /system/bin/su: No such file or directory
--- correcting permissions
Unable to chmod /system/bin/su: No such file or directory
--- correcting symlinks
rm failed for /system/xbin/su, Read-only file system
link failed Read-only file system
--- pushing Superuser app
failed to copy 'files\Superuser.apk' to '/system/app/./Superuser.apk': Read-only
file system
--- cleaning
--- rebooting
ALL DONE!!!
instead of USB3 port which stops in the begining

Finally i got it root with e-root, before that eroot always was stucking in the last step before rooting hopefully i am rooted again

Related

Different Firmware- can I still root?

I would like to root My LT18i Xperia Arc S, just so I can get rid of the bloatware, although if I could upgrade to ICS as well then that would be cool. I've found loads of instructions on how to root, but none for my firmware version, which is 4.0.2.C.0.5. The phone is locked to Three (a UK network operator). A lot of the instructions talk of downgrading the firmware from various versions to 4.0.2.A.0.42, and then rooting from there, although none list my particular firmware. Is this method possible for my firmware version? If it's not and I try anyway will I wreck my phone? I'd like to be as sure as possible before I start. My boot loader is locked.
Thank you.
timswait said:
I would like to root My LT18i Xperia Arc S, just so I can get rid of the bloatware, although if I could upgrade to ICS as well then that would be cool. I've found loads of instructions on how to root, but none for my firmware version, which is 4.0.2.C.0.5. The phone is locked to Three (a UK network operator). A lot of the instructions talk of downgrading the firmware from various versions to 4.0.2.A.0.42, and then rooting from there, although none list my particular firmware. Is this method possible for my firmware version? If it's not and I try anyway will I wreck my phone? I'd like to be as sure as possible before I start. My boot loader is locked.
Thank you.
Click to expand...
Click to collapse
Have you run SEUS or PC Companion at all? There's been 5 FW releases since then according to Wotan Server.
From what I have heard, the regular root method for GB, 4.0.2.A.0.58 and lower, should work also on 4.0.2.C.0.5 firmware. Give it a try, you got nothing to lose there.
OK, so I really am a total numpty, I was assuming that all updates could come OTA, and because I didn't have any updates available when I checked on the phone I must have the latest version, I hadn't realised that updating it from a PC did a full update. :silly:
So I'm now updated to ICS, although in a way my original question remains... Now my build number is 4.1.L.0.8, so can I follow the root guides for 4.1.A.0.562, for example the guide here: androidauthority.com/xperia-arc-s-lt18i-root-android-4-0-ics-80266 ? And equally importantly, if I try to follow the guide and it doesn't work on my firmware will it simply do nothing, or will it wreck the phone?
Thank you guys, I thought I had done a lot of reading up on rooting and flashing and unlocking boot loaders, but missed the obvious and a simple comment like "Have you tried SEUS" can make all the difference!
timswait said:
OK, so I really am a total numpty, I was assuming that all updates could come OTA, and because I didn't have any updates available when I checked on the phone I must have the latest version, I hadn't realised that updating it from a PC did a full update. :silly:
So I'm now updated to ICS, although in a way my original question remains... Now my build number is 4.1.L.0.8, so can I follow the root guides for 4.1.A.0.562, for example the guide here: androidauthority.com/xperia-arc-s-lt18i-root-android-4-0-ics-80266 ? And equally importantly, if I try to follow the guide and it doesn't work on my firmware will it simply do nothing, or will it wreck the phone?
Thank you guys, I thought I had done a lot of reading up on rooting and flashing and unlocking boot loaders, but missed the obvious and a simple comment like "Have you tried SEUS" can make all the difference!
Click to expand...
Click to collapse
If it doesnt work, your phone should be fine. But that also means that you've been doing something wrong. Give it a go
Sent from Xperia Arc S
I followed the instructions here for rooting:
http://forum.xda-developers.com/showthread.php?t=1601038&nocache=1
It seemed to go through all the stages, the phone rebooted several times and it came up "All done" at the end. The good news is that the phone still works fine, the bad news is that it doesn't seem to be rooted. I've installed Titanium Backup and it comes up with "could not acquire root privileges, please check that your phone is rooted", so I assume this means it hasn't worked? Is there any other way to see if it's rooted? This is the output from running the rooting batch script:
Code:
--- STARTING ----
--- WAITING FOR DEVICE
* daemon not running. starting it now *
* daemon started successfully *
--- creating temporary directory
mkdir failed for tmp, File exists
--- cleaning
rm failed for *, No such file or directory
--- symlinking tmp directory
failed on '/data/local/tmp' - Permission denied
link failed File exists
--- Rebooting
--- WAITING FOR DEVICE TO RECONNECT
--- PLEASE WAIT, THIS MAY TAKE A WHILE
if it gets stuck over here for a long time then try:
disconnect usb cable and reconnect it
toggle "USB DEBUGGING" (first disable it then enable it)
--- DEVICE FOUND
--- enabling emulator hack
/system/bin/sh: cannot create /data/local.prop: Permission denied
--- Rebooting
--- WAITING FOR DEVICE TO RECONNECT
--- PLEASE WAIT, THIS MAY TAKE A WHILE
if it gets stuck over here for a long time then try:
disconnect usb cable and reconnect it
toggle "USB DEBUGGING" (first disable it then enable it)
--- DEVICE FOUND
--- pushing busybox
3059 KB/s (1075144 bytes in 0.343s)
--- correcting permissions
--- remounting /system
mount: permission denied (are you root?)
--- checking free space on /system
0 KB/s (439 bytes in 1.000s)
--- Free space on /system : 56068 bytes
--- no cleanup required
--- copying busybox to /system/xbin/
/system/xbin/busybox: cannot open for write: Read-only file system
--- correcting ownership
Unable to chmod /system/xbin/busybox: No such file or directory
--- correcting permissions
Unable to chmod /system/xbin/busybox: No such file or directory
--- installing busybox
/system/bin/sh: /system/xbin/busybox: not found
--- pushing SU binary
failed to copy 'files\su' to '/system/bin/su': Read-only file system
--- correcting ownership
Unable to chmod /system/bin/su: No such file or directory
--- correcting permissions
Unable to chmod /system/bin/su: No such file or directory
--- correcting symlinks
rm failed for /system/xbin/su, Read-only file system
link failed Read-only file system
--- pushing Superuser app
failed to copy 'files\Superuser.apk' to '/system/app/./Superuser.apk': Read-only
file system
--- cleaning
rm failed for /data/local.prop, No such file or directory
rm failed for /data/local/tmp, Permission denied
failed on '/data/local/tmp.bak' - No such file or directory
--- rebooting
ALL DONE!!!
Press any key to continue . . .
There's four links to root threads now in my guide, give them a read.
Thanks, that guide was very useful. I've actually used a combination of the techniques, and it seems to have worked Here's what I did, might be useful to someone, also please if anyone who knows better than me can see any problems then please let me know if I'm going to have problems in the future
1. Backed up my firmware using the instructions from 100rabh791 here:
http://talk.sonymobile.com/message/178992
2. Flashed back to 4.1.A.0.562 Kernel using Nabeel's instructions here:
http://talk.sonymobile.com/thread/41119?start=0&tstart=0
3. Rooted using DooMLoRD's root kit here:
http://forum.xda-developers.com/showthread.php?t=1601038
At this point I seemed to have a fully working and rooted phone, however I thought it was best to go back to my original build version (4.1.L.0.8), so I re-flashed my backed up firmware, However this lost my root privileges, so I was back to the start. So I re-did steps 1-3 and then:
4. Re-flashed back to my original firmware, but checked the options "Exclude system", "Exclude baseband", "Exclude Fota" and "Exclude TA" (in other words just left Kernel unchecked).
So as I understand it (which I possibly don't), I should be back on my original, most up to date build version, but now have root access, please correct me if there's anything wrong with what I've done.
timswait said:
So as I understand it (which I possibly don't), I should be back on my original, most up to date build version, but now have root access, please correct me if there's anything wrong with what I've done.
Click to expand...
Click to collapse
Nice one, doesn't look like you'll have any issues, but the main thing is you've got root. What does it say in your Settings/About Phone/Build Number?
XperienceD said:
Nice one, doesn't look like you'll have any issues, but the main thing is you've got root. What does it say in your Settings/About Phone/Build Number?
Click to expand...
Click to collapse
4.1.L.0.8 which is what it was on after the official upgrades before I started the rooting process.

i have a question when i press Volume Up, Power, Menu buttons

it takes me to android recovery, i noticed theres a option that says apply update from sd card,
if i put the super user zip to my sd card will it root it? i dont want to brick it though! any suggestions?
please help!
well i just tried installing superuser zip that i got from here http://galaxys3root.com/galaxy-s3-root/how-to-root-galaxy-s3-on-mac-osx/
and it said signature verification failed. hmmm
Need custom recovery to flash that.
damn i got all happy for a seconds thinking i can root my s3 without using my mac!!!
:crying: still unable to root! damn you jellybean! hahaha
is downgrading to ics to root s3 troublesome?
Use the methods that are stickied. Can HARDLY ever go wrong there. I say hardly cause some forums for older phones are not up to date, these are.
mt3g said:
Use the methods that are stickied. Can HARDLY ever go wrong there. I say hardly cause some forums for older phones are not up to date, these are.
Click to expand...
Click to collapse
yeah ive been looking and the only way to root it is with a pc, which the closest one is the library that doesnt enable downloads! =(
beto0216 said:
yeah ive been looking and the only way to root it is with a pc, which the closest one is the library that doesnt enable downloads! =(
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1946149&highlight=root+with+mac
this won't work?
mt3g said:
http://forum.xda-developers.com/showthread.php?t=1946149&highlight=root+with+mac
this won't work?
Click to expand...
Click to collapse
nope this is what i get.
***************************************************************
*
* One-Click Root Script for Galaxy S3!
*
* brought to you by Ultimatedroid.blogspot.com
*
* Credit goes to XDA user sparkym3 for exploit & Max Lee.
*
***************************************************************
This script will give you
1. Root !
Please read full tutorial at Ultimatedroid.blogspot.com
***************************************************************
waiting... If you get stuck here, try another USB port.
* daemon not running. starting it now *
* daemon started successfully *
Start Rooting...
failed to copy 'debugfs' to '/data/local//debugfs': Permission denied
failed to copy 'su' to '/data/local//su': Permission denied
failed to copy 'debugfsinput' to '/data/local//debugfsinput': Permission denied
failed on '/data/local/tmp' - Permission denied
link failed File exists
reboot #1 - DO NOT DISCONNECT YOUR DEVICE!
Unable to chmod /data/local/debugfs: No such file or directory
/system/bin/sh: can't open /data/local/debugfsinput: No such file or directory
rm failed for /data/local/tmp, Permission denied
failed on '/data/local/tmp.bak' - No such file or directory
rm failed for /data/local/su, No such file or directory
rm failed for /data/local/debugfs, No such file or directory
rm failed for /data/local/debugfsinput, No such file or directory
reboot #2 - DO NOT DISCONNECT YOUR DEVICE!
All Done rooting Galaxy S3, install SuperUser or SuperSU app from Play Store to get full root!
rootmac.sh: line 40: unexpected EOF while looking for matching `"'
rootmac.sh: line 42: syntax error: unexpected end of file
I don't have a mac so I don't have the issues obviously but did you do what it said to do? Go to play store and install Super SU just to test? also, can you not use ODIN? Since no one else is helping I figured I would jump in and spit ball ideas.

ADB not working

Hi, I just got my replacement S3 and I am attempting to root it. I've tried doing it on my own and with toolkits but nothing seems to work.
When putting the phone in debugging mode it technically won't go in. The little jellybean guy no longer shows up on the top and it says connected as a media device but 5 times out of 10 it will show up in ./adb devices.
I am attempting to transfer the root files but every time it gives me permission denied, what can I do?
failed to copy 'debugfs' to '/data/local//debugfs': Permission denied
failed to copy 'su' to '/data/local//su': Permission denied
failed to copy 'debugfsinput' to '/data/local//debugfsinput': Permission denied
failed on '/data/local/tmp' - Permission denied
link failed File exists
reboot #1 - DO NOT DISCONNECT YOUR DEVICE!
Unable to chmod /data/local/debugfs: No such file or directory
/system/bin/sh: can't open /data/local/debugfsinput: No such file or directory
rm failed for /data/local/tmp, Permission denied
failed on '/data/local/tmp.bak' - No such file or directory
rm failed for /data/local/su, No such file or directory
rm failed for /data/local/debugfs, No such file or directory
rm failed for /data/local/debugfsinput, No such file or directory
reboot #2 - DO NOT DISCONNECT YOUR DEVICE!
All Done rooting Galaxy S3, install SuperUser or SuperSU app from Play Store to get full root!
RootMac.sh: line 40: unexpected EOF while looking for matching `"'
RootMac.sh: line 42: syntax error: unexpected end of file
Try uninstalling your Samung USB drivers and installing the most up to date ones instead. If they are up to date try doing that anyway. Also make sure your using your factory cable. And lastly try another USB port on or PC or another PC all together
Sent from my SAMSUNG-SGH-I747 using xda premium
I'm using a mac. Everything worked with the old device
I had trouble with this also. My replacement phone had Jelly Bean.
I just put it into Download mode and flashed a rooted stock ROM instead.
CZ Eddie said:
I had trouble with this also. My replacement phone had Jelly Bean.
I just put it into Download mode and flashed a rooted stock ROM instead.
Click to expand...
Click to collapse
Just tried that but the device doesn't show up in adb in download mode. Why is this so hard? My first phone was a 1-2 thing.
jliehr said:
Just tried that but the device doesn't show up in adb in download mode. Why is this so hard? My first phone was a 1-2 thing.
Click to expand...
Click to collapse
Why are you using ADB in download mode?
Use Odin.
CZ Eddie said:
I had trouble with this also. My replacement phone had Jelly Bean.
I just put it into Download mode and flashed a rooted stock ROM instead.
Click to expand...
Click to collapse
CZ Eddie said:
Why are you using ADB in download mode?
Use Odin.
Click to expand...
Click to collapse
I'm trying everything I can.
I have a windows/mac machine. The device doesn't show up on the PC (drivers/kies both installed) but it does in my mac but I get the permission denied errors for everything as mentioned in OP.
Sounds like ADB is requesting super user permissions from or Mac. Or best bet would be Odin on a PC. See if it sees the device. If it doesn't try it with debugging on and off
Sent from my SAMSUNG-SGH-I747 using xda premium
Have you updated the SDK to the latest? There were recent (in the last month or so) updates.

[Q] Rooting problems - Please help!

Hello everyone,
I've had my LG Nitro HD for about a year and a half. I've recently been disappointed with it's performance and battery live. I read rooting and adding a new rom really helps free up the phone's natural performance. I've unlocked a few phones in the past. This one seems to be giving me a lot of fits.
I downloaded a zip file called 'P930_v20e_ROOT". I do not want to share any external linking as it's usually frowned upon. Nevertheless I unzipped the folder and copied the file "LG_SystemBackupTest" to the root of my sd card. I downloaded a file manager app to execute the file. Once installed I enabled the option for unverified sources, and the option for USB under development mode. I also installed the OEM LG driver off of their website for the P930 model phone. I then ran the LG_SystemBackupTest file that was in my applications. While it ran it simply states "hello world". I powered off/restarted the phone as instructed.
Once the phone booted up I plugged in the usb cable to my Windows 8 PC. I then ran the "root_p880" file. Below is the error I get repeatedly.
DON'T TOUCH THE DEVICE OR UNPLUG WHILE ROOTING!
PUSH FILES
failed to copy 'busybox' to '/data/local/busybox': Permission denied
failed to copy 'su' to '/data/local/su': Permission denied
failed to copy 'Superuser.apk' to '/data/local/Superuser.apk': Permissio
Unable to chmod /data/local/busybox: No such file or directory
Unable to chmod /data/local/su: No such file or directory
Unable to chmod /data/local/Superuser.apk: No such file or directory
failed on '/data/local/tmp' - Permission denied
link failed File exists
REBOOT
/system/bin/sh: cannot create /data/local.prop: Permission denied
AGAIN REBOOT
AGAIN!?
mount: Operation not permitted
mount: Operation not permitted
/system/bin/sh: cannot create /system/xbin/busybox: Read-only file syste
Unable to chmod /system/xbin/busybox: No such file or directory
/system/bin/sh: /system/xbin/busybox: not found
/system/bin/sh: busybox: not found
/system/bin/sh: busybox: not found
Unable to chmod /system/xbin/su: No such file or directory
Unable to chmod /system/xbin/su: No such file or directory
Unable to chmod /system/app/Superuser.apk: No such file or directory
rm failed for /data/local.prop, No such file or directory
rm failed for /data/local/tmp, Permission denied
failed on '/data/local/tmp.bak' - No such file or directory
I've tried every possible combination I can think of. I even booted up one of my old Windows XP machines, performed all the steps above, and still the same. Just now I finally reset the phone to it's factory defaults. Only to get the same results. Can anyone provide any guidance?
Kind regards,
Jeremy
Just getting root isn't going to allow you to flash a new or custom rom. You need to install cwm using the P930 unbricking guide.
Re: Rooting problems - Please help!
audit13 said:
Just getting root isn't going to allow you to flash a new or custom rom. You need to install cwm using the P930 unbricking guide.
Click to expand...
Click to collapse
Thank you for the prompt reply. I do have another guide I was following to install a custom rom. However it states I first need to root. It provided no instructions and stated to google how to do it.
LilLowEK said:
Thank you for the prompt reply. I do have another guide I was following to install a custom rom. However it states I first need to root. It provided no instructions and stated to google how to do it.
Click to expand...
Click to collapse
Did you try both guides in this forum? I believe this is the guide I used: http://forum.xda-developers.com/showthread.php?t=1784709
You need to brick the phone, revive it, root, and install cwm.
audit13 said:
Did you try both guides in this forum? I believe this is the guide I used: http://forum.xda-developers.com/showthread.php?t=1784709
You need to brick the phone, revive it, root, and install cwm.
Click to expand...
Click to collapse
Thanks. I didn't use that guide. I'll read through it. It sound kind of odd that I first need to brick the phone just to un-brick it. If anyone else has any experience or used a different guide please feel free to share.
Best,
Jeremy
LilLowEK said:
Thanks. I didn't use that guide. I'll read through it. It sound kind of odd that I first need to brick the phone just to un-brick it. If anyone else has any experience or used a different guide please feel free to share.
Best,
Jeremy
Click to expand...
Click to collapse
What room are you using? You need to unlock the boot loader and this needs gingerbread, not ICS. This is the guide I have used on two different phones.
audit13 said:
What room are you using? You need to unlock the boot loader and this needs gingerbread, not ICS. This is the guide I have used on two different phones.
Click to expand...
Click to collapse
Thanks. I sent you a PM with some details on what I was using.
Re: Rooting problems - Please help!
audit13 said:
What room are you using? You need to unlock the boot loader and this needs gingerbread, not ICS. This is the guide I have used on two different phones.
Click to expand...
Click to collapse
LilLowEK said:
Thanks. I sent you a PM with some details on what I was using.
Click to expand...
Click to collapse
Problem seems to be solved. I rooted the phone with the help of the following thread.
http://forum.xda-developers.com/showthread.php?t=1886460
Thanks everyone! Now off to hopefully get a rom installed.

need help system is read only

Hi,
im trying to install twrp and having a tough time trying to find a solution to my problem, ive rooted using zeroepochs guide, when i run the command to extract and install the recovery.zip i get a read only error as below
[email protected]:/ $ sh /sdcard/firetv2_recovery_v5.zip
Extracting unzip...
Remounting /system read-write...
mount: Invalid argument
Extracting...
checkdir: cannot create extraction directory: /system/recovery
Read-only file system
ln: /system/bin/ext4_resize: Read-only file system
Remounting /system read-only...
any help is appreciated.
You need to go into root admin.
Use the command "Su" to get into root shell
Hi, thanks I've tried that and get the same issues?
skirocket said:
Hi, thanks I've tried that and get the same issues?
Click to expand...
Click to collapse
After su command was sent through ADB, have you granted access on the pop up screen that appears at first use?
- Reset (unplug and plug back in) unit
- let it boot into main menue
- connect through ABD
- at adb shell prompt type su
- enter
- A pop up screen should appear on your TV asking you to grant access for su
- using your FireTV remote select yes and press OK.
- see if issue is solved
bula1ca said:
After su command was sent through ADB, have you granted access on the pop up screen that appears at first use?
- Reset (unplug and plug back in) unit
- let it boot into main menue
- connect through ABD
- at adb shell prompt type su
- enter
- A pop up screen should appear on your TV asking you to grant access for su
- using your FireTV remote select yes and press OK.
- see if issue is solved
Click to expand...
Click to collapse
hi thanks for the reply, i have done that and it says that i have been granted SU but i get this message
[email protected]:/ # sh /sdcard/firetv2_recovery_v5.zip
Extracting unzip...
Remounting /system read-write...
mount: Invalid argument
Extracting...
checkdir: cannot create extraction directory: /system/recovery
Read-only file system
ln: /system/bin/ext4_resize: Read-only file system
Remounting /system read-only...
Sorry to pick this up again. But i have the same Issue. How have you installed TWRP?
Thanks
I used King root, then installed a custom rom, had too many problems trying to install twrp previously.
skirocket said:
I used King root, then installed a custom rom, had too many problems trying to install twrp previously.
Click to expand...
Click to collapse
Thank you
so you used this guide http://www.aftvnews.com/how-to-root...covery-and-a-pre-rooted-rom-all-without-a-pc/ with your rooted Fire Tv2?
i used this guide http://www.aftvnews.com/how-to-root-the-fire-tv-2-using-kingroot-no-usb-cable-required/. but at the time if i remember i updated my box to stock update 5.0.5 from 5.0.4 then rooted again.
Hi, the trick is to use this Guide http://www.aftvnews.com/how-to-root-the-amazon-fire-tv-2/
Worked perfectly
I know this is an old thread but I'll post what worked for me just in case...
On ADBLink, select Root → Mount /system RW. This will make /system writable.
Not sure if this is necessary, but I switch back to RO (read only) once I was done with my changes.

Categories

Resources