Imei-check trinity unlock - P3600 Software Upgrading

here you go ... one paid solution available
http://www.imei-check.co.uk/m700unlock.php

decebal said:
here you go ... one paid solution available
http://www.imei-check.co.uk/m700unlock.php
Click to expand...
Click to collapse
But does that do a CID unlock?

Thats what I'm wondering too...

mmone3 said:
Thats what I'm wondering too...
Click to expand...
Click to collapse
yes. it will supercid your device

decebal said:
yes. it will supercid your device
Click to expand...
Click to collapse
So then I guess it is settled (if the unlock works). We pay 28 euros, unlock our phone and load the new Dopod WWE ROM with gps enabled...I think I'll wait on reports of how this ROM performs.

I bought the unlock but am to scared to try it yet.

I've unlocked my Italian P3600. Now i have HTCSSuperCIDHTCE
^__^
Rember to activete USB Adavanced Function on START--MENU--SETTINGS--CONNECTION - USB to PC

wishmaster82 said:
I've unlocked my Italian P3600. Now i have HTCSSuperCIDHTCE
^__^
Rember to activete USB Adavanced Function on START--MENU--SETTINGS--CONNECTION - USB to PC
Click to expand...
Click to collapse
u already paid the unlock?

kitcar said:
u already paid the unlock?
Click to expand...
Click to collapse
yes... 38 eur

thanks i wish for a free solution soon

YESSSSSSSSSSSSSSSSSS~!
Working!!!!!!!!!!!!!!!!!!!!
CID Unlocked!

Guybrush said:
thanks i wish for a free solution soon
Click to expand...
Click to collapse
Maybe it is possible to do the same approach as the Hermes and reverse engineer the Imei-check program. I already take a look to the program with a hex-editor but the program is encrypted as far as I saw.
Don't know what is the best approach to start creating a own unlock utility.
My programming skills are limited to php and c# etc.
Hopefully Pof can give us some hints where to start.
I am willing to pay for the unlock service if it helps to create a CID unlock solution.

Imei-check unlockers are packed with themida, they put very good protections to make it very hard to disassemble and run in debuggers. Usb sniffing is possible, but they also try to prevent this.
There are basically two things that you need before you can make a free unlocker:
1) radio patch: Trinity radio has the same structure as Hermes radio, and the patch is almost the same. There are several parts patched, all have fixed offset except the last one:
Code:
Decoded radio, patched bits (first column is the offset)
+0000c810 d4 c8 b1 00 d4 c8 b1 00 d4 c8 b1 00 00 00 00 00
^^ ^^ ^^ ^^ ^^ ^^
+0000c820 d4 c8 b1 00 00 00 00 00 00 00 00 00 00 00 00 00
^^ ^^
+00010810 d4 c8 b1 00 d4 c8 b1 00 d4 c8 b1 00 00 00 00 00
^^ ^^ ^^ ^^ ^^ ^^
+00010820 d4 c8 b1 00 00 00 00 00 00 00 00 00 00 00 00 00
^^ ^^
+00102ef0 04 00 00 1a 06 10 a0 e1 04 00 a0 e1 ef fb ff eb
^^ ^^
The last part is at a variable offset between 0x00159600 and 0x00159900, and not always the same bits are patched.
You can extract the patch by sniffing what the unlocker does over USB.
Be warned that there are some trinity radios with HTC radio bootloader V1.0108, and this process is probably not valid for this radios, you should better capture the unlocker process while unlocking a device with a V1.0107 radio bootloader.
2) flashing unsigned code: You need a way to flash unsigned code in radio to be able to make a free unlocker. In hermes this is possible in 1.04 bootloader with 'rtask' command to access the radio bootloader, that's why my unlocker only works with this bootloader version, but in Trinity you don't have a bootloader that allows this AFAIK.
In short, what imei-check does to be able to flash unsigned code is putting a modified SPL in RAM, disable MMU and jump from WinCE to the address where this SPL is stored. Reimplementing this is a hard work, I tried by modifying haret but still haven't been able to successfully start a working bootloader from it.
If you are not able to do this with your programming skillz, you'll have to extract the files from imei-check unlocker, this can also be done by sniffing the activesync connection that the unlocker does prior to jumping to the modified SPL, but you will not be able to provide a free solution with this files, because imei-check will claim intellectual property rights on them, so you should better not publish this even if you are able to extract it from the unlocker.
Hope this makes more or less clear what you have to do, as always feel free to ask if you are interested in learning more and something is unclear, but please review the hermes thread first, where this is explained in more detail.
Good luck!

