Crazy diamond, trapped bootloader, rom and flash not works - Touch Diamond, MDA Compact IV General

Hi, i have a serious problem with my diamond...if someone knows how to fix it, i will be a lot of gratefull.
I have htc diamond movistar, with cooked rom 2.0.3 - BsB 1.1, during 4 mounths, 0 problems.
Yesterday, the diamond has reset 2 times...ok...but the third was the last. It died. Not turn on...never.
I can't revive them in any way. Do not start with any of my original 2 batteries .. It does not recognize the network stream, or the PC, ActiveSync does not recognize ... soft reset and hard reset doesnt rapair anything...
It starts 1 of 50 times, and when he makes, I only can put the bootloader mode, is the only thing i can do. And the bootloader recognice the usb mode. So i should can flash...no?
To send the diamond to technical service, i have to put the original rom and hardspl, but i can´t. All times that i try to flash, the process fail.
I had try to put the original spl (1.93), and the process arrives to 100%, but after the reset, bootloader says that i have 1.24 hardspl yet !!
And when i try to put any rom, cooked or original, always fails the process at diferent percentages...15%, 26%...65%... Always the same error, [302], connection fails.
So... is difficult that the diamond turn on, the rom doesn´t work and no pass of MOVISTAR logo...the bootloader works, but all the flashings that i try, fails.
¿¿How i can put the original spl and original rom to send to technical service??
THANKSSSS!!!

Related

qtek 9100 resets during boot

I tried to use imei-check to remove my cid lock but have run into problems.
first time I tried it things seemed to go fine but it never passed stage 1 and I was adviced on the computer screen that I should disconnect, reset computer and device and try again.
I tried but now the unlocker would report "communications errors" shortly after it had detected the phone as a Wizard.
Now the phone wouldn't boot (it resets itself after I get the Qtek logo screen with IPL (2.17) SPL (2.17) and OS (2.17.7.1))
I tried flashing with an original rom from Qtek (2.17.7.1) and it went well. I again tried the unlocker. exactly the same as the first time, and as the second time after that.
I again tried flashing with the original rom but now RUU wont put the rom on due to error 294 (invalid vendor ID).
the phone is still CID locked, the original rom wont install and it wont boot...
what the f*** should I do?
edit: after getting it to boot I find that gsm radio is not working, the phone does not charge etc.
Something went VERY wrong during the last flashing.
Edit: There seems to be an issue with my hardware. I dont believe that using imei-check software has anything to do with this. the flash-rom chip seems to be damaged.

Cannot Flash Original Rom

First off, anyone on this forum who has contributed anything, I am have the deepest respect for, and my favorites will get donations as soon as I have money. Ok enough a$$ kissing.
So here is my problem:
I flashed it's right's TNT 6.1 19919 after hardspling. After many problems, like pseudo-hard resetting (turning off, losing all but 6% battery, and changing the date back to what it was originally i.e. 1/27/06) while in a phone call and doing the same while using the wifi, i hard reset and still the same problems occurred. so I undid the hardspl, so now i am back to 2.25.001 in the bootloader but when i connect it to the computer (winxp) to flash the original rom (cingular 2.25) it freezes at 91%. If anyone has had this problem occur or knows the solution as to get ANY rom back on it, IT would be greatly appreciated.
Also after doing some reading I tried to flash wizard love 2.26 to it and that freezes at about 50-60%. so I am stuck and it is really annoying.
Full 8 hour charge, restart computer, different usb port. Same happens: Error 302 Update Error
Hum... maybe when you reCID locked it, you put a CID that's not for that official ROM you're trying to flash. The misbehavior of the phone is due to the ROM you had, not the CID Unlock. If I'm not mistaken, you can hardSPL it again, from bootloader. Then you can try and flash any other ROM you wish. Give my ROM (WM5SE rev5 - if your phone can handle 240MHz - or rev4) a go, after you have CID Unlocked your phone.
My phone can take up to 273 but, all the roms i flashed were g4 safe.... because the ipl spl never changed and i checked them in shell tool . it gives me a update error 302 which wizard love documentation says that the "phone needs a new rom code" which implies that it needs to be taken to cingular, and i dont think i can lie that well. how would one "accidentally" put their phone into bootloader?
theblackhandx said:
First off, anyone on this forum who has contributed anything, I am have the deepest respect for, and my favorites will get donations as soon as I have money. Ok enough a$$ kissing.
So here is my problem:
I flashed it's right's TNT 6.1 19919 after hardspling. After many problems, like pseudo-hard resetting (turning off, losing all but 6% battery, and changing the date back to what it was originally i.e. 1/27/06) while in a phone call and doing the same while using the wifi, i hard reset and still the same problems occurred. so I undid the hardspl, so now i am back to 2.25.001 in the bootloader but when i connect it to the computer (winxp) to flash the original rom (cingular 2.25) it freezes at 91%. If anyone has had this problem occur or knows the solution as to get ANY rom back on it, IT would be greatly appreciated.
Also after doing some reading I tried to flash wizard love 2.26 to it and that freezes at about 50-60%. so I am stuck and it is really annoying.
Full 8 hour charge, restart computer, different usb port. Same happens: Error 302 Update Error
Click to expand...
Click to collapse
You have posted present IPL/SPL 2.25.001,is it 2.25.001 or .0001 ?
As you removed 'HardSPL',did you reflash the appropriate IPL/SPL regarding your phones official bootloader IPL/SPL...?
You shud do the 'HardSPL' again and either do the removal of HardSPL again correctly as instructed in the sticky ' How to remove HardSPL' or Flash any other Rom to recover.
Cheers!
no it was 2.25.001 just a typo. i think i will try these suggestions when i get home and i will post my findings.

