[MOD] YU Yureka Unlocker: Reset Unlock & Tamper Bit - YU Yureka Android Development

Most of the concept & content of this thread is inspired by this thread, so a huge thanks to @Mnt-XDA.
INTRO / CONCEPT
Most of us know that we can flash custom roms or can root device only after UNLOCKING the bootloader from fastboot mode.
If you relock your bootloader, you will need to do a full backup-and-restore whenever you decide to unlock it again.
This mod will allow you to unlock the bootloader without wiping the userdata as oppose to "fastboot -i 0x1ebf oem unlock" command.
Titokhan said:
Note:
Many users should have trouble to UNLOCK their device for the FIRST TIME by using this method. Let me clarify few things for this mod.
The main purpose of this method is not UNLOCK Bootloader without wiping data. It's main purpose is to reset tamper bit, which can not be done by any other way.
UNLOCK Bootloader without wiping data -- is another outcome of this MOD.
If you have not unlocked your device before (at least for 1 time) by using command "fastboot -i 0x1ebf oem unlock", then this method might not work for you.
In case your device is locked and you want to install this mod from custom recovery like TWRP,
it will be possible only if, you can boot temporarily using command: fastboot -i 0x1ebf boot <custom_recovery.img>
If this command failed, you will not be able to run the mod and hence device will not be unlocked without wiping data. A stock YU Yureka doesn't support this, AFAIK.
In which condition the device can be booted to custom recovery by using command: fastboot -i 0x1ebf boot <custom_recovery.img>, is still not very clear. From my experiments, it requires only unlock bit to be true.
Before running the command , check your device status "fastboot -i 0x1ebf oem device-info"
and report your error with the following points:
1) Did you unlock your device before by any means (or by fastboot -i 0x1ebf oem unlock) ?
2) What is the recovery already installed in your device?
3) What is the status of your device: "fastboot -i 0x1ebf oem device-info"?
4) What error message you got when tried to run command: fastboot -i 0x1ebf boot <custom_recovery.img>?
5) Steps you tried.
There are 4 possibilities of the the value set of the 2 bits (unlock bit & tamper bit)
1) Unlock Bit - FALSE , Tamper Bit - FALSE
2) Unlock Bit - FALSE , Tamper Bit - TRUE
3) Unlock Bit - TRUE, Tamper Bit - FALSE
4) Unlock Bit - TRUE, Tamper Bit - TRUE
Kindly report your issues as I mentioned above.
Thanks
Click to expand...
Click to collapse
There are generally 2 bits present on some partition of the phone for keeping track of unlocking.
1) Unlock bit
2) Tamper bit
Both bits are initially FALSE. We can unlock bootloader by using command:
Code:
fastboot -i 0x1ebf oem unlock
and can see the device information by
Code:
fastboot -i 0x1ebf oem device-info
like:
Once you unlock, both bits will come TRUE. This mod will write the 2 bits in aboot partition and can reset
both bits (TOGGLE basically) without factory reset as opposed to "fastboot -i 0x1ebf oem unlock".
So for YU Yureka:
Code:
Partition - aboot (mmcblk0p4)
Unlock Bit Position - 0x000FFE10 Hex - (1048080) Decimal
Tamper Bit Position - 0x000FFE14 Hex - (1048084) Decimal
FYI, there is anoher partition named "abootbak" (mmcblk0p5) which is holding the backup of the original contents of "aboot", but there is no visible effects of it.
Unlock bit:
Tamper bit:
CREDIT
Credit goes to:
@osm0sis for the original script for Nexus devices.
@Mnt-XDA & @Polarfuchs for poting it to OnePlus One.
@segv11 for making BootUnlocker; I have already requested him to add support for Yureka.
WARNING
Since this mod writes on aboot (bootloader) partition to reset the 2 flags, it may brick your phone. I have tested the procedure thoroughly but still I'm requesting developers to test it first, then give feedback here. After that any normal user can use it. I'm not be responsible for any damage or bricking of your phone. Proceed at your own risk.
DOWNLOAD
Code:
File: YU_Yureka_aboot_(mmcblk0p4).7z
CRC-32: 9a8d4525
MD4: cf91807938ca679a3038161893f97c89
MD5: c60aa4a7477e2e0c18269ecede431339
SHA-1: acd5de06cb53ead6df5efebd4dfed3f9f7e4ac2a
https://mega.co.nz/#!Z1QkSYgC!mMBDFoMacVic7ubN6JNPaYD4xpxHQ9UsvgZ6RLlf1cE
https://drive.google.com/file/d/0B9zZIJPXbMsuWUV2TVpOcm81RmM/view?usp=sharing
Inside the 7z archive, there are 4 raw img files. Naming convention is UXTY.img:
U => Unlock bit
X => Status of Unlock bit, T(rue) or F(alse)
T => Tamper bit
Y => Status of Tamper bit, T(rue) or F(alse)
Use your desired method to restore e.g using dd from ADB shell or Terminal or using this by famous developer @wanam. This procedure needs root permission.
You need to restore them to aboot (mmcblk0p4) partition; otherwise your device can be bricked!
Recovery flashable ZIP is coming soon, which can be installed from any 3rd party recovery like CWM / TWRP.
THANKS
Please post feedback; thanks again!

