Hey,
First, I'd like to thank everyone who's contributed to these forums. I've been visiting often lately and the progress is awesome. And, this is my first post =)
So, I rooted my Desire. Made a nandroid backup using ROM Manager, and started trying different ROMs. I finally decided to go back to the stock ROM, and so restored my backup.
Then I decided to install a2sd. So I booted into AM Recovery, restored factory defaults, and wiped the cache. I then installed the zip from the same menu (r1-a2sd-desire-dalvik-fresh-signed.zip) and proceeded to partitioning. SWAP=0, ext2=384. Then I upgraded(?) ext2 to ext3 (again, from the same recovery menu).
And now, when I reboot my device it gets stuck on the first HTC splash screen. It doesn't even reach the animation. I've heard it takes some time to write caches or something but it's been at least 15 minutes already. Any ideas?
Of course, I know I can always restore my nandroid backup, but I want to get a2sd working.
Ok, first go back to Recovery. Did you wipe the SD:EXT partition too?
Wipe the following:
Factory Reset
Dalvik Cache
SD: EXT
Make sure your card is formatted as FAT32.
You may have to reflash the actual stock rom.
If you can get hold of another sd card, download the stock rom zip and apps2sd zip and place onto sd card using a card reader or another phone that accepts micro sd cards, re-insert sd card into phone, enter recovery, wipe everything, flash stock rom, apply Apps2SD zip in recovery zip after, then partition with 0Mb swap, 512Mb ext2, rest to FAT32. Convert ext2 to ext3.
-------------------------------------
Sent via the XDA Tapatalk App
Just to clarify, when you say flash stock rom, you mean rootedupdate.zip right? (The one used in the rooting process)
UPDATE: Ok, I just did it with rootedupdate.zip but got the same problem. I wiped to factory defaults, wiped the caches, and SD: EXT. Then installed rootedupdate.zip. Then installed Apps2SD, partitioned to your recommended values, and converted ext2 to ext3.
Still, HTC boot logo has been there for a good 10 min. It didn't even reach the animation. I've heard it could take some time to update caches or something like that. Could it possibly take that long?
Lil.Fl0w said:
Just to clarify, when you say flash stock rom, you mean rootedupdate.zip right? (The one used in the rooting process)
UPDATE: Ok, I just did it with rootedupdate.zip but got the same problem. I wiped to factory defaults, wiped the caches, and SD: EXT. Then installed rootedupdate.zip. Then installed Apps2SD, partitioned to your recommended values, and converted ext2 to ext3.
Still, HTC boot logo has been there for a good 10 min. It didn't even reach the animation. I've heard it could take some time to update caches or something like that. Could it possible take that long?
Click to expand...
Click to collapse
Try in this exact order:
UPDATE: Ok, I just did it with rootedupdate.zip but got the same problem. I wiped to factory defaults, wiped the caches, and SD: EXT, partitioned to your recommended values, and converted ext2 to ext3. Then installed rootedupdate.zip. Then installed Apps2SD
shawe_ewahs said:
Try in this exact order:
UPDATE: Ok, I just did it with rootedupdate.zip but got the same problem. I wiped to factory defaults, wiped the caches, and SD: EXT, partitioned to your recommended values, and converted ext2 to ext3. Then installed rootedupdate.zip. Then installed Apps2SD
Click to expand...
Click to collapse
Ok this is driving me nuts. I did exactly as you asked and it reached the same problem - stuck on the HTC boot screen before the animation even starts.
Funny thing is, I tried installing Amer's bravox ROM which includes Apps2SD (after partitioning my SD of course) and it worked! I'm sure it did because I tried installing a few apps and internal memory barely changed, and did the "su ls -l /data" test as well.
I'm just lost now. Btw, I'm not using a goldcard but I can boot just fine into recovery and all, and my device is not locked.
Any ideas? I've attached the Apps2SD zip I tried. It's worth mentioning, I've tried downloading it from quite a few different sources.
EDIT: I have a feeling the problem lies where BOOT is formatted during the Apps2SD installation. Is it supposed to?
I did everything you did in the first post and my desire gets stuck at htc loading screen. I followed the installation guide from here and just realized that it is actually not meant for bootloader .80 http://nimbu.amorvi.com/2010/05/how-to-root-your-htc-desire/#comments
What can I do to fix all these? Help needed urgently
benleong2008 said:
I did everything you did in the first post and my desire gets stuck at htc loading screen. I followed the installation guide from here and just realized that it is actually not meant for bootloader .80 http://nimbu.amorvi.com/2010/05/how-to-root-your-htc-desire/#comments
What can I do to fix all these? Help needed urgently
Click to expand...
Click to collapse
That post only says the rooting procedure is different for .80, not Apps2SD.
Like I mentioned before, I'm not sure what the problem is, but ROMs with Apps2SD built in work just fine, so that's what I'm doing.
Lil: In the past, Ive tried the a2sd file you attached and I was also not able to boot past the HTC screen so I just used MCR 3.1 with app2sd+.
You may want to try flashing the ROM with a gold card. I have an unbranded Desire and I need to use the gold card when I rooted or need to re-flash to stock. HTH.
amf said:
You may want to try flashing the ROM with a gold card. I have an unbranded Desire and I need to use the gold card when I rooted or need to re-flash to stock. HTH.
Click to expand...
Click to collapse
You mean reflashing rootedupdate.zip with a gold card? Because I remember trying without one, and it didn't work. Then I tried with one, and was a hassle. Tried again without, and it did work. So I'm guessing I might've missed something the first time I tried without a gold card..?
But from what I understood, it doesn't matter. As long as you're rooted you don't need a gold card, and the rooting process either works all the way or doesn't at all. Did I get something wrong?
And, just to make sure I understood you right, using a gold card should allow me to use the zip above?
If I remember it correctly, I copied the ROM I'm flashing to a gold card and used that card to flash the ROM.
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
Hi,
coming from an old Sense-based Modaco i decided to give my good ole Desire a little overhaul this weekend.
So i did:
applied Alpharev's S-Off
upgraded to 0.93.1000 HBOOT with N1 table
flashed a new radio (32.49.00.32U_5.11.05.27)
upgraded to AmonRa's 2.0.0 recovery via unrevoked3
Then i get rid of the Sense Rom and flashed CM6.1.1 plus DT A2SD script
So far so good, i did several nandroid backups and restores with AmonRA successfully. All was running smooth and sexy...
During watching TV with wifey i was bored and did another backup directly from ROM Mananger with CWM 2.5.0.7, just to be extra-safe, i thought!
After backup was finished i rebooted into CM 6.1.1 and noticed that my widgets arent loaded and all apps on SD were missing.
A reboot into AmonRA recovery and try to restore my last Nandroid backup : -> "E: cant mount /dev/block/mmcblk0p1...(No such file or directory)"
Also when booting into CM 6.1.1 all my filemanagers do not show any SD storage anymore.
Tried 4 different SD cards now.
What went wrong and most importantly, how do i get my Desire back to full life??
TIA, hope someone can help me...
Edit with some additional info:
- SD card is still fully readable in my Windows PC
- when i boot up the (half, w/o all my A2SD apps) CM 6.1.1, my network operator is found but i am not booked into the network
- device is still USB recognized in bootloader and fastboot, but not in recovery and when ROM is booted up anymore
To summarize:
everything worked fine incl. Nandroid backups/restores with AmonRa until i made a simple backup with Clockwork Mod 2.5.0.7
Did you try this one?
http://android.modaco.com/content/h...com/309939/usb-brick-rickrolled-b0rked-fixed/
It solved the problems for me.
Yay! You made my day, only one sleepless night
I skipped almost everything of the steps and just entered fastboot with 'fastboot oem enableqxdm 0' .
This fixed it all w/o the need to re-root and fixing the misc partition.
Just a restore of my CM 6.1.1 was needed and everything works like before again.
Muchas gracias again, i love this community!
Still i am wondering why a simple backup with CWM could cause this...
Edit: one problem is left -> USB is not started when the ROM is up and I plugin an USB cable (just nothing happens)? What could be the reason for this? Make SD card management somehow annoying (booting into recovery to mount it for PC)
Edit 2:
All is fixed now, wiping Dalvik and Cache resolved the remaining USB issue!
Congratulation
Felys said:
I skipped almost everything of the steps and just entered fastboot with 'fastboot oem enableqxdm 0' .
This fixed it all w/o the need to re-root and fixing the misc partition. D
Click to expand...
Click to collapse
Same problem as yours. Same cause I think.
Applied same solution. Got OK. But problem unsolved. Packing to send it to HTC...
To fix it entirely I had to apply the update.zip for fixing the misc-partition as well.
Try it 1st, its a matter of 2 minutes
Hello fellow mates,
I am running Leedroid 2.4A2SD and I am having clockwork mod 2.5.0.1.
Yest a strange thing happened...As I didn't have any nandroid backup for my rom over last 20days,I decided to backup my rom with the help of nandroid...
So I went into recovery and started backing up..The process went on fine..The screen also showed that back up was complete..
As usual I went to reboot the phone using reboot option...But the phone wouldn't boot up i.e it stuck @ HTC logo...So I flsahed a new rom again and set up all the things as they were earlier..After this I again tried to do a nandroid backup and after backup completion and rebooting the phone, it stuck at Htc logo screen again...
It might be SD Card Error.
My suggestion:
1. Copy all of your SD card contents to your computer.
2. Reformat your SD Card.
3. Move your SD card contents from your computer to your SD Card.
4. Try to restore your nandroid backup.
Good Luck..
will try it and let u knoe
Sent from my HTC Desire using Tapatalk
I've had this problem from ruu-ing then unrooting and doing an initial nandroid backup - it just bootloops. Only way I can get past it is to do the initial backup then reboot straight back into recovery, restore the nandroid I've just backup'd and then reboot.
Odd, happening with me on your version and 3.0.0.5