[SOLVED] On Reboot, Kernel keeps resetting to MM - Verizon Galaxy S 5 Q&A, Help & Troubleshooting

===Solved! Just overwrite your old SafeStrap by installing the SafeStrap.apk included at this thread:
http://forum.xda-developers.com/verizon-galaxy-s5/general/root-method-og5-ok3-t3290370
and be sure to have BusyBox installed prior to overwriting the SafeStrap install, otherwise it will not actually work.
Unsure if related, but if problem persists connect your microSD directly to a PC and look for ".MM_KERNEL_SS-FF_Flashable" folder
===
So I had followed jkruse's locked bootloader guide to use a stock MM ROM with SS support. After using it for a while, I decided to go back to OptimalROM. Unfortunately, every reboot results in stock recovery. I found I can just flash a PB1 kernel through Odin and that fixes it for now- however on the next reboot BAM- back to the same problem.
I assuming this is caused by the current SafeStrap I have installed- which was linked in the MM for locked bootloaders thread.
How can I prevent the kernel from being overwritten every reboot?
On a side note, where can I find the latest stagefreight fix zip for 5.0? I have tried a few but they only seem to work on the 5.1.1 ported ROMs. Tried Stagefreight_Fix_02_Nov.zip and gets stuck at boot. Same situation with Stagefright_Fix_v2_i9505_i337M.zip.
Surely there is a ported fix somewhere for 5.0 roms?

Can you not flash PB1 thru Odin and just root and install OptimalROM via FF that way

Nandr0idC0nsumer said:
Can you not flash PB1 thru Odin and just root and install OptimalROM via FF that way
Click to expand...
Click to collapse
I can always resort to that, but I am trying to figure out what it is that keeps reflashing the MM kernel on reboot. I assume its the MM_Safestrap.apk, but only @jrkruse knows for sure

It appears I was right on the money! After grabbing the SafeStrap.apk from the OK3-V5 root package and installing that version of SS over the MM specific one, I no longer have the issue! I also opened my microSD directly on my computer (not connected through phone USB) and deleted the .MM_KERNEL_SS-FF_Flashable (note the .) folder.
Hope this helps anyone else who downgrades.
Still looking for a solution to the Stagefright Vulns in 5.0 ROMs

Related

[Guide]ATT KitKat leak working with root

