[Q] Can't get root accesss? - HTC Droid DNA

Did everything correctly from start to finish, flashed the SuperSU and Busybox package, but still no root access.
Couldn't install binary on SuperSU so I tried superuser... begins to download the update but fails at request for root access.
Please HELP! TWRP installed fine, i've installed the 4.2 camera keyboard and clock through twrp and they all work fine...
Titaniumbackup says it has root, but I guess that isn't right.. lol
fastboot says *TAMPERED* and *UNLOCKED*.
I also apologize if this isn't the right place for this, I can't post in the development thread due to the fact that i have <10 posts

You sound rooted, if not you wouldn't have been able to install the 4.2 camera. download superuser and try that. if all is good. then try superSU.
Also reboot your phone and try to install superSU again. but you are rooted.

cmay227 said:
You sound rooted, if not you wouldn't have been able to install the 4.2 camera. download superuser and try that. if all is good. then try superSU.
Also reboot your phone and try to install superSU again. but you are rooted.
Click to expand...
Click to collapse
Sorry I meant to include that superuser failed to gain root access in the process of updating. SuperSU won't even update, just goes to installation failed.

theguitarhero94 said:
Sorry I meant to include that superuser failed to gain root access in the process of updating. SuperSU won't even update, just goes to installation failed.
Click to expand...
Click to collapse
are you trying to flash the binaries from the SU app? if so you can't do that with S-on you need to Download the Zip from the SU website and flash in recovery... watch one of the videos on root/ custom recovery they explain it in detail

DNA help
i installed what seems to be the first custom rom for the DNA
i unlocked the bootloader w/ htc dev and gained root w/ CWM
im having trouble posting to this thread as im a new user
http://forum.xda-developers.com/show...2014200&page=5
my device is hanging during boot animations at droid eye
how do i push the zip back to to SD card via command prompt if neccesay(if i wipe data)
also, im reluctant to perform factory reset from HTC bootloader menu w/ unlocked bootloader
BTW i did make a backup before rooting and before installing rom, but restore from it using CWM gives MD5 mismatch error
any advice?

bbeatz88 said:
i installed what seems to be the first custom rom for the DNA
i unlocked the bootloader w/ htc dev and gained root w/ CWM
im having trouble posting to this thread as im a new user
http://forum.xda-developers.com/show...2014200&page=5
my device is hanging during boot animations at droid eye
how do i push the zip back to to SD card via command prompt if neccesay(if i wipe data)
also, im reluctant to perform factory reset from HTC bootloader menu w/ unlocked bootloader
BTW i did make a backup before rooting and before installing rom, but restore from it using CWM gives MD5 mismatch error
any advice?
Click to expand...
Click to collapse
From what I understand if you are flashing the available custom ROM you must wipe system AND format data for it to install successfully. If you are able to get back into recovery just wipe those two and reflash the zip I believe you will be good to go after that.

two_cents said:
are you trying to flash the binaries from the SU app? if so you can't do that with S-on you need to Download the Zip from the SU website and flash in recovery... watch one of the videos on root/ custom recovery they explain it in detail
Click to expand...
Click to collapse
Finally got it to work. Fix was around xda. Had to install superuser and I then disable superuser in SuperSU and now the superuser updates correctly. Super su still asks me to update and fails but I guess I'll just use superuser... Weird also it reboots when the update fails sometimes

My problem is that I rooted the phone OK but randomly apps will say that they cannot get root. Like titanium backup will randomly do that, a reboot will usually fix it. Thoughts?

ilogik said:
My problem is that I rooted the phone OK but randomly apps will say that they cannot get root. Like titanium backup will randomly do that, a reboot will usually fix it. Thoughts?
Click to expand...
Click to collapse
I found that manually launching Superuser, then launching TiBu worked when TiBu wouldn't get root.

bbeatz88 said:
i installed what seems to be the first custom rom for the DNA
i unlocked the bootloader w/ htc dev and gained root w/ CWM
im having trouble posting to this thread as im a new user
http://forum.xda-developers.com/show...2014200&page=5
my device is hanging during boot animations at droid eye
how do i push the zip back to to SD card via command prompt if neccesay(if i wipe data)
also, im reluctant to perform factory reset from HTC bootloader menu w/ unlocked bootloader
BTW i did make a backup before rooting and before installing rom, but restore from it using CWM gives MD5 mismatch error
any advice?
Click to expand...
Click to collapse
md5 mismatch is because the backup is unrooted...

