Related
The purpose of this document is to clarify a few basics about HTC Android Phones and basic commands to interface with the phones. Think of this as a beginner's guides to the Android device from a non-traditional user's point of view. I'll keep it simple and plain as much as I can for the new users. I'll also try to keep all the technical aspects true as much as I can while keeping it simple.
Before you go on, please read this and understand the basic concepts and how and why following commands are being used. Do not follow anyone's instructions/tutorials/guides without prior basic understanding of what each command do. I do want to believe it's humans visiting this forum and not lemmings. If you do not understand, feel free to ask here. I will or someone else also knowledgeable will answer your questions. DO NOT QUOTE THIS AS A WHOLE. My pet peeves and a complete waste of screen space.
Sometime, depending on your OS, command names may change (e.g: mouse / mouse.exe / mouse-linux / mouse-mac). For general purpose, we'll use mouse instead of an OS specific commands in this instructions.
So to repeat myself, if you understood the concepts of the commands, and you are on a linux system and someone's guide says touch index.php, you will automatically type touch-linux or whatever the name of your executable is on your system.
We shall assume you know how to install needed drivers and where to get android sdk and put the sdk binaries (executables) in the system path. If we need to expend this let me know and I'll expend this here.
Further, if I get any parts wrong, PM me and I'll get those parts corrected.
Android Partition, SPL etc.
Partitions:
Followings are a list of partitions on your android phone.
misc - misc partition -
recovery - Recovery Partition - This is where the original HTC recovery or Amon Ra's recovery or any other Recovery would go. Basically if you reboot into recovery it'll boot from here.
boot - This is your boot partition
system - This is where all your system information (ROM resides)
cache - cache (When you factory reset the phone, this area is wiped)
userdata - user data (like your login, your user settings etc) When you factory reset the phone, this area is wiped)
So, if you replace the recovery image, you are pretty much set for updates provided here at XDA. Note: By replacing your recovery image, you may not be able to have OTA updates.
ROM images will normally replace boot and system images at the same time and often time, userdata and cache too; reseting the phone completely.
SPL/Bootloader/Radio/Bricking Phones:
SPL / Bootloader is like BIOS on a computer. At least I think of it that way. SPL can be updated! SPL comes as either Security-On of Security-Off (S-ON/S-OFF).
Note: It is my understanding that radio will boot first, followed by other systems. So it is IMPORTANT that your radio image/version will work with your SPL image/version. This is the one and only reason for phones being bricked. You can not brick your phone by flashing a ROM or Boot image or recovery image. Once you flash the wrong radio for the SPL, the only known method of recovery is to send the phone back into HTC for repair.
How do I know the phone is bricked? A bricked phone can not boot into bootloader, recovery, or into normal operation modes. You can not connect to a bricked phone via adb or fastboot. You can only see one screen on the phone and it will be the first splash screen.
Commands:
adb - Android Debug Bridge - One of the two things you'll need to know if you ever want to do anything non-conventional on your android based phone.
List of commands that can be used by adb can be prompted by typing adb at the system shell (command prompt or terminal)
Notable adb commands:
adb devices - If you don't know anything, this is the ONE thing you have to know.
adb devices will give you a list of devices connected to the computer. This is also a good way to make sure that your phone is actually connected to the computer.
adb reboot (bootloader|recovery)
adb reboot - this will reboot your phone normally.
adb reboot bootloader - this will reboot your phone back into the bootloader (white screen with the android on wheels)
adb reboot recovery - this will reboot your phone back into recovery console (either default or amon_ra's recovery).
adb shell - this will shell into the phone and you can now explore the phone. Remember phone's native backend os is linux so know your linux commands.
adb remount - remounts the system partition on the phone so you can you read/write to it.
adb push xxx yyy - will push xxx file from computer into yyy location/file on phone (needs rooted access)
adb pull xxx yyy - will pull xxx file from phone into yyy location/file on computer (needs rooted access)
Fastboot is protocol used to update the flash filesystem in Android devices from a host over USB. It allows flashing of unsigned partition images.
Notable fastboot commands:
fastboot devices - If you don't know anything, this is the ONE thing you have to know.
fastboot devices will give you a list of devices connected to the computer. This is also a good way to make sure that your phone is actually connected to the computer.
fastboot reboot - this will reboot your phone normally
fastboot oem unlock - this will unlock your bootloader - NOTE THIS WILL VOID YOUR NEXUS ONE WARRANTY
fastboot erase XXX - Will erase the partition XXX (such as userdata, cache) - mainly used for resetting phone and clearing userdata / factory settings.
fastboot flash XXX YYY - This will flash XXX partitionn with YYY image.
e.g: fastboot flash system system_update.img will flash/update your system partition with an image called system_update
If anyone needs me to dig deep into using anything else, please PM me. I'll add it on here. Hopefully this will help all newbies about the basic commands and what they do.
FAQs (UPDATED Feb 09, 2010)
Q: One question about the Android SDK. Do I need it to flash my N1 or just to program new apps? Where can I get it?
A: Android SDK is not entirely needed to flash the N1. However, there are tools in there that you need. Adb / Fastboot etc. Although they can be downloaded by themselves, the windows version of the SDK also have the Drivers that are needed for android devices for USB connection. So, it is recommended to get it. You can get it from developer.android.com
Q:I have never experienced anything like this when I did a hard-spl on my winmo phone. Radio versions are included with SPL's, right?
A: Official packages from HTC did come with nbh packaging, meaning it is a all in one upgrader that will update Radio, ROM, System etc, it is very much common for active development area here at XDA to get the radio or SPL or ROM separately and independently of one another. And as such, you will most likely flash them seperately (who wants to wait 6-8 months). Also, since this phone is released by google, HTC will most likely not update any major Radios. However, it is very likely that we will be hacking in Radio updates or any other "updates" from HTC from their new device - HTC Bravo.
Q: Is there a guide for snow leopard? I'm kind of stuck.
A: I personally ran android SDK and aforementioned executable on both MAC OS 10.5 and 10.6. Like I posted, the commands and the executable names may be slightly different. I may call adb and you may find it as adb-mac. I am not going to write 3 separate documents for 3 separate OSes. You have to know that adb=adb-mac (on your mac), adb-linux (for linux) etc. And yes the above guide will work universally.
Q: Can i replace the splash image..?? (unlocking related)
A: As of the above date (next to the FAQ) no you can not. Issue is probably a few folds. One of them is that splash1.img is not going in due to security lock. Remember, you unlocked the phone. HTC will not like it. Anyhow, I like the current quad color X. If you are thinking of getting rid of the lock logo, good luck. Even if you can get rid of it, you will still have to overcome the pink text that says ***UNLOCKED*** on your bootloader.
Q: Can you run Windows Mobile on Android Phones?
A: With enough resources given, sure. Will it ever happen? No. Why? Windows mobile compiler and builder cost $. As a matter of fact, as of version 5, it was going to cost me $75 per device. That's one of the reasons why handset makers went to Android open platform. Android is free and universal so as long as you use certain chipsets and certain items, you are good to go. Can it ever be ported? Sure. With right amount of time and money anything can be done. But at this point, it's cheaper for you to go buy a windows mobile smartphone.
Q: How do I know the phone is bricked?
A: You can not brick a phone unless you are flashing Radio/SPL packages. Make sure if you are doing that, you follow directions VERY CAREFULLY. A bricked phone can not boot into bootloader, recovery, or into normal operation modes. You can not connect to a bricked phone via adb or fastboot. You can only see one screen on the phone and it will be the first splash screen.
Q: I have installed the Android SDK however, i cannot seem to get the laptop to detect the nexus. What have i left out?
A: Most common item that people forget to enable is USB Debugging. Settings => Applications => Development => USB debugging [checked]
Q: I have rooted n1. when I go to recovery to do backup, I get the triangle with the little green android guy, but phone is stuck there. I have to remove battery to reboot phone. What have I done wrong?
A: You still have the stock (shipping) recovery. If you want a different recovery (Amon RA's), download it, the from fastboot, run fastboot flash recovery downloaded_recovery.img
Q: Which step of the rooting / recovery procedure does it give root?
A: Root and Recovery are two totally different things. Recovery is a partition that contain recovery information. Stock recovery is what allows OTA updates etc. Normally it will search for update.zip in the root folder of the SD card. Amon_RA's Recovery or any other recovery images are there to enhance the traditional stock recovery. Amon Ra's Recovery for example, contains thing such as ability to update from different zip files, and backup/restore of your data/system.
Rooting is not done by recovery but is a kernel level access (simply put) that will give root or "SU". It is done by patching the boot partition of the your android device.
Q: What are the differences, advantages, disadvantages of the different ROM's?
A: They are all different. Some have some features, some are plain stock, some are made for bleeding edge kernel etc. You'll have to try them out and figure out yourself. I may make a chart of what they are (see the bottom at my signature - wiki) but with too many android devices, I will need some major help. One person alone will not have total knowledge of all the ROM releases. There are just way too many devices and ROMs.
Q: Which ROM will allow OTA updates?
A: Stock ROM WITH Stock Recovery.
Q: If the phone is SIM/carrier unlocked and you root do you have to SIM unlock again?
A: SIM/Carrier unlock has nothing to do with rooting your phone. You can still have root and still be carrier locked. Nexus One comes carrier unlocked from factory.
Q: How much space is there for apps? is using the sd card really necessary? (on Nexus One)
A: Search google? The phone has 512MB or space. That SHOULD be more than enough for you. If not, you have some serious issues. I do not believe you will not App2SD for Nexus One. Google did say during the release conference that they will update Android/N1 so that apps can be run/installed to SD but that requires some system and security changes (mainly to prevent pirated software - Yes if I write something, I deserve to get paid for it).
Q: When you do "flash zip from sdcard" or "fastboot flash image" does this merge and overwrite the files in to the partition?
A: When you update a software (via recovery), software my be merged. However, if you fastboot flash, just like the word flash says, it will flash and overwrite the partition.
Q: Which partition does "flash zip from sdcard" affect?
A: Depends on what you are flashing. It could be any or all of the partitions such as SPL, Boot, System, Recovery, Radio. You should study first before randomly flashing things.
sorry, got it!
blakestimac said:
i apologize if this is the wrong place for this but, but i have adb setup perfectly, but fastboot is not recognized at all. could i have missed something?
Click to expand...
Click to collapse
I need your system info.
What os are you running? where did you get fastboot? what are you trying to do?
Don't forget fastboot boot for testing images. My most used command
I still have no idea how to use or setup adb i have downloaded the sdk and used fastboot and superboot to root my phone and am currently running the cm 5.0 beta 2 rom and want to learn how to use adb so i can enable the ram. Thanks, Joe
really a noob question here.....it wa easier with Hero.
i have installed the Android SDK
however, i cannot seem to get the laptop to detect the nexus.
what have i left out?
wishmaker738 said:
really a noob question here.....it wa easier with Hero.
i have installed the Android SDK
however, i cannot seem to get the laptop to detect the nexus.
what have i left out?
Click to expand...
Click to collapse
Check the FAQ.
dylanfan424 said:
I still have no idea how to use or setup adb i have downloaded the sdk and used fastboot and superboot to root my phone and am currently running the cm 5.0 beta 2 rom and want to learn how to use adb so i can enable the ram. Thanks, Joe
Click to expand...
Click to collapse
Ok. I need to know what you actually did. I am not understanding what you are trying to do.
Can't run adb commands - device not found
Thanks for the info. I am having an issue with running adb commands. My phone is rooted via superboot and I tested it with Nexus Torch which works. Now I am trying to install the new kernel so I can run the wireless tether app... but I can't get any of the adb commands to recognize the phone. I boot the phone by holding the trackball and power button. I am in USB debugging mode. When I run fastboot devices, the phone serial number shows up. When I run adb devices, it says no device detected. And when I try to run any other adb commands they do not work, even though fastboot commands work. Any ideas? Thanks.
Sorry i was pretty vague before i down loaded the sdk and also installed the adb setup file included with the superboot pack but just have no idea how to get it to work and add things through adb. I tried typing adb commands into comand line with the phone connected to the computer but nothing happend. just said not recognised command so i just basically need a rundown of how to setup adb.
dylanfan424 said:
Sorry i was pretty vague before i down loaded the sdk and also installed the adb setup file included with the superboot pack but just have no idea how to get it to work and add things through adb. I tried typing adb commands into comand line with the phone connected to the computer but nothing happend. just said not recognised command so i just basically need a rundown of how to setup adb.
Click to expand...
Click to collapse
I'm a noob so can't offer much help...but I would make sure the usb drivers are installed if you're using windows....this probably should have happened when you installed the sdk, but you can also install it through the device manager and point it to the folder where the usb drivers are located. Also make sure the phone is in USB debugging mode. also you may need to reboot your pc. Make sure you have setup running when you run the adb commands. you need to be in the same directory as the adb file, or in the case of the superboot pack you need to type "adb-windows" not just "adb". you may also need to put .exe, ie adb-windows.exe.
pwnvds said:
Thanks for the info. I am having an issue with running adb commands. My phone is rooted via superboot and I tested it with Nexus Torch which works. Now I am trying to install the new kernel so I can run the wireless tether app... but I can't get any of the adb commands to recognize the phone. I boot the phone by holding the trackball and power button. I am in USB debugging mode. When I run fastboot devices, the phone serial number shows up. When I run adb devices, it says no device detected. And when I try to run any other adb commands they do not work, even though fastboot commands work. Any ideas? Thanks.
Click to expand...
Click to collapse
You run fastboot from the white screen. Android on non-white screen. It's one or the other. It's ADB or Fastboot (depending on the mode of the phone).
dylanfan424 said:
Sorry i was pretty vague before i down loaded the sdk and also installed the adb setup file included with the superboot pack but just have no idea how to get it to work and add things through adb. I tried typing adb commands into comand line with the phone connected to the computer but nothing happend. just said not recognised command so i just basically need a rundown of how to setup adb.
Click to expand...
Click to collapse
Is the directory where ADB/fastboot (SDK) is installled in your system path?
I am guessing it's not. If it was, just by typing adb alone (without commands), it'll give you a list of commands. Click here if you want to know how to change your system path to include a particular folder.
We're now in the age of nintendo pilots and point and click OS that no one knows how to use command lines and system paths anymore.
recovery
I have rooted n1. when I go to recovery to do backup, I get the triangle with the little green android guy, but phone is stuck there. I have to remove battery to reboot phone. What have I done wrong?
umplarry said:
I have rooted n1. when I go to recovery to do backup, I get the triangle with the little green android guy, but phone is stuck there. I have to remove battery to reboot phone. What have I done wrong?
Click to expand...
Click to collapse
Answered in FAQ area.
seraph1024 said:
Answered in FAQ area.
Click to expand...
Click to collapse
I tried that before I posted. I searched the FAQ again. Maybe I am a complete DA, but still can't find answer. I don't mind searching, it will help me to learn, but could you point me in the right direction in FAQ?
umplarry said:
I tried that before I posted. I searched the FAQ again. Maybe I am a complete DA, but still can't find answer. I don't mind searching, it will help me to learn, but could you point me in the right direction in FAQ?
Click to expand...
Click to collapse
Q: I have rooted n1. when I go to recovery to do backup, I get the triangle with the little green android guy, but phone is stuck there. I have to remove battery to reboot phone. What have I done wrong?
A: You still have the stock (shipping) recovery. If you want a different recovery (Amon RA's), download it, the from fastboot, run fastboot flash recovery downloaded_recovery.img
Click to expand...
Click to collapse
There you go.
seraph1024 said:
There you go.
[/B]
Click to expand...
Click to collapse
Thanks for your help
seraph1024 said:
There you go.
[/B]
Click to expand...
Click to collapse
I had it downloaded, just had not flashed it
I've been looking all over, but I probably need to check the HTC Dream forum or something.
How do I install a custom ROM? I know you have to adb push update.zip somewhere, but I can't find any info about this. Please help.
Hey all,
I woke up today to see that my phone was locked up. I removed the battery and let it reboot, it goes back to the lock screen I have, shows the time/cell status.
And then it immediately locks up.
I'm able to get it into recovery mode and I wiped the cache, but no dice. I don't want to reset the data because I have some important sms messages that I'd like to back up, but I can't access the data folder in recovery mode it seems.
Is there a way to backup the data folder in recovery mode? Or another way to get the phone to not freeze on startup? I'm assuming something just got corrupt.
I am able to connect to it via ADB in recovery mode just fine, but can't pull my data directory or use the su commands (permission denied).
FYI: Phone is stock, except I did root it.
Bounty: $20 to anybody's paypal account if their advice helps me recover data.
Stock firmware but rooted rigjt? Man this might be a tuff one.
When u tried to get the files did you use adb pull command?
smokestack76 said:
When u tried to get the files did you use adb pull command?
Click to expand...
Click to collapse
Code:
C:\Programming\Android\tools>adb pull "/data/data/com.android.providers/telephony/databases/mmssms.db" "C:\Programming\Android\mmssms.db"
remote object '/data/data/com.android.providers/telephony/databases/mmssms.db' does not exist
I do have busybox on the phone, but still, I need to get root somehow. I don't even know how I can push an update.zip to the sdcard.
I was forced to reflash a stock phone over this issue, and lost the messages.
Tried to get back at them with dd of the internal data storage, had some messages I composed and emails, but nothing else.
Damn.
hi there,
after unlocking the phone I missed to see that all data would be lost. Obviously the ROM was set back to factory.
Two applications I found to recover the data:
1. 7-Data Android Recovery (can't even find the phone)
2. Android Data Recovery (finds the phone, phone tells me that superuser rights are granted everything ok, but then: "unable to get device storage information")
I would love to recover some data like photos, applications or contacts, before flashing another ROM.
ADB Drivers, fastboot etc is installed. Motorola Device Manager is installed. All Drivers have been successfully placed.
The Phone work works properly when plugged to PC and also USB Debugging is enabled.
Why do my data recovery programs don't access the phone?
TeamWin Recovery 2.7 has been installed, furnice Kernel 1.1.2 as well as SuperSU 2.4. has been installed.
maybe those are impedient`?
nordcupp_motoG said:
I would love to recover some data like photos, applications or contacts, before flashing another ROM.
Click to expand...
Click to collapse
Unlocking the phone will perform a factory reset. That means, everything that does not reside in your external sdcard is permanently lost.
If your device is properly set up with a google account, all your contacts, bookmarks,emails etc. will be restored. That means that everything you can access with your browser, like email, Chrome-bookmarks, are in sync with your device. If you allow google to backup your settings it will also try to restore your apps, but this is, and was, very unreliable.
If you must, you can manually backup your contacts with Contacts Backup Ultimate.
As for applications, nothing beats Titanium Backup. Ugly as hell but the most powerfull backup solution there is.
And last but not least, copy your photos, music, movies etc to your external sdcard.
All this has of course to be done before whiping your device.
P.S. Please update your recovery to the latest TWRP.
external sd may follow soon.
team win recovery that version is offically compatible to moto G14
so I chose that one.
thanks for the tipp. should have seen that earlier.
darryer said:
Titanium Backup is a good tool for Android. Or you can use Tenorshare This is a pro tool for Android data, it can recover all lost data like contacts, sms, call history, photos etc, even you have no backup.
Click to expand...
Click to collapse
I did use that tool as well as 7-Data Recovery and another one. None of them capable to access the phone.
Tenoshore told me after connecting the phone to the app and choosing what data to save, that the storage information is not accessible.
No clue as to how that happens.
nordcupp_motoG said:
No clue as to how that happens.
Click to expand...
Click to collapse
If you connect your device with usb-debugging enabled in the developer options, does a dialog pop up, presenting a RSA fingerprint, asking to allow usb-debugging? Allowing this is imperative.
that was done properly... the application does ask for this before you can chose what to save.
nordcupp_motoG said:
that was done properly... the application does ask for this before you can chose what to save.
Click to expand...
Click to collapse
What is the output of "adb devices" after you connect your device?
C:\adb>adb devices
adb server is out of date. killing...
* daemon started successfully *
List of devices attached
ZX1D22HLNC unauthorized
C:\adb>
but usb tunnel is working right now...
usb debugging is enabled...
adb should be up to date...
mmmh every try delivers different ansers:
second time said: devices attached.
third time said: daemon failed to start
and adb server didnt ack
ok, there is a well known issue with some devices and adb
there is an adb fix for it, but I couldn't get it to work so far.
nordcupp_motoG said:
C:\adb>adb devices
adb server is out of date. killing...
* daemon started successfully *
List of devices attached
ZX1D22HLNC unauthorized
Click to expand...
Click to collapse
Maybe this helps
http://stackoverflow.com/questions/18011685/cant-connect-nexus-4-to-adb-unauthorized
thank you.
I installed the Android SDK Studio and used the ADB from there.
ADB now works properly.
USB Tunnel sucks hard still though.
The connection shows up to be established and skype and whats app do work,
but playstore and chrome refuse to work also no regular app can reach the net
like wikidroyd & co...
nordcupp_motoG said:
playstore and chrome refuse to work also no regular app can reach the net
Click to expand...
Click to collapse
Maybe manually change dns in wifi settings will help.
manually change it where?
I don't see any menu for this in usb tunnel...
guess I gonna get a USB wifi next week.
nordcupp_motoG said:
manually change it where?
I don't see any menu for this in usb tunnel...
guess I gonna get a USB wifi next week.
Click to expand...
Click to collapse
Not on the mobile, on your pc. Change it to e.g. 8.8.8.8
Hello guys,
I tried to gain a root access yesterday on a Samsung Galaxy A510F and got it locked with a red FRP message.
Why did I want to gain a root access?
There was a text message deleted in the phone and I wanted to recover it for a police investigation (early stage, police don't want to ask carrier for data at the moment).
So, I read on stackoverflow that it was possible to get data from file '/data/data/com.android.providers.telephony/databases/mmssms.db' and read it via sqlite client, post title (sorry, can't send links):
backup-full-sms-mms-contents-via-adb
I managed to root the phone by midnight, root access was OK, I could do adb shell and su command and, for example, cat device information from some file in /system/ directory.
Next day, I could not get the device authorised in adb. When I started adb server, I got device list with the phone but unauthorised. So, advices were to revoke usb debug devices, remove files from `~/.android/`, re-enable usb debug option and so on. It didn't work.
I noticed that WiFi was turned on but disabled from switching it on or off, in grey.
So I restarted the phone and it got bricked, with FRP message.
I see that solution is to flash the phone with stock firmware but in this case I feel that this might delete all data from phone, including mmssms.db file.
Am I right? I see on youtube how-tos that there is system.img flashed in Odin and later on a fresh Android is starting...
Is it possible to get the phone up and running but with the mmssms.db file untouched?
Hello:
I've had my Moto X4 in service for over 4 years now...long past due for an upgrade. I've finally gone and done it, and have transferred my active service to my new phone.
I was using Google's backup service, which supposedly will sync wifi passwords over, but it did not work (not surprised). My research indicates I need to root my phone to gain access to /etc/wpa_supplicant.conf (a file I'm familiar with on linux).
So, now that I'm not using this phone anymore, all I am trying to do is get the last vestiges of data off of it before it gets wiped and possibly pressed into "retirement service" (eg, wifi smart device interface, child's play phone, etc).
I found many guides to rooting the X4, but they all say you will loose all your data first...That is counter-productive in this case, as the only reason I am rooting is to get a good backup.
Is there a solution to my issue (currently non-rooted, need to retrieve my very long list of saved wifi passwords accumulated over 4 years as an IT tech at hundreds of businesses.....)?
Thanks!
--Jim
If you go to your saved networks, you can click on any Wifi/SSID name and then press the "Share" button (usually with a QR Code icon). Next, take a screenshot of this code. By using a simple QR Code scanner to scan these QR Codes, the details of the codes will be converted to text. From there, you can clearly see the SSID and password of the network.
You can either painstakingly extract these details (for say, if you need them on a PC etc.), or click on the QR Code icon next to the add network button (recommended), and then scan these images on your other phone, adding them to its list of saved networks.
Note: This feature isn't in every phone, and I believe it's only in android 9/10+ (cannot confirm though)
Yep, not available on this phone (moto X4), unfortunately. I've been missing this repeatedly
This is Android version 9, Google Fi version. Is there somewhere I need to go to turn this on?
I think it comes as a built-in feature. It's included in AOSP android 10+ (confirmed), but some manufacturers, cough cough oneplus cough cough, choose not to add it.
Unfortunately, all other methods of recovery (including apps) seem to require root.
You could try to use the adb pull command to extract the file your looking for from your phone and paste in onto your pc, but I don't have enough knowledge regarding it to guide you on that. It doesn't require root though.
Before you try the adb pull option (as its a bit lengthy and could be difficult for some), try to root your phone using KingoRoot (not to be confused with KingRoot). Try its one-click root app first. It may fail multiple times, but after a couple of tries it should work. If it does work, it won't wipe your data, which is why I'm recommending it.
Unfortunately, Kingoroot apk fails at 90% each time, with error code 0x11DD99. It recommends me try the pc app, which it appears all downloads for it are down/broke, so I haven't been able to get it.
Any more suggestions?
adb pull?
you'll need to look up how it works and its syntax, but it should be able to copy files from your phone onto your pc.
you can also copy files from your pc onto your phone using adb push
i cant really guide you on this as ive only done it once, and that was a really long time ago
To get access to root data, you need root access...
I guess you can root your stock rom without erasing data.
Boot to twrp
Sideload magisk
Finway said:
To get access to root data, you need root access...
I guess you can root your stock rom without erasing data.
Boot to twrp
Sideload magisk
Click to expand...
Click to collapse
He can't get into TWRP without unlocking though..?
Finway said:
To get access to root data, you need root access...
I guess you can root your stock rom without erasing data.
Boot to twrp
Sideload magisk
Click to expand...
Click to collapse
PhotonIce said:
He can't get into TWRP without unlocking though..?
Click to expand...
Click to collapse
Otherwise, he could've used the twrp file manager to get the data, even without root.
Apparently it can be done via DroidKit, don't know if that's free though..
https://www.imobie.com/android-recovery/restore-saved-wifi-passwords-on-google.htm