[Q] TMOUS-HD2 Problemo! - HD2 Windows Mobile 6.5 Q&A, Help & Troubleshooting

Ok, so before the general populace of the forum, looks over this post thinking it's some noob who cant read through the forums to solve there own problem, i would like to say thanks in advance to anyone who can seriously provide some help.
Problem is as follows:::
1,)Phone is working fine using mini-winmo+cyan droid
2,) -PROBLEM- My android stops working, so now im stuck using a lite version of winmo
3,) Tried formatting the sdcard with the lite version winmo built in sdcard formatter, doesnt solve anything, dont exactly know what i was trying to solve with this step.
4,) I decide to get a nice fancy version of winmo, figured it would be as easy as just flashing it once n done.
5,)Decided on going with Ozrom, looked the best at the time.
6,) Run the ruucustom as admin, everything goes fine.
7,) -PROBLEM- after flashing the first boot leaves me stuck on the bootscreen.
So after all that i took the advice and tried to get back to the stock Tmous ROM, but as im typing this im still stuck on the Stick together screen, and also just for a control group i downloaded the latest HD2 cell winmo rom release, and that left me hanging on there version of the boot screen.
Same problem, different roms.. stuck on the loading/boot screen.
But, with the stock rom after playing around with removing the battery, simcard,sdcard and what have you i got the stock rom to boot!!!! I was so excited, i skipped the "How to use the on screen keyboard" tut and was typing in my email info when the phone reset on its own and all my hopes went down the drain... hopefully i will get some help on the issue, and like i said previously in the first paragraph i appreciate any and all help.
thanks.

---UPDATE---
Phone is on and working, intermittently.
When i plug the phone into the charger and wait for the amber light, it will boot up and actually enter into windows, now heres the kicker, removing the charger and using the phone will result in the phone turning off and restarting itself, hanging on the stick together screen.
Removing the battery, and replacing the battery after i push all the buttons, the same way you would power cycle a TV remote, and then connecting it to a charger is the only way ive been able to maintain the operation of the device.
Any ideas?

Try doing task29 reinstall winmo Rom of choosing.. see if that helps.. also I flash everything from bootloader. Also check battery pins make sure they aren't bent..
Sent from my Mytouch HD2

Related

[Q] I need help with my fascinate

I have a fascinate and have successfully rooted it, flashed the cricket info (i got talk and text) and had 3g at one point. All of the sudden 3G went out. I put CYANOGEN on there, latest 7.1 i believe for the fascinate.
Upon trying to revert back to the original ROM so I can get in there with PST and CDMA WS, I encountered a very strange set of problems and now I am just stumped. I tried to ask a couple of other people and no one seems to know what is happening.
Here is what happens, I try to put the original ROM on there, by using ODIN and doing the atlasv2.2 pit file, and the original ROM, froyo, and the other one eclair i think.
When I use odin it gets to the system part, then right after it goes to the part that would take the longest, and I forgot what its called, dataFS? it has FS at the end, and then the phone (while odin is still going) will go to either a blue screen or a green screen with no words. If you look closely, it appears there is a clock at the top right just like if the phone was on.
I have not overclocked this device at all so thats one thing that can be ruled out.
I've tried odin using both battery in and battery out method as different guides have stated different things. When the battery is out, I get a blue screen. When its in, i get a green screen.
The screen appears right after the normal odin screen, with the status bar, but it will dissapear when it comes to the dataFS part (right after system) then it will take about 20 - 45 minutes and I will get an error screen on odin.
Funny thing is i've used odin and that method and it worked the last time. It works fine if I need to flash a clockwork recovery. However, upon booting into recovery, half the time I will get an error that has to do with BUILD.prop and SCH-I500. This is when I try to flash any rom except MIUI. For some reason, MIUI kicks this phone around and its the only rom that works. CM7 wont work, stock won't and every other rom wont.
So, to sum it up, my main problem is ODIN and its funky behavior, and not being able to go back to stock so I can see if my 3g settings are correct. If you have any information, even if its just something to help get my wheels turning, then please post it up, any and all help is greatly appreciated folks, thanks.
I dont know if this would work but if u think the problem is Odin then I would uninstall odin and reinstall the newest version available. Also, make sure the phone driver software get done the same.
Then after that I would try odin again. Phone off, battery out. Open odin. Plug in usb. Make sure phone set usb to debug. Hold vol down button. Odin should see your phone.
Im sure u know all the steps up to this point but try again.
Good luck
Or u can try running odin as Admin on the comp.
Also if the problem persits I saw a user had a similar problem and of turned out to be his usb cable so try a different one if you can't fix it.
Sent from my ADR6350 using Tapatalk
See, thats what I thought too, but I will give it a shot and see. I doubt its the drivers, odin or the program, file or anything else because it does work with clockwork, and i've downloaded it several thousand times, plus it works great when I do anything but flash the original rom, odin will go fine. Drivers seem fine, it communicates and all that perfectly so I also highly doubt that.
I will get another cable and just try it on a whole different PC to see what happens. I was really hoping someone had this happen and had a fix but I might have to do some heavy delving. THANKS GUYS! I will try this and report back.
It was the cables, used a brand new USB cable and it worked, strangest thing that a cable can work but not work and its just a bunch of wires, but almost all my audio cables have to be bent or else you will loose a channel. I guess its just poor quality materials. So thank you, it works now and it was just the USB cables.

