[Q] I9000M: Rooting Froyo (JL2) - Galaxy S I9000 Q&A, Help & Troubleshooting

How do you root a JL2 Froyo on an I9000M?

I am looking how to root it also.

http://forum.xda-developers.com/showthread.php?t=803682

same here, superoneclick doesn't work. Tried all possible methods.
Killing ADB Server...
OK
Starting ADB Server...
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
OK
Waiting for device...
adb server is out of date. killing...
OK
Pushing rageagainstthecage...
adb server is out of date. killing...
OK
chmod rageagainstthecage...
adb server is out of date. killing...
OK
Running rageagainstthecage...
adb server is out of date. killing...
FAILED

Superoneclick works fine for me: http://goo.gl/DxOP7

What worked for me Bell I9000M JK4 or JL2 was to:
Disconnect Phone
Enable USB Debugging Mode
Shut Down Phone
Open SuperOneClick
Press ROOT
Wait until you see "Waiting for Device"
Connect Phone, wait for battery charging graphic
Turn On Phone
Let it do its thing, it should work all the way until you get SuperUser pushed to your device
If you get an USB error, try again from the start using another port

That's exactly what I did and had no problems. To get busybox installed, I opened titanium backup, clicked the "problems" button and let that app overall it.

has anyone found any other options to root other than SuperOneClick? I'm not sure if it's just my phone, but I start to get a lot of lag after using this to root...

For me, i just flashed speedmod inside the cwr there is a setting to root & install busybox

omg how does it take rageagainstthecage to run its thing.... it feels like its stuck

galaxywolf said:
omg how does it take rageagainstthecage to run its thing.... it feels like its stuck
Click to expand...
Click to collapse
make sure the phone is Awake, if it's in sleep mode (black screen) it wont do anything

How do I get a root file for my Bell Samsung Galaxy S Vibrant GT-I9000m with android 2.2 Froyo.UGJL2. I tried rooting it but I can't find any root file. I think I accidentally reformatted my internal sdcard. Pls. help!

I am having trouble using SuperOneClick, but it seems to be different from problems that other people are getting. I read through and watched the video. Everything said it was ok, and it seemed like all worked. I even got the "superuser" application installed. The problem is that su doesn't seem to work. If I go to a terminal window and type "su", I get Permission Denied. When I go to Titanium it says there is a problem with root. I tried installing busybox, and upgrading superuser, however these fail.
I just got my phone back from Samsung and they replaced the motherboard, and obviously put the new sotfware on it, however it seems to be the same 2.2 OS that everybody is talking about "JL2"
Has anybody seen this? any idea what might be happening?

I was able to answer my own question. I was able to root my phone using SuperOneClick by choosing the radio button for rageagainstthecage, instead of psneuter.

I have heard of many ppl having issues with Superoneclick and antivirus software preventing it from working properly or straight out removing it from the pc. Disabling the av software when you unzip and use the superoneclick may help.

Related

Require some guidence Samsung Captivate

