Related
I just did the S-OFF wire trick and have S-OFF, but now im stuck in the boot loader and if I reboot I just get the black Juopunut screen. Im guessing to get my phone working again I have to use CMD and do;
fastboot oem rebootRUU
fastboot flash zip jb_hboot.zip
fastboot reboot-bootloader
fastboot flash boot <boot image for your rom>
fastboot flash recovery <your recovery>
fastboot reboot
Im not familiar with using command prompts so once I open it I get; C:\Users\Ruki.
Now what command do I use to get to my phone and type in the needed commands?? I really need my phone back on and working
Do you use google talk? I can walk you thru
I have a recovery backup from the s off process but thats it. But idk how to flash it using command promt
ronnie498 said:
Have you flashed a recovery?
fastboot flash recovery ******.img
fastboot flash boot boot.img
Click to expand...
Click to collapse
ronnie498 said:
Do you use google talk? I can walk you thru
Click to expand...
Click to collapse
I do but no video atm. Ronnie0128 is my Google Talk name
Hello everyone, I have a favor to ask for.
I want o flash rogers rom on my PR Moto X but the crappy moto software can't recognize my phone.
I can't use rsd at all so I want to do it via fastboot.
Can you tell me how to do this with commands? Which parts do I need to flash?
like: fastboot flash system system.img and so on
But I need a full script of this, please help! Deadly need the update for the camera!
Thanks in advance!
chrisjenho said:
Hello everyone, I have a favor to ask for.
I want o flash rogers rom on my PR Moto X but the crappy moto software can't recognize my phone.
I can't use rsd at all so I want to do it via fastboot.
Can you tell me how to do this with commands? Which parts do I need to flash?
like: fastboot flash system system.img and so on
But I need a full script of this, please help! Deadly need the update for the camera!
Thanks in advance!
Click to expand...
Click to collapse
if your phone is not recognized for rsd purposes then you probably should be trying to flash anything through fastboot. Rsd uses fastboot to flash your system so if RSD is not recognizing the device then fastboot won't recognize the device either. If you don't have the most up to date drivers then you most likely will run into problems when trying to flash any images using fastboot.
Download moto device manager. plug the phone into the computer with the cable you got when buying the phone. Make sure it is on MTP (the mass media option). To do this after you plug the phone in you can pull down the notification bar and it will have what type of usb connection you are using right there. To change just click on it and select mtp. Nopen up moto device manager and it should download some stuff for your phone. Next time you plug your phone in you should see a webpage pop up and a little moto icon in the bottom right tool bar on your computer.
jayboyyyy said:
if your phone is not recognized for rsd purposes then you probably should be trying to flash anything through fastboot. Rsd uses fastboot to flash your system so if RSD is not recognizing the device then fastboot won't recognize the device either. If you don't have the most up to date drivers then you most likely will run into problems when trying to flash any images using fastboot.
Download moto device manager. plug the phone into the computer with the cable you got when buying the phone. Make sure it is on MTP (the mass media option). To do this after you plug the phone in you can pull down the notification bar and it will have what type of usb connection you are using right there. To change just click on it and select mtp. Nopen up moto device manager and it should download some stuff for your phone. Next time you plug your phone in you should see a webpage pop up and a little moto icon in the bottom right tool bar on your computer.
Click to expand...
Click to collapse
Thanks buddy. Actually fastboot works but RSD doesn't. I made it on fastboot.
For these guys have the same problem with me.
Script use in command,
fastboot flash partition gpt.bin
fastboot flash motoboot motoboot.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot erase customize
fastboot erase clogo
fastboot oem fb_mode_clear
chrisjenho said:
Thanks buddy. Actually fastboot works but RSD doesn't. I made it on fastboot.
For these guys have the same problem with me.
Script use in command,
fastboot flash partition gpt.bin
fastboot flash motoboot motoboot.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot erase customize
fastboot erase clogo
fastboot oem fb_mode_clear
Click to expand...
Click to collapse
I tried this on my VZW dev edition but it wouldn't let me flash system.img
alex94kumar said:
I tried this on my VZW dev edition but it wouldn't let me flash system.img
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2489249
everything was fine until I wanted to try the MIUI10 rom from 6x using the last guide on the forum (I'm not blaming anyone)... I was running the v9.6.12 with magisk installed and working fine, but I though I needed to uninstall magisk first so I tried to do it from the magisk manager and it always ended on the stock recovery image showing "no commands"(first mistake: I only needed to flash the original boot.img tho) so I went to fastboot and flashed the original boot.img and after that the phones was triying to boot but it never did it (I waited enough time looking the animation boot) so I though that my Rom was broken so I needed to install rom stock first. after searching on the forum I found this guide and I just tried it (I've done this before a lot of times on other devices):
(I ran first: fastboot flash unlock-critical or something like that, so I was able to flash all the .img files with no problems)
fastboot flash bluetooth_a C:\adb\images\bluetooth.img
fastboot flash bluetooth_b C:\adb\images\bluetooth.img
fastboot flash devcfg_a C:\adb\images\devcfg.img
fastboot flash devcfg_b C:\adb\images\devcfg.img
fastboot flash dsp_a C:\adb\images\dsp.img
fastboot flash dsp_b C:\adb\images\dsp.img
fastboot flash modem_a C:\adb\images\modem.img
fastboot flash modem_b C:\adb\images\modem.img
fastboot flash xbl_a C:\adb\images\xbl.img
fastboot flash xbl_b C:\adb\images\xbl.img
fastboot flash pmic_a C:\adb\images\pmic.img
fastboot flash pmic_b C:\adb\images\pmic.img
fastboot flash rpm_a C:\adb\images\rpm.img
fastboot flash rpm_b C:\adb\images\rpm.img
fastboot flash tz_a C:\adb\images\tz.img
fastboot flash tz_b C:\adb\images\tz.img
fastboot flash hyp_a C:\adb\images\hyp.img
fastboot flash hyp_b C:\adb\images\hyp.img
fastboot flash keymaster_a C:\adb\images\keymaster.img
fastboot flash keymaster_b C:\adb\images\keymaster.img
fastboot flash cmnlib64_a C:\adb\images\cmnlib64.img
fastboot flash cmnlib64_b C:\adb\images\cmnlib64.img
fastboot flash cmnlib_a C:\adb\images\cmnlib.img
fastboot flash cmnlib_b C:\adb\images\cmnlib.img
fastboot flash abl_a C:\adb\images\abl.elf
fastboot flash abl_b C:\adb\images\abl.elf
fastboot flash boot_a C:\adb\images\boot.img
fastboot flash boot_b C:\adb\images\boot.img
fastboot flash system_a C:\adb\images\system.img
fastboot flash system_b C:\adb\images\system.img
fastboot flash vendor_a C:\adb\images\vendor.img
fastboot flash vendor_b C:\adb\images\vendor.img
fastboot flash mdtp_a C:\adb\images\mdtp.img
fastboot flash mdtp_b C:\adb\images\mdtp.img
fastboot flash userdata C:\adb\images\userdata.img
fastboot flash splash C:\adb\images\splash.img
fastboot flash mdtpsecapp_a C:\adb\images\mdtpsecapp.img
fastboot flash mdtpsecapp_b C:\adb\images\mdtpsecapp.img
fastboot flash storsec C:\adb\images\storsec.mbn
fastboot erase ddr //I've never seen this command before
fastboot reboot
after flashing these files the phone is stucked in the "Android one" screen and it's not going further and its not showing any boot animation, is just static. I can enter to fastboot mode but the phone is never detected by my pc or my laptop, tried on windows and ubuntu:
$: sudo fastboot devices
$: (it shows nothing, is not being detected)
even windows doesnt make a sound when I connect my device while on fastboot (as it used to)
So I can't run any fastboot command and MiFlash is not working, I think this last one is because it needs to detect the phone on fastboot when you load a rom folder. I don't know what to do now (probably is the rollback protection getting me).
Is there any chance I can restore my phone without triying "test points" or something that deep/hard?...
Im thinking of sending my phone to warranty and hoping to get it working (at least when the phone tries to boot it doesn't show the "Unlocked" text or those security alerts). If someone knows anything about it or help me to find out what should I do, I'd love to try it. Thanks in advance.
sorry for my english, is not that good
MI a2 global version 4/64
bought it on mercadolibre.com.mx (probablemente estoy jodido :'v)
Edit: I opened My device, used the test points to enter edl mode and flashed 9.6.10 stock with MiFlash
If you can still boot in fastboot, type "fastboot oem edl" and see if the device enters EDL mode then try to flash the stock ROM. My phone sometimes doesn't connect to PC through fastboot as well and if I competely turn it off by force (Vol down and Power) and turn it back on after a while, the connection works again.
Not sure if the warranty will be possible
cyrillem28410 said:
Not sure if the warranty will be possible
Click to expand...
Click to collapse
yeah I agree, if they solve the problem the bootloader probably it's gonna be still unlocked and I'm just gonna waste time and money, I don't know how Xioami handles the bootloader-unlocked stuff, thanks
djmitza222 said:
If you can still boot in fastboot, type "fastboot oem edl" and see if the device enters EDL mode then try to flash the stock ROM. My phone sometimes doesn't connect to PC through fastboot as well and if I competely turn it off by force (Vol down and Power) and turn it back on after a while, the connection works again.
Click to expand...
Click to collapse
I can still boot on fastboot but it seems like is not working, I can't run any fastboot command, I gave it a try after 1 hour and I have the same problem, a zombie fastboot, thanks
[email protected]:~$ fastboot devices
[email protected]:~$ sudo fastboot devices
[sudo] contraseña para adairo:
[email protected]:~$ fastboot oem edl
< waiting for any device >
^C
[email protected]:~$ fastboot continue
< waiting for any device >
^X^C
[email protected]:~$
You are jodido
Thanks Sir :{v
Oleyiyo said:
You are jodido
Click to expand...
Click to collapse
Thanks Sir :{v
Adairo said:
Thanks Sir :{v
Click to expand...
Click to collapse
Try disconnecting and rebooting to fastboot and only then connect with the laptop or PC which is waiting for a device. Worked for me from time to time.
Benjamin_L said:
Try disconnecting and rebooting to fastboot and only then connect with the laptop or PC which is waiting for a device. Worked for me from time to time.
Click to expand...
Click to collapse
I tried what you said but the problem is still the same, I've tried a lot of combinations of buttons and orders to connect to pc with fastboot and they are not working for me. I think I'm gonna try to flash rom through test points or something like that, thanks!
Adairo said:
I tried what you said but the problem is still the same, I've tried a lot of combinations of buttons and orders to connect to pc with fastboot and they are not working for me. I think I'm gonna try to flash rom through test points or something like that, thanks!
Click to expand...
Click to collapse
Did you fix it?
My phone is not rebooting as stuck over android one logo only & OEM unlock & USB debugging are also NOT unlocked/enabled. Couldn't flash the ROM via mi flash tool even device is being identified correctly. An error is being encouneterd while aforesaid flashing is :Flash blutooth_a error"
Unable to unlock via fastboot using ADB tool as well as mi flash unlock tool.
Please guide...
sarrck said:
My phone is not rebooting as stuck over android one logo only & OEM unlock & USB debugging are also NOT unlocked/enabled. Couldn't flash the ROM via mi flash tool even device is being identified correctly. An error is being encouneterd while aforesaid flashing is :Flash blutooth_a error"
Unable to unlock via fastboot using ADB tool as well as mi flash unlock tool.
Please guide...
Click to expand...
Click to collapse
I'd like to ask. When you used the fastboot commands. Did you by any chance include sudo before executing the commands. Fastboot usually displays "waiting for any device" when you don't have sudo privileges and/or doesn't find your device?
Edit: Just saw you're on Windows. You could try going in fastboot from Linux since Linux recognizes Android devices easier but if OEM unlock wasn't enabled then all of this is for nothing.
Hello, I tried to install a rom on my moto z3 play and now it does not start. With "blankflash" I managed to make it turn on in mode fastboot but i try to install the original rom but it says "Oem_locked". Then install the moto smart asistant tool but it didn't work either, inside "moto asistant" I get "Error combining the connected device, please connect it and try again", when I connect it, an unsupported device appears. It is rare because the previous times I use the program, I download the official rom of the device and install it, but now it does not work. In "connected devices" it does not appear as "Qualcomm_Qdloader 9008" but appears as "Fastboot beckham S".
I'm really desperate I don't know what to do. If anyone knows how I can fix it please I need your help.
Is there a way to enable usb debugging from the "fastboot"?
Mica_Diazz531 said:
Hello, I tried to install a rom on my moto z3 play and now it does not start. With "blankflash" I managed to make it turn on in mode fastboot but i try to install the original rom but it says "Oem_locked". Then install the moto smart asistant tool but it didn't work either, inside "moto asistant" I get "Error combining the connected device, please connect it and try again", when I connect it, an unsupported device appears. It is rare because the previous times I use the program, I download the official rom of the device and install it, but now it does not work. In "connected devices" it does not appear as "Qualcomm_Qdloader 9008" but appears as "Fastboot beckham S".
I'm really desperate I don't know what to do. If anyone knows how I can fix it please I need your help.
Is there a way to enable usb debugging from the "fastboot"?
Click to expand...
Click to collapse
I believe your only option is RSD Lite if you have a windows 7 pc
https://forum.xda-developers.com/general/rooting-roms/guide-flashing-motorola-firmware-t4042039
sd_shadow said:
I believe your only option is RSD Lite if you have a windows 7 pc
https://forum.xda-developers.com/general/rooting-roms/guide-flashing-motorola-firmware-t4042039
Click to expand...
Click to collapse
Thank you !! I will try to do that, first I will see if I can get a pc with windows 7. that would be the only solution?
Mica_Diazz531 said:
Hello, I tried to install a rom on my moto z3 play and now it does not start. With "blankflash" I managed to make it turn on in mode fastboot but i try to install the original rom but it says "Oem_locked". Then install the moto smart asistant tool but it didn't work either, inside "moto asistant" I get "Error combining the connected device, please connect it and try again", when I connect it, an unsupported device appears. It is rare because the previous times I use the program, I download the official rom of the device and install it, but now it does not work. In "connected devices" it does not appear as "Qualcomm_Qdloader 9008" but appears as "Fastboot beckham S".
I'm really desperate I don't know what to do. If anyone knows how I can fix it please I need your help.
Is there a way to enable usb debugging from the "fastboot"?
Click to expand...
Click to collapse
Try this:
Connect your device to the PC in Fastboot mode and in the command prompt type:
Code:
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
Restart the device in Fastboot mode and follow the procedure for flashing the rom normally.
Code:
fastboot getvar max-sparse-size
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
fastboot bluetooth flash BTFM.bin
fastboot flash dsp dspso.bin
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system_b system_other.img
fastboot flash vendor vendor.img_sparsechunk.0
fastboot flash vendor vendor.img_sparsechunk.1
fastboot flash oem oem.img
fastboot flash oem_b oem_other.img
fastboot erase cache
fastboot erase carrier
fastboot erase userdata
fastboot erase DDR
fastboot oem fb_mode_clear
fastboot reboot
If you have problems with carrier signal and / or wifi, see this link: https://forum.xda-developers.com/showpost.php?p=83152527&postcount=4
fastbook flash instructions
Loko_vr said:
Restart the device in Fastboot mode and follow the procedure for flashing the rom normally.
Code:
fastboot getvar max-sparse-size
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
fastboot bluetooth flash BTFM.bin
fastboot flash dsp dspso.bin
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system_b system_other.img
fastboot flash vendor vendor.img_sparsechunk.0
fastboot flash vendor vendor.img_sparsechunk.1
fastboot flash oem oem.img
fastboot flash oem_b oem_other.img
fastboot erase cache
fastboot erase carrier
fastboot erase userdata
fastboot erase DDR
fastboot oem fb_mode_clear
fastboot reboot
Click to expand...
Click to collapse
Hi. I want to flash a rom using fastboot into my mz3 Play. I can't find a tutorial on it. After I download the ROM:
1. I unzip it to the desktop?
2. connect the phone to usb in fastboot mode?
3. Run the commands in fastboot?
or do I have to unzip the ROM into the ADB / fastboot folder?
kc12 said:
Restart the device in Fastboot mode and follow the procedure for flashing the rom normally.
Hi. I want to flash a rom using fastboot into my mz3 Play. I can't find a tutorial on it. After I download the ROM:
1. I unzip it to the desktop?
2. connect the phone to usb in fastboot mode?
3. Run the commands in fastboot?
or do I have to unzip the ROM into the ADB / fastboot folder?
Click to expand...
Click to collapse
https://forum.xda-developers.com/general/rooting-roms/guide-flashing-motorola-firmware-t4042039
Sent from my perry_f using XDA Labs
kc12 said:
Hi. I want to flash a rom using fastboot into my mz3 Play. I can't find a tutorial on it. After I download the ROM:
1. I unzip it to the desktop?
2. connect the phone to usb in fastboot mode?
3. Run the commands in fastboot?
or do I have to unzip the ROM into the ADB / fastboot folder?
Click to expand...
Click to collapse
Using fastboot, unzip the firmware files in the same folder as adb / fastboot and then follow the commands listed above.
Note:
The bootloader must be unlocked.
The adb drivers must be installed.
The device must be started in fastboot mode.
Loko_vr said:
Using fastboot, unzip the firmware files in the same folder as adb / fastboot and then follow the commands listed above.
Note:
The bootloader must be unlocked.
The adb drivers must be installed.
The device must be started in fastboot mode.
Click to expand...
Click to collapse
Thank you for responding! Presently my bootloader is unlockable. I have already done as you described and the rom flashed without issues. Thanks again.
---------- Post added at 11:07 PM ---------- Previous post was at 10:56 PM ----------
sd_shadow said:
https://forum.xda-developers.com/general/rooting-roms/guide-flashing-motorola-firmware-t4042039
Sent from my perry_f using XDA Labs
Click to expand...
Click to collapse
Thank you for the link. The tutorial is great for someone who is knowledgeable in fastboot. But my experience with fastboot is limited with booting and flashing twrp. And maybe a few simple other commands. The tutorial didn't have any information regarding what I was supposed to do with the ROM zip after I downloaded it. However, your tutorial had several links and following one link to another and to another.. ... I was able to determine that what you do with the zip file kind of depends on how you have set up your adb/ fastboot. And because of another article you wrote I was able to determine unzipping the rom in my abd/fastboot folder was what I needed to do. So, thank you for your knowledge, which is light years ahead of mine.
---------- Post added at 11:09 PM ---------- Previous post was at 11:07 PM ----------
sd_shadow said:
https://forum.xda-developers.com/general/rooting-roms/guide-flashing-motorola-firmware-t4042039
Sent from my perry_f using XDA Labs
Click to expand...
Click to collapse
Thank you for the link. The tutorial is great for someone who is knowledgeable in fastboot. But my experience with fastboot is limited with booting and flashing twrp. And maybe a few simple other commands. The tutorial didn't have any information regarding what I was supposed to do with the ROM zip after I downloaded it. However, your tutorial had several links and following one link to another and to another.. ... I was able to determine that what you do with the zip file kind of depends on how you have set up your adb/ fastboot. And because of another article you wrote I was able to determine unzipping the rom in my abd/fastboot folder was what I needed to do. So, thank you for your knowledge, which is light years ahead of mine.
kc12 said:
Thank you for responding! Presently my bootloader is unlockable. I have already done as you described and the rom flashed without issues. Thanks again.
---------- Post added at 11:07 PM ---------- Previous post was at 10:56 PM ----------
Thank you for the link. The tutorial is great for someone who is knowledgeable in fastboot. But my experience with fastboot is limited with booting and flashing twrp. And maybe a few simple other commands. The tutorial didn't have any information regarding what I was supposed to do with the ROM zip after I downloaded it. However, your tutorial had several links and following one link to another and to another.. ... I was able to determine that what you do with the zip file kind of depends on how you have set up your adb/ fastboot. And because of another article you wrote I was able to determine unzipping the rom in my abd/fastboot folder was what I needed to do. So, thank you for your knowledge, which is light years ahead of mine.
---------- Post added at 11:09 PM ---------- Previous post was at 11:07 PM ----------
Thank you for the link. The tutorial is great for someone who is knowledgeable in fastboot. But my experience with fastboot is limited with booting and flashing twrp. And maybe a few simple other commands. The tutorial didn't have any information regarding what I was supposed to do with the ROM zip after I downloaded it. However, your tutorial had several links and following one link to another and to another.. ... I was able to determine that what you do with the zip file kind of depends on how you have set up your adb/ fastboot. And because of another article you wrote I was able to determine unzipping the rom in my abd/fastboot folder was what I needed to do. So, thank you for your knowledge, which is light years ahead of mine.
Click to expand...
Click to collapse
I recommend LMSA's Flash Rescue it's easier
https://forum.xda-developers.com/general/general/update-moto-lenovo-moto-smart-assistant-t3951714
sd_shadow said:
I recommend LMSA's Flash Rescue it's easier
https://forum.xda-developers.com/general/general/update-moto-lenovo-moto-smart-assistant-t3951714
Click to expand...
Click to collapse
My phone is a sprint variant. I wanted to flash the brazil variant and the US canada variant, in hopes of one would solve my issue and I could get my bootloader unlocked. I couldn't get them to flash with the rescue tool. I followed someone's instructions where they were able to trick the tool by replacing the files in the lmsa's rom folder. Unfortunately I couldn't get either one to flash in the lmsa tool past 64%. They fail. So I had to fastboot them. Unfortunately I still can't get fastboot to retrieve my unlock data.
Hi all,
I know this is an older phone but I received it used and I tried to place Lineage OS 17 from this forum on it as I did with two others and it did not work.
I have tried multiple ROMs from this forum but I always end up at the fastboot menu. I have tried fastboot oem fb_mode_clear and that doesn't work.
The bootloader logs state:
AP Fastboot Flash Mode (Secure)
Fastboot Readon: Reboot mode set to fastboot
I would be happy if I can get ANY de-googled AOSP ROM working on this phone.
Can anyone lend a hand?
I have used the LineageOS19 image from the forum and it includes a recovery image that I can flash and successfully access.
I have a twrp image that I can flash into recovery and also access, but it demands a password to decrypt the user data.
I have noticed that when commanding fastboot -w, the device reports that raw is not a supported format.
Anything else that I can give you to help?
Thanks!
"fastboot -w" doesn't work properly on mine either from what I remember. "fastboot erase <partition>" does.
Make sure you're not in fastbootd first: fastboot reboot bootloader
Then:
fastboot erase carrier
fastboot erase userdata
fastboot erase metadata
fastboot erase ddr
(Adapted from flashfile.xml in the stock firmware file XT2041-4_SOFIA_RETUS_11_RPMS31.Q1-54-13-7_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip)