Database Users

S4 i9506 Soft Brick

Hi All,
New to forum here and to Android *re-engineering* in general. Wife gave me a task: to remove the stock S4 OS and replace it with something better.
These are the steps I followed:
1. In Download mode, used Odin v3.10 to flash TWRP 3.02 recovery
2. Booted to Recovery Mode, it gets to TWRP recovery ROM properly.
3. Recovered to CM13 nightly builds and rebooted to System.
4. Boots to System with the following message:
KERNEL IS NOT SEANDROID ENFORCING
Set Warranty Bit: kernel
Samsung Galaxy S4
GT-I95016
After that it just stays stuck on the screen until I reboot into Download or Recovery Mode.
None of the CM13 OS downloads I used work so far. I've also tried to recover to CM11 after the initial problem, but it doesn't work. Note that there are no releases for this, only nightly builds. Tried for 2 weeks already and I think I probably need some help.
Any ideas?

zdfan said:
Hi All,
New to forum here and to Android *re-engineering* in general. Wife gave me a task: to remove the stock S4 OS and replace it with something better.
These are the steps I followed:
1. In Download mode, used Odin v3.10 to flash TWRP 3.02 recovery
2. Booted to Recovery Mode, it gets to TWRP recovery ROM properly.
3. Recovered to CM13 nightly builds and rebooted to System.
4. Boots to System with the following message:
KERNEL IS NOT SEANDROID ENFORCING
Set Warranty Bit: kernel
Samsung Galaxy S4
GT-I95016
After that it just stays stuck on the screen until I reboot into Download or Recovery Mode.
None of the CM13 OS downloads I used work so far. I've also tried to recover to CM11 after the initial problem, but it doesn't work. Note that there are no releases for this, only nightly builds. Tried for 2 weeks already and I think I probably need some help.
Any ideas?
Click to expand...
Click to collapse
The message during boot is normal if you've modified the Bootloader (in this case, by flashing the recovery).
By "recover" I assume you mean installed/flashed a ROM.
Are you flashing the right ROM for the model?
Did you wipe before flashing?

GDReaper said:
The message during boot is normal if you've modified the Bootloader (in this case, by flashing the recovery).
By "recover" I assume you mean installed/flashed a ROM.
Are you flashing the right ROM for the model?
Did you wipe before flashing?
Click to expand...
Click to collapse
Thanks for replying - ok good to know that message is normal.
1. Yes I flashed the TWRP recovery ROM.
2. In TWRP recovery mode I installed the custom ROM for cyanogenmod 13 for i9506, downloaded from the Builds in this link: __download.cyanogenmod.org/?device=ks01lte___ (copy paste the URL as I cannot post external URL yet)
3. Yes, wiped before flashing.

zdfan said:
Thanks for replying - ok good to know that message is normal.
1. Yes I flashed the TWRP recovery ROM.
2. In TWRP recovery mode I installed the custom ROM for cyanogenmod 13 for i9506, downloaded from the Builds in this link: __download.cyanogenmod.org/?device=ks01lte___ (copy paste the URL as I cannot post external URL yet)
3. Yes, wiped before flashing.
Click to expand...
Click to collapse
How much time did you wait for the phone to boot?
Have you tried other ROMs, from here on the forum?
There is a GT-I9506 section from where you can download various modified ROMs.

GDReaper said:
How much time did you wait for the phone to boot?
Have you tried other ROMs, from here on the forum?
There is a GT-I9506 section from where you can download various modified ROMs.
Click to expand...
Click to collapse
1. Waited up to 1/2 hr, same screen.
2. I've tried CM11 and CM13
3. Could you give an example?

zdfan said:
1. Waited up to 1/2 hr, same screen.
2. I've tried CM11 and CM13
3. Could you give an example?
Click to expand...
Click to collapse
I'm a GT-I9505 user, can't really recommend you anything.
There's AICP, various CM13 builds and others. Just look through the GT-I9506 section (here on the forum) until you find something promising.

Doesn't boot to TWRP recovery

So after having my phone being stuck in a boot loop (just restarted one day and has been in a boot loop since) , I figured the thing to do was to flash TWRP 2.8.7.0 (I had a solution that had rooted my phone without a custom recovery). After a successful flash, I go to recovery (up volume + Power) and it says recovery on the Samsung screen.
And then, it goes back into the boot loop.

Suggests as usual flashed wrong file for model .
See multiple identical posts .
But if it was a prexisting boot loop then go back to your other posts .
Sent from my SM-N930F using XDA-Developers Legacy app