I have been trying to get the KitKat leak working in a safestrap rom slot for days. Each time it failed, and I concluded that it was currently incompatible with the hijack Hashcode was using. So, I tried flashing my KK rom to the stock slot, and then I immediately flashed supersu. Voila, KitKat with root on my locked at&t moto x!
The interesting thing is that this method should work for any rom that is compatible with the stock kernels (because locked bootloader wont allow any other kernel). Hopefully this will 'open the floodgates' to flashing AOSP roms on locked devices that can run safestrap.
I AM NOT RESPONSIBLE IF YOU MESS UP YOUR PHONE. With that said, this doesn't touch your bootloader, and you should be able to restore back to stock if there is a problem.
Here are the steps I followed on my locked ATT moto x starting with the at&t stock .51 rom:
1) extract ext4 filesystem image from leak's system.img
2) used android kitchen (thanks dsixda) to cook a flashable rom and fixed some symlinks with help from the updater-script found in dhacker29's 4.4 rom
3) root (pwnmymoto - thanks jcase)
4) install safestrap (thanks Hashcode)
5) copied the rom I cooked to sdcard
6) copied supersu flashable zip to sdcard (thanks chainfire)
7) booted to SS TWRP recovery
8) switched to stock rom slot
9) flashed my cooked rom
10) immediately flashed supersu
11) rebooted into bootloader
12) flashed kitkat kernel: fastboot flash boot boot.img
13) cleared cache and userdata
(I left the modem from the 4.2.2 .54 update)
Rebooted to kitkat with root!
I haven't tested bluetooth, but wifi and gps work. Strangely, the safestrap 'recovery or continue' screen is still there, but the /ss directory is empty. (I would like to know how to manually remove ss, as it is almost certainly not working now.)
I would be happy to share my flashable 4.4 rom, but I noticed that the original leak was taken down. What/where is the smart place to get this up?
I found a place to upload the rom: http://forum.xda-developers.com/showthread.php?p=47451659#post47451659
Hopefully the instructions there are clear...
Can I ask how you extracted from the system.img? I tried to follow the guide that uses ext4_unpacker, but it won't open it. It just says unknown file format. Guessing you did it on a Linux machine?
Ctrl-Freak said:
I have been trying to get the KitKat leak working in a safestrap rom slot for days. Each time it failed, and I concluded that it was currently incompatible with the hijack Hashcode was using. So, I tried flashing my KK rom to the stock slot, and then I immediately flashed supersu. Voila, KitKat with root on my locked at&t moto x!
The interesting thing is that this method should work for any rom that is compatible with the stock kernels (because locked bootloader wont allow any other kernel). Hopefully this will 'open the floodgates' to flashing AOSP roms on locked devices that can run safestrap.
I AM NOT RESPONSIBLE IF YOU MESS UP YOUR PHONE. With that said, this doesn't touch your bootloader, and you should be able to restore back to stock if there is a problem.
Here are the steps I followed on my locked ATT moto x starting with the at&t stock .51 rom:
1) extract ext4 filesystem image from leak's system.img
2) used android kitchen (thanks dsixda) to cook a flashable rom and fixed some symlinks with help from the updater-script found in dhacker29's 4.4 rom
3) root (pwnmymoto - thanks jcase)
4) install safestrap (thanks Hashcode)
5) copied the rom I cooked to sdcard
6) copied supersu flashable zip to sdcard (thanks chainfire)
7) booted to SS TWRP recovery
8) switched to stock rom slot
9) flashed my cooked rom
10) immediately flashed supersu
11) rebooted into bootloader
12) flashed kitkat kernel: fastboot flash boot boot.img
13) cleared cache and userdata
(I left the modem from the 4.2.2 .54 update)
Rebooted to kitkat with root!
I haven't tested bluetooth, but wifi and gps work. Strangely, the safestrap 'recovery or continue' screen is still there, but the /ss directory is empty. (I would like to know how to manually remove ss, as it is almost certainly not working now.)
I would be happy to share my flashable 4.4 rom, but I noticed that the original leak was taken down. What/where is the smart place to get this up?
Click to expand...
Click to collapse
Glad to see locked BLs getting some love. Any chance of KK screenshots? No one seems to have uploaded them on any thread. How has your experience been with it so far?
freak4dell said:
Can I ask how you extracted from the system.img? I tried to follow the guide that uses ext4_unpacker, but it won't open it. It just says unknown file format. Guessing you did it on a Linux machine?
Click to expand...
Click to collapse
This took me a day to figure out. I used simg2img in ubuntu.
anirudh412 said:
... How has your experience been with it so far?
Click to expand...
Click to collapse
The only material problem I am having is battery life - it seems noticeably worse that the att .54 ota version.

[Q] What to do for gaining Root on 5.0?

