Hey i just bought this tablet yesterday and rooted it with framaroot and it went fine. The volume however is very low for me so i read up on how to boost it by first decompiling framework-res.apk changing some value thingy and then recompiling it and signing it. well what i did next was copy the modded apk to my tablet (using windows explorer copy+paste, no adb pushing as i probably should have...?) and then using Root Browser on my tablet go to /system/framework/ and i renamed the original one so i can copy the modded one. but then some popups started happening like a lot and finally i just restarted it. now its stuck in a boot loop!!
i connected the device and i have DroidExplorer installed and it could see it. so i tried now "adb shell" in cmd prompt and then "su" but nothing happened. just a blank new line. $ didnt change to #
then i heard u need the Superuser.apk in the system/app folder so i tried motochopper and i saw that it copied it but there was lots of errors while the motochopper run.bat was executing. anyway i rebooted the phone by pressing the power button and volume down for a few seconds and now my computer cant even see the device anymore! (as MTP or anything)
this sucks hardcore. all i need is to just delete the modded framework-res.apk and rename the original file back to its original name but i have no idea how to do this now. what are my options? is this FUBAR or wut?
adb shell now says this:
C:\adt-bundle-windows-x86_64-20130917\sdk\platform-tools>adb shell
* daemon not running. starting it now on port 5037 *
ADB server didn't ACK
* failed to start daemon *
error: cannot connect to daemon
i dont have CWM installed or anything btw. i just got it yesterday so i didnt have time to do much with it.
your help is really appreciated!!
sorry if this is in the wrong section im kinda new here
I couldnt fix it so i thought i return it the place i bought it. i played stupid and they didnt even ask me if i rooted it or wut not. they made an exchange. im super lucky!
haha nice!
Related
Hey, so I was trying to enable non-market apps through ADB. Everything was going good until I typed in "adb reboot" and then stupidly unplugged the cable.
Now the phone doesn't do anything, can't boot Android, only the recovery menu. It just shows the intro movie and then shuts down. I've tried deleting user data and clearing cache from recovery which doesn't help.
I do have a NANDROID backup for it, both on the phone and on my PC (which was made with Clockworkmod Recovery). But the problem is that I don't have the update.zip for Clockwork on the /sdcard, it's in /titaniumbackup. How can I put the update.zip on the /sdcard of a bricked Captivate?
when you boot in recovery, does ur computer recognize the device if connected with usb? If so you can use adb to relocate files, droid explorer may even work.
Oh thanks, I had no idea ADB would work in recovery, gonna try that and get back to you.
As you can see I'm still new to Android. Dumped iPhone 3G for Captivate. But I'm learning!
So Droid Explorer won't install because it doesn't like 64bit Windows.
ADB can connect, but I can't put any file on the device (I've tried the "adb push" command) or gain root, says permission denied. Please help!
EDIT: Never mind, by some miracle of God it all worked out and let me adb push all I needed, I'm in Clockwork Recovery and my phone is gonna be OK.
i have droid explorer running on my intel, windows 7 ultim 64x rig. works.
you just have to make sure you dl the 64 bit version of the program. Here's a link:
http://de.codeplex.com/releases/49896/download/139717
you also need .net framework 3.5 sp1 at least. I installed the newest one and it works regardless.
im glad you managed to unbrick your device. Kudos.
Can anyone please help me out with my problem trying to root my phone.
What I did so far was:
Downloaded the samsung usb driver
USB debugging is on
downloaded superoneclick 1.7
connected phone to the computer using original USB cord.
opened superoneclick, changed to rageagainstthecage and clicked root
the following message resulted from doing this.
-----------------------------------------------------
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...
cannot stat 'C:\Users\k\rageagainstthecage': No such file or directory
OK
chmod rageagainstthecage...
Unable to chmod /data/local/tmp/rageagainstthecage: No such file or directory
OK
Running rageagainstthecage...
--------------------------------------------------------------------
After running rageagainstthecage, the superoneclick program just doesn't do anything else, and eventually freezes. PLEASE HELP. I been searching through forums for a while now, and I see other people with the same problem but it hasn't been resolved.
Try it again using the "Psneuter" method. That worked for me.
Sent from my SGH-T959V using XDA Premium App
phokingjuice said:
Can anyone please help me out with my problem trying to root my phone.
What I did so far was:
Downloaded the samsung usb driver
USB debugging is on
downloaded superoneclick 1.7
connected phone to the computer using original USB cord.
opened superoneclick, changed to rageagainstthecage and clicked root
the following message resulted from doing this.
-----------------------------------------------------
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...
cannot stat 'C:\Users\k\rageagainstthecage': No such file or directory
OK
chmod rageagainstthecage...
Unable to chmod /data/local/tmp/rageagainstthecage: No such file or directory
OK
Running rageagainstthecage...
--------------------------------------------------------------------
After running rageagainstthecage, the superoneclick program just doesn't do anything else, and eventually freezes. PLEASE HELP. I been searching through forums for a while now, and I see other people with the same problem but it hasn't been resolved.
Click to expand...
Click to collapse
Check Here for info on rooting and read my post. Don't use Rage. It also sounds like you are not connecting to your phone properly.
you can also follow http://forum.xda-developers.com/showthread.php?t=1025610 if you werent aread doing so
everything is successful after following your directions, but when it said sending 'su', or whatever to phone, the antivirus warning comes on and says "Installing package: com.noshufou.android.su is infected" . I even turned off the antivirus on the phone to see if it would work. But then i used Root Checker to see if it still worked it says Its not installed. any ideas?
EDIT: nevermind, restarted the phone and everything is working. THANKS.
phokingjuice said:
everything is successful after following your directions, but when it said sending 'su', or whatever to phone, the antivirus warning comes on and says "Installing package: com.noshufou.android.su is infected" . I even turned off the antivirus on the phone to see if it would work. But then i used Root Checker to see if it still worked it says Its not installed. any ideas?
EDIT: nevermind, restarted the phone and everything is working. THANKS.
Click to expand...
Click to collapse
Any antivirus will see SuperOneClick or any rooting software as a virus. You need to disable all antivirus software before you use it or it will stop the rooting process. It's good to see you got it to work.
phokingjuice said:
EDIT: nevermind, restarted the phone and everything is working. THANKS.
Click to expand...
Click to collapse
Congrats on successful root. Glad to hear that it worked out for you.
Sent from my SGH-T959V using XDA Premium App
Hi to all here. i just want to ask anyone what to do with my phone. well first of all, my phone is a sky pantech vega racer im-a760s, not really a match for samsungs popularity but budget wise this is the model for me. it has a dual core. now my problem starts when i started editing the build.prop in its system (tweaked for some texting problem of limited character sending). of course i know what im doing on that part, but the only thing i didn't think that would happen was, i copied it in my computer, i edited it there, then i saved it as "all" in file type so it wont become a ".txt" format. but when i placed it in my phone. the file instantly disappeared, i think it was only hidden and the phone just cant identify it nor read it like something. now i restarted the phone, it booted up to its logo then it just went blank and it just stops there. i tried pushing recovery with adb in my pc cmd. but it cannot detect my device(no problem with my adb installation to eliminate this from the question), i also tried putting an sd card with a recovery file but there was no option for sd card path. but the phone can still function well, i know because it can still be loaded under flashboot, download screen and S / W upgrade menu and it can still perform wipes for all partition and caches and can reset for factory settings etc. but whenever i will reboot, its not going to complete. anyone please help me how to make my phone be detected by my pc. The usb drivers are just fine, updated it many times, read all procedure for making the driver connect perfectly. i reformatted the sd so it wont be a problem when i put it in. but in the recovery menu i just cant see my sd card, theres just the option for "update from external storage" but it doesn't have anything inside. what a mess. i cant make my phone reflashed cause its not responding with the connection with my pc. but when i am opening an odin (just used for connection monitoring) there are two yellow boxes with com port like these: 0:[com7] and 0:[com9], so i know it is still somehow communicating with my pc. please help any advice, i dont want to resort to jtag for im not sure if it will support my phone and it's already avialable for the model but definitely not going to send my phone for repair cause it will be costly. thanks to all who will respond. Please help thank you. additionally: OS was ics version 4.0.4 and rooted. already gone through rooting several times with no problem. just the editing part.
to edit Android files on Windows use only Notepad++ anyway do not use Windows notepad this is for Windows files formatting only
well, you have to get build.prop from your phone edit on PC then copy back
so enter recovery connect phone to PC create a folder say C:\tmp
to get build.prop from phone
Code:
adb devices
adb shell
mount system
exit
that's to mount system partition then
Code:
adb pull /system/build.prop C:\tmp\build.prop
edit it and copy back to phone
Code:
adb push C:\tmp\build.prop /system/build.prop
maybe is not your case ? but I wanted to give you an idea
@ruscan.calin
Thanks, great. i will try this one once i get my phone recognized by my pc, adb seems not able to find my devcie have this message like this one:
"
c:\>adb devices
adb server is out of date. killing...
*daemon started successfully *
list of devices attached "
and that's it nothing happens.
thanks for the advice i will definitely use this once i get my phone connected with my system. thanks a lot
cruelink said:
@ruscan.calin
Thanks, great. i will try this one once i get my phone recognized by my pc, adb seems not able to find my devcie have this message like this one:
"
c:\>adb devices
adb server is out of date. killing...
*daemon started successfully *
list of devices attached "
and that's it nothing happens.
thanks for the advice i will definitely use this once i get my phone connected with my system. thanks a lot
Click to expand...
Click to collapse
start phone in recovery mode do not connect to PC at this time
open Device Manager now connect phone to PC
if you see ADB Interface connecting in Dev Manager it's ok if not you have a problem with phone drivers so install it again
ruscan.calin said:
start phone in recovery mode do not connect to PC at this time
open Device Manager now connect phone to PC
if you see ADB Interface connecting in Dev Manager it's ok if not you have a problem with phone drivers so install it again
Click to expand...
Click to collapse
Hi, cant still afford to make the adb component in my device manager to appear, but it's good to inform you that it helped me a bit because i was able to see the storage of my phone and i was also able to put some files in there without any hassle that alone was satisfying me that my phone is not really dead. sad to say i did everything i could to have my pc detect my phone via recovery menu, but still no devices found. it's really weird that some links are saying that i should make my phone's "usb debugging" enabled, wherein fact i cant even go beyond my original problem(bricked phone), i can't even see the inside of my phones directory, only the storage one that was activated just recently. i even did a reinstallation of my usb, uninstalled every other phone related usb installation to avoid conflicts reinstalled my phones proper usb installer then restart. no progress still to be called. it makes me feel that the phone was just trap in the state of booting and not knowing what to do because it cant see any command inside its system. i cant go into the systems directory as well. and that's the only way i think i could revive my phone in replacing a new build.prop, as you advised to be edited in a notepad++ which i recently acquired and installed. by the way how do i save the build.prop to its original file format, and what is the extension. thanks alot for helping out. im getting a little brighter each step of the way, im not loosing it to come to smashing my phone to pieces instead of keeping a very expensive paper weight.
usb debugging enabled is not useful in this case (you can't set it )
build.prop is a file with .prop extension save file with notepad++ name it build.prop then check location of file it should be build.prop notepad from Windows saves it as build.prop.txt that's not good also notepad adds some formatting characters inside file that's wrong so use only Notepad++ when working on Android files (or VIM for Windows editor etc anyway do not use Windows editors they are good for Windows files only)
-try these things on another computer (to install drivers etc)
-I advised somebody to send a mail to manufacturer and he got a reply with a link to stock rom... that's great !
-if you link me your build.prop file I can tell you if it's ok
-pc link - that's to be solved firstly check manufacturer site for sync software/ drivers even send mail
isa. rgiespea
ruscan.calin said:
usb debugging enabled is not useful in this case (you can't set it )
build.prop is a file with .prop extension save file with notepad++ name it build.prop then check location of file it should be build.prop notepad from Windows saves it as build.prop.txt that's not good also notepad adds some formatting characters inside file that's wrong so use only Notepad++ when working on Android files (or VIM for Windows editor etc anyway do not use Windows editors they are good for Windows files only)
-try these things on another computer (to install drivers etc)
-I advised somebody to send a mail to manufacturer and he got a reply with a link to stock rom... that's great !
-if you link me your build.prop file I can tell you if it's ok
-pc link - that's to be solved firstly check manufacturer site for sync software/ drivers even send mail
Click to expand...
Click to collapse
that's great news, you actually come to emailing the phones manufacturer? wow, im flattered. well you're a very nice guy to help me out on this. and i have good news too. i found out that i have a little conflicting usb drivers, as i have installed samsung for my previous phone(samsung galaxy 1) i had it liquidated for this new one. but a little hard on the support. you gave me a new idea about the usb. so i uninstalled all the related usb drivers and have it reinstalled. now i am able to communicate with OTA firmware server, and i got a reading that was not happening before(stucked in just detecting the phone) now i have a percentage reading of downloading or so. but i still have to wait if it will complete and have it repaired. so by now you can give me a little more help cause im still not at it in pushing through the use of adb programming. and the link you mentioned, i'll wait for the progress about it and see what really was it. and thanks a lot. really appreciate it.
fixed bricked phone via OTA by fixing link to pc.
Hi, i thank you for your help. i managed to fix the phone myself. i just missed the simple step that you advised me. fix the link first to pc. i have installed another model of the phone for the same manufacturer with different type so that was causing the mixed up for updating and recovering via the OTA site of the phone. so yey. you helped a lot. i thank you. i am now running at ics version 4.0.4 and now rooted. i will not commit the same mistake of saving the build.prop with another format. that was bad. so then i'll be very careful in editing the build.prop and first of all, i will keep a backup inside where i can access it even if it will be hard bricked. never forget that one from now on. so this is it. i thank you. of all the place ive been circling around for answer. here is where i found it. and just one person. hooray. thank you very much.
cruelink said:
Hi, i thank you for your help. i managed to fix the phone myself. i just missed the simple step that you advised me. fix the link first to pc. i have installed another model of the phone for the same manufacturer with different type so that was causing the mixed up for updating and recovering via the OTA site of the phone. so yey. you helped a lot. i thank you. i am now running at ics version 4.0.4 and now rooted. i will not commit the same mistake of saving the build.prop with another format. that was bad. so then i'll be very careful in editing the build.prop and first of all, i will keep a backup inside where i can access it even if it will be hard bricked. never forget that one from now on. so this is it. i thank you. of all the place ive been circling around for answer. here is where i found it. and just one person. hooray. thank you very much.
Click to expand...
Click to collapse
that's good news ! and thanks for feedback
feedback is an invaluable resource ! (some just forget about that from my experience :laugh: NOT your case ! )
Its been continuous 10 hours I have been googling and searching here but I am not able to find a single goddamn solution for this stupid ADB or fast boot **** in order to root my Desire S, I want to downgrade my HBoot in order to root I am using this guide:
http://forum.xda-developers.com/showthread.php?t=1399331
but all I am getting is this stupid error that's making me cry like hell:
adb server is out of date, killing...
ADB server didn't ACK
* failed to start daemon * (I dont even know what the hell this daemon is for me its DEMON)
error: unknown host service
Please someone help me out all I know its very very difficult to find adb drivers for HTC Desire S may be I am wrong but I have installed and uninstalled the drivers like thousand times from different sources nothing worked yet all ended on that stupid error!!!
uninstall whatever drivers you have currently on you PC.....I'd then suggest rebooting your PC to start clean.
then I'd suggest you download and install http://www.htc.com/uk/software/htc-sync-manager/download/ you may have to drop down and select the correct device type. you can then uninstall HTC Sync after wards as I believe it leaves the necessary drivers in place.
You may find that you have HTC_SYNC.EXE on your SD that came with your device, I know that mine did.
I'd also
the main issue was Desire S adb drivers I downloaded them so many times but no luck but at last from one forum dunno which I downloaded that .inf file and it worked like a charm but no use as I tried zergRush and Tacoroot but they both are not working giving errors!!
Sent from my HTC Desire S using Tapatalk 2
Some other programm is using port you need for adb
http://www.youtube.com/watch?v=JmvCpR45LKA
I have seriously searched EVERY DAMN INCH of the Internet for this. Okay, obviously, I've seen all the posts like this one:
http://forum.xda-developers.com/showthread.php?t=2351390 (I actually wanted to reply there but can't, sad)
And I've done all those steps, I've uninstalled everything, I've reinstalled everything, I've called my mom to tell her she wasn't lying to me about me being special, I've done it all ten times. This is what happens:
System stuff: Windows XP, cyanogenmod 10, ADB and Apps set to root, USB debugging on, Android 4.2.2, latest Android Commander, Galaxy S3 Sprint, Android Debug Bridge version 1.0.31
I open cmd and type adb devices, it shows me a device is available:
adb server is out of date. killing...
* daemon started successfully *
List of devices attached
ba0a8be4 device
I open Android Commander, it has a blank line that's highlighted blue, I click "OK", it says:
Connected device has status offline and cannot be used. Please reboot your device.
I reboot my device, same thing happens.
Does anyone have any ideas? I'm seriously about to just flash it to 421 but I hate just giving up. I hate it almost as much as I hate asking for help. I spent 7 hours last night (I was up until 2am!!) and then another 4 or 5 today just trying to figure this out. I'm completely lost here. Oh, another thing, since I'm at it, does anyone know how to delete the saved RSA key from my phone? I looked in that data/adb place that link said and renamed it but it didn't seem to reset the key... maybe I need to restart, I'll try restarting after I rename it. Yep, I bet that'll work. It probably had it in memory. Anyway, pointless rant about RSA done. I hope someone has some ideas before I resort to just sitting in the corner, cuddling up with my phone, and crying until my mommy tells me I'm special.
Another possibly important thing is that Droid Explorer works briefly (I can see phone's files come up) but then crashes when I try opening anything.
It also, as I was just playing with it, seems like Android Commander causes the adb server to become outdated. Does that mean anything? I just ran adb devices, then tried AC, then did adb dev again and it needed to restart the service. I don't know if that means anything. Just something I noticed.
Oops I had to update the link, I just realized I copied the wrong one from the page suggestions it does. This now has the one I meant.
Did you find a solution? I am having the same problem.
I gave up. Flashed stock, then cm 10 with system and cache wipes then cm 10.1 without wiping system. Haven't tried with my computer since I mostly use my phone. I'll check later and update this and let you know. I would have just kept stock but my god that stuff sprint puts on sickens me......
I found a solution and it works.
http://forum.xda-developers.com/showpost.php?p=40276190&postcount=1488
Yeah, I even said in my message that I made sure that was up to date. I was able to connect to adb and see it show up as a device now but Android Commander doesn't work. I did find out that adb push (and I assume pull) works but that probably worked before and I just didn't try. Anyway, I'm not too concerned. Glad you got yours figured out.
Hope this helps!
I managed to get android commander to work by installing the latest adb with the sdk manager and then I copied adb.exe, AdbWinApi.dll and AdbWinUsbApi.dll to the bin folder located where ever you install android commander!
lukesheardown said:
I managed to get android commander to work by installing the latest adb with the sdk manager and then I copied adb.exe, AdbWinApi.dll and AdbWinUsbApi.dll to the bin folder located where ever you install android commander!
Click to expand...
Click to collapse
Copying the adb files to the bin directory worked for me, thanks!