Develop Bugs

[FIX] 30 Nov r2: Volume Bug Fix!

Annoyed with the volume bug on your Galaxy Nexus? Well, i'm very proud to present the forthcoming official fixed boot image which resolves this problem. In order to flash this boot image, you need your bootloader to be unlocked at this time (use './fastboot-windows oem unlock' (or the appropriate version for your machine, included in the download). Note that the OEM unlock sequence wipes your device.
APPLY THIS AT YOUR OWN RISK! This is still in a testing phase internally. Although it works great for us, well, you never know.
Volume Bug Fix r3 - DOWNLOAD - MD5: 292ba3630f475b2f779a19057649200a
How to use - Windows, Linux and OSX
- Download the zip file above and extract to a directory
- Put your device in bootloader mode - Turn off the phone then turn on with the 'volume up' and 'volume down' buttons both pressed to enter the bootloader (as pictured below)
- WINDOWS - double click 'install-windows.bat'
- MAC - Open a terminal window to the directory containing the files, and type 'chmod +x install-mac.sh' followed by './install-mac.sh'
- LINUX - Open a terminal window to the directory containing the files, and type 'chmod +x install-linux.sh' followed by './install-linux.sh'
Please don't rehost this zip file - if you want to link to the fix, please link to this topic. That's all I ask. Enjoy!
P

Thanks a lot for your effort!
Does OEM unlock touch my guarantee?

Thanks Paul, I get the phone tomorrow morning & thanks to you we already have our hands on the fix. Thanks a million!

You can reverse the unlock with lock when required;
./fastboot-windows oem lock

I'm very curious as to whether the volume bug is also fixed for the bootloader, and if it affects CPU load in any way, anyone tested something along those lines yet?

Rubu said:
I'm very curious as to whether the volume bug is also fixed for the bootloader, and if it affects CPU load in any way, anyone tested something along those lines yet?
Click to expand...
Click to collapse
Me too. Can anyone confirm?
Sent from my Sensation using XDA App

This doesn't fix the bootloader, doesn't seem to affect the device in any other way.
P

paulobrien said:
This doesn't fix the bootloader, doesn't seem to affect the device in any other way.
P
Click to expand...
Click to collapse
I'm pretty sure you have tested the fix. Have you been able to reproduce the bug with this version ? (Other than in the bootloader) One word from you and I might buy the Nexus ;-)

Paul if you dont mind i will repack it to zImage flashable mod because your stock boot.img will disable all tweaks in my ROM if people flash it.
Sent from my HTC Sensation Z710e using Tapatalk

mike1986. said:
Paul if you dont mind i will repack it to zImage flashable mod because your stock boot.img will disable all tweaks in my ROM if people flash it.
Sent from my HTC Sensation Z710e using Tapatalk
Click to expand...
Click to collapse
Sure, that's what i've done for MCR, as long as you give appropriate credit that's cool!
P

And what's new kernel version? Or what's the base number it came from?

i have just applied this patch.
will report back if this helps.

mike1986. said:
And what's new kernel version? Or what's the base number it came from?
Click to expand...
Click to collapse
Still 3.0.1.
P

Thanks in advance(Nexus on its way)

With all credits to paulobrien, who delivered this stock kernel to us, I made recovery flashable .zip with zImage file (kernel) instead of whole boot.img, because I do some changes to ramdisk (another part of boot.img) and by flashing default boot.img over my ROM you will loose all my tweaks. Also there are no changes to ramdisk, volume button fix in only zImage related. So you can grab it from here
Just flash it in recovery. You can flash it on any ROM, not only mine.

Hope we get the updated kernel source soon!
P

paulobrien said:
This doesn't fix the bootloader, doesn't seem to affect the device in any other way.
P
Click to expand...
Click to collapse
Thanks for all your hard work! Cant wait for my GN, i hope ill get it this week!
Can you pleas tell me whats wrong with the bootloader? I only know the bug with the volume but ive never read something about bootloader bug ...
Thanks in advance

