Database Users

[Q] Can Someone Tell Me What I'm doing Wrong?

This has happened to me twice now, I've had to replace my D2 because it keeps bricking for some reason. I don't know why, but now whenever I try to download something from my SD card (a rom or a theme) It just bricks. I go to mounts/storage, click on that then I go to download from SD, I select my rom and it doesn't work. It'll go to the boot logo, show Matt's logo (I used Matts Epic2.5) and won't stop repeating it over and over again.
Sometimes it'll show the whole logo, then after maybe 5 times it'll show half the logo then stop and keep repeating this process. I don't know why, but it used to always work in the past. What am I doing wrong? Do I need to wipe my data and cache every time now? I never had to before.
I really miss my Droid 1 (root wise lol)

BTW, I don't know if this means anything, but do I need to deodex my phone or however you say it :S, sorry I'm really new to droid 2. I don't even know what deodex means lol. Anyone help me on explaining what that means?

Deodexing or de-odex-ing is how it makes more sense to me just means that all of the apk's or applications on your phone are together and don't have stray .odex files in the /system/app folder (or wherever they're located). Phone dev's will leave these .odex files out of the .apk's so that load times are supposedly faster but the file called services.jar which needs to be edited for detailed themes has to be de-odexed before it can be edited and if one file is de-odexed then the others should all be.
I'm not sure what specifically the problem is and please don't be offended if I'm going too far but in order to mount /system the entry in mounts/storage has to read "unmount /system". Make sure the you've got the entire ROM, but wiping cache and data is worth a shot too.
Also if you have a major problem with your droid 2 you just need to flash the .sbf there are two different ways to do it (and two versions of the sbf). One in windows and the other in linux and (thanks to me lol) the linux version is available to anybody with a windows computer too.

Yeah I fixed my phone today using the windows sbf. Do you think it's worth it to deodex my phone? And I don't know what the problem seems to be I have the full rom and I never had to wipe before :/ I guess I'll just wipe every time now.

Most of the ROM's now are de-odexed so you shouldn't have to the only reason you would need to is to theme. To check and see if it's deodexed just use Terminal emulator and enter
Code:
$ cd /system/app
$ ls
This means change directory to /system/app then list the files in there.(it's a lower case L)
If there are files that end in .odex then it's not de-odexed.

UPDATE: I sbf my phone and got it "unbricked". So I just got root access and then I tried to instal the 2.5 Epic Rom. These are the steps I went through.
1. Went to Titanium Backup and restored my Droid Bootstrapper app.
2. Opened the app and did the Flash Recovery, is said success then I went into recovery mode.
4. I went to Mounts and Storage, pressed OK on Mount/system
5. Went to Install from SD Card.
6. Went to EUnleashed2.5 (however it is)
7. It installed only halfway and said install is complete and the screen would just sit there when it was only less than halfway full.
9. Now my phone is bricked again and I am currently unbricking it.
What am I doing wrong?
EDIT: By the way, if those things that I clicked on aren't exactly right, it was because I was typing it from memory because my phone was bricked and I couldn't actually see them.

First, you have not been bricked - you've had bootloops, which means some files are corrupted, missing, or incompatible. You can cure a bootloop, but you can't cure a brick.
My guess is you're trying to install Epic 2.5, which has 2.2.20 baseband/kernel dependencies, over your new 2.3.20 baseband/kernel from the sbf. In other words, Epic 2.5 can't and won't install on your phone anymore. You'll have to wait for Epic 3.0 or use another ROM that has been built off 2.3.20.

karnovaran said:
First, you have not been bricked - you've had bootloops, which means some files are corrupted, missing, or incompatible. You can cure a bootloop, but you can't cure a brick.
My guess is you're trying to install Epic 2.5, which has 2.2.20 baseband/kernel dependencies, over your new 2.3.20 baseband/kernel from the sbf. In other words, Epic 2.5 can't and won't install on your phone anymore. You'll have to wait for Epic 3.0 or use another ROM that has been built off 2.3.20.
Click to expand...
Click to collapse
Lol thanks, that makes a lot more sense to me now. I just saw his post about 3.0, I can't wait till it comes out. Thanks for the help!

Trouble with all ROMs

I bought a DX earlier this week. It was updated to system 2.3.340 before i left the store. I also have a D2 and experience flashing ROMs and SBFing. What is puzzling me here is that no matter what ROM I install i get random reboots. This happens no matter what apps, activities, etc... i am doing, even when just idle, i will look down and phone is rebooting. I haven't tried SBFing the DX yet because i can't find a clear answer on how i need to do it. I know that a full .340 SBF does not exist yet. I have a full .32 SBF file and a system only .340 file. I am assuming that i would flash the .32 full, then the .340, or could i just flash the .32 and then let the phone update the factory way to .340? I am getting this reboot problem with Rubix 1.9.5, Fission 2.4.3, and GummyJar 2.5. Any advice, input, or help would be greatly appreciated. THanks in asvance.

willjohnson said:
I bought a DX earlier this week. It was updated to system 2.3.340 before i left the store. I also have a D2 and experience flashing ROMs and SBFing. What is puzzling me here is that no matter what ROM I install i get random reboots. This happens no matter what apps, activities, etc... i am doing, even when just idle, i will look down and phone is rebooting. I haven't tried SBFing the DX yet because i can't find a clear answer on how i need to do it. I know that a full .340 SBF does not exist yet. I have a full .32 SBF file and a system only .340 file. I am assuming that i would flash the .32 full, then the .340, or could i just flash the .32 and then let the phone update the factory way to .340? I am getting this reboot problem with Rubix 1.9.5, Fission 2.4.3, and GummyJar 2.5. Any advice, input, or help would be greatly appreciated. THanks in asvance.
Click to expand...
Click to collapse
try here http://rootzwiki.com/index.php/Smartphones/Motorola/Droid-X/Droid-X.html#comment220 scroll down towards the end (idk if you use windows or linux but the linux method of sbf'ing is alot easier ive used both) except in their directions it says an older sbf file just insert the one you have, then go here http://www.mydroidworld.com/forums/...ystem-baseband-2-3-340-kernel-bootloader.html to download these zip files for kernel updater, 340 system update your baseband and bootloader should already be the correct ones, (i recently bought my X too) then once you finally root your newly sbf'd X and installed droid x bootstrap etc and get into clockwork mod recovery you can flash those 2 zips (recommend flashing only one at a time, reboot, and do the next) and then you should be updated to full .340
gl

http://forum.xda-developers.com/showthread.php?t=869007
heres a thread with discussion about those update zips

Thanks for the quick replies. Gonna try your suggestion tonight or tomorrow. Now i get random lock ups followed by a boot after about five minutes. The only upside right now is that its 4 days old so if i can get some resemblance of factory back on it then i can just exchange it Thanks again will report back with results.
And also by "insert the file you have", i assume you mean the file i have that is VRZ_MB810_2.3.32_01.sbf is the file i need to use in RSD Lite, then update the other files with clockwork recovery?
Thanks again.

willjohnson said:
And also by "insert the file you have", i assume you mean the file i have that is VRZ_MB810_2.3.32_01.sbf is the file i need to use in RSD Lite, then update the other files with clockwork recovery?
Thanks again.
Click to expand...
Click to collapse
correct tho the one i used had was labeled VRZ_MB810_2.3.32_1FF_01.sbf

I guess the one i got is ok? it came from the TBH app from the market? I would like to get ahold of the one you got too if thats possible, since you know that file works.
LOL i am a dumbass, left the FF part out for somereason, thats the exact file name i have. Thanks again.\
Edit- Just tried this, i don't know whats wrong but it has the start button in RSD Lite greyed out when i select the file, its the exact one listed above. Gonna try same file from different locations

Ok, so now i am starting to worry. Tried 3 different .320 full sbf's. All the same result. Failed process close to the begging. Then on the phone it says
Critical Error
FEBE
0047
Please Helppppp. I don't need a really expensive paperweight, all i need to do is get it so that GummyJar doesn't show on boot and i can take it back, its brand new.

Try removing the battery. Then boot into recovery (volume down + power) then do a factory reset/restore.
Sent from my ADR6300 using XDA App

Tried that, i finally got it to flash, i had the phone in the desk dock, didn't think about it. Once i plugged it into the usb cable direct everything went fine(so far). Also i noticed that with this phone and my wifes D2, i have to put a (1) at the end of the sbf file name to get RSD Lite to use it, otherwise the start button stays greyed out. THanks for the replies and help, will post again if there are any more problems.

willjohnson said:
Tried that, i finally got it to flash, i had the phone in the desk dock, didn't think about it. Once i plugged it into the usb cable direct everything went fine(so far). Also i noticed that with this phone and my wifes D2, i have to put a (1) at the end of the sbf file name to get RSD Lite to use it, otherwise the start button stays greyed out. THanks for the replies and help, will post again if there are any more problems.
Click to expand...
Click to collapse
ive heard there are several problems with rsd lol thats why ive stuck with my ubuntu/Linux its 10x easier

willjohnson said:
I guess the one i got is ok? it came from the TBH app from the market? I would like to get ahold of the one you got too if thats possible, since you know that file works.
LOL i am a dumbass, left the FF part out for somereason, thats the exact file name i have. Thanks again.\
Edit- Just tried this, i don't know whats wrong but it has the start button in RSD Lite greyed out when i select the file, its the exact one listed above. Gonna try same file from different locations
Click to expand...
Click to collapse
i also believe you DO have to have it all in specific locations but idk i use linux to do it, if you continue to play with the X after u get new one i would read up on how to dual boot ubuntu its a whole lot easier once you find ur way around i have it booting off of a 1TB external hard drive no need to install the correct moto drives etc..just plain easy lol

Finally total success!!!! Flashed .320 Full SBF, then used the Kernel and System updates you referenced and bam, back to stock. Now i feel better about ROM flashing, cause i can recover from most anything with this process. THanks again for your help and info.

willjohnson said:
Finally total success!!!! Flashed .320 Full SBF, then used the Kernel and System updates you referenced and bam, back to stock. Now i feel better about ROM flashing, cause i can recover from most anything with this process. THanks again for your help and info.
Click to expand...
Click to collapse
it only takes once correctly doing it to feel comfortable lol also make sure using droid x bootstrap recovery make sure to tap the first choice and let it do its thing, otherwise it will constantly reboot to recovery EVERY time you turn it back on

Well... the SBF and updating where successful. But even after the SBF, SD Card Formating(Long format in windows, then 3 times on phone to be sure), clean install and download of all Fission stuff i normally use, still get random reboots. Gonna SBF again and try Rubix and see how that goes. If it still has problems too, i may SBF again and go to the store and return phone for a new one.

willjohnson said:
Well... the SBF and updating where successful. But even after the SBF, SD Card Formating(Long format in windows, then 3 times on phone to be sure), clean install and download of all Fission stuff i normally use, still get random reboots. Gonna SBF again and try Rubix and see how that goes. If it still has problems too, i may SBF again and go to the store and return phone for a new one.
Click to expand...
Click to collapse
try something blurless like darkslide, which im currently running, no random reboots

Funnyface19 said:
try something blurless like darkslide, which im currently running, no random reboots
Click to expand...
Click to collapse
LOL funny you should mention, thats what i actually decided to go with instead. It really looks great, seems to be seemless too. Since you use it maybe you could tell me... Can you overclock? I downloaded the blurless version from their link and it has the blur alarm clock and a few others? is this right or is something wrong with the link? Thanks again.

willjohnson said:
LOL funny you should mention, thats what i actually decided to go with instead. It really looks great, seems to be seemless too. Since you use it maybe you could tell me... Can you overclock? I downloaded the blurless version from their link and it has the blur alarm clock and a few others? is this right or is something wrong with the link? Thanks again.
Click to expand...
Click to collapse
Well I haven't overclocked yet anyway the phone gets hot enuf lol plus coming from an Eris 1k is fast lol
Um yeah it should be wright depends on what the blur clock looks like lol
Sent from my DROIDX using XDA App

I looked back at there post in another forum and it actually says that they added a few Blur parts in the blurless rom. I guess some blur things just work better.

willjohnson said:
I looked back at there post in another forum and it actually says that they added a few Blur parts in the blurless rom. I guess some blur things just work better.
Click to expand...
Click to collapse
yeah but the obsidian rom is completely blurless just not everything working

Running DarkSlide4.1 can't tell u last I had a reboot
Sent from my DROIDX using XDA App

[Q] EVO Rom/Root problems

I am having some serious issues with my evo. I have tried 10 different methods, googled 100 different help guides and still no fix.
I had originally rooted my phone using simple root and put the "fixed" froyo rom on there. Everything worked fine, but I was outdated and having some really slow issues so I wanted to try a new rom...Fresh.
Well I tried a few methods, but I somehow reverted my evo back to a nonroot of the original OS. Whenever i go into hboot, my recovery does not work. I push the PC36img and load it, then restart then I attempt to go to my recovery where it gives me the error picture with the yellow/red triangle. I then select recovery (after pressing UP volume and powerbutton) and try to load update from sd card. Everytime I do that I get a Failed error.
I've tried to reroot using several methods off this website, I've done everything I can to get it working but can't. Any help would be GREATLY appreciated!

Try reflashing your recovery image.

BTW I have hboot 79.0 with S-ON, so it looks like I def became unrooted.

noweakness said:
BTW I have hboot 79.0 with S-ON, so it looks like I def became unrooted.
Click to expand...
Click to collapse
Not sure how it would have just unrooted itself. I would run an RUU from here: http://forum.xda-developers.com/showthread.php?t=884060
Then, I would re-root and start clean again.

Heaterz16 said:
Try reflashing your recovery image.
Click to expand...
Click to collapse
I have a recovery-ra.img, how do I tell it to flash it?
I pulled up this list of recovery files, is there a particular one I should use?
htt p://goo-inside.me/amon_ra/supersonic/

Heaterz16 said:
Not sure how it would have just unrooted itself. I would run an RUU from here: http://forum.xda-developers.com/showthread.php?t=884060
Then, I would re-root and start clean again.
Click to expand...
Click to collapse
Ok I downloaded the top item:
RUU_SuperSonic_S_Sprint_WWE_3.70.651.1_Radio_2.15.00.11.19_NV_1.90_release_161482_signed
Ran the exe, surprisingly picked up my phone and started the image update. My phone restarted and it forced closed the app on my computer. Now I have a new HTC logo for about 5 min on my phone not doing anything. Should I wait it out or restart my phone?

noweakness said:
Ok I downloaded the top item:
RUU_SuperSonic_S_Sprint_WWE_3.70.651.1_Radio_2.15.00.11.19_NV_1.90_release_161482_signed
Ran the exe, surprisingly picked up my phone and started the image update. My phone restarted and it forced closed the app on my computer. Now I have a new HTC logo for about 5 min on my phone not doing anything. Should I wait it out or restart my phone?
Click to expand...
Click to collapse
I would have waited about ten minutes then restarted the phone. If the phone is stuck at the HTC logo, then I would go ahead and re-run the RUU.
Let me know how it turns out.

Heaterz16 said:
I would have waited about ten minutes then restarted the phone. If the phone is stuck at the HTC logo, then I would go ahead and re-run the RUU.
Let me know how it turns out.
Click to expand...
Click to collapse
ok, finally got it working. Had to restart the phone manually and try it on a different computer. It updated it to the newer version of android and hboot, thank goodness! That was the easiest and most productive thing I've been able to do so far, thanks!
Well now I try to boot into recovery and get the same error:
can't open /cache/recovery/command
Then I get :
E: signature verification failed
Installation aborted
When i try to load update from sdcard

noweakness said:
ok, finally got it working. Had to restart the phone manually and try it on a different computer. It updated it to the newer version of android and hboot, thank goodness! That was the easiest and most productive thing I've been able to do so far, thanks!
Well now I try to boot into recovery and get the same error:
can't open /cache/recovery/command
Then I get :
E: signature verification failed
Installation aborted
When i try to load update from sdcard
Click to expand...
Click to collapse
Ok, so, I think you said you got the RUU working which would have completely restored the phone to unrooted and stock from factory.
Now, you need to re-root your phone using one of the methods on xda. I used the manual method here: http://forum.xda-developers.com/showthread.php?t=829045. However, many people have had success with the one-click methods.
After you re-root (which will likely included installing a recovery), select a rom you want to try, boot to recovery, wipe and flash it. A great starter ROM is MikFroyo 4.6 or 4.5.

Try downloading the PC36IMG.zip from here: http://forum.xda-developers.com/showthread.php?t=705026
put that on the root of your SD card, then boot into HBOOT and it should find that PC36IMG.zip after a few seconds and ask if you want to flash it. Choose yes and let it finish. Should then be able to reboot into recovery.

ok thanks, i'll try it when I get back home

jesuspgt said:
Try downloading the PC36IMG.zip from here: http://forum.xda-developers.com/showthread.php?t=705026
put that on the root of your SD card, then boot into HBOOT and it should find that PC36IMG.zip after a few seconds and ask if you want to flash it. Choose yes and let it finish. Should then be able to reboot into recovery.
Click to expand...
Click to collapse
Ok, I tried this method...the filesize of pc36img.zip is only 3.5mb, but it didn't seem to work. It scanned the file then just went back to the hboot screen with my options never asking to flash.
I'm going to try to reroot using the other method now...

So I clicked the link and he forwarded to the autoroot.bat page so I used his method. It worked well (the 2nd time around) all the way until it started to push amon_ra_1.8-mod.... then after that it says rebooting into the bootloader, and it reboots into it and just says waiting for phone...
It does appear that my phone is rooted now, but my recovery is still not working. If I use ROM manager will it work since my phone is rooted or do I need to have a rooted ROM to run it off of?

noweakness said:
So I clicked the link and he forwarded to the autoroot.bat page so I used his method. It worked well (the 2nd time around) all the way until it started to push amon_ra_1.8-mod.... then after that it says rebooting into the bootloader, and it reboots into it and just says waiting for phone...
It does appear that my phone is rooted now, but my recovery is still not working. If I use ROM manager will it work since my phone is rooted or do I need to have a rooted ROM to run it off of?
Click to expand...
Click to collapse
Does your phone show s-off while in the bootloader? If so you should be able to run the FlashZip script and use that to flash the pc36img-sprintlovers zip. That one contains everything needed to bring your phone up to date and will leave you with a rooted rom and recovery.
Sent from my PC36100 using XDA Premium App

xHausx said:
Does your phone show s-off while in the bootloader? If so you should be able to run the FlashZip script and use that to flash the pc36img-sprintlovers zip. That one contains everything needed to bring your phone up to date and will leave you with a rooted rom and recovery.
Sent from my PC36100 using XDA Premium App
Click to expand...
Click to collapse
FINALLY! Thanks a million! My recovery is now working and it installed the built in sprinter lovers rom, I guess the anti-virus was stopping it so I disabled it and ran the flash script. I was able to install Fresh on there, just to try it out. I do have a few questions though:
1. I noticed after going through many pages that to update to a newer ROM version you don't always have to wipe clean, you can just install (or flash) the new update? I noticed in Fresh there is a built in app that does that. Is this true for most ROMS or only certain ones?
2. I assume I am using the RA recovery. I noticed the backup/restore feature on there. What exactly does that backup and when should I use it?
3. I've noticed I've been very low with memory on my phone (not SD card), I have about 258MB free. How can I clear space and when I mount my phone what files are important to keep and can I get rid of, is it okay to get rid of my rom.zip's and radio.zip's?
Thanks again to everyone, autoroot was def the most painless root ever.

noweakness said:
FINALLY! Thanks a million! My recovery is now working and it installed the built in sprinter lovers rom, I guess the anti-virus was stopping it so I disabled it and ran the flash script. I was able to install Fresh on there, just to try it out. I do have a few questions though:
1. I noticed after going through many pages that to update to a newer ROM version you don't always have to wipe clean, you can just install (or flash) the new update? I noticed in Fresh there is a built in app that does that. Is this true for most ROMS or only certain ones?
2. I assume I am using the RA recovery. I noticed the backup/restore feature on there. What exactly does that backup and when should I use it?
3. I've noticed I've been very low with memory on my phone (not SD card), I have about 258MB free. How can I clear space and when I mount my phone what files are important to keep and can I get rid of, is it okay to get rid of my rom.zip's and radio.zip's?
Thanks again to everyone, autoroot was def the most painless root ever.
Click to expand...
Click to collapse
1) You'll want to always wipe your cache/dalvik (I do everytime I'm in the recovery) but the Data depends on the ROM. Usually if you are going from one sense rom to another you are ok and the same for AOSP to AOSP. Going from Sense to AOSP you'll need to wipe data though.
2) Autoroot comes with a modified version of AmonRA, they are mostly just speed tweaks. To make a complete backup of your ROM select Boot (kernel), System (ROM), Data (Apps & Settings) and .android (apps on SD card)
3) You can delete the zips from your sd card if you don't need them but that's about normal for free memory.

