WARNING about downgrading from WM6 LVSW Edition (2007-03-20)

[Cuivienor]

Hey all,

I am posting this as an independent thread to be sure it gets some visibility. If an admin judges it should be put into the main LVSW thread, then he is welcome to move it within the LVSW thread. However I'm pretty sure I stumbled onto something that can prevent a lot of pain for some people.

Here is the scenario which occurred to three different people:
- SuperCID device.
- LVSW full version is installed with no problem => SPL 1.09
- Downgrade to any Official ROM using the provided normal RUU. Flashing goes 100% fine, not a single problem
- But upon reboot, we have a brick: Corrupted CID, SPL 1.09, No GSM, and depending on the Official ROM flashed KITL or no KITL (if the former, recoverable through hours of work with Platform Builder, if the later, unrecoverable). Since the flashing went 100% fine, that's weird, to say the least.

This same identical scenario has generated three bricks thus far:
- myself, repaired after a sleepless night spent on Platform Builder (my gratitude goes to Allan's most excellent post)
- lebogus, complete brick, no KITL, unrecoverable
- otto26, KITL, recoverable with Platform Builder

IMHO, three cases like that is too much to be a coincidence, especially after a 100% problem-free flashing of an official ROM.

Therefore, to anyone wishing to downgrade from a full version of LVSW (with SPL 1.09), he should make sure that before downgrading, he replaces the 1.09 SPL with Olipro's Hard-SPL to be sure that even if this scenario repeats itself, he doesn't have to go through Platform Builder.

I hope this thread won't be judged to be abusive and misplaced, if so I apologize.

Anyway maybe this will help someone.

Cheers
Yannick

[jcespi2005]

Hey all,

I am posting this as an independent thread to be sure it gets some visibility. If an admin judges it should be put into the main LVSW thread, then he is welcome to move it within the LVSW thread. However I'm pretty sure I stumbled onto something that can prevent a lot of pain for some people.

Here is the scenario which occurred to three different people:
- SuperCID device.
- LVSW full version is installed with no problem => SPL 1.09
- Downgrade to any Official ROM using the provided normal RUU. Flashing goes 100% fine, not a single problem
- But upon reboot, we have a brick: Corrupted CID, SPL 1.09, No GSM, and depending on the Official ROM flashed KITL or no KITL (if the former, recoverable through hours of work with Platform Builder, if the later, unrecoverable). Since the flashing went 100% fine, that's weird, to say the least.

This same identical scenario has generated three bricks thus far:
- myself, repaired after a sleepless night spent on Platform Builder (my gratitude goes to Allan's most excellent post)
- lebogus, complete brick, no KITL, unrecoverable
- otto26, KITL, recoverable with Platform Builder

IMHO, three cases like that is too much to be a coincidence, especially after a 100% problem-free flashing of an official ROM.

Therefore, to anyone wishing to downgrade from a full version of LVSW (with SPL 1.09), he should make sure that before downgrading, he replaces the 1.09 SPL with Olipro's Hard-SPL to be sure that even if this scenario repeats itself, he doesn't have to go through Platform Builder.

I hope this thread won't be judged to be abusive and misplaced, if so I apologize.

Anyway maybe this will help someone.

Cheers
Yannick

I don't think this thread abusive, but can help noob users. Really the HardSPL must convert in "the standar" for upgrading to WM6 in cooking. If someone cook any WM6 ROM, HardSPL must be part of package...

So thanks for your advice.

[mrvanx]

Heres a quick guide to flashing HardSPL (http://www.mrvanx.myzen.co.uk/hermes_guide/HardSPL.html) to help users on the way.
;)

[jcespi2005]

Heres a quick guide to flashing HardSPL (http://www.mrvanx.myzen.co.uk/hermes_guide/HardSPL.html) to help users on the way.
;)

Goooood work, man.....

Now lets the cookers to include HardSPL into his cooked ROMs to get the maximun protection against dead hermes...

[jasjamming]

Goooood work, man.....

Now lets the cookers to include HardSPL into his cooked ROMs to get the maximun protection against dead hermes...


Dears,

Black 1.2 now comes bumdled with Oli's 1.13.Oli Hard SPL for securiry measures and to avoid bad block problems.

[jcespi2005]

Dears,

Black 1.2 now comes bumdled with Oli's 1.13.Oli Hard SPL for securiry measures and to avoid bad block problems.

This is the correct way.... thanks :)

[Olipro]

I think you're talking out your bloody arse frankly.

I have no idea how you managed to shit up your radio, but that's what you've done, something definitely went tits up and I don't really think it's lwvs's fault unless he disassembled the radio and edited the bloody thing to deliberately corrupt a flash

[Cuivienor]

I don't think this thread abusive, but can help noob users. Really the HardSPL must convert in "the standar" for upgrading to WM6 in cooking. If someone cook any WM6 ROM, HardSPL must be part of package...

So thanks for your advice.

Thanks for letting me know :) I was just pretty unsure of where to put my message and whether it deserved a full-fledged thread...
Anyway I'm glad this can be of help and I hope it won't disappear too quickly into the depth of this forum (not at least until LVSW includes Olipro's bootloader...)

Yannick

[LegolasTheElf]

I'm going to post a rom of lvsw 3-20 that includes oli's 1.13 BL and the OS with extra ram ONLY. No radio, no IPL, no extrom. hang tight, I'm uploading now :)

[Cuivienor]

I think you're talking out your bloody arse frankly.

I have no idea how you managed to shit up your radio, but that's what you've done, something definitely went tits up and I don't really think it's lwvs's fault unless he disassembled the radio and edited the bloody thing to deliberately corrupt a flash

OK if so I'm sorry. It's just that three apparently successful flashings of official ROMs ending up in bricks look strange to me. Maybe it's theoretically impossible and it must mean that there was some external reason. But you have to admit that three times the same scenario within the last 2 days is an improbable coincidence.

I am not blaming lwvs by the way, his ROM is most excellent, I loved it, but needed to downgrade because of a problem I had with some of my software (WM6's fault, not lwvs's).
As said, maybe it's a completely external reason. Who knows? What I care about is that I noticed it happened following this scenario several times in a very short span. Make what you will out of it.

Just see it as a warning, and anyone is free to do as he or she wishes.

Cheers
Yannick

[mrvanx]

I'm going to post a rom of lvsw 3-20 that includes oli's 1.13 BL and the OS with extra ram ONLY. No radio, no IPL, no extrom. hang tight, I'm uploading now :)

URL please for the wiki ?

[jcespi2005]

I'm going to post a rom of lvsw 3-20 that includes oli's 1.13 BL and the OS with extra ram ONLY. No radio, no IPL, no extrom. hang tight, I'm uploading now :)

Thanks for your work.. sure this help more than one...starting with me :)

