Database Users

[Q] WP7 won't boot!?!?!

Hi, So I followed directions on getting WP7 onto my HD2, namely the HSPL3, the 2.15 radio, the MAGLDR 1.13, and no matter which WP7 ROM I install via MAGLDR's USB Flasher, It always doesn't boot after a successful install(by successful I mean it says reset!...on the screen and "finished" on the computer). My boot screen looks like
LOADING WPH
WPH LOAD
123456
GO GO GO!
Then it goes back to the tmobile "stick together" screen and then back to the LOADING screen and repeat that
If I interrupt it with MAGLDR and pick Boot WPH, I will get the screen that says
WPH LOAD
123456
GO GO GO!
and that leads to the reboot circle too
I tried reinstalling HSPL3, MAGLDR, Radio, WP7 roms, and none of that solves the not-boot problem.
Interestingly, all the NAND-based Android Roms work decently on my HD2, except the occasional freezing problems.
Please help, I really want WP7 on my phone T_T. Thank you.
PS: I tried installing with and without my Sandisk 16GB Class 2 sd card, and also tried booting with and without it. None of those worked. When I did install WP& with the sd card in the phone, I always format it to FAT32 beforehand.

same here.........

I have the same Issue, WP7 installs fine, but wont boot, gets to the GOGOGO! text and then reboots, Ive installed WP7 in the past, (DFT first release) so I know it works, but any rom I try now does the same,(Reboots after GOGOGO!) I currently have Andriod installed, (MAGLDR 113) but would love to try and make the move over for good.
Does anyone have any ideas as to how to fix this issue?
Thanks.
PS: I have the original 2GB Sandisk SD card, (worked on this in the past) and a Kingstone 8GB SD card currently onboard my HD2.

I used the files downloaded from this YouTube Video Tutorial
Worked 100% for me...
Maybe try fully reinstalling a 6.5 rom then starting from scratch?

Me too.....
Same problem
sometime it boot with vibration??
I mean non-stop vibration
I try with my Samsung 16GB Class 2 and Kingston 8GB Class 4 but nothing different
Tonight, I will try with Sandisk 8GB Class 4!

Well just flash any WM 6.5 ROM & then flash MAGLDR & then any WP7 ROM

Just do a task 29, then start over with fresh install of magldr and WP7.
If you still have issues its more then likley your SD card not been compatible or having some issues. WP7 is really picky about cards.

htcfreak said:
Well just flash any WM 6.5 ROM & then flash MAGLDR & then any WP7 ROM
Click to expand...
Click to collapse
There is no need to install WM just so you can install WP7. Besides, doing this will further corrupt and future flashes.
Task29 first to complete erase all traces of previous ROM's and then MAGLDR, the WP7. Of course, it could be your SD card, as stated all over the WP7 for HD2 forum. WP7 is apparently very finicky about having a compatible SD card for its use. I would recommend at least a Class 4, but Class 6 cards may provide WP7 the speed it needs to function.

hjhjhj said:
There is no need to install WM just so you can install WP7. Besides, doing this will further corrupt and future flashes.
Task29 first to complete erase all traces of previous ROM's and then MAGLDR, the WP7. Of course, it could be your SD card, as stated all over the WP7 for HD2 forum. WP7 is apparently very finicky about having a compatible SD card for its use. I would recommend at least a Class 4, but Class 6 cards may provide WP7 the speed it needs to function.
Click to expand...
Click to collapse
Err...wrong.
There is a very good reason to reinstall WM to get WP7 on it, if the SPL is buggered flashing to a STOCK original ROM will bring the device back to its native state, then working forward from there will ensure that youve covered all your bases, the task29 business is not going to fix SPL issues.
yes you could use a new version of HSPL but from experience starting from scratch can be the best way, radio, ROM, SPL all stock, the work forward.

I try with flasing back to WM 6.5 original and then install MLDGR via bootloader and final is install WP7. They cannot boot and sometime they boot with non stop vibration
and also I try by do Task29 and install MLDGR and final is WP7. I found as the same problem like above
I try with my 3 sd cards
one is 16gb class 2 Samsung
two is 8gb class 4 Kingstons
three is 8gb class 4 Sandisk
How can i do to install for WP7??

