Related
I have an XDA IIs from O2 and a Qtek 9090 from Vodafone (fairly litlle tinkering from Vodafone).
I want to unlock the XDA IIs (as does everybody else) but isn't the SimLock part of the Radio Rom, in which case cant I jusr replace this with the Voidafone Rom and hey presto!!
I am sure that this is not as simple as I have suggested, or everybody wouyld be doing it, but can someone explain to me where the SimLock subsystem is and therefore where I should start to poke, to unlock it.
I quite liked the idea of sending millions of AT commands to the wireless modem, but that sounded too easy as well.
I know what the Extended Rom does, and the Rom Rom (presumably OS), and in general I know what the radio Rom does, but if this is all there is then I cant see where the SimLock stuff would be held???
If you could reply I'd be grateful, and if anybody reads this and cracks an unlock, drop me a line as well.
Thanks in advance
During a lot of months I have been wondering this. In my opinion, I think that simlock is in the extended rom because it contains special programs from your provider, but I am not sure. The definite clue would be to change all the operating system (radio rom, OS rom, and extended rom) for other (for example, qtek 9090). If somebody knows how to do this and he tries it, please let us know. Thanks.
The code in the CE ROM (Or possibly the radio rom?) reads information from the phone hardware to detect if it is locked or unlocked and merely displays a message to the user indicating its current status when you try to use an alt network sim. The lock status, network locked to and unlock code is stored in a separate flash area of the phone hardware within the XDA IIs - not in one of the standard 3 roms.
This means that no matter what "standard" rom you put on the XDA it will not suddenly become "unlocked" (As I have had numerous different roms on mine since I purchased it - radio, ce and extended rom).
Unfortunately the area of the phone containing this information cannot easily be accessed and requres a code based on the IMEI number of the phone to access. Without the algorithm used to calc this code (Different for each phone type ie alg. for XDA II is different to one for XDA IIs) we cannot unlock the phone!
That said, I believe that the phone itself may not actually prevent the calls merely the firmware in the radio rom after detecting that the phone is "locked". Therefore, I believe it MAY be possible to hack the rom to allow it to be used on any network. PLEASE NOTE THAT I DO NOT KNOW THIS LAST BIT OF INFO FOR SURE, IT IS SPECULATION ONLY AS A POSSIBLE WAY AROUND THE SIM LOCK....... NOW WHERE IS MY HEX EDITOR!
A summary so far
Ok,
So the simlock code is contained in a fourth ROM somewhere in teh device that we dont know how to get to. The radio ROM then somehow reads to see if it is locked, and if it is prompts for the unlock, and if not then allows you to make a call etc.
This fourth ROM is likely to be pretty fixed, like the deviceID and is presumably unaccessable to anything without opening the device up, removing the chip and hitting it with a lightning bolt.
So where does that leave us. The screen that comes up about SIMlock, enter the number, which interestingly enough says that I have tried a large negative integer times, and then locks up permanently (or so it seams). This bit must be in one of the accessible ROMS, as it is too Windowsy for anything hardware wise.
This screen must call some other function that tries the unlock code into the unaccessable chip. It would probably be easier to attempt to remove the retry timeout and then retry millions of times, either with a simple sendkeys type function or with something cleverer. Or alternatively find the function that SIMLock calls to the hardware.
I am being creative here, hoping that someone can step in and be a little more factual. Anyone....
On the XDA II, if you unlock it, can you lock it again?
Think of this fourth "rom" more as as a type of BIOS with basic hardware call functionality with windows and radio rom sitting on top providing code to access the "BIOS" for radio functions (Bluetooth, GPRS, WiFi, GSM etc) and hardware functionality (LED's, buttons etc). It has a form of NVRAM with IMEI number stored as well as SIM locks etc....
I've recently purchased an XDA IIs (unlocked and used on Vodaphone). Overall very impressed but I am having some annoying problems that I'm hoping for advice on (my collegue has also purchased one and is having similar problems, so I don't think it a hardware problem)
The XDA has just the standard O2 software apps installed and I have upgraded to ROM 1.31.00 WWE (from my-xda.com a few days ago), its say radio version is 1.06.00
Problems:
1) Very unreliable software, I quite frequently (several times a day) have to press the reset button. I seem to have the most recent version from O2. I see some comments on the forum about disabling O2 Active software?
2) I'm using a Bluetooth headset (Jabra BT250), this worked well with my previous phone a Nokia 6310i. Specifically:
- When I receive an incoming call it rings on the headset, if I answer by pressing the button on the headset in generally (but not always) answers with the headset connected as I need. But if I answer by pressing the answer button on the phone (hard button or pop-up menu button) the headset isn't connected and its a struggle to get it to connect mid call. However if I make outgoing calls in nearly always uses the headset correctly. Very annoying an inconsistent behaviour. I'd rather not use a different headset as I like the Jabra and the problems seem to be due to the XDA as it worked fine on the 6310i
- The range is hopeless, people say its very hard to hear me if the XDA is more than a couple of feet away, even turning my head so the Jabra and XDA are on opposite sides degrades the quality badly, I didn't think my head was that thick! With the 6310i I could be at least 10 feet away
- The volume, even at maximum, is too low, especially in a noisy environement like a car. It's much less than with the 6310i on exactly the same BT 250
I hope there are some fixes for this. I think the XDA is a great, really useful all in one device, but the poor relaibility and terrible bluetooth headset support are really spoiling it for me
Regards
Mike
Hi...
I just ordered my XDA IIs..hehe..selling my PDA2k now..love the black color..
Hehe..anyway, my PDA2k was using the BT 3500 drivers and i have the same problem as yours occasionally.
Most of the time, when i answer from the unit (not the BT headset's button), the caller can barely hear my voice.
However if i use the BT headest's button, it was fine...
I was using the Jabra BT250 also..but sold it to get the Motorola HS850..
Both are giving me the same problems...
I've read on several threads where poeple are successful in using the BT 3900 patch (sorry of i'm wrong)..but my PDA2k does not work with the patch..the screen turns garbage n messed up..had to hard reset it
I love this unit..canlive around with its current problems..hehe..hopefully it gets fixed.
Cheers!
The BT problems described above appear fairly common amoung xdaIIs users. Based on my research on this, there are a few things listed below that can help. Listed in order of ease to do. Start with 1 and progress to 5 if you are feeling brave :? or wait for 6!
1. (EASY) Keep your add on "Today Plugins" to an absolute minimum: I have found that SBP Pocket Plus to be particularly troubelsome and had to uninstall it.
2. (NOT TOO DIFICULT) Disable O2 Active: O2 advised me that the xda2s is more stable in "corporate mode" with O2 Active disabled. To do this you will need to back up your device data to your PC and then do a hard reset. As the device boots up and starts to go through the configuration process, you will be prompted to choose "corporate mode". You only have about 5 seconds to say "yes" before the configuration continues and installs personal mode. Select 'yes' and you will be prompted for a code. Enter 0506 (that's zero five zero
six) and tap Finish. You will see the message "Welcome corporate user, O2 Active won't be installed". Your device is now ready and you will have everything except the Active User Interface.
3. (MORE DIFFICULT) Upgrade your BT Stack from BT Build 3500 to BT 3900. Details on how to do this are provide in the companion wiki-developers forum
4. (A LITTLE SCARY) Upgrade your Radio Stack to 1.10 and your BT Stack to Build 3900. If you want to upgrade the radio stack at all, WIKI folks recommend upgrading the radio stack first and then the BT Stack.
5. (MORE SCARY!) Upgrade your BT and Radio Stack AND your ROM. WIKI have posted 1.40, which it seems can be used in conjunction with the existing extended ROM on the O2 XDA 2s. Not for the feint hearted, although the instruction they post for this are pretty comprehensive I must say.
I "talked" to one xda2s user who had gone through to step 5 and most of his issues had been resolved. I am at number 2 right now... Thinking of going to 3,4,and 5, but probably waiting for 6.........
6...?......ah yes...., wait for O2 to post the next full ROM update... :wink:
Hope that helps
Regards
Chris
The BT problems described above appear fairly common amoung xdaIIs users. Based on my research on this, there are a few things listed below that can help. Listed in order of ease to do. Start with 1 and progress to 5 if you are feeling brave :? or wait for 6!
1. (EASY) Keep your add on "Today Plugins" to an absolute minimum: I have found that SBP Pocket Plus to be particularly troubelsome and had to uninstall it.
2. (NOT TOO DIFICULT) Disable O2 Active: O2 advised me that the xda2s is more stable in "corporate mode" with O2 Active disabled. To do this you will need to back up your device data to your PC and then do a hard reset. As the device boots up and starts to go through the configuration process, you will be prompted to choose "corporate mode". You only have about 5 seconds to say "yes" before the configuration continues and installs personal mode. Select 'yes' and you will be prompted for a code. Enter 0506 (that's zero five zero
six) and tap Finish. You will see the message "Welcome corporate user, O2 Active won't be installed". Your device is now ready and you will have everything except the Active User Interface.
3. (MORE DIFFICULT) Upgrade your BT Stack from BT Build 3500 to BT 3900. Details on how to do this are provide in the companion wiki-developers forum
4. (A LITTLE SCARY) Upgrade your Radio Stack to 1.10 and your BT Stack to Build 3900. If you want to upgrade the radio stack at all, WIKI folks recommend upgrading the radio stack first and then the BT Stack.
5. (MORE SCARY!) Upgrade your BT and Radio Stack AND your ROM. WIKI have posted 1.40, which it seems can be used in conjunction with the existing extended ROM on the O2 XDA 2s. Not for the feint hearted, although the instruction they post for this are pretty comprehensive I must say.
I "talked" to one xda2s user who had gone through to step 5 and most of his issues had been resolved. I am at number 2 right now... Thinking of going to 3,4,and 5, but probably waiting for 6.........
6...?......ah yes...., wait for O2 to post the next full ROM update... :wink:
Hope that helps
Regards
Chris
Chris
Thanks for this. I changed to Corporate mode 6 days ago and its only had one crash, compared to before 5-6 times PER DAY!
Any idea when O2 are meant to be offering the next ROM update (are we talking weeks or months)?
Regards
Mike
I can't not see the 5 seconds page for selecting "corporate mode" when i do a hard reset.
I do hard reset by press on/off button + press on reset button.
Hi Mike
Well, it is supposed to be the end of April, so my guess is that it will be weeks, rather than months at this point. Also, the 1.40 ROM posted on wiki is a WWE version, so maybe this is a 'bootleg' version of what is to come from O2... only a guess on my part here...not really sure of it's origin...
Regards
Chris
Hi MR2046
What device and what ROM version do you have loaded?
Regards
Chris
Hi cbrow51,
I use O2 XDAIIs
ROM : 1.31.00 WWE
Radio : 1.02.00
Protocal : 1337.32
ExtROM : 1.31.920 WWE
Thanks
2046
Hi MR2046
The option to select corporate mode comes up close to the end of the install after you do the hard reset. You only get about 5 seconds to say 'yes' and then enter the code, before personal mode continues and installs the O2 Active stuff.
I see from your info that you have the older radio ROM (Current 02 version is 1.06) and a different extended ROM (I have 1.31.139WWE)... Not sure if the difference in extended ROM would cause you not to get this option or not...
I would try hardresetting again and see if you get the corp mode option. if you don't, then you might want to download the latest ROM from the O2 web site.
Hope this helps
Chris
Thanks a lot
But the O2 asia website did not update anything. There is only a small patch for BT upgrade.
BTW, which O2 website you meant?
BT sync and internet access
Hi all,
what about Bt sync/internet access? does anyone manage to do it ? i do not use a headset but i am trying for some weeks to get connected to my desktop via BT - with no results... i upgraded to 3900 just today but it did not help .
the manual of the device is not helpful for doing so...
which O2 Website
Hi MR2406
ah! that probably explains it. Sounds like you have the O2 Asia ROM then, correct?
I am using the UK ROM from the UK O2 web site. I am not sure if you would be able to download the UK ROM to your device, which I assume is of Asian origin..? O2 UK state that you should only download their ROM if your device meets certain criteria. Take a look on the site and check compatibility before downloading / installing.
From the very rudimentary understanding that I have from looking through the wiki site, its possible that you might get some kind of country and or operator code errors if you install the UK rom on your device. That said, there are detailed instructions on how to correct these errors also.
If I were you, I would look through all the materials on wiki, check the O2 site in UK and then decide on the best approach.
Hope that helps
Regards
Chris
I have an MDAIII Purchased from T-Mobile in Germany.
This software "works" but there are several irritants which I wanted to cure. My overall goal was a device which would do:
-Motorcycle Navigation
-Palm with MS Word, Excel, Powerpoint
-Blackberry (My company requires it)
-Quad band phone (I travel to North America)
-WiFi
My previous device was a Blackberry 7290 and except for not doing everything I needed, it worked very well.
Now, I have to admit, this Blue Angel (I almost said "this Swiss Army Phone" but that would imply a quality many orders of magnitude beyond the HTC device) will do everything listed.
However;
- It won't send BB PIN messages (will receive them)
- I can't use it in English (replys to English mails say "Betr."
- MS Word doesn't support all the functions
- The missed call light only blinks for a fixed amount of time instead of going off when I've looked at the phone.
- The keyboard is the same size as the BB but unusable where the BB keyboard works very well.
- It requires several reboots a day
- The call quality is horrible and varies
- The Wifi range is half of the other devices I have
- PPT presentations say "made for an old unsupported version of PPT"
- Word doesn't support many of the formatting stuff I need
- Excel is also very limited in support
- I can't insert todays date and time in two keystrokes like I could on my first Palm years ago
- There is no standard command to close a program, it just stays in memory when clicking the red X
- The BB software doesn't handle the mails well (store, copy, delete, etc)
In the vain hopes of trying to conquer this thing I attempted to increase the software versions of the various programs.
After spending most of today failing, I am now resinstalling the T-Mobile version.
Here's what I tried:
I started last weekend with an update of the radio in an attempt to make the telephone problems go away.
After much much trial, error and reading (often in that order) I was able to use the trick of the entry in RUU.conf, and then the program MaUpgradeUt_noID.exe to force foriegn upgrades onto the device.
I also learned that a .CAB file will run as an installable executable so I installed the Blackberry cab after updating the roms to 1.4 and the radio to something also very recent.
While what I saw looked good, I didn't play with this configuration very long because I found no matter what I tried (including downgrading the radio version), the Blackberry refused to work.
So now I'm on the way back to 1.22 rom (The current released software which can be downloaded shows dates on the .nbf files of 26 April 05.), and I find that the BB software here is newer (2.0.1.26-26) than the one I downloaded as a cab (2.0.0.25). This also has a few more whistles and bells in it.
I also found that the 1.4 imate roms in the RAR file here are different than the files downloaded from the Imate site. (These here have an O² splash screen)
One more time I have to commend the RIM people. It is evident that the devices were made by people who need to use them.
In the meantime, the reinstall has completed and I'm going to bed.
I think if I had it to do over again, I'd get a device with a built in GPS antenna but no phone, and just keep the BB.
A possible improvement?
After the pains of yesterday I did upload the newest Bluetooth cab I could find and ran it.
After a soft reboot I found the today screen scrambled but was able to fix this by reselecting the a windows theme.
A brief test shows that everything seems to be ok - phone and Blackberry works.
A missed call is indicated in the top line, and when I've looked at the call, the blinking light goes away. Thats an improvement but the incoming mails still make the light blink constant.
My old Bluetooth was 1.0.0.3900 (the newest software currently available fron T-Mobile Germany)
My new BT is 1.6.0 build 0600.
Time will tell if this is better.
There is a recent press release about HTC and RIM working more together so maybe sometime we will be able to send PIN mesages too.
This entire forum is fantastic and it is a shame on HTC that such a complex fourm is necessary to manage the junk they put on the market.
Good work all!
Contacted o2 (UK) requesting a date for an official ROM upgrade to WM2005 and WMP10.. not definitive news, but if you believe their reply then it's on it way:
"A rom upgrade for the XDAIIs is still in test. We are unable to give a
release time or confirm it's contents until it is fully accredited.
As soon as any information is available it will be posted at
www.my-xda.com"
Fingers crossed, I don't fancy trying one of the modded versions just yet - I rely on the phone a bit too much at the mo.
-FM
O2's 2003SE software isnt exactly stable. I did the upgrade yesterday and its fine except the BT keeps turning off
If you want to increase the stabilty of an O2 XDAIIs, I'd do a hard reset. (Hold the power button whilst pressing the reset button). It'll come up saying it's going to install a load of stuff. Thats OK. When it asks if you want an O2 config or a corporate config, select corporate. You will then be prompted for a pin number. The numbre you require is 0506. Enter the numbers. The phone will eventually finish without installing the O2 active stuff. This, in my experience, turned a phone/pda that was always locking up into a very stable thing!
Hard reseting removes everything and returns it to it's out of the box state. You can restore a previously saved backup as this will put O2 active back on! I learnt this the hard way!
mine was still unstable after the corporate reset and removal of the o2 software....
running tomtom5, BT and media player doesnt help though
What are the chances of the NEW UK XDAIIS ROM containing support for i-mode?
I've got a sneaky suspicion it's why they have dragged the release of it out a bit.... It's taken a long time considering Asia has a ROM all done, that needed a few bugs fixed, but surely would not take this long....?
Must be something 'extra' going into it.
O2 i-mode launch is 'imminent'
http://www.theregister.co.uk/2005/09/20/o2_i-mode_autumn/
What is i-mode?
http://www.sourceo2.com/imode.html
from Wikipedia:
"Opposed to the WAP standard which utilizes WML on top of a specific protocol stack for wireless handheld devices, i-mode borrows from fixed Internet protocols such as C-HTML based on HTML, as well as DoCoMo proprietary protocols ALP (HTTP) and TLP (TCP, UDP). "
I may be completely barking up the wrong tree, but it should be manageable through a software update.....
Anyone know if this is a possibility?
I just purchased this phone and after extensive searching was unable to find any information regarding modifying the ROM.
This Quad Band Phone has the following features;
2.8" touchscreen
TI OMAP 1030 (ARM926T)
128 Rom 64 RAM
WM6.0
GPS
WiFi
Bluetooth 2.0
GPRS Edge
2Mp Camera
Microsim slot that supports up to 4GB T flash Card
I was wondering if there were some generic modding tools / instructions to extract and modify the ROM.
I primarily want to do this because the WM6.0 OS does not seem to be complete. e.g. the HKLM/Software/OEM/PhoneSetting key is not there and when added with the key ShowTimeZonePage there is no change. (this was done manually and with the HTC Registry wizard
I would also like to trim down unneeded programs to maximize the storage space and perhaps add the TF2D to the ROM.
TF2D installed perfectly on this device however takes the majority of my RAM limiting what I can install in there.
I read somewhere that this was an HTC Diamond Clone. While I do see the simular design I doubt the hardware is the same. Even still I have to ask. would the HTC software and ROM's work with this Phone?
One last question. Would it be possible to upgrade the OS to WM 6.1 using an existing ROM Image? I doubt it but had to ask. I am sure that I will have to dump the ROM from the phone and use that image to edit.
Please let me know your thoughts. Good or bad.
I hope to be able to modify this phone and if not that is ok because it is still a good phone as is. I was just hoping to get more out of it.
i have the same phone
hey, i have the same phone ... did you found anything about modding it ?
I was able to dump the ROM however since part of it is SRPK encoded I was unable to do anything with it.
I Have a more detailed thread on what I was able to accomplish going here
http://forum.xda-developers.com/showthread.php?t=455233
If you get any farther please share.
I Found the Rom for WM6.1
Hey, i found the rom for WM6.1 its an img file, but, i dont know how to procede, tell me how to send you, to test.
upload the file to this site
http://uploaded.to/
and post the link here
Are you sure this is for the hTY Q5? Where did you find it?
Rom
http://uploaded.to/?id=6u3czv
is from the Development team of the phone, is a "test" rom
matagatoz said:
http://uploaded.to/?id=6u3czv
is from the Development team of the phone, is a "test" rom
Click to expand...
Click to collapse
Hi!
Just reading through the forum here. ggeisler, any luck with that WM6.1 ROM?
HTY/Hantel Q5 - TouchFlo 3d (manilla)
Does anyone know if the new TouchFlo 3D Manilla (as seeon on the HTC Touch Diamond) works on tihs phone? and if so, any particular place I can I can find it to install it on the Hantel Q5 WM6?
Can someone tell me more about this device and it's InfraRed port
I want to know is this the CIR infrared port, so that u can use the device also as a remote controller for your television at about 2 meters distance?
Can someone please try this, I want to know this fact before buying one...
Can you recommend this phone for buying?
Thnx
Jaromirtje said:
Can someone tell me more about this device and it's InfraRed port
I want to know is this the CIR infrared port, so that u can use the device also as a remote controller for your television at about 2 meters distance?
Can someone please try this, I want to know this fact before buying one...
Can you recommend this phone for buying?
Thnx
Click to expand...
Click to collapse
Your best bet is to pose the question to the vendor on this one. Atleast you'll know for sure, otherwise be refunded if any information on the device that is inaccurate after purchase. Hail to eBay and PayPal protection! Seriously though, if the decision to buy this phone is based on a condition of using it for a remote control for your TV, you're best off not buying this device. Anyhow, I`m still waiting for my order of this device to arrive. I`ll test and let you know, but from the specs I read, it didn`t note a CIR infrared port. Anyone?
There is no infrared on this phone that I am aware of. Perhaps other model variants have one.
I have not had a chance to play with the ROM yet but as soon as I have a chance I will try to load it and post back here with the results.
Hantel007 said:
Does anyone know if the new TouchFlo 3D Manilla (as seeon on the HTC Touch Diamond) works on tihs phone? and if so, any particular place I can I can find it to install it on the Hantel Q5 WM6?
Click to expand...
Click to collapse
yes it works but I have only been able to get UPDATE 19 to work and it was verry slow. (ultimately had to remove it) you can install everything into memory fine but you will have very little space left on the device. If you install anything on the SD Card it will be to slow to use.
get it from here
http://forum.xda-developers.com/showthread.php?t=398173
Can someone already confirm if the hty q5 has cir or not....
the respones i got from ebay sellers:
*bestplace4you says it has no infrared at all, de factory is still developing it...
*www.tomtop.com says it is the short range infrared that has to be aimed directly
*light_wholesale says it is with the strong infrared signal (cir)
so still no view on this....
can someone bring the light to this topic...
Jaromirtje said:
Can someone already confirm if the hty q5 has cir or not....
the respones i got from ebay sellers:
*bestplace4you says it has no infrared at all, de factory is still developing it...
*www.tomtop.com says it is the short range infrared that has to be aimed directly
*light_wholesale says it is with the strong infrared signal (cir)
so still no view on this....
can someone bring the light to this topic...
Click to expand...
Click to collapse
NO IR at all
I have the device in my hand, nothing on it looks like it has an ir emitter.
I am sure tomtop is confusing this Q5 with another phone
this one has;
GPS
Bluetooth
Quadband (some models have triband so be careful you may need 850Mhz in some locations)
Edge
2MP Camera
WiFi
WM6 (hopefully upgradable to 6.1 still trying)
TF Card slot capable of up to 4GB (tried 8GB and only read 4)
But still no ir port.
Windows mobile has settings for ir but the hardware just is not there.
so one more time, I can confirm that there is no ir on this phone!
Tha last phone I had with ir sucked using as a remote. I ended up replacing the ir emmiter because the one that was in it was just to weak. the new emmiter worked better however the wavelengths transmitted via ir are not used by all remote controls.
If you want a remote go buy a remote. Using you phone is not the best option.
hey, mine has a 8gb microsd ... and it reads it all
ggeisler said:
yes it works but I have only been able to get UPDATE 19 to work and it was verry slow. (ultimately had to remove it) you can install everything into memory fine but you will have very little space left on the device. If you install anything on the SD Card it will be to slow to use.
get it from here
http://forum.xda-developers.com/showthread.php?t=398173
Click to expand...
Click to collapse
Ahh, Sorry to hear about the perfomance, was really looking forward to getting the interface on this device with smooth operation. One thing to note though, and this is something that I inquired about with the Windows ROM versions, is that my device came installed with Windows Mobile 6.1. I wonder if that would make a difference at all. Anyway, No big deal really. Right now my challenge is to get the GPS working. Keep getting the "No Valid GPS signal" etc.. and I've tried it everywhere.. suggestions? (sigh) Anyway, Thanks for providing me the link for U19, I'll give it a go and see what happens.
This message simply means that is has not locked onto a GPS Satellite signal yet. My phone has taken as long as 10 min to lock on (when indoors). It is significantly faster when outdoors.
FYI
COM: 5
Baud: 4800
(If using TomTom choose "Other NMEA GPS reciever")
If your phone came with WM6.1 would it be possible for you to dump an image of it for all of us with 6.0?
I have been trying to get the Image provided by matagatoz with no success.
I believe that na external program was used to first update the bootloader before updating the ROM. since I nether have this program or the updated bootloader all my attempts to upload this image have failed.
I have even attempted a SD card install but have not found an appropriate combination of file name of image, or key press combo for updating
I found that holding down Power and the End Call button resets device to factory defaults. Holding the end call and pressing the reset does the same thing. I have not found any other key press combination's that do anything else.
Update
Did you try to reboot it using Power + circle button, or turning it on with that combination... is supposed to load teh image file into rom from SD card with that
matagatoz said:
Did you try to reboot it using Power + circle button, or turning it on with that combination... is supposed to load teh image file into rom from SD card with that
Click to expand...
Click to collapse
Any clue as to what to name the image?
I have tried your key combo (reset while pressing circle) and the device shuts off and is unresponsive (nothing on screen) until it is reset again (will not power back on)
I think we may be on to something I think we just need the correct file name.
Currently I have tried;
HTC.nbh
HTY.nbh
ELFIMG.nbh
ELF0IMG.nbh
UPLOADER.IMG
Flash Procedure ( images on DOC inside ROM download RAR )
Xuzhou 999ppc smart phone network
3.13 before the escalation of the original guidelines
Web site: www.999ppc.com
Entities shop Address: Xuzhou Huaihai Road Hongqiao 137 million electronic market on the second floor A2-53
Tel :0516-82580216 Mobile: 13914898099 (晁生), 13092311039 (single Health) QQ: 49360705,65872551 QQ exchange group HTY group: 57,841,094
Taobao shop: http://shop36275237.taobao.com/
First, before the 3.13 version 6.1 upgrade steps:
Note: upgrading the necessary equipment (computers, USB line, leave the battery fixture), veneer, upgraded machine can be used tweezers to connect TP3, TP17 trigger. As a result of individual trigger abnormal escalation after using fake battery upgrade.
1. Intercalation USB line to install drivers. (Installed after the pull-out USB line)
2.2. Open decompression after the upgrade software,
3. Click on the upgrade software, upgrade function keys.
4. Connect USB cable, shorted PCBA contact.
5. Upgrade to connect the success of the upgrade started.
6. The upgrade is complete
Second, after the 3.13 version of Brush Tutorial:
1, to prepare a capacity of less than 1G cards tf.
2, will be available compression package (uploader.img) copied to the card's root directory
3, to ensure that your battery not too little, at least above 50%
4, will be shut down mobile phone and the battery is removed, place will be mounted on a mobile phone
5, copy files to the TF card into the phone TF bed
6, at the same time hold down the "power button + the middle of a round navigation button" after a few seconds the screen "update"
7,几十秒, the phone will automatically re-starting, so Q5 your success on the Brush