Help with recovering my Droid!!

Ok here is where I am at...I can only get into stock recovery and I have formatted data and factory reset and I only get the Motorola logo, I cannot boot into Android!
I used the Boostrap loader to get into Clockwork Recovery and wiped everything to install Apex but when I installed Apex it would not boot! I couldn't do anything but get into stock recovery. After rooting we deleted some system apps which I hear you should not do since you can't get the factory reset to work!! What can I do now? I am downloading a couple files so i can try and apply an update.zip to at least get back to stock. I did take a nandroid of my phone after I rooted but I can't get into Clockwork Recovery to restore it. Thanks in advanced.

Reinstall the removed system applications or SBF.
Sent from my DROIDX using XDA App

Can you please provide directions? I saw a site that showed how to copy over the uninstalled apps but I don't know where to download them, do you have a place?
How do i copy the sbf back? At the moment the phone will not even power on for some reason.

Android314 said:
Can you please provide directions? I saw a site that showed how to copy over the uninstalled apps but I don't know where to download them, do you have a place?
How do i copy the sbf back? At the moment the phone will not even power on for some reason.
Click to expand...
Click to collapse
Extract the zip file you used to install Apex and copy (push using adb) the contents of /system/app (or just /app/) from the extracted directory into your phone's /system/app/ directory.
You just have to do this for any apps you removed from the system folder.
If you would rather go the SBF route there are plenty of guides.
Also, to your note about the phone not powering on, if the battery died you will have to get a charged Droid X battery, as it will not charge in this state. Or you can splice a cable to charge the battery manually.
To check the battery state enter bootloader mode (hold both volume buttons and press power) and check whether is says 'OK To Program' or 'Battery Low'.
Sent from my DROIDX using XDA App