[jpvdp]

I had exactly the same problem, going from lvsw to an older official wm5 rom.
All went fine, 100%, reboot and NO GSM.

Recovered with KITL.

[LegolasTheElf]

@jpvdb Did you install OS only, or the full package?

[mrvanx]

Gotta ask, when downgrading to WM5 obviously this will flash a new SPL, Radio and OS to the device correct?? Because by the sounds of it people are using the full RUU package and not splitting into seperate nb files)

So firstly if it is 1.09 this WILL NOT be downgraded, and if the radio being flashed is of loader 0107 could this be the reason?

Since Most people now have a radio version with loader 0108 this might be the reason behind it??

If im GROSSLY incorrect please correct me right now (im after some of that olipro charm!!!! :D)

[mfabre]

I had exactly the same problem, going from lvsw to an older official wm5 rom.
All went fine, 100%, reboot and NO GSM.
Recovered with KITL.

I've done the downgrade twice without any problem. I am now back to 3-20 version. In case it helps to identify the problem, I have used Hard-SPL every time and I have flashed the different components separately.

I stayed with radio 1.35.00.11 and I only flashed the different OSs (extracting them from original ROMs when needed). No problems at all.

[LegolasTheElf]

I have created a lvsw 3-20 that installs ONLY Oli's 1.13 BL and OS with Extra ROM Storage ONLY!

