Develop Bugs

Stuck on boot (post-A2SD)

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.

Help, phone in constant boot loop

I've followed this guide on this forum to get a2sd:
http://forum.xda-developers.com/showthread.php?t=670087
And I have the Modaco mod, and I know it said there was a chance it could go wrong.
But I tried nandroid restore and it didn't work, now I'm still in a boot loop, what should I do
Trying to do this now:
Run a2sd remove to reset everything back...that will fix the bootloop by setting everything back to internal storage.
Hope it works
Didn't work.

Have u partitioned ur sd card with an ext2 partition? im using apps2sd, if i take my sd card out and turn my fone on, it gets stuck in a boot loop, partion ur sd card using recovery, if that dosent work just flash onther rom from recovery lol

AndroHero said:
Have u partitioned ur sd card with an ext2 partition? im using apps2sd, if i take my sd card out and turn my fone on, it gets stuck in a boot loop, partion ur sd card using recovery, if that dosent work just flash onther rom from recovery lol
Click to expand...
Click to collapse
I used rommanager to partition my sd card.
And the a2sd remove command didn't work, still in loop

Also, did you flash a MCR custom rom that already includes Apps2SD? if you did, then all you needed to do was partition your SD card while still in Recovery Mode. You only need to install Apps2SD separately if the rom you want to flash does not have Apps2SD incorporated into the rom.
If you have a rom with Apps2SD already installed, then in Recovery Mode, perform a full wipe, flash the rom, partition your SD card, and then convert ext2 to ext3. All steps should be perfomed while still in Recovery Mode and before you reboot your device.

MasDroid said:
Also, did you flash a MCR custom rom that already includes Apps2SD? if you did, then all you needed to do was partition your SD card while still in Recovery Mode. You only need to install Apps2SD separately if the rom you want to flash does not have Apps2SD incorporated into the rom.
If you have a rom with Apps2SD already installed, then in Recovery Mode, perform a full wipe, flash the rom, partition your SD card, and then convert ext2 to ext3. All steps should be perfomed while still in Recovery Mode and before you reboot your device.
Click to expand...
Click to collapse
The rom doesn't contain apps2sd.
And with a full whipe, do you mean a factory reset?

Burrid said:
The rom doesn't contain apps2sd.
And with a full whipe, do you mean a factory reset?
Click to expand...
Click to collapse
Yep, try going back into Recovery Mode menu and select Wipe > Wipe Data/Factory Reset using the optical trackpad. If you still get stuck, then I would suggest that you follow this guide:
http://nimbu.amorvi.com/2010/05/how-to-root-your-htc-desire/
It is very easy to follow and explains how to install Apps2SD separately. Try flashing the rom file (rootedupdate.zip) it mentions because you would otherwise be stuck in bootloop if you re-flashed your MCR rom having no way to load the Sense UI again and place the r1-a2sd-desire-dalvik-fresh-signed.zip onto your SD Card (unless you maybe downloaded it using ROM Manager or had another smartphone available where you could take out your sd card, insert it into the other phone, mount it, and place the downloaded r1-a2sd-desire-dalvik-fresh-signed.zip onto your sd card, then re-insert it back into your phone to flash)
Just remember to perform a full wipe in Recovery Mode menu (Wipe > Wipe data/factory reset, Wipe > Wipe cache, Wipe > Wipe Dalvik-cache). Then re-flash the rom and follow the guide to install Apps2SD.

Sorry to answer this late, I was away for the weekend.
It's a nice guide, but I don't have those files on my sd card, and I don't have an sd card adaptor.
I don't want to send my phone in

Try wiping everything (data, ext and dalvik-cache) and either try your nandroid backup again or reflash the rom.
Burrid said:
Sorry to answer this late, I was away for the weekend.
It's a nice guide, but I don't have those files on my sd card, and I don't have an sd card adaptor.
I don't want to send my phone in
Click to expand...
Click to collapse

tkirton said:
Try wiping everything (data, ext and dalvik-cache) and either try your nandroid backup again or reflash the rom.
Click to expand...
Click to collapse
I always tried the factory wipe and cache clear from my custom recovery but that didn't work.
Then I did a factory wipe and cache clear from my standard recovery and he started up again
I think everybody was telling me to do this, but I always did it in custom recovery.
Thanks a lot for the help tkirton and MasDroid!!

