Database Info

Help me, cannot flash CM9

I flashed the first build of CM9. so sweet, and now I have problem. Battery is 50% and after 2 hours, battery 0%, cannot charge phone.
I stock my phone back 2.2, original rom and download 4th build CM9.
Get stuck at Samsung Screen, follow the instruction, I cannot choose rom in CWM, screen cannot display full option and I can re-flash 4th CM9?
Plz, help me

You Can reflash again..? Did you get blue cwm?

I had this problem with CM9 too. What I did was I let it do its freezing thing on the charger for about 2 minutes, then I tried turning it on off the charger, just until the samsung logo disappears, then quickly replug in the phone and it'll charge! I'm assuming that's what your issue is, at least. As for the battery life, I'm not sure what to tell you there.

bigjoe2675 said:
You Can reflash again..? Did you get blue cwm?
Click to expand...
Click to collapse
yes, I cannot reflash again after got stuck at samsung screen.
back to blue CWM, the screen cannot display full options, cannot choose rom to reflash

kitarodo said:
yes, I cannot reflash again after got stuck at samsung screen.
back to blue CWM, the screen cannot display full options, cannot choose rom to reflash
Click to expand...
Click to collapse
Are you having rainbows?

Bjray said:
Are you having rainbows?
Click to expand...
Click to collapse
yes, rainbow display a half screen, and cannot choose rom or whatever you want ...

kitarodo said:
yes, rainbow display a half screen, and cannot choose rom or whatever you want ...
Click to expand...
Click to collapse
Two methods you can use...go back to stock and it will put gb boot loaders and CWM, so that you can flash CM9 with CWM visible/working.
Read all details on these OPs...
Odin
http://forum.xda-developers.com/showthread.php?t=1613523
One click
http://forum.xda-developers.com/showthread.php?t=1524081

ocesite 159
bigjoe2675 said:
Two methods you can use...go back to stock and it will put gb boot loaders and CWM, so that you can flash CM9 with CWM visible/working.
Read all details on these OPs...
Odin
http://forum.xda-developers.com/showthread.php?t=1613523
One click
http://forum.xda-developers.com/showthread.php?t=1524081
Click to expand...
Click to collapse
I will try it , thanks bro

so bad, stock 2.3.6 cannot flash any rom, cannot stock back to 2.2, odin cannot connect ??? what's happened ?

kitarodo said:
so bad, stock 2.3.6 cannot flash any rom, cannot stock back to 2.2, odin cannot connect ??? what's happened ?
Click to expand...
Click to collapse
Which method did you use? More details please, and we can get you flashing from 2.3.6. Don't go back to 2.2.
If you flashed one of the Odin to stock 2.3.6 options w/ root, you just need to use SGS Kernel Flasher (in market) to flash a kernel w/ cwm recovery. See the FAQ in the first link that bigjoe gave you.
If you used Heimdall one click, read further down in qkster's thread for how to get cwm recovery. You need cwm recovery to flash roms.
You don't need to Odin again, but to get it to see your phone, try a different USB port. Sounds like you're trying to use your Heimdall port (Heimdall libusb installs to and takes over one specific port.).
Sent from my SAMSUNG-SGH-I997 using Tapatalk 2

God feels like this everytime a thread like this is posted due to the lack or research and reading
{
"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"
}
lol

jscott30 said:
Which method did you use? More details please, and we can get you flashing from 2.3.6. Don't go back to 2.2.
If you flashed one of the Odin to stock 2.3.6 options w/ root, you just need to use SGS Kernel Flasher (in market) to flash a kernel w/ cwm recovery. See the FAQ in the first link that bigjoe gave you.
If you used Heimdall one click, read further down in qkster's thread for how to get cwm recovery. You need cwm recovery to flash roms.
You don't need to Odin again, but to get it to see your phone, try a different USB port. Sounds like you're trying to use your Heimdall port (Heimdall libusb installs to and takes over one specific port.).
Sent from my SAMSUNG-SGH-I997 using Tapatalk 2
Click to expand...
Click to collapse
thanks bro, after flash Heimdall on click, I came back to 2.2 - original rom, and now, I can flash CM9 and no problem so far

kitarodo said:
thanks bro, after flash Heimdall on click, I came back to 2.2 - original rom, and now, I can flash CM9 and no problem so far
Click to expand...
Click to collapse
If you went back to 2.2 bootloaders with a back-to-stock package, I hope that you like rainbows in your recovery. You didn't have to go back to Froyo to get to CM9. Either way, though, if it's working for you, then glad it worked out.

