I got 2 questions for CM6, I'll be getting my Desire back by Thursday hopefully :
1) CM6 by default doesn't have any of the Google's applications, including the Market App. I know it has a separate package, but it has too many Google's applications. The only ones I want from it are the Market, and the necessary ones required for operation(Google's accounts for authentication, setup wizard etc). Rest I want to download from Market(I see that most are available from it). So can I just delete the apps from the system folder in the package? If so, what are the must ones that must be kept?
2) Is the SD card required to be partitioned in 3 partitions(Fat32 + Ext2/3/4 + Linux Swap) when using CM6?
1. you can open gapps.zip and remove all the apps you don't need in /system...don't know which are "must have"
than you zip it back and flash it ,you can sign it but you don't have to...you can flash unsigned gapps.zip using clockwork recovery
2.no CM doesn't use apps2sd(ext) they use native froyo a2sd
hope this helps
I got another Q, can a Goldcard be used as a normal SD Card? I mean I plan on making one as soon as I get my Desire but I'll preserve it for future needs, I SLCD bricked my last one and realised the importance of having one. So would that be a good idea?
Thanks for your reply, it helps . Also, what are the kind of partitions I need to create for the SD card to be usable in the phone as well as Amon Ra's or ClockworkMod's Recovery? I created a FAT32 one using Windows and GParted(2 different times) but Clockwork's recovery or fastboot couldn't recognize them.
Yes the goldcard can be used as a regular sd-card
And for partitioning you only need a fat32 one as long as you don't run any old a2sd. Using windows should work fine, but you could try partitioning it again with amonra or something similar. And are you sure, you haven't got something wrong. The recovery is usually easily able to read fat32 easily, and how do you see, recovery and fastboot doesn't recognize it?
I have an unrevoked-forever (s-off) Incredible, running CM 6.0.2 (stable). I have been running an 8gb sd in, but recently I have been reaching the limits.... so I decided to upgrade it to 16gb.
I copied all the files from my 8gb to my PC, via phone USB. Then from my PC to a 16gb card, via card reader. When I unmounted the 8gb, and replaced it with the 16gb, it would not remount. I then started getting low memory warnings....but still could not get it to mount the SD card, old one or new one. So I rebooted and now I'm stuck in a boot loop, with either memory card, for some reason....
I tried a nandroid backup, and it says complete with one line saying "SD-ext.img not found- skipping...." then on reboot, it still goes into a boot loop.
Suggestions on what to try next are VERY welcome. I guess I should have not tried swapping the SD card while the phone was on?? I can of coarse boot into recovery, and I do have ClockworkMod 2.5.0.1.
Worse case scenerio, wipe? and run apply CM from SD card?
Why do people always get scared about the SD-ext error messages, where it's clearing data, formatting, or restoring backups. SD-ext is for apps2SD. The SD card partition for general storage is called sdcard.
With regards to your problem, I have no idea, Sorry.
SynbiosVyse said:
Why do people always get scared about the SD-ext error messages, where it's clearing data, formatting, or restoring backups. SD-ext is for apps2SD. The SD card partition for general storage is called sdcard.
With regards to your problem, I have no idea, Sorry.
Click to expand...
Click to collapse
I have no idea what SD-ext is for...I'm not "scared" of this error, I just want to get out of bootloop....if it's not related or important information, sorry....I assume I messed something related to the SD card....considering how/when this started happening....but of coarse I don't know exactly what I did, that's why I'm asking.
I don't get an "error" screen, I just get a boot loop. I don't even know where to begin to toubleshoot this....so thats what I am asking for...suggestions.
I thought that you assumed that error was the problem.
Does your phone still reboot loop when the sdcard is removed completely? You can try backing up the contents of the card onto your computer..then format it with FAT32 in windows. Try it with a completely empty card, but formatted as FAT32 of course.
If you're still having problems then if I were in your shoes I would resort to a factory reset, clear everything, and then start fresh (especially considering your nandroid backup did not work)
SynbiosVyse said:
I thought that you assumed that error was the problem.
Does your phone still reboot loop when the sdcard is removed completely? You can try backing up the contents of the card onto your computer..then format it with FAT32 in windows. Try it with a completely empty card, but formatted as FAT32 of course.
If you're still having problems then if I were in your shoes I would resort to a factory reset, clear everything, and then start fresh (especially considering your nandroid backup did not work)
Click to expand...
Click to collapse
The boot loop happens with, either card, and also with no SDcard in. I only get to the Cyanogen animation and it keeps looping......I will try formatting the cards on the PC and then pasting the SD card "copy/backup" from my initial try....
---if worse case----
I have never installed other roms, I have had relative success with CM....so I really don't know how to "wipe" and start fresh.
Are these steps close:
1. boot to recovery> ClockworkMod
2. select wipe data/factory reset
3. select wipe cache partition
4. select advanced> select wipe Dalvik cache?
5. install zip from SD card > select CM- 6.0.2
6. done?
Yes, those steps sound correct to me. That is your best shot.
The Incredible in general has reboot problems, for some reason it is very sensitive. I'm not really sure if you changing the SD card truly caused the problem or not, but it's worth reflashing the latest CM. I recommend 6.1 RC2
6.0.2 is quite old and it has a lot of problems, including force close mail client by default, a faulty radio interface layer that may cause reboots, and many, many other fixes have been implemented in 6.1 RC2 and the latest nightlies. Don't be discouraged that it is a release candidate..in reality it is much more stable than the 6.0.2 "stable".
SynbiosVyse said:
Yes, those steps sound correct to me. That is your best shot.
The Incredible in general has reboot problems, for some reason it is very sensitive. I'm not really sure if you changing the SD card truly caused the problem or not, but it's worth reflashing the latest CM. I recommend 6.1 RC2
6.0.2 is quite old and it has a lot of problems, including force close mail client by default, a faulty radio interface layer that may cause reboots, and many, many other fixes have been implemented in 6.1 RC2 and the latest nightlies. Don't be discouraged that it is a release candidate..in reality it is much more stable than the 6.0.2 "stable".
Click to expand...
Click to collapse
Well I downloaded a fresh 6.0.2 and 6.1 RC2 from Cyanogen....I followed the steps above to "wipe" and installed the 6.0.2....result= bootloop still
repeated steps to "wipe" again......selected to install 6.1 rc2......result= bootloop still
SO now I'm really at a loss. I figured with a wipe it would work....maybe my steps are wrong.....ANY suggestions now are welcome.
Do you know how to use advanced from the android ask. It can be used to figure out where your problems are.
Might be that the Dex cache is being created, but that only happened to me when flashing my own custom roms, not when changing SD cards.
Sent from my ADR6300 using XDA App
linuxmotion said:
Do you know how to use advanced from the android ask. It can be used to figure out where your problems are.
Might be that the Dex cache is being created, but that only happened to me when flashing my own custom roms, not when changing SD cards.
Sent from my ADR6300 using XDA App
Click to expand...
Click to collapse
No I do not know how to use the "advanced from android ask." But I am willing to learn if needed.....Is this the SDK tool? I believe I toyed with this when I first used the Unrevoked method to root....but thats been months and I don't mess with roms much. I started playing around with SDK a few minutes ago to familiarize myself....but idk.....
Is there a simple way to get some kind of log file? Can I load another recovery, like Amon_RA style type, which has some different options....but I don't know if it will help......Thanks for all suggestions thus far.
See I'm not exactly sure that the SD card was what caused the malfunction in the first place.
If you have an AMOLED incredible your 3G radio or battery may be beginning to fail...as I said before the Inc is very sensitive and tends to reboot a lot for stupid reasons.
You can certainly get a log if you use LogCat from ADB, but if you cant figure out exactly whats happening, then most likely you need a replacement.
You can unroot, turn S-ON, and put a stock RUU and see if you still get reboots (I'm willing to be that you will). But if you still get reboots completely stock, since you're stock you can go to verizon now and get a warranty replacement.
Quick review
- you unmounted the 8 Gb SD card, and removed it from the device while the device was still on, replaced it w/ the 16 Gb SD also while device still on?
- in the last working CM 6 ROM... were you using the SD card to cache memory or any other SD card usage tied to an AOSP ROM?
- what apps had you moved to SD card?
Absent all that, try and d/l a non AOSP ROM, for instance Virtuous, place it on your SD card in Recovery, and see if you can flash it.
Why? Solving for whether the device boots and will load a ROM at all - AOSP ROM's utilize the SD card more than Sense ROMs.
smtom said:
Quick review
- you unmounted the 8 Gb SD card, and removed it from the device while the device was still on, replaced it w/ the 16 Gb SD also while device still on?
Click to expand...
Click to collapse
Correct.
- in the last working CM 6 ROM... were you using the SD card to cache memory or any other SD card usage tied to an AOSP ROM?
Click to expand...
Click to collapse
I did use a rooted app to move things to the memory card, but I didn't see any benefits so I moved it back, at least I selected too, whether the program moved them back or not.....hmm...
- what apps had you moved to SD card?
Click to expand...
Click to collapse
you know I'm not sure I moved apps back. I know again I didn't see the benefit of apps/cache on the SD card, so I moved it back to phone....
------
Status as of 12/06/10 11:18am est.......Things I have done since last posts.
1. I have wiped numerous times via ClockworkMod. And tried CM 6.1rc2. Still got loop.
2. I installed Amon_RA recovery, wiped everything, formatted SD card through Amon, partioned SD card through Amon.....installed Cyan CM6.1 listed above, and phone sat loading at the initial screen "htc Incredible." Let it sit for 10+min....still nothing....
3. Tried to repeat step above...same results, now just initial screen, NO bootloop.
4. Installed ClockworkMod 2.5.0.5. Wiped. Install Virtuous 3.1.0. Recieved an error during install....."E:\" unable to read data...followed by a string of numbers and other info.....
5. Wiped.
6. Installed Hboot 92. (upgraded from 77)
7. Tried MIUI v0.12.3. Rom installed "successful." Rebooted and stuck on initial screen. been 5+ min as of now....
So NOW I am not getting a Bootloop....just a frozen screen. I can still get into recovery, so hopefully I still have options. Your insights or suggestions are the only thing keeping me trying ATM....I'm running out of options of my own.....
Well I still haven't got past initial boot screen with MIUI, even though it said installed correct during flash.....
SO I tried to wipe, and install Virtuous 3.1.0 again. got the same error...wrote it down this time:
E: Can't chown/mod /data/app (operation not permitted)
E: Failure at line 8: set_perm_recursive 1000 1000 0771 0644 DATA:app
Installation aborted.
I'm still at a loss, and taken any pointers or ideas. I may play around with other roms, but idk.
1. I tried Skyraid_333 and had the same results. Locked on initial white screen.
2. Wiped and tried a "stock" rom available from Virtuous.....http://www.virtuousrom.com/p/other-releases.html
It loaded and then it actually booted to the red eye droid (different from my original post which was the CyanMod boot anim)....yay....then it froze (eye stopped moving)....tried booting w/o SD card...same thing....
3. Wiped and decided to try Virtuous again. This time it loaded and installed "completely."
It booted again to the red eye animation....seemed to freeze, but I left it, and it finally started after 5+ min....I finally got a phone back.....
I do not know entirely what I did, in the process of loading all these roms. I do remember when I installed the "stock" rom, listed above, it had an install step which said installing "BOOT." (or something like that) I do not remember this listed step on the other rom installs...although they may do it and not list it....idk....
I have a feeling that the stock rom did something, but I don't know why a "wipe" does not reset everything, and why any rom wouldn't work....So I'm stuck back with HTC sense, due to the time I have been without a phone, I will live with it....I forgot how much I dislike this sense.......
Thanks to everyone who chimed in.
Congrats on you fixing your phone. I am still very new to this myself, but one of the first things I would have done would be install a stock rom again. It sounds like you lost or had some corrupt files which were fixed by going back to stock. If it were me I wouldn't be scared to wipe with a custom rom or nandroid backup, but thats just me.
i'm stuck with a similar problem: phone (dinc rooted, recovery CM 2.5.1.2, hboot .92) currently frozen on htc splash screen -
How it happened:
I was running MIUI 0.6 1.1.28.1, tried to re-format the SDcard to wipe it and start from scratch again. Did not nandroid beforehand (wiping SD) but pulled the 0.6 1.1.28.1 zip to my desktop. Tried formatting but phone wouldn't format it properly - wiped all info from SD, but no longer readable by phone or computer.
Used Mac disc utility to re-format and erase card to FAT32, still un-readable. Phone now only boots to splash screen, recovery works.
Brother has an un-rooted dinc so I grabbed his SD and mounted the card to the Mac via recovery, wrote onto it the MIUI rom I was previously using and did a full wipe (data, cache, davlik) and installed rom - rom installed correctly but still couldn't get past htc splash screen
Gave bro back his SD and tried mine again - got it to mount to the phone by partitioning through recovery, re-installed MIUI rom to my SD card and tried rebooting a number of times, still can't get past the splash screen (15+ mins)
Currently downloading virtuous "stock" rom as posted above and will try to wipe/ flash. It's a huge zip compared to the MIUI zip - maybe that's a good thing?
Here's to hoping.
Have tried flashing multiple versions of MIUI rom, packaged by n_i_x and warttack - no luck on either.
I just flashed the virtuous "stock" rom and got to the droid eye splash YES!! Mine may also be stuck in that screen though on the droid eye.
IT'S WORKING!!!!!!!!!!!!!!!
Can't even begin to say how relieved I am - I'm never getting rid of that magical virtuous zip.
So glad someone had gone though this before me.
AOSP interacts w/ SD
Handy information to know -
AOSP ROMs interact w/ the SD card quite a bit, whereas Sense ROMs not so much.
So, if a new SD and boot w/ AOSP, expect it to be wonky, particularly during boot.
hth
i dunno what caused it but mine has been doing this for about a month. Got my refurbished phone in today so HOPEFULLY that one will work better, but i dont really expect it, as this stupid boot loop issue seems to be a VERY common problem with inc's. I probably wont ever buy an HTC after this one, should have learned my lesson after the touch pro
anyway, even on stock rom, unrooted, with nothing extra, mine does this for no apparent reason
So a while back I rooted my desire, and played about with a few roms, then stuck with cyanogen for quite a while. This is the order of a few actions I took which I think may be where the problem occurred.
So from being rooted with cyanogen 7:
I decided to s-off the phone with alpharev
I then put a new splash screen on
Then decided I wanted a new sd card (I was told by a mate it will just go straight in no problems) So I bought an 8gb card stuck it in put my backed up data on the card and booted, all was fine.
I then thought about trying a few new roms that had appeared, and I tried flashing one only for the phone to hang forever on the splash screen.
I've been trying a few things to try to resolve it, stabbing in the dark, such as running unrevoked3 (maybe to root again, only for it to say the firmware is too new) I made my new sd card a gold card, like I did with the original.
None of these helped. has anyone any ideas or know how to sort this out???
What recovery do you have? Which ROM did hang?
Did you do a full wipe?
Does the rom you want to instal require a ext partition?
Sent from my GT-I9100 using XDA Premium App
I wiped the cache, and dalvik cache, even did a factory reset in recovery. Im using clockwork recovery.
I tried InsertCoin_GB_Sense2.1_CM7_v20 and Reflex_S_2.0_LITE_GingerBread_Sense-2.1_GRI40_A2SD+
Maybe these need an ext partition? Would that be it? I'm not sure how to set that up yet.
yes those roms need ext partition, don't know about reflex bu have insertcoin myself, 1GB ext4.
1.go to recovery
2.press on partition sd,choose the size, then after it's finished convert it to ext3 in partition sd again below the option of making one, you can make ext4, but thats up to you. ext3 is needed..
Don't forget to backup your sd, you'll lose everything on it
The ROM you mentioned is an a2sd ROM. So yes, you'll need to partition your SD card if you want to use a a2sd rom.
Sent from my HTC Desire using Tapatalk
Thanks for this I will get on it and let you know
I can't find an option in my clockwork to partition the sd. Just been searching a bit and seen it can be done through rom manager, that rebooted the phone and left me with the ! in a triangle and the small droid on the screen and when I press the power button it is in recovery it says installation aborted. Is there a guide for the Desire? I can't seem to find one....
Sorry found a guide on here. Will try to do it now.
Ok so I am really struggling to get anywhere with a few different guides to partition the card. Through rom manager it also says signature failed, although I have tried toggling the permissions. Major
stevoh84 said:
Ok so I am really struggling to get anywhere with a few different guides to partition the card. Through rom manager it also says signature failed, although I have tried toggling the permissions. Major
Click to expand...
Click to collapse
Steveoh like i told, do it from recovery(easiest), when you rooted you were able to change the recovery(unrEVOked), do so and change it to Ra recovery
Still if you don't want to this program can help youhttp://www.partitionwizard.com/free-partition-manager.html
Download this and do it from you pc, although it's very easy to do from recovery, takes 5,6 minutes mostly waiting..
I have created a partition with the program you recommenced. How will I know that it is ext 3? And that my phone will use it?
found it!
Here's a lovely and vague one for you all to try wrap your heads around...
Okay, so I started having trouble with my SD card about a year ago after my mate added a partition so I could flash A2SD ROMs (I believe - I was stuck and asked him to sort it and from what I can gather, that's what he did). It was fine for a while, then suddenly it became nigh on unresponsive to Android: I couldn't take photos, install apps to SD, basically any data transfer between the device and the SD storage was not happening. I think this was after I tried to delete some things to make room for videos and **** but I was stuck on about 300MB of the ~2GB available (this may have been my first attempt to delete after the partition, I'm not sure).
That was the birth of a problem I am still yet to fix. My dad needed a new phone and I wasn't using my Desire anymore. He's 53, and so the Sense UI was less than intuitive to him which lead to me offering to make it a bit simpler for him (flash a stock ROM and use a more information-centric launcher). The device badly needed updating anyways as I hadn't done so since my mate partitioned my SD card and some bugs had began to develop on the ROM I was using. So, I downloaded the latest CM build and set about reformatting the storage to see if I could solve some of the issues. In attempting to do so I think I performed a data, cache and dalvik cache wipe which removed the ROM I was currently using. The partitioning was successful, so I transferred the new ROM and attempted to flash - BOOM! Error message. Tried again, same thing. Now I have a phone that'll only boot into a recovery that's 5 full versions old (CM Recovery v2.5.0.7) without a way to flash an update img. I've tried on many different occasions to try and sort the problem and spent relentless hours trying to research a solution to the numerous different error messages this produces. Every error I can remember was a problem with read/write on the SD card, so I purchased a new one to no avail.
The phone CAN'T be bricked, surely. I still have access to things like USB mounting (which works absolutely fine), and most importantly, access to the recovery. Please don't tell me she won't live on, this is my baby and she's going down fighting! :'(
TL;DR SD card read/write issues. I only have access to recovery. I can mount the SD card via USB in CM Recovery, but every time I try to flash a new ROM I get numerous different read/write errors.
Go here:
http://forum.xda-developers.com/showthread.php?t=1408936
There you can download 4ext recovery that can be flashed via fastboot or using some flasher.
When you flash it repartition your sd card, choose only one sd-ext partition (not bigger than 1,5gb), no swap and fat32 for thevrest of your card.
After repartitioning try to flash some rom and see how it will work.
Hi
I have a Desire GSM rooted and S-ON RA-Desire v2.0.1 stock HBOOT Ext 4 1Gb latest radio ends in 23
Have been running on a custom rom for over a year now and want to install the latest copy of the same rom. The md5sum is identical for the zip file to the source.
Booted into recovery wiped all data, cache and then devlik-cache.
I have turned off signature verification and then selected my rom zip on SD card.
Installed the rom rather there were no errors and it took about 20 seconds (seemed too fast).
Next in recovery I did a reboot.
Now the screen went white with green HTC logo in centre for about 1 minute then after this a black screen with android written logo for about another 2 minutes.
Eventually phone boots into rom but it is not the new rom it is the exact same old rom.
I can see from applications listed that I am still super user so not lost root.
In settings software information everything is listed identical to what I had before.
The contents of the zip files are different so it is not the same rom being flashed.
Choosen rom is
[ROM][Cool Sense][5 April]Cool Droid v3|2.3.4|FASTEST|Data++/Stock (currently have Icecream sense v2 installed which is an earlier version of the same rom)
I did not install the alignment zip as I had already setup to use an earlier rom version and ext4.
What have I done wrong in trying to install my choosen rom please?
I feel like I must have missed something.
Not sure which recovery you have, with 4ext I boot to recover, format everything except sd then install zip and it seems to work, obviously everything then needs reinstalling from the backup you'll have made
Sent from my HTC Desire using Tapatalk 2
Hi
Unrevoked 3, as I have one of those odd PVT4 Desire phones 4000 erase size using RA Recovery. (something like that sorry if technical references are not super clear).
I use Titatium backup so reinstalling wont take long just need the ROM to install.
This is a fast glitch free rom using sense so I do not want to try a different rom as it gave me a year without trouble. Only doing this to start again with the space issue needing a refresh.
I have cleared delivk cache again and flashed my original v2 rom and that worked showing expected progress reports.
So I thought would try flashing the new v3 rom, and see if I got any joy this time.
Still no joy, it looks like it starts as two lines appear then it says complete with no obvious error.
So I reflashed the original v2 rom again and will go with that as I need a phone more then I need to play.
Odd.
Maybe the new v3 rom needs sOFF but as far as I could read it does not.
Even installing the previous rom things are still not right.
The apps that normally come with the rom are not installed such as Demon controller, No adds and Busy Box. I can see that they are in the zip file they are just not been added.
I can manually install Busy Box from the market so I know it is not a permission thing.
Titatium Backup is seeing my Ext4 partion (it calls it an ap2sd but it is showing) so I don't think there is a problem with my SD car arrangement.
I stupidly do not have a nandroid of the previous install I can restore.
So any ideas please why the previously working and installed rom is not reinstalling fully with all it's built in apps?
Anything I could try please?
Looks like I have identified the problem, my SD card is flakey and Gparted reports sick partion table that wont fix so the Ext4 partion was not been seen which is probably why the install failed and the apps were not installing.
New Sd card will be ordered and then start again.
Thankfully I dod have an uptodate SD card backup.
Phone is working just as a phone for the next few days.
These micro SD cards do not last long at this rate I get 1 year from them as this will be my third ordered.
Go to S-OFF, is better and mandatory for a lot of rom.
New card and more fiddle work with Gparted and now waiting for setup to complete as old v2 rom is installed. It works fast and is smooth plus has HTCsense so I can keep my sync capability so will be staying with it so I can live without S-OFF
Gparted when I followd the recommendations I kept getting a corrupt card on my phone so this is what worked for me.
Format card on phone
Then put card into usb card reader and place in PC
Reboot PC onto Gparted CD
Select SD card and then I resized the fat32 partion already there and then added a new EXT4 partion.
This worked for me.
Dump gparted, format the card through 4ext recovery
Sent from my HTC Desire using Tapatalk 2