I am on stock rom and rooted using the Super SU method. The only things I've flashed are the wifi fix, and edited build.prop to unlock tethering. My camera app will not open, and I get this error every single time. Doesn't work in instagram, snapchat, nothing. Anyone know what may be causing this?
Anyone? I would really like to get my camera working again
had the same problem today. restarted the phone and it worked again
ckret said:
had the same problem today. restarted the phone and it worked again
Click to expand...
Click to collapse
I've restarted several times even gone so far as to install a new OS. I'm thinking about undoing the changes just to fix this.
Try booting in Safe mode
ckret said:
Try booting in Safe mode
Click to expand...
Click to collapse
Camera still doesn't work
your cam may be disconnected from the motherboard. try claiming warranty
Wiped and installed the AOKP ROM and that fixed it.. Could've been the ROM or could've been the wipe, although I wiped several times before and it didn't fix it.
did you get the error again?
I had the same problem and I installed AOKP rom which fixed it at the beginning but after less 1 day the error back again.
now I'm on stock rom .35 (rooted with Magisk) and no camera error so far after 4 days
As far as i know, it is due to custom kernel, you may have installed that.. try flashing stock rom without any custom kernel..
Mayanknagpal.nm said:
As far as i know, it is due to custom kernel, you may have installed that.. try flashing stock rom without any custom kernel..
Click to expand...
Click to collapse
yes, I had custom kernel first time I got the error.
but then I got it also with custom rom.
now I'm on stock rom and stock kernel....but does it mean that I can never flash custom rom/kernel because of that error?
marcol87 said:
yes, I had custom kernel first time I got the error.
but then I got it also with custom rom.
now I'm on stock rom and stock kernel....but does it mean that I can never flash custom rom/kernel because of that error?
Click to expand...
Click to collapse
Custom roms do not have that error... and on stock rom you can use elementalX 2.0 , it is made for the .67.. so the camera issue is resolved.. i think this will help
I had this error on Stoneware .67 (stock based ROM) and resolved it by dirty flashing Stoneware and Magisk v.13 again.
and I had this error also on AOKP rom
I have been having this problem on the Stock ROM, non-rooted, for quite some time now. I have no idea what's causing this error. When I open it sometimes, it just throws an error. If I close it and open it again, it works as it should. It's very annoying.
I had the same thing, flashing roms didnt fix it so i flashed stock via RSD lite and everything was back to normal.
Same issue here, completely stock unrooted. This is not the first Android device I've had that's struggled to connect to the camera consistently... how hard can it be?
Can people getting this error try to disable the image stabilisation in video mode please? One of the errors I see when downloading a bug report refers to the stabilisation code and I've not had the "please restart camera" message since switching it off. Could be coincidence though as it's not like I get it every time the camera loads...
Hello ,
I tried rooting my Moto G5 using Moto G5 toolkit (flashing superSU). t
Then I flashed TWRP and Flashed the WLAN_CUSTOM
Now i get that generic warning screen of unlocked boot loader however My phone is not rooted. and I cant open camera at all , getting error as " Camera Busy - Camera unable to start. If this happens again, please power off your phone and restart."
Can someone help me fix this camera issue? or just help me to revert back as it was previously no root nothing, I guess this TOOLKIT has some bugs in it.
Any help will be appreciated as I am newbie with this android development.
the.MindHacker said:
Hello ,
I tried rooting my Moto G5 using Moto G5 toolkit (flashing superSU). t
Then I flashed TWRP and Flashed the WLAN_CUSTOM
Now i get that generic warning screen of unlocked boot loader however My phone is not rooted. and I cant open camera at all , getting error as " Camera Busy - Camera unable to start. If this happens again, please power off your phone and restart."
Can someone help me fix this camera issue? or just help me to revert back as it was previously no root nothing, I guess this TOOLKIT has some bugs in it.
Any help will be appreciated as I am newbie with this android development.
Click to expand...
Click to collapse
I had the same issue as you after using the toolkit, did you fix it?
Related
First of all I know there's another thread about this, but the guy seemed to be able to fix this problem by rebooting his phone so I'm making a new thread.
Today I flashed CM13 on my Nexus6P and it all worked fine until I tried starting the camera, which gave me the error mentioned in the title. Restarting the phone and erasng the app's data didn't work either.
Also everytime I boot my phone it shows me an "your device is corrupted" screen (not the bootloader unlocked screen) and when the phone starts it shows me something like "there's a problem with your phone, it might not work properly".
Is this my fault or is it a CM13 issue and how do I fix it? (I'm using today's official CM13 build with Open Gapps Mini arm64 for android 6.0)
Ju43 said:
First of all I know there's another thread about this, but the guy seemed to be able to fix this problem by rebooting his phone so I'm making a new thread.
Today I flashed CM13 on my Nexus6P and it all worked fine until I tried starting the camera, which gave me the error mentioned in the title. Restarting the phone and erasng the app's data didn't work either.
Also everytime I boot my phone it shows me an "your device is corrupted" screen (not the bootloader unlocked screen) and when the phone starts it shows me something like "there's a problem with your phone, it might not work properly".
Is this my fault or is it a CM13 issue and how do I fix it? (I'm using today's official CM13 build with Open Gapps Mini arm64 for android 6.0)
Click to expand...
Click to collapse
the error when booted can be resoled by flashing the latest vendor img, or at least the one relevant to your roms version.
took me about 2 weeks to figure this out because no one would give me the slightest hint when i asked.
the error screen when it first tries to start i havent been able to resolve, and am thinking there may be none.
not sure what your camera issue could be, but i have seen cam issues from the kernel, when the switch to 6.0,1 first began to merge.
maybe test another kernel, other than that i dont know.
Samehere
Ju43 said:
First of all I know there's another thread about this, but the guy seemed to be able to fix this problem by rebooting his phone so I'm making a new thread.
Today I flashed CM13 on my Nexus6P and it all worked fine until I tried starting the camera, which gave me the error mentioned in the title. Restarting the phone and erasng the app's data didn't work either.
Also everytime I boot my phone it shows me an "your device is corrupted" screen (not the bootloader unlocked screen) and when the phone starts it shows me something like "there's a problem with your phone, it might not work properly".
Is this my fault or is it a CM13 issue and how do I fix it? (I'm using today's official CM13 build with Open Gapps Mini arm64 for android 6.0)
Click to expand...
Click to collapse
I'm facing exactly the same issue. The camera works fine when I flash a stock based ROM like pure nexus or digitalhigh but as soon as I flash an aosp based ROM or cyanogenmod like chroma,screw'd,benzo. The camera says couldn't connect to camera and nothing seems to work. I've wiped cache, data but still no progress.
I even tried the flashable camera.zip but didn't work.
Problem Solved !!!
Ju43 said:
First of all I know there's another thread about this, but the guy seemed to be able to fix this problem by rebooting his phone so I'm making a new thread.
Today I flashed CM13 on my Nexus6P and it all worked fine until I tried starting the camera, which gave me the error mentioned in the title. Restarting the phone and erasng the app's data didn't work either.
Also everytime I boot my phone it shows me an "your device is corrupted" screen (not the bootloader unlocked screen) and when the phone starts it shows me something like "there's a problem with your phone, it might not work properly".
Is this my fault or is it a CM13 issue and how do I fix it? (I'm using today's official CM13 build with Open Gapps Mini arm64 for android 6.0)
Click to expand...
Click to collapse
Just flash the MBD08M.img via fastboot, then flash CM13 on top of it, restart the phone. The Camera won't work yet, now go to Benzo Rom and use his flashable vendor image for MMB29M via Recovery and Reboot. And it works like charm ! =D
You can also flash him flashable camera.zip, to get the stock camera
wrahul31 said:
Just flash the MBD08M.img via fastboot, then flash CM13 on top of it, restart the phone. The Camera won't work yet, now go to Benzo Rom and use his flashable vendor image for MMB29M via Recovery and Reboot. And it works like charm ! =D
You can also flash him flashable camera.zip, to get the stock camera
Click to expand...
Click to collapse
Thanks, I have reverted to stock ROM but I might try it soon
On my note3 (n900t), after I install any rom, which I've tried CM11, CM13, ResurrectionRemix v5.6.0 and 5.6.5, and the latest version for lollipop. Every time, it will install successfully via twrp, get to the welcome/language select screen, then the screen will go black, i.e. off. Pressing buttons or tapping the screen still turns the haptic motor, but does nothing, and the back/menu lights come on for a split second at a time, and sometimes spaz out turning on and off on their own.
these are the guides I followed, if it helps:
CM13: androiding.how/download-note-3-cm13-rom-marshmallow/
CM11: Just the wiki
RR: galaxynote3root.com/sm-n9005-galaxy-note-3-roms/resurrection-remix-rom-w-android-6-0-1-for-galaxy-note-3-marshmallow/The video in this one shows it working on a n900t, so it isnt a model compatibility thing
Is there something I've done wrong here? How can I fix this and install one of these?
(sorry about the links, I made an account to try and find help)
zxsq said:
On my note3 (n900t), after I install any rom, which I've tried CM11, CM13, ResurrectionRemix v5.6.0 and 5.6.5, and the latest version for lollipop. Every time, it will install successfully via twrp, get to the welcome/language select screen, then the screen will go black, i.e. off. Pressing buttons or tapping the screen still turns the haptic motor, but does nothing, and the back/menu lights come on for a split second at a time, and sometimes spaz out turning on and off on their own.
these are the guides I followed, if it helps:
CM13: androiding.how/download-note-3-cm13-rom-marshmallow/
CM11: Just the wiki
RR: galaxynote3root.com/sm-n9005-galaxy-note-3-roms/resurrection-remix-rom-w-android-6-0-1-for-galaxy-note-3-marshmallow/The video in this one shows it working on a n900t, so it isnt a model compatibility thing
Is there something I've done wrong here? How can I fix this and install one of these?
(sorry about the links, I made an account to try and find help)
Click to expand...
Click to collapse
Did you do all the wipes? On TWRP I always press advanced(I don't use factorey reset), then select everything but internal storage and SD, then I flash and it boots just fine.
robertofelce said:
Did you do all the wipes? On TWRP I always press advanced(I don't use factorey reset), then select everything but internal storage and SD, then I flash and it boots just fine.
Click to expand...
Click to collapse
Yep, I'm downloading the stock rom so i can get it working again, but I really want to try the rr marshmallow releases.. :|
zxsq said:
Yep, I'm downloading the stock rom so i can get it working again, but I really want to try the rr marshmallow releases.. :|
Click to expand...
Click to collapse
Remember that rr marshmallow releases don't work for SM N900. I guess that your phone is sm N9005. Right?
If it is, is awkward that you can't flash a rr marshmallow ROM
You should be in the T-Mobile note 3 forum?
Cm12.1 for the hltetmo: https://download.cyanogenmod.org/?device=hltetmo
zxsq said:
Yep, I'm downloading the stock rom so i can get it working again, but I really want to try the rr marshmallow releases.. :|
Click to expand...
Click to collapse
got exactly the same problem....Tried to flash repair stock rom with pit, with success, but doesn't change anything
can flash 5.0 stock or 5.1 port rom but not CM or AOSP..
if you find what happen....
Hi, I've had the same issue on my Note 3 N9005. I thought it was a problem caused by Knox, so I opened the original bootloader and I deleted every Knox file; then I flashed it and it works. I tried this solution with the Resurrection Remix Rom v5.6.5, but when I updated to v5.6.7 it gave me the same problem. After a sleepless night I realized that, being the problem related to hardware components (the screen), and being impossible that such components were broken, I thought that the real problem was the kernel, so I tried to flash a compatible kernel with the Marshmallow 6 version of Android and it finally works. The kernel in question was the NetHunter one (Kali Linux), that I flashed even when I flashed the bootloader, without noticing.
rikymatteo97 said:
Hi, I've had the same issue on my Note 3 N9005. I thought it was a problem caused by Knox, so I opened the original bootloader and I deleted every Knox file; then I flashed it and it works. I tried this solution with the Resurrection Remix Rom v5.6.5, but when I updated to v5.6.7 it gave me the same problem. After a sleepless night I realized that, being the problem related to hardware components (the screen), and being impossible that such components were broken, I thought that the real problem was the kernel, so I tried to flash a compatible kernel with the Marshmallow 6 version of Android and it finally works. The kernel in question was the NetHunter one (Kali Linux), that I flashed even when I flashed the bootloader, without noticing.
Click to expand...
Click to collapse
My note 3 smnN900t is doing that same thing and it sucks because I know I did everything perfectly!! What Kernel were you able to flash for it and where did you download it from? By the way thanks in advance for any help and info you can give!!!
Wrong forum
forum links .
http://forum.xda-developers.com/showthread.php?t=2574886
Please help I am having the same issue. Did anyone find a solution for this ?
Hello,
I have posted this on the cyanogenmod forum but everyone seems to be on holiday as I'm getting no replies. I'm hoping someone on here can help.
I recently had CM12.1 running on my S5 SM-G900F for about six months with no problems. I then switched over to CM13 and used that for about a month without any problems.
I decided to go back to CM12.1, I flashed the same CM12.1 Snapshot file that I had been using previously and it installed without error but when I rebooted the phone it would crash and reboot in a loop during start up. I wiped the phone and tried the install again about four or five times having the same problem until on the final attempt it managed to load the OS. Now that I have the OS running I cant connect to WIFI, the 'back' and 'recent apps' buttons on the phone don't respond (the home button does work), the camera app doesn't work (I get the error 'Can connect to Camera') and it keeps crashing and restarting on reboot. Everything else seems to work but the phone seems sluggish and there may be other errors that I haven't come across yet.
I thought that there may be a problem with the zip file I was flashing so I downloaded it again but it did the same thing. I've tried wiping and reinstalling several times but I get the exact same problems. The file I'm flashing is:
cm-12.1-20151007-SNAPSHOT-YOG4PAO333-klte.zip
If I go back to CM13 everything works fine so the problem is only with CM12.1.
I'm at a lost to explain why this keeps happening as I've had this running fine on my phone previously and wiping the phone and starting again doesn't do anything to solve the problem.
Any ideas please?
Come on people! Have a guess, I'm really stuck here!
I myself have not installed any custom roms on my s5 yet (bc of knox 0x0 lol) but try reverting back to the stock rom and then install cm12.1 again, maybe it could work.
Thanks, but I've tried that. Both stock rom and CM13 work without a problem. The issue only seems to be with CM12.1.
Can you tell what bothered you to go away from cm13 back to cm 12.1?
caned_monkey said:
Thanks, but I've tried that. Both stock rom and CM13 work without a problem. The issue only seems to be with CM12.1.
Click to expand...
Click to collapse
ezantera said:
Can you tell what bothered you to go away from cm13 back to cm 12.1?
Click to expand...
Click to collapse
CM13 sucks!!! snapchat and instagram keeps on crashing, now I'm using resurrection remix 5.7.3, that sucks too!!
Plz help me!!!!
Im installing custom rom in sm core prime 360H via twrp but its shows error number7
How to fix it..???
Any one help me plz i need it
Probably your internal storage if full or something. Which ROM were you installing anyway?
rms112 said:
Probably your internal storage if full or something. Which ROM were you installing anyway?
Click to expand...
Click to collapse
I tried every custom rom but same issue
Error code 7
My phone storage is almost 70%free
Plz help me to solv this
Are you sure you're using ROM built ONLY for G360H? None of us faced that error. Also remember Roms made for other device won't work and you may hard brick your device.
See here for more.
https://forum.xda-developers.com/showthread.php?t=2522762
rms112 said:
Are you sure you're using ROM built ONLY for G360H? None of us faced that error. Also remember Roms made for other device won't work and you may hard brick your device.
See here for more.
https://forum.xda-developers.com/showthread.php?t=2522762
Click to expand...
Click to collapse
Yes in 100% sure its 360H stock rom
I also try ins and inu both stock rom but issue is same
Can u tell me which stock are you use
Bdw are you indian....? Because my English is lil bit week?
rms112 said:
Are you sure you're using ROM built ONLY for G360H? None of us faced that error. Also remember Roms made for other device won't work and you may hard brick your device.
See here for more.
https://forum.xda-developers.com/showthread.php?t=2522762
Click to expand...
Click to collapse
I use this method also which is given in link but same issue ?
Idk man. You should probably try flashing official stock firmware using Odin. Its really easy. Then flash twrp by dreamstar. And start flashing custom ROMs.
I was on stock of Saudi Arabia. But I never used it after we got various CM builds..
I am on RR 5.8.3 by hash now.
Thnx for ideas
my problem solved
Now Installed​ lineage 7.1
Bdw how to close this Thread ?
rms112 said:
Idk man. You should probably try flashing official stock firmware using Odin. Its really easy. Then flash twrp by dreamstar. And start flashing custom ROMs.
I was on stock of Saudi Arabia. But I never used it after we got various CM builds..
I am on RR 5.8.3 by hash now.
Click to expand...
Click to collapse
RR 5.8.3 working fine
I trywd this but home button and resent apps cnt shows
Any idea about it...
rms112 said:
Idk man. You should probably try flashing official stock firmware using Odin. Its really easy. Then flash twrp by dreamstar. And start flashing custom ROMs.
I was on stock of Saudi Arabia. But I never used it after we got various CM builds..
I am on RR 5.8.3 by hash now.
Click to expand...
Click to collapse
RR 5.8.3 working fine ??
I trywd this but home button and resent apps cnt shows
Any idea about it...
Works fine with me. RR beta 1 based on 7.1.2.
You should ask on that thread of ROM. Maybe hash can help you!
Good luck.
Help i'm not sure but i think i might have bricked my sm-g360h.
HELP I'M NOT SURE BUT I THINK I MIGHT HAVE BRICKED MY SM-G360H. When i had some issues with my phone, I used twrp to flash cyanogenmod 12 custom rom on my phone some two weeks ago and it flashed properly. After a number of issues, i decided i wanted to go back to the stock rom. so i downloaded the firmware from sammobile, installed odin and flashed it with odin. when the flashing was done successfully, my phone rebooted instead of giving me the screen of a newly launched phone it went to the home screen, and had a pattern lock screen and tried my pattern lock from when i was on cyanogenmod 12 and it unlocked it. and gave me the screen of a newly lauched phone but before i could continue with startup, it rebooted immediately and each time it get to the lock screen, it goes to the screen with the samsung logo after some few seconds and then come back to the lock screen please help what do i do?
PS: one of the issues i had that made me want to return to the stock rom was the fact that i couldn't change my screen lock to none or swipe after i decided to use pattern on the cyanogenmod
yemialabipurpose said:
HELP I'M NOT SURE BUT I THINK I MIGHT HAVE BRICKED MY SM-G360H. When i had some issues with my phone, I used twrp to flash cyanogenmod 12 custom rom on my phone some two weeks ago and it flashed properly. After a number of issues, i decided i wanted to go back to the stock rom. so i downloaded the firmware from sammobile, installed odin and flashed it with odin. when the flashing was done successfully, my phone rebooted instead of giving me the screen of a newly launched phone it went to the home screen, and had a pattern lock screen and tried my pattern lock from when i was on cyanogenmod 12 and it unlocked it. and gave me the screen of a newly lauched phone but before i could continue with startup, it rebooted immediately and each time it get to the lock screen, it goes to the screen with the samsung logo after some few seconds and then come back to the lock screen please help what do i do?
PS: one of the issues i had that made me want to return to the stock rom was the fact that i couldn't change my screen lock to none or swipe after i decided to use pattern on the cyanogenmod
Click to expand...
Click to collapse
Sounds like problem of dirty flash not hard brick.
Here's what you should do.
1) go to twrp recovery using power + vol up
2) wipe everything except storage
3) Flash cm 13 beta 5 or 6 ( the latest beta) or lineage OS or RR
4) if the problem still exists, then used Odin to flash stock ROM and repeat steps 1 to 3
Also don't use cm 12. Its EOF and you won't get any bug fixes and updates.
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.