Develop Bugs

Error when install new rom....

Hello....
I am using SPL 1.20.Olipro and the rom is 20070519_LVSW_Trinity_WM6_v2.0.0.7
When I want to update new rom....Its doesn't work....
Whenever which rom (mUn's version or LVSW's rom)
Pic 1 is the error message
Pic 2 is my phone turned to this screen
{
"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"
}
Can someone can teach me how to fix this problem!!????
THANKS so much!!
My English is poor...Sorry

hi,when you have this error message you must try again and the Rom update works. I've already had this problem
salut,quand tu as un message d'erreur relance immédiatemment ta rom update et ça doit passer. J'ai déjà eu ce souci

New error........

when the phone come to bootloader screen restart update utility, if don't work use hardspl....

hi,
have you unlock CID?

same here
Hi,
I got the same problem, exactly the same error when i want to flash lvsw rom.
1. I superCID it (twice)
2. I updated using hard-SPL but everytime i get the same error code: 246 device not responding.
I tried reconnecting, resetting, with and without sim, but it all doesn't seem to work.
When I downloaded a shipped rom with GPS enabled, all went well...
Is there some kind of trick involved, or does it just not work for my p3600?
Thanx in advance,
Geert
--------------------------------------------------------------------------------------
@ kayzee
if you start hard-SPL and it opens the hard-SPL window, before you click next etc. open up lvsw rom updater and click next etc. in the lvsw updater.
I guess your Trinity thinks its hard-SPL but in fact ur flashing lvsw rom on ur Trinity

edit: please delete this message

Supergeert said:
Hi,
I got the same problem, exactly the same error when i want to flash lvsw rom.
1. I superCID it (twice)
2. I updated using hard-SPL but everytime i get the same error code: 246 device not responding.
I tried reconnecting, resetting, with and without sim, but it all doesn't seem to work.
When I downloaded a shipped rom with GPS enabled, all went well...
Is there some kind of trick involved, or does it just not work for my p3600?
Thanx in advance,
Geert
--------------------------------------------------------------------------------------
@ kayzee
if you start hard-SPL and it opens the hard-SPL window, before you click next etc. open up lvsw rom updater and click next etc. in the lvsw updater.
I guess your Trinity thinks its hard-SPL but in fact ur flashing lvsw rom on ur Trinity
Click to expand...
Click to collapse
same problem same procedure:;
when the first flash fail click exit and (w/o do anything) restart ruUpdate.exe or before do the update push and hold camera button and do a soft reset (holding camera button) when the phon is in "3 colors mode" start the update

The way it worked for me was to flash it while it was up and running as the software send's you into bootloader mode and then let's you flash ok. This way works for me.

I have problem!
After rom upgrade for cid unlock, the process stoped at 80% then phone now is freeze!
When i try to start up it it freeze on sfr logos! I've tried several times to repeat process rom upgrade for cid unlock but soft start qo at 7% an phone restart and same thing with original rom or sfr rom. Nothing to do it's died!
Please help me

have you tried to flash hard spl to your phone first? then try to flash another rom.
if not, follow the instructions here to use splxploit, then flash hard spl, then another rom

That didn't work for me. Does anyone know what to do yet?

Hi,
I have the same problem.
I have followed the indication of this forum:
http://forum.xda-developers.com/showthread.php?t=293957
1. Transfer SSPL/SSPL-TRIN.exe to your phone and run it
2. Tri-color screen will appear
3. Disable activesync (file -> connection settings -> uncheck "allow USB connections")
4. Connect your phone to your computer using the USB lead.
5. Run RUU/ROMUpgradeUtility.exe
6. Follow the flashing process (Check the "I understand..." and "I completed..." boxes and update!)
7. Allow your phone to reboot.
8. Transfer TRIN_Unlock_v1.exe program to your phone and run it
9. Click the Unlock Button, select unlock option. Select if you want SIM/CID unlock.
10. Click "Unlock!" and wait until process finishes.
11. When done, turn off your phone for 10 seconds and reboot after that.
I hope of to have been useful, I have resolved therefore
d.

