Database Users

Odin doesn't recognize my s7 edge (trying CF auto root)

Hi, I've been reading the thread for CF auto root to give it a go. I've downloaded the drivers (I've got 1.5.51 now installed, haven't been able to find later ones), I've got the 2.74 SU version that helps to overcome a recent security policy update issue reverting root status and the CF auto root zip file (CF-Auto-Root-hero2lte-hero2ltexx-smg935f.zip) which has odin 3.10.6 included (not quite sure if I can use any recent odin version). I even got my stock firmware com sammobile and extract the proper boot.img from the AP* file (just in case I got something wrong at sometime). I've enabled the OEM unlock too on developer options. I understand I can give it a go without having to go with a custom recovery (still not sure and haven't got the whole picture about the dm-verity thingy and what effects has on the device but someone mentioned something like loosing the encryption or so). This is my first try on getting root on my s7 edge G935F (international version), so it shouldn't have any boot.img problem (but trying to be prepare since I can't go about without my phone being working).
So, I've got my phone into download mode, started odin, loaded on AP the tar.md5 file from the CD auto root zip file (CF-Auto-Root-hero2lte-hero2ltexx-smg935f.tar.md5), connect the device throuhg usb cable and I was expecting Odin to recognize it but nothing happens. Since in the threads I've been researching for s7 edge there is no indication on waiting to see something happening on ODIN (but in some other threads - not s7 edge related though - mention something about having to see a blue indicator on COM), I'm not quite sure if I'm expected to just hit start even if no apparent change is happening on ODIN nor there is some drivers installing/configuring when connecting the device on download mode. Since I'm quite new to this, I'm no sure if I should connect the device first with some other option enabled, like USB debugging or if I'm missing something quite obvious for someone familiar with flashing with odin?
Kind regards for any help!
PS. I did tried to find an answer through searching but foung nothing related s7 edge wise so I'm at a loss not even knowing if just hitting start without having the device recognized on ODIN will do any harm at all (that newbie I am)

Try odin 3.11
Aldo plug your phone in first and than once recognised load the autoroot to ap

skinza said:
Try odin 3.11
Aldo plug your phone in first and than once recognised load the autoroot to ap
Click to expand...
Click to collapse
Thank you skinza for your reply, I did tried what you suggested and although it wasn't enough for getting it solved it helped me to know I was on the correct path and that I could use an updated odin.. finally, the problem was on embarrassing one since I went into download mode but hadn't push the volume up to get into the actual ODIN mode (too newbie of me but I was trying to follow the instructions I'd found and none were that specific - a bit afraid of messing it up). Nonetheless, thanks again for your time! Kind regards!
Edit: Now I'm rooted (thanks CF) and it took less than expected (a couple of mins or so). I didn't go the custom recovery way, so it might have been that.

cmanh said:
Thank you skinza for your reply, I did tried what you suggested and although it wasn't enough for getting it solved it helped me to know I was on the correct path and that I could use an updated odin.. finally, the problem was on embarrassing one since I went into download mode but hadn't push the volume up to get into the actual ODIN mode (too newbie of me but I was trying to follow the instructions I'd found and none were that specific - a bit afraid of messing it up). Nonetheless, thanks again for your time! Kind regards!
Edit: Now I'm rooted (thanks CF) and it took less than expected (a couple of mins or so). I didn't go the custom recovery way, so it might have been that.
Click to expand...
Click to collapse
Not a problem mate
Just fyi you will need twrp if you want to install custom roms like superman rom or echo rom etc

skinza said:
Not a problem mate
Just fyi you will need twrp if you want to install custom roms like superman rom or echo rom etc
Click to expand...
Click to collapse
Thanks again! for now I won't be going for a custom rom but wanted to be able to install a firewall to stop some apps from draining my prepaid data (limited)..
I was planning on having xposed installed but it seems I need a custom recovery for that as well.. I used to have xprivacy on a previous nexus 4 and loved I could limit some permissions that are still missing now on marshmallow but haven't got a grip yet as per the effects due to the dm-verity thing.. would you happen to know anything about it? and I was also wondering about if I do need to have the OEM unlock still enabled now that I'm rooted? (The later because I'd been robbed of my cellphones in the past - even recently a new s7 edge that didn't last me even a month and wouldn't want to let them have an easy pie on having the device available)
Regards!

I'm facing the same issue but even after going into download mode properly after pressing vol up
odin doesn't detect my s7 edge
I've installed all the drivers also

Singhathia said:
I'm facing the same issue but even after going into download mode properly after pressing vol up
odin doesn't detect my s7 edge
I've installed all the drivers also
Click to expand...
Click to collapse
Got the same issue. I'm new with this. My colleague wants me to learn and test and load Lineageos on some brand new S7 G930F devices he gave me which I have already switched to dev mode with OEM unlock and USB debugging on and the devices smoothly jumped into ODIN downloading.... mode
I also have the proper Samsung USB Driver installed. (did it several times after ODIN didn't recognize my device)
However, according to the manual, I should start up ODIN, then connect the device via USB cable to the workstation (as unsuccessful I already tried 3 workstations with Windows 7 and Windows 10) whilst having the phone in download mode... .BUT NOTHING APPEARS in the Log field and the ID:COM Box doesn't change colour and my manual says that it should.
My workstation however recognizes the devices with positive messages so I guess the drivers are good.
My co-worker gave me ODIN v3.10, but as this didn't work I downloaded and installed V3.12, but unfortunately also without any luck.
What am I doing wrong?

which OS?

S7 edge SM-G935F
Hey guys,
i tried rooting my s7 edge but after i got into TWRP my phone went into a bootloop. when i got back download mode, odin still found my phone, though everytime i tried to enter TWRP again, odin said there was a FAIL and my phone immediatly went back into bootloop. I tried to reinstall the samsung usb drivers but now odin cant find my phone anymore.
Before i screw up even more, can someone please help me? right now im stuck in download mode and odin 12, 11, and 10 all wont recognize my phone, also not if i use different cables. my windows laptop however still gives me the device found and device disconnected sound everytime i (dis)connect my phone.
any ideas?
thanks
EDIT: Okay i tried my USB 3.0 port and now odin found my phone. just weird... now i just need to solve the problem that I'm still stuck in the Bootloop but that probably doesnt belong in this thread

Need to downgrade from Marshmallow to Kit Kat because of Samsung Lock

I put myself into a perdicament and I have been searching high and low to figure this out.
Currently I am samsung Locked out of my phone, I am getting a processing failed error even on a correct samsung account entry. I've tried everything from deleting the account to re-entering the IMEI on the account to register it on the same username and pass. Unfortunately nothing.
Next I tried to bypass the samsung lock by using Root Junky's Method. I couldn't follow it all the way because my phone didn't have one crucial step ( to scan business card button) So I basically got around it by getting into google play and downloading a file explorer and continuing the process. I then downloaded SideSync and sololauncher to have some sort of homepage.
With all that I'm still not able to enter the samsung account info. when you try to add another account it just backs out instantly, and if you try to enter the information on an app that makes you log in, it just immediately closes the app.
Sooo, I've been reading the next possible solution is to get the phone on Kit Kat but I'm honestly having the hardest time doing so.
I dropped the phone down to lollipop and tried rooting but I got stuck on the phone not getting usb debugging dialog to pop up, even though It pops up for my samsung s3 so I know it's not the cord or my computer. This is where I'm stuck at. I have no clue how to drop the phone back down to Kit kat and would love someone to help me out or to just give me a nudge in the right direction.
Currently on pd1 stock samsung s5 vzw.
Thank you guys in advanced!

http://forum.xda-developers.com/verizon-galaxy-s5/general/booted-ncg-pb1-bootloader-t3431692
http://forum.xda-developers.com/ver.../reactivation-lock-off-finally-stuck-t3433342

damagi123 said:
http://forum.xda-developers.com/verizon-galaxy-s5/general/booted-ncg-pb1-bootloader-t3431692
http://forum.xda-developers.com/ver.../reactivation-lock-off-finally-stuck-t3433342
Click to expand...
Click to collapse
Thank you for the threads! The bottom one "reactivation lock" one is actually the one I started on, but for some reason, my phone will not for hte life of me bring up the debugging dialog, if i can get the debugging dialog to pop up then everything will be perfect and I can root and continue on from there.. but for some reason the galaxy s5, will not pop up that message, I've flashed ok3, pb1, pd1, and pd4 or whatever the latest one is. Hilariously pd4 actually popped up the debugging dialog to accept permission to my computer.... something that I can't do anything about or do anything with that since you cannot root on pd4. I have a galaxy s3 and that pops up debugging dialog instantly so I know it's neither my cord or my computer. All drivers, programs and adb are installed on my computer.
Those two forum threads are perfect if I can just get debugging to pop up.. it's like once I get the bypass to work for ok3 or pb1, none of the status bar things work, some pop ups work and I think that it is popping up but it's blocking it or something seeing how I'm just by passed through it and not actually done with the setup wizard.

Just need to get my phone authorized instead of unauthorized. the RSA KEY debugging pop up wont pop up at all. I'm not sure if it's because samsung lock basically shuts down part of the phone to be functional and wont let it pop up? I just can't figure it out.

I've been trying to figure this out but so far a no go
To make my guide 100% working I will try again tonight I think

natepez23 said:
I put myself into a perdicament and I have been searching high and low to figure this out.
Currently I am samsung Locked out of my phone, I am getting a processing failed error even on a correct samsung account entry. I've tried everything from deleting the account to re-entering the IMEI on the account to register it on the same username and pass. Unfortunately nothing.
Next I tried to bypass the samsung lock by using Root Junky's Method. I couldn't follow it all the way because my phone didn't have one crucial step ( to scan business card button) So I basically got around it by getting into google play and downloading a file explorer and continuing the process. I then downloaded SideSync and sololauncher to have some sort of homepage.
With all that I'm still not able to enter the samsung account info. when you try to add another account it just backs out instantly, and if you try to enter the information on an app that makes you log in, it just immediately closes the app.
Sooo, I've been reading the next possible solution is to get the phone on Kit Kat but I'm honestly having the hardest time doing so.
I dropped the phone down to lollipop and tried rooting but I got stuck on the phone not getting usb debugging dialog to pop up, even though It pops up for my samsung s3 so I know it's not the cord or my computer. This is where I'm stuck at. I have no clue how to drop the phone back down to Kit kat and would love someone to help me out or to just give me a nudge in the right direction.
Currently on pd1 stock samsung s5 vzw.
Thank you guys in advanced!
Click to expand...
Click to collapse
Have wifi signed and good to go before you follow his method then do his method at the WiFi screen after signing into WiFi
at the contact screen click add a website
And add this website
http://www.rootjunkysdl.com/files/?dir=Apps/FRP
Then click on the website link and it will go to web browser
and download frp bypass app and install tell me if it works

[email protected] said:
Have wifi signed and good to go before you follow his method then do his method at the WiFi screen after signing into WiFi
at the contact screen click add a website
And add this website
http://www.rootjunkysdl.com/files/?dir=Apps/FRP
Then click on the website link and it will go to web browser
and download frp bypass app and install tell me if it works
Click to expand...
Click to collapse
Heya Yeah, I have already done almost all of rootjunky's methods. Got into a a webbrowser and accessed google play, also downloaded that frp work around but i think it's for the google reactivation lock not samsungs reactivation lock. I reboot and it goes right back into the same thing. the frp bypass just makes it so you can reenter your google account info if you are google locked. :/

How can I recover data from my Core Prime SM-G360G with a broken screen of death? :-o

Hello experts!
First off I do admit I have cross posted some information here. Perhaps I should have just asked here first. As a lot of research I have been doing lead me here. I am also aware of the XY problem. So I am giving what information I have on my problem and what I have done to resolve it. In a nutshell I need to recover app data from internal storage.
So here is yet another story of a dropped Samsung Galaxy BSOD. The broken screen of death! :-o
So I dropped my phone and the screen broke, fixed it then put on a screen protector that fractured the new screen in my pocket, of all things. Through that it spiraled out and it needed a new LCD as well as screen which failed to repair as LCD remains blank now. I suspect the display controller has somehow fried. Decided to give up and buy a new phone.
My broken phone is a Core Prime G360G. The digitizer doesn't respond. The LCD is blank. The side buttons, volume, power and home, work fine.
The good news. It turns on and technically still works. It has no screen lock. I can plug it in to computer via USB and it mounts over MTP. I can also install apps remotely (so to speak) from another computer from the Play site. I've installed Samsung Switch this way. Switch does work and I managed to back up files from the Windows program which is good but in my case it isn't smart enough as it doesn't back up app data which I need. I also have AirDroid installed and can reach it that way I but didn't enable mirroring before the incident. Trying to use that to download an app (~10MB in my case) just results in the browser stalling.
The bad news. It is not rooted. It has stock standard firmware. USB debugging is not enabled. Last time I tested OTG wasn't supported. At least not for OTG USB sticks.
So in effect it's rooted without being rooted! Yes, i know, I know, Android rule of thumb; before you accidentally drop your phone, even without planning it, and not being a seer, enable USB debugging for no apparent reason! It all makes sense now.
I've spent the last two weeks reading forums all over the place, blogs and watching videos about how to recover data with a broken screen. And in almost all cases they tell you to enable USB debugging. Well that's nice advice and about as useful as advising someone with a broken toilet to sit down, do their business and then flush it! And is met with equally crappy commentary pointing the conundrum out.
My computer has Windows (Vista) and Linux (Mint 64). I read all about ADB and installed this on both Windows and Linux. And tried to talk to it that way with adb and fastboot which failed. I then read of Samsung devices being different, with a download mode, and using this Odin or Heimdall program. So I could "see" the process I tested with my new phone (a J5 Prime as it happens) and learned I needed to use download mode and how to enter it on boot. Recovery mode didn't work as expected. Heimdall was the only program that would work. I managed to view the PIT on my J5. Odin did see my phone but I found the interface harder to work with at first.
I tried on my Core. Blindly got it into download mode. Heimdall could see it. But the transport was buggy as I kept getting USB errors. I ended up removing it then compiling Heimdall v1.4.2 from source. This worked better, even though it was giving empty bulk transfer warnings, but it managed to download the PIT file. So at this point I can blindly get my Core into download mode and am able to communicate with it using Heimdall.
This is where I am at. I would prefer it if a screen mirroring app could be installed that would load up and activate remotely when a client run on my computer is loaded up. I don't care if it is VNC or how it connects. But it would need to load itself up on the phone and work without needing intervention on the phone and without USB debugging. If there is an emergency mirroring app on the Play store or even an APK that can be installed remotely, using AirDroid or any other means, I would be happy to test it. I'd write one myself if knew how to write an app! LOL.
If USB debugging could be enabled by any remote means then I am welcome to hear how. It opens a window to possibility. But a window that is hard to open if it's locked.
So I would prefer to keep this at the app level if possible. Since apps can help. But if need be as long as it doesn't destroy data I am willing to install a custom recovery image. It looks like I will need to do this as I have exhausted all other possibilities. At least, when I read of the latest broken screen mirroring app, there is always a catch of it needing debugging or activating on the phone.
Although there is support for other Core Prime variants, support for my specific G360G model seems to be lacking. The information I read looks vague at best. I read about CWM and TWRP. But on the TWRP site, although there is Core Prime images, nothing is listed for exactly a G360G. There is no point to me flashing TWRP recover image only to find it doesn't work and I have bricked recovery mode. I'd look like a right twerp!
So guys, after all the info I have given you, what's the next step? Thanks.

Okay so just an update here. I have some good news and bad news on my part. I've been hacking around with customising recovery and modifying compatible recovery images in order to get debugging activated.
The good news is I got USB debugging enabled. The bad news is my computer is unauthorised.
I'm stuck at this point. I updated the adb_keys file with what was on my computer and it won't budge. I finally get somewhere and now I've once again hit a wall. This is just so annoying. :-x

The final countdown. After months of cracking and hacking I've broken in! I modded my hack to create the needed folder just to be sure and updated my RSA key. Applied the firmware patch and let it reboot. Even while booting I knew something was different. The digitizer started responding to my touch and making water noises. Which was strange as I never noticed it doing that before.
I issued an adb command and it was accepted. I could then browse around the system. I already had screen mirroring software installed and all it needed was USB debugging working and suddenly it worked. This was a blessing as I found that trying to do other things like going into a root shell or do an adb backup caused a requester to come up on screen. Had I not been able to satisfy that on a virtual screen I would have run into the same trap of circles I had just climbed out of. Having a rooted phone with no root access.
I was then able to install a backup app and extract the data out. Hooray! I had actually installed it from Google Play site remotely but found there was no space for it and it had failed. But the account said it was installed. With a view to a mobile I could then remove another app and install it from Play on the phone itself. Given how well this worked once I learned what was needed to be done I suppose I should make up a guide. An automated script to create an ADB patch wouldn't go far astray.

Well, that didn't go well

Tab 5se Stock firmware
So I bought a 3rd 5se from a third party, all I checked for was for FRP lock, well it wasn't locked, but when I got it home and rebooted, it says is has a unlocked bootloader. So I hard factory reset it and now it states that only stock firmware can be installed in boot and won't go any further.
So I'm guessing I need to use ODIN to flash a factory ROM but I'm not sure which one as I can't seem to find a USA one on Sammoble, I do see a Canada one though.
Which version of ODIN should I use (WIN 10)
Which ROM, I'm in the USA, WIFI ONLY SM-T720, country code ?
Any other tips, as I haven't flashed anything in almost a decade probably.
Need to get this back to all stock, help

You want the XAR country code version which is the US rom. For Odin, use the newest version for our tablet. Good luck.

puredigital said:
Tab 5se Stock firmware
So I bought a 3rd 5se from a third party, all I checked for was for FRP lock, well it wasn't locked, but when I got it home and rebooted, it says is has a unlocked bootloader. So I hard factory reset it and now it states that only stock firmware can be installed in boot and won't go any further.
So I'm guessing I need to use ODIN to flash a factory ROM but I'm not sure which one as I can't seem to find a USA one on Sammoble, I do see a Canada one though.
Which version of ODIN should I use (WIN 10)
Which ROM, I'm in the USA, WIFI ONLY SM-T720, country code ?
Any other tips, as I haven't flashed anything in almost a decade probably.
Need to get this back to all stock, help
Click to expand...
Click to collapse
I use Frija instead of Sammobile to get the latest stock. Just use SM-T720 as the model and XAR as the CSC. If you search for how to unlock the bootloader, you can use the same proceedure to relock it. It should perform a factory reset as part of the process and you might not need to reflash a ROM.

Not sure..
Since the device won't turn off, restart nor go into download mode
Aqua blue sorta cyan screen. Top in red (like a terminal response) says," Only official released binaries are allowed to be flashed (vbmeta)"
Then on main screen in center;
Security Error: This phone has been flashed with unauthorized software & is locked. Call your mobile operator for additional support
lewmur said:
I use Frija instead of Sammobile to get the latest stock. Just use SM-T720 as the model and XAR as the CSC. If you search for how to unlock the bootloader, you can use the same proceedure to relock it. It should perform a factory reset as part of the process and you might not need to reflash a ROM.
Click to expand...
Click to collapse

puredigital said:
Since the device won't turn off, restart nor go into download mode
Aqua blue sorta cyan screen. Top in red (like a terminal response) says," Only official released binaries are allowed to be flashed (vbmeta)"
Then on main screen in center;
Security Error: This phone has been flashed with unauthorized software & is locked. Call your mobile operator for additional support
Click to expand...
Click to collapse
The only time a ran into a situation where I couldn't turn off that tablet, I just had to put it aside for a day or so till the battery ran down. Then use the method of holding both vol up and down, and NOT power, and then plugging in the cable from the PC. Must be from PC and not charger.

puredigital said:
Since the device won't turn off, restart nor go into download mode
Aqua blue sorta cyan screen. Top in red (like a terminal response) says," Only official released binaries are allowed to be flashed (vbmeta)"
Then on main screen in center;
Security Error: This phone has been flashed with unauthorized software & is locked. Call your mobile operator for additional support
Click to expand...
Click to collapse
I ran into this recently when I went back to stock to get the fingerprint for Magisk Module and then went back to Lineage. You just need to Odin the factory firmware. The tablet will turn off, I think the key combination to force it off is power and volume down? Its been a few weeks, but I was able to get back into download mode. I found other threads for samsung phones that had this same issue and basically used them as rough guides.
As mentioned you just need to use XAR ROMs, your box should say XAR. I believe both Canada and Cellular South ROMs will come up as XAR roms IIRC?

Bruh. I had the same issue and you will not be able to flash your way around and FRP lock. I found a guy on eBay to remove the FRP lock and NOT through flashing. For $10 is was done in 10 minutes. I get if you want to figure it out. I'm a flasher and love to figure this **** out too but with a recent update Samsung blocks this. Trust me. Spend $10 and it's done. Also many people say they can do this on eBay. I only recommend this guy: https://www.ebay.com/itm/273424666857. Just select a new auction of his and message him.
Sent from my SM-T720 using Tapatalk

elcidroyale said:
Bruh. I had the same issue and you will not be able to flash your way around and FRP lock. I found a guy on eBay to remove the FRP lock and NOT through flashing. For $10 is was done in 10 minutes. I get if you want to figure it out. I'm a flasher and love to figure this **** out too but with a recent update Samsung blocks this. Trust me. Spend $10 and it's done. Also many people say they can do this on eBay. I only recommend this guy: https://www.ebay.com/itm/273424666857. Just select a new auction of his and message him.
Sent from my SM-T720 using Tapatalk
Click to expand...
Click to collapse
He said he checked to make sure this was not the FRP lock. Assuming this is the same message I got which says only official binaries can be flashed, please take this to a service center and it there maybe a cost involved (obviously I'm paraphrasing), you can fix it with Odin. I was on the latest firmware as well, as I updated fully to get the fingerprint for the MagiskHide module. This sounds like a different issue, to me.
I mean if that works it's $10 well spent I guess.

Oh my apologies as I misread his post. I just saw "FRP" and chimed in. Hope he gets it sorted out.
OhioYJ said:
He said he checked to make sure this was not the FRP lock. Assuming this is the same message I got which says only official binaries can be flashed, please take this to a service center and it there maybe a cost involved (obviously I'm paraphrasing), you can fix it with Odin. I was on the latest firmware as well, as I updated fully to get the fingerprint for the MagiskHide module. This sounds like a different issue, to me.
I mean if that works it's $10 well spent I guess.
Click to expand...
Click to collapse

Almost !
Well, I finally reflashed the device with factory stuff, it's working fine now, no locks, except now it tells me the bootloader is unlocked on boot. I flashed it with Odin, no options, just loaded the 4 files and done.
How do I get this to STOCK, out of the box status. Steps ?

Device not starting/black screen after stock-ROM flash via Odin

Hello, everyone,
I tried to install LineageOS on my S10 Plus yesterday. That worked so far, but I found that it didn't have a decent camera app and the Samsung Watch wasn't that easy to connect either. So I thought I'd just go back to the Stock ROM again. I then downloaded the latest stock firmware according to this guide and installed it with Odin. The installation also runs through, after the installation the mobile phone starts and after the start screen there is an Android man with the signature "Erasing". After a few seconds, the device turns off and stays black. Even if I put it on the charger or try to restart it, nothing happens. I keep getting into download mode and recovery, but that's about it. Multiple reinstallations and resets via the recovery didn't help - the phone just won't start.
I used the CSC_... and not the HOME_CSC_... at the firmware is the right one for my phone.
Is there any way I can salvage the device? I'm afraid that something in the memory is defective now, which has nothing to do with the flashing itself. Do you have any ideas?
Many thanks!

tefracky said:
Hello, everyone,
I tried to install LineageOS on my S10 Plus yesterday. That worked so far, but I found that it didn't have a decent camera app and the Samsung Watch wasn't that easy to connect either. So I thought I'd just go back to the Stock ROM again. I then downloaded the latest stock firmware according to this guide and installed it with Odin. The installation also runs through, after the installation the mobile phone starts and after the start screen there is an Android man with the signature "Erasing". After a few seconds, the device turns off and stays black. Even if I put it on the charger or try to restart it, nothing happens. I keep getting into download mode and recovery, but that's about it. Multiple reinstallations and resets via the recovery didn't help - the phone just won't start.
I used the CSC_... and not the HOME_CSC_... at the firmware is the right one for my phone.
Is there any way I can salvage the device? I'm afraid that something in the memory is defective now, which has nothing to do with the flashing itself. Do you have any ideas?
Many thanks!
Click to expand...
Click to collapse
same thing happened to me today. but I flashed my s10e the bootloader and modem file of android 9 from twrp, the phone did not boot up and I loaded the stock rom again, then when I open it, it's the same as yours, I really need urgent help.
Releases · corsicanu/9820-bootloaders_and_modems
Contribute to corsicanu/9820-bootloaders_and_modems development by creating an account on GitHub.
github.com
EDİT: Anyway, I solved the problem, I flashed the bootloader and modem file that is suitable for my current version from the same site with twrp and the phone turned on. maybe you can solve it by flashing the bootloader and modem file suitable for the current version. try if you want

Thanks a lot, this worked!

tefracky said:
Thanks a lot, this worked!
Click to expand...
Click to collapse
I'm glad it worked.
I was very afraid that the phone died, what did you do for 5 days in this state?
Now I have a question in my mind: When Samsung releases an update in the future, will the bootloader and modem files be updated when we update it with odin? won't it be updated? After that, do we will always update manually as twrp? do you have any idea?

Well, I simply didn't use a mobile phone in these days. It was a very "interesting" experience, but not a huge problem. I sometimes opened WhatsApp as Windows App (interestingly, which works without phone).
I don't know, what happens at a Samsung Update, but until Android 13, I will not update (so probatly never). In our German forum (www.android-hilfe.de), a pre rooted and debloated "Stock"-Firmware is provided, but I can't install it, since my Bootloader is too new (V15 instead V14 for the ROM). When it is possible, I will install this firmware. If you are interested, here is the link: https://www.android-hilfe.de/forum/...3-2022-stock-rom-v2-0-pre-rooted.1000713.html

tefracky said:
Well, I simply didn't use a mobile phone in these days. It was a very "interesting" experience, but not a huge problem. I sometimes opened WhatsApp as Windows App (interestingly, which works without phone).
I don't know, what happens at a Samsung Update, but until Android 13, I will not update (so probatly never). In our German forum (www.android-hilfe.de), a pre rooted and debloated "Stock"-Firmware is provided, but I can't install it, since my Bootloader is too new (V15 instead V14 for the ROM). When it is possible, I will install this firmware. If you are interested, here is the link: https://www.android-hilfe.de/forum/...3-2022-stock-rom-v2-0-pre-rooted.1000713.html
Click to expand...
Click to collapse
thanks, if i'm going to use stock rom i prefer to root it myself