---

This belongs in Development?

---

Reserved for future use.

---

sufoalmighty said:
This belongs in Development?
Click to expand...
Click to collapse
Looks appropriate for me; Mods will decide.

---

Titokhan said:
Looks appropriate for me; Mods will decide.
Click to expand...
Click to collapse
You is right btw are you gonna post it in YU forums?

---

@sufoalmighty
https://forums.yuplaygod.com/threads/mod-yu-yureka-unlocker-reset-unlock-tamper-bit.2361/
:highfive:

---

This is interesting; I have tested two stock YU Yureka - one from 22nd & one from 29th sales. Both show:
Code:
Device tampered: [COLOR="Red"]true[/COLOR]
Device unlocked: false
Any possible explanation?

---

Titokhan said:
This is interesting; I have tested two stock YU Yureka - one from 22nd & one from 29th sales. Both show:
Code:
Device tampered: [COLOR="Red"]true[/COLOR]
Device unlocked: false
Any possible explanation?
Click to expand...
Click to collapse
There's a possibility that my Yureka is in this group. I actually didn't check my oem info before trying unlocking the bootloader. But when I tried to unlock my device for the first time, it failed. Then I checked my oem device-info and it showed as
Device tampered: true
Device unlocked: false
Can anyone shed some light on this issue?

---

@chandujram
Well, actually every Yureka & Yureka Plus carry the same flag. The official CPBs for restoration to stock also contain the same which indicates there's a quality checking flaw while publishing the firmware image; though its harmless.

---

@Titokhan Oh okay

---

