Is it possible to do it? Because i dont eant to trigger the safety net so i dont want to install recovery and root
I want to only pull and push from adb with the stock recovery
not possible.
build.prop would not be visible unless you have root.
pull and push does not work with stock recovery - only sideload (adb shows sideload mode when "adb devices").
What are you trying to achieve by editing build.prop?
Related
I have Root permission in my ROM (Using a DocRambone FroYo ROM). But when I reboot in Recovery mode (blue chars, I think normal recovery from Samsung), and start ADB Shell, the prompt is $ and I have no root permission (everything is denied).
If I reboot in Clockwork Recovery 2.5.1.2 (using ROM Manager), the one with green chars, the Galaxy is isolated and if I try ADB Shell, the result is Device not found...
Before Galaxy I had a Desire... with it, when rooted, I had root permission in Recovery and in normal boot.
How To have root permission available in Recovery too on Galaxy?
I need to do some operation via ADB shell. Or there is a way to flash Clockwork Recovery in the place of the normal Recovery (as I had in my Rooted Desire)?
Thanx
tesking said:
I need to do some operation via ADB shell. Or there is a way to flash Clockwork Recovery in the place of the normal Recovery (as I had in my Rooted Desire)?
Thanx
Click to expand...
Click to collapse
run adb root in recovery from this kernel
PS: I presume its a froyo ROM though.. dont know if there are any kernels supporting this in eclair.
tesking said:
I have Root permission in my ROM (Using a DocRambone FroYo ROM). But when I reboot in Recovery mode (blue chars, I think normal recovery from Samsung), and start ADB Shell, the prompt is $ and I have no root permission (everything is denied).
If I reboot in Clockwork Recovery 2.5.1.2 (using ROM Manager), the one with green chars, the Galaxy is isolated and if I try ADB Shell, the result is Device not found...
Before Galaxy I had a Desire... with it, when rooted, I had root permission in Recovery and in normal boot.
How To have root permission available in Recovery too on Galaxy?
I need to do some operation via ADB shell. Or there is a way to flash Clockwork Recovery in the place of the normal Recovery (as I had in my Rooted Desire)?
Thanx
Click to expand...
Click to collapse
if using ULTK (afaik doc's rom use that), you can type "adb root" on your PC, and the next time you say "adb shell" you'll get root.
sztupy said:
if using ULTK (afaik doc's rom use that), you can type "adb root" on your PC, and the next time you say "adb shell" you'll get root.
Click to expand...
Click to collapse
I tried but without success. If I enter in Recovery (standard one, with blue chars), and I type adb root, the answer is something like "adbd cannot have root privileges in production builds". If I try same command in Clockwork Recovery (started by ROM Manager, reboot in Recovery, the one with green chars), the result is "Device not found".
Ciao!
I think that the right way is to replace original recovery with Clockwork recovery... but how to?
I wanna change the battery icon so I replace the original framework-res.apk. Then I can't boot it. It stops on the screen of the cross. I have backed up the original apk. What can I do? Many thanks.
P.S. Stock Rom 2.3.6
Did you do a nandroid backup?
Do you have ADB set up and can the phone still show up in ADB?
Do you have unlock bootloader?
Assuming you have root and adb, you can just do
adb remount
adb push framework-res.apk /system/framework/
adb reboot
the framework-res.apk mentioned above is the original one. After the reboot things should be fine.
No nandroid backup
Rooted but locked bootloader
I have tried ADB but it couldn't detect my device
Can I use the push command though it's not found?
I doubt it but you can always try.
Probably have to do the passimg method.
Try doing a fix_permissions from recovery. If you added the file without changing the permissions, it could be causing all your problems.
If you have a custom recovery, boot into that and push the file. Otherwise, either unlock your bootloader or use a PASSIMG, both of which will wipe your device.
P.S. I don't think you can mess around with that apk unless your ROM is deodexed.
Sent from my Galaxy Nexus using Tapatalk
Is it possible to boot into CWM directly.
I am currently using this..
Bricked my phone while renaming framework-res.apk to framework-res.apk.bak .
Can't use adb push in recovery "Read-only file system" error..
Can't use adb remount as well, "Operation not permitted"
Edit: Sorry, please delete this thread. Found a way to rename back the framework-res.apk within recovery and using adb shell
[Emergency Guide] How to Blank or regenerate Watch (WA 5.01) after clearing \system
Prerequisit :
Be sure to have latest adb (1.0.32) and fastboot version. Download it from here
Link to know how to enter into fastboot
Under Fastboot
Download boot from here
Code:
- fastboot flash boot bootll.img
Download TWRP recovery from here
Code:
- fastboot flash recovery twrp.img
Go to Recovery and format all twice with TWRP recovery
Flashing back stock recovery :
Download stock recovery from here
Code:
- fastboot flash recovery recoverll.img
Back to stock recovery, format twice
Regenereting system step :
Download rooted AW 5.01 system directory from here
Code:
- fastboot flash system system.img
Go back to stock recovery, Choose apply update from ADB (adb sideload)
Download AW 5.01 update from here
Code:
- adb sideload 149e0c34d0ab10d3e356d6301915dcc04552d9db.signed-lenok-LWX48P-from-KNX01R.149e0c34.zip
Reboot system now. Choose langage, etc.
Nota : At this time, if you don't need root and Chainfire SU (witch is useless at this time) you can go just for flashing TWRP by :
Code:
- adb reboot bootloader
- fastboot flash recovery twrp.img
And that's it.
Or following steps : Rooting back Watch and custom TWRP Recovery support
Download stock rooted AW 5.01 system directory from here
Code:
- adb reboot bootloader
- fastboot flash system system.img
Reboot Watch, autorize adb debug on the watch
Download Chainfire SU 2.40 from here or BETA-SuperSU-v2.42.zip
Note : You can remove Superuser.apk from the zip file into \common recovery which it is not compatible with AW 5.01
Pushing SU to the watch
Code:
- adb push supersu.zip /sdcard/su.zip
Back to Fastmod and flashing TWRP advanced recovery
Code:
- adb reboot bootloader
- fastboot flash recovery twrp.img
Restart watch and go to TWRP recovery, install/flash su.zip from sdcard, reboot
Et Voilà !
Nice write up, I'm not sure doing the adb sideload does anything though. The system image is already patched, it was a backup from my device just rooted. Currently I have busybox working on the device and and working on init.d support so any changes we want to make will survive after reboot.
Sent from my A0001 using XDA Free mobile app
It'ill be nice :good:
HELP
I've done everything to try to get back to AW 5.01 but when I get to the adb sidelload part it says "error: device not found".
It's seem that windows 8 is not detecting my watch. Anyone have any insight on this would be great thanks!
Jay
edit...
Never Mind Got it to Work!
How did you get it to work?
I managed it, too. Turns out I had to reinstall drivers while in sideload mode. You can do it in device manager, select from computer, from list and find ADB composite device.
Hey guys, I accidentaly installed supersu apk on my watch and now I can see it in the menu all the time. How can I remove it from /system/app/SuperSu? Do I have to root first in order to gain rw rights on /system, remove whole SuperSu folder than do a factory reset for example and it won't show up anymore?
hornedfiend said:
Hey guys, I accidentaly installed supersu apk on my watch and now I can see it in the menu all the time. How can I remove it from /system/app/SuperSu? Do I have to root first in order to gain rw rights on /system, remove whole SuperSu folder than do a factory reset for example and it won't show up anymore?
Click to expand...
Click to collapse
simply flash this in twrp > https://hostr.co/3yMSrXUUMD8B and it will remove for you and you will get root also
Android 11, Is there anyway to mount or overlay values in framework-res.apk?
Edit figured it out. This was on LineageOS 18.1. enable root debugging in developer options. (If you dont see it, It's because you have magisk installed. In the future make sure you enable root debugging before installing magisk. It gets hidden. but just fastboot flash boot original boot img. enable it, then fastboot flash boot magisk patched boot.)
1. Create the RRO
adb root
adb remount
adb push /system/product/overlay/[RRO Name]/[RRO Name.apk]
adb reboot
I didn't have to sign or zipalign the file. You can if you want to, I used platform test keys until I realized it wasn't necessary.