Help: Totally Dead G Tablet

I received a G Tablet which had been used for development work for a few months. The person giving it to me (not the dev who has left) said the tablet was working fine, but had just become frozen at a reboot after he had tried to erase personal data from the tablet. I asked him if he had erased the sd card and he said "maybe" but that he couldn't remember. I powered the tablet on and sure enough it displayed two lines on a black background, one of which said something like loading kernel.
Now, these tablets were all rooted, and had Android 2.3 on them, via one of the ROMs discussed here. I don't know which one however.
So, I tried using NVflash to flash the tablet back to a stock ROM. Tablet then got stuck in a boot loop; I would see the Viewsonic logo, then the G Tablet logo, and then this would go on forever.
So I shut it down and tried again. This time Nvflash failed almost at the last step after having written most of the image.
And so here I am now, with a totally dead tablet. I cannot power it on. No combination of power or volume up/down buttons work. The only sign of life is when I plug it into its charger, and see the charging light come on.
I confirmed again with the person who gave me the tablet that the device was working just fine before it froze at a reboot after his erasing attempts.
Is there a way out of this? I hope so. Please help!
Thanks very much
Paul
texnote said:
I received a G Tablet which had been used for development work for a few months. The person giving it to me (not the dev who has left) said the tablet was working fine, but had just become frozen at a reboot after he had tried to erase personal data from the tablet. I asked him if he had erased the sd card and he said "maybe" but that he couldn't remember. I powered the tablet on and sure enough it displayed two lines on a black background, one of which said something like loading kernel.
Now, these tablets were all rooted, and had Android 2.3 on them, via one of the ROMs discussed here. I don't know which one however.
So, I tried using NVflash to flash the tablet back to a stock ROM. Tablet then got stuck in a boot loop; I would see the Viewsonic logo, then the G Tablet logo, and then this would go on forever.
So I shut it down and tried again. This time Nvflash failed almost at the last step after having written most of the image.
And so here I am now, with a totally dead tablet. I cannot power it on. No combination of power or volume up/down buttons work. The only sign of life is when I plug it into its charger, and see the charging light come on.
I confirmed again with the person who gave me the tablet that the device was working just fine before it froze at a reboot after his erasing attempts.
Is there a way out of this? I hope so. Please help!
Thanks very much
Paul
Click to expand...
Click to collapse
I would try popping it open and unplugging the internal battery then plugging it back in. Also hit the internal reset button while you're in there. It's pretty hard to actually kill one of these tablets. PM me if you need any other help.
help
Started my own thread, didnt mean to hijack. =)
Thanks, I will try removing the battery and let you know.
As for NVflash, I believe the latest version is here:
http://www.slatedroid.com/topic/171...-using-either-11-or-12-based-images-g-tablet/
However in my case I have no idea whether I have 1.1 or 1.2 and there is no way to determine this. Which one should I choose?
Paul
Doesn't matter for NVFlash, just download all of the flash files again because it might be that you have a bad download. Also make sure you have the right drivers installed since the drivers that automatically install when you plug it in sometimes don't work.
I'm pretty sure that if it boots past the birds, the hardware is working okay, so you should run the FORMAT version for NVFlash and then I'd run just a CWM flash setup and see if you can get into CWM and delete the partitions from within that.
The best thing to flash as far as ROMs would be Bekit's 1105 which is stock OTB with a few key changes. If you can't get the 1105 to play nice, you might really have some hardware problems.
I would go with the 1.2 BL, it will give you access to the newer roms as it appears that dev for the 1.1 BL seems to be dwindeling. I upgraded mine to 1.2 the other day and it worked great.

[Q] Help needed to unbrick HD2 - After restoring WinMo rom

