Develop Bugs

Bricked G4 h815, bootloader locked after flashing a new ROM

Hello, today i flashed one of the new nougat stock roms. The first boot was fine, everything worked perfectly . But after rebooting I've got the "your device is corrupt. it cannot be trusted and it may not work properly" message, and it wont boot anymore. I cant go into recovery and i cant go into download mode because i get the same the same message and the phone reboots. i can only access the fastboot mode for bootloader unlock, and apparently that my bootloader is now locked. So I've tried to unlock the bootloader again, but it says "Wrong Bootloader Unlock key". Anyone has any idea?

darkstewie92 said:
Hello, today i flashed one of the new nougat stock roms. The first boot was fine, everything worked perfectly . But after rebooting I've got the "your device is corrupt. it cannot be trusted and it may not work properly" message, and it wont boot anymore. I cant go into recovery and i cant go into download mode because i get the same the same message and the phone reboots. i can only access the fastboot mode for bootloader unlock, and apparently that my bootloader is now locked. So I've tried to unlock the bootloader again, but it says "Wrong Bootloader Unlock key". Anyone has any idea?
Click to expand...
Click to collapse
I have the exact same problem and to be honest I think we are f*****. I haven't found any way to re-unlock the bootloader since it seems that the unlock.bin doesn't match with the Device-ID anymore.

This is an IMEI problem. It goes to 0, so the unlock.bin no longer works. I also had this message but my phone was still booting. So I was able to solve the problem.
But you, you can not start your phone, so I do not know how to fix your problem. Sorry

Pif0u said:
This is an IMEI problem. It goes to 0, so the unlock.bin no longer works. I also had this message but my phone was still booting. So I was able to solve the problem.
But you, you can not start your phone, so I do not know how to fix your problem. Sorry
Click to expand...
Click to collapse
No it isn't an IMEI problem, I can reboot my phone and I can access the download mode to flash a KDZ which I did.
EDIT: Oh but I just see in the settings that my IMEI indeed turned into a zero... I do have a TWRP backup of my IMEI.
I quess it's a better idea to make my own G4 Q&A, Help & Troubleshooting thread for help.

I reply in your topic

Pif0u said:
Tutorial to restore imei
1 -Go to phone dial
2- Type *#546368#*815#
3- Go to SVC Menu
4- Go to Port Check Test
5 - Enable Port check test
6 - Download this :
Code:
https://mega.nz/#!cZ9TxBLT!v9qEfeNTeCKYw8XoAhaMOkN48pp4WtLBCU_8KlYeERs
7 - Run the program
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
8 - Click to Qualcomm NV Tools
9 -
10 - Check the box IMEI, Write your IMEI in IMEI(dec) and click to write.
11 - Reboot phone
Click to expand...
Click to collapse
Oh... I just made my own thread, I didn't notice your reply because you didn't quote me... But thanks for this tutorial! I'll give it a try :good:

Pif0u said:
This is an IMEI problem. It goes to 0, so the unlock.bin no longer works. I also had this message but my phone was still booting. So I was able to solve the problem.
But you, you can not start your phone, so I do not know how to fix your problem. Sorry
Click to expand...
Click to collapse
Well, that's sad. This doesn't make any sense . RIP my loevely G4 I guess. Thank you anyway!

darkstewie92 said:
Well, that's sad. This doesn't make any sense . RIP my loevely G4 I guess. Thank you anyway!
Click to expand...
Click to collapse
Hhmm maybe you aren't totally lost, you can access Fastboot mode right, so how have you tried to access the Download mode? You pressed the Volume up button and connected your device with a USB?
It seems you have the same problem as I had, your IMEI turned into a "0", that's why your unlock.bin fails to flash. Just try to access the Download mode for a couple of times, maybe with a but of luck it wil boot into Download mode eventually.

Is there a way to change imei on nougat? Because i cant go in download mode to downgrade to mm

Having the same issue. Cant enter on download or recovery. Fking sht
---------- Post added at 02:30 PM ---------- Previous post was at 02:18 PM ----------
How r u accessing fastboot for bootloader unlock?

Mr.FREE_Bird said:
Hhmm maybe you aren't totally lost, you can access Fastboot mode right, so how have you tried to access the Download mode? You pressed the Volume up button and connected your device with a USB?
It seems you have the same problem as I had, your IMEI turned into a "0", that's why your unlock.bin fails to flash. Just try to access the Download mode for a couple of times, maybe with a but of luck it wil boot into Download mode eventually.
Click to expand...
Click to collapse
I've tried like 20 times already, unfortunately it reboots almost instantly.

We all have the same problem at this point I know that we either hold the smartphone so or we send it to assistance but considering that it is not covered by warranty do not know how long it is

pedrogcsb said:
Having the same issue. Cant enter on download or recovery. Fking sht
---------- Post added at 02:30 PM ---------- Previous post was at 02:18 PM ----------
How r u accessing fastboot for bootloader unlock?
Click to expand...
Click to collapse
press volume down while your phone is turned off, and then plug your usb cable connect to your pc.

darkstewie92 said:
press volume down while your phone is turned off, and then plug your usb cable connect to your pc.
Click to expand...
Click to collapse
Not working for me aswell

