Related
According to the http://wiki.xda-developers.com/index.php?pagename=PB_KITL_HERMES i need to have "any valid signed dlls from a hermes/tytn device. You will need to copy that file 3 times and rename them to stk_service.dll, ril.dll and rilgsm.dll".
Please help me to find this files.
[email protected] said:
According to the http://wiki.xda-developers.com/index.php?pagename=PB_KITL_HERMES i need to have "any valid signed dlls from a hermes/tytn device. You will need to copy that file 3 times and rename them to stk_service.dll, ril.dll and rilgsm.dll".
Please help me to find this files.
Click to expand...
Click to collapse
It's this "file"...not "files". Grab a Hermes. Copy a valid dll three times. Rename each copy. Do the kitl thing.
Ninja1
Could you please clearify what do you mean by.
Grab Hermes.
Copy a valid dll three times. Rename each copy. Do the kitl thing.
Another problem is that i have bricked HTC Tytn.
Help me please.
Another problem is, where i can get Full Version of Microsoft Plaform CE 5.0.
[email protected] said:
Help me please.
Another problem is, where i can get Full Version of Microsoft Plaform CE 5.0.
Click to expand...
Click to collapse
http://www.microsoft.com/downloads/...50-D311-4F67-9FB3-23E8B8944F3E&displaylang=en
if you try this method, you dont need valid rills.dll,
Here you are just creating dummy rills. This method will take some 2-3hours to compile but it should get you out of the sh!t if you have no valid files..
this quote taken from JBO
"I've unbrick my phone!! Type 2 i think (stuck on windows screen).
I've used the superdave's method with Platform Builder. So, the steps:
- Download Windows CE 5.0 Trial Edition. It's a 2.6Mb file but others components will be downloaded during install (around 2 Gb for me, so be patient!). Choose to install ARMV4I processor platform (not the x86 selected by default).
- Run Platform Builder, File menu -> New Platform
Select "SAMSUNG SMDK2410: ARMV4I"
- Build OS menu -> check "Copy files to release directory after build"
- Build OS menu -> check "Make run-time image after build"
- Build OS menu -> click "Build and Sysgen"
One more time, be patient, tyhe compilation may take 20min.
After compilation successfull:
- Build OS menu -> Open Release Directory.
Copy 3 DLL's from this directory and paste in another (i.e. your Desktop). Rename them as stk_service.dll, ril.dll and rilgsm.dll
Copy the renamed DLL's back in the Release Directory
- Target menu -> Release Directory Modules -> Add the 3 DLL's
- Run your Hermes in KITL debug mode (COM MANAGER + POWER + RESET)
- In Platform Builder, Target menu -> Attach device
- Wait that the phone starts (may take 10min)
- You are in Windows Mobile !!
I had copy SSPL_HERM.exe to my MicroSD card before the operation. For that, I've used the SDcard adapter shipped with my MicroSD card and connect on a colleague PC with a 7-in-1 card reader.
So, once my phone was started, i've clicked SSPL_HERM, and after, I've followed the procedure for the pof' UNLOCKER v3.
Then flash a new ROM
So, for all who have an Hermes stuck on the windows screen, follow this method and unbrick it in 30min !!
Have a good day
PS: sorry for my approximative english!"
Mal..
malrose - thanks for your detail instructions.
I will try do this tomorrow.
i'm sorry, but this is very unclear to me...
Or, this KITL mode... I've never seen one on my phone so far, just can not activate it at all!
Anyone, please report, is KITL mode possible at all on DoCoMo and Softbank japanese ROMs...
Also, when one enters KITL mode using "healty" phone, what's displayed on screen?!?
sorry again.
Zgembo said:
i'm sorry, but this is very unclear to me...
Or, this KITL mode... I've never seen one on my phone so far, just can not activate it at all!
Anyone, please report, is KITL mode possible at all on DoCoMo and Softbank japanese ROMs...
Also, when one enters KITL mode using "healty" phone, what's displayed on screen?!?
sorry again.
Click to expand...
Click to collapse
Not all roms have kitl enabled. Press either power+comm+reset or comm+ok+reset..
I have just installed Microsoft CE 5.0.
Now try to do all you says.
KITL assistence needed
Hi,
I allready posted this in the Bricked Hermes Thread, but that thread is getting a bit busy
When trying the method of Superdave as described in http://wiki.xda-developers.com/index.php?pagename=PB_KITL_HERMES i get:
3195 PID:39ceb52 TID:39ceb2e !ERROR: NK!SC_CreateLocalView: failed opening "\windows\wince.nls"; error=2. Expect boot failure!
3198 PID:39ceb52 TID:39ceb2e !ERROR: NK!SC_CreateLocalView: make sure "wince.nls" is present in your image.
3201 PID:39ceb52 TID:39ceb2e Data Abort: Thread=839ce8ec Proc=802b3410 'filesys.exe'
3202 PID:39ceb52 TID:39ceb2e AKY=00000003 PC=03f8e83c(coredll.dll+0x0002e83c) RA=03f8e814(coredll.dll+0x0002e814) BVA=04000000 FSR=00000007
3206 PID:39ceb52 TID:39ceb2e Data Abort: Thread=839ce8ec Proc=802b3410 'filesys.exe'
3208 PID:39ceb52 TID:39ceb2e AKY=00000003 PC=03f8e83c(coredll.dll+0x0002e83c) RA=03f8e814(coredll.dll+0x0002e814) BVA=04000000 FSR=00000007
3464 PID:39ceb52 TID:39ceb2e Data Abort: Thread=839ce8ec Proc=802b3410 'filesys.exe'
3466 PID:39ceb52 TID:39ceb2e AKY=00000003 PC=80016e5c(NK.EXE+0x00016e5c) RA=80016e3c(NK.EXE+0x00016e3c) BVA=03f31528 FSR=00000007
Any ideas of fixing this?
Ooohhh yeahhhhhhhhhhhhhh.
HTC Tytn was recovered.
Thank all for help.
This method realy works, when devices hang on Windows Mobile Screen.
hi
i try to open microsoft window ce 5.0 through my pc but it shows error and can't open
i also download .net framework but same problem shows
any solution that how to use this software
malrose said:
Not all roms have kitl enabled. Press either power+comm+reset or comm+ok+reset..
Click to expand...
Click to collapse
Where can I find a ROM that has KITL enebled. I've tried two different, none has.
So how can I use this method if my hermes is not kitl enabled? In fact I have two dead hermes devices and I cannot enter in KITL mode on none of them. To flash other roms is impossible... as I'm writing this I'm installing on my pc the Win Ce platform builder and I really really hope not to waste time in trying this recovery method for two hermeses wich cannot start in kitl mode.
how to enable KTL MODE i can not enter this mode i tried
how to enable KTL MODE i can not enter this mode i tried
COMM manger - softreset
and
Comm manger - ok - soft reset
Comm manger - ok - power - softreset
all this is not work to me
why or how to enable this mode on my phone
hi
I need your help to fix my O2 Atom Exec.
i wanted to upgrade my ROM in to the WM6, at the bigining i copied the "diskimage_Ver.nb0" & "EBOOT.nb0" on my memory card. and got my Atom Exec into the bootloader , after download complited the LCD got dark, i got it on bootloader and start the "Device Software Update Utility" and clicked on "Next" until "Upgrad" was shown.When I clicked on "upgrade" this error was shown:"CONNECTION ERROR" . What should i do to fix it?
Thanks.
I'm looking for your answer.
donot ever try thru SD card.. there is a chance that you may brick your device.
Goto bootloader mode first then u run DSUU.
Now after i did that, it dosent work with DSUU .it show "error connection".and my divice shows the upgrade fail
How many files you have in the upgrade directory? Normally it should contain 6 files:
- Device Software Update Utility.exe
- diskimage_Ver.nb0
- EBOOT.nb0
- ExtendedRom.img
- nova_pda_033105.mot
- vl1d_pda_Ver.mot
It will always shown connection error if one of these files is missing
I have all of them,
It seems feasiable to full downloadig the Rom from SD(memory card), but i need mor files:
"diskimg.nb0 , eboot.nb0 , dm.nbo , flash.img , agent.mot , mot.mot , CPLD.img , assetInf.img , extended.img , Mdoc.img"
If it's possible to upgrading with them how can i rech them ?
hello...!!!?
can enybody help me with this case? I need Your Help. Please. . . .
shaemna said:
hi
I need your help to fix my O2 Atom Exec.
i wanted to upgrade my ROM in to the WM6, at the bigining i copied the "diskimage_Ver.nb0" & "EBOOT.nb0" on my memory card. and got my Atom Exec into the bootloader , after download complited the LCD got dark, i got it on bootloader and start the "Device Software Update Utility" and clicked on "Next" until "Upgrad" was shown.When I clicked on "upgrade" this error was shown:"CONNECTION ERROR" . What should i do to fix it?
Thanks.
I'm looking for your answer.
Click to expand...
Click to collapse
Why did you do this?! No one gave out instructions to flash anything using SD CARD in the first place! Of course you will get connection error because bootloader is not functioning. Remove your SDCard, start bootloader mode, and flash the normal way.
I did that but it's not worked. and got me "error connection", i saw some where that if i do it in the that way (with sd) it's worke and beacuse of that i did it in that wey, now what should i do? how can upgrad my ROM or downgrad it, my divice is alredy ded, how can i get it alive? help me
shaemna said:
I did that but it's not worked. and got me "error connection", i saw some where that if i do it in the that way (with sd) it's worke and beacuse of that i did it in that wey, now what should i do? how can upgrad my ROM or downgrad it, my divice is alredy ded, how can i get it alive? help me
Click to expand...
Click to collapse
can you go into bootloader mode?
yes it's go to the bootloader but when run DSUU plase of the last version of the rom and radio is empty, when i click on UPGRAD it get me ERROR CONNECTION
shaemna said:
yes it's go to the bootloader but when run DSUU plase of the last version of the rom and radio is empty, when i click on UPGRAD it get me ERROR CONNECTION
Click to expand...
Click to collapse
I'm sorry. I don't get you. You can go to bootloader, but you get an error. Can you post a screen shot of the error? so, I will know what to do.
How can I uplod picturs?
server is busy it get me Network Error (tcp_error) and cant upload it
the doucument of it is:
(the upgrade page)
Your Divice software is about to be update from:
divice CE image version:0
divice Radio image version:
to:
CE image version: 7210621
Radio image version: R060711N-MN2ARC-RS00011
.......
PLEAS CLICK update to continue
when i click upgrade it show me the fowloeeng error
ERROR:CONNECTION ERROR
THE DIVICE SOFTWAR UPDATE IS HAVING TROUBLE CONECTING TO YOUR DIVICE
PLEAS CHEKE
1)YUOR DIVICE IS PROPLY CONNECTED TO THE USB CABLE OR ...
.
.
.
now what should i do?
do you have any other USB to mini-USB cable? try changing it... The ones used for SD Card readers or Digital Cameras are the same, and do it again.
i do that in all of my USB ports and they are same and get me error conection again
Is there any wey else to inistall a ROM on my divice?
1) Is windows recognizing your device?.. (Do you have activesync installed?)
2) Did u try using different USB cable ?
3) Are you logged on as administrator?
4) Did you remove SD card before going to bootloader mode
5) What is the screen content when you go to boot loader mode
6) Before connecting the device go to bootloader first, then connect the device and then run DSUU
7) Activesync may install device drivers for your device so try installing activesync?
Thanks
when i get my divice in to the bootloader it's display:
===========MN2 Bootloader=
Jun 13 2006 20:41:44
copyright (c) 2006 Quanta cor
poration
CPLD Ver: A0060109
***********************
*Using '<-','->', 'Enter' *
*to choose what you want *
***********************
(1)debug module through UART
(2)jump to DM
enter your selection:
when i conect it to pc( as administrator user) the fallowing line was shown:
USB connected , waiting for download command...
and my computer beeping and found new hardware but not connected to activesync(4.5) , then i start DSUU and when start to upgrade computer show me "ERROR CONECTION" and my divice show me this note:
! ! ! Please use DSUU in OS mode and sync with pc first ! ! !
Usb transfer Fail
please help me
1. We get the most first sewing of Xda-atomexec-eng-20060614_r060428n_ex0028.exe (only by this sewing restore was able)
2. We drag out the files of eboot.nb0
3. We copy on miniSD in a root directory.
4. We insert miniSD in Pocket, enter in bootloader (Camera+SR)
5. We wait inundated while.
6. We take out a miniSD, enter in bootloader, start sewing on PC, connect to USB (it is needed to put to death in the processes of AS)
We are sewn!!!
Rom: 1.60.00 Ger
Datum (Date): 12/03/03
Radio: 1.06.01
Protokol: 1337.16
ExtRom: 1.60.08
---
At StartupScreen:
R 1.06.01
G 1337.16
D 1.60.00Ger
I have this T-Mobile Edition and try to upgrade this MDA with:
C_ShekharAKU3.5c.R40.P24_public
C_ShekharAKU7.0c.R40.P24_public
(Downloaded as recommandet here)
After doubleclick
Code:
HimaUpgradeUt.exe
the program start, but after a while it says, there is a error/problem, i should retry.
When I start to try something with the "bootloader" (on-switch, Action-button, reset) he explain me, i can´t install this version, cause the langua.
So pls. help a noob (first-timer of rom-modification), maybe u have a help-page in german too (Or step by step), cause all what i found at your wiki confuse me too much, cause i never heard somethin about this all - even how the extract a .nbf-file.
Thx for help
llbasha's guide
==================================================
6 steps to successfull Himalaya/WM2k5 upgrade.
==================================================
Note:
The Radio_.nbf is an optional component,
not included in this archive.
Get your favourite Radio ROM at http://buzzdev.net
====================================================================
1. Start your device in bootloader mode by pressing and holding down:
DPad + PowerButton + ResetButton
After a second release ResetButton, then release the rest of them.
Your screen will show word "Serial" at the top.
You are in bootloader mode now.
2. Place your device in the cradle, ensuring that the cradle
is plugged directly into a USB port on your PC and not to a hub
and that the power supply is connected to the cradle.
It is also a good idea to disable any screensavers on your desktop PC.
Once your device is cradled, the text on the screen will change to "USB".
3. Run HimaUpgradeUt_noid.exe
4. Sit back and wait for the Congratulations screen to be displayed
on your PC. Your device will still be displaying 'Upgrading radio stack, please wait',
but as long as the PC says it is done, then its all OK.
5. Detach your device from the cradle.
6. Now you have to hardreset your device.
Press ResetButton and hold down CameraButton + RecordButton.
Hold them pressed until the "Boot Options" menu appears on the screen.
Select the options as follows:
(for selecting use RecordButton, change values with CameraButton)
Enable KITL -> NO
Clean Registry Hive -> YES
Format Storage -> YES
When done, press DPad and wait until OS starts.
wow - ma, thx; perfectly :d:
It worked, no i have a version of 7.04.c, i guess win 6.0
---
Just few problems left:
1.) fixed
2.) Is there a german version anywhere???
3.) edit: my mistake; fixed
4.) I read, there is no problem of downgrade it (no, i don´t want), but from where i should get the german version for downgrading)
5.) My mda was without simlock (I could use every phonecard), i hope i still can ))
Edit2
6.) I have the program PowerLOC Destinator (a Navigation Program); when i would start, he tell´s me: Invalid PocketWizard Setup package
I guess Navigator is not made for win 6, cause the programm is the original sd-card
7.) At settings i can "switch" wlan; I guess this is just from the OS, cause as i know, a standart mda2 doesn´t have wlan
Background: A guy from phonecompany told me, that t-mobile, switched off the wlan-function, so that i customers doesn´tt know, that his pda can wlan (Branding of t-mobile); but the hardware is inside the pda; They made it at vario 2 and mda pro
Edit3:
Next Problem:
When i connect now the craddle with the mda, i get following error msg.
-Generic RNDIS (PROTOTYPE--Remember to change idVendor-
And ActivSync is not connecting
I duno, how to fix
ActiveSync 4.5 doesn´t work on my w2k-pc, and my mda sais he needs 4.5
With 4.2 and down, i can´tt connect the mda
Anyway, thx, thxy, thx, this was really a good describtion
well, Hard-SPL is released now! sorry for delay, I got distracted elsewhere
[size=+2]NOTE: This is NOT a SIM unlocker - it also doesn't unlock Security for other radios. if you need that, GO HERE[/size]
[size=+2]Donations are always appreciated to the big link in our signature ("elite project"). You can also donate via the link offered in the new Hard-SPL program. Thank you!![/size]
Preparations:
first an important note, if you want to flash more than one Iolite, contact cmonex for additional licenses via http://support.htc-unlocks.com. (the first license is transparently granted and free, so normal users do not need to worry.)
0) this package is for Iolite (Touch Cruise II/2009) devices. for any IOLI***** so far (SSPL loader checks this and gives a warning if needed), afaik there is no CDMA version so all the model variations should be fine.
1) if you have vista, WMDC update is recommended: http://www.microsoft.com/windowsmobile/en-us/help/synchronize/device-center.mspx
Instructions:
read this if unsure how to install Hard-SPL...
1) download latest Hard-SPL package (currently v1.10) from attachment, extract to an empty folder.
2) you must Have Phone Synced with PC in Windows Mobile!!!
3) NEW: internet access is required as the program checks online for updates and license.
4) run Iolite-Hard-SPL EXE on PC, make sure it's launched from a local drive (not through network drive, etc.). if you are on vista, launching as Administrator is strongly recommended, on XP administrator login is required. important: if your AV (norton/symantec mainly) warns about a virus, ignore it, it just doesn't like the packer I used to pack the program.
5) if possible, always use Automatic flash mode (for uses of Manual mode, see troubleshooting section)
6) it will ask you to wait while it prepares for the flashing, press OK. follow steps in the program and then in the RUU.
7) some notes: it should go through without any error messages, if one does pop up, then please follow the instructions included in the error text. if no specific instruction is shown, then ask for help in the thread, but this should not ever occur (as this means a really fatal error occurred).
more notes: when RUU says it will hard reset, do not worry, it is not going to do that. also when it says the flash will take 10 minutes, ignore that, it will only take a minute or so.
8) device should go to a tricolour screen now that says 1.09.C-SSPL, this is the SSPL version, which is temporary.
9) SPL flashes, device automatically reboots, job done.
10) to confirm you got it installed, go into bootloader mode (tricolour screen!) and verify the screen shows 1.09.OliNex, which is the Hard-SPL version.
NOTE: you will not see the SPL version during normal boot, that is the OS version, not SPL!
to enter SPL to check version, fully power the device off by long press of power key, then power on while holding the "volume down" key on the left side of the device. keep holding the volume down key until you see tricolour screen which is the bootloader mode, then release it.
NOTE 2: this is unsigned Hard-SPL. no limitations on flashing ROMs or radio packages. also, this has overwrite protection against HTC RUU's overwriting HSPL with a stock one, so if someone needs to revert to stock SPL for warranty reasons, a stock SPL downgrade package will soon be posted in this post as well. use this relocker *only* if you need to return the phone for warranty, and only use it as last step - after reflashing stock OS and radio. see steps at the end of this post about how to reflash stock SPL.
NOTE 3: do not use this RUU for anything other than SPL flashing (i.e. hardspl or stock spl restore)!!! nothing other than SPL's made by Olinex team (using OliNex custom cert, which is not public) will flash to make SSPL more secure. if you want to flash some other rom, then use shipped RUU or customRUU if you need to flash cooked ROM.
Troubleshooting:
- read the instructions above.
- read the instructions above.
- read the instructions above.
Manual flash mode for USB issues: you should usually go for Automatic flash mode; you must only attempt the Manual mode option if Automatic flash mode or SSPL-Manual.exe already put device in SSPL tricolour screen and you got USB issues. any other errors triggered while running in Autoflash mode will have to be fixed as instructed in the error message.
ModelID checking:
- afaik no CDMA model, so doesn't matter but let me know if you got any problems.
nothing happens on the device, does not enter tricolour screen mode:
- anyone having problems with the device entering SSPL automatically, please make sure you watch the device screen if it asks about running files. also try unchecking advanced usb functionality in settings.
- if it crashes instead of entering SSPL, you need to use Automatic mode.
general usb connection error problems if you get connection error in RUU after the device goes to 1.09.C-SSPL screen:
- try manual SSPL: copy SSPL-Manual-Iolite exe to the device and run it, then when it went to 1.09.C-SSPL tricolour screen and shows "USB" at the bottom in this screen, use Manual option in the Hard-SPL program on the PC.
- make sure device was still synced via USB to the PC at the point of it entering SSPL (the 1.09.C-SSPL screen)!
- try a different USB port
- try different USB cable
- do not touch USB cable during the process especially if it is already a bit dodgy
- also do not use USB hub
- you can also try rebooting your PC
- and you can try using another PC.
- also you can try unticking advanced network functionality in start menu / settings / connections / usbtopc applet.
- another reason for USB connection error: if your PC takes too long to load the drivers (if your device is in bootloader for the first time and perhaps if you are on vista), then if RUU times out, but device still says "USB" on the tricolour screen, just leave it there and re-run the RUU when driver installation finishes.
- finally, you can try disabling antivirus or firewall programs on the PC.
other issues:
- if Enterbootloader.exe fails to run (says missing component or similar), try a hard reset of the device.
- if device reboots instead of going to SSPL screen (1.09.C-SSPL), contact us by PM'ing cmonex. do not PM OliNex user, that is not monitored frequently.
How to reflash Stock/Shipped SPL - STEP BY STEP - FOR WARRANTY REASONS ONLY!:
0. please make sure you already flashed stock ROM and radio, because stock SPL flash is *always* the last step before sending the device in.
1. take the SPL relocker attachment, and run the EXE - this will flash 1.09.0000 stock SPL. simple as that!
2. flash
3. verify if it flashed by checking version in tricolour screen, it should say 1.09.0000.
credits:
first, "OliNex" is a team which means: cmonex + Olipro
Olipro -> EXE program concept that runs on the PC, Hard-SPL concept, server code, maintaining licenses
cmonex -> new PC EXE & SSPL loader for windows mobile and SSPL binary. Hard-SPL binary. (SSPL loader: partially based on haret and old pof&Olipro jumpspl code)
---reserved post---
---reserved---
"IOLI100
SPL-1.09.oliNex
MicroP-Iolite(LED) v5"?
Has it released? It has appeared on the interenet.
Let me see see!
chenjun_conan said:
"IOLI100
SPL-1.09.oliNex
MicroP-Iolite(LED) v5"?
Has it released? It has appeared on the interenet.
Click to expand...
Click to collapse
yes, I've sent it to several people. I'm posting it here too in a sec.
edit: posted
Dan
OK
you are great.
Thank you so much.
Fantastish!
THANK U VERY VERY MUCH!!!
after HSPL and flashing to Rissian ROM it says "Your OS ROM isn' t customized for your hardware Please reflash the proper ROM code or contact the service center' .
In the internet i've read that taking out the battery for 10-15 minutes must help. But it doesn't. Please help!
Great job, big thanks!
@ cmonex was send you a PM, please answer me. Thanks!
Greetings
Baga12 said:
after HSPL and flashing to Rissian ROM it says "Your OS ROM isn' t customized for your hardware Please reflash the proper ROM code or contact the service center' .
In the internet i've read that taking out the battery for 10-15 minutes must help. But it doesn't. Please help!
Click to expand...
Click to collapse
try to flash WWE|Eng and post result here
Nice work as usual guys.
Thread stuck
Dave
After IoliteSPLRelocker, the HSPL' s not working, why? Please help
Thank you
Thank you so much for your hard work.
My Iolite can do do just about anything right now.
Baga12 said:
After IoliteSPLRelocker, the HSPL' s not working, why? Please help
Click to expand...
Click to collapse
You tell us? It what way doesn't it work?
Dave
I tried to test the IoliteSPLRelocker, it flashed correctly, then I again tried to flash the HSPL with mhile my device was in three color mode, but it stops at the 0%, not going more. Stupid of me, of course
So? what about WWE Roms? Does anybody flash them at new HSPL?
thanks very much . it's great'
Baga12 said:
I tried to test the IoliteSPLRelocker, it flashed correctly, then I again tried to flash the HSPL with mhile my device was in three color mode, but it stops at the 0%, not going more. Stupid of me, of course
Click to expand...
Click to collapse
Please help!
max_nya said:
So? what about WWE Roms? Does anybody flash them at new HSPL?
Click to expand...
Click to collapse
Once you have Hard SPL, you can flash any ROM's (Cooked or Shipped) to your device. So put on Hard SPL, find a WWE ROM and flash it .
Baga12 said:
Please help!
Click to expand...
Click to collapse
I've just checked the re-locked and it does contain the correct SPL.
Connect your phone to you PC using AS, and then run the re-locked, once done your SPL should be 1.09 (with the .OliNex) again
Dave
I can flash CE rom, but can not flash radio,
when flash radio , prompt "Error 114: Radio Rom Update error".
on bootloader screen,
working himalaya should show
1. "Radio version";
2. "protocal version";
3. "rom version"
mine show
1. blank;(this line disapearred)
2. "no gsm";
3. "rom version"
have done hard reset and switch between several roms, no use.
My bootloader is 1.03.
Please help me,
my himalaya can only running as PPC now, phone function lost.
So I want to Upgrade Bootloader, I download pnewbootloader and boot106.nB0 from this page:
http://buzzdev.net/viewtopic.php?f=8&t=21036
After I run
-=-==-=-=--=-=-=-=-=-=-=-=-=-=
pnewbootloader -f boot106.nB0
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
I got:
"Do not run this tool unless :\n"
" - you want to downgrade your 5.17 bootloader to 5.15\n"
" - you have somehow managed to overwrite your bootloader and still\n"
" have a working ( ce bootable ) device, and still have the operating\n"
" system running\n"
"\n"
"If the above does not apply to you, press NO\n",
It seems that this pnewbootloader is wrote for xda1/wallaby, not for xda2/himalaya, since wallaby got bootloader version 5.15/5.17.
Anyway, I still click yes to continue.
-=-==-=-=-==-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
C:>pnewbootloader -f boot106.nb0
Copying C:itsutils.dll to WCE:windowsitsutils.dll
Unable to find flash info offset, cannot disable bootloader writeprotect
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-==-=-=-=-=-=-=-=-=-=-
It seems nothing happened,my himalaya is still running in windows.
I download the latest itsutilsbin-20090515,
extract pnewbootloader.exe and itsutils.dll to overwrite the previous one from http://buzzdev.net/viewtopic.php?f=8&t=21036.
The cursur of cmd line keep flicking and nothing happened.
my himalaya is still running in windows.Will it become brick after reset?
Thank you very much