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
Related
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?
Hi guys
I'm using samsung galaxy S5 (4.4.2) and recently upgraded to 5.0 using custom rom which I found here. It was working just great. I created 2 Nandroid using TWRP. One after a fresh installation another one after restoring my file contents from Helium and Titanium backup..
However something went wrong and i decided to restore my nandroid backup to revert back my changes. To my surprise both nandroid backup failed. I got a success message (using recovery mode) however when i reboot my phone im getting tons of messages like "System failed to start" "process failed to start" wait or press ok.
When I reflash the custom rom, it works fine, however i couldnt recover my system from nandroid backup.
I repeated several times but both nandroid gave me this same error. I even tried fixing permissions but no use. Then I used odin to flash a stock rom (BOA3) and rooted that using TWRP and most recent SU binaries. Its working great now, however I just wanted to know what is the best method to take a nandroid backup now? I'm afraid TWRP will bail out on me once again.
All the while I used CWM and it was great however 5.0 requires latest binaries and only can be rooted via TRWP recovery. Any suggestion? I just want to take a complete nandroid backup and save it in case if something goes wrong.
Thanks
sam20e said:
when i reboot my phone im getting tons of messages like "System failed to start" "process failed to start" wait or press ok.
Click to expand...
Click to collapse
I'm being plagued by this problem since I updated, flashing stock Lollipop using odin.
The problem first appeared after trying to restore my app+data using Titanium.
I went back to the beginning and flashed again but my phone is still unstable and I still occasionally get the '"System failed to start" "process failed to start" wait or press ok' issue that you have. A reboot generally sorts it out but the update has made my phone very unstable.
I also have big problems entering recovery and download modes using the buttons.
Cleaning my cache/davlik hasn't solved it either.
Hopefully someone can help us.
Anyone?
Got "Reactivation Lock" disabled?
Settings > General > Security
*Detection* said:
Got "Reactivation Lock" disabled?
Settings > General > Security
Click to expand...
Click to collapse
Yes. Thanks for the suggestion though.
Trouble in Galaxy town
Hi, I'll try make myself short.
1) Back when I had an Galaxy S2 i modded it a little bit but I haven't done it at all since then.
2) Now a few years later I got bored/sick of the stock ROM that comes with the S5 so I wanted to install something I knew had a good reputation, Cyanogenmod.
3) Getting a new recovery was an nightmare itself but eventually I got it working and made an backup so I could roll back if needed to.
4) Now, 24 hours of using CM12 I can only say one sentence: "What kind of crap is this?!" It's so unstable it's almost ridiculous. Bluetooth hangs up all the time thus requiring a reboot which leads to most-annoying-thing-ever-#2. The clock resets itself upon EVERY boot which makes WhatsApp go bananas. Doesn't matter if I previously set the time/date manually or let the phone do it automatically. Then there are the random hang ups that occur all the time and one third thing. Hardware acceleration in BS Player doesn't work AT ALL!
5) Said and done I reversed to the back up but oh man the phone wasn't happy about this (yes I made a wipe before recovering the backup). Nearly every basic service malfunctioned and were forcibly shut down. A factory reset made no difference...
6) For some reason I opened KIES and found out that an update with android lollipop was available so I (in a moment of despair) installed that hoping for salvation.
7) The phone boots properly and everything seems to be going wonderful until I realize that my network connection is high on something. Loses connectivity to my provider all the time thus the phone is totally useless.
8) I HAD to have a working phone for work and since no support is given on Sundays from Samsung I again installed CM12 just for the day.
Now to the good part!
9) When trying to recover the backup once again it's gone corrupt! Can't recover so now I'm stuck with buggy-as-h*ll-cyanogemmod12 with no means of reverting.
What-the-actual-****-do-I-do? Been trying to make some sense from the thread "Galaxy S 5 Original Android Development" but I feel so lost. So if someone could point me in the right direction I would be very grateful!
EDIT: What I want is to reverse back to original stock ROM. Screw the bloatware. I just need the phone stable and working!
EDIT2: After some more googeling I've figured out I need a stock ROM with the right CSC. I use a swedish carrier other than 'tre'. Shall I look for ROMs with CSC 'HTS' anyway? Can't find any info about other carriers in sweden.
EDIT3: Now I've found what I think is right on sammobile.com/firmwares/database/ (search query: 'g900f', first hit 'Sweden' CSC 'VDS'). Worried thou as it's Android Lollipop which made my phone go nuts. Can't find the KitKat version on that site...
EDIT4: Found the KitKat version on samsung-updates.com. The download speed is sooooooo slow (~6 hours)! Download limits should be illegal...
Thanks! //R
Good Day Everyone...
I hope you all are fine...
Allow me to explain my story till we hit the big problem that is the hotboot/fastboot...
10 months ago, I bought Samsung Note 4 SM-N910C ... Was switching from Broken screen Note 4... I had a Nandroid backup of it... but while restoring I messed up badly as I wiped the new device IMEI that time... but I managed to find someone to fix the phone and create a backup... Now Why did I change my phone again...? Battery degrading, phone heating and of course from time to another I must restore the IMEI backup as it gets corrupted suddenly and randomly... In addition to the Note 4 Great Offer...
All 3 phones were SM-N910C, however the first 2 came as KitKat 4.4.4 and the latest phone came as Lollipop 5.0.1 ...I didn't really care much as I grabbed the Nandroid and restored it carefully... Everything works great, Until after installing Xposed... softboot / hotboot / fastboot / quickboot whatever you wish to call acts similar to REBOOT but without shutdown... This issue is Critically annoying as I play from time to another with Xposed and rebooting sometimes don't give Xposed enough time to load the modules ... In addition the SIM lock is active at every reboot and the loading TIME...
I took a backup for all my application on Titanium Backup... Preformed a clean Install of Kitkat 4.4.4 ROM on the phone and restored the applications, Hotboot remained the same... I thought perhaps Xposed is the issue... So I went to ADB command ... adb reboot fastboot ... same results ... phone keeps REBOOTING without shutdown...
How Reboot without Shutdown? Do I know the difference between Hotboot & Reboot?
Yes I do know the difference...
a Reboot would go to shutdown animation, reboot to Samsung NOTE 4 then load the BootAnimation followed by its loop till device has loaded, reboot clears all memory and reload everything, Enter SIM Lock and takes time...
a Hotboot would go immediately to BootAnimation then loop while in the background it's just refreshing the Apps and services briefly, no SIM Lock needed, it doesn't take time...
My HOTBOOT is doing same as REBOOT but skipping the Shutdown animation...
So my Question: What is wrong with my Hotboot? Is it Lollipop? Do I need to check something?
I Thank you all for your patience and reading all what I wrote whether you Answered or not...
P.S: Some Xposed apps are acting weird on this phone compared to the 2 previous Note 4 phones...
Dante63 said:
Good Day Everyone...
I hope you all are fine...
Allow me to explain my story till we hit the big problem that is the hotboot/fastboot...
10 months ago, I bought Samsung Note 4 SM-N910C ... Was switching from Broken screen Note 4... I had a Nandroid backup of it... but while restoring I messed up badly as I wiped the new device IMEI that time... but I managed to find someone to fix the phone and create a backup... Now Why did I change my phone again...? Battery degrading, phone heating and of course from time to another I must restore the IMEI backup as it gets corrupted suddenly and randomly... In addition to the Note 4 Great Offer...
All 3 phones were SM-N910C, however the first 2 came as KitKat 4.4.4 and the latest phone came as Lollipop 5.0.1 ...I didn't really care much as I grabbed the Nandroid and restored it carefully... Everything works great, Until after installing Xposed... softboot / hotboot / fastboot / quickboot whatever you wish to call acts similar to REBOOT but without shutdown... This issue is Critically annoying as I play from time to another with Xposed and rebooting sometimes don't give Xposed enough time to load the modules ... In addition the SIM lock is active at every reboot and the loading TIME...
I took a backup for all my application on Titanium Backup... Preformed a clean Install of Kitkat 4.4.4 ROM on the phone and restored the applications, Hotboot remained the same... I thought perhaps Xposed is the issue... So I went to ADB command ... adb reboot fastboot ... same results ... phone keeps REBOOTING without shutdown...
How Reboot without Shutdown? Do I know the difference between Hotboot & Reboot?
Yes I do know the difference...
a Reboot would go to shutdown animation, reboot to Samsung NOTE 4 then load the BootAnimation followed by its loop till device has loaded, reboot clears all memory and reload everything, Enter SIM Lock and takes time...
a Hotboot would go immediately to BootAnimation then loop while in the background it's just refreshing the Apps and services briefly, no SIM Lock needed, it doesn't take time...
My HOTBOOT is doing same as REBOOT but skipping the Shutdown animation...
So my Question: What is wrong with my Hotboot? Is it Lollipop? Do I need to check something?
I Thank you all for your patience and reading all what I wrote whether you Answered or not...
P.S: Some Xposed apps are acting weird on this phone compared to the 2 previous Note 4 phones...
Click to expand...
Click to collapse
Lollipop 5.1.1 fix the "Hotboot" problem, also disable fingerprint (it's the main cause).
Next iteration of update will fix fingerprint problem.
d4rkkn16ht said:
Lollipop 5.1.1 fix the "Hotboot" problem, also disable fingerprint (it's the main cause).
Next iteration of update will fix fingerprint problem.
Click to expand...
Click to collapse
Thank you @d4rkkn16ht for responding...
So I should Flash lollipop 5.1.1 then flash back to kitkat?
I have done many tests for hotboot via trying multipl 4.4.4e apps... 2 apps out of 6 managed to hotboot...
Xposed installer failed...
TWRP manager failed...
APM+ failed...
Fastboot failed...
Simple reboot success...
Root toolbox success...
I have Kitkat 4.4.4 on my phone... Rooted with TWRP recovery and xposed installed... Busybody is present... Selinux enforcing... What more information do I need to provide?
Dante63 said:
Thank you @d4rkkn16ht for responding...
So I should Flash lollipop 5.1.1 then flash back to kitkat?
I have done many tests for hotboot via trying multipl 4.4.4e apps... 2 apps out of 6 managed to hotboot...
Xposed installer failed...
TWRP manager failed...
APM+ failed...
Fastboot failed...
Simple reboot success...
Root toolbox success...
I have Kitkat 4.4.4 on my phone... Rooted with TWRP recovery and xposed installed... Busybody is present... Selinux enforcing... What more information do I need to provide?
Click to expand...
Click to collapse
XPOSED is still problematic on TW odexed Lollipop ROM, so it is not recommended to install EXPOSED on your Note 4 with Lollipop.
Fingerprint causing many problem on Lollipop 5.0.1 - 5.1.1 (sudden lag, random hotboot, random apps kill), so disable fingerprint while you are on Lollipop.
Some said that COI update (5.1.1) fix fingerprint bug.
d4rkkn16ht said:
XPOSED is still problematic on TW odexed Lollipop ROM, so it is not recommended to install EXPOSED on your Note 4 with Lollipop.
Fingerprint causing many problem on Lollipop 5.0.1 - 5.1.1 (sudden lag, random hotboot, random apps kill), so disable fingerprint while you are on Lollipop.
Some said that COI update (5.1.1) fix fingerprint bug.
Click to expand...
Click to collapse
I am really getting lost...
You talk about Lollipop while I have downgraded to Kitkat... In other words, I have kitkat now on my phone... With hotboot problem...
Dante63 said:
I am really getting lost...
You talk about Lollipop while I have downgraded to Kitkat... In other words, I have kitkat now on my phone... With hotboot problem...
Click to expand...
Click to collapse
Upgrade to lollipop then, but you can't install Xposed on stock ROM
d4rkkn16ht said:
Upgrade to lollipop then, but you can't install Xposed on stock ROM
Click to expand...
Click to collapse
By why?
My two previous phones had KitKat and no problems...
Dante63 said:
By why?
My two previous phones had KitKat and no problems...
Click to expand...
Click to collapse
After a few KitKat updates my phone started random hotboot too.
On lollipop 5.1.1 (COH update) it's all gone with 2 drawbacks.
Fingerprint must be off or I'll get another random hotboot+random lag.
Xposed Framework is out of the question for Stock 5.1.1 ROM.
The only way to install Xposed is to flash non a TW ROM or flash a Deodexed Stock ROM which is not my preferences as XPOSED for 5.1.1 is still in ALPHA stage.
COI update said to be the best update as it fix fingerprint bug. But COI update is still unavailable in my country.
Since no solutions were found...
I'd share mine... You need Root...
Simply use this apk:
https://play.google.com/store/apps/details?id=simple.reboot.com
Create a widget and drop it on the home screen...
This solution is temporarily until the cause is found which will likely take a lot of time...
I have an At&t (though no at&t mobile service currently) Samsung tab 4 8inch. In the last few days it has started freezing SEVERAL times a day. it doesnot matter what app, its likely to freeze on any of them. I would say it probably happens most when Im backing out/exiting an app. When it freezes I can stilll shut screen off but when I turn it back on I am just where it froze -not lock screen, it wont acknowledge plugging charger in, and cant click restart. Touchwiz has stopped message may or may not come up, but I cannot click on it even if it does. The ONLY way I can shut it down then is down vol +power for about 15seconds. Then it restarts and may do it 5 minutes later or 5hours later.
It just started this suddenly. I also had not just installed anything.
If a custom ROM or something would fix it, I wouldnt mind doing that if someone could possibly give me the link(s) to 1 that works for this model and links to how to do so/what I need.
I dont know if it is related or not, but about 3 or 4 days before this started, by battery life & battery charging went suddenly TOTALLY to hell.
Please help me fix this irritating &aggravating problem. Thank you very much for your time &assistance!
There are no custom ROMs for the SM-T337A unfortunately. Is your tablet on KitKat or Lollipop and are you rooted?
You should back up your internal storage and then factory reset and wipe cache in stock recovery. If you are rooted, you should remove system apps that you don't need with titanium backup or something similar. If you are on KitKat you might want to consider either updating to lollipop or factory resetting and reflashing the stock KitKat firmware with Odin.
No im not rooted. However i would like to, but didnt know there was a method of rooting the t337a.
I cant seem to fins out how to find whether its lollipop or kitkat or what?
gdownloads said:
I cant seem to fins out how to find whether its lollipop or kitkat or what?
Click to expand...
Click to collapse
Settings > About device > Android version. If it says 4.4.2 it's kitkat, if it says 5.1.1 it's lollipop
Thanks for the help.
Yes its kitkat then because it says 4.4.2 . I think 1st I'll go ahead and search how to update it to Lollipop then go from there... Does that sound like a wise decision to you??
STOOPID Question: I went to the posts at bottom of your posts (granted, I didnt go thru all 59 pages, lol) but I have a brain-fart question... would I try to root and then update to lollipop or vice-versa??
I have found temp root for lollipop. Just look in the general section. As you wouldn't be able to ota lollipop while rooted anyways.
Hi,
I recepty run into a problem that I can not fix by myself.
My galaxy s7 started to overheat (it overheats during normal usage, browsing Web etc.)
1. I was using the phone rooted with CF autoroot without a problem for a month or so
2. I installed TRWP and then Xposed framework (all the correct files following guides from this forum) and it worked all OK.
3. 2 days after the above installation I decided to make a fresh clean install of ROM. I found a new updated ROM (June update) of the stock XEO ROM that I was using.
I made a data reset and factory reset with TRWP (wiping all) and then flashed the new ROM with Odin.
I rooted it and installed xposed.
4. Phone started to overheat during normal usage.
5. I tried to flash the new ROM without installing xposed, then trying flashing ROM without even rooting it later. I finally even flashed the "old" ROM from before the June update, with no rooting or touching anything, and it still overheats.
The clues I found as far:
1) i read somewhere that xposed can cause overheat like I described but I don't understand how it could be after I wiped de device so many times and running stock unmodified rom?
2) i read somewhere that there is some Google account backup bug that makes devices overheat which seems to be connected with the 3rd point
3) it seems that Android System battery usage is higher than normal
4) the device overheat mostly on the right middle part of the phone, along the right edge of the phone a little below the power button.
5) i don't belive it's user app related because the problem exist even after fresh install of rom without additional apps installed
I would really need some advice, because I ran out of ideas what to do.
Hello, our situation is similar... I've googled the issue and I've found no solution. My overheating problems started after I installed Xposed framework. Few minutes before, I rooted my phone with Odin and installed TWRP. After I used a module on Xposed, my phone began overheating on the right part of my phone below the power button as you described. I immediately uninstalled Xposed.... nothing worked, flashed my phone back to the stock rom....still the same. IF EVER FIND A SOLUTION, PLEASE SHARE IT WITH ME... I'M SO WORRIED. THANKS.
Possibly a long shot, but I would be opening the occulus app and seeing if it needs to update.
That issue was causing a bunch of phones to overheat last week. Solved by opening the app and letting it update.
Sent from my SM-G935F using XDA-Developers mobile app