Randy_Orton91 said:
We all have the same problem at this point I know that we either hold the smartphone so or we send it to assistance but considering that it is not covered by warranty do not know how long it is
Click to expand...
Click to collapse
I don't even know if they are gonna repair it, and if they do, we will need to pay I guess, I don't how much.

darkstewie92 said:
I don't even know if they are gonna repair it, and if they do, we will need to pay I guess, I don't how much.
Click to expand...
Click to collapse
Use this guide, i solve the problem: https://forum.xda-developers.com/showpost.php?p=73498317&postcount=140

Randy_Orton91 said:
Use this guide, i solve the problem: https://forum.xda-developers.com/showpost.php?p=73498317&postcount=140
Click to expand...
Click to collapse
thank you, but i cant even boot into the ROM. It worked fine the first time,now it doesn't boot anymore.

darkstewie92 said:
thank you, but i cant even boot into the ROM. It worked fine the first time,now it doesn't boot anymore.
Click to expand...
Click to collapse
Same to me

Try this method to live your download mode - https://forum.xda-developers.com/g4/...lcomm-t3452853

You can try a last attempt before you give up if you can not fix it: write an email to [email protected] explains the problem that you've updated to nougat beta and now your bootloader has re-locked and your imei is set on 0 and so the unlock.bin file does not work, try to see if they send you a working one, yesterday I wrote the email and they also answered me asking for more info but I have now solved the problem. Attach the device id and a photo of the back of the phone where the imei is written. Try it

Bricked 5T - locked recovery

Hi im having a hard time figuring this out, this is a brand new 5t that bricked itself while ota updating
the device is in a boot loop (wont go any further than the oneplus logo)
if i enter to the recovery it says LOCKED, and the oem unlock option on android is not enabled
im in argentina so i cant send the phone to oneplus rma
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
is there any way to unlock the bootloader? then i would be able to flash it and save the phone
Ps: a level 2 OnePlus tech guy tried a remote fix with the official brand software and it did not work

https://forum.xda-developers.com/oneplus-5t/how-to/oneplus-5t-unbricking-tool-confirmation-t3733012
Hope that helps. If you can get it to load in that mode, it'll fix about anything.

es0tericcha0s said:
https://forum.xda-developers.com/oneplus-5t/how-to/oneplus-5t-unbricking-tool-confirmation-t3733012
Hope that helps. If you can get it to load in that mode, it'll fix about anything.
Click to expand...
Click to collapse
Thanks a lot! i think that oneplus did use that file and did not work but i will try it again (at least 10 times)

I think it might be tricky to get it into the QHUSB mode unless it's hard bricked. I've fixed a 3t like that but luckily haven't had issues on the 5t yet. I think the only way might be via test point (which would require some hardware work that's not recommended for beginners). Thinking about it now, this might not have been the best solution to provide for your particular issue.
Just thought about this after re-reading your post. When you say that you booted into Recovery and it says locked but you posted a picture of the Fastboot screen showing just that the bootloader is locked - which is to be expected unless you went through the bootloader unlock process.
What happens when you actually boot to recovery? Have you tried factory resetting it there? I imagine the remote desk guy might have tried to adb sideload the update?

This is why I wish we had a fastboot OEM image install option like Google provides.
Maybe we do though and I just haven't found it yet.
Haven't looked very hard.

es0tericcha0s said:
I think it might be tricky to get it into the QHUSB mode unless it's hard bricked. I've fixed a 3t like that but luckily haven't had issues on the 5t yet. I think the only way might be via test point (which would require some hardware work that's not recommended for beginners). Thinking about it now, this might not have been the best solution to provide for your particular issue.
Just thought about this after re-reading your post. When you say that you booted into Recovery and it says locked but you posted a picture of the Fastboot screen showing just that the bootloader is locked - which is to be expected unless you went through the bootloader unlock process.
What happens when you actually boot to recovery? Have you tried factory resetting it there? I imagine the remote desk guy might have tried to adb sideload the update?
Click to expand...
Click to collapse
if i boot to recovery and press the power button to select factory reset or any usefull option, the phone resets, i think that the problem is a corrupt recovery, thats why i want to unlock it, install TWRP and then try to flash android

CZ Eddie said:
This is why I wish we had a fastboot OEM image install option like Google provides.
Maybe we do though and I just haven't found it yet.
Haven't looked very hard.
Click to expand...
Click to collapse
maybe this is an anti thief security measure? (since android 6.0 )

es0tericcha0s said:
I think it might be tricky to get it into the QHUSB mode unless it's hard bricked. I've fixed a 3t like that but luckily haven't had issues on the 5t yet. I think the only way might be via test point (which would require some hardware work that's not recommended for beginners). Thinking about it now, this might not have been the best solution to provide for your particular issue.
Just thought about this after re-reading your post. When you say that you booted into Recovery and it says locked but you posted a picture of the Fastboot screen showing just that the bootloader is locked - which is to be expected unless you went through the bootloader unlock process.
What happens when you actually boot to recovery? Have you tried factory resetting it there? I imagine the remote desk guy might have tried to adb sideload the update?
Click to expand...
Click to collapse
why would i have a problem putting the 5t on qhusb? i did not know that it could be done via testpoint
the phone works, the problem seems to be a faulty file on the bootloader or maybe an internal damage from factory (i hope this is not the case)
in a few hours i will try it all and post the result

Typically a phone will only go into the Qualcomm QHUSB mode when it's hard bricked. You're only soft bricked. What happens when you actually get into Recovery?

