Database Users

my saga of ROOTING XIAOMI REDMI 3 / unlocking bootloader redmi 3 on MIUI8

UPDATE 27 DEC2016
-I received SYSTEM UPDATED NOTIFICATION ON 27 DEC2016 FOR MIUI8 on 5.1.1 (1.2GB), while my device was bootunlocked and ROOTED.
- after updating, twrp + root was gone
- so i flashed twrp IDO and flash supersu + lazyflasher and rebooted my device
---------------------
Recently I did something wild by buying Redmi3. For a die hard Sony Xperia fan over last many years it was something wild for me.
Immediately I felt the boundaries within MIUI8 where
- no app can be disabled
- no application dock / all app icons landing on launcher
- MIUI mediocre music with no equalizers
- bundled google and other duplicate apps (Miui galary + google photos) which and cannot be removed
however the features i enjoyed the most in MIUI8 particularly
- Dual APPs
- detailed dual sim control and renaming status bar icons/shape
- detailed control of memory optimization in developer options
- better memory optimization ( atleast for facebook and messenger which take gb/s of place to run )
i started my investigation immediately about rooting the Xiaomi Redmi devices running on MIUI8 (android5x) and the short and sweet version says
1. Unlocking Bootloader
2. flashing TWRP
3. flashing SuperSU
4. Flashing LazyFlasher
BOOTING in to SYSTEM.
however the above missing all the bleeding saga of work around you have to perform in order to reach the point where u actually install twrp.
UNLOCKING REDMI3 (REDMI DEVICES) ​
prerequisite~~~
MAKE BACKUP OF YOUR DEVICE!!!!!!!!!!!!
DO IT ON YOUR OWN RISK
I AM SHARING MY OWN EXPERIENCE HERE!
ONLY ONE DEVICE SHOULD BE LINKED WITH ONE MI ACCOUNT ( what i have read ov
1. once you start using REDMI, you must create MIUI account in your device- verified by your Mobile Sim Career / valid email and having legitimate details about you. the more valid details you give to your MI Account, the chances of unlocking bootloader are more. I even had to connect it with my only facebook account!
https://drive.google.com/open?id=0B31ivZaiUAGMWTYxX3ZXLUxrb2c
2. for REDMI3 download the DEVELOPER ROM from http://en.miui.com/download-298.html and put it in the mobile's SD card or internal memory.
on Redmi3 goto UPDATER APP (in folder TOOLS) and click the 3 dots top/right and click CHOOSE UPDATE PACKAGE and install the DEVELOPER GLOBAL or DEVELOPER CHINESE ROM MIUI8 over stableROM
https://drive.google.com/open?id=0B31ivZaiUAGMa3lPUWVnWnVXdXc
https://drive.google.com/open?id=0B31ivZaiUAGMNXBCLWdnWHpYbXc
it may give you warning like its older version and all data will be wiped. Proceed anyways. the device will BOOT an install DEVELOPER ROM. This process took 1 hour and i had Developer ROM in my REDMI3. after booting i logged in to my MI ACCOUNT. (DATA WIFI enabled)
3. NOW~~~~ goto http://en.miui.com/unlock/ and fill the form , asking your MI account details and VALID reason why you want to unlock your redmi device. Once done you will be asked to wait for SMS by XIAOMI. it may take 10 to 12 days. at this point if anything about you account is fake or you change your SIM CARD/number in you REDMI3 / Redmi. your bootloader request will be denied. I recieved my SMS on day5
https://drive.google.com/open?id=0B31ivZaiUAGMVnMzb3RKSEtTdkU
3. once you get the sms, download MIunlock TOOL from
http://en.miui.com/forum.php?mod=at...kMjVifDE0Nzk5MDA2OTJ8NTQyOTQ4MzM5fDQxODQyOQ==
4. now here is the Tricky part! which i found after so many FAIL TO UNLOCK device errors is that you must be in CHINA/ TAIWAN / SINGAPORE inorder to run you MIUNLOCK TOOL. for this purpose i used https://www.tunnelbear.com/ application and location SINGAPORE
5. unzip miunlock tool and run the exe file. LOGIN using your MI ACCOUNT
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
account will be validated for unlocking permission
since you recieved SMS, MIUNLOCK will ask you to CONNECT YOUR DEVICE FASTBOOT MODE / remember redmi goes to fastboot mode when POWER and volume down keys pressed and hold simultaneously for few second with jerk.
if everything goes right , the SMS + SINGAPORE LOCATION by TunnelBear; Miunlock tool will finally UNLOCK your device (WHEW)!!!!!!!!
INSTALLING TWRP / SUPERSU / LAZYFLASHER (ROOTING REDMI)​
YOU HAVE NOW UNLOCKED device RUNNING ON global or chinese DEVELOPER ROM MIUI8, (you can check the unlock status from about device section)
now
1. Download the stable MIUI8 from http://en.miui.com/download-298.html, and flash it with UPDATER TOOL the way you installed developer rom (as explained above)
2. once stable rom is flashed, boot your device and started using it by logging in to MI Account, google accounts etc. (again whole process takes 1 hr)
3. download TWRP IDO https://drive.google.com/open?id=0B31ivZaiUAGMVjZ6ekU4TEVveTA
4. download lazy flasher and supersu (as attached) and put it in the sdcard or internal memory!
5. switch-off device (REDMI3) and boot it in FASTBOOT mode by holding VOLdown+power keys.
FLASH TWRP by adb commands. please see this video! its EXTREMELY HELPFUL!! follow it by heart!
https://www.youtube.com/watch?v=G_P7Qd3kpAI
6. once you boot twrp as system readonly! make BACKUP in sdcard or internal memory!
7. mount system! and flash both zipfiles in sequence (A) superSU & (B) LAZYFLASHER ( lazyflasher disables dm-varity and prevent you from bootloops)
8. REBOOT in to SYSTEM! the first boot may take some time!
CONGRATULATIONS you have ROOTED REDMI3 / XIAOMI
warning
1. you will no receive any updates since system is modified by twrp hence you have to FLASH any updates in fastboot mode by downloading fastboot version of MIUI in future using MIFLASH TOOL / or XDA FLASHER
https://drive.google.com/open?id=0B31ivZaiUAGMdFBSYWhoMnJzakk
---any future flashing will void rooting and twrp, so you have to install twrp/supersu/lazyflasher after every update.
2. I skipped the EDL mode part! XIAOMI devices are highly unstable and you can brick them VERY EASLY!!!!
3. I skipped the part where you can replace twrp.img with kernel.img by naming it kernel.img in FASTBOOT ROM version using 7-zip. again you can brick your device very easly!
HOWEVER
4. if your boot locking request has been denied by MIUI team,,,, EDL is your LAST OPTION

First of all, you're in wrong forum. This kind of thread should be on General section.
Second,
Unlocking process could be done in any region (I don't receive my SMS verification but my request is accepted). I'm in Indonesia and I don't use VPN and unlocking works. :good:
Sent from my ASUS_Z00A using XDA Labs

krasCGQ said:
First of all, you're in wrong forum. This kind of thread should be on General section.
Second,
Unlocking process could be done in any region (I don't receive my SMS verification but my request is accepted). I'm in Indonesia and I don't use VPN and unlocking works. :good:
Sent from my ASUS_Z00A using XDA Labs
Click to expand...
Click to collapse
sorry for posting in the wrong section
admins, please move the post to the right one
I am in kuwait, and i constantly got failure unless i tried region Singapore! My guess malaysia would also be acceptable ! however in my region its not getting unlocked

YasuHamed said:
I am in kuwait, and i constantly got failure unless i tried region Singapore! My guess malaysia would also be acceptable ! however in my region its not getting unlocked
Click to expand...
Click to collapse
If I remember: Xiaomi phones in Asia (excluding China) are mostly released in India, Indonesia, Singapore, Malaysia, and Taiwan.
That's why the unlocking process always fails on your case.
Sent from my ASUS_Z00A using XDA Labs

krasCGQ said:
If I remember: Xiaomi phones in Asia (excluding China) are mostly released in India, Indonesia, Singapore, Malaysia, and Taiwan.
That's why the unlocking process always fails on your case.
Sent from my ASUS_Z00A using XDA Labs
Click to expand...
Click to collapse
true!
i have read, people from other countries and locations cannot unlock Xiaomi

This worked for me. The twrp rooting part.
Flashed twrp, left it read only, then flashed the newest superSU (2.79) and then lazy flasher zip.
All good here! And I already had dm-verity issues and had to flash stock rom again. (30 minutes after I got the phone. Didn't read well enough first time around. Lol)
Thanks! :good:

Whoa, Darth is here! xD
Congrats on having your (new) device rooted. Hope you could enjoy the phone...
Sent from my Redmi 3 using XDA Labs

Darth said:
This worked for me. The twrp rooting part.
Flashed twrp, left it read only, then flashed the newest superSU (2.79) and then lazy flasher zip.
All good here! And I already had dm-verity issues and had to flash stock rom again. (30 minutes after I got the phone. Didn't read well enough first time around. Lol)
Thanks! :good:
Click to expand...
Click to collapse
oh you are welcome sir
i am glad to be help

2. for REDMI3 download the DEVELOPER ROM from http://en.miui.com/download-298.html and put it in the mobile's SD card or internal memory.
on Redmi3 goto UPDATER APP (in folder TOOLS) and click the 3 dots top/right and click CHOOSE UPDATE PACKAGE and install the DEVELOPER GLOBAL or DEVELOPER CHINESE ROM MIUI8 over stableROM
https://drive.google.com/open?id=0B3...3lPUWVnWnVXdXc
https://drive.google.com/open?id=0B3...XBCLWdnWHpYbXc
Click to expand...
Click to collapse
Hi op, i tap on the link and it brings me to the rom download page but it was for redmi 3 prime and i'm using redmi 3 (snapdragon version) Can this guide still work on my phone? or i just need to simply download dev rom for my phone's version? And i heard that Global rom doesn't allow for root activation so which rom should i dowload? i prefer global though

LoliIsMe said:
Hi op, i tap on the link and it brings me to the rom download page but it was for redmi 3 prime and i'm using redmi 3 (snapdragon version) Can this guide still work on my phone? or i just need to simply download dev rom for my phone's version? And i heard that Global rom doesn't allow for root activation so which rom should i dowload? i prefer global though
Click to expand...
Click to collapse
1) All Redmi 3 variants are Snapdragon, with difference in RAM, eMMC, and fingerprint sensor availability.
2) Who knows?
3) You can just flash SuperSU or Magisk.
Sent from my Redmi 3 using XDA Labs

krasCGQ said:
1) All Redmi 3 variants are Snapdragon, with difference in RAM, eMMC, and fingerprint sensor availability.
2) Who knows?
3) You can just flash SuperSU or Magisk.
Sent from my Redmi 3 using XDA Labs
Click to expand...
Click to collapse
So I can just flash SU from the stock recovery to gain root access?
Sorry for my ignorance though:crying:

LoliIsMe said:
So I can just flash SU from the stock recovery to gain root access?
Sorry for my ignorance though:crying:
Click to expand...
Click to collapse
With custom recovery of course.
Sent from my Redmi 3 using XDA Labs

krasCGQ said:
With custom recovery of course.
Sent from my Redmi 3 using XDA Labs
Click to expand...
Click to collapse
Now i'm stuck at flashing twrp part,
1. "adb reboot bootoader" the result was "bootloader is disabled"
so i entered into fastboot manually, plug in the cable and check with "fastboot devices" and it was connected.
2. i ran "fastboot flash recovery (and the file here)" it failed "data transfer failure (or something like that)<unknown>"
and i'm sure my bootloader is unlocked correctly. do i need the fastboot mode enabled in the developer option?

LoliIsMe said:
2. i ran "fastboot flash recovery (and the file here)" it failed "data transfer failure (or something like that)<unknown>"
and i'm sure my bootloader is unlocked correctly. do i need the fastboot mode enabled in the developer option?
Click to expand...
Click to collapse
Yeah, try to enable that.
Sent from my Redmi 3 using XDA Labs

krasCGQ said:
Yeah, try to enable that.
Sent from my Redmi 3 using XDA Labs
Click to expand...
Click to collapse
result still the same, no luck, but i found something
the daemon keeps shutdown like every 8 seconds, after waiting for a while and enter "adb devices" it's going to say daemon not running...
update:
i restarted my pc and now everything works fine silly pc thx man