problem
Titokhan said:
Most of the concept & content of this thread is inspired by this thread, so a huge thanks to @Mnt-XDA.
INTRO / CONCEPT
Most of us know that we can flash custom roms or can root device only after UNLOCKING the bootloader from fastboot mode.
If you relock your bootloader, you will need to do a full backup-and-restore whenever you decide to unlock it again.
This mod will allow you to unlock the bootloader without wiping the userdata as oppose to "fastboot -i 0x1ebf oem unlock" command.
There are generally 2 bits present on some partition of the phone for keeping track of unlocking.
1) Unlock bit
2) Tamper bit
Both bits are initially FALSE. We can unlock bootloader by using command:
Code:
fastboot -i 0x1ebf oem unlock
and can see the device information by
Code:
fastboot -i 0x1ebf oem device-info
like:
Once you unlock, both bits will come TRUE. This mod will write the 2 bits in aboot partition and can reset
both bits (TOGGLE basically) without factory reset as opposed to "fastboot -i 0x1ebf oem unlock".
So for YU Yureka:
Code:
Partition - aboot (mmcblk0p4)
Unlock Bit Position - 0x000FFE10 Hex - (1048080) Decimal
Tamper Bit Position - 0x000FFE14 Hex - (1048084) Decimal
FYI, there is anoher partition named "abootbak" (mmcblk0p5) which is holding the backup of the original contents of "aboot", but there is no visible effects of it.
Unlock bit:
Tamper bit:
CREDIT
Credit goes to:
@osm0sis for the original script for Nexus devices.
@Mnt-XDA & @Polarfuchs for poting it to OnePlus One.
@segv11 for making BootUnlocker; I have already requested him to add support for Yureka.
WARNING
Since this mod writes on aboot (bootloader) partition to reset the 2 flags, it may brick your phone. I have tested the procedure thoroughly but still I'm requesting developers to test it first, then give feedback here. After that any normal user can use it. I'm not be responsible for any damage or bricking of your phone. Proceed at your own risk.
DOWNLOAD
Code:
File: YU_Yureka_aboot_(mmcblk0p4).7z
CRC-32: 9a8d4525
MD4: cf91807938ca679a3038161893f97c89
MD5: c60aa4a7477e2e0c18269ecede431339
SHA-1: acd5de06cb53ead6df5efebd4dfed3f9f7e4ac2a
https://mega.co.nz/#!Z1QkSYgC!mMBDFoMacVic7ubN6JNPaYD4xpxHQ9UsvgZ6RLlf1cE
https://drive.google.com/file/d/0B9zZIJPXbMsuWUV2TVpOcm81RmM/view?usp=sharing
Inside the 7z archive, there are 4 raw img files. Naming convention is UXTY.img:
U => Unlock bit
X => Status of Unlock bit, T(rue) or F(alse)
T => Tamper bit
Y => Status of Tamper bit, T(rue) or F(alse)
Use your desired method to restore e.g using dd from ADB shell or Terminal or using this by famous developer @wanam. This procedure needs root permission.
You need to restore them to aboot (mmcblk0p4) partition; otherwise your device can be bricked!
Recovery flashable ZIP is coming soon, which can be installed from any 3rd party recovery like CWM / TWRP.
THANKS
Please post feedback; thanks again!
Click to expand...
Click to collapse
how to do this if i am unrooted also ,and unable to unlock bootloader due to response oem unlock cancel , what to do can i reinstall my bootloader hwat to do please help

---

@sudeep22
1. Please don't quote the whole post.
2. You can't do it while being unrooted.
3. What's the actual error while trying to unlock the bootloader?

---

Titokhan said:
@sudeep22
1. Please don't quote the whole post.
2. You can't do it while being unrooted.
3. What's the actual error while trying to unlock the bootloader?
Click to expand...
Click to collapse
thanks i am not too much aware about quoting
actualy when i was on stock 5.0.2 i unlocked my bootloader and get rooted for experiment, then i remove my root and relock bootloader.
now i am on 5.1.1 due to bad perfomance of this stock rom i am again trying to again unlock bootloader for flashing custom rom
but when in fastboot mode i give command to unlock bootloader it asks to press volume button , but after pressing button nothing happens presses again and again
after as time out massage command oem unlock cancelled

---

@sudeep22
1. Which device are you using, Yureka or Yureka Plus?
2. Are the volume rockers working?

---

i am using yureka
yes volume key normal condtion working normally after reading this thread i thought may problem of those two bits
which are for my devices
device tempred- true
device unlocked-flase

---

Sir I type OEM unlock it doesn't show plus volume up or down. It show ersa datauser and wait 20 sec. Then it go and can't ersa. When type OEM lock it show OK. How to solve it ?

---

sudeep22 said:
i am using yureka
yes volume key normal condtion working normally after reading this thread i thought may problem of those two bits
which are for my devices
device tempred- true
device unlocked-flase
Click to expand...
Click to collapse
Pls tell how to unlock OEM in this case
Device tampered : true
Device unlocked: false

---

@sudeep22 @garrylok
Please do a complete re-flash of Lollipop firmware using YGDP, then manually update to latest COS 12.1 build.

---

Titokhan said:
@sudeep22 @garrylok
Please do a complete re-flash of Lollipop firmware using YGDP, then manually update to latest COS 12.1 build.
Click to expand...
Click to collapse
Ydgp can't flash I try few CPB file. After start flash it fail. I also miflash and receive hello fail

---

@garrylok
Please send me the logs generated by YGDP. And describe more elaborately, what did you do with the device?