lichti1901 said:
Thanks for all your hard work! Cant wait for my GN, i hope ill get it this week!
Can you pleas tell me whats wrong with the bootloader? I only know the bug with the volume but ive never read something about bootloader bug ...
Thanks in advance
Click to expand...
Click to collapse
The phone suffers from the volume bug even when it's in the bootloader. A lot of people think now it could be a hardware problem because there isn't much going on the software side in this state.
Which means if it is a hardware problem and you fix it with a software patch then it could still cause some problems under the hood. For example the phone doesn't sleep proberly while it is in a 2G area.
But according to Paul it doesn't cause any reaction on the phone. Which makes the bug really strange.
Edit: At least for me.

Paul,
The .bat file is "fastboot boot *.img", which i understand wouldn't be permanent, can we also "fastboot flash boot *.img"
Cheers

ande_uk said:
Paul,
The .bat file is "fastboot boot *.img", which i understand wouldn't be permanent, can we also "fastboot flash boot *.img"
Cheers
Click to expand...
Click to collapse
i have manually run fastboot flash boot <image> on mine, and it worked.(i also backup a copy of my boot.img before hand just incase).
i believe what paul is trying to do is just a temporary fix (running it once) untill google release a proper update.

[9/9/12][Recovery]Clockworkmod v6.0.1.3

This is just a recovery I compiled from the latest available code from the CM10 source. It does not offer any major upgrade in function from ACL's latest cwm recovery, but is slightly aesthetically different.
Installation:
Download from link below, flash with fastboot
Code:
fastboot flash recovery recovery.img
Bugs:
recovery.log may show these errors:
Code:
failed to open /sys/class/android_usb/android0/state: No such file or directory
but it does not affect usb or mass storage afaik.
Download:
recovery_cwr_6.0.1.3.img - 3.36 MB 9912
Credits: Everyone involved in Android development.
Feel free to report any bugs and enjoy.

works great, but one question: what is the thing you are asked first time you click reboot system now and what should i have answered yes or no, cause i clicked no?

Ranomez said:
works great, but one question: what is the thing you are asked first time you click reboot system now and what should i have answered yes or no, cause i clicked no?
Click to expand...
Click to collapse
I have not seen that prompt before.. what did it say? If you don't know what it does, answering "no" is probably a good idea

jianC said:
I have not seen that prompt before.. what did it say? If you don't know what it does, answering "no" is probably a good idea
Click to expand...
Click to collapse
something about after reboot rom may flash stock recovery, do you want to disable recovery flash, thats the question i get

Ranomez said:
something about after reboot rom may flash stock recovery, do you want to disable recovery flash, thats the question i get
Click to expand...
Click to collapse
In that case, just choose "no".

sorry to revive this old thread, but i just realised this recovery has a big problem and wanted to warn anyone who may want to try it: most blckups made by it have md5 mismatch, i meant i got that error at 14 out of 15 backups created.
EDIT1: i had a look at the backup folder and as far as i can see some .img files are not generated (i think cache and recovery) and also the nandroid.md5 is not generated, but that is easy to fix by generating it by urself throu adb.

Battery loading Led not working
The Led is not working with this recovery while charging.
I guess the Battery is not loading, too.
Edit - This is only, when phone is off. -
Hope this can be fixed.
regards

Sorry about the bugs/lack of support but I do not have a Touch Pro 2 anymore.
The most help I can offer is uploading the device tree that I used to compile recovery in CM10 (and potentially compile a booting version of CM10 but that has never been accomplished due to kernel issues).
https://github.com/jianC/android_device_htc_rhodium

jianC said:
Sorry about the bugs/lack of support but I do not have a Touch Pro 2 anymore.
The most help I can offer is uploading the device tree that I used to compile recovery in CM10 (and potentially compile a booting version of CM10 but that has never been accomplished due to kernel issues).
http://ge.tt/1gVK1FS/v/0?c
Click to expand...
Click to collapse
If you would like to play with the 3.4.17 kernel for S&Gs, you can find it in this thread at the bottom of the first post.
Maybe some of the kernel issues will be fixed there? I can probably get the git for it if you would want it.

wizardknight said:
If you would like to play with the 3.4.17 kernel for S&Gs, you can find it in this thread at the bottom of the first post.
Maybe some of the kernel issues will be fixed there? I can probably get the git for it if you would want it.
Click to expand...
Click to collapse
Thanks for the links, but I do not have a rhod for testing anymore.. maybe someone adventurous could take a stab at it .

