Develop Bugs

Root Armani in 2018

Method 1:-
Download Custom Recovery for armani in your pc and rename it to recovery.img
and download root zip and paste it in your sdcard
Download 15 seconds adb & fast drivers and follow the instructions....
In pc type the following commands by opening cmd from shift+right click and open command prompt here after connecting the device to pc
Code:
adb devices
after successful install of drivers you will see the device listed in that
Code:
adb reboot bootloader
After rebooting into fastboot mode type the following commands
Code:
fastboot flash recovery recovery.img
after successful flashing of recovery then type this
Code:
fastboot reboot recovery
Flash SuperSU/Koush superuser in your TWRP/CWM/Philz recovery
Method 2:- Download Kingo ROOT and root
Method 3:- Download Kingo ROOT pc version in your pc and load it and connect your device to pc and root....
Method 4:- Download KingRoot and click to root....if it fails in first attempt, try atleast 5 times...

Yes these are indeed the best methods to root this phone.
Also, note that Magisk will not work for the stock MIUI because the phone has Android 4.4 and Magisk probably requires 5.0+. So, Magisk should be used for newer custom ROMs.
HemanthJabalpuri said:
I want to root my MIUI 9 armani in 2018.....
I don't have PC
Click to expand...
Click to collapse
Also, like you had said earlier, if you don't have a PC due to some reason, you can use another phone or tablet for that purpose (to flash the custom recovery). I've read somewhere that most Android devices having 5.0 and below came preloaded with adb fastboot binaries (for newer Android phones, you can easily obtain the binaries online and add them into the /system/bin folder if it is rooted) and hence you can connect your Redmi to this other device using an OTG cable and use the shell (any terminal app) to issue the commands. The only important thing to be considered in this approach is that the other (host) device should have a big enough battery to be able to provide sufficient current to the Redmi phone such that it should not get disconnected during the process.
This method is usually ignored by people, but it really works.

Reserved

Reserved

Code:
$ fastboot reboot recovery
fastboot: usage: unknown reboot target recovery
Cannot issue the last command.
When I flash TWRP and reboot nothing happens. Same Mi Recovery is present.
I am on MIUI 9. Not rooted. I am trying to get a custom recovery but I fail. Please help.

blazzer12 said:
Code:
$ fastboot reboot recovery
fastboot: usage: unknown reboot target recovery
Click to expand...
Click to collapse
Are you sure recovery was flashed properly?
Try this while in fastboot mode :-
Code:
fastboot devices
Make sure that your device is listed properly.
Try this
Code:
fastboot erase recovery
fastboot flash recovery <path to recovery img>
Then reboot using
Code:
fastboot reboot recovery
If still doesn't work out, try to directly boot into recovery image
Code:
fastboot boot <path to recovery img>
If still doesn't work out, then there might be a problem with the fastboot binary on the PC, try to reinstall the latest version of it on the PC and try again.
---------- Post added at 22:03 ---------- Previous post was at 21:55 ----------
blazzer12 said:
When I flash TWRP and reboot nothing happens. Same Mi Recovery is present.
Click to expand...
Click to collapse
If the issue is specific to TWRP Recovery, try to flash other recoveries. For example, older version of TWRP or maybe try Philz Touch recovery as well.

Yes, the fastboot devices is being listed. Still #2 didn't work. But #3 worked perfectly.
So for me flashing recovery didn't work. I had to temporarily boot into the recovery and then again flash the recovery from there.
Thank you for the help. :good:

Now we can root with Magisk too...
https://forum.xda-developers.com/ap...v7-universal-systemless-t3473445/post78829088
Note:- Magisk v22.1 is the last version to support Android 4.4.2

[root] redmi 4x root

