Develop Bugs

can not mount system in read-write mode using adb without recovery mode

I wanted to change my device model, so I copied build.prop from another mobile to my mobile. I am already rooted. But unfortunately I did not change the o.s. from gingerbread to froyo in build.prop ( I have android 2.2 FROYO) When I rebooted, there were many errors. It is now showing no sim card. Mobile network search gives error. Effectively, I can not use the mobile. Terminal emulator, X-plore etc. stopped working. Only Rom toolkit free version works and astro file manager works. Other programs are forcefully closed. Needles to say, I must replace new build.prop with new one.
Using adb I can only pull files but can not write as it is in read only mode.
adb root and adb remount works only if you are in recovery mode ? Y mobile does not have any custom recovery so when I boot in recovery mode it hangs.
Superuser has installed su in system\bin directory. But from adb shell I can use su also. It gives permission denied error. Hence I can not remount the system.
I have read similar threads and found that on some mobiles adb root or adb shell su works but on some not.
I am using Vista 32 bit with admin rights, still can not use root in adb.
Please tell me, how can I mount system read-write. I can not install root explore as google play and even internet is not working.
Please help.

maheshchavan said:
Using adb I can only pull files but can not write as it is in read only mode.
Click to expand...
Click to collapse
activate USB debugging then in console
Code:
adb shell
su
mount -o rw,remount /dev/block/mmcblk0p1 /system
adb push build.prop /system/build.prop
check where is your build.prop

