Hi guys,
I'm no stranger to rooting and installing ROMs, but doing so with ADB is completely new to me. I just got a G2 at the beginning of January, upgrading from a G1.
I spent about two hours trying to get the Android SDK and ADB working properly on my computer. Now ADB can see my phone, but when I try to do the first part of the temp root process from the wiki:
$ adb push su /sdcard/su
I get a permission denied error. I'm not supposed to be getting this, right? The gfree_temp-root.zip files are extracted to the folder where ADB is, and I can see in the prompt that ADB is trying to work, but I always get this error, and I don't want to continue until I know what's supposed to be happening. USB debugging is enabled and the terminal emulator app is installed. The sd card is mounted by the phone, not the computer. I still have 7+ GB left on the sd card.
$ adb push Superuser.apk /sdcard/Superuser.apk
gives me permission denied, too.
I've never installed Visionary or any other temp root app. The closest solution to this problem I saw was in response to a guy who had installed Visionary before, and so didn't need to worry about having superuser permissions. The only reason I could find that this might not work is because of stuff about rolling back OTA updates.
Thanks for any responses. Let me know if you need any more info.
I just used this method last night. Make sure you have USB debugging on first of all and make sure you don't have the "USB connected" option ticked when it prompts you. You want that off.
I had the permission denied too but when I turned off the USB Connection that mounts my sd card, I got it to work. Good luck!
The weird part is he specifically says he checked those things (USB debugging enabled and the SD card not mounted to the computer). Not sure why he'd be getting a permission denied (reading/writing from the SD card should not have any problems).
What OS are you running ADB on? And maybe this is a silly question but you are running the commands from your computer and not the terminal on your phone, right?
LGS1231 said:
I just used this method last night. Make sure you have USB debugging on first of all and make sure you don't have the "USB connected" option ticked when it prompts you. You want that off.
I had the permission denied too but when I turned off the USB Connection that mounts my sd card, I got it to work. Good luck!
Click to expand...
Click to collapse
That did it! Thanks, I am now perm-rooted and ready to overclock.
ianmcquinn said:
The weird part is he specifically says he checked those things (USB debugging enabled and the SD card not mounted to the computer). Not sure why he'd be getting a permission denied (reading/writing from the SD card should not have any problems).
What OS are you running ADB on? And maybe this is a silly question but you are running the commands from your computer and not the terminal on your phone, right?
Click to expand...
Click to collapse
I think I misspoke (typed?); when I said it was mounted by the phone, I meant I had selected to turn USB storage on with the phone. I thought I remembered seeing a way to do it through the computer, but I'm probably wrong. Either way, turning USB storage off fixed it, and now that I think about it, I understand why I would be getting permission denied. I guess I didn't fully understand what the wiki meant by "Make sure your phone's sdcard is mounted by your phone and not your computer when following these instructions."
For the record I'm using Windows 7 Professional, and installing ADB was a project in and of itself. Don't know if anyone else had problems with it.
Thanks for your help everyone. This is a great forum.
Great! Glad to be joined by another newly rooted user! CM7 Gingervillain is a great ROM, and I recommend you flash that. It already has an OC kernal built in so it's less work. All you would have to do is flash CM7 and then get SetCPU.
I love being rooted!
Edit: nevermind, I saw there was a superuser permission pop-up on my phone that I wasn't seeing before.
LGS1231 said:
Great! Glad to be joined by another newly rooted user! CM7 Gingervillain is a great ROM, and I recommend you flash that. It already has an OC kernal built in so it's less work. All you would have to do is flash CM7 and then get SetCPU.
I love being rooted!
Click to expand...
Click to collapse
Do the nightly builds have 4G working yet? It's not a huge deal because I use wifi at home, but it would be nice to keep 4G on there.
Related
On Thursday the 29th my phone decided to take a dump on itself. Since then it has not been able to:
-Read any micro SD cards
-Connecting to computer doesn't fully allow USB connections, it detects something plugged in, but nothing else. No ADB, no RUU update, no Sync, etc.
-Cannot charge unless off
All of the above happened while trying to get onto the leaked Froyo. I cleared the cache and wiped the data then this happened.
I already ordered a replacement from Sprint (which I have yet to hear about), but I think I can fix this one by updating the OS.
Problem is that it downgraded me to a version earlier than the one that was on the phone when I first got it. Being on this version is causing a problem by not allowing HTC Update to even see any updates.
So basically I need to update without the use of USB or SD card.
Any help?
Have you tried this http://forum.xda-developers.com/showthread.php?t=695243
063_XOBX said:
Have you tried this http://forum.xda-developers.com/showthread.php?t=695243
Click to expand...
Click to collapse
Thanks for the quick response.
That seems like it will be of a lot of help, but unfortunately adb cannot detect the phone.
EDIT:
It's also mildly amusing the way anytime someone also had this problem in that thread (the < waiting for device > in adb due to it not detecting the phone) people would just ignore it and continue on.
I have noticed that the computer can somewhat recognize the phone if it is in HBOOT USB mode. It is enough for the fastboot command to go through but return with a failed.
kbone213 said:
I have noticed that the computer can somewhat recognize the phone if it is in HBOOT USB mode. It is enough for the fastboot command to go through but return with a failed.
Click to expand...
Click to collapse
does adb work while it is in hboot? if so you should be able to push a pc36img.zip to it and fix it that way.
t3project said:
does adb work while it is in hboot? if so you should be able to push a pc36img.zip to it and fix it that way.
Click to expand...
Click to collapse
No, it only is able to recognize some things while in HBOOT. Example would be PDANet, which I used to be able to read the phone in the first place on Windows 7 x64, can see that the phone is connected. Adb still reads no devices though.
I'm pretty sure this happened when trying to wipe the phone to do a clean install. My assumption is that it wiped a file that was otherwise necessary to keep the SD card reader and USB port operational.
Is there any way that I can execute the "fastboot oem enableqxdm 0" somewhere on the phone without using adb?
Did another reset on it. Battery was low and turned the phone off without my knowledge. I turned it on to check if I had any messages or whatnot and got a message saying that the battery is low and that the current being given from the USB is not strong enough to charge it and to switch the cable.
What in the software would cause the current to be low?
HELP! I am VERY new to linux. I have the unrevoked file extracted and when i open it up it does not find my phone. any ideas? it says, even after i hook up my phone, "Waiting for device. Plug phone in now and enable USB debugging. You may require Linux root access." I have my phone plugged in and have USB debugging enabled, but how do i get root access? Do i simply open a terminal, type in sudo su and my password, then go back to the desktop, double click on the file, then plug my phone in again? Cuz so far thats not working. Im so confused! I dont know ANY commands for terminal either which im sure isn't helping me any. Thanks in advance!
dehahn1984 said:
I dont know ANY commands for terminal either which im sure isn't helping me any. Thanks in advance!
Click to expand...
Click to collapse
As far as I'm aware, you don't need to know any other than cd (change directory)
cd /placewherereflashis
sudo ./reflash
That's the way I understand it, but...
not working for me either. Hangs on the screen saying waiting for device.
I've got a fair amount of Linux experience (I'm president of a LUG, though I'm a desktop guy, not a server guy) and I installed ROMs on G1 with ease. This is proving a much more difficult process though.
I should note that I'm using a Nexus One, not an EVO, but I've heard conflicting reports as to if this will work with stock Froyo, so perhaps someone can clarify.
Hey, just got my desire HD and I thought that I'd try to unlock it's power by installing a custom ROM. I was following http://forum.xda-developers.com/showthread.php?t=954997 cause I have a Telus Desire HD. However, when I entered /data/local/tmp/misc_version -s 1.31.405.3 I got "backup failed" or something.
I decided to continue, anyways, with flashing the PD98IMG. But, at the end of the flashing it says "Main version is older, update failed!" Any ideas what I've been doing wrong?
Thanks!
You have to start the process again, and this time use "charge only" connection mode. The problem might also be some app that mounts your SD card when you connect your phone to a PC (for example winamp does this).
Wait, nevermind. I think I failed in making the goldcard because I restarted from scratch and so far it's working properly =D
Sorry for already spamming the forums with my first post xD
Yeah, I converted it to Charge Only too this time. Maybe it was a combination of both things that fixed it! Thanks! =]
When should I have charge only and when should I mount the SD card? Right now I'm pushing su (I'm guessing super user). Does that mean I should have the SD card mounted? It's saying device is not found so I'm a little confused by that
Anyone have any advice? =D
I enter: push su /sdcard/su
And it says: error: device not found
ADB drivers installed correctly? Charge only mode? USB debugging on?
Sent from my Desire HD using Tapatalk
Hi everyone,
Pretty much ready to cry here.
Here's my story:
I have unlocked and rooted my phone, and it was working fine since March. I decided to try a new ROM (AOPK instead of APEX) today , and put it onto my SD card. In Clockwork recovery mode, I wiped my "data factory reset", as well as "wipe cache and partition". After that I installed AOPK. It was very buggy (crashing all the time), so I decided to get rid of it and go back to APEX.
I then found that there's a newer version of APEX than the one I had, so I decided I'd copy that from my computer and give it a shot.
HOWEVER, now when I plug my phone into the computer, the USB device is not recognized by windows!!!
I've tried everything to get the drivers installed properly. I've read every thread I can find on the internet. I've tried to use the WugFresh GalaxyNexusToolKit to install the drivers like I did when I first unlocked and rooted the phone. I've tried installing drivers from all sorts of sites and forums.
Nothing is working. I can't access the phone through USB at all. It won't show up in My Computer.
I'd really appreciate if someone can help walk me through this.
Thanks so much for your help.
Turn off "fast charge".
X2. If you have the FrancoKernel app, disable it there.
In windows 7 go to to power option and change your power option to always on for USB or something along those lines .... fixed my issue up
Sent from a paranoid rom!
WiredPirate said:
Turn off "fast charge".
Click to expand...
Click to collapse
+1
It took me the longest time to finally realize that a month or so ago. Gave me the biggest headache because I thought it was on my computer's end, trying to reinstall the USB drivers.
Thanks for the responses guys.
However, I'm back to using APEX rom, and there is no fast charge option that I can see.
Also, I went back to AOKP rom to make sure that it was deselcted, and it is. After that, I reinstalled the APEX rom.
thanks guys, any other suggestions?
Also check the storage option in the settings and make sure that MTP connection is selected (click on the three dots in the top right or bottom right I dont remember). I was worried once that my device wasnt syncing either and found out that it was because of that.
What kernel are you running?
jonnyg1097 said:
Also check the storage option in the settings and make sure that MTP connection is selected (click on the three dots in the top right or bottom right I dont remember). I was worried once that my device wasnt syncing either and found out that it was because of that.
Click to expand...
Click to collapse
^ This
i also wasted a couple of hours trying to fix up my pc
MTP was always selected.
Kernel version "3.0.18-imoseyon-1.8.0-04373-gc91166d [email protected] #361"
Thanks for the suggestions
When you plug it in does it make the noise? Can you see it under device manager with a yellow exclamation point?
imoseyon also has a "fast charge" option, maybe someone else more knowledgeable than myself can explain how (if any) it differs then the version baked in ROMs. I just know that the franco/imoseyon control app has the option and so does certain ROMs, I dont know if they are independent of each other.
To turn off fast charge, open a terminal and type:
su
echo 0 > /sys/kernel/fast_charge/force_fast_charge
z06mike said:
When you plug it in does it make the noise? Can you see it under device manager with a yellow exclamation point?
Click to expand...
Click to collapse
Once plugged in, I do here a typical windows "dun-dun" sound. It is listed in device manager as "Unknown Device" with a yellow exclamation mark.
efrant said:
To turn off fast charge, open a terminal and type:
su
echo 0 > /sys/kernel/fast_charge/force_fast_charge
Click to expand...
Click to collapse
Silly question: How exactly do I open up a terminal. I googled it, but I'm getting a lot of complicated instructions that have to do with the Android SDK. Is this what I should be doing?
Thanks guys.
Download terminal emulator from play store. This will do the job nicely
*other similar apps are available*
Sent from my Galaxy Nexus using XDA
At this point, I'd be happy to even format my computer and completely wipe my phone so that's the SD card is clear and its back to the day I bought it.
WabbaJ said:
At this point, I'd be happy to even format my computer and completely wipe my phone so that's the SD card is clear and its back to the day I bought it.
Click to expand...
Click to collapse
As killyouridols said, Terminal Emulator works just fine.
1) Download, install and open the app.
2) Type in the following commands once the app is open:
su
echo 0 > /sys/kernel/fast_charge/force_fast_charge
3) Now trying plugging your device into your computer.
Also be sure you are trying to use a usb data cable. I know I have a few "power only" cables laying around that sometimes find their way into my backpack.
Thanks for the suggestions again.
I tried the Terminal Emulator, typing in:
su [ENTER]
echo 0 > /sys/kernel/fast_charge/force_fast_charge [ENTER]
Then I get a message: "No such file or directory".
Here's the exact text of everything I tried....
[email protected]:/ $ export PATH=/data/local/bin:$PATH
[email protected]:/ $ su
nel/fast_charge/force_fast_charge <
sh: cannot create /sys/kernel/fast_charge/force_fast_charge: No such file or directory
1|[email protected]:/ # su
nel/fast_charge/force_fast_charge <
sh: cannot create /sys/kernel/fast_charge/force_fast_charge: No such file or directory
1|[email protected]:/ #
Also, I've been using the original cable that came with the phone.
Anything else guys?
PS: on a related note, I also have a Motorolla car charger. It now only charges randomly, whereas it would charge every single time previously, and worked fine. I don't know how, but it seems things really got shook up by installing the AOPK rom.
WabbaJ said:
Once plugged in, I do here a typical windows "dun-dun" sound. It is listed in device manager as "Unknown Device" with a yellow exclamation mark.
Click to expand...
Click to collapse
Sorry, I didn't see this comment before.
If it shows up in device manager, then just update the driver: right-click on the yellow exclamation and select update driver, then search for the driver, by navigating to the directory you have it downloaded.
P.S., you do have USB Debugging enabled, right?
I did a "factory reset", this seems to have been a poor choice.
After the reset, I could still get onto the device via wireless adb, but su would return "permission denied". Today there was an automatic system upgrade, now I've lost the ability to connect to it via wireless adb or adb over USB.
Any hints would be wonderful.
vbrtrmn said:
I did a "factory reset", this seems to have been a poor choice.
After the reset, I could still get onto the device via wireless adb, but su would return "permission denied". Today there was an automatic system upgrade, now I've lost the ability to connect to it via wireless adb or adb over USB.
Any hints would be wonderful.
Click to expand...
Click to collapse
I don't know too much about adb, but I'll try to help
does your ADB detect the OUYA when you do "adb devices" when plugged in?
Either way, my advice would be to delete the OUYA drivers from your computer and reinstall them from scratch and then follow the steps to get adb working as if it never was. I haven't tried my adb since todays update, but I also don't use it for any reason.
I just turned on my console and have come to the conclusion that the automatic update broke su. How, i'm not sure, but it would seem that possibly you'll have to restart the process from scratch, redo adb and reload su.
lets just hope this isn't a sign that all future automatic updates will break su.
*EDIT* So it would seem that there is problems with the drivers. I have gotten ADB to work once again by deleting all the OUYA drivers from my computer and following the steps found at https://devs.ouya.tv/developers/docs/setup HOWEVER this presents a problem in that the system is only recognized as a adb device and has a broken MTP driver (whatever that is, maybe someone else will know). Maybe this is how it's supposed to be, I don't know, I don't remember seeing anything like that the first time.
After getting ADB back, I got SU back by running through the steps found here: http://forum.xda-developers.com/showthread.php?t=2272266 under how to install busybox, superuser, and su binaries. You should only have to go from step 1 to 4 on that one (only 4 if you still have the files on your computer).
I will note that the steps to get ADB on that second link did NOT work this second time. I'm not sure what this is due to. I'll be starting a new thread with this info, too.
JLCollier2005 said:
does your ADB detect the OUYA when you do "adb devices" when plugged in?
Click to expand...
Click to collapse
Nope.
JLCollier2005 said:
Either way, my advice would be to delete the OUYA drivers from your computer and reinstall them from scratch and then follow the steps to get adb working as if it never was. I haven't tried my adb since todays update, but I also don't use it for any reason.
[/QUOTE[
No drivers, running OSX & Linux.
Click to expand...
Click to collapse
Hard boot the OUYA and laptop, adb via USB seems to work again.
So far every OTA has removed su.
Sent from my GT-P3113 using Tapatalk 4 Beta