Database Info

cannot access adb and cannot bypass registration?

ok so i downloaded the SDK and the windows drivers. i downgraded the phone to rc29 and have just enabled adb on the phone using the command <enter>setprop persist.service.adb.enable 1<enter> and <enter>telnetd<enter>. i opened up CMD in windows and changed the directory where i needed and tried to run adb and it gave me this error: "* daemon not running. starting it now *
* daemon started successfully *
error: device not found"
why did it give me this error? and alo im stuck at the part where im supposed to "copy a busybox binary" using adb push. i dont know exactly what im supposed to do to do that step. i am a noob at this stuff so please be kind and use noob terms and steps.
Thanks
PS: i did connect the phone to the pc with the data cable and the add new hardware thing popped up and i installed the drivers like i was supposed to. it said something about they were installed correctly but may not be working properly, whatever that means.

Try this....
Unplug the phone.
Reboot the computer.
When fully rebooted, plug the phone back in and see what the computer does.
Did it say, "Found new hardware" or some such message?
Did it say that it couldn't find a driver?

Okay - after the OTA updates, I'm now having the same problem! Ouch!
Plugging in, running DOS Command...
c:\> adb devices
Reports that there are no devices attached!
BUG!!!!!!!!!!!!!!!

[Q] rooting samsung

please i want to ask some few questions.
How can i root my samsung galaxy s and be free of complications? i have tried the z4root once and it wasnt able
to root my device........is there anythin i did wrong? i just copied the apk file to the internal memory of the
phone and clicked on root n it started but along the way the phone hanged and i had to put it off and on and
the device was still the same unrooted
Is there any one click method that i can use like the application
z4root and how exactly can i use it cos i have read conflicting guides on how to use some of these one click apps
If i successfully root my samsung galaxy s can i still be eligible for updates? presently i have 2.1 eclair
installed and my kies tells me that i can update the firmware but my internet connection is very very slow and
i have tried like 4 times and cant update thru kies cos the network always times out. please is there any other
safe method of upgrading? i have actually read about odin but dont really get the guidelines straight.

from what I have heard z4 has a habit to hang. At least on the SGS model I have *Samsung Mesmerize*
It will hang once. Pull Battery to reboot and run again. It should take 2nd time.
No clue why .. just seems to be the case.
You know for sure its rooted if afterwards there is a APP called Superuser in your app drawer.
SuperoneClick seems to hang for me also .. Z4 has been the most surefire way I have seen.
Not sure of eligibility or Kies .. Probably have to unroot at least for update then root again. As for Kies I am in the States and not available here.

thanks for the reply
well, am so glad for ur reply. I have tried twice and it hanged ...........i also saw in a post that debugging has to be on. is it necessary to do it with or without a sim card and please how long did it take u to root urs cos mine stays almost 2 hours b4 hanging and i leave it another two hours before putting it off. I havent tried pulling the battery and rebooting and when it hangs i just leave it and dont even try it that same day again.
I will try it out the way u said n see if it will work out. Thanks again for ur reply

As mentioned before z4 will hang, sometimes it needs to be done a few times. It will definitely work on Galaxy S using Android 2.1 but it apparently won't root it successfully on Android 2.2 (Rogers at least, I'm not sure about AT&T).
Click to root and if it doesn't complete within 15 minutes then pull the battery, restart and try again. Do it until it roots, it will work. Don't wait 2 hours, there's no point and there's no harm in pulling the battery.
If you have Android 2.2 you'll probably need SuperOneClick.
EDIT: You have to be using USB Debugging and you can have a SIM card in there.

thanks a lot again i will continue doing it until it roots ...................glad i have someone that can help...........will still get back to u

