Develop Bugs

[Q] Stuck in recovery :(

Hi, I'm really hoping someone can help me. I've spent the last hour searching on here and although I've found lots of posts addressing similar issues to mine, I've not managed to solve it.
Before things went wrong I was running MoDaCo r5 without any issues. A2SD+ with an ext3 partition on the SD card (but no dalvik to sd). ClockworkMod recovery.
Decided to flash CyanogenMod 6.1.0 RC1 using ROM Manager. Downloaded it to the SD along with the Google apps, backed up my current ROM, wiped cache and data, installed CM... phone booted but then stuck on the CM boot screen for about 10 minutes. Did battery pull, rebooted, same thing. Tried several times more, no luck.
So booted into recovery and tried to restore my previous ROM. It goes through all the usual stuff then says its finished. Reboot. Stuck on the pink circle loading screen.
Wiped data, wiped cache, tried factory reset, clear storage.... Just gets stuck on the pink circle screen every time I reboot.
One thing I noticed - when I first boot into recovery (hboot screen) it briefly flashes up something about SD...Loading... No image (its too quick to read it all). Not sure if that means anything.
Also, at some point (I'm afraid I can't remember exactly when, but it was while I was doing something in recovery) it said something about 'not enough space on device', or something like that.
Sorry that's all a bit muddled - I thought I was more competent at all this stuff than I clearly am! PLEASE can someone help walk me through what I need to do to get things working again.
(I can't use adb with my computer - got into all sorts of problems trying to install/use it in the past, so if there's a solution that doesn't involve that it would be great. I have access to a Linux machine if that helps.)

UPDATE: After trying everything I could think of, I decided to try the nuclear option - Backed up everything on my SD card to my computer, then formatted it, copied the CM 6.1 zip back onto the SD and installed it, and it booted fine. Maybe had something to do with there not being enough space on the SD card? Does the ROM get unzipped onto the SD card during installation? If so I guess that could have been the sticking point as I only had about 250MB free!

[Q] Help with reboots

I realize this is a *common* problem but I can't find any way to resolve this! I have been searching the forums for reboot threads and haven't been able to solve this problem yet. I am quite a noob but I apologize for the length of this thread, I'm just trying to be as detailed as possible.
It all started when I flashed CM 6.0.2 stable. It ran fine for weeks and then it started to reboot occasionally on its own. It appears as though it reboots when I am doing something intensive like watching NFL mobile or starting several downloads. I tried the nightlies as well as 6.1 RC2, same problem.
I decided to try another ROM..I have tried Virtuous, Redemptive, and SkyRaider, all of which reboot a couple times the phone first boots after installation and then, they reboot randomly on their own while I'm doing various things.
I've tried the stock and custom kernels for Virtuous as well as King's Kernel BFS #5 with Virtuous. "Stock" kernels for SkyRaider and Redemptive.
Before you say anything of course I have cleared data/factory reset EVERY time before flashing a ROM. I've also cleared cache as well as Dalvik cache before I flash a ROM.
I've tried removing the SD card before the phone boots and it seemed to have helped Redemptive but it still rebooted at one point.
I rooted it with unrevoked 3 but never used unrevoked forever, although HBOOT shows S-OFF, do I still have to use unrevoked forever?
Incredible (AMOLED)
HBOOT: 0.92
ClockwordMod Recovery: 2.5.0.5
Baseband Radio: 2.15.00.09.01 (I tried 7.28 with CM, but it also had the problem, I haven't tried it again since then)
My main questions are:
(1) Should you clear the data/factory reset, clear cache, clear Dalvik, format SD-card or any combination AFTER the ROM is flashed for the first time? Is there something I'm missing here?
(2) What is the most stable ROM and/or kernel. I really don't want to go to stock but from what I remember I never had this problem on stock. I could try it again just to see if it has the problem.
(3) Should I try unrevoked forever, does it do anything differently than unrevoked 3?
(4) Would setting up ADB/logcat help diagnose the problem?
Any other input would be appreciated on how to stop these reboots. Thanks.

same here. i'm running uncommon & KK#5 and i get reboots while listening to pandora and browsing apps.
its gotten progressively worse over the past couple days, not sure what to try. going to try flashing another rom and see how that works

SD?
Couple ideas, and answers to some of your questions.
Answers:
Unrevoked3 does S-Off for you, so you don't have to do that. If it shows S-Off in HBOOT, it is S-Off.
You don't need to format the SD card w/ ROM flashes. If you do, you lose what's on the SD card. This is typically only done once - see below.
Ideas & a question/something to think about:
1] Make a Titanium Backup of all your user apps - also d/l appbrain if you haven't already, set up the appbrain account and sync it with your device. Now you have a picture of what apps are on your device.
2] With the device on, unmount the SD card, power down, and take the SD out of the device. Copy the entire SD card contents into a folder your PC so you'll have them. Format the SD card as FAT32 on the PC. (assuming you are not a mac user, in which case I cannot help...) Put the newly formatted/clean SD card back in the device.
2]Download from ROM Manager + Virtuous' stable stock ROM/kernel (included), but do not install it from ROM Manager. Reboot into recovery. In CWM, not ROM Manager, wipe data/cache & factory data reset and clear Dalvik before flashing. (you have already formatted the SD card, no need to do it again) See if issue(s) keeps happening. If so, try flashing the radio off to 7.28, then do the Virtuous +all wipes from CWM again, reload Virtuous and again and see if the issue keeps happening.
3] Go to Settings>Applications>Manage Applications ~ look thru each/every app and see if one (or many) have a ton of info in their data and/or cache. If so, clear out the data and/or cache in those apps.
4] Once you have a stable Virtuous ROM/kernel, take a look at the handy list of apps you have on appbrain - incrementally in/uninstall them to see whether any of these may be the culprit... If once you reinstall XYZ app on Virtuous' stable ROM/kernel, you may have your culprit.
5] Try a different SD card - solving for whether the SD you have is wonky.
Yep, it's a lot to do, but you want to know what is causing the reboots; ya gotta start w/ a clean slate and diagnose incremetally.
Let us know what worked (or didn't) so others can benefit from your experience.

2] With the device on, unmount the SD card, power down, and take the SD out of the device. Copy the entire SD card contents into a folder your PC so you'll have them. Format the SD card as FAT32 on the PC. (assuming you are not a mac user, in which case I cannot help...) Put the newly formatted/clean SD card back in the device.
Click to expand...
Click to collapse
I noticed that (at least in) Virtuous the browser as well as other apps use the SD card for cache. When I tried downloading files off the internet with the browser then it would crash. I changed the cache location to the phone and then it has worked fine since.
I did as you suggested, unmounted the SD card and then formatted with FAT32. My SD card was actually FAT beforehand, I think I had heard somewhere that it needs to be FAT in order to flash radios so when I was installing 9.01. Although I did have a minor rebooting problem before with 7.28, that may have been attributed to Cyanogen itself since that was the ROM I was using at the time.
So far it has been good but unless I get an uptime of at least 3 days we won't know for sure (that was about the average uptime when I had Cyanogen). If I still run into problems I'll follow your other recommendations. Thanks a lot smtom.