Hey Guys,
I had CWM installed on my nakaski since forever and used it to flash KK/PA before switching to Official Stock Lollipop which I'm currently on. I'm getting good performance for now and really not looking forward for any custom kernel or L based ROM.
But I'm definitely looking to root my N7, which I've read is not as simple as flashing the 'Update-SuperSU.zip' in custom recovery due to some kernel limitations on SELinux resulting in bootloops.
So right now, I'm wondering what should I do to root the thing, I can see the two options:
1. Flash a custom kernel which supports root and then flash the SuperSU zip in recovery.
2. Wait for CF to make the 'zygote' service method stable in the 2.27B build and flash on stock recovery.
I'm really looking to avoid bootloops at all if possible. I don't have the stock Lollipop image on me anymore and I'm stuck on a slow internet connection.
Can anyone suggest me what should I do?
If you think custom kernel is the way to go, please give a link to the thread of the custom kernel for stock L. (franco seems to be stuck on KK, right?)
PS: Can anyone give me a working mirror to TWRP based recovery for grouper. Their web portal seems down.
amangupta53 said:
Hey Guys,
I had CWM installed on my nakaski since forever and used it to flash KK/PA before switching to Official Stock Lollipop which I'm currently on. I'm getting good performance for now and really not looking forward for any custom kernel or L based ROM.
But I'm definitely looking to root my N7, which I've read is not as simple as flashing the 'Update-SuperSU.zip' in custom recovery due to some kernel limitations on SELinux resulting in bootloops.
So right now, I'm wondering what should I do to root the thing, I can see the two options:
1. Flash a custom kernel which supports root and then flash the SuperSU zip in recovery.
2. Wait for CF to make the 'zygote' service method stable in the 2.27B build and flash on stock recovery.
I'm really looking to avoid bootloops at all if possible. I don't have the stock Lollipop image on me anymore and I'm stuck on a slow internet connection.
Can anyone suggest me what should I do?
If you think custom kernel is the way to go, please give a link to the thread of the custom kernel for stock L. (franco seems to be stuck on KK, right?)
PS: Can anyone give me a working mirror to TWRP based recovery for grouper. Their web portal seems down.
Click to expand...
Click to collapse
Hi, amangupta53...
You're correct in that rooting lollipop is no longer just a simple matter of flashing a root update package via TWRP or CWM...
A modified kernel (boot.img) also need's to be flashed as well.
---
Probably the easiest way of 'pushing' the usual files, (su binary & SuperSU app) AND flashing a modified root compliant kernel/boot.img... all at the same time, and conveniently... is via Chainfire's CF-Auto-Root method.
This is the method I've used to root both my Nexus 7 and my Nexus 9, both running Lollipop.
---
Download to your PC, the CF-Auto-Root-grouper-nakasi-nexus7.zip from Chainfire..
Unzip it to some folder location on your computer/PC.
Boot the Nexus 7 into it's bootloader... and USB connect it to your PC.
Inside the folder containing the CF-Auto-Root file's you've just unzipped... run the CF-Auto-Root script appropriate to your PC... one of these, root-windows.bat, root-linux.sh or root-mac.sh.
---
If your Nexus 7's bootloader is NOT already unlocked, it will unlock it... AND IT WILL WIPE EVERYTHING ON THE DEVICE, essentially performing a factory reset... so, do be careful, and ensure you have everything that matters backed up elsewhere before you begin.
---
Once completed, reboot your Nexus 7, and you should be rooted.
Good luck, and hope this helps.
Rgrds,
Ged.
GedBlake said:
Hi, amangupta53...
You're correct in that rooting lollipop is no longer just a simple matter of flashing a root update package via TWRP or CWM...
A modified kernel (boot.img) also need's to be flashed as well.
---
Probably the easiest way of 'pushing' the usual files, (su binary & SuperSU app) AND flashing a modified root compliant kernel/boot.img... all at the same time, and conveniently... is via Chainfire's CF-Auto-Root method.
This is the method I've used to root both my Nexus 7 and my Nexus 9, both running Lollipop.
---
Download to your PC, the CF-Auto-Root-grouper-nakasi-nexus7.zip from Chainfire..
Unzip it to some folder location on your computer/PC.
Boot the Nexus 7 into it's bootloader... and USB connect it to your PC.
Inside the folder containing the CF-Auto-Root file's you've just unzipped... run the CF-Auto-Root script appropriate to your PC... one of these, root-windows.bat, root-linux.sh or root-mac.sh.
---
If your Nexus 7's bootloader is NOT already unlocked, it will unlock it... AND IT WILL WIPE EVERYTHING ON THE DEVICE, essentially performing a factory reset... so, do be careful, and ensure you have everything that matters backed up elsewhere before you begin.
---
Once completed, reboot your Nexus 7, and you should be rooted.
Good luck, and hope this helps.
Rgrds,
Ged.
Click to expand...
Click to collapse
Thanks Ged.
Seems like I missed CF-Auto Root Method in my list. But I guess it's essentially the automated format of option 1 I listed above. I've already switched to SlimROM 0.8 F2FS which included the M-Kernel and thus easy to root. (A friend pointed it out to me, I took the plunge for F2FS)
Thanks again for the detailed solution. I'm sure it'll be useful for anyone looking to root Stock Lollipop with Stock Kernel.
Cheers!

