hey, I'm only 1.40 Olinex unsigned;
when i first boot up I have this:
R 52.2.25.12h
G 1.00.25.05
D 1.93.0.0.0
My phone shuts down by itself, after i see the HTC logo and i hear the shut down sound.
why is that happening, is it software or hardware?
PS: RUU_Diamond_HTC_Europe_1.93.401.2_Radio_Signed_Diamond_52.29.25.12_1.00.25.05_Ship
I am flashing with this ROM, and with some other ROMs it is not even booting up
try this mate
try running mtty then reflash your rom, mtty formats your nand chip and repairs any erroes read THE DEFFINATIVE MTTY THREAD all explained there got to be worth a try hope this helps
trying this now will report on results thank you mate
still having problems, now phone wont boot up at all
i think i can make it boot
(I got USB error after i pressed <- and Vol Down to flash ROM )
is there a problem in my SPL? is my phone bricked?
i can boot into WinMo after i have left the phone for a few hours
but now 5-20 minutes after booting (depending on each time), suddenly i see the HTC logo, and here the shut down beep
any help ?
could it be a bad battery issue?
because when i turn it on i see an exclamation mark next to the battery icon in the bar on top
any suggestions? plzplzplz !!
MTTY Thread
Reflash your phone doing EXACTLY what it says in that thread and you should be good to go.
mzaouar said:
could it be a bad battery issue?
because when i turn it on i see an exclamation mark next to the battery icon in the bar on top
any suggestions? plzplzplz !!
Click to expand...
Click to collapse
Buy another battery, It looks like battery problem.
Good luck
now the battery looks like it's working fine, i've flashed a new radio ROM, but it's getting turned off again :S
should i upgrade to the 1.93 HSPL? because i have a 1.93 ROM
can the problem be from the radio?
Same thing here,
Been flashing the diamond to the bone.
After flashing the (22 jul) verion of the NRG warhawk rom
I have been experiencing some glitches.
As it was my first step from wm 6.1 to 6.5 and I dont want to go back.
The errors ive experienced are not related to rom issues.
Because i got em almost with every rom.
- random restarts
- loss of contacts
- no responding of the device
And ive been reading about the MTTY sollution I go and try that one.
Enonoid, so you didnt find a soltuion to your problem?
and if not, what do you suspect the culprit is?
Been flashing the diamond to the bone.
After flashing the (22 jul) verion of the NRG warhawk rom
I have been experiencing some glitches.
As it was my first step from wm 6.1 to 6.5 and I dont want to go back.
The errors ive experienced are not related to rom issues.
Because i got em almost with every rom.
- random restarts
- loss of contacts
- no responding of the device
And ive been reading about the MTTY sollution I go and try that one.
Reply With Quote
the problem isn't rom related running MTTY formats the chip where the rom resides its like reloading windows on your computer when you know there are bad sectors on your hard drive. it just wont happen follow the THE DEFINATIVE MTTY THREAD and honestly all should be fine it sounds quite tricky at first, but I use mtty everytime i reflash now saves whishing you'd done it once you've reinstalled everything and believe me its so easy if you just follow the guide.
Related
well i just downloaded and proceeded to flash the latest ROM from clubimate..
everything went normal, upgraded Radio, ExtROM, and CE ROM, then i was asked to unplug the device, and cold boot it, which i did.
after clearing the storage, the device reset, showed the splash screen, the version strings (latest ones) and stayed there.. i kept it for 15 minutes to no avail..
i reflashed again from the bootloader and still the same behaviour
Radio ROM takes 20 minutes to flash, EXT Rom takes less than a minute, then when CE flashing is done, i cold boot.. again it gets stuck on the boot splash screen
i tried a different PC, different cable, older ROM version.. all the same..
any clues as to what may have gone wrong here?
Thanks in advance
me too
Got the same problem and same description of proces
well,
i tried flashing the radio rom again, tried every mtty trick in the book and still got nothing.
eventually i've taken the phone to i-mate service center, and it's been there for a week
they said the motherboard is faulty and needs replacement, i'm suspecting the flash chip has gone bad.
now i'm not sure if this applies to all of us here with the same symptoms after the upgrade, but i really find it strange that after all these years with i-mate devices, upgrading, downgrading and flashing different roms, half the forum hits the same dead-end when a new update comes out from i-mate and they try to flash it on.
something is strange about the latest rom. i just wish i knew what it is
AntiProxy said:
...i'm suspecting the flash chip has gone bad...
Click to expand...
Click to collapse
you bet it is!
buzz
HELP PLEASE BUZZ
I have upgraded to rom JASJAR_WWE_13076_164_10900_wwe_ship
when rebooted I just get blank grey screen.
after messing about with mtty I got it so I can reinstall it again at last but then same problem.
Any I deas Buzz you da man
Cheer in advance
Jon
same problem here
damn, same problem with me
its not recognized by the pc and there is absolutely nothing on the screen
anyone found a solution for my thousand dollar paperweight?
AntiProxy said:
after clearing the storage, the device reset, showed the splash screen, the version strings (latest ones) and stayed there.. i kept it for 15 minutes to no avail..
Click to expand...
Click to collapse
I now have the same problem as well. I however received this through the trials and tribulations of getting my JJ into the damn bootloader...
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
i have flashed my diamond with the official htc rom
im on 1.40 olinex, now i can only access boot mode.
sometimes if i leave the phone without a battery for like 2 hours, when i turn it on i see the "touch diamond" logo, if i leave the battery for a whole day i see the windows mobile loading screen, but then suddenly the phone turns off
plz if you have any idea about this problem help me
If you can acces bootloader, then your diamond isn't bricked.
Try the unsigned version of olinex' hard-SPL and flash the ROM again.
Good luck!
hey ElCondor, im on 1.40 olinex, i cant flash it because it is protected
how can i flash the unsigned 1.40 olinex one?
Here is a link to the unsigned hard-spl.
Make sure you download "Unsigned-Hard-SPL-Diamond-OliNex.zip".
Follow the instructions:
1) Download, extract to an empty folder.
2) Run RomUpdateUtility.exe, Have Phone Synced with PC (go into bootloader, connect your cable, then the word "serial" in bootloader will change into "USB".
3) follow steps, check device for prompts after PC shows loading bar. it should go to black screen now.
4) SPL flashes, device automatically reboots, job done.
5) to confirm you got it installed, go into bootloader mode (volume down + reset, i.e. press volume down button and reset then keep holding the volume down key until you see tricolour screen) and verify the screen shows 1.40.OliNex.
note: you will not see the SPL version during normal boot, that is the OS version, not SPL!
Installing this will hard-reset your device.
Best Regards,
ElCondor
when i flashed the unsigned 1.40 olinex, the device rebooted
windows mobile is preparing your phone for first use
htc logo
phone went off :S
will try flashing rom again
flashed ROM again, now it wont boot up no htc diamond logo no nothing
i can access boot mode (1.40 olinex unsigned now i guess)
is there no way i can boot the rom? what seems to be my problem?
mzaouar said:
flashed ROM again, now it wont boot up no htc diamond logo no nothing
i can access boot mode (1.40 olinex unsigned now i guess)
is there no way i can boot the rom? what seems to be my problem?
Click to expand...
Click to collapse
Hi
If you can access the bootloader then your device is not bricked. Therefore download a rom of your choice then connect to the usb when on the bootloader then use a Diamond custom RUU (normally come with the rom) follow the steps. After rom updated make a hard reset. I hope it will run ok.
Looks your symtons are showing like your rom corrupted.
Good luck
i am flashing this ROM
RUU_Diamond_HTC_Europe_1.93.401.2_Radio_Signed_Diamond_52.29.25.12_1.00.25.05_Ship
the newest one i downloaded from htc. com is giving me rom update error
would you recommend a good rom for my phone?
after flashing and reflashing and hard resetting with the ROM showed above
still cant boot in ROM mode, only in boot mode
el condor sabes, anything ???
should i flash with a new rom, and if yes with which?
(diam100 olinex 1.40 unsigned)
Perhaps try a custom rom?
I found when flashing to an official rom from a different provider (my phones telstra and was flashing 3) I had issues with the rom booting and had to follow a post on here somewhere to get it working, however When I had this problem I could still flash any custom rom with no issues.
Unless its for warrenty purposes then its probably not worth flashing the "original" perhaps flash A.Z.T.O.R. = Alpha Zero Tweaked Official Roms which are close to the original but with benifits of being modded for faster speed etc.
Anyways Im no pro but I know what you are going through and I am trying to find the link to the fix to your problem as I also had the problem. But recommend trying a custom rom to confirm the problem is the same as mine.
For the record now I do not use official roms anymore, with WM6.5 running well for the most part on the diamond its a great step backwards when you revisited 6.1
flashed to SwiftBL-WWE-Diamond-v7.5-Full-16MbPP
still same problem can only go to boot mode
i am feeling there is no solution to my problem ?
is the phone bricked? :S
If you haven't done yet, flash the hard-spl I posted. Just do it, re-instal the hard-spl! Then, flash another ROM, maybe (as said before) your rom is corrupted.
The problem here is, that you first installed the unsigned hard-spl, and then flashed a corrupt rom. In that way, the hard-spl can be damaged too, so flash the hard-spl again and flash another rom should work.
Good luck!
I did :S but to no avail, I will do it again fingers crossed :S !
update: weird, everytime after i flash the hardspl unsigned, it boots up, i can see the "touch diamond" logo
windows mobile booted.. preparing your device..
update 2: windows mobile booted, installing everything
omgomg it looks it might work this time, fingers still crossed !!
el condor !! haha fingers crossed
update 3 :S : windows mobile installed properly, phone rebooted, went again and opened it, then i heard a sound from the speaker and the phone turned off :S
it must work what could the problem be now? last step !
Okay try a hard-reset, maybe that works.
If not, then flash hard-spl again, then hard-reset, then flash another ROM. Then hard reset. Then try again if it boots.
Is your battery enough charged? That could also be a reason.
did not work, wont even boot up
when i said if i leave battery out and such, I thought it might be hardware/heat related
http://www.htcwiki.com/thread/2069847/HTC+Diamond+-+Severe+Crashing+Problem,+maybe+heat+related
could this be it? will i have to send my phone for repairs?
because maybe when WinMo was loaded, the phone started to heat up and it shut down
so basically my solution is not a software fix??
If none of the tips worked, and you have the same problems as described in the site you linked, then you probably have to send it back.
One thing you could do: Try if the other hard-spls (1.37 and 1.93 unsigned) are working for you.
I'm sorry for you, maybe someone more skilled than me (like cmonex or olipro) knows how to solve your problem.
it's alright :S i thank you for all the help you have offered !
( it is customizing right now) but i expect it to reboot anytime now
worked, 5 minutes into winmo it restarts
mzaouar said:
worked, 5 minutes into winmo it restarts
Click to expand...
Click to collapse
oh,does it worked?how can you get it work?Please tell me....my diamond could only get in the bootloader yet....
mzaouar said:
worked, 5 minutes into winmo it restarts
Click to expand...
Click to collapse
OK good to hear that, if you have any more questions in future, just ask!
Glad to be of some help
msvb007 said:
oh,does it worked?how can you get it work?Please tell me....my diamond could only get in the bootloader yet....
Click to expand...
Click to collapse
Ive sent you a pm, there's no need to use this thread for your questions because the problem in this thread is solved.
So take a look at your pm!
Hello,
afther an update on my p3600 with an error.
I have only the bootscreen of the rom.
I cant flash any new rom , every time i have connection errors.
is there any chance to correkt the problem or to delet the phone completly?
A Hardreset doesn´t bring anything.
Please help me i cant do anything with my p3600.
take a look:
http://forum.xda-developers.com/showthread.php?t=572747
i read the thread,
but i have tested to update the hard spl but it doesn´t work.
The update software always told me that there is an connection error.
But when i want to install the rom 6.1 manila 2g the software found an connection and start to update but when the software is at 1% the update software told me that the rom is corrupt
This is the reason you should always install HardSPL BEFORE you start flashing any roms at all.
Once you have bricked it, then it is too late to put HardSPL on there.
The whole point of HardSPL is to ensure that you will always be able to get a connection to the device even if you have a broken rom on there.
If the phone is bricked, with no HardSPL on there, your only remaining option would be to try using an unbricking exploit procedure like this:
HTC Trinity Stack Overflow exploit - how to unbrick any Trinity stuck in bootloader!!
^^^ Sorry I have never had to do this myself and have no experience or advice on how to use that exploit utility ... hopefully there is enough help in that thread to get you going again.
Good luck.
EDIT: I thought I'd better just check you do realise that you can get the Tri-colour SPL screen up manually by holding down POWER + CAMERA buttons and 1sec press of STYLUS RESET button. Quickly reading through that splxploit thread I was disturbed to see just how many people didn't even know who to do that
Maybe it's just my paranoia from owning an "i" model but I have never done a single rom flash without first using that 3 button trick to get into SPL screen.
praefke1986 said:
...But when i want to install the rom 6.1 manila 2g the software found an connection and start to update but when the software is at 1% the update software told me that the rom is corrupt
Click to expand...
Click to collapse
Try flashing the Stock ROM that came with your phone. It may get you going again. Can be downloaded from the HTC website.
Hi guys, looked a lot of threads on this forum but didn't see one similar to my situation!!!
My HTC P3300 Artemis is dead in a very strange way.
-Had it for a week with WM5(factory, german) - had no problem.
-After a week i've installed the WIN6.5WWV from Shady, from this forum - everything was ok the system worked fine (did the USPL unlock before installing)
-The device worked for around a week and yesterday just died while i started a ringtone from my additional flash of 8G SDHC within the device (had no problem with the flash before)
-A note - while on 6.5, the device had different issues with stability, had to restart once in a while.
Description of death :
1. Power button does not start the device(?!)
2. Trying to Hard reset (2 soft buttons + Reset with the stylus) - firstly i get a black screen that asks for confirmation, i press the green button to confirm. I see the text :
Format FAT partition
Format is completed!!
Then a WM logo appears on the screen with a red text in upper left corner:
IPL 1.12.0001
SPL 1.11.0000
And the phone freezes in this state.(?!) - does it mean the SPL is freezing? because before that i saw like 4 lines written with red, now only 2, the last being with SPL.
PS:
-Tried to take out the battery and repeat all steps, tried to put charger to make sure the power is constant (don;t ask, just tried .
-Tried to take off battery, wait for 20 minutes, then repeat
-Tried to take battery, wait for one night and repeat (actually i didn't wait, i just went to bad, it was night already
-Tried the bootloader mode (the Power+Voice+Reset)- it works fine, but don;t know if this helps.
What could be wrong? Is it a hardware issue? Very strange!!
Thanks for your time
Have a good one
maybe u can flash it again in bootloader? that could solve the problem?
if else, it looks like a hardware issue or the phone is bricked.
mvenneker said:
maybe u can flash it again in bootloader? that could solve the problem?
Click to expand...
Click to collapse
Yesterday I tried to install from flash like described here - and it was dieing all the time at "Reading from SD" - the screen was becoming bright white and it just shut down. (tried 4 times with same result, only that the moment when the screen went white was different - from 5 seconds to 2-3 minutes)
Right now, when i wanted to reply about this, i said to myself, let me try one more time!!! What do you think???? It worked!!!!
Reading from SD (1-2 minutes)--> Flashing OS (2-3 minutes) and after this it was DONE!!!!
Shuuuush!!! HTC is so weird!!!
Thanks for the help ) i think there are 2 logical ways to go next:
A) Just use it and hope it's gonna be all right in future
B) Install a generic WM not a cooked one. And maybe it's wize to downgrade to WM6.1 or WM6?
What do you recommand?
Have a good one!!
I'm so happy i fixed it!!
well u can safely use a cooked rom, if read a few topics that it can occur sometimes that a cooked rom isnt good flashed the first time. maybe that was the case with your phone, who knows