SuperOneClick will work and i highly recommend it. It can also hang but if you follow these steps you will be fine.
Enable USB Debugging on your device.
Connect device to PC (do not mount USB)
Make sure drivers have installed. (check device manager)
Turn device off
Run SuperOneClick and select 'Root'
When you see 'waiting for device..' , turn device on and wait.
The program should run through until the end now without any further intervention. Congrats, you are rooted!
In this state, (rooted with stock ROM), you will still be able to receive OTA updates. If you want to go furthur, perhaps try a custom ROM or two, i suggest installing Rom Manager from the market. With that you can flash a custom recovery, back-up your entire device (nandroid), and then proceed to flashing a custom ROM. (In that order!)
Just remember that once you have a custom recovery in place you will no longer be able to receive OTA updates. If you have gone ahead and tried it you can always roll back by re-installing your nandroid backup. (Once you are back to your stock ROM a restart will put you back to stock recovery again too).
Hope this helps.

please DirkGently1, i really appreciate ur reply to my post but i am confused on some certain areas
1 Connect devive to PC (do not mount USB)
please what do u mean by do not mounth usb ? do u mean do not mount memory card or something am not getting
2 for the drivers, i already have kies and use it with my galaxy s and i believe the drivers should already be installed ..........else i need to install them again
3 does turn device off device mean the galaxy s should be turned off after it has been already connected to the pc cos ur 2nd step said connect device to pc
please am sorry for asking more questions .............just that am still not very clear on the super one root method. Thanks for your cooperation

Hi mate,
When you connect to PC you will see a new icon in the notification bar. When you pull the bar down you will see the notification 'USB connected' or something similar. Click on the notification and it will give you the option to 'mount USB'. Just ignore it!
I'm not sure what kies is? As long as your PC recognises your phone when it is plugged in you are ok.
Connect the phone to the PC via USB cable with USB Debugging enabled on the phone so that the PC 'sees' it. Then turn it off. Only turn it back on once SuperOneClick is running, 'root' selected and 'waiting for device..' comes up on the PC.
It's easier than it sounds. Good luck my friend.

thanks again for the clearification ...................will give it a try if zroot cant root my galaxy s

ok i have tried it but finally succeded after a lot of unplugging and plugging usb and clicking on debugging but i was asked if i wanted to test and i clicked yes and it stuck on the testing
this is what i got
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 rageagainstthecage...
9 KB/s (5392 bytes in 0.584s)
OK
chmod rageagainstthecage...
OK
Running rageagainstthecage...
OK
***IF IT KEEPS LOOPING, TRY DISABLING USB DEBUGGING NOW***
Killing ADB Server...
* server not running *
OK
Starting ADB Server...
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
OK
Waiting for device...
OK
Running rageagainstthecage...
OK
***IF IT KEEPS LOOPING, TRY DISABLING USB DEBUGGING NOW***
Killing ADB Server...
* server not running *
OK
Starting ADB Server...
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
OK
Waiting for device...
OK
Running rageagainstthecage...
OK
***IF IT KEEPS LOOPING, TRY DISABLING USB DEBUGGING NOW***
Killing ADB Server...
* server not running *
OK
Starting ADB Server...
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
OK
Waiting for device...
OK
Running rageagainstthecage...
OK
***IF IT KEEPS LOOPING, TRY DISABLING USB DEBUGGING NOW***
Killing ADB Server...
* server not running *
OK
Starting ADB Server...
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
OK
Waiting for device...
OK
Running rageagainstthecage...
OK
***IF IT KEEPS LOOPING, TRY DISABLING USB DEBUGGING NOW***
Killing ADB Server...
* server not running *
OK
Starting ADB Server...
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
OK
Waiting for device...
OK
Running rageagainstthecage...
OK
***IF IT KEEPS LOOPING, TRY DISABLING USB DEBUGGING NOW***
Killing ADB Server...
* server not running *
OK
Starting ADB Server...
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
OK
Waiting for device...
OK
Running rageagainstthecage...
OK
***IF IT KEEPS LOOPING, TRY DISABLING USB DEBUGGING NOW***
Killing ADB Server...
* server not running *
OK
Starting ADB Server...
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
OK
Waiting for device...
OK
Running rageagainstthecage...
ROOTED
Getting mount path...
/dev/block/stl9
OK
Remounting system with read-write access...
OK
Pushing su...
231 KB/s (26264 bytes in 0.111s)
OK
chmod su...
OK
Pushing Superuser.apk...
376 KB/s (196521 bytes in 0.510s)
OK
Remounting system with read-only access...
OK
Running a SU test...
it seems not to finish running the SU test, am i rooted?

