Tried searching the forum but couldn't find anything similar.
I rooted my ideos x5 with super one click, installed clockwork mod (perfect recovery by genekolar) and then installed genekolar's newest cyanogenmod [unofficial]. Tried installing 2 times with different downloads, wiping everything both times but I get no service or battery status. I checked my sim card, battery, booted the phone multiple times and checked my APN settings, the phone just doesn't find anything.
I would like to have gingerbread on my phone without installing the official one.
I also tried the MIUI rom but it stuck to the booting screen blasting that welcome jingle full volume every 3 seconds.
Any solutions?
Thanks!
This has been written for 1000000 times. You must update to official 2.3.5 if you want to use .35 kernel ROMs. If locked bootloader is what scares you then you dont need to worry because blefish already found a way to unlock it (http://forum.xda-developers.com/showthread.php?t=1457490). If you still dont want to update to offcial 2.3.5 then you can use .32 kernel ROMs
Oh, my search-fu wasn't good enough this time. Being noob 'n all. Thank you for informing me! I'll change this to solved and leave it here if anyone else is having the same problem
Thank you!!
Hello everybody,
I've searched en tried many of the solutions that were giving in the topics on this forum, but none of them worked for me. I hope you could help me.
I got my phone (red lens) to the point where I flashed JORDN_U3_97.21.51 with RSD v4.9 (as mentoined in the All-in-One Defy Guide). The phone worked and I was able to install 2nd Init and tried to flash a new ROM (tried several times with different ROMS like CM7, MIUI, WIUI and some Motorla ROMS). Each time I would end in a bootloop, after which I flashed JORDN_U3_97.21.51 again to get it working again.
Then I found this thread. I flashed it and got an Asian bootanimation followed by the Red Motorola Logo with a animated Blur-sign which I recognise as being android 2.2. However the phone ends up in a bootloop. The only thing I can reach now is the Bootloader. Also after this happened I couldn't flash back to JORDN_U3_97.21.51 anymore.
Could it be that I've got a non-downgradebale ROM installed now? What is the proper way to solve this problem? Or is there something I'm doing wrong?
Thanks in advance for all of your help!!
have you tried reading here? http://forum.xda-developers.com/showthread.php?t=966537
Hi,
I'm trying to use Multiboot on my defy (Red lenses and GB kernel). My original rom is the latest CM9 by Quarx.
Every ROM I installed (I tried MIUI V4, XIUI and CM10, all for Defy+) I get com.android.phone FC and, I think its because of this error, i cannot find network (yes, I tried to switch my baseband to the correct one).
I tried Multiboot v0.6.1 and v0.5.1 and get the same error. I tried v0.7 with TWRP, but with this I stuck at Motorola logo.
Its the firist time i'm trying to use multiboot, I did all the steps of more than 1 tutorial and give me the same error. Anyone know something I may have missed? I'll keep trying and if I got something i'll post here.
Thanks.
did you get multiboot working?
if not, what error does it gave??
and what steps did you followed???
Basically I instaled multiboot V0.6.1, then installed Multiboot Manager Free and created an image with cache: 150Mb, data 250Mb, and system: 350Mb. Then I flashed one of the ROMs tha I mentioned.
I get it working, I can load the system, conect via wifi, navigate and etc, but after startup I get com.android.phone FC and get no signal. This happened with all the ROMs tha I've installed.
EDIT:
It seems that I could solve it, I uninstalled Multi Boot Manager and installed Vibhinna, deleted the old system image and did everything again. Now I get no errors.
Thanks.
You should also be aware that if you have a GB base ROM you should download the Defy+ versions of the ROMs you want to use in multiboot.
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.
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?