jscott30 said:
If you went back to 2.2 bootloaders with a back-to-stock package, I hope that you like rainbows in your recovery. You didn't have to go back to Froyo to get to CM9. Either way, though, if it's working for you, then glad it worked out.
Click to expand...
Click to collapse
This time, I didn't get any problems, rainbows in recovery It's worked good for me, but 22/04 build, wireless work not good, turn on wireless too slow, sometimes need reboot to connect wireless

Hard brick? Soft brick? I need help

Please treat a newb gently...
I rooted my phone earlier tonight, followed all the instructions here, and everything went well. I flashed cwm recovery (I was most comfortable with it from an old phone.)
The first thing I did was back up my stock configuration for future use.
I then rebooted and started removing some bloatware. (The real reason I wanted to root.) I got a little overanxious and removed one app I decided I wanted back, so I rebooted to recovery and restored my backup with no problem.
Then, my phone wouldn't boot up out of recovery. So, I removed the battery and tried a simple boot - no luck. To make a long story short, I've booted to recovery multiple times. I've wiped and restored multiple times. No matter what I do though, the phone will not boot to anything but recovery.
Help!

Sounds a bit like the bootloader didn't unlock.
{
"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"
}
[/url]

How can I fix it?

butch50 said:
How can I fix it?
Click to expand...
Click to collapse
Ezunlock 1.2... Do you still have root?
Sent from my SCH-I535 using xda premium

Correct me if I'm wrong, but Ezunlock requires me to boot to the ROM. I can only boot to cwm recovery.
And yes, I rooted before trying to unlock the bootloader.

Sounds to me like you need to odin back to stock and start over. Guessing you didn't get the bootloader unlocked.

blackwolf77 said:
Sounds to me like you need to odin back to stock and start over. Guessing you didn't get the bootloader unlocked.
Click to expand...
Click to collapse
I've been away from a computer for a couple of days, but that's what I did. Worked like a charm, thanks.

Followed [GUIDE] Root for Jelly Bean 4.1.1 or 4.1.2, cannot mount sdcard to get .tar
blackwolf77 said:
Sounds to me like you need to odin back to stock and start over. Guessing you didn't get the bootloader unlocked.
Click to expand...
Click to collapse
I followed the directions exactly on this excellent xda site's "[GUIDE] Root for Jelly Bean 4.1.1 or 4.1.2" with all the correctly downloaded and installed files but when I get to "Step 4 - Rooting Your Device and Unlocking Your Bootloader Quote: Using your custom recovery flash the download you chose above from Step 1 (#3)"
I go to "install zip from sdcard" and I select it, and go to "choose zip from sdcard" I get "E: Can't mount / sdcard/".
So what does one do to "odin back to stock and start over"? Are the sequences of the steps in that guide in correct order? Thanks.

boldred said:
I followed the directions exactly on this excellent xda site's "[GUIDE] Root for Jelly Bean 4.1.1 or 4.1.2" with all the correctly downloaded and installed files but when I get to "Step 4 - Rooting Your Device and Unlocking Your Bootloader Quote: Using your custom recovery flash the download you chose above from Step 1 (#3)"
I go to "install zip from sdcard" and I select it, and go to "choose zip from sdcard" I get "E: Can't mount / sdcard/".
So what does one do to "odin back to stock and start over"? Are the sequences of the steps in that guide in correct order? Thanks.
Click to expand...
Click to collapse
To clarify after you flashed the bootchain through Odin did you then proceed to the step to flash a custom recovery? If you did, at the end of the custom recovery step did you wind up in recovery and do you have the SuperSU .zip on your phone? Keep in mind those instructions in that thread and the recovery image should work but are outdated. If things still don't work for you I would Odin back to stock to give yourself a fresh slate and then check out beanstown106's 1-click CASUAL package that will painlessly root, unlock your bootloader, and flash custom recovery for you.

