Trying to do a backup but adb pull isn't working - 7" Kindle Fire HD Q&A, Help & Troubleshooting

Hi all
So I'm doing step 1 of this guide but I seem to be having problems..
I did install the ADB drivers on my comp, installed SDK, and set the directories in PATH. ADB is turned on in the Kindle. But when I try to do the backup commands, I get a "remote object xxxxxxxxxxx does not exist"
Anyone have any idea what's going on here? I appreciate your help!

Any ideas?

I think you're on the wrong partition...

Rushead said:
I think you're on the wrong partition...
Click to expand...
Click to collapse
What do you mean? Sorry, I'm total noob with adb in general (and I just got the Kindle like a couple weeks ago )
I should add that when I do the first command the Kindle responds to it (as in the screen turns on when I send the command). Don't know if that helps you.

You need to pull from the correct directory. I think that's your only problem.

Thanks for your response.
How do I pull from the right directory? I'm using the code from the thread that's apparently supposed to work for everyone, don't know what's going wrong on my end :s

Are you rooted? Did you allow adb on the Kindle? Are you running as administrator in windows?

Rushead said:
Are you rooted? Did you allow adb on the Kindle? Are you running as administrator in windows?
Click to expand...
Click to collapse
Yeah I'm rooted (I have root access on the phone but no superuser app ever popped up when I rooted), adb is on in the Kindle, and I am running cmd as admin. :s

Hovo said:
Yeah I'm rooted (I have root access on the phone but no superuser app ever popped up when I rooted), adb is on in the Kindle, and I am running cmd as admin. :s
Click to expand...
Click to collapse
You can't run cmd as an Admin. You have to actually be using the Admin profile on your PC.

I'm on the admin account on my computer as well. Typing "adb devices" shows the device on the list, I don't understand why the backup code doesn't work.

Hovo said:
I'm on the admin account on my computer as well. Typing "adb devices" shows the device on the list, I don't understand why the backup code doesn't work.
Click to expand...
Click to collapse
The code works. It's just not finding your boot img.
Does your kindle boot normally?

Yep, I haven't installed the second bootloader yet because I wanted to backup the device first.
BTW, for what it's worth, the error happens with all 4 items the code is meant to backup; the system, recovery, bootloader and bootblock.

It sounds like adb is not enabled, though you said it is. Have you tried a factory reset?

Decided to give it another go this morning, and I feel so silly...
The adb shell was asking for root access this entire time, I never saw it until now though...
Thanks for all your help and sorry for makin you run around in circles. :s

Related

[Q] Hero CM7 RC2 stable I think!

