Root Unlocked Mi A2 without fastboot - Xiaomi Mi A2 / 6X Questions & Answers

Hello,
I have a mi A2 device that I unlocked it and flashed TWRP on it. I flashed TWRP on both slots and everything was ok.
After that, my USB board or charging board damaged for unknown reasons and the repairman could not fix it, Also, its charging board is very rare in my area and I can't find it.
So, my phone is never detected by PC but it can be charged, and I can't use fastboot commands.
A few days ago without knowing that DotOS has dedicated recovery, I flashed it with TWRP on slot A, and now I can't use TWRP on slot A anymore. But I think the TWRP is still installed on the slot B.
I really need root my device, so please help me.
1- Is there anyway to change slots without fastboot?
2- Can I install TWRP from anyway other than fastboot?
I tried to install TWRP zip file from DotOS recovery but it does not accept any file except DotOs official updates.
I can use adb commands with wireless debugging feature in android 11.
DotOS recovery options (Advanced option Does not include a useful option, just include reboot options and view logs)
{
"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"
}

1. Download dotos offical update
2. Download the twrp in .img form
3. Rename twrp to recovery.img
4. Put the recovery.img into the dotos zip. If it asks to replace file, just replace it
5. Flash

LR7875 said:
1. Download dotos offical update
2. Download the twrp in .img form
3. Rename twrp to recovery.img
4. Put the recovery.img into the dotos zip. If it asks to replace file, just replace it
5. Flash
Click to expand...
Click to collapse
DotOS not include recovery.img in zip file, but it installed recovery too.
Does this solution still works?
DotOS zip file:

Oh no the dotos recovery and system is compressed in the payload bin file
What will happen if you delete the payload.bin and replace it with the twrp recovery.img

LR7875 said:
Oh no the dotos recovery and system is compressed in the payload bin file
What will happen if you delete the payload.bin and replace it with the twrp recovery.img
Click to expand...
Click to collapse
Not works, can't flash

So can you boot into system

And did you adb sideload?

LR7875 said:
And did you adb sideload?
Click to expand...
Click to collapse
I can't use adb sideload in recovery, because of damaged usb, I can boot system but can't use sideload command in system

Related

install recovery using adb

Windows users should already have :
<<adb drivers>>
{
"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"
}
and
<<usb drivers>>
------------------------------------------------------------------------------------------------------------------------------------------------------
so u did root. u unlocked bootloader. u flashed a recovery and u installed a new rom. one day u start "digging" things to see if u can delete all the unwanted files so u make the phone faster and accidentally u deleted an important file and now it cant boot and it cant go into recovery. you are wondering what you CAN do now ! The answer is : Everything !
You can either go back to stock rom or
you can re-flash the recovery and then reinstall the rom.
1. Download the platform tools for your machine ( windows , linux or mac-os ). Here i have the adb fastboot for you.
2. Copy the recovery image to a location on your computer thats easier for you. The recovery image should have .img extension. If it is in a zip file, extract the .img file from it before proceeding.
3. Connect the phone to the pc and open cmd inside the fastboot folder you downloaded ( windows ). The others not on windows must use cd [path to their desktop,inside the platform tools where they see the adb file].
** If you are on a boot loop but the pc gets to recognize the phone even for a second then
4. Type
i) adb reboot-bootloader
ii) fastboot flash recovery recovery.img ( the command is: fastboot flash recovery [recovery image path/filename] )
5. When its done , reboot. Hold Volume down and power button to see if u get in recovery mode. :highfive:
Install the rom now the way you already know. There are many guides for that so i won't make a new.
cheers :good:
**Windows users can use this fastboot to unlock bootloader too. Lite fastboot commands guide provided here
**Linux users don't even need to download it , they can just directly download it from their terminal
I hope this thread helps a little those that dont know what to do when they delete an important file. *Pictures coming soon*

[GUIDE] How to get back the stock kernel of Nexus 5 (LMY47I)