Also its important to tell you that if you sbf on a low battery you could brick.... But even still I would say sbf is still the easiest option... You need the correct .sbf files and a program called rsd lite enter dl mode on the phone and bam stock dx. Make sure you wipe cache
/data after sbf in stock recovery or it sometimes loops
Sent from my rooted Nexus1

droid512 said:
Also its important to tell you that if you sbf on a low battery you could brick.... But even still I would say sbf is still the easiest option... You need the correct .sbf files and a program called rsd lite enter dl mode on the phone and bam stock dx. Make sure you wipe cache
/data after sbf in stock recovery or it sometimes loops
Sent from my rooted Nexus1
Click to expand...
Click to collapse
That's not really true, you just need to charge your battery. I've done this several times and a universal charger from radio shack fixed me up nicely (25 bucks). I've lost battery in the middle of sbf several times though and the Droid X has been unbrickable for me.
I'll put this out there though... if you do run dead in the middle of sbf you have to install ubuntu or another brand of linux in a VM or on another box, and flash your SBF with SBF_Flash. Unlike RSD Lite, that works 100% of the time no matter what. I've been "bricked" and nearly **** myself until I tried it on linux and it worked without a hitch.

Also I did this cut my charger wire and put colors accordingly on Battrey directly and recharged and started over
Sent from my DROIDX using XDA App