I'm not sure I haven't used this method, but check your app drawer for the superuser app, if it's there you're rooted

With z4 when the phone reboots, you tried to reopen it? the phone should ask you to give permission to Superuser you click "accept"

yes there is super user ap in my drawer. so how do i speed up my device now that am rooted

First get titanium backup to backup all your stuff then I guess you could go check out oclf (one click lag fix) to speed up the phone. Check out the captivate forum though, there's plenty of suggestions and help in there too. Congrats on the root.

thanks again on the tip i already have titanium backup and its saying my phone isnt rooted............its the only app saying that i wouldnt know why

You have to make sure you allow it root access when you first start the application. If you don't it will tell you that it's not being given root access. Also if you did z4 root did you temp or permanent root it? If you only temp rooted that will go away when you restart your phone. We'll need some more details here.

This is what you're looking for, I have done this myself (Captivate) and it worked perfectly

i didnt get the zroot 2 work 4 me so i used superoneclick and have rebooted a lot of times and still have root access to other apps its still the titanuim backup that is still different

Try opening your superuser app and check if titanium backup was denied root access or not. What does it say in there?
From my captivate to you.

Rooting
Hi Mate, Im not 100% sure, but I think Rageinthecage is a virus. Kasperskys says it is. be careful!

help rooting One X

I'm trying to root my phone using the method here: http://forum.xda-developers.com/showthread.php?t=1709424
without much luck... On page 33 one person mentioned getting to Daemon successfully started and having it just hang there, which is my problem, then said it was just dumb user error with never explaining what it was. Several people followed up with the same problem but no answer. Initially I started it up and it would just start up the daemon and sit, so I rebooted my phone to try again and now it doesn't even do that, it just spits out Exploit by beaups, script by designgears and sits there with a blinking cursor.
Phone is in charge only mode, USB Debugging enabled, HTC sync not running, have tried multiple USB cables and ports. I have a mac and am trying this through VirtualBox (and yes, the USB device for the phone is attached - not mounted as a disk). I can only guess this is what's causing the problem but I don't really see why it shouldn't work. Anything I can try?

Did you set the date on the phone forward a day or 2 before you tried again, like the thread says?
I didn't use this root method (rooted back on 1.73). But another person posted having similar troubles. Reinstalling the HTC drivers did the trick for that person.

redpoint73 said:
Did you set the date on the phone forward a day or 2 before you tried again, like the thread says?
I didn't use this root method (rooted back on 1.73). But another person posted having similar troubles. Reinstalling the HTC drivers did the trick for that person.
Click to expand...
Click to collapse
Date doesn't really come into play since the installer doesn't go anywhere. What HTC drivers? There's no mention of those. On a whim I installed HTC Sync and rebooted, I do get farther but don't seem to really get anywhere still. It does more stuff but seems like it keeps killing the server and a check for software updates finds nothing to update.
Exploit by beaups, script by designgears
* server not running *
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
adb server is out of date. killing...
* daemon started successfully *
** daemon still not runningerror: cannot connect to daemon
adb server is out of date. killing...
* daemon started successfully *
** daemon still not runningerror: cannot connect to daemon
adb server is out of date. killing...
* daemon started successfully *
** daemon still not runningerror: cannot connect to daemon
adb server is out of date. killing...
* daemon started successfully *
** daemon still not runningerror: cannot connect to daemon
Go to Settings, ATT Software update, check for updates.
Waiting for device to Reboot...
adb server is out of date. killing...
* daemon started successfully *
** daemon still not runningerror: cannot connect to daemon
adb server is out of date. killing...
* daemon started successfully *
error: more than one device and emulator
error: more than one device and emulator
error: more than one device and emulator
error: more than one device and emulator
error: more than one device and emulator
error: more than one device and emulator
error: more than one device and emulator
error: more than one device and emulator
error: more than one device and emulator
error: more than one device and emulator
error: more than one device and emulator
error: more than one device and emulator
error: more than one device and emulator
error: more than one device and emulator
Done! Rebooting...
error: more than one device and emulator
Press any key to continue . . .
Click to expand...
Click to collapse

