Hey everyone. I decided I would unlock my bootloader and trip Knox about two days before towelroot came out. Yay.
I've since gotten the OPO, so I wasn't that concerned. I wanted to give the phone to my mom who lives in another state, so I Odin'ed back to what I believe is the most current OEM firmware available (NK2) because I want my mom to be able to get updates OTA and not have to worry about troubleshooting her phone as much as if it were a custom ROM, or a phone with root.
Unfortunately, checking for a system update says the system is modified (ROM is all stock though) and device status is custom. I also discovered while testing the phone (it had been sitting in a drawer for months) that the microphone isn't working very well. I tried different sims, calling different people on different networks, I'm sure it's hardware problem. Is there any way to re-enable the OTAs? I'd like to get this hardware problem warrantied. The knox tripping didn't destroy the mic, so please no judgement here. I'm also not comfortable in removing the glass to replace the mic. If the mic could be replaced without that step, I would simply do that.
Thank you.
rockingondrums said:
Hey everyone. I decided I would unlock my bootloader and trip Knox about two days before towelroot came out. Yay.
I've since gotten the OPO, so I wasn't that concerned. I wanted to give the phone to my mom who lives in another state, so I Odin'ed back to what I believe is the most current OEM firmware available (NK2) because I want my mom to be able to get updates OTA and not have to worry about troubleshooting her phone as much as if it were a custom ROM, or a phone with root.
Unfortunately, checking for a system update says the system is modified (ROM is all stock though) and device status is custom. I also discovered while testing the phone (it had been sitting in a drawer for months) that the microphone isn't working very well. I tried different sims, calling different people on different networks, I'm sure it's hardware problem. Is there any way to re-enable the OTAs? I'd like to get this hardware problem warrantied. The knox tripping didn't destroy the mic, so please no judgement here. I'm also not comfortable in removing the glass to replace the mic. If the mic could be replaced without that step, I would simply do that.
Thank you.
Click to expand...
Click to collapse
Hmm. Last time I Odined back to stock, using the tar file of the firmware version that came before NK2, my device was totally fine to receive OTA, despite Knox being tripped. Try removing root first, then Odin stock NK2, then factory reset.
Hm, so I now need to install SuperSU in order to use the un rooting function? I would've thought a full stock image file would've eliminated root...
EDIT - Simple Root checker says SuperSU is not installed BUT terminal app "does Rooted".
Installed SuperSU, but binary is not installed, so it doesn't run. WTH? What happened to the good old days of just flashing stock images and not worrying about it anymore?
SOLVED
I looked at the slightly outdated stock collection thread, flashed the NG4 stock image, then was able to take the OTA update to NK2. Went ahead and told T-Mobile the whole problem and they really only seemed to care if there was physical damage or water damage (which there is not).
Just leaving this here for future searches. How do I get this thread closed?
Related
Alright, so over the last few weeks my phone has developed touchscreen issues, with large parts of the screen now not registering touches. The phone is very close to unusable and I plan to have it exchanged on warranty. HOWEVER, I was rooted back on Froyo (I lost root access with the Gingerbread update) and now I'm stuck with Superuser as a system app (unremovable). I need root access to remove SU, but I haven't been able to find whether or not rooting via .zip flash is reversible or not. I need an answer on whether or not it is, and if so, how.
Also, I'm not simply flashing back to stock because I've heard rumors that the phone keeps track of how many flashes it recieves. How credible is this?
Thanks for any help!
Chairsofter1138 said:
Alright, so over the last few weeks my phone has developed touchscreen issues, with large parts of the screen now not registering touches. The phone is very close to unusable and I plan to have it exchanged on warranty. HOWEVER, I was rooted back on Froyo (I lost root access with the Gingerbread update) and now I'm stuck with Superuser as a system app (unremovable). I need root access to remove SU, but I haven't been able to find whether or not rooting via .zip flash is reversible or not. I need an answer on whether or not it is, and if so, how.
Also, I'm not simply flashing back to stock because I've heard rumors that the phone keeps track of how many flashes it recieves. How credible is this?
Thanks for any help!
Click to expand...
Click to collapse
it is reversable download root uninstaller from the market if you are worried about it. me personally i have returned about 4 rooted phones ony to have them fixed and updated when sent back.
dont worry about it, its not unlocked so no harm done
I was rooted with custom recovery on MDK. I decided to restore my Stock rooted backup so I could take OTA path to MJ7.
I’m currently on MI1 waiting to update to MJ7 and noticed the Samsung Custom boot logo. Device Status says “Custom”. I’m no longer rooted, no more custom recovery due to the ME7 and MI1 OTA updates. How should I proceed?
I’m worried about tripping the Knox fuse and I know there’s no going back. Does it matter? Will the MJ7 update overwrite this status? Or do I need to take care of it on MI1 before moving forward to MJ7?
EDIT: While on MI1, I used the ODIN files to go completely back to stock MI1. This returned the Device Status to "Official" and the boot logo returned to normal. This link is for the ODIN files with instructions: (http://forum.xda-developers.com/showthread.php?t=2301259).
Screenshots, for reference.
You could try the [root] triangle away app. I would read through the thread 1st....http://forum.xda-developers.com/showthread.php?t=1494114
The straightforward approach might be just to ODIN back to stock MI1 and go from there. Will that solve the problem?
(http://forum.xda-developers.com/showthread.php?t=2301259)
^^^ what he said. Odin and start fresh. Although it does seem like a shame to see a MDK device getting updated and locked down but hey it's not my device.
Normally reading the first two sentences of this post would have been the most disheartening thing to see in a S4 forum, luckily or unlucky today it comes in second only to garwyn just closing the dev thread about coming up with ideas for unlocking the bootloader, and it happening so shortly and randomly after my post here, which I consider the most significant public progress we've made in unlocking this bootloader, because its the only public progress I've seen since we were gifted with loki.
majeiks said:
The straightforward approach might be just to ODIN back to stock MI1 and go from there. Will that solve the problem?
(http://forum.xda-developers.com/showthread.php?t=2301259)
Click to expand...
Click to collapse
Confirmed. This did the trick. Device Status says "Official" and the boot logo returned to normal. Will update OP with solution.
I'm on mdk lokied. I rather wait someone will surely make a stock rooted 4.3 or use it as a base for their rom..give it a week and it will be worth it. We probably won't get kitkat here for a long time and especially if your locked down.
Sent from my SCH-I545 using Tapatalk 2
cell128 said:
I'm on mdk lokied. I rather wait someone will surely make a stock rooted 4.3 or use it as a base for their rom..give it a week and it will be worth it. We probably won't get kitkat here for a long time and especially if your locked down.
Sent from my SCH-I545 using Tapatalk 2
Click to expand...
Click to collapse
yes patience is the way to go give it a little time if nothing develops then you can always go to a locked down device I upgraded my wife's phone and trust me the improvements are things we already had like the wi fi notification thing and the e911 icon being removed. I flashed the radio for the 4.3 update which is the most important thing anyways so I'm gonna hang in a little longer and see what roms pop up..
MJ7
matt1733 said:
yes patience is the way to go give it a little time if nothing develops then you can always go to a locked down device I upgraded my wife's phone and trust me the improvements are things we already had like the wi fi notification thing and the e911 icon being removed. I flashed the radio for the 4.3 update which is the most important thing anyways so I'm gonna hang in a little longer and see what roms pop up..
Click to expand...
Click to collapse
I was running Hyperdrive 9.1 on Safestrap on my I545. One day there must've been a pocket dial because I pulled it out and it said there were too many password attempts and I needed the recovery password or there would be a factory reset and data would be wiped. So I Safestrapped into stock, (ME7), but I never liked ME7, so decided to go back to unrooted stock and upgrade to MJ7.
Bottom line, so far I love it. It runs significantly smoother, faster, and with less bugs than the other ROMs I've tried. I'm not a developer and I understand the passion some have for custom options, but at the end of the day, if stock updates make improvements and eliminate most of the bugs, then it's a whole lot easier. I'm liking MJ7 on my phone.
Runamok said:
I was running Hyperdrive 9.1 on Safestrap on my I545. One day there must've been a pocket dial because I pulled it out and it said there were too many password attempts and I needed the recovery password or there would be a factory reset and data would be wiped. So I Safestrapped into stock, (ME7), but I never liked ME7, so decided to go back to unrooted stock and upgrade to MJ7.
Bottom line, so far I love it. It runs significantly smoother, faster, and with less bugs than the other ROMs I've tried. I'm not a developer and I understand the passion some have for custom options, but at the end of the day, if stock updates make improvements and eliminate most of the bugs, then it's a whole lot easier. I'm liking MJ7 on my phone.
Click to expand...
Click to collapse
Are you getting the security warnings yet? A friend has stock MJ7 and has been getting security warnings. He asked me to take a look at it . after about 3 seconds of googleing I found the answer. Its a known bug in MJ7.
http://forums.androidcentral.com/ve...xy-s4-security-notice-after-update-4-3-a.html
Knox security warnings - No biggie
azraell33 said:
Are you getting the security warnings yet? A friend has stock MJ7 and has been getting security warnings. He asked me to take a look at it . after about 3 seconds of googleing I found the answer. Its a known bug in MJ7.
Thank you for pointing this out. I checked into it and I doubt it's a bug. I DID get the security warning the next morning after install, which coincided with the timing of your message. My reaction to it was to simply agree to getting the security updates. I have not had any problems since, and my phone is running fine. I tried multiple ROMs while I had Safestrap on my phone, and MJ7 is performing as well as any of them. The caveat is that I'm not able to make as many mods to phone features, but to be honest, a lot of the mods were superficial tweaks that I didn't really use that much on a regular basis.
I APPRECIATE what developers have done to spur Verizon and Samsung into fixing the problems with the earlier versions of the software. Obviously, I was unhappy enough to attempt altering the firmware and risk losing warranty service. Having said that, I've come to a place where the time and effort it takes to act as my own customer service agent isn't serving me well. When I started having problems with my custom ROM and realized there had been not one, but TWO Verizon updates in the space of 3-4 months, I made a choice to accept the good with the bad and go the route of accepting updates in one easy click, instead of expending the energy it takes to be my own R&D and customer service department. .
MJ7 is running fine. Energy efficiency seems very good. Stability appears solid. Response time and hangups appear to be all but eliminated. Those were the reasons I tried a custom ROM, energy efficiency, stability and performance. MJ7 seems to have addressed those reasonably well.
A big THANK YOU to developers who had an influence in nudging Verizon into action. Security will continue to be a looming issue, and hopefully it will not quash the creativity of brilliant independent thought.
Click to expand...
Click to collapse
I had ME7 and rooted that, MODded some stuff, tweaked settings, disabled/froze bloatware... and everything was fine. Stable, fast enough.
Then I allowed (because I couldn't stand the constant Update Nag!!!) the MI1 update and DeLaVega Rooted that and things have been unstable since. Seemingly random apps are crashing and occasionally causing rebooting, sometimes it needs the battery pulled. The most critical app, and the one that leads to reboots the most, is Google Maps Nav - the one app I need most.
I am thinking I would like to revert to factory stock ME7, then re-root it, and maybe TWRP (and I have Titanium). There's nothing in MJ7 I need or want and I don't trust MI1 (it was out what... three weeks?)
I would do this myself but I can seem to find a ME7 Image that WIPES and unroots the phone.
It would probably help if someone would explain a bit more how the pieces work. I gather there's a bootloader, a kernal, the ROM and user data. Rooting deals with the boot cycle, the kernal is the main OS, the ROM contains OS layer above the kernal along with system apps and such. Obviously, those three have to get along. So my question is, if I used DeLaVega to root MI1, Can I just flash a non-wipe ME7 ROM? It seesm to me that the MI1 root tool would not get along with the ME7 ROM -- is that right?
BTW, I'm not a ROMmer. I get how ODIN works but I've never flashed anything (via Odin) to my phone(s) other than that MI1 root image (and WHY/WHAT is that 1.3gb?!? The ME7 exploit was a few KB)
Thank you VERY MUCH in advance for explanations, links and so on.
-- Bear
lordbear said:
I had ME7 and rooted that, MODded some stuff, tweaked settings, disabled/froze bloatware... and everything was fine. Stable, fast enough.
Then I allowed (because I couldn't stand the constant Update Nag!!!) the MI1 update and DeLaVega Rooted that and things have been unstable since. Seemingly random apps are crashing and occasionally causing rebooting, sometimes it needs the battery pulled. The most critical app, and the one that leads to reboots the most, is Google Maps Nav - the one app I need most.
I am thinking I would like to revert to factory stock ME7, then re-root it, and maybe TWRP (and I have Titanium). There's nothing in MJ7 I need or want and I don't trust MI1 (it was out what... three weeks?)
I would do this myself but I can seem to find a ME7 Image that WIPES and unroots the phone.
It would probably help if someone would explain a bit more how the pieces work. I gather there's a bootloader, a kernal, the ROM and user data. Rooting deals with the boot cycle, the kernal is the main OS, the ROM contains OS layer above the kernal along with system apps and such. Obviously, those three have to get along. So my question is, if I used DeLaVega to root MI1, Can I just flash a non-wipe ME7 ROM? It seesm to me that the MI1 root tool would not get along with the ME7 ROM -- is that right?
BTW, I'm not a ROMmer. I get how ODIN works but I've never flashed anything (via Odin) to my phone(s) other than that MI1 root image (and WHY/WHAT is that 1.3gb?!? The ME7 exploit was a few KB)
Thank you VERY MUCH in advance for explanations, links and so on.
-- Bear
Click to expand...
Click to collapse
as for as i know there is no method to downgrade once you have taken an update, not even with ODIN. once you take an OTA or update it you are stuck with it, you cannot go backwords
th3bl3d said:
as for as i know there is no method to downgrade once you have taken an update, not even with ODIN. once you take an OTA or update it you are stuck with it, you cannot go backwords
Click to expand...
Click to collapse
+1.
Now the only thing I can say is backup using TI and do a FDR (factory data reset).
This should clean up your issue. You will not lose root.
After that restore your apps one at a time and by all means make sure you *DO NOT* take the MJ7 update.
You think you are stuck now????
I have MI1 and it's rock solid with no crashes.
I have all the bloat frozen or disabled.
My phone never reboots or hangs.
tech_head said:
+1.
Now the only thing I can say is backup using TI and do a FDR (factory data reset).
This should clean up your issue. You will not lose root.
After that restore your apps one at a time and by all means make sure you *DO NOT* take the MJ7 update.
You think you are stuck now????
I have MI1 and it's rock solid with no crashes.
I have all the bloat frozen or disabled.
My phone never reboots or hangs.
Click to expand...
Click to collapse
I did FDR twice. Turned off restore of Google stuff during setup wizard, turned of AutoUpdate in Store so I could control what apps loaded, too.
After first FDR it appears I still had root. I think that MAYBE something went funky because I was rooted on ME7, let MI1 come via OTA, then DeLaVega'ed that. I just don't know.
Now, I have a different phone, I am going to need to UNroot and FDR the phone I will send back. Haven't found info on UNroot for Mi1/DeLaVega yet. I've seen ROMs for ME7-nowipe and MJ7-wipe.
Thanks
Bear
lordbear said:
I did FDR twice. Turned off restore of Google stuff during setup wizard, turned of AutoUpdate in Store so I could control what apps loaded, too.
After first FDR it appears I still had root. I think that MAYBE something went funky because I was rooted on ME7, let MI1 come via OTA, then DeLaVega'ed that. I just don't know.
Now, I have a different phone, I am going to need to UNroot and FDR the phone I will send back. Haven't found info on UNroot for Mi1/DeLaVega yet. I've seen ROMs for ME7-nowipe and MJ7-wipe.
Thanks
Bear
Click to expand...
Click to collapse
Look at this thread. -> http://forum.xda-developers.com/showthread.php?t=2301259
Hello. I have done quite a bit of searching, just can't find a similar enough post to tag on some questions. Sorry if this has been asked...but I did look over a month of posts, and google searching.
I have a Note 3 from September, rooted in October...not sure how I got it done...but I jumped the gun and unrooted it with SU thinking I would be able to OTA to 4.4.2. Nope!
So, I am stuck on 4.3.
My big question is how can I get to 4.4.2 with OUT starting over on the phone.
I guess this is a backup question. I have some settings turned on that indicate that a back up is going somewhere, but I can't confirm, and I don't know what all is backed up.
Pictures are backed up, but I would hate to lose them. They are on SD card anyway...so I realize I could take the card out, but something I read suggested I might lose even the micro-simm card contents. Not sure how that would be possible.
But what about things like Quick Notes, and S Note, and Contacts, and all of my apps that I have installed, and settings for those apps.
When I rooted back in October, it worked with out disrupting anything.
How can I get that to happen now WITH an upgrade to 4.4.2 AND getting it rerooted?
If I can't upgrade with out wiping it clean, I am probably going to stay put. So, then what is the best way to root to get "Wifi Tether Router" back working...as it is the only thing I need the phone rooted for.
Finally, what is the difference between NC5 and NC5D. I saw a recent post of somebody else asking it...but none of the replies gave an answer.
Thanks for any feedback.
I don't know if this will help, but you can give it a try. First, you might want to consider that you are where most of us are trying to get back to ( i.e. 4.3 with no KNOX !!! ). Ok, I would go to Samsung Firmware, and download the latest version of 4.4.2 NC5 to your PC. I would backup that copy of 4.3 on your device to your sdcard then if have an ext sdcard copy it there, or copy that backup to your pc. Most of your Pics and data should be in that backup, that you can copy back later with a file explorer like Root Explorer. Now do a factory wipe. Then take the NC5 zip you got from sammie and extract it to a file on your desktop this will change it to a .tar file. Find a copy of Odin v1.85 don't use the 3.09 version on the Samsung website if possible. Cool, reboot your device into download mode, start odin, plug in your device to your PC. Now, load that extracted file on your desktop into PDA odin, and click start. It will take minute to read Md5 then start installing. You will lose root and recovery !!! Your new bootloader will have KNOX 0x0. So, you will have to start over with the root process, but isn't that half the FUN !!! Chainfires v1.94 supersu will root NC5. As for the difference between NC5 and NC5D, It is my understanding they are the same. The D stands for a version of NC5 that was used by Samsung employees ( i.e. programmers and developers ) in the development of NC5. :fingers-crossed::fingers-crossed:
Lokerd, I see you have read my response. Great!!! I would add the you can root 4.4.2 NC5 several ways. As I said above Chainfires v1.94 SuperSu, and One click autoroot, and Towelroot for 4.4.2. All should root your device without tripping KNOX. However, as soon as you flash a new custom recovery like TWRP or Philz CWM ( my favorite ) it will trip KNOX. If you are out of warranty no biggie, besides you need a custom recovery if you want to get back to your 4.3 backup. ( By the way remember you need the same recovery (i.e. TWRP or CWM ) that you made the 4.3 backup with, now on NC5 just a newer version. This will make it easier to recover the 4.3 backup later. They say the most popular recoveries will recover each others backups, but that is rarely the case.
jimzweb1 said:
First, you might want to consider that you are where most of us are trying to get back to ( i.e. 4.3 with no KNOX !!! ).
Click to expand...
Click to collapse
Thanks for taking the time to reply! And to reply with such a nice well though out steps.
So...I should NOT being trying to upgrade? I can do that...just reroot and be done with this. I really don't want to risk having to lose info I have put on the phone, etc. A few new features is not going to be worth it. But, reading about improved 4g and wifi performance. Wifi calling is not important to me. But it would be nice to have the camera on the lock screen...but I bet I could find something that would do that the rooted phone I had.
So, let me ask this. If I do not care about KNOX, is the process you outlined above any easier?
Thanks!
Drew
lokerd said:
Thanks for taking the time to reply! And to reply with such a nice well though out steps.
So...I should NOT being trying to upgrade? I can do that...just reroot and be done with this. I really don't want to risk having to lose info I have put on the phone, etc. A few new features is not going to be worth it. But, reading about improved 4g and wifi performance. Wifi calling is not important to me. But it would be nice to have the camera on the lock screen...but I bet I could find something that would do that the rooted phone I had.
So, let me ask this. If I do not care about KNOX, is the process you outlined above any easier?
Thanks!
Drew
Click to expand...
Click to collapse
Well, if you are out of warranty, and you don't care about KNOX go ahead and upgrade. But, consider this: One, so where clear the only reason for the 4.3 backup is to get to your pics and data at a later time. Here is a link about trying to go back http://forum.xda-developers.com/showthread.php?t=2630514 Once you install 4.4.2 NC5 ( this will include a new kernel, bootloader, baseband, and OS ) you CANNOT go to back to 4.3. If you try to install the 4.3 backup after you have upgraded to NC5 you will soft brick your phone. Then, there's KNOX what is KNOX, KNOX is security software written by the NSA for Samsung. Now I'm not saying its spyware, but Samsung is !!! You can go to Samsung's website and all the info about KNOX you need is there.
To answer your last question, no. You have to go through all the motions.
If it was me, knowing what I know now. I would stay at 4.3, install an engineering bootloader (read up on bootloaders they are not forgiving if you mess up ) then try to upgrade basebands. Here is a link for NAB engineering bootloader which should be 4.3, http://forum.xda-developers.com/showthread.php?t=2655674 Here is the link for a NC5 baseband, http://forum.xda-developers.com/showthread.php?t=2701837 I believe this will improve your 4G lte.
Last, what I'm running. I run Note 3 "Sprint" 4.4.2 NC5 ( no choice bought the device new with that OS, voided my warranty the second day I owned it ). Rooted with Philz CWM recovery ( hltespr v 6.12.9 ) KNOX disabled and removed. I definitely like 4.4.2 NC5 a lot better than 4.3 my daughters Note 3 had 4.3 before I upgraded to 4.4.2 and rooted it. Here is my XDA website http://forum.xda-developers.com/showthread.php?t=2770729 so if you do upgrade this is a good place to start.
Ok. Sorry for more noob questions.
Ok, the only thing I want to ensure is that I don't lose things like S Note, Action Memo, Contacts, Pictures, apps installed. I just don't want to redo everything. Basically, I just want to upgrade the operating system and have everything up and running like it was...just new OS. Is that possible? I understand what you are saying about not being able to use the back up. I guess I just don't understand if I can upgrade this phone with out having to start back over with everything.
I am not out of warranty (purchased October 2013), but I don't see that it would be a problem. I normally don't break or drop my phone...although I did drop it and picked up a nick a few weeks ago. It was unusual circumstances. Point is...I guess I will worry about warranty issues if that comes up. On the other hand, the home button is a getting a little finicky, so I avoid it...using swipe down, and a notification toggle to go to Home whenever possible.
I don't understand the difference between bootloader vs. flashing vs. upgrading basebands vs. rooting as opposed to those other things. it doesn't help that there are multiple ways to do each of the above.
I think I am in over myhead.
Can you help me figure out what I had done before...as it was working pretty good. I Rooted it to get root access, but not sure how I did it. It was easy, and it didn't erase anything. I think I simply used Odin. Attached is a screenshot of a folder of stuff that I might have used. Can you tell what root method I used?
I think I am just going to go back to what I had...and still with 4.3. I actually looked at my wife's identical phone that is on 4.4.2 and other than wifi calling, I don't see the camera on lock screen, so I don't really think I should be messing with stuff I can't wrap my mind around trying to get to 4.4.2.
lokerd said:
Ok. Sorry for more noob questions.
Ok, the only thing I want to ensure is that I don't lose things like S Note, Action Memo, Contacts, Pictures, apps installed. I just don't want to redo everything. Basically, I just want to upgrade the operating system and have everything up and running like it was...just new OS. Is that possible? I understand what you are saying about not being able to use the back up. I guess I just don't understand if I can upgrade this phone with out having to start back over with everything.
I am not out of warranty (purchased October 2013), but I don't see that it would be a problem. I normally don't break or drop my phone...although I did drop it and picked up a nick a few weeks ago. It was unusual circumstances. Point is...I guess I will worry about warranty issues if that comes up. On the other hand, the home button is a getting a little finicky, so I avoid it...using swipe down, and a notification toggle to go to Home whenever possible.
I don't understand the difference between bootloader vs. flashing vs. upgrading basebands vs. rooting as opposed to those other things. it doesn't help that there are multiple ways to do each of the above.
I think I am in over myhead.
Can you help me figure out what I had done before...as it was working pretty good. I Rooted it to get root access, but not sure how I did it. It was easy, and it didn't erase anything. I think I simply used Odin. Attached is a screenshot of a folder of stuff that I might have used. Can you tell what root method I used?
I think I am just going to go back to what I had...and still with 4.3. I actually looked at my wife's identical phone that is on 4.4.2 and other than wifi calling, I don't see the camera on lock screen, so I don't really think I should be messing with stuff I can't wrap my mind around trying to get to 4.4.2.
Click to expand...
Click to collapse
Cool, your version of 4.3 should be NAB and no KNOX. If this is the case then you should be able to root, and return back to stock, if you have say a hardware issue with your device and have to return it under warranty. So, according to your last post image on 10/24/2013 you used CF Autoroot, if you want to read up here is the link to that http://forum.xda-developers.com/showthread.php?t=2466423
Now to get to the latest version of CF Autoroot you need to go to ChainFires ( CF ) repository here is the link http://autoroot.chainfire.eu/ just find the model of your phone and click on File to download. Put that file on your desktop, now go to your android downloads copy and paste Odin v1.85 to your desktop. Click on Odin extract, and open it, now click on PDA a box will open, now select desktop and click on CF Auotroot. It should come up in Odin next to PDA. Now boot your device into download mode, then connect to your PC. In the upper left hand box will light up COMM: with some number in green, blue, or yellow doesn't matter just telling you that a connection was made. Now click start on the bottom of Odin, sit back and watch the magic!
When it says pass your done. Now reboot your phone if doesn't do it by itself go to your app drawer and see if SuperSu is there. To install the Recovery just follow the same steps just substitute the recovery .tar file in place of CF Autroot. I see you have ChainFires v1.65 SuperSu the latest version is v2.01 here is the link http://forum.xda-developers.com/showthread.php?t=1538053. If you use CF Autoroot it will probably install the latest version of SuperSu automatically.
I see on 10/25/2013 you downloaded CWM recovery for hltespr ( sprint ) here is the link for Philz CWM http://forum.xda-developers.com/showthread.php?t=2596001 the latest version for sprint is 6.12.9 I don't use his unified all in one recovery version, I use the sprint version, but the choice is yours. :fingers-crossed:
jimzweb1 said:
Cool, your version of 4.3 should be NAB and no KNOX.
Odin v1.85 to your desktop.
Click to expand...
Click to collapse
Thanks for the continued help. Just about ready to reroot the thing.
So, you mention using 1.85...is that only because that is what I have? The latest CF-Auto-Root came with 3.07 but I had already downloaded 3.09 a couple of days ago trying to figure stuff out. I also saw a warning about using the latest Odin...but I think it applied to trying to do the Kindle Fire, which I determined was 3.3 and not able to be rooted with out a special cable, which I have ordered.
Anyway, does it matter if I use the 3.07 that came with the latest version of CF-A-R? Should I use 3.09? Or def stick with 1.85.
EDIT #5: I end up using 1.85 and the original Root, then the new ROOT. So, does it matter that I used the Root from October vs the newest one or older Odin vs. newer? I have it up now, so it is just a matter of tryingt o figure this out.
BTW, I thought I had bricked my phone...went back and read YOUR instruction again, and got it restarted. The instructions on the main CF-A-R thread do not make it very clear.
Thanks a bundle!
Great !!! It doesn't matter which version of Odin you use, as long as it gets the job done. As for CF Autoroot, after your done rooting and boot the device back up. It my take awhile but you will automatically be asked update your apps, and SuperSu will update binarys at that time.
I'm looking for some help/advice. I did search and didn't find anything on this although I would think it would have been covered before so my apologies if I missed it and it's already been answered.
I'm currently running Stang5Litre 5.0 OC1 V2 which I installed with Flashfire and I'm having a lot of issues with Good For Enterprise and it's root check. I can get it to work with Xposed as long as I stay on an old version of Good, but I've had two accidental upgrades that triggered a compliance failure and it's a long process with my work to get a new pin to get it going again. Using the detach from market in Titanium doesn't stick. I'm also interested in using Android Pay and can't get that to work at all. So I'm now considering getting rid of root. There isn't that much I do anymore that truly requires a rooted phone other than I really like being able to get rid of all the bloat and being able to freeze and unfreeze in Titanimum.
So my question is what options do I have? Can i fully unroot a debloated ROM or would I need to flash a stock unrooted OC1 ROM? Also, is the fact that my Samsung boot screen shows as unlocked an issue? I know that simply removing SuperSU isn't enough. I don't want to do anything that is going to prevent me from changing my mind down the road and going back to a rooted ROM which I know means not installing anything after OC1.
Any help would be appreciated.
Thanks
After doing a little more research on Good, I think I have no choice but to flash a completely stock unrooted ROM. Apparently it checks too many things to simply remove Root. So what are my options for going back to stock and still keeping the ability to root down the road if I choose?
Thanks