You are most welcome! There's a very good "Official Radio Thread" here on XDA. If you decide to flash the radio (my personal recommendation, but ymmv) read thru that thread before you flash the radio.
Also, I didn't mention, but implied via flash in CWM, to read the notes you see when the various areas are wiped. Why? ROM Manager doesn't show you all the notes, nor can you see what exactly may be erroring, if anything. Flashing in CWM is more cumbersome, but it is a LOT more informative if/when you have issues w/ your device.

broken SDCard - how to fix?

My HTC Desire started misbehaving earlier in the year, it would crash and reboot, when it rebooted the SDCard would not be detected, a few days later, it would crash again and the SDCard would re-appear.
When it was visible, the SDCard would work ok a long as you didn't use it much, listening to music for any length of time would cause it to fail again. The SDCard will stop working a day or so after boot, all by itself without any use.
Sometimes it was visible but apparently needed formatting (which isn't true). The card tests fine in computers and I've used two different cards with the same issues.
I figure the issue is with the SDCard controller, although I'd like to get other's views on what the issue might be. I'd like to repair the phone by replacing whatever is necessary, but my knowledge of the hardware build is non-existant right now, could anyone advise where I might start?

dnel said:
The card tests fine in computers and I've used two different cards with the same issues.
Click to expand...
Click to collapse
Do the cards misbehave in recovery also? Have you tried a different rom ?

handy5876 said:
Do the cards misbehave in recovery also? Have you tried a different rom ?
Click to expand...
Click to collapse
Yes, when the sdcard disappears completely CWM also cannot mount the card.
When the card stops being readable, reboot generally revives it for a little while so hard to tell if CWM is affected by this or not.
I've wiped and reloaded the rom, recently I successfully updated to the latest Cyanogenmod 7 but the procedure is too risky if I lose the card while flashing so I wouldn't do it again.

A link for HTC Desire disassembly if you are up to it
http://www.formymobile.co.uk/desiredisassembly.php
Never opened my desire. More details in this Nexus one teardown also http://www.ifixit.com/Teardown/Nexus-One-Teardown/1654/2

dnel said:
Yes, when the sdcard disappears completely CWM also cannot mount the card.
When the card stops being readable, reboot generally revives it for a little while so hard to tell if CWM is affected by this or not.
I/QUOTE]
check the contacts first before doing a disassembly . it might just need a spray contact cleaner on both card and phone.
Click to expand...
Click to collapse

or you could try this before disassembling your phone http://forum.xda-developers.com/showthread.php?t=691187
it might be an "usb brick".

Thanks for the replies, I decided to try a few things before I took a screw-driver to my phone and so far it's good news but I'm not sure why...
I remembered that a couple of weeks before the SDCard failed, I used alpharev to s-off and flash hboot to CM7r2. So a few days ago I reverted this change.
I re-flashed the stock hboot and then switched from Cyanogen 7.2.0.1 to the last MIUI gingerbread. This process nearly bricked my phone, at one point it wouldn't even boot into recovery and then the 4GB SDcard I was last using in the phone failed completely, but interestingly it failed while it was in my computer and not my phone. After this I switched to a 32GB class 10 SDCard that was in my phone when the SDCard originally started to misbehave so although the 4GB SDCard failed I don't think this is related to the problem because the problem presents with both cards.
After I flashed stock hboot and loaded MIUI, the problem hasn't presented itself, not once.
I then flashed back to CM7r2 and reloaded MIUI and the SDcard worked but I couldn't install any market apps, complaining of a lack of storage. This is with nothing in /data except for the dalvik cache and 250MB of "free space".
I then flashed to the Data++ hboot and reloaded MIUI and the market now works and the SDcard is working.
I don't know how the partition table on the MTD may have caused my SDCard to fail, the best I can guess is there is some bad memory area which when CM7r2 is loaded, corrupts an important system memory area.
I'm leaving it stable right now and will see whether the problem arises again before making further changes. I would be interested to know if there's any fsck-like apps that I could used to check the MTD for errors?

[HELP!!?!!?] SD Card and Recovery Problems

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.

[Q] Rom not installing

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