i guess u didn't make a backup b4 u did anything ...tisk tisk...sorry ur having problems but thats why u make a backup b4 u do anything.
could try putting ur sd card in ur computer, download a dif rom, and try flashing that...try libertys new rom
send from my cm7

{Guide} Easy CM7 from stock Froyo

This is a guide to install cyanogenmod 7.2 on the Motorola Flipside coming from stock Froyo the fastest and easiest way.
1. Root the flipside using superoneclick
2. Download the flipout recovery apk from the flipside development section
Link: http://forum.xda-developers.com/showthread.php?t=1136105
3. Download the Cyanogenmod rom from the flipside general section
Link: http://forum.xda-developers.com/showthread.php?t=1517880
4. Move both the apk and the rom zip to your SD card of your device
5. Turn on your device and then install the apk.
6. After installation open the app and hit install recovery system.
7. When its done hit reboot recovery
8. After its in recovery wipe data, cache, dalvik cache
9. Install rom zip from SD card
10. When complete hit reboot system now
Note: If It does not reboot but instead bootloops, pull the battery and the boot the phone while holding the x on the physical keyboard, when the motorola symbol appears let go of the power button while still holding the x button. once you see the yellow caution symbol with the android press vol up and vol down. In this recovery wip data and cache then rebbot. it should now boot into CM7
Enjoy
Hit thanks please
All Credit Goes To Those Who Made This Possible

