Database Users

Please HELPPPP!!!!!!!

Hello everyone
I have a big problem trying to solve a long time but I must admit that I give up
I tried to install nearly all versions of Android but after about 10 minutes I get stuck and have to remove the battery. On reboot it gives me nand faild to boot of nand and have to reinstall again
I have T-Mobile USA
Thanks
Please excuse me for my English

How are you Flashing your build? DAF or ZIP?
If ZIP, Try wiping everything before installing new build (Cache, data, and dalvik cache (it's in the advanced tab))
If that doesn't work, Task 29 -> MAGLDR -> Either CWM or DAF Android.

If you had this problem, than start from "0".
That means, format your sd-card and task29.
Good luck

Thanks for the replies.
I tried everything, including the original ROM installation, from t-mobile and everything hangs on restart

Nand Android not booting thru cwm Recovery

Hey,
I tried installing Android using cwm rec., everything goes well, but the android does not boot, it gets stuck on the booting screen, i tried several time, diff roms, still no results, can any one help me if im missing something? :S

make sure you are removing any leftover stuff from a previous rom on the SD card.
So in CWM, before you go to flash the rom, do a 'wipe data/factory reset' which should clear out the ext partition and the .androidsecure (or whatever its called) folder on the FAT32 partition.

I have done that, but it wont work, i've cleared cache too,
Btw how much time does it take on the first boot?

dont know, sorry, i've never used a sense rom, but i've seen posts referring to a good ten minutes or more, depending on the sd card and teh rom being installed, and how much stuff is moved to sd. Some roms just put just the app and dalvik folders there, some put much much more.
If it were me, i recon id be pulling teh battery at 10 mins.

do you have a 1gb partition on your sd card?
is the partition information for the rom correct?
are you using magldr or clk?

I have Tried wit a 2GB and a 1GB partition, I have Magldr 1.13, The Cwm size is also correct, 400mb for a 300mb rom.

amigo max said:
I have Tried wit a 2GB and a 1GB partition, I have Magldr 1.13, The Cwm size is also correct, 400mb for a 300mb rom.
Click to expand...
Click to collapse
You're absolutely sure the ROM you're trying to use is correct for the type of Android bootloader you have? (clk/magldr)
Did you check the MD5 sum of the rom.zip you downloaded? Maybe you got a bad download.
Did you wipe EVERYTHING? (full wipe, then in advanced, wipe dalvik and cache)
What method did you use to partition your sd card?

For now i Have followed the exact instructions from the DHD Desire rom, and it seems to work, I think the problem was wit the CWM recovery, I downloaded it from the Rom's page and it worked.

When I tried installing another Rom, I encountered the same prob, so I installed recovery again and it worked. Do I have to keep changing the recovery every time I put another Rom?
Sent from my HTC HD2 using XDA App

Yeah, some roms require different partition layouts, which are made when you flash CWM recovery.
If you are going from one rom to another and they both require the same partition layout, or if the new rom you're flashing requires a smaller system partition than your current rom, then you won't have to re-flash CWM. In that case, you'd just have to do a full wipe and then flash ur new rom.
The required/recommended CWM partition size is usually somewhere in the first few posts of the thread you download the rom from.
Sent from my HTC HD2 using XDA App

[Q] Clearing Settings

Hi,
I have an HD2 with MAGLDR and CWM. Now i want to update my Hyperdroid ROM because of some issues. The Last Time i did this, all my previous installed apps, sms and contacts are still there.
How can i make a complete clean installation of all this?
Thank you,
trial

Enter cwm
Choose wipe data/ factory reset
Flash new rom.

samsamuel said:
Enter cwm
Choose wipe data/ factory reset
Flash new rom.
Click to expand...
Click to collapse
I sugest to flash "daf.exe" application to recreate boot. And OFC from cwm partition/format SD if you want clean installation.
If you have problem with some roms, put task29 and fix permition
GL

flashing from zip overwrites the boot and system partition, and 'wipe data/factory reset' wipes sd-ext, cache, data and clears the .android folders on the fat32 partition, so unless you want to change the partition size, there is no extra benefit in reflashing cwm (which is what "flash daf.exe" means, for anyone that has only used the flashing tool) and as for task29,,, well i've always considered that to be superfluous except in times where things are genuinely wrong, and indeed doing a full "task29, cwm, rom flash" every time (some people even consider re-flashing hspl, the radio and magldr a 'clean' install ) hugely increase the load on the nand blocks, and considering the number of 'bad block' threads that have been coming up the last 6 months, keeping the number of writes,wipes and rewrites low has got to be top priority.
(course, just my thoughts, I'm no electronics engineer or dev )

[SOLVED] Task29 or multiple formats?

I've been reading .. and in my readings I've read different people saying different things . I heard running task29 a lot can cause bad blocks .. and I flash a lot of ROMs . So I created a task29 zip flash from recovery which formats all nand partitions 3 times in a row to wipe out everything . Is that good for the memory and is that enough to wipe everything clean or should I use task29 every time and not worry about that being the cause of bad blocks ? In short , which is safer ?
Sent from my HTC HD2 using Tapatalk

Well do the math,, task 29 wipes every block once, your zip wipes some three times, which would you suspect as being there times more likely to end in bad blocks?
To be honest what's the point? In 999 out of 1000 flashes its enough to do a 'wipe data factory reset' and then flash.

samsamuel said:
Well do the math,, task 29 wipes every block once, your zip wipes some three times, which would you suspect as being there times more likely to end in bad blocks?
To be honest what's the point? In 999 out of 1000 flashes its enough to do a 'wipe data factory reset' and then flash.
Click to expand...
Click to collapse
Well , in every ROM thread ive read , it says to task29 before flashing . and i thought task29 was a more "harsh" way of wiping the nand . Like a format , does it not just clear the blocks without writing to them ? I personally think either way is still "not good" for the flash memory . But i could be wrong . And i always thought there were "leftovers" from just doing a factory reset ?

In my opinion, task29 is very unnecessary.
Only do it if your device is having issues, otherwise flash roms and bootloaders directly without task29'ing.
By the way, by "task29" they mean empty-rom.nbh .. not empty-rom.zip .
As for the .zip, a full wipe does the same.

Marvlesz said:
In my opinion, task29 is very unnecessary.
Only do it if your device is having issues, otherwise flash roms and bootloaders directly without task29'ing.
By the way, by "task29" they mean empty-rom.nbh .. not empty-rom.zip .
As for the .zip, a full wipe does the same.
Click to expand...
Click to collapse
A full wipe cleans all partitions of the nand ? i thought it just did /userdata . and thank you thats what i thought task29 was . but is flashing an empty .nbh worse then running the format command ?

Let me clarify a few things for you:
Task29: removes everything off your device's internal memory, when you boot your phone after a task29 you will get stuck at bootscreen (first splash), because there is nothing on your device (no bootloader).
Under CWM:
Wipe data/factory reset is different from format that can be found in (mount & storage):
Wipe data/factory reset: does not remove your OS, it will only delete your personal data retaining your ROM intact.
But a format will completely remove your ROM and you will be stuck at the bootscreen if you do so.
Every thing under CWM does not touch your device's bootloader (cLK or MAGLDR), and they only affect the Android ROM within CWM.
Hope this help you

Marvlesz said:
Let me clarify a few things for you:
Task29: removes everything off your device's internal memory, when you boot your phone after a task29 you will get stuck at bootscreen (first splash), because there is nothing on your device (no bootloader).
Under CWM:
Wipe data/factory reset is different from format that can be found in (mount & storage):
Wipe data/factory reset: does not remove your OS, it will only delete your personal data retaining your ROM intact.
But a format will completely remove your ROM and you will be stuck at the bootscreen if you do so.
Every thing under CWM does not touch your device's bootloader (cLK or MAGLDR), and they only affect the Android ROM within CWM.
Hope this help you
Click to expand...
Click to collapse
Yes this i knew thanks though . My question is this , is it safer to wipe the bootloader off using task29 , then starting over , or is it safer to format all partitions of the NAND in CWM before changing to another ROM ?

I don't know which is safer. (or in other words, I don't know which is dangerous )
But if you must do a wipe, I'd recommend "Wipe data/factory reset" . That should do the job. (Most roms format partitions upon installation anyway so I coudn't care less )

Marvlesz said:
Wipe data/factory reset: does not remove your OS, it will only delete your personal data retaining your ROM intact.
Click to expand...
Click to collapse
it also wipes cache partition, the sd-ext partition on your sd card, and clears the .android folder on the fat32 part of the sd card. These last two are the reason many roms wont boot after flashing, even with a task29, since those two areas aren't touched by task29 (or your format zip presumably)
Im with Marvlesz, steer away from task29, , whats the use in removing magldr and cwm only to reflash it?
For me, a clean install would be ,,, cwm - wipe data factory reset - flash the new rom.
Only if the fresh rom doesn't boot after a few times rebooting (and performing a wipe data on the fresh rom, just like how in winmo it was recommended to do a hard reset straight after flashing) would i consider a task29.

Marvlesz said:
I don't know which is safer. (or in other words, I don't know which is dangerous )
But if you must do a wipe, I'd recommend "Wipe data/factory reset" . That should do the job. (Most roms format partitions upon installation anyway so I coudn't care less )
Click to expand...
Click to collapse
Okay thanks ! I wasnt sure if the single format they do upon installation was enough . Ive been getting small app crashes in some ROM's ive tried , so i formated each partition at least once before flashing the ROM and it fixed it . I remember when flashing WinMo ROMs a task29 was a must on my Rhodium . But i was pretty sure wiping the partitions in CWM was indeed good enough . I just kept getting confused when each ROM's thread said YOU MUST TASK29 so i was like well now im just confused lol . I'll mark thread solved
samsamuel said:
it also wipes cache partition, the sd-ext partition on your sd card, and clears the .android folder on the fat32 part of the sd card. These last two are the reason many roms wont boot after flashing, even with a task29, since those two areas aren't touched by task29 (or your format zip presumably)
Im with Marvlesz, steer away from task29, , whats the use in removing magldr and cwm only to reflash it?
For me, a clean install would be ,,, cwm - wipe data factory reset - flash the new rom.
Only if the fresh rom doesn't boot after a few times rebooting (and performing a wipe data on the fresh rom, just like how in winmo it was recommended to do a hard reset straight after flashing) would i consider a task29.
Click to expand...
Click to collapse
Thanks again guys !

