Database Users

[GUIDE] Unlock Bootloader, Root, Install TWRP & Decrypt

For an easy way to Unlock, Root & Decrypt your Mate 8 here are the steps you need to take. This has been requested by a number of you so here it goes:
1) Unlock your bootloader. There are three steps you can take. The first is free. The second method requires you to pay a few dollars but it works and is the fastest way. I would highly recommended this method. This is confirmed working on all models.
Option 1: Make a Huawei ID on your phone and stay signed in for 14 days and go then online to unlock your bootloader and it should work on the website.
https://uniportal.huawei.com/accounts/register.do?method=toRegister
Option 2: If you want to unlock your phone immediately and don't mind paying a few dollars this method works. Visit here:
https://www.dc-unlocker.com/buy
- Download the DC Unlocker Software
- On their site buy 4 credits. I used PayPal. It cost me around $4.38 USD.
- Follow the instructions in their tutorial. Choose "Read Bootloader Code" in DC-Unlocker to get your bootloader code. It was pretty easy.
- Put your phone in bootloader mode (plug into the computer and hold in power and volume down with the phone off) and download the Android tools from the link at the end of step two. Extract them to a folder on your desktop and open a command prompt to that folder and type in fastboot oem unlock xxxxxxxxxxxxxxxx where x is your bootloader unlock code the DC Unlocker program gave you.
2) Download the TWRP recovery of the EMUI version you are currently on (5.0 ,5.1, 6.0) from here:
https://drive.google.com/drive/folders/0B5I_q70mNuR4Vmo5LUUyU2t5TWs?usp=sharing
Then put your phone into Bootloader Mode (plug phone into computer and hold in power + vol down) and fastboot flash the TWRP recovery file you downloaded. Here are the Android tools you need to fastboot flash. Extract them to a folder and put the twrp recovery img file inside the folder as well and open up a command prompt to the folder and type in fastboot flash recovery TWRP-ENG-XXX.img (where XXX is the version of TWRP you downloaded) Then type in fastboot reboot. When your phone reboots shut it back down and then hold in volume up and power until it turns on and keep holding in volume up until the phone boots into TWRP recovery.
https://drive.google.com/file/d/0B5I_q70mNuR4UzdkeERRZExnUVk/view?usp=sharing
3) Root your phone.
In TWRP flash SuperSU:
https://drive.google.com/file/d/0B5I_q70mNuR4OWlXeTJuTjdoS0k/view?usp=sharing
After flashing you will be rooted and on TWRP successfully.
4) Decrypt your internal storage.
You must decrypt your internal storage so TWRP can see it or if you want to be able to flash a rom. If you're getting an unable to format data in TWRP then you know you need to do this. Boot into TWRP then go to Wipe then Advanced Wipe then Format Data and type in yes. This will wipe and decrypt your internal storage. BACK UP YOUR INTERNAL STORAGE before you do this if you have anything important on it. (Pics are at the bottom of this post) Then either flash one of my roms or decrypted boot.img to keep the internal storage decrypted. If you boot with the stock boot.img installed it will encrypt your internal storage again and you'll have to repeat the process.
*To take an ota or do the dload method you don't have to relock"

does flashing supersu through twrp directly work? in my case i needed to flash the decrypted boot image first, otherwise id have a bootloop after rooting...
Sent from my Huawei Mate 8 NXT-AL10 using Tapatalk

jbmc83 said:
does flashing supersu through twrp directly work? in my case i needed to flash the decrypted boot image first, otherwise id have a bootloop after rooting...
Sent from my Huawei Mate 8 NXT-AL10 using Tapatalk
Click to expand...
Click to collapse
It works for me when i'm on stock B137.

good stuff, maybe it was because of a different supersu version which phone do u have? AL10 or L29?

ajsmsg78 said:
It works for me when i'm on stock B137.
Click to expand...
Click to collapse
I downloaded your B137 and flashed it but its B133. I think B 133 is the latest one

jbmc83 said:
good stuff, maybe it was because of a different supersu version which phone do u have? AL10 or L29?
Click to expand...
Click to collapse
AL10. Make sure you have SuperSU 2.65 Beta

m3dd0g said:
I downloaded your B137 and flashed it but its B133. I think B 133 is the latest one
Click to expand...
Click to collapse
I think that's the latest international firmware, no?

ajsmsg78 said:
I think that's the latest international firmware, no?
Click to expand...
Click to collapse
B133 is the latest international B137 is the latest chinese right?

m3dd0g said:
B133 is the latest international B137 is the latest chinese right?
Click to expand...
Click to collapse
I believe so. I'm not too familiar with the International firmware. I saw it posted somewhere so I saved it in case anyone needed it.

