Related
I'm having trouble installing any roms on my girlfriends desire. Installing roms seems to work fine, right up until i try to boot the phone, it just gets stuck at the HTC screen, I've pulled the battery and tried again, but nothing works. I've tried multiple roms, and with every one, the same problem.
The phone is rooted, HBOOT 0.93.0001, S-ON, Baseband 32.54.00.32U_5.14.05.17
Anyone know what's going on? It's been a while since I've played with android phones, so I'm not current with all the lingo. I'm currently a WP7 user
Thanks for the help!
I'm assuming then it would be a2sd Rom?? Your ext3 or 4 setup? ROM manager sucks for this, use gparted or minitools(I've never used this one) and preferably a card reader.
Sent from my HTC Desire
Ya, I tried ROM manager for the partition, I'll give gparted a shot. thanks!
Ok, formatted the sd card, and repartitioned to FAT32, and 512mb of EXT3 and the same thing happens, it just hangs at the HTC screen after installing a rom.
How long are you giving it before pulling the battery? It can take 10 or 15 minutes on first boot. I'm assuming you've tried a couple of different roms.
yes, I have tried a few different ones. I'd say the longest I waited was around 25-30 minutes. In my previous experience flashing hero roms, the most I had ever had to wait for those was about 5 minutes, so I assumed the 30 minutes was long enough, and decided that nothing was going to happen.
A Dustman said:
yes, I have tried a few different ones. I'd say the longest I waited was around 25-30 minutes. In my previous experience flashing hero roms, the most I had ever had to wait for those was about 5 minutes, so I assumed the 30 minutes was long enough, and decided that nothing was going to happen.
Click to expand...
Click to collapse
i'm a previous hero owner, same thing happend to me, desire is different.
on all desire roms the op will tell you what hboot is made for and then to flash the alignement zip even if your sdcard is partioned , you have to otherwise the will never bootup and then you flash the rom plus whatever updates they suggest .
i think your hboot is stock, same as mine, but you need to S-off your phone in order to flash any roms, follow this guide: http://forum.xda-developers.com/showthread.php?t=1016084
try cool sensation or what ever takes your fancy
1-download the alignement zip , the rom and the updates if there are any
2- put all of them on your sd card (mount it or use usb card adapter)
3- go to recovery and flash them in sequence, usually alignement zip first + the rom and then reboot should be about 5 to 10mn any longer you in a bootloop means something wrong.
just have a good read before flashing any rom , and follow what they say.from step 1 till the end.
you'll get there, don't worry it wont brick your phone
I was under the impression that S-Off wasn't necessary for all roms, for example insert coin cm7. I could not get my computer to successfully boot from my flashdrive to perform the s-off with alpharev, so I skipped that step
I also flashed the alignment zip, and still had the same problem.
A Dustman said:
I was under the impression that S-Off wasn't necessary for all roms, for example insert coin cm7. I could not get my computer to successfully boot from my flashdrive to perform the s-off with alpharev, so I skipped that step
I also flashed the alignment zip, and still had the same problem.
Click to expand...
Click to collapse
You don't need s-off to flash roms, I'm not and flashed many. Make sure your installing roms for the stock hboot, cm7 won't work. From what I've seen unless your having problems with your ext the alignment patches can be more trouble than good.
Sent from my HTC Desire
Thanks a lot! I found a rom that works with the stock hboot, and it worked perfectly!
What rom are you using with the stock hboot? I'm having same problem.
Also I'm assuming cm7 is cyanogenmod7, i thought it worked with the stock hboot?
Ok, so I'm having another issue now... The market is not working, I tap it, and it brings up a white loading screen for about half a second then disappears. I tried a reset, and I still have the same problem. Is there something I need to flash in order for it to work? The rom I'm on is cool sensation v6, and I didn't see anything there about anyone having market issues, so I'm not sure what the problem is.
Thanks again
EDIT: I notice that under accounts and sync, it says that sync is currently experiencing problems
EDIT EDIT: I just remembered that with my old hero, I had to first sync over 3g only, tried that, and it solved my problem.
Under Applications, find the market and try clearing the cache
A Dustman said:
I could not get my computer to successfully boot from my flashdrive to perform the s-off with alpharev, so I skipped that step
Click to expand...
Click to collapse
Did you create a bootable usb drive?
firepanda said:
What rom are you using with the stock hboot? I'm having same problem.
Also I'm assuming cm7 is cyanogenmod7, i thought it worked with the stock hboot?
Click to expand...
Click to collapse
It's a bit misleading, cm7 does not refer to cyanogenmod7 but cm7 partion table.
You will usually find 2 different versions of most popular ROMs.
1. A2sd
apps2sd, usually A2sd+. This requires the stock partion table. You do not need to be S-off to flash these ROMs
2. CM7
This refers to the CM7 partion table (custom Hboot). To repartion your nand you need to be S-off. These ROMs are data++ ROMs.
So, no you do not need to be S-off to flash custom ROMs, you do need to be S-off to resize your partion tables. More info in this thread:
This explains Data++ versus A2SD very well:
http://forum.xda-developers.com/showthread.php?p=14615477#post14615477
I am debating on flashing my hboot as the idea of 100+MBs being wasted is killing me, plus I only have 31MB's left of internal memory with tons of apps running off my SD card.
I have been looking for tutorials and there seem to be a few different ways to do it and all methods seem to not fully explain (to me at least) what to do in full detail. I am a little nervous of bricking.
Is it really worth doing? Other than more space for apps are there any real benefits? Also the loss of cache isn't too appealing to me.
Anyone on here want to vent pros and cons and if you have a link to a detailed tutorial, please let me know.
nate51 said:
I am debating on flashing my hboot as the idea of 100+MBs being wasted is killing me, plus I only have 31MB's left of internal memory with tons of apps running off my SD card.
I have been looking for tutorials and there seem to be a few different ways to do it and all methods seem to not fully explain (to me at least) what to do in full detail. I am a little nervous of bricking.
Is it really worth doing? Other than more space for apps are there any real benefits? Also the loss of cache isn't too appealing to me.
Anyone on here want to vent pros and cons and if you have a link to a detailed tutorial, please let me know.
Click to expand...
Click to collapse
Flashing an HBOOT is totally worth it
easisest way to do is
http://ichristaylor.com/how-to-flash-the-hboot-on-your-htc-desire/
i think only benefit (very huge benefit) is free space.
If you like to fiddle then having write access to system when the phone is running Android can be convenient. But repartitioning the internal storage is the big one.
You don't have to shrink the cache partition - the Bravo-Sense hboot will still give you 70MB more /data without changing /cache. But many ROMs contain work-arounds that redirect market downloads, so the reduced size of the cache partition isn't an issue. I've been using a 5MB cache for a few months now and don't notice the difference, apart from having more space. But this does depend on the ROM, so do your reading first.
Only real drawback of a small cache is that you can't flash a radio from recovery (really can't, don't even think of trying it!). However, you can use a single fastboot command to do it instead, which many reckon is the better/safer way to do it anyway.
Large Hadron said:
If you like to fiddle then having write access to system when the phone is running Android can be convenient. But repartitioning the internal storage is the big one.
You don't have to shrink the cache partition - the Bravo-Sense hboot will still give you 70MB more /data without changing /cache. But many ROMs contain work-arounds that redirect market downloads, so the reduced size of the cache partition isn't an issue. I've been using a 5MB cache for a few months now and don't notice the difference, apart from having more space. But this does depend on the ROM, so do your reading first.
Only real drawback of a small cache is that you can't flash a radio from recovery (really can't, don't even think of trying it!). However, you can use a single fastboot command to do it instead, which many reckon is the better/safer way to do it anyway.
Click to expand...
Click to collapse
Well that brings up another question, I haven't flashed my stock radio and it seems to be running fine. How often do people flash their radios anyways?
its optional, do it only if you encounter any issues after flashing a ROM (no signal, wifi etc)
however i always update my radio to the newest just cause i like to have it up to date (not that i see any diffrence in the newest and the one from official FroYo.
vashishtuday said:
Flashing an HBOOT is totally worth it
easisest way to do is
http://ichristaylor.com/how-to-flash-the-hboot-on-your-htc-desire/
Click to expand...
Click to collapse
Question about this link. All the tutorials I see *the above link to ichristalylor* and alpharev seem to start off the tutorials with security off (s-off) is this correct? Or does the software "fastboot commander" do this for you when you start?
I think that's the only confusing part about these tutorials for me is I cannot figure out if s-off needs to be in place once you start the tutorials (yes I understand this is some hand holding here) I just find the tutorials vague about this issue. But once I figure out the s-off issue the rest seems to be pretty simple to follow.
Ok so I finally manned up and took the plunge, it was nerve racking at times but surprisingly easy to do. I hope this post helps others out there as I feel there is very little details out there.
- First step is to turn on USB Debugging on your phone 'Settings > Applications > Development > USB Debugging.
- Now run a backup on your phone before anything else this will save all the settings apps and your OS.
- Next step is you need to turn S-OFF, I did this by following the instructions here for me these details worked the best and were clear step by step.
- Next I changed my splash screen (*optional) by using 'Fastboot Commander' thanks to vashishtuday for the link, it provided software links and a rough detailed outline of how to use the software but once you are in fastboot on your phone the rest is pretty self explanatory on the software. Link Here
- And the next step I took was to use 'Fastboot Commander' again to actually run the partition file I downloaded from AlphaRev I read on one forum that a person was able to save the PB99IMG.zip file to their SD and run Fastboot on their phone and it automatically did everything for them. I did not have success with that method so I used Fastboot Commander.
- Once complete I used the software to power down the phone *Now for this step I am not 100% sure if it's safe for others to do but it worked for me* my phone restarted even though I requested it to shut down. It stuck on the loading splash screen so I pulled the battery restarted into recovery and ran a recovery of my backup and after it was complete my phone was back to normal with lots more space on the internal partition.
*Note from Parva4: If you flash your hboot, do some research before flashing your radio as some of the new hboot partitions cache are too small to hold the radio flash information and you could end up bricking your phone, if you have a new hboot partition use fastboot to flash your radios.
I hope this information helps those who are looking for a more step by step detail description. I am tempted to do a full write up with with step by step details but I feel as though this information and the links provided should be good.
I'll add one thing to this. Going S-Off is an equally simple affair to rooting the phone. S-Off allows you to use different hboots with different roms (that's a story in itself).
Now, one thing you'll often see is that the 'latest' radio file is often recommended for use with most roms, certainly the HD roms. Firstly, try the rom without updating the radio, in 90% of cases your phone will be fine. More importantly, Do NOT flash the radio file from the phone via recovery if you are using custom partitions (like CM7). It's possible that you have insufficient cache space (~30Mb required) to install it and you WILL brick the phone if this fails.
There are workarounds (flash the radio file from fastboot for eg.) but it's imperitive that you do this prior to finding out the hard way! I've flashed radio files several times with no issue, fortunately I was running a stock hboot! I have ventured into CM7 hboot and stuff and was lucky not to change the radio whilst I was on it knowing what I know now!
Do your research gentlemen!
Parva4 said:
I'll add one thing to this. Going S-Off is an equally simple affair to rooting the phone. S-Off allows you to use different hboots with different roms (that's a story in itself).
Now, one thing you'll often see is that the 'latest' radio file is often recommended for use with most roms, certainly the HD roms. Firstly, try the rom without updating the radio, in 90% of cases your phone will be fine. More importantly, Do NOT flash the radio file from the phone via recovery if you are using custom partitions (like CM7). It's possible that you have insufficient cache space (~30Mb required) to install it and you WILL brick the phone if this fails.
There are workarounds (flash the radio file from fastboot for eg.) but it's imperitive that you do this prior to finding out the hard way! I've flashed radio files several times with no issue, fortunately I was running a stock hboot! I have ventured into CM7 hboot and stuff and was lucky not to change the radio whilst I was on it knowing what I know now!
Do your research gentlemen!
Click to expand...
Click to collapse
Good reminder Parva4! I edited my last post to reflect.
I rooted my Desire (SLCD; Unrevoked 3) and it seems to be ok. Non-sense ROMs (and stock rom) are working correctly - no problems. But sense ROMs hang my desire. I have to reset phone. Any ideas to fix it?
sorry for my english, I tried to write correctly
I've tried some sense ROM (2.1, 3.0, and mix), and for me too, the phone become laggy.
Actually I'm testing the gingerburst ROM (GB+sense 2.1) witch uses Data2SD to increase memory.
working perfectly - very smooth
b.andy said:
I rooted my Desire (SLCD; Unrevoked 3) and it seems to be ok. Non-sense ROMs (and stock rom) are working correctly - no problems. But sense ROMs hang my desire. I have to reset phone. Any ideas to fix it?
sorry for my english, I tried to write correctly
Click to expand...
Click to collapse
When you say it hangs your Desire do you mean on boot or when you get to the homescreen/lockscreen?
(The english is ok by the way)
It hangs when it gets lockscreen. I wait about 10 minutes. On non-sense roms (cyanogenmod, aosp) and stock rom there are no problems. But I bought desire only for sense (especially for Sense 3.0)
@black3yed
I have never used data2sd, I will try that ROM.
Make sure you download correct version of the rom and configure your sd card correctly.
Swyped from Oxygen with Transparent XDA App
Similar issue here...
I have an unbranded original AMOLED Desire on Froyo.
Unrevoked 3 and AlphaRev S-OFF went fine. Took a nandroid backup.
I thought bravo_alphaspl-sense.img was supposed to allow the use of the original stock ROM, but installing it and restoring the backup makes the phone hang at "WHY SO SERIOUS?". After restoring the original partition table and reloading the nandroid backup it now seems fine again.
Is there no way to use the patched HBOOT partition tables with the stock Froyo ROM?
Any suggestions? I tried the IRC but no-one answered, but I'm a total IRC noob so I might have been doing it wrong.
I have tried searching for this, with little luck.
Alan
amh15 said:
Similar issue here...
I have an unbranded original AMOLED Desire on Froyo.
Unrevoked 3 and AlphaRev S-OFF went fine. Took a nandroid backup.
I thought bravo_alphaspl-sense.img was supposed to allow the use of the original stock ROM, but installing it and restoring the backup makes the phone hang at "WHY SO SERIOUS?". After restoring the original partition table and reloading the nandroid backup it now seems fine again.
Is there no way to use the patched HBOOT partition tables with the stock Froyo ROM?
Any suggestions? I tried the IRC but no-one answered, but I'm a total IRC noob so I might have been doing it wrong.
I have tried searching for this, with little luck.
Alan
Click to expand...
Click to collapse
With a nandroid backup, you make a complete image of the phone's state. This includes all partitions on the phone (/data, /system, /cache) and maybe on the sd card (sd-ext).
The sense partition table and the stock partition have different partition sizes for /system and /data. Important here is the /system partition. Stock roms (or better all sense roms) use not less then around 200 mb of the /system partition. All different partition tables than the stock one have a maximal size of 180 mb /system partition.
So if you restore a backup from a stock rom using a different partition table than the stock one, you want to move 200 mb to a place that has only max 180 mb free. That's why you get stuck at the alpharev splash screen.
The exceptions of this explanation are the sense roms here, from which mostly two different versions exist: One for stock hboot, one fore cm7 hboot. But this exception is not the case here.
Conclusion: When you use a stock rom, you cannot use any other partition table than the stock one. Unless, you do some modifications (see the post below).
MatDrOiD said:
Conclusion: When you use a stock rom, you cannot use any other partition table than the stock one.
Click to expand...
Click to collapse
Wrong.
erklat said:
Wrong.
Click to expand...
Click to collapse
Nice, thanks. Never heard about it.
I've got s-on, is it important?
No it's not, you either:
1. Trying to flash a ROM for non stock hboot (you need S-OFF and custom Hboot for this)
2. Didnt partitioned you SD Card with ext partition (or did it wrong)
amh15 said:
Similar issue here...
I have an unbranded original AMOLED Desire on Froyo.
Unrevoked 3 and AlphaRev S-OFF went fine. Took a nandroid backup.
I thought bravo_alphaspl-sense.img was supposed to allow the use of the original stock ROM, but installing it and restoring the backup makes the phone hang at "WHY SO SERIOUS?". After restoring the original partition table and reloading the nandroid backup it now seems fine again.
Is there no way to use the patched HBOOT partition tables with the stock Froyo ROM?
Any suggestions? I tried the IRC but no-one answered, but I'm a total IRC noob so I might have been doing it wrong.
I have tried searching for this, with little luck.
Alan
Click to expand...
Click to collapse
HBOOT zip files (update with alpharev recovery) : http://forum.xda-developers.com/showthread.php?t=1147184
Custom HBOOT (update with alpharev recovery): http://forum.xda-developers.com/showthread.php?t=806321
And look at my sig for a very good sense2.1 + sense3.0 addons
Hmm, i am e newbie here with the same problem on my HTC HD2.
all roms work fine except the ones WITH sense. Every one hangs at boot screen.
(the screen where it shows HTC originally i believe) just before the lock screen appears.
now i see i MUST partition my SD card (EXT3/EXT4) in order to use roms with sense ?
Yes.. I believe most ROMs require an EXT Partition on your sdcard. Can use gparted or minitool to partition it.
Another point to note is that sense 3 ROMs sometimes take AGES on first boot... sometimes it's a good idea to just leave it.. go do something, watch some tv.. go to the crapper, watch some more tv.. and then find it booted
bortak said:
Yes.. I believe most ROMs require an EXT Partition on your sdcard. Can use gparted or minitool to partition it.
Another point to note is that sense 3 ROMs sometimes take AGES on first boot... sometimes it's a good idea to just leave it.. go do something, watch some tv.. go to the crapper, watch some more tv.. and then find it booted
Click to expand...
Click to collapse
Thank you for your reply.
it is driving me nuts.
i will take your advice.
an hour will be enough i guess ?
after that, it just doesnt boot, right ?
Nachoman2010 said:
an hour will be enough i guess ?
Click to expand...
Click to collapse
If it isn't booted after 20 minutes tops, it is likely it will not boot at all.
So, like a half of a year ago I've got my Desire, second hand. Now I didn't want to be stuck forever on Android 2.2 and old Sense, so I decided to root and install a newer rom. Rooting and S-OFF were succesful after a bit messing around, but it worked. So, I've tried a lot of roms, but just a few of them seemed to work, Usually the ones, I didn't need. Right now I'm on the Touchwiz 5 JB rom, but it sometimes has a problem with the microphone. Else than that, it works nicely stable, many times more stable than the 2.3.3 RUU from HTC. But don't really like the interface, I'm a huge fan of Sense.
Now I didn't get any Sense rom to work, all the way from the 2.1 Sense roms to the newest 4.1 rom (where the number is the Sense version). I only got some plain roms to work, which I've used a little time, but they don't really satisfy me.
So, the tech information: rooted with Revolutionary, so the recovery is the ClockworkMod. The phone is also S-OFF, runs on HBOOT 6.93.1002, and currently runs on the Touchwiz 5 JB rom. I've tried almost all roms with Sense, exept for some new ones (4.0+) since they still have a lot problems with things I need to have.
So, I hope somebody is able to help me.
Looking right now, I haven't tried the latest Cooldroid Revolution yet, so I'll try that right now.
Tell us a little about your sd-ext partition.
I'm 99% certain you didn't create EXT partition on SD card, or you didn't do it correctly.
Use 4ext recovery to partition your SD (create 1GB ext4 partition and nothing else, rest will be FAT32 where you store your media etc.)
Reason why Touchwiz 5 JB worked for you, is that it doesn't require EXT partition to boot, since you have to activate a2sd script manually using terminal.
And without a2sd you will run out of space rather quickly.
Well, I indeed have no EXT partition, since I've tried that once, but resulted into a USB brick and malfunctioning SD-card. I will google it whenever I've tried this rom.
Scoutsassin said:
Well, I indeed have no EXT partition, since I've tried that once, but resulted into a USB brick and malfunctioning SD-card. I will google it whenever I've tried this rom.
Click to expand...
Click to collapse
Check out the partitioning guide in my sig.
abaaaabbbb63 said:
Check out the partitioning guide in my sig.
Click to expand...
Click to collapse
oooh nice and simple!
Good, with the EXT 2 partition it all works now. Got RSK Satelite (whatever it's called) running, Thanks for the help everybody!
Hello all,
I've done a search on this but can't find anything describing a problem exactly the same as mine (although I have a feeling it is what people mean when they say bootloop?).
So with the eventual aim of freeing up the internal storage on my Desire by partitioning the SD card (and using link2sd), I have gained S-OFF with the Revolutionary method, got root with superuser.zip and used 4ext Recovery Touch to format the SD card by using this guide. Now this is where things went a bit wrong. 4ext kept saying I was in safe mode and didn't seem to be doing anything. I followed some more instructions from here to wipe the cache and possibly some other things (this is probably where I went wrong..). I do believe I now have a 2GB sd-ext partition (ext3) and 6GB FAT32 (it's an 8GB card).
Now, when I boot the phone it goes straight to the hboot screen (white screen with skateboarding androids). No matter what options I choose it won't boot into Android-proper. I can however, get back into Recovery (4ext) so I'm assuming I'm not in a huge amount of trouble and have perhaps just screwed up my stock install.
I was planning on keeping it stock (it is actually my girlfriends so I didn't want any hassle), but now I am thinking I could just install a new ROM? Just wondering what my best route from here is..
Should I attempt to go back to stock by following a guide like this (2nd post) with a 'Desire 2.3 RUU (PB99IMG)'? Will that work? Will it undo everything else I've done? Having read up on here about RUUs I'm a bit scared of that to be honest..!
Or should I follow post #1 on the troubleshooting guide and use 4ext to install a brand spanking new ROM?
Thanks for any advice.
No need to RUU, that would undo everything.
So you're already s-off, with 4ext installed, and you can boot into recovery :good: You've partitioned your sd card correctly too (ext4 should in theory be faster than ext3, you can convert it quite easily in 4EXT, but may not make much difference)
Now just install a new rom from scratch is the easiest way. Pick one from the development section, still plenty of choice. You can even find the stock rooted 2.3.3 Rom there somewhere if she wants that. Use the "wipe all partitions except sd card" option within 4EXT, then install the ROM.zip.
When you pick a ROM, you should also check which hboot is more optimal for space within each thread. You're currently still on stock hboot I take it, which has 250MB system size. A lot of ROMs have smaller system than this, so using a more efficient hboot with smaller system size (and larger internal memory (/data) partition ) is beneficial. You'll need to go to alpharev.nl to find the hboots, and I recommend to flash them using fastboot commands
Depending on the ROM, you may not need to use link2sd at all as it likely has an A2SD script built in, or you may need to activate it via terminal commands, read/search the individual rom thread for details.
If you're still worried about space, I always recommend to use an app like 'diskusage' to browse all your partitions.
Thanks, very helpful. I did originally partition the ext-sd as ext4 but when it didn't work I thought I should perhaps try ext3. I thought perhaps the Desire wasn't recognising the ext4 format. As it turns out I think it was just because I had done it all in safe mode? Will the Desire recognise a 2gb ext4 partition? If so, I may as well reformat again..!
Unfortunately I'm at work now so don't have the phone infront of me. I remember it says 'Revolutionary' in pink at the top in hboot, but I can't remember the numbers.
As for ROMS.. hmn so many options. Any recommendations for something stable and reasonably fast. Stable being the top priority I suppose. I'm tempted to try a JB ROM but I'm assuming that wouldn't be particularly fast or stable! Might be interesting to try though. I will use Apex Launcher over the top of it anyway...
Scamm0r said:
Thanks, very helpful. I did originally partition the ext-sd as ext4 but when it didn't work I thought I should perhaps try ext3. I thought perhaps the Desire wasn't recognising the ext4 format. As it turns out I think it was just because I had done it all in safe mode? Will the Desire recognise a 2gb ext4 partition? If so, I may as well reformat again..!
Unfortunately I'm at work now so don't have the phone infront of me. I remember it says 'Revolutionary' in pink at the top in hboot, but I can't remember the numbers.
As for ROMS.. hmn so many options. Any recommendations for something stable and reasonably fast. Stable being the top priority I suppose. I'm tempted to try a JB ROM but I'm assuming that wouldn't be particularly fast or stable! Might be interesting to try though. I will use Apex Launcher over the top of it anyway...
Click to expand...
Click to collapse
Try deleting the 4ext folder on your sd card to fix the safe mode issue, or also try going into wipe and select "Format all partitions (except sd card)."
I would recommend any of milwilds roms. My personal favourite is this one. Its very fast and stable, based on gingerbread, and its usually what i install on other peoples desires.
As for jb roms go, i wouldnt recommend one if your installing it for someone that doesnt know much about phones. They arent particularly fast, but the one i use (in my signature) is quite stable in my opinion.
Scamm0r said:
Unfortunately I'm at work now so don't have the phone infront of me. I remember it says 'Revolutionary' in pink at the top in hboot, but I can't remember the numbers.
Click to expand...
Click to collapse
If you don't remember changing hboot, you're still on stock hboot.
As for ROMS.. hmn so many options. Any recommendations for something stable and reasonably fast. Stable being the top priority I suppose. I'm tempted to try a JB ROM but I'm assuming that wouldn't be particularly fast or stable! Might be interesting to try though. I will use Apex Launcher over the top of it anyway...
Click to expand...
Click to collapse
I can also vouch for mildwild roms. These have much smaller system sizes, so best to change hboot before you install them as instructed above. Most of them fit into cm7r2 hboot, but check each thread for compatibility.
Thanks guys. Would you recommend that MW ROM over something like CyanogenMod 7.2.0.1 off their site? I see CM banded around quite alot, seems to be a go-to ROM for alot of people?
I'm home now, this is what I see on hboot:
-Revolutionary-
BRAVO PVT1 SHIP S-OFF
HBOOT-6.93.1002
MICROP-031d
TOUCH-PANEL-SYNT0101
RADIO-5.11.05.27
Also, before I do it. Any problems for the Desire to see a 2GB ext4 partition? With the rest as FAT32? She won't be putting alot of media on it as she has a separate iPod.
Thanks.
Scamm0r said:
Thanks guys. Would you recommend that MW ROM over something like CyanogenMod 7.2.0.1 off their site? I see CM banded around quite alot, seems to be a go-to ROM for alot of people?
I'm home now, this is what I see on hboot:
-Revolutionary-
BRAVO PVT1 SHIP S-OFF
HBOOT-6.93.1002
MICROP-031d
TOUCH-PANEL-SYNT0101
RADIO-5.11.05.27
Also, before I do it. Any problems for the Desire to see a 2GB ext4 partition? With the rest as FAT32? She won't be putting alot of media on it as she has a separate iPod.
Thanks.
Click to expand...
Click to collapse
I would go with mw over cm. Cm 7 feels old and stale, while milwilds redux ROM feels fresh and different. In terms of stability and speed they are pretty much the same.
2gb shouldn't be too much of an issue, but usually the max recommend ext partition is 1.5gb.
Thanks again. I'm now up and running. Looks very nice indeed! I'll be honest though, I bailed out of flashing a new hboot. Too scary. After incurring the girlfriend's wrath after one day with a dead phone, I wouldn't want to brick it entirely!
A couple of questions now..
- Do I need to install link2sd? I'm looking at 'diskusage' but I'm struggling to make much sense of it. I can see my sd-ext on there though which I guess is good!
- Are there any peculiarities installing generic apps like Facebook, Youtube etc? At first glance the market seems to work ok.
- Does the cpu underclocking (whilst screen off) work well? Is it risky at all if I use the generic settings?
Also, I was going to chuck Apex launcher on it for her (I love it, and she wants a scrolling dock) but it's not compatible. Any others that are good? Nova isn't compatible either
Scamm0r said:
Thanks again. I'm now up and running. Looks very nice indeed! I'll be honest though, I bailed out of flashing a new hboot. Too scary. After incurring the girlfriend's wrath after one day with a dead phone, I wouldn't want to brick it entirely!
A couple of questions now..
- Do I need to install link2sd? I'm looking at 'diskusage' but I'm struggling to make much sense of it. I can see my sd-ext on there though which I guess is good!
- Are there any peculiarities installing generic apps like Facebook, Youtube etc? At first glance the market seems to work ok.
- Does the cpu underclocking (whilst screen off) work well? Is it risky at all if I use the generic settings?
Also, I was going to chuck Apex launcher on it for her (I love it, and she wants a scrolling dock) but it's not compatible. Any others that are good? Nova isn't compatible either
Click to expand...
Click to collapse
No need to install link2sd. A2sd is installed by default and is already activated. Dont worry about it.
Apex and nova need 4+, so i would recommend holo or go launcher. i think the default cpu settings work good enough.
Scamm0r said:
Thanks again. I'm now up and running. Looks very nice indeed! I'll be honest though, I bailed out of flashing a new hboot. Too scary. After incurring the girlfriend's wrath after one day with a dead phone, I wouldn't want to brick it entirely!
A couple of questions now..
- Do I need to install link2sd? I'm looking at 'diskusage' but I'm struggling to make much sense of it. I can see my sd-ext on there though which I guess is good!
- Are there any peculiarities installing generic apps like Facebook, Youtube etc? At first glance the market seems to work ok.
- Does the cpu underclocking (whilst screen off) work well? Is it risky at all if I use the generic settings?
Also, I was going to chuck Apex launcher on it for her (I love it, and she wants a scrolling dock) but it's not compatible. Any others that are good? Nova isn't compatible either
Click to expand...
Click to collapse
You won't brick your phone by flashing an hboot, as long as you follow all the instructions . It's beneficial just in case your girlfriend starts installing many apps. App data still gets stored on the internal memory (/data) partition, so it may get the low memory warning again which kind of defeats the purpose of doing this in the first place.
Open diskusage again, choose /system. You'll see a lot of free space on this partition....that's basically all completely wasted on stock hboot. At least you can see you sd-ext partition fillling up though.
There's another way to flash hboot without fastboot commands if you prefer. I always recommend that way simply because it forces the user to understand a little about what they're doing, plus it's always handy to install adb and fastboot drivers anyway
So:
- Download the PB99IMG_cm7r2.zip from alpharev.nl, rename it to PB99IMG.zip exactly, not PB99IMG.zip.zip, put it on the root of your sd card
- Reboot directly into recovery, nandroid backup (hard to go wrong now, no need to worry)
- Power down, boot into bootloader (vol down + power)
- It should find the file, and ask you to flash it, select yes
- Reboot into recovery, full wipe and nandroid restore
- It's exactly the same, but enjoy the extra internal memory. Open diskusage again, you'll find that there's less free space on /system, and /data has increased
Thanks Eddie, you're right of course. How safe is that method compared to using Android Flasher? I already had that installed on my PC for one of the steps previous.
So the nandroid backup will keep the phone set up as it is? I know she will have been customising her homescreens etc already now that it's up and running haha. OR is it best to reinstall the ROM again anyway and start from scratch?
I presume the backup option in 4ext recovery is a nandroid backup? I think I did one of those before after I got MW up and running.
Thanks again.
Scamm0r said:
Thanks Eddie, you're right of course. How safe is that method compared to using Android Flasher? I already had that installed on my PC for one of the steps previous.
So the nandroid backup will keep the phone set up as it is? I know she will have been customising her homescreens etc already now that it's up and running haha. OR is it best to reinstall the ROM again anyway and start from scratch?
I presume the backup option in 4ext recovery is a nandroid backup? I think I did one of those before after I got MW up and running.
Thanks again.
Click to expand...
Click to collapse
Android flasher is the same as fastboot really. It's just a program so you don't type things. I've never used it personally, but it should work. I believe you flash the cm7r2.img directly (not the.zip file). All 3 of those methods (fastboot, android flasher, PB99IMG.zip are safe, get the same result eventually)
The thing to remember (which I should have mentioned before) whichever method you use, check the md5 sums of the .img files before you flash them (you should be able to see those long text/numbers on the alpharev page). Search for a program called md5check. (It just basically verifies the file against that md5 sum like a barcode so you know haven't downloaded a bad file.)
Nandroid backup is an exact image of the phone as it is. Homescreens, saved game data, texts, everything. So you won't lose anything after restoring it. I suggested that you change hboot before you install the rom for this exact reason, so you wouldnt have to backup and restore, but we're here now already