Database Users

[SOLVED]Just flashed latest 0.3 ROM - no root?

EDIT: SOLVED
I just flashed the latest ROM but when I enable debugging and type "adb shell" im getting "$" instead of "#"...? I'm trying to remount the filesystem "mount -o rw,remount /dev/block/mtdblock3 /system" but am getting access denied because of this.
Do I need to try reflashing?

you need to adb shell then type "su" to get to a root shell i believe

EDIT: SOLVED! I was too blind to notice i had to allow the root request on my phone. thanks!
after i type 'adb shell' and get "$" everything i type next just gets echoed
ex:
Code:
$ su
su
test
test
etc

gohamstergo said:
EDIT: SOLVED! I was too blind to notice i had to allow the root request on my phone. thanks!
after i type 'adb shell' and get "$" everything i type next just gets echoed
ex:
Code:
$ su
su
test
test
etc
Click to expand...
Click to collapse
Usually if you have root, adb shell will automatically grant root access...the notification on the phone is a new one to me...

xsnipuhx said:
Usually if you have root, adb shell will automatically grant root access...the notification on the phone is a new one to me...
Click to expand...
Click to collapse
It seems to be caused by the "Superuser Permissions" app, included with the ROM

[Q] Editing Build.prop results in failure to boot [bricked]

As you may know, some Android games especially most Gameloft games are not compatible with the Kindle Fire. So in efforts to find a way to make certain Gameloft games to work such as Modern Combat 2 and Shrek Kart and others, I resorted to editing my build.prop in the systems folder to make my device compatible with the apps. So I copied the original build.prop file, renamed it, and saved it to my SD Card folder. I took the copy I made and I then replaced it with the build.prop from HTC Glacier. (I never knew what could possibly happen) So then to apply those settings you have to reboot the device. I rebooted the Kindle and now it won't boot up. It get's to the Kindle Fire screen when booting up but after several seconds it just shows a black screen. No physical damage has been incurred to it but I feel like my stupid mistake of modding the build.prop resulted in the Kindle Fire unable to boot up correctly. It also isn't recognized by the PC when I hook it up to a USB cable. So far I've found nothing that could help to solve this. I've seen a Factory Default Settings Cable which is a special cable to reverts the device to its factory default settings but I'm not too sure if that would work. I'm in desperate need of help as in I use my Kindle Fire for everyday work and play. Thanks.
EDIT: I've tried adb push and renaming and moving the build.prop into the /system/ but returns that it is a Read-File System Only. Also adb shell and su doesn't work as in it ends up with segmentation fault. I've tried to zergRush root it and permanently root it using KFU but it ends up with 'Cannot Access Package Manager. Is System running?' Also the mount -o rw,remount.....command doesn't work either as it says Permission Denied. All of this would be easy to accomplish if only it ADB allowed me to write onto the /system file.
EDIT**: The biggest issue I'm faced with is the permission settings that prevent my from editing anything. You cannot simply change it from RO to RW because apparently the ADB is not rooted. And I also can't root it because problems exist when accessing either Package Manager or Activity Manager. What I need is a way to access the /system files without a root (non-rooted). Either that or enable fastboot because I cannot access that either. On a reply on the second page is the resulting lines when changing bootmodes on the KFU.

Don't know how to fix your problem, but just wondering, did you just completely replace the kindle fire build.prop with the HTC glacier? Because you can't do that, it will, as you have learned, mess up your device.. Your supposed to edit the build.prop and just change a few things. Next time read up on the subject before deciding to mod the device you use everyday...

the cable you'r talking about is a "factory cable" it forces the kf to fastboot mode - it don't restore any settings !
you need fastboot mode to install fff (firefirefire - custom bootloader) and twrp (recovery)
do you allready have installed fff & twrp (or cwm) ?
if you have twrp installed and booted into then you have adb command available and can copy back the original build.prop

Did you remember to restore the read/write permissions to build.prop? It should be set to 644.