yep thats correct, B137 latest chinese and B133 latest international rom
thanks for the info, i had some problems with flashing supersu, but once i flashed the decrypted boot image my bootloop and partition mounting troubles in twrp were gone no idea what exactly was the culprit there but i guess ill stick to flashing the decrypted boot.img first before continuing with rooting a firmware...

i would like to do the 4$ Method. But link is dead
"Option 2: If you want to unlock your phone immediately and don't mind paying a few dollars this method works. Visit here:
https://www.dc-unlocker.com/how-to-r...er-unlock-code".
So i cant do it..
edit:
i think the dead link is:
https://www.dc-unlocker.com/huawei-android-hisilicon-unlock-guide
but if i scroll down there is no MATE8. Only MATE 7.

EGOiST1991 said:
i would like to do the 4$ Method. But link is dead
"Option 2: If you want to unlock your phone immediately and don't mind paying a few dollars this method works. Visit here:
https://www.dc-unlocker.com/how-to-r...er-unlock-code".
So i cant do it..
edit:
i think the dead link is:
https://www.dc-unlocker.com/huawei-android-hisilicon-unlock-guide
but if i scroll down there is no MATE8. Only MATE 7.
Click to expand...
Click to collapse
I made it two days ago and it works with mate8.

Does this now mean we are likely to see numerous custom roms & kernels being developed in the very near future for this awesome smartphone ?

i sure hope so especially since huawei seems to have publicized its kernel source for the mate 8 just recently in the end it depends on the interest of the devs, though, and the overall popularity of the mate 8! im staying optimistic that itll be better than with the mate 7

jbmc83 said:
i sure hope so especially since huawei seems to have publicized its kernel source for the mate 8 just recently in the end it depends on the interest of the devs, though, and the overall popularity of the mate 8! im staying optimistic that itll be better than with the mate 7
Click to expand...
Click to collapse
Its a BEAST of a phone, lets hope its POWER can be UNLEASHED to its true potential with such development

dont work . paid 4$ got things that looked like:
8++++++++++++++++++Unlock codes:
NCK : 46++++++++++++++++++
NetSub : 1++++++++++++++++++
SP : 00++++++++++++++++++
Unblock : 2++++++++++++++++++
and it says always failed (rmeote: password wrong)

EGOiST1991 said:
i would like to do the 4$ Method. But link is dead
"Option 2: If you want to unlock your phone immediately and don't mind paying a few dollars this method works. Visit here:
https://www.dc-unlocker.com/how-to-r...er-unlock-code".
So i cant do it..
edit:
i think the dead link is:
https://www.dc-unlocker.com/huawei-android-hisilicon-unlock-guide
but if i scroll down there is no MATE8. Only MATE 7.
Click to expand...
Click to collapse
Don't worry, it works with the Mate 8. You're doing something wrong if it didn't work.

Say we do unlock BL and then root... Than I guess we cannot get OTA updates right? Also does the BL re-lock?

icy20 said:
Say we do unlock BL and then root... Than I guess we cannot get OTA updates right? Also does the BL re-lock?
Click to expand...
Click to collapse
You should still get ota updates if you're unlocked and rooted. Yes you can relock just make sure you fastboot flash or do the dload method to get back to stock before you relock.

it's the code in first line, cofusing
---------- Post added at 01:06 AM ---------- Previous post was at 01:06 AM ----------
your phone is already unlocked to provider

[Guide][How to]Update Bootloader/Firmware to OOS3/H2OS2 w/o installing OOS/H2OS

