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)
Rooted my phone with with RDLV before the OTA, never froze anything in TiBu, but disabled.
Installed Wanam and such and made some changes to I am assuming build.prop (notification bar, notification prompts, etc.).
Did the OTA, lost root but not all my mods (including ad blocking as well), but now I show as "custom."
Refuse to risk Kingo to re-root and repair status. Sorry China.
Can I factory reset with MJ5 to get back to full stock without soft brick or must I re-root and undo my changes?
Yeah i just did the factory wipe in recovery and it's clean and still rooted.
[email protected] said:
Yeah i just did the factory wipe in recovery and it's clean and still rooted.
Click to expand...
Click to collapse
Yeah, I lost root, but the "custom" status has me concerned, especially in light of all the recent lockdowns that I won't be able to get 4.4 without fixing the "custom" status.
I just want to be sure doing a factory reset will clean up my mess without softbricking.
I would be sure to do it from the recovery partition not from inside the phone. As far as root it might clean that up as well I remember I was not rooted after ota however after reset I was again.
Sent from my SAMSUNG-SM-N900A using xda app-developers app
[email protected] said:
I would be sure to do it from the recovery partition not from inside the phone. As far as root it might clean that up as well I remember I was not rooted after ota however after reset I was again.
Sent from my SAMSUNG-SM-N900A using xda app-developers app
Click to expand...
Click to collapse
So I did this today, which un-did all of my customizations except two.
1. SuperSu is still installed left over from RDLV I guess.
2. The boot up AT&T sound is still gone after I made that particular mod.
Unfortunately, I'm still showing a "custom" status in settings as well. I can't think of any way to undo this without rooting again (with Kingo?) until we get an Odin-able MJ5.
Is this a correct assumption?
A few months ago I purchased S5 mini, model SM-G800F. Because the phone is not officially released here, it came with a modified ROM and KNOX status 0X1. Right now I am trying to return the phone close as possible to it's stock condition in order to re-enable OTA. I installed the original ROM version from the phone's source country - Romania. However I still have some issues.
1. When I enter download mode it shows both status as official, however when I check the phone status in options, it shows "custom" thus preventing FOTA from working.
2. I have rooted the phone with chainfire auto-root tool, and it increased the flash counter. I tried using Triangle-away app to reset the counter, however it does not work - counter still stays at 2.
3. Despite installing the original ROM, the CSC region still shows the modified one they had with the hacked ROM.
I would appreciate any possible help - also if possible, I would rather not do a factory reset.
As far as I know, there is no tool for mini to reset knox or reset flash count.
Try to read this article:
http://omegadroid.co/wanted-knox-void-warranty-0x1/
Lake292 said:
As far as I know, there is no tool for mini to reset knox or reset flash count.
Click to expand...
Click to collapse
I know the Knox is permanent, but I'd like at least the system to register as "official" on the status info, so FOTA could work
Wanam xposed mod should do the trick to be official again. Do not know if it also work for S5 mini
User_99 said:
Wanam xposed mod should do the trick to be official again. Do not know if it also work for S5 mini
Click to expand...
Click to collapse
yes it works on the mini.
if you cannot update over the air you can flash with odin without loosing data
Ok, I'll post an update.
After noticing that there is a new update available for my phone (G800FXXU1ANL1), I decided to try and update via KIES. Before doing that, I uninstalled all root related apps, while also clearing their data and performed a full unroot with SuperSU. The Kies update went off without a hitch and my device status has also returned to being official. Launching FOTA no longer gives the "modified system" error. Device CSC still seems to show the wrong code (ILO/SEE - the ILO being there from the original modified rom), and the flash counter has not reset, but those are minor annoyances as the bigger problems have been solved - device status is official and I regained the ability to get FOTA.
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.
This weekend, I rooted my Note 8, and I learned I had no use for it since I really cannot do much with it and mobile data will not work at all. I've tried numerous times to flash everything back to the way things were via Odin 3.14.1, but all has failed. I fear if I continue, I may cause a heard brick. Is there something I am doing wrong?
IV_Flower said:
This weekend, I rooted my Note 8, and I learned I had no use for it since I really cannot do much with it and mobile data will not work at all. I've tried numerous times to flash everything back to the way things were via Odin 3.14.1, but all has failed. I fear if I continue, I may cause a heard brick. Is there something I am doing wrong?
Click to expand...
Click to collapse
Maybe. You can check with Frija for latest stock Samsung firmware files and flash it with Odin to your device.
If this does not unroot completely, you may do a factory reset. Keep in mind that this will wipe your data. So backup everything important before.
Or use another method for unfortunately your device, such as described here:
How to Root and Unroot Samsung Galaxy Note 8
In this page we are providing information on root and unroot Samsung Galaxy Note 8 smartphone with or without PC.
rootunroot.com
I was rooted and have tried to go back to stock. Mine passes but will not boot. Get a constant bootloop. I have flashed combination files then stock. Keep getting dm-verity fail in stock recovery. Recognized Contributor Jrkruse even tried to help but nothing. Have flashed stock so many times I lost count. Any ideas?