Get it from here:

http://rapidshare.com/files/22731195/lvsw3-20.with.oli1.13.and.os.with.extra.ram.only.rar

** Please note, if you already have Oli's 1.13, choose 1.11 and HARD. **

** Thanks goes to the_passenger for creating the extra-ram version of the OS! Works like a champ on my two devices :)

[Cuivienor]

@mrvanx: correct, we are talking about full upgrades and downgrades. Your point is pretty interesting by the way, and it seems that mfabre's case goes in the way of this theory. But indeed you should wait for Olipro's expert opinion :)

@LegolasTheElf: talk about reactivity... You rule, man!

[LegolasTheElf]

URL please for the wiki ?
Already done! :D

[mrvanx]

...Rom: WM6! LVSW 3-20-07 WARNING!! Don't install LVSW radio! Use this instead! See this thread for more info!
....
....
....If you installed the entire rom that lvsw posted, it seems like the radio has been modified and it's causing issues. This update will prevent bricking of your phone when you go to change the radio.

However, if you only installed the OS and have NOT installed lvsw's radio, this is a useless upgrade unless you want the increased ROM storage.

I think it is a tad premature to announce that there is a problem with the LVWS ROM sir. It is more than likely that the problems experienced are due to people trying to reflash an old SPL, and a radio with loader 0107 (which CANNOT be downgraded).

I would recommend removing the line from your sig since we have only reports of THREE cases of this happening. We dont want to cause alarm to people who have been running this ROM without any problems.

[LegolasTheElf]

I think it is a tad premature to announce that there is a problem with the LVWS ROM sir. It is more than likely that the problems experienced are due to people trying to reflash an old SPL, and a radio with loader 0107 (which CANNOT be downgraded).

I would recommend removing the line from your sig since we have only reports of THREE cases of this happening.

Flashing an older radio is no problem. 0108 just isn't downgraded.

Old SPL's aren't a problem. It just wont downgrade (unless you know how).

Radio is the only thing that can cause bricks in this equation. It's definately that.

And lvsw says that he modified the radio! It's a bad mod.. I'm sure he tried as hard as he could to make it perfect; his OS is awesome! But, the radio is causing problems.

Besides, this will get you the 1.13.Oli which will prevent bricks, and give you an extra 10MB of ROM. It's all good.

[Cuivienor]

I would recommend removing the line from your sig since we have only reports of THREE cases of this happening.

Four with jpvdp. But I agree for all we know it could be another problem...

[LegolasTheElf]

Four with jpvdp. But I agree for all we know it could be another problem...

Bottom line is this:

INSTALLING OLIPRO'S 1.13.OLI BOOT LOADER IS THE SINGLE BEST THING YOU CAN DO TO PREVENT BRICKS!

My LVSW upload INCLUDES the 1.13.Oli Boot Loader.

[Cuivienor]

hahaha correct LegolasTheElf!

[jcespi2005]

I think it is a tad premature to announce that there is a problem with the LVWS ROM sir. It is more than likely that the problems experienced are due to people trying to reflash an old SPL, and a radio with loader 0107 (which CANNOT be downgraded).

I would recommend removing the line from your sig since we have only reports of THREE cases of this happening. We dont want to cause alarm to people who have been running this ROM without any problems.

Perhaps it is premature, but i'm rigth if i put people in way to make better ROM, and i think put HardSPL is a good idea.

There is the better idea can extract on this thread, not the bad or less bad ROM, but how to make better and secured ROMs.

EDITED: Take a look at http://forum.xda-developers.com/showthread.php?t=299564 Seems like LVSW put HardSPL in his new ROM. Good idea ;)

[Olipro]

I compared the radio and SPL from lvsw and guess what? they're identical to the retail ones

therefore, one can only assume you're not doing something right or your Hermes is screwy... I suggest this thread be deleted, it's misinformation of a very worrying and dangerous kind.

[shogunmark]

