Hi guys,
I am totally new to Android and it's my first post here also.
I 've just purchased my Xperia Arc S and follow the guide here to root my phone.
http://forum.xda-developers.com/showthread.php?t=1409269
Sadly, I failed from the very first step: installing adb driver:
There are 2 linked guides from the above post:
1st one:
http://forum.xda-developers.com/showthread.php?t=502010
I followed the pdf guide and wonder what to do after adb shell? it shows a "$" and asks for my command, I don't know what to type in, and I think it has not done anything to my phone either.
2nd guide:
http://forum.xda-developers.com/showthread.php?t=910008
The author of this post all talks about nookcolor. I tried and when I plugin my phone windows does not ask for anything.
What should I do now?
And btw, how can I check that abd driver has been installed correctly?
Thank you.
to check adb drivers. connect ur phone in normal mode with usb debugging selected.
nw in the windows command window type adb devices [enter]
nw some alphanumneric shd come.
to check if u r rooted. type su [enter] . nw $ shd turn to # .
Sent from my Nexus One using Tapatalk
Downgraded to .42 and rooted successfully
Related
This is the method I used to S-Off several devices (8 in total) on Windows 7 64 bit.
Remember, Team Unlimited does not recommend that you use any OS that is not supported as the drivers can cause some issues.
I have included a method that will test whether your drivers in your current setup will perform in a way that reduces the chance of all hell breaking loose.
Before starting, make sure you have downloaded and installed the HTC drivers for your phone and have Adb downloaded. A great place to get this is from “Team fireballas FakeCid AUTOMATIC bootloader unlock” thread.
We will need this file for a later process as well. (File Download)
Once downloaded, unzip it to C:\Root.
Verifying that your drivers are working correctly. (Typed commands are in red)
1) Attach your phone to you computer with the supplied USB cable.
2) Enable USB Debugging (Settings>Developer Options>USB Debugging)
3) Open a command prompt and navigate to the location you extracted the adb files to by typing: cd\
Then type: cd c:\Root\stuff
Your Prompt should read:
c:\Root\stuff>
4) Now type adb devices
You should see the following output in the command prompt.
C:\ Root\stuff >adb devices
List of devices attached
HT26KS311633 device
Your device will have a different device ID than what is listed above. Just make sure it shows a device ID and device listed after it.
5) Now type: adb reboot bootloader
At this point your phone should reboot into the bootloader with Fastboot selected.
6) Type: fastboot devices
You should see the following output in the command prompt.
C:\inc4>fastboot devices
HT26KS311633 fastboot
Ensure that your device is listed. Your device will have a different device ID than what is listed above. Just make sure it shows a device ID and fastboot listed after it.
7) Type: fastboot reboot
You should see the following output in the command prompt.
C:\inc4>fastboot reboot
rebooting...
finished. total time: 0.070s
Your phone should be rebooting.
You have now verified that your drivers are working correctly even after rebooting into fastboot.
At this point I cannot give you alternative instructions per Team Unlimited. So follow the directions listed HERE.
When you reach step 12 which states:
“Temproot your phone via any method available - we cannot help with this step and it is REQUIRED!”
Follow the following steps that were originally written by captainrewind in the “Team fireballas FakeCid AUTOMATIC bootloader unlock” thread.
Go to Settings -> Connect to PC and change Default connection type to Disk drive and disable Ask me.
Navigate to the folder in the command Prompt by typing
cd c:\Root\stuff
Now that you're there, type:
adb devices
If your phone pops up in the list, you're good to go!
Next, type
adb restore fakebackup.ab
DO NOT click OK to the restore on the device just yet!
Now type:
adb shell "while ! ln -s /data/local.prop /data/data/com.android.settings/a/file99; do :; done"
(errors will appear, ignore)
Accept the restore on the device, then type:
adb reboot
(At this time, you are temprooted, and the phone UI will be in an unusable state, with temproot shell.)
After reboot type:
adb shell
Verify that the prompt is "#" (meaning root) or "$" (meaning normal user). If it's not "#", please start over.
You can now return to Team Unlimited’s instructions and continue with step 13.
This should take you the rest of the way to S-Off.
*Madmoose* said:
I have included a method that will test whether your drivers in your current setup will perform in a way that reduces the chance of all hell breaking loose.
Click to expand...
Click to collapse
Excellent suggestion and great advice. Always make sure your computer can recognize your device in all device states before attempting root.
I found the hard way on a Kindle Fire and now always do this test (a couple of times) to make sure the device being rooted can be seen in all states by the PC. For whatever reason, my (original) Kindle Fire has a different USB Enum for each state and my Windows 7 64-Bit computer didn't recognize it in fastboot which caused a lot of irritation.
This is helpful but I believe unlimited specifically asked not to have any other how to threads
Sent from my Nexus 7 using Tapatalk 2
This isn't a how to about Unlimited's process. And frankly, they can request anything they want, but they will not control other peoples threads. They were talking about their own thread.
*Madmoose* said:
Next, type
adb restore fakebackup.ab
DO NOT click OK to the restore on the device just yet!
Now type:
adb shell "while ! ln -s /data/local.prop /data/data/com.android.settings/a/file99; do :; done"
(errors will appear, ignore)
Accept the restore on the device, then type:
adb reboot
Click to expand...
Click to collapse
I'd like to comment on this part, since it threw me off a bit and scared the daylights out of me.
After you issue the "while..." command, you'll get infinitely scrolling errors/warnings, or at least I did in Ubuntu. Just ignore them, nothing is wrong. While they are infinitely repeating in your terminal, just accept the restore on the phone and they stop. I don't remember the exact text of the error, but if someone could put it here that would probably be helpful to anyone wondering.
Very cool. Thanks madmoose!
Is It Working with HTC ONE V (GSM) ???
No dude this is the incredible 4G threads
I am so going to do this. Soon. Hawk might have an Ecliptic release some day.
Linch89 said:
No dude this is the incredible 4G threads
Click to expand...
Click to collapse
Will this make my laptop s-off
Sent from my Nexus 7 using Tapatalk 2
Only if your laptop is an Incredible 4G...
Add me to the list of S-OFF via Win7 64bit. I restored my Viper TWRP backup and all is running smootly. Now, I am off to customize my bootloader with RegawMOD Bootloader Customizer.
Used a modified version of this to achieve s-off but what really helped me was the "Verifying that your drivers are working correctly." section. When I had tried unlocking earlier I keep getting stuck in the error looping screen when restoring the fakebackup. This little set of instructions pointed me in the right directions for getting the drivers installed correctly.
Many thanks MadMoose and Happy New Year! :victory:
Many thanks to MadMoose. Everything worked for me on Win7 64bit as well, and would have worked more smoothly if I had done it your way
Yesssssssssssssssssss
Wow what a journey, used it on my 64 bit computer per another post here that gave a very nice detailed instructions. had to relock, temproot, s off, flash recovery, and then restore... but i would do it 100 times again! thanks everyone for your activeness in this community, hopefully it continues to grow
Has anyone tried to get s-off with Windows 8 x64 yet? I copied in the drivers, tried all the commands, and they replied normally. Will I brick my phone if I try?
I'm afraid it won't work unlimited said that 64 win7 wasn't officially supported it just happens to work
It may work but unlimited won't help/support you if you have problems.
bberryhill0 said:
It may work but unlimited won't help/support you if you have problems.
Click to expand...
Click to collapse
I'm just wondering if it doesn't work, then am I bricked? Or can I just pull the battery and restart?
spectre559 said:
I'm just wondering if it doesn't work, then am I bricked? Or can I just pull the battery and restart?
Click to expand...
Click to collapse
Went ahead with s-off in win 7 x64. Success!
Im starting this new thread because I was not able to find a solution for my problem for about 2 weeks now.
Issue : Unable to install recovery. Im trying to install recovery by following this thread : http://forum.xda-developers.com/showthread.php?t=2221102 - in the 3rd step when i flash the recovery i get this error "command write failed - unknown error"
- tried almost all the different types of steps available in xda and also outside xda.
My Environment:
Win8 Pro 32bit
LG optimus L9 flashed and rooted by lelus method - Current ROM - P76020c
Installed all LG drivers - PC suite is installed
Have SDK manager installed
Device is recognized when I run the "adb devices" command keeping phone switched on.
Device is recognized when I run the "fastboot devices" command when phone is in fastboot mode.
So I guess this is not a driver issue.
Im also attaching screenshots of the error and the commands that I have ran ....
SOOOOOOOOOOOO ... whats the prob here .... ... anyone faced this same prob ???? HELPPPP
rkn989 said:
Im starting this new thread because I was not able to find a solution for my problem for about 2 weeks now.
Issue : Unable to install recovery. Im trying to install recovery by following this thread : http://forum.xda-developers.com/showthread.php?t=2221102 - in the 3rd step when i flash the recovery i get this error "command write failed - unknown error"
- tried almost all the different types of steps available in xda and also outside xda.
My Environment:
Win8 Pro 32bit
LG optimus L9 flashed and rooted by lelus method - Current ROM - P76020c
Installed all LG drivers - PC suite is installed
Have SDK manager installed
Device is recognized when I run the "adb devices" command keeping phone switched on.
Device is recognized when I run the "fastboot devices" command when phone is in fastboot mode.
So I guess this is not a driver issue.
Im also attaching screenshots of the error and the commands that I have ran ....
SOOOOOOOOOOOO ... whats the prob here .... ... anyone faced this same prob ???? HELPPPP
Click to expand...
Click to collapse
As always, use at your own risk.
Upload recovery image to sdcard and change the file name to recovery.img if that helps
flash via adb from your computer
Code:
adb shell su -c busybox dd if=/sdcard/external_sd/recovery.img of=/dev/block/mmcblk0p4
or terminal emulator straight from the phone
Code:
su
busybox dd if=/sdcard/external_sd/recovery.img of=/dev/block/mmcblk0p4
Lelus said:
flash via adb from your computer
Code:
adb shell su -c busybox dd if=/sdcard/external_sd/recovery.img of=/dev/block/mmcblk0p4
[/QUOTE]
is this the exact code that we should type into the cmd after getting to fastboot mode ??? or shud this be ran while phone is switched on ???
Click to expand...
Click to collapse
rkn989 said:
is this the exact code that we should type into the cmd after getting to fastboot mode ??? or shud this be ran while phone is switched on ???
Click to expand...
Click to collapse
phone switched on, usb mode: camera or lg software
btw, you have unlocked the bootloader , right ?
Lelus said:
phone switched on, usb mode: camera or lg software
btw, you have unlocked the bootloader , right ?
Click to expand...
Click to collapse
yess .... my bootloader is unlocked ....
tried this and get an error - su not found - check screenshot
im not getting the command that we tried :
adb shell su -c busybox dd if=/sdcard/external_sd/recovery.img of=/dev/block/mmcblk0p4
"su" stands for ???
and where should i copy the .img file to ?? (i copied it to the root of the ext sd card)
anyone any suggestions ?????
May be your file is corrupt. Just give it a try.
Download latest version of CWM Touch and Non-touch version from http://www.clockworkmod.com/rommanager and try again.
cmahendra said:
May be your file is corrupt. Just give it a try.
Download latest version of CWM Touch and Non-touch version from http://www.clockworkmod.com/rommanager and try again.
Click to expand...
Click to collapse
Ive already tried that ... have tried downloading the files many times .. already have 4-5 copies of both the normal and touch recoveries ...
Its the same error !!!!!!
And yu want me to try by the fastboot method rite ?? not the method lelus juzz said ???
Lelus said:
flash via adb from your computer
Code:
adb shell su -c busybox dd if=/sdcard/external_sd/recovery.img of=/dev/block/mmcblk0p4
or terminal emulator straight from the phone
Code:
su
busybox dd if=/sdcard/external_sd/recovery.img of=/dev/block/mmcblk0p4
Click to expand...
Click to collapse
Can yu explain this in more detail. ????
Sent from my LG-P760 using xda app-developers app
rkn989 said:
Ive already tried that ... have tried downloading the files many times .. already have 4-5 copies of both the normal and touch recoveries ...
Its the same error !!!!!!
And yu want me to try by the fastboot method rite ?? not the method lelus juzz said ???
Click to expand...
Click to collapse
Lelus is explaining you in details and he is expert here. I am just confirming that if you have tried the basic things or not. By the way, your fastboot drivers seem working as device responds to "fastboot devices" command properly.
The fastboot screen should show the phone is unlocked or not, exactly like this....does it show like this screenshot?
SW Upgrade mode also should show unlocked like this screnshot.
If not, you may not be yet Unlocked and fastboot will not work.
cmahendra said:
Lelus is explaining you in details and he is expert here. I am just confirming that if you have tried the basic things or not. By the way, your fastboot drivers seem working as device responds to "fastboot devices" command properly.
The fastboot screen should show the phone is unlocked or not, exactly like this....does it show like this screenshot?
SW Upgrade mode also should show unlocked like this screnshot.
If not, you may not be yet Unlocked and fastboot will not work.
Click to expand...
Click to collapse
I din know where exactly to run those commands, so asked detailed steps
And the my bootloader is unlocked, I get the fastboot boot mode when I run the adb reboot command to unlock bootloader, yday when I flashed my phone with v20c, I gt the second screenshot as yu mentioned, also i tried running that *# command from inside the phone and it showed bootloader status- unlock.
So I hope it is unlocked! !!
Sent from my LG-P760 using xda app-developers app
ATLASTTT !!!!!!!!!!!!! I have succeeded in flashing my recovery .....
but the resolution is strange .... it just worked fine in WIN7 .... isn't that strange ???????????
Hi all,
I am trying to root my Tablet Z SGP312 build no. 10.1.C.0.370 with Doomlord's easy rooting tool v13.
I have installed the ADB driver on my tablet.
I have also disabled the PC companion and enabled the USB debugging mode and install unknown sources under the device administration.
Once I activated the runme.dat with my tablet connected to my PC, i followed the steps as shown and reached a point where I have to type the shell following shell commands:
cd /data/local/tmp
chmod 777 doomed
./doomed
I typed and entered the above commands one by one, but with no response from both the cmd and my tablet after typing ./doomed. I am not too sure what I have done wrongly. It would be great if someone could help me on this matter. Thank you.
I looked all over the internet for help with this phone. I rooted it for a friend and a week later, he said he restarted the phone and everything started force closing.
I troubleshot all day, and came to figure out that my only known to me as of now, is flashing CWM to it, via ADB. I am having several issues with setting up ADB, and getting the phone to communicate with my computer. Device manager DOES show that there is an ADB device installed correctly, so what would my next move be? I got the phone into FTM mode, (fastboot?) and I know that that is what I need to do to get ADB to communicate with my phone.
halp pls
Really no one can help???
bamp
cammiso94 said:
bamp
Click to expand...
Click to collapse
ADB Drivers for Windows Vista/7
Tutorial- http://www.youtube.com/watch?v=RDA8PpPSFuk
If you havn't found this yet...
Your answer is here: androidforums.com/flash-all-things-root/ Good luck!:good:
CWM Beta
From Android Forums ... Thanks to Junkie2100
this is an unfinished copy of cwm, tested to be almost completely functional
standard warnings apply, use at your own risk, you try to blame me for breaking your phone i will laugh at you
instructions:
fastboot method is possible, but i will go through the terminal/adb method
download the recovery file, and put it on the root of your sd. no folders, just directly on the sd
get your phone rooted and get a copy of terminal emulator or connect to it through adb on your computer, adb will require zte drivers and the adb program on the pc. the choice is yours
fire up adb by typing
Code (Text):
adb shell
in the command prompt, if its not working you dont have adb in the directory youre in, just copy adb.exe and the two .dll files to c:\windows\system32\ and itll work from anywhere, or learn how command prompt works
or fire up terminal emulator on the phone
on adb shell or terminal emulator type
Code (Text):
su
dd if=/sdcard/flash_cwm_test2.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery
you will then need to run
Code (Text):
reboot recovery
and then hit reboot when cwm comes up, if it asks to disable recovery flashing press yes or it will put stock recovery back next time the rom boots
known bugs:
unmounting doesnt work
downloads:
w.ww.4shared.com/file/2qBR2Kfr/flash_cwm_test2.html
i apologize for it being 4shared, if someone wants to make a mirror ill put it up
Hello,
first i must apologize for my English but, i´ve got my phone back from display repair and i have it now out of warranty so i decide to make a root but i cant find step-by-step guide to do that. I´am on 6.0.1 android, Kernel 3.10.49, type VDF-995NB02-CZ10d.
No flash, no bootloader unlock, anything, i get it back after hard reset.
Can anyone help me please? I rooting for first time no Samsung device. I have some experience but i cannot downgrade to 5.1.1 to use Kingroot or MobileGo to root. After the root i want update back to 6.0.1 or use custom ROM.
i searched on Modaco and here but i cannot find guide what i can undestand and be sure if that will work for me.
Thanks for all replies :angel:
Krejdlis said:
Hello,
first i must apologize for my English but, i´ve got my phone back from display repair and i have it now out of warranty so i decide to make a root but i cant find step-by-step guide to do that. I´am on 6.0.1 android, Kernel 3.10.49, type VDF-995NB02-CZ10d.
No flash, no bootloader unlock, anything, i get it back after hard reset.
Can anyone help me please? I rooting for first time no Samsung device. I have some experience but i cannot downgrade to 5.1.1 to use Kingroot or MobileGo to root. After the root i want update back to 6.0.1 or use custom ROM.
i searched on Modaco and here but i cannot find guide what i can undestand and be sure if that will work for me.
Thanks for all replies :angel:
Click to expand...
Click to collapse
Take a backup of your data before proceeding further.
Try this,
Download adb and Koush Universal adb driver and install them on ur pc, always install the driver first and don't install the drivers adb setup asks u to install.
Run command prompt as administrator.
Open the folder in c drive where adb is installed, u can use file explorer for this.
Press Shift+right click and select open command window here.
Enable USB debugging on your phone and connect it to the pc by a USB cord.
Enter command "adb devices" without quotation marks.
If it shows some device connected, only then proceed further.
Enter command " adb reboot bootloader"
Enter command " fastboot devices", if it shows some device to be connected, only then proceed further.
Enter command " fastboot oem unlock".
Ur phone may then ask for final confirmation on the phone screen, select yes.
When procedure completes, type "fastboot reboot" and ur phone will reboot.
U can now use Kingoroot for pc or any other tool for rooting.
Augustoandro said:
Take a backup of your data before proceeding further.
Try this,
Download adb and Koush Universal adb driver and install them on ur pc, always install the driver first and don't install the drivers adb setup asks u to install.
Run command prompt as administrator.
Open the folder in c drive where adb is installed, u can use file explorer for this.
Press Shift+right click and select open command window here.
Enable USB debugging on your phone and connect it to the pc by a USB cord.
Enter command "adb devices" without quotation marks.
If it shows some device connected, only then proceed further.
Enter command " adb reboot bootloader"
Enter command " fastboot devices", if it shows some device to be connected, only then proceed further.
Enter command " fastboot oem unlock".
Ur phone may then ask for final confirmation on the phone screen, select yes.
When procedure completes, type "fastboot reboot" and ur phone will reboot.
U can now use Kingoroot for pc or any other tool for rooting.
Click to expand...
Click to collapse
Am i in the right folder? :laugh:
from cmd i get this after first two commands
C:\Program Files (x86)\ClockworkMod\Universal Adb Driver>fastboot devices
'fastboot' is not recognized as an internal or external command,
operable program or batch file.
Using Win10
Krejdlis said:
Am i in the right folder? :laugh:
from cmd i get this after first two commands
C:\Program Files (x86)\ClockworkMod\Universal Adb Driver>fastboot devices
'fastboot' is not recognized as an internal or external command,
operable program or batch file.
Using Win10
Click to expand...
Click to collapse
Have you installed adb? If yes, then proceed further.
You are in the wrong folder. The correct path should be C:\adb
Then Shift+right click
Select "Open command window here"
Hello,
C:\platform-tools-latest-windows\platform-tools>adb reboot bootloader
phone rebooting
C:\platform-tools-latest-windows\platform-tools>fastboot devices
after this command it shows nothing
can you please make a steps for ADB drivers instalation, i dont know if i made it properly.
Thanks
Krejdlis if you are able to root please tell me how you did it - currently have the same issue
SomeoneAnonymous said:
Krejdlis if you are able to root please tell me how you did it - currently have the same issue
Click to expand...
Click to collapse
Hi, still in progress, i trying everything but still without succes. Someone know how to easily downgrade to 5.1.1 with this phone?
Now it give me this : <waiting for any device>