I got the phone from a guy on EBay and though it is unlocked to all networks and works with my Orange SIM, how do I know if it is CID unlocked ? :?
you will not know if it is CID unlocked.
your best bet is to CID unlock it anyway.
it wont harm the phone to CID unlock more than once.
If you just want a generic ROM and are happy with the one you're running right now (Minus the o2 junk) just hard reset your device and then when it gets to the "wait three seconds" part, soft reset right when it gets to that screen. It will prevent WM5 from installing all of O2s crap on there and you have basically a clean slate version of what ROM you're running.
I've bought myself a MDA Vario (T-mobile NL).
But i have a other provider so i treid to unlock it which failed.
So i downgraded to IPL:1.01 and SPL:1.01 using the button 1.05 rom.
And then unlocked using lokiwiz - HTC Wizard Unlocker UPDATE Version 0.2b.
I also unlocked the CID and i didn't see any errors in my dos prompt.
Now i am trying to upgrade again and it keeps failing, i get to the green red bleu screen but then it hangs. The phone works but i want newer software.
When i boot it says i have: IPL:1.01 and SPL:1.01.0000 GSM:1.12.10.0 and OS:1.5.4.2.
When i try to run lokiwitz again to unlock my CID it says that a file is inuse and doesn't finish. The first time it didn't do this.
I like to upgrade to: T-Mobile 2.26 ROM or http://forum.xda-developers.com/showthread.php?t=330080, i preffer the second rom.
Can someone tell me what is wrong, is it possible the CID unlock failed and it doesn't show?
MSSH said:
I've bought myself a MDA Vario (T-mobile NL).
But i have a other provider so i treid to unlock it which failed.
So i downgraded to IPL:1.01 and SPL:1.01 using the button 1.05 rom.
And then unlocked using lokiwiz - HTC Wizard Unlocker UPDATE Version 0.2b.
I also unlocked the CID and i didn't see any errors in my dos prompt.
Now i am trying to upgrade again and it keeps failing, i get to the green red bleu screen but then it hangs. The phone works but i want newer software.
When i boot it says i have: IPL:1.01 and SPL:1.01.0000 GSM:1.12.10.0 and OS:1.5.4.2.
When i try to run lokiwitz again to unlock my CID it says that a file is inuse and doesn't finish. The first time it didn't do this.
I like to upgrade to: T-Mobile 2.26 ROM or http://forum.xda-developers.com/showthread.php?t=330080, i preffer the second rom.
Can someone tell me what is wrong, is it possible the CID unlock failed and it doesn't show?
Click to expand...
Click to collapse
download WST TOOL from the link below and apply to check the unlock staus of your phone,if it says locked again apply the method of unlocking correctly
http://forum.xda-developers.com/showthread.php?t=329170
Error:
'When i try to run lokiwitz again to unlock my CID it says that a file is inuse and doesn't finish. The first time it didn't do this.'
I think you did not copied the Enablerapi.cab file in your phone correctly or executed it in there
good luck
Fixed it,
After reinstalling the EnableRapi.cab which got lost in some sort of way. Everything went A ok
MSSH said:
Fixed it,
After reinstalling the EnableRapi.cab which got lost in some sort of way. Everything went A ok
Click to expand...
Click to collapse
GRRRRRRRR8
Glade I was of any help,Happy flashing
Good luck
So I've upgrade my old 8125 successfully - got a new one due to a second USB port coming off main board. This new one is a slightly newer model - T2. Anywho - Was running Lokiwiz to CID and SIM unlock. Successfulyl Sim unlocked - also THOUGHT i successfully CID unlocked it (based on the progress of the program - all the way through auto hard reset),
but apparantly I didn't (as confirmed by the MTTY tool telling me I don't have sufficient privelages to create image of rom and an invalid Vendor ID error upon tmobile rom RUU). Also i get the familiar "fat format failure" message at the option screen when hard resetting.
So i can flash the heck out of the device with old and new Cingular roms as well as the TouchFlo and Touch Diamond roms but the only thing that changes after successful flashing is the splash screen and depending on the ROM the IPL/SPL number. The device remains frozen and hangs on the Boot Loader screen.
So in attempt to get this thing up and running i need a sanity check.
Mmy first question is
1) Based on info above would you agree the device is still CID unlocked?
2) Is there (cuz I can't find one) a utility besided IMEI unlock to get into the phone and CID unlock it through the RBG boot loader screen?
3) Since I UNSUCCESSFULLY CID unlocked the device using Lokiwiz in the first place - I still have the output file from Lokiwiz - is there a way that the IMEIUNLOCK progrogram from IMEI UK can read this binary file and unlock the device or do i just need to pony up the 40bucks and CID unlock this.
I can't think of another way to get back to a functioning device.
Additional Thoughts
I also had a thought - which is probably an impossibility - but is there any way if I get the IMEI unlock code from Cingular to somehow get it into the IMEI Unlock software or use some other program like MTTY to insert that code into the phone?
DAMN! - I still don't know how the CID unlock didn't go through the first time. -Maye it was because the rom didn't roll back.
BRoke Down
and purchased IMEI unlock - unlocked just fine. Now I was able to upgrade to the Tmobile rom- INstallation went through without a hitch- now I am stuck on the Tmobile Boot loader- WTF can't I get past the boot loader on any rom I use? This makes no sense. Anyone have any thoughts? IPl and SPL at this point both show 2.26. THis is really pissing me off.
Try using the SD method to create a OS ROM dump and restore it. Some people works with it.
Hi,
Little problem in here. I've got tried to update IncS but something went wrong and I'm here.
Phone after boot goes straight into the bootloader like in pic.
Is there any solution to make it live?
pool.xy said:
Hi,
Little problem in here. I've got tried to update IncS but something went wrong and I'm here.
Phone after boot goes straight into the bootloader like in pic.
Is there any solution to make it live?
Click to expand...
Click to collapse
A little problem here; you did not give us enough information on what exactly you were doing to your IncS.
It appears you may have been trying to run the S-Off downgrade procedure or you simply tried to run and flash an older RUU?
At this point my suggestion would be to go to HTCDEV.com and download the last and final ICS RUU for the IncS and use that to get your phone back to a working state.
tried to s-off and failed
Device is't not recognized after boot into bootloader by RUU
is there is needed any drivers or sth?
pool.xy said:
tried to s-off and failed
Device is't not recognized after boot into bootloader by RUU
is there is needed any drivers or sth?
Click to expand...
Click to collapse
When you ran the Gingerbread RUU to achieve S-OFF, I assume there was an error code of some sort (ex. Error 131 or 170 or something). Can you please tell us which error code it was?
In the meantime, please download the latest and must recent ICS update from HTCDEV.com as tpbklake advised. I'm sure you need a phone to use.
pool.xy said:
tried to s-off and failed
Device is't not recognized after boot into bootloader by RUU
is there is needed any drivers or sth?
Click to expand...
Click to collapse
Ok, if you tried to S-Off, then you missed the very first step. Since you have hoot version 2.02.0002, the first thing you must do it UNLOCK the boot loader using the procedure at HTCDEV.com.
Since your HBOOT screen shows a LOCKED status, that means you didn't even do that step. Otherwise your HBOOT status would show either UNLOCKED or RELOCKED.
If you follow the unlock procedure at HTCDEV.com you will end up with all of the correct drivers you need.
Unlock bootloader procedure is stuck on the selecting yes/no in the phone. I can't select yes... "no" option goes ok, "yes" - cant accept.
When pressing the power burton few moments; phone vibrates only.
Any1 got this problem?
pool.xy said:
Unlock bootloader procedure is stuck on the selecting yes/no in the phone. I can't select yes... "no" option goes ok, "yes" - cant accept.
When pressing the power burton few moments; phone vibrates only.
Any1 got this problem?
Click to expand...
Click to collapse
When you select yes/no did u use the hardware keys because it should work.
everythig is ok, I can switch between yes/no without aby problem but only no is able to be accepted. Then it's rebooting and stuck on bootloader again.
Is there any difference about the PC? Maby I should try with other computer? os?
Actually i'm working on Asus laptop with Win7 64bit
pool.xy said:
everythig is ok, I can switch between yes/no without aby problem but only no is able to be accepted. Then it's rebooting and stuck on bootloader again.
Is there any difference about the PC? Maby I should try with other computer? os?
Actually i'm working on Asus laptop with Win7 64bit
Click to expand...
Click to collapse
Make sure you are using a USB 2.0 port and not a USB 3.0 port.
I've tried with other PC, this time on WinXP, the same result. The only thing I can't do is selecting YES when phone asking about unlock bootloader.
I've no idea what to do..
---
When trying to update RUU, windows says "Device not recognized" after rebooting to bootloader. Any idea what's wrong?
---
And one more question. Is there any difference if I choose other region of IncS? I mean WWE or Asia or Hutchison? Maby there is the problem with accepting bootloader unlock?
pool.xy said:
I've tried with other PC, this time on WinXP, the same result. The only thing I can't do is selecting YES when phone asking about unlock bootloader.
I've no idea what to do..
---
When trying to update RUU, windows says "Device not recognized" after rebooting to bootloader. Any idea what's wrong?
---
And one more question. Is there any difference if I choose other region of IncS? I mean WWE or Asia or Hutchison? Maby there is the problem with accepting bootloader unlock?
Click to expand...
Click to collapse
No that wouldn't make a difference because the unlock token that your phone generated is what is used to generate the unlock.bin file, not the region you picked.
The device not recognized usually indicates a driver problem. Did up install the HTC drivers on the XP machine?
Finally, maybe the reason you cannot select YES is because the unlock.bin that was generated with a bad unlock token.
You might want to try and regenerate the unlock token and get a new unlock.bin.
In device manager phone detected as My HTC. New unlock code gives same result as old one.
Is it a brick?
pool.xy said:
In device manager phone detected as My HTC. New unlock code gives same result as old one.
Is it a brick?
Click to expand...
Click to collapse
Ok, do you have the HTC Sync app running on your PC? If so, uninstall the app, but leave the HTC drivers installed.
Also you never did say whether you we're using an official HTC USB cable or not.
You are not bricked. You can always download the official ICS RUU/ROM from HTCDEV.com and use that to get your phone operational again.
I know but how to do that with that phone?
I've got Desire HD also and there is no problem with detecting it in adb. IncS - not.
Tried also to create goldcard and update with PG32IMG.zip form latest RUU_VIVO_ICS_35_S_TWM_TW_4.10.921.1_Radio_20.74.30.0833U_3831.18.00.11_M_release_266252_signed and gets stuck like on the pic then reboot.
pool.xy said:
I know but how to do that with that phone?
I've got Desire HD also and there is no problem with detecting it in adb. IncS - not.
Tried also to create goldcard and update with PG32IMG.zip form latest RUU_VIVO_ICS_35_S_TWM_TW_4.10.921.1_Radio_20.74.30.0833U_3831.18.00.11_M_release_266252_signed and gets stuck like on the pic then reboot.
Click to expand...
Click to collapse
So does it always hang trying to update the radio? Is this what happens when you tried to run the RUU or does it not get this far?
When trying to update RUU the program stops on the bootloader reboot, then nothing happened. Connection Error (171)
pool.xy said:
When trying to update RUU the program stops on the bootloader reboot, then nothing happened. Connection Error (171)
Click to expand...
Click to collapse
Are you the original owner of this phone? If not, where did you purchase it and was it operational before you attempted to S-Off?
Yes, it's my old contract phone... and it worked before as well.
I've read about xtc clip. Will it work to unlock bootloader.
pool.xy said:
Yes, it's my old contract phone... and it worked before as well.
I've read about xtc clip. Will it work to unlock bootloader.
Click to expand...
Click to collapse
No, not since you now have HBOOT version 2.02.0002.
The XTC Clip only worked on the IncS with HBOOT 1.09 and below.
---------- Post added at 08:59 AM ---------- Previous post was at 08:55 AM ----------
I had one more thing your could try when you attempt to run the unlock.bin.
Once the screen comes up where you try to select YES, have you tried disconnecting the USB cable to see if that would allow ou to select YES?
Ok, thanks for help anyway.
---edit
not helping.
----
Problem solved. I've just formatted HDD and installed fresh Win7 then RUU program worked smooth as well. Now phone runs new ICS.
I don't know what caused that issue but I'm happy that finally phone started.
I have bought 3 years ago A HTC One M7 in the USA from Verizon. I worked in the States for a year and returned to the Netherlands. I cancelled my mobile contract with Verizon and asked them to unlock the M7 because I wanted to use the phone in NL with a local mobile provider. This worked partially. I could call with the phone but connecting to internet was only possible at very low speed. Also app updates did not work.
I contacted a local dude from a local Android forum who presented himself as an Android M7 guru. He was prepared to help me to load a complete fresh European RUU on the phone. I followed his instuctions precisely and this went initially smoothly. Changing VID, CID and whatever all through ADB. The final step however was installing the ruu and after wiping the phone content it was ready to install. And then the device was not recognized anymore by ADB. He also forgot to instruct me to install TWRP as a first step. So, I donot have TWRP.
Now the phone is bricked and here are the symptons.
The phone is charging incl battery logo. The phone boots but is not passing the boot logo. I can get into HBoot and it says unlocked s-off but I get a error message USB last connected devive caused an error. ADB commands do not work because the phone is not recognized. I can select recovery and then the PC tells me that a HTC android device is connected , that the phone a recognized as a mass storage device (portable device D:/ however I cannot reach the Phone in any way. I have killed USB drivers a millions times, deleted ADB and reinstalled. Deleted HTC sync mngr a million times, installed every possible usb driver kit etc etc etc. Even cleaned the register. Nothing seems to fix the problem. Factory reset fails because it fails to mount emmc. emmc indicates 0 bytes
I have tried now everything possible for 6 months and you are probably my last resort before I throw the phone in the bin. Local HTC partners are not allowed to touch the phone because it is a Verizon OEM phone.
So, what do you think? Is there any change to make this phone alive or not?
janveltman said:
I have bought 3 years ago A HTC One M7 in the USA from Verizon. I worked in the States for a year and returned to the Netherlands. I cancelled my mobile contract with Verizon and asked them to unlock the M7 because I wanted to use the phone in NL with a local mobile provider. This worked partially. I could call with the phone but connecting to internet was only possible at very low speed. Also app updates did not work.
I contacted a local dude from a local Android forum who presented himself as an Android M7 guru. He was prepared to help me to load a complete fresh European RUU on the phone. I followed his instuctions precisely and this went initially smoothly. Changing VID, CID and whatever all through ADB. The final step however was installing the ruu and after wiping the phone content it was ready to install. And then the device was not recognized anymore by ADB. He also forgot to instruct me to install TWRP as a first step. So, I donot have TWRP.
Now the phone is bricked and here are the symptons.
The phone is charging incl battery logo. The phone boots but is not passing the boot logo. I can get into HBoot and it says unlocked s-off but I get a error message USB last connected devive caused an error. ADB commands do not work because the phone is not recognized. I can select recovery and then the PC tells me that a HTC android device is connected , that the phone a recognized as a mass storage device (portable device D:/ however I cannot reach the Phone in any way. I have killed USB drivers a millions times, deleted ADB and reinstalled. Deleted HTC sync mngr a million times, installed every possible usb driver kit etc etc etc. Even cleaned the register. Nothing seems to fix the problem. Factory reset fails because it fails to mount emmc. emmc indicates 0 bytes
I have tried now everything possible for 6 months and you are probably my last resort before I throw the phone in the bin. Local HTC partners are not allowed to touch the phone because it is a Verizon OEM phone.
So, what do you think? Is there any change to make this phone alive or not?
Click to expand...
Click to collapse
You cant flash the European ruu on a verizon m7, only the verizon ruu will work on ne this CDMA variant. Now you must have fastboot working to 1) revert your cid back to verizon 2)flash TWRP tout le get adb working and change back your mid to verizon and 3) flash the verizon ruu.
alray said:
You cant flash the European ruu on a verizon m7, only the verizon ruu will work on ne this CDMA variant. Now you must have fastboot working to 1) revert your cid back to verizon 2)flash TWRP tout le get adb working and change back your mid to verizon and 3) flash the verizon ruu.
Click to expand...
Click to collapse
Thanks Alray for youe quick respons, I already figured out that Verizon was harware incompatible with European HTC's. Yes, I need tpo change CID, MID etc. but.......... How do I get my fastboot working?
janveltman said:
Thanks Alray for youe quick respons, I already figured out that Verizon was harware incompatible with European HTC's. Yes, I need tpo change CID, MID etc. but.......... How do I get my fastboot working?
Click to expand...
Click to collapse
make sure the correct drivers are installed on your computer and try other usb ports (2.0) and cable.
There is nothing you can do to fix your phone without fastboot...