Related
my phone seems to be in a really weird state right now - turning it on does absolutely nothing but adb does in fact detect it.
Code:
List of devices attached
HTXXX device
and if i run 'adb reboot recovery' i see the device in recovery mode.
Code:
$ adb reboot recovery
$ adb devices
List of devices attached
HTXXX recovery
also, while in recovery i can do adb shell and attempt to do a nandroid backup, but i get:
Code:
$ adb shell
~ # nandroid backup
E:unknown volume for path [/sdcard]
Can't mount /sdcard
at this point i've called htc to send it in for repair, but i would really like to get a backup before that and also return it to S-ON. i was running the latest clockworkmod and android revolution.
any help would really be appreciated.
Have you tried flashing an RUU?
yes, it keeps failing when trying to reboot into the bootloader. i've given up at this point - will be sending it back to htc and just hope they don't charge me some ridiculous amount just because i have s-off through the revolutionary script.
segfault82 said:
also, while in recovery i can do adb shell and attempt to do a nandroid backup, but i get:
Code:
$ adb shell
~ # nandroid backup
E:unknown volume for path [/sdcard]
Can't mount /sdcard
at this point i've called htc to send it in for repair, but i would really like to get a backup before that and also return it to S-ON. i was running the latest clockworkmod and android revolution.
any help would really be appreciated.
Click to expand...
Click to collapse
Is by any chance you phone connected as disk-drive? Try connecting it as charge only.
well the problem is the screen doesn't turn on so i can't see what's going on. although i'm pretty sure it's not connected as a disk drive because it doesn't automatically enable that.
Dear Sirs,
I have HTC Desire Z with CM 7.0.3 (superuser installed) and s-off. Posting here since the issue seems relevant to android in general rather than specific hardware...
I have already seen the following threads before opening this one but they do not help since I cannot issue any of the commands that they mention:
:http://forum.xda-developers.com/showthread.php?t=1364521
:http://forum.xda-developers.com/showthread.php?t=1087350
:http://forum.xda-developers.com/showthread.php?t=837102 (it says to use mount command but thats exactly where I get the permission denied)
When I boot the phone normally and "adb shell", I can get a root prompt (id command shows root user, "cd" shows "/"). But ANY command I run brings permission denied (even ls, chmod, mount). I literally can't do anything. Same whether I boot with/without S D card. I CAN however issue commands such as "adb pull /init.rc" if I exit and go back to DOS.
If I open a terminal session (with Superuser full permissions), I can SU as root, but again cannot issue any commands without getting "permission denied"/
However if I boot into clockworkmod recovery and mount /data and /system, and then open an adb shell via USB, I can connect as root and browse everything, everything is fine and all commands work OK. /etc/fstab shows all partitions would be mounted as rw.
So it looks like some application during boot, is resetting the permission for /system to be ro, and also removing root's privileges.
Please could you let us know if there is a method to determine what app is doing this during boot. I cannot see anywhere in init.rc where I can catch this application that is doing this and prevent it from making /system inaccessible after boot.
Preferably if someone could point me to the complete log of the boot process that shows each command that is run, I might have a clue as to where in the boot up process, the /system partition suddenly becomes ro and root loses all permissions.
The problem prevents busybox updating and other root apps that need to write to /system.
This was not a problem for months after installing and rooting CM 703, only recently it has become an issue, perhaps following some hidden Google update???
Thanks
Hey guys,
I just can't figure this one on my own. My phone is bricked, so I'm trying to use ADB in Recovery mode to fix it. The problem is, that 'su' always returns 'permission denied', so I can't mount system rw and that's where I'm stuck.
Phone is fully rooted - that's how I was able to brick it in the first place.
'/system/xbin/su' is also present (checked via Aroma).
Is there any way to "fix" this?
in the recovery go to mount and storage then mount /system.It will be mounted as RW.
I have the e3 stock recovery, so there are only these options:
reboot system now
apply update from sdcard
wipe data/factory reset
wipe cache partition
use aroma file manager it have terminal.You can use it in recovery.
or try adb remount
Yes, I know about the aroma terminal and I also tried some commands in it, but without a positive result. But just to be sure, what command(s) did you have in mind?
And 'adb remount' returns:
remount failed: Operation not permitted
if you have e3 recovery that means you havent rooted your phone which means su wont work first root your phone
also it would be great if you could explain a little more as to what you want to accomplish
Oh.. That doesn't sound very good..
I need to modify some files in the system/framework folder.
Anyway, it should be rooted, because I already replaced a system file.
I just found out on the web that in the system settings on CM10 -> Developer settings -> you can set root access also for ADB.
Maybe it helps?
Hi XDA-D,
I kinda helped my tf300t over the edge. I wanted to flash the new stock rom for troubleshooting purposes. I wanted to boot into Recovery but it froze the machine. Because I had fastboot options I pushed a the newest recovery (v6.0.2.3) and all seemed well untill I rebooted. Whatever I do The device boots into Recovery. It doesn't try to load the Rom and doesn't respond to "power vol down/up)
Recovery does start but with errors:
Code:
E: Can't mount /cache/recovery/command
E: Can't mount /cache/recovery/log
E: Can't mount /cache/recovery/last_log
and can't mount any directory (no /system, /cache, /data, /sdcard, etc)
Fast boot doesn't respond any more (keeps waiting for devices and doesn't list the tablet)
Adb recognises the tablet:
Code:
adb status-window
<-[2J<-[2HAndroid Debug Bridge
State unknown
adb devices
111111111111111111 Recovery
I think the boodloader is corrupt and the device defaults to recovery but the directories are gone, making sure that I can't install via fastboot or micro sd. Is there a way to restore this tablet with adb but without fastboot?
RVexx said:
Hi XDA-D,
I kinda helped my tf300t over the edge. I wanted to flash the new stock rom for troubleshooting purposes. I wanted to boot into Recovery but it froze the machine. Because I had fastboot options I pushed a the newest recovery (v6.0.2.3) and all seemed well untill I rebooted. Whatever I do The device boots into Recovery. It doesn't try to load the Rom and doesn't respond to "power vol down/up)
Recovery does start but with errors:
Code:
E: Can't mount /cache/recovery/command
E: Can't mount /cache/recovery/log
E: Can't mount /cache/recovery/last_log
and can't mount any directory (no /system, /cache, /data, /sdcard, etc)
Fast boot doesn't respond any more (keeps waiting for devices and doesn't list the tablet)
Adb recognises the tablet:
Code:
adb status-window
<-[2J<-[2HAndroid Debug Bridge
State unknown
adb devices
111111111111111111 Recovery
I think the boodloader is corrupt and the device defaults to recovery but the directories are gone, making sure that I can't install via fastboot or micro sd. Is there a way to restore this tablet with adb but without fastboot?
Click to expand...
Click to collapse
Hmm that doesnt sound good, CWM really sucks i refuse to use it lol. Does it have a terminal you enter? and have you been able to adb push anything to the tablet?
im thinking if you can adb push twrp to the device and open a adb shell you could try dd if=*path-to-twrp* of=/dev/block/mmcblk0p4
I havnt used the above in your situation so not sure if it will work, hopefully someone else can help. Goodluck mate
JoinTheRealms said:
Hmm that doesnt sound good, CWM really sucks i refuse to use it lol. Does it have a terminal you enter? and have you been able to adb push anything to the tablet?
*
im thinking if you can adb push twrp to the device and open a adb shell you could try dd if=*path-to-twrp* of=/dev/block/mmcblk0p4
*
I havnt used the above in your situation so not sure if it will work, hopefully someone else can help. Goodluck mate
Click to expand...
Click to collapse
*
Haven't tried to push a different recovery because I'm afraid I'll break the last thing that works. I think I can get a remote shell via adb. I was hoping there is a way to push a new kernel and boot but my knowledge is lacking.
RVexx said:
*
Haven't tried to push a different recovery because I'm afraid I'll break the last thing that works. I think I can get a remote shell via adb. I was hoping there is a way to push a new kernel and boot but my knowledge is lacking.
Click to expand...
Click to collapse
Id wait for someone elses input, i dont wanna mess with your adb lol. Im not sure about the above method since adb push would need access to sdcard, dd might work if you already have twrp on the device, again if you can access adb shell and dd works you might have a few things that could work, but even if you have a bricked device its not the end of the world. Asus might repair it, if not and your willing motherboards for these devices seem quite cheap, and if so you will have access to nvflash so something like wont happen again.
JoinTheRealms said:
Id wait for someone elses input, i dont wanna mess with your adb lol. Im not sure about the above method since adb push would need access to sdcard, dd might work if you already have twrp on the device, again if you can access adb shell and dd works you might have a few things that could work, but even if you have a bricked device its not the end of the world. Asus might repair it, if not and your willing motherboards for these devices seem quite cheap, and if so you will have access to nvflash so something like wont happen again.
Click to expand...
Click to collapse
Anyhow, thanks for thinking with me
I'll wait for someone who absolutely loves CWM
Here's where I'm at. I've got the system to give me the Mount /System option in recovery, now i just need assistance getting the build.prop pulled to my PC. What's the procedure for pulling the build.prop from the Android to PC via ADB while the system is mounted in recovery? Why am I getting one of these two ADB errors?
Error 1: Connect failed: closed.
error 2: Failed to get feature set: no devices or emulators
OR, am I approaching it wrong?
Thanks in advance,
K0mraid3
you dont need to be in recovery to do it via adb....
adb pull /system/build.prop
that will pull it to where evr you run the adb command
which would be
C;\adb more than likely
or you can choose a destination with
adb pull /system/build.prop c:\buildprop
if you create a folder called "buildprop" in the root directory of c:\
at least thats how i remember doing it many years ago, ive been away for a while at her majesties pleasure, so i cant try it currently as im not rooted
gav83collins said:
you dont need to be in recovery to do it via adb....
adb pull /system/build.prop
that will pull it to where evr you run the adb command
which would be
C;\adb more than likely
or you can choose a destination with
adb pull /system/build.prop c:\buildprop
if you create a folder called "buildprop" in the root directory of c:\
at least thats how i remember doing it many years ago, ive been away for a while at her majesties pleasure, so i cant try it currently as im not rooted
Click to expand...
Click to collapse
Thanks, so far, its still for some reason denying me permission when OS is booted. So i just cant quite figure out where im supposed to execute these commands, is my issue. I can boot directly to BL from recovery menu, but i can also mount system. i think maybe i need sto send command for r/w.. will try that now.
Another question, when i mount /system in recovery, does that carry over on boot?
no you can re mount system via adb though
Code:
$ adb shell
$ su
# mount -o rw,remount /system
gav83collins said:
no you can re mount system via adb though
Code:
$ adb shell
$ su
# mount -o rw,remount /system
Click to expand...
Click to collapse
1.Needs root for this command. If he have rooted device then why so much trouble needed. Simply use root explorer to copy
2.Since long Samsung have removed system from proc/mounts still magisk system_root can be used
3.Even with system in mounts you can't do system rw on S22 because of Samsung have implemented extra layer of protection. Even not with magisk system_root too
Indeed as of now there is no method available to make stock system/vendor/product/odm rw on S22 even with root access.
4.To copy file from system rw mount not needed, ro is fine
dr.ketan said:
1.Needs root for this command. If he have rooted device then why so much trouble needed. Simply use root explorer to copy
2.Since long Samsung have removed system from proc/mounts still magisk system_root can be used
3.Even with system in mounts you can't do system rw on S22 because of Samsung have implemented extra layer of protection. Even not with magisk system_root too
Indeed as of now there is no method available to make stock system/vendor/product/odm rw on S22 even with root access.
4.To copy file from system rw mount not needed, ro is fine
Click to expand...
Click to collapse
im yet to root my device so i cant test but what about
Code:
adb root
adb disable-verity
adb reboot
Then
Code:
adb root
adb remount
gav83collins said:
im yet to root my device so i cant test but what about
Code:
adb root
adb disable-verity
adb reboot
Then
Code:
adb root
adb remount
Click to expand...
Click to collapse
Do you got what I meant?
leave it.
dr.ketan said:
WTF
Do you got what I meant?
leave it.
Click to expand...
Click to collapse
look, there is no need for condescension and bad language, a simple "no" would have sufficed
Lol not meant to hurt you! but on which planet WTF is bad language
Here search WTF on xda
dr.ketan said:
1.Needs root for this command. If he have rooted device then why so much trouble needed. Simply use root explorer to copy
2.Since long Samsung have removed system from proc/mounts still magisk system_root can be used
3.Even with system in mounts you can't do system rw on S22 because of Samsung have implemented extra layer of protection. Even not with magisk system_root too
Indeed as of now there is no method available to make stock system/vendor/product/odm rw on S22 even with root access.
4.To copy file from system rw mount not needed, ro is fine
Click to expand...
Click to collapse
So my device is strange. It doesn't have root, but it indeed shows options in recovery to apply updates from ADB, SD Card aswell as boot directly to BL and to Mount /System, but when I'm booted, the OS is denying me permission to "Su" . I have verified that USB debugging is activated. So I'm trying to see if there's a way to pull the build.prop from Recovery since the Mount /System option is available, but my computer refuses to recognize the device in while in recovery, but easily finds it in Download, BL mode. No FRP lock. No accounts on device. But also no option to unlock bootloader. This device in particular is/was a development sample so I have no clue what the current state of the bootloader etc is in terms of being unlocked prior to me working on it.
It'd also worth noting that this device was loaded with Android 11 when I received it. I'm not kidding. So idk what's going on with this FrankenGalaxy
K0mraid3 said:
It'd also worth noting that this device was loaded with Android 11 when I received it. I'm not kidding. So idk what's going on with this FrankenGalaxy
Click to expand...
Click to collapse
K0mraid3 said:
So my device is strange. It doesn't have root, but it indeed shows options in recovery to apply updates from ADB, SD Card aswell as boot directly to BL and to Mount /System, but when I'm booted, the OS is denying me permission to "Su" . I have verified that USB debugging is activated. So I'm trying to see if there's a way to pull the build.prop from Recovery since the Mount /System option is available, but my computer refuses to recognize the device in while in recovery, but easily finds it in Download, BL mode. No FRP lock. No accounts on device. But also no option to unlock bootloader. This device in particular is/was a development sample so I have no clue what the current state of the bootloader etc is in terms of being unlocked prior to me working on it.
Click to expand...
Click to collapse
These options are normal in stock recovery and can be used only for flashing official zip (OTA), To have root access on your recovery, you needs custom one (TWRP) which is in development stage on S22
Without twrp, You needs to root device (must have oem unlock option in development option) to access system files while you are booted to android.
Android 11 on S22? Can you show me screenshot of settings - about phone - software info?
dr.ketan said:
These options are normal in stock recovery and can be used only for flashing official zip (OTA), To have root access on your recovery, you needs custom one (TWRP) which is in development stage on S22
Without twrp, You needs to root device (must have oem unlock option in development option) to access system files while you are booted to android.
Android 11 on S22? Can you show me screenshot of settings - about phone - software info?
Click to expand...
Click to collapse
Thanks for the clear answer, that's kind of what I'm working on is trying to gain root access, but like you said, I need oem unlocking, which isn't on this device. So I'm trying to find a backdoor/vulnerability that will take me even one step closer to atleast finding a way to set ro.secure. prop. Something VERY interesting I did find, is that if you put the device to Debug medium or high via device keystring activity, and play with the key combos, you can get booted into a mode called RDX, if you plug it into your dev system with the right drivers, it's treats the phone as if it were a Disk and shows a bunch of VZW upgrade software ment for PCs. I've installed it but haven't got it working quite yett.
No idea what you have shown in screenshot, I'd asked something else.
dr.ketan said:
No idea what you have shown in screenshot, I'd asked something else.
Click to expand...
Click to collapse
Maybe Heindall will give me better results. I just refuse to believe the manufacturers have outsmarted us all on this.