Develop Bugs

[Q] HTC ONE V sim unlock

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

Unlocking bootloader for LEX727

Hi All.
I just bought the leeco pro 3 and want to unlock the bootloader. I followed the steps outlined in "X727 (US Model) Persistent bootloader unlock from 5.8.019s". I turned on USB debugging, permanently added USB device, and turned on the "allow oem unlocking option". Then, i rebooted to fast boot and tried the following commands and received an error.
Code:
:~$[B] fastboot oem device-info[/B]
...
(bootloader) Device product name: [le_zl1_oversea]
(bootloader) Device tampered: false
(bootloader) Device unlocked: false
(bootloader) Device critical unlocked: true
(bootloader) Charger screen enabled: false
(bootloader) Serial console enabled: false
(bootloader) Serial hw output enabled: false
(bootloader) Display panel:
OKAY [ 0.083s]
finished. total time: 0.083s
:~$ [B]fastboot oem unlock-go[/B]
...
FAILED (remote: oem unlock is not allowed)
finished. total time: 0.008s
:~$ [B]fastboot oem unlock[/B]
...
FAILED (remote: oem unlock is not allowed)
finished. total time: 0.004s
[email protected]:~$ fastboot reboot
rebooting...
finished. total time: 0.007s
My phone came with 5.8.020S (I think) and I tried the above steps with that version. Then i updated to 5.8.021S and tried again and received the same issue. I checked for more updates but none were found.
I am sure this issue has been solved somewhere but I just want to make sure I do not brick this device. Please help.

Developer Options ---> usb debug ---> open ..
Developer Options ---> Oem unlock ---> open ..
Have you enabled them?

lazye53 said:
Developer Options ---> usb debug ---> open ..
Developer Options ---> Oem unlock ---> open ..
Have you enabled them?
Click to expand...
Click to collapse
Thanks for the reply.. Yes. Both of those options are on. I have tried multiple times to turn them off and on and redo the unlock at fast boot, but i get the same error

sagarc88 said:
Hi All.
I just bought the leeco pro 3 and want to unlock the bootloader. I followed the steps outlined in "X727 (US Model) Persistent bootloader unlock from 5.8.019s". I turned on USB debugging, permanently added USB device, and turned on the "allow oem unlocking option". Then, i rebooted to fast boot and tried the following commands and received an error.
Code:
:~$[B] fastboot oem device-info[/B]
...
(bootloader) Device product name: [le_zl1_oversea]
(bootloader) Device tampered: false
(bootloader) Device unlocked: false
(bootloader) Device critical unlocked: true
(bootloader) Charger screen enabled: false
(bootloader) Serial console enabled: false
(bootloader) Serial hw output enabled: false
(bootloader) Display panel:
OKAY [ 0.083s]
finished. total time: 0.083s
:~$ [B]fastboot oem unlock-go[/B]
...
FAILED (remote: oem unlock is not allowed)
finished. total time: 0.008s
:~$ [B]fastboot oem unlock[/B]
...
FAILED (remote: oem unlock is not allowed)
finished. total time: 0.004s
[email protected]:~$ fastboot reboot
rebooting...
finished. total time: 0.007s
My phone came with 5.8.020S (I think) and I tried the above steps with that version. Then i updated to 5.8.021S and tried again and received the same issue. I checked for more updates but none were found.
I am sure this issue has been solved somewhere but I just want to make sure I do not brick this device. Please help.
Click to expand...
Click to collapse
For 5.8.021S, go to page 26 ....

sagarc88 said:
Thanks for the reply.. Yes. Both of those options are on. I have tried multiple times to turn them off and on and redo the unlock at fast boot, but i get the same error
Click to expand...
Click to collapse
I had this issue also this I solved it.
Undo the OEM allow to unlock reboot then enable OEM to unlock bootloader.
Still had the problem.
I ended up flash the bootloader then then ran the bootloader unlock commander and it worked.
Sent from my LEX727 using xda premium

mchlbenner said:
I had this issue also this I solved it.
Undo the OEM allow to unlock reboot then enable OEM to unlock bootloader.
Still had the problem.
I ended up flash the bootloader then then ran the bootloader unlock commander and it worked.
Sent from my LEX727 using xda premium
Click to expand...
Click to collapse
You need to flash 2 files via adb first, then run the unlock command.
I did it successfully for 021s
Sent from my LEX727 using Tapatalk

kukuteku said:
For 5.8.021S, go to page 26 ....
Click to expand...
Click to collapse
This worked perfectly!! Thank you very much.

