[Desire Android Development] wensuan:
Error in installation

Dear all. I encountered an error during installation of the Supernova ROM. Root, H-Boot, Partition SD seemed all OK. At the reboot after installing the rom when the data2ext should auto install, at the "why so serious screen", I got the pink LED for a while, then a flash of blue LED, and then stuck.

Please find the form bellow and the attached log file.

Any help will be great!

1. Are you using an HTC Desire GSM phone (codename ‘bravo’)?…………………………………….Yes, it is HTC Desire GSM

2. Flash the Getlogs Flashable Tool and attach /sdcard/Data2SDlog.tar.gz (rename to .zip if necessary). Have you attached it to the post in XDA? (If you havent, nobody can help you!)…………………………………….Yes, see attached

3. Size of sdcard used…………………………………….Transcend 16GB Class 6

4. Size of each partition created and type of partitions made (Fat32, Fat, ext2, ext3 or ext4), whether each partition was Primary or secondary…………………………………….Created 2 partitions in Gparted: one Fat32 primary 14000MB and the other Ext4 primary the remainder (around 1250MB)

5. Whether you are S-OFF or S-ON (If you dont know what this is, press Power and Back button to boot to Hboot mode and see what it reads there: S-OFF or S-ON)…………………………………….S-OFF by Alpharev

6. Have you changed your Hboot type with Alpharev? If so, what kind of Hboot do you currently have (Bravo Stock/Bravo N1Table/Bravo Data++/Bravo Sense/Bravo Oxygen r2/Bravo CM7 r2)?…………………………………….As shown in the hboot screen BRAVO PVT4 ship S-OFF and HBOOT-0.93.0001 Microp-051d

7. What is the order of your partitions and the number of partitions (Eg: Two partitions; Fat32 Primary first, ext4 primary second)? Created 2 partitions in Gparted: first one Fat32 primary 14000MB and the second one Ext4 primary the remainder (around 1250MB)

8. Software used for partitioning (Gparted, 4Ext recovery, Amon Ra recovery etc)…………………………………….Gparted 0.9.0.7

9. Recovery Software installed, with version and subversion number (Eg: 4Ext 2.0.1/Clockworkmod 3.0.0 R3)…………………………………….CWM-AlphaRev Recovery v2.4.1.8

10. Detailed account of steps you did for the procedure, with output/errors at each step as received from the Recovery/Partitioning software…………………………………….Not that I have noticed. Seems OK all along.

11. Did you do a full wipe from Recovery before installation? It was a new installation from a stock ROM. Following your installation guidelines, so I only did Wipe Data/Factory reset in Recovery

12. Did you do any additional wipe in between flashing the Rom and the Data2installer (if applicable)?…………………………………….Nope, since I had S-OFF, no Data2installer required. I got stuck when it was autoinstalling the data2.

13. If you didnt wipe and did an upgrade, what ROM were you running previously?…………………………………….Not applicable. New installation.

14. Version of the ROM you installed, and the names of the Data2SD installer/reinstaller flashable zips you used (if any.)…………………………………….Supernova_2.4.0.0_signed.zip

15. If you’re using a custom kernel, full name of the kernel with author name, the kernel voltage if known, whether you have an overclocked/undervolted configuration…………………………………….Did not flash any custom kernel.

16. Did you install any custom theme? Which one? No custom themes

17. Did you flash any addons (mine or otherwise)? List them……………………………………..Nope

18. Did you get any of the following messages in recovery? …………………………………….

1. sd-ext could not be formatted, file already exists?…………………………………….Nope

2. Failure mounting ‘sd-ext’…………………………………….Nope

3. Or a message similiar to the above (Hint: This means your device is USB bricked)?…………………………………….Nope

19. Step at which major error was noticed…………………………………….At the reboot after installing the rom, when the data2ext should auto install. At the "why so serious screen", I got the pink LED for a while, then a flash of blue LED, and then stuck.

20. Recovery log as per the procedure detailed below……………………………………..

21. Any additional info you think is relevant…………………………………….Not that I could think of

22. Note: Attaching an adb logcat is extremely useful (though optional) for understanding any issues. Have you attached one as a text file?…………………………………….Not at the moment