[GUIDE][KENZO/KATE] Install LineageOS with locked bootloader

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Hello guys,
This is my first guide and it is focused on people who just bought their Redmi Note 3 (KENZO/KATE) and having problems with officially unlocking their bootloader. (stuck @ 50% like me)
If you don't want to wait on stock MiUi until you can officially unlock your bootloader (because you need to wait additional ~2 weeks after you received permission from Xiaomi until their servers updated) or you want that extra security layer with locked bootloader this guide is made for you!
Since official LineageOS 14.1 just released, i thought some of you guys are interested in this awesome, easy and safe method.
To save you time searching hours and hours through this forum i made this quick summery.
Downloads :
MiUi 8 Global Developer ROM 6.11.3: KENZO or KATE
ZCX TWRP (direct downloadlink: click here)
Mi Flash 6.8.30
Latest firmware (choose correct device)
[ROM][OFFICIAL][7.1.1][kenzo] LineageOS 14.1 by The_strix
Open GApps - ARM64 - Android 7.1
Instructions : (follow them carefully!)
Extract MiUi 8 Global Developer ROM and replace recovery.img (in images folder) with ZCX TWRP's recovery.img
Flash using Mi Flash (in EDL mode) and check clean_all
After finished flashing process unplug and press [volume up]+[power] until Mi logo shows up then release buttons and it boots to TWRP (change TWRP language from chinese to english: click here)
Reboot to system (if you get prompt: "Disable stock recovery replace now" > just swipe to allow disable)
Boot to MIUI and complete initial setup (important step - don't skip! first boot will take around 10 minutes)
-----------------------------------------------
Shutdown device and boot to TWRP again
(optinal) Backup every partition and safe this backup on an external device
Wipe > Advanced Wipe > check Dalvik / ART Cache, System, Data, Internal Storage, Cache > Swipe to Wipe
Flash Latest firmware, LineageOS 14.1 and GApps (ARM64, Android 7.1)
Reboot to system and you're DONE!!
updated method (works with newest MIUI version) :
There is a new updated method by kuan improved by @N.G. and @razr_96. Thanks for mentioning.
Advantages:
no need to download full MIUI fastboot rom
much faster method, only takes seconds to flash (instead of 4 minutes and you don't have to complete initial MIUI setup which also takes around 5 minutes)
this method is better if you want to stay on MIUI and just want to root
you can stay on your current MIUI version (even 7.1.19 which is currently the latest) and don't have to wipe your data
Disadvantages:
this doesn't clean everything, i would recommend to clean everything if you want to install a custom rom
you have to download a file i can not verify
Instructions : (follow them carefully!)
(optinal) Backup your current MIUI data (Settings > Additional settings > Backup & reset > Local backups > Back up) and copy it to an external media
Download and extract: Kenzo or Kate
(optinal) Replace included ZCX TWRP recovery.img (in images folder) with your preferred TWRP recovery.img
Flash using Mi Flash 20160401 (in EDL mode) and check flash all except data and storage (not clean_all like in the method mentioned above)
BE AWARE: This MiFlash version is different to the MiFlash version mentioned above! This version does only support 64 bit systems and you need atleast Windows 7!
After finished flashing process unplug and press [volume up]+[power] until Mi logo shows up then release buttons and it boots to TWRP (change TWRP language from chinese to english: click here)
Reboot to system
Video tutorial: https://www.youtube.com/watch?v=rCONN1_IPuU
Troubleshooting :
[APP][ROOT][7.1.1]QuickSettings Flashlight fix for all nougat roms
If something goes wrong, start over again and follow my guide step by step.
This guide only works with MiUi 8 Global Developer ROM 6.11.3 or lower.
Put MIUI 8 Global Developer ROM in "C:\ROM" - MiFlash tends to have problems if there are any spaces in folder names.
If you flashed something wrong and have no simcard signal anymore or no IMEI look here for help: EFS Recovery Guide
If you didn't remove your passcode before you did a backuprestore using TWRP:
TWRP > Advanced > Filemanager > /data/system > delete locksettings.db
Issues with locked bootloader :
none
(advanced technique) Higher security with locked bootloader:
Thanks @LeoYL !
A little addition: If you want a even higher level of security, which is nobody except you can flash packages in recovery, you can create a recovery with limited functions and forced signature verification, with your own keys embedded in that recovery.
This is just like the original status of nearly all Android devices when they are shipped: only signed OTA update packages can be applied via recovery. Normally, the packages are signed by OEMs; however, you can become the "OEM" by creating your own private key, which is used during package signing.
Just follow these guides to create a recovery with your own keys. I use CM 13.0 recovery, since it only has basic recovery features, including installing a ZIP file, factory reset, and it has mandatory ZIP signature verification.
http://mjg59.dreamwidth.org/31765.html
https://forum.xda-developers.com/showpost.php?p=62796459&postcount=2
The reason why I don't use TWRP is that it allows update packages with any signature. Although you can enforce signature verification, it can also be switched off in TWRP settings.
Now you get a recovery which only accepts ZIP packages that are signed with your own private key. The only downside is you need to sign every package you want to flash each time. But this also means that if a stranger picks your lost phone up, they can't tamper your phone's OS. If the "reset protection" feature works with locked bootloader on our Redmi Note 3, the only distance between our phones' security and Google devices' is edl mode and encryption.
Wanna try other custom roms?
Just follow this guide and you can flash every other nougat customrom as well like:
[ROM]AOSIP 5.5 for Redmi Note 3(Kenzo)[OFFICIAL BUILDS]
[ROM][Nightlies][android-7.1.1_r6]ResurrectionRemix 5.8.0[OFFICIAL][VoLTE]
[ROM][OFFICIAL][Weekly][7.1.1_R13][Slim 7 For Kenzo]
[ROM] ► [7.1.1 ► N4F26M] ► [OTA][OMS][Goodix] ► Nitrogen OS
credits :
@The_strix: For his development work
@Psy_man: For extracting nougat firmware
@kuan: For creating this method (french forum)
@Tobsucht TM: For answering my questions
If this guide was helpful to you, don't forget to press the Thanks! button :good:
Enjoy your new custom rom!
khajiit

This method also works with Kenzo, obviously using the Kenzo miui rom and firmware instead.

razr96 said:
This method also works with Kenzo, obviously using the Kenzo miui rom instead as well as not flashing the kate firmware.
Click to expand...
Click to collapse
That's right! Thanks for pointing it out.

Redmi Note 3 SE _ Kate
Thanks bro worked on my Kate :good:

How to successfully unlock bootloader(official way) worked for me
https://forum.xda-developers.com/redmi-note-3/how-to/successfully-officially-unlocked-redmi-t3543150
Just use that Miflash : rootjunkysdl.com/files/Redmi%20Note%203%20Pro%20Kenzo/Firmware%20Unbrick/MiFlash.zip
Because that one in thread not working properly.

armo1111 said:
https://forum.xda-developers.com/redmi-note-3/how-to/successfully-officially-unlocked-redmi-t3543150
Just use that Miflash : rootjunkysdl.com/files/Redmi%20Note%203%20Pro%20Kenzo/Firmware%20Unbrick/MiFlash.zip
Because that one in thread not working properly.
Click to expand...
Click to collapse
The guide you linked is not working for me, thats why i made this guide which works 100%.

I tried this with the Global developer ROM for my kenzo.
When I try to get into TWRP, the Mi logo flashes but nothing else happens.
When I let the MIUI ROM start up and try to get into the recovery again,
it only shows me to connect my device to the Mi PC Manager.
What am I doing wrong?

blitzpeace said:
I tried this with the Global developer ROM for my kenzo.
When I try to get into TWRP, the Mi logo flashes but nothing else happens.
When I let the MIUI ROM start up and try to get into the recovery again,
it only shows me to connect my device to the Mi PC Manager.
What am I doing wrong?
Click to expand...
Click to collapse
Did you follow my instructions correctly?
- replaced recovery.img with ZCX TWRP recovery.img - check?
- EDL mode - check?
- remove usb cable after flash and press volume up+power button until mi logo shows up and then release buttons - check?
- are you sure you have kenzo version? did you download rom for kenzo? - check?
!! caution: the rom linked in this guide is only for kate version!!

thank you ! I've been trying the official route for 6 weeks, getting absolutely nowhere (even though I finally do have unlock permission).
this method worked like a charm, finally I'm off MIUI and running LineageOS

khajiit said:
Did you follow my instructions correctly?
- replaced recovery.img with ZCX TWRP recovery.img - check?
- EDL mode - check?
- remove usb cable after flash and press volume up+power button until mi logo shows up and then release buttons - check?
- are you sure you have kenzo version? did you download rom for kenzo? - check?
!! caution: the rom linked in this guide is only for kate version!!
Click to expand...
Click to collapse
1. I guess, do I have to replace only the recovery.img or more? If only recovery.img, then yes!
2. Yes, otherwise MiFlash would give me an error instead of flashing the ROM
3. Yes, but it appears only for an blink of an eye and then disappears again, the phone screen then stays dark
4. Yes, the newest one. Maybe that's the problem?

blitzpeace said:
4. Yes, the newest one. Maybe that's the problem?
Click to expand...
Click to collapse
Yes, that's the problem! This method only works until version 6.11.3.
You have to flash 6.11.3 (or earlier) to get TWRP and then you can flash what you want.
Good luck!

Excellent :good:
To boot into EDL
If you are lost with chinese language in TWRP, look at the first screenshot
And for Gapps take 64bits

Hi, I just got this ROM but when I plug the device in my computer it keeps connecting/disconnecting rapidly. Did I do something wrong?

Very helpful, but i would like to suggest people to use miunlocktool from windows 7-32 bit operating system. Miunlocktool perfectly works in windows 7 & don't stuck at 50%. Before unlock process, just "add oem unlocking device" from MIUI developer setting then start unlocking process..... Its really works for me & also others who followed these steps.

Skex506 said:
Hi, I just got this ROM but when I plug the device in my computer it keeps connecting/disconnecting rapidly. Did I do something wrong?
Click to expand...
Click to collapse
Yes, you did something wrong
Are you sure you have a "KATE" device not "KENZO"?
Follow my guide carefully and try again. It works 100%!
Rifatspir said:
Very helpful, but i would like to suggest people to use miunlocktool from windows 7-32 bit operating system. Miunlocktool perfectly works in windows 7 & don't stuck at 50%. Before unlock process, just "add oem unlocking device" from MIUI developer setting then start unlocking process..... Its really works for me & also others who followed these steps.
Click to expand...
Click to collapse
You don't think i've/we've tried everything? Official unlock works for you? Great! But it doesn't work for everyone... trust me.
Can we please stop to suggest to unlock officially with different guides? This guide is for people who don't want to or can't unlock officially.

khajiit said:
You don't think i've/we've tried everything? Official unlock works for you? Great! But it doesn't work for everyone... trust me.
Can we please stop to suggest to unlock officially with different guides? This guide is for people who don't want to or can't unlock officially.
Click to expand...
Click to collapse
I also said that million times to other people who suggest me different types of official method. When i success after trying couple of methods then i realized it is possible to unlock kate. I'm not saying that your post is not helpful, i saw many post like that, mostly in whirlpool forum. BTW, good luck with your tips :good:

Sure it is possible to unlock Kate officially but you have to wait for Xiaomi to get permission and wait for their servers to syncronize.
You have to wait up to 1 month (depending on your location and other things) until their servers confirms that you have permission to unlock (unable to verify thing). All these guides outside are working but it's a matter of time until they start working. That's why they didn't work for you in first place. :good:

hi @khajiit
They say not enough storage when I want to flash it. Could you please help me with this?
Spoiler: not enough

actuallyaka said:
hi @khajiit
They say not enough storage when I want to flash it. Could you please help me with this?
Click to expand...
Click to collapse
You are using a really old MiFlash version, try updating to the version mentioned in this guide.
And rename your folder "Redmi note 3 pro" to "Redmi.note.3.pro" or "Redmi_note_3_pro".
MiFlash tends to have problem with spaces.

khajiit said:
You are using a really old MiFlash version, try updating to the version mentioned in this guide.
And rename your folder "Redmi note 3 pro" to "Redmi.note.3.pro" or "Redmi_note_3_pro".
MiFlash tends to have problem with spaces.
Click to expand...
Click to collapse
Thank you khajiit..
it works know with using 2016 version..

[REBRANDING][RESTORING] AIO Guide

1. Recover to FULL STOCK
Info
Following this guide wipes your data and locks the bootloader fully again!
Make sure you backed up your personal data and have your unlock code written down somewhere.
If you have TWRP installed flash the NoCheck recoveries from the rebranding guide below.
Firmware Database
* DUK-AL20C00B173 - Download
* DUK-L09C10 (** Uploading **)
* DUK-L09C432 (** Uploading **)
* DUK-L09C900B122 - Download
Tutorial
1. download the firmware for your model
2. extract the fw_DUK-<model number>.tar.gz file
3. format your MicroSD as ExFAT (Fat32 is limited to 4gb file transfer size)
4. copy the extracted dload folder in the root directory of your MicroSD
5. shutdown the device, insert the MicroSD and disconnect the USB cable
6. boot device using VOL+, Vol- and POWER and keep this combo pressed until the recovery process starts
7. once finished your device should reboot and be back in a working state
2. Rebranding
Info
Rebranding is available for the following devices at the moment:
* DUK-AL20C00
* DUK-L09C432
* DUK-L09C900
this process requires attention and patience aswell as an unlocked bootloader.
Your data will be wiped a few times, so be sure you made a backup before starting.
Also dump your current oeminfo just in case yours is not available for download (see tutorial).
I've successfully rebranded my device from C900 to C432, but i'm not responsible for damaged devices.
Because some users were able to rebrand their Honor V9 to H8 Pro (AL20C00 -> L09C432) i also added
H V9 OEMInfo and firmware to be able to rebrand vice-versa.
After rebranding you will continue to get OTA updates!
Be sure to follow the tutorial!
Prerequisites
* Unlocked bootloader
* TWRP installed
OEMInfo Database
* DUK-AL20C00 - oeminfo_DUK-AL20C00.bin - Download
* DUK-L09C900 - oeminfo_DUK-L09C900.bin - Download
* DUK-L09C432 - oeminfo_DUK-L09C432.bin - Download
Tutorial
1. download the corresponding oeminfo for the model you want to rebrand to
(e.g. you want to rebrand to C432, so you download DUK-L09C432 oeminfo)
2. place oeminfo_DUK-<model number>.bin (e.g. oeminfo_DUK-L09C432.bin) in the root of your micro sd card
3. flash OEMInfo through TWRP terminal:
Code:
dd if=/external_sd/oeminfo_DUK-<model number>.bin of=/dev/block/bootdevice/by-name/oeminfo
4. flash both stock recovery files via fastboot
Code:
DUK-RECOVERY-NoCheck.img - [URL="https://mega.nz/#!TkwjmSRB!O5-2dMXJGHzAnBFOzVLuURKwykzranv4Til_5GqE418"]Download[/URL]
DUK-RECOVERY2-NoCheck.img - [URL="https://mega.nz/#!qkQhERRR!i3akZFgk1Cx9kjPDee58gw4w8LkWe2BXRoz4n9eL8ZE"]Download[/URL]
[B]flash commands:[/B]
fastboot flash recovery DUK-RECOVERY-NoCheck.img
fastboot flash recovery2 DUK-RECOVERY-NoCheck.img
5. download one of the following stock roms depending on the region you want to rebrand to
(e.g. you want to rebrand to C432, so you download DUK-L09C432 firmware)
Code:
DUK-AL20C00B173 - [URL="https://mega.nz/#!D0xghY4A!jhpOY0wL7LF_yc4J3p4mDwvoVDyLYQeY7hbkm-hcV4g"]Download[/URL]
DUK-L09C432B120 - [URL="https://drive.google.com/open?id=0B134drJ4-Ed0b2ZVY1JSZExYaUk"]Download[/URL]
DUK-L09C900B122 - [URL="https://drive.google.com/open?id=0B134drJ4-Ed0T1B5RlRldkN4Q00"]Download[/URL]
this also locks your bootloader again (yes reset your bootloader, not just relocking)
6. extract the downloaded .tar file
7. copy the dload folder to the root of your micro sd
(make sure you format it as exfat, because fat32 is limited to 4gb file transfer size)
8. shutdown device
9. ensure you have usb cable disconnected
10. start device using vol+, vol- and power, keep the combination pressed until the upgrade starts
11. (OPTIONAL) boot into eRecovery, just like you would do to boot TWRP, and do a factory reset
12. (OPTIONAL) re-unlock your bootloader
3. Updating to unapproved OTAs
Info
this process requires attention and patience aswell as an unlocked bootloader.
Your bootloader will be relocked most likely, so be sure you backed up your data before starting.
Sucessfully tried updating from DUK-L09C432B130 -> DUK-L09C432B182.
Be sure to follow the tutorial!
Prerequisites
* Unlocked bootloader
* TWRP installed
* running stock, unrooted firmware to prevent compatibility issues
Tutorial
1. download the last (unapproved) update for your device (e.g. B182)
Code:
[I]how to do this?[/I]
firmware database: [URL="http://hwmt.ru/hwmtsite/firmware-database/?firmware_model=DUK&firmware_page=0"]http://hwmt.ru/hwmtsite/firmware-database/?firmware_model=DUK&firmware_page=0[/URL]
[B]Only FullOTA-MF are supported![/B]
1. click on [B]filelist[/B] for the version you want to download (the lines interesting for you are those starting with <vendorInfo)
2. fetch the links ... (depending on the update those can only be 2 files instead of 3)
update.zip - [COLOR="red"]http://update.hicloud.com:8180/TDS/data/files/p3/s15/G1635/g104/v90811/f2/full[/COLOR]/[COLOR="green"]update.zip[/COLOR]
update_data_full_public.zip - [COLOR="red"]http://update.hicloud.com:8180/TDS/data/files/p3/s15/G1635/g104/v90811/f2/full[/COLOR]/[COLOR="yellow"]public[/COLOR]/[COLOR="green"]update_data_full_public.zip[/COLOR]
update_full_DUK-L09_hw_eu.zip - [COLOR="red"]http://update.hicloud.com:8180/TDS/data/files/p3/s15/G1635/g104/v90811/f2/full[/COLOR]/[COLOR="yellow"]DUK-L09_hw_eu[/COLOR]/[COLOR="green"]update_full_DUK-L09_hw_eu.zip[/COLOR]
3. download all files
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
2. boot into TWRP
3. create HWOTA folder in the root of your internal storage (yes, it can be encrypted as long as you don't try to boot the device again)
4. move the firmware zip files into the previously created HWOTA folder
5. execute the following commands in twrp terminal
Code:
1. "mkdir /data/update" (without the quotes)
2. "mv /sdcard/HWOTA /data/update/HWOTA" (without the quotes)
6. flash both nocheck erecovery files via twrp
Code:
place them in the root of your internal storage!
DUK-RECOVERY-NoCheck.img - [URL="https://mega.nz/#!TkwjmSRB!O5-2dMXJGHzAnBFOzVLuURKwykzranv4Til_5GqE418"]Download[/URL]
DUK-RECOVERY2-NoCheck.img - [URL="https://mega.nz/#!qkQhERRR!i3akZFgk1Cx9kjPDee58gw4w8LkWe2BXRoz4n9eL8ZE"]Download[/URL]
[B]twrp terminal commands:[/B]
dd if=/sdcard/DUK-RECOVERY-NoCheck.img of=/dev/block/bootdevice/by-name/recovery_a
dd if=/sdcard/DUK-RECOVERY2-NoCheck.img of=/dev/block/bootdevice/by-name/recovery2_a
after flashing went good, delete both images from your internal storage again
7. zip files have to be added to the recovery command for a proper update process
Code:
[B]in twrp terminal:[/B]
echo --update_package=/data/update/HWOTA/<zip file> > /cache/recovery/command
depending on the number of zips you downloaded you have to execute the command multiple times, e.g.:
echo --update_package=/data/update/HWOTA/update.zip > /cache/recovery/command
echo --update_package=/data/update/HWOTA/update_data_full_public.zip >> /cache/recovery/command
echo --update_package=/data/update/HWOTA/update_full_DUK-L09_hw_eu.zip >> /cache/recovery/command
8. check if you have any left-over data inside the internal storage you may forgot to remove (e.g. NoCheck recovery)
9. reboot recovery, update process should now start (this replaces the NoCheck recovery aswell)
10. (OPTIONAL) boot into eRecovery, just like you would do to boot TWRP, and do a factory reset
11. (OPTIONAL) re-unlock your bootloader​
XDA:DevDB Information
Rebranding Guide, Tool/Utility for the Honor 8 Pro
Contributors
OldDroid, -=MoRpH=-
Version Information
Status: Stable
Created 2017-06-24
Last Updated 2017-07-20

firmwear download link erro!!!!!

nocheck reocovery and nocheck recovery 2 same link ?

sweetjuice said:
nocheck reocovery and nocheck recovery 2 same link ?
Click to expand...
Click to collapse
corrected, fw dl works fine for me btw

where can i get the twrp for honor 8 pro ?can i rebrand my V9 DUK-AL20 to DUK-L09C432?

sweetjuice said:
where can i get the twrp for honor 8 pro ?can i rebrand my V9 DUK-AL20 to DUK-L09C432?
Click to expand...
Click to collapse
maybe have a look into the "roms, kernels & recovery development" section?
you can try, but i don't know for sure, should work.
Also, please dump us your OEMInfo.
Regards

OldDroid said:
maybe have a look into the "roms, kernels & recovery development" section?
you can try, but i don't know for sure, should work.
Also, please dump us your OEMInfo.
Regards
Click to expand...
Click to collapse
thank you for you help. my DUK-AL20 rebrand to DUK-L09C00 successfully!
DUK-AL20 oeminfo https://drive.google.com/open?id=0B0Ra1dRtY0loWnRlT3ZQbTFGZVU

sweetjuice said:
thank you for you help. my DUK-AL20 rebrand to DUK-L09C00 successfully!
DUK-AL20 oeminfo https://drive.google.com/open?id=0B0Ra1dRtY0loWnRlT3ZQbTFGZVU
Click to expand...
Click to collapse
thanks, i will add it later to op.
Good to know that it works
i will try to get my hands on a stock rom for the device so you can revert any time.
Regards

sweetjuice said:
thank you for you help. my DUK-AL20 rebrand to DUK-L09C00 successfully!
DUK-AL20 oeminfo https://drive.google.com/open?id=0B0Ra1dRtY0loWnRlT3ZQbTFGZVU
Click to expand...
Click to collapse
Do you have any change in supported LTE networks?
I am wondering maybe this one will enable the B20 frequency. Not sure if there is any difference in hardware between 8 Pro and V9.

tibcsi0407 said:
Do you have any change in supported LTE networks?
I am wondering maybe this one will enable the B20 frequency. Not sure if there is any difference in hardware between 8 Pro and V9.
Click to expand...
Click to collapse
i have no idea how to check the frequency!!!

sweetjuice said:
i have no idea how to check the frequency!!!
Click to expand...
Click to collapse
Do you have root?
This one can check the available bands. Actually we will know it only if you live in a B20 area.

Hi Sweetjuice could you confirm that your v20 is working well with the Honor 8 pro firmware? I'm in same position as you on that I'm on the v9 China and really want to get rid of the China apps and even with Google play services on it I don't have a fully working Google assistant. Your feedback would be immense thanks mate

Thank you so much. My AL20 had successfully degrade with the help of your unchecked erecovery!

zhenufo said:
Thank you so much. My AL20 had successfully degrade with the help of your unchecked erecovery!
Click to expand...
Click to collapse
You mean downgrade man? Because degrade is a different thing.

adriansticoid said:
You mean downgrade man? Because degrade is a different thing.
Click to expand...
Click to collapse
he said that he rebranded successfully

OldDroid said:
he said that he rebranded successfully
Click to expand...
Click to collapse
Oh. I'm sorry.

tibcsi0407 said:
Do you have any change in supported LTE networks?
I am wondering maybe this one will enable the B20 frequency. Not sure if there is any difference in hardware between 8 Pro and V9.
Click to expand...
Click to collapse
to check the LTE frequency ,do i need to root the device first ?

sweetjuice said:
to check the LTE frequency ,do i need to root the device first ?
Click to expand...
Click to collapse
Yes, AFAIK.

lunchplease said:
Hi Sweetjuice could you confirm that your v20 is working well with the Honor 8 pro firmware? I'm in same position as you on that I'm on the v9 China and really want to get rid of the China apps and even with Google play services on it I don't have a fully working Google assistant. Your feedback would be immense thanks mate
Click to expand...
Click to collapse
so far so good

sweetjuice said:
thank you for you help. my DUK-AL20 rebrand to DUK-L09C00 successfully!
DUK-AL20 oeminfo https://drive.google.com/open?id=0B0Ra1dRtY0loWnRlT3ZQbTFGZVU
Click to expand...
Click to collapse
DUK-L09C00 ?? Maybe DUK-L09C900? Can you please help me with this task? I also have DUK-AL20 and want to get rid off these China software and notification bugs but a little bit scary to brick my device. Hope international version will help me on this. Also is everything ok after rebrand? everything works fine ?
Will be grateful if you help me to rebrand my device.

[Tool] 3/9/2019 Jarvinator GUI toolkit for Mi A2 (beta)

Completely Re-Written in C#
This version is actually up to date, sorry for the long time between releases, I had to learn c# before creating the C# version...
Anyways, you know the schpeel
I am not responsible for anything that happens to your device, or computer as a result of you using my toolkit. You are responsible for your own devices, don't be stupid.
Please note, this program is in it's early days, due to me not knowing a lot of c#. Please be patient if it is buggy, comment and join my telegram channel for support at https://t.me/a2_gui_toolkit
The features include:
Reboot options
Reboot to EDL mode
Common Links used in the forums
IMG flasher (beta)
Stock rom downloader and flasher (beta)
No install TWRP launcher
No install TWRP zip installer
Auto Root
Auto Update Checker.
Other features to come
Easter egg, can you find it?
Future features
Backup/Restore
Convert to Mi 6X
Mi 6x Support
Rom installer
Hex Kernel Installer
Possible Suggestions
Camera 2 enabler
OTA installer for rooted users
Some screenshots
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Release Notes
Version 1.0.2
Added auto-root functionality
Fixed random crashes and bugs
Added new UI elements for parts currently being worked on
Converted to use a c# adb api
added dropdown for noob mode
updated instructions and order of certain processes
added json support for twrp api (in the future will automatically download latest twrp version)
probably more I am forgetting
Version 1.0.1
fixed TWRP zip flashing on reboot
Fixed settings not saving correctly on certain systems
Fixed many misc bugs
Updated dialogs to be more convienient and guiding
Created disabled butttons to show future implimentations
Added backup via ADB backup, restore is not yet implimented
Please ensure you have .net version 4.6.1 or later! It can be downloaded here if not already installed.
https://dotnet.microsoft.com/download/dotnet-framework/net461
Download Toolkit Here
https://github.com/da-ha3ker/Jarvinator-A2-Toolkit-Release

Can you provide some screenshots or tutorial? Thank you in advance!

Can you provide the same tool for Mi A2 Lite ?

Thank you

8 no. revert to stock rom
if i use this will my bootloader unlocked a2 will revert to stock rom with bootloader locked?

Syed Shahriar said:
8 no. revert to stock rom
if i use this will my bootloader unlocked a2 will revert to stock rom with bootloader locked?
Click to expand...
Click to collapse
No. It will only flash the stock rom, your bootloader will still be unlocked. I will add re-lock bootloader as an option in future updates

Daha3ker said:
No. It will only flash the stock rom, your bootloader will still be unlocked. I will add re-lock bootloader as an option in future updates
Click to expand...
Click to collapse
flash rom with august patch?
and will stock rom be downloaded from the commands ?

No 4 installs the patches boot image right? No 5 install the original one? Do i have to install the unpatched image (unroot) before ota?

bartoloandre98 said:
No 4 installs the patches boot image right? No 5 install the original one? Do i have to install the unpatched image (unroot) before ota?
Click to expand...
Click to collapse
No 4 and 5 is correct. You will have to have an unrooted device to install ota's, so if you run the unroot it should work; So as long as your device's system hasn't been modified (eg busybox or non systemless modifications) you should be good to install the ota.

Syed Shahriar said:
flash rom with august patch?
and will stock rom be downloaded from the commands ?
Click to expand...
Click to collapse
The version is stated in the description. So yes, the August patch. The stock rom is in the Stock_images folder. So it is downloaded when you download the program.

Ahmed_hassan95 said:
Can you provide the same tool for Mi A2 Lite ?
Click to expand...
Click to collapse
I do not have an A2 lite, if you or someone you know would like to, you can port this to the lite version. It should not be too hard, I just don't have any way to test what would work and what would not.

I've my A2 already unlocked (BootLoader unlocked)
if i want simply to root it, have i simply to use 4. Root Device ?
does this install also TWRP ?
have i to launch 4 option with phone in faastboot, or in normal mode ?

webmasterone said:
I've my A2 already unlocked (BootLoader unlocked)
if i want simply to root it, have i simply to use 4. Root Device ?
does this install also TWRP ?
have i to launch 4 option with phone in faastboot, or in normal mode ?
Click to expand...
Click to collapse
You must run OEM unlock, unlock flashing and unlock critical, then run 4 to root the device. TWRP will cause a bootloop, so follow the instructions in option 6 to avoid it. TWRP is able to be used, but not permanetly installed.

No spiking english, how relock bootloader? Help me please!

Nestor0rtiz1 said:
No spiking english, how relock bootloader? Help me please!
Click to expand...
Click to collapse
fastboot oem lock

AhanafTanvir said:
fastboot oem lock
Click to expand...
Click to collapse
Could you explain me please?

Nestor0rtiz1 said:
Could you explain me please?
Click to expand...
Click to collapse
boot to fastboot mode in ur phone, connect via usb, open fastboot from pc. type
fastboot oem lock
tell me what happens

I really want to install GCAM and camera2API on my A2, but also, I don't want to lose OTA updates, banking funcionatility and don't want to keep bootloader unlocked.
Can I have this? Or am I dreaming too high?

kadu20es said:
I really want to install GCAM and camera2API on my A2, but also, I don't want to lose OTA updates, banking funcionatility and don't want to keep bootloader unlocked.
Can I have this? Or am I dreaming too high?
Click to expand...
Click to collapse
You won't lose data when locking the bootloader, only unlocking. You can OTA update, if you open magisk manager and uninstall (restore the original boot.img). I didn't test this myself, but I will as soon as the next OTA is available.

hugopg said:
You won't lose data when locking the bootloader, only unlocking. You can OTA update, if you open magisk manager and uninstall (restore the original boot.img). I didn't test this myself, but I will as soon as the next OTA is available.
Click to expand...
Click to collapse
Cool! When you get done, please, share your experience. If you can, share the process of restoring of the original "boot.img"

Stable Oxygen OS/Android 11 fastboot boot twrp.img lead to Qualcomm Crashdump

Hello,
My goal is to get an Android 11 Stable version with TWRP recovery and magisk root.
I cannot achieve this goal cause of an error - "Qualcomm crashdump" - i get when trying to boot into TWRP.IMG
Does anyone managed to install twrp recovery and root with Android 11 stable?
Thanks

BenoMosko said:
Hi!
First Thanks for the reply.
Second, I opened a thread just for that, maybe you can share your wisdom with us over there
Stable Oxygen OS/Android 11 fastboot boot twrp.img lead to Qualcomm Crashdump
Hello, My goal is to get an Android 11 Stable version with TWRP recovery and magisk root. I cannot achieve this goal cause of an error - "Qualcomm crashdump" - i get when trying to boot into TWRP.IMG Does anyone managed to install twrp...
forum.xda-developers.com
I dont have a T-Mobile OP6T i have a global device.
"it could work to set up a rooted OOS 10 (which should give you less trouble) and then use the method I described above to upgrade."
Can you share and give us step by step instruction please?
Which version should i be on with installing twrp recovery and root using magisk?
10.3.8?
10.3.12?
cant i do it straight from 11?
thanks.
Click to expand...
Click to collapse
I believe there's a rollback zip which could help you out. It's at the bottom of this article. Not sure if it works on stable. Note that it wipes everything!
scorpio76r said:
Yes, I have the T-Mobile which is internationally converted
Click to expand...
Click to collapse
TMO has not been very kind to development in any way. It may just take some time for modding to catch up or you may find a way. Much luck finding the answer I personally stay as far away from provider branded devices as I can

Timmmmaaahh! said:
I believe there's a rollback zip which could help you out. It's at the bottom of this article. Not sure if it works on stable. Note that it wipes everything!
TMO has not been very kind to development in any way. It may just take some time for modding to catch up or you may find a way. Much luck finding the answer I personally stay as far away from provider branded devices as I can
Click to expand...
Click to collapse
You are so correct. I will never purchase a carrier branded device again.

Timmmmaaahh! said:
I believe there's a rollback zip which could help you out. It's at the bottom of this article. Not sure if it works on stable. Note that it wipes everything!
TMO has not been very kind to development in any way. It may just take some time for modding to catch up or you may find a way. Much luck finding the answer I personally stay as far away from provider branded devices as I can
Click to expand...
Click to collapse
Hi,
I have the rollbacks and i can use mstool to do rollbacks to 10.3.8
that's not my issue.
Lets organize it.
I have a goal - OnePlus 6T with OOS11+TWRP+ROOT
can i achieve this goal?
if yes,
can u please give me details on how to achieve?
thanks.

BenoMosko said:
Hi,
I have the rollbacks and i can use mstool to do rollbacks to 10.3.8
that's not my issue.
Lets organize it.
I have a goal - OnePlus 6T with OOS11+TWRP+ROOT
can i achieve this goal?
if yes,
can u please give me details on how to achieve?
thanks.
Click to expand...
Click to collapse
This would also be helpful to people who are just purchasing this device which most likely will have the 11 update already

BenoMosko said:
Hi,
I have the rollbacks and i can use mstool to do rollbacks to 10.3.8
that's not my issue.
Lets organize it.
I have a goal - OnePlus 6T with OOS11+TWRP+ROOT
can i achieve this goal?
if yes,
can u please give me details on how to achieve?
thanks.
Click to expand...
Click to collapse
With an international version, I don't see any reason why it wouldn't work. After MSM'ing (whichever version) I'd first make sure it gets a working TWRP and Magisk root, then upgrade to latest 10 keeping the method I described in mind (to keep TWRP and root alive), then take the same step towards 11. I don't think it even matters which 10 is present, the full stable 11 zip will upgrade it either way. I was one (security) update behind.

Timmmmaaahh! said:
With an international version, I don't see any reason why it wouldn't work. After MSM'ing (whichever version) I'd first make sure it gets a working TWRP and Magisk root, then upgrade to latest 10 keeping the method I described in mind (to keep TWRP and root alive), then take the same step towards 11. I don't think it even matters which 10 is present, the full stable 11 zip will upgrade it either way. I was one (security) update behind.
Click to expand...
Click to collapse
Thank you so much for the support
"keeping the method I described in mind"
can you please copy paste it here?
and maybe do a little
1.
2.
3.
steps instructions please????????
thanks.

BenoMosko said:
Thank you so much for the support
"keeping the method I described in mind"
can you please copy paste it here?
and maybe do a little
1.
2.
3.
steps instructions please????????
thanks.
Click to expand...
Click to collapse
I already did
Timmmmaaahh! said:
That makes SafetyNet pass? I did the classic routine:
Install full zip (OnePlus6TOxygen_34.J.60) via 'Local upgrade' - no rebooting
Flash TWRP installer (I had 3.4.0-11) via Magisk - no rebooting
Flash Magisk via Magisk to other slot
Reboot! All done.
Click to expand...
Click to collapse

Timmmmaaahh! said:
I already did
Click to expand...
Click to collapse
Great, Thanks.
One more question...
when going back to 10.3.8 to install twrp, can i use the latest twrp version and not "3.4.0-11"?
thanks.

Timmmmaaahh! said:
I already did
Click to expand...
Click to collapse
Hi ..Will the twrp version 3.5.2-9 work too? Or do we have to use this version in your post?

Would flashing OOS 10 back clear all my data? Is there way to just install the TWRP and root it with magisk zip like we did earlier?

shreyas.kukde said:
Would flashing OOS 10 back clear all my data? Is there way to just install the TWRP and root it with magisk zip like we did earlier?
Click to expand...
Click to collapse
It has been a no go so far trying to get magisk and twrp on 11. I guess we will need to use the msm tool and,start from scratch

BenoMosko said:
Great, Thanks.
One more question...
when going back to 10.3.8 to install twrp, can i use the latest twrp version and not "3.4.0-11"?
thanks.
Click to expand...
Click to collapse
Libraplum76 said:
Hi ..Will the twrp version 3.5.2-9 work too? Or do we have to use this version in your post?
Click to expand...
Click to collapse
I really don't think versions are all that important. Try the latest one and work your way down from there? Best practice IMHO is just revisiting the TWRP thread when preparing to flash and check for any anomalies in OP and last 2 or 3 pages of the thread. Do the same for anything you need to flash (Magisk, OOS or custom ROM thread, etc.). More reading lowers the chances of failure.

Just use fastboot flash boot_a boot.img and preferably fastboot flash boot_b boot.img, instead of boot.img use beta3 prerooted and preinstalled with twrp boot image - you can find it somewhere on this forum in another section. Then just from fasboot boot to recovery and install oos11 again.

ppajdek said:
Just use fastboot flash boot_a boot.img and preferably fastboot flash boot_b boot.img, instead of boot.img use beta3 prerooted and preinstalled with twrp boot image - you can find it somewhere on this forum in another section. Then just from fasboot boot to recovery and install oos11 again.
Click to expand...
Click to collapse
You just brung hope, thank you. I will definitely go on the hunt for that recovery image*Edit, just found the link https://forum.xda-developers.com/t/...1-open-beta-2-and-open-beta-3-latest.4316563/

This has been solved for the oneplus 6t international converted on Oxygen 11 stable. Using the PRO3 file from the link I posted earlier (shout out to member KizuYuna who made and, provided the PRO3 file, also shout out to ppajdek for pointing me in the right direction ) I fastboot flash boot the file (simple drag and drop) it brought me to a twrp called pitch black( yaay! I had some form of twrp) while in there I flashed the 3.5.1_9-0 fajita installer zip. Next, I hit the power button in the pitch black twrp that gave me a option to reboot to recovery. Yaay, I rebooted to twrp 3,5.1_9-0. Next I flashed the latest 11 oxygen stable. After that I flashed the twrp installer again. After that, I rebooted to recovery (was glad I hadn't bricked by now) Next, I flashed magisk 23.0 and, lastly rebooted to system. (shocked that I didn't get a crash dump screen, lol) went into magisk and, enabled magisk hide. Here are pictures of the result, yaay. I did not post a picture of twrp, but yes it works and is present.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

scorpio76r said:
This has been solved for the oneplus 6t international converted on Oxygen 11 stable. Using the PRO3 file from the link I posted earlier (shout out to member KizuYuna who made and, provided the PRO3 file, also shout out to ppajdek for pointing me in the right direction ) I fastboot flash boot the file (simple drag and drop) it brought me to a twrp called pitch black( yaay! I had some form of twrp) while in there I flashed the 3.5.1_9-0 fajita installer zip. Next, I hit the power button in the pitch black twrp that gave me a option to reboot to recovery. Yaay, I rebooted to twrp 3,5.1_9-0. Next I flashed the latest 11 oxygen stable. After that I flashed the twrp installer again. After that, I rebooted to recovery (was glad I hadn't bricked by now) Next, I flashed magisk 23.0 and, lastly rebooted to system. (shocked that I didn't get a crash dump screen, lol) went into magisk and, enabled magisk hide. Here are pictures of the result, yaay. I did not post a picture of twrp, but yes it works and is present. View attachment 5384313View attachment 5384315
Click to expand...
Click to collapse
Great! Worked for me too. Thought I could never get Root or Twrp again.

scorpio76r said:
It has been a no go so far trying to get magisk and twrp on 11. I guess we will need to use the msm tool and,start from scratch
Click to expand...
Click to collapse
A telegram group titled OnePlus 6T Chat has a user who said he flashed latest TWRP and Latest Magisk and it worked for him. Strange..

shreyas.kukde said:
A telegram group titled OnePlus 6T Chat has a user who said he flashed latest TWRP and Latest Magisk and it worked for him. Strange..
Click to expand...
Click to collapse
Shocking, lol

scorpio76r said:
Shocking, lol
Click to expand...
Click to collapse
Can you provide the TWRP zip that you flashed?