Tried to install the RCMixHD v0.13 rom today and the installation fails. I get:
-- Installing:SDCARD:RCMixHD_v013 .zip
Finding update package...
Opening update package...
Installing update...
Formatting CACHE:...
Formatting SYSTEM:...
Deleting files...
E:Can't mount /dev/block/mmcb1k0p2
(File exists)
Deleting files...
Deleting files...
Copying files...
E:Can't mount /dev/block/mmcb1k0p2
(File exists)
E:Can't mount SDEXT:
E:Failure at line 11:
copy_dir PACKAGE:data SDEXT:
Installation aborted.
Click to expand...
Click to collapse
Is this me doing it wrong or is there some bug? I'm able to install roms just not this one.
EDIT: i've tried the desireZ rom aswell and that failed. I also noticed the line "E:Can't mount SDEXT:" and tried an sd card with an ext3 partition but it then failed to mount the fat32 (/sdcard) partition but was able to mount the ext partiton (/sd-ext). From what I've been reading its because it doesn't have an ext partition, but as I said when I do it then doesn't mount the non-ext partition.
I too was having similar issues and found that re-partitioning and formatting the card did the trick. Also I had a 700mb partition before which I have increased to 1gb.
Phil
Had the same problem myself.I ended up putting a stock rom on to access market place, installed rom manager which I partitioned with then ran hd rom and it worked.Only problem I have now is its stuck in a boot loop lol and not sure how to fix it but hey good luck.
Cool. Got it to work, using stigslim's method of using ROM manager had a slight issue with it saying the Rom wasn't signed but I turned off the verification then it worked fine. No boot loop.did use the wrong SD card though. *Facepalm*
thanks
Can you tell me what procedure you went through in recovery, if I follow your tracks I might get rid of the restart problem I have.cheers
pnw said:
Cool. Got it to work, using stigslim's method of using ROM manager had a slight issue with it saying the Rom wasn't signed but I turned off the verification then it worked fine. No boot loop.did use the wrong SD card though. *Facepalm*
thanks
Click to expand...
Click to collapse
what did u do ?
Exact same error as I got yesterday.. had to restore my sd card and restore to previous state. I assume there's something causing this rom to fail.
Using CWM 5.0.2.0, when I try to format /data, I get:
Error formatting /data!
When I try to format /cache, I get:
Error formatting /cache!
This all started because I decided to try Albinoman's AOSP 4.2 ROM. This is what happened:
1. Booted into CWM 5.0.2.0, made a nandroid backup of stock GB ROM.
2. Installed Albinoman's ROM using CWM, wiped /cache and /data.
3. Booted Albinoman's ROM, no problems. Decided I wanted to backup and restore some apps in the old ROM using Titanium Backup.
4. Restored nandroid backup of stock ROM. When it rebooted, all was well.
5. Used Titanium Backup to back up my apps.
6. Installed Albinoman's ROM again.
7. Cleared /data, it was fine. Cleared /cache. Stuck at "formatting" for half an hour.
8. Rebooted back to recovery and tried it again. Couldn't find E:.
9. Tried letting it boot. Stuck on the boot animation for 30-minutes.
10. Wipe everything and re-flash. Tried again. Still stuck on boot animation.
11. Manually unmount and tried to format /data and /cache, and I get the error messages.
I had installed Convert2Ext4_no_data_limit_normal_dalvik.zip to the stock ROM about 4-months ago, not sure if that makes a difference or not.
When I search, it looks like the news is bad... most people that had this error gave up and believed it to be hardware NAND failure. Anything I can do to confirm or rule out NAND failure?
UPDATE: Managed to flash RUU, but results were interesting. It worked and it boots, home screen is blank (no HTC widgets), and apps I'd installed are still there. Clear Storage and Factory Reset does not get rid of them! I can manually uninstall apps, but when I reboot, they come back. I guess the /data must be stuck in some kind of read-only state.
GnatGoSplat said:
Using CWM 5.0.2.0, when I try to format /data, I get:
Error formatting /data!
When I try to format /cache, I get:
Error formatting /cache!
This all started because I decided to try Albinoman's AOSP 4.2 ROM. This is what happened:
1. Booted into CWM 5.0.2.0, made a nandroid backup of stock GB ROM.
2. Installed Albinoman's ROM using CWM, wiped /cache and /data.
3. Booted Albinoman's ROM, no problems. Decided I wanted to backup and restore some apps in the old ROM using Titanium Backup.
4. Restored nandroid backup of stock ROM. When it rebooted, all was well.
5. Used Titanium Backup to back up my apps.
6. Installed Albinoman's ROM again.
7. Cleared /data, it was fine. Cleared /cache. Stuck at "formatting" for half an hour.
8. Rebooted back to recovery and tried it again. Couldn't find E:.
9. Tried letting it boot. Stuck on the boot animation for 30-minutes.
10. Wipe everything and re-flash. Tried again. Still stuck on boot animation.
11. Manually unmount and tried to format /data and /cache, and I get the error messages.
I had installed Convert2Ext4_no_data_limit_normal_dalvik.zip to the stock ROM about 4-months ago, not sure if that makes a difference or not.
When I search, it looks like the news is bad... most people that had this error gave up and believed it to be hardware NAND failure. Anything I can do to confirm or rule out NAND failure?
UPDATE: Managed to flash RUU, but results were interesting. It worked and it boots, home screen is blank (no HTC widgets), and apps I'd installed are still there. Clear Storage and Factory Reset does not get rid of them! I can manually uninstall apps, but when I reboot, they come back. I guess the /data must be stuck in some kind of read-only state.
Click to expand...
Click to collapse
Did you reflash the Convert2Ext4 mod after you flashed the new rom? See this thread and read the top part after 'IMPORTANT:' There is a link in there to the old thread as well with a lot of info.
I did try that, but my /data and /cache are still unable to be written to, wiped, or formatted.
e2fsck won't touch /data, it has a superblock error. It finds errors on /cache and appears to be fixing them, but when I re-run it, the same errors are still there.
GnatGoSplat said:
I did try that, but my /data and /cache are still unable to be written to, wiped, or formatted.
e2fsck won't touch /data, it has a superblock error. It finds errors on /cache and appears to be fixing them, but when I re-run it, the same errors are still there.
Click to expand...
Click to collapse
Since you flashed the RUU, did you install an EXT4 compatible kernel or are you using the stock kernel? Maybe try restoring your working nandroid backup, then run the .zip to revert Convert2Ext4. Or even better, if you have a nandroid from before you installed the EXT4 mod.
DaggerDave said:
Since you flashed the RUU, did you install an EXT4 compatible kernel or are you using the stock kernel? Maybe try restoring your working nandroid backup, then run the .zip to revert Convert2Ext4. Or even better, if you have a nandroid from before you installed the EXT4 mod.
Click to expand...
Click to collapse
Wiping /data and /cache are enough to revert the mod.
Sent from my Galaxy Nexus using Tapatalk 2
Uggh, definitely doesn't sound so good. Since the RUU won't work, I'd say check out this thread:
http://forum.xda-developers.com/showthread.php?t=2123966
Yep, my partitions are no longer EXT4. #1 is EXT3 and #2 is EXT2. I guess that means Convert2Ext4 is no longer in play and the problem is unrelated.
Here is my parted:
Code:
parted /dev/block/mmcblk0 print
Model: MMC SEM08G (sd/mmc)
Disk /dev/block/mmcblk0: 7944MB
Sector size (logical/physical): 512B/512B
Partition Table: msdos
Number Start End Size Type File system Flags
1 8192B 797MB 797MB primary ext3
2 797MB 1007MB 210MB primary ext2
3 1007MB 7944MB 6937MB primary fat32 lba
Yeah, I read that thread and it didn't sound encouraging! I get pretty much the same errors.
Even rm 1 and rm 2 don't remove the partitions. It's like they're read-only. I'm using the parted from CWM 5.0.2.0. Should I use a different one?
Also when I try e2fsck on it:
Code:
~ # e2fsck -pf /dev/block/mmcblk0p1
e2fsck -pf /dev/block/mmcblk0p1
/dev/block/mmcblk0p1: recovering journal
e2fsck: unable to set superblock flags on /dev/block/mmcblk0p1
~ # e2fsck -pf /dev/block/mmcblk0p2
e2fsck -pf /dev/block/mmcblk0p2
/dev/block/mmcblk0p2: Unconnected directory inode 34817 (/???)
/dev/block/mmcblk0p2: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY.
(i.e., without -a or -p options)
~ # e2fsck -f /dev/block/mmcblk0p2
e2fsck -f /dev/block/mmcblk0p2
e2fsck 1.41.6 (30-May-2009)
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Unconnected directory inode 34817 (/???)
Connect to /lost+found<y>? y
yes
Pass 4: Checking reference counts
Inode 2 ref count is 2, should be 3. Fix<y>? yes
Inode 34817 ref count is 3, should be 2. Fix<y>? y
yes
Pass 5: Checking group summary information
Block bitmap differences: +274 +(449--510) +(645--701) -(139524--139541) -(139
85--139800)
Fix<y>? yes
Free blocks count wrong for group #0 (7919, counted=7799).
Fix<y>? y
yes
Free blocks count wrong for group #17 (7934, counted=7929).
Fix<y>? yes
Free blocks count wrong (198324, counted=198199).
Fix<y>? y
yes
Free inodes count wrong for group #17 (2048, counted=2045).
Fix<y>? yes
Directories count wrong for group #17 (0, counted=1).
Fix<y>? y
yes
Free inodes count wrong (51189, counted=51186).
Fix<y>? yes
/dev/block/mmcblk0p2: ***** FILE SYSTEM WAS MODIFIED *****
/dev/block/mmcblk0p2: 14/51200 files (14.3% non-contiguous), 6601/204800 blocks
When I tried it without the -p is when it looks above like it's fixing something, but it really didn't fix anything because it does the same thing when I try e2fsck again (as if it's read-only).
Is MMCBLK0 one physical NAND chip? If so, how come I can read/write/erase the /emmc with no problems? Isn't that just another partition on the same NAND disk?
If /data and /cache are really bad, is there any possible way to do an equivalent of a low-level format on the NAND and repartition?
Is booting CWM 5.0.2.0 and using adb shell supposed to have root privileges?
I can't modify the partition table using either parted or fdisk. I even tried zeroing the partitions using dd if=/dev/zero of=/dev/block/mmcblk0p1, p2, and even the whole of mmcblk0, but nothing actually gets written.
Since it seems like the NAND is probably irreparably borked, can I approach this problem from a different angle?
Can I partition my sdcard with an ext3 and ext2 partition, and tell Android to use those as /data and /cache respectively?
What in Android maps /dev/block/mmcblk0p1 to /data and /dev/block/mmcblk0p2 to /cache, and can I change those to point to partitions on sdcard?
Or is that hard-coded into the kernel?
GnatGoSplat said:
Since it seems like the NAND is probably irreparably borked, can I approach this problem from a different angle?
Can I partition my sdcard with an ext3 and ext2 partition, and tell Android to use those as /data and /cache respectively?
What in Android maps /dev/block/mmcblk0p1 to /data and /dev/block/mmcblk0p2 to /cache, and can I change those to point to partitions on sdcard?
Or is that hard-coded into the kernel?
Click to expand...
Click to collapse
It is hard coded into the kernel. To get root in adbshell try typimg su. This seems to be happening to more and more people as these phones get up there in age.
GnatGoSplat said:
Since it seems like the NAND is probably irreparably borked, can I approach this problem from a different angle?
Can I partition my sdcard with an ext3 and ext2 partition, and tell Android to use those as /data and /cache respectively?
What in Android maps /dev/block/mmcblk0p1 to /data and /dev/block/mmcblk0p2 to /cache, and can I change those to point to partitions on sdcard?
Or is that hard-coded into the kernel?
Click to expand...
Click to collapse
The answer is yes to both actually. Thrle boot.img would need to be customized. The best way is a flashable zip in recovery. Data and cache would need to be wiped manually ad recovery will not pick this up. Expect poorer performance though as SD cards tend to be slower than built in storage.
Sent from my Galaxy Nexus using Tapatalk 2
Thanks! So it sounds like the way to make this work is to compile a custom kernel? I don't know the first thing about it, but I think I could learn.
This is only in the kernel, so I could flash any 3rd party D-Inc ROM and just flash my customized kernel and it will see /data and /cache on the sdcard?
I could probably get one of those fast Class 10 cards if it turns out this is too slow, but I do recall changing vold.fstab once to fool Android into seeing /emmc as /sdcard and the /emmc (as /sdcard) didn't benchmark all that much faster than a real sdcard. I'm assuming /data and /cache are the same speed as /emmc since they're on the same mmcblk0 device, so I'm thinking maybe sdcard performance would be acceptable.
This actually sounds like it could be a better long-term solution than replacing the motherboard because no telling if a new motherboard will fail soon too.
The motherboard should be reliable. Emmc may die. Especially considering how old current dincs are.
I was talking about the boot.img which is not ROM independent and kernels aren't always either. Best idea is a flashable zip to modify the ram disk but I need the partition names if you decide to do it. I recommend keeping cache and data in the same order.
Also there would need to be a flashable wipe script to wipe data and cache.
Sent from my Galaxy Nexus using Tapatalk 2
Sorry, I wasn't very clear. By motherboard failing, I was assuming NAND is soldered to the motherboard, and if that's the case, ruined NAND = ruined motherboard. I had thought maybe I could buy a DInc with smashed LCD and good motherboard and just swap into mine (because mine is MINT condition), but I thought if I do that, I could very well end up in the same place as I'm in now and using sdcard would be more of a guarantee I wouldn't have to worry about this again.
I think I understand, the boot.img and kernel aren't exactly the same thing, but the kernel is part of boot.img? Or is it only the RAMDisk that needs changed, or both? You mentioned partition names, are you offering to make these modifications for me?
By same order, do you mean because mmcblk0p1 is /data, mmcblk0p2 is /cache, and mmcblkp3 is /emmc, I should partition my sdcard the same way with data 1st, cache 2nd, and sdcard 3rd?
Should I partition it with the phone, PC, or does it matter? Should the sizes of the new /data and /cache be the same size as original, or is there any reason I should make them larger?
Could I wipe the new /data and /cache simply by booting into Recovery and using adb shell and format them?
Also, the commands I was issuing in adb shell were from booting into CWM Recovery. Is it possible that mode can't write because I didn't login as root using the su command? I hadn't thought that would be the problem seeing as how the RUU and Android itself can't write to /data and /cache and other people managed to fix partition problems without needing to run su.
GnatGoSplat said:
Sorry, I wasn't very clear. By motherboard failing, I was assuming NAND is soldered to the motherboard, and if that's the case, ruined NAND = ruined motherboard. I had thought maybe I could buy a DInc with smashed LCD and good motherboard and just swap into mine (because mine is MINT condition), but I thought if I do that, I could very well end up in the same place as I'm in now and using sdcard would be more of a guarantee I wouldn't have to worry about this again.
I think I understand, the boot.img and kernel aren't exactly the same thing, but the kernel is part of boot.img? Or is it only the RAMDisk that needs changed, or both? You mentioned partition names, are you offering to make these modifications for me?
By same order, do you mean because mmcblk0p1 is /data, mmcblk0p2 is /cache, and mmcblkp3 is /emmc, I should partition my sdcard the same way with data 1st, cache 2nd, and sdcard 3rd?
Should I partition it with the phone, PC, or does it matter? Should the sizes of the new /data and /cache be the same size as original, or is there any reason I should make them larger?
Could I wipe the new /data and /cache simply by booting into Recovery and using adb shell and format them?
Also, the commands I was issuing in adb shell were from booting into CWM Recovery. Is it possible that mode can't write because I didn't login as root using the su command? I hadn't thought that would be the problem seeing as how the RUU and Android itself can't write to /data and /cache and other people managed to fix partition problems without needing to run su.
Click to expand...
Click to collapse
The NAND is likely soldered to the motherboard, so you're right about that.
To answer your first question, yeah, the kernel is part of the boot.img. The other part is the RAMdisk which is the only thing that needs to be changed.
Partition it in the same order. Probably parted via adb shell. 100MB for cache and at least 750MB for data. Sizes don't matter too much but you want enough.
adb shell has root access automatically in recovery. The issue is hardware most likely so your proposed workaround may be the only option.
First plan of attack is to find the partition names which would be mmcblk1p1 and mmcblk1p1 if you partition the sdcard the same way as the ROM is partitioned. Ideally you need to be able to fix the partitions themselves. I'll try to give more info later.
I copied the partition sizes from mmcblk0, so here's what I have on my 16GB SD card:
Code:
Model: SD SA16G (sd/mmc)
Disk /dev/block/mmcblk1: 16.0GB
Sector size (logical/physical): 512B/512B
Partition Table: msdos
Number Start End Size Type File system Flags
1 8192B 797MB 797MB primary ext2
2 797MB 1007MB 210MB primary ext2
3 1007MB 16.0GB 15.0GB primary fat32 lba
mmcblk1p1 for /data
mmcblk1p2 for /cache
mmcblk1p3 for /sdcard
Will that work? I couldn't get mmcblk1p1 to show up as ext3. I did use mke2fs -j /dev/block/mmcblk1p1 to format it and I've read ext3 = ext2+journal, so I guess the fact it's not saying "ext3" under filesystem is okay?
GnatGoSplat said:
I copied the partition sizes from mmcblk0, so here's what I have on my 16GB SD card:
Code:
Model: SD SA16G (sd/mmc)
Disk /dev/block/mmcblk1: 16.0GB
Sector size (logical/physical): 512B/512B
Partition Table: msdos
Number Start End Size Type File system Flags
1 8192B 797MB 797MB primary ext2
2 797MB 1007MB 210MB primary ext2
3 1007MB 16.0GB 15.0GB primary fat32 lba
mmcblk1p1 for /data
mmcblk1p2 for /cache
mmcblk1p3 for /sdcard
Will that work? I couldn't get mmcblk1p1 to show up as ext3. I did use mke2fs -j /dev/block/mmcblk1p1 to format it and I've read ext3 = ext2+journal, so I guess the fact it's not saying "ext3" under filesystem is okay?
Click to expand...
Click to collapse
You would be correct. Yes, that's fine.
Thanks, what should be my next steps?
GnatGoSplat said:
Thanks, what should be my next steps?
Click to expand...
Click to collapse
I'll have to find time to make scripts that will modify the ramdisk, unless you can just extract it and make the changes yourself.
That would be great, I really appreciate all the help so far.
Do you think ramdisk is the only place a change will need to be made?
I was trying to see if I could figure out how to extract ramdisk from boot.img and found a perl script, but I haven't gotten around to playing with it.
Jump to post 2 for CWM log
(SORRY I was calling it the wrong thing, i corrected it to say /preload)
Hey guys, thanks for dropping in and taking the time to read this... been lurking since the OG Evo. Anyways, here's the problem.
I posted some of this in another thread http://forum.xda-developers.com/showthread.php?t=2086769
I ran whompasaurus for a few months and jumped to NoWizAOSP for a while. Then I decided to try MacksRom and didn't like it. So I decided to go back to whomp and I couldn't. Aroma would fail every time because of an error something like "file_getprop failed to stat tmp/aroma-data/launchers.prop no such file or directory". So then I flashed
[ROM][RESTORE][5-12-13]Back to UNROOTED Stock with Auto Flash Count Reset
After flashing this I am still having problems with TWRP saying it can t mount /preload. I've tried booting into recovery and doing a factory reset after installing this RESTORE rom, but still no dice.
I keep thinking it has something to do with partitions so i found a PIT file and flashed it through ODIN and it didnt seem to do anything. IDK, maybe I got the wrong PIT file or I did it wrong?
I flashed CWM cuz it lets you format /preload... but it wont do it.
I think maybe there is something wrong with my vold.fstab so here is what mine looks like:
dev_mount sdcard /storage/extSdCard auto /devices/platform/s3c-sdhci.2/mmc_host/mmc1/
Idk if this is what its supposed to look like. If anyone can post what their vold.stab looks like?
The phone still works fine but I can hardly flash anything. It's better than nothing but if anyone can point me in the right direction, that would be awesome.
Here is a log from CWM:
ClockworkMod Recovery v6.0.2.5
recovery filesystem table
=========================
0 /tmp ramdisk (null) (null) 0
1 /efs ext4 /dev/block/mmcblk0p3 (null) 0
2 /boot emmc /dev/block/mmcblk0p8 (null) 0
3 /recovery emmc /dev/block/mmcblk0p9 (null) 0
4 /cache ext4 /dev/block/mmcblk0p12 (null) 0
5 /system ext4 /dev/block/mmcblk0p13 (null) 0
6 /data ext4 /dev/block/mmcblk0p17 (null) -16384
7 /preload ext4 /dev/block/mmcblk0p14 (null) 0
8 /modem emmc /dev/block/mmcblk0p10 (null) 0
9 /carrier ext4 /dev/block/mmcblk0p16 (null) 0
10 /sdcard datamedia /dev/null (null) 0
11 /external_sd vfat /dev/block/mmcblk1p1 /dev/block/mmcblk1 0
W:Unable to get recovery.fstab info for /datadata during fstab generation!
W:Unable to get recovery.fstab info for /emmc during fstab generation!
W:Unable to get recovery.fstab info for /sd-ext during fstab generation!
I:Completed outputting fstab.
Irocessing arguments.
I:Checking arguments.
I:device_recovery_start()
Command: "/sbin/recovery"
Formatting /preload...
Creating filesystem with parameters:
Size: 20971520
Block size: 4096
Blocks per group: 32768
Inodes per group: 1280
Inode size: 256
Journal blocks: 1024
Label:
Blocks: 5120
Block groups: 1
Reserved block group size: 7
Created filesystem with 11/1280 inodes and 1118/5120 blocks
Done.
I:Can't partition non-vfat: datamedia
I:Can't format unknown volume: /emmc
I:using /data/media for /sdcard.
Tried to format and mount /preload within CWM and that is what I get. Tried doing an ODIN flash to stock with PIT and re-partition. Didnt work.
Please help.
I recently had the same problem and a lot of my flashes were failing. I ended up using Odin to completely unroot my phone and install the stock rom. Then used the note 2 toolkit to re-root and clean install everything now everything works as it should.
evertroy said:
Jump to post 2 for CWM log
(SORRY I was calling it the wrong thing, i corrected it to say /preload)
Hey guys, thanks for dropping in and taking the time to read this... been lurking since the OG Evo. Anyways, here's the problem.
I posted some of this in another thread http://forum.xda-developers.com/showthread.php?t=2086769
I ran whompasaurus for a few months and jumped to NoWizAOSP for a while. Then I decided to try MacksRom and didn't like it. So I decided to go back to whomp and I couldn't. Aroma would fail every time because of an error something like "file_getprop failed to stat tmp/aroma-data/launchers.prop no such file or directory". So then I flashed
[ROM][RESTORE][5-12-13]Back to UNROOTED Stock with Auto Flash Count Reset
After flashing this I am still having problems with TWRP saying it can t mount /preload. I've tried booting into recovery and doing a factory reset after installing this RESTORE rom, but still no dice.
I keep thinking it has something to do with partitions so i found a PIT file and flashed it through ODIN and it didnt seem to do anything. IDK, maybe I got the wrong PIT file or I did it wrong?
I flashed CWM cuz it lets you format /preload... but it wont do it.
I think maybe there is something wrong with my vold.fstab so here is what mine looks like:
dev_mount sdcard /storage/extSdCard auto /devices/platform/s3c-sdhci.2/mmc_host/mmc1/
Idk if this is what its supposed to look like. If anyone can post what their vold.stab looks like?
The phone still works fine but I can hardly flash anything. It's better than nothing but if anyone can point me in the right direction, that would be awesome.
Click to expand...
Click to collapse
The preload issue is unrelated to you being unable to install the rom you want. The preload partition is empty and worthless. You should probably post your install issue in the thread for the rom you're installing because I bet it's related to something in the way that rom installs
billard412 said:
The preload issue is unrelated to you being unable to install the rom you want. The preload partition is empty and worthless. You should probably post your install issue in the thread for the rom you're installing because I bet it's related to something in the way that rom installs
Click to expand...
Click to collapse
But ive installed the whompasaurus rom a few times, and it never gave me this problem. Only until i tried a couple other roms and tried to go back to whomp it wont install. I cant believe its the rom because nobody else has this issue. It has to be something with my phone.
Can i reconstruct that partition with adb? Whould it help and what would I type?
billard412 said:
The preload issue is unrelated to you being unable to install the rom you want. The preload partition is empty and worthless. You should probably post your install issue in the thread for the rom you're installing because I bet it's related to something in the way that rom installs
Click to expand...
Click to collapse
Hey man, you were totally spot on with that! Sorry I had doubt in you, but it was totally the whompasaurus rom that was not playing nice. I kept selecting custom install and aroma would blow past the "choose your launcher" screen so it wouldnt generate a launchers.prop. Selected FULL install and it went through all the motions of letting me select my choices, including a launcher, and installed just fine.
Thanks again! I just can't believe how much time I wasted on this. Now I know that there was really nothing wrong, I feel like bricking this phone is near impossible with all the abuse I put it through trying to "fix" it.
evertroy said:
Hey man, you were totally spot on with that! Sorry I had doubt in you, but it was totally the whompasaurus rom that was not playing nice. I kept selecting custom install and aroma would blow past the "choose your launcher" screen so it wouldnt generate a launchers.prop. Selected FULL install and it went through all the motions of letting me select my choices, including a launcher, and installed just fine.
Thanks again! I just can't believe how much time I wasted on this. Now I know that there was really nothing wrong, I feel like bricking this phone is near impossible with all the abuse I put it through trying to "fix" it.
Click to expand...
Click to collapse
Glad you got it resolved.
billard412 said:
Glad you got it resolved.
Click to expand...
Click to collapse
Yeah, it would help if I actually read the menu in the ROM installer. Man, I'm such an idiot.