Thanks. Going to try this now. Fingers crossed!
Edit: Ok. Successful install on the first try. A few problems though. 3g doesn't work (known issue) and I haven't been able to get link2sd working again just yet. There's a lot more ram to play with and the overall performance thus far is awesome. Its like my phone got a new engine. Everything is fast and zippy and runs as smooth as butter.
Sent from my MB508 using XDA

jovanphilip said:
Thanks. Going to try this now. Fingers crossed!
Edit: Ok. Successful install on the first try. A few problems though. 3g doesn't work (known issue) and I haven't been able to get link2sd working again just yet. There's a lot more ram to play with and the overall performance thus far is awesome. Its like my phone got a new engine. Everything is fast and zippy and runs as smooth as butter.
Sent from my MB508 using XDA
Click to expand...
Click to collapse
Glad to hear that. And yes the 3g doesent work. makes the phone reboot randomly. to fix go into mobile network settings and click use 2g networks only. they worked well enough for me. Happy to see i helped someone out.

Dixinormous said:
Glad to hear that. And yes the 3g doesent work. makes the phone reboot randomly. to fix go into mobile network settings and click use 2g networks only. they worked well enough for me. Happy to see i helped someone out.
Click to expand...
Click to collapse
I didnt have that problem with mine. Didnt have to use that fix as it was working just fine without going through that. Unfortunately I bricked mine after I stupidly reinstalled the flipout bootloader again. (DO NOT do that). Its stuck in an endless boot loop. Im unable to flash the sbf for froyo through RSD Lite because the phone switches off when its plugged into the pc. Which means its bricked unless i can get an official update.zip to flash through the bootloader manually. (i doubt that would even work because you cant downgrade with an update.zip file afaik)

jovanphilip said:
I didnt have that problem with mine. Didnt have to use that fix as it was working just fine without going through that. Unfortunately I bricked mine after I stupidly reinstalled the flipout bootloader again. (DO NOT do that). Its stuck in an endless boot loop. Im unable to flash the sbf for froyo through RSD Lite because the phone switches off when its plugged into the pc. Which means its bricked unless i can get an official update.zip to flash through the bootloader manually. (i doubt that would even work because you cant downgrade with an update.zip file afaik)
Click to expand...
Click to collapse
Why would you reinstall the flipout bootloader?? after installing the cm7 its recovery is installed as well. to enter it all you have to do is hit reboot and the recovery from your power menu. sounds like u messed up bigtime

I know. I really messed up. I think I did it to reflash the rom to bring it back to stock settings. I carried it back to the store I bought it. My warranty is still valid and they don't have the technical means to figure out whether I tampered with the software. I'll likely get a new one or another one worth the same value I paid for the flipside.
I was about to sell it to a friend anyway as I'm more interested in the galaxy nexus. I guess it's not all that bad. If I do get it or a new one back, I'll donate it to someone working on the ROM. So in the end, we all win.