Related
Hi,
I am a SoftBank X01HT user. Recently a rom update was released and I applied it.
ftp://210.136.175.150/F1_RUU/RUU_X01HT_1.33.761.4_1.14.00.10.exe
After update the bootloader version changed to 1.09, so I downgraded the bootloader to 1.04 and it seems to be successful (I confirmed it in bootloader mode screen). Then I installed the DoCoMo version shipped rom of following versions.
ROM Version: 1.23.731.2
Radio Version: 1.06.00.10
Bootloader: 1.04
Language: JPN (Japanese)
CID: DOCOM801
The installation finished successfully, but the radio version is 1.14!!
ROM Version:1.23.731.2
Radio Version:1.14.00.10
I tried to upgrade radio to 1.20 but in vain. I ran MaUpgradeUt_noID.exe and it seemed to work correctly till 99% (however it shows ERROR 114 finally).
After soft reset, I found that the radio version was still 1.14.00.10.
What's the matter? Anyone can help please?
Best regards,
uedam said:
Hi,
I am a SoftBank X01HT user. Recently a rom update was released and I applied it.
ftp://210.136.175.150/F1_RUU/RUU_X01HT_1.33.761.4_1.14.00.10.exe
After update the bootloader version changed to 1.09, so I downgraded the bootloader to 1.04 and it seems to be successful (I confirmed it in bootloader mode screen). Then I installed the DoCoMo version shipped rom of following versions.
ROM Version: 1.23.731.2
Radio Version: 1.06.00.10
Bootloader: 1.04
Language: JPN (Japanese)
CID: DOCOM801
The installation finished successfully, but the radio version is 1.14!!
ROM Version:1.23.731.2
Radio Version:1.14.00.10
I tried to upgrade radio to 1.20 but in vain. I ran MaUpgradeUt_noID.exe and it seemed to work correctly till 99% (however it shows ERROR 114 finally).
After soft reset, I found that the radio version was still 1.14.00.10.
What's the matter? Anyone can help please?
Best regards,
Click to expand...
Click to collapse
I also have this problem. I try to upgrade my X01HT's Radio to 1.16 and 1.20. But after softreset it show 1.14 in radio....
01015 said:
I also have this problem. I try to upgrade my X01HT's Radio to 1.16 and 1.20. But after softreset it show 1.14 in radio....
Click to expand...
Click to collapse
In addition I tried this rom with bootloader 1.09 and radio 1.18.00.10.
ftp://xda:[email protected][1].35.255.2_1.35.255.102_1.08.00.10_SHIP.EXE
The radio rom was not upgraded to 1.18, it remains 1.14.
very weird... can you attach a usb-monitor capture when trying to flash another rom? see the wiki (upgrading problems) for instructions on how to use usb-monitor.
pof, see http://forum.xda-developers.com/showpost.php?p=1068511&postcount=35
might be due to the new SoftBank ROM sold since December?
Even they http://www.imei-check.co.uk/m3100unlock.php couldn't do it:
The Unlocker it will NOT WORK with Japanase Softbank devices with SPL1.09 and radio 1.14.00.10 sold after 1st December 2006. To check your spl just put the phone in bootloader :hold the [OK] button (from the left side of the phone where the volume button is) and the [power on] button and in same time press the [reset] hole (near to the charger connector -- use stylus to press it!) and you can see IPL and SPL
Radio version can be checked from Start->Settings->System->Device Information:Radio Version.
If you buy the unlocker and claim that your phone is a 1.09 we will NOT refund you. We don't know when we will release a new update or IF we will release one!!!
Click to expand...
Click to collapse
Yes, I think the new softbank device has the radio area "read only" somehow, that makes impossible to patch the radio in order to SIM/CID unlock. However I would like to see a USB Monitor capture of the process when trying to flash a radio rom on it, to see exactly what the bootloader returns. If anyone can attach it, it would be great
pof said:
Yes, I think the new softbank device has the radio area "read only" somehow, that makes impossible to patch the radio in order to SIM/CID unlock. However I would like to see a USB Monitor capture of the process when trying to flash a radio rom on it, to see exactly what the bootloader returns. If anyone can attach it, it would be great
Click to expand...
Click to collapse
Would be an explaination but uedam said he is stuck on 1.14.0.1 since he installed the new X01HT ROM. This implies he had another version before - so it seems that the read only effect isn't caused by the hardware but by the ROM and can't be removed by flashing another ROM (at the moment).
Perhaps there is a hidden command executed when the ROM is flashed. Something that write-protects a range in memory. But I have no explaination why the process runs until 99%.
Someone has to log the USB traffic when flashing the new ROM.
By the way: I'm not willing to test this on my own device
pof said:
very weird... can you attach a usb-monitor capture when trying to flash another rom? see the wiki (upgrading problems) for instructions on how to use usb-monitor.
Click to expand...
Click to collapse
pof,
I installed usbmon and tried radio rom 1.20 upgrade again (it also failed...)
Here is the log files exported from usbmon. I hope it will help to solve the problem.
ftp://xda:[email protected]/Uploads/Hermes/Tools_and_Programs/usbmonlog.zip
Sorry, the file was too large to attach to this post.
p.s. If you need further information, please let me know.
Thanks uedam, the process seems to be the same like in every other device. The only "minor" strange thing is that when flashing a 0x10000 byte block at address 0x6d0000 you get a failure the first time, then the RUU does an 'rerase' of this memory portion, tries again and gets a success, and follows with the radio flashing process. But I think this has nothing to do with the problem we're facing here.
sn00x said:
Would be an explaination but uedam said he is stuck on 1.14.0.1 since he installed the new X01HT ROM. This implies he had another version before - so it seems that the read only effect isn't caused by the hardware but by the ROM and can't be removed by flashing another ROM (at the moment).
Perhaps there is a hidden command executed when the ROM is flashed. Something that write-protects a range in memory. But I have no explaination why the process runs until 99%.
Someone has to log the USB traffic when flashing the new ROM.
By the way: I'm not willing to test this on my own device
Click to expand...
Click to collapse
Yes, before upgrade I unlocked my X01HT and used with DoCoMo rom. The radio version was 1.06.00.10.
I uploaded the USB traffic log and please view the file. Does the same thing occur when writing another rom? or this is the first case?
pof said:
Thanks uedam, the process seems to be the same like in every other device. The only "minor" strange thing is that when flashing a 0x10000 byte block at address 0x6d0000 you get a failure the first time, then the RUU does an 'rerase' of this memory portion, tries again and gets a success, and follows with the radio flashing process. But I think this has nothing to do with the problem we're facing here.
Click to expand...
Click to collapse
Hmmm, would it make sense to have him log the full-upgrade process - presumably the "locking" happened when he did the RUU_X01HT_1.33.761.4_1.14.00.10.exe
and hopefully it would happen even if Radio 1.14 were already on the system when he re-did the full upgrade.....
Richard
Yes, this will be at least worth looking at
pof said:
Yes, this will be at least worth looking at
Click to expand...
Click to collapse
I did full rom upgrade again and got log to the file.
ftp://xda:[email protected]/Uploads/Hermes/Tools_and_Programs/fullupgradelog.zip
It's beyond my comprehension.
p.s. It's very large (about 400MB text file, the zip is about 120MB)
Hey uedam, nice work dude!
I've had a quick look and seems a normal upgrade to me, I see nothing related to the write-locking of the radio, but will look at it more deeply later, in case I skipped something important.
However I extracted GSM.nb from softbank 1.33.761.4 ROM and GSM.nb from HTC 1.18.416.1ROM which both should be radio 1.14.00.10 but the files are different, so I guess the locking is done in the radio itself (??).
pof said:
Hey uedam, nice work dude!
I've had a quick look and seems a normal upgrade to me, I see nothing related to the write-locking of the radio, but will look at it more deeply later, in case I skipped something important.
However I extracted GSM.nb from softbank 1.33.761.4 ROM and GSM.nb from HTC 1.18.416.1ROM which both should be radio 1.14.00.10 but the files are different, so I guess the locking is done in the radio itself (??).
Click to expand...
Click to collapse
pof, it sounds quite interesting. Softbank built the special version of 1.14.00.10 radio?
So, if possible, we cook new rom which includes radio rom same as HTC 1.18.416.1 rom then the person who has 1st version of X01HT can upgrade it safely?
uedam said:
So, if possible, we cook new rom
Click to expand...
Click to collapse
Unless I missed it, no one has been able to cook Hermes (or any of the new format) ROMs.
Richard
pof said:
However I extracted GSM.nb from softbank 1.33.761.4 ROM and GSM.nb from HTC 1.18.416.1ROM which both should be radio 1.14.00.10 but the files are different, so I guess the locking is done in the radio itself (??).
Click to expand...
Click to collapse
Oooh, that *IS* an interesting (and unpleasant) development. Sounds like imei-check has annoyed some people with good connections to HTC
Richard
rsolomon said:
Unless I missed it, no one has been able to cook Hermes (or any of the new format) ROMs.
Richard
Click to expand...
Click to collapse
If it is impossible, the person who has contract with softbank will have much trouble. Because they have to upgrade their devices till 1st of April in order to use internet connection. Softbank announced that we would not be able to connect to the net without upgrading to new rom.
uedam said:
If it is impossible, the person who has contract with softbank will have much trouble. Because they have to upgrade their devices till 1st of April in order to use internet connection. Softbank announced that we would not be able to connect to the net without upgrading to new rom.
Click to expand...
Click to collapse
Where is this announced? My understanding is that it is not possible to use "Direct Internet" if you don't have the latest ROM but you can still access the internet via normal packet communication - it's more expensive though.
chainbolt said:
Where is this announced? My understanding is that it is not possible to use "Direct Internet" if you don't have the latest ROM but you can still access the internet via normal packet communication - it's more expensive though.
Click to expand...
Click to collapse
Sorry, my explanation was not correct. You are right. Thanks.
Just got a X01HT after Dec, version is 1.09. After reading all these threads, is it possible to use "DownGrade_SPL.rar" downgrade to 1.04 as I know sim unlock is still not available yet, just want to use chinese rom instead..........
Thks,
hi there,
please reaqd the wiki and the sticky threads on this board, the solutions ar eposted there.
cheers,
Thks, just tried and it successfully downgrade to 1.04......so now I can flash the chinese rom or i need to make it super CID before that??
I have the same case as yours. I tried to flash the rom to HK version but failed, so I installed cestar instead
mj13 said:
i need to make it super CID before that??
Click to expand...
Click to collapse
yes, you are right.
riderhk said:
I have the same case as yours. I tried to flash the rom to HK version but failed, so I installed cestar instead
Click to expand...
Click to collapse
Just tried flash it to HK rom and it worked....
mj13 said:
Just tried flash it to HK rom and it worked....
Click to expand...
Click to collapse
How can you make it? I have downgraded to 1.04. But can not flash the ROM
(Cause the CID. How can you make the CID??)
wiccawaiwai said:
How can you make it? I have downgraded to 1.04. But can not flash the ROM
(Cause the CID. How can you make the CID??)
Click to expand...
Click to collapse
1.04 has a bug. even if you get an error message when you try to burn a rom from another company, do nothing with your device and run the same update again on your pc. you can update the rom this time.
qtotter said:
1.04 has a bug. even if you get an error message when you try to burn a rom from another company, do nothing with your device and run the same update again on your pc. you can update the rom this time.
Click to expand...
Click to collapse
My system hangs when I run the flash program second time, so my x01ht is still in Japanese version
riderhk said:
My system hangs when I run the flash program second time, so my x01ht is still in Japanese version
Click to expand...
Click to collapse
is your bootloader 1.04?
mj13 said:
Thks, just tried and it successfully downgrade to 1.04......so now I can flash the chinese rom or i need to make it super CID before that??
Click to expand...
Click to collapse
Hello mj13,I looked around the posts and I could not find any solutions to downgrade my X01HT shipped after Dec from 1.09 to 1.04.Would you please tell me where did you find it or how to finish it?
And ,since downgraded to 1.04 ,does that mean I can unlock my X01HTto use another SIM card using the v2a version unlocker?
Thank you vey much.
qvik123 said:
Hello mj13,I looked around the posts and I could not find any solutions to downgrade my X01HT shipped after Dec from 1.09 to 1.04.Would you please tell me where did you find it or how to finish it?
Click to expand...
Click to collapse
http://wiki.xda-developers.com/index.php?pagename=Hermes_Howto_Bootloader104
qvik123 said:
And ,since downgraded to 1.04 ,does that mean I can unlock my X01HTto use another SIM card using the v2a version unlocker?
Click to expand...
Click to collapse
If its pre December 2006 yes, if it's post December 2006 no.
qtotter said:
is your bootloader 1.04?
Click to expand...
Click to collapse
yes, already downgraded to 1.04.
Would you mind try to upgrade the rom again? If it doesn't work, please let us know
Hi,pof!Thank you very much for answering my question on the 1.09 to 1.04 topic.But I still got some questions.In the link you gave me it says I can not downgrade my bootloader unless I go to the IMEI something website and pay some dollars.Is that the only way to downgrade my bootloader?
And you told me even if I downgraded my bootloader,I still can not unlock my phone.That means,if I downgraded,I can burn other language rom (like English)but I can not use other company's SIM card.Am I right?
Sorry to bother you.Hava a good day!
Sorry to post it again after giving you a private message.
qvik123 said:
Is that the only way to downgrade my bootloader?
Click to expand...
Click to collapse
Legally yes, as you have SPL-1.09 now.
qvik123 said:
And you told me even if I downgraded my bootloader,I still can not unlock my phone.That means,if I downgraded,I can burn other language rom (like English)but I can not use other company's SIM card.Am I right?
Click to expand...
Click to collapse
Yes, because softbank 1.14 radio doesn't allow to be upgraded even if you flash another ROM this radio will be kept in your device.
Ok so I have a little problem with the whole 1.09 -> 1.04 thing.
I have been searching for a couple days or so and gathering some information about it, but I don't think that anyone has had my problem yet. I have a pre-Dec. x01ht, and I stupidly upgraded to 1.09 (don't ask why; I'm still kicking myself). So after trying to downgrade with a couple different versions of the 1.04 provided here with no avail, I found the downgrade_spl file that has been floating around. Each time I keep getting the same problems.
When I active sync with my computer and start the downgrade (upgrade?) process i get past the first preliminary check with the phone and when it jumps to the second check, the phone resets into the tri-color screen for about half a second, and then a white upgrade looking screen. after that the phone checks itself and everything says "ok", but it never resyncs with the computer. The computer stays on the screen that would show a progress bar, but after it hangs there it gets an error screen. i also tried doing everything from the boot mode (the tri-color menu), and that also gets an error. when i try from the boot mode, the both of the progress bars start, but before either go anywhere they both the computer screen comes up with an error in the program. it asks me if i want to recover or view the file, and recover also doesnt work.
Has anyone else had this problem, and if so how did you go about solving this dillema?
ok guys and girls. I just put in a request to have my phone replaced because of screen issues. I have SuperCID unlocked my phone, and have the XDA live running on it right now with radio version 1.27. What do i need to do to make it looked like the phone has never been messed with?
I just don't want them to call me back and give me @#$% about it.
Thanx for the help.
how about flash the rom it came with
You can flash the original ROM version and language. But the SuperCID stays. Unlikely that they'd spot this unless they examine the phone deeply.
I sent a SuperCID'ed and SIM unlocked Cingular 8125 in for replacement about 7 months ago and it was replaced without question. I know they're different devices, but that's my experience.
k thanx for the help guys
hey im sending my device in with screen issues as well, and i have the 1.34 radio is there any way to get it back to the 1.16 radio it came with. i tried to flash it back but it never starts upgrading
I handed in my bricked JASJAM a couple of days ago for "warranty repair". No word yet whether the warranty will cover this or I will have to pay the MB swap.
SSPL Tool will work for this.
koolhand79 said:
hey im sending my device in with screen issues as well, and i have the 1.34 radio is there any way to get it back to the 1.16 radio it came with. i tried to flash it back but it never starts upgrading
Click to expand...
Click to collapse
You should not have to worry about the CID, but it might be better if you flash the old ROM and radio. SSPL is the way to go if you can't flash it back to what is was.
Yeah, hopefully SuperCID isn't a problem, but it would be nice to have a way to reverse it some time in the future, especially now that Des's SSPL makes it redundant for most people.
abubasim said:
I handed in my bricked JASJAM a couple of days ago for "warranty repair". No word yet whether the warranty will cover this or I will have to pay the MB swap.
Click to expand...
Click to collapse
How much do you think that it will cost to replace the mother board?
kyphur said:
SSPL Tool will work for this.
Click to expand...
Click to collapse
i tried the SSPL tool with this and still nothing. i get the BL screen with the SSPL and 1.09.ds but it never starts to upgrade the radio. it just sits at 0%
koolhand79 said:
i tried the SSPL tool with this and still nothing. i get the BL screen with the SSPL and 1.09.ds but it never starts to upgrade the radio. it just sits at 0%
Click to expand...
Click to collapse
Des SSPL uses spl 1.09 which does not have 'rtask' command, so you must use a radio upgrade in NBH format, not in NBF as you're probably using now.
koolhand79 said:
i tried the SSPL tool with this and still nothing. i get the BL screen with the SSPL and 1.09.ds but it never starts to upgrade the radio. it just sits at 0%
Click to expand...
Click to collapse
When I updated my radio today (for the first time), mine sat at 0% for about 2.5 minutes before moving directly to 4%, and eventual success. Are you sure you're waiting long enough?
pof said:
Des SSPL uses spl 1.09 which does not have 'rtask' command, so you must use a radio upgrade in NBH format, not in NBF as you're probably using now.
Click to expand...
Click to collapse
ok i am using the nbf and not the nbh. any advice on how to get this radio in nbh. i have searched the WIKI and maybe im missing something. if so just point me in the right direction. thanx
RabanJr said:
How much do you think that it will cost to replace the mother board?
Click to expand...
Click to collapse
The price seems to vary a bit depending on the country. A couple of guys on the dead hermes thread have done it. This post shows that the prices charged by HTC America and HTC Europe vary significantly.
just to ask, if i use the aku 2.3, radio 1.16 rom full update from the wiki site, will it change everything back for me or will i have to use the sspl program? I just want to make it look like verything is fine.
Flashed WMXL 0.20 yesterday. All fine. I stupidly installed a WM2003 program that seems to have edited the graphics driver. Now the thing wont boot past the HTC splash screen. I've tried flashing, same rom, different t-mobile roms etc. No luck, always same error.
What gives?
Installing a program does not usually brick a device.
And if your graphics driver has been modified,I suggest you do a hard reset on your device.
If that is not helping,please provide your SPL and Radio version,also Cid status and so on ,see who can help you here.
Spuddy said:
Flashed WMXL 0.20 yesterday. All fine. I stupidly installed a WM2003 program that seems to have edited the graphics driver. Now the thing wont boot past the HTC splash screen. I've tried flashing, same rom, different t-mobile roms etc. No luck, always same error.
What gives?
Click to expand...
Click to collapse
Sounds like you're flashing & writing before reading. I'm guessing you went straight to the WM6 rom and didn't do any of the SIM or CID unlocking. Read the following threads and you should discover what you need and probably loads more too...
The Hermes Bible - points to all you need to know
http://wiki.xda-developers.com/index.php?pagename=HTC_Hermes
Common upgrade problems (including yours)
http://wiki.xda-developers.com/index.php?pagename=Hermes_UpgradeProblems
Good luck in your discoveries
Thanks for your advice. I have managed to flash a hungarian T-Mobile ROM to my device and am now going to make is supercid so I can put WM6 back on. Thanks again.
Spuddy said:
Thanks for your advice. I have managed to flash a hungarian T-Mobile ROM to my device and am now going to make is supercid so I can put WM6 back on. Thanks again.
Click to expand...
Click to collapse
Congrats and have fun flashing - it's addictive.
I'd suggest that you read and try Olipro's Hard-SPL before you go any further. This appears to be the answer to many of our prayers because you should be able to recover a bad radio flash. (I'm guessing that the 1.04 version will become most popular)
Hard-SPL, Or How to Not Brick Your PDA Ever Again
http://forum.xda-developers.com/showthread.php?t=296722
Spuddy said:
. . . a WM2003 program that seems to have edited the graphics driver . . .
Click to expand...
Click to collapse
What program was that, if you don't mind my asking?
abubasim said:
What program was that, if you don't mind my asking?
Click to expand...
Click to collapse
DotPocket.
http://www.dotpocket.com/pocket-pc-software.html
just to dispel the myth;
SPL 1.01MFG Flashing via mtty is NOT faster than using the RUU; HTC do not deliberately slow down the process, that's just bloody stupid; the reason it can take longer is if you include a Radio ROM, because flashing a radio takes sodding ages, but can people please learn that using a proper NBH is a smarter and safer way to flash their Hermes.
I second that. this myth appeared because 1.01MFG was the first bootloader that allowed us to flash unsigned, but it didn't allow to flash a radio. So there was the general "feeling" that signature checking was slowing down the process, but it was not: the slowness is caused by flashing the radio.
True, but from strictly a ROM cooker perspective, its not faster. It takes time to build/run the RUU & when you're testing cooked roms, its just far easier to fire up the sspl 1.01MFG and lnb the new os.nb directly.
I understand safety to be the presence of BL v1.10.Oli at location 50020000.
Consequently, I keep this version flashed and test out cooked ideas (currently I'm working on the ATI video issue so I've been flashing a lot of test roms) using your 1.01MFG sspl bootloader.
Expanding on this, I believe that production cooked ROMs should include your 1.10.Oli SPL bootloader from a safety perspective based on my understanding that the BL is flashed first in the RUU under the control of the 1.09Des SSPL loader. This will guarantee a safety net should something go wrong during the OS and/or Radio flashing portion of the process. I would also imagine that this is why you state that RUU flashing is safer too.
Maybe this should be SOP whenever a new production ROM is released by Operators too: Repackage everything into a sspl that also loads 1.10.Oli. Of course, when HTC takes their inevitable next steps in this "spy vs. spy" battle, all this may be invalidated...
Here's an interesting thought: Your bootloader advancements have actually helped Operators since using this technique should result in far fewer bricks being returned for new devices. Now the question is this: does this cost HTC I wonder? Or to put it differently: who sucks up the cost of a bricked Hermes that is replaced in warranty. Whomever this is is very happy with you Olipro and likely to offer you a job as a top developer . Conversely, whomever sucks up the cost is gonna put a contract out on you....
JK: The fact is this: both have a contract on you b/c you've invalidated CID
When I run the RUU, I'll open the Windows Media Player to play the MP3 files, and the update process will be finished in 2-3 minutes.
I guess my major question is this:
At what time during the RUU flashing process is the bootloader flashed? If its the first thing to be flashed then my points above are valid. If not, then everybody who flashes needs to insure that they have 1.10.Oli in flash before stripping the bl out of any ROM they wish to flash. Perhaps we could begin to go through production ROMs and designate those that have had this done with another column on the Wiki.
Sleuth255 said:
At what time during the RUU flashing process is the bootloader flashed?
Click to expand...
Click to collapse
In the order it is placed on the NBH file, generally IPL & SPL are the first.
Sleuth255 said:
If its the first thing to be flashed then my points above are valid.
Click to expand...
Click to collapse
Yes they are: the HardSPL is flashed but the process continues with the current bootloader on device... but after the flashing process ends (or fails) HardSPL is there, which lets you recover the bad flash because even if radio is b0rken the device is seen as SuperCID. Only those with radio bootloader 0108 will need to flash a hardSPL based on 1.09 to be able to recover, the rest will be fine with the one based in 1.04.
pof said:
HardSPL is there, which lets you recover the bad flash because even if radio is b0rken the device is seen as SuperCID. Only those with radio bootloader 0108 will need to flash a hardSPL based on 1.09 to be able to recover, the rest will be fine with the one based in 1.04.
Click to expand...
Click to collapse
But there isn't a 1.09 hardSPl yet, no?
VivaErBetis said:
But there isn't a 1.09 hardSPl yet, no?
Click to expand...
Click to collapse
no, but if someone manages to bork their radio AND can't get into the OS, then something can be done.
Olipro said:
no, but if someone manages to bork their radio AND can't get into the OS, then something can be done.
Click to expand...
Click to collapse
I happen to be in this exact situation. Have bootloader 1.09 and a corrupt radio (which is why I tried to reflash and ended up with a brick). Any ideas?
/politby
politby said:
I happen to be in this exact situation. Have bootloader 1.09 and a corrupt radio (which is why I tried to reflash and ended up with a brick). Any ideas?
/politby
Click to expand...
Click to collapse
no... not quite; you need a Hard-SPL bootloader first; or, you need to be able to boot Windows.
Olipro said:
no... not quite; you need a Hard-SPL bootloader first; or, you need to be able to boot Windows.
Click to expand...
Click to collapse
that's what I thought. Any forecast on when (if) you'll have one available?
politby said:
that's what I thought. Any forecast on when (if) you'll have one available?
Click to expand...
Click to collapse
no... I mean you either need to have flashed on a Hard-SPL before you buggered it up, or you need to be able to still get into Windows after buggering it
Olipro said:
no, but if someone manages to bork their radio AND can't get into the OS, then something can be done.
Click to expand...
Click to collapse
But, will you publish a 1.09 Hard SPL? I will be a good protection measure for those who got the radio bootloader 0108 (like me ).
VivaErBetis said:
But, will you publish a 1.09 Hard SPL? I will be a good protection measure for those who got the radio bootloader 0108 (like me ).
Click to expand...
Click to collapse
well, if you flash 1.04 and bugger up your radio, then of course I'll send you it to flash on, but since it's essentially Des's work, I'm leaving it to him to make his own formal release .
Olipro said:
well, if you flash 1.04 and bugger up your radio, then of course I'll send you it to flash on, but since it's essentially Des's work, I'm leaving it to him to make his own formal release .
Click to expand...
Click to collapse
Ok. Fortunately I don't need it ***yet***. Thanks Olipro.
BTW: I got your 1.10 version installed and it works very well. Thanks.