Sorry for bothering you,
I had a problem while flashing a Rom. Now my trinity is dead. It only appears the "HTC smart mobility", symbol with some red little numbers at the bottom of the page.
Is there something I still can do my self or should I run to service assistance?
Obviously it doesn't connect to active sync.
Please just give me a hint....

Download the official locked ROM
Put the trin in bootloader mode manually... Flash... now the phone is locked again... supercid it again... then try again with hard spl

samov said:
Download the official locked ROM
Click to expand...
Click to collapse
I've already downloaded the official WM5.
samov said:
Put the trin in bootloader mode manually...
Click to expand...
Click to collapse
Please, I don't know how to do this operation. My PDA looks dead.
samov said:
Flash... now the phone is locked again...
Click to expand...
Click to collapse
Ok, I think I know how to do this
.
samov said:
supercid it again...
Click to expand...
Click to collapse
Supercid? Sorry, what does it mean?
samov said:
then try again with hard spl
Click to expand...
Click to collapse
Please could you tell me how to do this?
Probably not very used to this operations, so please try to explain in a more explicit way.
Thank you so much for your kind assistance.

you really should read more before you try to flash..
the wiki defines all of these terms that you aren't understanding.
manually place in bootloader by holding power button + camera button + soft reset.
You can download hard-spl(makes phone look like CID unlocked, does not void warranty and allows you to flash unsigned ROMs) in Trinity Upgrading forum, and also SuperCID tool (unlocks your phone to use ROMs from any carrier, but voids warranty). SuperCID is unnecessary in my opinion
please follow the upgrade guides on my site if you're confused. For now, Place your device in bootloader, and flash hard-spl, then the ROM of your choice. Follow the hard-spl guide on my site for details and download links.
hope it helps

racerx_ said:
you really should read more before you try to flash..
Click to expand...
Click to collapse
You're right. Now I know.
racerx_ said:
manually place in bootloader by holding power button + camera button + soft reset.
Click to expand...
Click to collapse
Done.
racerx_ said:
You can download hard-spl(makes phone look like CID unlocked, does not void warranty and allows you to flash unsigned ROMs)
Click to expand...
Click to collapse
Done. I've downloaded the DES Crash Proof Spl.
racerx_ said:
please follow the upgrade guides on my site if you're confused.
Click to expand...
Click to collapse
I've followed the instructions here
http://trinityguides.info/index.php?option=com_content&task=view&id=39&Itemid=66
But I still have a doubt. Because it says "Make sure the activesync icon is be green (finished synchronizing)" . But as I've already said, it seems that my pda doesn't connect at all.
Please, help me. probably I'm close to the solution. Sorry for bothering you!

Anyway I've tried the following:
Downloaded the DES CRASH PROOF SPL.
Connected my Trinity to my pc.
The active sync doesn't extablish a connection. No green light.
Put the PDA in bootloader mode manually
run the spl
After a few clicks, the program on the pc says: ERROR [270] The image file is corrupted. Please check your update utility.

I tried to flash the official WM5 and now it's ok. It works fine with it. Can I try again to flash the unofficial WM6 rom from the forum now?
thanx !

screen not working, cannot boot! any ideas?

anyone knows how suddenly the screen doesn't respond anymore?
I cannot even boot into windows, it needs the calibration, cannot even switch it off because i need to tap "yes"!!!
Any ideas? It is brand new and i have tried several roms but cannot go beyond the boot green screen.
Thank you.

If you get to the align screen when you do the align screen it just restarts the align screen process over again right ?.....if thats the case i had the same problem i sent it in to htc and it was covered by the warranty

is that right - you try flashing one rom, after flashing get not rospense.
than you try an other rom but same equal.
is that correct?
but you can long press with dialog yes/no.
for "clicking" yes press only action-button
(the big round thing in middle)

Can you access the device from windows (see it as a removable drive?)
If so, you can create a "welcome.not" file from your pc and copy it to the internal storage. This will make it bypass the "align screen" steps when you boot up.
The file just needs to be an empty file. Create a "New Text Document" on your desktop, rename it to "welcome.not" and place it in the root of your internal storage (if you can access it).
Haven't tried this on my Diamond, only ever on devices with an external microSD, so I'm not entirely sure that it will work. It worked for me when my TyTn II screen broke. Once it's done, you can use a program like SOTI Pocket Controller to navigate around the device more freely from your PC.
This is good for diagnosis of problems, and enabling you to flash back to stock ROM and SPL for use of your warranty etc. but I'm afraid it seems inevitable that you'll eventually need to replace the screen, which hopefully you'll be able to use you warranty for.

