Stuck in bootloader - 8525, TyTN, MDA Vario II, JasJam ROM Development

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

Related

[Help] White-Screen after 3-26 LVSW firmware flash

Sorry to open a new thread, but I want to ask is there any method to fix this problem apart from using Mitty?
I tried flashing LVSW 3-26 firmware using SPL 1.06 or the 1.1x, both gave me the end results of white screen.
I am newbie to Mitty and worry of bricking my device with Mitty.
Can anyone suggest what I could do to cast the white screen away?
Desperately in need of help.
Thanks
I see by the sorry for a new thread you have read
http://forum.xda-developers.com/showthread.php?t=299644
I am with you. Right now I would go to a different version. The previous LSVW or another build. I am trying the mtty thing but I am running vista and cannot get NBHextract to work.
If you do not want to risk it maybe holding off a day and checking back for an update. These guys are fast. Also like I said go to a different version. I flashed the revious LSVW os only and it worked 3 times in a row perfect
When you say white screen what do you mean?? You get a white screen and the device doesnt boot?? or the device has a white today screen?
people
for black 1.3 i will release two versions
one with SPL and OS (with RUU 3.6)
and
one with only OS using standard RUU (assuming you already have HardSPL)
this will give u an option
jasjamming said:
people
for black 1.3 i will release two versions
one with SPL and OS (with RUU 3.6)
and
one with only OS using standard RUU (assuming you already have HardSPL)
this will give u an option
Click to expand...
Click to collapse
Hell yes. Makes the guide clearer to make (i will mention the value of embedded HardSPL and radio though )
mrvanx said:
When you say white screen what do you mean?? You get a white screen and the device doesnt boot?? or the device has a white today screen?
Click to expand...
Click to collapse
The White Screen for me is i can see the HTC Flash screen, but the Windows Mobile screen becomes white without me even seeing it and the Today screen is also white also.
Also, i was wondering if using Hard-SPL might help?
Thanks
nope i am using hard spl and tried it still white screen
Me too....
I also got the white screen of death. lol.
i used the version that was posed on the main page. After the update and initial boot the white screen comes on.
I was able to bypass this after several resets. Then it will start the customisation process. After which it will restart and go to a white today screen with no icons. I do have the task bars at top and bottom but no dialer.
My fix. I went and dl RUU_HER_6.20.100.0_0.00.00.00_XDA_WWE_XBOW_Custom. I installed it and works like it did before.
I will wait till there is a fix for this...
BTW I have a cingular 8525
I WANT TO OFER YOU GUYS SOMTHING
those of you who got white screen do you have language on boot?
i mean do you have diffrent language pack that need to be boot when you make hard reset?
cause i notice that when my language pack boot with new rom igot
white screen the language pack stuck it
then i remove my language pack from booting then its ok!!
After 1 whole day 24 hours non-stop fidgetting with my device, still NO LUCK...
Flashed it so many times, but still white screen.
Anyone can help me out?
Thanks
HKFreak said:
After 1 whole day 24 hours non-stop fidgetting with my device, still NO LUCK...
Flashed it so many times, but still white screen.
Anyone can help me out?
Thanks
Click to expand...
Click to collapse
Think this should help, I did cut the quote down a bit.
mxlaser said:
After hours and sleepless night, and so many flashes i think the NAND in my dopod was hot enough to fry a breaky for me, i've come to the comclusion, i have 100%, no issue success with all ROMS, using 1.01MFG and MTTY flashing each part seperatly. Not one time has a white screen appeared, with ANY rom, and i've tested all the current WM6 roms.
I d/l'd and tried the latest LVSW rom (26/3) and have exactly the same issue when using the packaged RUU to install it. However, when i use MTTY, its perfect every time.
I would suggest the following steps
1. Load into the bootloader mode (HOLD POWER/OK buttons and press soft reset)
2. Flash SPL-1.01MFG onto your device (Read wiki info and file links here)
3. Once flashed, reboot and do step one again to get back into boot mode. You should now see your boot as 1.01MFG
4. Use NBHextract to extract 06_OS.nb file from RUU_signed.nbh file found in downloaded rom package.
5. Load up MTTY, follow steps in the wiki for the 1.01MFG on how to flash OS.nb (OS.nb is the 06_OS.nb file renamed to make it easier)
6. Once flash is complete, the latest rom is installed and you won't have a white screen
7. Now flash Hard SPL v4 onto your devic for safety reasons.
And this fix is EASY to do, 100% works every time.
Click to expand...
Click to collapse
It worked 100% for me first time.
Just for the record I used ROMbaker to get the 06_os.nb then just rename it to os.nb.
Also if you are not sure and feel nervous about bricking it, then just wait for a proper fix.
Finally I got the white screen a few times and everytime I flashed the previous LSVW os only the device worked perfect. From my reading Olipro may have found the problem haveing to do with bad blocks. Nothing major but I believe they are working on it currently.
If you follow these directions and install 1.01MFG, you can BRICK YOUR DEVICE with ANY mistake!
We're not talking about a brick that can be fixed either. You precious phone will become a paper-weight forever more! Really.
I DON'T CARE WHAT THE N00BS ON HERE SAY; FLASHING 1.01MFG IS **NOT** A RECOMMENDED WAY TO FIX THIS PROBLEM! DO NOT INSTALL 1.01MFG UNLESS YOU ARE OK WITH THE CHANCE THAT YOUR PHONE WILL BE BROKEN FOREVER!!
bubu23 said:
I WANT TO OFER YOU GUYS SOMTHING
those of you who got white screen do you have language on boot?
i mean do you have diffrent language pack that need to be boot when you make hard reset?
cause i notice that when my language pack boot with new rom igot
white screen the language pack stuck it
then i remove my language pack from booting then its ok!!
Click to expand...
Click to collapse
No, I have never installed any language packs on my phone. I use good ol' english.
HKFreak said:
After 1 whole day 24 hours non-stop fidgetting with my device, still NO LUCK...
Flashed it so many times, but still white screen.
Anyone can help me out?
Thanks
Click to expand...
Click to collapse
Just go back to a previous version of WM6.
It only takes several minutes to put back XDA- Live.
mzahiri said:
Just go back to a previous version of WM6.
It only takes several minutes to put back XDA- Live.
Click to expand...
Click to collapse
I tried going back to WM5 firmware.
Flashing the firmware is a success but I still got the white-screen-of-death.
Any other options?
Thanks
SPL-1.35.Olipro will be released shortly; this should address the issue of the whitescreen error, all those having problems under 1.30 should no longer encounter it if they were able to flash fine with old SPL's
Olipro said:
SPL-1.35.Olipro will be released shortly; this should address the issue of the whitescreen error, all those having problems under 1.30 should no longer encounter it if they were able to flash fine with old SPL's
Click to expand...
Click to collapse
Go Oli Go!
Question ?
Hi All,
Sorry N00b alert at this .. but very IT literate
Just a quick question off the cuff, what was the last(est) version (can you provide a link) that i can flash to now .. (not mucking around seperating stuff etc) that wont give me the white screen issue.
I am currently sitting on LSVW 25/3 1.38.10 radio and 1.13oli
Thanx test

