apparently, my phone has bad blocks in internal memory, it gets very laggy every time, when trying to read/write data in background. is there a method to move them, or to install rom on external sd?
sory for bad eng, i'm from russia.
Related
For a stupid question, when we launched Android through HTC HD2 and using File Manager like Astro File Manager. Are we still able to access Win Mo system file? Or it will be blocked?
Dun feel like messing up the system, lol ...
you should ony be able to access whats on the memory card
No, we are not. Android is stored on your SD and WinMo in NAND. So you can't get access because the phone pretends Android that it's internal memory is in the phone altough it is stored on your SD in the data.img. Hope you will understand this sentence, I'm not very good in English grammar
So don't worry about messin' up WinMo.
Ladies & gentlemen;
Good day!
Well, I am one of those who admire the XDA BIG TIIIMMEE!! However I have an HD2 and managed to have it as a NAND Android after the help of the XDA (as usual of course!) Anyway when I started looking for new ROMs I have noticed that there is new method or way which I do not grasp, comprehend and assimilate AT ALL....ZIP that is, such as [A2SD+], NAND SD and ClockworkMod.Recovery!!!
What is the difference between running Android on NAND & SD with ClockworkMod?!
I am sorry people because truly I must have missed threads or the way of understanding, so hopefully you'll going to be the teacher of mine for now and always!
Could anyone help me as if I am 7 years old?!!!
THANK YOU XDA & Members!!!!
Android nand is running off internal memory. Sd option is what it says, a build running off your sd card opposed to running it with nand.
Thank you for your explanation, but does that mean if the Android runs off internal memory would make the running proccess faster or it would hepl smoothen applications response?! What is the use if I already have the internal memory, wouldn't be even better off?!
Hello
SD Builds start to boot from SD card while being on WM6.5. The hardware shutsdown WinMo and runs Android on it.
NAND Builds run from the internal memory of the phone(just like where WinMo was before)
RAM Builds load all the OS from the SD Card inside the RAM.
[A2SD+] means that you can use a small ext2,ext3 or ext4 partition in your SD Card for increasing your internal storage memory for installing more apps... so this means more internal space.
ClockworkMod is a small linux-based booting utility allowing users to install Android Builds on-the-go which are stored as zip packages on the SD Card. It allows you to install new kernels as update.zip packages as well without having to re-format your entire phone again, or just to erase all personal data on the sd-ext partition.
So, in fact a lot of things have changed in the last 3 months... these are just a few features i can tell you about every method, but at least I hope this will help you to understand quickly a bit about all that.
You know!!?? I Thank you all guys!!!!
NAND runs off the internal memory and even though you get much lower Quadrant scores, NAND is much more responsive and smooth.
The only reason SD based builds get more Quadrant is because of I/O speeds thanks to the SD card.
SD builds are fast, but NAND builds are much SMOOTHER and reliable and if you can do something on SD, you can do it just as well on NAND (gaming for example).
So I used to use NAND android then I figured out I had bad blocks on my HD2 so I flashed back to windows mobile and started using SD android. I get a lot of freezing issues and many times my phone won't wake up (on SD android). So my question is do bad blocks affect SD android? Which version of SD android is most stable in your opinion because 2 I tried froze a lot. Thanks!!
are you sure the bad blocks on the phone not on the SD card?
I would do a task29 on the phone from bootloader usb screen and then dl Partition Wizard 7, install it, put the microsd into a use adapter, plug it into the computer, open PW7, delete all partitions on the card, create a new one in the space of the blank card (FAT32 SYSTEM, leaving 1024MB of space for a second partition (EXT3-4: "SD-EXT CACHE"), if your NAND ROM calls for it. Safely eject the usb-sd, take it out and mount it in the phone again, then proceed with flashing clk, magldr, CLMrecovery, or flash stock ROM from TMOUS. If that doesn't work, there's no easy fix> Partition Wizard seems to bail me out with most SDcard issues. Good luck!
Hello everyone, I did an error report to see if I had any bad blocks on my HD2 and unfortunately I had 3. While I have these 3 bad blocks I don't see any issues with the performance on my HD2. I am hoping anyone can tell me how these blocks will effect my device. Report is attatched with this post. Thank you
Origin8 said:
Hello everyone, I did an error report to see if I had any bad blocks on my HD2 and unfortunately I had 3. While I have these 3 bad blocks I don't see any issues with the performance on my HD2. I am hoping anyone can tell me how these blocks will effect my device. Report is attatched with this post. Thank you
Click to expand...
Click to collapse
What a bad block is is a block(a block is a sector on the memory module inside the phone) that is well bad. Meaning that sector or location on the memory module is not useable at all. Its simply ignored by windows mobile and android. HOwever, since they are ignored, the amount of data is limited. I have 3 bad blocks in my data partition, thus those three blocks can not hold data, making my data partition smaller.
Issues arise when one has many bad blocks in places like system, boot, recovery partitions. Because one may set said parition to 150 megabytes however those bad blocks in that partition are not useable, so in reality there may only be 100~ megabytes of useable space. Which causes boot loops and boot hangs because when you flashed the ROM not all the files were copied over to that partition. But three bad blocks are not a problem, especially if they reside in data or cache partitions.
As per performance, it wont harm it at all, like i said above, it only decreases the amount of useable disk space.
There is a way to fix bad blocks, but it requires a JTAG device costing up near the price of a new phone. Unless youre lucky and know someone who works for a cell phone repair shop, or a carrier, my buddy works for verizon and he successfully got rid of all his bad blocks on his Droid. What a JTAG device does is simply rewrites the file system, in this case it rewrites the YAFFS2 file system. Its the same thing on windows when you want to rebuild the MBR.
Hope that cleared some stuff up for ya
Origin8 said:
Hello everyone, I did an error report to see if I had any bad blocks on my HD2 and unfortunately I had 3. While I have these 3 bad blocks I don't see any issues with the performance on my HD2. I am hoping anyone can tell me how these blocks will effect my device. Report is attatched with this post. Thank you
Click to expand...
Click to collapse
Bad blocks are not affecting the working of your device, especially if the amount is around 5 blocks. If you experience further blocks, enable the last 24MB of your NAND and flash the device with CWM and make sure you set different system size so the whole of the phone can be repartitioned and bad blocks can be fixed most of the time with reformatting the whole phone and set a different system size in flash.cfg for the CWM Recovery. You don't really need expensive tools to fix the bad memory blocks while it can be fixed with underformatting your HD2.
Since the bad blocks are in the data partition, there shouldn't be that much problems because the data partition does not contain any system data, only user apps and user data (correct me if i'm wrong). So if you install an app on one of the bad blocks, the app probably will only crash and not your whole system.
If you want to make sure that doesn't happen, you have to repartition and skip the bad blocks so there isn't a possibility that there will be any writing or reading on those bad blocks.
.:ICEMAN:. said:
...... You don't really need expensive tools to fix the bad memory blocks while it can be fixed with underformatting your HD2.
Click to expand...
Click to collapse
Thats so not true. Just search the forums for threads containing bad blocks. HUNDREDS of people have commented that task29/task2a DO NOT repair bad blocks. Formatting a partition or wiping it clean does not "realign" the blocks and correct them. Only a JTAG device can do that. I have been researching a way to do it in linux since Yaffs2 is a linux counterpart but im coming up dry since we cant view the internal phone memory on a computer. there has to be some sort of OS to handle the USB link. (for example: tri colored boot loader, android, windows mobile, recovery, MAGLDR, CLk etc..)
I had seen a few posts months ago about being about to food bad blocks with task 29 and 2a. I tried it after some "claimed" it to work, well failed..big fail at that. Task anything will not fix this type of issue, only JTAG.
Sent from my HTC HD2 using xda premium
Thanks for the help guys but does this happen with all phones or is it the HD2 only? I don't plan on upgrading any time soon but it would be nice to know. Thank you
It's a common problem... NANDs have limited rewrite cycles...
The HD2 is one of the most "flashed" device out there with so many roms and os and this make it easy to get bad blocks.
elesbb said:
Thats so not true. Just search the forums for threads containing bad blocks. HUNDREDS of people have commented that task29/task2a DO NOT repair bad blocks. Formatting a partition or wiping it clean does not "realign" the blocks and correct them. Only a JTAG device can do that. I have been researching a way to do it in linux since Yaffs2 is a linux counterpart but im coming up dry since we cant view the internal phone memory on a computer. there has to be some sort of OS to handle the USB link. (for example: tri colored boot loader, android, windows mobile, recovery, MAGLDR, CLk etc..)
Click to expand...
Click to collapse
I agree, the underformatting not fully wiping out all the bad sectors, but it does a great wipe with a few bad blocks especially if you set different block size in the flash.cfg. When the bad blocks are keep increasing then we really need the ITAG device to fix the bad blocks. I have had a queit lot hd2 phones in my hand such as eu and tmous handsets and a quiet lot of them have had about 5 bad blocks, with task and realigining the blocks with modifying the flash partitions alignment was able to fix them for a while. Bad blocks are not affecting the performance but really increasin the storage and bad block will come up in every single NAND phone, just need to choose the right rom and use it with it as long as possible without re-flashing then the blocks can survive for longer time. The most important at all is not to worry about bad blocks as long as there are just a few of them...
How can I get a binary badblocks for use in my android armv7???
I bought this unit:
http://es.aliexpress.com/item/Double...Number=1463369
And i have a problem. I cannoy install new apps, i tried to move them to sd, i could move a lot, but not all apps, i need to install some more apps but internal memory is not enouth, what can i do?
Thanks and sorry for my bad english, i'm spanish.
U2Endless said:
I bought this unit:
http://es.aliexpress.com/item/Double...Number=1463369
And i have a problem. I cannoy install new apps, i tried to move them to sd, i could move a lot, but not all apps, i need to install some more apps but internal memory is not enouth, what can i do?
Thanks and sorry for my bad english, i'm spanish.
Click to expand...
Click to collapse
Your link is no good.
Depending on the type, you may be able to install a custom ROM that changes the install partition size. We would need to know what unit you purchased, however.