Related
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!
I have an unusual problem with my oem att tilt running SPL-1.56.0000 (according to the bootloader screen).
The ROM is somehow corrupted in that it will not boot past the giant ATT logo and coordinates (?) screen. I have been having some trouble with the device, but this is a new occurrence not related to anything I did. I have never reflashed the ROM, and because it is in a current hosed state I cannot run hardspl on the device.
I have tried reloading many of the "ATT OEM" ROMs I can find, but they all return "Invalid ID" error the ROM uploader I believe because the versions don't match.
Is there any way to reflash the ROM and bootloader on the device without having first run hardspl? Am I SOL?
Thanks
RK
Did you try going to tri-color first then flashing a stock tilt rom?
Dude, I have the same problem...
I bought the tilt 2 weeks when I was in a business travel in the US and came back to Argentina... I'm kind of screwed about the warranty 'cause I don't think I'll go again so soon to the US...
Is there anybody who can help us with this?
The very diference is that (At the ATT start up Logo screen) the bottom line says D 1.57.00.00 instead of D 1.56.00.00.
Tried everything... soft reset, hard reset... and so on...
The thing is that at some point I think I can get to the phone in some way since if I turn on the phone keeping pressed the camera button and enter in the rom loader screen I can get comm to the phone using mtty (As pof explained to do for "Un-brick" the phone (In the case you got a bad flashing) in this thread...
So, please If anybody have any idea it would be great!
I still have a little hope, because it's like there is some kind of communication between the phone and the computer...
Thanks in advance to any help.
A.
both of you...
Check my sticky thread for reverting back to the stock tilt ROM and SPL...
all you really need from there is the Stock ATT ROM... download it!
Put your phone in Bootloader (shouldn't be too difficult by the sounds of it)
Install the stock ATT ROM.
If this doesn't work try extracting the downloaded ROM (using WinRAR or similar) then just run the ROMUpdateUtility.exe
Then you might want to consider installing HardSPL... the default download should work for the 1.56 guy. The 1.57 guy will need to download jwocky2001's whitescreen fix (check the stickies).
Good Luck!
I am at the tricolor screen and I have tried the instructions on your thread (thanks very much for making it so easy). However, it says invalid vendor ID after loading 1%; the device automatically reboots and reverts back to the ATT screen until I place it back into the tricolor bootloader again. I thought this was because the version I'm running is 1.56 and I could only find two original OEM ATT ROMs, neither was 1.56 and both failed.
BTW I couldn't do the part about hardspl and running the kaiser program on the device for obvious reasons, but I could get the kaiserruu program to recognize the device, another ROM and attempt to upload it.
Any other thoughts? Do I really need the exact same ATT OEM ROM as what is on the device or is something else wrong?
Thanks again
RK
I searched but could not find an instance like this..
While flashing:
RUU_Kaiser_CINGULAR_WWE_3.57.502.2_radio_sign_25.88.40.05_1.65.21.18_Ship.exe
The bar hangs at 13% and then I get the boot loader screen. It reads the normal SPL info, Jocky's 3.29 so on, and I see the RUUNBH in the upper right hand screen.
HOWEVER, it then reverts to the flash progress bar and finishes the flash with no other issues. Phone boots and RUUNBH is gone.
Does this mean I have a bad sector or block? Don't have this problem with any other ROM's, just this one. Should I be worried?
Thanks!
EDIT: By the way, I tried flashing the ROM twice with identical results.
xconradx said:
I searched but could not find an instance like this..
While flashing:
RUU_Kaiser_CINGULAR_WWE_3.57.502.2_radio_sign_25.88.40.05_1.65.21.18_Ship.exe
The bar hangs at 13% and then I get the boot loader screen. It reads the normal SPL info, Jocky's 3.29 so on, and I see the RUUNBH in the upper right hand screen.
HOWEVER, it then reverts to the flash progress bar and finishes the flash with no other issues. Phone boots and RUUNBH is gone.
Does this mean I have a bad sector or block? Don't have this problem with any other ROM's, just this one. Should I be worried?
Thanks!
EDIT: By the way, I tried flashing the ROM twice with identical results.
Click to expand...
Click to collapse
It's normal stuff. I get this aswell.
Cool, anyone else experienced this?
Also, I know that the famed RUUNBH is common, but what does it actually mean? Rom Update Utility NBH? What is NBH?
Thanks kristoff!
xconradx said:
Cool, anyone else experienced this?
Also, I know that the famed RUUNBH is common, but what does it actually mean? Rom Update Utility NBH? What is NBH?
Thanks kristoff!
Click to expand...
Click to collapse
NBH is the file format you are flashing to the device, so I guess it is something to do with that, maybe it sets this flag when flashing and removes it when done, if it gets interupted the flag gets left.
Thats my best guess, and I have been known to guess right before
To avoid this, try the Hard SPL range by cmonex.
Dave
The AT&T ROM is behaving this way because it contains an updated SPL (3.56), and that is the first thing it flashes. The phone then reboots and resumes the ROM and Radio flash.
This is normal behavior.
Yep, just a flag telling you "Hey I'm using the RUU (Rom Update Utility) to flas a .nbh (Firmware) file.
The only time this is not normal is if the flag isn't reset after flashing. This can easy be reset in that case however with a terminal emulator.
NotATreoFan said:
The AT&T ROM is behaving this way because it contains an updated SPL (3.56), and that is the first thing it flashes. The phone then reboots and resumes the ROM and Radio flash.
This is normal behavior.
Click to expand...
Click to collapse
Ok, this leads to another problem. I am running SPL 3.29. I have tried numerously to upgrade to 3.56. I always get error 262, some sort of communication a minute or so after the progress bar comes up.
I know I should post in that thread, but maybe you can shed some light here?
xconradx said:
Ok, this leads to another problem. I am running SPL 3.29. I have tried numerously to upgrade to 3.56. I always get error 262, some sort of communication a minute or so after the progress bar comes up.
I know I should post in that thread, but maybe you can shed some light here?
Click to expand...
Click to collapse
EDIT: If I could follow directions I would probably be paid more at work too. I got it to work AFTER I removed my SD card.
Thanks for everyone's help!
LOL....
I got that message without reading this thread and thought....AW SH!T...I just bricked the sucker...
Really glad that in my daze I didn't disconnect the USB cable because it started up again. Had I disconnected it, probably woulda bricked!
Same here
I did not have this "RUNNBH" on tilt screen before (while upgrading). Will it be possible to remove this I feel this sis causing freezes in my device.
[email protected]
Hello guys...
Iam not new, and i have already flashed my first(it was wasted not by my fault)KAISER, it was one year ago and i did it with HARDSLPv1, and lately added some new roms cooked by sakajati(respect)...
Yesterday i bought new one(but one year old) so i tried to flash him as well, i have used HARDSPL 1.93, and then i tried to put Sakajati"s 4th feb ROM, but i come across one big trouble, everytime i try to put it on i encounter the same RUU error:
ERROR [262] : UPDATE ERROR
This error occurs during the CE ROM code upgrade process. Solution: If this happens, you can just soft-reset the device and run RUU again. The update process will then continue. Note: At this stage, the Wince is destroyed; instead, it is in upgrade mode.
what to do...????
i am very afraid that i destroyed my Kaiser...???
what it means that Wince is destroyed...
Please help me, i am desperate...
Iam not new,
Click to expand...
Click to collapse
But the solution could be found here (search)
If you see the tri color screen everythng is ok, just win mobile is destroyed. Try to flash a rom from your sd card
Thank you very much...
I hope it will work, i really did search for about an hour and tried to put rom on sevral times, but i didnt find nothing 100% secure, i dont want to indanger the unit any more that i did...
thanks again, i will try it tommorow morning at my job, thats where my SD card is...
)))
greganovak said:
Thank you very much...
I hope it will work, i really did search for about an hour and tried to put rom on sevral times, but i didnt find nothing 100% secure, i dont want to indanger the unit any more that i did...
thanks again, i will try it tommorow morning at my job, thats where my SD card is...
)))
Click to expand...
Click to collapse
Part of the problem is that 1.93 is a jump spl and should be used to upgrade to Hard spl 3.29 or 3.56, not as an spl on its own. You need to run jump spl 1.93 from your device and make sure you are connected to your computer, when you see the bootloader you need to unplug your USB, count to 10 and plug your USB back in then flash a hard spl to your phone! Again 1.93 is not a Hard Spl by itself, it is only a middle man to flash a Hard Spl.
I think the best would be to flash a stock rom at first, cause therefore you don't need an other bootloader. Then flash Hardspl (3.29 if you have a kaiser or 3.56 if you have a tilt) and then flash any rom you want
i obviusly have a lot to learn, mate how do I asses if I have TILT or KAISER, what is the main difference...
[email protected]: i have already DL the stock rom before i posted the tread, i hoped on that resolution if there were no answer...
in about 10 hours from now i will get my hands on my tilt/kaiser and hope to arranged the mess i done; I drop by in any case at that time and notify you about condition and my successes...
p.s.:sorry for my poor english...
greganovak said:
i obviusly have a lot to learn, mate how do I asses if I have TILT or KAISER, what is the main difference...
[email protected]: i have already DL the stock rom before i posted the tread, i hoped on that resolution if there were no answer...
in about 10 hours from now i will get my hands on my tilt/kaiser and hope to arranged the mess i done; I drop by in any case at that time and notify you about condition and my successes...
p.s.:sorry for my poor english...
Click to expand...
Click to collapse
It realy doesnt make that much of a difference, I have a tilt and I use 3.29 and I would recomend it to anyone over 3.56 so flash either one, they will both work! And your english is great so no need to say sorry!
greganovak said:
i obviusly have a lot to learn, mate how do I asses if I have TILT or KAISER, what is the main difference...
[email protected]: i have already DL the stock rom before i posted the tread, i hoped on that resolution if there were no answer...
in about 10 hours from now i will get my hands on my tilt/kaiser and hope to arranged the mess i done; I drop by in any case at that time and notify you about condition and my successes...
p.s.:sorry for my poor english...
Click to expand...
Click to collapse
A Tilt is a At$T branded Kaiser, a TyNT II is a HTC branded Kaiser. Tilt has a different keyboard and OEM rom., only differences. People say use 3.56 if you have a Tilt because that is an AT$T Spl, but I use 3.29 on My Tilt and it works great so it doesn't really matter.
hey...
nothing seems to work...
I have tried to put default rom dl from here: http://wiki.xda-developers.com/index.php?pagename=Kaiser_ROMs but the problem is that it is not bootable from SD, that has to be because the USB conection isnt on (i selected the 3.34.721.2) so i given up that way
Then i flashed the HARD spl 3.29(have kaiser) via SD steb by step first with this instruction: http://forum.xda-developers.com/showthread.php?t=433835; and it dint go through
so i tried with this instruction: http://forum.xda-developers.com/showthread.php?t=420683
it didnt work either, they are the same I know(noticed later);
So problem is that i stuck at WHITE screen that says "LOADING..."
nothig else...???
finally i manage to load/boot the htc rom from xda-wiki site, but i have to chose another one
I have tried to put default rom dl from here: http://wiki.xda-developers.com/index...me=Kaiser_ROMs but the problem is that it is not bootable from SD, that has to be because the USB conection isnt on (i selected the 3.34.721.2) so i given up that way
Click to expand...
Click to collapse
Hey man, nice to see that your device rewakes, you can flash every rom from sd card, simply rename the nbh file to kaisimg.nbh than restart into bootloader and it will automatically take the one from the card
Unfortanly, althought i would like you to be right, you are not. When i tried to do it via SD, i stuck at white screen saying LOADING...(blue) and nothih further... and i tried also the Cmonex_s Hard SPL3.29_SD which also stucks at same screen
So now (after updatig with default rom) that i have basicly normal working device i startet from the top. Using @mskip"[email protected] tutorial called: Flasing your first rom (for noobs); it all goes well, till i start to update RUU(sakajati 4 feb) if it matters, and i tried both (spls 1.56 and 1.93), it stops updatig at 17% and notrhin else then works just puting back the HTC default rom from wikiXDA side(thank god for that)
i am thinking of MTTY, although i dont know what it does guys here almoste all say it fix bad rom flash, but i am not sure if thats my main problem, i rahter think it has something with spls...
if someone has some good advice i will be very grateful...
greganovak said:
Unfortanly, althought i would like you to be right, you are not. When i tried to do it via SD, i stuck at white screen saying LOADING...(blue) and nothih further... and i tried also the Cmonex_s Hard SPL3.29_SD which also stucks at same screen
So now (after updatig with default rom) that i have basicly normal working device i startet from the top. Using @mskip"[email protected] tutorial called: Flasing your first rom (for noobs); it all goes well, till i start to update RUU(sakajati 4 feb) if it matters, and i tried both (spls 1.56 and 1.93), it stops updatig at 17% and notrhin else then works just puting back the HTC default rom from wikiXDA side(thank god for that)
i am thinking of MTTY, although i dont know what it does guys here almoste all say it fix bad rom flash, but i am not sure if thats my main problem, i rahter think it has something with spls...
if someone has some good advice i will be very grateful...
Click to expand...
Click to collapse
Hi,
I couldn´t flash my Kaiser via SD at the first time and tried something that worked.
The SD´s are formatted in Fat16 usually, try to format to Fat32... It seems like a stupid thing, but worked for me.
Reagards and good luck.
SD must be formated FAT32, to work, also I sugest a smal card, 512 or something like that, SHDC usual doesn't work
I have 1GB SD and its not shdc, so thats ok.and i have done it right now, like you two guys said so i formated it with FAT32 but still no succes.
I guess that this tree lines in red/green/blue screen arent right:
KAIS130
SPL-3.02.0000
CPLD-8
i thing this SPL has to da something to do with all this mess a have done
I have flashed a couple of roms( i had three devices) and i flashed a few for my friends and all was OK till now, and i dont know what else to do...
greganovak said:
I have 1GB SD and its not shdc, so thats ok.and i have done it right now, like you two guys said so i formated it with FAT32 but still no succes.
I guess that this tree lines in red/green/blue screen arent right:
KAIS130
SPL-3.02.0000
CPLD-8
i thing this SPL has to da something to do with all this mess a have done
I have flashed a couple of roms( i had three devices) and i flashed a few for my friends and all was OK till now, and i dont know what else to do...
Click to expand...
Click to collapse
Yes, you still have a stock spl on there. It needs to be hard spl'd before you flash anymore. Check out the stickies at the top of the forum.
hi again...
Well, I respect the "rules" of forum, thats why i wouldnt ask for insructions that are already written(thanks for the authors) with that i mean stickys, because i read them, almost all...
But I still tried once again, and I came across the same thing, i stuck at 17% when loading RUU or if i choose the VIA SD i stuck at white screen with blue text saying (LOADING...)...
nothing else helps than loading the dafault ROM by HTC... as i already said once again...
if i manage to solve the problem i will be in touch; what do you thing about MTTY
Edit 1:
i have done everything as it says in the instruction, and just like some of you "replyed" me...
but i always stuck at 17%when loading RUU, when i flash it with SPL 1.56 or 1.93 i never get stuck at white screen it always apeare the mentioned SPLs nimbers and some other text in yellow but when i then load RUUs i stuck at excatly 17% nothing less nothing more
edit 2:
yupi....yupi
i made it...
http://forum.xda-developers.com/showthread.php?t=354061 here is my lifesavior...
those instruction were the one that helped my problem...
it is very nice to ba a part of this community....