Okay guys first let me tell you why I have created a new thread just for updating the BL and Firmware ,
I know we already have methods of updating like:
1. flashing the full OOS3 zip through stock recovery ,this method is quite simple for the ones who are on stock recovery and just want to update their OOS version.If you fall in this category then you have no purpose here,you may leave.
2. Is method provided by our fav helping hand @Joshwin Aranha ,that method is sure for the rest of us who dont fall in the above category,but is way too long,although simple and effective still "long".
I created this thread to help the CM13(Official or Sultan's)//any custom rom using new BL,users who want to update their BL without flashing the OOS through the tedious way just to update BL and users who are stuck on bootlogo due to old BL with roms using new BL.
Here I will guide you through the required steps to update our bootloader "In easiest and fastest way without wiping and restoring anything".
So what are we waiting for ,lets start .
Prerequisites
you will need two files for this process,nothing else.
1 . First one is BLUpdater zip --->Here.
2. Second is TWRP compiled from latest sources use either This or the one from Here<--use v41 or use Sultan's from Here OR if you are Martin's fan like me and want to use his MutiRom TWRP goHere.
PS:I am assuming you have Unlocked Bootloader and have either
official/blu_spark/sultan's/ Multirom TWRP installed,in a working condition on OOS2.x BL(if not what are you doing here).
Note: make sure oem unlocking is checked in developer options in your current rom,else updating the BL may cause it to get locked ,and you will have to unlock it again and flash the recovery manually through fastboot itself.
Now the steps
1.First copy both of the above files in your sdcard or otg or ext-sdcard,any place accessible in recovery.
2. Now boot into recovery Choose Install and choose the "OPXBLUpdateOOS3.1" zip and flash it.
3. Don't reboot now ,go to Install again ,this time use "Install Image" button in lower right corner,navigate to folder where you copied the new TWRP,you should be able to see the file,select it ,choose recovery in the next menu and flash.
NOTE:If you chose to use Sultan's recovery.zip then just flash it normally.
4. Don't reboot come back to TWRP home ,goto reboot and recovery ,if TWRP says no OS installed ignore it.
Now voila you should have updated your firmware/BL.Congrats.
You can now install any rom that supports the new BL.Older roms won't boot on the new MM BL.So check the rom thread before installing the rom and later on quacking here about your device being stuck at bootlogo.
Notes
i)Neither I nor XDA will be responsible if your OPX bricks or explodes or ditches you and flies to space.
ii)We are not touching system partition so last installed ROM will be intact.
iii)This guide will leave you into bootable rom only if you have a rom installed that works on latest firmware.
iv)This can also be used to restore all your OPX partitions back to OOS3.x partition state,if you messed any.
v)In case you are using latest nightly (cm13) and face bootloop - go Here
psst:If you are not diggin the new BL,and wanna downgrade again ,back to old BL,check this post.
PS: (second one,I know) This guide was made by taking inspiration from Joshwin's post and devtry method.
Also click Thanks if I helped you

matwaking said:
Okay guys first let me tell you why I have created a new thread just for updating the BL and Firmware ,
I know we already have methods of updating like:
1. flashing the full OOS3 zip through stock recovery ,this method is quite simple for the ons who are on stock recovery and just want to their OOS version.If you fall in this category then you have no purpose here,you may leave.
2. Is method provided by our fav helping hand @Joshwin Aranha ,that method is sure for the rest of us who dont fall in the above category,but is way too long,although simple and effective still "long".
So I created this thread just to shorten the process provided by Joshwin.I also created this thread to help the official CM13 users who have problem with latest nightlies due to new bootloader or are stuck in bootlogo.
...
PS: (second one,I know) This guide was made by taking inspiration from Joshwin's post and devtry method.
Also click Thanks if I helped you
Click to expand...
Click to collapse
Booomshkalaka!!!
Great guide, can't test (already have new bootloader and too lazy to switch back but look very good.
Thx to all
Kurt

Kurt Krummbein said:
Booomshkalaka!!!
Click to expand...
Click to collapse
Lol .
Thanks mate.

Will this work if I'm in bluspark twrp but the previous version..? Or do I have to change to official twrp?

jonrodz said:
Will this work if I'm in bluspark twrp but the previous version..? Or do I have to change to official twrp?
Click to expand...
Click to collapse
Will work with any twrp,no requirement of official one.

Thanks, bro. One more doubt. I'm currently on DU rom with custom kernel... Do you think rom will boot after this..?

jonrodz said:
Thanks, bro. One more doubt. I'm currently on DU rom with custom kernel... Do you think rom will boot after this..?
Click to expand...
Click to collapse
No it wont,right now almost all the custom roms need to update to support new firmware.Only latest cm13 nightlies are booting now,also aosp compiled by olddroid for new BL(shh its only for testers right now)
also maybe the MIUI8 port ,just posted in the forums.

I'm a litte bit confused.
Currently I'm on nighty October 1st. (cm-13.0-20161001-NIGHTLY-onyx.zip)
Can i update the Bootloader with your method and after that booting up my current nightly version?
Or do I have to update after the bootloader update to nightly version 12 (the currently latest)?

jerikooo said:
I'm a litte bit confused.
Currently I'm on nighty October 1st. (cm-13.0-20161001-NIGHTLY-onyx.zip)
Can i update the Bootloader with your method and after that booting up my current nightly version?
Or do I have to update after the bootloader update to nightly version 12 (the currently latest)?
Click to expand...
Click to collapse
no update the BL using the steps above ,then flash the latest nightly.That way it would be good.
Or you can flash nightly first then update BL.Choice is yours.I recommend updating the BL first.

