Related
I rooted my Hero a long time ago and installed Cyanogen's Recovery Image 1.4 on at the same time.
Over the last couple of days I've finally got hacked off waiting for an official 2.1 ROM to be released and decided to have a play with some of the Custom ROMs. The problem I've run into is that all of the guides talk about erasing data from different directories and partitions but none of them discuss how to do it !?
All I really need to know is if this is something that must be done via adb and what/where the directories are that need to cleared out.
I have searched and trawled but I get the feeling that this step is something that is done antomagically by the newer Recovery Images. If that's the case, would you suggest I upgrade mine ? And to what ?
Thanks for the help
(Really looking forward to playing with VillainROM 6 )
Yep,... Id 1st updrage your recovery to AmonRa 1.6.2.
Use BTDAG's guide in my signature to find out how to install it or I think there are ADB instructions for the installation in the Amon Ra thread.
Once that is done, before you flash a new ROM, turn of your phone, you go into your recovery by holding "HOME" and "POWER" buttons, then go into wipe, then select all of them one by one,....
[Recovery ROM] [07-Mar-2010] RA-hero-v1.6.2
Thanks ddotpatel, I guessed it might be due to the age of the Recovery Image I've got
I'll upgrade this evening
ddotpatel said:
Yep,... Id 1st updrage your recovery to AmonRa 1.6.2.
Use BTDAG's guide in my signature to find out how to install it or I think there are ADB instructions for the installation in the Amon Ra thread.
Once that is done, before you flash a new ROM, turn of your phone, you go into your recovery by holding "HOME" and "POWER" buttons, then go into wipe, then select all of them one by one,....
Click to expand...
Click to collapse
Any idea exactly what stats are erased by the battery stats & rotation settings options?
No idea pal,... but if Im flashing a new ROM without having 100% battery I leave the battery settings wipe.
I assumed that wiping battery stuff makes your phone think your battery is full after the wipe,...
So say its actually at 50%, then you wipe stats and flash a new ROM, then your phone thinks that battery is at 100% so will only charge upto that level.
The only thing I'm basing this on is I have read people say that when flashing a ROM when battery is not 100% they seem to lose battery capacity. But who knows, it could be psychological?
AFAIK battery stats deletes stuff like which programs have been using your battery as well as the currently stored battery figure. I assume that on next boot it checks the battery capacity afresh and goes with that figure.
Rotate one - i assume is to do with application rotation and the g-sensor.
I always wipe this data because it can't hurt - worst case it has to work it out again and it takes an extra 10 secs or so on startup.
Lithium Ion batteries don't have the "memory" problem of older batteries where they forget any charge that is left in the battery when it is put on charge and assume when its removed from charge that it is 100%. They should always stay the same capacity for their entire life duration. Again this is all AFAIK
Aahaaa,...
I always take what you say as gospel BTDAG.
Might have a read up on batteries later,... If I remember,... If I can be arsed!
Do you ever flash ROMs without having 100%?... No problems?
btdag said:
I always wipe this data because it can't hurt - worst case it has to work it out again and it takes an extra 10 secs or so on startup.
[snip]
Again this is all AFAIK
Click to expand...
Click to collapse
I took the same cautious view as ddotpatel. I figured if it's important enough to store in it's own private flash, it's probably holding data related in some way to the physical state of the phone, or an estimate thereof. I'm wary to touch them without ever having seen any solid info on what's there.
I've noticed one or two new ROM threads where the user is told to wipe these stats. I hope no one gets burned as a result.
BTW Also all afaik. It's just that in my case that isn't very far.
I was hesitant for a long time to root my phone and use custom ROMs because of the fact that the MyTouch 3G had a perfected SPL so it was more complicated to do and I didn't want to brick my phone. I read a lot on Wiki and various forums and decided to experiment. I got my phone rooted with a custom ROM with very little effort or time and I love it! Here's the way I pieced this together for my MyTouch 3G LE Fender (should work and HTC Magic, MyTouch 3G 1.2, and maybe the original MyTouch 3G).
First, as it has been mentioned in other threads, download and install Universal Androot. This does give you root access when inside the OS but from what I've seen it DOES NOT give you true root access before the OS loads. That's ok though.
With my newly founded root access I got ROM Manager and Titanium Backup premium from the market. I opened Titanium Backup and ran a batch to backup all user apps and system info and saved it on my SD card. I then downloaded the latest stable CyanogenMod ROM, the tiny Google Apps package, and RA Recovery v1.7.0G (optional) and saved them to the root of my SD card. Now the fun began!
I opened ROM Manager and chose "Flash ClockworkMod Recovery". The phone rebooted and flashed the new recovery image. I got back into ROM Manager and chose "Install ROM from SD Card" and pointed it to the CyanogenMod ROM. Again, it rebooted and installed the ROM. The first time you see your phone's splash screen and the new Cyanogen splash screen is a little unnerving because they are there for a long time. It only happens the first boot after installing a new ROM.
Now I was running CyanogenMod 6 (you can probably use whatever ROM you want). If I remember correctly this version has ROM Manager cooked into it. I went back to ROM manager and told it to flash the ClockworkMod Recovery image again and it rebooted and did so. I went back into ROM manager when my phone was done booting and chose to "Install ROM from SD Card" again but this time pointed at the tiny Google Apps package. When my phone rebooted I now had the new ROM & the Google Apps.
From here I reinstalled Titanium Backup, opened it, and chose to restore user apps and system data. When it was finished all of my apps and quite a bit of my cookies and settings were all back into place. I didn't have to go through the tedious process of reinstalling apps or re-entering password on websites. Very nice!
Now for some personal preference. After I got the setup of my homes screens, etc finished I went back into ROM Manager and chose to flash the RA Recovery v1.7.0G. Just a personal perference. The ClockworkMod Recovery worked very well so this is optional.
Another preference was that I got LauncherPro Plus. This ROM has ADW Launcher cooked in but to me LauncherPro Plus makes it look like Froyo more (because at this point I was running Froyo with a different launcher since the stock isn't in this ROM) and LP seems to be a good bit faster than ADW. Again, personal preference.
Just a few suggestions. Froyo seems to have a smaller footprint on your internal memory than Donut but seems to push the CPU more. I played with some apps and now my phone is insanely fast! I used Set CPU to overclock, Autostarts to limit the apps that launch themselves, AutoKiller Memory Optimizer to help keep RAM available, Advanced Task Manager to dump RAM when I need to, and CacheMate to dump cache periodically. I know that sounds like a lot but my phone has never been this fast before. Very nice!
1 last thing. My battery life sucked afterwards. I thought it might be the battery stats so I ran phone to 0% battery and let it shut off. Then I charged it up to 100% and left it on the charger for a few more hours. I did the same thing again. After 2 full battery cycles my battery is lasting 24-30 hours with moderate use (checking FB a few times a day, about 50 text messages a day, checking TapaTalk several times a day, and a few random tasks here and there). It just needed to be recalibrated.
I hope this is helpful to someone. It was really easy to do.
This may "wreak of non-search" and I am sorry if it does. While I have searched, the overall panic that one experiences when you suspect a brick and cannot afford to have a brick.... (that, plus a friend purchased this Glacier for me to help me get back on my feet with respect to career/employment, etc., so a good amount of guilt is thrown into this mix)... all prevents me from rationally and methodically searching thread after thread to figure out why I am having the problem I am having.
I will be as precise as possible.
1. Back in Feb., I perm rooted with visionary... then about 2 weeks later, I read that this root was not true radio s=off perm root, so I used adb and the scripts to perm root again--using the wiki as a guide. Saved a copy of the partition 7 bin on my laptop as an added precaution. Also, BTW, I never flashed the engineering HBOOT. It didn't seem essential to do so... PLUS, in almost every guide it warned that this was the most likely chance for one to f*ck up and brick, so in the interest of erring on the side of caution, I skipped that.
2. I kept stock ROM for several weeks after that... just enjoying root and freezing bloatware with Ti, and doing other root-enabled mods... nothing too involved.
3. About 1 week ago, I finally decided to flash my ROM. I had Rom Manager (paid version), and had flashed ClockworkMod Recovery 3.0.0.5. Further, as an FYI, I had/have numerous nandroid backups on the SD, plus several Ti backups of apps/data... even sync'd this with dropbox, so I can access those now (which are not of any help obviously).
4. I first flashed a CM7 nightly build--wiped data and cache, and as far as I know followed the guides precisely. All was well...new ROM worked alright... some bugs, but it was nice to have the new features, etc.. And of course the mental gratification of having 2.3.3 (GB) instead of 2.2.1 (boring old froyo). I updated the nightly maybe 2 times... in each case, I simply flashed without backing up those ROMS or wiping data/cache as they didn't seem necessary, plus I still had all my stock rom nandroid backups on the SD.
5. Then Last night, RC4 came out. I flashed this the same way... no wipe. This morning... after using it for awhile, I started to get forced close problems on numerous apps... and the one that was most bothersome was my Market app... So after trying to Fix Permissions using RM to no avail.... I decided to restore the last nandroid backup of my stock (rooted) ROM. All seemed well while the restore was progressing... I was powered by AC (as always). But when the phone rebooted at the end of the restore, it stayed at the MyTouch splash for a long time... longer than I thought was appropriate (~20 minutes). So, I took out the battery since nothing else responded, and tried to boot into recovery. WHen I tried this, I got 3 quick vibrate alerts, and a blank screen, with the LED flashing every second in an ominous disconcerting way. (!!) Again, I removed battery, then tried to start phone again normally. Same problem.... It won't go past the MyTouch splash.
Since I cannot get into the phone... I am of course panicked... I have ADB on my laptop if needed, but I really am at a loss as to why this happened, and what I can do at this point....
Please, please advise. My utmost appreciation and sincerest gratitude in advance for any assistance.
Thank you!!!
syntropic
syntropic said:
5. Then Last night, RC4 came out. I flashed this the same way... no wipe. This morning... after using it for awhile, I started to get forced close problems on numerous apps... and the one that was most bothersome was my Market app... So after trying to Fix Permissions using RM to no avail.... I decided to restore the last nandroid backup of my stock (rooted) ROM. All seemed well while the restore was progressing... I was powered by AC (as always). But when the phone rebooted at the end of the restore, it stayed at the MyTouch splash for a long time... longer than I thought was appropriate (~20 minutes). So, I took out the battery since nothing else responded, and tried to boot into recovery. WHen I tried this, I got 3 quick vibrate alerts, and a blank screen, with the LED flashing every second in an ominous disconcerting way. (!!) Again, I removed battery, then tried to start phone again normally. Same problem.... It won't go past the MyTouch splash.
Click to expand...
Click to collapse
Can you boot in to the bootloader?pull the battery put it in then hold the power button down and the volume rocker down?
should come up to a white screen.
take the battery out and let the phone sit a little bit. this has worked for others to get into hboot then recovery. Also if you get it going INSTALL THE ENG HBOOT! Can really help you with soft brick among other things.
Sent from my HTC Glacier using XDA App
Can you boot in to the bootloader?pull the battery put it in then hold the power button down and the volume rocker down?
Click to expand...
Click to collapse
No... that is what I meant when I said tried to "boot into recovery". And I got the 3 vibrate alerts and a blank screen, and nothing........
take the battery out and let the phone sit a little bit. this has worked for others to get into hboot then recovery. Also if you get it going INSTALL THE ENG HBOOT! Can really help you with soft brick among other things.
Click to expand...
Click to collapse
Will do... Thank you. DO you have any idea of where I f*cked up here??
Could be a number of things. Like wipe didn't go through completely , bad download, or just random crap out like a few others. Even flashing with the wrong cwr version can less to your issues. Lol like I said could be a number of things. Sorry I couldn't be more helpful.
Sent from my HTC Glacier using XDA App
OK... Good news. I am in now in CWR. BTW, this may have been something that was my mistake to begin with. When I originally tried to boot into Bootloader, I held the volume button UP. I just tried both up and down volume hold while powering on. When I hold volume up, I get 3 vibrate alerts and nothing. When I hold volume down, I go straight into the bootloader/HBOOT.
OK.. So as said, I am now in CWR. What is the best course of action here...?? Can I try to restore my nandroid backup (maybe a different one) of my old rooted stock ROM? Should I do a factory reset (prefer not to, but I submit to the advice of my more skilled android fans)?
Just a point in the right direction, and I think we can put this thread to bed. Thanks a million just for holding my hand while I fixed this....
I would wipe EVERYTHING but the sd card where your backup is, then attemp restoring whatever rom you had last. 2.2 and 2.3 use different versions of clock work and don't remember which 3.0.0.5 went with. So use that last one that booted and then updat clock work to 3.0.0.6 as it will flash both 2.2 and 2.3
Sent from my HTC Glacier using XDA App
syntropic said:
OK... Good news. I am in now in CWR. BTW, this may have been something that was my mistake to begin with. When I originally tried to boot into Bootloader, I held the volume button UP. I just tried both up and down volume hold while powering on. When I hold volume up, I get 3 vibrate alerts and nothing. When I hold volume down, I go straight into the bootloader/HBOOT.
OK.. So as said, I am now in CWR. What is the best course of action here...?? Can I try to restore my nandroid backup (maybe a different one) of my old rooted stock ROM? Should I do a factory reset (prefer not to, but I submit to the advice of my more skilled android fans)?
Just a point in the right direction, and I think we can put this thread to bed. Thanks a million just for holding my hand while I fixed this....
Click to expand...
Click to collapse
What recovery are you using? 3.0.0.5? and you're trying to flash a 2.2 ROM. Thats where the problem lies. See my post regarding this. It's in my signature, the green one.
I would wipe EVERYTHING but the sd card where your backup is, then attemp restoring whatever rom you had last. 2.2 and 2.3 use different versions of clock work and don't remember which 3.0.0.5 went with. So use that last one that booted and then updat clock work to 3.0.0.6 as it will flash both 2.2 and 2.3
Click to expand...
Click to collapse
OK... and neidlinger... I think I read that post before and didn't quite get the full understanding of it.... I grasp now that you can only restore a 2.2 with a 3.0.0.4 CWR.
EDIT: MUSTKll20... Well, you were right... This is not ROM specific. I tried Re-Flashing RC3, which previously worked fine. Now, since I have CWModRec 3.0.0.5, I need to use a 2.3 ROM.... So I thought I would start with this idea. So, I guess, I need to get whatever is corrupt deleted... So my only question thus remains: How do I wipe everything except the SD from within CWR?
And now that there seems to be a 3.0.0.6 which solves this mismatch trap, why would it not be simpler just to reflash the CM7 RC4, then update CWMod, then just see if my original force close issue is even still occurring, and if so, then I would flash/install eng. HBOOT, "Wipe Everything except SD" (btw, does CW have a selection for that? Is that factory reset? Or will a factory reset wipe my SD.... because obviously that would be bad)
I don't really now how to wipe the internal... Except if I had a terminal and used dd, but as much as I am comfortable with Linux, I still do not understand how the SD and the ROM are separated and why, and how, and what shell commands do what to each....
AND THANKS AGAIN SO MUCH YOU GUYS FOR TAKING TIME TO ANSWER MY CRISIS-INFUSED QUESTIONS!
syntropic said:
OK... and neidlinger... I think I read that post before and didn't quite get the full understanding of it.... I grasp now that you can only restore a 2.2 with a 3.0.0.4 CWR.
And now that there seems to be a 3.0.0.6 which solves this mismatch trap, why would it not be simpler just to reflash the CM7 RC4, then update CWMod, then just see if my original force close issue is even still occurring, and if so, then I would flash/install eng. HBOOT, "Wipe Everything except SD" (btw, does CW have a selection for that? Is that factory reset? Or will a factory reset wipe my SD.... because obviously that would be bad)
I don't really now how to wipe the internal... Except if I had a terminal and used dd, but as much as I am comfortable with Linux, I still do not understand how the SD and the ROM are separated and why, and how, and what shell commands do what to each....
AND THANKS AGAIN SO MUCH YOU GUYS FOR TAKING TIME TO ANSWER MY CRISIS-INFUSED QUESTIONS!
Click to expand...
Click to collapse
You can flash CM7RC4, and install 3.0.0.6. That's pretty much the only way you can fix it..
and android phone have a method of using a section of the SD card for their memory banks. I'm not really sure how it works either, but it does. You can wipe the internal w/o wiping the SDcard.
Wiping the phone from with in the recovery image will not touch the SDcard, it will only wipe the internal. You can format the SD card from the Recovery Image, but i'll leave that dog sleep so we do not it accidentally.
last little clean-up question.
Sorry to bump this... last LAST question...
Mustkll20: I realized that you were correct to suggest to wipe everything except the SD... Something is corrupt.
But I am not real sure exactly how to wipe EVERYTHING except the SD, from within CW recovery... Since that is the only mode I have available to me. Once I wipe, I will reinstall CM RC3, then update Clockworkmod Recovery to 3.0.0.6, and then try and download RC4 again using another method, and re-flashing.
I would trial and error this, but do not want to wipe the SD.
Thanks guys... seriously.
You can flash CM7RC4, and install 3.0.0.6. That's pretty much the only way you can fix it..
Click to expand...
Click to collapse
I didn't see your reply... ummm. and I do need to wipe.. Because I have tried to re-flash both RC3 and RC4, and I get what must be a "bootloop": During the CM splash, it stops and then reboots---over and over. It never did that before.... so my problem is something else...
I don't know what else there is besides the SD and the ROM, but whatever it is, I need to delete it. So should I do a factory reset???
Also, are you sure you are holding the volume down and pressing power to boot into recovery? The result you described is what happens when you hold the volume up and press power.
lowandbehold said:
Also, are you sure you are holding the volume down and pressing power to boot into recovery? The result you described is what happens when you hold the volume up and press power.
Click to expand...
Click to collapse
Yep... I know the thread is not for thrillseekers (i.e., its boring), but I mention that I discovered this phenomenon... so I really wasn't in all that bad a spot to begin with.
I still need to figure out how to fix my current problem.... all CM RCs (I can only flash 2.3 ROMs because of CW 3.0.0.5) go into what I guess is a bootloop. In other words, they do not ever boot, just crash and restart. And the RC3 ROM I used worked fine before this... so something else is causing this problem. I need to wipe everything I guess, but I just don't know how... without touching the SD card and from within Clockwork Recovery.
Ok. Go into recovery.
1. Wipe data/factory reset
2. wipe cache partition
Both of these are on the main screen.
Go to advanced
3. Wipe Davlik Cache
Go back to main screen
Go into mounts and storage
4. format boot
5. format system
Try all of that. It will not touch your sd card. After doing this flash the ROM again. Keep us updated and good luck.
lowandbehold said:
Ok. Go into recovery.
{...}
Try all of that. It will not touch your sd card. After doing this flash the ROM again. Keep us updated and good luck.
Click to expand...
Click to collapse
Thank you for the concise and thorough response!!!!!!! Id thank you, but have used up my allotment. get ya tommorow!!
And it worked! Thank you!
But.... ummm.... there is no market app. I would think the CM ROM would have this, but apparently it doesn't. I need to install Ti, etc. to restore all my apps.
Does anyone have a download link or at least a version # that is appropriate?
syntropic said:
And it worked! Thank you!
But.... ummm.... there is no market app. I would think the CM ROM would have this, but apparently it doesn't. I need to install Ti, etc. to restore all my apps.
Does anyone have a download link or at least a version # that is appropriate?
Click to expand...
Click to collapse
You can thank the Google c&d order for that. Go to cyanogenmod.com. there is a link there for the gapps zip.
Sent from my HTC Glacier using XDA App
OK... I thoght Gapps.zip was just Google Docs. Luckily, I had that on my SD card from one of my many ROM downloads. I see why they had to make it separate.
But I am installing it, and everything is great... And I learned a lot too... Which can only mean trouble.
Thanks!
there's like 20 miui roms with different names. I just want the best one.
I'm going for this: http://forum.xda-developers.com/showthread.php?t=1123922
but i also dunno about it.
any support?
xriderx66 said:
there's like 20 miui roms with different names. I just want the best one.
I'm going for this: http://forum.xda-developers.com/showthread.php?t=1123922
but i also dunno about it.
any support?
Click to expand...
Click to collapse
That's the one I flashed yesterday. Follow the install instructions posted in the lithium miui thread.
No app drawer on miui, so using launcher pro. With launcher pro, the widgets are working, which weren't for some reason on the stock launcher.
Make sure you let your phone rest the full 8 and 4 mins, I don't know why but I did, and apparently it's important.
GPS also works, but I had to play with it to get it going.
SamsungVibrant said:
That's the one I flashed yesterday. Follow the install instructions posted in the lithium miui thread.
No app drawer on miui, so using launcher pro. With launcher pro, the widgets are working, which weren't for some reason on the stock launcher.
Make sure you let your phone rest the full 8 and 4 mins, I don't know why but I did, and apparently it's important.
GPS also works, but I had to play with it to get it going.
Click to expand...
Click to collapse
but thats my actual question... which one should i download? Is one better or has any advantages than the other?!
also i need to disable voodoo lagfix right? Because I just did it...
i'm going to go ahead and flash the one i linked to, it seems to look better. Thanks for the help.
edit:
am i meant to follow THESE instructions?
cashyftw said:
Lets get this out of the way first. I am not responsible if you screw up your phone, but you are probably here because you already screwed up your phone. I have now been through this several times over the last few days. Some will say this process is overkill, but there is no denying that it always works, so please refrain from stating the obvious.
If you have installed or updated CM7/MIUI and lost your baseband, IMEI, or both, this should help you. Due to the amount of people currently having this problem, I would recommend this be stickied at least temporarily until things are straightened out, so people can find it easily.
For Windows only, I do not have a Mac.
Step 1 - Read the entire post and understand everything involved before you attempt this. This is a long ride, probably 30-40 minutes from start to end. This is not for new people, and will assume you have a certain amount of knowledge because you attempted to flash CM7/MIUI.
DO NOT SKIP OR SHORTCUT ANY STEP IN THIS PROCESS, UNLESS I SPECIFICALLY STATED YOU MET THE CRITERIA TO DO SO. DO NOT EVEN THINK ABOUT TRYING THIS UNLESS YOU CAN REACH DOWNLOAD MODE AND RECOVERY USING BUTTONS WITH THE PHONE OFF!
Step 2 - Gather what you need...
1 - The AIO Vibrant Toolbox : http://forum.xda-developers.com/showthread.php?t=954509
Install according to directions in the post. Donate to this guy. He spent alot of time making this easy for you to do.
2 - The old CM7 install files : http://www.mediafire.com/?gn4qoonoe3cjyp6
Unzip to a location that is easy to get to.
3 - The new version of CM7/MIUI you want to install, from the thread of your choice. Donate to the developer you are using, they spend alot of their free time making your phone better. They don't get paid for it, and they dont charge you for it.
4 - Your phone, with a full battery.
Step 3 - Odin to JFD and install Clockwork 2.x
1 - Fire up the AIO Toolbox. Do not connect your phone yet, but power it down and pull your battery. See that sticker under it that says IMEI? Write it down! You will be referencing it a few times throughout the process. Start Odin and select your pit and pda files, they should automatically come up if you are using the toolbox. Hold down your volume up and down buttons, and insert your USB cable, then insert your battery. You should go to download mode, and see Odin connect. Hit start and let it fly. Once it reboots, unplug your phone. Go to settings/about phone and you should have a JFD baseband. Hit status, and check your IMEI. See how it matches the one you wrote down? Yay! Move on to the next item. If it does not, you have some reading to do because you really screwed something up, and it is beyond my power to help you...
2 - Mount phone and put the following files on the root of the sd card:
vibrant-efsbackup.zip (if you already have a backup/efs folder on your sd card you do not need this)
cm7-vibrant-initial-20110224.zip
The zip file of the new CM7/MIUI rom you want to flash.
3 - Download ROM Manager and install clockwork recovery 2.x (if you already have the update.zip on your sd card, which you should, you can also skip this) and power down your phone.
4 - Boot into recovery using the 3 button method (holding volume up and down and power, releasing power when the word VIbrant appears on your screen), hit reinstall packages, you may have to hit it twice to get to clockwork recovery. Choose to install zip from sd card, and select vibrant-efsbackup.zip. Let it do its thing. Then select reboot, and when it does, check your sd card for a backup/efs folder. Got it? Good. Power down the phone. (Obviously, if you already have the efs backup completed, you could have skipped this step.)
Step 4 - Install Clockwork 3.x and Old CM7
1 - Fire up the AIO Toolbox. Do not connect your phone yet, but pull your battery. Start Odin and hit the pda button, select the file cm7-vibrant-initial-kernel.tar from the CM7 package you unzipped (Remember, in a place that is easy to find). THIS IS IMPORTANT - UNCHECK AUTO REBOOT!!! Hold down your volume up and down buttons, and insert your USB cable, then insert your battery. You should enter download mode, and see Odin connect. Hit start and let it fly. Once it is finished, pull the usb cable. With the download mode screen still on your phone, boot into recovery using the 3 button method. You should now be in clockwork recovery 3.x. Move on to the next item! If you did not get in, you can try to pull your battery, replace it and boot into recovery from there. If you still can't get there, you get to go where the people who do not properly follow instructions go... back to Step 1.
2 - In clockwork 3.x, choose factory reset, and let it do it's thing. Then go to mounts and storage, and format system, data, and cache. Choose install zip from sd card and choose cm7-vibrant-initial -20110224.zip. As it is installing, one of the last things you see should be "restoring efs". Hit reboot when finished, and boot into CM7. When it boots, make sure you toggle the lockscreen a couple times so it connects to service. Check baseband and IMEI again. Baseband should have changed, but it does not matter until we get to where we are going. IMEI still the same right? Awesome! Power down the phone, move to the next step! It's not? You my friend, get to meet all your other friends back at Step 1.
Step 5 - Installing what you really want...
1 - Boot into recovery using the 3 button combo. Do a factory reset, wipe cache partition, go to advanced and wipe Dalvik cache. Choose install zip from sd card, and pick that shiny new version of CM7/MIUI you picked out. You are almost there. Flash it! Reboot, and when it comes back up, take note of what time it is and DO NOT TOUCH THE PHONE FOR 15 MINUTES. You have no idea the amount of bugs this squashes. After that, check the baseband and IMEI, even though you already know it is right anyway. If it is not, do i have to say it again? You know where you are going...
2 - Destroy the paper you wrote your IMEI on, you would not want that info in the wrong hands...
3 - Enjoy your new rom
FAQ:
Q: I did everything you said, and it did not work!
A: You either skipped a step, or did not stop at the point I told you you were screwed.
Q: No, seriously, I did everything you said!
A: Seriously, I have done this 5 times in the past 3 days, and it worked every time.
Q: I installed CM7 nightly #9,10,or 11 with this method, and I have no sound on calls. What gives?
A: These builds have known issues with in call audio. Flash CM7.1
Q: Once I am on CM7/MIUI, do I have to do this every time or can I update normally?
A: Once you are on CM7 or MIUI with the proper IMEI and a good baseband, you should be able to update via the rom posting instructions. If you decided to switch from CM7 to MIUI or vice versa, I would go back to this process to get your initial installation.
Q: I installed CM7.1 and then tried to go to MIUI, and lost everything again, what happened?
A: There are changes betweeen CM7 to 7.1 that have made this difficult due to compatability issues, which is why I recommend doing this process again if you want to switch between the two.
Q: I thought there was an easier way to do this, why so many steps?
Read the first paragraph of the post, but I guess that is also asking too much...
Click to expand...
Click to collapse
Click to expand...
Click to collapse
xriderx66 said:
also i need to disable voodoo lagfix right? Because I just did it...
i'm going to go ahead and flash the one i linked to, it seems to look better. Thanks for the help.
Click to expand...
Click to collapse
Just install the one you linked to, the one direct from miui.us.
The other Lithium one looks like it's customized, overclock kernal, stuff like that.
I disabled vodoo lag fix. I odin back to 2.1. Then I installed stock 2.2.
Then I followed the instructions exactly. Wipe dalvic cashe, format system/data/cache, wipe factory restore, etc etc.
Not sure if I had to install 2.2 first, but I did anyway since the install instructions were for upgrading from a 2.2 rom and not a 2.1 rom.
thanks for the help. I'm on MIUI now, just gotta wait the total 12 mins for it to settle down. ;P
@xriderx66, please will you be kind enough to let me know your experience with the MIUI. i am strongly thinking of flashing same rom.
Thanks in advance.
No, that lengthy install instruction is outdated
xriderx66 said:
thanks for the help. I'm on MIUI now, just gotta wait the total 12 mins for it to settle down. ;P
Click to expand...
Click to collapse
You don't have to install via those long instructions anymore. Apparently those are outdated.
Just manually backup your /efs and keep a copy on your computer, just because everyone should have a copy of their /efs folder and nv_data.bin, otherwise if you run into trouble you can lose your IMEI.
Then follow these simple instructions as outlined by user nickmcminn60 for his Lithium MiUi rom, but it worked for the regular MiUi also:
INSTALL INSTRUCTIONS (For Lithium and SS-11 If you are on MIUI, CM-7 or a 2.2)
-Wipe Dalvik Cache
-Wipe Cache Partition
-Wipe Data/Factory Reset
-Format-System, Cache and Data (Located under "Mounts & Storage)
-Flash LE Lithium (EDIT by me samsungvibrant..OR THE STOCK VERSION OF MIUI could be flashed here)
-Fix Permissions
-Reboot and Let Settle For 8 Min
-Reboot again Let Set For 4 Min..
No need to do the longer install process you had mentioned in the prior post.
belushi7 said:
@xriderx66, please will you be kind enough to let me know your experience with the MIUI. i am strongly thinking of flashing same rom.
Thanks in advance.
Click to expand...
Click to collapse
It's a very smooth rom, it has fast animations and i love em'
The only thing bugging me right now is battery life drains way faster than what i'm used to. I'll find out more on calibrating the battery/changing kernels etc.
SamsungVibrant said:
You don't have to install via those long instructions anymore. Apparently those are outdated.
Just manually backup your /efs and keep a copy on your computer, just because everyone should have a copy of their /efs folder and nv_data.bin, otherwise if you run into trouble you can lose your IMEI.
Then follow these simple instructions as outlined by user nickmcminn60 for his Lithium MiUi rom, but it worked for the regular MiUi also:
INSTALL INSTRUCTIONS (For Lithium and SS-11 If you are on MIUI, CM-7 or a 2.2)
-Wipe Dalvik Cache
-Wipe Cache Partition
-Wipe Data/Factory Reset
-Format-System, Cache and Data (Located under "Mounts & Storage)
-Flash LE Lithium (EDIT..OR THE STOCK VERSION OF MIUI)
-Fix Permissions
-Reboot and Let Settle For 8 Min
-Reboot again Let Set For 4 Min..
No need to do the longer install process you had mentioned in the prior post.
Click to expand...
Click to collapse
Yeah, thanks, i figured that out.
Any specific kernels you're using for better battery life?
@SamsungVibrant, please how do you backup your /efs? is there a thread you can point me at so I can read it up?
how do i make my phone stop vibranting everytime i get a text message?
belushi7 said:
@SamsungVibrant, please how do you backup your /efs? is there a thread you can point me at so I can read it up?
Click to expand...
Click to collapse
With root explorer, free from market. Enable root within that app in settings. Also enable root with superuser app in tools folder. Then navigate to efs folder copy and paste it.
Sent from my GT-I9000 using XDA App
xriderx66 said:
how do i make my phone stop vibranting everytime i get a text message?
Click to expand...
Click to collapse
It is in settings, sounds.
Sent from my GT-I9000 using XDA App
I always flash MIUI still being on Voodoo and I don't notice anything.
Sent from my GT-I9000 using XDA Premium App
Is it ok to flash with gb bootloaders???
Yup but ur external SD card wont work
Sent from my GT-I9000 using XDA Premium App
From what I have seen Lithium is actually meant to be more of a development ROM for new features. The other ROM made by that developer is the SS series which is meant to be more of a daily driver (eg. more stable), and it has additional tweaks from the official MIUI release to try to achieve things like better battery life as well as a OC or UVable kernel.
SS can be found here:
http://forum.xda-developers.com/showthread.php?t=1099533
and here:
http://forums.miui.us/showthread.php?7067-ROM-SS-11.1-%281.9.30%29-**UPDATED**-10-01-11
Unrelated to the OP, but if you're using Launcher Pro you're missing out on one of the best aspects of MIUI: No App Drawer! Instead you organize your apps into folders on the Home page. It makes you wonder why there ever was an app drawer. Seems like a silly concept now that I've been using MIUI for a while.
Alanrocks15 said:
Yup but ur external SD card wont work
Sent from my GT-I9000 using XDA Premium App
Click to expand...
Click to collapse
not true anymore, can be flashed with GB bootloader.
Sent from my GT-I9000 using xda premium
Hey guys,
I know everyone is going to first think, What the hell, this is too easy what a noob.
Anyway, point is, ive been looking for a tutorial on this for ages and just can´t find one.
On all Android Roms they always just write things like "Also make sure to intall the kernel" and thats it or when you look through generall ROM tutorials for android you just see "Don´t forget to install the coresponding kernel"
Nothing on how to do it.
So I have the following questions please:
1. I want to install this ROM on my HTC HD2
http://forum.xda-developers.com/showthread.php?t=1316632
Click to expand...
Click to collapse
How do I install the kernel for it?
2. It tells me to partition the SD card, I really don´t get what they mean with all of those numbers?
Please send me to a tutorial where it is explained or explain it, it would really be a great great help. Thank you!
Well.
First thing - it depends on whether you want to flash the Magldr or cLK version.
I highly recommend cLK, with it you can use ClockworkMod Recovery, which will allow you to easily install pretty much everything that's in correct zip format.
So if you flash the cLK version, afterwards you just download the kernel (that's in the thread you provided) in the .zip format and save it on your sdcard. Then go into Clockworkmod Recovery (if you don't know what it is, search the net, and study) and flash zip from sdcard. That's it for the kernel.
If you want to use Magldr, I can't help with that, I'm using cLK.
About SD partitioning - there is a good guide here https://docs.google.com/document/d/1dhXJZPjZzBHcAtIE_jfEeuG988UDUaP7GfZk909nNCc/edit?hl=en&authkey=CLDJw80N&pli=1
It's a guide made especially for AmeriCan Android ROM, but the partitioning part is well written and it should work for all ROMs like that.
Just check it out, if you need anything more, let me know.
Thanks man.
This is great.
Did it with cLK and it was really easy.
Thanks!
Edit.
I need some help on this ROM. I tried to post this question in the ROM thread but it wont let me so im hoping someone can help me here.
My phone won´t boot anymore. It just gets stuck at the HTC logo with this ROM installed.
What I did was:
1. Wiped data and cleared cache
2. Installed kernel via CWM (from SD)
3. Installed ROM via CWM (from SD)
4. After succesful install (with out errors at least) i press reboot now.
And from then on its just suck at the HTC logo.
Ive left it for over an hour now just to be sure but nothing.
Can someone tell me what is wrong with it?
Thanks!
Cheesus182 said:
Thanks man.
This is great.
Did it with cLK and it was really easy.
Thanks!
Click to expand...
Click to collapse
No problem mate, if anything more, just ask - here or PM.
Edit:
P.S. if you wanna confirm that you have the new kernel installed, just go to settings, about phone and there you see the kernel info.
I'm going to jump this existing thread as I also have a beginners question on the same subject...
I already installed a ROM (NexusHD2) and having huge battery drain problems (drains from 100% to dead in aprox. 15 hours on 100% standby with no applications running), but having less than 10 posts on this forum, I can't ask in the thread for the particular ROM. But I see a lot running this ROM with a tytung_r14 kernel, so I figured that I probably had to install this as well and I'm going to try it, but one question though...
Was I supposed to install the kernel BEFORE installing the ROM? Or can I just go and install the kernel now and all will be dandy?
Thanks.
Just flash Rom again in Recovery mod then flash kernel later on. It's gonna be fine, I believe.
Sent from my Desire HD using xda premium
Why should I do a recovery flash of my ROM and then flash kernel afterwards instead of just flashing the kernel right now if that is possible?
The ROM was flashed friday afternoon, so it's a pretty clean ROM.
You can flash kernel at anytime, you don't have to reflash anything.
Also, it might not be the kernel, which is responsible for your battery life.
Search for thread called something like ultimate battery guide for android and there are all things you can do to check what's wrong and make your battery life great. I did that, and am very satisfied.
DaneX said:
I'm going to jump this existing thread as I also have a beginners question on the same subject...
I already installed a ROM (NexusHD2) and having huge battery drain problems (drains from 100% to dead in aprox. 15 hours on 100% standby with no applications running), but having less than 10 posts on this forum, I can't ask in the thread for the particular ROM. But I see a lot running this ROM with a tytung_r14 kernel, so I figured that I probably had to install this as well and I'm going to try it, but one question though...
Was I supposed to install the kernel BEFORE installing the ROM? Or can I just go and install the kernel now and all will be dandy?
Thanks.
Click to expand...
Click to collapse
I'm currently running the existing ROM on my SD card, and I'm not experiencing any battery drain what so ever...
I've also installed the ROM in NAND previously and didn't experience any heavy battery drain as well.
But to answer your question, no you weren't suppose to install the kernel before installing the ROM; The ROM (in SD or NAND format) already comes with a compiled kernel (It's a file called zImage).
You can install the kernel and you should just be dandy. Just remember that your battery life is heavily influenced by your cell reception and by the synching that occurs in the background.
To give you a reference, my phone is at 89% has been on standby for 13.5 hours with WIFI ON and data ON, but with data synching turned OFF for facebook and gmail. I'm also currently running it through the SD card with kernel r13. You should get similar results with the newer or existing kernel.
g.s said:
To give you a reference, my phone is at 89% has been on standby for 13.5 hours with WIFI ON and data ON, but with data synching turned OFF for facebook and gmail. I'm also currently running it through the SD card with kernel r13. You should get similar results with the newer or existing kernel.
Click to expand...
Click to collapse
Is this with the NexusHD2 ROM?
When my phone is "sleeping" with screen/WiFi/Sync/Bluetooth OFF my phone is using 55-60 mA.
With the screen on and lowest standard brightness setting it is at 115-125 mA
DaneX said:
When my phone is "sleeping" with screen/WiFi/Sync/Bluetooth OFF my phone is using 55-60 mA.
Click to expand...
Click to collapse
That means that you have a lurking app that keeps your phome from going into standby,so called partial wake.
Go into you app Spare Parts, click on battery history, choose other usage, since last boot or unplugged.
The screen on and running percentages tell you about the wake lock.
If it is nearly the same, that means you have almost no partial wakes.
If running is much higher, than screen on, that means you have some app that keeps phone awake.
Now choose partial wake usage in Spare Parts and it'll show you the apps.
And now you either uninstall them or change settings.
I'm on AmeriCan Android rom, getting 1-4mAh consumption in standby.
DaneX said:
Is this with the NexusHD2 ROM?
When my phone is "sleeping" with screen/WiFi/Sync/Bluetooth OFF my phone is using 55-60 mA.
With the screen on and lowest standard brightness setting it is at 115-125 mA
Click to expand...
Click to collapse
Yep, this is with the NexusHD2 ROM. My phone during standby, only draws about 2-4mA.
55-60mA during sleep/standby is not normal. Are you in an area with bad cell reception?