Rom Installation Issues With Safe Strap - AT&T Galaxy Note 3 Q&A, Help & Troubleshooting

I am fairly new to using the Galaxy Note 3, but an experienced user and firm believer in flashing roms and gaining root access to our Android devices. I have tried multiple roms on my device, and with every single rom they fail to install. I get an error that says "E: Error executing updater binary in zip" I have tried reinstallimg, wiping the device, even formatting the system with no luck. Any answers are very much appreciated.
Btw, I know my bootloader is locked with the AT&T variant and am using the Safe Strap version 3.75 specifically for my model N900a on kitkat firmware NC2 if this helps any!

With a locked bootloader, only custom ROMs based off a stock Samsung rom can be flashed to the n900a.

I'm new, and not sure if this is the right place to comment haha

audit13 said:
With a locked bootloader, only custom ROMs based off a stock Samsung rom can be flashed to the n900a.
Click to expand...
Click to collapse
The rom I was trying to flash was supposed to be based off of Samsung's touchwiz, a full port from the g9200. I'm a little confused here, on the download page here in XDA forums, the instructions and download page said it was specifically for my model and that it would work. The rom's name is Aurora Note 3 Full G9200 Port v3

Often, an updater script error during the flash process indicates that the phone's minimum requirements are not met for the ROM to install.
Is this the ROM: https://forum.xda-developers.com/note-3-att/development/10-11-15-t3223180 ?
This appears to be a Lollipop ROM as indicated in the first post which means the phone probably needs to be running a Lollipop bootloader and modem.

audit13 said:
Often, an updater script error during the flash process indicates that the phone's minimum requirements are not met for the ROM to install.
Is this the ROM: https://forum.xda-developers.com/note-3-att/development/10-11-15-t3223180 ?
This appears to be a Lollipop ROM as indicated in the first post which means the phone probably needs to be running a Lollipop bootloader and modem.
Click to expand...
Click to collapse
This is a screen shot of the directions I was following in order to be able to update to the rooted lollipop ROM.

Thread closed, you must use instructions (posted here on forums) to update to rooted lollipop for you to be able to flash custom roms for your N900a device. You must root lollipop, with root access you flash NC2 flasher apk to flash the kernel needed to use safestrap after that boot into safestrap and then flash the rom of your choice and flash the OC1 kernel so your device will boot back on. And there you have it!

Related

[Q] [q] i537 4.4.2 on i9295

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 .

[Q] Remove Malware by Flashing a New Rom.

