What's new
DroidForums.net | Android Forum & News

This is a sample guest message. Register a free account today to become a member! Once signed in, you'll be able to participate on this site by adding your own topics and posts, as well as connect with other members through your own private inbox!

[ROM] [BETA] CyanogenMod 7 for Droid 2

Can he use the tbh sbf zip? If not and you needed to use rsd lite, use this link

TBH & MyDroidWorld Present: Droid 2 (2.3.20) Triple Threat

If you need help, pm me and I'll call you if you need help with a walk through.

Droid 2-honeybread cyanogenmod 7 (build-16)

That sounds like it could work... If only I could actually boot the phone. The phone just stays at the moto logo, it doesn't even get to the cyanogenmod 7 boot animation.
 
Can you get into the bootloader? Power and up? You'll sbf from there. Make sure you have a good charge on the battery. You can't charge it now

Droid 2-honeybread cyanogenmod 7 (build-16)
 
Can you get into the bootloader? Power and up? You'll sbf from there. Make sure you have a good charge on the battery. You can't charge it now

Droid 2-honeybread cyanogenmod 7 (build-16)

Yes I can get to a screen that says "bootloader, d2.32, battery OK, OK to program, connect USB, data cable"

Ps commas are line spaces.
 
Last edited:
Perfect. That's what you want. Turn off the phone now until you're ready to sbf. Save that juice! Now use the thread above to dl the full sbf file and extract it to the desktop. Dl and install rsd lite 4.9 to your pc and go to motorola.com to getting the latest drivers.

Droid 2-honeybread cyanogenmod 7 (build-16)
 
before I flashed build #16 I was on #17 all the way down until build 4 I think. When I flashed build 4 i completely wiped it, and since then I have just wiped the dalvik cache and installed the next version from rom manager.

I don't understand what the heck you did here. You were on #17? From where? Build #16 is the latest. I don't see #17 anywhere. You proceeded to flash #16 over #17? You kept flashing older builds on top of the newer ones till build #4? Why? That makes absolutely no sense.

The older the build you run on the more bugs and issues you face. The reason for the nightlies is to work out bugs and issues and post it for people to flash on top of their current build. That is the purpose of eliminating problems, adding new features and additions and such. Build #16 contains source codes and everything else from the very first build. Only difference is the tweaking (fixing bugs and issues, adding features and additions, etc). Every change made to a build is carried onto the next nightly.
 
I've been told that I could do that... I forget the source but I was told that you only needed to do a complete wipe when your installing a totally new rom. And I've been doing that since build #4 and this is the only one I've had a problem with. I assume there's an SBF tutorial around here somewhere, right?

I didn't mean "you can't do that"; I was just curious as to why you were flashing an older build over a newer one.
 
I've been told that I could do that... I forget the source but I was told that you only needed to do a complete wipe when your installing a totally new rom. And I've been doing that since build #4 and this is the only one I've had a problem with. I assume there's an SBF tutorial around here somewhere, right?

I didn't mean "you can't do that"; I was just curious as to why you were flashing an older build over a newer one.

You aren't suppose to flash older builds on top of newer ones and proceed down the line of nightlies like that. That's the very reason why his phone is messed up right now. Basically the newer builds took on changes from the older build and overwrote parts of the script, codes, framework-res and other stuff thus making it go haywire. Think of it like trying to put a truck engine inside something like a Porche. It doesn't work.
 
I was wondering about where he found build 17. I didn't think there was one as of today. Wow, this is one big fuster cluck indeed. Never heard of going backwards.

By the way, I am overjoyed with cm so far. So happy I finally jumped over.
Just for my information, am I on the froyo kernel now? If for some reason I wanted to go back to gb roms (I know cm is gb, but I mean liberty, Apex etc..), will I need to flash the monster file again first? I assume so.

Droid 2-honeybread cyanogenmod 7 (build-16)
 
Wow I guess I can't speak today.. So to clear it up:

I started at build 4. Every succeeding day I flashed the new nightly ontop of the previous ( so 5 atop 4, 6 atop 5, etc.) and wiped the dalvik cache only. I ended up with build 16, which caused the problem I spoke about above. I never had build 17, that was a typing error that caused a whole lot of rather funny debate about me being stupid (haha).

Hope that clears it up.. And I will be using the full SBF to fix it. Thank you all
 
Wow I guess I can't speak today.. So to clear it up:

I started at build 4. Every succeeding day I flashed the new nightly ontop of the previous ( so 5 atop 4, 6 atop 5, etc.) and wiped the dalvik cache only. I ended up with build 16, which caused the problem I spoke about above. I never had build 17, that was a typing error that caused a whole lot of rather funny debate about me being stupid (haha).

Hope that clears it up.. And I will be using the full SBF to fix it. Thank you all

I don't think any of us thought you were stupid; I for one was just confused as to why you would want to flash an older build over a newer one. Thanks for clearing it up. Unfortunately, I still can't help you because I've never had a problem upgrading from build to build using ROM Manager, and only wiping Dalvik cache. My recommendation to SBF still stands.
 
I was wondering about where he found build 17. I didn't think there was one as of today. Wow, this is one big fuster cluck indeed. Never heard of going backwards.

By the way, I am overjoyed with cm so far. So happy I finally jumped over.
Just for my information, am I on the froyo kernel now? If for some reason I wanted to go back to gb roms (I know cm is gb, but I mean liberty, Apex etc..), will I need to flash the monster file again first? I assume so.

Droid 2-honeybread cyanogenmod 7 (build-16)

My understanding is that you are correct. It is a froyo kernel. You have to go monster to go back to the other gb roms.

Sent from my DROID2
 
Anyone having an issue with Dolphin mini? Whenever I hit the menu key within the application, I get a fc. It sucks because this is my favorite browser. I'll just use the stock for now.

Droid 2-honeybread cyanogenmod 7 (build-16)
 
I've run into a pretty big issue on my phone and I was wondering if I could get some opinions on what to do.

So last night I was on cm7 build 6 official, and I decided to try out liberty 2.01 to see if I could get some better battery life. I formated system/wiped data/wiped cache, and installed liberty successfully.

After messing around with it and trying out some themes, I decided I really didn't like it after coming from cm7, so I downloaded the official build 16 and flashed it after formating system/wiping data/wiping cache.

The rom flashed successfully and I have everything up and running but...my phone won't charge. I am using the wall charger and when I plug it up, the battery doesn't drain and the icon is moving like it is charging, but the percentage never goes up.

After plugging and unplugging it, I did get it to charge to 90% but it would go no further. So I went ahead and did the battery calibration, and let the phone run down to about 80% and decided to try to charge it again. Now it's gotten up to 83% and just sitting there. Any ideas?
 
It seems like you made some head way. You calibrated which is what I would have suggested. Not sure, but I think it is charging. It's just representing it wrong. I'll look around.



On another topic, Is it possible to flash the imoseyon tweaks or use a systcl app to perform some tweaks or should I leave it alone?

Droid 2-honeybread cyanogenmod 7 (build-16)
 
Last edited:
Back
Top