Related
The problem is the phone is showing Custom when the phone is turned on. I was on MF3, had rooted via the SD card method. The custom appeared at that point. I did a factory reset and the custom went away and lost root but the superuser app was still showing in the app draw (factory reset did not delete this). I was planning on reloading the MF3 firmware via odin but lent the phone to my daughter while I replaced the screen in her note2. Well of course she got the upgrade message to 4.3 from AT&T, did it and now the unlocked custom is back. Not sure why as it was showing as official, the trip counter was still 0 (never installed a ROM on it) BUT the superuser app was there.
Now on 4.3 I've rooted/unrooted via Kingo, during the unroot it removes superuser but the custom won't go away. I installed Triangle Away while rooted and it still shows 0 on the flash counter. Is there something in this Knox security (not sure how to check this) causing the custom?
Just want to get it back to any stock AT&T firmware so I can sell it. TIA for any help
there are only certain roms you can flash while being on mf3. If you did the mk2 update there is no recovery out yet. Using vroot and kingo are unsafe methods of rooting so puts your device at risk.
rzracer2 said:
The problem is the phone is showing Custom when the phone is turned on. I was on MF3, had rooted via the SD card method. The custom appeared at that point. I did a factory reset and the custom went away and lost root but the superuser app was still showing in the app draw (factory reset did not delete this). I was planning on reloading the MF3 firmware via odin but lent the phone to my daughter while I replaced the screen in her note2. Well of course she got the upgrade message to 4.3 from AT&T, did it and now the unlocked custom is back. Not sure why as it was showing as official, the trip counter was still 0 (never installed a ROM on it) BUT the superuser app was there.
Now on 4.3 I've rooted/unrooted via Kingo, during the unroot it removes superuser but the custom won't go away. I installed Triangle Away while rooted and it still shows 0 on the flash counter. Is there something in this Knox security (not sure how to check this) causing the custom?
Just want to get it back to any stock AT&T firmware so I can sell it. TIA for any help
Click to expand...
Click to collapse
Install the Xposed framework from xda. Then, install the Wanam module and look for the Setting under "Security Hacks" that reads "Fake system status" and check the box and reboot.
The issue won't truly be resolved until you flash an official ROM, but the Custom screen will be gone at boot.
rzracer2 said:
The problem is the phone is showing Custom when the phone is turned on. I was on MF3, had rooted via the SD card method. The custom appeared at that point. I did a factory reset and the custom went away and lost root but the superuser app was still showing in the app draw (factory reset did not delete this). I was planning on reloading the MF3 firmware via odin but lent the phone to my daughter while I replaced the screen in her note2. Well of course she got the upgrade message to 4.3 from AT&T, did it and now the unlocked custom is back. Not sure why as it was showing as official, the trip counter was still 0 (never installed a ROM on it) BUT the superuser app was there.
Now on 4.3 I've rooted/unrooted via Kingo, during the unroot it removes superuser but the custom won't go away. I installed Triangle Away while rooted and it still shows 0 on the flash counter. Is there something in this Knox security (not sure how to check this) causing the custom?
Just want to get it back to any stock AT&T firmware so I can sell it. TIA for any help
Click to expand...
Click to collapse
unroot via kingo, then factory rest...worked for me on 4.3
Do you plan on a warranty exchange?
I love seeing the custom on boot, it lets me know and other everyday normal people know my phone is slightly modified.
ROOTED ATT MK2 using Tapatalk
Not sure what I'm going to do with the phone yet, probably sell it but not totally sure. Wondering with it now showing Custom on the boot screen and in the OS will it still receive OTA updates? Hoping the AT&T 4.3 or 4.4 image will be available in the future and that might help.
rzracer2 said:
Not sure what I'm going to do with the phone yet, probably sell it but not totally sure. Wondering with it now showing Custom on the boot screen and in the OS will it still receive OTA updates? Hoping the AT&T 4.3 or 4.4 image will be available in the future and that might help.
Click to expand...
Click to collapse
I was rooted custom and received my OTA no problem. Yes
ROOTED ATT MK2 using Tapatalk
Hi,
I bought an S4 which was previously rooted. Last owner unrooted it and used triangle away to make sure all was as stock looking as possible.
Last week I did a factory reset on the phone as I was having issues with it. After the reset it shows all the stock apps and standard Rogers bloatware. BUT it now has a couple of Bell Bloatware apps as well!!!
I need to send the phone in for repair as I am getting "intermittent SIM card not detected, phone is restarting error". Should I be worried that Samsung will detect that the phone was at one time rooted?
What should I do?
Thanks
rezadue said:
Hi,
I bought an S4 which was previously rooted. Last owner unrooted it and used triangle away to make sure all was as stock looking as possible.
Last week I did a factory reset on the phone as I was having issues with it. After the reset it shows all the stock apps and standard Rogers bloatware. BUT it now has a couple of Bell Bloatware apps as well!!!
I need to send the phone in for repair as I am getting "intermittent SIM card not detected, phone is restarting error". Should I be worried that Samsung will detect that the phone was at one time rooted?
What should I do?
Thanks
Click to expand...
Click to collapse
When the last owner unrooted the phone, they likely used one of the odin files from here which are all Bell based for I337M (Canadian S4). There is a thread in here where this happened to another user and they returned the phone to stock Rogers instead of Bell, you will need to search for that thread. The bigger concern is Knox is probably tripped on the phone, when it boots up there will be some tiny text it the top left corner, yellow and red I believe, there is a thread about that here too.... If Knox is tripped (pretty sure it is) then all you can do is try to get it repaired by Samsung, I wouold be interested to find out if they do it or not.....
Thanks for the reply.
I shut the phone down and then turned it back on, paying close attention to evenrything. There is no small text in any corner. What is odd id that the phone goes through its boot sequence, gets to the lockscreen, and then goes through the boot sequence again a second time.
And for clarification, I have all the Rogers bloat, but I have three Bell bloat apps too!
I will do a search again to see if I can find the threads you have mentioned.
Gage_Hero said:
When the last owner unrooted the phone, they likely used one of the odin files from here which are all Bell based for I337M (Canadian S4). There is a thread in here where this happened to another user and they returned the phone to stock Rogers instead of Bell, you will need to search for that thread. The bigger concern is Knox is probably tripped on the phone, when it boots up there will be some tiny text it the top left corner, yellow and red I believe, there is a thread about that here too.... If Knox is tripped (pretty sure it is) then all you can do is try to get it repaired by Samsung, I wouold be interested to find out if they do it or not.....
Click to expand...
Click to collapse
rezadue said:
Thanks for the reply.
I shut the phone down and then turned it back on, paying close attention to evenrything. There is no small text in any corner. What is odd id that the phone goes through its boot sequence, gets to the lockscreen, and then goes through the boot sequence again a second time.
And for clarification, I have all the Rogers bloat, but I have three Bell bloat apps too!
I will do a search again to see if I can find the threads you have mentioned.
Click to expand...
Click to collapse
You have to go into download mode to see the text.
Sent from Black<3's I337 running Foxhound ROM
Put the phone in download mode and no small text.
Now that the phone is not rooted, can I put it in download mode, attach it to a PC and flash a stock Rogers 4.3 ROM via ODIN? Do I need root for this?
rezadue said:
Oh, and one other question. Now that the phone is not rooted, can I put it in recovery mode, attach it to a PC and flash a stock Rogers 4.3 ROM via ODIN? Do I need root for this?
Click to expand...
Click to collapse
Not to ODIN it no. Root not required.
Found the other thread, you have spoken of. It seems like that guy got bloatware from Bell INSTEAD of Rogers. I have blaotware from Rogers(ok
) AND Bell(Not ok).
http://forum.xda-developers.com/showthread.php?t=2422497
Almost same issue here on my N900W8. My phone is working fine and rooted, except I got the Rogers AND Bell apps too before rooting and flashing CWM (only way I knew of at the time to force boot following seandroid enforcing error). I data wiped, downloaded and flashed the labeled "Rogers" stock ROM from SamMobile, and first time I ever saw bloatware from two carriers on any phone.
I disabled the Bell apps thinking that was all, but instead of 4G, I get H+. LTE connects fine outdoors, but H+ seems slightly slower than the 4G I'm used to. Which makes me wonder if LTE speeds are impacted too, hope not. Anyway, it's a bother because I am rarely in an LTE zone.
Tomorrow, I will try unrooting with SuperSU (is this even important if I'm wiping & flashing?), data wiping with CWM, re-flashing same file from SamMobile and not flashing anything more, and trying emergency recovery with Kies. Anyone know if this will work or change anything in the end? Or is Kies 3 also affected by the Knox counter? CSC (OYA) is the same as the non-rooted up-to-date S4 in the house.
Thanks
OP, have you tried using someone else's SIM card? Just a thought.
Hello all,
I have a Samsung Galxy S5 with AT&T model SM-G900A. Any time the phone reboots, on the "Samsung Galaxy S5" boot screen, it says "Custom" and has an "Unlocked Padlock" logo as if the phone were rooted or something. A while back, I was trying to do a basic root to allow use of Titanium Backup using the Towelroot app, which failed because it said my phone was not supported. I'm not sure if this has caused it, or if, as I read elsewhere, it was caused by my once changing from Dalvik to ART. However, I have since switched back to Dalvik, I know its not rooted because SU and other such apps wont work, and I have even Factory Reset the device but I can not get rid of this. I would like to return my phone to its default state. How can I get rid of this "Custom" and Lock Logo? Your help is greatly appreciated! Thanks so much!
-Noomrise
It won't hurt anything as long as Knox isn't tripped but you can download the full stock retail ROM and flash it in Odin or Kies 3.
Update: Phone thinks its rooted?
Noomrise said:
Hello all,
I have a Samsung Galxy S5 with AT&T model SM-G900A. Any time the phone reboots, on the "Samsung Galaxy S5" boot screen, it says "Custom" and has an "Unlocked Padlock" logo as if the phone were rooted or something. A while back, I was trying to do a basic root to allow use of Titanium Backup using the Towelroot app, which failed because it said my phone was not supported. I'm not sure if this has caused it, or if, as I read elsewhere, it was caused by my once changing from Dalvik to ART. However, I have since switched back to Dalvik, I know its not rooted because SU and other such apps wont work, and I have even Factory Reset the device but I can not get rid of this. I would like to return my phone to its default state. How can I get rid of this "Custom" and Lock Logo? Your help is greatly appreciated! Thanks so much!
-Noomrise
Click to expand...
Click to collapse
Okay, so here is an update. After performing a factory reset in order to try and fix this issue, I was playing around and opened the "Softcard" app and received the message that it doesn't work on rooted phones. Since the Towelroot app did not work, I don't understand this. I have also been unable to get SuperUser to install binaries, saying the phone is not rooted. Don't know what this means or if it helps, but thought id give an update. Thanks again!
Would you be so kind as to provide me with a link to the retail ROM and instructions on flashing it through Kies 3? THANKS!
I'd have to do a search. .. or you could. ?
Rapunzl said:
I'd have to do a search. .. or you could.
Click to expand...
Click to collapse
Thanks, I found the file (I hope) and downloaded odin, and it is currently flashing. I will let you know if it a) removes the custom lock and b) fixes the softcard app thinking the phone is rooted. Thanks for your help!
It Worked!!!!!
Rapunzl said:
It won't hurt anything as long as Knox isn't tripped but you can download the full stock retail ROM and flash it in Odin or Kies 3.
Click to expand...
Click to collapse
I would like to report that flashing the stock ROM has fixed both the Custom Lock boot screen as well as SoftCard thinking my phone was rooted. Thank you Rapunzl for your help, you are awesome!
Hey everyone!
I've got an interesting predicament here. A little back story: a while back I installed TowelRoot, and then Xposed Framework. Everything was kosher until I got an OTA update (I believe the NG3 update) and it killed the root. No problem, I'm fine without root. But now that Lollipop has come out, I want to update but can't. My buddy applied the same root, but did not do Xposed. The difference between our phones after that OTA update: mine says "Custom" with an unlocked padlock at the Samsung boot screen; his does not.
I read in another thread that someone took their phone to Best Buy and the guys at the Samsung booth were able to fix the problem because they can pull updates and apply them via USB. So we went there yesterday and they had no problem getting Lollipop on my buddy's S5 Active. Mine, however, would not take the update. The Samsung S.M.A.R.T. tool they use on the PC was saying that "my device is running an unauthorized operating system", even though I have never flashed a custom ROM.
When I go into download mode, the Knox flag does not appear to be tripped. I've also performed a clean factory reset with a data wipe and that still didn't allow me to update. Whenever I try to update, it downloads the entire 4.4.4 update (which needs to be done first, before the 5.0 update) and it starts to install, failing at 25%, without hesitation, every single time.
I've attached a couple of screenshots that I hope will help. Any ideas will be greatly appreciated.
MGArcher007 said:
Hey everyone!
I've got an interesting predicament here. A little back story: a while back I installed TowelRoot, and then Xposed Framework. Everything was kosher until I got an OTA update (I believe the NG3 update) and it killed the root. No problem, I'm fine without root. But now that Lollipop has come out, I want to update but can't. My buddy applied the same root, but did not do Xposed. The difference between our phones after that OTA update: mine says "Custom" with an unlocked padlock at the Samsung boot screen; his does not.
I read in another thread that someone took their phone to Best Buy and the guys at the Samsung booth were able to fix the problem because they can pull updates and apply them via USB. So we went there yesterday and they had no problem getting Lollipop on my buddy's S5 Active. Mine, however, would not take the update. The Samsung S.M.A.R.T. tool they use on the PC was saying that "my device is running an unauthorized operating system", even though I have never flashed a custom ROM.
When I go into download mode, the Knox flag does not appear to be tripped. I've also performed a clean factory reset with a data wipe and that still didn't allow me to update. Whenever I try to update, it downloads the entire 4.4.4 update (which needs to be done first, before the 5.0 update) and it starts to install, failing at 25%, without hesitation, every single time.
I've attached a couple of screenshots that I hope will help. Any ideas will be greatly appreciated.
Click to expand...
Click to collapse
Have you resolved this issue, if so, would you mind sharing how you did it. I've been combing the net for a few days trying to discover what is going on and your issue appears to be exactly what I am experiencing. I've read about flashing back to my stock firmware using Odin but I cannot get into download mode, when I try and get there, the phone only says "recovery reboot" in blue small font on the top of the screen and reboots.
Thanks
Ladies and gents, I apologize for abandoning this thread. I forgot exactly how I got to get the phone to update, but if I recall correctly, it had to do with me putting the phone in download mode, downloading the original firmware and using ODIN to flash it. Afterward, the "unlocked" padlock symbol disappeared and the phone was able to get the OTA update from AT&T.
I have since moved from an LG G4 to a V20 and that is what I am currently playing with. I also have a Samsung Galaxy S6 Edge (which T-Mobile replaced my G4 with when the touch screen stopped responding). I was quite stoked to find out that there is a way to root it and (seemingly) unlock the bootloader, so I'll be toying with that this weekend to see what I can do. I'd love nothing more than to just wipe that Samsung-ified Android and install a vanilla Android or CM.
Good luck to anyone who is still trying to fix this issue. Again, my apologies. I'll dig through my archives and see if I can piece together what I did to get it going again. I still have the S5 Active. Best phone by far. It's a great backup phone for when the new stuff goes kaput.
I have tried everything I can possibly think of in a short period of time, and need an answer in a hurry. The phone (Verizon Samsung Galaxy Note 3 N-900V) was rooted back when kitkat was the main OS using geohot's towelroot (or possibly kingo root I can't remember which i used after I got the phone and upgraded from ICS). I have 2 of these exact same phones, used the exact same rooting method, and unrooted by uninstalling the superuser app, rebooted, and installed the OTA update to lolipop. My phone works fine, (the one I'm typing from) however, my other phone decided to take a dump. It's a software bug between the samsung firmware and the new lolipop OS. It was working for several months, then all the sudden it wouldn't recognize/register the APN. Now it doesn't see anything just about with the phone. Not even the IMEI from the phones serial number. The sim card has been replaced twice and has worked for a matter of a few hours, however, upon restarting the phone, it goes back to no service, and nothing is registered or recognized. I reflashed the phone with the stock 5.0 Lolipop using Odin several times to no avail. My phone (one I'm using now) once did this months ago, and I was able to access the service menu and reregister the SIM card and phone has worked fine since. With this other phone, I can't get into the service menu at all because nothing is registering. So, after reflashing 4 or 5 times, factory reseting from both the OS and from recovery booting, it still has the same issue. Here is my question. It used to be when I reflashed, the custom padlock would disappear. I'm getting a new phone tomorrow, and I need to get rid of the custom padlock before I return the old phone. I can use Odin, or whatever but it has to be something, I can do while it stays stock. The knox counter has not been tripped, and the flash counter is not tripped nor showing anything on the download mode. Everything lools, and feels stock, except that custom padlock. Is there a way to get rid of that custom padlock unrooted, by reflashing? I even used a pit file to repartition, but that didn't work either. Need help A.S.A.P.!
I would just hard brick the phone just before returning it...they will just throw it out at that point and your secret will be safe.
Hard Brick
xxperrin said:
I would just hard brick the phone just before returning it...they will just throw it out at that point and your secret will be safe.
Click to expand...
Click to collapse
You thinking maybe a NAND erase?
Hard Brick
I've thought about flashing the wrong rom too but dunno if that will work 100%. I either need to fix it, or make it 100% unrecoverable. Any advice?