Database Info

[Q] LG Optimus V stuck in android system recovery

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

FIT Droid flashing problem.

Hello everybody,
I just tried flashing FIT Droid to my galaxy fit.
The phone wont boot now. The screen says "FITDroid".
I'm really freaked out.
Pls help.
Before flashing I flashed CM7. In CM7,Wifi was not working.
So went for FITDroid. Before flashing CM7 i had gingerbread 2.3.3(official update from kies).

reboot in recovery mode and wipe data and cache.
If that doesn't work flash a new firmware using ODIN

reboot in recovery mode and wipe data and cache
if not work may be u can try this one
make sure the CWM is installed on the phone
CWM entered then select mount storge
formats / cache
format / data
format / system
format / sdext
then install fitdroid from sdcard
If that doesn't work flash a Stock Rom using Odin

how long does it stay in FitDroid Boot word? in my case it took about 50-10 mins before it reached the home screen...
try to wipe the data and the cache...

Thanks that helped...

[Q] How to wipe cache Partition

I try to wipe the cache partition on my Galaxy Tab 7.0 P3100 by booting up by pressing volume button up and power button and chose wipe cache partition and when it start erasing after 5 second it's sowing error and boot to system without wiping the cache.
I'm using JB 4.2.2 with no root.
Any way to wipe the cache?

godsmack_dmx said:
I try to wipe the cache partition on my Galaxy Tab 7.0 P3100 by booting up by pressing volume button up and power button and chose wipe cache partition and when it start erasing after 5 second it's sowing error and boot to system without wiping the cache.
I'm using JB 4.2.2 with no root.
Any way to wipe the cache?
Click to expand...
Click to collapse
The may be a write problem with the cache. Does the tab works fine in normal usage?
Alternatively, you could root it and flash CM Recovery, and then try wiping cache. If it works good, otherwise its a failing hardware.