theguitarhero94 said:
md5 mismatch is because the backup is unrooted...
Click to expand...
Click to collapse
no... md5 mismatch is because the backup probably failed and the device rebooted before it completed. this is a known issue with both twrp and cwm recoveries on HTC DNA

Deuces said:
no... md5 mismatch is because the backup probably failed and the device rebooted before it completed. this is a known issue with both twrp and cwm recoveries on HTC DNA
Click to expand...
Click to collapse
gotcha, he didn't say anything about it not finishing, and I had the same issue a while back on my incredible and the backups definitely were completed... so i'm not really sure

OP, go see my post in this sub-forum about not being able to update the su binary. It should solve your issues.
Sent from my rooted and debloated Droid DNA.

I'm having the same issue, but disabling root in SuperSU doesn't work, and when I update the SU binary in SuperSU or Superuser my phone reboots.

Related

Cannot root. Followed this....

First I got back to stock by RUU-ing through adb. Back to 4.0.3, PH98IMG_ICS_4.03.605.2 after locking the bootloader.
Unlocked the bootloader back.
Then I installed AmonRa recovery.
Booted, completed the setup and went back to recovery and selected the from from Dev's menu, "Install superuser and su".
The Superuser app is installed.
Checked with the root checker, and its saying unrooted.
What am I doing wrong?
lamborg said:
First I got back to stock by RUU-ing through adb. Back to 4.0.3, PH98IMG_ICS_4.03.605.2 after locking the bootloader.
Unlocked the bootloader back.
Then I installed AmonRa recovery.
Booted, completed the setup and went back to recovery and selected the from from Dev's menu, "Install superuser and su".
The Superuser app is installed.
Checked with the root checker, and its saying unrooted.
What am I doing wrong?
Click to expand...
Click to collapse
Which version of amon ra ? I am not certain , but I pretty sure version 3.15 the install Su didn't work. Thought he fixed it in 3.16 . Otherwise, just install a custom Rom .
Sent from my HTC Rezound using Tapatalk 2
Flash this over the top
http://download.chainfire.eu/331/SuperSU/UPDATE-SuperSU-v1.32.zip
Then install Busybox
https://play.google.com/store/apps/details?id=stericson.busybox&hl=en
Or can do the above and just choose a custom rom, with a normal data & system wipe prior to flashing.

[Q] Does not have proper root

Hey guys,
I have an i9300, rooted with slimbeam installed. A few days ago I dropped my phone and the screen cracked and the display disappeared; so I got it replaced. When I turned my phone on again, it was stuck on the boot screen. So I fully wiped my phone and flashed slimbean again (as I already had the file on my external SD card). This got me passed the boot screen and my phone is working fine except it seems like I don't have proper root access. I downloaded a root checker and thats the message I got "Does not have proper root access" and when I run superSU it said "the su binary needs to be updated" so I click on update and I get a message saying " install failed. Reboot and try again" I reboot and tried again and same error
Anyone know what my best course of action would be?
EDIT: It also randomly keep rebooting.
Thanks a lot guys!
Cheers
bd101 said:
Hey guys,
I have an i9300, rooted with slimbeam installed. A few days ago I dropped my phone and the screen cracked and the display disappeared; so I got it replaced. When I turned my phone on again, it was stuck on the boot screen. So I fully wiped my phone and flashed slimbean again (as I already had the file on my external SD card). This got me passed the boot screen and my phone is working fine except it seems like I don't have proper root access. I downloaded a root checker and thats the message I got "Does not have proper root access" and when I run superSU it said "the su binary needs to be updated" so I click on update and I get a message saying " install failed. Reboot and try again" I reboot and tried again and same error
Anyone know what my best course of action would be?
EDIT: It also randomly keep rebooting.
Thanks a lot guys!
Cheers
Click to expand...
Click to collapse
If you have Phil's touch recovery then go in the settings and reroot your device and install supersu app from play store and update your binaries...
Sent from my GT-I9300
kunal1540 said:
If you have Phil's touch recovery then go in the settings and reroot your device and install supersu app from play store and update your binaries...
Sent from my GT-I9300
Click to expand...
Click to collapse
Would that be in recovery mode? Cause I couldn't find anything regarding root there. or should I follow this http://forum.xda-developers.com/galaxy-s3/orig-development/i93xx-philz-touch-t2002953
Thanks! I realy appreciate your help
bd101 said:
Would that be in recovery mode? Cause I couldn't find anything regarding root there. or should I follow this http://forum.xda-developers.com/galaxy-s3/orig-development/i93xx-philz-touch-t2002953
Thanks! I realy appreciate your help
Click to expand...
Click to collapse
yes in philz recoverey in philz settings i think...re root option and install supersu from play store..or
alternative is to flash supersu zip file from the respective thread..
Flash the latest supersu's .zip from a custom recovery.... Here's the thread
http://forum.xda-developers.com/showthread.php?t=1538053
kunal1540 said:
yes in philz recoverey in philz settings i think...re root option and install supersu from play store..or
alternative is to flash supersu zip file from the respective thread..
Click to expand...
Click to collapse
i did flash superuser from the respective thread. When I run the root checker app I still get the "Sorry! This device does not have proper root access". When I run SuperSU it says "There is no SU binary installed and SuperS cannot install it. This is a problem! "
What do I do now? I was hoping flashing SuperSU would solve the problem.. but i guess that didnt work