blackwolf77 said:
Sounds to me like you need to odin back to stock and start over. Guessing you didn't get the bootloader unlocked.
Click to expand...
Click to collapse
shimp208 said:
To clarify after you flashed the bootchain through Odin did you then proceed to the step to flash a custom recovery? If you did, at the end of the custom recovery step did you wind up in recovery and do you have the SuperSU .zip on your phone? Keep in mind those instructions in that thread and the recovery image should work but are outdated. If things still don't work for you I would Odin back to stock to give yourself a fresh slate and then check out beanstown106's 1-click CASUAL package that will painlessly root, unlock your bootloader, and flash custom recovery for you.
Click to expand...
Click to collapse
Thank you for your reply.
Yes, I did have the SuperSU zip on the sdcard in the phone but I got the error message and continue to do so even after formatting two different sdcards, using the CWM that was installed. The sdcards won't mount in the phone. I can still use the phone (it's one week-old now) but the "custom" screen now appears when turning it on. I'd just like to get the stuff off of the phone that I put on there during this botched process. Apparently, after reading about this situation, this problem appears to be that the CWM corrupts itself and has to be uninstalled, re-installed, uninstalled and etc. until it finally correctly does it what it was supposed to do. This seems too risky now. This is an expensive phone and I thought that I had selected the best option for rooting, unlocking the bootloader and installing a ROM after searching for a week, so I was prepared for problems. I've rooted/unrooted devices before. But I wasn't prepared for this kind of error at this level. I still may try it using TWRP Recovery 2.4.3.0 rather than the ClockworkMod Touch Recovery 6.0.2.3. But, first, I need to know how to get back "to stock" -- the way it was before I tried this. The firmware of my phone is VRBMF1 and I do have a "d2vzw_VRBMF1_firmware.zip". I would deeply appreciate tips on how to use Odin to undo the changes made to my phone and restore it back to where it was before I tried this.
Thank you for your reply.

boldred said:
Thank you for your reply.
Yes, I did have the SuperSU zip on the sdcard in the phone but I got the error message and continue to do so even after formatting two different sdcards, using the CWM that was installed. The sdcards won't mount in the phone. I can still use the phone (it's one week-old now) but the "custom" screen now appears when turning it on. I'd just like to get the stuff off of the phone that I put on there during this botched process. Apparently, after reading about this situation, this problem appears to be that the CWM corrupts itself and has to be uninstalled, re-installed, uninstalled and etc. until it finally correctly does it what it was supposed to do. This seems too risky now. This is an expensive phone and I thought that I had selected the best option for rooting, unlocking the bootloader and installing a ROM after searching for a week, so I was prepared for problems. I've rooted/unrooted devices before. But I wasn't prepared for this kind of error at this level. I still may try it using TWRP Recovery 2.4.3.0 rather than the ClockworkMod Touch Recovery 6.0.2.3. But, first, I need to know how to get back "to stock" -- the way it was before I tried this. The firmware of my phone is VRBMF1 and I do have a "d2vzw_VRBMF1_firmware.zip". I would deeply appreciate tips on how to use Odin to undo the changes made to my phone and restore it back to where it was before I tried this.
Thank you for your reply.
Click to expand...
Click to collapse
To use Odin I would first download the latest version of Odin from here. Then I would extract the contents of the .zip file that contains Odin to a folder on your computer. Also I would recommend downloading the I535VRBMF1 firmware from here. Once you have done this click on the Odin .exe file. Now that you have launched Odin I would recommend taking a look at this guide on how to flash the firmware. After you have flashed the firmware to your device and have a clean slate then I would go ahead and use the 1-click by beanstown106 to root, unlock bootloader, and install custom recovery. Feel free to keep asking questions if you need as I'll be happy to answer them.

Here is a list of all .img files in the newest update. Which ones should I NOT flash?

OK so this is going to be a unique question for some reason. I can't find what a lot of these .img files do, and no sites really break it down.
Basically I am rooted/unlocked bootloader on my Google Pixel (from the Google store) and I want to flash everything possible except .imgs that will mess with my bootloader or ones that will wipe my phone.
I understand that flashing all of these are not necessary, as no guides even mention modem.img, but I want to make sure I have the most up to date everything, plus I want to learn what all these imgs are for.
Anyway, here is the complete list:
{
"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"
}
What is pmic.img? hosd? apdp? rpm?
A lot of guides and sites make no mention on a lot of these, and a lot of them seem important, especially in regards to getting the best signal on my phone, battery, wifi reception, and things like that.
So for argument's sake, say I want to manually flash as many of those img files as possible, but without loosing root, without locking my bootloader, and without losing my data, which ones am I free to flash? Everything but boot.img and bootlocker.img? I have no clue!
Thank you very much in advance for any info!