Flashing Critical Locked
I'm just a dabbler in this stuff, but I think I understand everything required to get LineageOS on my LEX727. The problem is, in the process of learning, I think I locked the ability to flash aboot, and now I can't get the twrp recovery onto my phone. Does anyone have any ideas or know what to do? If I can do anything from here?
Thanks for any help!

MAHawbs said:
I'm just a dabbler in this stuff, but I think I understand everything required to get LineageOS on my LEX727. The problem is, in the process of learning, I think I locked the ability to flash aboot, and now I can't get the twrp recovery onto my phone. Does anyone have any ideas or know what to do? If I can do anything from here?
Thanks for any help!
Click to expand...
Click to collapse
What did locked ability flash abootd it d relock bootloader.
What did you ?
Sent from my SM-A730F using xda premium

[Q] problem with locking bootloader

Hello everyone.
I've got some strange problem with my pixel 2 xl.
I did googleand searched here to find any solution but I couldn't find any.
So, I unlocked the bootloader because I wanted to root my phone and install a custom rom.
But after a while I realized that I loved my phone more when he was unrooted... so I unrooted my phone with the "flash all.bat" that google provide us.
The strange thing is that everytime Im locking the bootloader Im getting a message "Can't find valid operating system...." and im getting a bootloops with that message.
the only way I can turn the phone on properly is by unlocking the bootloader and keep it that way.............
what should I do?
Is it bad if I just keep it the bootloader unlock?

Maybe try running the flash all to both slots and see if you can relock then?

rickysidhu_ said:
Maybe try running the flash all to both slots and see if you can relock then?
Click to expand...
Click to collapse
I think this is the correct answer. You're going to want to flash-all the factory image to both slots before relocking the bootloader.
fastboot getvar current-slot *(take note of the current slot this command returns)*
flash-all
fastboot --set-active= *(=a or =b to change slot to the opposite the first command returned)*
flash-all
fastboot flashing lock_critical
fastboot flashing lock
fastboot oem device-info
Verify that the returned device info after the last command is;
(bootloader) Verity mode: true
(bootloader) Device unlocked: false
(bootloader) Device critical unlocked: false
(bootloader) Charger screen enabled: true
Now you are back to 100% stock with locked bootloaders. Reboot and set up your factory fresh device.

Namolas said:
I think this is the correct answer. You're going to want to flash-all the factory image to both slots before relocking the bootloader.
fastboot getvar current-slot *(take note of the current slot this command returns)*
flash-all
fastboot --set-active= *(=a or =b to change slot to the opposite the first command returned)*
flash-all
fastboot flashing lock_critical
fastboot flashing lock
fastboot oem device-info
Verify that the returned device info after the last command is;
(bootloader) Verity mode: true
(bootloader) Device unlocked: false
(bootloader) Device critical unlocked: false
(bootloader) Charger screen enabled: true
Now you are back to 100% stock with locked bootloaders. Reboot and set up your factory fresh device.
Click to expand...
Click to collapse
thanks for your answer!
im trying to switch slots between a to b but it says to me "fastboot: unknown option -- set-active=b

Orpalili said:
thanks for your answer!
im trying to switch slots between a to b but it says to me "fastboot: unknown option -- set-active=b
Click to expand...
Click to collapse
Looks like you've got a space in between -- and set?
Needs to be one space after fastboot and that's all;
fastboot --set-active=b

I'm more interested in what Ill effects you had being rooted. Unless I'm actually using root to facilitate something in particular I can't even detect that root exists other than seeing the icons in the drawer...

Namolas said:
Looks like you've got a space in between -- and set?
Needs to be one space after fastboot and that's all;
fastboot --set-active=b
Click to expand...
Click to collapse
still not working :crying:

Orpalili said:
still not working :crying:
Click to expand...
Click to collapse
I don't know why, sorry. I just went through all the motions to make sure I didn't miss something but it all executes for me. Is that the only command not working for you??
Last login: Tue Feb 27 09:04:26 on ttys000
Codys-MBP:~ namolas$ fastboot devices
*****7/11****** fastboot
Codys-MBP:~ namolas$ fastboot getvar current-slot
current-slot: a
finished. total time: 0.001s
Codys-MBP:~ namolas$ fastboot --set-active=b
Setting current slot to 'b'...
OKAY [ 0.016s]
finished. total time: 0.016s
Codys-MBP:~ namolas$ fastboot flashing lock_critical
...
FAILED (remote: Set device locked! canceled)
finished. total time: 3.895s
Codys-MBP:~ namolas$ fastboot flashing lock
...
FAILED (remote: Set device locked! canceled)
finished. total time: 2.653s
Codys-MBP:~ namolas$ fastboot oem device-info
...
(bootloader) Verity mode: true
(bootloader) Device unlocked: true
(bootloader) Device critical unlocked: true
(bootloader) Charger screen enabled: true

