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.
Okay I got another phone from Sprint today and it has 1.5 on it. I have been trying to root this damn thing for hours but it does not seem to work. I have tried using the ADB program but when I type in that mount -o rw, long ass command way of rooting it, this does not work. I have also tried installing the flash recovery thing with that other image to recover and that crap dont work either. Any ideas? Am I being retarded and doing something wrong
If you have Windows
http://geekfor.me/new-release/fresh-kitchen-105
Would really appreciate some help here guys...
basically i have a new SLCD nexus one with Ramons 1.8.01 recover image.
I tried uploading a few roms but none of them worked..
so I'm trying to restore one of two nandroid backups i made before i started messing..
on the phone if i go into recovery and select nandroid restore then i get an error telling me to run nandroid-mobile.sh via ADB.
So, i set up adb, follow a guide (here) and end up with an error saying
error: unyaffs not found in path
does anyone know how i can get that backup working???
I've attached a copy of my cmd window..
Any help would be gratefully appreciated
Quick update, I have Cyanogen 6.0.0 working on the phone now..
But i'd still like to be able to restore!
jamin100 said:
Would really appreciate some help here guys...
basically i have a new SLCD nexus one with Ramons 1.8.01 recover image.
I tried uploading a few roms but none of them worked..
so I'm trying to restore one of two nandroid backups i made before i started messing..
on the phone if i go into recovery and select nandroid restore then i get an error telling me to run nandroid-mobile.sh via ADB.
So, i set up adb, follow a guide (here) and end up with an error saying
error: unyaffs not found in path
does anyone know how i can get that backup working???
I've attached a copy of my cmd window..
Any help would be gratefully appreciated
Click to expand...
Click to collapse
I would suggest trying to type the directory instead of using default. When the restore prompts you to either type the directory or hit enter... instead of hitting enter type:
/sdcard/nandroid/HT08BP800418/BCDS-20100911-2252
See if it gives you the same error.
NOTE: That IS case sensitive.
Thanks for your reply, unfortunately it does give the same error, I have 3 nandroid backups but cant restore any of them which is worrying incase anything happens to the phone!
Please help
Try this... while in the shell... type the following:
Code:
ls -l /sdcard/nandroid/HT08BP800418/BCDS-20100911-2252
It should bring up a list of 5 files. Go ahead and attach a screen if you can if you are getting a list of files. If not let me know what error you get.
Thanks for your help,
here's the screen shot
Nobody encountered this problem?
Ok... sorry had you look in the wrong place. I thought it was looking in the directory with the image in it for what it needed. I just looked at the nandroid code. Turns out... it looks for some executables that are required for the script to run. It doesn't have to do with your image and I think your images are probably fine.
I need you to run 2 more commands so I can see where the problem is. First run:
Code:
env
Next run:
Code:
which unyaffs
The "env" command should show your enviroment variables. What we are looking for is for /system/bin to be in your "PATH" variable. It should be because it checks for another executable first "flash_image" and it is not coming up with an error. The second file it is checking for is "unyaffs". Next you need to check and make sure unyaffs is actually in your /system/bin folder. It is probably not... and would explain the error you are getting.
I guess my first question is... is this happening on all ROMs you have tried (or have you only gotten one up and running)? If it is there may have been a problem when you flashed it. Even though it is possible that you could copy it to the /system/bin I would suggest not doing this. The reason is because if that one file is missing... there may be other files missing that should be there from when you flashed your ROM. These missing files... if there are any... could cause problems later. It might be best just to reflash whatever ROM you are using. I would suggest CM6 (not nighties) and then moving to some other ROM once you get a "known good" to work with.
Hey GoblinLord,
Thanks for your help on this, really appreciate it..
OK, well i've ran the two commands that you said and have attached the screenshot with the output. I've tried going to /system/bin but get permission denied errors through adb.
Although it looks like the PATH is actually /sbin rather than /system/bin ???
As for the roms..
I'm currently using CM6 (the stable version) as this was the only one that I could manage to get to work. As this is a SLCD nexus i dont think there are many roms that have the right drivers for the screen. Its does work fine though.. The nandroid restore is the only part of the phone that i cannot get working....
Again thanks for the help...
jamin100 said:
Hey GoblinLord,
Thanks for your help on this, really appreciate it..
OK, well i've ran the two commands that you said and have attached the screenshot with the output. I've tried going to /system/bin but get permission denied errors through adb.
Although it looks like the PATH is actually /sbin rather than /system/bin ???
As for the roms..
I'm currently using CM6 (the stable version) as this was the only one that I could manage to get to work. As this is a SLCD nexus i dont think there are many roms that have the right drivers for the screen. Its does work fine though.. The nandroid restore is the only part of the phone that i cannot get working....
Again thanks for the help...
Click to expand...
Click to collapse
Hmmm... the permission denied is normal. That is because it is a folder and not an executable. You should be able to do:
Code:
ls -l /system/bin
This will list what is in your /system/bin directory. As for your path being different... that seems a bit strange. I am doing the commands from a terminal on my device... once I get back home today I will do it through the ADB shell and see what I get. The "which" command will only look in the folders in your "PATH" variable for the executable. If /system/bin is not in there I am not sure how it is passing the part where it looks for "flash_image". In my sbin folder I only have the ADB daemon (adbd) executable. What you could do is manually add the /system/bin to your PATH variable while in the shell... that may work. You can try the following:
Code:
PATH=$PATH:/system/bin
Run that before running your restore command. That should manually place the directory you need into your PATH environment variable. I will do a little testing with ADB once I get home and update this if I get to before you try it.
Thanks for the reply....
I won't be able to try this until Wednesday as I have left the USB cable at work ....
I will try it Wednesday and let you know...
Thanks
Sent from my Nexus One using XDA App
jamin100 said:
Thanks for the reply....
I won't be able to try this until Wednesday as I have left the USB cable at work ....
I will try it Wednesday and let you know...
Thanks
Sent from my Nexus One using XDA App
Click to expand...
Click to collapse
I checked my environment variables via ADB. Mine did show the /system/bin in my PATH variable. Seeing as this is a shell being run on your device... I would still venture to say that something may have went wrong when you flashed your ROM originally. That or something you installed changed it for some crazy reason (and shouldn't have). Either way, I still think it would be best to flash again... possibly to a different version. I know you would have had to get a modified version of CM6 so... if you don't mind me asking where did you get your copy?
EDIT: Correction... I am getting the same path variable as you when in recovery mode. I am not quite sure why this is... the guide I found for using nandroid restore through ADB doesn't seem to run into this issue. It might be some kind of issue related to just Amon_Ra recovery. This would mean that Amon_Ra Recovery just didn't add it to the PATH variable... which I guess is rather odd... but whatever. Just try manually adding it to the PATH variable as mentioned above and then run the restore. It should work then.
EDIT 2: I did a bit of researching on that error you are getting when you try and restore in recovery. Reference:
http://forum.xda-developers.com/showthread.php?t=621940
Various people point to things that may cause this error. Is your phone charged? Do you have plenty of space on your SD card?
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
So I decided I wanted to have DSP manager and remembered an app I had on my D1 called "Root Toolbox" that could do it. The developer has since crippled the app so I pulled an old version off the D1 and proceeded to install DSPManager. Everything seemed to work fine until a reboot, I got stuck at the dreaded M. So I came here right away and thankfully found this post:
http://forum.xda-developers.com/showthread.php?t=1236465
So I follow the instructions exactly but when I go to do "adb remount" I got the message "remount failed: Operation not permitted". So I went ahead and did an "adb reboot" and when I got the adb shell back up, I was root, YAY. So I mounted /system and first removed the DSPManager.apk. I knew it also replaced the file /system/lib/libaudioflinger.so based on previous research so I downloaded the system dump and replaced libaudioflinger.so with the original. But here is where it gets weird, as SOON as I replaced the file libaudioflinger.so my phone magically unstuck itself from the M and booted up. Not sure why, but it was a huge relief.
Just wanted to share my experiences in hopes that it will help someone down the road. I'm also kind of curious why it suddenly booted when it got its original libaudioflinger.so back?