I flashed my phone a couple of weeks ago with Schaps 4.31 Rom. It has been working a treat ! This is the first time I flashed a phone and I followed MR.Vanx instructions.
All was working fine untill yesterday. I had my 3rd freeze of the day. Oh well I thought, thats 3 in 2 weeks never mind must just be having a bad day.
It got worse. I soft reset my phone and now all I get is the Olipro bootloader 3 colour screen ! So I took the battery out and left it for 2 hrs. Still the same.
Whats wrong with it ?
Does this happen like that ?
Can I recover or do I need to flash again or is this permanent ?
HELP HELP HELP
Anyone know ? Phoen still not working. Can someone help ?
http://wiki.xda-developers.com/index.php?pagename=Hermes_Unbrick
dan1967 said:
http://wiki.xda-developers.com/index.php?pagename=Hermes_Unbrick
Click to expand...
Click to collapse
<Sarcasm mode> Thanks. Like I never thought to look there. </Sarcasm mode>
I was more interested in the other questions I asked ... IE is this normal after 2 weeks operation ? etc
no, shouldnt happen like that. try putting the .nbh file on a sd card after formatting fat 32. rename to hermimg.nbh then put in phone. if you're in bootloader it should automatically start the flash. this should get you out of bootloader and back into windows. make sur ebattery is more than 50% by putting on to charge for awhile first. hope this helps. Cheers.
Thanks for the response.
I think I can do it via USB as usual I am just waiting for the phone to charge a bit first. Obviously with no OS I have no idea how much battery % it has !! DOH !
Oh well I will post back for those interested once I know if it is goign to work or not !
Previously been stuck on bootloader before, and I just flashed a different ROM via USB. This worked fine for me. Would also try what ultramag69 said previously
Suggested sd as this has become my favourite way of flashing. No chance of NASTY accidents like computer resets, someone unplugging usb or other little things t5hat seem to happen to people as they flash there precious hermes. Sorry if this sounds like a hard sell but I really believe this is the safest way to flash your device. I've even flashed below 50%... Plugged in power. Was in a rush and had no time. Its never failed while I have had bricks and glitches with the usb. And thats my two cents......
Well it just gets stranger, I waited untill the phone was fully charged. It was plugged in to PC via usb swtiched off so I could see the charge light go green. When I switched the phone on with USB connected to go to bootloader screen to reflash, it booted windows !
Its now working fine ! I did nothing except charge it.
How very dare it !
Suggest you check the device for bad blocks.
Put the device into bootloader, start mtty.exe
connect to USB and run the command "Info 8".....this will report if the device has bad blocks (three should turn up even on a normal device).
then run "task 2a" to fix any bad blocks that are evident.
It might be worth flashing a new ROM to it to overwrite any corrupted sectors, just as a precautionary measure?
Have you tried hard resetting the device by holding the 2 left and right buttons (below the screen) and then reseting with the stylus?
This will then ask if you want to reset to factory..or if you have a cooked ROM reset back to the cooked ROM?
Helped me out and then promptly re-ROM'd the thing...
Hope this helps.....
ultramag69 said:
no, shouldnt happen like that. try putting the .nbh file on a sd card after formatting fat 32. rename to hermimg.nbh then put in phone. if you're in bootloader it should automatically start the flash. this should get you out of bootloader and back into windows. make sur ebattery is more than 50% by putting on to charge for awhile first. hope this helps. Cheers.
Click to expand...
Click to collapse
Ok had a problem today JASJAM seemed to loose phone reception has done this before , since I had the offical Telstra ROM on there for some time thought I would re-install , however stopped at 12% then was stuck on bootloader, tried the SD card method above get through the IPL , BOOTLOADER SPLASH 1&2 and EXTROM but seems to stay on GSM in the list any ideas as to what the problem maybe?
You need to loas SPL 1.01 MFG, then connect using MTTY.EXE.
after issueing:
USB>task 32 (you will get)
Level = 0 (now issue)
USB>set 14 0
USB>task 8
p.s. if you have other than SPL 1.01 MFG, you may need to use set 16 0 or other value. Do search.
Now the device should boot, if it does not:
Press the soft keys (the ones below CONTACTS and CALENDAR) together with the RESET. The device should go through installing windows procedure.
Good luck.
Simple.
Related
First, I would like to thank everyone on this forum for valuable information. I have been able to flash a Blue Angel and more recently a Universal (SPV M5000) with a Jasjar, O2 and Qtek ROM.
I have researched the forum but have not found any answer close to my problem.
After the lastest update (O2 Exec just released), I did not reset the unit properly and now my screen is completely dead/blank. I tried to reflash but it is no longer recognized (will not power back up)
No possibility in putting in Boot loader mode (power+light+reset) or doing a hard reset (the 2 _ and reset).
has anyone experienced this and can I revive it, at least, bring it back to a boot loader so I can reflash? Thank you to all :roll:
Just a thought. Have you tried leaving out the battery pack for a while, say an hour or better overnight? Might be worth trying the hard-reset sequence with the battery still out, then insert the battery and hard-reset again. If it responds, try flashing again.
It is possible to get the Universal in a totally confused state. Mine does this everytime if I power down the workstation *without* first disconnecting the Exec from the USB-Sync cable. Fortunately, it will respond after a battery out plus reset, then battery in plus soft-reset, so I don't actually have to clear the memory.
Hope you dig yourself out of the brown stuff!
i am trying this at the moment as I do not know what else to do. I will put the battery back tomorrow in hope it will restart again.
Thank you for the advice
i am trying this at the moment as I do not know what else to do. I will put the battery back tomorrow in hope it will restart again.
Thank you for the advice
claudef said:
i am trying this at the moment as I do not know what else to do. I will put the battery back tomorrow in hope it will restart again.
Thank you for the advice
Click to expand...
Click to collapse
No to do that , connect ypur ppc to pc amd flush again after finish just push reset buttom , you will be ok, otherwide try one more time
Unfortunately, I cannot flash because it will not power up or start the boot loader. The pc does not recognize the device
claudef said:
i am trying this at the moment as I do not know what else to do. I will put the battery back tomorrow in hope it will restart again.
Click to expand...
Click to collapse
That worked for my when I was flashing my JAM, no problems. Scary, but successful. Think I may have left it a couple of days, to be sure. I then reflashed it successfully.
Although I refused to flash my Exec - too damned expensive to replace, and the ROM is 95% as good as it needs to be.
My DOPD - bought in China was running a chinese version of WM5.0 and I wanted to install a english version.
After upgrading my DOPOD 900 with the upgrade : Universal_Upgrade_v1.30.68_radio_1.09.0.zip I have problem.
It is really DEAD. soft reset does nothing and a hard reset only gives the option of "0" and "X" which do nothing.
the USB is no longer recognised and nothing seems to want to communicate with the Dopod. It seems the USB loader program is no longer running on the Dopod.
Has anybody any idea how I can attach to the device an install a new bootloader, or something.
I had the same issue and I have a solution. But, let me tell you my process that got me where you are.
I tried performing the update using the No_ID (or whatever) method and kept getting errors. I rebooted my PC and changed the Operator ID using the HTC64 Extended ROM Tool.
After this, I was able to use the typical installer. The flash went fine and I hard reset as instructed. From that point on, I had your exact problem.
A dead screen. I was able to redo the hard reset after pulling the battery but I would just end up with the dead (blank) screen again. ONCE, I did get it into boot loader mode where I could actually read the screen. But, of course I reset and again had a dead screen.
My solution was to revert back to a true O2 ROM. Even though I couldn't see the screen (still can't), the ROM update is proceeding as I type this. I'm at 44% of the radio ROM installed.
Hope this gives you hope!
Well, good news. I just finished the ROM update and I'm looking at the O2 boot image.
Is there any indication that the QTek ROM looks for the Carrier info to be QTek or it will fail once installed? Just wondering why I had this problem.
ARG! Reflashing with QTek ROM did the same thing. :evil:
Blank screen and all.
check 2 things
uncheck usb from active sync
hardreset after upgrade has been completed
just do the upgrade again and it should come alive again
Thanks and another question
Well thanks for the hope. but I have tried this already with no luck, however after this message I will try again. My biggest problem is that I cant regain communication over the usb.
I would like to know how your system behaved when you plugged in your apparantely dead device. My system just says device un recognised and I cant begin a download with or without active sync.
So I cant get another rom image to download.
regards
Nick
dolebole said:
check 2 things
uncheck usb from active sync
hardreset after upgrade has been completed
just do the upgrade again and it should come alive again
Click to expand...
Click to collapse
This was the first thing I did.
The problem is that I cannot get any communication over the USB.
The device is unrecognised on USB and after starting any ROM download it just timesout after "checking information from device" message .
Ever seen a dead USB interface like this ?
The USB PnP mgr sees the hardware but cannot establish the device type !!
Nick
@mobinick: You and I have the same situation.
I have 2 Universal dead like this. 1 Exec and 1 Jasjar.
Both dead, blank screen, can not enter bootloader, can not connect with PC. PC can not recognize the driver usb of the device.
I opened the phone and found that logically everything is so so. There is no clue about hardware.
So I think: the address of the bootloader with device ID maybe unlucky damaged.
Who can fix this problem pls share us some experience.
Thanksss
ta_mobile said:
@mobinick: You and I have the same situation.
I have 2 Universal dead like this. 1 Exec and 1 Jasjar.
Both dead, blank screen, can not enter bootloader, can not connect with PC. PC can not recognize the driver usb of the device.
I opened the phone and found that logically everything is so so. There is no clue about hardware.
So I think: the address of the bootloader with device ID maybe unlucky damaged.
Who can fix this problem pls share us some experience.
Thanksss
Click to expand...
Click to collapse
Why don't you guys take it to your respective service centres and get it fixed?
Even if you have to pay something, it will certainly be better than these bricks occupying table space.
Have you tried going back to an original O2 ROM? I went to 1.13.139 WWE and all is fine now.
Just to share my experience with you guys here:
I posted my problem way back during the Radio Upgrade from 1.04 to 1.06. My Dopod 900 got stuck on the splashscreen. I couldn't get my device to pass the splashscreen even after upgrading/downgrading the radio ROM back and forth two times.
Finally, I just forced my device into bootloader mode (Backlight+Reset+Power). Even after doing this, the dopod screen was completely blank (no indication of serial/usb letter on the screen). I downloaded the official O2 exec ROM and plug my device (in bootloader mode) back to the USB port. It said unrecognized port on my PC. Despite that, I reflashed my Dopod back with the NoID tool the complete O2 ROM (Radio, Main ROM & The extended). Once completed, my device regained its consciousness.
I managed to flashed back the 1.06 radio after that. And has since been upgraded 4 times (two i-mate, one Orange and the latest QTek ROM) with no problem whatsoever.
I had the exact same problem as you to guys, i tried to update it, and it wouldn't budge...
It constantly, without fail timed out... I tried everything...
As my hope started to wain, i gave it one last shot...
I took out everything, sim and sd and battery, then connect the battery back and from the bootloader menu, connected it to the pc, with usb cable...
Finally it worked!! Like normal, i was able to load any and all rom and radio updates...
Wouldn't work, from the normal working screen (which was working for a while, i later tested this out, and found out ) and also wouldn't work, from the bootloader (power+backlight+reset) with sim+flash in there....
Hope you guys have some luck.. I htink you should, because i was in the exact same boots as you guys...
It worked for me
My O2 Exec did exactly the same thing, and I spent (on and off) 24 hours trying to get the damn thing to go again - wouldnt charge either....
I too finally took out everything, SIM and sd and battery, then connect the battery back and from the bootloader menu (which I only found about from this site), connected it to the pc, with usb cable...
It worked as well - bloody brilliant. I now have the latest 02Exec Upgrade (Version 1.30.162 AKU2 Release) and all is great.
Cant believe that 2 days after logging email with O2 site, they have not responded...
Would almost kiss you guys.....
Solution for getting stuck in bootloader
http://wiki.xda-developers.com/index.php?pagename=Instructions for those stuck on Boot Screen
Everything was fine, I was just browsing for wireless connections and then I've done a softreset and to my surprise it went into bootloader mode, and now whatever I do (softreset, remove battery, hard reset) it goes immediately in the bootloader mode and I can't boot windows.
I am running SPL 2.10 Olipro IPL 1.04.
Not sure if this is relevant at all, but I am running Schap's 4.31.
Any ideas?
Thanks
read the wiki
since youre hard spl you can flash the rom again. jsut run the ruu and select 2.10 and select hard spl, dont auto-detect,go through the steps and it will flash
Hmmm try reinstalling 4.31 or any other ROM again to see if it works!
Tried that already. I have tried the same ROM again (schaps 4.31), and tried the t mobile official ROM (WM6). they didn't change anything, it flashed the rom to the end and then after the reboot it goes back to the bootloader and can't get off it. I have tried the phone's original ROM which was WM5 but I couldn't do that (doesn't flash it, it says the phone is not available, maybe because it's in bootloader and it doesn't connect to activesync).
The strange thing is that overnight I left the phone off and this morning it did boot into windows (this was on the official t mobile WM6 rom) and went as far as running the custom network settings, but then after the restart it went back to bootloader and now it's back, can't get out of it.
Any ideas?
oooo
im having the very same prob
official wm6 from t-mob (UK) upgrade from WM5 that came with the hermes.
now i cnt get outta boot load.
check out my fight to bash the brick back in to its senses...
http://forum.xda-developers.com/showthread.php?t=361323
If anyone can help give my phone CPR - please do.
serializable said:
Tried that already. I have tried the same ROM again (schaps 4.31), and tried the t mobile official ROM (WM6). they didn't change anything, it flashed the rom to the end and then after the reboot it goes back to the bootloader and can't get off it. I have tried the phone's original ROM which was WM5 but I couldn't do that (doesn't flash it, it says the phone is not available, maybe because it's in bootloader and it doesn't connect to activesync).
The strange thing is that overnight I left the phone off and this morning it did boot into windows (this was on the official t mobile WM6 rom) and went as far as running the custom network settings, but then after the restart it went back to bootloader and now it's back, can't get out of it.
Any ideas?
Click to expand...
Click to collapse
Run mtty and try to see if there is bad NAND blocks on the device, to do that run 'info 8' which will report if bad blocks exist. If they do (there should be 3 bad blocks on a normal device, ignore them) then run 'task 2a' which should sort out bad blocks, then flash a new ROM.
EDIT:: Always look at the Hermes Unbricking Thread aswell.
Ok, thanks mr vanx. I'll try that.
Here's a quick update: it would appear that after it is off for a while (about 30 mins, without the battery) it boots into windows, but then after any restart it goes back stuck in the bootloader. Does this mean anything to anybody?
Brilliant
mrvanx said:
Run mtty and try to see if there is bad NAND blocks on the device, to do that run 'info 8' which will report if bad blocks exist. If they do (there should be 3 bad blocks on a normal device, ignore them) then run 'task 2a' which should sort out bad blocks, then flash a new ROM.
Click to expand...
Click to collapse
Thank you ! That fixed it.
Brilliant!
Out of curiosity, what does set 14 0 do? (as stated here: http://wiki.xda-developers.com/index.php?pagename=Hermes_UpgradeProblems#problem4)
serializable said:
Thank you ! That fixed it.
Brilliant!
Out of curiosity, what does set 14 0 do? (as stated here: http://wiki.xda-developers.com/index.php?pagename=Hermes_UpgradeProblems#problem4)
Click to expand...
Click to collapse
Sweet stuff, glad that worked
set 14 0 i presume is a standard bad NAND command or something, thankfully in HardSPL olipro enabled checking and fixing of bad blocks.
Have fun with your Hermes again
Thank you
mrvanx said:
Sweet stuff, glad that worked
set 14 0 i presume is a standard bad NAND command or something, thankfully in HardSPL olipro enabled checking and fixing of bad blocks.
Have fun with your Hermes again
Click to expand...
Click to collapse
Cheers mate, I sure will !
This was like reading a good book with a very happy ending.
I feel all warm and fuzzy inside.
stuck in HTC splash screen ..Help!
HI guys ,
I have been following the forum from a long time ..... so before i proceed .... i would like to acknowledge all the great work the guys r doin out here !!..
was working on a friends jasjam which had schaps 4.20 running ... due to some issuses ( screen going blank white )with schaps' ROM , was trying to flash K's 1.30b .... the flashing froze midway .... after that could only see the bootloader for a couple of days .... used the mtty method to recover ... but now i am stuck with the first splashscreen and it doesn't budge from there.....
Would really like some advice here guys
Hiya XDA
I've been trying all evening to get any HardSPL onto my Diamond without success, everytime I try I get to 0% and after a few minutes "error [260] connection" and the phone keeps its' black screen until I soft-reset it.
Can anyone help me get a hardspl onto my phone? I would really like to try WM6.5. I've read many SPL-guides already, so you don't have to point me to them
(even that on modmydiamond.info)
Thanks in advance!
esset said:
Hiya XDA
I've been trying all evening to get any HardSPL onto my Diamond without success, everytime I try I get to 0% and after a few minutes "error [260] connection" and the phone keeps its' black screen until I soft-reset it.
Can anyone help me get a hardspl onto my phone? I would really like to try WM6.5. I've read many SPL-guides already, so you don't have to point me to them
(even that on modmydiamond.info)
Thanks in advance!
Click to expand...
Click to collapse
Here's the Tutorial and here's the Troubleshooter. They're both stickies. Please search and read before posting.
Thanks for the quick response, but as I said. I've read all stickies and guides, and it's still stuck at 0%.
esset said:
Thanks for the quick response, but as I said. I've read all stickies and guides, and it's still stuck at 0%.
Click to expand...
Click to collapse
Did you let your device sync with Activesync/Windows Mobile Device Center?
Try recreating the sync pairing.
Try uninstalling the device from PC's Device Manager and reinstalling it and then try recreating the sync partnership.
Try another USB port.
Yes, yes, yes and yes. I even tried doing it on my laptop.
Edit: I even tried flashing down to 1.93 with HTCs official stuff, no success there either
esset said:
Yes, yes, yes and yes. I even tried doing it on my laptop.
Edit: I even tried flashing down to 1.93 with HTCs official stuff, no success there either
Click to expand...
Click to collapse
Another USB cable?
Try manually entering bootloader and connect to PC. The label should say USB not Serial and try from there.
esset,
May I ask what branding/model of the Diamond you own?
I own a pure AT&T model just purchased a week or two ago. And, so far I've also had almost zero luck flashing it. I'm moving from an AT&T Tilt which I've flashed so many times, the USB port is starting to wear down. I've also got a lot of experience with many small computing devices with all types of weird programming and flashing routines, so I'm not a newbie. But the AT&T Fuze just seems to be locked in a way that has yet to be covered by the good XDA folks here. Heck, I can't even dump the shipped ROM off the device to send it here for checking out by the developers. All I've been able to do is flash an odd 1.90 HardSPL that seems to have locked the phone even tighter than before. YUCK!
If you're in this same scenario, I'd suggest patience. Eventually someone with enough knowledge of these devices will be able to help out. It is frustrating though, after flashing the other phone so many times with so many different configurations to be held back on the new one.
tnyynt said:
Try manually entering bootloader and connect to PC. The label should say USB not Serial and try from there.
Click to expand...
Click to collapse
You might find this odd. The down-volume + back arrow key combo doesn't seem to work with some of the new versions of the Diamond. I've tried on two of them, and neither respond to this key combo at startup.
Many times entering the bootloader is not a problem though. The routine does cause the phone to go there. And, I can get it there by other means. Just not via the boot up sequence. This tells me there is something very different about these models....
I tried starting and flashing directly from the bootloader (showing USB), and the phone got to show a percentage field (the one when you are flashing) but same here, is constantly at 0% until the flashing utility times out and tells me to reboot my phone and guides me through steps if it has been semi-bricked (bootloader is the volume down + softreset, right?)
I bought my phone in the first shipment to Sweden, it's not locked to any company, bought it without subscription
Else I just flashed it up to latest ROM from htc.com (still no success with HardSPL ) to 2.03.413.2 SVE (02/06/09)
Radio: 1.09.25.23
Version: 52.51.25.26H
ninjaedit: (In the four-colored bootloader thing it says DIAM100 64M SPL-2.03.0000 MicroP-Diam (LED) v11)
Tell me if you need any other info :]
Here's another indication that the new phones are different. I've copied a DIAMIMG.nbh file to both a flash card inside the phone, and to it's internal memory. (sorry, but the thread on that location is confusing on what memory. I assume like most phones of the past that it's supposed to be the flash card, but "internal memory" is not a flash card.) But, the loader screen always responds with "no image file" when it's called up. So, is there a different name expected now?
put manual hardspl into your device, and click to it from your device..
zerocool81 said:
put manual hardspl into your device, and click to it from your device..
Click to expand...
Click to collapse
Tried that with every Hard-SPL linked to from this thread: http://forum.xda-developers.com/showthread.php?t=415191
Didn't work
Something's changed.
zerocool81 said:
put manual hardspl into your device, and click to it from your device..
Click to expand...
Click to collapse
Hi uhm, was that answer aimed for me or to scottwilkins?
If it was for me, is it possible to flash the mobile directly from the memory-card (or internal flash card)? Else if you mean the "manual make-the-screen-black-and-go-to-bootloader" my screen just goes blank, as when you do it with the RUU, and just stops there. Also seems like it looses the connection via USB doing so too. And flashing through the bootloader directly (volume down at softreset) shows the progressbar on the phone, but steadily at 0% (when trying to flash).
search and download
a) SDA_ApplicationUnlock.exe (Desktopprogram)
b) EnterBootloader.exe (ATTENTION: it must be that for diamond, normaly find by flashing-tools)
connect with active sync and copy EnterBootloader.exe to pda-root.
start SDA_ApplicationUnlock.exe on desktop and follow all but reset (DONT RESET)
start EnterBootloader.exe on pda
if bootloader-Mode and USB-Label than start flashing
wait for response
scottwilkins said:
Tried that with every Hard-SPL linked to from this thread: http://forum.xda-developers.com/showthread.php?t=415191
Didn't work
Something's changed.
Click to expand...
Click to collapse
try this.. put this file into internal storage and lounch this from ppc
http://rapidshare.com/files/207721836/SSPL-Manual.rar
okokur said:
search and download
a) SDA_ApplicationUnlock.exe (Desktopprogram)
b) EnterBootloader.exe (ATTENTION: it must be that for diamond, normaly find by flashing-tools)
connect with active sync and copy EnterBootloader.exe to pda-root.
start SDA_ApplicationUnlock.exe on desktop and follow all but reset (DONT RESET)
start EnterBootloader.exe on pda
if bootloader-Mode and USB-Label than start flashing
wait for response
Click to expand...
Click to collapse
I tried what you suggested, I successfully unlocked the phone (and did Not reboot it). Ran the bootloader; and the screen just went black, as usually, and nothing more happens
zerocool81 said:
try this.. put this file into internal storage and lounch this from ppc
http://rapidshare.com/files/207721836/SSPL-Manual.rar
Click to expand...
Click to collapse
That program makes the Fuze screen just turn black and do nothing. Cool, huh
Seems that the newer stock ROMS might be blocking something... hmmmm....
Well, crap!
I just figure out where my whole problem is...
The Fuze (my phone) = The Raphael
NOT the Diamond.
I just scrolled down the forum list, saw a phone that looked like mine and went there. DOH!
I feel like a total dumb-ass.
If I'd scrolled just a bit farther down the XDA forum, then I'd seen the Raphael phone.
Holy Cow! Go ahead, say it, I deserve it...
Thanks for all the help otherwise. It was a learning experience for me....
esset said:
I tried what you suggested, I successfully unlocked the phone (and did Not reboot it). Ran the bootloader; and the screen just went black, as usually, and nothing more happens
Click to expand...
Click to collapse
hi,
i think, you have the wrong bootloader.
i find this and try it by me self. this brings your fone definitly to bootloader.
than you can start manualy the hard spl by normal description way.
http://rapidshare.com/files/208123046/EnterBootloader.exe.html
okokur said:
hi,
i think, you have the wrong bootloader.
i find this and try it by me self. this brings your fone definitly to bootloader.
than you can start manualy the hard spl by normal description way.
http://rapidshare.com/files/208123046/EnterBootloader.exe.html
Click to expand...
Click to collapse
Thanks, but that file takes me into the bootloader, and when I start flashing the percentage is still at 0% until the software times out. Same as before, just the usual "going-into-the-bootloader".
Hi guys,
Can anyone help me here ?
When I try to start up my Phone, it always loads the bootloader ...
I tried running reflashing a rom and task29, but no help there :s
Does anyone have an idea what to try ?
Tnx
Nick
Some people with the same problem said that their batterie was broken. Can you try another batterie?
I'll give it a try
Will let you know ...
Lennyz1988 said:
Some people with the same problem said that their batterie was broken. Can you try another batterie?
Click to expand...
Click to collapse
Nope, doesnt help.
Tried with a friend's battery, and have the same result.
Also tried using his phone with my battery and worked perfectly.
Any other ideas?
Trickass said:
Nope, doesnt help.
Tried with a friend's battery, and have the same result.
Also tried using his phone with my battery and worked perfectly.
Any other ideas?
Click to expand...
Click to collapse
Just to ask: You're not (accidentally) holding down the volume key when you press the power key (or reset) to turn on, are you? That puts it into bootloader.
MCbrian said:
Just to ask: You're not (accidentally) holding down the volume key when you press the power key (or reset) to turn on, are you? That puts it into bootloader.
Click to expand...
Click to collapse
No, I'm not doing that
I thought maybe it got stuck though, something like that :s but when I do press it, I hear a pretty clear "click", so I guess it's not broken at all...
Also, I noticed that when I try to reflash a ROM, the "current image" (or whatever it's called) is blank ...
(I mean the thing that sais the version number of the currently installed rom)
Okay, sounds dumb I know, but did you flash a new rom after flashing Task29?
It is used to wipe the OS out completely BUT you then have to re-install a new OS...
Just thought I'd ask.....
Same issues.
Same issues on my touch pro 2.
The only solution i find in order to make it boot is with mtty on a Windows xp pc with no activesync.
Perform a
set 14 0
task 8
then the phone boot on the os but on the next reset stay in bootloader !
ultramag69 said:
Okay, sounds dumb I know, but did you flash a new rom after flashing Task29?
It is used to wipe the OS out completely BUT you then have to re-install a new OS...
Just thought I'd ask.....
Click to expand...
Click to collapse
Lol yeah I know that
Thanks anyway
Frederic.james said:
Same issues on my touch pro 2.
The only solution i find in order to make it boot is with mtty on a Windows xp pc with no activesync.
Perform a
set 14 0
task 8
then the phone boot on the os but on the next reset stay in bootloader !
Click to expand...
Click to collapse
Hm, I'll see if I can find a Windows XP pc somewhere and try ... MTTY doesn't seem to work with Win7 x64
Trickass said:
Lol yeah I know that
Thanks anyway
Hm, I'll see if I can find a Windows XP pc somewhere and try ... MTTY doesn't seem to work with Win7 x64
Click to expand...
Click to collapse
Hummm i have see somwhere a howto for mtty on W7... but i'm a little lazy i have choose to do this on a old windows xp
But this command are just temporary i'm searching for something more stable !
Some news from my Rhodium Stuck in bootloader
I have try to Hardspl it (Olinex 0.85)
The good news is i have manage to do it, the bad news is after that even the
set 14 0
don't manage to make it boot.
After a while searching, (thanks wiki of another phone) i have find those command :
password BsaD5SeoA
set 14 0 # Maybe it's usless now but in fact i don't know
set 1 0
task 8
And now i'm back to my start....
I tried using the MTTY commands, and when I did it the first time, the phone booted and performed its "first run setup" thing.
After rebooting though, it went back to the tricolor screen, and I can't get past it anymore, even with the same MTTY commands ...
Any other ideas ? :/
mtty, a lot of post on the internet...
hi,
I think we are a the same point !
I have find a way to start a boot with the HTC screen but the phone tel me that a txt file is missing on the sd card ???!!!???
with mtty :
boot
yes it's quite simple why i haven't think of that befor i don't know... but that didn't solve my problem at all.
I have send a mail to HTC in order to have a diferent point of view but all they said to me is doing a hard reset (who didn't do anything...)
I will post the avancement of my test but i feel a little stuck.
Note : After searchin on the internet, the set 14 0 tel to the phone to boot on the os after a flash (sometime the phone don't reconize the end of flash)
the set 16 0 (or set 16 1) disable (or enable) the RUUNBH tag on boot loader.
More Infos...
I have find a post on a other forum whos said that a defective battery could result to an unstable beaviour of the phone.
I have let it without battery for a day and, today it has directly boot on the OS.
I have ordered a battery on ebay and waiting for it maybe the solution ?
Frederic.james said:
I have find a post on a other forum whos said that a defective battery could result to an unstable beaviour of the phone.
I have let it without battery for a day and, today it has directly boot on the OS.
I have ordered a battery on ebay and waiting for it maybe the solution ?
Click to expand...
Click to collapse
Oke, I will try to take out the battery tomorrow as well ... Although, I tried using a different battery and it didn't help ...
Right now, I managed to boot using mtty set 14 0 > task 8, which seems to work
(sometimes, I need to do the task 8 twice in a row ...)
So as of now, I managed to flash a stock rom onto the phone, and only have to try and reset hardspl back to stock as well.
Waranty here I come ...
lol mine is out of waranty, and it's the solution i ve find everywhere !
did you try hard reset by holding the call and hang up button together when you power up the phone.
last time I remove a program and tha cause me to boot ot a black screen after teh bootloader. Hard reset fix the issue as it return teh phone to the sotck setting of the rom.
PUTALE said:
did you try hard reset by holding the call and hang up button together when you power up the phone.
last time I remove a program and tha cause me to boot ot a black screen after teh bootloader. Hard reset fix the issue as it return teh phone to the sotck setting of the rom.
Click to expand...
Click to collapse
yes, i've try it (HTC has send me the same advise) and... same issue !
In order to done the hard reset (who didn't execute when the phone is to boot in bootloader) i have do a set 14 0 and reset with power and holding the two call hang and power.
But thanks for the advise !
Frederic.james said:
lol mine is out of waranty, and it's the solution i ve find everywhere !
Click to expand...
Click to collapse
Out of warranty ?
How old is it then ?
Mine is just under 1 year old, so I'm lucky I guess ... and I hope
Trickass said:
Out of warranty ?
How old is it then ?
Mine is just under 1 year old, so I'm lucky I guess ... and I hope
Click to expand...
Click to collapse
Hum it's the phone of a firend who give it to me... and he has buy it on e-bay.... for the waranty sound difficult to retreive a bill and... I will search till i find something to do