Namolas said:
I don't know why, sorry. I just went through all the motions to make sure I didn't miss something but it all executes for me. Is that the only command not working for you??
Last login: Tue Feb 27 09:04:26 on ttys000
Codys-MBP:~ namolas$ fastboot devices
*****7/11****** fastboot
Codys-MBP:~ namolas$ fastboot getvar current-slot
current-slot: a
finished. total time: 0.001s
Codys-MBP:~ namolas$ fastboot --set-active=b
Setting current slot to 'b'...
OKAY [ 0.016s]
finished. total time: 0.016s
Codys-MBP:~ namolas$ fastboot flashing lock_critical
...
FAILED (remote: Set device locked! canceled)
finished. total time: 3.895s
Codys-MBP:~ namolas$ fastboot flashing lock
...
FAILED (remote: Set device locked! canceled)
finished. total time: 2.653s
Codys-MBP:~ namolas$ fastboot oem device-info
...
(bootloader) Verity mode: true
(bootloader) Device unlocked: true
(bootloader) Device critical unlocked: true
(bootloader) Charger screen enabled: true
Click to expand...
Click to collapse
yes thats the only command that not working for me

Orpalili said:
yes thats the only command that not working for me
Click to expand...
Click to collapse
I think I might know what the problem is.... You need to update your fastboot to the newest version.
https://developer.android.com/studio/releases/platform-tools.html

Namolas said:
I think I might know what the problem is.... You need to update your fastboot to the newest version.
https://developer.android.com/studio/releases/platform-tools.html
Click to expand...
Click to collapse
YESSSS!!!! IT WORKED!!
Thank you very much!!!!!!!!!!!!11:fingers-crossed::highfive::victory::laugh:

Thank you!
Namolas said:
I think this is the correct answer. You're going to want to flash-all the factory image to both slots before relocking the bootloader.
fastboot getvar current-slot *(take note of the current slot this command returns)*
flash-all
fastboot --set-active= *(=a or =b to change slot to the opposite the first command returned)*
flash-all
fastboot flashing lock_critical
fastboot flashing lock
fastboot oem device-info
Verify that the returned device info after the last command is;
(bootloader) Verity mode: true
(bootloader) Device unlocked: false
(bootloader) Device critical unlocked: false
(bootloader) Charger screen enabled: true
Now you are back to 100% stock with locked bootloaders. Reboot and set up your factory fresh device.
Click to expand...
Click to collapse
Hey man, just wanted to say thanks. You saved my ass!

thank you so much dude!
Namolas said:
I think this is the correct answer. You're going to want to flash-all the factory image to both slots before relocking the bootloader.
fastboot getvar current-slot *(take note of the current slot this command returns)*
flash-all
fastboot --set-active= *(=a or =b to change slot to the opposite the first command returned)*
flash-all
fastboot flashing lock_critical
fastboot flashing lock
fastboot oem device-info
Verify that the returned device info after the last command is;
(bootloader) Verity mode: true
(bootloader) Device unlocked: false
(bootloader) Device critical unlocked: false
(bootloader) Charger screen enabled: true
Now you are back to 100% stock with locked bootloaders. Reboot and set up your factory fresh device.
Click to expand...
Click to collapse

After I flash updates; I always boot up first. To make sure it actually does before rooting, relocking.
I've read to many horror stories and written a couple myself.

fastboot unlock_critical derp

If I remember correctly, on the P2XL, we were able to do both unlock and unlock_critical from fastboot. And them lock them both separately. However, since the last two clean flashes for me, I'm unable to lock or unlock both the partitions. I can only unlock or lock either one of them. When I try to do the other, it fails stating that the device is already unlocked! Another thing I noticed is that when I run sudo fastboot oem device-info, I get the below:
Code:
(bootloader) Verity mode: true
(bootloader) Device unlocked: true
(bootloader) Charger screen enabled: true
OKAY [ 0.000s]
Finished. Total time: 0.000s
If you notice,
Code:
(bootloader) Device critical unlocked: false/true
is completely missing!
Due to this, my device remains uncertified and always fails safety net.
Any idea how to fix this?

Locked bootloader

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 ?