Database Users

[q] adb remount wont work on vibrant

So i rooted my vibrant with the hopes of removing some of the bloatware. i rooted with the one click root method, loaded clockwork recovery, i know i am rooted but every time i try adb remount i get remount failed: no such file or directory.
so i tried going into clockwork recovery in the partition menu and mounting system there and trying adb remount and got remount failed: operation not permited. i ran adb root and got root can not run on factory builds (or something close to that)
in adb shell ive tried mounting every which way i can think of and nothing works.
ive searched all over and havent been able to find a fix, please help

root explorer didnt work either
also i tried deleting the system apps with root explorer and it would mount either

adb remount wont work on a factory kernel like it says
you can use adb shell and use su to give you root access, you also need to remount /system so it's not a read-only filesystem, there are several posts around here detailing how

cojonesx said:
adb remount wont work on a factory kernel like it says
you can use adb shell and use su to give you root access, you also need to remount /system so it's not a read-only filesystem, there are several posts around here detailing how
Click to expand...
Click to collapse
like i said in my post, i tried shell and couldnt get it to mount. maybe i did it wrong

[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] Kindle fire dies

Houston, we've got a problem:
I did root on my kindle fire device. Everything worked well by now. Then I tried to copy android.vending_v3.4.4.apk (new market) to /system/app and it did not work even with root permissions, I changed permissions to whole directory /system/app to 777 and then I changed back the permissions for the directory /system/app and set permissions for com.android.vending_v3.4.4.apk to rw-r--r-- a clicked on the file and I got an error, which I didnt record for myself. I turned off and on my Kindle and from this moment it is not possible to start up the device. I stil have Kindle logo flashing. Could you please help me to solve this problem? Is it possible to make any flash? If yes, how?

I would use adb to fix permissions for /system/app, you can find good instructions a couple of pages into stickied thread on unbricking.

problem
I'm doing something wrong. I can not change the permissions from Read-only to Read-write. Can you please write what procedure should I do?
adb devices
List of devices attached
700E002600000001 device
adb remount
remount failed: Operation not permitted
adb -d shell chmod 777 /system/app
Unable to chmod /system/app: Read-only file system
My bugreport: motus[dot]sk[slash]bugreport.txt - its too long to attachment.

Try su
Sent from my SPH-D710 using xda premium

grebec said:
I'm doing something wrong. I can not change the permissions from Read-only to Read-write. Can you please write what procedure should I do?
adb devices
List of devices attached
700E002600000001 device
adb remount
remount failed: Operation not permitted
adb -d shell chmod 777 /system/app
Unable to chmod /system/app: Read-only file system
My bugreport: motus[dot]sk[slash]bugreport.txt - its too long to attachment.
Click to expand...
Click to collapse
You obviously didn't read the thread the above poster is talking about. I give clear instructions on the main post of said thread to fix your problem. If you would read it first you might not be having these issues. If you do continue to have problems please direct them to the appropriate thread (again, the unbricking/restore KF thread).

unbricking/restore KF thread
I have read "[HOW TO] Unbricking/Restoring your Kindle Fire". I did as instructed and I ended phrase "fastboot -i 0x1949 reboot" Kindle fire wrote "Your kindle has detected a problem and must clear app storage". After restart stopped working completely. Kindle logo before unbrick always flashing, but now, only light.
If I kindle fire connect to an ADB report is:
db shell
* daemon not running. starting it now *
* daemon started successfully *
error: device not found
I need to be there again complete image. How do I do? I do not know connect Kindle fire with computer.

Failed root attempt - what next??

This question originally got posted on the relevant thread in the Android dev forum, but didn't get any replies so am trying it here in hope....I'm looking for advice on what I can try next which would be safe to try.
I installed and ran the Google Nexus 7 TOOLKIT V4.0.0, but the root failed (and I was also unable to backup the ROM, probably because the root failed). I did the following using the toolkit:
- unlocked the bootloader
- tried rooting using the SuperSU Method (I'm running build JOP40D on a brand new tablet
- got the "downloading boot.img" message (OK), and it rebooted
- did the Android setup after the reboot
- selected USB debugging mode - the tablet rebooted.
During the above process I noticed the message "remount failed: operation not permitted" amongst a stream of other messages.
The subsequent install of BusyBox also failed, with the following messages amongst others:
Code:
Setting permissions..
Unable to chmod /system/xbin/su: No such file or directory
Unable to chmod /system/app/Supervisor.apk: No such file or directory"
...
Testing busybox has been installed properly
...
/system/bin/sh: su: not found
Sending the command 'ls -l /system/xbin/' to device..
You should see a list of all busybox commands
/system/bin/sh: su: not found
Completed
How can I establish what the current state of my machine is, and what is the safest next step in my attempts to root it?

unlocked the bootloader? then all you have to do is fastboot flash a custom recovery then flash the su binaries or a custom rom then reboot. btw, dont use root toolkits, especially if your not familiar with basic procedures. nexus devices dont need root toolkits, its just as easy to root your device the right way.

simms22 said:
unlocked the bootloader? then all you have to do is fastboot flash a custom recovery then flash the su binaries or a custom rom then reboot. btw, dont use root toolkits, especially if your not familiar with basic procedures. nexus devices dont need root toolkits, its just as easy to root your device the right way.
Click to expand...
Click to collapse
Well, I think the Unlock Bootloader part worked. How could I check if it was successful?

itm said:
Well, I think the Unlock Bootloader part worked. How could I check if it was successful?
Click to expand...
Click to collapse
It seems that my attempt to unlock the bootloader wasn't successful - when I re-tried the Root option from the toolkit I got a message saying that the bootloader was locked.
So....I tried to unlock the bootloader again (with the tablet in Fastboot mode). I got the Yes/No option on tablet and selected Yes. I saw red text at the bottom of the Fastboot screen saying "Lock state - unlocked". So I then selected the option to Root (option 2, using the Chainfire method. This failed with the following errors:
remount failed: Operation not permitted
(then a few "no such file" messages removing old root files)
Pushing superuser.apk and su binary..
failed to copy root\su to /system/xbin/su : Read-only file system
failed to copy root\Superuser.apk to /system/app/Superuser.apk : Read-only file system
Setting permissions..
Unable to chmod /system/xbin/su: no such file or directory
Unable to chmod /system/app/Superuser.apk: no such file or directory
It looks like it's not being allowed write access to the drive???

[Q] [Q} Having issues getting bypasslkm.zip installed

Hello! I'm trying to help a friend root his phone and I totally f'd it up and now I have no wifi or data and I can't figure out for the life of me how to get bypasslkm.zip installed I've tried installing it from SD card with invalid signature message and I've tried adb sideload and adb push as per the post
"adb push bypasslkm /data/local/tmp
cd /data/local/tmp
chmod 755 bypasslkm
./bypasslkm"
I keep getting "error: closed" what am I doing wrong? I'm a total noob :crying:

shanda5303 said:
Hello! I'm trying to help a friend root his phone and I totally f'd it up and now I have no wifi or data and I can't figure out for the life of me how to get bypasslkm.zip installed I've tried installing it from SD card with invalid signature message and I've tried adb sideload and adb push as per the post
"adb push bypasslkm /data/local/tmp
cd /data/local/tmp
chmod 755 bypasslkm
./bypasslkm"
I keep getting "error: closed" what am I doing wrong? I'm a total noob :crying:
Click to expand...
Click to collapse
You ran the last commands in adb shell or Terminal Emulator right? Also it's easier to get the flashable bypasslkm zip from the downgrade thread, flash that in safestrap, and run it with init.d
Sent from my SGH-I337 running Blackbox 3.0