Related
HI, everyone
i got a problem with my defy recently.
i was running CM7 by Epsylon3.
As we all know, this rom comes with defy basebandswitcher v4.0, and it works well.
Yestoday, i want to update this "BBS" to v4.1. but when i uninstall v4.0 and install v4.1(http://forum.xda-developers.com/show....php?t=1203297), open it , it shows "unable to detect your baseband configuration, it's possibly damaged."
then i reinstall v4.0, but i cant find it in app drawer. i'm sure it's installed and i can see it in "setting-->applications-->manage applications" also in "dev tools-->package browser".
i tried the method in this thread: http://forum.xda-developers.com/showthread.php?p=21844497 . I renamed "system/etc/motorola/bp_nvm_default" and reset it to default use v4.1. but no new filefolder "bp_nvm_default" generated. and the problem still exist.
i also flashed offical SBF file 3.4.2_179-4.4(VFSBLUR) , 3.4.2_177-005(NORDIC) and reflashed CM7. still cant find app with v4.0 and the same message with v4.1.
Edit:half fixed... I reflashed stock sbf (different versions) several times , then flash CM7-11 again, after a bootloop, pull out the battery, power up, the "BBS" v4.0 bundled worked normally. but v4.1 still doesn't work.
Another question, i got a FOTA (com.motorola.process.system) FC. Maybe i should repost another thread. There is no responding here. Sorry for my poor english....
Ok this is a really strange Problem. I have two notes. On both I flashed the s5 port from Fahadali. Both had v6 on them and everything was awesome. He left development though so I continued the Project trying to make a "v7" Version, while doing that after I flashed the modified v6 many times but suddenly it softbricked. All I did Change though were some apks.
I've done this many times before with other roms without any Problems at all.
Then I reflashed stock NF4 through Odin and the newest twrp. Flashed v6 (the original non modded version) and it softbricked again...
I tried again, same result. I tried to Flash other recoveries, other bootloaders, other fw's through Odin and a lot more but: nothing.
Everytime I Flash v6 it breaks. I tried to Flash v5 and then suddenly: It worked! I tried to Flash other roms like Omega, and they work aswell. Only the v6 Version doesn't.
So if that's the case and the phone itself is clean (wiped 100 times Flashed stock even with a pit file) the Rom must be corrupted right? So I checked the md5 and well it was correct. I redownloaded and still: same md5. I checked the md5 on the note aswell. I tried using a sd Card instead and still: the same result.
In the meantime my other note worked perfectly, even with my modded Rom. So I continued to work on the v7 using that one. And then after like 14 flashes: the same Problem on that one aswell.
In detail:
I use twrp. And get into the Aroma installer of the Rom. It installs without any Errors whatsoever. Then I reboot.
And now the important part: the kernel has not been flashed cause it's not showing up in red (the rom's using a custom kernel).
This doesn't happen when I use the v5 Rom(still), and never happened before even with the v6. So I even tried flashing the kernel afterwards trough Odin and it gets successfully flashed. But the Rom still doesn't boot...
This means though that because of the kernel not being flashed (even though in Aroma it Shows that it does) even the rest might not get flashed. It only wiped the System Partition and that's it. But then the question remains why did it work before?? And why does it work for all the other People that have flashed it? And why did it work on mine until I flashed it more than 14 times?? And why does v5 and all the other roms still work fine?
I really don't get why this happens. Some v6 files have to still be on the device somehow, or idk. It's impossible cause I wiped but who knows. I've never seen anything like it, neither has the original dev of the Rom.
I Need to get v6 working, else I can't continue to build this Rom. Which is a big Problem for all who wants the s5 Rom.
I hope someone knows what to do. Thank you for your time.
Pls help me out guys, im just a newbie. So i flashed the latest nightly CM12.1 and when it booted up, system UI has stopped appeared and i cant get rid of it. I think i didn't re-enable android debugging before flashing it. Is there any way i can enable android debugging before i flash the rom and gapps again? Pls help me out guys. I think i broke my phone.
You don't need to enable debugging, its just that latest cm12.1 build is broken, I just reflashed myself because of that systemui crash, you need to reflash too. You can use version with date 2015-04-16, and then update from the phone using cm integrated updater to version 2015-05-11, because version 2015-05-13 is broken.
Same thing happened to me this morning after I flashed the Nightly of 2015-05-13. I downloaded the Nightly with CyanDelta to reduce the download size and flashed in thorough recovery. After my device booted, I noticed my wallpaper changed and I kept getting "Unfortunately, SystemUI has stopped" error. But it kept showing up every 1-2 seconds making the device unusable. So I just flashed the Nightly of 2015-05-12 which was working and the error stopped showing. Thanks to CyanDelta that keeps a copy of the old Nightly after installing a new one.
I hope that you still have the "stable" Nightly on your device to roll back to the previous Nightly. If you have access to a computer, you might be able to download it directly from CM's website, transfer it thorough USB and flash it with Recovery. That would be the only solution I can come up with beside restoring a NANdroid Backup. But I'm no pro in Android stuff, maybe someone can come up with another solution.
ExcaliburUser said:
Pls help me out guys, im just a newbie. So i flashed the latest nightly CM12.1 and when it booted up, system UI has stopped appeared and i cant get rid of it. I think i didn't re-enable android debugging before flashing it. Is there any way i can enable android debugging before i flash the rom and gapps again? Pls help me out guys. I think i broke my phone.
Click to expand...
Click to collapse
Thanks for the info bro. :good:
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
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?