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!
Related
tryin to get mac to adb to device, but cannot get it to work.
anyone have success? would like to test these nice roms out.
thanks
nitty917 said:
tryin to get mac to adb to device, but cannot get it to work.
anyone have success? would like to test these nice roms out.
thanks
Click to expand...
Click to collapse
I did it on my MBP. What problems are you having?
I did it on my macbook..
I also did it on my Mac. Like someone else said what specifically is the issue you're encountering?
there is a post in about using Terminal app from the market to do this and it works!
brianb7590 said:
I did it on my MBP. What problems are you having?
Click to expand...
Click to collapse
thanks, I cant get it to communicate in terminal,
i have no idea. i dloaded the sdk, dragged the adb from tools folder,
onto the terminal, it opens up all the adb commands but after that i cant type
nothing.
nitty917 said:
thanks, I cant get it to communicate in terminal,
i have no idea. i dloaded the sdk, dragged the adb from tools folder,
onto the terminal, it opens up all the adb commands but after that i cant type
nothing.
Click to expand...
Click to collapse
Don't drag it to the terminal.
I would navigate to the directory where you stored the SDK and go to the tools folder and run it that way or you search up how to set your PATH to include the tools folder.
nitty917 said:
tryin to get mac to adb to device, but cannot get it to work.
anyone have success? would like to test these nice roms out.
thanks
Click to expand...
Click to collapse
Like the others who have already replied, I also did it on my mac and was a complete noob. It was only through much trial, error, YouTube, and 3 other sites that I figured it out. Needless to say I'm now fluent in adb and would be happy to answer any questions you have since I was in exactly the same shoes as you last weekend. Below are the biggest things you need to know when you start:
1. When you plug the phone into your computer make sure you select "Charge Only." If you select "Use Phone as Disk Drive" you won't be able to write to the phone, only read. I ran in circles for a long time getting "Read-Only File System" errors and it was all due to having the phone mounted as drive.
2. Make sure you have USB Debugging turned on. After that, you should be able to communicate with the phone fine.
3. ADB - The instructions are nearly identical regardless of operating system but on a mac you need to add "./" (without the quotes) before adb commands. For example, lets say I have a file on my desktop called "Test_File.img" that I want to push to the root of the sdcard. On my Mac I would type "./adb push /Users/Bryan/Desktop/Test_File.img /sdcard/" (without the quotes of course) & (Bryan is my Username)
4. To avoid any issues make sure none of the folders or file names you are working with have spaces in the name.
Hopefully all this helps and does no lead to more confusion than when you started. Again, if there are any specific errors you are seeing post them here and either I or someone else would be happy to answer them.
Bryan
okolowicz said:
Like the others who have already replied, I also did it on my mac and was a complete noob. It was only through much trial, error, YouTube, and 3 other sites that I figured it out. Needless to say I'm now fluent in adb and would be happy to answer any questions you have since I was in exactly the same shoes as you last weekend. Below are the biggest things you need to know when you start:
1. When you plug the phone into your computer make sure you select "Charge Only." If you select "Use Phone as Disk Drive" you won't be able to write to the phone, only read. I ran in circles for a long time getting "Read-Only File System" errors and it was all due to having the phone mounted as drive.
2. Make sure you have USB Debugging turned on. After that, you should be able to communicate with the phone fine.
3. ADB - The instructions are nearly identical regardless of operating system but on a mac you need to add "./" (without the quotes) before adb commands. For example, lets say I have a file on my desktop called "Test_File.img" that I want to push to the root of the sdcard. On my Mac I would type "./adb push /Users/Bryan/Desktop/Test_File.img /sdcard/" (without the quotes of course) & (Bryan is my Username)
4. To avoid any issues make sure none of the folders or file names you are working with have spaces in the name.
Hopefully all this helps and does no lead to more confusion than when you started. Again, if there are any specific errors you are seeing post them here and either I or someone else would be happy to answer them.
Bryan
Click to expand...
Click to collapse
If you're going to be using adb on a regular basis, and want to avoid typing "./" before each command, you can add the android sdk tools path to your .bash_profile file in your home directory. Something along the lines of:
export PATH=${PATH}:/path_for_ur_sdk_folder_location/android-sdk-mac_86/tools
mocalve said:
If you're going to be using adb on a regular basis, and want to avoid typing "./" before each command, you can add the android sdk tools path to your .bash_profile file in your home directory. Something along the lines of:
export PATH=${PATH}:/path_for_ur_sdk_folder_location/android-sdk-mac_86/tools
Click to expand...
Click to collapse
That wont be saved. It goes away after every reboot.
Fixter said:
That wont be saved. It goes away after every reboot.
Click to expand...
Click to collapse
True, if you enter it from the command line. But if you add it to the .bash_profile file , it will stick... at least on my Mac Pro it does...
mocalve said:
True, if you enter it from the command line. But if you add it to the .bash_profile file , it will stick... at least on my Mac Pro it does...
Click to expand...
Click to collapse
If I add those entering nano .bash_profile and enter that command and the pressing Ctrl X and Yes it will stick?
Fixter said:
If I add those entering nano .bash_profile and enter that command and the pressing Ctrl X and Yes it will stick?
Click to expand...
Click to collapse
It should... although I use vi instead of nano. Regardless, after saving the .bash_profile, you'll have to fully exit the terminal application and restart for the path setting to take effect. After that, it'll be in effect every time you start terminal.
mocalve said:
It should... although I use vi instead of nano. Regardless, after saving the .bash_profile, you'll have to fully exit the terminal application and restart for the path setting to take effect. After that, it'll be in effect every time you start terminal.
Click to expand...
Click to collapse
Nano is way cleaner. And yeah. It got applied.
So I have no idea why my G2 isn't being found with the htc sync but its not. I followed this thread here (http://forum.xda-developers.com/showthread.php?t=865685) I made sure i had the platform-tools installed before changing the path. I think this is the problem I am having. There are 2 paths that appear; One in user variables and then one in system variables. I have tried altering both but I am having no luck. Does anyone have any clue to what is going on?
HTC Sync will install the correct USB drivers for your G2. Although you cannot actually *run* HTC Sync with your G2 unless it is running a Sense (Desire Z) ROM. So just install it but don't try to actually run it or sync with it.
It's the System Variables path that you want to change, to add the appropriate directories. This just lets you run adb from any directory on your PC. Even if you haven't got it added, it should still work if you "cd" to the directory where adb resides (in which case you will need to put any files into there that you wish to "push" to your phone).
What is the problem you're having, is it saying "no internal command" or similar ?
DressedUpPanda said:
So I have no idea why my G2 isn't being found with the htc sync but its not. I followed this thread here (http://forum.xda-developers.com/showthread.php?t=865685) I made sure i had the platform-tools installed before changing the path. I think this is the problem I am having. There are 2 paths that appear; One in user variables and then one in system variables. I have tried altering both but I am having no luck. Does anyone have any clue to what is going on?
Click to expand...
Click to collapse
The PATH issue, relates to ADB, if you are running into errors like:
'adb' is not recognized as an internal or external command
Click to expand...
Click to collapse
When executing ADB commands that is your issue, it can be resolved by adding the path where ADB lives to either your user or system PATH in Windows. The PATH is irrelevant if you are running ADB from the folder where the ADB files live.
The other (common) issue is drivers, where ADB is working but won't see your device. Do you see an "ADB Device" or similar with a yellow icon in your device manager when your phone is connected to your PC? If so you don't have the correct driver loaded. The only reason you install HTC Sync is to load this driver but the driver can also be loaded separately.
Sorry to hi-jack this thread, and since I'm new to adb I might as well use this.
I have adb running, did the file paths and everything. I'm just trying to test it out, since I'm already rooted using visionaryr13 as well as s-off. Went back and gfree over that, and I've also verified through terminal emulator on my phone, but I'm just testing my skills with adb and failing miserably. I Have d/l the verify file, and unzipped in a folder inside my downloads folder I might add.
When it says:
"
VERIFY (using "gfree_verify")
Now you can try using a new SIM card to verify that it worked.
In addition you can use gfree_verify to verify the state of your locks.
Download gfree_verify.zip from gfree_verify_v01.zip
ON YOUR PC:
Unzip gfree_verify_v01.zip to a place on your computer. Navigate to where the file is on your computer, and type:
$ adb push gfree_verify /data/local
"
I'm having a problem with the navigate to where the file is on your computer and type. I have cmd open, and have tried everyway but the right way to push this through. This is the error I'm getting.
cannont stat 'gfree_verify': no file or directory
EDIT: I got it and I'm sure everyone is laughing at this idiot. So in the cmd prompt you have to navigate to where you put the folder, then push the file to your phone, DUH!
OK, stupid question number two, since I answered number 1.
When you are in a adb shell in your cmd, how do you get out of it besides exiting cmd?
mrbmg said:
When you are in a adb shell in your cmd, how do you get out of it besides exiting cmd?
Click to expand...
Click to collapse
Type "exit".
ty ty.
Ok so I updated something in adb and it's not working. LOL, well restarted, and now the sdk manager is updating some more stuff so hopefully that is the reason I was not getting in.
EDIT: everything is working now.
Ty stevie, really appreciate all your hard work helping us noobies man!
steviewevie said:
HTC Sync will install the correct USB drivers for your G2. Although you cannot actually *run* HTC Sync with your G2 unless it is running a Sense (Desire Z) ROM. So just install it but don't try to actually run it or sync with it.
It's the System Variables path that you want to change, to add the appropriate directories. This just lets you run adb from any directory on your PC. Even if you haven't got it added, it should still work if you "cd" to the directory where adb resides (in which case you will need to put any files into there that you wish to "push" to your phone).
What is the problem you're having, is it saying "no internal command" or similar ?
Click to expand...
Click to collapse
Ya my problem is that when I finally get to do the commands it tells me that "adb is not recognized as an internal or external command.
@raitchison- I checked my device manager and it says that i have the most current driver for the phone. Unfortunately it doesn't say anything about 'adb' it shows my 'portable devices' then into my 'E:/' drive and in the details there it stats 'Android phone'
DressedUpPanda said:
Ya my problem is that when I finally get to do the commands it tells me that "adb is not recognized as an internal or external command.
@raitchison- I checked my device manager and it says that i have the most current driver for the phone. Unfortunately it doesn't say anything about 'adb' it shows my 'portable devices' then into my 'E:/' drive and in the details there it stats 'Android phone'
Click to expand...
Click to collapse
You just need to add the correct directories onto the end of the path in System Variables. Go right to the end of the path, and then separated by semi-colons (do not put spaces in) add the two pathnames of the tools and platform-tools folder of the Android SDK. If you have done that and it is still not working, copy and paste the path variable up here and we can try checking it.
As I said, you could "cd" to the folder with adb in it, and then run "adb devices" from there, and it should work. But setting up the path will make it more convenient.
steviewevie said:
You just need to add the correct directories onto the end of the path in System Variables. Go right to the end of the path, and then separated by semi-colons (do not put spaces in) add the two pathnames of the tools and platform-tools folder of the Android SDK. If you have done that and it is still not working, copy and paste the path variable up here and we can try checking it.
As I said, you could "cd" to the folder with adb in it, and then run "adb devices" from there, and it should work. But setting up the path will make it more convenient.
Click to expand...
Click to collapse
Ok well here is the path that i have set up.
- C:\AndroidSDK\tools;C:\AndroidSDK\platform-tools
I saved the file right to my "C" drive so thats why i didn't go to the program files. I also changed the name of the folder so it was easier to type.
Edit: I got it to finally recognize my device. I went back to my path and found that i had spaced in between my ';' and 'C:/' so thank you very much Stevie on making me double check it!!!
I cannot figure this out to save my life. I have downloaded and installed HTC Sync. I have the folder for android-sdk setup on my local drive. I added the environmental settings so I don't have to change directories each time.
I connect my phone with USB Debugging enabled, and then open command prompt. I change directories to E:\android-sdk\tools (My "E" drive is my default drive). Anytime I try and "Adb" command, it says that ADB isn't recognized as a command. I don't know why. Cannot figure it out to save my life.
I've attached some pictures so you can get a brief idea as to what I am talking about. I am on Windows 7 32 bit, if that makes any difference.
The first thing I noticed from your screenshot that is that you dont have adb application in your sdk tools folder.
adb has moved...try the platform-tools folder instead of just tools.
*Sigh*
I would miss something as simple as that. It's working now, thank you guys.
Edit:
One more question.. I am trying to install the "com.skype.raider-all-in-one-camwidth". I am assuming I need to use ADB to push it to the system files, but how do I go about doing that from CMD? Probably incredibly simple, but I'm lost again. Lol
dpilcher said:
adb has moved...try the platform-tools folder instead of just tools.
Click to expand...
Click to collapse
I wonder if the adb_has_moved.txt file in his screenshot might have given him a clue?!?
JimSmith94 said:
I wonder if the adb_has_moved.txt file in his screenshot might have given him a clue?!?
Click to expand...
Click to collapse
Lol I admitted it was something stupid to miss, forgive me.
Can anyone help me with the file pushing though? I am trying install that Skype .zip file, and I'm assuming it has to be pushed to the system area. Any clues as to how I go about that?
If you need to get it into system apps,
Adb push filename /system/app
Make sure you put a space between the end of the filename and the /
And make sure the file is located in the platform-tools folder.
I'm able to use adb to connect to the device and reboot into bootloader but every time I try to install a TWRP recovery.img i constantly get the message
C:\Users\David>fastboot boot recovery.img
cannot load 'recovery.img': No error
C:\Users\David>
I can't figure out what it is that I'm doing wrong. Is there a simple issue holding me up? I only bought the gpe for the sole reason of making this a seemless task. At this rate i might as well return this and get a v500.
jerzykid said:
I'm able to use adb to connect to the device and reboot into bootloader but every time I try to install a TWRP recovery.img i constantly get the message
C:\Users\David>fastboot boot recovery.img
cannot load 'recovery.img': No error
C:\Users\David>
I can't figure out what it is that I'm doing wrong. Is there a simple issue holding me up? I only bought the gpe for the sole reason of making this a seemless task. At this rate i might as well return this and get a v500.
Click to expand...
Click to collapse
Which recovery are you trying to install? And, are you in the install directory? Have you unlocked the boot loader first? sorry for all the questions, but you should be answered so we know more detail.
sleekmason said:
Which recovery are you trying to install? And, are you in the install directory? Have you unlocked the boot loader first? sorry for all the questions, but you should be answered so we know more detail.
Click to expand...
Click to collapse
The questions are welcomed.
1)I'm installing in platform-tools folder where adb.exe is located as many posters have suggested. It's located in a folder directly in the C:/ Drive
2)The bootloader was unlocked before i purchased the g pad
3)I'm trying to install TWRP. I tried 3 different versions (including the latest) with the same result.
I've tried the Path under Enviromental Variables that some users suggest. Through some research some have said to put the recovery image directly under the C drive and use cd to change the path until it registers on command prompt. then go through the shell commands. I haven't tried this yet.
jerzykid said:
The questions are welcomed.
1)I'm installing in platform-tools folder where adb.exe is located as many posters have suggested. It's located in a folder directly in the C:/ Drive
2)The bootloader was unlocked before i purchased the g pad
3)I'm trying to install TWRP. I tried 3 different versions (including the latest) with the same result.
I've tried the Path under Enviromental Variables that some users suggest. Through some research some have said to put the recovery image directly under the C drive and use cd to change the path until it registers on command prompt. then go through the shell commands. I haven't tried this yet.
Click to expand...
Click to collapse
I don't know much about windows... Your path is c/users/David . in Linux, the prompt would be opened in platform-tools. It sounds like you you should either have the recovery image in David, or your prompt opened in platform tools. In any case, it sounds as though you are trying to install it from the wrong location. unfortunately, being windows, somebody else may better be suited to help you.
SOLVED
sleekmason said:
I don't know much about windows... Your path is c/users/David . in Linux, the prompt would be opened in platform-tools. It sounds like you you should either have the recovery image in David, or your prompt opened in platform tools. In any case, it sounds as though you are trying to install it from the wrong location. unfortunately, being windows, somebody else may better be suited to help you.
Click to expand...
Click to collapse
so changing the path to the folder containing adb.exe was correct but I had to put the recovery.img directly like many have said. In Windows the command prompt doesn't always default to C:\(or whatever your main drive is called) and you have to manually change this.Most people are fairly fluent with command promt but for those who aren't you must use " cd.. " (without quotes)to change the path to your base directory. i hope this helps anyone else.I've seen others explain it but not detailed enough
When I boot after the update of the rom, unlock pattern shows as 3x3 dots. I'm coming from previous version with 6x6 pattern. System doesn't accept pattern because it's not the same. I can't change pattern grid size, not showing recovery with Google account and I had disabled Google function to find the device for privacy reasons.
ictecnics said:
When I boot after the update of the rom, unlock pattern shows as 3x3 dots. I'm coming from previous version with 6x6 pattern. System doesn't accept pattern because it's not the same. I can't change pattern grid size, not showing recovery with Google account and I had disabled Google function to find the device for privacy reasons.
Click to expand...
Click to collapse
Look here, this might be your solution to bypass the screen lock feature. But for sure you need access to your /data directory.
Uluru25 said:
Look here, this might be your solution to bypass the screen lock feature. But for sure you need access to your /data directory.
Click to expand...
Click to collapse
This is what I don't have: Access to data it shows encrypted folder names.
you can change the screen lock from adb cmd line, you just need to figure out the encoding.
Code:
adb shell locksettings set-pattern --old '17=CIOPQRST' '14789'
https://blog.alxu.ca/unlocking-large-pattern-encryption-in-twrp.html
alecxs said:
you can change the screen lock from adb cmd line, you just need to figure out the encoding.
Code:
adb shell locksettings set-pattern --old '17=CIOPQRST' '14789'
https://blog.alxu.ca/unlocking-large-pattern-encryption-in-twrp.html
Click to expand...
Click to collapse
adb devices shows "device unauthorized" when system has booted so I can't use adb shell. Before the update/pattern problem I tried several times to flash magisk via TWRP, process shows ended succesfully but phone remains unrooted. I've tried to unistall renaming magisk to uninstaller.zip and fails with a message that can't access to data. I don't know if with TWRP I can do anything but I would to flash again previous version of the ROM but it's not downloadable online.
you can authorize adb with a script that runs from overlay.d or from system/etc/init
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
alecxs said:
you can authorize adb with a script that runs from overlay.d or from system/etc/init
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
Click to expand...
Click to collapse
Let me post the message that I have when
When I boot the system and I try adb shell:
* daemon not running; starting now at tcp:5037
* daemon started successfully
error: device unauthorized.
This adb server's $ADB_VENDOR_KEYS is not set
Try 'adb kill-server' if that seems wrong.
Otherwise check for a confirmation dialog on your device.
When I try adb devices (also with system booted):
List of devices attached
1270c2f0 unauthorized
No sure if magisk it's installed properly.
to which partition you have copied RSA key to phone? where did you place the init script?
alecxs said:
to which partition you have copied RSA key to phone? where did you place the init script?
Click to expand...
Click to collapse
I don't know how to do it, I've to read link in the post with calm. I only flashed ROM zip's from recovery and Magisk zip/apk, never modified other things manually like modifiing files with adb shell. I'm discovering a lot of things to do via adb / fastboot due to my problem. I'm a GNU/Linux user but with basic knowledge of system scripts and structure.
use AIK to modify boot.img, you will see if there exist overlay.d directory or not (only if the boot.img is patched with Magisk)
otherwise mount /system(_root) rw and place the script there. I used the /cache partition for the key. It didn't work on my Samsung but there are many ways to authorize adb, it's all written in that thread.
I have moved the off-topic discussion to separate thread.
alecxs said:
use AIK to modify boot.img, you will see if there exist overlay.d directory or not (only if the boot.img is patched with Magisk)
otherwise mount /system(_root) rw and place the script there. I used the /cache partition for the key. It didn't work on my Samsung but there are many ways to authorize adb, it's all written in that thread.
Click to expand...
Click to collapse
Hi
Seems that I have overlay.d directory when unpacked boot.img. I have to put init.adbguard.rc and adbguard.sh in this directory?
According to https://blog.alxu.ca/unlocking-large-pattern-encryption-in-twrp.html and https://github.com/TeamWin/Team-Win-Recovery-Project/issues/1388 I think that my 6x6 pattern was 123456<BHNT but when I try adb shell twrp decrypt '123456<BHNT' I have this warning:
/system/bin/sh: can't open BHNT: No such file or directory
TWRP cannot decrypt, you need to do this in Android. Don't forget the quotes, < is a special char for redirecting files.
ictecnics said:
Hi
Seems that I have overlay.d directory when unpacked boot.img. I have to put init.adbguard.rc and adbguard.sh in this directory?
Click to expand...
Click to collapse
I'm waiting to try this but I don't know if this is the procedure.
alecxs said:
TWRP cannot decrypt, you need to do this in Android. Don't forget the quotes, < is a special char for redirecting files.
Click to expand...
Click to collapse
In Android = system booted I think. Command returned the error with quotes. I tried to put \ before < symbol (also with quotes) and command decrypt in TWRP failed with code 6.
unpack the zip and you have the directory names where the .rc and the .sh file belong to. edit the path in shell script with the location of adb_keys file, if necessary. repack the boot.img, flash it, find your local adbkey.pub, rename it adb_keys and copy to proper location on phone (I used cache partition). if the script is executed successfully, adb_keys will renamed to adb_keys.bak. after second reboot adb is authorized.
alecxs said:
unpack the zip and you have the directory names where the .rc and the .sh file belong to. edit the path in shell script with the location of adb_keys file, if necessary. repack the boot.img, flash it, find your local adbkey.pub, rename it adb_keys and copy to proper location on phone (I used cache partition). if the script is executed successfully, adb_keys will renamed to adb_keys.bak. after second reboot adb is authorized.
Click to expand...
Click to collapse
I checked the directory structure where I extracted the AIK and I only see a sbin subdirectory inside overlay.d. The path is /home/..../AIK-Linux-v3.8-ALL/AIK-Linux. Once "unpackimg.sh" is run, "ramdisk" and "split_img" directories are created. Inside "ramdisk" there is only "overlay.d", ".backup" and the "init" file, inside "split_img" only files. About the adbkey.pub file so far I have only located an "adbkey" file (without .pub) inside /home/.../.android and the first line says "-----BEGIN PRIVATE KEY---- -". I honestly don't know what to put or where
ramdisk/overlay.d is the right directory for the .rc file, and the .sh file should placed ramdisk/overlay.d/sbin. I meant this zip I have linked two days ago, you obviously didn't read that thread:
alecxs said:
you can authorize adb with a script that runs from overlay.d or from system/etc/init
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
Click to expand...
Click to collapse
if there is no adbkey.pub file in ~/.android directory, run adb with another phone so a file is created.
alecxs said:
ramdisk/overlay.d is the right directory for the .rc file, and the .sh file should placed ramdisk/overlay.d/sbin. I meant this zip I have linked two days ago, you obviously didn't read that thread:
if there is no adbkey.pub file in ~/.android directory, run adb with another phone so a file is created.
Click to expand...
Click to collapse
I connected another phone, enabled OEM debugging and OEM unlock and no adbkey.pub is created in ~/.android, it shows the same files as before: adb.5037 and adbkey. Ran adb shell, connected to other phone, no file created.