[RECOVERY] TWRP 2.5 - i9505 Ex#2

Hello again, I bring to you, TeamWin Recovery Project or commonly known as TWRP (2.5) for your beloved i9505 (S4). I decided to build this as a number of users (including myself) are not much fans of CWM. This gives you the ability to flash your favourite custom ROMs, Kernels, Mods. I have pushed the TWRP Device Tree to my Github, for all of you curious people. Thankyou to 'as i9000' for giving me the stock recovery. Note: This thread will be moved to the i9505 section once its created. If you Encounter any issues with this recovery, report them to this thread with a recovery.log. You can get it by, adb pull /tmp/recovery.log
This has not been tested by me and is still experimental. I hold no responsibility
for any problems caused. YOU! Are trying this at your own risk. Don't blame me that I wasted your $700.
Put a scare in you didn't I?
I have provided the stock recovery if you encounter any issues, you can always flash back. It is Odin flashable.
Downloads:
TWRP (2.5) Experimental #Offi: Download (tech TeamWin)
Stock Recovery: http://d-h.st/LqC
Changelog:
Code:
[I][U]Experimental #2[/U][/I]
Attempted boot fix
Board MSM890 added to list
system.prop updated
Temporarily removed some twrp flags
[I][U]Experimental #1[/U][/I]
Public release

Does NOT work, tested this just now!
when you try to boot in recovery, phone is restarted automatically, recovery cannot be reached, so i went back to stock recovery

karoolus said:
Does NOT work, tested this just now!
when you try to boot in recovery, phone is restarted automatically, recovery cannot be reached, so i went back to stock recovery
Click to expand...
Click to collapse
Thankyou for reporting. Building new version now. one that will hopefully boot in recovery. (skipped some changes i thought werent necessary)
EDIT: i9505 user, who is willing to test. PM ME

not that I don't appreciate your effort in building it,
but won't the TWRP team create an official thread for the S4?

PLUG313 said:
not that I don't appreciate your effort in building it,
but won't the TWRP team create an official thread for the S4?
Click to expand...
Click to collapse
Maybe they will, maybe they wont. who knows
-----------------------------------------------------------------------------------------
Experimental #2 Online. Should fix recovery issues

Do you plan on making a recovery for the at&t s4?

fix-this! said:
Do you plan on making a recovery for the at&t s4?
Click to expand...
Click to collapse
Send me the stock recovery. and download this on your phone: https://play.google.com/store/apps/details?id=com.cls.partition&hl=en and send me the info

tested exp2, didn't work either.. i can't use ADB on work pc (driver restrictions etc) and i can't take the device home with me, so i can't take logs, sorry..

karoolus said:
tested exp2, didn't work either.. i can't use ADB on work pc (driver restrictions etc) and i can't take the device home with me, so i can't take logs, sorry..
Click to expand...
Click to collapse
Then it'll take a long time to fix the boot to recovery..

karoolus said:
tested exp2, didn't work either.. i can't use ADB on work pc (driver restrictions etc) and i can't take the device home with me, so i can't take logs, sorry..
Click to expand...
Click to collapse
Can you please test the CWM recovery and let us know if it works?
http://forum.xda-developers.com/showthread.php?p=40383354

karoolus said:
tested exp2, didn't work either.. i can't use ADB on work pc (driver restrictions etc) and i can't take the device home with me, so i can't take logs, sorry..
Click to expand...
Click to collapse
Try this, I doubt it will work at all. But get some filemanager that can browse ~/ directories. if it says root not available or something, deny it and check if you can continue. If yes, open the recovery.log and send me its contents.

Can anyone try this please??
I dont know if it will work but give a try.
Thank's

Doesn't boot in Recovery.

Can no one provide a recovery.log? that is the only thing needed to fix these issues

emwno said:
Can no one provide a recovery.log? that is the only thing needed to fix these issues
Click to expand...
Click to collapse
I would like to, but since i installed chainfires root my phone doesnt boot anymore... Waiting for a stock ODIN rom for the GT-I9505...
Then i can send it to you...

