Hi there
Didn't know if this was the right place to post. But im developing this tool for flashing ROMs onto HTC devices. And when the flash process is done, im displaying the IMEI number on the display, so that the users can pack the devices back to their original box, without having to disassemble the unit, to find the right IMEI.
In the previous phones i developed this tool to, which covers MAGICIAN, ALPINE, BLUEANGEL, SABLE and BEETLES i did like this:
rtask a (enter radio bootloader)
rtask 7 (enter GSM Command debugging
AT+CGSM (get an info string that contains the IMEI)
I dont know if this was the right procedure, but it worked for me. But the new TyTN device doesnt recognize the rtask 7 command, and i just can't seem to find a way to get the IMEI no. now. If someone knows about this, please help.
Thanks in advance.
jbj
Here is the wiki page with information of the Hermes bootloader:
http://wiki.xda-developers.com/index.php?pagename=Hermes_BootLoader
I think the problem is that when you do "rtask a" you are in radio bootloader, and then you cannot enter "rtask 7" because rtask is not a valid radio bootloader command.
Is your tool available somewhere?
Unfortunately not... were using it in out company, because HTCs tool only flashes 1 phone at a time. We are selling ~1 million devices per year, so we needed another tool so i've developed this tool, so we can flash up to 16 devices at a time. But the company owns the program and the code, so i can't share it. BUT i'm willing to answer any questions which i can answer, regarding the flashing process.
OK, regarding your answer, in the "old" days i could do an rtask 7 after entering radio bootloader.... but it doesnt seem to work anymore. But there might have been another way.
ok, have u tried without "rtask a"... I mean just issuing "rtask 7" and "AT+CGSM"?
I don't know what you're using to debug this, but in mtty or minicom you cannot see the output when you talk to radio/gsm bootloader. A good idea is to use a USB monitor software and see what the bootloader really replies, I listed some here: i like the one from HHD software.
http://forum.xda-developers.com/showpost.php?p=1023730&postcount=43
Let me know if you have a better / easier way to talk to the radio bootloader
Ahhh, ok... I tried with MTTY first, but i can just code it directly into my program. Its ready for sending and receiving data. Ill try the different setups, though my program instead, and come back when i know some more.
OK just tried a few different scenarios:
1)
rtask a (enter bootloader)
- Doesnt return with "USB>"
rtask 7
- returns "Invalid cmd..!"
AT+CGSN
- Returns "0" and a linefeed.
2)
This time without the rtask a
rtask 7
- returns "rtask 7USB>" and 0x13
AT+CGSN
- Returns "AT+CGSN Command Error !!USB>"
So... Still can't.
You should see something like 'AT-Command Interpreter ready', which bootloader version are you using?
Try issuing "[email protected]_USB" before "AT+CGSN" and see what happens...
pof said:
You should see something like 'AT-Command Interpreter ready', which bootloader version are you using?
Try issuing "[email protected]_USB" before "AT+CGSN" and see what happens...
Click to expand...
Click to collapse
I know, that was the message i got with all the previous phones. I'll try that command...
EDIT: Ok, when passing the command "[email protected]_USB" i get the message "Command Error !!". I passed it in between rtask 7 and AT+CGSN. But without the rtask a command.
Ok, just bumping this one last time. I hoped someone here could give me an option.
I'm curious too... if no one answers and you find it yourself please post it here, i'm suscribed to the thread.
YES... I got it.
After doing some testing and probing, i started throwing some random "rtask" commands to the phone... Well, turns out that "rtask b" is the old "rtask 7", which is the AT Command debugger.
So if anyone would be so kind to notify the dude whos doing this document
http://wiki.xda-developers.com/index.php?pagename=Hermes_BootLoader
So he can keep it up to date?
And if you want to exit the AT Command Interpreter, you have to write "retuoR"
rtask a still works like before.
Thanks for your info, this is a great finding
Wiki bootloader page updated...
Related
Dears,
wdata command can write data to P3300. It is possible to use this command to upgrade ROM and get around the CID lock?
If so we can make a RUU program to flash anything into ROM.
Is this pssible?
ylatsj said:
Dears,
wdata command can write data to P3300. It is possible to use this command to upgrade ROM and get around the CID lock?
If so we can make a RUU program to flash anything into ROM.
Is this pssible?
Click to expand...
Click to collapse
Of course its a good idea but I think the process is much more complicated. The update proccess depends not only on ROMUpdateUtility but also depends on the Bootloaders security. If the bootloader does not open the port for entering data, no data can be entered so no ROM update can be done. Bootloader opens the port only when the CID in the ROM file maches with the device's CID and the Signature is intact. Thats why we need USPL that does not check CID and Signature.
Tamagochi said:
Of course its a good idea but I think the process is much more complicated. The update proccess depends not only on ROMUpdateUtility but also depends on the Bootloaders security. If the bootloader does not open the port for entering data, no data can be entered so no ROM update can be done. Bootloader opens the port only when the CID in the ROM file maches with the device's CID and the Signature is intact. Thats why we need USPL that does not check CID and Signature.
Click to expand...
Click to collapse
I thought IPL won't check CID lock for wdata command. So I guess we can use wdata to flush anything into ROM (a clean,pure WM without any headers)
And we don't use ROMUpdateUtility but write an application to directly deal with the USB port on bootloder.
The purpose is to save hundreds of bricked phones. The current SuperCID program doesn't work with bootloader mode!!!
Anyone can tell me what address the Artemis OS begins with so that I can make the USB applicaiton to try to flush OS to the ROM address?
great!!
I think POF can help you
He is active in Hermes treads
ylatsj said:
I thought IPL won't check CID lock for wdata command. So I guess we can use wdata to flush anything into ROM (a clean,pure WM without any headers)
And we don't use ROMUpdateUtility but write an application to directly deal with the USB port on bootloder.
The purpose is to save hundreds of bricked phones. The current SuperCID program doesn't work with bootloader mode!!!
Anyone can tell me what address the Artemis OS begins with so that I can make the USB applicaiton to try to flush OS to the ROM address?
Click to expand...
Click to collapse
I dont think so, the SPL is like a bodyguard. To be able to write to the flashROM, some ports should be opened (enable write mode). Only the SPL can enable write mode, and it is very stubborn. Every time an application tries to write to the DOC, it asks for the CID and Signature. If these info do not match with the ones inside the DOC, it will refuse to enable write mode. You can fool it with CID but you cannot fool it with Signature unless you can imitate the signature and use it to sign the ROM file.
So the problem is how to imitate the signature or to extract it from a signed one.
Tamagochi said:
I dont think so, the SPL is like a bodyguard. To be able to write to the flashROM, some ports should be opened (enable write mode). Only the SPL can enable write mode, and it is very stubborn. Every time an application tries to write to the DOC, it asks for the CID and Signature. If these info do not match with the ones inside the DOC, it will refuse to enable write mode. You can fool it with CID but you cannot fool it with Signature unless you can imitate the signature and use it to sign the ROM file.
So the problem is how to imitate the signature or to extract it from a signed one.
Click to expand...
Click to collapse
First, sorry for q on first post and no introduction.
Basically, im male, so didn't rtfm until I got stuck...CID Locked device...botched WM6 upgrade...blah blah...bootscreen...blah...you know the score.
This thread has piqued my interest though. I am a programmer with quite a bit of experience of embedded devices. I figured that there is some way to do something like this...but not really sure how as documentation is a bit thin on the ground!
What does the wdata command actually do? My understanding is that it copies arbitary data into the devices address space...but where from? We have a dst and len, but what is the src?
wdata [Len [StartAddr]]
I assume that the flash-rom is simply mapped into linear address space.
gamefreaks said:
First, sorry for q on first post and no introduction.
Basically, im male, so didn't rtfm until I got stuck...CID Locked device...botched WM6 upgrade...blah blah...bootscreen...blah...you know the score.
This thread has piqued my interest though. I am a programmer with quite a bit of experience of embedded devices. I figured that there is some way to do something like this...but not really sure how as documentation is a bit thin on the ground!
What does the wdata command actually do? My understanding is that it copies arbitary data into the devices address space...but where from? We have a dst and len, but what is the src?
wdata [Len [StartAddr]]
I assume that the flash-rom is simply mapped into linear address space.
Click to expand...
Click to collapse
This is what I thought as well that the flash-rom is simply mapped into linear address space. But I don't know where it sits and which segment is for IPL,SPL,OS,EXTROM. etc...
And I am not sure if the IPL will secure the ROM write when it execute the "WDATA" command.
Here is the introduction for WDATA command
wdata [StartAddr Len]
Write data to memory(if write to ROM, need erase first).
StartAddr : Start address of memory.
Len : How many bytes will be written.
Length must not more than 0x10000 bytes(buffer limitation).
Write to RAM: 4 bytes(CRC checksum limitation).
1 byte(in user mode).
Write to ROM: 4 bytes(CRC checksum limitation).
2(16-bit)/4(32-bit) bytes(in user mode).
Write to ROM(16-bit data bus): 32 bytes(writebuffer mode).
Write to ROM(32-bit data bus): 64 bytes(writebuffer mode).
Length must be 4 bytes boundary(CRC checksum) if not in user mode.
After command execute, then send out the data to terminal.
Data format: HTCS(4 bytes)+DATA+checksum(4 bytes, if not in user mode)+HTCE(4 bytes).
Also please check this URL
http://forum.xda-developers.com/archive/index.php/t-285112.html
Pay atttention on this
Write data to memory(if write to ROM, need erase first).
"If write to ROM" This means the ROM is for sure being mapped into the memory space. And what important is that WDATA doesn't talk to the IPL on any CID information. This possibly means that IPL won't stop a write to ROM.
So it is worth to give a try here. The information we need before make the USB application is:
1) Where does the ROM start inside the memory address space
2) Where does the OS start and end
3) How to erase the ROM before WDATA (Another USB command but what is it)
Actually, if we know where the IPL starts we could even directly flush the IPL to Pof's superCID. But this is a little dangerous becasue it is possible to crash the IPL ROM so that the Artemis even can't start bootloader. So better not do it but to flush the OS only and make the birck start first. Then use Pof's baby to flush the SuperCID.
OK, long post. Hope we can have more experts in this thread. Thank you folks for your attention on my topic.
Sorry if this is fool question. Does anyone know how to reset phone lifetime to zero. I am using Dopod 838pro. Thank you
hardreset ought to do the job
It depends what you mean. If it's the overall incoming / outgoing call timers (not just ones you can reset after individual calls) then a hard reset will not reset them. Nor will flashing new ROMs Radio or otherwise.
Now of course, I cannot think of a legitimate reason for doing this other than to fool a prospective purchaser of the phone, except perhaps if you have just bought the phone and want just your own totals. Still, this is not a legit activity.
Theoretically speaking only, it would be possible:
Method 1
Code:
1) put device in bootloader mode
2) disable activesync usb connections
3) connect to bootloader using mtty.exe
4) when you see "USB>" prompt type this (DO NOT COPY-PASTE):
USB> rtask b
0 <--- wait until you see a "0" here
ate1 <--- enable local echo
atv1 <--- verbose output for return values
[email protected]?1 <--- get outgoing call time
[email protected]?0 <--- get incoming call time
[email protected]=<value1>,<value2> <--- set incoming and outgoing call
OR
Method 2
http://forum.xda-developers.com/showpost.php?p=743016&postcount=4
http://forum.xda-developers.com/showpost.php?p=1320316&postcount=5
Mike
I have successfully reseted call timers. Cheers Mikes
I tried but i was not able to did it, maybe because my pc running Microsoft Windows Vista ???
mikechannon said:
[email protected]=<value1>,<value2> <--- set incoming and outgoing call
Click to expand...
Click to collapse
not true... it won't accept any value, the specific purpose of this is solely to reset the timers
casperkid said:
I have successfully reseted call timers. Cheers Mikes
Click to expand...
Click to collapse
Which way ???
I'll try 3 methods and fail. Tell me bro ...
I tried Method 1. But when connect to bootloader using mtty.exe
I do not see a "USB>" prompt I see a "Cmd>" prompt.
What is wrong?
Hrrrm.. I thought I'd try this too as I've always been curious about this...
It seems I get the Cmd> prompt too - is this as I'm accessing the 2.10.Olipro bootloader? Is there a different command set to this?
Hrrrmmm - Replying to myself...
It looks like you need to have to have HardSPL-1.10 installed - as looking at the changelogs for Olipro's HardSPL:
Code:
Hard-SPL-1.11
- Flashing Radio BL 0108 now supported
- Downgrading SPL no longer allowed.
- rtask command removed.
- new RUU interface required to flash ROM files.
Hard-SPL-1.10
-Initial release; SuperCID and no signing required
-Compatible only with Radio BL 0107
-has rtask commands for accessing radio facilities.
This means you'd have to downgrade to SPL v1.10 to get into the rtask b command set. Then upgrade to v2.10 later on...
That being said, when I try [email protected]=270F,270F I just get back "ERROR". It seems to do this on all values except 0000,0000 - however this doesn't seem to modify the call timers returned by talk?0 and talk?1...
Phone is currently IPL-1.04, SPL-1.10.Oli - which I understand should work, however I get the following:
Code:
USB> info 2
HTCSUSB> task 32
Level = 0
USB> rtask b
Enter Radio Image
AT-Command Interpreter ready
atv1
OK
ate1
OK
[email protected]=2710,2710
ERROR
[email protected]?0
@TALK: 00023C7D
OK
[email protected]=ffff,ffff
ERROR
Flashed back to SPL-1.01.Oli and the same problems... [email protected]=xxxx,xxxx will error on any value that isn't 0000 - which obviously doesn't reset the timers.
eightball said:
I tried Method 1. But when connect to bootloader using mtty.exe
I do not see a "USB>" prompt I see a "Cmd>" prompt.
What is wrong?
Click to expand...
Click to collapse
I have the same before, but after I flash my ROM with Hard-SPL-V7, and I see right away the USB> under mitty.exe. Search the forum for Hard-SPL-V7 if you want. After resetting the timer, you may want to flash back the Hard-SPL-V7 to another version. Good Luck!
Reason for resetting the timer: I bought my ATT 8525 in eBay, and I hate to see my phone showing hundreds minutes of incoming and out-going calls. Secondly, it is a chanllenge to myself if I can do it. Yes, I did it. It is part of the reason I bought ATT 8525/Hermes, it is FUN to do modifications!
Huh? Hard-SPL v7 doesn't have the rtask commands required to do this! Do you mean that you downgraded to 1.10, then reset usage, then upgraded to v7 afterwards?
Thanks to Pof, my phone was SIM Unlocked & SuperCID before hand. I tried to get USB> under mitty.exe with no luck. Eventually, I tried to change my HardSPL version, thanks to Olipro, I download the HardSPL-V7 from this thread http://forum.xda-developers.com/showthread.php?t=296722
As I said, after I flashed my ROM with this HardSPL-V7, I can get USB> under mitty.exe. Yes, after resetting the timer, I switched back to the original HardSPL by running Pof's Sim & SuperCID program again.
aaronwms said:
Thanks to Pof, my phone was SIM Unlocked & SuperCID before hand. I tried to get USB> under mitty.exe with no luck. Eventually, I tried to change my HardSPL version, thanks to Olipro, I download the HardSPL-V7 from this thread http://forum.xda-developers.com/showthread.php?t=296722
As I said, after I flashed my ROM with this HardSPL-V7, I can get USB> under mitty.exe. Yes, after resetting the timer, I switched back to the original HardSPL by running Pof's Sim & SuperCID program again.
Click to expand...
Click to collapse
I don`t understand how did you reset the timers in Hard-SPL-V7 when rtask command is disabled???
That's what I was wondering... I still haven't managed to figure this out - see my earlier posts for details...
CRCinAU said:
That's what I was wondering... I still haven't managed to figure this out - see my earlier posts for details...
Click to expand...
Click to collapse
I will try today with Hard-SPL 1.10 and SPL 1.04. I will report what happend!
I did a downgrade from HardSPL V7 (2.10 Olipro) to HardSPL 1.10 and done the folowing commands:
USB> rtask b
Enter Radio Image
AT-Command Interpreter ready
There was no "0" so I typed ate1 an got "0". Then continued:
atv1
OK
[email protected]=270F,270F
OK
Success. Timers are 00:00:00. The important thing is to have SuperCID on "info 2".
Hrrrm - I just did exactly what you did again, and it still errors... The difference is that I'm running radio version 1.50.30.10. I'm in the middle of flashing it back to 1.48.00.10 to try...
Nope... Still errors...
Code:
USB> rtask b
Enter Radio Image
AT-Command Interpreter ready
(type in atv1e1)
OK
[email protected]?0
@TALK: 00026755
OK
[email protected]=270F,270F,
ERROR
This is using SPL-1.10.Oli, radio version 1.48.00.10.
From what I understand, my device is SuperCID...
Code:
USB> info 2
HTCSUSB> task 32
Level = 0
USB>
What am I missing here? lol
IPL-1.04
SPL-1.10.Oli
Radio: 1.48.00.10
New Generic RTL Xperia ROM images are officially released;
Code:
[I]ROM images[/I]
[B]Customized DE[/B]
http://rapidshare.com/files/155680913/APP_SW_X1i_GENERIC_DE_1213-6439_CDF1215-3303_KOV_R1AA017.image.html
[B]Generic FR[/B]
http://rapidshare.com/files/155700645/APP_SW_X1i_GENERIC_FR_1213-6441_CDF1215-3307_KOV_R1AA017.image.html
[B]Generic IT[/B]
http://rapidshare.com/files/155252393/APP_SW_X1i_GENERIC_IT_1213-6444_CDF1215-3309_KOV_R1AA017.zip.html
[B]Generic SE[/B]
http://rapidshare.com/files/155685806/APP_SW_X1i_GENERIC_SE_1213-2274_CDF1215-3315_KOV_R1AA017.image.html
[B]Customized UK[/B]
http://rapidshare.com/files/154889093/APP_SW_X1i_GENERIC_UK_1213-6450_CDF1215-1832_KOV_R1AA017.zip.html
[B]Customized T-Mobile NL[/B]
http://rapidshare.com/files/155690891/APP_SW_X1i_TMO_NL_1213-2293_CDF1216-0475_KOV_R1AA020.image.html
[B]O2 DE[/B]
http://rapidshare.com/files/155769609/APP_SW_X1i_O2_DE_1213-2272_CDF1215-1634_KOV_R1AA017.image.html
[I]Instructions / Movie / Trouble Shooting[/I]
[B]Working Instructions Guide (Mechanical level) for X1i/X1a[/B]
http://rapidshare.com/files/155696508/Guide_Working_Instructions_Mechanical_X1i.pdf.html
[B]Working Instructions Guide (Mechanical level) for X1i/X1a[/B]
http://rapidshare.com/files/155696939/Guide_Repair_Movies_Mechanical_X1i.pdf.html
[B]Trouble Shooting Guide (Mechanical level) for X1i/X1a[/B]
http://rapidshare.com/files/155697184/Guide_Trouble_Shooting_Mechanical_X1i.zip.html
Code:
[B]How to enter bootloader mode on your Xperia:[/B]
0. Make sure your phone battery is fully charged.
1. Turn off your phone.
2. Remove and reinsert the phone battery.
3. Press and hold first the volume down button on the phone and then the phone power button.
4. Continue holding the two buttons (volume down + power button) down until the phone display turns on and displays colored stripes.
5. Release the buttons.
6. Attach the USB-mini cable to the phone and the PC.
7. Take a cold beer :).
[I]Delay a few minutes, or alternativity take a short nap[/I]
8. Follow included instructions.
9. Read again.
...
10. Start playing with your device
I have also attached some technical guides together with mechanical/electrical repair manuals which includes assembly and disassembly hints, I really do hope the community finds them useful. If you are missing something, don't hesitate to PM me or you can mention in this thread what you really are looking for.
It is required that you've got a security unlocked phone (SuperCID with HardSPL) for being able to use the ROM images linked above!
Regards
thanks a lot
arash_ ! Thanx
awesome, thx for sharing with us
I tried UK IT SE versions, they all stoped at either 10% or 11%.
Now I cant use my phone anymore, it shows a four color screen(red green blue and white),
and says that
KOVS110
SPL-0.72.0000
MicroP1-787
MicroP2-707
Upgrade ROM code error
Please try again
Serial
--
I tried to use RUU to recover the process, but it didn't work, always stops at 10%
I am not an engineer, don't know much about it, could anymore one just tell me how to make my phone work again, I just want the SE system back, I am done with flashing the ROM. thanks
ffffdddd said:
I tried UK IT SE versions, they all stoped at either 10% or 11%.
Now I cant use my phone anymore, it shows a four color screen(red green blue and white),
and says that
KOVS110
SPL-0.72.0000
MicroP1-787
MicroP2-707
Upgrade ROM code error
Please try again
Serial
--
I tried to use RUU to recover the process, but it didn't work, always stops at 10%
I am not an engineer, don't know much about it, could anymore one just tell me how to make my phone work again, I just want the SE system back, I am done with flashing the ROM. thanks
Click to expand...
Click to collapse
the same problem here
any ideas how to unlock that cid?
Its a happy day again !!! Yipiii
1. Download mtty.exe
2. Disable activesync (connection settings -> uncheck "allow usb connections")
3. Connect your x1 to PC using USB cable.
4. Open mtty, select USB port and click OK.
5. Hit ENTER twice, you should see the "Cmd>" prompt.
6. Type the command "boot"
and its alive again but after restart need mtty to boot again.
so realy need to unlock cid to be god flashed
Very usefull thread. For CID unlocking need's HardSPL. arnisv, does this repair dead phones eg. stuck at tricolour (bootloader) screen ?
borce_razor said:
Very usefull thread. For CID unlocking need's HardSPL. arnisv, does this repair dead phones eg. stuck at tricolour (bootloader) screen ?
Click to expand...
Click to collapse
No, it doesn't work on my phone
ffffdddd said:
No, it doesn't work on my phone
Click to expand...
Click to collapse
Try this
Code:
MTTY (How to fix a bad ROM flash!) Hi,
I didn't see any post about using MTTY on Kaiser.
If I did a bad ROM flash with my previous device (HTC Universal), I could always fix this by clearing the FAT table with MTTY.
Believe me... if you flash and it stops ad 85% you will be very happy if you can use this tool!
Reason I started this thread is to help out people who are having such a problem with there Kaiser!
This is the correct procedure to get you out of trouble
1. Stop ActiveSync, by Task Manager (press Ctrl + Alt + Delete)
kill two processes rapimgr.exe and wcescomm.exe
2. put your device into the cradle
3. Run mtty and Choose WCEUSBSH001 in 'PORT' (if it doesn't show then you didn't stop all active sync processes above!)
4. type "set 16 0" without the quotes to tell bootloader to boot the OS after reset. (for some devices it can also be "set 14 0")
5. type "task 8" to get your device formatted
6. type "task 0" to ask your device reboot
7. take the device out of the cradle, and manually reset it if it does not do that already.
Incase of an emergency it could be very helpfull I think!
Thank you all for providing the input in this thread so I could make this small user manual!
Happy flashing!
Search for MTTY ver 1[1].42 or other, this is from our forum. It work's on Kaiser, maybe will work on xperia. And I'M NOT RESPONSIBLE FOR ANY DAMAGE DONE WITH THIS
Xperia HardSPL thread created
What rom is the swedish one? Newer or the same as it was delivered with?
Edit: Im new to windows mobile. What should i look for to check what version i have?
[email protected] said:
What build is the swedish on? Newer or the same as it was delivered with?
Click to expand...
Click to collapse
As i see it, it's the same as we allready have
borce_razor said:
Very usefull thread. For CID unlocking need's HardSPL. arnisv, does this repair dead phones eg. stuck at tricolour (bootloader) screen ?
Click to expand...
Click to collapse
no it just boots the phone in wm and all works exept can not restart the phone without myyt
If you turn off the phone it can't be booted again without mtty ?
borce_razor said:
If you turn off the phone it can't be booted again without mtty ?
Click to expand...
Click to collapse
yes need help of mtty
How its possible know which version have CID? All swedish version have CID but its able to unlock and after that u can flash to English OS?
ok after
Cmd>set 16 0
Cmd>task 14 0
now phone boots without mtty
borce_razor said:
Try this
Code:
MTTY (How to fix a bad ROM flash!) Hi,
I didn't see any post about using MTTY on Kaiser.
If I did a bad ROM flash with my previous device (HTC Universal), I could always fix this by clearing the FAT table with MTTY.
Believe me... if you flash and it stops ad 85% you will be very happy if you can use this tool!
Reason I started this thread is to help out people who are having such a problem with there Kaiser!
This is the correct procedure to get you out of trouble
1. Stop ActiveSync, by Task Manager (press Ctrl + Alt + Delete)
kill two processes rapimgr.exe and wcescomm.exe
2. put your device into the cradle
3. Run mtty and Choose WCEUSBSH001 in 'PORT' (if it doesn't show then you didn't stop all active sync processes above!)
4. type "set 16 0" without the quotes to tell bootloader to boot the OS after reset. (for some devices it can also be "set 14 0")
5. type "task 8" to get your device formatted
6. type "task 0" to ask your device reboot
7. take the device out of the cradle, and manually reset it if it does not do that already.
Incase of an emergency it could be very helpfull I think!
Thank you all for providing the input in this thread so I could make this small user manual!
Happy flashing!
Search for MTTY ver 1[1].42 or other, this is from our forum. It work's on Kaiser, maybe will work on xperia. And I'M NOT RESPONSIBLE FOR ANY DAMAGE DONE WITH THIS
Click to expand...
Click to collapse
Thanks a lot, my phone is working again, although its still in Swedish.
How to see which CID verrsion is my BlackStone ?
same questions here lol
Start your HD in bootloader mode (tri-color), connect with mtty and issue getdevinfo command to check the CID.
Thanks mate
Could you elaborate a bit more? I cant seem to get the phone to connect properly to mtty. I don't get a prompt but a "notepad like" editor that cant execute anything, you just type in it.
Thanks.
There's no dedicated wiki article for mtty. Check out:
http://wiki.xda-developers.com/index.php?pagename=Hermes_BootLoader
Just don't use Hermes commands
Ok..so first of all thanks for clicking on my thread.I hope somebody can help me flash a rom.I can't post the link because I'm new....I added a text file with the link(yes, it's on xda)
Post #9 describes a process of flashing this rom.
My device: HW6915 vG.39 G4(flash chip)
I am having trouble with this step pdocwrite spl -n0 -b 0x20000 0 0x80000.
Yes I know what the bootloader is and I know how to get into it.So after I connect the device via usb(while in BL mode) i run the command mentioned above.The problem is that nothing happens(screenshot included),it just stays at the same command and does not progress at all.CPU usage is little to none.And if I do try to flash the rom anyway the progress bar on sable_RUU gets stuck at 1% and after a few minutes gives an error.I tried this on XP 32 and on 7 64.
Yes, this is my first post, so take it easy.
Thanks for any help.
hello. i have the same problem but my sable ruu progress bar freezes at 51% and then pop up error:201. help?
For you it's stuck at 51% because you also flashed the bootloader(CEBL.nbf).I chose not to as it's optional.Even so I'm still stuck on the original problem.
Anybody know the answer to this?
my problem is identical. i am also having trouble with pdocwrite spl -n0 -b 0x20000 0 0x80000.after i run the command nothing happens,it just stays at the same command and does not progress at all as in your case. then when i run sable_ruu it freezes at 51%
did you try...
did you try opening the command prompt as administrator?
Code:
1. Click on start
2. Type command
3. Then either right click and then pick run as administrator or just CTRL + SHIFT + Click
If that doesn't work you can try disabling UAC by clicking start, typing UAC pick the first option then dragging the slider to the bottom and restart computer
You need to write SPL when phone is on and connected with ActiveSync, not in bootloader.
Spiaatie said:
You need to write SPL when phone is on and connected with ActiveSync, not in bootloader.
Click to expand...
Click to collapse
Ok it works thanks guys for all the help.
Will report back to your thread and tell you about my findings
Thanks,appreciate it
Thanks from me too. On the first look wm 6.1 runs faster than 5.0 and gps does not work (igo 2006 plus-can not find gps com port).
my suspicions on gps is it might be driver related in asset viewer (Settings/System/MyCPL 7) under GPS it used to state whether it was on or off in WM5 but now it says N/A
jambongo said:
my suspicions on gps is it might be driver related in asset viewer (Settings/System/MyCPL 7) under GPS it used to state whether it was on or off in WM5 but now it says N/A
Click to expand...
Click to collapse
Yes the driver is indeed missing as this is ported from a hp without gps(i guess so anyway).First clue is that it doesn't include any base navigational software.
Second igo 8 reports ''gps driver not found''
n can you! help???
you seem to know how to proceed to tryin' roms on you hw6915;
......i don't!
can u help me, i'm really a newbie on this!!!
i wish there was an "upgrade your ipaq verson for dummies" or somthing!!
i got the hp ipaq hw6915, an usb connector, Internet access!! anything else?
oussahoo said:
you seem to know how to proceed to tryin' roms on you hw6915;
......i don't!
can u help me, i'm really a newbie on this!!!
i wish there was an "upgrade your ipaq verson for dummies" or somthing!!
i got the hp ipaq hw6915, an usb connector, Internet access!! anything else?
Click to expand...
Click to collapse
Beware dude this is higly experimental.There is no GPS for example.The rom is wm6.1.This is just for people who want to test and no it obviously not official.All files can be found at the link in the TEXT file I attached to my first post.
1.Connect your device to activesync(suggest a hard reset first,however it's optional)
2.Extract SPL vG.39.7z anywhere you want.
3.Run ''Command prompt'' (if using vista/7 RUN AS ADMINISTRATOR)
4.Enter this command pdocwrite spl -n0 -b 0x20000 0 0x80000 (WAIT UNTIL IT FINISHES).This command replaces a file in the ROM which allows you to flash ''non-original roms'' basically software CID unlocking which allows flashing of ''cooked roms''
5.You will get warnings on your hp regarding a dll file(itsutils.dll) PRESS YES
6.Put your device in bootloader mode.[hold the two buttons next to the joystick(the round thingy) and shortly tap the reset button with your stylus
7.Open activesync,go to connections and untick allow USB connections
8.Extract 6915_ENG.7z and run Sable_RUU
9.Press on the big ''Upgrade button''
10.There will be a progress bar, when it's done it should say something like '' Update finished !!''
11.Go back to activesync and re-tick allow USB connections
I wrote this for everybody who's got trouble flashing roms on their hw69xx.Yep I had this problem too.
This detailed enough?
jambongo said:
did you try opening the command prompt as administrator?
Code:
1. Click on start
2. Type command
3. Then either right click and then pick run as administrator or just CTRL + SHIFT + Click
If that doesn't work you can try disabling UAC by clicking start, typing UAC pick the first option then dragging the slider to the bottom and restart computer
Click to expand...
Click to collapse
A question ....
but it happens to me the same error in XP and not out of the 1% resulting in the error 201
Can you help me!
hi
I have the hw6915
to me the procedure doesn't go
he/she writes me "client_initialize Fail Error 601"
a question: what I write on the Command Pront
thanks
for further information
the cell doesn't connect him to activesync
it is jammed on screens her/it USB - LOGO HP INVENT and in low vG.39
THANKS
@spiaatie
mine is in bootloader
however it doesn't connect him with Activesync
what do I have to do?
which procedure do I have to do?
thanks
can't program ipaq 6945
When ever I push upgrade button, it just hangs and afer a while I get the message:
client_getosver Fail !! Error :501
I'm using it on windows XP,
could someone help me!!!
Thanks!
rra_pn said:
client_getosver Fail !! Error :501
Click to expand...
Click to collapse
Did you install SPL?
Yes, I did de pdcowrite on command prompt, then it gave me the warning on my ipaq and then it finished.
After that I unticked the allow usb connections on active sync
then I press the two buttons next to the joystick and press the reset
I run sable
and then it does what i Posted
Thanks!