Related
Does anyone know if these are cross-compatible in terms of KDZ and ROMs? people are having success with the Bell variant, but someone said they had difficulty rooting the Rogers variant. I have yet to see anyone with a Rogers or Bell G2.
The KDZ files are named differently and have different sizes for all 3. Someone reported that Cleanrom ATT works with Bell variant, just remove boot.img. Except that the Bell D803 is the most expensive...
I just want to know if the Rogers one is compatible with ATT stuff.
I don't see why it should be an issue. The phones are all the same besides the minimal bloat each carrier throws on their. When i rooted my Bell G2, it was using a root method meant for a Rogers D803. Cleanrom should flash fine on any of the D803s provided you delete the boot.img
custo said:
I don't see why it should be an issue. The phones are all the same besides the minimal bloat each carrier throws on their. When i rooted my Bell G2, it was using a root method meant for a Rogers D803. Cleanrom should flash fine on any of the D803s provided you delete the boot.img
Click to expand...
Click to collapse
Ok thanks. But do you know exactly why we have to delete the boot.img?
droid_<3er said:
Ok thanks. But do you know exactly why we have to delete the boot.img?
Click to expand...
Click to collapse
Yes because the kernel differences between the different models. They use different radio bands, and people have been having modem issues so until that is sorted do not use kernels outside of the D803 variants. It may be something ridiculously simple like a zip addon to flash overtop to correct the minor differences but until then don't do it or at least make sure you TWRP your entire install first.
wy2sl0 said:
Yes because the kernel differences between the different models. They use different radio bands, and people have been having modem issues so until that is sorted do not use kernels outside of the D803 variants. It may be something ridiculously simple like a zip addon to flash overtop to correct the minor differences but until then don't do it or at least make sure you TWRP your entire install first.
Click to expand...
Click to collapse
So for now, we can flash ATT stock-based roms without minding the kernel?
OK so I have no clue really want safestrap is really. I've only had phones that I could unlock my bootloader.
I guess my questions are is how much different is safestrap vs unlocked bootloader and did Verizon/Samsung lock this thing down to the point we can't unlock this thing.?
I just bought this phone on Verizon edge and had no knowledge about this thing being locked down.
Simple search will help.
Safe strap allows you to Flash stock ROMs and stock kernels. It is not a bootloader bypass. You cannot have recovery at this time. The chance of an actual bootloader unlock and/or recovery is slim.
We currently do have root.
If you want to do anything other than flash stock based ROMs and kernels (when SS is available, which is likely soon), then you should use a different device or get the Dev edition when it comes out.
You should do more research before putting that much money on a device down. I want the Note3 very much, but I much prefer a device with more flexibility, even if it isn't as badass.
I've had safe strap on my bionic and flashed asop ...but why would anyone on this device want asop??? ...that would not make a lot of..."touchwiz" lol.
Thanks for the reply. Yes your correct but no need to be an douche. Yes search answers questions but people who have used safestrap can sometimes provide better answers. This is the q&a section so that means you can ask questions. Anyways thanks for part of your reply.
Sent from my SM-N900V using xda app-developers app
jprovan1 said:
Thanks for the reply. Yes your correct but no need to be an douche. Yes search answers questions but people who have used safestrap can sometimes provide better answers. This is the q&a section so that means you can ask questions. Anyways thanks for part of your reply.
Sent from my SM-N900V using xda app-developers app
Click to expand...
Click to collapse
I hope that was for the jerk and not the joke.....
Was for the jerk. I liked the joke
Sent from my SM-N900V using xda app-developers app
xdadevnube said:
Simple search will help.
Safe strap allows you to Flash stock ROMs and stock kernels. It is not a bootloader bypass. You cannot have recovery at this time. The chance of an actual bootloader unlock and/or recovery is slim.
We currently do have root.
If you want to do anything other than flash stock based ROMs and kernels (when SS is available, which is likely soon), then you should use a different device or get the Dev edition when it comes out.
You should do more research before putting that much money on a device down. I want the Note3 very much, but I much prefer a device with more flexibility, even if it isn't as badass.
Click to expand...
Click to collapse
This is wrong. Safestrap is a bootstrap recovery. It IS a "bootloader bypass" of sorts. Once everything is squared away, safestrap WILL allow flashing of non-stock ROMs and the execution of Kexec kernels. We will have access to almost everything available with an unlocked bootloader, except it will require room on our internal storage for the ROM files.
Banggugyangu said:
This is wrong. Safestrap is a bootstrap recovery. It IS a "bootloader bypass" of sorts. Once everything is squared away, safestrap WILL allow flashing of non-stock ROMs and the execution of Kexec kernels. We will have access to almost everything available with an unlocked bootloader, except it will require room on our internal storage for the ROM files.
Click to expand...
Click to collapse
AFAIK, it will not allow kexec, as that is a different exploit. Also, it cannot modify aboot. So you will not be able to install AOSP ROMs or anything but a modified stock kernel. Believe me, I would love to be wrong.
xdadevnube said:
AFAIK, it will not allow kexec, as that is a different exploit. Also, it cannot modify aboot. So you will not be able to install AOSP ROMs or anything but a modified stock kernel. Believe me, I would love to be wrong.
Click to expand...
Click to collapse
Hashcode has implemented kexec into nearly every device's safestrap. Also, AOSP is still possible with the stock kernel. You simply have to incorporate certain parts of the stock ROM. I did all of this on the Droid Bionic. I had an AOSP ROM before safestrap was even created. It had a couple Blur elements that were very minor, but required.
Do we loose safestrap if we take OTA upgrade to Kitkat (when it's available)?
Banggugyangu said:
Hashcode has implemented kexec into nearly every device's safestrap. Also, AOSP is still possible with the stock kernel. You simply have to incorporate certain parts of the stock ROM. I did all of this on the Droid Bionic. I had an AOSP ROM before safestrap was even created. It had a couple Blur elements that were very minor, but required.
Click to expand...
Click to collapse
I was thinking of the S4 that doesn't have kexec and cannot flash AOSP. It is reasonable to assume that the N3 could get kexec even although the S4 doesn't have it.
SS is not bootloader bypass. Many benefits of an unlocked bootloader will not be realized with SS. However, it should be a decent option for at least getting some ROMs. With kexec, then most people will be happy.
xdadevnube said:
I was thinking of the S4 that doesn't have kexec and cannot flash AOSP. It is reasonable to assume that the N3 could get kexec even although the S4 doesn't have it.
SS is not bootloader bypass. Many benefits of an unlocked bootloader will not be realized with SS. However, it should be a decent option for at least getting some ROMs. With kexec, then most people will be happy.
Click to expand...
Click to collapse
There is a huge difference when Hashcode has the phone in question. It's my understanding that this is the first Samsung phone he has had.
So he's stated that he plans to add kexec? That would be [email protected]$$.
Sent from my SM-N900V using Tapatalk
I still have a MDL bootloader and have been running clean GE ROMs since they came out. I really want to try out AT&T's latest MK2 4.3 official ROM, but it seems no one has just released a clean flashable in CWM rom like I have seen in past releases.
Is it because most people have to use Safestrap now with the newer bootloaders and have no use for flashable MK2 ROMs anymore?
I don't want to upgrade my bootloader by just putting on MK2 the normal way, I want to keep the ability to flash ROMS, but really want to try out a stock MK2 so I can try out the Samsung stuff again.
Sure there are a ton of MK2 ROMs in the forums here, but they are heavily modded with stuff I really don't want. I just want a clean ROM without anyone's MODs except for the usual of removal of the protections that would prevent me from reflashing a different ROM in the future.
Can anyone please point me in the right direction?
chocodough said:
I still have a MDL bootloader and have been running clean GE ROMs since they came out. I really want to try out AT&T's latest MK2 4.3 official ROM, but it seems no one has just released a clean flashable in CWM rom like I have seen in past releases.
Is it because most people have to use Safestrap now with the newer bootloaders and have no use for flashable MK2 ROMs anymore?
I don't want to upgrade my bootloader by just putting on MK2 the normal way, I want to keep the ability to flash ROMS, but really want to try out a stock MK2 so I can try out the Samsung stuff again.
Sure there are a ton of MK2 ROMs in the forums here, but they are heavily modded with stuff I really don't want. I just want a clean ROM without anyone's MODs except for the usual of removal of the protections that would prevent me from reflashing a different ROM in the future.
Can anyone please point me in the right direction?
Click to expand...
Click to collapse
It's mostly because we already got a root method, so nobody's seen a purpose in putting together a flashable one to experiment on. I'm sure it can be done using the same method which the MF3 stock ROM was made, but someone just has to be willing to flash back to completely stock and run some terminal commands.
EDIT: Found a system dump, just nobody has compiled it into a flashable zip. http://forum.xda-developers.com/showpost.php?p=47943805&postcount=760
Maybe someone could look at it.
EDIT2: StockUp has a rebloat addon if you want AT&T apps, and comes with all the normal Samsung things. It's probably your best bet. http://forum.xda-developers.com/showthread.php?t=2498244
DeadlySin9 said:
It's mostly because we already got a root method, so nobody's seen a purpose in putting together a flashable one to experiment on. I'm sure it can be done using the same method which the MF3 stock ROM was made, but someone just has to be willing to flash back to completely stock and run some terminal commands.
EDIT: Found a system dump, just nobody has compiled it into a flashable zip. http://forum.xda-developers.com/showpost.php?p=47943805&postcount=760
Maybe someone could look at it.
EDIT2: StockUp has a rebloat addon if you want AT&T apps, and comes with all the normal Samsung things. It's probably your best bet. http://forum.xda-developers.com/showthread.php?t=2498244
Click to expand...
Click to collapse
Hopefully a DEV has their original laying around somewhere.
Of course I would prefer to have the KNOX stuff removed. I'm not sure what files to remove to do it myself.
I've seen some ROMs similar to what I am looking for in the Tmobile section here, but they still have stuff like modded or replaced kernels and of course all the Tmobile stuff in them. Would be nice to have the actual AT&T version without KNOX.
Hopefully that wouldn't be asking too much.
DeadlySin9 said:
It's mostly because we already got a root method, so nobody's seen a purpose in putting together a flashable one to experiment on. I'm sure it can be done using the same method which the MF3 stock ROM was made, but someone just has to be willing to flash back to completely stock and run some terminal commands.
EDIT: Found a system dump, just nobody has compiled it into a flashable zip. http://forum.xda-developers.com/showpost.php?p=47943805&postcount=760
Maybe someone could look at it.
EDIT2: StockUp has a rebloat addon if you want AT&T apps, and comes with all the normal Samsung things. It's probably your best bet. http://forum.xda-developers.com/showthread.php?t=2498244
Click to expand...
Click to collapse
Ok thanks, I'll look into that.
chocodough said:
Hopefully a DEV has their original laying around somewhere.
Of course I would prefer to have the KNOX stuff removed. I'm not sure what files to remove to do it myself.
I've seen some ROMs similar to what I am looking for in the Tmobile section here, but they still have stuff like modded or replaced kernels and of course all the Tmobile stuff in them. Would be nice to have the actual AT&T version without KNOX.
Hopefully that wouldn't be asking too much.
Click to expand...
Click to collapse
StockUp has KNOX removed and is based off the AT&T version, and like i said has that rebloat zip with AT&T apps. All you have to do from there is get a 4.3 kernel
This one? have you read it?
MF3 system and boot images, no bootloader so you are safe. Need custom kernels, due to mf3 rom expecting mf3 bootloader and kernel.
http://forum.xda-developers.com/showthread.php?t=2378946
Personal suggestion, don't try the MF3 and stay with GE, update it to 4.3 or 4.4 if you want, because you won't be losing anything going touchwiz and instead will be adding a ton of crap. Even after debloating you will still end up with a ton of crap.
ps. lovely edit system the forum has...
chocodough said:
I still have a MDL bootloader and have been running clean GE ROMs since they came out. I really want to try out AT&T's latest MK2 4.3 official ROM, but it seems no one has just released a clean flashable in CWM rom like I have seen in past releases.
Is it because most people have to use Safestrap now with the newer bootloaders and have no use for flashable MK2 ROMs anymore?
I don't want to upgrade my bootloader by just putting on MK2 the normal way, I want to keep the ability to flash ROMS, but really want to try out a stock MK2 so I can try out the Samsung stuff again.
Sure there are a ton of MK2 ROMs in the forums here, but they are heavily modded with stuff I really don't want. I just want a clean ROM without anyone's MODs except for the usual of removal of the protections that would prevent me from reflashing a different ROM in the future.
Can anyone please point me in the right direction?
Click to expand...
Click to collapse
Upgrade bootloader? It seems like a downgrade if it restricts what you can flash. Have you tried the international roms? Sure it won't have the at&t stuff which most people don't want but it'll have the samsung stuff you seem to want. Make sure to flash lokidoki after installing international rom or install an at&t kernal.
gb.sn said:
This one? have you read it?
MF3 system and boot images, no bootloader so you are safe. Need custom kernels, due to mf3 rom expecting mf3 bootloader and kernel.
http://forum.xda-developers.com/showthread.php?t=2378946
Personal suggestion, don't try the MF3 and stay with GE, update it to 4.3 or 4.4 if you want, because you won't be losing anything going touchwiz and instead will be adding a ton of crap. Even after debloating you will still end up with a ton of crap.
ps. lovely edit system the forum has...
Click to expand...
Click to collapse
He was looking for MK2, not MF3.
crash822 said:
Upgrade bootloader? It seems like a downgrade if it restricts what you can flash. Have you tried the international roms? Sure it won't have the at&t stuff which most people don't want but it'll have the samsung stuff you seem to want. Make sure to flash lokidoki after installing international rom or install an at&t kernal.
Click to expand...
Click to collapse
He said he doesn't want to upgrade bootloader, that's why he's looking for a loki 4.3 stock.
I am here to give a quick warning to all users. Please, do not revert to older versions of Android. This can cause your device to brick when you take an ota. The reason for the brick is because the ota process flashes secure elements and these elements can not be mixed. Once, you mix these you will brick. Also, if you have reverted the only safe way to update is thru a full xml.
If anyone would like to extend on this point please do. I am writing this up before class as I see people are bricking.
Sent from my XT1053 using Tapatalk
papi92 said:
I am here to give a quick warning to all users. Please, do not revert to older versions of Android. This can cause your device to brick when you take an ota. The reason for the brick is because the ota process flashes secure elements and these elements can not be mixed. Once, you mix these you will brick. Also, if you have reverted the only safe way to update is thru a full xml.
If anyone would like to extend on this point please do. I am writing this up before class as I see people are bricking.
Sent from my XT1053 using Tapatalk
Click to expand...
Click to collapse
1+^
Sent on my Gummy running Lenoto X
I'll only add that the first few bricks from this were just bad luck.....but after the posts about it.....the further bricks can be blamed on poor research, reading and self learning. These things are what XDA is supposed to be about. Blindly flashing this and that without doing homework first is a recipe for disaster with what we do here.
Sometimes people, like me, are brushed off as jerks or know it all's when we remind people of these things, or tell them to read and search instead of answering their questions.....but really we're just trying to help people help themselves and learn more about what they are doing.
Anyway.....personally ...I'll continue to be a "jerk" and remind people of this stuff occasionally, cause it just may get through to some people.
Also.....XDA rules state to search before posting....Wow has that been forgotten these days. LOL
Peace all!
Sent from my Moto X cellular telephone...
My sentiments too, at this rate I think the moto x will have the world record for hard bricks
Sent on my Gummy running Lenoto X
flashallthetime said:
My sentiments too, at this rate I think the moto x will have the world record for hard bricks
Sent on my Gummy running Lenoto X
Click to expand...
Click to collapse
No kidding! LOL. I despise Samsung....but it was very hard to brick. LOL. This bootloader version mixed with OTA stuff on the X is a mess.
Sent from my Moto X cellular telephone...
---------- Post added at 07:21 PM ---------- Previous post was at 07:19 PM ----------
Oh...throw in unlocked bootloader methods, vs locked bootloader methods and the x can get pretty confusing. Personally.....I think people should avoid the phones that can't be boot loader unlocked like the plague. LOL
Sent from my Moto X cellular telephone...
Avoid flashing firmware at the least, there's now a flashable 4.4.2 stock ROM too, so you have options to safely flash roms
Sent on my Gummy running Lenoto X
If you are going play then you must be read to play. As for people who want to use otas there's a trick. Remove all secure elements from the zip just keep the patches to system boot and modem. That way you do not brick. But please don't return your X when you do brick because of taking OTAs on a Frankenstein device with this bootloader and that gpt
Sent from my XT1053 using Tapatalk
i think it's always a good idea not to go back in android versions!
Reading this makes me feel sad. I come from a SGSII, on which I could flash anything, without braking it .
So let me get this straight: if I have the Sprint version (no dev version available) and want root without voiding the warranty I have to downgrade to 4.2.2 and use RockMyMoto, flash 4.4, and use SlapMyMoto. However, if I do that, any future OTA upgrades will cause a brick so while I can flash future ROMs I will be stuck on the current firmware?
ahecht said:
So let me get this straight: if I have the Sprint version (no dev version available) and want root without voiding the warranty I have to downgrade to 4.2.2 and use RockMyMoto, flash 4.4, and use SlapMyMoto. However, if I do that, any future OTA upgrades will cause a brick so while I can flash future ROMs I will be stuck on the current firmware?
Click to expand...
Click to collapse
No , the problem happens when you upgrade your boot loader to 4.4.2, you can not downgrade. As long as you stay with 4.4 BOOTLOADER you can downgrade to 4.2.2 post camera ota. If you flash the 4.4.2 BOOT LOADER and decide to Frankenstein your phone and flash an older boot loader , you're SOL, 4.4.2 BOOT LOADER is a one way ticket
Regardless if your boot loader is unlocked or locked. Just because I have a unlocked boot loader does not give me Amy extra ability to flash an older boot loader ,it gves me a better way of rooting and flashing roms
Sent on my Lenoto A2109 tablet
flashallthetime said:
No , the problem happens when you upgrade your boot loader to 4.4.2, you can not downgrade. As long as you stay with 4.4 BOOTLOADER you can downgrade to 4.2.2 post camera ota. If you flash the 4.4.2 BOOT LOADER and decide to Frankenstein your phone and flash an older boot loader , you're SOL, 4.4.2 BOOT LOADER is a one way ticket
Regardless if your boot loader is unlocked or locked. Just because I have a unlocked boot loader does not give me Amy extra ability to flash an older boot loader ,it gves me a better way of rooting and flashing roms
Sent on my Lenoto A2109 tablet
Click to expand...
Click to collapse
Thanks. My motomaker Moto X is on its way, hopefully it won't have the 4.4.2 boot loader from the factory.
Personally I think that anyone even remotely interested in hacking, flashing, or anything of that nature should have gotten a developer edition. Especially if you're not sure of what you're doing. No company has ever offered something that makes being a phone geek so easy and yet, not many have taken advantage.
I also feel that not enough people try to do things the "hard way". But I find fastboot way easier and safer than many of the tools provided. And once you learn it it's useful on many devices and similar to Odin etc. I just don't want Motorola getting a bad rap for other people's foolishness
MotoX GSM Developer Edition, Bootloader Unlocked, Rooted, Stock 4.4.2 Great Britain on T-Mobile !
SymbioticGenius said:
Personally I think that anyone even remotely interested in hacking, flashing, or anything of that nature should have gotten a developer edition. Especially if you're not sure of what you're doing. No company has ever offered something that makes being a phone geek so easy and yet, not many have taken advantage.
I also feel that not enough people try to do things the "hard way". But I find fastboot way easier and safer than many of the tools provided. And once you learn it it's useful on many devices and similar to Odin etc. I just don't want Motorola getting a bad rap for other people's foolishness
MotoX GSM Developer Edition, Bootloader Unlocked, Rooted, Stock 4.4.2 Great Britain on T-Mobile !
Click to expand...
Click to collapse
It makes no difference having a DE edition or a Rogers unlockable boot loader moto as I have , they are essentially the same beast, I can do everything you can do, a DE edition will brick as fast as any other moto variant. I think people who have no common sense is the problem, they assume that flashing firmware is like flashing custom ROMs and its not
Sent on my Lenoto A2109 tablet
papi92 said:
If you are going play then you must be read to play. As for people who want to use otas there's a trick. Remove all secure elements from the zip just keep the patches to system boot and modem. That way you do not brick. .........
Sent from my XT1053 using Tapatalk
Click to expand...
Click to collapse
Out of curiosity. Have you done this with your X? From what I gather it seems to be a "safe(r)" way of upgrading without compromising the bootloader, yet I haven't read where anyone has actually tried doing it. The threads where those on 4.2.2 flashing 4.4.x firmwares from other carriers is coming to mind. Why risk it if what you are saying works? I have a new VZ dev ed that I'm trying to figure out how to handle the 4.2.2 update on, if it ever comes.
edthesped said:
Out of curiosity. Have you done this with your X? From what I gather it seems to be a "safe(r)" way of upgrading without compromising the bootloader, yet I haven't read where anyone has actually tried doing it. The threads where those on 4.2.2 flashing 4.4.x firmwares from other carriers is coming to mind. Why risk it if what you are saying works? I have a new VZ dev ed that I'm trying to figure out how to handle the 4.2.2 update on, if it ever comes.
Click to expand...
Click to collapse
He's a developer, staying with only system images and modems your safer, modems do not always work in specific locations, UK modem will not work in Brazil, so keep your existing modem , the system files are all basically the same with minor changes, T-Mobile and rogers have no bloat, rogers has the carrier logo, where T-Mobile doesn't, at&t has at&t bloatware. As for Verizon,spring and us cell I have no idea as its CDMA and I have the gsm variant
Sent on my Lenoto A2109 tablet
flashallthetime said:
He's a developer, staying with only system images and modems your safer, modems do not always work in specific locations, UK modem will not work in Brazil, so keep your existing modem , the system files are all basically the same with minor changes, T-Mobile and rogers have no bloat, rogers has the carrier logo, where T-Mobile doesn't, at&t has at&t bloatware. As for Verizon,spring and us cell I have no idea as its CDMA and I have the gsm variant
Sent on my Lenoto A2109 tablet
Click to expand...
Click to collapse
It's starting to come together...
Knowing this I still don't quite get why so many people seemed to be flashing firmware from other carriers when they could have cherry picked what they "needed".
It would be nice to figure out how to use the system.img from other carriers as VZ's firmware appears to have about 100MiB of "added features" that I'd prefer not to have.
Being that the risk appears to be negligible I may attempt to push the system.img from another carrier to see what happens.
edthesped said:
It's starting to come together...
Knowing this I still don't quite get why so many people seemed to be flashing firmware from other carriers when they could have cherry picked what they "needed".
It would be nice to figure out how to use the system.img from other carriers as VZ's firmware appears to have about 100MiB of "added features" that I'd prefer not to have.
Being that the risk appears to be negligible I may attempt to push the system.img from another carrier to see what happens.
Click to expand...
Click to collapse
You can flash other carrier images, sprint and us cell are 2 CDMA carriers without any issues, system IMG ,boot IMG and non_hlos.bin are the files you need (not motoboot.IMG that's the bootloader)
Sent on my Lenoto A2109 tablet
So many of the brick stories I'm reading about could have been avoided had people trying to expedite the upgrade to 4.4.2 just flashed everything but the bootloader?
At some point I need to figure out how to get one of the bloatless system files VZ X as I'm not sure where the 100MB of stuff comes from.
Next steps, tell self "yes this phone is worth keeping" and unlock the bootloader.
Again, thanks for your patience
edthesped said:
So many of the brick stories I'm reading about could have been avoided had people trying to expedite the upgrade to 4.4.2 just flashed everything but the bootloader?
At some point I need to figure out how to get one of the bloatless system files VZ X as I'm not sure where the 100MB of stuff comes from.
Next steps, tell self "yes this phone is worth keeping" and unlock the bootloader.
Again, thanks for your patience
Click to expand...
Click to collapse
Yes but people always jump in head first, the only issue is if they happen to flash the old system.img 4.4 and have the 4.4.2 boot loader, chances are they will end up hard bricked, why? Going back to 4.4 will ping moto servers for the ota, it gets downloaded and installed, bam hard bricked,
If you flash just system.img , do not take any ota at all
Sent on my Lenoto A2109 tablet
Hello people I was just wondering if anybody was using the Link2sd app on their phone, And if they had any problems running it with safestrap and while running on rom slot? I have a samsung galaxy s5 and its rooted. Im running out of memory on my phone and would like to be able to download more applications
There seems to be some critical and unspecified assumptions being made here that you haven't told us about. Why are you using Safestrap? Is it because your have a locked bootloader e.g. limited by having a Verizon /ATT phone? Or for some other reason? For that matter, what S5 model and precise firmware and Safestrap versions are you using?
We can't see your phone or divine the missing information. You should provide a lot more detail if you are looking for accurate answers.
.
link2sd and Safestrap
fffft said:
There seems to be some critical and unspecified assumptions being made here that you haven't told us about. Why are you using Safestrap? Is it because your have a locked bootloader e.g. limited by having a Verizon /ATT phone? Or for some other reason? For that matter, what S5 model and precise firmware and Safestrap versions are you using?
We can't see your phone or divine the missing information. You should provide a lot more detail if you are looking for accurate answers.
.
Click to expand...
Click to collapse
Sorry about not giving enough information, Im using the latest version of Safestrap. And the reason im using it is because Im running Alliance rom
and the guy on the youtube video told me to install safestrap before installing a new rom so incase something goes wrong I could just reboot using my stock rom. I dont exactly know what safestrap is lol. Anyway i have a Samsung galaxy s5 Verizon model SM-G900V And I have no idea where to find the Firmware versions im using. I would just like to know can I use link2sd on my phone with out causing any problems.
You don't need Safestrap to run the Alliance ROM. Ostensibly you have it because you are using a Verizon phone. Verizon unlike most carriers locks the bootloader which restricts what you can do with your phone. That is a problem that other carriers e.g. TMobile don't have to deal with. Safestrap is an emulator that makes a virtual copy of your ROM, recovery, etc to allow actions that the Verizon locked bootloader wouldn't otherwise allow.
The upshot of which is that using Safestrap enormously complicates how things work and affects compatibility at a low level. The information that you didn't provide about file versions ans so forth is crucial to sorting all that out and I won't venture a guess without that info. I'd suggest that you post your question in the Verizon S5 forum, rather than this one as you'll find a lot more people with the same configuration as you who may be in a good position to answer your question.
.