flashed CM7 RC2 I think month or so ago. Phone's been running fine slow but fine. Today Im texting the gf and look down and see blank wall paper. Reboot teh phone htc screen comes up vibrates then starts over. Cant do **** with this think besides stick down the front of my pants! Ive powered and booted to hboot, fastboot etc., cant get it to go into recovery any help would be greatly appreciated before I have a stroke!
FAIL. This should be in Q+A. Can you start ADB and access the device? Are you s-off? How did you root the phone? What have you tried? What recovery do you have? Can you read? Is the battery full? Did you search?
well since I rooted the phone about 2 [email protected]##ing years ago memory does not serve. S-off dont know does it do that when you flash the rom or install clockworkmod recovery or the several other steps that you follow when you flash the new ROM? If you have to flash it with the image then no that wasn't an option when I loaded this ROM.
ADB automatically starts when the system boots so I don't have to start it, yes its running no I cannot see the device. Battery was about 75% when the screen went blank.
Im going to ignore the can you read and should be in the Q&A comment el duce as this is the place where the experts play and the other 10000 questions about boot looping reside. Does anyone wanna help or just be an a...?
Questions don't belong in the Development section <---please click link and read....moved to general...
TMcGuire17 said:
well since I rooted the phone about 2 [email protected]##ing years ago memory does not serve. S-off dont know does it do that when you flash the rom or install clockworkmod recovery or the several other steps that you follow when you flash the new ROM? If you have to flash it with the image then no that wasn't an option when I loaded this ROM.
ADB automatically starts when the system boots so I don't have to start it, yes its running no I cannot see the device. Battery was about 75% when the screen went blank.
Im going to ignore the can you read and should be in the Q&A comment el duce as this is the place where the experts play and the other 10000 questions about boot looping reside. Does anyone wanna help or just be an ass?
Click to expand...
Click to collapse
I might be an a.., but I am helping, that's why I asked a bunch of questions. You are not s-off, you would know if you were. ADB is a program you use on your computer, not the phone. I asked because you can flash a recovery image using ADB even though the phone won't boot - so my new question here would be do you have ADB on your computer? You should have ADB if you rooted a long time ago, before there were 1-click root methods. I would recommend charging your phone, since many reboots would kill it. Wait til the charging light turns green. Once it's green boot into the bootloader, then access your phone via ADB and see if recognizes the device. If it does we can work from there. As to your BS about posting in dev because it felt better, that's lame as hell, I would have helped in q+a as well, but I would've been less of an ass because you were posting in the correct section. Anyway, charge it up, and reply if you know how to use ADB or not, then we can move on.
EDIT: I just reread your posts, did you say you can boot into your ROM, just not recovery? If so you can also flash a recovery image using terminal emulator. Let me know.
@TMcGuire17
Let’s take the aggression down about 5 notches and remember that when asking for help it is important to post in the correct section. The fact that you want your question answered quickly does not change the fact that this thread has no place in development. XDA is not tech support and while members can be very helpful you should not expect answers from anyone. When you have to search for the answer or figure out a solution…you are able to learn…understand…and then help others…and that is what XDA is about. Calling people names is never acceptable...I have edited your post. I am tempted to close this thread but I will leave it open in the hopes that you find your answer…but any more name calling or bickering and this thread is closed.
@il Duce
Thanks for helping...but next time leave out the "FAIL. This should be in Q+A" and just report the post...it is only going agitate the situation.
Thanks!
krook6023 (mod team)
krook6023 said:
@il Duce
Thanks for helping...but next time leave out the "FAIL. This should be in Q+A" and just report the post...it is only going agitate the situation.
Thanks!
krook6023 (mod team)
Click to expand...
Click to collapse
LOL ok my bad. I get angry. It's the Irish in me.
Well there you have it! Im as Irish as they come any good conversation between Irish is gonna start with either a beer or a fight. Now that intro's are over....I do have adb loaded need to update it. I'll be back later to check it out and see if I can access the device.
Peace
TMcGuire17 said:
Well there you have it! Im as Irish as they come any good conversation between Irish is gonna start with either a beer or a fight. Now that intro's are over....I do have adb loaded need to update it. I'll be back later to check it out and see if I can access the device.
Peace
Click to expand...
Click to collapse
Scotch-Irish actually, red beard to prove it, lol. You shouldn't need to update your adb If you have adb, and on windows, and it's old, try this: open command prompt from your start menu. type "cd C:\android-sdk-windows\tools" (or just copy paste that with no quotes) then type "adb devices" and if it says "random numers phone" like "2222555555 HTC recovery" or whatever, you're good. Report back.
I updated the sdk because everytime I run that adb devices command I get a command not recognized as an internal or external command. Wanted to make sure there wasn't an issue with it being out of date. My directory is c:\androidsdk\tools\adb devices
The adb services is running
TMcGuire17 said:
I updated the sdk because everytime I run that adb devices command I get a command not recognized as an internal or external command. Wanted to make sure there wasn't an issue with it being out of date. My directory is c:\androidsdk\tools\adb devices
The adb services is running
Click to expand...
Click to collapse
So now does it show your device?
sent from a series of tubes.
No it still wont execute the command
If it does, type "adb shell" enter "su" enter "flash_image recovery /sdcard/nameof yourrecovery.img"
Thanks il Duce. If I get adb running Ill try it and post back.
TMcGuire17 said:
I updated the sdk because everytime I run that adb devices command I get a command not recognized as an internal or external command. Wanted to make sure there wasn't an issue with it being out of date. My directory is c:\androidsdk\tools\adb devices
The adb services is running
Click to expand...
Click to collapse
Hey TMcGuire, If you updated to the latest SDK, the new path for ADB is no longer \Tools (unless you moved a bunch of files) Try c:\androidsdk\platform-tools
TMcGuire17 said:
I updated the sdk because everytime I run that adb devices command I get a command not recognized as an internal or external command. Wanted to make sure there wasn't an issue with it being out of date. My directory is c:\androidsdk\tools\adb devices
The adb services is running
Click to expand...
Click to collapse
This is not the correct path. Try typing "cd C:\androidsdk\tools" enter, then try "adb devices" OH YEAH and do you know if you had usb debugging on in the phone settings? You may have to run the RUU if you didnt. That can be done from fastboot, but try the other command first, then the flash command.
Edit, platform tools like posted above mine, sorry I dont have the new sdk.
sent from a series of tubes.
Thanks guys. Yes I have the new sdk and I did find the correct directory for the adb. I can run it now but still no device. Im not sure if I had debugging on or not I thought it did but.......ran adb shell device not found. How about a quick tut on fastboot!
so here is where Im at. fastboot lists my device. I've try to flash the rom from fastboot but no go. Tried to copy the ROM renamed update.zip to the sdcard via fastboot then I was gonna run update but it returned: sending '/sdcard' (72819 KB) FAILED (sounds familiar )(remote not allow)
TMcGuire17 said:
Thanks guys. Yes I have the new sdk and I did find the correct directory for the adb. I can run it now but still no device. Im not sure if I had debugging on or not I thought it did but.......ran adb shell device not found. How about a quick tut on fastboot!
Click to expand...
Click to collapse
look here:http://forum.xda-developers.com/showthread.php?t=958968
read the info, I think jasonmaloney put the zip you need near the end of the thread.
Read, tried failed. It wont push anything to the device. Always comes back as failed remote: not allow