Hi everybody,
This is my second post at XDA and as an answer to my first post (List of Lollipop 5.1 custom kernels for the Nexus 5) This post guides you how get back the stock kernel (LMY47I).
Always remember: You flash at your own risk! This post is only for the Lollipop build LMY47I!
There are two ways to get the stock kernel back, the first with a custom recovery like TWRP or CWM and the second with FASTBOOT (UNLOCKED BOOTLOADER is imortant)
1. Download the STOCK-KERNEL.ZIP in the attachments and extract it (for example with WINRAR or 7-ZIP). Then you have two files. The only one you need is the Kernel.zip file! Copy it to your phone, then switch to the custom recovery navigate to the Kernel.zip file and flash it. Now reboot the phone. The stock kernel was succesfully flashed.
2. Download the STOCK-KERNEL.ZIP in the attachments and extract it (for example with WINRAR or 7-ZIP). Then you have two files. The only one you need is the boot.img! If you haven't downloaded the Android SDK yet download it now! Switch to folder where you installed the SDK and navigate to "platform-tools". Copy the boot.img file into it. Now reboot your phone into FASTBOOT (Bootloader) with POWER Button + VOLUME DOWN and connect your phone to your PC wait until the drivers are installed if you get an error install the latest Google drivers. Open CMD navigate to "platform-tools" and type: "fastboot flash boot boot.img". Reboot your Phone and disconnect the USB-Cable. The stock kernel was succesfully flashed.
Error
Can't flash the zip, says "Unable to execute"
falcon.prj said:
Can't flash the zip, says "Unable to execute"
Click to expand...
Click to collapse
What is the name of the .zip that you tried to flash?
some custom kernels also modify/replace other files in the system partition, so is flashing just boot.img enough to return to stock kernel then?
Wakamatsu said:
What is the name of the .zip that you tried to flash?
Click to expand...
Click to collapse
Kernel.zip
And the problem was with TWRP, sorry
and thanks!
iamelton said:
some custom kernels also modify/replace other files in the system partition, so is flashing just boot.img enough to return to stock kernel then?
Click to expand...
Click to collapse
Nope. So this thread is kinda pointless. You need to reflash your rom after hellscore, code blue, elementalx and probably franco (not used franco since kitkat)
From hells thread -
{
"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"
}
Sent via tapatalk from my cataclysm'd Lollipooop Nexus 5

[O][P]Unoficial TWRP 3.4.0 & Root

{
"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"
}
TWRP 3.4.0 & Root
Root and absolutely working TWRP 3.4.0 from nemo-nemo!
Oreo & Pie​
Features
In the new TWRP and Root installation method described below, there is no need to format the Data partition to remove the encryption.
Thanks to TWRP's built-in FB Encryption (File Based Encryption), the contents of the Data partition are available with encryption preserved. The folders on the external memory have the correct names and structure.
- Forced DM-Verity removal
- Forcibly removing the protection of Motorola Hab
- Now there is no need to sew additional decoders when installing TWRP and receiving Root or when installing custom firmware!
- Full access to Oem partition modification directly from the running system using Root Explorer, which previously was only possible with Root obtained through SuperSu.
Installation Instruction
1. Download archive with files for installation TWRP and Magisk Google Drive
2. Extract files:
- twrp-3.4.0-nash-nemo-nemo.img to the folder adb with drivers adb & fastboot ;
- twrp-installer-3.4.0-nash-nemo-nemo.zip, Magisk-disable-dm-verity-v20.4.zip to the SD Card..
This is a special modification of Magisk for Motorola devices. You can read about it here Link
3. Boot the phone in fastboot mode, connect it to a PC and perform the following commands:
Code:
fastboot boot C:\adb\twrp-3.4.0-nash-nemo-nemo.img
4. The phone restart in to Recovery.
5. Go to the "Install" section. Click on "Select Storage" button, select Micro SD card, OK. Install twrp-installer-3.4.0-nash-nemo-nemo.zip and Magisk-disable-dm-verity-v20.4.zip.
6. Reboot into the system.
Attention! Backup creation after TWRP and Magisk installation should be done only after full booting into the system. Otherwise restoration of the Data partition backup will be interrupted with an Error 255.
Сredits:
nemo-nemo
TeamWin-TWRP
ilia3367
Thanks a lot, everything works fine. The only issue I had was the russian language on the first boot in TWRP, but it is easy change to english.
forgottennick said:
Thanks a lot, everything works fine. The only issue I had was the russian language on the first boot in TWRP, but it is easy change to english.
Click to expand...
Click to collapse
Well, this is understandable. This TWRP was created by 4PDA developers.
do I have to flash Magisk-disable-dm-verity whenever I want to install a custom rom?
If you need a Root then of course yes.
Very good, works, thanks!
Will this method work for the Verizon version of the Z2 Force?
ilia3367 said:
If you need a Root then of course yes.
Click to expand...
Click to collapse
Willi this work on the Verizon Z2 Force?
will4958 said:
Willi this work on the Verizon Z2 Force?
Click to expand...
Click to collapse
Verizon and Root concepts are not compatible.
hey, im getting a bootloop when trying this. no idea why?

General [CLOSED] ⚗️AOSP(SHARED)CrDroid V8.8 - UNOFFICIAL by DigiGoon