big problems...i think i'm sinking fast

Did everything the way I normally do when flashing a new rom.
Now when I attempt to load any ROM from my sd card, I get this message:
Installing system files ...
E:Error in /sdcard/Incredible Files/SkyRaider_33_Sense_Final.zip
(Status 0)
Installation aborted.
I also try to do a restore from my nandroid backups and it ALWAYS "freezes". Now the only thing I can do is boot into recovery but nothing after that. I've read through a lot of material and know how to do most things, however I'm by no means an expert and now I feel like I've caused irreversible damage.
HELP?

sounds to me like your rom got corrupt during the download, i would try to download it again after deleting the file off your SD card.
did you download it from a PC or from your inc? i have seen people get corrupt files when downloading straight from the inc, its best to use a PC to download the roms
you can use the mount menu in recovery to mount your usb storage if you dont have an adapter to read the microsd, this will let you replace the possibly corrupt rom with a fresh zip

My original sd card has become unreadable by both my incredible and by my sd card reader. I have another one and loaded all of the backed up files I had on the old one. I've tried downloading the ROM through ROM Manager as well as placing the file on the new sd card and both do the same thing.
I honestly have no idea what to do now and am worried that not everything I need was transferred to the new sd card.
I just want to be able to load ANY ROM and I'm willing to reset/wipe anything and everything but I don't think there's anything I can do at this point....

well there is nothing that needs to be on the SD card at all aside from the backup or [rom].zip file you are trying to flash
have you tried installing a different rom with recovery? maybe virtous rom?
also what version of clockwork recovery are you running?

powellshake2 said:
My original sd card has become unreadable by both my incredible and by my sd card reader. I have another one and loaded all of the backed up files I had on the old one. I've tried downloading the ROM through ROM Manager as well as placing the file on the new sd card and both do the same thing.
I honestly have no idea what to do now and am worried that not everything I need was transferred to the new sd card.
I just want to be able to load ANY ROM and I'm willing to reset/wipe anything and everything but I don't think there's anything I can do at this point....
Click to expand...
Click to collapse
And you're sure it's FAT32?
Sent from my ADR6300 using XDA App

Positive it's FAT32 and I just flashed the most current Clockwork Recovery from ROM Manager.

powellshake2 said:
Positive it's FAT32 and I just flashed the most current Clockwork Recovery from ROM Manager.
Click to expand...
Click to collapse
Try to format/partition the sd via recovery. The new clockwork has this method (haven't tried it and don't know if it works) and the alternate RA does, too. I've used that one and know it works. Try that (leave the defaults, which is 512mb sd-ext, 32mb or similiar swap, I think, and the rest as FAT32).

boot into hboot (vol down and power when device is off)
what hboot version and baseband are you running?
I dont think the sd card is the problem

I wiped the dalvik and batt stats and for whatever reason tried again to reinstall the ROM and it went through this time.
Everything seems to be working as normal. Man was that one weird ass experience.

[Q] CWM recovery dooesnt see Restore files after formatting to Fat32 with GParted.

Before installing a Custom ROM on my rooted Desire I am trying to sort out the SDCard as required but am running into problems.
The guides I've read say to change the size of the Fat32 partition on my card to allow an Ext partition. The trouble is in GParted my card just comes up as 'unallocated'.
If I do format it to Fat32 and add an Ext partition (both Primary) once I put my recovery files (and or update.zip for custom ROM) on the card and enter CWM Recovery it doesnt see the files. It just says 'no files found'.
At one point my phone said it couldn't mount SD Card. This even occured when booting phone as usual as no memory card was showing up.
Has anyone else had this problem?

