Does anyone know which is newer, and what changed between the two?
I have XXUAME2, and I've updated my firmware through Kies. I don't remember what I had before. This one must be newer.
Haven't noticed any change, apart from the blue default background in the wallpapers is now a bit darker without the sun flare. I might've noticed a few very minor things in the settings, though I don't remember what they were.
Well I was on XXUAMDC when I first got my handset, and flashed XXUAMDN via Odin when getting root access. I found it removed any carrier branding and fixed a bug with the standard launcher not allowing sorting apps in folders properly. Just wondering if XXUAME2 is newer and fixes anything else.
StuartTheFish said:
Well I was on XXUAMDC when I first got my handset, and flashed XXUAMDN via Odin when getting root access. I found it removed any carrier branding and fixed a bug with the standard launcher not allowing sorting apps in folders properly. Just wondering if XXUAME2 is newer and fixes anything else.
Click to expand...
Click to collapse
I'll tell you a sad story about XXUAME2.
I rooted my phone a few weeks after I got it, everything worked fine. Then I saw the firmware update in Kies, sure I'll download! I already knew updating stock firmware would remove root, but I could always flash it again. So after I updated my firmware, I flashed root again. This time the phone couldn't recognise the superuser app, and kept alerting that there was a threat (meaning the superuser app) every 5 minutes but root still worked. So I removed superuser completely. The threat messages didn't stop, though. I flashed a clean stock ROM, everything was fine.
Until, an ancient evil awakens! (not really ancient, but...) My Group Play app started acting weirdly. It was constantly 50-70% of my battery drain, even above the screen, on my battery page. I freezed the app and hoped for the best, but it didn't work. I couldn't remove it because my root messed up. BetterBatteryStats didn't recognise anything odd. I asked XDA, but my thread only got 1 answer telling me to look for updates, and none were to be found. Google didn't tell me anything. So I gave up, and did a factory reset. I didn't really mind, I got the phone back running and looking the same in one evening, it's not as if I had years worth of stuff in it yet. This was 2 days ago, and everything seems to be pretty much normal.
I probably messed up somewhere, but thought I'd still write a cautionary tale about updating firmware while rooted. As I mentioned, probably nothing of importance was updated, so it would be a little safer to not update. You won't miss out.
Tozenator said:
I'll tell you a sad story about XXUAME2.
I rooted my phone a few weeks after I got it, everything worked fine. Then I saw the firmware update in Kies, sure I'll download! I already knew updating stock firmware would remove root, but I could always flash it again. So after I updated my firmware, I flashed root again. This time the phone couldn't recognise the superuser app, and kept alerting that there was a threat (meaning the superuser app) every 5 minutes but root still worked. So I removed superuser completely. The threat messages didn't stop, though. I flashed a clean stock ROM, everything was fine.
Until, an ancient evil awakens! (not really ancient, but...) My Group Play app started acting weirdly. It was constantly 50-70% of my battery drain, even above the screen, on my battery page. I freezed the app and hoped for the best, but it didn't work. I couldn't remove it because my root messed up. BetterBatteryStats didn't recognise anything odd. I asked XDA, but my thread only got 1 answer telling me to look for updates, and none were to be found. Google didn't tell me anything. So I gave up, and did a factory reset. I didn't really mind, I got the phone back running and looking the same in one evening, it's not as if I had years worth of stuff in it yet. This was 2 days ago, and everything seems to be pretty much normal.
I probably messed up somewhere, but thought I'd still write a cautionary tale about updating firmware while rooted. As I mentioned, probably nothing of importance was updated, so it would be a little safer to not update. You won't miss out.
Click to expand...
Click to collapse
The reason for that is chainfire's root method doesn't work for newer versions (or should I say didn't, apparently it does now). The newer kernel didn't allow root access, making the su binary appear to be missing. The error messages are also normal on newer versions, since it detects something is trying to get root access. To get around the missing binary issue, you can use djembey's modified version of getting root instead, which afaik installs the older kernel again so it can actually get root. Then to get rid of the repeated error messages, you have to disable KNOX. Again, it says how in djembey's root thread.
XXUAMDN is one of the newer versions which didn't work via chainfire's method, yet I have root access with no issues after following djembey's thread. Might be worth a look to get yours sorted.
StuartTheFish said:
The reason for that is chainfire's root method doesn't work for newer versions (or should I say didn't, apparently it does now). The newer kernel didn't allow root access, making the su binary appear to be missing. The error messages are also normal on newer versions, since it detects something is trying to get root access. To get around the missing binary issue, you can use djembey's modified version of getting root instead, which afaik installs the older kernel again so it can actually get root. Then to get rid of the repeated error messages, you have to disable KNOX. Again, it says how in djembey's root thread.
XXUAMDN is one of the newer versions which didn't work via chainfire's method, yet I have root access with no issues after following djembey's thread. Might be worth a look to get yours sorted.
Click to expand...
Click to collapse
Interesting, very interesting. I might look into rooting one more time, then. Thanks!
Funny how you helped me instead of the other way around. Thanks again, I hope more people notice your thread and maybe you'll get your answer!
where is this new firmware xxuamdn, havent found anything about it..
im having camera, battery drain, slowness issuess still hope it fixes..
Sent from my GT-I9500 using xda app-developers app
I have none of those issues, but never did even on the older version. All I did was Google for galaxy s4 update and I found a download link for it along with Odin. But there's also XXUAME2 out there and I don't know which one I'd be better having. Unless the only difference is the radio depending on where in the world you are?
My G2 keeps randomly rebooting. Sometimes it will reboot without me doing anything to it, and sometimes it will reboot when I try to unlock it. The only thing I have done to the phone is root with the method in these forums. I haven't installed any non-market apps or anything. Since the root method was kind of suspicious, I suspect that is the problem. How do I un-root? I have tried the "back to stock" method, but nothing happened after I completed that. How can I resolve this issue? Does anybody else have this problem?
Edit: Even if rooting was not the cause of my problems I still need to un-root in case I need to take the phone back to Verizon.
paw123 said:
My G2 keeps randomly rebooting. Sometimes it will reboot without me doing anything to it, and sometimes it will reboot when I try to unlock it. The only thing I have done to the phone is root with the method in these forums. I haven't installed any non-market apps or anything. Since the root method was kind of suspicious, I suspect that is the problem. How do I un-root? I have tried the "back to stock" method, but nothing happened after I completed that. How can I resolve this issue? Does anybody else have this problem?
Edit: Even if rooting was not the cause of my problems I still need to un-root in case I need to take the phone back to Verizon.
Click to expand...
Click to collapse
I read something about beta chrome causing reboots...not sure if your using a beta version of chrome.
emplox said:
I read something about beta chrome causing reboots...not sure if your using a beta version of chrome.
Click to expand...
Click to collapse
Hmm I do not think that I have a beta version of chrome, but just in case, I disabled Chrome and installed Firefox instead. I will update if that appears to fix the problem.
Edit: Nope. The problem still exists.
Also, I managed to unroot using super SU. The problem is that it still says that my phone is rooted when I go to about>status.
I had the same problem today. It happened when I got a text. It rebooted like 3 times one after another. Then it just stopped. Weird.....
Anyone any ideas? I have the T-Mobile version. NOT ROOTED
Mine just shut off entirely no reboot I had to power it on. On the T-Mobile version
Sent from my LG-D801 using Tapatalk 2
Holy crap....mine just went into a reboot cycle for like 20 times. It happened while I was taking a photo. It also happened when I tried to unlock my device. Not very pleased right now. never had a single reboot on my gs4
Mines shut off like 5 times today no reboot it just shuts down lol so T-Mobile is sending me a brand new one and if that has problems to I may go back to my nexus 4 and wait for the nexus 5 or something this phone is amazing in every way except when I go to unlock and it is ******* shut down ugh
Sent from my LG-D801 using Tapatalk 2
I have a nexus 10 and was running 4.3 when I downloaded Wug's Nexus Root Toolkit v1.7.2. I loaded drivers using driver solution #2 (solution #1 didn't work for some reason). I followed all instructions to unlock and root w/ custom recovery. I got an error message from the superuser app about an SU binary missing. I researched and found a file to flash to fix this. But the device isn't working properly. It freezes and reboots after 3-4 actions. Any actions cause the problem, whether it's going into settings and changing something, moving a widget, or trying to open an app. I can't even get the file onto the device to flash. So I flash stock and unroot and re-lock (all using Wug). The device has the same problem as before... I can't do more than 3-4 things before it freezes and reboots. I never had this problem before I unlocked and rooted. Has anyone run into this? I've searched for a while and can't seem to find a similar thread, and I apologize if there is was somewhere that I couldn't find. I just want my tablet back.
Hello,
I've had my S5 for a few months now and I've rooted it with CF Auto Root.
All was well untill a few days ago when my phone suddenly crashed, rebooted and wouldn't properly turn on again.
All apps were crashing, and after clicking 'OK' on the notifications I had a black screen and that was it.
I cleared all data and did a factory reset through recovery, now all is well.
But today it happend again, and of course, the factory reset clears it up but if I have to do this every week I'll go mental..
So, does anyone else have this or have had this? If so, please help!
It's the G900F, 5.0 Lollipop with CLauncher installed (if this makes a difference).
Baseband: G900FXXU1BOB7
Buildnumber: LRX21T.G900FXXU1BOB7
Hope to hear from you guys soon!
im getting this too, so i make constant backups using TWRP.
unfortunately that is not solving the root cause.
It's really weird, all I did last time was change the brightness..
Sent from my SM-G900F using XDA Free mobile app
I don't know if it is the same problem, afeter the reboot i have no problem, but since a few weeks my phone is rebooting every day or two. In every case i was doing something different. Know i believe is supersu or root it self because after each reboot i must autorize root permission again.
Hello there all, for the past few hours I've been attempting to root my AT&T Samsung Galaxy S7 Edge (SAMSUNG-SM-G935A). I have had several issues with this process that I am going to detail below, any and help is very, very appreciated.
I believe I have tried this four to five times, to no avail, and each time it has gotten somewhat better I believe.
The first time, I got through the process of using ODIN correctly, it displayed me with the PASS graphic and I continued onward. I went on to the Fast Boot step where I attempted to install SuperSU and it looked like it had worked to me, but this was my first attempt so that honestly doesn't mean much. Anyway, I opened up my phone, SuperSU was not there, and I used the Root Checker. The Root Checker told me it hadn't installed correctly. I pondered for a bit as to what I should do and ran the process again from the beginning. However, the second time I swapped to a better USB port on my PC and there was a difference in the performance of Fast Boot, and SuperSU had installed. I went to my Root Checker, and it again told me that there was no root. I believe I tried once more, I then Factory Reset my device. After I did this, I went through the same process again, following along perfectly to text directions and video tutorials and it installed SuperSU, but no root was there.
I believe I may have done it once or twice since the Factory Reset. Another thing I would like to note about this process was that from the very beginning it has given me the "symptoms of a root". By this I mean the lag, different icons in the carrier bar up top, and possibly more. One other thing I noticed was that even when I had Factory Reset my device, it still gave me the icon on my start up screen. The icon that shows the unlocked lock and says "custom" beneath it.
As I said in the beginning, any and all help is greatly appreciated. Thank you all in advance!