If your booted back to twrp try to flash lineage now or boot to stock samsung android 6 rom that you flashed during the process
Sent from some device I modified
Goes through Sam Boot twice. Attempts lineage once, then boots back to recovery.
If your booted back to twrp try to flash lineage now or boot to stock samsung android 6 rom that you flashed during the process
Sent from some device I modified
I have this device...x3 one is on lineage 16.0, one is on lineage 14.1 and one is on stock marshmallowGoes through Sam Boot twice. Attempts lineage once, then boots back to recovery.
I have this device...x3 one is on lineage 16.0, one is on lineage 14.1 and one is on stock marshmallow
With magisk.
Problem is probably with TWRP. Which version do you have?
Edit: I probably won't be back on this thread for a while, so I'll lay out my suspicion. I think you are still using twrp that comes from the OP. Update to the latest version of twrp then to the super clean install method recommended by @curiousrom. Also update your baseband with the package from lineage developer haggertk found here
https://androidfilehost.com/?w=files&flid=142906
I'm not sure why @jrkruse is being so unhelpful they have been instrumental in supporting this device over the years and should have been able to help you. In the future feel free to tag or message me, @curiousrom is also a great resource for this device.
No need to get hot, it wasn't an attack. I was just surprised you weren't able to help. This is a very common problem, and updating twrp is the most obvious and common solution. I'm thankful for all the work that you have put into this device, and even stated so in my post. Take a deep breath and try to see the good instead of the bad.Are you really calling me unhelpful. Dude everything I have posted here has been tried and tested by thousands of people but I have long since moved on. Lineage wasn’t even a thing when I left this device so excuse me if im not very helpful on lineage and excuse me if I don’t check these threads daily
Sent from some device I modified
I have this device...x3 one is on lineage 16.0, one is on lineage 14.1 and one is on stock marshmallow
With magisk.
Problem is probably with TWRP. Which version do you have?
Edit: I probably won't be back on this thread for a while, so I'll lay out my suspicion. I think you are still using twrp that comes from the OP. Update to the latest version of twrp then to the super clean install method recommended by @curiousrom. Also update your baseband with the package from lineage developer haggertk found here
https://androidfilehost.com/?w=files&flid=142906
I'm not sure why @jrkruse is being so unhelpful they have been instrumental in supporting this device over the years and should have been able to help you. In the future feel free to tag or message me, @curiousrom is also a great resource for this device.
If your booted back to twrp try to flash lineage now or boot to stock samsung android 6 rom that you flashed during the process
Sent from some device I modified
I have everything you need to put you on what ever firmware you choose with unlocked bootloader if android 6 is what you want then flash that stuff
Sent from some device I modified
...lineage 17.1 (Which i'm running), rooted? lol This has been a problem. Magisk edits the boot, so kind of asses it out...
Appreciate it. Guess i should read more. =XMagisk modifies boot.img which is the kernel.
Magisk does not touch the S5's bootloader which is aboot.
So you can install Magisk safely on your S5 G900V without re-locking the bootloader.
***
See, I still have my S5. I haven't tried Safe strapping 6.0.1
But if we can flash zips via SS to a stock MM build, hold my beer, I still thinks that Marshmallow is rootable on CID 11. Which is what I got.
Wasn't that the major milestone on the Note8 and 9.0?
But we have to think. The CID 11 G900V is able to be dirty cow patched on 6.0.1 && Has a leaked flash programmer &&&& we thus have an EDL CLEAN Safestrap potentially.
Given the Trinity. Root is within sight. I just need a new computer. I got hard drives w/ WSLv2, Ubu20.04, and x86 9.0.
If I can get a setup I might just be able to spruce up that GHR console for stock Marshmallow without trying to RE a rawprogram XML.
I'm still looking to try.
I actually have a way you can boot safestrap on marshmallow on s5 without using a computer. Even if dirty cow root worked it’s only temporary so safestrap is much better option
Sent from my iPhone using Tapatalk
Greetings from the AT&T S5 Forum!
We've recently discovered the usability of engineering firmwares in our journey to get root, as outlined here: https://xdaforums.com/att-galaxy-s5/general/guide-merry-christmas-heres-t3516196
...
Directions:
Before you get going, use this APK to check your eMMC chip's CID:
eMMC_CID_Checker_.apk[/SIZE][/B][/CENTER]
[/HIDE]
if phone is CID=11 running 6.0, is it possible to root even if it's only temporary while staying on stock 6.0? I just want to freeze/uninstall all the garbage on this phone...
I just cleaned them up a little I'll Pm you the changesThe OP has been updated to reflect @jrkruse 's new instructions
I cant seem to get the link for locked bootloaders to work... But does this mean that CID 11 people will finally have unlocked bootloaders and can install Lineage OS? may seem like a dumb question...