Related
I renewed my at&t 2 year contract on Sept 5th and upgraded to an s4. The phone has given me nothing but problems from the moment I first touched it. Long story short is that im taking it back to the store tomorrow and returning it. I called the store today and the girl on the phone basically said that since im still within my 14 days it will be a straight across trade for a new s4. I didn't mention to her that the phone is rooted and debloated. When I first received the phone it wasn't running the MF3 firmware. I unlocked and rooted the phone and installed a couple different roms trying to eliminate the near unusability due to lag and freezing. (I Know I should have just returned the phone immediately) I ended up soft bricking the phone while flashing custom firmware... So I used odin to get back to the original stock firmware, then did the at&t MF3 upgrade and rooted. Question- I know this is doubtful, but does anyone know of a way to restore the MF3 firmware to stock? If not, what should I do to get the phone as close to stock as possible? I was thinking I could reinstall all of the AT&T bloat from the playstore, turn them back into system applications via titanium back up and the uninstall SuperSU. The current device status under about device is listed as "Official"...
Go to best buy they can flash it to stock mf3
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app
johnharty3 said:
Go to best buy they can flash it to stock mf3
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Thanks for the reply! Do you think I would absolutely need to do that before taking it in for exchange, or do you think restoring the bloat and uninstalling SuperSU would be sufficient. BestBuy is kinda out of the way for me but I would do it if it was absolutely necessary...Thanks
I called today and they told me at best buy to come in and they coukd restore it to stock but I think you would be fine just removing SU
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app
norcal61 said:
Thanks for the reply! Do you think I would absolutely need to do that before taking it in for exchange, or do you think restoring the bloat and uninstalling SuperSU would be sufficient. BestBuy is kinda out of the way for me but I would do it if it was absolutely necessary...Thanks
Click to expand...
Click to collapse
Yea if it still says official under device status you're fine. Uninstall all rooted apps like greenify, superSU, titanium backup, etc... Make sure you defrost/enable any freezed/disable apps just in case.
When you go in tomorrow, stay positive and act as if nothing happened.
haremmon said:
Yea if it still says official under device status you're fine. Uninstall all rooted apps like greenify, superSU, titanium backup, etc... Make sure you defrost/enable any freezed/disable apps just in case.
When you go in tomorrow, stay positive and act as if nothing happened.
Click to expand...
Click to collapse
Sweet, thanks for the reinforcement! That was my plan exactly! If they say anything about the phone having been rooted, ill be like " rooted? whats that?"...LOL
norcal61 said:
Sweet, thanks for the reinforcement! That was my plan exactly! If they say anything about the phone having been rooted, ill be like " rooted? whats that?"...LOL
Click to expand...
Click to collapse
"Don't worry fine AT&T Representative! This phone has never been used to plant trees!"
I took the phone in yesterday and got a stubborn rep who wanted to trouble shoot and blah blah blah. She took the phone in the back. When she came out she said all the phone needed was a new sim. I said no I want a new phone. So she said to come back tomorrow when the manager is there. Whatever she did to the phone caused the custom status to return. I had official status upon entering the store. Dont know how that happened. Im off to att to see if I can trade it in today.
Sent from my SAMSUNG-SGH-I337 using Xparent Green Tapatalk 2
norcal61 said:
I took the phone in yesterday and got a stubborn rep who wanted to trouble shoot and blah blah blah. She took the phone in the back. When she came out she said all the phone needed was a new sim. I said no I want a new phone. So she said to come back tomorrow when the manager is there. Whatever she did to the phone caused the custom status to return. I had official status upon entering the store. Dont know how that happened. Im off to att to see if I can trade it in today.
Sent from my SAMSUNG-SGH-I337 using Xparent Green Tapatalk 2
Click to expand...
Click to collapse
Please post back and let us know what happened.
Sent from my SAMSUNG-SGH-I337 using Tapatalk 4
Sounds like what I went thru. Brought my new phone home and accidently updated to MF3 without knowing I screwed myself in the process. Returned 2 days later complaining of random reboots and sod's. They tried to troubleshoot my phone and told me a restore was needed to get my fon right. Told them if they don't replace my S4 with a new one I'll cancel the contract right on the spot.
After about an hour of their blah blah blah they gave me a brand new 32gb on MDL and I'm happily rooted now on CM... I'm liking this phone a lot now!
Sent from my SGH-I337 using XDA Premium 4 mobile app
supitsronnie said:
Please post back and let us know what happened.
Sent from my SAMSUNG-SGH-I337 using Tapatalk 4
Click to expand...
Click to collapse
Yesterday I took the phone into BestBuy to have them flash it with MF3 to try and get rid of the custom status and boot screen. They looked at me like I was speaking Chinese when I asked them to do this in the phone dept. Even the geek squad had no idea what I was talking about. They said they had no way to reflash the phone. All they could do was restore the phone within the settings...UHG!! So no luck there on going back to official status. I found instructions here in the forum that work like a charm for going back to official status and getting rid of the custom boot screen. I used theses steps. All thanks go to Senior Member - ou812bkewl
1. Re-root again using the same method you did before for MF3, then:
--a) Reboot, update SuperSU app and it's binary
--b) Reboot again, verify device status is back to"Official"
--c) Reboot again, verifying that, this time, the boot screen is back to normal again
2. Download a file manager app in the Play Store called "Total Commander" and enable "Root functions everywhere" in its settings.
3. Navigate to a folder called "/system/xbin"
4. Delete ONLY files in that folder with the word "busybox" within its filename or symlink path. You should end up with three files left. I did. Two of them are SuperSU related. DO NOT DELETE ANY OF THEM!
5.Open SuperSU and, in its settings, select the "Full un-root" option. Once SuperSU closes, reboot.
When you reboot, wait a full minute and check on device status. It should still say "Official" and you will be fully un-rooted.
So im completly unrooted and official...Im off to the AT&T store shortly to try and exchange this thing...wish me luck!
norcal61 said:
Yesterday I took the phone into BestBuy to have them flash it with MF3 to try and get rid of the custom status and boot screen. They looked at me like I was speaking Chinese when I asked them to do this in the phone dept. Even the geek squad had no idea what I was talking about. They said they had no way to reflash the phone. All they could do was restore the phone within the settings...UHG!! So no luck there on going back to official status. I found instructions here in the forum that work like a charm for going back to official status and getting rid of the custom boot screen. I used theses steps. All thanks go to Senior Member - ou812bkewl
1. Re-root again using the same method you did before for MF3, then:
--a) Reboot, update SuperSU app and it's binary
--b) Reboot again, verify device status is back to"Official"
--c) Reboot again, verifying that, this time, the boot screen is back to normal again
2. Download a file manager app in the Play Store called "Total Commander" and enable "Root functions everywhere" in its settings.
3. Navigate to a folder called "/system/xbin"
4. Delete ONLY files in that folder with the word "busybox" within its filename or symlink path. You should end up with three files left. I did. Two of them are SuperSU related. DO NOT DELETE ANY OF THEM!
5.Open SuperSU and, in its settings, select the "Full un-root" option. Once SuperSU closes, reboot.
Click to expand...
Click to collapse
When you reboot, wait a full minute and check on device status. It should still say "Official" and you will be fully un-rooted.
So im completly unrooted and official...Im off to the AT&T store shortly to try and exchange this thing...wish me luck!
Click to expand...
Click to collapse
Good luck, let us know how it goes.
haremmon said:
Good luck, let us know how it goes.
Click to expand...
Click to collapse
I made it to the att authorized dealer where I bought the phone. The manager was totally cool and exchanged the phone for me no problems. The new phone came with the MDL firmware as well as the first. This phone was not buggy and laggy out of the box like the last one. I updated the firmware to the mf3 build and decided to leave it unrooted until there is an unlock and restore method for this build. This phone is working great and having no problems. I'm pleased
Sent from my SAMSUNG-SGH-I337 using Xparent Green Tapatalk 2
norcal61 said:
I made it to the att authorized dealer where I bought the phone. The manager was totally cool and exchanged the phone for me no problems. The new phone came with the MDL firmware as well as the first. This phone was not buggy and laggy out of the box like the last one. I updated the firmware to the mf3 build and decided to leave it unrooted until there is an unlock and restore method for this build. This phone is working great and having no problems. I'm pleased
Sent from my SAMSUNG-SGH-I337 using Xparent Green Tapatalk 2
Click to expand...
Click to collapse
Congrats, glad you got your phone back safely.
If you don't mind me asking but why did you update your phone to MF3 build as many would have blocked the update right away. :s
haremmon said:
Congrats, glad you got your phone back safely.
If you don't mind me asking but why did you update your phone to MF3 build as many would have blocked the update right away. :s
Click to expand...
Click to collapse
Thanks! I thought long and hard about weather or not I was going to update to mf3. I decided that since I'm not going to root the phone or install anything custom at this time I may as well be on the latest firmware.
Sent from my SAMSUNG-SGH-I337 using Xparent Green Tapatalk 2
norcal61 said:
Thanks! I thought long and hard about weather or not I was going to update to mf3. I decided that since I'm not going to root the phone or install anything custom at this time I may as well be on the latest firmware.
Sent from my SAMSUNG-SGH-I337 using Xparent Green Tapatalk 2
Click to expand...
Click to collapse
I hope you don't ever want to install a custom rom. Since you did that, you will likely never be able to.
I'm not really worried about. I pretty much enjoy a stock experience. I have two nexus 7 tablets for hacking and playing with mods. I use this phone for my business and I'm just after a straight forward experience. If there's ever an app that I want that requires root I can always root this firmware. And I would be surprised if this bootloader stays locked forever.
Sent from my SAMSUNG-SGH-I337 using Xparent Green Tapatalk 2
Hi,
On MF3.
I'm rooted. I have clock work recovery installed.
I can download the update succeffuly however when the phone reboots the install begins, gets as far as 25% then fails. Phone reboots back to 4.2.2 with a message that says the install was interrupted.
Have tried twice with the same result.
Anyone else experiencing this?
Sent from my SAMSUNG-SGH-I337 using Tapatalk
ckalantzis said:
Hi,
On MF3.
I'm rooted. I have clock work recovery installed.
I can download the update succeffuly however when the phone reboots the install begins, gets as far as 25% then fails. Phone reboots back to 4.2.2 with a message that says the install was interrupted.
Have tried twice with the same result.
Anyone else experiencing this?
Sent from my SAMSUNG-SGH-I337 using Tapatalk
Click to expand...
Click to collapse
If I were you I would go back and read a little information about mf3 and what kind of recovery can be used. It sounds to me like you might be very confused. In order to correctly keep from bricking your phone you may want to read up on things. Good luck.
ckalantzis said:
Hi,
On MF3.
I'm rooted. I have clock work recovery installed.
I can download the update succeffuly however when the phone reboots the install begins, gets as far as 25% then fails. Phone reboots back to 4.2.2 with a message that says the install was interrupted.
Have tried twice with the same result.
Anyone else experiencing this?
Sent from my SAMSUNG-SGH-I337 using Tapatalk
Click to expand...
Click to collapse
Since you are rooted, take a look in the /cache/recovery directory. Read the log file. It will tell you where things messed up.
For example, I had forgotten that I did something with csc and had replaced the feature.xml file. Luckily, I had a back up of the original file. I renamed it, fixed is file permissions to rw-r--r--, advanced my clock one day, and then was able to install MJ9.
Good luck, and remember you won't have root anymore when you install this (for the time being)
Yrs,
dkephart
Sent from my SAMSUNG-SGH-I337 using Tapatalk
ckalantzis said:
Hi,
On MF3.
I'm rooted. I have clock work recovery installed.
I can download the update succeffuly however when the phone reboots the install begins, gets as far as 25% then fails. Phone reboots back to 4.2.2 with a message that says the install was interrupted.
Have tried twice with the same result.
Anyone else experiencing this?
Sent from my SAMSUNG-SGH-I337 using Tapatalk
Click to expand...
Click to collapse
I had the same problem. The only way I was finally able to upgrade to 4.3 was to use Odin to revert to stock (unrooted) 4.2.2 MF3 using the files on this thread: http://forum.xda-developers.com/showthread.php?t=2502003 Once I did that I ran the OTA update to 4.3 and it worked without any problems
To able to keep your root and upgrade from 4.2.2 to 4.3 you have to change your param file back to the stock. Thats all the information that I have so far so... not completely sure. But I think that is what you're supposed to do.
Because you have a custom param file, when you try to upgrade to 4.3 it's telling you there is an issue with your phone.
I may be wrong.
Is there a copy of the correct feature.xml? Im having the same issue
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
According to the log its stopping when it can't find the chat on apk. I did remove it using titanium.
Will restore it try again andbipdate the thread. Thanks for pointing out the correct log file to look at.
Sent from my SAMSUNG-SGH-I337 using Tapatalk
I checked again and found my backup feature.xml. Typed this from mj9.
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
ckalantzis said:
Hi,
On MF3.
I'm rooted. I have clock work recovery installed.
I can download the update succeffuly however when the phone reboots the install begins, gets as far as 25% then fails. Phone reboots back to 4.2.2 with a message that says the install was interrupted.
Have tried twice with the same result.
Anyone else experiencing this?
Sent from my SAMSUNG-SGH-I337 using Tapatalk
Click to expand...
Click to collapse
I had the same problem happen to me on Wednesday night and last night. Today I used Odin to go back to stock MF3, however, then I couldn't get the OTA update. It kept saying my firmware was up to date each of the three times I restored it.
Now I'm finally on MJ9 after copying "update-mf3-mj9.zip" to my SD card, going into recovery mode, and updating from external SD card. Now I can use my Galaxy Gear!
Cause I want to sound like a noob.
How did you install CWM on what reads to me a MF3 S4.
Those on MF3 have been using Safestrap cause CWM hasn't been possible.
Sent from my ATT S4 MF3 using Tapatalk
jball said:
Cause I want to sound like a noob.
How did you install CWM on what reads to me a MF3 S4.
Those on MF3 have been using Safestrap cause CWM hasn't been possible.
Sent from my ATT S4 MF3 using Tapatalk
Click to expand...
Click to collapse
I was excited when I rooted the phone, then installed ROM manager premium. It allowed me to install the recovery. You can even boot into the recovery from ROM Manager.
However since the S4 is locked down tight, you can do any thing from there. So i can't flash anything. It even gives me a message saying as much.
However it is partially installed I can boot into it at will.
I will post a video of it. So that you all have an idea of what im talking about.
Sent from my SAMSUNG-SGH-I337 using Tapatalk
Don't waste your time with a video,its your stock recovery.your not the first to have done this.lets jump ahead a bit and just install Safestrap.whats Safestrap you might ask?search for it and READ please sir.
Sent from my ATT S4 MF3 using Tapatalk
jball said:
Don't waste your time with a video,its your stock recovery.your not the first to have done this.lets jump ahead a bit and just install Safestrap.whats Safestrap you might ask?search for it and READ please sir.
Sent from my ATT S4 MF3 using Tapatalk
Click to expand...
Click to collapse
While I was preparing to record it, I did notice that you are correct. Although Rom Manager goes through the motions of flashing the recovery, when you attempt to boot into the Recovery, you are faced with an Error, and default back into Android Recovery.
Although I know all about Safestrap...I think we've all missed the point. The OP was meant to get help about why the 4.3 OTA was failing 25% into the install.
I've got what I needed by being pointed to the location of the install log.....and while reading through it, I noticed that the install is failing because I removed the Chat On APK. I will install from backup and move forward.
Thank you all who provided the necessary guidance to solve the original problem.
Thank you as well to those who helped clear up the whole Clockwork vs Android recovery part. Although a minor part of the original post, it's good that we don't spread misinformation.
Cheers
ckalantzis said:
While I was preparing to record it, I did notice that you are correct. Although Rom Manager goes through the motions of flashing the recovery, when you attempt to boot into the Recovery, you are faced with an Error, and default back into Android Recovery.
Although I know all about Safestrap...I think we've all missed the point. The OP was meant to get help about why the 4.3 OTA was failing 25% into the install.
I've got what I needed by being pointed to the location of the install log.....and while reading through it, I noticed that the install is failing because I removed the Chat On APK. I will install from backup and move forward.
Thank you all who provided the necessary guidance to solve the original problem.
Thank you as well to those who helped clear up the whole Clockwork vs Android recovery part. Although a minor part of the original post, it's good that we don't spread misinformation.
Cheers
Click to expand...
Click to collapse
You handled this all very well.
ITNV said:
I had the same problem. The only way I was finally able to upgrade to 4.3 was to use Odin to revert to stock (unrooted) 4.2.2 MF3 using the files on this thread: http://forum.xda-developers.com/showthread.php?t=2502003 Once I did that I ran the OTA update to 4.3 and it worked without any problems
Click to expand...
Click to collapse
Did you use all files? I mean, I've been trying the same for the past couple of days, and I even asked in that thread if I could use just the PDA file, nobody replied so I went ahead and did it, it removed the root and I kept all my files and settings (That was the idea) but just after that I can't connect anymore to Kies ( I could without issues, I did a full backup moments before) and trying to do the sideload it always gives me the Error 7, I even tried the full SD card update,it erased everything and guess what, when it rebooted for my surprise I was still at 4.2.2 MF3, so it just did the Wipe Data and then rebooted, so I lost almost 6 hours getting everything back as it was and then, I had the Damaged SD card error so I also lost all my pictures and videos withoout back up.
So, as you can see half a day later I'm still at the same point I was this morning and with a huge loss, so, please, Did you use all the files? If you did, doing this erase everything also?
Thanks in adavance.
erasat said:
So, as you can see half a day later I'm still at the same point I was this morning and with a huge loss, so, please, Did you use all the files? If you did, doing this erase everything also?
Thanks in adavance.
Click to expand...
Click to collapse
Yes. I used all the files. The result was a completely stock unrooted 4.2.2 so, yes, it reset the phone and erased everything that I had on there. (It left my external SD card intact but I would still advise removing it if there is anything on there you don't want to lose.)
ITNV said:
Yes. I used all the files. The result was a completely stock unrooted 4.2.2 so, yes, it reset the phone and erased everything that I had on there. (It left my external SD card intact but I would still advise removing it if there is anything on there you don't want to lose.)
Click to expand...
Click to collapse
Yep, that was the reason why I just used the PDA I didn't want to lose my data, and then I did it anyways, my mistake was not doing the Odin Restore just after I realized that it erased everything and I was still at 4.2.2, that's was the perfect time to do it, but now, after I finally put everything back as it was, I simply don't see myself by my own choice, doing all this again.
Thanks.
erasat said:
Did you use all files? I mean, I've been trying the same for the past couple of days, and I even asked in that thread if I could use just the PDA file, nobody replied so I went a head and did it, it removed the root and I kept all my files and settings (That was the idea) but just after that I can't connect anymore to Kies ( I could without issues, I did a full backup moments before) and trying to do the sideload it always gives me the Error 7, I even tried the full SD card update,it erased everything and guess what, when it rebooted for my surprise I was still at 4.2.2 MF3, so it just did the Wipe Data and then rebooted, so I lost almost 6 hours getting everything back as it was and then, I had the Damaged SD card error so I also lost all my pictures and videos withoout back up.
So, as you can see half a day later I'm still at the same point I was this morning and with a huge loss, so, please, Did you use all the files? If you did, doing this erase everything also?
Thanks in adavance.
Click to expand...
Click to collapse
It was mentioned several times in that thread exactly what files to use and how to use them. There were also several pictures provided that showed EXACTLY what the ODIN screen should look like before the flash.
scott14719 said:
It was mentioned several times in that thread exactly what files to use and how to use them. There were also several pictures provided that showed EXACTLY what the ODIN screen should look like before the flash.
Click to expand...
Click to collapse
In the thread, there are tons of instances where it explains where to use each file and even pictures, I know because I read every single post, but none of them explains if I could use just the PDA one if I wanted to keep my settings while unrooting the phone, that's why I asked about it, because nobody replied to my question I decided to be the guinea pig, and yes, it works, you keep your settings, and I was glad, but as you can see, what I wanted to accomplish didn't work after all. Without all the files it doesn't fix the issue that causes the error 7 when doing the sideload.
help with mf3 to mj9
Having the same issue and formatted card with backup image.
Update got to 23 % and failed
now phone refuses to flash in odin.....and im missing factory apps preventing me from doing anything to get it back to stock
anyone have a stock restore image I could use in kies?
Would that work properly?
I have looked around the forums for this problem, but could only find something about root checker.
But does the G2 have a flash counter like the Samsung phones does?
What i mean by this is; Will i be able to restore the stock firmware via the LG flash tool, and the stores would never be able to tell it was flashed?
I'm asking because my brother bricked his device, and made the sim card reader stop working. And after we factory reset the phone via Odin and sent it back to be repaired, we got it back without getting it fixed. Turns out we missed the Flash counter, and now that phone is out of warrenty.
Does the G2 have a similar counter build in? If not, good job LG!
Yes, the LG G2 has a rootchecker. Unfortunately there is no way to reset it for now. I've used LG flash tool to restore to stock at least 4 times, but it still shows "ROOTED" in red letters when I switch to download mode. It shows "unrooted" right after restoring to stock, but restart and check it an hour later and it shows "ROOTED." I'm still looking for a solution to this. My GPS is horrible so I want to return it.
benjaminj007 said:
Yes, the LG G2 has a rootchecker. Unfortunately there is no way to reset it for now. I've used LG flash tool to restore to stock at least 4 times, but it still shows "ROOTED" in red letters when I switch to download mode. It shows "unrooted" right after restoring to stock, but restart and check it an hour later and it shows "ROOTED." I'm still looking for a solution to this. My GPS is horrible so I want to return it.
Click to expand...
Click to collapse
Anyone else confirm this?
I though a simple flash to stock resets the flash/rooted message.
bigup7 said:
Anyone else confirm this?
I though a simple flash to stock resets the flash/rooted message.
Click to expand...
Click to collapse
Mine goes back to UNROOTED after flashing to stock. D802.
MalignantQuechnitlan said:
Mine goes back to UNROOTED after flashing to stock. D802.
Click to expand...
Click to collapse
What I understand from benjaminj007's post, his goes to UNROOTED as well, however at some point it reverts to ROOTED. Have you checked yours after some time or just after flashing?
I installed stock somewhere last week, just checked and it still says unrooted.
As far as I remember my 802 also said unrooted after my total reset using lg Flash tool.
Sent from my LG-G2 using Tapatalk
Hello Gents,
Have had my S4 for about a year now and its been awesome (still on MK2, stopped it from updating). It is rooted and safestrap has been installed. I didn't get around to installing a custom ROM though so im still on stock ROM. Been noticing some random issues today and cant pinpoint why. First I am unable to turn on WIFI, was able to yesterday but now it just stays grey. I randomly lose my data connection (well it has a circle with a line through it) and it randomly just pops back on to 4g. I was playing on the phone one time and no SIM error came up but then went away. Power saving mode turned itself on randomly when i have over half battery. Lots of random things happening...
Now i did lose some data and have been trying to recover it this past week using this thread http://forum.xda-developers.com/gal...e-internal-memory-data-recovery-yes-t1994705/
I didn't make it far though because when i try to launch ADB Shell it gives me a permission error.
So that is another thing on the list, it is no longer prompting me to give root access to things. I also noticed that when i power on the phone, it no longer shows Samsung with a lock like it did ever since i rooted it. It now shows Samsung Galaxy S4...I Guess i may have lost root? I downloaded root checker and it says i still have it. Anyway its just so confusing, is it time to blow everything out and go back to stock MK2 and start over? What do you guys think? Thanks!
If you don't mind, I'd say Odin to stock would be your first troubleshooting step.
Don't forget, internal SD gets erased when you Odin to stock.
Sent from my SGH-I337 using XDA Premium 4 mobile app
guut13 said:
If you don't mind, I'd say Odin to stock would be your first troubleshooting step.
Don't forget, internal SD gets erased when you Odin to stock.
Sent from my SGH-I337 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Think so huh? I was thinking so...and yeah i know it erases internal memory, ill pull everything off before that and titanium backup apps and blah blah..
What i'd like to know is does Odin to stock blow EVERYTHING out including root and safe strap to where i would have to do that all over again? and i assume there is an Odin to stock for MK2? because i do not want the new update...
jermo said:
Think so huh? I was thinking so...and yeah i know it erases internal memory, ill pull everything off before that and titanium backup apps and blah blah..
What i'd like to know is does Odin to stock blow EVERYTHING out including root and safe strap to where i would have to do that all over again? and i assume there is an Odin to stock for MK2? because i do not want the new update...
Click to expand...
Click to collapse
I think Odin to stock is easier than troubleshooting every issue that you are having. Especially considering you already tried fixing one of them.
Yes. Odin wipes the slate clean. You'd have to root and install safestrap again. In case you don't have it.
mk2 odin... http://forum.xda-developers.com/showthread.php?t=2621279
root for mk2... http://forum.xda-developers.com/showthread.php?t=2565758
guut13 said:
I think Odin to stock is easier than troubleshooting every issue that you are having. Especially considering you already tried fixing one of them.
Yes. Odin wipes the slate clean. You'd have to root and install safestrap again. In case you don't have it.
mk2 odin... http://forum.xda-developers.com/showthread.php?t=2621279
root for mk2... http://forum.xda-developers.com/showthread.php?t=2565758
Click to expand...
Click to collapse
thanks brother! running through the long ridiculous process now
I see you have started the process... But wouldn't doing a FDR first be a simpler first effort? You would still have to restore root and data and apps, but it would be a bit easier and probably fix the problem. Just a thought. Hope all worked out!
I restored my galaxy back to stock with Odin and now I'm getting constant Knox pop ups. Anyone know the fix to make this go away so I can give the phone to my wife to use unrooted?
Thanks in advance for your help
Sent from my iPhone using Tapatalk
Also, if I try and install the Knox app, it says it can't be installed because I previously installed a custom os
Sent from my iPhone using Tapatalk
Last thing, it's showing custom rom in the download screen. It's not showing Knox 0x1. So Knox wasn't tripped.
Sent from my iPhone using Tapatalk
didureboot said:
I restored my galaxy back to stock with Odin and now I'm getting constant Knox pop ups. Anyone know the fix to make this go away so I can give the phone to my wife to use unrooted?
Thanks in advance for your help
Sent from my iPhone using Tapatalk
Click to expand...
Click to collapse
There's a real easy fix if you're rooted...
What does the pop-up even say, you never explained
I think I solved the problem. I changed the file system to art and then back to dalvik. The lock and custom are gone on boot up now. Now I just gotta figure out why when trying to update, it says that the update service is temporarily unavailable.
Does your baseband and build number match? What did you flash?
I was rooted on NI2. Restored to stock NI2. Had the custom message with the padlock icon on startup. Finally changing to art and back to dalvik made the padlock go away.
T
didureboot said:
I think I solved the problem. I changed the file system to art and then back to dalvik. The lock and custom are gone on boot up now. Now I just gotta figure out why when trying to update, it says that the update service is temporarily unavailable.
Click to expand...
Click to collapse
You could Odin the build you wanted to update to. Did you connect with kies?
I didn't connect with kies. I used standard Samsung drivers and Odin.
didureboot said:
I didn't connect with kies. I used standard Samsung drivers and Odin.
Click to expand...
Click to collapse
Some people connect to kies to get their updates. Just thought that might be worth trying.
Hadn't thought about that. Will remote into my home computer and get that installed so I can try that this evening. Thanks for the idea.
didureboot said:
Hadn't thought about that. Will remote into my home computer and get that installed so I can try that this evening. Thanks for the idea.
Click to expand...
Click to collapse
Here is someone with the same problem. Seems like their answer was to flash the stock firmware.
http://forums.androidcentral.com/sa...ollipop-not-working-out-help.html#post4223525