Have decided to root my phone with Adb and fastboot devices in Windows 10 and also installed drivers sucessfully and i can se my phone in cmd when i type fastboot devices.
Have unlock the bootloader in the phone and Enabled USB failure search in Advanced settings in developers mode.
When i loaded the Twrp file in cmd with adb i could copy and write the file to my fastboot device but when i reboot the phone into bootloader i se that download mode are disabled.
How can you unlock download mode ?
When i try to reboot into recovery mode i get the Android bot with a red triangle into it.
Im guessing that happens for i dont have download mode enabled and im wounder is the Twrp file on my phone or have that setting stopped this process?
Related
Hello,
Recently I flashed a CWM file on my android 'Lava Iris X1 Grand'. Now my phone is stuck in a bootloop. For some reason i cant enter recovery mode even before my phone was stuck in a bootloop. I am not sure whether my phone has USB debugging enabled or not. I have even rooted my android with KingRoot. I have downloaded your Minimal Adb and Fastboot but it cant find my device.
Overall problem:
1) Phone Stuck in Bootloop
2)USB debugging enabled ? Not sure
3) Can't enter recovery mode
4) ADB wont find my device
Note : When I used Minimal Adb and Fastboot, when i type Fastboot devices some numbers appear but when I used the command 'adb devices' my device is not shown. I have a backup at my phone through the Flashify app but since recovery mode cant show I cant recover it.
Please help me out here. I don't know what else to do.
Thank You in advance
Fixed
Sorry posted in wrong section
My phone is fixed now using SP Flash Tool
Used ADB to unlock bootloader but now ADB can't "see" the phone in download mode
I have a Windows 7 PC and I used that with Android SDK to unlock the bootloader and that worked. Now (trying to install recovery) I can put the phone (5.1.1) in download mode and the PC registers the phone in Device Manager but ADB doesn't see it. I've changed nothing with the PC since unlocking the bootloader and I've confirmed USB debugging is enabled on the phone but the command 'adb devices' lists nothing below 'List of Devices Attached'. Has anyone heard of this? Any troubleshooting suggestions?
Try go to device manage and look for a device with a strange name using the Android ADB device driver, choose update and look for a driver for LGE ADB device instead.
I did t think think adb works in download mode, and it sure won't work in bootloader
If you are on lollipop then use fastboot to flash TWRP
fastboot flash recovery nameofrecovery.img
Sent from my LG-H901 using XDA-Developers mobile app
Hey friends i was able to unlock bootloader of my REDMI NOTE 3 OFFICIALLY.
I wan to root the device and install TWRP but for tat i have to connect my phone in fastboot mode.
The thing is phone is recognised as an adb device when it is on but after putting the phone in fastboot mode my laptop is not showing in cmd after " fastboot devices" command
plz help if anyne know how to fix this.
How are you putting it in fastboot mode?
did you already install correct driver in your pc?
you can try to instal latest mi pc suite which will help you to instal correct driver for your phone.
If you're already success unlocking with official way..then it's mean your fastboot driver already correct (if you're using the same computer when you're unlocking before)
Maybe i think you're missed something to put your phone into fastboot mode..
First way you can go into fastboot mode with ADB command while your phone already ON, just typing command "adb reboot bootloader" then enter..your phone will reboot into fastboot mode
Second way to go into fastboot mode firstly you must turn off your phone..just wait until that phone is truely OFF..
then press and hold volume down button..then followed with pressing and hold power button..your phone will booting into fastboot mode.
Is it possible to install twrp recovery and root using magisk in this phone or not possible because of mediatek processor?
Bhai have patience , this is Mediatek we all know but another thing to notice is This is MT- g95 SoC ?
Orange state in realme 7 when bootloader unlocked but unable to use fastboot.
I have unlocked my realme 7 bootloader with in-depth test built for realme 6 pro. It is working. But now after unlocking the phone factory resets itself and when trying to go into fastboot mode with ADB command ADB reboot bootloader the fastboot verify check fails all the time. So how to go into fastboot mode after bootloader unlock. This issue never happened when I start in-depth test after permissions. It's very strange that even after unlocking the phone is not booting into fastboot mode while giving error in verification. Guys can anyone knows how to solve this. Please reply asap.
Realme 7 After unlocking the bootloader is not going into fastboot mode again.
Can anyone tell when twrp for realme 7 wipp be available
I think i made a mistake by choosing mtk soc because it's hard chance to get twrp for mtk soc
Simple solution realme 7
Senxco said:
I have unlocked my realme 7 bootloader with in-depth test built for realme 6 pro. It is working. But now after unlocking the phone factory resets itself and when trying to go into fastboot mode with ADB command ADB reboot bootloader the fastboot verify check fails all the time. So how to go into fastboot mode after bootloader unlock. This issue never happened when I start in-depth test after permissions. It's very strange that even after unlocking the phone is not booting into fastboot mode while giving error in verification. Guys can anyone knows how to solve this. Please reply asap.
Click to expand...
Click to collapse
I think your adb driver not working please install adb driver reinstall and verfiy fails problem solve, thanks
No no adb driver is working and tested on other devices. I think the problem is with smartphone serial key ( It shows serial key mismatch and therefore fastboot unlock verify fail in fastboot mode).
To Root you phone:-
Download your device boot image > download magisk manager > patch your device boot image > go to fastboot mode > type in command >fastboot --disable-verity--disable-verification > flash vbmeta (fastboot flash vbmeta (put your vbmeta path here) > flash magisk patched image (fastboot flash boot (put your patched file path here) now reboot your phone it will be rooted if on First boot it didn't then reboot your device
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.