Database Info

[Q] Help with ATRIX!!!

Ok, so i have a new Atrix that came stock with 2.3.4/4.5.91 from AT&T. I Rooted it, unlocked the bootloader, and installed this Recovery: recovery-en-goapk-0630-1029. Then I tried to flash CM& Beta, and all hell broke loose. on reboot, it got stuck on the Dual Core screen, and I can do anything else, because now i get battery to low to flash error. What mode does the phone need to be in so it will charge, and what do i need to do to fix this?

I have a Droid two global by Motorola and bricked it at one point in time. I had the same issue. I am not sure if this is the case with the atrix, but it very possibly could be. In his state often Motorola phones will not charge themeselves. There are a few options. The easiest is if you have a buddy that has the same phone as you. You can borrow the battery from his phone. You could also simply buy another battery. The honestly best, but hardest method is to buy or make your own Motorola factory cable. You can look that up online. After you have a charged battery simply find instructions to recover your phone via fastboot, or sbf. Hope you get it working
P.s. if this helped you, or you simply appreciate me taking the time out of my fourteen year old life then please press the thanks button

Well, I was able to rescue my phone lol. After the panic set in and I was calm again, I searched the house and found my microSD to SD adapter, and downloaded the "alien" ROM, entered recovery and was able to install it. After that phone booted up properly and went it charge mode....thank God lol. So now I'm left with another series of questions...why wouldn't the recovery install the backup I made, and wouldn't the CM7 beta not install, but the alien rom installed just fine? I might to go to the forum specific area for androids foe this one...

D150shorty said:
Well, I was able to rescue my phone lol. After the panic set in and I was calm again, I searched the house and found my microSD to SD adapter, and downloaded the "alien" ROM, entered recovery and was able to install it. After that phone booted up properly and went it charge mode....thank God lol. So now I'm left with another series of questions...why wouldn't the recovery install the backup I made, and wouldn't the CM7 beta not install, but the alien rom installed just fine? I might to go to the forum specific area for androids foe this one...
Click to expand...
Click to collapse
Gonna answer my own question here...I had the wrong recovery installed. For others wanting to install CM7, use rom manager, and install the most current version of clockworkmod recovery and make sure to update it. This was my golden ticket to CM7 love

[Q] Samsum Galaxy Fit No Boot

