Hi there
I've unfortunately gotten a faulty devices and I'm suppose to get it switched with a new device. (another story about not being able to make calls, scrathing sound etc)
I've rooted my phone and it worked flawlessly, but today I wanted to un-root and would install the apps i've removed with root explorer. Therefore I downloaded a system/ dump and tried restoring the "app" directory in system/ with root explorer. This resulted in random force closes
Then I used "adb" su to copy all the app files from sdcard (where I copied the files from the dump) to the system/app directory. After a while it was done and I type reboot... [Bricked?]
Now the phone keeps rebooting. Getting the LG logo with sound and afterwards the LG logo with progress bar... then rebooting...
I need help
djkoch said:
Hi there
I've unfortunately gotten a faulty devices and I'm suppose to get it switched with a new device. (another story about not being able to make calls, scrathing sound etc)
I've rooted my phone and it worked flawlessly, but today I wanted to un-root and would install the apps i've removed with root explorer. Therefore I downloaded a system/ dump and tried restoring the "app" directory in system/ with root explorer. This resulted in random force closes
Then I used "adb" su to copy all the app files from sdcard (where I copied the files from the dump) to the system/app directory. After a while it was done and I type reboot...
Now the phone keeps rebooting. Getting the LG logo with sound and afterwards the LG logo with progress bar... then rebooting...
I need help
Click to expand...
Click to collapse
Try to hard reset, turn off your phone press volume - and power.
Thanks for the response... When I press power+volume down, the "unpacking box with android person" appears for a 20 seconds or so... the reboots and I'm back to rebooting constantly
When I try pressing volume down and home key/returnkey I can get in to S/W update mode, but I cant get the ADB to work?
Other suggestions?
That's why its a bad idea to delete stock apps in the first place when we don't have custom recovery yet.
gensplejs said:
That's why its a bad idea to delete stock apps in the first place when we don't have custom recovery yet.
Click to expand...
Click to collapse
It wasnt a problem when deleting them, and the phone was alright... it was when restoring through ADB it went wrong... I need a suggestion to get it fixed not an "I-told-you-so"
Yeah... sorry... i was kinda an ass.
But sadly I'm all out of ideas.
Maybe if we had a service manual (not user manual)
Sent from my LG-P990 using XDA Premium App
Can you connect to phone by adb?
You need to clear dalvik cache.
Hi Doc
No... unfortunately I cant get ADB to work....
I can get into S/W update mode, but ADB doesnt work. I can get the Factory reset to begin too, but it just gets into the reboot circle again.
If there was just a way to get into ADB mode I could push every single file again
Damn... I hope it isn't bricked for good
If HR doesn't work. Just return for warrenty.
Cause if it reboots that a corrupted boot.img
Try to see if you can get alist of apps installed on phone.
If superuser.apk is not in there, return it for warrenty.
In one of the reboots I think I had a glimse of a connection thru ADB acouple of times. I had approx. 10 seconds before rebooting again.
Did a list... and guess I saw a dir called "root" but didnt have time to get into the system/app directory...
If we can't find a solution I think I'll try to return the phone and hope for a new one without any question asked
Have you tried putting it in sw update mode and running the LG update tool?
http://www.lg.com/dk/support/mc-support/mobile-phone-support.jsp?countryCd=dk
Might do the trick
Yes I've tried the LG update tool. It says it has a new update, but the current firmware version doesn't show, and when I'm trying to do the update It aborts and says that the phone cannot be updated...
I just tried the Factory Reset and you can abort the reset when the "unpacking box" is showing by pressing the home key. Then you get into the 3e recovery menu... But there no way to select an option. Would have tried to wipe cache partition and data/factory reset. In the text it only says "formatting DATA:..., Formatting CACHE:..., Formatting MISC:..."
djkoch said:
Yes I've tried the LG update tool. It says it has a new update, but the current firmware version doesn't show, and when I'm trying to do the update It aborts and says that the phone cannot be updated...
I just tried the Factory Reset and you can abort the reset when the "unpacking box" is showing by pressing the home key. Then you get into the 3e recovery menu... But there no way to select an option. Would have tried to wipe cache partition and data/factory reset. In the text it only says "formatting DATA:..., Formatting CACHE:..., Formatting MISC:..."
Click to expand...
Click to collapse
There in no way to restore you phone now because we don't have any tools that's work with optimus 2x.
Bring it back to retailer and say that phone is just not booting and you want a replacement.
Edit: Well... discount the advice below for the time being... I've found myself in the same position and the commands below don't work.
My phone is also now useless...
I replied to your thread over at MoDoCo, and although the thread has gone off track it does have Paul's attention.
djkoch said:
Yes I've tried the LG update tool. It says it has a new update, but the current firmware version doesn't show, and when I'm trying to do the update It aborts and says that the phone cannot be updated...
I just tried the Factory Reset and you can abort the reset when the "unpacking box" is showing by pressing the home key. Then you get into the 3e recovery menu... But there no way to select an option. Would have tried to wipe cache partition and data/factory reset. In the text it only says "formatting DATA:..., Formatting CACHE:..., Formatting MISC:..."
Click to expand...
Click to collapse
Oh dear.
I tend to agree, whilst it will be recoverable it could be very time consuming.
A factory reset will wipe cache and dalvik cache, so that's not your problem.
Neither is boot.img your problem, that will be intact.
However, if you can't get a console (via adb or terminal) you're in a difficult position.
Try issuing the 'stop' command in your brief adb window to see if you can preserve the shell.
Code:
$ su
# stop
If you can then try and mount /system rw
If you can do that then you can possibly self recover... by carefully and selectively adding files to /system/app/, rebooting and trying, again and again.
Related
Hope someone can help me here...I already rooted my CDMA HTC Hero and was in process of installing the CM6 zip file from my sd card through ClockworkMod Recovery...After rebooting, It just shows the HTC screen and it just sits there. I took the battery out and reset back to the original...I am running 2.15 update and a build of 2.32.651.2...This is my first time rooting/modifying a phone...Thanks
douglaspott said:
Hope someone can help me here...I already rooted my CDMA HTC Hero and was in process of installing the CM6 zip file from my sd card through ClockworkMod Recovery...After rebooting, It just shows the HTC screen and it just sits there. I took the battery out and reset back to the original...I am running 2.15 update and a build of 2.32.651.2...This is my first time rooting/modifying a phone...Thanks
Click to expand...
Click to collapse
How long did it just sit there? Starting up a new ROM the first time sometimes takes a few minutes or more. It it's not rebooting itself, let it sit and load.
maybe
douglaspott said:
Hope someone can help me here...I already rooted my CDMA HTC Hero and was in process of installing the CM6 zip file from my sd card through ClockworkMod Recovery...After rebooting, It just shows the HTC screen and it just sits there. I took the battery out and reset back to the original...I am running 2.15 update and a build of 2.32.651.2...This is my first time rooting/modifying a phone...Thanks
Click to expand...
Click to collapse
more info is needed to help you. What steps did you take EXACTLY? get long winded. Like what root method, what recovery, what wipe process, what flash process, etc.
Okay...I used Z4Mod and went with a permanent root (seemed to be successful)...I grabbed the free version of ROM manager from the mkt place...I then flashed Clockwork Recovery in ROM Mgr...Finally, I selected "Install ROM from SD Card." A prompt showed up and I selected "Backup Existing ROM" and "Wipe Data and Cache." After checking OK, it rebooted and froze on the HTC screen for 15+ minutes two times. I have two zip files on my sd card: "update-cm-6.1.0-RC1-Heroc-signed.zip" and "gapps-mdpi-20101213-signed.zip" This is as far as I could get...thanks!
Well when you chose to backup existing rom that was good. When you chose to wipe data that was bad. Now your phone can't boot into anything because you wiped all of your data. But you were smart and made a backup. A general rule of thumb at least IMO
Is only wipe data if your flashing a new rom or having trouble with an exiting one. With that being said. Just boot into recovery by
Holding home and power until you see your recovery
Then look for an option that says install update zip from sd or update from sd. I don't use clockwork mod but I'm sure its something to that effect. Then choose install from sd or what ever the option was. Then you should see your two rom zips on your sd choose which one to install,let it finish and reboot. Being a fresh install it might take a minute. Or if you want to go back to your factory rom just look for an option that says restore and choose your backup you made when you used rom manger. Hope this helps good luck.
Yea its me Again With the
Modified Hero-
douglaspott said:
Okay...I used Z4Mod and went with a permanent root (seemed to be successful)...I grabbed the free version of ROM manager from the mkt place...I then flashed Clockwork Recovery in ROM Mgr...Finally, I selected "Install ROM from SD Card." A prompt showed up and I selected "Backup Existing ROM" and "Wipe Data and Cache." After checking OK, it rebooted and froze on the HTC screen for 15+ minutes two times. I have two zip files on my sd card: "update-cm-6.1.0-RC1-Heroc-signed.zip" and "gapps-mdpi-20101213-signed.zip" This is as far as I could get...thanks!
Click to expand...
Click to collapse
Instead of installing from ROM Manager, select the option to Reboot Into Recovery.
From there, select Wipe Data/Factory Reset, then select Wipe Cache Partition, then go into Advanced and select Wipe Dalvich Cache.
Once those steps are complete, go back to the main menu and select Install zip from SD Card, then select Choose zip from SD Card. Find the CM zip and select it.
Once it completes, select Install zip from SD card again, find the gapps zip and select it.
Go back to the main menu again, and select Reboot now.
That's an old build of 6.1 anyway, grab the "stable" release instead.
Thanks for all of your assistance. Where can I find a current, stable 6.1 download file? I will replace it on my sd card before going forward.
Also, how do I get to the boot/recovery screen? When I choose recovery, it freezes with the HTC screen...I have success getting the phone back to original when I select fastUSBboot, or something similar to that...
Trying powering off, then press and hold the Home button while you press and release (don't hold) the Power button.
If that doesn't work, try pressing the volume up button while pressing the Power button.
Turn off the phone and hold volume down and power. A white screen will appear from there press the home button. It will take a good 15 to 20 seconds to get into recovery. Are you waiting long enough???
Or power off phone and hold power and home untill it boots into your recovery remember it takes a few seconds 10 to 15 seconds
Yea its me Again With the
Modified Hero-
I selected the home key to get into recovery...after 10+ minutes of showing the HTC screen, I think there is something wrong. This goes back to the same issue when I originally attempted to install the CM ROM - it was supposed to reboot into recovery but instead restarted into a frozen HTC screen. What ele can I do? Can I just go back to original and try all over again? I had to take the battery out and reset the device...
After Fastbooting, I lost network access and can't get into the marketplace...When I go into ROM manager to restore the backup, it just sits and looks like it is working on it...How long should this take? Is 10 min too long?
So your able to boot into your rom right.??? So just go to rom manger and choose flash alternate recovery. Place a different recovery on your sd and flash it. Or just flash the clockwork recovery. Basically I think you need to get into recovery first.
Yea its me Again With the
Modified Hero-
I think you're right as far as getting into recovery being the key...Since my network is down, I had to try "Flash Alternative Recovery," but it showed "An error occurred while flashing your recovery" ...Is there another alternative to getting a new recovery installed?
My network connection just started working...I had to uncheck and recheck the connect to network...Clockwork recovery finally worked and I was able to install 6.0 and the Google apps...Thanks for all of your help! I do have one additional question - How do I set up my apps to store on the sd card instead of the internal memory? Thanks again
I'm having a similar issue as OP.
This is my first time trying to load CM7 on my Hero CDMA. I rooted my phone successfully and then installed Amon_Ra's Recovery (v1.6.2) and wiped the data/Dalvik-cache and then flashed CM7 and Google Apps. Everything seemed to install without problem.
However, when I reboot the device it doesn't get past the initial "HTC" screen.
I then attempted to use adb to look at the logs but when I boot into recovery mode and enable USB mode, the computer doesn't recognize an HTC device/serial:
c:\Android\android-sdk\platform-tools>adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
000000000000 recovery
and trying to access the logs or run shell commands through adb fails.
It's been stuck on the "HTC" logo for 10 minutes; I'm not sure if I just need to wait it out or if something has gone awry. Did I just brick my phone or can this be salvaged?
I managed to flash whatever I had backed up from nandroid, but it's incredibly unstable. Took several resets and almost an hour stuck on the "HTC" splash screen before booting. I have missed calls and can make them, which is a good sign, but I'm repeatedly hit with an error "The application Setup Wizard (process com.android.setupwizard) has stopped unexpectedly. Please try again.".
I can't post pastebin links since I'm new, but I have dumps of logcat and /proc/last_kmsg.
At this point I'd be happy to either get CM working OR revert back to a stable stock ROM.
How did you root ???
Also what's your baseband/ radio ??
Also what hboot are you currently on ??
Root-Hack_Mod*Always\
I needed to have a phone so I took it back to Sprint and they were able to do a factory reset. So while I'm glad it's not bricked, I'd prefer to have a better ROM on here.
I rooted using the following set of commands:
adb push asroot2 /data/local/
adb shell
chmod 0755 /data/local/asroot2
/data/local/asroot2 /system/bin/sh
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
cd /system/bin
cat sh > su
chmod 4755 su
Firmware version 1.5
Baseband version: 1.04.01.09.21
Kernel version: 2.6.27-533ce29d [email protected]
Build number: 1.56.651.2 CL85027 release-keys
Software version: 1.56.651.2
Hardware version: 0002
I'm not sure how to find out the hboot version.
When you first rooted or before did you make a backup/nandroid ?? Also after you rooted did you flash a recovery ??
Root-Hack_Mod*Always\
Well I screwed the pooch on this one...
While browsing on the streak the battery died and after that I had force close issues for just about every user and system app on the phone. Normally that can be something corrupted on the sdcard from the shutdown and you can typically find the folder and remove it. The alternative would be running fix permissions in terminal, adb, or rom manager. That's not the case here (that I've found). It happens or has happened to me on my sgs before but not my nexus or g1 before that so I'm not sure what specifically triggers it. While trying to find the corrupted file I I tried to install Rom Manager but I can't get into the market despite clearing the cache. I can't install any apps at all actually - it will reboot the phone.
It seems to be a permissions problem. When the issue started like 8 hours ago the sdcard, system, and data were all read only. I fixed the sdcard by mounting to my computer and fixing the permissions in windows by changing the folder properties. I eventually fixed the system permissions (I believe) when I fastboot flashed the boot and system.img for the "performance fixes"; however, I can't for the LIFE of me fix the permissions of the /data and whatever else still is read-only. Flashing the system.img did change that to read-write though which was a major step in the right direction. Seriously, I've tried wiping in recovery (it says it works but doesn't wipe when rebooting), fastboot erase /data to name another attempt with no results after rebooting. It just doesn't erase anything like recovery, fastboot, and everything else doesn't have permission to erase, delete, or modify the data partition.
I can't install apps normally or adb.
I can't wipe data - I get errors in adb about it being read-only.
I can't wipe data in Recovery. It wipes, then reboots, with none of the data wiped.
I can't wipe in Fastboot using Fastboot erase /data - same thing as above.
I can't install root explorer only I'm pretty sure that won't work if fastboot doesn't.
I can't fix permissions using any method that I know of...
Is there anything I'm missing on ways to erase/format /data and everything else that might have this permission problem?
Logcat: http://db.tt/0bzhUQi
*edit:
So I also have root when booting amidst all the force closing (tested with titanium backup) I have but ADB doesn't. I can only get su with adb when I run OneClickRoot again and I get the "failed to copy rateagainstthecage to /data/local/tmp/rageagainsthecage. Read-only filesystem. Then says "unbalbe to chmod /data/local/tmp/tageagainsthecage read-only file system which is what I got also when I tried fixing the permissions for that folder. With that - I only have temporary root only in adb - fully rooted otherwise...
Same problem here cant save or delete. Very time I start up I get the welcome screen and I have to input all my info then all of my apps start to crash. I tried flashing the boot and system.img with fastboot but that did nothing so I decided to see what will happens if I erased all of my partitions (system, boot, userdata, recovery and cache) Fastboot reports back that my partitions all got erased but when I boot up (it shouldn't boot up because all partitions are deleted)it start up to the welcome screen and I back to the same problem that I cant permanently wright or delete to the internal drive
Ya - I'm at a total loss. Keep me posted on what you try and I'll do the same. I won't be able to mess with it until later today and not really sure of what I'll try next. As of now it's essentially worthless to use...
Sorry what will happen if you factory reset now and erase tablet storage? (option 4 with volume up +power button)?
At least you have almost nothing more to lose here right.
Otherwise the only solution I think is to wait for CWM recovery image to come out then...
Sorry that this happened to your DS7. I struggled with quite some issue with mine too, it is pretty annoying.
I tried that factory reset over 10 time. All of the same files that I had on the streak7 before this problem stay intact. Factor rest from the recover mode dont seem write to the streak7
killahbeatz said:
I tried that factory reset over 10 time. All of the same files that I had on the streak7 before this problem stay intact. Factor rest from the recover mode dont seem write to the streak7
Click to expand...
Click to collapse
+1. I even fastboot erased /data or attempted to. Seems like the command works but when you reboot everything is still there.
Found the other post which I didn't find http://goo.gl/xlO6y earlier.
I'm wondering if we tried setting permissions with adb with the mounts they're finding in this thread http://goo.gl/wOynl
I'll post back if I can find the chmod commands. That info might help though.
I tried fastboot -w to erase the data from the device. It boots with no force close issues now but I still can't wipe anything (still read only). I think I can install apps now though so hopefully I can install Rom Manager and Root Explorer to fix permissions and see what I can find out. Doubt it will work but hey, if I started out with read only sdcard, data, and system, and now have read-only data, that's progress I suppose.
I only have it for another few days before returning. I received the replacement yesterday and have to mail it back soon.
Quick SUMMARY (see details below if you've got some minutes to read!)
-> I need HELP!!!
-> Phone is rooted stock GB with jb hboot unlocked bootloader and TWRP v2.2.0, also superCID.
-> Problem is phone apps keep force closing and won't retain any change I make after reboot
-> Last installed program was ROM Toolbox
-> Steps already taken include: Reboots, Fix permission, Wipe (ALL), ROM Update using Windows, RUU using SD card.
Details
I have a Vivid with Stock Gingerbread (Rooted, Bootloader Unlocked, Juopunutbear hboot, SuperCID S-OFF, TWRP Recovery v2.2.0)
I recently removed the SD card on my vivid to use on another phone (SGS III) and when I returned the SD card and started my vivid, I tried using the file manager (ES Explorer) and it force closed, following series of other apps force closing.
I restarted the phone and the force closing didn't stop. I tried uninstalling the most recently installed app (ROM Toolbox) thinking it might be the culprit and nothing changed. I rebooted the phone and noticed every time I rebooted, the phone goes back to the state (installed apps, settings and every other thing) it was before I removed the SD card.
I installed Titanium Backup to make a Backup and flash the phone, but it kept force closing and after several reboots and attempts, it installed but couldn't acquire root.
I restarted to recovery to fix permissions and cleared cache and dalvik cache then rebooted the phone. No luck!!!
I eventually decided to wipe the ROM and do a fresh RUU install. I wiped system and data using recovery but when I restarted the phone, it booted to the (pre-SD card removal) state and was still force closing.
I tried installing ICS using the RUU from att and I got an "Error 155" on the way. I also tried installing the RUU using PH39IMG method with the SD card, it goes through the normal install process and when the phone booted, it's still the same state it was that it takes me to changing nothing.
I've tried all I know and it seems the phone is "write-locked" as it won't retain any change after reboot, suggestions to what I can do to fix this weird problem please.
I am not so sure...
Did the sgs3 reformat your sdcard to a different file system?
Sent from my HTC Holiday using Tapatalk 2
rignfool said:
I am not so sure...
Did the sgs3 reformat your sdcard to a different file system?
Sent from my HTC Holiday using Tapatalk 2
Click to expand...
Click to collapse
No it didn't. I only used the sdcard to copy some files to the sgs3 and I still could access the sdcard on my vivid through Root Browser in ROM Toolbox.
hardware maybe
Interesting... One thing you could do is enable USB debugging, and save a logcat showing your phone hitting some of these FCs so we can see what is causing them.
Once USB debugging is enabled, simply boot your phone, plug into your computer via USB, open a command prompt to where you have ADB tools installed, and type "adb logcat > log.txt
That will stream the log from your phone into a text file. After you get one or two FCs, on the command window hit CTRL + C to close the console, and save the log. Then post it as an attachment here.
ess.boyer said:
Interesting... One thing you could do is enable USB debugging, and save a logcat showing your phone hitting some of these FCs so we can see what is causing them.
Once USB debugging is enabled, simply boot your phone, plug into your computer via USB, open a command prompt to where you have ADB tools installed, and type "adb logcat > log.txt
That will stream the log from your phone into a text file. After you get one or two FCs, on the command window hit CTRL + C to close the console, and save the log. Then post it as an attachment here.
Click to expand...
Click to collapse
Thanks ess.boyer. I've been busy over the past few weeks so just saw your reply now.
The phone is in a pretty bad shape right now, I managed to drop it and the screen is shattered so I can't touch the screen to use it.
But I put it on and did the log. Please find attached.
Thanks for wanting to help!!!
So I think the install is probably botched. I'd recommend wiping EVERYTHING and reinstalling from RUU (maybe try a different RUU even).
However, first, please try wiping your cache and dalvik cache. Most of the errors are from not being able to find symbols in dalvik.
Also, are you restoring apps using Titanium backup or some other such program? If so, that could also be an issue. If you have, and wiping cache & dalvik cache don't work, you may want to try wiping /data entirely, and NOT restoring apps before you can confirm that the FC issues you were seeing are still there.
Give the cache & delvik clean a try, and if that doesn't work, please attach a similar log so I can confirm you're seeing the same issues, then we can go from there.
ess.boyer said:
So I think the install is probably botched. I'd recommend wiping EVERYTHING and reinstalling from RUU (maybe try a different RUU even).
However, first, please try wiping your cache and dalvik cache. Most of the errors are from not being able to find symbols in dalvik.
Also, are you restoring apps using Titanium backup or some other such program? If so, that could also be an issue. If you have, and wiping cache & dalvik cache don't work, you may want to try wiping /data entirely, and NOT restoring apps before you can confirm that the FC issues you were seeing are still there.
Give the cache & delvik clean a try, and if that doesn't work, please attach a similar log so I can confirm you're seeing the same issues, then we can go from there.
Click to expand...
Click to collapse
Please see my steps already taken.
I've wiped cache and dalvik, I've installed RUU thru windows, I've installed RUU from SD card. But whenever the Phone boots up, the phone state does not change at all (all apps are as they are, all settings are as they are).
I even tried to lock bootloader, remove superCID. Just a reboot and it all goes back to what it was.
Thanks
What happens if you reboot the phone without the SD card in it?
ess.boyer said:
What happens if you reboot the phone without the SD card in it?
Click to expand...
Click to collapse
The phone boots up to homescreen normally and the apps installed on SD don't work, with reduced FC
As per the title. I have an S4 Active, humming along happily with "activeroot" applied when it first became available. I realized this morning that I never deleted the activeroot app itself, but when long-pressing the icon to get to the uninstall menu, my finger slipped. I really like geohot and his work, a whole lot, but the fact that there isn't at least a confirmation screen before overwriting important system files really grates on me. The instant the tap happened, the screen went black, and became immediately stuck on the AT&T logo at reboot.
If I power the phone up normally, I only see the AT&T logo for as long as I care to stare at it before powering it down. I can reboot into the stock recovery, but because the phone doesn't ask me for the disk-encryption password as in a normal boot, I see the error "Can't mount /data (Invalid argument)". The only non-destructive thing I could do at that menu was to wipe the cache, which obviously did nothing for my bootloader or encrypted disk. I feel pretty sure I haven't lost any data on that encrypted disk yet, and I know I could do a full factory wipe, but I'm hoping I have a better option:
1) Could it possibly be as simple as trying to send "towelroot", the newest root, to the phone via adb and execute it?
2) Without the ability to write to the disk, can I get a log file for further troubleshooting / ideas?
3) Is there a way to decrypt the disk over usb to at least pull over any non-backed-up files before performing a factory wipe?
4) Can I install a different recovery which might give me more or better options?
Thanks for any help you can provide! = )
Stock Android 6.0 with stock recovery, no root, locked bootloader. Ran the device out of internal storage by writing too many files to the application's data directory. The device crashed and now it goes black after the boot animation. Able to get to the bootloader and recover menus. Lots of data stuck on the device. Any advice on pulling the files or getting Android to start again?
Try wiping the cache in the recovery menu.
Red_81 said:
Try wiping the cache in the recovery menu.
Click to expand...
Click to collapse
Tried this already. Thanks for the suggestion!
Sorry, I didn't see that I your original post so I had to start at the beginning with the most simple suggestion.
Go to recovery and try to use the adb shell to copy off the data you want to keep. Maybe also try a backup from adb (I forget the command).
If you know of a program that is taking up alot of data in the data partition that you don't care about losing then you could try using the shell to delete that data file.
Otherwise, you may just have to factory reset and start over.