JJEgan said:
Suggests as usual flashed wrong file for model .
See multiple identical posts .
But if it was a prexisting boot loop then go back to your other posts .
Sent from my SM-N930F using XDA-Developers Legacy app
Click to expand...
Click to collapse
Flashed twrp-2.6.3.1-hltetmo.tar successfully.
While its connected into my PC, it gets stuck at the T-mobile sign at full brightness.
When I unplug it, it goes back to a boot loop.

You want the TMobile forum not this one .
Sent from my SM-N930F using XDA-Developers Legacy app

Confirm the model # in download mode before flashing anything else.

Has there been solution for this one? I got n9005 and i can't get other than twrp 2.8.7.0 working, have tried different bootloaders but without luck. Only stock images what works are N9005XXUGNG1_N9005NEEGNG1_NEE(cant update to lollipop, stucks on bootloop) and N9005XXUGBOK6_N9005XEOGBOJ1_XEO. Also had luck with some unofficial cm13 rom.
I'am not that familiar with this samsung style of using odin instead of fastboot and adb so i'am litlle bit lost and just don't know what else anymore can i do to get working new twrp so i can install nougat.

What rom are you going to install.
Sent from my SM-N930F using XDA-Developers Legacy app

i tried official lineageos 14 hlte, it looks like installation goes fine with twrp 2.8.7.0 but phone wont boot. currently i have nordic bootloader and modem BL_N9005XXSGBQD1 and CP_N9005XXUGPQB1 and twrp 2.8.7.0 just tried to upgrade newer twrp from image file but same old bootloop again.
Could there be something wrong in filesystem? Is there some pit-file that i can try with my phone without risk of bricking it?
---------- Post added at 22:22 ---------- Previous post was at 22:06 ----------
btw, where does that charging icon come when phone is power off? my phone is just boot looping when powered off and i put charger on it.

Bootloop thats often wrong TWRP used .
Flash latest TWRP through TWRP or try Philz Recovery .

tried to install 3.1.1.0 from twrp 2.8.7.0. Install went fine without any errors but still not booting to recovery. found philz 6.13.0 after browsing, it also boots to recovery, installing lineageos went to boot loop just as it has done before.

I would start at step one.
Boot to download mode .
Note model and flash stock rom via Odin.
Sent from my SM-N930F using XDA-Developers Legacy app

i have tried both stock 4.4 and 5.0 roms, both boot and works fine but i still can't make twrp higher than 2.8.7.0 to work.

Okay. Now i have restored stock N9005XXUGBNL8, root and installed twrp app and used it to flash twrp 3.1.1.0 Flashing went fine as usually, phone boots as normally but still when i try to boot recovery phone reboots after 10-15sec. Also did try to flash multiple versions of twrp and no newer than 2.8.7.0 works.

Try one of the custom non ASOP roms see if that boots .
Sent from my SM-N930F using XDA-Developers Legacy app

Anyone found a solution?
I have the same problem,twrp above 2.8.7.0 dont work(bootloops) and new 7.1.2 roms do the same thing.
I manage to install an old 7.1.1 cyanogen 14 rom from 2016 december 10 minutes ago and it's working for now.
Next thing i tried to update the rom to a new build from january 2017 but i got bootloops...it's very strage.

Managed to install crdroid 7.1.2 from twrp 2.8.7.0, aokp unofficial also worked but still no luck with lineageos and newer twrp.

@stepi1 - Did you manage to find a solution to this problem? You are certainly not alone. I have exactly the same problem, and so do others! Nothing newer than TWRP 2.8.7 works on my N9005. Read the last few pages of this thread and you will see that I have the exact same issue. Seems there is either a bug or something different in the device tree for TWRP versions 3 and above which is not allowing the phones to boot these newer versions - https://forum.xda-developers.com/galaxy-note-3/development/recovery-twrp-3-2-1-1-t3746760
Chris

Sorry but no, i didn't find any solution used old twrp and crdroid for a while before giving up with that phone.

stepi1 said:
Sorry but no, i didn't find any solution used old twrp and crdroid for a while before giving up with that phone.
Click to expand...
Click to collapse
Thanks for confirming that.
Chris

fanilas said:
Anyone found a solution?
I have the same problem,twrp above 2.8.7.0 dont work(bootloops) and new 7.1.2 roms do the same thing.
I manage to install an old 7.1.1 cyanogen 14 rom from 2016 december 10 minutes ago and it's working for now.
Next thing i tried to update the rom to a new build from january 2017 but i got bootloops...it's very strage.
Click to expand...
Click to collapse
This is a known problem with some hlte devices, including mine. It has something to do with the way the newer TWRP versions (>v3) are built. There are devs working on it, but as of yet, the problem has not yet been resolved.
Chris