For me clean install means first do a factory/data reset. Will clean ext, and previous roms leftover folders. Then i will go to mounts in cwm. Do format every thing i got except sd.
On next boot, magldr, cwm is there. But no boot or rom. Then from magldr, i go to cwm and install the zip. I barely had done task 29 2 times in 3 mnths, just for repartition. ( though its not needed for repartition).
Sent from my HTC HD2 using xda premium

Stuck at splash screen

hello,
i have flashed a nand android rom over my previous nand rom, but im stuck at the splash screen for sometime.
can anybody tell me why its taking so much time, The rom I've flashed is NexusHD2 ICS.
and i tried searching but the results werent fruitful.

Did U flashed correct partition layout for this ROM?

icke said:
Did U flashed correct partition layout for this ROM?
Click to expand...
Click to collapse
how to do that, im new to this, just bought the phone today,
read in a guide that i have just to install zip from sd card via CWM.

Installations:
Please use at least 165MB system partition and at least 2MB cache partition.
Please refer to ksubedi's HD2 NAND Toolkit and/or mskip's guide.
Cache partition (/dev/block/mtdblock4) is only used by CWM.
Cache partition size is not important because the data partition (/dev/block/mtdblock5) is used as the cache space when running Android.
If your HD2 has bad NAND blocks, you may need larger partitions.
Wipe
Wipe Data/Factory Reset while doing a fresh install. (Optional: also delete /sdcard/Android folder or format your SD card if you have any strange issue.)
Advanced -> Wipe Dalvik Cache while upgrading from an old version and wanting to retain data.
Flash this ROM.
MAGLDR: Flash NexusHD2-ICS-CM9_V1.5.zip, then reboot.
　 cLK　 : Flash NexusHD2-ICS-CM9_V1.5.zip and the cLK kernel, then reboot.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1090783
http://forum.xda-developers.com/showthread.php?t=1044830

Me Install But Not Show SD Card.