Related
Hi guys,
I've been playing around with my Nexus S for about 3 weeks and I've decided to root it, but I have some question, I've been searching the answers in older posts but it's not quite clear yet, hope you can help me.
When I unlocked the bootloader, what kind of data will be wiped? It's just the SD card or also all the apps I've already downloaded? what about SMS, pictures and videos?
Is there anyway I can backup that data considering I haven't root it yet???
Thanks in advance.
dont do it man. i just got my phone yesterday at 1 pm and its now 12am and its bricked by lack of support from the cummunity. i studyied and studied 4 around 10 hours. then bricked my device. and i have a good idea i wont be getting a replacement this time
LINKSLOVESANDROID said:
dont do it man. i just got my phone yesterday at 1 pm and its now 12am and its bricked by lack of support from the cummunity. i studyied and studied 4 around 10 hours. then bricked my device. and i have a good idea i wont be getting a replacement this time
Click to expand...
Click to collapse
lol what? its nobodys fault but your own. all the resources are available, just because somebody isnt responding to your threads and holding your hand to restore a nandriod backup doesnt make it a "lack of a community".. and your phone isn't bricked, it can be recovered but you are too close-minded and cant install Clockwork Recovery / get drivers working
The data that will be wiped are most likely your SMS/settings/etc. This is standard procedure. And its something you'll go through a lot when you are using custom ROMs.
There are complete instructions for rooting, unrooting and unbricking your phone. It's all here in the forums, and many other places, you just have to look and learn. I read for two weeks before I unlocked and loaded a ROM into my NS.
If you don't have a need to root your phone I wouldn't do it just because you can. I wanted to run the Voodoo app so I had to root and load a ROM. It took a little while but it was painless and I liked learning about the Android system.
You do have to backup your app and your SD, but that was the easy part.
It's close to impossible to brick a nexus device. They purposely come with totally open boot loaders specifically for that purpose!
RogerPodacter said:
It's close to impossible to brick a nexus device. They purposely come with totally open boot loaders specifically for that purpose!
Click to expand...
Click to collapse
its not only Nexus devices but like I said people are using the term brick wrong. with these new phones coming out, a lot of them are hard to brick.
if you're phone is able to get into recovery/start/download mode (odin not popular but still an option)/bootloader then its not bricked.
if its unable to start in any form or way.. its considered a brick. please stop using the term in its wrong definition.
"brick" describes a device that cannot function in any capacity (such as a device with damaged firmware)
In the strictest sense of the term, bricking must imply that software error has rendered the device completely unrecoverable without some hardware replacement.
http://en.wikipedia.org/wiki/Brick_(electronics)
Click to expand...
Click to collapse
I think guys you have lost focus about my question, it's not about how to root (there is a lot of info about), it's about what kind of data will be wiped and how to back it up
Netconn said:
You do have to backup your app and your SD, but that was the easy part.
Click to expand...
Click to collapse
What's the best way to do it? It's there an app or I have to day it by myself?
Make a nandroid backup first and foremost! Use Titanium Backup to make a backup of all your apps. If you want a backup of your sms, go sms pro really does a great job of that. Dont forget your contacts as well! Then copy your sd card and place it on the hard drive of your computer. When you unlock the bootloader, it does wipe your sd card. Once your unlocked and rooted, you should be able to restore everything once you replace the copy of your sd card back on the phone. Coming over from a Vibrant, I was nervous about rooting the phone but its an easy process. Just take your time and do lots of reading! Hope this helps!
Thenx, but I still have one doubt, if I haven't root my phone yet, will nandroid or titanium work?
Sent from my Nexus S using XDA App
Woops..yeah, your right there. Too quick to reply. I followed this method here..
http://forum.xda-developers.com/showthread.php?t=895545
and had no problems. Once you get unlocked/rooted and clockwork recovery, then you can make the fore mentioned backups. Export your contacts to the sd card then copy the sd card to the hard drive of your computer before unlocking the boot loader. I do not think apps get affected during the sd wipe unless you have them stored there.
zephiK said:
its not only Nexus devices but like I said people are using the term brick wrong. with these new phones coming out, a lot of them are hard to brick.
if you're phone is able to get into recovery/start/download mode (odin not popular but still an option)/bootloader then its not bricked.
if its unable to start in any form or way.. its considered a brick. please stop using the term in its wrong definition.
Click to expand...
Click to collapse
i followed the instructions to flash gri74 back to stock and my phone wont turn on, wont goto any mode, wont read that its hookedup to my pc
isnt that what we call a brick? ive had issues on a galaxy s with this game issue. htc devices i can fly through the root procedure but i got this 1 rooted, tried reflashing to stock and the phone wont turn on at all.
may i suggest a noob proof guide|? i postted 1 in the htc desire forum and people love it. yesterday i returned a moto xoom because ti was overheating , got a nexus s and 2day il b returning that because it wont turn on. can any1 help me think of a good idea i can tell the future shop return people?
kmhil said:
I think guys you have lost focus about my question, it's not about how to root (there is a lot of info about), it's about what kind of data will be wiped and how to back it up
What's the best way to do it? It's there an app or I have to day it by myself?
Click to expand...
Click to collapse
you are forced to lose your data to initially root your device. then after that point, you can always create backups and never lose data again while you switch between ROMs and flashing etc. but i think to initially root, you have to lose everything. not the sd card though.
LINKSLOVESANDROID said:
i followed the instructions to flash gri74 back to stock and my phone wont turn on, wont goto any mode, wont read that its hookedup to my pc
isnt that what we call a brick? ive had issues on a galaxy s with this game issue. htc devices i can fly through the root procedure but i got this 1 rooted, tried reflashing to stock and the phone wont turn on at all.
Click to expand...
Click to collapse
Do keep in mind, we don't have an i9020 or an i9023, we have an i9020A So the instruction out there all need to take that into considerations. I rooted mine fine with no "Bricking" I had to follow the instruction for the i9023, but it worked. I figure it took me all of 1 minute to root my phone. Admitedly, the "One click root" for the Galaxy series was easier.
I try to make it a point to never be the "First" person to do something on their phone. Much safer that way.
I also find it very unusual that you've managed to brick two phones, I've also had the pleasure of owning the telus fascinate, and not once did i get it bricked, I tried Bionics, CM7, Darky's and a bunch of other ones. Just never mess with the boot loader. When you went back to stock, did you make sure it was a stock ROM for the I9020A?
Have you tried connecting the USB to a computer, holding the volume up (or in the case of the galaxy, both up and down) While powering on the device? I've had to use that a few times to recover my galaxy (Thank you odin!!).
Now in regards to the OP, I would recommend using a program like Ti to back everything up, unlock the bootloader then restore from Ti, it's a little more hassel, but you can pretty much keep your settings and data. Personally, i rooted my phone before configuring a single thing on it.
kmhil said:
Thenx, but I still have one doubt, if I haven't root my phone yet, will nandroid or titanium work?
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
there is no way to make a good backup without rooting.
basically yes, you will lose all your settings
there are a few apps you can use to backup your apk before unlocing/rooting the phone.
look for App admin on market https://market.android.com/details?id=az.mecid.appadmin&feature=search_result
the stuff backed to SD does not get wiped
only the internal storage stuff
LINKSLOVESANDROID said:
dont do it man. i just got my phone yesterday at 1 pm and its now 12am and its bricked by lack of support from the cummunity. i studyied and studied 4 around 10 hours. then bricked my device. and i have a good idea i wont be getting a replacement this time
Click to expand...
Click to collapse
i took about 12 minutes total to unlock my bootloader, flash clockwork, and flash a custom rom. its not difficult if you pay attention to what you read. youre phone is not bricked. btw, i read your threads. if you werent so demanding, i would have helped. use the pdanet website the next time you need to install the proper driver, and follow the directions that they give you.
When I unlocked I used Astro to back up my apps, I turned on the Google data sync to back up my contacts and I did a back up of my SD on my computer.
When the unlock and recovery was done NS asked for my Google account then it restored all my contacts, Astro restored all my apps and I restored my files from my computer. A few steps but not difficult at all.
You will have to redo your accounts and data, and maybe an app or two won't load but the market will show them installed, just reinstall any that didn't.
Make sure you follow the directions properly in the forum. I had to use two computers to get it to work, but it did work and nothing was damaged.
With all that said.... This was the first time I have ever owned or altered an Android phone. Sure I was nervous... Now I'm hooked.. haha
I wound up using NSCollab .17 so far so good..
First thing I did when I got my phone was fastboot oem unlock.
Even if you don't want to root, use another ROM. Fastboot unlock it so your data doesn't get wiped.
If your hardware and everything seems okay, then flash Clockwork Recovery and do a nandroid backup so you can restore to pre-flashing point if you need it for OEM purposes.
Afterwards, go crazy and flash like theres no tomorrow and find something that you'll like.
And agreed with simms. You've made so made so many threads about this. I would help you step by step but I've been busy so I can't do that anymore. But if you search, you'll find about two or three threads where I did help somebody get their phone to a working state.
The basic idea is... if your phone doesn't boot but you can get to recovery.
- Download a ROM or Nandroid backup
- Install USB drivers
- Fastboot oem unlock (if you haven't)
- fastboot flash recovery recovery.img (or whatever the recovery.img is named) should be in /sdk/tools
- reboot into recovery (adb reboot recovery)
- mount and storage: mount USB, put the nandroid backup or ROM onto phone
- nandroid restore or flash a ROM (wipe factory,dalvik,cache --> flash ROM (if its CM7.. flash gapps afterwards)
- reboot
your phone boots. alternatively, you can use Odin but thats not a popular method but the choice is available if you wish to go towards that approach
in the worse worse possible case scenario there is always ODIN to the rescue
Why did you guys wait at all?
Once i got the phone i immediately plugged it into my computer and rooted it.
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
First off, this is not my phone, but my dad's, so I'd really like to avoid a factory reset. Also, the phone isn't rooted.
He managed to install some Wifi Tools app, which is a quite an ugly virus. Even the reviews say what an absolute crap of an app this is. Its even messing with the phone's mobile network connectivity.
So, the issue is, I can't remove this app. I can go into Device admins, and select deactivate on the bottom right part of the screen , but I can't even select 'Deactivate' in the window that pops up afterwards. Even if I tap furiuosly on the screen, nothing happens. After that, the settings app is all messed up. It doesnt react to most inputs, like it's frozen, or I can only scroll, but can't enter any subsections. 'Curiously', I can't enter the Security subsection if I don't restart the Settings app, even if everything else works.
How the hell do I remove this hellspawn? I know I can't do it through ADB because it has Admin privileges. Admin privileges that can't be revoked.
Hello,
Your options are:
1)root the device and then you can get rid of the app.
2)use the factory reset option in system settings to reset the device.
3)boot to stock recovery and use the factory reset and wipe cache option in recovery.
4)the last option you won't need but you can restore the stock firmware via whatever flashtool the device uses.
If you are trying to avoid resetting the device to prevent losing data then try rooting the device and just use root access to remove the app. Depending on the rooting method you won't lose any saved data.
If you don't like either of those options, try posting your question in the forum linked below.
http://forum.xda-developers.com/android/help
Thanks for the answer, but I already solved it. I rooted the phone with Framaroot and then nuked it from the phone with Titanium Backup. Afterwards, I locked down root access/rights as best as I could. Better safe than sorry heh.
boki9999 said:
Thanks for the answer, but I already solved it. I rooted the phone with Framaroot and then nuked it from the phone with Titanium Backup. Afterwards, I locked down root access/rights as best as I could. Better safe than sorry heh.
Click to expand...
Click to collapse
You can remove root access if you think its too risky for your dad, if you think he may at some point make a big mistake because of root access I would recommend removing root to avoid getting the device in a situation that nay not be fixable. If you need root later you can re root it like you did this time, you may can even go a step further and install a custom recovery and use it to create a nandroid backup, then if at some point something goes wrong you can just restore the nan droid and be back to how everything was when the backup was created. You might even be able to make the backup then remove root and if you need root back you can restore the band to is and have root to do what needs to be done. Just a few options for you, whatever you think would work best.
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)
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