Database Users

~# ???

hey all
so i was one of the lucky ppl who was able to get my phone rooted in the beginning. everything worked perfect, wireless teather, adfree ...
last night i unrooted and installed the OTA then used unrevoked3 to reroot, everything went fine but now when i am in recovery if i type adb shell i get:~# and if i type su its not found in /system/bin...whats going on? i have Superuser.apk all my root aps work but i dont know what the "~#" and why i cant get into su in recovery...

ezy1022 said:
hey all
so i was one of the lucky ppl who was able to get my phone rooted in the beginning. everything worked perfect, wireless teather, adfree ...
last night i unrooted and installed the OTA then used unrevoked3 to reroot, everything went fine but now when i am in recovery if i type adb shell i get:~# and if i type su its not found in /system/bin...whats going on? i have Superuser.apk all my root aps work but i dont know what the "~#" and why i cant get into su in recovery...
Click to expand...
Click to collapse
clockworkmod recovery is root by default, there is no su cause you don't need it. # = su prompt versus $ = user prompt...

Shadowmite said:
clockworkmod recovery is root by default, there is no su cause you don't need it. # = su prompt versus $ = user prompt...
Click to expand...
Click to collapse
So all is good?

Yes....all is good. Reported.

I'm not issuing warnings yet for questions posted in development which may fall under that scope. I have requested a Q&A sub-forum be created for DI. We'll see how that pans out. Until then, please post questions in the thread where you believe your issue is coming from. Otherwise, please post questions in the DI/General sub-forum until a Q&A forum is created. Thanks!

ezy1022 said:
hey all
so i was one of the lucky ppl who was able to get my phone rooted in the beginning. everything worked perfect, wireless teather, adfree ...
last night i unrooted and installed the OTA then used unrevoked3 to reroot, everything went fine but now when i am in recovery if i type adb shell i get:~# and if i type su its not found in /system/bin...whats going on? i have Superuser.apk all my root aps work but i dont know what the "~#" and why i cant get into su in recovery...
Click to expand...
Click to collapse
i have that problem right now. i have the original root(via loop.bat) in place, nothing else. i get the symbol "~#" too when i try to enter the adb shell while in recovery. adb devices show that my phone is attached and i am able to execute most commands. but there are some commands like "cd" that only work in the shell.
so we are going to need to resolve this eventually.
yes, you do not need su in recovery but you will need adb shell.
if there's anyone out there who can help us with this "~#" when typing adb shell in recovery, it would be greatly appreciated.

If you see that then that means you are using adb shell. No need for Su, but if you're removing apps etc mount the /system in the partitions menu of clockworkmod. Then cd /system/app to edit your apps.
Sent from my ADR6300 using XDA App

[Q] ADB "Permission Denied"

hey guys need help so my Mytouch 4G updated and perm rooted, and i keeep gettin gthe permission denied everytime i try and execute a command thru adb thru my pc or on the Terminal Emulator. Did something not go thru on root or am i missing something simple? any help would be greatly appreciated. Thanks

mrpanic7 said:
hey guys need help so my Mytouch 4G updated and perm rooted, and i keeep gettin gthe permission denied everytime i try and execute a command thru adb thru my pc or on the Terminal Emulator. Did something not go thru on root or am i missing something simple? any help would be greatly appreciated. Thanks
Click to expand...
Click to collapse
You may have to run visionary and reboot a few more times to make root privileges stick.
My MyGlacier 4G MINE!!!

Try this:
: adb shell (this should give $)
:$ su (next line type su, this should give you prompt on Super user to allow permission)
:# ( once you get this your good)
Sent from my HTC Glacier using Tapatalk

Try to install visionary and then re install open click temp root then permoot super user should ask to approve click yes. After that restart
Sent from my HTC Glacier using XDA App

Please post questions in Q&A forum. Thank you

ok everytime i try adb shell in terminal emulator it says the permission denied, im gonna try the first reply again and then see....any other ideas?

also guys, when i try and run visionary again it says your device is already rooted, along with when i type su in TE, it gives # with superuser permissions quote showing on bottom of screen, but i was trying to run adb commands from pc or from te and they still show permission denied. SetCPU works.