no, actually, i don't get to the alignement screen, i'm stuck to the "tap the screen to start using....bla bla. And cannot go further cause the screen dosen't respond. not even to shut off. Completely no response to the taps.

thank you i will try it but any idea where to get the original uspl? It is a device from france, i've got the original rom from htc site with the serial number but i still need to get it to the original uspl right? now it has the unsigned olinex, no good for a warranty, right?
and anyway the guy who sold it to me he's overseas for probably a year so...bad luck for me.

AFAIK, you need to know what the SPL was before you flashed Olinex's. I doubt there is a way to find out what it was, unless you know someone near you who had the same device at the same time who hasn't CID unlocked theirs.
Unfortunately, I've never been in a situation where I've needed to use my warranty, so I've never flashed back, but I would guess the best thing to do is to try looking it up, doing a bit of research to try to make an educated guess as to which version you might have had. It may not matter if you're slightly out, I don't how fussy they are or how rigorously they check. I would guess that as long as there is a stock SPL, it would probably pass for the original and they wouldn't look twice. Don't quote me though, like I said, I've never been there.
If anybody thinks I am completely and utterly wrong or has experience of returning to original stock ROM and SPL for warranty purposes, please feel free to correct me!

Help Please!!!

I have flashed my at&t tilt 2 with core cell evo v1.2 & it was working fine for awhile but now my screen is just black i can hear the phone make sounds and all but can't see the screen at all i really need help fixing this as this is the only phone i have any help or suggestions will be greatly appreciated thanks in advance.

i may be wrong but from what u have described... ur having a Sleep of Death (SOD) problem. have u tried takin out the battery or soft reseting the phone?
heres a link to a potential problem solver. Try to stay away from CHT lock and auto update apps!

sagarc88 said:
i may be wrong but from what u have described... ur having a Sleep of Death (SOD) problem. have u tried takin out the battery or soft reseting the phone?
Click to expand...
Click to collapse
yes i have done both and after the phone reboots i can hear sounds but i am still unable to see anything on the screen

Edit - I take that back, if it's still not working after a reboot

Have you tried entering the bootloader and re-flashing with the stock ROM?

If you can't see anything at all on the screen, no splash screens etc, even after soft-reset or entering the bootloader, then it sounds like you have a hardware problem (screen failure).

steviewevie said:
If you can't see anything at all on the screen, no splash screens etc, even after soft-reset or entering the bootloader, then it sounds like you have a hardware problem (screen failure).
Click to expand...
Click to collapse
i can't even tell if i can enter the bootloader screen because i can't see anything on the screen is there any way to tell if it's in the bootloader screen without being able to see the screen at all & if i do have a hardware problem (screen failure) how can i put stock spl & stock rom back on the phone to get it serviced

steviewevie said:
Edit - I take that back, if it's still not working after a reboot
Click to expand...
Click to collapse
if its still not working after a reboot then what? please help me i need a solution to fix this because if i can't even fix this how can i even send it in to get fixed i won't be able to because it has been flashed & has hardspl on it
"PLEASE HELP"

It's a tricky situation. So if you hold down Volume Down (and keep it held down) and press the reset button, then you still don't have anything come up on the screen ?
How about if you try a hard reset, does anything come up then ? You can hear the phone making sounds, so it seems like it's just the screen ?
Putting the charger in doesn't help, does it ?
You could try flashing a stock ROM from SD card and seeing what happens.
You might well have to send it back under warranty with HardSPL still on. In that case, if it was me, then if they tried to say the warranty was void just because of HardSPL I would argue very strongly against that and ask them to prove it - e.g. how can HardSPL stop your screen working ? I don't know what country you're in, but in the UK I think our consumer protection laws would have something to say about that.