Firstly this is my first helpful post so be gentle.
How to root the Redmi 4x
First off I am not accountable if your fry your device or shut down the power grid etc.
Alright. It took me some research and trial and error but I found the CORRECT way to root the Redmi 4x.
Needed files:
Lasted version of the magisk zip. DO NOT USE ANY VERSION OF SUPER SU. IT CAUSES BOOTLOOP.
TWRP for Redmi 4x
Lazy patcher.
Adb and fastboot files.
Step one:
Ensure your bootloader is unlocked. If not search XDA for a thread there are multiple threads showing you how to do it. Once that's done let's move on.
Step 2:
Alright let's get going with flashing TWRP first.
You need to enable developer options and enable USB debugging on your Redmi. To do that go to settings>about devices>scroll down>continually tap on MIUI version and a toast notification will tell you that you are now a developer>go to developer option under the more options tab and enable USB debugging.
Step 3:
Now that we've got USB debugging we can connect to Adb. Firstly download all aforementioned files and place them in the same folder as your Adb installation for ease of access. Now open up a command prompt in that folder by either typing "cmd" into the address bar or shift+right click and select open command window here. Now you need to connect your phone via USB to your computer and ensure it is connected by entering "adb devices" into the command window.
Step 4: commands
Here are the commands you will need to enter. I recommend making a backup of everything first.
Enter these commands
adb reboot bootloader
Fastboot flash recovery (put TWRPS full file name here including the .zip)
Wait for it to finish.
Now DO NOT BOOT TO SYSTEM.
Enter in fastboot reboot and hold volume up to enter recovery. If you boot to system it will remove twrp and you will have to reflash it.
Once in Twrp check the box to allow modifications and slide right.
Go to advanced and the ADB sideboard.
Now flashing magisk and lazy patcher.
Reconnect your phone to the computer and leave Twrp on sideload mode.
Enter this command
adb sideload (lazy patchers full file name here)
Now I made sure my phone still booted to system after this because every time I flashed SuperSU it would boot loop.
Once your back in sideload mode let's flash magisk.
adb sideload (magisks full file name here).
Once it's done select reboot to system from Twrp and enjoy your root!!
Again I say do not use any flashable root other than magisk. I don't know if I had a specific problem but every single one I tried resulted in bootloop.

magisk instructions

guys please give me noob friendly instructions for installing magisk latest ver on my lenovo p2 15.1 latest build .

Same

First make sure you have USB debugging enabled on your phone, then install ADB on your PC. Connect the phone to the PC and in the installation folder (ADB > platform-tools) shift right click and choose Open command window here. Type adb devices and authorize your PC on the phone. Download the ROM and extract boot.img from it, transfer it to your phone. On the phone install Magisk Manager and patch the boot.img (Install > Patch boot image). Transfer patched_boot.img back onto the PC (to the ADB > platform-tools folder), then boot your phone into fastboot (VOL down and POWER buttons). Repeat the Open command window here step and type fastboot flash boot patched_boot.img. Reboot your phone (fastboot reboot). You are now rooted on custom ROM.

After installing magisk , do I need to install any module to prevent boot loop like f2fs loop module etc .

Check if you can install modules. If you're facing problems, then you will need to change a few things. The "cannot mount magisk_merge.img" issue for example can be solved by patching and flashing boot image from here https://forum.xda-developers.com/lenovo-p2/development/kernel-f2fs-upstreamed-kernel-twrp-t3845976. I tried tinkering with modules for it and ended up bricking my phone. I would also recommend using TWRP from this thread, it got rid of my second problem (which I now forgot).
Just remember that you will need to flash the patched custom kernel after any ROM update.

Rooting 7T without TWRP / Pre-patched Magisk boot.img for 10.0.13.HD65AA (Global)