Well I've spent about three hours on this again today still to no avail.
I tried formatting the card in recovery then brought it up in gparted. The card was still showing up as 'unallocated' and when I created the Fat32/Ext partitions the card once again failed to be read by recovery. Although Windows has no problem seeing it.
Eventually my phone and gparted couldnt see or mount the card at all. After running my phone and formatting the card it eventually saw it.
I thought the problem may be because I connected my card to gparted through the phone so tried a card reader but the card reader didn't appear to work. I don't know if the difference I explained is important.
Is it feasible to install a decent custom rom with A2SD with the partition created through recovery? (which gparted also didnt see) as I am having an absolute headache with gparted. Every work around I try just creates a new problem.

Try this: Use Gparted to partition whole card to 1 FAT32 primary partition and then partition it via 4ext recovery into two partitions as required.

Thanks, I'll try it once the kids give me some peace.
Its actually the Supernova 2.4.0.0 ROM I'm trying to install but if I do partition the SD Card with Ext4 Recovery when I do the required Full Wipe won't it go back to how it was? and then I'd have to setup the phone and install the app again to re-partition it? Would I be able to do this before I install the custom ROM?

Steveh8204 said:
Thanks, I'll try it once the kids give me some peace.
Its actually the Supernova 2.4.0.0 ROM I'm trying to install but if I do partition the SD Card with Ext4 Recovery when I do the required Full Wipe won't it go back to how it was? and then I'd have to setup the phone and install the app again to re-partition it? Would I be able to do this before I install the custom ROM?
Click to expand...
Click to collapse
A full wipe doesnt repartition the card. It only formats some partitions. Partition first, then do a wipe and finally install the rom. Installation instructions for the rom are given on supernova.droidzone.in

Droidzone said:
A full wipe doesnt repartition the card. It only formats some partitions. Partition first, then do a wipe and finally install the rom. Installation instructions for the rom are given on supernova.droidzone.in
Click to expand...
Click to collapse
By 'Full Wipe' do you mean the wipe data/factory reset from ClockworkMod Recovery?

Steveh8204 said:
By 'Full Wipe' do you mean the wipe data/factory reset from ClockworkMod Recovery?
Click to expand...
Click to collapse
You were the one who mentioned a full wipe! I thought that was what you meant.

Droidzone said:
You were the one who mentioned a full wipe! I thought that was what you meant.
Click to expand...
Click to collapse
The installation instructions mention a full wipe but reading further it does mention a factory reset so its ok. Will let you know how I get on once the kids are in bed.

Right after some messing about I've had some success. I booted back into Android once I'd used GParted and after a while it saw my SD Card ok.
My Windows PC only saw 12.9GB (of a 16GB card), my phone saw the full 14.9gb in Android and GParted saw both partitions.
As I'd just done a factory reset and my PC saw my Phone I transferred the ROM File to my memory card and installed.
As I had downloaded the Extreme edition I followed the Classic install instructions as instructed and rebooted (after booting to android after install).
The LEd flashed green a couple of times as mentioned but then stopped and is now stuck on the htc screen.
Am I right the file I installed (Supernova_2.4.0.0_signed) is the classic version? Should I have downloaded a sepaerate file for the A2SD installer? The instructions don't seem to suggest this.
And most importantly how do I get my phone to work? lol, please help!
Update: Before I installed the ROM it was showing up correctly in GParted and in Windows it was only showing the Fat32 section which I assumed to be correct. After removing the battery I am back to starting up as normal (with the new Custom ROM) but the SD Card will not show up in GParted and will only allow me to use in Windows if I format first which I havent done. Therefore I can only conclude the file system has got lost somewhere which is why the A2SD installer crashed.
I've very happy with the improved ROM but I still don't have extra stoarge space which was the whole point in upgrading.
Any idea where I can go from here?

The file is right. However I cant suggest anything until you follow the proper reporting format and pull logs from your phone as per post #3 of supernova thread. The report should be filed in the Supernova thread or on the Supernova Forum at droid-force.com

Droidzone said:
The file is right. However I cant suggest anything until you follow the proper reporting format and pull logs from your phone as per post #3 of supernova thread. The report should be filed in the Supernova thread or on the Supernova Forum at droid-force.com
Click to expand...
Click to collapse
OK fair enough will do, where do I post it though? just in the Help and troubleshooting thread I take it?