steviewevie said:
It's a tricky situation. So if you hold down Volume Down (and keep it held down) and press the reset button, then you still don't have anything come up on the screen ?
How about if you try a hard reset, does anything come up then ? You can hear the phone making sounds, so it seems like it's just the screen ?
Putting the charger in doesn't help, does it ?
You could try flashing a stock ROM from SD card and seeing what happens.
You might well have to send it back under warranty with HardSPL still on. In that case, if it was me, then if they tried to say the warranty was void just because of HardSPL I would argue very strongly against that and ask them to prove it - e.g. how can HardSPL stop your screen working ? I don't know what country you're in, but in the UK I think our consumer protection laws would have something to say about that.
Click to expand...
Click to collapse
how can i flash anything if i can't see the screen?

Doo Doo said:
how can i flash anything if i can't see the scrren?
Click to expand...
Click to collapse
I've never flashed via SD, so I could be wrong on this. But I thought it was still possible. I see that the instructions (in the sticky on flashing ROMs) say to put it into the bootloader and "follow the on-screen instructions". I wonder if it's possible to just wait for a while and then press the appropriate key ? Though I don't know what the "appropriate key" is.
Perhaps someone who has flashed via SD can comment further, e.g. as to whether it's possible to do this without seeing the screen ?

steviewevie said:
I've never flashed via SD, so I could be wrong on this. But I thought it was still possible. I see that the instructions (in the sticky on flashing ROMs) say to put it into the bootloader and "follow the on-screen instructions". I wonder if it's possible to just wait for a while and then press the appropriate key ? Though I don't know what the "appropriate key" is.
Perhaps someone who has flashed via SD can comment further, e.g. as to whether it's possible to do this without seeing the screen ?
Click to expand...
Click to collapse
man i really need to fix this maybe you can ask around for me since i'm new here & really don't know anybody on this board

I know it's frustrating, I'd be kinda worried if I had an apparently-non-working screen too. But please be patient, and wait for more people to see your posting. The folks in the US will be coming online around this sort of time, so there will be more people looking in and hopefully someone can help further.

Flash without seeing the screen
Enter boot loader even if you can not see the screen. You can flash your phone to stock then enter boot loader again and hard spl. I had a similar situation and was able to complete the process and warranty repair with AT&T no problems, or you can pay to have it fixed at an outside shop. I was quoted 150 and refused to spend that muck so I flashed the phone without seeing the screen...

I saw your post over on Sergio's thread but decided to answer you here.
You do have a blown screen, no doubt there. How that happened is not really relevant.
My best advise is to connect your phone to your PC and wait for the activesync connection to come up. Once that happens you know you have a good connection and can flash. Run the RUU (or exe) for your stock ROM, the on screen (PC Screen) prompts will let you know if it can't proceed. Once the stock ROM is back on it, follow the same procedure and put the stock SPL back. Then send it off to get the screen replaced.
Hope that helps
Russ

Russ741 said:
I saw your post over on Sergio's thread but decided to answer you here.
You do have a blown screen, no doubt there. How that happened is not really relevant.
My best advise is to connect your phone to your PC and wait for the activesync connection to come up. Once that happens you know you have a good connection and can flash. Run the RUU (or exe) for your stock ROM, the on screen (PC Screen) prompts will let you know if it can't proceed. Once the stock ROM is back on it, follow the same procedure and put the stock SPL back. Then send it off to get the screen replaced.
Hope that helps
Russ
Click to expand...
Click to collapse
well when i plug my phone to the computer activesync is not popping up what can i do to get activesync to recognize my phone

can somebody please help me i need to reflash my phone but i am unable to see anything on my screen when i plug it up to my computer activesync is not working so what can i do please i really need help with this

Flashing witout screen
Step 1
Enter boot loader mode (* Remove the back cover from the phone.
* Hold the Volume Down button.
* Use the stylus to press the reset hole.
* Or if the device was powered off, press the power button whilst holding down the Volume Down button.)
and attach to computer. (wait 30 to 60 seconds)
Step 2
Check device manager for HTC mobile sync under mobile devices.(Active sync will not work in boot loader mode)
Step 3
Flash using Rhodium CustomRUU on your PC. (use original ROM from At&T.
Step 4 repeat for Radio
Step 5 Use Stock_SPL_Restore_087.zip from http://forum.xda-developers.com/showthread.php?t=550131 repeat the process with it.
This should work it did for me. Let me know if you run into problems.

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

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.