Note 3 SM-N9005 & Lineage or Ressurection 14.1 Nougat boot problems AND TWRP 3.1.1.0

Note 3 SM-N9005 & Lineage or Ressurection 14.1 Nougat boot problems AND TWRP 3.1.1.0
I'm doing sth wrong and it must be so obvious that just i can't see what it is - hopefuly you can give me some pointers or advice.
I tried Ressurection and Lineage 14.1 ROMs but i just can't get them to boot on sm-n9005 (checked that all the downloads are correct etc). I tried flashing TWRP 3.1.1.0, flashing went well but now i can't boot into recovery. Latest TWRP i can get to work is 2.8.7. (or CWR 6.0.4.6 touch).
Basicaly i can flash anything but nothing works (except unofficial lineage 14.1 buil 20170116 from Trader418 - and even his latest build don't work). :crying:
I get stuck at boot screen with "GALAXY NOTE 3" in the center of screen and in upper left corner when going in recovery says "RECOVERY BOOTING....." in blue and "SET WARRANTY BIT : RECOVERY" in yellow. With normal boot i get "KERNEL IS NOT SEANDROID ENFORCING" in red and "set warranty bit : kernel" in yellow. That's all even after 2 hrs of waiting (no differences flashing with CWR or TWRP).
Could the flashing with non-original cable be the problem!?!
I am upgrading from Lollipop 5.1.1. (CM 12.1) that flashes and works flawleslly.
I'd appreciate any help! :good:

The phone is running the latest boot loader and modem?

I have the same problem and i dont find the solution. Some can help us?

MICROVICIAO said:
I have the same problem and i dont find the solution. Some can help us?
Click to expand...
Click to collapse
we need more complete info about phone, twrp, CP+BL rom...
impossible for me to run last RR but crdroid or aex yes...

rayman95 said:
we need more complete info about phone, twrp, CP+BL rom...
impossible for me to run last RR but crdroid or aex yes...
Click to expand...
Click to collapse
The first problem its i can install twrp 3.x.x, i tryed with a lot off bootloaders news in the forum how "BL_N9005XXSGBQD5" or "BL_N9005XXSGBQD1-Nordic", and the baseband "CP_N9005XXUGPQB1-Nordic" and others. But i can flash 2.8.7.0 twrp without problems.
and the second problem its i can flash the Resurrection Remix of "vidwhal", can install but have a bootloop.
also i tryed flashing 4 archives (bl,cp,ap,csc and PIT) for clear or something.
i have sm-n9005 and tested a lot bootloaders and basebands, i want flash twrp 3.x.x.x and the resurrection rom based on nougat.

MICROVICIAO said:
The first problem its i can install twrp 3.x.x, i tryed with a lot off bootloaders news in the forum how "BL_N9005XXSGBQD5" or "BL_N9005XXSGBQD1-Nordic", and the baseband "CP_N9005XXUGPQB1-Nordic" and others. But i can flash 2.8.7.0 twrp without problems.
and the second problem its i can flash the Resurrection Remix of "vidwhal", can install but have a bootloop.
also i tryed flashing 4 archives (bl,cp,ap,csc and PIT) for clear or something.
i have sm-n9005 and tested a lot bootloaders and basebands, i want flash twrp 3.x.x.x and the resurrection rom based on nougat.
Click to expand...
Click to collapse
Last RR need TWRP 3.1.1-0 so you can't flash it without it...try to flash last TWRP with the 2.8.70 TWRP version or by odin
and you need last nordic CP for using RR..look my signature for having a good combination...

Anyone found a solution? I have the same problem,can't install nougat roms and trwp 3.x.x.x.
Every time i got bootloops and it's the first time my phone does that.
5.0(instaled with odin) and 6.0(instaled with twrp 2.8.7.0) roms works fine.
Ive tried so many modems and boodloaders.
I need to flash something else?
Can be some hardware issues?

Got the same problem:
1) I make a full reinstall with Odin (try with many version and i'ts always ok):
AP_N9005XXUGBNL8_CL3643614_QB3415922_REV00_user_low_ship_MULTI_CERT.tar.md5
BL_N9005DXSGBQA1.tar
CP_N9005XXUGBPI1.tar
CSC_OXA_N9005OXAGBNL8_CL3643614_QB3415922_REV00_user_low_ship_MULTI_CERT.tar.md5
HLTE_EUR_OPEN.pit
2) I install TWRP 2.8.7.0 version above doesn't work (but no error message with Odin)
3) With TWRP i install : cm-13.0-20151225-UNOFFICIAL-hlte.zip
Boot is ok but i've got this message in the center of screen and in upper left corner when going in recovery says "RECOVERY BOOTING....." in blue and "SET WARRANTY BIT : RECOVERY" in yellow. With normal boot i get "KERNEL IS NOT SEANDROID ENFORCING" in red and "set warranty bit : kernel" in yellow
If i try to install a newer version of TRWP but it doesn't work (no error message with Odin, Passed)
If i try to install LineageOS it doesn't work i've got a bootloop...
---------- Post added at 08:08 AM ---------- Previous post was at 07:57 AM ----------
SebastjanS said:
I'm doing sth wrong and it must be so obvious that just i can't see what it is - hopefuly you can give me some pointers or advice.
I tried Ressurection and Lineage 14.1 ROMs but i just can't get them to boot on sm-n9005 (checked that all the downloads are correct etc). I tried flashing TWRP 3.1.1.0, flashing went well but now i can't boot into recovery. Latest TWRP i can get to work is 2.8.7. (or CWR 6.0.4.6 touch).
Basicaly i can flash anything but nothing works (except unofficial lineage 14.1 buil 20170116 from Trader418 - and even his latest build don't work). :crying:
I get stuck at boot screen with "GALAXY NOTE 3" in the center of screen and in upper left corner when going in recovery says "RECOVERY BOOTING....." in blue and "SET WARRANTY BIT : RECOVERY" in yellow. With normal boot i get "KERNEL IS NOT SEANDROID ENFORCING" in red and "set warranty bit : kernel" in yellow. That's all even after 2 hrs of waiting (no differences flashing with CWR or TWRP).
Could the flashing with non-original cable be the problem!?!
I am upgrading from Lollipop 5.1.1. (CM 12.1) that flashes and works flawleslly.
I'd appreciate any help! :good:
Click to expand...
Click to collapse
except unofficial lineage 14.1 buil 20170116 from Trader418 - and even his latest build don't work)
Which one did you test ?
lineage-14.1-20170713-UNOFFICIAL-hlte.zip.md5sum ?
https://forum.xda-developers.com/ga...ndroid-7-0-cm14-trader418-unofficial-t3459973

MICROVICIAO said:
The first problem its i can install twrp 3.x.x, i tryed with a lot off bootloaders news in the forum how "BL_N9005XXSGBQD5" or "BL_N9005XXSGBQD1-Nordic", and the baseband "CP_N9005XXUGPQB1-Nordic" and others. But i can flash 2.8.7.0 twrp without problems.
and the second problem its i can flash the Resurrection Remix of "vidwhal", can install but have a bootloop.
also i tryed flashing 4 archives (bl,cp,ap,csc and PIT) for clear or something.
i have sm-n9005 and tested a lot bootloaders and basebands, i want flash twrp 3.x.x.x and the resurrection rom based on nougat.
Click to expand...
Click to collapse
I solved my problem by following those steps https://forum.xda-developers.com/ga...p-nougat-holy-grail-hlte-rock-stable-t3630301
I think the modem and bootloader were outdated on my phone. After upgrading them to those in thread mentioned, it worked like a charm. Hope that helps.

Leakcim said:
Got the same problem:
1) I make a full reinstall with Odin (try with many version and i'ts always ok):
AP_N9005XXUGBNL8_CL3643614_QB3415922_REV00_user_low_ship_MULTI_CERT.tar.md5
BL_N9005DXSGBQA1.tar
CP_N9005XXUGBPI1.tar
CSC_OXA_N9005OXAGBNL8_CL3643614_QB3415922_REV00_user_low_ship_MULTI_CERT.tar.md5
HLTE_EUR_OPEN.pit
2) I install TWRP 2.8.7.0 version above doesn't work (but no error message with Odin)
3) With TWRP i install : cm-13.0-20151225-UNOFFICIAL-hlte.zip
Boot is ok but i've got this message in the center of screen and in upper left corner when going in recovery says "RECOVERY BOOTING....." in blue and "SET WARRANTY BIT : RECOVERY" in yellow. With normal boot i get "KERNEL IS NOT SEANDROID ENFORCING" in red and "set warranty bit : kernel" in yellow
If i try to install a newer version of TRWP but it doesn't work (no error message with Odin, Passed)
If i try to install LineageOS it doesn't work i've got a bootloop...
---------- Post added at 08:08 AM ---------- Previous post was at 07:57 AM ----------
except unofficial lineage 14.1 buil 20170116 from Trader418 - and even his latest build don't work)
Which one did you test ?
lineage-14.1-20170713-UNOFFICIAL-hlte.zip.md5sum ?
https://forum.xda-developers.com/ga...ndroid-7-0-cm14-trader418-unofficial-t3459973
Click to expand...
Click to collapse
Read & try the reply above.

