Related
I am a little confused. I have been trying to get WM6 on my T-mobile Wizard and actually got TNT 1.1 loaded and was working fine. I found that I could no longer view my contacts. The page would appear and then as quickly as it appeared it disappeared.
So I figured, I at least got it this far. I will just reload this rom and see if perhaps something did load right. Well after the reload. The phone boots up to the splash screen with IPL\SPL numbers and just sits. NOTHING.
I left it there for like 2 hours and still nothing. But I can still get into the BootLoader.
My questions to you gurus is:
Is the phone fubared?
Can I do some kind of master reset?
Why would it tell me "Invalid Vendor ID" when trying to flash the orginal T-mobile rom?
Are there any tools that can help me out? Paid\free?
Please help!!! Seriously! Please HELP!!!
Very much appreciated.
Thanks
Drunknasty said:
I am a little confused. I have been trying to get WM6 on my T-mobile Wizard and actually got TNT 1.1 loaded and was working fine. I found that I could no longer view my contacts. The page would appear and then as quickly as it appeared it disappeared.
So I figured, I at least got it this far. I will just reload this rom and see if perhaps something did load right. Well after the reload. The phone boots up to the splash screen with IPL\SPL numbers and just sits. NOTHING.
I left it there for like 2 hours and still nothing. But I can still get into the BootLoader.
My questions to you gurus is:
Is the phone fubared?
Can I do some kind of master reset?
Why would it tell me "Invalid Vendor ID" when trying to flash the orginal T-mobile rom?
Are there any tools that can help me out? Paid\free?
Please help!!! Seriously! Please HELP!!!
Very much appreciated.
Thanks
Click to expand...
Click to collapse
if your device is G3, unlocking is required to flash any rom, before upgrade your device, it is recommended to flash an official WM5.0 rom (in your case T-Mobile rom) with IPL and SPL 2.xx then flash again.
in general there are many probabilities for your issue.
((Where is TNT1.1?? did you mean 1.0?? ))
My Bad meant 1.0
So to get it straight.... I will need to unlock my phone each time?
Oh and to correct myself again, when flashing with the T-mobile ROM it says UPGRADE ONLY. And the read me file says its the wrong RUU. But it is the same file from Tmobile I used when I first got the phone. But I will try again.
Are there any other suggestions?
You need to read the "how to flash" sticky.
I did. I am not any expert or anything but I believe the phone is unlocked already since I once had WM6 on my phone. The real issue I am having is that it wont boot past the splash screen after flashing.
And that is true when re following the steps in guide. After flashing to the button rom it will not boot past the splash screen.
Try another ROM.
Sounds like you need the "Wizard Love" rom. I dont have the link handy but I am sure someone else does.
Drunknasty said:
I did. I am not any expert or anything but I believe the phone is unlocked already since I once had WM6 on my phone. The real issue I am having is that it wont boot past the splash screen after flashing.
And that is true when re following the steps in guide. After flashing to the button rom it will not boot past the splash screen.
Click to expand...
Click to collapse
Already got it. Thanks I am trying to load it now. But the only thing is that the last time it failed and I can understand what the error says. I know the number is 300 but can read the language.
But I will let you guys know when this load completes.
Thanks again for all the assistance.
No worky worky. The load completed and then boots the splash screen shows and then stays there.
Any ideas?
Try to remove the battery and let it out for at least half an hour. Then put it back in and see what it does then.
I thought the same thing too. So when it got done last night, out of frustration, I removed the battery and left it there to wait on when I get off work today. I will report back on what happens.
Again I would like to thank you guys for helping me. I really do appreciate it!
STEP 1 install the original manufacturer ROM
T-mobile UK
http://www.tm-phonedownloads.com/download_manager_mda_vario.html
T-mobile US
http://www.t-mobile.com/wmupgrade/
Search for the original rom for any other
instructions on how to use the original rom can be found here
http://support.t-mobile.com/knowbase/root/public/tm23294.htm?&A2L.SERVICE=AboutUpgrading
Put it in the bootloader mode.. ( three color screens )
hope this helps..
cheers
Praneet
Ok I did that and it gave me ERROR 296: UPGRADE ONLY
Then it tells me that the NBF file cannot be used for my PDA Phone. Please get newer NBF file.
Is there any way I can get the Tmobile splash and IPL\SPL number back to original, it doesnt need to boot all the way into WCE but atleast show the same numbers and splash during boot up?
Or any other way to get this thing to work?
Thanks guys
BTW it is a HTC Wizard from T-mobile.
If you are getting an error 300 you need a newer rom update utility, and regardless if your phone is a G3 or G4 it needs to be unlocked before you flash any rom.. LOAD a OFFICIAL cingular ROM onto your device before going any further, then unlock your phone either via www.imei-check.com or through some of the tools offered here...
Which one should I down load from Cingular? Even though I have a Tmobile phone?
what ipl and spl are you using and what radio are you using. Just post all the numbers from the bootloader
As soon as I get home, I will post them.
Thanks
Ipl 1.01
Spl 3.08
Thanks
Drunknasty said:
Ipl 1.01
Spl 3.08
Thanks
Click to expand...
Click to collapse
uh oh. someone tell me if I'm wrong, but I think this is bad. it's the result of flashing a g4 with g3 or the other way around... keep searching, and good luck.
flash the original t-mobile rom. your phone doesn't appear to be unlocked. good luck
Yup, first time disaster. I followed the guide here, installed the necessary Cert_SPCS.cab/EnableRapi.cab files, rebooted, and then started the Shelltool update...only to belatedly notice a notification screen on my 8125 asking if I wanted to run one of the programs.
I said yes, but even though the update completed, my 8125 is stuck at the boot screen.
Worse, I reset the 8125 into boot loader mode and tried to flash back, only to get a 300 error. I tried to use an updated RUU and ROM set, only to get 264 or 274 errors.
Any hope here, or did I just manage to brick my 8125?
Are you trying to flash an offical rom while in bootloader mode?
Yup. Tried to flash the official 8125 ROM from HTC. Tried to flash a number of different ROMs, actually - I always get a 264 or 274 "Communication" error, except for the official ROMs, which gave me a 300 error.
Not looking good here...
this has helped me with bad flashes
http://forum.xda-developers.com/showthread.php?t=298613
Been there, done that. In fact, that was the thread I first read. I've tried to flash to Wizard_love, but I get a 264 error.
From what I've read in the RUU Docs, a 264/274 error is rare, and fatal in this case. It's not looking good...
(On the bright side, the iPhone release has created a flood of used 8125's on eBay )
I did a little searching for you,
http://www.google.com/advanced_search?q=+site:http://forum.xda-developers.com&hl=en&lr=&as_qdr=all
I read some were how to flash a phone that has errors, I couldn't find that post. Maybe someone else here knows of that post You didn't mention is your phone G3 or G4 I did find this post, doesn't look good. I hope someone has a better answer for you, good luck.
http://forum.xda-developers.com/showthread.php?t=304456
Another post I found for you.
http://forum.xda-developers.com/showthread.php?t=294107
Thanks for the links, unfortunately it's still a no-joy situation here.
This is a G4 Cingular 8125 - sorry I forgot to mention that earlier.
ActiveSync was set to allow USB connections, and I've tried using the official RUU update utility from HTC for the Cingular 8125 with the 8125 in Bootloader (3 color) mode - I get an error 274.
I then tried the Wizard_Love version - error 264.
Next, the MB WM6 ROM - error 300.
Finally, in desperation I try the Shelltool app method again, even though I can't copy over the necessary bootloaders. It hangs up mid-flash, as expected.
Can't go forward, can't go back. Looks like I've got myself a brick...sigh...
upd: ahh, it is g4.....
so ignore whats below
it IS NOT brick ,trust me i had exactly same prob while testing cooked ROM - all yyou need is to download chinese rescue ROM, THEN flash it by its RUU, then RUU wLOVE, then flash ..anythin(g3)...and then flash IPLSPL, as it will be unequal, usually.
its unclear, why RUU cant do flash sometimes, but i believe, that you do not have brick( i had same situation 3 times = 14 flashes..;/ but machine is alive !)
of course, you may have same errors with chinese..if connecting, reconnecting etc is not working, then...use any rescue ROM closest to original, old hogs. check your firewall, and remember - SR device before EACH try - oterwise you surely will have 300 error - 1 try for each reset, no more.
chinese rescue ROM(you MUST flash wlove after that 1), or shelltool will lead you to...3bars.;/
http://pda.oleyek.com/ROM/Others/RUU_Prodigy_1070302_103_10703102_CMCC_CHS_Ship.exe
if its not working...maybe that 1..
http://rapidshare.com/files/29657481/RUU_TMobile_US_226102_22610105_022511_WWE_Ship_tmob_rom.exe
maybe other...
wizard love rescue ROM:
http://rapidshare.com/files/8651097/Wizard_Love_2.26.10.2_WWE_Novii_CF2.rar
Just a "happy ending" update:
Was just about to buy a new 8125 on eBay, when I gave it another try - hard reset the device twice in a row, then tried again to flash back to the original Cingular 8125 ROM -- it worked!
Then, in a fit of flashing madness, I went ahead and flashed one of Faria's latest WM6 sets -- and it worked as well!
So, not only don't I have brick, I actually got it upgraded. Whew...
pls help for flashing rom
pr0naLd said:
this has helped me with bad flashes
http://forum.xda-developers.com/showthread.php?t=298613
Click to expand...
Click to collapse
I have spent 24 hrs flashing my qtek 9100 sim free - i think it is the g4 as IPL IS 2.17 / SPL 2.17 NO ZEROES THOUGH . IT DOES SYNC BEYOND 99% AND THE HELP WINDOWS COMES OUT - IT GOES BACK TO THE BOOTLOADER SCREEN ( 3 - 4 LINES OF RED BLUE GREEN ). PLS HELP AS I AM DYING TO GET THE WM 6.0 ONTO MY WIZARD. thanks and appreciate.
[email protected]
BOWERS said:
I have spent 24 hrs flashing my qtek 9100 sim free - i think it is the g4 as IPL IS 2.17 / SPL 2.17 NO ZEROES THOUGH . IT DOES SYNC BEYOND 99% AND THE HELP WINDOWS COMES OUT - IT GOES BACK TO THE BOOTLOADER SCREEN ( 3 - 4 LINES OF RED BLUE GREEN ). PLS HELP AS I AM DYING TO GET THE WM 6.0 ONTO MY WIZARD. thanks and appreciate.
[email protected]
Click to expand...
Click to collapse
Kindly confirm its a G3 or G4 before flashing. This will help you out. http://forum.xda-developers.com/showthread.php?t=298613
wizard G4 boot ok but jump to B/L screen
its aliveeee its aliveeeeeeeeee
Hi everyone,
I think I may have bricked my Kaiser. I've been following some similar threads but nothing seems to be working to fix the problem.
I was going through the process to flash a new Rom, starting with installing HardSPL following this thread I was. I was having problems, I think because I have the 1.82 ROM version.
Finally, I thought I had HardSPL installed, so I continued to run KaiserCustomRUU.exe. This completed (jumped from 0% to 100%) very quickly. However, I reset my phone and it is now stuck in the tri-color bootloader screen
The screen has the says:
KAIS130
SPL-1.82.0000
CPLD-8
and has the letters RUUNBH in the top right corner.
I've tried removing the battery and resetting, but the phone always goes back to this screen. I've also tried running mtty, but without success. The command 'readconfig' returned a result 'Command error !!!'.
does anyone know of anything else I can try?
Small bit of good news: if I issue the command 'boot' using mtty, my phone boots into my original ROM successfully, with the mtty output:
InitDisplay: Display_Chip=1
No card inserted
OSSIReadBack ++
Read SI data from flash success
tail signature match
Checksum match
UserStorageSIPreload ++
It takes a long time to boot (like a couple of minutes), but it does eventually boots up fine. When I reset, I'm back at the tri-color screen though
If your at the tri-color screen, just reflash a new rom
Im not an expert but when its at the tri colour screen, try to flash Hard SPL again, it should pick it up and flash i believe.
If that goes through ok, then do the same to flash another ROM.
Again no expert at unbricking but its definately worth a try
japher said:
Small bit of good news: if I issue the command 'boot' using mtty, my phone boots into my original ROM successfully, with the mtty output:
InitDisplay: Display_Chip=1
No card inserted
OSSIReadBack ++
Read SI data from flash success
tail signature match
Checksum match
UserStorageSIPreload ++
It takes a long time to boot (like a couple of minutes), but it does eventually boots up fine. When I reset, I'm back at the tri-color screen though
Click to expand...
Click to collapse
Try this.
1.) Open ActiveSync and navigate to File > Connection Settings - Uncheck Allow USB connections.
2.) Download this ROM http://rapidshare.com/files/5781641...dio_sign_22.45.88.07_1.27.12.11_Ship.rar.html and flash it to your device.
That should work for you.
hi alltheway. thanks for the advice!
I don't want to sound ungrateful, but are you sure the above is safe? I just don't want to make a wrong step now and totally screw up the device (now that I can successfully do a manual boot using mtty).
I know you can't guarantee it but is this what others who are stuck in the bootloader have done?
japher said:
hi alltheway. thanks for the advice!
I don't want to sound ungrateful, but are you sure the above is safe? I just don't want to make a wrong step now and totally screw up the device (now that I can successfully do a manual boot using mtty).
I know you can't guarantee it but is this what others who are stuck in the bootloader have done?
Click to expand...
Click to collapse
I had this problem about 2 weeks ago.
I was flashing one of Dutty's Great ROMs and I lost power at the house and shut down my computer when I was 46% done.
I had the same RUUNBH in the top right hand corner. All I did to fix this was flash a factory shipped ROM like the one I provided to you and it worked great. No issue thus far.
Honestly I can't gurantee 100% if this will totally fix your problem but I am 95% sure.
Unless some other users have an answer for you I think this will be your best solution. Regardless of what you do you will have to flash to a new ROM anyways.
Also, I'm a bit dubious on whether i will be able to flash to that ROM. I don't think I have the right HardSPL installed to flash roms (see what my boot-loader screen says in the first post).
I'm no expert though.... obviously
Thanks for all the info alltheway. I'm too tired now (will probably f*ck the thing up even further! ), so I'll try flashing this tomorrow.
Here's some more info I've collected using mtty (my phone is an O2 XDA Stellar):
Code:
Cmd>info 2
HTCSO2___001¯JG±HTCE
Cmd>getdevinfo
GetDevInfo: Get CID OK
HTCSKAIS1300O__0HTCE
New Thread
Read this:
http://forum.xda-developers.com/showthread.php?t=355910
Hi tqm. I've been following that post but as far as I can tell there is no solution there yet.
From what I can tell from that thread (and others), the only way stop the phone booting to the tri-color screen (in RUUNBH mode) is to flash with a ROM that matches the vendor. I think because I haven't been able to install HardSPL properly, my phone's version of SSPL will only load O2 ROMs (could be wrong here, but that's the picture I'm building ). Unfortunately no-one seems to have extracted the ROM from an XDA Stellar :\
I believe alltheway's solution above worked for him because he had HardSPL installed properly. He could load the stock ROM to fix the phone, because his SSPL version allowed different ROMs to be loaded. I'm not certain of this, and I'll probably try his suggested solution when I get home today... but I'm not too confident.
If only there was an mtty command to just get the phone out of 'RUUNBH' mode. I've seen the command 'task 8' mentioned on here, but it doesn't work when I try it. Does anyone know of a list of mtty commands for the Kaiser anywhere?
Definitely flash the original ROM, it will get your device to the default HTC shipped state.
Then sync phone with ActiveSync, install HardSPL again and then flash custom ROM.
I remember i had the same issue but the original rom is a lifesaver
You mean the original HTC ROM? or the original O2 ROM? (what my phone originally came with)
If I don't have one of the HardSPL versions posted on the forums (I believe they never installed properly, which is what caused all my problems I think), will I still be able to flash the stock HTC ROM:
RUU_Kaiser_HTC_WWE_1.56.405.5_radio_sign_22.45.88.07_1.27.12.11_Ship.exe
Basically my questions is: is this stock HTC ROM flash-able to ALL kaisers? (even without downloading/installing HardSPL from the forums)
If not (i.e. I can't flash even the stock HTC ROM), is it expected that if I can't successfully install HardSPL, my Kaiser will only accept O2 ROMS?
japher said:
You mean the original HTC ROM? or the original O2 ROM? (what my phone originally came with)
If I don't have one of the HardSPL versions posted on the forums (I believe they never installed properly, which is what caused all my problems I think), will I still be able to flash the stock HTC ROM:
RUU_Kaiser_HTC_WWE_1.56.405.5_radio_sign_22.45.88.07_1.27.12.11_Ship.exe
Basically my questions is: is this stock HTC ROM flash-able to ALL kaisers? (even without downloading/installing HardSPL from the forums)
If not (i.e. I can't flash even the stock HTC ROM), is it expected that if I can't successfully install HardSPL, my Kaiser will only accept O2 ROMS?
Click to expand...
Click to collapse
IMHO the HTC stock ROM should work even without HardSPL, at least for me it worked fine... but just for sure have your O2 stock ROM by hand.
jaso2005 said:
Im not an expert but when its at the tri colour screen, try to flash Hard SPL again, it should pick it up and flash i believe.
Click to expand...
Click to collapse
I don't thinks there's a way to flash HardSPL on tri-color scrren so far, coz activesync cannot connected to computer
the best way is trying to find the phone's offcial ship rom to flash
No luck trying to flash with the stock HTC ROM:
RUU_Kaiser_HTC_WWE_1.56.405.5_radio_sign_22.45.88.07_1.27.12.11_Ship.exe
After getting to 1%, it reports an error:
Error [294] : Invalid Vender Id
As suspected, looks like this will only accept an O2 ROM Will have to wait until one is available.
Did you try installing HardSPL and then reflashing?
the stock HTC rom will not load onto your kaiser simply because it is still CID locked to O2's CID code. You HAVE to find the O2 rom that your device came with or any O2 ROM and reflash that and you will be good to go. You may also try and flash HardSPL but I dont think its going to work. But remember have a friend or someone on the forum dump and rebuild the O2 rom for you and just reflash the OS.nb or ROM only no radio!
It is very simple to dump and rebuild a rom so if you have a friend that has a kaiser have him over for an hour and dump his
thats your only shot at this point.
URPREY said:
Did you try installing HardSPL and then reflashing?
Click to expand...
Click to collapse
My current ROM version is 1.82. I don't think installing HardSPL has been solved for this ROM version, which I think is where all my problems started. I have tried, but no version of HardSPL (that I've found) will install correctly.
austinsnyc said:
You HAVE to find the O2 rom that your device came with or any O2 ROM... just reflash the OS.nb or ROM only no radio!
Click to expand...
Click to collapse
Thanks for the reply austinsnyc, this is what I'm hoping to do now, I'm watching this thread 'Has anyone dumped the o2 Stellar rom yet ?' closely Maybe I should reconstruct the ROM myself, I'm just a bit worried about arsing that up as well I'd rather someone experienced reconstructed and verified the ROM (on a phone that isn't already messed up).
Out of interest, would you be able to give me a succinct explanation of what is actually wrong with my phone at present? As far as I can tell, the only problem is that the boot-loader is stuck in RUUNBH mode. Has part of the ROM on the phone actually been destroyed?
I'm assuming right now that the point of flashing the O2 ROM is just to make the phone 'finish' a flash and get out of RUUNBH mode. Or is it actually to re-instate something that has been lost?
If it is to reinstate something that's at present lost, is this data definitely part of the os.nb?
If it's just to get the boot-loader out of RUUNBH mode, I'm REALLY gutted that there isn't just a mtty command to do this
Oh yeah, and perceptivepixel.com Ace!
Hi,
Was changing the ROM on my Kaiser, using JUMPspl as I had got the white screen using Hardspl. During the upgrade got an error at about 18%, went through the recovery procedure only to get back to the Bootloader screen with the screen saying
SPL-1.93.0000
I think it should say something different here!
At the moment can only get the the tri-colour bootloader screen with usb at the bottom.
Please any help would be much appreaciated.
Thanks
If you are at the tri-color bootloader screen, reflash a ROM.
that's where the process starts at anyhow,the bootscreen.
But doesn't the SPL have to be either Hardspl or jumpSPL.
I have tried to do the rom update again but sticks on 0% and gives error 262
Alemaker said:
If you are at the tri-color bootloader screen, reflash a ROM.
that's where the process starts at anyhow,the bootscreen.
Click to expand...
Click to collapse
Not advisable if he has the default SPL still though which by the number appearing at the tri col screen it appears to be the case.
Try doing a hard reset and see if it boots into the original ROM then at least you will find out if it is bricked or not, however, i'm not sure it will work based on the fact you got part way through in the first place.
Hold down the keys directly next to the Send and End (green and Red) Hold in the stylus and keep them all held untill you get a screen telling you to press the green (send) key.
Tried the hard reset, takes me back into the bootloader. Any other ideas?
Hmm... ok then.... you are pretty much looking at a very expensive paperweight at this moment in time then.
Look at this thread...it "may" (i'm not promising anything but it may point you in the right direction) help you out. Let us know how it goes.
http://forum.xda-developers.com/showthread.php?t=361612&highlight=bricked
cmcmill01 said:
Hi,
Was changing the ROM on my Kaiser, using JUMPspl as I had got the white screen using Hardspl. During the upgrade got an error at about 18%, went through the recovery procedure only to get back to the Bootloader screen with the screen saying
SPL-1.93.0000
I think it should say something different here!
At the moment can only get the the tri-colour bootloader screen with usb at the bottom.
Please any help would be much appreaciated.
Thanks
Click to expand...
Click to collapse
Hate to joint the parade, but the exact same thing happened here - 18% now stuck at 1.93.0000
For anyone else reading this BEFORE flashing a new ROM please read, read and read again EVERYTHING related to flashing on this site, wikis and wherever else you can get info.
Another idea for you. Search around here for how to flash from an SD card that may solve the issue out for you. As previously noted though....READ READ READ and be 110% certain you understand what you are doing before you do anything.
http://forum.xda-developers.com/showthread.php?t=276963&highlight=stuck+bootloader
details some info for a Wizard, should it be the same for a Kaiser?
Will Mtty get me any further?
MTTY will at least give you a USB connection to the device it is worth a shot given your current situation.
There is hope!
I did a clean reboot of my PC and disabled my antivirus (avast) and was able to sucessfully reflash the new 1.62 rom (released from ATT site today).
Thanks will try the new 1.62 rom.
What commands can you use with MTTY?
tried the At&t rom gives me an error on the vendor id. Will try a HTC rom
I have tried multiple roms and they all give me the same error Error 294:Invalid Vender ID
Any ideas
Am starting to get worried because if the misses finds out that I have bricked the new phone, I am up to my neck i it.
If you are stuck in boot loader & would like some help via MSN Messenger, please PM me or look for me on MSM messenger at [email protected]. I will be available to help later this evening or tomorrow morning.
I have most of the files to fix these issues & can use MSN fileshare folders to help you.
Good chance that you can be up again in a matter of minutes
cmcmill01 said:
I have tried multiple roms and they all give me the same error Error 294:Invalid Vender ID
Any ideas
Am starting to get worried because if the misses finds out that I have bricked the new phone, I am up to my neck i it.
Click to expand...
Click to collapse
Invalid Vendor I.D. is cuz it's locked.
Had the exact issue myself and found a ATT ROM that will boot. It saved me bigtime, so I saved it. It's in one of the posts on one of the threads but I have the actual ROM, it'll overide that lock.- PM me if ya need it.
Got the same solution, Holy S**t about to have a heart attack. Tried nearly ever ROM out there, it was the Asia one that got me going.
Lesson learned: make sure you Hardspl after jumpspl.
Thanks for all the help folks
Glad ya got it fixed. One quick question?
Is your original ROM ATT or HTC ?
It is a HTC ROM. Done My Hardspl and got Sleuth v3.0 on it already
Happy days
Ok, so rapid short overview:
I tried to flash my O2 Stellar with the new HTC wm6.1 Kaiser ROM. The HTC website, for reasons unbeknowest to me would only give me the italian ROM, so I got the english variant off rapidshare.
Tried to flash, everything going well, until (at 0%) it turns around and says the ROM isn't compatible. I figure this requires some HardSPL goodness, but the installer for THAT jumps to 100% in seconds and doesn't seem to do much. Tried a soft SPL (SSPL-KAIS.. no white screen issue), hey-ho, presto! ROM tries to install.
...hangs at 15%, device reboots to the rainbow. Displays:
KAIS130
SPL-1.82.0000
CPLD-8
In the corner: RUUNBH
I've read ALL the other threads on this issue to try and restore the phone. I've tried ALL the O2 ROM dumps people have supplied (all two of them I could find) and every time it either had an error 262 (comms error) at 0%, or got as far as 1% or maybe 2% and then error 29-something (ROM not compatible/suitable for phone). O2 originals, cooked ROMs, HTC updated ROMs, ROMs for different vendors (those produced "wrong vendor" errors). NOTHING IS WORKING!! *tears out hair*
Apparently connecting with mtty and typing "boot" causes the device to try booting the original rom before the flash. I figure maybe I could boot it, copy the phone's OWN rom (c'mon, THAT rom would HAVE to work, right?!) and reflash it. So I fire up mtty, tell it to boot. But it doesn't. Instead, the screen sort of.. fades, between the SPL and pure white (looks almost like display is broken!) and mtty displays:
...OH. Ok, just tried again to copy mtty text and now it's booting.
This is what mtty displays as the phone boots:
Cmd>boot
InitDisplay: Display_Chip=1
No card inserted
OSSIReadBack ++
Read SI data from flash success
tail signature match
Checksum match
UserStorageSIPreload ++
Click to expand...
Click to collapse
Ok, focus of the thread changing, does anyone know if I could dump the ROM and flash it? I'm about to find out anyway but if someone knows this is foolish please let me know
Cheers, everyone.
Not looking good for you.
Sounds like you flashed a ROM into the SPL at a guess. You shouldn't flash anything except SPL's when you are in Soft SPL's (SSPL or JumpSPL).
Try PM'ing a guy called GSLEON3. He's a mod here and for a beer or two will probably set you right.
@GSLEON3, I really should figure some of this out someday myself. That way I can help rather than just pointing users to you.
EDIT:
You have tried the stuff in here first? http://forum.xda-developers.com/showthread.php?t=371154
Ta
Dave
DaveShaw said:
Sounds like you flashed a ROM into the SPL at a guess. You shouldn't flash anything except SPL's when you are in Soft SPL's (SSPL or JumpSPL).
Click to expand...
Click to collapse
In retrospect that's exactly what I did, yeah. Luckily the boot command worked on the fourth try (as above... guess perseverance gets results) and the phone worked enough for me to retry the HardSPL install (which worked). Then I was able to flash the O2 Stellar ROM found elsewhere in this forum which allowed the phone to boot normally again. THEN I was able to flash the english HTC Kaiser 6.1 WWE ROM.
That thread linking to MTTY techniques for formatting may have come in very useful, I will remember that one!
Go and "security unlock" your device now. It makes it almost unbrickable.
There is a app called FrankenKaiser which can re-install your SPL if you decide to format it (not that you would want to under normal circumstances)
Ta
Dave