Hi!
After flashing my first phone (Nexus 5) using my Fedora Workstation OS, I got encouraged and decided to degoogle my Motorola X4 and install Lineage_OS on it. I have Moto X4 XT1900-7. I successfully unlocked the bootloader and downloaded newest TWRP (3.4.0.0) for my device. I moved the zip file to my platform tools folder and than used:
sudo fastboot flash boot recovery.img
Unfortunately I think, the recovery.img file was TWRP that I previously used to install LineageOS on Nexus 5. My phone showed that it was installed in partition B
After that I used command:
sudo fastboot boot recovery.img
And nothing was happening. So in the fastboot mode I manually picked recovery mode, this is when my device went into infinite loop, and at the end it kicked me back to fastboot screen - it looks like that right now (see pictures below). I can't access recovery mode, I can't flash any other version of TWRP (I tried), I can't start the device.
I will be forever grateful if you can give me some help - what do I have to do now to go back to stock ROM or to proceed with installing LIneage_OS? I'm not very advanced so please forgive me if I will be asking some stupid questions here!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sorry, I can't upload the photos for some reason.
Here's what I see after starting fastboot mode:
AP Fastboot Flash Mode (Secure)
BL: MBM-3.0-payton_retail-8510c11-190829
Baseband: <not found>
Product/Variant: payton XT1900-7 32GB P4
Serial Number: ZY224HC647
CPU: SDM630 1.0 (6)
eMMC: 32 GB SAMSUNG DD68MB RV=08 PV=02 FV=0000000000000002
DRAM: 3GB SAMSUNG LP4x DIE=12Gb M5=01 M6=06 M7=00 M8=0E
Console [NULL]: null
Tools Mode Config: DISABLED
Power OK
flashing_unlocked
Connect USB Data Cable
Here's what I see when I try to enter recovery mode manually from fastboot:
If this is a Verizon device, please use the Software Repair Assistant on computer to repair your device. Connect your device to your computer to get the Software Repair Assistant.
If this is not a Verizon device or Software Repair Assitant did not help for any reason, please connect customer care centre for further assistant.
AP Fastboot Flash Mode (Secure)
No bootable A/B slot
Failed to boot Linux, falling back to fastboot
Fastboot Reason: Fall-through from recovery boot mode
The x4 is an A/B device so the partition setup has changed a bit. There is not longer a recovery partition and the recovery is embedded into boot partition BUT you can't just flash it like you did – that will wipe out the bootimage of the ROM. You also should not have to use `sudo` with fastboot. Read the instructions here to install TWRP, or if you just want to use it temporarily, skip the installing the zip part.
I'm surprised `fastboot boot twrp.img` is not working for you. But you may need to re-flash the stock boot partition that you overwrote with the boot partition from one of the zips here. Determine your current version by running `fastboot getvar all`. If you can't match your current version, you may have to flash the entire stock ROM. Open the flashfile.xml to determine the fastboot commands you need to run. For example:
Code:
<step MD5="fab3b8601a77f38f851d9ccbb191def7" filename="bootloader.img" operation="flash" partition="bootloader"/> => fastboot flash bootloader bootloader.img
<step MD5="b7b1b121f4f96a4a7e1b24848ed3f23b" filename="NON-HLOS.bin" operation="flash" partition="modem"/> => fastboot flash modem NON-HLOS.bin
and so on...
I would skip the steps to erase any partitions until you have booted into TWRP and backed up everything. Speaking of which, as soon as you get into TWRP... back up persist and everything else other than system and data to an SD card!
---------- Post added at 08:17 AM ---------- Previous post was at 08:04 AM ----------
And after re-reading your first post, you definitely need to use the proper TWRP and follow the device specific instructions! Don't assume it's like another device. You'll likely end up with an expensive paperweight if you continue down that road...
Most mistakes can be fixed through fastboot but not all.
Just want to help, be careful
Thank You very much! I will try to follow those instructions and get back to You
EDIT:
I tried to install twrp using the link you provided above.
This is what I experienced so far, using terminal in Linux (POP_OS):
[email protected]:~/Programs/platform-tools$ adb
Android Debug Bridge version 1.0.41
Version 30.0.4-6686687
Installed as /home/asti/Programs/platform-tools/adb
[email protected]:~/Programs/platform-tools$ adb devices
List of devices attached
[email protected]:~/Programs/platform-tools$ fastboot devices
ZY224HC647 fastboot
[email protected]:~/Programs/platform-tools$ fastboot boot path/to/twrp.img
fastboot: error: cannot load 'path/to/twrp.img': No such file or directory
[email protected]:~/Programs/platform-tools$ fastboot boot ~/Programs/platform-tools/twrp.img
Sending 'boot.img' (33432 KB) OKAY [ 0.945s]
Booting (bootloader) Failed to load/authenticate boot image: Not Found
FAILED (remote: '')
fastboot: error: Command failed
[email protected]:~/Programs/platform-tools$ ~/Programs/platform-tools/twrp.img
bash: /home/asti/Programs/platform-tools/twrp.img: Permission denied
[email protected]:~/Programs/platform-tools$ adb push ~/Programs/platform-tools/twrp.zip /sdcard
adb: error: failed to get feature set: no devices/emulators found
[email protected]:~/Programs/platform-tools$ fastboot boot ~/Programs/platform-tools/twrp.img
Sending 'boot.img' (33432 KB) OKAY [ 0.939s]
Booting (bootloader) Failed to load/authenticate boot image: Not Found
FAILED (remote: '')
fastboot: error: Command failed
[email protected]:~/Programs/platform-tools$ fastboot getvar all
(bootloader) kernel: uefi
(bootloader) version-bootloader: MBM-3.0-payton_retail-8510c11-190829
(bootloader) product: payton
(bootloader) board: payton
(bootloader) secure: yes
(bootloader) hwrev: P4
(bootloader) radio: EMEA
(bootloader) storage-type: eMMC
(bootloader) emmc: 32GB SAMSUNG DD68MB RV=08 PV=02 FV=0000000000000002
(bootloader) ufs: N/A
(bootloader) ram: 3GB SAMSUNG LP4x DIE=12Gb M5=01 M6=06 M7=00 M8=0E
(bootloader) cpu: SDM630 1.0 (6)
(bootloader) serialno: ZY224HC647
(bootloader) cid: 0x0032
(bootloader) channelid: 0x40
(bootloader) uid: 734CE21E
(bootloader) securestate: flashing_unlocked
(bootloader) verity-state: disabled (0)
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 536870912
(bootloader) reason: Fall-through from normal boot mode
(bootloader) imei: 356516080692333
(bootloader) meid:
(bootloader) date: 10-14-2017
(bootloader) sku: XT1900-7
(bootloader) carrier_sku:
(bootloader) battid: SNN5995A
(bootloader) battery-voltage: 4259
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) ro.build.fingerprint[0]: motorola/payton_tmopl/payton:9/PPW
(bootloader) ro.build.fingerprint[1]: S29.69-37-5/63ca8:user/release-key
(bootloader) ro.build.fingerprint[2]: s
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.29.381.29.payton_tmo
(bootloader) ro.build.version.full[1]: pl.tmopl.en.US
(bootloader) ro.build.version.qcom: LA.UM.7.2.r1-04900-sdm660.0
(bootloader) version-baseband: <not found>
(bootloader) kernel.version[0]: Linux version 4.4.153-perf-g3ff98f3 (hud
(bootloader) kernel.version[1]: [email protected]) (gcc version 4.9.x 201
(bootloader) kernel.version[2]: 50123 (prerelease) (GCC) ) #1 SMP PREEMP
(bootloader) kernel.version[3]: T Thu Aug 29 11:07:24 CDT 2019
(bootloader) git:abl: MBM-3.0-payton_retail-8510c11-190829
(bootloader) git:xbl: git:xbl
(bootloader) gitmic: gitmic
(bootloader) git:rpm: git:rpm
(bootloader) git:tz: git:tz
(bootloader) git:hyp: git:hyp
(bootloader) git:devcfg: git:devcfg
(bootloader) git:cmnlib: git:cmnlib
(bootloader) git:cmnlib64: git:cmnlib64
(bootloader) git:keymaster: git:keymaster
(bootloader) gitrov: gitrov
(bootloader) git:storsec: git:storsec
(bootloader) frp-state: no protection (0)
(bootloader) ro.carrier: reteu
(bootloader) current-slot:
(bootloader) running-bl-slot: _b/_b
(bootloader) running-boot-lun: 0
(bootloader) slot-count: 2
(bootloader) slot-successful:_a: yes
(bootloader) slot-successful:_b: no
(bootloader) slot-unbootable:_a: yes
(bootloader) slot-unbootable:_b: yes
(bootloader) slot-retry-count:_a: 6
(bootloader) slot-retry-count:_b: 0
all: listed above
Finished. Total time: 0.094s
I will try to re-install stock ROM and keep you updated.
What commands should I exactly run on terminal while my phone is in the fastboot mode to install the stock ROM? Can somebody help me with that? I'm sorry but I'm a total newbie!
I've read the flashfile.xml that you suggested @htsmi but I don't understand much from it nor know what should I do next with it.
Yeah it looks like it is refusing to boot anything, even from fastboot, due to the corrupted boot partition
Note: installing TWRP is not going to be successful until you get your boot partition back to normal. And I would only boot into TWRP using `fastboot boot twrp.img` – replace twrp.img with the file you downloaded from the TWRP payton page – because the installed version will be overwritten when you install a custom ROM.
It looks like your is the 'TMOPL' variant which I don't see in the lolinet site. One way around that is to use Lenovo Moto Smart Assistant on a Windows machine to download and install the original firmware. Unfortunately it now makes you sign in with your Lenovo account to use the software. I don't remember the exact name of the operation in there but it's something like "system recovery". It will automatically download and install the proper firmware in fastboot mode so you don't have to worry about choosing the right one.
Let me know if you're at least able to boot back into stock after that. Then I'll go over steps for TWRP in order to backup important partitions before you install LineageOS if you need them.
Hi!
I used Lenovo Smart Assistant - it connects to my device and reads my phone model, but when I try to go through recovery, it shows a message that some key data is missing and the installation can't proceed.
Is there a way to install stock ROM from terminal, using fastboot? Could you help me with that?
@htsmi Here's what I saw while using what you suggested:
https://u.pcloud.link/publink/show?code=XZ2vSHXZljmYvB2SOqYb62fVC95FCuHM5vWy
Related
I recently got a Moto G 2014 from a friend, who somehow managed to brick it to a point, where it's unrecoverable for me, even after hours of googling and trying. Maybe someone of you has an idea on how to fix this.
I still can boot to fastboot mode, but no farther than that. Recovery doesn't work, and system also. When I'm trying to boot either, I get a fall-through to bootloader with reason "Invalid boot image header".
I already tried restoring stock by flashing several different stock ROMs, but none of them worked so far. I also tried different systems (Windows 10, Arch Linux), but it doesn't seem to make a difference.
When flashing gpt.bin via fastboot, it shows me no error (most of the time, sometimes it's "Preflash validation failed") in console, but the phone shows a "no valid gpt found" message afterwards.
When trying to flash any other partition, I either get "Failed to erase partition" and "Failed to flash partition logo/motoboot/whatever" or (bootloader) permission denied.
I am running fastboot as root on my Arch machine, and when typing "fastboot devices" it shows the serial number of the device followed by "fastboot".
Bootloader is already unlocked.
Here is a dump of "fastboot getvar all":
Code:
(bootloader) version: 0.5
(bootloader) version-bootloader: 4883(*)
(bootloader) product: titan
(bootloader) secure: yes
(bootloader) hwrev: 0x8400
(bootloader) radio: 0x5
(bootloader) emmc: 8GB Sandisk REV=06 PRV=07 TYPE=17
(bootloader) ram: 1024MB Samsung S4 SDRAM DIE=4Gb
(bootloader) cpu: MSM8226 CS
(bootloader) serialno: ZX1D224SLX
(bootloader) cid: 0x0007
(bootloader) channelid: 0x45
(bootloader) uid: FEC299050F000000000000000000
(bootloader) unlocked: yes
(bootloader) securestate: unlocked
(bootloader) iswarrantyvoid: yes
(bootloader) mot_sst: 3
(bootloader) max-download-size: 536870912
(bootloader) reason: Fall-through from mot-charger boot mode
(bootloader) imei: [censored]
(bootloader) meid:
(bootloader) date: 09-03-2014
(bootloader) sku: XT1068
(bootloader) battid: (null)
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Thu Aug 6 3:34: 7 UTC 2015"
(bootloader) ro.build.fingerprint[0]: motorola/titan_retde/titan_umtsds:
(bootloader) ro.build.fingerprint[1]: 5.0.2/LXB22.99-16.3/6:user/release
(bootloader) ro.build.fingerprint[2]: -keys
(bootloader) ro.build.version.full[0]: Blur_Version.22.56.3.titan_retde.
(bootloader) ro.build.version.full[1]: retdeall.en.DE
(bootloader) ro.build.version.qcom[0]: AU_LINUX_ANDROID_LNX.LA.3.5.1_RB1
(bootloader) ro.build.version.qcom[1]: .04.04.02.048.045
(bootloader) version-baseband:
(bootloader) kernel.version[0]: Linux version 3.4.42-g0bea67a ([email protected]
(bootloader) kernel.version[1]: ilclbld36) (gcc version 4.8 (GCC) ) #1 S
(bootloader) kernel.version[2]: MP PREEMPT Tue Aug 25 22:40:50 CDT 2015
(bootloader) sdi.git: sdi.git
(bootloader) sbl1.git: sbl1.git
getvar:all FAILED (status read failed (No such device))
finished. total time: 22.864s
I really hope someone of you has an idea, because I am stumped.
Ever tried to boot twrp ? I mean directly booting with the command: fastboot boot twrp.img ?
This version: https://dl.twrp.me/titan/twrp-2.8.5.0-titan.img Newer ones may fail
zman01 said:
Ever tried to boot twrp ? I mean directly booting with the command: fastboot boot twrp.img ?
This version: https://dl.twrp.me/titan/twrp-2.8.5.0-titan.img Newer ones may fail
Click to expand...
Click to collapse
Yes, I forgot to mention it, but I already tried this. Result is an error message on the phone saying "Incomplete boot image for booting".
any solution you got for this problem?
Unfortunately not, no
Hey Guys!
I have a problem with a motorola xt1900 (x4) is stuck in the unlock bootloader notify, I tried many forms by fastboot but did not succeed.
First of all, I installed the lineage 16.0, it was great, but then I wanted to do root, I downloaded the magisk and it gave bootloop after flash, so I tried to put the 8.0 stockrom and I've been stuck ever since, can't unlock again, i still have the code from motorola.
"the device is Corrupted, Can not Be trusted, Will not boot"
I tried to flash the TWRP, but I could not.
I ended up in a semi-hard bricked phone where recovery wouldn't boot and my phone told me both slot A and B was missing. My way of fixing my phone when all I could do was seeing a bootloader with an error message (as you seem to have) was to flash it with the flash all software found here https://www.androidfilehost.com/?fid=890278863836292604 Run flash_all.bat as an administrator in Windows or ./flash_all in Linux as root ( sudo ./flash_all ). Remember, you don't need to enter recovery, the boot error message should be good enough.
The thing you need to accept is all your data will be wiped. If you wanted to save anything, it was already too late. Once you run that flash, reboot your phone into your bootloader and run the command
fastboot boot '/your_path_here/twrp-3.2.3-1-payton.img'
This will force your phone to boot using TWRP from your computer and from there you should be able to upload a ROM and install. -- Remember if using Linux to add the sudo command before that.
Hey man! I'm on Windows.
By the way, don't care about data. just want my phone working.:crying:
still same error message, (bootloader) "flash permission denied"
"remote failure"
I try again the unlock code, says ok finished, but didn't work.
danielwah said:
Hey man! I'm on Windows.
By the way, don't care about data. just want my phone working.:crying:
still same error message, (bootloader) "flash permission denied"
"remote failure"
I try again the unlock code, says ok finished, but didn't work.
Click to expand...
Click to collapse
The same happened to me using the regular adb flashboot commands...I have my X4 totaly locked... Any new?
tuliusy2k said:
The same happened to me using the regular adb flashboot commands...I have my X4 totaly locked... Any new?
Click to expand...
Click to collapse
My errors:
(bootloader) WARNING: OEM images are required in the LOCKED state.
(bootloader) Flashing images can result in a non-boot condition.
(bootloader) Flash a proper OEM signed boot.img first.
This is my fastboot getvar all
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot getvar all
(bootloader) kernel: uefi
(bootloader) version-bootloader: MBM-3.0-uefi-641a15b-180328
(bootloader) product: payton
(bootloader) board: payton
(bootloader) secure: yes
(bootloader) hwrev: P4
(bootloader) radio: LATAM
(bootloader) storage-type: eMMC
(bootloader) emmc: 32GB SAMSUNG DD68MB RV=08 PV=02 FV=0000000000000002
(bootloader) ufs: N/A
(bootloader) ram: 3GB SAMSUNG LP4x DIE=12Gb M5=01 M6=06 M7=00 M8=0E
(bootloader) cpu: SDM630 1.0 (6)
(bootloader) serialno: 0039062204
(bootloader) cid: 0x0032
(bootloader) channelid: 0x01
(bootloader) uid: 9EB17BE5
(bootloader) securestate: oem_locked
(bootloader) verity-state: enforcing (0)
(bootloader) iswarrantyvoid: no
(bootloader) max-download-size: 536870912
(bootloader) reason: Volume down key pressed
(bootloader) imei: ***********************
(bootloader) meid:
(bootloader) date: 10-10-2017
(bootloader) sku: XT1900-6
(bootloader) carrier_sku:
(bootloader) battid: SNN5995A
(bootloader) battery-voltage: 3942
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) ro.build.fingerprint[0]: motorola/payton/payton:8.0.0/OPWS2
(bootloader) ro.build.fingerprint[1]: 7.57-40-25/32:user/release-keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.27.301.32.payton.ret
(bootloader) ro.build.version.full[1]: ail.en.US
(bootloader) ro.build.version.qcom: <not found>
(bootloader) version-baseband: <not found>
(bootloader) kernel.version[0]: Linux version 4.4.78-perf-g18bb7f8 (huds
(bootloader) kernel.version[1]: [email protected]) (gcc version 4.9.x 20150
(bootloader) kernel.version[2]: 123 (prerelease) (GCC) ) #1 SMP PREEMPT
(bootloader) kernel.version[3]: Thu Oct 18 11:48:40 CDT 2018
(bootloader) git:abl: MBM-3.0-uefi-641a15b-180328
(bootloader) git:xbl: MBM-3.0-uefi-dfccc3a-180328
(bootloader) gitmic: MBM-3.0-uefi-dfccc3a-180328
(bootloader) git:rpm: MBM-3.0-uefi-245b046-180328
(bootloader) git:tz: MBM-3.0-uefi-eee7f2d-dirty-180328
(bootloader) git:hyp: MBM-3.0-uefi-eee7f2d-dirty-180328
(bootloader) git:devcfg: MBM-3.0-uefi-eee7f2d-dirty-180328
(bootloader) git:cmnlib: MBM-3.0-uefi-eee7f2d-dirty-180328
(bootloader) git:cmnlib64: MBM-3.0-uefi-eee7f2d-dirty-180328
(bootloader) git:keymaster: MBM-3.0-uefi-eee7f2d-dirty-180328
(bootloader) gitrov: MBM-3.0-uefi-eee7f2d-dirty-180328
(bootloader) git:storsec: MBM-3.0-uefi-eee7f2d-dirty-180328
(bootloader) qe: "qe 0/0"
(bootloader) frp-state: no protection (0)
(bootloader) ro.carrier: amxbr
(bootloader) current-slot: _a
(bootloader) running-bl-slot: _a/_a
(bootloader) running-boot-lun: 0
(bootloader) slot-suffixes: _a,_b
(bootloader) slot-count: 2
(bootloader) slot-successful:_a: no
(bootloader) slot-successful:_b: no
(bootloader) slot-unbootable:_a: no
(bootloader) slot-unbootable:_b: no
(bootloader) slot-retry-count:_a: 6
(bootloader) slot-retry-count:_b: 0
all: listed above
finished. total time: 0.219s
I have the same problem "The device is Corrupted, Cannot Be trusted, Will not boot"
Use the fastboot getvar all command, find the sku version of it and download the rom with the same number that appears in the fastboot and install normally, it worked with me now at dawn. The only rom that works when the unit is in this state and the one in it
i am the same problem...
After relock bootloader it wont boot, dont enter recovery, only enter in fastboot, but flashing is locked!
Any stock system not flash....
---------- Post added at 03:44 PM ---------- Previous post was at 03:43 PM ----------
i am the same problem...
After relock bootloader it wont boot, dont enter recovery, only enter in fastboot, but flashing is locked!
Any stock system not flash....
I found the solution! (for me)
1 - Enter in fastboot (volume down + power), and boot up the "boot.img" of the last system used in my phone. (Lineage 16.0)
https://drive.google.com/file/d/1OaWtQo1jfX5glVj1pnjDnu8NDkgDOHDd/view?usp=sharing
"fastboot boot boot.img"
And the phone enter a System!
2 - Activate ADB, and allow superuser comands in ADB - "Developer Settings"
And run the command for show "Enable OEM Unlocking"
adb shell setprop ro.oem_unlock_supported 1
Check toggle "Enable OEM Unlocking"
3 - Power off and put in fastboot again
4 - re-run "fastboot oem unlock <<your code>>"
5 - Ready! Your phone unlocked flashing again!
I woke up in the morning and found my phone had crashed. I turned it off and it woudlnt come back on. same error message...
your devise is corrupt. it cant be trusted and will not boot.
Has anyone found a way to recover it without losign nay data. i really cant afford to lose my pics and videos.
Any help would be appreciated.
PS i rooted this phone a long time ago and not fluent in the root process
juniofdm said:
I found the solution! (for me)
1 - Enter in fastboot (volume down + power), and boot up the "boot.img" of the last system used in my phone. (Lineage 16.0)
https://drive.google.com/file/d/1OaWtQo1jfX5glVj1pnjDnu8NDkgDOHDd/view?usp=sharing
"fastboot boot boot.img"
And the phone enter a System!
Click to expand...
Click to collapse
I tried this on my device (never rooted, never unlocked bootloader), and at first it gave me the error:
Sending 'boot.img' (22249 KB) FAILED (remote: 'unknown command')
fastboot: error: Command failed
Then subsequent attempts just get stuck on the 'Sending' line. This was using the stock image from this post: https://forum.xda-developers.com/t/rom-stock-pie-9-0-moto-x4-retail-android-pie.3876156/
I've run out of options as the Rescue and Smart Assistant isn't working either. Any help appreciated.
it worked for me thanks
So i just did something really stupid, i unlocked the bootloader and installed a custom rom which worked relatively well, but then i tried to relock the bootloader with the custom rom installed. Now the bootloader doesnt work i get this error in cmd:
C:\Users\gabe\Downloads\minimal_adb_fastboot_1.4.3_portable>fastboot oem unlock
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
...
(bootloader) invalid boot state
OKAY [ 0.172s]
finished. total time: 0.187s
I can still access recovery (TWRP) and flash roms but i cant boot into any rom
Gabe.lars97 said:
So i just did something really stupid, i unlocked the bootloader and installed a custom rom which worked relatively well, but then i tried to relock the bootloader with the custom rom installed. Now the bootloader doesnt work i get this error in cmd:
C:\Users\gabe\Downloads\minimal_adb_fastboot_1.4.3_portable>fastboot oem unlock
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
...
(bootloader) invalid boot state
OKAY [ 0.172s]
finished. total time: 0.187s
I can still access recovery (TWRP) and flash roms but i cant boot into any rom
Click to expand...
Click to collapse
send a screenshot of bootloader screen and issue you face prolly you can fix it by flashing stock back
What's the output of fastboot getvar all?
I tried the fastboot oem unlock command on my unlocked bootloader and it gives me the same error, so I don't think you've got any issues there.
The window to the left is when I tried to unlock the bootloader again and the window to the right is when I tried to flash a stock rom
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Try fastboot oem fb_mode_clear
Also, the images didn't attach (Could be you have too new of an account)
The getvar all info is:
C:\Users\gabe\Downloads\minimal_adb_fastboot_1.4.3_portable>fastboot getvar all
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) version: 0.5
(bootloader) version-bootloader: moto-msm8953-C2.07
(bootloader) product: sanders
(bootloader) board: sanders
(bootloader) secure: yes
(bootloader) hwrev: P4
(bootloader) radio: 3
(bootloader) storage-type: emmc
(bootloader) emmc: 32GB SKHYNIX HBG4a2 RV=08 PV=A5 FV=00000000000000A5
(bootloader) ram: 3GB SKHYNIX LP3 DIE=8Gb M5=06 M6=04 M7=00 M8=5F
(bootloader) cpu: MSM8953
(bootloader) serialno: ZY322J6PRM
(bootloader) cid: 0x0032
(bootloader) channelid: 0x1c
(bootloader) uid: 6C8C46F400000000000000000000
(bootloader) securestate: flashing_locked
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 536870912
(bootloader) reason: Reboot mode set to fastboot
(bootloader) imei: 355657080847294
(bootloader) meid:
(bootloader) date: 12-20-2017
(bootloader) sku: XT1800
(bootloader) battid: SB18C15118
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Sat Dec 5 7:33:44 UTC 1970"
(bootloader) ro.build.fingerprint[0]: motorola/sanders_n/sanders_n:7.1.1
(bootloader) ro.build.fingerprint[1]: /NPSS26.116-26-18/22:user/release-
(bootloader) ro.build.fingerprint[2]: keys
(bootloader) poweroffalarm: 1
(bootloader) ro.build.version.full[0]: Blur_Version.26.346.22.sanders.re
(bootloader) ro.build.version.full[1]: tail.en.US
(bootloader) ro.build.version.qcom: LA.UM.5.6.r1-03800-89xx.0
(bootloader) version-baseband: M8953_24.34.07.35.01R SANDERS_LATAM_CUST
(bootloader) kernel.version[0]: Linux version 3.18.31-perf-gce86ddc-0017
(bootloader) kernel.version[1]: 1-g3d401e1 ([email protected]) (gcc ver
(bootloader) kernel.version[2]: sion 4.9 20150123 (prerelease) (GCC) ) #
(bootloader) kernel.version[3]: 1 SMP PREEMPT Tue May 29 21:14:21 CDT 20
(bootloader) kernel.version[4]: 18
(bootloader) sbl1.git: git=MBM-NG-VC2.07-0-gb564bed
(bootloader) rpm.git: git=MBM-NG-VC2.06-0-g5578f74
(bootloader) tz.git: git=99b0ebd-dirty
(bootloader) devcfg.git: git=99b0ebd-dirty
(bootloader) keymaster.git: git=99b0ebd-dirty
(bootloader) cmnlib.git: git=99b0ebd-dirty
(bootloader) cmnlib64.git: git=99b0ebd-dirty
(bootloader) prov.git: git=99b0ebd-dirty
(bootloader) aboot.git: git=MBM-NG-VC2.07-0-g19332ff
(bootloader) qe: qe 0/0
(bootloader) frp-state: no protection (77)
(bootloader) ro.carrier: retcl
all: listed above
Ok. That's actually super helpful information.
1: You have the last version of Nougat before they started rolling out oreo. This is good.
2: It says your bootloader is locked. That is bad.
lets start with a simple possible fix. Download the Lenovo Motorola Smart assistant and install it. https://support.lenovo.com/us/en/downloads/ds101291
When it opens, go to the Flash tab at the top. It will give you two choices. Upgrade or Recover. Obviously we want recover.
It should detect your phone, and download and flash the compatible firmware. This software is designed to work with locked bootloaders, so it should fix it.
If it doesn't, we can try doing it on our own. We can reflash the firmware with a locked bootloader as long as you have the same or newer that what is currently on it. So you'd need NPSS26.116-26-18 which is also easy to get.
the lenovo motorola smart assistant doesnt recognize the device nor lets me manually select the model
i tried flashing the NPSS26.116-26-18 ROM as explained here: https://forum.xda-developers.com/mo...lash-official-firmware-moto-g5s-plus-t3681018 but after flashing a few files it begins failing the files
https://photos.app.goo.gl/v8XTki3CiU8AFcoT7
I think we are both having the same issues. https://forum.xda-developers.com/mo...ed-potter-mistake-sanders-help-t3866370/page2
@Gabe.lars97, so how did you solve the problem?
I have been using my Moto X4 on a custom ROM (with magisk) for over 3 years without any issues. Just yesterday, my phone battery died and I plugged in a charger and start up the phone in a couple of mins and I get this message "Your device is corrupt. It cant be trusted and will not boot.
I was surprised to find that on the Fastboot screen, the OEM Status shows as LOCKED - How can this happen after so many years and that too in a snap ?
The problem now is that I'm not sure if the "OEM Unlocking option" under Developer Settings is disabled (It has been long since I went into these settings).
When I try to unlock OEM, I get this message below. What are my options now since the phone doesn't start for me to enable the option using the GUI ? I would like to access my data if there is an chance.
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem unlock O4USDSC3JS6UX4VQBA1B
...
(bootloader) Check 'OEM unlocking' in Android Settings > Developer
(bootloader) Options
OKAY [ 0.012s]
finished. total time: 0.013s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot getvar all
(bootloader) kernel: uefi
(bootloader) version-bootloader: MBM-3.0-uefi-c18849c-181018
(bootloader) product: payton
(bootloader) board: payton
(bootloader) secure: yes
(bootloader) hwrev: P4
(bootloader) radio: APAC
(bootloader) storage-type: eMMC
(bootloader) emmc: 64GB SAMSUNG DH6DMB RV=08 PV=05 FV=0000000000000005
(bootloader) ufs: N/A
(bootloader) ram: 4GB SAMSUNG LP4x DIE=16Gb M5=01 M6=06 M7=10 M8=12
(bootloader) cpu: SDM630 1.0 (0)
(bootloader) serialno: ZY224GABCD
(bootloader) cid: 0xDEAD
(bootloader) channelid: 0x00
(bootloader) uid: 00000000
(bootloader) securestate: oem_locked
(bootloader) verity-state: enforcing (0)
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 536870912
(bootloader) reason: Volume down key pressed
(bootloader) imei: 351899081981234
(bootloader) meid:
(bootloader) date: 10-25-2017
(bootloader) sku: XT1900-2
(bootloader) carrier_sku:
(bootloader) battid: SNN5995A
(bootloader) battery-voltage: 4135
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) ro.build.fingerprint[0]: motorola/payton/payton:8.0.0/OPWS2
(bootloader) ro.build.fingerprint[1]: 7.57-40-3-15/16:user/release-keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.27.306.16.payton.ret
(bootloader) ro.build.version.full[1]: ail.en.US
(bootloader) ro.build.version.qcom: <not found>
(bootloader) version-baseband[0]: M660_7036.16.01.69.02R PAYTON_APACDSDS
(bootloader) version-baseband[1]: _CUST
(bootloader) kernel.version[0]: Linux version 4.4.78-perf-gc27dd6c (huds
(bootloader) kernel.version[1]: [email protected]) (gcc version 4.9.x 20150
(bootloader) kernel.version[2]: 123 (prerelease) (GCC) ) #1 SMP PREEMPT
(bootloader) kernel.version[3]: Thu Oct 18 11:53:59 CDT 2018
(bootloader) git:abl: MBM-3.0-uefi-c18849c-181018
(bootloader) git:xbl: MBM-3.0-uefi-dfccc3a-181018
(bootloader) git:pmic: MBM-3.0-uefi-dfccc3a-181018
(bootloader) git:rpm: MBM-3.0-uefi-245b046-181018
(bootloader) git:tz: MBM-3.0-uefi-30789d4-dirty-181018
(bootloader) git:hyp: MBM-3.0-uefi-30789d4-dirty-181018
(bootloader) git:devcfg: MBM-3.0-uefi-30789d4-dirty-181018
(bootloader) git:cmnlib: MBM-3.0-uefi-30789d4-dirty-181018
(bootloader) git:cmnlib64: MBM-3.0-uefi-30789d4-dirty-181018
(bootloader) git:keymaster: MBM-3.0-uefi-30789d4-dirty-181018
(bootloader) git:prov: MBM-3.0-uefi-30789d4-dirty-181018
(bootloader) git:storsec: MBM-3.0-uefi-30789d4-dirty-181018
(bootloader) qe: "qe 1/1"
(bootloader) frp-state: protected (77)
(bootloader) ro.carrier: retin
(bootloader) current-slot: _b
(bootloader) running-bl-slot: _b/_b
(bootloader) running-boot-lun: 0
(bootloader) slot-suffixes: _a,_b
(bootloader) slot-count: 2
(bootloader) slot-successful:_a: yes
(bootloader) slot-successful:_b: yes
(bootloader) slot-unbootable:_a: yes
(bootloader) slot-unbootable:_b: no
(bootloader) slot-retry-count:_a: 6
(bootloader) slot-retry-count:_b: 6
all: listed above
finished. total time: 0.984s
C:\Program Files (x86)\Minimal ADB and Fastboot>
1/ You'd better hide serial and imei number from your post
2/ Moto forums say to try to fix it going back to stock rom using rescue software
Rescue and Smart Assistant Tool - Motorola
<h6><span style="color:#FFFFFF"><strong>Our Rescue and Smart Assistant tool</strong><br />can help diagnose and resolve issues on your<br />Motorola phone or Lenovo phone/tablet.</span></h6>
www.motorola.com
And if does not work to send to repair services
GL
OK. I tried the RSA software and that too identifies my phone correctly, downloads the Stock ROM and failed with an error message saying "Flash Failed. try again". Could this be due to the settings in Developer options being disabled ?(which I cannot get to)
I tried the below to see if it helps, but didnt get far :
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot boot boot.img
downloading 'boot.img'...
OKAY [ 0.514s]
booting...
(bootloader) permission denied!
FAILED (remote failure)
finished. total time: 0.524s
Do I have any options to bring back my phone even if if the data is lost and i need to go back to stock ROM or any other ROM. I just want to have a working phone. Please advise.
Is there a way to unlock the OEM or enable the Unlock OEM in Dev settings without being able to boot into the Operating system ?
Only if you can send adb commands
And so, be able to enter Recovery mode (buttons volume down+power when phone off, just in case)
'Install update > From adb' menus will make you enter adb mode
There may have plenty of softwares for data recovery through adb
Finway said:
Only if you can send adb commands
And so, be able to enter Recovery mode (buttons volume down+power when phone off, just in case)
'Install update > From adb' menus will make you enter adb mode
There may have plenty of softwares for data recovery through adb
Click to expand...
Click to collapse
Thanks. Can adb commands be used even if USB debugging may not be enabled ? Can you guide me to a post on the forum which I can use to follow instructions to try and install a new ROM keeping in mind my current situation.
In Recovery Mode yes you can send adb commands
Do you have acces to it ?
Code:
adb sideload lineage-19.1-20220426-nightly-payton-signed.zip
or any other version of lineage to install it
Info about payton | LineageOS Wiki
wiki.lineageos.org
may i know if this is solved? i have same problem as well, wanna know how to get my x4 out of the error message
My Wife has an X4, xt1900-1 from Google Fi, that she no longer uses as a phone but uses it on wifi only to run a special piece of software. It got the "device is corrupted" error and will not boot to anything other than FastBoot. Adding results of "Fastboot getvar all" at the end of post. Running "Fastboot oem get_unlock_data" returns:
(bootloader) Failed to get unlock data.
OKAY [ 0.002s]
Finished. Total time: 0.003s
Running LMSA initially wouldn't detect the device, then it did detect and begins the re-flash process but fails at flashing around 69 percent.(nice) No other information is given other than flashing failed.
Attempting to flash the firmware that the LMSA downloaded manually via fastboot and it flashes the first couple bits but fails at the bootloader.
Attempting to fastboot boot into twrp returns:
Sending 'boot.img' (38672 KB) OKAY [ 1.412s]
Booting (bootloader) permission denied!
FAILED (remote: '')
fastboot: error: Command failed
I found the blankflash image for this version of payton, when attempting to run it, the terminal just displays:
< waiting for device >
And nothing ever happens.
I've tried it on Windows and Linux with a handful of different cables and the results are the same. Am I SOL and it's time to replace the device?
Thanks,
(bootloader) kernel: uefi
(bootloader) version-bootloader: MBM-3.0-payton_fi-eca8056931-200924
(bootloader) product: payton
(bootloader) board: payton
(bootloader) secure: yes
(bootloader) hwrev: P4
(bootloader) radio: NA
(bootloader) storage-type: eMMC
(bootloader) emmc: 32GB SAMSUNG DD68MB RV=08 PV=02 FV=0000000000000002
(bootloader) ufs: N/A
(bootloader) ram: 3GB SAMSUNG LP4x DIE=12Gb M5=01 M6=06 M7=00 M8=0E
(bootloader) cpu: SDM630 1.0 (2)
(bootloader) serialno: ZY224H58SP
(bootloader) cid: 0xDEAD
(bootloader) channelid: 0x00
(bootloader) uid: 00000000
(bootloader) securestate: oem_locked
(bootloader) verity-state: enforcing (0)
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 536870912
(bootloader) reason: UTAG bootmode configured as fastboot
(bootloader) imei: 356484080483981
(bootloader) meid:
(bootloader) date: 10-15-2017
(bootloader) sku: XT1900-1
(bootloader) carrier_sku:
(bootloader) battid: SNN5995A
(bootloader) battery-voltage: 3899
(bootloader) iccid: 8901260971113779407
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) ro.build.fingerprint[0]: motorola/payton_fi/payton_sprout:9
(bootloader) ro.build.fingerprint[1]: /PPWS29.69-39-6-13/badd5:user/rele
(bootloader) ro.build.fingerprint[2]: ase-keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.29.491.55.payton_fi.
(bootloader) ro.build.version.full[1]: google_fi.en.US
(bootloader) ro.build.version.qcom: LA.UM.7.2.r1-04900-sdm660.0
(bootloader) version-baseband: M660_7048.65.01.101R PAYTON_NA_CUST
(bootloader) kernel.version[0]: Linux version 4.4.153-perf-g097f40be62ed
(bootloader) kernel.version[1]: ([email protected]) (gcc version 4.9.x
(bootloader) kernel.version[2]: 20150123 (prerelease) (GCC) ) #1 SMP PR
(bootloader) kernel.version[3]: EEMPT Thu Sep 24 04:43:29 CDT 2020
(bootloader) git:abl: MBM-3.0-payton_fi-eca8056931-200924
(bootloader) git:xbl: MBM-3.0-payton_fi-b24b3b6a2-200924
(bootloader) gitmic: MBM-3.0-payton_fi-b24b3b6a2-200924
(bootloader) git:rpm: MBM-3.0-payton_fi-f97e5eb-200924
(bootloader) git:tz: MBM-3.0-payton_fi-68ee948c3-200924
(bootloader) git:hyp: MBM-3.0-payton_fi-68ee948c3-200924
(bootloader) git:devcfg: MBM-3.0-payton_fi-68ee948c3-200924
(bootloader) git:cmnlib: MBM-3.0-payton_fi-68ee948c3-200924
(bootloader) git:cmnlib64: MBM-3.0-payton_fi-68ee948c3-200924
(bootloader) git:keymaster: MBM-3.0-payton_fi-68ee948c3-200924
(bootloader) gitrov: MBM-3.0-payton_fi-68ee948c3-200924
(bootloader) git:storsec: MBM-3.0-payton_fi-68ee948c3-200924
(bootloader) frp-state: protected (77)
(bootloader) ro.carrier: retus
(bootloader) current-slot: a
(bootloader) running-bl-slot: _a/_a
(bootloader) running-boot-lun: 0
(bootloader) slot-count: 2
(bootloader) slot-successful:_a: no
(bootloader) slot-successful:_b: no
(bootloader) slot-unbootable:_a: no
(bootloader) slot-unbootable:_b: no
(bootloader) slot-retry-count:_a: 4
(bootloader) slot-retry-count:_b: 0
all: listed above
Finished. Total time: 0.047s
Heyyo, blankflash only works if you reboot the device into EDL mode. I can't remember if powering it off, holding down both volume keys and plugging it into a PC will actually boot it into EDL mode or not for Motorola devices though...
You can also try the TinyFastbootScript and see if that works?
Download the ROM from here:
lolinet mirrors - firmware, software, iso etc.
lolinet mirrors - powered by h5ai
mirrors-obs-2.lolinet.com
Download TinyFastbootScript from here which also has the instructions:
lolinet mirrors - firmware, software, iso etc.
lolinet mirrors - powered by h5ai
mirrors.lolinet.com
If that doesn't work and you can't force reboot to EDL? You can search on Amazon / AliExpress or others for an "Android EDL cable" which can also work to force EDL mode.
ThE_MarD said:
Heyyo, blankflash only works if you reboot the device into EDL mode. I can't remember if powering it off, holding down both volume keys and plugging it into a PC will actually boot it into EDL mode or not for Motorola devices though...
You can also try the TinyFastbootScript and see if that works?
Download the ROM from here:
lolinet mirrors - firmware, software, iso etc.
lolinet mirrors - powered by h5ai
mirrors-obs-2.lolinet.com
Download TinyFastbootScript from here which also has the instructions:
lolinet mirrors - firmware, software, iso etc.
lolinet mirrors - powered by h5ai
mirrors.lolinet.com
If that doesn't work and you can't force reboot to EDL? You can search on Amazon / AliExpress or others for an "Android EDL cable" which can also work to force EDL mode.
Click to expand...
Click to collapse
Awesome thanks for the reply. Yeah I tried a couple different key combinations that I have seen people reference but nothing seemed to work, however I didn't try holding down both volume keys while plugging it in. I'll try that, and also try the tinyfastboot script too and see what happens. Thanks!
Well I think it's toast. The Tinyfastboot script was giving a lot of the same errors when I was running things manually. I could not get the device to boot into EDL through key combinations either. I think the biggest issue is that the bootloader is locked, and cannot be unlocked. I might try to find a cable and give that a shot but I am thinking now it's a waste of time.
Thanks for the help anyway.
Im facing same issue here as well. so EDL method doesnt work?