This won't exactly answer your question but first, nothing but you specifically locking your bootloader will lock it. Flashing an updated bootloader doesn't lock it.
I'm running the completely stock ROM but rooted and with TWRP. When the July update came out, I extracted the full update zip, modified the flash-all.bat to remove the "-w" wipe command from the one fastboot command that includes it so I didn't lose any app data. Then flashed the entire stock ROM and made a TWRP backup of the boot.img.
Then redid the fastboot boot TWRP.img, flashed the full TWRP RC2 zip, rebooted recovery, re-flashed SuperSU v2.82 and everything is golden. Note that I downgrade TWRP to RC1 for back up and restore, and use RC2 for all flashing.
I also did a full Titanium Backup to Google drive and also a full TWRP backup before any of this and copied to a flash drive as things happen.
The TWRP backup of the current correct unmodified boot.img has saved me a couple of times when I was away from the computer and did something to cause the phone to only boot to recovery. After restoring the backup just flash SuperSU again.

roirraW "edor" ehT said:
This won't exactly answer your question but first, nothing but you specifically locking your bootloader will lock it. Flashing an updated bootloader doesn't lock it.
I'm running the completely stock ROM but rooted and with TWRP. When the July update came out, I extracted the full update zip, modified the flash-all.bat to remove the "-w" wipe command from the one fastboot command that includes it so I didn't lose any app data. Then flashed the entire stock ROM and made a TWRP backup of the boot.img.
Then redid the fastboot boot TWRP.img, flashed the full TWRP RC2 zip, rebooted recovery, re-flashed SuperSU v2.82 and everything is golden. Note that I downgrade TWRP to RC1 for back up and restore, and use RC2 for all flashing.
I also did a full Titanium Backup to Google drive and also a full TWRP backup before any of this and copied to a flash drive as things happen.
The TWRP backup of the current correct unmodified boot.img has saved me a couple of times when I was away from the computer and did something to cause the phone to only boot to recovery. After restoring the backup just flash SuperSU again.
Click to expand...
Click to collapse
Thanks! I don't want to flash just the update though; I want to flash the entire release as I am going to be using the t-mobile version from now on. I think the only difference is it fixed the t-mobile glitch where wifi calls don't ring.
I do appreciate all the other advice though!
Anyone with any ideas to me original post, please keep them coming because I am desperate to learn!

daddylonglegs said:
Thanks! I don't want to flash just the update though; I want to flash the entire release as I am going to be using the t-mobile version from now on. I think the only difference is it fixed the t-mobile glitch where wifi calls don't ring.
I do appreciate all the other advice though!
Anyone with any ideas to me original post, please keep them coming because I am desperate to learn!
Click to expand...
Click to collapse
I just want to make sure I was clear. I flash the entire "release", if by release you mean not the OTA but the full large firmware.

Not sure why you want to do it this way, maybe I am missing something. Just download the full factory image for t mobile and use the flash all bat file. If you want to save your data and apps edit it and remove the -w from it.
That flashes everything and does it correctly.

TonikJDK said:
Not sure why you want to do it this way, maybe I am missing something. Just download the full factory image for t mobile and use the flash all bat file. If you want to save your data and apps edit it and remove the -w from it.
That flashes everything and does it correctly.
Click to expand...
Click to collapse
Well I looked inside the text files and it doesn't look like the command flashes literally everything. But maybe I'm wrong?
Also I don't want to lose root or lock my bootloader.

daddylonglegs said:
Well I looked inside the text files and it doesn't look like the command flashes literally everything. But maybe I'm wrong?
Also I don't want to lose root or lock my bootloader.
Click to expand...
Click to collapse
It does everything. You wont relock it unless you yourself issue the fastboot command to lock it. Yea, you will loose root which takes two minutes to do.
If you just want to update use FlashFire from Chainfire and use it to install the ota file feom Google. Me, I just flashall after removing the -w from the flashall bat file and the reroot.

Can't boot into fresh custom rom anymore -> keeps booting recovery (TWRP)

