A bunch of you guys know my kaiser is stuck in an infinite boot loop...
I have hardspl 3.56 on it currently. Worse mistake ever. It doesn't have most of the commands you use with mtty to recover...
From what I've seen, to replace the hardspl you have to run the softspl program from inside windows on the phone. And to get it back to factory spl you also have to run a program from windows on the phone. Is there no other way to do this? If we can install radios and stuff off of the SD card, is there anyway to embed an spl into that installer or another method? I think If I could get the spl replaced I could get my phone fixed using mtty.
Thanks,
nomb
the thing is spl has to load outside of the boot,oader screen its like trying to install windows while using it..your using the bootloader when you flash from sd therefore you cant update spl (which is the bootloader) from within itself you must be in the OS and load a softspl emulating a bootloader mode
Thats weird I swear I was able to put my hermes spl back to factory with it bricked. So then basically I might as well through my kaiser away?
nomb
talk with the mods..alltheway might help or even jocky they can help you unbrick your device and if not just take it to a att device support center and say you dont know what happened and youl get a new device (if your with att)
pazookie said:
talk with the mods..alltheway might help or even jocky they can help you unbrick your device and if not just take it to a att device support center and say you dont know what happened and youl get a new device (if your with att)
Click to expand...
Click to collapse
If you did the ATT warranty exchange since it is still under warranty, will they check to see if you changed the SPL on the device? And if they do what are the repercussions?
nomb
nomb said:
If you did the ATT warranty exchange since it is still under warranty, will they check to see if you changed the SPL on the device? And if they do what are the repercussions?
nomb
Click to expand...
Click to collapse
They probably check, and if they do, they will bill you $400, their "cost" for the Tilt.
NotATreoFan said:
They probably check, and if they do, they will bill you $400, their "cost" for the Tilt.
Click to expand...
Click to collapse
I read somewhere that the 3.56 spl was starting to be included with the official roms?
nomb
nomb said:
I read somewhere that the 3.56 spl was starting to be included with the official roms?
nomb
Click to expand...
Click to collapse
That may be true. But it will say something like SPL 3.56.0000; not SPL 3.56.Hard.
Do you have any commendations? I really feel like I should be able to get my phone working again.
Basically I restarted my phone and now it is stuck. I turns on and shows the ATT splash screen and then when it should show you all the versioning information in the bottom right corner it restarts itself and starts all over. I keeps doing this. I can get into the bootloader and have been able to flash roms onto it using usb. I thought I could recover using mtty and then found out that hardspl3.56 doesn't have the commands needed in it.
Any suggestions would be very much appreciated.
nomb
i sent in a device with hardspl and didnt get billed...ive heard they dont check spl..let alone the bootloader a long as it is a cingular rom then your good to go and if it cant boot then your set
Hmm, decisions, decisions...
Related
So, you've decided that your shiny new toy isn't very well setup by default. You flashed a ROM and lo and behold, you missed some instruction somewhere and now you think it's bricked.
Here's the good news:
It's not bricked!!
Bricked means that it's dead and it's in no way or shape recoverable.
There is still a chance. (As long as you didn't try to hardSPL with another Device's SPL...)
All you have to do is:
For the WING:
Hold the Camera button and WHILE holding it, soft reset the device (that means press the little hole above the memory card with the stylus.) That will bring you to the bootloader. Now download the appropiate RUU and run that program. A few minutes later and your new shiny toy is back to it's crappy OEM but working self!
I'll put in links for those who can't find them...
Here's tmobile's ROM.
WOW! That´s all??
Ok - then provide us a link to a XDA Terra RUU!!!!!!
hahahaha. Thanks for this help. Maby for some people it is usefull - but written 1000 times before.
ivanmmj said:
So, you've decided that your shiny new toy isn't very well setup by default. You flashed a ROM and lo and behold, you missed some instruction somewhere and now you think it's bricked.
Here's the good news:
It's not bricked!!
Bricked means that it's dead and it's in no way or shape recoverable.
There is still a chance. (As long as you didn't try to hardSPL with another Device's SPL...)
All you have to do is:
For the WING:
Hold the Camera button and WHILE holding it, soft reset the device (that means press the little hole above the memory card with the stylus.) That will bring you to the bootloader. Now download the appropiate RUU and run that program. A few minutes later and your new shiny toy is back to it's crappy OEM but working self!
I'll put in links for those who can't find them...
Click to expand...
Click to collapse
papamopps said:
WOW! That´s all??
Ok - then provide us a link to a XDA Terra RUU!!!!!!
hahahaha. Thanks for this help. Maby for some people it is usefull - but written 1000 times before.
Click to expand...
Click to collapse
I know it has been stated a million times. I'm just tired of the same question being asked over and over again and so here we are...
Too bad it'll be stated a million more times afterwards too.
falconeyez said:
Too bad it'll be stated a million more times afterwards too.
Click to expand...
Click to collapse
If we sticky it and threatened their lives if they don't read it... lol
ivanmmj said:
For the WING:
Hold the Camera button and WHILE holding it, soft reset the device (that means press the little hole above the memory card with the stylus.) That will bring you to the bootloader. Now download the appropiate RUU and run that program. A few minutes later and your new shiny toy is back to it's crappy OEM but working self!
Click to expand...
Click to collapse
It will not help!
ASerg said:
It will not help!
Click to expand...
Click to collapse
And we hold their pet's hostage?
ivanmmj said:
And we hold their pet's hostage?
Click to expand...
Click to collapse
Or better yet, tell them to send us their phones, then we "unbrick" them and sell them on eBay.
falconeyez said:
Or better yet, tell them to send us their phones, then we "unbrick" them and sell them on eBay.
Click to expand...
Click to collapse
Might work out, I get 10% of the over all sold
Ghostrider
Ghostrider said:
Might work out, I get 10% of the over all sold
Ghostrider
Click to expand...
Click to collapse
Fine, but I get 15% because it's my thread.
The instructions to do this are actually in my newbie thread. Which is a sticky.
TylerC161 said:
The instructions to do this are actually in my newbie thread. Which is a sticky.
Click to expand...
Click to collapse
I know, but most people don't search. I figured, maybe if it says "How to fix your bricked phone" on the title, they might get the idea.
It was actually done mostly as a joke...
help
I used the hardSPL from this thread..
http://forum.xda-developers.com/showthread.php?t=358225
It worked successfully and I was able to restart into WM6. Then I tried loading the TouchIT 4.4 and it installed cleanly with no errors. But when I went to restart it, my Wing just sits there at the CanonYang boot screen and never changes.
I tried using the steps here to restore the tmo default rom, but it after 1% on the progress bar, the screen goes blank and the CanonYang screen comes back. Is there anything I can do?
edit: I can get to the bootloader screen with the color bars. I'm not sure if this additional info will be of any help.
IPL 4.10.0002
SPL 4.70.Yang
gumbico said:
I used the hardSPL from this thread..
http://forum.xda-developers.com/showthread.php?t=358225
It worked successfully and I was able to restart into WM6. Then I tried loading the TouchIT 4.4 and it installed cleanly with no errors. But when I went to restart it, my Wing just sits there at the CanonYang boot screen and never changes.
I tried using the steps here to restore the tmo default rom, but it after 1% on the progress bar, the screen goes blank and the CanonYang screen comes back. Is there anything I can do?
edit: I can get to the bootloader screen with the color bars. I'm not sure if this additional info will be of any help.
IPL 4.10.0002
SPL 4.70.Yang
Click to expand...
Click to collapse
SPL 4.70.yang!!! your device is HARD-SPL!!
So going back to stockrom--> delete the SPL.nbh from EVERY RUU you are running.
Then it shouldn´t stop......
Big Thanks papa! That did the trick. My Wing is happy once again and running Open Touch. But I still want to give TouchIt another try.
And what if i cant find stock RUU mine came with some arabic keyboard and spl was 1.08 , thanks to Oli he didnt mention that SPL should be 4 or higher , so device is bricked since first Olis release and no way to find this arabic stock RUU.
Any Help ?????
Hitec
If the device had an spl of 1.08 prior to HardSPLing it, then you'll have to bring the device to your nearest repair center. There isn't a way around that. Oli doesn't know everything and that's the risk we take when we try new and experimental things that people create but have no way of testing. But, we live and learn. If it wasn't for that issue, you could always cook your own ROM and if the HardSPL was working, you could've easily flashed any ROM. But the keyboard wouldn't been wrong until you could find someone who had the correct keyboard and you extracted the ROM from it and cooked that keyboard driver into your ROM.
Oh noooo!!
Hi ivanmmj,
I used your guide to flashing my HTC P4350 at http://forum.xda-developers.com/showthread.php?t=358615.
It was in French and I wanted it in English. So I downloaded one of the official HTC ROMs "HTC_P4350_WWE_4.17.405.2_4.1.13.44_02.94.90_Ship.exe" assuming this was the English one because all the others couldn't have been.
I copied the "RUU_signed.nbh" from the above HTC ROM and put it into the RUU folder as instructed by yourguide (I didn't copy the SPL.nbh file). I then ran the herald-uspl.exe and everything went fine until the RUU utility stopped with the error "invalid vender ID".
The RUU exited without completing, now all I get when the device boots is the screen giving my IPL (1.08.001) and SPL (1.08.001). How do I flash another ROM from this state? I can't do it the "normal" way because ActiveSync can't see the device. When I try to use the RUU tool that comes with your tool, the progress bar shows then it says the tool can't be used with my device.
Someone please help!
foo_bar_baz said:
Hi ivanmmj,
I used your guide to flashing my HTC P4350 at http://forum.xda-developers.com/showthread.php?t=358615.
It was in French and I wanted it in English. So I downloaded one of the official HTC ROMs "HTC_P4350_WWE_4.17.405.2_4.1.13.44_02.94.90_Ship.exe" assuming this was the English one because all the others couldn't have been.
I copied the "RUU_signed.nbh" from the above HTC ROM and put it into the RUU folder as instructed by yourguide (I didn't copy the SPL.nbh file). I then ran the herald-uspl.exe and everything went fine until the RUU utility stopped with the error "invalid vender ID".
The RUU exited without completing, now all I get when the device boots is the screen giving my IPL (1.08.001) and SPL (1.08.001). How do I flash another ROM from this state? I can't do it the "normal" way because ActiveSync can't see the device. When I try to use the RUU tool that comes with your tool, the progress bar shows then it says the tool can't be used with my device.
Someone please help!
Click to expand...
Click to collapse
Oh wow. I'm so sorry. I think I may have forgotten to put up a warning for people that have an SPL lower than 4.0. Was your SPL lower than 4.0? If it was, you cannot use the USPL OR the HardSPL and they end up writing part of the ROM over your current SPL and brick the device. This, unfortunately, needs to be fixed by your local repair center. I'll talk to the Mods about unlocking that thread so that I can update it.
ivanmmj said:
Oh wow. I'm so sorry. I think I may have forgotten to put up a warning for people that have an SPL lower than 4.0. Was your SPL lower than 4.0? If it was, you cannot use the USPL OR the HardSPL and they end up writing part of the ROM over your current SPL and brick the device. This, unfortunately, needs to be fixed by your local repair center. I'll talk to the Mods about unlocking that thread so that I can update it.
Click to expand...
Click to collapse
Oh deary me! I am so dead now - I live in Tanzania, East-Africa. My "local" repair center is several hundred thousand miles away across The Big Blue. What exactly do the repair center folks do to fix the device? Perhaps I can soldier out myself with some guidance...
Thank you,
foo_bar_baz.
i have been roming and cooking with my tmobile wing for about a year now so ive become really good at it i have yet to brick my phone.....UNTILL NOW
MY NOOB HUSBAND thought while i was at work and he was using my phone to rom it he didn't know that certin roms go with certin phones so when he put the neo rom onto my tmoble wing he bricked it
i have it into bootloader mode but when i plugh it inot the usb activesync wont reconize it so i am having a hard time hard spl ing it...is the phone useless now or is there a way to fix it. im also getting an rom error. anyone have any advice....
What SPL is it showing? If your phone wasn't HardSPL'ed before, he may have ruined it and nothing will fix it short of changing the motherboard. Try flashing it with the stock RUU if it's not HardSPLed. If it is, try flashing it with your ROM named HERAIMG.nbh and place it in your SD card. Good luck.
on the bootloader screen it shows
ipl 4.10.0002
spl 4.10.0000
hyoungluv said:
on the bootloader screen it shows
ipl 4.10.0002
spl 4.10.0000
Click to expand...
Click to collapse
Sounds like the IPL and SPL are still intact. It's not HardSPL'ed so just try the stock RUU. Not having the green icon on activesync doesn't mean it doesn't see it. It means that it isn't synchronizing.
yup same thing happened to me with my first flash. i used a different rom and thought i bricked. recovered with the stock RUU
divorce him. it's that simple
jkjk
yeah, just RUU it.
lol divorce him thatsfunny, the papers were out but lucky for him i fixed it lol...i shoulda thought of using the stock rom to begin with thanks eveyone for your help and advice
hyoungluv said:
lol divorce him thatsfunny, the papers were out but lucky for him i fixed it lol...i shoulda thought of using the stock rom to begin with thanks eveyone for your help and advice
Click to expand...
Click to collapse
Great to hear that it's working, again! Now, for an important part: So you're a silent personal cook who only cooks for herself? ^_^
No, the most important part is... HARD SPL THAT THING! lol
If mine read
IPL 4.26.0002
SPL 4.26.0000
is that really bad?
Thanks for your help
EDIT:
Thanks God, it isn't. Was able to install TMobile's ROM from Bootloader.
IF others have bricked their Herald/Wing:
1. Download TMobile's ROM from here : http://wiki.xda-developers.com/index.php?pagename=Herald_Upgrades (Choose 4.26.531.4)
2. Enter Bootloader on your Wing (Hold in the camera button and then soft reset with your stylus)
3. Run the TMobile ROM.
It worked for me. Hope it does for you too.
ok, some urgent help needed, yesterday ok, today will not start. only get as far as, 'smart mobility' R1.27.12.32 G22.45.88.07H D 1.56.00.00
phone is standard WM6 HTC. i have the 6.1 image for upgrading and tried to load using SD card, i get past tri colour screen, then loading, then checking then 'not allowed' and back to tri colour. it says KAIS130, SPL-1.93.000 CPLD-8. what?next
any help appreciated guys......
gazzacbr said:
ok, some urgent help needed, yesterday ok, today will not start. only get as far as, 'smart mobility' R1.27.12.32 G22.45.88.07H D 1.56.00.00
phone is standard WM6 HTC. i have the 6.1 image for upgrading and tried to load using SD card, i get past tri colour screen, then loading, then checking then 'not allowed' and back to tri colour. it says KAIS130, SPL-1.93.000 CPLD-8. what?next
any help appreciated guys......
Click to expand...
Click to collapse
To Flash a ROM you'll most likley need Hard SPL
Follow the "Getting Started" Link in my Sig.
If you cannot get WM to boot, you'll need to re-flash your orginal carriers ROM.
Ta
Dave
thanks for quick reply DaveShaw. fell at the first though, site for 'Cmonex's HardSPL 3.29SD' is blocked here in UAE, dont know why. are there any other links?
gazzacbr said:
thanks for quick reply DaveShaw. fell at the first though, site for 'Cmonex's HardSPL 3.29SD' is blocked here in UAE, dont know why. are there any other links?
Click to expand...
Click to collapse
You shouldn't be using cmonex's SD method the first time round. It is for upgrading only.
I have downloaded the package from point 2 (you should follow the USB method in post 3, NOT the SD set) and have upload it onto my site, please let me know when you are done with it.
http://taeguk.co.uk/xda/HardSPL and CidUnlocker.zip
Ta
Dave
ok, thanks DaveShaw, i have downloaded those files. the method in step 2 involves copying the jump progs to the device memory, which i do not have access to as it will not start. can i just copy to the sd card? thats why i was trying to flash a standard rom. i need a solution that will work just from the card. will the RUU_Kaiser_HTC_WWE_1.56.405.5_radio_sign_22.45.88.07_1.27.12.11_Ship.rar load using what i have on my phone now? i assume that the spl gets replaced when i upgrade to 6.1 with htc ruu. i can try anything as i have nothing to lose now (do i?)
gazzacbr said:
ok, thanks DaveShaw, i have downloaded those files. the method in step 2 involves copying the jump progs to the device memory, which i do not have access to as it will not start. can i just copy to the sd card? thats why i was trying to flash a standard rom. i need a solution that will work just from the card. will the RUU_Kaiser_HTC_WWE_1.56.405.5_radio_sign_22.45.88.07_1.27.12.11_Ship.rar load using what i have on my phone now? i assume that the spl gets replaced when i upgrade to 6.1 with htc ruu. i can try anything as i have nothing to lose now (do i?)
Click to expand...
Click to collapse
Enter your bootloader and try flashing any ROM supplied by your carrier to get into Windows Mobile.
What screen do you get stuck on? If it is the tri color screen check out the link in my signature.
Ta
Dave
Hi again, i am not actually 'stuck' on the screen as i can get into the loader, its just that i get the message saying that the (newer) rom will not load. i am extending my (c)rapidshare as free will not let me down load the 'standard' rom, then i will try that (just had to re-initialise my paypal and the passwords are on eWallet the phone, so ive reloaded the eWallet on my pc and ....so it goes on zzzzzzzzzz its funny how these things spiral down - not).
is there any way to update the spl only from the sd card?
gazzacbr said:
Hi again, i am not actually 'stuck' on the screen as i can get into the loader, its just that i get the message saying that the (newer) rom will not load. i am extending my (c)rapidshare as free will not let me down load the 'standard' rom, then i will try that (just had to re-initialise my paypal and the passwords are on eWallet the phone, so ive reloaded the eWallet on my pc and ....so it goes on zzzzzzzzzz its funny how these things spiral down - not).
is there any way to update the spl only from the sd card?
Click to expand...
Click to collapse
No.
Can your phone boot into Windows or not?
Ta
Dave
Hi, no, it will not boot to windows. just been reading around while 'RUU_Kaiser_HTC_WWE_1.56.405.5_radio_sign_22.45.88.07_1.27.12.11_Ship' is downloading. ive got connected with mtty and get cmd>. when i type boot i get 'Command Error !!!' i assume thats not good, i think rom is corrupted. tried standard HTC 6.1 RUU_Kaiser_HTC_FIN_3.29.414.0_radio_sign_25.83.40.02_1.65.17.56_Ship version 3.14.4.1 again on USB and after phone says 1% also message saying that it will not load error 294: invalid vendor id
gazzacbr said:
Hi, no, it will not boot to windows. just been reading around while 'RUU_Kaiser_HTC_WWE_1.56.405.5_radio_sign_22.45.88.07_1.27.12.11_Ship' is downloading. ive got connected with mtty and get cmd>. when i type boot i get 'Command Error !!!' i assume thats not good, i think rom is corrupted. tried standard HTC 6.1 RUU_Kaiser_HTC_FIN_3.29.414.0_radio_sign_25.83.40.02_1.65.17.56_Ship version 3.14.4.1 again on USB and after phone says 1% also message saying that it will not load error 294: invalid vendor id
Click to expand...
Click to collapse
Yeah, you need the ROM your carrier supplied.
Where is the Phone from?
Does a Hard Reset help?
Ta
Dave
woo hoo, yippeeeeeeeeeeeeee. the kaiser lives. back to standard 6.0 rom. cheers, i owe you a beer (or 2) if you are ever in abu dhabi, let me know ;-)
i can reload all from sprite backup (only from yesterday) to get me going again
but..... next will try to replace spl and then load 6.1. not sure why HTC standard would not let me update, i thought the ruu would update any htc phone
HardSPL 3.29 is first (yes?) then will try Kaiser_HTC_ASIA_HK_WWE_3.34.721.2 which sounds good. one more thing, my phone is not locked so do i need to do the 'SIM and CID-Unlock'
gazzacbr said:
woo hoo, yippeeeeeeeeeeeeee. the kaiser lives. back to standard 6.0 rom. cheers, i owe you a beer (or 2) if you are ever in abu dhabi, let me know ;-)
i can reload all from sprite backup (only from yesterday) to get me going again
but..... next will try to replace spl and then load 6.1. not sure why HTC standard would not let me update, i thought the ruu would update any htc phone
HardSPL 3.29 is first (yes?) then will try Kaiser_HTC_ASIA_HK_WWE_3.34.721.2 which sounds good. one more thing, my phone is not locked so do i need to do the 'SIM and CID-Unlock'
Click to expand...
Click to collapse
That's right, flash the HardSPL 3.29 first (SIM unlock is optional, CID unlock isn't needed - Hard SPL takes care of that - but it comes as part of the SIM unlock) then flash a WM6.1 ROM.
Ta
Dave
gazzacbr said:
not sure why HTC standard would not let me update, i thought the ruu would update any htc phone
Click to expand...
Click to collapse
Only if it's from the same region the RUU was intended for eg the European TyTN II's won't accept the latest Hong Kong WWE ROM by default because of this so as already suggested hardSPL works around this. My WM 6.0 UK original TyTN II upgraded to WM 6.1 OK but that was using the HTC UK provided ROM update. That updated everything required including the SPL and Radio to the required HTC versions. I'm back on the original WM 6.0 version though due to reliability issues with 6.1 and poor GPS performance.
Hi there,
My brother also has an HD and off course I put a nice custom ROM on it
However, the screen is dead since yesterday.
I already put the original dutch ROM on it, but it shows a nasty green windows screen. I can't get any further beyond allign screen...
My question: when he sends his HD to HTC, they will probably won't fix it, because they can see it's HSPL (?).
So anybody knows how to restore to complete original, without getting into the phone with cabs? I put HSPL on it, the phone is 6 months old.
Any help would really be appreciated!!!!
Thx a lot
mcowly said:
Hi there,
My brother also has an HD and off course I put a nice custom ROM on it
However, the screen is dead since yesterday.
I already put the original dutch ROM on it, but it shows a nasty green windows screen. I can't get any further beyond allign screen...
My question: when he sends his HD to HTC, they will probably won't fix it, because they can see it's HSPL (?).
So anybody knows how to restore to complete original, without getting into the phone with cabs? I put HSPL on it, the phone is 6 months old.
Any help would really be appreciated!!!!
Thx a lot
Click to expand...
Click to collapse
You can restore original SPL and rom without having to get into phone with cabs.
As long as you can enter bootloader screen you can restore stock SPL.
I came across this "step for step" process via a search. I have not tried it yet (and hopefully never have to -
How to reflash Stock/Shipped SPL - STEP BY STEP - FOR WARRANTY REASONS ONLY!
0. be sure to first restore stock OS, and stock radio. stock SPL is always to be done last!!
1. download your choice of a stock spl package (ie the original SPL).
2. also download the original hardspl from the attachments in this post. (I presume you already have this?)
3. run the hardspl exe but do not click anything in RUU yet. just let the hardspl EXE extract the files for flashing. (You can probably skip this step)
4. the SPL you want to revert to is a .NBH file, put the stock SPL NBH in the extracted hardspl package, overwriting the original NBH file in it!
5. continue with the RUU (or if needed, run SSPL-Manual.exe manually, then run RUU when it goes to tricolour 1.07.OliNex screen), it goes to 100%, reboots, done.
+6. to verify, enter bootloader mode, see version number on tricolour screen, should now just say 1.14.0000.
that's it.
+7. no worries: if your device is stuck in bootloader mode with Hard-SPL and you need warranty service, you can still flash stock SPL.
As I said, I have not tried this. If this does not work, search on this site or Google for additional info. Hope it helps.
mcowly said:
Hi there,
My brother also has an HD and off course I put a nice custom ROM on it
However, the screen is dead since yesterday.
I already put the original dutch ROM on it, but it shows a nasty green windows screen. I can't get any further beyond allign screen...
My question: when he sends his HD to HTC, they will probably won't fix it, because they can see it's HSPL (?).
So anybody knows how to restore to complete original, without getting into the phone with cabs? I put HSPL on it, the phone is 6 months old.
Any help would really be appreciated!!!!
Thx a lot
Click to expand...
Click to collapse
follow to:http://forum.xda-developers.com/showthread.php?t=431217
then download ship rom to flash your HD.
longnguyen30 said:
follow to:http://forum.xda-developers.com/showthread.php?t=431217
then download ship rom to flash your HD.
Click to expand...
Click to collapse
Thanks for linking to the post, I just added the steps
The OP however says that they have already flashed back to the stock ROM, but that the colours are screwy. This needs the stock SPL restored as well in order to recover normal functioning (or at least so that they can send in for repairs without voiding the warranty).
ClydeB1 said:
Thanks for linking to the post, I just added the steps
The OP however says that they have already flashed back to the stock ROM, but that the colours are screwy. This needs the stock SPL restored as well in order to recover normal functioning (or at least so that they can send in for repairs without voiding the warranty).
Click to expand...
Click to collapse
note that; if you restore stock SPL 114 or 115 please download the same rom version for flashing.
ex: when you restore SPL 114 you must have ship Rom:http://rs68l32.rapidshare.com/files....479.3_Radio_52.49a.25.26_1.09.25.14_Ship.exe
because the different SPL & Rom version will make wrong screen.
wow, thank you very much for the quick and usefull replies!
I installed this ROM:
http://rapidshare.com/files/2189268...6.404.1_Radio_52.62.25.34_1.13.25.24_Ship.exe
So after this I have to install original SPL? Can you guys see which one?
Thanks in advance!
mcowly said:
wow, thank you very much for the quick and usefull replies!
I installed this ROM:
http://rapidshare.com/files/2189268...6.404.1_Radio_52.62.25.34_1.13.25.24_Ship.exe
So after this I have to install original SPL? Can you guys see which one?
Thanks in advance!
Click to expand...
Click to collapse
firstly you must Hard SPL 1.56 Olinex
secondly flashing your rom
And restore with SPL 1.13 I assume?
mcowly said:
And restore with SPL 1.13 I assume?
Click to expand...
Click to collapse
The process of restoring stock rom/SPL is only to be used if you plan to return device. If you are wanting to keep you you mentioned earlier then you would need to put either USPL or HSPL on your device first. I would recommend USPL for you as it would be easier to return to stock SPL afterwards.
Once you have rom on your device, DO NOT restore stock SPL afterwards. You only restore this if you plan to return your device. If you did you would have to go through whole process of putting USPL or HSPL onto your device again to flash another rom.
The phone has to be returned because of screen problems.
I will put SPL 1.13 on it and then flash the earlier mentioned ROM.
Then return to HTC
mcowly said:
The phone has to be returned because of screen problems.
I will put SPL 1.13 on it and then flash the earlier mentioned ROM.
Then return to HTC
Click to expand...
Click to collapse
No probs. Out of curiosity what screen problems do you have? Are they Hardware problems or is it something else which could possibly be fixed through the assistance of xda users
It's the phone of my brother, he tells me that the screen doesn't respond anymore, so he can't get past the calibration!
I'll give an update when HTC fixed this (or replaced it )
Thanks for all the help!
I'm doing this right now. I had been using Dutty's V6 before. I never updated the radio, so Ishouldn't have to change it, right?
Anyway, I flashed the stock RUU_BlackStone_HTC_WWE_1.56.405.1_Radio_52.62.25.34_1.13.25.24_Ship.exe rom, and that went fine. I'm trying to flash the stock 1.13 spl, and I get error 202: connection. It thinks it can't see my phone, even though it does the initial connection, and even sees what version (1.56) of the spl is on there. Any ideas?
Ok, I did this: I put the phone into bootloader manually by pressing up when it boots up to get to the tricolor screen. That let me run the 1.13 spl pdate, and it said it completed successfully. However, when it boots ups, it still shows D:1.56 olinex or whatever. Did it not work?
Ok, acutally I think it did load up. The Bootloader shows SPL-1.13.0000. So why does it show:
R1.13.25.24
G52.62.25.34u
D1.56.00.00
Is this ready to send in for service?
scythe000 said:
Ok, acutally I think it did load up. The Bootloader shows SPL-1.13.0000. So why does it show:
R1.13.25.24
G52.62.25.34u
D1.56.00.00
Is this ready to send in for service?
Click to expand...
Click to collapse
If your SPL says 1.13.0000 then you are fine to send phone in for service.
R1.13.25.24 - Radio Version
G52.62.25.34u - Protocol Version
D1.56.00.00 - ROM Version
All queries answered
Hi
http://wiki.cyanogenmod.com/index.php/Full_Update_Guide_-_G1/Dream_Firmware_to_CyanogenMod says
DO NOT FOLLOW THESE STEPS unless you've followed the previous steps on this page (or if you manually flashed your radio with the LATEST version). Otherwise, you WILL brick your phone.
Click to expand...
Click to collapse
So does brick really mean brick? It cannot be repaired? I once heard only DangerSPL can do that.
Tell us more.
Thanks,
G1Dreamer said:
Hi
http://wiki.cyanogenmod.com/index.php/Full_Update_Guide_-_G1/Dream_Firmware_to_CyanogenMod says
So does brick really mean brick? It cannot be repaired? I once heard only DangerSPL can do that.
Tell us more.
Thanks,
Click to expand...
Click to collapse
That's exactly what it means. If you don't know what you're doing, you will brick your phone. Completely. Especially if you don't update your radio. Just like you can brick your phone if you put in a wrong radio for your device, or a wrong spl for that matter.
Any time you flash the radio or SPL there is the potential for something to go wrong and possibly cause a brick, even if you meet all the requirements, buuuut as long as the SPL requires the radio you're on and you don't play hot potato while it's flashing you should be fine. Brick means it's dead, the nand needs to be reflashed at the factory or you can replace the motherboard yourself (containing the nand).
Yep, I've bricked a G1 before. I don't remember exactaly what I did, I think I flashed the same Hard SPL twice, and bam. Brick. Luckily enough it as within the 14 days return period of buying it, and I was able to get my money back and buy another.
AdrianK said:
you don't play hot potato while it's flashing you should be fine. Brick means it's dead.
Click to expand...
Click to collapse
This is what NOT to do
I already installed HardSPL once. Now I am going to from CM back to original Firmware and back since I made some mistakes with apps2sdcard. Will my HardSPL remain? If not that would mean that the orinigal SPL would be reinstalled does it not? In that case the chance of bricking would be there again?
G1Dreamer said:
I already installed HardSPL once. Now I am going to from CM back to original Firmware and back since I made some mistakes with apps2sdcard. Will my HardSPL remain? If not that would mean that the orinigal SPL would be reinstalled does it not? In that case the chance of bricking would be there again?
Click to expand...
Click to collapse
SPL and radio are independant of the ROM. So, no.
So my HardSPL could remain forever and I will always get the joy of backing up my phone and will never have to fear a brick because of a new SPL?
Im just a user no developer. I just want to do regular stuff with my phone and use CM. Are there any situations where I still have to change the SPL?
G1Dreamer said:
So my HardSPL could remain forever and I will always get the joy of backing up my phone and will never have to fear a brick because of a new SPL?
Im just a user no developer. I just want to do regular stuff with my phone and use CM. Are there any situations where I still have to change the SPL?
Click to expand...
Click to collapse
You will have to change if you want a Hero ROM. There should be no reason to update the SPL
Just be careful upgrading either SPL or Radio. Read up to make sure it wont cause a brick for sure.