mrpanic7 said:
also guys, when i try and run visionary again it says your device is already rooted, along with when i type su in TE, it gives # with superuser permissions quote showing on bottom of screen, but i was trying to run adb commands from pc or from te and they still show permission denied. SetCPU works.
Click to expand...
Click to collapse
Ok, go into adb shell and type su + enter. Watch your phone when you do this. Superuser should ask if you want to allow "unknown" root privileges. "unknown" is adb. Click allow and your problems should go away.
My MyGlacier 4G MINE!!!

So typing su works and the message terminal emulator is granted permissions, but then any other commands dont work
Sent via MyTouch 4G

Whats a test command I could try?
Sent via MyTouch 4G

mrpanic7 said:
So typing su works and the message terminal emulator is granted permissions, but then any other commands dont work
Sent via MyTouch 4G
Click to expand...
Click to collapse
I ran into this same issue and it drove me crazy. I would not get prompted by the phone to allow su permissions when going through ADB- kept getting "permission denied"
I did finally get SU permissions through ADB, but I dont recall exactly what I did to get prompted to allow access.
I will try to retrace what I did... believe I had ADB shell running (without su permissions "$"), but I also had terminal emulator running on my phone. I entered the su command on my phone, then I did the same from ADB shell.
Finally the phone prompted me to allow access - accepted - and no problems from that point.
Basically, I just had to keep f'n with it.

Yeah thats my problem exactly. Yeah I appreciate any assistance you can provide. I mean my pc reads my device when I adb devices command, but it wont allow nothing past that. Please keep me informed on anything I can try, also im not thag most fluent with using sdk/adb stuff so any additional info with using that is much appreciated thanks again fellow enthusiasts!
Sent via MyTouch 4G

Have you tried to bacup su, then uninstall su. Reinstall su, Then try it again. MIGHT work
Sent from my HTC Glacier using XDA App

yeah i re-installed su and didnt help, @dbiggs-what can i do thru adb to initiate the su permissions to the device like you did?

I wish I could help more specifically, but I dont remember exactly what I did that allowed me access- just kept trying
Maybe try this...(dont be offended if any of these steps are ones that you already know or have tried, I am just trying to be as thorough as I can from memory)
Open up super user, then go back to the terminal emulator and enter the "su" command to gain superuser permissions.
Plug the phone into the computer, select charge only, enter ADB through tools (probably "C:\Android\tools" if your Android folder is in the root of your harddrive).
from the prompt C:\Android\Tools, enter:
adb shell
then you will get the "$" that you mentioned.
enter the "su" command, and hopefully you will get prompted to allow superuser permissions for ADB.
I am pretty sure these are the steps that I took, just had to keep trying.
Lemme know how it works out.