For those who can't root via TWRP or somehow lost root while updating (like I did), I have a patched boot image to aid others in this endeavor. This is a boot.img from a T-Mobile 7T which I had converted to the Global ROM, extracted and patched by Magisk after applying the latest update (10.0.13.HD65AA). Fully tested and working!
Instructions:
Unzip and place it in a convenient folder (ie, C:/adb/ or whatever's easy to remember.
Open a cmd prompt and navigate to your fastboot/adb folder.
Then run the command
Code:
fastboot boot boot.img
Your phone will be "temp-rooted" once it boots. If you haven't already, install Magisk Manager, then flash Magisk itself (ALWAYS do direct install!).
Don't install any modules yet. Just reboot when prompted after the Magisk flashing process is done.
Profit!
Download from Google Drive
[I dunno where else to upload this that XDA would consider "safe," so GDrive it is, I suppose.]
Spoiler: Process for manually patching the boot.img without TWRP:
Requirements: Stock device with unlocked bootloader only (no other mods), most recent OTA update applied and system rebooted. Fastboot and ADB Windows executables.
1) Enable advanced reboot and usb debugging in developer options.
2) Reboot to bootloader.
Code:
adb reboot bootloader
3) Boot to twrp
Code:
fastboot boot twrp.img
(or whatever you named it).
4) Once booted, enter:
Code:
adb shell
dd if=/dev/block/bootdevice/by-name/boot of=/tmp/boot.img
exit
5.5) Copy file to the PC:
Code:
adb pull /tmp/boot.img stock_boot.img
6) Reboot phone back to Android.
6.5) Copy boot.img back to phone:
Code:
adb push stock_boot.img /sdcard/boot.img
7) Make sure you have a data connection.
8) Install Magisk Manager.
9) Select option to install Magisk (not the Magisk App). Choose "Select and Patch a File."
10) Point to the boot.img.
11) It will do its thing then come back with a done message. File /sdcard/download/magisk_patched.img will be created.
12) Copy this file to your PC, either using MTP or ADB.
Code:
adb pull /sdcard/download/magisk_patched.img
13) Reboot the phone into bootloader mode again.
Code:
adb reboot bootloader
14) Boot the patched boot from step 12:
Code:
fastboot boot magisk_patched.img
15) Launch Magisk Manager again. You should see the current version available and the installed version below that now. If all is good, choose to install/update Magisk, then "Direct install" and reboot when finished.

I guess you posted it in wrong section as mentioned the file is for Oneplus 7t ?

>Akshay< said:
I guess you posted it in wrong section as mentioned the file is for Oneplus 7t ?
Click to expand...
Click to collapse
OH! You're right. I goofed. I'll ask a mod to move it.

This will delete all the data from the phone + bootloader needs to be unlocked?

Brontok said:
This will delete all the data from the phone + bootloader needs to be unlocked?
Click to expand...
Click to collapse
Flashing this doesn't erase your data, unlocking the bootloader does, though (and is necessary to flash this).

GuyInDogSuit said:
Flashing this doesn't erase your data, unlocking the bootloader does, though (and is necessary to flash this).
Click to expand...
Click to collapse
never mind!
someone already did!
https://forum.xda-developers.com/showpost.php?p=83780229&postcount=12
thanks anyway!

Will this work for 10.0.13 tmobile ? Thanks

gershee said:
Will this work for 10.0.13 tmobile ? Thanks
Click to expand...
Click to collapse
You might be better off pulling the boot.img yourself and patching it. I can't guarantee that this will even work on the T-Mobile version. But if you want to test it, just boot the img and root from Magisk once it loads. If it bootloops, well, then we know.
EDIT: Updated OP with instructions on how to patch the boot.img.

GuyInDogSuit said:
You might be better off pulling the boot.img yourself and patching it. I can't guarantee that this will even work on the T-Mobile version. But if you want to test it, just boot the img and root from Magisk once it loads. If it bootloops, well, then we know.
EDIT: Updated OP with instructions on how to patch the boot.img.
Click to expand...
Click to collapse
Thanks!
Worked like a charm.

Recovering data on a DEAD Redmi Note 8 PRO

Hello,
I hope this is the right section for this post.
I've been using a Note 8 Pro with zero issues until one week ago when I accidentally dropped the phone in the water.
After a few seconds submerged the display turned off and I felt an intense heat coming from the zone of the battery.
Having no chance to recover the phone (tried with Isopropyl Alcohol too) I decided to open it and manually dry/clean each component, having seen the situation inside gave me the phone is dead but I still want to recover some pictures/data from it.
Before opening the open Minitool was not detecting any device on my Windows Laptop, after cleaning each component Minitool is instead detecting the phone via USB, but I still can't extract any data because the "Usb debugging" option is not tuned on (and no the device is not rooted).
Is there any option to extract data from the phone? There's a way to turn on USB Debugging via ADB on a non-rooted phone?
Thanks,
Andrea.

how about trying your luck with a service ? most of the time they do have access to special programs, which have a better functionality than adb.

Thanks for the hint, but I am not happy with the idea of someone playing with my data

