Related
A little over a month ago I flashed the damagecontrol ROM and haven't looked back. Aside from having 2.1 early, I was also able to access su features, blah blah blah. My question is: I am still losing internal memory even after enabling A2SD, partitioning my SD card into three sections (ext3, swap, and probably fat32 or something). I noticed a gain of about 40mb right away but each time I download a program my internal memory shrinks. Any ideas? I'm not a pro at this but really wanting to learn.
-------------------------------------
Sent via the XDA Tapatalk App
joshuaharp said:
A little over a month ago I flashed the damagecontrol ROM and haven't looked back. Aside from having 2.1 early, I was also able to access su features, blah blah blah. My question is: I am still losing internal memory even after enabling A2SD, partitioning my SD card into three sections (ext3, swap, and probably fat32 or something). I noticed a gain of about 40mb right away but each time I download a program my internal memory shrinks. Any ideas? I'm not a pro at this but really wanting to learn.
-------------------------------------
Sent via the XDA Tapatalk App
Click to expand...
Click to collapse
Even with A2SD there are still files that get written to internal storage for cacheing. You will see your memory go down.
Ah. I didn't realize that. Are there other ways to free up the internal memory? I'm down to around 25mb...
-------------------------------------
Sent via the XDA Tapatalk App
If you have a nice class of sd card you could move dalvik to sd. That freed up a good spot of memory for me.
the same thing is going on with my phone i only see an added 40mb onto the internal storage when i put on a2sd,when i hear about other kids that get around 90mb when using a2sd.
willowmp said:
If you have a nice class of sd card you could move dalvik to sd. That freed up a good spot of memory for me.
Click to expand...
Click to collapse
I just threw a 4GB Class 6 in and partitioned it. Before that I was running the stock 2GB (Class 2 I think). I've been considering a few options but not sure what the process should be and how to proceed:
- dalvik cache to sd
- jit compiling (alhtough, I've almost completely ruled this out due to rumors of instability issues)
- swapping sd (I'm not sure if this will have ill-effects on my system or not)
I would feel at more liberty to experiment if I knew what to do if my phone ran into an error that crippled it (i.e., stuck in boot loop). I'm really fresh to this, so it's a bit intimidating at first.
joshuaharp said:
I would feel at more liberty to experiment if I knew what to do if my phone ran into an error that crippled it (i.e., stuck in boot loop). I'm really fresh to this, so it's a bit intimidating at first.
Click to expand...
Click to collapse
Before you read one more post on this forum go install RA-Amon's recovery and make a nandroid backup. Then copy the backup folder onto your computer.
That is if you haven't already done so. This will save you a lot of trouble should something go wrong, unless you really do something spectacular.
Edit: Just checked my internal memory. 149mb free and I have a handfull of apps installed atm.
On another note I flashed the godmode overclocked kernel, the 768 one or whatever, and installed setcpu, and my god my phone is fast. Current settings are max 767, min: 518. Yes my min is fairly high but at 518 it is butter smooth and I have multiple batteries so...
willowmp said:
Before you read one more post on this forum go install RA-Amon's recovery and make a nandroid backup. Then copy the backup folder onto your computer.
That is if you haven't already done so. This will save you a lot of trouble should something go wrong, unless you really do something spectacular.
Edit: Just checked my internal memory. 149mb free and I have a handfull of apps installed atm.
On another note I flashed the godmode overclocked kernel, the 768 one or whatever, and installed setcpu, and my god my phone is fast. Current settings are max 767, min: 518. Yes my min is fairly high but at 518 it is butter smooth and I have multiple batteries so...
Click to expand...
Click to collapse
This kernel (.29 kernel, right?) is one I've been recently considering. I've made a nandroid backup through ROM Manager (is this as good as RA-Amon's recovery?). I'm not sure what to do with this should something go wrong...unless I can boot up and have access to the ROM Manager app – I'll cross that bridge when I come to it. Some questions:
concerning flashing a recovery
- what exactly does this do? (as I understand it, it writes a recovery file to my sd card, so that i can boot up in recovery mode should something cause my os to fail...is this correct?)
concerning the godmode overclocked kernel
- how long have you had this flashed on your phone?
- can I flash over my current ROM (damagecontrol 2.08.1)?
- will I lose info and have to wipe everything not on my SD card?
- I've partitioned my sd card for A2SD, will this cause problems?
- how long is your battery life on average?
Thanks dude.
willowmp said:
Before you read one more post on this forum go install RA-Amon's recovery and make a nandroid backup. Then copy the backup folder onto your computer.
That is if you haven't already done so. This will save you a lot of trouble should something go wrong, unless you really do something spectacular.
Edit: Just checked my internal memory. 149mb free and I have a handfull of apps installed atm.
On another note I flashed the godmode overclocked kernel, the 768 one or whatever, and installed setcpu, and my god my phone is fast. Current settings are max 767, min: 518. Yes my min is fairly high but at 518 it is butter smooth and I have multiple batteries so...
Click to expand...
Click to collapse
What did you set your swap and ext on when you partitioned your sd
xxxk15 said:
What did you set your swap and ext on when you partitioned your sd
Click to expand...
Click to collapse
ext: 1024 (or whatever the first 1gig choice is, I believe it is something like this)
swap: 30 (I believe, or whatever it automatically pops up as when formatting)
Through Dconfig I have apps2sd, dalvik to sd, and sd swapping with the default 30mb enabled.
Dalvik heap is set to 16mb and lowmemkiller set to less. JIT not enabled.
Current version DamageControl, the 768 overclocked kernel and toast's newest radio.
joshuaharp said:
This kernel (.29 kernel, right?) is one I've been recently considering. I've made a nandroid backup through ROM Manager (is this as good as RA-Amon's recovery?). I'm not sure what to do with this should something go wrong...unless I can boot up and have access to the ROM Manager app – I'll cross that bridge when I come to it. Some questions:
concerning flashing a recovery
- what exactly does this do? (as I understand it, it writes a recovery file to my sd card, so that i can boot up in recovery mode should something cause my os to fail...is this correct?)
concerning the godmode overclocked kernel
- how long have you had this flashed on your phone?
- can I flash over my current ROM (damagecontrol 2.08.1)?
- will I lose info and have to wipe everything not on my SD card?
- I've partitioned my sd card for A2SD, will this cause problems?
- how long is your battery life on average?
Thanks dude.
Click to expand...
Click to collapse
RA-Amon's custom recovery is a must and is vastly more important than a back-up app. RA-Amon's recovery is an actual recovery image, thus as long as your phone boots up to the HTC logo you should be able to access RA-Amon's recovery and thus restore the backup before the phone is even accessing the rom.
Flashing a recovery image is like flashing a rom, but instead of a rom you are flashing a recovery image. Your phone has a stock recovery image on it right now, I don't know the key combo but hold a certain pattern of keys down while turning the phone on and you will enter it. It looks I think like a triangle with an ! in the middle or something. This is sorta useless for us though because I don't think you can really do much with it.
When you flash a recovery img (RA-Amon's) that stock recovery image is just replaced with Amon's. After you do flash the recovery holding the HOME and power button to turn the phone on and continuing to hold it will cause you to enter Amon's recovery, which is a green menu. From this menu you can amke backups/restore them, wipe the data on the phone (factory reset), flash .zips (roms, bootscreens, themes, kernels) and other things.
What you are referring to the writing backup to sd card is called nandroid. Nandroid is an option in the recovery, so yes if you do flash the wrong rom or your phone won't boot up (boot loop or whatever) as long as you can access recovery which is one of the first things loaded when you hit the power button (unless you really do something spectacular like flashing a gsm hero's radio you almost always will be able to get into recovery. don't even touch radios right now, flash the wrong one and your phone won't even turn on/charge. aka your motherboard will be totaled) so you will almost always be able to nandroid recovery your os if something does go wrong.
In short before you do anything flash the recovery.
Now on to your other questions. I have been running the overclocked kernel for one day, but it appears stable and seems to be working good for me. When you flash a kernel you always flash it over a rom, because if you do it the other way the rom will replace the kernel. So yes once you have damagecontrol or another rom that supports that kernel you can simply go into recovery and use flash .zip to flash the kernel over the rom. As always make sure to make a nandroid before doing so.
DamageControl supports apps2sd, and you enable it to use a2sd using the Dconfig app that is included in the rom. It is generally a good idea to partition your sd card whenever you switch between roms unless they say it is fine. You should go ahead and copy over a backup of your sd card to your computer, however you need not format or wipe your sd card when flashing roms. Honestly I don't think you need to partition your sd card again, unless after you flash the rom the os won't boot up all the way or loops/crashes. If it does then partition the sd card and try rebooting the phone and it should fix it.
Also you can format and partition your sd card in recovery under Other.
As for my battery life I have been switching b/w roms and such and I just started using the OC kernel, but with the DamageControl rom back when I only had that flashed my batt life was good.
However I do have 3 batteries and an external battery charger for my phone. Check out the accessories section of this forum, 2 batteries and the charger for 11 bucks from Hong Kong on ebay.
Hope I helped.
So, through the damagecontrol dconfig app I banned "sense", rebooted and now my phone is stuck in a bootloop. Do I restore from previous nandroid backup or do I need to flash my phone? Suck.
joshuaharp said:
So, through the damagecontrol dconfig app I banned "sense", rebooted and now my phone is stuck in a bootloop. Do I restore from previous nandroid backup or do I need to flash my phone? Suck.
Click to expand...
Click to collapse
Just want to say first off: "I am an idiot". Nandroid backup from 5 days ago, booted up by holding *home and *power, then selecting to restore. Very easy. I can actually breathe now. Back in business. Sorry to waste your guy's time. We can keep the thread going minus my drama...
joshuaharp said:
Just want to say first off: "I am an idiot". Nandroid backup from 5 days ago, booted up by holding *home and *power, then selecting to restore. Very easy. I can actually breathe now. Back in business. Sorry to waste your guy's time. We can keep the thread going minus my drama...
Click to expand...
Click to collapse
It's all good.
See why I emphasized flashing your recovery before messing with anything? xD
xxxk15 said:
What did you set your swap and ext on when you partitioned your sd
Click to expand...
Click to collapse
I set the swap to 32mb and ext3 to 512mb I believe...does this sound right?
willowmp said:
RA-Amon's custom recovery is a must and is vastly more important than a back-up app. RA-Amon's recovery is an actual recovery image, thus as long as your phone boots up to the HTC logo you should be able to access RA-Amon's recovery and thus restore the backup before the phone is even accessing the rom.
Flashing a recovery image is like flashing a rom, but instead of a rom you are flashing a recovery image. Your phone has a stock recovery image on it right now, I don't know the key combo but hold a certain pattern of keys down while turning the phone on and you will enter it. It looks I think like a triangle with an ! in the middle or something. This is sorta useless for us though because I don't think you can really do much with it.
When you flash a recovery img (RA-Amon's) that stock recovery image is just replaced with Amon's. After you do flash the recovery holding the HOME and power button to turn the phone on and continuing to hold it will cause you to enter Amon's recovery, which is a green menu. From this menu you can amke backups/restore them, wipe the data on the phone (factory reset), flash .zips (roms, bootscreens, themes, kernels) and other things.
What you are referring to the writing backup to sd card is called nandroid. Nandroid is an option in the recovery, so yes if you do flash the wrong rom or your phone won't boot up (boot loop or whatever) as long as you can access recovery which is one of the first things loaded when you hit the power button (unless you really do something spectacular like flashing a gsm hero's radio you almost always will be able to get into recovery. don't even touch radios right now, flash the wrong one and your phone won't even turn on/charge. aka your motherboard will be totaled) so you will almost always be able to nandroid recovery your os if something does go wrong.
In short before you do anything flash the recovery.
Now on to your other questions. I have been running the overclocked kernel for one day, but it appears stable and seems to be working good for me. When you flash a kernel you always flash it over a rom, because if you do it the other way the rom will replace the kernel. So yes once you have damagecontrol or another rom that supports that kernel you can simply go into recovery and use flash .zip to flash the kernel over the rom. As always make sure to make a nandroid before doing so.
DamageControl supports apps2sd, and you enable it to use a2sd using the Dconfig app that is included in the rom. It is generally a good idea to partition your sd card whenever you switch between roms unless they say it is fine. You should go ahead and copy over a backup of your sd card to your computer, however you need not format or wipe your sd card when flashing roms. Honestly I don't think you need to partition your sd card again, unless after you flash the rom the os won't boot up all the way or loops/crashes. If it does then partition the sd card and try rebooting the phone and it should fix it.
Also you can format and partition your sd card in recovery under Other.
As for my battery life I have been switching b/w roms and such and I just started using the OC kernel, but with the DamageControl rom back when I only had that flashed my batt life was good.
However I do have 3 batteries and an external battery charger for my phone. Check out the accessories section of this forum, 2 batteries and the charger for 11 bucks from Hong Kong on ebay.
Hope I helped.
Click to expand...
Click to collapse
Dude...helped IMMENSELY! I'm still digesting it.
That's good to know about flashing radios. I was going to flash the most recent one for 2.1 roms on CDMA heros, but I think I'll wait to hear more about it.
I think I feel comfortable flashing the .29 kernel over my current ROM. I gotta be honest though, the DConfig thing kind of weirds me out now, after trying to use it. I'm not sure which button is going to cause my phone to freak out.
If you have a nice class of sd card you could move dalvik to sd. That freed up a good spot of memory for me.
Click to expand...
Click to collapse
I'm considering doing this but have read that this causes issues with nandroid backup. Have you experienced this?
-------------------------------------
Sent via the XDA Tapatalk App
N.B. I have S-Off (but not full radio), an overclocking module loaded and clockwork recovery.
My phone has been working absolutely fine the last few days overclocked to 1.3. Today I downloaded megajump (a game) and played it for a bit before the screen went blank, so I did a battery pull reset. Since then I have been unable to boot fully, it makes the HTC sound and gets stuck at the HTC screen.
Occasionally when I reboot it it starts up clockwork recovery but I'm not sure what to do with this and how to initiate this recovery stage to start with.
I know the answers to this problem are in the forum somewhere but I'm struggling to find where to start. It seems an odd issue as it has been working fine (including switching on and off etc).
N.B. Shortly before this problem I updated ROM manager from the market
Thanks in advance
gloscherrybomb said:
N.B. I have S-Off (but not full radio), an overclocking module loaded and clockwork recovery.
My phone has been working absolutely fine the last few days overclocked to 1.3. Today I downloaded megajump (a game) and played it for a bit before the screen went blank, so I did a battery pull reset. Since then I have been unable to boot fully, it makes the HTC sound and gets stuck at the HTC screen.
Occasionally when I reboot it it starts up clockwork recovery but I'm not sure what to do with this and how to initiate this recovery stage to start with.
I know the answers to this problem are in the forum somewhere but I'm struggling to find where to start. It seems an odd issue as it has been working fine (including switching on and off etc).
N.B. Shortly before this problem I updated ROM manager from the market
Thanks in advance
Click to expand...
Click to collapse
Hook your phone up to the comp with it powered off, type in "adb logcat" into your computer's Terminal, and display the results.
gloscherrybomb said:
N.B. I have S-Off (but not full radio), an overclocking module loaded and clockwork recovery.
My phone has been working absolutely fine the last few days overclocked to 1.3. Today I downloaded megajump (a game) and played it for a bit before the screen went blank, so I did a battery pull reset. Since then I have been unable to boot fully, it makes the HTC sound and gets stuck at the HTC screen.
Occasionally when I reboot it it starts up clockwork recovery but I'm not sure what to do with this and how to initiate this recovery stage to start with.
I know the answers to this problem are in the forum somewhere but I'm struggling to find where to start. It seems an odd issue as it has been working fine (including switching on and off etc).
N.B. Shortly before this problem I updated ROM manager from the market
Thanks in advance
Click to expand...
Click to collapse
Ok so once it boots into Clockwork recovery you have a couple of options, first did you ever make a back up of any of your roms? If yes , scroll down to backup and restore and select it, next choose Restore, It will give you a list of any roms you have backup before, choose one and it will restore to one of those backup roms, option two if you have a complete rom zip file on your sd card you can choose install zip from SD card, choose zip from SD card, apply and your good, if you dont have a rom zip on your SDcard you can put one there by selecting mounts and storage in Clockwork recovery, Mount USB storage, and put a rom on the root of you SDcard, then go back and run my option two that I just gave you, If for some reason you cant mount the sdcard, shut the phone down, remove the sdcard, use a card reader to install a zip to the root of the sdcard and then follow option two.
Remember before you flash anything wipe data/ and cache.
Panic over, having reset it numerous times and left it for well over 30 mins, it has now managed to load up properly.
Very strange!
Mods feel free to delete this topic if you like...
I perma-rooted my T-Mobile G2, but now I'm lost.
Since I can't flash official ROMs, what can I do to update OS? Are there any options besides CM7? If I switch to CM7, does it mean I lose all my previous installations? And does it mean I'm stuck with CM forever? When do you expect official version of CM7 to be released?
Thank you in advance.
You can flash any ROM you want. There are many good solid ones in the Development forum here and other android forums of course.
If you're looking to back up your apps before you install a ROM (because you must wipe all data when installing new ROMs) I'd advise you download an app called Titanium Backup. I use it regularly when switching ROMs and it really is necessary. This can back up all apps, app data, and even system data if you want. You can then restore after flashing your new ROM.
CM7 is at RC-1 (Release Candidate) which means that it has been declared stable enough with few enough bugs for the general public. I've personally been running nightlies for a few weeks now with no issues, and the RC-1 seems to be similar. There really is no date for when it will become an official release, but if you're up for waiting that's totally understandable.
If you don't wanna go with the CM7 RC route, you can always go to one of the other Sense-based ROMs, or even CM6 which has been extremely stable for a long time now. You can always just check out one of the stock 2.2 roms as well, they're often optimized with no bloatware and often run quicker than the stock ROM with perm root you have now.
Changing ROMs is easy, and just because you decide one doesn't mean you can't switch to another. Just use the app "ROM manager" to backup, wipe, and install different ROMs as you see fit.
Basically which ROM you choose is up to you. Just look through the dev forum and check out the offerings, read then ask questions and try them out. I definitely recommend reading some of the stickies about backing up/flashing/etc. before you get going.
Kinda hard for me to give more info because it seems like you're pretty new. I'd just advise that you read up on everything and always do backups before you flash any ROM or update in order to restore if you run into issues.
tulgaa said:
I perma-rooted my T-Mobile G2, but now I'm lost.
Since I can't flash official ROMs, what can I do to update OS? Are there any options besides CM7? If I switch to CM7, does it mean I lose all my previous installations? And does it mean I'm stuck with CM forever? When do you expect official version of CM7 to be released?
Thank you in advance.
Click to expand...
Click to collapse
1. Download and install ROM Manager and within ROM Manager flash ClockworkMod Recovery. This will allow you to create and restore complete backups of your phone. This should be the first thing you do. Second, create a backup (a Nandroid). It will be almost impossible to screw things up permanently with ClockworkMod Recovery installed and a backup on your sd card.
2. After you have a backup created, you can start trying different ROMs and if you don't like it, just try another one or restore your backup. You can even have multiple backups of different ROMs and switch back and forth if you want.
3. You are going to see a lot of references to gapps, which is short for Google Apps. Many ROMs come pre-loaded with gapps - Cyanogen was stopped by Google from incorporating them into his ROM's so the package is made available to flash immediately after you flash a CM ROM. Once you log in to Google with your account (use the same one every time) all your market apps will start downloading from the market automatically - that is all the apps that you had actively installed before you switched ROMs. Your phone will be sluggish at first while it updates all your market apps. To backup apps that you've installed from your sd card, download Titanium backup.
4. Now that you're rooted you aren't stuck with anything. Your options are wide open. Just look over the XDA site. It'll be obvious how much you can do with your phone now.
I'm on CM7 now and its very stable. Download build #41 - 42 should be out by the morning. If you decide to go with that, you won't believe how much more your phone has to offer than the stock ROM. I don't believe you'll ever want to go back to stock again, but if you do there's information here in the forums to do that including unrooting your phone.
I agree with this, read about the different roms in the G2 Development Section especially.
It's a bit confusing with all the roms, but as long as you backup your rooted setup now, you should be free and fine to try several different ones. (See step 1 about by EdKeys).
I recommend purchasing Titanium Backup...it will allow you to reinstall all your apps relatively quickly and keep all saves/settings.
Try out a sense rom (for example Virtuous) as well as CM7. I tried out sense before, but it makes the phone feel slow despite being very cool. When I first rooted my G2 I went straight for Cyanogenmod 6.1.1, as it was the stable version. Cyanogenmod 7 RC1 is way better.
Good luck and I hope you find something you like!
I highly recommend Virtuous.
Also, this isn't stated anywhere normally, so I'll share with you: I absolutely suggest using ROM Manager for most everything - it's a GUI for Clockworkmod, basically, and makes things a bit easier.
HOWEVER
The only ROMs you'll find in ROM Manager are ones that the developer has submitted. Not all devs care that much, so you'll find a TON more ROMs to try in the Development subforum. To flash one of those, simply download the .zip file of the ROM to your memory card (it doesn't matter where, you could put it on the root or you could create a 'romstotry' folder if you wanted).
Once you have the zip file on your memory card, open ROM Manager, choose 'Install Zip from SDcard' and show ROM Manager which zip file you want to use. IT'll then pop up and ask if you want to wipe, and if you want to backup your current ROM.
If you're switching between two different ROMs, you *always* want to wipe. Always. If you're simply installing a new version of the ROM you currently have installed, you don't *need* to wipe (unless the dev specifically says that you need to, so read the changelogs), but it's a good idea to do so anyways. You'll have a bit more setup to do, but wiping will prevent most problems that people seem to have.
hope that helps.
Thank you very much all. I installed CM 7 RC1 and it works great. I will try other ROMs when I get familiar with CM.
tulgaa said:
I perma-rooted my T-Mobile G2, but now I'm lost.
Since I can't flash official ROMs, what can I do to update OS? Are there any options besides CM7? If I switch to CM7, does it mean I lose all my previous installations? And does it mean I'm stuck with CM forever? When do you expect official version of CM7 to be released?
Thank you in advance.
Click to expand...
Click to collapse
Hi - the first thing I did after perma-root was change the boot animation for my G2 - you can do it by hand, or you can use an application located in market - just search for 'boot animation.'
After that's it's straight to the custom ROMs - I'm using Sense Virtuous 1.0.0 and loving it.
Hope someone might be able to help.
Just got my vega and first thought was to root, backup rom and flash. Im used to doing iit with my desire so thought it would be easy!
so i,m using Visionary to root, first temp then perm. Run titamium backup that should root and backed up a couple of apps no problem. Installed rom back up v3. Back starts by reboot and then sits at android out of the box before i have to switch it off after 10 mins or so. I i still try and flash after this (or before if i miss this stage) with new rom, cant open apps or force close and wifi just says error.
Great device though
Thanks
bRim
Which rom are you trying to flash?
I use the built in applications backup, located in settings/software tool to backup apps, with no problems.
Ive tried the r8 version and one other and ive also used the app backup but wanted to get the whole rom done before a full flash.
Hey guys, I just wanted to share my experience so far. I can't post on the MIUI page because I don't have enough posts, so I'll share here for anyone interested.
For anyone wanting to try MIUI for the DX, here's my experience, some tips, and suggestions.
-Beware, installing or trying to install ANY ROM may brick your phone. although it's very rare and unlikely to be unable to find a solution to problems, it can and has happened. so take caution and read instructions and so-forth carefully.
Some history of my DX. I soft-bricked my phone back in the early months of the DX trying to deodex it to install themes. It was stuck on M logo for 2 days before i learned enough from scratch to find out what an SBF was, where to find it, and how to flash my phone back to stock. Ever since then these nice folk on XDA-developers forums and other droid forums have helped me successfully mod my phone many times, through Q&A, detailed instructions, and a little luck.
I've rooted my phone using the command method, Z4Root, and several other processes. Some were hard to figure out, some soft-bricked my phone, most were easy as pie. I'm on a Z4Root atm.
The first successful ROM I installed was GUMMY-JAR. I liked it, it was good to me. nothing like the comprehensive ROMs out now though.
Then I jumped to Liberty 1.5, Liberty x.x etc... Liberty was awesome, but was still basically Froyo with advanced options. I loved it.
Now, just today, I've installed MIUI. And let me tell you, its amazing!
For anyone running Froyo Liberty ROMs, I believe that you can install MIUI right over the top. I didn't think it was going to work, as I hadn't seen anyone mention if it did or not over the top of Liberty 1.5.
If you want to install MIUI, go here. http://forum.xda-developers.com/showthread.php?t=1181486
You MUST be rooted, and be running FROYO, NOT GB! You must also have the Droid X bootstrapper.
I won't give instructions, as I'm not qualified to do so. But I can tell you what I did from Liberty 1.5. MAKE SURE TO MAKE A BACKUP FIRST! 1) I downloaded the MIUI ROM from the above XDA post to my SD card on my phone. 2) I clicked 'bootstrap recovery' on the DX bootstrapper app, then 'reboot recovery.' My phone booted into clockwork recovery mode. 3) wiped data/factory reset. 4) cleared cache. 5) install from SD Card. 6) install MIUI.zip i downloaded from the link i posted above. let it run it's course. rebooted. DONE.
It's really that easy if you are running the DX stock Froyo kernal.
Keep in mind with MIUI, it does NOT auto-sync your Google account. you need to go into the options>>accounts/sync and add your Google account. You can then re-install apps from your backup or just re-download them. Make sure you've synced your contacts with your Google account so they will be there when you add your Google account.
Some thoughts on MIUI...
There is NO STOCK APP DRAWER. I recommend ADW launcher or Launcher PRO. The MIUI launcher inst bad, but it's like iOS in that there's no app drawer. It's just a bunch of screens with all your app icons like an iPhone.
You can download theme's and customize themes through settings>>personal>>theme manager. MIUI allows you to change fonts, boot animation, boot audio, lock-screen style, status bar, icons, launcher, wallpapers, text style, dialer style etc. There's tons of pre-made packages, but you can also change them all individually and create one you like best. You can do all of this directly from the settings menu including looking up new themes, downloading them, and applying them.
MIUI is running on 2.3.4 GB. So it wont say 2.2 anymore after you install. (I believe the kernal is still Froyo though? Please correct me if I am wrong)
I really hope this helps some of you newbies. I am thankful for all of you that have made posts like this that I have found useful in the past.
Note- some people are having issues installing MIUI. They are getting bootlooped on the M logo for some reason. I have no idea why this is, it worked perfectly for me first try. Just remember to follow the instructions on the ROM page, and that you are running the correct version of Android. You shouldn't get a boot-loop if you do so.
Hope this helps!
i have a question.... and this question is what will decide if i keep this or go back to liberty gingerbread....
how the hell do i flash anything.. i can't even install clockwork mod without getting bootloops.... and i'd love to flash certain apps onto this.... but if this can not be done i will have to go back.... the only thing going into recovery does is use the retarded original recovery... and that is a big deal.. if i ruin my phone on the go and need to pullup a backup i can not do this with this rom and i will end up phoneless until i can get to a computer to sbf
nosboost300 said:
i have a question.... and this question is what will decide if i keep this or go back to liberty gingerbread....
how the hell do i flash anything.. i can't even install clockwork mod without getting bootloops.... and i'd love to flash certain apps onto this.... but if this can not be done i will have to go back.... the only thing going into recovery does is use the retarded original recovery... and that is a big deal.. if i ruin my phone on the go and need to pullup a backup i can not do this with this rom and i will end up phoneless until i can get to a computer to sbf
Click to expand...
Click to collapse
What exactly are you asking? "Flashing" is the process of basically overwriting your current Android OS with an Android OS SBF. If you are trying to install MIUI, you cannot do it with Gingerbread installed on your phone. "You MUST be on CyanogenMod 7 or .340 Froyo to flash this rom!" (MIUI)
If you want to install MIUI, i think the best bet would be SBF flashing to stock DX 2.2 .340 FROYO, re-rooting, then using the DX boot-strapper to boot into recovery. Then installing the MIUI .zip from SDcard in the recovery menu. Everything should work fine after that. Rmember you CANNOT go into recovery using DX boot-strapper once this ROM is installed. you CAN go into recovery with this ROM using ROM-manager. This is what I have experienced so far, and what others have said also.
no.. i already have the rom installed... i just want to be able to go into recovery without needing to be booted up.
i'm trying to install some zips through clockwork such as the old blur camera and a few other things... i will install rom manager and see how it goes from there... i love the UI of this rom but as far as being comfortable and stable.. liberty gingerbread has my vote as of now
i've cleared my cache and data several times and i get force closes alot. and this is a clean install coming straight after an SBF.
with liberty gingerbread i had the ability to set it so every phone reboot, even if a battery pull, would boot directly into clockwork mod.. making it easy for me in case i installed a zip that would get me into bootloop
Hmm, sorry mate, I dunno what to tell ya. Try looking aroudn forums or startign a new thread. someone more knowledgable than you or me will help you out.
thanks for everything though!! this really is a beautiful rom and i'd love to stick with it... i'll bite the bullet for the meantime and post around to get some help... i'd love to post in the developer section but i don't have enough posts yet.. haha
nosboost300 said:
no.. i already have the rom installed... i just want to be able to go into recovery without needing to be booted up.
i'm trying to install some zips through clockwork such as the old blur camera and a few other things... i will install rom manager and see how it goes from there... i love the UI of this rom but as far as being comfortable and stable.. liberty gingerbread has my vote as of now
i've cleared my cache and data several times and i get force closes alot. and this is a clean install coming straight after an SBF.
with liberty gingerbread i had the ability to set it so every phone reboot, even if a battery pull, would boot directly into clockwork mod.. making it easy for me in case i installed a zip that would get me into bootloop
Click to expand...
Click to collapse
You need to install Rom Manager, and select flash Clockwork Recovery. Make sure you select Droid X (2nd Init). Then you can reboot into recovery with Rom Manager :-D
laxattack said:
You need to install Rom Manager, and select flash Clockwork Recovery. Make sure you select Droid X (2nd Init). Then you can reboot into recovery with Rom Manager :-D
Click to expand...
Click to collapse
but the problem is that i would like to be able to go into recovery without having to do it through an app... i'd like to make it so every reboot (including battery pull) makes it boot into recovery. thats how i had liberty gingerbread doing it... if not.. i can live with it.. i'll just be a little more careful on what i'm installing
Just wanted to chime in about MIUI rom, I just flashed it yesterday and am ABSOLUTELY loving it thus far. I had no trouble at all installing the rom what-so-ever. I used ROM Manager to do the whole thing: downloaded newest ver. of MIUI, backup current ROM, wipe data and dalvik. Let it run its course and it rebooted and was up and running in no time flat!