Database Users

[Q] [PLZ HELP] Note 4 Won't Reset (Not-Rooted)

hello there, I have a N910F and I have tried resetting it through the settings, as it goes into recovery it says 'installing system update' then just shows up the recovery without actually wiping the phone. when I do wipe the data it completes fine but when I click onto reboot system now an error comes up saying failed to mount data and something in brackets which I cant read because t reboots too quickly. the phone starts up with all my data still in tact.
I have also tried to flash the latest Lollipop version for the device but it as soon as I click start the flash fails. this is confusing me because this phone is not rooted. I even tried to flash TWRP but the stock recovery still seems to show up.
very puzzled would like to know if anyone can help me would appreciate it a lot! :good:

Strange Wifi Problem

Background: So i bought this used S5 900f from someone and it gave me "recovery is not seandroid enforcing" error while rooting and installing recovery. i found a workaround for this error by immediately pulling the battery trick after root. I have installed TWRP and root and they work but this "Recovery is not seandroid enforcing error" still displays when i try to enter recovery for about 2-3 seconds and then the recovery boots.
Now the Problem is : My s5 900f is not saving Wifi password on any of the lollipop builds i have tried Many UK 5.0 (BTU) Builds from Sammobile , and Nordic Countries 5.0 as soon as i restart or shutdown m phone Wifi password is reset and i have to enter it again after turning my phone on again. Surprisingly When i downgrade to any of the kitkat Builds Wifi starts saving passwords just fine?
Things i have tried
Format, Clear dalvik cache, cache, data, system, internal Storage and install different 5.0 builds.
Enabling disabling Google backup, it doesn't help.
Kindly Help me out does Wifi not saving password has anything to do with this "Seandroid not enforcing Error" . And how to fix this issue i am at verge of smashing this phone. .....:angel:

http://forum.xda-developers.com/galaxy-s5/general/s5-forget-wifi-passwords-reboot-fix-t3105976

Thanks alot buddy, you just saved my phone....Phewwww do you know why it happened in the first place?

Buggy ROM is all I can think, it happened to me with a clean install of the latest LP ROM so I went looking for a fix for myself
I tweeted to Samsung UK about it, and they just talked to me like I was stupid, I guess they don't want to admit to it being their fault

UPDATE NOW after the build prop fix, i rebooted fine once... After installing TWRP the phone is crashing on boot up....touchwiz crashes along with all other programs it wont let me boot up. Maybe TWRP messed something up.

Try clearing the caches from recovery, the build.prop fix doesn't cause any issues like that, but I've had issues after flashing custom TWRP before, generally clearing caches / pulling battery fixes it

*Detection* said:
Try clearing the caches from recovery, the build.prop fix doesn't cause any issues like that, but I've had issues after flashing custom TWRP before, generally clearing caches / pulling battery fixes it
Click to expand...
Click to collapse
does your phone display "recovery is not seandroid enforcing" just before entering twrp? i tried clearing cache and battery pulling didnt work....now flashing earlier 5.O btu.

Yea, just means it's a custom recovery

*Detection* said:
Yea, just means it's a custom recovery
Click to expand...
Click to collapse
Some folks are able to flash any 5.0 build and they don't get the Build.Prop issue. i just reflashed and the issue came back...will re edit the build.prop till now i have rooted + installed TWRP no issues so far only build.prop left to be edited..... could you please tell me why is it persistent on some phones that even reflashing, formating doesn't help.

Unfortunately Nothing works....I have been more than patient with this device...been flashing and trying different things for 18 hours now. It works fine but after going to recovery (Just by entering it) and then rebooting will freeze my phone with "Unfortunately Media storage has stopped working...and everything else like touchwiz also crashes".......i was so...so wrong to move to a samsung This Definitely is my last samsung phone...for now i will keep trying different things.

Try a different recovery, Philz Touch, CWM etc
Are you definitely flashing the latest TWRP?
The way I install TWRP is using TWRP Manager from G Play store
https://play.google.com/store/apps/details?id=com.jmz.soft.twrpmanager&hl=en_GB
Install BusyBox first or it'll prompt you before doing anything
https://play.google.com/store/apps/details?id=stericson.busybox&hl=en_GB
The defaults it prompts you to change for locations can be left as they are