1. Try reboot phone to recovery
2. Connect it to your computer (download Platform-tools)
3. In the folder with Platform-tools open cmd
4. In cmd - adb shell
5. cd storage/emulated/0
6. ls
7. Now, using the commands, drag files from your phone to your PC

Thanks for your hint.
No luck so far, I think because the phone is not in recovery mode.
I can hear the phone starting up several times (hear the jingle) so I think it's in a reboot loop and I don't know how to boot it into recovery mode wo a working display (tried with power/volume up combination with no luck).
From the windows taskbar I can see that the phone is recognized for a few seconds before it restarts.
EDIT: trying to switch the phone on with the combination "power/volume down" brings to a kind of stable state and I can now see the phone in the windows taskbar recognized as a generic "android device". Still no luck when trying to access the phone as there's no device in windows and no device obtained through "adb devices" command.
EDIT1: I think that the phone is in "FASTBOOT" mode. If I type "fastboot devices" I can see it detected but still can't access it.

Any idea? Should I give up?

If it's popping up and down you need something to keep track.
You can try my UsbLog.exe (in the sig), it just sits there and shows what devices appear (if they have a driver) and disappear.
Try these to see if anything is working:
Code:
C:\>fastboot devices
C:\>fastboot getvar all
C:\>fastboot oem device-info

Yes it's popping up and down when it's booted in recovery mode whilst is stably connected when in fastboot mode but in this case I can't access the internal memory of the device.
I didn't get the purpose of logging the devices connecting to the USB as I can see the device connected for a while and correctly recognized as Redmi Note 8 pro but as it keeps popping out windows have no time to show it's folder.
As for the code you wrote: i will try asap but already tried with "fastboot devices" and I get the phone correctly listed but still can't access its memory as told.

