[Q] Getting error with ADB shell - General Questions and Answers

"daemon still not runningerror cannot connect to daemon"
I keep getting this error, no matter what I have tried, I can't fix it. I have all the latest update, and drivers should be downloaded because it was working at some point.

James_Caliber said:
"daemon still not runningerror cannot connect to daemon"
I keep getting this error, no matter what I have tried, I can't fix it. I have all the latest update, and drivers should be downloaded because it was working at some point.
Click to expand...
Click to collapse
what is your phone info? make model spl radio kernel ect...

Related

Rogers 2.2 update is available through Kies

Yep...Go get it.
EDIT: I mean Kies...The update box was in my way when I was typing lol
So what is the ROM version name?
A.VOID said:
So what is the ROM version name?
Click to expand...
Click to collapse
Just a min, update failed...I think cause launcher pro was the default home...trying again damn it.
Someone post a odin copy.
?
Let the BRICKING begin!
Would love an ODIN of this ROM... looking forward to it!
Installed Kies... Update process starts but Kies crashes. Anyone else have this issue? I'm currently trying to unroot to see if that makes a difference.
Edit: Exact issue is: MSC.Thunder.FirmwareUpdate has stopped working.
Does it regardless if I choose to backup or not the contacts and data.
Edit 2: Unroot changes nothing.
Edit 3: Doing a factory reset on the device doesn't help either. WTF?
connected to Kies - message "This device will be supported soon"
Fortysixandtwo said:
connected to Kies - message "This device will be supported soon"
Click to expand...
Click to collapse
http://www.samsung.com/ca/support/detail/supportPrdDetail.do?menu=SP00&prd_ia_cd=01012200&prd_mdl_cd=SGH-I896ZKARWC&prd_mdl_name=SGH-I896&prd_ia_sub_class_cd=P#
Get it here
Wonder if it'll be 2.2.1...
Ok so I just got back from writing an exam and will try to reinstall Kies. I tried 2 times to update through my computer this morning and once on my wife's PC (She has a Captivate as well)
All 3 attempts it says that Its downloaded the update but then it fails when it tries to install. Now remember I've not rooted or anything, so i think that there might be a newer version of kies or something...going to look now.
But anyways it tries to update it says a bunch of stuff like: You phone Jsomething1 and the update is supposed to be Jsomething2...I dont get it.
Remember I dont hack or mod phones in the slightest, so I have no clue what this J1 (mine) and the update of j2 is...?
The update is big though, takes a few minutes to download and I have a 16mps download speed...
Downloading this version of Kies and will try again:
http://www.samsungapps.com/about/onPc.as
I'm with Rogers with an AT&T Captivate (Rooted and Cognition 2.3b6). Will I be able to update my device to it? I much prefer the Rogers software than AT&T's. I don't care if I have to use Odin or erase everything.
alexvtr said:
Installed Kies... Update process starts but Kies crashes. Anyone else have this issue? I'm currently trying to unroot to see if that makes a difference.
Edit: Exact issue is: MSC.Thunder.FirmwareUpdate has stopped working.
Does it regardless if I choose to backup or not the contacts and data.
Edit 2: Unroot changes nothing.
Edit 3: Doing a factory reset on the device doesn't help either. WTF?
Click to expand...
Click to collapse
What ROM are you on ?
Did you put the phone in recovery mode when you have the first pop up menu ?
ScottyNuttz said:
Wonder if it'll be 2.2.1...
Click to expand...
Click to collapse
Nope it's 2.2
Where does it say it was released?
gunstar3035 said:
Ok so I just got back from writing an exam and will try to reinstall Kies. I tried 2 times to update through my computer this morning and once on my wife's PC (She has a Captivate as well)
All 3 attempts it says that Its downloaded the update but then it fails when it tries to install. Now remember I've not rooted or anything, so i think that there might be a newer version of kies or something...going to look now.
But anyways it tries to update it says a bunch of stuff like: You phone Jsomething1 and the update is supposed to be Jsomething2...I dont get it.
Remember I dont hack or mod phones in the slightest, so I have no clue what this J1 (mine) and the update of j2 is...?
The update is big though, takes a few minutes to download and I have a 16mps download speed...
Click to expand...
Click to collapse
Did you put your phone in Recovery mode like the first pop up is asking ? (Unplug usb cable from phone (not the computer), power off the phone, Hold vol up/down button and plug usb cable. You should now be in download mode (black/yellow screen with a shovelling droid)
silvertag said:
What ROM are you on ?
Did you put the phone in recovery mode when you have the first pop up menu ?
Click to expand...
Click to collapse
Stock ROM from Rogers
No, not recovery mode.
PC runs W7-32 for what it's worth.
In the meantime, I did some research on the error I mentioned above.
It appears it's a very common issue with KIES.
There are a few workarounds.
So far, I tried the "SIM-out" method and it doesn't work for me.
Next, I'm trying the regedit method.
Will report on results.
@silvertag: your upgrade worked fine or you haven't tried yet?
Enhanced said:
Where does it say it was released?
Click to expand...
Click to collapse
Nowhere you have to check Kies server to know it's been released. There is still no confirmation from Rogers last i checked.
alexvtr said:
Stock ROM from Rogers
No, not recovery mode.
PC runs W7-32 for what it's worth.
In the meantime, I did some research on the error I mentioned above.
It appears it's a very common issue with KIES.
There are a few workarounds.
So far, I tried the "SIM-out" method and it doesn't work for me.
Next, I'm trying the regedit method.
Will report on results.
@silvertag: your upgrade worked fine or you haven't tried yet?
Click to expand...
Click to collapse
Yes it worked fine you HAVE to put the phone in download mode before you start downloading the update or it will fail at the upgrade part.

[Q] 3.1 @rooted devices

OK, so why does 3.1 update fail on a rooted device ?
The only thing I did when rooting my device was to replace
the "su" program. If I revert that change, will the OTA update
work ?
Anybody has the original "su" and it's mode settings (ls -l) ?
Thanks,
rudi
PS: Actually, I guess we need the "su" from 3.0.1 ...
But to get "su" on there in the first place, you likely had to flash your boot.img.
The update checks your system and boot.img to verify that it's stock before proceeding, as applying patches to modded files will likely have craptastic results.
What method are you using to update? What specific error message are you getting on the failure?
Yeah, so if reverse the boot.img and "su" package, the original
update should work ?
I don't remember the error message, I got the OTA update, and
it basically failed. Has not shown up again ...
Thanks,
rudi
FYI, I was able to root my xoom without loosing any data following these steps:
http://www.mydroidworld.com/forums/...ow-manually-update-your-xoom-3-1-3-0-1-a.html
luudee said:
I don't remember the error message, I got the OTA update, and
it basically failed. Has not shown up again ...
Click to expand...
Click to collapse
Weird...I'm rooted...got the OTA update, hit Install now, it went through the countdown process to reboot and install update, but then nothing happend. No reboot, no error message. I manually shutdown and turned on the device and got nothing.
Is that what happened to you?
--Q
Yeah, that's what happened to me as well. It looks like it will install the update,
but than shows some message for a second and than shows the android with
the Explanation mark (Warning sign).
If you check, you will see that you are still using 3.0.1 ... (At least that was my case).
Follow the post i referenced above, it is easy, safes all your data and gives
you 3.1 and root.
Cheers,
rudi
Thanks...that was my original plan, but then I got the OTA notification and figured I'd do that instead. Guess not! LOL
--Q

adb push

do im trying to flash the new radio cause im testing out my battery to get my max performance but i cant adb push.........do i need to update the drivers and SDK platform?
i havent use adb at all expect when i rooted and thats it.....so i kinda forgot how
Flipnfr3ak said:
do im trying to flash the new radio cause im testing out my battery to get my max performance but i cant adb push.........do i need to update the drivers and SDK platform?
i havent use adb at all expect when i rooted and thats it.....so i kinda forgot how
Click to expand...
Click to collapse
Hi,
if you still have Adb from your original S-off'ing, then just install the latest HTC Sync, and this will update your drivers.
Should then be able to flash radio without issue.

Galaxy S3 Root on Verizon

Hey all. Unfortunately, I can't post in the development forum because this is my seventh post. :crying: Anyways, I had a comment about the verizon root and hopefully somebody can either move this to that sticky or answer... Anyways...
I wanted to see what was done to the modified image to make sure nothing strange was put in it. I downloaded the 'orig' from fus, extracted the image, and ran a md5 check on all the files. I then downloaded your system.img file and ran a md5check on all the files. I found two files were added...
#
330a331
> 65bd72996c68f289c5fa0b81f0874127 app/Superuser.apk
2007a2009
> d1a9de9724c662a50a9a128e48b1fb37 xbin/su
#
When I tried to find the versions of those files and the md5 hashes, they don't match. Here's your version...
65bd72996c68f289c5fa0b81f0874127 app/Superuser.apk
d1a9de9724c662a50a9a128e48b1fb37 xbin/su
I then downloaded 'superuser' from http://androidsu.com/superuser/, which I'm assuming is the source. For the 3.1.3 version, I get this...
MD5 (system/app/Superuser.apk) = e0bc7b7284b68c9539b6ec6b306310e0
MD5 (system/bin/su) = 054c9a22d8900d50ce6172fd56bbf414
For the 3.2-RC2 version, I get this...
MD5 (system/app/Superuser.apk) = d0abb9413f712f2f7dd43ed47df6c2d8
MD5 (system/bin/su) = 96c672c1339da363232f42dd87b4a3cf
As you can see, the md5's are different which make me a little uneasy about it. I was wondering if anybody knew of the source for these. I think I just email'ed invisiblek the same thing, but don't know if it would get to him or not. Maybe somebody else knows the answer.
Thanks!
WTF?
Im confused, I see active topics saying the S3 hasn't got root yet due to the locked boot loader, I also see active topics saying it has been unlocked + rooted..
answer
OK, I still haven't got my s3, so I haven't tried it. But from what I read, you can flash a custom system.img and put su and supervisor.apk on it. This allows you to get 'root' on the device. Here's a reference...
http://forum.xda-developers.com/showthread.php?t=1756885
Verizon Failed on on Odin now stuck at SIII boot screen
wiz561 said:
OK, I still haven't got my s3, so I haven't tried it. But from what I read, you can flash a custom system.img and put su and supervisor.apk on it. This allows you to get 'root' on the device. Here's a reference...
http://forum.xda-developers.com/showthread.php?t=1756885
Click to expand...
Click to collapse
Verizon Failed on on Odin now stuck at SIII boot screen
I tried the procedure with rooted.system.img and Odin 3.07 and it threw root Xmit Write fail. Then it just hung.
I pulled the battery and now it won't boot. I tried doing Vol Up + Home to do a hard reset to no avail.
I also tried Samsung-Updates.com-SCH-I535_VZW_1_20120705143513_fti2qg2lmf file through Odin with no success.
I've rooted phones in the past but never through this method.
I'm hoping I haven't bricked it.
I have a spare 16 GB card if I can recover something that way.
I can't reactivate my old Rezound because now the SIM card is invalid and they are two different sizes so I can't use the new one in the old phone.
1. Bootloader is [still] locked
2. Root has been achieved
Solved the problem. I tried a better micro usb cable and a different usb port.
Everything went great after that. I'm now rooted fully.
daffy113 said:
Verizon Failed on on Odin now stuck at SIII boot screen
I tried the procedure with rooted.system.img and Odin 3.07 and it threw root Xmit Write fail. Then it just hung.
I pulled the battery and now it won't boot. I tried doing Vol Up + Home to do a hard reset to no avail.
I also tried Samsung-Updates.com-SCH-I535_VZW_1_20120705143513_fti2qg2lmf file through Odin with no success.
I've rooted phones in the past but never through this method.
I'm hoping I haven't bricked it.
I have a spare 16 GB card if I can recover something that way.
I can't reactivate my old Rezound because now the SIM card is invalid and they are two different sizes so I can't use the new one in the old phone.
Click to expand...
Click to collapse
..
The answer is that this type of question doesn't belong in the dev threads, but in the S3 Q&A forum. If MD5 doesn't match, then you have a bad download or bad copy, or the posted MD5 is incorrect.
Unable to Root VZW SG3
I have been unable to download the Samsung ADB interface driver for my phone. So I can't root using Debugs ADB root method. Is there something I need to do in order to get ADB installed for my device so it can recognize my phone?
luisdr007 said:
I have been unable to download the Samsung ADB interface driver for my phone. So I can't root using Debugs ADB root method. Is there something I need to do in order to get ADB installed for my device so it can recognize my phone?
Click to expand...
Click to collapse
Download works in Droidstyles guide.
http://forum.xda-developers.com/showpost.php?p=28530394&postcount=1
prdog1 said:
Download works in Droidstyles guide.
http://forum.xda-developers.com/showpost.php?p=28530394&postcount=1
Click to expand...
Click to collapse
thanks, but not sure what you mean. i've clicked on the link but not sure where to go. I see the section for windows OS, but not sure what to download.
luisdr007 said:
thanks, but not sure what you mean. i've clicked on the link but not sure where to go. I see the section for windows OS, but not sure what to download.
Click to expand...
Click to collapse
Here is direct link from Samsung.
http://www.samsung.com/us/support/owners/product/SCH-I535MBBVZW
Click see all downloads>software
prdog1 said:
Here is direct link from Samsung.
Click see all downloads>software
Click to expand...
Click to collapse
thank you. i will uninstall the current drivers, reboot, and install these and see what happens.
prdog1 said:
Here is direct link from Samsung.
Click see all downloads>software
Click to expand...
Click to collapse
I tried installing drivers again, but no avail. i keep getting "There was a problem installing this hardware, SAMSUNG Android ADB Interface. This device is not configured correctly. (code 1)" Not sure what else to do.
Did you reboot the PC
prdog1 said:
Did you reboot the PC
Click to expand...
Click to collapse
I uninstalled, rebooted, and then installed new drivers, and still getting that error. I can't seem to figure out what the problem is. I also installed Kies, and SDK, and still can't get to work.
luisdr007 said:
I uninstalled, rebooted, and then installed new drivers, and still getting that error. I can't seem to figure out what the problem is. I also installed Kies, and SDK, and still can't get to work.
Click to expand...
Click to collapse
Need to reboot PC after drivers are installed and make sure usb debug is turned on in phone settings.
prdog1 said:
Need to reboot PC after drivers are installed and make sure usb debug is turned on in phone settings.
Click to expand...
Click to collapse
ok, I did not reboot after I installed drivers. USB debugging is checked on the phone. Let me reboot PC and I will keep you posted. thank you very much for you help with this. I'm not new to rooting, but I am new to the Samsung phones. I've had the DX for the last 2 years, and never had issues rooting or flashing ROMS.
prdog1 said:
Need to reboot PC after drivers are installed and make sure usb debug is turned on in phone settings.
Click to expand...
Click to collapse
So I rebooted and I'm not getting the error. But adb is still not recognizing my device.
luisdr007 said:
So I rebooted and I'm not getting the error. But adb is still not recognizing my device.
Click to expand...
Click to collapse
ADB shows mine as offline emulator.

Issues trying to use flashtool

I am trying to use flash tool and I keep getting errors at the end and my phone will not boot up after.
The most recent one said 'processing of modern.sin finished with errors'
Anyone know a way to fix this? I have tried downloading different regions but I haven't managed to get one to flash correctly. I tried running software repair after each try and it fails as well.
Thanks
nikekicks said:
I am trying to use flash tool and I keep getting errors at the end and my phone will not boot up after.
The most recent one said 'processing of modern.sin finished with errors'
Anyone know a way to fix this? I have tried downloading different regions but I haven't managed to get one to flash correctly. I tried running software repair after each try and it fails as well.
Thanks
Click to expand...
Click to collapse
Reinstall the drivers.
Use back panel to connect your device.

Categories

Resources