Related
Hello guys,
I want to share with you a modification of the Android Developers Bridge that I've been working on. I've mod it so that it synchronises a folder in your desktop with a folder in your phone (the sdcard) through the USB wire without having to mount/unmount the sdcard (I feel this is quite slow). It is very similar to services like Dropbox, UbuntuOne etc. but without using internet.
(It seems I can't post URLs because I haven't posted before here. Sorry for making you have to copy&paste...)
More explanations can be found here:
[GITHUB]https://github.com/kendersec/ADBLink/blob/master/README
The binary for the modified adb is in the downloads section:
[GITHUB]https://github.com/downloads/kendersec/ADBLink/adb
and you can find the all the source code and some documentation here:
[GITHUB]https://github.com/kendersec/ADBLink/
It's all ready to compile (no need to download the whole Android system).
I hope some of you find it useful
Very cool idea! I'm surprised there aren't more ADB mods!
This looks like its very painfully close to what I've been looking for: adb sync that works bidirectionally. Basically, when I'm backing up my SDcard I don't want to have to adb pull files that haven't changed since this wastes time and effort (this would also be extremely helpful for backing up the new CWM nandroid blob folders; only backing up the new/modified files). Currently the adb sync command will sync files from desktop to phone, but NOT from phone to desktop. Can ADBLink do this, and if so, is there any way to do it without a daemon? Just a one-shot command when I'm backing up my phone is all I'm looking for.
Sorry for necro-bumping the thread, but this is a great little mod so maybe more people should see it. Thanks for any help you can provide!
Request and Thank You!
osm0sis said:
Very cool idea! I'm surprised there aren't more ADB mods!
This looks like its very painfully close to what I've been looking for: adb sync that works bidirectionally. Basically, when I'm backing up my SDcard I don't want to have to adb pull files that haven't changed since this wastes time and effort (this would also be extremely helpful for backing up the new CWM nandroid blob folders; only backing up the new/modified files). Currently the adb sync command will sync files from desktop to phone, but NOT from phone to desktop. Can ADBLink do this, and if so, is there any way to do it without a daemon? Just a one-shot command when I'm backing up my phone is all I'm looking for.
Sorry for necro-bumping the thread, but this is a great little mod so maybe more people should see it. Thanks for any help you can provide!
Click to expand...
Click to collapse
Exact same situation here. I second this request, and also extend my own thanks to the author of this mod :good:
Hey, same thing here. Any way to sync a specific folder to pc automatically via adb (usb)?
Hi, all I want to do is put a script somewhere which will be executed during boot/startup as root.
Actually I want to (try to) delete about 10 cyanogenmod apps (browser, file browser, voice caller etc.) on every boot so I can keep updating cm as much as I want without manually uninstalling those apps.
I have made script in the past and I was able to use it from terminal emulator as root but I have never got lucky by putting script somewhere where it will be executed automatically.
P.S. I am not sure if I should post it to Q&A forum, but it is more complex I think so I will post it here. Please be kind moderators to me and just move it to Q&A forum if necesarry.
Put your scripts in /data/local/userinit.d. They will run upon boot.
You can also use the Scripter tool within ROM Toolbox Pro. Paste in your script then click 'Set at boot'.
Only valid for Moto G 2014!
Hello, forum mates. I have spent few days with this great device, I gave it meanwhile to my sister as present.
ATM, there are barely any custom ROMs, so I will list here few good things to do right after unlocking its bootloader and obtaining root access :angel:
So here you can read my little checklist and do whatever you prefer:
DISCLAIMER:
Code:
[I]your warranty is now void. All you do
with your phone is on your own risk!
Partitions info is valid for XT1068
international GSM dual-SIM only! Workflow
is tested only on KitKat factory image![/I]
Click to expand...
Click to collapse
Unlocking Bootloader: Motorola's website
Removing startup screen with warning of unlocked bootloader: flash attached zip in custom recovery
(I can confirm that the attached zip works, it will restore the white original Motorola splash screen)
1. Boot custom recovery without flashing it:
Copy and paste custom recovery (file format: img) into your SDK/platform-tools folder, I recommend here TWRP_2.8.0.1_Titan_v2 that I have successfully tested myself. Until this point the latest Motorola USB driver must be installed on your Windows PC, USB debugging (under "developer options") on your phone must be enabled. However, I generally recommend using Linux instead of Windows. You can check in my short guide for Ubuntu users how to install fastboot and ADB in Ubuntu. I have no clue about Mac iOS, sorry.
Here we go:
Navigate in CMD line into the directory where your adb.exe is saved. Example on my PC, it is in the folder "AndroidSDK", and there in the folder "platform-tools". So my commands would be:
Typing on keyboard Win+R
Enter cmd
the command line appears after that
Code:
cd c:\androidsdk\sdk\platform-tools
Now I'm in my desired folder. The next command is checking the USB driver / ADB connection:
Connect the phone to with your PC via USB cable and enter in cmd:
Code:
adb devices
Correct response:
HTML:
xxx(serial No)xxx device
If you don't see serial No of your Moto G, check if USB debugging is enabled. If serial No is there but "offline" instead of "device" appears, you will only have to confirm the promt on your phone's screen to allow USB debugging. If nothing appears, try to update your USB driver (don't go any further without working ADB connection!)
Now we will boot into bootloader mode and check there if fastboot connection is also working:
Code:
fastboot devices
Correct response:
HTML:
xxx(serial No)xxx fastboot
If the response looks like that, we can now boot into the custom recovery without flashing it onto device. The recovery.img will be booted directly from "platform-tools" folder, while stock recovery still remains installed on the phone. My recovery.img file's name is for example "TWRP-Titan", so after I've previously saved it in my "platform-tools" I will now enter in cmd:
Code:
fastboot boot TWRP-Titan.img
The phone will boot into the beautiful touch-recovery TWRP. Blue screen is there? Yesssss!! :good:
Now we can start with backups of our still 100% stock firmware in the next chapture.
Click to expand...
Click to collapse
2. Backup your stock firmware:
While still in the TWRP, simply create backup of all your partitions. It is strongly recommended to save backup on the external SD card, as many modifications or next unlocking of the bootloader (if relocked) will every time blow all your data from the internal memory.
Now still in TWRP, install SuperSU.zip
Reboot into the system
Now we will backup stock recovery, that we can later flash at any point back:
Code:
adb shell (enter)
su (enter)
Look at this point on the screen of your phone, SuperSU will promt you to allow SU access for shell, You should confirm that.
Code:
dd if=/dev/block/mmcblk0p32 of=/sdcard/recovery.img
It will save the "recovery.img" file in your /sdcard folder on your phone's internal memory. It is strongly recommended to create the new folder on your external SD card where you can move all backup img files. To move the files, use any root file browser like for example Root Browser. When you open Root Browser for the first time, it will prompt oyu to install few utilities (busybox, unrar etc) which you should allow.
At this point, your entire stock firmware has been saved as backup.
Click to expand...
Click to collapse
3. Backup all partitions of your factory image / firmware:
Just the same way as you have previously created backup of your "recovery.img" you can
create "img" backup files of all your partitions. Check the attached screenshots and simply replace in the adb shell command the number of the mmcblk0p block No with the one you desire to backup and change "recovery" to the proper partition names, just like in the screenshots:
Click to expand...
Click to collapse
4. Restore to 100% stock firmware:
To return to 100% stock, you simply need to flash (or only boot) again TWRP 2.8.0.1, to restore your nandroid backup of your stock firmware and -if custom recovery was flashed- to flash in bootloader mode your stock recovery back. Paste your (stock) "recovery.img" file into "platform-tools" folder and execute in bootloader mode:
Code:
fastboot flash recovery recovery.img
After that simply restore your TWRP backup of stock and flash in bootloader mode your stock recovery back. To unroot permanently, open SuperSU app and choose the option "Full unroot" under "settings".
To relock the bootloader again: reboot to bootloader mode and execute in cmd:
Code:
fastboot oem lock
Your Moto G should be now again 100% stock.
Click to expand...
Click to collapse
If you benefit from this guide, show me your love and please hit "THANKS" button.
Credits also to all guys who have created linked guides (please hit there "thanks" also)
EASY MODS (Moto G 2014 stock firmware)
I am myself very big fan of SlimRoms (I was AlphaBeta SlimKat tester on few devices), so I was desperately missing the "Real Dark Slim" mode (and several other mods) on the Moto G 2014 factory image 4.4.4
I had to darken my Moto G 2014, so here I share now quite easy way how to get dark UI on many apps:
Click to expand...
Click to collapse
DARK UI APPS:
On the attached screenshots is an example of the "normal" Play Store (light UI) YouTube app vs the modified, dark UI YouTube app.
Luckily, the Team BlackOut consisting out of some great developers and contributors has darkened out whole bunch of apps. Please visit their website or please visit their thread where you can get more info and download directly the app TBO updater (ver.5.0.0 is up to date ATM, it is a lot better than the v.3 which was suffering of regular FCs on many devices).
With the TBO app you will find also boot animations, wallpapers etc and info how to install, the most important to avoid data loss and crying is: don't forget to create nandroid backup before modifying!
List of modified apps by the TBO available in dark UI (choice, uncomplete list):
Apollo music
Calendar
Chromecast
Drive
DropBox
Ebay
ES File Explorer
Facebook
Google now
Google+
Gmail
Hangouts
Instagram
Keep
MMS (AOSP)
Netflix
PayPal
PlayStore
WhatsApp
Skype
Spotify
Translate
Twitter
YouTube
etc.
Small tipps for the flawless un/installation of the system apps:
Regarding the fact that issues could occur when replacing the system apps (probably caused by smaller scripts which might remain as "corpses" after removing the apps) here is quite reliable way to go:
gain root access (flash SuperSU zip in custom recovery)
backup all apps that should be replaced with the darkened ones (recommended: Titanium Backup to create backup, or SD Maid to create *apk file)
now uninstall the respective apps (also with TB or SD Maid)
Open Play Store, install again and uninstall respective apps (that will remove reliably all rests)
Install the darkened apps (apk files or flashable zips that you have downloaded with TBO Updater)
Enjoy dark apps!
TROUBLESHOOTING: If anything goes wrong (bootloop, dark app FCs etc) delete darkened app and restore your app backup. I have never faced bootloop, but some apps simply might not work and will FC. Even if somebody would face bootloop, restoring the nandroid backup will revert all changes.
For normally installed apps (non-system apps): simply uninstall them through Play Store and install darkened ones instead. If TBO apps don't work, uninstall them and install again from the Play Store normal versions.
Click to expand...
Click to collapse
All credits here go to @djdarkknight96, @B_Boytm, @Gunthermic, @dafoxs, @train, @darkknight and our beloved SlimGapps maintainer, @dankoman :highfive:
Sorry, if I forgot to mention someone- remind me please!
(please if you use their modified apps, don't forget to find some posts of those guys here on forum and hit several times "thanks" button!)
Xposed frameworks
Add hunderds of mods, change functions of your hardware buttons, add double-tap-to-sleep, make your phone to fly etc, endless mods possibilities with Xposed frameworks (main thread)
Little guide for people who never used Xposed frameworks before:
download Xposed installer apk (v. 2.7 experimental is my recommendation for 4.3 and newer firmwares)
download also Xposed-Disabler-Recovery.zip from the main thread (if anything goes wrong)
create nandroid backup!
install Xposed installer app
open the app and Install/Update framework
reboot
if anything goes wrong, you end up with bootloop or so, reboot recovery and flash Xposed-Disabler-Recovery.zip (if even that doesn't help, restore nandroid backup)
if the phone reboots fine (it should) download modules you desire to use and install them
reboot
enjoy your new, customized firmware
If you find this post useful, please hit "THANKS" and honour my time spent to share this with you. Please also hit thanks to all devs and contributors whose work brought you benefits.
Click to expand...
Click to collapse
Hope to see soon more tweaks from you
Gerriitw said:
Hope to see soon more tweaks from you
Click to expand...
Click to collapse
I will post in the second post few more ideas with smaller mods on the stock firmware like using dark UI apps, some useful little frameworks modules, debloating etc.
This thread is actually not so interesting for experienced users, it's all quite common stuff.
tetakpatalked from Nexus 7 flo
Very helpful for newbies....U have done great job...hope to see more...
Second post updated (mods of stock 4.4.4 firmware)
Hello guys
I have a OP 8 Pro rooted phone with Android 11.
I want to remove pre-installed apps but the system is in Read-only mode.
I use Root Explorer with root access but impossible to have RW mode in Root Explorer.
I try with adb but nothing happen.
It seems that the rw mode is inaccessible.
Can you help me please ?
Thanks for all.
Johncaffee said:
Hello guys
I have a OP 8 Pro rooted phone with Android 11.
I want to remove pre-installed apps but the system is in Read-only mode.
I use Root Explorer with root access but impossible to have RW mode in Root Explorer.
I try with adb but nothing happen.
It seems that the rw mode is inaccessible.
Can you help me please ?
Thanks for all.
Click to expand...
Click to collapse
Did you tried MiXplorer? I had various issues with other file explorers but MiXplorer always worked fine for me.
MiXplorer
Raiz said:
Did you tried MiXplorer? I had various issues with other file explorers but MiXplorer always worked fine for me.
MiXplorer
Click to expand...
Click to collapse
Sorry I've just seen your response (sorry for my english).
I've found a solution.
You have to install adb before and USB Debugging enabled.
Plug the phone into PC and change it from charge only to file transfer.
In the folder where adb is installed, you have to do SHIFT+RIGHT CLICK to open PowerShell.
Then, in the terminal, enter :
adb devices
This print the serial number of the device (first time you have to click ok on the phone).
after, enter :
adb shell
You are into your phone.
execute the next command :
pm uninstall -k --user 0 "name of package"
(without quote. You can see the name of package in Titanium or SD Maid for exemple.)
Done
It seems to be ok for me.
Johncaffee said:
Sorry I've just seen your response (sorry for my english).
I've found a solution.
You have to install adb before and USB Debugging enabled.
Plug the phone into PC and change it from charge only to file transfer.
In the folder where adb is installed, you have to do SHIFT+RIGHT CLICK to open PowerShell.
Then, in the terminal, enter :
adb devices
This print the serial number of the device (first time you have to click ok on the phone).
after, enter :
adb shell
You are into your phone.
execute the next command :
pm uninstall -k --user 0 "name of package"
(without quote. You can see the name of package in Titanium or SD Maid for exemple.)
Done
It seems to be ok for me.
Click to expand...
Click to collapse
This command is used to hide the app from the main user, the apk file is still here and if you factory reset the apps will be there again.
If it doesn't bother tho that's cool
Pre-installed apps ( so called bloatware ) typically are located in /system/priv-apps, their owner typically is ROOT what means they can't get uninstalled / deleted by ordinary Android user ( e.g user 0 ), so, disabling them pretty much remains your only option.
I tried Mixplorer but the file is blocked in read-only mode
Johncaffee said:
I tried Mixplorer but the file is blocked in read-only mode
Click to expand...
Click to collapse
You need to enable root in mixplorer settings
I do it.
Just in Android 11, it seems to be impossible to enter in rw mode.
Johncaffee said:
I do it.
Just in Android 11, it seems to be impossible to enter in rw mode.
Click to expand...
Click to collapse
..
Not work.
I have the same screen like you. I remove but thd phone say "no deleted file".
Johncaffee said:
Not work.
I have the same screen like you. I remove but thd phone say "no deleted file".
Click to expand...
Click to collapse
I get those messages, the folder I delete stays but the file inside is deleted
Not me. The file is still here
try systemrw 1.32.
open twrp and put in this ZIP:
systemrw_1.32_flashable.zip
and all systemwide rw mode
Edit: the Owner of this ZIP ask me to remove that File here.
Im amazed how noone replied with proper instructions. The guy literally wants a r/w ability. Inorder to do that super partition needs to be modified which is done with systemrw zip.
At least someone shared it. Thanks @012345678
012345678 said:
try systemrw 1.32.
open twrp and put in this zip
and all systemwide rw mode
Click to expand...
Click to collapse
It seems to be work. Thank you
012345678 said:
try systemrw 1.32.
open twrp and put in this zip
and all systemwide rw mode
Click to expand...
Click to collapse
Worked on OnePlus 8 Pro (IN2023) with OxygenOS 10.5.10.IN11AA. Thanks
Hi @012345678. Thanks for your interest in my SystemRW project.
Sorry but unauthorized, unofficial, unverified re-uploads of my SystemRW files (or parts thereof) are not allowed!
Therefore I must please ask you to remove your unauthorized, unofficial, incomplete re-upload of my SystemRW project from your comment above. The unofficial version that you re-uploaded it's missing the original sysrw_repair script!
Instead could you please simply put a link to the official SystemRW project page ? Thanks
The official download mirrors that I provided there work just fine and I'll add more official download mirrors soon! Dont worry
I can only offer customer support for the latest official version of my script that was downloaded directly through the official SystemRW project page
Thank you!
Enjoy a fully read/write-able device!
Great news! New SystemRW version coming soon!
lebigmac said:
Hi @012345678. Thanks for your interest in my SystemRW project.
Sorry but unauthorized, unofficial, unverified re-uploads of my SystemRW files (or parts thereof) are not allowed!
Therefore I must please ask you to remove your unauthorized, unofficial, incomplete re-upload of my SystemRW project from your comment above. The unofficial version that you re-uploaded it's missing the original sysrw_repair script!
Instead could you please simply put a link to the official SystemRW project page ? Thanks
The official download mirrors that I provided there work just fine and I'll add more official download mirrors soon! Dont worry
I can only offer customer support for the latest official version of my script that was downloaded directly through the official SystemRW project page
Thank you!
Enjoy a fully read/write-able device!
Great news! New SystemRW version coming soon!
Click to expand...
Click to collapse
Sure, i removed that. Sorry
Hello guys
Just to say : doesn't work on Oxygen OS 11.0.11.11 IN11BA.
That's all.
Have a good day
Hi @Johncaffee thanks for your feedback. What exactly is the problem with your OnePlus device? You must tell me now because I'm working on brand new version which will be released very very soon (this month!)
It's work with older Oxygen firmware version but not with new firmware version?
Development of new version took a little bit longer than expected because my SystemRW / SuperRW featuring MakeRW by lebigmac project was stolen, hacked, rebranded and reuploaded as their own by multiple hacker thieves in the meantime. It's almost impossible to protect open source or even closed source software from ruthless cyber pirates nowadays. Anyone good with obfuscation and encryption please contact me now thanks!
Thanks you too have a nice day
****Moderator Note****
A thread on this topic already exists here. Links have been removed from this one.
In Samsung's TTS app, someone discovered an exploit where the app, using it's receiver capabilities, will accept just about any command or information it receives from just about anything. This exploit so far as I know has not yet been patched but does affect a significant number of existing Samsung devices up to present day including the Samsung Galaxy Note 9 (SM-N960U) and probably others. Essentially this exploit allows a user to to run commands as system user (User: 1000) which is essentially one user level below root access. I am hoping this exploit will assist us in finding a root method for this device. In the meantime, as system user, you can run any command in a shell that is available to system. Running root commands will not work. I have not yet explored the extent of this exploit's capabilities, but you can change system props, some of which persist a reboot, probably disable some applications as opposed to uninstalling them per user, have full access to the /data directory and the ability to change anything in /data/system/users/0 at the very least. You need a Windows computer in order to perform these operations. It maybe possible to do through linux, but I did not try. This will also allow Lsposed patch to be installed on the device (a variant of the xposed framework). Though I am not sure it is required this will also allow you to use the dial pad on the device to Launch pretty much every important Samsung secret code that exists. Using Google to search for Samsung secret codes you can find what you need.
NOTE: I did not create this exploit and I do not claim any authorship or ownership over it. I just got it to work on this device. For reference, further reading and additional details and installation methods, please ***Link removed*** The steps below is the easiest and most basic method.
IMPORTANT: changing some of these props and other settings may cause device instability. In some cases a general factory reset will not change these settings back to your factory settings, so if you screw something up you're going to have to download your device's stock firmware and flash your device using odin.
1. Go to the Github repository above and download the zip file and extract it to anywhere you want. If you don't have minimal ADB and fastboot installed, you can get it here. Otherwise you'll need to download Google's platform-tools for Windows.
2. Plug your Note 9 into your PC, making sure ADB is authorized on the device.
3. Navigate to the exploit's folder and open a cmd window inside the folder, or place the folder's files in the platform-tools folder and navigate there and open a cmd window. To do this, click on the folder's window, press and hold down the shift key while right-clicking your mouse and select either "open cmd window here" or "open powershell window". Use adb to push the "samsungTTSVULN2.apk" to /data/local/tmp:
Code:
adb push samsungTTSVULN2.apk /data/local/tmp
.
4. Install "komraids_POC_V1.5.apk" using adb and reboot your Note 9:
Code:
adb install komraids_POC_V1.5.apk and open the app once. Navigate to settings, apps and select the app. Turn off battery optimizations.
adb reboot
5. When your Note 9 is completely rebooted (wait a minute or two after turning it back on, before you unlock your device), return to the exploit's or platform-tools folder and run 'systemshell.exe'. When the box pops up, click on 'start shell' and wait for the process to complete. When finished, click on 'reopen running shell'. You should be user: 1000. Run 'id' in that shell and the user should return as user: 1000. If not successful, navigate to the Github repository for other means of installation. Please note you will have to run this process on your device after every reboot.
With this level of access, you can change some system props, launch hidden activities including some degbug menus in various apps, as well as other things. From the Github repository, some examples of abilities:
Access to most of /efs /efs/imei /efs/sec_efs /efs/FactoryApp - Access to most of /data /data/system /data/user/0/ANY_SYSTEM_APP - The "Insthk" bin becomes useable, - Secure Folder/Separated Apps becomes COMPLETELY compromised if you also install the POC in it (UID 150_system) - start IOTHidden Menu, DM Mode, Service Mode, Multiple Debugging and hidden menus as well as preconfig in system context- Change many protected props, such as: setprop persist.service.adb.root 1, setprop sys.hidden.otatest 1, setprop sys.hiddenmenu.enable 1, setprop persist.sys.knox.device_owner true, setprop persist.sys.usb.qxdm.debug 1, setprop persist.service.adb.enable 1, setprop persist.sys.usb.qxdm.debug 1, setprop persist.rollback.is_test true, setprop sys.oem_unlock_allowed 1.
Click to expand...
Click to collapse
Some props I was able to change which persist upon rebooting:
Code:
persist.service.adb.root 1
setprop sys.hiddenmenu.enable 1
persist.service.adb.enable 1
persist.security.ams.enforcing 0
I am hoping with this access we can figure out a way to use it to our advantage to gain root access. I have only ever had this experience once, where we had gained system level shell access through a debug app accidently left on an Amazon Fire 10 tablet. That access later progressed to root access and from my understanding it is most likely possibility if we can gain this level of access on the device than it is more than likely there is a way to also gain root access. I would very much like any feedback anybody can provide and hopefully we can get further along in this. Please post your modifications and other tricks and hacks in this thread so others can follow along.
@DragonFire1024 Please note that a thread already exists on this topic:
***LOCKED UNTIL FURTHER NOTICE*** System Shell Exploit - ALL Samsung Mobile Devices NO BL UNLOCK REQUIRED.
***MODERATOR ANNOUNCEMENT: THREAD CLOSED*** @K0mraid3 you are hereby required to provide proper credit in your OP as follows: Link the assigned CVE for this exploit as it mentions the author's blog and GitHub, OR Link the original research repo...
forum.xda-developers.com
We do not allow multiple threads on the same topic:
5. Create a thread topic or post a message only once, this includes external links & streaming media.
As a large forum, we don't need unnecessary clutter. You're free to edit your message as you like, so if you do not receive an answer, revisit your message and see if you can describe your problem better. Not everyone is online at the same time so it might take a while before you receive an answer.
You can bump your unanswered question once every 24 hours
Duplicate threads and posts will be removed
Always post in an existing thread if a topic already exists, before creating a new thread.
Use our search function to find the best forum for your device.
Links to an external source are only allowed if relevant to the topic in hand. A description must be included, no copy & pasting from the original source.
Click to expand...
Click to collapse
I am closing this thread.
If you or someone else working on the project would like to have an open thread to discuss this topic, please refer to the original. However, I expect you to read the warnings I have posted, as the exploit covered must be credited to the individual who discovered it.