Hello everyone,
so the other day I managed to wet my Trinity a little bit (don't ask how) and it seems to work fine nevertheless, except the programme memory was wiped and the front keys stopped working - which I guess is a software fault because they do work if I keep them both pushed and soft-reset (they bring up the clear storage screen). I thought I'd reflash the ROM but now I suddenly find out I can't! I can boot into the bootloader (by keeping the buttons pressed and soft resetting or by launching SSPL-TRIN) but it's stuck at "Serial" and it won't go into the USB mode - I tried several different USB cables including the original, to no avail. USB works for ActiveSync without any problems. I've also tried putting several different TRINIMG.nbh on my storage card but the bootloader won't budge either. The Trinity is a SuperCID and works well except for the buttons and the bootloader...
I'd be very grateful indeed for any ideas!
Cheers,
k.
koulat said:
Hello everyone,
so the other day I managed to wet my Trinity a little bit (don't ask how) and it seems to work fine nevertheless, except the programme memory was wiped and the front keys stopped working - which I guess is a software fault because they do work if I keep them both pushed and soft-reset (they bring up the clear storage screen). I thought I'd reflash the ROM but now I suddenly find out I can't! I can boot into the bootloader (by keeping the buttons pressed and soft resetting or by launching SSPL-TRIN) but it's stuck at "Serial" and it won't go into the USB mode - I tried several different USB cables including the original, to no avail. USB works for ActiveSync without any problems. I've also tried putting several different TRINIMG.nbh on my storage card but the bootloader won't budge either. The Trinity is a SuperCID and works well except for the buttons and the bootloader...
I'd be very grateful indeed for any ideas!
Cheers,
k.
Click to expand...
Click to collapse
Yo !! first excuse my english !! lol !!
You must go to : "start - settings - connexions - USB to PC" and uncheck the option "activate advanced network" (or something like that, my p3600 is in french language). Theoretically in the bootloader the "serial" will turn to "USB" when you'll plug your cable and so you'll be able to reflash your ROM.
Peace !!
Tried that but the bootloader stays at "Serial" whatever I plug into the phone... Hm!
I'm more hopeful about the SD update method--what can I be doing wrong? I noticed that when there is a TRINIMG.nbh file on my card, the bootloader very briefly flashes a grey screen with blue letters saying "Loading" (I guess) but then returns to its normal three-coloured state. Any ideas on what that means?
Thanks everyone!
i had the same problem, take another cable and then it works, i have to many usb-cable, but with one it function, hope i could help...
greets bambi42
I've tried several cables including the original one which had worked before... no luck!
I removed a program yesterday and somehow my OS became corrupt. I could not get into the OS and was stuck at the splash screen. I went to reflash WM6 but when I plugged in activesync, nothing happened. The AS icon wasn't turning green and I was flipping out. I still kept it plugged and flashed my phone and it worked anyway. I thought that was strange.
See Usb pins contact of the pda , may one of them is on another
i had this probleme , and now it works !!!!
Related
I tried to flash my Qtek 9100 to WM6 using the flashing tutorial on this site.
I followed the steps in the tutorial. I downgraded to Buttons ROM, unlocked the CID, and then I flashed the 3.08 IPL/SPL in stead of the T-Mobile 2.26.
Then I tried to use farias kitchen to make a WM6 and flashed it to the phone.
Everything seemed to go smoothly, but when I tried to start the phone after flashing the 3.08 and farias' to the phone, the phone just hangs at the startup screen with the picture of the beer glass and the coloseum.
I've tried to downgrade to Buttons firmware and I've also tried the Xda_MiniS_LaunchROM, but it doesn't help. I'm still stuck at the welcome screen.
Is there anything I can do, or have I bricked my phone for good?
flash an original qtek rom to your phone then try to flash the rom again
Your phone isnt bricked (yet)
I've done that, but it doesn't help. Still just hangs at the SPL/IPL screen.
Solution (worked for me)
I found a solution while looking trough the forum
I was facing the same problem on a G3 phone
this is copied from that link except the link to MTTY.exe is different (previous one doesn't work
See (http://forum.xda-developers.com/showthread.php?t=307332)
1- I tought that a SD backup was needed, and yes it is. But u can use your own phone and your own SD to do it.
2- Get a clean SD card (in qtek 9100 / Htc Wizard case is MiniSD) with 128MB (some people say 64MB, but I personally used a 128MB, maybe a 64MB is enough)
3- Kill (task manager) wescomm.exe (this is related with activesync installed on your PC). Insert the blank SD card on the phone.
4- Get your phone in bootloader mode. Like this : Phone powered off, press Camera button + Power On, will enter in bootloader mode (RGB screen).
5- Now connect your USB cable to your phone. And start MTTY.exe ( http://forum.xda-developers.com/showthread.php?t=231190 ). After open, on Port selection, choose USB and press OK. A window will open with a blank sheet.
6- Type "r2sd all" and hit enter... wait to the end (at end shows "cmd>"). On your phone screen u can follow backup progress... small bar will appear down the RGB screen.
7- Power off the phone (or remove battery), enter bootloader mode (camera button + power on) and this time RGB won´t appear right away. Will ask if u want to "download SD image", press voice dial button to agree, and writting will begin. Wait to the end. Power off and power on normally. Now your phone should be working ok. Not even needed to reflash the phone after this.
I hope this helps you out
It worked for me (and other people if you look at the forums)
That solution was already known and was, in fact, discovered for the Wizard by a guy called 'Drugstore'
But what really matters is that this procedure only works if the device is already CID unlocked.
cheers
MDA Vario freezes at 2nd boot screen
I have the same problem. I flashed wm6.1 according to tutorial on this side. everything worked fine, until the time I uninstalled some application. after that my Vario froze. after soft reset it stopped on second screen (the one with info), and so it is anytime I try to reflash to other ROM. everything works fine until the time it shoud reboot.
I found this thread and tried the thing with backup image. everything worked, copying image to the phone ended with success. so I turned off the phone and started it again. but now, after all, I'm just back at the beginning
can somebody help me out with another solution??? pls.....
Try mtty
grinmustaine said:
I have the same problem. I flashed wm6.1 according to tutorial on this side. everything worked fine, until the time I uninstalled some application. after that my Vario froze. after soft reset it stopped on second screen (the one with info), and so it is anytime I try to reflash to other ROM. everything works fine until the time it shoud reboot.
I found this thread and tried the thing with backup image. everything worked, copying image to the phone ended with success. so I turned off the phone and started it again. but now, after all, I'm just back at the beginning
can somebody help me out with another solution??? pls.....
Click to expand...
Click to collapse
maybe trying mtty
task 28
task 28 55aa
then upgrade again
this is not the steps as is... so search the way
+ Que PPC said:
maybe trying mtty
task 28
task 28 55aa
then upgrade again
this is not the steps as is... so search the way
Click to expand...
Click to collapse
I didn't have chance to try this.... My Vario is already dead... Probably is my fault... As far, I wasn't able to flash to official T-mobile ROM, I did a backup copy to a SD card on my friends phone, and then tried to copy the image into mine... I'm afraid I destoyed bootloader this way After I turned off my phone first time after flashing, it didn't start again.... It doesn't react even to wall charger... Nothing... Just dead Vario
Get a powerfull charger
grinmustaine said:
I didn't have chance to try this.... My Vario is already dead... Probably is my fault... As far, I wasn't able to flash to official T-mobile ROM, I did a backup copy to a SD card on my friends phone, and then tried to copy the image into mine... I'm afraid I destoyed bootloader this way After I turned off my phone first time after flashing, it didn't start again.... It doesn't react even to wall charger... Nothing... Just dead Vario
Click to expand...
Click to collapse
There is a post that suggest that somebody revives his batt with a wall charger, maybe is your batt... is dead... or your s is bricked.
So after an unsuccessful ROM flash my phone was stuck at bootloader for quite sometime...i had a micro SD card reader and inserted it into multiple computers running XP, vista and ubuntu...they all registered that i had plugged something in but wouldn't show it as a disk drive...now i've already figured out how to access it but i put a new ROM image on it and tried to reflash but after the flash when my phone booted up it simply switched itself off... when i switched it back on it went back to the bootloader and tried to reflash the ROM. mid flash it just switches itself off... I realize that this is probably due to the charge level of the phone so i plugged it it but it will be off and charging then it will suddenly decide its got enough battery power and boot up to the bootloader screen until it dies again...how do i stop this vicious loop
tlglegacy said:
So after an unsuccessful ROM flash my phone was stuck at bootloader for quite sometime...i had a micro SD card reader and inserted it into multiple computers running XP, vista and ubuntu...they all registered that i had plugged something in but wouldn't show it as a disk drive...now i've already figured out how to access it but i put a new ROM image on it and tried to reflash but after the flash when my phone booted up it simply switched itself off... when i switched it back on it went back to the bootloader and tried to reflash the ROM. mid flash it just switches itself off... I realize that this is probably due to the charge level of the phone so i plugged it it but it will be off and charging then it will suddenly decide its got enough battery power and boot up to the bootloader screen until it dies again...how do i stop this vicious loop
Click to expand...
Click to collapse
can you put your phone into bootloader mode (power and vol down together whilst powering on)? be a good idea to remove your sd card first.
cr1960 said:
can you put your phone into bootloader mode (power and vol down together whilst powering on)? be a good idea to remove your sd card first.
Click to expand...
Click to collapse
I can't really manually put it into bootloader mode, but when the phone thinks its charged enough it will start up itself and go into bootloader mode
Does your phone say "RUUNBH" in the top right corner? Have you yanked out your battery then put it back in before charging? Those are the two things I would try. And BTW, in the future you shouldn't create two threads in different parts of the forum.
DaveTheTytnIIGuy said:
Does your phone say "RUUNBH" in the top right corner? Have you yanked out your battery then put it back in before charging? Those are the two things I would try. And BTW, in the future you shouldn't create two threads in different parts of the forum.
Click to expand...
Click to collapse
yea im sorry its just my phones been down for days and its really bugging me and i just want to get this fixed and my phone does say RUUNBH in the top right corner and i have yanked out the battery waited a few seconds for good measure and put it back in before charging...it still just loops into bootloader before dieing and charging again
Phone started up again this is what it says in bootloader
RHOD300 32 M SS-BC RUUNBH in top right
SPL-0.85.Olinex
MicroP(LED) 0x0A
MircroP(KEY) 0x04
TURBO HW/TURBO SW
TP MFG DATA
then it has some numbers and code error under it with try again
then it says 218,842 calibrated
Okay, the problem is that the RUU flag is set, and the device won't do anything until that is cleared. What you need to do is establish a connection via MTTY. Follow the instructions here about how to connect to your device via MTTY. Once you get an MTTY connection established with your device (it may take awhile, MTTY is quirky like that), simply type
Code:
set 16 0
You may need to manually soft reset the device. Then, I highly recommend flashing to a stock ROM using the microSD card method, before flashing another cooked ROM.
DaveTheTytnIIGuy said:
Okay, the problem is that the RUU flag is set, and the device won't do anything until that is cleared. What you need to do is establish a connection via MTTY. Follow the instructions here about how to connect to your device via MTTY. Once you get an MTTY connection established with your device (it may take awhile, MTTY is quirky like that), simply type
Code:
set 16 0
You may need to manually soft reset the device. Then, I highly recommend flashing to a stock ROM using the microSD card method, before flashing another cooked ROM.
Click to expand...
Click to collapse
hey thanks Dave i plugged in the usb then i waited until my phone was charged enough to switch on and go to bootloader then i opened MTTY the USB port showed up i selected it and it connected no problem i typed in set 16 0 then the device reset and showed the touch pro 2 boot screen then my phone died and started charging...i left it charging overnight and this morning it booted up and started loading the ROM...after it was finished i hard reset it just to be sure and now it's working perfectly thanks very much i appreciate the help
Duplicate thread??
Dude!! you already opened this same thread here, and HERE. Why another??
Closing thread.
Don't do this again.
Hello everyone,
I am having problems to connect my Tilt to my pc.
First of all, when I power it on, the screen goes black and says "smart mobility" .. so far so good; but after a few seconds it starts again and loops endlessly. At that point the only way to power it down it to take the battery off.
I installed the drivers manually (Vista) and hoped to be able to use mmty (after pressing "camera button" and " power button") but I never managed to get a connection.
Does anyone have any ideas on how to get my HTC tilt back to a running state?
Sooo, this only happens when connected to the PC or all the time?
It happens all the time even when not connected to PC
I forgot the most important part ... this happend since I tried to update windows mobile (source downloaded from HTC official site).
Hard reset?
if you mean holding down both green and red headset button+pressing the reset button, yes I've tried that but didn't change anything.
It went through a whole process and nothing changed? Try to flash back to an oem rom. (seems to be the new popular suggestion).
ok but how can you do that if you can't get to connect it to a PC via usb?
By following the proper steps to flash a phone either by usb or SD card.
The phone doesn't need to be fully booted to flash.
Ok, that's good news for thanks.
If by any chance you have a link to a tuto in order to do that you're welcome. Otherwise I'll google it and get back to you to keep you posted.
It's all in the sticky
http://forum.xda-developers.com/showthread.php?t=397434
Thanks I shall try to night
Thank you for your time. I finally managed to do it and my HTC is back to running.
The only problem I had trouble to solve (if it can be of any help to anyone) is that I had to unrar the *.exe which I didn't could be done.
Thanks again
hello all!
my phone was working properly (rooted but not boot unlocked)
pc companion told me there were a new version availlable (.253) I accepted, install, reboot, everything was fine.
I tried to backup my data in order to change the sd card to a bigger one...then it told me there was a problem while backuping so I did a reboot
this is where the problem begins:
now I have a white triangle with a screwdriver in it and a blue bar below it with an animation inside and it's stuck there...what does it mean for a start?
can you please help?
I'd like to recover it in order to get back my data (photos and video I wanted to put on the new sd card)
tried flashtool but it doesn't recognise the phone...
note: before doing all that, free space was low on my XZ internal storage (like 300 megs)
dave_id said:
hello all!
my phone was working properly (rooted but not boot unlocked)
pc companion told me there were a new version availlable (.253) I accepted, install, reboot, everything was fine.
I tried to backup my data in order to change the sd card to a bigger one...then it told me there was a problem while backuping so I did a reboot
this is where the problem begins:
now I have a white triangle with a screwdriver in it and a blue bar below it with an animation inside and it's stuck there...what does it mean for a start?
can you please help?
I'd like to recover it in order to get back my data (photos and video I wanted to put on the new sd card)
tried flashtool but it doesn't recognise the phone...
note: before doing all that, free space was low on my XZ internal storage (like 300 megs)
Click to expand...
Click to collapse
Unplug your phone from the USB cable and then start, see if that helps
This is exactly what I've encountered, can't find much help in the web, re-flash with wipe cache no joy, in the end re-flash with wipe data boot normally, last backup was 4 days old, restore and lost 4 days game progress...
Sent from my C6603 using XDA Premium HD app
That's strange.
Also had the same.
I updated to the .253 ROM and firmware etc and everything working fine.
I then rebooted after removing some system apps and got this.
I left it for a while and still stuck there.
Pressed a few buttons and still nothing then it suddenly rebooted (not sure if related to pressing the buttons or not) and everything was fine.
Then when it booted up it did the NFC firmware update so maybe related to that.
Not had it since and rebooted a few times.
Phil
thanks for replying guys.
problem really is that I can't use flashtool, for some reason I can't go in flashboot mode (green led right?)
and in fact I don't know all the key pressing procedures (if someone can post them all)
...but I think I got the press down and connect right, problem is that I have the green led for less than one second and then nothing...
dave_id said:
thanks for replying guys.
problem really is that I can't use flashtool, for some reason I can't go in flashboot mode (green led right?)
and in fact I don't know all the key pressing procedures (if someone can post them all)
...but I think I got the press down and connect right, problem is that I have the green led for less than one second and then nothing...
Click to expand...
Click to collapse
Hi,
I also encountered this when I tried to use the old root method of .253. (yah, stupid of me but managed to salvage)
Just let it run for like 20 minutes or so and it will reboot subsequently. (As long as the progress bar still move, you should be ok)
Seems like a self-recovery process in place I guess.
yeah I guess you're right , but the first time was so long (more than 20 minutes ) so I thought it was dead...it is obviously some kind of self repair,
because now after a lot of reboots it suddenly started correctly after 5minutes of this blue bar moving....and now working? WTF?
things that I did in case it could help:
-used flashtool beta 4
-flashed a base .434 in blind mode (choosed xperia Z in the list)
-went into flashboot (press down and then plug usb) I had the green light for just a second...(I also installed EMMA drivers from sony , don't know if it helped)
-reboot then wait (I put it also on the docking bay , don't know if it helped as well but it made the blue bar go faster it seems, not sure tho...)
I used "hard boot" also : just jkeep pressing up and the power button until it vibrates 3 times.
maybe just puting it on the dock and then wait (quite some time) is enough (and makes sense)
I just had the same issue - WTF!!!
I just let it sit there for a while and it automatically started.
This is f*** crazy smart (stupid) phone.
DOn't know exactly what my wife did, but I doubt she flashed anything:laugh:
The battery died, she conncted to the charger, most probably with pushing some of the volume buttons and phone booted into Triange mode. Now it's stuk in this mode since an our.
I did Hard reset, but after phone is plug into wall charger it automatically boots in Triange mode.
This is in stock ROM without any modifications, unlocking, anything.
esselite said:
This is f*** crazy smart (stupid) phone.
DOn't know exactly what my wife did, but I doubt she flashed anything:laugh:
The battery died, she conncted to the charger, most probably with pushing some of the volume buttons and phone booted into Triange mode. Now it's stuk in this mode since an our.
I did Hard reset, but after phone is plug into wall charger it automatically boots in Triange mode.
This is in stock ROM without any modifications, unlocking, anything.
Click to expand...
Click to collapse
Just wait - sometimes it takes a while but it'll eventually boot up.
I think [NUT] said somewhere that this is a repair of certain permissions by the phone itself. I've only ever had this for some minutes - but it is possible if the battery an out it could invoke this. Shouldn't be anything to worry about.
And I think fastboot is blue led - you could try flashmode.
I tend to do lots and lots of flashing and mods so I've seen it several times. The first time caught me by surprise and lasted for a long time...now I'm just used to it ..
In my case waiting in triangle mode did not helped. Was waiting 5 hours at work. I flashed with flashtool again stock ROM without wiping data and still no response.
FInally flashed with wipe and phone is running but all data gone. What a crap.
Good afternoon staff,
Just enter the site, so if you're posting wrong, a thousand apologies.
But I need your help ...
My Milestone're not giving image is Turnin on and then realize that he's bound for tightening the volume button and it makes the sound that is increasing the volume. The android 2.2 it was. It was working before, the glass touch had given problem and I went to change it, but I ended up breaking the flex cable, that great, then I had to order a new one. I made the change correctly, but then it stopped displaying image when I tried to turn on. I tried to reconnect all over again, one time I showed the logo of motorola and then disappeared and has not appeared since.
I tried using RSD Lite v5.3.1 (installed drivers Motorola_end_user_drivers_5.1), downloaded a SBF (SHLA_U2_01.03.0_USASHLSVIVBRLA01C.0R_USASHLSVIVBRLAT_P031_A012_HWp2a_1FF.sbf) and tried flashing, plugged the milestone on (no picture but on), after that the pc installed the necessary drivers and RSD there recognized the phone, but he says: Changing to flash mode ... only after he gives this status: failed flashing process. unable to retrieve interface handle. (0x7027). Phone disconected.
Then he fails in flashing.
I wanted to help you because I am without a cell time, so ...
Thank you in advance
Other Comments:
- My Power button does not work anymore = \
- I removed the Micro Sd who came and formatted and I'm using for something else, so all I did was without the Micro SD.
Please Me help!
thx
GOOGLE TRADUCTOR DID IT! =)
I'm not sure if I can understand you. The only thing came in my mind is installing OpenRecovery on your sdcard and try flashing a custom rom.