Phone: UK T-mobile branded (vario IV) Raphael (GSM)
Been running custom roms & radios since i got it, had hard-spl on it.
The phone has a fault, so needs to be returned to factory settings for warrenty.
Problem 1)
The fault is with the mini-usb connector - so it is not possible to establish a data link to a pc
Problem 2)
Restoring everything!
I replaced the rom, radio, undid the security unlock & replaced the splash screen - all ok
Replacing the SPL i ran into problems (and then made it all worse!). I used a rebuilt spl 1.69 (what the phone shipped with) - which flashing from SD card loaded ok, but wouldnt overwrite the hard spl. (it loaded 100%, reset and still on hard spl)
I then read that the OliNex 1.90 warrenty restore spl was the only one which would overwite hard spl, but once i had done that, i could then write the correct spl back to the phone.
The 1.90 flashed from the sd card fine. Now the device starts on the boot loader saying i have an "Upgrade ROM code error Please try again"
However, it wont let me flash anything from the SD card now - i've tried the correct (1.69) spl, hard spl, the original (restored) rom and a HTC original rom.
The screen starts on the boot loader, then changes to the grey flashing screen where it says "loading..." (before flashing spl 1.90 this lasted less than 2 secs before saying what was on the sd card to flash) and never loads the nbh from the sd card to accept or not.
I've tried re-formatting the sd card again.
If anyone can help with this i'd be extremely greatful. But, please dont suggest anything from the pc - it simply wont connect (its not a windows, activesync or .net problem - the phone has a hardware fault)
my best guess is that the SPL you flashed locked the Carrier Code and you can't flash any rom besides one that matches the carrier code... or something went corrupt and the code is bad
Slight update:
It seems the HTC rom i tried in post 1 wasnt an original one, but rebuilt.
If i use a "new" and i guess signed NBH it passes the "loading..." screen onto "checking..." before telling me its not allowed.
Is there anyway of ID'ing the "expected" ID? and then is there a way of supplying that ID to a custom nbh?
Related
After flashing to a new ROM - WM6 the phone didn't boot the WM6 installation. Instead the old Orange logo appeared and entered in bootloader mode. I tried restoring the ROM from the original WM5 ROM (Orange RO) but it said Not Allowed. Ok... I flashed then a Cingular WM5 ROM and it worked. The initial logo changed and the OS booted. Immidiatly after the Windows Mobile splash I got a message "Data Crashes. Contact service center". If I remove the SIM card the message dissapears. I think something got screwed during the first flash since it didn't go through. I mention that I used the same ROM to flash another C600 phone and it works perfectly.
So... now I can boot up Cingular WM5 and play around with applications, but as soon as I insert my SIM card the Data Crashes message appears. It is my guess that some vital information such as the IMEI got screwed or a checksum somewhere is not checking.
Do you have any ideea how can I fix this?
You didn't superCID did you?
Sounds like you screwed over your GSM section, check with the SPV Services client if it can read your CID/SIM-Lock status
Phil
It was probably that... but to my knowledge I ran lokiwiz.bat.
No, SPV Services can't read the info from my phone - Illegal readZone attempt - RAPI init failed
stargatesg1 said:
It was probably that... but to my knowledge I ran lokiwiz.bat.
No, SPV Services can't read the info from my phone - Illegal readZone attempt - RAPI init failed
Click to expand...
Click to collapse
this means your phone was not application unlocked properly..
Right! Now spv-services works.
When clicking on the SIMLock Tools I get phone unlocked 00000000000000.
When clicking on the CID Tool I get:
Current CID: 0800313131313131313100000000000000000000000000000000000000000000
Technical details:
Now: 160 = 87554b2c510d9ed5da3c2b29dc9068653ce2b67d2065595e3ce2b67d2065595e, 160 = 4d0c1bd5d17f2fc4
Chg: 160 = 87554b2c510d9ed5da3c2b29dc9068653ce2b67d2065595e3ce2b67d2065595e, 160 = 4d0c1bd5d17f2fc4
cool. Enjoy!
Ok, now try flashing WM6GSMUPDATE and then a WM6 ROM and it SHOULD work
Phil
I flashed the WM6GSMUPDATE and then the WM6 ROM and it still doesn't work. After flashing the WM6 ROM I get returned to the old ROM's bitmap with Cingular logo and then the bootloader appears. Any ideeas? Can you give me a direct link to the latest WM6 ROM? Perhaps mine is somehow damaged although I succesfully flashed another C600.
Thanks.
Any ideas? Please?
Is there any way to fix the "Data crashes. Please contact your service center." problem using a HTC Tornado?
Htc Sda T-mobile Is Dead
MY PHONE IS DEAD WHEN POWER UP ONLY SEE T-MOBILE AND DEAD, THE PROBLEN I HAVE WHEN I try flash a WM6 ROM AND MY COMPUTER SHUT DOWN, NOW IS IMPOSIBILE TO ME TO MAKE A RESET OF THE PHONE YOU KNOW WHAT I NEED TO DO, THANK YOU AND I WAIT YOUR ANSWER
Can you get to the bootloader? If yes, then try flashing again.
What i’ve done is edited the IPL/SPL version from 3.08.0001 to 2.25.0001.
The reason for this is, I was building a ROM and accidently removed some USB registry entries or something else equally stupid, the result was the phone booted with no USB support.
This would be an easy fix if I wanted to dig through my crap to find a mini SD card to fix the registry or replace files.
However I decided to save myself the search and put the phone in boot loader mode, I figured I would just flash the original ROM back into the phone.
This did not work because the update utility can’t flash over the newer 3.08.0001 IPL/SPL.
Long story short with the edited version I can now flash back to the original ROM even if I waste the OS.
This is of course for soft SPL users not a replacement for hard SPL.
As always use at your own risk.
Is this 3.08 for G4 owners or could G4 owners always get 3.08?
Yes and yes.
The problem is if you flash 3.08.0001 to your phone and you mess up the OS you could have a useless brick.
The IPL/SPL 3.08.0001 wasn’t made for many devices.
This would only allow you to flash back to an OEM ROM, the OEM ROM would write over the top of IPL/SPL and they would have to be flashed back to the phone again.
For the last couple days I've been trying to reflash a TP2 I have lying around, and I've run into a host of problems. The most current problem is that while flashing from the SD the update will complete the bootloader, splash 1 and splash 2 and then fail at the Radio. I am stumped.
After the fail I've used mtty to reset the RUUNBH flag, and then tried again.
I've tried the factory signed roms for sprint and verizon with no difference. This device is security unlocked, but does not have HSPL (nor can I get HSPL to load via USB, and can not find an SD solution).
This hardware is an unbranded pre-production device (RHOD400), currently running SPL 0.63
Any ideas would be appreciated.
--fail screen--
00018003
RHODIMG.nbh - FAIL
BOOTLOADER - OK
SPLASH1 - OK
SPLASH2 - OK
RADIO -FAIL
OS -
Update Terminate
UPDATE FAIL
I've tried flashing a few different radios, but haven't had any success as of yet.
The Sprint, Verizon, and Telus shipped signed roms all get to the radio portion of the flash and fail.
Running the manual HSPL flash gets the device to show the percent complete screen, but it never goes beyond 0%.
Any direction would be appreciated. I'd love to get this unbranded device working again.
ur phone has to be HARD-SPL'd before flashing a radio i thought? if ur running SPL0.xx then i dont think it will work...
Hi there,
This article is very misleading...
h**p://theunlockr.com/2009/08/22/how-to-unroot-your-mytouch-3g/
I installed an ENG SPL and on my Vodafone 32B, all fine, flashed this rom as it stated it should work on almost any phone, it flashed ok BUT it put 1.33.0006 (Perfect SPL) and somehow my microsd got nuked. So I can start up the phone and get to the first time wizard, but because it's SIM locked to O2 I cannot login to google with my Vodafone SIM and therefore cannot install the flashrec.apk... I'm completely stuck. I can't goldcard as I can't get to ADB... I have nandroid backups and I'm borrowing someone elses microsd but I can't do flashboot (says now allowed) and I can't re-flash with SAPPIMG.zip it just keeps saying missing image or invalid.
Is there anything I can do?
*Slaps forehead very very hard*
Thanks,
Zas.
Ok, solved it:
h**p://***.mphone.co.uk/mms_wap_settings_vodafone.html
I added an APN for vodagone, got 3G then I could login. Hope this helps someone!
Zas.
I have a problem on my HTC HD7. I tried to flash the Rom and the process didn't go well.. Now on the bootmanager (colored screen) is not written serial or usb in the bottom and my PC doesn't recognise it in this mode, but zune recognise it when it's Turned on. How can I solve that problem?
P.S. I had another problem, my device rebooted automatically sometimes.. And it show me a message "Storage card did non work"
Thank you
Franci4396
Were you trying to flash a custom ROM? There's a very clear warning on the RSPL program not to use it on bootloader (SPL) versions 4 or greater. It sounds like you had version 4, based ont eh error you report...
The best way that I know of to fix the problem is GoldCard, though installing an official update CAB that includes a new bootloader (basically, any HTC firmware CAB for your phone) has been reported to work too.
The "storage card" error sounds like there's a problem with the internal microSD that the HD7 uses to store data. They come loose sometimes. You can replace that card, but getting to it without voiding your phone's warranty is difficult. If you're already out of warranty, though, it's not too hard if you have a set of small screwdrivers.
Can you give me a goldcard cab site??
For either GoldCard or a suitable update CAB (they are *not* the same thing), search the dev&hacking sub-forum. You'll need an OEM CAB that is for your phone and newer than your current firmware, if you want to go that route. Note, however, that it will lock your bootloader down even more. You can't flash right now anyhow, so unless you just want to flash a stock ROM I wouldn't bother fixing the bootloader that way.