Well I realized that last attempt had HTC Sync running, so I killed that. Now I'm back to sitting at daemon successfully started. For fun I tried to do the non one click root, however indeed after doing the first command I get the more than one device or emulator connected error. adb devices lists my phone once initially, but after running: adb shell rm /data/data/com.redbend.vdmc/lib/libvd*
adb devices lists my phone multiple times and I can go no further. I might have to try and find a real windows computer to use, maybe the vm is just doing something funky here.

chadcf said:
What HTC drivers? There's no mention of those. On a whim I installed HTC Sync and rebooted.
Click to expand...
Click to collapse
The drivers get installed with HTC Sync. So re-installing Sync would have fixed the drivers, if that was causing the issue. Sorry I can't help you anymore than the suggestions I've already made. Hopefully, somebody else can help.

chadcf said:
Well I realized that last attempt had HTC Sync running, so I killed that. Now I'm back to sitting at daemon successfully started. For fun I tried to do the non one click root, however indeed after doing the first command I get the more than one device or emulator connected error. adb devices lists my phone once initially, but after running: adb shell rm /data/data/com.redbend.vdmc/lib/libvd*
adb devices lists my phone multiple times and I can go no further. I might have to try and find a real windows computer to use, maybe the vm is just doing something funky here.
Click to expand...
Click to collapse
That's a typical VM issue. You can run right from linux or mac with the manual method. Just get the right version of ADB for your O/S and add a ./ before each command that starts with "adb".

Bootloop after Trickdroid tweaks

Hello Forum,
I have a problem with my Htc One S today i installed Trickdroid 8.0 and it worked fine so i wanted to install the tweaks too. So i selected what i wanted and when the phone started it got stuck at the bootloader screen. I thought it just needed some time but after 15 minutes i gave up and turnt it off. Then i went into the recovery to install the rom newly but it always says it can't mount the sd card. Already relocked the bootloader and tried to install the europe ruu 1.78 but i got error 131 i have read that might be, beacause mine was branded by T-Mobile (but no simlock or else)
Really need help appreciate any answer

Really no one knows how i can fix this ? Need to fix it pretty soon because i need my phone :/ I can't even turn mine off, so i just let the battery die don't think that's to good either

Boot into recovery and ref lash. What tweak did you do? Not all work with 8.0. Tweaks have not been updated for this version. Make sure to do a full wipe.

j0hnh0lmes said:
Boot into recovery and ref lash. What tweak did you do? Not all work with 8.0. Tweaks have not been updated for this version. Make sure to do a full wipe.
Click to expand...
Click to collapse
I can't reflash in recovery, because it always says "can't mount sd card"
Don't remember all of the tweaks i did but i did the nova launcher, remove sense, some apps, all of the tweaks on the first page and some other.

Okay now I did a "clear storage" and a "reset to factory defaults" with a stock recovery and after that i reinstalled the custom recovery again. Now I can access the sdcard again but it's empty of course. Then i bootet in recovery and tried to push the trickdroid zip on to the sdcard via adb like this "adb push Trickdroid_v8.0.0.zip /sdcard/Trickdroid_v8.0.0.zip" but then it says:
daemon not running starting it now on port 5037
daemon started successfully
protocol failure
and simply ends. How can I push the Rom really need help, because my phone has no rom at all right now ?
ah okay needed to use the adb in the android sdk folder not in the little fastboot folder i had it just worked

