Database Info

[Q] Phone stuck "Optimizing apps" after upgrading rom

Long time visitor, first time poster.
Upgraded rom today when I found of there was an official 4.3 upgrade for the Verizon GS3. Looked around and found this one: http://forum.xda-developers.com/showthread.php?t=2600305 Before that, I was on the last official stock, flashed deodexed rom.
Installed rom zip via CWM, rebooted. After loading screen, it starts upgrading apps. It got stuck on 82 of 601. After 15 minutes, I booted into recovery and wiped cache (failed to do this during initial install, it never was a problem before). Reboot, gets stuck on 93 of 465. Hard reboot, total number keeps going down, but keeps sticking.
After several hard reboots (pulling the battery), I got it down to 1 of 1, but it won't go any further. It's been about an hour.
What do I do next?
While waiting for ideas, I'll hard reset, boot into recovery, wipe cache again, and see what happens.
Edit: Wiped cache partition from CWM, rebooted, still stuck at 1 of 1.

CaffeinatedGuy said:
Long time visitor, first time poster.
Upgraded rom today when I found of there was an official 4.3 upgrade for the Verizon GS3. Looked around and found this one: http://forum.xda-developers.com/showthread.php?t=2600305 Before that, I was on the last official stock, flashed deodexed rom.
Installed rom zip via CWM, rebooted. After loading screen, it starts upgrading apps. It got stuck on 82 of 601. After 15 minutes, I booted into recovery and wiped cache (failed to do this during initial install, it never was a problem before). Reboot, gets stuck on 93 of 465. Hard reboot, total number keeps going down, but keeps sticking.
After several hard reboots (pulling the battery), I got it down to 1 of 1, but it won't go any further. It's been about an hour.
What do I do next?
While waiting for ideas, I'll hard reset, boot into recovery, wipe cache again, and see what happens.
Edit: Wiped cache partition from CWM, rebooted, still stuck at 1 of 1.
Click to expand...
Click to collapse
I believe you may need to use ODIN to manualy re-flash the 4.3 update. NOTE: This will lock your bootloader, but seeing as how you have already upgraded it already is.

Mtsprite said:
I believe you may need to use ODIN to manualy re-flash the 4.3 update. NOTE: This will lock your bootloader, but seeing as how you have already upgraded it already is.
Click to expand...
Click to collapse
Do I specifically need to find a rom that is Odin flashable, or should I try another zipped package flashed through recovery?

CaffeinatedGuy said:
Do I specifically need to find a rom that is Odin flashable, or should I try another zipped package flashed through recovery?
Click to expand...
Click to collapse
Don't use Odin to flash the official tar file, you'll lock your bootloader and you'll be stuck.
Wiping dalvik cache should work, but if it doesn't then do this.
In recovery factory reset, wipe cache, wipe dalvik cache, format system, then format internal sd card (this will erase everything on your phone). Then reflash the rom again.
Sent from my SCH-I535 using Tapatalk 2
---------- Post added at 01:55 PM ---------- Previous post was at 01:53 PM ----------
Mtsprite said:
I believe you may need to use ODIN to manualy re-flash the 4.3 update. NOTE: This will lock your bootloader, but seeing as how you have already upgraded it already is.
Click to expand...
Click to collapse
His bootloader is not locked, he never upgraded to the official 4.3 ota.
Sent from my SCH-I535 using Tapatalk 2

BadUsername said:
Don't use Odin to flash the official tar file, you'll lock your bootloader and you'll be stuck.
Wiping dalvik cache should work, but if it doesn't then do this.
In recovery factory reset, wipe cache, wipe dalvik cache, format system, then format internal sd card (this will erase everything on your phone). Then reflash the rom again.
Click to expand...
Click to collapse
I wanted to try something else before formatting the card and having to deal with that, so I downloaded the zipped rom here http://forum.xda-developers.com/showthread.php?t=2591895
From CWM I wiped cache (again), wiped dalvik (again), and installed rom. On reboot, went through app optimization without any problems.
I'm not sure what the problem was, but I fixed it by using a different rom.
Thank you for the help.

[Q] Wipe Dalvik does not work on CWM recovery - stuck on boot screen (Help!) RAZR HD

Hi there,
Here is what I've done:
Started with stock ICS rom and USB Debugging ON
Unlocked the device via Fastboot and Motorola Unlocker Program unique code
Installed the latest CWM recoveryhttp://www.clockworkmod.com/rommanager image via Fastboot (V 6.0.4.4)
Done Wipe Data/Factory Reset + Wipe Cache + Wipe Dalvik (it worked the first time)
Installed CM11 KitKat Nightly Update (It does work since I have another XT925 with it and it is perfect)
Installed Updated GAPPS zip file
Restarted
Here is when things started to fail:
My screen was stuck at the Bootloader Unlocker warning - and yes, I've left it there for a long time and nothing happened
So I've followed this thread to get out of the stuck logo: http://forum.xda-developers.com/showthread.php?t=2260105
Now I get into the boot animation but it is stuck at it for hours
I've tried to perform another data wiping on CWM as suggested by other threads and Wipe Data/Factory Reset and Wipe Cache works but Wipe Dalvik doesn't. CWM doesn't show any errors, doesn't freezes or anything, just doesn't show the same feedback lines from when I do the Wipe Data/Factory Reset and Wipe Cache.
I've installed stable CM10 release but I still get stuck at CM10 boot animation.
The NOOB here would really apreciate some help since the phone belongs to my dad and he will be comming back to get it tomorrow :/
Thanks in advance guys!

dirceucorsetti said:
Hi there,
Here is what I've done:
Started with stock ICS rom and USB Debugging ON
Unlocked the device via Fastboot and Motorola Unlocker Program unique code
Installed the latest CWM recoveryhttp://www.clockworkmod.com/rommanager image via Fastboot (V 6.0.4.4)
Done Wipe Data/Factory Reset + Wipe Cache + Wipe Dalvik (it worked the first time)
Installed CM11 KitKat Nightly Update (It does work since I have another XT925 with it and it is perfect)
Installed Updated GAPPS zip file
Restarted
Here is when things started to fail:
My screen was stuck at the Bootloader Unlocker warning - and yes, I've left it there for a long time and nothing happened
So I've followed this thread to get out of the stuck logo: http://forum.xda-developers.com/showthread.php?t=2260105
Now I get into the boot animation but it is stuck at it for hours
I've tried to perform another data wiping on CWM as suggested by other threads and Wipe Data/Factory Reset and Wipe Cache works but Wipe Dalvik doesn't. CWM doesn't show any errors, doesn't freezes or anything, just doesn't show the same feedback lines from when I do the Wipe Data/Factory Reset and Wipe Cache.
I've installed stable CM10 release but I still get stuck at CM10 boot animation.
The NOOB here would really apreciate some help since the phone belongs to my dad and he will be comming back to get it tomorrow :/
Thanks in advance guys!
Click to expand...
Click to collapse
Mount usb from 6044.
Dl philz 6045, he has new ones now, 607... flashable version to your sd.
Flash philz
Reboot recovery
May be dl another rom copy just in case
There is a new wipe in philz more complete.
You may need to format data & data media.
Also see this link about 2 settings. Starts with: Now I am sure.... Philz link there too.
http://forum.xda-developers.com/showthread.php?t=2545120
Good luck.
---------- Post added at 07:07 PM ---------- Previous post was at 06:44 PM ----------
I made a flashable just for you at that link.

I was going to sleep but now back to work. I am going to do that. Let you know.
Enviado de meu XT925 usando Tapatalk

You are THE MAN!
Thank you AVIWDOOWKS! Just thank you very much! It worked like a charm!
This is the first time that I have come to XDA to ask for help and I now have my phone up and ready less than half an hour from posting my question!
Have a nice weekend!
aviwdoowks said:
Mount usb from 6044.
Dl philz 6045, he has new ones now, 607... flashable version to your sd.
Flash philz
Reboot recovery
May be dl another rom copy just in case
There is a new wipe in philz more complete.
You may need to format data & data media.
Also see this link about 2 settings. Starts with: Now I am sure.... Philz link there too.
http://forum.xda-developers.com/showthread.php?t=2545120
Good luck.
---------- Post added at 07:07 PM ---------- Previous post was at 06:44 PM ----------
I made a flashable just for you at that link.
Click to expand...
Click to collapse

Problem installing Android KitKat (either Omnirom or Cyanogenmod)

Hi!
I'm experiencing an annoying problem while updating my XOOM (MZ605) with the latest KitKat ROM.
I followed the instructions to repartition my device, and I tried using both Omnirom and Cyanogenmod roms, but I get the same error everytime.
In the step of wiping everything (but the SD card), I get a couple of messages saying that it was unable to mount cache to E: drive. TWRP recovery system says that the wipe process failed. Anyway, I went further in the steps, and I was able to flash the room and the gapps (it passes the BigPart partition check), but when I boot into system, my xoom stays stuck at the splash screen; it is not booting.
I tried both Omnirom and Cyanogenmod, and I get stuck in the same place. I thought I messed some part, so undone the BigPart, installed stock rom from motorola, and started over. But got the same problem.
I would liek to know if anyone know whats going on with the partiitoning, and if I can get rid of the mounting errors.
Thank you!

toiel said:
Hi!
I'm experiencing an annoying problem while updating my XOOM (MZ605) with the latest KitKat ROM.
I followed the instructions to repartition my device, and I tried using both Omnirom and Cyanogenmod roms, but I get the same error everytime.
In the step of wiping everything (but the SD card), I get a couple of messages saying that it was unable to mount cache to E: drive. TWRP recovery system says that the wipe process failed. Anyway, I went further in the steps, and I was able to flash the room and the gapps (it passes the BigPart partition check), but when I boot into system, my xoom stays stuck at the splash screen; it is not booting.
I tried both Omnirom and Cyanogenmod, and I get stuck in the same place. I thought I messed some part, so undone the BigPart, installed stock rom from motorola, and started over. But got the same problem.
I would liek to know if anyone know whats going on with the partiitoning, and if I can get rid of the mounting errors.
Thank you!
Click to expand...
Click to collapse
In your process of wiping...did you try to wipe just the cache by itself. When I got that error message i would go back to the main menu in recovery and just wipe the cache (or whatever giving me an error message) by itself.

Same problem here
gooniegoogoo2 said:
In your process of wiping...did you try to wipe just the cache by itself. When I got that error message i would go back to the main menu in recovery and just wipe the cache (or whatever giving me an error message) by itself.
Click to expand...
Click to collapse
Same problem here... I can't properly do some of the advanced wipes in the process of trying to install omni.
I did as you suggested and tried wiping them individually but to no success.
I am definitely not as fluent in this stuff as a lot of you on here are, but I am competent/confident enough to follow good instructions.
Somebody help please!

Cant install KitKat Roms
I am having the same issue and have done the same thing. Tried installing both CM and OMNI with no success. the recovery is telling me the came thing that it cannot mount E:\ 'cache' and other files i need to wipe.
Some one please help.

i was wondering...
i was wondering if the fact that i used to have a custom rom and then reverted back to stock (relocked the bootloader and unrooted successfully) last year before i attempted the omni install could be a factor?

But it worked before
ohDevious said:
i was wondering if the fact that i used to have a custom rom and then reverted back to stock (relocked the bootloader and unrooted successfully) last year before i attempted the omni install could be a factor?
Click to expand...
Click to collapse
I'm getting the same "can't mount cache" error when converting to Big Part - I had previously been running several Big Part roms, and had no problem with the conversion at that time - I then reverted back to stock (using VZW OTA's) for awhile, but want to give the Big Part roms another shot - I've tried several methods of reverting to stock, then coming back to install a 10.1 ROM, which is successful, but when I flash the Big Part TWRP and try the conversion, I get the cache mount error every time - I can revert to the "normal" TWRP, reformat, and re-install non-big part roms without a problem - help us Obi Wan! WTF?

I was getting the same thing as you guys. Stuck on splash screen. What I did to fix mine was under TWRP go to wipe, did factory reset wipe, then data wipe. Then mine worked for me. Takes about 3-5 minutes to boot on 1st start after wiping. Hope this helps.
---------- Post added at 08:25 PM ---------- Previous post was at 07:50 PM ----------
lightnuup said:
I was getting the same thing as you guys. Stuck on splash screen. What I did to fix mine was under TWRP go to wipe, did factory reset wipe, then data wipe. Then mine worked for me. Takes about 3-5 minutes to boot on 1st start after wiping. Hope this helps.
Click to expand...
Click to collapse
I forgot to mention click the format data tab under wipe and type yes.

I just had this same experience. I think the directions are somehow missing a step or we're misreading it.
lightnuup said:
I was getting the same thing as you guys. Stuck on splash screen. What I did to fix mine was under TWRP go to wipe, did factory reset wipe, then data wipe. Then mine worked for me. Takes about 3-5 minutes to boot on 1st start after wiping. Hope this helps.
---------- Post added at 08:25 PM ---------- Previous post was at 07:50 PM ----------
I forgot to mention click the format data tab under wipe and type yes.
Click to expand...
Click to collapse

A day not spent well
I am having the same issue all of you guys are having. I had 10.1 stingray (4.2.2) running well and thought it was time to try Kit Kat. Both the ROMs wind up the same way, a loooong running splash screen (over an hour before I manually rebooted). Over and over no mater how many ways I tried to wipe the XOOM I kept getting the Can't mount the cache message. I was able to revert back to 10.1 but I can't figure why others can make the install and we cannot. I have asked others on the forum but no one can answer the question?
Anyone? Thanks! Paddy

I was finally able to figure this out last night. I was looking at my cache and data formats and both were formatted as f2fs. I believe it's under wipe in the latest TWRP (2.7.1.0), there's an option on the left that shows you the format type of your drives. On non BigPart TWRP I changed the cache and data to ext4. Rebooted back into recovery, and followed the guide posted here to apply BigPart to my Xoom: http://forum.xda-developers.com/showthread.php?t=2506997 :: Then I was able to load Omni BigPart edition with no issues at all. I'd be happy to give more details if anyone wants. I'm in the office now, otherwise I'd post some snap shots. I'll update this when I get home.

has anyone recovered from the "unable to mount cache" error? I have followed all the information in this thread, checked out the relevant links all to no avail.
The only additional data I can provide is that when I go into the wipe menu (TWRP 2.7.1) / advanced / select cache / and "repair or change" I have all 0's for the cache size MBs. Repairing the cache or changing file system claims to be successful, but it's always 0 MBs. For grins I tried all of the above with TWRP 2.6.3 and had no better results.
Thanks in advance.

Tab 2 10.1 restart constantly

My "Galaxy Tab 2 P5100" constantly restarts. Has the stock ROM with root and cwm 6.0.1.
Only reboot if the tablet is in android system or power off.
In the recovery dont restart.
This is the problem:
If i make a factory reset, when the tablet restart, this fails.
In the CWM, wipe data/factory reset: data wipe complete successfuly. But when the tablet restart, the data dont wiped.
If i delete my pictures or unistall apps, when restart, the deleted pictures or apps are there again.
I flash TWRP or philz recovery whit odin: succesfully flashed, when restart cwm 6.0.1 is still there.
In the cwm i flash another custom rom: successfully flashed. When restart, nothing flashed, the tablet still in the stock original rom.
Odin back to stock fails at system write.

Something is really wrong
---------- Post added at 03:49 PM ---------- Previous post was at 03:48 PM ----------
Have you tried /system wipe?

shsagnik said:
Something is really wrong
---------- Post added at 03:49 PM ---------- Previous post was at 03:48 PM ----------
Have you tried /system wipe?
Click to expand...
Click to collapse
When i flash a custom rom , the installer format system, then write the new rom. In the recovery say successfully wiped and flashed, but when restart again, the original rom a data still there.
Odin start to write system, fails at the write, but the tablet boot to the original android system and data.

Try using adb to install recovery

shsagnik said:
Try using adb to install recovery
Click to expand...
Click to collapse
CWM v6.0.1.0 dont have the option to enable sideload.
ADB error: closed

[emoji51]

¿?

Maybe we must call someone by spamming other threads

I have the same problem :crying:
when in recovery mode, it says something like
"did not match sized '/system/csc/common/system/csc/....."
about wallpaper thing, with red font.
already wipe chace also factory reset, but after reboot, the internal memory still the same. the pictures, the apps.
flash via odin stuck at nand write, then failed.
I can enter the homescreen, but just for 5-7 seconds, then it will restart. then do the same cycles.
How to solve this? is this a hardware problem?
someone said about emmc bricked, he replace the mainboar with the new 1. its too expensive for me, especially for now, this tab no longer up to date compare to newest devices nowadays.
sorry for my english, my brain also got some brick :silly:

[SOLVED] Google Apps Not Working And Recovery Refusing To Open

About two weeks ago just before CyanogenMod's announcement of its closure I updated my Moto G2015 (1GB) to the latest nightly, which was CM14.1 released on the 25th of December, with its corresponding GAPPS version also released on the 25th of December (ARM, android 7.1, Full)
Yesterday the 7th of January my Google Apps decided that they didn't want to open, at first I thought it was just updating and since my battery was low I plugged in my device, I later realised that my device randomly went to a boot loop and stayed there. I grew impatient so I restarted the phone and went to the Recovery Mode (To Re-Flash the ROM), but to my annoyance the recovery (TWRP) just stayed on the 'Teamwin' logo forever, it would randomly go black then return to that logo. infuriated I turned on my phone and went to backup/reset and clicked 'factory reset'. it annoyingly booted me into recovery to reset the device, which of course I couldn't do.
Now the simple answer would have been for me to go and wipe the cache and data from 'google play services' and or 'launcher3' but I did, either it always shows 'calculating' preventing me from clicking 'manage space' or clearing 'cache' or when it did finally show, after I did click the button for the cache and or data to be cleared it would say 'calculating', and a quick check would discover that nothing was actually cleared.
Kind Regards, and Thank You to any help recieved,
NotSoGreat

Boot TWRP or CWM Recovery (not sure if it's still called CWM Recovery now that LineageOS has replaced it) with the command 'fastboot boot recovery.img' but replace recovery.img with your actual recovery image filename. If TWRP won't boot wait, sometimes a theme or corruption in the TWRP directory on internal storage can pause the startup of TWRP by several minutes, if that still fails boot CWMR and remove the TWRP directory or wipe internal storage.
Once you can get TWRP to boot properly, backup everything (MPT works in TWRP) and wipe and reflash, should be good to go.

acejavelin said:
Boot TWRP or CWM Recovery (not sure if it's still called CWM Recovery now that LineageOS has replaced it) with the command 'fastboot boot recovery.img' but replace recovery.img with your actual recovery image filename. If TWRP won't boot wait, sometimes a theme or corruption in the TWRP directory on internal storage can pause the startup of TWRP by several minutes, if that still fails boot CWMR and remove the TWRP directory or wipe internal storage.
Once you can get TWRP to boot properly, backup everything (MPT works in TWRP) and wipe and reflash, should be good to go.
Click to expand...
Click to collapse
Thanks for the reply, what you're saying makes sense and would probably work, but I found a simpler work around. I'm actually annoyed I didn't do it earlier.
So simply put, I downloaded my stock recovery which worked and then I just factory reset my device from there, that reset the CM14.1 ROM and let my Google Apps work again. Now about the recovery, I'm a bit skeptical about Re Flashing it, but I think I'll try it next weekend and post the results.

NotSoGreat said:
Thanks for the reply, what you're saying makes sense and would probably work, but I found a simpler work around. I'm actually annoyed I didn't do it earlier.
So simply put, I downloaded my stock recovery which worked and then I just factory reset my device from there, that reset the CM14.1 ROM and let my Google Apps work again. Now about the recovery, I'm a bit skeptical about Re Flashing it, but I think I'll try it next weekend and post the results.
Click to expand...
Click to collapse
Have you tried it since you wiped? It might just work now that the reset wiped internal storage...

acejavelin said:
Have you tried it since you wiped? It might just work now that the reset wiped internal storage...
Click to expand...
Click to collapse
I'll try now.

acejavelin said:
Have you tried it since you wiped? It might just work now that the reset wiped internal storage...
Click to expand...
Click to collapse
Right, so I reinstalled and flashed the latest version TWRP, when I opened into it, it took about 1 minute before it opened up, it ran a quick operation that I just glimpsed, it looked like it was wiping cache and user data, my phone was rebooted and I was right, my phone had been reset for the second time today (I'm almost a pro at reinstalling all my apps). I rebooted into the recovery and Look and Behold, it was working.
Thanks slot for your help and time.