Hi, i discovered a fix for this problem and made 2 flashable zips. Follow the steps.
If you have 4.0.2 or older just do steps 3 and 4.
1- Download the 4.0.2 firmware and the firmware of your current version:
OP3T files:
Oxygen 4.1.1:https://drive.google.com/open?id=0Bzko1towAti5XzNCRVVwUVYzRms
Oxygen 4.1.0:[url]https://drive.google.com/open?id=0Bzko1towAti5WW1rUThrb3lHUWs[/URL]
Oxygen open beta 3:[url]https://drive.google.com/open?id=0Bzko1towAti5d3BtOEtXdk9hVTA[/URL]
Oxygen 4.0.3:[url]https://drive.google.com/open?id=0Bzko1towAti5NzU5b3lDaEZfZ3M[/URL]
Oxygen 4.0.2:[url]https://drive.google.com/open?id=0Bzko1towAti5NGVsTUtfd2VUY2M[/URL]
OP3 files:
Oxygen 4.1.1:https://drive.google.com/open?id=0Bzko1towAti5eXpXOXRUcXRoeXc
Oxygen 4.1.0:[url]https://drive.google.com/open?id=0Bzko1towAti5WEtoYXd0NW1qUVk[/URL]
Oxygen open beta 12:[url]https://drive.google.com/open?id=0Bzko1towAti5aVVvNkIwTURjaE0[/URL]
Oxygen 4.0.3:[url]https://drive.google.com/open?id=0Bzko1towAti5SW5FdE1EczQybUU[/URL]
Oxygen 4.0.2:[url]https://drive.google.com/open?id=0Bzko1towAti5eDFmZzZPQVI2OXc[/URL]
2- Flash in TWRP the 4.0.2 firmware zip.
3- Reboot to bootloader and connect your phone to the pc.
4- Use this commands:
fastboot oem disable_dm_verity
fastboot oem enable_dm_verity
5- Reboot to recovery
6- Flash in TWRP the firmware of your current OOS version.
And you are done! :highfive:
Migdilu said:
Hi, i discovered a fix for this problem and made 2 flashable zips. Follow the steps.
1- Download the two files:
[url]https://drive.google.com/open?id=0Bzko1towAti5Uld0cWp1YWdfLXM[/URL]
[url]https://drive.google.com/file/d/0Bzko1towAti5LXFUbEJwYUFFbGc/view?usp=sharing[/URL]
2- Flash in TWRP the 4.0.2 firmware zip.
3- Reboot to bootloader.
4- Use this commands:
fastboot oem disable_dm_verity
fastboot oem enable_dm_verity
5- Reboot to recovery
6- Flash in TWRP 4.0.3 firmware zip.
And you are done! :highfive:
Click to expand...
Click to collapse
thanks for the fix
but 4.0.3 firmware says 3.5.3 firmware for 3t.Is that a updater script error??
kunal1540 said:
thanks for the fix
but 4.0.3 firmware says 3.5.3 firmware for 3t.Is that a updater script error??
Click to expand...
Click to collapse
Exactly, I'm uploading a new file correcting that. But don't worry, you flashed the 4.0.3 firmware. Thanks for the report!
Worked for me as well. Thank you.
thanks worked at my 1+3T.
working for me also on A3010.
thanks.
Please add
Code:
getprop("ro.display.series") == "OnePlus 3T" || abort("E3004: This package is for \"OnePlus 3T\" devices; this is a \"" + getprop("ro.display.series") + "\".");
as first line in your updater-script which prevents bricked devices.
Nice to see it's working!
sniperle said:
Please add
as first line in your updater-script which prevents bricked devices.
Click to expand...
Click to collapse
I'll check that later, thanks!
I just flashed 4.0.2 firmware zip.
Then choose Reboot to bootloader.
Phone just goes off.
Now wont power at all. Even if I plug in to power it up, the light doesnt lit up.
It's comepletly dead now
Oh, god, I just killed my phone beacouse that verity thing! I should leave it alone.
done it with 4.0.2 rooted and without succes
Is this only for OnePlus 3T?
I fuc..d my device beacouse I flashed this on my OnePlus 3?
I didn't look the topic name before. And in post it didnt stated taht its for OP3T only.
nitramcek said:
I just flashed 4.0.2 firmware zip.
Then choose Reboot to bootloader.
Phone just goes off.
Now wont power at all. Even if I plug in to power it up, the light doesnt lit up.
It's comepletly dead now
Oh, god, I just killed my phone beacouse that verity thing! I should leave it alone.
Click to expand...
Click to collapse
You did something wrong. Do you have 3 or 3t?
nitramcek said:
Is this only for OnePlus 3T?
I fuc..d my device beacouse I flashed this on my OnePlus 3?
I didn't look the topic name before. And in post it didnt stated taht its for OP3T only.
Click to expand...
Click to collapse
Its on oneplus 3t forum.. Can you boot to booloader?
madmax28011980 said:
done it with 4.0.2 rooted and without succes
Click to expand...
Click to collapse
Just do step 3 and 4 if you are on 4.0.2 or older. Now flash 4.0.2 firmware and then do 3 and 4 and you are done.
off topic I know, but can someone explain why people are getting this error? If you root correctly you don't this error.
Migdilu said:
Its on oneplus 3t forum.. Can you boot to booloader?
Click to expand...
Click to collapse
No. It's compleatly dead.
I got in this forum thru link on other forum about DM-verity and didnt really look on what forum I landed until i bricked device.
nitramcek said:
No. It's compleatly dead.
I got in this forum thru link on other forum about DM-verity and didnt really look on what forum I landed until i bricked device.
Click to expand...
Click to collapse
I'm sorry. Make a thread on oneplus 3 forum explaining that you accidentally flashed 3T firmware, maybe someone has a solution for this.
EDIT: Take a look at the unbrick guide: https://forum.xda-developers.com/oneplus-3/how-to/guide-mega-unbrick-guide-hard-bricked-t3405700
Snappiestjack said:
off topic I know, but can someone explain why people are getting this error? If you root correctly you don't this error.
Click to expand...
Click to collapse
Not sure what/if I've done wrong TBH... still, I had the message
I reflashed op3t recovery i then reflashed oxygen 4.0.2 but still getting the error then i flashed twrp 3. and then the su after that i have flashed your 4.0.2. Img and gave the fastboot commands still the error is there maybe i do something wrong! The weird is that when i enter twrp it asks me for a pattern... Should i remove security locks from oxygen 4.0.2 and try again! Anyway.. Goodnight for now.
It's worked!!!
thx a lot!!!
Related
****** 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.
Is this equivalent to unofficial unlock or the official one?
BlueJeans said:
Is this equivalent to unofficial unlock or the official one?
Click to expand...
Click to collapse
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.
can miflash just flash the boot.img?
meangreenie said:
can miflash just flash the boot.img?
Click to expand...
Click to collapse
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.
Nice tutorial , this will be helpful to those people who are still stuck on 50% error ,Good work !
NVDX11 said:
Nice tutorial , this will be helpful to those people who are still stuck on 50% error ,Good work !
Click to expand...
Click to collapse
Hope that moderator is not here too.
vdbhb59 said:
Hope that moderator is not here too.
Click to expand...
Click to collapse
Haha , yep :laugh:
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.
kraatus90 said:
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.
Click to expand...
Click to collapse
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.
vdbhb59 said:
Step 6. Change:
a. "ro.secure=1" to "ro.secure=0"
b. "ro.adb.secure=1" to "ro.secure=0"
These enable OEM Unlock over Server and over Developer mode.
Click to expand...
Click to collapse
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.
abihary said:
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.
Click to expand...
Click to collapse
Thanks for pointing this out bro. My typing error.
It is ro.adb.secure
vdbhb59 said:
Thanks for pointing this out bro. My typing error.
It is ro.adb.secure
Click to expand...
Click to collapse
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.
abihary said:
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.
Click to expand...
Click to collapse
Any day welcome.
For kenzo or hennessy?
zenex01 said:
For kenzo or hennessy?
Click to expand...
Click to collapse
For kenzo
zenex01 said:
For kenzo or hennessy?
Click to expand...
Click to collapse
Kenzo and unfortunately currently limited to LP.
Searching for MM and N pattern to unlock.
What MIUI version you using? @vdbhb59
I tried with 7.3.2.0 after flashing then check bootloader but still locked. I skip step 6.
MiripRedmoon said:
What MIUI version you using? @vdbhb59
I tried with 7.3.2.0 after flashing then check bootloader but still locked. I skip step 6.
Click to expand...
Click to collapse
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.
vdbhb59 said:
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.
Click to expand...
Click to collapse
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?
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
HOW TO ROOT YOUR XIAOMI REDMI NOTE 4X MTK aka NIKEL
DISCLAIMER:
There might be more than 1 way to root this phone, this tutorial is based off of the procedure I used to root my phone. For your device's safety do not mix resources (downloads) from other threads with this thread. I first rooted when my phone was on MIUI 8.2 and Android 6.0.1 (It still works on higher versions of the software). Before continuing with the procedure, you are responsible for your phone and what you do to it, this thread worked for me but doesn't necessarily mean it will work for you as well if you don't follow the steps correctly or use different files. Nonetheless, I take no responsibility for what happens to your phone if anything goes wrong.
Requirements:Unlocked Bootloader (Click here for the procedure)
Custom Recovery "TWRP" (Click here to download)
ABD Drivers (Click here to download)
SuperSU (Click here to download)
(Download the latest .zip file called "Recovery Flashable" NOT any APK's)
Procedure:
1) Unlock your Bootloader (skip if already unlocked)
2) Download all the required files
3) Install the ADB Drivers
4) Move the downloaded SuperSU zip file to your phone's SD CARD or internal memory
5) Open the .bat file inside the NIKEL FLASHKIT folder
- Οnce the batch opens select the first option (FLASH ZCX-TWRP 3.0.2-X FOR Redmi Note 4 MTK)
6) Enable USB Debugging
- Enable developer options by clicking couple of times on the MIUI Version (Settings > About Phone)
- After you've enabled the developer options, go to additional settings and find "developer options"
- Enable USB Debugging
7) Connect your phone to your PC
8) Follow the instructions being printed on the NIKEL FLASHKIT batch file you've previously opened
9) After your phone has entered TWRP go to Install and find the .zip of SuperSU
10) Select the file then swipe to install and reboot, DONE!
norskaa said:
Hello everyone, I recently purchased a Xiaomi Redmi Note 4X and I'd like to root it,
Android Version : 6.0 MRA58K
MIUI Version : MIUI Global 8.2 | Stable 82.1.0 (MBFMIDL)
Is there currently any possible / safe way to root this phone? If so, please be kind and link me to a thread. Thanks in advance! <3
Click to expand...
Click to collapse
Well, you need an unlocked bootloader inorder to get root access.
Go apply for permissions if you haven't applied yet!
sachin n said:
Well, you need an unlocked bootloader inorder to get root access.
Go apply for permissions if you haven't applied yet!
Click to expand...
Click to collapse
Hello, thanks for your reply. I've just requested a bootloader unlock. What do I do after that in order to root my phone?
norskaa said:
Hello, thanks for your reply. I've just requested a bootloader unlock. What do I do after that in order to root my phone?
Click to expand...
Click to collapse
Flash the custom recovery (*.img) through fastboot command. For RN4 MTK there's limited custom recovery available, but you may consider trying Cofface TWRP or ZCX TWRP. After that you can install SuperSU or Magisk from custom recovery. There are plenty tutorials of flashing custom recovery and rooting device using TWRP in RN4 MTK device, search this forum or Google.
Devaz01 said:
Flash the custom recovery (*.img) through fastboot command. For RN4 MTK there's limited custom recovery available, but you may consider trying Cofface TWRP or ZCX TWRP. After that you can install SuperSU or Magisk from custom recovery. There are plenty tutorials of flashing custom recovery and rooting device using TWRP in RN4 MTK device, search this forum or Google.
Click to expand...
Click to collapse
Thanks for your reply, I've searched for video tutorials regarding flashing etc. All the videos I've found are about RN4 and NOT RN4X (which I own), does that make any difference?
norskaa said:
Thanks for your reply, I've searched for video tutorials regarding flashing etc. All the videos I've found are about RN4 and NOT RN4X (which I own), does that make any difference?
Click to expand...
Click to collapse
Doesn't matter sir, Xiaomi released 4/64GB MTK variant as wells, I assume you've the same.
Get TWRP for MTK variant of Redmi-note-4 and flash it. Nothing to worry.
sachin n said:
Doesn't matter sir, Xiaomi released 4/64GB MTK variant as wells, I assume you've the same.
Get TWRP for MTK variant of Redmi-note-4 and flash it. Nothing to worry.
Click to expand...
Click to collapse
Thank you so much for all your help! Ill post once I've tried it and successfully flashed my device, so other people with the same device could maybe find help here.
norskaa said:
Thank you so much for all your help! Ill post once I've tried it and successfully flashed my device, so other people with the same device could maybe find help here.
Click to expand...
Click to collapse
So, is it worked?
joppendaro said:
So, is it worked?
Click to expand...
Click to collapse
Yes
mr
mr flash twrp it is alive what mode fastboot
Thanks...
Sir.. Thanks a lot, I completed the whole process to install TWRP and root my redmi note 4x (Nikel) Ram 4GB internal 64 GB but I had to press volume down and power to force fastboot to come up then continue your step doubleclick the .bat file inside the NIKEL FLASHKIT folder...
MIUI Global 8.5 Stable 8530 (MBFMIED)
Yes, sometimes it works with the first try, other times you have to manually enter fast boot, and other you may need to reconnect your USB while in the process. It can be tricky at some point but it eventually works out
i tried few times and it is just not working for me. i dunno what n how... i unlocked bootloader from mi site. and nothing i try seems to work for me.
Kenannp said:
i tried few times and it is just not working for me. i dunno what n how... i unlocked bootloader from mi site. and nothing i try seems to work for me.
Click to expand...
Click to collapse
Could you give a more detailed explanation? Such as telling if you receive any errors , if the prerequisites installed correctly etc.?
norskaa said:
Could you give a more detailed explanation? Such as telling if you receive any errors , if the prerequisites installed correctly etc.?
Click to expand...
Click to collapse
nothing special. just when it says ur in twrp,nothing happens. i kept waiting even 20 mins n nothing.
repeated procedure few times and nothing.
but it worked,i changed usb cable and i went through,which is weird,usb works normal. copy/paste,charging...everything. but i didnt work for flasher.
however changed it and its all ok now
Kenannp said:
nothing special. just when it says ur in twrp,nothing happens. i kept waiting even 20 mins n nothing.
repeated procedure few times and nothing.
but it worked,i changed usb cable and i went through,which is weird,usb works normal. copy/paste,charging...everything. but i didnt work for flasher.
however changed it and its all ok now
Click to expand...
Click to collapse
Well at least the problem is solved now. Even though I think I mentioned in the thread that it might not work at all times and that you may have to disconnect the USB at some point. Anyways , good work
im glad that i found this thread.. sadly when i download the files.. its corrupted.. download several times.. same issue.. pls help.
xda111114 said:
im glad that i found this thread.. sadly when i download the files.. its corrupted.. download several times.. same issue.. pls help.
Click to expand...
Click to collapse
I've reuploaded the resources again. Here you go https://www.dropbox.com/s/52wb2dm1ludtfz8/Xiaomi Root.rar?dl=0
can someone help me. it's not booting into recovery mode. what should i do?
Does it still work in the latest version of MIUI 9.5.1.0? I have successfully installed TWRP but the .zip file might be outdated.
SUPPORTS 3/3T oreo
UPDATE:
Installation:
1.Flash TWRP latest
2.Flash latest magisk 14.5(beta)
Reboot
This process is difficult for some people. If you dont understand do not try this.
This is only for 8.0 oreo users
IM NOT RESPONSIBLE FOR OF YOUR DEVICE
Dont get panic nothing is going to happen
Credits:
@akhilnarang for Modified TWRP
INSTALLATION
IMPORTANT
Download the necessary zip file according to your device.
DO NOT TURN ON YOUR DEVICE UNTILL THE WHOLE PROCESS END.
If you twrp replaced by stock recovery in some steps just reflash the twrp and continue.
INSTALLATION:
STEP 1: Flash modified twrp and boot into recovery
STEP 2:Flash bootloader.zip and turn off your device by power button.
STEP 2.1: Boot into bootloade and connect to pc and type in adb cmd fastboot oem selinux permissive
FOR SOME ADB NOT ACCEPT ABOVE CMD AND THOSE FOLLOW THE GUIDE AND OTHERS JUST FLASH THE MODEM.ZIP AND MAGISK
STEP 3:Again boot into twrp and choose Advanced>sideload
STEP 4: Connect device to pc and open adb cmd and type abd sideload <file_path_modem.zip>
OP3 users skip step 5 and 6
STEP 5: Turn off your device by power button and reboot into bootloader
STEP 6: Flash boot.img fastboot flash boot boot.img
STEP 7: Finally reboot into recovery and magisk 14.3 and restart the device
For people dont understand this i uploaded a video of this tutorial kindly watch tell
DOWNLOAD SECTION:
OP3T: [url]https://drive.google.com/open?id=0B2rXSbosp3PfYmttd29MeEphdlk[/URL]
OP3:[url]https://drive.google.com/open?id=0B2r...[/URL]
Magisk 14.3(beta):[url]https://drive.google.com/open?id=0B2rXSbosp3PfWHQwaUxrQmNWZTA[/URL]
??
waiting.....
I like penguins.
magisk
да уже есть рабочий magisk для oneplus 3/3t '' oreo ":good:
reported
Explain why this works. And what modifications did you do to the boot image and bootlaoder image?
Yeah, we need some major details.. what exactly are we flashing here? I understand and it's a great guide if it works, but why does it work?
Lol, flash a boot.img without sources / knowing where the image come from ?
Nope, sorry.
casual_kikoo said:
Lol, flash a boot.img without sources / knowing where the image come from ?
Nope, sorry.
Click to expand...
Click to collapse
Exactly.. I'm guessing that's the basis for another person commenting they've reported the thread.. and why we're pushing for info. Nice if it works, but we need to see/know why it works.
jbarcus81 said:
Yeah, we need some major details.. what exactly are we flashing here? I understand and it's a great guide if it works, but why does it work?
Click to expand...
Click to collapse
Actually boot loader.zip from older OOS 3.2.0. And [boot.img is from OB16(THIS STEP IS ONLY FOR 3T)]
I just downgrade the boot loader.
ZacharyTheUmbreon said:
Explain why this works. And what modifications did you do to the boot image and bootlaoder image?
Click to expand...
Click to collapse
Boot img is stock oreo boot img for 3T only.
Bootloader is downgraded for those abd is not accepting the cmd fasboot oem selinux permissive.
sparky vicky said:
Boot img is stock oreo boot img for 3T only.
Bootloader is downgraded for those abd is not accepting the cmd fasboot oem selinux permissive.
Click to expand...
Click to collapse
But you forgot to say that when you set selinux permissive via fastboot you'll have a big freeze in system
jbarcus81 said:
Exactly.. I'm guessing that's the basis for another person commenting they've reported the thread.. and why we're pushing for info.
Click to expand...
Click to collapse
Not completely sure either, but I think the "reported" comment was due to the fact the thread was started (with title referencing Magisk in Oreo) with the only text in the first post saying "uploading". And it stayed that way for hours. It felt like an unnecessary and gratuitous tease.
Not 100% sure of the timing (I dropped offline) but I think the actual guide/instructions were not posted until (hours) after the "reported" post.
redpoint73 said:
Not completely sure either, but I think the "reported" comment was due to the fact the thread was started (with title referencing Magisk in Oreo) with the only text in the first post saying "uploading". And it stayed that way for hours. It felt like an unnecessary and gratuitous tease.
Not 100% sure of the timing (I dropped offline) but I think the actual guide/instructions were not posted until (hours) after the "reported" post.
Click to expand...
Click to collapse
Ah that could be ...
@topjohnwu is looking into it already: https://forum.xda-developers.com/on...vice-development/kernel-t3404970/post74192753
It works!
I flashed boot image and Modem.zip in twrp instead of using the terminal. Works great! Thank you.
Link for OP3 is broken - OP3:https://drive.google.com/open?id=0B2r...
Is this a working method to get magisk running as without magisk I'm hesitant to update.
wyrmeth said:
Is this a working method to get magisk running as without magisk I'm hesitant to update.
Click to expand...
Click to collapse
Wait a week and see if there's an update that doesn't require hacky workarounds.
Sent from my OnePlus3T using XDA Labs
How to Fix for WIERD LOCKSCREEN BUG on Android 8 and + custom roms
Many of them are facing this Bug after setting up Lockscreen, after few reboots we face System UI FC when entering Unlock code or pattern. This bug is faced when using Oreo, Pie and 10. And this bug is not present on Nougat.
Warning You will loss your all data including your device internal storage and i will be not responsible for any bricks if it happens on your device
Steps :-
Step 1 :- First of all Download MIUI global stable FASTBOOT ROM from the link http://bigota.d.miui.com/V10.2.1.0....XM_20190114.0000.00_6.0_global_8a48e54fe3.tgz
Step 2 :- download mi flashtool and install on your pc and extract fastboot_rom.tgz to a folder.
Step 3 :- Important to have Official Unlock, if you are Unofficially unlocked try this method :- https://forum.xda-developers.com/re...icially-unlock-bootloader-redmi-note-t4009799
Step 4 :- Now copy userdata.img and persist.img from images folder to minimal adb and fastboot folder.
Step 5 :- Now open command window and write following commands -
fastboot erase persist
fastboot erase userdata
fastboot flash persist persist.img
fastboot flash userdata userdata.img
Step 6 :- Now "clean" flash a custom rom 8 or above it. And check whether this bug is still present of not. If you still face the bug then once flash full MIUI through Mi flash tool and repeat Step 5. Note :- After repeating Step 5 don't boot back into MIUI. After performing Step 5 quickly flash twrp and wipe MIUI and flash Custom rom.
Step 7 :- The bug will be gone.
I have made it easy.
If you guys have any Problem regarding this Pm or contact me on telegram my account @sk_ik_27400
Enjoy Flashing:fingers-crossed:
How many days have you checked? Actually after clean flash it happens after roughly one and a half day
One more thing, I am not officially unlocked, I use twrp with locked bootloader, should I try this?
arnabbandopadhyay said:
How many days have you checked? Actually after clean flash it happens after roughly one and a half day
One more thing, I am not officially unlocked, I use twrp with locked bootloader, should I try this?
Click to expand...
Click to collapse
i can 100 percent guarantee it will work i tried about 2 to 3 weeks no issues.
if u are unofficially unlocked then then i would recommend unlock officially using china dev fastboot rom because for many global dev or stable doesnt work
by the way u can if u flash with unofficialy unlocked bootloader then u will be stuck simply do is first of all flash all clean and lock then but remember use that fastboot rom which is recommended for unlocking unofficially rather than latest. then unlock its bootloader then on bootloader flash same image files i have said in above thread simple. also kindly check thread for unnoficial unlocking. http://en.miui.com/thread-345728-1-1.html
tap thanks if helped
Ishaan Kaushal said:
i can 100 percent guarantee it will work i tried about 2 to 3 weeks no issues.
if u are unofficially unlocked then then i would recommend unlock officially using china dev fastboot rom because for many global dev or stable doesnt work
by the way u can if u flash with unofficialy unlocked bootloader then u will be stuck simply do is first of all flash all clean and lock then but remember use that fastboot rom which is recommended for unlocking unofficially rather than latest. then unlock its bootloader then on bootloader flash same image files i have said in above thread simple. also kindly check thread for unnoficial unlocking. http://en.miui.com/thread-345728-1-1.html
tap thanks if helped
Click to expand...
Click to collapse
after doing all, should I wipe all dalvik, system, data, cache, internl before flashing oreo rom?
arnabbandopadhyay said:
after doing all, should I wipe all dalvik, system, data, cache, internl before flashing oreo rom?
Click to expand...
Click to collapse
yes after flashing image files from bootloader simply flash twrp and wipe everything and flash any oreo rom but remember once check in twrp recent screen that there is no warning regarding encrption
It was probably magisk issue
nathanchance said:
also @D-m-x (and everyone else), please try this Magisk build (it can be installed in the modules tab in Magisk Manager)
https://transfer.sh/YVFdi/Magisk-v16.7-1674-.zip
It includes a commit that should fix all of the weird issues with Magisk like the PIN not being accepted after a reboot or the phone getting stuck at the Google logo with the progress bar. The root cause is services crashing during the boot chain and either causing deadlock or lack of functionality. It's entirely possible that a service crashed during boot and started causing issues.
Click to expand...
Click to collapse
Please refer to this post if you have magisk installed. thanks to @nathanchance
Ishaan Kaushal said:
yes after flashing image files from bootloader simply flash twrp and wipe everything and flash any oreo rom but remember once check in twrp recent screen that there is no warning regarding encrption
Click to expand...
Click to collapse
No decryption related message in twrp. I did all qnd will report you back after couple of days, whether is it fixed or not.
arnabbandopadhyay said:
No decryption related message in twrp. I did all qnd will report you back after couple of days, whether is it fixed or not.
Click to expand...
Click to collapse
ok :good:
Dims_Camper said:
Please refer to this post if you have magisk installed. thanks to @nathanchance
Click to expand...
Click to collapse
ok i tried all magisk version but i was fed up with this bug i dont know whether ur method works or not but i know this bug happens due to encryption on userdata. i dont think ur method will because magisk is universal and if problem is related to magisk then it should have happened with many devices not kenzo only
by the way thanks if ever faced again that bug i will try your method:laugh:
Ishaan Kaushal said:
ok :good:
Click to expand...
Click to collapse
On 1st reboot device asking " enter your password to start android", I tried to enter twrp, same thing happens, asking for password.
arnabbandopadhyay said:
On 1st reboot device asking " enter your password to start android", I tried to enter twrp, same thing happens, asking for password.
Click to expand...
Click to collapse
do u use telegram? if yes pm tag mentioned above in thread else send a screenshot of it
Ishaan Kaushal said:
do u use telegram? if yes pm tag mentioned above in thread else send a screenshot of it
Click to expand...
Click to collapse
I use but coudn't start my phone now, I am uploading pic
Ishaan Kaushal said:
ok i tried all magisk version but i was fed up with this bug i dont know whether ur method works or not but i know this bug happens due to encryption on userdata. i dont think ur method will because magisk is universal and if problem is related to magisk then it should have happened with many devices not kenzo only
by the way thanks if ever faced again that bug i will try your method:laugh:
Click to expand...
Click to collapse
i'm referring a post on pixel 2 thread, it's not only kenzo things apparently.
arnabbandopadhyay said:
I use but coudn't start my phone now, I am uploading pic
Click to expand...
Click to collapse
i am not able to see any screenshots attach again
Dims_Camper said:
i'm referring a post on pixel 2 thread, it's not only kenzo things apparently.
Click to expand...
Click to collapse
ok:good:
arnabbandopadhyay said:
I use but coudn't start my phone now, I am uploading pic
Click to expand...
Click to collapse
which rom u flashed?
before doing the method i suggested did u had your set a lockscreen password?
if yes simply enter that password and check else from boot loader enter followimg commands from cmd fastboot erase persist
the again flash persist using fastboot and then reboot to rom
Ishaan Kaushal said:
which rom u flashed?
before doing the method i suggested did u had your set a lockscreen password?
if yes simply enter that password and check else from boot loader enter followimg commands from cmd fastboot erase persist
the again flash persist using fastboot and then reboot to rom
Click to expand...
Click to collapse
I flashed cardinal. I never set any lockscreen password or pin, only a set a pattern.
I couldn't flash persist from fastboot, as I am unofficially unlocked, I need to flash only using mi flash in edl mode.
Unlocking bootloader officially is a harrassment, always getting "couldn't add your account: error 20075" something like that
arnabbandopadhyay said:
I flashed cardinal. I never set any lockscreen password or pin, only a set a pattern.
I couldn't flash persist from fastboot, as I am unofficially unlocked, I need to flash only using mi flash in edl mode.
Unlocking bootloader officially is a harrassment, always getting "couldn't add your account: error 20075" something like that
Click to expand...
Click to collapse
bro its better u contact me on telegram it will better to help Your there
arnabbandopadhyay said:
I use but coudn't start my phone now, I am uploading pic
Click to expand...
Click to collapse
Your device is encrypted!!!
Format data through recovery.
nilesh8343 said:
Your device is encrypted!!!
Format data through recovery.
Click to expand...
Click to collapse
doing this only produces lock screen bug