As already stated, your not supposed to replace the whole file, build.prop tells android which device you have, so now Android thought and configured itself to different hardware config. which is not available to it. Adb seems like the only option.

I should have really looked more into it before modifying the build.prop. I replaced the ENTIRE build prop with the build.prop of HTC Glacer. (I know, i know I was stupid) And referring to the factory cable, I don't think I'll resort to that: too time consuming. In regards to the last person that posted before me who said that my only option was ADB could you elaborate? Thanks for all your feedback.

gococogo321 said:
I should have really looked more into it before modifying the build.prop. I replaced the ENTIRE build prop with the build.prop of HTC Glacer. (I know, i know I was stupid) And referring to the factory cable, I don't think I'll resort to that: too time consuming. In regards to the last person that posted before me who said that my only option was ADB could you elaborate? Thanks for all your feedback.
Click to expand...
Click to collapse
Your going to have to use adb to basically remove the HTC Glacier build.prop and replace it with the original build.prop.
For example:
Adb remount <- allows you to mount system as rw
Adb pull /path-to-original/build.prop
Adb push build.prop /system
Adb shell chmod 644 /system/build.prop <- sets permissions to rwrr
Adb reboot
Sent from my Kindle Fire using xda premium

You dont have access to recovery? Either TWRP or CWM?

daggy1985 said:
Your going to have to use adb to basically remove the HTC Glacier build.prop and replace it with the original build.prop.
For example:
Adb remount <- allows you to mount system as rw
Adb pull /path-to-original/build.prop
Adb push build.prop /system
Adb shell chmod 644 /system/build.prop <- sets permissions to rwrr
Adb reboot
Sent from my Kindle Fire using xda premium
Click to expand...
Click to collapse
I tried doing that but it says something like Access Denied or Read-Only File System when i try to push the build.prop into it.

gococogo321 said:
I tried doing that but it says something like Access Denied or Read-Only File System when i try to push the build.prop into it.
Click to expand...
Click to collapse
Did you use the 'adb remount' command? Sometimes, when attempting to push a file to the system, I get the 'read-only file system' and I have to issue adb reboot followed by adb remount and then push the file again. It seems after a time the mount system as read write automatically goes back to read-only.
Sent from my ADR6400L using xda premium

Have you got TWRP or ClockworkMod?
Because you could flash a new rom then.

abd - root mode
Perhaps, running adb in root mode will
allow you to push the original build.prop
back. Then execute "adb remount / rw" to mount the
root directory as read/write. Hopefully you will be able to push
it then follow daggy1985's instructions.
* In Win 7, type "cmd " at the 'SEARCH/RUN' and hold
shift + ctrl while hitting 'Enter' to put yourself
in Admin mode which apparently makes adb work in root mode when you launch it.
* Xda-dev is the coolest site for Android that I have seen. Kudo's to everyone participating.

sum1nil said:
Perhaps, running adb in root mode will
allow you to push the original build.prop
back. Then execute "adb remount / rw" to mount the
root directory as read/write. Hopefully you will be able to push
it then follow daggy1985's instructions.
* In Win 7, type "cmd " at the 'SEARCH/RUN' and hold
shift + ctrl while hitting 'Enter' to put yourself
in Admin mode which apparently makes adb work in root mode when you launch it.
* Xda-dev is the coolest site for Android that I have seen. Kudo's to everyone participating.
Click to expand...
Click to collapse
Thanks but I have actually been running it from Administrator from the very beginning. I've used Kindle Fire Utility KFU and it says that ADB Server is Online and my Bootmode is 4000 but it says ADB root: No. And whenever I choose any bootmode whether it be Normal, Fastboot, or Recovery, it always shows this:
***********************************************
* Activating Normal (4000) *
***********************************************
Installing BurritoRoot, Courtesy of Jcase of TeamAndIRC!
1393 KB/s (1164225 bytes in 0.816s)
Error: Could not access the Package Manager. Is the system running?
Activating BurritoRoot...
Error type 2
android.util.AndroidException: Can't connect to activity manager; is the system
running?
Elevating the Shell...
* daemon not running. starting it now *
* daemon started successfully *
/data/local/tmp/BurritoRoot3.bin: permission denied
mount: Operation not permitted
mount: Operation not permitted
failed to copy 'files\rbfb' to '/system//rbfb': Read-only file system
Unable to chmod /system/rbfb: No such file or directory
Unable to chmod /system/rbfb: No such file or directory
mount: Operation not permitted
mount: Operation not permitted
***********************************************
* Root Activated *
***********************************************
The kindle is successfully running in root mode.
<idme> Invalid permission
reboot: Operation not permitted
Same goes for the Temp Burrito Root and installing FFF and TWRP. It always shows something about cannot access Package manager. I have no clue what the Package Manager even does but apparently I cannot find a solution to that.

