ok i have tried searching but im a bit dumbfounded i restored my phone back to stock via a ruu , then i set s-on back via command fastboot oem writesecureflag 3 now i need to set it back to locked , would really appreciated being pointed in right direction if possible please ?
** edit tried C:\Android\com>htc_fastboot oem lock
...
FAILED (remote: unknown command)
finished. total time: 0.021s
htc_fastboot finished. total time: 0.179s
C:\Android\com>
C:\Android\com>fastboot oem lock
...
(bootloader) [KillSwitch] : /dev/block/bootdevice/by-name/frp
(bootloader) [KillSwitch] Last Byte is 0X00, disable unlock
(bootloader) [KillSwitch] oem unlock Turn Off!
OKAY [ 0.015s]
finished. total time: 0.016s
C:\Android\com>
tonnytech said:
ok i have tried searching but im a bit dumbfounded i restored my phone back to stock via a ruu , then i set s-on back via command fastboot oem writesecureflag 3 now i need to set it back to locked , would really appreciated being pointed in right direction if possible please ?
** edit tried C:\Android\com>htc_fastboot oem lock
...
FAILED (remote: unknown command)
finished. total time: 0.021s
htc_fastboot finished. total time: 0.179s
C:\Android\com>
C:\Android\com>fastboot oem lock
...
(bootloader) [KillSwitch] : /dev/block/bootdevice/by-name/frp
(bootloader) [KillSwitch] Last Byte is 0X00, disable unlock
(bootloader) [KillSwitch] oem unlock Turn Off!
OKAY [ 0.015s]
finished. total time: 0.016s
C:\Android\com>
Click to expand...
Click to collapse
Use SunShine again and choose S-OFF/Locked. Afterwards go S-ON again, just like you did before.
You need to have flashed an RUU intended for your original model, not just stock.
errikosd said:
Use SunShine again and choose S-OFF/Locked. Afterwards go S-ON again, just like you did before.
You need to have flashed an RUU intended for your original model, not just stock.
Click to expand...
Click to collapse
thanks for the reply i sorted it as you suggested already appreciate reply thou
Related
Is there a way to sim unlock my htc one v?
I've unlocked the bootloader, rooted the device, put it on s-off, installed CyanogenMod Android 4.1.2, kernel version 3.0.16-HELLBOY; i flashed the kernel and rom; i tried to upgrade the ruu but it returned me the error 131 which reffered to some incompatibility ruu, even tho it was the most appropiate one.
another thing i tried was to hack into the mmcblk0p6 and take the un_lock_code but the unlock.sh returned me this error:
[email protected]:/ # IMEI:
[email protected]:/ # UN_Lock_code:
[email protected]:/ # /system/unlock.sh[34]: + + : unexpected 'end of expression'
my radio is 3831.19.00.120. The network is locked on O2, UK. I've tried a lot of things, but nothing worked.
Can you help me guys?
Thanks in advance!
XTZY23 said:
Is there a way to sim unlock my htc one v?
I've unlocked the bootloader, rooted the device, put it on s-off, installed CyanogenMod Android 4.1.2, kernel version 3.0.16-HELLBOY; i flashed the kernel and rom; i tried to upgrade the ruu but it returned me the error 131 which reffered to some incompatibility ruu, even tho it was the most appropiate one.
another thing i tried was to hack into the mmcblk0p6 and take the un_lock_code but the unlock.sh returned me this error:
[email protected]:/ # IMEI:
[email protected]droid:/ # UN_Lock_code:
[email protected]:/ # /system/unlock.sh[34]: + + : unexpected 'end of expression'
my radio is 3831.19.00.120. The network is locked on O2, UK. I've tried a lot of things, but nothing worked.
Can you help me guys?
Thanks in advance!
Click to expand...
Click to collapse
That depends on what fastboot commands your hboot supports. If you have an eng hboot you can remove simlock with fastboot. But I cannot remember the command off hand. Connect up to the pc in fastboot mode and issue the.command fastboot oem h and it will output all the options available. Post them here for us all to learn from please
Sent from my HTC Desire S using Tapatalk
htc one v_commands
heavy_metal_man said:
That depends on what fastboot commands your hboot supports. If you have an eng hboot you can remove simlock with fastboot. But I cannot remember the command off hand. Connect up to the pc in fastboot mode and issue the.command fastboot oem h and it will output all the options available. Post them here for us all to learn from please
Sent from my HTC Desire S using Tapatalk
Click to expand...
Click to collapse
this is what it returned:
C:\Fastboot>fastboot oem h
...
(bootloader) command list
(bootloader) get_identifier_token
(bootloader) checkKeycardID
(bootloader) keytest
(bootloader) heap
(bootloader) boot
(bootloader) reset
(bootloader) powerdown
(bootloader) rebootRUU
(bootloader) heap_test
(bootloader) erase_phone_storage
(bootloader) gotohboot
(bootloader) rtask
(bootloader) task
(bootloader) enableqxdm
(bootloader) gencheckpt
(bootloader) readmeid
(bootloader) lock
(bootloader) writesecureflag
(bootloader) readsecureflag
(bootloader) readsimlocktype
(bootloader) clearsimlocktype
(bootloader) readcid
(bootloader) writecid
(bootloader) list_partition_emmc
(bootloader) load_emmc
(bootloader) check_emmc
(bootloader) check_emmc_mid
(bootloader) read_mmc
(bootloader) read_sandisk_fw
(bootloader) get_wp_info_emmc
(bootloader) send_wp_info_emmc
(bootloader) get_ext_csd_emmc
(bootloader) get_sector_info_emmc
OKAY [ 0.041s]
finished. total time: 0.042s
C:\Fastboot>
XTZY23 said:
(bootloader) readsimlocktype
(bootloader) clearsimlocktype
(bootloader) readcid
(bootloader) writecid
Click to expand...
Click to collapse
I would use these 2 sets here. First make a nandroid backup, just incase
Then issue these fastboot commands one after another and copy the results.
Fastboot oem readcid
Fastboot oem readsimlocktype
All good? Now first we want to change your cid to super. So issue this command
Fastboot oem writecid 11111111
Fastboot reboot bootloader
Fastboot oem readcid
Your cid should now show up as 11111111, that's 8 1's
All good? Lastly we issue these commands.
Fastboot oem clearsimlocktype
Fastboot reboot
Now just check your simcard and all should be well you can now flash any ruu for any carrier without issue, but always check its compatible with your model type first!
Sent from my HTC Desire S using Tapatalk
fisrt step:
C:\Fastboot>fastboot oem readcid
...
(bootloader) cid: O2___001
OKAY [ 0.003s]
finished. total time: 0.004s
C:\Fastboot>fastboot oem readsimlock
type
...
(bootloader) sdcc_init_memory_device done
(bootloader) Wait for AMSS ready
(bootloader) AMSS is ready
(bootloader) readsimlocktype: SimLockType: 0
OKAY [ 21.759s]
finished. total time: 21.760s
step 2:
C:\Fastboot>fastboot oem writecid 11
111111
...
(bootloader) AMSS is ready
(bootloader) buf_addr:4FC300,buf_size:200,start_sector:1739D
(bootloader) sdcc_init_memory_device done
(bootloader) Finish write sector address 1739D ...
(bootloader) writecid: successfully
OKAY [ 0.691s]
finished. total time: 0.692s
C:Fastboot>fastboot reboot-bootload
er
rebooting into bootloader...
OKAY [ 0.151s]
finished. total time: 0.153s
C:\Fastboot>fastboot oem readcid
...
(bootloader) cid: 11111111
OKAY [ 0.004s]
finished. total time: 0.005s
C:\Fastboot>fastboot oem clearsimloc
ktype
...
(bootloader) sdcc_init_memory_device done
(bootloader) Wait for AMSS ready
(bootloader) AMSS is ready
OKAY [ 21.758s]
finished. total time: 21.760s
C:\Fastboot>fastboot reboot
rebooting...
finished. total time: 0.155s
C:\Fastboot>
XTZY23 said:
fisrt step:
C:\Fastboot>fastboot oem readcid
...
(bootloader) cid: O2___001
OKAY [ 0.003s]
finished. total time: 0.004s
C:\Fastboot>fastboot oem readsimlock
type
...
(bootloader) sdcc_init_memory_device done
(bootloader) Wait for AMSS ready
(bootloader) AMSS is ready
(bootloader) readsimlocktype: SimLockType: 0
OKAY [ 21.759s]
finished. total time: 21.760s
step 2:
C:\Fastboot>fastboot oem writecid 11
111111
...
(bootloader) AMSS is ready
(bootloader) buf_addr:4FC300,buf_size:200,start_sector:1739D
(bootloader) sdcc_init_memory_device done
(bootloader) Finish write sector address 1739D ...
(bootloader) writecid: successfully
OKAY [ 0.691s]
finished. total time: 0.692s
C:Fastboot>fastboot reboot-bootload
er
rebooting into bootloader...
OKAY [ 0.151s]
finished. total time: 0.153s
C:\Fastboot>fastboot oem readcid
...
(bootloader) cid: 11111111
OKAY [ 0.004s]
finished. total time: 0.005s
C:\Fastboot>fastboot oem clearsimloc
ktype
...
(bootloader) sdcc_init_memory_device done
(bootloader) Wait for AMSS ready
(bootloader) AMSS is ready
OKAY [ 21.758s]
finished. total time: 21.760s
C:\Fastboot>fastboot reboot
rebooting...
finished. total time: 0.155s
C:\Fastboot>
Click to expand...
Click to collapse
Did it simunlock OK?
Sent from my Nexus 7 using Tapatalk
Hmm, maybe yes maybe not
It passed the sim network locked screen, but now it says "no network available" and when im making a call, it says "mobile network unavailable" \
I REINSTALLED THE RUU i was trying to install it in the first place and it worked. so thanks for your help
PS: the new challenge is this error: mobile network unavailable because it is disconnected
************update***************
1.last night i put s-on on my phone...but
2.even on s-off i could not unlock the bootloader after installing the RUU_PRIMO_U_ICS_40A_HTC_Europe_2.22.401.1_Radio_20.76.30.0835U_3831.19.00.120_release_273801_signed
3. no bootloader unlock->no root->no s-off->no simlock
4. the message header is ****Relocked**** and the error the i receive when i try to unlock the bootloader again is:
C:\Fastboot>fastboot flash unlocktoken Unlock_code.bin
sending 'unlocktoken' (0 KB)...
OKAY [ 0.640s]
writing 'unlocktoken'...
FAILED (remote: unlock token check failed)
finished. total time: 0.650s
***********fixed this one*************
HTC ONE toolkit 2.0-Squabbi-- saved me fro a lot o work! great thanks to squabbi!
XTZY23 said:
It passed the sim network locked screen, but now it says "no network available" and when im making a call, it says "mobile network unavailable" \
I REINSTALLED THE RUU i was trying to install it in the first place and it worked. so thanks for your help
PS: the new challenge is this error: mobile network unavailable because it is disconnected
Click to expand...
Click to collapse
http://www.sieempi.eu/blog/2011/09/22/universal-sim-unlock-for-s-offed-htc-devices-536 ok give this a bash pal. will hopefully fix the issue.
GSM problem/hardware problem
thanks heavy_metal_man for replies!
the config.dat file worked, partially i think, returning only one error: Open Cid file failed.
as i could see my phone does not react to find any mobile network available, even tho my phone is "reading" the simcard now. i can see contacts, messages, etc.
ps: i don't have the back cover. would that be the problem?
XTZY23 said:
thanks heavy_metal_man for replies!
the config.dat file worked, partially i think, returning only one error: Open Cid file failed.
as i could see my phone does not react to find any mobile network available, even tho my phone is "reading" the simcard now. i can see contacts, messages, etc.
ps: i don't have the back cover. would that be the problem?
Click to expand...
Click to collapse
The back cover for these kinds of phones usually have "antenna boosting" pads. My htc sensation gets no signal without the back cover on.
For anyone else I would recommend trying the linked website solution from sieempi before fastboot commands
Sent from my Nexus 7 using Tapatalk
So finally received my htc 10 and whelp im unable to unlock the bootloader.
sending 'unlocktoken' (0 KB)...
OKAY [ 0.016s]
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.047s
yes oem unlocking is enabled and this is the factory unlocked one preordered from HTC. Has anyone seen similar issues with their unit?
Sunderwear said:
So finally received my htc 10 and whelp im unable to unlock the bootloader.
sending 'unlocktoken' (0 KB)...
OKAY [ 0.016s]
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.047s
yes oem unlocking is enabled and this is the factory unlocked one preordered from HTC. Has anyone seen similar issues with their unit?
Click to expand...
Click to collapse
Try a different browser
Sunderwear said:
So finally received my htc 10 and whelp im unable to unlock the bootloader.
sending 'unlocktoken' (0 KB)...
OKAY [ 0.016s]
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.047s
yes oem unlocking is enabled and this is the factory unlocked one preordered from HTC. Has anyone seen similar issues with their unit?
Click to expand...
Click to collapse
i had the same issue and used Microsoft Edge browser and it worked as per suggestion from somebody here
I'm having the same issue. Can't figure it out
Different browser did not work for me.
Think I had this issue once when I didn't copy the code into the box properly, copy it exactly as they do first line to last, I tend to have to remove some leading text from each row.
I was getting this error too but didn't realize I generated the code before checking the OEM Unlocking option dialog. The code changes once you do so.
Pasting this code in will just give you an unlock code that fails with that error message. Make sure you did not accidentally do it backwards.
Not sure how browser would be an issue.
Using the Microsoft Edge browser worked for me, but I have no idea why
I've got the same problem. OEM unlocking is enabled and I've regenerated my unlock_code.bin after doing so. I've made sure there's no leading or trailing spaces in the oem token code thing I paste in. I've tried downloading the unlock_code.bin through Microsoft Edge. Exact same error as OP. Any clues?
Took me 3 tokens
Sent from my HTC 2PS6200 using XDA-Developers mobile app
A while ago i rooted my android Phone as per this guide: "http://forum.xda-developers.com/one-m9/general/guide-root-install-twrp-htc-one-m9-t3061133".
Now when trying to revert to stock as per this guide: "http://www.androidswiki.com/restore-htc-one-m9-to-stock-easy-guide-and-download-links/" i got locked out of my Phone.
As soon as i locked the bootloader as per the instructions the Phone wont boot into Android OS and i cannot transfer the RUU file to the SDcard as i get the error: "error: device not found".
when trying to unlock the device via the command: fastboot flash unlocktoken Unlock_code.bin
i get:
sending 'unlocktoken' (0 KB)...
OKAY [ 1.008s]
writing 'unlocktoken'...
(bootloader) flash unlocktoken
(bootloader) [KillSwitch] : /dev/block/bootdevice/by-name/frp
(bootloader) [KillSwitch] Last Byte is 0X00, disable unlock
(bootloader) [KillSwitch] oem unlock Turn Off!
OKAY [ 0.019s]
finished. total time: 1.027s.
the only things i can boot in atm are the download mode and the bootloader mode.
Please advice as how to proceed.
I bought a WWE HTC 10 to use in the states... I used sunshine and have s-off locked status, I changed the cid and mid to the unlocked us numbers and did a conversion using the htc ruu.exe, I have a red warning every time i start the phone about development purposes only etc... I figure this must have to do with the s-off so i want to set it back to on as though i just bought a usa unlocked model!
im in download mode
I tried the good old
Code:
fastboot oem writesecureflag 3
and i got this output
Code:
...
(bootloader) HTC KEY CARD VERSION: 7
(bootloader) VERIFY_BY_PROJECT_SIGN_KEY_FAIL hosd (-9)
FAILED (remote: Partition verify fail -9)
finished. total time: 1.024s
what am i doing wrong?
THC Butterz said:
I bought a WWE HTC 10 to use in the states... I used sunshine and have s-off locked status, I changed the cid and mid to the unlocked us numbers and did a conversion using the htc ruu.exe, I have a red warning every time i start the phone about development purposes only etc... I figure this must have to do with the s-off so i want to set it back to on as though i just bought a usa unlocked model!
im in download mode
I tried the good old
Code:
fastboot oem writesecureflag 3
and i got this output
Code:
...
(bootloader) HTC KEY CARD VERSION: 7
(bootloader) VERIFY_BY_PROJECT_SIGN_KEY_FAIL hosd (-9)
FAILED (remote: Partition verify fail -9)
finished. total time: 1.024s
what am i doing wrong?
Click to expand...
Click to collapse
Go to bootloader mode?
Sent from my SM-G935T using Tapatalk
didnt work in bootloader mode at all
Code:
...
FAILED (remote: unknown command)
finished. total time: 0.052s
didnt work in uru mode either
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem rebootRUU
...
OKAY [ 0.001s]
finished. total time: 0.002s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem writesecureflag 3
...
(bootloader) HTC KEY CARD VERSION: 7
(bootloader) VERIFY_BY_PROJECT_SIGN_KEY_FAIL hosd (-9)
FAILED (remote: Partition verify fail -9)
finished. total time: 1.042s
THC Butterz said:
didnt work in bootloader mode at all
Code:
...
FAILED (remote: unknown command)
finished. total time: 0.052s
didnt work in uru mode either
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem rebootRUU
...
OKAY [ 0.001s]
finished. total time: 0.002s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem writesecureflag 3
...
(bootloader) HTC KEY CARD VERSION: 7
(bootloader) VERIFY_BY_PROJECT_SIGN_KEY_FAIL hosd (-9)
FAILED (remote: Partition verify fail -9)
finished. total time: 1.042s
Click to expand...
Click to collapse
Actually if you still have the red warning then the Ruu likely didn't fully flash. You shouldn't have that message if it successfully flashes.
Sent from my SM-G935T using Tapatalk
dottat said:
Actually if you still have the red warning then the Ruu likely didn't fully flash. You shouldn't have that message if it successfully flashes.
Sent from my SM-G935T using Tapatalk
Click to expand...
Click to collapse
after speaking with jcase figgured out that because the ruu didnt mach the one the phone shipped with im sol for turning s-off back to s-on
THC Butterz said:
after speaking with jcase figgured out that because the ruu didnt mach the one the phone shipped with im sol for turning s-off back to s-on
Click to expand...
Click to collapse
Yeah I still believe that a fully flashed matching Ruu will clear that flag. Can you try flashing again and see if the dev flag clears?
Sent from my SM-G935T using Tapatalk
Hey so I have a razer phone and I am stuck in the bootloader "download" mode Oem Unlock is disabled and cant enable because I am in a boot loop and I can't install stock because I can't unlock bootloader. Can anyone help me?
did you ever fix
have the same problem right now any help would be appreciated
does fastboot recognize the device?
same problem
Hi, I have the exact same problem,
fastboot is working, but cannot unlock
Code:
fastboot oem device-info
(bootloader) Verity mode: true
(bootloader) Device unlocked: false
(bootloader) Device critical unlocked: false
(bootloader) Charger screen enabled: true
OKAY [ 0.008s]
Finished. Total time: 0.009s
Code:
fastboot flashing unlock
FAILED (remote: 'Flashing Unlock is not allowed
')
Finished. Total time: 0.004s
I cannot go into the android system, screen stay black, I need to wait for the battery to run out to test again from powered off phone (if I boot normally)
any help ?