I installed a ROM the other day and when it booted backup it now shows a screen that says Custom with a lock underneath it. How do I get rid of this screen as it seems to make my device boot up slower. I had this happen to my Galaxy S3 also and I fixed it by returning everything to stock but I really don't want to do that. Any suggestions?
bvm1228 said:
I installed a ROM the other day and when it booted backup it now shows a screen that says Custom with a lock underneath it. How do I get rid of this screen as it seems to make my device boot up slower. I had this happen to my Galaxy S3 also and I fixed it by returning everything to stock but I really don't want to do that. Any suggestions?
Click to expand...
Click to collapse
There is a module for xposed framwork called wanam xposed that module has option in the security hacks section to fake system status to offical which will return the original galaxy s4 boot screen after a reboot or two. Its a quick fix without having to return everything to stock.
Ok thanks. I will try it out
Does Xposed work on Cyanogenmod based builds?
since service isn't working for the lineage roms, I decided on the next best thing the n - ify module
I don't want a boot loop though so that's why I'm asking this question
Tried it it | works
I just went ahead and tried it myself because there is a way to recover from xposed bootloops.
you wont have to worry because xposed works on this phone
Hello Guys.
Im in dire need of help actually. Ive recently rooted my galaxy grand 2 running 4.4.2 KK and set it up with twrp v3.1.
yet im having the issue when i install a custom rom.
1.) Cyanogenmod - MM
When i install the rom, it installs and and on 1st reboot it optimizes all the apps yet gets stuck on "starting apps". when i force restarted it, it boots till the welcome screen to select the language but then the touch screen stops responding but its not stuck as pressing the power button turns off the screen and back on and also on long press reboot options appear , which on the other hand responds to touch. so im guessing its not the touch screen issue? but then ive noticed that apps also crash while im on the welcome screen.
2. Resurrection remix - MM
Same issue yet this passes the starting apps screen and goes to the home screen directly but only to be found that the screen isnt responding.
this is very weird because of all the phones ive installed custom rom on, this is the first case im having such trouble.
could it be because knox is installed? i tried getting rid of it from the stock rom but everytime i try that i cant boot back up because it gets stuck at the samsung logo.
can some one help me quick because this is really irritating.
Thanks.
Maybe its realy screen problem... did the touch screen works on twrp
fire_onCA said:
Maybe its realy screen problem... did the touch screen works on twrp
Click to expand...
Click to collapse
Yes It Does. Its not the screen issue because on stock rom everything works properly.
Im guessing somethings interrupting with the OS, causing the apps to crash.
aymanabdulla said:
Hello Guys.
Im in dire need of help actually. Ive recently rooted my galaxy grand 2 running 4.4.2 KK and set it up with twrp v3.1.
yet im having the issue when i install a custom rom.
1.) Cyanogenmod - MM
When i install the rom, it installs and and on 1st reboot it optimizes all the apps yet gets stuck on "starting apps". when i force restarted it, it boots till the welcome screen to select the language but then the touch screen stops responding but its not stuck as pressing the power button turns off the screen and back on and also on long press reboot options appear , which on the other hand responds to touch. so im guessing its not the touch screen issue? but then ive noticed that apps also crash while im on the welcome screen.
2. Resurrection remix - MM
Same issue yet this passes the starting apps screen and goes to the home screen directly but only to be found that the screen isnt responding.
this is very weird because of all the phones ive installed custom rom on, this is the first case im having such trouble.
could it be because knox is installed? i tried getting rid of it from the stock rom but everytime i try that i cant boot back up because it gets stuck at the samsung logo.
can some one help me quick because this is really irritating.
Thanks.
Click to expand...
Click to collapse
Flash twrp 3.0.0 (over your existing twrp 3.1). Just copy the twrp.zip to your root directory of internal storage and flash using twrp 3.1. Maybe that will help because it helped me.
mfaisal98 said:
Flash twrp 3.0.0 (over your existing twrp 3.1). Just copy the twrp.zip to your root directory of internal storage and flash using twrp 3.1. Maybe that will help because it helped me.
Click to expand...
Click to collapse
but I've already tried that! I started off with 3.0 and when that didn't work I moved to 3.1!
I also noticed I get a small message on top when. I start the phone with the Samsung logo saying that something isn't seandroid when I install a custom room but it isn't like an error or something.
Could the issue be with the kernal?
Or should I try cwm recovery now?
aymanabdulla said:
but I've already tried that! I started off with 3.0 and when that didn't work I moved to 3.1!
I also noticed I get a small message on top when. I start the phone with the Samsung logo saying that something isn't seandroid when I install a custom room but it isn't like an error or something.
Could the issue be with the kernal?
Or should I try cwm recovery now?
Click to expand...
Click to collapse
If you get some error message on boot while there is the Samsung logo then there is something wrong! Now you should:
1. Flash the stock rom (to correct that error message on boot)
2. Flash recovery
3. Root (SuperSU 2.82)
4. Continue with the installation (thru twrp 3.0.0) of 6.0.1 but before that:
(a) Factory reset
(b) Wipe data
(c) Wipe cache
(d) Wipe dalvik cache)
(e) DO NOT WIPE THE SYSTEM!
Goog luck
I suggest flashing the stock 4.4.2 ROM via Odin and then start everything from scratch. Currently facing the same problem after flashing the Ressurection Remix M 5.7.4.
mfaisal98 said:
If you get some error message on boot while there is the Samsung logo then there is something wrong! Now you should:
1. Flash the stock rom (to correct that error message on boot)
2. Flash recovery
3. Root (SuperSU 2.82)
4. Continue with the installation (thru twrp 3.0.0) of 6.0.1 but before that:
(a) Factory reset
(b) Wipe data
(c) Wipe cache
(d) Wipe dalvik cache)
(e) DO NOT WIPE THE SYSTEM!
Goog luck
Click to expand...
Click to collapse
Its not actually an error message but a small notice on the top left corner.
When I restore my official rom back the message is normally gone.
But I will try again with ur advice again because I always wipe system before flashing the rom so it could be causing the issue.
Thanks I'll let u know what happens
kaiserfakinaway said:
I suggest flashing the stock 4.4.2 ROM via Odin and then start everything from scratch. Currently facing the same problem after flashing the Ressurection Remix M 5.7.4.
Click to expand...
Click to collapse
I did do that. I have the official stock rom running now since RR and cyanogenmod isn't responding.
aymanabdulla said:
I did do that. I have the official stock ROM running now since RR and CyanogenMod isn't responding.
Click to expand...
Click to collapse
Have you tried flashing RR or CM13 after flashing the stock ROM?
and could you give me the full name of the stock ROM?
aymanabdulla said:
Hello Guys.
Im in dire need of help actually. Ive recently rooted my galaxy grand 2 running 4.4.2 KK and set it up with twrp v3.1.
yet im having the issue when i install a custom rom.
1.) Cyanogenmod - MM
When i install the rom, it installs and and on 1st reboot it optimizes all the apps yet gets stuck on "starting apps". when i force restarted it, it boots till the welcome screen to select the language but then the touch screen stops responding but its not stuck as pressing the power button turns off the screen and back on and also on long press reboot options appear , which on the other hand responds to touch. so im guessing its not the touch screen issue? but then ive noticed that apps also crash while im on the welcome screen.
2. Resurrection remix - MM
Same issue yet this passes the starting apps screen and goes to the home screen directly but only to be found that the screen isnt responding.
this is very weird because of all the phones ive installed custom rom on, this is the first case im having such trouble.
could it be because knox is installed? i tried getting rid of it from the stock rom but everytime i try that i cant boot back up because it gets stuck at the samsung logo.
can some one help me quick because this is really irritating.
Thanks.
Click to expand...
Click to collapse
Did you flashed the vendor.zip provided after flashing the rom?If not,then it is the cause of that problem
kaiserfakinaway said:
Have you tried flashing RR or CM13 after flashing the stock ROM?
and could you give me the full name of the stock ROM?
Click to expand...
Click to collapse
Yes, thats what i did.
G7102DDUBNK1_G7102ODDBNK1_G7102DDUBNK1_HOME.tar.md5 this was the file name. it works fine i guess, had some issues with the sim as the phone keeps on asking to reboot but no other issues.
Subhashis said:
Did you flashed the vendor.zip provided after flashing the rom?If not,then it is the cause of that problem
Click to expand...
Click to collapse
Yes i did. as well as the front cam + patch fix. i flashed both yet still the same issue.
mfaisal98 said:
If you get some error message on boot while there is the Samsung logo then there is something wrong! Now you should:
1. Flash the stock rom (to correct that error message on boot)
2. Flash recovery
3. Root (SuperSU 2.82)
4. Continue with the installation (thru twrp 3.0.0) of 6.0.1 but before that:
(a) Factory reset
(b) Wipe data
(c) Wipe cache
(d) Wipe dalvik cache)
(e) DO NOT WIPE THE SYSTEM!
Goog luck
Click to expand...
Click to collapse
Ok i tried this with the steps u have told me. still no luck
i went to twrp opened wipe, wiped dalvik cache, cache, internal storage and data. but not the system.
same issue. also the small message which comes in the top left corner is
"Kernal is not seandroid enforcing" red colour font
"set warranty bit : kernal" yellow colour font
why is this shown?
should i try cwm?
So I have been trying various ROMs and found out that this problem only exists on MM ROMs. RR-M and CM13 both starts but system stops responding completely. But RR-N and CM14.1/12.1/12 are working flawlessly.
---------- Post added at 08:05 AM ---------- Previous post was at 08:03 AM ----------
aymanabdulla said:
Ok i tried this with the steps u have told me. still no luck
i went to twrp opened wipe, wiped dalvik cache, cache, internal storage and data. but not the system.
same issue. also the small message which comes in the top left corner is
"Kernal is not seandroid enforcing" red colour font
"set warranty bit : kernal" yellow colour font
why is this shown?
should i try cwm?
Click to expand...
Click to collapse
That small message is not a problem. It is showing because the kernel is not selinux enforcing.
kaiserfakinaway said:
So I have been trying various ROMs and found out that this problem only exists on MM ROMs. RR-M and CM13 both starts but system stops responding completely. But RR-N and CM14.1/12.1/12 are working flawlessly.
---------- Post added at 08:05 AM ---------- Previous post was at 08:03 AM ----------
That small message is not a problem. It is showing because the kernel is not selinux enforcing.
Click to expand...
Click to collapse
Why Doesnt any one else have this problem?
oh is it? what about lineage os 13.1 running MM?
Fine i have put cm12.1 for download, will flash it and let u know what happened.
Fingers Crossed
kaiserfakinaway said:
So I have been trying various ROMs and found out that this problem only exists on MM ROMs. RR-M and CM13 both starts but system stops responding completely. But RR-N and CM14.1/12.1/12 are working flawlessly.
---------- Post added at 08:05 AM ---------- Previous post was at 08:03 AM ----------
That small message is not a problem. It is showing because the kernel is not selinux enforcing.
Click to expand...
Click to collapse
Thank You So MUCH.....
The issue was with the MM roms, because cm12.1 seems to be working perfectly, although not the camera. could someone tell me what about that now?
what now should we close this thread or figure out why MM isnt working on this device? Kernal Issue?
Could someone also check if the Lineage os with MM works or not?
Thanks again.
aymanabdulla said:
Thank You So MUCH.....
The issue was with the MM roms, because cm12.1 seems to be working perfectly, although not the camera. could someone tell me what about that now?
what now should we close this thread or figure out why MM isnt working on this device? Kernal Issue?
Could someone also check if the Lineage os with MM works or not?
Thanks again.
Click to expand...
Click to collapse
Have you tried any TW MM ports like J7 Hybrid MM Heavily Debloated Port or [ROM][6.0.1][TW][Electron Rom][Version 1] or [ROM][6.0.1][TW] JSERROM Version 3.1 [BETA][ms013g]?
kaiserfakinaway said:
Have you tried any TW MM ports like J7 Hybrid MM Heavily Debloated Port or [ROM][6.0.1][TW][Electron Rom][Version 1] or [ROM][6.0.1][TW] JSERROM Version 3.1 [BETA][ms013g]?
Click to expand...
Click to collapse
Nope, all of them have camera issues too.
but im sure there will be a fix for this, since its running LOLLIPOP.
I'll let u know.
aymanabdulla said:
Thank You So MUCH.....
The issue was with the MM roms, because cm12.1 seems to be working perfectly, although not the camera. could someone tell me what about that now?
what now should we close this thread or figure out why MM isnt working on this device? Kernal Issue?
Could someone also check if the Lineage os with MM works or not?
Thanks again.
Click to expand...
Click to collapse
Might not be a kernel issue because I have also tried with this custom kernel [KERNEL][5.x/TW/6.x]Infected Kernel R4[15-05-2016] and still the same.
hi
I can not upgrade to Android 5.0.2. Because After flashing screen is black.
My phone only boots with Android 4.4.4
Android 5.0.2 I've also tested 4 files. Do not boot again
I also have the same problem with installing the Custom ROM. Custom ROM is installed. But my phone will not boot. And the black screen stays there after flashing
How can I fix this problem?
please help!!!
maziar__rahmannezhad said:
hi
I can not upgrade to Android 5.0.2. Because After flashing screen is black.
My phone only boots with Android 4.4.4
Android 5.0.2 I've also tested 4 files. Do not boot again
I also have the same problem with installing the Custom ROM. Custom ROM is installed. But my phone will not boot. And the black screen stays there after flashing
How can I fix this problem?
please help!!!
Click to expand...
Click to collapse
same problem i am facing now - Did you get a solution for this ? I only have to use the stock rom
Hello, So i recently Flashed the new version of hadesRom ( V.11.0 ) into my S8 ( SM-G950FD ) and I'm facing a problem that i never had before, my Screen freezes for like 5 or 6 seconds when im doing some actions for example when the device is locked and i turn the screen up and swipe to unlock , it freezes for 5 sec. or when i press the Settings ( the little gear icon ) in my status bar.
I've also flashed Magisk root and an optimizer app called " L Speed Manager " but im not sure that would be my problem because i had the Magisk root with hadesRom before this update .
I'll appreciate if anyone can actually help me. thanks !
ItzMatt said:
Hello, So i recently Flashed the new version of hadesRom ( V.11.0 ) into my S8 ( SM-G950FD ) and I'm facing a problem that i never had before, my Screen freezes for like 5 or 6 seconds when im doing some actions for example when the device is locked and i turn the screen up and swipe to unlock , it freezes for 5 sec. or when i press the Settings ( the little gear icon ) in my status bar.
I've also flashed Magisk root and an optimizer app called " L Speed Manager " but im not sure that would be my problem because i had the Magisk root with hadesRom before this update .
I'll appreciate if anyone can actually help me. thanks !
Click to expand...
Click to collapse
Welcome to the forum!!
factory reset from within the phone and then again via recovery, flash the stock firmware, let it boot, do initial login information and allow updates, root as you did before, flash twrp, boot to twrp, wipe all, reinstall
Youdoofus said:
Welcome to the forum!!
factory reset from within the phone and then again via recovery, flash the stock firmware, let it boot, do initial login information and allow updates, root as you did before, flash twrp, boot to twrp, wipe all, reinstall
Click to expand...
Click to collapse
thanks!
im kinda confused. do u mean that i have to flash the stock Rom then wipe it and flash the custom rom again ?
ItzMatt said:
thanks!
im kinda confused. do u mean that i have to flash the stock Rom then wipe it and flash the custom rom again ?
Click to expand...
Click to collapse
unfortunately, yes. When your phone is exhibiting these symptoms, the nuclear bomb method is the best route to go