I followed your guide with a locked bootloader, and now I'm in bootloops . Just suggest you put a big red "make sure your bootloader is unlocked" in the steps, not in the footnote.

Duplicate post.Deleted

ccaappton said:
I followed your guide with a locked bootloader, and now I'm in bootloops . Just suggest you put a big red "make sure your bootloader is unlocked" in the steps, not in the footnote.
Click to expand...
Click to collapse
Reboot into fastboot mode and
Code:
fastboot oem unlock
And using a custom recovery and custom rom makes me assume one have unlocked bootloader

matwaking said:
Reboot into fastboot mode and
Code:
fastboot oem unlock
And using a custom recovery and custom rom makes me assume one have unlocked bootloader
Click to expand...
Click to collapse
Thanks! I actually relocked my bootloader not long after installed cm13, and disabled "unlock oem" in "developer settings"(I don't know why I did this). So both system and rec is inaccessible, and fastboot is useless in this case. Fortunately I followed the unbrick guide: http://forum.xda-developers.com/oneplus-x/general/guide-mega-unbrick-guide-hard-bricked-t3272108 and get the old bootloader back. Now I could enter CM13-09-28 with all my data intact.
Just hope to let people know the hard lesson I learned, and how to deal the bootloops.
And guys, NEVER RELOCK BOOTLOADER AGAIN!

ccaappton said:
Thanks! I actually relocked my bootloader not long after installed cm13, and disabled "unlock oem" in "developer settings"(I don't know why I did this). So both system and rec is inaccessible, and fastboot is useless in this case. Fortunately I followed the unbrick guide: http://forum.xda-developers.com/oneplus-x/general/guide-mega-unbrick-guide-hard-bricked-t3272108 and get the old bootloader back. Now I could enter CM13-09-28 with all my data intact.
Just hope to let people know the hard lesson I learned, and how to deal the bootloops.
And guys, NEVER RELOCK BOOTLOADER AGAIN!
Click to expand...
Click to collapse
Well no fix without any problems hehehe,.Haapy 4 u.
Click that button if you think my posts are useful

Is this enough to install CM14 or do i have to install the whole room and them flash CM14?

Manelit said:
Is this enough to install CM14 or do i have to install the whole room and them flash CM14?
Click to expand...
Click to collapse
taking you wanna flash ashwins cm14 right. You just wanna follow the instructions in first post and then flash the cm14.No need to install the whole Oos zip.
This way you should have updated BL and working cm14.
Just flash the cm14 after booting into new TWRP

I've just followed the procedure from OP and all went smooth as butter. Thanks
Directly after that (without reboot) I've installed the latest CM13 (with GApps) and Arsenic R24. Working as a charm

slaav said:
I've just followed the procedure from OP and all went smooth as butter. Thanks
Directly after that (without reboot) I've installed the latest CM13 (with GApps) and Arsenic R24. Working as a charm
Click to expand...
Click to collapse
Press that sweet sweet button mate

1.First copy both of the above files in your sdcard or otg or ext-sdcard,any place accessible in recovery.
2. Now boot into recovery Choose Install and choose the "OPXBLUpdateOOS3.1" zip and flash it.
3. Don't reboot now ,go to Install again ,this time use "Install Image" button in lower right corner,navigate to folder where you copied the new TWRP,you should be able to see the file,select it ,choose recovery in the next menu and flash.
4. Don't reboot come back to TWRP home ,goto reboot and recovery ,if TWRP says no OS installed ignore it.
Click to expand...
Click to collapse
Hi, everyone
I'm accidentally reboot device after second step. Now device freezing on "+1 powered by android". Can I remove this zip, or... what can I do next?)

walsash said:
Hi, everyone
I'm accidentally reboot device after second step. Now device freezing on "+1 powered by android". Can I remove this zip, or... what can I do next?)
Click to expand...
Click to collapse
u can flash bluespark twrp via fasboot
Sent from my ONE E1003 using XDA-Developers mobile app

Downgrade is it allowed?

I'm using Rn7 4gb 64gb PFGMIXM global version. I wonder if i will unlock bootloader and install TWRP or Orange it will allow me to downgrade version without bricking or any problem?

On global rom the ARB is activated, if you want to downgrade to older version you can use miui.eu instead because there is no ARB on miui.eu

Hi there, you can downgrade between MIUI 10.X without the need of use of TWRP/ORANGE, you just need the Bootloader unlocked and the MI Flash Tool with any Fastboot Miui ROM (But if you want to, you can still use the custom recoveries for Recovery ROMs) I Downgraded from 10.3.6.0 to 10.2.7.0 with fastboot rom and everything went smooth. (Be aware that after using MI Flash tool the Bootloader will be relock)

BlackGarnett said:
Hi there, you can downgrade between MIUI 10.X without the need of use of TWRP/ORANGE, you just need the Bootloader unlocked and the MI Flash Tool with any Fastboot Miui ROM (But if you want to, you can still use the custom recoveries for Recovery ROMs) I Downgraded from 10.3.6.0 to 10.2.7.0 with fastboot rom and everything went smooth. (Be aware that after using MI Flash tool the Bootloader will be relock)
Click to expand...
Click to collapse
Can you give instruction? After bootloader unlock? I read other comment from other thread it can brick the device. Do we have the same device? 48mp cam and PFGMIXM? Can you post here your screenshot of your current Rn7 version?
If i'm going to install TWRP is it safer than downgrade using MI flashtool?

gAracUh said:
Can you give instruction? After bootloader unlock? I read other comment from other thread it can brick the device. Do we have the same device? 48mp cam and PFGMIXM? Can you post here your screenshot of your current Rn7 version?
If i'm going to install TWRP is it safer than downgrade using MI flashtool?
Click to expand...
Click to collapse
Hi sure, I'm on 10.3.5.0 right now, found it as the better ROM for my personal using, and yes I have global version PFGMIXM, after testing what I needed to, between 10.3.6.0-10.2.7.0 I stayed up in 10.3.5.0. (I can't post any screenshot right now but maybe later I might attach to this post --- Update, attached the screenshot)
-About the brick, I actually can't explain what it triggers but most of the time I belive has been happening to others RN7 versions.
-About the TWRP safety, is the same I believe (as long as you know what you are doing), I prefered to try the downgrade my first time using MI flashtool cuz it's official and less possibilities of problems, you can always unlock again the bootloader after the flash doing the same steps and w/o waiting time cuz already did that phase.
-The instructions are simple and they are the same given by Xiaomi in their ROM site.
On here: Fastboot Method
Instructions via Fastboot method:
-Download and install the Adb+fastboot drivers or xiaomi drivers for rn7 (that I believe you already have if you unlocked the bootloader)
-Download and install the Mi FlashTool (The link above)
-Download the FASTBOOT ROM for you need, remember it to be PFGMIXM (On internet you can find the 10.2.7.0/10.2.8.0 and the 10.3.5.0 FASTBOOT ROM -- On Xiaomi site you can find the 10.3.6.0 lastest fastboot ROM)
-Turn off the device. Press the Volume– key and the Power button at the same time to enter Fastboot mode. Then connect the device to the Windows PC/laptop via a micro USB cable.
-Double click on the downloaded ROM file to decompress it. Open the file folder for the decompressed ROM pack, and copy its path .
-Open the MI flashtool and you can either click "select" to search the folder of the uncrompressed ROM or just paste the path if you copied it early (example: C:\User\User1\Desktop\complete_folder_rom).
-Click Refresh and the device will be detected automatically.
-Then just click flash and wait the process that will take some minutes
-After the flash is done, the status will say "flash done" and will appear a "success" message, then the phone will reboot itself and start as it was out-of-the-box for the first config
Same instructions are with pictures in the link.
I didn't tried the downgrade in TWRP/Orange but I believe is the same as flashing any ROM, wipe dalvik, cache, data, system and then flash the ROM - for TWRP/Orange the ROM is the "Recovery" version ones, not the Fastboot as the steps above (TWRP will always mark you an error for MIUI Recovery ROMS so erase "compatibility.zip" in the ROM, this usually is not needed in Orange as I belive i've read it)
My recommendation is to use the Fastboot Method
Also PFGMIXM ver only have the ROM versions mentioned, 10.2.3.0 (10.2.3.0 PFGMIXM not the EEA one, it's rare to see and only come in stocks phones) it's a rare out-of-the-box-rom-version I saw, and the 10.2.1.0 was deleted from Xiaomi servers long time ago, so to downgrade you are only going to find the 10.2.7.0 ROM.

BlackGarnett said:
Hi sure, I'm on 10.3.5.0 right now, found it as the better ROM for my personal using, and yes I have global version PFGMIXM, after testing what I needed to, between 10.3.6.0-10.2.7.0 I stayed up in 10.3.5.0. (I can't post any screenshot right now but maybe later I might attach to this post --- Update, attached the screenshot)
-About the brick, I actually can't explain what it triggers but most of the time I belive has been happening to others RN7 versions.
-About the TWRP safety, is the same I believe (as long as you know what you are doing), I prefered to try the downgrade my first time using MI flashtool cuz it's official and less possibilities of problems, you can always unlock again the bootloader after the flash doing the same steps and w/o waiting time cuz already did that phase.
-The instructions are simple and they are the same given by Xiaomi in their ROM site.
On here: Fastboot Method
Instructions via Fastboot method:
-Download and install the Adb+fastboot drivers or xiaomi drivers for rn7 (that I believe you already have if you unlocked the bootloader)
-Download and install the Mi FlashTool (The link above)
-Download the FASTBOOT ROM for you need, remember it to be PFGMIXM (On internet you can find the 10.2.7.0/10.2.8.0 and the 10.3.5.0 FASTBOOT ROM -- On Xiaomi site you can find the 10.3.6.0 lastest fastboot ROM)
-Turn off the device. Press the Volume– key and the Power button at the same time to enter Fastboot mode. Then connect the device to the Windows PC/laptop via a micro USB cable.
-Double click on the downloaded ROM file to decompress it. Open the file folder for the decompressed ROM pack, and copy its path .
-Open the MI flashtool and you can either click "select" to search the folder of the uncrompressed ROM or just paste the path if you copied it early (example: C:\User\User1\Desktop\complete_folder_rom).
-Click Refresh and the device will be detected automatically.
-Then just click flash and wait the process that will take some minutes
-After the flash is done, the status will say "flash done" and will appear a "success" message, then the phone will reboot itself and start as it was out-of-the-box for the first config
Same instructions are with pictures in the link.
I didn't tried the downgrade in TWRP/Orange but I believe is the same as flashing any ROM, wipe dalvik, cache, data, system and then flash the ROM - for TWRP/Orange the ROM is the "Recovery" version ones, not the Fastboot as the steps above (TWRP will always mark you an error for MIUI Recovery ROMS so erase "compatibility.zip" in the ROM, this usually is not needed in Orange as I belive i've read it)
My recommendation is to use the Fastboot Method
Also PFGMIXM ver only have the ROM versions mentioned, 10.3.4.0 (10.3.4.0 PFGMIXM not the EEA one, that's why it's rare to see and only come in stocks phones) it's a rare out-of-the-box-rom-version I saw, and the 10.2.1.0 was deleted from Xiaomi servers long time ago, so to downgrade you are only going to find the 10.2.7.0 ROM.
Click to expand...
Click to collapse
Thank you very much for detailed instructions the reason why i want to downgrade is the battery life. I noticed after two consecutive update within one month the battery backup is not good like before. I am pretty sure about that because it has been 1 month since i bought this.
Even the power saver is always activated I'm not satisfied with the battery backup now. I'm thinking if i will flash Havoc, Lineage or Lower version of miui what do you think? which of these is good for battery?

