Related
Hi.
I was checking each build today and noticed that the file structures between builds are different. Example, Matt's or Darkstone's has a rootfs.img and system.ext2 while shubcraft has htcleo_update.tar.gz and root folder, but no system.ext2 nor rootfs.img.
How come the structures are different? Hopefully one or some of the devs can chime in on this.
Oh and how come the initrd.gz cannot be extracted? I tried extracting one and when I opened it I saw a bunch of garbled syntax....
Thanks
i'm not a dev so i can't be 100% sure on this. i can tell you that when i load shubcraft's build up for the first time... the first screen says it is a htc hd2 on the setup screen. the other 2 say n1 or desire i think.
so my guess would be that shubcraft's build is more modified and the others is more image based from the other phones.
1 reason i loved shubcraft's build was that it kept my phone named correctly. i don't like going into my phone's about screen and seeing it named n1 or desire... cause it's not... heh, i have a HD2 and i'm proud of it dangit! =)
w0LfNiNja said:
i'm not a dev so i can't be 100% sure on this. i can tell you that when i load shubcraft's build up for the first time... the first screen says it is a htc hd2 on the setup screen. the other 2 say n1 or desire i think.
so my guess would be that shubcraft's build is more modified and the others is more image based from the other phones.
1 reason i loved shubcraft's build was that it kept my phone named correctly. i don't like going into my phone's about screen and seeing it named n1 or desire... cause it's not... heh, i have a HD2 and i'm proud of it dangit! =)
Click to expand...
Click to collapse
Actually, ita very easy to change the phones name on Android, im on Darkstones Froyo v1 and i changed it from saying" HTC Desire" to "HTC Leo" going to switch it back to HD2 tho. But the filesystems im not to sure about.
Sent from my HTC HD2 running DarkStone HD2Froyo v1
It's just because Shu8i do not supply system and userdata images with it's build, instead he relay on creating that files on first start of Android, that is the main reason Shu8i's build take so much more time to start up at first.
It's just a trade-off, less file size you download, more time to wait for first boot.
bangsters said:
Hi.
Oh and how come the initrd.gz cannot be extracted? I tried extracting one and when I opened it I saw a bunch of garbled syntax....
Thanks
Click to expand...
Click to collapse
It can just use
gunzip initrd.gz
cpio -d -i < initrd
Its a gzipped cpio file
mr_billionaire said:
Actually, ita very easy to change the phones name on Android, im on Darkstones Froyo v1 and i changed it from saying" HTC Desire" to "HTC Leo" going to switch it back to HD2 tho. But the filesystems im not to sure about.
Sent from my HTC HD2 running DarkStone HD2Froyo v1
Click to expand...
Click to collapse
guess i'm not that smart just yet. heh.
There are currently (from the files I've checked) two ways of packaging Android builds; the "Zego" way and the "XDAndroid" way.
Inside both builds, you'll find a haret (kernel loader), clrcad (enables audio in android), initrd.gz (initial root filesystem), zImage (kernel), and startup (the script haret uses to set up linux).
The XDAndroid-based builds have, additionally, a rootfs which is a big package intended to allow the same XDAndroid build to run on a wide variety of devices.
IMHO, the Zego initrd is much better because: 1. it allows for "otapackage" updates, 2. It's for HD2 only, 3. It's much cleaner and can run AOSP builds straight from a make (as long as you specify that the build images use ext2).
The disadvantage, though, is that it uses a regular init.rc instead of a hero one (only difference is that hero core jars aren't loaded into the classpath), so it takes a slight modification to get sense builds running.
The XDAndroid initrd, instead, just loads the rootfs and then from the rootfs several scripts run to determine the kind of device that's being used and then when the device is detected, the files used for that device (included in the rootfs) are "pushed" to the system image to allow all hardware to work correctly.
Hello,
I think there are phones (like mine) that doesn't work right with android os. I tried a lot of builds and most of them crashes while booting.
With WMO the phone WORKS PERFECT!!
I tried
-task29,
-rewrite radio (2.12.50.02_2)
-Change a lot of SDCards of different marks. Formatting with panasonic tool and XP format at diferents cluster size (16k and 32k)
-rewrite WMO ROM (without 2.14 drivers) a lot of times.
I think there is something in the HW that hangs on booting process. Maybe setting the vdd of voltage regulator becouse some builds crash inmediatly after of this message.
I only have 3 functionaly builds (only with any seconds screen freezes):
mattc froyo sense 1.7
mdeejay froyo sense 2.0
mdeejay froyo sense 2.1
The rest are crashing!!!
Im going to put android boot logs with the hope that some good developer can determine this bug.
HANGS WHILE WHITE HTC WHITE SCREEN. Sometimes boot itselfs
-Shubcraft 1.5
http://pastebin.com/HH1ayhvF
-Hyperdroid 1.2
http://pastebin.com/RR1RXStG
-Froyostonev2
(no paste bin yet available)
HANGS WHILE ANDROID TEXT LOGGING
-Bangsters1.3b: Last line: Slab Corruption
http://pastebin.com/jtd52ZGb
-mdeejay sense 1.3b: Last lines: acpuclk_set_vdd_level got regulator. BUG: workqueue. leaked lock or atomic
(no pastebin yet available)
Thanks for any help!!
Reading your post it seems you've tried almost everything, so just keep trying different radios and roms. And hope!! For everyone else who's confused about what to do when android wont boot:
1) Install Chuckys Droid Rom with the recommended radio, i believe 2.11/2.10 is the most stable.
2) Format your SD Card in Ubuntu as MBR then create a single FAT Partition. This is because once the partitioning is messed up xp cant fix it, this was the only way i found to get mine to boot properly.
3) Choose your android build carefully, my best luck has been with the CM6 based versions. As far as I know Shubcraft 1.5 is the most stable, but hyperdroid is very close and faster. If you use hyperdroid make sure you edit the startup.txt as the path to the android folder is incorrect and will fail to boot.
4) Enjoy Android!!
OK, here is my problem.
UK HD2 -> Generic running 1.66 stock, with HSPL 2.08, and Radio 2.12.50.02.
I have been running many of the different Android builds on my phone since the first one came out with no problems, until now...
My phone will not run any of the new ones at all. They give the instruction to leave on first boot to create the data store, takes about 5-10min. I have left my phone for hours with a faded black screen, with a few lines on it, but it never gets any further than that.
Have tried:
Mattc Leo + Froyo 1.5*, 1.6*, 1.7 and 1.8
Mattc Evo 1.0.1
Mattc NexusLeo 1.1
Mdeejay Froyo Sense 2.2
Mdeejay eVo 1.0
FroyoStone Sense 1* and 2
Darksotne HD2Froyo 2.1*
Darkstone DesireROM 2*, 3*, 4* and 5*
*= ones that have worked
It seems to me that something has changed with all the newer ROMS that are stopping them from working for me. I have format my SD every time i try a new ROM and have even hard reset my WinMo to see if that the problem -> Nothing works!
As Marvin would say: "I just want you to know, i am feeling very depressed today"
Help please
SquithyX said:
OK, here is my problem.
UK HD2 -> Generic running 1.66 stock, with HSPL 2.08, and Radio 2.12.50.02.
I have been running many of the different Android builds on my phone since the first one came out with no problems, until now...
My phone will not run any of the new ones at all. They give the instruction to leave on first boot to create the data store, takes about 5-10min. I have left my phone for hours with a faded black screen, with a few lines on it, but it never gets any further than that.
Have tried:
Mattc Leo + Froyo 1.5*, 1.6*, 1.7 and 1.8
Mattc Evo 1.0.1
Mattc NexusLeo 1.1
Mdeejay Froyo Sense 2.2
Mdeejay eVo 1.0
FroyoStone Sense 1* and 2
Darksotne HD2Froyo 2.1*
Darkstone DesireROM 2*, 3*, 4* and 5*
*= ones that have worked
It seems to me that something has changed with all the newer ROMS that are stopping them from working for me. I have format my SD every time i try a new ROM and have even hard reset my WinMo to see if that the problem -> Nothing works!
As Marvin would say: "I just want you to know, i am feeling very depressed today"
Help please
Click to expand...
Click to collapse
show us your step by step procedure in running android, so people when they see it may know at which point you may be making an error.
also, after reading this
post, I came to the conclusion that indeed many left
over junks in winmo are messing up the process of Android running, so I took it to mean that we have to do a Task 29 every time we try a build.
make sure the android build is in a folder marked android the older roms went on the root of the sd! another thing is when haret boots see if the writing says failer to mount sd and get back to me or pm me well figure it out!!
Definitely task29 that sucker. Also consider a "meant for android" WM rom like chuckydroid. Radio 2.14 is now available if you want to try something else.
polo735 said:
Definitely task29 that sucker. Also consider a "meant for android" WM rom like chuckydroid. Radio 2.14 is now available if you want to try something else.
Click to expand...
Click to collapse
Yeah, I was going to suggest task 29 and then reinstall a different WM Rom.
I am using the 2.14 radio with great results.....
Good Luck.
try new sd card
I can understand your frustration, If the task 29 alone does not help, I would get a new sd card, I have read its best to long format card, task 29 phone, install your windows rom of choice( I like chuckys android), then install android. good luck
Steps taken so far
Ok, first off, Thank you all for your responses!!!!
Was expecting to get flamed, as i had searched the forums and could not find anything myself but expected there to be something somewhere, that somebody knew about.
With the older ROMS that are stored on the root of SD, i formatted the SD and copied the data over using SD adaptor in my MacBook Pro's SD slot -> Worked like a charm!!
With the newer ones, that have worked anyway the procedure was the same, format SD and copy Android folder over from Mac -> again worked like a champ!
But now with these new ones i have tried the old methods of format and copy using SD adaptor, tried formatting and coping the Android folder on to the phone using the USB connection on the phone, tried renaming the "Android" folder "android".
I have not updated or changed the WinMo ROM, but i have reloaded it, when i found out about this problem. I task 29 and then reflashed with the stock 1.66 and still no dice.
Step by step for last ones i have tried:
1. Power off phone and remove battery (not needed i know but hay)
2. Remove SD card and put in SD adaptor
3. Insert into Mac and format card Fat (Mac Fat = Win Fat32)
4. Unarchive Android ROM and copy to SD - (/StorageCard/Android)
5. After copy complete wait for 5min then eject SD (i like to make sure there is nothing in the buffer)
6. Put into phone, put battery in and power up (normally with the battery cover off lol)
7. Wait for the unfortunate Windows logo and phone to boot up ("Launching HTC Sense" seems to take forever)
8. As soon as phone started either run the Android icon from Sense or open File Explorer and run both programs
9. HeRET starts, screen goes black see txt (guess bootloader loading the kernel) for 1 second then screen fades to black with faint lines running down it (backlight on very dull)
10. Wait...wait...wait (Mattc Leo Froyo 1.8 waited 20min, then fell asleep and when i awoke 5hours later it was still the same)
I dont get it, so to recap i have formatted my SD every-time i have tried, i have task29 my phone about a week ago, tried many of the ROMS on here and nothing, i have tried one of the old ones and that works though!!!!
Arrrgg, Please somebody point out what stupid thing i am doing wrong.
"Even the doors don't like me!"
Could this be it?
I have spent more time reading forums and such like, could it be due to the fault described here in this post?
http://forum.xda-developers.com/showthread.php?p=8264796
If you are using a standard stock 1.66 rom your radio may not be compatable. I had the same issue to start off with. Would boot half way then die. I upgraded my radio now using 2.14 and can boot no problem at all.
SquithyX said:
Ok, first off, Thank you all for your responses!!!!
Was expecting to get flamed, as i had searched the. . . . . . or changed the WinMo ROM, but i have reloaded it, when i found out about this problem. I task 29 and then reflashed with the stock 1.66 and still no dice.
Step by step for last ones i have tried:
1. Power off phone and remove battery (not needed i know but hay)
2. Remove SD card and put in SD adaptor
3. Insert into Mac and format card Fat (Mac Fat = Win Fat32)
4. Unarchive Android ROM and copy to SD - (/StorageCard/Android)
5. After copy complete wait for 5min then eject SD (i like to make sure there is nothing in the buffer). . . . .
Click to expand...
Click to collapse
I have experimented with Stock UK WWE 1.66 about two weeks ago, and no matter
what Radio and HSPL I put on it, once I clicked on Haret, it goes exactly like you describe it
White faint lines all over the screen which seems like very fine drops of rain.
you can always try Winmo ROMs specifically made to be Android friendly.
also it would be valuable if you read this Thread read
at least the first and 13th post
Good staff
I have already installed several androids and they all happen and then install it works fine until the restart after that never get put to work again!
What am I to fail!
Help please!!
HTC HD2
★ |Artemis HD2 ROM Family Ver 35.0 Gen III | ★
ROM date: 17.09.2010
Radio version: 2.14.50.04
HSPL2: 1.66HSPL
Protocol version: 15.42.50.09U
Manila version: v2.5.20191914.0
WinMO: WM 6.5.5 Professional COM5 Build 23578
Android:● SEVERAL
Wow. If I understand you correctly, this has been SOOOOO covered in this forum.
The HD2 does not BOOT to Android unless you have set up a special program that STILL loads Windows Mobile first and then boots to Android.
You always have to run CLRCAD and HARET from your Android folder on your SD card, EVERYTIME you reboot. There are programs that automate this if you do a SEARCH.
J
Thanks for your response
I always do the same, and similarly, that is the way you have mentioned!
But it only works once after turning off or renice do the same and already works if you delete and re-paste it all makes work on sd!
U have several android builds ................ duh................... each folder is on the root of your SD card so Windows doesn't know which build to load since each build has an Android name on it. Rename each folder and its startup text to match it.
If its not that then I'm not sure what your talking about.
I think its your radio version, your using 2.14.xxxxx but you should only use up to 2.12.xxxxx see the following thread.
http://forum.xda-developers.com/showthread.php?t=732380
First of all, I know there are "many" Android Install Help! thread and I have gone thorough so many of them if those information would help my problem but unfortunately they did not help...
I'd gone thorough this post very carefully at least 10 times
http://forum.xda-developers.com/showthread.php?t=653614
and I've been suffering to install almost all Android ROM on my T-Mobile US HD2 over 4 weeks so I finally decided to post my issue for help!
My current environment:
- T-Mobile USA (TMOUS) HD2
- HSPL3
- Radio: 2.12.50.2_2
- WM ROM: Dutty's N4S v3 & Co0Kie 1.8.1
Note: WM works really well and very stable
PC environment
- Windows XP SP3 English
- Windows XP SP3 Japanese
* Both Windows are different box and used for flashing WM ROM and Radio. They both do the job without any error. BTW, Current HD2 was flashed with English XP for ROM and Radio.
- MacBook Pro: Snow Leopard: Mostly used for data transfer (movie, music, etc). I use "GS Finder" to globally search and trash "._*" files occasionally to clean the garbage made by OSX.
My current ROM flashing process are as follows:
1) Boot Loader:
Already have installed HSPL3 and have installed many Custom WM ROMs.
2) Format SD Card:
Using "Panasoic SD Format app"
http://panasonic.jp/support/global/cs/sd/download/sd_formatter20.html
Tried all combination of Format as
[Quick] [Erase ON] [Erase OFF] and Resize [ON] [OFF]
Also, I format my microSD from HD2 as well. Cluster size is shown as "32K" when format with WM SD card format app.
Any suggestion of recommended combination of formatting microSD?
I have two microSD cards:
a. Kingston 16GB class 4
b. 3C Pro 16GB class 6
Both benchmarked and confirmed that they're not "fake" class 4 nor class 6.
3) Run "Task29":
To clean the garbage off from HD2.
http://forum.xda-developers.com/showthread.php?t=644781
4) Flash WM ROM:
Currently, I'm using Dutty's N4S v3 as WM ROM. I also have tried many Android ROM + Recommended WM ROM + Radio, such as "ShubCraft STOCK 1.5+ChuchyDroid+Radio 2.10.50.26", or "mccm 1.5 + OzDroid 1.11 + Radio 2.14.50.04", "HD2Froyo V2.1 + Energy Leo COM2 Barebones WM Build For Android + Radio 2.14.50.04"
and many more recommended combos. Unfortunately, none of the combo really helped.
5) Hard Reset:
As many threads suggested, I also made sure to hard reset after WM ROM Flash.
6) Settings from WM:
Make sure to turn "Off" for "Automatically adjust backlight" from WM. Also, set volume as "one volume" (not separate ringer and master). Check off all "Screen Dim, Sleep" check boxes.
7) Start Android:
Copy "Android" folder to the "Root" of microSD card. Run "CLRCAD.exe" then "haret.exe" to boot Android ROM.
Since the log flows goes soooo fast that makes difficult to read the messages but at least there are consistency in any Android ROM that complains "No such a file or folder. Cannot create xxx" type of error during install.
When/How trouble started:
For my 1st week of using HD2 with Dutty's Creme de la Creme v3 and v5, ShubCraft and few other ROM were working OK (I believe I was also trying mattc 1.7 Froyo w/Sense).
One day, I tried "HyperDroid v1.1" then Android did not load anymore. Since then, some Android ROM just "Vanishes" when tried to load and freeze (like mattc Froyo w/sense 1.8). Many of ROMs just freezes at "HTC" logo (I wait at least 60 min to give enough time to let ROM start, but they're simply freezes… I bet 60 min is enough to boot, isn't it?).
Only Android ROM which "berely" work is "mattc Froyo w/sense 1.7" but still freezes at least 10 times a day. Mostly, Sleep of Death but many occasion activate/deactivate WiFi triggers freeze, too.
… I have been trying resolve my issue over 4 weeks now, and spending too much time and effort on this and I'm eager to resolve it!! I believe I tried almost every tips suggested on forum but I'm also certain that I must have missed something. Please suggest anything if you think I'd missed something I mention above.
PLEASE HELP!!
(or should I wait some super-chef will release NAND flash version Android?)
taka_mass said:
First of all, I know there are "many" Android Install Help! thread and I have gone thorough so many of them if those information would help my problem but unfortunately they did not help...
I'd gone thorough this post very carefully at least 10 times
http://forum.xda-developers.com/showthread.php?t=653614
and I've been suffering to install almost all Android ROM on my T-Mobile US HD2 over 4 weeks so I finally decided to post my issue for help!
My current environment:
- T-Mobile USA (TMOUS) HD2
- HSPL3
- Radio: 2.12.50.2_2
- WM ROM: Dutty's N4S v3 & Co0Kie 1.8.1
Note: WM works really well and very stable
PC environment
- Windows XP SP3 English
- Windows XP SP3 Japanese
* Both Windows are different box and used for flashing WM ROM and Radio. They both do the job without any error. BTW, Current HD2 was flashed with English XP for ROM and Radio.
- MacBook Pro: Snow Leopard: Mostly used for data transfer (movie, music, etc). I use "GS Finder" to globally search and trash "._*" files occasionally to clean the garbage made by OSX.
My current ROM flashing process are as follows:
1) Boot Loader:
Already have installed HSPL3 and have installed many Custom WM ROMs.
2) Format SD Card:
Using "Panasoic SD Format app"
http://panasonic.jp/support/global/cs/sd/download/sd_formatter20.html
Tried all combination of Format as
[Quick] [Erase ON] [Erase OFF] and Resize [ON] [OFF]
Also, I format my microSD from HD2 as well. Cluster size is shown as "32K" when format with WM SD card format app.
Any suggestion of recommended combination of formatting microSD?
I have two microSD cards:
a. Kingston 16GB class 4
b. 3C Pro 16GB class 6
Both benchmarked and confirmed that they're not "fake" class 4 nor class 6.
3) Run "Task29":
To clean the garbage off from HD2.
http://forum.xda-developers.com/showthread.php?t=644781
4) Flash WM ROM:
Currently, I'm using Dutty's N4S v3 as WM ROM. I also have tried many Android ROM + Recommended WM ROM + Radio, such as "ShubCraft STOCK 1.5+ChuchyDroid+Radio 2.10.50.26", or "mccm 1.5 + OzDroid 1.11 + Radio 2.14.50.04", "HD2Froyo V2.1 + Energy Leo COM2 Barebones WM Build For Android + Radio 2.14.50.04"
and many more recommended combos. Unfortunately, none of the combo really helped.
5) Hard Reset:
As many threads suggested, I also made sure to hard reset after WM ROM Flash.
6) Settings from WM:
Make sure to turn "Off" for "Automatically adjust backlight" from WM. Also, set volume as "one volume" (not separate ringer and master). Check off all "Screen Dim, Sleep" check boxes.
7) Start Android:
Copy "Android" folder to the "Root" of microSD card. Run "CLRCAD.exe" then "haret.exe" to boot Android ROM.
Since the log flows goes soooo fast that makes difficult to read the messages but at least there are consistency in any Android ROM that complains "No such a file or folder. Cannot create xxx" type of error during install.
When/How trouble started:
For my 1st week of using HD2 with Dutty's Creme de la Creme v3 and v5, ShubCraft and few other ROM were working OK (I believe I was also trying mattc 1.7 Froyo w/Sense).
One day, I tried "HyperDroid v1.1" then Android did not load anymore. Since then, some Android ROM just "Vanishes" when tried to load and freeze (like mattc Froyo w/sense 1.8). Many of ROMs just freezes at "HTC" logo (I wait at least 60 min to give enough time to let ROM start, but they're simply freezes… I bet 60 min is enough to boot, isn't it?).
Only Android ROM which "berely" work is "mattc Froyo w/sense 1.7" but still freezes at least 10 times a day. Mostly, Sleep of Death but many occasion activate/deactivate WiFi triggers freeze, too.
… I have been trying resolve my issue over 4 weeks now, and spending too much time and effort on this and I'm eager to resolve it!! I believe I tried almost every tips suggested on forum but I'm also certain that I must have missed something. Please suggest anything if you think I'd missed something I mention above.
PLEASE HELP!!
(or should I wait some super-chef will release NAND flash version Android?)
Click to expand...
Click to collapse
Tr ythis: http://leoandroid.com/viewtopic.php?f=212&t=168
maybe its the SD card; i tried one i had before to keep from possibly frying my 16gb and couldn't get anything to really work though it was only 2gb.
On my pc I backed up the orignal tmo usa 16gb class 2 card via a usb reader, formated it; copied android over i'm using "[BUILD][17.10.2010][FroyoStone Sense - V3.2][Kernel: linux_on_wince_htc 2.6.32.15]" I then all my other stuff; put the sd card back in my phone, installed Android Launcher 4.0 on winmo and i've been good since!
This is on a tmo usa hd2 w/ the latest radio and an Energy windows rom (obviously hardspl'd)
the install was quite easy for me... thats why I think its maybe your SD card. AFter digging around a bit it seems the sd card is the main factor in a happy hd2 android experience so far my original 16gb is kicking ass
I'm inclined to blame the SD card as well. The other issue it sounds like is your phone is messed up. Sorry I know I'm not much help. Good luck with everything.
Edit: try one of the later radios. I switched to 2.14.50 and haven't had hardly any problems since.
Thanks AMCJUNGLE! I'll go through your suggested link. "HTC Sync" and "Boot Android when boot Win ROM for first time" are new info to me (Step 9 and 10). I'll also try to run with suggested WM ROM and Android ROM as well and see if it does the trick!
Thanks computerjlt!
Yeah, I also accuse SD card is the core of this cause but I also formatted SD soooooo many times. Using "Windows Explorer", "Panasonic SD Format app", "Win XP Manage Computer > Disk Management", etc. Also, Disk Management will allow me to select the "cluster size" so I set it to 32K and 64K as well, but no luck.
I'll try your suggested WM/Android ROM Combo if AMCJUNGLE's link would not do the trick.
Thanks dung8604! I'm really hoping my phone is not messed up (T-T)
Yep, I tried 2.14.50 and 2.15.50 (the latest Radio) as well with Dutty's WM ROM but it did not fix the problem.
My plan is to stick with recommended WM ROM + Radio + Android ROM first, then if it would fix my situation, I'll upgrade my Radio with the latest for better signal and less battery drain. I'm really hoping to do this sometime soooooooon!!
Bad Disk Sector = Broken microSD?
OK, I tried this method with very detailed instruction suggested by AMCJUNGLE
http://leoandroid.com/viewtopic.php?f=212&t=168
Still no luck
As many other mentioned, it could be microSD causing this problem.
From my Mac, I used DiskUtility and FastAid returns no error. However, I tried "fsck" from terminal, I got this:
THE FOLLOWING DISK SECTORS COULD NOT BE READ: 16, 17, 18, 19, 20, 21, 22, 23, 24, 25, 26, 27, 28, 29, 30, 31,
ioctl (GCINFO): Inappropriate ioctl for device
fsck: /Volumes/SDCARD: can't read disk label
Does this mean my microSD is damaged? If so, is there way to fix it?
Hmm. Chkdsk from XP still returns "No Error"... Mystery continues
taka_mass said:
OK, I tried this method with very detailed instruction suggested by AMCJUNGLE
http://leoandroid.com/viewtopic.php?f=212&t=168
Still no luck
As many other mentioned, it could be microSD causing this problem.
From my Mac, I used DiskUtility and FastAid returns no error. However, I tried "fsck" from terminal, I got this:
THE FOLLOWING DISK SECTORS COULD NOT BE READ: 16, 17, 18, 19, 20, 21, 22, 23, 24, 25, 26, 27, 28, 29, 30, 31,
ioctl (GCINFO): Inappropriate ioctl for device
fsck: /Volumes/SDCARD: can't read disk label
Does this mean my microSD is damaged? If so, is there way to fix it?
Click to expand...
Click to collapse
If your card is damaged you cannot fix it. You need to replace it.
AMCJUNGLE,
It sounds like have a bad news. What I did was checking microSD using
From XP: Chkdsk e:\ >>>> OK. No problem found.
From XP: Run Disk Analyze tool called "FromHDDtoSSD" to run "full analyze".
>>> OK. No bad sector is found and reported 100% clean disk.
From OSX 10.6: Disk Utility to Check/Repair Disk and got this and not problem.
Verify and Repair volume “NO NAME”
** /dev/disk2s1
** Phase 1 - Preparing FAT
** Phase 2 - Checking Directories
** Phase 3 - Checking for Orphan Clusters
55 files, 15645504 KiB free (488922 clusters)
Volume repair complete.Updating boot support partitions for the volume as required.
However, if I test fsck from OSX Terminal against mounted microSD by
fsck /dev/rdisk2s1
result returns as
BAD SUPER BLOCK: MAGIC NUMBER WRONG
By some research, "BAD SUPER BLOCK: MAGIC NUMBER WRONG" is caused by area of Administrative File Management info is damaged or broken. In short, my microSD is screwed up...
Fixed... somehow
OK, still using same WM ROM (Dutty NS4 v3), same Radio (2.10.50.2_2), but suddenly, "HD2Froyo V3" WORKED!!
No Sleep of Death, no freeze, OS behaves very fast and stable. In addition, Skype 3G Mod works 100% (it didn't with mattc 1.7).
I still have no clue what went well because so many other new roms (such as ShubCraft 2.0, mdeejay eVo Sense v. 2.3, etc).
Anyway, I'm super happy now and I will definitely keep the current environment until Android allow NAND install. Yey!