I have an XT907 I used with Verizon for a while in NJ, then gave it to my kid for playing games once I changed carriers (mid-contract). I've looked at the phone and it would get stuck at the red eye screen. I've gone to recovery and wiped the user data/cache, no help.
The bootloader is LOCKED (and doesn't seem eligible to unlock). I've tried using Matt Groff's Razr utility to restore the system/boot images, but my guess is that since the bootloader is locked, it won't let me overwrite critical system files. I think I may have messed something up by trying to update some of the files but not the core system files. Maybe that's not even the problem, I dunno.
I've looked at how to unlock a bootloader but it seems to require root access, which I can't get since the device is unbootable. The device is also ineligible for unlocking normally (thanks, Verizon). Now it's stuck on an infinite loop with the red eye for about 25 seconds, then reboots. Repeat forever. Do I have any other choices for recovering my system? Can the device be unlocked via fastboot (maybe a custom recovery image)? Or is the problem not even the system/boot images?
Or am I SOL? I can't go to Verizon because I bailed from the contract. Not sure if they were (somehow) responsible for messing up the phone in the first place?
blakeloverain said:
I have an XT907 I used with Verizon for a while in NJ, then gave it to my kid for playing games once I changed carriers (mid-contract). I've looked at the phone and it would get stuck at the red eye screen. I've gone to recovery and wiped the user data/cache, no help.
The bootloader is LOCKED (and doesn't seem eligible to unlock). I've tried using Matt Groff's Razr utility to restore the system/boot images, but my guess is that since the bootloader is locked, it won't let me overwrite critical system files. I think I may have messed something up by trying to update some of the files but not the core system files. Maybe that's not even the problem, I dunno.
I've looked at how to unlock a bootloader but it seems to require root access, which I can't get since the device is unbootable. The device is also ineligible for unlocking normally (thanks, Verizon). Now it's stuck on an infinite loop with the red eye for about 25 seconds, then reboots. Repeat forever. Do I have any other choices for recovering my system? Can the device be unlocked via fastboot (maybe a custom recovery image)? Or is the problem not even the system/boot images?
Or am I SOL? I can't go to Verizon because I bailed from the contract. Not sure if they were (somehow) responsible for messing up the phone in the first place?
Click to expand...
Click to collapse
Do you know what system version your device was on before this incident?
If you were on Jelly Bean - I would suggest flashing 183.46.10 (the first KitKat build) with RSD Lite - then root and unlock the bootloader.
If you were already on KitKat - then you can restore with RSD Lite.
Everything you need > http://forum.xda-developers.com/droid-razr-m/general/guide-faq-how-to-root-boot-unlock-t2869432
As the title implies. Is this possible? if so, how?
I'm talking about the one that says "your device can't be checked for corruption" .... etc
No
It's not the end of the world, but I'm hoping that someone will find a workaround for this.
Seeming that it's allowed and doesn't break manufacturers warranty, it seems rather odd to consistently display this at boot after the first time.
It's because you bootloader is unlocked, therefore it doesn't pass certain security checks. It's like that with the Nexus 6p and I'm sure it's like that with the pixel. That will never change I don't believe.
Also becareful not to ever lock your bootloader while you have a custom recovery installed or you will brick your device.
Eric214 said:
It's because you bootloader is unlocked, therefore it doesn't pass certain security checks. It's like that with the Nexus 6p and I'm sure it's like that with the pixel. That will never change I don't believe.
Also becareful not to ever lock your bootloader while you have a custom recovery installed or you will brick your device.
Click to expand...
Click to collapse
My Nexus 4 and 6 didnt have that warming but my Moto E 2015 does. I think its based on the phone. All UNLOCKED Bootloader.
Warning Sucks!
It's a security requirement set by Google (to show a warning message like that) as part of the agreement for OEMs to use Android on their devices. It will not be going away anytime soon.
The Axon 7 has a patch to get rid of this warning...
(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
I have had my Essential Phone for almost two years now and one day last week when I turned the phone on I saw the following error message.
You device is corrupt. It can't be trusted and may not work property.
Visit this link on another device:
gc.o/ABH
Press Power Key to Continue
There is a red exclamation point at the top that looks like this <!>. I contacted Essential Support and they told me the only way that message gets displayed is when someone has unlocked the bootloader at some point. I have never connected my phone to a USB cable for anything other then charging it with a power outlet and I have certainly never heard of ADB before this error occurred.
I would like to know how this error has happened if all I do is install a few apps from the Play Store and install OS updates when the are officially available OTA. Essential Support has said its my fault and will not help.
I tried to reset the phone back to factory settings several times. I have used the reset from within the Settings, I have used ADB to side-load the latest OTA OS from Essentials website and I have also tried some kind of flashing reset but no matter what I did I could not get this error to go away. These methods are described on the Essential site linked below.
Here is the link to Essentials website that I used. Since this is my first XDA post it will not let me post the whole URL. (essential.com/developer/current-builds)
I eventually ran the following command which did remove the error.
Code:
adb reboot "dm-verity enforcing"
From what I can tell this just prevents the error message from being displayed, correct? If the reason for the error is still there then what are my options? Should I worry about this error? Is it possible for me to reset the phone in someway to get this error message to go away and put the phone back into a secure and safe state? I don't care about any user data on the phone. The whole thing can be erased, which I think I have done sever times already trying to fix this.
Any suggestions would be greatly appreciated because beyond trying to fix this error I have no experience with ADB or modifying a phone in anyway.
Thanks,
-eric
Is there anyone who can offer help?
EricAndroid said:
Is there anyone who can offer help?
Click to expand...
Click to collapse
You can unlock your bootloader and unlock critical partitions than flash the latest bts (back to stock) from the link below. Make sure to read the directions and use a quality type c USB 3.0 or 3.1. you basically download the zip and unzip it, then run the flash-all-wipe.bat from fastboot mode. This will fix the actual problem. Good luck and make sure to ask in that thread if you get stuck.
Almost forgot, make sure to download the Essential Window's drivers(from thread below as well). You don't need to worry about setting up adb and fastboot because it's Automatic when you run the commands from the zip you download. Also make sure you first uninstall any instance of adb or fastboot that may already be on your computer.
https://forum.xda-developers.com/es...ment/stock-7-1-1-nmj20d-t3701681/post74437484
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 . . .