Related
im having some serious issues with my SU.
i tried temporizer's fix with no help.
it started a while ago when i flashed a theme and i could never get it back.
Ive tried EVERYTHING (to my knowledge which is definitely not vast lol) to no avail. and from what temp and a couple others have told me its a problem with cyan recovery 1.3, but now i cant flash to 1.4. im stuck with no SU, no way to flash a new recovery and pretty much half ass phone. ive never had this type of problem since i rooted back in januaryish. any help would be much appreciated.
anon1ski said:
im having some serious issues with my SU.
i tried temporizer's fix with no help.
it started a while ago when i flashed a theme and i could never get it back.
Ive tried EVERYTHING (to my knowledge which is definitely not vast lol) to no avail. and from what temp and a couple others have told me its a problem with cyan recovery 1.3, but now i cant flash to 1.4. im stuck with no SU, no way to flash a new recovery and pretty much half ass phone. ive never had this type of problem since i rooted back in januaryish. any help would be much appreciated.
Click to expand...
Click to collapse
Download cyan's recovery 1.4 to your sdk tools folder, start the phone in fastboot mode [back+power] folder and run:
Code:
fastboot boot cm-recovery-1.4.img
That should boot the recovery image and you can work from there to reflash whatever you want.
sdk tools folder? and that would beeeeeeee?
apparently im not as savvy as i once thought..... lol
anon1ski said:
sdk tools folder? and that would beeeeeeee?
apparently im not as savvy as i once thought..... lol
Click to expand...
Click to collapse
Errr... you don't have the sdk?
You don't use adb...?!
That's like trying to play football with no limbs..
Get yourself rigged up with this:
http://developer.android.com/sdk/1.5_r3/installing.html
btw.. you won't need to set up eclipse or the adt plugin for this, just make sure your environment variables and java paths are set up as per the guide.
well while football WITH limbs does sound much less entertaining, i am normally no where near a computer, and do almost everything right from my phone.... and i mean everything..... i download all my roms, themes, etc. right to my download folder, find em', rename em' flash em' and im good to go. i went on a computer to get the recovery simply because it downloads wrong on my phone and saves as a text file, seems like it does the same on mozilla for some people but i got it in .img form and its on the root of my card, and nothing.
anon1ski said:
well while football WITH limbs does sound much less entertaining, i am normally no where near a computer, and do almost everything right from my phone.... and i mean everything..... i download all my roms, themes, etc. right to my download folder, find em', rename em' flash em' and im good to go. i went on a computer to get the recovery simply because it downloads wrong on my phone and saves as a text file, seems like it does the same on mozilla for some people but i got it in .img form and its on the root of my card, and nothing.
Click to expand...
Click to collapse
I do a lot of stuff from my phone too tbh, Somehow it satisfies my geek cravings more fully.. But adb is massively useful when you're on the pc.. saves a lot of cramped typing on the device keyboard.
Fastboot will be your saviour in this case though, and you're gonna need a proper box to run that on.
i have NO idea what im doing with adb, i just downloaded it and im just starign at my screen like it tried to feed me a cheeseburger.....
anon1ski said:
i have NO idea what im doing with adb, i just downloaded it and im just starign at my screen like it tried to feed me a cheeseburger.....
Click to expand...
Click to collapse
lol.. adb is pretty simple.. a few examples:
Code:
adb push localpath devicepath # push files to your phone eg: adb push c:\update.zip /sdcard
adb pull devicepath localpath # pull files from device
adb shell # basically a terminal running on your device that you control from your pc.. im sure you can figure this out if you do everything from your phone.
adb shell reboot # guess?
adb shell reboot recovery # go straight to recovery without holding any buttons
fastboot should be in the same folder as adb.. you can use it to flash .img files from the pc or just boot the images without flashing them.
how do i run fastboot, adb, etc. in relation to them running processes on my phone.
i downloaded everything. i just dont know how to run it or if i have to run a couple things, have my phone in recovery or fastboot(im guessing).
god. i feel like a moron.
anon1ski said:
how do i run fastboot, adb, etc. in relation to them running processes on my phone.
i downloaded everything. i just dont know how to run it or if i have to run a couple things, have my phone in recovery or fastboot(im guessing).
god. i feel like a moron.
Click to expand...
Click to collapse
Assuming you're on windows, you'll have to install the adb driver first (not the standard android that windows installs automatically, theres a seperate driver in the usb_driver folder of the sdk). You also need to enable usb debugging on your phone.
Follow this guide if you need to:
http://forum.xda-developers.com/showthread.php?t=532719
You can use adb whatever mode your phone is in.. even when its stuck in a bootloop usually. You don't need to be running anything on the phone, the drivers are switched on by init.rc.
Fastboot can only be run with the phone in fastboot mode (surpisingly).
thanka alot man. im gonna give this all a try.
Good luck
ok. got adb running. ran the command you gave me. it brings up 1.4 but doesnt push it to my phone...... can i actually INSTALL 1.4 from fastboot/adb?
nevermind. figured it out. used common sense and just ran fastboot flash recovery recovery.img and it worked. thanks for everything
my super user still wont work.; so apparently it had nothing to do with the recovery..... im going to wipe, reflash cyan 3.9.1. and see if that works.
Hello everyone, I apologize in advance if I've posted this in the wrong section. Ok so here is my problem, I recently got Cyanogen 4.04 (Latest stable release) on my phone. I was gonna try out the overclock app from the App market but it doesn't let me open it because i'm not ROOT. I thought users are always ROOT in modded ROM, are they not? If not then what should I do to ROOT? I used the one click method for root at the begining (to install cyanogen) and Haykuro SPL Update. Thanks.
p.s I am a complete noob so please go slow.
If you have used the 1-Click-Root method, did you follow the steps to type in telnetd using a terminal app? If not then I would go back and re-trace your steps.
NeoBlade said:
If you have used the 1-Click-Root method, did you follow the steps to type in telnetd using a terminal app? If not then I would go back and re-trace your steps.
Click to expand...
Click to collapse
Yes I did the telnetd thing. After rebooting clicking on an emptyspace then RETURN, wait, RETURN then telnetd which took me to the contact list. Then Home. Then I went to the terminal app and did the 4 step thing. But I did all that before flashing the Cyanogen for the first time. Now that I have Cynogen installed, if I try to Connect in telnet it gives me an error and if I try to do the 4 step thing in Terminal emulator it says "permission denied. (are you root?)". Please tell me what should I do?
pooranimator said:
Yes I did the telnetd thing. After rebooting clicking on an emptyspace then RETURN, wait, RETURN then telnetd which took me to the contact list. Then Home. Then I went to the terminal app and did the 4 step thing. But I did all that before flashing the Cyanogen for the first time. Now that I have Cynogen installed, if I try to Connect in telnet it gives me an error and if I try to do the 4 step thing in Terminal emulator it says "permission denied. (are you root?)". Please tell me what should I do?
Click to expand...
Click to collapse
type su into the terminal emulator and see what is says. if you were able to flash a custom rom then your phone is rooted, you could've gotten a bad download.
Download Better Terminal from the Maket and as david mentioned, type in "su" then press enter to see if you have root access.
if nothing pops up upon entering su does that mean a new wipe and install is nessecary??
Reason i ask is i can't get the terminal emulator to work either that came with the build....is it the same thing as better terminal????. I used a one click install and everything is running fine on my 4.0.4 build but i tried earlier as well to install the "overclock" app from market and it wouldn't work. I decided to purchase SetCPU instead for a buck and it works no problem. By the way i have a my touch 3g..
mikespy said:
if nothing pops up upon entering su does that mean a new wipe and install is nessecary??
Reason i ask is i can't get the terminal emulator to work either that came with the build....is it the same thing as better terminal????. I used a one click install and everything is running fine on my 4.0.4 build but i tried earlier as well to install the "overclock" app from market and it wouldn't work. I decided to purchase SetCPU instead for a buck and it works no problem. By the way i have a my touch 3g..
Click to expand...
Click to collapse
dont think the terminal emulator works w/o a physical keyboard
better terminal will get the job done, but not the same app. You can just use that instead of terminal
but if terminal does work w/o a physical keyboard, when you type su, what does it do?
if it asks to allow or deny, click allow. if you hit always deny, go to the superuser app and erase all settings.
if it doesnt ask anything, when you type su, it should drop one line and have this symbol #
B-man007 said:
dont think the terminal emulator works w/o a physical keyboard
better terminal will get the job done, but not the same app. You can just use that instead of terminal
but if terminal does work w/o a physical keyboard, when you type su, what does it do?
if it asks to allow or deny, click allow. if you hit always deny, go to the superuser app and erase all settings.
if it doesnt ask anything, when you type su, it should drop one line and have this symbol #
Click to expand...
Click to collapse
Thanks for the help....
I actually did download better terminal and when i typed in su and hit enter. It went to the screen your talking about and since i had just installed SetCPU it asked if i wished to allow i clicked yes. So i asume i have rooted correctly and guess the "overclocking" program on the market might just not download on my phone correctly with the cyan 4.0.4.
Thanks
Thanks to all of you for your replies. I think I know what the problem was. The OverclockWidget is a Widget...duh silly me. I was trying to open it as a regular app and was failing. Added it as a widget on the first screen and now everything works. I have one quick unrelated question, while downloading the latest experimental release of Cyanogen I read at the bottom of the post in read that the users should not use any Apps2SD while using Cyaogen's latest release because the ROM does it by itself or something like that. What does that mean?
@mikespy- tap and hold for a sec on your screen and add the OverclockWidget widget on your screen then tap to open. That's how you open the OC util.
So I flashed SuperD yesterday, and all is cool. Its not my first time using roms, and everything went smooth.
But then today I wanted to change the keyboard layout back to the German layout. So I went to Terminal Emulator and began to edit the layout using this method (tested, working from these forums)
su
mount -o rw,remount /system
cp /sdcard/trout-keypad-v3.kcm.bin /system/usr/keychars
Anyway, once I finished, it said that this operation isnt possible. Then I realized that I forgot to put the file on sd card. So I added the file, but then the strange part came....
I then again went into terminal emulator and typed "su" to start the process again but now im getting the "permission denied error! 5 min ago I didnt have this error and could mount just fine! The phone is running fine, but it seems like I ve lost root.
Do I need to reflash the rom or the spl to reverse this? I really just need access to Terminal again. Anyone know how to fix this? I tried rebooting just to see if it was some type of bug, but even after reboot Im still getting permission denied.
Could really use some help on this!
Use adb shell. Try clearing the saved options in the SU application. Try a different terminal program. Lastly, try to just reflash the rom.
evilkorn said:
Use adb shell. Try clearing the saved options in the SU application. Try a different terminal program. Lastly, try to just reflash the rom.
Click to expand...
Click to collapse
I installed a new Terminal, and it seems to work fine. Might seem like a dumb question, but Im really not sure if I have root or not?!
If it worked what's the question?
evilkorn said:
If it worked what's the question?
Click to expand...
Click to collapse
Your right. Was a dumb question. It just confused me, as one terminal is giving me access, and another wont. Guess its just a bug.
Anyway, I reflashed the rom, and all is perfect. Thanks for the help though guys.
Just like the title suggests, I need help. I have been working on this for three days and have not accomplished anything.
I have been rooted for six months, flashed many roms, kernels, enabled apps2sd, etc.., etc.., but I do not know how it all works(just to give you a little FYI).
"I do not have a recovery screen anymore." At first I just wasn't able to push a new one, it would tell me "usage flash_image partition.img" or something very similar. I searched for that phrase and found something with it in the G1 forums, tried it(probably should have asked first), and now I don't even have a recovery image. Like I said I've tried almost everything and it may be simple but this is beyond me, someone please help.
Sent from my HERO200 using XDA App
secbrad said:
Just like the title suggests, I need help. I have been working on this for three days and have not accomplished anything.
I have been rooted for six months, flashed many roms, kernels, enabled apps2sd, etc.., etc.., but I do not know how it all works(just to give you a little FYI).
"I do not have a recovery screen anymore." At first I just wasn't able to push a new one, it would tell me "usage flash_image partition.img" or something very similar. I searched for that phrase and found something with it in the G1 forums, tried it(probably should have asked first), and now I don't even have a recovery image. Like I said I've tried almost everything and it may be simple but this is beyond me, someone please help.
Sent from my HERO200 using XDA App
Click to expand...
Click to collapse
what happens when you hold home then press the power button? Is there any sort of screen if you get a screen you need to install android sdk and flash a new recovery image using adb
bycoo222 said:
what happens when you hold home then press the power button? Is there any sort of screen if you get a screen you need to install android sdk and flash a new recovery image using adb
Click to expand...
Click to collapse
Yes there is a screen, it's the green HTC w/ white background. It will just sit there forever. I am at work right now so I can't do it yet but when I get home I'll try it, hopefully that works.
BTW, from my phone I can't tell if you have a donate button. I was serious about that.
Sent from my HERO200 using XDA App
Try downloading the RUU and then re-rooting your phone. It will be wiped clean from the RUU install then you'll be able to push a new recovery img over. If you don't want to do that my other suggestion is if you can't manually flash the recovery try downloading RomManager from the market and using that to flash a recovery.
As far as why you can't flash a recovery where are you placing the recovery.img when you try? are you doing it from your computer or from your sdcard using a terminal emulator? If its from your computer make sure that the recovery.img is in the tools folder and make sure you type it word for word (caps included) if your trying to do it from the terminal emulator and its on your sdcard the same applies as it must be letter for letter and word for word, but before you can type anything you have to gain root access in the terminal you do this by simply typing su and then enter. SuperUser Permissions will ask you if its ok to use root click ok then type in what you need to.
Since you said you've been trying to flash it I assume you know what to type but if you need it again just ask I'll post it up for you. Hope this helps.
Here's something I wrote a few days ago to help someone who was trying to flash a custom recovery might be helpful.
Flashing a custom recovery is pretty easy there is a couple of ways to do it some find it easier to do by putting it on the sd card and flashing it through a terminal emulator or if you have your htc sync and adb set up already you can throw it on your sd card and type this
Code:
adb remount
Code:
adb shell
Code:
flash_image recovery /sdcard/RA-darchstar.img
You should see this below
Code:
# flash_image recovery /sdcard/RA-darchstar.img
flash_image recovery /sdcard/RA-darchstar.img
#
Reboot into recovery and you should be all set to go. The other way by using the terminal emulator you'll just type in this in:
Code:
su
Accept Root access request from SuperUser Permissions then type:
Code:
flash_image recovery /sdcard/RA-darchstar.img
You should see the same output to know you did it correctly. Hope this helps.
secbrad said:
Yes there is a screen, it's the green HTC w/ white background. It will just sit there forever. I am at work right now so I can't do it yet but when I get home I'll try it, hopefully that works.
BTW, from my phone I can't tell if you have a donate button. I was serious about that.
Sent from my HERO200 using XDA App
Click to expand...
Click to collapse
No donate needed
Sent from my HERO200 using XDA App
Also try quick boot to get in to recovery
Sent from my HERO200 using XDA App
Thanks
Thanks everyone for all you help. I ended up being able to do it through terminal. I guess next time I won't wait three days to ask for a thirty second fix.
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