Not at home to double check your command line--sounds like that is issue
But, you can type adb devices first to see if phone is recognized
I usually cd to the directory I have adb/fastboot files in, put zip on C: root
and type: adb push C: "then the rest"

rugmankc said:
Not at home to double check your command line--sounds like that is issue
But, you can type adb devices first to see if phone is recognized
I usually cd to the directory I have adb/fastboot files in, put zip on C: root
and type: adb push C: "then the rest"
Click to expand...
Click to collapse
Thanks for your help but as i have written i already got it back working thread can be closed

Sorry,
I posted before your edit showed up--

Glad to hear.

steps for next time
Hi, just before the thread is locked.
What has helped me in more of these occassions:
1. Make sure you read the install instructions of the ROM builder (I overlooked the 'flash Boot.img' which was added after some version)
2. Make sure you don't 'custom' work your memory (no partitioning etc).
3. First install the ROM and do REQUIRED afterwork (most often: Data/factory reset. Which doesn't wipe your photo's or just your account information and saved settings that will interfere with new rom options)
4. after making sure it boots and it reboots.
5. If this is the case, make sure you get the tweak package pointed out by the rom builder.
6. If all else fails, first read up on XDA and rom builder's site (often community on XDA) THEN start actions well informed.

[Q] ADB device not found

Hi, I've try to setup other languages to my moto g, and rename framework-res.apk from system/framework to framework-res.apk.bak :crying: So my device can't boot up. And i have trouble in service menu, if i select any point in menu device will reboot right away. work now.
I've tried to use ADB, but
c:\adb>adb shell
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
error: device not found
How can i fix ADB or whole problem?
fix system by [GUIDE] Moto G - Restore stock firmware
abd still not work.

Download the official drivers from Motorola, install, boot into fastboot, choose the last point and let the several drivers install.
Then you have adb access.
If this doesn't work the first time, try again, firstly removing all drivers in Windows.