Unable to boot up after upgrade ROM to WM6

I follow instruction in http://forum.xda-developers.com/showthread.php?t=313486 but after hardreset.
My p800w is stuck in T-Mobile logo and version number. It can't continue booting up to windows mobile.
Question: How to flash ROM without ActiveSync?
How to recovery my Artemis?
Welcome any advice,
Thanks in advance.
Yea me to, mine is now a brick after that upgrade? No active sync connection possible and all I get now is the blue O2 start screen after the hard reset with the red writing and numbers in the top left hand corner..
Phone is an UK XDA Orbit
IPL 1.25.0001
SPL 1.11.0000
GSM 02.67.90
OS 3.4.0.0
HELP!!!!!!!
yeah, I had the same problem and have created a thread for it already. unfortunately I got no useful replies, and it seems that I am stuck waiting for an official o2 ROM so that I can recover my Orbit.
It seems there is a way to un brick our phones I just need to get my phone bootted into bootlader mode which no one seems to say how to do??
Can anyone help how I can boot my Orbit , like what combo of keys I need to press to boot it into bootloader mode then XP will see it at a driver level apparently Active Sync still won;t but I will be able to run some German ROM update with the ROM file replaced with the other ones and it may come back to life..
Help how can I boot my phoen in bootloader mode???
motomob said:
It seems there is a way to un brick our phones I just need to get my phone bootted into bootlader mode which no one seems to say how to do??
Can anyone help how I can boot my Orbit , like what combo of keys I need to press to boot it into bootloader mode then XP will see it at a driver level apparently Active Sync still won;t but I will be able to run some German ROM update with the ROM file replaced with the other ones and it may come back to life..
Help how can I boot my phoen in bootloader mode???
Click to expand...
Click to collapse
I read in here that you hold the voice button and soft reset.
Decaf said:
I read in here that you hold the voice button and soft reset.
Click to expand...
Click to collapse
Correct and use mtty
Already see in the forum ....
Thanks guys and apologies for the spelling..I ran the Artemis_USPL before I tried upgrading to WM6 and again have been able to run it after with my new brick now with the phone in bootloader mode but still when I try and run the german ROM update a) it will only work with the german file which freezes @ 3%? This seems to be a known problem reading around and b )when I replace it with the smaller ROM file, 54MB the german one is 66MB, I originally tried to use it doesn't read the ROM file or the update utility doesn't want to read it. I reckon I might be able to get it back if I can get one of the ROM update utilities to read a good ROm file and send it to the phone.
I can;t find this MTTY program to sniff the USB port and return the code of if the USPL util wokred as I think that could be key to all of this.
Can anyone post a quick how to here for
1) install MTTY from somewhere
2) what command to run agaist the phoen to see if the USPL util worked and what values I should be looking for
3) another WM6 ROM version (that the update utils can read) download location I can download from to try and send to the phone using the German update util
Not asking for much am I but I desperately need my phone back WM5 or 6 in the next day or so so really can't send it off.
Thanks
Error message I recive at the 3% stage when using the German ROM and english update util.
use the file attach and read that :
http://forum.xda-developers.com/showthread.php?t=285112
Thanks but I'm not that cleud up on what commands I'm meant to be sending. It works in Bootloader mode I ge a response from the phone by send it a command. But even if I get a response telling me what the CID status is its not much help as I think ti shoudl have tekane BEBEs ROM by now as I've got the german ROMUpdateUtility sending that 54,272KB file to the phone but it stops after 3%. What are my options?
motomob said:
But even if I get a response telling me what the CID status is its not much help as I think
Click to expand...
Click to collapse
That's right. On older models MTTY was quite useful, but not on the Artemis. You cannot use it to read the CID status anyway. If you are not sure about the status, run the USPL tool, just to make sure.
I've already re run the USPL ROMUpdateUtility and it completes 100% okay in bootloader mode. But after I hard reset and then try and flash the WM6 BEBE ROM or any ROM German etc back onto it it either fails with the error code I posted up earlier or gets to 3% and fails.
What are my options at this stage? Does anyone have a link to another ROM I can try like the original WM5 O2 ROM or any other WM6 ROm that might work. I'm willing to give them all a try as it's just a useless phone right now and I haven;t sent it off as 1) I need it before the weekend and 2) As I can flash some ROMs with the USPL and others have done this no problem I really feel there must be a solution as I can still falsh the phone.
What can I say RTFM... I did it all right and I didn't have a brick, I missed out one small detail... loading on the ROM with the extended ROM. All now running and it does seem a little faster than WM5.
Thank you to all those that tried to help out. To the others that are still having probs.. Don't try and run the update in the middle of a busy day in the office whilst trying to manage 100 other things meaning you are probably missing out a line like me...
One question though how do I get back my O2 power and storage meters on the today screen back as I liked them and the WiFi seems to have a bug where when it is enabled and you click on the WiFi symbol up the top it only allows you to switch it on, when it is already on.. so you have to open up the COMM manager to switch it off.
So how did you fix it exactly? I have read this thread thoroughly and can't find out what you did!
ERROR[206] occurs while trying to update ROM to WM6
While tring to update ROM to WM6 on O2 XDA Orbit i encounter ERROR[206].
I wanted to attach the screen shot but dont know how to do that, but anyway what i am doing is i attached my pda to my pc via activesync using supplied usb cord. Everything goes well till i reach a screen where it says "You are now ready to update your ROM image...." and once i click next a progress bar apperas and my pda shuts and activesync exit's automatically and my pda tries to restart with RBG band and some text:RUU, IPL 1.25.0001, SPL 1.25.0000 and USB. And thats it after few seconds or a min i get the ERROR[206] and my pda hangs.
I dont know why Activesysn shutsdown ???
Just an additional in i want to tell that without installing activesync i am not able to connect/pair my pda with my pc. So do i need to install the drivers and then try or it doen't matter cause once i install Active sync i can connect the device.
Please help me with this....
Thanks
unable to load bootloader!!!!!!!!!!!!
HELP!!!!!!!!
I have HTC3300, tried to update rom, now its bricked. I tried to start bootloader by pressing the voicebutton and softreset but loads in t-mobile screen and hangs, im unable to start the bootloader.
Is this end of story or are there any other options to get the bootloader to start????
please help
Bootloader
I had a problem with my phone loaded touch flow 4 and cid unlocking, everything was fine then after a while it froze at boot up.
I look put the battery and did a hard reset, put it into bootloadeder mode, reflashed with a t-mobile rom does not need to be cid unlocked to do that.
Once origonal rom was working, cid unlock again, flashed back to touchflow 4.0 - sorted
Where did you got an tmobile rom from can you tell me. Mine is also freezing on booting almost once every day or so after I've upgraded to 4.0