I think you need to get a factory programming cable like we talked about on gtalk. I'm confident that will fix this.
Sent from my DROIDX using Tapatalk

I used android commander for windows, mounted system in TWRP and used android commander to copy a new working build.prop to the right place.
With a cable from my htc desire.

would make a little test:
issue "adb shell"
if you get a error message your up to a factory cable because the system shell is messed up and you have no possibility to get to fastboot mode to install fff & twrp
if you get a $ or # prompt you can resume and try "mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system" to mount system in read/write mode

daggy1985 said:
Your going to have to use adb to basically remove the HTC Glacier build.prop and replace it with the original build.prop.
For example:
Adb remount <- allows you to mount system as rw
Adb pull /path-to-original/build.prop
Adb push build.prop /system
Adb shell chmod 644 /system/build.prop <- sets permissions to rwrr
Adb reboot
Sent from my Kindle Fire using xda premium
Click to expand...
Click to collapse
hey, I've tried to remount my rooted galaxy y, fall in for same problem.but there show this message; "remount failed: Operation not permitted"
my device's usb debugging mode was off in last entire.
what I have to do now?

how did u edit build.prop in the first place if u don't have root and this might help
http://yaseminavcular.blogspot.com/2012/01/how-to-get-bricked-kindle-fire-back-to.html?m=1
Sent from my R800i using Tapatalk

[Q] Help - adb shell permission denied, after Vega Tools problem

