Hey guys,
i hope you can help.
I wanted to root my phone because i needed a chat from whatsapp and needed the key for decryption.
Unfortunatley my Phone Number was no longer active to reactivate whatsapp.
Now i used Chainfires Autoroot for the S7 and now after the start it says "Verification Failed, you have to reset your phone to factory settings"
I dont wanna lose all the Data, is there any way to prevent this?
Or to just go back before the rooting?
pls help, thank you!
Related
Hello,
i have a G920F (Vodafone Germany branded).
After i recieved the last 6.0.1 update a week ago i reseted my phone for a better performance.
So i backed up everything and did a hard reset from the recovery.
After restoring everything back Whatsapp had problems to recover any of the last 7 backups "tried Google drive and local".
While searching i found that i might be able to fix this by decrypting and then re-encrypting the database on pc.
For that i need to access these two files but i don't want to root my device:
"/data/data/com.whatsapp/databases/msgstore.db"
"/data/data/com.whatsapp/files/key"
I tried many ways (adb, xplore) and i always get "access denied"
Does anybody have another method to do it? or maybe knows another way to solve my Whatsapp problem?
Or could it be something in the software that prevents WA from restoring? WA support didn't respond eventhough i sent them an email a week ago.
Thanks in advance guys
Hey guys firstly i want to apologize if i'm on the wrong forum.
I have screwed up and i hope you guys could help.
I have a Samsung S6 that worked perfectly, but i wanted to sell it and buy an S7 and so i have done a "hard" factory reset by pushing Vol up, Home, Power buttons. Turns out i had to do a "soft" factory reset first.
Now when i tried to sell my phone with all parts and documents i have failed!
It turns out that the phone asks for my Samsung ID but obviously i can't remember an ID that i have created more than a year ago that was of no use to me!
I think i still have warranty but that is my last option for something like this, i have not rooted this device it runs on marshmallow.
What can i do to fix it myself?
I haven't tried flashing it with a stock rom simply because i fear that that will trigger KNOX, even though i'm desperate to fix this, i haven't crossed that border of despair.
Guys please help, i'm counting on your replies.
Thank you.
Flashing a stock rom that was made for your phone will NOT trigger knox. You can use samfirm and odin to do it
ankushkatari said:
Flashing a stock rom that was made for your phone will NOT trigger knox. You can use samfirm and odin to do it
Click to expand...
Click to collapse
Thanks for your reply, do you mean from sammobile? Also i do not remember what version if marshmallow i was running, is there a way for me to figure it out now?
Okay i figured out what version of marshmallow i was running simply because i had put updates on automatic so it must be the last 6.0.1
However i do not know anything about samfirm i have used odin before on my s4 like 3 years ago, and i only used it to root my s4.
Could anyone please help me out?
Btw, if i successfully put a stock firmware on it throigh samfirm and odin, will it remove my email? Or is it omly worth a try?
Are you certain that it will not trigger knox?
Okay i tried flashing the same firmware unto my devicd but it seems that i can't flash anything because Reactivation Lock is enabled.
I didn't enable it (at least i don't remember) mayve the marshmallow update enabled Reactivation Lock?
I'm almost at the point of throwing my phone into a wall, it's getting close.
Did you figure it out. I'm in the same boat with my S6 edge
Hello everyone.
I need some help recovering data from a Samsung J7 (2016) with a screen pin. If it's possible, if I can remove only that pin without touching the apps in the phone will be great. I was thinking to format and then pass a recovery app after rooting but I think I will have issue with Google FRP.
Not sure if I go to download mode and root through Odin if I can then remove the pin (or through custom recovery) and do it without USB debugging enabled.
Why I need the data? The owner died few days ago (suicide) few days ago and the family and local police asked me for help to access the phone, so the information is very important.
I tried some things but I'm out of ideas right now. I don't care if the phone have warranty which will be lost.
Also, I'm not doing it for money, I'll do it to help the family.
Any help/idea will be great.
Thanks.
i have the solution
demlasjr said:
Hello everyone.
I need some help recovering data from a Samsung J7 (2016) with a screen pin. If it's possible, if I can remove only that pin without touching the apps in the phone will be great. I was thinking to format and then pass a recovery app after rooting but I think I will have issue with Google FRP.
Not sure if I go to download mode and root through Odin if I can then remove the pin (or through custom recovery) and do it without USB debugging enabled.
Why I need the data? The owner died few days ago (suicide) few days ago and the family and local police asked me for help to access the phone, so the information is very important.
I tried some things but I'm out of ideas right now. I don't care if the phone have warranty which will be lost.
Also, I'm not doing it for money, I'll do it to help the family.
Any help/idea will be great.
Thanks.
Click to expand...
Click to collapse
just go to youtube there is a video of tech trend
smartass08 said:
just go to youtube there is a video of tech trend
Click to expand...
Click to collapse
Which video? How if I don't have custom recovery but stock?
It doesn't help and I don't want to f**k the data trying to flash twrp without being sure the phone will boot up
UPDATE:
I have access to the Google account linked to the device. I set a PIN through device manager and tried it after inserting a sim card with internet, but I haven't wait enough and after inserting the PIN I got blocked another 60 minutes....damn.
I can't find if he set a Find my phone through Samsung (I don't know which email he used)
Hey everyone,
I am new to the programming scene and this forum.
Anyways, I run a repair business in Ontario and have repairs come in daily. In particular today, I had a Samsung Galaxy S7 come in for repair and the issue the customer explained was they forgot their pin or pattern lock. I used to be able to use TWRP and go into the system and delete the gesture.keys without losing all data but I read up on the new technology now with Knox and bootloader and I was told flashing TWRP on the Galaxy s7 without bootloader unlocked will cause bootloop. All I need is to get into TWRP to delete those keys because customer CANNOT lose any DATA (very important). Is there anyway to get TWRP on the Canadian variant without wiping or causing a boot loop. I don’t need root. Just need access to the system files from recovery to delete that key file. Unless someone else can chime in and offer another solution, but please HELP!
ghostnetworksolutions said:
Hey everyone,
I am new to the programming scene and this forum.
Anyways, I run a repair business in Ontario and have repairs come in daily. In particular today, I had a Samsung Galaxy S7 come in for repair and the issue the customer explained was they forgot their pin or pattern lock. I used to be able to use TWRP and go into the system and delete the gesture.keys without losing all data but I read up on the new technology now with Knox and bootloader and I was told flashing TWRP on the Galaxy s7 without bootloader unlocked will cause bootloop. All I need is to get into TWRP to delete those keys because customer CANNOT lose any DATA (very important). Is there anyway to get TWRP on the Canadian variant without wiping or causing a boot loop. I don’t need root. Just need access to the system files from recovery to delete that key file. Unless someone else can chime in and offer another solution, but please HELP!
Click to expand...
Click to collapse
If the bootloader on that device is locked, you won't ever be able to use TWRP at all, not ever, not by any means.
If you know exactly what firmware build number thay had installed before this happened, you can try flashing that exact version of stock firnware via Odin. As long as the firmware that you flash does not contain a different(upgraded/downgraded) bootloader, it "shouldn't" wipe their personal data but it does wipe the user settings(pin/pass in this case). When flashing via Odin, the user data does not get wiped unless the bootloader on the device is upgraded or downgraded during the flashing process. Their data should stay intact if you use the firmware version that is already on the device.
If the bootloader is locked, then regardless of what you do, flashing the firmware is the only way you're going to fix this, whether it wipes their data or not. Flashing the current firmware that is already on the device is really your only option.
Sent from my LGL84VL using Tapatalk
TWRP
I’ve managed to reset the password because cudtomerbhad her Samsung account linked to the phone. Logging into Samsung online gives you the option to remotely unlock the pattern. She now has all her data and password is gone. Thanks for the quick reply regardless
ghostnetworksolutions said:
I’ve managed to reset the password because cudtomerbhad her Samsung account linked to the phone. Logging into Samsung online gives you the option to remotely unlock the pattern. She now has all her data and password is gone. Thanks for the quick reply regardless
Click to expand...
Click to collapse
Ah yeah, I forgot about that option because I don't use the Samsung account feature on my phones. Plus, I was looking from a perspective of what could be flashed or not without causing data loss.
Sent from my LGL84VL using Tapatalk
Hi All
I have an S7 Exynos with latest Magisk installed and everything has been working flawlessly till I decided this early morning, for not any particular reason(except my increasing amount of grey hair ), to lock the "developer options". I think I have done the same maybe a couple of years ago though cannot remember how I had solved it.
Obviously my phone was instantly locked.
Would someone be able to link a good working solution with being able to keep data and apps? I am a bit desperate as my work is starting again tomorrow.
Thanks a lot.
look at frp bypass
Costum binary blocked by FRP lock is a protection, whene you do a factory reset from recovery. the only way you get this message is with odin.
this one works for me on s7, s7 edge and s6 tab
Thanks @Dagobert
I will have a look at it now and see if it is not too scary. See my S7 FRP
kiwigi said:
deleted as repeated post
Click to expand...
Click to collapse
Do you have acces to the phone?
kiwigi said:
deleted as repeated post
Click to expand...
Click to collapse
If you have acces to the phone then backup your data do a factory reset. Then you can flash whatever you want. Frp lock is a google protection with a google account. Whene you do a factory reset from settings you wipe the frp.
What is Google FRP?
FAQ for Samsung Mobile Device. Find more about 'What is Google FRP?' with Samsung Support.
www.samsung.com
I have access to the phone via PC/Odin only. No booting as per image above. I wand to keep Data and Apps
I assume I have to flash stock with home csc to be able to enter the phone again? Then root again, if I so wish?
Yup. Maybee a long shot but try Flashing your former firmware with Odin, using HOME_CSC. I think thats the solution
More info on that in this topic
Help! How to flash without losing data?
Good day! My phone got stuck on breathing Samsung logo after my phone updates. Now the only option I have in mind is to restore factory data. But I have some important files in my phone that is very essential in my work. I know I have read that...
forum.xda-developers.com
hmm., done the flashing with the files plus home csc and it asks for password, which I have entered without success. I know the password and it justs does not accept it.
See the factory reset warning and the FRP lock still being on now.
I'm desperately trying to avoid wipping data and apps.
edit: unfortunately I had to format/reinstall as I could not find a workable option.