Pof, anyone,
I tried the Imei-check unlock. Unfortunately it wouldn't work on my HTC P3600. The guys that run the service were great and gave me a refund. Apparently there is something strange about my phone/ROM. I decided to reload the "shipped" HTC Trinity ROM on the XDA Ftp site. When the bootloader screen came up it said MFG SPL 1.01...??? What is that? I thought it should be SPL 1.06 7 or 8??? In the end the ROM loaded normally so I suppose that I can wait for the official ROM update like others. I'm just wondering why my SPL is different.

Because imei-check unlocker puts this bootloader version on your device.

pof said:
Because imei-check unlocker puts this bootloader version on your device.
Click to expand...
Click to collapse
Is this a bad thing? Could it cause problems later? I guess it can be changed back again by another ROM update?
Thanks

SPL-1.01 ??
if that bootloader could be extracted, i think a free unlocker for trinity could be reality very very soon!

I have patched the 1.22.01.01 radio with HTC_BOOT 0107. When flashed on a Trinity device should give security Level=0 (SuperCID) and allow to SIM unlock it using any MSL code.
Download: GSM122patched_unsigned.zip​
The only problem is that you can't flash it because is not signed and the bootloader won't allow it, so you need to start researching how to flash unsigned code on Trinity. I don't have a Trinity and can't help you much on this.

hi i am a noob. what i have to do with the *.nb file?!

pof said:
I have patched the 1.22.01.01 radio with HTC_BOOT 0107. When flashed on a Trinity device should give security Level=0 (SuperCID) and allow to SIM unlock it using any MSL code.
Download: GSM122patched_unsigned.zip​The only problem is that you can't flash it because is not signed and the bootloader won't allow it, so you need to start researching how to flash unsigned code on Trinity. I don't have a Trinity and can't help you much on this.
Click to expand...
Click to collapse
Since I have bootloader MFG 1.01 on my Trinity do you think this bootloader would allow me to run the file?

Related

Checking simlock status?

Is there a way to check the simlock status on a kaiser?
All I've got in the whole house is t-mobile sims and I'm trying to sell it but I don't know if it's locked or not, is there a way to check?
Thanks,
- Anthony
trinode said:
Is there a way to check the simlock status on a kaiser?
All I've got in the whole house is t-mobile sims and I'm trying to sell it but I don't know if it's locked or not, is there a way to check?
Thanks,
- Anthony
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=2590275&postcount=2
Ta
Dave
thanks for the link, but I'm getting no response from that app at all
click send and nothing happens (obviously I put a command in first)
my bad, [email protected] not [email protected] should be at the start of the command
This is what I get:-
[email protected]
0
[email protected]?40
00 0
That unlocked?
trinode said:
my bad, [email protected] not [email protected] should be at the start of the command
This is what I get:-
[email protected]
0
[email protected]?40
00 0
That unlocked?
Click to expand...
Click to collapse
Yes that is unlocked, I have updated the link I posted with upper case
Dave

[Dev] Enable fastboot/unbrick

