Related
Hello guys,
i have a bricked rooted oneplus x
I had issues with the rooted rom so i flashed the newest stock rom via twrp
The phone boots up and showed the usual otimizing apps message. After the proccess is done it just the usual "let me helpt set up your phone page" and then restarts
I cant acces twrp anymore and when i try to acces the stock recovery it just shows a oneplus logo
I do have access to fastboot though (i hope that leaves some hope)
I have tried the MegaUnbrickGuide here in the forum but i wasn't able to install the drivers i need for that method
One more thing whenever i try
Code:
fastboot boot recovery.img
i get the "remote dtb not found" message
Does that have to do with developer options not being unlocked?
Any ideas on how to just get some form of working os installed on the device
(i dont care wheter rooted or not at this point have been trying stuff for hours now)
regards
Jan
First download Minimal ADB and Fastboot and install it.
Go into fastboot mode.
1. Re-unlock your bootloader using the command - fastboot oem unlock
2. After doing that, download the latest version of TWRP(which at the time of writing this is 3.1.0) and rename it to 'recovery.img'
3. Open a command window in the place you have downloaded the recovery by pressing the shift key and right clicking and then choosing the option Open Command WIndow Here... Flash the recovery using the command fastboot flash recovery recovery.img
4. Boot into it using the command fastboot boot recovery.img
5. If it still gives 'remote dtb not found' then follow this guide: https://forum.xda-developers.com/oneplus-x/help/opx-remote-dtb-solution-t3480274
6. If it boots into recovery, your phone is now fine and go ahead and flash whatever ROM you want.
Cheers!
Hi,
I've been trying to follow instructions to flash Lineage OS* on my Samsung Galaxy S3 (i9300) currently running Android 4.3. Would appreciate any help.
I followed the Lineage wiki tutorial to download platform tools (ADB and fastboot).
I'm following detailed instructions from how-to-geek [link removed], as the ones on getdroidtips seem garbled. I've downloaded all of the relevant software to my PC, except for SU, and I have enabled developer mode and USB debugging.
Running the adb devices command shows my phone as a device, but when i try 'fastboot oem unlock', fastboot doesn't work at all. Initially fastboot wasn't recognised as a command, as Windows virus blocker prevented the fastboot.exe from being unzipped, so i manually moved that file over. Now the command prompt just says 'waiting for device' forever.
Any ideas?
Thanks
Hello
Hello there, You don't need to unlock the bootloader as this model is already unlocked. The SHV-E210S has to be unlocked. So you just need to flash Chainfires SuperSU through Odin and install custom recovery.
https://forum.xda-developers.com/ga...2012-cf-root-6-4-supersu-cwm5-5-t1695238/amp/
can anyone pls help with how to root the Lenovo TB-x306f
i already unlocked the bootloader but that's as far as i was able to go with it.
i want to also like to install a recovery to flash the evolutionx rom if someone can pls help me and others that needs the same help.
GOD BLESS
I second that. There's nothing out there.
What I tried was to download the original ROM patch the boot.img with magical, replace in LMSA download folder and start a rescue. Didn't help. Got boot loop.
Ok, maybe a bit more details on what I tried already:
1. Enabled developer options. Good.
2. OEM unlocked. ADB connected. Good.
3. Boot to bootloader working. Good.
4. fastboot not listing the device after fastboot devices. Not good.
5. Googling around, found an universal root method with Magisk. Good.
6. Donwloaded, installed and ran RSA (Lenovo Rescue and Smart Assistant). Connected to device. Good.
7. Entered Rescue and using that downloaded the original ROM. Good.
C:\ProgramData\LMSA\Download\RomFiles\TB_X306F_S100134_210120_BMP
8. Copied boot.img to device, installed MagiskManager, patched image with magisk, downloaded the image to PC, replaced the original boot image with the patched one. Good.
9. Started the Rescue procedure in RSA. Rom flased. Good.
10. Bootloop. Bad.
No idea why would that not work, any help, pointers, ideas appreciated.
EDIT: There's a new ROM version now: TB_X306F_S100152_210205_BMP
For a preface, I have the same Tablet as OP. I tried to unlock the bootloader, following seemingly every guide out there but, no success so far. I've enabled debugging, activated OEM unlock and, adb detects my device but, after I send it to fastboot (adb reboot bootloader), no more commands work. I've updated the driver in Manager as one guide suggested but, still nothing.
I used command (fastboot OEM unlock) to continue but nothing. What am I doing wrong?
So just a tip for those that are looking for a guide to do a complete bootloader unlock for TB-X306F, there isn't one. I found a bunch of different ways to go about unlocking the bootloader from different Lenovo devices. First thing is that you need Minimal ABD Fastboot v1.4.3 if Platform Tools or LeTools doesn't work. Use CMD with admin rights, not PowerShell.
Everything else to unlock it is the same from all the guides out there. Make sure to use "fastboot flashing unlock" when unlocking instead of "fastboot oem unlock" or "fastboot oem unlock-go" if they dont work.
Second tip is for root when installing the Magisk patched boot image. While you're getting the boot.img, make sure to also grab the vbmeta.img from the ROM folder and place it in the Minimal ADB Fastboot folder where you will be using CMD. Do all the steps to get the patched boot image. Once you got the boot.img patched, enter fastboot then enter the command "fastboot --disable-verification flash vbmeta vbmeta.img" This will disable verification needed to boot correctly. After that, enter the command "fastboot flash boot <name of .img>" like normal to flash the patched boot.img from magisk. Then fastboot reboot.
This is what I did to get my TB-X306F unlocked and rooted. YMMV.
Different threads that I read to get to where I got, credit goes to them:
LENOVO Tab M10 Plus
After receiving my LENOVO Tab M10 Plus TB-X606F I tried to root my tablet. my Firmware version is TB-X606F_RF01_200103 - loaded the Lenovo Rescue and Smart Assistant (V5.0.0.25) - enabled OEM unlock - downloaded magisk - installed ADB now my...
forum.xda-developers.com
Lenovo M10 HD 2nd Gen X306F boot loop if boot.img is patched - android 10 · Issue #3832 · topjohnwu/Magisk
I recently installed magisk manager and extracted the boot.img from tb-x306f_rf01_200926 upon doing a fastboot flash boot magisk_patched.img , the machine goes into a boot loop. Am I doing somethin...
github.com
TWRP for LENOVO Tab M10 FHD - TB-X606F?
Hello, Possessing two tablets of this brand, I was wondering if a custom recovery existed for this one, I can look everywhere on all the forums, Russian, English, etc ... But, I do not find. If anyone can create one with this SOURCE CODE from...
forum.xda-developers.com
Lenovo tab m8
Hello, Any root and custom ROM available for the Lenovo tab m8 tb8505 variant? The stock rom feels good for the price but if something better to make the tab feel nicer.. Thanks :) :)
forum.xda-developers.com
By any chance can u pls.... Make a video on the steps u explained including on where to get that file needed. Pls thank u and GOD BLESS YOU. If u can find the time to do it .
I apologize for asking for so much help on this.
I too would very much care to see a video of the process but, I have no problem trying it first hand to myself. This tablet is just weird. It can be detected but, as soon as I boot into fastboot, it can't pick it up anymore even though, I had grabbed all of the recommended tools so far such as the fast Boot and the bundle.
A detailed guide would be good enough too
Following @doink_doink 's post (and some bootloops after...) I finally managed to root my Lenovo M10 HD 2 gen (TB-X306X) with magisk. I'll attempt to write a simple guide for who's still interested with rooting this kind of devices since there's not much literature online.
Rooting Lenovo M10 X306X (should also work for other models)
I am by no means held responsible for eventual damage you can inflict on your device, follow the underlying steps of your own accord.
Desktop Tools:
Minimal ADB and Fastboot
Lenovo Rescue Smart Assistant (LRSA from now on)
MTK (Mediatek) Preload Drivers (If your device isn't listed in fastboot)
Mobile Tools:
Magisk Manager App
Steps:
1 - From LRSA click on "Rescue" Tab
2 - Select the model of your tablet and then download
3 - From "Downloads" in the top right corner of the LRSA, click on "Open" to go into the LRSA download folder
4 - Connect your device and set it into USB Debugging and File Transfer
5 - Copy boot.img from LRSA download folder into the device's download folder
6 - Run Magisk Manager App on your device
7 - From Magisk Manager App choose "Install" on the right side of Magisk
8 - Choose the only option "Select and patch a file"
9 - Choose the boot.img you previously copied into the device's download folder
10 - Copy the new file "patched_boot.img" or similar name to the folder where Minimal ADB and Fastboot was installed
11 - Copy the file vbmeta.img from LRSA download folder to Minimal ADB and Fastboot folder
12 - From your device's settings enable developer options and enable OEM Unlock
13 - Execute a cmd session with administrator privileges
14 - Execute in the cmd: adb reboot bootloader (if everything went right the device should reboot in fastboot mode)
15 - Execute in the cmd: fastboot flashing unlock
16 - Execute in the cmd: fastboot --disable-verification flash vbmeta vbmeta.img
17 - Execute in the cmd: fastboot flash boot patched_boot.img
18 - Execute in the cmd: fastboot reboot
The device should correctly reboot and everything should be good to go now.
If something bad happens, like a bootloop or something, turn off the device and use the LRSA to rescue your device.
I don't get around to checking my email as often as I used to so I just now got around to seeing this but, I will try this after I get home from work in 10 hours plus time. If I can get this to successfully work, I will be flat out amazed. I had gotten to the point where I had just given up any and all hope that I would get it to work.
Show
Chairos said:
Following @doink_doink 's post (and some bootloops after...) I finally managed to root my Lenovo M10 HD 2 gen (TB-X306X) with magisk. I'll attempt to write a simple guide for who's still interested with rooting this kind of devices since there's not much literature online.
Rooting Lenovo M10 X306X (should also work for other models)
I am by no means held responsible for eventual damage you can inflict on your device, follow the underlying steps of your own accord.
Desktop Tools:
Minimal ADB and Fastboot
Lenovo Rescue Smart Assistant (LRSA from now on)
MTK (Mediatek) Preload Drivers (If your device isn't listed in fastboot)
Mobile Tools:
Magisk Manager App
Steps:
1 - From LRSA click on "Rescue" Tab
2 - Select the model of your tablet and then download
3 - From "Downloads" in the top right corner of the LRSA, click on "Open" to go into the LRSA download folder
4 - Connect your device and set it into USB Debugging and File Transfer
5 - Copy boot.img from LRSA download folder into the device's download folder
6 - Run Magisk Manager App on your device
7 - From Magisk Manager App choose "Install" on the right side of Magisk
8 - Choose the only option "Select and patch a file"
9 - Choose the boot.img you previously copied into the device's download folder
10 - Copy the new file "patched_boot.img" or similar name to the folder where Minimal ADB and Fastboot was installed
11 - Copy the file vbmeta.img from LRSA download folder to Minimal ADB and Fastboot folder
12 - From your device's settings enable developer options and enable OEM Unlock
13 - Execute a cmd session with administrator privileges
14 - Execute in the cmd: adb reboot bootloader (if everything went right the device should reboot in fastboot mode)
15 - Execute in the cmd: fastboot flashing unlock
16 - Execute in the cmd: fastboot --disable-verification flash vbmeta vbmeta.img
17 - Execute in the cmd: fastboot flash boot patched_boot.img
18 - Execute in the cmd: fastboot reboot
The device should correctly reboot and everything should be good to go now.
If something bad happens, like a bootloop or something, turn off the device and use the LRSA to rescue your device.
Click to expand...
Click to collapse
Hi I have the same device I have my patched boot.img and vbmeta.img but when I adb reboot bootloader fastboot commands don't work anymore fastboot flashing unlock says <waiting for device> and every other command. I have latest fastboot drivers google USB drivers I've done everything I have no hope please reply and help me
Hello231 said:
Show
Hi I have the same device I have my patched boot.img and vbmeta.img but when I adb reboot bootloader fastboot commands don't work anymore fastboot flashing unlock says <waiting for device> and every other command. I have latest fastboot drivers google USB drivers I've done everything I have no hope please reply and help me
Click to expand...
Click to collapse
* I have the TB-X306F***
Hello231 said:
Show
Hi I have the same device I have my patched boot.img and vbmeta.img but when I adb reboot bootloader fastboot commands don't work anymore fastboot flashing unlock says <waiting for device> and every other command. I have latest fastboot drivers google USB drivers I've done everything I have no hope please reply and help me
Click to expand...
Click to collapse
I'm currently experiencing the same issue. I have done everything, followed every step provided by Chairos and it wont surpass beyond the <Waiting for device> message. I just got this device today for a fair price, hoping I could root the device, and typical me forgot to research if it was officially compatible with TWRP.
cratee said:
I'm currently experiencing the same issue. I have done everything, followed every step provided by Chairos and it wont surpass beyond the <Waiting for device> message. I just got this device today for a fair price, hoping I could root the device, and typical me forgot to research if it was officially compatible with TWRP.
Click to expand...
Click to collapse
I got it for free for online classes but that's not the problem twrp is out for this device unofficialy but many say that it works, anyways good luck on u mate I gave up on rooting this device I can't do it anymore I've been trying for 4 months but nothing still if I had the Chance and the correct guide I would definitely do it
cratee said:
I'm currently experiencing the same issue. I have done everything, followed every step provided by Chairos and it wont surpass beyond the <Waiting for device> message. I just got this device today for a fair price, hoping I could root the device, and typical me forgot to research if it was officially compatible with TWRP.
Click to expand...
Click to collapse
Make sure you have the latest MTK usb drivers.
Hello Everyone,
I apologize for the delay but I didn't get notified of your replies.
I also got the waiting for device problem, but as @Yahoo Mike says, it's the MTK USB drivers that are used to communicate with the device in fastboot mode. Latest drivers should do.
Let me know if you're still experiencing the problem after installing the latest MTK drivers, since it depends on which motherboard the tablet has but all models should use mediatek.
Worked like a charm! Thanks.
Can anyone please confirm if there is a TWRP even unofficial IMG out there? And if any kind soul could share the file too I would be so grateful thanks
worked beautifully ...
just the installation of the latest MTK drivers is not very typical. however, you can follow this guide to install MTKL drivers and disable the driver signature enforcement
Download MTK USB Drivers for Windows 11, 10 - Driver Easy
To flash files to your MediaTek chipset phones, you need to have the latest MediaTek drivers installed. We'll show you how to install the MTK driver easily.
www.drivereasy.com
When you Restart: go to Advanced Options to find the Driver Signature Disablement option
I received yesterday my TB-X306X, with Android 10 and with software version S100184_210325_BMP. First thing to do was to unlock and root the tablet, without any issue, thanks to clear indications found on this thread.
Has anybody been able to find working TWRP for this tablet ?
So, I recently tried to root my Redmi 5 phone and install Lineage OS into it. This is my first time doing it, so I believe I may not have understood the words I had been reading well. Due to this, I'll try to be as descriptive as possible with the actions I had taken that led to my device being stuck.
I had followed this guide, for the most part: https://www.getdroidtips.com/lineage-os-17-xiaomi-redmi-5/
As per the guide, I performed the following actions:
Enabled the developer options
Registered my device to my Mi account
Enabled USB debugging, OEM unlocking
Rebooted in fastboot mode using the ADB tools through CMD (adb reboot bootloader)
While in fastboot mode, I used the Mi Unlock tool to unlock my device.
As per my understanding, these steps would unlock the bootloader. I rebooted my device, set it up (the phone behaves as if freshly booted) and checked the settings menu after enabling developer options again. It shows the bootloader is already unlocked and that Mi Account status is also unlocked. I enabled the USB debugging options again and carried on with the guide.
I then downloaded the rosy TWRP file (version 3.5, I think).
I even downloaded GApps and Lineage 18.1 OS
I tried to copy the above files into my Redmi 5 internal storage
The Lineage and GApps file failed to copy, but I was able to copy the TWRP file
One thing to note here, I am not sure if my USB cable is faulty or if my phone's micro USB port is faulty or if my laptop's USB ports are faulty. When the phone is connected to my PC, it is extremely lousy. If I shake the cable even a bit, it disconnects and reconnects. When I try to use the file explorer to copy the files from my laptop to the android phone, it usually fails for large files or large quantities of small files. I believe this was the reason behind the failure. Nonetheless, I decided to do the TWRP part first.
The guide said to reboot in recovery mode and that would take me to TWRP recovery mode. Well, it did not! It took me to a menu that had the following options:
Reboot
Reboot to System
Back to Main Menu
Wipe Data
Wipe All Data
Back to Main Menu
Connect to MIAssistant
I assumed I had entered recovery mode incorrectly, so I followed the link in the guide on how to enter recovery mode. It suggested using the ADB tools.
I used the command: adb reboot recovery
It did the same thing that I had done. So, I assumed that that is the recovery mode, but I am unable to enter TWRP recovery mode. There was another link that would show me how to do this.
I followed that link and downloaded the files that was mentioned. However, the guide tells little to nothing on what to do with these files. The only file that was used was the rosy twrp file.
I enabled the USB debugging mode on my phone.
Opened CMD from the folder with ADB
Entered the command: adb reboot bootloader
Phone enters fastboot mode
Entered the command: fastboot devices
I can see that a device is connected
Entered the command: fastboot flash recovery rosy-3-5.img (I renamed it for convenience, I believe that was allowed because every website had different name for their file)
I then rebooted into recovery mode by first rebooting it normally: fastboot reboot
Then entering the command: adb reboot recovery
It still showed the same old recovery menu. Nothing had changed. I looked around the internet and found that I could boot with the TWRP image by entering the command: fastboot boot rosy-3-5.img
This opened the screen that I was expecting, but it did not open the chinese menu at all. It directly went to the screen that had options such as Install, Wipe, etc.,
I rebooted normally and then tried to transfer the GApps file and Lineage file into my phone. As usual, it was failing. I tried to use the adb push command and it still failed but with an error saying "permissions denied"
At this point, I looked up how to get root permissions and I learnt that I had to root my device. I looked up how to root with Magisk and SuperSU. The guides all required me to boot in TWRP recovery and then install the files from my phone. Unable to transfer the files to my phone, I uploaded the files to my google drive, and manually downloaded into my phone. I boot up rosy (TWRP recovery, or so I think) using ADB tools. Unfortunately, it does not recognize any of the files in my internal storage. Everything is empty.
Defeated by this, I decided to let it go. I had a factory reset Redmi 5 at the time. I then watched a video that showed how to root with Magisk, but wasn't specific to Redmi 5, it was a generic video for android devices.
I installed the magisk manager apk into my android phone.
Then I copied the boot.img file from the Lineage folder into my android device. Despite the OS being 600 MB large, the boot.img file was only 11 MB.
Anyway, I patched the boot.img file using magisk manager.
It created a file called magisk-patched_1pTOD.img (I'm a bit unsure of the name, but it was similar to that).
The video said that I should copy this file into my laptop and then reboot my phone into fastboot.
Once in fastboot, I had to enter the command: fastboot flash boot magisk-patched_1pTOD.img
I believed that this would root my device and grant me root access. I don't know what my actions were actually supposed to do, but my device is unusable for all intents and purposes. I rebooted the device and it shows the Mi logo for a brief moment and there's no light. An empty dark screen, it's not even a black screen. It's like the display fails to work. I can switch into recovery mode and into fastboot mode but normal reboot did the same.
Thinking that I bricked my phone, I tried to unbrick it.
I downloaded the fastboot rom for Redmi 5 rosy and then installed the Mi Flash tool along with the drivers for it.
I then selected the correct ROM folder (it kept showing up as can't find flash script until I was in the right folder for it)
Rebooted my phone into fastboot mode
Hit refresh on the Mi Flash tool
It showed my device
I chose Clean All option
I hit flash
It goes up till 97%-ish and then fails with an error saying "flash system error".
However, I noticed that now, I can see that the Mi Logo doesn't disappear now. I can still go into recovery mode and fastboot mode, but normal reboot takes me to the permanent Mi Logo Screen. I cannot even shut it down. It auto reboots to the Mi Logo Screen if I do so.
I connected my device to my laptop and then opened the ADB tools.
I entered the following command to see if it's recognized by adb:
adb devices
It did not. I then switched to fastboot mode manually by pressing the Vol Down and Power buttons.
Then entered the following to see if it is recognized in fastboot mode:
fastboot devices
It showed my device there. So I used the following command to reboot and see if it is recognized in fastboot again:
fastboot reboot
While it shows the Mi Logo screen, I typed the command:
fastboot devices
It still shows my device.
I concluded that my device is in an infinite fastboot loop. I cannot boot it up normally. I cannot flash the Redmi 5 ROM into it either. I cannot use my phone.
If anybody has actually gone through this entire mess that I made, and has figured out what went wrong or at least how to fix it, please help me.
Message me on telegram @benzoylperoxide
Hope I could help you with this situation.
If you got data, download fastboot rom based on nought and fastboot rom 9.5.30
Download latest miflash tool from miglobe website.
Install proper drivers from miunlock tool zip file.
And Hope for the best.
Ping me tommorow at anytime.
Good night Bro
incertam7 said:
So, I recently tried to root my Redmi 5 phone and install Lineage OS into it. This is my first time doing it, so I believe I may not have understood the words I had been reading well. Due to this, I'll try to be as descriptive as possible with the actions I had taken that led to my device being stuck.
I had followed this guide, for the most part: https://www.getdroidtips.com/lineage-os-17-xiaomi-redmi-5/
As per the guide, I performed the following actions:
Enabled the developer options
Registered my device to my Mi account
Enabled USB debugging, OEM unlocking
Rebooted in fastboot mode using the ADB tools through CMD (adb reboot bootloader)
While in fastboot mode, I used the Mi Unlock tool to unlock my device.
As per my understanding, these steps would unlock the bootloader. I rebooted my device, set it up (the phone behaves as if freshly booted) and checked the settings menu after enabling developer options again. It shows the bootloader is already unlocked and that Mi Account status is also unlocked. I enabled the USB debugging options again and carried on with the guide.
I then downloaded the rosy TWRP file (version 3.5, I think).
I even downloaded GApps and Lineage 18.1 OS
I tried to copy the above files into my Redmi 5 internal storage
The Lineage and GApps file failed to copy, but I was able to copy the TWRP file
One thing to note here, I am not sure if my USB cable is faulty or if my phone's micro USB port is faulty or if my laptop's USB ports are faulty. When the phone is connected to my PC, it is extremely lousy. If I shake the cable even a bit, it disconnects and reconnects. When I try to use the file explorer to copy the files from my laptop to the android phone, it usually fails for large files or large quantities of small files. I believe this was the reason behind the failure. Nonetheless, I decided to do the TWRP part first.
The guide said to reboot in recovery mode and that would take me to TWRP recovery mode. Well, it did not! It took me to a menu that had the following options:
Reboot
Reboot to System
Back to Main Menu
Wipe Data
Wipe All Data
Back to Main Menu
Connect to MIAssistant
I assumed I had entered recovery mode incorrectly, so I followed the link in the guide on how to enter recovery mode. It suggested using the ADB tools.
I used the command: adb reboot recovery
It did the same thing that I had done. So, I assumed that that is the recovery mode, but I am unable to enter TWRP recovery mode. There was another link that would show me how to do this.
I followed that link and downloaded the files that was mentioned. However, the guide tells little to nothing on what to do with these files. The only file that was used was the rosy twrp file.
I enabled the USB debugging mode on my phone.
Opened CMD from the folder with ADB
Entered the command: adb reboot bootloader
Phone enters fastboot mode
Entered the command: fastboot devices
I can see that a device is connected
Entered the command: fastboot flash recovery rosy-3-5.img (I renamed it for convenience, I believe that was allowed because every website had different name for their file)
I then rebooted into recovery mode by first rebooting it normally: fastboot reboot
Then entering the command: adb reboot recovery
It still showed the same old recovery menu. Nothing had changed. I looked around the internet and found that I could boot with the TWRP image by entering the command: fastboot boot rosy-3-5.img
This opened the screen that I was expecting, but it did not open the chinese menu at all. It directly went to the screen that had options such as Install, Wipe, etc.,
I rebooted normally and then tried to transfer the GApps file and Lineage file into my phone. As usual, it was failing. I tried to use the adb push command and it still failed but with an error saying "permissions denied"
At this point, I looked up how to get root permissions and I learnt that I had to root my device. I looked up how to root with Magisk and SuperSU. The guides all required me to boot in TWRP recovery and then install the files from my phone. Unable to transfer the files to my phone, I uploaded the files to my google drive, and manually downloaded into my phone. I boot up rosy (TWRP recovery, or so I think) using ADB tools. Unfortunately, it does not recognize any of the files in my internal storage. Everything is empty.
Defeated by this, I decided to let it go. I had a factory reset Redmi 5 at the time. I then watched a video that showed how to root with Magisk, but wasn't specific to Redmi 5, it was a generic video for android devices.
I installed the magisk manager apk into my android phone.
Then I copied the boot.img file from the Lineage folder into my android device. Despite the OS being 600 MB large, the boot.img file was only 11 MB.
Anyway, I patched the boot.img file using magisk manager.
It created a file called magisk-patched_1pTOD.img (I'm a bit unsure of the name, but it was similar to that).
The video said that I should copy this file into my laptop and then reboot my phone into fastboot.
Once in fastboot, I had to enter the command: fastboot flash boot magisk-patched_1pTOD.img
I believed that this would root my device and grant me root access. I don't know what my actions were actually supposed to do, but my device is unusable for all intents and purposes. I rebooted the device and it shows the Mi logo for a brief moment and there's no light. An empty dark screen, it's not even a black screen. It's like the display fails to work. I can switch into recovery mode and into fastboot mode but normal reboot did the same.
Thinking that I bricked my phone, I tried to unbrick it.
I downloaded the fastboot rom for Redmi 5 rosy and then installed the Mi Flash tool along with the drivers for it.
I then selected the correct ROM folder (it kept showing up as can't find flash script until I was in the right folder for it)
Rebooted my phone into fastboot mode
Hit refresh on the Mi Flash tool
It showed my device
I chose Clean All option
I hit flash
It goes up till 97%-ish and then fails with an error saying "flash system error".
However, I noticed that now, I can see that the Mi Logo doesn't disappear now. I can still go into recovery mode and fastboot mode, but normal reboot takes me to the permanent Mi Logo Screen. I cannot even shut it down. It auto reboots to the Mi Logo Screen if I do so.
I connected my device to my laptop and then opened the ADB tools.
I entered the following command to see if it's recognized by adb:
adb devices
It did not. I then switched to fastboot mode manually by pressing the Vol Down and Power buttons.
Then entered the following to see if it is recognized in fastboot mode:
fastboot devices
It showed my device there. So I used the following command to reboot and see if it is recognized in fastboot again:
fastboot reboot
While it shows the Mi Logo screen, I typed the command:
fastboot devices
It still shows my device.
I concluded that my device is in an infinite fastboot loop. I cannot boot it up normally. I cannot flash the Redmi 5 ROM into it either. I cannot use my phone.
If anybody has actually gone through this entire mess that I made, and has figured out what went wrong or at least how to fix it, please help me.
Click to expand...
Click to collapse
Flash system error in MiFlash? Probably the stock rom you downloaded and extracted is corrupted.
Please try flashing MIUI 9 for your Redmi 5.
Yeah, users have had issues with twrp being replaced by stock rom.
For TWRP,
fastboot flash revovery (recovery name.img)
Fastboot boot (recovery name .img)
After that flash your custom rom after wiping system,boot, vendor, data and cache, Internal format might be needed if it's encrypted.
Then, after custom rom is flashed, flash gapps and then twrp zip in TWRP, yeah you saw it right, flash twrp zip in TWRP. This way, twrp won't get replaced.
You can give directly flashing TWRP and flashing custom rom the way I told, Flashing Miui isn't important if your goal is to flash custom rom.
Hi!
I'm still on my way ro root my Samsung Tab SM-T725, after upgrading to Android 11. Before Android 9 was on the device, succesfully rooted via Magisk. Updating and keeping the root status didn't work properly, the flashing process in Odin failed. Therfefore I had to flash the latest stock recovery, successfully. So now I have Android 11 on my device but no root. The bootloader is open and USB debugging enabled.
I tried the method described here. But the flashing in Odin failed again. So now I try to follow the instructions on the Magisk website. If I get everything right a processed recovery.img has to be flashed via ADB/Fastboot. That's new to me and I have questions.
- Is fastboot and download/recovery mode the same? Booting to the recovery and following "reboot to bootloader" leads to the turquois "Downloading" window. The same occurs when prompting "ADB reboot fastboot" e. g. Again the mentioned Downloading window shows up, nothing (special) with fastboot. Is that correct?
- Will therefore all fastboot commands not work? And only ADB is possible on my tablet? Is that common for Samsung devices?
- Can the flashing of the patched recovery.img (for Magisk) be done with ADB as well? Instructions always mention fastboot.
- My device doesn't show up in ADB when being in recovery mode. In normal mode it is listed when entering "ADB devices". Trying again in recovery mode the list stays empty - and all other commands have no effect. Current Samsung and Google USB drivers are installed. How could that be solved? Without ADB (perhaps fastbood) running in download mode I shouldn't be able to flash (and root the device) as planned.
I hope I described everything properly. I'm not that Android expert - but successfully managed to root a couple of devices over the years.
Samsung devices dont know of Fastboot mode. But you can run them in either Recovery or Odin / Download mode or Normal mode.
Running Samsung devices in Download mode you can flash ROM or update system in the Android device. When the Samsung device has entered Download mode, the device will boot from external sources. You can also make the stock ROM replaced in Download mode.
ADB mode is the Normal mode.
In Recovery mode ADB - with some exceptions - isn't working
Because your device is a Samsung one the Google USB drivers are senseless. Remove them to avoid conflicts.
Thanks for the quick and helpful response!
That makes clear why the tablet didn't show up in ADB. And that all rooting efforts for Samsung devices via that way should be obsolete. Strange enough that Magisk doesn't mention this on their instruction site.
So I'll have to try on with flashing a patched AP via Odin - and hope for a solution for my fail-problem.