Related
Hi there,
I am new to xda and new to Android hacking.
What I wanna ask is, (I guess it's of most newbies concern as well), can we have a 100% backup of our system (stock ROM)? Obviously, it is important because:
If we perform an official (OTA) update to a new Android version. And we don't like it. It is possible to get back to the old original one which we are used to. (not everybody likes new things, and/or not every new thing is good)
If our phones are having some problems. And we have to give it back to the company for a fix. In most cases they will flash a new ROM for us. If we wanna keep using the old one (explained in #1), we have to keep a copy of it by ourselves.
If we want to try new custom ROMs, we may want to switch it back after trying.
Whenever we do any modifications, it's always better to keep a backup/roll-back point. In case anything goes wrong, we have a safeguard.
For the official warranty issue.
Yup I do see there are some official stock ROMs downloads for some particular phones. But those are not really a backup of our original ROMs. And it's always hard to verify if those downloads are the original official releases. And, if those downloads are 100% stock ROMs, this means some guys out there could make it, so what is the way to do so?
Or, how those mobile phone companies do it in their labs?
I have been doing researches on this topic for a few days. Some posts claim that their methods are "backup stock ROM" or "backup before rooting". But after digging into it, they requires rooting and/or flashing CWM. Here comes a few questions:
Questions
Rooting will in fact changes some files/data of the system. So backup after root is NOT getting the original stock ROM. Is it?
Is there a method to "un-root", so ALL the changes are TOTALLY reverted?
Installing/flashing things like CWM in phone requires rooting, which would make the ROM not original. Is there a way to extract the system backup from a computer externally?
In addition, I have found some related pieces. which could be useful to anyone viewing this post, and might be useful for you to solve this (my) question. :fingers-crossed:
* as I'm a new user, I can't post links directly. Please delete the blank spaces in between.
ht tp://www .modaco .com/topic/351269-backup-original-rom/
In reply #5, user C3C0 raised a method of backing up the original stock ROM without root. But it seems he is flashing CWM and that method is only for ZTE Skate.
adb backup tool of Android SDK
At the first sight i came across this approach, I thought it is the official method to do whole system (ROM) backup (WOW - how nice!). But after studying for a few more posts, I think adb backup can only backup app+app_data, and possibly some system settings only. Am I correct? And also, adb backup is only for ICS (Android 4.0), isn't it?
adb backup usage: ht tp://forum.xda-developers .com/showthread.php?t=1420351
(But mentioned in the bottom of #1 the poster is having some issues on using adb backup. Perhaps there are some bugs and not reliable(?)
One more question on adb backup: Can it backup just one app+app_data, and restore just one app+app_data, without affecting other things? If yes, we don't need to root and don't need Titanium Backup (which requires root) for backup app+app_data. Isn't it?
** In case I have said anything or any terms wrongly in this thread, please DO correct me, for helping me and helping others.
P.S. i am using LG Optimus 3D.
Thanks a lot, wholeheartedly,
midnite_
Backup phone before root
Hello all this is my first post here...woohoo!:fingers-crossed: This forum is amazing as to the amount of information available. I just wish that in looking for what I need to do I did not need to look in so many places. I feel that if I want to root my T-Mobile GS3 that all the information should be in one subsection of the forum, but it is not that simple I guess....lol Anyway any help would be greatly appreciated.
I have a Samsung GS3 with T-Mobile that I want to root. Everyone says to back up the phone before you do it but I am not really seeing how to make a backup before I start. It appears that most of the guides to root just say to backup without telling you how to fo it. Another thing (correct me if I am wrong) I see the nandroid backup that I think is a backup of the phone however it seems to be done after you make changes to the phone and I thought the backup was supposed to be done before you do anything. Is it that there is not a way to make a complete backup with an unrooted phone?
My question is basically the same as the OP here. I have been reading and reading and reading posts here in the forum. There is much information here and much of it is duplicated with slight variances in some of the duplicates. I am not certain as to which rooting method I should use. There seem to be so many choices. As a new person to this forum I will say that you can find just about everything about any phone which is awesome. The hard thing is sifting through the many options to pick one to use for your issue.
I do see that Mr. Robinson has a thread with backups of the original roms. The only thing is that they are default roms that are like an out of the box phone and not my phone with my apps and my settings. That is what I want to backup...My phone with my settings and my apps.
:good: Thank you in advance for any one that can shed some light on this for me and the OP'er
ASharpEdge said:
Hello all this is my first post here...woohoo!:fingers-crossed: This forum is amazing as to the amount of information available. I just wish that in looking for what I need to do I did not need to look in so many places. I feel that if I want to root my T-Mobile GS3 that all the information should be in one subsection of the forum, but it is not that simple I guess....lol Anyway any help would be greatly appreciated.
I have a Samsung GS3 with T-Mobile that I want to root. Everyone says to back up the phone before you do it but I am not really seeing how to make a backup before I start. It appears that most of the guides to root just say to backup without telling you how to fo it. Another thing (correct me if I am wrong) I see the nandroid backup that I think is a backup of the phone however it seems to be done after you make changes to the phone and I thought the backup was supposed to be done before you do anything. Is it that there is not a way to make a complete backup with an unrooted phone?
My question is basically the same as the OP here. I have been reading and reading and reading posts here in the forum. There is much information here and much of it is duplicated with slight variances in some of the duplicates. I am not certain as to which rooting method I should use. There seem to be so many choices. As a new person to this forum I will say that you can find just about everything about any phone which is awesome. The hard thing is sifting through the many options to pick one to use for your issue.
I do see that Mr. Robinson has a thread with backups of the original roms. The only thing is that they are default roms that are like an out of the box phone and not my phone with my apps and my settings. That is what I want to backup...My phone with my settings and my apps.
:good: Thank you in advance for any one that can shed some light on this for me and the OP'er
Click to expand...
Click to collapse
Hi ya,
It's so nice that you are having the same concern as I do.
As far as i know, the approaches of rooting differ from phones to phones. So we may have to find our own specific rooting method in the phone model sub-forums. It won't be hard for your popular S3
I would like to have a look at that Mr. Robinson's thread. If he can backup the stock ROM, those app+app_data wont a big issue (i guess).
cheers,
midnite_
midnite_ said:
Questions
Rooting will in fact changes some files/data of the system. So backup after root is NOT getting the original stock ROM. Is it?
Is there a method to "un-root", so ALL the changes are TOTALLY reverted?
Installing/flashing things like CWM in phone requires rooting, which would make the ROM not original. Is there a way to extract the system backup from a computer externally?
Click to expand...
Click to collapse
Hi midnight, welcome to a new and exciting world of Android and trying new things. First, let me assure you, what you want is NOT something new. People have been doing this type of thing for years. That is flashing and testing roms. As you will learn, it actually becomes quite addictive. We call those folks that get addicted to flashing: Flashaholics or crackflashers, lol
First let me talk about "root". This process consists of unlocking a lower level of the Android system known as the bootloader. Unlocking the bootloader of your device allows you to flash a custom recovery, flashing a custom recovery allows you to flash the Superuser binary and Superuser.apk, This is what allows you to use apps that require "root". The bootloader is not an OS file. So when you are unlocking your bootloader you are not modifying your stock rom. Only when you have flashed the Superuser package have you modified your stock rom. And even that isn't really modifying anything. When you flash the Superuser package, it adds two files to your rom at certain locations of the file system. It adds the Superuser.apk file to system/app and it adds the SU binary to system/bin. Basically you CAN have a totally S-OFF (unlocked) bootloader and still have an entirely stock rom if you want. But the real benifit is flashing a custom recovery like ClockworkMod Recovery and then flash the superuser package.
As far as extracting the stock system, you should try giving adb a go. Do it right now if you like. Ensure you have the android sdk installed and properly set up on your computer and your computer can recognize your phone. Ensure your phone is in debugging mode, connect your phone to your computer, open up a command window, and run this command:
Code:
adb pull \
This command will pull everything off your phone except for data which is where your market or Google Play apps are stored.
Beyond XDA there are aso more resources to learn from. For example, http://www.android.com is a good place to start, and to learn more about adb check out http://developer.android.com/tools/help/adb.html
If you need to learn how to setup the sdk here is the place to learn how: http://developer.android.com/sdk/index.html
I'm sure others will add to this as well which is the good thing about this community.
Welcome to XDA, I hope you have fun learning, and maybe share back someday things you learn along the way.
wildstang83 said:
Hi midnight, welcome to a new and exciting world of Android and trying new things. First, let me assure you, what you want is NOT something new. People have been doing this type of thing for years. That is flashing and testing roms. As you will learn, it actually becomes quite addictive. We call those folks that get addicted to flashing: Flashaholics or crackflashers, lol
First let me talk about "root". This process consists of unlocking a lower level of the Android system known as the bootloader. Unlocking the bootloader of your device allows you to flash a custom recovery, flashing a custom recovery allows you to flash the Superuser binary and Superuser.apk, This is what allows you to use apps that require "root". The bootloader is not an OS file. So when you are unlocking your bootloader you are not modifying your stock rom. Only when you have flashed the Superuser package have you modified your stock rom. And even that isn't really modifying anything. When you flash the Superuser package, it adds two files to your rom at certain locations of the file system. It adds the Superuser.apk file to system/app and it adds the SU binary to system/bin. Basically you CAN have a totally S-OFF (unlocked) bootloader and still have an entirely stock rom if you want. But the real benifit is flashing a custom recovery like ClockworkMod Recovery and then flash the superuser package.
As far as extracting the stock system, you should try giving adb a go. Do it right now if you like. Ensure you have the android sdk installed and properly set up on your computer and your computer can recognize your phone. Ensure your phone is in debugging mode, connect your phone to your computer, open up a command window, and run this command:
Code:
adb pull \
This command will pull everything off your phone except for data which is where your market or Google Play apps are stored.
Beyond XDA there are aso more resources to learn from. For example, ht tp://www .android .com is a good place to start, and to learn more about adb check out ht tp://developer .android .com/tools/help/adb.html
If you need to learn how to setup the sdk here is the place to learn how: ht tp://developer .android .com/sdk/index.html
I'm sure others will add to this as well which is the good thing about this community.
Welcome to XDA, I hope you have fun learning, and maybe share back someday things you learn along the way.
Click to expand...
Click to collapse
Hi Wildstang,
Thanks very much for your warm welcome and very informative reply. So are you a Flashaholics or Crackflashers yet?
As I am a newbie, please forgive me if I am asking dumb questions.
As far as I understand,
The steps of root is
1. Unlock the bootloader
2. Flash Superuser binary & Superuser.apk
** does "flash a custom recovery" means "flash Superuser binary & Superuser.apk"?
"Flash Superuser binary & Superuser.apk" is just "add SU binary to system/bin" and "add Superuser.apk to system/app". Then why not just copy them into place?
I just found on the web that "flashing" means replacing the OS of the phone with a new ROM. Would that still keeping the stock ROM?
To have a backup of the original stock ROM, can I
1. Unlock the bootloader
2. Flash Superuser binary & Superuser.apk
3. Perform the backup
And later, after I have flashed a new ROM, or whatever I do, as long as I didn't brick it, when I want to rollback my phone to its original, I can
1. Restore the backup
2. Delete "SU binary in system/bin" and "Superuser.apk in system/app"
3. re-lock the bootloader
Is this correct?
I don't mean to challenge you. But does adb pull \ really backup the system, or just all the files?
Thanks very much again!
midnite_
Hey midnite_,
I am a newbie too and have a lot of blank spots in my understanding of what we can do with android. I also came here with same question. I found how to root, this isn't a secret. Like you, I want to know how do I fix it if I break it.
So, with regards to your questions.
1. Unlock the bootloader
Not clear on this one, as not every tutorial even mentions this part. My feeling is that this might be specific to some phones, like HTC.
2. Flash Custom Recovery (such as AmonRa, CWR, TWRP...)
Recovery is an intermediate stage of phone booting process after bootloader but before OS.
It is there to allow OTA (Over the air) updates. During those, the OS is halted and replaced with a newer one.
What this means for us is that the recovery is capable of replacing OS (ROM - are these terms interchangeable?).
Recovery is the same as hidden partition on windows, that is sometimes present on a PC. It has a limited interface.
It can replace one OS image with another. It probably checks the checksum and creates the new one after the update. It is probably the gatekeeper.
Stock recovery will not replace OS with an image from SD card or from PC through USB. Only OTA.
This is the reason for flashing the custom (hacked) recovery on.
Custom recovery is made to allow additional options, such as allowing image sources such as PC or SD card, and also a ROM backup (write OS image to PC).
3. Flash update file using "upgrade from SD card" function of custom recovery now in place.
In this step, the Superuser.apk and bin files are placed. Stock recovery will not let us do that.
Also, I think the reason we can't just use ADB to "copy" superuser package to phone is because the system is either running or exists as an image (compressed?), and is probably protective of its modification. (So, likely the superuser package also replaces the checksum that the OS uses to check if it has been compromised?) Yes, this modifies your rom.
I assume that unrooting could be done after this by updating again with a file that removes superuser package and that would make your rom stock again.
4 OR flash custom ROM, which usually includes superuser package. Of course using custom rom means you no longer have stock rom.
To have a backup of original ROM, you would :
1 Unlock bootloader,
2 Flash (install) custom recovery
3 superuser doesn't matter here
4 Use custom recovery function to back up your stock ROM.
I want to know the answers to the rest of your questions as well as some clarifications to mine.
Personally, I am looking for a way to backup the stock recovery as well.
I know there are some people asking about this. The procedure appears to be as follows:
(pieced together so don't take it as a tutorial)
1 Unlock bootloader (again, unclear on this. Also some mention S-OFF and others don't)
2 With USB debugging allowed (meaning connect as device requiring a driver), Connect to a PC with ABD, and a driver installed.
3 From ADB, issue a command "adb boot recoveryimage.name" instead of the usual "adb flash recoveryimage.name".
This will make the phone boot into a custom recovery image that is residing on PC, without first writing it to the phone.
4 Unclear how, but make that custom recovery now being live to back up stock rom to pc.
5 Unclear how, but make that custom recovery now being live to flash either root or custom rom to the phone.
6 Disconnect, reboot the phone. Once in OS, use root privileges to mount recovery partition ? (this makes it visible as drive)
7 Don't know how, but use root privileges to back up now visible stock recovery partition to PC as image.
( This should give you two out of three original parts.)
Keep in mind that even if my peace-by-peace "know-how" ever works, there is at least one clearly faulty step:
The back up of the original state of the boot loader has been never made. I do not know if it is easily can be toggled back and forth from lock to unlock and back without leaving any trace. Also, like yourself, I probably don't quite understand what am I talking about, but I have tried to make as much sense of what I have read here and there.
This is my first smart phone, and my experience with linux is limited to building a minecraft server on MineOS, which was pre-made so that not much was required to make it run. I have "mounted" a partition for the first time last week, trying to break Win7recovery, booting it with Knoppix. This is why I think this is probably will come in play here too, as the recovery partition on W7 was hidden. Until then I didn't understand what mounting means, as windows always does it for you. So, take everything I say with a bunch of salt.
Please, let me know too, if you find out more. I want to flash the hell out of my Prism, but I want to be smart about it.
bump... midnite_ r u still around?
Hi Descent2,
Yes i am still around but i am busy with other stuffs at this moment. Thanks very much for your reply. You have studied a lot and you really did good summarisations. Very informative and I learnt a lot from it. Hope some of the masters or experienced ones would come by and bring us out of the mist
cheers,
midnite_
Descent2 said:
Hey midnite_,
I am a newbie too and have a lot of blank spots in my understanding of what we can do with android. I also came here with same question. I found how to root, this isn't a secret. Like you, I want to know how do I fix it if I break it.
So, with regards to your questions.
1. Unlock the bootloader
Not clear on this one, as not every tutorial even mentions this part. My feeling is that this might be specific to some phones, like HTC.
2. Flash Custom Recovery (such as AmonRa, CWR, TWRP...)
Recovery is an intermediate stage of phone booting process after bootloader but before OS.
It is there to allow OTA (Over the air) updates. During those, the OS is halted and replaced with a newer one.
What this means for us is that the recovery is capable of replacing OS (ROM - are these terms interchangeable?).
Recovery is the same as hidden partition on windows, that is sometimes present on a PC. It has a limited interface.
It can replace one OS image with another. It probably checks the checksum and creates the new one after the update. It is probably the gatekeeper.
Stock recovery will not replace OS with an image from SD card or from PC through USB. Only OTA.
This is the reason for flashing the custom (hacked) recovery on.
Custom recovery is made to allow additional options, such as allowing image sources such as PC or SD card, and also a ROM backup (write OS image to PC).
3. Flash update file using "upgrade from SD card" function of custom recovery now in place.
In this step, the Superuser.apk and bin files are placed. Stock recovery will not let us do that.
Also, I think the reason we can't just use ADB to "copy" superuser package to phone is because the system is either running or exists as an image (compressed?), and is probably protective of its modification. (So, likely the superuser package also replaces the checksum that the OS uses to check if it has been compromised?) Yes, this modifies your rom.
I assume that unrooting could be done after this by updating again with a file that removes superuser package and that would make your rom stock again.
4 OR flash custom ROM, which usually includes superuser package. Of course using custom rom means you no longer have stock rom.
To have a backup of original ROM, you would :
1 Unlock bootloader,
2 Flash (install) custom recovery
3 superuser doesn't matter here
4 Use custom recovery function to back up your stock ROM.
I want to know the answers to the rest of your questions as well as some clarifications to mine.
Personally, I am looking for a way to backup the stock recovery as well.
I know there are some people asking about this. The procedure appears to be as follows:
(pieced together so don't take it as a tutorial)
1 Unlock bootloader (again, unclear on this. Also some mention S-OFF and others don't)
2 With USB debugging allowed (meaning connect as device requiring a driver), Connect to a PC with ABD, and a driver installed.
3 From ADB, issue a command "adb boot recoveryimage.name" instead of the usual "adb flash recoveryimage.name".
This will make the phone boot into a custom recovery image that is residing on PC, without first writing it to the phone.
4 Unclear how, but make that custom recovery now being live to back up stock rom to pc.
5 Unclear how, but make that custom recovery now being live to flash either root or custom rom to the phone.
6 Disconnect, reboot the phone. Once in OS, use root privileges to mount recovery partition ? (this makes it visible as drive)
7 Don't know how, but use root privileges to back up now visible stock recovery partition to PC as image.
( This should give you two out of three original parts.)
Keep in mind that even if my peace-by-peace "know-how" ever works, there is at least one clearly faulty step:
The back up of the original state of the boot loader has been never made. I do not know if it is easily can be toggled back and forth from lock to unlock and back without leaving any trace. Also, like yourself, I probably don't quite understand what am I talking about, but I have tried to make as much sense of what I have read here and there.
This is my first smart phone, and my experience with linux is limited to building a minecraft server on MineOS, which was pre-made so that not much was required to make it run. I have "mounted" a partition for the first time last week, trying to break Win7recovery, booting it with Knoppix. This is why I think this is probably will come in play here too, as the recovery partition on W7 was hidden. Until then I didn't understand what mounting means, as windows always does it for you. So, take everything I say with a bunch of salt.
Please, let me know too, if you find out more. I want to flash the hell out of my Prism, but I want to be smart about it.
Click to expand...
Click to collapse
check here
All your answers can be found here: [REF] [GUIDE] Welcome to your device, the Galaxy S III. For more XDA related issues check here: [GUIDE] - XDA New User Guide - Getting started on XDA
Good Luck!
mf2112
XDA Moderator
ASharpEdge said:
Hello all this is my first post here...woohoo!:fingers-crossed: This forum is amazing as to the amount of information available. I just wish that in looking for what I need to do I did not need to look in so many places. I feel that if I want to root my T-Mobile GS3 that all the information should be in one subsection of the forum, but it is not that simple I guess....lol Anyway any help would be greatly appreciated.
I have a Samsung GS3 with T-Mobile that I want to root. Everyone says to back up the phone before you do it but I am not really seeing how to make a backup before I start. It appears that most of the guides to root just say to backup without telling you how to fo it. Another thing (correct me if I am wrong) I see the nandroid backup that I think is a backup of the phone however it seems to be done after you make changes to the phone and I thought the backup was supposed to be done before you do anything. Is it that there is not a way to make a complete backup with an unrooted phone?
My question is basically the same as the OP here. I have been reading and reading and reading posts here in the forum. There is much information here and much of it is duplicated with slight variances in some of the duplicates. I am not certain as to which rooting method I should use. There seem to be so many choices. As a new person to this forum I will say that you can find just about everything about any phone which is awesome. The hard thing is sifting through the many options to pick one to use for your issue.
I do see that Mr. Robinson has a thread with backups of the original roms. The only thing is that they are default roms that are like an out of the box phone and not my phone with my apps and my settings. That is what I want to backup...My phone with my settings and my apps.
:good: Thank you in advance for any one that can shed some light on this for me and the OP'er
Click to expand...
Click to collapse
Thanks mf2112. But those resources are seem only for GS3. And it seems it is not teaching us to backup our stock ROMs, it provides stock ROMs for us to download instead. Is there a general way to backup our stock ROMs?
Thanks,
midnite_
mf2112 said:
All your answers can be found here: [REF] [GUIDE] Welcome to your device, the Galaxy S III. For more XDA related issues check here: [GUIDE] - XDA New User Guide - Getting started on XDA
Good Luck!
mf2112
XDA Moderator
Click to expand...
Click to collapse
You must unlock your bootloader then flash a custom recovery. You will then use that custom recovery to make a backup of your rom. That backup will be stored on your sd card.
Now, I have tried to help you and so have a couple other folks. You expect us to just give you answers step by step. I am sorry but this is simply not how XDA works. XDA is set up in a way which makes it for any users to find quickly what they want to know. Use the search feature on the site and you will find many answers. I tell you to go do your own research now and be proud of what you learn on your own. And if you cannot, please do not try to modify your phone further, you may just brick it if you aren't careful.
midnite_ said:
Thanks mf2112. But those resources are seem only for GS3. And it seems it is not teaching us to backup our stock ROMs, it provides stock ROMs for us to download instead. Is there a general way to backup our stock ROMs?
Thanks,
midnite_
Click to expand...
Click to collapse
I put in the GS3 links since the OP was using that phone. Every phone will be different so I don't think a general way or guide would be practical.
Sent from my HTC Sensation 4G using xda premium
Welcome to the Kyocera DuraForce super thread
There isn't much information floating around for the DuraForce and I've created this thread to aggregate information as it's found so we have a single place for useful information, hacks, etc.
I'll keep the thread as up to date as possible and organize any information from future posts into the originals so people can find information easier.
There is a Lollipop update available for the device as of early February, 2016. I have found a way for users to update if the OTA fails (see below). I've also updated the below posts with information regarding the Lollipop update and moved the KitKat notes to another location (link for old notes is below)
Ota - lmy47v1218_2217
For those who are having trouble applying a FOTA on the DuraForce, check /cache/fota/xyz_fotalog_123.dat It's a text file that contains a lot of really good info on what is going on during a FOTA. Including errors. Keep a look out for signature mismatch errors.
I had errors with the following files. Took me a few tries to get the OTA applied as each attempt resulted in one error.
Uninstall Xposed (moar hacks)
/system/usr/keylayout/gpio-keys.kl (disable PTT/Speaker buttons)
/system/etc/permissions/platform.xml (sd card "fix")
If trying to address the issues manually does not work, follow the procedure below.
Download "vanilla" system image from HERE (link)
Extract zip file
Ensure at least 2Gb of storage is available for internal data
adb push mmcblk0p21_KVT49L_0617_0132 /storage/sdcard0/
adb shell
su
dd if=/storage/sdcard0/mmcblk0p21_KVT49L_0617_0132 of=/dev/block/mmcblk0p21
Reboot phone once it completes. It will take awhile and not report anything during the process.
After phone boots, run "adb reboot recovery"
Wipe data / factory reset
Wipe cache
Reboot
Run software update
General Notes - Lolipop
Force Reboot: Pwr + Vol Up + Vol Dn + Back + Home + App Switcher buttons for ~10-30 seconds
Root: Use KingRoot from http://king-root.net/ -- I used the android APK successfully
SD cards bigger than 32Gb still do not work correctly on stock firmware
Known Working Customizations
To be determined
KitKat Notes
All previous notes for KitKat have been moved to a document in box. The notes can be found HERE (link)
Sources / Mirror(s)
The OSS drop is available on Kyocera's developer site: http://www.kyoceramobile.com/support/developers/
Misc file mirror: https://nuskunetworks.box.com/s/p5hwq3hboctl0saze0wkcv3jzfefuw45
Do you trust Kingo?
I'm THRILLED to hear you were able to root and freeze all the AT&T crapware. I can't wait to do the same. But how do you feel about Kingo? I'm almost leaning more to keeping the bloat, kind of the devil you know, you know?
kemonine96 said:
Welcome to the Kyocera DuraForce super thread
There isn't much information floating around for the DuraForce and I've created this thread to aggregate information as it's found so we have a single place for useful information, hacks, etc.
I'll keep the thread as up to date as possible and organize any information from future posts into the originals so people can find information easier.
If you're looking for root, look no further than Kingo. I can confirm the Windows version of Kingo is working on the AT&T varient of the DuraForce.
Click to expand...
Click to collapse
tomzweifel said:
How do you feel about Kingo?
Click to expand...
Click to collapse
I've used it a few times over the last year and can only complain it does a sloppier job compared to SuperSU. Every pre-canned root wants to crap all over /system and none is better than the other so long as you get the su binary in a working state IMHO. I know Kingo is harder to clean up after than SuperSU / others but it's a hell of a lot easier to just use Kingo to root and cleanup after. Stacking root exploits and similar like Kingo is doing is a huge PITA and best left to those specializing in such things.
tomzweifel said:
I'm almost leaning more to keeping the bloat, kind of the devil you know, you know?
Click to expand...
Click to collapse
Fair enough, I was able to replace Kingo with SuperSU pretty easily:
Install SuperSU from Play Store
Run SuperSU and update su binary via "Normal" mode
Authorize SuperSU when Kingo prompts
Allow SuperSU to replace su binary
Freeze/Remove Kingo
Reboot and enjoy SuperSU
Optional: cleanup other Kingo remnants
Components to clean up?
Any chance you can steer me towards the "remnants" that need to be cleaned up and where to find them, just to make sure I get it all? I'm probably going to go though this exact process tonight or tomorrow.
Thanks for the information!
kemonine96 said:
I've used it a few times over the last year and can only complain it does a sloppier job compared to SuperSU. Every pre-canned root wants to crap all over /system and none is better than the other so long as you get the su binary in a working state IMHO. I know Kingo is harder to clean up after than SuperSU / others but it's a hell of a lot easier to just use Kingo to root and cleanup after. Stacking root exploits and similar like Kingo is doing is a huge PITA and best left to those specializing in such things.
Fair enough, I was able to replace Kingo with SuperSU pretty easily:
Install SuperSU from Play Store
Run SuperSU and update su binary via "Normal" mode
Authorize SuperSU when Kingo prompts
Allow SuperSU to replace su binary
Freeze/Remove Kingo
Reboot and enjoy SuperSU
Optional: cleanup other Kingo remnants
Click to expand...
Click to collapse
tomzweifel said:
Any chance you can steer me towards the "remnants" that need to be cleaned up and where to find them, just to make sure I get it all? I'm probably going to go though this exact process tonight or tomorrow.
Thanks for the information!
Click to expand...
Click to collapse
Unfortunately I don't have notes on what Kingo leaves around on /system... Some searching online or poking about /system should yield results.
New OTA Update
I just got notified of an available OTA update but I can't find a changelog or any info on it yet. I'll be sure to post it if I find it.
tomzweifel said:
I just got notified of an available OTA update but I can't find a changelog or any info on it yet. I'll be sure to post it if I find it.
Click to expand...
Click to collapse
Please do. I haven't gotten any notifications yet and I'm kinda curious what the OTA will contain.
http://www.att.com/esupport/article.jsp?sid=KB426870&cv=820
Software update includes
Kyocera Remote Lock
Miscellaneous improvements, fixes, and security updates
Dkesler76 said:
http://www.att.com/esupport/article.jsp?sid=KB426870&cv=820
Software update includes
Kyocera Remote Lock
Miscellaneous improvements, fixes, and security updates
Click to expand...
Click to collapse
Thanks for the heads up. Too bad it's not L.
kemonine96 said:
Thanks for the heads up. Too bad it's not L.
Click to expand...
Click to collapse
np yeah i wished it was to lol... seems that my phone wont take the ota i did delete the bloatware....probably why it wont update u know how to force the ota or do u know where i can get the apks to reinstall them to update it... ty dan
Dkesler76 said:
np yeah i wished it was to lol... seems that my phone wont take the ota i did delete the bloatware....probably why it wont update u know how to force the ota or do u know where i can get the apks to reinstall them to update it... ty dan
Click to expand...
Click to collapse
I managed to free up some time this weekend and I'm going to be pulling the OTA and seeing what I can do for re-packing it for those of us who are rooted and/or de-bloated.
Will post back with more info after I've had some time to poke at the OTA some.
Edit 1: Looks like this has patches for system and boot. /cache/delata looks like the directory where everything was downloaded. Hopefully binwalk and some other tools will yield useful information on what's contained within.
Edit 2: Looks like I was able to install the OTA despite being rooted. I'm waiting for 1st boot to verify root persisted and I'm also working on mirroring a number of partitions that can be used to "go back" to stock as well as images for updated partitions post-OTA.
Dkesler76 said:
np yeah i wished it was to lol... seems that my phone wont take the ota i did delete the bloatware....probably why it wont update u know how to force the ota or do u know where i can get the apks to reinstall them to update it... ty dan
Click to expand...
Click to collapse
I managed to get a stock boot and system partition uploaded today that you should be able to use to restore the de-bloated apps. The image is here
You can use a Linux machine (or other methods) to extract the APKs and put them back or use busybox + dd to restore the contents of the partition (you may need to re-root if writing the partition using dd). There are some good guys on XDA and elsewhere on how to restore a partition image on an Android device.
Edit: The posted file is for an ATT device
Good news everybody! The ATT OTA doesn't remove root and can be installed as-is provided you've not de-bloated the ROM or installed Xposed. If you've de-bloated (see below) you'll need to restore the missing bloatware and if you've installed Xposed, you'll need to uninstall it prior to applying the OTA.
In one of the early OP's there's a link to the "misc file mirror" that contains partition images for boot and system partitions. These are from an ATT device and can be used to restore back to a state that'll allow the OTA to apply.
Happy hacking and OTAing everyone.
kemonine96 said:
I managed to get a stock boot and system partition uploaded today that you should be able to use to restore the de-bloated apps. The image is here
You can use a Linux machine (or other methods) to extract the APKs and put them back or use busybox + dd to restore the contents of the partition (you may need to re-root if writing the partition using dd). There are some good guys on XDA and elsewhere on how to restore a partition image on an Android device.
Edit: The posted file is for an ATT device
Click to expand...
Click to collapse
weird i tried dd and busy box and no go not showing up on device
Dkesler76 said:
weird i tried dd and busy box and no go not showing up on device
Click to expand...
Click to collapse
What isn't showing up?
Dear Friends,
About to pull a trigger on an AT&T LG G4, can someone give me a short answer, ASAP?
Is it possible to have permanent Root and Xposed on the AT&T variant WITHOUT ridiculous bugs like a "green dot" in the camera of the phone? (what does the green dot even mean? It's on every picture? Is it a watermark? Just on the GUI?)
If possible, how? And should I buy the phone?
Appreciate any QUICK responses, about to buy now! Thanks so much in advance!
I just bought the G4 a couple of days ago. I was able to root, but there is no twrp or xposed as far as I know. I also don't have the green dot and everything is working fine!
Thanks for the quick response, my friend. Can you share the method/thread/image you used to Root?
I think you can install Xposed without TWRP via FireFlash? Can someone please confirm?
Thanks guys!
Just got my G4 two days ago. You can root and you can install Xposed with FireFlash. Root requires pushing a rooted version of whatever software version you are currently running. If you can't find one you can inject root into your own system.img using Ubuntu. After root get FireFlash and the right xposed zip and be patient, it can sit black screen, appearing dead for 20-30 minutes. Over all not too hard. Took me a couple hours from The un-boxing to Xposed. Definitely do it. The green dot on camera comes from the PR system.img. I'd stay clear of that. Everything is working great on mine!
@Nowak4G - Thanks bud, that's what I read too. Can you point me to the guide and img file you used that worked for you? I doubt I'd prefer the Ubuntu way...
One other question... Is there a way/app/Xposed module that's kind of like G3TweaksBox for us? Letting us change the Status bar icon colors and toggle colors?
I highly doubt themes work for us since we can't Flash them without custom recovery?
Thanks again!
GravityBox works for status bar stuff and yeah here are the threads I used. Good luck bud!
http://forum.xda-developers.com/showthread.php?p=62028519
http://forum.xda-developers.com/g4/general/lg-g4-100-root-success-directives-root-t3180586
http://forum.xda-developers.com/showthread.php?p=62664473
I'm not totally sure what stuff can and can't be flashed using FireFlash. But for applying icon themes with Xposed I use this module, Unicon:
https://drive.google.com/file/d/0B1nrydqmmOBUdFoyV0FBLUM1OVE/view?usp=docslist_api
I've had my LG G4 rooted and running Xposed with a lot of modules enabled.
If the phone you buy is on the 10G software version (and want to stay on that version), you should be able to root it following the method in the LG G4 Low Effort Root thread. Follow it to the dot and enjoy partial freedom.
If the phone you buy is on 10I, there is a rooted image floating around. So you could take the 10I update (or make sure your phone's on the 10I version), and root it using the Low Effort Root method.
I would also recommend the following:
1. keeping a copy of your untouched fresh system image in your internal memory (as early as possible after buying the phone). In case of a bad flash you have something to possibly go back to - otherwise you'll end up with the PR ROM and the green dot. The method and commands to extracting the system image is very similar to rooting, except instead of dd'ing into the system partition from SD, you do the opposite (from system partition to SD)
2. disabling system apps and system updates using the debloater tool and a tutorial here on the forums
Regarding flashing files via recovery, I usually extract the files and place them in the correct directory with the right permissions. Usually most files use 0644 permissions, but I would first check the existing permissions with ES File Explorer.
Hello @Nowak4G and @mu3g,
Guys thank you for your response. I can confirm that the seller I bought the phone from took the 10l upgrade. I have little to no experience rooting locked bootloader phones, and I have to be honest, I am more confused than I have the answers. Now that I have confirmed that I will end up with 10l update, can you guys give me a noob boost and give me step by step on how to root, Xposed, and possibly back up my stock image, since I do NOT want to end up with the PR build, with the green dot, in case things go wrong?
Am I correct that the right answer to my problem is, Low Effort Root with the floating 10l rooted img file, located here: https://drive.google.com/file/d/0B54ceS-n3ZAiaVAxMkJFLXNMYmM/view?pli=1
Please help me out guys, would even appreciate more if we can maybe connect on Google Hangouts for some dynamic help? Please let me know and thank you again for your wonderful so far !
Yes, exactly. Use the floating around 10I rootedsystem.img with the Low Effort Root instructions. But definitely keep a unrooted system.img on the internal storage as a backup. Instructions are in the LER thread. Just read carefully and follow the steps and you should be fine. All copy and pasting.
You have the correct 10I rooted system img file. I would recommend following the LER steps and backing up the system image for 10I (see post 2 of the LER thread). This would give you the stock image for later use. Then follow the LER steps to the dot using the rooted system image file you have from the google drive link. The LER thread has pretty clear instructions on backup and flashing system image files for the G4. Just make sure to rename your downloaded file as "system.rooted.h81010i.img" and use it in the command...the file name here is the most important!
Thank you guys, couple of follow up questions:
1. Do I run the backup command to copy my Non Rooted image, right after the step that gives us the DIAG Port Number? Or do I do it after the "id" step?
2. The generated back up, I assume will be done as an .img file in the root of my phone, correct? I assume I just back this up on my computer and/or External HD?
3. This is the scariest step. When I am running the step for flashing the rooted img, I need to rename the downloaded file to, "system.rooted.h81010i.img" as @mu3g recommended? Why not, "system.rooted.h81010m.img" for example?
4. I just use the exact file name we determined above for my downloaded rooted 10l image file, in the flash command when following the LER guide? Exactly that file name, correct?
Thank you again for all your help and excuse me for my continuous noobness!
Answers:
1. Run the backup command in Step 7 of the LER root ("Run the command specified in the section below titled 'Commands to Run' to flash the rooted system image.") <<---replace the commands to run with the command to backup your unrooted clean system image to your internal memory ---- if you compare the commands, it will become obvious on how the data is being moved (pushed or pulled from the phone).
2. The generated backup will be on the root of the internal memory of the phone. Yes, you can then move it to your computer or any other location for safekeeping AFTER you've booted your phone up properly - don't do any of this while you're still in the LER state.
3. I just gave you a recommendation on the name..you can name the rooted system image file whatever you want - you can even leave it as the way it is....just make sure to use the EXACT file name for the image in the commands to run (also 10I, 10M etc. are software version numbers..I'm not aware of a 10M version being released for AT&T. In any case, just use the EXACT file name for the rooted image.
Thank you @mu3g! I think I am now ready to go through the process myself with confidence.
I am, however, still a bit confused about the file name of the rooted image that I will be flashing. If the phone already has 10l installed, and I leave the name of the rooted image intact, that is, "system.rooted.h81010l" would the phone still accept/get tricked into, thinking that it's getting an "update"? Or did you mean that the file name could literally be anything like, "filename.img" and if the commands match it, all will be installed correctly? As in, when the system boots, it will have all the correct build and software information with it being a 10l update and etc?
Please forgive the annoying, detailed questions, but I want to not mess this up, since every guide triple emphasizes the importance of the command being absolutely right! Thank you!
You can literally name it blahblahblah.img as long as you use blahblahblah.img in the commands to run for the rooted system image. The file naming scheme has nothing to do with the acceptance or rejection of a system image. When you're in the bootloader mode ready to download files (which is the mode for LER), you can inject any file into any partition, anywhere on the phone...it's just whether the phone can use it or not properly and whether or not it ends up being a brick
Your file name for the system has nothing to do with the build number showing on the phone after booting up.
EDIT: The only reason I gave you that file naming scheme is because you don't seem to be too comfortable with the command line, thats all..that way you could copy paste the command from the LER guide and just replace "g" with "i" - that's all..if you're good with the command line and careful, you'll be fine..just make sure the file name is correct..you can't get much else wrong.
Understood brother, just needed that clarity. I am not an absolute noob with cmd line, but you know how it goes when you're rooting your phone, the perpetual fear of an expensive paperweight!
I cannot find the thanks button here, wish I could, so I could thank you over and over and @Nowak4G, but either way, thank you so so much @mu3g!!
good luck!
How did it go? Were you able to go through with it?
While the green dot does usually appear on 810 phones running the PR KDZ, I have heard reports of it on some 815 ...its pretty random. I just did a warranty exchange for my 810 so I will likely be staying on the ATT software.
Hi Guys, wanted to update this thread with my results...:
I successfully rooted on H810l (AT&T) with 0 issues, following the Low Effort Root. Per the recommendations of the process, I also backed up my Stock, Unrooted, .img file for restoration to Stock, if it were needed. Well, I might be moving on from this phone and need to return to stock. Can someone advise the exact steps/commands to return to stock using the unrooted .img file I backed up before pushing the rooted .img? And can you confirm that you did this successfully as well?
I would really appreciate it! Thank you!
I have not done it myself, but if you uninstall all your root apps completely, make sure to enable any and every disabled app you may have (like for example AT&T apps etc.) using the debloater software and then follow LER to install the stock image on it, it should come back to bone stock. Remember, the key here to to ensure that no root apps exist on the phone - I guess SU will get wiped out, but its better to do it clean. And secondly, any disabled apps need to be re-enabled for a smooth process. These are just my $0.02...so proceed with caution.
Hi, so some background, it has been a long time since I have touched custom ROMs or root access on an android device (back when the Nexus 2 released) so I don't really remember anything and know nothing about how the android environment has changed.
The reason for my post is that I was "hiding" sentimental/sensitive material in a folder associated with the Google Drive application using a file manager app (cut and paste into Drive folder) so that it wouldn't appear in Gallery scans, and when my drive app wasn't working as expected I (stupidly) uninstalled the update (can't actually uninstall the app on stock ROM) causing the folder to be wiped. Now I'm trying to find a way to recover the files but all the solutions recommended by a google search that I've tried require root and from what I know, correct me if I'm wrong, unlocking my bootloader to gain root access will wipe my internal storage which would probably defeat the whole purpose(?) of trying to recover information as it will overwrite the sectors. So does anyone know of anyway that I can recover this data from my device? I am willing to root as long as it will yield results.
tl;dr - need to recover files on stock P20 Pro (locked bootloader, no root), please help I am lost and a noob now
Thanks in advance!
P.S. This was (incorrectly) posted in the discussion forum before and I have requested it to be deleted
BUMP
bump!
Bump! Can anyone please help?
Bump? :fingers-crossed:
toushingo said:
Bump? :fingers-crossed:
Click to expand...
Click to collapse
Stop bumping. You are simply in the wrong section. None of us has a Pro model. This is the P20-Forum. Not Pro, not lite. I can not understand why people see 3 different devices as one. Ask here. Good luck!
Hello,
I hope that this is the right side of the forum to describe my problem. I desperately need help. It's a long story:
I had on my Samsung phone the app of "Chrome", which I always use to surf the internet. Using the google browser IN THAT APP, I have downloaded lots of things (I'm a scholar, so I like to read and I use to download everything that I found interesting). I have updated the app and I was frustrated, because I couldn't take anymore screenshots while surfing in "incognito mode". So, I decided to delete the update: i went into "settings", then "apps", and then I have brought back the app of "Chrome" as it was when i bought my phone. Sadly, I then noticed that I had lost every file in my download folder; I had lost every file downloaded with that app.
I had not synchronized my Google account, I can do no backup. I'm so angry and sad because I've always thought that the files downloaded would have stayed in my phone until I and only I would have decide to delete them.
I have done a lot of research on the internet and I have found out that there are some apps that can recover a very large part of lost files. But, in order to do this, I have to root my phone.
My phone is a Samsung Galaxy J2 SM-J250Y/DS, and the Android version is 7.1.1. I have seen that rooting a phone could be very dangerous; also, to me is very complicated. But there is a program called Kingoroot, which, once installed on my computer, could (it's a possibility, I know!) rooting my phone easily.
What should I do? Should I try the rooting method? It seems to me the only way...
I ask you any suggestions... Please help me. I am a depressed student that, in this life, can only enjoy reading and books...
(I am Italian, and I hope my English is understandable. If I did any mistake, please forgive me.)
Sorry can't help you get what you lost back... I feel your pain.
After losing thousands of bookmarks over the decades I started using Colornotes to save my important bookmarks.
You can save the hyperlink with a title, color, and whatever text you want to add. If you punch the hyperlink it opens in the default browser.
The app allows you to save it's data to your sd card which you can backup on your PC.
Use ApkExport to make a loadable copy of the app to future proof it.
ColorNote Notepad Notes - Apps on Google Play
ColorNote® - Easy to use notepad for notes, shopping list, to-do list, calendar
play.google.com
Thank you very much for your reply.
But... If I root my phone, and if the rooting is done without any damage, is there a possibility to get most of my files back? Or, even if I root my device, I will never be able to recover them?
It sounds like it deleted the data when you rolled the apk back (to factory load?).
If so it's going to be very sketchy at best to recover them.
I guess history's been deleted as well?
There are many coders here that have far greater knowledge than myself with Chrome.
My understanding of rooting is very basic as with Chrome which I rarely use.
If no one else replies in a day or two, bump it back to the top. Hope you find a work around solution.
AlexiusFrigerius said:
But... If I root my phone, and if the rooting is done without any damage, is there a possibility to get most of my files back? Or, even if I root my device, I will never be able to recover them?
Click to expand...
Click to collapse
Rooting Android by means of TWRP and/or Magisk ( keyword: SuperSU ) affects its /data partition where phone's data typically are housed. Therefore it cannot be excluded that data stored there is overwritten and can therefore no longer be restored.
jwoegerbauer said:
Rooting Android by means of TWRP and/or Magisk ( keyword: SuperSU ) affects its /data partition where phone's data typically are housed. Therefore it cannot be excluded that data stored there is overwritten and can therefore no longer be restored.
Click to expand...
Click to collapse
Is there the possibility if deleted that it's still on the system cache and is there a way to recover it if so on a none rooted phone?
Maybe using ABD?
Don't some on the "one touch" root solutions claim to preserve the data?
Android doesn't have a recycle bin thus nothing gets cached. Deleting a file means nothing else than marking the space it occupies - whereever this disk space is located - as usable so that it can be overwritten by the system.
Have never used a "One-Click-Root" utility ...
blackhawk said:
It sounds like it deleted the data when you rolled the apk back (to factory load?).
If so it's going to be very sketchy at best to recover them.
I guess history's been deleted as well?
There are many coders here that have far greater knowledge than myself with Chrome.
My understanding of rooting is very basic as with Chrome which I rarely use.
If no one else replies in a day or two, bump it back to the top. Hope you find a work around solution.
Click to expand...
Click to collapse
Yes, it's just like I told. And yes, even history has been deleted.
Thank you for your help! I will wait until someone may give me a solution, or a possibility for a solution.
jwoegerbauer said:
Rooting Android by means of TWRP and/or Magisk ( keyword: SuperSU ) affects its /data partition where phone's data typically are housed. Therefore it cannot be excluded that data stored there is overwritten and can therefore no longer be restored.
Click to expand...
Click to collapse
Ok, I understand...
jwoegerbauer said:
Android doesn't have a recycle bin thus nothing gets cached. Deleting a file means nothing else than marking the space it occupies - whereever this disk space is located - as usable so that it can be overwritten by the system.
Have never used a "One-Click-Root" utility ...
Click to expand...
Click to collapse
Thank you for your explanation.
jwoegerbauer said:
Android doesn't have a recycle bin thus nothing gets cached. Deleting a file means nothing else than marking the space it occupies - whereever this disk space is located - as usable so that it can be overwritten by the system.
Have never used a "One-Click-Root" utility ...
Click to expand...
Click to collapse
Yeah I was aware of the overwrite issue but on an unrooted device I don't think you can access the system cache. Even if you could the data could be so juxtaposed from lose of file structure as to be unusable.
One-Click-Root worked on older versions of Kitkat allegedly.
So... I understand. But I want to try. I want to root my phone. But I have to know how and I must prevent my phone from all the risks.
blackhawk: you said that the "One-Click-Root" method worked only for Kitkat Android. But I have read here that with Kingoroot i could have a chance:
How to Root Android Nougat (7.0/7.1) | KingoRoot Apk
Root any Android Nougat 7.0 7.1 device with KingoRoot.
www.kingoapp.com
(It's important: I AM NOT SPAMMING Kingoroot, I just want to understand If I can trust what it's written in their site. Also, in the link, at the end of the page, there is written that I can root my phone with my PC, which, to me, seems a safer way. It's the main idea I had when I decided to write in this forum, because I wanted to know the opinions of people that are very able to use these methods and these kind of programs.)
AlexiusFrigerius said:
So... I understand. But I want to try. I want to root my phone. But I have to know how and I must prevent my phone from all the risks.
blackhawk: you said that the "One-Click-Root" method worked only for Kitkat Android. But I have read here that with Kingoroot i could have a chance:
How to Root Android Nougat (7.0/7.1) | KingoRoot Apk
Root any Android Nougat 7.0 7.1 device with KingoRoot.
www.kingoapp.com
(It's important: I AM NOT SPAMMING Kingoroot, I just want to understand If I can trust what it's written in their site. Also, in the link, at the end of the page, there is written that I can root my phone with my PC, which, to me, seems a safer way. It's the main idea I had when I decided to write in this forum, because I wanted to know the opinions of people that are very able to use these methods and these kind of programs.)
Click to expand...
Click to collapse
You can try it; it will either work or nothing will happen. Even if it works it's likely those files are gone. Maybe better to chalk it up to another lesson from the University of Hard Knocks.
You could try contacting Google tech support to see if they have any ideas.
The last AT&T firmware update was specifically to block easy rooting by Kingroot; the rats learn quick.
blackhawk said:
You can try it; it will either work or nothing will happen. Even if it works it's likely those files are gone. Maybe better to chalk it up to another lesson from the University of Hard Knocks.
You could try contacting Google tech support to see if they have any ideas.
The last AT&T firmware update was specifically to block easy rooting by Kingroot; the rats learn quick.
Click to expand...
Click to collapse
Thank you very much for your help. I understand: I must give up. But the most important thing is to learn something about anything we do. Anything could help for future situations.
"It's a shame to stumble twice on the same stone" (Polybius, 31,11, 5).
Thank you again. Goodbye!
AlexiusFrigerius said:
Hello,
I hope that this is the right side of the forum to describe my problem. I desperately need help. It's a long story:
I had on my Samsung phone the app of "Chrome", which I always use to surf the internet. Using the google browser IN THAT APP, I have downloaded lots of things (I'm a scholar, so I like to read and I use to download everything that I found interesting). I have updated the app and I was frustrated, because I couldn't take anymore screenshots while surfing in "incognito mode". So, I decided to delete the update: i went into "settings", then "apps", and then I have brought back the app of "Chrome" as it was when i bought my phone. Sadly, I then noticed that I had lost every file in my download folder; I had lost every file downloaded with that app.
I had not synchronized my Google account, I can do no backup. I'm so angry and sad because I've always thought that the files downloaded would have stayed in my phone until I and only I would have decide to delete them.
I have done a lot of research on the internet and I have found out that there are some apps that can recover a very large part of lost files. But, in order to do this, I have to root my phone.
My phone is a Samsung Galaxy J2 SM-J250Y/DS, and the Android version is 7.1.1. I have seen that rooting a phone could be very dangerous; also, to me is very complicated. But there is a program called Kingoroot, which, once installed on my computer, could (it's a possibility, I know!) rooting my phone easily.
What should I do? Should I try the rooting method? It seems to me the only way...
I ask you any suggestions... Please help me. I am a depressed student that, in this life, can only enjoy reading and books...
(I am Italian, and I hope my English is understandable. If I did any mistake, please forgive me.)
Click to expand...
Click to collapse
Hi, I would suggest you can try free tool for Android Phone such as Stellar Data Recovery for Android which easily recover deleted files like, photos, audio files, videos files from your Android phone internal memory storage.
Source: https://www.stellarinfo.com/media-tools/android-data-recovery.php
{Mod edit: Quoted post has been deleted}
That drfone again. Scamware.
Do Not Use.
Drfone if used will encrypt "recovered" data and ask you to pay for it. After which the original data is gone leaving only the encrypted copy.
It is not free... not to be trusted!
Ran into this scam many years ago.