Related
I've followed the instructions to a T on the wiki but I'm having a few problems. I had to downgrade to RC29 and then put "recovery.img" and the HardSPL "update.zip" on the root of the memory card. I even finished with the telnet commands (which didn't seem to do anything) and flashed JesusFreke's 1.5 crb43. Now when I try to use the Terminal Emulator for abd commands I get a permissions error. In addition, nothing shows up in my Superuser Permission application leading me to believe that I may not have rooted properly.
Any help would be greatly appreciated.
I forgot to mention that I cheated and I don't know if that was a problem. I started with crb43 and used the old exploit to downgrade to rc29 (format sd card, copy rc29 update.zip to root of card, enter bootloader mode and flash).
SharpieMarker said:
I've followed the instructions to a T on the wiki but I'm having a few problems. I had to downgrade to RC29 and then put "recovery.img" and the HardSPL "update.zip" on the root of the memory card. I even finished with the telnet commands (which didn't seem to do anything) and flashed JesusFreke's 1.5 crb43. Now when I try to use the Terminal Emulator for abd commands I get a permissions error. In addition, nothing shows up in my Superuser Permission application leading me to believe that I may not have rooted properly.
Any help would be greatly appreciated.
Click to expand...
Click to collapse
You should be using adb for terminal commands. If you type 'adb' in the terminal you will get nothing.
Go to terminal emulator and type 'su'
if it brings up the permission screen press 'allow'
if your command line changed from '$' to '#' then you have successfully rooted.
There shouldn't be anything in superuser permissions if you haven't given any apps permissions (every app is considered a different user)
Hope this helps, but this seems like a thread that would be better suited to the Q&A or Dream topics since this is the Development section not general questions...just thought I'd mention it.
Just AIM me: Breakthecycle2
Breakthecycle2 said:
Just AIM me: Breakthecycle2
Click to expand...
Click to collapse
I can't use AIM at work. I am better reached at [email protected]
I think that worked. su brought up permissions window and when I select allow I now have root. Brilliant. Thanks very much for the assistance.
EDIT:
Oops
Then what am I missing about this? I'm attempting to replace these files to increase my maximum volume and I'm unable to use any of the adb commands, even with root.
adb remount
- wait for the 'remount succeeded' message
adb push Desktop/AudioFilter.csv system/etc
adb push Desktop/AudioPara4.csv system/etc
adb push Desktop/AudioPara4_TMUS.csv system/etc - Optional
SharpieMarker said:
Then what am I missing about this? I'm attempting to replace these files to increase my maximum volume and I'm unable to use any of the adb commands, even with root.
adb remount
- wait for the 'remount succeeded' message
adb push Desktop/AudioFilter.csv system/etc
adb push Desktop/AudioPara4.csv system/etc
adb push Desktop/AudioPara4_TMUS.csv system/etc - Optional
Click to expand...
Click to collapse
adb is the Android Device Bridge that allows you to interface your G1/Magic with an x86 Windows system. It is included in the Android Developer Toolkit.
You need windows and to have your G1 connected to your computer. There are a few really good threads giving step by step walkthroughs on setting it up correctly, just use the search.
ADB for Dummies
ADB for Dummies
ADB can't be used from terminal emulator on the phone...you have to use it from your windows command prompt...read up on ADB first.
Whenever I try to run adb from terminal, or drag the adb tool into the terminal window and do adb devices, it says permission denied?
How do i go around this?
I have usb debugging enabled
I am trying to figure out how to use adb on osx and i am having trouble.
edit: figured it out. When draggin the adb into terminal you need to add a command to it
Not wanting to bump really old threads but I've just written a guide on how to run ADB from Terminal as you would in Windows etc.
Have a look!
http://forum.xda-developers.com/showthread.php?p=9842005
I'm not sure that this belongs here but...
I was ciurious to know if anyone has tried to download and use Android SDK and Flashing files (Fastboot, ADB etc.) from a USB flash drive?
Or in my case I would like to use one of my old 8GB microSD cards as a mobile flash toolbox so i could flash on the go when I'm away from home. On another computer?
Sure you can, you either need to navigate to the folder that has the ADB and Fastboot files stored in before you can execute and ADB or Fastboot commands at the same time in order to use the ADB or Fastboot commands to install, push, copy, remove or anything you must place the file that you want to copy, push, or move into the same folder that ADB or Fastboot is in.
Cool
I just want to run a couple of 'setprop' commands to enable cam2api and eis.
To install twrp, we need oem unlock, of course. Once installed, would I be able to connect via usb and run 'adb root', to then do the setprop commands?
I'm just trying to keep it simple, enable cam2api and eis, and go back to stock, if possible.
Sound do able?
Actually, now that I think about it, maybe twrp isn't needed at all for 'adb root'? Maybe just unlock bootloader, device resets, enable dev and adb, connect usb and then 'adb root'?
without oem unlock (iow, as it is now); 'adb root' returns 'adbd cannot run as root in production builds'. But with oem unlock then it may work?
AsItLies said:
I just want to run a couple of 'setprop' commands to enable cam2api and eis.
To install twrp, we need oem unlock, of course. Once installed, would I be able to connect via usb and run 'adb root', to then do the setprop commands?
I'm just trying to keep it simple, enable cam2api and eis, and go back to stock, if possible.
Sound do able?
Click to expand...
Click to collapse
You do not need twrp. You need root access. Even then you cannot just run "adb root" because debugging and secure flags in the default.prop (which is compiled into vendor and boot images) disable that exact command. I was able to find a workaround though. You still need root (systemless should allow ota updates so don't worry about that) but in place of "adb root" run the following.
adb shell
su
mount -o rw,remount -t ext4 /system
exit
This will do the same thing, just through adb shell instead of straight adb.
If you really want to go stock, (no root) you can root the device and download a build prop editor (tons of them on the play store) edit the values you want, then unroot by flashing the stock boot.img. Just keep your bootloader unlocked. You're welcome!
For those following along on this adventure
One thing you can do now, if you haven't already, is be sure you have the (one of the) recent versions of fastboot installed. Older versions don't recognize multiple 'slots' (The A & B slots on the MiA2). The following link has the packages for Linux, Windoh's, and Mac.
To test your fastboot just use 'fastboot -h' and you'll want to see options like '--slot' and '--set-active[=SLOT]. If you have that already, at least this part is accomplished, if not, need to update your fastboot.
https://developer.android.com/studio/releases/platform-tools
Great info @Daha3ker - looking for a simple systemless root now. Trying to keep it all as simple as possible
AsItLies said:
For those following along on this adventure
One thing you can do now, if you haven't already, is be sure you have the (one of the) recent versions of fastboot installed. Older versions don't recognize multiple 'slots' (The A & B slots on the MiA2). The following link has the packages for Linux, Windoh's, and Mac.
To test your fastboot just use 'fastboot -h' and you'll want to see options like '--slot' and '--set-active[=SLOT]. If you have that already, at least this part is accomplished, if not, need to update your fastboot.
https://developer.android.com/studio/releases/platform-tools
Great info @Daha3ker - looking for a simple systemless root now. Trying to keep it all as simple as possible
Click to expand...
Click to collapse
My tool installs systemless and removes it. If you choose root, do what you need to do, then unroot you should be good. The toolkit is about as simple as it gets right now when it comes to rooting.
https://forum.xda-developers.com/mi-a2/how-to/mi-a2-toolkit-unlock-bootloader-root-t3834585
Otherwise you can use https://forum.xda-developers.com/mi-a2/how-to/guide-how-to-root-xiaomi-mi-a2-magisk-t3831586
root your phone, do what you like then follow the same steps to flash the stock boot.img instead of the rooted version.
P.S. All root options available right now are systemless unless you install a custom rom.
P.P.S. Setprop commands are used systemlessly (Applied at boot using magisk). so if you unroot, your custom values will not stay. You must edit the actual build.prop
A set of steps to try:
1. Root the device. Toolkit or Manually
2. Install https://play.google.com/store/apps/details?id=com.jrummy.apps.build.prop.editor&hl=en_US or similar on your phone.
3. Add the following to the end of the build.prop
persist.camera.HAL3.enabled=1
4. reboot phone and verify it is enabled using https://play.google.com/store/apps/details?id=com.airbeat.device.inspector or similar. If level 3 is green then you are good, if not then I may be missing another value that needs changing.
5. unroot the device using the same method you used earlier to root the device. Toolkit or Manually
6. reboot and see if the settings stuck. I am curious to see if it works..
I'm hoping to pull an image of my decrypted /data partition in order to hopefully recover some deleted files via sophisticated recovery software on the PC side of things. I manage to pull an image just fine, but it ends up being encrypted when adb is done pulling it.
From what I can gather doing a lot of google searches when you decrypt in TWRP you're supposed to get a new apparent mount/partition visible under /dev/block or thereabouts. Called "dm-0" on a lot of other phones it seems, but I don't get one of those. Decrypting directly on the phone or via adb works just fine and I can access my /data partition via the shell w/o issues.
However this still ends up being encrypted after pulling it. Is there a way to actually create and pull a decrypted image of said partition this way or am I way off? I need help finding said decrypted and supposed mount point/partition. Can't see anything new under /dev/block or as far as those directories goes so I'm at a loss.
Using:
XZ1 Compact
Android 9
TWRP 3.6.1_9-0
Latest adb from android sdk platform tools as of this writing.
Hmm. Have you tried pulling it while the phone is in recovery? If you are rooted, before pulling have you tried giving root to adb?
adb shell
su
Yes that's what I'm trying to do in order to get a decrypted image. Did not try pulling the image as root. You think that could make a difference?
EDIT: Hold on though. From the shell you can't send adb commands? I.E. opening the terminal with adb shell you have no access to adb?
knerlington said:
Hold on though. From the shell you can't send adb commands? I.E. opening the terminal with adb shell you have no access to adb?
Click to expand...
Click to collapse
adb root
adb remount
Now you're back to adb. Not sure if it will make a difference in this case, but worth a shot.
Also, you could try making a copy of the patrition via TWRP > Advanced > File manager and transferring it to PC regularly from explorer.
I have no problems making an image of said partition in different ways, but the problem is that everything that I need access to from the image file is encrypted despite making the image from twrp after decrypting it.
I'm trying to restore and recover deleted files from this partition, but in order to do that I need an image that I can use in more sophisticated recovery programs.
So is this possible at all or is there a way to decrypt an encrypted image somehow?