Related
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 read that the Cricket Galaxy S5 (G900AZ) is a rebranded AT&T S5 (G900A). Has anyone tried ODIN flashing the stock AT&T rom on the Cricket model?
For instance, i have read people flashing the Tmobile S5 stock rom on the MetroPCS version and it works fine even though the model numbers are slightly different. It changes the phone into the Tmobile version.
spydc said:
I read that the Cricket Galaxy S5 (G900AZ) is a rebranded AT&T S5 (G900A). Has anyone tried ODIN flashing the stock AT&T rom on the Cricket model?
For instance, i have read people flashing the Tmobile S5 stock rom on the MetroPCS version and it works fine even though the model numbers are slightly different. It changes the phone into the Tmobile version.
Click to expand...
Click to collapse
Did you ever get an answer to this?
NO, but....
The Cricket S5 is indeed a rebranded AT&T model. I have both of those models including a LA G900M (TTT.) Major difference is nowhere near as much bloatware, and most importantly an unlocked bootloader. The only advantage would be upgrading to MM if you want stock, since the January update still has it on LP. You're better off trying a LA stock ROM though (I say this because they use the same custom recovery) But cutom ROM's can take you there as far as 7.1 Nougat right now.
I just recently rooted my Cricket model with CF Auto-root (klteaio), flashed the latest TWRP (klte) recovery and installed Xposed Framework (by dkcldark... wanam custom won't work.) Had a little of lag first couple of days, but I guess that's to be expected. Hope this helps in some way.
gello924 said:
The Cricket S5 is indeed a rebranded AT&T model. I have both of those models including a LA G900M (TTT.) Major difference is nowhere near as much bloatware, and most importantly an unlocked bootloader. The only advantage would be upgrading to MM if you want stock, since the January update still has it on LP. You're better off trying a LA stock ROM though (I say this because they use the same custom recovery) But cutom ROM's can take you there as far as 7.1 Nougat right now.
I just recently rooted my Cricket model with CF Auto-root (klteaio), flashed the latest TWRP (klte) recovery and installed Xposed Framework (by dkcldark... wanam custom won't work.) Had a little of lag first couple of days, but I guess that's to be expected. Hope this helps in some way.
Click to expand...
Click to collapse
Wait, it has an unlocked bootloader on the rebranded G900A?
Vesnyx said:
Wait, it has an unlocked bootloader on the rebranded G900A?
Click to expand...
Click to collapse
This gives me an idea.... What if we use flashfire to flash G900AZ firmware on the G900A (including the UNLOCKED BOOTLOADER)
Sent from my Amazon KFGIWI using XDA Labs
AptLogic said:
This gives me an idea.... What if we use flashfire to flash G900AZ firmware on the G900A (including the UNLOCKED BOOTLOADER)
Click to expand...
Click to collapse
You could always try it. I don't know exactly how well it will work.
You would have to be rooted FIRST on the G900A in order for FlashFire to work. If i remember correctly anything already on LP can't be rooted or downgraded back to KK.
---------- Post added at 11:30 PM ---------- Previous post was at 11:12 PM ----------
Y'know what would be really nice???: Seeing that android updates are only good for 2yrs on a particular model after its initial released, and the given the fact that most carries plans are only 2yrs; wouldn't it be nice if (for sake of argument in THIS thread) AT&T would release a firmware for their phones, that would unlock the bootloader and possibly SIM unlock the phone as well. I mean after 2yrs the device is paid for and quite frankly no longer belongs to them. I hate the idea of being forced to either get a new device once my plan has expired or use MY phone with the carrier its branded under. Of course it probably has everything to with them making their money from those of us who can't do without having a new device every year.
So I can pull a copy of the G900AZ engineering firmware I found, but I doubt we'll be able to flash it. What is was thinking is that we use beaups CID changer to make our device into one similar to the cricket wireless one. Since it is essentially a dev edition of our phone.
You cant just flash a unlocked bootloader to a locked bootloader phone. A specific explout must be developed to defeat the bootloader. Simply shashing over it will never work.
The G900AZ is just a rebranded version of the G900A though. I don't think there are any glaring differences like there would be from G900T to G900A. If the aboot does flash then it would be a simple unlock.
@NavSad @AptLogic
If you wanna try this, here's a link to their firmwares:
https://www.sammobile.com/firmwares/database/SM-G900AZ/
You'd most likely need to extract the correct files and be on the correct versions before flashing these.
Apparently, something similar happened with the T-Mobile Galaxy S6, where the MetroPCS firmware was flashed on the T-mobile firmware.
Vesnyx said:
The G900AZ is just a rebranded version of the G900A though. I don't think there are any glaring differences like there would be from G900T to G900A. If the aboot does flash then it would be a simple unlock.
@NavSad @AptLogic
If you wanna try this, here's a link to their firmwares:
https://www.sammobile.com/firmwares/database/SM-G900AZ/
You'd most likely need to extract the correct files and be on the correct versions before flashing these.
Apparently, something similar happened with the T-Mobile Galaxy S6, where the MetroPCS firmware was flashed on the T-mobile firmware.
Click to expand...
Click to collapse
I tried ODINing the G900AZTUU3BOG3 firmware, and it immediately returned a SECURE CHECK FAIL: aboot
I'll try using FlashFireon it tomorrow during my batch of tests.
AptLogic said:
I tried ODINing the G900AZTUU3BOG3 firmware, and it immediately returned a SECURE CHECK FAIL: aboot
I'll try using FlashFireon it tomorrow during my batch of tests.
Click to expand...
Click to collapse
Just so I can get an idea of what everyone's fuse values are, do you mind telling me what you see after RP SWREV in Download Mode.
NavSad said:
Just so I can get an idea of what everyone's fuse values are, do you mind telling me what you see after RP SWREV in Download Mode.
Click to expand...
Click to collapse
Mine are S1, T1, R1, A2, P1. I'm on Lollipop 5.0 with with ability to downgrade to NCE.
Also @AptLogic, maybe try through stock recovery, just as a precautionary measure.
P l e a s e do not try this
So I tried using FlashFire to flash the G900AZ firmware and I HARD BRICKED MY PHONE.
If anyone wants to give me advice on how to unbrick it PLEASE DO because I have to put all my development on hold indefinitely until I can unbrick it or buy a new one (which isn't likely because I don't have the cash for that right now).
AptLogic said:
So I tried using FlashFire to flash the G900AZ firmware and I HARD BRICKED MY PHONE.
If anyone wants to give me advice on how to unbrick it PLEASE DO because I have to put all my development on hold indefinitely until I can unbrick it or buy a new one (which isn't likely because I don't have the cash for that right now).
Click to expand...
Click to collapse
Try using a debrick image.
NavSad said:
Try using a debrick image.
Click to expand...
Click to collapse
I can't get the phone to boot, not even into Download Mode
AptLogic said:
I can't get the phone to boot, not even into Download Mode
Click to expand...
Click to collapse
Does it show up as qualcomm qhusb hulk when connected to your pc in device manager?
NavSad said:
Does it show up as qualcomm qhusb hulk when connected to your pc in device manager?
Click to expand...
Click to collapse
I took the battery out of the phone and hooked it up to my computer and its showing up as "RELINK HS-USB QDLoader 9008 (COM14)" in device manager
AptLogic said:
I took the battery out of the phone and hooked it up to my computer and its showing up as "RELINK HS-USB QDLoader 9008 (COM14)" in device manager
Click to expand...
Click to collapse
I would try this method:
Grab a sdcard
Grab a debrick image here:https://www.androidfilehost.com/?fid=457095661767140194
Then put the sdcard in your computer and use Win32 DiskImager to write to the sdcard. After that, put the sdcard in your phone and boot into Download Mode.
If your phone isn't fixable using this method you'd have to try JTAG.
NavSad said:
I would try this method:
Grab a sdcard
Grab a debrick image here:UPLOADING
Then put the sdcard in your computer and use Win32 DiskImager to write to the sdcard. After that, put the sdcard in your phone and boot into Download Mode.
If your phone isn't fixable using this method you'd have to try JTAG.
Click to expand...
Click to collapse
Is the debrick image just the first 200MB of the phone's data?
Is it possible to flash a tmobile stock ron onto the verizon note 4?
No, without proper files I wouldn't bother. Even if you successfully boot it up, data ...WiFi and important things of that nature won't work
gb5393 said:
Is it possible to flash a tmobile stock ron onto the verizon note 4?
Click to expand...
Click to collapse
Nope. Verizon and AT&T models have encrypted bootloader that won't be unlocked to flash a custom ROM or another factory ROM not signed with the correct Samsung firmware keys. Sell it and get the T-Mobile version if you want everything to work properly and have full control over your device.
niftydl said:
Nope. Verizon and AT&T models have encrypted bootloader that won't be unlocked to flash a custom ROM or another factory ROM not signed with the correct Samsung firmware keys. Sell it and get the T-Mobile version if you want everything to work properly and have full control over your device.
Click to expand...
Click to collapse
I was afraid of something like that. I knew it was potentially possible because I have done it to my S4, went from Telus to T-Mo.
Hello Guys , i have the T-mob n4 , my question is: can i flash a unbranded n4 firmware on my T-mob ?
I was just curious if I do root my phone with the ping pong root that just came out. Would I be able to flash any galaxy s6 rom or do they have to be specific to the variant I have?
No, not until someone clever can unlock our bootloaders so we can utilize the necessary custom recovery, twrp or clockwork mod.
Hello, I currently have a few Samsungs (old, S3), and they are all rooted (I am familiar with rooting, firmware loading via Odin, TWRP/CWM, etc). I have read a large number of posts on how the Galaxy S5 after 5.X is boot loader locked. I was gifted with a AT&T Samsung Galaxy S5, with the Sim unlock code (and I would like to use it), however, it has been updated to G900AUCS4CPA2. To add insult to injury, I am on T-Mobile.
Forum posts have indicated that the only requirement to move to T-Mobile is to change the sim. However, it would be nice to use the wifi calling, etc (or at least a T-Mobile rom). Even though the bootloader is locked, is there a way to install a Tmobile S5 5.X or 6.X rom? It seems like installing different AT&T roms via Odin is possible, as long as they are >=5.X. Is there a way to install a T-Mobile rom via Odin?
Barring all of that, is there a way to install a totally generic rom, and not be AT&T branded/bloated/etc?
Thank you.
No. The locked bootloader prevents all of that.
shortydoggg said:
No. The locked bootloader prevents all of that.
Click to expand...
Click to collapse
Ok, but it came with 6.0 and I downgraded to PA2. So there is no way to install anything else?
Backstory: I initially tried and failed to install 4.4.2, and with more reading realized that I was on the "bootloader locked" 6.0, and that I had thrashed the current rom that was installed. I then found an XDA post on moving back to 6.0, but it starts with PA2, which installed successfully and the phone is on PA2 (the rom I posted in the beginning of the thread). So, I can seemingly install AT&T roms, as long as they are 5.0+?? I just can not move anywhere else??
Thank you for your input.