I337mvlufnc1 bootloader - What are my options?

I picked up a used GS4 JFLTECAN and the battery life on the stock rom is brutal, so I would really like to try something else. I have flashed recoveries kernals and roms before on other devices but have never had to deal with these "locked" boot loaders.
I have the I337mvlufnc1 bootloader and the most recent Android 5.0.1 OTA update from Rogers. My ROM and modem are I337MVLUGOH1
Can I ODIN TWRP at this point? Or will I brick my device?
Here's how I wound up at this point.
I have managed to root by odining SuperUserSU.zip by following these instructions; http://www.google.ca/url?sa=t&rct=j...4gA4TauS3dXnXcIOA&sig2=MHLMfY4z5M21bgTArDKniQ
I installed wakelock detector and a root uninstaller for bloatware as well as greenify to take advantage of root and try to fix battery drain issues. However I did something wrong and now whenever I boot "Package Access Helper" and "System UI" both unfortunately stop. I am also being prompted to select a homescreen every time I boot (touchwiz variants)
Rather than factory resetting to the stock firmware I would prefer to get on something different. any help is appreciated.
Paging @raptor170 ?
arasarn said:
I picked up a used GS4 JFLTECAN and the battery life on the stock rom is brutal, so I would really like to try something else. I have flashed recoveries kernals and roms before on other devices but have never had to deal with these "locked" boot loaders.
I have the I337mvlufnc1 bootloader and the most recent Android 5.0.1 OTA update from Rogers. My ROM and modem are I337MVLUGOH1
Can I ODIN TWRP at this point? Or will I brick my device?
Here's how I wound up at this point.
I have managed to root by odining SuperUserSU.zip by following these instructions; http://www.google.ca/url?sa=t&rct=j...4gA4TauS3dXnXcIOA&sig2=MHLMfY4z5M21bgTArDKniQ
I installed wakelock detector and a root uninstaller for bloatware as well as greenify to take advantage of root and try to fix battery drain issues. However I did something wrong and now whenever I boot "Package Access Helper" and "System UI" both unfortunately stop. I am also being prompted to select a homescreen every time I boot (touchwiz variants)
Rather than factory resetting to the stock firmware I would prefer to get on something different. any help is appreciated.
Paging @raptor170 ?
Click to expand...
Click to collapse
From my understanding with that bootloader is that it will prevent you from downgrading to say 4.3 etc etc. To be extra Safe, have stock firmware files from sammobile handy, but you should be good..... Don't quote me on it tho lol
He was successful on twrp flash, anyone watching this lol, all i337m unlocked
So If anyone else gets a used galaxy s4 here is the procedure to root and install custom recovery with the most recent OTA updates installed. There is no need to worry about any locked bootloader or anything.
Step 1: get root with Odin
http://www.google.ca/url?sa=t&rct=j&...5M21bgTArDKniQ
go to twrp.me
Step 2: flash twrp 2.8.4.0 with Odin
Step 3: flash twrp 2.8.7.0 (or a newer version if one is available) via twrp itself. After 2.8.4.0 TWRP only has .img files released which are to be flashed directly from twrp.
Step 4: Flash a rom.
arasarn said:
So If anyone else gets a used galaxy s4 here is the procedure to root and install custom recovery with the most recent OTA updates installed. There is no need to worry about any locked bootloader or anything.
Step 1: get root with Odin
http://www.google.ca/url?sa=t&rct=j&...5M21bgTArDKniQ
go to twrp.me
Step 2: flash twrp 2.8.4.0 with Odin
Step 3: flash twrp 2.8.7.0 (or a newer version if one is available) via twrp itself. After 2.8.4.0 TWRP only has .img files released which are to be flashed directly from twrp.
Step 4: Flash a rom.
Click to expand...
Click to collapse
Easiest waytp flash the ol s4 great writeup for anyone starting off on the s4. Let me add a step 3a: backup efs in twrp for if the rare case you loose imei, chance of getting it back
raptor170 said:
Easiest waytp flash the ol s4 great writeup for anyone starting off on the s4. Let me add a step 3a: backup efs in twrp for if the rare case you loose imei, chance of getting it back
Click to expand...
Click to collapse
Add this to the first post of the Canadian galaxy s4 mega thread.

