yashsingh1/xdaforums huggingface dataset:
[Xiaomi Redmi Note 3 Guides, News, & Discussion] vdbhb59:
****** I DO NOT TAKE ANY RESPONSIBILITY FOR ANY BRICKS/BOOT LOOPS/Mi LOGO BRICK. I AM SHARING THE STEPS THAT I HAVE USED AND YOU USE THESE STEPS AT YOUR OWN RISK ******

Use Android Image Kitchen to decompress and Recompress.

Unzip the whole Kitchen and ROM files through 7 Zip * mode.

Copy the "boot.img" to the Android Kitchen Unzipped Folder.

Follow the following steps:

Step 1. Decompress the boot.img file through Android Image Kitchen (unpackimg.bat)

Step 2. Open the file "fstab.qcom" via notepad / notepad++.

Step 3. Remove the ".verify" from it and save the file. Do not change the file extension. (Though it should not ask/or do). (This unlocks bootloader over server).

Step 4. Open default.prop via notepad / notepad++.

Step 5. Change "ro.secureboot.devicelock=1" to "ro.secureboot.devicelock=0" (This unlocks the bootloader).

- Additional Amendments if you want, like enabling adb, debug, etc, then do Step 6, else go to Step 7. STep 6 somehow seems to have some error on WiFi access. In case you do not want that, do not perform Step 6. a. and 6.b.,.

Step 6. Change:

a. "ro.secure=1" to "ro.secure=0"

b. "ro.adb.secure=1" to "ro.adb.secure=0"

These enable OEM Unlock over Server and over Developer mode.

c. "ro.debuggable=0" to "ro.debuggable=1".

This turns on USB Debug.

d. "persist.sys.usb.config=none" to "persist.sys.usb.config=adb"

This turns on ADB mode.

e. "persist.sys.timezone=Asia/Shanghai" to "persist.sys.timezone=Asia/XXX".

One can set the default locale from here. (This does not seem to work on Beta ROM's, as the server denies setting locale). (Though it should not ask/or do).

- Save the file. Do not change the file extension.

Step 7. Recompress these files back through repackimg.bat."

A new file "image-new.img" will be created. Rename the file to "boot.img" and replace the same to the unzipped folder of the ROM.

You now have a cooked/modded boot.img within the ROM, and your device is bootloader unlocked. Now Flash the ROM through MIFlash.

Also note: Rename the TWRP/Custom Recovery image to "recovery.img" and replace it with the Stock Recovery within the ROM. Now you have Custom Recovery ROM.

These steps take no more then 5-6 minutes, and are pretty easy. :)

Happy Flashing.

N.B.: I have attached the Android Kitchen File here. :)
[Xiaomi Redmi Note 3 Guides, News, & Discussion] BlueJeans:
Is this equivalent to unofficial unlock or the official one?
[Xiaomi Redmi Note 3 Guides, News, & Discussion] vdbhb59:
Actually None. I mean not the official, nor the unofficial one.

I am on unlocked bootloader myself.

These are the steps I did to unlock my bootloader.

I have even rooted my RN3QC within 10 days from purchase.

I just wanted to unlock and have even custom TWRP 3.0.2-2. :)
[Xiaomi Redmi Note 3 Guides, News, & Discussion] meangreenie:
can miflash just flash the boot.img?
[Xiaomi Redmi Note 3 Guides, News, & Discussion] vdbhb59:
Nope, I tried, and it went to bootloop once and second time to mi logo.

The easiest way to install the boot.img and the recovery.img are:

If you want TWRP to be your recovery and that too after flashing the ROM, I will ask you to replace the default recovery file within the unzipped ROM with the TWRP Recovery File. The default recovery path is within the images folder and called recovery.img.

Just rename the TWRP Recovery image file to recovery.img and replace it in images folder, and flash through MIFlash. Done. :)

And if you want to flash boot.img, then flash through TWRP. That is the easiest method.

Safe and no bricks.