Hi guys,
I successfully flashed Android to my HD2 a few months back. I used what I believe is Cotulla's rom(?). However the other day my phone sorta died and whenever I plugged it into the charger it would vibrate go through the boot screen and reset at the "1234 go go go" stage. I read some reading on the forum and flashed it back to "RUU_Leo_S_HTC_WWE_3.14.405.2_Radio_15.42.50.11U_2.15.50.14_LEO_S_Ship" from the HTC website, using the SD card. Windows mobile restored the phone and I started using it again.
I tried to put android back on it and I think I unsuccessfully tried to update the radio after which the phone sorta died again. So I thought ok, no problem, lets get back to windows again. So I installed the HTC rom again through the SD card, which the screen told me was successful. But now I can't get the phone to boot or go into bootloader or anything. When I plug the charger in, I get a vibrate and HTC bootscreen, with the red writing at the bottom left and then dead to only do this again and again. If i pull out the charger, the phone just dies. Battery charge was about 50% when it died.
Any ideas or help on how to resurrect my beloved HD2 would be greatly appreciated!
*quick update*
I stuck the phone in the fridge for a while and managed to get it into the bootloader just once and flashed the official winmo rom again, which was successful but still dead phone!
What made you decide to stick the phone in the fridge??
What is your SPL version??
mentalityx said:
What made you decide to stick the phone in the fridge??
Click to expand...
Click to collapse
Probably the dozens of threads that talk about successfully flashing only when the phone has been cooled.
@op it doesn't look good. Usually the fridge trick working implies hardware overheating issues.
Just confirm please, its not a tmous right?
Samsamuel is right, i just read about it and thought hey, why not! plus it got a priceless look from the mrs! lol
It's definitely not TMOUS, its UK Virgin and the SPL was 3.03.0000 if I recall correctly.
When I cool it, I can get it into bootloader, but only once.
well, i still suspect its hardware and unfixable, but there have been cases where for whatever reason a rom suddenly seems to fix it. Try all the versions of the correct stock Rom.
Try the 1.43 the 1,66 and again the 3.14, wwe ones, chilling the phone well before each flash, a good 20 mins.

Rooted phone gone bad! Can I just wipe to factory?

Some of you might have seen my earlier thread, my ReZound is rooted. HTC sent out the ICS update my phone attempted to install it and afterwards it would not advance past the white HTC screen. After many hours of playing around with it (being semi-noobish to all things rooting, but decently knowledable with technology) I realized that on the H-boot screen it was telling me that the Image was missing. I assumed that the HTC update deleted it? After thinking about it, I thought that maybe installing a custom ROM would fix this, so I grabbed Scotts Clean ROM. Sure enough I did and I was finally able to advance past the white HTC screen. It looks as if everything is working fine with the phone now EXCEPT I have no data and no calling connection. Im assuming that my phone is just that messed up from the attempted upgrade this morning that im missing files needed for the connection.
My next thought was to just say heck with it and do a factory reset hoping to get back to a bone stock phone that at least functioned, but when I try the factory reset it doesnt work....
Any ideas of what I should do next? Ive spent 5-6 hrs trying to fix this phone today, I really hope to get something figured out. Thank you everyone for your help!
EDIT: I feel like an idiot... Because of putting the battery in and out for resets I left the back off the phone. I now have service. Main issue now is that when I try to call out, as soon as I type a number on the dialer it freezes up and restarts itself....
The phone still tries to look for the old image on the restart and gives me issues every time on startup still also. Id like to be able to get this back to not needing a ROM....
If it were me, I would download the official RUU for ICS found here: http://www.androidpolice.com/2012/0...cream-sandwich-ruu-for-final-ota-3-14-605-12/ IIRC, mirror #3 was the fastest. Then follow the directions from that site:
After downloading the file, rename it to "PH98IMG.zip" (no quotes)
Place the renamed file onto the root of the SD Card
Power down your device
Reboot into the bootloader by holding VOL DOWN + Power
The flashing process should begin automatically
Let the device reboot, and you should be done.
That will get you up and running. Then you can go about rooting it again if you like.

HTC One Won't Boot After Failed Rom

When I bought my HTC One it already had a custom rom installed.
It was some stock android 4.2.1 nexus but with chinese interface and alot of chinese apps and recovery etc were all chinese.
So I couldn't do **** with this and tried to removing it and getting it back to stock HTC one rom.
After alot of tutorials online on xda and many others I couldn't find one that was easy enough for me to make it happen.
It was also my first time with a HTC. Never done it via fastboot/commandprompt etc.
I'd like to add that I am on a MAC aswell It took me a while to find a tutorial via mac but mine simply did not accept those commandlines which worked in the tutorials.
Afterwards I tried flashing it via recovery by installing from SDcard. Which is probably quite the stupid thing to do but I was angry and didn't know any other options since everything failed.
After It started installing stock rom from SD card it was stuck at a screen with "No command" A lying dead android with a red triangle above him and there was one line: Install /sdcard..
I was hoping he would install it but he didn't do anything and got stuck there.
I couldn't restart, couldn't get back to recovery, to anything nothing worked.
I waited untill battery life was drained.
Which happened and after batterylife ended and I put him back on a charger nothing happends.
Phone wont turn on whatsoever.
When I put him on a charger the phone blinks real quick to a white screen and goes back to black screen and still doesnt start whatsoever.
How ****ed am I ?
Can I get rid of this?
Can I still install that stock ROM that I so badly want?
Thanks

Categories

Resources