*Detection* said:
Try a different recovery, Philz Touch, CWM etc
Are you definitely flashing the latest TWRP?
The way I install TWRP is using TWRP Manager from G Play store
https://play.google.com/store/apps/details?id=com.jmz.soft.twrpmanager&hl=en_GB
Install BusyBox first or it'll prompt you before doing anything
https://play.google.com/store/apps/details?id=stericson.busybox&hl=en_GB
The defaults it prompts you to change for locations can be left as they are
Click to expand...
Click to collapse
Yeah i am using twrp-2.8.7.0-klte.img. Will try Philz now can u guide me to the correct CWM i cant find it anywhere. thanks

dork997 said:
Yeah i am using twrp-2.8.7.0-klte.img. Will try Philz now can u guide me to the correct CWM i cant find it anywhere. thanks
Click to expand...
Click to collapse
Should be able to find everything you need here
http://forum.xda-developers.com/showthread.php?t=2697523
Instructions for ADB manual install, and also ODIN
Philz is a big favourite over CWM - Id try Philz first
Strange your same model S5 takes a fit with TWRP, it works fine on my G900F
Might be worth trying the App install method I posted

*Detection* said:
Should be able to find everything you need here
http://forum.xda-developers.com/showthread.php?t=2697523
Instructions for ADB manual install, and also ODIN
Philz is a big favourite over CWM - Id try Philz first
Strange your same model S5 takes a fit with TWRP, it works fine on my G900F
Might be worth trying the App install method I posted
Click to expand...
Click to collapse
Thanks for your Help, i guess this problem is too complicated. Anyway this time i installed Philz recovery > formatted everything > remove user content and data > custom formatted everything > flashed 5.0 BTU. and surprisingly its saving WiFi passwords without any build prop changes. So i am going to leave it here . 5.0 Unrooted with stock recovery everything working (FOR NOW) . This time i used Odin 3.10 instead of 3.07. I hope it does not get stuck at boot logo and start crashing. Only one problem it kept connecting to "update server" evem tho i had disabled the auto update option from settings>about >updates . i restarted immediately hopefully it wont try to update again. Thanks again for your help.

Problem booting a custom ROM

Hi all!
I'm trying to install the BlissPop ROM (BlissPop-v3.9-jflte-OFFICIAL-20150828-2215) [Lollipop 5.1.1]. I'm flashing using the TWRP Recovery (v2.8.5.0). Here are the steps I'm doing:
Factory reset (Data/Dalvik/cache)
Wipe cache (again)
Wipe Dalkvik (again)
Flash BlissPop-v3.9-jflte-OFFICIAL-20150828-2215.zip
Reboot
When I do that, I get the error message:
KERNEL IS NOT SEANDROID ENFORCING
Set Warranty Bit : kernel
Unfortunately, I'm one of the ones where it's not simply a warning with it merrily continuing it's boot, it is stuck on the screen displaying "Galaxy S4 i9505".
In an attempt to get some kind of lollipop ROM installed, I came across the JFLTE-GPE ROM, and have now flashed it (JFLTE-GPE-20150919) [Lollipop 5.1.1]. I have done the exact same steps as I had tried to do with BlissPop, but obviously flashing JFLTE-FPE instead.
Voila! It works! It lingers on the message 'KERNEL IS NOT SEANDROID ENFORCING" and proceeds to boot successfully, and is now running fine. Now, I have searched for days (yes, days!) to try and find a way to get the BlissPop ROM to work properly, but all the sites/threads I've come across offer little detail on the poster's part, have no solution, or a solution that doesn't work for me. Any help is greatly appreciated! If you need any more information about my device, don't hesitate to ask.

warrior4894 said:
Hi all!
I'm trying to install the BlissPop ROM (BlissPop-v3.9-jflte-OFFICIAL-20150828-2215) [Lollipop 5.1.1]. I'm flashing using the TWRP Recovery (v2.8.5.0). Here are the steps I'm doing:
Factory reset (Data/Dalvik/cache)
Wipe cache (again)
Wipe Dalkvik (again)
Flash BlissPop-v3.9-jflte-OFFICIAL-20150828-2215.zip
Reboot
When I do that, I get the error message:
KERNEL IS NOT SEANDROID ENFORCING
Set Warranty Bit : kernel
Unfortunately, I'm one of the ones where it's not simply a warning with it merrily continuing it's boot, it is stuck on the screen displaying "Galaxy S4 i9505".
In an attempt to get some kind of lollipop ROM installed, I came across the JFLTE-GPE ROM, and have now flashed it (JFLTE-GPE-20150919) [Lollipop 5.1.1]. I have done the exact same steps as I had tried to do with BlissPop, but obviously flashing JFLTE-FPE instead.
Voila! It works! It lingers on the message 'KERNEL IS NOT SEANDROID ENFORCING" and proceeds to boot successfully, and is now running fine. Now, I have searched for days (yes, days!) to try and find a way to get the BlissPop ROM to work properly, but all the sites/threads I've come across offer little detail on the poster's part, have no solution, or a solution that doesn't work for me. Any help is greatly appreciated! If you need any more information about my device, don't hesitate to ask.
Click to expand...
Click to collapse
Update your recovery to the latest TWRP. You are using an outdated version.