ruscan.calin said:
activate USB debugging then in console
Code:
adb shell
su
mount -o rw,remount /dev/block/mmcblk0p1 /system
adb push build.prop /system/build.prop
check where is your build.prop
Click to expand...
Click to collapse
OMG ruscan.calin i COULD KISS YOU! I had tried to change my OG EVO 4G's buildprop file to another phone so that I could purchase & download an incompatible Google Play app. However after I restarted the phone wouldn't start! It would boot into my rooted HTC EVO 4G Android 2.3.3 and HTC Sense 2.1 but it would get stuck on the wallpaper with just the notification bar at the top and all buttons would be frozen. However I noticed when I plugged in my phone to my computer via usb the computer recognized it. I always keep my phone with USB debugging enabled so I thought I should be good right? I have spent the last 4 hours trying to install and setup adb with no real previous experience with it. I am familiar with dos from years ago and that helped me as it's basic procedure, commands, etc. Then I found out how to install the HTC drivers which I needed and then download the Android SDK with adb that's included which many guides show easily. I started the command prompt (cmd), typed my adb devices command and hurray it showed my phone! I connected and quickly navigated to the build.prop system folder! Luckily when I changed the file I made a bak backup and left it in the same folder. Now the main issue was figuring out how to change the naming of the files which I did via usual adb commands (mv build.prop.bak build.prop). But then to no avail I couldn't get it to write due to it being a system read only folder! Arg! Then I found your post on here, above, and typed it in simply leaving out the adb push portion and replacing that with the mv file command instead and first changing the name of the bad file and then replacing the bak file as the good copy! I exited back to the adb main and unplugged my phone. Moment of truth and man was everything flashing through my head at once! I booted up and YESSSSSSSSSSSSSS, it worked! I went back into root explorer and got rid of the offending leftovers and I've learned my lesson! I just don't want to think about what would have happened if I hadn't found this post. Thank you and if anyone else makes this hug mistake let me know and maybe I can help. Moral of the story don't mess with the build.prop or any system folder unless you know what you're doing! Thanks again!
Quick Guide to Fix Android "build.prop" Issues:
1. Find and download USB drivers for your phone by model or type (HTC EVO 4G's HTC Fastboot drivers): http://downloads.unrevoked.com/HTCDriver3.0.0.007.exe
2. Download and install Android SDK and choose adb: http://developer.android.com/sdk/index.html
Guide: http://htcevohacks.com/htc-evo-hacks/how-to-install-android-sdk-and-adb-drivers-for-htc-evo-4g/
3. Run a command prompt from the "c:/program files/android/android-sdk/platform-tools/" directory. I had to copy the command prompt to get it to open there but sometimes a right-click action will do it. The guide below will help just navigate down to "Using ADB" and skip the rest.
Guide: http://www.howtogeek.com/114667/how...y-default-move-almost-any-app-to-the-sd-card/
4. Once you open the command prompt and you're in the "c:/program files/android/android-sdk/platform-tools/" foler type "adb devices" and your device should appear. If it does move on to next step.
5. Then type adb shell and use the ls command to see directories. Then you'll need to navigate to the system folder by typing "cd system" and then type "ls" to look around in the directory (similar to "dir" in DOS). You should now see the bad build.prop file.
6. You'll need to rename the file or push a correct version. First you need to use the "adb shell" command again and then "su" and finally "mount -o rw,remount /dev/block/mmcblk0p1 /system" to make the directory writable (see ruscan.calin post above for additional info).
Note: I only had to rename my build.prop as I already had my old one in the same system folder. You may have to copy the bad build.prop to your computer, edit it and then push it back to the same system directory. These directions are only for renaming files in the same folder. For the info on how to copy the file to your computer and push it back to your phone go to step *10 below or use the guide below it.
7. I already had the bad build.prop in the system directory with my old one which I had named build.prop.bak. If you have this too simply rename by changing the name first of the bad file to anything by typing "mv build.prop build.prop.bad" or similar.
8. Next rename the build.prop.bak to build.prop by typing "mv build.prop.bak build.prop". Everything should go smoothly and move onto the next step.
9. Finally, If no error messages are found, simply type "adb reboot" or "adb shell reboot" (Depending which version of ADB you have). You should be done, your phone will reboot like normal (working, lol) and everything should be working again! YAY!
*10. To copy the build.prop to your phone type "adb pull /system/build.prop c:\" and the file should be placed in the main c:/ directory on your computer. Navigate to the root (c:/) directory and then right click and "open with" the "build.prop" file using a notepad or other file editor. Then use the text editor (Notepad, etc) to change back what you originally changed to mess everything up. There is tons of stuff on the net to let you know what to fill back in depending on your phone model/type. Or it's possible to get a previous version from an old Nandroid backup or similar. Save the changed text file and make sure its named the same "build.prop" and make sure it's still in the root directory (If you're having issues on this step or just want more insight check out the guides and threads below for more help).
Guide 1: http://androidforums.com/admire-all...p-computer-not-phone-using-root-explorer.html
Guide 2: http://www.modaco.com/topic/328943-quick-guide-to-modifying-buildprop-with-adb/
Guide 3: http://forums.androidcentral.com/sp...-replaced-build-prop-phone-wont-start-up.html
*11. We've already made the directory writable in step 6 so we simply need to push the file back to the phone. If any error message appear re-do step 6 to make writable again. Otherwise push the modified file back to the phone by typing "adb push c:\build.prop /system/". Back to step 9 above! Yay!
If anyone wants to help cleanup this quick guide or make any changes feel free. I just wanted something so that if anyone else has this issue they won't have to worry or search forever to find a solution. OMG it's 2:30AM, to bed... I ride! LOL
Enjoy,
5th :highfive:

THANK YOU!!! Totally saved me today.
One thing that I noticed. After pushing the correct build.prop, I had to fully power down, then turn back on my Razr for it to load up the fixed build.prop.

error message,Help please
Hello, when i am going to mount and change the permission i am getting constant error od device not found or sh:not found.
What to do?Help me please?

jigarpattani said:
Hello, when i am going to mount and change the permission i am getting constant error od device not found or sh:not found.
What to do?Help me please?
Click to expand...
Click to collapse
What step are you on? What phone do you have? More info please?

i am have problem whit my pantech flex i need to use the build.prop.bak but when i type the su it stay in blank do nothing any ideas pls help

ehy there hope someone can help me...i have an archos 97b platinum, messed up with build.prop. So i pulled out and restored but can't push in any way. I have a cwm installed, tablet rooted but i alwais got "permission denied" at push command. Other error is operation not permitted" if i try remount command from adb. i can do mount -o rw,remount /dev/block/mtdblock7 /system but after that push still give me permission denied.
any suggestion?
http://imgur.com/FDLp4fl
i open a 2nd cmd, give the mount -o rw,remount /dev/block/mtdblock7 /system , and system is now rw, but from the first cmd when i give "push build.prop /system (or /system/build.prop) it will always return me permission denied
help

dev.block
i want to view to dev/block using adb shell #
eg . what block is boot.img
what block is recovery.img
what block is system.img
what block is cache.ing
adb shell getprop mtd is not work . Pls Help Me & sent to mail [email protected]

[Q] Noob question - how to set up adb for 8.9?

Hi! I am an extreme noob at this, and I'm aiming to install cm10 on my 8.9. Rooting doesn't seem too difficult, but installing TWRP does.
The instructions in Haschode's post says "Step 1. Backup..." and then gives lot of code lines that if I understand it correctly are to be entered in command prompt after I have installed ADB. Is there something specific for 8.9 in setting this up? I understand I need the adb package, but do I also need special derivers for the 8.9, like these
http://forum.xda-developers.com/showthread.php?t=1890413
And do they work on 8.9? And do I always need to be in "fastboot" when entering adb lines?
Sorry if this is very easy, kind of weary since it seems easy to brick it. And maybe some guidance will benefit others as well Many thanks.

Have you installed the android SDK?
Sent from my GT-N7100 using Tapatalk 2

apd said:
Have you installed the android SDK?
Sent from my GT-N7100 using Tapatalk 2
Click to expand...
Click to collapse
Honest answer is "I'm not sure, I think so". I installed "eclipse", is that enough? Some guides seem to say you have to set up a "path variable"?
Very grateful for the help

cfbruck said:
Hi! I am an extreme noob at this, and I'm aiming to install cm10 on my 8.9. Rooting doesn't seem too difficult, but installing TWRP does.
The instructions in Haschode's post says "Step 1. Backup..." and then gives lot of code lines that if I understand it correctly are to be entered in command prompt after I have installed ADB. Is there something specific for 8.9 in setting this up? I understand I need the adb package, but do I also need special derivers for the 8.9, like these
http://forum.xda-developers.com/showthread.php?t=1890413
And do they work on 8.9? And do I always need to be in "fastboot" when entering adb lines?
Sorry if this is very easy, kind of weary since it seems easy to brick it. And maybe some guidance will benefit others as well Many thanks.
Click to expand...
Click to collapse
The 'dd' command is used to copy and convert files on block devices. In this case, it is used to create images of your device's partitions to restore later in fastboot in case things go wrong. Since you normally don't have access to the partitions being copied, you need to have root permissions on your device. ADB is necessary to communicate with the device's shell which has access to the 'dd' command. ADB commands will only work in normal or recovery modes, and fastboot commands will only work in fastboot mode.

cfbruck said:
Honest answer is "I'm not sure, I think so". I installed "eclipse", is that enough? Some guides seem to say you have to set up a "path variable"?
Very grateful for the help[/QUote. Just download android android adt and do it. From my experience, root step is more difficult than install 2nd boot.
Click to expand...
Click to collapse

Thanks everyone,
I am stuck here:
adb push stack /data/local/tmp/
When i enter that to "Install the stack override in /system:" it says
cannot stat 'stack' no such file or directory
I put the stack file in the directory i'm standing when i'm writing the command, is that correct?
Again many thanks,

The "stack" is the stack override file used to circumvent the OMAP security that checks to make sure certain partitions have the appropriately signed headers.
When working with files from the command line, the file used must be in the current directory or the path to the file must be appended to the command.

soupmagnet said:
The "stack" is the stack override file used to circumvent the OMAP security that checks to make sure certain partitions have the appropriately signed headers.
As mentioned before, when working with files from the command line, the file used must be in the current directory or the path to the file must be appended to the command.
Click to expand...
Click to collapse
Thanks again,
So, file "stack.htm" is in the directory "platform-tools" and I'm standing in this very directory so it looks like this:
C:\adt-bundle\sdk\platform-tools>adb push stack /data/local/tmp/
still get the response
cannot stat 'stack': no such file or directory
why oh why??

cfbruck said:
Thanks again,
So, file "stack.htm" is in the directory "platform-tools" and I'm standing in this very directory so it looks like this:
C:\adt-bundle\sdk\platform-tools>adb push stack /data/local/tmp/
still get the response
cannot stat 'stack': no such file or directory
why oh why??
Click to expand...
Click to collapse
Okay, first of all, the file should NOT be named "stack.htm"! You may want to verify the md5sum of that file before installing it or you may definitely brick your device permanently.
That being said, IF the file were supposed to be called "stack.htm", then the command would be "adb push stack.htm...."
You should seriously consider whether or not you are in over your head before you do permanent damage to your device.

soupmagnet said:
Okay, first of all, the file should NOT be named "stack.htm"! You may want to verify the md5sum of that file before installing it or you may definitely brick your device permanently.
That being said, IF the file were supposed to be called "stack.htm", then the command would be "adb push stack.htm...."
You should seriously consider whether or not you are in over your head before you do permanent damage to your device.
Click to expand...
Click to collapse
Well, I did actually check the checksum, it checked, and the file in hashcodes download link is labelled stack.htm, or rather it is labelled "stack" and is a htm-type-file if understand it correctly. (The name in the directory says just "stack" of course, and under file type it says htm)
I still get the same response. Maybe I am in over my head and is missing something very basic...
Anyway, glad for the help!

cfbruck said:
Well, I did actually check the checksum, it checked, and the file in hashcodes download link is labelled stack.htm, or rather it is labelled "stack" and is a htm-type-file if understand it correctly. (The name in the directory says just "stack" of course, and under file type it says htm)
I still get the same response. Maybe I am in over my head and is missing something very basic...
Anyway, glad for the help!
Click to expand...
Click to collapse
If you are absolutely 100% certain that the md5 checks out, just rename the file to "stack" or change the command to match the file name.
I'm very suspicious though, because on a Windows system, the stack file should be of an unknown file type because there is no file extension. It should just be called "stack".

soupmagnet said:
If you are absolutely 100% certain that the md5 checks out, just rename the file to "stack" or change the command to match the file name.
I'm very suspicious though, because on a Windows system, the stack file should be of an unknown file type because there is no file extension. It should just be called "stack".
Click to expand...
Click to collapse
Ok, there must be something fishy here then, ill look into it tomorrow, thanks for homing in on it!

[GUIDE] Backing up a phone with broken display

I have seen several of threads asking about how to recover data from a phone that has a broken display.
Backing up a phone with broken display
Prerequisites
Rooted phone with broken display/digitizer/etc. Display is nonfunctional for whatever reason.
ADB for your platform. Downloads for Windows, Mac, and Linux can be found at my dev-host.
Drivers installed (Windows), rules file set up (Linux + Mac). Drivers for windows can be found here. Rules file for Linux can be found here.
Recovery file attached to this post. (twrp.img)
External sdcard with at least 2 GB free space inserted in your broken phone.
openrecoveryscript.txt file attached to this post.
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Backing up your broken device
Extract the ADB zip somewhere convenient.
Move the twrp.img recovery file into the ADB extracted directory.
Move the openrecoveryscript.txt file into the ADB directory.
Open a command prompt / terminal window in the ADB directory.
Windows: Windows Key + R => Type in "cmd" then click "RUN".
Linux: Open a terminal window by selecting it from your applications.
ALL:
Code:
cd /path/to/ADB/directory
Pull the battery from your phone, place it back in and boot into recovery (VolUp + Home + Power).
Connect your phone to your computer
Make sure that the following command returns "XXXXXX recovery" before proceeding to the next step.
Code:
./adb devices
Expected output:
Code:
List of devices attached
XXXXXXX recovery
Now to install TWRP recovery to your device. Type the following commands ( after each line). Linux users: Make sure you prepend each command with "./", as in "./adb ...". ALL Make sure you type the commands in CAREFULLY.
Code:
adb push twrp.img /tmp/twrp.img
adb shell dd if=/tmp/twrp.img of=/dev/block/mmcblk0p18
Wait until the last command above returns an output similar to below before proceeding to the next step:
Code:
12916+0 records in
12916+0 records out
6612992 bytes (6.3MB) copied, 1.094278 seconds, 5.8MB/s
Now pull your phones battery and reboot into recovery once again.
Run the following command to make sure your phone has booted into recovery completely.
Code:
adb devices
Expected output
Code:
List of devices attached
XXXXXXX recovery
Type the following to set up a script that will backup your phone to your external sdcard.
Code:
adb push openrecoveryscript.txt /cache/recovery/openrecoveryscript
Reboot your phone once more. This time, TWRP will begin backing up your ROM.
Wait for the backup to finish. You will know it is finished when you feel your phone reboot once more.
Optionally, you can check the state of your backup by running the following command and reading the last couple lines of it's output.
Code:
adb shell cat /tmp/recovery.log
Click to expand...
Click to collapse
Click to expand...
Click to collapse
That's it! Your entire system (/system, /data, /cache, and boot) will be backed up to your external sdcard. Just pop the sdcard in your replacement phone and you're good to go.
Enjoy and donate to the TWRP devs! This would not be possible if TWRP did not use the OpenRecoveryScript scripting engine!

Or you can use skip's unified toolkit.
I literally just used it. Moving the backup to my new device right now.

loserskater said:
Or you can use skip's unified toolkit.
I literally just used it. Moving the backup to my new device right now.
Click to expand...
Click to collapse
Whatever floats your boat :good:

Sorry, had to
Sent from my SGH-I747 using Tapatalk 2

Actually, this process might directly meet my needs.
You mentioned that the recovery image and script were attached to the initial post, though I must be missing something in that I don't see where they might be. Perhaps you could offer a pointer, please?
- ooofest

Ah sorry, you can find the files here
http://forum.xda-developers.com/showthread.php?t=2353828
Don't use the twrp.img from there though...go to the twrp website and download the latest .img file for your phone (d2att)
Sent from my S3 on Sense 5 (you jelly?)

CNexus said:
Ah sorry, you can find the files here
http://forum.xda-developers.com/showthread.php?t=2353828
Don't use the twrp.img from there though...go to the twrp website and download the latest .img file for your phone (d2att)
Click to expand...
Click to collapse
Thanks - I downloaded the appropriate files, but wonder if this can be used on a stock phone.
That is, I was able to push twrp.img to /tmp/twrp.img, but cannot write in the next step:
Code:
adb shell dd if=/tmp/twrp.img of=/dev/block/mmcblk0p18
/dev/block/mmcblk0p18: cannot open for write: Permission denied
This is a stock AT&T phone, in recovery mode, never been rooted.
- ooofest

You need to be rooted for this to work.

CNexus said:
You need to be rooted for this to work.
Click to expand...
Click to collapse
Ya know . . . I need to read things more carefully. Was so excited to see something that might possibly help. Sorry about that.
It's been awhile since I looked into rooting the Galaxy S III and will look around, but don't recall that this can be rooted from recovery, unfortunately. And, it seems that USB Debugging is not turned on when it boots to the lockscreen.
Hm.
- ooofest

Question Seeing root files from computer?

My OnePlus 9 Pro is rooted. I tried seeing the protected system files such as those in /data from my computer in the following ways and none of the work. (I can see these files with Root Explorer on the phone).
1) command line using "adb shell", "ls -l", "cd data", and then "ls -l". The first two commands work, but I get "Permission denied" on the last command.
2) The Google application "Android File Transfer" running on my Mac
3) The Mac application "MacDroid"
4) The open source application "OpenMTP"
Alls of these lead to only seeing the files in the simulated SD card. How can I did deep into the Android file system from my computer, while the phone is connected?
Thanks in advance