es0tericcha0s said:
Typically a phone will only go into the Qualcomm QHUSB mode when it's hard bricked. You're only soft bricked. What happens when you actually get into Recovery?
Click to expand...
Click to collapse
I did the entire process and the result is the same as before doing it, the phone turns on and gets stuck on the oneplus logo, it does nothing else, the recovery works but doesnt do anything usefull

Do you get any errors when performing a factory reset? As in a partition not mounting? Since your baseband doesn't show in the fastboot mode, I'm thinking maybe an /efs error. If you got it new, I'd talk to 1+ about an RMA since this was caused by an official update and one of their technicians already failed to fix it.

es0tericcha0s said:
Do you get any errors when performing a factory reset? As in a partition not mounting? Since your baseband doesn't show in the fastboot mode, I'm thinking maybe an /efs error. If you got it new, I'd talk to 1+ about an RMA since this was caused by an official update and one of their technicians already failed to fix it.
Click to expand...
Click to collapse
It may well be a partition error, one+ is not being helpfull right now
I did comit an error saying that the recovery works, it doesnt work, the pone only goes into fastboot and qhusb mode, after that it will allways get stuck on the oneplus logo
On adb i get feedback if i try to flash the phone says "not allowed, locked device"
I think that the problem is a corrupt bootloader
The msmdownloader tool works, i dont know what It copies on to the terminal but i want to flash the recovery and bootloader using that tool, i dont know if it is possible

this the md5sum file that i found in a compilation for oneplusone (msmdownloader tool)
so i shoud be able to do the same with the 5t

es0tericcha0s said:
Typically a phone will only go into the Qualcomm QHUSB mode when it's hard bricked. You're only soft bricked. What happens when you actually get into Recovery?
Click to expand...
Click to collapse
that is no true, u just have the phone powered off and then hold the volume + and plug the device in, if u saw the video in the unbrick post he was not bricked at all and everything was working good and still did a restore, not sure why it is not working for the OP but it should fix it.

Yes i can enter into qhusb, and i can flash the phone with msm downloader, but i used the origibal file that oneplus technicians use amd it didnt work, now i want to flash hydrogen os or the recovery file only into the terminal but i dont know how to modify the msm downloader (the unbrick tool)

Had the same error message tonight after spontaneous reboot of my (unmodified and locked) device. Fortunately, reimaging with stock ROM from downloads.oneplus.net via adb sideload worked for me, without losing any data. Tried that?

sascha224 said:
Had the same error message tonight after spontaneous reboot of my (unmodified and locked) device. Fortunately, reimaging with stock ROM from downloads.oneplus.net via adb sideload worked for me, without losing any data. Tried that?
Click to expand...
Click to collapse
I remember that the device wouldnt flash anything because it was locked, but I will try the sideload right away

It has been impossible to fix, this is the best i got doing fastboot boot recovery.img

Hard bricked, any help welcome.

So, was thinking to give dp5 a try since I have a OnePlus 6 as a main phone now, and get the pixel with a fresh Android 9 flavour before putting it up for sale.
But, don't know why I thought it's a good idea to lock the bootloader first then get the OTA.
But since I was running nitrogenOS, after locking the bootloader, the phone won't boot, giving the "No valid os to boot" screen.
Stock recovery is inexistent as well, can only boot to fastboot but I've tried to boot/flash with no lock, it tells me it cannot be done on a locked state.
If anyone can help me saving the phone, I'd be really thankful, can even pay for a couple of beers too.
The phone was bought 2nd hand and I can't RMA it. Please let me know if there's anything else I could try to bring it back to life. Thank you everyone.
Sent from my ONEPLUS A6003 using Tapatalk

Blue305 said:
So, was thinking to give dp5 a try since I have a OnePlus 6 as a main phone now, and get the pixel with a fresh Android 9 flavour before putting it up for sale.
But, don't know why I thought it's a good idea to lock the bootloader first then get the OTA.
But since I was running nitrogenOS, after locking the bootloader, the phone won't boot, giving the "No valid os to boot" screen.
Stock recovery is inexistent as well, can only boot to fastboot but I've tried to boot/flash with no lock, it tells me it cannot be done on a locked state.
If anyone can help me saving the phone, I'd be really thankful, can even pay for a couple of beers too.
The phone was bought 2nd hand and I can't RMA it. Please let me know if there's anything else I could try to bring it back to life. Thank you everyone.
Click to expand...
Click to collapse
You should have returned to full stock before locking the bootloader my friend. You should be able to unlock it again, and then fastboot the factory image with the flash-all.bat script to get you up and running.

Badger50 said:
You should have returned to full stock before locking the bootloader my friend. You should be able to unlock it again, and then fastboot the factory image with the flash-all.bat script to get you up and running.
Click to expand...
Click to collapse
Agreed, as long as the OP did not also uncheck the oem switch...
Please, anyone reading this... Do Not RELOCK your boot loader unless you are 100% back to stock. Again, not stock... No RELOCK!!
To the OP, please report back how you make out!

CyberpodS2 said:
Agreed, as long as the OP did not also uncheck the oem switch...
Please, anyone reading this... Do Not RELOCK your boot loader unless you are 100% back to stock. Again, not stock... No RELOCK!!
To the OP, please report back how you make out!
Click to expand...
Click to collapse
Well bruh, if he did uncheck OEM unlocking, it's....
"Turn out the lights the party's over" You are now the proud owner of a fancy paperweight! ?

