Related
25 minutes looking on the forums didn't really help me with what i need help with. i flashed Crossbow from a CID unlocked ex Faria aku 3.3 XDA Mini S, and i couldn't get signal, or play any sounds, in addition...the phone was extremely slow! i read that this is due to my device being CID unlocked, when i should flash an operator rom (to reCID lock it), then continue with the upgrade. surely this contradicts what threads say about phones MUST be CID unlocked otherwise you'll brick your phone etc. how can i get Crossbow Underground to be stable, and run normally?
also, my Faria 8mb aku 3.3 has moments of being lightning fast, and long periods of being stupidly slow (i.e. 10 seconds to unlock the phone from standby), does anybody know why it does this, and what i could do to fix it. Hard reset didn't do anything, and it's only getting slower. if i just left the phone after it being really slow, normally it will sort itself out and run fast again, after half an hour or so. the processor is set to default (not that this makes a difference as 260mhz doesn't speed it up), and i only have the normal programs on there.
any help atall will be greatly appreciated,
thanks,
thepolice
thepolice said:
25 minutes looking on the forums didn't really help me with what i need help with. i flashed Crossbow from a CID unlocked ex Faria aku 3.3 XDA Mini S, and i couldn't get signal, or play any sounds, in addition...the phone was extremely slow! i read that this is due to my device being CID unlocked, when i should flash an operator rom (to reCID lock it), then continue with the upgrade. surely this contradicts what threads say about phones MUST be CID unlocked otherwise you'll brick your phone etc. how can i get Crossbow Underground to be stable, and run normally?
Click to expand...
Click to collapse
I'm running Most Beautiful Edition so can't comment on Underground specific issues, but I don't think anyone has said that you should re-CID Lock your phone (actually I don't think you can, but thats another topic ). What I have suggested (and seen others suggest) is to always go back to an official ship ROM before upgrading. I went from Faria's AKU 3.3 straight to MBE and had all sorts of weird issues (active sync problems, Outlook complaining the calendar was corrupt, and more). I was frustrated and reflashed the TMobile 2.26 rom to go back to Faria's then it hit me I didn't do this before doing WM6. So I put MBE back on, and its worked great since. So I'm a firm believer now to take the extra time to move back to a shipped official ROM before loading a new custom one..
...the processor is set to default (not that this makes a difference as 260mhz doesn't speed it up)
Click to expand...
Click to collapse
Use batterystatus (for me I'm using .04.200 and not the beta 1.x one as it caused me issues) and have that overclock your device. If you can't see a difference, then I wonder if you have some hardware issue with your Wizard. I'm now running overclocked at 260Mhz via BatteryStatus and its been very stable and there is a definite improvement.
mfrazzz said:
I'm running Most Beautiful Edition so can't comment on Underground specific issues
Click to expand...
Click to collapse
Thanks, that was really useful
I can't run Most Beautiful, when i flashed it, it wouldn't boot atall. But this may be because i didn't flash the shipped rom before, is this likely?
When i flash the shipped rom, upon boot, the spl and ipl go back to 2.26...surely this means it's relocked. Should i flash the t-mobile rom instead? or wont this work as it wasn't the shipped rom - if that makes sense.
anyway, thanks so much for you help, you've explained a lot to me
thepolice said:
I can't run Most Beautiful, when i flashed it, it wouldn't boot atall. But this may be because i didn't flash the shipped rom before, is this likely?
Click to expand...
Click to collapse
Thats possible. can't say its likely, but its possible
When i flash the shipped rom, upon boot, the spl and ipl go back to 2.26...surely this means it's relocked. Should i flash the t-mobile rom instead? or wont this work as it wasn't the shipped rom - if that makes sense.
Click to expand...
Click to collapse
Yes when you flash the shipped rom the IPL/SPL will change to what comes with that ROM (for TMobile one it will be 2.26). That does NOT relock it. Only if you go back to a 1.x ROM will you have to deal with being relocked.
Example, I'm on a Cingular 8125. If I tried (out of the box) to flash the TMobile 2.26, it wouldn't work as its CID Locked. But after doing the CID Unlock, I can now flash TMobile, QTEK, O2, or whatever because it is CID Unlocked. And as long as I stay with 2.x roms, I can switch around as much as I want (it does't get relocked).
So definetly go back to an official shipped rom (and Tmobile 2.26 is the highly recommended one by about everyone), and then flash whichever custom rom you want to try. Its extra work to reflash an official rom but I think it removes problems some people see when they go from custom to custom.
thank you very much, i got my phone sorted now, and everything is clear to me.
It's okay now...got it sorted
Just curious, but what are you running now? And what worked for you?
mfrazzz said:
Just curious, but what are you running now? And what worked for you?
Click to expand...
Click to collapse
Right now i'm running the Faria 8mb. i was running Crossbow Underground, but i didn't see the point in going to all the efforts to fix the keyboard problems (because then I'd have to fix the predictive text) as the Faria Crossbow rom is coming out soon, i'll just get that...can't wait!
All the problems i had seemed to be becuase i wasn't flashing the shipped rom before the new one.
Hy everyone. I tried installing NBD 8.1, 8.2, and 8.3 on my phone today and it goes well. It says it has finished updating my phone and then when I start my phone, it says its being customized and I see everything being installed. After it is done installing, it resets. When it resets it is just the same old thing. It looks the same way it did when I first bought the phone. Im using a Cingular 8125 if it makes any difference. Thanks.
Your phone is still CID locked.
Follow this tutorial to unlock it, and follow the steps closely.
i wouldnt follow that tutorial just yet. You still need to give us a little more information like if your wizard is a G3/G4. You can only cidunlock your wizard if it is a G3.
I wonder why newbies are always told to CID unlock...
Shelltool works perfectly for flashing new OS (I flashed my CID locked G4 at least 6 times) and there should not be any risk of bricking the phone...
Mirek
mirekluza said:
I wonder why newbies are always told to CID unlock...
Shelltool works perfectly for flashing new OS (I flashed my CID locked G4 at least 6 times) and there should not be any risk of bricking the phone...
Mirek
Click to expand...
Click to collapse
I agree! I'd been flashing my G4 phone from about 5 months ago with different ROMs (almost continuously)... ShellTool is the best tool that I tried to flash ROMs without risk.
Cheers!
mirekluza said:
I wonder why newbies are always told to CID unlock...
Shelltool works perfectly for flashing new OS (I flashed my CID locked G4 at least 6 times) and there should not be any risk of bricking the phone...
Mirek
Click to expand...
Click to collapse
nobody bothers to read anymore and dont know what the search link looks like. The just jump on the bandwagon. But its true i had a hard time following some instructions but i got through it.
Really??
I used shelltool 2 times without problem, but then i get the 1 time a message - flashing done after 8 minutes and the flash wasnt really on the phone. Since then i use RUU (which is in the love wizard rom package) and it works for me.
Today i tried flashing nbd 8.3 to faria aku 3.3 and other faria rom with aku 4. In both casec the flashing stoped at 99% and i had to reflash it with nbd rom.
The flash didnt end , cause i have cid-locked phone?? I would like to have a newer aku(i have 2.3). HELP
I used Shelltool to install the rom I had. It finished after about ten minutes, and then I hard reset my device.
Whenever I start my phone up now it just hangs on the Cingular start up screen and this is what it says.
IPL 2.25
SPL 2.25
GSM 02.25.11
OS 6.6.6.666
Any idea what went wrong or if there is any way to fix this?
Thanks
Are you using Vista?
Nope. I used Windows XP Pro.
I had the same problem with shelltool on xp pro sp2. Get the phone in bootloader mode and flash again. Maybe with RUU , which is in the wizard love rom package. Just replace the .nkb file (rom file) to one u want.
I don't like this topic name. It should be: "I don't know how to install new rom"
A few advices from long time shelltool user
(I used it to flash "faria real thing", several version of "crossbow reloaded", "xda mobile", "pandora", "wrcx3"). I am on a locked G4 phone.
a) I always start by flashing the original ROM of my provider (in my case T-Mobile CZ) in normal way. This may not be a needed, but I read that it is *recommended*to flash your provider's ROM to have some stable base. It takes about 10 minutes or so.
b) Afterwards I flash using shelltool (see shelltool documentation how it is done)
Possible problems with shelltool
a) It does not end and the flashed phone seems to be frozen (clock is not updated etc.):
No problem, flash is done. After 30 minutes from the flash start just take your phone, do the hard reset and everything will work ok.
This (shelltool not ending) happens often, but as I said - it is no problem.
b) The wrong flash
Either the shelltool is interrupted prematurely or it the phone freezes during restart afterwards.
No problem, just reflash your provider's ROM in normal way and try again shelltool.
This happens only very rarely and I never went through this more than once.
Conclusion
Since the shelltool is limited to flashing only OS, you should not ever brick your phone in this way... The most you can do is to screw up your OS - which can be quickly recovered by flashing the official ROM from your provider.
Flashing by normal way is more dangerous: if you flash a locked phone with the ROM containing more than just OS, you can easily brick your phone (if you flash ROM just with the OS you will wonder that nothing has changed - at least this is like I understand it).
Mirek
zoki said:
I don't like this topic name. It should be: "I don't know how to install new rom"
Click to expand...
Click to collapse
I have to agree with you Zoki. Has nothing to do with your ROM.
zoki said:
I don't like this topic name. It should be: "I don't know how to install new rom"
Click to expand...
Click to collapse
I'm sorry. I didn't mean to offend you or anything. I just thought I did it the right way the first time and that something went wrong but not on my part because I followed directions doing it. I'm not saying anything bad about the rom. Sorry!!
I'll try to do it with the RUU then. Thanks a lot.
I was trying to follow the many different ways to unlock, Hard SPL, and flash a new ROM but this is just way over my head. I think I may have screwed up my phone. I've been reading for 4 hours and I'm just throughly confused (this was so much easier on th Artemis!). I downloaded the jumpSPL1.56-KAS, ran it from the phone (not the storage card). Then I ran Kaiser-HardSPL-3.56 and that seemed to work fine. Then I tried to run step 1 of the KaiserUnlocker and now it will only show me the AT&T boot screen and nothing else after that. What did I do wrong?
I'm trying to unlock the phone so I can use it on T-Mobile USA and flash a new ROM. I've flashed ROMS before but I just never realized how involved this process was on other devices.
And yes, I can get to the boot loader screen.
shawndh said:
I was trying to follow the many different ways to unlock, Hard SPL, and flash a new ROM but this is just way over my head. I think I may have screwed up my phone. I've been reading for 4 hours and I'm just throughly confused (this was so much easier on th Artemis!). I downloaded the jumpSPL1.56-KAS, ran it from the phone (not the storage card). Then I ran Kaiser-HardSPL-3.56 and that seemed to work fine. Then I tried to run step 1 of the KaiserUnlocker and now it will only show me the AT&T boot screen and nothing else after that. What did I do wrong?
I'm trying to unlock the phone so I can use it on T-Mobile USA and flash a new ROM. I've flashed ROMS before but I just never realized how involved this process was on other devices.
And yes, I can get to the boot loader screen.
Click to expand...
Click to collapse
Ick...this sounds like one of a couple of things...either you really screwed it up (btw, even "really screwed up" has been known to be fixable thanks to the super awesome folks here on XDA Devs) or it's a simple fix. My first suggestion would be to put it back into bootloader (just hold the usualy bootloader buttons and stick the stylus up in the Reset hole OR take the batter out and put it back in, your choice I think) and try rerunning everything EXCEPT the KasierUnlocker (btw, dont quote me but I would almost swear KaiserUnlocker needed a special radio flashed in order to properly work...you may wanna head back to that thread and check it out. I unlocked mine with it and I can about guarantee I had a special radio...) and see if it fixes anything OR find a compatible radio and reflash it (well, first off...get it into bootloader and tell us what the bootloader says on it)
Anyways, first things first would be to see what the bootloader is showing and then work from there. Sounds like a little bug so don't freak out too bad. If you think flashing these babies are hard then you really didnt try flashing G4 versions of the Wizard =P I totally bricked one because it was the pesky G4s and I didn't realize it at the time (complete newbness lol) So yeah, Kaiser's are a LOVELY change for me =] I've flashed mine countless times and loved it since the moment I got it! =D
But yeah, gimme info! =]
Did you use WM6.1 or WM6.0 to unlock the phone? Put in boot loader and flash orginal WM6.0 ROM as the other user suggested. You should be able to flash it if it is not a brick.
If it doesn't work you can use mtty to recover your phone, the needed information you'll find in the Kaiser Wiki.
Hope it helps
I just had this exact problem.
Use the EXE included in the tutorial to flash any windows 6.1 ROM from the bootloader via USB, and you will boot again.
HTCOmega said:
Ick...this sounds like one of a couple of things...either you really screwed it up (btw, even "really screwed up" has been known to be fixable thanks to the super awesome folks here on XDA Devs) or it's a simple fix. My first suggestion would be to put it back into bootloader (just hold the usualy bootloader buttons and stick the stylus up in the Reset hole OR take the batter out and put it back in, your choice I think) and try rerunning everything EXCEPT the KasierUnlocker (btw, dont quote me but I would almost swear KaiserUnlocker needed a special radio flashed in order to properly work...you may wanna head back to that thread and check it out. I unlocked mine with it and I can about guarantee I had a special radio...) and see if it fixes anything OR find a compatible radio and reflash it (well, first off...get it into bootloader and tell us what the bootloader says on it)
Anyways, first things first would be to see what the bootloader is showing and then work from there. Sounds like a little bug so don't freak out too bad. If you think flashing these babies are hard then you really didnt try flashing G4 versions of the Wizard =P I totally bricked one because it was the pesky G4s and I didn't realize it at the time (complete newbness lol) So yeah, Kaiser's are a LOVELY change for me =] I've flashed mine countless times and loved it since the moment I got it! =D
But yeah, gimme info! =]
Click to expand...
Click to collapse
I know. The crazy thing is that I've successfully flashed a G3 and a G4 Wizard and I still find this confusing.
When I go to the boot loader screen I have:
KAIS1*0
SPL-3.56.Hard
CPLD-8
When I reset the device normally I get:
R 1.27.12.11
G 22.45.88.07H
D 1.62.00.00
I didn't try to flash any other ROMS to unlock it. I just went with the hard SPL and then tried the Unlock tool. The phone is stock.
Thanx for the replys. I reflashed the original ROM and now it's working again. This is what I have now:
When I go to the boot loader screen I have:
KAIS1*0
SPL-3.56.Hard
CPLD-8
Now when I reset the device normally I get:
ROM version 1.62.502.0
Radio version 1.27.14.09
Protocal version is 22.45.88.07H
Device info:
Windows Mobil 6
CE OS 5.2.1622 (Build 18128.0.4.4)
Can I go strait to a SIM unlocker and then flash a new ROM?
Well you've got HardSPL 3.56 flashed to it.
Why do you need to sim unlock it? Sim unlocking is not neccesary to flash one of the many Roms avaliable for the Kaiser/Tilt.
Once it's got HardSPL flashed, you're free to flash any type of rom onto it
shawndh said:
I was trying to follow the many different ways to unlock, Hard SPL, and flash a new ROM but this is just way over my head. I think I may have screwed up my phone. I've been reading for 4 hours and I'm just throughly confused (this was so much easier on th Artemis!). I downloaded the jumpSPL1.56-KAS, ran it from the phone (not the storage card). Then I ran Kaiser-HardSPL-3.56 and that seemed to work fine. Then I tried to run step 1 of the KaiserUnlocker and now it will only show me the AT&T boot screen and nothing else after that. What did I do wrong?
I'm trying to unlock the phone so I can use it on T-Mobile USA and flash a new ROM. I've flashed ROMS before but I just never realized how involved this process was on other devices.
And yes, I can get to the boot loader screen.
Click to expand...
Click to collapse
A couple of things:
1) The Kaiser-Unlocker only works on 1.xx hardspl's, so you'll have to put one of those on first.
2) You do need to install the patched radio before you run it.
3) You'll need to flash a compatible radio afterward too, or else your device might not boot all the way.
4) Next time please post these questions in the thread for the unlocker you are using. It makes it much simpler for everyone.
stuff said:
Well you've got HardSPL 3.56 flashed to it.
Why do you need to sim unlock it? Sim unlocking is not neccesary to flash one of the many Roms avaliable for the Kaiser/Tilt.
Once it's got HardSPL flashed, you're free to flash any type of rom onto it
Click to expand...
Click to collapse
But HardSPL 3.56 doesn't SIM unlock the phone from what I understand. I need to use it with T-Mobile SIM. So I need to chenge to a 1.XX Hard SPL to do this?
So I guess I went wrong with flashing 3.56 first and not 1.1
Then I need to patch the radio
Run the unlocker
rinstall the radio
Then flash the ROM
Problem I have now is that I can't seem to go back down to a lower SPL version.
shawndh said:
But HardSPL 3.56 doesn't SIM unlock the phone from what I understand. I need to use it with T-Mobile SIM. So I need to chenge to a 1.XX Hard SPL to do this?
Click to expand...
Click to collapse
You need to read the instructions carefully, and ask questions in that thread. All the experts in unlocking will be there to help you.
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....
Ok, I'm kind of at my wits end. I've already bricked a Sprint Snap, and I'm trying to get HARD to display on my tri-color instead of 0000 before I try ookba's rom again.
But I can't. I've done everything correct. SDA application unlocker - auto.bat from the JockyW thread, JumpSPL and boot Rom Update Utility. Every time it goes to a 100%, but once I reboot and then hold volume down I still get
CEDA200
SPL-0.34.0000
MicroP-Willow#C (LED) v58B.
No luck. I've tried hard resetting my phone with brand new factory settings (my old 6.1 was heavily modded). I've tried XP and Vista. No luck. When I confirm jumpSPL my screen goes black. Then I run RomUpdateUtility while the screen is black. Is that right? Please advise me, I'd love to have 6.5 on my snap.
Please use the correct version of Hard SPL, suitable for your phone!(S 511). Above all use Jump SPL (depending on your SPL version) and follow the prompts in the DOS window. Just press space bar. On your phone, screen will turn black this is NORMAL!Then free to interact in any way with the phone and without disconnecting the phone from the PC will need to run Hard SPL.Again attention, according to your platform (S511).After all this if all is well you should install the favorite ROM .
Good Luck!!!
i have followed these steps
I have started the romupdateutility with the black screen and it completes to a 100 percent. however my tricolor splash screen doesn't change.
Strange ...Something is wrong there.Try on another PC, make sure Active Sync or Windows Mobile Device Center is working properly.But most importantly try another JumpSPL and HardSPL, those you have now may have errors or can be corrupt file.Had happened to me with my old Diamond.
what is supposed to happen?
The .0000 should say .HARD if the flash was successful right? If a phone is HARDSPL then it won't change after a hard reset right? I really can't get this to work... is there a newer jumpspl I should try? Everytime RomUpdateUtility completes with the black screen my phone reboots and nothing has changed
DAMN
I just bricked my second snap by trying a different version of JumpSPL, really really upsetting. I can't believe I did that again, all I wanted was my device to be HardSPL and now its a paperweight. UGHHHH no phone certainly isn't better than stock 6.1... I'm probably done trying to 6.5 this damn thing. I'm going to replace it and never mess with it again. Thank you for trying to help.
Sorry man, really sorry. And I agree with you, 6.5 is nothing better than 6.1 and I think so.I have 6.5 and do not see an obvious improvement or an addition to performance.Perhaps a higher consumption of resources.I think it depends on preference.In your case maybe not everything is lost.Read this very very very carefully: "Flashing and Unbricking your Maple" by Ookba.Even if they refer to Maple, can help you.Good luck!
yay!
After getting a new s511, I attempted this for the third time
Well, It worked like magic. .Hard is now visible on my tri-color screen. SO!
Now I can flash the ROM? Do I just turn my phone on to its homescreen and plug it in to run RomUpdateUtility? Any other precautions I should take?
@Johny, thanks so much man for all of your help i appreciate it.
Yes, theoretically should work without problems now.Turn on the phone then start running RomUpdateUtility. If Hard is visible, you are insured in case of failure to update the ROM. In my case...I did not succeed the first time this.Even if I did HardSPL, I could not install 6.5, an error occurs...All they have resolved JumpSPL.If you have problems post here. Good luck!
Johnny_BV said:
Yes, theoretically should work without problems now.Turn on the phone then start running RomUpdateUtility. If Hard is visible, you are insured in case of failure to update the ROM. In my case...I did not succeed the first time this.Even if I did HardSPL, I could not install 6.5, an error occurs...All they have resolved JumpSPL.If you have problems post here. Good luck!
Click to expand...
Click to collapse
salut Johnny . putem vorbi de telefon?
drc38 said:
salut Johnny . putem vorbi de telefon?
Click to expand...
Click to collapse
Please provide an english translation, since this is a english forum
Device Help
I have a HTC Snap 511 from a Wireless Carrier in Puerto Rico it works just as fine as Sprint's. Actually its the same phone under another carrier. I tried Updating the rom i got lucky it boots 6.5 but i downloaded the wrong rom because its for a GSM phone not CDMA now its asking me for SIM and i can't updated to the one it goes ( that i downloaded sometime later )... Tri-Color Says:
CEDA200
SPL-0.39.0000
MicroP-Willow#C (LED) v 58B
i tried putting the s511 Sprint ROM but says at upgrade communication error.
I think its because im downgrading roms?
CEDA is 2.00.XXXX
WILL is 1.50.XXX
Any comments are aprreciated.
PS-
SIM Failure
The SIM card is missing or is not valid.You can still make emergency calls if your service providers supports it.
--##_- 240x320 Fun! -_##--
Which Un RAR arhivator complete work on this device (Snap S511) ???
I`m test all and not working nothing. WM 6.5 and WM 6.1
Not description for Icons in the SYSTEM(WM 6.5) menu... Baaaaad.