Hey guys, I tried flashing the Touch It rom and I thought I followed the instructions to the letter but my wing doesnt get passed the 1st boot screen (the white t-mobile screen). I have the original RUU rom but cant run it because active sync doesnt connect to my phone. How do I unbrick my phone or install the original rom w/o my phone being detected by active sync?
EDIT: nm, i restored the original ROM thru bootloader.
Related
Hey folks,
I got the T-Mobile SDA and it's allready running WM5, so I skipped step 1-4 in the how to and wanted to flash the patched ruu from step 5.
But whenever I start the flash tool it starts fine, checks version and then boots into the bootloader mode (the one with the color bars). But after that it wount start flashing. After a while it aborts with a communication error. Also when it switches to the bootloader mode the activesync connection disappear, which I assume is correct, but from my mda2 which I flashed couple of times via the bootloader I remember that when it went into the bootloader some sort of device was discovered from windows. with the sda it's not the case.
Anyone got an idea what is going on here? I thought after I flashed wm5 on the damn thing getting wm6 on there would be a piece of cake...
thanks for your help!
4saken
_4saken_ said:
Hey folks,
I got the T-Mobile SDA and it's allready running WM5, so I skipped step 1-4 in the how to and wanted to flash the patched ruu from step 5.
But whenever I start the flash tool it starts fine, checks version and then boots into the bootloader mode (the one with the color bars). But after that it wount start flashing. After a while it aborts with a communication error. Also when it switches to the bootloader mode the activesync connection disappear, which I assume is correct, but from my mda2 which I flashed couple of times via the bootloader I remember that when it went into the bootloader some sort of device was discovered from windows. with the sda it's not the case.
Anyone got an idea what is going on here? I thought after I flashed wm5 on the damn thing getting wm6 on there would be a piece of cake...
thanks for your help!
4saken
Click to expand...
Click to collapse
by the sound for this you have allready got the bootloader the right one. if it says spl 1.01.0109 on the green part of you bootloader then you can flash wm5 or wm6 these no need to flash the patched ruu
lol, ok. it's flashing now! I didnt think I already had the right version. But you were right. it said 1.01.0109 in the green bar.
let's hope it goes trough without a glitch
I flashed some rom on here a while back. The wife has the wiz and I have the herald. Anyhow, she was having problems so I figured I'd flash the stock 2.26 tmo rom back on her mda. I ran through the update utility and it crashed at about 7x %. Now it is stuck in a bootloader reboot loop...Anyone have any suggestions?? I need to get her phone working again so any help is appreciated. By the way, its a G3 device.
Thanks
Kevin
Just reflash the t-mobile stock ROM again, as simple as that. Most of the time when you have a failed flash you get the bootloader every time you boot. Make sure you don't connect the sync cable until after you're in the bootloader and when you do connect it it says USB at the bottom and you should be good to flash from there.
Last night I flashed my MDA Compact II with a ROM in this forum. The ROM update seemed to go okay, but now the Charmer won't boot. All I get is the splash screen, which says:
IPL 3.08
SPL 3.08.0000
OS 4.0.0.0
I get no charge indicator light when the phone is plugged in (power or USB). Does anyone know how I can fix this or why this is happening?
Hi
I have the same problem too. I just flash back the original t-mobile flash and it's ok again. But whenever i try to flash it again it hangs on the boot screen again. So if you want it to work just use an original T-mobile flash and it will be ok again
Venom
So but it does not discover ROM at original even fix-up me. But computer sees.
It receives messages at each start-up with errors RUU
It can high wines (blames) CID
Try this, to bring charmer back to life.
This metod don't work.
Ok here is a step by step of what happend.
I bought a unlocked HTC Hero originally T-mobile branded.
I followed the instructions on Unlockr to Root the phone.
I then downloaded the 2.3 Modaco rom and flashed it to the phone exactly as described by Unlocker. HOWEVER as suggested (strongly) on the Modaco post in these forums I did not do a nandroid backup of the original HTC(t-mobile) rom on the phone.
When i restarted the phone it simply goes from the power up screen, to the HTC screen, then to the Tmobile branded screen then to a black screen the restarts. During this cycle no buttons work. If i take the battery out and turn the phone on I can get to recovery etc.
How can I either install the rom correctly or bring it back to how it was or in any way make the phone usable again.
I hope you can help. I'm overseas with no money so I can't afford to have wasted this, im about to cry(figuratively not literally haha).
Well I figured it out all by myself!
Need to boot into recovery mode. Plug in via usb.
Follow instructions to get adb working.
Use the cmd interface to push a new update.zip file to the phone
From the phone, in recovery, flash the new update.zip to replace the corrupted one that was causing the repeated restarts.
Hello,
I've got a problem with my Blackstone. I just flashed the latest topix Rom trough SD card and all went well (rom update:succes), and then i did a HR. But ever since then the screen won't turn on. I tried to softreset, hardreset, removing the battery for a few minutes and turn on, and entering bootloader. The screen stayed black. When i plug in the usb charge cable the orange led does go on, and when i press the power button the phone vibrates for half a second and plays the bootsound (as usual). I can even get an activesync connection with my pc.
Suggestions anyone?
Edit: Just flashed a new Rom (the latest energyrom); screen still stays black. I am still able to get an activesync connection + orange/green led
EDIT2: people in this thread seem to be having thesame problem I have with my blackstone. It seems to be a hardware defect... Now let's hope it will be repaired under warranty
Ok, I'm replying instead of editing because I've got a new problem now
I want to return my phone to claim warranty. I did manage to flash a stock rom + radio, but the problem is i use hspl and i am unable to flash a stock spl to the device. When I run the Hardsplwrapper-Blackstone.exe (doesnt matter wether its the unsigned olinex or the 1.56 olinex version) I get a 260: connection error when i use Windows XP, and a 202: connection error when using Windows 7.
The wiki says to run SSPL manually from a file explorer in your phone... But without a working screen that is a bit hard. I als don't have any screen viewing app installed on my device...
EDIT: also tried installing mymobiler to be able to view the screen but I am unable to connect...
Anyone?
I managed to flash stock spl by putting the device in bootloader manually while I had it connected to usb. Then I waited til the bootloader connected to my pc (I could tell because the "new hardware found"screen popped up). then I ran the hspl.exe and copied the stock .nbh spl file. After that I was able to finish the wizard
ok, another question (sorry mods for replying to my own thread _again_ )
I flashed a stock rom + radio and stock SPL (version 1.14). Is this enough to be able to claim warranty, or will HTC find out that i've been using HSPL and custom firmwares? I wouldn't like to have to pay for repairs because they find out about that.