stock_N910VVZW2CPG2_VZW updated with FlashFire, Rooted

This is too complicated for me to explain everything but here is my Cheat Sheet !
If you have been flashing you probably already have these files.
1. Odin SamMobile N910VVRU2BPA1_N910VVZW2BPA1_N910VVRU2BPA1_HOME.tar
reboot and factory reset a few times if needed to remove custom icon
2. Odin hsbadr's N910VVRU2BPA1_N910VVRU2CPD1_FullFirmware.tar HERE
3. Unlock with the samsung_unlock_n4-fix PROCESS use SIM card for data. Wi-Fi will not work at this point.
4. Odin twrp-3.0.2-0-trltevzw.tar Uncheck Auto Reboot, Manually boot into TWRP
5. Odin hsbadr's N910VVRU2CPD1_StockRestore.tar HERE
6. TWRP BETA-SuperSU-v2.71-20160331103524, Factory Reset, boot system
7. Use FlashFire to Flash firmware package SamMobile N910VVRU2CPG2_N910VVZW2CPG2_N910VVRU2CPG2_HOME.tar
( ! System and Cache only ! )
SAME as the thread Safe System Updates_6.0.1 MM_FlashFire, dm-verity work around, SM-N910V
Except Now that SamMobile has posted 2CPG2 I was able to skip steps and go straight to Flashing the firmware package with FlashFire.
No need to do over the air updates.
-----------------------------------------------------------------------------------------------
Note: I was able to skip the recommended rooting of 5.1.1
I did not do the unlock using Kingroot until step 3 and I did not permanent root with Super Su until step 6.
No matter how you get there the phone has to be on [Firmware] [MM] [6.0.1] [RetEd/DevEd] Safe Upgrade to Marshmallow [N910VVRU2CPD1] then you can use FlashFire.
I have been flashing and playing with roms on many devices and there is something I don't understand. Why can't someone inject root into the factory tar file and make the upgrade a much simpler process? If our devices once rooted are considered the same as a developer edition, why can't we simply flash whatever image we want?
PaulPizzRom is just as good......
tbtaf said:
I have been flashing and playing with roms on many devices and there is something I don't understand. Why can't someone inject root into the factory tar file and make the upgrade a much simpler process? If our devices once rooted are considered the same as a developer edition, why can't we simply flash whatever image we want?
Click to expand...
Click to collapse
OR BETTER!!!!!!
Think you could fix your 'HERE' links in your OP?
hsbadr's CPD1 is already rooted or something? I just re-went through the unlock process and i thought if you flashed a stock firmware it re-locked the bootloader?
azreark1 said:
Think you could fix your 'HERE' links in your OP?
hsbadr's CPD1 is already rooted or something? I just re-went through the unlock process and i thought if you flashed a stock firmware it re-locked the bootloader?
Click to expand...
Click to collapse
Chick on the link in OP
Safe System Updates_6.0.1 MM_FlashFire, dm-verity work around, SM-N910
That's all I got right now
I am in : [ROM] [5.1.1] Kyubi Note 5 Port Final [N910VVRU2BPA1] [2/23/16]
Can i flash stock rom 5.1.1 by flashfire?
Could someone please upload the ota zip file only
I'm on 5.1.1 PA1/PD1 with TWRP installed and would love to move to 6.0...would I have to start all over to accomplish this or could I begin in the middle of your guide where I am?
thanks!!
Nevermind..I'm on 6.0
Many thanks!
mistake
Posted too soon. Need to delete and repost later with more info

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

Categories

Resources