4X extremely slow after rooting/reboot

So, I followed the guide we all did here:
http://forum.xda-developers.com/showthread.php?t=1818502
And before someone asks: I have deleted the Backup app (IS11LG_SystemBackupTest.signed.apk) we had to install during rooting after the phone was rooted.
The phone then happily ran, rooted. SUpersu was installed/updated, the phones root check said it's all perfect, I was a happy camper. But today I had to reboot it. I can't say if it was the first reboot after rooting, sadly. The phone boots up, arrives at the lockscreen (some colorful defaultthing, before I get to see my GO Locker screen after login), and then stops being responsive, it basically at first feels like it's not reacting at all. Some things are responsive, strngely ... I get accurate sounds when touching the screen for instance. If I then wait, I eventually get to the SIM Unlock ... which is also totally unresponsive, it will maybe show two digits, then freezes up. Strangely, I could type the remaining digits and hit OK and the SIM would unlock ... but the screen no longer showed what I typed. I then arrive at GO locker, can unlock it (sluggish and slow again) and finally am properly logged in, but still totally sluggish and slow. Needles to say it's a pseudobrick that way, unusable.
What's going on and what could I check?
Please try the following:
alexp999 said:
REALLY SLOW AFTER ROOT?
Remove the "SystemBackupTest" app, if you haven't already.
On your phone, go to "Settings -> Developer options" and make sure "USB debugging" is TICKED
Connect your phone via USB to your computer.
Open a command prompt (may need admin privelages, right click, run as administrator)
Type without quotes "cd C:\o4xr" and press enter.
Type without quotes "adb shell rm /data/local.prop" and press enter.
Type without quotes "adb reboot" and press enter.
Click to expand...
Click to collapse
alexp999 said:
Please try the following:
Click to expand...
Click to collapse
Thanks, that fixed it! It's not easy to do, as the scrolling lists do not work, either, and you can't seem to get to the developer options, it won't scroll. Strangely enough "internally" it seems to do things ... if you re-enter the options, they're down to the end of the list, it looks like it doesn't update the screen properly (much like when I had to enter the SIM code).
Anyway, it's fast again, whew ... I was scared. What is the local.prop thing, if I may ask?
voon said:
Thanks, that fixed it! It's not easy to do, as the scrolling lists do not work, either, and you can't seem to get to the developer options, it won't scroll. Strangely enough "internally" it seems to do things ... if you re-enter the options, they're down to the end of the list, it looks like it doesn't update the screen properly (much like when I had to enter the SIM code).
Anyway, it's fast again, whew ... I was scared. What is the local.prop thing, if I may ask?
Click to expand...
Click to collapse
I'm not entirely sure, I just know it gives us temp root for the rest of the root script to run.
Hm, so its' not a systemwide ini file or so, that existed before ... it was created during the above rooting process and was an undesired leftover from it? I'm always a bit worried if I delete something with such an unspecific name in the OS
voon said:
Hm, so its' not a systemwide ini file or so, that existed before ... it was created during the above rooting process and was an undesired leftover from it? I'm always a bit worried if I delete something with such an unspecific name in the OS
Click to expand...
Click to collapse
Its actually created by the SystemBackupTest app.
The script then removes it just before issuing a reboot.
The only way it can come back, is if you accidently open that app again before uninstalling it.
alexp999 said:
Its actually created by the SystemBackupTest app.
The script then removes it just before issuing a reboot.
The only way it can come back, is if you accidently open that app again before uninstalling it.
Click to expand...
Click to collapse
I see, I might have done that ... good to know. Anyway, great that it works again, thanks again
laggy phone
My lg 4x hd is very slow after root...
I just tried to make this few steps above, but I got this message.
Any idea what to do?
Pls help me!
THX
66aaa
66aaaa said:
My lg 4x hd is very slow after root...
I just tried to make this few steps above, but I got this message.
Any idea what to do?
Pls help me!
THX
66aaa
Click to expand...
Click to collapse
It looks like you have either plugged in more than one android device, or you have an android emulator (from the SDK I guess) running. Unplug all USB devices (except keyboard and mouse) and then try again. Good luck!
If you have an emulator running try "adb -d shell rm /data/local.prop"
Edit: To see all adb-devices type "adb devices". This will return a list of all adb-devices connected (emulators + usb devices)
Dexxon said:
If you have an emulator running try "adb -d shell rm /data/local.prop"
Edit: To see all adb-devices type "adb devices". This will return a list of all adb-devices connected (emulators + usb devices)
Click to expand...
Click to collapse
I still don't understand and hope you do it...
THX for your help!
As you can see the same device is listed two times. Restarting the adb server may help. Just type "adb kill-server" and than launch the second command from your screenshot. Maybe this works.
Dexxon said:
As you can see the same device is listed two times. Restarting the adb server may help. Just type "adb kill-server" and than launch the second command from your screenshot. Maybe this works.
Click to expand...
Click to collapse
This is the result...what to do know?
THX
The devices is detected and the command is executed, but the file does not exist. Make sure that there is a file "prop.local" at /data. If not, you may have a different problem.
Maybe you have an emulator running or Bluestacks installed... Uninstall Bluestacks...
I don't think that this is the case as the device shows up with a serial number in the "adb devices" list.
To be sure it is the correct phone you could compare the serial number shown in the list with the serial number of your phone (you might find this information in settings -> about phone).
Dexxon said:
The devices is detected and the command is executed, but the file does not exist. Make sure that there is a file "prop.local" at /data. If not, you may have a different problem.
Click to expand...
Click to collapse
I don't have in the system/data "prop.local" file...sure....
What is emulator and Bluestacks?
I really don't understand this problem I have...
Could you help me pls?
THX
66aaaa said:
I don't have in the system/data "prop.local" file...sure....
What is emulator and Bluestacks?
I really don't understand this problem I have...
Could you help me pls?
THX
Click to expand...
Click to collapse
An emulator is a program which emulates Android so you can execute Android-Apps on your PC. BlueStacks is an emulator. It may show up as an adb devices, but this is not the case here.
Back to your problem: Are you sure the rooting process worked?
Did you reboot your phone after rooting?
I didn't root my phone under ICS so I don't have any experience with this
no one raised this question to confirm or did this info was provided anywhere
What version of ROM? ICS V10x? JB V20x? User could had used the wrong guide.
Best way out is to do a reflash and retry rooting if all fails.
Dexxon said:
An emulator is a program which emulates Android so you can execute Android-Apps on your PC. BlueStacks is an emulator. It may show up as an adb devices, but this is not the case here.
Back to your problem: Are you sure the rooting process worked?
Did you reboot your phone after rooting?
I didn't root my phone under ICS so I don't have any experience with this
Click to expand...
Click to collapse
I dont't have this Bluestacks emulatur, sure...
I have Superuser working properly on JB V20 stock ROM. The only thing it is very slow sometimes, Thats why I tried to make the process above...
I made the root few month ago...and rebooted many times since than...
Any idea what to do now?
THX