Stock WM6.5
Then
HSPL
Radio
if you must, task29
MAGLDR
WP7 remember to put the SD card in first and once its finished flashing i unplug it too!

divinebaboon said:
Hi, So I followed directions on getting WP7 onto my HD2, namely the HSPL3, the 2.15 radio, the MAGLDR 1.13, and no matter which WP7 ROM I install via MAGLDR's USB Flasher, It always doesn't boot after a successful install(by successful I mean it says reset!...on the screen and "finished" on the computer). My boot screen looks like
LOADING WPH
WPH LOAD
123456
GO GO GO!
Then it goes back to the tmobile "stick together" screen and then back to the LOADING screen and repeat that
If I interrupt it with MAGLDR and pick Boot WPH, I will get the screen that says
WPH LOAD
123456
GO GO GO!
and that leads to the reboot circle too
I tried reinstalling HSPL3, MAGLDR, Radio, WP7 roms, and none of that solves the not-boot problem.
Interestingly, all the NAND-based Android Roms work decently on my HD2, except the occasional freezing problems.
Please help, I really want WP7 on my phone T_T. Thank you.
PS: I tried installing with and without my Sandisk 16GB Class 2 sd card, and also tried booting with and without it. None of those worked. When I did install WP& with the sd card in the phone, I always format it to FAT32 beforehand.
Click to expand...
Click to collapse
I have exactly the same problems! -> http://forum.xda-developers.com/showthread.php?t=1133664
Nothing works. Tried also Task 2a, Task 28, Task 29, installing WM 6.5...
The problem is not related to sd card, after go go go the device ist still restarting. After taking out the battery for 5 Minutes WP7 is starting, but if i restart the device, the booting loop continous...
Any suggestions?

I had these issue with my previous SD card.
I was using a sandisk 16 gb class 4. It booted first time, but then the more you install etc, the more unstable the card became, and every now and then, it would do this.
So, i FIRMLY believe that this is an SD card issue, i think, you should buy a new one, preferably not a massive 16 gb one, although i cant really give recommendations for the obvious reason.
Buy a new one, re-flash your phone with it in. DONT format it on your computer first, just leave it how it is, delete any software off it and put it in your phone.

Thank you for your answer,
the problem ist definitivly not related to SD Card. Because the rebooting issue after the magldr go go go happens also without a SD Card. I have also tried 5 other SD Cards:
Sandisk 16 GB Class4
Sandisk 16 GB Class2
Sandisk 8 GB Class2
Sandisk 4 GB Class2
Sandisk 2 GB Class 2
same problem.
Tried also the method which you explain in your post.... nada!
Installing and booting Android or WM 6.5 works perfect! Only after installing WP7 this problem happens, no matter which rom i use.
Tried also many radio roms,
Reinstalled OSPL and HSPL again.
Wiping device by Task 2a, Task28 or Task29....
It´s really strange!

I don't know if this would help, but I always format my SD card with my old nokia phone before I start the flashing process (Task 29 - Radio - MAGLDR - flash)

Jackson5 said:
Thank you for your answer,
the problem ist definitivly not related to SD Card. Because the rebooting issue after the magldr go go go happens also without a SD Card. I have also tried 5 other SD Cards:
Sandisk 16 GB Class4
Sandisk 16 GB Class2
Sandisk 8 GB Class2
Sandisk 4 GB Class2
Sandisk 2 GB Class 2
same problem.
Tried also the method which you explain in your post.... nada!
Installing and booting Android or WM 6.5 works perfect! Only after installing WP7 this problem happens, no matter which rom i use.
Tried also many radio roms,
Reinstalled OSPL and HSPL again.
Wiping device by Task 2a, Task28 or Task29....
It´s really strange!
Click to expand...
Click to collapse
it could still be the SD card, just because someone has tried 20 odd cards that didnt work doesnt mean that it must be something else
in saying that it should install without the SD card which would support your argument that the SD card isnt 100% at fault
did you try going back to a stock ROM, flashing via SD card and not via USB?