I wanted to flash my ROM to the stock ROM to remove any possible malware.
If I flash to a custom ROM will the Malware be removed?
Not really sure if I have actual Malware, but want to do it just in case. It's one of those random numbers showing up on the data usage screen.
Regardless, I want to act as if it were a virus or malware. Will flashing to a Custom ROM get me the results I am looking for?
Just return the device to stock via flashing the stock images. During that process you can command to erase user data and in the end you will have a phone like it came out the box.
Is that like a nomral factory reset?
I was trying to do this. http://forum.xda-developers.com/moto-x/general/guide-moto-x-return-to-100-stock-using-t2446515
The link for the firmware was broken.
Sp00ns said:
Is that like a nomral factory reset?
I was trying to do this. http://forum.xda-developers.com/moto-x/general/guide-moto-x-return-to-100-stock-using-t2446515
The link for the firmware was broken.
Click to expand...
Click to collapse
Look for your firmware here.
http://forum.xda-developers.com/moto-x/general/info-tip-web-sites-official-leaked-roms-t2923347
XT1049
Could not find my rom, but I found it here
iKrYpToNiTe said:
Yes please Safestrap Recovery
Click to expand...
Click to collapse
(Can't post directly there with less than 10 posts.
So this, Safestrap recovery, is only if your already rooted, right? I would be following "For unlocked users" instructions if I have never done anything to my phone. It is a late 2013 version I think it may have an OTA 4.4 update, though not sure if that applies since its not rooted or anything.
The instructions say "1. Boot into TWRP 2.7 factory reset then install the rom."
But I need root access to install twrp?
I suppose using the ROM for my phone with the instructions form he thread I was looking at before (linked in prior post) will be a bad idea.
Since I have done nothing to my phone (i think an ota update to 4.4.2), can't I simply do a custom image recovery and have it be okay?
This thread seems to suggest i can just us RS LITE and boot the recovery image I pulled from the other thread using RSDLITE.
Would that work out? Should I, Can I, use the safestrap or unlocked image from here (iKryptonites thread)? I wasn't able to find my rom in the other links you posted, though else were it was hinted that I could use a sprint rom.
With a locked bootloader and no root, you have no reason to think about custom recoveries, SafeStrap, and ROMs.
If you want to upgrade to 4.4.4, flash this http://www.filefactory.com/file/63sfruck3srr/REPW_XT1094_4.4.4_KXE21.187-L2.24_cid6_CFC.xml.zip in RSD Lite.
If you want to stay on 4.4.2, flash this http://www.filefactory.com/file/6ra...A20.16-1.24-1.12-12-release-keys-cid6.xml.zip in RSD Lite.
I would recommend flashing 4.4.2 (if that's what is currently on your phone) then check out Sunshine to see if it will unlock your bootloader. If you need instructions on how to use RSD Lite, use Google. Do not try to downgrade the firmware on your phone.
nhizzat said:
With a locked bootloader and no root, you have no reason to think about custom recoveries, SafeStrap, and ROMs.
If you want to upgrade to 4.4.4, flash this http://www.filefactory.com/file/63sfruck3srr/REPW_XT1094_4.4.4_KXE21.187-L2.24_cid6_CFC.xml.zip in RSD Lite.
If you want to stay on 4.4.2, flash this http://www.filefactory.com/file/6ra...A20.16-1.24-1.12-12-release-keys-cid6.xml.zip in RSD Lite.
I would recommend flashing 4.4.2 (if that's what is currently on your phone) then check out Sunshine to see if it will unlock your bootloader. If you need instructions on how to use RSD Lite, use Google. Do not try to downgrade the firmware on your phone.
Click to expand...
Click to collapse
Okay, got it thanks. All i Wanted to do was just flash my phone into anything for the afore mentioned reasons

[Q] Confirm Rooted Update to Lollipop

Can someone confirm that to update from Android 4.2.2 Rooted & S-Off to Android 5.0.1 while maintaining Root and S-Off, I just need to flash a custom ROM based on Android 5.0.1?
I would like the updates and particularly compatibility with recent apps, as I've fallen behind on versions (4.2.2 being evident of that).
I've read around several threads on the forum and have been getting conflicting understandings (most likely my interpretations, not so much the actual wording). For reference,
http://forum.xda-developers.com/htc-one-m8/help/how-perform-ota-update-to-lollipop-t3026182
http://forum.xda-developers.com/ver...-to-update-to-lollipop-rooted-htc-m7-t3111435
The second link suggests flashing santod's ROM should do the trick.
Based on santod's walkthrough, since I am on KitKat 4.2.2 and firmware/software number 1.10.605.15, I would:
Flash the 1.10.605.15 firmware from the boot menu (holding power when phone is turning on and loading the zip),
Flash the Firmware Combo for m7vzw Lollipop using adb
Don't need to do Radios or Kernel because those were previously included,
But do flash recovery
Let phone boot and all set on Lollipop
Is this correct, or do I need to flash a recovery or something to be able to update to something running Lollipop?
Thanks!
gravitach007 said:
Can someone confirm that to update from Android 4.2.2 Rooted & S-Off to Android 5.0.1 while maintaining Root and S-Off, I just need to flash a custom ROM based on Android 5.0.1?
I would like the updates and particularly compatibility with recent apps, as I've fallen behind on versions (4.2.2 being evident of that).
I've read around several threads on the forum and have been getting conflicting understandings (most likely my interpretations, not so much the actual wording). For reference,
http://forum.xda-developers.com/htc-one-m8/help/how-perform-ota-update-to-lollipop-t3026182
http://forum.xda-developers.com/ver...-to-update-to-lollipop-rooted-htc-m7-t3111435
The second link suggests flashing santod's ROM should do the trick.
Based on santod's walkthrough, since I am on KitKat 4.2.2 and firmware/software number 1.10.605.15, I would:
Flash the 1.10.605.15 firmware from the boot menu (holding power when phone is turning on and loading the zip),
Flash the Firmware Combo for m7vzw Lollipop using adb
Don't need to do Radios or Kernel because those were previously included,
But do flash recovery
Let phone boot and all set on Lollipop
Is this correct, or do I need to flash a recovery or something to be able to update to something running Lollipop?
Thanks!
Click to expand...
Click to collapse
I didn't read everything in the links u posted, but the update to 5.0.2 will NOT remove S-off or turn u back to S_on, and will not re-lock bootloader, but it will remove root, but since it doesn't relock bootloader, all u have to do is re-flash custom recovery in fastboot , and then re-flash supersu from custom recovery.

Best Way and ROM (Note 7 Port) to Flash my SMN900A?

Hi recently few members oriented me about the note 3 att version issues when trying to add a new port to it. I read a little and now i am looking for recommendations to get the best (fastest, clean, uptodate) por for my phone. Opinion recommendations are welcome. I am looking for something stable.
If the n900a is running a 4.3 or newer bootloader, the bootloader is locked which means twrp cannot be installed to the phone and the phone will only run custom roms that can be flashed with safestrap or possibly flash fire.
audit13 said:
If the n900a is running a 4.3 or newer bootloader, the bootloader is locked which means twrp cannot be installed to the phone and the phone will only run custom roms that can be flashed with safestrap or possibly flash fire.
Click to expand...
Click to collapse
I think is running the old version. I checked the AP and it ends in OC2
With oc2, the bootloader is locked.
audit13 said:
If the n900a is running a 4.3 or newer bootloader, the bootloader is locked which means twrp cannot be installed to the phone and the phone will only run custom roms that can be flashed with safestrap or possibly flash fire.
Click to expand...
Click to collapse
and there is a way out of this? i cant really be sure some posts says you cant soe post there are ways to get something up
Nope, I know of no way around the locked bootloader. Same situation exists for the AT&T Samsung s4 which also has a locked bootloader.
I have never seen a post where someone can run twrp or cwm on an at&t s4 or note 3 with a locked bootloader.
Ohh well there goes my hope i guess i cant do anything. Any other kind of modification i can do to this phone?
You can root to remove bloatware. You can also use safestrap to flash some custom ROMs. Look in the development thread for ROMs that work with a locked bootloader. Here's an example: http://forum.xda-developers.com/showthread.php?t=2786666
audit13 said:
You can root to remove bloatware. You can also use safestrap to flash some custom ROMs. Look in the development thread for ROMs that work with a locked bootloader. Here's an example: http://forum.xda-developers.com/showthread.php?t=2786666
Click to expand...
Click to collapse
Do you have a link to any tutorials showing how to root a n900a without needing TWRP? All the guides I am seeing are not n900a specific or tie-in custom ROM flashing as well which is obviously not applicable in this case.
This post may help: http://forum.xda-developers.com/showpost.php?p=59666958&postcount=2
audit13 said:
You can root to remove bloatware. You can also use safestrap to flash some custom ROMs. Look in the development thread for ROMs that work with a locked bootloader. Here's an example: http://forum.xda-developers.com/showthread.php?t=2786666
Click to expand...
Click to collapse
oh well you try no note 7 port for me thanks for the help
audit13 said:
This post may help: http://forum.xda-developers.com/showpost.php?p=59666958&postcount=2
Click to expand...
Click to collapse
It would help, but I'm already on 5.0 OC2. Is is even possible to root at this point?
It only takes 10 minutes to Odin back to 4.4.4, which can be rooted.
http://forum.xda-developers.com/note-3-att/general/kitkat-4-4-4-n900aucudnl1-odin-tars-t2999317
Then I highly recommend the AryaMod ROM. Insanely fast and the battery lasts forever.
http://forum.xda-developers.com/note-3-att/development/rom-aryamod-v8-3-tw-lollipop-att-t3422443

A few Questions from a Noobie

Hi, im new to Note 5 Dev. and been out of the loop since it was released. i had a Sony Xperia play and a Galaxy s3 before and know how to do the basic stuff to do custom roms and flash stuff etc. to those Phones. But a Note 5 is different, running on Lollipop, having EFS partition stuff and OEM unlock Stuff. i just want to ask a few questions to make sure i don't do something stupid (i already did some of the research for answers on some of this for a few days now and some are Informative and Awesome, but a little outdated) so tnx in advance kind People :fingers-crossed:
My Device: SM-N920C (UAE)
Android Ver: 5.1.1 (Lollipop) Stock
Questions:
1.) Can i Revert back to 5.1.1 (lollipop) stock/ [Downgrade] , IF i decided to update to Nougat Stock?? (just curious ) and if yes, can you kindly link me to a process? if not, then that's fine too :laugh:
2.) Do you have to Enable OEM unlock if Updating Stock (in my case Nougat)??
I red somewhere on Magisk thread here on XDA that it can Grant Root Access to 5.0+ . If so, installing TWRP and Flashing Magisk on 5.1.1 involves Enabling USB Debugging and OEM Unlock.
3.) Do i have to Enable OEM Unlock Forever now? cause i saw some threads says that if you disable it, you will have a bootloop or a soft brick and will have to Flash Stock again and repeat. (don't really have a problem with it being Enabled, but the other people in Tutorials , Vid. Tutorials and Thread Posts just mentions "Enable it". And never really says after the process is done u can Disable it and stuff.), just want to have that information, cause i Understand that OEM is a LOCK that Even if someone steals your phone and has a lock in it. they can't just Flash a Stock Rom on it to Unlock it. [great feature] :fingers-crossed:
4.) if i have a Custom Recovery and Rooted my phone ver. 5.1.1 successfully, can i still Unroot it and go back to Stock 5.1.1?? also applies to other Versions of android. EX. nougat Stock then i root it, will i still unroot it and go back to stock?
5.) Do you need to be in a Specific Version of android to use the Custom Roms?? i mean i'm in android 5.1.1 [if rooted], can i flash a Nougat Custom Rom or a s8 port etc.?? or do i need to be in Stock Nougat > Root it > then flash Custom Nougat Roms?
That is all, Sorry if all the Questions are Freakin Long Shahaha, i just want to be specific so all the people who are also newbies can understand the questions and have answers. Tnx again for the people who have the patience to read and answer these questions. :highfive:
shadowhog006 said:
Hi, im new to Note 5 Dev. and been out of the loop since it was released. i had a Sony Xperia play and a Galaxy s3 before and know how to do the basic stuff to do custom roms and flash stuff etc. to those Phones. But a Note 5 is different, running on Lollipop, having EFS partition stuff and OEM unlock Stuff. i just want to ask a few questions to make sure i don't do something stupid (i already did some of the research for answers on some of this for a few days now and some are Informative and Awesome, but a little outdated) so tnx in advance kind People :fingers-crossed:
My Device: SM-N920C (UAE)
Android Ver: 5.1.1 (Lollipop) Stock
Questions:
1.) Can i Revert back to 5.1.1 (lollipop) stock/ [Downgrade] , IF i decided to update to Nougat Stock?? (just curious ) and if yes, can you kindly link me to a process? if not, then that's fine too :laugh:
2.) Do you have to Enable OEM unlock if Updating Stock (in my case Nougat)??
I red somewhere on Magisk thread here on XDA that it can Grant Root Access to 5.0+ . If so, installing TWRP and Flashing Magisk on 5.1.1 involves Enabling USB Debugging and OEM Unlock.
3.) Do i have to Enable OEM Unlock Forever now? cause i saw some threads says that if you disable it, you will have a bootloop or a soft brick and will have to Flash Stock again and repeat. (don't really have a problem with it being Enabled, but the other people in Tutorials , Vid. Tutorials and Thread Posts just mentions "Enable it". And never really says after the process is done u can Disable it and stuff.), just want to have that information, cause i Understand that OEM is a LOCK that Even if someone steals your phone and has a lock in it. they can't just Flash a Stock Rom on it to Unlock it. [great feature] :fingers-crossed:
4.) if i have a Custom Recovery and Rooted my phone ver. 5.1.1 successfully, can i still Unroot it and go back to Stock 5.1.1?? also applies to other Versions of android. EX. nougat Stock then i root it, will i still unroot it and go back to stock?
5.) Do you need to be in a Specific Version of android to use the Custom Roms?? i mean i'm in android 5.1.1 [if rooted], can i flash a Nougat Custom Rom or a s8 port etc.?? or do i need to be in Stock Nougat > Root it > then flash Custom Nougat Roms?
That is all, Sorry if all the Questions are Freakin Long Shahaha, i just want to be specific so all the people who are also newbies can understand the questions and have answers. Tnx again for the people who have the patience to read and answer these questions. :highfive:
Click to expand...
Click to collapse
1)If you flash stock 7.0 on your device if available then its hard to revert to back to stock 5.1.1 as there is thread in Question&Answers section about downgrading from 6.0.1 to 5.1.1 but many are unsuccessful(I have successfully downgraded from 7.0 to 6.0.1 but Cant confirm about 5.1.1 as google has changed many security policies in updates versions like 6.0.1 or 7.0 which will block your bootloader to downgrade easily/Issue you will face like lossing of baseband or corrupt imei which will block you from receiving network signal)
2)Yes its very important to enable Oem unlock and usb debugging while flashing any stock firmware using odin to avoid DM-Verity/SW Check Fail/Custom Binary blocked by FRP like issues which are hard to solve enough OR you will might hard brick your device which will be difficult to make it live again( AFAIK to flash TWRP or Any root access using odin there is instruction to enable Oem Unlock before flashing always remember it as a essential step before flashing anything using odin)
3)Yes once you enable Oem unlock for purpose of modification of your device, it needs to be unlocked or even its enabled by default to overcome reported issue like infinite bootloop or Many i mentioned in my 2nd Post And Oem unlock allows your bootloader to be customised by flashing mods or roms which is by default locked so that you could not easily modify your device as well as to avoid further modification issues
4)If you choose to stay at 5.1.1 and rooted your device with installed TWRP then yes you can unroot it by flashing 5.1.1 using odin( In case your on 6.0.1 or Even on 7.0 you can unroot your device with the same process but here to remind you that you need to flash stock 6.0.1 or 7.0 respectively version on which you rooted your device So if you will try to unroot it by flashing 5.1.1 again while your on 7.0 rooted device then again here downgrade issue which will probably give you mentioned error as a result)
5)To use custom nougat based roms or any S8+ port based on 7.0 you should atleast upgrade your bootloader and modem to 6.0.1( If your rooted on 5.1.1 and try installing nougat roms then your device will not boot as your using old bootloader, so upgrade bootloader or modem either to 6.0.1 or you can update whole system to 7.0>root>install TWRP>flash custom nougat based roms or s8+ ports afterall choice is your as if you want to upgrade only BL and Modem to 6.0.1 or want to upgrade system with BL and Modem to 7.0, i will mention here is BL and Modem for 7.0 are also available to flash you can find those on dr.ketan rom n10 installation instruction section in Samsung galaxy note 5>Android development>Dr.ketan Rom N10 instead of whole system update but Flashing Stock full firmware is always recommended for good reception and avoid glitches)
I think i have tried to fulfil all of your queries as far possible by myself
Regards,
AssassinCreed-Xda Developers
Too bad about the answer to the 3rd question, that feature would've been nice to have. but oh well. shahahaha
~Ooh!! i have a follow up question regarding your Answer to the 4th question. Can i also flash other Countries Stock firmware?? for example: mine is Stock 5.1.1 [UAE] can i flash Stock 5.1.1 [USA] or other Country variants?? [of course unlocked bootloader] , i searched again here for people who did that and for some reason they encounter Errors and Unable to revert back to their Original Stock Firmwares.
@AssassinCreed Thank you. yup, clear cut answers. Thank you!! :victory: :victory:

Categories

Resources