I didn't messed up with the OEM unlock from developer options, but I can't unlock the bootloader from fastboot unfortunately.. tried the flash.all as well, but I'd doesn't do much , keeps telling me that the phone is in a lock state...
Sent from my ONEPLUS A6003 using Tapatalk

Blue305 said:
I didn't messed up with the OEM unlock from developer options, but I can't unlock the bootloader from fastboot unfortunately.. tried the flash.all as well, but I'd doesn't do much , keeps telling me that the phone is in a lock state...
Click to expand...
Click to collapse
Which command did you use when you locked it?
You may want to look into Deuces recovery script as well to get you out of this pickle.
https://forum.xda-developers.com/pi...ol-deuces-bootloop-recovery-flashing-t3704761

Badger50 said:
Which command did you use when you locked it?
You may want to look into Deuces recovery script as well to get you out of this pickle.
https://forum.xda-developers.com/pi...ol-deuces-bootloop-recovery-flashing-t3704761
Click to expand...
Click to collapse
Thank you, but unfortunately I've ran the script but nothing happened, still cannot get it unlocked or boot to recovery
Sent from my ONEPLUS A6003 using Tapatalk

Blue305 said:
Thank you, but unfortunately I've ran the script but nothing happened, still cannot get it unlocked or boot to recovery
Click to expand...
Click to collapse
Then possibly try different cables and USB ports. Again, which command(s) did you use to lock the bootloader???
Sometimes you have to run Deuces a few times to get it too work.

Badger50 said:
Then possibly try different cables and USB ports. Again, which command(s) did you use to lock the bootloader???
Sometimes you have to run Deuces a few times to get it too work.
Click to expand...
Click to collapse
I'll try different cables then.
I've used fastboot flashing lock, and now is locked, and can't boot to recovery or start os, just boot to bootloader.n
Sent from my ONEPLUS A6003 using Tapatalk

in fastboot, do:
fastboot flashing unlock
then
fastboot flashing unlock_critical

Blue305 said:
So, was thinking to give dp5 a try since I have a OnePlus 6 as a main phone now, and get the pixel with a fresh Android 9 flavour before putting it up for sale.
But, don't know why I thought it's a good idea to lock the bootloader first then get the OTA.
But since I was running nitrogenOS, after locking the bootloader, the phone won't boot, giving the "No valid os to boot" screen.
Stock recovery is inexistent as well, can only boot to fastboot but I've tried to boot/flash with no lock, it tells me it cannot be done on a locked state.
If anyone can help me saving the phone, I'd be really thankful, can even pay for a couple of beers too.
The phone was bought 2nd hand and I can't RMA it. Please let me know if there's anything else I could try to bring it back to life. Thank you everyone.
Click to expand...
Click to collapse
You can give a try for RMA... they sometimes accept RMA for 2nd hand devices as well

ram4ufriends said:
You can give a try for RMA... they sometimes accept RMA for 2nd hand devices as well
Click to expand...
Click to collapse
Thanks, I didnt know that. Is there a specific number I need to call? Thanks again.
Sent from my ONEPLUS A6003 using Tapatalk

uicnren said:
in fastboot, do:
fastboot flashing unlock
then
fastboot flashing unlock_critical
Click to expand...
Click to collapse
I've tried that but it doesnt allow me to do it
Sent from my ONEPLUS A6003 using Tapatalk

Blue305 said:
I've tried that but it doesnt allow me to do it
Sent from my ONEPLUS A6003 using Tapatalk
Click to expand...
Click to collapse
What specifically is the error you receive?
If you want help, you should provide as much detail as possible.
Have you tried recovery and sideloading a full OTA image? I know you said 'stock recovery is inexistent' what does that mean, you get the 'no command' screen with red triangle?

uicnren said:
What specifically is the error you receive?
If you want help, you should provide as much detail as possible.
Have you tried recovery and sideloading a full OTA image? I know you said 'stock recovery is inexistent' what does that mean, you get the 'no command' screen with red triangle?
Click to expand...
Click to collapse
I'm sorry, you're right, I should have been more specific.
The error looks like this:
FAILED (remote: Flashing Unlock is not allowed
)
finished. total time: 0.001s
Also, when I try to boot in the recovery, Nothing happens, the device reboots, Showing me the normal screen "Can't find valid operating system, The device will not start".
I can only get to fastboot, I've tried "adb devices" while in fastboot but nothing is detected.
Thank you for the help so far, if there's anythiing else I could try, please tell me.

This is what it looks like.
View attachment 4562979
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my ONEPLUS A6003 using Tapatalk

Blue305 said:
I'm sorry, you're right, I should have been more specific.
The error looks like this:
FAILED (remote: Flashing Unlock is not allowed
)
finished. total time: 0.001s
Also, when I try to boot in the recovery, Nothing happens, the device reboots, Showing me the normal screen "Can't find valid operating system, The device will not start".
I can only get to fastboot, I've tried "adb devices" while in fastboot but nothing is detected.
Thank you for the help so far, if there's anythiing else I could try, please tell me.
Click to expand...
Click to collapse
adb commands will never work in bootloader.
try: fastboot devices
if the unlocking commands are denied, then it seems like OEM unlocking has defaulted to locked without there being a valid OS and/or no recovery.
if that is the case and you cannot unlock the bootloader, you wont be able to install an OS.
Also how are you trying to get to recovery, I will assume from the hardware buttons while in fastboot?
for fun (not that it should make a difference) try: fastboot reboot recovery
Also out of curiosity, what version of fastboot are you currently using?

