Failed Flash - Touch Diamond2, Pure General

Hi guys, first of all I would like to know where my original post is, did it get deleted??? it was about the warning message for the battery level right at the AT&T screen... but anyways....
I was recommended to flash the original ROM from HTC,(AT&T Pure) I did and Im having a big problem?, phone gets recognized as usb, flash process starts BUT right at 9% it seems that the device reconnects itself to the usb and then I get a BSOD with multiple IRQ requests error, tried 2 or 3 times disconnecting any other usb device from the pc and still get the same at the exact 9% of flashing...
Would that be a windows problem? Im using XP, please advise
Thanks.

You have to connect with ActiveSync and not as USB Mass Storage.

ialafroz said:
Hi guys, first of all I would like to know where my original post is, did it get deleted??? it was about the warning message for the battery level right at the AT&T screen... but anyways....
I was recommended to flash the original ROM from HTC,(AT&T Pure) I did and Im having a big problem?, phone gets recognized as usb, flash process starts BUT right at 9% it seems that the device reconnects itself to the usb and then I get a BSOD with multiple IRQ requests error, tried 2 or 3 times disconnecting any other usb device from the pc and still get the same at the exact 9% of flashing...
Would that be a windows problem? Im using XP, please advise
Thanks.
Click to expand...
Click to collapse
I cant connect it using activesync, that is the problem, before it used to give this battery warning at the att splash screen, now with this failed flash phone is stuck at the 9%, I will need to try this from a different pc

try to flash from sd card. it's quite easy. search Topaz section of this forum and you'll find how to. if it's fails, then you'll probably have to do MTTY. and this is not easy

flash success
OK, I tried from a different computer and it finished ok.
Unfortunately the Warning batt low message still is there.

Related

exec wont start