用odin3重新刷一遍recovery，一切难题迎刃而解。和楼上解法差不多。先root再用固件管家刷第三方clockworkmod。
(英语不好没法输英文抱歉。(

I had the same issue after the 4.2.2 update. I was going to wipe it because the Tab was real laggy. I got the same error. Mine is a gt-p3113.
Sent from my GT-P3113 using XDA Premium 4 mobile app

I don't think it's a hardware problem. Try installing a custom recovery and then wiping cache. A good process should be like this:
1. Root device
2. Install Custom Recovery (CWM or PHILZZ)
3. try to wipe cache
Once you have rooted and have installed custom recovery, you may also like to try out new roms.
I would suggest not rooting if you have warranty left. If you have, best option is to send it in warranty and ask them to try wiping cache.

obmahmood said:
I don't think it's a hardware problem. Try installing a custom recovery and then wiping cache. A good process should be like this:
1. Root device
2. Install Custom Recovery (CWM or PHILZZ)
3. try to wipe cache
Once you have rooted and have installed custom recovery, you may also like to try out new roms.
I would suggest not rooting if you have warranty left. If you have, best option is to send it in warranty and ask them to try wiping cache.
Click to expand...
Click to collapse
My tab still in warranty but I'm willing to trying every solution cause warranty will simply will reset factory sittings and they will say it's fixed and come to get it. But in the same time I don't want to lose the warranty.

godsmack_dmx said:
My tab still in warranty but I'm willing to trying every solution cause warranty will simply will reset factory sittings and they will say it's fixed and come to get it. But in the same time I don't want to lose the warranty.[/COLOR][/SIZE]
Click to expand...
Click to collapse
Yeah, that's basically what I am thinking. I only have until February when my warranty runs out, then I may do the root and mod deal.
Sent from my GT-P3113 using Tapatalk

I did a downgrade to JB 4.1.2 but the tab stuck at samsung animation boot screen but I did manged to enter recovery mode and do a wipe cache partition and restart to know if it gone boot but it did stuck at samsung animation screen than I used odin to but it back to 4.2.2 and it worked fine with no restart for the first 24 hour but it did restart once while I'm using it in the half of the second day and two while I'm recharging it at the end of second day.
And here we are at the third day with no restart for about 15 hour since the last restart.
I hope it's the end for this problem.

Just getting the logo and a black screen after an update

Samsung Galaxy S2 i727 Skyrocket.
I recently updated to a 4.3 rom.
It booted up and I just got a message "Unfortuanately, Nfc Service has stopped. Blame Tyler."
I couldn't get the message to go away and the only thing I could do was a hard reboot.
Still same issue.
Rebooted into Recovery mode.
Factory Reset, wipe cache partition, format /system, wipe dalvich cache
Restored an older rom.
It booted up with no issues. But when I rebooted, I just get the Samsung logo and then the screen goes black.
I even tried Factory Reset, wipe cache partition, format /system, wipe dalvich cache and installed a new rom from scratch.
Same problem.
I have no idea what to try next or why this is happening.
Any help or comments are welcome.
Thanks

benraines said:
Samsung Galaxy S2 i727 Skyrocket.
I recently updated to a 4.3 rom.
It booted up and I just got a message "Unfortuanately, Nfc Service has stopped. Blame Tyler."
I couldn't get the message to go away and the only thing I could do was a hard reboot.
Still same issue.
Rebooted into Recovery mode.
Factory Reset, wipe cache partition, format /system, wipe dalvich cache
Restored an older rom.
It booted up with no issues. But when I rebooted, I just get the Samsung logo and then the screen goes black.
I even tried Factory Reset, wipe cache partition, format /system, wipe dalvich cache and installed a new rom from scratch.
Same problem.
I have no idea what to try next or why this is happening.
Any help or comments are welcome.
Thanks
Click to expand...
Click to collapse
What recovery are you using?
Sent from my SAMSUNG-SGH-I727 using xda app-developers app

Clock Work Method CWM...
I've done several ROM updates in the past with no problems...

benraines said:
Clock Work Method CWM...
I've done several ROM updates in the past with no problems...
Click to expand...
Click to collapse
What version of cwm? Most likely you need to update it. And what 4.3 rom?

Thanks.
I had a an older version of CWM and just upgraded to 6043..
Its now working with reboots...
I didn't realize CWM had that type of effect..
jd1639 said:
What version of cwm? Most likely you need to update it. And what 4.3 rom?
Click to expand...
Click to collapse

Problems after updating firmware for my samsung galaxy note 8 gt-n5110

I installed cm12.1 rom for my samsung galaxy note 8 gt-n5110 and after i turned it on this was what happened. It constantly showed text boxes like "unfortunately, google app has stopped" and after i closed it another one showed up and now i cant control it anymore! I cant even finish the setup! What can i do?
Im new to these firmware stuff btw.

sunglassesman said:
I installed cm12.1 rom for my samsung galaxy note 8 gt-n5110 and after i turned it on this was what happened. It constantly showed text boxes like "unfortunately, google app has stopped" and after i closed it another one showed up and now i cant control it anymore! I cant even finish the setup! What can i do?
Im new to these firmware stuff btw.
Click to expand...
Click to collapse
Try a smaller Gapps package than the one that you flashed with the ROM. The package you used is probably too large to fit in the system partition along with the ROM.
Or, you didn't factory reset, wipe cache and wipe dalvik cache when you flashed the ROM. Failing to do those wipes will cause bugs due to the new system conflicting with the saved system data/settings from the previous system. In other words, data left over from the old ROM is causing problems with the new ROM.
Sent from my SM-S767VL using Tapatalk

Droidriven said:
Try a smaller Gapps package than the one that you flashed with the ROM. The package you used is probably too large to fit in the system partition along with the ROM.
Or, you didn't factory reset, wipe cache and wipe dalvik cache when you flashed the ROM. Failing to do those wipes will cause bugs due to the new system conflicting with the saved system data/settings from the previous system. In other words, data left over from the old ROM is causing problems with the new ROM.
Sent from my SM-S767VL using Tapatalk
Click to expand...
Click to collapse
Hey thanks for replying but it seems like i cant even finish the setup. Therefore i cant load any files into my device. Any suggestions?

sunglassesman said:
Hey thanks for replying but it seems like i cant even finish the setup. Therefore i cant load any files into my device. Any suggestions?
Click to expand...
Click to collapse
Boot back into recovery, then factory reset, wipe cache and wipe dalvik cache, then reboot.
If that doesn't work, try booting back into recovery then flash the ROM then the Gapps then factory reset, wipe cache and wipe dalvik cache then reboot.
If that doesn't work, try booting back into recovery, then select the "Wipe" option, then choose the "advanced wipes" option, then choose the system partition, then swipe the slider at the bottom to run the wipe, then try flashing just the ROM but don't flash the Gapps, factory reset, wipe cache and wipe dalvik cache then reboot. After you get the device booted, you can delete the Gapps file then download a smaller package and put it in your phone's internal storage then boot back into recovery and select the "Install" option, at this point, you already have the ROM installed so no need to flash it again, but you do need to flash the new Gapps file, then factory reset, wipe cache and wipe dalvik cache.
Do you see how important it is to factory reset, wipe cache and wipe dalvik cache every time you flash? It is a vital step.
Sent from my SM-S767VL using Tapatalk

Hey thanks for all these but my device is using cwm right now so can you pls rewrite the instructions for me?
Also i cant finish the setup with all these popups so theres no way i can load files into it.
And yeah i guess i didnt wipe data or caches away after i finished flashing the files.
Thank you so much.