I'm trying to flash Magisk custom boot.img using fastboot but it will never detect the device, tried everything in the first page of Google with different searches, nothing works. Tried downloading Samsung developer drivers from here, tried this tool while in fastboot and then while the device is booted normally, tried this 15 second ADB installer tool to install Google adb and fastboot drivers, tried Kies, tried uninstalling all the relevant devices and using the Windows default ones, tried another laptop, another USB cable, another USB port, many videos and articles but still nothing. When I run fastboot devices, it doesn't show me anything, adb devices works just fine and shows the device when booted normally, of course I run fastboot devices when I'm in fastload but nothing shows up.
My device is SM-N910C treltexx EGY EXynos5433, tried all this mainly on Windows 11 but also tried with the Samsung developer drivers on a Windows 10 device.
I have WSA installed with hyper-V and Virtual Machine Platform installed on 11, could this be a problem? Also I noticed that when I run adb reboot fastboot, the device just restarts, the same when I choose Run fastboot in recovery mode, the only way for me to get to fastboot is pressing power +home +volume down. Also Odin recognizes the device in fastboot just fine.
So how to solve this? Or is there a method to flash Magisk's boot.img without fastboot? Or an alternative that does its job?
With further research I managed to do it with Odin. Took the patched file and renamed it to boot.img, used 7z to make a tar archive out of it. Loaded it in Odin as an AP and it worked! I have been using Magisk 24.3 all along because there is an issue with 25.0 that makes it stuck on the logo screen on rooted Galaxy Note 4 devices.
Still, is there a way to use fastboot on this device?
samsung galaxy note 4 (snapdragon and exynos) won't have fastboot mode, sorry.
Related
Hi,
I rooted my mojo and then i installed twrp, then i installed cyanogenmod 12 and i tryed to reboot but when i pressed reboot TWRP asked "Your device isnt rooted want to root? but i presed no accidentaly (one of the worst mistakes of my life) and it stucked on bootloop and i tryed to reboot it on recovery mode to fix it using fastboot but it stucks on rebooting... (on the screen of terminal on my laptop) and i waited for a long long time, but nothing happened.
Please help!
Did you use towelroot, or the USB-USB cable?
If towelroot, then you may not be able to recover the device without using a USB-USB cable. The fastboot prevents the MOJO from being bricked, because you can always re-flash it using the USB-USB method, even if the OS installed isn't working.
If you have a USB-USB cable, you need to use that to boot from TWRP again (or re-flash it to the fastboot if it won't work) and then re-wipe the MOJO and re-install CM12 + the Gapps, then re-boot the system as per the instructions. If you have any questions regarding clarification of the procedure, feel free to ask.
I used towelroot to root it and i tried fastboot to reboot it but on windows 10 don't detect it and on mac os X el capitan stucks on rebooting.....
The Windows driver should be in the same folder as fastboot. I was using Windows 7 and it didn't detect either, but the driver makes it detect correctly.
http://i.imgur.com/8O5FDgB.jpg
Windows 10 cant, but i will try with an windows 7 old (not so old) laptop
https://drive.google.com/file/d/0B3gWeKqMPK8HcjE2ZC1hOU0yUDA/view?usp=sharing
hi again, i tried with the windows 7 laptop but now fastboot dont detect it,i installed the drivers succesfully but fastboot dont detects it
https://drive.google.com/file/d/0B3gWeKqMPK8HajBUNlMyZEcxV1k/view?usp=sharing
SOLVED: the reason it didnt detected it its because on windows you needed to turn on testdriversigning and install the .inf file included on the MoDaCo mod zip on the windows.drivers and after that you needed to write "fastboot -i 0x0738 <command> , "0x0738" is the mojo´s usb vendor so it sended the commands directly to the mojo.
The problem was that the data and system partitions were corrupted so i reformated them with "fastboot -i 0x0738 erase system -w", the -w is for erase userdata. After that i booted the twrp recovery by "fastboot -i 0x738 boot <recovery.img path>" and from twrp i reinstalled android and it worked!
Hey gang - this has been a bigger challenge than on any of my other devices, it's weird.
I've DLed both the TAR and IMG versions of TWRP.
Reboot to recovery, try to flash the TAR with Odin... it thinks about it for about 90 seconds and then tell me "FAILED!" Meanwhile, on the Tab screen, the little progress bar starts... but then nothing happens after that.
So I figure I'll use ADB/Fastboot to flash the IMG. So. Booted into the OS, USB Debugging on... connected to my W10 box > Command Prompt, I type "ADB devices."
[Hex code for Tab] - unauthorized
I unplug / replug and get the popup "Authorize USB debugging?" on the Tab. [OK]
ADB devices gives me [hex] - device
Fastboot devices doesn't show anything.
OK. ADB reboot recovery
Now in recovery mode.
ADB devices... -> nothing
Fastboot devices... -> nothing
Why does it show up in teh OS but not in recovery? And why does ADB work but not Fastboot in the OS?
Maddening. Help?
Quick follow-up. Got it installed.
I tried a different computer, and downloaded Odin 3.12 to that vs. 3.10 on my main computer. Not sure which of these changes was responsible but I was able to flash TWRP without issue.
Device LG G6
Model : G600LR30c
I was thinking of installing a custom os which requires TWRP recovery installed in the device which recuires the device to be bootloader unlocked. But when I use the command "adb reboot bootloader" in minimal adb the device never goes to boot menu, instead it simply restarts and then if I put the command "fastboot oem device-id", it never shows the id and keeps showing "waiting for a device" instead. Please help me resolve this.
P.S: I also tried to access boot menu using key combo. but in vain
If you can put the phone in Fastboot mode during powerup or restart, it's a Windows issue if it don't work. Windows must recognize the device via PnP and install a different set of drivers each time the usb mode changes. If it don't work when the phone is already in Fastboot mode, try different drivers.
I once had two sets installed, that from the device manufacturer and that ripped from the Google SDK(on XDA). This way all usb modes worked, but Windows couldn't perform the Reboot Fastboot/Recovery commands fom ADB like is the case here and the Windows software had, suitable drivers installed, to be able to access the phone if it was already set to Fastboot/Download etc mode.
That was a TI OMAP based LG L9 under Win7. Starting with Windows 8.1, Fastboot was no longer working at all, you could only perform disaster recovery via D/L mode with a stock image and then root the thing with a one-click rooter to be able to install a recovery from Android etc etc, but that was due to the no longer supported TI SoC. But Qualcomm also tends to completely abandon older SoCs.
Hi Guys
So my current goal is to root my galaxy S10+ (SM-G975F) running exynos with android 11. I've seen many methods that are supposed to work for android 11, some more complicated than the others.
The method I chose to stick with, is to enter bootloader through adb using cmd on my computer and to flash twrp that way. (Bootloader is unlocked already)
After that I should be able to install magisk via twrp to complete the root access.
My inital thought was to flash twrp via odin, because odin did recognize my phone after entering bootloader. The problem was that after flashing twrp with odin and performing vol down + power then bixby + vol up + power which normally makes you enter twrp, I got stuck in a bootloop. After that I had to flash the stock ROM via Odin to "repair" my phone.
From what I've read this is due to the vbmeta protection mechanism, that you need to deactivate to avoid bootlooping.
So I heard that you can extract the boot.img file from the official firmware and edit the file with HxD Binary editor to replace a bitcode's value with a series of 0's. Unfortunately I couldn't find that specific code in boot.img.
So the remaining option was to manually flash vbmeta.img and to disable verity verification via cmd.
This is where the big problem lies, my PC does not recognize the device as soon as I enter Download mode. I tried every possible fix I could find online, they all revolve around installing certain drivers and applying them to the device in the device manager. Apparently the device needs to appear in the device manager under "other devices" with a yellow triangle then you can manually select a driver to install. Unfortunately as soon as I enter Download mode (Via cmd command or manually) my device totally disappears from the pc. Only Odin still recognises it somehow.
I installed official android device drivers, specific drivers for bootloader etc.
Every online guide about solving this problem needs you to locate the device and to apply certain drivers to it, but nothing appears for me.
I hope somebody can help me
Format data?
What your twrp version ? your twrp version must be version support 11.
You cant flash Magisk via TWRP. It doesn't work, Install the magisk App
Wrong place to ask this stuff
Hey guys, I know this isn't super active anymore, but I tried looking and tried posting elsewhere, and I can't find the answer I need. I'm sure it's something super simple I've overlooked.
I was gifted a 2015 Nvidia Shield TV Pro that was never used, so when I turn it on it gets stuck forever asking for my google login and won't proceed (like this thread here).
I can access the fastboot menu on the unit, and I've installed the PC drivers - BUT
When I open command and type "adb devices" it shows no devices connected.
I'm TOLD this is because I need to activate USB debugging on the unit, but how can I toggle on the USB debugging if I can't get past the google sign-in for a first-time set up?
Am I approaching this wrong?
PLEASE help!
Hello, I have exactly the same issue.
I would be really grateful if someone could help us.
i think you must set your SHIELD in FASTBOOT mode and after flash the stock firmware from https://developer.nvidia.com/gameworksdownload (you can't set FASTBOOT mode from ADB because of the wrong login)
to set fastboot mode look here : https://nvidia.custhelp.com/app/ans...invoke-the-android-fastboot-menu-on-shield-tv
Thanks conduisant! It helped.
I have spent some time to flash new recovery:
How far I was able to proceed:
I downloaded ADB Fastboot drivers
I downloaded recovery image (nv-recovery-image-shield-2017-atv-8.2.3)
I connected Nvidia Shield 2017 (model: P2897) with USB-A-to-USB-A cable to the PC
I was able to see "unknown device" so I installed ADB drivers (SHIELD_Family_WHQL_USB_driver_201801)
In device manager I can see my shield (as a Android Bootloader Interface)
I can access fastboot (pressing A+B on controller during turn on of shield)
I opened CMD and type "fastboot devices" - press enter - I can see my device is listed "03xxxxxxx fastboot"
I am able to execute "fastboot oem unlock", so bootloader is unlocked
I am able to write recovery image by using following commands written in instructions:
fastboot flash staging blob
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot flash vendor vendor.img
fastboot oem lock
fastboot reboot
(no errors, everything was "OKAY")
But after the device restart , I can post only until the nvidia logo and that is it. Unfortunately I do not even know which was the original (stock) version of system in nvidia shield pre-installed. I tried to flash several versions of recovery images, but nothing helped. I can still see only nvidia logo :-(
But what I noticed, my Fastboot looks pretty different. I do not see my bootloader version, also some options are missing (lock bootloader, unlock bootloader etc.)
I also tried another options - boot recovery kernel, safe mode, but only nvidia logo every time.What is strange, when I turn-on the device, the Fastboot is automatically booted (I do not even hold A+B to initiate fastboot) I need to select continue.
So now I am not even able to try login into the shield anymore. I guess I already bricked the device :-(
what you have done is pretty correct !
Shield seems to be hard bricked, you can also try to flash TWRP + lineage OS ROM only to see if the SHIELD still not boot...i've no other idea
Thank conduisant for your effort!
Unfortunately, I am not able to boot into the TWRP.
I tried to flash TWRP what I have found here on forum:
UNOFFICIAL-twrp-3.0.2-ALL-Shields-build2.zip
But no success.
I tried to also flash official TWRP:
twrp-3.2.3-0-foster.img
But also no success.
I do not know which offical recovery to flash before LineageOS ROM (or it does not matter?)
Unfortunately, for some reason my gamepad in Fastboot stopped working (gamepad is connectied via USB to the shield, closest to HDMI port)
It just rumble when Fastboot booted and blinks blue led. I tried to charge gamepad - or - another nvidia shield gamepad but it does not work.
Also USB keyboard does not work. Looks like the USB port does not work properly anymore, so I am not able to click "Continue" in fastboot anymore to post at least until nvidia logo.
Luckily, the bootloader is still unlocked, so I am able to flash anything but I have already lost my mind.
I need another coffee and one full-day of meditaion.
i've got 2017 SHIELD, and i've flashed this TWRP last days + this LINEAGE OS : and all working good
TWRP = https://eu.dl.twrp.me/foster/twrp-3.7.0_9-0-foster.img.html
LINEAGE OS = https://download.lineageos.org/foster
when USB debugging is ON, only one USB port is activate for USB devices (keyboard for example) : it's the port near HDMI, the other port (near fan grid) is for ADB connection for the PC