Greetings.
It doesn´t boot.
First details:
Galaxy Fit rooted and 2.3.4 Gingerbread (worked fine)
I downloaded rom-manager and wanted to change to custom roms.
So far.
As I tried to install clockwork I found this in your forum:
http://forum.xda-developers.com/showthread.php?t=1339640
and did everything exactly written there
then restartet, started rom-manager and chose the first option (Clockworkthingy).
As there was a choice of the device, I didn´t find my device and chose the last in list (which did´t work and then I picked the first in list and accepted.
downloaded syanogen 7.0 and after download and backup-chose it told me it would reset and start in recovery ... that was the last I´ve seen from my galaxy ...
Is it broken now.
Please help!
note: tried to start recovery with vol+, home and power as well as usual way to start it. without success

Come on. Some of you Guys are able for sure to tell me, if it is hopeless or there IS something I can do to get it working again.
I know nearly nothing about Smartphones and stuff so
Please!

Rodsengard said:
Come on. Some of you Guys are able for sure to tell me, if it is hopeless or there IS something I can do to get it working again.
Please!
Click to expand...
Click to collapse
Sorry to say that your phone is bricked.
First, rom manager doesn't support your device.
Second, you are an idiot that you selected unknown device from list to make it work.
Third, the thread doesn't have any tutorial about rom manager it is CWM that is meant to be flashed using odin.
Fourth, I probably this is hard brick and nothing can be done.
IN MY VIEW GO TO THE SAMSUNG SERVICE CENTER AND TELL THEM THAT YOU LEFT YOUR FOR CHARGING OVERNIGHT AND ITS NOT BOOTING.
THEY WILL SURELY HELP FOR FREE AS THEY DON'T KNOW WHAT YOU DID AND THIS IS AN APPROPRIATE REASON.

Thank you for your honesty.

Your phone still can be fix up. Your phone not brick yet.. Your phone might get bricked if it running out of battery during flashing, like a half way flashing, then you are in the worse case scenario.
Recovery mode unavailable? Forget about recovery since it has been.broken. What important now is to get access to download mode by pressing vol down + power + home key. If you can access download mode, then your phone can be fixed in 5min.
Read this, before you go any further, if you sure that you already successfully flashed any rom before it went brick. Just do this simple step, for cm7, u need siyah kernel, go download (siyah 2.1.1 .tar)... Not .zip.
Remove your battery then put it back, get into download mode then flash siyah 2.1.1 with Odin 1.85.if your phone already flashed cyanogenmod7, then your phone should boot up and work properly.
If it doesnt work, click the link on my signature, follow all steps provided tp get back your to work as stock. Then start flashing again.
Ps : dont use backup, dont use romanager.
Sent from my GT-I9100 using xda premium

My guide is for SGS2 International. Not ATNT, please find stock rom for your phone version. But the flashing method are just the same..
Sent from my GT-I9100 using xda premium

Thank you for your efforts neobirdrio, but as I wrote above, nothing works.
No combination with vol+ or - and the 2 other HW-Keys.
But if we are still in Topic, what exactly do I have to do with an intact Galaxy fit to flash it to a custom ROM.
What Custom ROMS would run with it?
Where Do I get the Newest Version?
And is it worth changing it?
I wanted something special, something faster than Gingerbread and (of course the original Froyo on it), including something needs less Space.
Could you advice me?
(I ordered a new one swince it happened)

Try read this post,
http://forum.xda-developers.com/showthread.php?t=1120880
Latest stock firmware for galaxy fix is 2.3..which is gingerbread.
Sent from my GT-I9100 using xda premium

Still trying this out.
Did it in this way press three Keys, push batery in and so on ... One time on my netbook it came to life by meaning system told me, that it installs driver (seemed to be recognized right) and ODIN told, there is a connection. I started ODIN (which was prepared to do Gingerbread onto it) But it did nothing. I am not sure if I startet Odin with Adminrights, soooo ... Do now backup of the partition, put a much earlier backup on my PC and try it again (I am running out of PCs, so I simulate, that this is a new Computer )
I keep you informed.
Thanks again so far.

Tried it again, but it didn´come back to life
So Thanks to all ppl helped me.

Remove Supercharged Atrix V5

I am way N00b at this but how do I remove this from my Atrix 2? It is eating up my battery and I can't open some of my apps, they force close. Is it possible to flash back to the point prior to this?
It was backed up before I started but know I cant find the back up. I just want to go back to the point when it was rooted. I used "MotoFail" to root and everything was going great and decided to try this, my bad, any ideas besides buying anoter phone?;-(

ozziedog said:
I am way N00b at this but how do I remove this from my Atrix 2? It is eating up my battery and I can't open some of my apps, they force close. Is it possible to flash back to the point prior to this?
It was backed up before I started but know I cant find the back up. I just want to go back to the point when it was rooted. I used "MotoFail" to root and everything was going great and decided to try this, my bad, any ideas besides buying anoter phone?;-(
Click to expand...
Click to collapse
you have one option, flash the fxz and reroot.
start over.
there is a great nOOb thread telling how to do it.
http://forum.xda-developers.com/showthread.php?t=1396650

ozziedog said:
I am way N00b at this but how do I remove this from my Atrix 2? It is eating up my battery and I can't open some of my apps, they force close. Is it possible to flash back to the point prior to this?
It was backed up before I started but know I cant find the back up. I just want to go back to the point when it was rooted. I used "MotoFail" to root and everything was going great and decided to try this, my bad, any ideas besides buying anoter phone?;-(
Click to expand...
Click to collapse
How did you back up?
If you used CWM (from the A2 Bootstrapper) just reboot into CWM, go to backup and restore, select restore, and select the backup that you made.
If you didn't use CWM or you can't find the backup then you will have to flash the fxz as said above. It will completely remove all of your apps and return you to stock 2.3.5. Make sure that you follow the directions about replacing files.

Thank you matt99017d I will check the link and cogeary I did the back up CWM I'll go that route first if that doesnt work, I'll go back to the beginning. Thank you again for the help

I could not find the backup in CWM so I flashed fxz following the instruction on the link you provided and the info. I'm back to 2.3.6 and it is rooted. Thats as far as I'm going for now, thanks for the help you all provided.

I see at /system/etc/init.d 2 files with sd-card optimization. 03sdtweak and 99override. Is there right or needed to delete one of them?

I highly suggest getting Titanium, for the cases where you don't have a back up, because I lost all my free apps and I don't even remember what all I had. I'm getting things back as I need them.

Douchewithaphone said:
I highly suggest getting Titanium, for the cases where you don't have a back up, because I lost all my free apps and I don't even remember what all I had. I'm getting things back as I need them.
Click to expand...
Click to collapse
https://market.android.com/mylibrary
^ shows everything you've installed from the Android Market. You should have records somewhere if you got things from the Amazon Appstore.
I haven't tried it myself but if you've made a backup in CWM you have the option to only restore apps/data.

Well I decided to give SuperCharged V5 with update 1, and when I disconnected form the charger this morning it was stuck in the boot animation. It has been stuck in that position for the last 30 minutes.
I connected it to PC and it doesnt show as being connected. I've done a search and can't find anything on how to fix it.
I did a battery pull, took SD card out to see if I could maybe transfer something from it to desktop, but everything that was on it is gone.
Don't know what happened.
Can someone point me in the right direction?? In the mean time I'll keep looking.

Ozzie Im in a similar situation. I"m in a bootloop as well (Supercharged Logo just keeps rolling on the screen). I can't get into the Android OS, and I also can't even get into Fastboot to flash back to stock. At this time it appears its bricked. I have been trying to fix this the past 12 hours.
Are you in the same situation??!

ej_424 said:
Ozzie Im in a similar situation. I"m in a bootloop as well (Supercharged Logo just keeps rolling on the screen). I can't get into the Android OS, and I also can't even get into Fastboot to flash back to stock. At this time it appears its bricked. I have been trying to fix this the past 12 hours.
Are you in the same situation??!
Click to expand...
Click to collapse
I am sorry to say, but if you can't get into fastboot it's probably bricked

so i installed V5 and update 2 and i am getting the force closes and my phone won't show up when i plug the usb into my computer
and i can't delete or edit files in my files and i can't open any websites or connect to airdroid on wifi, or use data so i can't get any files onto my phone
help...

flashing the stock fxz worked

Man...and I was gonna do this...flash the supercharged ROM. Nevermind.

after i flashed the 2.3.5 fxz like the bootstrapping thread instructed, i installed the ota update and rooted my phone again and then i tried the custom rom again just for fun
but this time i did v5 and then update 1. then instead of doing update 2, i flashed the image of the rom that's linked right under update 2 in the supercharged thread
it works flawlessly for me now
so i would just recommend that

[GUIDE] T-Mobile US One S - How to ROOT and flash ROMs

So I know there's been some controversy and scares going around about the US version, since it JUST came out. I'm here to calm you guys down. I have now rooted mine, flashed an interim CWM touch version (not permanent) and have flashed a ROM......ALL successfully.
Here's what I did:
UNLOCKING:
Unlock your bootloader by registering at HTCdev.com and following the unlock instructions. Under device, choose "All other devices", as the One S is not yet listed. It'll walk you through getting your unlock token and flashing it.
ROOTING
Follow Paul O Brien's instructions on rooting your phone. I flashed the r3 superboot file he had. The first time it didnt take and just booted the phone back up. Second time it took, and seems to have stuck, at least for apps. Please note that my phone says *TAMPERED* along with the *UNLOCKED* notification. I have no idea what that means exactly, but everything works great for me.
This means if you dont want to leave Sense but want to get the tons of useless and annoying T-Mobile and other bloatware apps out, you can. T-Mo are dicks and make almost 100% of the apps on it by default SYSTEM apps, therefore unremovable. So you'll need root and Titanium Backup to freeze or delete them. I'd recommend freezing the non-TMo one's just in case.
FLASHING ROMS
1. Flash Paul O Brien's intermin CWM touch version. You MUST use this interim CWM version for the moment, as the others do not work properly. Some things like USB mount dont work in this interim version, but the important functions like wipe and flash, backup and restore, and restart do work. The CWM recovery seems permanent, based on my initial trials, so no worries about reflashing it each restart.
2. Flash your ROM of choice from Clockworkmod Recovery. I'm using Black Dragon right now, but there are others out there as well. I'm personally looking forward to CM9, but its a little ways away, usability-wise.
So there you have it, all you US guys. Don't be afraid to mod your phone. Remember all the warranty void disclaimers as always. I'm not responsible for you bricking your phone. This is just my experience in just under 24hrs of use. Things are looking good for the One S.

bump... i see US users still asking.
Mods, can we perhaps sticky this post of mine? I don't want to take credit for the actual methods of rooting, since Paul O Brien and others deserve that credit, but I think it'd be helpful for US users, since many don't know whether or not the international method works.
That, or perhaps editing the Intl guides to make it clear that the US version accepts the same methods and ROMs.

Worked great for me
Sent from my HTC VLE_U using xda premium

So if we root and flash a custom ROM is there any way to get the phone back to factory state, and get rid of the *TAMPERED* and *UNLOCKED* notification??

Did anyone else get a bit of a sad chuckle out of the first step in the instructions being "remove and reinsert battery"?

cyberchuck9000 said:
Did anyone else get a bit of a sad chuckle out of the first step in the instructions being "remove and reinsert battery"?
Click to expand...
Click to collapse
Great, now my blisters on my fingers will heal.
But still.... I cannot imagine not needing a batt pull.

nickmv said:
Mods, can we perhaps sticky this post of mine? I don't want to take credit for the actual methods of rooting, since Paul O Brien and others deserve that credit, but I think it'd be helpful for US users, since many don't know whether or not the international method works.
That, or perhaps editing the Intl guides to make it clear that the US version accepts the same methods and ROMs.
Click to expand...
Click to collapse
+1

androidcues said:
Great, now my blisters on my fingers will heal.
But still.... I cannot imagine not needing a batt pull.
Click to expand...
Click to collapse
If you need to perform a hard reset on the One S, you hold down the power button for about 7-10 secs.

First of all, thanks for this thread...I used the HTC One S All in one tool kit to unlock my phone, unfortunately I miss understood one of the directions(#5) and stopped using the tool kit and followed another thread, much to my surprise, my bootloader is unlocked, hooray My question is, how do I get back to the original state if that is possible? The reason I ask, is I would like to go back and do it correctly...I used better terminal emulator to see if I had root, but all I got was the $ sign instead of the # sign So I would like to start over...
Thanks in advance for the help

I'm honestly not sure what the procedure is for relocking an HTC bootloader. Perhaps do some Google research on some of the latest models, and I bet you'll find something.
That being said, once you unlock the bootloader a single time, the best you can do is go to **RELOCKED** state. You'll never get back **LOCKED**. Once it's gone it's gone. I'm curious about the **TAMPERED** message though. That's an ugly word.

not sure what exactly went wrong.
somehow flashed CWM and now thats the only thing my phone will boot to, even after re-flashing the stock recovery.
can't get the phone to turn on, only CWM every single time.

suhailtheboss said:
not sure what exactly went wrong.
somehow flashed CWM and now thats the only thing my phone will boot to, even after re-flashing the stock recovery.
can't get the phone to turn on, only CWM every single time.
Click to expand...
Click to collapse
Uh oh that doesn't sound good
Sent from my HTC VLE_U using xda premium

yeah, tried reflashing both CWM & stock recovery. phone still boots to CWM everytime.
Luckily i can still access the phone via ADB, (while in recovery) so i'm sure i'll be able to sort it out. just need to take a fresh crack at it tomorrow. gonna switch back to my galaxy nexus tonight. (oh wait, i dont have any other phones that use microsim)
haha.

Hmm, interesting. Did you flash the interim recovery that Paul O Brien posted, and not another version? Just wanna make sure. I've heard of this happening in my past experience with the Nexus S, but I can't recall what the deal was. Regardless, I don't think you're in trouble. As with your GNex, it's very hard to completely brick the device unless you flash perhaps a bad hboot file, however I'm not really familiar with HTC devices.
This is my first HTC so I'm still trying to learn how the hboot and other processes work together. Sry to hear you had bad luck.
UPDATE: You should try the root install script. It tells the phone to boot after install. That might get you booted atleast.
Some thoughts:
1. Flash the stock recovery back and reflash CWM
2. Clear cache and dalvik within CWM, and make sure to use the 'Reboot System' option if you aren't already.
From what I can tell, your "boot-to-recovery" flag is set on the phone, and isn't getting cleared.

nickmv said:
So I know there's been some controversy and scares going around about the US version, since it JUST came out. I'm here to calm you guys down. I have now rooted mine, flashed an interim CWM touch version (not permanent) and have flashed a ROM......ALL successfully.
Here's what I did:
UNLOCKING:
Unlock your bootloader by registering at HTCdev.com and following the unlock instructions. Under device, choose "All other devices", as the One S is not yet listed. It'll walk you through getting your unlock token and flashing it.
ROOTING
Follow Paul O Brien's instructions on rooting your phone. I flashed the r3 superboot file he had. The first time it didnt take and just booted the phone back up. Second time it took, and seems to have stuck, at least for apps. Please note that my phone says *TAMPERED* along with the *UNLOCKED* notification. I have no idea what that means exactly, but everything works great for me.
This means if you dont want to leave Sense but want to get the tons of useless and annoying T-Mobile and other bloatware apps out, you can. T-Mo are dicks and make almost 100% of the apps on it by default SYSTEM apps, therefore unremovable. So you'll need root and Titanium Backup to freeze or delete them. I'd recommend freezing the non-TMo one's just in case.
FLASHING ROMS
1. Flash Paul O Brien's intermin CWM touch version. Some things like USB mount dont work, but the important functions like wipe and flash and restart do. The CWM recovery seems permanent, based on my initial trials, so no worries about reflashing it each restart. I cant speak for the non-interim solutions, but from what I can gather, they are problematic, so avoid them for now.
2. Flash your ROM of choice from Clockworkmod Recovery. I'm using Black Dragon right now, but there are others out there as well. I'm personally looking forward to CM9, but its a little ways away, usability-wise.
So there you have it, all you US guys. Don't be afraid to mod your phone. Remember all the warranty void disclaimers as always. I'm not responsible for you bricking your phone. This is just my experience in just under 24hrs of use. Things are looking good for the One S.
Click to expand...
Click to collapse
Is this part a must? Would you mind PM'ing me with how to do this part if it's a must? I have Unlocked and rooted my phone, just waiting for a good ROM to come by.

Thongvilay said:
Is this part a must? Would you mind PM'ing me with how to do this part if it's a must? I have Unlocked and rooted my phone, just waiting for a good ROM to come by.
Click to expand...
Click to collapse
That step is only if you want to flash ROMs, or need to wipe cache, dalvik, etc. CWM is used for flashing and recovery/backup purposes. If you're not using ROMs yet, then you have no need for it.

nickmv said:
Hmm, interesting. Did you flash the interim recovery that Paul O Brien posted, and not another version? Just wanna make sure. I've heard of this happening in my past experience with the Nexus S, but I can't recall what the deal was. Regardless, I don't think you're in trouble. As with your GNex, it's very hard to completely brick the device unless you flash perhaps a bad hboot file, however I'm not really familiar with HTC devices.
This is my first HTC so I'm still trying to learn how the hboot and other processes work together. Sry to hear you had bad luck.
UPDATE: You should try the root install script. It tells the phone to boot after install. That might get you booted atleast.
Some thoughts:
1. Flash the stock recovery back and reflash CWM
2. Clear cache and dalvik within CWM, and make sure to use the 'Reboot System' option if you aren't already.
From what I can tell, your "boot-to-recovery" flag is set on the phone, and isn't getting cleared.
Click to expand...
Click to collapse
thanks for the tips, i had tried clearing cache/dalvik within CWM and it still would not work. and yes i did flas the interim CWM from paulobrien
luckily the phone would work via ADB while in CWM. So i pushed three different ROMS to the phone, at first each oen would lock up and reboot within 20 seconds of doing anything. I then went back into recovery & wiped data/cache/dalvik maybe 10 times out of sheer frustration. Then re-flashed a fresh copy of black_dragon_v4.0, didnt do anything after boot. just let it sit there till this morning.
now the phone seems to be working perfectly...
so hopefully if anyone encounters this problem my last couple posts will help them out!

suhailtheboss said:
thanks for the tips, i had tried clearing cache/dalvik within CWM and it still would not work. and yes i did flas the interim CWM from paulobrien
luckily the phone would work via ADB while in CWM. So i pushed three different ROMS to the phone, at first each oen would lock up and reboot within 20 seconds of doing anything. I then went back into recovery & wiped data/cache/dalvik maybe 10 times out of sheer frustration. Then re-flashed a fresh copy of black_dragon_v4.0, didnt do anything after boot. just let it sit there till this morning.
now the phone seems to be working perfectly...
so hopefully if anyone encounters this problem my last couple posts will help them out!
Click to expand...
Click to collapse
Wow, I have no idea dude. That sounds kinda crazy. Hopefully all will be well in the future and you won't come across it again.

the only variable i can think of is that i did have the phone about a week before launch. HTC mailed it to me directly.
I thought maybe that had somethign to do with it, but as far as i can tell the phone was the final shipping version.

I sent you a PM, trying to find a solution.

[Q] Bricked my G2x...Last resort, please help!

Sooo it seems I have now bricked my beloved G2x. I have tried every recovery method on xda I can find (a few times), but still no luck.
I was trying to restore stock on my phone to catch the new OTA update, and it has failed...miserably.
Now, my phone gets to the little T-Mobile G2x splash screen and then reboots. I've tried NVflash'ing the firmware, I've tried kdz (which I absolutely cannot get to work right), I've tried sacrificing a chicken to the LG powers-that-be (okay, haven't tried that...YET), but nothing has worked.
Does anybody know of an absolute "unbrick" method?
Thanks in advance for the help!
Also, every now and then, the phone will actually make it to the initial "Touch the android to begin." screen, but my battery (which was 100% charged before this started) now says 0%, even when plugged in.

these links were in the first page of me searching "brick help"
http://forum.xda-developers.com/showthread.php?t=1611968&highlight=brick+help
http://forum.xda-developers.com/showthread.php?t=1180331&highlight=brick+help
http://forum.xda-developers.com/showthread.php?t=1619893&highlight=brick+help

I've tried those methods, and almost every other I could find. I've searched this forum for hours today before posting this, and no matter what I use, I get stuck in either a bootloop or i get a reboot after a minute of being booted. I've tried different recoveries, different ROMs, different flashing methods, and it all ends up the same way.

if you've actually tried things you might want to post exactly what you have tried what were the outcomes and so on and so on. I'm not going to assume what you have tried and assume what the process you did and where you might have messed up. I'm sure neither is anyone else. So unless you help me help you we together are not going to get anywhere.

To the best of my recollection, here's how it went down:
Started off with running Genesis v1 Beta 6.
Ran G2x batch clean up tool w/ CWM Touch
Flashed cyanogen_p999-ota.eng.feli.zip in CWM
* At this point my phone would not make it past more than 1 minute after booting. It would boot up, but after approx. 1 minute, it would reboot, no matter what I did w/ it. This happened several times
Wiped everything through CWM, flashed Genesis again (default install)
*Had same reboot issues listed above
Used NVFlash to push stock V21e firmware http://forum.xda-developers.com/showthread.php?t=1248644
*After this, My phone would not make it past the "T-Mobile G2x with Google" splash screen. You would hear the T-mobile jingle, then the screen would "get stuck" for about one minute, and then the phone would reboot and go through the LG logos to the splash screen and repeat endlessly until I performed a battery pull
Restored stock recovery using NVFlash
*Did a reboot and suddenly saw the boot animation from Genesis!? Not sure how that happened, but it never made it past the boot animation
Ran G2x batch clean up again to try to "clean" the phone, and pushed the V21e firmware again
*Same boot problem
Flashed stock recovery again, then attempted to use KDZ. KDZ will continue to force close midway through the operation, and I cannot get it to work
Pushed V21e yet again
*Now it started making it to the initial set-up "Touch the android..." dialog. I could actually make it through this part, and then the phone would reboot again
*Somewhere in the middle of this, my battery went from reading 95%(The few times it would actually boot) to reading 0%. I wiped battery stats in CWM, but it didn't fix it. "Hey, maybe my battery actually died," I thought, so it's now on the wall charger, waiting for me to try to rescue it again.
I'm going to *attempt* to install a nandroid in CWM, and pray that it fixes things, but if that does not work, I'm at a complete loss

mt3g said:
if you've actually tried things you might want to post exactly what you have tried what were the outcomes and so on and so on. I'm not going to assume what you have tried and assume what the process you did and where you might have messed up. I'm sure neither is anyone else. So unless you help me help you we together are not going to get anywhere.
Click to expand...
Click to collapse
+1
More info would be great!
If I were you, would give a shot of mansa_noob's clean up tool:
http://forum.xda-developers.com/showthread.php?t=1590523
It will reorganize your partitions. Then you just need to flash CWM recovery, then the stock ROM.
Edit:
Just saw your new post, wow that's interesting. I'm not too sure if the touch CWM has anything to do with it, how about to try the normal recovery version of the clean up tool, then maybe a different stock ROM?
Sent from my LG-P999 using xda premium

the only thing I can think of will get me flamed lol, don't use those clean up tools unless it is a last resort! I can say I've never had an issue with just flashing after going through mounts and storage (data, system,cache) and wiping the main things.
The fact that the phone can be booted and it is showing images on the screen means you are not bricked. On the other hand, I've yet to read the issues you are describing, ever. You got quite mess on your hands.
KDZ is your best bet, what do you mean it just "continues to force close"

DupleX01 said:
+1
Just saw your new post, wow that's interesting. I'm not too sure if the touch CWM has anything to do with it, how about to try the normal recovery version of the clean up tool, then maybe a different stock ROM?
Sent from my LG-P999 using xda premium
Click to expand...
Click to collapse
Tried CWM 5.0.2.0, also. I've tried both the stock ROM and the basic cyanogen ROM (Sorry, can't remember exactly where in the cycle those fell...I've repeated several steps several times)

Alright, so It's fixed! Thanks for the interest.
Just for the sake of somebody who (somehow) might have something similar, here's what fixed it....and be warned, this is QUITE unorthodox:
My phone was fully charged (turned off, showing the charged battery icon). I removed the battery, the SIM, and the SD card, and stuck my phone in the fridge for about 10 minutes...That's right, the fridge. I read somewhere that this may help when writing to the disk, and I figured "why not?"
I then pushed V21e using NVflash again, and, lo and behold, it works like a champ! Now just to get the latest OTA update, sit back, and wait for the latest and greatest ROMs to trickle down.
Also, sorry about the original post being kind of vague...It was posted after literal hours of searching and trying different things, and the frustration clouded my brain.

that is crazy lol, but glad something worked for you...

mt3g said:
the only thing I can think of will get me flamed lol, don't use those clean up tools unless it is a last resort! I can say I've never had an issue with just flashing after going through mounts and storage (data, system,cache) and wiping the main things.
The fact that the phone can be booted and it is showing images on the screen means you are not bricked. On the other hand, I've yet to read the issues you are describing, ever. You got quite mess on your hands.
KDZ is your best bet, what do you mean it just "continues to force close"
Click to expand...
Click to collapse
Hey buddy. I won't flame. You are absolutely right. I don't use the cleanup tool a lot either but then since my bluetooth issue is fixed I am slacking .
I am curious though why it did not work but will respond to op in a minute.
Sent from my LG-P999 using XDA

rtotheichie said:
Alright, so It's fixed! Thanks for the interest.
Just for the sake of somebody who (somehow) might have something similar, here's what fixed it....and be warned, this is QUITE unorthodox:
My phone was fully charged (turned off, showing the charged battery icon). I removed the battery, the SIM, and the SD card, and stuck my phone in the fridge for about 10 minutes...That's right, the fridge. I read somewhere that this may help when writing to the disk, and I figured "why not?"
I then pushed V21e using NVflash again, and, lo and behold, it works like a champ! Now just to get the latest OTA update, sit back, and wait for the latest and greatest ROMs to trickle down.
Also, sorry about the original post being kind of vague...It was posted after literal hours of searching and trying different things, and the frustration clouded my brain.
Click to expand...
Click to collapse
I am afraid if my theory is correct your flash (memory) may be going. The symptoms you have described and the fix you mention would suggest a data retention problem. If it breaks again (i hope that I am wrong and it won't) you may have to stick it in the fridge again but if that happens get rid of it fast!
Sent from my LG-P999 using XDA

rtotheichie said:
Alright, so It's fixed! Thanks for the interest.
Just for the sake of somebody who (somehow) might have something similar, here's what fixed it....and be warned, this is QUITE unorthodox:
My phone was fully charged (turned off, showing the charged battery icon). I removed the battery, the SIM, and the SD card, and stuck my phone in the fridge for about 10 minutes...That's right, the fridge. I read somewhere that this may help when writing to the disk, and I figured "why not?"
I then pushed V21e using NVflash again, and, lo and behold, it works like a champ! Now just to get the latest OTA update, sit back, and wait for the latest and greatest ROMs to trickle down.
Also, sorry about the original post being kind of vague...It was posted after literal hours of searching and trying different things, and the frustration clouded my brain.
Click to expand...
Click to collapse
Yet another proof of G2X's unbrickable fame with a happy ending.
Happy for you!
Sent from my LG-P999 using xda premium