I installed new soft to my phone and i lost some of photos, screenshot
If I rooted my phone, can I recover my data that was lost after the software update? Can I unroot it later without any effects or issues with banking apps and financial services?
Also, I hope there is a way to retrieve photos and files without rooting the phone because I have tried several methods on both the phone and PC, but they are not recognizing the device even though it appears on the Explorer.
Short answer:
1. A stable wired / wíreless ADB must be given
2. The partition that holds the data in question must be decrypted
3. The phone must be rooted
4. The partition in question must get dumped to PC
5. An external forensic software is needed to read the dumped partition / fles in question
shadyhoo said:
If I rooted my phone, can I recover my data that was lost after the software update?
Click to expand...
Click to collapse
To root your phone, you'll need to unlock the bootloader first.
If you unlock the bootloader, it will erase your internal storage and all files will be lost.
Is your bootloader unlocked as of now?
To keep you updated:
You are able to root Android without unlocking the bootloader, keyword: temporary root.
Even though it is possible in some cases to obtain root access without an unlocked bootloader, unlocking the bootloader is required to permanently root a device.
xXx yYy said:
To keep you updated:
You are able to root Android without unlocking the bootloader, keyword: temporary root.
Even though it is possible in some cases to obtain root access without an unlocked bootloader, unlocking the bootloader is required to permanently root a device.
Click to expand...
Click to collapse
What are the uses of temporary root?
This post says it is not possible in Android 6 and newer.
I know that people around here who claim a temporary ROOT isn't possible at newer Android versions. That this still happens / happened here at XDA doesn't make things true.
xXx yYy said:
I know that people around here who claim a temporary ROOT isn't possible at newer Android versions. That this still happens / happened here at XDA doesn't make things true.
Click to expand...
Click to collapse
Can you provide more information on this? Even links to existing posts would also do fine.
I'm interested to know if it can be used to debloat the system without tripping Knox or other disadvantages of an unlocked bootloader.
TheMystic said:
To root your phone, you'll need to unlock the bootloader first.
If you unlock the bootloader, it will erase your internal storage and all files will be lost.
Is your bootloader unlocked as of now?
Click to expand...
Click to collapse
I had some photos and I was done soft for the phone and lost my photos and screenshot
My phone is a Sony Xperia xz1 compact.. Do you mean to activate this option?
shadyhoo said:
I had some photos and I was done soft for the phone and lost my photos and screenshot
My phone is a Sony Xperia xz1 compact.. Do you mean to activate this option?
Click to expand...
Click to collapse
Activating that option is just the first step. There are other things to do to unlock the bootloader.
Since your bootloader is locked as I expected, rooting to recover files is out of question now. That's because if you follow steps to unlock the bootloader, it will wipe everything on your phone. The question of recovery won't arise.
xXx yYy said:
To keep you updated:
You are able to root Android without unlocking the bootloader, keyword: temporary root.
Even though it is possible in some cases to obtain root access without an unlocked bootloader, unlocking the bootloader is required to permanently root a device.
Click to expand...
Click to collapse
My phone is sony xperia xz1 compact
If you root the phone, will this cause a problem with banking financial applications?
is it possible to completely remove the root after that without any problem or I will need to make a new software?
As I can see you've no idea what rooting Android means: it's simply spoken adding SU binary to Android's
filesystem - preferredly put it into RW-mounted /data/local/tmp directory. My recommendation: Become familiar with this, e.g. look inside here.
xXx yYy said:
I know that people around here who claim a temporary ROOT isn't possible at newer Android versions. That this still happens / happened here at XDA doesn't make things true.
Click to expand...
Click to collapse
So why not just teach us ignorant noobs and grab the cash?
I didn't even exclude exploits (such as mtk-su) in my bounty, I just limited to a real android device phone or tablet
alecxs said:
get yourself a smartphone and learn the basics. I will pay $ 100 if you show any proof of your magic temporary root.
Click to expand...
Click to collapse
@shadyhoo if you factory resetted the device during update, your data is already lost.
You can root your phone after bootloader is unlocked. There might be a way to cheat bootloader and root with Magisk, but still the chances to recover any data is very low to zero. On flash memory the data is discarded right on deletion, recovery tools on file system level won't work because only the emmc flash memory controller (which runs it's own proprietary firmware) knows where the data is located. Only data that isn't discarded yet might be recoverable if it's not too long ago deleted.
It would be possible to get a dump of /dev/block/dm-0 and run extundelete if custom recovery were previously installed. Unfortunately the TWRP for Sony Xperia xz1 compact AFAIR requires custom kernel that supports FOTAKernel partition, boot image must include ramdisk extraction utility extract_elf_ramdisk for installing custom recovery. So this is a showstopper even on cheated bootloader lock.
you can however try to flash magisk patched boot image in EDL mode and see if that passes locked bootloader anyway, if the boot.img is properly AVB signed. if phone is rooted you can dump /dev/block/dm-0 during runtime.
But first clarify how the data was deleted. If a factory reset during the update occured it's absolutely pointless, because once the disk encryption key has changed the data is 100 % unrecoverable.
alecxs said:
So why not just teach us ignorant noobs and grab the cash?
I didn't even exclude exploits (such as mtk-su) in my bounty, I just limited to a real android device phone or tablet
@shadyhoo if you factory resetted the device during update, your data is already lost.
You can root your phone after bootloader is unlocked. There might be a way to cheat bootloader and root with Magisk, but still the chances to recover any data is very low to zero. On flash memory the data is discarded right on deletion, recovery tools on file system level won't work because only the emmc flash memory controller (which runs it's own proprietary firmware) knows where the data is located. Only data that isn't discarded yet might be recoverable if it's not too long ago deleted.
It would be possible to get a dump of /dev/block/dm-0 and run extundelete if custom recovery were previously installed. Unfortunately the TWRP for Sony Xperia xz1 compact AFAIR requires custom kernel that supports FOTAKernel partition, boot image must include ramdisk extraction utility extract_elf_ramdisk for installing custom recovery. So this is a showstopper even on cheated bootloader lock.
you can however try to flash magisk patched boot image in EDL mode and see if that passes locked bootloader anyway, if the boot.img is properly AVB signed. if phone is rooted you can dump /dev/block/dm-0 during runtime.
But first clarify how the data was deleted. If a factory reset during the update occured it's absolutely pointless, because once the disk encryption key has changed the data is 100 % unrecoverable.
Click to expand...
Click to collapse
That's what happened to me an error occurred and the phone froze and then rebooted continuously, it never works, I tried to turn it on for a whole day uselessly bootloop continuously ,
I connected the phone. With a pc using sony companion pc program to repair software, app tell me will erase every thing while installing a new software and erased everything, and the phone appeared as a completely new object
through Google backup downloaded applications, messages, etc.,
but personal photos and files do not exist, and this is what I'm looking for
Do I have any chance to get my photos back or is there no chance ?
shadyhoo said:
I connected the phone. With a pc using sony companion pc program to repair software, app tell me will erase every thing while installing a new software and erased everything, and the phone appeared as a completely new object
Click to expand...
Click to collapse
This counts as factory reset, therefore no chance sorry.
I'm sad to see so many people get into this position.
Backing up the data to MyMegaApp can be complicated because some of that is stored in /data/data/com.mymegaapp/...
Some of that is stored in /sdcard/Android/data/com.mymegaapp/...
Photos are generally stored in /sdcard/DCIM/Camera and that is trivial to backup.
Photos are probably the most valuable thing you have on your phone.
For Windows user, you can use my adbsync.exe in my sig.
Here is one line out of my "sync" script (actually a makefile):
Code:
adbsync /hscu /s C:\Handy\MotoG storage/emulated/0/DCIM/Camera
So at the same time I make sure that all my books and guitar transcriptions are on my device I also backup all the photos.
This probably happens multiple times a week.
And of course I backup my desktop too.
Renate said:
This probably happens multiple times a week.
And of course I backup my desktop too.
Click to expand...
Click to collapse
This. Or just do not care attitude. I still had that when the 1st mSD died. 2nd was bad, about half year of photos and such went. Still hoping to recover it somehow. Then 3rd one went not so long ago. Windows "fixed" it, but now it has some folder added, with files that I don't what they all are... less than a month of damage this time...
So, like Renate said, take backups and take them often.
Adbsync is really good indeed.
Although the usage instructions might need some more details/examples like above...
(Just like some of Renate's other progs - might... )
edit a typo
CXZa said:
Although the usage instructions might need some more details/examples like above...
(Just like some of Renate's other progs - might... )
Click to expand...
Click to collapse
Mmm, probably guilty. You can always ask though.
I always say that I wouldn't cry if a truck ran over my Android.
That is, as long as at the time the device wasn't in my pocket.
Renate said:
You can always ask though.
Click to expand...
Click to collapse
That's not how it works... people just don't realize the potential of your programs that way..
Probably i'm not any better in that though.. lol.
CXZa said:
That's not how it works... people just don't realize the potential of your programs that way..
Click to expand...
Click to collapse
Yeah, I probably should add some examples to some things.
Edit: I added some examples and stuff. Happy(er)?
http://www.temblast.com/adbsync.htm
I was looking in the previous days to recover data from the phone and found a lot of programs, most of which require root for mobile and are not free, meaning that if I want to restore some files, I have to root and also format the phone!! And you all say that it is almost impossible to return files after formatting, so what do all these programs that require rooting the phone do?! I do not understand the usefulness of such programs
Related
Alright, where do I start?
So I'm not really and expert on flashing stuff on Android. I was pretty comfy not rooting my phone for more than a year. TBH, I didn't really need it, because I was not a power user, but I've recently installed a root app called King User (King Root, etc.). Before you say anything... YES! I know it is the lazy way to do it. It made things easy for the very few apps I could not use without root permission. However, when I received the latest OTA (5.1.1. security update) I had to disable root authorization in order to install it. So I disabled it using the app's built in authorization setting.
The OTA update failed and gave me the error with the opened up android and the red exclamation mark. So I thought that the app messed something up. Disabling in house did nothing. Uninstalling it did nothing. So I decided to replace it with SuperSU using this guide: http://forum.xda-developers.com/general/help/replace-kinguser-supersu-t2903003. I bet I'm not the only one who had problems after doing this. This, obviously, made things even worse. After SuperSU deleted KingUser and updated itself the phone remained stuck inside a bootloop. So I figured this replacement process messed up permissions.
Here is where it gets tricky, or rather stupid... My bootloader is locked and I have no custom recovery (because like I said, I just needed temporary root access for a couple of apps and wanted to avoid the hassle). When I enter Recovery mode in default fastboot it gives me the "No command" error (probably because of SuperSU permission). Now I don't even know if the phone is rooted or not. USB debugging was not enabled last time the phone was on and now I think I'm stuck in this point where nothing works without something else. I've been reading a couple of threads around here and elsewhere and I don't know what to do next... Doing a full recovery now would probably be asking for a lot, but right now, I would be happy if I could just do a factory reset or something...
Anyone?
val3nteen said:
Alright, where do I start?
So I'm not really and expert on flashing stuff on Android. I was pretty comfy not rooting my phone for more than a year. TBH, I didn't really need it, because I was not a power user, but I've recently installed a root app called King User (King Root, etc.). Before you say anything... YES! I know it is the lazy way to do it. It made things easy for the very few apps I could not use without root permission. However, when I received the latest OTA (5.1.1. security update) I had to disable root authorization in order to install it. So I disabled it using the app's built in authorization setting.
The OTA update failed and gave me the error with the opened up android and the red exclamation mark. So I thought that the app messed something up. Disabling in house did nothing. Uninstalling it did nothing. So I decided to replace it with SuperSU using this guide: http://forum.xda-developers.com/general/help/replace-kinguser-supersu-t2903003. I bet I'm not the only one who had problems after doing this. This, obviously, made things even worse. After SuperSU deleted KingUser and updated itself the phone remained stuck inside a bootloop. So I figured this replacement process messed up permissions.
Here is where it gets tricky, or rather stupid... My bootloader is locked and I have no custom recovery (because like I said, I just needed temporary root access for a couple of apps and wanted to avoid the hassle). When I enter Recovery mode in default fastboot it gives me the "No command" error (probably because of SuperSU permission). Now I don't even know if the phone is rooted or not. USB debugging was not enabled last time the phone was on and now I think I'm stuck in this point where nothing works without something else. I've been reading a couple of threads around here and elsewhere and I don't know what to do next... Doing a full recovery now would probably be asking for a lot, but right now, I would be happy if I could just do a factory reset or something...
Anyone?
Click to expand...
Click to collapse
Start here, http://forum.xda-developers.com/showthread.php?p=53439068. I'd return to stock and start all over, it will wipe your device, see the return to stock thread linked there. Then don't be lazy and read some more in the thread I linked you to. The n5 is one of the easiest devices to work with and you don't need kingroot, tool kits and junk like that
Sent from my Nexus 5 using XDA Free mobile app
You should flash TWRP custom recovery on your phone that way you can copy your personal data to your pc first, then you should flash the factory image
deelan_chan said:
You should flash TWRP custom recovery on your phone that way you can copy your personal data to your pc first, then you should flash the factory image
Click to expand...
Click to collapse
Thanks, but that is not possible, as I have not enabled USB debugging before bootloop. I need to unlock the bootloader (wipe) to install TWRP and backup data.
Can you get into fastboot mode? You can flash twrp from there no USB debugging needed
Sent from my Nexus 5 using Tapatalk
Problem is his bootloader is locked, so follow fastboot for unlocking bootloader and then clean install latest factory image. Also, flash twrp after everything is working (and relock bootloader if you want) so this does not happen again.
wangdaning said:
Problem is his bootloader is locked, so follow fastboot for unlocking bootloader and then clean install latest factory image. Also, flash twrp after everything is working (and relock bootloader if you want) so this does not happen again.
Click to expand...
Click to collapse
Did just that. All fine now. However, I had to flash all .img files separately in fastboot (system, boot, cache, etc.), because adb was not working. Had some problems with the drivers. The device did not show up correctly within device manager. Fortunately, I did not loose anything. Had all my contacts and apps backed up with Google.
Thanks for all advice! I appreciate everyone's guidance.
val3nteen said:
Did just that. All fine now. However, I had to flash all .img files separately in fastboot (system, boot, cache, etc.), because adb was not working. Had some problems with the drivers. The device did not show up correctly within device manager. Fortunately, I did not loose anything. Had all my contacts and apps backed up with Google.
Thanks for all advice! I appreciate everyone's guidance.
Click to expand...
Click to collapse
But it is so fun to use fastboot. I remember almost dunking my wife's G2 until I got it to fastboot. Pain in the butt, but the command prompt does not lie
I stupidly trusted the "transfer to SD card" function and now my Z5 Compact has moved a big chunk of my photos from internal storage to… nowhere. They've been deleted and I’m not sure if I can get them back. I've managed to recover the thumbnails using FonePaw so I'm assuming the original full resolution files are still hanging around somewhere in the internal storage.
All the "recovery" tools I’ve found require your phone to be rooted in order to recover the deleted files from the internal storage. I'm aware that, in order to root the phone, the bootloader needs to be unlocked but that there are issues with losing DRM keys and the impact of that on some of the phone’s functions (specifically a number of the camera features). Given the camera was the primary reason I purchased this phone, I am reluctant to do something that messes with that, especially since this is the second handset as the first one was replaced under warranty after only three months (and this one still has 4 months of warranty left and has been having intermittent issues). There is also the issue that unlocking the bootloader factory resets the phone and therefore wipes all the data.
I know there is a bit of a workaround in that I can downgrade the firmware from Marshmallow to Lollipop and temporarily root the phone in order to backup the TA partition so I can restore the DRM keys et al after unlocking the bootloader and rooting the phone. Again, as I understand it the firmware downgrade will wipe my phone.
Normally wiping my phone wouldn’t bother me beyond being a pain to reinstall apps etc. What concerns me is that, given my missing files are likely floating somewhere in the internal storage ether, would a factory reset completely wipe those files from the phone permanently? Or would I likely still be able to recover them using appropriate software even after the reset, downgrade, unlocking of bootloader, and rooting?
I don't know much about it (and I’m willing to find out more for myself) but is it possible to use something like adb backup to back up the whole phone and restore that to the phone after rooting in order to recover the missing files? Or will that also only work on a rooted phone?
If it's unlikely that my missing files would survive the repeated resets during the rooting process then I will probably just take this as a lesson learned the hard way and not bother trying to recover the files. Given the way my luck has been going, this handset will also fail before 12 months and I'll have no warranty – and still no files!
Thank you in advance for any light you can help shed on this dilemma
ontheaisle said:
I stupidly trusted the "transfer to SD card" function and now my Z5 Compact has moved a big chunk of my photos from internal storage to… nowhere. They've been deleted and I’m not sure if I can get them back. I've managed to recover the thumbnails using FonePaw so I'm assuming the original full resolution files are still hanging around somewhere in the internal storage.
All the "recovery" tools I’ve found require your phone to be rooted in order to recover the deleted files from the internal storage. I'm aware that, in order to root the phone, the bootloader needs to be unlocked but that there are issues with losing DRM keys and the impact of that on some of the phone’s functions (specifically a number of the camera features). Given the camera was the primary reason I purchased this phone, I am reluctant to do something that messes with that, especially since this is the second handset as the first one was replaced under warranty after only three months (and this one still has 4 months of warranty left and has been having intermittent issues). There is also the issue that unlocking the bootloader factory resets the phone and therefore wipes all the data.
I know there is a bit of a workaround in that I can downgrade the firmware from Marshmallow to Lollipop and temporarily root the phone in order to backup the TA partition so I can restore the DRM keys et al after unlocking the bootloader and rooting the phone. Again, as I understand it the firmware downgrade will wipe my phone.
Normally wiping my phone wouldn’t bother me beyond being a pain to reinstall apps etc. What concerns me is that, given my missing files are likely floating somewhere in the internal storage ether, would a factory reset completely wipe those files from the phone permanently? Or would I likely still be able to recover them using appropriate software even after the reset, downgrade, unlocking of bootloader, and rooting?
I don't know much about it (and I’m willing to find out more for myself) but is it possible to use something like adb backup to back up the whole phone and restore that to the phone after rooting in order to recover the missing files? Or will that also only work on a rooted phone?
If it's unlikely that my missing files would survive the repeated resets during the rooting process then I will probably just take this as a lesson learned the hard way and not bother trying to recover the files. Given the way my luck has been going, this handset will also fail before 12 months and I'll have no warranty – and still no files!
Thank you in advance for any light you can help shed on this dilemma
Click to expand...
Click to collapse
it won't delete files from external sdcard unless you select to wipe it too!
in this case you cannot recover anything
unlocking means wiping completely sdcard so ... Impossible
:good:
Greetings,
I've been lurking around XDA trying to find good EMUI 5.0 root support.
I've been proposed by the HiCare app to prematurely update to EMUI 5.0 w/ Nougat, and I do say prematurely, since where I'm living (France), no one ever heard of such witchery
However, i seem to understand that TWRP and SuperSU fall a bit on the short side, notably with the decryption algorithms not being implemented yet, courtesy of Huawei making things as difficult as they can. Here it seems that very limited support for the H8's special Kernel is available given Huawei's pain-in-the-ass attitude.
The million dollar question i'm asking the forums today/tonight is "Can the device encryption be disabled, permanently ?". I do understand and acknowledge the potential risks of such procedure, as if my phone gets stolen, indeed my data is at risk, so is my phone with rooting and such nonsense (talking from experience, since i've bricked the poor thing on day one...).
I would like to thank everyone on this forum beforehand, as without this great community, my phone would still be gathering dust waiting some unbrick miracle to happen, shoutout to Team-MT for their Multi-Tool that saved my day
Thank you all.
I'd sure like to know this too. Seems decryption is the biggest hurdle to get around when it comes to anything twrp and su.
If you only need root access I can say that you can have root access and TWRP with Nougat. Not everything is working (access to data partition is tricky) but you can have root.
ViCioPT said:
If you only need root access I can say that you can have root access and TWRP with Nougat. Not everything is working (access to data partition is tricky) but you can have root.
Click to expand...
Click to collapse
Then my question should be "How can i mount /system and /data for flashing ?", since these are the real nightmares.
Do you have a quick explanation or tutorial to provide me please ?
Thank you
ViCioPT said:
If you only need root access I can say that you can have root access and TWRP with Nougat. Not everything is working (access to data partition is tricky) but you can have root.
Click to expand...
Click to collapse
I'm not sure if I need access to the data partition. All I'd like is AdAway which I believe modifies the hosts file in the system partition and Viper4Android which again I believe is in the system partition. What method did you use to do this? Just unlock the bootloader, install which version of TWRP? I see there's a 3.0.2 but there'e the present encryption issue and which version of supersu did you use?
Also, I can find versions of B360 full firmware laying around, but have not seen successful reflashing of it to go back to stock if there's any issues.
DJ Daemonix said:
Greetings,
The million dollar question i'm asking..
Click to expand...
Click to collapse
You simply format the data partition in TWRP and encryption is gone. I think you (don't remember) have to flash the EU region specific Nougat update .ZIP afterwards. Yes, I have first hand experience.
and To do root to a pixel is worth it??
oraned said:
and To do root to a pixel is worth it??
Click to expand...
Click to collapse
Yes.
It's a personal preference. I am rooted for Titanium backup, Adaway, and Flash kernel.
Sent from my Pixel 2 using Tapatalk
Other than OTA updates requiring sideloading, what are the drawbacks of rooting? Does Google Pay still work? Are there any apps which will fail to run? Any other negatives?
huladaddy said:
Other than OTA updates requiring sideloading, what are the drawbacks of rooting? Does Google Pay still work? Are there any apps which will fail to run? Any other negatives?
Click to expand...
Click to collapse
http://lmgtfy.com/?q=why+to+not+root+android
System rooting, if done properly, is just adding the (call it file or utility - it's both from a Linux viewpoint) file su to the system, so it's not a matter of damaging the phone or rendering it useless. And with Magisk (systemless rooting) it's even easier. Magisk will restore the boot partition (which is all it modifies) so you're left with an untouched phone and, if you really want it stock, you can always boot to TWRP (without installing it), back up your data, copy the backup and /sdcard ro a PC, flash the latest factory ROM, boot to TWRP, restore it, copy /sdcard back and aside from the bootloader being unlocked, you haven't done anything.
The question, though, is whether it's worth it. If you're never going to do anything that needs root access, of course not. It's 10 minutes you'll never get back. But if you want to tweak the kernel, or some other parts of Linux, or you want to run something that will only run with root access, I don't see any reason not to - as long as you know what you're doing and don't brick the phone. (I've recovered from what I call a "semi-hard brick" twice [level 2 tech support actually shipped a replacement phone because they were convinced that it was bad hardware, but I figured out how to recover from the problem in software], so I think the phone is pretty "recoverable".) And if you run Linux, running without su or sudo just feels wrong - it's like running on one leg. Just remember to exit if you run su in a terminal, for the usual reasons - rm -r -d --no-preserve-root will still remove the entire partition. (Which should still be recoverable from, unless you get really stupid.)
Rukbat said:
System rooting, if done properly, is just adding the (call it file or utility - it's both from a Linux viewpoint) file su to the system, so it's not a matter of damaging the phone or rendering it useless. And with Magisk (systemless rooting) it's even easier. Magisk will restore the boot partition (which is all it modifies) so you're left with an untouched phone and, if you really want it stock, you can always boot to TWRP (without installing it), back up your data, copy the backup and /sdcard ro a PC, flash the latest factory ROM, boot to TWRP, restore it, copy /sdcard back and aside from the bootloader being unlocked, you haven't done anything.
The question, though, is whether it's worth it. If you're never going to do anything that needs root access, of course not. It's 10 minutes you'll never get back. But if you want to tweak the kernel, or some other parts of Linux, or you want to run something that will only run with root access, I don't see any reason not to - as long as you know what you're doing and don't brick the phone. (I've recovered from what I call a "semi-hard brick" twice [level 2 tech support actually shipped a replacement phone because they were convinced that it was bad hardware, but I figured out how to recover from the problem in software], so I think the phone is pretty "recoverable".) And if you run Linux, running without su or sudo just feels wrong - it's like running on one leg. Just remember to exit if you run su in a terminal, for the usual reasons - rm -r -d --no-preserve-root will still remove the entire partition. (Which should still be recoverable from, unless you get really stupid.)
Click to expand...
Click to collapse
Thanks for the great reply. My experience has been with rooting Samsung phones, and one of my concerns is tripping an equivalent KNOX meter. Reading between the lines, it appears that the Pixel 2 XL doesn't have anything like that and that it should be possible to completely make the phone stock again. Am I correct?
huladaddy said:
Thanks for the great reply. My experience has been with rooting Samsung phones, and one of my concerns is tripping an equivalent KNOX meter.
Click to expand...
Click to collapse
Maybe Knox make economic sense to Samsung, AT&T and Verizon, but I consider it the worst thing ever done to cellphones.
Reading between the lines, it appears that the Pixel 2 XL doesn't have anything like that and that it should be possible to completely make the phone stock again. Am I correct?
Click to expand...
Click to collapse
Unless you format the bootloader partition (which would take a bit of doing). I can imagine it happening, but after 45 years of developing software, I can't figure out how to do it with the tools available.
I like to root for Titanium backup, Adaway, Solid Explorer, Custom kernels, Magisk Modules, ...
This phone has the ringtone and notification volumes mixed. Root is worth it to have that separated; sadly I'm on Verizon. Other than that I'm pretty content.....
Hi all,
I just got my Pixel 7 Pro few hours ago and I'm followed the instruction to copy my app and data from my Pixel 4. But it seems that some apps are not restored and some are restored but no data.
Is there anyone who can recommend a tool to backup data on my Pixel 4 and then restore them on Pixel 7 Pro (I would like to avoid to root it)? I should be able to find the APK to re-install some of the apps.
I tried Helium (Carbon) (I used it many years ago) but some apps cannot be backup (Helium says "not allowed").
Thanks a lot,
Axello
If the apps you are trying to restore are 32bit apps they will not restore, or work any longer.
jaseman said:
If the apps you are trying to restore are 32bit apps they will not restore, or work any longer.
Click to expand...
Click to collapse
Thanks Jaseman.
Since I moved from my Pixel 4, I assumed my apps are not 32-bit.
I'm more interested to find a way to backup the data from my Pixel 4 to restore in my Pixel 7 Pro. Any idea?
axello said:
Thanks Jaseman.
Since I moved from my Pixel 4, I assumed my apps are not 32-bit.
I'm more interested to find a way to backup the data from my Pixel 4 to restore in my Pixel 7 Pro. Any idea?
Click to expand...
Click to collapse
axello said:
...
Is there anyone who can recommend a tool to backup data on my Pixel 4 and then restore them on Pixel 7 Pro (I would like to avoid to root it)? I should be able to find the APK to re-install some of the apps.
...
Thanks a lot,
Axello
Click to expand...
Click to collapse
Usually, as a rule of thumb, you need to be able to root both devices in order to transfer the data part of backups....
I could be wrong here; but isn't there ways to install apps through adb and/or backup and restore through adb? Maybe someone else out there can help....
You could always unlock bootloader, root, transfer apk's and data, then unroot and even re-lock bootloader (I do NOT recommend doing this last part as many people have bricked their device doing so unnecessarily...)...
If you do go that route, a lot of people are using Swift Backup with almost complete success and/or I saw a couple of people still using Migrate....
I personally haven't had issues with Swift, but I transferred most everything through the cord; but on the select times I used them for apps that didn't come from the Play Store, it worked perfectly...
simplepinoi177 said:
Usually, as a rule of thumb, you need to be able to root both devices in order to transfer the data part of backups....
I could be wrong here; but isn't there ways to install apps through adb and/or backup and restore through adb? Maybe someone else out there can help....
You could always unlock bootloader, root, transfer apk's and data, then unroot and even re-lock bootloader (I do NOT recommend doing this last part as many people have bricked their device doing so unnecessarily...)...
If you do go that route, a lot of people are using Swift Backup with almost complete success and/or I saw a couple of people still using Migrate....
I personally haven't had issues with Swift, but I transferred most everything through the cord; but on the select times I used them for apps that didn't come from the Play Store, it worked perfectly...
Click to expand...
Click to collapse
Thanks Simplepinoi177,
I have never root my phones and I'm worried to do something wrong and break it.
I'll see if I need to setup these so one by one except if there is anyone else with another suggestion.
Axello
Is root easy/safe?
Would Google updates still be pushed on the phone without issue?
I think I saw some post about root, I'll go read them but I'm still concern I am not knowledgeable enough to do it...
axello said:
Is root easy/safe?
Would Google updates still be pushed on the phone without issue?
I think I saw some post about root, I'll go read them but I'm still concern I am not knowledgeable enough to do it...
Click to expand...
Click to collapse
I would say that basic rooting is relatively safe; in most cases if all else fails, you can simply load up bootloader mode and flash the stock factory image to restore your phone. Unless you are installing custom ROMs, kernels, or modded Magisk or some modules, you should be safe as attempting to apply those things (instead of merely just having root access) is what has a higher risk of bricking/bootloops where you can't access recovery or bootloader mode.
But I just realized that you are attempting to transfer data from a Pixel 4. In order to root the Pixel 4 to get access to the app data, you would have to unlock the bootloader which factory resets the phone -- so the point is rendered moot and goes against the whole point.
So, I guess I don't have anything else to suggest as having root access seems to be the only real way of accessing and transferring/backing-up app data.
Again, you might ask someone more knowledgeable if it's possible to use the adb commands to backup and restore apps with their data....
simplepinoi177 said:
I would say that basic rooting is relatively safe; in most cases if all else fails, you can simply load up bootloader mode and flash the stock factory image to restore your phone. Unless you are installing custom ROMs, kernels, or modded Magisk or some modules, you should be safe as attempting to apply those things (instead of merely just having root access) is what has a higher risk of bricking/bootloops where you can't access recovery or bootloader mode.
But I just realized that you are attempting to transfer data from a Pixel 4. In order to root the Pixel 4 to get access to the app data, you would have to unlock the bootloader which factory resets the phone -- so the point is rendered moot and goes against the whole point.
So, I guess I don't have anything else to suggest as having root access seems to be the only real way of accessing and transferring/backing-up app data.
Again, you might ask someone more knowledgeable if it's possible to use the adb commands to backup and restore apps with their data....
Click to expand...
Click to collapse
Thanks a lot for your help, greatly appreciated.
Yes, maybe there is not much choice then. One of the problem is an app that didn't get the data transferred and I cannot login anymore (company has bankrupted)