gAracUh said:
Thank you very much for detailed instructions the reason why i want to downgrade is the battery life. I noticed after two consecutive update within one month the battery backup is not good like before. I am pretty sure about that because it has been 1 month since i bought this.
Even the power saver is always activated I'm not satisfied with the battery backup now. I'm thinking if i will flash Havoc, Lineage or Lower version of miui what do you think? which of these is good for battery?
Click to expand...
Click to collapse
Yes I did it due the same thing, for battery and ram management, but most of it perfomance, and I got it balanced on 10.3.5.0, not the best but it does the job for me. I haven't tested Havoc neither Lineage, but if just battery your concern, you can take a read to LionHeart90's Guide ON THIS LINK or you can go and try by yourself each ROM till you find the most one that suit for you :good:

BlackGarnett said:
Yes I did it due the same thing, for battery and ram management, but most of it perfomance, and I got it balanced on 10.3.5.0, not the best but it does the job for me. I haven't tested Havoc neither Lineage, but if just battery your concern, you can take a read to LionHeart90's Guide ON THIS LINK or you can go and try by yourself each ROM till you find the most one that suit for you :good:
Click to expand...
Click to collapse
Thank you for your response and for the link you gave. I think this is the day that i have been waiting for 78hrs to unlock bootloader. I guess i go with the Havoc. Thank you very much and God bless??
Update: Thank you again, I downgraded my Rn7 form 10.3.6 to 10.2.7.0