dazza9075 said:
it could still be the SD card, just because someone has tried 20 odd cards that didnt work doesnt mean that it must be something else
in saying that it should install without the SD card which would support your argument that the SD card isnt 100% at fault
did you try going back to a stock ROM, flashing via SD card and not via USB?
Click to expand...
Click to collapse
Yes installing WP7 without sd card does also not solve the problem.
Had also installed 2 different Stock Roms (3.14 and 1.72) via sd card -> nothing!
If i use Mtty and run info 8, i get the following info:
DEVICE NAME=samsung_KBY00N00HM
DEVICE ID=0xBC
DEVICE MAKER ID=0xEC
PAGE SIZE=0x800
TOTAL PAGE SIZE=0x840
BLOCK COUNT=0x1000
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 28 (0x1C) is reversed block
BLOCK 29 (0x1D) is reversed block
BLOCK 30 (0x1E) is reversed block
BLOCK 31 (0x1F) is reversed block
BLOCK 1635 (0x663) is bad block
BLOCK 2920 (0xB68) is bad block
BLOCK 3527 (0xDC7) 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=0x1DD40
Partition[3], type=0x4, start=0x1EDC0, total=0x18DC0
CE Total Length(with sector info) = 0xF7D6E00
CE CheckSum Length(without sector info) = 0xF6E0000
Task 28 or Task29 does not repair these blocks. I think that these bad blocks cause this problem...
maybe another one with the sam problem can try to use info 8 to check, if he has also bad nand blocks

[Q] NAND for 1024 v 512 leo

I have a Leo 1024 and am trying to figure out which roms I can use. I know the rule of thumb is to not use a Rom unless it specifically says it's ok for your device, but I've found that many threads don't mention anything about which version of the phone it is compatible with.
So, should I assume that if it doesn't explicitly state a Rom is only for a 512 Leo, it will work fine on my device? If I did install one, like a cyanogen mod, what would the drawbacks be? Would I just not be able to use the extra space on my device?
Thanks in advance.
Sent from my HTC HD2 using XDA App

That rule is for Windows Mobile 6.5 ROMs, not Android. As long as you have flashed MAGLDR (and preferably Clockwork Recovery too) , you can use any nand Android ROM you want, just follow the installation instructions in the particular ROM's thread.
-HD2 Android-

Thanks for the help. So I won't kill my phone by doing it, but will I lose out on any space if I use one made for a 512 as opposed to one optimized for a 1024? Or am I just making stuff up here?

That depends on the size of the build. Some of the early roms made for the 512 device were squashed and had apps removed etc. In this case you will have plenty of internal memory to install from the market.
The more recent Desire HD based builds are now no longer squashed, so in order to still fit on the 512 device data and apps are moved to partitions on the sd card. For the 1024 device you however don't need the sd card partitions and you will use more of your 1024 device's internal memory.

To expand on that, my understanding is you can use any ROM on the 1024, it's only if you have a 512 phone that you need to take more consideration.
If you take the 512 route, you'll be formatting your SD card into new partitions etc, which is pointless if you have a 1024 phone as you'll just be straining your memory card/battery-life for no reason.

Correct

how to find out if my phone is a 512 one or a 1024 one ??
plz help....

Bad Blocks Help

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???

[Q] Fault in sdcard reader? WP7 works though