Steveh8204 said:
OK fair enough will do, where do I post it though? just in the Help and troubleshooting thread I take it?
Click to expand...
Click to collapse
To be honest I'm starting to think the problem lies with CWM Recovery.
Is it easy to downgrade as I am on 4.0.1.4?

Steveh8204 said:
To be honest I'm starting to think the problem lies with CWM Recovery.
Is it easy to downgrade as I am on 4.0.1.4?
Click to expand...
Click to collapse
Take my advice and move over to 4ext recovery.. It's the best atm.. you'll love it.
Edit:
I saw your post at droid-force.com and have responded to it there/

[Q] SD CARD being read but cant flash?

Hi guys okay so i have a problem. i have cwm recovery and i have slim bean on my s4 installed and the thing is i i tried flashing a rom from my external sd card 32gb and it automaticallly fails no matter how many times i try and its fat32 aswell thats what it says on its properties. But when i move the rom to my phone memory it flashes just fine so what is the matter here? If someone could help ASAP that would be awesome

zee24 said:
Hi guys okay so i have a problem. i have cwm recovery and i have slim bean on my s4 installed and the thing is i i tried flashing a rom from my external sd card 32gb and it automaticallly fails no matter how many times i try and its fat32 aswell thats what it says on its properties. But when i move the rom to my phone memory it flashes just fine so what is the matter here? If someone could help ASAP that would be awesome
Click to expand...
Click to collapse
Backup your SD card data, reformat the SD card. And restore the data, should work. However, the issue i was having with flashing ROMs was not due to SD card issues, but my actual data partition was corrupt and using CWM i formatted my entire data partition and everything flashed properly then.

elesbb said:
Backup your SD card data, reformat the SD card. And restore the data, should work. However, the issue i was having with flashing ROMs was not due to SD card issues, but my actual data partition was corrupt and using CWM i formatted my entire data partition and everything flashed properly then.
Click to expand...
Click to collapse
HEY i tried re formatting the card but still sometimes it works other times it doesnt flash it makes no sense to me, sometimes i flash an 19505 rom and it works other times the same rom says installation aborted so then i install an 1337m rom and it works and 19505 ddoesnt i honestly am so confused why the hell is cwm doing this? Sometimes it flashes a rom and other times the same rom doesnt flash??? Can you tell me what you formatted from cwm so i can try that too

-_-
elesbb said:
Backup your SD card data, reformat the SD card. And restore the data, should work. However, the issue i was having with flashing ROMs was not due to SD card issues, but my actual data partition was corrupt and using CWM i formatted my entire data partition and everything flashed properly then.
Click to expand...
Click to collapse
And now the roms wont even flash from my internal memory either wtf??? I think twrp might be a better recovery i might ue that insted of cwm im thinking cwm is the problem

zee24 said:
And now the roms wont even flash from my internal memory either wtf??? I think twrp might be a better recovery i might ue that insted of cwm im thinking cwm is the problem
Click to expand...
Click to collapse
Back up your internal SD card and wipe the data partition completely. Youre having the exact same issues i was. its not the recovery, TWRP sucks imo

elesbb said:
Back up your internal SD card and wipe the data partition completely. Youre having the exact same issues i was. its not the recovery, TWRP sucks imo
Click to expand...
Click to collapse
^ What he said. Never had a problem with Philz but more than a few with TWRP.

elesbb said:
TWRP sucks imo
Click to expand...
Click to collapse
Amen brotha, amen. :highfive:

Unnessasary hate
Lol why you guys hating I got twrp and did what you said and all seems to be good I think twrp is better because in twrp there's a key important feature which is a file manager built in let's you move zips from sd card to internal or vice versa cwm doesn't have that

zee24 said:
Lol why you guys hating I got twrp and did what you said and all seems to be good I think twrp is better because in twrp there's a key important feature which is a file manager built in let's you move zips from sd card to internal or vice versa cwm doesn't have that
Click to expand...
Click to collapse
It has some nice features but for me, the only real functions for recovery are:
1) Wipe data/cache/dalvik and some other mounts.
2) Nandroid backup and restore.
Don't have any other needs, and CWM hasn't given me any troubles in ages, TWRP on the other hand... But if CWM had the file manager, it would make it that much better for me.