Reset Warranty Bit on Android One Devices

[awaaas]

So, after searching and asking to no avail, I decided to test it myself, and it works!

After you unlocks your android one device, your warranty bit is set to no, even if you lock it again afterwards.
This may or may not affects your real warranty service. But better safe than sorry.

This will also locks your bootloader once again.

Download
http://goo.gl/CPTQOf

How to use
1. Download file seccfg.img above
2. Download TWRP or CWM or PhilZ, if you don't already have it
3. Enter fastboot mode
4. Boot custom recovery

fastboot boot <path/to/custom/recovery/file.img>

5. After entering custom recovery, push my seccfg.img to internal memory:

adb push seccfg.img /sdcard/

6. (Optional) Do a backup to your original seccfg before overwriting it:

adb shell dd if=/dev/block/platform/mtk-msdc.0/by-name/seccfg of=/sdcard/seccfg_original.img

7. Overwrite the seccfg:

adb shell dd if=/sdcard/seccfg.img of=/dev/block/platform/mtk-msdc.0/by-name/seccfg

8. And you are done.

To check wether your warranty bit is back or not, back to fastboot and type this command:

fastboot getvar all

Alternative method using fastboot
After downloading, enter fastboot mode, and flash the file from there by using:

fastboot flash seccfg <path/to/seccfg.img>

and you're done.

Yet another alternative method using custom recovery
Just flash attached flashable zip via custom recovery, and you are done.

 

[Devam03]

So, after searching and asking to no avail, I decided to test it myself, and it works!

After you unlocks your android one device, your warranty bit is set to no, even if you lock it again afterwards.
This may or may not affects your real warranty service. But better safe than sorry.

Download
http://goo.gl/CPTQOf

How to use
1. Download file seccfg.img above
2. Download TWRP or CWM or PhilZ, if you don't already have it
3. Enter fastboot mode
4. Boot custom recovery

fastboot boot <path/to/custom/recovery/file.img>

5. After entering custom recovery, push my seccfg.img to internal memory:

adb push seccfg.img /sdcard/

6. (Optional) Do a backup to your original seccfg before overwriting it:

adb shell dd if=/dev/block/platform/mtk-msdc.0/by-name/seccfg of=/sdcard/seccfg_original.img

7. Overwrite the seccfg:

adb shell dd if=/sdcard/seccfg.img of=/dev/block/platform/mtk-msdc.0/by-name/seccfg

8. And you are done.

To check wether your warranty bit is back or not, back to fastboot and type this command:

fastboot getvar all

Yea It Works!

 

[rahuldasari12]

help

can any one help me how to do this process..icant understand how to proceed

 

[Saurabh K]

can any one help me how to do this process..icant understand how to proceed

I thiink its not that important to get the warranty back (at least on Indian variants) as flashing the stock ROM via SP flash tools of fastboot does the job. Interesting procedure by the way.......

 

[awaaas]

can any one help me how to do this process..icant understand how to proceed

I think it is pretty straightforward

I thiink its not that important to get the warranty back (at least on Indian variants) as flashing the stock ROM via SP flash tools of fastboot does the job. Interesting procedure by the way.......

There's currently no checking either here in Indonesia, but better safe than sorry

 

[Saurabh K]

Again, why would you want your warranty, there is a solution of any problem on XDA ....

Sent from my Sparkle V

 

[awaaas]

Again, why would you want your warranty, there is a solution of any problem on XDA ....

Sent from my Sparkle V

Some problems are simply not resolvable by us, for example, in this video, the phone's light sensor is broken, can you repair it by yourself? No, and reflashing the phone doesn't help. You still needs the warranty service for something that outside your reach/knowledge.

 

[Saurabh K]

Any manufacturing defect is always the responsibility of the company and any hardware damage done intentionally is not covered under warranty if I'm right. I appreciate your work and of course I'm not arguing.

Sent from my Sparkle V

 

[DarkHeart Z]

Will it work for 8 gb devices too ?

 

[awaaas]

Will it work for 8 gb devices too ?

Yes, I personally tested this on 8 GB device.

 

[DarkHeart Z]

Yes, I personally tested this on 8 GB device.

Thanks a lot lot much more bro you guys have made our day easier than ever

 

[DarkHeart Z]

Yes, I personally tested this on 8 GB device.

And one last thing I need to know . I booted into twrp but adb is not working can I know why ?

 

[awaaas]

And one last thing I need to know . I booted into twrp but adb is not working can I know why ?

Check your device manager, maybe your device isn't yet installed properly. Install the driver manually if that actually the case.

 

[DarkHeart Z]

Check your device manager, maybe your device isn't yet installed properly. Install the driver manually if that actually the case.

Checked . No missing driver showed . same thing happened with sp flash tool too . but later after 1st unlocking bootloader driver got recognized . I am wondering if it is the cause .

 

[awaaas]

Checked . No missing driver showed . same thing happened with sp flash tool too . but later after 1st unlocking bootloader driver got recognized . I am wondering if it is the cause .

I have updated the original post with flashable zip, just flash it via your custom recovery, and you should be done.

 

[DarkHeart Z]

I have updated the original post with flashable zip, just flash it via your custom recovery, and you should be done.

Thanks bro . Will you create a flashable zip for backing up orginal seccfg ? please . since I cannot access adb from recovery so it will be really helpful for all of us
Edit : Latest twrp has this kickass feature called terminal command . this fixed my problem . I backed up my original seccfg with it .
Edit : Bro the the person who modified the recovery actually broked the adb and many other features too . I used @1cefire 's recovery and everything is perfect there . just like mini android os in recovery .

 

[KcLKcL]

Thank you very much for this, I made my own seccfg backup after reading this thread, and I'm glad I did. I managed to restore it as well. No need to worry anymore about warranty