[Q] OTA update not working - Nexus 4 Q&A, Help & Troubleshooting

I have a nexus 4 which I rooted successfully and installed cm 10.1 on android 4.2.2 factory. I installed one of the nighty roms last week and it has been working fine.
today I tried to flash the cm-10.1-20130304-EXPERIMENTAL-mako-M2.zip which was an OTA update.
I used the update option in settings and after updating to cm-10.1-20130304-EXPERIMENTAL-mako-M2.zip successfully I wasn't sure what to do,
I knew that I had to install the gapps again but wasn't sure how. So went back to square one, booted into recovery, did a factory reset, cache wipe, delvick cache wipe and reinstalled cm-10.1-20130304-EXPERIMENTAL-mako-M2.zip and then installed the gapp package. After that my my google apps don't work, have done restore with Titanium backup and still not working . Don't know what to do.
I have gone back and wiped cache and delvic cache again and reinstalled the gapps but still none of google apps will run.
should I do a factory reset and start the whole procedure over again and reinstall everything?

Do a full wipe, flash cm10.1 and gapps and I recommend flashin Francis kernel. Make sure its the latest
Sent from my Nexus 4 using xda premium

Related

Rebooting when installing an APP (Tranquility 3.6)

Hello,
I recently installed tranquility 3.6. I cleared the cache and installed via Rom Manager. I was running OTA 2.3.340 and the install went fine. I rebooted and had no bootloop or anything.
The phone booted fine and runs fine but I can no longer install any apps. I cleared the markets cache and all that and it still would not work.
I also cannot install any app through Astro manually.
When I cleared the cache it removed the Rom Manager recovery, since I can no longer access it.
My delima is I can no longer install anything to reinstall a new rom.
Now I would like to know if the System only 2.3.340 SBF will fix this or not. I read online going into the stock recovery and doing a factory reset would work as well.
I REALLY need this back working
I fixed this problem by booting into recovery and clearing data/factory reset and clearing the cache.
Sent using dx/xda app
I did the same thing as the post above. Fixed everything for me
I think that's a common problem for Tranquility. I had to wipe and install it a few times to get everything working properly. No issues since then though.
Sent from my DROIDX using XDA App
had similar problems
http://forum.xda-developers.com/showthread.php?t=895311
i wasn't able to factory reset from recovery, however i was able to factory reset from inside Android which then booted it into recovery just fine (this was after SBF'ing the first time)
apparently doing a factory reset will fix tranq

[Q] Correct wipe/flash procedure

Disclaimer: I'm used to my old Evo 4G and use a triple wipe script built into my recovery (smelkus) whenever I flash a rom. It pretty much wipes everything.
For the Nexus 7, what needs to be wiped to flash a rom? I did a factory reset, wiped data, wiped cache, wiped system, wiped dalvik-cache, and then flashed a new rom, but I wasn't sure if all that was necessary. I'm using the latest TWRP recovery.
If I'm moving from one rom based on a jelly bean version to another based on the same version, am I ok?
Can I assume upgrading to a new version of the same rom that I don't have to wipe? (I know this one is rom specific, but in general.)
Can I leave data and will that retain my apps? Otherwise, I use Titanium Backup religiously on my Evo and now on my Nexus 7.
I searched within some of the rom instructions as well as the rooting guides, but didn't see anything specific as to what to wipe. Some threads seem to say just factory reset and maybe dalvik-cache.
Instructions with what to wipe usually come in the original post of each ROM. Usually the same ROM with different version only requires a cache wipe while moving between different ROM's requires a full wipe/reset + dalvik.
Worse comes to worse you try something and it doesn't boot and you get back into recovery and fix it.

[SOLVED] Remove old play apps?

I flashed a new ROM using Philz CWM but I cant install anything from Google Play as it says its already installed.
I did wipe data/factory reset as well as wipe cache partition before installing the rom.
I believe my old apps are still installed but I don't know how to remove them.
Answer: Downloaded GApps from wiki.rootzwiki.com/Google_Apps and flashed in CWM.

[Q] Quarx 4.3 Rom: Settings are restored after reboot and playstore not working