uicnren said:
adb commands will never work in bootloader.
try: fastboot devices
if the unlocking commands are denied, then it seems like OEM unlocking has defaulted to locked without there being a valid OS and/or no recovery.
if that is the case and you cannot unlock the bootloader, you wont be able to install an OS.
Also how are you trying to get to recovery, I will assume from the hardware buttons while in fastboot?
for fun (not that it should make a difference) try: fastboot reboot recovery
Click to expand...
Click to collapse
YEs, the unlocking comands are denied.
I used the volume keys to try and get to recovery, but no luck..
That command doesn't work either.
I really don't know what else to do, im quite desperate

Blue305 said:
YEs, the unlocking comands are denied.
I used the volume keys to try and get to recovery, but no luck..
That command doesn't work either.
I really don't know what else to do, im quite desperate
Click to expand...
Click to collapse
Sorry, I added some questions to previous reply, what version of fastboot are you using?
try: fastboot --version

uicnren said:
Sorry, I added some questions to previous reply, what version of fastboot are you using?
try: fastboot --version
Click to expand...
Click to collapse
it's this one:
fastboot version 0.0.1-4500957
Installed as G:\platform-tools\fastboot.exe

G960F/DS not booting system nor recovery

I recently got a used Samsung Galaxy S9 (G960F/DS) with a broken screen (shattered glass and a black spot on the LCD). I was preparing to replace its screen, however, I'm currently not getting the device to boot.
When connected to power, the phone turns on automatically and ends up stuck on the "Samsung Galaxy S9 Secured by Knox Powered by android" screen. When disconnecting power, it turns off after 1-2 seconds.
By pressing power + bixby + volume down, the device enters download mode. When trying to flash stock firmware (BL + AP + CP + CSC) downloaded through Frija (SM-G960F_2_20211021052205_oql3mv17br_fac) the process fails and the phone shows "An error has occured while updating the device software. Use the Emergency recovery function in the Smart Switch PC software". However, I was able to flash the four parts separately by rebooting in between.
This doesn't change anything about the booting problem though. Holding power + bixby + volume up doesn't boot recovery either.
I'd be happy to hear any suggestions. If any more information is required, I'm happy to send you everything I know.

Jogius said:
I recently got a used Samsung Galaxy S9 (G960F/DS) with a broken screen (shattered glass and a black spot on the LCD). I was preparing to replace its screen, however, I'm currently not getting the device to boot.
When connected to power, the phone turns on automatically and ends up stuck on the "Samsung Galaxy S9 Secured by Knox Powered by android" screen. When disconnecting power, it turns off after 1-2 seconds.
By pressing power + bixby + volume down, the device enters download mode. When trying to flash stock firmware (BL + AP + CP + CSC) downloaded through Frija (SM-G960F_2_20211021052205_oql3mv17br_fac) the process fails and the phone shows "An error has occured while updating the device software. Use the Emergency recovery function in the Smart Switch PC software". However, I was able to flash the four parts separately by rebooting in between.
This doesn't change anything about the booting problem though. Holding power + bixby + volume up doesn't boot recovery either.
I'd be happy to hear any suggestions. If any more information is required, I'm happy to send you everything I know.
Click to expand...
Click to collapse
May I'm wrong, but the first impression seems that not only the screen is defective, keep in mind that a device with that broken screen had to receive a severe shock (or various of them), to this can happen, in the incident -of course- other hardware could be damaged.
But taking apart the hardware thing, did you try to format data through stock recovery? Or could you see in the recovery screen (if something is visible) the current build number, so you can flash the right firmware instead of a lower version or the first you found out there?

SubwayChamp said:
May I'm wrong, but the first impression seems that not only the screen is defective, keep in mind that a device with that broken screen had to receive a severe shock (or various of them), to this can happen, in the incident -of course- other hardware could be damaged.
But taking apart the hardware thing, did you try to format data through stock recovery? Or could you see in the recovery screen (if something is visible) the current build number, so you can flash the right firmware instead of a lower version or the first you found out there?
Click to expand...
Click to collapse
I feel like the phone might have another hardware defect, but I'd still like to try my best to fix it.
Unfortunately, the previous owner already tinkered with the device aswell, when I received it, it was not booting stock recovery. However, I only tried flashing the newest update of the firmware - was that the wrong approach? How (and where) can I find a lower version without knowing the exact version details?
Thank you for the input!

Jogius said:
I feel like the phone might have another hardware defect, but I'd still like to try my best to fix it.
Unfortunately, the previous owner already tinkered with the device aswell, when I received it, it was not booting stock recovery. However, I only tried flashing the newest update of the firmware - was that the wrong approach? How (and where) can I find a lower version without knowing the exact version details?
Thank you for the input!
Click to expand...
Click to collapse
Not sure if as the screen is broken you can see something through it, in the recovery screen you'll find the build number version for your device.
Flashing the latest update is always the best bet to not fail. Flashing lower version is not a good idea. You also have to check what is the input in the download screen, if something like KG prenormal warning is there, then you can't flash something in this state.
Also, as the previous owner seems to be not so careful with this device, it is probable that the latest Google account is still there that will trigger the FRP protection.

