Related
This is copied from the Droid2 section and is said to work on the X for those of us that didnt move SU b4 updating to 2.2 or those that lost root for whatever reason.
Cool How to root the Droid 2
All credit goes to Sebastian Krahmer at http://c-skills.blogspot.com/. Please see fit to donate via Paypal to [email protected]
***NOTE: Proceed at your own risk. I and the providers of this code are not responsible for anything you do to your phone!***
Setup:
- Install adb (here) and Motorola drivers for windows(32-bit or 64-bit)
- Download attached archive
- Extract to a directory, I used c:\Droid2Root
- Make sure you have USB degugging enabled
- Change connection to PC Mode
Process:
- Open command prompt
- cd c:/wherever-your-sdk-tools-folder-is
- adb devices (to verify the connection)
- cd c:/Droid2Root
- adb push Superuser.apk /sdcard/Superuser.apk
- adb push su /sdcard/su
- adb push busybox /sdcard/busybox
- adb push rageagainstthecage-arm5.bin /data/local/tmp/rageagainstthecage-arm5.bin
- adb shell
- cd data/local/tmp
- chmod 0755 rageagainstthecage-arm5.bin
- ./rageagainstthecage-arm5.bin
- let the process run until it 'kicks' you out (may take a minute or two)
- cd c:/wherever-your-sdk-tools-folder-is
- adb devices (to verify the connection)
- adb shell (you should now have a # prompt, if not return to ./rage step above)
- mount -o rw,remount -t ext3 /dev/block/mmcblk1p21 /system
- cp /sdcard/Superuser.apk /system/app/Superuser.apk
- cp /sdcard/su /system/bin/su
- cp /sdcard/busybox /system/bin/busybox
- chmod 4755 /system/bin/su
- chmod 4755 /system/bin/busybox
- mount -o ro,remount -t ext3 /dev/block/mmcblk1p21 /system
- exit
- exit
I'm sure there are certain steps that could be streamlined or eliminated, so please feel free to make a suggestion and I'll edit the post.
Additional thanks to @rainabba and AllDroid.org for their excellent Droid X rooting tutorial, which assisted me greatly in this process.
Attached Files
File Type: rar Droid2Root.rar (954.1 KB, 733 views)
Last edited by karnovaran; Yesterday at 01:58 PM.. Reason: Clarity
Reply With Quote
Hello all...
This worked on my DX that I upgraded to 2.2 just fine. The root pw isn't given anywhere in the instructions as it is in the 2.1 manual root steps.
Any thoughts on the root pw so that I can SSH to the device after rooting?
This method worked for me after thru much trial and error I was able to update to Froyo only to discover I lost root. Did not want to roll back to 2.1 and start over. Thanks so much to everyone who came up with root process and to those who discovered it worked on the DX.
I tried intstalling the 64bit drivers (then rebooted) then hooked it up in PC mode and can't seem to get it to show up in the list of attached devices.
Tried uninstalling and reinstalling everything, the one click roots say it can't find my droid X and going through your instructions adb can't find my device ether. I kinda been having a problem with doubletwist where it doesn't recognize my device properly, could that be related?
I don't know why, but after typing ./rageagainstthecage-arm5.bin it showed the text talking about donations, etc went right back to the $ prompt, and never booted me out of shell. I waited 15 minutes at the $ prompt before Ctrl-break'ing out of shell and trying to relogin. noticed adb is repsonding sluggish. Maybe it's still working? Anyone else having this problem?
Edit: I retried the ./rageagainstthecage-arm5.bin command after rebooting the phone and it worked this time. And I'm rooted! Wireless Tether for Root app works perfectly!
Also I notice when I say PC mode the little debugger icon then doesn't show up like it does in USB mode or charge mode. could this be why the device isn't showing up?
Ok so I manage to get everything good up until the point where I should be looking for a # instead of a $ for terminal. I've done the rage and waited till it kicked me out and went back in and got the same result.
The way that I got through my problems is I set the droid x to USB charge only mode (PC mode there was no debugging and every time I plugged it in, it wouldn't take the ADB driver it wanted a MB810 or something driver)
I know I set the permissions right, and it does run (shows up a little message about donating and in a min or so kicks me out, anything else I can try?
Thanks for the help.
mavermc said:
I tried intstalling the 64bit drivers (then rebooted) then hooked it up in PC mode and can't seem to get it to show up in the list of attached devices.
Click to expand...
Click to collapse
You need to turn off USB debugging first time you connect DX to PC and let the drivers install. After the drivers install, turn on USB debugging and let the driver installation complete again. Then go in terminal (also make sure you change directory to where the adb application is) and type in "adb devices". If your device does not show up, change USB connection method to Windows Media Sync mode on DX and try again.
I hope that helps because that is the limit of my knowledge on the subject.
No reboot, battery pull, then reboot = weird!
Okay, so after I rooted my DX, I went to reboot it (powered off then back on) and it got stuck on the M screen. So I pulled the battery, reinserted it, and then powered on again. It rebooted fine. So...why the battery pull?? Anyone??
So i rooted using this method, (finally got it to work, just used it in usb charge mode on a XP machine) Now my phone seems to drop battery like crazy, all I've changed besides the root is install set cpu (and set some profiles to lower the clock with screen off and low battery and hi temp) installed battery life widget and a little white widget that shows what the current clock speed is. oh and wifi teather, any idea why my battery just sucks now? and things like battery info (to show whats using the battery) force closes on me after root, anyone else with these problems?
read-only what? help!!
is it ppossible to do this from the device?
Will this root work on ota froyo upgrade that we will have in a few days?
Sent from my DROIDX using XDA App
Like many have said it works perfectly if you disable the USB Debugging...install all drivers again and then put it in "Charge Mode"
I finally have my phone rooted...Now I know why my Deodex didnt wanna work. Thanks to all for releasing this and ending my headache
Hi all.
Give a try to my version of the instructions. This is kind of like the holy grail of rooting the Droid 2 at the moment. Much clearer! More info! Enjoy!
http://forum.xda-developers.com/showpost.php?p=7865824&postcount=164
dscottjr81 said:
- ./rageagainstthecage-arm5.bin
- let the process run until it 'kicks' you out (may take a minute or two)
- cd c:/wherever-your-sdk-tools-folder-is
- adb devices (to verify the connection)
- adb shell (you should now have a # prompt, if not return to ./rage step above)
Click to expand...
Click to collapse
One thing I found was after it ran and returned to a cursor, I closed the cmd window and relaunched it and had no issues. Before I restarted I did switch to Charge only w/ USB debug active.
It wouldn't work at all for me until I put the contents of the Droid2Root.rar in my /tools folder. The adb commands would not work as soon as I "cd c:/Droid2Root", but the adb commands would work in the /tools folder. So I just put the contents of the Droid2Root.rar in my /tools folder and it worked just fine. O yea I'm on the OTA 2.2 (2.3.15) that came out today. I also did it under "Charge Only" with debugging.
So I take it that the One-Click root will not work withfroyo 2.2 update????
i continuously get the money sign even after it kicks me out from the ./rage step and i kill-server then adb shell.
its still there even after 3 attempts at the ./rage step what should i do? it just wont (#) prompt me
Here's how I hooked my A7 to my PC over USB and successfully used the ADB shell with it.
I hooked up a USB A-A cable first.
Then, on the device I used root explorer to make the following changes to /system/etc/usbotg.sh
#!/system/bin/sh
cat /proc/test_program/serial > /data/data/sn
if [ -f /data/data/com.android.providers.contacts/databases/contacts2.db-journal ]; then
echo "-------------------- Error journal, remove it -------------------"
rm /data/data/com.android.providers.contacts/databases/contacts2.db-journal
fi
sleep 1
# echo on > /sys/devices/platform/tegra-ehci.1/usb2/power/level #disable it to avoid suspend/resume fail # this was already disabled
#echo 10 4b a0 e4 07 00 > /proc/test_program/ecctl # not sure what this was for, had disabled it during testing
#echo on > /sys/devices/platform/tegra-ehci.0/usb1/power/level # not sure what this was for, had disabled it during testing
echo 0 > /proc/test_program/usb # set slave mode (set to 1 for host only mode)
#done
I used root explorer to mount the partition as r/w, and backed up the file, and set the backup as a+x (if i run that file manually, it switches the usb port back to host).
I also installed the android sdk pack, plus the google driver pack addon.
I applied the changes described at tegradeveloper.nvidia.com/tegra/forum/faq-where-can-i-find-usb-drivers to the driver inf file.
I rebooted my android device, and plugged it into my pc. Following the instructions in the above link I manually specified the device type.
The end result?
C:\Program Files (x86)\Android\android-sdk-windows\platform-tools>adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
02804145421f6397 device
C:\Program Files (x86)\Android\android-sdk-windows\platform-tools>
C:\Program Files (x86)\Android\android-sdk-windows\platform-tools>adb shell
# ls
ls
config
misc
cache
acct
sdcard
storage
mnt
d
etc
system
sys
sbin
proc
init_recovery.rc
init.rc
init.goldfish.rc
init
default.prop
data
root
dev
#
I hope someone finds this useful.
This is great! I seriously can't wait to get my A7 in the mail. This will make modding alot easier!!!
A big thank you!
That's great news! Does it charge while plugged in?
Afraid not, but then again I didn't expect it to.
Moved to general as not android development
greenaar
Did you restart elocity every time when you switched host-mode?
I successfully connected my A7 to PC via adb (but notice, when device went sleep it turned off usb too)
And i go back only if i change script and restart
tjc2k4 said:
That's great news! Does it charge while plugged in?
Click to expand...
Click to collapse
Uses 19+ volts to charge. Usb is only 5 volts
did you have anymore definitive success or recommended instructions for enabling adb over usb on the elocity?
i've tried;
echo 0 > /proc/test_program/usb
which did seem to disable hosting/my thumb drive quit detecting, but could never get adb. android never seemed to like the script at all.
thanks for any response.
Didn't the otg_USB apk work for you???
@acid123; i've never seen a otg_usb.apk. the script seemed entirely unsuccessful for me, if thats what you mean, and appears to be based on an older file, as the new script doesn't exactly look like the one posted. i chose to try the scripts line by line mostly w/ errors, but it looks like i'll revisit the script again.
If you want to remove the carrier branded boot and shutdown animations or the default Samsung animations that you see upon startup and shutdown, you can enter these commands via adb shell or in a terminal emulator on your Galaxy Tab. This code renames the files so that they are no longer accessed when the device is started while keeping them from auto-replicating. Deleting or moving the files with root explorer will not work because the files will be replaced almost immediately. You have to be rooted in order to gain the superuser privileges needed to edit the files in /system.
If you aren't already rooted, you can use z4root or superoneclick.
After that, if you choose, you can enter the commands through adb shell or through a terminal emulator available through the market. If you are not familiar with adb, you can get information on it here: basic adb/shell info
If you don't want to be tethered to the computer, you can take the terminal emulator route. I used "Android Terminal Emulator" by Jack Palevich. It is free on the market, but I'm sure that any of the other ones will work just as well.
If you have a Sprint Galaxy Tab and want to remove the Sprint animations/sounds at startup and shutdown, enter the following commands. Be careful, because you are editing /system files.
Code:
su
mount -o remount,rw /dev/mtdblock3 /system
mv /system/media/bootani.qmg /system/media/_bootani.qmg
mv /system/media/video/shutdown/shutdown.qmg /system/media/video/shutdown/_shutdown.qmg
mv /system/media/audio/ui/PowerOff.wav /system/media/audio/ui/_PowerOff.wav
mv /system/etc/PowerOn.snd /system/etc/_PowerOn.snd
mount -o remount,ro /dev/mtdblock3 /system
exit
For those of you with tabs other than the Sprint Tab, you may have to add the line:
Code:
mv /system/etc/PowerOn.wav /system/etc/_PowerOn.wav
This line goes after the command to move "PowerOn.snd"
These commands will leave the standard Samsung bootanimation. If you want to get rid of all bootanimations completely you can enter the following code:
Code:
su
mount -o remount,rw /dev/mtdblock3 /system
mv /system/media/bootani.qmg /system/media/_bootani.qmg
mv /system/media/samsungani.qmg /system/media/_samsungani.qmg
mv /system/media/video/shutdown/shutdown.qmg /system/media/video/shutdown/_shutdown.qmg
mv /system/media/audio/ui/PowerOff.wav /system/media/audio/ui/_PowerOff.wav
mv /system/etc/PowerOn.snd /system/etc/_PowerOn.snd
mount -o remount,ro /dev/mtdblock3 /system
exit
Now open your terminal or adb shell again.
Now enter:
Code:
su
cd /data/local
chmod 777 nobootani.sh
./nobootani.sh
exit
Now restart your tab. You will see that the shutdown animation is gone. When the tab restarts, the carrier/default animations are gone.
thanks
thanks a lot rkmj - I can confirm that this is working on my Sprint CDMA Galaxy Tab. The animations has been removed.
I just got it a couple of days back and I am in the process of removing all the junk from samsung and sprint without flashing a custom ROM cuz seriously there isnt any worth taking the risk.
I have cleaned almost all of them and with this fix my TAB just feels like totally unbranded now.
Next step is to make it faster without a custom ROM, ideas are welcome or maybe a safe list of services I can disable without breaking my tab.
Nice, thanks man
Sent from my GT-P1000 using XDA App
The at&t startup logo and sound is gone with overcome rom, but the t-mobile startup logo is still there.
So what will remove the t-mobile start screen?
I'm pretty sure this will remove the T-Mobile startup. Most of the carrier-branded startup routines are in the same locations. If this doesn't work though, you might check /system/media for a file called "bootanimation.zip" If that fails to produce, check /data/local for the same file. If you have that "bootanimstion.zip" file, you can either swap that bootabimation file for a custom one or get rid of it altogether.
Sent from my Samsung Galaxy Tab
rkmj said:
I'm pretty sure this will remove the T-Mobile startup. Most of the carrier-branded startup routines are in the same locations. If this doesn't work though, you might check /system/media for a file called "bootanimation.zip" If that fails to produce, check /data/local for the same file. If you have that "bootanimstion.zip" file, you can either swap that bootabimation file for a custom one or get rid of it altogether.
Sent from my Samsung Galaxy Tab
Click to expand...
Click to collapse
I have a tmobile galaxy tab, and the bootanimation.zip is just the startup movie that plays. Mine has been replaced with anouther. The white tmobile screen bugs the heck out of me, is not part of my custom boot animation but still shows. So does the samsung galaxy tab black screen.
Can I get rid of these two screens?
Sent from my GT-P1000 using XDA Premium App
There's an app called BAC or Boot Animation Changer that works with my rooted Moto Droid but not with my rooted Sprint Galaxy Tab. Would you have any idea whether after removing the boot animation if it will work? TIA
I'll test and see what results I get; just thought it might be good to have an informed opinion first. And many thanks for the post.
Thanks for this; just wanted to get rid of my carrier branding (Telstra) on my Galaxy Tab. I'm rather happy with the Samsung animation and even the on/off sounds.
good work
works beaut on Telstra 8.9.. give or take file names changes of course but the result is spot on...out with Tesltra crap...
rkmj said:
I
Now restart your tab. You will see that the shutdown animation is gone. When the tab restarts, the carrier/default animations are gone.
Click to expand...
Click to collapse
is that work other devices ? mean note 4 etc? and another cariror like sprint verizon etc?
hello guys. battery of my zf5 is dead. i have dissambled it and get the controller, and i have conected another battery (bigger one, 6000mah) to controller.
now device work, but it using only 2100 mah from battery, because this value is setted in framework-res.apk, and in the charge-full file from /sys/class/power_supply/battery.
now, i have modified value in the framework-res.apk, recompiled it and pushed to device (no problem with this).
now, i have pulled charge-full file from /sys/class/power_supply/battery folder, modified it, but i cannot copy/replace it back to device.
i have root, i have rw permisions to root of device.
i have chmod 777 -R /sys/class/power_supply/battery folder, chmod +x -R /sys/class/power_supply/battery folder. i have try to change owner of /sys/class/power_supply/battery/charge-full file. but no luck, allways i get Failed: operation not permited.
tryed copy/replace from adb shell, from twrp file manager, from twrp terminal. no luck
can please anyone help me?
thx!!
Hello guys and gals,
my wife managed to break her screen on the SM-G900F Model from germany and she got her a new phone. The problem is now that she has some data on the phone she needs (like the google e-mail what she has forgotten the name of) and some other stuff. I want to enable usb debugging over recovery and mirror the screen on my pc (i did that once on my old Galaxy S3 Neo).
I was searching on this forums for a sollution to enable usb debugging over recovery https://forum.xda-developers.com/showthread.php?t=2697523.
I managed to flash the recovery, but adb still does not recognise the phone while in recovery mode. I am running out of options and i really need help of some dev to decompile the kernel, edit the init-rc, and to recompile the kernel, so i could flash it on the phone. I was looking at some guides, but i just don't get it how to do that
Click to expand...
Click to collapse
It would help if someone has some user friendly guide to do that, so i would try that on my own.
I hope there is someone who can help me.
Stock Rom version: G900FXXS1CPLV_G900FDBT1CPJ1_G900FXXU1CPJ1_HOME.tar.md5
Click to expand...
Click to collapse
Hi,
Why not using latest TWRP custom recovery instead of trying old/outdated and not officially supported CWM?
I have no problem with accessing to ADB from latest TWRP.
TomyVk said:
Hello guys and gals,
my wife managed to break her screen on the SM-G900F Model from germany and she got her a new phone. The problem is now that she has some data on the phone she needs (like the google e-mail what she has forgotten the name of) and some other stuff. I want to enable usb debugging over recovery and mirror the screen on my pc (i did that once on my old Galaxy S3 Neo).
I was searching on this forums for a sollution to enable usb debugging over recovery https://forum.xda-developers.com/showthread.php?t=2697523.
It would help if someone has some user friendly guide to do that, so i would try that on my own.
I hope there is someone who can help me.
Click to expand...
Click to collapse
Boot to TWRP recovery
Then enter these commands in a terminal/cmd window on pc
If you're not rooted leave out the su from below - think it should still work
Assuming you have Samsung USB drivers & adb setup on pc
Code:
adb shell
su
mount -o remount,rw /system
cd /
echo "persist.service.adb.enable=1" >> default.prop
echo "persist.service.debuggable=1" >> default.prop
echo "persist.sys.usb.config=mtp,adb" >> default.prop
echo "persist.service.adb.enable=1" >> /system/build.prop
echo "persist.service.debuggable=1" >> /system/build.prop
echo "persist.sys.usb.config=mtp,adb" >> /system/build.prop
This will enable adb but you still may face unauthorized as you get a prompt on phone screen to allow adb & to accept connection - you maybe able to manually send the rsa key but you will have to Google that if you face that problem - it will depend on Android version
ADB should be enabled in latest twrp recovery so pull the build.prop edit it then push it back setting correct permissions
However if you are simply copying files just enter twrp & you will be able to see all your phone files via USB connection on your pc
Obviously with Google email you would need to boot the phone so try the above to enable adb debugging in normal boot
TheFixItMan said:
Boot to TWRP recovery
Then enter these commands in a terminal/cmd window on pc
If you're not rooted leave out the su from below - think it should still work
Assuming you have Samsung USB drivers & adb setup on pc
Code:
adb shell
su
mount -o remount,rw /system
cd /
echo "persist.service.adb.enable=1" >> default.prop
echo "persist.service.debuggable=1" >> default.prop
echo "persist.sys.usb.config=mtp,adb" >> default.prop
echo "persist.service.adb.enable=1" >> /system/build.prop
echo "persist.service.debuggable=1" >> /system/build.prop
echo "persist.sys.usb.config=mtp,adb" >> /system/build.prop
This will enable adb but you still may face unauthorized as you get a prompt on phone screen to allow adb & to accept connection - you maybe able to manually send the rsa key but you will have to Google that if you face that problem - it will depend on Android version
ADB should be enabled in latest twrp recovery so pull the build.prop edit it then push it back setting correct permissions
However if you are simply copying files just enter twrp & you will be able to see all your phone files via USB connection on your pc
Obviously with Google email you would need to boot the phone so try the above to enable adb debugging in normal boot
Click to expand...
Click to collapse
Well, i have flashed the latest twrp recovery twrp-3.2.3-0-klte.img.tar over odin. It flashed without problems.
But the same problem persists, when i boot in to recovery mode adb does not recognise th phone in recovery mode.
When i type adb shell i just get a "error: device not found" from adb
I have installed the newest samsung drivers over Kies3.
TomyVk said:
Well, i have flashed the latest twrp recovery twrp-3.2.3-0-klte.img.tar over odin. It flashed without problems.
But the same problem persists, when i boot in to recovery mode adb does not recognise th phone in recovery mode.
When i type adb shell i just get a "error: device not found" from adb
I have installed the newest samsung drivers over Kies3.
Click to expand...
Click to collapse
How do you know twrp booted if you can't see the screen?
TWRP will have adb support so as long as twrp booted it will work
Once you have flashed twrp in odin you must boot into twrp as soon as the phone restarts for twrp to stick - if you switched the device off or the phone booted normally you will have to reflash twrp - if you can't see the screen that maybe an issue
TheFixItMan said:
How do you know twrp booted if you can't see the screen?
TWRP will have adb support so as long as twrp booted it will work
Once you have flashed twrp in odin you must boot into twrp as soon as the phone restarts for twrp to stick - if you switched the device off or the phone booted normally you will have to reflash twrp - if you can't see the screen that maybe an issue
Click to expand...
Click to collapse
Oh, that might be the problem. What do i have to do after the flashing to boot in to twrp?
The same key combination as for the recovery mode or something else, or do i just disable automatic reboot in odin?
TheFixItMan said:
How do you know twrp booted if you can't see the screen?
TWRP will have adb support so as long as twrp booted it will work
Once you have flashed twrp in odin you must boot into twrp as soon as the phone restarts for twrp to stick - if you switched the device off or the phone booted normally you will have to reflash twrp - if you can't see the screen that maybe an issue
Click to expand...
Click to collapse
TomyVk said:
Oh, that might be the problem. What do i have to do after the flashing to boot in to twrp?
The same key combination as for the recovery mode or something else, or do i just disable automatic reboot in odin?
Click to expand...
Click to collapse
As soon as the device restarts & the Samsung logo appears (that you can't see) hold Vol up home button & power button
Can try disabling auto restart then pull the battery after flash & then hold the button combo to start
TheFixItMan said:
As soon as the device restarts & the Samsung logo appears (that you can't see) hold Vol up home button & power button
Can try disabling auto restart then pull the battery after flash & then hold the button combo to start
Click to expand...
Click to collapse
Thank you, it worked. I will now try to enable the usb debugging
TheFixItMan said:
Boot to TWRP recovery
Then enter these commands in a terminal/cmd window on pc
If you're not rooted leave out the su from below - think it should still work
Assuming you have Samsung USB drivers & adb setup on pc
Code:
adb shell
su
mount -o remount,rw /system
cd /
echo "persist.service.adb.enable=1" >> default.prop
echo "persist.service.debuggable=1" >> default.prop
echo "persist.sys.usb.config=mtp,adb" >> default.prop
echo "persist.service.adb.enable=1" >> /system/build.prop
echo "persist.service.debuggable=1" >> /system/build.prop
echo "persist.sys.usb.config=mtp,adb" >> /system/build.prop
This will enable adb but you still may face unauthorized as you get a prompt on phone screen to allow adb & to accept connection - you maybe able to manually send the rsa key but you will have to Google that if you face that problem - it will depend on Android version
ADB should be enabled in latest twrp recovery so pull the build.prop edit it then push it back setting correct permissions
However if you are simply copying files just enter twrp & you will be able to see all your phone files via USB connection on your pc
Obviously with Google email you would need to boot the phone so try the above to enable adb debugging in normal boot
Click to expand...
Click to collapse
When i try to mount the system partition i just get this:
mount -o remount,rw /system
mount: can't find /system in /proc/mounts
TomyVk said:
When i try to mount the system partition i just get this:
mount -o remount,rw /system
mount: can't find /system in /proc/mounts
Click to expand...
Click to collapse
You might have a problem of when twrp starts it asks you to swipe to allow system modifications but you can't see that
See if are able to do an adb screen cast that allows you to control the screen via adb then you can fully get into twrp
Or see if you can simply pull the build.prop & default.prop to pc & edit it & push it back
TheFixItMan said:
You might have a problem of when twrp starts it asks you to swipe to allow system modifications but you can't see that
See if are able to do an adb screen cast that allows you to control the screen via adb then you can fully get into twrp
Or see if you can simply pull the build.prop & default.prop to pc & edit it & push it back
Click to expand...
Click to collapse
When i type ls in the shell i get this
Code:
ls
boot init.rc sdcard
cache init.recovery.hlthchrg.rc seapp_contexts
charger init.recovery.qcom.rc selinux_version
data init.recovery.service.rc sepolicy
default.prop init.recovery.usb.rc service_contexts
dev license sideload
efs modem sys
etc oem system
external_sd proc tmp
file_contexts property_contexts twres
file_contexts.bak recovery ueventd.qcom.rc
firmware res ueventd.rc
fstab.qcom root usbstorage
init sbin vendor
The system folder is empty tho. I have pulled the default.prop to my pc and pushed it back, created the build.prop and pushed it in to the system folder.
After i did that i typed exit and then adb reboot. Still no usb debugging. I checked the files again and the default.prop was back to the original, and the build.prop from the system folder was gone after the reboot. I don't know what i am doing wrong. I even have root access....
TomyVk said:
When i type ls in the shell i get this
Code:
ls
boot init.rc sdcard
cache init.recovery.hlthchrg.rc seapp_contexts
charger init.recovery.qcom.rc selinux_version
data init.recovery.service.rc sepolicy
default.prop init.recovery.usb.rc service_contexts
dev license sideload
efs modem sys
etc oem system
external_sd proc tmp
file_contexts property_contexts twres
file_contexts.bak recovery ueventd.qcom.rc
firmware res ueventd.rc
fstab.qcom root usbstorage
init sbin vendor
The system folder is empty tho. I have pulled the default.prop to my pc and pushed it back, created the build.prop and pushed it in to the system folder.
After i did that i typed exit and then adb reboot. Still no usb debugging. I checked the files again and the default.prop was back to the original, and the build.prop from the system folder was gone after the reboot. I don't know what i am doing wrong. I even have root access....
Click to expand...
Click to collapse
System isn't mounted which is why you can't access it - you need to swipe to enable system modification when you first start twrp which you can't see hence I said see if are able to control screen from pc
Make sure you set the correct permissions for the file - 644 or rw-r-r
TheFixItMan said:
System isn't mounted which is why you can't access it - you need to swipe to enable system modification when you first start twrp which you can't see hence I said see if are able to control screen from pc
Make sure you set the correct permissions for the file - 644 or rw-r-r
Click to expand...
Click to collapse
File permissions are correct, i have checked them as soon i saw that it wont work.
i have tried to mirror the screen over adb with
https://www.xda-developers.com/scrcpy-control-android-on-pc/
http://marian.schedenig.name/2014/07/03/remote-control-your-android-phone-through-adb/
and i was checking on google arround, nothing works. It also seems like that the touch screen is broken...
Anyone knows maybe annother option to mount the system?
TomyVk said:
File permissions are correct, i have checked them as soon i saw that it wont work.
i have tried to mirror the screen over adb with
https://www.xda-developers.com/scrcpy-control-android-on-pc/
http://marian.schedenig.name/2014/07/03/remote-control-your-android-phone-through-adb/
and i was checking on google arround, nothing works. It also seems like that the touch screen is broken...
Anyone knows maybe annother option to mount the system?
Click to expand...
Click to collapse
No other than the commands I've given you
TheFixItMan said:
No other than the commands I've given you
Click to expand...
Click to collapse
Means the only chance would be to pull a rom and edit it so that adb is enabled and flash it on the device....
Well, i think i got a new hobby xD