Freeze on boot screen

Hello,
Today my vibrator goes mad, so I decided to send my phone back (I still have the warranty).
In order to proceed, I have to put back the official SFR ROM, and luckily I found this link on the wiki : ftp://xda:[email protected]/Uploads/Trinity/SFR_S300+_ROM_French_1.23.163.2_Only_OS.rar
So I did a little backup of all my data, I take off the memory card, and I started the installation.
But at 9%, it bugs. Hopefully, the ROMUpdateUtility display a message that I have to put off and put in the USB cable, and retry the installation. Its seems that works, because the transfer was complete and the phone reboot automatically .
But when the phone reboot, it display the classical boot screen SFR Bonjour, show some numbers (M 05 - B 05 - D 1.23 - R 1.50.08.11 - G 32.83.7020.20h) and when this numbers disappear the phone freeze.
I've try to wait half an hour, but the SFR boot screen stay, and the phone didn't respond to anything (I've try to put the power cable, and the LED set on only if the phone is off). I have to put off the battery to turn off the phone.
If somebody could help me, please!
And excuse me if I made any mistake, english is not my native language.
I have the same issue......
I have the same issue, my SPVM700 just sits on the initial splash screen after I tried to re-flash it to the original Orange ROM [as I too had to return it for a warranty repair]. I used Mozzer's Orange ROM [http://forum.xda-developers.com/showthread.php?t=309959] to restore it - the procedure looked the same as with other ROMs I had successfully loaded but it was only when I tried to restore the official MNO ROM that my Trinity bricked.
I can access the bootloader screen [TRIN100 IPL-0.50, SPL-9.99CP] and can flash the device, where the progress bar always reaches 100% on the PC and the PDA and then the PDA automatically reboots, however, it does not advance past the splash screen.
I have tried the Hard-SPL fix [ http://forum.xda-developers.com/showthread.php?t=299659 ] and then re-flashed the device with other ROMs that I had tried previously [Schaps, AX3L, HTC Official WM5 P3600 ROM etc..] but still get no joy - is there something that I should have done prior to re-loading the original ROM that I have missed and is my Trinity now forever a brick?
you've presumably tried a hard reset? but it's not written above so i thought i'd just check.. (pressing two soft reset buttons and pushing the stylus in the reset hole?)
Yes I did try a hard reset even though I didn't expect much from it as I had just replaced the ROM [effectively wiping the ROM and replacing it with a different ROM] and none seemed to boot. Once the device has started booting up, the only way to switch it off is to disconnect the battery [and the only way to switch it back on is to soft reset] so I am guessing there is a hardware issue caused by returning the device to the Original MNO build as this was the ROM upgrade that trashed the device - other ROMs tested prior to this had loaded successfully.
Sorry to bring this back but since the link is in Behemot's sig, it is not resolved yet. Have you guys loaded SSPL before flashing? If you haven't, the OEM Rom won't boot with HardSPL. Try flashing another custom Rom and use this method before flashing the Shipped Rom.
Good luck.
ask ilos for original SFR rom or search for extenue SFR rom. or contact me by personal message and give me your mail i have the SFR ROM without radio ROM (you can get the radio on this forum)...
Sorry, I've forget to update this thread...
So, for me the only solution was to bring back the device to an SFR store (it is still under warranty).
I believed they would reproach me that the RADIO was not the original one or something like that, but no. They didn't make any remark and send my device back with an official SFR ROM.
The only thing is that they take more than a month instead of the traditional two weeks to fix it.
So all is ok for me.
I hope you will solve your problem

HELP!! I think my Wizard is a Paper weight! Bricked!

HELP PLEASE!!
Ok so i think i bricked my wizard!
I have the t-mobile MDA wm5 unlocked g3.
I've flashed it to the WM6 Rom and everything had been working well, except there was no MMS feature on the phone at all which sucked! . My girlfriend thought it would be better if she did the "windows mobile update" icon feature that was on the phone to speed up the phone....She downloaded the updates & my phone shut off!! When it rebooted everything seemed normal...
1st.
T-mobile screen
IPL 2.26
SPL 2.26
GSM 02.25.11
OS 10.1.0.811
-Then i get the green windows mobile splash screen, but after i get an error message!!
*Device Authentication*
“Device authentication failure. Please contact the product manufacturer. For reference, please provide your device ID.
3563820017905901 38000050bf3f5173”
Ive tried to boot in safe mode to try & flash my phone again but for sum reason my computer wont recognize my phone is plugged in! What do i need to do?!? Please help, any help is thankful!
is not a bricked wizard men
easy men easy... but please tell to your girl dont push everything that she dont nderstands... Everybody knows that upgrade official is only for original OS like windows XP or VISTA..
Firs of all
Put your Wizard on bootloaders mode... plug in via usb the PC Active sync wont recognize your phone.. then run the original shipped Stock ROM and then your Coocked rom...
But if the PC at the same time you place your Device on Bootloaders and plug it via USB... shows a pop up message that said Windows cant recognize your device or unknown device or something... Restart your Pc... Hard reset your PDA... and replug your Device as I said it before... if not check your USB cable maybe a broken cable failure...
IF NOT?????!!!!!!!! then Use another PC with XP!!!!!
If it still on his not reconized message you are in serious problem but your girfriend Too...
Good luck
Easy..."Device Authentication failure" is caused by your ROM. Just flashing another custom ROM and the message should go away.
I'm surprised that the chef that made your WM6 rom left the Windows Update feature in there, it was bound to crash a cooked rom, since the update service never worked properly anyway.
I'm sure flashing another rom will resolve this.
yeah, flash the rom (you might want to try WizFlo 20273 v6.1.1.3 - i'm on it, and loving it). heck, you can even do a hard reset and that would probably resolve it.

Trouble with reset

I dont' know if this is the problem of onkolog rom or just the way i flash my phone.
First i use the old rom of davideuck Davideuck_V-7, CE OS 5.2.20769 on 29,March . I then got trouble with battery drained with this rom when i used SPB 3.0.
I try to update to new 6.1 rom of onkolog on 1, May
This is what i did.
My phone was on and connected to my PC. I then run HardSPL 1.56 successfully.
The phone was on again and i run the wrapper file in the same folder with onkolog rom. It run smoothly but when it recognized my O2 network it told me to be restarted after 5 seconds and when the "htc" words appear my phone hang.
i need to do a soft reset and this time it worked.
I then tried to install flip it. It required to restart after install and this time i got hang again.
I install htc Tweak and use it soft reset, some times it worked sometimes my phone hang and i need to do soft reset.
The same problem appear when i used A-A reset software.
I then decided to go back to early version of onkolog 6.1 rom (used older version of hspl) on 1-April and still got the same problem.
I tried to reflash with uspl but still stucked with usb driver.
Can anybody tell me how to show this problem . I really like the idea of onkolog but maybe he is too busy to answer me.

Categories

Resources