Oreo 8.1 Update T585XXU4CRJ8 problems

Hello all
I installed the latest T585XXU4CRJ8 Oreo 8.1 update over Nougat 7 on the SM-T585. (BTU / UK)
Everything went well using Odin and the Oreo stock rom from the Updato website.
Cleared the cache and factory reset from recovery mode as normal practice. Booted up ok.
The problem is the device doesn't recognise the network sim card anymore (worked perfectly on Marshmallow & Nougat).
I've tried factory reset a few times, no difference.
Removed and reinserted the sim, even tried another sim.
Having checked 'about tablet > software details' , carrier is unknown and the IMEI has dissapeared !
I've tried to reinstall Nougat 7 and Marshmallow 6 back on the SM-T585 and Odin fails every time.
Tried 2 computers and 3 different usb cables.
Even trying to reinstall Oreo 8.1 again Odin fails!
Theres no frp lock activated, and the oem unlock tab is checked, usb debugging enabled too.
I've read somewhere Samsung have done something to Oreos BootLoader file to stop people downgrading back to earlier software.
I know its early days, but if anyone can offer any solutions, it'd be appreciated.:good:
How to change the BL file version, so i can reinstall earlier stock roms back?
The Oreo update seems more hassle than its worth and I didnt expect the sim card to be unrecognised once updated, let alone being faced with the puzzle of how to downgrade the software.
Thanks for reading. :good:

