Hi,
I'm stuck on 'samsung' logo screen after flashing stock rom. Please see details below if you can assist.
1. I have sm-505fn from carphone warehouse uk with jan/feb 2020 update..
2. I did oem unlock and flashed twrp
3. this gave bootloader warnings, but eventually went into twrp.
4. I didn't do the dm verify installation and after couldn't get into twrp again. (not sure how to sideload this at this stage)
because i didn't do above step and rebooted, i think i tripped the knox and SG/RMM state became 'prenormal'.
kept getting error: "Only official released binaries are allowed to be flashed" if i tried installing twrp again.
5. tried installing stock rom btu for march 2019, but odin gave errors as couldn't install older stock.
6. then installed feb 2020 stock from sammobile rom A505FNXXS4ATB1 which is the btu version.
7. above worked fine with odin and everything succeeded.
8. On reboot the first warning vanished, and I only got the 2nd bootloader warning. phone went through a 5 second update screen, then rebooted.
9. then got samsung a50 logo and system started booting with plain samsung logo.
10. been stuck at plain samsung logo for 40 min. tried restarting but same problem.
Can you please advise what i should do?
Can't believe its such a headache to install twrp this device (and then later remove the bl warnings
Thanks
ok, I got stock reinstalled and it worked in the end.
the bootloader was unlocked, and developer option to unlock was greyed out.
as it still gave the bootlocker warning, i turned oem lock on again via long press up on download mode. this fixed all warnings and i can boot now without warnings.
when i go into developer mode now, there is no option to oem unlock again.
if i go into download mode, there is no option to long press up and unlock again
on download mode it says:
KG State: prenormal
OEM Lock: ON (U1)
how can I turn oem lock off again, so I can try to install twrp?
Please assist.
thanks
SOLVED -
managed to turn oem unlock option again by turning off auto time update and setting clock back 10 days.
then on restart, the option appeared again and was set to oem unlock ticked.
went into download mode and i could see option again to unlock booloader.
long pressed up and it unlocked bootloader, erased data and restarted to system....
now... lets try to install twrp again and hope it doesn't give me 'unofficial binary' error due to SG prenormal state.
lol.. its KG STATE not SG fyi
Typo
lawmanukdc said:
Typo
Click to expand...
Click to collapse
lol id believe that in 1 comment but everywhere? oh well no biggie lol.. hope ur enjoyin ur phone now
How did you succeed to get the stock reinstalled ? Was it different version ?
lawmanukdc said:
ok, I got stock reinstalled and it worked in the end.
the bootloader was unlocked, and developer option to unlock was greyed out.
Click to expand...
Click to collapse
Related
So guys, bought this phone used 3 days ago. The phone was rooted and the fingerprint scanner was not working giving some error. So I decided to get the phone returned back to stock.
I flashed the G925TUVU3DOJ7_G925TTMB3DOJ7_G925TUVU3DOJ7_HOME.tar file via odin 3.10.6. All files were successfully flashed with pass message but now i am stuck on the boot screen at s6 edge logo. I did a factory reset and wiped the cache but no luck.
The recovery shows an error of dm-verity verification failed... as well in the bottom. I can get the phone in download mode. The current binary is samsung official but in system status it still says Custom. I tried flashing G925TUVU2COF6_G925TTMB2COF6_G925TUVU2COF6_HOME.tar but it doesn't let me flash it as I read i cannot downgrade.
I have tried searching at different places but couldn't seem to find any appropriate solution as most of them are for cof6 or cof8 firmware. I would appreciate a lot if someone could guide me step-by-step procedure to get my phone working back.
Note: I think that the phone IMEI was also repaired as the IMEI on back glass and in the system does not match.
I also cannot get any assistance from t-mobile as I live in Pakistan. I could not attach shots as i have less than 10 posts so writing the status:
In download mode:
PRODUCT NAME: SM-G925T
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Custom
FRP LOCK: OFF
Secure Download: Enabled
KNOX WARRANTY VOID: 1 (0x0301)
AP SWREV: B:3 K:2 S:2
Recovery error at the bottom:
dm-verity verification failed. . .
Need to check DRK first. . .
It sounds like there may be an issue with your IMEI. I think you should try and use Smart Switch on your PC to do an emergency recovery. It will completely wipe the phone and reset everything to how it should be.
Emergency recovery requires the serial number in order to proceed. You can get that by going into Download mode but before you hit Vol Up to continue hit Home instead. It will show IMEI and Serial Number (the bottom number).
Samsung Smart Switch for PC can be downloaded from Here. Install Smart Switch. Start up Smart Switch and click more in upper right corner. If you don't have the Samsung drivers installed you can install them from here. Or if you would like to reinstall them.
After you are done with drivers connect your phone to the PC and click more and click "Emergency software recovery and initialization" (the first option). It should ask for your serial number. enter it and it should start doing it's thing.
Hopefully this works for you and good luck.
Thanks for the fast reply. I flashed it using the smart switch software. The program completed successfully but still the same result. Stuck at boot logo and same dm-verity error in recovery
DM Verity Verification failed
muhsaad said:
Thanks for the fast reply. I flashed it using the smart switch software. The program completed successfully but still the same result. Stuck at boot logo and same dm-verity error in recovery
Click to expand...
Click to collapse
Hello , if you still facing this issue after flash full stock
try to write unikernel v8-002 (remember FRP LOCK = OFF )
It must work ,
i am sure after flash Unikernel is will work
post result if not work
Thanks alot @jayshaa. Finally booted up... Hats off to you man...!! :good:
Sorry to disturb again... Today when I restart the phone, I couldn't pass the boot screen as I gave me the error Custom Binary blocked by FRP Lock. Frp lock turned on automatically and now I am again stuck at the boot screen. I again flashed the stock rom but the frp lock is still on. I couldn't flash the kernal as well because of this lock.
Someone please guide me to turn this frp lock off and get my phone working again.
Need to check DRK first. .
This error means at some point your efs probably was wiped meaning the drk was wiped... unless this is fixed the phone will boot loop everytime you update unless you flash a modified kernel...
So how do I fix that or turn frp lock off?
Anyone???
muhsaad said:
Sorry to disturb again... Today when I restart the phone, I couldn't pass the boot screen as I gave me the error Custom Binary blocked by FRP Lock. Frp lock turned on automatically and now I am again stuck at the boot screen. I again flashed the stock rom but the frp lock is still on. I couldn't flash the kernal as well because of this lock.
Someone please guide me to turn this frp lock off and get my phone working again.
Click to expand...
Click to collapse
That can only be turned off via Developer Options in Settings. If you flashed a custom kernel then you cannot turn it off because you will boot loop. You must flash stock kernel. Or just reflash the stock firmware package.
After you get back to stock. get to developer options and turn off the FRP lock. Then you can flash away.
HELP. (SOLVED)
Hi Guys, yesterday I have tried to lock my bootloader again on android 9, after not successfully security patch update, after I lock my bootloader the phone has erased all system, , I have downloaded the factory image from google site but every stock image I flash I get stuck in the google white screen, I can’t update by sideloading, because when I lock the bootloader all system gone.. I CAN ACCESS THE FASTBOOT MODE AND RECOVERY MODE phone stuck on boot screen with google logo help….. I have tried many stock images but same problem with all versions..
Also get he messege "Your device is corrupt. It can't be trusted and may not work properly.
Visit this link on another device: g.co./ABH
PRESS POWER BUTTON TO CONTINUE".
PLS HELP..
zetareticuli said:
HELP.
Hi Guys, yesterday I have tried to lock my bootloader again on android 9, after not successfully security patch update, after I lock my bootloader the phone has erased all system, , I have downloaded the factory image from google site but every stock image I flash I get stuck in the google white screen, I can’t update by sideloading, because when I lock the bootloader all system gone.. I CAN ACCESS THE FASTBOOT MODE AND RECOVERY MODE phone stuck on boot screen with google logo help….. I have tried many stock images but same problem with all versions..
Also get he messege "Your device is corrupt. It can't be trusted and may not work properly.
Visit this link on another device: g.co./ABH
PRESS POWER BUTTON TO CONTINUE".
PLS HELP..
Click to expand...
Click to collapse
You probably should look into this.
https://forum.xda-developers.com/pi...ol-deuces-bootloop-recovery-flashing-t3704761
With a locked bootloader, you cannot flash system images. You need to be unlocked to do so.
But it seems that you did something wrong when re-locking the bootloader: It is normal that a factory reset is performed, but the OS should stay on the phone.
So I would first unlock the bootloader again - both fastboot flashing unlock and fastboot flashing unlock_critical, like described here: https://developers.google.com/android/images
Also note that you always need to update the Android SDK Platform-Tools, like descibed in the link. As always: Those who can read do have an advantage
Then you should be able to flash the latest factory image again and are ready to go.
Badger50 said:
You probably should look into this.
https://forum.xda-developers.com/pi...ol-deuces-bootloop-recovery-flashing-t3704761
Click to expand...
Click to collapse
I couldn't dig myself out of a soft brick the other day too. That saved me as well. Worked like a charm the first time.
zetareticuli said:
HELP.
Hi Guys, yesterday I have tried to lock my bootloader again on android 9, after not successfully security patch update, after I lock my bootloader the phone has erased all system, , I have downloaded the factory image from google site but every stock image I flash I get stuck in the google white screen, I can’t update by sideloading, because when I lock the bootloader all system gone.. I CAN ACCESS THE FASTBOOT MODE AND RECOVERY MODE phone stuck on boot screen with google logo help….. I have tried many stock images but same problem with all versions..
Also get he messege "Your device is corrupt. It can't be trusted and may not work properly.
Visit this link on another device: g.co./ABH
PRESS POWER BUTTON TO CONTINUE".
PLS HELP..
Click to expand...
Click to collapse
Sounds like you may have made some changes to your partitions, then locked the bootloader.
I would unlock the bootloader again, and reflash all the partitions to factory.
Then lock bootloader again.
exist2resist said:
Sounds like you may have made some changes to your partitions, then locked the bootloader.
I would unlock the bootloader again, and reflash all the partitions to factory.
Then lock bootloader again.
Click to expand...
Click to collapse
SOLVED WITH [TOOL] Deuces Bootloop-Recovery & Flashing Script v4.4/v4.5
Thanks alot guys
mikelikesbikes said:
I couldn't dig myself out of a soft brick the other day too. That saved me as well. Worked like a charm the first time.
Click to expand...
Click to collapse
Thanks my friend works like a charm..
exist2resist said:
Sounds like you may have made some changes to your partitions, then locked the bootloader.
I would unlock the bootloader again, and reflash all the partitions to factory.
Then lock bootloader again.
Click to expand...
Click to collapse
Solved with [TOOL] Deuces Bootloop-Recovery & Flashing Script v4.4/v4.5..
Hello
I was on an android 9.0 GSI image.
After disabling developer options in settings the device couldn't boot.
It was showing "custom firmware blocked by FRP lock" error.
I couldn't enter TWRP recovery as well. So I restored stock firmware through odin.
I tried to toggle on OEM unlock in settings with no result, after reboot it remains OEM and FRP locked. I also tried to OEM unlock through combination firmware but the toggle doesn't work.
Does anyone know if there is a solution to this problem ?
Thanks in advance,
NoirX said:
Hello
I was on an android 9.0 GSI image.
After disabling developer options in settings the device couldn't boot.
It was showing "custom firmware blocked by FRP lock" error.
I couldn't enter TWRP recovery as well. So I restored stock firmware through odin.
I tried to toggle on OEM unlock in settings with no result, after reboot it remains OEM and FRP locked. I also tried to OEM unlock through combination firmware but the toggle doesn't work.
Does anyone know if there is a solution to this problem ?
Thanks in advance,
Click to expand...
Click to collapse
Probably going to have to wait 7 days
*Detection* said:
Probably going to have to wait 7 days
Click to expand...
Click to collapse
I tried that too but i think the issue is a little bit more complicated. The toggle is there but it does nothing. On stock firmware it goes through a factory reset as expected but the device remains oem locked. On combination firmware the toggle is there too, but it won't switch on. Thank you.
I have a similar issue....
Waited a full week for the OEM Unlock.
Ticked it last night.
Rebooted to download mode > Flashed TWRP > Passed.
Rebooted to TWRP, it showed up, then it presented a bunch of red code errors before quickly resetting and defaulting back to normal Recovery again..... WTF
Looks like ill have to wait another 7 days because in Download mode it now says OEM Mode is Unlocked but its still RMM State: PreNormal mode on... no OEM Unlock setting in my Developer settings.
Anyone else had an issue with TWRP randomly throwing up errors upon first boot and then restarting before you can do anything???
I used the Patched ODIN here: https://forum.xda-developers.com/android/software/patched-odin-3-13-1-t3762572
Combined with TWRP 3.2.3-0 recovery....
AMDPOWERFIST said:
I have a similar issue....
Waited a full week for the OEM Unlock.
Ticked it last night.
Rebooted to download mode > Flashed TWRP > Passed.
Rebooted to TWRP, it showed up, then it presented a bunch of red code errors before quickly resetting and defaulting back to normal Recovery again..... WTF
Looks like ill have to wait another 7 days because in Download mode it now says OEM Mode is Unlocked but its still RMM State: PreNormal mode on... no OEM Unlock setting in my Developer settings.
Anyone else had an issue with TWRP randomly throwing up errors upon first boot and then restarting before you can do anything???
I used the Patched ODIN here: https://forum.xda-developers.com/android/software/patched-odin-3-13-1-t3762572
Combined with TWRP 3.2.3-0 recovery....
Click to expand...
Click to collapse
Why are you using a patched ODIN?
Uncheck "Auto Reboot" in ODIN settings, once TWRP has flashed disconnect USB then power off the phone and immediately boot into recovery, do not let it reboot first
*Detection* said:
Why are you using a patched ODIN?
Uncheck "Auto Reboot" in ODIN settings, once TWRP has flashed disconnect USB then power off the phone and immediately boot into recovery, do not let it reboot first
Click to expand...
Click to collapse
I'll try with normal Odin next time. I do suspect this might have been the issue.
AMDPOWERFIST said:
I have a similar issue....
Waited a full week for the OEM Unlock.
Ticked it last night.
Rebooted to download mode > Flashed TWRP > Passed.
Rebooted to TWRP, it showed up, then it presented a bunch of red code errors before quickly resetting and defaulting back to normal Recovery again..... WTF
Looks like ill have to wait another 7 days because in Download mode it now says OEM Mode is Unlocked but its still RMM State: PreNormal mode on... no OEM Unlock setting in my Developer settings.
Anyone else had an issue with TWRP randomly throwing up errors upon first boot and then restarting before you can do anything???
I used the Patched ODIN here: https://forum.xda-developers.com/android/software/patched-odin-3-13-1-t3762572
Combined with TWRP 3.2.3-0 recovery....
Click to expand...
Click to collapse
@*Detection*, I had the exact same issue as yours tonight when I tried to install TWRP for the first time. Red code errors then an automatic restart and then default back to normal Recovery. As far as I know I used normal Odin and I followed installation instructions to the letter. So back to square one for me. I'll definitely have another crack in 7 days. Interested to know how you went with your second effort. If you had success please post what you did step by step.
And @AMDPOWERFIST, out of interest, how do you power the phone OFF from the Download screen? I know how to restart. Thanks.
bulky68 said:
@*Detection*, I had the exact same issue as yours tonight when I tried to install TWRP for the first time. Red code errors then an automatic restart and then default back to normal Recovery. As far as I know I used normal Odin and I followed installation instructions to the letter. So back to square one for me. I'll definitely have another crack in 7 days. Interested to know how you went with your second effort. If you had success please post what you did step by step.
And @AMDPOWERFIST, out of interest, how do you power the phone OFF from the Download screen? I know how to restart. Thanks.
Click to expand...
Click to collapse
Just realised that I got the 2 posters mixed up in my previous post. My apologies @*Detection* and @AMDPOWERFIST.
hello, i was hoping to get some help with my device not being rootable.
i followed these two guides word for word i cant post links because im new here but i followed the naldotech twrp + root s9 guide and the highonandroid s9 root guide.
tried both reinstalled OS with csc and home-csc twice for each one when my phone was stuck in a loop so i can make sure that its back to factory before i try another method. my phone it either gets stuck at samsung logo or just reboots to recovery never goes to samsung logo my oem unlock button always stays off even though i follow the steps and it says under it that bootloader already unlocked and it never goes blue and oem lock: off in download mode, i did not setup my samsung or google accounts in any of those resets that way no settings get synced.
i really need the help i have been trying this for the past month and a half and i have tried everything i could think off and nothing is working.
current software installed: G960FXXU2CRLI_G960FOXM2CRLI_XSG
Model: SM-G960F/DS
OS: 9.0.0
chriskay525 said:
hello, i was hoping to get some help with my device not being rootable.
i followed these two guides word for word i cant post links because im new here but i followed the naldotech twrp + root s9 guide and the highonandroid s9 root guide.
tried both reinstalled OS with csc and home-csc twice for each one when my phone was stuck in a loop so i can make sure that its back to factory before i try another method. my phone it either gets stuck at samsung logo or just reboots to recovery never goes to samsung logo my oem unlock button always stays off even though i follow the steps and it says under it that bootloader already unlocked and it never goes blue and oem lock: off in download mode, i did not setup my samsung or google accounts in any of those resets that way no settings get synced.
i really need the help i have been trying this for the past month and a half and i have tried everything i could think off and nothing is working.
current software installed: G960FXXU2CRLI_G960FOXM2CRLI_XSG
Model: SM-G960F/DS
OS: 9.0.0
Click to expand...
Click to collapse
Did u fix it ? Cos I have similar issue but on my phone it says the bootloader is locked and the OEM unlock option never turns on , when I turn it on it does factory reset and reboot the device but the option stays off
Akhayev said:
Did u fix it ? Cos I have similar issue but on my phone it says the bootloader is locked and the OEM unlock option never turns on , when I turn it on it does factory reset and reboot the device but the option stays off
Click to expand...
Click to collapse
no fix yet and same thing is happening to me the OEM options always stays off and that's even after a clean firmware install i really hope we can find a way to fix this
chriskay525 said:
no fix yet and same thing is happening to me the OEM options always stays off and that's even after a clean firmware install i really hope we can find a way to fix this
Click to expand...
Click to collapse
Did u wait for 7 days ?
So , I just tried to flash TWRP on a SM-G960F/DS via Odin v3.13.3 and I got the error from the title in the Download Mode. The phone works 100% but I really wanna get another UI . I forgot to mention I already unlocked the OEM from dev mode.
EDIT In a way or another the ODIN said PASS but after flashing the TWRP and trying to boot into recovery I was shocked to see the stock Recovery , just why?
Maybe you have Prenormal status. You'll have to wait few days without turning off your phone and then you'll be able to flash twrp.
ZoiraP said:
Maybe you have Prenormal status. You'll have to wait few days without turning off your phone and then you'll be able to flash twrp.
Click to expand...
Click to collapse
the prenormal is likely correct, unsure if the waiting 168 hours is still a thing or not tho.