@tk_xda
Put su -c before the ls command, or open a root shell by running su. You also need to have superuser access for adb enabled to use this command.

tk_xda said:
My OnePlus 9 Pro is rooted. I tried seeing the protected system files such as those in /data from my computer in the following ways and none of the work. (I can see these files with Root Explorer on the phone).
1) command line using "adb shell", "ls -l", "cd data", and then "ls -l". The first two commands work, but I get "Permission denied" on the last command.
2) The Google application "Android File Transfer" running on my Mac
3) The Mac application "MacDroid"
4) The open source application "OpenMTP"
Alls of these lead to only seeing the files in the simulated SD card. How can I did deep into the Android file system from my computer, while the phone is connected?
Thanks in advance
Click to expand...
Click to collapse
Try adb shell then su and acknowledge it on phone.....

DavidxxxD said:
Put su -c before the ls command, or open a root shell by running su. You also need to have superuser access for adb enabled to use this command.
Click to expand...
Click to collapse
TheGhost1951 said:
Try adb shell then su and acknowledge it on phone.....
Click to expand...
Click to collapse
Thanks. Is there any way to get this level of access using the other utilities I named, or is the only way from the computer through adb commands?

@tk_xda
You can also use a terminal app to open a shell locally on the device. Be careful and don't run
Bash:
rm -rf /*
It will make a painful brick of it.
Have fun!

tk_xda said:
computer
Click to expand...
Click to collapse
Do a TWRP backup and open it on the computer with 7zip
(editing system files while the system is ON can lead to crash ...)

loopypalm said:
(editing system files while the system is ON can lead to crash ...)
Click to expand...
Click to collapse
Yes I can confirm.

tk_xda said:
Thanks. Is there any way to get this level of access using the other utilities I named, or is the only way from the computer through adb commands?
Click to expand...
Click to collapse
No, you could use Termux on phone, similar to adb

loopypalm said:
Do a TWRP backup and open it on the computer with 7zip
(editing system files while the system is ON can lead to crash ...)
Click to expand...
Click to collapse
I would want to access a small group of files on the computer. Copying an entire backup from the phone would be cumbersome. Typically, I might like to get nosy about the database tables an app uses to store its data and would want just the data for an app.
I would not be editing system files unless I have a specific informed purpose, but would like to be able to copy any of them to my computer that I choose to examine.
TheGhost1951 said:
No, you could use Termux on phone, similar to adb
Click to expand...
Click to collapse
I have Root Explorer app on the phone and can rummage with that when I desire to rummage into something on the phone. My current workaround when I want a few system protected or app data files is to copy them with the Root Explorer into the simulated SD card, and then get the data from there with the computer. By this post, I was hoping to navigate more directly just by connecting the phone to the computer and copying what I want.

tk_xda said:
I would want to access a small group of files on the computer. Copying an entire backup from the phone would be cumbersome. Typically, I might like to get nosy about the database tables an app uses to store its data and would want just the data for an app.
I would not be editing system files unless I have a specific informed purpose, but would like to be able to copy any of them to my computer that I choose to examine.
I have Root Explorer app on the phone and can rummage with that when I desire to rummage into something on the phone. My current workaround when I want a few system protected or app data files is to copy them with the Root Explorer into the simulated SD card, and then get the data from there with the computer. By this post, I was hoping to navigate more directly just by connecting the phone to the computer and copying what I want.
Click to expand...
Click to collapse
Some things are easy and some are not. It can't be about shortcuts all the time. Sometimes the reward takes some effort!

tk_xda said:
... database tables an app uses to store its data and would want just the data for an app.
Click to expand...
Click to collapse
Even if you found a way to mount "data" it will be encrypted (unless you running an old rom or flashed DFE before ...)
see also this

Help enabling adb from recovery (broken screen)

The purpose of this is to use my phone via scrcpy for my sms verification and stuff.
So far I've tried these methods of editing default.prop/prop.default, and setprop persist.sys.usb.config etc etc
but still undetected from "adb devices"
Any workaround? thanks
I'm using OrangeFox recovery.

VanGreat said:
The purpose of this is to use my phone via scrcpy for my sms verification and stuff.
So far I've tried these methods of editing default.prop/prop.default, and setprop persist.sys.usb.config etc etc
but still undetected from "adb devices"
Any workaround? thanks
I'm using OrangeFox recovery.
Click to expand...
Click to collapse
Orange Fox has enabled ADB by default. Your screen is broken? How do you know OF has been booted?

VanGreat said:
So far I've tried these methods of editing default.prop/prop.default, and setprop persist.sys.usb.config etc etc
but still undetected from "adb devices"
Click to expand...
Click to collapse
How did you edit these files? Did you un-/repack the recovery.img inside the downloaded zip?
The prop.default in your ramdisk.img shows:
ro.adb.secure=0
persist.sys.usb.config=adb
Everything seems to be correctly from device's site. No need to edit sth.

No. Somehow I need to access to adb on OS and those settings has been disabled on new rom. As I said i need to access to my sms app

You'd like to patch the setting files via recovery to gain access with ADB in system? USB-debugging is toggled off? Are there already the adb_keys of your PC in /data/misc/adb to allow access?

Yes I need to enable usb debugging through recovery.
I think i have to enable adb first before authorizing my device on /data/misc/adb

We do both via OF:
First you should find the needed setting file and check its permissions for restoring it correctly afterwards (assuming you're already in the device's shell by entering 'adb shell'):
Code:
ls -al /data/system/users/0/settings_global.xml
Note the permissions.
Then leave the device's shell and pull the file:
Code:
exit
adb pull /data/system/users/0/settings_global.xml
Open setting_global.xml with an editor and set the line
Code:
package="com.android.settings" defaultValue="0" defaultSysSet="true" /> <setting id="7676" name="adb_enabled"
to value=1
Push the file back:
Code:
adb push settings_global.xml /data/system/users/0
and check the permissions:
Code:
ls -al /data/system/users/0/settings_global.xml

Authorizing:
On your PC search for
Code:
C:\Users\<USER>\.android\adbkey.pub
copy that file into your ADB folder. Then push it to:
Code:
adb push adbkey.pub /data/misc/adb_keys
and set the permissions:
Code:
adb shell chmod 0640 /data/misc/adb_keys
adb shell chown system:shell /data/misc/adb_keys

okay i'm now on your authorizing part, it now says something but it still says unauthorized on "adb devices"

what i actually did was to flash aosp rom and edit build.prop there and set the adb variables

USB debugging seems to be active. But I don't know why it says unauthorized. Maybe there is another setting related to ADB in settings_global.xml that needs to be activated for Xiaomi devices like yours.

VanGreat said:
what i actually did was to flash aosp rom and edit build.prop there and set the adb variables
Click to expand...
Click to collapse
Do not edit any file but the setting file. You must not change the props.

something wrong with /data encryption. I for sure pushed the adb_keys on /data/misc/adb but when I rebooted at the recovery or system it goes back nothing.
some say this was aosp system as they won't allow /data modification?

Are you able to open /data in OF and do you see the folders/files in there? With the correct names?

If yes, you don't have any problems with encryption

WoKoschekk said:
Are you able to open /data in OF and do you see the folders/files in there? With the correct names?
Click to expand...
Click to collapse
i only saw recovery folder. also gave me "cant mount /data (invalid argument)" when i try to mount it first.

VanGreat said:
i only saw recovery folder. also gave me "cant mount /data (invalid argument)" when i try to mount it first.
Click to expand...
Click to collapse
Then you have no chance to activate ADB and get access to your SMS.

assuming encryption is healthy in boot mode, you can enable usb-debugging and authorize RSA key from either /system or boot, no access to /data needed.
this is for custom ROM by modifying /system
[OTA] ADB-Enabler - Flashable UPDATE.ZIP File
This tool is not meant to be used on Android devices with dm-verify or Android Verify Boot (AVB) enabled Every Android device has a stock recovery installed. That default recovery typically at least offers you the 4 options reboot system now...
forum.xda-developers.com
this is for stock ROM by modifying boot
Accessing my phone with a dead screen
So my phone screen connector was liquid damaged. No touch or display. It's an Essential Phone which supports HDMI output, however I can't unlock it because I don't see the lock screen on the monitor I just see a lock icon. I have...
forum.xda-developers.com
take note (on stock MIUI only) scrcpy won't work on xiaomi devices, com.miui.securitycenter prevents that. unless you have bonded mi account, you can't enable USB debugging (Security settings) in developer options.