Renate said:
If it's popping up and down you need something to keep track.
You can try my UsbLog.exe (in the sig), it just sits there and shows what devices appear (if they have a driver) and disappear.
Try these to see if anything is working:
Code:
C:\>fastboot devices
C:\>fastboot getvar all
C:\>fastboot oem device-info
Click to expand...
Click to collapse
After rebooting the phone in fastboot mode I can see it recognized as a generic android device from windows (still can't access the storage folder of the device).
fastboot devices----> I get the device listed with a series of numbers/letters
fastboot getvar all---> I get a list of information on token/token version/partition type and size/baseband/bootloader etc.
fastboot oem device-info----> FAILED (remote: unknown command)
So I think it's clear that the device is in Fastboot mode and instead is in a boot loop when started in revocery mode.
Is there a way to extract data from fastboot mode?
Thanks,
Andrea.

If you put a custom recovery on it in the first place you can try reflashing recovery from fastboot.
Fastboot doesn't allow you to read anything.
oem device-info is obviously an oem command that might not be on any device.
You've got a Mediatek processor. That has some low level equivalent to Qualcomm EDL, but I have no experience with that.
If you can get there you can download the user data partition, but it's probably encrypted. Also no experience with that.
The easiest is if you can get the system to mount/decrypt the partition.
You've tried the normal system too?
Is this A/B? Have you tried changing slots?
How much time does it stay up in recovery? Do you have ADB? Maybe try:
Code:
# stop recovery
Does that prevent it from looping?

So I should try to flash a custom recovery like TWRP for example?
What you mean with "normal system too"?
Changing slots you mean changing usb port?
It stays in recovery less than one second so I can't give any command via ADB.
EDIT: cant' flash any custom recovery because the bootloader is locked.
If I Try to unlock the bootloader via MiUnlock I get a warning saying that all data will be erased.
Any idea on how to unlock the bootloader wo wiping all the data?

Sephiroth79 said:
So I should try to flash a custom recovery like TWRP for example?
What you mean with "normal system too"?
Changing slots you mean changing usb port?
It stays in recovery less than one second so I can't give any command via ADB.
EDIT: cant' flash any custom recovery because the bootloader is locked.
If I Try to unlock the bootloader via MiUnlock I get a warning saying that all data will be erased.
Any idea on how to unlock the bootloader wo wiping all the data?
Click to expand...
Click to collapse
There is a mediatek bootloader unlocked you just have to boot in Brom mode and it'll unlock it please follow this
PS: press all buttons

MysticNoOb said:
There is a mediatek bootloader unlocked you just have to boot in Brom mode and it'll unlock it please follow this
PS: press all buttons
Click to expand...
Click to collapse
My bootloader is unlocked!
Thank you very much.
Now I am going to try to flash a custom recovery mode via fastboot in order to access the internal memory of the phone.
EDIT: I've just flashed twrp-3.6.2_9-0-begonia.img but still can't boot into recovery mode.
Any hint on how to extract data from the system now?

You really want to boot the normal system because that's the best way to get decrypted data.
I realized that you don't have ADB enabled there.
You should look at B. Kerler's https://github.com/bkerler/mtkclient/
If you can pull the boot image off your device then I might be able to fix it so that you have ADB.
You'd have to flash it back in fastboot or mtkclient.
You can also pull a copy of userdata off the device with mtkclient.
As far as booting into recovery, there's a way.
Here's how, if you don't have A/B (that is you flashed TWRP into recovery and not recovery_a or recovery_b)
then you can fastboot flash a special file into the misc partition and it wil boot into recovery next reboot.
To return things to normal you have to flash the empty file to the misc partition.
Code:
C:\>fastboot flash misc misc-rec.img
C:\>fastboot reboot
Only do this if you don't have partitions that end in _a or _b

I really don't know if I have partitions A and B as you mentioned and I think there's no way to check actually.
I confirm I don't have "USB Debugging" active on the phone.
So if I understand correctly I should do the following:
- Flash misc-reg.img via Fastboot
- Boot into recovery just rebooting the system after flashing the above file;
- use MTKclient to dump userdata or boot image to enable ADB on (I will need help with mtkclient I suppose).
Is it correct?
EDIT: flashed TWRP first and misc-rec then rebooted via Fastboot/Reboot but nothing happens.

Sephiroth79 said:
My bootloader is unlocked!
Thank you very much.
Now I am going to try to flash a custom recovery mode via fastboot in order to access the internal memory of the phone.
EDIT: I've just flashed twrp-3.6.2_9-0-begonia.img but still can't boot into recovery mode.
Any hint on how to extract data from the system now?
Click to expand...
Click to collapse
TWRP cant boot because you used wrong one. Search again in that unlock bootloader channel and use suitable one.

Kirasu2080 said:
TWRP cant boot because you used wrong one. Search again in that unlock bootloader channel and use suitable one.
Click to expand...
Click to collapse
Hmmm, I am almost sure that the TWRP I've flashed was listed under Redmi Note 8 pro page. Can you please indicate more precisely where should I sera
EDIT: I think I've downloaded and flashed the correct TWRP file.
@Renate can you please detail your method so I can try to extract data from the phone?

Sephiroth79 said:
Hmmm, I am almost sure that the TWRP I've flashed was listed under Redmi Note 8 pro page. Can you please indicate more precisely where should I sera
EDIT: I think I've downloaded and flashed the correct TWRP file.
@Renate can you please detail your method so I can try to extract data from the phone?
Click to expand...
Click to collapse
1/Yeah it's official. You "flashed correct TWRP." Downgrade to Miui Android 9 (_9 in it's name) to boot into that TWRP and lose your data.
2/In unlock bootloader video above, search other video in his channel playlist and find TWRP video suitable for your Miui version.

Kirasu2080 said:
1/Yeah it's official. You "flashed correct TWRP." Downgrade to Miui Android 9 (_9 in it's name) to boot into that TWRP and lose your data.
2/In unlock bootloader video above, search other video in his channel playlist and find TWRP video suitable for your Miui version.
Click to expand...
Click to collapse
Can't find the right video, can you kindly send me a link (I am on the latest Miui version and I am in Europe)?
In all the videos I've seen on his page he is using the device to install TWRP etc.
I think I just need the correct TWRP version for my MIUI release and then I'll flash TWRP and misc-reg.img. Is it right?

Sephiroth79 said:
Can't find the right video, can you kindly send me a link (I am on the latest Miui version and I am in Europe)?
In all the videos I've seen on his page he is using the device to install TWRP etc.
I think I just need the correct TWRP version for my MIUI release and then I'll flash TWRP and misc-reg.img. Is it right?
Click to expand...
Click to collapse
Use brp 3.5.2 v3.1 or V3.6 to decrypt Miui 12.5