I will try to describe exactly what I did. I warn you that if you want to repeat this, then do everything at your own risk!
Original message
1. The cleanest installation possible
We do a COMPLETE cleanup and format the DATA in TWRP not lower than version 3.4... then reboot into bootloader and connect to the PC with a good cable. Run Fastboot on the PC in the command line in turn enter the following commands:
fastboot devices
fastboot erase all
fastboot reboot bootloader
2. Install motoXT1799-2_GLOBAL_2021.02.20_oreo.zip
Use the firmware from here: motoXT1799-2_GLOBAL_2021.02.20_oreo
3. Install Magisk
The latest version of Magic-v22.0.apk must be installed and Magisk-v22.0.zip
4. Go to the developer menu
In the developer menu, we give permissions to unlock the OS bootloader, as well as give permission to debug via USB.
5. Run adb Fastboot on the command line
The phone must be connected to the PC via USB. We enter the command adb devices on the smartphone, a dialog box should appear to allow debugging this device or something like that, respectively, we give permission.
Next, we reboot into the bootloader with the command adb reboot bootloader
6. Blocking
Previously, we copy the stock recovery.img to the folder with adb Fastboot
Enter the commands:
fastboot flash recovery recovery.img
fastbo fastboot flashing lock
We reboot into the system.
7. Delete Magisk as unnecessary
To do this, go to the program select delete see two items select first "restore partitions or something like that" then delete.
8. Do a factory reset
If everything is done correctly, we get a device with Oreo Android 8.1.0 as if it came out of the factory.
{
"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"
}
Related
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*
Hello community I need your help!
I was running CM 12.1 on my tablet and I wanted to make a factory reset, well... I did and because the tablet has to restart, it did and since then I got stuck on the TeamWin logo page
{
"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 I cannot go to the option, it just stays there
This are some of the output I get from ADB
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>adb devices
List of devices attached
0123456789ABCDEF recovery
And if I uses "adb reboot fastboot" it does, but then the output of "adb devices" and "fastboot devices" is null
I have tried a lot commands, but I always get the same results <waiting for device>
My drivers are working.
I already unplug/plug/restart the table but the <waiting for device> is still there
I still tried with this tool http://forum.xda-developers.com/showthread.php?t=1951254 but it doesnt work, event trying a fastboot command manually doesn't work.
Any ideas!! please help!
DarkWolfSLV
I have the exact same problem i have been trying all day to find a fix but no luck D;
Fixed it DUDE I Kinda Found A Fix i can know access TWRP DDD
1. Download This https://docs.google.com/uc?id=0B4lZE...xport=download
2.connect kindle to pc and boot up the kindle normally
3.extract the Zip and open tha bat file
4. select option 4 It should then say waiting for device
5.open up cmd adb and type adb reboot-bootloader then it should say clearing cashe or user data then after about a min power off ur device then power it back on
6.then it should now say clearing cashe or user data On of them then after a min switch of ur device then back on and team win should load the next problem is that i cant send files through to my kindle so i cant flash anything. maybe i need newdrivers cna someone link me to one.
Edit; reboot The device again and it should boot into cm12 but once again im stuck in a boot loop and unsure of what to do the boot loop is just the cm12 logo it does not go onto the actual os
nvm lol wait about 5 mins it should boot.
How To Unlock Bootloader Of YU Yureka Black
{
"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"
}
This is a short tutorial to explain how to unlock Bootloader of YU YUREKA BLACK
REQUIREMENTS :
1. YUREKA BLACK Phone
2. Download USB Drivers From Here . USB Drivers Windows & Install It on Your Machine.
3. ADB & Fastboot Drivers Installed In your Machine.
a. ADB & Fastboot Driver For Windows
b. On Linux Machine Run these commands to Install ADB & Fastboot Drivers
"sudo apt-get install android-tools-adb && sudo apt-get install android-tools-adb"
PROCEDURE OF UNLOCKING BOOTLOADER :
1.Connect your device in ADB Interface & from CMD run " adb reboot bootloader" Command to enter Fastboot Mode.
2.Once Device is in fastboot mode verify availability of Device in fastboot mode by running "fastboot devices" command in cmd.
3. Run "fastboot oem unlock-go" to Unlock the Bootloader of YUREKA BLACK.
(You can also run "fastboot oem unlock-tinno" this command will not wipe your data)
4. After running above command device will boot into recovery mode and data will be wiped automatically .
5. Once data is wiped device will automatically reboot to system with unlocked Bootloader.
6. Now u can flash TWRP - Official TWRP for YU Yureka Black
Amazing share dev, keep up to great work as always
Not able to enter fastboot
Hi,
Following works
"adb devices"
"adb reboot recovery"
However when I do
"adb reboot bootloader"
device restarts and gets stuck at "YUREKA BLACK" "POWERED BY android".
Also when I start device with Volume Down+Power button, I get into FFBM.
It just has variety of test options and no boot to bootloader/recovery.
Two button at bottom are shutdown and reboot.
Device is manufactured in 2019.
Any ideas how to get into bootloader mode.
Edit: Solved, issue with driver in fastboot mode.
I've followed the process outlined here. After installing the ZIP, it rebooted, but went back to recovery. When I said reboot system, it said No OS installed.
So, I tried to start over by formatting data and then copying the zip again via ADB Push. Then the trouble starts. After adb push, which takes about 5 minutes, it says
Code:
failed to copy 'xiaomi.eu_multi_HMNote10Pro_V12.5.3.0.RKFMIXM_v12-11.zip' to '/sdcard/xiaomi.eu.zip': write failed: No space left on device
After that, the data partition seems corrupted. Whenever I go to Install, it shows 0 bytes. Upon Googling I found a solution by formatting to ext2 and back to ext4. Then, it shows again as 100000MB. However, adb push every time fails with same problem.
For some weird reason, I can push to /data. But still running into same problem after installing ROM and rebooting, it goes back into recovery.
I also tried to sideload, but then I run into this issue:
Code:
D:\Tools\ROMs>adb sideload xiaomi.eu_multi_HMNote10Pro_V12.5.3.0.RKFMIXM_v12-11.zip
loading: 'xiaomi.eu_multi_HMNote10Pro_V12.5.3.0.RKFMIXM_v12-11.zip'
* cannot read 'xiaomi.eu_multi_HMNote10Pro_V12.5.3.0.RKFMIXM_v12-11.zip' *
So, I'm stuck with a device without any ROM. Any suggestions please?
Did you ask in the MIUI EU forums as well? Since there would be more ppl familiar with these issues than here.
I'm also interested in this since I prefer EU roms. Also you need a specific TWRP version which I believe is still in alpha stage for the 10 Pro since its still a new device. There should be a TWRP thread somewhere here where you can also ask.
I just got my 10 pro and need to wait a few more days to unlock BL, then I will be flashing an EU rom, hence my interest. Hope you find a solution.
Use TWRP from here:
https://forum.xda-developers.com/t/4248449/
fastboot reboot bootloader
fastboot boot TWRP_file_name.img
Format Data, type yes.
{
"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"
}
Reboot to recovery.
The internal storage should be visible.
Connect phone to PC and put ROM into phone.
Flash ROM, format data, yes
Reboot to system.
If above not work, make your phone under fastboot mode, Mi-Flash, and flash your stock fastboot MIUI. Don't lock your bootloader.
Prerequisites:
Bootloader unlocked (Unlock Guide, Video Tutorial)
Magisk Manager
ADB and Fastboot tools (Download, Setup Guide)
Steps:
For Rui 2.0
Goto TWRP (Download link and Install Guide) or any other custom recovery (ofox)
Rename Magisk-v25.2.apk to Magisk-v25.2.zip
Flash Magisk-v25.2.zip and reboot
For Rui 3.0
Get boot.img and vbmeta.img from export firmware (Download, Convert to SP tool guide)
Use magisk to patch the boot image:
{
"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"
}
Connect the device to the PC via USB Cable.
Now transfer the patched boot file(magisk_patched.img) and vbmeta.img from your device to the platform-tools folder on your PC.
Inside the same folder, right-click on an empty area while pressing the ‘Shift’ key.
Select the option ‘Open PowerShell window here.
Or you could also head over to the platform-tools folder on your PC, type in CMD in the address bar, and hit Enter. This will launch the Command Prompt.
Type in the below code to make sure the device is successfully connected (an alpha-numeric code suggests successful connection):
Code:
adb devices
Now type in the below code to boot your device to fastboot/bootloader mode:
Code:
adb reboot bootloader
Next, type the below code to flash the patched boot image file:
CSS:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
fastboot flash boot magisk_patched.img
fastboot reboot
Credits:
Thanks to @ManshuTyagi for TWRP and @topjohnwu for Magisk
PS: I have tested this on only RMX 3031, and it may work on GT neo(CN) (RMX 3357) without any edits. If it works for you, please let me know, will update the post accordingly.
and how to update RUI 3 afterwards without a full wipe?
good day, any guide on how to obtain the Boot.img and vbmeta.img file