Related
New to the forum and spent all day looking for a fix and searched throughout the forum so posting here for a response. I've found the same question via other sites with it being the last comment with no answer.
My desire is rooted and has clockworkMod installed. Neither the redux-v1.0RC6 or AuraxTsesnse_8.4 roms will install either via clockworkmod recovery or the rom manager app.
I've been though the wiping of cache, data, dalvik and factory reset and makes no difference.
It goes to installing update and then E:\error in /sdcard/updateversionname.zip (status 0) Installation aborted.
I've seen it mentioned that the SD card needs to be formatted with FAT32, it already is.
Don't know where to go from here.
thanks in advance.
The SD acrd needs to have an EXT (3 or 4) partition too, at least 512 MB. Not just only FAT32.
I thought it odd that people were suggesting FAT32 for the SD card, I know linux / android cant read FAT32 preboot. Obviously windows needs FAT32 for getting stuff on and off the device.
Thanks a lot.
Well for stock Android it is FAT32 you need, but for custom ROMs with A2SD+ you need to have an EXT partition, as well. But this is written almost in every ROM's thread.
I copied data off my sd card, formatted with rom manager which created 512 mb ext file system and the rest fat32. Then copied all my data back to card.
Booted to clockwork, cleared cache and wiped data and tried to install again, no difference, same status 0 error.
Running nandroid restore for the umpteenth time today :-(
Strange, what ROM do you want to install? Filename? I never had status 0's...
ROM's from this forum:
AuraxTSense_8.4_Official_OTA_2.2_FRF91_A2SD+.zip
Redux-v1.0.0-RC6-signed.zip
Those should work, so can't understand. Disable signature verification, maybe that helps.
Also your phone is PVT4? MAybe that's the cause.
I'm running redux Rc6 rom.
I have clockworkmod 3.0 installed which i used to flash the zip, and I had already partitioned my SD card using gparted as it is the ONLY way I found to successfully partition it (750mb ext3 partition). Rom manager definitely did not work for me, don't use it!!
Hope this points you in the right direction, cost its an awesome rom!!
Wildcardspv
Sent from my HTC Desire using Tapatalk
@ nagypapi
I'm not familiar with what pvt4 is, a quick read through the forum mentions pvt3 & pvt4 desires. I haven't waded through the hundred page thread yet to find what this is and which applies to my device. It was a UK T-mobile device bought 2.5 months ago and I unlocked it from T mobile network and rooted it with unrevoked. Also signature verification on or off makes no difference.
@wildcardspv
Which would you recommend, the Froyo or Gingerbread ROM ? I read only 0.4% of Android users are running Gingerbread compared to 52% running Froyo. I'm inclined to try Froyo first as I would hope there would be fewer bugs and less likelihood of app related problems.
I'm actually pretty happy with 2.1, it does everything I need it to except it does not have Thai fonts installed and the hack looks like a headache. Can you confirm if Froyo or Gingerbread have Thai glyphs installed ?
I'm pretty sure my problem is SD card related as I couldn't install the droidsans Thai glyphs zip either. I'll give gparted a go and see how I get on.
Thanks to all for helpful responses.
Well, to check that, boot your phone into the bootloader, hold down power + volume down and you should get a screen like this.
If you have PVT4 with earsize 40000, you must flash the latest Amon RA instead of CWM.
Anyways what version of CWM are you using right now?
Moreover, using the Gparted method to partition your card is better than using ROM manager. Mount your card from recovery (mount & storage > mount usb storage). and try to partition with GParted.
Booted into HBOOT and doesn't mention anything about 3 or 4 version of PVT and nothing about earsize, it just says below:
BUZZ PVT SHIP S-ON
HBOOT-0.80.0007
MICROP-0622
TOUCH PANEL-ATMELC03_16ac
RADIO-3.35.19.01
Aug 9 2010
CWM is v2.5.0.1
Anyone know of any gparted live CD mirrors ? Taking forever to download from gparted site and it's not my connection.
I partitioned with gparted a 768 ext2 and the rest FAT32. It made no difference, same status zero on any ROM I try to install.
Sorry bump for some help..
Would really appreciate some help with this, surely I can't be stuck on 2.1 forever. It seems odd that I can back up and restore ROMS with ROM manager and clockwork pre-boot no problem. But I've no idea why I cant install any other ROM.
Just noticed... your radio is 3.35.19.01? Never seen that before... I've always seen Radios starting with 5.xxx
Also no PVT numbering (BUZZ PVT - never heard on the Desire - on Wildfire, yes)
Are you sure you have a HTC Desire? Because from those data I have to think , you have a WILDFIRE.
And the prize for the biggest idiot in the rooms goes to...
Thanks for pointing out my monster faux pas, lol.
No probs, happens sometimes, but I have to admit, it was a big one
Hey. I tried to install Marange MIUI, but got stuck on a boot-loop (HTC image was up for like 10 seconds, then the screen went black and repeated). So now I've restored my original ROM from a un-root .exe so it's like when I got it out of the box.
Now I want to give it another try, but want to know what I might have done wrong.
I downloaded the latest version of Marange MIUI, put the .zip on my SD card, made the partition in ext3 then installed MIUI through ClockworkRecovery. The installation went fine and when I re-booted my device it began the bootloop. I did wipe the cache and all that also, but it didn't work anyways. Also tried updating to the latest radio.
But now it's all back to square one, like when I bought it. Only thing I've done is to root it with unrevoked3.
Do I have to install anything special, like another ROM and then patch it with Marange MIUI?
Thankful for all help I can get, since I really want to run this ROM.
Also, sorry for noobing down this community.
The requirements are in the marange thread, right after the list of whats NOT working.
sCaos said:
Hey. I tried to install Marange MIUI, but got stuck on a boot-loop (HTC image was up for like 10 seconds, then the screen went black and repeated). So now I've restored my original ROM from a un-root .exe so it's like when I got it out of the box.
Now I want to give it another try, but want to know what I might have done wrong.
I downloaded the latest version of Marange MIUI, put the .zip on my SD card, made the partition in ext3 then installed MIUI through ClockworkRecovery. The installation went fine and when I re-booted my device it began the bootloop. I did wipe the cache and all that also, but it didn't work anyways. Also tried updating to the latest radio.
But now it's all back to square one, like when I bought it. Only thing I've done is to root it with unrevoked3.
Do I have to install anything special, like another ROM and then patch it with Marange MIUI?
Thankful for all help I can get, since I really want to run this ROM.
Also, sorry for noobing down this community.
Click to expand...
Click to collapse
Are you s-off? How did you make your ext partition?
Sent from my toaster
abaaaabbbb63 said:
Are you s-off? How did you make your ext partition?
Sent from my toaster
Click to expand...
Click to collapse
No, I'm s-on, according to HBOOT.
Well, first I formatted my SD-card through windows in FAT32. Then I downloaded MiniTool Partition Wizard and made a ~610MB partition in ext3 as a primary. It didn't have a driver letter on the partition, though. It's just called "*:" in MiniTool. Was I supposed to name the partition something, maybe?
If I need S-Off, how do I fix that?
sCaos said:
No, I'm s-on, according to HBOOT.
Well, first I formatted my SD-card through windows in FAT32. Then I downloaded MiniTool Partition Wizard and made a ~610MB partition in ext3 as a primary. It didn't have a driver letter on the partition, though. It's just called "*:" in MiniTool. Was I supposed to name the partition something, maybe?
If I need S-Off, how do I fix that?
Click to expand...
Click to collapse
It seems that whatever you used to partiton didn't do its job. S-off with revolutionary:
revolutionary.io
Then install 4ext recovery and partition your sd-card with it.
Use the PB99IMG method.
http://forum.xda-developers.com/showthread.php?t=1751258
Sent from my toaster
abaaaabbbb63 said:
It seems that whatever you used to partiton didn't do its job. S-off with revolutionary:
revolutionary.io
Then install 4ext recovery and partition your sd-card with it.
Use the PB99IMG method.
http://forum.xda-developers.com/showthread.php?t=1751258
Sent from my toaster
Click to expand...
Click to collapse
Thanks alot for the help! Ran into a bit of a problem with the 4ext recovery though. When I partitioned the SD-card, I then later was without any free space on my SD-card. It was like 172mb used and 0mb free. Why did it do that? I can't really set any size for my FAT32 partition, only the 1st and second sd-ext and for the swap files. Do I really need 2 sd-ext? Noticed that it says "skip" on the top when partitioning, if I skip like the 1st sd-ext, do I make room for the FAT32 partition?
When u partition ur sdcard with 4ext, it really depends on what rom u are installing coz some require different partition sizes but most roms require this so follow this -
Boot into recovery then choose
tools/partition sdcard
Remove all partitions and start from scratch
1024
Skip
Skip
Ext4
All done
Just be sure to check rom thread first for sizes, but 9 times out of 10 this is whats required.
Sent from my non - JB HTC Desire
jmcclue said:
When u partition ur sdcard with 4ext, it really depends on what rom u are installing coz some require different partition sizes but most roms require this so follow this -
Boot into recovery then choose
tools/partition sdcard
Remove all partitions and start from scratch
1024
Skip
Skip
Ext4
All done
Just be sure to check rom thread first for sizes, but 9 times out of 10 this is whats required.
Sent from my non - JB HTC Desire
Click to expand...
Click to collapse
Thanks mate
Tried that, but the screen has been stuck on the "MI xiaomi.com" screen for like a crapload of time. Way beyond 15 minutes.. Is it supposed to take this long? Never took more than 5 min with any other ROM :/
Dont think so, iv never used this rom. Did u do a full wipe before flashing? If it were me id boot recovery, goto
Wipe/format
Wipe dalvik
Wipe all partitions except sdcard
Then try reinstall the rom
Sent from my non - JB HTC Desire
Hey guys, as the title mentions, I've got my device almost up to speed. The trouble is, I can't seem to get it to partition properly. Or at all. I'm at 20mb of internal space left, and that's really hampering my ability to enjoy this otherwise fantastic phone.
I've tried Minitool Partition wizard, but my device thinks its corrupts my SD card. I've tried ROM manager (setting it to 512mb external and 0mb swap), but rom manager runs, reboots the phone, and nothing changes. Well. Mostly. I tested it out by installing a 10mb app from the store, but it used up the internal storage space, and disappeared! I can't find and uninstall it anymore! This is driving me absolutely crazy. I've lost so much time looking through forums and trying things out.
- uninstall rom manager
- do not use minitool partition wizard
- backup your sd card and use gparted to partition sd card, step 5 here. alternatively you can use 4ext recovery, easy to install as you are already s-off. copy everything back once partitioned.
you say you are 'hbooted', but have you actually changed your hboot to cm7r2, this will repartition your internal memory so you have more space. search for guides (how to change hboot...), recommend to do this through fastboot commands (again this is easy because you are already s-off).
once this is all set up (cm7r2 hboot and correctly partitioned sd card), you need to use a script or app to move the apps to the partition. i recommend something like s2e or link2sd.
for general reading, i recommend these set of guides.
Use 4ext recovery to partition SD, and get rid of ROM Manager.
Sent from my HTC Desire using xda premium
k3lcior said:
... and get rid of ROM Manager.
Click to expand...
Click to collapse
Curious to know why. I have never used ROM Manager but was going to...
murtuzasb said:
Curious to know why. I have never used ROM Manager but was going to...
Click to expand...
Click to collapse
it's not that it's a bad app, just particularly bad for htc desire. can screw things up. found out here, suroot is well respected and i trust his advice
plus you don't actually need to use rom manager...all the actions can be carried out within recovery anyway.
Hey Eddie, thanks for the info. I'll load up the Gparted this evening. Get this damn device running properly finally.
Once partitioned, I'm worried about this aforementioned missing facebook app. I don't care that it's not working, only that it's taking up unusable space. I'm down to 13mb of internal storage. After using Gparted to partition, would it be best for me to do a fresh install of CM7? And would that reset my root and S-off?
I'm also constantly getting confused about fastboot and hboot. Aren't they intrinsically linked? Actually, scratch that. What is fastboot, and how does it relate to hboot?
And why, when I tried to partition my card using clockwork recovery, did it update (and possibly replace) my recovery?
As for whether I have CM7 hboot set up, I'm honestly not sure. My hboot / fastboot window (the one that shows up after rebooting, with a white screen and 3 android on the bottom on skateboards, with the options for FASTBOOT/RECOVERY/CLEAR STORAGE/SIMLOCK?) is set to -REVOLUTIONARY-, HBOOT 6.93.1002. If that doesn't answer the question, how can I check if I have the CM7 hboot?
Thanks for the time, man. I appreciate you helping me understand how all this works! There was a time when I thought I was understanding the process. Then things stopped working. =p
Dysoncube said:
Hey Eddie, thanks for the info. I'll load up the Gparted this evening. Get this damn device running properly finally.
Once partitioned, I'm worried about this aforementioned missing facebook app. I don't care that it's not working, only that it's taking up unusable space. I'm down to 13mb of internal storage. After using Gparted to partition, would it be best for me to do a fresh install of CM7? And would that reset my root and S-off?
I'm also constantly getting confused about fastboot and hboot. Aren't they intrinsically linked? Actually, scratch that. What is fastboot, and how does it relate to hboot?
And why, when I tried to partition my card using clockwork recovery, did it update (and possibly replace) my recovery?
As for whether I have CM7 hboot set up, I'm honestly not sure. My hboot / fastboot window (the one that shows up after rebooting, with a white screen and 3 android on the bottom on skateboards, with the options for FASTBOOT/RECOVERY/CLEAR STORAGE/SIMLOCK?) is set to -REVOLUTIONARY-, HBOOT 6.93.1002. If that doesn't answer the question, how can I check if I have the CM7 hboot?
Thanks for the time, man. I appreciate you helping me understand how all this works! There was a time when I thought I was understanding the process. Then things stopped working. =p
Click to expand...
Click to collapse
There u go, technicial definitions: http://forum.xda-developers.com/showthread.php?t=805247
If u havent changed your Hboot since u s-offed then it should be stock.
Dysoncube said:
Hey Eddie, thanks for the info. I'll load up the Gparted this evening. Get this damn device running properly finally.
Once partitioned, I'm worried about this aforementioned missing facebook app. I don't care that it's not working, only that it's taking up unusable space. I'm down to 13mb of internal storage. After using Gparted to partition, would it be best for me to do a fresh install of CM7? And would that reset my root and S-off?
I'm also constantly getting confused about fastboot and hboot. Aren't they intrinsically linked? Actually, scratch that. What is fastboot, and how does it relate to hboot?
And why, when I tried to partition my card using clockwork recovery, did it update (and possibly replace) my recovery?
As for whether I have CM7 hboot set up, I'm honestly not sure. My hboot / fastboot window (the one that shows up after rebooting, with a white screen and 3 android on the bottom on skateboards, with the options for FASTBOOT/RECOVERY/CLEAR STORAGE/SIMLOCK?) is set to -REVOLUTIONARY-, HBOOT 6.93.1002. If that doesn't answer the question, how can I check if I have the CM7 hboot?
Thanks for the time, man. I appreciate you helping me understand how all this works! There was a time when I thought I was understanding the process. Then things stopped working. =p
Click to expand...
Click to collapse
take your time and read the guides i first linked you, and the one above to help with definitions.
minitool can go horribly wrong. clockworkmod recovery is also not very good at partitioning. gparted is always recommended.
you are currently on stock hboot because you haven't changed it. hboot just refers to the way all your internal memory partitions are laid out. in other words currently you have a 250MB system partition, but your cm7 rom system size is say 140MB (i.e. you're wasting 110MB)
when you change hboot to cm7r2, it has a 145MB system, so you waste say only 5MB. the extra reparitioned space becomes more internal memory (increases from 147MB to 287MB)
i say fastboot commands because that's just a method of actually changing your hboot.
so:
- use an app like titanium to backup all your apps. backup you contacts to gmail if you haven't already, use another app to backup sms if you need them too.
- backup your entire sd card to PC
- partition sd card, ~1gb ext4 should be enough, using the guide i linked.
- copy everything back to sd
- change hboot to cm7r2, search for guides (i recommend using fastboot commands)
- boot into recovery, nandroid backup
- full wipe and reinstall (you won't lose root or s-off)
- before you restore, install s2e or link2sd. select to move apps to sd-ext, keep app data and dalvik cache on internal (287MB should be enough space unless you have LOADS of apps), may need to reboot afterwards.
- restore everything else.
- i recommend to use another app like 'diskusage' to check all your partitions are working correctly.
seems like a faff, but this should have been the way to set it up in the first place
So, things went well, thanks to you guys.
I had already paritioned using minitool partition wizard. Gparted would NOT work for me, so I gave the minitool partition another shot. Installed the CM7 HBoot, wiped everything, reinstalled CM7 (since I was getting a bootloop problem), now everything seems to be running fine. Android detects 280mb of internal storage. I installed a 40mb app, transferred it to the SD card, and it's working beautifully. Im pretty darn happy with how things have turned out. Are there any other things I should verify, to make sure everything installed alright?
it wont boot coz u partitioned ur sdcard and changed hboots. so because u didnt do a backup u will have to flash the CM7 rom again. put CM7 rom on ur sdcard, boot into recovery, full wipe and flash the rom
Sent from my HTC Desire
Dysoncube said:
So, things went well, thanks to you guys.
I had already paritioned using minitool partition wizard. Gparted would NOT work for me, so I gave the minitool partition another shot. Installed the CM7 HBoot, wiped everything, reinstalled CM7 (since I was getting a bootloop problem), now everything seems to be running fine. Android detects 280mb of internal storage. I installed a 40mb app, transferred it to the SD card, and it's working beautifully. Im pretty darn happy with how things have turned out. Are there any other things I should verify, to make sure everything installed alright?
Click to expand...
Click to collapse
gparted should always work if done correctly, what exactly would not work? if repartitioning using gparted, delete all existing partitions and start from scratch. as per guide, FAT32 should be first (on the left), ext4 partition second, both labelled as primary.
if minitool worked then you got lucky (many cases including myself in early days when it just screwed things up), i'd still recommend giving gparted another go.
when you say transferred to sd card, are you manually moving apps to sd using 'move to SD' within settings? if so then you're actually moving them to FAT32 partition of sd card, and not the ext4 partition...
follow what i said before, use an app (easiest) or script to move apps to sd-ext. if done correctly you shouldnt have to move any apps to sd, keeing them on should internal 'trick' them to sd-ext, it moves all of the app (and can move widgets too). and like i said, another app like 'diskusage' you can actually see your sd-ext filling up if setup correctly.
[you successfully changed hboots which is good! :victory:]
Hallo everyone
I just got a brand new class 10, 32GB SDHC card, a great upgrade from my previous 4GB. Instead trying to do a complicated move over, or should I say upgrade, I choose to simply start from scratch with my new favorite Desire Rom: http://forum.xda-developers.com/showthread.php?t=2070704
I pop in my new card, boot into 4EXT Recovery Touch (1.0.0.5RC9), format and partition the sdcard 1024MB for EXT/rest for fat32. I toggle the usb, copy over CM10.1_VJ_4.2.2_V6.2.zip and try to install it, but I get the following error:
Formatting System....
Installing Cm10.1 VJ
Creating symlinks
Setting Permissions
set_perm: some changes failed
E:Error in /sdcard/CM10.1_VJ_4.2.2_V6.2.zip
(status 7)
Installation aborted.
If I try with the older version: CM10.1_VJ_4.2.2_V6.0_Sense_Data++, I get this:
Opening update packge...
E:can't open /sdcard/CM10.1_VJ_4.2.2_V6.0_Data++.zip
(bad)
Installation aborted
If I try to install the ROM on my old 4GB, then it works without anyway problems. I have no idea why, or what am I doing wrong. I have been installing lots of roms, and I've never encouraged this problem before. What am I doing wrong?
If I then take out the 4GB stick, and do my first time boot with the 32GB card, then it seems to work! But this doesn't seem like a good solution (this is just my bad guesswork though)?
You may have bought a faulty sd-card. Hope it has warranty.
abaaaabbbb63 said:
You may have bought a faulty sd-card. Hope it has warranty.
Click to expand...
Click to collapse
Bah :/ I have 14 days return. Is there a test that I can run to check for faults?
Couldn't I just first time boot with the 32GB card? What are the negative consequences (if any)?
decon89 said:
Bah :/ I have 14 days return. Is there a test that I can run to check for faults?
Couldn't I just first time boot with the 32GB card? What are the negative consequences (if any)?
Click to expand...
Click to collapse
Erase your ext partition, then try to install a ROM again. If it does the same thing, then it's the sd-card's fault.
First time boot doesn't help if you'll lose data from your sd-card being faulty.
abaaaabbbb63 said:
Erase your ext partition, then try to install a ROM again. If it does the same thing, then it's the sd-card's fault.
First time boot doesn't help if you'll lose data from your sd-card being faulty.
Click to expand...
Click to collapse
I had this problem too, but I found out that since I changed my HBoot to one provided by jmcclue, and I was using that for such a long time that I had forgotten to flash the stock one back, this message came up. I think the problem's with the HBoot with this guy too, because when I reverted to stock Hboot, it all installed fine...
And BTW, who uses a *Recovery* to prepare the SDCard when they have a PC at hand and if he had a faulty card, how could he copy those ROMs???
dock ntsrrui
alicarbovader said:
I had this problem too, but I found out that since I changed my HBoot to one provided by jmcclue, and I was using that for such a long time that I had forgotten to flash the stock one back, this message came up. I think the problem's with the HBoot with this guy too, because when I reverted to stock Hboot, it all installed fine...
And BTW, who uses a *Recovery* to prepare the SDCard when they have a PC at hand and if he had a faulty card, how could he copy those ROMs???
Click to expand...
Click to collapse
Right. Should I just follow point 14 in this guide? http://forum.xda-developers.com/showthread.php?t=1275632
Sorry if this is an obvious question, but I bought my Desire used with S-off/rooted already fixed for me
decon89 said:
Right. Should I just follow point 14 in this guide? http://forum.xda-developers.com/showthread.php?t=1275632
Sorry if this is an obvious question, but I bought my Desire used with S-off/rooted already fixed for me
Click to expand...
Click to collapse
You're lucky then If you're already rooted and (Pis)S-Off'd, then no need for that, but you can always have a quick peak at that tutorial just to see how things work....! Welcome to the rooted world
I switched back to the stock hboot and downloaded the stock hboot version of the ROM. I'm now able to install the rom, but when I try to run a2sd install I get this error:
/sd-ext not mounted properly, it might have errors
Found Block device. /dev/mmcblk0p2
removing flags...
Is this just another sign of a broken sdcard?
Hi I've downgraded HBOOT to s-off (also giving new HBOOT), flashed new HBOOT compatible with all roms and flashed roms o plenty on my desire s (saga) but my desire (bravo) has been a little more complicated to say the least!
The roms for the desire 1 all go on about having xxx Mb HBOOT and all the various partition sizes needed, nether of these seem to apply on the desire s and dispute having read guides over and over, I cant seem to get the partitions right (1.5mb main mem left after clean rom flash) im wondering if its to do with the hboot instead.
Before AND after partitioning the device, the gingerbread rom iused to get from hboot 1.03 to one compatible with revolutionary works fine, I am currently on the HBOOT version revolutionary planted on the phone ( HBOOT-6.93.1002, RADIO-5.17.05.23 )
The custom rom I tried booted a couple of times but as I said, with only 1.5mb of mem left and lagged like a Pentium 4 pc trying to play battlefield 4 lol.
That rom has not booted since but restoring via recovery to the gingerbread rom, all works fine.
The custom rom I installed was omni-4.4.2-20140518-bravo-homemade, i want to try others but this was just a starting ground.
Please can someone point me in the right direction, as i said, I've followed guides for partitioning the SD card and I've gone wrong somewhere and can't figure out what.
Thanks Steve.
steve_htc_wizard said:
Hi I've downgraded HBOOT to s-off (also giving new HBOOT), flashed new HBOOT compatible with all roms and flashed roms o plenty on my desire s (saga) but my desire (bravo) has been a little more complicated to say the least!
The roms for the desire 1 all go on about having xxx Mb HBOOT and all the various partition sizes needed, nether of these seem to apply on the desire s and dispute having read guides over and over, I cant seem to get the partitions right (1.5mb main mem left after clean rom flash) im wondering if its to do with the hboot instead.
Before AND after partitioning the device, the gingerbread rom iused to get from hboot 1.03 to one compatible with revolutionary works fine, I am currently on the HBOOT version revolutionary planted on the phone ( HBOOT-6.93.1002, RADIO-5.17.05.23 )
The custom rom I tried booted a couple of times but as I said, with only 1.5mb of mem left and lagged like a Pentium 4 pc trying to play battlefield 4 lol.
That rom has not booted since but restoring via recovery to the gingerbread rom, all works fine.
The custom rom I installed was omni-4.4.2-20140518-bravo-homemade, i want to try others but this was just a starting ground.
Please can someone point me in the right direction, as i said, I've followed guides for partitioning the SD card and I've gone wrong somewhere and can't figure out what.
Thanks Steve.
Click to expand...
Click to collapse
How much size partition have u made?
Sent from my HTC Desire using XDA Free mobile app
So the initial 'hboots' you have been seeing are merely version numbers relating to official ROMs
e.g.
0.93 is for a Froyo ROM
1.02 is for the Gingerbread ROM
1.03 is HTC dev unlocked ROM I believe
Your version number now doesn't really mean much, but the fact that you are S-OFF now means you can change your hboot. When custom ROMs refer to hboots in this sense, they are merely talking about your internal nand partition sizes.
So going back to before you gained s-off, you were on stock hboot, with the following sizes:
250MB /system
40MB /cache
147MB /data
You are still technically on stock hboot, so your sizes internal nand memory still looks like this. The /data partition is your internal memory, which as you can see is tiny.
S-OFF gained the ability to change your hboot if you so wish. You can find the different hboot partition tables at alpharev.nl. You can flash a different hboot with both smaller /system and /cache sizes, hence much larger /data (internal memory) using fastboot. More /data = more internal memory = more space for apps :good:
You need to flash a compatible custom ROM with a /system size just smaller than the corresponding hboot to optimise your space.
So for instance, cm7r2 hboot has a /system size of 145MB. You need to flash a ROM with say a 140MB extracted system size to fit (it will usually just say in the first post).
Some ROMs will still only fit into stock hboot, but you can still gain space by A2SD whereby apps are moved to the sd-ext partition. You may have to manually activate it, instructions are normally given in each ROM thread.
You also need a correctly partitioned sd card (using 4EXT recovery or gparted only) along with the custom ROM to optimise app space. Which guide did you use? And how big is your partition?
lilsafbig said:
How much size partition have u made?
Sent from my HTC Desire using XDA Free mobile app
Click to expand...
Click to collapse
these are the stats quoted in the info page of 4EXT RECOVERY-
SYSTEM- mtd3 250mb- 14.2mb free
DATA- mtd5 147mb-100.9 free
CACHE- mtd4 40mb- 33.4mb free
SDCARD- fat32 6.4gb-5.6gb free
SD-ext- ext4 513mb-487.9 free
SWAP- swap 513mb - -
eddiehk6 said:
So the initial 'hboots' you have been seeing are merely version numbers relating to official ROMs
e.g.
0.93 is for a Froyo ROM
1.02 is for the Gingerbread ROM
1.03 is HTC dev unlocked ROM I believe
Your version number now doesn't really mean much, but the fact that you are S-OFF now means you can change your hboot. When custom ROMs refer to hboots in this sense, they are merely talking about your internal nand partition sizes.
So going back to before you gained s-off, you were on stock hboot, with the following sizes:
250MB /system
40MB /cache
147MB /data
You are still technically on stock hboot, so your sizes internal nand memory still looks like this. The /data partition is your internal memory, which as you can see is tiny.
S-OFF gained the ability to change your hboot if you so wish. You can find the different hboot partition tables at alpharev.nl. You can flash a different hboot with both smaller /system and /cache sizes, hence much larger /data (internal memory) using fastboot. More /data = more internal memory = more space for apps :good:
You need to flash a compatible custom ROM with a /system size just smaller than the corresponding hboot to optimise your space.
So for instance, cm7r2 hboot has a /system size of 145MB. You need to flash a ROM with say a 140MB extracted system size to fit (it will usually just say in the first post).
Some ROMs will still only fit into stock hboot, but you can still gain space by A2SD whereby apps are moved to the sd-ext partition. You may have to manually activate it, instructions are normally given in each ROM thread.
You also need a correctly partitioned sd card (using 4EXT recovery or gparted only) along with the custom ROM to optimise app space. Which guide did you use? And how big is your partition?
Click to expand...
Click to collapse
you posted this as I was leaving my last post so I did not see it till I posted my partition info, I can't remember off the top of my head what the guide was called but will try and find it and post the link, what you have written has explained a lot and it very very helpfull thankyou for your detailed post, I will get back to you when I have had a chance to read over it again and have a play, the misses is watching a film with me at the moment and I can't mess with the phone till its finished of im in trouble lol
steve_htc_wizard said:
these are the stats quoted in the info page of 4EXT RECOVERY-
SYSTEM- mtd3 250mb- 14.2mb free
DATA- mtd5 147mb-100.9 free
CACHE- mtd4 40mb- 33.4mb free
SDCARD- fat32 6.4gb-5.6gb free
SD-ext- ext4 513mb-487.9 free
SWAP- swap 513mb - -
Click to expand...
Click to collapse
You should have made atleast 1gb partition because them apps will fill up quickly and there's no need for a swap partition.
Sent from my HTC Desire using XDA Free mobile app
eddiehk6 said:
Which guide did you use? And how big is your partition?
Click to expand...
Click to collapse
Ok,found the guide this is what I followed.
http://forum.xda-developers.com/showthread.php?t=2125513
I think it must be the hboot that's the issue but can't look into it properly yet
Thanks again and I will report back
steve_htc_wizard said:
you posted this as I was leaving my last post so I did not see it till I posted my partition info, I can't remember off the top of my head what the guide was called but will try and find it and post the link, what you have written has explained a lot and it very very helpfull thankyou for your detailed post, I will get back to you when I have had a chance to read over it again and have a play, the misses is watching a film with me at the moment and I can't mess with the phone till its finished of im in trouble lol
Click to expand...
Click to collapse
Lol no matter how addictive these forums can be...the misses always takes priority...always
As above, @lilsafbig is correct
lilsafbig said:
You should have made atleast 1gb partition because them apps will fill up quickly and there's no need for a swap partition.
Sent from my HTC Desire using XDA Free mobile app
Click to expand...
Click to collapse
Did not see your post till after my last again, will def make it 1gb or bigger when I re partition it, misses is tired and has abandoned film, yay!
I will get playing around and reading everything you have all written again so im clear son things, I appreciate your help everyong and will post back when ive made some changes.
Steve.
re formatted the sd card how advised to, flashed rom and nothing, re wiped, installed the hboot sugeseted on the roms page but still nothing, just stuck on the htc splash.
Installed a ics rom and everything is working great, the other has issues with this phone lol
Which method did you use to partition, 4ext recovery or gparted?
Stock hboot or the Alpha Jelly hboot will work, as both have 250MB /system size. Are you using fastboot to flash them?
How are you performing the wipe before installation? 'wipe all partitions except sdcard' option within 4ext should be sufficient.
eddiehk6 said:
Which method did you use to partition, 4ext recovery or gparted?
Stock hboot or the Alpha Jelly hboot will work, as both have 250MB /system size. Are you using fastboot to flash them?
How are you performing the wipe before installation? 'wipe all partitions except sdcard' option within 4ext should be sufficient.
Click to expand...
Click to collapse
yes im using the PB99IMG method for flashing them, I partitioned using 4EXT.
I realised stock shouldent be a problem by the numbers explained to me but thought it couldent do any harm to flash a specific hboot reccomended by the rom cheff, it also slightly changed the install process for some reason if you were running a hboot other than it so I shought in the name of compatibility I would give it a try but nope lol, HTC slash screen again ha ha.
I will try another 4.4 rom to see what happen but it is a little strange as it did boot and run poorly before
All the help I have had on thhis topic has been great and has really helped me, I hope someone else who is confused see this and is helpers also
How are you performing the wipe before installation? 'wipe all partitions except sdcard' option within 4ext should be sufficient.
Click to expand...
Click to collapse
You may have corrupted the ROM.zip download. Try again, and verify the md5 sum if it has one.
You may need to activate a2sd first then flash the gapps package straight after, check instructions
Like you said, if that still doesn't work, get any ROM booting as a first step (along with corresponding hboot beforehand if you want to optimise space).