Database Info

[ROM] Tab 3 7.0 SM-T210/R Stock 4.4.2 KitKat Update

This is the stock US KitKat ROM for The Galaxy Tab 3 7" Tablet. Finally found it after a bunch of hassle online, and figured I'd post it here to make things easier for everyone.
When I Odin'd this ROM, it actually upgraded my tablet, and left all my items installed (not guaranteeing this will work the same for everyone else).
Afterwards, I just Odin'd TWRP to reroot using Chainfire's SuperSU (no other Superuser would work) and called it good.
Caution: if you are using a custom ROM, this may not work without reflashing stock 4.1.2 since the 4.4.2 ROM appears to be an update, rather than a full ROM.
Rooted devices and custom kernels that are otherwise stock should be fine.
The cache, and if possible dalvik-cache should be cleared before flashing. Some of those files can sometimes interfere with upgrades.
It might be necessary to pinpoint apps that are force closing, uninstall and reinstall them. Some apps, particularly paid apps, store their data differently on KitKat, and will automatically fail as a result.
If that fails, it might be necessary to factory reset the device.
The Stock 4.1.2 ROM for the T210R is available here: http://forum.xda-developers.com/gal...-stock-sm-t210r-4-1-2-jellybean-odin-t2958676
The T210R...XAR file is for the 210R:
https://drive.google.com/open?id=0B2iEgzRTFjrQTmI0ZjRBbWtOajQ&authuser=0
The ITV file is for the T210 (no R)
To download these ROMs, a torrent client is required (such as utorrent).
Anyone who wishes to contribute, please seed if you can after downloading ("Force Starting" the torrent will seed it indefinitely.)

Can I flash this on the SM-T210?

john410 said:
Can I flash this on the SM-T210?
Click to expand...
Click to collapse
I've seen both devices referenced together quite regularly, implying that they use the same ROM.
http://www.boeboer.com/samsung-galaxy-tab-3-7-sm-t210r-manual-guide-wifi/
And even use the same kernel from what I've read:
http://forum.xda-developers.com/showthread.php?t=2439564
I would take standard precautions, such as having a odin image of your original software available and performing a backup of your current system (if able).
Perhaps someone else has some insight to this question?
edit: Looks like I had my information wrong. Found where I obtained the ROM from, it is for the T210R model, and was not intended for the T210.
There are custom ROMs that have been patched for use on both devices, which is where my confusion came from, but this is an official ROM.
I have gotten my hands on the T210(no R) ROM file, and have update the Links above.
I am not responsible for any failed attempts at flashing to either device.

Greaper88 said:
I've seen both devices referenced together quite regularly, implying that they use the same ROM.
http://www.boeboer.com/samsung-galaxy-tab-3-7-sm-t210r-manual-guide-wifi/
And even use the same kernel from what I've read:
http://forum.xda-developers.com/showthread.php?t=2439564
I would take standard precautions, such as having a odin image of your original software available and performing a backup of your current system (if able).
Perhaps someone else has some insight to this question?
edit: Looks like I had my information wrong. Found where I obtained the ROM from, it is for the T210R model, and was not intended for the T210.
There are custom ROMs that have been patched for use on both devices, which is where my confusion came from, but this is an official ROM.
I have gotten my hands on the T210(no R) ROM file, and have update the Links above.
I am not responsible for any failed attempts at flashing to either device.
Click to expand...
Click to collapse
First, thanks for this. I have the T210R. I tried using this and had the same result, it updated the tablet instead of loading a completely new version. I did however run into a problem...the tablet had many for closes and reboots to a point it was unusable and so I reverted back to my backup. Did you see this? Maybe I had a bad download?