Getting "device offline" with adb after 4.4 OTA

This is just weird. I went back to stock to get the 4.4 OTA. Done, now I want to reinstall TWRP and I'm getting the device offline error. Debugging is on, drivers are installed . . . what stupid mistake have I made?
OK - oddly, I reinstalled the sdk and it works. Who knows?
robsw said:
This is just weird. I went back to stock to get the 4.4 OTA. Done, now I want to reinstall TWRP and I'm getting the device offline error. Debugging is on, drivers are installed . . . what stupid mistake have I made?
OK - oddly, I reinstalled the sdk and it works. Who knows?
Click to expand...
Click to collapse
I'm having the same issue, but reinstalling the sdk didnt help.... im lost, i really want this root
robsw said:
This is just weird. I went back to stock to get the 4.4 OTA. Done, now I want to reinstall TWRP and I'm getting the device offline error. Debugging is on, drivers are installed . . . what stupid mistake have I made?
OK - oddly, I reinstalled the sdk and it works. Who knows?
Click to expand...
Click to collapse
nickfromfresno said:
I'm having the same issue, but reinstalling the sdk didnt help.... im lost, i really want this root
Click to expand...
Click to collapse
try turning off/on usb debuggin.. also try revoking the usb debug auths.. check your adb version to be 1.3x..those should fix it
kreegaa said:
try turning off/on usb debuggin.. also try revoking the usb debug auths.. check your adb version to be 1.3x..those should fix it
Click to expand...
Click to collapse
I have this same issue. Device shows up in "adb devices" but, shows to be "offline."
I'm running Windows8, adb version 1.0.29, with an MotoX (ATT). I cd to "platform-tools" to run adb.
---------------------------
Ok, I solved it by locating the 1.0.31 adb files here: http://forum.xda-developers.com/attachment.php?attachmentid=1724500&d=1360704125
I unzipped and replaced the adb files in the "platform-tools" folder with the ones from the above link. My issue was that the older adb files weren't causing the MotoX to prompt me to verify access from my computer. Updated adb files caused the prompt. Once, I verified my computer access - all is good!
shaneaus said:
I have this same issue. Device shows up in "adb devices" but, shows to be "offline."
I'm running Windows8, adb version 1.0.29, with an MotoX (ATT). I cd to "platform-tools" to run adb.
Any suggestions?
Click to expand...
Click to collapse
You need adb version 1.0.32 or above. I had the same problem.
m0biusace said:
You need adb version 1.0.32 or above. I had the same problem.
Click to expand...
Click to collapse
in linux this can be a sign that you need to run ADB as SUDO.
nickfromfresno said:
I'm having the same issue, but reinstalling the sdk didnt help.... im lost, i really want this root
Click to expand...
Click to collapse
There are a couple other things to try.
One, just get the latest ADB platform tools and see if your device shows up online using that adb.
The other thing would be to delete the adb keys on your phone. Remove /data/misc/adb/adb_keys.