I was running OdexLite V4.2 but I was having some issues. I thought this was caused because I flashed it over my Marshmallow rom. So I flashed the latest available S6 edge official firmware from sammobile (G925FXXU5EQI6_G925FPHN5EQI2_PHN) and after that I fully booted the phone and shut it down. Then through Odin I flashed TWRP (twrp-3.1.1-0-zerolte.img.tar) and tried to install OdexLite again. I tried V4.2, V4.1, V4.0 but all of them kept rebooting me back into recovery. No matter what I tried. I haven't tried another ROM yet, tried to download NOBLE NOUGAT S8 PORT 5.1 but I don't have an Telegram account. I can't seem to find a download link without having to use my phone number.
What can be the cause of my phone to keep rebooting into the recovery? I already used V4.2 (till this morning) and it always worked. I redownloaded the file (V4.2 and TWRP) but that didn't change anything. Then I flashed back to stock Marshmallow like before, fully booted the system, shut down and install TWRP again. And then tried to flash V4.2 (and after that V4.1 and V4.0) but still my phone keeps rebooting into recovery after finishing the ROM. I tried various options in the aroma installer (stock choices and the same choices I made the first time when it worked)
I did a full erase (erase everything) and then copy the files through TWRP to the phone and flash it. And erased everything and used an OTG stick with the files to flash. I tried factory reset, wipe cache, etc. after the phone reboots back into recovery after the installation.
What's going wrong?? Please help me I don't know what else to try...

No, only the ROM files