[email protected] said:
First, thanks for this. I have the T210R. I tried using this and had the same result, it updated the tablet instead of loading a completely new version. I did however run into a problem...the tablet had many for closes and reboots to a point it was unusable and so I reverted back to my backup. Did you see this? Maybe I had a bad download?
Click to expand...
Click to collapse
I did not have this problem, but I didn't have much on my Tab either. (Some apps don't play well with KitKat upgrades.)
Torrents have multiple segmented hashchecks to make sure you get an uncorrupted download, but it might still be possible. I'm reasonably sure my file is OK since I've used it (can't speak for the non R file though).
Did you clear your cache, and if possible your dalvik cache? I've read that some of those files interfere with upgrades.
If you can pinpoint the apps that are force closing, uninstall and reinstall them. Some apps, particularly paid apps, store their data differently on KitKat, and will automatically fail as a result.
Other option would be to try a factory reset and see if that fixes it. (I understand not wanting to do that though.)
One more thing, if your ROM isn't stock, or stock rooted (custom kernel should be ok too), you may have to flash 4.2 before the 4.4 ROM will work on the device.

Right guys, here i go, just joined and first question!!!
i have not ever rooted a sm-t210 but it was rooted when i bought it second hand!
i have linux installed on my p.c. and was wondering if there is a way to upgrade to and official KITKAT!
as stated i am having problems because my SM-T210 wifi only! and want to update to kitkat official release!
but was hoping also that there is a way/method to root via LINX and not via windows!!
if that is not possible how do i go about it on windows!! as i can use a friends WINDOWS-P.C. if i must!
ah also my SM-T210 does not have the options to change the function of the USB-function,,,
i.e.
it used to have an option to,, use as a mass storege, media transfer or use with samsung keis,,, or some thing of the sort
but this option has dissapeared! may have been my fault!!!! as i uninstalled some system apps,
now it crashes and reboots whenever i try to turn of USB-DEBUGGING options in DEVELOPER-OPTIONS !!!!
many thanks in advance,
Void.Naught

void.naught said:
Right guys, here i go, just joined and first question!!!
i have not ever rooted a sm-t210 but it was rooted when i bought it second hand!
i have linux installed on my p.c. and was wondering if there is a way to upgrade to and official KITKAT!
as stated i am having problems because my SM-T210 wifi only! and want to update to kitkat official release!
but was hoping also that there is a way/method to root via LINX and not via windows!!
if that is not possible how do i go about it on windows!! as i can use a friends WINDOWS-P.C. if i must!
ah also my SM-T210 does not have the options to change the function of the USB-function,,,
i.e.
it used to have an option to,, use as a mass storege, media transfer or use with samsung keis,,, or some thing of the sort
but this option has dissapeared! may have been my fault!!!! as i uninstalled some system apps,
now it crashes and reboots whenever i try to turn of USB-DEBUGGING options in DEVELOPER-OPTIONS !!!!
many thanks in advance,
Void.Naught
Click to expand...
Click to collapse
I do know that Heimdall is a multiplatform flashing tool substitute for Odin. Check out
http://forum.xda-developers.com/galaxy-tab-3/general/root-sm-t210-r-using-heimdall-t2936061
for more info. Hope it helps.

thank you for finding and posting the correct files for this tab

hi i have a galaxy tab kid t2105 rooted, is it possible to install any other rom after 4.1.2?

Greaper88 said:
Rooted devices and custom kernels that are otherwise stock should be fine.
Click to expand...
Click to collapse
Just to triple check, by the above quote you mean that if my tablet is currently rooted, I should still be fine to flash this update correct? [obviously it would become non-rooted once flashed and I'd have to re-root it as you mentioned you rooted after installing]
Also, how much space does this take up?
thanks
~J

ubuntujason said:
Just to triple check, by the above quote you mean that if my tablet is currently rooted, I should still be fine to flash this update correct? [obviously it would become non-rooted once flashed and I'd have to re-root it as you mentioned you rooted after installing]
Also, how much space does this take up?
thanks
~J
Click to expand...
Click to collapse
That is correct. I was rooted running the Werewolf custom OC kernel. I still had my tablet upgrade without wiping, and one other user has reported back saying the same. But I can not promise upgrade as opposed to overwrite.
The flash file once extracted, is about 1.4 GB, I don't know sizes beyond that. It does not repartition the tablet however.

Greaper88 said:
That is correct. I was rooted running the Werewolf custom OC kernel. I still had my tablet upgrade without wiping, and one other user has reported back saying the same. But I can not promise upgrade as opposed to overwrite.
The flash file once extracted, is about 1.4 GB, I don't know sizes beyond that. It does not repartition the tablet however.
Click to expand...
Click to collapse
Awesome, thanks!
~J

Could you upload the T210 ITV file? This torrent is going to take 10 hours

No system file
Well this is awesome, system won't mount and I don't have a backup. Samsung website does NOT have the stock firmware, and attempting to get it for another country just to get this to load so I can flash a ROM leaves me with having to download at 15kbs. I am in the process of selling this to someone for their kid... And there are ZERO seeders for these files. Lovely.

Sorry, m'y post an error

ragnaroksangel said:
Well this is awesome, system won't mount and I don't have a backup. Samsung website does NOT have the stock firmware, and attempting to get it for another country just to get this to load so I can flash a ROM leaves me with having to download at 15kbs. I am in the process of selling this to someone for their kid... And there are ZERO seeders for these files. Lovely.
Click to expand...
Click to collapse
Are you looking for the Stock Rom?

Darthlord064 said:
Are you looking for the Stock Rom?
Click to expand...
Click to collapse
I am, can you help?

Greaper88 said:
I do know that Heimdall is a multiplatform flashing tool substitute for Odin. Check out
http://forum.xda-developers.com/galaxy-tab-3/general/root-sm-t210-r-using-heimdall-t2936061
for more info. Hope it helps.
Click to expand...
Click to collapse
For some (unknown) reason, Odin3 nor JOdin3 doesn't seem to work for flashing my Samsung Galaxy Tab3 device. For that reason I tried Heimdall-Frontend, but to make that work you need to extract the content of a stock ROM first.
Anyways, it still didn't lead to get my device into factory reset yet.
But that's another story on which I still have not yet found the answers needed to get the device successfully back into factory reset.
My guess is that the 'system.img' file, of Android 4.4.2, successfully has been loaded from Heimdall-Frontend, yet by going into reboot right away after Heimdall-Frontend releases the connected device, the download may be deleted.
I read that the cause of that may lie in the fact that Android 4.4.2 is only an update and no full ROM.

I'm stuck

Hi guys,
for some reason after I did update to KangVIP I can't get rid off it. Besides I got no wifi and bt and I was going to start over with b023 as suggested but at this point I wont bother anymore.
I did wipe the system, I did advanced wipe using twrp but no matter what I do none of the stock firmwares are going through however the Kanga one always goes through.(KangaVIP goes through only in TWRP)
twrp 2.8.7.0
wipe
advanced wipe
I select all the partitions
mkdosfs process ended with error=1
unable to wipe /usb
unknown mtp message type: 1
unable to wipe /usb
I go back, restart to fastboot, (device is saying there is no OS installed), I restore the recovery, create dload folder on my sdcard, put there 028 (actually I tried all of them already), volume+ volume - power and I get error.
What am I missing ?
Anyone can help ?
Thanks in advance.
Eric

First you did a OTA from B029 to B209?
If so you are now on a Android 6 ROM you cant go back to Android 5 without a Rollback from Huawei.

Hirs_E_Fruit said:
First you did a OTA from B029 to B209?
If so you are now on a Android 6 ROM you cant go back to Android 5 without a Rollback from Huawei.
Click to expand...
Click to collapse
Yes I did then I wiped everything and started with b028 again.
Same thing, wifi didn't work same with BT.
Wipe again and this time I did local update and since the local update I can't go back not even b029.

77Eric77 said:
Yes I did then I wiped everything and started with b028 again.
Same thing, wifi didn't work same with BT.
Wipe again and this time I did local update and since the local update I can't go back not even b029.
Click to expand...
Click to collapse
Right now you are on a Android 5 or Android 6 ROM?
If you on a Android 5 ROM you can force update a Complete ROM to install a clean system and try if everything works.

Hirs_E_Fruit said:
Right now you are on a Android 5 or Android 6 ROM?
If you on a Android 5 ROM you can force update a Complete ROM to install a clean system and try if everything works.
Click to expand...
Click to collapse
I'm stuck on 6.0
I know I can do force update on 5.0 I said it above I just can't do it with 6.0 -> b029, only with your rom.

Anyone else is having this issue ?
The Kanga rom got a quite few problems no wifi and not BT, Google play services crashing (this can be fixed with gapps) my co worker just tried it with his own methods and same issue. After I went through the whole Kanga thread 60% of the posters got problems most of them are ignored.

I don't have any problems but I think the people with problems are people who have a DAV 701L.

Hirs_E_Fruit said:
Right now you are on a Android 5 or Android 6 ROM?
If you on a Android 5 ROM you can force update a Complete ROM to install a clean system and try if everything works.
Click to expand...
Click to collapse
Hirs_E_Fruit said:
I don't have any problems but I think the people with problems are people who have a DAV 701L.
Click to expand...
Click to collapse
I got DAV-703L, just simple question, why is the wifi and bt not working ?
When I get into Kanga I can remove the root or deny access to it is there a way to ditch it ?
Yeah I know it's working for you and it's not working for 10 other people including 703L owners. There is something wrong with the rom no doubt about it.

77Eric77 said:
I got DAV-703L, just simple question, why is the wifi and bt not working ?
When I get into Kanga I can remove the root or deny access to it is there a way to ditch it ?
Yeah I know it's working for you and it's not working for 10 other people including 703L owners. There is something wrong with the rom no doubt about it.
Click to expand...
Click to collapse
I think there was an error while flashing and without a full clean Rom flash i can't see a solution.
Before I got it to work I flashed it more than 3 times and everytime everything worked so I think don't think the ROM is that bugged.

Hirs_E_Fruit said:
I think there was an error while flashing and without a full clean Rom flash i can't see a solution.
Before I got it to work I flashed it more than 3 times and everytime everything worked so I think don't think the ROM is that bugged.
Click to expand...
Click to collapse
The first rom you introduced is working "fine" I get the wifi and bt no problem but once I switch into the latest build it's gone.
Any idea where can I get full clean Rom ?
This one is a no go http://www.needrom.com/download/p8max-dav-703l/

I managed to rollback to 5.1.1 but when I try to force flash it, it says it's not compatible.

If you don't update properly to B209, when you flash any B209 rom you are going to run into issues such as the wireless Bluetooth and sim card switching for some. If you properly updated the dload method should have completed successfully. Look at the kernel and radio version of B209 in About phone and compare it to others and see if they match.

ajsmsg78 said:
If you don't update properly to B209, when you flash any B209 rom you are going to run into issues such as the wireless Bluetooth and sim card switching for some. If you properly updated the dload method should have completed successfully. Look at the kernel and radio version of B209 in About phone and compare it to others and see if they match.
Click to expand...
Click to collapse
I don't want to use your rom even if you removed the Chinese it's still inside the system. Boot load times take much longer. Unexpected crashes. I did try it on 4 phones with OTA and local updates 2 are working but the Kang does crash twice a day minimum.
All what I'm asking is how to restore it to it's original settings, this was my worst mistake ever.
What I'm trying to say if I do something I do it properly just look at your thread 85% failure ratio that doesn't look like it was done properly does it ?

77Eric77 said:
I don't want to use your rom even if you removed the Chinese it's still inside the system. Boot load times take much longer. Unexpected crashes. I did try it on 4 phones with OTA and local updates 2 are working but the Kang does crash twice a day minimum.
All what I'm asking is how to restore it to it's original settings, this was my worst mistake ever.
What I'm trying to say if I do something I do it properly just look at your thread 85% failure ratio that doesn't look like it was done properly does it ?
Click to expand...
Click to collapse
Really dude?? No worries, it will be the last time I do anything for the P8Max. Maybe you should just sell the phone since you're having all sorts of issues with it....or maybe you should have left it totally stock then. Or maybe read through the Mediapad X2 forums because the two phones are very similar.

[6045O] Attempting to upgrade to Lineage 13

Alright, This is just because I am trying to take precautions so that way I do not end up with a brick.
Currently I am rocking 5.1 PAC-MAN and things are going well. But LineageOS for MM for 6045 came already and I want to use that as my daily driver.
Here is where I run into a problem. For those of you that know I only have LP radios and modems on my system. Main problem I am having and is keeping me from flashing is the lack of a MM radio and or modem. Is there anyone that is on 6045O that had tried this out without having that lockscreen problem?

If you don't flash the MM radios, you will end up with lock screen issues, unfortunately.
-EDIT-
So apparently I can't read. I have the 6045O and this link has the correct modem files to fix the lock screen issues.
https://mega.nz/#F!u0UBAICD!DzKYnswfK5J6dw5WQNgEDg
6.0.1 modem is the file you need.

magus7091 said:
If you don't flash the MM radios, you will end up with lock screen issues, unfortunately.
-EDIT-
So apparently I can't read. I have the 6045O and this link has the correct modem files to fix the lock screen issues.
https://mega.nz/#F!u0UBAICD!DzKYnswfK5J6dw5WQNgEDg
6.0.1 modem is the file you need.
Click to expand...
Click to collapse
Attempted. Everything but the pin issue is good. Weird how it trips badly with the PIN. Installing SuperSU as we speak.
EDIT: Looped after SuperSU flash..
EDIT2: Going back to 5.1. Thank you very much for the support.

Huskied said:
Attempted. Everything but the pin issue is good. Weird how it trips badly with the PIN. Installing SuperSU as we speak.
EDIT: Looped after SuperSU flash..
EDIT2: Going back to 5.1. Thank you very much for the support.
Click to expand...
Click to collapse
While playing around with ROMs for the phone I had some odd issues here and there. As far as the SuperSU flash, it almost always loops a couple times during the reboot process, but I've switched to the lineageOS official su addon because I like native support and root management. Also it never did those initial boot loops. When I did have an issue (just recently, in fact) I ran a wipe of the system partition, then installed the rom, and ran the repair file system option in TWRP, and since then it's been smooth as butter. If you're interested in giving it another go, just let me know and I should be able to link you the files, as they're on my google drive.

magus7091 said:
While playing around with ROMs for the phone I had some odd issues here and there. As far as the SuperSU flash, it almost always loops a couple times during the reboot process, but I've switched to the lineageOS official su addon because I like native support and root management. Also it never did those initial boot loops. When I did have an issue (just recently, in fact) I ran a wipe of the system partition, then installed the rom, and ran the repair file system option in TWRP, and since then it's been smooth as butter. If you're interested in giving it another go, just let me know and I should be able to link you the files, as they're on my google drive.
Click to expand...
Click to collapse
May I ask one more thing? Have you ever gotten the PIN lock or password or pattern lock to work?
EDIT: Nvm. Using Hi-Locker for now. All is good.

I use a pattern lock on mine, and after flashing the modem files, the lock screen functions as it should with all methods. Consider re-flashing the modem and ROM if you get to where you want to play with it, full wipe prior, no dirty flash.

Has Anyone Gotten a Custom ROM onto a BLN-L24 (US Variant)?

I have tried quite a few ROMs, and all ended up going back to stock firmware because they wouldn't boot. I know I have to format data, and some ROMs ask you to change the data partition as f2fs.
Still, I think that there may be no ROMs that currently work for the US variant. One guy said LOS 13 worked, but when I flashed it, it failed. If someone has gotten it to work, can you please post as many steps as you remember on how to get it work?

Debrand to BLN-L21 following this guide and you're ready to flash cooked ROMs https://forum.xda-developers.com/honor-6x/how-to/guide-successful-debranding-to-bln-t3701050

RedSkull23 said:
Debrand to BLN-L21 following this guide and you're ready to flash cooked ROMs https://forum.xda-developers.com/honor-6x/how-to/guide-successful-debranding-to-bln-t3701050
Click to expand...
Click to collapse
Thanks, but wouldn't there be more issues down the line with a debranded phone? What if I soft-bricked my phone, it seems like it'd be really hard to restore? Has anyone actually ever done this on a BLN-L24?

Hello all,
I too am having issues with flashing roms to this device, US variant (BLN-L24). In my particular case, the rom boots up (EliteRom v7.1) and will actually function. However, wifi does not work, as well as I have no sound whatsoever. Youtube also will not play, nor will any videos, which I'm guessing is tied to whatever issue is with the sound. I have flashed multiple times per the step by step instructions, as well as following the Youtube video, all with the same result over the last few days. At this point, my phone is effectively useless to me, though cellular data does still work, just no calls can be answered. Anyone have any suggestions I might be able to follow? Also, even my TWRP backup that I made before installing the rom will not restore at this point. Any help is appreciated, thanks.

Jessooca said:
You must be missing a step or something, because [Elite ROM][EMUI 5.1] Elite ROM v7.1 for Honor 6X by HassanMirza01 works on the L24 us variant without issues, I have none.
Perhaps go back to stock and start over. I haven't had any issues with his rom and I didn't do anything more than what's needed to root/install twrp and flash the rom per his instructions.
Click to expand...
Click to collapse
I just followed the instructions; I believe to the best I could, and I'm stuck in a bootloop now. Which version of EMUI were you on before flashing? I was on EMUI 5.0 which may be my issue.
I started from EMUI 5.0
Unlocked my bootloader
Let it factory reset
Installed the Elite TWRP on the page
Booted to Elite TWRP
Formatted all partitions excpet for external sd card
Reformatted Data to f2fs
Re-wiped data
Checked that it was f2fs
Installed Elite ROM zip
Installed open gapps 7.0 ARM64
Installed the patch
Rebooted
Bootloop

i4ybrid said:
I just followed the instructions; I believe to the best I could, and I'm stuck in a bootloop now. Which version of EMUI were you on before flashing? I was on EMUI 5.0 which may be my issue.
I started from EMUI 5.0
Unlocked my bootloader
Let it factory reset
Installed the Elite TWRP on the page
Booted to Elite TWRP
Formatted all partitions excpet for external sd card
Reformatted Data to f2fs
Re-wiped data
Checked that it was f2fs
Installed Elite ROM zip
Installed open gapps 7.0 ARM64
Installed the patch
Rebooted
Bootloop
Click to expand...
Click to collapse
On one of the attempts that I did for installing, I installed the patch and it put me in a boot loop. Maybe not installing the patch can help you?

I cant get anything to work for the US version. Sure stuff boots but some of it is just broken. On octOS i am unable to use root unless i switch supersu to automatically grant root to apps. I cant get root access by using prompt because nothing pops up. On crdroid i have the same exact issue. Id rather have the prompt than allow any app root access without my knowledge. With ELITE ROM my first boot brings up a home screen with no keyboard. It completely skips any kind of setup screen. I can get the setup screen by flashing a keyboard from an aroma gapps installer but then i lose google services. The US version also seems to be forgotten as for most roms you wont see it anywhere under supported lists.

I've never been able to get a custom rom to work on my BLN-L24. Everything just ends in a never-ending bootloop of frustration.
Though, I have only ever tried with EMUI 5.0+. Maybe an earlier version of EMUI gets better results...?

code_name_duchess said:
I've never been able to get a custom rom to work on my BLN-L24. Everything just ends in a never-ending bootloop of frustration.
Though, I have only ever tried with EMUI 5.0+. Maybe an earlier version of EMUI gets better results...?
Click to expand...
Click to collapse
It really sucks that nothing seems to work. Ive tried flashing using multiple recoveries and ive tried all kinds of flashing to fix issues with the ROMS. Nothing helps. If anyone has successfully gotten a ROM fully working on BLN-L24 they need to tell people exactly what they did step by step.

It seems that for the roms located here, they seem to all assume that the phone has been debranded to bln-l21 variant. I don't know if it has any bearing on the current issues we're all experiencing, but I did notice that all twrps available for this device on the forums state they are the "Open Kirin Edition". It's been a while since I've rooted or rom'd a phone besides this one, but I've never encountered a twrp with a custom name like that.
I know that the developer of the EliteRom had his custom twrp, but is there a different twrp besides that one that does not state it is an "Open Kirin Edition"? Like I said, not sure if it has any bearing on things here, but I've been very confused about that.

TurtlePwr82 said:
It seems that for the roms located here, they seem to all assume that the phone has been debranded to bln-l21 variant. I don't know if it has any bearing on the current issues we're all experiencing, but I did notice that all twrps available for this device on the forums state they are the "Open Kirin Edition". It's been a while since I've rooted or rom'd a phone besides this one, but I've never encountered a twrp with a custom name like that.
I know that the developer of the EliteRom had his custom twrp, but is there a different twrp besides that one that does not state it is an "Open Kirin Edition"? Like I said, not sure if it has any bearing on things here, but I've been very confused about that.
Click to expand...
Click to collapse
For most phone i've ever owned you never had to change the recovery for each ROM. Its confusing. Most recoverys say Open Kirin Edition when booting. What confuses me is why we need to debrand to get the ROMS to work. If the phone pretty much run on the same hardware then why is L24 having so many issues? Why are the devs not testing on these devices?

BakedOnSomeSour said:
For most phone i've ever owned you never had to change the recovery for each ROM. Its confusing
Click to expand...
Click to collapse
Right, that's what I was thinking. For any phone I've ever rom'd, there was always just one twrp that everyone worked from.
Edit: found this while looking through the roll back to stock forum. I don't know if it will help anyone else, but figured I'd put it here as well if it might. All credit for this goes to the original poster johnnyrichter:
johnnyrichter said:
Tried this method after being on LineageOS for a week or two and having poor LTE signal, no MMS, and voicemail issues so I'm trying to go back to stock so I can have a fully functional phone since I rely on it heavily for work. Followed all steps using BLN-L24 B360 firmware. On step 10 I rebooted to update and it went right to "5% Installing Update" and stuck there for 5 mins, then rebooted itself, has been sitting at "honor" boot screen for 14 minutes so I made it reboot to EMUI recovery, wiped/factory reset, rebooted, loaded EMUI afte 2 more minutes. Appears to have worked and hopefully my issues are fixed!
Edit: Signal, mms, and voicemail issues fixed.
Click to expand...
Click to collapse
Hopefully will benefit someone here as well.

When debranding the BLN-L24, and branding it to BLN-L21, are there any issues with the ROMs once they're installed? I imagine the radios, and such are different for the two models??

BakedOnSomeSour said:
Why are the devs not testing on these devices?
Click to expand...
Click to collapse
Devs can only test devices they have in possession. If they don't have your phone model, how are they going to test it?

galapagos said:
Devs can only test devices they have in possession. If they don't have your phone model, how are they going to test it?
Click to expand...
Click to collapse
well, many don't want to give them a phone because most developers here tend to stop work on a ROM and leave people hanging.

I have gotten several ROMs working on L24 variant...
Yes it seems to me any Elite kernel based ROM works or should work on the L24. But /data must be ext4 format. Then even that the ROM works, the fingerprint scanner never allows a complete successful scan. I think because it must be f2fs format for that encryption to work or something. This is the link to those ROMS https://hassanmirza01.blogspot.com/p/custom-roms.html?m=1
On the other hand the LOS based ROMs never work or at least they reboot and the screen is always black or the ROM branding just stays there flashing. This sucks cause I want to run the newest Resurrection ROM but I ask the developer about why I have that problem or how long that ROM takes to boot and I never get an answer. He also just put a new beta AOKP ROM up and it does the same black screen thing too.
I am also suspicious it has to do with the version of TWRP. I think some are capable of formatting f2fs correctly or the encryption or whatever. Point is some of the devs need to be a little more consistent answering questions at a minimum. I know it takes time to fix bugs but give us a little heads up.

SM-G955U - [Odin Issues] Attempting to Return to Factory Firmware (Phone works)

Hello everyone, looking for advice in how to return to factory firmware. First, a few bullets to condense the information, then an expanded explanation below. Any assistance would be appreciated.
TL : DR
-Xfinity Mobile GS8+, SM-G955U
-Phone boots and works fine
-When device was still on Nougat, the Oreo beta firmware update.zips were floating around
-Downloaded and installed via factory recovery said update.zips in succession
-Stuck on pre-release build, want to get back to official Verizon Firmware and receiving OTAs
-Current Build: R16NW.G955USQU2CRAD
-Desired Build: G955USQS5CRI4 (Verizon, 09.11.18)
-Tried flashing CRI4 package manually via Odin, Odin said no
-A few hours of Googling and reading through forums as etiquette demands I try first has led me to post this, never not been able to find a fix in the forums
-Plz help, will PayPal/GooglePay/whatever you a 12-pack of beer or whatever to whoever gets me back to factory
Things I've Tried:
-Factory reset
-Odin
-Smart Switch
-OTA
So I have a Galaxy S8+ purchased through Xfinity Mobile. I wasn't able to get into the Oreo beta officially offered through the Samsung Program, but there were update.zips floating around that allowed you to migrate to the pre-release builds. The samsung.firmware.science link above was relatively straightforward - pick your model, it had the latest official build, download an update.zip, and profit.
As the beta program progressed and various more final builds were released, these builds provided additional successive update.zips, until ultimately resting on what was the final version, build number R16NW.G955USQU2CRAD, which I am on currently. I use various forms of Package Disabler and had until recently kept a lot of Samsung's bloat disabled, including the OTA services. Note this only disables them and keeps them from running, not actually remove them from the phone.
Anyway, being an old ROM crackhead from back in the day when aftermarket ROMs actually provided significant software improvements over the garbage that OEMs ship on their phones, I don't like OTA updates that often because I prefer to factory reset after each update - the updates usually make the phone feel sluggish, which may be placebo, but here we are. In light of all the recent Android security vulnerabilities, despite not doing dumb stuff on my phone I figured it was time to go ahead and OTA to get the newest security patch. The issue is that my phone does not recognize any new OTAs despite being on a firmware build from January 2018.
I'm familiar with Odin, figure no big deal, grab the newest build for Verizon (Xfinity Mobile runs on Verizon towers, there's currently a Verizon sim in the device, and Xfinity Mobile builds seem to be entirely absent) and try to flash G955USQS5CRI4 dated 09.11.18. Verified through redundant sources this is, in fact, the latest Verizon build for the S8+.
Lo and behold, it doesn't work. Contacted Samsung regarding possible solutions, their chat agent wasn't very helpful, directed me to a local authorized repair store, who said they may or may not be able to flash it back with Samsung's software, and it requires what may be a two hour diagnostic that checks every possible thing it can on the device, and if it's not an official build, they will tell me to **** off, not withstanding the fact that the guy mentioned that the software from time to time glitches and crashes. My experience with flashing firmware makes me wary of what would happen during a system flash if the software crashes.
Anyway, for those of you who bothered to read past the TLR and embrace my dissertation, I've been out of the flashing game for a while, and because flashing factory firmware via Odin was my go to in the past, I'm not up to date on fixes for obscure issues. A few hours of Googling and reading through forums and I'm not anywhere closer than where I started, and I'd rather fix this myself rather than go to a store and potentially pay them for something that is "out of warranty."
Any ideas would be much appreciated, would gladly PayPal/Google Pay/Whatever someone a 12-pack of beer/$ to someone who can help me get this thing back to factory firmware.
Thanks in advance for any help.

From looking at your odin log almost looks like nothing was flashed, usually you will see abl.elf, modem, system.img, etc.... in the log while it's being flashed; After it checked the MD5 and started flashing it almost immediately closed it looks like but see no errors.
*After looking again I notice it says (success 0/fail 1) so it did not flash anything. Also make sure you are using the newest odin to flash
My suggestion, try flashing without USERDATA; When I flash I flash:
BL/AP/CP/CSC_OYM and not the HOME_CSC and never UserData
If that doesn't work try odin to G955USQU2CRC5 (Verizon 4/18) and then from there update to the latest update.

bmxmike said:
From looking at your odin log almost looks like nothing was flashed, usually you will see abl.elf, modem, system.img, etc.... in the log while it's being flashed; After it checked the MD5 and started flashing it almost immediately closed it looks like but see no errors.
*After looking again I notice it says (success 0/fail 1) so it did not flash anything. Also make sure you are using the newest odin to flash
My suggestion, try flashing without USERDATA; When I flash I flash:
BL/AP/CP/CSC_OYM and not the HOME_CSC and never UserData
If that doesn't work try odin to G955USQU2CRC5 (Verizon 4/18) and then from there update to the latest update.
Click to expand...
Click to collapse
Thanks for the response. I'm downloading the CRC5 file from Updato, and while the download speed is fluctuating, it's averaging around 50 KB/s with an ETA around 22~ hours. Is there a faster method to download this? I have a 300 Mb/s connection, so there's no bottleneck.
I'll try those steps in Odin, but can you expand on the reasoning so I understand the underlying mechanics? I was using the CSC_OYM and not the HOME_CSC, but why does this make a difference? Why never use USERDATA?

zerofighter1 said:
Thanks for the response. I'm downloading the CRC5 file from Updato, and while the download speed is fluctuating, it's averaging around 50 KB/s with an ETA around 22~ hours. Is there a faster method to download this? I have a 300 Mb/s connection, so there's no bottleneck.
I'll try those steps in Odin, but can you expand on the reasoning so I understand the underlying mechanics? I was using the CSC_OYM and not the HOME_CSC, but why does this make a difference? Why never use USERDATA?
Click to expand...
Click to collapse
I'm saying I have never flashed USERDATA as I've never seen it packed in most the roms I download, only other thing they have included is MAYBE a pit file for repartitioning. As for CSC:
Home_CSC: Flash the firmware without wiping the data (if you just want to update the ROM)
CSC: Flash the firmware along with a complete wipe including data (mostly used in cases like bricked phones or Go-Back-To-Stock situations)
I would try reflashing in download mode doing what I suggested and make sure that only reboot, nand erase, and f. reset are the only things checked.
As for downloads my suggestion is google try this:
site:androidfilehost.com G955USQU2CRC5
or
G955USQU2CRC5 filetype:zip (basing on the fact the roms I've downloaded all are zip format)
I think you can search from within the site, not sure. If you can find it always try download off filehost atleast I do because better speeds.

bmxmike said:
As for downloads my suggestion is google try this:
site:androidfilehost.com G955USQU2CRC5
or
G955USQU2CRC5 filetype:zip (basing on the fact the roms I've downloaded all are zip format)
I think you can search from within the site, not sure. If you can find it always try download off filehost atleast I do because better speeds.
Click to expand...
Click to collapse
https://forum.xda-developers.com/att-galaxy-s8+/how-to/g955u-stock-g955usqu2crc5-odin-files-t3773033
I managed to find this under AT&T SM-G955U thread, is this of any significance? Okay to flash?

zerofighter1 said:
https://forum.xda-developers.com/att-galaxy-s8+/how-to/g955u-stock-g955usqu2crc5-odin-files-t3773033
I managed to find this under AT&T SM-G955U thread, is this of any significance? Okay to flash?
Click to expand...
Click to collapse
Should have mentioned, the reason I'm asking is there is a discrepancy between the file size from Updato and this file - Updato file is 3.6~ GB and the one in this thread is 3.12~ GB.

No telling could be way it was compressed or files inside, like I said the rims I usually download don't include a USERDATA tar so maybe one has one and the other doesn't.
Have you tried again with what you have now?
There's been plenty of times I've tried to flash something to where I sometimes have to do it 3-5 times cause I over look something like under options (especially with resetting Odin cause when I do that it automatically enables partitioning for some reason). Also try a different USB cable, cause there should be something in Odin logs to lead you to problem; ex:
1 > 2 = This error usually means lower version Bootloader
Couldn't open file on XXXX: = Usually means partitioning was selected but no partition table given
Also if nothing else try flash in cosmey, I have yet to flash a v5 BL so I can't give you a this is what you need to do because my USB port is not working, but I've flashed from v1 to v3 in cosmey and have never had a issue with software only User Error (I'm trying to find a way to update from partycyborg to the same as you without Odin but cant because of my BL)

bmxmike said:
No telling could be way it was compressed or files inside, like I said the rims I usually download don't include a USERDATA tar so maybe one has one and the other doesn't.
Have you tried again with what you have now?
There's been plenty of times I've tried to flash something to where I sometimes have to do it 3-5 times cause I over look something like under options (especially with resetting Odin cause when I do that it automatically enables partitioning for some reason). Also try a different USB cable, cause there should be something in Odin logs to lead you to problem; ex:
1 > 2 = This error usually means lower version Bootloader
Couldn't open file on XXXX: = Usually means partitioning was selected but no partition table given
Also if nothing else try flash in cosmey, I have yet to flash a v5 BL so I can't give you a this is what you need to do because my USB port is not working, but I've flashed from v1 to v3 in cosmey and have never had a issue with software only User Error (I'm trying to find a way to update from partycyborg to the same as you without Odin but cant because of my BL)
Click to expand...
Click to collapse
Hey sorry, I've been busy working and haven't had the time to get back to this. I'm going to try this today and I'll get back to this post with an update.