Hey my camera was just running fine on my stock rom on my note 2. However when I installed custom rom (dn3 and omega), all it does was failed to connect to camera every time I try to load camera.
I tried a lot of things like safe mode, run another camera app, clear cache, wipe data, reinstalled a diferent rom etc, changed kernel from omega's stock to agni (omega's stock was causing me all my apps to FC) but I still could NOT get my camera to boot. I tried runnign the stock test thing *#0*# but only my front camera can boot while the back one FC.
Any ideas what I should do next?
(I have no idea which stock ROM to use and whether I can downgrade from 4.4.2 to 4.1.x or lower)
(I also have no idea whether I can go from R3 of my AGNI kernel to R2 without causing problems)
nikdimas said:
Hey my camera was just running fine on my stock rom on my note 2. However when I installed custom rom (dn3 and omega), all it does was failed to connect to camera every time I try to load camera.
I tried a lot of things like safe mode, run another camera app, clear cache, wipe data, reinstalled a diferent rom etc, changed kernel from omega's stock to agni (omega's stock was causing me all my apps to FC) but I still could NOT get my camera to boot. I tried runnign the stock test thing *#0*# but only my front camera can boot while the back one FC.
Any ideas what I should do next?
(I have no idea which stock ROM to use and whether I can downgrade from 4.4.2 to 4.1.x or lower)
(I also have no idea whether I can go from R3 of my AGNI kernel to R2 without causing problems)
Click to expand...
Click to collapse
I would suggest a full wipe including preload and cache / dalvik / data and flash ROM (DN3 V5+ works great) let ROM settle and try again if works then flash Agni Kernel R2 after
bunglebp said:
I would suggest a full wipe including preload and cache / dalvik / data and flash ROM (DN3 V5+ works great) let ROM settle and try again if works then flash Agni Kernel R2 after
Click to expand...
Click to collapse
yea did that but it only FCs everywhere on every app. :/
I tried another kernel (nadia) and until now no FCs.
What's the difference? What mistake did I make -_-" aren't kernel cross compatible?
Related
Hi everybody, apologize if this kind of question has been discussed before. I have did my homework and research in the dedicated kernel threads and the Q&A section, however, seems I am the only one that can't get custom kernels work on my phone, at all!
OK, here is my story. My S3 (ATT variant, i747) runs perfectly with AOKP (10/16 release) and CM10 (10/18 nightly), on default kernels come with them of course. However, after flashing the KT747 Ktoonsez's kernel, my phone goes crazy. It is suffering from random hot reboot, system freezing, core processes are killed randomly, black screen, no apps can be launched, and etc. Basically, my phone stops working. I have also tried the lean kernel (which has been proved working just fine in i747), which can't even get booted into OS. I am pretty sure I was following the suggested steps when flashing the ROM and kernel. Here are my steps:
1. Boot into recovery (I have tried CWM and TWRP, no differnce)
2. Make nandroid bakcup.
3. Full wipe: Format data -> wipe system -> wipe cache -> wipe dalvik cache.
4. Flash ROM -> flash gapp -> flash Kernel -> wipe cache -> wipe dalvik -> fix permission (I have tired wipe cache/dalvik before flashing kernel, no difference)
5. Reboot.
I clearly aware there was a big chance after 10/14 CM10 build about kernel, and I am pretty sure I am using the correct KT747-AOSP-JB-1016 release with my AOKP 10/16 build, but still, won't work at all.
Please let me know if I didn't anything wrong when flashing the kernel or ROM. Any suggestion is welcome. Thanks in advance.
Kevin
You may want to try not flashing the ROM and kernel together, meaning flash the ROM and gapps following all recommended instructions then reboot. After fully loading into android, boot back into recovery flash kernel, wipe cache/dalvik, fix permissions and reboot again. See if that helps. May also want to allow a couple reboots before you give up on the kernel, sometimes it takes a few for the kernel to 'settle.'
dntesinfrno said:
You may want to try not flashing the ROM and kernel together, meaning flash the ROM and gapps following all recommended instructions then reboot. After fully loading into android, boot back into recovery flash kernel, wipe cache/dalvik, fix permissions and reboot again. See if that helps. May also want to allow a couple reboots before you give up on the kernel, sometimes it takes a few for the kernel to 'settle.'
Click to expand...
Click to collapse
Thanks man, will try your method and report back.
once you flashed your ROM(aokp) you need to reboot and let the phone fully boot into android... after that reboot to recovery and try flashing your Gapp + kernel
don't forget all the wiping and fixing permission for each steps
edit: wow this tab was open for a long time i guess. there was no other answer when i wrote this browsing through my opened tabs.
dingrn said:
Hi everybody, apologize if this kind of question has been discussed before. I have did my homework and research in the dedicated kernel threads and the Q&A section, however, seems I am the only one that can't get custom kernels work on my phone, at all!
OK, here is my story. My S3 (ATT variant, i747) runs perfectly with AOKP (10/16 release) and CM10 (10/18 nightly), on default kernels come with them of course. However, after flashing the KT747 Ktoonsez's kernel, my phone goes crazy. It is suffering from random hot reboot, system freezing, core processes are killed randomly, black screen, no apps can be launched, and etc. Basically, my phone stops working. I have also tried the lean kernel (which has been proved working just fine in i747), which can't even get booted into OS. I am pretty sure I was following the suggested steps when flashing the ROM and kernel. Here are my steps:
1. Boot into recovery (I have tried CWM and TWRP, no differnce)
2. Make nandroid bakcup.
3. Full wipe: Format data -> wipe system -> wipe cache -> wipe dalvik cache.
4. Flash ROM -> flash gapp -> flash Kernel -> wipe cache -> wipe dalvik -> fix permission (I have tired wipe cache/dalvik before flashing kernel, no difference)
5. Reboot.
I clearly aware there was a big chance after 10/14 CM10 build about kernel, and I am pretty sure I am using the correct KT747-AOSP-JB-1016 release with my AOKP 10/16 build, but still, won't work at all.
Please let me know if I didn't anything wrong when flashing the kernel or ROM. Any suggestion is welcome. Thanks in advance.
Kevin
Click to expand...
Click to collapse
Kevin my phone is exactly having the same problem did you come to a resolution
Especially on aosp roms it might help to flash the rom, let it boot once, then boot into recovery and flash kernel, wipe cache & dalvik, and fix permissions.
Also i've heard that some people will have alot of reboots before the kernel starts running smooth and stable. Or you could just have a bad phone that doesn't like to be tweaked. If i were you i'd take advantage of that warranty and try to get a replacement.
sorry for being a newbie....but what do you mean by fix permissions? =/
ohaai said:
sorry for being a newbie....but what do you mean by fix permissions? =/
Click to expand...
Click to collapse
In cwm, advanced -> fix permissions
It fixes system file permissions. This could be why your having having FCS.
jefferson9 said:
In cwm, advanced -> fix permissions
It fixes system file permissions. This could be why your having having FCS.
Click to expand...
Click to collapse
ive tried so many different methods of flashing kernels and all of them result in huge problems with crashes and random reboots all methods posted earlier are a gigantic fail. Im returning this refurbished phone for another refurbished and will report back
droidfta said:
Kevin my phone is exactly having the same problem did you come to a resolution
Click to expand...
Click to collapse
No luck, poor me. I have given up and stuck with stock kernel comes with task's AOKP.
dingrn said:
No luck, poor me. I have given up and stuck with stock kernel comes with task's AOKP.
Click to expand...
Click to collapse
hey had the same exact problem. Got a new phone under warranty cpu temps run lower and stable under current kt747 kernel I'll wait a few more days before underclocking but it's defiantly the phone you just got a weak cpu like I did
Hi Guys,
I was wondering if anyone could help me with a strange issue I have.
When I flash to stock root ROM my phone works fine, including my camera, however, when I flash to ANY custom ROM my camera only works when my flash is off. If I turn the flash on the camera attempts to take a picture and then freezes and I have to do a battery pull to get it back on.
I will through a curveball here and say that I have had extremely limited success (but success nonetheless) when I use my original OEM battery.
The flash itself works fine as I can use apps like flashlight no problem.
Oh and app's from the Play store work fine as well w/ flash on.
Anybody experience this before? I have searched and found nothing,
Thanks everyone.
How are you wiping before flashing? I recommend wipe data, cache, dalvik, format /system.
And by "any" ROMs do you mean 4.2 ROMs or both 4.1 and 4.2?
Well the stock ROM was 4.1.1.
The thing is I've had this problem for a long time now so it would be on both 4.1 and 4.2.
New development though, I just re- flashed to PKD ROM and the flash works intermittently. It seems when I take a picture if something closeup with flash it works but when the subject is far away the camera app just goes black.
So, about your wipe procedures...
xBeerdroiDx said:
So, about your wipe procedures...
Click to expand...
Click to collapse
Sorry,
So when I flash a ROM I wipe data/factory clear dalvik and clear cache.
I've done that from stock to custom.
The next time you flash, have everything backed up/saved to your sd card or pay and follow the wipe procedures I recommended above. It wipes the OS completely off, leaving you a completely blank slate for the new rom. Have your desired rom and gapps on your micro sd card
Blender7 said:
Sorry,
So when I flash a ROM I wipe data/factory clear dalvik and clear cache.
I've done that from stock to custom.
Click to expand...
Click to collapse
You forgot to format /system manually in mount/boot, that causes a lot of errors (it caused a bootloop issue when going from stock to Slim for me)
Hi,
For about a few days, I can't flash any touchwiz based rom, even the ones I could flash without any problem before. After I flash any touchwiz rom, my phone goes into a bootloop cycle. Though I can boot into recovery and download mode with key combinations. I don't know when this happened for the first time but as far as I can remember, it would be after I flashed some 4.4 AOSP rom (could be Omnirom, I'm not sure though)
What I did to recover from boot loop:
- Wipe cache, wipe dalvik cache and reboot, no joy.
- Wipe cache, wipe dalvik cache, wipe data, reboot, no joy.
- Wipe cache, wipe dalvik cache, wipe data, wipe data/media, reboot, no joy.
- Pulled out the battery between these steps too.
At first, I thought something was wrong about the aroma installer itself because the phone was getting frozen during aroma installer setup screen, then I came up that it was caused due to my older CWM version, so I updated the recovery and it didn't freze again during installation.
And by the way, I've lost my efs partition during these processes, thankfully I've had a nandroid backup from a couple of months before.
Now I'm stuck with AOSP roms and the only way I can use a touchwiz rom is to flash the stock rom via odin. But I want to use the new leaked version based Note3 featured roms.
I've seen similar topics at S4 section but I couldn't be sure if I can do the exact steps for an N7100 international device.
I'm pretty familiar with linux system and I can use adb so I can provide any kind of information you need to diagnose this issue. Thanks in advance. Best regards.
HOW I SOLVED THIS PROBLEM
- Wiped everything (system, data, sdcard, of course internal sdcard)
- Flashed n7100 16GB pit file via odin
- Flashed stock rom via odin
- During these steps, I realized that my CSC code had been changed, I've corrected it acording to my country code
- Rooted my phone again
- Flashed CWM 6.0.4.3 recovery
- Flashed DN3 V3.1 rom
- Bingo, I successifully booted into DN3 rom but had no WIFI
- Flashed MJ5 bootloader
- Rebooted, then WIFI worked without a problem
- Setup my phone and did some restore
It's all good now. Thanks for everything, I hope these steps can help someone facing the same problem.
Guys, I really need some help.. Any idea about what might the problem be?
Sent from my GT-N7100 using XDA Premium 4 mobile app
Download HD wipe script,flash the script zip via cwm/philz then try installing the rom of your choice.
I found the script from tamirda's phoenix rom thread and is very useful:http://d-h.st/fWr
Full wipe cache and reset in recovery menu, clear everything, you should be up and running.
akp.ajinkya said:
Download HD wipe script,flash the script zip via cwm/philz then try installing the rom of your choice.
I found the script from tamirda's phoenix rom thread and is very useful..
Click to expand...
Click to collapse
Thanks for the reply. I flashed this superwipe script, then flashed DN3 rom but still I got stuck at Samsung Galaxy Note II screen boot loop. I really don't understand this. What am I missing? What would happen if I wipe the entire internal memory block, I mean the whole things, even the root partition too.. I'm thinking that maybe there's some file inside the root partition that prevents me to flash touchwiz roms or perhaps something wrong about touchwiz based roms' bootloaders.. I'm truely pissed..
(InsertNameHere) said:
Full wipe cache and reset in recovery menu, clear everything, you should be up and running.
Click to expand...
Click to collapse
Have you read my first message? I remember that I've mentioned I've done already what you ask me to do.. Believe me I wouldn't shoot a new thread if I could've solved my problem with such easy steps. I've already done so many wipes, including internal SD and whatsoever.. I'm really confused and NEED help. Thanks anyway..
I think you can go for the method you mentioned.But also give a try to start fresh i.e pit file flashing...wiping everything n installing stock rom then rooting,flashing custom recovery n then installing any TW custom rom.
Also give other TW based roms a try too.
Im having the same problem but after flashing kernels (e.i. saber & perseus).
Im currently running on Tigra rom. Is this a compatibility issue or im just missing something here too?
I came across flashing bootimg but this thread http://forum.xda-developers.com/showthread.php?t=1752270
is for One S, im not sure if will work on Note 2 & haven't tried it yet.
Any suggestions? help pls...
akp.ajinkya said:
I think you can go for the method you mentioned.But also give a try to start fresh i.e pit file flashing...wiping everything n installing stock rom then rooting,flashing custom recovery n then installing any TW custom rom.
Also give other TW based roms a try too.
Click to expand...
Click to collapse
Well, the problem is gone.
What I did was the things you said.
- Wiped everything (system, data, sdcard, of course internal sdcard)
- Flashed n7100 16GB pit file via odin
- Flashed stock rom via odin
- During these steps, I realized that my CSC code had been changed, I've corrected it acording to my country code
- Rooted my phone again
- Flashed CWM 6.0.4.3 recovery
- Flashed DN3 V3.1 rom
- Bingo, I successifully booted into DN3 rom but had no WIFI
- Flashed MJ5 bootloader
- Rebooted, then WIFI worked without a problem
- Setup my phone and did some restore
It's all good now. Thanks for everything, I hope these steps can help someone facing the same problem.
Happy to help you bro
Just like the title says. It's been a while since I've flashed a different ROM so I may be missing something simple. I'm currently using stock nexOgen 1.7 ROM, I was trying to flash one of two different CM ROMs and each time I had the same thing happen no data, the three buttons on the front wouldn't work and the keyboard wouldn't show up, it kept promoting a android keyboard force close. Each time I flash I'm wiping system, dalvik, cache, and data. I did not flash a different kernel just ROM and gapps. Let me know if I'm missing something.
Thanks guys
kazerak2 said:
Just like the title says. It's been a while since I've flashed a different ROM so I may be missing something simple. I'm currently using stock nexOgen 1.7 ROM, I was trying to flash one of two different CM ROMs and each time I had the same thing happen no data, the three buttons on the front wouldn't work and the keyboard wouldn't show up, it kept promoting a android keyboard force close. Each time I flash I'm wiping system, dalvik, cache, and data. I did not flash a different kernel just ROM and gapps. Let me know if I'm missing something.
Thanks guys
Click to expand...
Click to collapse
Maybe try going into recovery and wipe cache and davlik and fix permissions see if that straightens out the rom
well erm
I am now using cm11 linaro rom
1). before flashing this rom, i did follow instruction, at the part of format preload, it failed but i just keep on going to flash it
now, my camera is very lag, and during the panorama mode, it became worse than the stock rom
does that matter the camera problem ?
2). what is I wanna flash other custom ROM into my device, is there any difference between flashing custom rom from custom rom and from stock rom ? and is it just follow the instructions the gave ?
3). what if I want to flash back the same rom, should I follow the instruction again ? because i doubt that the "format preload" step affected my camera quality.
4). what if the format preload steps failed again, what shoud i do ?
I know its really lots of questions but im just about to start rooting and flashing my device one week ago
and so, i did follow the cultural here, search before ask, and i didnt get my answer
Thanks if you helping me out
wk0308 said:
well erm
I am now using cm11 linaro rom
1). before flashing this rom, i did follow instruction, at the part of format preload, it failed but i just keep on going to flash it
now, my camera is very lag, and during the panorama mode, it became worse than the stock rom
does that matter the camera problem ?
2). what is I wanna flash other custom ROM into my device, is there any difference between flashing custom rom from custom rom and from stock rom ? and is it just follow the instructions the gave ?
3). what if I want to flash back the same rom, should I follow the instruction again ? because i doubt that the "format preload" step affected my camera quality.
4). what if the format preload steps failed again, what shoud i do ?
I know its really lots of questions but im just about to start rooting and flashing my device one week ago
and so, i did follow the cultural here, search before ask, and i didnt get my answer
Thanks if you helping me out
Click to expand...
Click to collapse
1) Aosp roms are not on power with Stock samsung camera ,alternative to that would be using Lenovo camera (I use this while on AOSP roms),I dont think panaroma mode works on it but other features works really well and better than AOSP and on power with Samsung camera.
2) custom rom to custom rom meaning you are already rooted so you just need to flash the new rom after doing the wipes ,flashing a stock rom via odin and then flashing a custom recovery and then making the correct wipes and then flashing a custom rom (unless you download a stock pre rooted stock rom from xda ,you can flash it via custom recovery arleady and just do the wipes)
3) To avoid formatting preload (although not sure why it gave you error) but you could use TWRP recovery instead ,it works just as good with AOSP roms and to do the wipes follow this Go to wipe,click on Advanced Wipe and choose Dalvik Cache, Cache, System , Data & Internal Storage.Now go back to main menu and flash the ROM.
Hope this helps.
singhpratik87 said:
1) Aosp roms are not on power with Stock samsung camera ,alternative to that would be using Lenovo camera (I use this while on AOSP roms),I dont think panaroma mode works on it but other features works really well and better than AOSP and on power with Samsung camera.
2) custom rom to custom rom meaning you are already rooted so you just need to flash the new rom after doing the wipes ,flashing a stock rom via odin and then flashing a custom recovery and then making the correct wipes and then flashing a custom rom (unless you download a stock pre rooted stock rom from xda ,you can flash it via custom recovery arleady and just do the wipes)
3) To avoid formatting preload (although not sure why it gave you error) but you could use TWRP recovery instead ,it works just as good with AOSP roms and to do the wipes follow this Go to wipe,click on Advanced Wipe and choose Dalvik Cache, Cache, System , Data & Internal Storage.Now go back to main menu and flash the ROM.
Hope this helps.
Click to expand...
Click to collapse
1) So i can simply replace the camera with lenovo camera which i can get on play store ? and the not on power with samsung camera means the roms are usually not good with samsung camera ?
2) sorry what i mean is, do I have to wipe all those data or caches no matter what ROM i am in as my device is rooted and custom recovery installed ?
3) so the problem is now, can i straight away wipe the Dalvik Cache, Cache, System , Data & Internal Storage and straight away reboot system ?
wk0308 said:
1) So i can simply replace the camera with lenovo camera which i can get on play store ? and the not on power with samsung camera means the roms are usually not good with samsung camera ?
2) sorry what i mean is, do I have to wipe all those data or caches no matter what ROM i am in as my device is rooted and custom recovery installed ?
3) so the problem is now, can i straight away wipe the Dalvik Cache, Cache, System , Data & Internal Storage and straight away reboot system ?
Click to expand...
Click to collapse
1) I mean the AOSP cameras are not as good as Samsung Stock cameras.
2) Yup unless you are flashing an upgrade of the SAME rom (especially AOSP) then you can just install the ROM.re install gapps wipe cache and dalvik (your apps will remain intact) but if you are switching from AOSP to Touchwiz or vice versa full wipe is must.
3) No you cannot reboot system cause those options especially system ,data and internal storage wipes your phone basically NO ROM is installed on your phone so you need to go back in main menu of twrp choose install and navigate to external card and flash the desired ROM of choice
singhpratik87 said:
1) I mean the AOSP cameras are not as good as Samsung Stock cameras.
2) Yup unless you are flashing an upgrade of the SAME rom (especially AOSP) then you can just install the ROM.re install gapps wipe cache and dalvik (your apps will remain intact) but if you are switching from AOSP to Touchwiz or vice versa full wipe is must.
3) No you cannot reboot system cause those options especially system ,data and internal storage wipes your phone basically NO ROM is installed on your phone so you need to go back in main menu of twrp choose install and navigate to external card and flash the desired ROM of choice
Click to expand...
Click to collapse
budd i really have to thank you !!!
u helped me twice !!!
THANKSSS
hahahahahhaa
REALLY THANKS BROOOO HAHHAHAHA
singhpratik87 said:
1) I mean the AOSP cameras are not as good as Samsung Stock cameras.
2) Yup unless you are flashing an upgrade of the SAME rom (especially AOSP) then you can just install the ROM.re install gapps wipe cache and dalvik (your apps will remain intact) but if you are switching from AOSP to Touchwiz or vice versa full wipe is must.
3) No you cannot reboot system cause those options especially system ,data and internal storage wipes your phone basically NO ROM is installed on your phone so you need to go back in main menu of twrp choose install and navigate to external card and flash the desired ROM of choice
Click to expand...
Click to collapse
how do I replace the camera by the way ? o.o
wk0308 said:
how do I replace the camera by the way ? o.o
Click to expand...
Click to collapse
Just don't use the AOSP camera unless you want to delete it? Then either go to system/app or system/priv-app and search for the stock camera file on and delete it.
Lenovo camera from here install as normal apk