N.B.: FYI: Few Stable ROM's have a verity check on even after official unlock. That just means that the server has not yet updated their unlock, and if it is not done manually, then it will remain locked on server.
[Xiaomi Redmi Note 3 Guides, News, & Discussion] NVDX11:
Nice tutorial , this will be helpful to those people who are still stuck on 50% error ,Good work !
[Xiaomi Redmi Note 3 Guides, News, & Discussion] vdbhb59:
Hope that moderator is not here too. :P
[Xiaomi Redmi Note 3 Guides, News, & Discussion] NVDX11:
Haha , yep :laugh:
[Xiaomi Redmi Note 3 Guides, News, & Discussion] kraatus90:
So this should work on redmi 3s too ? gonna give it a try now. thanks dude.

Btw are you the guy who got banned on miui forum ? i had bookmarked a post similar to this but when i actually got time to read it, it was deleted by mod.

Edit : does not work lol, was stuck on Qualcomm HS-USB Diagnostics 900E mode, and couldn't get it to fasboot/edl mode. tried many different key combinations and and now finally got it fixed. so i guess it works only on RN3. now gotta wait for them to fix their db.
[Xiaomi Redmi Note 3 Guides, News, & Discussion] vdbhb59:
R3S it should not work, and as you confirmed it does not work.

Yes I am thr guy whose post got deleted, and the Mod is still adamant on saying it does not unlock bootloader.

They have changed the method to unlock on MM, so this apparently is only for LP.
[Xiaomi Redmi Note 3 Guides, News, & Discussion] abihary:
Noob question, due to I need to ensure something.

Point 6.b.

It is correct, change "ro.adb.secure=1" to "ro.secure=0"

Since this is different command.

Anyway, thanks for your share.
[Xiaomi Redmi Note 3 Guides, News, & Discussion] vdbhb59:
Thanks for pointing this out bro. My typing error.

It is ro.adb.secure
[Xiaomi Redmi Note 3 Guides, News, & Discussion] abihary:
You're welcome. I need to share this simple way to my friend, thats why i read it carefully to avoid any problem. For myself, already unlocked few weeks ago.