Moving from O2 WM6 to BB v 4

Hi all,
Plz bear with my ignorance when it comes to upgrading ROMS etc.
Basically yesterday I upgraded to O2's official WM6 ROM .... and find it "not so good". It is slow to respond etc( i found it slower than my WM5 )
So now I wanna move to BB4, question is how do i do it??
I have downloaded an Artemis_USPL from Prof. So what are the steps I need to do??
Is it ...
1) Run start_uspl.exe from the zip file and let it complete.
2) Run( double click ) the img-46785-Tom_B_B_v4_0_TouchFlo_Professional.exe
Is that all I need to do?
Also, if I brick it .... what do i need to do to revert to an original ( say o2 WM6 ROM) ... is it USPL it again then run the O2 rom??
Many thanks
Fahd
yep, thats what you need to do. both 1) and 2) will need some user input and after it's done the device resets itself. so after 1) wait until restart is complete, then do 2).
for your original roms you dont need uspl. but if you are not completely sure, run it anyway.
Thanks for that. Time to give it a whirl! Wish me luck!!
Hmmm doesnt wanna play ball.
Did the above and ran uspl .... got stuck on a white screen. So I rebooted the Orbit and tried running the BB4 .exe ... got to 3 % and told to that .......
Error 270: Update Error. The image file is corrupted. Please check your update ultilty.
Can anyone help?? It will not upgrade ROM.
I keep getting the white screen and it cant run ROM utility(Error 224: Device not responding ).
I then reset the device and run BB4 ... I get to 3% and then I get error:270 ( image file is corrupt ). I have downloaded the ROM again and still get this error.
Any helpers out there??
Thanx
Fahd
I had the ame problem mate. What you need to do is revert back to the original 02 WM5 Rom which can be found on this forum somewhere. Then once installed, run uspl & then the BB4 Rom & hey presto your sorted.
For some reason i couldnt get uspl to work on WM6 02 rom either
Hi fadhp,
Ensure that your windows firewall is disabled and also you shut down any anti-virus programs running on your PC
I also found that turning off all the plugins on the today screen helped me to upgrade my O2 orbit.
I went through the same issues as you with corrupted images at 2% , however following the steps above helped me.
The firewall was disabled and so was AV ... so not sure about next steps.
I thibnk I shall try downgradind to original O2 WM5 rom and then upgrade ....
question is where in this forum is that Rom!! I had seen it before but as usual when u dnt need something you find it and when you need it u cant!
Will keep on searching .... anyone know the link plz save me some time!
Thanx
F
question is where in this forum is that Rom!!
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=314866&page=2&highlight=orbito2uk-wm5
The link for the original O2 WM5 is in post #13, the 3rd one down.
Thanks for that.
Downgraded to WM5 now .... and tried to run BB4 .... still no joy. Same error.
Maybe i'll try another ROM just to see if that works and if it doesnt then MUST be my PC or something.
Here goes!
Cheers guys will kepp u posted.
F
Tried another machine ..... XP SP2 not FW or AV still failed.
Always get to 3% then crash.
HELP!!
Tried BB3.7 still no luck. 3% and crashes .... on 2 diff PC's.
I noticed that USPL runs ver 3.0.3.0 of the update utility but the actual ROMS when you launch them are running 3.6.3.6 ... does this make a difference?
Help guys plz!
Those are the issue no's of the rom upgrade utilities - it does not matter. It appears you are still not cid unlocked. whats your spl no? take it from first bootscreen.
SPL is 1.25.0000
IPL is 1.25.0001
Ideas??
The spl from uspl is 1.110000 so you need to run uspl again. Even if the screen goes blank wait till it says your rom has been upgraded.
Thing is when i run USPL and it gets to 100%, all i get is a white blank screen and nothing happens. So i have to reset the device.
Then i try and run the BB4 etc install and get to 3% before it conks out.
When I get the white screen ... what else can i do??
Some people had to run uspl 3 times in a row for it to work. Did you wait a while on white screen before giving up? I guess you are on 02 wm5 at the moment if not flash to that and try again. If you are do a hard reset and try again - few times in a row.
OK looks like USPL doesnt work for me!
Everytime I ran it under WM5 i still had 1.25.0000 and then i upgraded ROM to O2 WM6 and now everytime I run USPL it stays at 3.04.0000.
It doesnt do anything after the white screen ..... just sits there like a duck!
With so many ppl having succesfully done this surely someone can be a Wizard of Orbit??
fahdp said:
Thing is when i run USPL and it gets to 100%, all i get is a white blank screen and nothing happens. So i have to reset the device.
Then i try and run the BB4 etc install and get to 3% before it conks out.
When I get the white screen ... what else can i do??
Click to expand...
Click to collapse
Had same problem. Dont reset the phone but just if you see only the black screen, run the USPL update.
I have an orbit and uspl flashed first time from wm5 and wm6 - is yours usa orbit? If you really cant run uspl then it will need cid unlock from imei check - it costs but you have permenant cid unlock so you need not worry again.

HELP ... Bootloader Screen is all I get

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.

HTC Diamond bricked?

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!

Categories

Resources