I think the problem was I used all four files (AP, BL,CP & CSC) from the Netherlands rom and that's whats screwed the device up!
As in no SIM card acknowledgement. I ran the IMEI number off the rear casing through a blacklist checking site and it came back clean.
After many attempts trying every Odin program variant possible and even tried mixing and matching files from different stock roms ( MM 6.0.1 , N7 and Oreo 8.1). To try and get the network carrier file installed, Odin refused to install anything.
https://desktop.firmware.mobi/device:754/firmware:1660
https://download.chainfire.eu/1069/CF-Root/CF-Auto-Root/CF-Auto-Root-gtaxllte-gtaxlltexx-smt585.zip
https://twrp.me/samsung/samsunggalaxytaba101wifi2016.html
Tried the above routes to root to no avail, but Magisk worked by patching the boot.img file (which worked ok). Then tried Odin to install TWRP recovery, again from the site above, nothing but blue and fuzzy lines on the boot screen. The device wouldn't boot into the OS, had to go straight to download mode. Prior to that, I even installed the TWRP manager apk and connected to wifi to flash the TWRP.img from inside the OS environment and the same happened again with all variants of TWRP! Wouldn't boot, properly, no screen visuals, but lines......
Surely someone else on here has the same device (BTU UK) SM T585 that has a working TWRP recovery?
After many hours, I couldn't get Odin to play ball , so the only option left was to try the route of root, twrp recovery then installing a custom rom from twrp.
(https://forum.xda-developers.com/ga...-ultra-lean-rom-galaxy-tab-10-1-2016-t3467942)
But it's a no go as TWRP wouldn't install properly, I'm totally miffed by the damage the software has done.
Surely just reflashing the CP file should have reinstated the network facility, but it hasn't.
The last resort is for me to wait until Samsung actually release the UK version of Oreo 8.1 and see if I can get the sim card working again.
Moral of the story is wait until a UK version of the update is released, and even then you have to question is it worth it, if Samsung are making bootloader files so no downgrades are possible, nor allowing any modifications.
Hopefully this info may help others out who are thinking of upgrading or having similar issues.
Cheers for reading

tsam19 said:
I think the problem was I used all four files (AP, BL,CP & CSC) from the Netherlands rom and that's whats screwed the device up!
As in no SIM card acknowledgement. I ran the IMEI number off the rear casing through a blacklist checking site and it came back clean.
After many attempts trying every Odin program variant possible and even tried mixing and matching files from different stock roms ( MM 6.0.1 , N7 and Oreo 8.1). To try and get the network carrier file installed, Odin refused to install anything.
https://desktop.firmware.mobi/device:754/firmware:1660
https://download.chainfire.eu/1069/CF-Root/CF-Auto-Root/CF-Auto-Root-gtaxllte-gtaxlltexx-smt585.zip
https://twrp.me/samsung/samsunggalaxytaba101wifi2016.html
Tried the above routes to root to no avail, but Magisk worked by patching the boot.img file (which worked ok). Then tried Odin to install TWRP recovery, again from the site above, nothing but blue and fuzzy lines on the boot screen. The device wouldn't boot into the OS, had to go straight to download mode. Prior to that, I even installed the TWRP manager apk and connected to wifi to flash the TWRP.img from inside the OS environment and the same happened again with all variants of TWRP! Wouldn't boot, properly, no screen visuals, but lines......
Surely someone else on here has the same device (BTU UK) SM T585 that has a working TWRP recovery?
After many hours, I couldn't get Odin to play ball , so the only option left was to try the route of root, twrp recovery then installing a custom rom from twrp.
(https://forum.xda-developers.com/ga...-ultra-lean-rom-galaxy-tab-10-1-2016-t3467942)
But it's a no go as TWRP wouldn't install properly, I'm totally miffed by the damage the software has done.
Surely just reflashing the CP file should have reinstated the network facility, but it hasn't.
The last resort is for me to wait until Samsung actually release the UK version of Oreo 8.1 and see if I can get the sim card working again.
Moral of the story is wait until a UK version of the update is released, and even then you have to question is it worth it, if Samsung are making bootloader files so no downgrades are possible, nor allowing any modifications.
Hopefully this info may help others out who are thinking of upgrading or having similar issues.
Cheers for reading
Click to expand...
Click to collapse
I had the same problem, went from Lineage 14.1 to Oreo stock rom (the flashable one you can find on this site, i flashed also the Bootloader/modem file in the thread). No imei, no baseband. Returned back to lineage and got back imei and baseband, but after my screen was going to sleep (after the regular 1 min) I had only black screen and vertical red lines. I flashed then Resurrection Remix 6.2, Lineage 15, Lineage 16, always the same problem. Then I used Odin and the original firmware of Nougat from SamMobile, at the first attempt i flashed only the AP file. I turned to have the same problem, but this time the lines were white. I flashed all the 4 files again with Odin, problem solved and back to Lineage 14.1 (the only custom rom were everything works)

Domenico F.
What version of TWRP have you installed for the T585 and from what site?
Also what root method did you use?
I have tried all available and all seem corrupt i.e don't install properly, no proper boot up with onscreen options. Just fuzzy lines.
Again root i've tried many, but don't work with this Oreo 8.1., even Magisk is problematic.
I think its pretty sad of Samsung sending out poor quality updates for us to use. Their heading the same way as Apple and the way they control customers.
If I could go back to a custom MM or Nougat, I would. But TWRP / ROOT are an issue. i.e no TWRP no custom rom!
If anyones thinking of updating and reading this topic, stay clear of the Oreo 8.1 update for the SM T585. Once installed theres no turning back.....so it seems
Thanks for replying.

tsam19 said:
Domenico F.
What version of TWRP have you installed for the T585 and from what site?
Also what root method did you use?
I have tried all available and all seem corrupt i.e don't install properly, no proper boot up with onscreen options. Just fuzzy lines.
Again root i've tried many, but don't work with this Oreo 8.1., even Magisk is problematic.
I think its pretty sad of Samsung sending out poor quality updates for us to use. Their heading the same way as Apple and the way they control customers.
If I could go back to a custom MM or Nougat, I would. But TWRP / ROOT are an issue. i.e no TWRP no custom rom!
If anyones thinking of updating and reading this topic, stay clear of the Oreo 8.1 update for the SM T585. Once installed theres no turning back.....so it seems
Thanks for replying.
Click to expand...
Click to collapse
just flash the nougat firmware from SamMobile. You have to flash all the 4 files in the zip you are going to download. AP, CSC, etc. Once you have your tablet completely stock you can install again TWRP and flash whatever CUSTOM rom you want.
I easily rooted the phone with odin flashing only the TWRP in AP box (twrp taken from this post https://forum.xda-developers.com/showpost.php?p=78145080&postcount=160) avoid the auto-reboot. You have to put the tab in DL mode, connect it to pc, start odin flash the twrp in AP file e unselect Auto-reboot. As soon as the process is done you have to log in recovery mode at the first boot with home + power + vol up and flash dm-verity. I rooted with Magisk without any problem just flashing the v17.3. Now i' m back to nougat (from Oreo) and i can install whatever custom rom i want. But honestly the only one fully working is Lineage 14.1. Resurrection remix 6.2 has problem with camera and gps don't lock. Same for Oreo version. Tried Pie, same problem.

Domenico F
Thanks for the info.
I tried to install MM 6.01 & Nougat 7 stock rom and they wouldn't install, no matter what I did. ( see Odin pictures )
The last chance was to try Oreo 8.1 again and I did manage to reflash the 'Netherlands stock Oreo 8.1 rom' (after 10 hours!) using all four files (AP,BL,CP,CSC).
I then reset the device a couple of times via stock recovery. Took the OEM lock off, theres no FRP lock either. Enabled developer mode > debug mode (all the usual setting changes prior to rooting / twrp install).
At this point the imei and sim card network ARE recognised and work on the device as normal.
HOWEVER I found once I rooted by any genuine means > Magisk v16 (patched boot img taken from stock rom) and also the CF gtaxlltex sm t585 auto root method.
And when the device booted back up, the 'imei and sim card' WERE NOT usable, nor recognised, no network...........I also noticed BusyBox wouldn't install at all, message about integrity of root.
Adaway and Lucky Patcher recognised root.
I also then tried installing TWRP 3.0.2.0 -3.2.3.0 from many locations and again, none of them worked at all. Just blue lines, fuzzy screen etc. On some occasions Odin wouldn't even process the files.
I include pictures of the files I used.
Its evident to me that I can use the device normally i.e sim card , make calls, data etc if I don't attempt to install root / twrp recovery.
So no root , no twrp , then no custom rom usable or installable. It sounds like Samsung are out to stop custom software on their products.
If the Netherlands stock rom 'BL' (boot loader) file is encrypted with this new binary v3 or v4 to stop OS modifications. I wouldn't recommend using it when flashing the new Oreo 8.1 rom or future new releases.
The best way is to just use the AP file ONLY and overlap Nougat 7 or MM 6. And because you've kept your original BL from earlier stock roms, it may be possible to downgrade back to MM or Nougat if need be.
Once the latest new Oreo / Pie 'BL files' are used in the Odin flashing process, it causes big problems.
Hopefully, maybe someone smart enough can find away to decipher these new BL files and offer a replacement method. which will allow software downgrades and modifications

tsam19 said:
Domenico F
Thanks for the info.
I tried to install MM 6.01 & Nougat 7 stock rom and they wouldn't install, no matter what I did. ( see Odin pictures )
The last chance was to try Oreo 8.1 again and I did manage to reflash the 'Netherlands stock Oreo 8.1 rom' (after 10 hours!) using all four files (AP,BL,CP,CSC).
I then reset the device a couple of times via stock recovery. Took the OEM lock off, theres no FRP lock either. Enabled developer mode > debug mode (all the usual setting changes prior to rooting / twrp install).
At this point the imei and sim card network ARE recognised and work on the device as normal.
HOWEVER I found once I rooted by any genuine means > Magisk v16 (patched boot img taken from stock rom) and also the CF gtaxlltex sm t585 auto root method.
And when the device booted back up, the 'imei and sim card' WERE NOT usable, nor recognised, no network...........I also noticed BusyBox wouldn't install at all, message about integrity of root.
Adaway and Lucky Patcher recognised root.
I also then tried installing TWRP 3.0.2.0 -3.2.3.0 from many locations and again, none of them worked at all. Just blue lines, fuzzy screen etc. On some occasions Odin wouldn't even process the files.
I include pictures of the files I used.
Its evident to me that I can use the device normally i.e sim card , make calls, data etc if I don't attempt to install root / twrp recovery.
So no root , no twrp , then no custom rom usable or installable. It sounds like Samsung are out to stop custom software on their products.
If the Netherlands stock rom 'BL' (boot loader) file is encrypted with this new binary v3 or v4 to stop OS modifications. I wouldn't recommend using it when flashing the new Oreo 8.1 rom or future new releases.
The best way is to just use the AP file ONLY and overlap Nougat 7 or MM 6. And because you've kept your original BL from earlier stock roms, it may be possible to downgrade back to MM or Nougat if need be.
Once the latest new Oreo / Pie 'BL files' are used in the Odin flashing process, it causes big problems.
Hopefully, maybe someone smart enough can find away to decipher these new BL files and offer a replacement method. which will allow software downgrades and modifications
Click to expand...
Click to collapse
Honestly i think this run for Oreo it's not really worth. I said you what I did and now i have no problems. I'm not in hurry to use Oreo (as stock rom). I think Lineage 14.1 is the most stable and fastest rom i tried till now, and most of all everything is working. I think i'll give a try via Odin to the official stock rom when it will be available for download (i live in Germany) but sadly I don't use most of the Samsung bloatware installed by default.

WRP Oreo 8.1 on Galaxy Tab 10.1 (T585)
Then I've tried
twrp_3.2.3-1_sm-t585_29918 which gives only stripes when booting into recovery
Do I have to flash the stock boot/recovery before flashing this one,
or this is broken, as well.
Many thanks for a hint,
Helmut

Hope this helps.
So, as I was trying to search for my Galaxy Tab A6 (SM-T585) for Deodexed Stock ROM, I stumbled upon this thread https://forum.xda-developers.com/galaxy-tab-a/themes/mod-twrp-odin-t3650215 just follow the instructions to fully flash Oreo. By the way when flashing Root, I would recommend Magisk Beta https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
it does not damage the IMEI at all(Thread here, read the comment:https: //forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445) . The TWRP, I think we should leave it be, don't flash an update for the TWRP.
Thanks. Hope this helps.

MiaMOTo SU # said:
By the way when flashing Root, I would recommend Magisk Beta https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
it does not damage the IMEI at all
Click to expand...
Click to collapse
Neither does a custom recovery, so not sure what your point is?

I mean if your having problems using MAGISK use the beta version

Trouble flashing roms sm t350

Hello all, maybe you can help...
After finally getting a stable TWRP from @ashyx that finally booted, I attempted to flash roms and Gapps on my SM-T350. This should be simple enough, but every rom I flash either doesn't boot or boots with only sound and no display!!!!
Yes, I'm running TWRP 3.2.3-1 courtesy of @ashyx
Yes, I've wiped several times.... wiped internal storage sometimes too
I'm running the latest official 7.1.1 release from Samsung.... I cannot get anything else to boot!
Please offer some support, I need some help y'all!
-------------------------------------------
EDIT: THIS ISSUE HAS BEEN SOLVED
Check the latest comments for more info

I'm having the exact same issues, never experienced this before with any device. Hope someone can help or we can find a fix.

Same - SM-T350
I was able to install Jazzrom but none of the other SM-T350 roms. I can hear sound when I press the power button, but no display when trying Lineage 15 or 16. Jazzrom runs slow, that is why I'm not sticking with it. I have tried several versions of TWRP as well. 3.2.3-1 seems to be the only one that got Jazzrom installed. Thanks in advance for your time. Same issue with crDroid rom ver 5.2

my suggestion would be to use odin to reflash to stock, and reinstall twrp. i've never encountered that specific issue with the device

elginsk8r said:
my suggestion would be to use odin to reflash to stock, and reinstall twrp. i've never encountered that specific issue with the device
Click to expand...
Click to collapse
Tried that.... no luck. Everyone else who reported a problem is having the same exact issue as me.... it's strange.

Here is what I posted in the crDroid area:
I might be posting a little soon but finally on the road to success after only getting a blank screen after boot. Downgraded the stock 7.1.1 to marshmallow T350XXU1BPK1 using the BL, AP and CSC files in Odin. Used TWRP TWRP-3.2.1-lineage-15.1_j1_20180418_gt58wifi. Versions of TWRP that worked before didn't work after the downgrade. Installed April 9th crDroid ROM and gapps pico. I am now at the sign in screen.

heymanster said:
Here is what I posted in the crDroid area:
I might be posting a little soon but finally on the road to success after only getting a blank screen after boot. Downgraded the stock 7.1.1 to marshmallow T350XXU1BPK1 using the BL, AP and CSC files in Odin. Used TWRP TWRP-3.2.1-lineage-15.1_j1_20180418_gt58wifi. Versions of TWRP that worked before didn't work after the downgrade. Installed April 9th crDroid ROM and gapps pico. I am now at the sign in screen.
Click to expand...
Click to collapse
Hmm..... I will check this out. Thanks for the lead! I will let u know what happens

heymanster said:
Here is what I posted in the crDroid area:
I might be posting a little soon but finally on the road to success after only getting a blank screen after boot. Downgraded the stock 7.1.1 to marshmallow T350XXU1BPK1 using the BL, AP and CSC files in Odin. Used TWRP TWRP-3.2.1-lineage-15.1_j1_20180418_gt58wifi. Versions of TWRP that worked before didn't work after the downgrade. Installed April 9th crDroid ROM and gapps pico. I am now at the sign in screen.
Click to expand...
Click to collapse
This solved it!!! Finally!!! For clarification, anyone who is having this issue must downgrade to stock Marshamallow (BPK1) and flash twrp 3.2.1. It must have something to do with the newer oreo bootloader, so just downgrade and Viola! Success! :good: