i was running CM7 then i went back to stock and it kept saying my memory was getting low so i went to settings>privacy>factory data reset. then now it wont come out of android system recovery with any rom or anything! PLEASE HELP!!
if i were you i would just load another custom rom:
1. in recovery, wipe data, cache, dalvik cache
2. connect your phone to your computer
3. download a custom rom on your computer and transfer it to your phone (by enabling usbms toggle)
4. flash the rom
ok i did that and it didnt work, said it installed successfully then i went to reboot system now and just went back in android system recovery.
Do it again and again and again until it works. Which recovery are you using and which rom? Btw, I guess you now know why they say not to use the inphone factory reset on the phone. May want to check in the ov forum instead of the general forums
jawz101 said:
Do it again and again and again until it works. Which recovery are you using and which rom? Btw, I guess you now know why they say not to use the inphone factory reset on the phone. May want to check in the ov forum instead of the general forums
Click to expand...
Click to collapse
RA-thunderc-1.1.0-GNM
and im trying to flash stockopv
and after its about it finish the words say
"installing update...
ohno...
..."
1. in recovery, wipe data, cache, dalvik cache
done
2. connect your phone to your computer
done
3. download a custom rom on your computer and transfer it to your phone (by enabling usbms toggle)
done
4. flash the rom
done
and after the xionia_cwma_12518.6 my phone keep boot into recovery mode wipe data, cache, dalvik cache reboot and go back to LG log freezes that or sometimes it going back to the same state :"recovery mode wipe data, cache, dalvik cache reboot" I can't make the phone connected stable with my pc if i can get this connection stable i would fix my problem so i can't even use ADB.EXE
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
I'm all ready to flash a custom rom on my device and came across this: How To Load Custom ROM on Your Android Device (After Using the Revolutionary Method), ( <---- type this link into google apparently im not allowed to post outside links so just type it in to google) however no where in the instructions is he wiping the cache partition or dalvik cache, I've heard from most people if you don't wipe the cache you could end up with a phone eating a bowl of boot loops, or having a paperweight, so is he wrong or is it not important, please explain?
Yes it is very important when flashing a rom or flashing just about anything else to wipe cache and delvik cache. Also if flashing a rom for the first time you must delete all data/factory reset. Wiping the caches will never hurt anything it will just make your phone take a while to boot the first time so don't be afraid to do it when flashing anything
Sent from my SGH-I777 using xda app-developers app
It is important as the last person explained. Though check your phone model and see if it has a hidden recovery or boot loader. Phones like my triumph let me get my phone back even it gets stuck in a boot loop or corrupts the recovery menu.
Oh okay thank you both, its just I have an htc aria, and I want to flash a rom, but I don't know how, I have it rooted, but i don't know how to flash a rom successfully, because I don't want to brick it.
I was following a guide to root and flash a ROM for my LG Optimus V. I got to the step where I wipe data/factory reset, cache, and dalvik-cache, but I decided to continue the guide later and powered off my phone and ended up in fastboot. I got out of fastboot by installing the zip files for BACKside ROM from the recovery menu, so now my phone works but a few things are off like I can't receive calls, getting server errors on google play, and getting an error that com.phone.android stopped working. I'm not sure what to do next to resolve those issues.
Edit: I realized that before installing BACKside, I didn't wipe caches or format anything since I had done them before my phone went into fastboot. Does this make a difference and means I need to re-install BACKside (by wiping caches, formatting, and then flashing)?
flowerTea said:
I was following a guide to root and flash a ROM for my LG Optimus V. I got to the step where I wipe data/factory reset, cache, and dalvik-cache, but I decided to continue the guide later and powered off my phone and ended up in fastboot. I got out of fastboot by installing the zip files for BACKside ROM from the recovery menu, so now my phone works but a few things are off like I can't receive calls, getting server errors on google play, and getting an error that com.phone.android stopped working. I'm not sure what to do next to resolve those issues.
Edit: I realized that before installing BACKside, I didn't wipe caches or format anything since I had done them before my phone went into fastboot. Does this make a difference and means I need to re-install BACKside (by wiping caches, formatting, and then flashing)?
Click to expand...
Click to collapse
1)maybe the rom and ur baseband don't match
2) maybe bcoz u didn't wipe so ders problem
3) or the rom itself has prob
so do a full wipe including formatting system.
i have rooted my phone with gingerbreak and wanted to install gingersnap rom. i followed this methood http://forum.xda-developers.com/showthread.php?t=1197991 and my phone is stuck in fastboot now.... i am able to press home+voldown+power button to go into clockwork recovery i think thats what its called and pretty much nothing else please help im new to this stuff
Go into the recovery, then use the volume keys to navigate around and either the search button or the menu button will select things depending on the version you're using. Once you're there, wipe cache and dalvik cache, then reboot it. The boot will take a long time, if after five minutes it's still trying to boot, then go back into recovery, wipe cache and dalvik cache, then install a rom like gingersnap. If after another five minutes that isn't working, boot into recovery again do a factory reset (this will wipe all of your apps, contacts, calendar entries etc), wipe system, wipe cache and wipe dalvik cache (do not wipe sd card or external storage) then install a rom like gingersnap and see if it boots up.
thanks for trying to help but none of that helped i dont really know how to install/flash a rom but i looked around a bit and found that i made a backup before i tryed to flash it so thanks
Watch the videos about installation of custom rom for Android (LG P500) !!
Me too learned from that videos!
Now using OXYGEN ROM!
Sent from my LG-P500 using xda premium