out of curiosity... has anyone tried to load the 1.01MFG bootloader on their device prior to flashing the OEM rom?? i bring this up cause i wonder if it has something do to with the oli bootloader??? Not cutting on oli as he has done wonderful things for us, but if there is a flaw with it somewhere then we need to find it and fix it.... anyone willing to risk their device to try this? :D

[Cuivienor]

I'll just repeat myself. At least I'm not trying to mislead people or anything. I'm just seeing what happened to several people (not just me). People assumed the radio was wrong you proved it wasn't. We don't know if this WM6 ROM is directly connected to the problem or is its indirect cause or is not related whatsoever, a reaction of the device I don't know... and again I don't care.

I'm just seeing that a certain sequence of events caused several bricks within the last few days whereas this sequence of events shouldn't have. It may be wrong or misleading to mention LVSW, but I think censorship is worse in that there is a non-negligible chance that my thread will prevent bricks. I'm reporting what happened, and people draw the consequences from that or not. They're intelligent enough to do that on their own. If you want to delete this thread then I want you to realize that it is a form of censorship.

You don't agree with whatever is written in there. You have a lot of expertise to back that up. FINE! You made your point. Your opinion backed by a lot of technical expertise, etc VS my layman report backed by nothing but observations available in written form in this thread and the bricked Hermes thread. People can choose.

Finally the whole point is moot now with the release of LVSW 03-25. Your Bootloader rules, and I'm sure you're the first one to admit that putting it on the Hermes if there's any intent to flash ROMs is a Good Thing (tm).

Cheers
Yannick

[Halldor]

I compared the radio and SPL from lvsw and guess what? they're identical to the retail ones

therefore, one can only assume you're not doing something right or your Hermes is screwy... I suggest this thread be deleted, it's misinformation of a very worrying and dangerous kind.


I agree! I started to sweat and this seems to have no merit at all.

[pof]

@Cuivienor: I just flashed lvsw 20070320 including it's 1.09 bootloader and radio, then went back to older WM5 rom. I had no problem at all.

What I think, is same problem as when the SA 1.35 rom was released: bootloader 1.09 is a very good brick-maker... and lvsw included this SPL in his rom, so more chances of bricking with 1.09 than with any other bootloader.

[Cuivienor]

@pof: You probably are right. Thanks for doing this on your side as well.