gAracUh said:
Thank you for your response and for the link you gave. I think this is the day that i have been waiting for 78hrs to unlock bootloader. I guess i go with the Havoc. Thank you very much and God bless?
Update: Thank you again, I downgraded my Rn7 form 10.3.6 to 10.2.7.0
Click to expand...
Click to collapse
Glad to know it helped you, Good luck and bless for you too. :good:

Rooting J701F

I've seen people here struggling with rooting j701f a.k.a J7 Nxt. I always got bootloop when installed TWRP and flashed Magisk, so little trick here is installing custom kernel; i am using Helios kernel 3.1 and it works perfectly. (Select wifi driver new with android pie when installing, first option).
Technically it should work on J7 Nxt /Neo /Core. Tested in J7 Nxt 701F, DDU6CSF1 Stock firmware OneUI 1.1 Indian Variant.
Procedure from start.
Given:
You're running on Pie.
OEM Unlock option enabled in developers Option.
Get Odin - https://odindownload.com/SamsungOdin/
Get TWRP - https://forum.xda-developers.com/ga...-j701f-core-nxt-exynos-7870/recovery-t3693009
Get Helios Kernel https://forum.xda-developers.com/ga...70/kernel-heliospie-kernel-3-1-j701x-t3941438
Start Odin and untick auto reboot option.
Select Boot.tar file in BL
Select Recovery.tar file in AP
Flash.
Unplug phone.
Remove battery.
Put it back.
Hold Volume up (+) then Home then Power button for 20-30seconds
Press Power button.
Press power button again.
You'll see TWRP recovery 3.1.1 , say thanks to GhaithSYR
Swipe to modify system.
Format data, Type yes (Beware it'll erase all data and factory reset except SD card.
Flash Kernel.
Reboot.
Update Magisk.
You can update your TWRP to 3.2.1 : https://forum.xda-developers.com/ga...-exynos-7870/stable-twrp-3-2-1-j701f-t3742401
Credits:
@GhaithSYR for TWRP
@JaskaranSM and @@ananjaser1211 for Helios Kernel
@topjonhuw For Magisk
@lzzy12 for TWRP 3.2.1 Image
Also hit Thanks to respective threads linked above.
PM for Queries. Bit busy so posting it short, will update Detailed guide soon.
NOTE:
for OEM Unlock option enabled ( I used miraclebox EE activation, but not sure it got it on with it or it was by default, See reference guide)
Reference Guide, credits @Jukmisael : https://forum.xda-developers.com/ga...e-nxt-exynos-7870/install-twrp-j7nxt-t3974337
RECOVERING:
If you mess up and device is not working there is very easy way to get stock rom back. No need to panic at all.
Go to Sammobile.com get your Stock Rom.
Flash via Odin.
Done.

xperia ray said:
I've seen people here struggling with rooting j701f a.k.a J7 Nxt. I always got bootloop when installed TWRP and flashed Magisk, so little trick here is installing custom kernel; i am using Helios kernel 3.1 and it works perfectly. (Select wifi driver new with android pie when installing, first option).
Technically it should work on J7 Nxt /Neo /Core. Tested in J7 Nxt 701F, DDU6CSF1 Stock firmware OneUI 1.1 Indian Variant.
Procedure from start.
Given:
You're running on Pie.
OEM Unlock option enabled in developers Option.
Get Odin - https://odindownload.com/SamsungOdin/
Get TWRP - https://forum.xda-developers.com/ga...-j701f-core-nxt-exynos-7870/recovery-t3693009
Get Helios Kernel https://forum.xda-developers.com/ga...70/kernel-heliospie-kernel-3-1-j701x-t3941438
Start Odin and untick auto reboot option.
Select Boot.tar file in BL
Select Recovery.tar file in AP
Flash.
Unplug phone.
Remove battery.
Put it back.
Hold Volume up (+) then Home then Power button for 20-30seconds
Press Power button.
Press power button again.
You'll see TWRP recovery 3.1.1 , say thanks to GhaithSYR
Swipe to modify system.
Format data, Type yes (Beware it'll erase all data and factory reset except SD card.
Flash Kernel.
Reboot.
Update Magisk.
You can update your TWRP to 3.2.1 : https://forum.xda-developers.com/ga...-exynos-7870/stable-twrp-3-2-1-j701f-t3742401
Credits:
@GhaithSYR for TWRP
@JaskaranSM and @@ananjaser1211 for Helios Kernel
@topjonhuw For Magisk
@lzzy12 for TWRP 3.2.1 Image
Also hit Thanks to respective threads linked above.
PM for Queries. Bit busy so posting it short, will update Detailed guide soon.
NOTE:
for OEM Unlock option enabled ( I used miraclebox EE activation, but not sure it got it on with it or it was by default, See reference guide)
Reference Guide, credits @Jukmisael : https://forum.xda-developers.com/ga...e-nxt-exynos-7870/install-twrp-j7nxt-t3974337
RECOVERING:
If you mess up and device is not working there is very easy way to get stock rom back. No need to panic at all.
Go to Sammobile.com get your Stock Rom.
Flash via Odin.
Done.
Click to expand...
Click to collapse
I have a Samsung J7 CORE sm-j701f and on Pie version
my problem is after flashing twrp via odin "only official binaries are allowed to be flashed(recovery)" pop up in download mode.
my phone is OEM unlocked and can u help me fix this?, I cant root my phone if i cant fix this thing. Help will be appreciated, thank you.

Anlle said:
I have a Samsung J7 CORE sm-j701f and on Pie version
my problem is after flashing twrp via odin "only official binaries are allowed to be flashed(recovery)" pop up in download mode.
my phone is OEM unlocked and can u help me fix this?, I cant root my phone if i cant fix this thing. Help will be appreciated, thank you.
Click to expand...
Click to collapse
It means phone is not OEM unlocked flash older firmware and check. It's been long i rooted this phone, currently not using it I don't remember exactly what I did to get rid of this msg - unofficial binary.
But i remember changing date back to few months and enabling allow OEM unlock.
There is another guide of rooting including a tool phoenix something. Search Xda it exits here. All I can say is keep fighting i tried a lot time and at the end it worked, I even used custom kernel Helios and rooted properly with magisk.

xperia ray said:
It means phone is not OEM unlocked flash older firmware and check. It's been long i rooted this phone, currently not using it I don't remember exactly what I did to get rid of this msg - unofficial binary.
But i remember changing date back to few months and enabling allow OEM unlock.
There is another guide of rooting including a tool phoenix something. Search Xda it exits here. All I can say is keep fighting i tried a lot time and at the end it worked, I even used custom kernel Helios and rooted properly with magisk.
Click to expand...
Click to collapse
Thank you, I will try until my phone is rooted. best of luck of me hehehe.

Anlle said:
Thank you, I will try until my phone is rooted. best of luck of me hehehe.
Click to expand...
Click to collapse
NOTE:
for OEM Unlock option enabled ( I used miraclebox EE activation, but not sure it got it on with it or it was by default, See reference guide)
Reference Guide, credits @Jukmisael : https://forum.xda-developers.com/gal...j7nxt-t3974337

xperia ray said:
NOTE:
for OEM Unlock option enabled ( I used miraclebox EE activation, but not sure it got it on with it or it was by default, See reference guide)
Reference Guide, credits @Jukmisael : https://forum.xda-developers.com/ga...e-nxt-exynos-7870/install-twrp-j7nxt-t3974337
Click to expand...
Click to collapse
Thanks
According to the photos shown, you need to use MiracleBox, as it is prenormal
Try using this tutorial

How do I downgrade my redmi 7a miui 12.5.2.0 to miui 10?

I was planning to downgrade my redmi 7a to miui 10 because of lags delay etc, but when I choose update package and use the miui 10 rom it says "Couldn't verify update package. Update via usb instead." I'm afraid to do it on pc because I dont know the procedure and I don't want my phone to be bricked.

nenekdx said:
I was planning to downgrade my redmi 7a to miui 10 because of lags delay etc, but when I choose update package and use the miui 10 rom it says "Couldn't verify update package. Update via usb instead." I'm afraid to do it on pc because I dont know the procedure and I don't want my phone to be bricked.
Click to expand...
Click to collapse
Stock recovery won't accept this downgrade. The only way, is unlocking bootloader, and flashing the ROM zip through a custom recovery.

SubwayChamp said:
Stock recovery won't accept this downgrade. The only way, is unlocking bootloader, and flashing the ROM zip through a custom recovery.
Click to expand...
Click to collapse
Yeah, what you can do if you want is to
1: unlock bootloader (pretty simple if you follow the official instructions from Redmi)
2: install MiFlashTool (explained here: https://www.getdroidtips.com/guide-.../#How-to-Flash-Xiaomi-Firmware-using-Fastboot)
3: download the version you want from mifirm.net
4: flash your phone (you can choose to lock it or to unlock it)
5: go about your day happy everything worked out and you could get an answer 3 days late hahaha

golobolo said:
Yeah, what you can do if you want is to
1: unlock bootloader (pretty simple if you follow the official instructions from Redmi)
2: install MiFlashTool (explained here: https://www.getdroidtips.com/guide-.../#How-to-Flash-Xiaomi-Firmware-using-Fastboot)
3: download the version you want from mifirm.net
4: flash your phone (you can choose to lock it or to unlock it)
5: go about your day happy everything worked out and you could get an answer 3 days late hahaha
Click to expand...
Click to collapse
You did bad quote, I didn't want to make any flashing round.
Thanks but I know the process.
I just responded to a user about the specific issue about flashing a stock recovery ROM lower than the current, using a stock recovery, and my answer still fits for them.