First, thanks to Bin4ry and NielDK for initial fix. This is the sequel if their work in another thread.
The fix will be considered complete when it'll be able to revive all phones: non-booting and radio-bricked, and enables fastboot on simlocked phones!
===
I think that SIM-lock is not signed anymore after bootloader unlock. If it was, then phone wouldn't boot even after flashing simlock.ta, because SE phones with bad/unsigned/damaged SIM-lock don't boot.
simlock.ta converted to ASCII:
Code:
���������������������
���
������������������������
����������������������4OP_ID="108";OP_NAME="Customized";CDA_NR="1241-4091";��� �00101-*���������������
������������������������
������������������������
������������������������
���������������������������������������������������������
Operator: 001-01-* meaning it's simlocked.
SIM-locked 7DA unit:
Code:
d—FÀB„›ü‡ÞydØ¥¾‡q�
���
–ƒµâMMCß!2P€®> Ö÷êBY(wêÿÕÄ«�l³V)v*‡f¨Ê˜¶ü¶½l©���
ÛðÔŠ�v–-|›SöíS«Ë±ë‘ ׌€Ò/pÀ»®uKؘ*[Eá c}ëÈø%£8�DOP_ID="162";OP_NAME="Rogers";CDA_NR="1247-6276";ROOTING_ALLOWED="0";�CSERVERID="bmcsecs01";AUTHCERT="UNKNOWN";TIMESTAMP="110412 01:30:10" �00101-*������302720-*�����������
—êFk#Üä¯y'?¶…ª˜ (êÚ÷’(xø¶âƒM¥Â*ßÙõ�WÝÈØ*„���
‘2=Ôs#8÷kÚŸœ"í IÙèhO®{à’¥ª|B΃iÃǹֶ
E„B[=—b���
t¼²föb±8§®@IjÚœ�\ ŽDR¦Sp"<¢ç¯‚¶í̽Ú)ïhâ+xÕ_‰���
`’ÇkùÁ|v�yìòYç_6Q qL¶`* Ý0©ª-©`\wŒPL(@™,ήjæþþ”*�6636209799586744������������������������ È‚V"s7Ïæw93æ=àFz¿~9Í¡®gÙÄ.??
Note the ROOTING_ALLOWED=0.
BL unlocked and working:
Code:
wñMpjEZ÷îlBÀ3øÛ^�
���
�¤*‘ƒ¡<i_{<Ž(B-Kÿà (?Dð/;©c$™ùÀ
˯¤uœ º;`”’`o²¨éG���
¤m ¶.úÑ
!°_Zª|ã_ »go£°TçðgDivT0½KH�RÍíý‡³e‚˜ãÿ�‘OP_ID="435";OP_NAME="Customized";CDA_NR="1247-6199";ROOTING_ALLOWED="1";;RCK_H="654E9886B5ECE33DDB814F5C7DC2D502FC07FBD1A872A013748964FC5D8281ED"CSERVERID="bmcsecs01";AUTHCERT="UNKNOWN";TIMESTAMP="110325 08:24:03"���
ÒÞ,€†ÌÓtda”qæmºØTrà ¦ôää¥ÌÆ-çý¤àŸ{¦l)N5ÑFÓ°{R“ùSÓ���
“m
F‡¡²ŽD¹$ìw‚v³µÑ´æ @ãKˆx¾®7à¡¥‚ûknóÚPÎ?í˜ø/“É`N8���
ºDJ6¿´”…¬yVfWÕ³d ‡*Ñ@ãõÝÊØ^ãPGsŸÜ½€nD_ŽF°€Ù¯|���
×|`ˆß9‰à¼ãö*e|°eM½ ”0cœêՍúlªÛž«3Z¼3€ùy*™rôsþðÑE+����������������˜Ä.9ÿY±º'ƒJÙ?" ƒä??
simlock.ta doesn't say is rooting allowed or not, so BL won't allow it.
Click to expand...
Click to collapse
TA Misc, 8FD from bricked, fastboot off, no network:
ta = 000008FD 00 00 00 00 05 00 00 00 03 00 00 00 08 00 00 00
TA Misc, 8FD from BL unlocked and BL locked device fully working:
ta = 000008FD 00 00 00 00 05 00 00 00 03 00 00 00 08 00 00 00
TA Misc, 8FD from non-booting phone:
ta = 000008FD 00
TA Misc, 8FD on SIM-locked phone:
ta = 000008FD 00
TA Misc, FreeXperia Team's fix:
000008FD 00 00
That's strange, on factory-fastboot-capable phones 8FD is same though one has got fastboot, and other not, and bricked fb capable and SIM-locked has got the same 8FD.
Looks like there is something in 8FD, but fastboot capability is somewhere else in TA Misc (partition 02).
FYI, TA Misc is where we should look for. 7DA is simlock unit and it might be worth investigating.
Click to expand...
Click to collapse
will this also mean you can relock your bootloader?
Why would you want to do that?
If my initial theory works, then it's possible but only if you made TA backup before unlocking bootloader.
No idea why any one would not want custom roms, with a easy way of loading them on with a new boot-loader,
guessing in case it has to go back for some kind of repair that will require the warranty to be back to 100%, who knows
All we can do now is wait till Omnius will support TA backup/restore.
But I can't do anything until i find SIM-free, bootloader locked phone.
blagus said:
All we can do now is wait till Omnius will support TA backup/restore.
But I can't do anything until i find SIM-free, bootloader locked phone.
Click to expand...
Click to collapse
I have a sim locked phone, so I can help with steps 4-6, if you haven't got anyone in board yet, once Omnius supports TA b/r for the arc. :-D
Sent from my LT15i using XDA App
ponggoloids said:
I have a sim locked phone, so I can help with steps 4-6, if you haven't got anyone in board yet, once Omnius supports TA b/r for the arc. :-D
Sent from my LT15i using XDA App
Click to expand...
Click to collapse
Thanks! Now looking for someone with SIM-free, fastboot available and bootloader locked.
blagus said:
Thanks! Now looking for someone with SIM-free, fastboot available and bootloader locked.
Click to expand...
Click to collapse
I have sim free, bootloader locked phone..... and i can help you but do i need to unlock the bootloader in this process?
as you see in step two you will need to unlock your bootloader after the first three backups. As for why i want to be able to lock the bootloader its just in case ill ever need the drm stuff or things like that. I just think its nice to have the possibility if ill ever need it. BTW when you ask for sim free do you mean a phone that doesent have actual simcard in it? Cause i have a arc bought on a contract, and it shows up in fastboot but it does use a sim card
mineralvann said:
as you see in step two you will need to unlock your bootloader after the first three backups. As for why i want to be able to lock the bootloader its just in case ill ever need the drm stuff or things like that. I just think its nice to have the possibility if ill ever need it. BTW when you ask for sim free do you mean a phone that doesent have actual simcard in it? Cause i have a arc bought on a contract, and it shows up in fastboot but it does use a sim card
Click to expand...
Click to collapse
simfree means a phone which is not locked to any carrier like vodafone or T-Mobile and can be used with any sim
oh i thought the phone had to be sim unlocked for fastboot to be enabled
chowdarygm said:
I have sim free, bootloader locked phone..... and i can help you but do i need to unlock the bootloader in this process?
Click to expand...
Click to collapse
Yes, you will. I hope that this is not the problem for you, and at the same time I can test if writing original TA before unlocking can relock bootloader
blagus said:
Why would you want to do that?
If my initial theory works, then it's possible but only if you made TA backup before unlocking bootloader.
Click to expand...
Click to collapse
One word: Warranty.
Warranty will be valid as long as you flash original Arc firmware before sending it to the repair.
If you're not willing to unlock it and nothing's gonna change your mind, say so. But, on the other side, this way you can test if bootloader can be relocked or not in TA - if it enables fastboot on locked devices, I'm sure this can relock bootloader too
Hi,
Sim-free Arc with locked bootloader here. Don't have the time to try atm, however, but I will see if I find some free moment the next days.
Phone can be set back into factory default by using the "repair" function in SE PC Companion?
Kind regards,
cherryfish
cherryfish said:
Hi,
Sim-free Arc with locked bootloader here. Don't have the time to try atm, however, but I will see if I find some free moment the next days.
Phone can be set back into factory default by using the "repair" function in SE PC Companion?
Kind regards,
cherryfish
Click to expand...
Click to collapse
If you plan to have any custom ROMs you'll have to unlock bootloader anyways... and don't worry about the time, Omnius doesn't support TA backup/write yet...
And at the same time we can check if restoring original TA will relock bootloader (that's the root of my need for TA backups).
And unlocked bootloader won't void warranty by itself - SE clearly states that additional repair charges may occur due to modified phone's firmware, not unlocked bootloader.
PM me if you're in, so I can provide you with detailed info.
My Arc is locked. It provided from Movistar spain. I have generic global.
Tell me I can help you.
SIM free, so far not unlocked. I have tomorrow and Friday off work so willing to help. If you'e had no joy let me know, willing to help
what would homer do? said:
SIM free, so far unlocked. I have tomorrow and Friday off work so willing to help. If you'e had no joy let me know, willing to help
Click to expand...
Click to collapse
If you have unlocked bootloader then it's not very useful...
blagus said:
If you have unlocked bootloader then it's not very useful...
Click to expand...
Click to collapse
My Arc is Locked.

Unlock Program - Bootloader Hack: 16 chances to unlock relock

All Thanks to @Derjan23
I used Code from his post here
thanks to @OopsWare for his analysis of this code here
Disclaimer:
I am not responsible for any damage at your device!
You're running this programm on your own risk!
Here's unlock Program it does the following
1-try to read odm_reserved
2-check if your bootloader unlocked or locked
3-calculate the most effective string that you have to echo to reverse bootloader state(it will relock if your Bootloader is unlocked - unlock if your Bootloader is locked
4-you can copy echo command and use it after su root in terminal
DONT BLOWN ALL FUSES WITH echo /data/local/tmp/odm_reserved >/sys/firmware/fuse/odm_reserved
The unlock check use 8 bytes of fuses which are Stored at sys/firmware/fuse/odm_reserved in the 1st 16 hexadecimal digits
I will use the value most unlocked devices have to explain 00000040 000000c0
those 8 bytes divided into 2 groups:
1- red group is unlockable or no unlockable
2- blue group for locked unlocked
each hexadecimal digit represented in 4bits the unlock check needed only 2bits from each group - 1st check iteration is made on digit 4 and digit c
4 = 0100 binary
c=1100 binary
1st group: unlockable is 01 non-unlockable is 10 - 00 stops checking - 11 check next 2 bits
2nd group: unlocked is 11 any other value is locked
here is the order it iterates through those bytes
00000040 000000c0
1-40 c0
2-00 00
3-00 00
4-00 00
the order inside each byte
40 = 01000000
c0 = 11000000
1-01 11
2-00 00
3-00 00
4-00 00
Conclusion : you have 16 chance to unlock relock the method used is unlocking (thanks to d in odm word) but blows all your chances
to unlock you need 01 in 1st group 11 in 2nd group
if 1st group is 10 like in 80 10000000 your only choice to unlock is to flash these fuses and use next ones so you should make them 11010000 which equal d0 and you need 11 in corresponding bits in 2nd group
00110000 30
so in your rooted JB device use Terminal app
1- su
2- echo 40000000c0 >/sys/firmware/fuse/odm_reserved
here's the 4 chances in 1st byte in order
1- unlock 40000000c0 relock c000000000
2- unlock d000000030 relock f000000000
3- unlock f40000000c relock fc00000000
4- unlock fd00000003 relock ff00000000
thats in 1st byte of our 4 bytes 2nd will be unlock 40ff0000c000 relock c0ff00000000
1st byte in 1st group will be ff and 1st byte in 2nd group it doesn't matter so i used 00 and it'll continues like this
be aware that any binary 1s in odm reserved can't be 0 again so the result of echo command = digits you send logical OR digits in the file
why would anyone want to relock the bootloader?
Also does this mean that users who did echo /data/local/tmp/odm_reserved have a permanently unlocked bootloader? that ant be relocked?
DavidXanatos said:
why would anyone want to relock the bootloader?
Also does this mean that users who did echo /data/local/tmp/odm_reserved have a permanently unlocked bootloader? that ant be relocked?
Click to expand...
Click to collapse
they have a chance to relock without unlocking again @exFAT did it - if bootloader itself check this fuse then unlock methods(adb and fastboot) only sets this flag so bootloader allow any boot images (unlocked) or specific ones (locked)and this flag is dangerous because when it becomes all ones (16 f) you will stayed with locked device forever
if unlocking methods change bootloader itself then unlock through hack only shouldn't be enough and unlock methods should be used - and in that case relock should have no effect only its shown like this in hidden menu
hmm...
here: http://forum.xda-developers.com/showpost.php?p=40635481&postcount=8
he wrote that despite of having blown all fuses he can still but CWM and a custom ROM.
Just a question...?
After reading this i've just been thinking...
Would flashing the firmware through LG Flash Tool affect the Bootloader lock state?
Has anyone followed the ODM Reserved Mod and re-flashed an LG Firmware?
If so does the Bootloader Unlock remain? Is it permanent? :good:
i used the ODM hack and flashed back to LG jelly bean with LG Mobile Flash Tool. Bootloader is still unlocked Flashed CWM & CM.10.1 over my 232.10 Hutchison branding! Now my baseband Version is from my Provider instead of the EUR one.
sorry about my english ^^
i think that using LG Flash Tool to rollback to ICS will affect that.
reas0n said:
i think that using LG Flash Tool to rollback to ICS will affect that.
Click to expand...
Click to collapse
I don't think soo... when you go back to JB, bootloader still unlocked.
RuedasLocas said:
I don't think soo... when you go back to JB, bootloader still unlocked.
Click to expand...
Click to collapse
I have tried it my self using the very first thread about unlocking the bootloader with writing fuse in temp folder. Went back to ICS with LG Flash Tool and afterthat I updated to stock jelly bean and rooted it is still unlocked. But I really don't know if it was locked in ICS? any ways I on CM10.1 and its TOP.
I also think it's like @RuedasLocas wrote.
GizModio said:
After reading this i've just been thinking...
Would flashing the firmware through LG Flash Tool affect the Bootloader lock state?
Has anyone followed the ODM Reserved Mod and re-flashed an LG Firmware?
If so does the Bootloader Unlock remain? Is it permanent? :good:
Click to expand...
Click to collapse
Erazor84 said:
i used the ODM hack and flashed back to LG jelly bean with LG Mobile Flash Tool. Bootloader is still unlocked Flashed CWM & CM.10.1 over my 232.10 Hutchison branding! Now my baseband Version is from my Provider instead of the EUR one.
sorry about my english ^^
Click to expand...
Click to collapse
lock state is put in fuses being read in odm_reserved file - Jellybean Rom allowed write them - I tried same hack on rooted ICS and it was not working
bootloader official unlock procedure does change odm_reserved from 4000000000 to 40000000c0
they needed to drop some of their security to allow us to write these fuses through adb to unlock our bootloader
so any flashing doesn't affect it but hack method will do
future81 said:
lock state is put in fuses being read in odm_reserved file - Jellybean Rom allowed write them - I tried same hack on rooted ICS and it was not working
bootloader official unlock procedure does change odm_reserved from 4000000000 to 40000000c0
they needed to drop some of their security to allow us to write these fuses through adb to unlock our bootloader
so any flashing doesn't affect it but hack method will do
Click to expand...
Click to collapse
So both the "ODM_Reserved Mod" and the official Boot-loader unlock do exactly the same?
They both change the code?
GizModio said:
So both the "ODM_Reserved Mod" and the official Boot-loader unlock do exactly the same?
They both change the code?
Click to expand...
Click to collapse
I think so maybe official bootloader unlock do other things additional to that but i'm convinced the bootloader itself kept unchanged it's only was checking these fuses even on ICS - that can be proved if someone with unlocked bootloader flashed ICS and tried flashing cwm recovery after rooting it and rebooted into it without security errors
I've made small program to unlock relock
OP updated
Hmm...
Sent from my LG-P880 using Tapatalk 2
exFAT said:
Hmm...
Sent from my LG-P880 using Tapatalk 2
Click to expand...
Click to collapse
so did you flash stock Rom with lg methods and then laufersteppenwolf kernel?
if you didn't use lg flash tools you shouldn't risk try it
here is unlocking process log
D/UnlockService( 625): sim state:0 mcc:4095 mnc:255
D/UnlockService( 625): readSysfs_string() : 0x000000000000000000000000000000000000000000000000 00000040000000c0
D/UnlockService( 625): setUnlockAvailBit strRead : 00000000000000000000000000000000000000000000000000 000040000000c0
D/UnlockService( 625): setUnlockAvailBit reversed : 40000000
D/UnlockService( 625): setUnlockAvailBit nProcessingNumber : 40000000
D/UnlockService( 625): setUnlockAvailBit nResetMaskingBits : c0000000
D/UnlockService( 625): setUnlockAvailBit nNotAvailMaskingBits : 80000000
D/UnlockService( 625): setUnlockAvailBit nAvailMaskingBits : 40000000
Click to expand...
Click to collapse
and this is hidden menu unlock check log
BootloaderUnlock_Test( 2641): readSysfs_string() : 0x000000000000000000000000000000000000000000000000 0000004000000000
BootloaderUnlock_Test( 2641): bootloader_unlock_flag_read strRead : 00000000000000000000000000000000000000000000000000 00004000000000
BootloaderUnlock_Test( 2641): bootloader_unlock_flag_read reversed : 40000000
BootloaderUnlock_Test( 2641): bootloader_unlock_flag_read reversed : 00000000
BootloaderUnlock_Test( 2641): nProcessingNumber_Avail : 40000000
BootloaderUnlock_Test( 2641): nProcessingNumber_Unlock : 0
BootloaderUnlock_Test( 2641): bootloader_unlock_flag_read nResetMaskingBits : c0000000
BootloaderUnlock_Test( 2641): bootloader_unlock_flag_read nNotAvailMaskingBits : 80000000
BootloaderUnlock_Test( 2641): bootloader_unlock_flag_read nAvailMaskingBits : 40000000
Click to expand...
Click to collapse
so unlock bootloader typically reverse hidden menu check - it requires avail masking bits (first 4 or d not 8 or e) and set corresponding bits to 11 (c or f)
even the rest of the log before the odm reversed part (readsysfs) looks like a checking with operator if it allows bootloader unlocking or not then the unlocking itself is made by this flag
and i'm not sure whats the difference between really locked (4 with non 11 in corresponding bits or 8) and between that all f situation - it's stopped because it checked all fuses and didn't find required 4 and didn't stopped with 8
future81 said:
so did you flash stock Rom with lg methods and then laufersteppenwolf kernel?
if you didn't use lg flash tools you shouldn't risk try it
here is unlocking process log
and this is hidden menu unlock check log
so unlock bootloader typically reverse hidden menu check - it requires avail masking bits (first 4 or d not 8 or e) and set corresponding bits to 11 (c or f)
even the rest of the log before the odm reversed part (readsysfs) looks like a checking with operator if it allows bootloader unlocking or not then the unlocking itself is made by this flag
and i'm not sure whats the difference between really locked (4 with non 11 in corresponding bits or 8) and between that all f situation - it's stopped because it checked all fuses and didn't find required 4 and didn't stopped with 8
Click to expand...
Click to collapse
I was on Kholk's kernel and stock v20b HKG when I relocked (apparently). I flashed Werewolf kernel manually via terminal emulator, rebooted fine.
Sent from my LG-P880 using Tapatalk 2
does the fuse remain even when you move away from STOCK ROM?
jonnya70 said:
does the fuse remain even when you move away from STOCK ROM?
Click to expand...
Click to collapse
yes its hardware bit designed to be written once
I just tried your App and it Worked very Good.
The Hidden Menu Shows Unlocked in my Phone and I even not Restart the Phone.
Now I just have to get CWM to confim everything it's ok but I'm sure it will work.

Downgrade 8.0.0.157 C433 to a DC Unlocker version ?

Hello my friends,
I had an iPhone before so it might be very complicated for me.
As I understand, the bootloader code works only with a specific firmware (I have a mate 10 Pro).
My actual version is 8.0.0.157 C432 (newest).
As I read they updated the xloader to 02 ? On which version can I downgrade to use DC unlocker ? Tried it yesterday but I get a error message that my device is not supported (error code 375).
Or are there other solutions to unlock my boot loader ? Paid already 4 euro for the DC unlocker account.
You can not downgrade a 02 xloader based firmware to a 01 xloader based firmware. Dont try it. It will hard-brick your phone and there is no way to unbrick it. As your bootloader is still locked, you can not use any no-check recovery method to downgrade, but what you can do is get bootloader unlock code by using dc huawei bootloader code app. You have to pay 25€ as I remember and they get your bootloader unlock code using your IMEI.

Unlock Bootloader Honor 4C

Hello.
Help me get the code to unlock the bootloader on the Honor 4C device.
Serial Number: A8K4C15724008701
IMEI: 866778029027251
Product ID: 50763430
Model: HUAWEI Honor 4C (CHM-U01)
Thankful
Hey, check this thread, you can unlock your bootloader using this method. Root access is needed. No internet connection required, easy peasy!
Need help on how to unlock bootloader

Categories

Resources