It's just that I still don't get how a successful flash can lead to a brick (actually several successful flashes to several bricks as I've been roaming in the brick thread for the last 2 days).

Maybe I cried wolf too early I don't know, but if it were to be done again, I would do it again simply because too many coincidences may mean something, and they didn't just jump out of my own imagination.

Anyway thanks again for trying the thing yourself and I can only praise LVSW for his hard work and his latest ROM.

Yannick

[jpvdp]

Seems there are quite some "defensive" reactions to this.
Really I think nobody is trying to flame the lvsw rom or anything.
Just strange it happened to 4 people.

I did use a full wm5 install, guess that was wrong, but I am sure others will do in the future, isnt some sort of warning about that in place then?

Anyways, as far as I can tell the ts only wanted to put a warning out..

[ach2]

Hey all,

I am posting this as an independent thread to be sure it gets some visibility. If an admin judges it should be put into the main LVSW thread, then he is welcome to move it within the LVSW thread. However I'm pretty sure I stumbled onto something that can prevent a lot of pain for some people.

Here is the scenario which occurred to three different people:
- SuperCID device.
- LVSW full version is installed with no problem => SPL 1.09
- Downgrade to any Official ROM using the provided normal RUU. Flashing goes 100% fine, not a single problem
- But upon reboot, we have a brick: Corrupted CID, SPL 1.09, No GSM, and depending on the Official ROM flashed KITL or no KITL (if the former, recoverable through hours of work with Platform Builder, if the later, unrecoverable). Since the flashing went 100% fine, that's weird, to say the least.

This same identical scenario has generated three bricks thus far:
- myself, repaired after a sleepless night spent on Platform Builder (my gratitude goes to Allan's most excellent post)
- lebogus, complete brick, no KITL, unrecoverable
- otto26, KITL, recoverable with Platform Builder

IMHO, three cases like that is too much to be a coincidence, especially after a 100% problem-free flashing of an official ROM.

Therefore, to anyone wishing to downgrade from a full version of LVSW (with SPL 1.09), he should make sure that before downgrading, he replaces the 1.09 SPL with Olipro's Hard-SPL to be sure that even if this scenario repeats itself, he doesn't have to go through Platform Builder.

I hope this thread won't be judged to be abusive and misplaced, if so I apologize.

Anyway maybe this will help someone.

Cheers
Yannick

I'm probably going to get flamed a bit here for not reading the rest of the thread, but... 3 friends upgrading ok then downgrading and producing 3 bricks is a bit of a coincidence... Usually friends feed from each other so the less experienced copy the most experienced (or adventurous)

Can you remember EXACTLY how you all downgraded and on what phones? There must be a common denominator. I've done this a few times (WM5 to WM6 and back) without problems.

BTW, Your thread isn't abusive, it's obvious you've done some reading and experimenting , and have expressed the results well:)

[Cuivienor]

@ach2

As far as I can tell, we four (yeah it's up to four now) are not especially friends (we don't know each other, it's just the bricked hermes thread (and one in this thread) which are a testimony to those bricks).

To tell you *exactly* how I downgraded: I downloaded the French Qtek ROM from the wiki (1.18.256.2), connected my device with ActiveSync 4.5. I double-clicked on the exe, followed the steps as usual (next next update) and the flashing went perfectly fine (with the Qtek installer even going as far as telling me the flashing was successful).
I thought it was until I was blocked on the WM5 startup screen and No GSM, CID corrupt. This on a previously SuperCIDed HTC TyTN HERM200.

One of the others (lebogus) did the same, from what I gathered: same device, one of the wiki's 2 French ROMs (not sure which, presumably the Orange/Vodafone 1.23.163.5 one because it didn't have KITL activated and I am SURE the Qtek ROM has it), same method of downgrading. Successful, but brick nonetheless.

Still one of the others (otto26) used the German HTC ROM (1.18.257.2) from the wiki, on a HERM200 device (presumably an HTC TyTN as well since it's Germany, but it would have to be asked). Again flashing successful but brick anyway.

I don't know what ROM the last one used (jpvdp) but as far as I can tell, same method of downgrading. Since he reads the thread, maybe he can give us more details. You guessed it, 100% successful is a brick.

That's about it

Yannick

PS: for more details, pages 71 to 77 of the bricked hermes thread

[ach2]

Normally I'll support Olipro and LegolasTheElf because I think they're gods (like Hermes himself, or at least his dad:) ), but on this ocassion I think they're wrong to call for this thread to be closed...

@Cuivienor - Sorry, when you were talking about 'friends' I imagined people you knew with the same phone, not other forum members.

I can only think that if the flashing process (WM5 to WM6) and re-flashing process (WM6 to WM5) was identical then something in the pre-conditioning (ie, in-between flashing and re-flashing) was different.

What were the bootloaders just before flashing? I ALWAYS check this before an upgrade or change because I have overwritten the SPL in the past and want to make sure I have one of Olipro's BL's before upgrading.

Anyway, this is a bit moot at the moment because there are 4 bricks out there which need (or needed repairing) so maybe we concentrate on that for now.

4 similar (but not necessarily identical) flashing processes have caused bricks (out of the thousands of successful flashes). This doesn't mean that the ROM is faulty, but may mean that our descriptions of the process with which we flash are not specific enough. However, it also doesn't mean that the ROM is perfect, there MAY be certain times when (even if only a small percentage) that the ROM causes the problem. If we ignore the few times then we become like M$ where an accepted failure rate is ok as long as it's small enough.

Please don't close this thread because we may actually discover the root cause of these bricks - even if it is 'fuckwit' errors (sorry Olipro - like the phrase:) )

[Cuivienor]

Please don't close this thread because we may actually discover the root cause of these bricks - even if it is 'fuckwit' errors (sorry Olipro - like the phrase:) )

Isn't it "fucktard errors"? :D
Anyway for the four of us it was the LSVW WM6 full ROM installed, therefore SPL 1.09. At the time when I downgraded I thought SuperCID was protection enough and since I was flashing an official ROM on a laptop (so no risk of power shortage) I was OK. And I was "right" since the flashing went "successfully"......

Anyway for all of us it was SPL 1.09. As pof suggested earlier in the thread it might just be the fault of SPL 1.09, which is as he said "a very good brick-maker". Pof himself tried the full upgrade and downgrade, and his device didn't brick.

If you need any more data about it, go right ahead and ask

Yannick

[shafez]

Hey all,

I am posting this as an independent thread to be sure it gets some visibility. If an admin judges it should be put into the main LVSW thread, then he is welcome to move it within the LVSW thread. However I'm pretty sure I stumbled onto something that can prevent a lot of pain for some people.

Here is the scenario which occurred to three different people:
- SuperCID device.
- LVSW full version is installed with no problem => SPL 1.09
- Downgrade to any Official ROM using the provided normal RUU. Flashing goes 100% fine, not a single problem
- But upon reboot, we have a brick: Corrupted CID, SPL 1.09, No GSM, and depending on the Official ROM flashed KITL or no KITL (if the former, recoverable through hours of work with Platform Builder, if the later, unrecoverable). Since the flashing went 100% fine, that's weird, to say the least.

This same identical scenario has generated three bricks thus far:
- myself, repaired after a sleepless night spent on Platform Builder (my gratitude goes to Allan's most excellent post)
- lebogus, complete brick, no KITL, unrecoverable
- otto26, KITL, recoverable with Platform Builder

IMHO, three cases like that is too much to be a coincidence, especially after a 100% problem-free flashing of an official ROM.

Therefore, to anyone wishing to downgrade from a full version of LVSW (with SPL 1.09), he should make sure that before downgrading, he replaces the 1.09 SPL with Olipro's Hard-SPL to be sure that even if this scenario repeats itself, he doesn't have to go through Platform Builder.

I hope this thread won't be judged to be abusive and misplaced, if so I apologize.

Anyway maybe this will help someone.

Cheers
Yannick


This exactly what happend to me too.

Now I am stuck with my Jasjam not working in my drawer.

Thanks and Regards

[Cuivienor]

This exactly what happend to me too.

Now I am stuck with my Jasjam not working in my drawer.

Thanks and Regards

Fifth case...

shafez, feel free to post in the Upgrading forum in the brick thread to tell us more about it (flashing to what ROM, all the info as shown on the second post of the first page of the brick thread) and to check the wiki http://wiki.xda-developers.com/index.php?pagename=Hermes_UpgradeProblems and http://wiki.xda-developers.com/index.php?pagename=Hermes_Unbrick, if your device still has KITL, then it may still be saved...

Yannick

[shafez]

Fifth case...

shafez, feel free to post in the Upgrading forum in the brick thread to tell us more about it (flashing to what ROM, all the info as shown on the second post of the first page of the brick thread) and to check the wiki http://wiki.xda-developers.com/index.php?pagename=Hermes_UpgradeProblems and http://wiki.xda-developers.com/index.php?pagename=Hermes_Unbrick, if your device still has KITL, then it may still be saved...

Yannick

Cuivienor

Could you please post how you got over this problem in details ?

Thanks and regards

[Cuivienor]

Go to http://forum.xda-developers.com/showthread.php?t=286755 read the first post completely and imitate the template of the second post to tell us about your problem.

EDIT: Assuming you have KITL enabled, the steps to follow are there http://wiki.xda-developers.com/index.php?pagename=PB_KITL_HERMES

[shafez]

Go to http://forum.xda-developers.com/showthread.php?t=286755 read the first post completely and imitate the template of the second post to tell us about your problem.

Model: i-mate JASJAM
ROM Before Flash: QTEK_WWE_2.11.255.1_102_6275_1.38.00.10_108
Before Flash: 1.38
Bootloader Before Flash: 1.11
Flash failed at: 18%
Flashing ROM: WM6 for Hermes LVSW Edition (2007-03-20)
Flashing Radio: 1.34.00.10
Bootloader After Failure: 1.09
CID Before Failure Super CID: Yes
CID Corrupt: Yes
Radio Corrupt: Yes
No GSM Error: Yes
Stuck In Bootloader: No
Stuck On Windows Mobile Splash: Yes
Can boot into OS: No
Tried mtty command set 14 0: Yes
Tried wiki problem number 5: Yes
mtty info 2 output: CID: Wait interpreter timeout HTCSF kEØ(HTCEUSB>FF
Current Device Status: unusable

Please Help

Thanks and Regards

[gregouille]

I upgraded to LVSW 03-20
My SPL is now 1.09

If i upgrade to LVSW 03-25 i understand that I'll get 1.13.Oli SPL

- Is that Hard SPL ?
- If yes, that means that I do not have to force any other SPL through RUU ?
- If yes, that means that I can install any (upgrade or downgrade) ROM ?

Thanks for your answers

Greg

[Cuivienor]

@shafez

OK so only four cases. Your case is not like the others. To diagnose your case, please read http://wiki.xda-developers.com/index.php?pagename=Hermes_Unbrick , the especially important point is the last one, to know whether you have KITL enabled. Also when you know that do not post in this thread anymore about your brick. From now on post in that thread http://forum.xda-developers.com/showthread.php?t=286755 , I'll be watching it to help.

@gregouille
Yes 1.13.Oli is HardSPL.
Right now you have SPL 1.09. It is as far as I know recommended that you install Hard SPL on your own before doing any ROM flashing.
However since LVSW now has 1.13.Oli you should be quite safe anyway.

Yannick

[gregouille]

Thanks a lot

[Cuivienor]

Even if this will make Olipro irate, I'll add something to that.

I have done a full install of LVSW (latest version: 26/03/2007) followed by a full downgrade to the French Qtek official ROM, and all the flashings were 100% successful. I have done this three times.
Those three times were followed by a brick (quickly repaired because that time I had Hard-SPL, thanks to Olipro, and could flash a radio only ROM), and it is a process I can demonstrate on my phone because for now, it works 100% of the time: flash LVSW, flash Qtek French ROM, 100% successful => brick with No GSM.

Also up to now, 5 other very similar (but downgrading from Taiwan AKU 3.3.1) and 4 identical cases have been brought to my attention.

So not the fault of LVSW of course (as I've always been saying) since Taiwan AKU 3.3.1 has the same symptoms, but there is a problem, and I'm not talking out of my arse.

Yannick

[Sniper258]

Even if this will make Olipro irate, I'll add something to that.

I have done a full install of LVSW (latest version: 26/03/2007) followed by a full downgrade to the French Qtek official ROM, and all the flashings were 100% successful. I have done this three times.
Those three times were followed by a brick (quickly repaired because that time I had Hard-SPL, thanks to Olipro, and could flash a radio only ROM), and it is a process I can demonstrate on my phone because for now, it works 100% of the time: flash LVSW, flash Qtek French ROM, 100% successful => brick with No GSM.

Also up to now, 5 other very similar (but downgrading from Taiwan AKU 3.3.1) and 4 identical cases have been brought to my attention.

So not the fault of LVSW of course (as I've always been saying) since Taiwan AKU 3.3.1 has the same symptoms, but there is a problem, and I'm not talking out of my arse.

Yannick

So, what you are saying is that a brick with a corrupted radio only or complete brick.
Also, I'm just wondering if you had any problems connecting your device to PC to flash the radio again. Did you face any or did you flash it through the memory card.
The reason I ask is to know as much as possible so I'd never brick my device again when it comes from repair.
Thanks

[Cuivienor]

It's basically a radio brick, but the OS is not bootable (so no way to execute HERM-SSPL). If you don't have Hard-SPL installed (which you do if your upgraded to LVSW), then KITL is the way to go.
I flashed the radio using the latest Custom RUU under bootloader mode (1.40.Oli) and it worked through USB with no problem to unbrick the device.

[Sniper258]

Thanks Cuivienor