Related
I've searched high and low for a root for my new galaxy note 3. I've seen somethings say the las vegas one or whatever but it couldn't be done on 4.4.2 kitkat. I've seen something about kingo. Which is the best method to root and unlock my boot loader so that i can flash roms.
Samsung galaxy note 3
Android version 4.4.2 kitkat
model- SM-n900a
Thank you in advance for your help! :good::laugh:
No rooting yet and there hasn't been unlocked bootloaders on the AT&T Note 3 yet.
Sent from my SAMSUNG-SM-N900A using Tapatalk
really???? bummer
A root method for 4.4.2 will be found eventually, so try to tough it out until its found. Not having root sucks, but it will hopefully come soon. An unlocked bootloader will most likely never happen unless someone holds the CEO of AT&T hostage (any volunteers?), so no custom kernels or AOSP for us unless someone gets Loki working.
Face_Plant said:
A root method for 4.4.2 will be found eventually, so try to tough it out until its found. Not having root sucks, but it will hopefully come soon. An unlocked bootloader will most likely never happen unless someone holds the CEO of AT&T hostage (any volunteers?), so no custom kernels or AOSP for us unless someone gets Loki working.
Click to expand...
Click to collapse
I'm glad your that positive that a root method for 4.4.2 will be found, however (not to be a negative nelly) KK has some security features that Google has added, that would make it even harder to achieve root. That, with the added AT&T "updated" locked bootloader, would make it almost impossible to obtain root. Then, adding salt to the wound, the new S5 has just been released, so every DEV that's worth their salt would want to hop on the new tech bandwagon and tackle something new.
I personally don't care about root. I never rooted my Note 3 until the OTA update, which kept getting stuck at 27%. I followed the instructions to obtain root, installed the OTA update, but FORGOT TO UNROOT my phone!!! That stupid SU app is in the way, and I can't uninstall it! When it comes time for me to upgrade my Note3 to a Note4, anyone can simply look in my app draw and see SU app. Even ISIS wont work because it thinks my phone is rooted. I want to simply root my phone, delete that SU app, and un-root. It's that simple. If I can do this using ADB, i'll try it in a heartbeat.
awe that sucks..hopefully someone comes up with some thing soon. Thanks for your replies. When they do come up with a root method would we still be able to flash roms being that our bootloader is locked?
dunn816 said:
I've searched high and low for a root for my new galaxy note 3. I've seen somethings say the las vegas one or whatever but it couldn't be done on 4.4.2 kitkat. I've seen something about kingo. Which is the best method to root and unlock my boot loader so that i can flash roms.
Samsung galaxy note 3
Android version 4.4.2 kitkat
model- SM-n900a
Thank you in advance for your help! :good::laugh:
Click to expand...
Click to collapse
At this time there is no way to root KitKat, period, either with De La Vega, or Kingo. In addition, the bootloaders are totally locked down. There currently is a petition here, to see if we can get AT&T to unlock them
---------- Post added at 10:41 AM ---------- Previous post was at 10:40 AM ----------
dunn816 said:
awe that sucks..hopefully someone comes up with some thing soon. Thanks for your replies. When they do come up with a root method would we still be able to flash roms being that our bootloader is locked?
Click to expand...
Click to collapse
Search through the forum, there is a way to flash custom ROMS, just not in the typical way
lawalty said:
I'm glad your that positive that a root method for 4.4.2 will be found, however (not to be a negative nelly) KK has some security features that Google has added, that would make it even harder to achieve root. That, with the added AT&T "updated" locked bootloader, would make it almost impossible to obtain root. Then, adding salt to the wound, the new S5 has just been released, so every DEV that's worth their salt would want to hop on the new tech bandwagon and tackle something new.
Click to expand...
Click to collapse
It still doesn't hurt to look up. The S5 is locked down tight just like the Note 3 so I don't see why devs would dump the Note 3 just to work on another locked device. The Note 3 is still relatively new and pretty popular so I doubt it's going to be given up on just yet.
Hey everyone!
First off, I apologize if I am posting this in the wrong area, as this is my first post here.
About two months ago, I used TowelRoot on my phone and achieved root status. Afterwards, I installed Xposed Framework and started loading modules. When AT&T pushed out an OTA update which updated the kernel, making rooting impossible once again, I did lose my root status. However, Xposed Framework and all of my modules remained installed and still function.
The interesting part is, after a reboot, I noticed that my boot splash screen says "Samsung Galaxy S5 Active", and "Custom" with the unlocked padlock at the bottom. Also, under device status, it says "custom" instead of "official".
I haven't attempted to flash a custom recovery on this phone, but what I'd really like to know is -- is my device's bootloader unlocked now, can I flash a recovery on it, and is there any ROM like a Cyanogenmod base that will be compatible with this phone? I haven't had any luck with researching it because everyone with the AT&T variant of this phone has a locked bootloader, so there hasn't been much opportunity to play with it.
I'd appreciate any help I can get on the matter. I'd like to see what this thing is capable of!
dont mess with itttt leave it until someone replies we need to extract your firmware, hold onto it if you not messing around, im not experinced enough but someone will pm you im sure
MGArcher007 said:
Hey everyone!
First off, I apologize if I am posting this in the wrong area, as this is my first post here.
About two months ago, I used TowelRoot on my phone and achieved root status. Afterwards, I installed Xposed Framework and started loading modules. When AT&T pushed out an OTA update which updated the kernel, making rooting impossible once again, I did lose my root status. However, Xposed Framework and all of my modules remained installed and still function.
The interesting part is, after a reboot, I noticed that my boot splash screen says "Samsung Galaxy S5 Active", and "Custom" with the unlocked padlock at the bottom. Also, under device status, it says "custom" instead of "official".
I haven't attempted to flash a custom recovery on this phone, but what I'd really like to know is -- is my device's bootloader unlocked now, can I flash a recovery on it, and is there any ROM like a Cyanogenmod base that will be compatible with this phone? I haven't had any luck with researching it because everyone with the AT&T variant of this phone has a locked bootloader, so there hasn't been much opportunity to play with it.
I'd appreciate any help I can get on the matter. I'd like to see what this thing is capable of!
Click to expand...
Click to collapse
MGArcher007 said:
Hey everyone!
First off, I apologize if I am posting this in the wrong area, as this is my first post here.
About two months ago, I used TowelRoot on my phone and achieved root status. Afterwards, I installed Xposed Framework and started loading modules. When AT&T pushed out an OTA update which updated the kernel, making rooting impossible once again, I did lose my root status. However, Xposed Framework and all of my modules remained installed and still function.
The interesting part is, after a reboot, I noticed that my boot splash screen says "Samsung Galaxy S5 Active", and "Custom" with the unlocked padlock at the bottom. Also, under device status, it says "custom" instead of "official".
I haven't attempted to flash a custom recovery on this phone, but what I'd really like to know is -- is my device's bootloader unlocked now, can I flash a recovery on it, and is there any ROM like a Cyanogenmod base that will be compatible with this phone? I haven't had any luck with researching it because everyone with the AT&T variant of this phone has a locked bootloader, so there hasn't been much opportunity to play with it.
I'd appreciate any help I can get on the matter. I'd like to see what this thing is capable of!
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?p=54642044
Sent from my SAMSUNG-SM-G900A using XDA Premium HD app
Apparently there are many different circumstances under which the splash screen says custom, which have nothing to do with the bootloader being locked or unlocked. I seem to recall it showing up for people when they just switched to ART runtime, and in some cases it didn't even go back when they switched back to Dalvik. Many of the methods for making this not appear just involve cosmetically hiding it, not actually cleaning up whatever it is that is being detected.
What I wouldn't give to have this bootloader unlocked
Sent from my SAMSUNG-SM-G900A using XDA Free mobile app
If there is a dev that wants a s5 to experiment with to get the bootloader unlocked I'll be happy to donate my s5 if I can get it back after finding an exploit . But the dev needs to come with unanimous recommendation by the devs. Let me know I can still use my s3.
Sent from my SAMSUNG-SM-T537A using XDA Free mobile app
Aw man, I was really hoping that the bootloader just somehow magically unlocked itself. Wishful thinking, I suppose. I love my S5 Active, I just wish I had a little more freedom with customizing it in ways like I could my S3.
I wonder if this is a result of Knox being disabled during the root... Either way, I hope I'll still receive OTA updates for things like 4.4.4 if they ever decide to release it, and eventually Android L.
For now, I can't complain -- surprisingly enough, even without root, my Xposed Framework still functions very well and I can still make backend and UI changes in GravityBox.
Regardless, thanks for all the replies, guys! I probably won't mess with trying to fix it unless they come out with an OTA update that I can't get as a result of this.
MGArcher007 said:
Aw man, I was really hoping that the bootloader just somehow magically unlocked itself. Wishful thinking, I suppose. I love my S5 Active, I just wish I had a little more freedom with customizing it in ways like I could my S3.
I wonder if this is a result of Knox being disabled during the root... Either way, I hope I'll still receive OTA updates for things like 4.4.4 if they ever decide to release it, and eventually Android L.
For now, I can't complain -- surprisingly enough, even without root, my Xposed Framework still functions very well and I can still make backend and UI changes in GravityBox.
Regardless, thanks for all the replies, guys! I probably won't mess with trying to fix it unless they come out with an OTA update that I can't get as a result of this.
Click to expand...
Click to collapse
Sadly. ...We may never see the bootloader unlocked without a factory method...
It's encryption prevents us from even being able to open it into a usable state...
We need either an encryption key....or a new bootloader entirely...
Not happening any time soon....g
I've got a S6 Active that when I received it was on Lollipop. I was able to flash MM (using thread here on XDA) to it before it was officially released from the carrier. Then I was able to flash back to stock Lollipop and then received the MM 6.0.1 update from the carrier. I wanted to flash back to Lollipop for testing purposes but was unable. I think it's because the bootloader is locked?
I've read a bunch of threads saying that the S6 active has nott been rooted? Has a locked bootloader? Can't run custom roms?
Can someone please give me the scoop on this. I'd like to go back to lollipop for testing but I don't think its possible. Is that the case? Thanks.
Roveer
roveer said:
I've got a S6 Active that when I received it was on Lollipop. I was able to flash MM (using thread here on XDA) to it before it was officially released from the carrier. Then I was able to flash back to stock Lollipop and then received the MM 6.0.1 update from the carrier. I wanted to flash back to Lollipop for testing purposes but was unable. I think it's because the bootloader is locked?
I've read a bunch of threads saying that the S6 active has nott been rooted? Has a locked bootloader? Can't run custom roms?
Can someone please give me the scoop on this. I'd like to go back to lollipop for testing but I don't think its possible. Is that the case? Thanks.
Roveer
Click to expand...
Click to collapse
hi
yes it's not possible to downgrade your rom or your bootloader because of the locked bootloader that prevents any try to modify the device...
is this typical of most phones? I've read of others frutrations about the S6 active still having a locked bootloader. Did I just pick a bad platform? Is S6 the same way? How about S7 series? Thanks.
roveer said:
is this typical of most phones? I've read of others frutrations about the S6 active still having a locked bootloader. Did I just pick a bad platform? Is S6 the same way? How about S7 series? Thanks.
Click to expand...
Click to collapse
Locked bootloaders are often the case for phones provided by carriers. While a phone purchased directly from the manufacturer is usually able to have its bootloader unlocked, carrier phones are locked by the carrier themselves, preventing any tampering by the end user. A custom ROM is any modified version of Android not developed by the company that made your phone. Think of it like a third party system. To get these custom ROMs onto your phone you must "flash" (simply, install) the ROM from your computer to your phone. However, a locked bootloader prevents this. While in some cases there are ways to get around carrier locked bootloaders, it is generally futile. If you purchased the S6 Active in hopes of tinkering around with custom ROMs, I'm afraid you have picked the wrong phone. The S6 Active, as of currently, is permanently locked to Samsung's and AT&T's "stock ROM"
EDIT: as for going back to Lollipop, the reason this is generally not possible is due to the fact that the Marshmallow update also updated critical parts related to the bootloader. It is impossible to roll back these changes once they have been made as they are strictly one way.
Thanks for the explanation. I didn't buy the phone for the express reason for changing android versions but rather to use as my daily driver. We are a BES 12 (Blackberry Enterprise Server) shop and I have found a bug that causes the VPN portion of the software to drop after an hour or so. Simply hitting the home button (waking the phone up re-establishes the vpn and mail flow continues). I'm working with BB to determine what's going on. I've disabled all power saving and doze settings yet still the problem. They are going to activate some other phones on my system to see if they see the problem. My reason for wanting to go back to lollipop is that I don't believe I saw this problem when I was on that OS so I was hoping to go back to confirm that behavior. I like the "active" phones for their ruggedness but don't have an unlimited budget to be buying handsets.
Roveer
roveer said:
Thanks for the explanation. I didn't buy the phone for the express reason for changing android versions but rather to use as my daily driver. We are a BES 12 (Blackberry Enterprise Server) shop and I have found a bug that causes the VPN portion of the software to drop after an hour or so. Simply hitting the home button (waking the phone up re-establishes the vpn and mail flow continues). I'm working with BB to determine what's going on. I've disabled all power saving and doze settings yet still the problem. They are going to activate some other phones on my system to see if they see the problem. My reason for wanting to go back to lollipop is that I don't believe I saw this problem when I was on that OS so I was hoping to go back to confirm that behavior. I like the "active" phones for their ruggedness but don't have an unlimited budget to be buying handsets.
Roveer
Click to expand...
Click to collapse
If the software you are referring to is something provided by blackberry, perhaps they need to patch their software for compatibility with Android Marshmallow. While not all software is broken by a major Android update, there are definitely some that are. Of course enterprise level software is entirely foreign to me (I'm only 17), so getting a second opinion on this issue would definitely be a good idea.
OK, I understand locked bootloader preventing from flashing any custom roms etc. Even preventing previous official android. Here's another question: Is there a way to flash current android version? I'm on G890AUCS4CPF3 which is an AT&T build. What is the carrier's method to reflash current OS when there has been some corruption to the version that is on the phone. Not just wipe, but reload entire android, re-create file system etc... That's what I want to try next. Blackberry has activated a Samsung S6 on my server and it (so far) is not exhibiting the same problem as my S6 Active. This leads me to believe that it my be a problem with my hardware. I want to do a reload at this point. Any ideas how I can do that? Odin flash? Is there a repository for the G890AUCS4CPF3 ROM?
Thanks,
Roveer
roveer said:
OK, I understand locked bootloader preventing from flashing any custom roms etc. Even preventing previous official android. Here's another question: Is there a way to flash current android version? I'm on G890AUCS4CPF3 which is an AT&T build. What is the carrier's method to reflash current OS when there has been some corruption to the version that is on the phone. Not just wipe, but reload entire android, re-create file system etc... That's what I want to try next. Blackberry has activated a Samsung S6 on my server and it (so far) is not exhibiting the same problem as my S6 Active. This leads me to believe that it my be a problem with my hardware. I want to do a reload at this point. Any ideas how I can do that? Odin flash? Is there a repository for the G890AUCS4CPF3 ROM?
Thanks,
Roveer
Click to expand...
Click to collapse
Carriers can tell if your Firmware is theirs or not because official Firmware is digitally signed by Samsung and AT&T.
As for using Odin, that would be your most viable option. However, I am not aware of any Odin images for the Marshmallow update on the S6A. As far as I know, Odin cannot get around the restriction of having a newer Bootloader, so you cannot flash down.
One thing you can try is to wipe cache partition. If that fails, factory reset from within the bootloader. Just make sure you've backed your data up.
EDIT: Take note that there is a difference in Firmware between the S6 vs the S6A.
EDIT 2: In your other thread you stated you can't flash back to lollipop due to a locked bootloader. This is actually due to, as stated before, the newest bootloader tha to the latest Android Marshmallow update.
FevenKitsune said:
Carriers can tell if your Firmware is theirs or not because official Firmware is digitally signed by Samsung and AT&T.
As for using Odin, that would be your most viable option. However, I am not aware of any Odin images for the Marshmallow update on the S6A. As far as I know, Odin cannot get around the restriction of having a newer Bootloader, so you cannot flash down.
One thing you can try is to wipe cache partition. If that fails, factory reset from within the bootloader. Just make sure you've backed your data up.
EDIT: Take note that there is a difference in Firmware between the S6 vs the S6A.
EDIT 2: In your other thread you stated you can't flash back to lollipop due to a locked bootloader. This is actually due to, as stated before, the newest bootloader tha to the latest Android Marshmallow update.
Click to expand...
Click to collapse
So I wiped the cache partition and factory reset within the bootloader and tried my app again. It continued to fail. I even found the MM image in the S6 Active MM thread and sideloaded it. It was only 400+ megs though. Still the app doesn't work so I'm starting to doubt that my problems are related to my particular S6 but its always a possibility. I'm trying to get Blackberry to dig up their own S6A and test on their own. They've been testing with a S6 for the past 2 days (on my BES server) and haven't seen the same problems, so it's either my device or a problem with the S6A (which as has been pointed out does use a different firmware version than the S6), but until I can get another S6 Active device to test I won't know.
Roveer
This phone i have i bought recently.I would like help rooting this phone so i can remove stuff i don't need.
The only problem is the OEM unlock is missing from the Dev Options.I have looked for many ways to unlock this option and i am scratching my head.
It's been a while since i tried to Rooting...Would like some kinda video and guide.
Not worried about the Warranty BS i own the phone.
FYI Edit: the android version is 12 and recently updated as of yesterday.
Current update (G781U1UEU7EVE4)
the short, painful truth... you can't unlock, root or do anything with that phone other than flash stock firmware.
3mel said:
the short, painful truth... you can't unlock, root or do anything with that phone other than flash stock firmware.
Click to expand...
Click to collapse
There was a solution for Android 10 oneui 2.5. I was assured by a samsung rep that a second s20 fe 5g phone I ordered would have android 10 and oneUI 2.5. I wanted a twin for the phone I'm using that is comfortably rooted. When the phone arrived it had android 12 and oneUI 4.0. I can wait for a solution.I am hoping one will eventually arrive. Has anything become available recently or should I dash my hopes of ever rooting my second?
Is it possible to downgrade from 13 to 12? I think the upgrade messed up my camera. Or maybe a way to reflash the camera firmware?
If the bootloader wasn't updated you can roll it back.
How can I find out if it was updated? I have a US unlocked phone. Its updated from 11 to 12 and now to 13.
See this thread, different models but the same information applies.
blackhawk said:
See this thread, different models but the same information applies.
Click to expand...
Click to collapse
This is the build I'm on now:
RedCrane3 said:
This is the build I'm on now:
Click to expand...
Click to collapse
Hello good morning
Of course, it can be downgraded, as long as the binary number is the same... example in the image.
The bootloader version is 9 so for you to roll back that build number's 5th digit from the end needs to be the same or higher.
With stock Snapdragon's locked bootloader it's easy to get locked into an OTA upgrade you don't want if it updates the bootloader too. I have two N10+'s, one running on 9, the other 10 (can't be rolled back to 9). That's what they were loaded when bought new. They will likely remain on those versions for their service lives as they are running well. I prefer Pie though.
I could be running Android 11 or 12 but I blew them off mostly because of the scoped storage bs.
The first thing I disable is OTA updates, once bitten twice shy. Had a S4+ that got screwed up by a OTA update that couldn't be rolled back... it sucks.
Thank you guys for helping me with all of this information. I guess I have a decision to make.
I can try to rollback to Android 12 in the hopes that will fix my camera issue, or I can sit tight and hope that a future update will resolve it.
Either way, I'm beginning to regret allowing OTA updates.
I really love the hardware of this phone, especially the screen, but its not important to me to have the latest Android (security updates are important though).
I originnaly submitted the problem to Samsung through their members app and the tech who looked at it said he *thought* it was a hardware issue, but come on, what are the chances that the one camera stops working right after the update to 13 and OneUI 5? I take very good care of my phone and never drop it (certainly didn't recently, after the update), there's not a scratch on it.
I suppose its possible, but it would be an incredible coincidence...
The tech suggested I visit a service center (which for me would be a Best Buy, yikes) or call their support 800 number, but what are they going to be able to do that the tech couldn't?
I just don't know if I can trust their initial assessment - no one knows everything, and plenty of people give up on a problem and pass it off the first trouble they run into. Maybe the tech just wasn't interested in digging deeper? A quote from their answer:
"Chi request is getting timed out. Read wide camera sensor seems to be not responding to requests [...]"
I guess my question is: can a downgrade to 12 even fix the issue?
Should I wait for another update?
Or should i just heave Samsung over the side and try to install a custom ROM?
Thanks again for all your help.
You're welcome.
If the bootloader is locked you can't install a custom rom. This is the case with most newer Snapdragon's including the N10+.
The Samsung Experience center at the best buys can run advanced diagnostics so they might be able to find the issue. They can also roll it back or try a reflash of 13.
blackhawk said:
You're welcome.
If the bootloader is locked you can't install a custom rom. This is the case with most newer Snapdragon's including the N10+.
The Samsung Experience center at the best buys can run advanced diagnostics so they might be able to find the issue. They can also roll it back or try a reflash of 13.
Click to expand...
Click to collapse
Ah, ok, but do you mean that the version I have (unlocked US snapdragon) is not able to unlock the bootloader, or just that I'd need to do that first? I do have experience with custom ROMS; my old moto X4 has seen many different ROMS in it's lifetime, so I do feel comfortable unlocking the bootloader and flashing other ROMS.
RedCrane3 said:
Ah, ok, but do you mean that the version I have (unlocked US snapdragon) is not able to unlock the bootloader, or just that I'd need to do that first? I do have experience with custom ROMS; my old moto X4 has seen many different ROMS in it's lifetime, so I do feel comfortable unlocking the bootloader and flashing other ROMS.
Click to expand...
Click to collapse
That refers to the carrier not bootloader I think. Not sure about your specific model's bootloader.