I see some people here asking about getting su privileges in adb, however I do have SU and I can run su in adb shell. My problem is that I am trying to push some files and use Android Commander. I can't run "adb remount" (remount failed: Operation not permitted), I can't copy files in Android Commander (it's says that I do not have ROOT)
How can I get Read-Write in ADB ??
Edit: Oh, now I got it, I don't have root in ADB, when i type "adb root" it says "adbd cannot run as root in production builds"

Did anyone figure this out? I'm being denied on TE and PC also.

I have managed to be able to get around this issue by going into recovery mode on my phone.
If the end result that you are looking for is to adb push files, then the easier way to do this is to flash clockwork recovery to your phone, then start your phone into recovery mode, mount system and you should be able to push files no problem.
Lemke know if this helps.
Sent from my HTC Glacier using XDA App

mrpanic7 said:
hey guys need help so my Mytouch 4G updated and perm rooted, and i keeep gettin gthe permission denied everytime i try and execute a command thru adb thru my pc or on the Terminal Emulator. Did something not go thru on root or am i missing something simple? any help would be greatly appreciated. Thanks
Click to expand...
Click to collapse
I'm pretty sure your issue has nothing to do with SU access. Most likely, your phone is simply mounting as r/o (read only) when it boots up, so ADB is unable to change anything to the system folder. The easiest way to mount as r/w (Read/Write) is to go into Root Explorer and click the r/w button in the top right corner, and then go to ADB and see if it will allow you to do the same commands that it previously denied.
I have the same issue with my phone mounting as r/o by default, but I haven't been able to figure out how to automount as r/w on the MT4G. If anyone knows how, please share.

I had this same issue, on several android phones including MT4G. Here is how I fixed it.
1. Connect phone via usb (I was in "charge only" mode, not disk drive mode)
2. Open command prompt and navigate to the android tools folder
3. type "adb shell"
4. MAKE SURE YOUR PHONE SCREEN IS ON AND UNLOCKED
- The above step is very important otherwise you will not get the SU prompt
5. At the "$" prompt type "su"
6. Your phone should now display the SU screen asking you to allow the connection root access.
7. Once you allow it, you are golden.
I did this on a windows pc. Hope it helps.

[Q] Command Prompt Issue When Trying To Exit ADB Shell?

Hi this is my first post on the site and i would appreciate it if anyone could help me with this problem. (I know your probably fed up of hearing about rooting problems but anyway!)
I have succesfully installed ADB and as far as i know it seems to be working properley as i can access the ADB shell on my device.
However when i get to a certain stage of the rooting process it all seems to go wrong.
wiki.cyanogenmod.com/index.php?title=HTC_Tattoo:_Full_Update_Guide
I have been using the above rooting guide (can't hyperlink first post!) and i cannot get past stage 7 of the process because the 'exit' command doesnt seem to work in Command Prompt (Windows 7) and it is stopping me from being able to exit the ADB Shell. I have tried other ways of exiting the shell such as ctrl+C but this kills ADB completely and i think that it is undoing the previous steps of the guide.
I do get the message:
uid=0(root) gid=1000(shell) groups=1003(graphics),1004(input),1007(log),1011(adb),1015(sdcard_rw),3001(net_bt_admin),3002(net_bt),3003(inet)
so i think that i have successfully rooted the device but i cannot proceed to push the 'su' file to the device as i can't exit the adb shell, i just keep getting lists of text saying reboot (-n) (-p) and everytime i use the exit command nothing seems to happen and the flashing # symbol keeps coming back.
Has anybody else had this problem? or have any idea of how to stop the ADB Shell with any other commands other than 'exi't or Ctrl+C?
Cheers.

If device is rooted, by writing in command prompt the command "adb shell", must appear the symbol #, if the symbol $ appears the device isn't rooted.
If you cannot use adb from pc, run on device a terminal emulator(you can find one on market) the above command to see if you're rooted. Then you can give the next commands from terminal emulator(maybe you need to copy the nessecary files on sd card and change the related paths to point to sd card)

I'm having the exact same problem while rooting my HTC Tattoo (on Windows 7).
I have Android 1.6 (Donut), the baseband is 13.29a.55.13H_3.35.07.33, kernel is 2.6.29-gf922713 and build is 1.67.173.37.
Please help and thanks in advance . I really want to install CyanogenMod 7...

more info
When i say i have rooted the device i mean temporarily by pushing and changing the 'm7' file, the problem is pushing the 'su' file to the device to make the root permanent.
I do get the # symbol when in ADB Shell but only after changing m7 on the device. As i cannot complete the whole rooting process the # is not there permanently and it returns to the $ symbol.
Thanks for the reply, i will try and do it using a terminal on the device. Do you not need root access to use a terminal app?

I'm having the same issue. When I input exit it stucks into that loop and then I got to ctrl+c, and of course the root does not stick
From that point forward I can't do anything else...
If someone overcome the problem please post.

I just used this app to root a zte blade with a new greek stock rom:
http://forum.xda-developers.com/showthread.php?t=803682
Seems to work for almost all devices and in first post have some info about root levels and links to a workaround for devices that have some lock which prevents the full rooting.
I didn't tried anythink cause the rooting process was successful, but you can try this app and if still have problems try to follow the instructions given.
Good luck.

If you have your mobile rooted can you just use this commands:
cd /data/local/bin/
chmod 755 flash_image
flash_image recovery /sdcard/recovery-clockwork-x.x.x.x-click.img
to perform a recovery flash? Without using the su command?
I don't remember if I tried it, but, if it works I recommend using Androot for rooting the device, it worked for me(checked by Root Checker ).
I'm mentioning this just because you recommended the SuperOneClick app.

Update:
For all trying to get thing done, follow the instructions on 1Click modified by tenis and flash the latest cyanogenmod.
It worked!!!

I got it to work using androot. Cm7 is awesome
Sent from my HTC click using XDA App

exit command in adb seems to lock up
like omgsufc, I also reach this stage and can see the message:
uid=0(root) gid=1000(shell) groups=1003(graphics),1004(input),1007(log),1011(a db),1015(sdcard_rw),3001(net_bt_admin),3002(net_bt ),3003(inet)
Again, like omgsufc, when I issue the command:
# exit
ADB shell seems to go into some kind of loop. Pressing ctrl-c or ctrl-d also give the same results. I thus can't go to the next stage. Any help or clues would be greatly appreciated.
I'm on Ubuntu 11.04.
TIA for any help.

Finally got it to work
No matter what I did, rooting using m7 just didn't work for me (Ubuntu 11.04). Running 'while ./m7 ; do : ; done' got me temporarily rooted as issuing 'id' shows me at 'uid=0(root)'. However, issuing 'exit' just left me in a long loop in the terminal from which it never recovers, and hence I could not complete the root process this way.
So I tried androot, which appeared to root me right away. Issuing 'su' in Android Terminal worked, and doing the same in ADB Shell also gets me to the # prompt. However, issuing the 'flash_image recovery' failed no matter what I did. I tried ROM Manager after this initial androot root: it gives me a success message after flashing ClockworkMod recovery, but when I reboot into recovery it just fails. Fastboot also failed consistently.
Finally, when I tried Terminal Emulator to get root access by issuing the command 'su', it says permission denied, even though Terminal Emulator gave me root access.
So... I unrooted Androot. Again trying to root using m7 I got the same problems as before.
I didn't bother trying flash_image or fastboot and instead tried rooting with androot. After doing so, this time Terminal Emulator allowed root access, which gave me some hope.
So I pulled out ROM Manager again, and woot! My Tattoo is on CyanogenMod 7 and am I a happy camper! I like what Cyanogen has given us: ADW Launcher is as good for me as Sense ever was... actually it's better. And finally I get to use all the new apps I've been wanting to use but wouldn't run on Android 1.6.
So thank you Cyanogen, thank you xda-developers, particularly KalimochoAz, thank you Koushik Dutta for ROM Manager, and thank you, whorever developed androot!

[Q] Motoblur home process failing

Hello All,
I would really appreciate help on this issue I have been having. I recently rooted then unlocked the bootloader of my device. I downloaded a root uninstaller and may have somehow killed the home process from running. Now, when i turn on the device, i get the error
The application Home (process com.motorola.home) has stopped unexpectedly
It does not go away and comes repeatedly back, not allowing me to change any settings whatsoever. I don't know what to do. I tried going into android recover mode and both wiped the device and cleared the cache, but the problem persists. I also tried putting a cyanogenmod version on the devices SD card but cant get it install because for some reason I can't get clockwork mod installed correctly. I cannot turn on USB debugging mode because I can't get into the settings. I tried using the .sbf to flash it but it is the .sbf I used to unlock the device so I am not sure that is the right one or if the right one would even do the trick, I fear that the system files that run the home application may be corrupt, deleted or permanently inactive. I would appreciate any ideas people may have to help me.
Also, becuase I factory reset the device, the bootloader is unlocked, but it is no longer rooted, and I cannot root it at this time becuase I cannot turn on USB debugging mode.

I was looking at the guide here;
http://forum.xda-developers.com/showthread.php?t=1302423
And was wondering why it didn't work when I tried to install CWM, then I noticed something I didnt see;
"DO NOT FORGET TO DO THIS PART: After the install of RomRacers recovery boot up your phone. Open up your favourite file browser (I used Astro file manager to do this ) and navigate to /system/etc/ and delete the file called 'install-recovery.sh'"
Is there a way to do this from the PC as I wouldn't be able to on my device? Or is the fact that it is not currently rooted going to stop me from doing anything?
Thanks,

heronpj said:
I was looking at the guide here;
http://forum.xda-developers.com/showthread.php?t=1302423
And was wondering why it didn't work when I tried to install CWM, then I noticed something I didnt see;
"DO NOT FORGET TO DO THIS PART: After the install of RomRacers recovery boot up your phone. Open up your favourite file browser (I used Astro file manager to do this ) and navigate to /system/etc/ and delete the file called 'install-recovery.sh'"
Is there a way to do this from the PC as I wouldn't be able to on my device? Or is the fact that it is not currently rooted going to stop me from doing anything?
Thanks,
Click to expand...
Click to collapse
If you are familiar with ADB, the basic commands would be:
Code:
adb remount rw
adb shell
While in the ADB shell:
cd /system/etc
rm install-recovery.sh
exit
that should cover it.
let me know if this works for ya.

Thanks for your response. The only problem is my phone isn't in USB debug mode, and I can't set it to be. Any idea of how to get that turned on without being able to get into the settings?
FaithCollapsing said:
If you are familiar with ADB, the basic commands would be:
Code:
adb remount rw
adb shell
While in the ADB shell:
cd /system/etc
rm install-recovery.sh
exit
that should cover it.
let me know if this works for ya.
Click to expand...
Click to collapse

heronpj said:
Thanks for your response. The only problem is my phone isn't in USB debug mode, and I can't set it to be. Any idea of how to get that turned on without being able to get into the settings?
Click to expand...
Click to collapse
can you boot into recovery?

FaithCollapsing said:
can you boot into recovery?
Click to expand...
Click to collapse
I can, and have down a wipe data as well as cleared the cache, problem persists.

Solved!!! I was able to basically button mash until somehow the screen to log into the play store came up. Download launcher pro and that got me back into my phone! Thanks for your help

I deleted an important application on my rooted phone

Note: I'm new to XDA, so I've basically made no posts so far. I tried posting this under HTC Bolt/Evo 10, but since I have not made the 10 post threshold yet, I cannot post there, so I just made the post here. If this post needs to be relocated please let me know.
After rooting my phone (HTC Bolt), I foolishly deleted some bloatware applications without backing them up. One of them was TouchPal, a preinstalled keyboard app. I didn't think this would be much of a problem because I already had it disabled in settings and was using a separate keyboard app for other purposes.
However, when I restart my phone, it always asks me to type my pin and "decrypt" the phone. I'm not sure why it does this (previous cell phone didn't), but apparently (this is only a theory) it uses this keyboard application, so I can't actually type my PIN in to decrypt my phone.
I could be completely wrong, and I might have accidentally deleted some other important file from my phone, but either way, I don't know how to fix my phone right now.
I did a bit of research and found out I was supposed to flash a ROM onto my device. However, I don't think I can even connect my device to my computer because normally I would have to enable USB debugging and file transfers.
So basically: is there a way to connect my phone to my computer that would allow me to do whatever is necessary to let me access my phone again? (also should I be flashing a completely new ROM? I should still have everything on my phone except a couple bloatware applications, so is there an easier workaround?)
Update: I got my phone to connect to my PC by booting it in recovery mode. I'll delete this thread if I can successfully flash a ROM.

Hey!
You have already rooted your phone - perfekt!
Now you can start to your bootloader and from there you can flash a twrp recovery if you haven't yet.
If you didn't, there are many tutorials how to do: google: your phone flash custom recovery via fastboot mode
If you have done this - you can easily backup your data with twrp recovery (I think twrp is the best)
After you have done this you can make a full whipe of your system.
If you have done this maybe the failure isnt anymore, but now you have no code to unlock! If the app is still not there - go to apkmirror.com and download the app(there are even system apps). Or just google "xxx.apk download"
After this you can restore your data from twrp!
Summary:
1. Flash recovery. Via fastboot mode
2. Restore your data via recovery
3. Full Wipe
4. Restart
5. If app is still not there - search for APK and install
6. Reboot to recovery (e.g. volume up and home at starting phone, google...)
7. Restore data
8. Restart to system.
I don't know if this Is work, but it's worth to try.
If this don't work: you can transfer data from phone to PC via fastboot mode and then you can flash custom ROM or stock rom,...
I hope this works!
Greets
Ksa

Ksawerion said:
Hey!
You have already rooted your phone - perfekt!
Now you can start to your bootloader and from there you can flash a twrp recovery if you haven't yet.
If you didn't, there are many tutorials how to do: google: your phone flash custom recovery via fastboot mode
If you have done this - you can easily backup your data with twrp recovery (I think twrp is the best)
After you have done this you can make a full whipe of your system.
If you have done this maybe the failure isnt anymore, but now you have no code to unlock! If the app is still not there - go to apkmirror.com and download the app(there are even system apps). Or just google "xxx.apk download"
After this you can restore your data from twrp!
Summary:
1. Flash recovery. Via fastboot mode
2. Restore your data via recovery
3. Full Wipe
4. Restart
5. If app is still not there - search for APK and install
6. Reboot to recovery (e.g. volume up and home at starting phone, google...)
7. Restore data
8. Restart to system.
I don't know if this Is work, but it's worth to try.
If this don't work: you can transfer data from phone to PC via fastboot mode and then you can flash custom ROM or stock rom,...
I hope this works!
Greets
Ksa
Click to expand...
Click to collapse
Thanks for the reply. How would I install the apk onto my device?

ztcfrank123 said:
Thanks for the reply. How would I install the apk onto my device?
Click to expand...
Click to collapse
I remember an easier way.
Maybe you can install app via ADB in recovery mode.
Therefore you need:
custom recovery
ADB tools installed on your PC
USB Driver installed
The APK downloaded from here: https://www.apkmirror.com/?post_type=app_release&searchtype=apk&s=TouchPal
If you have done this - reboot to recovery.
Navigate on your PC to the adb tools folder where adb.exe is in it. Open CMD with right click on address line.
Then write in CMD:
adb devices
If your phone is found, adb commands are working.
Then copy the APK in the folder where adb.exe is in it.
Type in CMD:
adb push xxx.apk /system/app(the address where you delete apk)
So maybe this works
So first check:
- custom recovery flashed?
- adb tools installed?
- USB driver installed?
If you have further questions, let me know.
KSA

Ksawerion said:
Type in CMD:
adb push xxx.apk /system/app(the address where you delete apk)
Click to expand...
Click to collapse
How would I find out the address where I deleted the apk? I already had adb, USB drivers, and custom recovery installed.

ztcfrank123 said:
How would I find out the address where I deleted the apk? I already had adb, USB drivers, and custom recovery installed.
Click to expand...
Click to collapse
How did you delete the files?
Nice, then boot into recovery start CMD where you adb is installed and write" adb devices"
Do you see your device?

Ksawerion said:
How did you delete the files?
Nice, then boot into recovery start CMD where you adb is installed and write" adb devices"
Do you see your device?
Click to expand...
Click to collapse
The files were deleted within the phone itself through Titanium Backup, so I have no idea where the file location is. As of now, I can adb push the apk, but I don't know where to push it to.

ztcfrank123 said:
The files were deleted within the phone itself through Titanium Backup, so I have no idea where the file location is. As of now, I can adb push the apk, but I don't know where to push it to.
Click to expand...
Click to collapse
The now try:
adb remount
adb push Xxx.apk /system/app
adb shell chmod 644 /system/app/xxx.apk
adb reboot

Ksawerion said:
The now try:
adb remount
adb push Xxx.apk /system/app
adb shell chmod 644 /system/app/xxx.apk
adb reboot
Click to expand...
Click to collapse
Sorry for the late reply.
The command "adb shell chmod 644 /system/app/xxx.apk" doesn't work for some reason. It says it is not a directory. (I changed the name from xxx to the actual apk name by the way)

ztcfrank123 said:
Sorry for the late reply.
The command "adb shell chmod 644 /system/app/xxx.apk" doesn't work for some reason. It says it is not a directory. (I changed the name from xxx to the actual apk name by the way)
Click to expand...
Click to collapse
Okay then forget this command and only try 'adb push' command, and restart phone maybe it works. Merry Christmas bre

Ksawerion said:
Okay then forget this command and only try 'adb push' command, and restart phone maybe it works. Merry Christmas bre
Click to expand...
Click to collapse
Yeah... I already tried that. Also I tried a bunch of other adb commands like deleting the file and it couldn't find the directory either .
Merry Christmas to you too!

ztcfrank123 said:
Yeah... I already tried that. Also I tried a bunch of other adb commands like deleting the file and it couldn't find the directory either .
Merry Christmas to you too!
Click to expand...
Click to collapse
Was pushing successful? What says CMD after 'adb push'?