A12.1​Flashing instructions​adb reboot bootloader
fastboot flash boot_ab boot.img
fastboot flash vendor_boot_ab vendor_boot.img
fastboot reboot recovery
in recovery wipe data(factory reset)
then select apply update from adb
and from pc sideload rom.zip and reboot
DOWNLOAD
https://dl.androidrom.dev/?dir=roms/crdroid/milahaina
{
"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"
}
Others AOSP ROM
https://forum.xda-developers.com/t/shared-aosp-rom-a13-by-ipsbhangu.4483171/
https://forum.xda-developers.com/t/aosp-shared-evolutionx-v6-7-unofficial-by-preet0608.4486623/​
why this rom isn't in the developement thread?
Is it because it's shared?
Edmondo Occhipinti said:
why this rom isn't in the developement thread?
Is it because it's shared?
Click to expand...
Click to collapse
Nope,as long as the developer does not publish it on XDA it will remain shared. (I also shared the Siberia and I deleted the thread as soon as the official one arrived). That's all.
NOSS8 said:
Nope,as long as the developer does not publish it on XDA it will remain shared. (I also shared the Siberia and I deleted the thread as soon as the official one arrived). That's all.
Click to expand...
Click to collapse
So shared roms go on the General section?
Edmondo Occhipinti said:
So shared roms go on the General section?
Click to expand...
Click to collapse
yeap ,because i am not a developer.
Hello.
Someone try it ?
I tryied to install it, but a get an error when i try to flash boot a_b.img, cmd said that s not a *. Img
Cengiz67 said:
I tryied to install it, but a get an error when i try to flash boot a_b.img, cmd said that s not a *. Img
Click to expand...
Click to collapse
Cmd:
fastboot boot twrp.img
Power shell
./fastboot boot twrp.img
then in Twrp go to Advanced - flash current TWRP.
So :
Flash and boot twrp ok
Tryin' to do :
fastboot flash boot_ab boot.img
fastboot flash vendor_boot_ab vendor_boot.img
Say that is not booting and vendor img
Cengiz67 said:
So :
Flash and boot twrp ok
Tryin' to do :
fastboot flash boot_ab boot.img
fastboot flash vendor_boot_ab vendor_boot.img
Say that is not booting and vendor img
Click to expand...
Click to collapse
Img must be in the same folder as the command.
try to install platform tools and put the img inside.
check syntax.
I did it but doesnt work
Cengiz67 said:
I did it but doesnt work
Click to expand...
Click to collapse
Post a screenshot of the CMD
Install with commands or with the TWRP but not both.
OK when i try again i ll post it
Does screen mirror work properly in this rom?
Or what are the current and known bugs?
Anyone use this ROM as a daily driver?
Update
https://dl.androidrom.dev/?dir=roms/crdroid/milahaina
THREAD LOCKED
Requested by OP.
Regards,
shadowstep
Senior Moderator

[GUIDE]Xiaomi.EU ROMs Flashing Guide All Devices [Linux-Only]

Requirements:
Your device's bootloader must be unlocked.
Prerequisites:
Ubuntu/Debian/Ubuntu-Based Distros:
Open terminal
Type sudo apt install adb
Once that is installed.
Type sudo apt install fastboot.
Done.
Fedora:
Open terminal.
Type sudo dnf install android-tools.
Let it install and done.
OpenSUSE:
Download this official package from here according to your version :
https://software.opensuse.org/download.html?project=hardware&package=android-tools
(Use either one the add repository and install manually or grab binary packages directly options.)
Click to expand...
Click to collapse
MIUI 12 (Weekly And Stable)
{
"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"
}
Go to the sourceforge link of the rom and see the date of your rom. In this case it's alioth.
See the date of your rom . Now go to xiaomiformwareupdater.com and select your device. Then click download.
New page will appear. Type fastboot in the searchbar of the page. Now see global rom the date closest to the release of the xiaomi.eu rom and download.
Unzip the rom file to the root of home directory and connect your device to fastboot mode and open a terminal in the rom folder and run the command:
./flash_all.sh
A terminal window will popup and close after 15-20 min approx when flashing is done.This will delete your data.
Let the device boot into MIUI.
Once it boots power it off . Then press the vol down + power button until fastboot in orange letters appear.
TWRP method:
Flash twrp using fastboot.
Boot into twrp.
Go to wipe and format data.
Then factory reset in wipe.
Do not wipe anything in advanced wipe !
Copy the zip file to a fat32 formatted sdcard or usb.
Connect sdcard or usb to device.
Go to install , select storage , sd/usb, select rom zip and flash.
Once flashing done , wipe dalvik.
Reboot to recovery.
Reboot to system.
Done.
Fastboot:
Unzip rom file to root of home directory.
Go into folder.
Run fastboot installation script in folder
Open terminal window in the folder
If updating from older rom.
Run command in terminal:
./linux_fastboot_update_rom.sh
Done.
If installing first time.
Run command in terminal:
./linux__first_install_with_data_format_.sh
NOTE(For Stable And Recovery ROMs):
CHECK THE XIAOMI.EU THREAD FOR KNOWING IF YOUR ROM IS FASTBOOT OR RECOVERY.
Alternatively If you want you can flash india , eea , turkey , etc variants of stock rom instead of global , then flash xiaomi.eu according to the instructions above. But keep in mind that the release date of stock rom that you are flashing should be closest to the release date of xiaomi.eu weekly rom.
Install magisk after first boot and reboot after installing magisk to get rid of system lags.

Categories

Resources