Related
Dear All,
I've tried to upgrade to ROM Hermes_1.18.416.1_1.18.416.101_1.14.00.10_WWE_Ship
and unluckly cable loosen and I reset the phone.
Since it's in the middle and can't success enter the Windows Mobile,
but the bootloader was updated to 1.06.
Now I can't flash any ROM either
HER_DopodAsia_1237074_1060010_WWE_SHIP or the new one.
The tools on "imei check" even can't recognize my phone.
Any one can help me on this issue, please?
Thanks in advance.
Try the steps here, let us know the results:
http://wiki.xda-developers.com/index.php?pagename=Hermes_UpgradeProblems
If you don't fix it with the proposed solutions attach USB Monitor capture in text format as explained in the bootom of the page.
I have the same issue, and sent it to service, and now I have the phone back and they could not fix it, so got no radio or imei number, so none of the FAQ will work for me.
So I have an expensive paper weight.
Hi,
ME TOO!!
I recently had a power cut (yes, a lights off power cut!) that killed my PC half wat through installing the Cingular English CWS__001 1.34.502.1 09/21/06 ?? 1.16.00.00 32.53.7018.01H 14955.2.3.0 ROM onto my SPV 3100.
Now SPV 3100 will boot to the ROM I was running prior to the upgrade but I can't use the telephone. I'm also not able to rerun the upgrade as it got far enough through the process to upgrade my bootloader to 1.06 - therefor rendering me unable to load another ROM.
Before the crash I was using the Imate ROM as below and M3100 was sim unlocked and running on o2 3G
i-mate English CDL__001 1.20.305.3 07/21/06 1.20.305.104 1.07.03.10 32.41.7010.02H 14955.2.3.0 1.04
I have also tried imei without any joy.
the PDA part of my M3100 still works but the phone is dead. I have been told that if you can get the latest radio installed then you satnd a chance of the phone part working.
We need a hack to get bootloader 1.4 back on the phones.
Please help.
Thanks
My one now is a photo frame which one show "HTC" or "Windows Mobile",
at least your one is a PDA.
There are nothing in "info 2" and so nothing can be flash into it.
Is it possible to have something written CID and IMEI to phone in mtty
and let the flash rom success?
i am in the same situation like yhlee. Pof, i have reply your pm and ready to upload the result file to FTP. where should i upload to?
Thanks
oh i forgot to say, mine is even worst. as soon as i turn on the unit. it will go right into bootloader without press any button.
The USB Log is too large (around 2MB)
and can't upload, any suggestion?
Thanks.
rnc1688 said:
oh i forgot to say, mine is even worst. as soon as i turn on the unit. it will go right into bootloader without press any button.
Click to expand...
Click to collapse
This can be fixed by bootloader commands 'set 14 0' and 'task 8', will reboot your device and boot into OS again (but no GSM yet!)
yhlee said:
The USB Log is too large (around 2MB)
and can't upload, any suggestion?
Click to expand...
Click to collapse
Upload it to xda-developers ftp:
ftp://xdaupload:[email protected]/Uploads/Hermes/
USER: xdaupload
PASS: xda
POF, file have been uploaded, file name= rnc1688
Thanks
'set 14 0' and 'task 8' didn't work
@rnc1688: It starts the flashing process, but you get a "CID not allow (255)" error because your CID is corrupted and you are in bootloader 1.06.
Is not booting WM5 after "set 14 0" in mtty.exe? If it's not booting WM5 you'll not be able to flash bootloader 1.04 and bypass CID checking.
so i guess my unit is bricked now.
I've upload the file which named yhlee.txt.
However, I'm going to send the unit for service.
Hope they can fix.
Any way to make it show the bootloader screen on start-up
everytime?
"set 14 1" doesn't work after push the RESET button.
Thanks.
@yhlee: U're getting exactly the same error as rnc1688. Device in bootloader 1.06 which has corrupted CID, however you say you can go into OS, so it would be possible for you to downgrade the bootloader so it does not enforce CID checking.
yhlee said:
Any way to make it show the bootloader screen on start-up everytime? "set 14 1" doesn't work after push the RESET button.
Click to expand...
Click to collapse
Try "set 1e 1" and then "set 14 1", you'll boot stright into bootloader.
@rnc1688: If you want to go WM5 try this:
"set 1e 1" and then "set 14 0", you should be able to boot stright into OS.
no luck either
grrr!!!... command "set 14 [0|1]" is working fine in 1.04 here to switch boot into WM5 or boot in bootloader mode... probably different in 1.06??? I don't have a 1.06 now to test
Mine one is just showing "Windows Mobile" but stuck there,
but seems rnc1688 one is a PDA but my one is nothing.
I've sent to distributor for service.
Thanks you pof.
yhlee said:
I've sent to distributor for service.
Click to expand...
Click to collapse
Let me know when they fix it... i'm curious about if they will fix it with 1.06 or they will downgrade to 1.04 first.
I got a correct message back from the service company, and they will not fix a bootloader 1.06 unless the original rom has been release with it, I was told that is HTC policy on this.
here is what I've done and what happened:
my ROM was HTC 1.18.255.3 07/22/06 with bootloader 1.04 then I ran "HERM_Unlock_v2a.exe" on the device but I didn't use "HTC_Hermes_Radio_for_SIMunlock_v1.16.00.69" to save time and i wanted a CID unlock only.
after "SUCCESS!" message from "HERM_Unlock_v2a.exe", I connected my device via USB to PC and started to upgrade to Cingular 1.31.502.1 08/30/06 with aku 2.6 and bootloader 1.06 but when I get the "ID ERROR",without disconnecting the USB, I switched back to ugrading to previous ROM HTC 1.18.255.3 and the Processe started with no problem untill 98%, then suddenly upgading interrupted a message came saying connection error or somting like that!
since then my device is stuck on windows mobile screen and I've tested solutions in the "Hermes_Upgrade Problems" page and tried using the "Hermes SD Card flashing" method, But It seems impossible to flash my phone agian.
Help me PLEASE,HELP
someone help me please!
POF can't you help me please
I think Pof is away until 3rd december, I have the similiar problems with my second hermes, if you have then use mtty to see if you have an corrupted cid using info 2.
Do you have the original rom to go back on if so that will fix your problem.
I've used mtty to send some commands to my device and it answers to some of them but It just stop responding when I type "info 2" or "info 3".
and i tried this in mtty:
"
USB>checkimage
IPL CRC checksum = 0x9FCC6BEB
SPL CRC checksum = 0x3BF03635
CE CRC checksum = 0xC0E1751A
ExtROM CRC checksum = Total Block= 1024
dwBlockIndex= 1024
Address Error1!!!
Get checksum ERROR!!!
0x0
Radio Image CRC checksum =
"
again It stop responding
also tried upgrading, no matter which ROM I try, it just can't connect to device.
and thanx for your relpy.
hi, since there is NO htc service center available around me I have to do something about it myself but my phone is still dead and I'm using a nokia 1101. PLEASE someone help me, pof are you back? can you help me?
I've tried all in this page:
"http://wiki.xda-developers.com/index.php?pagename=Hermes_UpgradeProblems"
and this one too:
"http://forum.xda-developers.com/showthread.php?t=280733"
and tested qtek 2020 rom but no use.
from what I've found out my device hang up and stop responding when it gets the "INFO 2" or "INFO 3" or "TASK 32" or perhaps any thing involving CID so no upgrading utility is able to connect to it, the only thing is to connect to it using "mtty.exe" which I've tried any command found here, but no use again.
and my SPL is 1.04
can anyone help me?
mht220 said:
I ran "HERM_Unlock_v2a.exe" on the device but I didn't use "HTC_Hermes_Radio_for_SIMunlock_v1.16.00.69" to save time and i wanted a CID unlock only.
Click to expand...
Click to collapse
Wrong, you also need a patched radio to CID unlock. Running only the exe file without the patched radio has no effect on the unit.
mht220 said:
from what I've found out my device hang up and stop responding when it gets the "INFO 2" or "INFO 3" or "TASK 32" or perhaps any thing involving CID so no upgrading utility is able to connect to it, the only thing is to connect to it using "mtty.exe" which I've tried any command found here, but no use again.
and my SPL is 1.04
Click to expand...
Click to collapse
Please attach usb monitor capture when trying to flash a ROM and a radio ROM. Otherwise can't help you.
here is exported files from usb-monitor:
and tanx for your reply
uuh... there must be something really wrong with it, no response to bootloader commands. If no sd card flashing is possible, I would suggest you to send it to service centre too.
pof said:
...I would suggest you to send it to service centre too.
Click to expand...
Click to collapse
It's a difficult option for me, as I should send it to a foreign country to service center,so are you sure there is no way like erasing somewhere using mtty?
pof said:
... no response to bootloader commands...
Click to expand...
Click to collapse
but it respond to some of them in mtty.exe e.g. "erase", "set" and some other.
pof said:
...If no sd card flashing is possible...
Click to expand...
Click to collapse
no it would stuck in "checking..." forever
tanx
HI,
I have same exactly problem on my spv m3100: since sept06 I've tried every kind of Unlock software,upgrade ROM and method found in xda..In mtty bootloader (spl 1.04) respond at every command but not "info 2","info 3" and "task 32".Sd card method works but if you try to upgrade other ROM,in your screen "loading..." and then "checking..." hangs on because the ROM upgrade must to match CID (I suppose..).I'll wait the next ROM Upgrade and ORANGE won't release it until gen07..
warrio said:
I'll wait the next ROM Upgrade and ORANGE won't release it until gen07.
Click to expand...
Click to collapse
it seems your problem is like mine if so, I don't think ANY normal upgrade can solve your prolem 'cause it can't connect to it.
so don't wait and send your device to service center, if you can.
I'm in your same conditions:there's no repair center here so I have to wait Orange who release a upgrade Rom (I hope asap..).
Hello everybody - can anyone help me at this moment. I am right now sitting with my Hermes connected through USB. I was flashing the standard ROM with RUU_HERMES_HTC_WWE_1[1].35.255.2_1.35.255.102_1.08.00.10_SHIP. Unfortunately it stopped at 5% some half an hour ago. I prefer to ask you before disconnecting it. Please help!!!!!!!!!
OK, having no answer I decided to disconnect it and look for an answer. Now I know that I have a 1000 USD brick and no possibility to put it back to work.
I now suspect that the upgrade did not work properly because my device had a CID lock. That is quite strange however, because I bought it on the open market without any commitment to any GSM operator.
I am now stuck on the tricolor bootloader screen with SPL 1,09.
Basing on the post: http://forum.xda-developers.com/showthread.php?t=285157 - especially on the lines:
"1.09
You can't downgrade to bootloader 1.04 by flashing a Shipped ROM. However imei-check.co.uk is able to downgrade the bootloader.
There was a solution posted on this forum, but it was stolen from imei-check and was removed. If you are not willing to pay you have to wait until another solution is developed.
The RadioROM can't be upgraded. You have to downgrade to bootloader 1.04 to unlock your device.", despite seeing info on the website, I paid to imei-check the 20 pounds.
So far I only lost money, time and nerves trying to downgrade or "repair" my hermes. Nothing works. If anybody has any suggestions please share on the forum or PM me.
BTW I started the whole process with SPL 1,04.
Sounds to me like a flaky USB port which is why it stopped at 5%. Try another port in the rear of your PC and re-flash. Be sure to follow the mantra:
Windows XP, screensaver, powersave disabled
No other programs running.
i had a similar problem probably with the flaky usb port as Sleuth255 mentioned. trying with a different pc is another option if you have one and that was what i did with success.
im not sure about the hermes.. but i know on the wizard as long as you could get to the bootloader screen (the RGB screen) that your device isnt bricked yet.. i would follow the other suggestions about usb ports and using different pc's, i bet you can make your $1k work for you again
Try:
Go into bootloader by pressing down both the POWER button and SIDE OK together and using the stylus at the same time to press the RESET button at the bottom.
Make sure you have disabled the USB connection in ActiveSync, before trying to connect to the bootloader:
File --> Connection settings --> uncheck "allow USB connections"
Connect your USB-Cable
Download mtty.exe. Start it and connect to USB
When you see "USB>" Type "info 2". You should get: "HTCS" + CID + (4-byte checksum) + "HTCE". Remeber what CID you have.
Look for a Shipped ROM that matches your CID
Download and flash it using a different USB-Port or PC than the last time
Afterwards you will be able to use the file that you got from imei-check. The imei-check downgrader/unlocker only works if you've got a working operating system on your device.
After typing "info 2" in mtty.exe I get the following line
HTCSF kEŘ(HTCEUSB>
Which of those is the CID? I cannot find any matching one in the Wiki.
corrupted CID by wrong flash.
OK, I have now the confirmation of the diagnosis - as I was suspecting.
Can I now have some help in the solution?
Some people succeded with the method described as "problem 5" here:
http://wiki.xda-developers.com/index.php?pagename=Hermes_UpgradeProblems
but some others don't succeed and have a brick. Try the steps on the wiki, if you are not able to fix it this way, send it to repair centre.
Following the steps from point 5 of the given website, I only get the following lines:
USB>password 0000000000000000
HTCSPass1.CMˆËHTCEUSB>
USB>set le 1
USB>erase a0040000 c80000
HTCST ÚČŇHTCEUSB>
USB>erase a0cc0000 c80000
HTCST ÚČŇHTCEUSB>
USB>erase a1940000 640000
HTCST ÚČŇHTCEUSB>
USB>set le 0
USB>
Unfortunatelly nothing changes.
I've the same problem. I was flashing the HTC 1.18.416.1 1.18.416.101 1.14.00.10 but the process has stopped to 89 % and now the phone is in bootloader mode spl- 1.06 and don't enter in windows mode !!! My cid is HTCSORANG001a#USB> I hope that i've not a brick !!!
mtadeuszak said:
Following the steps from point 5 of the given website, I only get the following lines:
[...]
Unfortunatelly nothing changes.
Click to expand...
Click to collapse
Your bootloader is 1.09 and you'll not be able to flash anything because the CID will not match. Send it to service centre.
deika95 said:
I've the same problem. I was flashing the HTC 1.18.416.1 1.18.416.101 1.14.00.10 but the process has stopped to 89 % and now the phone is in bootloader mode spl- 1.06 and don't enter in windows mode !!! My cid is HTCSORANG001a#USB> I hope that i've not a brick !!!
Click to expand...
Click to collapse
Your phone is not trashed, but there is no rom matching your CID yet. You should have cid unlocked it before flashing a rom with BL 1.06.
Try to boot OS again using "set 14 0" (see wiki, "problem 4"), if that doesn't fix it (chances are it will not), then wait until orange releases a rom upgrade with CID "ORANG001".
I've try the procedure "Problem 4" but after "write nand success" and sr it don't start. My cid is always ORANG001 with spl-1.06
pof said:
Your bootloader is 1.09 and you'll not be able to flash anything because the CID will not match. Send it to service centre.
Your phone is not trashed, but there is no rom matching your CID yet. You should have cid unlocked it before flashing a rom with BL 1.06.
Try to boot OS again using "set 14 0" (see wiki, "problem 4"), if that doesn't fix it (chances are it will not), then wait until orange releases a rom upgrade with CID "ORANG001".
Click to expand...
Click to collapse
Please Pof try to help me. Where can i find that rom ? Thanks
You can't find it at the moment. It's not released yet
sn00x said:
You can't find it at the moment. It's not released yet
Click to expand...
Click to collapse
But you think that it will be available ? Thanks
Yes it will surely be released I think. But nobody knows when. Perhaps tomorrow, perhaps next year.
It bet it will be listed here when it's available.
Hi all,
I know this has been asked and answered lots of times, I have read all the wiki posts I could find, but still I'm not 100% sure that I understand correctly, hence this question.
I have a Dopod 838 Pro (Hermes) which I have SuperCID'ed and loaded with bootloader 1.09.
My ppc gets stuck on the windows mobile screen, and in addition I can see in the HTC subsplash screen the "NO GSM" indicator for a flick of a second.
I can go into bootloader and connect with mtty.
In another thread (and also in the wiki), it is suggested that the only way to get my machine back, is first to downgrade to SPL 1.04, and the only way to do this since I'm at 1.09 and no windows, is to purchase the IMEI-CHECK tool .
Am I correct in understanding this? or is there another way?
Thanks for any and all help.
Chris
No, I think you quit reading a bit soon.
With the new unlocker v3 and Des' SSPL flashing method, you no longer need to downgrade from 1.09 to flash anything. Simply find the newest version of the ROM and Radio you are trying to load and run the exe. Hard to believe, but it's really that easy.
Hi and thanks for the reply,
will the v3 unlocker work even if I cant boot my ppc and so I cant connect with activesync?
The only thing I can do, is boot into bootloader on the ppc and connect using the mtty tool.
Can I still use the method you suggest?
Thanks again,
Chris
T-mobile unlocker bootloader 1.09
chrisvor said:
Hi and thanks for the reply,
will the v3 unlocker work even if I cant boot my ppc and so I cant connect with activesync?
The only thing I can do, is boot into bootloader on the ppc and connect using the mtty tool.
Can I still use the method you suggest?
Thanks again,
Chris
Click to expand...
Click to collapse
Im having the same problem
Hi X01HT Rock....
can I ask u a favor? If you find a solution please PM me... I will do the same
thanks
Chris
you can't use the unlocker unless you can copy it to the device and run it from there.
from xda wiki
Problem 5: Device shows NO GSM when booting
* The radio stack is screwed, you don't get GSM signal and the phone says unknown SIM status
* Device won't start after trying to unlock it with HTC Universal Unlocker (HTC_Uni_SIM_Unlock_v1)
Here is how to fix it:
1. Disable activesync on your computer by right click on activesync icon -> connection settings -> uncheck "allow USB connections".
2. Put your Hermes in bootloader mode
3. Connect device to computer using USB cable.
4. Open mtty.exe and select USB port, then connect.
5. Hit enter twice, you will see the "USB>" prompt.
6.
Type the following commands (do not copy paste!!!)
USB> password 0000000000000000
USB> set 1e 1
USB> erase a0040000 c80000
USB> erase a0cc0000 c80000
USB> erase a1940000 640000
USB> set 1e 0
7. Reset your phone and put it back in bootloader mode
Click to expand...
Click to collapse
now copy unlock v3 to your phone, and run on the phone.
download radio 1.34 and run on your pc, while your device and pc is in activesync mode.
I believe all of this is in the wiki.
lpsi2000 said:
I believe all of this is in the wiki.
Click to expand...
Click to collapse
yeah, but the guy's device is locked with a 1.09 bootloader. we might need POF's help here.
please PLEASE guys, i need your help here (POF are you reading this?)
My machine was made SuperCID using v2a before all this sh*t happened and it was running smoothly.
It now seems that some of the mtty commands I read and tried to apply resulted in the SuperCID status to go away and now it's *scrambled* (info 2 results in "HTCSF kEØ(HTCE"). So now I cannot flash ANY rom into it even if I could.
I get to the bootloader (SPL 1.09) and also up to the windows mobile splash screen.
Also at the HTC subsplash I can see the "No GSM" msg for a fraction of a second.
Please help me unbrick this baby. I can't afford to buy another one
cant run the mtty that way
I have tried to run the password and every thing it I am having some problems with the communication
HTCST ÚÈÒHTCEUSB>
USB>password 0000000000000000
HTCSPass1.CMˆËHTCEUSB>set 1e 1
USB>erase a040000 c80000
HTCST ÚÈÒHTCEUSB>erase a0cc0000 c80000
HTCST ÚÈÒHTCEUSB>erase a01940000 640000
HTCST ÚÈÒHTCEUSB>set 1e 0
USB>
this is what happens then I try to rest the phone but it just goes back to whatit was doing.
I think that I have a language problem here.
chrisvor said:
My machine was made SuperCID using v2a before all this sh*t happened and it was running smoothly.
Click to expand...
Click to collapse
SuperCID unlocker v2a would not have worked on SPL 1.09. It might have said that unlocked successfully, but it wont have unlocked. Only unlocker 3 will unlock a SPL 1.09 phone. You'll have to keep hammering on the "bricked hermes" sticky. Someone will get round to helping you in a day or two.
I put this in the wrong place and cannot delete. Sorry for the misspost.
Hello,
I have seen on the Universal thread a way to completly format the device. After that lot of people who were stuck in windows mobile screen have recovered their device.
I dont know if it is working with hermes.
http://forum.xda-developers.com/showthread.php?t=289325
X01HT Rock said:
Im having the same problem
Click to expand...
Click to collapse
Me too....!!!! Can't solve this problem
.VIBE said:
you can't use the unlocker unless you can copy it to the device and run it from there.
from xda wiki
now copy unlock v3 to your phone, and run on the phone.
download radio 1.34 and run on your pc, while your device and pc is in activesync mode.
Click to expand...
Click to collapse
I did what you said before but can't solve the problem
.VIBE said:
SuperCID unlocker v2a would not have worked on SPL 1.09. It might have said that unlocked successfully, but it wont have unlocked. Only unlocker 3 will unlock a SPL 1.09 phone. You'll have to keep hammering on the "bricked hermes" sticky. Someone will get round to helping you in a day or two.
Click to expand...
Click to collapse
@.VIBE:
My original SPL at the time when I applied v2a unlocker was 1.01, and v2a unlocked it, I verified it with "info 2" in mtty just after, and also after all this mess started.
Something I did while trying to get out of this mess, changed my SuperCID status and corrupted it.
Is there a way to make it superCID again if the only thing I can connect with is mtty?
Thanks
Chris
You guys with bricked phones need to carefully read and understand ALL of the "dead hermes? corrupted radio? Post comments here" sticky!
Everything that POF currently knows on unbricking your device is in there also Superdave has some help for those who can get into KITL mode. Even then not every brick is recoverable at the moment, but you need to spend some time reading to find out!!
I've noticed that POF's not as quick as he used to be in replying to these kind of threads, I surmise he could be a little fed up with repeating the same thing over and over again, but I could be wrong.
Best of luck to you and my advice at the moment to anybody else coming across this is to SuperCID your phone and always try to keep your bootloader at SPL 1.04 (upgrade using mtty) as it makes recovering from bricked phones much easier.
Im having the same problem
There Is A Way Of Downgrading From 109.
Search Google For Downgrade_SPL Then Do This.
1. Go to Google, search for DownGrade_SPL.rar
2. Connect your tytn to PC and wait until activesync completed.
3. Run M3100v3cUnlock.exe. Once you see checking device.... in DOS box and whilte screen on your tytn, close the program (Dos box) immedaitely.
4. Run ROMUpgradeUt.exe and follow the japanese wizard to complete the boot loader downgrade.
5. Reboot your tytn and then put it into bootloader mode agian, you should see SPL-1.04. Great!
Cheers
@Mousey
You need to be able to fully boot into the OS to connect to activesync and the phones described here can't. The only other way I know of downgrading from 1.09 to 1.04 is from KITL mode which not all ROMS have. Full details are in the sticky I mentioned earlier.
OK guys, here it is... Hard-SPL for all of you that want to **** around with your devices a little bit more than everyone else.
It's 2.60 and has an unrestricted rbmc as well as allowing you to lnb files and once again access the AT interpreter/Bootloader via rtask, although I should point out that the command for the AT interpreter is now "rtask 7" - "rtask b" performs a security check that wastes time... I put this in for completeness more than anything to have a similarity to the newer MFG bootloaders.
and yes... I can count, I know I've gone from V7 to V9, but there was a previous build I made internally.
and finally... when it flashes, it will go to 100% then your device will restart; the RUU will throw an error but just click the exit button, all is well.
This bootloader will also allow you to overwrite it... but this requires especially modifying the NBH to do so... otherwise it's just skipped
Code:
[b]CURRENT FEATURES[/b]
-SuperCID
-no file signing required
-no password required to authenticate with bootloader
-bad NAND can be recovered with "task 2a"
-bad NAND can be recovered by flashing an OS
-SPL protected from all HTC retail SPLs being flashed by accident (to bypass, use SSPL)
-IPL protected from all flashes; protection against bogus NBH's
-bad NAND can again be checked for with "info 8"
-version displays 2.60.Olipro
-no longer tries to read bad NAND - should fix whitescreen issue
-lnbs command converted to lnb
-rtask command ported back; "rtask 7" replaces "rtask b"
-can be overwritten with a special NBH
[b]ChangeLog[/b]
[b]Hard-SPL-2.60[/b]
-ported rtask back into the bootloader
-special NBH can be made to overwrite SPL
-lnbs now converted to lnb
-special credits in info 7 command :)
[b]Hard-SPL-2.30[/b]
-Unlocked RBMC command; internal release only
[b]Hard-SPL-2.10[/b]
-based on a newer SPL base; bugfixes.
-IPL flashing disabled to prevent bogus NBHs bricking your device.
[b]Hard-SPL-1.40[/b]
-repairs a bug that affected SPL being replaced by retail ones.
[b]Hard-SPL-1.35[/b]
-addresses an issue for those with Real Bad Blocks to prevent whitescreens.
[b]Hard-SPL-1.30[/b]
- removed password for wdata commands and rbmc etc.
- activated "task 2a" to allow recovering bad blocks as well as flashing valid OS.
- Disabled SPL flashing; this SPL protects you from writing over it by accident.
- Bad Blocks "info 8" command works now allowing you to check for bad blocks.
[b]Hard-SPL-1.13[/b]
- Patched NAND check; bad NAND ignored, valid OS can be flashed to recover bad blocks.
[b]Hard-SPL-1.11[/b]
- Flashing Radio BL 0108 now supported
- Downgrading SPL no longer allowed.
- rtask command removed.
- new RUU interface required to flash ROM files.
[b]Hard-SPL-1.10[/b]
-Initial release; SuperCID and no signing required
-Compatible only with Radio BL 0107
-has rtask commands for accessing radio facilities.
2-3 times I try to flash, but without success. Always have a error 262 or 260 and progress bar stay on 0%....After 20 min I tried again and some thinks happened very fast that I can't explain, but latter I see ipl 1.10 olines, or similar, and see spl 2.60. After soft reset I see my "old" spl 2.30Olipro. One more time I start and now is ok. IPL -1.03 SPL-2.60.Olipro
10x Oli.
Great works
well... I was pretty chuffed myself
Great one buddy!
太棒了。
Good job，thanks
Necessity to replace v7 with v9?
Hi Olipro,
Congratulations on the new version of Hard-SPL.
One quick question though, is it advisable to replace the v7 with this new v9 on our phones at present?
I mean is the level of protection more or less the same for the average person who does not want to piss around with phone flashing as much as the pro's do.
Regards.
Trezona said:
Hi Olipro,
Congratulations on the new version of Hard-SPL.
One quick question though, is it advisable to replace the v7 with this new v9 on our phones at present?
I mean is the level of protection more or less the same for the average person who does not want to piss around with phone flashing as much as the pro's do.
Regards.
Click to expand...
Click to collapse
why don't you read the feature list and figure it out for yourself
Olipro said:
OK guys, here it is... Hard-SPL for all of you that want to **** around with your devices a little bit more than everyone else.
It's 2.60 and has an unrestricted rbmc as well as allowing you to lnb files and once again access the AT interpreter/Bootloader via rtask, although I should point out that the command for the AT interpreter is now "rtask 7" - "rtask b" performs a security check that wastes time... I put this in for completeness more than anything to have a similarity to the newer MFG bootloaders.
and yes... I can count, I know I've gone from V7 to V9, but there was a previous build I made internally.
and finally... when it flashes, it will go to 100% then your device will restart; the RUU will throw an error but just click the exit button, all is well.
This bootloader will also allow you to overwrite it... but this requires especially modifying the NBH to do so... otherwise it's just skipped
Code:
[b]CURRENT FEATURES[/b]
-SuperCID
-no file signing required
-no password required to authenticate with bootloader
-bad NAND can be recovered with "task 2a"
-bad NAND can be recovered by flashing an OS
-SPL protected from all HTC retail SPLs being flashed by accident (to bypass, use SSPL)
-IPL protected from all flashes; protection against bogus NBH's
-bad NAND can again be checked for with "info 8"
-version displays 2.60.Olipro
-no longer tries to read bad NAND - should fix whitescreen issue
-lnbs command converted to lnb
-rtask command ported back; "rtask 7" replaces "rtask b"
-can be overwritten with a special NBH
[b]ChangeLog[/b]
[b]Hard-SPL-2.60[/b]
-ported rtask back into the bootloader
-special NBH can be made to overwrite SPL
-lnbs now converted to lnb
-special credits in info 7 command :)
[b]Hard-SPL-2.30[/b]
-Unlocked RBMC command; internal release only
[b]Hard-SPL-2.10[/b]
-based on a newer SPL base; bugfixes.
-IPL flashing disabled to prevent bogus NBHs bricking your device.
[b]Hard-SPL-1.40[/b]
-repairs a bug that affected SPL being replaced by retail ones.
[b]Hard-SPL-1.35[/b]
-addresses an issue for those with Real Bad Blocks to prevent whitescreens.
[b]Hard-SPL-1.30[/b]
- removed password for wdata commands and rbmc etc.
- activated "task 2a" to allow recovering bad blocks as well as flashing valid OS.
- Disabled SPL flashing; this SPL protects you from writing over it by accident.
- Bad Blocks "info 8" command works now allowing you to check for bad blocks.
[b]Hard-SPL-1.13[/b]
- Patched NAND check; bad NAND ignored, valid OS can be flashed to recover bad blocks.
[b]Hard-SPL-1.11[/b]
- Flashing Radio BL 0108 now supported
- Downgrading SPL no longer allowed.
- rtask command removed.
- new RUU interface required to flash ROM files.
[b]Hard-SPL-1.10[/b]
-Initial release; SuperCID and no signing required
-Compatible only with Radio BL 0107
-has rtask commands for accessing radio facilities.
Click to expand...
Click to collapse
I stuck in Tri-Color Screen, how can restore !?
Please help
cm1437 said:
I stuck in Tri-Color Screen, how can restore !?
Please help
Click to expand...
Click to collapse
Kill yourself.
Dear Oilpro,
I mean during flashing 2.60, it shown error msg,
then i try to recovery, but it can't.
Now i reboot it, it stuck in Tri-Color Screen,
What can i do!?
Please comment
cm1437 said:
Dear Oilpro,
I mean during flashing 2.60, it shown error msg,
then i try to recovery, but it can't.
Now i reboot it, it stuck in Tri-Color Screen,
What can i do!?
Please comment
Click to expand...
Click to collapse
run the rtask command for completing the flash
What's meaning of rtask?
Where can i found it?
pasan said:
run the rtask command for completing the flash
Click to expand...
Click to collapse
err... no, don't... that's not what it's for at all
Olipro said:
Kill yourself.
Click to expand...
Click to collapse
You are right... there is no stupid question... just offensive answers...
Olipro said:
Kill yourself.
Click to expand...
Click to collapse
Thats funny
cm1437 said:
Dear Oilpro,
I mean during flashing 2.60, it shown error msg,
then i try to recovery, but it can't.
Now i reboot it, it stuck in Tri-Color Screen,
What can i do!?
Please comment
Click to expand...
Click to collapse
Exactly the same problem. I was using 2.30.Olipro.
Stuck in bootloader.
Tried set 14 0 without success...
Please, ¿any idea?.
I've talked with Olipro in the chat and he kindly help me to manage the problem:
- Disconnect Active Sync USB connection.
- Start MTTY
- Push Enter to saw CMD> or USB>
- Type
set 16 0
and pres ENTER
and it's solved....
My error was a noobs error; I started the bootloader manually but the RUU starts a SoftSPL so it doesn't runs. Now, I've upgraded to 2.60.olipro without problems. I recognized that I'm stupid
Thanks Olipro!!!!!
Got error 282 and prompted with view documentation or recovery. Used mtty and set 16 0 to recover back.
Tried a couple of times but with same error.
Yes, get the same tri color Bootloader screen.
I reflash a new OS, problem solved for me att least.