I am trying to install a custom ROM to Advent Vega tablet (here in Brazil, sold as Toshiba MyPad). Tried a lot of things, for a long time.
When I try to install CWM, using nvflash or adb, it appears not to work. When I booted into Recovery, very few options appear, only to restore a backup and Wipe data. No option for install zip from sdcard and others I am used to in other devices.
So, I installed Vega Tools 4.1, and tried other ways. One of the tries was an option to install Corvus over Stock ROM.
After running that, my problem got worse. Now, the tablet does not boot anymore. I can yet put it in flash and use adb.
I realized that the script ran by VegaTools did this "amazing" thing:
adb-windows.exe shell /sbin/busybox rm -r /system/* ; /sbin/busybox mkdir -p /system/bin ; /sbin/busybox cp /data/mcr/sh /system/bin/sh
adb-windows.exe shell /sbin/busybox sync
So, it destroyed the /system and the following commands did not work to rebuild it to the new ROM.
Ok, my situation now is:
I copied /system/bin files to the devices using adb push, but now when I try to get into the device via adb shell I receive:
C:\Users\claroedu\Downloads\Software\Android\Toshiba MyPad\windows>adb -s 037c70c141dfc1d7 shell
- exec '/system/bin/sh' failed: Permission denied (13) -
So, I cannot get into the device to fix the permissions, and cannot do anything else.
Another very strange thing: after I ran that trash script, now adb find 2 devices, when threre is only one connected:
C:\Users\claroedu\Downloads\Software\Android\Toshiba MyPad\windows>adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
037c70c141dfc1d7 device
emulator-5554 device
Before that, only the emulator one appeared.
Can you guys provide me some help, on how to fix this? Firstly, how could I get into adb shell again, bypassing this "permission denied" error?
I am using adb on windows.
Thanks a lot for any help, in advance.
Eduardo
EDIT: now the things appear to be even worse. Now, the tablet is in an infiite loop. It appears as adb device, and few seconds after, reboots

No one can help me?
eclaro said:
I am trying to install a custom ROM to Advent Vega tablet (here in Brazil, sold as Toshiba MyPad). Tried a lot of things, for a long time.
When I try to install CWM, using nvflash or adb, it appears not to work. When I booted into Recovery, very few options appear, only to restore a backup and Wipe data. No option for install zip from sdcard and others I am used to in other devices.
So, I installed Vega Tools 4.1, and tried other ways. One of the tries was an option to install Corvus over Stock ROM.
After running that, my problem got worse. Now, the tablet does not boot anymore. I can yet put it in flash and use adb.
I realized that the script ran by VegaTools did this "amazing" thing:
adb-windows.exe shell /sbin/busybox rm -r /system/* ; /sbin/busybox mkdir -p /system/bin ; /sbin/busybox cp /data/mcr/sh /system/bin/sh
adb-windows.exe shell /sbin/busybox sync
So, it destroyed the /system and the following commands did not work to rebuild it to the new ROM.
Ok, my situation now is:
I copied /system/bin files to the devices using adb push, but now when I try to get into the device via adb shell I receive:
C:\Users\claroedu\Downloads\Software\Android\Toshiba MyPad\windows>adb -s 037c70c141dfc1d7 shell
- exec '/system/bin/sh' failed: Permission denied (13) -
So, I cannot get into the device to fix the permissions, and cannot do anything else.
Another very strange thing: after I ran that trash script, now adb find 2 devices, when threre is only one connected:
C:\Users\claroedu\Downloads\Software\Android\Toshiba MyPad\windows>adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
037c70c141dfc1d7 device
emulator-5554 device
Before that, only the emulator one appeared.
Can you guys provide me some help, on how to fix this? Firstly, how could I get into adb shell again, bypassing this "permission denied" error?
I am using adb on windows.
Thanks a lot for any help, in advance.
Eduardo
EDIT: now the things appear to be even worse. Now, the tablet is in an infiite loop. It appears as adb device, and few seconds after, reboots
Click to expand...
Click to collapse
Please, any help?

[Q] CWM ADB Shell All Commands Permission Denied

Greetings,
I'm new here, and can't get over to the developers forums to ask. I have two GT-I9500s for development purposes, one if full of junk, and the other is still stock, except for recovery. They both have CWM Recovery v6.0.3.2, the latest available pre-compiled I've found. The stock phone has only been booted once. That system is not rooted (and this is my whole point, I want as close to stock as possible)
I am attempting to extract the system image from Stock I9500. I have booted into CWM Recovery mode, then "adb shell" into the device. All commands I issue to the shell return "Permission Denied"
Code:
:$ adb shell
~ $ ls
/sbin/sh: ls: Permission denied
~ $ dd of=/storage/extSdCard/SYSTEM.img if=/dev/block/mmcblk0p20 bs=4069
/sbin/sh: dd: Permission denied
~ $ su
/sbin/sh: su: Permission denied
~ $ sudo su
/sbin/sh: sudo: Permission denied
I have tried to use Advanced->Fix Permissions to no avail.
CWM is pure and latest from www dot clockworkmod dot com slash rommanager (new users apparently cannot post links). CWM is able successfully operate "Backup to External" from the stock device.
The end goal is to clone the clean, stock device onto the other one. CWM claims success on "Restore from External" to the other device, but it sits on the "Samsung" loading screen forever.
A solution to either or both of these problems would be appreciated.
This was accidentally posted to General a few minutes ago, but as a new user, I don't have the ability to delete it.
-MM

You need to boot the device and then connect it to adb. Then you get a popup on your phone to allow your pc. After that you can use adb from cwm.

Lennyz1988 said:
You need to boot the device and then connect it to adb. Then you get a popup on your phone to allow your pc. After that you can use adb from cwm.
Click to expand...
Click to collapse
I booted into android, connected it to Ubuntu, enabled ADB, authorized the device, chose to remember the device, then "adb shell" into the phone. I can LS and CD around.
I rebooted into CWM Recovery, did "adb shell" and still cannot execute LS. CD works but that is bash internal not a program. Other programs are still "Permission Denied"

I am not that an expert of adb, but couldn't that be caused by the fact that you are not rooted?

Lennyz1988 said:
I am not that an expert of adb, but couldn't that be caused by the fact that you are not rooted?
Click to expand...
Click to collapse
You're conflating the environments. CWMis inherently rooted; when in recovery, Android is never booted. I have execute permission in Android, not in CWM.

nvm

As resolution to my problem, I never did fix Clockwork Mod. Instead, I flashed TWRP for the I9500 and it allows me to execute
Code:
adb shell su -c ...

reboot disemmcwp doesnt work

Hi, "adb shell reboot disemmcwp" doesnt work for me on 2017G 7.1.1 (B05).
Some weeks ago i used a different command that worked. But i cant remember this command and cant find it anymore via google.
Does anyone know which command it is?!
thanks.

It depends on where you're doing this at. Are you using CMD or terminal on the phone?

nolimit78 said:
Are you using CMD or terminal on the phone?
Click to expand...
Click to collapse
cmd as admin and also with terminal (root).

Spillunke said:
cmd as admin and also with terminal (root).
Click to expand...
Click to collapse
I just used 'adb reboot disemmcwp' and it worked.

This command doesnt work for me.
No effect with CMD or terminal. There is an other similar command that works.
EDIT: im not sure, but is it maybe a problem of magisk? I use Magisk, not SuperSu. Would it work with SuperSu?

PUSH

Spillunke said:
PUSH
Click to expand...
Click to collapse
Did you try it? What was the error? Its very bad practise to just say "it did not work".

After booting up, i cant deinstall system apps for example.
Now i switched to an other stock rom and now i can deinstall systemapps, but there are still problems: cant delete files in system/ but this seems to be an magisk based issue.

Spillunke said:
After booting up, i cant deinstall system apps for example.
Now i switched to an other stock rom and now i can deinstall systemapps, but there are still problems: cant delete files in system/ but this seems to be an magisk based issue.
Click to expand...
Click to collapse
try mount -o rw,remount,rw /system (as root)
if that doesnt work, try this in terminal in twrp.

Zobat said:
try mount -o rw,remount,rw /system (as root)
if that doesnt work, try this in terminal in twrp.
Click to expand...
Click to collapse
All in one line or are this 3 single commands?

hi guys.
this simple process is so hard for me but somehow i managed to reboot disemmcwp
i learned that my ZTE HSUSB driver not properly installed (check through you device manager).
after properly installed it, i manage to pair with my laptop
before
C:\adb>adb shell
* daemon not running; starting now at tcp:5037
* daemon started successfully
error: device unauthorized.
after
C:\adb>adb shell
[email protected]:/ $
so just type
C:\adb>adb shell
[email protected]:/ $ reboot disemmcwp

colmanjr said:
hi guys.
this simple process is so hard for me but somehow i managed to reboot disemmcwp
i learned that my ZTE HSUSB driver not properly installed (check through you device manager).
after properly installed it, i manage to pair with my laptop
before
C:\adb>adb shell
* daemon not running; starting now at tcp:5037
* daemon started successfully
error: device unauthorized.
after
C:\adb>adb shell
[email protected]:/ $
so just type
C:\adb>adb shell
[email protected]:/ $ reboot disemmcwp
Click to expand...
Click to collapse
msm8974? you sure you have an axon7?