LineageOS on a vzw Galaxy S5? - Galaxy S 5 Q&A, Help & Troubleshooting
Can I put LineageOS on my Galaxy S5 using SafeStrap? If not, would Odin do the trick instead?
What, if anything, do I need to do to maintain root?
Do I need to unlock the bootloader before flashing the ROM?
Do the steps in the above link work on unlocking the verizon bootloader or will I make a brick?
If there's a link to getting LineageOS onto my Verizon S5 while keeping root please point me in the right direction. Thank you.
androidman807 said:
Can I put LineageOS on my Galaxy S5 using SafeStrap? If not, would Odin do the trick instead?
What, if anything, do I need to do to maintain root?
Do I need to unlock the bootloader before flashing the ROM?
Do the steps in the above link work on unlocking the verizon bootloader or will I make a brick?
If there's a link to getting LineageOS onto my Verizon S5 while keeping root please point me in the right direction. Thank you.
Click to expand...
Click to collapse
you first need to root then unlock bootloader then install twrp then flash Lineage and Gapps and your all set , all information regarding how to root and unlock bootloader are in the vzw section , do make a full back up of your sdcard(micro sd card) to your computer because unlocking the bootloader will wipe/format your memory card(keep that in mind)
also i suggest you update your modem and bootloader , just in case you would like to test the ported rom which most of them run on a higher bootloader and with a old bootloader you will face issues with wifi and nav buttons specially with the vzw variant (i also have a vzw) , update it to i think the highest so far by @jrkruze is qf2 , for example the skiesrom (a s8 port) runs on a qf5 bootloader but updating vzw bootloader to qf2 fixes the wifi and nav button bugs.
Good Luck and also do properly read the instructions word for word.
I'm so grateful for your response. You've been down this road and know the traps. I believe my original post has the right thread on unlocking the bootloader for vzw, and I appreciate the warning about it erasing the micro-sd card.
Two follow-up questions:
Where can I find the update for the modem?
Also to avoid the wifi and nav problems, do I want the QF2 or QF5? And where do I find those? Here it says to use latest bootloader (QA1) with QF2 modem. Does that make sense? If so I just need to know where to find those.
Thank you again so very much.
KazuDante said:
you first need to root then unlock bootloader then install twrp then flash Lineage and Gapps and your all set , all information regarding how to root and unlock bootloader are in the vzw section , do make a full back up of your sdcard(micro sd card) to your computer because unlocking the bootloader will wipe/format your memory card(keep that in mind)
also i suggest you update your modem and bootloader , just in case you would like to test the ported rom which most of them run on a higher bootloader and with a old bootloader you will face issues with wifi and nav buttons specially with the vzw variant (i also have a vzw) , update it to i think the highest so far by @jrkruze is qf2 , for example the skiesrom (a s8 port) runs on a qf5 bootloader but updating vzw bootloader to qf2 fixes the wifi and nav button bugs.
Good Luck and also do properly read the instructions word for word.
Click to expand...
Click to collapse
androidman807 said:
I'm so grateful for your response. You've been down this road and know the traps. I believe my original post has the right thread on unlocking the bootloader for vzw, and I appreciate the warning about it erasing the micro-sd card.
Two follow-up questions:
Where can I find the update for the modem?
Also to avoid the wifi and nav problems, do I want the QF2 or QF5? And where do I find those? Here it says to use latest bootloader (QA1) with QF2 modem. Does that make sense? If so I just need to know where to find those.
Thank you again so very much.
Click to expand...
Click to collapse
The Latest bootloader (after you unlocked your current bootloader) : https://forum.xda-developers.com/showpost.php?p=73734257&postcount=3143
latest modem : https://forum.xda-developers.com/showpost.php?p=61802396&postcount=1 ( use the ones in the odin section , you will need to be bootloader unlocked and have odin+latest samsung drivers installed)
latest twrp : https://dl.twrp.me/klte/ ( the ones that ends with .tar are for flashing using odin , since you dont have twrp yet but flashing twtp comes last after rooting and unlocking bootloader and updating bootloader then update the modem then odin flash twrp then have lineageos and nougat gapps on memory card. reboot while holding vol up and home button to reboot into twrp to install lineageos system then gopengapps , afterwards you can install magisk to have root access on lineageOS as well .
p.s after you unlock bootloader and the system reboots normally return to download mode then use odin to flash twrp , i just noticed(remembered that latest bootloader update uses twrp and not safestrap recovery.
to unlock current bootloader : https://forum.xda-developers.com/showpost.php?p=71202995&postcount=3
Thank you so much. So if I understand right it's:
1) UNLOCK bootloader
2) UPDATE bootloader (latest is QF2)
3) update modem (latest tar was QI2)
4) flash TWRP from Odin (you linked to klte version; qualcomm but I have vzw)
5) install LineageOS and gapps from TWRP
6) install magisk from TWRP to get root
Is that correct?
Correct bootloader and modem versions?
OK to use klte for Verizon?
Magisk is for root, done last, and not superSu?
If all those are Yes, then I guess the prep work is done and now I just have to bite the bullet, do a safestrap and titanium backup and dive in.
Thanks again - I really do appreciate it.
KazuDante said:
The Latest bootloader (after you unlocked your current bootloader) : https://forum.xda-developers.com/showpost.php?p=73734257&postcount=3143
latest modem : https://forum.xda-developers.com/showpost.php?p=61802396&postcount=1 ( use the ones in the odin section , you will need to be bootloader unlocked and have odin+latest samsung drivers installed)
latest twrp : https://dl.twrp.me/klte/ ( the ones that ends with .tar are for flashing using odin , since you dont have twrp yet but flashing twtp comes last after rooting and unlocking bootloader and updating bootloader then update the modem then odin flash twrp then have lineageos and nougat gapps on memory card. reboot while holding vol up and home button to reboot into twrp to install lineageos system then gopengapps , afterwards you can install magisk to have root access on lineageOS as well .
p.s after you unlock bootloader and the system reboots normally return to download mode then use odin to flash twrp , i just noticed(remembered that latest bootloader update uses twrp and not safestrap recovery.
to unlock current bootloader : https://forum.xda-developers.com/showpost.php?p=71202995&postcount=3
Click to expand...
Click to collapse
androidman807 said:
Thank you so much. So if I understand right it's:
1) UNLOCK bootloader
2) UPDATE bootloader (latest is QF2)
3) update modem (latest tar was QI2)
4) flash TWRP from Odin (you linked to klte version; qualcomm but I have vzw)
5) install LineageOS and gapps from TWRP
6) install magisk from TWRP to get root
Is that correct?
Correct bootloader and modem versions?
OK to use klte for Verizon?
Magisk is for root, done last, and not superSu?
If all those are Yes, then I guess the prep work is done and now I just have to bite the bullet, do a safestrap and titanium backup and dive in.
Thanks again - I really do appreciate it.
Click to expand...
Click to collapse
yes thats correct , also there is no vzw variant of lineage since vzw is merged under klte , so every rom you download the one you have to choose is klte unless the dev make a build for each variant but not likely to happen anymore.
A very basic assumption may have been overlooked, but it seems the CID on my lollipop PB1 is 11 Toshiba eMMC. Method 2 of unlocking stopped at step 4 with an error in the terminal screen indicating this is only for Samsung eMMCs. Is it possible to unlock an 11, and if so, where would I find those steps?
KazuDante said:
yes thats correct , also there is no vzw variant of lineage since vzw is merged under klte , so every rom you download the one you have to choose is klte unless the dev make a build for each variant but not likely to happen anymore.
Click to expand...
Click to collapse
androidman807 said:
A very basic assumption may have been overlooked, but it seems the CID on my lollipop PB1 is 11 Toshiba eMMC. Method 2 of unlocking stopped at step 4 with an error in the terminal screen indicating this is only for Samsung eMMCs. Is it possible to unlock an 11, and if so, where would I find those steps?
Click to expand...
Click to collapse
sadly cid 11 cannot be unlocked , best option is to only change current S5 with another S5 and hope its a CID 15 , or sadly get another phone but check xda forum to see if it has any latest custom roms and bootloader can be unlocked.
But for CID 11 theres no unlocks for those , only thing is safestrap roms that allows you to run ports like PhoenixRom and other stock but modded roms but using safestrap
Thanks you so much again. How can I tell which ROMs are stock I can use in safestrap (like Phoenixrom) and which are custom I can't use (like LineageOS)?
And if I have a safestrap backup to my sd card of my stock lollipop and don't like phoenix (which seems to be MM) can I restore from safestrap back to my stock LL?
KazuDante said:
sadly cid 11 cannot be unlocked , best option is to only change current S5 with another S5 and hope its a CID 15 , or sadly get another phone but check xda forum to see if it has any latest custom roms and bootloader can be unlocked.
But for CID 11 theres no unlocks for those , only thing is safestrap roms that allows you to run ports like PhoenixRom and other stock but modded roms but using safestrap
Click to expand...
Click to collapse
androidman807 said:
Thanks you so much again. How can I tell which ROMs are stock I can use in safestrap (like Phoenixrom) and which are custom I can't use (like LineageOS)?
And if I have a safestrap backup to my sd card of my stock lollipop and don't like phoenix (which seems to be MM) can I restore from safestrap back to my stock LL?
Click to expand...
Click to collapse
that im not sure about that so i cant give you any pointers since i have not done anything with safestrap besides the process to unlock the bootloader.
Thanks anyway. It seems it should work, since safestrap won't disappear. Maybe I should post a new thread. Thank you again for all your time.
KazuDante said:
that im not sure about that so i cant give you any pointers since i have not done anything with safestrap besides the process to unlock the bootloader.
Click to expand...
Click to collapse
I am also essentially looking to install LineageOS on my Galaxy S5, but before proceeding, I just wanted to make sure that what I'm looking to do is correct. Currently I am running an old version of PhoenixROM with an old unlocked bootloader. I know that I will need to update the bootloader in order to prevent issues, such as wifi not working.
Should all I need to do is follow JKruse's instructions here, flashing LineageOS as the last and final step? I'm hoping that it is this easy, but I do have my doubts and that is why I am asking on here for advice.
Thank you to all in advance!
Related
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.
[Guide][How to]Update Bootloader/Firmware to OOS3/H2OS2 w/o installing OOS/H2OS
Okay guys first let me tell you why I have created a new thread just for updating the BL and Firmware , I know we already have methods of updating like: 1. flashing the full OOS3 zip through stock recovery ,this method is quite simple for the ones who are on stock recovery and just want to update their OOS version.If you fall in this category then you have no purpose here,you may leave. 2. Is method provided by our fav helping hand @Joshwin Aranha ,that method is sure for the rest of us who dont fall in the above category,but is way too long,although simple and effective still "long". I created this thread to help the CM13(Official or Sultan's)//any custom rom using new BL,users who want to update their BL without flashing the OOS through the tedious way just to update BL and users who are stuck on bootlogo due to old BL with roms using new BL. Here I will guide you through the required steps to update our bootloader "In easiest and fastest way without wiping and restoring anything". So what are we waiting for ,lets start . Prerequisites you will need two files for this process,nothing else. 1 . First one is BLUpdater zip --->Here. 2. Second is TWRP compiled from latest sources use either This or the one from Here<--use v41 or use Sultan's from Here OR if you are Martin's fan like me and want to use his MutiRom TWRP goHere. PS:I am assuming you have Unlocked Bootloader and have either official/blu_spark/sultan's/ Multirom TWRP installed,in a working condition on OOS2.x BL(if not what are you doing here). Note: make sure oem unlocking is checked in developer options in your current rom,else updating the BL may cause it to get locked ,and you will have to unlock it again and flash the recovery manually through fastboot itself. Now the steps 1.First copy both of the above files in your sdcard or otg or ext-sdcard,any place accessible in recovery. 2. Now boot into recovery Choose Install and choose the "OPXBLUpdateOOS3.1" zip and flash it. 3. Don't reboot now ,go to Install again ,this time use "Install Image" button in lower right corner,navigate to folder where you copied the new TWRP,you should be able to see the file,select it ,choose recovery in the next menu and flash. NOTE:If you chose to use Sultan's recovery.zip then just flash it normally. 4. Don't reboot come back to TWRP home ,goto reboot and recovery ,if TWRP says no OS installed ignore it. Now voila you should have updated your firmware/BL.Congrats. You can now install any rom that supports the new BL.Older roms won't boot on the new MM BL.So check the rom thread before installing the rom and later on quacking here about your device being stuck at bootlogo. Notes i)Neither I nor XDA will be responsible if your OPX bricks or explodes or ditches you and flies to space. ii)We are not touching system partition so last installed ROM will be intact. iii)This guide will leave you into bootable rom only if you have a rom installed that works on latest firmware. iv)This can also be used to restore all your OPX partitions back to OOS3.x partition state,if you messed any. v)In case you are using latest nightly (cm13) and face bootloop - go Here psst:If you are not diggin the new BL,and wanna downgrade again ,back to old BL,check this post. PS: (second one,I know) This guide was made by taking inspiration from Joshwin's post and devtry method. Also click Thanks if I helped you
matwaking said: Okay guys first let me tell you why I have created a new thread just for updating the BL and Firmware , I know we already have methods of updating like: 1. flashing the full OOS3 zip through stock recovery ,this method is quite simple for the ons who are on stock recovery and just want to their OOS version.If you fall in this category then you have no purpose here,you may leave. 2. Is method provided by our fav helping hand @Joshwin Aranha ,that method is sure for the rest of us who dont fall in the above category,but is way too long,although simple and effective still "long". So I created this thread just to shorten the process provided by Joshwin.I also created this thread to help the official CM13 users who have problem with latest nightlies due to new bootloader or are stuck in bootlogo. ... PS: (second one,I know) This guide was made by taking inspiration from Joshwin's post and devtry method. Also click Thanks if I helped you Click to expand... Click to collapse Booomshkalaka!!! Great guide, can't test (already have new bootloader and too lazy to switch back but look very good. Thx to all Kurt
Kurt Krummbein said: Booomshkalaka!!! Click to expand... Click to collapse Lol . Thanks mate.
Will this work if I'm in bluspark twrp but the previous version..? Or do I have to change to official twrp?
jonrodz said: Will this work if I'm in bluspark twrp but the previous version..? Or do I have to change to official twrp? Click to expand... Click to collapse Will work with any twrp,no requirement of official one.
Thanks, bro. One more doubt. I'm currently on DU rom with custom kernel... Do you think rom will boot after this..?
jonrodz said: Thanks, bro. One more doubt. I'm currently on DU rom with custom kernel... Do you think rom will boot after this..? Click to expand... Click to collapse No it wont,right now almost all the custom roms need to update to support new firmware.Only latest cm13 nightlies are booting now,also aosp compiled by olddroid for new BL(shh its only for testers right now) also maybe the MIUI8 port ,just posted in the forums.
I'm a litte bit confused. Currently I'm on nighty October 1st. (cm-13.0-20161001-NIGHTLY-onyx.zip) Can i update the Bootloader with your method and after that booting up my current nightly version? Or do I have to update after the bootloader update to nightly version 12 (the currently latest)?
jerikooo said: I'm a litte bit confused. Currently I'm on nighty October 1st. (cm-13.0-20161001-NIGHTLY-onyx.zip) Can i update the Bootloader with your method and after that booting up my current nightly version? Or do I have to update after the bootloader update to nightly version 12 (the currently latest)? Click to expand... Click to collapse no update the BL using the steps above ,then flash the latest nightly.That way it would be good. Or you can flash nightly first then update BL.Choice is yours.I recommend updating the BL first.
I followed your guide with a locked bootloader, and now I'm in bootloops . Just suggest you put a big red "make sure your bootloader is unlocked" in the steps, not in the footnote.
Duplicate post.Deleted
ccaappton said: I followed your guide with a locked bootloader, and now I'm in bootloops . Just suggest you put a big red "make sure your bootloader is unlocked" in the steps, not in the footnote. Click to expand... Click to collapse Reboot into fastboot mode and Code: fastboot oem unlock And using a custom recovery and custom rom makes me assume one have unlocked bootloader
matwaking said: Reboot into fastboot mode and Code: fastboot oem unlock And using a custom recovery and custom rom makes me assume one have unlocked bootloader Click to expand... Click to collapse Thanks! I actually relocked my bootloader not long after installed cm13, and disabled "unlock oem" in "developer settings"(I don't know why I did this). So both system and rec is inaccessible, and fastboot is useless in this case. Fortunately I followed the unbrick guide: http://forum.xda-developers.com/oneplus-x/general/guide-mega-unbrick-guide-hard-bricked-t3272108 and get the old bootloader back. Now I could enter CM13-09-28 with all my data intact. Just hope to let people know the hard lesson I learned, and how to deal the bootloops. And guys, NEVER RELOCK BOOTLOADER AGAIN!
ccaappton said: Thanks! I actually relocked my bootloader not long after installed cm13, and disabled "unlock oem" in "developer settings"(I don't know why I did this). So both system and rec is inaccessible, and fastboot is useless in this case. Fortunately I followed the unbrick guide: http://forum.xda-developers.com/oneplus-x/general/guide-mega-unbrick-guide-hard-bricked-t3272108 and get the old bootloader back. Now I could enter CM13-09-28 with all my data intact. Just hope to let people know the hard lesson I learned, and how to deal the bootloops. And guys, NEVER RELOCK BOOTLOADER AGAIN! Click to expand... Click to collapse Well no fix without any problems hehehe,.Haapy 4 u. Click that button if you think my posts are useful
Is this enough to install CM14 or do i have to install the whole room and them flash CM14?
Manelit said: Is this enough to install CM14 or do i have to install the whole room and them flash CM14? Click to expand... Click to collapse taking you wanna flash ashwins cm14 right. You just wanna follow the instructions in first post and then flash the cm14.No need to install the whole Oos zip. This way you should have updated BL and working cm14. Just flash the cm14 after booting into new TWRP
I've just followed the procedure from OP and all went smooth as butter. Thanks Directly after that (without reboot) I've installed the latest CM13 (with GApps) and Arsenic R24. Working as a charm
slaav said: I've just followed the procedure from OP and all went smooth as butter. Thanks Directly after that (without reboot) I've installed the latest CM13 (with GApps) and Arsenic R24. Working as a charm Click to expand... Click to collapse Press that sweet sweet button mate
1.First copy both of the above files in your sdcard or otg or ext-sdcard,any place accessible in recovery. 2. Now boot into recovery Choose Install and choose the "OPXBLUpdateOOS3.1" zip and flash it. 3. Don't reboot now ,go to Install again ,this time use "Install Image" button in lower right corner,navigate to folder where you copied the new TWRP,you should be able to see the file,select it ,choose recovery in the next menu and flash. 4. Don't reboot come back to TWRP home ,goto reboot and recovery ,if TWRP says no OS installed ignore it. Click to expand... Click to collapse Hi, everyone I'm accidentally reboot device after second step. Now device freezing on "+1 powered by android". Can I remove this zip, or... what can I do next?)
walsash said: Hi, everyone I'm accidentally reboot device after second step. Now device freezing on "+1 powered by android". Can I remove this zip, or... what can I do next?) Click to expand... Click to collapse u can flash bluespark twrp via fasboot Sent from my ONE E1003 using XDA-Developers mobile app
Need help flashing ROM on I545
Hi it is the first time I am flashing Android ROM. I have done some reading already. Before I start, I still have a few questions and also want to make sure I am doing it right. I own the Galaxy S4 Verizon I545. It is running Samsung ROM Android 4.4.2, Baseband I545VRUFNC5. My goal is to flash a new ROM with recent Android versions, hopefully 7.1.1 (but I would settle with Marshmallow if that is more stable), it can be close to AOSP, I don't need ROMs with extra features. In my understanding, the bootloader is locked, it will only load signed kernels and recovery. And then the kernel would load the system. In order to flash the system, it is best to flash the recovery first with TWRP. TWRP is modded with loki hack so it would load with the locked bootloader. So here are my questions: 1. Does it matter which firmware/baseband I am currently on? For some phones (LG G2) I heard newer firmware fixed the loki hack. Should I update to the latest Samsung rom or leave it at NC5? 2. I don't see many ROM posted for the i545, which one is the most recent and reasonable stable? The Cyanogen website is down, should I try LineageOS? 3. I see different instructions for flashing TWRP. Can I flash it with just Odin? Some instruction mentioned rooting the phone first with KingRoot or other root, and then use dd. Does the phone have to be rooted? (I prefer not to if it is not necessary) 4. If after I flashed recovery, it fails to boot into TWRP, what can I do to restore everything to default? 5. The kernel will be untouched in the process right? I am only flashing recovery and system ROM, and the kernel will work fine with the new system ROM? Here are the step and software I plan to use: 0. reset the phone to factory 1. use Odin to flash TWRP 2.8.7 2. download a ROM compatible with I545 and place it on the phone 3. flash the system using TWRP Any feedback would be appreciated. PS: Also I have a LG G2 D801. I would flash that phone instead if it is easier. I just want to get started and learn some things along the way.
https://forum.xda-developers.com/galaxy-s4-verizon
Oh Sorry. Didn't notice there is another forum. Should I repost there?
Yes.
1. Yes, it does matter. As you said, newer firmwares have fixed the exploits which make the phone harder to hack. 2. Any ROM should support your phone. They are generally unified. 3. In the name of anything holy, do not root with KingRoot. If you want to root, then the only way to go is CF-Auto-Root. Rooting is sometimes necessary because recovery won't always install with Odin. 4. Flash stock ROM. 5. Kernels are specific to ROMs. So no, the kernel won't be untouched.
verizon s5 on pd1 mm rootable or not?
Hi all, I really need some help here. I am reading in some stickied tutorials that mm is not rootable, and on some others it says it may be rootable if your mmc begins with 15 and may be able to unlock bootloader. I don't know which to go by here. My sons phone is a verizon s5, on pd1 and has mmc number beginning with 15. I really want magisk in it as some apps we use simply don't work with straight root. I have scoured the internet in hopes of finding the info needed and came up with too many conflicting reports so I came back to ask the experts here. However, even the search function here still leads me to some conflicts. Can someone please link me to a tutorial that I can use to root his phone? Any help is greatly appreciated. Thank you in advance.
tattmann said: Can someone please link me to a tutorial that I can use to root his phone? Click to expand... Click to collapse You can only directly root PD1 (or any MM firmware) if the phone's bootloader is unlocked already. SM-G900V's bootloader is locked by default, CID15 means that it can be unlocked. In the case if rooting is possible (CID15) for Android 6.0 (PD1 is a 6.0 firmware) you'll need to: 1. Flash a firmware which allows direct rooting. Modern method is to flash COMBINATION firmware. This rooting has nothing to do with the future rooting of your PD1, this rooting is for unlocking the bootloader. 2. Gain root and install SafeStrap recovery. 3. Flash a MM (say, PD1) bootloader and unlock it. 4. Download stock PD1 firmware and remove the bootloader from it. 5. Flash this firmware with Odin. The result of these operations will be a SM-G900V phone with stock PD1 firmware and unlocked bootloader. Now you can root your PD1. 6. Download TWRP from their site and flash it with Odin. 7. Download Magisk zip-file. 8. Flash Magisk zip-file with TWRP.
ok, lengthy process lol. Is ok, I will start looking for the files to download and get everything set up. Thank you for your time and for replying. UPDATE: I got it. The phone is now on resurrection remix with twrp and magisk. Thank you for your help!
Need help jumping back into things - Unlock bootloader, update TWRP
Hey I've been out of the rooting/custom rom scene for a while and would love to get back in. I have a rooted Verizon S5 with Safestrap 3.75/TWRP 2.7.1.0, Android 4.4.2 and 15xx eMMC CID and I would like to install the latest LineageOS version. From what I understand, in order to get to my goal of installing the latest LineageOS I would need to: 1. Unlock my bootloader (essentially turning my retail S5 into a Dev Edition) 2. Install latest TWRP version 3. Wipe and install LineageOS I don't know if my bootloader is unlocked already or not. When booting, the lock symbol is open and it says 'unlocked' but I'm not sure if that is for the bootloader or if that is for carrier locking as I do remember unlocking my S5 to work with other carriers once I left Verizon. I don't think my bootloader is unlocked as that is a pretty recent development and I have been out of this scene for a few years. Is there another way to make sure mine is locked or not? From what I read, I must have TWRP 3.2.1-0 or newer to get LineageOS. Is there a way to just update Safestrap with a newer TWRP version or do I need to uninstall completely? How can I do this without bricking my device? I feel like this is where I am going to have the most issues as none of the threads I have read really show any instructions for people in this situation. Once my device has the right TWRP version and unlocked bootloader I think the install of the rom should go smoothly but I want to make sure that I don't brick my device on the way there. Any help would be appreciated.
mint_optics said: Hey I've been out of the rooting/custom rom scene for a while and would love to get back in. I have a rooted Verizon S5 with Safestrap 3.75/TWRP 2.7.1.0, Android 4.4.2 and 15xx eMMC CID and I would like to install the latest LineageOS version. From what I understand, in order to get to my goal of installing the latest LineageOS I would need to: 1. Unlock my bootloader (essentially turning my retail S5 into a Dev Edition) 2. Install latest TWRP version 3. Wipe and install LineageOS I don't know if my bootloader is unlocked already or not. When booting, the lock symbol is open and it says 'unlocked' but I'm not sure if that is for the bootloader or if that is for carrier locking as I do remember unlocking my S5 to work with other carriers once I left Verizon. I don't think my bootloader is unlocked as that is a pretty recent development and I have been out of this scene for a few years. Is there another way to make sure mine is locked or not? From what I read, I must have TWRP 3.2.1-0 or newer to get LineageOS. Is there a way to just update Safestrap with a newer TWRP version or do I need to uninstall completely? How can I do this without bricking my device? I feel like this is where I am going to have the most issues as none of the threads I have read really show any instructions for people in this situation. Once my device has the right TWRP version and unlocked bootloader I think the install of the rom should go smoothly but I want to make sure that I don't brick my device on the way there. Any help would be appreciated. Click to expand... Click to collapse The latest instructions to root your phone & more can be found at https://forum.xda-developers.com/verizon-galaxy-s5/development/rom-t3855148.