Database Info

MikRom Bootlooping on evo shift - HELP!!

This just started yesterday and i cant stop it. My phone reboots and says that memory is nearly full, then goes into a bootloop. I cant stop it long enough to back up texts, phone contacts and call log which is REALLY important; is there a way to back that up through recovery?
i'm really desperate here!
Edit: I can get the phone working through a format, but i need to be able to get contacts and sms backed up

Alternitavely, is there a way to run a clockword mod backup on an android emulator on my comp, so i can back up my important stuff?

what you should try doing is putting your sd card directly into your computer and delete stuff you don't need to get back so memory and then once you do that out it back into your phone

i cleared up the memory, internal and external. the stupid ROM is still broken

if its just the rom go to a different one and redownload mikrom later to make sure nothing happened in the initial download

If you haven't already, try removing some apps through adb, then reflash the ROM only wiping dalvik and cache. You shouldn't lose any of your text, call logs or contacts if you don't wipe data.
Sent from my PG06100 using Tapatalk

From The Hacker Manifesto:
I made a discovery today. I found a computer. Wait a second, this is cool. It does what I want it to. If it makes a mistake, it's because I screwed it up. Not because it doesn't like me... Or feels threatened by me.. Or thinks I'm a smart ass.. Or doesn't like teaching and shouldn't be here...
Click to expand...
Click to collapse
I love it sooooo the rom isnt stupid, the team of developers supporting it are amazing and you should setup adb and get a logcat, also you should nandroid before you flash so in case it goes wrong you can flash back, like insurance but you actually get something from this without paying..
if you did nandroid boot into bootloader and select recovery (hold volume down and power on use volume button to highlight recovery and power button to select)

I'm not sure if mikrom wipes or not but there's always that advanced restore option in cwm recovery flash rom, restore data and sd-ext if you have a ext partition with important data on it.

crump84 said:
If you haven't already, try removing some apps through adb, then reflash the ROM only wiping dalvik and cache. You shouldn't lose any of your text, call logs or contacts if you don't wipe data.
Sent from my PG06100 using Tapatalk
Click to expand...
Click to collapse
I managed to get some apps removed, its no longer giving me the memory-full error, but its still bootlooping a minute or so after loading. going to try the cache and davlik wipes, then a another install....
JKILO said:
From The Hacker Manifesto:
Click to expand...
Click to collapse
thanks I always do a nandroid backup before doing a format; doesnt help. I can load the clean rom just fine, but when i restore, it goes into bootloop again....
sparksco said:
I'm not sure if mikrom wipes or not but there's always that advanced restore option in cwm recovery flash rom, restore data and sd-ext if you have a ext partition with important data on it.
Click to expand...
Click to collapse
ok, ill try this.
Also, how do i set up an sd-ext to automatically backup texts and call history etc to it?

crump84 said:
If you haven't already, try removing some apps through adb, then reflash the ROM only wiping dalvik and cache. You shouldn't lose any of your text, call logs or contacts if you don't wipe data.
Sent from my PG06100 using Tapatalk
Click to expand...
Click to collapse
did not work - goes back to bootloop. how do i install ADB?

Jedman67 said:
did not work - goes back to bootloop. how do i install ADB?
Click to expand...
Click to collapse
http://developer.android.com/sdk/index.html
Beginner's Guide to Installing the SDK and Getting Started with ADB
If nothing else, like Jkilo said, provide a logcat and maybe someone could take a look.

Did you ever get this fixed?
The usual way of fixing this is formatting /system, wiping dalvik, wiping cache, and reflashing the rom.

VICODAN said:
Did you ever get this fixed?
The usual way of fixing this is formatting /system, wiping dalvik, wiping cache, and reflashing the rom.
Click to expand...
Click to collapse
no. what i did was a backup, complete factory reset, wipe, dalvik wipe, etc - several times each, including a full on sd-card format, which took me hours to reload everything back on - and then reflashed MikShift. It worked fine for about a day, but then it started to go into bootloops again, so i again did a backup, full reset and all wipes, and restored data only to the new flash of mikshift. Once again its bootlooping.
LOG: ive been off the forums for several months, how do i get this log?
IMAGE: When i go into bootloader and enter recovery, it shows me a message in green text
"PG06diag.zip
No image!
PG06diag.nbh
No image or wrong image!
PG06img.zip
No image!
PG06img.nbh
No image or wrong image!"
At this point, im ready to RUU back to factory unrooted, so i can take it back to sprint and get it replaced.
I should not need to reflash the ROM every single day.

Jedman67 said:
no. what i did was a backup, complete factory reset, wipe, dalvik wipe, etc - several times each, including a full on sd-card format, which took me hours to reload everything back on - and then reflashed MikShift. It worked fine for about a day, but then it started to go into bootloops again, so i again did a backup, full reset and all wipes, and restored data only to the new flash of mikshift. Once again its bootlooping.
LOG: ive been off the forums for several months, how do i get this log?
IMAGE: When i go into bootloader and enter recovery, it shows me a message in green text
"PG06diag.zip
No image!
PG06diag.nbh
No image or wrong image!
PG06img.zip
No image!
PG06img.nbh
No image or wrong image!"
At this point, im ready to RUU back to factory unrooted, so i can take it back to sprint and get it replaced.
I should not need to reflash the ROM every single day.
Click to expand...
Click to collapse
OK
0) Run a backup with titanium backup.
1) First of all go to clockwork -> mounts storage -> FORMAT /SYSTEM.
2) Wipe /cache, wipe dalvik, wipe/data, factory reset, repartition sd card.
3) Redownload the rom or try a proven ROM like UKE or CM7-255. If AOSP MAKE SURE TO FLASH GAPPS.
NO NEED TO RUU.
4) DO NOT RESTORE YOUR BACK UP. See how stable the phone runs.
5) If the phone is still unstable try a different battery.
6) Do not flash a custom kernel.

i formatted my backup SD card, and copied the essential data to it, and i have it running in the phone now. it seems to be running fine so far, i suspect the other SD may have gotten corrupt or physically damaged

Vic: every single time this has happened, i first went to clear the data and dalvik caches and ran a factory reset, all through the CWM recovery interface. Then when i reinstall mikshift, i restore the data using advanced restore, wait 24-48 hours, bootloops start all over again.
after two days of running on the new sd card, i start getting bootloops again. it must be a problem with the phone or the OS, but at this point i dont care anymore.
Is there a guide to RUU back to stock unroot? this phone is going back to sprint by weeks end, period.
thanks for the help folks.

Jedman67 said:
Vic: every single time this has happened, i first went to clear the data and dalvik caches and ran a factory reset, all through the CWM recovery interface. Then when i reinstall mikshift, i restore the data using advanced restore, wait 24-48 hours, bootloops start all over again.
after two days of running on the new sd card, i start getting bootloops again. it must be a problem with the phone or the OS, but at this point i dont care anymore.
Is there a guide to RUU back to stock unroot? this phone is going back to sprint by weeks end, period.
thanks for the help folks.
Click to expand...
Click to collapse
Here's the 2.2 RUU zip http://forum.xda-developers.com/showthread.php?t=971550 Just put it on the root of sd, boot in hboot and let it do its thing.
Or you can run the RUU exe, just download and run from your pc. It's pretty self explanatory http://forum.xda-developers.com/showthread.php?t=1335068

Jedman67 said:
Vic: every single time this has happened, i first went to clear the data and dalvik caches and ran a factory reset, all through the CWM recovery interface. Then when i reinstall mikshift, i restore the data using advanced restore, wait 24-48 hours, bootloops start all over again.
after two days of running on the new sd card, i start getting bootloops again. it must be a problem with the phone or the OS, but at this point i dont care anymore.
Is there a guide to RUU back to stock unroot? this phone is going back to sprint by weeks end, period.
thanks for the help folks.
Click to expand...
Click to collapse
The problem is you didn't format /system.

Redownload the Rom. Then follow THIS GUIDE when you flash.

VICODAN said:
The problem is you didn't format /system.
Click to expand...
Click to collapse
Exactly 10 char
---------- Post added at 12:34 AM ---------- Previous post was at 12:31 AM ----------
prboy1969 said:
Redownload the Rom. Then follow THIS GUIDE when you flash.
Click to expand...
Click to collapse
Yeah that guide is great for flashing sense roms since "most" sense roms don't format/wipe the system partition correctly. Aosp roms you just do a data facotry wipe and everything installs just fine

[Q] Flashing first ROM... is this normal?

I just tried flashing Liquid 2.7 on my S3 using TWRP. Cleared cache and Dalvik, then rebooted. Saw some text then the Samsung logo. Then two 'droids dancing. Then nothing. Nada. Black screen. Not responsive to the power button. Eek!
VZW S3, bootlocker unlocked, stock rooted 4.1.2 to begin with.

dmccrack said:
I just tried flashing Liquid 2.7 on my S3 using TWRP. Cleared cache and Dalvik, then rebooted. Saw some text then the Samsung logo. Then two 'droids dancing. Then nothing. Nada. Black screen. Not responsive to the power button. Eek!
VZW S3, bootlocker unlocked, stock rooted 4.1.2 to begin with.
Click to expand...
Click to collapse
Post the file name of the zip you flashed. When flashing roms, you should either wipe
1) Factory reset, cache, and dalvik then flash your rom
2) System and Factory Reset then flash your rom
Can you access download mode or recovery?

Liquid-JB-v2.7-OFFICIAL-d2vzw-schi535.zip
Yes, I can get into recovery. I have backups if I need to restore (assuming I can navigate the process correctly).
SlimSnoopOS said:
Post the file name of the zip you flashed. When flashing roms, you should either wipe
1) Factory reset, cache, and dalvik then flash your rom
2) System and Factory Reset then flash your rom
Can you access download mode or recovery?
Click to expand...
Click to collapse

The ROM was downloaded via Goo.im app
dmccrack said:
Liquid-JB-v2.7-OFFICIAL-d2vzw-schi535.zip
Yes, I can get into recovery. I have backups if I need to restore (assuming I can navigate the process correctly).
Click to expand...
Click to collapse

So I decided to restore my TWRP backup from last night. Entered "Restore" in TWRP, selected the backup, and swiped to restore... FAILED! "Failed to wipe /system"
[Reboot]
"You do not appear to be rooted. Root now?"
[Yes]
Continued reboot, now stuck on the "Samsung Galaxy SIII" splash screen. Letting it cogitate for a bit, but seems like it should have moved by now.
dmccrack said:
The ROM was downloaded via Goo.im app
Click to expand...
Click to collapse

Hmmm... tried another restore, did a TWRP system wipe first. The restoration says it completed... and... wait for it... booting normally! So far so good, at least I appear to be back to where I was before my pre-ROM-flash debacle.
The one response I received (thank you, SlimSnoopOS) was as follows:
1) Factory reset, cache, and dalvik then flash your rom
2) System and Factory Reset then flash your rom
Any other suggestions? Also, I'm not wed to the idea of the Liquid ROM over the others... anyone recommend I start with a different ROM, now that I'm back to square one?
dmccrack said:
The ROM was downloaded via Goo.im app
Click to expand...
Click to collapse
dmccrack said:
So I decided to restore my TWRP backup from last night. Entered "Restore" in TWRP, selected the backup, and swiped to restore... FAILED! "Failed to wipe /system"
[Reboot]
"You do not appear to be rooted. Root now?"
[Yes]
Continued reboot, now stuck on the "Samsung Galaxy SIII" splash screen. Letting it cogitate for a bit, but seems like it should have moved by now.
Click to expand...
Click to collapse

dmccrack said:
Hmmm... tried another restore, did a TWRP system wipe first. The restoration says it completed... and... wait for it... booting normally! So far so good, at least I appear to be back to where I was before my pre-ROM-flash debacle.
The one response I received (thank you, SlimSnoopOS) was as follows:
1) Factory reset, cache, and dalvik then flash your rom
2) System and Factory Reset then flash your rom
Any other suggestions? Also, I'm not wed to the idea of the Liquid ROM over the others... anyone recommend I start with a different ROM, now that I'm back to square one?
Click to expand...
Click to collapse
No problem. As for your issue, its fairly simple actually. What you need to do is a clean flash which is either of the two steps I listed earlier. You're trying to go from TW to AOSP but what you did was only wipe the cache then flashed the rom. Wiping cache and dalvik cache is regarded as a dirty flash, something you only do when flashing a newer version of the rom you're on. You never fully removed the TW rom before flashing Liquid which is why it did not boot. Basically, when you want to flash a new rom, by a different developer, you need to do 1 or 2 in order to have a successful flash.
For AOSP roms, you should also be flashing the recommended GApps (Google Apps) as well so that you have your Play Store and a few other Google Apps. The latest "generic" gapps zip is listed here at the top, its "20120301" which is March 1st. Liquid may have their own, that's for you to find out via their thread. Google apps are included in TW roms so this is not necessary.

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.

[Q] Tablet not working

So i rooted my tablet about a week ago and went to install adaway today when i went to reboot it it got stuck in a loop and so i tried a factory reset but now its in a loop of starting, saying upgrading apps, then saying process com.android.phone has stopped working then restarting again and keeps going what can i do to fix it?

CarsonM135 said:
So i rooted my tablet about a week ago and went to install adaway today when i went to reboot it it got stuck in a loop and so i tried a factory reset but now its in a loop of starting, saying upgrading apps, then saying process com.android.phone has stopped working then restarting again and keeps going what can i do to fix it?
Click to expand...
Click to collapse
You Should flash the stock firmware through Odin . Your data will not be erased .
Don't forget to press the thanks button :good::good::good:

Really! Flash to stock just for a bootloop. Unnecessary I think. I would just go to recovery and wipe system, cache, and dalvik and reflash the ROM. If that doesn't fix, then do the same but wipe data as well. You'll have to reinstall apps of course with that last one. Also, If you have an external sd card and a card reader, you could download a different ROM to the card and flash that one in recovery.

Lol
wolfclan68 said:
Really! Flash to stock just for a bootloop. Unnecessary I think. I would just go to recovery and wipe system, cache, and dalvik and reflash the ROM. If that doesn't fix, then do the same but wipe data as well. You'll have to reinstall apps of course with that last one. Also, If you have an external sd card and a card reader, you could download a different ROM to the card and flash that one in recovery.
Click to expand...
Click to collapse
Flashing to stock always fix bugs that wiping can't solve
Because flashing to stock will restores the original firmware :good:
Sent from Gallifrey using TARDIS

[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.