Related
---US Cellular / CDMA Desire--- not GSM!
I'm officially sick of waiting for USCC's 2.2 update, and I'm going to hope they release a RUU sometime in the future, so I can send in for warranty if I have to.
But I'll take that chance. Getting ready for my jump, so far I understand.
1) unrEVOked is the best way to get custom recovery (CWR), root, and S-OFF.
2) From the CWR, I perform a nandroid backup of my stock USCC rom.
3) From the CWR, I perform a wipe.
4) From the CWR, I apply the Cyanogen .zip
5) From the CWR, I apply the gapps .zip
And then I'll at least have 2.2 and app2sd+
So far so good?
In the future I would like to learn cMTD, and look at Phoenix or FTRapid roms that let me resize partitions for even more space, but one thing at a time.
Bonus question : If I want to modify the Cyanogen .zip file before I apply them, to like remove ADW and add a different launcher, I simply have to change the zip and then re-sign it using the SDK, right?
Really? 50 views and no one can tell me if I'm on the right track or missing something? I don't want to mess this up, and xda I was told is the only place to trust for real good info.
I never rooted a CDMA version Desire, but your steps seems to be OK.
But you forgot something. If you want to use the a2sd+, you must create an ext partition on your SD card.
Modifying the .zip? You can remove the apks by simply deleting from the zip file and copy over the new ones (does not know if you have to modify something else).
Also you don't need to sign it, just click on Toggle signature verification in CWR and you should be fine (at least it's working for me with unsigned .zips)
yes that is pretty much it, just make sure the rom file you downloaded is compatible withcdma desire
And when using cwm there is no need to resign zips, as it should not check the signature by default. Also instead of editing the rom file, you could always just remove the apps afterwards
Yep, looks good, although I would add cmtd and vork kernel.
Edit: Here is a walkthrough for everything. CMTD instructions courtesy of TheUltimateDroid.com
You can download firerat's CMTD files on MIUI: http://miui-dev.com/forums/showthre...ns-for-MIUI-in-4-Simple-Steps!&highlight=cmtd (download the files marked a,b,c,d)
Here is the 11/29 compile of Vork kernel. It's not the newest, but I found it to be the fastest. Courtesy of Navalynt: http://www.4shared.com/file/d8v4Ztz2/vorkKernel_bravoc_1129.html
Boot into recovery (you should already be rooted with clockwordmod recovery and s-off before you get to this point)
PERFORM A NANDROID BACKUP! (Under Backup and Restore select Backup) - you should have done this earlier
Select Install zip from sdcard
Select Choose zip from sdcard and select recovery-v1.5.6-CustomMTD_S.zip
Press the physical back arrow twice to make sure you are at the main menu of the recovery
Select Advanced then Reboot Recovery
Once you are back in recovery you need to select Wipe data/factory reset
Scroll down to Mounts and Storage then select to format /boot and /system
** At this point the recovery has been patched with the cMTD and all of the partitions have been correctly formatted so you can install your ROM
Now go to choose zip from SD card, select the CM version you downloaded and install
after that's complete, select the google addon (gapps) and install
after that's complete, select vork kernel and install
after that's complete, select the boot-v1.5.6-CustomMTD_S.zip and reboot.
You should be up and running after this with about 290mb of internal storage, CM6/2.2 and everything that entails and pulling down around 1900 in quadrant (on a clean install).
Awesome, thanks so much guys! Time to break some warranty~
fyi, you need SetCPU to take full advantage of that overclock kernel.
Akilldema: Thanks for the info on cMTD and the kernel. Seems very straightforward and I think I will try that right away too.
I love it when the thousands of threads and searches come up with 5 different ways to do 1 thing grrr......
Good thing XDA has a forum community willing to help a starter.
Thanks again!
tufkal said:
Akilldema: Thanks for the info on cMTD and the kernel. Seems very straightforward and I think I will try that right away too.
I love it when the thousands of threads and searches come up with 5 different ways to do 1 thing grrr......
Good thing XDA has a forum community willing to help a starter.
Thanks again!
Click to expand...
Click to collapse
If you're planning on doing cmtd, just follow those steps above exactly, it's everything you need to get the rom/kernel/cmtd installed. It's better to do cmtd when you initially flash the rom IMO, I've had trouble applying it later.
Success! Everything suggest here worked great, and everything is fabulous!
One quick followup, I noticed that Cyanogen doesnt actually use APP2SD+, they use their own modified version of the official FroYo APP2SD, which doesnt require a ext partition. (I think? Is that right?)
I have no problem making a ext partition and going the APP2SD+ route, but....how?
Can I do APP2SD+ with Cyanogen? Is the Cyanogen mod w/ the 290mb of space I have gonna be fine?
tufkal said:
Success! Everything suggest here worked great, and everything is fabulous!
One quick followup, I noticed that Cyanogen doesnt actually use APP2SD+, they use their own modified version of the official FroYo APP2SD, which doesnt require a ext partition. (I think? Is that right?)
I have no problem making a ext partition and going the APP2SD+ route, but....how?
Can I do APP2SD+ with Cyanogen? Is the Cyanogen mod w/ the 290mb of space I have gonna be fine?
Click to expand...
Click to collapse
You are right. For me personally, 290mb and the ability to move most of the app to SD is plenty of space. I have a ton of apps (everything I see that I want) and still only have 1 or 2 moved to sd. I never did the official apps2sd, it does cause slightly more strain on the card and I never neeeded it. However, here are instructions on how to do DarkTremor's apps2sd. http://www.theultimatedroid.com/forum/index.php?/topic/333-running-low-on-space/
You have to register there to see it, but link includes all files and instructions on how to do it all. Again, for me, it was unneeded.
Hey,
So Im new to the whole rooting/custom ROM area after moving to android from iOS (Best decision ever.).
I've managed to root my HTC Desire using unrevoked, so its fully rooted. But I want to install the baadnwz InsertCoin CM7/STOCK ROM to my Desire. As my mate recommended it too me.
It's located here: (Im not allowed to post links... Just google:
Code:
baadnwz InsertCoin CM7/STOCK v45
I havent got a clue wheere to start tbh.. I would definetly prefer to keep all my apps/contacts/messages and not do a reinstall, if possible.
Thanks in advance!
Tim
1. Backup all apps&data with Titanium Backup/My Backup Root
2. Go to recovery and do a nandroid backup
3. Put ROM's zip to sdcard
4. In recovery, Wipe all userdata and wipe dalvik cache
5. Install ROM's zip
6. Boot up
7. Install app what you used to back up and restore all apps
Wow thansk for the quick reply!
I've got titanium backup, will it backup EVERYTHING? So I basically have the same phone, with a few added features of the Custom ROM?
Also, do I not need to use ROM Manager at all?
Before you flash the ROM:
From what I get it (and I just flashed successfully v45 twice), you need:
1. ext3/4 partition after your fat32 on the sdcard (can be done manually by gparted or by ClockWorkMod in the menus)
2. s-off (using alpharev's iso on a stock rom, and from what I understand, it is necessary for v45.)
3. CM7 partition table (fastboot flash hboot bravo_alphaspl-cm7.img, fastboot reboot-bootloader, fastboot erase cache. You get the image file from alpharev's site)
4. Clockworkmod 3.2 (alpharev gives you 2.5, you need to flash a new one or fakeflash it)
Only after that you flash the ROM.
-If you use free titanium backup u need to back up all apps one by one
-Yep, same phone with extra features
-No need for Rom manager
Thanks Q, forgot to mention those things
And if you don't want to flash CM7 partition sizes, just download A2SD version of insertcoin
Hey guys,
I was trying to install this INSERT COIN ROM (I had one of the previous versions) without any progress for a couple of days, untill I ran on this thread.
So I saw that I needed CWM 3...
(My issue was that I was not able to increase the internal phone storage via the ext4 partition.)
Did a search in the forum and found a link on how to flash it via ROM manager. It all went well, but downgraded my CWM version to 2.5.0.7 i think... And on the same thread a guy posted that he did a image flash from a Terminal Emulator.... Soooo... I decided to give it a try... I did everything and nothing happened...
What I thought of doing next was flashing a simple ROM before doing everything all over again. I got into bootloader (power off button and volume down) and when in go to recovery it gets stuck on the startup screen.
I'm sory if it is not the right place to ask, but I do not know what to do... Phone loads normaly, but without recovery...
And I am helpless right now...
Please, anyone advise how to proceed.
Thanks so much.
1. Is your phone rooted?
2. Is your phone s-off?
3. What do you see on the recovery stuck screen? (Is it a phone with a red triangle on it?)
The-Q said:
1. Is your phone rooted?
2. Is your phone s-off?
3. What do you see on the recovery stuck screen? (Is it a phone with a red triangle on it?)
Click to expand...
Click to collapse
The phone is both rooted and S-OFF.
I see the splash screen of AlphaRev and nothing more... Nothing happens, but when I remove the battery, insert it again and start it the phone loads. There is just no RECOVERY option.
Once you press Power+Vol Down, instead of going to recovery, go to fastboot mode, connect device to usb, and on your computer:
fastboot flash recovery image-file-of-new-recovery.img
where "image-file-of-new-recovery.img" is the image of cwm-2.5 or cwm-3.2.
Good luck, cross fingers, and no warranty provided
The-Q said:
Once you press Power+Vol Down, instead of going to recovery, go to fastboot mode, connect device to usb, and on your computer:
fastboot flash recovery image-file-of-new-recovery.img
where "image-file-of-new-recovery.img" is the image of cwm-2.5 or cwm-3.2.
Good luck, cross fingers, and no warranty provided
Click to expand...
Click to collapse
Thank you so much! It worked!
Isn't it supposed to have more than 200MB of free internal memory?
I don't know what I'm doing wrong... Tried every way...
IMHO this is one of the best guides I've seen so far for flashing a desire from start to finish:
http://forum.xda-developers.com/showthread.php?t=1016084
Lothaen said:
IMHO this is one of the best guides I've seen so far for flashing a desire from start to finish:
http://forum.xda-developers.com/showthread.php?t=1016084
Click to expand...
Click to collapse
Thanks, man. I'll give it a try & give feedback.
Summarizing the stages: (SERVED WITHOUT WARRANTY!!!)
SD Card partition table (purposed): (8GB)
7 GB FAT32
1 GB ext3/4 (without journaling!)
Then you need:
1. Root (I assume you have, use unrevoked otherwise)
2. Backup all
3. flash a stock rom
4. Use alpharev's iso to s-off
5. Rewrite partition table (internal phone partitions, not sdcard): fastboot flash hboot bravo_alphaspl-cm7.img , fastboot reboot-bootloader , fastboot erase cache
6. Wipe all
7. flash ClockWorkMod 3.2 or fakeflash it.
8. flash InsertCoin ROM itself.
9. recommend to flash a new radio (fastboot flash radio radio_image.img)
(Ofcourse, if you already done some of these, just skip)
Correct me if I missed a thing!
cypher_bg said:
Isn't it supposed to have more than 200MB of free internal memory?
I don't know what I'm doing wrong... Tried every way...
Click to expand...
Click to collapse
Depends what partition table layout you are using. I use CM7 and after flashing i have ~210MB free internal memory
4rm45 said:
Depends what partition table layout you are using. I use CM7 and after flashing i have ~210MB free internal memory
Click to expand...
Click to collapse
Okay then... Why do you need an separate 1GB ext3? On the previous INSERTCOIN I was using it was for app2sd, so I guess that this version does not support that.
And if that is the case... I fill a lot more relieved and dumber because I did everything right.
So if that is the issue, then if you get low on space? Move them to SD or there is some other trick?
Sory once again for the dumb questions.
Yes, that ext3 is for app2sd.
If you are low on space how much exactly do you have free internal memory?
Well, I have about 200MB now on a freshly flashed ROM. But i thought that it would be more, since on the previous INSERTCOIN that I had was about twice as much.
Does that mean that your InsertCoin installation is complete?
Hi all,
I was using the CM7 nightly 203, with the custom MTD partition 140 40. Just wanted to try Sunaabh ROM. Wil the old MTD partition give problems when i flash this new ROM? This ROM is 122MB in size. plz explain how to go abt in flashing this sense rom
Yes, it will. Sense ROMs need upwards of 200MB system partition. You will have to remove the Custom MTD Partitions before proceeding. (It can be removed by flashing Clockworkmod Recovery again, after wiping everything)
Thanks for the prompt reply I have not done that even once.. For this, i must go to ROM manager, Click on Flash ClockWorkMod Recovery and then press "Flash Recovery." Or if am wrong, could you pls explain me?
Not sure if this will work for you too but it did for me, I first changed the settings in the txt file then flashed a new rom and ran the bravo boot zip again.
I did that going from cm7 to sfm and it worked for me without having to flash cwm.
I think if you just change the txt file to fit your new rom then run it all again as you install, should be fine.
Sent from my HTC Wildfire using xda premium
No, that is the temporary way to do it, and it will not touch your actual Clockworkmod Recovery. I would recommend the Fastboot Method.
I have attempted to explain it here:
http://forum.xda-developers.com/showpost.php?p=17633085&postcount=93
So, first boot to Clockworkmod Recovery, Go to Mounts and Storage, then select:
- format /cache
- format /data
- format /system
This will remove all data from your phone (Except stuff on the SDCard). Then, reflash Clockworkmod Recovery from the procedure I linked above.
EDIT: Or you can follow what Scratch wrote above. Make your settings the default (ie 250 40 by changing the values on the text), then proceed. Now that I think of it, his method is way more efficient.
Works perfect. But one question. I had values 190 and 40. But titanium back up shows 262mb of which 94 is free for system and 183mb of which 113 alone is free for internal. Have I done anything wrong ?
Sent from my HTC Wildfire using xda premium
It seems to have reverted back to the Stock settings somehow... BTW, Ti Backup isn't the most reliable one to check the partitions. Use Terminal Emulator, and type su , followed by busybox df -h to get the exact values of all partitions.
As I often have problem of internal memory (not enough),
I tried to apply on my Wildfire the Custom MTD Partitions, as explained here:
http://forum.xda-developers.com/showthread.php?t=1233340
(and which seems very interesting)
But even all steps seems to do something, it doesn't have any impact on the size of the memory...
I tried to apply this size of memory: 145 10 (mtdpartmap.txt)
In order, I did this:
backup, reboot to CMW Recovery, Nandroid Backup, copy the 3 files needed on the SDCard,
format /cache, then format /data, then format /system, then perform a Wipe Data / Factory Reset, then flashed recovery zip, then Reboot Recovery, then Restore the nandroid backup
=> Remark: at the end of the retore of backup, I had an error: "Error while formatting /sd-ext!" (don't know if it's normal)
Then I flashed the boot zip, and finally reboot the Wildfire.
But when I'm checking the memory, sizes are the sames: 183 interal (including 40 for cache).
What I did wrong ?
HTC Wildfire S-Off, CM7 n215
Recovery: 4.0.0.2
S2E used
Make sure your not naming the txt mtdpartmap.txt.txt only have 1 .txt at end.
Sent from my HTC Wildfire using XDA App
Yes, as I saw that someone did it, I verified it.
I tested without any extension too (only mtdpartmap), but result was the same.
I will try again, by changing the values-number in the file...
Maybe an additional question: inthe topic is written:
"When you flash a new ROM, you WILL lose the new settings ("partially"). To overcome this, after flashing your new ROM, flash the boot-v1.5.8-Beta-CustomMTD_S attachment immediately after flashing the ROM before restarting your device."
Does it mean that I should do these operations each time I want to install the last build of cm7 ?
Yes, you have to flash the 'boot' attachment only everytime you flash a new nightly (or a new ROM, or even restore an old ROM, for that matter). If you don't, the device will not boot. (This is applicable even if you do not wipe before flashing a new nightly)
For your issue, although I can't really seem to figure out what the issue is, I would say try flashing a fresh install once just to check whether the procedure itself works or not.
If it still doesn't work after a fresh ROM install, try with the older version of the Custom MTD Script: (Although this shouldn't really be the problem)
http://db.tt/JjGxneZD
http://db.tt/C5noTQl9
this happened to me, but i realized rooted phone doesn't mean s-off, double check it has s-off?
I can solve this issue lol i think. Do this order instead
:backup, reboot to CMW Recovery, Nandroid Backup, copy the 3 files needed on the SDCard
Wipe Data / Factory Reset
Flash bravo-recovery-v1.5.8-CustomMTD.zip
format /cache, then format /data, then format /system
Reboot Recovery, then Restore the nandroid backup
BEFORE REBOOT:Flash bravo-boot-v1.5.8-CustomMTD.zip
Now should work. Well this is how i do it and works. I did the order you said the first few times
I hope this helps
Thx to all for your help.
Yes, my wildfire is S-OFF, I verified again.
About the version v1.5.8, I got it, and will install it quietly in the order you indicated below, I will inform you if it's ok by this ;-)
I just tested in this order, and I'm blocked at the end on the blank screen HTC.
But, little question: I used the files recovery-v1.5.8-Beta-CustomMTD_S.zip et boot-v1.5.8-Beta-CustomMTD_S.zip (so tagged as beta). Are they the sames files than the ones you used ?
HTC Wildfire S-Off
HBOOT 6.01.1002, CM7 n228
S2E used
Just for info:
finally I just tested again the same order, but I flashed an new build instead of to restore my last backup.
It booted correctly, and as I can see, I have now more memory available.
Many thx
Now, I have to restore my apps and data (thx titanium )
flippy12 said:
Just for info:
finally I just tested again the same order, but I flashed an new build instead of to restore my last backup.
It booted correctly, and as I can see, I have now more memory available.
Many thx
Now, I have to restore my apps and data (thx titanium )
Click to expand...
Click to collapse
Damned, I talked too quickly.
This didn't impact the memory, even I flashed MTD for 145 10, I still have the sotck format memory
Only once have I had problems loading custom mtd values,I tried for hours and figured out it was the cwm 2.5.0.7 version which was causing problems cos as soon as I tried with 3.2.0.0 it applied 1st time. Have you tried different cwm?
sent from my wilderbeast:buzz
Which cmw are u using? I used version 5.0.2.0
Sent from my HTC Wildfire using xda premium
Ah yes, interesting point...
On ROM Manager (4.7.0.5), I see that CWM is 5.0.2.0.
In recovery mode (used to backup/restore for this operation) , CWM is v4.0.0.5.
Does this version a correct one, or should I upgrade it to the 5.0.2.0 ?
flippy12 said:
Ah yes, interesting point...
On ROM Manager (4.7.0.5), I see that CWM is 5.0.2.0.
In recovery mode (used to backup/restore for this operation) , CWM is v4.0.0.5.
Does this version a correct one, or should I upgrade it to the 5.0.2.0 ?
Click to expand...
Click to collapse
In order to ignore (solve I mean) this problem of CWM version, I flashed directly the version 5.0.2.0 by the terminal: now it's ok in recovery mode too.
So, I will start again this afternoon the MTD update..
Many thx, I think this time I'm in a good way to success the update
I will give you news...
Mtd certainly works with cwm 5.0.2.0 so you shouldn't have any problems.
sent from my wilderbeast:buzz
Finally, yesterday, I started all since the beginning:
downloaded again the files, installed CM7.1.0.1, followed the described procedure for MTD, and it's ok, I have the Power of ... my wildfire
Again, thx for your help, and I don't forget to thank 3xeno for the guide
Same problem with Custom MTD Partitions
I have flash the boot and recovery files. I have made a nandroid backup i restore it. The mtd file looks like : mtd 170 22 . The rom memory is 512 /system & /cache partitions have only 192 mb. Memory for my applications is only 274 mb. In "About Phone" says i have 118/310 (free/avail).Where it's manager of application i have 245 used and 29 free.I should have 55 mb free.. bot no. Rest of my memory to 512 where it is? Should i delete the nandroid backup? Danke!
amNezic# said:
I have flash the boot and recovery files. I have made a nandroid backup i restore it. The mtd file looks like : mtd 170 22 . The rom memory is 512 /system & /cache partitions have only 192 mb. Memory for my applications is only 274 mb. In "About Phone" says i have 118/310 (free/avail).Where it's manager of application i have 245 used and 29 free.I should have 55 mb free.. bot no. Rest of my memory to 512 where it is? Should i delete the nandroid backup? Danke!
Click to expand...
Click to collapse
Its 512MB and not 512MIB/MO. Hence, the actual usable capacity is actually 483MB instead of 512MB (If I am not mistaken). (The analogy is similar to any flash drive / hard disk you buy - the actual formatted capacity is lower than the rated capacity)
Hi folks,
I'm brand new to the world of Android. Over the past couple days I've managed to go from a UK Orange branded Desire, to a fully rooted, S-Off Desire running MildWild v4.3 with the help of some of the guides on this site. But I've finally hit an impasse and could really use a bit of guidance.
Given the technical limitations of the phone I wanted a stable Rom which was relatively easy to install for a first try. But I can't find the information I'm after regarding sd-ext. I'm hoping someone could clarify or point me towards answers for the following:
I've managed to enable installing and moving to sd-ext, but for some reason certain apps e.g. gmail, mail, google play cannot be moved to sd-ext let alone uninstalled from the phone. Is this because they are core system/Android applications?
Even after setting the default install location to sd-ext, once I've installed several apps my internal memory drops from 101mb to 71mb. Is this to be expected? I've not finished installing my apps so I expect this to drop some more.
On the stock HTC rom, the browser would save a cache to the internal memory, so I opted for Opera Mobile instead. Is this still true for Mildwild? Or does the rom store data & caches to the sd card?
Ultimately, I'm shooting for my apps to reside on the sd-ext partition and making sure as much of the data/cache is there, leaving as much space free on the internal memory.
1. these are system apps, so cannot be uninstalled. keep them on system partition anyway, they run fine from there.
2. yes. app data, system app dalvik cache and app cache get stored on /data partition (internal) with this rom. space will gradually decrease the more you install.
3. yes, as above app cache gets stored on /data, including browser, thought this is probably true for most roms.
a couple of points:
1. I believe you are still on stock hboot. to maximise space, you need to change to cm7r2 hboot (easy since you are s-off). basically if you are still on stock hboot, you have a lot of system partition space free and wasted, which can be repartitioned to internal by switching hboot...i.e. you get more internal memory
i recommend to:
- nandroid backup
- change to cm7r2 hboot (recommend using fastboot, guide here)
- boot into recovery, full wipe and nandroid restore2. install an app like 'diskusage'. you'll be able to browse all your partitions to see how and where all your space is being used to help troubleshoot space issues. can do this for any rom.
Thanks for the clarification.
eddiehk6 said:
a couple of points:
1. I believe you are still on stock hboot. to maximise space, you need to change to cm7r2 hboot (easy since you are s-off). basically if you are still on stock hboot, you have a lot of system partition space free and wasted, which can be repartitioned to internal by switching hboot...i.e. you get more internal memory
i recommend to:
- nandroid backup
- change to cm7r2 hboot (recommend using fastboot, guide here)
- boot into recovery, full wipe and nandroid restore
Click to expand...
Click to collapse
Regarding the hboot, you are likely correct. As far as I know the n00b proof everything guide I've followed didn't mention anything about changing hboot. I did see mention of cm7r2 on rom download pages but didn't understand what it meant.
Having looked at the Alpharev website, if I've understood it correctly, by flashing the Hboot with cm7r2, I should have approximately 140mb more than on the stock hboot. While flashing the hboot *seems* simple enough am I able to return to my original hboot at a future date or is it lost forever, meaning I have to rely on the Alpharev hboot images?
If I'm going to wipe the device anyways for the hboot it gives me a chance to try a different rom
2. install an app like 'diskusage'. you'll be able to browse all your partitions to see how and where all your space is being used to help troubleshoot space issues. can do this for any rom.
Click to expand...
Click to collapse
I downloaded diskusage, what a lovely program!
I did notice I had a peculiar folder on my sd card titled "backup" with two backups around 250-350mb in size. I'm guessing these are my nandroid backups?
5nak3 said:
Thanks for the clarification.
Regarding the hboot, you are likely correct. As far as I know the n00b proof everything guide I've followed didn't mention anything about changing hboot. I did see mention of cm7r2 on rom download pages but didn't understand what it meant.
Having looked at the Alpharev website, if I've understood it correctly, by flashing the Hboot with cm7r2, I should have approximately 140mb more than on the stock hboot. While flashing the hboot *seems* simple enough am I able to return to my original hboot at a future date or is it lost forever, meaning I have to rely on the Alpharev hboot images?
If I'm going to wipe the device anyways for the hboot it gives me a chance to try a different rom
Click to expand...
Click to collapse
you understand exactly the differences between the hboots. you'd be surprised that people who do actually flash them have no idea what they're doing or what they are
you can easily switch between hboots, you pick it depending on the rom's system size. you can go back to stock hboot by flashing 'bravo downgrader' (some hboots like cm7r2 are write protected), followed by 'bravo stock' from alpharev.
before flashing them, check the md5sums of the hboots using a free program like md5check.
once you've set up fastboot as above, follow the commands on alpharev (just beneath the table of hboots). you'll see cm7r2 at the top of the bootloader screen if successful.
I downloaded diskusage, what a lovely program!
I did notice I had a peculiar folder on my sd card titled "backup" with two backups around 250-350mb in size. I'm guessing these are my nandroid backups?
Click to expand...
Click to collapse
nandroid backups are stored in sdcard/clockworkmod/backup
i always keep a couple on PC for safe keeping, they can also start to take up a lot of space on sd once you start to install lots of apps.
make sure you always nandroid backup before flashing a zip or different rom. when/if you restore them if something goes wrong or you don't like the changes, you restore the exact state of the phone (contacts, apps, homescreens...EVERYTHING)
Ok I must be missing a trick somewhere.
I've followed all the steps outlined on Alpharev's site:
1) Nandroid backup in recovery.
2) Verify the MD5SUM of the file you downloaded against the one in the table.
3) Flash HBOOT with your phone in fastboot mode (Back+POWER) -> 'fastboot flash hboot bravo_alphaspl.img' (change into the correct filename for the HBOOT you downloaded)
4) 'fastboot reboot-bootloader'
5) 'fastboot erase cache'
6) Boot recovery, wipe everything and restore.
Click to expand...
Click to collapse
Everything is great up till step 5. In fact my fastboot menu says "alpharev cm7 v2" which I can only assume means great success on my part.
Can someone please explain what step 6 is? Do i reboot the device? Should I power down and do "volume key+power" then wipe? In my fastboot menu there is no recovery option...
5nak3 said:
Ok I must be missing a trick somewhere.
I've followed all the steps outlined on Alpharev's site:
Everything is great up till step 5. In fact my fastboot menu says "alpharev cm7 v2" which I can only assume means great success on my part.
Can someone please explain what step 6 is? Do i reboot the device? Should I power down and do "volume key+power" then wipe? In my fastboot menu there is no recovery option...
Click to expand...
Click to collapse
Fastboot erase cache is a fastboot command.
In fastboot menu select bootloader and press power and then in bootloader select recovey and press power to enter recovery
Sent from my HTC Desire
jmcclue said:
Fastboot erase cache is a fastboot command.
In fastboot menu select bootloader and press power and then in bootloader select recovey and press power to enter recovery
Click to expand...
Click to collapse
Excellent, I was lost at that last step and this is what I needed to piece it all together. I can happily confirm everything went well. I have my rom installed and the phone is still going.
Many thanks jmcclue, and of course eddiehk6 really appreciate your help in getting my up and running.
mildwild sd-ext
5nak3 said:
Hi folks,
I'm brand new to the world of Android. Over the past couple days I've managed to go from a UK Orange branded Desire, to a fully rooted, S-Off Desire running MildWild v4.3 with the help of some of the guides on this site. But I've finally hit an impasse and could really use a bit of guidance.
Given the technical limitations of the phone I wanted a stable Rom which was relatively easy to install for a first try. But I can't find the information I'm after regarding sd-ext. I'm hoping someone could clarify or point me towards answers for the following:
I've managed to enable installing and moving to sd-ext, but for some reason certain apps e.g. gmail, mail, google play cannot be moved to sd-ext let alone uninstalled from the phone. Is this because they are core system/Android applications?
Even after setting the default install location to sd-ext, once I've installed several apps my internal memory drops from 101mb to 71mb. Is this to be expected? I've not finished installing my apps so I expect this to drop some more.
On the stock HTC rom, the browser would save a cache to the internal memory, so I opted for Opera Mobile instead. Is this still true for Mildwild? Or does the rom store data & caches to the sd card?
Ultimately, I'm shooting for my apps to reside on the sd-ext partition and making sure as much of the data/cache is there, leaving as much space free on the internal memory.
Click to expand...
Click to collapse
Hi folks,
just a quick note on this post. I just moved from Mildwild CM- 5.0 to Mildwild 4.3 (Oxygen) because the first one was giving me a delay problem on call. before the move I have made a titanium backup of all my apps+data. After the I have installed mildwild 4.3 and restored all the app+data I have something like 17Mb internal memory free whether with the MildWild 5.0 I had more than 40mb.
Could something explain that? Did I do something wrong?
thanks
stegal said:
Hi folks,
just a quick note on this post. I just moved from Mildwild CM- 5.0 to Mildwild 4.3 (Oxygen) because the first one was giving me a delay problem on call. before the move I have made a titanium backup of all my apps+data. After the I have installed mildwild 4.3 and restored all the app+data I have something like 17Mb internal memory free whether with the MildWild 5.0 I had more than 40mb.
Could something explain that? Did I do something wrong?
thanks
Click to expand...
Click to collapse
Nop, you can move them manually to sdcard. I don't think when restoring apps they will all go straight to sdcard, sometimes you need to move them manually.
You can also go to cyanogenmod settings and in the first option (I think is about allowing moving apps?) select there to move to sdcard by default.
To help you can also download S2E from the market, open it, select Apps and Private Apps and if dalvik if you still need space. Leave app data on internal, selecting only Applications to be moved. Reboot, if you're still short on space, open S2E again and select to move Dalvik as well, reboot, you should be okay now
Using cmr2 hboot also allows more space on internal, less headaches
stegal said:
Hi folks,
just a quick note on this post. I just moved from Mildwild CM- 5.0 to Mildwild 4.3 (Oxygen) because the first one was giving me a delay problem on call. before the move I have made a titanium backup of all my apps+data. After the I have installed mildwild 4.3 and restored all the app+data I have something like 17Mb internal memory free whether with the MildWild 5.0 I had more than 40mb.
Could something explain that? Did I do something wrong?
thanks
Click to expand...
Click to collapse
do not use S2E with Mildwild Oxygen: "S2E works only with CyanogenMod7 and CyanogenMod9"
you do not need to use any extra apps to move apps to sd-ext. follow the instructions in the first post of the mildwild thread.
you should be s-off with cm7r2 hboot to maximise space with this rom. (cm7r2 hboot with Mildwild CM-5.0 would also work)
read my first reply in this thread to understand where all your apps/dalvik/data are stored: i.e. use an app like 'diskusage' to check