Related
I had a few questions that I can't pull up much information on. There looks to be a ton of updates we now have the option of putting on our EVO, what are the differences.
Kernel
--- Alright, I know this one but for anyone who doesn't. This is the heart of the phone. It is what allows software to talk to hardware.
--- Why do some of the kernel changes break the camera/accelerometer? Are these drivers built into the kernel instead of modules? Can they not be rebuilt with different kernels?
NAND
--- What is the NAND and why are we unlocking it?
--- NAND is a type of flash, no? Are all they system files (i.e. the /system folder) on their own chip inside the evo? How can rooting and remounting the system r/w not control the /system folder?
--- While I'm at it, does rooting just me remounting everything but the /system folder as r/w. So a non rooted phone is read only except for the SD card and where ever apps from the market are installed?
Recovery
--- It seems like there are a couple recovery systems out there... clockwork and another. Did the EVO not come with its own recovery system. What have these modded versions added?
ROMS
--- What are these really doing if they are not messing with the /system folder. Are they just a bundle of different programs? Change the rom and you change the programs that are installed? What is the difference between a ROM and a DEV-ROM
RADIO
--- What is the deal with the new radio. Is it updated drivers for the baseband? This kind of gets into my kernel question about how the drivers are handled within the kernel. How can this work across multiple kernels, but we cant get the camera working?
I know this is a lot, but if anyone could fill in some of the holes for me I would appreciate it.
Thanks
bump...
Any thoughts? You don't have to answer them all.
I am NO expert, but can help a bit....
Kernel
--- Alright, I know this one but for anyone who doesn't. This is the heart of the phone. It is what allows software to talk to hardware.
--- Why do some of the kernel changes break the camera/accelerometer? Are these drivers built into the kernel instead of modules? Can they not be rebuilt with different kernels?
From my understanding, the kernles that break the camera, are kernels that are ports of kernels from other phones. So, the drivers for the camera are not the same as for the other phones camera.
Recovery
--- It seems like there are a couple recovery systems out there... clockwork and another. Did the EVO not come with its own recovery system. What have these modded versions added?
My understanding is that the phone's original recovery, is locked to only flash Sprint's Official ROM's. So the custom recovery will allow to flash custom ROM's
ROMS
--- What are these really doing if they are not messing with the /system folder. Are they just a bundle of different programs? Change the rom and you change the programs that are installed? What is the difference between a ROM and a DEV-ROM
Aside from changing apps, ROM's can do different things like optimizing the apps so that they run smoother, move data from one place to another to run more efficiently and allow for a number of customizations that would not be available with only the stock ROM rooted. A ROM is understanded as a usable, stable ROM. A DEV-ROM is one that is not stable, were it has things that still dont work and need to keep improving.
Hope it helps!
Perfect thanks.
The ROM/DEV-ROM thing was really bugging me, and the recovery explanation makes sense.
amw2320 said:
I had a few questions that I can't pull up much information on. There looks to be a ton of updates we now have the option of putting on our EVO, what are the differences.
Kernel
--- Alright, I know this one but for anyone who doesn't. This is the heart of the phone. It is what allows software to talk to hardware.
--- Why do some of the kernel changes break the camera/accelerometer? Are these drivers built into the kernel instead of modules? Can they not be rebuilt with different kernels?
Click to expand...
Click to collapse
So with *.NIX kernels such as linux, unix, and the android kernel there are modules that make up the kernel itself. Any *.NIX kernel is going to be modular and this makes it more efficient and robust. In the case of specific items not working between different kernels, it most likely means the kernel was compiled with specific modules that have specific scripts and drivers in it. This method speeds up the kernel because it takes out stuff not needed. But means it limits the devices the kernel can run on.
In the case of Android ROMs not being able to fully interface with hardware, it likely means the kernel is missing something as another commentator already suggested.
NAND
--- What is the NAND and why are we unlocking it?
--- NAND is a type of flash, no? Are all they system files (i.e. the /system folder) on their own chip inside the evo? How can rooting and remounting the system r/w not control the /system folder?
--- While I'm at it, does rooting just me remounting everything but the /system folder as r/w. So a non rooted phone is read only except for the SD card and where ever apps from the market are installed?
Click to expand...
Click to collapse
We are unlocking NAND and rooting phones to get access to file systems that are locked down by phone manufactures/cell providers. Doing so unleashes the full potential of the device.
If you rooted your phone and you do not have full access to the file system, you only did part 1 of the root process. There are 2 parts because one unlocks NAND and the other unlocks the file system completely with the phone booted. Step 1 just unlocks filesystem for NAND which means you have to be booted into NAND for full access to file system. I think I have that right.
Recovery
--- It seems like there are a couple recovery systems out there... clockwork and another. Did the EVO not come with its own recovery system. What have these modded versions added?
Click to expand...
Click to collapse
Clockwork and the others are just replacing NAND with their own system, if I am correct. I recommend doing this if you are rooted because you get better features and a constantly updated system, where as NAND is only updated when Sprint and HTC have an update with a NAND update in it (which isn't often). The way I recommend updating this is using ROM Manager once you are rooted. It is very safe and easy.
ROMS
--- What are these really doing if they are not messing with the /system folder. Are they just a bundle of different programs? Change the rom and you change the programs that are installed? What is the difference between a ROM and a DEV-ROM
Click to expand...
Click to collapse
When you see ROM, think GUI for the OS, collection of apps and scripts. The ROM what you are going to interact with and use. I highly recommend flashing a custom ROM once rooted because you will have less problems and they are way more efficient than stock. Developers take time and care to test and tweak their ROMs so that they not only perform good, but give us the features we want. Find one you like and install. Make sure you do a NAND backup though once you get everything installed the way you like. Also do a titanium backup (app from marketplace) too.
RADIO
--- What is the deal with the new radio. Is it updated drivers for the baseband? This kind of gets into my kernel question about how the drivers are handled within the kernel. How can this work across multiple kernels, but we cant get the camera working?
Click to expand...
Click to collapse
It is recommended not to mess with the radio unless a ROM you want requires it. I flashed it without any trouble at all and things seem fine on my phone. Some people recommend flashing it because they think it makes the cell radios in the phone perform more efficiently and such. This is all I can say on the radio as I'm no expert.
I see most of the questions have been answered above...I'll attempt as well and perhaps it will help clarify (or just give a different way of looking at it).
amw2320 said:
I had a few questions that I can't pull up much information on. There looks to be a ton of updates we now have the option of putting on our EVO, what are the differences.
Kernel
--- Alright, I know this one but for anyone who doesn't. This is the heart of the phone. It is what allows software to talk to hardware.
--- Why do some of the kernel changes break the camera/accelerometer? Are these drivers built into the kernel instead of modules? Can they not be rebuilt with different kernels?
Click to expand...
Click to collapse
Yes, the kernel is the heart of any OS (Windows has one, Linux has one, etc). The kernel is where everything eventually goes to do anything.
The reason the new kernels do not have camera functionality is because, while we have generic source code, we do not have the drivers/modules for that source code. HTC does some modifications within the source that are proprietary and so we have to attempt to try and reverse engineer it. About the time we do, they release the source code (I have suspicions of conspiracy, but that may just be me) and that's when the kernel's really roll out with some fun stuff.
New kernels will be the source of the most new features...overclocking, efficiency improvements, etc.
NAND
--- What is the NAND and why are we unlocking it?
--- NAND is a type of flash, no? Are all they system files (i.e. the /system folder) on their own chip inside the evo? How can rooting and remounting the system r/w not control the /system folder?
--- While I'm at it, does rooting just me remounting everything but the /system folder as r/w. So a non rooted phone is read only except for the SD card and where ever apps from the market are installed?
Click to expand...
Click to collapse
This is one of the areas I'm most weak in for understanding but I'll still take a stab.
NAND is a type of flash and, to my knowledge, it's own seperate chip. It is usually locked to prevent modifications that could break your phone or prevent it from updating properly...I *think* it's used during boot so the lock would translate straight through to your OS and prevent changes if put in a locked state (think similar to how some SD cards have a "lock" switch on the side to make it read only, except a software version of it).
Recovery
--- It seems like there are a couple recovery systems out there... clockwork and another. Did the EVO not come with its own recovery system. What have these modded versions added?
Click to expand...
Click to collapse
Clockwork and AmonRA's recoveries are replacements that add functionality over the stock recovery. The stock recovery is only meant to be used by the manufacturer to perform certain tasks (like updating, resetting, etc...but no user functions like backup/restores.). Both Clockwork and AmonRA's recoveries add the ability to take a complete image of your phone (so that you can always restore any software changes no matter how severe), reformat and partition your sd card (to add/remote a cache partition or a partition for Apps2SD), reset battery stats, and a host of other things I'm sure I haven't even touched on. Also, I believe they add the functionality to flash unsigned updates done by the community (not just restricting us to HTC's updates).
ROMS
--- What are these really doing if they are not messing with the /system folder. Are they just a bundle of different programs? Change the rom and you change the programs that are installed? What is the difference between a ROM and a DEV-ROM
Click to expand...
Click to collapse
Most of the ROMs you see now require NAND unlocks so that they can mess with the apps in /system. Some ROMs are just a certain package of apps or a set of themes. Others add functionality or make certain things easier to implement. Yet others are tweaked to attempt to change other aspects of the OS to improve performance of battery life through tweaks to when the system performs certain tasks.
Ultimately, each ROM is different and the changelogs *should* tell you what all they've done over the stock (or if they're based on another ROM, you can open that page to see the tweaks they are tweaking, etc). (Sometimes it can get pretty big on the tweaks on another rom's tweaks on another rom's tweaks...check the CDMA hero forums for some combination roms ).
ROMs vs Dev-ROMs - Dev-ROM's are usually a work in progress...they are testing new features and often will be on the bleeding edge (emphasis on bleeding). These will sometimes (even likely) break something while they try and improve or add new functionality in another aspect. You should only flash these if you want to help test and if you have an idea of what's going on so you can help troubleshoot.
Normal ROMs are usually more stable (usually) and will have milder modifications (though once a DEV-ROM has successfully gotten a new feature stable, most other ROMs will incorporate those changes...it's kindof a lifecycle).
RADIO
--- What is the deal with the new radio. Is it updated drivers for the baseband? This kind of gets into my kernel question about how the drivers are handled within the kernel. How can this work across multiple kernels, but we cant get the camera working?
Click to expand...
Click to collapse
Radio images are a bit more like firmware updates to the radio chip. These often help to improve reception or connectivity or fix instabilities or other problems. Not everyone experiences the issues that it attempts to fix and doing a flash on your own does have certain risks. The odds of a problem arising for you isn't high, but the effect is potentially severe if a problem does occur. The main thing to remember is to ensure you have enough battery for the changes to occur (firmware updates in general recommend this on all devices, be it laptop BIOS updates or phone radio updates...I recommend using the wall charger and not unplugging it until 5 minutes after the update has completed), and ensure that you don't try and do anything else on the phone while the update is occuring.
I know this is a lot, but if anyone could fill in some of the holes for me I would appreciate it.
Thanks
Click to expand...
Click to collapse
Hopefully the info given by me and my fellow ex-newbies will help with your desire to learn! There's a lot of cool stuff about our phones and I love that we can get a bit into the guts of the thing (unlike some phones*)
*I can't help but throw a little jab at Apple every so often.
This is great information and helps me to push myself even further towards ROM development.
I enjoy my Evo and this website is amazing
Great thread and information, I was looking for something similar. I'm totally new to Android and want to start the whole rooting process.
I don't mean to hijack the thread or anything, but some terms are thrown around and I don't have a 100% understanding of what they really mean....could someone please define them?
Recovery?
Flashing?
Thanks codemonk and webs, that was awesome.
Onepanda, i'll give your question a shot.
Flashing is really just putting files on you phone. Generally it refers to replacing the andriod system files. You can flash a kernel, a ROM, drivers, or just an update to one of those.
Recovery is a mode you can put your phone into from boot. This is where you flash the files from. You cant just replace system files while they are running, so you boot into recovery mode and flash them from there.
Recovery mode also has a few other features allowing you to reset settings (cache) and make backups.
Hello everyone,
I just got myself a new HTC Desire with Vodafone Branding.
HBOOT : 0.800
Software number: 1.19.161.5 (I believe this should be Android 2.1)
Kernel version : 2.6.29-b7e82785 (I guess this is still HTC original)
I wanna root my phone and if I guess that I can do further, I am also thinking of using another rom.
My main concern is that the internal memory can not fit any more apps and I still want to add more, after searching in the internet I found out that I need to root and/or to use other rom.
Second concern...I just wanna learn..
I have downloaded Unrevoked3 and the H-Boot USB driver.
From what I have read, I am all set for rooting (gonna do this tomorrow evening after work and after I have calmed down a bit, I am a bit nervous cause this is my first time ).
I have removed the HTCsync but still keeping the drivers.
I also know that I will need ClockworkMod. Make EXT2/3/4 partition with at least 512MB (I would like to make it 1gb) and optional SWAP (perhaps I will make it 256mb, do I really need SWAP?).
So, please teach me on :
1. Now about the rom, I need an Android 2.2 with optimum stability and speed, to tell you the fact, I don't even now which one and where to get it.
2. Beside the main rom, do I need also the camera and radio rom to get them running? again where to get them? How do I install them? The same way as installing the main rom (from HBOOT recovery)? Before or after installing the main rom?
3. How to make the back up of my current rom, setting, and apps? I don't have much apps yet but perhaps I would need the backup if something went wrong.
I still a whole bunch of questions but I guess those will do for now.
Please be kind and help me one this one pleaassssseeeeeeeee...
Anyway...thanks in advance.
Read in development.
Sent from my Evil Lair using Doomsday Device
1. This thread has all the rom's in it. It's all about personal taste but if you like sense i would recommend Leedroid to start with.
2. When you come form 2.1 you will need to upgrade your Radio, if you OTA upgrade to 2.2 before rooting you do not have to update your radio but you can. A link to the radio thread is also in the above link.
3.
Once you are rooted with unrevoked you can preform a nandroid form recovery or you can download Rom Manager from the market and backup via that.
If you just want to backup apps you can use titanium backup or you could sync your apps with appbrain and reinstall them.
About the ext partition, i think swap is not necessary and if you want a 1 gig partition use Gparted
Thank you very much for the answer.
I will look into those first.
If I found any trouble, I will ask you guys again.
Thank you again.
First, I wanna say thank you again.
I have read some review about the LeeDroid. It sounds very good.
I will pick LeeDroid as my first after market rom.
I will thus flash (.zip files are already downloaded in the PC) :
Leedroid 2.2e
Latest Radio ROM; 32.48.00.32U_5.11.05.27
LeeDroid 2.2e Kernel Boot Fix (Just to be sure, because I don't how my desires proc can be OCed)
DSP Manager.
My last questions:
- Is there any particular order which rom I should flash first?
Example : LeeDroid - Radio - Kernel Fix - DSP manager
-Can I flash them all with only 1 reboot (flash everything and choose reboot only once in H-Boot recovery menu)? or Do I have to flash only one at a time, reboot, and flash the next one and reboot again?
I'm not sure about radio's.
But if you flash leedroid 2.2e you need to flash it and after it (without reboot) flash the bootfix kernel.
Addons and theme's should be flash after the first full boot.
that is the correct order
you must flash the rom first, reboot, then flash the rest all in one go. REMEBER the first reboot is important!!
Got it!
Radio (I need the radio rom cause my radio rom is old, belongs to original 2.1) , Leedroid main rom and Kernel Fix in one go, then 1st reboot.
And then the other addons in one go.
and of course reboot again.
Thanks a lot guys!
aaa said:
Got it!
Radio (I need the radio rom cause my radio rom is old, belongs to original 2.1) , Leedroid main rom and Kernel Fix in one go, then 1st reboot.
And then the other addons in one go.
and of course reboot again.
Thanks a lot guys!
Click to expand...
Click to collapse
check here for improved gaming performance, you can download leedroid kernel with boot fix, SD speed fix and GPU driver patch http://forum.xda-developers.com/showthread.php?t=825304
h3llb3nd4 why is it important to reboot after rom flash?
It needs to install the boot images for the Rom.
Sent from my HTC Desire using XDA App
lots of things came up to me this weekend, I am not able to flash my Desire.
Since I am doing this for the first time, I would like to have a quite time for myself alone, so that I am calm during the flashing just in case if something went wrong.
well...I will do it (I hope) on next friday evening...
I will write again the progress next week.
Untill now all I have done is the rooting via Unrevoked3, and installing the rom manager from android market. I haven'T even formatted the sd card.
Thanks again.
OK, Go to hell with quiteness.
I can not wait hehehehe just to anxious to start flashing.
and.....
I did it...it works...
Thank you
Flashing is not that hard...hehehehe...
I have played with LeeDroid and I have to say...This can do a lot more than the original.
Hmmm...I a fan of Sense although some say it slows down the phone.
I have tried the HTC HD ROM on my Desire, I like the new sense but too bad the camera still doesn't work. I have to go back to LeeDroid just because of the camera problem.
|OP|,
I joined this forum because I am a newbie just like you (before you got your Jedi-Flashing Wings).
I too have a HTC Desire running Android 2.2 (Kernel 2.6.32.15). I have exactly the same problem as you had - I've run out of room for apps on internal memory and the standard Froyo apps2sd thing can't shift anything else to the SD card.
I'm really interested to learn how your phone handles apps now. Does your phone think it has 1 gig of internal memory? Are you able to shift every app to the SD card? Did you have to give up your HTC apps and widgets?
I would really appreciate any feedback.
Cheers!
Yup...limited room for installing apps is my main or perhaps my only reason of flashing my desire with modified rom.
- About the 1GB thing, well I didn't do it since I wanna try the flashing procedure just as it is described in youtube desire rom flashing guide (not confident enough to do it all alone), and it is shown in youtube using only 512MB
But, I will try it later (planned on december after I finish my university assignment).
-Well, I have flashed and used it only for about a day or two, so I am still not 100% sure, but all the apps I have downloaded and installed are all going to the SDCard. I guess all of them will eventually go to the SDCard.
-HTC Apps and widgets? Everything is there, as far as I noticed until now.
Now, I am enjoying the DSP equalizer, apps to SDCard (16GB ), but still afraid of OCing.
SMS, WLAN, Camera, E-Mail, etc. seem to work smooth, no bugs found so far.
My Desire seems to run faster than with the original rom, but it is just my subjectiv comparison.
The phone won't 'see' your EXT partition but when you install apps the quoted storage will barely go down...I have a 1GB EXT3 partition on my SD card for when I use a custom ROM, its 16GB so I don't miss the space as I'm on a stock ROM at present and don't use many apps
EddyOS said:
The phone won't 'see' your EXT partition but when you install apps the quoted storage will barely go down...I have a 1GB EXT3 partition on my SD card for when I use a custom ROM, its 16GB so I don't miss the space as I'm on a stock ROM at present and don't use many apps
Click to expand...
Click to collapse
If the storage are going down or used slowly, is it worth to have 1GB as EXT3 or just leave it be at 512MB?
Depends on the ammount of unneccessary apps you plan to install
EddyOS said:
Depends on the ammount of unneccessary apps you plan to install
Click to expand...
Click to collapse
Hahahahahahaha....
You got that one right on the spot.
Most of my apps are games.
Games are not considered as necessary apps.
I will stick with 512MB
Thanks EddyOS and |OS|,
This sounds awesome! I've got 14 MB remaining on my internal memory and a long list of apps I still want to play with.
With this news I'm going to jump into the whole flashing/rooting thing (incidently why do both of these terms have sexual overtones?).
LeeDroid here I come!
|O2| did you use the Unrevoked root method? Could you possibly post the youtube link that you mentioned? I am, as you were, quite anxious about turning my beloved Desire into an expensive paperweight so any extra tips would be very appreciated. (I have heard that it is fairly simple and has a very low risk but I'm still a bit hesitant)
Thanks again! What a wonderfully helpful community this is!
Hi all,
Please can you help me with the end questions, a quick background of what i've done so far.
I have been a member of Modaco for a while and used to own a Orange San Francisco, first android phone. I learnt a bit with that i.e rooting and updating to Paul's modaco rom's, market apps etc.
I have since bought a HTC desire and joined XDA which is a (superb forum), I'm really happy with my desire its on O2 contact and is the white newer version.
I was really confused with regards to rooting as the bootloader was high 0.93 so couldnt use some methods but newer posts showed that it was as easy as downloading unrevoked. Again had some problems rooting, realised that HTC sync must be installed first and then removed otherwise unrevoked will not pick up your phone.
Unrevoked rooted and installed Clockwork recovery, I then read about Amron Ra which is apparently more stable than Clockwork when installing Rom's, some posts suggested installing Rom manager and using flash recovery option, then alternative flash option in Rom manager to install AmonRa. So I installed Rom Manager it installed a newer version of Clockwork but when I then went to install alternative flash this option was blanked and not available.
After reading again I learnt I could flash Amron ra with unrevoked 3.0, you must go to file and custom recovery then find Amron Ra the version i installed was
recovery-RA-desire-v2.0.0-CM.img, I think this is the latest?.
Unrevoked went through the process, but stopped (oh no i thought this is going to get bricked) luckily everything was ok, after reading again I learnt that once rooted if your using unrevoked again its best to factory reset, so I backed everything up using Clockwork and made my first nand backup, I also packed up my installed apk's.
After factory reset, unrevoked did its magic and walla Amron Ra installed.
Now for the next step where I have some questions, unlike the orange san francisco the htc desire has loads of roms, some with sense (which i dont really know what is exactly yet) some froyo again what is froyo?, and some miui and some non sense.
So to a neebie where do you begin?
1. I have read about partitioning your sd card ext 2, 3 and 4, are these needed to use specific Roms and which ext do you need as it is very confusing?, I like the miui rom (MIUI XJ D2EXT X-PART 1.2.11) again there are 3 downloads there which should I download?
2. If the ext are needed must you have all 4 ext on a card and if so how much do you allocate for each if you have an 8gb card for example I read somewhere that the ext effects speed how can this be?
3. What are kernels I seem to be reading up about them a lot but no one really explains what they do, are they needed when installing a new Rom and can you mix and match different kernels with roms?.
4. Why is updating the radio on Rom's so important?, I see new roms then radio files must these be flashed?.
5. What is a dalvik cache clean is it the same as factory reset?
6. If I install a miui rom, which I'm interested in to start will there be any difficulties in later installing other sense or non sense roms and how do I go about avoiding these problems?.
7. What is the latest and best Miui rom available at the moment is it MIUI XJ D2EXT X-PART 1.2.11
These are all the questions for now, any help would be greatly appreciated at the moment I have a 4gb class 2 SD card but will be getting a 8gb class 6 in the next day or so, I mostly use the phone for texting, internet and sat nav.
Thanks a lot guys in advance.
All the best
Mav
You can refer to my answers over on MoDaCo
Wow, you have made quite a novel here
Half of your questions are answered TBH in the forums, so you should serach next time.
Okay
1.Which ext do you need? It will be 3 or 4, but every ROM thread specifies what do you need for it.
2. Of course you need all ext partitions on the SD Card. Again, there are ROM threads which specifies the size of the partitions. But usually look slike this:
* A2SD - Fat + Ext3/4, 0.5-1.5GB recommended.
* D2WE - Fat + Ext3/4, 1-1.5GB recommended.
* D2EXT - Fat + Ext4 + Ext4 + Swap (fat+1GB+0.3GB+0.1GB)
Can differ tough.
3.About the Kernels.
Tou can mix, but AOSP ROM with AOSP Kernel, Sense with Sense kernel. It is a chance that it will work otherwise, but will be buggy or phone won't boot.
4.If the ROM has new RIL (Radio interface layer) preinstalled, it is recommended to use a newer radios. Altough 5.11 version should work on every ROM.
5. No it is not.
dalvik cache is a program cache area for the program dalvik. Dalvik is a java based virtual machine that is the bases for running your programs (the ones that have the .apk extension). In order to make access times faster (because there's not JIT (just in time) compiler installed by default), the dalvik-cache is the result of dalvik doing a optimization of the running program. Sounds confusing. It's similar to the prefetch files in Windows.
Click to expand...
Click to collapse
6. No problems should be - just do a full wipe (factory reset, wipe data, cache & dalvik).
7. Yeah, that is the latest version I know of.
Hope youll find the answers good enough
Thanks guys,
Just a bit confusing I would post to the author of the rom but at present haven't got enough posts.
Just a further quick questions, what do they mean by swap? and also there are 3 files to download xj, au, and dev, why 3 files and which is the best.
thanks
XJ, AU and DEV are 3 different builds by different authors so you'd need to check them all out
Here's a link to the MIUI-Dev website that you might wanna look at. It's quite quiet but obviously all MIUI
http://www.miui-dev.com/forums/forumdisplay.php?16-HTC-Desire-GSM
So EddyOS, I read somewhere on the modaco forum that you had miui installed at one point, if you had to put one on again which one would you use along with radio and kernel?.
I can see that you have loads of experience and i'll go with your recommendation I appreciate that it is a preference thing i mainly want something quickish, stable and cool looking (xj, au or dev?).
I like the miui because they look like an iphone but have an android feel so to speak so best of both worlds, im no iphone hater but it is over rated but icons look cool.
thanks
mav
IMPORTANT: Stable to me means little to no bugs after months of use, not hours or days. This is not a thread for experimentation
Hi there,
I'm currently using mildwild 4.3 on my original HTC desire.
The intention to begin with was to get a ROM that would be as stable as possible and would cause me as little fuss as possible and basically I could continue using with the desire until the desire itself gave up with battery, too many falls, a cracked screen etc, none of which has happened yet so is still going strong.
This phone is for business use and I don't enjoy having to change ROMS like a lot of users on the site would, I just want something that works and will give me the least amount of hassle.
The phone does restart itself on occasion but this has happened with other ROMS I've used too.
I'm not too pushed about having the latest and greatest apps and gadgets which may be offered in the latest android versions. I'm happy with what 4.3 offers, anything extra would be a bonus.
Now the issue with 4.3 again is the internal space. Right now if I go to apps > manage > all, I see I have 129MB used and 19MB free, I've been using LinksSD as an extra APP on 4.3 and have moved all I can to the SD card, so I can't free any more space. Unfortunately if I'm giving it heavy use and get a lot of emails etc, the USED/FREE ratio changes and if free gets to about 15MB, then I get the space warning and synching to the phone stops and I can't get important business information which I sync with the calendar etc.
I've managed to keep it steady around the 19mb mark but what prompted this message was the release of a new app I want which takes up 30mb as opposed to the current one on the phone taking up 10mb, I'm afraid this will use up my precious few MB and will give me the synching issues again.
So what I was wondering is, does Mildwild 5.5 (or greater) handle the internal space in a different way that as long as I have decent sized SD card, I should never have space issues with the internal memory? This is important also as both my friend and my father are having internal space issues with their original desire and if I find a solution would like to help them too.
If you could please advise on the most stable version of Mildwild for the HTC Desire and if there is one that handles the internal space differently to 4.3 and would therefore never give me internal space issues as long as I have a decent SD card inserted. 4.3 isn't the answer it seems, but hopefully there is an alternative?
Stability is of prime importance, given the phone is used and is crucial for my business and may be put on my father and friends phone too, I need to make sure I don't have to touch any phone due to bugs etc, hopefully ever! I'd also like everything to simply "work", video recording, bluetooth etc.
Any feedback, direct links to suggested ROMS etc would be greatly appreciated! I'd prefer to not stray away from Mildwild as before installing 4.3 I did a lot of research and I'd rather stick to what I know.
I would stay with oxygen, but you should update to the latest version.
abaaaabbbb63 said:
I would stay with oxygen, but you should update to the latest version.
Click to expand...
Click to collapse
Thanks for the reply, so 4.3 is oxygen and 5.5 isn't? What's the latest oxygen do you know and does it address the space issue? What are the main reasons you suggest sticking with oxygen? Stability?
cormie said:
Thanks for the reply, so 4.3 is oxygen and 5.5 isn't? What's the latest oxygen do you know and does it address the space issue? What are the main reasons you suggest sticking with oxygen? Stability?
Click to expand...
Click to collapse
5.5 is an old CM7 based Mildwild.
4.3 is an old Oxygen based Mildwild.
Newer oxygen here:
http://forum.xda-developers.com/showthread.php?t=1353861
I would choose oxygen because it is the most stable custom android rom I know.
And if you would like more space, either change hboot, or check the sd-card partition guide in my sig.
I concur with MW's Oxygen-based ROMs as the most stable and reliable choice for your phone. However, instead of the most recent version (called MW-4.9 JG), I'd recommend version MW-4.4.
Why? Because up until that version, the ROM base that MildWild used was Oxygen w/ roalex tweaks, and from MW-4.5 onwards he went back to pure Oxygen. I find the roalex tweaks to be a very nice extra touch to the ROM, they make it feel like a more polished, finished piece of work.
Bottom line is, it's the best ROM I ever had on my phone, and after using it for months I've yet to encounter problems with it.
Thanks a lot for the continued support folks.
Ok, so given that oxegen is the most stable, I'd like to stay with that. Would there therefore be much difference between the 4.3 I'm currently using and 4.4 and then of course, 4.9? I do like polished tweaks, but if there's more stability in 4.9 I'd rather that.
So I guess it's either stick with 4.3, update to 4.4 or update to 4.9
Now, if I update, will either 4.4 or 4.9 provide a better way to manage the internal space issue?
I'm not very technical when it comes to these things, in fact, I had to pay someone to do a teamviewer session with me to guide me through doing the ROM etc in the first place so if I can avoid another ROM install, I'd prefer that.
Will changing the hboot (haven't a clue how to do that ) or following the guide in your sig coincide with 4.3, 4.4 or 4.9 do you think and if so, will completing the guide step by step mean no more space issues as long as I've free space on my SD card?
cormie said:
Thanks a lot for the continued support folks.
Ok, so given that oxegen is the most stable, I'd like to stay with that. Would there therefore be much difference between the 4.3 I'm currently using and 4.4 and then of course, 4.9? I do like polished tweaks, but if there's more stability in 4.9 I'd rather that.
So I guess it's either stick with 4.3, update to 4.4 or update to 4.9
Now, if I update, will either 4.4 or 4.9 provide a better way to manage the internal space issue?
I'm not very technical when it comes to these things, in fact, I had to pay someone to do a teamviewer session with me to guide me through doing the ROM etc in the first place so if I can avoid another ROM install, I'd prefer that.
Will changing the hboot (haven't a clue how to do that ) or following the guide in your sig coincide with 4.3, 4.4 or 4.9 do you think and if so, will completing the guide step by step mean no more space issues as long as I've free space on my SD card?
Click to expand...
Click to collapse
i'm also on V4.3, not upgraded because of reasons ZeGuitarist has stated, i would suggest trying to stick with it if you like the rom itself. the space issue is separate to the rom, and is because of two reasons:
- you're still on stock hboot. changing hboot allows repartitioning of internal space to use it more efficiently: currently on stock hboot your system size is 250MB, but the rom's system is only ~140MB, so you waste 110MB. this can be converted to extra data space by changing hboot to cm7r2. it's system is only 145MB, and you waste only say 5MB, and you get bigger 287MB data partition.
- you're using link2sd which you don't need to, the rom can use the ext partition by default.
what i would suggest
- backup all user apps (titanium), contacts (to google) and sms if you need to.
- nandroid backup so you have a safe point to return to
- s-off (use revolutionary, search for guides)
- change hboot to cm7r2, would recommend using fastboot (again search for guides)
- full wipe, reinstall rom
- enable applications on sd-ext by default here, do not use link2sd anymore
- restore apps
it assumes you have partitioned your sd card correctly using gparted or 4ext recovery, follow abaaaabbbb63's guide. you can check your space using apps like 'diskusage'.
this setup can have a lot more space for apps, you shouldn't have to manage your space issues on most roms as long as you know where and how things are stored before asking about "low memory"
eddiehk6 said:
i'm also on V4.3, not upgraded because of reasons ZeGuitarist has stated, i would suggest trying to stick with it if you like the rom itself. the space issue is separate to the rom, and is because of two reasons:
- you're still on stock hboot. changing hboot allows repartitioning of internal space to use it more efficiently: currently on stock hboot your system size is 250MB, but the rom's system is only ~140MB, so you waste 110MB. this can be converted to extra data space by changing hboot to cm7r2. it's system is only 145MB, and you waste only say 5MB, and you get bigger 287MB data partition.
- you're using link2sd which you don't need to, the rom can use the ext partition by default.
what i would suggest
- backup all user apps (titanium), contacts (to google) and sms if you need to.
- nandroid backup so you have a safe point to return to
- s-off (use revolutionary, search for guides)
- change hboot to cm7r2, would recommend using fastboot (again search for guides)
- full wipe, reinstall rom
- enable applications on sd-ext by default here, do not use link2sd anymore
- restore apps
it assumes you have partitioned your sd card correctly using gparted or 4ext recovery, follow abaaaabbbb63's guide. you can check your space using apps like 'diskusage'.
this setup can have a lot more space for apps, you shouldn't have to manage your space issues on most roms as long as you know where and how things are stored before asking about "low memory"
Click to expand...
Click to collapse
Hey,
Thanks a lot for that info, it looks like it's going to be a bit too complicated for me to do myself. I need the least amount of downtime on my phone as possible, but I've an android expert I can call on who can do these things over teamviewer so I'll see what he thinks and if he can do it.
So you're saying if I do the above, I can continue using 4.3 (or 4.4 I guess I may as well update to while I'm at it?) and should have a lot more recognised space to do for internal apps and the likes and then that's the most efficient way I can possibly make the most of the Desire?
I don't play games and I don't bother with any apps I don't have true long term use for, so hopefully if it's done right, that will be it!
cormie said:
Hey,
Thanks a lot for that info, it looks like it's going to be a bit too complicated for me to do myself. I need the least amount of downtime on my phone as possible, but I've an android expert I can call on who can do these things over teamviewer so I'll see what he thinks and if he can do it.
So you're saying if I do the above, I can continue using 4.3 (or 4.4 I guess I may as well update to while I'm at it?) and should have a lot more recognised space to do for internal apps and the likes and then that's the most efficient way I can possibly make the most of the Desire?
I don't play games and I don't bother with any apps I don't have true long term use for, so hopefully if it's done right, that will be it!
Click to expand...
Click to collapse
it's not that bad. there are guides for everything, most of us here have achieved everything by ourselves with no prior experience and without being android experts...
personally, i would recommend doing it yourself, that way you learn a bit too. much easier to work out for yourself if things go wrong. i would say that if you learnt how to do it in the first place, you'd understand the space issues a lot more.
but yes, this method just results in the same rom (or slightly upgraded one, think 4.4 had the same sd-ext settings, not sure), but with more efficient space layout for apps.
you could install 'diskusage' right now before you do anything, that will help the understanding of where your low space comes from. you'll see loads of free wasted space on /system
eddiehk6 said:
it's not that bad. there are guides for everything, most of us here have achieved everything by ourselves with no prior experience and without being android experts...
personally, i would recommend doing it yourself, that way you learn a bit too. much easier to work out for yourself if things go wrong. i would say that if you learnt how to do it in the first place, you'd understand the space issues a lot more.
but yes, this method just results in the same rom (or slightly upgraded one, think 4.4 had the same sd-ext settings, not sure), but with more efficient space layout for apps.
you could install 'diskusage' right now before you do anything, that will help the understanding of where your low space comes from. you'll see loads of free wasted space on /system
Click to expand...
Click to collapse
Thanks again for the feedback. Given the problems I've seen this guy face before when things don't go smoothly, I think I'd rather have him at hand. I'm pretty much watching what he does and doing the phone end of things so learn as I go along anyway. I popped him a link to your post #7 above when I saw it so I'll see what he says. I'm probably going to do 3 phones at once too as my friend and father are having space issues aswell so be well worth having an expert on hand!
Actually, any chance of a link to the correct 4.4 I should be going for?
I'll drop a link later, and add some more links to my personal recommended tweaks (like island3r's modded kernel so you can use smartassV2 governor, etc.). I'll update this post.
ZEDIT: Here's the links:
- MildWild-V 4.4: https://www.dropbox.com/s/1zu8dquw2echwhd/MildWild_V-4.4.zip
- Latest Thalamus kernel modded by island3r: http://forum.xda-developers.com/showthread.php?p=31096646&highlight=smartassv2#post31096646
- AGPS patch: https://www.dropbox.com/s/ggtgzme8bqscbq3/agps.patch.google.build.alt.v3.1.zip
- Stock bootanimation (don't flash this, manually put it in /data/local on your device's internal memory): https://www.dropbox.com/s/j3tek2gq9678lzk/bootanimation.zip
You're welcome.
Hit thanks pretty please?
Thanks a lot for that. I don't want to complicate things too much as I think I'll be doing this to 4 phones at the one time, my own, my friends, my fathers and a back up desire I have for business. What would the tweaks do exactly?
I heard back from my android expert anyway and he said the following:
To the best of my memory (And my chat records!), your phone is on the stock HBOOT with the standard partitioning. If you'd like to go all the way and repartition the phone and set up a stable ROM w/ Apps2SD and all the bells and whistles, it can definitely be done but everything will be brought back to a clean slate on all three phones (Including the contents of the SD Card) so they'll all need to be backed up.
Ideally, what we could do is...
Change the HBOOT to Cm7 R2 or Oxygen R2 (Which is a bit more lean and splits it 100MB system and 332MB data)
Flash the latest stable Cm7 or Oxygen based ROM depending on what you prefer
With clean and empty SD cards, we'll partition it for 1-2GB apps2SD and set up the ROM to use that space
Click to expand...
Click to collapse
So I guess I should stick to Oxygen for both the Hboot and the Rom? So Mildwild 4.4 and what about the Hboot? EDIT: Just saw that eddiehk6 suggested Cm7 R2, Which would be best in my situation I wonder?
Consdering I'm having space issues in the current set up, so applications > manage > all shows 129mb used, 20mb free, how much can I expect that to change by? It wouldn't be worth all the hassle on 4 phones if it's only going to make it an extra 50mb or so, will it completely change the way the space is handled and I should have no more space issues with moderate use until the phone packs in itself?
Post updated.
I'd recommend cm7r2 HBOOT. You can expect plenty of space for user apps, if you follow these steps:
- Flash the ROM (and, optionally, the mods I posted).
- Go into system settings > applications > development > check "sd-ext" and reboot. The ROM will mount and recognise your sd-ext partition from now on.
- Go back into system settings > applications > preferred install location. Select sd-ext and reboot.
- After reboot, you can reinstall all your apps. With the above settings, apps will be installed on sd-ext by default. You can change this for any separate app at any point should you wish, though (for example, I like to keep widget I'm using on internal memory). This is one of the advantages of roalex's Oxygen mod over standard Oxygen, btw.
If you need any more help, give me a shout. Cheers!
Thanks a lot for that and for all the links above too!! Very much appreciated, I'm not too tech as I said but I'll point the other guy to your posts and we'll hopefully get all the phones sorted to make the most of them and they'll be stable as possible until they compose
ZeGuitarist said:
Post updated.
I'd recommend cm7r2 HBOOT. You can expect plenty of space for user apps, if you follow these steps:
- Flash the ROM (and, optionally, the mods I posted).
- Go into system settings > applications > development > check "sd-ext" and reboot. The ROM will mount and recognise your sd-ext partition from now on.
- Go back into system settings > applications > preferred install location. Select sd-ext and reboot.
- After reboot, you can reinstall all your apps. With the above settings, apps will be installed on sd-ext by default. You can change this for any separate app at any point should you wish, though (for example, I like to keep widget I'm using on internal memory). This is one of the advantages of roalex's Oxygen mod over standard Oxygen, btw.
If you need any more help, give me a shout. Cheers!
Click to expand...
Click to collapse
Hi ZeGuitarist, is there anyway to port JB transition animations to MW4.4 Oxy? framework-res.apk ll do ?
Thanks
karthikus said:
Hi ZeGuitarist, is there anyway to port JB transition animations to MW4.4 Oxy? framework-res.apk ll do ?
Thanks
Click to expand...
Click to collapse
You can't simply use a JB framework-res.apk on a GB rom. Best you can do is manually replace the icons and stuff
karthikus reminded me of one thing actually, in the current bluetooth settings on mildwild 4.3, it's not possible to rename bluetooth devices but apparently in ICS and JB it is, is it possible to get this functionality while doing the updates without risking stability I wonder?
It doesn't exactly solve my problem I posted about here: http://www.boards.ie/vbulletin/showthread.php?p=83280543 but it may help..
abaaaabbbb63 said:
You can't simply use a JB framework-res.apk on a GB rom. Best you can do is manually replace the icons and stuff
Click to expand...
Click to collapse
How about replacing framework-res apk from latest MW Oxygen (which has JB animations) to the old version. Will it work coz they both have different base ?
I was telling my friend that I'd be able to help his memory issue and he said he found something that would give 2gb of internal memory, as opposed to the 332 or so I'd get from doing the methods above. It's described here: http://www.andreagrandi.it/2011/08/...emory-to-2gb-using-cyanogenmod-7-and-data2sd/
Does anyone know if this is indeed possible?
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