Hi,
I rooted my Samsung Note 4 a couple months ago. Everything has been working great with the rooted device. However, I want to unroot the device so that I can install Android 5 (lollipop). When I press Vol up, center and on/off button, I get the message "dm-verity verification failed". So I cannot install the stock rom with ODIN since ODIN does not recognize the device. I have downloaded the correct version of ODIN, stock rom and windows drivers for Samsung Note 4 SM-N910F.
I also tried returning to factory settings on the recovery mode, but the message is still there.
Can Anybody help me please?
You need to press and hold power button + volume Down + home button to enter download/odin mode and be able to flash via odin
Hi All,
I have a SM-G920I,
rooted it with ping pong root (confirmed rooted with root checker app).
installed the twrp app and Stericson busy box
installed the twrp recovery mode or boot loader, it confirmed it was successful
rebooted into twrp recovery.*********PROBLEMS*****************
Its stuck at the SAMSUNG Galaxy S6 powered by android screen for more then 20 minutes.
I'ved tried
1) power+volume down (that reboots it) back to logo
2) I've tried the above and then volume up+power+home, releasing power when the logo appears
3) I've tried the above and then volume up+power+home, not releasing power when the logo appears
4) I've tried the above and volumn down+home.
all 4 options leave me with the same problem. samsung logo screen and no options
I've scowered the inter-webs for a solution and haven't found anything to help. similar posts always suggest "just volumn up+power+home to recovery mode" but I cannot get there.
any suggestions?
so I'm an idiot. apparently a combination of volume down+power then volume down+power+home put me in odin download mode. problem solved....
Hi All, I have a SM-T713 which was rooted, TWRP 3.0.2-1 installed and Lightning ROM 6.0.1 installed. Today I went to Settings | Developer Options and turned off the OEM unlock something. Then I went to the Terminal Emulator and run su, then reboot recovery. Now my tablet is stuck with "Custom binary blocked by FRP. SECURE FAIL: RECOVERY". I tried Home + Volume Down + Volume Up + Power, the tablet is restarted and then that message appears again. If I do Home + Volume Down + Home, a blue screen appears "If you want to download a custom OS, press the volume up key. Otherwise, press the volume down key to cancel". Pressing volume up show a Downloading... screen. Then I don't know what to do next.
Please help if you know how to fix it. If the instructions are for Linux (because I'm using Linux), it's the best. Windows instructions are ok too.
Thanks.
dxxvi said:
Hi All, I have a SM-T713 which was rooted, TWRP 3.0.2-1 installed and Lightning ROM 6.0.1 installed. Today I went to Settings | Developer Options and turned off the OEM unlock something. Then I went to the Terminal Emulator and run su, then reboot recovery. Now my tablet is stuck with "Custom binary blocked by FRP. SECURE FAIL: RECOVERY". I tried Home + Volume Down + Volume Up + Power, the tablet is restarted and then that message appears again. If I do Home + Volume Down + Home, a blue screen appears "If you want to download a custom OS, press the volume up key. Otherwise, press the volume down key to cancel". Pressing volume up show a Downloading... screen. Then I don't know what to do next.
Please help if you know how to fix it. If the instructions are for Linux (because I'm using Linux), it's the best. Windows instructions are ok too.
Thanks.
Click to expand...
Click to collapse
Hey i did the exact same thing, did you fixed it, if so how?
solved it
if you haven't solved it just download smart switch go to emergency recovery or something like that put your device model in my case (sm-t813)
and put your serial and you are pretty much done hope you the best
Never switch "OEM unlock" back to OFF
Hello, I have a SM-N920P with a custom FRP (FAP) Lock. I searched every forum and videos on YouTube to find out how I can unlock my phone. Most of the people downgrade the phone into 5.1.1 (Lolipop) or 6.0.1 (Masrshmellow) and the phone should boot to normal. However, I've used latest Odin (3.12) or Z3X Tool v27.2, and I cannot able to disable the FRP lock. I tried to used Z3X to disable the locked, but it kept saying "Searching Samsung USB Flash Interface... detected COM4
Setup connection... OK
Reading PIT from phone... OK
Searching FRP lock... OK
Erasing FRP... OK
Searching Reactivation lock... OK
Erasing Reactivation lock... error
Done with Samsung Tool PRO v.27.2"
Besides the FRP lock, I am unable to downgrade or using the stock ROM to flash the phone, it kept saying error and fail with various attempts. HOWEVER, I am able to flash my phone using the latest 7.0 Nougat (DQE1), and (DQC5). Yet, the phone keeps booting on a loop with a Samsung logo. This is a really rare case and I need anybody know more experience than me can help. Please reply ASAP and I'm looking forward for your reply. Thank you.
After flashing the stock 7.0 nougat. If it is in bootloop for 5-10 minutes. Power off your device. Go into recovery. Do a factory reset. Restart device.
Did you have any mods? I had the same problem yesterday. OEM Unlock was getting turned off and I don't know why. Just do a factory reset as the user above me said. Odin will not allow you to downgrade.
________
Hey, my phone is Sprint, too. My phone was getting the FRP lock after a few reboots. I have done several mods like TWRP, root by the latest Magisk, deodex, edge panels, csc tweaks...etc. The FRP lock debacle was on the newest Sprint build wich is DQF1. I downgraded to DQE1 and I noticed that OEM unlock was disabled. I guess that was the problem. In over 9 months of owning this unlocked phone, I didn't touch the OEM unlock. (I'm on a GSM Network)
BTW, OEM Unlock is located in Depeloper Options, to enable it you must enable developer options by going into the menu, search the build number and tap it several times.
Mustafa Jafri said:
After flashing the stock 7.0 nougat. If it is in bootloop for 5-10 minutes. Power off your device. Go into recovery. Do a factory reset. Restart device.
Click to expand...
Click to collapse
cachanilla86 said:
Did you have any mods? I had the same problem yesterday. OEM Unlock was getting turned off and I don't know why. Just do a factory reset as the user above me said. Odin will not allow you to downgrade.
________
Hey, my phone is Sprint, too. My phone was getting the FRP lock after a few reboots. I have done several mods like TWRP, root by the latest Magisk, deodex, edge panels, csc tweaks...etc. The FRP lock debacle was on the newest Sprint build wich is DQF1. I downgraded to DQE1 and I noticed that OEM unlock was disabled. I guess that was the problem. In over 9 months of owning this unlocked phone, I didn't touch the OEM unlock. (I'm on a GSM Network)
BTW, OEM Unlock is located in Depeloper Options, to enable it you must enable developer options by going into the menu, search the build number and tap it several times.
Click to expand...
Click to collapse
Thank you, based on what you guys saying, I understand that Samsung won't let you downgrade. I able to boot up 7.0 Nougat firmware to the phone (DQE1), and (DQC5). However, I keep getting bootloop after using Odin to flash the phone, and FRP lock is still on. Is there any tickmarks on ODIN that I have to check such as "Nand erase", "Auto reboot", "Flash lock", "F-reset time" or anything in the tickmarks? Then, I couldn't access to the recovery mode (vol up + home + power ) after odin sucessful flashed my phone. Is it because I got stuck in a bootloop and I cannot turn off my phone? I tried to took the battery off so the phone can be turn off, then when I tried to go to recovery mode, it's a bootloop again...Please help, I'll try different ways in order to get the phone to work again. Thank you.
PhuGamer said:
Thank you, based on what you guys saying, I understand that Samsung won't let you downgrade. I able to boot up 7.0 Nougat firmware to the phone (DQE1), and (DQC5). However, I keep getting bootloop after using Odin to flash the phone, and FRP lock is still on. Is there any tickmarks on ODIN that I have to check such as "Nand erase", "Auto reboot", "Flash lock", "F-reset time" or anything in the tickmarks? Then, I couldn't access to the recovery mode (vol up + home + power ) after odin sucessful flashed my phone. Is it because I got stuck in a bootloop and I cannot turn off my phone? I tried to took the battery off so the phone can be turn off, then when I tried to go to recovery mode, it's a bootloop again...Please help, I'll try different ways in order to get the phone to work again. Thank you.
Click to expand...
Click to collapse
You dont need to take out the battery. In note 5 you can power off the device by pressing Power button + Volume down button at the same time.
Do a factory reset using recovery.
Mustafa Jafri said:
You dont need to take out the battery. In note 5 you can power off the device by pressing Power button + Volume down button at the same time.
Do a factory reset using recovery.
Click to expand...
Click to collapse
Thank you. You made it sound so easy. I able to turn off the phone, but I still cannot access to the recovery mode. Is it vol up + power button + home for recovery? That's what I do after flash the phone, turn it off, and still a boot loop. FRP still on if I go back to download mode. Are you sure my tickmarks on ODIN is right? Heres a link for the pic: ibb.co/fHwwVF
PhuGamer said:
Thank you. You made it sound so easy. I able to turn off the phone, but I still cannot access to the recovery mode. Is it vol up + power button + home for recovery? That's what I do after flash the phone, turn it off, and still a boot loop. FRP still on if I go back to download mode. Are you sure my tickmarks on ODIN is right? Heres a link for the pic: ibb.co/fHwwVF
Click to expand...
Click to collapse
You dont need nand erase. Anyways seems like it wasnt the issue.
Power off device (Power + Volume Down)
Recovery (Power + Volume Up + Home)
Factory Reset.
Maybe try to flash again with only Auto Reboot and F. Reset Time TICKED.
Mustafa Jafri said:
You dont need nand erase. Anyways seems like it wasnt the issue.
Power off device (Power + Volume Down)
Recovery (Power + Volume Up + Home)
Factory Reset.
Maybe try to flash again with only Auto Reboot and F. Reset Time TICKED.
Click to expand...
Click to collapse
I tried multiple attempts but it doesn't work. Bootloop even though I tried to put into recovery mode. Nothing happend. Is it because of FRP lock? Or do I have to switch the rom or anything in the phone?
PhuGamer said:
I tried multiple attempts but it doesn't work. Bootloop even though I tried to put into recovery mode. Nothing happend. Is it because of FRP lock? Or do I have to switch the rom or anything in the phone?
Click to expand...
Click to collapse
Did you try flashing stock rom again? Tick only Auto Reboot and F. Reset time in Odin.
And keep in mind one thing. The first boot takes about 4-5 minutes.
Try flashing stock rom again if its still in bootloop then try going in recovery mode and do a factory reset.
If it still doesnt work then maybe I can help you through skype video.
Yea, I tried stock rom Nougat 7.0 for my N920P. Matter of fact, I tried to use other 7.0 firmware for the device but still the same. I can't downgrade like you mention. I continue to get bootloop, and I still cannot access to recovery mode no matter how I tried. It would be wonderful If you can do skype video.
PhuGamer said:
Yea, I tried stock rom Nougat 7.0 for my N920P. Matter of fact, I tried to use other 7.0 firmware for the device but still the same. I can't downgrade like you mention. I continue to get bootloop, and I still cannot access to recovery mode no matter how I tried. It would be wonderful If you can do skype video.
Click to expand...
Click to collapse
ok pm me your skype
Hi.
I am running stock 5.1. Phone is unlocked according to recovery - it states "unocked status 3". When I try to flash TWRP it does not stick. When I press volume down to choose reboot recovery it just turns off. When I try volume down and power to boot it comes back with an android on it's back saying no command.
Any ideas how I can fix this?
I sorted it.
I was pressing the power button instead of volume up when trying to choose boot recovery after twrp flash.