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
Related
First of all sorry for my English...
Yesterday I was trying to install vanir room to my p880 after 10 hours I rooted the phone and unlock the bootloader then installed cwm but after reboot I get stuck on logo so I used kdz and load LGP880AT-00-V20a-262-000-MAR-26-2013+0 with (after 4 hours ) then i try using twrp and finally load the room (vanir_p880_4.4.4.112414.zip) and Gapps after rebooting I started getting crashes ( aosp keyboard, com.google, home and back buttons etc didn't work)
so again kdz then i try other room Paranoid but the same thing..
What I'm doing wrong? I used factory reset, wipe etc but same results
what gapps you flashed?
blansh heretics
The ones that are here http://forum.xda-developers.com/showthread.php?t=2439739
But I load another rom without gapps and got same errors, wizard stopped, com.Google stopped. And keyboard.
G0ll0 said:
The ones that are here http://forum.xda-developers.com/showthread.php?t=2439739
But I load another rom without gapps and got same errors, wizard stopped, com.Google stopped. And keyboard.
Click to expand...
Click to collapse
I don't really know what happened, did you successfully flashed kdz?
Where did you get it from? Here?: http://lg-phone-firmware.com/index.php?id_mod=15
Try to flash one of these (choose correct one for you)
Than you have to install recovery again.
But before that you can try to wipe /system, /data, /cache and then flash CM11 (I know it works without problems)
And I recommend you these Gapps: http://forum.xda-developers.com/showthread.php?t=2397942
LGaljo said:
I don't really know what happened, did you successfully flashed kdz?
Where did you get it from? Here?: http://lg-phone-firmware.com/index.php?id_mod=15
Try to flash one of these (choose correct one for you)
Than you have to install recovery again.
But before that you can try to wipe /system, /data, /cache and then flash CM11 (I know it works without problems)
And I recommend you these Gapps: http://forum.xda-developers.com/showthread.php?t=2397942
Click to expand...
Click to collapse
well... yes i think I flashed kdz (LGFlashTool ?) I used kdz to recover my phone to original, I know my phone is Korean version and right now I use P88020A-EUR-XXX original firmware installed with kdz
What is CM11? and how i flash it?
so I have to root and unlock bootloader again and use twrp again right?
G0ll0 said:
well... yes i think I flashed kdz (LGFlashTool ?) I used kdz to recover my phone to original, I know my phone is Korean version and right now I use P88020A-EUR-XXX original firmware installed with kdz
What is CM11? and how i flash it?
so I have to root and unlock bootloader again and use twrp again right?
Click to expand...
Click to collapse
I think you should try with CWM first, get it: http://download2.clockworkmod.com/recoveries/recovery-clockwork-touch-6.0.4.5-p880.img
you can flash it with this app if you are rooted: https://play.google.com/store/apps/details?id=com.cgollner.flashify
then you can download CM11 from here: http://download.cyanogenmod.org/?device=p880
and gapps from last mine post
and then boot to recovery, do factory reset and wipe /system, then flash rom and gapps.
Hope it helps
Crash After Flash OTA Vanir 5.0
I had a similar experience. I was installing OTA latest update of Vanir...not realising that it was 5.0...a screen came up telling me that it needed to flash another recovery...not realising why it needed that, I ignored the request to flash. Of course, I then "bricked" the phone. I was able to install the original JB 4.12 (v20c) back onto the phone but now it won't root. I've tried almost every method in this forum to no avail.:
ADB just gives a message "error: closing" when I use the boot.exe method
o4xr method does nothing
all-in-one method also does nothing
ADB does recognise the device. Drivers are installed. Any help is welcome!
BermiePT said:
I had a similar experience. I was installing OTA latest update of Vanir...not realising that it was 5.0...a screen came up telling me that it needed to flash another recovery...not realising why it needed that, I ignored the request to flash. Of course, I then "bricked" the phone. I was able to install the original JB 4.12 (v20c) back onto the phone but now it won't root. I've tried almost every method in this forum to no avail.:
ADB just gives a message "error: closing" when I use the boot.exe method
o4xr method does nothing
all-in-one method also does nothing
ADB does recognise the device. Drivers are installed. Any help is welcome!
Click to expand...
Click to collapse
Have you tried to flash a recovery using fastboot? You won't need to root (if you are going to use a custom ROM) and/or it will be easier with a custom recovery
Soft brick after last update.
Hello,
I seem to have a similar problem. I updated a few days ago using Vanir updater. There were no warnings re updating the recovery, just a warning regarding losing root. I checked restore root. The phone rebooted to the bootloader logo, then to a black screen. Now, I can access Cyanogen recovery, SW update mode, abd fastboot mode using buttons and the recovery options. ADB can see the phone only in recovery mode, but not in fastboot or SW update mode. CM recovery has no option to mount USB storage, so my PC cannot see the phone, and I cannot side load a new recovery and flash a new ROM.
Is there any way to use ADB if it cannot see your phone in fastboot or SW mode? Perhaps modify the settings.secure string to enable ADB? ADB can see the phone in recovery mode.
Otherwise I will try flashing a stock ROM via KDZ or LG firmware update tool, the re-root and proceed - but rooting was a major ordeal the first time, so I would like to avoid doing that again.
Thanks in advance.
EDIT : I got rid of the problem and managed to root my phone.
I'm having trouble rooting the K3 note flashed with VIBE UI 3.0. I'm using Lenovo K50a40, Indian Version and I flashed the Dev version of Vibe UI ROM (v 3.0 from hackerpower's signature) . The flashing went all fine. Then I tried to reroot the phone but I noticed that the recovery was the stock one. So I proceeded to reflash the recovery using fastboot but it showed that the file had been downloaded but could not be flashed to the recovery partition. I thought of using SP Flash Tool to flash the recovery. I flashed AthlonX's material TWRP recovery and it flashed okay. Then on rebooting the phone I find it remains stuck on the boot logo with Lenovo written on white backdrop. There's also text written in a small black strip on the bottom left which says "=>Tool DL Image Fail" . The phone stays on that screen for a minute or two and then goes out. Earlier I couldn't boot into the phone due to the above mentioned problem. Then I waited for the battery to drain and then powered the phone on normally (without pressing the button combination for recovery mode) and the phone booted up just fine but the recovery was the stock one .
From all this, there's one thing I've concluded- that this phone has some kind of defense mechanism that protects against installing a custom recovery. This occurred even when I tried rooting on Stock 2.5 VIBE UI. That time I overcame the problem by flashing recovery using fastboot and then booting directly into the recovery instead of system. Now, however, fastboot isn't able to flash the recovery (the transfer of the image is successful but the flashing fails) .
Finally, I request anyone who can help me in any way to Root the phone or to get a recovery installed to please reply.
Thanks.
how were you able to root it
Lord AJ said:
EDIT : I got rid of the problem and managed to root my phone.
I'm having trouble rooting the K3 note flashed with VIBE UI 3.0. I'm using Lenovo K50a40, Indian Version and I flashed the Dev version of Vibe UI ROM (v 3.0 from hackerpower's signature) . The flashing went all fine. Then I tried to reroot the phone but I noticed that the recovery was the stock one. So I proceeded to reflash the recovery using fastboot but it showed that the file had been downloaded but could not be flashed to the recovery partition. I thought of using SP Flash Tool to flash the recovery. I flashed AthlonX's material TWRP recovery and it flashed okay. Then on rebooting the phone I find it remains stuck on the boot logo with Lenovo written on white backdrop. There's also text written in a small black strip on the bottom left which says "=>Tool DL Image Fail" . The phone stays on that screen for a minute or two and then goes out. Earlier I couldn't boot into the phone due to the above mentioned problem. Then I waited for the battery to drain and then powered the phone on normally (without pressing the button combination for recovery mode) and the phone booted up just fine but the recovery was the stock one .
From all this, there's one thing I've concluded- that this phone has some kind of defense mechanism that protects against installing a custom recovery. This occurred even when I tried rooting on Stock 2.5 VIBE UI. That time I overcame the problem by flashing recovery using fastboot and then booting directly into the recovery instead of system. Now, however, fastboot isn't able to flash the recovery (the transfer of the image is successful but the flashing fails) .
Finally, I request anyone who can help me in any way to Root the phone or to get a recovery installed to please reply.
Thanks.
Click to expand...
Click to collapse
i have been using the sp flash tool to download the recovery i want and every time goes back to the stock one
obviously i lost my gapps with the update
but i dont have the google play services issue since i had to re install stock rom and never update google services and just when ahead and applied the updates 2.8 and 3.0,
do you have any ideas
daniiaroxyo said:
i have been using the sp flash tool to download the recovery i want and every time goes back to the stock one
obviously i lost my gapps with the update
but i dont have the google play services issue since i had to re install stock rom and never update google services and just when ahead and applied the updates 2.8 and 3.0,
do you have any ideas
Click to expand...
Click to collapse
If the recovery goes back to stock then you should probably try to boot into the recovery before rebooting to system after SP Flash Tool has done it's job.
Hi so I down loaded one more time the recovery thru sp tool
But this time I took the battery out for few seconds instead of rebooting right away
And it worked
Once I rooted back the phone I tried flashing the gapps but it didn't work
I tried changing the permission s thru root explorer for the google base app as I so on a post and nothing
Any ideas
I followed the steps in this guide attempting to flash a rom. https://forum.xda-developers.com/tm...lopment/rom-stock-debloated-deodexed-t3423387
I was able to flash the BL and modem no problem. I proceeded to flash twrp and have been stuck at boot since. I can only go back into DL mode. Read a few places that said to reinstall rom. How do i go about installing a rom via odin? Any help is greatly appreciated.
jleed88 said:
I followed the steps in this guide attempting to flash a rom. https://forum.xda-developers.com/tm...lopment/rom-stock-debloated-deodexed-t3423387
I was able to flash the BL and modem no problem. I proceeded to flash twrp and have been stuck at boot since. I can only go back into DL mode. Read a few places that said to reinstall rom. How do i go about installing a rom via odin? Any help is greatly appreciated.
Click to expand...
Click to collapse
Okay. Here's what you do...
First, boot to DOWNLOAD MODE. Once in Download Mode, press the keys again like you are booting to Download Mode (VOLUME DOWN + HOME + POWER)
Watch the screen while holding the keys. When the screen goes blank, switch to the key combination for booting RECOVERY (VOLUME UP + HOME + POWER) and hold them until the TWRP screen appears. If the TWRP screen does not appear then we know TWRP didn't stick when you flashed it via Odin.
If the TWRP screen appears, release the keys and let it continue to boot to TWRP.
If TWRP does not boot, then I'd suggest flashing the stock firmware for your device. You can download the stock firmware for your device from www.sammobile.com or from www.updato.com
Sammobile.com is a very slow download unless you pay for a premium account. Updato is much faster. Make sure to select the correct region for your device before downloading the firmware.
Which version of Odin are you using? I've been using 3.12.3 and haven't had any problems at all with this version.
Once you habe downloaded the stock firmware, open Odin. Boot your device to Download Mode and then connect your USB cable. Make sure Odin shows you are connected.
Next, click the OPTIONS TAB in Odin and un-check
AUTO REBOOT. Then, select the AP TAB in Odin and navigate to the firmware file you have downloaded. Let Odin do its thing to verify the file and click START to begin the flash. Once the flash is complete, disconnect the USB Cable and press the key combination for booting to Download Mode again. Once the screen goes black, switch to the key combination for booting RECOVERY. Once in recovery you can select the reboot option to boot your device normally and start fresh from there and attempt to flash TWRP again.
Also, which Note 5 do you have?
fast69mopar said:
Okay. Here's what you do...
First, boot to DOWNLOAD MODE. Once in Download Mode, press the keys again like you are booting to Download Mode (VOLUME DOWN + HOME + POWER)
Watch the screen while holding the keys. When the screen goes blank, switch to the key combination for booting RECOVERY (VOLUME UP + HOME + POWER) and hold them until the TWRP screen appears. If the TWRP screen does not appear then we know TWRP didn't stick when you flashed it via Odin.
If the TWRP screen appears, release the keys and let it continue to boot to TWRP.
If TWRP does not boot, then I'd suggest flashing the stock firmware for your device. You can download the stock firmware for your device from www.sammobile.com or from www.updato.com
Sammobile.com is a very slow download unless you pay for a premium account. Updato is much faster. Make sure to select the correct region for your device before downloading the firmware.
Which version of Odin are you using? I've been using 3.12.3 and haven't had any problems at all with this version.
Once you habe downloaded the stock firmware, open Odin. Boot your device to Download Mode and then connect your USB cable. Make sure Odin shows you are connected.
Next, click the OPTIONS TAB in Odin and un-check
AUTO REBOOT. Then, select the AP TAB in Odin and navigate to the firmware file you have downloaded. Let Odin do its thing to verify the file and click START to begin the flash. Once the flash is complete, disconnect the USB Cable and press the key combination for booting to Download Mode again. Once the screen goes black, switch to the key combination for booting RECOVERY. Once in recovery you can select the reboot option to boot your device normally and start fresh from there and attempt to flash TWRP again.
Also, which Note 5 do you have?
Click to expand...
Click to collapse
Hey, thanks for your response. So I was able to get my System back to working. I had to downoad the stock firmware through sammobile. I ended up paying for the fast download (30days of service) Well ill keep updato in mind if this every happens again. Im on N920TUVU4EQE1 For the n920T since i had already flashed the modem and bootloader before i flashed twrp. I'm on Odin 3.12.3 as well.
"This device uses dm-verity!
This means that swiping to allow system modifications will prevent you from being able to boot if you are using the stock kernel. In order to bypass dm-verity's boot prevention, you will have to install a kernel that has dm-verity disabled in the fstab."
Apparently the kernel i was using wasnt allowing twrp to install. So now i have to figure out how to root my new stock firmware and install recover so i can flash a rom.
jleed88 said:
Hey, thanks for your response. So I was able to get my System back to working. I had to downoad the stock firmware through sammobile. I ended up paying for the fast download (30days of service) Well ill keep updato in mind if this every happens again. Im on N920TUVU4EQE1 For the n920T since i had already flashed the modem and bootloader before i flashed twrp. I'm on Odin 3.12.3 as well.
"This device uses dm-verity!
This means that swiping to allow system modifications will prevent you from being able to boot if you are using the stock kernel. In order to bypass dm-verity's boot prevention, you will have to install a kernel that has dm-verity disabled in the fstab."
Apparently the kernel i was using wasnt allowing twrp to install. So now i have to figure out how to root my new stock firmware and install recover so i can flash a rom.
Click to expand...
Click to collapse
What you have to do is this...
Flash TWRP, swipe to allow system modifications and then flash the no_verity_opt_encrypt_5.1.zip available from
https://build.nethunter.com/android-tools/no-verity-opt-encrypt/
This zip will disable dm-verity and forced encryption in the fstab and allow you to boot normally.
Once this had been done you can flash the root zip of your choice and go to town with debloating, custom ROM's and custom kernels.
jleed88 said:
Hey, thanks for your response. So I was able to get my System back to working. I had to download the stock firmware through sammobile. I ended up paying for the fast download (30days of service) Well ill keep updato in mind if this every happens again. Im on N920TUVU4EQE1 For the n920T since i had already flashed the modem and bootloader before i flashed twrp. I'm on Odin 3.12.3 as well.
"This device uses dm-verity!
This means that swiping to allow system modifications will prevent you from being able to boot if you are using the stock kernel. In order to bypass dm-verity's boot prevention, you will have to install a kernel that has dm-verity disabled in the fstab."
Apparently the kernel i was using wasnt allowing twrp to install. So now i have to figure out how to root my new stock firmware and install recover so i can flash a rom.
Click to expand...
Click to collapse
fast69mopar said:
What you have to do is this...
Flash TWRP, swipe to allow system modifications and then flash the no_verity_opt_encrypt_5.1.zip available from
https://build.nethunter.com/android-tools/no-verity-opt-encrypt/
This zip will disable dm-verity and forced encryption in the fstab and allow you to boot normally.
Once this had been done you can flash the root zip of your choice and go to town with debloating, custom ROM's and custom kernels.
Click to expand...
Click to collapse
When i flashed TWRP i unchecked the Auto-Reboot option. did a key combo to get to twrp but it didnt ask me to swipe to allow system modification. So i went ahead and flashed no_verity_opt_encrypt_5.1.zip with success. Proceeded to flash SuperSU-v2.66 and it got stuck at -Creating paths. I rebooted to recovery and found this guide https://forum.xda-developers.com/galaxy-s6/general/root-s6-nougat-supersu-t3570740
Coming from sickmade 6.0.1 and through all the struggles i am now at stock ROOTED firmware EQG3 andriod 7.0! I just had to take my time and search around a bit. You guys are all amazing. Hopefully if someone has this problem they will find this thread.
jleed88 said:
When i flashed TWRP i unchecked the Auto-Reboot option. did a key combo to get to twrp but it didnt ask me to swipe to allow system modification. So i went ahead and flashed no_verity_opt_encrypt_5.1.zip with success. Proceeded to flash SuperSU-v2.66 and it got stuck at -Creating paths. I rebooted to recovery and found this guide https://forum.xda-developers.com/galaxy-s6/general/root-s6-nougat-supersu-t3570740
Coming from sickmade 6.0.1 and through all the struggles i am now at stock ROOTED firmware EQG3 andriod 7.0! I just had to take my time and search around a bit. You guys are all amazing. Hopefully if someone has this problem they will find this thread.
Click to expand...
Click to collapse
Glad it's working for you. Good job. Now you can make your Note 5 your own. I'm an S6 Edge Plus user. We use the exact same ROM as the Note 5. We just use a different kernel. Happy flashing. If you run into any issues don't hesitate to ask me or anyone else here at XDA. This is a great place to read and learn especially with your Note 5. If a problem has occurred before you can bet that someone has posted about it and you will find a solution.
the phone initially booted up normally. and i power off try to enter recovery mode but i got bootloop , is there any way to get into odin mode , recovery mode is broken ( i flashed recovery with odin it took 15 minutes so i click stop and it crashed ) my phone is sm m20
Hello friends, I've been trying to fix a giant problem with my son's cell phone for three days ... He asked me to rotate it, but I brickee it, I comment on what happens and what I did:
specs:
Glaxy A6 + (SM-A605GN)
1-install TWRP by ODIN (Correct installation)
2-Install TWRP files "force_encryption_disabler, RMM State Bypass and non-verity-opt-encrypt (I think here is my mistake, since I do not know the functions of these files, in my time of Flasheo does not exist) I take it out of this tutorial: androidinfotech.com/root-samsung-galaxy-a6-plus-2018-sm-a605f-fn-gn-pie/[/url])
Error 3-First; I didn't have access to the internal memory in the TWRP, so I followed this tutorial youtube.com/watch?v=bqyVQCGlyqs[/url]) to change the partition system so I could access the internal memory correctly
4- Install the Magisk correctly through the TWRP
5- Restart (And my hell began) ...
a- TWRP informs me that I did not have OS installed on reboot
b- When restarting the screen it tells me: Set guarantee bit: Kernel (in yellow)
c- Try to install the Firmware Stock by Odin, but I can't, it doesn't throw me an error, but it doesn't install anything at all, IT KEEPS ME THE TWRP INTACT
d-Download a Modified ROM, the installation by TWRP and it was installed correctly, but the SIM card does not work (I assume it is because it has a different modem) and I get an error for almost everything L
I want to go back to the Stock ROM but ODIN does nothing ... Please I need your help.
I can access Download and TWRP mode.
discuss the translation ...
Friends, any ideas ?? ... any help is appreciated.
As you already flashed twrp, so i think you know how to go download mode. Just see any youtube video how to flash stock rom on s8/s9. Download your latest firmwere from sammobile or samfrew and flash. Procedure is same as s8 or s9.
tutul2336 said:
As you already flashed twrp, so i think you know how to go download mode. Just see any youtube video how to flash stock rom on s8/s9. Download your latest firmwere from sammobile or samfrew and flash. Procedure is same as s8 or s9.
Click to expand...
Click to collapse
Friend, that's the problem, ODIN doesn't let me install the Stock Rom, at the end of the flash process with Odin, the phone remains intact (with the TWRP intact)
DARKSIDERS_2012 said:
Friend, that's the problem, ODIN doesn't let me install the Stock Rom, at the end of the flash process with Odin, the phone remains intact (with the TWRP intact)
Click to expand...
Click to collapse
What kind of error? or it flashes perfectly? Give us something.. Photo of odin and your phone's download mode screen...
When you first time booted twrp, you needed to click on wipe > format data. This will decrypt your phone (and it wipe your internat storage) then you can flash rmm and no verity. After that, click on reboot > recovery and then reboot > system (or flash magisk). Recommended to flash latest rmm and no verity.
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