On flashing a Custom Rom, my phone gets stucked with continous FC ("Unfortunately Phone Crashed","Press OK") just after the phone boots.
I had faced the same problem earlier so someone on XDA suggested to use twrp recovery. Then i flashed the purity rom and it worked fine, but then as you may know now, as PA is out, so flashed it and again i'm getting continuous fc error....
currently i'm using purity rom, stock kernel and twrp recovery (2.6.3.3)
I would flash back to a stock 4.2.2 and start over. I find that this is the only way I can install certain roms.
audit13 said:
I would flash back to a stock 4.2.2 and start over. I find that this is the only way I can install certain roms.
Click to expand...
Click to collapse
I already did this and again i'm facing the same problem
htrapy said:
I already did this and again i'm facing the same problem
Click to expand...
Click to collapse
Strange. Are you updating the bootloader and radio before flashing a 4.4 rom?
Are you doing a factory reset???? And flashing a proper gapps after ROM? You should always do this when going from one ROM to another. Sometimes a manual format of /system is necessary also.
no i am not updating my bootloader and radio before flashing (rather didn't know if i had to update them,fyi i bought my nexus 4 this september)....and yes i'm doing a factory reset (using the wipe option in twrp recovery which warns clearing of data, cache and dalvik memory)
Related
Hey,
Today in between flashing a new ROM i went back to 4.2.2 cm10.1.2, just to check some things out before flashing a 4.3 ROM that i was intending to do in the first place.
However after having reverted to 4.2.2 when i went and install the 4.3 ROM i noticed i had no signal, since then i've tried flashing the radio and boot from 4.3 Factory Image via fastboot, tried installing a different 4.3 ROM, all with no success.
What can I do?
Btw i still get signal in 4.2.2
Thanks.
Mottz said:
Hey,
Today in between flashing a new ROM i went back to 4.2.2 cm10.1.2, just to check some things out before flashing a 4.3 ROM that i was intending to do in the first place.
However after having reverted to 4.2.2 when i went and install the 4.3 ROM i noticed i had no signal, since then i've tried flashing the radio and boot from 4.3 Factory Image via fastboot, tried installing a different 4.3 ROM, all with no success.
What can I do?
Btw i still get signal in 4.2.2
Thanks.
Click to expand...
Click to collapse
Check APN settings?
How do I do that?
Also the phone app just crashes totally when I try to do anything with it, even entering airplane mode triggers that.
Sent from my Nexus 4 using Tapatalk 4
You should do a clean wipe before you flash 4.3 from an older version, do a factory reset and wipe the system partition, then flash 4.3 rom.
via xda app
It might have to do with TWRP.
http://forum.xda-developers.com/showthread.php?p=45323439
Try flashing TWRP 2.6.0.0 then proceed from there to flash your rom.
I guess i forgot to mention, i did a clean install, i factory reset before reverting.
And i have TWRP installed, I've tried several ROMs and in all of 4.3 ROMs i dont have signal and the Phone app FCs when i try to use it.
On that note, does TWRP Factory Reset wipes System Partition?
Factory reset does wipe system partition except /data/media.
Flash TWRP 2.6.0.0 (this version)
Factory reset
Flash Rom
Flash Gapps
Flash Modem
Flash Kernel
Flash Supersu
Wipe caches
Reboot
Btw, here is some insight on what to wipe in TWRP:
http://teamw.in/whattowipe
Oh I just saw your previous post, didn't understand it at first but now that I think about it I do actually have 2.6.1.0.
Ill try what you said and report back.
Thanks.
Sent from my Nexus 4 using Tapatalk 4
It worked, thanks alot!
Hey guys,
I'm not a total scrub at flashing roms and there's still a bunch of things that I don't understand. I'm pretty positive that I flashed Slimrom correctly but here's the situation.
Started on 4.2.2 Slimrom
Reboot to TWRP recovery
Format factory reset/format data, system, cache, dalvik cache
Flash Slimrom 4.3 stable build 1
Successfully reboots into 4.3
Okay now here's the weird part.
The first time I rebooted back into recovery to flash gapps. After I flashed gapps and tried to reboot into the rom, the phone freezes at the screen with "google" and the unlock sign on the bottom. The only way I can get it to boot into the rom again is if I reformat/reset EVERYTHING (including format data) and reflash 4.3. After a few tries of messing around with not wiping dalvik/cache and stuff I realized that even if I don't flash gapps it still freezes on the google screen. So here's my main problem
After flashing 4.3 slimrom, the phone boots into the rom only once. If I try restarting my phone it freezes on the "google" screen.
Anyone know what I'm doing wrong?
Just to clarify it's a LG Google Nexus 4 mako.
Sorry if I'm being redundant. I just want to give as much detail as possible. If you need anymore info let me know!
Thanks
ms3195 said:
Hey guys,
I'm not a total scrub at flashing roms and there's still a bunch of things that I don't understand. I'm pretty positive that I flashed Slimrom correctly but here's the situation.
Started on 4.2.2 Slimrom
Reboot to TWRP recovery
Format factory reset/format data, system, cache, dalvik cache
Flash Slimrom 4.3 stable build 1
Successfully reboots into 4.3
Okay now here's the weird part.
The first time I rebooted back into recovery to flash gapps. After I flashed gapps and tried to reboot into the rom, the phone freezes at the screen with "google" and the unlock sign on the bottom. The only way I can get it to boot into the rom again is if I reformat/reset EVERYTHING (including format data) and reflash 4.3. After a few tries of messing around with not wiping dalvik/cache and stuff I realized that even if I don't flash gapps it still freezes on the google screen. So here's my main problem
After flashing 4.3 slimrom, the phone boots into the rom only once. If I try restarting my phone it freezes on the "google" screen.
Anyone know what I'm doing wrong?
Just to clarify it's a LG Google Nexus 4 mako.
Sorry if I'm being redundant. I just want to give as much detail as possible. If you need anymore info let me know!
Thanks
Click to expand...
Click to collapse
Are you flashing the right Gapps package? Be sure you are flashing the latest 4.3 one.
abaaaabbbb63 said:
Are you flashing the right Gapps package? Be sure you are flashing the latest 4.3 one.
Click to expand...
Click to collapse
Yep I'm positive. I redownloaded both the 4.3 rom and gapps package multiple times just to make sure. Also it doesn't reboot even if I don't flash gapps. Doesn't boot at all if I flash both the rom then gapps at the same time.
bump
then, wipe data/factory reser and flash the stock rom. the rom might be the problem
davinnwilliam said:
then, wipe data/factory reser and flash the stock rom. the rom might be the problem
Click to expand...
Click to collapse
It works for everyone else though. It's Slimrom 4.3 stable build 1.
Rom isn't the problem.Slim rom beta 1(4.3) is super stable. Use any version of twrp recovery other than 2.6.1.0 and wipe system+data,flash slim rom,flash slim gapps,reboot.
Note: if you flashed franco kernel then this may be the issue for your bootloop also you may want to upgrade your bootloader and radio to 4.3 versions(bootloader more important)
Hi I hope you can help me with this,
I was on a custom 4.3 rom running on old bootloader. I then
updated to 4.4.2 rom but my camera is not working only a black screen and giving
me a warning message " Camera failed" and once that happens
the whole system lags. I've read around that it could be a hardware
problem but when I switched back to the 4.3 rom the camera is working
smoothly again. I have tried 3 different 4.4.2 custom roms but same issue persists.
My question is could this have anything to do with my bootloader? I am planning
on flashing a stock 4.4.2 firmware with the new bootloader to see if that helps but what
worries me is if this doesn't help then I have no way anymore to go back to
a 4.3 firmware where my camera still works. Can you help me point to a solution
to this problem? Or which stock firmware I should flash to test if my camera
will work on that firmware.
Did you fully wipe before flashing?
Lennyz1988 said:
Did you fully wipe before flashing?
Click to expand...
Click to collapse
Yes full wiped in Aroma, Formatted Int/ext card from Philz recovery, restored factory
from rom didn't help either.
What custom rom did you flash? Do you use the correct modem for the old bootloader?
Lennyz1988 said:
What custom rom did you flash? Do you use the correct modem for the old bootloader?
Click to expand...
Click to collapse
I have tried Phoenix ROM, GoldenEYE , ECHO ROM, I am not sure if
I am using the right modem though I just flashed the file suggested on this page.
I'm on the Phoenix rom and it's running stable for me. I am also running on the old bootloader.
I had troubles at first after upgrading to 4.4.2, but after I wiped /system in recovery, everything worked.
You could try it. Make sure to backup /efs to your external sd or pc. Backup your entire internal sdcard, because it will be wiped. I didn't know that, so I lost everything on my sd
Perform a full wipe. Then wipe /system from the recovery (i used clockwork recovery). After that just flash and don't install any tweaks in aroma.
Hello, xda. I have a lot of time using the Motorola android phones, but faced with the problem of firmware change on my xt907 for the first time. I'm on stock 4.4.2 (182.46.10) with root, custom recovery, but now would like to try CM or gummy.
I met a problem that after cm-11-20140914-NIGHTLY or any other ROM installed from recovery, during the first boot, after language selecting my phone starts cyclic reboot.
I tried cwm 6.0.3.9 and twrp 2.8.0.0, 2.7.1.0, doing all wipes before (or/and after) installation. I try to install this ROMs over 4.4.2 stock and on the clean system (after erase /system). But nothing worked. With RSDLite I can always switch back to 4.4.2 I can always switch back to 4.4.2, but the inability to use CM bother me.
I have original xt907 from verizon, but I use it abroad (gsm).
I will be glad to hear any ideas and suggestions about this situation, many thanks
And sorry for my pigin-English
Do you wipe data before installing the ROM?
Klen2 said:
Do you wipe data before installing the ROM?
Click to expand...
Click to collapse
Sure. Before and/or after. From fastboot (first time), from recovery. And i`m telling about clean stock 4.4.2 from RSDLite
I need some help, I really don't know what to do anymore..
I've installed the optimized cyanogenmod 13 and now my sensors don't work. It works randomly for about 10-20 minutes then stops. The only sensor that works without any problem is the light one..
I don't know what can I do. Can this be from hardware, even working sometimes?
All the sensors are recognized by phone, they just don't work.
I've already jumped into a lot of ROMs and nothing. I've already done a full wipe (system, data, caches, internal) and installed official stock ROM and nothing.
Now I'm on lollipop 9.0 and I can't get this to work even for 10 minutes, but I know that on other rom it will work for about 10 minutes.
What can I do?
Did you install the latest official stock or just any stock rom with Odin?
audit13 said:
Did you install the latest official stock or just any stock rom with Odin?
Click to expand...
Click to collapse
I installed the latest stock rom right from sammobile.
audit13 said:
Did you install the latest official stock or just any stock rom with Odin?
Click to expand...
Click to collapse
I don't know if has anything to do, but if you have a s4 with root, can you please verify if in your folder "persist" have anything? It stays right in the root.
Thanks!
Weird that stock didn't fix the issue. You also performed a factory wipe from stock recovery before booting the newly-flashed ROM for the first time?
Sorry, I don't have an s4 with me at the moment. I can check later today.
audit13 said:
Weird that stock didn't fix the issue. You also performed a factory wipe from stock recovery before booting the newly-flashed ROM for the first time?
Sorry, I don't have an s4 with me at the moment. I can check later today.
Click to expand...
Click to collapse
Do you mean the recovery that comes with stock rom? I never used him. My wipes I always do from TWRP
I really don't know what else I can do. I don't want to change de motherboard :/.. I still think that is from software
You should try wiping with stock recovery.
audit13 said:
You should try wiping with stock recovery.
Click to expand...
Click to collapse
Install the stock rom again, then turn off phone, power+volume up+home and do a wipe data/cache factory reset? Is this different from the TWRP wipe?
Maybe I can do this wipe via settings on the system?
On lollirom 9.0 I can't get them working even for 10 minutes
Sometimes, a wipe using stock recovery works better than a wipe using a custom recovery.
Flash with Odin and use stock recovery to wipe before booting the stock ROM for the first time.
audit13 said:
Sometimes, a wipe using stock recovery works better than a wipe using a custom recovery.
Flash with Odin and use stock recovery to wipe before booting the stock ROM for the first time.
Click to expand...
Click to collapse
Ok.. I'll try to do this and I post the result here. This not working, there's anything else I can do?
Not sure what else to try as flashing stock and wiping with stock recovery usually fixes software glitches.
audit13 said:
Sometimes, a wipe using stock recovery works better than a wipe using a custom recovery.
Flash with Odin and use stock recovery to wipe before booting the stock ROM for the first time.
Click to expand...
Click to collapse
Again, only light sensor working.. anything else?
The sensorhub test gives me PASS.
Everything was working before flashing cm13?
audit13 said:
Everything was working before flashing cm13?
Click to expand...
Click to collapse
Yes, perfectly. Never had this issues before optimized cyanogenmod 13 :/. That's why I think its from software, but I have no idea what to do anymore..
I am at a loss too. The phone shows the correct imei, baseband, and bootloader?
audit13 said:
I am at a loss too. The phone shows the correct imei, baseband, and bootloader?
Click to expand...
Click to collapse
Yes. The phone is 100% ok, just the sensors not working.. Now even for 10 minutes is working :/, just the light sensor
Anything else I can do? :/
Dont know if a logcat can help, but..
I just started the phone and searched for "gyro"
As you can see, gyro_sensor was not found.. Maybe we got something here?????
--edit--------
Searching now I found that this is something about .idc files, right in /system/usr/idc. I just don't know what file.. @audit13
How about flashing a custom rom that is based on the original stock rom?