Related
I cannot use the default "Encrypt Phone" option on the settings menu of my Nexus 4. When used, it just reboots the phone and I have done this process over 5 times with no success.
I used the Android Nexus 4 ToolKitv2.0.0 and the recommended root tools and am running obviously 4.2.2.
Any reason why it's doing this? Thanks.
Bubblewhip said:
I cannot use the default "Encrypt Phone" option on the settings menu of my Nexus 4. When used, it just reboots the phone and I have done this process over 5 times with no success.
I used the Android Nexus 4 ToolKitv2.0.0 and the recommended root tools and am running obviously 4.2.2.
Any reason why it's doing this? Thanks.
Click to expand...
Click to collapse
Are you using a custom recovery - TWRP or CWM? You need to be using the stock recovery image to encrypt your phone. The nexus toolkit will allow you to re-flash the stock recovery.
One the stock recovery has been re-flashed, you should be able to encrypt your phone. I had to re-flash stock recovery, reboot the phone, then reflash the stock recovery again.
Once the device has been successfully encrypted using the stock recovery, you can re-flash either the TWRP or CWM as your recovery. TWRP supports reading data from encrypted devices, so it is probably the way to go (not sure if CWM dows now, but it didn't last time I looked).
Does encrypting the phone make a dramatic difference in speed (as in slow down) for the phone or does it mainly affect boot times?
Thanks for the tip about having stock recovery as I also wanted to encrypt phone as well. Would one have to de-encrypt phone then install custom recovery to update a custom Rom (I'm running paranoid android) then flash to stock recovery to encrypt phone again- seems long winded :-\
Just from reading the above post once flashed to stock recovery and then encrypted device, it's okay to flash back to TWRP and still have an encrypted device?
Is there another way to do this when running a custom rom?
Sent from my Nexus 4
randomvector said:
Does encrypting the phone make a dramatic difference in speed (as in slow down) for the phone or does it mainly affect boot times?
Thanks for the tip about having stock recovery as I also wanted to encrypt phone as well. Would one have to de-encrypt phone then install custom recovery to update a custom Rom (I'm running paranoid android) then flash to stock recovery to encrypt phone again- seems long winded :-\
Just from reading the above post once flashed to stock recovery and then encrypted device, it's okay to flash back to TWRP and still have an encrypted device?
Is there another way to do this when running a custom rom?
Sent from my Nexus 4
Click to expand...
Click to collapse
I haven't noticed a difference in speed, however technically there will be a little bit of a slowdown.
I'm running stock Android, so I don't know how well it plays with custom ROMs, but you can re-flash a TWRP recovery after encrypting your phone with stock Android on it.
If the custom ROM installation wipes the data partition, it would remove the encryption.
I've tried flashing stock recovery using Nexus 4 Toolkit and recovery is back to stock. However the phone is still just rebooting when I press encrypt device. What am I doing wrong?
For some reason I had to reflash the stock recovery, reboot, then reflash the stock recovery again. No idea why, but it worked for me!
Sent from my Nexus 4 using Tapatalk 2
Booted back into stock recovery device is still rebooting itself after hitting the encrypt button, Encryption did not happen.
Found the problem but I can't seem to fix it. Flashing the stock recovery doesn't seem to actually do it. When I boot to recovery when flashed to stock, it just shows the android mascot with an open chest and a warning symbol. Have reflashed many times over 5, and still doesn't work. It seems like I need the actual image recovery file. something like Recovery.img?
Bubblewhip said:
Found the problem but I can't seem to fix it. Flashing the stock recovery doesn't seem to actually do it. When I boot to recovery when flashed to stock, it just shows the android mascot with an open chest and a warning symbol. Have reflashed many times over 5, and still doesn't work. It seems like I need the actual image recovery file. something like Recovery.img?
Click to expand...
Click to collapse
The android with a warning symbol is the normal symbol of stock recovery.
However, I wonder, if you could solve the problem? My nexus doesn't want to encrypt itself too. Flashed stock recovery already twice and it just keeps rebooting when I start the encryption process.
Quick update: After trying it several times in a row it finally worked (after the fourth time or so). I have no clue why it didn't work before as I haven't change anything.
c_m_l said:
Quick update: After trying it several times in a row it finally worked (after the fourth time or so). I have no clue why it didn't work before as I haven't change anything.
Click to expand...
Click to collapse
Thanks for your perseverance! I spent half a day trying to encrypt my rooted Galaxy S4 with the similar problem as you:
I go into System Settings, click "Encrypt Phone", then I get the green android and the phone just reboots itself as normal.
What worked for me: AIRPLANE MODE.
I was rebooting it time after time with no effect (following your suggestion). Once I turned on the Airplane Mode, the encryption started working.
My Current Setup:
Android 4.2.2 Jelly Bean
Samsung Galaxy S4 Google Edition (GT-I9505g) rooted via CF auto root. + Full disk encryption!
Works perfectly!
Now I can have different passwords for disk encryption (long strong password) and for locker screen (simple)
JohnnyBBB said:
Thanks for your perseverance! I spent half a day trying to encrypt my rooted Galaxy S4 with the similar problem as you:
I go into System Settings, click "Encrypt Phone", then I get the green android and the phone just reboots itself as normal.
What worked for me: AIRPLANE MODE.
I was rebooting it time after time with no effect (following your suggestion). Once I turned on the Airplane Mode, the encryption started working.
My Current Setup:
Android 4.2.2 Jelly Bean
Samsung Galaxy S4 Google Edition (GT-I9505g) rooted via CF auto root. + Full disk encryption!
Works perfectly!
Now I can have different passwords for disk encryption (long strong password) and for locker screen (simple)
Click to expand...
Click to collapse
Old thread, same issue, HTC One w/ OmniROM (m7att). My Nexus 10 did it as well.
The person saying to reflash stock? DOn't listen to that. Doesn't need to be done. Encrypted all my devices w/ TWRP installed.
Airplane mode DID work, though.
I just had this issue with my N4, too. I read on the Google Product Forum that this was because a process prevents from unmounting the /data partition. ("Nexus 5 is not going through encryption process" - can't post link due to being new)
With that in mind, I rebooted into safe mode and then tried again and it worked on the first try (At least it started the encryption process, it's at 10% now)
I had this problem for a looooong time. Thankfully, I seem to have discovered a solution for those still encountering this issue.
Turn off SuperSU (Settings -> More -> Application manager -> All -> SuperSU -> Turn Off)
Reboot into Safe Mode (How to)
Run encryption (Settings -> More -> Security -> Encrypt Device)
Turn on SuperSU after complete (Settings -> More - > Application manager -> Turned Off -> SuperSU -> Turn On)
Last night I got a Galaxy S5 as an anniversary gift and successfully rooted and installed TWRP and Alliance Rom 4.4.2 and everything is going smooth for the most part except for fingerprint scanning.
When going to define a new fingerprint or access fingerprint options it gives an error: "An error has occurred with the fingerprint sensor...".
The process I took to mod it was use Odin to downgrade the kernel back to a towelroot friendly one, use towelroot to gain root, install busybox, flash previous kernel back using Odin, installed Safestrap (nandroid backed up), installed Alliance Rom via Safestrap recovery, installed SuperSU (disabled KNOX) and here I am. Does disabling KNOX cause the issue?
Any advice would be greatly appreciated! Thanks XDA
Yes I have searched forums and google before posting. Yes I wiped prior to installing the rom.
Unrelated problem: the phone also does not shut down. When going to shut down the samsung shut down animation plays then the screen goes black and just hangs there. The LED shows a blue light and the bottom soft keys are lit up and it will stay that way until I pull the battery. Any advice?
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
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 rooted my J5 (SM-J500FN) yesterday the first time. Since then I reflashed the CF-Auto-Root file about 5 times because my phone got stuck at the bootup screen (on the top of the screen it said in yellow: Set Warranty Bit : kernel). This was due to Samsung KNOX which I somehow was able to deactivate it. After trying many times I now can restart my phone consistently without any bootloops (the yellow text is still there).
My problem now is that after about 3 minutes runtime root checker doesnt detect my device as rooted. SuperSU writes that my device isnt rooted. After a restart root works again for maximum 5 minutes. Im really puzzled because I never experienced someting like that befor and I have no clue how to solve this...
-Toby
Toby9 said:
I rooted my J5 (SM-J500FN) yesterday the first time. Since then I reflashed the CF-Auto-Root file about 5 times because my phone got stuck at the bootup screen (on the top of the screen it said in yellow: Set Warranty Bit : kernel). This was due to Samsung KNOX which I somehow was able to deactivate it. After trying many times I now can restart my phone consistently without any bootloops (the yellow text is still there).
My problem now is that after about 3 minutes runtime root checker doesnt detect my device as rooted. SuperSU writes that my device isnt rooted. After a restart root works again for maximum 5 minutes. Im really puzzled because I never experienced someting like that befor and I have no clue how to solve this...
-Toby
Click to expand...
Click to collapse
Happened to me too in the summer...
CF-autoroot isn't really good... Try the old method of flashing SuperSU trough a recovery (TWRP). this should work with no bugs, no matter what.
That yellow text above the screen: "Set Warranty Bit: kernel" is all good. It indicates that your device is rooted by indirectly saying that the system has been modified. I think that some repair app in the phone is restoring files after startup which makes you lose root after a couple of minutes. I suggest you try flashing with TWRP (custom recovery).
Thank you both. I flashed the SuperSU zip and now it is working perfectly.