Related
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)
**Make certain that your reactivation lock in security settings is off before beginning this process**
1. Take the NG3 OTA update.
2. Download and install Towelroot-v3.apk(this version does not require internet access).
3. Place your phone into "Download Mode" (press and hold the Home, Volume Down, and Power keys until the phone powers on and displays warning screen, then press Volume Up key) and flash the G870A_NE4_Stock_Kernel using Odin's PDA slot(AP in Odin v3.09+).
4. Open the Towelroot app from your app drawer and press "Make it Rain" to root your device.
5. Power off then boot into "Download Mode" again and flash the G870A_NG3_Stock_Kernel also in Odin's PDA slot(AP in Odin v3.09+).
6. Download SuperSu to manage root access. Done!
Troubleshooting:
1. If the NG3 OTA update fails consider flashing the G870AUCU1ANE4_Full_Odin.tar to return to stock then take the NG3 OTA update, (or place the G870A_NE4toNG3_OTA.zip onto your ext-sdcard and sideload from stock recovery). Once updated to NG3 continue to Step 2 above.
2. The most common cause of an Odin flash failure is a bad usb port or cable. Please check before reporting a failure.
Notes:
1. After flashing the NE4 kernel your phone may run a little wonky and towelroot may not root on the first try. If that happens reboot and try towelroot once again. Once rooted and after flashing the NG3 kernel your phone will once again run like a champ!
2. The above process will not affect your User Data or Knox Warranty Flag.
Credits:
@lordmorphous - Tester
Gonna try this... Thanks! :beer:
Sent from my SAMSUNG-SM-G870A using XDA Free mobile app
Yes this worked. Thank you very much.......
Are we going to trip Knox using the method above ???
Just wanna be sure about this. ...g
gregsarg said:
Are we going to trip Knox using the method above ???
Just wanna be sure about this. ...g
Click to expand...
Click to collapse
Nope.
Does anyone have a list of the benefits of updating to NG3?
I just rooted my new phone on NE4 and I want to know whether it's worth taking the time.
Thanks for the How-to! Worked great for me!
Any benefits on ng3 over stock?
Root possible for 'straight out-of-the-box' G870AUCU1ANG3???
I've looked and looked around the forums here and have come to the conclusion that the AT&T S 5 I recently picked up is, sadly, unable to be rooted. Does anyone here know if this is true? As the title suggests, my phone seems to have come loaded with G870AUCU1ANG3. Is it possible that it came with the previous iteration (NE4, I think??) and I didn't avoid an update, thus meaning I can flash the earlier version? Can I even tell whether it's possible to 'revert' to NE4 (or whatever it would be)? Is any of this even possible without having been previously rooted, or am I wasting my time searching this out? Naive but earnest questions... sorry if I'm in the wrong place here. I promise, I poked around the site for a few days in search of clarity before posting.
papayajelly said:
I've looked and looked around the forums here and have come to the conclusion that the AT&T S 5 I recently picked up is, sadly, unable to be rooted. Does anyone here know if this is true? As the title suggests, my phone seems to have come loaded with G870AUCU1ANG3. Is it possible that it came with the previous iteration (NE4, I think??) and I didn't avoid an update, thus meaning I can flash the earlier version? Can I even tell whether it's possible to 'revert' to NE4 (or whatever it would be)? Is any of this even possible without having been previously rooted, or am I wasting my time searching this out? Naive but earnest questions... sorry if I'm in the wrong place here. I promise, I poked around the site for a few days in search of clarity before posting.
Click to expand...
Click to collapse
There shouldn't be any reason why you can't follow the instructions in the 1st post of this thread starting with step 2.
I've been searching for a while and can't find anything about using this root method and then being able to install safestrap. Has anyone been successful in doing this? Do I need to downgrade before and does anybody have the downgrade file? FYI Just bought my phone last night and was successful in rooting.
rescuedad said:
I've been searching for a while and can't find anything about using this root method and then being able to install safestrap. Has anyone been successful in doing this? Do I need to downgrade before and does anybody have the downgrade file? FYI Just bought my phone last night and was successful in rooting.
Click to expand...
Click to collapse
Never mind, I figured it out. If you have the active you need to downgrade the kernel to NE4 like you do if you need root. Then you install Safestrap 3.75. I'm doing a Nandroid backup as I type. I'm going to re-flash the NG3 stock kernel when I'm done and hopefully that will be fine.
If it bricks, I can always take it back since I blocked the knox counter... BTW I'm on At&T
I downgraded to the NE4 to root. Along with others here I have to ask, what are, if any, benefits to upgrading the kernel?
panthersdzynes said:
I downgraded to the NE4 to root. Along with others here I have to ask, what are, if any, benefits to upgrading the kernel?
Click to expand...
Click to collapse
Not sure I understand the question but I will take a shot......typically the kernel, modules, and non-hlos.bin have to match or else you may experience issues such as no wifi, lag, etc. The NE4 and NG3 kernel and modules may be similar enough that you will not experience issues immediately but they may develop later unless you reflash the NG3 kernel to match your modules and non-hlos.
muniz_ri said:
Not sure I understand the question but I will take a shot......typically the kernel, modules, and non-hlos.bin have to match or else you may experience issues such as no wifi, lag, etc. The NE4 and NG3 kernel and modules may be similar enough that you will not experience issues immediately but they may develop later unless you reflash the NG3 kernel to match your modules and non-hlos.
Click to expand...
Click to collapse
I see. Thank you, that answers my question.
THanks XDA
Been away along time. Had iphones for the last 6 years. Use to go here all the time in the Kaiser days (Att Tilt) if any of you remember. I see XDA has still been kicking ass while I've been gone! Glad to be back and Thank You everyone especially first poster for the guide to root my Att GS5 Active.
THANK YOU
Working perfectly. ..thank you. ..g
There was a small update released today. Can someone that is rooted grab it from their fota/cache folder and send to me so that I can update this guide? Thanks.
WORKED! AWESOME!
Now... I have installed SuperSU. Was that left out of the first post?
Also, if I do not flash the NG3 Stock Kernel back afterwards, will I experience funkiness?
Thanks again!
A little background. A few months ago I purchased a Samsung Galaxy S4 Active SG-I537 from a person on Craigslist after my HTC One M7's microphone died. Anyway, I thought the phone was fully stock. I started to become suspicious that this was not the case when I checked for software updates from AT&T and the updates began to fail repeatedly. I downloaded a root checker from the Google Play store and, confirming my suspicions, I had root access. I didn't really like finding this out this way, but it was my own fault for not asking. Having installed CyanogenMod on both a Galaxy S1 Fascinate and an S2 Skyrocket, I knew something about these things and decided to just live with it as the phone seemed to work otherwise.
Recently I tried playing video on my DirecTV app and found that the app would not function on a rooted phone. That coupled with the fact that I am hearing that Android 5.0 Lollipop will soon be released for the S4 Active made me want to return the phone to a stock firmware. So I began reading. The problem I have is that I have no idea whatsoever how the phone was rooted. I know that the firmware was 4.2.2 UCUAMF3. So I downloaded ODIN and the full ODIN package of UCUCNE3 and then followed the below guide to a T.
Everything seemed to work, I got a pass green light from ODIN. But I have a circle with a line thru it where the AT&T wording usually appears. The 'about device' page in the settings also says 'Baseband version' is unknown. and I have no cell abilities. I can do everything from the smartphone end via WiFi. But I have no cell phone capabilities. Can't make calls, etc. What I need now is someone to point in the proper direction of where to look for the knowledge on how to fix this problem. Any help would be greatly appreciated.
Thanks.
Code:
Quote:
MF3 to MF2 (Official: Released 2013-06-21)
Quote:
MF3 to MF3 (Official: Released 2013-06-21)
Quote:
MF3 to MI2 (Leaked: Released 2013-09-25)
Quote:
MF3 to ML2 (Official: Released 2014-01-07)
Quote:
MF3 to NC9 (Official: Released 2014-04-16)
Quote:
MF3 to NE3 (Official: Released 2014-06-06)
Download the NE3 Full Odin Package from the i537 Firmware Thread.
Extract SGH-I537UCUCNE3_v4.4.2_ATT_ALL.zip using a program such as 7-zip.
Download the Windows program Odin. For more information about what Odin is and where to get it, please read the Odin section in the first post.
Open the version of Odin that you downloaded (preferably Odin v3.07)
Once opened, you need to load the files for the Bootloader, PDA, Phone, and CSC. The required files are located in the Odin Files folder. It should look exactly like the screenshot below with the appropriate checkboxes checked.
Next put your phone in download mode. For more information on how to put your phone in download mode, please read the download mode section in the first post.
Once your phone is in Download Mode, connect it to your computer using the cable that came with your phone. IMPORTANT: Odin and Samsung phones are very finicky when flashing firmware, the only usb cable that is guaranteed to work is the cable that came with your phone. You may use other usb cables, but Odin may not detect your phone. If Odin does not detect your phone try connecting to a different usb port or a different computer.
If your phone has connected properly it should show up properly in the Odin window similar to the following picture:
Once Odin has detected your phone, hit Start. It will take a long time to flash the package to your phone and will completely wipe your phone. DO NOT DISCONNECT THE CABLE OR TURN OFF YOUR COMPUTER. If the process is abruptly interrupted you risk permanently bricking your phone, so be careful.
When the program has finished it is safe to disconnect everything and reboot your phone. Your phone will be completely stock, unrooted and you will have to setup your phone from scratch again. If you wish to root the NE3 firmware, please visit the towelroot website.
tried asking the person you bought it from?
I've heard that installing a firmware/rom twice in a row can help things. try that! good luck!
If IMEI is null (check by dialing *#06#) and similar situation like this?
http://forum.xda-developers.com/showthread.php?p=56473692
O-T said:
If IMEI is null (check by dialing *#06#) and similar situation like this?
http://forum.xda-developers.com/showthread.php?p=56473692
Click to expand...
Click to collapse
Wow, I spent 7 hours on this yesterday and couldn't find that thread. I guess my search skills aren't what I thought they were. A huge thanks, O-T. I'm back up and running. I flashed the MF1 modem to get the service menu back up and selected the correct option. I was then able to reflash the NE3 firmware and now I have baseband and IMEI properly identified and working. Took another couple of hours but I'm there. Again, mucho thanks.
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.
Just got this att G4 ACTIVE On [email protected]@lk
SGH-I537
BaseBand version = I537UCUCNH4
Build number = KOT49H.I537UCUCNH4
OTA updated To NH4. Never been rooted.
It fails to update any further to Lollipop.
After downloading the update it restarts and says Installing...... but before its done it reboots.
MESSAGE Update Failed "Software Update Interrupted"
I tried manual method, renaming the file to update.zip on SD and get this ERROR
"error tmp/sideload/package.zip status 7" During install
it wipes the phone and no update
Most guides pertain to NE3 , NH3
How does Having NH4 change things?
Options & Opinions For Updating NOROOT/ROOT Welcome
NH4 is a stagefright patch for NH3
NH4 does not seem to have patched stagefright vulnerability
thisisapoorusernamechoice said:
NH4 is a stagefright patch for NH3
Click to expand...
Click to collapse
I'm running rooted i537UCUCNH4 (android 4.4.2) and an app from the google playstore called "stagefright detector" by Zimperium Inc. reports that my phone is vulnerable. It passes six tests but fails two. All are similarly named. The two my AT&T SGH-I537 does not pass are CVE-2015-6602, and CVE-2015-3864. I have opened my default messaging app and unchecked the setting box for "Auto retrieve". Any messages with pictures or multimedia files, even from trusted relatives, now prompts with a download button for these MMS messages. All attempts to dowload fail. I've told some of my relatives to send any of their multimedia messages to my wife's iphone, rather than my android phone.
Don't really care to change to lollipop or rooted lollipop on this device as I already have tried both.
I think we should all revert to either, word of mouth, snail mail, carrier pigeon delivery, or the pony express.
namitutonka said:
I'm running rooted i537UCUCNH4 (android 4.4.2) and an app from the google playstore called "stagefright detector" by Zimperium Inc. reports that my phone is vulnerable. It passes six tests but fails two. All are similarly named. The two my AT&T SGH-I537 does not pass are CVE-2015-6602, and CVE-2015-3864. I have opened my default messaging app and unchecked the setting box for "Auto retrieve". Any messages with pictures or multimedia files, even from trusted relatives, now prompts with a download button for these MMS messages. All attempts to dowload fail. I've told some of my relatives to send any of their multimedia messages to my wife's iphone, rather than my android phone.
Don't really care to change to lollipop or rooted lollipop on this device as I already have tried both.
I think we should all revert to either, word of mouth, snail mail, carrier pigeon delivery, or the pony express.
Click to expand...
Click to collapse
Lol, also, how did you root your phone? I have the i537 UCUCNH4 4.4.2 also, but I can't get into the download mode.
hooded defender said:
Lol, also, how did you root your phone? I have the i537 UCUCNH4 4.4.2 also, but I can't get into the download mode.
Click to expand...
Click to collapse
You have to follow this site's instructions to root: http://www.w0lfdroid.com/2014/09/To...-and-Note3-Android-4.4.2-NF-or-Later.html?m=1 with one important change. For step 7, use the following NH4 kernel: https://www.androidfilehost.com/?fid=24052804347796155.
You get into download mode by first shutting your phone down, then hold vol- and power
0
thisisapoorusernamechoice said:
You have to follow this site's instructions to root: (cant post a u r l) with one important change. For step 7, use the following NH4 kernel: (cant post a u r l).
You get into download mode by first shutting your phone down, then hold vol- and power
Click to expand...
Click to collapse
Thanks! I actually already started trying that method, but I can't because I can't flash back to 4.3. It just won't enter into download mode, it just vibrates and then proceeds to start up normally. I have tried any number of button combinations including the normal ones. It will boot into recovery mode though. Also, it will display an at&t logo instead of the normal galaxy logo.
hooded defender said:
Thanks! I actually already started trying that method, but I can't because I can't flash back to 4.3. It just won't enter into download mode, it just vibrates and then proceeds to start up normally. I have tried any number of button combinations including the normal ones. It will boot into recovery mode though. Also, it will display an at&t logo instead of the normal galaxy logo.
Click to expand...
Click to collapse
4.3 has nothing to do with this and have you tried using adb to to make your phone boot into download mode?
thisisapoorusernamechoice said:
4.3 has nothing to do with this and have you tried using adb to to make your phone boot into download mode?
Click to expand...
Click to collapse
Not yet, I'm new to all of this, so I will see what I can do with adb. If you know a good tutorial for it, that would be nice, but I'll try and figure it out.
Also, I thought you had to flash back to 4.3 to root, then flash back to 4.4.2, which is why I needed to get into download mode - and to use odin if I needed that too.
hooded defender said:
Not yet, I'm new to all of this, so I will see what I can do with adb. If you know a good tutorial for it, that would be nice, but I'll try and figure it out.
Also, I thought you had to flash back to 4.3 to root, then flash back to 4.4.2, which is why I needed to get into download mode - and to use odin if I needed that too.
Click to expand...
Click to collapse
You're not using Odin to flash an older version of android, you're using Odin flashing an older kitkat (i.e. 4.4.2) kernel