Related
I just got my captivate 1 month ago (first android). I rooted the phone and installed Cognition 2.3b6 right when i got it. I have never backed up the phone.
2 days ago the phone dropped from about 18 inches onto the bathroom floor. Cracking the interior of the screen. Origintally i could see the top half, the touchscreen hardly works. Now i can only see a faint blue color when i boot hte phone. It still works, i get alarms and feel it vibrate.
I understand that I might be able to do a nandroid backup (is it possible to do it blind?), but is that the correct thing to do? Will that change the deviceID of my replacement phone from AT&T (insurance replacement).
I would like to get the data backed up and transferred over asap so i can pack the old phone up and ship it off before the holidays.
Thank you guys!
adb pull /sdcard
Some one else might be able to help you with the specifics, but pull the /sdcard data from your phone.
From a phone
what?
I figured i need to probably copy it to the sd card. But from what i understand, some applications rely on DeviceID's and not the actual phone. Ergo, if you do a complete nandroid backup it will also copy over the DeviceID (from what i understand, correct me if i'm wrong).
Or is that something different than what you are suggesting?
Your data is stored in /sdcard. The external sdcard is /sdcard/external_sd for froyo, cant remember file path for 2.1. What else could you be wanting to transfer to the new phone?
From a phone
I've never done it before, I want to be able to transfer all data (ie, installed apps, cached notebooks for evernote, preferences, etc) to the other phone.
I have never done this before on an android phone and don't know the best way to tackle this using a cracked screen (can't even unlock the phone)
I think I can manage to do a nandroid backup ( http://www.youtube.com/watch?v=sEqbjUb4WxM ) but i'm concerned about the device id
Cassetti said:
I've never done it before, I want to be able to transfer all data (ie, installed apps, cached notebooks for evernote, preferences, etc) to the other phone.
I have never done this before on an android phone and don't know the best way to tackle this using a cracked screen (can't even unlock the phone)
I think I can manage to do a nandroid backup ( http://www.youtube.com/watch?v=sEqbjUb4WxM ) but i'm concerned about the device id
Click to expand...
Click to collapse
There are 2 way i can think of.
1- Like mentionned in prior post do a adb pull /sdcard
2- Boot into recovery and try to a backup from there blindly (following online pictures/video of the different menus and pressing the buttons accordingly).
I don't see the big deal about your deviceid. Many users have had a auto generated id with roms. It will be ported with the nandroid. Not sure just how wide spread the use of deviceid is used in apps.
Thanks I was really confused about the whole DeviceID thing. Figured it was best to play it safe.
I'll give it a try, i'm sure i can manage to do a nandroid backup on my phone
I'll keep you posted
There are ways of getting your device id back. First of all theres a market app that can backup the device id on your new phone and restore it back after you restore the backup http://www.appbrain.com/app/android-id-changer/adaptive.cogid Or you could search around the forums and/or google for ways of changind and backing up your device id, there are multiple ways of doing it. And don't forget about backing up your sdcard, like boborone said, do an adb pull /sdcard from the clockworkmod screen (adb works from recovery in case you didn't know).
Hell man, you can adb pull the whole phone if you want.
From a phone
Can you send the link to where i can find out how to do and adp full pull from the pc? The only instructions i'm seeing are for the android sdk (bit confused)
the sdk is downloaded to your pc, and then you run that command from a terminal/command prompt with the phone connected.
kmac1914 said:
the sdk is downloaded to your pc, and then you run that command from a terminal/command prompt with the phone connected.
Click to expand...
Click to collapse
Do i need to have left the phone in USB debugging mode? I believe 3 days before the accident, i turned off USB debugging on purpose (for file transfers)
Check out my Screencast video...It may help you here.
http://forum.xda-developers.com/showthread.php?t=877652
Cassetti said:
Do i need to have left the phone in USB debugging mode? I believe 3 days before the accident, i turned off USB debugging on purpose (for file transfers)
Click to expand...
Click to collapse
I believe you can use adb from recovery screen.
connexion2005 said:
Check out my Screencast video...It may help you here.
http://forum.xda-developers.com/showthread.php?t=877652
Click to expand...
Click to collapse
Thanks, the screencast helped, but i honestly think that 2 days before i did this, I turned off usb debugging (so i could use my phone as a hard drive)
I think that is why whenever i plug in my phone, it vibrates really hard and droid explorer doesn't find any devices. Suggestions?
...[from elsewhere] ...I didn't see any mention of this in the how-to threads so I didn't back up my EFS files from the stock rom. Anyone here have had any issues with this after going back to stock?
Click to expand...
Click to collapse
That is an example of things that are scattered in many threads...specifically, what are the things you should DO or SAVE before flashing a new ROM?
Above seems to be one (except is "EFS" a folder or what?). Would folks please offer your suggestions of the "protective" steps to be done/preserved in case of future difficulties.
Actually, in addition to the one quoted, doing a Titanium Backup is in almost all of the how-to discussions, so I guess that is already covered.
efs is really only relevant if you plan on using kies. Your phones product code and imei number are stoped in those files. flashing roms can alter these files. I have never done this. If you want to down load root explorer, or free option android mate. I would pay for root explorer. Find the efs file copy and paste it to your internal sd. Then save it to your pc
Android id. Dl android id changer from market. if you have not already dl busy box from market. Install busy box using app. Open android id changer, click save id, custom flashes change this and it us god to have it saved, you can restore using same app after flash
Do you know what odin is?
Do you know your build number?
mcord11758 said:
efs is really only relevant if you plan on using kies. Your phones product code and imei number are stoped in those files. flashing roms can alter these files. I have never done this. If you want to down load root explorer, or free option android mate. I would pay for root explorer. Find the efs file copy and paste it to your internal sd. Then save it to your pc
Android id. Dl android id changer from market. if you have not already dl busy box from market. Install busy box using app. Open android id changer, click save id, custom flashes change this and it us god to have it saved, you can restore using same app after flash
Do you know what odin is?
Do you know your build number?
Click to expand...
Click to collapse
Recapping this...
EFS is a file. Can save it using Root Explorer or Android Mate.
I have copied down all the data under the battery. Is there more than that in this file?
I am confused about second paragraph. You mention download
Android ID Changer
Busy Box
Which one is it that captures the Android ID? And obviously it saves it, but where?
Yes, odin is mentioned in the how-to's, but it IS part of the flashing process. I am looking for things that should be done BEFORE starting that.
Yes, I know the build (1006). It is part of the data under the battery. And flashing wouldn't destroy or modify that.
Yes the efs had your csc or product code. If you flash a rom that is a port from another device this may be changed. Not an issue if you do not use kies.
Busybox is an app that installs commands onto your phone that certain programs need to operate correctly. Titanium backup and android id changer need this to function correctly. Android id changer saves your id in a file on your internal sd. The file is called update.id when you flash a rom you open the app again click load id, then change id. Phone reboots, id us back to your original id
Odin is a utility that flashes you back to stock 2.1. It is used by many as a safe way to go from rom to rom with a clean install. It is also used to recover from software bricks.
If you have more questions that pop up pm me, this way we are not clogging up the q&a
I think the exchange helps many people who I assume, like me, are trying to sort all this out.
MAIN purpose of the thread is to identify things to do/save before beginning the 'change to another ROM' process--which to me would include the Odin flash back to stock if you aren't there already.
But these side question resolutions are pertinent.
Your Busybox comment threw me a curve. It sounds like you are saying it installs stuff TiBU and Android ID Changer need in order to work. You mean TiBU as downloaded from the market does not work as a standalone app?
tibu needs busy box. If you download tibu and open the app there is a button on the bottom that says problems. If you click it it will also look to install busy box commands.
You are right about the usefulness of threads like this, no disrespect but it looks like you joined xda 4 days ago. These types of discussions are constant and rehashed on nearly a daily basis. For some odd mental quirk I read then all and help when I can. There are a thousand questions you can have, the offer to pm was to keep it easy
I have been reading for two weeks--I mean reading A LOT, not just 4 days ago; that was when I registered on the site. This is a =wonderful= resource, but it is a plain fact that what you need to know is scattered all over the place, both video and written how-to's. I have not found a single one that includes everything you need to know. I mean, for example, they will tell you to do something, which seems trivial to them, but which really involves other knowledge. And that sounds like a non-isue, but in fact it is a complete showstopper for "us" types. Yes, you can go off hunting to clarify the incompleteness, but that is exactly what I am talking about--hunting all over the place.
By the time someone gets to the point they can create something with completeness, the problem is...they are already to the point they can create such a thing. That contradiction arises from it being almost impossible to remember what you didn't know "back then."
I had been studying HARD trying to get "it," everything you need to do to flash a different ROM. Then, a day or so ago, in all that hunting around I speak of, someone mentioned "be sure you ... before you flash." It dawned on me that, when you think you are ready to flash, you aren't. There are things that should be done BEFORE. I started the "hunt" again as alluded to here. Then I said, dang, all us newbies would be well served if all the preliminary do's and save's were in one thread (preferably, ultimately in one LIST). Thus the reason for this thread.
If I am wrong, and other newbies really don't need to know these things, then yes, it can be done in PM. Others will never see it, and still be stuck in the hunting-all-over mode. Thus, I think it is desirable and helpful to others to put it in public, in one thread.
Once again no disrespect. Your point is taken.
Tibu to back up all your user apps, no system information. unless you want to learn how to use odin in the case of issues
Android id changer to back up your android id
Rom manager to back up your current setup, and flasg clockwork recovery. Never restore a backup of one rom on top of another rom
Contacts to external sd, sim, or sync with google
Efs using root explorer to copy folder and save in pc
Odin to flash stock and or recover from software brick. Builds 1010 and above do not use one click odin
No offense taken, and that's a great input. Thanks.
If others see anything else, please contribute.
Ok, I am also new at this, I have flashed 3 Roms. This is what I have done when changing ROMs.
Download Titanium Backup and rom manager. Back up your apps with Titanium Backup.
Download the ROM you want to flash.
Download Odin.
Turn on usb debugging.
Plug phone into the computer, pull down the notification window and click on usb to mount the sd card.
Open this up to look at files.
You should have an update.zip file you can copy to your desktop. You also should have a folder named Titanium Backup that you can save as well.
Once you have this, you can begin.
Take your phone to stock using odin. There are several tutorials available. I used this one,http://forum.xda-developers.com/showpost.php?p=10056254&postcount=36 because I have a 1010 phone.
Once this is done, I push the voume up and down along with the power button. You will get a menu giving you a choice to reinstall packages. You need to click this, go to yes, and it will pull up to the same menu again. Hit reinstall packages again which will get you to clockwork recovery.
Now, I chose to wipe/factory reset to make sure my phone was "clean".
Then, I chose to apply the update.zip.
Then, I chose to install a zip file from the sd card, scrolled down to the rom file, and chose it.
Then it will install the Rom. You will choose go back, then reboot the system. Then your Rom should be installed.
I think I remembered everything. I used a few tutorials:
http://theunlockr.com/2010/08/02/how-to-load-a-custom-rom-on-the-samsung-captivate-vibrant/
and this one:http://forum.xda-developers.com/showpost.php?p=10183875&postcount=4
Hope this helps!
OOPS. Thanks, but this thread is for things to do or save BEFORE starting the ROM change.
So... let's say that you didn't save your android id before you flashed... will that cause problems?
beryxil said:
So... let's say that you didn't save your android id before you flashed... will that cause problems?
Click to expand...
Click to collapse
You tell me. Did you? Are you experiencing problems?
it depends on the rom you are using. You may experience issues downloading from market and certain games may give you issues.
If you did not save it and you are not having problems then no big deal. You can go back to stock and save it, then flash again.
Hi,
i've imported my photos from my internal memory via sony bridge for mac accidentally in Iphoto. I didn't see the app was faded and crossed. Turns out only the app Photos is still working. So after importing 2700 pics (big trip and behind with backup), the question popped if I wanted to delete the fils on my phone and I said yes. I tried to re install Iphoto, but nothing there, but older pics. I tried the temporary files from the Mac, but nothing.
So now I got my hopes up for a data recovery software thing. But although Windows (Im working on another laptop) did install the drivers correctly and I see my phone in the folder structure, no data recovery software recognises my phone although I switched to MSC and USB-debugging. I think because I haven't rooted it i suppose. Well, that's what all the forum members say
So I think rooting is my only option left? I am wondering if it works for my goal to get my data back. I read that unlocking the boot loader means everything will be erased, so then there would be no point for me to do this. Is it possible to root it without losing my (deleted) data on the internal memory? I know it is being overwritten now as we speak, but I'm sure I can save a few photos!
thanks a million!
First off, I don't fully understand the first bit involving iPhoto. But if I understand correctly, you need to recover files deleted from internal memory.
I think recognizing a phone's internal memory is indeed a steep expectation for general Windows file recovery software. However, there may be some specialized programs out there designed just for that purpose. I know for a fact they exist for iOS for example. Not that I'm a fan. Anyway, googling "recover Android files Windows" showed some interesting results, but as I have no experience I can make no recommendations. I did see Easeus among the results, and I personally would start there based on experience with other software by them: http://www.easeus.com/android-data-recovery-software/free-android-data-recovery.html
This would be your safest bet. As you probably know, your photos are still there as long as they are not overwritten. Being able to recover from an external device (PC) is therefore preferable to making changes to your internal memory. It's also far less complex than rooting
Another thought before getting into rooting: I don't suppose you had an app like Google+ making automated backups of your pictures? If so, you might find them on your Google Drive. This also might be a good idea to avoid trouble like this in the future
Third and last resort: you could try a data recovery app on your phone, like GT Data Recovery. That does requires root. The good news: you don't need to unlock your bootloader to be able to root. Locked bootloader means you're limited to stock roms, but they too can be rooted.
Here's a useful thread describing in detail what you'd need to do:
http://forum.xda-developers.com/z3-compact/general/how-to-root-backup-drm-keys-t3013343
In your case, I'd run data recovery ASAP, meaning
Downgrade your firmware, leaving data in Flashtool unchecked (!!) (See thread's FAQ for detailed explanation)
Root
Install GT Data Recovery or similar from Google Play and run it
After you've recovered all photos you can and backed up all your other data, follow the procedure in the recommended way, which includes wiping data. Do note however, that the firmware mentioned there is outdated (March 2015). You can find up to date firmware here: http://forum.xda-developers.com/z3-compact/general/list-stock-firmwares-d5803-d5833-t2906706
Good luck!
(Thanks to @bilboa1 and @istux for their useful posts!)
Thanks!
I did try several data recovery software programs, including EaseUS, but none recognised my internal memory unfortunately. I switched all auto back up programs like Google Plus off, because it was just too much. I take so many pics of my kids and the selection process usually doesn't take place directly, so it backs up everything and I've got to many pics in my Google Plus account. But this was a wise lesson i should backup somehow.
So only option 3 is left. As i read it, when I root it, the data on my internal memory won't be deleted? Stock ROM is fine for me, I'm very happy with my standard software, if rooting is what it takes, that's what i should do.
If you're rooted, you can use the app DiskDigger. Worked for me
Sent from my D5833 using XDA Free mobile app
kjoz said:
Thanks!
I did try several data recovery software programs, including EaseUS, but none recognised my internal memory unfortunately. I switched all auto back up programs like Google Plus off, because it was just too much. I take so many pics of my kids and the selection process usually doesn't take place directly, so it backs up everything and I've got to many pics in my Google Plus account. But this was a wise lesson i should backup somehow.
So only option 3 is left. As i read it, when I root it, the data on my internal memory won't be deleted? Stock ROM is fine for me, I'm very happy with my standard software, if rooting is what it takes, that's what i should do.
Click to expand...
Click to collapse
Generally speaking, wiping data is recommended when flashing a new ROM. Because Giefroot requires older firmware, you need to flash that firmware. Which means a data wipe comes recommended. Technically however, wiping data is optional. It is possible to downgrade without wiping data (by unchecking the respective option in Flashtool). So that is what I'd do in order to recover your pictures.
Once that has been accomplished, along with a backup of all other data you wish to keep, I would start the whole process again as described in the thread I linked to. Because this time, the objective would be not data recovery, but ending up with a stable phone. And that means wiping data. (Highly recommended.)
I don't want to complicate things further, but if you don't care about being rooted after data recovery, you could just upgrade to regular stock firmware instead of pre-rooted firmware. This would allow you to skip a few steps of the process, and also avoid being unable to apply Sony's OTA updates. (Significant updates can cause a loss of root.)
Personally, I would not want to give up root once I have put effort into getting it.
kjoz said:
Hi,
i've imported my photos from my internal memory via sony bridge for mac accidentally in Iphoto. I didn't see the app was faded and crossed. Turns out only the app Photos is still working. So after importing 2700 pics (big trip and behind with backup), the question popped if I wanted to delete the fils on my phone and I said yes. I tried to re install Iphoto, but nothing there, but older pics. I tried the temporary files from the Mac, but nothing.
So now I got my hopes up for a data recovery software thing. But although Windows (Im working on another laptop) did install the drivers correctly and I see my phone in the folder structure, no data recovery software recognises my phone although I switched to MSC and USB-debugging. I think because I haven't rooted it i suppose. Well, that's what all the forum members say
So I think rooting is my only option left? I am wondering if it works for my goal to get my data back. I read that unlocking the boot loader means everything will be erased, so then there would be no point for me to do this. Is it possible to root it without losing my (deleted) data on the internal memory? I know it is being overwritten now as we speak, but I'm sure I can save a few photos!
thanks a million!
Click to expand...
Click to collapse
If you have successfully imported from the phone into iPhoto, then you simply need to import your iPhoto Library into Photos in Mac.
Check if you can find the iPhoto library by going to Finder -> Home -> Pictures
There should be 2 libraries there - one for iPhoto, and one for the newer Photos app that came along in April. Double-click the iPhoto library and wait for Photos to launch, then follow the instructions to import the library into Photos.
Make sure you have enough disk space (on the Mac) to do this. You'll need at least as much free space as the size of the iPhotos library to import it into Photos and possibly more.
Hello,
I'm a beginner lost in reading all the useful information on this forum.
I started with the idea to reduce the permissions of applications of my Razr I.
Google pointed to this http://www.xda-developers.com/protecting-your-privacy-app-ops-privacy-guard-and-xprivacy/
And I'm really happy and surprised about all information I can find here, thank you that much for
making this possible to all of you!
As today I feel ready to start playing around with my phone I wanted to ensure I understood the items right.
May be for you it takes only some seconds to verify my guess and can give a short notice
about Step 2 or 3 is easier to become implemented.
Step 1.) I wanted to do a full backup before I start, following this thread:
So I'll install ADB on my PC and run "adb backup -f FullBackup.ab -apk -all"
This works on a Razr I with 990.43.74.xt890.Retail.en.EU - of the shelf and is not risky at all - or?
Could you pls. tell whether it is really true I can switch back to my backup if I'm not happy with my System?
Step 2.) My first intention was to root my device and install Xposed framework
http://forum.xda-developers.com/showthread.php?t=2299428
http://repo.xposed.info/module/de.robv.android.xposed.installer
And to use Permission Master out from google play store
First of all I wanted to ask you whether this is feasible technicaly and esp. for a beginner?
Alternative to Step 2 Step 3?
Step 3.) In general I'm happy with my Razr I Android 4.4.2 (990.43.74.xt890.Retail.en.EU)
But I'm wondering whether it would be easier or has less risk to use a custom ROM instead of implementing Step 2.
By reading in this forum I found out there is a planty of features FM-Radio, enhanced stand-by current ,
to get rid of preinstalled aps and so on.
I'm an embedded developer but do not have the overview about the architecture of Android devices, what I got so far is:
There is a bootloader which needs to be changed from OEM closed to open.
There is a boot partition I flash ROMs in.
I need some tools on my PC combined with SDK and Motorola drivers to allow a USB-Debuging and flashing.
And sure as always once your bootloader is damaged you are lost, so I understand even backup will not help here.
So I'll keep my fingers crossed.
Thanking you in anticipation and pls accept my excuses about my english and stupid beginners questions.
Best Regards
gonso
PS:
As I main entry point I used the
http://forum.xda-developers.com/razr-i/general/index-razr-t2832722
from there I'll try to get ADB, drivers etc.
Hi GonsoXDA,
Step 1: I have never used it. Didn't even know that it existed. On the internet there are numerous people who uses it and it seems to work. Maybe someone else can give some info about this or just try it. U can try it with a non-important app and see if it works. Just backup it, delete it and restore it.
Step 2: This works just fine. But do know 3 things:
1. First root: To get root on stock rom, u need to use kingsdroot methode afaik. And that one sends your IMEI to some rare ip adress. I personnaly don't trust this and stay away from it, but there are many people who use it.
2. Xposed requires a recovery to install the framework. It can be done mannually or by the app i suppose. With only root u don't have a recovery on your device that can perform such action.
3. If something goes wrong only a full restore with RSD-Lite can most of the time help u out. Because u don't have a recovery that works than.
Step 3: We only have 2 full roms. 1 for JB (stock) and a working CM11 rom (kitkat).
Only the Jellybean roms support fm-radio, on every newer rom fm-radio is cut out of the audio firmwares. The risk of going to this is even less as Step 2, because u can do a full backup and restore of ur phone. ( I would chose for this if u want to play a bit with the phone and ur warranty is already out of years)
The gereneral idea about the android architecture is this (it is different for almost every device and the Razr I has many more thing to hold into account, but if u are here only for the roms and xposed, there is no more to know):
Bootloader: Is like an uefi bios for PC, but then for android. It also contains fastboot
Bootimage(boot): Has all the info like kernel and ramdisk to boot the system
Recovery: Is like 'boot', but boots into the recovery partition that lets u change every aspect of the device if u know how. Its mainly used to flash a custom recovery to, backup and restore a nandroid backup and flash/wipe roms, mods, (all/specific) data and packages.
Systempartition: Is the system the boot boots into. It's android.
Datapartition: Where all the user data is stored.
Cachepartition(dalvik): Where all cache is stored and in earlier android versions also dalvik. But not now anymore.
Fastboot: To flash/wipe the above partitions and many more (needs drivers)
Adb: To push, pull, command things in system or recovery (needs drivers)
Sdk: contain the abd and fastboot packages, but aren't needed for adb and fastboot because with the right drivers can work on there own (see the internet)
If u have a custom recovery and only change things on the system, data and cache partition there is almost no way to damage the phone. There is always a backup through recovery. As long as u stick to the things u can do in recovery.
The only thing tha can mesh up your phone beyond repair is doing wrong stuff withint the bootloader and other inner parts in the phone(like i did to get newer kernel working) or u are in bad luck and you internal memory blocks. See 'Super brick samsung phones' (emmc error).
I suggest:
- Unlock your bootloader
- Install custom recovery
- Make a backup with the recovery
- Do what u want, xposed on stock rom, try CM11?
- If things won't boot, restore through recovery
And always, read up before doing anything. There are thousands of articles about android, flashing things, repairing android, using adb and fastboot. AND ALWAYS HAVE A BACKUP PLAN!
Hello,
always having a backup seems not to be that easy.
So I unlocked my boot loader and tried to install twrp2850 and twrp2860 via mfastboot.
The mfastboot with 533.353kB caused the following "(bootloader) Variable not supported!"
I rebooted into bootloader and tried recovery -> horizontal Android man with a red !-rectangle
After reboot to normal power up my phone seems to be in factory reset, all my data is gone :crying:
ok crying dosn't help so I looked around and tried with another mfastboot 186.178kB and recoverycwm6.0.5.1.4.img.zip
http://forum.xda-developers.com/showthread.php?t=2441224
The twrp I tooked from here: http://forum.xda-developers.com/showthread.php?t=2278483 seems not to work.
I did a backup with cwm is there a change to get back my data? I think I know the answer.
In the meanwhile I installed
http://forum.xda-developers.com/razr-i/development/rom-unofficial-cyanogenmod-11-t2966855
And will try to install
http://forum.xda-developers.com/xposed/modules/tool-installer-xposed-installer-zenfones-t2983589
Thank you for the help, work and excuse the stupid beginner posts.
Regards
gonso
gonsoXDA said:
Hello,
always having a backup seems not to be that easy.
So I unlocked my boot loader and tried to install twrp2850 and twrp2860 via mfastboot.
The mfastboot with 533.353kB caused the following "(bootloader) Variable not supported!"
I rebooted into bootloader and tried recovery -> horizontal Android man with a red !-rectangle
After reboot to normal power up my phone seems to be in factory reset, all my data is gone :crying:
ok crying dosn't help so I looked around and tried with another mfastboot 186.178kB and recoverycwm6.0.5.1.4.img.zip
http://forum.xda-developers.com/showthread.php?t=2441224
The twrp I tooked from here: http://forum.xda-developers.com/showthread.php?t=2278483 seems not to work.
I did a backup with cwm is there a change to get back my data? I think I know the answer.
In the meanwhile I installed
http://forum.xda-developers.com/razr-i/development/rom-unofficial-cyanogenmod-11-t2966855
And will try to install
http://forum.xda-developers.com/xposed/modules/tool-installer-xposed-installer-zenfones-t2983589
Thank you for the help, work and excuse the stupid beginner posts.
Regards
gonso
Click to expand...
Click to collapse
Than u know the answer, it is no I think.
Both twrp images should work just fine, but always chose the latest. The message "(bootloader) Variable not supported!" doesn't do anything So don't worry about that one. There should be a lot more in you log that the message if twrp didn't install. U did extract it and flash it with the command: mFastboot flash recovery <recovery-image>. Where <recovery-image> could be C:/users/*/Downloads/recovery.img.
Hello,
yes sure "The secret of health for both mind and body is not to mourn for the past, worry about the future"
So I use CM11 now for about 2 days and I'm really impressed, so far everything works :good: THANK YOU!!!
As I asked already I installed XPosed and Permission Manager, but I found XPrivacy might be the better solution and switched to this.
(Today I do not have all the technical background to judge whether it is technically equivalent, but I'll investigate on it)
Esp. one thing I'm wondering, why XPrivacy is reading my Contacts once I check the permissions of an app?
But the more important thing I recognized differences between CM11 and the Stock ROM. One is the Entry
"Privacy" in the settings. It seems to be more or less the XPosed and XPrivacy, or?
But it seems the Restrictions are not shared, so I can restrict in the one and do not see the restriction in the other tool.
So first is there a risk to use both, is it useful or just doing the same twice.
Thank you
Gonso
gonsoXDA said:
Hello,
yes sure "The secret of health for both mind and body is not to mourn for the past, worry about the future"
So I use CM11 now for about 2 days and I'm really impressed, so far everything works :good: THANK YOU!!!
As I asked already I installed XPosed and Permission Manager, but I found XPrivacy might be the better solution and switched to this.
(Today I do not have all the technical background to judge whether it is technically equivalent, but I'll investigate on it)
Esp. one thing I'm wondering, why XPrivacy is reading my Contacts once I check the permissions of an app?
But the more important thing I recognized differences between CM11 and the Stock ROM. One is the Entry
"Privacy" in the settings. It seems to be more or less the XPosed and XPrivacy, or?
But it seems the Restrictions are not shared, so I can restrict in the one and do not see the restriction in the other tool.
So first is there a risk to use both, is it useful or just doing the same twice.
Thank you
Gonso
Click to expand...
Click to collapse
That's a sentence.
Why XPrivacy needs it i don't have a clue. For that sort of things u need to be by the dev of the app.
CM has a lot of features out of the box compared to stock, but stock is most of the time a bit more optimized in terms of proprietary stuff like camera.
So as u noticed, CM had an inbuilt security app. This app (CM) and XPrivacy don't share there settings, so that's the difference u see. But most likely if u disable something in one of the apps it is disabled even tho the other doesn't say it because it doesn't know of it.
I don't think it will be a risk. They both do the same thing, but they don't know about it. To be on the safe side, just use one and restore the other to default. U can always search on the web if they don't get along.
U can now make a full backup, so everything can be reverted and your data should be relative safe.
Hello,
thank you again - I now find the answer by reading in the development part of the forum. For me as a beginner it is sometimes not easy to interpret the discussions there.
If accepted I will use the thread now as a kind of diary, may be some other users will have similar destinations and my learn from my mistakes.
So to answer my question a little more detailed, but with less background know how than Hazou. Pls. do not trust me I'm a beginner, I have not analyzed the code just the behavior - feel free to correct or contradict my words!
The XPosed is in the area of permissions just a framework which allow other modules to put some code between an app requesting permissions and the Android core granting this permissions. The Xposed it self doesn't handle settings or permissions you did in modules like the CM Privacy, Permission Manager or XPrivacy.
As a result I came to the same conclusion it is not a risk, but an overhead to have more than one pice of code between the app requesting permissions and the Android core. -> My proposal: Do not use more than one of this Permission control apps in parallel.
From the privacy perspective the Permission is just a starting point, it allows you to hide your private information from the app. On the other side many apps will need access to the data to work and most of them are able to connect to the internet.
So I realized the next step would be the restriction of internet usage of apps. Here permissions are sword but we need a scalpel, to separate the necessary from the unwanted connections. This scalpel could be AFWall+ and "Netzwerk Log", this is a firewall and a sniffer.
What I can say to day the apps run on CM11 installed on my Razr I.
So it looks like I see my destination raising on the horizon and I will try to formulate it in the following order:
1.) Hide Contacts, Calls and SMS from Apps who do not need this to work -> XPrivacy
2.) Disable some Android features I think I don't need.
(e.g. Captive Portal Check - settings put global captive_portal_detection_enabled 0)
3.) Restrict the internet access of some apps to servers they need to connect. ( e.g. E-Mail client is restricted to connect to the mail server)
4.) Limit the access to my pictures, stored on SD card. [I have not found a solution so far]
If you read this I think 1 is reasonable for most of you, even if you do not have deep Android or Network know how (as I have), you just restrict the permissions - if app crashes or doesn't do the job you expect you may permit access or uninstall the app. (XPrivacy allows you also to fake data)
3 is a usual task of a network administrator, if you are used with iptables it is just work. I'll try to find out whether there is somewhere a source of "Templates". Usually the network admins share there common settings based on services, once I find out I'll post.
To restrict the access to SD Card I only see the change to extend the sandbox of Android to the SD and to hide files which does not belong to the app. As I would store my pictures on SD as I would store my Navi Data, but neither the Navi app should see my pictures nor the Cam and Gallery my Navi Data. ...
I don't know whether there is an app out there but It should be possible the same way like XPrivacy fakes the other data.
Thank you
Gonso
Hello,
Most of the time I used the numbers to just put in the extension, so if I want to call 0049 9876 54 321 I put the numbers 321 the Motorola dialer will show a list of all contacts where the number contains 321.
Some Numbers of contacts are not shown as well, seems if a contact has more numbers only one or two are shown.
The CM11 dialer doesn't show the number, is there a setting to get this feature?
I tried to get my Stock dialer back, so I copied dialer.apk from stock into the /system/sec-app/ directory of the CM11 and restarted the phone -> doesn't change the dialer ....
Any proposals? I'm terrible sorry for my stupid questions, I read several threads and still no idea about a possible solution
Gonso
PS: CM11 file manager shows a secure storage /storage/emulated/0/storage/secure - what is the algorithm used for the encryption.
gonsoXDA said:
Hello,
Most of the time I used the numbers to just put in the extension, so if I want to call 0049 9876 54 321 I put the numbers 321 the Motorola dialer will show a list of all contacts where the number contains 321.
Some Numbers of contacts are not shown as well, seems if a contact has more numbers only one or two are shown.
The CM11 dialer doesn't show the number, is there a setting to get this feature?
I tried to get my Stock dialer back, so I copied dialer.apk from stock into the /system/sec-app/ directory of the CM11 and restarted the phone -> doesn't change the dialer ....
Any proposals? I'm terrible sorry for my stupid questions, I read several threads and still no idea about a possible solution
Gonso
PS: CM11 file manager shows a secure storage /storage/emulated/0/storage/secure - what is the algorithm used for the encryption.
Click to expand...
Click to collapse
Stock CM dialer doesn't have that function afaik. The moto one doesn't work because it needs the Moto framework to work. Just download a dialer U trust from the playstore.
I don't have any clue about the secure storage, sorry.
Hi Guys,
I have an issue accessing my P20 pro, that I PRAY someone can help me with!
So, the story goes as such. I recently updated my P20 using Hurupdate, and as part of the process i disabled Screen lock in Developer options (i didnt delete the actual PINs, fingerprints etc from the phone) in order that i can get access to the data partition in decrypted format in TWRP and update the phone.
Upgrade appeared to go fine and phone worked no problems...until I tried to re-enable and re-implement fingerprint unlock. It asked me to set up a 6 digit PIN first, which i tried, but it seemed to go around in circles. Eventually it took a PIN, and then BOOM! I was unable to use that PIN to access the phone.
I've tried the old school method of deleting the locksettings.db file from /data/system (didnt seem to be any .key files for some odd reason), and now i dont get prompted for a pin, but i get a blank desktop. This is clearly because the data partition is still encrypted and the phone cannot access the data to start up my desktop etc.
My question, is there a way to remove the PINs/Fingerprints and security setting via TWRP on the P20, in order that the data partition mounts in decrypted format?
This is really important guys, so any help would be amazing. I have photos on the phone of a family member that recently passed away very suddenly, and I would be devastated if i couldnt get them back.
Cheers all.
Have you deleted ALL locksettings files and all files with .key ending? (Oh there were no key files)
password.key
pattern.key
locksettings.db
locksettings.db-shm
locksettings.db-wal
Something like that.
Yeah they are all gone. When i reboot the phone into the OS, i just get a blank desktop and no launcher.
crstephenson said:
Hi Guys,
I have an issue accessing my P20 pro, that I PRAY someone can help me with!
So, the story goes as such. I recently updated my P20 using Hurupdate, and as part of the process i disabled Screen lock in Developer options (i didnt delete the actual PINs, fingerprints etc from the phone) in order that i can get access to the data partition in decrypted format in TWRP and update the phone.
Upgrade appeared to go fine and phone worked no problems...until I tried to re-enable and re-implement fingerprint unlock. It asked me to set up a 6 digit PIN first, which i tried, but it seemed to go around in circles. Eventually it took a PIN, and then BOOM! I was unable to use that PIN to access the phone.
I've tried the old school method of deleting the locksettings.db file from /data/system (didnt seem to be any .key files for some odd reason), and now i dont get prompted for a pin, but i get a blank desktop. This is clearly because the data partition is still encrypted and the phone cannot access the data to start up my desktop etc.
My question, is there a way to remove the PINs/Fingerprints and security setting via TWRP on the P20, in order that the data partition mounts in decrypted format?
This is really important guys, so any help would be amazing. I have photos on the phone of a family member that recently passed away very suddenly, and I would be devastated if i couldnt get them back.
Cheers all.
Click to expand...
Click to collapse
Hey man,
I have got a similar situation. Did you manage to solve the issue?
You may have to go into the boot-loader and do a factory reset