Hi,
Thanks for the speedy reply, unfortunately updating the recovery to TWRP v2.8.7.0 didn't fix the problem. On the JFLTE-GPE ROM thread, there was a link to an alternate kernel. I managed to boot BlissPop successfully by flashing it and then the kernel. However, it is now stuck at the loading screen.

warrior4894 said:
Hi,
Thanks for the speedy reply, unfortunately updating the recovery to TWRP v2.8.7.0 didn't fix the problem. On the JFLTE-GPE ROM thread, there was a link to an alternate kernel. I managed to boot BlissPop successfully by flashing it and then the kernel. However, it is now stuck at the loading screen.
Click to expand...
Click to collapse
Are you also wiping /system before flashing? I don't see you mentioning it in the first post but it's mandatory.

After fishing new rom factory reset through recovery.good luck

Hi, so I've tried wiping /system as well, with no luck. I have also factory reset after flashing the ROM, and it still didn't work. But when I factory reset it, the computer detected the connection, but it didn't show on My Computer? I'm not sure if that means anything, am I being too impatient? I did wait a good 20 minutes.

Samsung S4 stucked at startup screen after root & flash...

I just rooted my device with a one-click-root app, then i downloaded CWM recovery app , and flashed the Xposed Modules firmware. After this, i reboot my device but my device stucked at the startup screen of samsung. Tried factory reset, and formating system, cache , but still fail to open my phone. When going to the recovery menu , it says "recovery is not seandroid enforcing" , and when i click "Reboot device" it says , "Root access missing. Root device?" and there were two option , "NO" and "YES FIX ROOT /SYSTEM/XBIN/S/" , tried both options , but still can't on my phone... HELP.....

Download the official firmware from sammobile and install it via odin.. if you don't know how to do it just search in the forum for the correct guide to help you

Don't use cwm, use twrp as the custom recovery.

jiawen99 said:
I just rooted my device with a one-click-root app, then i downloaded CWM recovery app , and flashed the Xposed Modules firmware. After this, i reboot my device but my device stucked at the startup screen of samsung. Tried factory reset, and formating system, cache , but still fail to open my phone. When going to the recovery menu , it says "recovery is not seandroid enforcing" , and when i click "Reboot device" it says , "Root access missing. Root device?" and there were two option , "NO" and "YES FIX ROOT /SYSTEM/XBIN/S/" , tried both options , but still can't on my phone... HELP.....
Click to expand...
Click to collapse
Guys, the recovery isn't important. IT'S IMPORTANT TO DON'T FLASH xposed framework on the stock firmware. Install a custom ROM is the best way to stay away from xposed framework problems.

recovery mode

hi, i have two questions:
when i open recovery mode i have a message "installing system update" and after "no command"
is it normal?
in recovery mode (after an earlier "error") i have a message (at the bottom screen) "E:failed to open /dev/block/bootdevice/by-name/misc: no such file or directory"
it is something important? what does it mean?
my phone is j5(2016), sm-j510fn with official android 7.1.1 XEO (update installed via odin same as stock samsung rom 6.0.1)
the phone works fine, but i want to know what these "error" messages mean in the recovery mode
i have one more question:
after installing nougat update via odin (one file rom) my phone didn't back to factory settings, that's good?

I observed that too...
I observed that too, when i tryed to do a hard reset,but i got a different problem my phone officialy updated this night and since it updated it keeps giving me the error: "Unfortunetly com.android.phone has stopped" and it does not receve any service :crying:, i wiped the cache partiton, i did a factory reset, but it keeps giving me this error, did this happen to anyone else?