adb doesn't work here atm. If I get it to run, I'll send you the Log-File.

Unfortunately I had flashed chainfire's root before attempting this. I flashed exp2 and every time I attempted to boot recovery it would just kick me back to the battery charging screen (plugged in).
I booted back to the OS but it didn't have that log...
adb pull /tmp/recovery.log
remote object '/tmp/recovery.log' does not exist
Should I not boot back to the OS to get that file?

adb is working now here. But I have the same problem like Harry.
remote object '/tmp/recovery.log' does not exist

ausdim said:
Can anyone try this please??
I dont know if it will work but give a try.
Thank's
Click to expand...
Click to collapse
I tried this but it didn't work. Same thing as all the others.

harrybozack said:
I tried this but it didn't work. Same thing as all the others.
Click to expand...
Click to collapse
Boot into recovery. Then into system and try these:
Code:
adb pull /cache/recovery/last_log
Code:
adb pull /cache/recovery/log

TWRP (Ianmacd) Images, New Space.

This is NOT my work (Ianmacd) and guide is written by Mr Pickles all credits to him for his install method.
Also this is just a copy and paste but the guide is well written and TWRP should cause less issues.
I'm sure Gieti94 is just perhaps busy with other commitments, credit also to him for his fantastic efforts.
Just a new space for the currently working TWRP so all don't get in a pickle.
----------------------------
Download Maintained By Pickles (best all in one convenient place) will have everything necessary for twrp functionality. Credit to pickles.....:good:
http://bit.ly/2VlcqYd
Excellent installation Guide below
Install Guide
---------------------------
- NOT A SINGLE STEP IS UNNESSECARY
- DO THEM _ALL_ EXACTLY!
- ALL YOUR DATA WILL BE GONE - BACKUP!
---------------------------------------
DO NOT INSTALL MODPACK FROM SOLDIER - IT BREAKS TWRP!
---------------------------------------
If you have any problems - contact @PiCkLeS or on Telegram by PiCkLeS or @rp4k
---------------------------------------
All development is by @ianmacd (Ian Macdonald).
---------------------------------------
0 - No matter what you have today, no root or Magisk-only solution or TWRP with Magisk-solution, do ALL the steps..
1 - Make sure you copy the "Magisk_Manager_Ian_install.apk" file and "Multidisabler-g97x_by_Ian.zip" file to your sd-card before you start!
2 - Download latest firmware via Samfirm or Frija or in any way you can, and unpack.
3 - Boot your phone to Download mode (Power+Bixby+VolDown) and remember to have the USB connected to your computer, it won't boot to DL-mode otherwise
4 - Keep autoboot etc in Odin settings, put each file in its place (AP, BL, CSC etc) and _dont_ use HOME_CSC, use CSC-only-file.
5 - After Odin is done, your phone will reboot automatically - let it! It can feel like forever, but let it do its restarts and stuff until you are in system-setup
6 - Do the setup as per usual, CONNECT TO WIFI but you can safely just say Skip on sign in and other stuff
7 - When setup says its all finished and you get to the standard launcher - go into Settings and enable Developer settings
8 - This step IS necessary.. If you don't do this step, you might get in pre-normal rrm state and you will have wait 7 days to try again: Enter Developer settings and look for the "OEM Unlock" switch - if you are rooting for the first time, Enable it. If you already have root since before or unlocked your bootloiader before, just confirm that its Enabled and graded out.
9 - If you already have an unlocked bootloader, skip to step 12. If not, continue with step 10.
10 - IF you never have unlocked your bootloader before, Power off the phone and boot into download mode again. You will see the long press volUp option for unlock bl, do that.
11 - IF you never have unlocked OEM before, boot the phone again, do the setup without signing in etc but connect to wifi, enable dev settings, go into dev settings and check that OEM now is enabled and grayed out.
12 - Reboot the phone in recovery mode (Power+Bixby+VolUp and keep holding until you are in stock recovery. Choose and do a factory reset.
13 - Reboot to bootloader with option in Recovery.
14 - Flash the tar you got (S10x-TWRP+Magisk_fixed_by_Ian.tar I Odin in the AP-slot. DISABLE auto reboot in Odin first!
15 - When the tar has flashed - Do as instructed on the phone, hold Power+VolDown for a few seconds and AS SOON AS THE SCREEN GOES BLACK -> quickly press power+bixby+volUp for a _long_ time, and I mean it can feel as if its a full minute! After a while you will see TWRP starting with its start screen, you can now let go and enter TWRP.
16 - FORMAT data, then WIPE data AND Cache. DO NOT LET IT REBOOT
17 - Flash "Multidisabler-g97x_by_Ian.zip" from SD card
18 - Go back to start screen of TWRP, Choose Reboot, Choose Recovery - YOU MUST ALWAYS CHOOSE REBOOT TO RECOVERY and _NOT_ system!
19 - Let the phone reboot into system, it will do some reboots it self, and again it will feel like it takes FOREVER - Just let it do its thing and DO NOT PRESS ANY KEYS!
20 - When your phone is finally done booting, just do the normal setup/signing for real this time.
21 - When you are done and in system/launcher, install "Magisk_Manager_Ian_install.apk" from SD card and verify that you now have Magisk Manager installed.
22 - Start Magisk Manager and say YES to what it says, it will do some stuff and then say "Rebooting in 5 seconds" - LET IT BOOT AND DO NOT TOUCH ANY KEYS this time either..
23 - Now when booted to system, start Magisk Manager and see that you have all green and its installed.
24 - Now you have root.
** Every time you reboot manually, be prepared to hold Power+Bixby+VolUP until you see the Samsung S10x-logo, then release and let it reboot, you will have root.
** Every time you power off the phone, when you power ON again, hold Power+Bixby+VolUP until you see the Samsung S10x-logo, then release and it will boot with root.
** Every time you want to enter TWRP-recovery, do as above but KEEP HOLDING THE KEYS UNTIL TWRP-start screen shows then release. Remember to choose reboot to recovery afterwards and you will boot with root.
** IF you screw up and forget or miss the key combo, just let it boot to system, immediately when system is up - reboot again and do the key combo and all is fine again.
This is me just trying to get an emergency first aid space, nothing more, I'm NOT trying to take any credits or dismiss Gieti94.
Thanks All

Duncan1982 said:
This is NOT my work (Ianmacd) and guide is written by rp4k all credits to him for his install method.
Click to expand...
Click to collapse
This is my tutorial and not r4pk. And I'd prefer that you use the download I provide here and no where else to make sure the right files gets downloaded when updated.
http://bit.ly/2VlcqYd
/P

Yea I can keep the OP updated, this is just an emergency first aid thread, thanks to Pickles for his well written guide.
I'm really not wanting to offend anyone, just for all to make life a bit easier....

very nice to have a reliable twrp solution, pitty that we don't have too many things to flash in recovery

Please remove the alternate download link, I have updated the multidisabler zip with a important update, v1.1 and the one download link for all is just for things like that, the other download link still have the old zip.
Very important that everyone uses Ian Macdonald's new v1.1 multidisabler script.
/P

I can update the mega link with the new disabler I reposted it to mega because I can't access Google @PiCkLeS
And yes I never said I wrote the guide I just added myself for helping people

rp4k said:
I can update the mega link with the new disabler I reposted it to mega because I can't access Google @PiCkLeS
Click to expand...
Click to collapse
I understand. But that doesn't seem to be a big problem for any one else and the bigger problem is that you risk having a link that is being used by the people only see it here and don't read anywhere else, or this message, and end up with old information or even worse, outdated files.
I can help you get the files on PM but please remove these links outside of my drive, which I maintain every day and keep up to date. It's not for vanity, it's for safety.
For now please edit your text and remove the link. All must use v1.1 of the multidisabler zip by Ian.
/P

Maybe this thread was a bad idea, as stated I am around and willing to keep things up to date
I know the importance, and how things are at present.

Duncan1982 said:
Maybe this thread was a bad idea, as stated I am around and willing to keep things up to date
I know the importance, and how things are at present.
Click to expand...
Click to collapse
Listen, just to be clear. I and I dont think Ian have a problem with you having this thread.
All I am worried about is the download link. Things can and are happening fast. If there are multiple sources for downloading files in this case, and today one was updated with important improvements, and there are many places to download from people can miss that and download old files that can cause big problems.
Keep the downloading to one good source and everything will be fine. The thread in it self can do much good by showing that there is an alternative, it works and right now almost 100 people in 24 hours have used it. Fantastic!
So I dont think it was a bad idea, I just dont want PM:s from people in a week or two asking why their device suddenly lost data, only to find out that they downloaded from a source that didnt have the latest files.
Thats all.
//P

PiCkLeS said:
Listen, just to be clear. I and I dont think Ian have a problem with you having this thread.
All I am worried about is the download link. Things can and are happening fast. If there are multiple sources for downloading files in this case, and today one was updated with important improvements, and there are many places to download from people can miss that and download old files that can cause big problems.
Keep the downloading to one good source and everything will be fine. The thread in it self can do much good by showing that there is an alternative, it works and right now almost 100 people in 24 hours have used it. Fantastic!
So I dont think it was a bad idea, I just dont want PM:s from people in a week or two asking why their device suddenly lost data, only to find out that they downloaded from a source that didnt have the latest files.
Thats all.
//P
Click to expand...
Click to collapse
I fully appreciate and understand that, the reason I created as I have plenty of time to maintain, and will keep it up to date I have been around for quite some time, if you look at my posts (search) I have had almost every device you can think of, currently have the Vivo IQOO also, I have enough experience to understand the important and implications.
I don't want your PM's to be going crazy so I'll fully respect your decisions and will keep everything updated also. But it is better if everything is tody and not one thing here and there, OP has been updated with your direct link, is this cool?
Just thought by creating this thread that it might help, my sincere and good intentions are hopefully evident

PiCkLeS said:
Please remove the alternate download link, I have updated the multidisabler zip with a important update, v1.1 and the one download link for all is just for things like that, the other download link still have the old zip.
Very important that everyone uses Ian Macdonald's new v1.1 multidisabler script.
/P
Click to expand...
Click to collapse
Can I install multi Disabler 1.1 withouth lost data?

zubi182 said:
Can I install multi Disabler 1.1 withouth lost data?
Click to expand...
Click to collapse
Yes just flash it in twrp, nothing will be lost.
/P

I assume this is only for the Exynos version? Or does it work for Snapdragon as well?

mistermidas said:
I assume this is only for the Exynos version? Or does it work for Snapdragon as well?
Click to expand...
Click to collapse
You have a working snapdragon root? How did you get past step #9 of launching stock recovery after you flashed magisk

rp4k said:
You have a working snapdragon root? How did you get past step #9 of launching stock recovery after you flashed magisk
Click to expand...
Click to collapse
Man... did you even read my comment???
I was asking if this would work for Snapdragon, not saying I got it to work. It doesn't mention if it's a method for both versions in the OP or not.

mistermidas said:
Man... did you even read my comment???
I was asking if this would work for Snapdragon, not saying I got it to work. It doesn't mention if it's a method for both versions in the OP or not.
Click to expand...
Click to collapse
Sorry I responded when I was half asleep. My fault.

I will try this out and post and update, i had no luck with previous twrp, always boot loops regardless of what i do.
My bootloader is unlocked but not grayed out. Can i still do it?

mercifool said:
I will try this out and post and update, i had no luck with previous twrp, always boot loops regardless of what i do.
My bootloader is unlocked but not grayed out. Can i still do it?
Click to expand...
Click to collapse
Yes, just do exactly all the steps and use the new files in the link and you will be fine.
//P

deleted

Carotix said:
hi ,
do you have the OEM switched to on?
if not , you need it ..... if you can't get it because you are waiting the 7 days , you can make this trick
open settings and set the date 8 days before ... then reboot
so you can enable OEM in developer settings
Click to expand...
Click to collapse
Hi there, are these instructions for Exynos only or can I apply it to Snapdragon as well, please advise. Thank!

[GUIDE][BEGONIA]Unlock Bootloader, Flash TWRP and Root[PROPER]

Code:
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
CLICK HERE TO READ THE MEGATHREAD BEFORE DOING ANYTHING TO YOUR DEVICE
Here we are guys... After searching here and there i found some working ways to Root this device without getting bricked. So let's discuss about these :
1. UNLOCKING BOOTLOADER :
- Download the Mi Unlock app to PC, and sign in with your Mi Account;
- Enable Developer Option in your phone by tapping the "Build Number" 7 times
- Go to Developer Options "Settings > Additional Settings > Developer Options
- Enable USB Debugging and OEM Unlocking
- Aslo add account in Mi Unlock Status (Can be found in Developer Options
- Install all the required drivers (adb drivers, vcom drivers etc.) In your PC [I'll link these below]
- Shut down your phone manually, and hold Volume down key and Power button to enter Fastboot mode
- Connect your phone to PC using USB cable and click "Unlock". In Mi Unlock Tool
- You will be given a specific time (168 hours mostly)
- Wait until that and redo Unlock process
- Woah you have Unlocked your device
2. FLASHING TWRP :
- Install Minimal ADB and fastboot on your PC [Link will be provided below]
- Download LR Team TWRP [This work for now, I'll provide link below and will update it after we have another proper TWRP]
- Put that TWRP in the file location of ADB and Fastboot (Right click on Minimal ADB and Fastboot icon on desktop and click on Open file location)
- rename that recovery to "twrp" for convenience (optional)
- Now Connect your phone to PC With USB Debugging on (keep phone on).
- Type
Code:
adb devices
and accept the pop up on phone's screen.
- Now reboot your phone to Fastboot mode
- Type
Code:
fastboot devices
- Your device ID will be visible on Screen.
- Then type
Code:
fastboot flash recovery twrp.img
- When it's done, Remove cable and Hold Power + Vol. Up when phone starts turning on leave the power button but keep pressing Vol. UP until TWRP splash Screen shows up.
- Done U did it
3. ROOTING :
- In TWRP mount System
- Go to Advanced > file manager
- then go to system_root > system and delete "recovery-from-boot.p"
- Go home and again go to advanced and Select "Close AVB2.0" swipe to confirm.
- Go back and select "Install Root"
- Here you go magisk 19.4 will be installed (U can chose any other versions afterwards.)
- Reboot the device to system.
- Ah Yes you did it
In case anything goes wrong ask me here or in official telegram group
LINKS
1. Mi Unlock tool
2. Minimal ADB and Fastboot
3. ADB Drivers for MTK
4. MTK USB Drivers
5. LR Team TWRP
If this helped you then hit the Thanks Button. Good Luck

Does it work for the china edition of the phone?

These are the the same instructions as found here https://forum.xda-developers.com/showpost.php?p=80604223&postcount=2
Why create a new thread without giving any credits. It's cluttering the forum.
In case anything goes wrong ask me here or in official telegram group
Click to expand...
Click to collapse
Reported, read the FAQ about telegram.

donkyshot said:
These are the the same instructions as found here https://forum.xda-developers.com/showpost.php?p=80604223&postcount=2
Why create a new thread without giving any credits. It's cluttering the forum.
Reported, read the FAQ about telegram.
Click to expand...
Click to collapse
Ah ok...i didn't check that thread... I just searched here and there and created a simple guide...

Robstir said:
Yes it does, I just rooted mine, Chinese 8gb RAM with Chinese ROM (no Google) only problem I just found was - can't make a TWRP back up on either storage, says can't make the folder, key unavailable.
I tried a couple of other methods which didn't work, so great stuff for posting here, I don't use Telegram, so it's really helped me, even if it is a duplicate, wind your neck in with the reporting Donkeywhatever!
Thanks OP
Click to expand...
Click to collapse
I'm glad to hear that it helped you...

Robstir said:
Thanks, it did brilliantly, any advice on the TWRP can't make the backup folder?
I'm keen to start pruning the system of the useless Xiaomi bloatware but not without a backup, flashed Magisk 20.1 also, working perfectly.
Click to expand...
Click to collapse
Wait for a proper TWRP. Cuz devs are already working on it

anybody tried that with chinese phone swapped to global rom?

Robstir said:
Yes it does, I just rooted mine, Chinese 8gb RAM with Chinese ROM (no Google) only problem I just found was - can't make a TWRP back up on either storage, says can't make the folder, key unavailable.
I tried a couple of other methods which didn't work, so great stuff for posting here, I don't use Telegram, so it's really helped me, even if it is a duplicate, wind your neck in with the reporting Donkeywhatever!
Thanks OP
Click to expand...
Click to collapse
Erm the issue i have with ChinaRom is that I cant use my own homescreen launcher... even with root I cant bypass it... so I have to be on Global ROM... but china variant with global rom causes boot loop.... and seeing that you are using the only TWRP available i think the results are the same...
---------- Post added at 05:42 AM ---------- Previous post was at 05:42 AM ----------
pritish1998 said:
Wait for a proper TWRP. Cuz devs are already working on it
Click to expand...
Click to collapse
Oo really? Gee can't wait....

so always bootloop issue with china/global device?

Bricked my China Rom Phone
I just bricked my phone - story here:
https://forum.xda-developers.com/redmi-note-8-pro/help/help-to-unbrick-china-redmi-note-8-pro-t4004681
So does anyone have any idea how I can unbrick? Should I REM out the antirollback check lines in flash_all.bat?
Any help is much appreciated! Thank you!

My phone came with the Global EU (EEA) version ROM, i have flashed Global (MI) version. Will this method still work or will it cause bootloop? I don't want to brick my device so asking in advance. I was lucky to just get stuck in bootloop with my previous try using a different recovery.
P.S. I used MiFlash Tool and flashed the ROM through Fastboot.

Hey Pritish1998,
I must admit, I was a little leery, after reading all the other threads about installing twrp and rooting and the horror stories they contained. Well, your instructions seemed fairly simple. I followed them EXACTLY... and I lost my ass, everything got wiped, my imei, everything!!!
Totally kidding, everything worked perfectly, I followed your steps exactly as stated. I did not loose any data, nothing, every app, all my downloads, everything is still on my phone. THANK YOU SO MUCH!
Also, TWRP, is still installed, didn't get wiped out by the stock recovery. I have root, and oh, I am on MIUI Global, on the United States phone I ordered off of Amazon. More Specifically, MIUI Global 11.0.1.0(PGGMIXM) Android Version 9 PPR1.180610.011. I received the MIUI 11 update about 3 days ago, and was still waiting the 160 some hours out for the bootloader unlock. I just got the bootloader unlocked about 3 hours ago. Went through numerous instructions and posts and this one seemed to make the most sense. I wasn't sure about MIUI 11 working, but fudge it, I thought I would just return the phone if I had a problem, but nope, you're instructions were clear and precise and I followed them to a tee and its working great and I have Magisk and did the safetynet update, and I'm all good.
I haven't updated Magisk to 20.1 though. Didn't want to press my luck.
Thanks so much bro, really, thank you.

this procedure worked as well on an indonesian 11.0.1. rom!!!
thx!

Hello good day! I have a question about TRWP:
1) Is it safe to install this TRWP f I am on 11.0.1.0 PGGEUXM?
Has anyone else done it since rom EEA instead of Gobal (MI)?
Thank you

Thank you very much, magisk works perfectly

donkyshot said:
These are the the same instructions as found here https://forum.xda-developers.com/showpost.php?p=80604223&postcount=2
Why create a new thread without giving any credits. It's cluttering the forum.
Reported, read the FAQ about telegram.
Click to expand...
Click to collapse
NOTHING WRONG WITH THE ABOVE POST BUT MORE INFORMATIVE. The link you claimed to be original is for the Chinese device only not for the Global. TWRP is also different. Check the files.

neoxcool said:
NOTHING WRONG WITH THE ABOVE POST BUT MORE INFORMATIVE. The link you claimed to be original is for the Chinese device only not for the Global. TWRP is also different. Check the files.
Click to expand...
Click to collapse
No need for caps lock. We can read.
It was initially a double post he just edited it later and changed it to a guide, which is fine.
It's the same procedure like initial Chinese twrp which was and is already posted here.

I'm on xiaomi.eu beta Android 10 but now i can't boot the recovery, any ideas?

.

Martin213 said:
You can't boot to stock recovery?
Be careful now i think you're one step ahead brick...
Click to expand...
Click to collapse
Phone is working normally but i want to change to stable, but the recovery is not booting.