Had a previously rooted X2 that was upgraded to 2.3.4 OTA and lost root privileges.
I downloaded zdooder's adaptation of psouza4's Do-All One Click script for rooting at rootzwiki.com /topic/3216-rootunroot-droid-3-root-instructions-one-click-added-for-windows-linux-osx/page__p__74595#entry74595
Here is how I did it (your results may be catastrophic, so try this at your own risk):
1. Download the script from the link above and extract to a folder
2. Set USB Debugging on in your phone, attached my phone to the Linux box via the USB cable, and set the USB connection to PC Mode
3. Started a terminal and go to the folder where the script files are located:
./run_to_root_your_droid3.sh
4. The phone rebooted three times -- unlocked the phone after each reboot
Since I had previously been rooted, I needed to delete previous versions of Superuser:
5. Still in the command prompt --
./adb.linux
6. Entered the following commands:
mount -o remount,rw /dev/block/system /system
rm /system/bin/su
rm /system/xbin/su
exit
7. Ran the script again:
./run_to_root_your_droid3.sh
8. The phone rebooted three times -- unlocked the phone after each reboot
VICTORY!
Chris
iggyst00ge said:
Had a previously rooted X2 that was upgraded to 2.3.4 OTA and lost root privileges.
I downloaded zdooder's adaptation of psouza4's Do-All One Click script for rooting at rootzwiki.com /topic/3216-rootunroot-droid-3-root-instructions-one-click-added-for-windows-linux-osx/page__p__74595#entry74595
Here is how I did it (your results may be catastrophic, so try this at your own risk):
1. Download the script from the link above and extract to a folder
2. Set USB Debugging on in your phone, attached my phone to the Linux box via the USB cable, and set the USB connection to PC Mode
3. Started a terminal and go to the folder where the script files are located:
./run_to_root_your_droid3.sh
4. The phone rebooted three times -- unlocked the phone after each reboot
Since I had previously been rooted, I needed to delete previous versions of Superuser:
5. Still in the command prompt --
./adb.linux
6. Entered the following commands:
mount -o remount,rw /dev/block/system /system
rm /system/bin/su
rm /system/xbin/su
exit
7. Ran the script again:
./run_to_root_your_droid3.sh
8. The phone rebooted three times -- unlocked the phone after each reboot
VICTORY!
Chris
Click to expand...
Click to collapse
i used that method and the phone stays rooted after reboots.
Was this a problem in the past or something? I thought I saw another thread somewhere saying something about rooting in Linux also. The first time I ever rooted my phone was on Linux and I had no problems.
Related
I am running bamf 1.6.3 remix.. I also am using Handcent sms.. I have synced and redownloaded handcent.. No matter how many times I try the sync won't catch.. The contact images remain little androids.
I Heard of a solution and tried to figure through it..
It appears the ROM Manager fix permissions script messed up the permissions on the thumbnails in the contacts folder. The files were mistakenly permissioned as 771 which meant the jpg thumbnail files were unreadable.
This is what I did to fix it:
1. Boot into clockworkmod recovery
2. Go into the mount/umount section
3. mount /system
4. mount /data
5. Connect usb data cable to computer from phone (I use linux so I don't need anything special in the way of drivers)
6. adb shell
7. mount /datadata
8. The above step may take a few seconds to mount
9. cd /datadata/com.android.providers.contacts
10. chmod og+rx *
11. cd files
12. chmod 664 *.jpg
13. cd /
14. umount /datadata
15. umount /data
16. exit
17. Reboot your phone
I ran into a problem at step 6...
I tried to access the adb shell from the command prompt on the computer I rooted my phone through..
When i typed adb shell into my prompt It could not recognize the device or the command.
-- Am I doing something wrong?? Is there Another solution? I love all the help everyone in forums give, it keeps a community running. I am just such a noob, one word lines never do me any good. A little explanation is GREATLY appreciated.
THANKS ALL.
Ok first things first : If you installed some launcher and your touch screen is not responding and you dont have USB debugging enabled then the only way to fix that is to install the original firmware, dload from here : http://www.androidtablets.net/forum...huawei-ideos-s7-slim-official-firmware-4.html check post 35 for the one i used
If you do have debugging enabled the download Superoneclick from below.
The super one click can aslo root the S7 slim and it has adb installed. Unxip it somewhere and go into the \adb folder. Open command prompt from there and run
Adb devices
If it doesnt show your device the either the debugging is not enabled or the right driver is not loaded. (Menu, Settings, Applications, Development, USB Debugging (Yes))
type adb shell
cd\data\app
rm *launcher*.apk
exit
adb reboot
This will remove the launchers thats faulty and touch screen will work again.
If you guys find a clockworkmod that works then leme know here cause i loaded the wrong one and its messed up.
Use psneuter to root and use the adb in the zip for the above
Cia
How to flash Recovery
Reserved for now
Use other Launchers
ADB remount
adb push c:\bluetooth_power.sh /system/etc/
unzip attached file to c:\
Swapping sdcard and sdcard2 around
adb remount
adb push vold.fstab /system/etc/vold.fstab
if you get permission denied error when doing adb remount then try the following instead :
adb push vold.fstab /sdcard/vold.fstab
adb shell
su
mount -o remount rw /system
cp /sdcard/vold.fstab /system/etc/vold.fstab
mount -o remount ro /system
exit
exit
reboot
Copy attached file into ur adb directory (and unzip it has the modified and original file in the zip) and do the above
Grumps said:
adb remount
adb push vold.fstab /system/etc/vold.fstab
if you get permission denied error when doing adb remount then try the following instead :
adb push vold.fstab /sdcard/vold.fstab
adb shell
su
mount -o remount rw /system
cp /sdcard/vold.fstab /system/etc/vold.fstab
mount -o remount ro /system
exit
exit
reboot
Copy attached file into ur adb directory (and unzip it has the modified and original file in the zip) and do the above
Click to expand...
Click to collapse
this works great - - i had a problem where i have not been able to recover my internal SD card - tried everything - even back to original eclair and all - now i just use the external sd (16gb) for everything. No problems with camera recognizing sd card or programs not downloading, etc, etc....
I'll still try to maybe swap out the internal card, or try to get it functional again somehow, but in the meantime, the S7 if again functional.
Rom
Im currently using this rom an dit works perfectly : http://www.androidtablets.net/forum...ical/15812-rom-tri_zet-ideos_s7-slim-mod.html
Only problem i had was updating google maps so i just loaded the new version via .apk manually
O yes If you load that rom and it comes on the first time the screen might not respond (stuck on lockscreen) but its busy loading software in the background. Mine came up on the lock screen saying connect charger although the battery wasnt low so i plugged the charge cable in. It then rebooted after a while and the touch screen is working perfectly.
http://forum.xda-developers.com/showthread.php?t=942166
Grumps said:
Im currently using this rom an dit works perfectly : http://www.androidtablets.net/forum...ical/15812-rom-tri_zet-ideos_s7-slim-mod.html
Only problem i had was updating google maps so i just loaded the new version via .apk manually
O yes If you load that rom and it comes on the first time the screen might not respond (stuck on lockscreen) but its busy loading software in the background. Mine came up on the lock screen saying connect charger although the battery wasnt low so i plugged the charge cable in. It then rebooted after a while and the touch screen is working perfectly.
http://forum.xda-developers.com/showthread.php?t=942166
Click to expand...
Click to collapse
I just got my Slim S7 yesterday, hated the launcher so I replaced it not thinking it would cause such a problem... long story short I tried installing the rom you linked hoping it would fix it(tried everything else) and the touch screen still is unresponsive and USB debugging is now disabled. Any ideas?
phxtravis said:
I just got my Slim S7 yesterday, hated the launcher so I replaced it not thinking it would cause such a problem... long story short I tried installing the rom you linked hoping it would fix it(tried everything else) and the touch screen still is unresponsive and USB debugging is now disabled. Any ideas?
Click to expand...
Click to collapse
well I finally got it working. I ended up doing multiple battery pulls and installed the geeksu recovery, and that's all I did. I'm up and running on that rom. Only thing is thatbi somehow lost root, but that was no biggy.
Hi,
Did a search and someone said they were able to root with thecubed method on Mac via Terminal, but I've had no luck so far. Are there any other options for us Mac users?
Thanks
BTW I did see some instructions but it only applies to Verizon. I have the international version D802.
Any help would be greatly appreciated.
use virtual machine and use windows?
I haven't found any easy way to do it, other that running bootcamp and windows on the mac..
You can do it via adb just fine on osx (I'm on snow leopard). You can check which commands to run by opening the Windows script as a text document. It's easy to follow what's going on and has sections for each device
xdabbeb said:
You can do it via adb just fine on osx (I'm on snow leopard). You can check which commands to run by opening the Windows script as a text document. It's easy to follow what's going on and has sections for each device
Click to expand...
Click to collapse
I opened root.bat as a text file but as far as how to input the commands I'm not sure what to do as it seems to differs from the video. Sorry I'm not that familiar working with Terminal.
If you could help out that would be great.
Thanks
xdabbeb said:
You can do it via adb just fine on osx (I'm on snow leopard). You can check which commands to run by opening the Windows script as a text document. It's easy to follow what's going on and has sections for each device
Click to expand...
Click to collapse
Ahhhhh! You know Mavericks is free, right? UPGRADE THAT THING!
On another note... same issue w/ me. I ended up rooting it via my PC, but after that you can use Android File Transfer to manage files and load roms and stuff via OSX.
sell ur POS apple and get a pc...?
digitard said:
Ahhhhh! You know Mavericks is free, right? UPGRADE THAT THING!
On another note... same issue w/ me. I ended up rooting it via my PC, but after that you can use Android File Transfer to manage files and load roms and stuff via OSX.
Click to expand...
Click to collapse
Ha! I haven't upgraded because I still feel snow leopard is the best. I don't like how they've integrated so much ios in the last two, and SL is lean/efficient.
If I have some time I'll write down the commands in a reply. Do you have adb already set up?
xdabbeb said:
Ha! I haven't upgraded because I still feel snow leopard is the best. I don't like how they've integrated so much ios in the last two, and SL is lean/efficient.
If I have some time I'll write down the commands in a reply. Do you have adb already set up?
Click to expand...
Click to collapse
Yes already have adb set up. Thanks for this. Really appreciate it.
No problem. What version of the G2 do you have?
---------- Post added at 11:49 PM ---------- Previous post was at 11:48 PM ----------
Ignore that, I just saw you mentioned the international version
OK, here you go:
1) Go here here and here and thank them both for their work...and read their disclaimers about breaking your phone. The same applies here.
2) Download the attached archive and extract the contents into whatever folder you want...for the purposes of this I'll assume you did so to a directory called ~/D802_OSXroot. If you chose a different directory, modify the steps below accordingly. The archive I attached only contains the appropriate file for the international (D802) LG G2, and I used Chainfire's SuperSU instead of the older ChainsDD su binary and apk. While you're at it, go here and thank him.
3) Make sure USB Debugging is enabled on your phone in Settings>Developer Options
4) Connect your phone via usb cable. You'll get the popup asking what type of connection on your phone. Select Internet connection and then Ethernet when asked. You should see the debugging icon in the status bar of your phone
5) Open terminal on your mac
6) To verify that you are properly connected run the following command:
Code:
adb shell "ls -a /"
you should see the contents of the root of your phone...inlcuding a number of init files. If you do, proceed. If you don't, you have an adb/connection problem.
7) Execute the following in the terminal window to go to the directory where the archive has been extracted on your mac:
Code:
cd ~/D802_OSXroot
8) Execute the following to push the loki exploit file to your phone
Code:
adb push ./g2_security /sdcard/g2_security
9) Unplug your usb cable from the phone
10) On your phone go to Settings>Developer Options and disable USB Debugging
11) Re-enable USB Debugging
12) Plug in your USB cable (follow step 4)
13) Verify adb connectivity (follow step 6)
14) Go back to your terminal window, make sure you are still in the same directory with the files from the archive and execute the following commands in order:
Code:
adb shell "mount -o remount,rw /system"
Code:
adb push ./su /system/xbin/su
Code:
adb shell "chown 0.0 /system/xbin/su;chmod 06755 /system/xbin/su;sync;mount -o remount,ro /system"
Code:
adb install superuser.apk
15) Launch the SuperSU app on your phone. It will likely prompt you to update the su binary...let it do so and then reboot your phone. You should be rooted now.
Good luck!
xdabbeb said:
OK, here you go:
1) Go here here and here and thank them both for their work...and read their disclaimers about breaking your phone. The same applies here.
2) Download the attached archive and extract the contents into whatever folder you want...for the purposes of this I'll assume you did so to a directory called ~/D802_OSXroot. If you chose a different directory, modify the steps below accordingly. The archive I attached only contains the appropriate file for the international (D802) LG G2, and I used Chainfire's SuperSU instead of the older ChainsDD su binary and apk. While you're at it, go here and thank him.
3) Make sure USB Debugging is enabled on your phone in Settings>Developer Options
4) Connect your phone via usb cable. You'll get the popup asking what type of connection on your phone. Select Internet connection and then Ethernet when asked. You should see the debugging icon in the status bar of your phone
5) Open terminal on your mac
6) To verify that you are properly connected run the following command:
Code:
adb shell "ls -a /"
you should see the contents of the root of your phone...inlcuding a number of init files. If you do, proceed. If you don't, you have an adb/connection problem.
7) Execute the following in the terminal window to go to the directory where the archive has been extracted on your mac:
Code:
cd ~/D802_OSXroot
8) Execute the following to push the loki exploit file to your phone
Code:
adb push ./g2_security /sdcard/g2_security
9) Unplug your usb cable from the phone
10) On your phone go to Settings>Developer Options and disable USB Debugging
11) Re-enable USB Debugging
12) Plug in your USB cable (follow step 4)
13) Verify adb connectivity (follow step 6)
14) Go back to your terminal window, make sure you are still in the same directory with the files from the archive and execute the following commands in order:
Code:
adb shell "mount -o remount,rw /system"
Code:
adb push ./su /system/xbin/su
Code:
adb shell "chown 0.0 /system/xbin/su;chmod 06755 /system/xbin/su;sync;mount -o remount,ro /system"
Code:
adb install superuser.apk
15) Launch the SuperSU app on your phone. It will likely prompt you to update the su binary...let it do so and then reboot your phone. You should be rooted now.
Good luck!
Click to expand...
Click to collapse
Has anyone tried this method?
Sent from my LG-D802 using Tapatalk
xdabbeb said:
OK, here you go:
1) Go here here and here and thank them both for their work...and read their disclaimers about breaking your phone. The same applies here.
2) Download the attached archive and extract the contents into whatever folder you want...for the purposes of this I'll assume you did so to a directory called ~/D802_OSXroot. If you chose a different directory, modify the steps below accordingly. The archive I attached only contains the appropriate file for the international (D802) LG G2, and I used Chainfire's SuperSU instead of the older ChainsDD su binary and apk. While you're at it, go here and thank him.
3) Make sure USB Debugging is enabled on your phone in Settings>Developer Options
4) Connect your phone via usb cable. You'll get the popup asking what type of connection on your phone. Select Internet connection and then Ethernet when asked. You should see the debugging icon in the status bar of your phone
5) Open terminal on your mac
6) To verify that you are properly connected run the following command:
Code:
adb shell "ls -a /"
you should see the contents of the root of your phone...inlcuding a number of init files. If you do, proceed. If you don't, you have an adb/connection problem.
7) Execute the following in the terminal window to go to the directory where the archive has been extracted on your mac:
Code:
cd ~/D802_OSXroot
8) Execute the following to push the loki exploit file to your phone
Code:
adb push ./g2_security /sdcard/g2_security
9) Unplug your usb cable from the phone
10) On your phone go to Settings>Developer Options and disable USB Debugging
11) Re-enable USB Debugging
12) Plug in your USB cable (follow step 4)
13) Verify adb connectivity (follow step 6)
14) Go back to your terminal window, make sure you are still in the same directory with the files from the archive and execute the following commands in order:
Code:
adb shell "mount -o remount,rw /system"
Code:
adb push ./su /system/xbin/su
Code:
adb shell "chown 0.0 /system/xbin/su;chmod 06755 /system/xbin/su;sync;mount -o remount,ro /system"
Code:
adb install superuser.apk
15) Launch the SuperSU app on your phone. It will likely prompt you to update the su binary...let it do so and then reboot your phone. You should be rooted now.
Good luck!
Click to expand...
Click to collapse
Thanks for this. I'm having an issue at the first step. I have tested adb when I downloaded the SDK and if I direct the command ./adb devices to that specific folder it can read my phone, but just going into terminal and entering adb shell "ls -a /" al I get is -bash: adb: command not found
Also when I connect my phone to the mac I get options on the G2 but none are internet then ethernet. I get: Charge Phone, Media Sync, Tethering, LG Software, Send Images. The Mac does not ask me what connection I want.
ck37 said:
Thanks for this. I'm having an issue at the first step. I have tested adb when I downloaded the SDK and if I direct the command ./adb devices to that specific folder it can read my phone, but just going into terminal and entering adb shell "ls -a /" al I get is -bash: adb: command not found
Also when I connect my phone to the mac I get options on the G2 but none are internet then ethernet. I get: Charge Phone, Media Sync, Tethering, LG Software, Send Images. The Mac does not ask me what connection I want.
Click to expand...
Click to collapse
It sounds like the first issue may just be due to you not having adb set up properly. If you execute "echo $PATH" in terminal and don't see the android/tools and android/platform-tools directories there, that's the problem. You can either set your path variable to include those directories or just edit the commands I listed accordingly.
The second issue may be due to a difference in the D802 rom vs the VS980. The important thing is that USB Debugging is enabled and that you can access your phone via adb. The 802 may not prompt you in the same way, but if you fix your adb setup the commands will work the same. The rooting method listed (which is the same as thecubed method) is predicated on that working properly.
xdabbeb said:
It sounds like the first issue may just be due to you not having adb set up properly. If you execute "echo $PATH" in terminal and don't see the android/tools and android/platform-tools directories there, that's the problem. You can either set your path variable to include those directories or just edit the commands I listed accordingly.
The second issue may be due to a difference in the D802 rom vs the VS980. The important thing is that USB Debugging is enabled and that you can access your phone via adb. The 802 may not prompt you in the same way, but if you fix your adb setup the commands will work the same. The rooting method listed (which is the same as thecubed method) is predicated on that working properly.
Click to expand...
Click to collapse
I think I figured it out. What I did was transfer the ADB icon from my SDK folder into this one. From there I was able to get access to adb inside the D802 folder. I did have to enter the ./adb as opposed to adb though.
As for the LG I selected tethering as that seemed to be the option similar to the internet/ ethernet choice you mentioned.
All other commands worked accordingly.
Binaries updated for SuperUser as well. At this point how do I get into recovery to upload ROMS etc?
ck37 said:
I think I figured it out. What I did was transfer the ADB icon from my SDK folder into this one. From there I was able to get access to adb inside the D802 folder. I did have to enter the ./adb as opposed to adb though.
As for the LG I selected tethering as that seemed to be the option similar to the internet/ ethernet choice you mentioned.
All other commands worked accordingly.
Binaries updated for SuperUser as well. At this point how do I get into recovery to upload ROMS etc?
Click to expand...
Click to collapse
What I did was installed flashify from the market. This app allows you to backup and then flash a new recovery. Make sure you dl the right one for your device!
Sent from my LG-VS980 using Tapatalk
So I've been tinkering around with CM12.1 on this watch for a while (since I switched my phone from the Samsung Galaxy Note 4 to the Xiaomi Mi Max) and yesterday decided to give Android Wear another try (note: I had the LG G Watch back in the really early Android Wear days) and there have been quite a few tweaks that I decided to apply so will share them all here as I remember them.
Android Wear:
Gaining root:
Since we can not use systemless SuperSU (because we can't edit the kernel on the go) like the other watches we need to use a system only root method so I will share how to do that:
You can do this either manually by creating a .supersu containing "SYSTEMLESS=false" file in /system/ before flashing Wear SuperSU or just flash the zip from here before the SuperSU Wear zip: https://forum.xda-developers.com/android/software-hacking/root-disabler-t3370794
Also here is the latest SuperSU Wear zip file: https://drive.google.com/file/d/0B3zB2zRyWlLBNmhwSmNBUEp1SVU/view
Note: you will have a Busybox app installed when you boot AW, you need to connect to Wi-Fi to be able to use it, otherwise it will crash.
Note 2: If you are connected to the phone via Bluetooth the Wi-Fi will automatically disconnect but you can disable this behavior in Developer Options on the watch.
Disabling touch to wake:
This was really annoying for me, I only want the device to wake by pressing the button not when I tilt the watch or touch the screen since that means the watch will be waking up uselessly a lot, tilt to wake can be disabled from the Android Wear app on the phone but for disabling touch to wake you need to edit some system files.
Note: this requires either having root or booting into TWRP and being connected to a PC using either Bluetooth ADB or the watch with the cradle and an USB cable.
AW+root method:
With the watch connected to the computer using either ADB over Bluetooth or the USB cable do the following in a shell:
Code:
adb pull /system/usr/idc/sec_touchscreen.idc
Now you will get the sec_touchscreen.idc file on your PC, open it using Notepad++/gedit/some other Linux EOF format compatible text editor (NOT NORMAL NOTEPAD OR ANY MICROSOFT OFFICE APP!!!!)
The last line should look like:
Code:
touch.wake=1
Just delete that line or set it to 0 and save the file.
Now back to the shell:
Code:
adb shell "mount -o remount,rw /system"
Code:
adb push sec_touchscreen.idc /system/usr/idc/
Code:
adb reboot
Done, now touching the screen will no longer wake up the device.
TWRP method:
Boot the watch in TWRP and connect it to the PC using the cradle and an USB cable then do these commands in a shell:
Code:
adb shell "twrp mount system"
Code:
adb pull /system/usr/idc/sec_touchscreen.idc
Now you will get the sec_touchscreen.idc file on your PC, open it using Notepad++/gedit/some other Linux EOF format compatible text editor (NOT NORMAL NOTEPAD OR ANY MICROSOFT OFFICE APP!!!!)
The last line should look like:
Code:
touch.wake=1
Just delete that line or set it to 0 and save the file.
Now back to the shell:
Code:
adb push sec_touchscreen.idc /system/usr/idc/
Code:
adb reboot
Done, now touching the screen will no longer wake up the device.
I am not sure if this is a problem with AW or the AW kernel with TWRP or it was just me but TWRP didn't display properly for me after I switched from CM12.1 to AW (it would only display till I clicked something then screen turns off) so I will post how to flash the zip files without being able to see TWRP:
You will need to be connected to a computer that has ADB setup for this.
The one thing you need to actually do on TWRP on the watch is select the "never ask again" and swipe to allow system modifications on the first run of TWRP. Note that after you click to tick the "never ask again" check box the screen will already go black so remember the layout so that you'll be able to swipe the slider.
Now you will open a shell on the PC and "adb shell" to the watch that is connected with an USB cable and the charging cradle.
Now you are in the TWRP shell so do these commands:
Code:
twrp mount system
Code:
twrp install /sdcard/disable_systemless_root.zip
Code:
twrp install /sdcard/SuperSU-2.78-wear.zip
Code:
twrp wipe cache
Code:
twrp wipe dalvik
Code:
reboot
NOTE: This assumes that you have put the zips from the first post in the internal storage of the device for which /sdcard/ is a mount point.
Will post more stuff soon, just wanted to post the tutorial on how to root AW for now, I'll be leaving home soon so I'll be back to post the rest of the stuff later today.
As a secondary note right now I am trying to port some AW 2.0 apps to work on 1.5 but we'll see how that goes, don't get your hopes up.
When i try push file adb say: read only file system
I write this and now it's ok:
adb shell
su
mount -o rw,remount /dev/block/mmcblk0p25 /system
exit
adb push sec_touchscreen.idc /system/usr/idc/
Thesebax4 said:
When i try push file adb say: read only file system
I write this and now it's ok:
adb shell
su
mount -o rw,remount /dev/block/mmcblk0p25 /system
exit
adb push sec_touchscreen.idc /system/usr/idc/
Click to expand...
Click to collapse
Why did you add that /dev/block/mmcblk0p25?
The right command is:
Code:
mount - o remount,rw /system
Also did you first root your device?
I never needed to add anything, that's why I'm asking?
I don't have root. TWRP ask me to make system writable, i try to swipe (yes) but screen goes black... Maybe this is fault. I search this in google https://forum.xda-developers.com/showthread.php?t=1749657 (second post) I change the partition from mmcblk0p1 to mmcblk0p25 because gear s have /system under mmcblk0p25. And this working for me.
Thesebax4 said:
I don't have root. TWRP ask me to make system writable, i try to swipe (yes) but screen goes black... Maybe this is fault. I search this in google https://forum.xda-developers.com/showthread.php?t=1749657 (second post) I change the partition from mmcblk0p1 to mmcblk0p25 because gear s have /system under mmcblk0p25. And this working for me.
Click to expand...
Click to collapse
Ah, I was thinking you were in AW not TWRP, as I said in the 2nd post you have to swipe on the black screen, you will feel a vibration, for me both methods work properly without the extra mounting.
I've installed recovery and Android wear os, but due to Heavy battery drainage and no phone audio I'm trying to Go back to stock.
I've tried flashing Stock firmware Using Odin but after flashing when the watch boot up, after Samsung gear s logo screen Goes blank and after few seconds Samsung animation comes Up but doesn't complete the animation anf Goes blank again.
I need help to fix this.
Thanks in advance
Here is how I succeeded to enable USB debugging (also adb and remote view) on Samsung Galaxy Note 4 with broken screen.
1. Following the DeathDrifterz's advice I was able to set the device in recovery mode with ROOT access and adb :
DeathDrifterz said:
So, I have a Galaxy Note 4, broken screen, broken digitizer. Do not have access too an MHL cable or Mouse to hook up to TV. The phone has a password and usb debugging disabled, so kies and the computer won't recognize it. Not even when in download mode. I did flash CWM rcovery to the phone, but this still wouldn't allow me to see the phone in recovery mode. What did work was I downloaded the trial version of Wundershare Dr. Fone, booted phone into download mode, let the program run and start searching for files. Stopped the program. Unplugged the phone. Exited Dr Fone. Opened cmd in the platform-tools folder of the SDK platform. At this point, I was now able to see the phone, in recovery, listed under ADB Devices.
So Dr Fone took the phone from download mode (vol down + home + power, then press vol up after vibrate) to recovery mode once it started finding files. Disconnect the phone from the PC, exit Dr Fone and reconnect the phone to the PC. It will still be in recovery mode. Open cmd prompt in the platform-tools folder. adb devices shows phone in recovery, used adb pull /sdcard/ and it worked like a charm. All files on the phone have now been downloaded.
Broken screen, no digitizer, password locked, USB debugging disabled, and it was free. Took 5 minutes once Dr Fone was downloaded (will take longer if you don't have the sdk tools.)
Hope it helps.
Click to expand...
Click to collapse
2. In other forum I found tutorial how to enable USB debugging from recovery with root access :
Connect the device to Mac or PC in recovery mode. (I had to map the process in my mind as the screen was broken).
Now open terminal/CMD in computer and go to platform-tools/. type and enter ./adb devices to check if the device is connected in recovery mode.
To mount the respective directories, type:
Code:
./adb shell mount data
./adb shell mount system
Get the persist.sys.usb.config file in your system using:
Code:
./adb pull /data/property/persist.sys.usb.config /Your directory
Now open that file in a texteditor and edit it to mtp,adb and save.
Now push the file back in the device:
Code:
./adb push /your-directory/persist.sys.usb.config /data/property
Get the build.prop file:
Code:
./adb pull /system/build.prop /your-directory
Add these lines:
Code:
persist.service.adb.enable=1
persist.service.debuggable=1
persist.sys.usb.config=mtp,adb
Push build.prop back into the device:
Code:
./adb push /your-dir/build.prop /system/
This way you enabled USB debugging on your device. But you still can't connect. Why? Because it asks for RSA verification. If you could view your display then you could easily tap on YES to authorize the device.
3. Skipping RSA verification :
The ADB keys (after authorization) are saved in /data/misc/adb/adb_keys, so I have one Samsung Galaxy S3 with working display which already authorized my PC.
So I got the adb_keys file from it. I connected the Samsung Galaxy S3 to my PC and use :
Code:
./adb pull /data/misc/adb/adb_keys
Then reconnected the Note 4 and pushed the file in it:
Code:
./adb push /your-dir/adb_keys /data/misc/adb/adb_keys
4. Reboot! And Voila: the devices boots normally and adb connects without asking for verification.
After that I used Vysor chrome extension and Vysor apk to view the device screen and act with the device.
I installed the apk with :
Code:
./adb install apk_name.apk
Sources :
https://forum.xda-developers.com/showthread.php?t=2395047
https://android.stackexchange.com/questions/120394/can-i-enable-usb-debugging-using-adb
https://www.vysor.io/
It works! With the first method.
I have Samsung Galaxy s5, lineage os 14.1,
After my screen broke, I couldn't see my device through adb devices, no matter what driver I have installed - and believe me I've tried all the methods.
Then I've installed CWM recovery, adb recognized it in devices but I wasn't able to pull sdcard with adb pull command in Windows 7. I got access denied.
Then I saw this post and I got access to sdcard!
Works on OnePlus One with Lineage 14.1
Works like a charm on my OnePlus One with lineage 14.1
Just want to mention that if you have problems mounting /data and/or /system
I got help from this post: https://forum.xda-developers.com/galaxy-s2/help/mount-adb-t1107545
Basically, the dirty solution I found with help from kaukassus post was:
1.
Code:
adb mount
- to view name of available mounts and identify /system and /data
2.
Code:
adb shell mount -o rw,remount -t yaffs2 /dev/block/[U]mmcblk0p28[/U]
underlined is the part that is different
- to mount the data folder. Do the same for system. Then I just followed the steps from this tutorial.
The part with the RSA verification I resolved with a little help from https://gist.github.com/varhub/7b9555cdd1e5ad785ffde2300fcfd0bd
Enable ADB (2/2): RSA verification
For the RSA verification that you asked to bypass, I don't know whether it would work in your device, but it worked in my little experiment. In Lollipop, the ADB keys (after authorization) are saved in /data/misc/adb/adb_keys. Your private key is saved in computer. In Linux the directory location is $HOME/.android/. On Windows that usually translates to %USERPROFILE%.android, but keys might end up in C:\Windows\System32\config\systemprofile.android in some cases.
adb push ~/.android/adbkey.pub /data/misc/adb/adb_keys
Click to expand...
Click to collapse
Thanks for post
Worked top to bottom, on my Galaxy S5 6.0.1 (ALEXNDR ROM)!
Used step .2, .3 and oledolez tips aswell.
Got the screen cracked and black, went crazy because I had the SD card encrypted and couldn't get the stuff outta there...
Thanks a lot!
Hugo
GS5 CWM Stock ROM
Hello ! I broke my gs5(sm-g900f)'s screen and now it is constantly black. I tried everything on the thread and my device is always shown as unauthorized in vysor or when checking in ADB with /adb devices. This means I have succeeded to enable USB Debugging through ADB, however I must be having problems with the RSA key. Any help would be appreciated!!
Thanks in advance !
Dan
P.S The phone was completely stock when I broke it and I blindly installed cwm-6.0.4.7 and CF-auto-root with odin, so maybe there is a problem with that ?
what if the partition is encrypted? How I would enter the boot password with a broken screen?
xaviermchot said:
what if the partition is encrypted? How I would enter the boot password with a broken screen?
Click to expand...
Click to collapse
I had the same problem and fixed it in TWRP doing this command:
Note: Use this command only if your /data/ partition has the ext4 file system. There are some other similar commands for other file systems, but i don't remember they.
Code:
adb shell make_ext4fs /dev/block/[B]mmcblk0p20[/B]
(Bold part can change depending of your device)
Then just do a normal wipe and flash again the ROM.
MiroBiala said:
Here is how I succeeded to enable USB debugging (also adb and remote view) on Samsung Galaxy Note 4 with broken screen.
1. Following the DeathDrifterz's advice I was able to set the device in recovery mode with ROOT access and adb :
2. In other forum I found tutorial how to enable USB debugging from recovery with root access :
Connect the device to Mac or PC in recovery mode. (I had to map the process in my mind as the screen was broken).
Now open terminal/CMD in computer and go to platform-tools/. type and enter ./adb devices to check if the device is connected in recovery mode.
To mount the respective directories, type:
Code:
./adb shell mount data
./adb shell mount system
Get the persist.sys.usb.config file in your system using:
Code:
./adb pull /data/property/persist.sys.usb.config /Your directory
Now open that file in a texteditor and edit it to mtp,adb and save.
Now push the file back in the device:
Code:
./adb push /your-directory/persist.sys.usb.config /data/property
Get the build.prop file:
Code:
./adb pull /system/build.prop /your-directory
Add these lines:
Code:
persist.service.adb.enable=1
persist.service.debuggable=1
persist.sys.usb.config=mtp,adb
Push build.prop back into the device:
Code:
./adb push /your-dir/build.prop /system/
This way you enabled USB debugging on your device. But you still can't connect. Why? Because it asks for RSA verification. If you could view your display then you could easily tap on YES to authorize the device.
3. Skipping RSA verification :
The ADB keys (after authorization) are saved in /data/misc/adb/adb_keys, so I have one Samsung Galaxy S3 with working display which already authorized my PC.
So I got the adb_keys file from it. I connected the Samsung Galaxy S3 to my PC and use :
Code:
./adb pull /data/misc/adb/adb_keys
Then reconnected the Note 4 and pushed the file in it:
Code:
./adb push /your-dir/adb_keys /data/misc/adb/adb_keys
4. Reboot! And Voila: the devices boots normally and adb connects without asking for verification.
After that I used Vysor chrome extension and Vysor apk to view the device screen and act with the device.
I installed the apk with :
Code:
./adb install apk_name.apk
Sources :
https://forum.xda-developers.com/showthread.php?t=2395047
https://android.stackexchange.com/questions/120394/can-i-enable-usb-debugging-using-adb
https://www.vysor.io/
Click to expand...
Click to collapse
Dear experts,
I've been trying to follow the above steps but cannot get data and system mounted:
PS C:\Users\Azubi\AppData\Local\Android\Sdk\platform-tools> adb devices
List of devices attached
52001077b43913d3 recovery
PS C:\Users\Azubi\AppData\Local\Android\Sdk\platform-tools> adb shell mount data
mount: mounting /dev/block/mmcblk0p21 on /data failed: Device or resource busy"
I'm trying to access a Galaxy S5 mini with broken screen and digitizer. It's rooted and runs with TWRP and Lineage OS.
The aim is to enable usb debugging in order to mirror the screen on pc.
Has anyone been encountering this already and could help?
Many thanks
Max