AT&T version of this thread: http://forum.xda-developers.com/showthread.php?p=47413669
Started with N900AUCUBMI9, rooted via RDLV (N900AUCUBMI9_OneClickBin)
accepted OTA update (i know) to N900AUCUBMJ5, lost root
Wanted root back, attempted RDLV again, got SECURE CHECK FAIL : cache, stuck in "Firmware upgrade encountered an issue. Please select recovery mode in Kies and try again"
Found this thread: http://forum.xda-developers.com/showthread.php?p=47411605
Flashed PIT ONLY, successfully booted up into MJ5, unrooted. Should have left it alone there. KNOX flag 0x0
Wanted root back, thought I could downgrade BL, AP/PDA, Phone, CPC to MI9 as suggested in above thread.
BL fails with SW REV CHECK FAIL : [sbl1]Fused 2 > Binary 1. AP/PDA, fails with SECURE CHECK FAIL : system. Phone successfully flashed to MI9. CPC fails with SECURE CHECK FAIL : cache
Stuck in "Firmware upgrade encountered an issue. Please select recovery mode in Kies and try again"
Flashed PIT again, phone tries to boot but "Process system isn't responding" after AT&T globe boot animation, then reboots
Attempted RDLV again, get SW REV CHECK FAIL : [sbl1]Fused 2 > Binary 1, presumably because the MI9 BL can't be flashed over the MJ5 BL.
I'm stuck folks. Any suggestions welcome. Am I just going to have to wait for a stock MJ5 package/files similar to the MI9 files in the thread above?
For those reading who were dummies like me and accepted the OTA update, lost their root, tried to re-root with RDLV: flash the PIT file ONLY from the above link and you should be back into MJ5, un-rooted.
Help please?
Well lets see here. I was rooted (Kingo) <Updated ver.
I saw the update.
Un-rooted with the SuperSU app.
Did the update
Re-rooted with Kingo.
Re-did all xposed/winam stuff.
Rebooted
Phone is on new firmware with root and I'm loving it.
The End.
LuckyColdJohnson said:
Well lets see here. I was rooted (Kingo) <Updated ver.
I saw the update.
Un-rooted with the SuperSU app.
Did the update
Re-rooted with Kingo.
Re-did all xposed/winam stuff.
Rebooted
Phone is on new firmware with root and I'm loving it.
The End.
Click to expand...
Click to collapse
yes, that's the way i should have done it (SU persist, un-root, OTA, SU root) but I didn't and now here i am.
I followed the info to flash PIT only and my phone rebooted. Now fc's allot of stuff. Can't get past it. Build number mi9, baseband mj5. Do you think someone will make an mj5 odin? Or any advice would be greatly appreciated.
Same here
Same situation here ;_; can you post just the Pit? the zip is taking forever for the fact that I just need an XML file.
ditto
+1 I was updated and rooted and decided to jack around with a data toggle in notification (/data/data/com.android.providers.settings/databases/settings.db) and here i am
So I flashed the .pit
which let me reboot.
However now I'm in a horrible limbo state where pen imput crashes in an infanite loop making anything on the phone painful to do.
I think it's because my PDA and CSC are MI9 but my phone updated to MJ5.
I tried recovery mode wipe and "reset Phone" in settings and the issues persist.
This lovely mismatch has also rendered my ability to install firmware via Kies imposible. Nulling my plan to just roll back to stock.
Anybody have an odin one click for MJ5? I'd rather be stock than inoperable.
I'm afraid to try the method listed above for Knox flag reasons. If rolling back to MI9 is unreliable and might throw flags.
Hope someone else gets further than I have soon.
LuckyColdJohnson said:
Well lets see here. I was rooted (Kingo) <Updated ver.
I saw the update.
Un-rooted with the SuperSU app.
Did the update
Re-rooted with Kingo.
Re-did all xposed/winam stuff.
Rebooted
Phone is on new firmware with root and I'm loving it.
The End.
Click to expand...
Click to collapse
Where is this kingo?
Sent from the phone with the best specs on the market, "NoTe III"
mnorris0678 said:
+1 I was updated and rooted and decided to jack around with a data toggle in notification (/data/data/com.android.providers.settings/databases/settings.db) and here i am
Click to expand...
Click to collapse
I soft bricked my phone probably 5 or 6 times before getting it to work!
Sent from my SAMSUNG-SM-N900A using Tapatalk
tyiphius said:
I soft bricked my phone probably 5 or 6 times before getting it to work!
Sent from my SAMSUNG-SM-N900A using Tapatalk
Click to expand...
Click to collapse
Would you do us a solid, and elaborate on how you fixed it?
bloodyRevolver said:
I'm afraid to try the method listed above for Knox flag reasons. If rolling back to MI9 is unreliable and might throw flags.
Hope someone else gets further than I have soon.
Click to expand...
Click to collapse
FYI, nothing that I have domes so far has tripped KONX. Still at 0x0
bloodyRevolver said:
Would you do us a solid, and elaborate on how you fixed it?
Click to expand...
Click to collapse
+1
Sweet. Your OP lead me to believe that you tripped it somewhere. Honestly I'm beginning to care less and less about it. I honestly think that with a full ODIN of the current OTA WE'd be back in the clear. The inability to roll back after The thing updated without my permission is frustrating to say the least. Coming from iOS I'm also a bit surprised by the lack of OEM firmware existing in the wild.
settings.db
Might anybody have a stock unmodified /data/data/com.android.providers.settings/databases/settings.db file that i can try loading with adb?
Resolved issue with at&t.
Couldn't handle waiting for SM-N900A stock firmware so I took my phone to AT&T retail store (I didn't have warranty with them). They referred me to At&t Device support center and told me that I have a manufacture warranty with samsung for 1 year and since i didn't have any water damage or such, just a boot loop, i can just exchange it for a "like-new" product and might ship between 6 business days.
nikeflight19 said:
Couldn't handle waiting for SM-N900A stock firmware so I took my phone to AT&T retail store (I didn't have warranty with them). They referred me to At&t Device support center and told me that I have a manufacture warranty with samsung for 1 year and since i didn't have any water damage or such, just a boot loop, i can just exchange it for a "like-new" product and might ship between 6 business days.
Click to expand...
Click to collapse
I was offered the same deal. Preferred to hold out hope that we'd get an MJ5 firmware ripped and running before that.
Where can I find this pit file?
WHERE CAN i FIND THE PIT FILE
hunterdg said:
AT&T version of this thread: http://forum.xda-developers.com/showthread.php?p=47413669
Started with N900AUCUBMI9, rooted via RDLV (N900AUCUBMI9_OneClickBin)
accepted OTA update (i know) to N900AUCUBMJ5, lost root
Wanted root back, attempted RDLV again, got SECURE CHECK FAIL : cache, stuck in "Firmware upgrade encountered an issue. Please select recovery mode in Kies and try again"
Found this thread: http://forum.xda-developers.com/showthread.php?p=47411605
Flashed PIT ONLY, successfully booted up into MJ5, unrooted. Should have left it alone there. KNOX flag 0x0
Wanted root back, thought I could downgrade BL, AP/PDA, Phone, CPC to MI9 as suggested in above thread.
BL fails with SW REV CHECK FAIL : [sbl1]Fused 2 > Binary 1. AP/PDA, fails with SECURE CHECK FAIL : system. Phone successfully flashed to MI9. CPC fails with SECURE CHECK FAIL : cache
Stuck in "Firmware upgrade encountered an issue. Please select recovery mode in Kies and try again"
Flashed PIT again, phone tries to boot but "Process system isn't responding" after AT&T globe boot animation, then reboots
Attempted RDLV again, get SW REV CHECK FAIL : [sbl1]Fused 2 > Binary 1, presumably because the MI9 BL can't be flashed over the MJ5 BL.
I'm stuck folks. Any suggestions welcome. Am I just going to have to wait for a stock MJ5 package/files similar to the MI9 files in the thread above?
For those reading who were dummies like me and accepted the OTA update, lost their root, tried to re-root with RDLV: flash the PIT file ONLY from the above link and you should be back into MJ5, un-rooted.
Help please?
Click to expand...
Click to collapse
nabooki said:
WHERE CAN i FIND THE PIT FILE
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2502049
First page of the second link you posted. It's in the zip with all the other MI9 files. If you look further down the thread he also posted another version of the PIT. Read read read read.
Hello all.. Been gone for a bit. Catching up now and hoping for a solution but if anyone has figured this out, please let me know how or provide a link! (Mj5 Odin stock recovery)
So, the situation is a bit weird. About a week and a half ago, some update came out for my AT&T Note 3, and after declining, later it forced me to install it. After installing, it seemed to have disabled root, but I still had the custom icon show up when it booted, and root functions were disabled. It was as if root was not uninstalled, but disabled. I've tried re-rooting the normal way, but that gives a fail when I try to use the OneClickBin application. I haven't tried skipping that and installing root for fear of bricking the phone on some incompatibility. If someone else has this problem or has solved it, please let me know what you did or give any advice you can. The ideal result would be for my phone to end up back in the stock firmware, updated and ready to root as if nothing was wrong. I'd also appreciate it if anyone can give me info on the update that broke it, so I can check for a root method which is compatible with it. Thanks in advance.
Ralkero said:
So, the situation is a bit weird. About a week and a half ago, some update came out for my AT&T Note 3, and after declining, later it forced me to install it. After installing, it seemed to have disabled root, but I still had the custom icon show up when it booted, and root functions were disabled. It was as if root was not uninstalled, but disabled. I've tried re-rooting the normal way, but that gives a fail when I try to use the OneClickBin application. I haven't tried skipping that and installing root for fear of bricking the phone on some incompatibility. If someone else has this problem or has solved it, please let me know what you did or give any advice you can. The ideal result would be for my phone to end up back in the stock firmware, updated and ready to root as if nothing was wrong. I'd also appreciate it if anyone can give me info on the update that broke it, so I can check for a root method which is compatible with it. Thanks in advance.
Click to expand...
Click to collapse
You got the update to MJ5, try using Kingo Root.
I'm noticing that Kingo Root's version page does not list the SM-N900A model. We're sure it's supported, right?
Yup! I used it on mj5 update
Solarenemy68 said:
You got the update to MJ5, try using Kingo Root.
Click to expand...
Click to collapse
Thanks, that worked.
Just picked up this phone yesterday. It was a Galaxy S4 Active from AT&T model i537 build number UCUCNH3 running 4.42. I wanted to root it so I scoured the internet and came upon this thread:
http://forum.xda-developers.com/showthread.php?t=2629093
which explained how I needed to flash the NE3 kernel in order to exploit the root and then I could flash NH3 back (although I did not realize this last part until later )
I rooted my phone which was successful. Then I loaded safestrap which was also successful and I attempted to load some roms that I had heard some had limited success with. I did not have success with the ROMs but I also didn't brick my phone so no harm no foul. However, I after doing a factory reset I realized my Wi-Fi is not working. It will work right after a factory reset briefly but then it just kind of disappears and the Wi-Fi screen will perpetually say it is turning on.
I tried turning back the clock by getting rid of safestrap and re-flashing the NH3 kernel and doing many more factory resets (both through recovery mode and from system) but no luck
TLR; Please Help me get my Wi-Fi back!
Let me know if you found a solution.
I have a similar problem. My i537 Wifi configuration is not remembered by NH3 and after a few reboots, it will fail to turn on completely.
Maybe this one has an obvious solution, but my brief searching around did not find it. I had root access on my S5 using the towelroot method. I used Super SU to unroot. And then I let the phone install a couple of minor OTA updates. All downloaded and installed correctly. The big one 5.0 update however only downloads correctly. But does not install. When trying to install the 5.0 update, my phone reboots, shows install progress up to 27% and then quits the install and reboots into normal mode and reports that installation was interrupted.
At first I tried freeing up a lot of space, when that did not work, I completely reset the phone to factory defaults. And that did not work either. And with that I am out of ideas on how to get 5.0 on my S5. Has any of you seen this issue? Or have any ideas for me to try?
Thanks.
Odin back to NCE then take all of the OTA updates. Use the downgrade to NCE tar found in the general section.
Nucleartx said:
Odin back to NCE then take all of the OTA updates. Use the downgrade to NCE tar found in the general section.
Click to expand...
Click to collapse
Thanks for the suggestion. I am in the process of trying it out. Will update here with the result.
at least am not only one with this problem wish there was steps too much post on the fourms on downgrades and there steps so different.
I was trying to set up my corporate email using knox and it just won't complete the knox installation using mobileiron. After some research, I opened up the Samsung My Knox app and it gives me an error message saying "My KNOX cannot be installed because a custom OS has previously been installed on this device". I have never attempted to root my S5, my knox flag is 0x0 and I am on PA2 I flashed using ODIN. Has anybody seen this problem before? is there a way to fix this problem?
Anyone?
still no luck and have not found anything similar from other forums
yesterday I rebooted my device and to my surprise, during the initial bootscreen, a padlock and the label "Custom" appeared. Funny thing is I have never flashed a custom ROM on my device or attempted to root. I rebooted again and the message did not show up anymore. I think it might have something to do with a flash counter, but I am not sure if it is possible to reset it. Again, my knox flag is 0x0, so I don't know what is going on. Any insight will be helpful.
I think I figured out what went wrong. Seems like when I flashed PA2, the bootloader for some reason did not flash and it stayed on OI5. Once I flashed again the BL file, I am now able to open Knox and my enterprise email.