I just switched to the samsung captivate (build number:ECLAIR.UXJI2) after being an iphone user for years. I put in every mod in that i could, unlocked it, & jailbroke it as much as humanly possible. Android is totally new to me. I have sucessfully rooted my device, but have no idea how to unlock the nand protection in order to install busy box so that I can install certan apps and utilities. My other problem is that I dont know what nand is, what busybox is, or what they do. I'm unfemilliar with the android terms as well and what they do, sush as flash, rom, ect.
I put 20 hrs of research in, in the last 3 days on line, and all i got done was a root.
I know im asking alot, but i can return the favors of android info with iphone info.
Thanks in advance to who ever helps me.
Did you download busy box app from market?
Busy box is a set of commands that many root programs utilize
groovydude1981 said:
I just switched to the samsung captivate (build number:ECLAIR.UXJI2) after being an iphone user for years. I put in every mod in that i could, unlocked it, & jailbroke it as much as humanly possible. Android is totally new to me. I have sucessfully rooted my device, but have no idea how to unlock the nand protection in order to install busy box so that I can install certan apps and utilities. My other problem is that I dont know what nand is, what busybox is, or what they do. I'm unfemilliar with the android terms as well and what they do, sush as flash, rom, ect.
I put 20 hrs of research in, in the last 3 days on line, and all i got done was a root.
I know im asking alot, but i can return the favors of android info with iphone info.
Thanks in advance to who ever helps me.
Click to expand...
Click to collapse
After u root:
1. Go to market and search for busybox and install it.
2. Open busy box, and follow the steps in it install the required commands.
You should be good now.
mcord11758 said:
Did you download busy box app from market?
Busy box is a set of commands that many root programs utilize
Click to expand...
Click to collapse
@mcord11758: * one more collision *
diablo009 said:
@mcord11758: * one more collision *
Click to expand...
Click to collapse
We are in sync
mcord11758 said:
We are in sync
Click to expand...
Click to collapse
oops. wrong word. u sure know how to phrase ur sentences. r u in any business/management role?
diablo009 said:
oops. wrong word. u sure know how to phrase ur sentences. r u in any business/management role?
Click to expand...
Click to collapse
I am in sales, but my educational background Is business
groovydude1981 said:
I just switched to the samsung captivate (build number:ECLAIR.UXJI2) after being an iphone user for years. I put in every mod in that i could, unlocked it, & jailbroke it as much as humanly possible. Android is totally new to me. I have sucessfully rooted my device, but have no idea how to unlock the nand protection in order to install busy box so that I can install certan apps and utilities. My other problem is that I dont know what nand is, what busybox is, or what they do. I'm unfemilliar with the android terms as well and what they do, sush as flash, rom, ect.
I put 20 hrs of research in, in the last 3 days on line, and all i got done was a root.
I know im asking alot, but i can return the favors of android info with iphone info.
Thanks in advance to who ever helps me.
Click to expand...
Click to collapse
Wow, I had my phone rooted and flashed within an hour of even learning what it all was.
Video tutorials are the best way to learn the basics, and once you have a grasp of what youre doing written instructions become easier to understand.
I recommend watching as many ROM review and install videos as possible, make sure to watch them more than once and while youre actually doing the steps.
thanks for the quick responce
I did download busybox from the market, but it tells me that everything is unavailable, and that my phone is rooted but my nand protection is still on. Plus busybox tells me that it can't find itself, whatever that means. lol
Pls let me know how to correct this.
By the way I used super 1 click 1.6.3 to root my device.
Thanks ppl your all awsome.
I also watched lots of videos, but could not find anything specific to my device. What other device videos are compatible in content with my samsung captivate?
thanks again.
Did you click install in busy box?
I dont know why but Itried busy box again and it installed. Now i think I just need nand protection removed andthe on click lag fix installed. it still wont install
groovydude1981 said:
I dont know why but Itried busy box again and it installed. Now i think I just need nand protection removed andthe on click lag fix installed. it still wont install
Click to expand...
Click to collapse
I would not use one click lash fix, but that is just me. If you want a lag fix consider a custom rom. One click lag fix is obsolete
thanks for the heads up. I installed the one click lag fix for now. When i learn how to use custom roms, ill uninstall it and use an up to date rom.
some help
groovydude1981 said:
thanks for the heads up. I installed the one click lag fix for now. When i learn how to use custom roms, ill uninstall it and use an up to date rom.
Click to expand...
Click to collapse
This is probably a great place for you to start.
http://forum.xda-developers.com/showthread.php?t=887525
there is a one click out there with root, unroot, and non market apps. i'm looking for it for you
EDIT
Here it is
http://forum.xda-developers.com/showthread.php?t=803682
Also before doing too much i'd familiarize yourself with the ODIN one click and learn about it as well as download mode so you know how to fix a bricked phone, well a soft bricked one.
I used super 1 click to root my phone, but anything you can send me is most appreciated. I will not be able to thank you enough.
Try rooting again with Galaxy one click root.
What will galaxy one click do for me that super one click wont?
They both essentially do the same thing. After your phone has been rooted you need to see if you can find the Super User app. It should be installed on your phone.
I've meant to update the Q&A sticky with what versions are easy to root.. so I apologize for not having it there.
When you install anything that requires root access (hence why your phone is rooted to begin with ) you would get a pop up requesting to have that application gain root access.
But.. there are only a few 3rd party apps that require root access if your not going to flash a custom ROM.
Titanium Backup btw will install the latest version of BusyBox for you - it is a highly used application to backup your system and applications for your phone.
Another highly used application is ROM Manager (used for flashing ROMs)
I would highly suggest you get familiar with how you restore your phone back to stock - then check out teh sticky under the dev forum on how to flash a custom ROM.
Then your on your way to becoming a fellow flash junky
I'm in the same boat as groovydude.
I have a 2 month old Samsung Captivate (first smart phone). I'm trying to root it. I have run SuperOneClick at least 6 times trying everything that I can find in the forums. I have drivers installed. Does anyone know if this tool will work on this phone, or if there is a tool that does. The output from SuperOneClick-ShortFuse is below. Every time it runs it tells me it is rooted, and every app that I open requiring root tells me it is not.
I have tried instructions to root via Update.zip. The instructions were to drop the file on the internal sd. When I plug the phone into the usb port, two drives show up. Nothing can be dropped on either. They both say to insert a disk. I have no external sd card. Does anyone know what might be the holdback?
Also, SuperOneClick said that BusyBox was installed, but I could not find it, so I downloaded Stericson's BusyBox installer. It failed to install with a message that the phone was now rooted but BusyBox was not found. It said the application failed because the phone is not "nand unlocked." What is nand unlocked? The only unlocking procedures that I can find instructions for are to unlock a phone from a carrier. Is this what "nand means"?
I tried Titanium Backup to install BusyBox, and it complains that the rom is not rooted after both other processes said it was. TI offered to download and install BusyBox and it failed too.
Does anyone know why all these procedures say that they have rooted the phone but nothing still works? Or what is nand unlock? and how is it done?
SUPERONECLICK OUTPUT:
SuperOneClick v1.6.5.0
Killing ADB Server...
OK
Starting ADB Server...
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
OK
Waiting for device...
OK
Pushing psneuter...
558 KB/s (585731 bytes in 1.024s)
OK
chmod psneuter...
OK
Running psneuter...
OK
***IF IT KEEPS LOOPING, TRY DISABLING USB DEBUGGING NOW***
Killing ADB Server...
OK
Starting ADB Server...
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
OK
Waiting for device...
OK
Running psneuter...
ROOTED
Pushing busybox...
974 KB/s (1062992 bytes in 1.065s)
OK
chmod busybox...
OK
Getting mount path...
/dev/block/stl9
OK
Reading OS Version properties...
Version: 1.5
OK
Remounting system with read-write access...
OK
Pushing su-v1...
640 KB/s (26256 bytes in 0.040s)
OK
chmod su...
OK
Creating /system/xbin...
mkdir failed for /system/xbin, File exists
OK
Copying busybox (/system/xbin/)...
OK
chmod busybox (/system/xbin/)...
OK
Installing busybox (/system/xbin/)...
OK
Pushing Superuser.apk...
1626 KB/s (196521 bytes in 0.118s)
OK
Remounting system with read-only access...
OK
Running a SU test...
Test failed!
FAILED
ro.wifi.channels=
ro.product.cpu.abi=armeabi-v7a
ro.product.model=SAMSUNG-SGH-I897
ro.build.tags=test-keys
ro.build.version.release=2.1-update1
ro.build.description=SGH-I897-user 2.1-update1 ECLAIR UCJH7 release-keys
ro.product.brand=Samsung
ro.product.device=SGH-I897
ro.build.version.incremental=UCJH7
ro.build.type=user
ro.build.date.utc=1282903617
ro.board.platform=s5pc110
ro.product.name=SGH-I897
ro.product.board=SGH-I897
ro.build.user=jetaek.lee
ro.build.display.id=ECLAIR
ro.build.version.codename=REL
ro.build.product=SGH-I897
ro.build.id=ECLAIR
ro.build.version.sdk=7
ro.product.cpu.abi2=armeabi
ro.product.manufacturer=samsung
ro.product.locale.region=GB
ro.build.date=2010. 08. 27. (???) 19:06:57 KST
ro.product.locale.language=en
ro.build.host=sep-11
ro.build.fingerprint=Samsung/