I have been having trouble lately booting any sd build or nativeSD rom from sd card.
I have tried formatting cards in windows (including sdformatter) and linux (gparted), re-installing hspl, wm6.5 then magldr, but to no avail.
I get a message in 4ext sd recovery saying that the sdcard has only 1 partition of size "null", it doesn't recognize sdext or swap partitions.
When i try to run an sd build, it reboots (attached dmesg).
All this is despite the fact that wp7 is installed in nand and runs without any problems, this i think means the sdcard reader is not at fault.
I first reported this in here (and up to post #727).
Any ideas?

I have realized that WP7 works even without an SD-card inserted, so a working WP7 is not a proof that a card is functioning well. I don't have anything more, sorry

magldr's clear sd. have you tried that?
also, try using minitool partition wizard bootable disc to erase and wipe everything on the card, and recreate partitions and try again

I have copied the posts in that thread and posted them here, if the problem is resolved, I will delete those posts, to keep that dev thread tidy, as has gilbert32 (I might do it anyway)
Post 1
Hi securecrt, it booted first time and after upgrading apps (not fresh install) it rebooted to bootanimation then went to lockscreen. I was able to play around with it for a bit and even managed to record a video (it doesn't play back on pc btw) but then gallery FCed and i got a reboot to magldr. Since then it doesn't want to boot past htc screen (attached dmesg).
I will try a fresh formatted sdcard and fresh install. Have to backup stuff first.
WP7 not affected though
attachment- http://forum.xda-developers.com/attachment.php?attachmentid=2014818&d=1370285990
Click to expand...
Click to collapse
Post 2
Since trying securecrt's kernel on nativeSD, i have been unable to boot any nativeSD rom or any sd build on any of my sdcards.
However wp7 does boot ok, so it can't be my sdcard slot, which i thought might be the problem.
I am at a loss to explain it.
My 4ext sd recovery says that it can't mount the sdcard and does not show any partitions apart from fat32 of null size and B under free.
Please can anyone confirm this, and pretty please do not try to boot this until someone can explain what has happened
Click to expand...
Click to collapse
Post 3
gilbert32 said:
not sure but maybe while you were recording a video, the sdcard fat32 partition got somehow corrupted? can you try running diskcheck on your pc to make sure it's correct?
and as i understood, after trying to shoot video, gallery FC'ed and it rebooted?
Click to expand...
Click to collapse
I have 3 cards, for nativeSD. None of them are working. that is 3 sd recoverys, 1 on each. all show the same. sd builds dont boot either. Something in phone is wrong.
I can try re-installing magldr or wm6.5. But would like to try and work out what is wrong first, for others
Click to expand...
Click to collapse
marco.palumbi replied
I guess that you tryed to remove the battery and let the phone stay for some minutes before inserting it again.....
Click to expand...
Click to collapse
Post 4
Trying that while i type this. Last night i managed to boot a couple of nativeSD roms but after rebooting they refused to boot again. Also one of the cards showed normal partitions in recovery, then later i looked again and all 3 were only showing fat32 of null size.
Really confusing.
After leaving battery out for 5 mins, i looked in recovery and saw all 3 partitions. But couldn't boot sd build, nor nativeSD.
Another odd thing is the led on my card reader doesn't seem to want to stay steady, it keeps flashing intermittantly as if being accessed, i have to wait for it to settle before removing. After swapping out initrd.gz and zimage for another nsd rom to test, i look at recovery and get fat32 null again. Perhaps the problem is in pc, idk. New nsd rom doesn't boot either.
Edit; have attached dmesg of last nsd attempt, tytung's ics
Attachment- http://forum.xda-developers.com/attachment.php?attachmentid=2016224&d=1370337872
Click to expand...
Click to collapse
Post 5
gilbert32 said:
I'd say it's time to go back to stock wm rom and try booting an sd or nativesd rom. if it fails, maybe try formatting a card with wm's format utility (which unlocks wp7's sd card) and try again. i'd say the kernel + initrd.gz have affected magldr and the card's mbr somehow
Click to expand...
Click to collapse
I think you are right gilbert32, something is wrong.
I just booted into ubuntu on pc and swapped out initrd.gz and zimage for another nsd rom, not booting. No flashing led this time. I had the phone battery out whilst changing OS on pc, recovery shows null still.
WM6.5, here i come again
Edit; I installed wm6.5 (had to do it twice, first time had an error box appear, not seen that before)
2 out of 3 cards were not seen by wm6.5, 3rd card was seen and i managed to boot a nativeSD rom, but after reboot recovery showed fat32 null and couldn't boot after.
I installed magldr and used fourth card i used for wp7. After formatting with sdformatter, deleting mbr, creating partitions with minitool installing sd 4ext recovery, recovery shows fat32 null again.
Tried to install twrp2.2.1.4 but it doesn't boot.
I think i am going to have to re-install hspl.
Sorry marc1706 for hijacking your thread with all this
Click to expand...
Click to collapse
securecrt posted
...It will not break anything. ...
Click to expand...
Click to collapse
(I believe securecrt BTW, it is what makes this so puzzling to me)
Post 6
Thanks gilbert32, I flashed hspl, now i cant flash wm6.5, or reflash magldr, or run any nativeSD build (if i get one to boot it just hangs), so you could say it is serious
I have put my sim in an old(er) phone for now since waiting on calls.
I had formatted the card fat32 32kb clusters.
Gonna give it a break for now, i have been at it on and off all day. need to get things done.
It is odd that 4ext sd always boots regardless of whether anything else does.
Anyway, i am conscious of the fact that it is probably my hardware that is at fault. Until someone else posts in this thread with similar problems I will refrain from further posts here.
Thanks again.
Click to expand...
Click to collapse

gilbert32 said:
magldr's clear sd. have you tried that?
also, try using minitool partition wizard bootable disc to erase and wipe everything on the card, and recreate partitions and try again
Click to expand...
Click to collapse
I used clear sd (and last 24mb nand) when re-installing wp7 after hspl etc.
Not sure about a bootable disk, I used minitool on windows 7 (I dual boot pc win7/ubuntu)

Marvlesz said:
I have realized that WP7 works even without an SD-card inserted, so a working WP7 is not a proof that a card is functioning well. I don't have anything more, sorry
Click to expand...
Click to collapse
But it is fully functional, i can even view contents of sdcard fat16 partition which has an android sdbuild on it (which also doesn't boot)

Robbie P said:
I used clear sd (and last 24mb nand) when re-installing wp7 after hspl etc.
Not sure about a bootable disk, I used minitool on windows 7 (I dual boot pc win7/ubuntu)
Click to expand...
Click to collapse
well i'd try minitool bootable disc. only 40mb. and i always use it when coming from wp7. sd would usually not get recognized on wm without using it so try it.
just delete all volumes on the sd (DO NOT DELETE THE HARD DISC's VOLUMES, ONLY SD )and create one fta32 partition and try 4ext recovery
Robbie P said:
But it is fully functional, i can even view contents of sdcard fat16 partition which has an android sdbuild on it (which also doesn't boot)
Click to expand...
Click to collapse
with my experience, android needs fat32 partition not wp's 200mb fat16 partition

gilbert32 said:
well i'd try minitool bootable disc. only 40mb. and i always use it when coming from wp7. sd would usually not get recognized on wm without using it so try it.
just delete all volumes on the sd (DO NOT DELETE THE HARD DISC's VOLUMES, ONLY SD )and create one fta32 partition and try 4ext recovery
Click to expand...
Click to collapse
I tried minitool bootable disk and formatted the whole card with FAT32 (32Kb clusters, aligned to cylinder (also tried aligned to Mb) with same result, null in 4ext recovery, and an sd build doesn't boot.
with my experience, android needs fat32 partition not wp's 200mb fat16 partition
Click to expand...
Click to collapse
I know, but it (usually) works on that partition. I posted a thread on it here, it was a proof of concept (no formatting/repartitioning needed) and also charges extended batteries in wp7.

it seems more and more about hardware problem.....
can you post a few more dmesg's ?

gilbert32 said:
it seems more and more about hardware problem.....
can you post a few more dmesg's ?
Click to expand...
Click to collapse
1. Leo king sd build (reboots)
2. PA beta v1.992 sd build (reboots)
3. jellycarbon nativesd (hangs on splashscreen)
4. miuiv15b nativeSD (hangs on splashscreen)
5. miui THANHVO31 nativesd(hangs on splashscreen)
6. Sense4a sdbuild (reboots)
...

Robbie, you're located in London right? I'm in Portugal, i can send you a hd2 motherboard for you to test, this motherboard is fully functional, the problem is that it overheats if you stress it too much, but at least you can check if the problem is your motherboard or not.
Cheers
Sent from my GT-I9300 using Tapatalk 2

yugoport said:
Robbie, you're located in London right? I'm in Portugal, i can send you a hd2 motherboard for you to test, this motherboard is fully functional, the problem is that it overheats if you stress it too much, but at least you can check if the problem is your motherboard or not.
Cheers
Sent from my GT-I9300 using Tapatalk 2
Click to expand...
Click to collapse
I've seen a video of disassembling and reassembling of hd2 and it makes my palms sweat thinking about it
I have a cracked screen on my phone and was thinking of replacing the digitiser anyway. So I might take you up on your kind offer. I will see if anyone else has any ideas first:fingers-crossed:
Thanks mate.:good:

Robbie P, can you try installing a nand rom like cm7 only on nand?
and nativeSD roms hang on splash screen right? if so, maybe you can use adb. try mounting system manually and data too, then type stop and start
maybe sd isn't mounting well.
also use cd to /dev/block . is mmcblk0pX present there?

It seems that on first android boot after coming from wp7, i am more likely to be able to boot into nativeSD android. Subsequent boots don't work. But it only works sometimes. And the time i managed to boot into tytung's ics, i got a bsod after a call (attached dmesg, seems i lost sdcard).
It looks more to me like a hardware issue with my sdcard port.
I haven't tried nandroid yet. And when it isn't working, i can't connect to phone with QTadb.

Robbie P said:
It seems that on first android boot after coming from wp7, i am more likely to be able to boot into nativeSD android. Subsequent boots don't work. But it only works sometimes. And the time i managed to boot into tytung's ics, i got a bsod after a call (attached dmesg, seems i lost sdcard).
It looks more to me like a hardware issue with my sdcard port.
I haven't tried nandroid yet. And when it isn't working, i can't connect to phone with QTadb.
Click to expand...
Click to collapse
Code:
[ 2.930053] @@@ SD power 17 @@@
[ 2.999237] @@@ SD power 15 @@@
[ 3.141662] mmc1: host does not support reading read-only switch. assuming write-enable.
[ 3.141723] mmc1: new high speed SDHC card at address e624
[ 3.142150] mmcblk0: mmc1:e624 SU32G 29.7 GiB
.........................................
[ 126.136596] FAT: Directory bread(block 29848915) failed
[ 126.143280] auo_panel_cfg_setup exit
[ 126.954467] EXT4-fs error (device mmcblk0p2): ext4_find_entry: reading directory #409602 offset 0
[ 126.954650] EXT4-fs (mmcblk0p2): previous I/O error to superblock detected
you are right i think. sd card slot is probably somehow loose and sd is getting disconnected. maybe after booting tytung's ics, after the call, holding the phone and moving it in hand made the sd card get lost again. try booting multiple times, each time removing and reinserting the sd. ig it works more often, then that's your problem

I've sussed it
I found somewhere that says you can clean the sdcard slot with a piece of card wetted with alcohol (remove battery first). I tried it dry first and found dirt corresponding to the outside contacts of the card. It started booting, but gave a few errors and not all my SDcards showed correct partitions. So i tried wetting a new piece of paper card with GF's nail polish remover and inserting it in and out of slot (paper card should be same width as contact end of sdcard (if it is smaller, it could move from side to side and snag one of the phones contacts)).
It all seems good now.
Thanks gilbert32, yugoport & marvelz for your contributions. Much appreciated.
Looking at the dirt on the dry paper card, most dirt was on pin 8, some on pin 1 (see wikipaedia, tech details,transfer mode), so they only get used in 4-bit bus mode. Perhaps this is the reason why android wouldn't work, but wp7 does.
Lastly, i noticed that my wp7 card (16gb "old" card) has the sides worn down and metal is showing. The plastic from this could have covered the phone pins 1 & 8, or it could have been fluff
Back on android again:highfive:

Robbie P said:
I've sussed it
I found somewhere that says you can clean the sdcard slot with a piece of card wetted with alcohol. I tried it dry first and found dirt corresponding to the outside contacts of the card. It started booting, but gave a few errors and not all my SDcards showed correct partitions. So i tried wetting a new piece of paper card with GF's nail polish remover and inserting it in and out of slot (paper card should be same width as contact end of sdcard (if it is smaller, it could move from side to side and snag one of the phones contacts)).
It all seems good now.
Thanks gilbert32, yugoport & marvelz for your contributions. Much appreciated.
Looking at the dirt on the dry paper card, most dirt was on pin 8, some on pin 1 (see wikipaedia, tech details,transfer mode), so they only get used in 4-bit bus mode. Perhaps this is the reason why android wouldn't work, but wp7 does.
Lastly, i noticed that my wp7 card (16gb "old" card) has the sides worn down and metal is showing. The plastic from this could have covered the phone pins 1 & 8, or it could have been fluff
Back on android again:highfive:
Click to expand...
Click to collapse
That's great! i'm glad you got it sorted out
Regards

gilbert32 said:
That's great! i'm glad you got it sorted out
Regards
Click to expand...
Click to collapse
It seems i posted too soon earlier, and it is back to showing null in recovery
Looking at the sd port, there seems to be a piece of metal sticking up around the area of pin 1 (rhs), so i think it has broken (possibly not helped by me prodding it with bits of card). Wp7 still works though. I took the case off and the port is soldered to the motherboard, so no chance of fixing it, for me at least.
Anyway, I have bought a second hand hd2 from one very careful lady owner (wm6.5 user), never been flashed, no scratches, looks brand new, no bad blocks and cheap. I showed my hd2 with cracked screen to the seller with wp7.8 on it and booted an sd android on the new one to check for connections etc. they were impressed but sold it nonetheless (they said "how did you do that?", I said that it was extremely complicated)
I now have a hd2 with wp7.8 and a hd2 with slim jb on nand dataonext, and I am a happy bunny again

Robbie P said:
It seems i posted too soon earlier, and it is back to showing null in recovery
Looking at the sd port, there seems to be a piece of metal sticking up around the area of pin 1 (rhs), so i think it has broken (possibly not helped by me prodding it with bits of card). Wp7 still works though. I took the case off and the port is soldered to the motherboard, so no chance of fixing it, for me at least.
Anyway, I have bought a second hand hd2 from one very careful lady owner (wm6.5 user), never been flashed, no scratches, looks brand new, no bad blocks and cheap. I showed my hd2 with cracked screen to the seller with wp7.8 on it and booted an sd android on the new one to check for connections etc. they were impressed but sold it nonetheless (they said "how did you do that?", I said that it was extremely complicated)
I now have a hd2 with wp7.8 and a hd2 with slim jb on nand dataonext, and I am a happy bunny again
Click to expand...
Click to collapse
that's good
a friend gave me an hd2 without screen/digitizer. it was supposedly fully working but misses those 2 components.
took it to a local store that is an EXPERT in fixing htc phones (called htc solutions ). they said they had to check if the motherboard was working. it was supposed to be okay. sadly, nope.
they sad it was damaged, so i'm taking it back for the battery

gilbert32 said:
that's good
a friend gave me an hd2 without screen/digitizer. it was supposedly fully working but misses those 2 components.
took it to a local store that is an EXPERT in fixing htc phones (called htc solutions ). they said they had to check if the motherboard was working. it was supposed to be okay. sadly, nope.
they sad it was damaged, so i'm taking it back for the battery
Click to expand...
Click to collapse
I know of a very nice person in Portugal with a spare motherboard :fingers-crossed:

wifi problem

Hello.
Friends I have a strange problem. wifi don't work on android os.....but it work on wp7 and wp6.5 as well.
I tried : cm....miui...and other android roms on clk and magldr.......
plz help

Hi imanaab, are you using NAND android roms? Only thing I can think of is that there is a bad block in your nand right where the OS wifi commands are.
Try NativeSD, or an SD build to check, or increase the size of your /system partition might do it.

Robbie P said:
Hi imanaab, are you using NAND android roms? Only thing I can think of is that there is a bad block in your nand right where the OS wifi commands are.
Try NativeSD, or an SD build to check, or increase the size of your /system partition might do it.
Click to expand...
Click to collapse
yes I tried sd but wifi still not work