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???
Related
Hey guys, I;m appealing for a little help here.
I have an HTC HD2 which has been great for about a year but all of a sudden it has problems.
I;ve been using this rom pretty much since it came out....
http://forum.xda-developers.com/showthread.php?t=905060
I;ve never had any problems with it untill now. I started to get the "insufficient storeage space available" message on it so I assumed a restore/reflash would solve the problem.
I used HD2 toolkit to resize my MAGLDR partition to 450MB & reflashed - the phone wouldnt boot. Stuck on the HTC logo.
Repartitioned to 400 - still no boot!
Repartitioned to 350 - still no boot!
Repartitioned to 300MB - phone now boots however now, I;ve installed no apps & when I try to install spotify, its telling me insufficient storeage available, again! With nothing on the phone except the ROM!
I'm a bit of a n00b with all this stuff, but had my HD2 running fine for ages & its frustrating me that now it wont work properly!
Anyone care to help? THanks, Cardz.
Edit: im using MAGLDR 1.13 & the latest Clockwork mod to flash the ROM. I'm wiping cache & data partitions every time...... :/
Install it with as lower as possible space for system partition. In your case it shoud be 135MB of system partition and 2MB cache but I recommend to put some more of space for system partition as I had some problems with low system partition so you can put 150MB for system partition.
The simple explanation of why you dont have enough of space for apps is that you gave too much of space for system partition and simply this ROM does not require that much of space for system partition. And other space left in your phone memory will be used for apps etc.
EDIT: And also try to install MAGLDR and CWM manually if you can and when you install CWM edit flash.cfg in WordPad or other text editing tool before you flash CWM and edit system partition size to 150MB and Cache size to 2MB
jan.selep said:
EDIT: And also try to install MAGLDR and CWM manually if you can and when you install CWM edit flash.cfg in WordPad or other text editing tool before you flash CWM and edit system partition size to 150MB and Cache size to 2MB
Click to expand...
Click to collapse
Thanks a lot for the reply, i understand now about the 150MB/2MB cache, but what is the point of this other bit? Could you explain more the purpose of this?>
cardyology said:
Thanks a lot for the reply, i understand now about the 150MB/2MB cache, but what is the point of this other bit? Could you explain more the purpose of this?>
Click to expand...
Click to collapse
Well to simply explain you why i wrote you to use manual installation of CLOCKWORKMOD RECOVERY was that I wanted to explain you how is it working with partitioning your nand memory using cwr or magldr. I just added some helpfull info for you from my experience with HD2 and android flashing. So in the future you will know what to do and you will be able to uderstand more from technical point of view about flashing etc. I just wanted.to share some of my experience with you
But it is up to you if you want to use hd2 toolkit or manual configuration.
Sent from my HTC HD2 using xda premium
You can also use 4ext recovery instead of clockwork...
Sent from my HTC HD2 using xda premium
Afaik it's better to post in a similar topic than create a new one, so here I go.
I have recently switched to an ICS NAND rom and since then I keep having constant storage problems. I understand that in order to solve that I have to partition my SD card but it seems, since I don't really understand the whole android storage management process too deeply, I am not doing things properly cause I keep getting "Low on space" notifications. I attach some screenshots below in order to give you more info about my sd card partitions and rom specs. Please let me know what I did wrong and how I can solve it. I understand I will probably need to repartition and reflash the devide again?
Edit: The screenshots I have attached don't have 2nd part mounted, going to upload proper screens in a minute. Done.
Edit 2: Will this fix my problems?
(cant post proper links yet)
wwwDOTjayceooiDOTcom/2011/12/26/how-to-create-custom-clockworkmod-recovery-partition-size-for-htc-hd2/
You are mixing different things. In the first post of this thread the issue was the partitioning of the internal Flash-ROM in the Phone.
You wrote about the SD card partitioning and these things are totally different.
I think, you have a problem with your internal memory and you have to try the same things like cardyology has done after the hint from jan.selep.
Partitioning for Ubuntu's users
I don't find the way to modify partitioning of the internal Flash-ROM when you are an Ubuntu user on PC (no Windows boot anywhere..)
Monolecte said:
I don't find the way to modify partitioning of the internal Flash-ROM when you are an Ubuntu user on PC (no Windows boot anywhere..)
Click to expand...
Click to collapse
If you use cLK instead of magldr you can repartition from the cLK bootloader, , no PC necessary.
Before you say 'I cant install cLK without a PC', there is a version of cLK you can flash from sd card.
It will mean you have to resinstall your rom, though.
I believe more simple to find a Windows PC...
dont see why it should take any more than 25 minutes to accomplish, properly prepared.
samsamuel said:
dont see why it should take any more than 25 minutes to accomplish, properly prepared.
Click to expand...
Click to collapse
Hummmm because the Murphy's law? :crying:
I found a Windows PC, I downloaded the HD2 Toolkit... but not the good one, because the last version don't works with 32 bits PC. So, I found the good one, I saved all my stuff, I tried to repartition and... I miss a dll and other bull****... 2 hours later, I thought is too long to be good and I sought a lighter ROM (I understood Hyperdroid CM7 has a 150 Mo system partition : it's very short!), but, I found nothing with ICS or JB, only GB... pfff.
So, I took a week to flash ROM, I read miles of thread, hours to understand how my device working and each time I found a solution, each time I have at less a new issue to solve. It pissed me of.
Monolecte said:
Hummmm because the Murphy's law?
Click to expand...
Click to collapse
Haven't you heard? Murphy was an optimist!
---
If you have a 50% chance of being right, you will be wrong 90% of the time...
NYLimited said:
Haven't you heard? Murphy was an optimist!
---
If you have a 50% chance of being right, you will be wrong 90% of the time...
Click to expand...
Click to collapse
You're right : I did it!!!
Miles of threads here was usefull indeed!
I won against the machine!
Youpi!
Monolecte said:
You're right : I did it!!!
Miles of threads here was usefull indeed!
I won against the machine!
Youpi!
Click to expand...
Click to collapse
CONGRATULATIONS! I love a happy ending!
And, if you read only 10% of the posts some of us read your would find it rather refreshing too!
---
If you have a 50% chance of being right, you will be wrong 90% of the time...
hello,I am having big problems with my T-mobile Hd2...In few words,I cannot install any android Rom,either NAND or SD...my guess is that my bad blocks might cause the problem...here is the list
Cmd>info 8
--- 2K bytes sector version ---
DEVICE NAME=samsung_KBY00U00VM
DEVICE ID=0xB3
DEVICE MAKER ID=0xEC
PAGE SIZE=0x800
TOTAL PAGE SIZE=0x840
BLOCK COUNT=0x2000
BLOCK PAGE=0x40
Checking block information
BLOCK 0 (0x0) is reversed block
BLOCK 1 (0x1) is reversed block
BLOCK 2 (0x2) is reversed block
BLOCK 3 (0x3) is reversed block
BLOCK 8 (0x8) is reversed block
BLOCK 10 (0xA) is reversed block
BLOCK 11 (0xB) is reversed block
BLOCK 12 (0xC) is reversed block
BLOCK 13 (0xD) is reversed block
BLOCK 14 (0xE) is reversed block
BLOCK 15 (0xF) is reversed block
BLOCK 91 (0x5B) is bad block
BLOCK 455 (0x1C7) is bad block
BLOCK 1060 (0x424) is bad block
BLOCK 2332 (0x91C) is bad block
BLOCK 3339 (0xD0B) is bad block
BLOCK 4184 (0x1058) is bad block
BLOCK 5083 (0x13DB) is bad block
BLOCK 5190 (0x1446) is bad block
BLOCK 6926 (0x1B0E) is bad block
Partition[0], type=0x20, start=0x2, total=0x63E
Partition[1], type=0x23, start=0x640, total=0xA40
Partition[2], type=0x25, start=0x1080, total=0x1D780
Partition[3], type=0x4, start=0x1E800, total=0x59380
CE Total Length(with sector info) = 0xF4F4000
CE CheckSum Length(without sector info) = 0xF400000
I have searched alot about but I couldnt find any solution to bypass the problem...I dont know if I bad blocks cause the problem but every time i try to enter cwm(AD Recovery) my phone stucks on Go Go Go!I ve made a lot of threads but none has gave me a solution yet...As i said,my phone is a T-mobile, with hspl 2.08 on it and the radio 2.15.50.14 radio...Please give me a solution because I am really getting tired with my phone...thanks in advance
tsagas said:
hello,I am having big problems with my T-mobile Hd2...In few words,I cannot install any android Rom,either NAND or SD...my guess is that my bad blocks might cause the problem...here is the list
Cmd>info 8
--- 2K bytes sector version ---
DEVICE NAME=samsung_KBY00U00VM
DEVICE ID=0xB3
DEVICE MAKER ID=0xEC
PAGE SIZE=0x800
TOTAL PAGE SIZE=0x840
BLOCK COUNT=0x2000
BLOCK PAGE=0x40
Checking block information
BLOCK 0 (0x0) is reversed block
BLOCK 1 (0x1) is reversed block
BLOCK 2 (0x2) is reversed block
BLOCK 3 (0x3) is reversed block
BLOCK 8 (0x8) is reversed block
BLOCK 10 (0xA) is reversed block
BLOCK 11 (0xB) is reversed block
BLOCK 12 (0xC) is reversed block
BLOCK 13 (0xD) is reversed block
BLOCK 14 (0xE) is reversed block
BLOCK 15 (0xF) is reversed block
BLOCK 91 (0x5B) is bad block
BLOCK 455 (0x1C7) is bad block
BLOCK 1060 (0x424) is bad block
BLOCK 2332 (0x91C) is bad block
BLOCK 3339 (0xD0B) is bad block
BLOCK 4184 (0x1058) is bad block
BLOCK 5083 (0x13DB) is bad block
BLOCK 5190 (0x1446) is bad block
BLOCK 6926 (0x1B0E) is bad block
Partition[0], type=0x20, start=0x2, total=0x63E
Partition[1], type=0x23, start=0x640, total=0xA40
Partition[2], type=0x25, start=0x1080, total=0x1D780
Partition[3], type=0x4, start=0x1E800, total=0x59380
CE Total Length(with sector info) = 0xF4F4000
CE CheckSum Length(without sector info) = 0xF400000
I have searched alot about but I couldnt find any solution to bypass the problem...I dont know if I bad blocks cause the problem but every time i try to enter cwm(AD Recovery) my phone stucks on Go Go Go!I ve made a lot of threads but none has gave me a solution yet...As i said,my phone is a T-mobile, with hspl 2.08 on it and the radio 2.15.50.14 radio...Please give me a solution because I am really getting tired with my phone...thanks in advance
Click to expand...
Click to collapse
You seem to have a lot of bad blocks, but as far as I know, bad blocks do not affect the phone's ability to run SD Android. Are you able to flash a WinMo ROM again?
You might be having bad blocks in boot (and maybe recovery partitions too). Try to flash a larger partition size for all partitions.
EDIT: That was for NAND. SD Builds using Haret method should work just fine.
Nigeldg said:
You seem to have a lot of bad blocks, but as far as I know, bad blocks do not affect the phone's ability to run SD Android. Are you able to flash a WinMo ROM again?
Click to expand...
Click to collapse
yes, I can flash winMo and WP7 without any problem,but I cannot flash any android rom...I get stuck on Go Go Go! every time I try...
ph03n!x said:
You might be having bad blocks in boot (and maybe recovery partitions too). Try to flash a larger partition size for all partitions.
EDIT: That was for NAND. SD Builds using Haret method should work just fine.
Click to expand...
Click to collapse
tried it and nothing happened...also SD builds should work but still they don't...so I don't exactly know whats the problem with my phone...
Is it possible that all these happens cause of my SD card?maybe it s not fully compatible or low class or something?
tsagas said:
Is it possible that all these happens cause of my SD card?maybe it s not fully compatible or low class or something?
Click to expand...
Click to collapse
Some SD cards aren't compatible with MAGLDR (I know that because mine isn't, it simply can't launch SD builds from MAGLDR) but I've never heard of one being incompatible in WinMo (although it's possible). You mentioned WP7 - perhaps it's something to do with the way Windows Phone formats SD cards?
Oh, and also please use the edit post feature rather than triple posting
Nigeldg said:
Some SD cards aren't compatible with MAGLDR (I know that because mine isn't, it simply can't launch SD builds from MAGLDR) but I've never heard of one being incompatible in WinMo (although it's possible). You mentioned WP7 - perhaps it's something to do with the way Windows Phone formats SD cards?
Oh, and also please use the edit post feature rather than triple posting
Click to expand...
Click to collapse
my SD is compatible with WinMo6.5 it's a cheapish chinease 32gb copy of kingston(I think)
Nigeldg said:
Some SD cards aren't compatible with MAGLDR (I know that because mine isn't, it simply can't launch SD builds from MAGLDR) but I've never heard of one being incompatible in WinMo (although it's possible). You mentioned WP7 - perhaps it's something to do with the way Windows Phone formats SD cards?
Oh, and also please use the edit post feature rather than triple posting
Click to expand...
Click to collapse
wp7 formats the sd card in a way that once done it cant be used on android
unless something is done to it not sure what
but he needs to look in the hd2 wp7 section for the fix
Kameirus said:
wp7 formats the sd card in a way that once done it cant be used on android
unless something is done to it not sure what
but he needs to look in the hd2 wp7 section for the fix
Click to expand...
Click to collapse
yes,i know...but i am on winMo6.5 so that's not the problem
tsagas said:
yes,i know...but i am on winMo6.5 so that's not the problem
Click to expand...
Click to collapse
These things aren't as consistent as that. For example, as I've said my SD can't run SD Android when in MAGLDR, but it worked without a hitch when I used WinMo+SD Android. Same thing applies for CWM, works fine. Although it might not necessarily be the right answer, don't just rule it out like that. Is the card read on your PC?
Kameirus said:
wp7 formats the sd card in a way that once done it cant be used on android
unless something is done to it not sure what
but he needs to look in the hd2 wp7 section for the fix
Click to expand...
Click to collapse
Formatting with an indestructible Nokia I think
Nigeldg said:
These things aren't as consistent as that. For example, as I've said my SD can't run SD Android when in MAGLDR, but it worked without a hitch when I used WinMo+SD Android. Same thing applies for CWM, works fine. Although it might not necessarily be the right answer, don't just rule it out like that. Is the card read on your PC?
Formatting with an indestructible Nokia I think
Click to expand...
Click to collapse
yes,it can be read on my PC
Nigeldg said:
These things aren't as consistent as that. For example, as I've said my SD can't run SD Android when in MAGLDR, but it worked without a hitch when I used WinMo+SD Android. Same thing applies for CWM, works fine. Although it might not necessarily be the right answer, don't just rule it out like that. Is the card read on your PC?
Formatting with an indestructible Nokia I think
Click to expand...
Click to collapse
yep thats it
Kameirus said:
yep thats it
Click to expand...
Click to collapse
ehmmm whats it?
tsagas said:
ehmmm whats it?
Click to expand...
Click to collapse
you need to find someone with a nokia and put your sdcard in it and format it
Kameirus said:
you need to find someone with a nokia and put your sdcard in it and format it
Click to expand...
Click to collapse
Can't you format it using hp USB storage utility? Or even a Linux terminal? Or even mini tool partition wizard? I would first recommend hp USB storage utility, as that wipers everything, including the master boot record. I'm surprised you are having issues with bad blocks for sd. Unless you have a fake card considering you said it's a cheap Chinese 32gb. What happens is they take a 2gb or other super cheap sd card and modify it to show as a higher size, this then makes files and parts of files broken and lost. Thus rendering the file in operable. I'm not saying this is true, but it wouldn't hurt to go buy a cheap 2gb from Walmart and test it out. Also when copying files, one should use an adapter and not the phones USB mass storage option. Just a few things to try
Sent from my GT-I9100 using Tapatalk
ive asked someone i know who has used wp7 to came and see if he can help out in anyway
"Someone" is here now but has to go to work right now unfortunately.
I have a HD2 with 3 bad blocks, one of them in the IPL/SPL region, which already caused a hard brick on it which i could manage to revive giving it to someone with a jTag box.
This is just an anecdote and not applicable to you, just to tell you i've had my troubles too
in general there is one thing for sure: bad blocks are handled by the memory controller alone and as such - in theory - do not affect the operating system as there are reserve adresses assigned for each bad block which the OS then is redirected too.
However, for some odd reason WP7 and WinMo do cope with this mechanism very well but Android seems to somehow stubbornly ignore the redirecting and get stuck at the bad blocks each time it hits one, causing every imaginable sort of random misbehaviour. Which is very annoying.
However, since you got a Tmob device with plenty of chip space there should be absolutely no problem increasing your partition size and have the thing run off SD-EXT mainly and only use small portitions of the NAND for the OS like the Team Blue Droid ROM does (runs perfectly on my bad blocked device btw, only EU version).
The fact that you get stuck at the go go go screen might very well be something completely different and not the Bad Blocks at all even though that theory sounds rather logical.
I tend to think it might much rather be your SD Card and would first of all recommend you to try different brands and speeds, especially the slower ones like CL 2,4 or 6 but never 10 as that is regularly causing issues for many people.
I will get back to you later or tomorrow when i got time and hear what you have to say about the different SD Cards and then i could try to walk you through some ideas i was pursuing with my device back then when i got it full of bad blocks.
Hope i can help you. Not sure though.
Sneakyghost said:
"Someone" is here now but has to go to work right now unfortunately.
I have a HD2 with 3 bad blocks, one of them in the IPL/SPL region, which already caused a hard brick on it which i could manage to revive giving it to someone with a jTag box.
This is just an anecdote and not applicable to you, just to tell you i've had my troubles too
in general there is one thing for sure: bad blocks are handled by the memory controller alone and as such - in theory - do not affect the operating system as there are reserve adresses assigned for each bad block which the OS then is redirected too.
However, for some odd reason WP7 and WinMo do cope with this mechanism very well but Android seems to somehow stubbornly ignore the redirecting and get stuck at the bad blocks each time it hits one, causing every imaginable sort of random misbehaviour. Which is very annoying.
However, since you got a Tmob device with plenty of chip space there should be absolutely no problem increasing your partition size and have the thing run off SD-EXT mainly and only use small portitions of the NAND for the OS like the Team Blue Droid ROM does (runs perfectly on my bad blocked device btw, only EU version).
The fact that you get stuck at the go go go screen might very well be something completely different and not the Bad Blocks at all even though that theory sounds rather logical.
I tend to think it might much rather be your SD Card and would first of all recommend you to try different brands and speeds, especially the slower ones like CL 2,4 or 6 but never 10 as that is regularly causing issues for many people.
I will get back to you later or tomorrow when i got time and hear what you have to say about the different SD Cards and then i could try to walk you through some ideas i was pursuing with my device back then when i got it full of bad blocks.
Hope i can help you. Not sure though.
Click to expand...
Click to collapse
Wait, i thought he had WinMo6.5 running as nand, and wanted to run android via SD haret.ext and clrcad.exe? if so bad blocks should not effect him and he has an issue with his SD card.. but very good information bookmarking your post for future references to people who need bad block info
elesbb said:
Wait, i thought he had WinMo6.5 running as nand, and wanted to run android via SD haret.ext and clrcad.exe? if so bad blocks should not effect him and he has an issue with his SD card.. but very good information bookmarking your post for future references to people who need bad block info
Click to expand...
Click to collapse
he states in this post http://forum.xda-developers.com/showpost.php?p=27277432&postcount=4
that he can run winmo and wp7 fine just not android
so if he has flashed wp7 it has locked his sd card and he wont be able to run
anything from the sdcard untill he reformats it
here is what i found on the hd2 wp7 forum
http://forum.xda-developers.com/showthread.php?t=1242071
Dear all!
I would like to ask for assistance in connection with the HD2 device.
First of all thank you very ROM I could try, hats off to everyone who built them.
The problem many would be now if an app I use (whatever it is), and someone calls me, then the device freeze, slow Lessa, who writes that "the android.phone application is stopped.'ll Ask for your PIN code and reboots . pulled the CPU clock frequency, set it as possible. But all in vain. now It used to be used for stable ROMs also exists. Please help me to correct the error!
Hints at the following e-mail address: [email protected]
Thanks in advance!
Sincerely MrScottt21
Need more information like
.what bootloader used
.which type of memory used rom(nand or data-EXT or Native SD)
Are you getting this on first use or?
Sent from my MediaPad 7 Lite using xda premium
Hello!
I used CLK and MAGLDR Bootloader (Dark Force's Team).
The ROM is always watching for the correct partition size that the ROM "manufacturers" offered to the ROM. NAND and SD were Native-ROM. So far, everything has worked perfectly fine varieties. The radio version RadioLeo2.15.50.14 because the European unit. This is one of the most stable radio which is made to the HD2. 3.7 GB of ROM I downloaded from here on XDA and android.hd2roms.com website. Not much everything worked except for the second Third run-up. All before installing formatted the internal memory (NAND), the HD2 Task29 Tool Kit program.
Always 2x 3x checking the system partition or the microSD Ext2, Ext3, Ext4 partition before starting anything can be installed. I am always careful. Therefore, I do not understand what's wrong.
I hope you can, or you can help me.
Thanks in advance!
Sincerely Mrscottt21.
MrScottt21 said:
The ROM is always watching for the correct partition size that the ROM "manufacturers" offered to the ROM.
Click to expand...
Click to collapse
The partition sizes recommended for most ROMs are conservative minimum sizes. They assume your device has no bad blocks in memory, something that is likely incorrect.
Start increasing the size of the system partition by 10-20 MB each installation try. If you are using a DataOnEXT installation make your system partition 399 MB (nothing beyond it is used with DataOnEXT anyway).
---
If you have a 50% chance of being right, you will be wrong 90% of the time...
Greetings!
Thanks for the quick response. We try this option to see if you will.
One question: What did you mean, "bad blocks in memory"? This refers to the NAND or the memory card? Thank you for your answer!
Sincerely MrScottt21.
MrScottt21 said:
Greetings!
Thanks for the quick response. We try this option to see if you will.
One question: What did you mean, "bad blocks in memory"? This refers to the NAND or the memory card? Thank you for your answer!
Sincerely MrScottt21.
Click to expand...
Click to collapse
nand ......
I accustomed to storing their audio or video file like photos into a mini memory stick. However, how can we recover them once lost? What can I do ? Any software like Power Data Recovery?? 3Q for your advice.
Wait, what does this have to do with Win8? I'm confused (or maybe you are)...
Assuming "memory stick" (whatever the <REDACTED> that is) exposes itself as a standard block-storage device, you can probably use whatever recovery tools you're used to... no guarantee they'll work, though.
I've had a positive experience using MiniTool Power Data Recovery.
It worked wonders on a flash disk that apparently lost its data, but with this software I could recover most of them, although with very ugly file names.
There are 4 options which can be confusing but I've mostly used Digital Media Recovery and Undelete Recovery.
For non media files, the result wasn't so great but I recovered some files from an almost defective SD card.
cha91 said:
I've had a positive experience using MiniTool Power Data Recovery
Click to expand...
Click to collapse
Well, what can i say but thank you so much!
Had the same problem and all the pictures of my holiday were gone. :victory:
With kind regards, Basti
pHaZic said:
Well, what can i say but thank you so much!
Had the same problem and all the pictures of my holiday were gone. :victory:
With kind regards, Basti
Click to expand...
Click to collapse
You're welcome! I'm glad it helped.
I had the same problem a while ago so now I recommend this software
mining said:
I accustomed to storing their audio or video file like photos into a mini memory stick. However, how can we recover them once lost? What can I do ? Any software like Power Data Recovery?? 3Q for your advice.
Click to expand...
Click to collapse
yup, any recovery software will do, just defrag first before recovering for best result
Physiotherapist said:
yup, any recovery software will do, just defrag first before recovering for best result
Click to expand...
Click to collapse
Worst result dont you mean... Recovery software relies on the fact that when deleting a file it is simply removed from the file table but the data itself is still present. Defragging will move files around and will now believe where your file previously existed is now unallocated space and will happily over-write it. For recovery software to work at its best you need to ensure as few changes are made to the file system as physically possible.
SixSixSevenSeven is correct. Leaving aside the fact that defragging a flash storage device (like a memory stick, SD card, SSD, CompactFlash, etc.) is a terrible idea in general*, it will drastically reduce your chances of being able to recover any data at all. If you have already done a defrag, the odds are very good that your data is now unrecoverable.
* Win7 and up know not to actually defrag Flash-based storage, but what they do instead - called TRIM, and intended to optimize the storage - is almost as bad for purposes of data recovery. TRIM tells the "disk" that the physical memory cells which were storing the data of deleted files are no longer needed, which typically has the effect of zeroing the data.
During the research in order to build the TWRP recovery for this device I have noticed a very interesting fact. Although the phone is sold as a device with 8 GB internal memory, the memory chip used inside seems to be two times bigger. There is an unused (non-formatted) partition "mmcblk0p38" labeled as userdatabak and its size is 7816 MB. There is no data there, it is a completely blank partition. It will be interesting if the mmcblk0p37 (userdata) partition can be resized in order the reported internal memory of the device to be increased. I intend to experiment with this soon and will post an update here if I have some success. If anyone is interested and is willing to share ideas regarding the resizing I will be glad to see them.
does parted print show the partitions?
The 6039k (dual sim version) already has 16gb of rom and 1,5 of ram, maybe the parts used in the mono sim one are the same but just turned down, still strange for the manufacturer to cripple the phone on porpuse, more memory means an even better phone for the price and more sales...
Demetris said:
does parted print show the partitions?
Click to expand...
Click to collapse
No it doesn't. The partition table contains a protective MBR sector, and unfortunately parted cannot handle this layout. I'm playing with a raw image of the entire phone memory and successfully resized the partitions in it. But I used gdisk and resize2fs ... gdisk however is not available in the recovery mode on the phone. In this thread @meghd00t has a static build of gdisk which should do the trick. I will try to use it later directly on the device.
SUCCESS!!!
I did it ! The static build of gdisk works perfectly (big thanks @meghd00t). Here are screenshots before the repartitioning and afterwards. I will post a guide how can be done later today.
petrov.0 said:
I did it ! The static build of gdisk works perfectly (big thanks @meghd00t). Here are screenshots before the repartitioning and afterwards. I will post a guide how can be done later today.
Click to expand...
Click to collapse
So the phone is being sold as a 8gb somewhere? If no negative repercussions then great find! I thought the 4.7 had 16gb as well.
famewolf said:
So the phone is being sold as a 8gb somewhere?
Click to expand...
Click to collapse
Yes, the version with one sim card is with 8GB internal memory even according to gsmarena and is sold like this
famewolf said:
If no negative repercussions then great find! I thought the 4.7 had 16gb as well.
Click to expand...
Click to collapse
What you mean with negative repercussions ?
petrov.0 said:
I did it ! The static build of gdisk works perfectly (big thanks @meghd00t). Here are screenshots before the repartitioning and afterwards. I will post a guide how can be done later today.
Click to expand...
Click to collapse
Good job Sir!! This is what makes XDA such an amazing place to be!! This should be put on the main XDA portal!!
Nope stop or Alcatel will change the nands on new batches
Demetris said:
Nope stop or Alcatel will change the nands on new batches
Click to expand...
Click to collapse
Too late . The guide is already in the development section.
petrov.0 said:
Yes, the version with one sim card is with 8GB internal memory even according to gsmarena and is sold like this
What you mean with negative repercussions ?
Click to expand...
Click to collapse
I wondered at the possibility the chip actually was used for something such as a system backup. I also considered the possibility they sold it as an 8gb because areas in the 2nd partition did not pass quality standards and could possibly result in data loss over time. Cpu makers used to sell quad cores that failed tests as dual cores with the other two cores "locked"....and of course folks figured out how to unlock them but the system would crash from time to time.
Maybe the 6045i has 32GB??? Jajaja
famewolf said:
I wondered at the possibility the chip actually was used for something such as a system backup.
Click to expand...
Click to collapse
Initially I thought about this too. It is possible. But how can we know this? And why you will leave a completely blank partition there ? Belive me there is nothing else than zeroes in it.
famewolf said:
I also considered the possibility they sold it as an 8gb because areas in the 2nd partition did not pass quality standards and could possibly result in data loss over time.
Click to expand...
Click to collapse
Not likely. The memory chip probably will not leave the factory with size bigger than the offered from the actual manufacturer of the device (the phone in this case). If there are bad blocks they will not be seen by the software and will not be available to the user at all. But this is only a speculation based on my limited knowledge on the NAND chips (and little googling about the NAND technology). For now my device works with internal memory twice bigger than the initial one and only the time will show how durable the memory chip is.
And hey this is xda-developers. Why we participate here if not to play with our devices ?
techware7 said:
Maybe the 6045i has 32GB??? Jajaja
Click to expand...
Click to collapse
Sorry...no userdatabak partition on the 6045.
Thanks for sharing that. Im very interested in expanding my storage but how would that work with any further update such as OTA or even rooting? Would we have to undo the partition, would the update force us to re partition afterwards, or does this thing have no influence whatsoever to all of this? Sorry if the question seems stupid
Sent from my 6039Y using Tapatalk
Rorshan said:
Thanks for sharing that. Im very interested in expanding my storage but how would that work with any further update such as OTA or even rooting? Would we have to undo the partition, would the update force us to re partition afterwards, or does this thing have no influence whatsoever to all of this? Sorry if the question seems stupid
Sent from my 6039Y using Tapatalk
Click to expand...
Click to collapse
Rooting has no relation to the expansion of the device internal memory. Regarding the OTA ... who knows. Do you have an official update? I do not. In the upgrade for the 6045 the checks were only for the system files and the recovery partition. But prior an official update we can't know how the same will work. Personally I don't think that the owner of a modified device should use the OTA prior to check what will happen after it.
petrov.0 said:
Rooting has no relation to the expansion of the device internal memory. Regarding the OTA ... who knows. Do you have an official update? I do not. In the upgrade for the 6045 the checks were only for the system files and the recovery partition. But prior an official update we can't know how the same will work. Personally I don't think that the owner of a modified device should use the OTA prior to check what will happen after it.
Click to expand...
Click to collapse
Okay. But then is there any way to undo these changes in order to get OTA updates? Would restoring from a system image or any other form of backup affect the partition and get it back to its original state? Or should we definitely not try to expand the memory if we want updates?
Rorshan said:
Okay. But then is there any way to undo these changes in order to get OTA updates?
Click to expand...
Click to collapse
The resizing of the partition does not require root access (except from the recovery during the resizing), so you will be able to check for OTA updates (from the phone) and to receive them (when such are available), if your device is not rooted. As I said earlier however, because we still don't have an official update, we don't know what will be the checks in it and also what modifications will be included.
Rorshan said:
Would restoring from a system image or any other form of backup affect the partition and get it back to its original state?
Click to expand...
Click to collapse
No, the size of the partition will remain the same. To restore its initial size you will have to use gdisk again (in order to change the GPT layout), or if you have a backup of the entire memory chip (mmcblk0) prior the repartitioning, to flash it back to the device.
Thank you for this great find. I can confirm partition #38 (7.3Gb) exists on my 6039Y -2AVDRO7. Still, I'll wait for feedback if future OTAs work ok with the extended partition space.
@petrov.0 did you try to write and read from the extended memory blocks after the new allocation? I mean, is there any chance that the partition was only simulated and data might get corrupted?
@ anyone can post the partition table from a 16Gb DualSIM 6039Y, out of curiosity? thanks
rioachim said:
Thank you for this great find. I can confirm partition #38 (7.3Gb) exists on my 6039Y -2AVDRO7. Still, I'll wait for feedback if future OTAs work ok with the extended partition space.
@petrov.0 did you try to write and read from the extended memory blocks after the new allocation? I mean, is there any chance that the partition was only simulated and data might get corrupted?
Click to expand...
Click to collapse
Yes I did. I filled all the space with raw partiton images and then checked their md5susms.