For whatever reason, when I was tweaking with safestrap and all the variants of software you can use upon rooting, my device decided to designate itself as a custom set device. Now, whenever I boot it up, it has the Samsung text, but it also has the custom logo with the padlock.
I've heard that triangleaway can solve this problem, but is it working smoothly with i537?
Yes it works. I tried myself and it worked perfectly exactly the same as with the regular GS4. Just keep in mind that you have to run the triangle away application from stock rom.
Sent from my GT-I9295 using XDA Premium 4 mobile app
Related
Recently wanted to update to kitkat after i rooted my phone and got frustated with it so I unrooted it and noticed the custom padlock logo was still on. after further review I see it was left with the device status set to custom as per normal when you root your phone. i did some digging and heard a lot of people stating some times if you used a 64 gig sd card it can trigger the custom status, well i use one and have since it was rooted and sadly enough after rooting and unrooting both with the sd card in and out it stays locked at the custom status. i really want to update the phone to kitkat from 4.3 because rooting really doesnt do it for me anymore. but i can not for the life of my figure out how to get it to switch back to official. i know if you used xposed module you can fake it to official. but when i upgrade to kitkat i will lose root permission and this is where my problems arise.
1. If i go ahead and update using xposed to fake my offical status will knox be triggered?
2. When i upgrade and lose root will the device automatically switch to back to official after upgrading or will i be stuck with the custom status and not be able to get anymore updates?
3. Is there any proven method to actually switch back to official permanately and not fake it like with xposed?
cynicalsinner91 said:
Recently wanted to update to kitkat after i rooted my phone and got frustated with it so I unrooted it and noticed the custom padlock logo was still on. after further review I see it was left with the device status set to custom as per normal when you root your phone. i did some digging and heard a lot of people stating some times if you used a 64 gig sd card it can trigger the custom status, well i use one and have since it was rooted and sadly enough after rooting and unrooting both with the sd card in and out it stays locked at the custom status. i really want to update the phone to kitkat from 4.3 because rooting really doesnt do it for me anymore. but i can not for the life of my figure out how to get it to switch back to official. i know if you used xposed module you can fake it to official. but when i upgrade to kitkat i will lose root permission and this is where my problems arise.
1. If i go ahead and update using xposed to fake my offical status will knox be triggered?
2. When i upgrade and lose root will the device automatically switch to back to official after upgrading or will i be stuck with the custom status and not be able to get anymore updates?
3. Is there any proven method to actually switch back to official permanately and not fake it like with xposed?
Click to expand...
Click to collapse
Use triangle away.
you will need root.
graydiggy said:
Use triangle away.
you will need root.
Click to expand...
Click to collapse
Can you give me a bit more detail then rhat? I downloaded it and I am currently rooted
cynicalsinner91 said:
Can you give me a bit more detail then rhat? I downloaded it and I am currently rooted
Click to expand...
Click to collapse
i had that problem i had to do a factory reset to get it to go away
I used Kingo to root. Decided to return to stock. After several manual reboots FINALLY removed "Custom" unlock and FINALLY RETURNED TO "Official".
Sent from my SAMSUNG-SM-N900A using xda app-developers app
jerrycoffman45 said:
i had that problem i had to do a factory reset to get it to go away
Click to expand...
Click to collapse
Sadly I have many times and it still persist. This is exactly what has happened since I got my phone a few months back. Bought it from at&t > rooted it > uprooted it because j couldn't figure out safe strap or how to install toms > rerooted it and tried again > successfully that time > got bored and wanted return to stock and upgrade > custom status issue now
There isn't much else to explain. You install triangle away, open the app and click reset flash counter.
Sent from my SM-N9005A using XDA Premium 4 mobile app
graydiggy said:
There isn't much else to explain. You install triangle away, open the app and click reset flash counter.
Sent from my SM-N9005A using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Oh wasn't sure if that was it or not my count is still set to 0 so I was thinking there was something else to it
Nope. It resets the flash counter and should reset the custom splash screen and custom status in settings.
I have never had issues with it.
Sent from my SM-N9005A using XDA Premium 4 mobile app
graydiggy said:
Nope. It resets the flash counter and should reset the custom splash screen and custom status in settings.
I have never had issues with it.
Sent from my SM-N9005A using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Custom is gone away from the boot logo and in download it reads as official however under settings it still says custom. If I were to just go ahead with the update even though under settings it says custom would it fail and trip knox? Or would everything get reset to official stock?
It will not trip knox.
If you have never done the "revert to MJ5" thread it should be fine.
Sent from my SM-N9005A using XDA Premium 4 mobile app
---------- Post added at 08:10 PM ---------- Previous post was at 08:10 PM ----------
Everything would go back to official
Sent from my SM-N9005A using XDA Premium 4 mobile app
Did you delete system apps while you were rooted (maybe via TitaniumBackup)? I'm in the same boat: TriangleAway made the padlock go away but the "Custom" status is still in device settings. I think it's because the system partition is no longer stock because I deleted some AT&T bloat. I have NB4 and can't update to KitKat (probably because it detects this custom status) and I can't downgrade to MI9 because bootloaders for NB4 and MI9 are not compatible. Looks like I'm stuck until I can use Odin with official KitKat.
I have 5.0 lollipop rooted on galaxy s5 at&t, how can install custom recovery like safestrap on it?
As far as I am aware it isn't doable at the moment.
Unable to at the moment. I tried installing TWRP, big mistake as it brought a screen saying there was software installed not approved by att and to shut the phone off and take in to a store. Just had to reflash the rooted lollipop and it went away.
Sent from my SAMSUNG-SM-G900A using XDA Premium 4 mobile app
Same problem
I have tried so many things also. I'm rooted and 5.0 at&t. It has to be possible to do. It has to be possible. If we could downgrade and install and upgrade. I been scratching my head about this for weeks. Needs to be solved. Haha.
Hello everyone. I did the root on my Galaxy S6 edge, and everything's been working great. The only thing I really use it for right now is so that I can run my app radio unchained reloaded app. Otherwise I haven't changed anything. Recently I've been getting carrier updates coming in that I have not been able to accept. They continue to fail. Is there a way I can update my phone yet still keep root? Or is there something else going on?
Chemdawg said:
Hello everyone. I did the root on my Galaxy S6 edge, and everything's been working great. The only thing I really use it for right now is so that I can run my app radio unchained reloaded app. Otherwise I haven't changed anything. Recently I've been getting carrier updates coming in that I have not been able to accept. They continue to fail. Is there a way I can update my phone yet still keep root? Or is there something else going on?
Click to expand...
Click to collapse
You can Odin back to stock (oc3), take update, then root using latest ping pong root. Or, flash a custom oe2 rom using flashfire, then use Odin to update firmware to OE2, such as is explained here: http://forum.xda-developers.com/showthread.php?p=61198002. Or use smart switch to update, which will remove root.
This question was asked a few days ago:
http://forum.xda-developers.com/showthread.php?p=61365924
Sent from my SM-G925V
I have a note 3 with at&t that's never been rooted but I would like to. Can sometimes point me in the right direction to get started?
Sent from my SAMSUNG-SM-N900A using XDA-Developers mobile app
Anyone can point us to the right direction for rooting?
Sent from my Nexus 10 using Tapatalk
zubero said:
Anyone can point us to the right direction for rooting?
Sent from my Nexus 10 using Tapatalk
Click to expand...
Click to collapse
+1 for OC2, I mean all, I, am, seeing is Downgrade options to 4.4 KitKat then towel root then Safestrap then flash slotted Updated Lollipop Rom? All, I want is to remove bloat and use exposed, is there a root for OC2? Without downgrading thanks
Here's the video for downgrading and rooting. Then after that you can use any of the builds available. I'm using Alliance v12. Works like a charm,I almost gave up on my phone and was about to buy a new one. After downgrading to NC2,rooted and the pushing in Alliance 12 it's back. Thank you community.
https://youtu.be/QL6V7Y8vNms
Sent from my Nexus 10 using Tapatalk
zubero said:
Here's the video for downgrading and rooting. Then after that you can use any of the builds available. I'm using Alliance v12. Works like a charm,I almost gave up on my phone and was about to buy a new one. After downgrading to NC2,rooted and the pushing in Alliance 12 it's back. Thank you community.
https://youtu.be/QL6V7Y8vNms
Sent from my Nexus 10 using Tapatalk
Click to expand...
Click to collapse
So you downgraded to NC2 which I'm assuming is 4.4.2 becuase Im on NJ5, downgraded to NC2 or Jellybean I think and rooted with towel root and installed safestrap via the instructions, but when I try to reboot into Safestrap after installing and it installs, I grant it Superuser, and click Reboot to Recovery and nothing happens, any ideas? Becuase I need Safestrap, so I can flash Alliance, or Backup or anything else, but there are SO MANY conflicting OP's, regaurding Safestrap "it abandoned", "it only works on 4.2.2", "there's a work around for Safestrap on 4.4.4, by flashing Kitcat Kernal" "or Safestrap will work on on OC1 also with correct kernel"
All I want is to be on the "LATEST FIRMWARE FOR THIS PHONE, THAT WILL ALLOW ME TO EFFECTIVELY USE SAFESTRAP, TO BACK UP, FLASH, AND RUN ALLIANCE ETC..."
IF that means being someone a beer, I'm cool with that, been around here for awhile and had many Samsung phone Notes One, Two, S3, S4, but never had to deal with this bootloader crap, just so frustrated at this point[emoji726]
Sent from my SAMSUNG-SM-N900A
Did you install busybox before installing safestrap?
Sent from my DROID Turbo using XDA-Developers mobile app
Yeah I'm pretty sure I did I mean I have Busy box installed of course, and Safestrap, and I'm not sure in what order, however if Busy box was causing the issue, then Safestrap would not install at all, right? But yes now that I remember, when I got this phone it was already updated to OC1 (at that time the latest build) after try to sift through all the different out dated tutorials, I finally just did what I mentioned above, but Safestrap "Installs fine", "Allows me to grant SU", then "allows me to (click)" reboot to recovery" then FAIL.... nothing happens, on NJ5, I know Safestrap ended development at some point, and don't you also have to flash a certain kernel in order for SS to work on KK? So Confused
Sent from my SAMSUNG-SM-N900A
You need to install Busybox, then open busybox and tell it to install it into the system
Then open safestrap and do likewise.
I did this on nc2 no idea how it'll work on an older version.
Sent from my DROID Turbo using XDA-Developers mobile app
mrkhigh said:
You need to install Busybox, then open busybox and tell it to install it into the system
Then open safestrap and do likewise.
I did this on nc2 no idea how it'll work on an older version.
Sent from my DROID Turbo using XDA-Developers mobile app
Click to expand...
Click to collapse
so mrkhigh, thank you by the way first! off, to your response, so as far as you know "Safestrap" did not require any additional steps, to work on 4.3, like an updated kernel, which I know makes no sense to me eithier, other than the permission changes that occured at the true root level on NJ5 Update, and SafeStrap itself not being a true recovery, in the word of true TWRP, per this pain in my @$$ bootloader, which I have already made knowen in this community, AND others, is simply a loophole, to the "right to modify" ruling by the FTC some years back, if you will to the carriers, at&fee included among others
Sent from my SAMSUNG-SM-N900A
After hunting for files to download for Odin and failing, and trying two one-click solutions that told me the files are not available, I am having trouble finding step-by-step help for rooting my Galaxy Note 3 N900AUCSEOC3 for my Android 5.0 install (received as a normal upgrade from AT&T). I gather that the OC3 refers to a particular release (of OEM Android?). I haven't quite digested the implications of attempting to install a custom rom, so I first want to simply root the device, preferably, but not necessarily, without making KNOX angry (although perhaps I can't install a custom rom without first rooting, anyway?). Is there a tested way to do this for my Galaxy Note 3 -OC3, or can someone confirm that it can't be done at this time?
GregJ7 said:
After hunting for files to download for Odin and failing, and trying two one-click solutions that told me the files are not available, I am having trouble finding step-by-step help for rooting my Galaxy Note 3 N900AUCSEOC3 for my Android 5.0 install (received as a normal upgrade from AT&T). I gather that the OC3 refers to a particular release (of OEM Android?). I haven't quite digested the implications of attempting to install a custom rom, so I first want to simply root the device, preferably, but not necessarily, without making KNOX angry (although perhaps I can't install a custom rom without first rooting, anyway?). Is there a tested way to do this for my Galaxy Note 3 -OC3, or can someone confirm that it can't be done at this time?
Click to expand...
Click to collapse
Same problem over here. I used to mess with this stuff on the note 1 but been out of the game too long.
The AT&T Note 3 has a locked boot loader so you can't flash a custom ROM using TWRP. You can only flash custom ROMs that can be installed via SafeStrap.
I too am having the same problem, I can not find the files to root my AT&T Note 3, Bootloader: N900AUCSEOC3. Also what does this mean: I see two hlte codes, one is hlteatt under Device tab, (I am using Device Control from the Play Store) and the other is hlteuc on the Product tab. With the hlteuc code, does this mean that I can root this with a generic SM-N900 Root or not. I can post a screenshot if necessary. EDIT: I have tried all sorts of "Auto Root" apps such as KingoRoot TowelRoot KingRoot Universal Androot, etc. to no Avail.
Do you have a copy of the OC3 file?
Sent from my SM-N900A using XDA Premium HD app
RETIEF said:
Do you have a copy of the OC3 file?
Sent from my SM-N900A using XDA Premium HD app
Click to expand...
Click to collapse
No, I do not, unfortunately.
I was on OC2, so I am not sure at all about 3 but this worked for me.
First flash NC2 files in odin
https://forum.xda-developers.com/note-3-att/general/n900aucucnc2-odin-files-t2838117
Then root that using this post but NOT that Safestrap
https://forum.xda-developers.com/showpost.php?p=65467618&postcount=6
Use this one
https://forum.xda-developers.com/devdb/project/?id=2054#downloads
I have flashed Aurora rom and Alliance v12 to stock slot without any problems. Alliance is very buggy. NFC and System FC like crazy. Be SURE to wipe before installing rom. First boot takes forever.