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
Related
So I'm a bit of genius and decided I'd try to fully fix my 99% functional phone and have now made it so it won't boot into home screen... I believe I corrupted blur-services.apk and/or blurcontacts.apk, so I get greeted with a series of crash screens.
What I did? I copied over some Bell XT860 system files (including blur-services.apk) from a system dump in Root Explorer, which caused a crash in the middle of copying. After rebooting the phone, it won't properly go into home screen. I tried a system recovery with no luck, oops.
So I'm hoping/assuming that copying over blur-services.apk properly through ADB might solve the issue, but I can't get into ADB on my phone. I've tried using bp-tools & psouza's tool for temp ADB rooting, with no luck -- it won't pickup the connection, even though my phone's storage is available on my computer and clearly connects. Granted, I might be missing a step somewhere...
If someone could guide me into getting into ADB, I can push the blur-services files properly and hopefully regain control over my phone again...
I must say... if I can get this phone operational again, I will stop messing with it!
Two issues...
1) I could use a non-corrupted copy of each of these files [along with their respective odex files]...
2) I can't get into ADB on my phone. I've tried using bp-tools & psouza's tool for temp ADB rooting, with no luck -- it won't pickup the connection, even though my phone's storage is available on my computer and clearly connects.
I must say... if I can get this phone operational again, I will stop messing with it!
Update:
Luckily for me, I was still able to access my gmail and launched Android Market from there. This allowed me to download Go Launcher, GO Contacts, etc. and at least restore functioning to my phone. Most importantly, this enabled me to check off USB debugging (which I lost when I foolishly reset my phone).
So now I've got a semi-functional phone that gives me error messages at least every 30 seconds about one of the .com applications closing.
However, there is hope that I can get her fully functional since I can now obtain ADB access!
---------- Post added at 02:08 AM ---------- Previous post was at 01:44 AM ----------
Sweet, after being able to check USB debugging, I was able to save my self again using psouza4's tools and guidance.... I really have no idea where noobs like me would be without his help!
Main Lessons:
1) Don't play with your phone too much without a proper SBF
2) If you're like me and can't resist, DO NOT FACTORY RESET YOUR PHONE. This only makes the problem worse.
I have tried CJ's method, but I keep losing it and the subscription check takes over again. I cannot do the write protection hack (if that has anything to do with this, not sure) because the script fails when searching for ADB for whatever reason and I use ADB all the time.
I just want to be able to tether with my unlimited data. Any ideas?
tluley51 said:
I have tried CJ's method, but I keep losing it and the subscription check takes over again. I cannot do the write protection hack (if that has anything to do with this, not sure) because the script fails when searching for ADB for whatever reason and I use ADB all the time.
I just want to be able to tether with my unlimited data. Any ideas?
Click to expand...
Click to collapse
i was able to successfully pull framework-res.apk and take out the entitlement check, but i ran into problems recompiling it so i'm not comfortable posting it yet until those are resolved. the method for doing it is out there (on this forum actually somewhere but i don't have the link in front of me), but i ran into a few things. here's the post i made about trying to resolve those issues...
http://forum.xda-developers.com/showpost.php?p=49260289&postcount=7
everything SEEMS to work so far, including native tethering without the entitlement check (knock on wood), but i haven't gotten to give it any real good testing and the framework file is about 3mb smaller than the original. not sure if that's good, bad or indifferent...
If you go into the bootloader, volume down to recovery, press volume up to select it, Android will reboot without write protection enabled and THEN do CJ's method, it works!! Courtesy of Coderedpl
My apologies for posting a question on what is most likely the wrong forum - but after 15-minutes of searching, I could not find the right forum for a new Galaxy Tab Active 2 question.
This is a question more related to software and may be more generic ?
My wife is the owner of a new Galaxy Tab Active 2 , and she is struggling to have her many Android applications installed not on the 16-GByte internal memory, but instead on a 128 GB microSD card she has in the Tablet. She has found various guides, but they either are not applicable to Active2 (as their menu options don't exist on Active 2) or they simply only work for some apps but not the necessary/important to her applications that she wants to transfer to the microSD card. In particular she would like the application "Line" ( https://play.google.com/store/apps/details?id=jp.naver.line.android&hl=en ) and also "WhatsAPP' (https://play.google.com/store/apps/details?id=com.whatsapp&hl=en) configured such that all their data goes on the microSD card. Unfortunately (especially for Line) she has not been able to do such.
Can anyone point me to the correct forum area ?
Again - my apologies for likely posting in the wrong area.
I own tab active 2 sm-390 too. 16gb is really not enough. We can only wait some professional to root the machine. Once root, we can try 'adaptive storage' or other app like 'App2SD' to save internal storage.
Just want to update you that I solve the storage problem.
1) You need to download the firmwire , extract the 'boot.img' file. Then, copy the file to your tablet.
2) Then, you have to install Magisk Manager and run the manager to patch the 'Boot.img'. In setting, remember to set the output file to odin format.
3) Copy the patched file to computer. In computer, run odin to install the patched file to tablet.
4) The tablet will then be reset. Now, the tablet is already rooted.
5) Then, run Apps2SD, you can move all apps to SD.
I am now have around 50 apps installed.
Please a step by step
Awesome!
You are such a genius to give us this good news
Can you please provide us a step by step guide and also the links to the files so that we can follow.
Thank you so much
How are you getting root.
I have the galaxy tab active 2 / T395 and have tried all the stand alone apks out there that claim they can root any android device; 'KingRoot, KingoRoot, OneClickRoot, z4mod.z4root, Rootmaster and Framaroot'. But do absolutely nothing for the T395 active 2.
However I can confirm that 'mark.mccv' method of rooting DOES WORK for the T395.
I guess the days of using CF-Auto Root & TWRP are over for the newer Nougat 7.1.1
mark.mccv said:
Just want to update you that I solve the storage problem.
1) You need to download the firmwire , extract the 'boot.img' file. Then, copy the file to your tablet.
2) Then, you have to install Magisk Manager and run the manager to patch the 'Boot.img'. In setting, remember to set the output file to odin format.
3) Copy the patched file to computer. In computer, run odin to install the patched file to tablet.
4) The tablet will then be reset. Now, the tablet is already rooted.
5) Then, run Apps2SD, you can move all apps to SD.
I am now have around 50 apps installed.
Click to expand...
Click to collapse
You forgot to mention, when installing the 'patched_boot.img' you need to turn 'OFF' both the FRP & OEM locks. Otherwise, when trying to flash the 'patched_boot.img' through Odin on the PC.
The devices download screen shows 'custom binary boot file' blocked by the FRP & OEM locks......
For anyone stuck on this ROOT process , you turn off the FRP lock by just deleting your Google accounts from your devices settings page.
Remove, turn OFF the OEM lock , by going to 'settings' > 'developers tools' > 'oem unlock'
On flashing the patched_boot.img , you will see a verification screen page after reboot, which forces you to reset, reformat your device. So back up your files beforehand.
Once reset, your device is rooted, ready to install busybox , adaway etc.
Well Crap...I just got my Nice, New, Sparkleing Tab Active2 and cant root it yet. I have the New US version SM-T397U Unlocked model. cant find a Stock firmware on Sammobile as of yet...any ideas?
EDIT: Neeeevermind... I did a lil hacking and cracking (for about 26min, lol) to find the files I needed for the SM-T397U. If anyone is looking for em let me know and I'll shoot em' your way. Guessing I'm the first person to root a T397U, hope more will follow. I havent even had this thing 6 hours yet. Thanks for the write up and all those that contributed to the tools and info.
Crap: posetd this is two threads, realized i was typeing in the wrong one, cut and pasted and still hit send. oops
Worked perfectly, Thank you very much!
WARNING: THIS WILL WIPE EVERYTHING ON YOUR TABLET.
Backup all of your important files before you flash the patched boot.img using odin.
I tried to backup my app data using samsung switch and it worked, but didn't restore most of my device settings and all of my app data.
(Good thing I kept backups for my important apps that had in app backup functionality - like Nova launcher and Squid)
Also, If you are having any trouble, then you can take a look at this thread (more detailed): https://forum.xda-developers.com/galaxy-tab/help/how-to-root-samsung-galaxy-tab-active-2-t3775664
Last thing, you probably won't be able to get OTA updates after you perform these steps, it doesn't matter though since this tablet isn't going to be updated that frequently (The 8.0 update is going to come at the end of 2018, source)
Did App data remain after rooting
mark.mccv said:
Just want to update you that I solve the storage problem.
1) You need to download the firmwire , extract the 'boot.img' file. Then, copy the file to your tablet.
2) Then, you have to install Magisk Manager and run the manager to patch the 'Boot.img'. In setting, remember to set the output file to odin format.
3) Copy the patched file to computer. In computer, run odin to install the patched file to tablet.
4) The tablet will then be reset. Now, the tablet is already rooted.
5) Then, run Apps2SD, you can move all apps to SD.
I am now have around 50 apps installed.
Click to expand...
Click to collapse
Hi mark.mccv
Please confirm if the data remained (i.e. was not erased) after the rooting?
Thanks in advance.
I just came across a little gem, my uncle Gave me his T397U that he used to use for work, but has since upgraded!!!! I was so stoked until I powered up to realize that’s its full on knox mdm and is running what I’m assuming is the OS from his job, accessing reg samsung os at all is only possible through safe mode at the present moment ...I apologize if I’m in the wrong area, I’m vey New and honestly not even navigating around the boards to efficiently just yet ! Hopefully someone will want to throw me a bone! Thank you all for the amazing plethora of information!!!!
I read many posts and articles the past few hours and realized a few things, would you correct me if they are wrong please.
My phone:
Pixel 4XL, adb reboot recovery gives "no command" it would seem it might have been rooted at some point before I bought it, but now the bootloader is locked and no custom recovery is on it.
Can I not recover data without root?
Saw few articles mention `adb pull' and `dd` to copy block device, which I can't do with no root.
Is it possible to just install busybox with adb and be able to copy block device?
As per this article https://www.andreafortuna.org/2018/...imaging-android-file-system-using-adb-and-dd/
I might have to wait a bit for TWRP as I did upgrade to Android 11 and it seems it is only supports Android 10 at the moment.
In order to put TWRP on my phone I probably need to unlock the bootloader and would that mean lose all user data? Then I really have no hopes of recovering the audio file I'm looking for as then I couldn't decrypt it?
I know the file's mount point and can figure out which block device it was on, but wouldn't the encryption get lost if android was wiped?
Is there a way to get TWRP without factory restore phone, or busybox or something that will help get block devices out.
Someone mentioned that these dm block devices are decrypted, are they? I will attach a screen shot with list of my block devs.
Thanks for any help or pointer, I can't be destroying this phone as I have money on it and other stuff needed for traveling, so I don't even feel like trying to install busybox to see if adb pull would work, and others mentioned if trying to get block dev off the phone while partition is mounted might lose some data, so they advised using TWRP while partition is unmounted and then copy it's image.
I also found this but I would need root, he mentions 'temporary root' is that even a thing?
Extract Android Userdata Partition for Recovery and Forensics - Root101 | Fundamentals of Linux Administration
Open Source and Linux. Guides and Ideas for Designing Highly Available and Scalable Production Environments
www.root101.net
@GogoAkira - Your long, rambling post is very confusing, and you do not clearly state what it is you are trying to do or the current state of your phone. I want to start by saying that if you have not done so already, you need to be on the very latest version of the adb/fastboot binaries. If the phone is working fine and you can access all your files, there are some non-root ways to back up almost all of your data, but you're NOT going to get anything near a nandroid backup. If your phone is working fine on 11 (why would you not be on 12?) you can also enable usb debugging from within the developer options menu and then use it from the RECOVERY mode. You cannot use adb from your PC without first enabling adb debugging. I say this because you claim "adb reboot recovery" won't work. Of course it won't work. You cannot access adb in the FASTBOOT mode. Probably the first thing you need to confirm is that you have enabled USB DEBUGGING and whether or not your ALLOW OEM UNLOCKING toggle can be set to yes. Whether or not you can do this will tell us alot. If it is greyed out in the off position your bootloader is a) currently locked, and b) probably will not be able to be unlocked. Knowing that, then clearly state what it is you are trying to accomplish and people will try to help.
Hi,
I am in a bit of trouble I have a Motorola Edge 20 (2022) and I was playing with De-Bloater under Magisk. It worked really fine until I pushed the limit of how many Motorola apps i can remove. The last one was the wrong one, I think it was Motorola settings storage (provider) or so. Now the phone won't boot anymore and I was stupid enough not to back up the photos I made in the last three days.
I don't have TWRP on the phone (it's not available yet), so the Android recovery has to do. I saw that I can mount /system, but I don't know how to modify or even read it after mounting it. The internet is full of instructions of how to mount it and always mentions that you can then modify anything on it, but nowhere does it explain exactly HOW to do that
adb shell/push/pull just says "unable to... : closed"
The second option seems to adb sideload some zip. But what zip would I have to flash to disable the De-Bloater without factory resetting everything?
thanks
whoohoo! I jst discovered Safe Mode. Immediate problem thereby solved However, I am still interested in the first part of my question: how to use the mounted /system in Recovery Mode?
michael-brade said:
whoohoo! I jst discovered Safe Mode. Immediate problem thereby solved However, I am still interested in the first part of my question: how to use the mounted /system in Recovery Mode?
Click to expand...
Click to collapse
with stock recovery, youre unlikely to win as /data is decrypted (usually) and /system is largely unmountable and writeable (at least easily)
the usual prescription if you cant get into safe mode is:
Code:
adb wait-for-device shell magisk --remove-modules
from the bible (read on for TWRP ways which are 100% easier):
Magisk - Installation and troubleshooting:Magisk and MagiskHide Installation and Troubleshooting guide
didgeridoohan.com
which obviously removes all modules, even us experienced folks fond ourselves using the magical key combo to get into safe mode on occasion because we flew too close to the sun doping something in magisk
ironically debloating wasnt one of those times for me, i gave a log of what i debloated to the author of one debloater modules recently when he released a new version of his module and he was like "and it still boots?"...the list of debloated packages was at 135, and i could remove even more...
Thanks, good to know. But even adb wasn't able to connect anymore, Android got stuck even earlier.
However, I don't really mind if /system is read-only, I am more interested in how to (even theoretically) use the stock recovery. There is no manual and nobody said anything so far. So once you clicked "mount /system", what to do?
Lenovo (owner of Moto) has a online 'rescue' site that u can go to with your phone connected to the PC and it'll flash your Moto back to stock...prolly won't retain ur data, but it saved my a$$ a few times with my old twrp-less A/B slotted Moto G7. Can't recall the exact url but am sure u can dig it up with google.
Zaxx32 said:
Lenovo (owner of Moto) has a online 'rescue' site that u can go to with your phone connected to the PC and it'll flash your Moto back to stock...prolly won't retain ur data, but it saved my a$$ a few times with my old twrp-less A/B slotted Moto G7. Can't recall the exact url but am sure u can dig it up with google.
Click to expand...
Click to collapse
Hmm... but I can already do that without their help using fastboot. No need for the Android recovery.
Isn't it strange that there is a function we don't know how to use or how it works?