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?
Related
Hello,
I recently rooted my sgs4 gt-i9505 to the goolge edition using a YoTube tutorial on how to do so. Everything worked fine at the start but when I tried to install the PAC man rom, it jus stayed in the loading screen.
I restarted and tried rebooting but to no avail. I went back into the recovery mode and wiped the phone (divlac, cashes and system) then I reinstalled the google rom to find my wifi was not working. I tried the same process again, wipe- reinstall. Now I can't receive calls, the wifi doesn't work, home button only works on double tap, pull down status bar works but nothing in displayed.
My question is, does anyone have any ideas on how I would return my device to normal or know a full proof recovery and rom I can use that will correct these problems.
I am in the UK if that makes any difference.
Thanks for all and any help.
Matt
Matt.graham said:
Hello,
I recently rooted my sgs4 gt-i9505 to the goolge edition using a YoTube tutorial on how to do so. Everything worked fine at the start but when I tried to install the PAC man rom, it jus stayed in the loading screen.
I restarted and tried rebooting but to no avail. I went back into the recovery mode and wiped the phone (divlac, cashes and system) then I reinstalled the google rom to find my wifi was not working. I tried the same process again, wipe- reinstall. Now I can't receive calls, the wifi doesn't work, home button only works on double tap, pull down status bar works but nothing in displayed.
My question is, does anyone have any ideas on how I would return my device to normal or know a full proof recovery and rom I can use that will correct these problems.
I am in the UK if that makes any difference.
Thanks for all and any help.
Matt
Click to expand...
Click to collapse
You could try to go back to stock and check if everything still works there.
Did you flash the correct modem/baseband for the ROM / your carrier? There is a thread in general for all the modems. Chances are with a KitKat ROM you need to update your modem. Read that thread and give it a go. The file is about 15mb and takes a minute to flash in Odin. Failing that go back to stock.
Nothing in status bar: that's what it looks like in stock, you can use 2 fingers for the quick settins. Installl WANAM XPOSED fromwork for more tweaks and options!!
Home button double tap: that's the way it works on the google edition, that's just it. BUT wanam xposed can change this with the Gravity Box module!! You could try the Echoe 2.2 kitkat rom it has xposed pre-installed.
Keep in mind things look blanker and less functional as you no longer have samsung touchwiz which adds a LOT of stuff to the stock experience!
One more thing: ALWAYS make a nandroid backup before flashing ANYTHING at all, you never know when you will need it. Backup the nandroid to your PC also just in case, things go missing/ get deleted! T
First of all I would like to state that I am running echo-rom, I would like to have posted in there but the thread is closed.
My first problem is that the expandable volume menu does not work, this happened to me before with other roms (all on TW) but I couldn't be bothered until now. Whenever I click the gear icon which should expand, it doesn't work. It works before (until I do something?). Anyway I flashed the rom yesterday and didn't bother configuring/customizing it until today. I will try to describe anything I did until the point I noticed it broke again.
I enabled xposed framework, with the modules: wanam xposed, enable battery stats for kitkat, gravitybox, app-settings and xposed torch.
I tweaked some stuff in wanam xposed and in the echo customization center.
Anyway I don't really know what caused it, if no one knows why I will try to pay attention next time when it happens.
The second problem is that whenever I try to swipe down to open my notification bar it doesn't want to work half the time. On my home screen the statusbar turns black (instead of transparent), so there is some sort of registration of touch? I proceed to let go of my finger and and then try again. I also thought that I could have misplaced my finger but I don't know why the statusbar would turn black then.
If anyone knows or has encountered this problem before please share,
much appreciated.
I dunno know but i tried exposed once with a slimrom and it messed my phone up really bad upto the point everything was force crashing. To me i think exposed is your problem. Try wiping data, cache, dalvik, and format system and boot with cwm recovery then flash official firmware for you phone. DO NOT USE 4.3 FIRMWARE IF YOUR ON A 4.4 ROM!! Look for 4.4 rom instead. Sammobile good site but need registraion and slow download for free users (about 1hour) after that try instakking. Your fav rom without xposed. Im 80% sure it will work
So I fixed it, I disabled both gravitybox and wanam xposed and after the reboot volume expand worked again, then I enabled wanam xposed again and it still worked. Either way gravitybox caused it, or it was caused by a conflict between the two.
Also the statusbar problem, my rom has an option where you double-tap the battery icon to change the style of it, I noticed by trying to swipe down from the battery icon it doesnt work. So there you have it. Problem solved
The reason is really simple. You don't read before you install the modules.
You can't use Gravitybox on a TW based rom. It's states that in the description. Gravitybox is for aosp only!
Same applies for the post from 189cutter. Wanam Xposed is only for TW based roms. Slimrom is clearly no TW based rom.
So if you want to use the modules, read if they are for your rom. Also make sure that there is no overlapping in functions, because that could cause strange problems as well.
Point taken but im never ever ever gonna use xpose or such things like it lol now im using cm m9 and its perfect lol
I have an XT1644. I rooted it and installed Xposed about a week ago. Out of nowhere, today the camera no longer works. I have not installed any new apps or done anything else to the phone. When I open up the camera, the image is all black and the onscreen buttons are not responsive. I have to wait a bit and then it says "camera error camera must be restarted". I have rebooted into safemode and factory reset and the problem persists. Anybody have any idea whats going on?
roygbiv859 said:
I have an XT1644. I rooted it and installed Xposed about a week ago. Out of nowhere, today the camera no longer works. I have not installed any new apps or done anything else to the phone. When I open up the camera, the image is all black and the onscreen buttons are not responsive. I have to wait a bit and then it says "camera error camera must be restarted". I have rebooted into safemode and factory reset and the problem persists. Anybody have any idea whats going on?
Click to expand...
Click to collapse
I flashed stock and that fixed it, but then I again rooted and the problem returned. If I boot into "factory mode" the camera works. On safe mode it doesn't, so I'm guessing it's not a hardware problem.
i had this problem yesterday.
Rooted no problems, Installed Xposed stable version, and then out of the blue after 1 day my camera wasn't working.
Even after i disabled the modules it still was not working.
I had to restore a backup i made the night before....
coolhead said:
i had this problem yesterday.
Rooted no problems, Installed Xposed stable version, and then out of the blue after 1 day my camera wasn't working.
Even after i disabled the modules it still was not working.
I had to restore a backup i made the night before....
Click to expand...
Click to collapse
I fixed it by flashing the newest stock firmware. The old stock firmware was not only messing up the camera, but other things as well. Ever since I did that, I've had 0 problems. Rooted and Xposed have been working just fine for weeks. Give it a shot.
roygbiv859, where do you get the "latest firmware" and how to flash it?
I am hitting this problem and my phone says software is already up to date. Same thing as you guys -- camera and flashlight only work in factory mode.
I have Xposed and root as well, but I remember things used to be working all together.
I noticed that in "factory mode" cellular network does not work, and battery never charges, otherwise I do not really mind running in that mode.
I saw a version number "MPJ24.139-48" at bottom of status page, is that the firmware number? Looks like I am already on the latest.
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.
Love the V20's but this is the second one that has had this problem of the phone stating that the second screen or the system UI has stopped working and I have to close the app and the screen flickers until I reboot the whole phone. Anyway to fix this?
Rooted or not? Need little more details. If rooted... Stock rom, custom rom, kernel, ect.?