[Q]How to downgrade superSU versions

I have an HTC One M8 with ROM 4.16.1540.8 (5.0.1)
I'm trying to remove my SuperSU app so that i can downgrade it to a lower version(2.20) due to incompatibility with some of my apps (puzzle and dragons).
Bootloader is unlocked and it is s-on.
I have tried removing SuperSU through the app itself by using the reinstall, switch superuser app, and full unroot functions, but everytime I restarted the phone superSU would be back and in version 2.46. I also tried manually deleting the apk and su files in the bin and xbin folders in system using es file explorer but a restart just brought those back too.
Any help would be greatly appreciated. Thanks!
Find the flashable zip for the "older" version and flash in recovery. I would think that should do it.
Hi thanks for the reply.
I flashed superSU 2.23 from recovery, but i got stuck in bootloop. What should i do to fix it? Thanks!
Edit: flashed the updated su back in and got out of it. How do i do the downgrade without a bootloop?
ah46657 said:
Hi thanks for the reply.
I flashed superSU 2.23 from recovery, but i got stuck in bootloop. What should i do to fix it? Thanks!
Edit: flashed the updated su back in and got out of it. How do i do the downgrade without a bootloop?
Click to expand...
Click to collapse
Hmm, wouldn't expect that to happen. Obviously, since I would never intentionally bootloop someone!
Flash the stock ROM or restore stock nandroid. Then flash the desire SuperSU zip. That's the best I can think of.
Make a nandroid backup of your current setup (if you haven't already) to revert to "just in case".
how to unflash supersu zip
redpoint73 said:
Hmm, wouldn't expect that to happen. Obviously, since I would never intentionally bootloop someone!
Flash the stock ROM or restore stock nandroid. Then flash the desire SuperSU zip. That's the best I can think of.
Make a nandroid backup of your current setup (if you haven't already) to revert to "just in case".
Click to expand...
Click to collapse
recently i installed lineage os 14.1 in my device (rooted) and flashed supersu2.79 , but after updating it it 2.82, its showing SU BINARY OCCUPIED , so can i try downgrade supersu by flshing lower version,, if so how should i unflash previous supersu zip help
rajkumar1221 said:
recently i installed lineage os 14.1 in my device (rooted) and flashed supersu2.79 , but after updating it it 2.82, its showing SU BINARY OCCUPIED , so can i try downgrade supersu by flshing lower version,, if so how should i unflash previous supersu zip help
Click to expand...
Click to collapse
So you tried to flash 2.82? I don't think that is the proper way to update. Since you already have SuperSU installed, you should just be able to go into the SuperSU app, and update the binary from there. Or is that what led to the "binary occupied" error?
But back to the basic question, you can't "unflash" SuperSU. You can "dirty flash" Lineage (just wipe cache and dalvik, can keep user data), and that will put you back on the "unrooted" Lineage ROM. Then you should be able to flash SuperSU 2.82 via zip.
redpoint73 said:
So you tried to flash 2.82? I don't think that is the proper way to update. Since you already have SuperSU installed, you should just be able to go into the SuperSU app, and update the binary from there. Or is that what led to the "binary occupied" error?
But back to the basic question, you can't "unflash" SuperSU. You can "dirty flash" Lineage (just wipe cache and dalvik, can keep user data), and that will put you back on the "unrooted" Lineage ROM. Then you should be able to flash SuperSU 2.82 via zip.
Click to expand...
Click to collapse
i unrooted my device now,, should i have to "first root" it with official lineage os extra file addonsu arm and then should i have to flash supersu zip ?
rajkumar1221 said:
i unrooted my device now,, should i have to "first root" it with official lineage os extra file addonsu arm and then should i have to flash supersu zip ?
Click to expand...
Click to collapse
I don't personally use Lineage. I believe you will need to flash both of those, yes.
@redpoint73 , found this script made by osm0sis to "unSU". not sure if is relevant to earlier posts but thought maybe if you havent seen it yet would be worth looking at. maybe could help someone.?
http://forum.xda-developers.com/showthread.php?p=63615067

Can't fix root. Do I need to flash recovery again?

So I just successfully installed CM13 on my i9300. Everything works fine, but I just found out I lost root rights.
I went and downloaded the Super SU app from the PlayStore, launched it and that gave an error that there's no SU binary installed and I need to manually root again.
So I downloaded UPDATE-SuperSU-v2.65-20151226141550.zip, put it on the sdcard, rebooted into CWM Recovery, installed the zip and booted back into the system (when prompted to fix boot I selected no as recommended), but now I STILL HAVE NO ROOT RIGHTS and the Super SU app still gives the same error.
Is there a specific SuperSU.zip I should be installing in recovery to make it work?
Or is something wrong with the recovery and do I need to flash that through Odin? (I don't think this is the case though, as flashing CM13 and gapps went completely fine)
Thanks for any isnight and tips
There is already Root option in developer settings.Can you try it?
ArdaCsknn said:
There is already Root option in developer settings.Can you try it?
Click to expand...
Click to collapse
In Developer Options I have set Root Access to Apps and ADB it didn't give any error, but doesn't seem to be doing anything either... In file manager I can't reach root, Root Checker app fails, Super SU gives than binary error, and another app that requires Root Access says I don't have it as well..
warriotox said:
In Developer Options I have set Root Access to Apps and ADB it didn't give any error, but doesn't seem to be doing anything either... In file manager I can't reach root, Root Checker app fails, Super SU gives than binary error, and another app that requires Root Access says I don't have it as well..
Click to expand...
Click to collapse
Flash rom again and dont flash SuperSu its better now without using SuperSU
I got the same problem. I tried to root with odin again but it didnt work...
Flash cm13, wipe data and cache and flash cm13 again. Cm13 should be pre rooted.
Sent from my HTC One M9 using Tapatalk
Hi Guys, I have the same problem too after CM13. Unfortunately rooting again with ODIN flashed stock recovery back and am stuck on CM13 now with no root and stock recovery. Can someone help please? Below is the detailed description of what happened.
----------------------------
1. My Samsung Galaxy SIII International (I9300) was rooted and I had CM11 stable/snapshot version there since last 2-3 weeks.
2. Yesterday, I tried upgrading the latest CM13 nightly for my device.
3. While doing so, and rebooting, it asked me the normal message "root possibly lost, fix, yes or no". I accidentally pressed no.
4. Then I noticed after CM13 was flashed, that I do not have root access anymore. Please note that at this point in time, I was not aware that it has to be explicitly enabled in developer options.
5. I came to know that I lost root when I tried to boot in to recovery (CWM) to install gapps.
6. Now, under the impression that I do not have root anymore, I tried to root again with Odin as I had been doing all these days.
- By doing that, ODIN removed my custom recovery (CWM) and flashed it with stock recovery.
- Though ODIN said PASS after reboot, I still do not have root access.
7. Removed cache, wipe data, and factory reset, multiple times but no help.
8. Enabled root for both apps and adb in Developer options, but no use.
9. I also tried KINGO root ( a very popular tool for SGS3 these days) but in vain.
10. Now, am stuck with CM13 and stock recovery and unable to do anything with ROM manager or anything else as I do not have root anymore.
11. Am able to install few apks for whatsapp and facebook for now and living with it, but it wouldn't let me install playstore apk too anymore.
Highly appreciate any quick feedback.
same here after rooting once cm13 by developer option, for some reason i had to use hide my root app, now unable to get root back
Its a problem with the s3, it forgets root. The most reliable is chainfire and sticking with a stock rom.
You must:
Wipe to factory,
flash an original rom via odin,
Boot straight to recovery and wipe to factory again,
Flash original rom again,
Boot straight to recovery and wipe to factory,
Allow the phone to boot.
You must flash at least twice and reset to factory at least twice, even tho I sad it thrice, to kill all remnants of the old rooted rom.
Then you can flash chainfire via odin and go from there.
Beamed in by telepathy.

Samsung Galaxy S6 Edge (with samsung ecryption) stuck in TWRP please help

Please can someone help me sort out my S6 edge. I was trying to root my phone to change my encryption pin to a 20 digit passcode. I used odin to put twrp-3.1.1-0-zerolte.img onto my phone and now it is stuck on TWRP and won't boot normally. Could someone please tell me how I can remove TWRP or even just make my phone boot as usual. I never made a backup or copies of my photos and I really don't want to lose my data. THANKYOU! for anyone who can help me out I really appreciate it.
####WILL PAY ANYONE WHO CAN GUIDE ME THROUGH FIXING####
additional info:
UK(europe) Samsung Galaxy S6 Edge
SM-G925F
zerolte
Android 7.0
Kernel version 3.10.61-10531122
The way I was trying to root the phone was for (I believe) unencrypted devices, therefore I never actually rooted the phone just put TWRP onto it and it didn't work the way it was supposed to so I stopped.
I've never rooted a phone before and therefore don't want to rush into fixing it incase I cause irreparable damage.
I read on these forums that to do what I was doing I would need to use adb sideload because it's encrypted. I have got android sdk, adb but haven't done anything yet. I'm hoping for someone who definitely knows how to fix it before I go ahead and make a mess of it :\
I had Samsung Knox installed on my phone, I've just found out that that has probably caused the problem? Is it at all possible I can fix this and not lose my data?
TWRP says: Could not mount /data and unable to find crypto footer
I have tried wiping the cache and nothing changes.
Just flash original firmware
gurinder073 said:
Just flash original firmware
Click to expand...
Click to collapse
will I keep all the data and it work as usual? do you mind telling me exactly how i do that? do i enter download mode again and use odin same as before? and Thankyou
Did u tried reboot then system in twrp?
shahram Ali said:
Did u tried reboot then system in twrp?
Click to expand...
Click to collapse
yeah I just get the initial samsung logo over and over and it doesn't boot
I found this firmware download but it's 2GB? I'll pay anyone who can give me a foolproof fix :\
https://www.sammobile.com/firmwares/galaxy-s6-edge/SM-G925F/VOD/download/G925FXXU5EQDG/131324/
bump
OK, calm down. You haven't lost anything or likely to if you just slow down a bit.
OK first things first, what caused the actual boot loop?
Describe the exact steps. It wouldn't have been TWRP itself. Ignore any errors you are seeing regarding /data they are irrelevant at the moment.
Did you install SuperSU and which version? Did TWRP ask to install its own SuperSU version?
ashyx said:
OK, calm down. You haven't lost anything or likely to if you just slow down a bit.
OK first things first, what caused the actual boot loop?
Describe the exact steps. It wouldn't have been TWRP itself. Ignore any errors you are seeing regarding /data they are irrelevant at the moment.
Did you install SuperSU and which version? Did TWRP ask to install its own SuperSU version?
Click to expand...
Click to collapse
I did everything in this video up until 2:55.
https://www.youtube.com/watch?v=M8ji0yjf7IY
where his phone rebooted into the system mine just stayed on TWRP. I tried rebooting into system and I just get the samsung logo over and over. all I have done from that point is try wiping the cache.
I just used odin to put TWRP onto it and then stopped when it didn't do what it was supposed to.
And no TWRP didn't install SuperSU as I was planning to install Nougat_Root_SuperSU_No_kernel_included myself.
s6edge stuck twrp said:
I did everything in this video up until 2:55. where his phone rebooted into the system mine just stayed on TWRP. I tried rebooting into system and I just get the samsung logo over and over. all I have done from that point is try wiping the cache.
I just used odin to put TWRP onto it and then stopped when it didn't do what it was supposed to.
And no TWRP didn't install SuperSU as I was planning to install Nougat_Root_SuperSU_No_kernel_included myself.
Click to expand...
Click to collapse
Then your issue is you haven't installed Supersu. Once you've installed SuperSu V2.79 SR3 then your device should boot.
Your issue is likely dmverity. SuperSU will fix that by patching the boot.img.
ashyx said:
Then your issue is you haven't installed Supersu. Once you've installed SuperSu V2.79 SR3 then your device should boot.
Your issue is likely dmverity. SuperSU will fix that by patching the boot.img.
Click to expand...
Click to collapse
Thankyou very much, I will have to do that with adb sideload right? is there a straightforward way I can do this without the risk of messing it up?
:\
ashyx said:
Then your issue is you haven't installed Supersu. Once you've installed SuperSu V2.79 SR3 then your device should boot.
Your issue is likely dmverity. SuperSU will fix that by patching the boot.img.
Click to expand...
Click to collapse
I have sideloaded Nougat_Root_SuperSU_No_kernel_included.zip and it booted up asked me for my encryption key and when I entered it I get a message saying:
Verification failed
Unable to restart your device. The integrity verification has failed. You need to reset your device to factory default settings. This will erase all your data.
I am currently trying to sideload SuperSu V2.79 SR3 but it gets stuck on "- Creating image"
I guess I'm screwed at this point?
I also saw somewhere that it says Knox has been tripped, dno if that matters....
Thanks
my mistake.
Ignore this post
s6edge stuck twrp said:
I have sideloaded Nougat_Root_SuperSU_No_kernel_included.zip and it booted up asked me for my encryption key and when I entered it I get a message saying:
Verification failed
Unable to restart your device. The integrity verification has failed. You need to reset your device to factory default settings. This will erase all your data.
I am currently trying to sideload SuperSu V2.79 SR3 but it gets stuck on "- Creating image"
I guess I'm screwed at this point?
I also saw somewhere that it says Knox has been tripped, dno if that matters....
Thanks
Click to expand...
Click to collapse
All you really need to do is flash the stock recovery and boot image as your system partition should be unmodified.
You can flash the whole firmware and it won't affect your data.
If it's a 4 file firmware you should only need to flash the BL and AP parts with ODIN.
ashyx said:
All you really need to do is flash the stock recovery and boot image as your system partition should be unmodified.
You can flash the whole firmware and it won't affect your data.
If it's a 4 file firmware you should only need to flash the BL and AP parts with ODIN.
Click to expand...
Click to collapse
Thanks a lot man, will see what I can do.
s6edge stuck twrp said:
Thanks a lot man, will see what I can do.
Click to expand...
Click to collapse
This is the UK nougat update.
http://updato.com/firmware-archive-select-model?record=266726363D3611E7963AFA163EE8F90B
Instructions are here: http://updato.com/how-to/how-to-install-an-official-samsung-stock-firmware-using-odin
tried reflashing multiple times. would only accept the unlocked firmware, and still said I had to restore I ended up clicking reset device thinking it would restart but it deleted the data..... Make backups guys.... & a big thanks to ash for all the help just a shame I couldn't save my data
s6edge stuck twrp said:
tried reflashing multiple times. would only accept the unlocked firmware, and still said I had to restore I ended up clicking reset device thinking it would restart but it deleted the data..... Make backups guys.... & a big thanks to ash for all the help just a shame I couldn't save my data
Click to expand...
Click to collapse
One good reason to never run encryption on the device.
If you want to attempt data recovery, download the app disk digger pro. It has a high success rate of recovery. Just ensure you save the recovered files to SD card.
Just to note though this app needs root to work properly. You can use magisk to gain root rather than supersu.
s6edge stuck twrp said:
tried reflashing multiple times. would only accept the unlocked firmware, and still said I had to restore I ended up clicking reset device thinking it would restart but it deleted the data..... Make backups guys.... & a big thanks to ash for all the help just a shame I couldn't save my data
Click to expand...
Click to collapse
Just incase... did you use Google photos? If you do and sync was on you will have your photos saved to cloud.
callumbr1 said:
Just incase... did you use Google photos? If you do and sync was on you will have your photos saved to cloud.
Click to expand...
Click to collapse
I believe it was the google photo gallery but it hasn't synced anything
wouldn't have been so bad if I could have at least saved the photo's. and I doubt any recovery program will get anything because of it been encrypted but I can give it a go for nothing

Categories

Resources