Using Linux Mint, after installing fastboot, I had to run fastboot command in root in order to get my Moto G reconnized (without root, the command was pending forever with a "< waiting for device >"

shaftenberg said:
firstly removing all drivers in Windows.
Click to expand...
Click to collapse
Solution, thanx.

shaftenberg said:
Download the official drivers from Motorola, install, boot into fastboot, choose the last point and let the several drivers install.
Then you have adb access.
If this doesn't work the first time, try again, firstly removing all drivers in Windows.
Click to expand...
Click to collapse
Hi I accidentally wiped the internal storage of my Moto G XT1033, since the OS is lost now my phone is stuck at bootloader warning. I can access TWRP recovery. In device manager I can see Google Nexus ADB Interface. And in taskbar (safely remove hardware and eject media) phone is recognized as Eject XT1032. But in file explorer/My computer I can't see the phone.
I've tried adb shell command and I am getting the same error:
C:\Minimal ADB and Fastboot>adb shell
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
error: device not found
and with adb devices command following error:
C:\Minimal ADB and Fastboot>adb devices
List of devices attached
(this line/area is blank)
C:\Minimal ADB and Fastboot>
Can you please explain this step? I am not getting it.
boot into fastboot, choose the last point and let the several drivers install.
I went into fastboot mode but my pc is not installing any drivers and showing same adb shell error. (phone drivers are already installed I uninstalled and reinstalled them)
How can I fix ADB or this problem? Please help
Update:
Problem solved with USB OTG

Did you check device manager on pc with phone plug to usb, to look if some driver is missing???
Enviado desde mi [email protected]|¢0π usando Tapatalk 2

xtrover said:
Did you check device manager on pc with phone plug to usb, to look if some driver is missing???
Enviado desde mi [email protected]|¢0π usando Tapatalk 2
Click to expand...
Click to collapse
Thanks problem solved with USB OTG

Juste300 said:
Thanks problem solved with USB OTG
Click to expand...
Click to collapse
Hi, sorry for answer in an old post but I have a similar error with my Moto G with
"C:\Minimal ADB and Fastboot>adb shell
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
error: device not found"
But I don't understand what do you mean with the problem it's resolved with USB OTG (sorry but I'm so newby with the Moto G, I come from a Xperia U)
many thanks for all the help

Skarsnik said:
Hi, sorry for answer in an old post but I have a similar error with my Moto G with
"C:\Minimal ADB and Fastboot>adb shell
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
error: device not found"
But I don't understand what do you mean with the problem it's resolved with USB OTG (sorry but I'm so newby with the Moto G, I come from a Xperia U)
many thanks for all the help
Click to expand...
Click to collapse
The above error came on my phone too; my case was I accidentally wiped out my phone internal storage while installing a new custom rom. When internal storage of phone is wiped out then we can't install/access the custom rom because storage is formatted. Also 1st generation Moto G does not has external memory slot which might help to install the custom rom from memory card.
So the solution of above problem is get an OTG cable, attach your USB flash drive with your phone via OTG cable. Put your custom rom in flash drive in a folder. Then in TWRP recovery Menu install your custom rom by accessing flash drive. That's it.

Hi all,
I have a XT-1033 Moto G with dual Sim and I have a Google and Padlock screen. The phone was not rooted and had the standard 4.4.4 ROM. When I saw your post Juste300 I thought it might help me get the phone back in working order, however, when I do the Vol Down/Power button I get a list of option all of which are not familiar to me:
Normal Powerup
Recovery
Factory
Barcodes
BP Tools
QCOM
The Normal and Factory just send me back to the Google padlock and right now I'm waiting for the battery to charge enough so I can swap it for the USB OTG key with the XT1033_Retail_Asia_444_Optimized_v1.1.zip on it (should have I unpacked the zip onto the key, or is it okay still zip packaged?). I tried with the XT1033_Retail_Asia_444_Stock_Untouched.zip but there's something hinky with the zip because copying it onto the usb key got as far as 60 MB and no further after ten minutes...
Anyway, from that list of choices what should I do?
Thanks in advance for any help!
B
---------- Post added at 01:32 PM ---------- Previous post was at 12:56 PM ----------
Update:
Tried the Recovery option - goes back to the Google lock screen for a mo, there's a flash at the top of the screen like a menu bar, then there's a dead android on his back with the hatch open and a red exclamation mark sign. Eventually, the phone reboots back to Google lock.
B
B
---------- Post added at 02:09 PM ---------- Previous post was at 01:32 PM ----------
Here's a screenshot:
http://www.dropbox.com/s/ff4b5bf08ak5zv7/IMG_20150629_140200048_HDR.jpg?dl=0
B
PS. Barcodes shows barcodes for the IMEI, product code and so on.

I think I have a similar problem... Tried to flash the lollipop 5.1 update, but accidentally used the GPe version for my non-GPe XT1039... Now I'm stuck at the bootloader, and every option gives me a google lock screen. ADB doesn't seem to see the device any longer... Is it bricked?

I think I may as well bin mine. I spoke at length with Motorola support last night and the upshot was that they'd send me a replacement after I sent mine to the states and that replacement would still cost me $200 - hardly worth it when I could just buy a new one for half that price.
What a waste.
B

finnfather said:
I think I may as well bin mine. I spoke at length with Motorola support last night and the upshot was that they'd send me a replacement after I sent mine to the states and that replacement would still cost me $200 - hardly worth it when I could just buy a new one for half that price.
What a waste.
B
Click to expand...
Click to collapse
I'm getting the same screen as you: Google and padlock.. But I get that whatever option I select. So I can't access any recovery to do anything.. and fastboot doesn't seem to see the phone either... Is that it for mine too then?

shaftenberg said:
Download the official drivers from Motorola, install, boot into fastboot, choose the last point and let the several drivers install.
Then you have adb access.
If this doesn't work the first time, try again, firstly removing all drivers in Windows.
Click to expand...
Click to collapse
what is the last point here?