cichy. said:
hi, i have two questions:
when i open recovery mode i have a message "installing system update" and after "no command"
is it normal?
in recovery mode (after an earlier "error") i have a message (at the bottom screen) "E:failed to open /dev/block/bootdevice/by-name/misc: no such file or directory"
it is something important? what does it mean?
my phone is j5(2016), sm-j510fn with official android 7.1.1 XEO (update installed via odin same as stock samsung rom 6.0.1)
the phone works fine, but i want to know what these "error" messages mean in the recovery mode
i have one more question:
after installing nougat update via odin (one file rom) my phone didn't back to factory settings, that's good?
Click to expand...
Click to collapse
That is normal for the stock android recovery.
I would reccomend to clean flash the new nougat if you are comming from a custom ROM. But if you just installed it over stock 6.0.1 than it is ok if its not wiped. It would be the same that you installed nougat OTA.
---------- Post added at 02:57 PM ---------- Previous post was at 02:54 PM ----------
Ticsy said:
I observed that too, when i tryed to do a hard reset,but i got a different problem my phone officialy updated this night and since it updated it keeps giving me the error: "Unfortunetly com.android.phone has stopped" and it does not receve any service :crying:, i wiped the cache partiton, i did a factory reset, but it keeps giving me this error, did this happen to anyone else?
Click to expand...
Click to collapse
If you did a factory reset and the problem persists, you should install nougat manualy over odin.

Haxomen said:
That is normal for the stock android recovery.
I would reccomend to clean flash the new nougat if you are comming from a custom ROM. But if you just installed it over stock 6.0.1 than it is ok if its not wiped. It would be the same that you installed nougat OTA.
---------- Post added at 02:57 PM ---------- Previous post was at 02:54 PM ----------
If you did a factory reset and the problem persists, you should install nougat manualy over odin.
Click to expand...
Click to collapse
Thanks for the answer i went to a service and they fixed the problem for me as i am still afraid of bricking my phone but i will try to learn how to root and change roms on a phone i got at home that i do not need... btw they said it had a problem with the IMEI number and that it had 50/50 chance of bricking but they managed to repair it... anyway thanks for the answer ^_^

cichy. said:
hi, i have two questions:
when i open recovery mode i have a message "installing system update" and after "no command"
is it normal?
in recovery mode (after an earlier "error") i have a message (at the bottom screen) "E:failed to open /dev/block/bootdevice/by-name/misc: no such file or directory"
it is something important? what does it mean?
my phone is j5(2016), sm-j510fn with official android 7.1.1 XEO (update installed via odin same as stock samsung rom 6.0.1)
the phone works fine, but i want to know what these "error" messages mean in the recovery mode
i have one more question:
after installing nougat update via odin (one file rom) my phone didn't back to factory settings, that's good?
Click to expand...
Click to collapse
"E:failed to open /dev/block/bootdevice/by-name/misc: no such file or directory"
My phone also had this problem. after I download latest stock ROM "J510FNXXU2BRL1_J510FNODD2BRL2_SLK" (SLK is my region) from sammobile and flashed it using Odin.
But it was make new problem. now phone looping on Samsung logo. I looked at screen about 15min. not start android. I tried different different method to solve.
finally download TWRP from XDA ,after flash it and booted to twrp.
after did these steps.
1. Wipe > Advanced Wipe
2. select 'Data' (partition)
3. Now tap 'Repair or Change file system'
4. Now tap on 'Repair file system'. If it is done, it say done.
( In my case it not complete and say has some mounting errors. and I tap on 'Change file System' next select 'EXT4' and swiped to change.
now repeat step no 4. )
5. Now flash latest stock ROM using Odin and re boot.
done!
after about 5-8 min phone start correctly.
after I checked the error "E:failed to open /dev/block/bootdevice/by-name/misc: no such file or directory" in recovery mod. oh! it has gone. :laugh:
I'm sure it will work to you also.

Ranasinghe said:
"E:failed to open /dev/block/bootdevice/by-name/misc: no such file or directory"
My phone also had this problem. after I download latest stock ROM "J510FNXXU2BRL1_J510FNODD2BRL2_SLK" (SLK is my region) from sammobile and flashed it using Odin.
But it was make new problem. now phone looping on Samsung logo. I looked at screen about 15min. not start android. I tried different different method to solve.
finally download TWRP from XDA ,after flash it and booted to twrp.
after did these steps.
1. Wipe > Advanced Wipe
2. select 'Data' (partition)
3. Now tap 'Repair or Change file system'
4. Now tap on 'Repair file system'. If it is done, it say done.
( In my case it not complete and say has some mounting errors. and I tap on 'Change file System' next select 'EXT4' and swiped to change.
now repeat step no 4. )
5. Now flash latest stock ROM using Odin and re boot.
done!
after about 5-8 min phone start correctly.
after I checked the error "E:failed to open /dev/block/bootdevice/by-name/misc: no such file or directory" in recovery mod. oh! it has gone. :laugh:
I'm sure it will work to you also.
Click to expand...
Click to collapse
same error, trying to do but cant get twrp installed as I have frp lock on, any ideas how to get it off without being able to get into developer options?

Someone has resolved this problem?