I have a Moto Z4 XT1980-3 (Unlocked retail version with RETUS channel) with bootloader locked - no modifications from official state so far. When I got the December 2019 security patch upgrade, something network-related got corrupted - I have not been able to connect to any WiFi at all! This was the origin of all the desaster.
I read through the internet and found the information that it could happen that an OTA upgrade may not have been got on the device properly and if there are any hassles afterwards, it is required to do a full flash of the recent firmware. Okay, no problem, I thought. I am really familiar with ADB, fastboot and so on, and so I did. Took the recent firmware from here: https://mirrors.lolinet.com/firmware/moto/foles/official/RETUS/ (the one uploaded on 6th of December 2019).
The result was that I could flash all parts of the firmware, except of boot, vbmeta and dspso - for these parts I got a "(bootloader) Preflash validation failed" error. So now I am with an inconsistent firmware state and can only access fastboot mode (not even recovery). Plus sometimes when booting it, I get errors of unbootable A/B slots in the bootloader log. After having flashed gpt again, these errors disappear and I simply get the message that my device won't boot because of an invalid operating system.
What I have already tried to do:
- flash a full factory image (see above)
- use RSD lite (this tool detects my device as connected, but with no device information at all (only "?") and says it can not be switched to fastboot mode - but I am in fastboot mode already ???)
- use LSMA Smart Repair Assistant (this tool says my device is not compatible)
- Blankflash (I have not found out yet how to get my device in edl mode from fastboot)
As bricked devices are a more general Android issue and Moto Z4 is not very spread (the corresponding device forum is almost dead), I try to ask my question here in the general Android troubleshooting section. I hope, somebody can give me any advice how to reanimate my device. Maybe, anybody with special Motorola experience who can tell me why I can not flash the full factory image or explain how I can get boot, vbmeta and dspso back to the device. Any help appreciated.
Related
My LG-E970 (AT&T) will not boot. What happened was FreeGee had an error part way though and I did not think anything of it. I had already successfully rooted my phone hours earlier and all seemed to be working well. I turned my phone off for the night and when I went to turn it back on it would not boot. It went into what it called "Demigod" mode, from which I can access Fastboot, but the recovery appears to be broken as well. I have tried accessing Fastboot to re-flash the recovery but neither Fastboot or ADB can even find the device. I've tried every USB driver I can find and nothing seems to help. Device Manager shows when it's connected under Unknown Devices and it names it Android, but ADB and Fastboot don't see it. All I can see on the Fastboot screen is the following information:
FASTBOOT MODE
PRODUCT_NAME - mako
VARIANT - mako 16GB
HW VERSION - rev_10 (168)
BOOTLOADER VERSION - MAKOZ10f
BROADBAND VERSION - N/A
CARRIER INFO - NONE
SERIAL NUMBER - 003fa9505095f3a5
SIGNING - production
SECURE BOOT - enabled
LOCK STATE - unlocked
Any solutions would make me incredibly grateful. I have tried everything I can think of and I hate having to ask for help, but I see no other choice at this point.
fyrestorm90 said:
My LG-E970 (AT&T) will not boot. What happened was FreeGee had an error part way though and I did not think anything of it. I had already successfully rooted my phone hours earlier and all seemed to be working well. I turned my phone off for the night and when I went to turn it back on it would not boot. It went into what it called "Demigod" mode, from which I can access Fastboot, but the recovery appears to be broken as well. I have tried accessing Fastboot to re-flash the recovery but neither Fastboot or ADB can even find the device. I've tried every USB driver I can find and nothing seems to help. Device Manager shows when it's connected under Unknown Devices and it names it Android, but ADB and Fastboot don't see it. All I can see on the Fastboot screen is the following information:
FASTBOOT MODE
PRODUCT_NAME - mako
VARIANT - mako 16GB
HW VERSION - rev_10 (168)
BOOTLOADER VERSION - MAKOZ10f
BROADBAND VERSION - N/A
CARRIER INFO - NONE
SERIAL NUMBER - 003fa9505095f3a5
SIGNING - production
SECURE BOOT - enabled
LOCK STATE - unlocked
Any solutions would make me incredibly grateful. I have tried everything I can think of and I hate having to ask for help, but I see no other choice at this point.
Click to expand...
Click to collapse
I hope you backed up your EFS. Mine was borked by the broken FreeGee that I ran the other night.
I was able to install a custom recovery from Linux by adding a udev rule and restarting the udev service. (Unlike Windows nonsense, this doesn't require a complete new packaging of the driver.)
If you're willing to tackle some Ubuntu (which is easy), I can give you a step-by-step to getting a custom recovery on your phone. It will probably work even from a live CD without even having to install Ubuntu to your harddrive.
Have you read and tried about the LGNPST method of flashing the TeenyBins and installing TWRP recovery ??
I think it should work , as I had the same issue as of today and with the help of those I was at least able to install TWRP recovery. Haven't tried flashing any ROM but I think it should work.
------------------------------------------------------;
http://forum.xda-developers.com/showthread.php?t=2230994
Please read it carefully.You'll find all the information in the thread , let me know if I can be of any help.
Here's my thread for the issue I had today , it seems similiar to your's.
http://forum.xda-developers.com/showthread.php?t=2557320
I was trying to fixed my honor 20 pro after atempting the root process, beacuse I thought the warning message (your device is unlocked and can't be trusted) on the boot screen was the cause of why I could't find some apps on the play store such as Netflix. (and I don't need the root anymore)
After I read some guides and tried to restore the system from eRecovery (without success) I tried the bootloader cmd method with the phone connected via usb in fastboot mode.
Unfortunatly i probably deleted some img files by prompting fastboot flash bootloader (but i'm not sure) and i bricked the system which is now stucked in a boot loop.
I'd like to restore the whole system with a factory firmware but I can't find the official one.
I only found one on androidhost.ru but it seems to do not contain any KERNEL.img or SYSTEM.img
Should I asked to the technical support the firmware or does anyone can provide a proper one? or any other solutions?
I'd just like to restore my honor as a new phone without root.
Hello, i want to share my experience because it may me useful for others. I have also a question for you at the end of the story.
I rooted my MI A3 with magisk but without twrp back in 2019 following the guide posted on this forum. The phone had android 9 and I never did software updates. Once in a while a messagge appeared on the screen saying that my software was obsolete and that I needed to update but I always managed to dodge it.
Some days ago my phone started behaving strangly (eg: I turned the volume down to zero but it turned up by itself) so I decided to reboot it. Something went wrong and the phone rebooted in fastboot mode. I tried many things but the phone was only able to boot in fastboot mode.
I thought that maybe the problem was related to the software update that sometimes was popping on the screen. So, i connected the phone to my pc and executed some fastboot commands:
fastboot getvar current-slot (to know which partition was in use. It was B)
fastboot set_active A (to switch to the other partition)
fastboot reboot
The phone rebooted correctly but it was on android 10 (before the problem it was on android 9) and without root. Everything seemed working fine and all the data was safe (only one thing changed, the boot process require much more time now). So, I realized that the phone applied the system update by itself (without my consent).
Now my question. The phone works well for the moment but how can i check the status of the partition B? I suspect that it may be damaged.
Furthermore I would like to flash the stock firmware, clear all the data and unroot the phone. Can I proceed? Should I flash both partitions?
Thanks
Any suggestions?
Hi, I am using a oneplus 7t pro mclaren edition. I have soft-bricked the device. I tried to change the filesystem in twrp to f2fs when i was in stock rom (I know it was a stupid mistake). Now the boot and recovery partitions are destroyed. I can boot to actual fastboot mode. Tried to use payload dumper but whenever it tries to boot fastbootd it says
fastboot: error: Failed to boot into userspace fastboot; one or more components might be unbootable.
Tried erase everything I got the following error using "fastboot -w"
Erasing 'userdata' OKAY [ 0.229s]
/home/abhijith/Documents/op7t/output/make_f2fs failed with status 1
fastboot: error: Cannot generate image for userdata
I have heard of MSM unbrick tool but as far as i know it only works in windows , before installing VM with windows , I want to know if there is any other way i can recover my device. I have a11 fastboot rom and a12 stock rom. Please help
I have exactly the same problem, same errors etc. if I find any solution I'll post it here. Can't use my phone until then I guess. It all happened after my phone was bricked after trying to install TWRP (previously used LineageOS Recovery).
I followed this guide which resulted in the same errors as for you: https://forum.xda-developers.com/t/...ock-fastboot-roms-for-oneplus-7t-pro.3991189/
Okay, I managed to unbrick my phone, but you won't like the (probably only) solution:
- You NEED Windows (7-10) for this, as the tools are only available on this platform, sadly
- There is this one Indian Guy that will save you:
- Includes how to install all drivers and how to get your phone into COM Mode
- This uses the MSM tool. For 1+ 7T Pro, get it here: https://forum.xda-developers.com/t/...l-to-restore-your-device-to-oxygenos.4002909/
- This is going to STOCK RESET you phone 100%, meaning that your bootloader will be locked etc.
- If you get into any Chinese menu after the phone reboots, you can use Google Lens for translation
I can't believe this worked because it just feels so hacky, but trust me, it's a good last resort as you can always put your phone into COM Mode, regardless of how hard you messed up the system [citation needed].
For me even in device manager qualcomm device itself is not showing :0
abhijiths362 said:
For me even in device manager qualcomm device itself is not showing :0
Click to expand...
Click to collapse
Follow the video. When all drivers are installed and you hold both volume buttons while the device is off, it will show up as a COM/serial device for a few seconds before booting.
Important: Only connect the cable while already pressing the buttons or it won't work.
I was able to get to edl mode and msm tool was detecting but now i am facing sahara communication error i dont have official cable so maybe that might be the reason will try that also
@Colin_T Thanks for the help. I was able to install stock rom to my oneplus 7t pro. I really want to install pixel experience, in the instructions it is saying flash oos 12 firmware. But in the official website i am only seeing 11. What to do?
My phone (Moto G Play 2021 Guamna XT2093-4) got stuck in a boot loop and I can not for the life of me figure out what to do about this. I have looked for the relevant guides and have no idea what I am looking for, I have searched for BOOT LOOP but can not find something that is completely relevant to my phone.
Someone please point me in the right direction so I can get my phone back up and running as this is frustrating to have this happen and I have no clue where to look for this.
nameo said:
My phone (Moto G Play 2021 Guamna XT2093-4) got stuck in a boot loop and I can not for the life of me figure out what to do about this. I have looked for the relevant guides and have no idea what I am looking for, I have searched for BOOT LOOP but can not find something that is completely relevant to my phone.
Someone please point me in the right direction so I can get my phone back up and running as this is frustrating to have this happen and I have no clue where to look for this.
Click to expand...
Click to collapse
Reset the moto g power (2021)| Motorola Support US
motorola-global-portal.custhelp.com
sd_shadow said:
Reset the moto g power (2021)| Motorola Support US
motorola-global-portal.custhelp.com
Click to expand...
Click to collapse
Thanks, although none of those steps worked, and when I go to "Recover Mode" I get a No Command screen.
I want to note that I did download the latsest firmware from LMSA, which gave me firmware GUAMNA_RETAIL_RZAS31.Q2_146_14_16_subsidy_DEFAULT_regulatory_DEFAULT_CFC.xml
Which then I tried to follow the steps with flashing the firmware from scratch using the Online FlashFile Converter Tool, based on the flashfile.xml in that folder with the firmware.
I followed those steps, without clearing my user data, and the phone still continues to be in a boot loop, but then comes to a screen that says "Boot Failed. Press POWER KEY to Retry", and has a bit more infor saying:
AP FastBoot Flash Mode (Secure)
No Bootable A/B slot
Failed to boot Linux, falling back to fastboot
FastBoot Reason: Fall-through from normal boot mode
I then tried to manually flash the gpt.bin partition per this post with below:
[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
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot oem fb_mode_clear
Still returns with the same No Bootable A/B slot error, then I tired to re-flash again manually per this post:
Moto G Power flashing guide
This guide also applies on other Moto phones shipping with Android 10 (not compatible with phone updated from Android 9) Requirements: * Adb must be up to date. You will use new fastbootd interface. You can toggle between bootloader and...
forum.xda-developers.com
Only up to step 7, which I also skipped wiping user data, and then did fastboot reboot, same No Bootable A/B slot
I am not sure what else I can do.
Update, I tried the LMSA restore with wiping my data, still have A/B slot issue.