SubwayChamp said:
Not sure if as the screen is broken you can see something through it, in the recovery screen you'll find the build number version for your device.
Flashing the latest update is always the best bet to not fail. Flashing lower version is not a good idea. You also have to check what is the input in the download screen, if something like KG prenormal warning is there, then you can't flash something in this state.
Also, as the previous owner seems to be not so careful with this device, it is probable that the latest Google account is still there that will trigger the FRP protection.
Click to expand...
Click to collapse
I attached an image of what information download mode has. The second image shows what happens when I try to boot recovery (or anything except download mode for that matter).
You are right that the FRP ist still turned on. Does that mean there is no way to go around this?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Jogius said:
I attached an image of what information download mode has. The second image shows what happens when I try to boot recovery (or anything except download mode for that matter).
You are right that the FRP ist still turned on. Does that mean there is no way to go around this?
View attachment 5478243View attachment 5478245
Click to expand...
Click to collapse
Yes, I suspected that, FRP is active, try to find the guy that sold to you this device, and ask him to log out from his Google account. Also the FRP trigger can be a false positive in the instance that you can enable OEM unlock toggle (what it is not actually enabled), and if Odin allow you to flash something on it and from there you could set it up your device normally.

SubwayChamp said:
Yes, I suspected that, FRP is active, try to find the guy that sold to you this device, and ask him to log out from his Google account. Also the FRP trigger can be a false positive in the instance that you can enable OEM unlock toggle (what it is not actually enabled), and if Odin allow you to flash something on it and from there you could set it up your device normally.
Click to expand...
Click to collapse
I'll try to get in touch with the seller, thank you! However, does FRP change anything about the device not being able to boot at all? Do you have any tips for me how to troubleshoot the fact that not even recovery mode is working?

Jogius said:
I'll try to get in touch with the seller, thank you! However, does FRP change anything about the device not being able to boot at all? Do you have any tips for me how to troubleshoot the fact that not even recovery mode is working?
Click to expand...
Click to collapse
frp still allows you to boot, it just will ask for your google account when setting the phone up