[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?

using osx to unlock bootloader???

first, i have already unlocked my bootloader using windblowz on a boot camp partition of my mac. BUT, since android is a unix-like os, and osx is a unix-like os, FOR MY OWN EDUCATION, i want to be able to use the osx terminal to do this stuff to my n6.
so here's what i tried, and none of it works... as in, none of it even results in any like link between my phone and my osx computer.
1) i watched this youtube video from droidmodderX, and followed it to the letter:
https://www.youtube.com/watch?v=aUkcWlknFsE
from the time he plugs his n6 into his mac, NOTHING he says will happen, actually happened. it was as if i had plugged the phone into nothing. He says NOTHING about installing the android SDK for osx in his video. sooo....
2) next, i install the android SDK for osx, thinking droidmodderX was just careless in his video, and forgot to mention that you need to do this. NOTHING. i open the terminal and run the various fastboot commands from the root directory... NOTHING. using the terminal, i change over to the directory where i actually put the SDK, and then run the fastboot/adb commands from terminal again, and NOTHING. I tried this with the phone in fastboot, and with the phone not in fastboot, and NOTHING.
so how do you get osx to talk to this phone with fastboot/adb commands using the terminal?
fwiw, android file transfer works fine in the gui, so i know the physical connecction is good.
also, fwiw, i did use the search function and someone asked a similar question about his n5 about a year ago... and got no answer. not a single one.
-peter
If you run "./adb devices" without quotes does it see the phone at all? Make sure you have the most up to date SDK for OS X and also make sure you update the platform-tools in the SDK manager.
Check this thread out, might help a bit.
EDIT: Try running the commands as root/sudo.
I used this method on my MacBook Air to root my device without any issues. Make sure that you are in the correct folder when executing the commands. The first time it should ask you for your password. Also make sure that you have USB debugging enabled on your phone and that you are in the bootloader. You can also try to download Android File Transfer (google it) and see if it works with your phone. Hope that this helps.
You're aware that the bootloader on the Nexus 6 can be unlocked simply by toggling "Enable OEM Unlock" under Developer Settings, right?
With that said, I agree that it is smart to keep up with proper ADB/Fastboot commands as those are the most sure fire way to get you out of a pinch.
I have had absolutely no issues using Terminal to perform Fastboot commands on my Nexus 6 using my Mac with OSX Yosemite. As long as you get it setup correctly you should have no issues.
I just dug up the detailed instructions I used to get my Mac setup for this. Start from scratch, follow these instructions and you should be good to go:
http://forum.xda-developers.com/showthread.php?t=1917237
geebee1932 said:
I used this method on my MacBook Air to root my device without any issues.
Click to expand...
Click to collapse
what method? can you be more specific? did you mean to put in a link describing the "method"?
geebee1932 said:
Make sure that you are in the correct folder when executing the commands.
Click to expand...
Click to collapse
I ran all the fastboot commands, to the letter, from the youtube video, from the terminal, in the folder where i had the SDK. nothing....
geebee1932 said:
The first time it should ask you for your password.
Click to expand...
Click to collapse
It didn't.
geebee1932 said:
Also make sure that you have USB debugging enabled on your phone and that you are in the bootloader.
Click to expand...
Click to collapse
I did.
geebee1932 said:
You can also try to download Android File Transfer (google it) and see if it works with your phone. Hope that this helps.
Click to expand...
Click to collapse
As I said in my original post, I already have Android File Transfer, no need to google it. It works great. Had it for years.
I made some headway when I started using ./adb before each command. It sees my device now and when i ran ./adb help, it put out a list of commands and switches in the terminal, that I'm starting to play with. thanks for the ./adb clue. that was a biggie now using ./adb i can reboot and boot into bootloader. but for example "./adb fastboot oem lock", (without the quotes), does nothing. (i used "oem lock" as a test, because the bootloader is already unlocked)
-peter
geebee1932 said:
I just dug up the detailed instructions I used to get my Mac setup for this. Start from scratch, follow these instructions and you should be good to go:
http://forum.xda-developers.com/showthread.php?t=1917237
Click to expand...
Click to collapse
thanks mate. that's the second reference to that link. it must be good
and geebee, sorry i sounded so douchey. i know you're trying to help. i was frustrated.
-peter
pcrussell50 said:
thanks mate. that's the second reference to that link. it must be good
and geebee, sorry i sounded so douchey. i know you're trying to help. i was frustrated.
-peter
Click to expand...
Click to collapse
No worries at all - I was frustrated myself until I found the YouTube video. I think after ./ you need a space before you use the command line. What I did was put the CF auto-root folder (unzipped) on my desktop. I renamed the folder CF to make it easy. I opened the folder and doubled clicked on the Mac file. It should open and say just press enter - it will not work. Keep the folder open and open up the terminal. Here is what I had to do.
Put the phone is download mode with "Start" appearing - then plug into computer. (make sure debugging on)
cd /Users/mycomputername/desktop/CF - I needed a space after cd
paste and copy the 3 sudo commands (with the sudo) out of the CF folder one at a time - pressing enter after each.
The first enter - you should be asked for your password.
Mike
Going well now guys thanks. I like having two unix-like devices (osx computer and android handset), talking without needing drivers.
-peter
sn0warmy said:
You're aware that the bootloader on the Nexus 6 can be unlocked simply by toggling "Enable OEM Unlock" under Developer Settings, right?
With that said, I agree that it is smart to keep up with proper ADB/Fastboot commands as those are the most sure fire way to get you out of a pinch.
I have had absolutely no issues using Terminal to perform Fastboot commands on my Nexus 6 using my Mac with OSX Yosemite. As long as you get it setup correctly you should have no issues.
I just dug up the detailed instructions I used to get my Mac setup for this. Start from scratch, follow these instructions and you should be good to go:
http://forum.xda-developers.com/showthread.php?t=1917237
Click to expand...
Click to collapse
Hello everyone,
I'm in the same boat, except my device won't show up under devices in transmission after the "./adb devices" command.
Got a Nexus 6, 2009 Macbook running OSX Mavericks. I followed http://forum.xda-developers.com/showthread.php?t=1917237 to a T, but no luck. Android File Transfer works just fine. Usb debugging and oem unlock is checked on my phone, I restarted both phone and computer. Any advice/guidance/direction would be greatly appreciated, thanks!

Categories

Resources