Related
Hi, I'm sorry if this isn't the right place to post this but Im having to use someone else's windows phone and its hard to navigate through the site.
My problem is that I tried to root my s6 edge plus using an application called King Root. The install got to 17% and then turned the phone off. When I load the phone up now I just get the message "custom binary locked by FRP lock" in red writing and the phone instantly boots off.
Is there a way to get around this without losing my data on my phone? I have some very important photos that are on there that I really don't want to lose, unfortunately nothing is backed up. I've been researching and apparently this is possible using a programme called Odin? I hope this is possible as I don't want to lose my stuff on my phone.
Any help would be great, thank you.
To be brutally honest if you haven't heard of Odin and you're using Kingroot, you're way out of your depth and you shouldn't be even thinking about rooting your device.
Not being nasty, sincerely. But you need to do a LOT of research.
The only way to rescue your device is to flash a stock firmware via Odin. There are guides on this site, read them and then read them again and again. Your photos are probably gone unfortunately. I would say definitely, but mircles can happen..
Good luck!
Maybe just flashing the stock bootloader may help but once you atart flashing the pda i think your photos may be gone. Unless where ever they are stored doesnt get over written they may be recovered uisng a data recovery app on the play store like gt recovery and the deep scan option.. it still finds photos from 5 new rom installs on my opo
I have a few Blackberry Privs to play around with atm. I have one that was exhibiting some unusual things before I flashed it, It seems like it was in some sort of test mode. I am not sure how to revert back to it, it seems like it was boot image AAC603 which allowed such testing to go on. sadly I didn't throw any Fastboot/ADB commands at it nor did I see if there was any diag ports open before I installed an OS on top of it. It doesn't seem to have an IMEI and now it just goes straight into bootloader mode.
if there was someway to get it back into testmode what commands should i throw at it ?
e.g. backup rom/partitions, "fix imei"
Is there a way to boot from the bootchain software backup version of the AAC603 ?
http://imgur.com/a/5gaqJ
How were you able to flash anything on this device? I know booting up still won't work, but maybe thisn could be helpful for eventual root access and flashing other ROMs?
(Soft-)Bricked S7 Edge/G935F with FRP lock & DRK error, but no root/OEM unlock/ADB
Hello guys,
I bought a, what I thought to be, soft bricked S7 Edge (G935F) from the bay. It was listed as having sw issues, so I thought I could easily fix the issue myself. Stupid me, this one really isn't easy to fix. I've tried a lot of different hints that I found meandering around the web, but none of them have proofed working so far. I would appreciate some help because I don't seem to be making any progress.
When I got the phone, it would boot directly into Android Recovery with a dm-verity error on the bottom.
Below is what I have tried already:
1 . First I did the obvious, factory reset and wipe partition. No change.
2. Downloaded the latest firmware with updato (SM-G935F Region DBT) and flashed with Odin. It then booted into a screen with a hazard sign and a DRK error (Device does not have DRK, please install DRK first. press any button). Then returned to Android Recovery with variations of the DRK and dm-verity error messages
3. I flashed the same firmware again. This time the phone booted up to a Samsung error that said to use SmartSwitch's Emergency recovery. I tried but it asks for a recovery code and I don't have one.
4. I used an older version of SmartSwitch which gave me the initialization option where you need to input the device model and SN - SmartSwitch decided not to cooperate and noted that the S7 edge does not support initialization
5. I tried to flash CF-autoroot but it gave an error in Odin and failed because it is "Blocked by FRP Lock". I can't boot normally into android. Any workaround?
6. I used a dm-verity workaround file (G935FXXU1DQC4_FIX_DRK_dm-verity.tar) to actually get the phone booted up- but then it asks for the account information to do away with the FRP lock. And the former owner does not want to give me his login information. In addition, none of the workarounds (bluetooth, modem terminal prompts, etc.) did work.
7. Flashed oldest Android version I could find for the G935F - 5.1.1 - this gave me a prompt right after reboot that looks like the password request for encrypting memory. default_password and variations did not work. I am still stuck with...
No Support SINGLE-SKU
Supported API: 3
dm-verity error...
failed code : 0x02
...in the recovery
8. I flashed the combination file and was able to boot into Factory Binary and used the IMEI recovery option which is supposed to fix also the DRK issue. No luck.
So, this is where I am right now. If anyone out there still has sparks of hope, I would be delighted to hear about them.
Thanks much in advance!
Conversion software and ADB Shell
Small update - I booted into factory mode again using the conversion firmware. This way, I could connect to the device via ADB and use ADB shell. There is a guide (here: https://forum.xda-developers.com/s7-edge/how-to/guide-how-to-fix-check-drk-imei-issues-t3379516) which guides through IMEI recovery using the conversion software and factory mode - that is supposed to also help with DRK issues. Did not work for me.
Another great guide (here: https://forum.xda-developers.com/no...fix-drk-dm-verity-factory-csc-serial-t3422965) used ADB shell to push and repair the DRK with some additional files. Since the device is not rooted, I did not get very far, either.
So, no progress whatsoever.
In summary, I can get the device booted up into factory mode using the conversion firmware, or, by using the dm-verity tweaked firmware, I can end up in the Google Account locked part of the initial start-up settings.
Any ideas?
Have you looked at the process to completely re-do a phone stuck in the Google auth log-in? At least that is how I understand where you are stuck. I have a phone arriving soon that I will need to re-flash to get out of that, via Odin.
JeffDC said:
Have you looked at the process to completely re-do a phone stuck in the Google auth log-in? At east that is how I understand where you are stuck. I have a phone arriving soon that I will need to re-flash to get out of that, via Odin.
Click to expand...
Click to collapse
Hi JeffDC,
Thanks a lot for the reply. How would this process look like? I have flashed the phone with all sorts of variations of Android L, M and N - plus the combination fw and the one with the dm-verity/DRK workaround which at least got the phone booted up. But then I am stuck at the google auth request.
I cannot flash anything custom since the FRP lock is on.
Hence, if there is any other way to re-do the phone as you are saying, I would live to hear about it.
https://forum.xda-developers.com/s7-edge/help/s7-edge-custom-binary-block-frp-lock-t3347688
https://forum.xda-developers.com/s7-edge/how-to/guide-how-to-fix-check-drk-imei-issues-t3379516
https://forum.xda-developers.com/no...fix-drk-dm-verity-factory-csc-serial-t3422965
JeffDC said:
https://forum.xda-developers.com/s7-edge/help/s7-edge-custom-binary-block-frp-lock-t3347688
https://forum.xda-developers.com/s7-edge/how-to/guide-how-to-fix-check-drk-imei-issues-t3379516
https://forum.xda-developers.com/no...fix-drk-dm-verity-factory-csc-serial-t3422965
Click to expand...
Click to collapse
Hi JeffDC,
Thanks a lot for the links.
Link #1: I can flash the file #1 and get the device visible for ADB by using the combination FW before starting the steps. Unfortunately, step #2 does not work due to lack of permissions. I guess because of missing root.
Links #2 and #3: These are the guides I was already referencing in my post #2 - they both do not work due to, I guess, missing root.
Smart Switch initialization
Update: I got smart switch to do the update and initialization for the device. Workaround was to use a different real serial number than the one of the actual device (I can only assume that it has got to do with country presets).
Cool stuff, all went smooth - but, still the same result. The device ends up in recovery showing the dm-verity error (failed code : 0x02) with FRP lock on and no root.
https://forum.xda-developers.com/ve...-factory-reset-protect-unlock-t3414590/page11
Interesting read, particularly ignoring the trojan squabbling.
Uses script and setup files to get around FRP.
I suggest you to re-try flashing with Odin the Stock Marshmallow Firmware. Then Boot Into Stock Recovery do a Full Wipe.
zzThrain said:
I suggest you to re-try flashing with Odin the Stock Marshmallow Firmware. Then Boot Into Stock Recovery do a Full Wipe.
Click to expand...
Click to collapse
Thanks for the recommendation. Done that (MM downgrade and full wipe) - same result, still DRK error only booting to recovery.
JeffDC said:
https://forum.xda-developers.com/ve...-factory-reset-protect-unlock-t3414590/page11
Interesting read, particularly ignoring the trojan squabbling.
Uses script and setup files to get around FRP.
Click to expand...
Click to collapse
Hi JEffDC, thanks for the follow-up hints. Very interesting read and approach. As commented in the other thread, I think the package download link in the opening post is dead. I am also curious to see 2 more complexities in action:
1. Will this work on a G935F variant (Exynos vs Snapdragon)?
2. The only way for me to get to the Google Account prompt is by using the modded dm-verity version mentioned in my first post - but I am not sure I can get ADB access enabled simultaneously
Good luck.
Deleted
Hey sathiere,
Came across this. It apparently removes the FRP before the system can start it up! Let me know what you think. I'm going to try it on a locked Edge next week or two. Seems to go right after the FRP protection file.
https://forum.xda-developers.com/galaxy-s7/help/how-to-bypass-frp-galaxy-s7-possibly-6-t3622126
and the download link works.
JeffDC said:
Hey sathiere,
Came across this. It apparently removes the FRP before the system can start it up! Let me know what you think. I'm going to try it on a locked Edge next week or two. Seems to go right after the FRP protection file.
https://forum.xda-developers.com/galaxy-s7/help/how-to-bypass-frp-galaxy-s7-possibly-6-t3622126
and the download link works.
Click to expand...
Click to collapse
Hi JeffDC, came across that thread last night - checked it out, but cannot really make sense of it just now. I will be posting directly in this one in the next minutes.
Regarding the link for the other thread - the google drive link for me shows invalid/no content...
sathiere said:
Hi JeffDC, came across that thread last night - checked it out, but cannot really make sense of it just now. I will be posting directly in this one in the next minutes.
Regarding the link for the other thread - the google drive link for me shows invalid/no content...
Click to expand...
Click to collapse
Yes, I am hoping for a response to my post there, near the end, clarifying. I think I get the method, and it's really pretty straight forward, really.
sathiere, I think basically what it does is provide two connections to the phone at the same time, one via Odin, and the other via direct ADB.
Step one is to flash a Universal boot loader, which is unlocked or can be unlocked via ADB. Now with the locked boot loader out of the way, on to getting rid of FRP.
Step two is run the. bat file which deletes the Persistence file, which is the Google encrypted setup file/FRP file. BOOM, FRP gone.
Then either stay on the Universal bootloader, or go back and flash the OEM.
Brilliant!
I have the same problem with a sm930f binary 2 boot loader. Stock Rom doesn't start and frp lock. How you fix it ? Thank you
Try this method
https://forum.xda-developers.com/general/general/solved-bypass-frp-lock-drk-error-t3779082
Admin, sorry, but the suggestions were close, but no cigar...
So I got sick and tired of trying to Google "Google FRP bypass" on Nougat 7.0 (Google got "smart" and hid those?)...
I went through Cellunlocker, and they did a remote desktop connection, downgraded my S6 Edge plus from 7.0 to 6.0.
After they downgraded my OS, they used some tools, like usbredirector.exe and some others, I couldn't see their computer screen... so I don't know what else they used, they managed to bypass the FRP, I was presented with the home screen! Yeah! The download of the OS took a little under an hour, but the bypass took mere minutes. I trust them to unlock, and do FRP bypass.
After that though, I noticed that the 32GB that's supposed to be there, ISN'T.
It is now only 8GB.
I've yet to hear back from them... But, I thought I'd ask here.
I was given a Stock ROM from Poland or something (I've the International model.) It is loaded with the usual bloatware that Samsung and Google hands out. I barely got enough room to sideload Super SU (Google Play wouldn't as the memory requirements weren't met.)
I tried to upgrade to Nougat 7.0 which did work, but I've no idea where the rest of the memory disappeared to.
Factory reset doesn't work, and I tried to free up some space by sideloading system/app/mover, and it fails, stating that "couldn't remount /system."
Has anybody else experienced this issue, and is there a fix for this?
dave68 said:
Admin, sorry, but the suggestions were close, but no cigar...
So I got sick and tired of trying to Google "Google FRP bypass" on Nougat 7.0 (Google got "smart" and hid those?)...
I went through Cellunlocker, and they did a remote desktop connection, downgraded my S6 Edge plus from 7.0 to 6.0.
After they downgraded my OS, they used some tools, like usbredirector.exe and some others, I couldn't see their computer screen... so I don't know what else they used, they managed to bypass the FRP, I was presented with the home screen! Yeah! The download of the OS took a little under an hour, but the bypass took mere minutes. I trust them to unlock, and do FRP bypass.
After that though, I noticed that the 32GB that's supposed to be there, ISN'T.
It is now only 8GB.
I've yet to hear back from them... But, I thought I'd ask here.
I was given a Stock ROM from Poland or something (I've the International model.) It is loaded with the usual bloatware that Samsung and Google hands out. I barely got enough room to sideload Super SU (Google Play wouldn't as the memory requirements weren't met.)
I tried to upgrade to Nougat 7.0 which did work, but I've no idea where the rest of the memory disappeared to.
Factory reset doesn't work, and I tried to free up some space by sideloading system/app/mover, and it fails, stating that "couldn't remount /system."
Has anybody else experienced this issue, and is there a fix for this?
Click to expand...
Click to collapse
Find stock rom with .pit file and flash in odin
I was given stock ROM 6.0, but I don't know if it has the .pit file... How would I know? I use the samtool to get the ROM from Samsung, wouldn't it have it? Please and Thanks again!
Also, does that determine whether or not we have 32GB VS 64GB? Or is there a physical limitation? There must be, but just curious if I load the .pit for a 64GB device, could I be THAT lucky?
Frp bypass Oreo Samsung Galaxy s6 plus
I’m sorry I’m posting to wrong area but I can’t figure out how to post I think I’m having a brain overload Can someone please help me I’ve spent the last three days trying to bypass FRP lock on the Samsung S6 plus for my daughter because she got scammed and got a phone that was in a lock on craigslist I have tried every and all forms where I seem to get stuck each time is downloading the driver for Samsung USB driver it downloads from all the sites but none of them work or show up in my device manager so all the methods are impossible at that point what is it that I’m doing wrong.
The .pit file does indeed determine 32gb or 64gb... without It, 8gb. Also I have a copy of.... wait... is that the S6 Edge +? If so I have original stock with proper. Pit file. If not, you have to keep looking... hope this helps.
Falleninkedangel said:
I’m sorry I’m posting to wrong area but I can’t figure out how to post I think I’m having a brain overload Can someone please help me I’ve spent the last three days trying to bypass FRP lock on the Samsung S6 plus for my daughter because she got scammed and got a phone that was in a lock on craigslist I have tried every and all forms where I seem to get stuck each time is downloading the driver for Samsung USB driver it downloads from all the sites but none of them work or show up in my device manager so all the methods are impossible at that point what is it that I’m doing wrong.
Click to expand...
Click to collapse
I actually have firmware / unlocking software I could probably give you a hand
Edit 3: TL;DR: This is appears to be an S8 exclusive error, it's shown in the recovery:
"Product device tree not found, couldn't verify firmware" or something like that. For solutions, please look that up.
So, I bought a bootlooping S8 in the hopes of fixing it.
Since OEM and FRP lock are on, I went with installing Samsung firmware on it, as installing a custom recovery at this point is not possible.
The default recovery wouldn't work, so I wasn't able to know which firmware exactly to flash, because I couldn't find out which model exactly I have bought.
I do not know the carrier of the device either, but it should be from some german provider.
All of the firmwares I tried just bootlooped, but the recovery works again, except for ADB, which is quite unfortunate, and I have no idea why it fails, the device shows up when I'm in the recovery menu, but as soon as I activate ADB, it's gone from the list of connected devices.
Combination firmwares sometimes show some turning gears animations, but then crash with some, thought often memory related, pretty random crash issue.
Another problem I am now facing is that in the process of trying to find a working firmware I now upgraded the devices "binary level"? (forgot what exactly it was called) to 6, so I can't flash any older firmware or combination firmware than 6, since downgrading isn't allowed.
I received the device with either binary level 1 oder 2.
My theory is that I don't have the right firmware, since I keep seeing dm-verity and license errors...
I am happy to provide logs if necessary.
The goal is to have an unlocked bootloader/ custom recovery.
I literally am going INSANE over this FRP blocking me from flashing TWRP and being done with this in under 10 minutes, please help :c
PS: Some random info attached
Edit 1: With the IMEI code i found while opening the phone I now know my model number: SM-G950FZKADBT.
Any tips for finding the PDA code of the originally installed system? Or finding a matching firmware?
Is this even neccesary? Why do official firmwares not work for me? :c
Edit 2: Somewhat solution: I think the only way to recover this device would be to find it's firmware, which is just NOT to be found...
So, until a miracle happens I'm gonna keep reading "Firmware is not valid" errors in the log
Did you look in samfrew.com ? ? ? I just grabbed a fw from there.
The dnld was loooong so I purchased a privilege for faster speed . . .