Jogius said:
I'll try to get in touch with the seller, thank you! However, does FRP change anything about the device not being able to boot at all? Do you have any tips for me how to troubleshoot the fact that not even recovery mode is working?
Click to expand...
Click to collapse
FRP works mainly in two ways, when you didn't enable OEM unlock and of course USB debugging then FRP detects an unofficial attempt to inject some custom binary rejecting to boot to system, (What would be the purpose of FRP if you could flash a custom binary, rooting it and then pulling all the data you want?) sometimes this is bypassed by formatting data either booting to recovery (that you say you can't do at this time) or flashing the CSC different from the CSC_HOME, this will wipe/format all your data. And the second instance where FRP can be trigger is when the device was black listed (plus the Samsung account if the last owner didn't log out). The first thing you have to do when buying a Samsung device is logging into the two accounts, then formatting data, and from there you can do what you want.

Flashing firmware while samsung account still present?

Hi, is it possible to flash a new firmware of this device while the samsung account still present on the device?
Can anyone tell me what would happen if i would simply flash a new firmware and root it without logging out the samsung account beforehand?

sarf2k4 said:
Hi, is it possible to flash a new firmware of this device while the samsung account still present on the device?
Can anyone tell me what would happen if i would simply flash a new firmware and root it without logging out the samsung account beforehand?
Click to expand...
Click to collapse
I'm not sure exactly what you're asking. If you dirty flash firmware (no data wipe) and root it, then you'd be updated with root and still have all your credentials on the device.

V0latyle said:
I'm not sure exactly what you're asking. If you dirty flash firmware (no data wipe) and root it, then you'd be updated with root and still have all your credentials on the device.
Click to expand...
Click to collapse
Sorry for not clarifying. What I meant is to simply flash a new firmware with odin while the samsung account still in the phone, as in, if we want to do a factory data reset from the settings interface, we have to key in the password or unbind the device from the account

sarf2k4 said:
Sorry for not clarifying. What I meant is to simply flash a new firmware with odin while the samsung account still in the phone, as in, if we want to do a factory data reset from the settings interface, we have to key in the password or unbind the device from the account
Click to expand...
Click to collapse
Are you asking whether flashing factory firmware will get rid of FRP?
I typically use Odin to flash firmware, and there's two ways to do it. In the firmware package, you have the BL, AP, CP, CSC, and HOME_CSC files. If you want to dirty flash without wiping user data (including a Samsung account), use the HOME_CSC file in the CSC slot. If however you want to force a data wipe, use the CSC file.

V0latyle said:
Are you asking whether flashing factory firmware will get rid of FRP?
I typically use Odin to flash firmware, and there's two ways to do it. In the firmware package, you have the BL, AP, CP, CSC, and HOME_CSC files. If you want to dirty flash without wiping user data (including a Samsung account), use the HOME_CSC file in the CSC slot. If however you want to force a data wipe, use the CSC file.
Click to expand...
Click to collapse
Erm... I don't know what an FRP really is, it has been a while since I last do phone rooting and flashing
I am asking because I saw a warning of odin v3.14.4 with the following message
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

sarf2k4 said:
Erm... I don't know what an FRP really is, it has been a while since I last do phone rooting and flashing
I am asking because I saw a warning of odin v3.14.4 with the following message
View attachment 5812713
Click to expand...
Click to collapse
Did you have a Samsung account on the device already?
FRP = Factory Reset Protection. Requires the Google account login information that was previously on the device before factory reset in order to continue setup; this is an anti-theft measure.
Your bootloader has to be unlocked to use Odin.

V0latyle said:
Did you have a Samsung account on the device already?
FRP = Factory Reset Protection. Requires the Google account login information that was previously on the device before factory reset in order to continue setup; this is an anti-theft measure.
Your bootloader has to be unlocked to use Odin.
Click to expand...
Click to collapse
Yeah, you could say get rid of FRP
It has the account of the previous owner (it was given out). The previous owner kept telling me to bring it to a samsung center to reformat/factory reset it because the previous owner forgot his password
By unlocked, did you mean from the developer menu?

sarf2k4 said:
Yeah, you could say get rid of FRP
It has the account of the previous owner (it was given out). The previous owner kept telling me to bring it to a samsung center to reformat/factory reset it because the previous owner forgot his password
By unlocked, did you mean from the developer menu?
Click to expand...
Click to collapse
That's where you start - you enable OEM Unlocking in Developer Options, then you reboot to download mode and unlock the bootloader.
A clear indication of whether the bootloader is unlocked is the "OEM LOCK" line in download mode; if the bootloader is locked it'll say ON, if unlocked it'll say OFF
Are you able to get into the device at all? Is it locked by a password or pattern? If I were you I'd try to get the previous owner to unlock it; it's their responsibility to remove FRP before they sell the device.

V0latyle said:
That's where you start - you enable OEM Unlocking in Developer Options, then you reboot to download mode and unlock the bootloader.
A clear indication of whether the bootloader is unlocked is the "OEM LOCK" line in download mode; if the bootloader is locked it'll say ON, if unlocked it'll say OFF
Are you able to get into the device at all? Is it locked by a password or pattern? If I were you I'd try to get the previous owner to unlock it; it's their responsibility to remove FRP before they sell the device.
Click to expand...
Click to collapse
I don't know how to get into download mode and unlock the bootloader. From what I've read, I need to turn off the phone, press power/bixby? + volup then plug usb? This is the actual part that I somewhat confused because I already have the required file in order to root, twrp, and ketan's rom. Just the instruction wasn't very clear on what exactly what I must do, more below
Yes I'm able to get into the device, it is just that I can't get rid of the samsung account of the previous owner that enforces the FRP from the settings page because the device asks for the password of the previous owner's account in order to remove it
The flashing/rooting instruction were from http://www.mediafire.com/folder/d4ugie4yadxu6/N975F which is:
Section 2
Instructions for users who are on Stock Q/R/S Non rooted/Other ROMS or running trouble like boootloop
- First install stock latest stock S (A12) firmware (recommended same base if available, base info can be found in changelog post on XDA)
- Download ROM N975F_N976B_DrKetanROM_S*.zip and copy to SD card/USB & Check MD5
- Download & Extract N97*_TWRP_*_tar.md5 + Booloader and Modem according your device variant.
- Flash TWRP file with AP tab of Odin
- Again Reboot to Download mode
- Flash Bootloader and Modem
- Reboot to TWRP(DON't REBOOT TO SYSTEM) - Wipe - Format DATA (Full wipe) This will erase all data from your device
- Reboot TWRP - Flash N975F_N976B_DrKetanROM_S*.zip
- Reboot to System
Read Instrcutiona at end "After rebooting to System"
Click to expand...
Click to collapse
The part where I don't get is, "again reboot to download mode" and "reboot to twrp". I read on other thread, I have to untick "auto-reboot" option in odin?

sarf2k4 said:
I don't know how to get into download mode and unlock the bootloader. From what I've read, I need to turn off the phone, press power/bixby? + volup then plug usb?
Click to expand...
Click to collapse
No, don't press power. Just turn phone off, don't connect USB yet, and hold both Volume buttons while plugging in USB cable. It should start with a prompt for download mode, device unlocking, or cancel. Select device unlocking.
sarf2k4 said:
This is the actual part that I somewhat confused because I already have the required file in order to root, twrp, and ketan's rom.
Click to expand...
Click to collapse
What file? What exactly is your end goal here?
sarf2k4 said:
Just the instruction wasn't very clear on what exactly what I must do, more below
Yes I'm able to get into the device, it is just that I can't get rid of the samsung account of the previous owner that enforces the FRP from the settings page because the device asks for the password of the previous owner's account in order to remove it
Click to expand...
Click to collapse
Hmm. Hopefully a clean flash in Odin will do the trick.
sarf2k4 said:
The flashing/rooting instruction were from http://www.mediafire.com/folder/d4ugie4yadxu6/N975F which is:
The part where I don't get is, "again reboot to download mode" and "reboot to twrp". I read on other thread, I have to untick "auto-reboot" option in odin?
Click to expand...
Click to collapse
Yes. The idea here is that after you flash TWRP, you can't let the device boot into system, because if it does, it'll overwrite TWRP with the stock recovery.
But let's just focus on one step at a time; you first need to unlock the bootloader. Use the key combo I described above, and select whatever option mentions device unlocking. Should be a blue warning screen asking if you want to unlock the bootloader (may have an option for Device Unlock mode). Follow the prompt to unlock the bootloader. Once done report back here and we'll go to the next step.

V0latyle said:
No, don't press power. Just turn phone off, don't connect USB yet, and hold both Volume buttons while plugging in USB cable. It should start with a prompt for download mode, device unlocking, or cancel. Select device unlocking.
What file? What exactly is your end goal here?
Hmm. Hopefully a clean flash in Odin will do the trick.
Yes. The idea here is that after you flash TWRP, you can't let the device boot into system, because if it does, it'll overwrite TWRP with the stock recovery.
But let's just focus on one step at a time; you first need to unlock the bootloader. Use the key combo I described above, and select whatever option mentions device unlocking. Should be a blue warning screen asking if you want to unlock the bootloader (may have an option for Device Unlock mode). Follow the prompt to unlock the bootloader. Once done report back here and we'll go to the next step.
Click to expand...
Click to collapse
I followed your instruction, I wasn't sure connect to which, a charger outlet or pc/laptop. I decided to connect to a laptop anyway while holding both volume buttons. As you described, a cyan warning screen appeared, I proceeded by holding volup and another volup again to proceed with unlocking bootloader. It states that the phone will be wiped during the process.
The phone rebooted twice, first one says there's a yellow triangle that the bootloader has been unlocked, it shows the android with "preparing" message. It then rebooted once again and I pressed the power button to proceed when there yellow triangle appeared on this second boot up.
The phone stuck at SAMSUNG text for like about 5 minutes? I thought it got bricked or something so I detached the usb. After a while the phone booted up like a new phone with the first time setup wizard. I skipped everything.
Going into settings, the account of the previous owner is not there anymore, checking software information shows the latest build of N975FXXS8HVJ1, oneui 4.1, android 12

sarf2k4 said:
I followed your instruction, I wasn't sure connect to which, a charger outlet or pc/laptop. I decided to connect to a laptop anyway while holding both volume buttons. As you described, a cyan warning screen appeared, I proceeded by holding volup and another volup again to proceed with unlocking bootloader. It states that the phone will be wiped during the process.
Click to expand...
Click to collapse
Sorry, I should have been more specific.
sarf2k4 said:
The phone rebooted twice, first one says there's a yellow triangle that the bootloader has been unlocked, it shows the android with "preparing" message. It then rebooted once again and I pressed the power button to proceed when there yellow triangle appeared on this second boot up.
The phone stuck at SAMSUNG text for like about 5 minutes? I thought it got bricked or something so I detached the usb. After a while the phone booted up like a new phone with the first time setup wizard. I skipped everything.
Going into settings, the account of the previous owner is not there anymore, checking software information shows the latest build of N975FXXS8HVJ1, oneui 4.1, android 12
Click to expand...
Click to collapse
Alright, success. So what is your end goal here? Are you trying to install a custom ROM? Let me know what you're ultimately trying to accomplish so I can help you with the next steps.

V0latyle said:
Sorry, I should have been more specific.
Alright, success. So what is your end goal here? Are you trying to install a custom ROM? Let me know what you're ultimately trying to accomplish so I can help you with the next steps.
Click to expand...
Click to collapse
Thank you for the help.
I actually came from samsung galaxy note 1, gt-n7000, hard bricked accidentally 2 years ago because of the brickbug present if I'm not careful, but it got me. So I am using a vivo phone for almost a year, for which I can't even flash any firmware let alone running adb commands to grant permission on the phone. It is running android one and it has full locked down in my opinion.
I actually missed the viper4android that I tweaked on my note 1 for a very good sound quality I achieved back then although viper4android wasn't the only reason I wanted to root it. I would like to have adaway at least as well. Perhaps some other 'extra' features that stock can't offer.
I'm not sure how do I put it during the use of this device while still in the previous owner's account is that, when I launched netflix or youtube (respecting the privacy of course), the phone screen became brighter than I would like. Even if it is slightly dimmed, launching one of these app would make it brighter, then go back down to previous brightness when exiting them.
There's already a screen burn-in from excessive youtubing from the previous owner and I can see why, 3 years later this phone has burn-in already because of the app's behavior of 'boosting' the brightness. Not sure if some of the rooted modules 'can' prevent these brightness adjustments by the app or not.
I also never used any banking/financial app on any of my mobile devices
edit:
I often go for stock rom most of the time.
Coming from note 1 that has the potential brick bug during that era especially exynos variants, this note 10+ don't have any potential brick bug do they?
I also tried to restart the phone, I still get that yellow triangle warning saying bootloader has been unlocked and can't be verified, would like to get rid of that as well. Furthermore, I checked the developer menu, "oem unlocking" is now missing

You didn't answer my question, bud. What are you trying to do? What is your goal? For example, are you trying to get a custom ROM installed? Or were you just trying to get the Samsung account removed?

V0latyle said:
You didn't answer my question, bud. What are you trying to do? What is your goal? For example, are you trying to get a custom ROM installed? Or were you just trying to get the Samsung account removed?
Click to expand...
Click to collapse
Sorry if I veered off, yes I would like to have custom rom installed which is to have root in mind. I'm eyeing for drketan's mostly stock rom