I have a Samsung Galaxy S5 Active SGH-I537 on carrier AT&T and have tried to unlock unsuccessfully. I have a couple of months left on the warranty but want to use it on my carrier. I was thinking of rooting it and unlocking with regionlock away, but want to be sure if something goes wrong I can go back to the stock ROM. This assuming of course it doesn't get completely bricked and can send it to Samsung for whatever repair.
Can this be done without Samsung detecting it was rooted? If so what would be my best course of action?
I am on 4.3 with MF1 baseband.
Papote13 said:
I have a Samsung Galaxy S5 Active SGH-I537 on carrier AT&T and have tried to unlock unsuccessfully. I have a couple of months left on the warranty but want to use it on my carrier. I was thinking of rooting it and unlocking with regionlock away, but want to be sure if something goes wrong I can go back to the stock ROM. This assuming of course it doesn't get completely bricked and can send it to Samsung for whatever repair.
Can this be done without Samsung detecting it was rooted? If so what would be my best course of action?
I am on 4.3 with MF1 baseband.
Click to expand...
Click to collapse
Grab the stock FW from here and flash with ODIN.
I just now rooted the phone using the method from this page using SafeRoot and Disable Knox. I did have to flash the pwnedkernel Modem in CP using ODIN 3.09 from here. Now that I was rooted, I installed and ran RegionUnlock Away from here.
I finally flashed the modem using to originalkernel.tar.md5 in CP using ODIN and flashed.
I now have my SGH-I537 phone rooted and unlocked.
Using the method I mentioned above, if I ever want to UNROOT and leave no trace, what is the correct way to do so?
Would Flashing the stock firmware be enough?
Thanks.
Hi i just read about the i9295 and the i537 and they are the same device accept the different in the frameware version (the i9295 - 4.2.2, i537 - 4.4.2).
so i have the question can i install the i537 4.4.2 stock rom on the i9295?
and if not i'll be happy if you can explain why (just so i can understand).
thanx ahead! :laugh:
solokiller11 said:
Hi i just read about the i9295 and the i537 and they are the same device accept the different in the frameware version (the i9295 - 4.2.2, i537 - 4.4.2).
so i have the question can i install the i537 4.4.2 stock rom on the i9295?
and if not i'll be happy if you can explain why (just so i can understand).
thanx ahead! :laugh:
Click to expand...
Click to collapse
While the i9295 and the i537 have the same hardware, they have different software. More specifically, the i9295 has an unlocked bootloader while the i537 has a locked bootloader. What this means is that the i9295 is able to flash/install a custom recovery, custom kernel, and custom ROM while on the i537, in order to flash anything it must be signed by Samsung. Only official firmware is signed by Samsung, so there is no way to flash a custom recovery or custom kernel. There is a way to flash custom ROMs, but that's not important here.
To answer you question, theoretically you could flash the i537 firmware on your i9295, but you will most likely end up with a bricked phone because bootloaders are only compatible with their intended models. So the i537 bootloader will only work with the i537 and will brick the i9295.
If you still really want the i537 4.4.2 firmware on your phone, I'd be more than happy to trade my i537 for your i9295. This is a great phone and works great in every respect, I only wish it had an unlocked bootloader like the i9295. If I could do it all over again I would have bought the i9295 instead.
EDIT: I think @mythi is working on a stock 4.4 ROM for the i9295, you might want to ask him about it.
Devo7v said:
While the i9295 and the i537 have the same hardware, they have different software. More specifically, the i9295 has an unlocked bootloader while the i537 has a locked bootloader. What this means is that the i9295 is able to flash/install a custom recovery, custom kernel, and custom ROM while on the i537, in order to flash anything it must be signed by Samsung. Only official firmware is signed by Samsung, so there is no way to flash a custom recovery or custom kernel. There is a way to flash custom ROMs, but that's not important here.
To answer you question, theoretically you should be able to flash the i537 firmware on your i9295, but you will end up with a locked bootloader and no way to revert it. Your phone would still work and you'd still be able to use it, but it would be locked down so that you'd only be able to use AT&T firmware. If you really want 4.4 on your phone, I suggest you flash one of the custom ROMs in the development section.
If you still really want the 4.4.2 firmware on your phone, I'd be more than happy to trade my i537 for your i9295. This is a great phone and works great in every respect, I only wish it had an unlocked bootloader like the i9295. If I could do it all over again I would have bought the i9295 instead.
EDIT: I think @mythi is working on a stock 4.4 ROM for the i9295, you might want to ask him about it.
Click to expand...
Click to collapse
Hi thank you very much for your answer it helped me a lot.
and about the locked bootloader, are you sure that it can't be revert?
and one more thing i bought this phone like two weeks ago so what is the best custom rom for now? (i saw only the carbon rom 4.4.2)
and one more question, if the i537 4.4.2 is signed by samsung but with locked bootloader and the i9295 4.2.2 is also signed by samsung and with unlocked bootloader so cant i just flash back the i9295 framewere over the i537 framewere?
solokiller11 said:
Hi thank you very much for your answer it helped me a lot.
and about the locked bootloader, are you sure that it can't be revert?
and one more thing i bought this phone like two weeks ago so what is the best custom rom for now? (i saw only the carbon rom 4.4.2)
Click to expand...
Click to collapse
Once you have a locked bootloader, the only way to get another bootloader on the phone is to flash one that has been signed by Samsung. Samsung uses a different signature on unlocked bootloaders, so there is no way to revert.
I don't think you really looked? I just opened the Development forum and found the following on the first page:
[S4-I9295● KK 4.4.2][05.05 M1][SOKP》》SONIC OPEN KANG PROJECT][AIO][Weekly Builds]
[Rom] Updated [Unofficial] Carbon Rom 4.4.2 based on CM11.0 [24.04.14]
[Rom] [Unofficial] BeanStalk 4.4.2 based on CM11.0 [24.04.14]
[ROM][4.4.2]Unofficial Dirty AOSB Build]
[ROM] 4.4.2 | MoKee Opensource | CM & AOSP | HALO][Dirty-Build]
[ROM][4.4.2][Unofficial Dirty SlimBean Build][New Build Available][Slim Weekly 3.0]
In the Original Development forum there is [ROM][Unofficial/Experimental][Android 4.4] CyanogenMod 11.0 for SGS4A (int'l). It's under constant development and I hear good things about it, but again, I have an i537 so I can't try any of these.
Devo7v said:
Once you have a locked bootloader, the only way to get another bootloader on the phone is to flash one that has been signed by Samsung. Samsung does not sign unlocked bootloaders, so there is no way to revert.
I don't think you really looked? I just opened the Development forum and found the following on the first page:
[S4-I9295● KK 4.4.2][05.05 M1][SOKP》》SONIC OPEN KANG PROJECT][AIO][Weekly Builds]
[Rom] Updated [Unofficial] Carbon Rom 4.4.2 based on CM11.0 [24.04.14]
[Rom] [Unofficial] BeanStalk 4.4.2 based on CM11.0 [24.04.14]
[ROM][4.4.2]Unofficial Dirty AOSB Build]
[ROM] 4.4.2 | MoKee Opensource | CM & AOSP | HALO][Dirty-Build]
[ROM][4.4.2][Unofficial Dirty SlimBean Build][New Build Available][Slim Weekly 3.0]
In the Original Development forum there is [ROM][Unofficial/Experimental][Android 4.4] CyanogenMod 11.0 for SGS4A (int'l). It's under constant development and I hear good things about it, but again, I have an i537 so I can't try any of these.
Click to expand...
Click to collapse
If Samsung doesnt sign unlocked bootloaders so how the i9295 have one?
and thank you for the custom roms
solokiller11 said:
If Samsung doesnt sign unlocked bootloaders so how the i9295 have one?
and thenk you for the custom roms
Click to expand...
Click to collapse
The just flash it to the phone. To simplify the way the bootloader works, it is the first thing that loads when you power on the phone, it then tells the phone what other pieces of software to load (aboot, sbl, kernel, etc.).
With an unlocked bootloader, it does just that, it loads the next piece of software during the booting of the phone. With a locked bootloader, the bootloader checks the signature of the next piece of software to load, if the signature matches the signature that the bootloader expects then the next piece of software loads. If the signature doesn't match, then booting stops.
When you flash something to the phone using Odin (currently the way you flash bootloaders), with an unlocked bootloader Odin will flash it, for better or worse. But with a locked bootloader, the bootloader checks the signature of the file you are trying to flash and if they match then it can be flashed, if it doesn't match then the flash aborts without any changes being made.
So, how can Samsung put an unlocked bootloader on the phone without it being signed? When you start with empty hardware you can essentially put any software you want on the phone, there is nothing there preventing it, but once you put a locked bootloader on the phone if will then check every single piece of software you try to flash to the phone.
TL;DR Think of the hardware as an empty room. You can put anything you want in the room to start with, but if the first thing you put in the room is a door with a lock, then the only things you can put in the room from then on are things that have a key to that lock.
Devo7v said:
The just flash it to the phone. To simplify the way the bootloader works, it is the first thing that loads when you power on the phone, it then tells the phone what other pieces of software to load (aboot, sbl, kernel, etc.).
With an unlocked bootloader, it does just that, it loads the next piece of software during the booting of the phone. With a locked bootloader, the bootloader checks the signature of the next piece of software to load, if the signature matches the signature that the bootloader expects then the next piece of software loads. If the signature doesn't match, then booting stops.
When you flash something to the phone using Odin (currently the way you flash bootloaders), with an unlocked bootloader Odin will flash it. But with a locked bootloader, the bootloader checks the signature of the file you are trying to flash and if they match then it can be flashed, if it doesn't match then the flash aborts without any changes being made.
So, how can Samsung put an unlocked bootloader on the phone without it being signed? When you start with empty hardware you can essentially put any software you want on the phone, there is nothing there preventing it, but once you put a locked bootloader on the phone if will then check every single piece of software you try to flash to the phone.
TL;DR Think of the hardware as an empty room. You can put anything you want in the room to start with, but if the first thing you put in the room is a door with a lock, then the only things you can put in the room from then on are things that have a key to that lock.
Click to expand...
Click to collapse
Hi man Thank you very very much for the explanation about the bootloaders and i think i gonna install the carbon rom
Devo7v said:
While the i9295 and the i537 have the same hardware, they have different software. More specifically, the i9295 has an unlocked bootloader while the i537 has a locked bootloader. What this means is that the i9295 is able to flash/install a custom recovery, custom kernel, and custom ROM while on the i537, in order to flash anything it must be signed by Samsung. Only official firmware is signed by Samsung, so there is no way to flash a custom recovery or custom kernel. There is a way to flash custom ROMs, but that's not important here.
To answer you question, theoretically you should be able to flash the i537 firmware on your i9295, but you will end up with a locked bootloader and no way to revert it. Your phone would still work and you'd still be able to use it, but it would be locked down so that you'd only be able to use AT&T firmware. If you really want 4.4 on your phone, I suggest you flash one of the custom ROMs in the development section.
If you still really want the 4.4.2 firmware on your phone, I'd be more than happy to trade my i537 for your i9295. This is a great phone and works great in every respect, I only wish it had an unlocked bootloader like the i9295. If I could do it all over again I would have bought the i9295 instead.
EDIT: I think @mythi is working on a stock 4.4 ROM for the i9295, you might want to ask him about it.
Click to expand...
Click to collapse
NONONONONONONO ... never ever i say never ever repeat what u said in here ... flashing a other devices bootloader will destroy your phone and you will need something called jig to fix it ... this happens because every device that sammy realeses has a private key for certain partitions on the mmc like the bootloader the rbm etc ... flashing other devices partitions even if the share the same hardware (yes) even if they are from the same family will kill your phone and you will end with a paper that need 200$ service . i request you to edit your comment since alot of the people here are noobs or have little knowelge .
mythi said:
NONONONONONONO ... never ever i say never ever repeat what u said in here ... flashing a other devices bootloader will destroy your phone and you will need something called jig to fix it ... this happens because every device that sammy realeses has a private key for certain partitions on the mmc like the bootloader the rbm etc ... flashing other devices partitions even if the share the same hardware (yes) even if they are from the same family will kill your phone and you will end with a paper that need 200$ service . i request you to edit your comment since alot of the people here are noobs or have little knowelge .
Click to expand...
Click to collapse
I'm going to edit my post, but I'm also going to disagree with you. Back when I had a Samsung Captivate you were able to flash Galaxy S i9000 ROMs with some minor tweaks. Inadvertently I accidentally flashed an i9000 one-click to my i897. The flash finished and my was messed up, but not so bad that it made the phone unusable (i.e. buttons were mapped incorrectly and the display was inverted). I discovered I had installed an i9000 bootloader on my phone because the partitions were different and I couldn't boot the phone after flashing i897 stock firmware. The only way I could get stock firmware back on my phone was to flash i897 bootloaders which lead me to believe that my phone had the i9000 bootloader on it. Maybe I'm wrong and maybe Samsung has changed the way things work in the past 4 years, but I do not believe this was always the case.
That said, I will make sure that everybody understands that they could brick their phone if they flash a different bootloader.
Devo7v said:
I'm going to edit my post, but I'm also going to disagree with you. Back when I had a Samsung Captivate you were able to flash Galaxy S i9000 ROMs with some minor tweaks. Inadvertently I accidentally flashed an i9000 one-click to my i897. The flash finished and my was messed up, but not so bad that it made the phone unusable (i.e. buttons were mapped incorrectly and the display was inverted). I discovered I had installed an i9000 bootloader on my phone because the partitions were different and I couldn't boot the phone after flashing i897 stock firmware. The only way I could get stock firmware back on my phone was to flash i897 bootloaders which lead me to believe that my phone had the i9000 bootloader on it. Maybe I'm wrong and maybe Samsung has changed the way things work in the past 4 years, but I do not believe this was always the case.
That said, I will make sure that everybody understands that they could brick their phone if they flash a different bootloader.
Click to expand...
Click to collapse
Well the captivate is another story the developers got a leak of a signed rbm of the chipset of (i suspect) the humming bird chipset ... when you have something like that minor modifications can be done ... the same happened a while ago with some 8xx and i not sure of the 6xx -which runs in our phones- the leaked rbm would help devs to make other variants easily compatible in the low level side .
bootloaders :good:are also different story ... each and every device these days has a private key as i said earlier this key gets checked before booting by something in chipset (hardware side) and if key mismatch the device will enter a qcom mode for debugging etcetcetcetc........
trust me you don't want to brick a 600$ for simply to flash a bootloader :good:
mythi said:
Well the captivate is another story the developers got a leak of a signed rbm of the chipset of (i suspect) the humming bird chipset ... when you have something like that minor modifications can be done ... the same happened a while ago with some 8xx and i not sure of the 6xx -which runs in our phones- the leaked rbm would help devs to make other variants easily compatible in the low level side .
bootloaders :good:are also different story ... each and every device these days has a private key as i said earlier this key gets checked before booting by something in chipset (hardware side) and if key mismatch the device will enter a qcom mode for debugging etcetcetcetc........
trust me you don't want to brick a 600$ for simply to flash a bootloader :good:
Click to expand...
Click to collapse
Thanks for the info. So here a related question, what would happen if you took an i9295 with 4.2.2 on it and flashed the i537 4.2.2 firmware minus the bootloader? Would it fail to boot due to partitioning or would it work?
mythi said:
NONONONONONONO ... never ever i say never ever repeat what u said in here ... flashing a other devices bootloader will destroy your phone and you will need something called jig to fix it ... this happens because every device that sammy realeses has a private key for certain partitions on the mmc like the bootloader the rbm etc ... flashing other devices partitions even if the share the same hardware (yes) even if they are from the same family will kill your phone and you will end with a paper that need 200$ service . i request you to edit your comment since alot of the people here are noobs or have little knowelge .
Click to expand...
Click to collapse
hi man i dont think you right because my last phone was xtreamer joyz which is the exact same phone as the newman n2 and i could install both official framewere with no problem and those two phones have the exact same specs and also the i537 and the i9295 so i think it should work just fine.
but my knowelge isnt good as yours so correct me if im wrong here but i think it should work
EDIT: I still asking my question but also joining to Devo7v question about what will happen.
Devo7v said:
Thanks for the info. So here a related question, what would happen if you took an i9295 with 4.2.2 on it and flashed the i537 4.2.2 firmware minus the bootloader? Would it fail to boot due to partitioning or would it work?
Click to expand...
Click to collapse
If we get a way of unlocking the bootloader we can do this ... I will explain further ...
A stock Sammy ROM comes in the form of a tar.md5 package the .md5 part holds the signature of Sammy , this signature is a type of code that makes the bootloader understand that this package is a signed one with a Sammy key ... When we take the bootloader out of The package (sbl1.bin , sbl2.bin and sbl3.bin) we have to take other parts such as the rbm after taking these we have to repackage the remaining parts in a new tar package ... After doing this we can sign it with an md5 key but this key will give missmatch errors during flash so we have to get the keys of Sammy ... Even if we find those we will have find away to unlock the bootloader to unlock more things
mythi said:
If we get a way of unlocking the bootloader we can do this ... I will explain further ...
A stock Sammy ROM comes in the form of a tar.md5 package the .md5 part holds the signature of Sammy , this signature is a type of code that makes the bootloader understand that this package is a signed one with a Sammy key ... When we take the bootloader out of The package (sbl1.bin , sbl2.bin and sbl3.bin) we have to take other parts such as the rbm after taking these we have to repackage the remaining parts in a new tar package ... After doing this we can sign it with an md5 key but this key will give missmatch errors during flash so we have to get the keys of Sammy ... Even if we find those we will have find away to unlock the bootloader to unlock more things
Click to expand...
Click to collapse
I have to say that i didn't really understand why i cant install the official samsung i537 over the official samsung i9295 because the both signed by Samsung.
like if i have flashed the i9295 4.2.2 official stock on my i9295 so i can flash the i537 4.4.2 official stock no? they both have the Samsung key no?
solokiller11 said:
I have to say that i didn't really understand why i cant install the official samsung i537 over the official samsung i9295 because the both signed by Samsung.
like if i have flashed the i9295 4.2.2 official stock on my i9295 so i can flash the i537 4.4.2 official stock no? they both have the Samsung key no?
Click to expand...
Click to collapse
So u have a gt-i9295 i thought you have i537 :crying::crying: any way that can be possible as i did it already just wait and you will get it ... i have ensured it won't brick any phone but wifi and camera are not working
mythi said:
So u have a gt-i9295 i thought you have i537 :crying::crying: any way that can be possible as i did it already just wait and you will get it ... i have ensured it won't brick any phone but wifi and camera are not working
Click to expand...
Click to collapse
Hi thank you very much for your answer :laugh:.
And if I will choose to install the i537 4.4.2 on my i9295 do you know if i can fix the camera and the wifi?
solokiller11 said:
Hi thank you very much for your answer :laugh:.
And if I will choose to install the i537 4.4.2 on my i9295 do you know if i can fix the camera and the wifi?
Click to expand...
Click to collapse
I don't have any idea what must be done ... But I need to investigate more on this .
I originally had KitKat 4.4.2 rooted using towelroot, but I got tired of the ugly TouchWiz UI and wanted to try Lollipop. I successfully used the FlashFire method and flashed a pre-rooted Lollipop OF3 Stock ROM (DeOdexed) and I am using the OA1 Bootloader (I believe it's KitKat) which I flashed with Odin.
I would like to use Safestrap to flash the .zip required to use Xposed on Lollipop. I read that to get safestrap somewhat functioning, you have to flash a stock kernal to get it to boot into safestrap, flash your .zip, then flash another kernal to ensure that the phone actually boots after using safestrap.
I can't find a straightforward answer as to what kernals I should be using to do this for my specific phone and if it is even possible. I will list my phone's details below.
Thank you!
-AT&T Samsung Galaxy S5 G900A
-Lollipop 5.0 (Pre-rooted OF3 Stock ROM)
-G900A OA1 Bootloader (KitKat bootloader?)
Heyossb said:
I originally had KitKat 4.4.2 rooted using towelroot, but I got tired of the ugly TouchWiz UI and wanted to try Lollipop. I successfully used the FlashFire method and flashed a pre-rooted Lollipop OF3 Stock ROM (DeOdexed) and I am using the OA1 Bootloader (I believe it's KitKat) which I flashed with Odin.
I would like to use Safestrap to flash the .zip required to use Xposed on Lollipop. I read that to get safestrap somewhat functioning, you have to flash a stock kernal to get it to boot into safestrap, flash your .zip, then flash another kernal to ensure that the phone actually boots after using safestrap.
I can't find a straightforward answer as to what kernals I should be using to do this for my specific phone and if it is even possible. I will list my phone's details below.
Thank you!
-AT&T Samsung Galaxy S5 G900A
-Lollipop 5.0 (Pre-rooted OF3 Stock ROM)
-G900A OA1 Bootloader (KitKat bootloader?)
Click to expand...
Click to collapse
You can just use flashfire to install the xposed zip. Just make sure you're flashing the one for Samsung phones by arter97.
This is the one i use:
Xposed modules on G900A_OF2 - 5.0
is DeOdexed required for this - is it possible with non-DeOdexed?
Thank you
Hello!
I've done some reading and having not gotten a satisfactory answer I thought I'd throw my question out to the community.
I'm currently running Twisted Lollipop v7.
I can Odin back to stock 4.4.2 whenever and redo towelroot and install safestrap etc.
I've been unsuccessful at flashing an AOSP rom and wanted to confirm once and for all if it is truly impossible to flash Blisspop or Cyanogenmod or Sonic or any of those I enjoyed on my trusty old S3 onto my unlocked At&T S5 Active.
If it is not possible I will get rid of this unlocked AT&T S5 active and get a used what? The T-mobile variant? The international variant? I just want to be able to flash whatever the hell I want without too much hassle! I do like the phone other than that though!
Looking forward to any advice!
Thanks!
Edbogue
edbogue said:
Hello!
I've done some reading and having not gotten a satisfactory answer I thought I'd throw my question out to the community.
I'm currently running Twisted Lollipop v7.
I can Odin back to stock 4.4.2 whenever and redo towelroot and install safestrap etc.
I've been unsuccessful at flashing an AOSP rom and wanted to confirm once and for all if it is truly impossible to flash Blisspop or Cyanogenmod or Sonic or any of those I enjoyed on my trusty old S3 onto my unlocked At&T S5 Active.
If it is not possible I will get rid of this unlocked AT&T S5 active and get a used what? The T-mobile variant? The international variant? I just want to be able to flash whatever the hell I want without too much hassle! I do like the phone other than that though!
Looking forward to any advice!
Thanks!
Edbogue
Click to expand...
Click to collapse
No you can not flash any AOSP roms on a device that runs safestrap, the bootloader isnt unlocked so you cant install a custom recovery the closest thing to a recovery is safestrap, and with a locked bootloader you can not install kernels which is why you cant install AOSP based roms.
mcmellens said:
No you can not flash any AOSP roms on a device that runs safestrap, the bootloader isnt unlocked so you cant install a custom recovery the closest thing to a recovery is safestrap, and with a locked bootloader you can not install kernels which is why you cant install AOSP based roms.
Click to expand...
Click to collapse
Thank you for your response!
Blues! It's what I suspected. I intend to offload this phone as a result and get another. Which variant would you recommend I get so I can flash happily and not worry about a locked bootloader? The SM-G900F, or what else would you recommend?
Thanks for your help!
Edbogue
edbogue said:
Thank you for your response!
Blues! It's what I suspected. I intend to offload this phone as a result and get another. Which variant would you recommend I get so I can flash happily and not worry about a locked bootloader? The SM-G900F, or what else would you recommend?
Thanks for your help!
Edbogue
Click to expand...
Click to collapse
Any phone that has a carrier would be locked for the most part, i know sprint and maybe t-mobile usually don't lock there bootloaders, but that doesn't mean anything they could still be locked down. Your best bet if your looking to get a new phone for whatever reason stick with the ones straight from samsung the international versions. they usually don't have locked bootloaders.
Hello, anyone can you help me ?
i have a problem with my phone,
i have s4 active sgh-i537 ROM lollipop (I537UCUCOC6) and Rooted (succes with kingroot).
and now, how to install TWRP/CWM ?
i try to flash all version TWRP and CWM for s4 active via ODIN but always failed. i try flash .img file via app TWRP Official, Rashr, Flashify and failed again
can s4 active sgh-i537 install TWRP or CWM ? need to UBL ?
if not, how to fix my problem ?
Thankyou for help, and sorry for bad english.
The i537 had a locked bootloader, it is not possible to flash custom recovery. You can only flash 2 ROMs in the development section through FlashFire. If you want an unlocked bootloader you need to buy the i9295.
Devo7v said:
The i537 had a locked bootloader, it is not possible to flash custom recovery. You can only flash 2 ROMs in the development section through FlashFire. If you want an unlocked bootloader you need to buy the i9295.
Click to expand...
Click to collapse
If he's still on 4.4.2 he can use SafeStrap
GarnetSunset said:
If he's still on 4.4.2 he can use SafeStrap
Click to expand...
Click to collapse
True, but I doubt this is would help him accomplish his goal in the end. Yes it is recovery, but if he is trying to install one of the ROMs meant for the i9295 he's going to be out of luck.
Devo7v said:
True, but I doubt this is would help him accomplish his goal in the end. Yes it is recovery, but if he is trying to install one of the ROMs meant for the i9295 he's going to be out of luck.
Click to expand...
Click to collapse
Very true. But I prefer safestrap over flashfire, because its safer in the long run.
Devo7v said:
The i537 had a locked bootloader, it is not possible to flash custom recovery. You can only flash 2 ROMs in the development section through FlashFire. If you want an unlocked bootloader you need to buy the i9295.
Click to expand...
Click to collapse
Which two ROMS? Sick as hell?
Thank you!