Hello, and thank you all for reading and trying to help. Let me explain the situation..
all working until i accidently went into dev options and forgot to turn the OEM Bootloader Unlock back on. Reboot and FRP fail. Yes rookie error.
So after trying to reflash stock firmware (U5), reboot into stock recovery and dm-verity error occurs. FRP lock is on so i cannot flash TWRP and im all out of ideas...
things ive tried.
tried multipule combinations of flashing boot.img, repacking stocks with and without certain img contents etc and reflashing. Maybe i havnt found the right combination?
reflashing stock firmware (N920IDVU5CRK2_N920ITEL5CRK1_TEL), and wiping DATA from recovery after ODIN PASS. Just noticed the other day if i do the recovery key combo after its first initial boot during the 'installing update' screen, it will pose a 'no command' screen, then after a few moments dumps me into the recovery with a dm-verity successfull. But if i reboot again it will dm-verity error. So i was thinking maybe i need to hit download mode after the successful dm-verity and flash without recovery.img. Not sure as my lack of understanding but id love to fix this.
any help, suggestions would be appreciated and if any further information is needed im more than happy to provide.
(phone is out of warrenty)
(currently binary 5 and using stocks from sammobile)
Try root with ctautoroot
Sent from my Redmi Note 8 using Tapatalk
Related
Hi
The device is Samsung Galaxy Tab S2 8.0 SM-T713.
Following is what happened:
1. Installed TWRP and then Installed Lightning ROM v1.0.
2. Restarted the tablet without turning on OEM Unlock.
3. Did not boot by giving error "custom binary blocked by frp lock"
4. Tried installing stock firmware with odin. Firmware installs successfully but when the tablet reboots, it keep showing the glowing samsung logo.
5. Tried multiple different firmwares and eventually tried the latest firmware for the XAR region. Now only that firmware can be installed and all other older firmwares fail in the installation step giving the error "sw rev check fail aboot fused 2 binary 1"
Would really appreciate if anyone could help.
I assume that flashing pit file with the latest XAR region firmware will help boot the tablet but i cannot find the pit file to use.
Please HELP!
I think your problem is the result of flashing TWRP prior to flashing the stock ROM via Odin. Try this. Do a full wipe via TWRP. Then instead of booting into TWRP and then selecting "download" to use Odin, boot directly into download mode by holding Home, Vol down and power. Then flash the stock ROM. This should not only allow you to boot, but should also replace TWRP with the stock recovery. If it still doesn't boot, you should be able to use the stock recovery to perform a full wipe and again try Odin to install stock. But until you get the stock ROM to boot, trying any other ROM is useless.
lewmur said:
I think your problem is the result of flashing TWRP prior to flashing the stock ROM via Odin. Try this. Do a full wipe via TWRP. Then instead of booting into TWRP and then selecting "download" to use Odin, boot directly into download mode by holding Home, Vol down and power. Then flash the stock ROM. This should not only allow you to boot, but should also replace TWRP with the stock recovery. If it still doesn't boot, you should be able to use the stock recovery to perform a full wipe and again try Odin to install stock. But until you get the stock ROM to boot, trying any other ROM is useless.
Click to expand...
Click to collapse
The problem is that the TWRP recovery is long gone. Its not on the tablet anymore. I cannot flash TWRP because of FRP lock. I can access stock recovery but it also does not allow me to wipe data and factory reset due to FRP lock.
Any other suggestions.
I was able to finally restore the device using the method described in a sammobile forum.
Look at the second post on the thread titled " SmartSwitch: Install & update or replace firmware".
It is a tutorial to reinitialize the device to factory settings using Samsung Smart Switch software.
rafayzq said:
I was able to finally restore the device using the method described in a sammobile forum.
Look at the second post on the thread titled " SmartSwitch: Install & update or replace firmware".
It is a tutorial to reinitialize the device to factory settings using Samsung Smart Switch software.
Click to expand...
Click to collapse
I can't find that thread in the Sammobile forum but just googling "FRP lock" brings up a bunch of You Tube videos on how to remove the lock. Personally, I've never run into the problem.
I didn't realize from the OP that getting the stock ROM back was due to the lock but rather that the tablet was stuck at the Samsung logo rather that where you are asked for the Google login info.
Just so I've got it right and others understand, before you attempted to install a new ROM, was there an option in settings that would have allowed you to turn off using the lock and thereby have avoided the problem?
lewmur said:
I can't find that thread in the Sammobile forum but just googling "FRP lock" brings up a bunch of You Tube videos on how to remove the lock. Personally, I've never run into the problem.
I didn't realize from the OP that getting the stock ROM back was due to the lock but rather that the tablet was stuck at the Samsung logo rather that where you are asked for the Google login info.
Just so I've got it right and others understand, before you attempted to install a new ROM, was there an option in settings that would have allowed you to turn off using the lock and thereby have avoided the problem?
Click to expand...
Click to collapse
All the problems started when i restarted the tablet running a custom rom without enabling the OEM Unlock option in Developer Options in settings.
The lesson i learned the hard way is that you should always keep the OEM Unlock enabled
Hello,
I am new to this forum, but have done a bit of unlocking and installing custom roms on other phones (mostly OPO's, both my old one and friends). But this new OP 3T I just got is giving me some troubles I have not encountered before. I would LOVE to put this into the correct forum, but of course with my being new to this forum...rules...
I am following the standard install over on the TWRP site and on the OP3T, the install finishes and then I reboot and I get a screen that says:
"Your device has been unlocked and can't be trusted. If you don't want to see this screen, please lock your device by "fastboot oem lock" an erase userdata..."
I have never seen this before. Can someone give me a idea what could be going on here? Do I need to re-lock it? What did OP do to their phones!!?!
Oh and also, I am planning on installing LineageOS. Any reason I shouldn't?
Thanks!
Blenderite said:
Hello,
I am new to this forum, but have done a bit of unlocking and installing custom roms on other phones (mostly OPO's, both my old one and friends). But this new OP 3T I just got is giving me some troubles I have not encountered before. I would LOVE to put this into the correct forum, but of course with my being new to this forum...rules...
I am following the standard install over on the TWRP site and on the OP3T, the install finishes and then I reboot and I get a screen that says:
"Your device has been unlocked and can't be trusted. If you don't want to see this screen, please lock your device by "fastboot oem lock" an erase userdata..."
I have never seen this before. Can someone give me a idea what could be going on here? Do I need to re-lock it? What did OP do to their phones!!?!
Oh and also, I am planning on installing LineageOS. Any reason I shouldn't?
Thanks!
Click to expand...
Click to collapse
Is nothing wrong with your device ..What you get is a warning that your bootloader is unlocked ...
You gonna get this every time you want to boot to your ROM or to twrp....
You can proceed further to install any ROM that you like...
I think you can find a guide on XDA forums to disable this warning if you want...
cultofluna said:
Is nothing wrong with your device ..What you get is a warning that your bootloader is unlocked ...
You gonna get this every time you want to boot to your ROM or to twrp....
You can proceed further to install any ROM that you like...
I think you can find a guide on XDA forums to disable this warning if you want...
Click to expand...
Click to collapse
Ok I tried that and a new problem came up!! When I try to reboot into recovery, I do not get TWRP, but the stock recovery that was there originally! Unless they have completely changed the look of TWRP. I will try to upload a picture of it if that helps.
You can't get rid of the bootloader-unlocked warning without re-locking your bootloader, which you really should not do while you have a custom recovery installed.
Are you sure you've flashed TWRP and not just booted it it from a local file on your computer? Try using fastboot to wipe recovery first before flashing TWRP.
Anova's Origin said:
You can't get rid of the bootloader-unlocked warning without re-locking your bootloader, which you really should not do while you have a custom recovery installed.
Are you sure you've flashed TWRP and not just booted it it from a local file on your computer? Try using fastboot to wipe recovery first before flashing TWRP.
Click to expand...
Click to collapse
I followed the Fastboot method on this page (rules won't let me post the link normally): twrp. me/devices/oneplus3t.html
Blenderite said:
I followed the Fastboot method on this page (rules won't let me post the link normally): twrp. me/devices/oneplus3t.html
Click to expand...
Click to collapse
Right on that page (last paragraph of fastboot install method), you will see:
Note many devices will replace your custom recovery automatically during first boot. To prevent this, use Google to find the proper key combo to enter recovery. After typing fastboot reboot, hold the key combo and boot to TWRP. Once TWRP is booted, TWRP will patch the stock ROM to prevent the stock ROM from replacing TWRP. If you don't follow this step, you will have to repeat the install.
I had a heck of a time with this myself (even reading the above). Even rebooting (after flash TWRP) to recovery (power+vol down), the TWRP install would still not "stick". Had to try multiple times. I also rooted with SuperSU 2.79 at some point in that process, which may or may not have helped TWRP to finally "stick".
redpoint73 said:
Right on that page (last paragraph of fastboot install method), you will see:
Note many devices will replace your custom recovery automatically during first boot. To prevent this, use Google to find the proper key combo to enter recovery. After typing fastboot reboot, hold the key combo and boot to TWRP. Once TWRP is booted, TWRP will patch the stock ROM to prevent the stock ROM from replacing TWRP. If you don't follow this step, you will have to repeat the install.
I had a heck of a time with this myself (even reading the above). Even rebooting (after flash TWRP) to recovery (power+vol down), the TWRP install would still not "stick". Had to try multiple times. I also rooted with SuperSU 2.79 at some point in that process, which may or may not have helped TWRP to finally "stick".
Click to expand...
Click to collapse
I tried this once before, but after your suggestion to try it several times, it finally worked! Thanks!!
Flash TWRP, reboot, press the volume down key before the phone boots, go into recovery, you should see TWRP flash screen, that usually works but I'm glad you got it going
Hello everyone,
I am not completely new to customizing but I've run into a problem and I have tried everything I knew to try and everything I have searched for online so far.
What I have:
Galaxy Note 5
SM-N920T
Baseband: N920TUVS5ERF2
I installed twrp to perform a full system backup in preparation for a full factory reset. The backup was successful, no problem there. I did the factory reset from twrp, now all the phone will do is reboot into the recovery menu and now it says "dm-verity error... failed code: 0x02)
I flashed it back to full stock with ODIN with the latest firmware, which said successful, but boots into recovery.
I flashed 4 of the older official firmware, boots into recovery.
I reflashed twrp and restored the backup, boots into recovery.
I flashed a custom rom, recovery.
Had twrp reload the filesystem with EXT4...
Used ADB to disable verity checks...
Used ADB to pull, push and rebuild permissions for the build.prop edited to disable verity checks...
Nothing has worked and I am out of ideas.
Hopefully, someone reading this will have the key to getting this fixed. It's a good phone, well cared for and I don't want to replace it.
Thanks in advance for any and all help. :fingers-crossed:
flash no-verity-opt-encrypt zip file?
topgunpilott said:
Hello everyone,
I am not completely new to customizing but I've run into a problem and I have tried everything I knew to try and everything I have searched for online so far.
What I have:
Galaxy Note 5
SM-N920T
Baseband: N920TUVS5ERF2
I installed twrp to perform a full system backup in preparation for a full factory reset. The backup was successful, no problem there. I did the factory reset from twrp, now all the phone will do is reboot into the recovery menu and now it says "dm-verity error... failed code: 0x02)
I flashed it back to full stock with ODIN with the latest firmware, which said successful, but boots into recovery.
I flashed 4 of the older official firmware, boots into recovery.
I reflashed twrp and restored the backup, boots into recovery.
I flashed a custom rom, recovery.
Had twrp reload the filesystem with EXT4...
Used ADB to disable verity checks...
Used ADB to pull, push and rebuild permissions for the build.prop edited to disable verity checks...
Nothing has worked and I am out of ideas.
Hopefully, someone reading this will have the key to getting this fixed. It's a good phone, well cared for and I don't want to replace it.
Thanks in advance for any and all help. :fingers-crossed:
Click to expand...
Click to collapse
Contact me on [email protected]
I will help you
Okay.....I need help!
I have never been this stuck or confused with a phone/Android in my life. First let me state that my bootloader is unlocked and I am on pie stock variant 55.24. that is as far as I can get apparently. I have tried rooting/installing twrp to no avail. I am able to boot twrp through the bootloader with the command but I am not able to boot it through the bootloader option even after flashing the boot.Img found in this thread. I am very perplexed as to what im missing and now I feel like a total moron as I am probably missing a very simple step. I have the apparent dm no verity zip but am unaware where to flash it if I cannot really get into twrp property.
I would appreciate any help.
I should state that when I try and boot into twrp from the bootloader option it just says no command.
i was installing a gsi, i went into recovery, i wiped all, and then when i rebooted, it said dm-verity is corrupted, i tried to go into recovery, it doesn't work and i get the same error, so i tried to flash the official stock rom, nothing, do you have a way to fix it? (adb doesn't work since the recovery doesn't work, i tried to reflash it but nothing)
Gamer_Mida said:
i was installing a gsi, i went into recovery, i wiped all, and then when i rebooted, it said dm-verity is corrupted, i tried to go into recovery, it doesn't work and i get the same error, so i tried to flash the official stock rom, nothing, do you have a way to fix it? (adb doesn't work since the recovery doesn't work, i tried to reflash it but nothing)
Click to expand...
Click to collapse
You can always start from scratch, in BROM mode.
Here I show how to do it:
No Recovery, No Fastboot, No FastbootD – No Problem! – Case Study with Xiaomi Redmi Note 10 5G
Caution: The process shown below is not for the average user. If you do not understand the process, you should not do it at all. There is a risk of rendering your phone completely dead. Should you …
diy.viktak.com
thanks