I wonder if we can use another rooted phone instead of PC to fastboot flash Moto Z2 Force?
http://www.droidviews.com/use-your-android-device-as-pc-for-fastboot-and-adb/
There is a link at the above URL's page for the same file that I've re-attached to this post. I will test it now, but I've already installed it to my other phone, which is a rooted US Snapdragon S8+. Both ADB and FASTBOOT execute in root Android terminal; I just have to test via USB-OTG now. Good luck!
FYI, if I had to guess, since the binaries are older, you may want to append partition slots to the partition specified. For example:
fastboot flash boot_a yourfilehere.img
fastboot flash boot_b yourfilehere.img
UPDATE 1: both ADB and Fastboot recognize the device. Fastboot starts to flash but never finishes. ADB recognizes the device but won't auto-connect on default port. I am using adb and fastboot on S8+ connected to Moto Z2 Force. I will also try adb in TWRP recovery. It is possibly an S8+ issue, so please let me know if it works on your rooted phone. In all likelihood, it may partly be due to the binaries being too old relative to the Android version of phones involved (i.e., API 24 for S8+ and API 25 for Moto Z2 Force).
UPDATE 2: TWRP on Moto Z2 Force in sideload mode is recognized as sideload by ADB on S8+. However, even though it detects sideload and device number of Moto Z2 Force, it won't flash sideload; the error says * cannot read 'sideload' *. Again, maybe ADB and Fastboot will flash, etc., with some other rooted Android phone besides S8+, but I think it may well be the outdatedness of the binaries from the above URL.
UPDATE 3: SUCCESS!!!! My old rooted Note 5 (running Nougat 7.0) fastboot flashed the Moto Z2 Force's boot_a partition!!!! Yay!!!
Nice!
Related
fastbootd flashing of LOS is not working for me. NOTE: *"fastbootd"* process not fastboot. I'm trying an unofficial LOS on an Android10 device (Moto G8 Power) that evidently requires fastbootd. An informed XDA member kindly linked to the official doc on this new stuff ... but I'm too n00b to post Google's doc here.
I _can_ actually boot the phone into fastbootd -- using a command below -- and the splash screen says in BIG red letters "fastbootd", but right after the reboot, my USB connection is lost, and the rest of the fastboot commands return "< waiting for any device>"
This command reboots and displays "fastbootd":
Code:
$ sudo adb reboot fastboot
Everyone suggests downloading latest ADB & flashboot binaries ... OK, I'll bite: what version are you running that works? Below is my version and it is newer that what others have downloaded (I saw v29.x being suggested on XDA).
Code:
$ fastboot --version
fastboot version 30.0.4
Installed as /usr/bin/fastboot
$ adb --version
Android Debug Bridge version 1.0.41
Version 30.0.4
Installed as /usr/bin/adb
What is the sequence folks use for devices needing this new fastbootd process? Perhaps the dev for this unofficial LOS overlooked doc'ing a step that isn't obvious to me.
BTW: if I reboot into the regular bootloader, my adb stays connected to the phone. I learned this hard way while trying to troubleshoot ... while in the regular bootloader, I accidentally started a $ fastboot flash boot boot.img, and it started flashing! Luckily the phone immediately rejected it, rebooted into system recovery, and I got back into Android10.
vap0rtranz said:
fastbootd flashing of LOS is not working for me. NOTE: *"fastbootd"* process not fastboot. I'm trying an unofficial LOS on an Android10 device (Moto G8 Power) that evidently requires fastbootd. An informed XDA member kindly linked to the official doc on this new stuff ... but I'm too n00b to post Google's doc here.
I _can_ actually boot the phone into fastbootd -- using a command below -- and the splash screen says in BIG red letters "fastbootd", but right after the reboot, my USB connection is lost, and the rest of the fastboot commands return "< waiting for any device>"
This command reboots and displays "fastbootd":
Everyone suggests downloading latest ADB & flashboot binaries ... OK, I'll bite: what version are you running that works? Below is my version and it is newer that what others have downloaded (I saw v29.x being suggested on XDA).
What is the sequence folks use for devices needing this new fastbootd process? Perhaps the dev for this unofficial LOS overlooked doc'ing a step that isn't obvious to me.
BTW: if I reboot into the regular bootloader, my adb stays connected to the phone. I learned this hard way while trying to troubleshoot ... while in the regular bootloader, I accidentally started a $ fastboot flash boot boot.img, and it started flashing! Luckily the phone immediately rejected it, rebooted into system recovery, and I got back into Android10.
Click to expand...
Click to collapse
Make sure, this is really your device
https://forum.xda-developers.com/moto-g8/development/rom-lineageos-17-1-t4163021
kurtn said:
Make sure, this is really your device
https://forum.xda-developers.com/moto-g8/development/rom-lineageos-17-1-t4163021
Click to expand...
Click to collapse
No, I'm using the doc that is for the Moto G8 Power (the URL ends with 4163275 not 4163021). I could see how this could be easily confused b/c of Moto's branding and both are from the same Dev.
Both require fastbootd so at this point it should not matter until I get to the actual .img's.
Jp
So I've decided to root and customize my Z2 Force and want to unlock the bootloader to get TWRP installed. All device side settings are correct (USB Debug, OEM unlock etc.) in developer mode. ADB commands are working fine as I can see my SN when using ADB Devices command. I then reboot to the bootloader through ADB (adb reboot bootloader) and it works fine and my Z2 boots into the bootloader. Then I try to get the unlock code (fastboot oem unlock) and I get a message after trying to run the command: access denied. I started my CMD window using run as admin - no help. Installed ADB all over again with new generic drivers and moto drivers - no help.
I don't understand why I'm getting this message. I've unlocked and rooted all my phones over the years but they've all been HTC. Never messed with a moto phone like this before. I bought this phone directly through moto and it's suppose to be a carrier unlocked version. Anyone think this is a permalocked bootloader version - MODEL:XT1789-04 TYPE:M29E2
Any help is appreciated.
Hi dear community,
I have a new Moto G30 which is now does not boot and keeps getting stuck at bootscreen where the logo is, even after trying to boot for hours. This happened after a reboot where nothing special happened before. I have not installed any custom ROM, and have no idea why this is happening. There is no SD card in it, battery can not be taken out. I tried booting from stock recovery in all possible ways, nothing worked. Tried leaving it shut off for half a day.
Support say the only option is factory reset. However I need to get the data to my laptop before resetting. Is there a way to use Rescue and Smart Assistant for this? I can not boot the phone and can only boot in recovery. Or could I install TWRP or something via ADB sideload would allow me to then use ADB pull or something to get the photos, but TWRP is not yet available for G30?
Thank you!
cricket62 said:
Hi dear community,
I have a new Moto G30 which is now does not boot and keeps getting stuck at bootscreen where the logo is, even after trying to boot for hours. This happened after a reboot where nothing special happened before. I have not installed any custom ROM, and have no idea why this is happening. There is no SD card in it, battery can not be taken out. I tried booting from stock recovery in all possible ways, nothing worked. Tried leaving it shut off for half a day.
Support say the only option is factory reset. However I need to get the data to my laptop before resetting. Is there a way to use Rescue and Smart Assistant for this? I can not boot the phone and can only boot in recovery. Or could I install TWRP or something via ADB sideload would allow me to then use ADB pull or something to get the photos, but TWRP is not yet available for G30?
Thank you!
Click to expand...
Click to collapse
Did you enable adb debugging, in dev options before bootloop?
Did you enable adb debugging, in dev options before bootloop?
Click to expand...
Click to collapse
Hi unfortunately not, I only enabled "developer mode" but didnt think to enable ADB debugging as I was just getting to know the new phone and stock Android 11.
cricket62 said:
Hi unfortunately not, I only enabled developer mode but didnt think to enable ADB debugging as I was just getting to know the new phone and stock Android 11.
Click to expand...
Click to collapse
Is the Bootloader unlocked?
Use LMSA Rescue to download firmware.
You will see a screen that has the device's current firmware, and the firmware LMSA will download.
Make sure they are the same, you can post a screenshot of that if you are not sure.
Then use fastboot.exe to flash this
Code:
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot oem fb_mode_clear
then reboot the device.
[Guide] Using Fastboot.exe with Motorola devices
Guide: Using Fastboot.exe with Motorola Devices If your device has its own section please post in that section. You can ping me with @sd_shadow MediaTek or Qualcomm Chip? Do I have a MediaTek Device? see post #26 Info: If you have a MediaTek...
forum.xda-developers.com
sd_shadow said:
Is the Bootloader unlocked?
Click to expand...
Click to collapse
No, reason is since Lineage OS or TWRP are not yet build for G30 I wanted to keep the fully functional stock.
sd_shadow said:
Use LMSA Rescue to download firmware.
You will see a screen that has the device's current firmware, and the firmware LMSA will download.
Make sure they are the same, you can post a screenshot of that if you are not sure.
Then use fastboot.exe to flash this
Code:
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot oem fb_mode_clear
then reboot the device.
[Guide] Using Fastboot.exe with Motorola devices
Guide: Using Fastboot.exe with Motorola Devices If your device has its own section please post in that section. You can ping me with @sd_shadow MediaTek or Qualcomm Chip? Do I have a MediaTek Device? see post #26 Info: If you have a MediaTek...
forum.xda-developers.com
Click to expand...
Click to collapse
Thanks so much!! I will try that and write results when I get to it! Have a good healthy day!
Hi Just wanted to update: I still need to set up the USB redirect of the fastboot device to the Windows virtual machine. So may take a bit longer for me to get to it.
I am trying to flash the LineageOS on my Redmi Note 5 Pro (whyred). Initially, I used Windows 10 for the Xiaomi Unlock Tool. However, the Xiaomi Unlock Tool did not detect my device. So, I used this tool https://www.xiaomitool.com/V2/ to unlock my bootloader and it unlocked instantly. Now, I am using Ubuntu 21.04 (I am more comfortable using the command line here) (with android-tools-adb and android-tools-fastboot packages installed) to try to flash TWRP first.
When I connect my device, adb devices can recognise it. Then I use adb reboot bootloader to enter into fastboot. Now, fastboot devices can recognise it too. The screen of the phone shows the fastboot icon.
But, the problem comes here. I use fastboot flash recovery twrp.img and I get this error
FAILED (Write to device failed (No such device))
Click to expand...
Click to collapse
Now, when I use fastboot devices again. I don't see my device. Another change I see is press any key to shutdown written on the top left corner of the screen of my phone.
USB debugging, USB debugging security, OEM debugging are all enabled. Bootloader is unlocked (as I see in the settings). The phone is updated to latest MIUI version supported officially. And I used the same laptop and method to flash TWRP in a Redmi 3S (land) some time back.
(Posted the same question on android.stackexchange.com also) (https://android.stackexchange.com/questions/238996/redmi-note-5-pro-unable-to-flash-twrp)
Something else I experienced is that after randomly trying to get this right again and again, the command fastboot flash recovery twrp.img did not terminate or fail and got stuck.
So, this was a duplicate. I used the 5th method here and it worked for me. https://forum.xda-developers.com/t/everything-about-anti-roll-back-whyred.3816219/
Hey guys,
I have Lineage OS installed on my Poco F3. I have (at least not really) never experienced any issues with Lineage so far. Everything has worked really smoothly up until I updated the latest version of Lineage OS. The update took ages for some reason and now my Lineage is incredibly unstable.
It doesn't show any of my contacts anymore, play services and the app store crash all the time, giving me notifications non stop.
I tried manually updating the firmware as I figured something went wrong (obviously) but my device does not talk to my computer over a usb. I went to the settings and those showed me that the file transfer option is unclicked, I can't seem to change it either.. Really annoying.
Does anyone know what to do? I don't want to factory reset because of my authenticator. Shall I just wait for the next update and hope it's fixed?
Kind regards, pls halp!!
You could try going into Fastboot mode (https://www.hardreset.info/devices/xiaomi/xiaomi-poco-f3/fastboot-mode/), boot TWRP (fastboot boot TWRP.img) and then change boot partition (e.g. from a to b).
You get the twrp image here:
Xiaomi Poco F3
Disclaimer:Team Win strives to provide a quality product. However, it is your decision to install our software on your device. Team Win takes no ...
twrp.me
I recommend using minimal ADB and Fastboot if you're using windows:
[TOOL]Minimal ADB and Fastboot [2-9-18]
Introduction ADB and Fastboot are arguably two of the most indispensable tools used when working with Android devices. If you really want to modify, debug, and tweak along with their countless uses in rooting, and other procedures ADB and...
forum.xda-developers.com
Make sure you don't accidentally flash the twrp.img but use the "fastboot boot twrp.img" command!
Edit: just realized you can change active boot slot with just fastboot, i.e. no need to flash twrp):
Just boot into Fastboot, find out active boot partition:
fastboot getvar current-slot
And then change accordingly, i.e. if above command returns "a" choose "b" and vice versa wit this command: fastboot set_active b