Related
Hi everyone. I tried finding info on my firmware, but somehow i couldn't find wether or not it is "rootable" it is 12.0.A.1.257, global version. Can someone confirm if it is indeed rootable. Thanks!
skojevac said:
Hi everyone. I tried finding info on my firmware, but somehow i couldn't find wether or not it is "rootable" it is 12.0.A.1.257, global version. Can someone confirm if it is indeed rootable. Thanks!
Click to expand...
Click to collapse
YES its rootable all you need to run the doomloard's event exploit from original dev section.. happy rooting
ok, I checked that thread and now have additional question for anyone who can have a time and knowledge to answer. obviously there is a new stock rom 12.0.A.2.245 for our bellowed SP. now, I have that older version 12.0.A.1.257 and though I tried updating device firmware I receive message that my phone is up to date. so I assumed this is probably due to some drug deal sony have with my operator ( the one the phone came from) and now for some reason sony would not let me update firmware (yet). so my question is next, actually there are several questions:
A. am I'm going to brick my phone if I manually download and update new firmware via flashtool regardless of sony saying my device is up to date?
B. Is this new firmware 12.0.A.2.245 so much better that is actually worth updating? (this should be A)
C. if i root this old firmware and perhaps install CW as well, and than update to the new one, am I'm going to loose both root and CW, or perhaps only CW after updating? or i will get to keep root and CW?
D. is it better to update and than root, or root and than update?
i hope this is not too much. thanks! :angel:
ps. i forgot to say, though my phone came from an operator, it is not sim locked and boot unlock status is YES
skojevac said:
ok, I checked that thread and now have additional question for anyone who can have a time and knowledge to answer. obviously there is a new stock rom 12.0.A.2.245 for our bellowed SP. now, I have that older version 12.0.A.1.257 and though I tried updating device firmware I receive message that my phone is up to date. so I assumed this is probably due to some drug deal sony have with my operator ( the one the phone came from) and now for some reason sony would not let me update firmware (yet). so my question is next, actually there are several questions:
A. am I'm going to brick my phone if I manually download and update new firmware via flashtool regardless of sony saying my device is up to date?
B. Is this new firmware 12.0.A.2.245 so much better that is actually worth updating? (this should be A)
C. if i root this old firmware and perhaps install CW as well, and than update to the new one, am I'm going to loose both root and CW, or perhaps only CW after updating? or i will get to keep root and CW?
D. is it better to update and than root, or root and than update?
i hope this is not too much. thanks! :angel:
ps. i forgot to say, though my phone came from an operator, it is not sim locked and boot unlock status is YES
Click to expand...
Click to collapse
A. no unless u r on unlocked bootloader that should brick our phone.
B. every firmware bring new advantages and disadvanteges..so i think u should upgrade it because camera has been improved! (low light photography)
C no u will loose both root and cwm
D both first update than root !! ROOT IS AWSM!!! it makes u feels that device is actually yours!!
thanks for a quick reply. so, I am going to update first and than do that "flash old kernel - root - flash new kernel" thing. and than backup the TA partition from here http://forum.xda-developers.com/showthread.php?t=2292598
I would like to save the BE and DRM keys 'cause I'm sure I'll unlock bootloader as well that entire process is what makes android so much better that sh**pple. like you said, you actually get to own your device. thanks again and thanks XDA!
Hi Guys, I just got the phone (international/ non-carrier version) yesterday. Updated it to 4.3, and rooted it, following the guide from HTCOneRoot.com.
Everything is fine and dandy, as when I rooted my previous phone. But in my sheer eagerness, I didn't find out that the 4.4 was available also.
I now have a rooted phone, and I can't update it, as it goes directly to TWRP recovery when I try to install. I guess this is what it's supposed to do?
From what I can read you cannot install OTA when you have rooted your phone.
So I tried looking up how to unroot it. But this seems like a rather difficult project, and I am not sure I understand. From what I read I need to download a RUU, to install a stock rom(?) and I tried looking up this, but there are tons to select from, and I haven't the slightest clue which matches my phone. Can anyone be of assistance, as to how I can revert my root and update to 4.4, so I can root my phone with the latest android, instead? I'm not really interested in getting a custom rom on my phone.
Guess I should've read more about rooting before doing it, as I'm kind of a novice, but I'm more a trial and error kinda guy .
Thanks.
Edit: Or should I just find a custom "stock" KitKat ROM, and install that, from my current position? Is that even possible?
Sort of an answer
Faderskibet said:
Hi Guys, I just got the phone (international/ non-carrier version) yesterday. Updated it to 4.3, and rooted it, following the guide from HTCOneRoot.com.
Everything is fine and dandy, as when I rooted my previous phone. But in my sheer eagerness, I didn't find out that the 4.4 was available also.
I now have a rooted phone, and I can't update it, as it goes directly to TWRP recovery when I try to install. I guess this is what it's supposed to do?
From what I can read you cannot install OTA when you have rooted your phone.
So I tried looking up how to unroot it. But this seems like a rather difficult project, and I am not sure I understand. From what I read I need to download a RUU, to install a stock rom(?) and I tried looking up this, but there are tons to select from, and I haven't the slightest clue which matches my phone. Can anyone be of assistance, as to how I can revert my root and update to 4.4, so I can root my phone with the latest android, instead? I'm not really interested in getting a custom rom on my phone.
Guess I should've read more about rooting before doing it, as I'm kind of a novice, but I'm more a trial and error kinda guy .
Thanks.
Edit: Or should I just find a custom "stock" KitKat ROM, and install that, from my current position? Is that even possible?
Click to expand...
Click to collapse
Hey man, so to find the right ruu go here htcdev webiste, go under kernel source code and then choose device as the one and then choose carrier and download one of the matching ones.
For the other stuff I'm in the same boat as you. Just waiting for answers...I would try looking at youtube and type how to unbrick htc one and try those first. Didn't work for me but might for you.
christianpencz said:
Hey man, so to find the right ruu go here htcdev webiste, go under kernel source code and then choose device as the one and then choose carrier and download one of the matching ones.
For the other stuff I'm in the same boat as you. Just waiting for answers...I would try looking at youtube and type how to unbrick htc one and try those first. Didn't work for me but might for you.
Click to expand...
Click to collapse
Thanks. I'll look that up.
I am not bricked, as the situation is now. I just have a rooted phone, working with 4.3. And I want to upgrade to 4.4.
So I guess I have to choose HTC as carrier? I live in Denmark and am unsure whether to choose EU or EU NFC as region? Also what kernel version do I want to download? I am somewhat unsure what to do next.
Faderskibet said:
Thanks. I'll look that up.
I am not bricked, as the situation is now. I just have a rooted phone, working with 4.3. And I want to upgrade to 4.4.
So I guess I have to choose HTC as carrier? I live in Denmark and am unsure whether to choose EU or EU NFC as region? Also what kernel version do I want to download? I am somewhat unsure what to do next.
Click to expand...
Click to collapse
Do a fastboot getvar all, and choose the RUU that matches your MID and your CID
I've only rooted my phone so far. From what I understand I can just install a "custom 4.4" from this point, right?
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 .
So I just bought the XT1068 and I know that the L update is still not released in India so how can I flash it instead of waiting for the OTA? Any step-by-step guides would be helpful because I am quite the noob. My phone is brand new, just removed out of the box so please tell me how to flash the update.
Ajit99 said:
So I just bought the XT1068 and I know that the L update is still not released in India so how can I flash it instead of waiting for the OTA? Any step-by-step guides would be helpful because I am quite the noob. My phone is brand new, just removed out of the box so please tell me how to flash the update.
Click to expand...
Click to collapse
Check this out:
http://droiddefy.com/how-to-update-...69-to-official-android-5-0-lollipop-manually/
That is the best tutorial i could find! Cheers!
Edit:
There could be some bugs for dual sim models. the xt1069. Make sure to read the comments and especially the tutorial
Ajit99 said:
So I just bought the XT1068 and I know that the L update is still not released in India so how can I flash it instead of waiting for the OTA? Any step-by-step guides would be helpful because I am quite the noob. My phone is brand new, just removed out of the box so please tell me how to flash the update.
Click to expand...
Click to collapse
Mate, I'd hold on a bit if I were you . You have to unlock your bootloader to flash these ROMs. Unlocking means losing your warranty (special case in India :crying. And there's also tiny bugs in those ROMs.
aditya.upadhyaya said:
Mate, I'd hold on a bit if I were you . You have to unlock your bootloader to flash these ROMs. Unlocking means losing your warranty (special case in India :crying. And there's also tiny bugs in those ROMs.
Click to expand...
Click to collapse
It all depends - while I will leave the research up to you, I was able to update without unlocking the bootloader on an xt1064. The trouble is that all the pieces have to fall into place correctly, meaning that you have to have the right update file for your build (and YOUR device - xt1068). My update process was haphazardly documented here. Basically, I started out with a carrier locked (Consumer Cellular) version of the phone, running their specific build. I unlocked the phone's sim lock via online vendor, flashed over the latest factory firmware I could find at the time (21.11.23.titan_retuaws). from there, I installed the specific update to go from 21.11.23 to 22.21.25 (where I am now). but that's the kicker - you need the OTA files that correspond to your exact build(s) and there may be more than one to get you all the way up to current.
Anyway, I did all of this using official, signed OTA files and firmware and more importantly, with a locked bootloader.
joeparker54 said:
It all depends - while I will leave the research up to you, I was able to update without unlocking the bootloader on an xt1064. The trouble is that all the pieces have to fall into place correctly, meaning that you have to have the right update file for your build (and YOUR device - xt1068). My update process was haphazardly documented here. Basically, I started out with a carrier locked (Consumer Cellular) version of the phone, running their specific build. I unlocked the phone's sim lock via online vendor, flashed over the latest factory firmware I could find at the time (21.11.23.titan_retuaws). from there, I installed the specific update to go from 21.11.23 to 22.21.25 (where I am now). but that's the kicker - you need the OTA files that correspond to your exact build(s) and there may be more than one to get you all the way up to current.
Anyway, I did all of this using official, signed OTA files and firmware and more importantly, with a locked bootloader.
Click to expand...
Click to collapse
NIIIICEEE!!!!!! But the problem here is, we don't have Lollipop OTAs for XT1068/69 to do that.:crying:
I recently made an insurance claim for my phone and had to send my unlocked firmware note 8 back. Problem I'm having now is, I cant get the new one on an unlocked firmware. I keep getting errors in all the Odins I have. I dont know much about the v4 bootloader or when it was locked. I was able to gi back to Nougat on my old phone and then upgrade back oreo. That was in August though. Any help would be appreciated. I cant stand this ATT ****!
cameronw2023 said:
I recently made an insurance claim for my phone and had to send my unlocked firmware note 8 back. Problem I'm having now is, I cant get the new one on an unlocked firmware. I keep getting errors in all the Odins I have. I dont know much about the v4 bootloader or when it was locked. I was able to gi back to Nougat on my old phone and then upgrade back oreo. That was in August though. Any help would be appreciated. I cant stand this ATT ****!
Click to expand...
Click to collapse
You can only flash the same bootloader v4 firmwares or higher from now on. No downgrading possible to bootloader v3 or below!
Can't even go back to Nougat (that was on bootloader v3 and below)!
If you are just need the unbranded firmwares look for the ones with the bootloader v4.
Eg N950U(U1)SQS"4"CRH1. The 4 in "" is your bootloader version.
If you want to root or go back to nougat then you'll need to talk to ATT for another phone that's on bootloader v3 or below.
BluePhnx said:
You can only flash the same bootloader v4 firmwares or higher from now on. No downgrading possible to bootloader v3 or below!
Can't even go back to Nougat (that was on bootloader v3 and below)!
If you are just need the unbranded firmwares look for the ones with the bootloader v4.
Eg N950U(U1)SQS"4"CRH1. The 4 in "" is your bootloader version.
If you want to root or go back to nougat then you'll need to talk to ATT for another phone that's on bootloader v3 or below.
Click to expand...
Click to collapse
Could you possibly link me the the firmware I do need? I would really appreciate as I'm stuck on this current firmware. I've looked and looked. I'm just unable to find the right firmware. I suppose it's possible I'm not getting the right one. Idk.
cameronw2023 said:
Could you possibly link me the the firmware I do need? I would really appreciate as I'm stuck on this current firmware. I've looked and looked. I'm just unable to find the right firmware. I suppose it's possible I'm not getting the right one. Idk.
Click to expand...
Click to collapse
The easiest is to use SamFirm to download the firmware. Then use modified ODIN 3.13.1 to flash it.
Mr. Orange 645 said:
The easiest is to use SamFirm to download the firmware. Then use modified ODIN 3.13.1 to flash it.
Click to expand...
Click to collapse
I figured all out! I managed fo flash the latest unlocked without any issues.