[Q] ADB Issue - device offline

A couple of days ago I flashed Eclipse v2.0, wanting to change my phone up a bit I had been on shift3r for a few weeks. Anyways, just now I was trying to copy some modules into my /system/lib/modules to overclock my device and was having issues copying within my phone. So I tried to use an adb shell to do so, but I keep getting the output of the device being offline, this is what I'm getting:
-NV57H:~$ adb devices
List of devices attached
0A3BAF200C014015 offline
And I have done a search, where some people were having trouble using certain cords, mainly with Samsung devices, and switched cords with success. This does not apply in this situation as I have used adb many times with the cord I'm using, and also I did try to switch cords anyways. Also the only other thing I saw was a situation involving driver installation and re-installation creating problems. As I am on Lubuntu, and not Windows, this does not apply to the situation because I have neither installed or re-installed drivers. My adb is setup properly because I have been using this computer for a couple weeks now and it was working previously. Any ideas on anything that could have happened? or maybe I should switch ROMs?
additionally: on my file manager, in the address bar for my device when it is plugged up, it is seeming odd to me, this is now what the address is showing for my device's sdcard:
gphoto2://[usb:002,007]/
I think I might have messed something up on my Bionic. If you read the first post I was saying how I tried adb on the same computer I've been using, AFTER flashing Liberty. Well I've gotten rid of Liberty and went back to SHIFT3R to try to fix the problem, and my problem is still looming. I have tried on Lubuntu and Windows, and my girlfriend's Incredible 2 works on both of the OS's with the same cables I'm using as well. I remember the other day when I was flashing Liberty, I had to mount my USB while in recovery to move the file onto my SDCARD because it had vanished once I tried looking for it to flash it. I remember when I tried to eject my phone from my computer (lubuntu), it said that it was busy and could not unmount the phone, after the file transfer screen went away as well. And then I waited a few minutes and tried again, it said the same thing, but I unplugged the cable anyways and unmounted USB in recovery. The file flashed fine so I know it was not still transferring the zip file. If anyone knows what I may have done or what I may be able to do to fix this let me know. I just wanted to update the thread with my most recent trials and errors in fixing it. Thanks to anyone who can guide me. I have never had issues with adb before.
O man i really hope someone can help us with this issue.
I have the same problem..
I am trying to use the path saver, and it keeps telling me device offline.
RSD lite won't even recognize it.
HELP!!!
Me too
I had the same problem... I wanted to upgrade the radio on my Bionic to the .901 load... I could not get adb to see my device.
Using Windows 7 64 bit (Ultimate).
RSD Lite would not recognize device either.
Decided "Screw it", I'll just go back to my nandroid backup... which didn't work either.... soooo... here I am.... stuck.
Off to google I went... I don't know which of these fixed it, but it is working now... here is what I did.
Found a thread that stated "run your commands from the 'C:\platform-tools' directory... so I took all of the files from the "Bionic Path Saver 1" and copied and pasted them into this directory.
Secondly, instead of just double clicking the upgrade batch file (runmebbb.bat) like I was before, I opened a DOS command shell -IN ADMINISTRATOR MODE- and ran the batch file from there.
It immediately kicked off and I was off and running.
For those of you that don't know what I am talking about, I was upgrading... using instructions from this thread:
http://forum.xda-developers.com/showthread.php?t=1433783
I hope this helps... it bugged the crap out of me... but the feeling of relief certainly makes up for it.
Well the thing is it doesn't work on windows or Linux with my bionic. I've tried various Android devices that I own and all of them work on both of my operating systems except for my bionic
Sent from my DROID BIONIC using Tapatalk
Same issu
I just installed Eclipse 2.2 on my Bionic and now i am getting the same issue. Has anyone found an answer or a fix for this? Also, does the .902 patch have anything to do with it? Any help is greatly appreciated.
Once i had this problem the only way i fixed this was by using RSDLite to flash a FXZ. Changing ROMs didnt work, nothing worked but that. It wont affect RSD reading the phone in AP Fastboot mode. Just make sure you install moto drivers and have the newest version of RSD Lite. That worked for me, now I have my adb back
Sent from my Transformer TF101 using xda premium
Are you using Safestrap recovery? If so I think that may be the issue.
Try downloading "ADB Over Wifi" from the market.
Then "adb connect iport"
The widget should show you ip/port when you activate it.
Bionic 2.2 Eclipse adb device offline
Hello,
I am having the same problem. I'm using Safestrap. Droid Bionic on the 902 update, rooted with Eclipse 2.2. Everything is fine except adb shows my device as offline. I've looked on this forum and searched and it's not the cable. Also ADB over WIFI does not work. I'm not sure why it has the result it does there should not be 2 ports...
COMMAND: adb connect 10.0.2.2:5555
RESULT: unable to connect to 10.0.2.2:5555:5555
s.wyckoff1 said:
Hello,
I am having the same problem. I'm using Safestrap. Droid Bionic on the 902 update, rooted with Eclipse 2.2. Everything is fine except adb shows my device as offline. I've looked on this forum and searched and it's not the cable. Also ADB over WIFI does not work. I'm not sure why it has the result it does there should not be 2 ports...
COMMAND: adb connect 10.0.2.2:5555
RESULT: unable to connect to 10.0.2.2:5555:5555
Click to expand...
Click to collapse
First of all, it automatically adds 5555 into your address so instead use
Adb connect 10.0.2.2 or whatever your ip is. And as far as not showing your device with a USB cord, try various other cables. I have over ten cables and maybe two work with my bionic. I urge you to use as many as possible before my next recommendation. This problem screwed with me for a couple months and finally i booted into fastboot mode and FXZd my phone. I booted my phone up after that and adb worked perfect. I don't know what causes this.
Sent from my DROID BIONIC using xda premium
Eventually I discovered why adb wasn't working. Apparently there was no adb daemon running. I came across this in a different thread awhile back. Once I copied it to my phone's /sbin/ directory (there was a link to the file in this post http://forum.xda-developers.com/showthread.php?t=974824) and ran adbd from a terminal I could use logcat. However it was removed everytime the phone cycles power so only a temporary fix. I was considering trying another rom instead of eclipse 2.2. It was also buggy in that when I tried to do an adb install it broke terminated the daemon.
If you're using linux I always do "sudo adb start-server"
Sent from my DROID BIONIC using Tapatalk 2

I Can't root my se xperia x8

I m not pro or something and i know that it this thread may be a thrash but please guys help me root my phone i have tried to root it with the superoneclick but it does fail at rageagainstthecage and i mean it stucks there i have done the usb debbuging and also i havent mounted the memory card / sd card.
I have also tried one other program DooMLoRD v4 and it also fails because all the time it tries something and it says failed failed failed ....
Could anyone help me im a newbie so i need as much help as it would be possible.
Thanks for reading.
its firmware is 2.1-update1
model number e15i
TraCegr said:
I m not pro or something and i know that it this thread may be a thrash but please guys help me root my phone i have tried to root it with the superoneclick but it does fail at rageagainstthecage and i mean it stucks there i have done the usb debbuging and also i havent mounted the memory card / sd card.
I have also tried one other program DooMLoRD v4 and it also fails because all the time it tries something and it says failed failed failed ....
Could anyone help me im a newbie so i need as much help as it would be possible.
Thanks for reading.
its firmware is 2.1-update1
model number e15i
Click to expand...
Click to collapse
install all drivers that need for x8 here and here
1. use flash tool - click PADLOCK icon
or
2. use x8toolbox
i have pc company i believe that covers it as i have read
use superoneclick
the problem is that i used superoneclick and it stucks at a point where it says rageagainstthecage
BlackRabbit1703
how do i install
X8_drivers??
turn on usb debugging then use superoneclick, try newer version...if u'r using newer then use 2.1.1..it worked for me.....have u installed gordon't gate drivers?
if superoneclick 2.1.1 not working then install gordon gate drivers then use flashtool for root
bandarigoda123 said:
turn on usb debugging then use superoneclick, try newer version...if u'r using newer then use 2.1.1..it worked for me.....have u installed gordon't gate drivers?
if superoneclick 2.1.1 not working then install gordon gate drivers then use flashtool for root
Click to expand...
Click to collapse
yes and also i have 2.3 superoneclick i just stuck rageagainstthecage for some reason
Waiting for device...
OK
Running rageagainstthecage...
OK
***IF IT KEEPS LOOPING, TRY DISABLING USB DEBUGGING NOW***
Killing ADB Server...
OK
Starting ADB Server...
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
OK
Waiting for device...
OK
Running rageagainstthecage...
i have installed the drivers but i dont know why
try with x8toolbox
stamatis16 said:
try with x8toolbox
Click to expand...
Click to collapse
i dont know how to use it correctly i select e10 then close my phone press back button then connect it to pc again
just use superoneclick 2.1.1
try it now
TraCegr said:
i dont know how to use it correctly i select e10 then close my phone press back button then connect it to pc again
Click to expand...
Click to collapse
no need for flash mode with x8toolbox, you just connect it without doing anything, with usb debuging on
stamatis16 said:
no need for flash mode with x8toolbox, you just connect it without doing anything, with usb debuging on
Click to expand...
Click to collapse
i did it with usb debugging and it shows me an error i chose 1 and then 1 and after this
processing command...
waiting for device...
running psneuter exploit on device...
unable to chmod /data/local/tmp/psneuter: no such file or directory
device not exploited!!!
this error comes.
and about superoneclick2.1 i cant use that i get an error
SuperOneClick v2.1.1.0
Checking drivers...
Killing ADB Server...
* server not running *
OK 0,05s
Starting ADB Server...
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
OK 4,05s
Waiting for device...
OK 0,03s
2.1.1
Getting manufacturer...
Sony Ericsson
OK 0,02s
Getting model...
E15i
OK 0,02s
Getting version...
-X_d
OK 0,02s
Checking if rooted...
False
OK 0,03s
Installing BusyBox (temporary)... - Step #1
2015 KB/s (1062992 bytes in 0.515s)
OK 0,55s
Installing BusyBox (temporary)... - Step #2
OK 0,16s
Rooting device... - Step #1
cannot stat 'C:\Users\TRACE\Downloads\Compressed\SuperOneClickv2.1.1-ShortFuse\Exploits\psneuter': No such file or directory
OK 0,04s
Rooting device... - Step #2
Unable to chmod /data/local/tmp/psneuter: No such file or directory
OK 0,02s
Rooting device... - Step #3
OK 0,00s
Rooting device... - Step #4
./psneuter: not found
FAILED
somehow i managed to install a program superuser
TraCegr said:
somehow i managed to install a program superuser
Click to expand...
Click to collapse
OK you should be rooted now..
To test quickly, open terminal and type:
su
followed by ENTER
If you are rooted then you'll get a prompt askinmg you to allow root access..
Good luck..
i saw that when it was rooted ehm how can i install the app 2 sd i need it

[Q] Cant get RockMyMoto to work ..and cant push files with adb

I can push files but telnet doesnt want to run them or something.
ERROR MESSAGE:
"dalvik vm unable to locate class 'rockmymoto'.
I dont think I could be anymore drained and pissed off right now. I'm trying to get 4.4 rooted. It's been SIX HOURS so far. Not sure whats wrong. I've seen that other people have had the problem and there solutions don't fix my problem.
I've reinstalled everything, drivers sdk/adb, java, motorola device drivers, etc multiple times.
I have rsdlite'd back to 4.2.2 camera update
installed motorola mobility drivers (phone says "mot composite adb device" under device manager)
I run adb and do an "adb devices" and my device shows up.
I run a adb push rockmymoto.jar /sdcard/ and also SU
I reboot
the files show up
I connect to 2222 with cylmida (*sp) impactor
obtained my ip address,
ran telnet and connected
but when I do the dalvikvm -cp /sdcard/rockmymoto.jar rockmymoto command
I get teh #$^*$# error that says "dalvik vm unable to locate class 'rockmymoto'.
#&($#& YOU MACHINE!!!!!!!!!!!!
Any idea what I am doing wrong? I have unauthorized apps installation enabled. I have usb debugging enabled. ????
If you're trying to root 4.4, I think you need to be using slapmymoto.
Sent from my XT1060 using Tapatalk
MikeG7265 said:
If you're trying to root 4.4, I think you need to be using slapmymoto.
Sent from my XT1060 using Tapatalk
Click to expand...
Click to collapse
Thanks but I'm trying to root 4.2.2 and then go to 4.4. To do that I need rock and motowpnomodofrodo. then slappy
I'm still stuck with the same dalvikvm error like it cant find the rock and su even though it was pushed with ADB. I've spent WAY too much time trying to get this working. I even had to dig out the old wireless router. and YES AP is off in my router.
Possibly an issue with case sensitivity?
nhizzat said:
Possibly an issue with case sensitivity?
Click to expand...
Click to collapse
OMG that was it. THANK YOU! The next thing I ran into was the math problem that RockmyMoto gave me. It was: a/50=? ....WTF. Thankfully i reran rock and it asked me a real math question.

[Q] ADB device unauthorized, no root, can't figure it out?

Hey, all. So, I just got a Moto X through AT&T, and I'm looking to root it. It came with the 4.4 update already on it, so I've been trying to follow the appropriate guides from jcase, but I'm running into an error very early on. After I download the ADT bundle and get adb installed and have it up and running, I was at first finding that my device wasn't showing up when I did the command "adb devices". I fixed this by getting the drivers from motorola with their device manager download, but...
Now I'm getting it showing up as an unauthorized device. I have USB debugging enabled, to start. I never received an authorization option when plugging my phone into my computer. I have it set to PTP, not MTP. I've tried toggling the USB debugging off and on multiple times, I've tried the revoke usb debugging authorization multiple times, and I've gone through and deleted the .android folder in C->Users->me. Since I don't have root, I can't go through and delete any sort of folder in my phone involving adb, because I saw that a lot as I've been doing google searches on how to try and fix this before posting here. One of my attempts when deleting .android involved me unplugging my Moto X, deleting the .android folder, running adb kill-server and then adb start-server commands, and rebooting my Moto X before plugging it back in. I still have never received an option to authorize my device.
I am running on Windows 8.1, if that makes any difference. I checked my adb version using the command, and it shows me running adb version 1.0.31. I am rather new to playing around with phones and whatnot, and all of the things I have tried were things that I found through google searches that pointed me to threads here at XDA. I'm willing to try pretty much anything, and I will report back and give further information if needed.
Thanks in advance, all
Xenther said:
Hey, all. So, I just got a Moto X through AT&T, and I'm looking to root it. It came with the 4.4 update already on it, so I've been trying to follow the appropriate guides from jcase, but I'm running into an error very early on. After I download the ADT bundle and get adb installed and have it up and running, I was at first finding that my device wasn't showing up when I did the command "adb devices". I fixed this by getting the drivers from motorola with their device manager download, but...
Now I'm getting it showing up as an unauthorized device. I have USB debugging enabled, to start. I never received an authorization option when plugging my phone into my computer. I have it set to PTP, not MTP. I've tried toggling the USB debugging off and on multiple times, I've tried the revoke usb debugging authorization multiple times, and I've gone through and deleted the .android folder in C->Users->me. Since I don't have root, I can't go through and delete any sort of folder in my phone involving adb, because I saw that a lot as I've been doing google searches on how to try and fix this before posting here. One of my attempts when deleting .android involved me unplugging my Moto X, deleting the .android folder, running adb kill-server and then adb start-server commands, and rebooting my Moto X before plugging it back in. I still have never received an option to authorize my device.
I am running on Windows 8.1, if that makes any difference. I checked my adb version using the command, and it shows me running adb version 1.0.31. I am rather new to playing around with phones and whatnot, and all of the things I have tried were things that I found through google searches that pointed me to threads here at XDA. I'm willing to try pretty much anything, and I will report back and give further information if needed.
Thanks in advance, all
Click to expand...
Click to collapse
i also use mine on MTP but im running win7
issue def sounds like you did not allow the connection. have you tried uninstalling the drivers in device manager for the phone restarting and letting windows reinstall them and see if you can get the toast on your phone and accept it.
if that fails i would try competley reinstalling everything or trying another computer, another cable, another port.
dray_jr said:
i also use mine on MTP but im running win7
issue def sounds like you did not allow the connection. have you tried uninstalling the drivers in device manager for the phone restarting and letting windows reinstall them and see if you can get the toast on your phone and accept it.
if that fails i would try competley reinstalling everything or trying another computer, another cable, another port.
Click to expand...
Click to collapse
I tried PTP because people were saying that they were having better luck with phones in PTP, not MTP. I haven't tried uninstalling the drivers yet, which might be the issue. I tried initially just plugging my phone in before I downloaded the Motorola Device Manager program, so I'll try going through and uninstalling the drivers, and the MDM program, and then reinstalling (when I get home from work).
I'll try another port, and I can also try another computer, so I'll also do that when I get home. Thanks for your response, and I'm really hoping this works :good:
Xenther said:
I tried PTP because people were saying that they were having better luck with phones in PTP, not MTP. I haven't tried uninstalling the drivers yet, which might be the issue. I tried initially just plugging my phone in before I downloaded the Motorola Device Manager program, so I'll try going through and uninstalling the drivers, and the MDM program, and then reinstalling (when I get home from work).
I'll try another port, and I can also try another computer, so I'll also do that when I get home. Thanks for your response, and I'm really hoping this works :good:
Click to expand...
Click to collapse
i looked threw a couple threads of people having this issue. this is the order i would troubleshoot myself one other thing i have read is something about unsigned drivers which i dont think you should be having any issues with it but if you ever see a window that states about unsigned drivers reboot your PC while tapping F8 and tap the down arrow till you highlight Disable driver signature required i think is what it says and see if that helps
1. drivers only(make sure you restart after you remove the drivers and make sure you check the box for delete drivers)
2. different port
3. different cable
4. complete reinstall of adb and everything.( also restart after you uninstall everything.)
5. different computer (or use virtual PC if you don't have another PC)
6. re post here lol
Hope this all helps man
dray_jr said:
i looked threw a couple threads of people having this issue. this is the order i would troubleshoot myself one other thing i have read is something about unsigned drivers which i dont think you should be having any issues with it but if you ever see a window that states about unsigned drivers reboot your PC while tapping F8 and tap the down arrow till you highlight Disable driver signature required i think is what it says and see if that helps
1. drivers only(make sure you restart after you remove the drivers and make sure you check the box for delete drivers)
2. different port
3. different cable
4. complete reinstall of adb and everything.( also restart after you uninstall everything.)
5. different computer (or use virtual PC if you don't have another PC)
6. re post here lol
Hope this all helps man
Click to expand...
Click to collapse
Thanks again, so much, for all this! I'll go through all of these in about... two hours or so. I'll report back regardless of the outcome. You're awesome for this! :highfive:
No problem man hope it fixes your problem
Sent from my XT1056 using xda app-developers app
dray_jr said:
i looked threw a couple threads of people having this issue. this is the order i would troubleshoot myself one other thing i have read is something about unsigned drivers which i dont think you should be having any issues with it but if you ever see a window that states about unsigned drivers reboot your PC while tapping F8 and tap the down arrow till you highlight Disable driver signature required i think is what it says and see if that helps
1. drivers only(make sure you restart after you remove the drivers and make sure you check the box for delete drivers)
2. different port
3. different cable
4. complete reinstall of adb and everything.( also restart after you uninstall everything.)
5. different computer (or use virtual PC if you don't have another PC)
6. re post here lol
Hope this all helps man
Click to expand...
Click to collapse
So, I've done everything in this list, and also added trying forums.motorola.com/posts/caa12135bd?commentId=725256#725256 out. I'm pretty much out of ideas, because everything I've searched showed pretty much everything you've suggested (and that I tried!) as suggestions
I appreciate the help, but so far (at this rate), I think I might just not have to root. This is super frustrating to me!
EDIT: Actually, I think I finally have something here! After hooking it up to another computer, installing the adk and everything, making sure all the drivers showed up as installed correctly and getting nothing I pretty much resided to giving up. I, for whatever reason, decided to try and run adb. After I did, and ran the start-server command, it gave me the window to accept my laptop's fingerprint! Finally on to follow the rest of the guides!
Thanks!!!
Second edit: So, proceeding to step 3 or so in RockMyMoto, I'm encountering another issue. When running Impactor and trying to run telnet on port 2222 or whatever that is, I get an error that says Signature Bugs unavailable. If I'm understanding correctly, I have to do everything in this guide to downgrade to 4.2.2 or whatever the version with the camera update is, because there isn't a root available for 4.4 without downgrading. But now I'm seeing that I somehow need to downgrade from 4.4 to the previous version in order to get Impactor/telnet working correctly?
I'm super lost now :C
well in order to root 4.4 you have to downgrade to 4.2.2 camera update. if your not sure on how to do it here is a link to a video on how to do it
http://forum.xda-developers.com/showthread.php?t=2446515
and if you are having issues with telnet here is a guide that might help
http://forum.xda-developers.com/showthread.php?t=2509676
if after reading that if you are still lost i can setup remote access via Teamviewer and show you how to do it. but only if you are comfortable with it.
dray_jr said:
well in order to root 4.4 you have to downgrade to 4.2.2 camera update. if your not sure on how to do it here is a link to a video on how to do it
http://forum.xda-developers.com/showthread.php?t=2446515
and if you are having issues with telnet here is a guide that might help
http://forum.xda-developers.com/showthread.php?t=2509676
if after reading that if you are still lost i can setup remote access via Teamviewer and show you how to do it. but only if you are comfortable with it.
Click to expand...
Click to collapse
So I'm going to work on downgrading to 4.2.2 camera update right now. Thanks for all these links and offers for help :good:. I'll report back, hopefully with a successful root
EDIT: A question for you. Am I able to run my phone in ART runtime after I root it, should I stay in dalvik or w/e it is, or does it not matter?
Xenther said:
So I'm going to work on downgrading to 4.2.2 camera update right now. Thanks for all these links and offers for help :good:. I'll report back, hopefully with a successful root
EDIT: A question for you. Am I able to run my phone in ART runtime after I root it, should I stay in dalvik or w/e it is, or does it not matter?
Click to expand...
Click to collapse
i wouldn't see why not but i am not sure
26344422579
dray_jr said:
i wouldn't see why not but i am not sure
Click to expand...
Click to collapse
Alright, cool. I'll make a backup after I'm done with everything and try it out. Maybe do some poking around here first, see if it came up at all.
I've hit a few snags, but so far I've figured everything out. I'm working on doing SlapMyMoto right now, which is the last step for root and to be on 4.4, yeah?
Xenther said:
Alright, cool. I'll make a backup after I'm done with everything and try it out. Maybe do some poking around here first, see if it came up at all.
I've hit a few snags, but so far I've figured everything out. I'm working on doing SlapMyMoto right now, which is the last step for root and to be on 4.4, yeah?
Click to expand...
Click to collapse
correct
dray_jr said:
correct
Click to expand...
Click to collapse
I didn't want to bug you with this, so I had made a post over in the SlapMyMoto thread, but I'll put it up here. If you don't wanna bother, I'll hang around in the SMM thread and wait for a response.
"I've done everything from 1-3, including accepting and installing the OTA update to 4.4. I'm trying to run the last command in step 4, the adb shell stuff, but literally nothing is happening. I still have access from motowpnomo, I checked using the write_protect command, and it is still showing a "0" I don't know what to do at this point, though.
USB Debugging is on, adb devices shows my phone as being connected correctly
This is a screen cap of what my command prompt shows after I input that command from step 4
http://i.imgur.com/WeekMAf.png
Any suggestions?"
Xenther said:
I didn't want to bug you with this, so I had made a post over in the SlapMyMoto thread, but I'll put it up here. If you don't wanna bother, I'll hang around in the SMM thread and wait for a response.
"I've done everything from 1-3, including accepting and installing the OTA update to 4.4. I'm trying to run the last command in step 4, the adb shell stuff, but literally nothing is happening. I still have access from motowpnomo, I checked using the write_protect command, and it is still showing a "0" I don't know what to do at this point, though.
USB Debugging is on, adb devices shows my phone as being connected correctly
This is a screen cap of what my command prompt shows after I input that command from step 4
http://i.imgur.com/WeekMAf.png
Any suggestions?"
Click to expand...
Click to collapse
everything looks fine bro just finish the last command and then run root checker you should be fine.
i know when i ran mine nothing happened also, after the last command wait a few mins if nothing happens toggle Bluetooth like is says and if it does not restart then restart the phone and you should be good if not we will figure it out
i might downgrade just to run back threw it to see if i can figure it out and maybe put together a package for you that i know works. but i am on the sprint X
dray_jr said:
everything looks fine bro just finish the last command and then run root checker you should be fine. i know when i ran mine nothing happened also, after the last command wait a few mins if nothing happens toggle Bluetooth like is says and if it does not restart then restart the phone and you should be good if not we will figure it out
Click to expand...
Click to collapse
I'm confused again; when I run the last command (I literally just copypasted the entire fourth step command into my command promt), I get an error.
http://i.imgur.com/yr11VjL.png
Screenshot of after I type in the last command
I'm about to head out to work, so I'll be able to work on this later tonight, but if you have any suggestions I would be super appreciative (not to say that I already am not!)
Xenther said:
I'm confused again; when I run the last command (I literally just copypasted the entire fourth step command into my command promt), I get an error.
http://i.imgur.com/yr11VjL.png
Screenshot of after I type in the last command
I'm about to head out to work, so I'll be able to work on this later tonight, but if you have any suggestions I would be super appreciative (not to say that I already am not!)
Click to expand...
Click to collapse
no no do them one by one
adb shell
enter
cp /sdcard/install.sh /data/local/tmp/install.sh
enter
chmod 755 /data/local/tmp/install.sh
enter
echo "/data/local/tmp/install.sh" > /sys/kernel/uevent_helper
enter
and the device should restart
im running a nandroid backup as we speak and im going to revert back to the 4.2.2 camera update and run threw it again see if i can't figure out what is hanging u up.
dray_jr said:
no no do them one by one
adb shell
enter
cp /sdcard/install.sh /data/local/tmp/install.sh
enter
chmod 755 /data/local/tmp/install.sh
enter
echo "/data/local/tmp/install.sh" > /sys/kernel/uevent_helper
enter
and the device should restart
im running a nandroid backup as we speak and im going to revert back to the 4.2.2 camera update and run threw it again see if i can't figure out what is hanging u up.
Click to expand...
Click to collapse
Alright, I tossed the adb stuff on my flash drive, and I'm going to see if I can try this at work. I'll report back. You are going above and beyond to help me out, and it's just amazing. After my last community being the League of Legends community, I'm not used to this! :highfive:
dray_jr said:
no no do them one by one
adb shell
enter
cp /sdcard/install.sh /data/local/tmp/install.sh
enter
chmod 755 /data/local/tmp/install.sh
enter
echo "/data/local/tmp/install.sh" > /sys/kernel/uevent_helper
enter
and the device should restart
im running a nandroid backup as we speak and im going to revert back to the 4.2.2 camera update and run threw it again see if i can't figure out what is hanging u up.
Click to expand...
Click to collapse
Running each of the commands works, until the last one. I get "can't create /sys/kernel/uevent_helper: Permission denied" error message
EDIT: I got it! Yeah!! :highfive: I found someone suggesting to take the phone back to 4.2.2 with this error message and redo SMM, and it stuck! Downloaded root checker, and I got a congrats result! Thanks so much, mate! You've been such a huge help; I was going to give up the first night before I even decided to post here!
I'm glad to hear you got it rooted finally if you have any other questions or need any ideas on what to do please feel free to pm me anytime
Sent from my XT1056 using xda app-developers app
i've got one for you... running windows 7, 32 bit. Eset AV-disabled.. have 4.2.2 rooted, but can't get moto-wp-nomo to successfully run...any ideas?

Categories

Resources