Related
Hi,
1. If somebody experience this issue with lack of netwrok after Nougat full Rom update, like:
https://forum.xda-developers.com/showpost.php?p=71063185&postcount=121
than follow this fix from another thread:
https://forum.xda-developers.com/showpost.php?p=71054990&postcount=1456
for me it all seems to work fine now.
2. If somebody has issues with MiFlash, I think it is actually better to do the flash within first 5-10, after that it gives strange errors. If so, restrt EDL and press flash on MiFlash a bit faster .
Regards
I failed to boot nougat using these steps:
Boot to edl.
Flashed using miflash full b15 file and then b15 twrp file.
Flashed in twrp a2017 N modem.
Then it gets stuck at 5 secs screen and phone just reboots back to edl. Am i doing it wrong?
However it boots to nougat if only flashing just the b15 full.
Hi,
I had stock B13 Chinese. I MiFlahed fastboot_unlock packge,
did fastboot oem unlock,
MiFlashed B15 twrp,
copied NON-HLOS.bin file from Chinese modem(link above) into extracted B15 Full package folder(which replaced exsiting file in there) ,
reset dalvik etc.from twrp,
flashed B15 full which included already new modem file,
I let it boot finally till the end into standard mode.
This way I don't even have twrp now and all works fine.
Regards
RubiCom said:
Hi,
I had stock B13 Chinese. I MiFlahed fastboot_unlock packge,
did fastboot oem unlock,
MiFlashed B15 twrp,
copied NON-HLOS.bin file from Chinese modem(link above) into extracted B15 Full package folder(which replaced exsiting file in there) ,
reset dalvik etc.from twrp,
flashed B15 full which included already new modem file,
I let it boot finally till the end into standard mode.
This way I don't even have twrp now and all works fine.
Regards
Click to expand...
Click to collapse
Hi, what you mean you don't have twrp? Is it possible to install it somehow again? Is it possible to install SuperSU then? I'm asking this because I want to install A2017U B15 firmware (with OTA support) on A2017 (Chinese model with B13, stock recovery and locked bootloader) and just want to be sure in everything before I start Many thanks!
Wuchko said:
Hi, what you mean you don't have twrp? Is it possible to install it somehow again? Is it possible to install SuperSU then? I'm asking this because I want to install A2017U B15 firmware (with OTA support) on A2017 (Chinese model with B13, stock recovery and locked bootloader) and just want to be sure in everything before I start Many thanks!
Click to expand...
Click to collapse
Hi,
If you MiFlash B15 Full package it overwrites recovery partition...it is a full package after all. If you want TWRP on your nougat after that you need to Miflsh the B15 TWRP package. However inside the TWRP package, there is also modem driver file which you need to first replace with the new modem file, same as with B15 FULL package.
It is al soooo simple. I had some issues with MiFlash initially, as I read somewhere to "keep the vol up down, power fo 5 sec, release, wait 5seconds and than flash"
However I had near 100% success rate when I did press the flash button around 2-5 seconds after booting into EDL mode. Once you do oem unlock, the process is simple as burning ISO image on a CD
I have it now without that last step. It is unlocked, but without TWRP. I did however MiFlashed TWRP yesterday and it did work fine than as well. I don't however think I need TWRP anymore. I did Dalvik etc. reset during upgrading to Nougat... and that's all I needed it for. Maybe I'm wrong and I will MiFlash it again some day, but honestly, this was first time I flashed any Android phone as I come from Nokia- Windows Phone and all I wanted is working Daydream, Netflix VR for my long business flights. It works now. The rest I might need I will install from play store.
It does have that message about unlocked bootloader when you boot the phone, but it does not bother me and I read somewhere that it is better not to relock he phone.
How do I even know if it's OTA capable? When I checked updates, it says your phone is up to date.
Regards
Ok, now is everything much more clear to me, thank you!
Please help fellow china version users... @RubiCom
I have flashed b15 and the updated modem for china but my signal is still unusable. It keeps restarting the sim and when I go to sim settings, "com.android.phone" crashes. Some other settings related to calls/sim also crashes.
my sim is working fine when I'm on LOS. I really just want to use stock system since audio isn't fully fixed with LOS.
BTW, i'm already BL unlocked since b13. Do I still have to flash b15 twrp? I mean I could just fastboot flash twrp after installing full b15. Is there something special miflashing the b15 twrp package?
otaconremo said:
Please help fellow china version users... @RubiCom
I have flashed b15 and the updated modem for china but my signal is still unusable. It keeps restarting the sim and when I go to sim settings, "com.android.phone" crashes. Some other settings related to calls/sim also crashes.
my sim is working fine when I'm on LOS. I really just want to use stock system since audio isn't fully fixed with LOS.
BTW, i'm already BL unlocked since b13. Do I still have to flash b15 twrp? I mean I could just fastboot flash twrp after installing full b15. Is there something special miflashing the b15 twrp package?
Click to expand...
Click to collapse
I follow all the steps in original thread and after all everything works (at least for me) . But, it was a little bit complicated to make it work
So, first after unlocking I installed B15 TWRP, then entered into TWRP and deleted cache, dalvik, etc.. After that I put my phone into EDL again and flashed B15 original (I didn't boot phone to OS between flashing ROM's at all). But, on boot B15 original I still had some chinese symbols and I couldn't finish setup (phone stuck at google account setup). So, I repeated this three steps (installation of B15 TWRP, wiping everything in TWRP and installation of B15 original) again. This time I've got "android encrypted" or some similar message on boot B15 original(??!!), but after reboot everything was completely normal (except message that bootloader is unlocked, which is normal). I don't have TWRP, but 2G/3G/4G signal is great on both SIM's without lose and I have official updates. Comparing with chinese MM, this Nougat is far more better and faster, like I have a new phone
Wuchko said:
I follow all the steps in original thread and after all everything works (at least for me) . But, it was a little bit complicated to make it work
So, first after unlocking I installed B15 TWRP, then entered into TWRP and deleted cache, dalvik, etc.. After that I put my phone into EDL again and flashed B15 original (I didn't boot phone to OS between flashing ROM's at all). But, on boot B15 original I still had some chinese symbols and I couldn't finish setup (phone stuck at google account setup). So, I repeated this three steps (installation of B15 TWRP, wiping everything in TWRP and installation of B15 original) again. This time I've got "android encrypted" or some similar message on boot B15 original(??!!), but after reboot everything was completely normal (except message that bootloader is unlocked, which is normal). I don't have TWRP, but 2G/3G/4G signal is great on both SIM's without lose and I have official updates. Comparing with chinese MM, this Nougat is far more better and faster, like I have a new phone
Click to expand...
Click to collapse
I figured out what's wrong my my setup but still I can't find a way to fix this.
It seems that when I use my original sim cards (2 sims with the same provider), they both get disconnected every second.
When I put another sim from another provider, it does work but still my original sim doesn't get signal. even when changing slots.
I'm really confused how to make them work together.
otaconremo said:
I figured out what's wrong my my setup but still I can't find a way to fix this.
It seems that when I use my original sim cards (2 sims with the same provider), they both get disconnected every second.
When I put another sim from another provider, it does work but still my original sim doesn't get signal. even when changing slots.
I'm really confused how to make them work together.
Click to expand...
Click to collapse
That's weird. I'm also using SIM's from same providers, but without any problems.. Don't know what to tell, maybe you can try install B15 TWRP and wipe everything, then install B15 original and try again.. First time I also had some weird problems...
Wuchko said:
That's weird. I'm also using SIM's from same providers, but without any problems.. Don't know what to tell, maybe you can try install B15 TWRP and wipe everything, then install B15 original and try again.. First time I also had some weird problems...
Click to expand...
Click to collapse
this is actually wierd. I had this problem my my sims. And I had flashed this many times already trying out different methods including miflash and even stock flashable zips from draken. all yields to the same results.
Do you have any idea where to tweak carrier settings from system files? i tried *#*#4636*#*# but still fails.
Unfortunately I don't know it. I guess I had plenty of luck flashing these ROM's, considering how many people have problems..
Long story short I wanted to update to oreo from the latest version of Oxygen OS so I downloaded the update through a VPN which caused my phone to bootloop. In the process of recovering everything, i had to format all data so I formatted everything and reinstalled a stable version of oxygen os from their site. Now all of a sudden I couldn't connect to wifi as it said it was disabled however I fixed this by defaulting my mac address but apparently that didn't work as it connected to the wifi but nothing actually loads or works. Much help would be appreciated!
Note : Wifi only connects if its set to static IP however when changed to DHCP it gets tuck on obtaining an IP adress.
Same problem... Please help us out, been stuck trying to figure this out for hours now with no success. Thanks
Same here I'm going to look to see if there's a way to reset DHCP then you've given me a clue.
Nope this doesn't seem to be the issue in my case the phone won't even associate with router according to the router.
---------- Post added at 07:29 PM ---------- Previous post was at 07:02 PM ----------
My logcat isn't giving me a lot of clues,
--- redacted ---
Click to expand...
Click to collapse
same problem, downgraded back to nougat and the problem still persists
So I've done some more ground work it appears TWRP can't properly upgrade the phone however the stock recovery can via an ADB sideload.
My suspicion is the DM-verity doesn't actually work right or that magicsk 14.6 is not compatible with our version oreo.
Unfortunately I rely on root for a few important functions so I'm not about to give that up unfortunately it seems the update does something that cause the wifi to stop working.
I'm looking into an update that was floating around during the oreo beta that allowed people to go from Oreo back to Nougat maybe there were some steps in there that fixed your wifi antennas so they weren't perminently broken and you can safely roll back I'm going to try flashing that next wish me luck.
Although I haven't properly solved this issue I decided to flash the no limits rom which is based on oxygen OS and I flashed the stable Oreo version which fixed the wifi problem that I was having, however when flashing this rom I did use the Blu spark TWRP instead of the original and I'm unsure if that made any difference whatsoever.
Ok so I managed to revert back to Nougat proper here's the procedure
1. Flash stock recovery. Stock recovery does apparently more than just flash the system partition during an ADB sideload
2. boot into stock recovery. Wipe everything System, Wipe Cache, Wipe Personal data
3. Enable ADB sideload
4. Flash OxygenOS OTA proper
5. Allow system to boot verify wireless functionality
6. Boot back into stock recovery
7. Flash the roll back build this will fix any wifi driver issues in a hidden partition I bet. It can be found on the oreo beta post here https://forum.xda-developers.com/oneplus-5/how-to/official-oxygenos-beta-1-android-oreo-t3710003 or just download it direclty here [Here]
8. After the rollback build finishes booting verify wireless functionality (optional)
9. Flash back your recovery and it should all be working again.
I guess those of us that want a working root and descrypted data will have to wait for either a working dm-verity for oreo or an updated magicsk the current 14.6 doesn't seem to be all that reliable. And all this on christmas!
I had the same issue. Flashing the oreo OTA worked for me.
twrp-3.1.1-1-cheeseburger
download oreo from here: https://forum.xda-developers.com/oneplus-5/how-to/official-oxygenos-5-0-android-8-0-t3724234
RIT35H said:
I had the same issue. Flashing the oreo OTA worked for me.
twrp-3.1.1-1-cheeseburger
download oreo from here: https://forum.xda-developers.com/oneplus-5/how-to/official-oxygenos-5-0-android-8-0-t3724234
Click to expand...
Click to collapse
I have now flashed this using the blu spark twrp after getting rid of my custom rom and everything seems to work so thanks!
However I seem to be facing a Magisk issue now no matter what ROM I use when flashing magisk i boot into a black screen until i remove it using the uninstaller
Queried and resolved in below thread.
https://forum.xda-developers.com/oneplus-5/help/wifi-completely-broken-t3721004
vortex-5 said:
Ok so I managed to revert back to Nougat proper here's the procedure
1. Flash stock recovery. Stock recovery does apparently more than just flash the system partition during an ADB sideload
2. boot into stock recovery. Wipe everything System, Wipe Cache, Wipe Personal data
3. Enable ADB sideload
4. Flash OxygenOS OTA proper
5. Allow system to boot verify wireless functionality
6. Boot back into stock recovery
7. Flash the roll back build this will fix any wifi driver issues in a hidden partition I bet. It can be found on the oreo beta post here https://forum.xda-developers.com/oneplus-5/how-to/official-oxygenos-beta-1-android-oreo-t3710003 or just download it direclty here [Here]
8. After the rollback build finishes booting verify wireless functionality (optional)
9. Flash back your recovery and it should all be working again.
I guess those of us that want a working root and descrypted data will have to wait for either a working dm-verity for oreo or an updated magicsk the current 14.6 doesn't seem to be all that reliable. And all this on christmas!
Click to expand...
Click to collapse
Thank you very much. Back on Nougat now without wifi issues!
It seems like it's probably magisk support since 14.6 current build doesn't work on nougat either.
I have note 3 sm-n9005 htle running os lineage 15.1 that made by @haggertk
I have been using lineage 14.1 unofficial made by trader418 and haggertk for months everything was working fine i didn't have any problem then week ago i saw lineage 15.1 so i clean flashed my phone to lineage 15.1 at first everything was working fine then after a few minutes i restarted my phone and then my phone stopped receiving signal
I restarted a few more time times and suddenly signals came back
But then a few hours later same thing happened again
Now every time i restart my phone or battery dies i have to restart my phone serval time till signal comes back
Today i realized every time my phone stops receiving signal phone app (dialler app) crashes when i dial *#06# and auto network registration automatically turns off when i turn it back on it says can't connect to thins network now please try again later. Or when i try to choose my network manually it says error while searching for networks
After a few restarts everything just works fine everything goes back to normal
I've already changed CP and BL serval times to serval different (CP and BL)s it didn't work
Anyone else has this issue?
Or please anyone knows how to fix it?
I'd the same problem with you before. I tried to flash new modem and bootloader (in LOS) but it didn't change. So, this what I did (it quite long but I hit jackpot after that)
1. Download Phronesis Rom (it is custom stock rom, maybe can use another custom stock rom) and put in the internal storage
2. flash TWRP2.8.70
3. you can see instruction on how to flash Phronesis
4. Reboot system
5. Enable Developer option (if it is disable)
6. Flash Bootloader (BL) and Modem (CP)
7. check it back using phone info app (for me, it did work)
8. reboot recovery, flash TWRP 3.2.1.1 again
9. Full wipe
10. Flash LOS and gapps
11. reboot system
hope this will help
azliazmi said:
I'd the same problem with you before. I tried to flash new modem and bootloader (in LOS) but it didn't change. So, this what I did (it quite long but I hit jackpot after that)
1. Download Phronesis Rom (it is custom stock rom, maybe can use another custom stock rom) and put in the internal storage
2. flash TWRP2.8.70
3. you can see instruction on how to flash Phronesis
4. Reboot system
5. Enable Developer option (if it is disable)
6. Flash Bootloader (BL) and Modem (CP)
7. check it back using phone info app (for me, it did work)
8. reboot recovery, flash TWRP 3.2.1.1 again
9. Full wipe
10. Flash LOS and gapps
11. reboot system
hope this will help
Click to expand...
Click to collapse
Why you need phronesis? Only for enabling developer options? Maybe you forgot the critical step of removing battery before entering to download mode to flash BL and CP in ODIN? Because you seem to use a custom ROM only for enabling developer options and checking phone info samsung app (both of which can be done in stock firmware or even LOS itself).
Because I need to flash the modem. I tried flash the modem using ODIN in LOS and RR (both with developer option) but unfortunately failed. That's why I going back to Phronesis, just to flash the modem
azliazmi said:
Because I need to flash the modem. I tried flash the modem using ODIN in LOS and RR (both with developer option) but unfortunately failed. That's why I going back to Phronesis, just to flash the modem
Click to expand...
Click to collapse
I have seen many users flash modem on LOS and RR using ODIN when steps are done correctly. The part confusing me on noth of your posts is you didnt try to check your modem after flashing in LOS (using settings/about or phone info samsung app)? Because if it shows it updated, then it is updated. If not, then you have missed a step. That simple. It cannot be that "it shows modem is updated but somehow it isnt".
I dont think any external step of flashing another custom ROM is necessary. Flashing modem step-by-step procedure is available in many posts of @svbarbosa and @Hereiwas.
I did check the modem after flashing every single time, I flashed with different modem and bootloader, unfortunately the result is same. After failed so many times, than I tried flash Phronesis as my last resort. And I really don't know and understand why my device like that (I follow exactly the procedure as given)
azliazmi said:
I'd the same problem with you before. I tried to flash new modem and bootloader (in LOS) but it didn't change. So, this what I did (it quite long but I hit jackpot after that)
1. Download Phronesis Rom (it is custom stock rom, maybe can use another custom stock rom) and put in the internal storage
2. flash TWRP2.8.70
3. you can see instruction on how to flash Phronesis
4. Reboot system
5. Enable Developer option (if it is disable)
6. Flash Bootloader (BL) and Modem (CP)
7. check it back using phone info app (for me, it did work)
8. reboot recovery, flash TWRP 3.2.1.1 again
9. Full wipe
10. Flash LOS and gapps
11. reboot system
hope this will help
Click to expand...
Click to collapse
Thanks man it worked for me to
Some how lineage 15.1 makes the baseband not work properly and makes unchangeable I tried to change it before it always gave me pass in Odin but never really changed the baseband and I didn't realize that till I tried your method
Now my phone works perfectly
Eleo said:
I have seen many users flash modem on LOS and RR using ODIN when steps are done correctly. The part confusing me on noth of your posts is you didnt try to check your modem after flashing in LOS (using settings/about or phone info samsung app)? Because if it shows it updated, then it is updated. If not, then you have missed a step. That simple. It cannot be that "it shows modem is updated but somehow it isnt".
I dont think any external step of flashing another custom ROM is necessary. Flashing modem step-by-step procedure is available in many posts of @svbarbosa and @Hereiwas.
Click to expand...
Click to collapse
I never check it before but when I red your comment I tried changing baseband and bootloader and then I realized it always gives pass on Odin but it never did really change baseband or bootloader i think the problem is with the lineage 15.1 that makes baseband untouchable
azliazmi said:
I'd the same problem with you before. I tried to flash new modem and bootloader (in LOS) but it didn't change. So, this what I did (it quite long but I hit jackpot after that)
1. Download Phronesis Rom (it is custom stock rom, maybe can use another custom stock rom) and put in the internal storage
2. flash TWRP2.8.70
3. you can see instruction on how to flash Phronesis
4. Reboot system
5. Enable Developer option (if it is disable)
6. Flash Bootloader (BL) and Modem (CP)
7. check it back using phone info app (for me, it did work)
8. reboot recovery, flash TWRP 3.2.1.1 again
9. Full wipe
10. Flash LOS and gapps
11. reboot system
hope this will help
Click to expand...
Click to collapse
I have flash LineageOS 15.1, i also have problem with signal and gsm,after that i flash CP and BL,it was the same.
i go back on stock Rom,download samsung Firmware and flash phone. now if I install Phronesis do i need again to flash CP and BL?
If you are already on stock rom, no need to flash phronesis.
Ok. But I want to install LineageOS, how to fix problem with Gsm network?
Updating BL and CL did not solve the problem. What should I do?
---------- Post added at 02:18 AM ---------- Previous post was at 02:08 AM ----------
One more question: when I go back to stock rom i don't have root anymore but I have installed Twrp recovery. This phonesis rom is nice. I would like to flash my phone with this rom. Do I need root and does gsm network working without installing BL and CL?
I will install this rom from my phone without root from TWRP 3.1.1. Can I do that?
I have the same damn problem!! LineageOS is sooo buggy with SIM mobile signal connection... it just kills it!!! How the hell can I fix this? Where can I get the modem files for Samsung 900V?
Please read thread and see your identical post .
Suggest you stick with stock rom or try your models forum.
https://forum.xda-developers.com/verizon-galaxy-note-3
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
I was running LOS 16 until last night and decided to switch to RevengeOS/Evolution X
When I tried to flash either of these ROMs with CosmicDan's TWRP I got an error 1 (logs attached)
Eventually when I tried to flash LOS 16 again with the original TWRP, that didn't flash either. Tried flashing the stock ROM via the zip here on XDA but that just went into a bootloop.
Finally, I was able to flash Pixel Experience and HavosOS -- both of which now have an issue where the fingerprint gets registered and the gestures also work but it just doesn't work for unlocking the phone and it shows "Not Recognized"
Note : I'm on the latest March firmware 10.0.6.0
Probably need a firmware update or a firmware that matches the ROM. To be sure, restore first with MiFlash, unlock bootloader again if necessary, then hotboot TWRP to start installing everything. Make sure to flash firmware files as this affects the modem and FP. If the vendor partition really got corrupted then you can try to fix it or flash stock with MiFlash.
I also had mounting errors when I flash more than 1 zip. Reboot TWRP and make sure you have the correct slot selected -- then flash your zip.
what is the "original" TWRP did you use?
Same here. Can only flash stock 10.0.4 . Also 10.0.4 can't update via ota, I updated with the twrp flashable 10.0.8 zip. This happen after revert back from treblized repartition
same here i dont know why i get this error i've never flashed rom using TWRP
Same here: the fingerprints are corretly registered but can't be used to unlock the phone ("Not recognized"), and they are forgotten after a phone reboot
Edit: try to disable PIN or Draw Unlock Pattern (so that you remove both fingerprints and code unlock), restart the phone, add a fingerprint selecting FINGERPRINT + Password option, choose a password and add a fingerprint.
It should work now; then you can use again your favourite method to unlock
Always disable unlock pattern before flashing custom roms
Sometimes you have to extract "persist.img" from Fastboot image, and then use "fastboot flash persist persist.img"