rifek4 said:
That's maybe why...
Click to expand...
Click to collapse
I also replied to you in the other topic, I didn't had to do it before and the install instruction don't mention to install root either. But today I found flashing root can be the solution (while it wasn't mentioned in the startpost)
But V4.2.3 fixes the recovery loop. I'm now going to try V4.1 and/or V4.0 with flashinh magisk afterwards to see if that solves the problem.
Links to the solution page (page 100)
https://forum.xda-developers.com/ga...lite-rom-920f-920i-925f-925i-t3550706/page100
But thanks anyhow, I didn't know that I had to flash that. I just followed the instructions to be sure I didn't skip anything important :good::good:

rifek4 said:
Because that isn't nothing new and every one user who flashing custom ROM's must know that every time after flash ROM we must flash ROOT
Click to expand...
Click to collapse
I have flashed a_lot_of_roms on many different phones and I almost never had to do this. The times I had to do this, it was always instructed in the install routine I had to. Never had a loop to recovery before. I guess it was luck? Especially because the exact same rom worked before without flashing root. But this was a first for me and I'm flashing roms since the MDA Compact
{
"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"
}
But I'm happy I've learned this today, wished I learned this already yesterday :silly: missed my sleep this night
(Nederlandse Pool?)

rifek4 said:
Yes, same for me, I modding phone since 2006/7 year then we did mainly Sony Ericsson's and Nokia modding, later was more... If you Google my nick names "Leito07" with "Sony", "Nokia" word then you will see my first mods, sometimes there even are files from almost 10 years ago, look HERE: http://www.topsony.com/forum/showthread.php/18057-SquaSh-WBXML-Acoustic-by-Leito07
But on currently models like S6 with custom 7.0 FW for example we always must flash ROOT to patch boot image, otherwise phone will give us bootloop...
P.S.
Yep, you? Nederlandse Dutch misschien? :laugh:
Click to expand...
Click to collapse
Nice! Haha
P.S.
Nee geen probleem, enkel nieuwsgierig haha. Ik gewoon Hollandse Hollander. Geen Turkse, geen Poolse, gewoon lekker standaard :laugh:

rifek4 said:
Jaaaa... Zo standaard niks... Ik weet dat je alle racisten bent, maar we praten niet over het hier...
Click to expand...
Click to collapse
Haha uiteraard. Nee gewoon een brave Nederlander. Wel fan van Poolse vrouwen

rifek4 said:
Because that isn't nothing new and every one user who flashing custom ROM's must know that every time after flash ROM we must flash ROOT
Click to expand...
Click to collapse
That's false. You don't need to flash root, only roms that need that, like Noble.

Markos said:
I was running OdexLite V4.2 but I was having some issues. I thought this was caused because I flashed it over my Marshmallow rom. So I flashed the latest available S6 edge official firmware from sammobile (G925FXXU5EQI6_G925FPHN5EQI2_PHN) and after that I fully booted the phone and shut it down. Then through Odin I flashed TWRP (twrp-3.1.1-0-zerolte.img.tar) and tried to install OdexLite again. I tried V4.2, V4.1, V4.0 but all of them kept rebooting me back into recovery. No matter what I tried. I haven't tried another ROM yet, tried to download NOBLE NOUGAT S8 PORT 5.1 but I don't have an Telegram account. I can't seem to find a download link without having to use my phone number.
What can be the cause of my phone to keep rebooting into the recovery? I already used V4.2 (till this morning) and it always worked. I redownloaded the file (V4.2 and TWRP) but that didn't change anything. Then I flashed back to stock Marshmallow like before, fully booted the system, shut down and install TWRP again. And then tried to flash V4.2 (and after that V4.1 and V4.0) but still my phone keeps rebooting into recovery after finishing the ROM. I tried various options in the aroma installer (stock choices and the same choices I made the first time when it worked)
I did a full erase (erase everything) and then copy the files through TWRP to the phone and flash it. And erased everything and used an OTG stick with the files to flash. I tried factory reset, wipe cache, etc. after the phone reboots back into recovery after the installation.
What's going wrong?? Please help me I don't know what else to try...
Click to expand...
Click to collapse
Make sure the ROM your flashing is ROOTED, if not ROOT is yourself and try again.

Reflash Stock fails with mismattached carrier ID and failure to verify dmverity

Hi,
i tried to reflash stock on my Galaxy S8+ G955F after having issues with flasing the latest Renovate ICE Rom (Android 8) with Magisc, which did not install., I read in another thread that Magic can fail to install when having SuperSU before which I had in the beta of that ROM, and the solution would be to reflash Stock and unroot. This is WHY I did it.
I downloaded from sammobile and flashed with ODIN. In another thread I found out that the dmverity problem could be fixed with removing the cache.img out of the CSC; which i did try, but with no effect.
I am guessing that the carrier mismatch is the actual problem. I have a german phone and I selected germany on the sammobile so I am not sure how there can be a mismatch.
I also tried to reflash TWRP but it wont go into TWRP which I guess might be because of OEM lock reactivated through stock rom flashing.
Anyone knows how I could proceed from here?
Thanks!
{
"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"
}

I will do some research

For my country there is only the Android 7 stock rom available. The custom rom I flashed before was Android 8 so could this be a problem? I am not sure if it will make things worse if I flash one of the available Android 8 versions with "wrong" CSC.

unimatrix27 said:
For my country there is only the Android 7 stock rom available. The custom rom I flashed before was Android 8 so could this be a problem? I am not sure if it will make things worse if I flash one of the available Android 8 versions with "wrong" CSC.
Click to expand...
Click to collapse
im worried I bricked my phone. Is there a way to unlock the bootloader without being able to boot the phone? so that way i could maybe use TWRS again and try a custom rom? I cant use fastboot as I can only go into download mode or in the stock recovery. Is this even the right place to ask about a solution? Im totally desperate. Thanks!

Jessooca said:
Did you get your phone fixed yet? I had a couple people PM me over the past couple weeks with the same issue, both phones work fine now. PM me if you still need your phone fixed.
If not, good stuff, have a great weekend
-Jessica
Click to expand...
Click to collapse
I managed to boot the phone into stock a few minutes ago. I dont know how i did it. I applied "Factory Reset" and "Wipe Cache" a few times and then it did boot. I did then check that OEM unlock is enabled, whcih it still was. I then tried to flash TWRP again, ending up with the same problem, that TWRP would simply not start and trying to start it just gives me the constant Boot logo (the one you see first after turning the device on) and obviously with TWRP now on it, the stock would not boot any more, so I reflashed stock, and now back to square 1. Factory Reset and Wipe cache have not worked so far.

Update:
I am able to get stock rom to work. No matter which version of ODIN I use and which exact stock rom image, the result is always the same: The normal update process failes with the messages according to my initial screenshot. Then, when doing factory Reset and reboot, it fails again. Repeating those steps (Factory Reset and Reboot) multiple times eventually works and the ROM boots up. This is good in terms of a phone on stock rom is better than a bricked phone. I am still wondering if that might even be a hardware issues which does not let me update it just in a normal way. Or something with EFS, no idea.
Unfortunately I am NOT able to get TWRP to work. I am simply checking that OEM unlock is enabled and then i flash using ODIN / AP the latest (also tried some older version) TWRP - the latest version is twrp-3.2.1-0-dream2lte.img.tar. This leads to the phone neither booting to TWRP (holding VolUp, Bixby and Power) nor to boot normally any more. And this means I have to redo the above steps to flash Stock rom again, which takes 1-2 hours every time.
Again, stock rom is better than bricked, but really I would like to go back to rooted custom rom to be able to use Titanium backup and other stuff.

I dont know why, but after several attempts to flash TWRP I managed to get it running and with that part done it was no problem to install Custom ROM and everything works now. Thanks for your help!