Hello Guys,
I have came back to tinkering with my defy and I understand that Quarx's new rom has some bugs but I haven't seen or read where this is happening? So everytime I reboot the settins are restored (wifi, background, time, etc.). I came from Quarx's 4.1.2 rom with full wipe and fresh install of 4.3 rom. Another problem is that I also flashed TJKV's minimal gapps for 4.3 and market crashes right away and now my browser is also doing the same which it hadn't before. I have been through worse with this phone but now I can't seem to get pass this problem.
Motorola Defy Green Lens
Using Bootmenu v2.2-beta
Recovery-Twrp v2.6.0.0
Try a clean install. Wipe system, data and cache. Then install cm10.2, and gapps. I generally remove a couple apks from the system partition after installation
Sent from my MB526 using Tapatalk 2
thekguy said:
Try a clean install. Wipe system, data and cache. Then install cm10.2, and gapps. I generally remove a couple apks from the system partition after installation
Sent from my MB526 using Tapatalk 2
Click to expand...
Click to collapse
Hey there, I did wipe system, data, and cache but I think the problem is that every time I do it in twrp it says failed but it also says completed. The log says that it failed to mount data and system so I think this is causing the problem.
I used aroma to wipe sys, data, and cache before installing rom but still have the same error. Browser and playstore is currently not fc on me anymore and it is just that the settings aren't being saved after reboot.
Good, now convert data and cache to ext4 from boot menu
Sent from my MB526 using Tapatalk 2

[Q] Flashing various TW Lollipop fw over existing CM12 fails

Hello,
actually I'm using a SGS4 I9505 with cm-12-20150304-NIGHTLY-jfltexx and CWM 6.0.5.1.
I've tried to flash several TW Lollipop firmware wich i found in the I9505 forum:
1. Kushan+Touchwiz+Lollipop+Lite+Rom+v.1.2
2. S4_Echoev42_EchoePop2_020315
3. OA7-2.1F
4. XXUHA07-v2.01
Before flashing any oft this firmwares i made a factory reset, wiped both caches and installed the modem Firmware via Odin.
After flashing firmware # 1 and 2 my phone was stuc in a bootloop (only Samsung Galaxy S4 Logo appears).
Flashing firmware #3 and 4 fails and cwm reports error 7.
Flashing cm12 afterwards isn't a problem and runs fine.
I think the wipe fails or doesn't work properly. Is it enougth to select factory reset in cwm and wipe the dalvik cache manualy?
What can I do?
With besteht regard
Mirko (NemesisMF)
What if it is a recovery problem?
Thought about that too.
Should i try twrp or philz?
I switched to Philz Recovery and flashed S4 Echoe Rom v42 without any Problems.
CWM seems to have a problem to falsh TW Lollipop images ower an existing CM12 an the I9505.
You need to do full wipe not just cache.
ranger4740 said:
You need to do full wipe not just cache.
Click to expand...
Click to collapse
As I wrote above I did a factory reset before flashing and wiped the caches with cwm. If that is not enougth it would be nice to explain what else I have to wipe or post a link.
While using philz recovery the factory reset for clean system is enougth and the new System is working fine.
Factory wipe is not full wipe, you need to do a full wipe as in format to install new rom, phillz recovery has this feature can't remember exactly where, I think its under advanced.
Just have a look in the sub menus.
Just to explain it better when you do a full wipe it deletes every part of the existing
Rom including the system, data and cache and some other stuff completely removing the android operating system, so unless the rom you install does a wipe before install parts of the existing system will remain and can cause boot issues. For example as you've already discovered you are trying to install a tw rom over an existing cyanogenmod 12 installation which Will cause it to hang on boot.
NemesisMF said:
As I wrote above I did a factory reset before flashing and wiped the caches with cwm. If that is not enougth it would be nice to explain what else I have to wipe or post a link.
While using philz recovery the factory reset for clean system is enougth and the new System is working fine.
Click to expand...
Click to collapse
Do you mean a factory reset from within Android itself? If so, then that's a complete obsolete step. When before flashing a rom you should perform a factory reset, then they always mean a full wipe from the recovery. You need to do a full wipe from the recovery. That means the /system partition is being wiped. You will see it in the screen during the wipe if it wipes /system.
But it also could have been a problem of CWM. I don't think it is being updated anymore, so better use TWRP or Philz.

Categories

Resources