Anyway, thanks for your feedback.
[Xiaomi Redmi Note 3 Guides, News, & Discussion] vdbhb59:
Any day welcome. :)
[Xiaomi Redmi Note 3 Guides, News, & Discussion] zenex01:
For kenzo or hennessy?
[Xiaomi Redmi Note 3 Guides, News, & Discussion] NVDX11:
For kenzo
[Xiaomi Redmi Note 3 Guides, News, & Discussion] vdbhb59:
Kenzo and unfortunately currently limited to LP. :(

Searching for MM and N pattern to unlock.
[Xiaomi Redmi Note 3 Guides, News, & Discussion] MiripRedmoon:
What MIUI version you using? [MENTION=7281065]vdbhb59[/MENTION]

I tried with 7.3.2.0 after flashing then check bootloader but still locked. I skip step 6.
[Xiaomi Redmi Note 3 Guides, News, & Discussion] vdbhb59:
I am on 6.9.9 Global Beta. I had unlocked when I was on 6.8.18 Global Beta.

You need to check the steps properly, or if you want, attach your boot.img filehere, and I will change and reattach it here for you.
[Xiaomi Redmi Note 3 Guides, News, & Discussion] candiesdoodle:
So you are back to a locked bootloader when you moved to 6.9.9?

And for doing that you just flashed the fastboot tgz file in edl mode?

Btw, overall comment -> u mean to say .. using this process there is no need to replace/ flash the modded emmc_appsboot.mbn file?
[Xiaomi Redmi Note 3 Guides, News, & Discussion] vdbhb59:
No, I am still on an unlocked bootloader, and though I am on an unlocked state, others seem to be facing issues while trying to unlock their bootloader. I never had to unlock it officially, though post moving to 6.9.9 (6.8.18 is an earlier version), I checked, and mine showed already unlocked.

I have been flashing both fastboot and recovery files in both the modes (fastboot and edl mode) and also via the recovery (twrp), I flashed my boot.ig through twrp as well.

However, I will suggest flash recovery through edl/twrp mode, and fastboot through fstboot mode, cause I am not afraid of bricking my phone. I am used to all these. :D

And the replacing of emmc_appsboot.mbn at times causes hardbrick for few kenzo as well as kate devices, so what I do is I amend just the cache on it, and use it for my own. Editing biNary files can be troublesome. I used this as a guide for my first 5 times, and still hard bricked my phone the 6th and the 7th time (This is for my Galaxy Grand Duos I9082). lol

http://xdaforums.com/showthread.php?t=2192061
[Xiaomi Redmi Note 3 Guides, News, & Discussion] MiripRedmoon:
Yeah, i follow the steps properly, tried again using all steps, the phone cannot boot.
[Xiaomi Redmi Note 3 Guides, News, & Discussion] vdbhb59:
Use the modded boot file, with SSU2.65 and TWRP3.0.2-2. There are few who are facing issues due to some hardware issues, but not to sure what exactly. :(
[Xiaomi Redmi Note 3 Guides, News, & Discussion] GrabielZero:
This work on the RN3 especial edition? i tired to try official unlock and always stop un 50%
[Xiaomi Redmi Note 3 Guides, News, & Discussion] candiesdoodle:
Regarding the emmc_appsboot.mbn ... My question was specifically on whether you have to replace this file to have an unlocked bootloader. All guides mention that the stock emmc_appsboot.mbn needs to be replaced with a modded one. Ofcourse that entails editing the file in hex or binary etc.

However as a process.. your guide did not cover this part though now you mention that you actually do something with it (amend the cache?)

So I think it will be helpful if you explain the detailed steps for this part and include in the OP.

Edit: btw, the link you posted is about changing the partition sizes using the emmc_appsboot.mbn file. How does it relate to Unlocking the bootloader.
[Xiaomi Redmi Note 3 Guides, News, & Discussion] tofu21:
This is really odd. unpackimg.bat tells me "no image file supplied" . I found that could mean the file is signed but what does that even mean?

I even executed the bat file in command prompt with Admin control. Still, same error.

Edit again: Found this thread and used unpackimg filename.img to extract and it worked!!! :D

http://xdaforums.com/showthread.php?t=2073775
[Xiaomi Redmi Note 3 Guides, News, & Discussion] tofu21:
Okay, I can say that this method doesn't work for my Snapdragon phone. Perhaps I'm doing something wrong. In all my attempts, I used Global stable fastboot roms like Version: V7.3.5.0.LHOMIDD up to Version: V7.3.7.0.LHOMIDD and have flashed at least 5 times.

I followed all the steps but skipped Step 6. MiFlash always says "success". However, when I booted up the phone, I got stuck in EDL mode, boot loop or even some black screen with an image of a phone connected to a cable(forgot what that's called). Maybe I'll come back to this another day...
[Xiaomi Redmi Note 3 Guides, News, & Discussion] vdbhb59:
TBH, if you read I do not replace the media biNary file, nor do I amend cache to RN3, albeit to Grand Duos.

However, the only reasn I do not replace mbn is cause the modded files make many apps crash for me. I tried it the first time with RN3, but many Indian Apps crashed. However, if you want, I will go ahead and mention the step in my OP. Will mention though, an and fc/fs may happen.

Also, I use my own mbn file, however cannot upload that one, cause I change a lot of stuff in it, and may give sysui crashes to others.

Edit: Unable to recollect which link you are talking about mate?
[Xiaomi Redmi Note 3 Guides, News, & Discussion] vdbhb59:
As I mentioned, this is only for LP, and also that many people are not able to unlock this due to some issues, which I am unable to identify. However, I will try and see what I can do. I will be offline for almost a week or so, as am not in town. However, will try and look it up asap post that. Cheers mate.
[Xiaomi Redmi Note 3 Guides, News, & Discussion] candiesdoodle:
Frankly, i think your method is 'misleading'.

I would urge people not to follow this method. There is not a single user who has confirmed this method is working. Only confirmations are of brick/ bootloops etc.

You still havent updated your OP to talk about what you do the emmc...mbn file which is critical to unlocking the bootloader.

And then You forget about the link in your post (really?) ---> http://xdaforums.com/showthread.php?t=2192061

This method is incomplete/ incorrect at best!!
[Xiaomi Redmi Note 3 Guides, News, & Discussion] vdbhb59:
Firstly: KINDLY Mind your language -> C***???

Secondly: Do you think everyone is free to post everything and remember everything??

Thirdly: I post or go through many links, why do you believe that I will remember or know what link you are asking about. Did I dream of it?

Fourthly: I speak politely, and if I am wrong, I accept it. I may be mistaken here, but I feel a sense of revolt here. Did I go ahead and fool anyone? I shared my way of unlocking, and mind it mate, I have given each steps as I took them.

Fifthly: I did not and I repeat, never used and modded or edited/modded a mBn file for RN3 QC. Hence, there is no way I will tell others to use it. It is their own wish if they want to use or not, and they will do it at their own risk.

Finally: Kindly and I repeat this again, KINDLY do not use any bad words. Refrain from speaking mannerlessly.

Danke Schôn

Vishal
[Xiaomi Redmi Note 3 Guides, News, & Discussion] candiesdoodle:
happily removed the word that made you so offensive dude. haha

good luck :good:
[Xiaomi Redmi Note 3 Guides, News, & Discussion] vdbhb59:
Bro, I did get offensive, but I will also be humane enough to accept that I do not want to post the details for modding emmc_appsboot.mbn as I had once assisted one of my friends in modding it, told him how to do it, and somehow or the other his phone got bricked to the point wherein he lost almost his hardware as well. I hence do not take chances with others, as I know how to do it, but then others may not be able to do it. (Not judging anyone).

Anyways, I apologies for my bad behaviour and heated manners.

Warm Regards,

Vishal
[Xiaomi Redmi Note 3 Guides, News, & Discussion] manudhomra:
Does this mathod works with MIUI Global Developer rom 6.6.29. or which version support plz confirm
[Xiaomi Redmi Note 3 Guides, News, & Discussion] candiesdoodle:
No it doesn't. Don't risk it
[Xiaomi Redmi Note 3 Guides, News, & Discussion] master.pumpgun:
tried it a minute ago, just bricks you device (6.8.18 developer)
[Xiaomi Redmi Note 3 Guides, News, & Discussion] candiesdoodle:
Told you...

Read the thread you would have figured out anyways!! I don't know why this thread is still open. Mods should just close it.

Hope you recovered your device.
[Xiaomi Redmi Note 3 Guides, News, & Discussion] Free Radical:
Yep, doesn't work. Neither did the reddit method by its own.

Soft bricked my virgin locked bootloader Kenzo which I bought yesterday and flashed with China developer fastboot rom . Don't fret, its easily recoverable using Fastboot-EDL and reflash using MiFlash.

Better to just use the unofficial unlock method.
[Xiaomi Redmi Note 3 Guides, News, & Discussion] master.pumpgun:
hm, I made a mistake while following the steps, just realised that the comma = ",verifiy" must be deleted. I just deleted the "verify". And in the same try I took a custom recovery to miflasher so it maybe work with just boot.img flashing?
[Xiaomi Redmi Note 3 Guides, News, & Discussion] Pera.Kojot:
One thing... Im little green in this kind of work so I have to chack all twice.

After repack img result is two files: image-new.img and ramdisk-new.cpio. First had to be renamed to boot.img and what about second?

Looking in kitchen folder after unpacking you will have 2 new folders: ramdisk and split_img. And in folder split_img you will find fajl boot.img-ramdisk.cpio.gz . And all editing is done on files in ramdisk folder.

I dont have knowlage to say exact but i think that is reason for all reported unsuccess trys of your method. Simply repackimg.bat dont repack boot.img in right format for kenzo.
[Xiaomi Redmi Note 3 Guides, News, & Discussion] vdbhb59:
Just rename "image-new.img" to "boot.img". Copy paste the newly created image file to the ROM folder. Keep a copy of the original boot image in case of any issues to reflash with this. Run the cleanup.bat, and in case any clear off the unpacked unwanted files post repacking.

I just flashed another ROM 6.11.3 (Global Dev), successfully.

I am flashing almost every week. I follow the same method.

Cannot say why others face "no success". :eek:
[Xiaomi Redmi Note 3 Guides, News, & Discussion] vdbhb59:
Yes works on all versions. :)
[Xiaomi Redmi Note 3 Guides, News, & Discussion] vdbhb59:
It works smoothly. Else why would I post it here. Odd, that people do not try properly.

If it should be closed, why not you try to post something that you tried and want to share?

Anyhow, it works, and I flash regularly. Odd for others.
[Xiaomi Redmi Note 3 Guides, News, & Discussion] chirag2212:
If i will unlock bootloader of my rn3 (kenzo) this way then all custom roms like cm13 cm14.1 etc .. flash directly without any zip edit or boot patch or emmc problems..
[Xiaomi Redmi Note 3 Guides, News, & Discussion] vdbhb59:
Please close the thread@

Hello Site Admins..

Kindly close the thread.
[Xiaomi Redmi Note 3 Guides, News, & Discussion] vdbhb59:
Unlock Bootloader

* EXTRA STEP - Make SURE ADB INTERFACE is UNINSTALLED *

Open and login your account with Mi Unlock Tool and minimize it,

Once you're logged in then disconnect your internet connection.

Boot into fastboot mode (Hold Volume Down+Power), a Mi bunny image will be shown. Plug your device into the computer.

Open Device Manager and search for Kedacom USB Device, double click on Android Bootloader Interface, then click Uninstall, tick Delete Driver Software for this device then OK

Unplug and reconnect your phone (phone state is still in fastboot mode)

Device manager will start blinking and an Android Phone will appear, wait till driver installing window disappear after you plugged your device

After the driver installing windows is gone then reconnect your Internet.

Open the Mi Unlocking Tool wait till it detect your device.

Once it's shown then tap on Unlock

I unlocked in 1 try after these steps..

I had never tried this one earlier, so was not aware..
[Xiaomi Redmi Note 3 Guides, News, & Discussion] vdbhb59:
Will rewrite the exact steps I did to get the phone unlocked for 50% error of account different from the device.

1. First log off from mi account on phone.

2. Then connect device in normal mode to PC.

3. Login to mi unlock with mobile number. Minimize it and don't close it at all.

4. Open device manager and search for adb interface. It will be showing with a yellow exclamation mark.

5. Uninstall it.

6. Disconnect internet on both PC and Mobile.

7. While connected to PC launch into fastboot mode.

8. Let PC try and install adb interface. It will or will not be able to. Don't worry if it does not.

9. Once the status is done or not done for adb, disconnect the phone from PC while in fastboot mode.

10. Uninstall adb interface again.

11. Reconnect mobile still in fastboot mode.

12. If adb gets installed good, if not then better.

13. Reconnect internet on PC.

14. Click on unlock.

15. Voila. Done and dusted.

Tip. If you get issues, just try with failed adb (exclamation one).

The steps took 3-4 minutes.

Ensure your sync and backup is completely off on phone for MI Cloud.

??
[Xiaomi Redmi Note 3 Guides, News, & Discussion] Art Vanderlay:
Thread closed at OP's request.
[Verizon HTC 10 Questions & Answers] eriknors:
So my problem is this, everytime I try to change roms my phone doesn't recognize my Google account as being the only account I've ever registered my phone with. Has anyone ran into this and if so what can I do to fix it? I'm S-OFF and UNLOCKED running leedroid and am on the latest TWRP.
[Verizon HTC 10 Questions & Answers] dottat:
See hangout. Not for posting here.
[Nexus 6P Q&A, Help & Troubleshooting] krolla03:
Hey all you people who have flashed some version of 7.0. How is Doze on the go working for you? Have you noticed an increase in battery life? Are you missing notifications?

Or did you still see better battery life with Xposed and Amplify?
[Nexus 6P Q&A, Help & Troubleshooting] joooe:
There's already threads about the battery on Android 7. Why start another?
[Nexus 6P Q&A, Help & Troubleshooting] krolla03:
Sorry didnt see (actually i didnt really look that hard) my bad
[Nexus 7 (2013) Q&A] CWempe:
I think my Nexus 7 ist bricked. :(

But first things first:

- I unlocked and rooted my Nexus 7 a long while ago and could not ota-update the firmware because of that.

- last time I tried flashing the factory image I failed, because the device was not recognized correctly in fastboot mode connected to my windows computer

so I was stucked with my android 5

- for some reason I have no working recovery mode. :(

I finally tried it again now and got a little further.

After unsucessfully trying to edit the INF-file for the latest_usb_driver_windows, i tried connecting the tablet to my ubuntu media pc.

For the first time "fastboot devices" showed my device!

I locked the bootloader again to install the OTA update.

Fore some reason the installation resulted in an "error" (dead android figure). :(

Then I tried:

sudo fastboot flash recovery openrecovery-twrp-2.8.5.0-flo.img

and got:

sending 'recovery' (8166 KB)...

FAILED (data transfer failure (Protocol error))

finished. total time: 0.010s

- I tried many different usb cables (incl. the original cable and some more expensive from Anker)

- I tried all USB ports (USB 2.0 and 3.0)

Any idea what I can try next?
[Nexus 7 (2013) Q&A] k23m:
It is not bricked :)

the protocol error comes from an obsolete Ubuntu fastboot app

no need to lock the bootloader to receive OTA updates

NRT can simplify USB driver installation on Windows

you may need factory image, CM, or TWRP
[Nexus 7 (2013) Q&A] CWempe:
This tool sounds great.

But unfortunately it does not work for me. :(

I still get the "device could not be started (code 10)" error in Win10 device manager.

(Maybe I should have mentioned this sooner)

I tried all drivers.

Does anybody know if there is a better/working fastboot version for ubuntu.

To sumerize, I have two problems at the moment:

- Windows: driver issue

- Ubuntu: fastboot issue.

:(
[Nexus 7 (2013) Q&A] k23m:
Linux Mint Fastboot

Yes, try:

get linuxmint-18-cinnamon-32bit.iso and boot it from USB (no need to install it)

start networking

use Software Manager to install 'Fastboot' (virtually in RAM)

download twrp-3.0.2-0-flo.img

boot N7 in fastboot mode and plug it in

check lsusb for ID = 18D1:4EE0

run: sudo -i

run: fastboot boot twrp-3.0.2-0-flo.img

Works for me...
[Nexus 7 (2013) Q&A] CWempe:
Finally got the time to try your solution.

The device gets recognized correctly in Linux Mint.

I installed "fastboot" (not "android-tools-fastboot").

Version: 1:6.0.1+r16-3

When I execute the boot command I get:

"downloading 'boot.img'...

FAILED (data transfer failure (Value too large for defined datatype))"

When I execute the same command again, it stays at "downloading [..]" and nothing happens.

I am using the original Nexus 7 USB cable.
[Nexus 7 (2013) Q&A] k23m:
But did you unlock the bootloader first? Do it and never re-lock, OTA does not depend on it.

Then post the output of:

fastboot oem device-info
fastboot getvar all
fastboot oem gpt-info
fastboot format cache
[Nexus 7 (2013) Q&A] k23m:
In your first post you wrote "I unlocked and rooted my Nexus 7 a long while ago" but then "I locked the bootloader again to install the OTA update" :confused:

While the fault symptoms are new and unique, they point to eMMC flash memory IC failure. Typical faulty eMMC test...

fastboot format cache
Size: 587202560
Block size: 4096
Blocks per group: 32768
Inodes per group: 7168
Inode size: 256
Journal blocks: 2240
Label:
Blocks: 143360
Block groups: 5
Reserved block group size: 39
Created filesystem with 11/35840 inodes and 4616/143360 blocks
...[hangs forever]...

Your eMMC goes further but still rejects an update. There is an indication that you have the fault-prone Kingston eMMC, note your log...

(bootloader) partition[30].size 27852783 KB

Hynix eMMC has:

(bootloader) partition[30].size 28180463 KB

More info is linked in my signature.
[Nexus 7 (2013) Q&A] CWempe:
You got me.

But I also said I tried flashing TWRP, wich needs unlock, right? :)

Nevermind.

It looks like a new motherboard is a little expensive and not easy to buy in germany.

So my only other options I see are:

- ASUS Service (I will try to contact them)

- pray for a fix (http://xdaforums.com/nexus-7-2013/general/rd-thread-trying-to-solve-ota-brick-t3117495)

- wait for the Google Pixel 7 to be release in a few month. ;)