Hi, I'm a newbie here.
I have great interest for purhcasing Softbank X01HT.
At the beginning, I proposed to flash the rom to English verison.
But recently, I see some messages that we cannot downgrade the bootloader 1.09 to 1.04 anymore.
Therefore, I would like to know ........
Is anyone working on the downgrade method for bootloader 1.09 ?
If so, what's the status now ?
Can I expect there will be a new solution coming soon ?
So many questions ..... hope someone can answer me. Thx !
1.09 to 1.04
ok, what I understood is :
1- you can download from 1.09 to 1.04.
see :
Bootloader
The bootloader is the place where you can change the low-level software parameters and some hardware parameters of the Hermes, change and read the ROM and provides information about it.
The bootloader is invoked 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.
The bootloader version is shown for a short amount of time when booting the device. You'll see "SPL-1.0X"
Versions
* 1.04
There is a bug in bootloader 1.04 wich allows you to flash any ROM without a CID check. You have to be in bootloader mode to use this bug.
It's possible to upgrade the RadioROM. You can even flash a patched RadioROM wich is needed to unlock your device.
* 1.06
The bug from version 1.04 is fixed. Without downgrading to a Shipped ROM with bootloader 1.04 that matches your CID it's not possible to flash a ROM with a different CID.
The RadioROM can't be upgraded. You have to downgrade to bootloader 1.04 to unlock your device.
* 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.
"There was a solution posted on this forum", the remaining of it is here, what can be shown :
1. Go to Google, search for DownGrade_SPL.rar (rq : does not work anymore)
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!
6. Download pof's HTC_Hermes_SIM_Unlock_v2a from
ftp://xda:[email protected]_v2a.zip
7. Flash the patched radio rom 1.16, then Reboot.
8. Copy HERM_Unlock_v2a.exe a small PPC app pof wrote into your TYTN memory.
9. Open File Explorer, run HERM_Unlock_v2a.exe on your TYTN and wait about 1 minute until it shows up a completed message. Reboot again!
10. Download mtty.exe from
http://wiki.xda-developers.com/uploads/mtty.exe
11. Disable ActiveSync, and then run mtty.exe, choose usb connection; Enter. You should see USB> prompt. Type in: info 2 . When you see 00000000 or SuperCID string. You are safe and ready to upgrade to the latest TYTN 1.35 Rom with bootloader 1.09.
2- BUT the trick is that it is impossible to SIM unlock even if you downgrade Right now there is no solution, and I don't know when or if there will be. I hope there will be one indeed...
3- you can still change the language, but it is limited in two ways :
for the good news :
http://forum.xda-developers.com/showthread.php?t=281617
for the bad news :
http://forum.xda-developers.com/showthread.php?t=284765
and a good news in process:
http://forum.xda-developers.com/showthread.php?t=284765&page=5
but I don't get exactly how it works...
For more information look around the board, or I will try to retrieve the info.
take care,
I'm looking forward buying the same device
dam
alexnalexn said:
Is anyone working on the downgrade method for bootloader 1.09 ?
If so, what's the status now ?
Click to expand...
Click to collapse
As dam has explained, some time ago we published a method to downgrade the bootloader to 1.04 but this method used imei-check copyrighted files and had to be removed from the forum, some people downloaded the files and it has appeared on chinese and russian sites after we removed it from XDA-Developers, but this method violates imei-check copyright and should not be used, if you are a legal person and want to downgrade the bootloader now you should BUY imei-check unlocker.
I started working on a project to Downgrade SPL by modifying HaRET tool with the help of some other people, we managed to put IPL on ram and jump to it, but we still haven't managed to do it with SPL (the device hangs when copying to memory). Now I'm quite busy and can't dedicate all the time I need for this, but will try to finish it once I know how to copy the SPL correctly... if someone has experience in this and want to help, let me know and I can send you the source of modified haret, but it's still a lot to do... once this is finished there will be a free method to downgrade bootloader, now there isn't.
When bootloader is downgraded to 1.04 you can change the ROM because it has a bug where the CID is not checked if you run the RUU twice. You can also use HERMES SIM & CID unlocker when you have bootloader 1.04. But on softbank x01ht version sold after 1 December 2006 it is not possible to SIM & CID unlock even if you have bootloader 1.04 because the radio is read only and can't be patched. AFAIK no one has knowledge on how softbank did this, and there is no known method to circumvent this yet.
Related
Hi
Im hopeing someone can help me I know this issue has probably been discussed loads of times and im a muppet for doing it, I was looking at different ROM's for my Orange M3100 and thought I would go for the IMATE JASJAM ROM so I could get MSN messenger .... I unfortunatly selected the TELSTRA 1.06 Bootloader ROM and downloaded instead of the 1.04 ( I should have read the posts on this ROM before!). Now I am stuck in bootloader 1.06 and as I have read the only way to get back to 1.04 is to flash with a ROM that is the same as my carrier (Orange UK).... the only Orange ROM is the Romanian one thats just been put on the WIKI, I have tried with this but its coming up Vendor ID error... if anyone can help or tell me how I can go back to 1.04 id be grateful? if not do I just have to wait until orange UK bring out a ROM with bootloader 1.06 ????
Thanks a lot ! James UK
Same problem with Cingular bootloader 1.06
I've the same problem with Cingular 1.34 bootloader 1.06, I try to downgrade with same bios CID (CWS__001 as I read on this forum) to bootloader 1.06 but I receive an error "WRONG VENDER ID" (also if i leave connected my PDA and I restart RUU utility it give me the same error)
I've also tried to install another vendor bios with bootloader 1.06 as suggested but I receive the same error message!!!
Emanuele
Unfortunately, you're stuck unless you either a) wait for a bootloader for your CID or b) pay the $38 to do the super-CID unlock. There's a thread on that stickied, so if you decide to do it, help them out by doing the usb capture.
Thanks... I have already unlocked the device with IMEI-Check.co.uk do you mean this? If I have unlocked it then do you think I should run IMEI check again on the device and it may unlock the CID ? cheers, James
If you run the imei tool again (with the latest version of theire software) it will reverse your bootloader to 1.04 and make your device super CID
This is a patched radio ROM that can be used to remove the Operator SIM lock and CID lock from HTC Hermes based telephones.
It can be used in all HTC Hermes devices, the only restriction is that the device must have bootloader version 1.04
Warning:
If you run this upgrade on any other device than HTC Hermes, you will most probably render it DEAD!
Disclaimer:
This is free to use but at your own risk, I take no responsiblity for any conflict, fault, or damage caused to your phone by this unlocking procedure. It may invalidate your warranty.
Full caution is advised.
Website:
http://pof.eslack.org/hermes-unlocker/
Install Instructions:
Enter bootloader mode on your Phone. To do this, simultaneously hold side OK and POWER buttons together and reset with stylus.
[You should see SPL-1.04 on the top of the tri-color screen, if you see SPL-1.06 you'll need to downgrade the bootloader]
Connect your phone to your computer using the USB lead.
Run the MaUpgradeUt_noID.exe program – this will reflash your phone with a patched radio ROM required to unlock.
Wait patiently.
Once the MaUpgradeUt_noID.exe upgrade completes, it will end up saying "Upgrade Error 114", but the patched radio ROM will be flashed anyway, dont worry about that error!
Soft reset with stylus (Device will not be hard reset and no data will be lost)
Allow your phone to reboot. Once it has, connect to your PC using Activesync, and copy the HERM_Unlock_v2a.exe program onto your phone. Alternatively, copy it to an SD card and insert into your phone.
Run HERM_Unlock_v2a.exe on your phone. Wait about 1 minute.
You should see a "SUCCESS!" message from HERM_Unlock_v2a.exe, after that soft reset your phone.
Process is (hopefully) complete!
If the phone requests unlock code when you put a locked SIM, the code is: 22051978.
Frequently Asked Questions:
Q - How do I know my bootloader version?
A - When you are on the tri-color screen check the number after SPL-X.XX
Q - How do I downgrade to bootloader 1.04?
A - See this comment. I'm working on an altnative method for all devices, but it's not ready yet.
Q - What is the CID and how do I check which one I have?
A - See this comment.
Donations:
I spent some time and money developing this free unlocker, there's no need to pay me for that, but donations are always appreciated. You can find a paypal button to donate on the unlocker website.
Thanks to:
buzz_lightyear, itsme, vijay555, arc, Asukal, machinagod - for the wise advice and support
everyone else in xda-developers.com
History:
v2a [14-11-2006] - bugfix release, thanks to all who reported the problems!
(hopefully) fixed bug where unlock code has to be entered manually
(hopefully) fixed bug where SuperCID was not kept after rom upgrades in some cases
v2 [12-11-2006] - updated to patched radio 1.16
unlocking software provided (HERM_Unlock_v2.exe): thanks buzz for the source of UNI_Unlock_v1 ;-)
SuperCID is now kept after rom upgrades
v1 [05-11-2006] - patched radio 1.13
unlock manually
Notes:
- v2a makes SuperCID sticky after ROM upgrades, those who used v1 or v2 and are still running the patched radio only need to run HERM_Unlock_v2a.exe on the device to keep SuperCID forever.
Download:
HTC_Hermes_SIM_Unlock_v2a.zip
Enjoy!
Sweet
First to say thank you from everybody.
Hi
I´ve finaly unlocked my german MDA Vario II with your patched ROM and it works !!!
Thank you pof, you´ve done a very hard job perfectly !
Scorpio16v
scorpio16v said:
Hi
I´ve finaly unlocked my german MDA Vario II with your patched ROM and it works !!!
Click to expand...
Click to collapse
Glad to hear it worked
Just want to add my thanks and congratulations. Superb work.
Totallytechie
will this working on softbank X01HT?
Great job!!
Dear POF
first of all congratulation you finish your great job
just short term.
Now I could my X01HT from SOFTBANK JP SIM network
unlocked successfully.
please keep it up your engineering skill.
best regards,
Dear jarodcn
As I mentioned above I succeed to unlock my X01HT perfectory
by using master POF's solution.
1. down grade bootloader 1.06 to 1.04.
2. then provide POF's method as described in this thread.
all procedures clearly mentioned in his former thread and comment.
Great to see that it is finaly done !
You did an amazing work there! As my device is already unlocked I cannot test, but I am pretty sure that it works flawlessly ;-)
Will this work on T-mobile Vario II
Or is it for HTC devices/ Roms only?
Should work on all Hermes, definately works on Vario II with Dopod Rom.
mikeycollins13 said:
Or is it for HTC devices/ Roms only?
Click to expand...
Click to collapse
You can belive, it works with the MDA Vario II. It should work with all devices of the "HERMES" class.
God job! and how to downgrade bootloader
Hello pof,
I can downgrade bootloader from 1.06 to 1.04 without Radio patch.
Using files:
1) HERMIMG_IPL1.01_SPL1.04_ONLY.nbh ( Special thanks to pof.)
Get this file from xda-forum ftp-site.
ftp://xda:[email protected]/Hermes/Technical/unlocker-reversed.zip
2) EnterBL.exe, GetDeviceData.exe, ROMUpgradeUt.exe, RUU.dll, RUUUI.dll
Get these files from any Shipped_Complete_Updates.
( Run Updates and getting files from temporary folder.)
3) All files in the same folder.
How to:
1) Conect Hermes to your PC
2) Run M3100v3cUnlock.exe without key-file ( no need payment.)
3) When key-file required, close the M3100v3cUnlock window.
4) Run ROMUpgradeUt.exe
Caution:
It's only bootloader downgrade. When anybody get error with
Free SIM unlocker and bootloader 1.06, you can try this method
before unlocking.
riki0081 from Japan.
Hi,
tried to unlock my T-Mobile Vario II from UK, but the unlock code was wrong...further after I run MaUpgradeUt_noID.exe another error than the one described appeared (forgot which one it was)...can anyone help? Did I do something wrong?
Confirm this solution.
http://forum.xda-developers.com/showthread.php?t=281617
I can downgrade bootloader from 1.06 to 1.04 without Radio patch.
Using files:
1) HERMIMG_IPL1.01_SPL1.04_ONLY.nbh ( Special thanks to pof.)
Get this file from xda-forum ftp-site.
ftp://xda:[email protected]
2) EnterBL.exe, GetDeviceData.exe, ROMUpgradeUt.exe, RUU.dll, RUUUI.dll
Get these files from any Shipped_Complete_Updates.
( Run Updates and getting files from temporary folder.)
3) All files in the same folder.
How to:
1) Conect Hermes to your PC
2) Run M3100v3cUnlock.exe without key-file ( no need payment.)
3) When key-file required, close the M3100v3cUnlock window.
4) Run ROMUpgradeUt.exe
Caution:
It's only bootloader downgrade. When anybody get error with
Free SIM unlocker and bootloader 1.06, you can try this method
before unlocking.
riki0081 from Japan.
Click to expand...
Click to collapse
I succeeded with first solution for downgrading bootloader 1.06 to 1.04
but worry about sim lock , so I use this solution to unlock sim lock and succeed.
thanks POF for your kindness.
Damn pof .. this is crazy .. YOU ROCK!!!
Why is the unlocker tied to the RadioROM upgrade? Anyway you can make the unlocker available by itself?
Vodafone Spain
Hi All
Thanks POF for your hard work here. Question: I have an original Vodafone Spain 1605, I haven't made any Rom/Radio Update, how should I proceed?
My HTC info:
Rom Version: 1.20.164.3
Radio Version: 1.03.06.00
Protocol Version: 32.34.7010.01W
I don't understand if I need to update my Radio version first or just follow your process.
Thanks very mcuh
Excellent - congratulations!
Nice work pof! Hermes=OWN3D!
I am flashing right now and will post results. I am on Dutch T-Mobile Vario II with original shipped ROM (Dutch)
I am getting exited
Does this mean that if we keep this patched radio then we always are going to have an Super CID device ?? That basically means replacing the included Radio.nbf with this patched one on any ROM package Or am I missing something ?
Also is this a stable ROM. My VARIO II has/had 1.05.02 ?
ok so i just recieved my Cingular 8525 today after having my 8125 stolen.
i am trying to successfully install iiwpo but i have encountered a lot of problems so far:
1. i am trying to CID unlock so i can write IIWPO to the extended ROM. on the startup screen i cannot see anywhere that states if i have a 1.04 or 1.06 bootloader so i haven't even attempted to unlock it for fear of damaging something.
2. i can't find a working version of iiwpo. the file that i have downloaded seems to be corrupt and it won't unpack...
i don't want to lose this phone like i did the 8125- please help!!!
p.s. oh and i am also looking for the name of that program that is packaged in with the molski ROM for the universal that places the little red dot in the 'close program' X and asks if you REALLY want to close the program or not. can anyone provide a name for this particular program??
thanks in advance for any help!!!
The hermes doesn't display ipl/spl info at startup like the Wizard did. You have to go into bootloader mode to see it. However, it's already known that your 8525 will be running the 1.34 Cingular ROM which has BL 1.06. To unlock, you have to flash to the v1.30 ROM here which has BL 1.04. Then you can unlock/SuperCID and go back up to whatever ROM you like. SuperCID will give you R/W rights on the ExtRom once it's unhidden using the tools here.
Flashing is much more dangerous on the hermes than it was on the wizard due to the timeframes involved (flash takes 20-30 minutes). Be absolutely sure you have a solid USB connection. Read up on flashing best practices here too before you start. You've got an hour or so of flashing time in front of you:
- downgrade to v1.30
- unlock & superCID
- upgrade to v1.34 again
This is becoming a common issue and there are a lot of people with a bricked Hermes devices, usually because of a WinXP crash, bad USB port, USB hub or pulled USB cable while flashing.
This thread is in the aim of finding a solution to all these common problems: if you are the owner of a bricked hermes, please post your comments here instead of opening a new thread.
There seems to be 3 types of bricked (or dead) hermes devices:
Type 1 bricks: Corrupted radio area: No GSM, No CID, no IMEI
Usual reason for that is flashing whent wrong when RUU was flashing the radio stack (GSM.nb). Other reason can be that you flashed radio from another device (universal unlocker run on hermes, for example).
Within the type 1 bricks, there seem to be two variants:
Type 1a:devices which can boot windows mobile but can't use the phone functions.
Type 1b: devices which can't boot windows mobile and are stuck while booting, see also type 2 bricks below.
Type 2 bricks: Stuck in boot process
Usual reason for that is that flashing went wrong when the RUU was flashing any rom part different than IPL and SPL. Symptoms can vary depending on which is the ROM part affected. The most common is OS because it is the bigger part. Radio is the second most common.
Type 2a: When the phone boots, it goes directly to bootloader mode (tri-color screen)
Type 2b: When the phone boots, it stays in subslpash screen (htc or operator logo)
Type 2c: When the phone boots, it doesn't pass the windows mobile logo
Hybrid Bricks: combinations of both type 1 and type 2 bricks
These usually have a corrupted radio and are stuck in bootloader, unfortunately these are very common too, and the most dificult to repair.
We made a wiki page long time ago whith the solutions that have worked for some people to fix bricks, unfotunately these solutions do not work for everyone, some devices are more bricked than others
First thing you have to do is visit this wiki page and follow the process explained: Common upgrade problems
If you can't repair your brick after following the process, please provide a USB monitor capture in ANSI text format (this is explained on the wiki page too) as this is the only thing that can give us a real idea on what your exact problem is. Please don't come crying and say "help me" because we can't help you if you don't provide useful information, you are in front of a big problem and you will have to loose some hours reading and experimenting before repairing your brick. If you are not willing to loose some hours reading, go and send the device to the service centre for a repair as it is the only valid solution most of the times.
Hopefully after research of everyone in this thread we can find new solutions for some of the bricks
EDIT: Please use axiom's comment below as a template for your comment and attach USB monitor capture: If your bootloader is 1.04 attach capture when trying to flash an extracted radio ROM and when trying to flash a shipped rom update. If your bootloader is 1.06 or 1.09 only attach the usb monitor capture of the shipped update.
EDIT (2007-03-22):
After more than 3 months since this thread started and more than 660 comments, we have now solutions for some bricks, so I compiled the most common on this unbricking guide:
How to unbrick your bricked hermes
Please spend some time reading through the wiki and thread comments before posting desesperately, otherwise you'll get no answer.
The following info may help in isolating the problem and keeping the clutter down.:
I'm including my info.
Model: O2 XDA Trion
ROM Before Flash: Dopod 1.23.707.4
Radio Before Flash: 1.16
Bootloader Before Flash: 1.04
Flash failed at: 6%
Flashing ROM: 1.35.255.2
Flashing Radio: 1.18.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>
Current Device Status: unusable
Hi, I've managed to brick my Hermes as well.. First time on any of my HTC Devices....
Model: Vodafone v1605
ROM Before Flash: Voda Launch ROM
Radio Before Flash: Not sure
Bootloader Before Flash: 1.04
Flash failed at: 8%
Flashing ROM: 1.35.255.2
Flashing Radio: 1.18.00.10
Bootloader After Failure: 1.09
CID Before Failure Super CID: Yes
CID Corrupt: Yes
Radio Corrupt: Assume Yes
No GSM Error: Not got that far
Stuck In Bootloader: Yes
Stuck On Windows Mobile Splash: Not got that far
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>
Current Device Status: unusable
You may already know this, as I posted it in all over the other threads of people with bricked hermes, but I'm posting again to make sure every piece of information is concentrated on this thread, and see if finally this can get us somewhere
HTC bootloader returns data encapsulated in a block between HTCS (start) and HTCE (end), before the HTCE there's always a 4-byte checksum of the data. You're getting a timeout when you query the bootloader for the device's CID, so the output you see is "F" which means failure (T means success) encapsulated in this HTCS/HTCE block, plus the checksum. The CID is read from the security area of the device, found on radio, but the wrong flash corrupted the radio area.
As the CID is not returned, the error you get when flashing the ROM is "CID Not allow (255)". The security level depends on CID, as the device has CID corrupted, the security level returned is FF (255), which means you can't bypass CID check in bootloader.
You both have bootloader 1.09 which does enforce CID checking (as opposite to bootloader 1.04 which has a known bug to circumvent this). This bootloader also only allows updates with bootloader version > 1.09 (and no such bootloader exists yet).
Bootloader 1.04 allows to flash unsigned code in radio with radio bootloader command 'rwdata', but radio bootloader is accessed through command 'rtask' and this command has been removed in following bootloader versions.
All the commands to flash code in bootloader 1.06 and above require the code to be signed (the commands are 'wdatah' and 'lnbs'), and bootloader checks the signature before the code is actually flashed on the device. So modifying a 1.04 bootloader to show itself as 1.10 is not possible because it will return a certificate error and will not be possible to flash.
Command 'lnbs' doesn't check CID, but it is only enabled if device has security level=0, and as your radio is corrupted and your seclevel=FF it will not be possible to use this command to fix it even if you had a signed bootloader, so 'wdatah' is the only command that would allow you flashing code, but 'wdatah' requires a NBH header to be sent, which contains the CID of the update and is checked against the missing CID on your device and will never match (even if you could modify the NBH header and have a valid signature after).
In conclusion, my recommendation to you is that you send the device to service centre to get it repaired and don't try to fix this by yourselves, as you will go nowhere.
Many thanks for explaining it so succinctly Pof, much appreciated. With this error I've learnt a heck of a lot more about the ROM flashing process... I guess it may be time to send the unit for repair!
This is the full report after I soft rest my phone while the USB is still connected. Would any one know what the rest of the data means? I did it in the morning then just left it for the day to see what would happen, I just got back from work.
onj: can you use axiom comment as a template to provide information?
radioerror.txt: I see you're using the Himalaya upgrade utility there... rbmc reads data from memory, but I don't know what is at 0x70010000. It would be better if you can provide a log of hermes RUU.
Model: x01ht
ROM Before Flash: i-mate
Radio Before Flash: 1.07.03.10
Bootloader Before Flash: 1.04
Flash failed at: 0%
Flashing ROM: JASJAR_WWE_19096_19505_11300_AKU_3_2_ship
Flashing Radio: 1.13.00
Bootloader After Failure: 1.04
CID Before Failure Super CID: success
CID Corrupt: don't know
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: stalls
Current Device Status: unusable
I will upload the usbmonitor with using
RUU_HERMES_HTC_WWE_1[1].35.255.2_1.35.255.102_1.08.00.10_SHIP
the upgrading dies after info 3
computer says ERROR [222] Device not responding
that's with all the RUU's that I use and even the full upgrade ROM
Hi, I have a herm 200 an i have a Type 2a bricks (it goes directly to bootloader mode tri-color screen).
But i upgrade with the rom (ME_DT_WWE_1182553_106_10303_Ship) and all run good. but 3 moths later i have the type 2a bricks.
I try with that solution (http://wiki.xda-developers.com/index.php?pagename=Hermes_UpgradeProblems) and others and NOthing.
In screnn say herm200 ILP-1.00 and Her200 SPL-1.04.
ps: sorry my english is very bad.
@onj: Oh ****! You where trying to flash an HTC Universal ROM in your HTC Hermes!! These are different devices, most probably that's what screwed it.
From your attached file I see bootloader does not answer to any command.
@landtd5: please use axiom comment as a template, and attach USB monitor capture when tryng to flash a shipped rom and a radio rom.
Yup, I upgraded with the wrong Rom. After going through the forum for the past 2 weeks I realized what I did. I guess it's time for me to send it to the shop
thanks for you help pof
jash431 Dead Tytn
I had tytn with this rom
"TYTN_me_dt_wwe_1182553_106_10303_ship" which has bootloader 1.04
And I upgraded with
"RUU_HERMES_HTC_WWE_1.35.255.2_1.35.255.102_1.08.00.10_SHIP"
during upgrade stopped and after that I cannot do anything with it
It never answer to any solutions .
Please help me .
USB monitore is attached here .
jash431 said:
USB monitore is attached here .
Click to expand...
Click to collapse
This is not useful: You saved LGS file, please follow instructions in wiki, you need to EXPORT as ANSI TEXT file. Also please use the 1st comment as a template to provide useful information.
Jash431
I exported in ansi text
@jash431: doesn't return anything... when you connect to bootloader on mtty, do you see the USB prompt? does it answer any commands?
Jash431
I'm sorry . this is complete one .
yes I can work with mtty.exe and my info 2 is "HTCSF kEØ(HTCEUSB>"
jash431: hybrid brick with corrupted radio and bootloader 1.09. Send it to repair centre.
jash431
is it theorically possible to fix my tytn . I mean maybe in future someone make a downgrade or SuperCID rom !! .
Because in my country doesn't exist repair center (Iran) . So what can I do ???
then keep it until something is found to fix this, creative solutions to the problem will come to your mind after looking everyday at a $500 brick.
Jash431
Thanks pof for your answer . I'll check my private message every day , for your solution and I remember you whenever I see a 500$ . ( Of course 500$ doesn't exist but you do ).
I Have read allot of data, unbrick tutorials and upgrades suggestions...
but I Still haven't found what is the correct upgrade stages.
As far as I have read from the unbrick suggestions, I've reached to the following order:
1) Upgrading SPL (Enabling KITL)
2) Unlocking
3) Upgrading radio
4) Upgrading Windows
Can someone confirm or recommend/add other steps ?
During the upgrade steps, will the HERMES be usable ?
Unlock first THEN hard spl.
DONT mess with your radio if it works fine, as this is part that can COMPLETELY brick your phone(you may be able to use as a PDA but not gonna be a phone EVER again.)
Load an os(either a stock one OR one of the cooked roms our TOP chefs cook up.), most come as OS only, no radio.
Hope this helps.... Cheers
It is useless for me, I cannot unlock the phone, due to different locking technique.
there are few posts about a locked Jasjam, with no olutions.
all the unlocking process went well, 3 times...
after the unlock process, when I insert the sim, it connects to the network, (indicated with 5 lines) and after about 5 seconds, it disconnect and says :
"The system detected an invalid SIM card"
and asks for unlock code.
now I have the following versions:
IPL 1.01
SPL 1.40.Olipro
Radio 1.16
any ideas ?
The Solution
To unlock Cellcom (Israel) JASJAM, As weird as it sounds, you should disable/deactivate/uninstall/whatever the EYRON Multi language support, which comes pre-installed.
I'll let the experts explain it.
I Dont know if it works for Orange-il Tytn too.
please consider note this in unlock guide ?
Now, which version of HARD-SPL with KITL should I Install... (Link will be helpful)
Please note that I Only Unlock the SIM, and not SuperCID, the .BAT file of the unlocker says:
"CID Unlock: will make your phone SuperCID forever, don't check this if you are unsure. HardSPL will do same effect without loosing warranty."
Olipro ver 7(Hard SPL) This is considered the best for the layman, if you want to develope roms/ programs then you should use ver 9. However, ver. 9 does throw up an error after flashing. There is no problem and olipro said he'd get around to fixing it, BUT.......
Hope this helps...
ultramag69 said:
Olipro ver 7(Hard SPL) This is considered the best for the layman, if you want to develope roms/ programs then you should use ver 9. However, ver. 9 does throw up an error after flashing. There is no problem and olipro said he'd get around to fixing it, BUT.......
Hope this helps...
Click to expand...
Click to collapse
I have upgraded to Olipro V7
When I Boot into bootloader, I see:
IPL-1.04
SPL-2.10.Olipro
But I Still not get any sign of KITL according to this threat (Step 5).
The Device is booting normally, as if I'm not holding any bottons.
How can I check if KITL enabled ?
Do I need KITL while using OLIPRO V7 ?
Orenk,
Have you read the Mr Vanx guides or the wiki? Here are the links:
http://www.mrvanx.org/cms/
http://wiki.xda-developers.com/
WB