Related
I unlocked my G3 easy..
Now I read you cant unlock a G4 and some say you can (for free that is)
All I need is a SIM unlock for my G4
Where is the cut to the chase post on Sim unlocking a G4.
Thanks,
Jason
Sorry if this is the elevendybillion post but my head is pounding from the yes no crap lol And this is my only phone
Ok here it is Instructions for SIM Unlocking your Prophet :
1. Download ftp://xda:[email protected]/Uploads/Prophet/Prophet-tools/Lokiwiz03a.zip
2. Unzip Lokiwiz03a.zip somewhere on your computer
3. Make sure that your phone is connected via ActiveSync with the computer
4. Execute lokiwizMSL.bat on your computer
If it states: "Could not update itsutils.dll to the current version, maybe it is in use?"
Do the following :
*Copy the cab's from the Utils folder in the Lokiwiz03a.zip file to your Prophet and execute them.
(There are two files : "Cert_SPCS.cab" and "EnableRapi.cab")
*Execute lokiwizMSL.bat on your computer
5. It will give you the SIM unlock code after it runs, write it down somewhere.
6. Just get a different SIM from the one your phone is locked to, and install it in the phone (you have to turn off your phone)
7. Turn on your phone
8. When it asks your pin code enter your normal pin.
9. It then asks you for the Service Provider Unlock Code: Here you insert the SIM unlock code you wrote down in step 5.
10. That's it, enjoy your unlocked Prophet !
It Took me for ever but i found it
??
hi
what if it says system could not find path specified
gvattes said:
hi
what if it says system could not find path specified
Click to expand...
Click to collapse
You are not following the instructions correctly or missing any step.Perhaps you are not pasting and executing the two files "Cert_SPCS.cab" and "EnableRapi.cab" correctly in your phone.Reread the guide again and do it correctly,ok
Cheers!
Unlock code does not wok
I have a Wizard G4. I have run Lokiwiz3a and it generated an eight digit unlock code. I have entered that code 4 times. It tells me the unlock code is not valid and I that I have tried 4 times. Wait and try again. Any suggestions, please?
Unlock code does not work
I have a Wizard G4. I have run Lokiwiz3a and it generated an eight digit unlock code. I have entered that code 4 times. It tells me the unlock code is not valid and I that I have tried 4 times. Wait and try again. Any suggestions, please?
Worked like a charm! Thanks a load!
THANKS a LOT
Excellent. Worked superb. Thanks a lot.
Just wanna say Thank You!
Hi!
Thanks for the great instructions, I also tried v2 but failed. ;-)
However due to you instructions it worked fine!
Now I still need to get rid of the branding - but that´s another story!
Anyway, MANY THANKS!!!
Alex.
Thank you
I have an MDA that has seen better days and got a Cingular 8125...I spent 5 hours reading boards about unlocking it...THANK YOU IT WORKED!!!
Anyone know why it won't generate a token for me? I feel like I'm making a stupid mistake here, but it reboots to fastboot, tells me to copy the ID token and paste it into the HTC page. Makes sense, but there's no token to copy?
tekhna said:
Anyone know why it won't generate a token for me? I feel like I'm making a stupid mistake here, but it reboots to fastboot, tells me to copy the ID token and paste it into the HTC page. Makes sense, but there's no token to copy?
Click to expand...
Click to collapse
Are you requesting the token from the command prompt while connected but not active sync. I think the command is fastboot get_identifier_token or whatever is on the HTC dev site. Then the in the command prompt it will suddenly display like 17 lines of code ..it will have a start and a stop..
mjh68 said:
Are you requesting the token from the command prompt while connected but not active sync. I think the command is fastboot get_identifier_token or whatever is on the HTC dev site. Then the in the command prompt it will suddenly display like 17 lines of code ..it will have a start and a stop..
Click to expand...
Click to collapse
Yeah, I just did it in the command line. HTC Super Tool is supposed to just run the script for you, but it didn't seem to work for me. The get identifier command worked just fine.
i had the same problem so i ran it manually
I have the phone in Bootloader mode (holding down power and volume down keys). I have all the required software installed. I use the command prompt to get my token and copy the info into the requisite slot in the HTC website window and when I hit the continue button I get an error message "Error Code: Invalid Bootloader Token Length.
Error Reason: The submitted Token appears to be the wrong length and won't work"
I have tried multiple times on two different computers. Always the same error. It is 7:30 pm EDT. I need help cuz I may be running out of time.
DiggerG said:
I have the phone in Bootloader mode (holding down power and volume down keys). I have all the required software installed. I use the command prompt to get my token and copy the info into the requisite slot in the HTC website window and when I hit the continue button I get an error message "Error Code: Invalid Bootloader Token Length.
Error Reason: The submitted Token appears to be the wrong length and won't work"
I have tried multiple times on two different computers. Always the same error. It is 7:30 pm EDT. I need help cuz I may be running out of time.
Click to expand...
Click to collapse
You aren't copying it right. Read the instructions and ensure you are only copying the information it wants
Sent from my HTC One using xda premium
Finally got it to work, but I'm not sure what I did differently. Put Command prompt window next to website window and that did it, but don't know why. Anyhow I have my email.
And I'm unlocked!!!
mine is stuck at waiting for device after i put in the command. Is there anyway anyone can send me the fastboot, adb, and adbwinapi.dll they used? I'm wondering if mine just isn't the right one but they should be. also i have the phone hooked up first and then go into fastboot and it says fastboot usb before i type in the command
thanks for any help
What do you mean "Stuck waiting for device after I put in the command"? If you pm me an email address, I can send the files tonight when I return from work.
DiggerG said:
What do you mean "Stuck waiting for device after I put in the command"? If you pm me an email address, I can send the files tonight when I return from work.
Click to expand...
Click to collapse
I type in "fastboot oem get_identifier_token" and then it displays waiting for device but doesn't do anything after that I waited for 30 minutes the first time and it stayed saying that. Ok I'll PM it now thank you
brom66an6 said:
I type in "fastboot oem get_identifier_token" and then it displays waiting for device but doesn't do anything after that I waited for 30 minutes the first time and it stayed saying that. Ok I'll PM it now thank you
Click to expand...
Click to collapse
The device isnt connected properly to the computer. Make sure you open your command prompt in the android folder and have the files within the same folder (i did this on OS X)
And then check to make sure you the computer recognizes the phone with
fastboot devices
You should see your device listed if it is connected properly.
brom66an6 said:
I type in "fastboot oem get_identifier_token" and then it displays waiting for device but doesn't do anything after that I waited for 30 minutes the first time and it stayed saying that. Ok I'll PM it now thank you
Click to expand...
Click to collapse
Did you install the HTC Sync Manager or install the HTC USB drivers from another source? Your phone won't be detected until you have the drivers installed. (I'm assuming you're using a Windows computer)
brom66an6 said:
mine is stuck at waiting for device after i put in the command. Is there anyway anyone can send me the fastboot, adb, and adbwinapi.dll they used? I'm wondering if mine just isn't the right one but they should be. also i have the phone hooked up first and then go into fastboot and it says fastboot usb before i type in the command
Either need htc drivers or your not in fastboot usb/bootloader
thanks for any help
Click to expand...
Click to collapse
If your getting that error, you have fastboot and adb but you haven't installed htc drivers yet.
If you don't have fastboot/adb files you will get a unknow command error.
Sent from my SPH-L710 using Tapatalk 2
*edit - I got it taken care of now i uninstalled and reinstalled the drivers and it worked this time. Thank you everyone for the help.
has anyone received the "Error Code (10) A request for the USB descriptor failed" error message? i can't get my laptop to seen my device in fastboot mode. i've installed/uninstalled the HTC drivers but no change. weird part is that i can communicate with my device via ADB when booted normally. any suggestions would be appreciated.
Waiting (and waiting) for device
18th.abn said:
If your getting that error, you have fastboot and adb but you haven't installed htc drivers yet.
If you don't have fastboot/adb files you will get a unknow command error.
Sent from my SPH-L710 using Tapatalk 2
Click to expand...
Click to collapse
I'm having exactly the same issue as brom66an6. fastboot starts, but never proceeds from "waiting for the device". If this is a driver problem, what drivers need to be installed on the phone?
what next??? I have the identifier token..
DiggerG said:
And I'm unlocked!!!
Click to expand...
Click to collapse
Great for you, I can't wait to get there myself.
It was late last night and I was one click away, but wan't sure how long until the next break stop would be, so I went to bed.
Now, I cannot recall what I was supposed to do. Can anyone please shed some light on the next instructions, I can no longer access these as I believe it was shown when you click to continue??
I have all the files/drivers and token placed in the same location on my drive and as a guess I've also copied the token .zip file to the SDcard on my HTC One X (vodafone stamped
I really wished they have a removable battery and media card support!! I have just purchased a new battery from eBay that proclaims a new chip on it that prevents overcharging. So that should be interesting, since the HTC charger is not a switching charger like my BlackBerry ones were.
What I want:
ROOT
a new clean/fast/efficient ROM, was thinking clockworkmod.
Since I have zero experience and limited time to troll through forums these days, I am really finding it hard to find a REALLY simple step by step guide to perform this. I know, it's not a simple proccess, I know, but perhaps just the steps in a efficient, simple list, overlooking stuff like backups etc, but perhaps a TIP to mention it would be a good idea as the next step will wipe everything etc
Thanks if you're still reading and perhaps WERE at my stage once before.
I'm sure custom ROMs are a personal preference, but any bad points about ROMs would probably be better than selling the good points.
CWM should be fine for my first attempt???
MANY thanks in advance for your time.
Steve.
[EDIT]
I'm now unlocked!!!!
I found the website that I was following, it is fantastic and just the right amount of simple for me.
Check it out...
www*droid-now*com/2013/08/htc-one-unlocking-bootloader-installing-custom-recovery-and-root/
Amazing Thanks..
DiggerG said:
Finally got it to work, but I'm not sure what I did differently. Put Command prompt window next to website window and that did it, but don't know why. Anyhow I have my email.
Click to expand...
Click to collapse
That sounds stupid... but it works, worked for me...
hi
i am trying to unlock the bootlaoder for my new htc m9
after i got the unloch_code, i receive this msg in cmd
target reported max download size of 800000000 bytes
sending 'unlocktoken' (0 KB)...
OKAY [ 0.009s]
writing 'unlocktoken'...
(bootloader) flash unlocktoken
(bootloader) [KillSwitch] : /dev/block/bootdevice/by-name/frp
(bootloader) [KillSwitch] Last Byte is 0X01, enable unlock
FAILED (remote: UnlockToken Verify Fail!!)
finished. total time: 0.038s
please help
what is missing ?
Can someone answer this
My htc one x9 gets recognized by my laptop everything works well
Lequired software is installed properly
And i try to type in fastboot devices and my phone appears to be in fastboot
But when i type fastboot oem get_identifier_token it says FAILED(remote:unknown command)
Finished.time:0.005
Plz im begging for help
Mine struck after the entry of code fastboot OEM get_identifier_token and my device is already detected and it's showing three dots "..." And that's it
I'm following this https://www.getdroidtips.com/android-10-q-sony-xperia-x/ guide about changing ROM of my phone to Android 10. My Xperia X is stuck on Android 8
and isn't getting any further upgrades. It gets only security patches. But that will end soon too.
I got unlocking code from Sony but I got a pushback from fastboot:
running fastboot -i [received code here]
resulted in error: invalid vendor id '[received code here]'
How should I proceed ?
I can't remember exactly but I think you need to put two zeros or so in front of your code. When you know what to look for it should become obvious when reading Sony's unlocking page I think it was.
*EDIT* I think you need to add 0x according to https://forum.xda-developers.com/t/cant-unlock-bootloader.2937836/
armorgeddon said:
I can't remember exactly but I think you need to put two zeros or so in front of your code. When you know what to look for it should become obvious when reading Sony's unlocking page I think it was.
*EDIT* I think you need to add 0x according to https://forum.xda-developers.com/t/cant-unlock-bootloader.2937836/
Click to expand...
Click to collapse
Yeah it is sorted now. Cheers !
Just a quick heads-up.
unlock token - OnePlus (United States)
www.oneplus.com
By the way, to root without readily available stock firmware, first unlock bootloader, then boot a pre-rooted GSI with DSU Sideloader, pull stock boot partition from there, and finally patch/flash it. This applies to the Open variant as well.
AndyYan said:
Just a quick heads-up.
unlock token - OnePlus (United States)
www.oneplus.com
By the way, to root without readily available stock firmware, first unlock bootloader, then boot a pre-rooted GSI with DSU Sideloader, pull stock boot partition from there, and finally patch/flash it. This applies to the Open variant as well.
Click to expand...
Click to collapse
Tried to unlock but apparentpy my device only has 7 digits in the serial number which keeps me from being able to use the website to request the unlock code.
I used the debloat script I found on n200 threads to get oem unlock on option. T-Mobile variant
PsYk0n4uT said:
Tried to unlock but apparentpy my device only has 7 digits in the serial number which keeps me from being able to use the website to request the unlock code.
I used the debloat script I found on n200 threads to get oem unlock on option. T-Mobile variant
Click to expand...
Click to collapse
Try prepending 0s?
Well. I was thinking that doing that would make the unlock token they give me different from what the phone would be expecting
PsYk0n4uT said:
Well. I was thinking that doing that would make the unlock token they give me different from what the phone would be expecting
Click to expand...
Click to collapse
Tried adding zero on front and back of serial it just tells me invalid serial
PsYk0n4uT said:
Tried adding zero on front and back of serial it just tells me invalid serial
Click to expand...
Click to collapse
Chatting with OnePlus hasn't yielded anything so far
Just a tip, because in my infinite forgetfulness I wasted an hour last night trying to figure out why I was getting the error, fastboot could not open target HAL.
Remember that you must request the unlock code from fastboot, not fastbootd. Which is what you will boot into if you issue adb reboot fastboot.
So here's a quick step by step.
1.Enable usb debugging. 2. Connect your device and allow access for the computer. My device asks if I want it to charge or transfer files. Select transfer files/Android auto and then use adb start-server. May have to unplug the USB cable and reconnect. Select "always allow this device/PC".
3. Issue "adb devices" to make sure your connected.it should list your device by it's serial number. If not then try unplugging the device and revoke adb authorizations in dev options and toggle USB debugging off and back on, may even need to reboot the device to get it to connect after doing this.
4. If your device is listed under devices go ahead and issue "adb reboot fastboot"
5. Once rebooted issue "fastboot devices" and make sure the device is listed again.(If not listed make sure you have your driver's installed correctly and fastboot is installed correctly, may need to install Android SDK into same folder as fastboot)
6.You can select English or whatever language if you want but it doesn't seem necessary.You are in fastbootd mode you will see if you DO select a language.
So from here issue"fastboot reboot bootloader" device will reboot and you will have scrollable option at the top beginning with a big green START at the top. This is regular fastboot And where you wanna be to get your unlock code for submitting to Oppo for your unlock token.
7. Issue "fastboot oem get_unlock_code"
8. It should return the info you need, you will also need your IMEI number when submitting so be sure to copy that down.
you can copy and paste the unlock code into notepad or Word and delete out the extra stuff so your left with just the two lines of your unlock code as one single contiguous string of numbers.
8. Go to the link listed by OP and submit the required info. And wait for what seems like forever.
ADB/Fastboot commands-quick recap.
1. adb reboot fastboot
2. fastboot reboot bootloader
3. fastboot oem get_unlock_code
PsYk0n4uT said:
ADB/Fastboot commands-quick recap.
1. adb reboot fastboot
2. fastboot reboot bootloader
3. fastboot oem get_unlock_code
Click to expand...
Click to collapse
Simply "adb reboot bootloader". You won't need fastbootd until GSIs (which I already did ofc).
Thanks, definitely a quicker way to get to fastboot. I guess I wasn't sure if you could reboot directly. Seems maybe I was confusing an older device where you had to reboot to fastboot then "fastboot reboot fastboot" to get to fastbootd for a whole different reason.
This one goes directly to fastbootd when you "adb reboot fastboot"
Nice catch.
with this particular model in scope, what do either of you guys suggest I do if I have gottne the age old bricked message "destroyed boot/recovery image"".. I've tried the MSMTool route and cna't get it to register under Device Manager with the Qualcomm drivers.. It's highly upsetting..
I'm not really sure to be honest, this is my first OnePlus device and just trying to contribute anything I can to get the N20 section up and going as I make progress with the device.
Just a quick search though turns up this and maybe it could be of use if you can still access the bootloader.
the current image(boot/recovery) have been destroyed
I updated my oneplus 8t to KB2005_11.C.11 (OOS 12 ) by first booting to twrp-3.6.1_11-0-kebab.img and then flashed the KB2005_11_C_OTA_1100_all_362b9b_10100001.zip. After the upgrade I had no mobile data on t-mobile and had Volte instead of 5g...
forum.xda-developers.com
Someone mentions extracting the boot.img from stock image and flashing it. I would imagine it should work for you if the stock firmware can be found and circumstances are similar. Maybe at least a start. Wish I could be of more help, maybe someone else can chime in that knows more.
Try Linux, maybe a live dist. if your on a windows machine that won't recognize it just to get it into a state that you can work with it again.
Just an idea, I don't want to steer you wrong as i still have a lot to learn
DrScrad said:
with this particular model in scope, what do either of you guys suggest I do if I have gottne the age old bricked message "destroyed boot/recovery image"".. I've tried the MSMTool route and cna't get it to register under Device Manager with the Qualcomm drivers.. It's highly upsettinghav
Click to expand...
Click to collapse
DrScrad said:
with this particular model in scope, what do either of you guys suggest I do if I have gottne the age old bricked message "destroyed boot/recovery image"".. I've tried the MSMTool route and cna't get it to register under Device Manager with the Qualcomm drivers.. It's highly upsetting..
Click to expand...
Click to collapse
I want to try and help but I'm so new it's sketchy I don't want to say something and get bashed
Please feel free to comment. Don't worry about the trolls. We would love to have you to be part of this conversation. If you have suggestions just post them, and if your unsure about anything just mention that you are. It's a great way to learn. Don't worry about negative feedback, take it as constructive criticism. You may find that the feedback can clear up many questions and/or misconceptions. You never know how your dialogue with other members could help someone else in the future. These forums are here to document all of it just for that purpose. We are all here to learn or help others who want to learn. Though this account is only a year old I have been around these forums on and off for many years and I learn something each and every time I come in search of wisdom. I'm by no means an expert but I find that others benefit from my questions and answer just as much as I have over the years.
Fyi according to a recently made friend who also had the 7 digit serial issue, they were told by OnePlus their dev team is working on an OTA update that will resolve the serial number issues. I'm not sure how that's going to work but I saw the email between them and Oppo support
I guess this must be a widespread issue that they feel is cheaper to invest the amount of money it takes for r&d to come up with a fix than it was to replace a few devices or attempt to do remote repairs.
But this also makes me wonder what avenue they will take to correct the issue.
Also I wonder if someone with the right skillset could gather enough bootloader unlock codes along with the unlock tokens, serial, IMEI, pcba etc.. maybe the algorithm their using to generate the codes could be broken. I'm no crypto expert or math genius either, but if we have the variables to the equation minus one but have the answer, isn't this pretty simple almost pre-algebra?
I mean I guess their not worried about enough people being brave enough to give out sensitive info like that. But maybe Im just ignorant of the complexity of these algorithms.
64 digit key on one end
T-Mobile bought sprint and they have T-Mobile sims no. But I understand that sprint is still a somewhat seperate company (tried to buy a T-Mobile phone and it would not activate on my sprint account. So I bought this from the sprint side of the T-Mobile site so I knew it would work but I assume this is a sprint phone and not a T-Mobile phone so this method would not work.
Can anyone confirm this?
PsYk0n4uT said:
Please feel free to comment. Don't worry about the trolls. We would love to have you to be part of this conversation. If you have suggestions just post them, and if your unsure about anything just mention that you are. It's a great way to learn. Don't worry about negative feedback, take it as constructive criticism. You may find that the feedback can clear up many questions and/or misconceptions. You never know how your dialogue with other members could help someone else in the future. These forums are here to document all of it just for that purpose. We are all here to learn or help others who want to learn. Though this account is only a year old I have been around these forums on and off for many years and I learn something each and every time I come in search of wisdom. I'm by no means an expert but I find that others benefit from my questions and answer just as much as I have over the years.
Click to expand...
Click to collapse
okay peep theres a way i put my oneplus into efu mode, hold both vol up and down then put usb c in continue to hold u should hear PC recognize it
So, before i do it, would deleting the modemst1/modemst2 partitions still let me bypass the t-mobile sim lock and let me unlock the phone like it did on the old oneplus phones?
Flashed a patched boot.img and lost modems. Anyone willing to post the modems? Are they device specific like a device partition?
Sim locked and trying to recover. No radios are working