I'm reading some conflicting stuff from years back on xda and now I'm not sure what the latest info is. I'm planning to purchase a g900a to replace my g900f that went crazy and I enjoyed the freedom of flashing whatever custom rom I wanted...
Is that still available to a g900a? The first hurdle would be rooting which I read was achieved using towel root.
The 2nd would be getting it to work on a different carrier since I live in the Philippines. I read that using a custom rom would negate this issue...
Then last would be the custom rom. Can I flash other rooms if it is rooted?
Where does the bootloader fit in all of this?
Sadly, it is still stuck on certain custom roms, and with the bootloader remaining locked by AT&T, the phone's age, and lack of developer interest, it's likely going to remain that way.
Be very wary of buying an AT&T Samsung model if you're interested in easy-rooting and ROMS like LineageOS and whatnot. Otherwise you'll probably just have to look elsewhere.
Related
I get what a bootloader is--the low level programming that checks everything and then boots the OS. And I have read that when they say "locked bootloader" it means "encrypted bootloader".
Have previous bootloaders been un-encrypted and thus made flashable? Or was some "exploit" found that enabled the bootloader to be replaced with one that would be unencrypted and thus ROMs could be flashed?
It sounds like the bootloader being locked/encrypted prevents much being done in the way of custom ROM flashing. So at this point we have Safestrap, unless that doesn't work on the AT&T g900a.
So, what are the designers working on at this time--unencrypting the bootloader, finding a way to simply replace it, or using something like Safestrap to create a space where a different ROM can be placed and the bootloader bypassed in some way?
I suppose I am curious to find out just how tough this locked bootloader problem is for the devs.
Sent from my SAMSUNG-SM-G900A using xda premium
kettir said:
I get what a bootloader is--the low level programming that checks everything and then boots the OS. And I have read that when they say "locked bootloader" it means "encrypted bootloader".
Have previous bootloaders been un-encrypted and thus made flashable? Or was some "exploit" found that enabled the bootloader to be replaced with one that would be unencrypted and thus ROMs could be flashed?
It sounds like the bootloader being locked/encrypted prevents much being done in the way of custom ROM flashing. So at this point we have Safestrap, unless that doesn't work on the AT&T g900a.
So, what are the designers working on at this time--unencrypting the bootloader, finding a way to simply replace it, or using something like Safestrap to create a space where a different ROM can be placed and the bootloader bypassed in some way?
I suppose I am curious to find out just how tough this locked bootloader problem is for the devs.
Sent from my SAMSUNG-SM-G900A using xda premium
Click to expand...
Click to collapse
From what I have seen very few bootloaders have ever been unencrypted publicly by the community. There have been some devices although rare that the manufacturer has had a change of heart and allowed to be decrypted in most cases at the cost of your factory warranty.
My last phonetic galaxy s3 was not encrypted and allowed an insecure boot image. This did not check to make sure the rom, modem, or kernel were not signed. The development community is still very alive today years after its release.
Hashcode's safestrap allows for a custom rom but to my knowledge has never allowed a viable custom kernel. He did amazing work with this technology around the Motorola Droid 3 but the community never really built up support for the device.
It's a shame as my old s3 with a good rom and custom kernel is much much faster and more usable than this locked down s5.
Sent from my ASUS Transformer Pad TF700T using Tapatalk
spasch said:
From what I have seen very few bootloaders have ever been unencrypted publicly by the community. There have been some devices although rare that the manufacturer has had a change of heart and allowed to be decrypted in most cases at the cost of your factory warranty.
Click to expand...
Click to collapse
I did a quick Google to find out if other carriers had the s5 with an unencrypted bootloader. Nothing came up immediately except mention of the Verizon s5 developer edition. Android Police had this to say about the developer version:
The unlockable bootloader on the Developer Edition allows end users to easily flash a custom recovery, and then root or flash a custom ROM. Other than the unlockable bootloader, this Galaxy S5 is exactly the same as the standard Verizon model in both hardware and software.
I did a comparison of the straight Verizon s5 to the GSM s5 on Phonescoop and noticed differences (less GSM levels). Therefore it would be a loss, as far as performance goes, to get the Verizon developer version.
Overall, I'm happy with my s5. I've got root. I've found ways to get the features I want (often through Xposed.) It definitely seems faster than my s5 even though I'm burdening it with Go Launcher (just to get all the pretty themes.) I can freeze the bloatware or even delete it via Titanium Backup. So I'm not super anxious about it. I just hate being locked out of anything on something I purchased and own.
kettir said:
I did a quick Google to find out if other carriers had the s5 with an unencrypted bootloader. Nothing came up immediately except mention of the Verizon s5 developer edition. Android Police had this to say about the developer version:
The unlockable bootloader on the Developer Edition allows end users to easily flash a custom recovery, and then root or flash a custom ROM. Other than the unlockable bootloader, this Galaxy S5 is exactly the same as the standard Verizon model in both hardware and software.
I did a comparison of the straight Verizon s5 to the GSM s5 on Phonescoop and noticed differences (less GSM levels). Therefore it would be a loss, as far as performance goes, to get the Verizon developer version.
Overall, I'm happy with my s5. I've got root. I've found ways to get the features I want (often through Xposed.) It definitely seems faster than my s5 even though I'm burdening it with Go Launcher (just to get all the pretty themes.) I can freeze the bloatware or even delete it via Titanium Backup. So I'm not super anxious about it. I just hate being locked out of anything on something I purchased and own.
Click to expand...
Click to collapse
Plz sign this
https://www.change.org/petitions/att-give-us-the-freedom-to-modify-and-build-unlock-our-bootloaders
Sent from my SAMSUNG-SM-G870A using XDA Premium 4 mobile app
Hello So I have a brand new, unlocked, Samsung Note 3 (SN-900A - AT&T variety) that I bought from Best Buy. In the next few days I'll be switching to T-Mobile (no comments on carrier switch please), but since the GSM phone is unlocked I can use it on T-Mobile's network
Here is the current status of my phone:
Used Odin to flash back to stock AT&T 4.4.2 ROM from installed NL1 4.4.4
Rooted device on 4.4.2 and then upgraded to rooted/stock AT&T ROM 4.4.4 using SuperSU, BusyBox, and SafeStrap as explained here, here, and here (did not update to Lollipop)
Used Root App VIP to manually disable AT&T bloatware now that I have the phone rooted on 4.4.4
So in its current form my phone is rooted on 4.4.4 and working pretty well. I'm happy thus far and don't want to get too greedy since it works.
However I have a few questions about how to backup my current ROM and about geeting some better understanding about the root and ROM process. I would be quite appreciative if someone could assist me with the answers please!
It appears the original Dev of Safestrap (the core app at the heart of rooting and upgrading the Note 3 in my process) has moved onto greener pastures. Since SafeStrap does not work on 4.4.4 (can't boot into recovery or do backups), what is the replacement tool/utility? Should I use Odin for everything? OdinMobile? CWM? TWRP? FlashFire? I've read a bunch of threads on the differences and I'm having a hard time making heads or tails of it all. The main thing I want to be able to do now is backup my current ROM like you could previously with Safestrap, and update to a new ROM if I so choose.
I never wanted the bloatware - do you think I flashed the wrong ROM? Should I have used a stock ASOP ROM if I didn't want bloatware or is this not possible on the 900A?
Ironically if I had to have bloatware I would have preferred to have T-Mobile's since I will be on their network. Could I have put a T-Mobile ROM image on an AT&T variant of the phone? (just curious)
I used a AT&T stock ROM apparently from those links I posted which propogated the bloatware to 4.4.4, however at least I'm rooted. I believe this was all done to not disturb the KNOX flag. I have a warranty from BestBuy I would like to keep (1 year), but I can't go to AT&T for warranty service (they are not my carrier) and I didn't buy the phone from T-mobile either, so is the warranty worth anything anyway?
I keep reading that the AT&T variant of Note 3 has a 'locked bootloader' and that's what's with going to all the trouble with SafeStarp was about. Essentially it loads an alternate image/ROM not disturbing the stock one so that the KNOX flag is never triggered. Is there a way to unlock the bootloader on this phone or should I even care?
I'm early enough in this process that if I went down the wrong path I could do something different. Any or all help/assistance is greatly appreciated!
atconway said:
Hello So I have a brand new, unlocked, Samsung Note 3 (SN-900A - AT&T variety) that I bought from Best Buy. In the next few days I'll be switching to T-Mobile (no comments on carrier switch please), but since the GSM phone is unlocked I can use it on T-Mobile's network
Here is the current status of my phone:
Used Odin to flash back to stock AT&T 4.4.2 ROM from installed NL1 4.4.4
Rooted device on 4.4.2 and then upgraded to rooted/stock AT&T ROM 4.4.4 using SuperSU, BusyBox, and SafeStrap as explained here, here, and here (did not update to Lollipop)
Used Root App VIP to manually disable AT&T bloatware now that I have the phone rooted on 4.4.4
So in its current form my phone is rooted on 4.4.4 and working pretty well. I'm happy thus far and don't want to get too greedy since it works.
However I have a few questions about how to backup my current ROM and about geeting some better understanding about the root and ROM process. I would be quite appreciative if someone could assist me with the answers please!
It appears the original Dev of Safestrap (the core app at the heart of rooting and upgrading the Note 3 in my process) has moved onto greener pastures. Since SafeStrap does not work on 4.4.4 (can't boot into recovery or do backups), what is the replacement tool/utility? Should I use Odin for everything? OdinMobile? CWM? TWRP? FlashFire? I've read a bunch of threads on the differences and I'm having a hard time making heads or tails of it all. The main thing I want to be able to do now is backup my current ROM like you could previously with Safestrap, and update to a new ROM if I so choose.
I never wanted the bloatware - do you think I flashed the wrong ROM? Should I have used a stock ASOP ROM if I didn't want bloatware or is this not possible on the 900A?
Ironically if I had to have bloatware I would have preferred to have T-Mobile's since I will be on their network. Could I have put a T-Mobile ROM image on an AT&T variant of the phone? (just curious)
I used a AT&T stock ROM apparently from those links I posted which propogated the bloatware to 4.4.4, however at least I'm rooted. I believe this was all done to not disturb the KNOX flag. I have a warranty from BestBuy I would like to keep (1 year), but I can't go to AT&T for warranty service (they are not my carrier) and I didn't buy the phone from T-mobile either, so is the warranty worth anything anyway?
I keep reading that the AT&T variant of Note 3 has a 'locked bootloader' and that's what's with going to all the trouble with SafeStarp was about. Essentially it loads an alternate image/ROM not disturbing the stock one so that the KNOX flag is never triggered. Is there a way to unlock the bootloader on this phone or should I even care?
I'm early enough in this process that if I went down the wrong path I could do something different. Any or all help/assistance is greatly appreciated!
Click to expand...
Click to collapse
When I'm on a 4.4.4 Rom, I use AT&T OC1,NL1,NJ5 SafeStrap Work Around http://forum.xda-developers.com/note-3-att/general/att-nj5-safestrap-t2957471 install the Kernel Flasher http://forum.xda-developers.com/note-3-att/development/nc2-flasher-app-unsafe-t2989141/ grant it Supersu and tap to reboot, it will boot to Safestrap and do your backup or whatever you are doing. Once done you MUST flash the kernel may it be the NL1 or OC1, but you must flash it with Safestrap. The NL1 kernel (SM-N900A_NL1_KERNEL_RecoveryFlashable.zip) is for NL1 and NJ5 Roms and the OC1 kernel (SM-N900A_N900AUCUEOC1_KERNEL_Recovery-Flashable.zip) is only for OC1 Roms. I don't use Mobile Odin or FlashFire. Even though you are on T-Mobile the phone is AT&T which has a locked boot loader, so you can not use CWM or TWRP and you are stuck using only AT&T Roms. You can use Titanium Backup to remove any bloatware (Backup first saves on headache, case something goes wrong or you can freeze it). This is a T-Moible Rom that is ported for AT&T; T-Mobile Alliance Lollipop Rom on ATT Note 3 http://forum.xda-developers.com/note-3-att/general/t-mobile-alliance-rom-att-note-3-t3065127 and since you are on T-Mobile, you wouldn't have to "After the phone came up, I went to settings..general..applications...running .... and found every Tmobile app and cleared cache and disabled them. The real important one here is the Visual Voicemail. Otherwise it will keep on trying to contact Tmobile and then you will get text messages saying there is an error." It is a OC1 Rom (Lollipop) so you would need the SM-N900A_N900AUCUEOC1_KERNEL_Recovery-Flashable.zip because you would flash this in Safestrap once you have used the Kernel Flasher to access Safestrap. [How-To] Update to N900A_NL1 - 4.4.4 and Keep Root (12-24-2014) http://forum.xda-developers.com/note-3-att/general/how-to-root-n900aucudnl1-4-4-4-12-24-t2983357 is just the plain AT&T Rom that's been rooted, that's why you got all that bloatware. I go right here for any Rom I wish to install, Android development for the AT&T Galaxy Note 3 http://forum.xda-developers.com/note-3-att/development Forgot to say, write down your APN settings, so you can still get data. T-Mobile Network: Samsung Galaxy Note 3 (N900) https://support.t-mobile.com/docs/DOC-11447 in case.
Rooted i747 said:
This is a T-Moible Rom that is ported for AT&T; T-Mobile Alliance Lollipop Rom on ATT Note 3 http://forum.xda-developers.com/note-3-att/general/t-mobile-alliance-rom-att-note-3-t3065127 and since you are on T-Mobile...
Click to expand...
Click to collapse
This had all been really helpful, thank you. I've read the post a bunch and followed all the steps. The NC2 flasher is awesome and works great!
However, I'm trying to make heads or tails though of the T-Mobile Alliance ROM version to use (reminder I want a T-Mobile ROM on my AT&T Note 3 since I'm on T-Mobile's network). The underlying link that has the T-Mobile Alliance ROM to actually download states that KNOX is removed and activated (0x1). However the link provided by you to the T-Mobile Alliance flashing instructions page has multiple replies saying KNOX remains undisturbed and is at 0x0 after completion. I'm probably asking the wrong questions, but is the process of using Safestrap regardless of the ROM I'm using prevent KNOX from being tripped? Or is it that the newest version of the Alliance ROM is what would trip KNOX (i.e. should I use an older version of the ROM that doesn't remove KNOX)?
I have everything backed up, downloaded and ready to flash and install. I just want to flash this T-Mobile Alliance ROM but not trip KNOX. Once I can get a clear understanding this I'm ready to move forward and complete it.
atconway said:
This had all been really helpful, thank you. I've read the post a bunch and followed all the steps. The NC2 flasher is awesome and works great!
However, I'm trying to make heads or tails though of the T-Mobile Alliance ROM version to use (reminder I want a T-Mobile ROM on my AT&T Note 3 since I'm on T-Mobile's network). The underlying link that has the T-Mobile Alliance ROM to actually download states that KNOX is removed and activated (0x1). However the link provided by you to the T-Mobile Alliance flashing instructions page has multiple replies saying KNOX remains undisturbed and is at 0x0 after completion. I'm probably asking the wrong questions, but is the process of using Safestrap regardless of the ROM I'm using prevent KNOX from being tripped? Or is it that the newest version of the Alliance ROM is what would trip KNOX (i.e. should I use an older version of the ROM that doesn't remove KNOX)?
I have everything backed up, downloaded and ready to flash and install. I just want to flash this T-Mobile Alliance ROM but not trip KNOX. Once I can get a clear understanding this I'm ready to move forward and complete it.
Click to expand...
Click to collapse
Safestrap will not stop Knox from tripping. If you are not sure, if you Knox will trip or not then I say don't flash it. I never flashed that Rom, so I can't say. The Roms I have used and my Knox still 0X0. Currently on FireKat Deodex NC2 KK V19N3/V19N4 http://forum.xda-developers.com/showthread.php?t=2786666 AllianceROM Lollipop v9.1 http://forum.xda-developers.com/showthread.php?t=2778933 Note 4 Port Evolution 3.0 http://forum.xda-developers.com/note-3-att/development/rom-note-4-port-evolution-1-0-t2982296 Note 4 Port Evolution 3.0 you will have to flash extra things in Safestrap to make it work right.
atconway said:
This had all been really helpful, thank you. I've read the post a bunch and followed all the steps. The NC2 flasher is awesome and works great!
However, I'm trying to make heads or tails though of the T-Mobile Alliance ROM version to use (reminder I want a T-Mobile ROM on my AT&T Note 3 since I'm on T-Mobile's network). The underlying link that has the T-Mobile Alliance ROM to actually download states that KNOX is removed and activated (0x1). However the link provided by you to the T-Mobile Alliance flashing instructions page has multiple replies saying KNOX remains undisturbed and is at 0x0 after completion. I'm probably asking the wrong questions, but is the process of using Safestrap regardless of the ROM I'm using prevent KNOX from being tripped? Or is it that the newest version of the Alliance ROM is what would trip KNOX (i.e. should I use an older version of the ROM that doesn't remove KNOX)?
I have everything backed up, downloaded and ready to flash and install. I just want to flash this T-Mobile Alliance ROM but not trip KNOX. Once I can get a clear understanding this I'm ready to move forward and complete it.
Click to expand...
Click to collapse
Got bored so I tried it. Did not trip Knox and I really didn't see a different from AllianceROM Lollipop v9.1 http://forum.xda-developers.com/showthread.php?t=2778933 Well, I don't care for it, so back to FireKat! :silly:
Thanks for trying it out and your assistance I did the same on my phone immediately after you did and got the same results. It works great and should be a viable option for those like me that have an AT&T phone, but want to load a T-Mobile based ROM.
I'll be curious if that Alliance ROM though stays up to date with the newer versions of Android (i.e. 5.0.2, etc.) It appears to be based on 5.0.0 from what I can tell. Only reason I ask is because my experience with 5.0 on my old S4 has been awful. Fells like I'm back on Android Gingerbread with 500mb of ROM. :S There are so many memory leaks on my S4 now it stinks. 4.4.4 was way better.
Good news is I haven't seen that same issue thus far with the Alliance ROM, so hopefully is worked out whatever shortcomings the OS had.
Is there literally nothing for this? I've got the method to downgrade to 4.1.1 but that only yields root apparently. No custom roms or anything.
Is there anything available for this tablet or remarkable about being on 4.1.1 I've searched both on all boards here on Tab S2 and it seems useless.
Aside from that, is there any way to unlock the simcard slot?
I apologize for the questions but it's looking like the tab may as well stay on 6.0.1.
Thanks for comments and advice, and yes, I've searched up and down (T817T all boards, etc.)
You have got to search and read through a bit more.
I only got this tablet (a used one of course) only 2 days back, so others may be able to help you more.
For me I just rooted the tablet and installed some xposed modules. For my need with the tablet, I don't need anything else.
Unlocking simcard slot has to be done from tmobile. I am not aware of any hacks available in xda.
You can install twrp and root the device if you want. T810/T815 they uses the same chipset. The information I have gathered so far indicate that you can install aosp roms for those models, but you shall not get cellular connectivity. Any chance of having official Nougat on this tablet is very very slim. There are some aosp 7.0 roms, but they are in early developmental stage; things like fingerprint sensor won't work.
Anyone feel free to correct me if I am wrong on any of the things I mentioned.
I no longer have tmobile.
Could I flash the t810 firmware onto the t817 tab s2? This way I could get the updates straight from Samsung.
I was only able to get one ROM to work on mine. Ultimately, I gave up and just kept it stock.
Sent from my SM-N920T using Tapatalk
I'm also frustrated with the T817T. I have been able to root it, flash TWRP, but I have never been able to flash a custom ROM. I have heard that the T815 ROMs should work, but I get an error in TWRP if I try to flash one.
I was reading something in the Note 10.1 2014 forum that you could flash the P605 (International) ROM to the P607T (T-Mobile) if you unzipped the ROM, removed the modem files, and rezipped it. I'm wondering if something like this would work for the T817T as well.
If anyone has any ideas how to do this, please respond here.
Hi,
I realllyyyy need some advice... I bought an unlocked AT&T Samsung S5 from ebay as a spare phone. Currently is on android 5.1.1. Is there anyway this can be updated to a newer version? I've read several posts on how to do this except they are for different builds. I tried doing on and flashing with Odin but it just said Failed.
The build I have is G900AUCU4CO15 I cant seem to find anything online about how to update it. Is there no new version available for this build? Should I return this one and get a different S5 or an S6?
Thanks
I did similar to you : bought an unlocked s5 off ebay which turned out to be an AT&T branded one when it arrived. I used the Odin method to get up to MM, without any problems.
However, if you still have the option I would try to return it and get a non AT&T one as they are locked down and you can't do much with them (pretty much no custom ROMs, and no chance of Nougat or further ROM development).
tooplanx said:
I did similar to you : bought an unlocked s5 off ebay which turned out to be an AT&T branded one when it arrived. I used the Odin method to get up to MM, without any problems.
However, if you still have the option I would try to return it and get a non AT&T one as they are locked down and you can't do much with them (pretty much no custom ROMs, and no chance of Nougat or further ROM development).
Click to expand...
Click to collapse
I have an ATT s5 phone. I have been fully updated to newest android. I just did this today.
https://forum.xda-developers.com/att-galaxy-s5/general/guide-merry-christmas-heres-t3516196
Rooted and it worked! took a couple of extra restarts and a roll back to standard OS. However I am now running Talking monkeys rom https://forum.xda-developers.com/att-galaxy-s5/development/5-0-oc7-tms5-1-0-4-29-15-t3095987 and Loving it!
I have the AT&T Note 8 variant. I have installed the latest updates for the device. As I understand it, that makes rooting more difficult. It's been a while since I installed any ROM. I believe I must still root before I can install a custom ROM. What are the steps I need to take with that being the case?
Are there really no custom ROMs for the N950U? I looked through the ROMs section, and every single one of them seemed to be for the other variants.
Thanks for all pointers.
More difficult? There is no current root method if you've taken the update.
Flash ROM's? Do you know how to unlock the bootloader? I know of about 50 people that would pay good money to learn how to do that.
Start reading this thread. It will get you caught up on the status of root for the Snapdragon variant as well as all of the pitfalls.
Thanks. Will do.