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?
Related
Hello all,
I am usually a reader of this forum, first time post. I have done a search on this but I can't get it to install.
My current phone is running Froyo 2.2.1 system version 2.3.340. I have rooted it with the Z4mod root version 1.3.0.
Now, when I saw the update come down I uninstalled all my root applications and removed my root from my phone. It downloaded in no time flat. About 11 minutes yesterday morning at 9:49AM. (first attempt) And then I started the install and it shut down correctly and turned back on. When it turned back on it did what it was supposed to, had the unbox with android icon. The load bar gets to about 35% then the unbox changes to the triangle with the ! in the middle. Then it boots up Froyo and states the install failed. I attempted about 5 more times then said lets see what verizon says. This was probably the worst thing to do cause they did jack. The store I went to had 25 bricked droid X's yesterday. I was the only one to just have it fail and Froyo to work correctly. To quickly shorten this story they refused to assist in installing Gingerbread.
Any Ideas on getting it installed?
Try wiping data through stock recovery and if that doesn't work, you could try an SBF
Thank you for info. I ended up SBF'ing the phone. Says I need to re-activate the phone because there is a blue triangle next to the signal bars.
I know this is probably a repeated question but how do i re-activate the phone. Do I need to take it to Verizon?!
NVM, figured it out.
same thing happened to me. however i did not remove my z4root on froyo. install failed. did not try sbf, was hoping i wouldn't have to.
biggest reason ive found thus far amongst several different threads/ and friends with droids, root really didnt have much to do with it, as long as you were unrooted again the update went well, bloatware seemed to be the issue. myself i had uninstalled a lot of dumb memory eating stuff while i was on froyo such as the nfl and nfs games, blockbuster app so on, when i pulled the update originally it didnt detect that so it fubared me on getting the ota update. sbf the way to go, im so in love with my DX for being idiot proof atm i could dance lol
Wtf got the ota update and its starts all good but then it hangs a yellow ! appears.. what can i do? i even did a factory reset i only was rooted and i took care of that.
zero313 said:
Wtf got the ota update and its starts all good but then it hangs a yellow ! appears.. what can i do? i even did a factory reset i only was rooted and i took care of that.
Click to expand...
Click to collapse
at least you are getting something OTA
Ditto
Unfortunately, I get the same thing. I was rooted, but I unrooted (not quite as thoroughly as you did, as I only used the "Unroot" option, but we got the same results). Wonder if it is something wrong with the update...
seanfrisbey said:
Unfortunately, I get the same thing. I was rooted, but I unrooted (not quite as thoroughly as you did, as I only used the "Unroot" option, but we got the same results). Wonder if it is something wrong with the update...
Click to expand...
Click to collapse
Did you change ANYTHING when rooted? Did you freeze, rename, modify or delete ANY of the files in the original ROM in any way, shape or form?
Same thing here
When I bought this device 3 weeks ago, I rooted it with z4root. Not too long after an update disabled z4root on the tablet.
I thought no big deal, but then today comes and I the OTA update won't work.
Anyone more experienced than me have any ideas of how to get this update applied properly?
Me too. Update failed to install. Not sure why. I have also tried unrooting.
FloatingFatMan said:
Did you change ANYTHING when rooted? Did you freeze, rename, modify or delete ANY of the files in the original ROM in any way, shape or form?
Click to expand...
Click to collapse
I'm confused, if I froze an application, didn't unfreeze it but did a factory reset...wouldn't that resolve the issue?
ok so i woke up this morning and my a500 notified me the there was an update available so as you can imagine I was very happy to finally have this, so i updated and when it was done it said update successuful but when I checked it still said 3.01......WTF
Not rooted ever..
Those interested in getting back their OTA, properly backing up their original ROMS or restoring them, please follow the tutorials in this thread:
Going back to stock TUTORIAL
Be helpful and provide your firmware if you have a backup so we can build a database for those who don't.
Be sure to report what is working and what is not working for you once you've tried the tutorials!
Unlike the 14 threads on these matter I take the responsibility as OP to upgrade my original post as firmwares and new info becomes available.
Let's create a focused troubleshooting and tutorial thread,
Thanks.
I'm rooted via gingerbreak and the update worked fine while still rooted. It did break root. Just had to re-apply gingerbreak and all is good, back to root with latest update.
gingerbreak worked with official 3.1 ?
it didn't work with 'leaked' 3.1 ?
OTA
Ok after long night and hours of research i found out a lot.
1 if you have modded ad hoc in wpa_supplicant file recover the original file
2 if you have modded the phone.apk and telephoneyprovider.apk to save battery this is the reason why you won't get the update.
i put these files back and instantly got an update, i mean the exact second i set those back
i can't believe this my updates keep failing to install. FING POS i tried everything, factory reset
i have tried everything, even factory reset, it fails while installing after reboot
acer support are a bunch of retards, they don't even know they sell tablets????????
need help i can't upgrade, it fails every time
does anyone know where the install logs are
the log is \cache\recovery\last-log
Oklahoma City, OK noon CST
First attempt failed:
Changed the wpa_supplicant back to original and all went smooth the second time
I never changed anything and it failed.
**Edit: I rebooted my devices and left it completely alone after unzip and it rebooted into recovery mode and seems to be installing **
I had the same problem, It was pretty disheartening.... but I unrooted my device, re-booted and tried again and SUCCESS!!!
But now I can't get it to re-root using gingerbreak... HELP!
SUCCESS!
Ok. I got OTA update 4.010.08 (122.71 MB) this morning. It failed.
So I unrooted my device. Re-started it and tried again... SUCCESS!
I tried using Gingerbreak to root it again. FAIL!
So I used this: http://forum.xda-developers.com/showthread.php?t=1138228
SUCCESS!
Hope this helps those of you who are having problems.
No need to unroot nor go to stock.
I had the same issues. Then I simply used Acer Recovery to install stock recovery and everything worked fine.
Ceger
Acer Recovery?
Did Acer Recovery come with the tablet?
I tried the update numerous times over the last 4 days. Most of the time the download would fail, which I put down to my slow internet connection and overloaded Acer servers. But about 5 times it would finish downloading and then error out on install with a message about the update being invalid. I tried rebooting several times during this process. I have never rooted the tablet and only have a few apps installed as it was a recent purchase.
Finally it worked when I ejected the external SD card and rebooted. It may be a coincidence, but anyone else who gets the "invalid update" warning during install on an unrooted device may wish to try this prior to the download/install.
Alright so here's the thing.
I just got a Galaxy Gear 2 Neo. I installed the Gear Manager App on my phone, and verified the Gear is the correct one. After that, the phone proceeds briefly to download some drivers or something I presume, and then the app "bounces". It just keeps opening and FC'ing, and repeating over and over. I have tried rebooting my phone, reinstalling the app. Disabling the bluetooth, turning off and on and restarting the watch.
I am beginning to think that I am going to have to return to stock S5. I still have the Mar 31st build and all original infos related to the launch. When I initially rooted, I removed a TON of crap from the phone and things I thought I would never use according to the guides that were released by other users.
I guess my question is, what am I going to have to do? I want to keep rooted as x-posed and xtether have been a lifesaver! If I have to odin back to stock, with the Mar 31st build, would I still be able to Re-root and return things to how they are now with no issues?
I am sure a lot of you, if you've read this far are like "is this guy on crack?" I am not all TOO knowledgeable with rooting, but I have successfully done it twice, and I need to push out of my bubble of fear about screwing up my device! It's my life-line to work.
~Kevin
kprice8 said:
Alright so here's the thing.
I just got a Galaxy Gear 2 Neo. I installed the Gear Manager App on my phone, and verified the Gear is the correct one. After that, the phone proceeds briefly to download some drivers or something I presume, and then the app "bounces". It just keeps opening and FC'ing, and repeating over and over. I have tried rebooting my phone, reinstalling the app. Disabling the bluetooth, turning off and on and restarting the watch.
I am beginning to think that I am going to have to return to stock S5. I still have the Mar 31st build and all original infos related to the launch. When I initially rooted, I removed a TON of crap from the phone and things I thought I would never use according to the guides that were released by other users.
I guess my question is, what am I going to have to do? I want to keep rooted as x-posed and xtether have been a lifesaver! If I have to odin back to stock, with the Mar 31st build, would I still be able to Re-root and return things to how they are now with no issues?
I am sure a lot of you, if you've read this far are like "is this guy on crack?" I am not all TOO knowledgeable with rooting, but I have successfully done it twice, and I need to push out of my bubble of fear about screwing up my device! It's my life-line to work.
~Kevin
Click to expand...
Click to collapse
Once you odin back to stock NI2 and re-root you can flash this in safestrap to get your wifi tether without having to use xposed. As for the rest of your questions I think I answered them in the other thread. Easy to follow directions to root NI2 are there as well in the OP. We do have the option to flash backwards with the firmware so far.
Thank you for the reply Misterxtc, I am sorry for the delay in reply. I managed to get the gear to connect, after watching it FC and re-open 20 times, my techie buddy put one finger on it, and it worked. Cheeky bastard. Anyhow. I replied to your other post.
Thanks again.
Hi guys,
Have just spent the last couple of hours trying to research this but still not quite sure what's the best (safest!!) way of upgrading to lollipop on my SM-910G. I am rooted and currently on 4.4.4 and when I try to do an OTA update, I get the msg "The operating system has been modified in an unauthorised way.... etc etc"
When I connect via Kies, I get a pop up msg telling me that lollipop is available however when I try to update it tells me that I have to be unrooted. I read an article where some guy messed up his rooted S4 while trying to update via Kies. Can't afford for that to happen on my phone, I've backed up all my apps and data via Titanium Backup but now need to know what the safest way is to upgrade and keep all my settings etc.
I've downloaded the right 5.0 ROM (N910GDTU1BOC5_N910GXSA1BOC5_XSA.zip) for my model - am I correct to say that if I flash via Odin, I will lose all my apps and settings (and root)?
If I want to update and keep all my settings, am I safe to unroot via SuperSU, then update via Kies? I've read about how unrooting via SuperSU isn't really a complete unroot?
At the end of the day unless I'm 100% certain I will probably stay on 4.4.4 since there has been some horror stories with battery drain and stuff on 5.0
Has anyone been in a similar situation?
highon2str said:
Hi guys,
Have just spent the last couple of hours trying to research this but still not quite sure what's the best (safest!!) way of upgrading to lollipop on my SM-910G. I am rooted and currently on 4.4.4 and when I try to do an OTA update, I get the msg "The operating system has been modified in an unauthorised way.... etc etc"
When I connect via Kies, I get a pop up msg telling me that lollipop is available however when I try to update it tells me that I have to be unrooted. I read an article where some guy messed up his rooted S4 while trying to update via Kies. Can't afford for that to happen on my phone, I've backed up all my apps and data via Titanium Backup but now need to know what the safest way is to upgrade and keep all my settings etc.
I've downloaded the right 5.0 ROM (N910GDTU1BOC5_N910GXSA1BOC5_XSA.zip) for my model - am I correct to say that if I flash via Odin, I will lose all my apps and settings (and root)?
If I want to update and keep all my settings, am I safe to unroot via SuperSU, then update via Kies? I've read about how unrooting via SuperSU isn't really a complete unroot?
At the end of the day unless I'm 100% certain I will probably stay on 4.4.4 since there has been some horror stories with battery drain and stuff on 5.0
Click to expand...
Click to collapse
highon2str said:
Hi guys,
Have just spent the last couple of hours trying to research this but still not quite sure what's the best (safest!!) way of upgrading to lollipop on my SM-910G. I am rooted and currently on 4.4.4 and when I try to do an OTA update, I get the msg "The operating system has been modified in an unauthorised way.... etc etc"
When I connect via Kies, I get a pop up msg telling me that lollipop is available however when I try to update it tells me that I have to be unrooted. I read an article where some guy messed up his rooted S4 while trying to update via Kies. Can't afford for that to happen on my phone, I've backed up all my apps and data via Titanium Backup but now need to know what the safest way is to upgrade and keep all my settings etc.
I've downloaded the right 5.0 ROM (N910GDTU1BOC5_N910GXSA1BOC5_XSA.zip) for my model - am I correct to say that if I flash via Odin, I will lose all my apps and settings (and root)?
If I want to update and keep all my settings, am I safe to unroot via SuperSU, then update via Kies? I've read about how unrooting via SuperSU isn't really a complete unroot?
At the end of the day unless I'm 100% certain I will probably stay on 4.4.4 since there has been some horror stories with battery drain and stuff on 5.0
Click to expand...
Click to collapse
hi
Just a few points ...First if you " dirty flash" official stock Rom with Odin, then you will lose root ( so to me there is no need to unroot first ) However you do not loose any 3 rd party apps or settings . Also i never use Kies as my personal experience is that it is a waist of time .Regarding Lollipop well i have flashed several newer " version"/changelog/dated of Lollipop 5.0.1 over the past months and all of them have been good to me...( ..overall.) No real battery drain ,no lag ( only recent button and one " Samsung bug in the setting " Accessibilty" .
All my "problems " on Lollipop, on and off, was caused by 3 rd party apps
eg.Past few days i had suddenly random reboots over and over .i reflashed Lollipol ,i factory reset ,but the random reboots continued .
i then started to install all my +_ 162 ..?? apps one by one and checked
Eventually found my culprit ..'Greenify " (the experimental paid ,bolt on package, which is meant mostly for Xposed module with few functions you can also use without Xposed eg "don't remove Notifications " and Greenify system apps l)
After using Greenify for months with no issues it suddenly started giving problems .
So i could have given Lollipop the blame for my woes but i did not .
Yes I do believe Lollipop has issues ,but overall i cannot complain .
yes ,Titanuim is the way to go .
Also i "unrooted " via SuperUser app once, no problem at all, but then why do this if you just flash over it and root is gone
Bottom line ,
you can be "stuck " on Android v4.4.4 hoping and waiting .......?
or faceup to Lollipop ?
its your choice ?
good luck
Hey willcor thanks for the reply! Good to hear your experiences with this. Interestingly I've had a similar problem of sluggishness, lag and random rebooting (multiple times a day) on my Note 4 running kitkat. This went on for about 2 or 3 days. Tried installing some recently installed apps thinking it might have caused it, and now it seems it's fixed itself, I think??
Even pulling the battery and restarting often took ages to boot. Took my 128GB SD card out and tried to boot thinking maybe it was the card but it still lagged and restarted by itself. Like I said it seems ok now and has been ok for the last few days, but now that you mention Greenify, I have that installed too along with a few exposed modules. This rebooting problem is what motivated me to think about upgrading to lollipop to see if it would fix it.
Going by what you said, if I am not going to lose apps, data and settings, then I might flash to lollipop, then re-root. Sounds like the way to go. Maybe...
willcor said:
hi
Just a few points ...First if you " dirty flash" official stock Rom with Odin, then you will lose root ( so to me there is no need to unroot first ) However you do not loose any 3 rd party apps or settings . Also i never use Kies as my personal experience is that it is a waist of time .Regarding Lollipop well i have flashed several newer " version"/changelog/dated of Lollipop 5.0.1 over the past months and all of them have been good to me...( ..overall.) No real battery drain ,no lag ( only recent button and one " Samsung bug in the setting " Accessibilty" .
All my "problems " on Lollipop, on and off, was caused by 3 rd party apps
eg.Past few days i had suddenly random reboots over and over .i reflashed Lollipol ,i factory reset ,but the random reboots continued .
i then started to install all my +_ 162 ..?? apps one by one and checked
Eventually found my culprit ..'Greenify " (the experimental paid ,bolt on package, which is meant mostly for Xposed module with few functions you can also use without Xposed eg "don't remove Notifications " and Greenify system apps l)
After using Greenify for months with no issues it suddenly started giving problems .
So i could have given Lollipop the blame for my woes but i did not .
Yes I do believe Lollipop has issues ,but overall i cannot complain .
yes ,Titanuim is the way to go .
Also i "unrooted " via SuperUser app once, no problem at all, but then why do this if you just flash over it and root is gone
Bottom line ,
you can be "stuck " on Android v4.4.4 hoping and waiting .......?
or faceup to Lollipop ?
its your choice ?
good luck
Click to expand...
Click to collapse
highon2str said:
Hey willcor thanks for the reply! Good to hear your experiences with this. Interestingly I've had a similar problem of sluggishness, lag and random rebooting (multiple times a day) on my Note 4 running kitkat. This went on for about 2 or 3 days. Tried installing some recently installed apps thinking it might have caused it, and now it seems it's fixed itself, I think??
Even pulling the battery and restarting often took ages to boot. Took my 128GB SD card out and tried to boot thinking maybe it was the card but it still lagged and restarted by itself. Like I said it seems ok now and has been ok for the last few days, but now that you mention Greenify, I have that installed too along with a few exposed modules. This rebooting problem is what motivated me to think about upgrading to lollipop to see if it would fix it.
Going by what you said, if I am not going to lose apps, data and settings, then I might flash to lollipop, then re-root. Sounds like the way to go. Maybe...
Click to expand...
Click to collapse
hi,
Just a quick remark. When i was on Android v4.4.4, most of my issues eg. Private mode S HEALTH... (yes i know there was quick fixes /patches , that you could apply) Play store not installing apps, lags from time to time etc was caused by Xposed Framework. As far as i can remember Xposed was never optimise for Android v4.4.4? As "good" as Xposed was, it gave me "terrible headache /problems" on my Note 4....... even after uninstalling Xposed it broke some apps functionality! (This is a fact for me) . but yet, on all my other devices, no issues ! As stated in my previous post, that Lollipop experience, has been over all, very good for me.,(I have accepted the few bugs, that comes with every software update be it Android v4.4.4 or Android v 5.0.1.)
Lollipop also enabled me to use other apps /features eg Network Toggle app (change network only to LTE or LTE/3G or 3G only.. root required)
Bottom line
for me is.... yes, Lollipop has issues, but most of mine was caused by 3rd party apps not optimised 100% , work smoothly on Lollipop.
good luck
..............................
post note....
Titanium, i forgot, you might have some minor issues at first. Titanium could not find backup folder on my ext sd same as on Android v4.4.4) , so i used NextApp Sdfix (Play store, free app) Titanium, then was able to locate back ups. Again yesterday, i factory reset my device because of a Nova launcher, toggle notification issue and because i also wanted to for a period of time.
Titanium could not write and above NextApp Sdfix said i had no write premisson after running NextApp. i formatted my ext sd on laptop and NextApp did its work and Titanium working 100%
Just thought to make you aware if issue arrived.
Thanks... I forget all these root features have to be redone. I've also given extsd access on kitkat after rooting. Will have to do it all over again I guess!
Ok just a quick update. Flashed to 5.0.1 with Odin and rooted with CFautoroot. Everything seems to be ok apart from after rooting and rebooting, I got a "could not do normal boot" msg, saying that the phone was in download mode and not to disconnect the target. I pulled the batt and booted up normally ok. Checked in Titanium and found root access ok, activated write to SD and all seems normal.
Things seem a bit sluggish with lollipop, so I uninstalled xposed (which now won't work on this version), greenify and some other apps, and booted into recovery to wipe cache partition. When it was done wiping the cache and said to reboot, I got the same "could not do normal boot" msg. Once again I pulled the battery and it booted ok.
Not sure what has happened or if anything is affected - should I re-flash 5.0 with Odin and re-root all over again?
highon2str said:
Ok just a quick update. Flashed to 5.0.1 with Odin and rooted with CFautoroot. Everything seems to be ok apart from after rooting and rebooting, I got a "could not do normal boot" msg, saying that the phone was in download mode and not to disconnect the target. I pulled the batt and booted up normally ok. Checked in Titanium and found root access ok, activated write to SD and all seems normal.
Things seem a bit sluggish with lollipop, so I uninstalled xposed (which now won't work on this version), greenify and some other apps, and booted into recovery to wipe cache partition. When it was done wiping the cache and said to reboot, I got the same "could not do normal boot" msg. Once again I pulled the battery and it booted ok.
Not sure what has happened or if anything is affected - should I re-flash 5.0 with Odin and re-root all over again?[/QUOTE
hi,
i am sure i read somewhere about.re: your remark, when you rooted and got a msg, with
"could not do a normal reboot... I am sure it could be ( @ Chainfire,) Cf autoroot website not sure.?
I would have search for a answer /reason!/ explanation Then i would afterwards, reflash Rom. (depends on you)
Just a quick question.... At what stage did you uninstall Xposed....? before /after flashing etc. i stated before that i found Xposed "broke /caused issues after i uninstalling it. (facts about two or three times it happened , in past )
Also i had no problem in using Greenify again (i have re installed it) its just the donation /paid / experimental package i am a bit hesitant with.
good luck
Click to expand...
Click to collapse
Hey guys, I have since reflashed and rerooted and now seem to have less problems, although the phone is still sluggish, randomly locking up and restarting , and sometimes restarting to the green android "could not do normal boot" screen.
Question now is, can I boot into stock recovery to do a factory reset? I've done some research but the views seem conflicting. Is this recommended, will I be stuck in a bootloop and will I still be rooted after the reset?
I never did a factory reset when flashing from 4.4 to 5.0.1 so I'm hoping this will fix the issues I've got now.
Sent from my SM-N910G using Tapatalk
Anyone?
Sent from my SM-N910G using Tapatalk
I bought an unlocked AT&T S4 a few months ago. It had Lollipop on it when I got it. I rooted it with Kingoroot and, Kingoroot's idiosyncrasies notwithstanding, everything worked fine. I was able to tweak some apps' config files, give myself 16 million color bombs in Candy Crush, and things like that.
Then I flew too close to the Sun - TWRP, Cyanogenmod (or whatever it's called), etc. A few misteps found me with a boot loop problem. "Software not athorized by AT&T..." was all she wrote.
I started reading some of the forums, played a bit with Kies, installed Odin, and finally got the phone to start up. Problem is I'm now running Jellybean with no Wi-Fi. The phone works fine otherwise and Smart Switch reinstalled all of my apps ( I wasn't expecting that). I rooted it using saferoot (pretty cool!). But I'd like to go back to Lollipop and get my Wi-Fi back, though I'd settle for Jellybean if I can get Wi-Fi working, if that's the best I can do.
Can somebody point me in the right direction?
Sounds like your phone has a locked bootloader which means you cannot install TWRP, or CWM,
Have you checked here for a solution: http://forum.xda-developers.com/showthread.php?t=2616221 ?
audit13 said:
Sounds like your phone has a locked bootloader which means you cannot install TWRP, or CWM,
Have you checked here for a solution: http://forum.xda-developers.com/showthread.php?t=2616221 ?
Click to expand...
Click to collapse
Nailed it! After following that link and finding the common elements in a few others, I'm back on Lollipop, Wi-Fi is working, and I've freed up probably half of my device's memory! But I need more!!!
Thank you.