Hello,
this is what the problem is, the power button doesnt bring it back to life. i do a soft reset, it says press zero to clear, i do that it doesnt work. then i do a hard re-set and it shows 'serial', i plug in the usb and it changes to USB (think that's what is called the boot loader'.
now i ran teh exec official firmware, it managed to update it onces but after that i did a soft reset and it didnt come to life. i repeated that process again but this time the firmware didnt even manage to communicate with the device as it said unknown usb device. and then i got an error 101, connection error
any ideas whati can do to make sure it gets restored, i am really going nuts now!!
Same Problem
I am having the same problem with my 02 exec. My phone keeps on being in bootloader, I have tried mtty and I don't have usb connection. Hmm I have tried uni_exitbootloader ,but it tells me that it can not open my usb port. Which sucks. Truely and I am stuck. I am running vista. So I am stumped because I don't know what else to do.
Me too
I am stuck on bootloader page the one that says USB at the top and V1.00 at the bottom. I have Vista so can not use mtty or the other one. I have turned off the USB on Windows Mobile thingy from Vista like activesync. I can get the white screen to show O and X for either factory reset or exit. And I have tried the bootloader screen as noted above. So can anyone help?
i got it working for 2days and then when i was on wifi, it crashed again and wont start again, i get to serial/usb mode of bootloader and also to hard reset when i press 0 to clear everything. but then it doesnt start again.
i thought it was something to do with the battery so i put in a new battery but that still doesnt help.
can someone send me a link to mtty and what to use it. i shall give that a try again.
thanks
mines just still stuck
same im still stuck in boot loader wont budge from he bootloader screen with serial v1.00 on cannot connect via usb as the connection broken i use a extrunal battery charger and got serveral batterys any help yet?

Executive dead after update??

Can the experts explain this one or sugest a solution???tryed to flash the new rom on to my beloved xda......the rom was the latest "1933.18533_Thingonaspring.ROM.v3.2" but when running the flash the strange messaged showed up......error flashing rom...from there onwards the device is not recognised on my pc...Have tried in my laptop with the same result....any clues???
many thanks.....
long live buzzzzzz
Try to uninstall the ActiveSync, restart PC and reinstall ActiveSync again.
On your Uni, go to bootloader, will display Serial, plug in USB Cable, will display USB. Run NOID flash program to reflash your Uni.
If still can recogniced your Uni, pls try to change other USB port or other PC (Win XP).
I think I have nice paper weight
Have tryed to get the uni in boot mode but it shoes balck screen with no boot mode at all.have also tryed on my laptop but as soon as I plug it in it say device not recognised..I did try to recover from a bad flash but with no luck..
Cant think of any more solutions.........
Go to the HTC offical site and download an offical rom for Universal.Go to bootloader and get connected to your PC,no matter it is recogized or not,run the exe file you just downloaded,it will flash the rom in your device.When upgrading finished,power on ,and you may flash any rom you like to your device now.
It might useful to get a fully charged battery and to try going into bootloader mode, if that fails, then you your best bet have to send it back to your vendor to get it repaired
thats the problem.....
thats the problem...cant get the uni in bootmode....I do press light+power+reset and the screen is dead....tryed to charge the baterie just in case but the light on the uni starts to blink red and thats it.......I'm getting the impression that the uni became a paperweigth......sadly.....
I think should empty the battery, try to charge your battery over 12 hrs or borrow other people battery to test can go in to bootloader mode or not ?
If can go, try to check the USB Connection at your Activesync and than to flash, or try to uncheck the USB Connection at your Activesync and than flash.
My Uni also same like this problem before, my laptop got 2 USB port. 1st port i try the above mention, still cant recognized my Uni. So i try 2nd port, and Uni was recognized.
done it all....no joy
have done all that sugested but still no joy..I think that during the room flashing a power supply problem on the pc caused this....could it be that the uni became a paper weigh due to the room flashing ???If there was a power supply problem.....Is there anyway to recover the uni from a bad room flashing???

Hermes is stuck in bootloader(tri-color) after failed update.

Okay, so I've already done a quick search of the forums and haven't found a situation close enough to mine to remedy my problem.
I was trying to update my ROM. I was flashing it when the progress bar stopped around 13%. After that, When I tried recovery, it seemed to stop detecting the phone at all. That is when I started looking around for other fixes.
Phone will start up into boot-loader(the tri-color screen), which shows
HERM100
IPL-1.03
HERM100
SPL-1.11
Now the main problem is that none of the updaters work because my computer cannot even detect that the phone is plugged in. When I try to plug it in, the computer shows "Unrecognized device". I use Windows Home Premium.
I've also tried MTTY. There is no USB option from the dropdown menu. I've killed Windows Mobile Device Center before trying this option.
Help me guys! What should I do?
http://forum.xda-developers.com/showthread.php?t=420135
see post 6 and later

Wizard won't start

Dear users,
My Wizard won't start.
Information:
- Stuck at bootloader
- Hard reset won't work
- Updating (at windows xp) won't work, as it stops at 99% (tried 3 roms, even the original from t-mobile). Giving a communication error and my wizard keeps rebooting.
When did this start? After using Button_rom 1.5, it stopped at 99% =)
Anyone that can help me?
Thank you
ErnstJanF said:
Dear users,
My Wizard won't start.
Information:
- Stuck at bootloader
- Hard reset won't work
- Updating (at windows xp) won't work, as it stops at 99% (tried 3 roms, even the original from t-mobile). Giving a communication error and my wizard keeps rebooting.
When did this start? After using Button_rom 1.5, it stopped at 99% =)
Anyone that can help me?
Thank you
Click to expand...
Click to collapse
Mostly,Communication errors are due to weak or drained battery,get it fully charged.
Secondly,get the phone in Bootloaders (RGB) screen and hook it up with pc via usb cable and watch small usb appear at the bottom of the Bootloader,if its there,then reflash the official rom,if its not there,then its a connectivity problem.Either the usb cable is faulty or the mini usb port of the phone.You can even try by changing and plugging the usb cable in another pc usb port.
BTW, remove any sdcard or minisd inserted in the phone before flashing.
zabardast_1 said:
Mostly,Communication errors are due to weak or drained battery,get it fully charged.
Secondly,get the phone in Bootloaders (RGB) screen and hook it up with pc via usb cable and watch small usb appear at the bottom of the Bootloader,if its there,then reflash the official rom,if its not there,then its a connectivity problem.Either the usb cable is faulty or the mini usb port of the phone.You can try be changing and plugging the usb cable in another pc usb port.
Click to expand...
Click to collapse
Thank you,
My phone had problems recently. It won't start without power cable. And it suddenly shutdowns as I am playing games or listening to music.
It allways hangs at 99%, and with the original ROM it hangs at 80% and also gives the error. It just reboots =(
Ive powered the phone up the all night, after that I tried to flash a rom, but it gave me the exact error at 99%.
Anyone that can help me?
ErnstJanF said:
Thank you,
My phone had problems recently. It won't start without power cable. And it suddenly shutdowns as I am playing games or listening to music.
It allways hangs at 99%, and with the original ROM it hangs at 80% and also gives the error. It just reboots =(
Ive powered the phone up the all night, after that I tried to flash a rom, but it gave me the exact error at 99%.
Anyone that can help me?
Click to expand...
Click to collapse
smell like a bad battery.
revertive said:
smell like a bad battery.
Click to expand...
Click to collapse
New battery is coming in tomorrow, I will test it =)

[Q] HTC HD2 Won't charge or be recognized via USB

Hello,
I recently successfully installed Windows Phone 7 rom onto my HTC HD2. The phone was working fine and would charge the battery when connected to a dedicated charger on the wall plug as well when it was plugged into another computer. I recently attempted to plug the phone into the computer via USB only to find it wouldn't recognize it ,no prompts on the computer or the orange light on the phone. I turned off the phone, removed the battery for several minutes, I started the phone up again and it would boot into Windows Phone 7 normally without any errors but still it would not be recognized by the computer or allow itself to be charged by an external battery power. I had read somewhere that if I where to select Mass Storage option off the bootloader that it would charge the battery and create a partition on the computer. Huzzah! the computer recognized the partition, but the battery still wasn't charging. Going through multiple threads I have read that it might Magldr others say it's the windows phone 7 rom not being fully stable yet and messing with the battery settings, I don't know where to go from here, i'm hoping someone can help. Here are the direct steps that I took since I got the phone:
Phone: HTC HD2 T Mobile
1. Unlock the phone (successfully)
2. installed HSLP3
3. Flashed Radio leo 2.15.50.14
4. Installed/Flashed MAGLDR113
5. Using USB Flasher installed the LEO70_ROM
That's all no settings afterwards were messed with, and Windows phone 7 came up normally and worked perfectly.
Side note: I have tried multiple micro USB cords and different Socket Wall Chargers.
Any assistance is greatly appreciated.
Thanks,
Mr_Pickles
I've yet to find out why it does this, or a step by step guide to fix it, however it is fixable, it will charge battery if you boot to magldr mode, no light will come on but it does charge, mine done this before and came out of it seemingly by its self, or more likely by a combo of things I did, anyhow, charge it up in magldr first, also try using usbdview to list all your USB devices, delete them all, windows can get confused some times
well fancy that, just happened to me again there, ok, so was at work, and my phone wouldnt take a charge via the socket or USB port on a working PC, like i said before it does charge via magldr
anyhow, just got home and plugged it in to my PC that i know it syncs with and all was fine.
So for you i'd definitely suggest deleteing your USB devices to make sure there is no conflicts, charge up your phone via a wall charger in magldr, then get it working with your PC, perhaps then you will get it working,
Thanks, it still isn't charging when it's on MAGLDR, i'm starting to think the battery might be dead. Either way I've ordered an external battery charger and an extra battery, hopefully that solves my issue. Although it still perplexes me why when attempted to connect to a computer it doesn't recognize it.
Unfortunately at this point the battery is completely drain so I can't do anything until the charger and the extra battery comes, but until then i'll keep digging for the answer.
Cheers,
Mr_Pickles
Mr_Pickles said:
Thanks, it still isn't charging when it's on MAGLDR, i'm starting to think the battery might be dead. Either way I've ordered an external battery charger and an extra battery, hopefully that solves my issue. Although it still perplexes me why when attempted to connect to a computer it doesn't recognize it.
Unfortunately at this point the battery is completely drain so I can't do anything until the charger and the extra battery comes, but until then i'll keep digging for the answer.
Cheers,
Mr_Pickles
Click to expand...
Click to collapse
ah yes that is a problem, youve got the charger coming so its a bit late now but that happened to me once, if its just a bit too dead to get you to magldr to charge then i found if you pop it out, wrap it in a cloth and warm it up, do not place it directly on a heat source, by warming it up a bit it helps give it a wee nudge with its chemical reactions inside, potentially enough to get in to magldr.
there is no way of knowing if its charging via magldr other than it not turning off. but with an external on the way you will be fine.
as for it having issues
im guessing its because the battery controller on the HD2 isnt the same as the controller from where the ROM was pulled, meaning whilst its compatible, its not ideal, the not connecting thing could be a symptom of this, im just guessing here but if lets say the battery controler forgets what its doing could that knock out the who USB connection, the USB ports on the computer will have com ports connected whilst the charger will only have the power ports connected, perhaps a combo of all of these things is the reason
but what id do is get it charged first, use the program USBDVIEW (google it) and remove all USB devices associated with a connection to a HUB reboot and connect the HD2 (fully charged) to a different port than usual. it should install drivers and away you go!
Ok! So i got the charger and did all the steps below but still nothing, the computer won't recognize the phone through USB unless I go to Mass Storage option off of MAGLDR. Any thoughts?
The Windows 7 OS runs just fine. It's the connection to the computer/charger through USB that is the problem. Even when loading the boot loader (multi color screen) and then connecting the USB it won't recognize it, the bottom stays on "Serial".
Any help would be much appreciated.
Thank you,
Mr_Pickles
righty, this could be a challenge,
so usb storage mode IS detected when you plug it in with magldr
therefore we can rule out hardware issues
So physically it will connect, that leaves several different possible issues
first things first, you didnt mess about with USB tethering did you? i really hope you didnt and if you did you better start praying your phone is still unlocked and will allow unsigned apps, and that you still have the USB tethering app installed!
next, WP7 software issue, something is buggered stopping it for connecting,
unlikely if you cant connect via the SPL
Desktop Driver issue.
if there is any USB conflict on your PC it can create many problems for you did you try uninstalling all USB devices using USBDVIEW in admin mode, then try plugging it in again?
ok some other questions, does MAGLDR allow you to go to and use USB flasher mode, as if you where updating you WP7 ROM? does your PC connect and install a device driver when you plug it in? (make sure you deleted all USB devices before hand)
lastly, do you have access to another computer that has NOT had this phone plugged in to?, purely to see if it will get detected in SLP mode or ideally in WP7 itsself? this would obviously rule out your whole PC and would help pinpoint the issue!
Hi Dazza,
Here are the answers to your questions:
Q: first things first, you didnt mess about with USB tethering did you? i really hope you didnt and if you did you better start praying your phone is still unlocked and will allow unsigned apps, and that you still have the USB tethering app installed!
A: I did not mess with the USB tethering, my phone is still unlocked.
Q: Desktop Driver issue.
if there is any USB conflict on your PC it can create many problems for you did you try uninstalling all USB devices using USBDVIEW in admin mode, then try plugging it in again?
A: Yes I did, it still did not connect to the device, not allowing to view it as a storage device or charge the phone. The phone also does not recognize that it has been plugged in to the computer.
Q: ok some other questions, does MAGLDR allow you to go to and use USB flasher mode, as if you where updating you WP7 ROM? does your PC connect and install a device driver when you plug it in? (make sure you deleted all USB devices before hand)
A: Yes it does, it installs the drives and the phone shows the connection has been made through USB.
Q: lastly, do you have access to another computer that has NOT had this phone plugged in to?, purely to see if it will get detected in SLP mode or ideally in WP7 itsself? this would obviously rule out your whole PC and would help pinpoint the issue!
A: Yes I have. I tried 3 different computers and none of them recognize the phone.
Side notes:
- I have flashed an Android ROM to see if that would fix the error so I can switch back to WIN 7, but even with the android ROM the computer still does not recognize the phone being plugged in, nor does the phone recognize it has been plugged into the computer.
- When I have gone to the bootloader (multi color screen) in my attempts to bring back the phone to it's orginal state, it still does recognize the phone and won't let me install the base OS and radios for the phone.
I hope this info helps, man i'm really starting to regret getting this phone.
Thanks,
Mr_Pickles
ok, think we need to start again, its sounding all a bit dodgy, MAGLDR is working but the bootloader and WP7 itsself isnt....
you tried reflashing android to no effect
the only common denominator is the SPL/HSPL and the Radio
However because bootloader isnt working in USB mode you cant flash....
SO, next attempt is.....
Format a small SD card, format it as FAT32 or if that fails try FAT16 (512MB card) this is the tricky bit because some cards will not work.
Downloaded the original ROM for your device, usually a .exe file
Open the exe with a zip/rar program,
Extracted RUU_signed.nhb,
Move ruu-signed.nbh to your sd card,
Rename ruu_signed.nbh to leoimg.nbh
Then power phone off,
pop your small SD card with leoimg on in your HD2
Press and hold volume down, tap power but contiue to hold vol down.
The phone should boot into bootloader mode, and it "should" automatically discover there is a leoimg.nbh file on your sd card and ask you to flash.
If it is the wrong image, you should get a failed install message, but if you phone does nothing at all then either the sd card is faulty or the sd card reader is faulty (unlikely if WP7 was using it), or the nbh file is corrupt.
Faulty SD cards could be format issues, ideally you would format the card in the device itsself but you dont have that option unless android will let you do it, which is always an option!
Righty, hopefully that will reset your device SPL radio and all to the original state, if it works and you can get 6.5 working again see how you get it, its a hunch but i reckeon the SPL got buggered up, i cant see any other logical reason for it not to work, think of the SPL as a BIOS on your PC, if you turn USB off in your BIOS you dont have usb working in the OS.
Just to add to the topic here. If you can still transfer data but not charge or receive power via USB does not mean it is not a hardware issue. It just means the pins for data transfer in the USB port are working. A standard USB port has 5 pins in it (this includes micro and mini USB ports) only 2 of the pins are for power transfer the other 3 are for data transfer.
Also if you do not have ActiveSync or WMDC installed on the computer you connect to via USB while in bootloader you will not get the HTC USB sync (USB in white bar of bootloader) connection because these programs have the USB drivers for the HTC USB sync connection, they are not preloaded on the HD2. Therefore the do not auto install when you plug your USB cable in and are in bootloader. I learned this thechard way.
The OP had posted in the HD2 General forum too and I had advised them to try to use a multi meter to test the battery pins while the charger is plugged into the HD2 to comfirm voltage is getting to the battery. I also advised them to try and flash back to a Windows Mobile ROM to see if charging was possible. Both of these things would rule out a hardware issue.
MAGLDR still has this charging bug, it will let you charge while in USB Mass Sty bit it is not charging the battery correctly and this why, quoted straight from the first post inthe MAGLDR thread.
Battery controller inside LEO needs runtime control during charge, it implemented in OS.,
Click to expand...
Click to collapse
The runtime control means that MAGLDR can not control the rate at which the battery is charged which is not good for 2 reasons. One too little (too slow) of a charge rate or too much (too fast) of a charge rate is detramental to your battery life and battery chargeablity. The secound is to much voltage going to the battery can cause the Li-Ion battery in the HD2 to explode. Now reason number 2 is a very unlikely senerio as all common USB type wall chargers only put out 5.0v to 5.1v and that is safe for Li-Ion batteries, but there is still the risk. But as the quote says the "run time control" is implamented by the OS so when you charge with your HD2 booted into the OS it is safe and not harmful to your battery.
I hope the OP gets their charging issue worked out and I hope it is not a hardware issue.
indeed, the power pins as you pointed out could be the issue, im trying not to complicate things at the moment because even if it was, it should still commence coms to the computer, it does connect via magldr so we can assume that firstly the cable is ok on the data lines, secondly the PC is able to detect the device meaning the device itsself is working
We can also assume that if all USB devices have been removed and no ActiveSync or WMDC is installed then Windows would still detect new hardware but will fail to install it, if the drivers were present and it connected we'd have fixed half the problem!
physically it can connect (magldr proven) but something is prohibiting it in bootloader and the OS, the PC isnt detecting it at all. I dont understand why magldr works and bootloader doesnt unless magldr is able to run its own form of bios, i dont know how it works so i couldnt be sure, so im running with a hunch that the HSPL/SPL is buggered as it wont connect to the pc in bootloader.... if we can flash via SD it will help rule that out.
aye the charger thing on magldr is concerning, but it will be ok to give it a short amount of juice to get to windows, overcharging is the issue, could potentially blow up but its unlikely, the plug charger should have a built in IC to knock it down to a trickle charge when it detects its reversing the polarity....should! lol
Thanks everyone, i'm planning on trying this out tonight when I get home and using the SD to bring it back to stock. Hopefully this solves the problem otherwise I'm thinking that T-Macgnolia is correct and one of the Pins in the USB is broken and would need to be fixed.
I really do appreciate all the effort you guys have given in your response.
Mr_Pickles
Mr_Pickles said:
Thanks everyone, i'm planning on trying this out tonight when I get home and using the SD to bring it back to stock. Hopefully this solves the problem otherwise I'm thinking that T-Macgnolia is correct and one of the Pins in the USB is broken and would need to be fixed.
I really do appreciate all the effort you guys have given in your response.
Mr_Pickles
Click to expand...
Click to collapse
its possible that the bootloader or the OS needs the power to be connected in order to function, you did say that you have tried different USB ports and a number of cables, the only other posibility would be that the pin on the phone its self is broken, thats going to be difficult to test.
do the SD thing first, if that doesnt work boot to android, note the battery level, get it to around 50%, then turn off the phone and boot to MAGLDR, you do not need to have it in USB storage mode or anyother mode, just leave it plugged in at the MAGLDR menu.
now the USB port on a PC will provide no more than 500mAh, so if you had 50% charge that would be about 600mAh in the battery, leave the phone plugged in to your PC in MAGLDR menu for an hour, that should give it no more than 1100mAh of juice, (it will actually be less than that as your screen will still be sucking juice)
if you use the 1A wall charger then only charge it for 30min, just to be on the safe side. (if you can i would recomend this one as it rules out any issues with data pins) and if its not working it wont completely drain your battery sitting there with the screen on
anyhow, boot back in to android and see what the battery level is indicating, if its gone up you know its charging, if its gone down you know it isnt, which may indicate a broken phone.
Good luck and keep us posted!
Success! Loading the stock ROM through the SD and finally my computer recognizes the phone! Thank you so much everyone for your help, I can't tell you how much I appreciate it.
Mr_Pickles said:
Success! Loading the stock ROM through the SD and finally my computer recognizes the phone! Thank you so much everyone for your help, I can't tell you how much I appreciate it.
Click to expand...
Click to collapse
no probs mate, thats why XDA dev is here!
i think its almost certain its a SPL issue, possibly got corrupted somehow, least you know its not hardware, i know this sounds a bit much after all you just went through but dont give up on WP7
Hi Guys,
I had exactly the same problem as Mr_Pickles.
I had tried reflashing the stock rom using the SD card method.
Everything installed normally, but after the flashing the HTC logo appears followed by the Radio version and other info shown in the bottom of the screen in red text.
Then the mobile reboots and keeps doing the same thing again and again.
Could someone help me on this please?
nvenon said:
Hi Guys,
I had exactly the same problem as Mr_Pickles.
I had tried reflashing the stock rom using the SD card method.
Everything installed normally, but after the flashing the HTC logo appears followed by the Radio version and other info shown in the bottom of the screen in red text.
Then the mobile reboots and keeps doing the same thing again and again.
Could someone help me on this please?
Click to expand...
Click to collapse
did you install HSPL? before doing anything or is it doing this restart after you reflashed your Stock ROM via the SD card
nvenon said:
Hi Guys,
I had exactly the same problem as Mr_Pickles.
I had tried reflashing the stock rom using the SD card method.
Everything installed normally, but after the flashing the HTC logo appears followed by the Radio version and other info shown in the bottom of the screen in red text.
Then the mobile reboots and keeps doing the same thing again and again.
Could someone help me on this please?
Click to expand...
Click to collapse
Hey Guys,
I experienced the same problem with the installation of wm6.5 stock rom (with having hspl 2.0 installed) as nvenon and couldn't find a solution.
dazza9075 said:
did you install HSPL? before doing anything or is it doing this restart after you reflashed your Stock ROM via the SD card
Click to expand...
Click to collapse
HSPL 2.0 installed, Stock rom installed via sd card method, still the same problem.
The point is that I read somewhere to just keep on flashing wp7, which works fine until operating XBmod-Yuki Rom Build 7004:
- While the wp7 works fine, the phone can't be recognized by any PC via USB, so i can't update the build via update cab sender
- But: The phone is detectable and chargable in bootloader mode, so now hardware issue?
I would appreciate any help.
Thanks in advance!
Hello,
I have had this problem in the past and it stumped me for a bit of time until I looked very carefully at how I was resetting the device. If you are not careful and with flashing etc you will be ripping the battery out all the time.
Look at the device with the battery out and you will see those 3 little pins. They need to be in a line for the battery to make decent contact with it. Over time if you are constantly taking out your battery it will bend them... you can just use your finger to straighten them.
That should do it. It got to a point I always take out my battery carefully now and make sure these pins are aligned before putting it back in.
okay, this is my time to post here.
using h2owner's wp7.8 rom I got a problems with sudden stop charging till once my battery dead completely.
after that I have (quoting my post from h2o thread):
"
it's not to abuse as we know all the risks we take testing roms, just asking for your advice:
1. I did install your latest rom
2. after some time it stopped charging at all
3. the problem is the phone got unable to charge under sd android as well.
4. at the end of story battery got dead - can't load magldr.
5. managed to direct power on it via red/black cables of usb to +/-
6.but the problem still the same - I can't charge battery via phone
7. and even more - can't enable usb via bootloader (tricolor) - serial only:
- usb flasher works only with wp7 rom install;
- magldr, hspl, task29 flash via usb flasher fails with critical error 0000001;
- naturally, can't flash winmo;
- usb storage works well."
1. nbh of the default os flashed fine
2. pins are aligned
3. issue is still here
please, help if you can
dimdimdim said:
okay, this is my time to post here.
using h2owner's wp7.8 rom I got a problems with sudden stop charging till once my battery dead completely.
after that I have (quoting my post from h2o thread):
"
it's not to abuse as we know all the risks we take testing roms, just asking for your advice:
1. I did install your latest rom
2. after some time it stopped charging at all
3. the problem is the phone got unable to charge under sd android as well.
4. at the end of story battery got dead - can't load magldr.
5. managed to direct power on it via red/black cables of usb to +/-
6.but the problem still the same - I can't charge battery via phone
7. and even more - can't enable usb via bootloader (tricolor) - serial only:
- usb flasher works only with wp7 rom install;
- magldr, hspl, task29 flash via usb flasher fails with critical error 0000001;
- naturally, can't flash winmo;
- usb storage works well."
1. nbh of the default os flashed fine
2. pins are aligned
3. issue is still here
please, help if you can
Click to expand...
Click to collapse
okay, now I got "00028002 not allow" error trying flash stock original rom from sd...
still no sd in bootloader, which changed to 1.42...
completely lost.

Categories

Resources