Locked Bootloader - Bootloop - XT1879-04 - please help - Moto Z2 Force Questions & Answers
I got to this point after following a guide here to install magisk and MK100 Nash. I lost baseband, probably because I naively flashed XT1789-05 firmware from the guide, to an 04. Idk, anyway, I hadn't read as much at that point and thought I needed to lock the bootloader again *duh duh.* So I'm reading a lot about how this might be impossible to recover from and it's starting to look like it. I've downloaded 10s of GB of firmware to multiple computers, and I for sure can say that the bootloader is rejecting any flashing of firmware from OCX27.109-51 or OCX27.109-36 that I've tried anyway. There may be yet more stock firmwares to try, but I think I'm missing the point with all that because shouldn't any stock firmware be accepted by the bootloader? Anyway, if I could get people to muster up whatever they can on getting out of this trap I laid myself, I would really appreciate it. I was very foolish to attempt this when my food stamps and college application depend on me having a phone number. Plus this phone was sweet I feel like I betrayed it.
I've been trying to fuss with Qualcomm recovery but either EDL is broken too, since some commands I've tried to get it into EDL just resulted in it going to the ol' "can't be trusted," screen but that might be just that it's not going into EDL anyway. Thinking about getting a deepflash cable or something. I lack the patience and dexterity to rig it myself right now. But I don'y want to get my hopes up if it's screwed.
One fun quirk is that if I fastboot boot boot.img it actually does boot to a broken OS where "pixel setup" infinitely crashes but I can get it to let me use a black desktop with limited settings, like I can use the flashlight haha. No adb or ability to change developer settings though. In case it wasn't clear, I can't use TWRP, factory reset, or anything but fastboot essentially.
I'm wondering if someone knows a shell script I could possibly load into fastboot to enable OEM unlock again? AS in, commands to change the OEM unlock to "enable" in dev ops?
I noticed fastboot has a shell option '-c' which I was hoping to leverage with one of those broken boot.imgs maybe change the settings that way?
Btw I also have tried using the LMSA tool and it's a piece of crap, it never seemed like it would work on my other computer, but it had a weird connection. I installed windows on this one and it seemed to work, possibly a USB 2.0 thing, but as soon as LMSA seemed to actually be maybe doing something, I lost the ability to sign in. It just hangs forever and says it was successful then asks again (or it doesn't). I added a new windows user, tried reinstalling like 40 times, it behaved erratically but ultimately the problem persisted and now it remembers my login info between uninstalls and across new users but can't actually log in.
(bootloader) kernel: uefi
(bootloader) version-bootloader: MBM-3.0-nash_tmo-641a15b-180420
(bootloader) product: nash
(bootloader) board: nash
(bootloader) secure: yes
(bootloader) hwrev: PVT
(bootloader) radio: NA_UMTS
(bootloader) storage-type: UFS
(bootloader) emmc: N/A
(bootloader) ufs: 64GB SAMSUNG KLUCG4J1ED-B0C1 FV=0200
(bootloader) ram: 4GB SAMSUNG LP4x DIE=16Gb M5=01 M6=06 M7=10 M8=12
(bootloader) cpu: MSM8998 2.1 (0)
(bootloader) serialno: ZY224TL8V5
(bootloader) cid: 0x0015
(bootloader) channelid: 0x85
(bootloader) uid: 3F57D9A7
(bootloader) securestate: flashing_locked
(bootloader) verity-state: logging (0)
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 536870912
(bootloader) reason: Volume down key pressed
(bootloader) imei:<Not zero>
(bootloader) meid:
(bootloader) date: 03-25-2018
(bootloader) sku: XT1789-04
(bootloader) carrier_sku: XT1789-04
(bootloader) battid: SNN5987A
(bootloader) battery-voltage: 3748
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) ro.build.fingerprint[0]: motorola/nash_tmo_c/nash:8.0.0/OCX
(bootloader) ro.build.fingerprint[1]: S27.109-51-7/9:user/release-keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.27.241.9.nash_tmo_c.
(bootloader) ro.build.version.full[1]: tmo.en.US
(bootloader) ro.build.version.qcom: LA.UM.6.4.r1-04300-8x98.0
(bootloader) version-baseband: <not found>
(bootloader) kernel.version[0]: Linux version 4.4.78-perf-g668a0f8 (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 Jan 10 22:25:12 CST 2019
(bootloader) git:abl: MBM-3.0-nash_tmo-641a15b-180420
(bootloader) git:xbl: MBM-3.0-nash_tmo-9869834-180420
(bootloader) gitmic: MBM-3.0-nash_tmo-9869834-180420
(bootloader) git:rpm: MBM-3.0-nash_tmo-b13e14f-180420
(bootloader) git:tz: MBM-3.0-nash_tmo-7d478e6-180420
(bootloader) git:hyp: MBM-3.0-nash_tmo-7d478e6-180420
(bootloader) git:devcfg: MBM-3.0-nash_tmo-7d478e6-180420
(bootloader) git:cmnlib: MBM-3.0-nash_tmo-7d478e6-180420
(bootloader) git:cmnlib64: MBM-3.0-nash_tmo-7d478e6-180420
(bootloader) git:keymaster: MBM-3.0-nash_tmo-7d478e6-180420
(bootloader) git:storsec: MBM-3.0-nash_tmo-7d478e6-180420
(bootloader) gitrov: MBM-3.0-nash_tmo-7d478e6-180420
(bootloader) qe: "qe 1/1"
(bootloader) frp-state: no protection (0)
(bootloader) ro.carrier: tmo
(bootloader) current-slot: _a
(bootloader) running-bl-slot: _a/_a
(bootloader) running-boot-lun: 2
(bootloader) slot-suffixes: _a,_b
(bootloader) slot-count: 2
(bootloader) slot-successful:_a: yes
(bootloader) slot-successful:_b: no
(bootloader) slot-unbootable:_a: no
(bootloader) slot-unbootable:_b: no
(bootloader) slot-retry-count:_a: 7
(bootloader) slot-retry-count:_b: 0
What -05 firmware did you flash?
41rw4lk said:
What -05 firmware did you flash?
Click to expand...
Click to collapse
I don't even know anymore, it was on a computer that I had to wipe and install windows over in order to try everything I did. The clue in my other computer, which is probably accurate, is NASH_TMO_C_OCXS7.109-51-14-7_subsidy-TMO_RSU_regulatory-default_DEFAULT. I'd be willing to bet that is the firmware that is currently flashed, before it was modified with Magisk v20.4, MindTheGapps-8.1.0-arm-20180808_153837, and either MK100 or MK81 of Mokee. I'm no longer even sure if this firmware is for 05, that's just what the name of some other archive this all got dumped into. It's also the version that the instructions I was following used, before I even knew there were 6 versions.
NASH_TMO_C_OCXS7.109-51-14-7_subsidy-TMO_RSU_regulatory-default_DEFAULT is the last firmware available for TMO, hopefully whatever firmware you've flashed wasn't a pie firmware.
With a locked bootloader you can only flash official signed same version or newer firmware. I would try to flash that again, your goal is to get a booting system that you can enable oem unlocking in. That will give you more flexibility to solve other issues if needed. However if you've flashed a oie firmware you might be out of luck.
41rw4lk said:
NASH_TMO_C_OCXS7.109-51-14-7_subsidy-TMO_RSU_regulatory-default_DEFAULT is the last firmware available for TMO, hopefully whatever firmware you've flashed wasn't a pie firmware.
With a locked bootloader you can only flash official signed same version or newer firmware. I would try to flash that again, your goal is to get a booting system that you can enable oem unlocking in. That will give you more flexibility to solve other issues if needed. However if you've flashed a oie firmware you might be out of luck.
Click to expand...
Click to collapse
Well, I looked up that exact filename and attempted to flash the firmware from it. Am I somehow doing this wrong? (see attached -- fastboot version eac51f2bb6a8-android )
https://postimg dot cc/BPq1sbmS
This matches the firmware from the folder I found everything else in, like magisk and some utilities from the first night of this, so it should be the one that's on there. I don't think I flashed pie firmware, unless I installed a ROM that was Pie I think that I only flashed Oreo stuff. (Were they just unable to think of a desert that starts with Q?)
I'm noticing my build fingerprint and blur version correspond with the firmware OCSX.109-51-7/9, which also tells me this should have worked (that firmware also doesn't work). I lost baseband before this happened though ( that's why I locked it, because I thought that would fix it smh), I don't know what does that besides flashing the wrong firmware or really screwing something else.
urvurm said:
Well, I looked up that exact filename and attempted to flash the firmware from it. Am I somehow doing this wrong? (see attached -- fastboot version eac51f2bb6a8-android )
https://postimg dot cc/BPq1sbmS
This matches the firmware from the folder I found everything else in, like magisk and some utilities from the first night of this, so it should be the one that's on there. I don't think I flashed pie firmware, unless I installed a ROM that was Pie I think that I only flashed Oreo stuff. (Were they just unable to think of a desert that starts with Q?)
I'm noticing my build fingerprint and blur version correspond with the firmware OCSX.109-51-7/9, which also tells me this should have worked (that firmware also doesn't work). I lost baseband before this happened though ( that's why I locked it, because I thought that would fix it smh), I don't know what does that besides flashing the wrong firmware or really screwing something else.
Click to expand...
Click to collapse
I've attached the latest adb/fastboot files and a flashall.bat for TMO. Delete any .bat files in your firmware folder and then extract the attached zip into the same firmware folder. Then try running the flashall and keep track of what flashes and what doesn't. Again the goal is to get a booting system that you can enable oem unlocking on so that you can unlock your bootloader again.
41rw4lk said:
I've attached the latest adb/fastboot files and a flashall.bat for TMO. Delete any .bat files in your firmware folder and then extract the attached zip into the same firmware folder. Then try running the flashall and keep track of what flashes and what doesn't. Again the goal is to get a booting system that you can enable oem unlocking on so that you can unlock your bootloader again.
Click to expand...
Click to collapse
Under way, will update with output from fastboot. Thank you for helping me.
Update, it's acting differently, preliminary results show that it is automatically appending slot names with extra "_". I'm going to edit the bat file and add "--slot all" to the relevant partitions. I am getting flash permission denied for the bootloader though. I want to let it run all the way through with the slot option. Nvm I don't know what "relevant is" Here's the output from the unedited bat so far:
I'm having serious issues with copying from the command line, idk if you've got tricks for that.
Code:
C:\Users\enewt\Downloads\OCXS27.109-15-14-7>fastboot oem fb_mode_set
OKAY [ 0.016s] Finished. Total time: 0.016s C:\Users\enewt\Downloads\OCXS27.109-15-14-7>fastboot getvar max-sparse-size
max-sparse-size: 268435456 Finished. Total time: 0.000s C:\Users\enewt\Downloads\OCXS27.109-15-14-7>fastboot flash gpt gpt.bin
(bootloader) is-logical:gpt: not found
Sending 'gpt' (206 KB) OKAY [ 0.000s]
Writing 'gpt'
(bootloader) Validating 'gpt.default.xml' (bootloader) Committing 'gpt.default.xml'
(bootloader) - flashing 'gpt_main0.bin' to 'partition:0'
(bootloader) - flashing 'gpt_main1.bin' to 'partition:1'
(bootloader) - flashing 'gpt_main2.bin' to 'partition:2'
(bootloader) - flashing 'gpt_main3.bin' to 'partition:3'
(bootloader) - flashing 'gpt_main4.bin' to 'partition:4'
(bootloader) - flashing 'gpt_main5.bin' to 'partition:5' OKAY [ 0.132s] Finished. Total time: 0.138s C:\Users\enewt\Downloads\OCXS27.109-15-14-7>fastboot flash bootloader bootloader.img
(bootloader) is-logical:bootloader: not found
Sending 'bootloader' (9884 KB) OKAY [ 0.316s]
Writing 'bootloader'
(bootloader) Validating 'bootloader.default.xml'
(bootloader) flash permission denied (bootloader) flash permission denied (bootloader) flash permission denied (bootloader) flash permission denied (bootloader) flash permission denied (bootloader) flash permission denied (bootloader) flash permission denied (bootloader) flash permission denied (bootloader) flash permission denied (bootloader) flash permission denied (bootloader) flash permission denied (bootloader) flash permission denied (bootloader) Cancelling 'bootloader.default.xml' FAILED (remote: '') fastboot: error: Command failed C:\Users\enewt\Downloads\OCXS27.109-15-14-7>fastboot flash modem NON-HLOS.bin --slot_all
fastboot: unknown option -- slot_all C:\Users\enewt\Downloads\OCXS27.109-15-14-7>fastboot flash modem NON-HLOS.bin
(bootloader) is-logical:modem__a: not found
Sending 'modem__a' (97459 KB) OKAY [ 2.949s]
Writing 'modem__a'
(bootloader) Invalid partition name modem__a FAILED (remote: '')
fastboot: error: Command failed
Sending 'fsg__a' (5596 KB)
OKAY [ 0.185s]
Writing 'fsg__a'
(bootloader) Invalid partition name fsg__a FAILED (remote: '')
fastboot: error: Command failed C:\Users\enewt\Downloads\OCXS27.109-15-14-7>fastboot erase modemst1
Erasing 'modemst1' (bootloader) Permission denied
FAILED (remote: '') fastboot: error: Command failed C:\Users\enewt\Downloads\OCXS27.109-15-14-7>fastboot erase modemst2
Erasing 'modemst2' (bootloader) Permission denied
FAILED (remote: '') fastboot: error: Command failed C:\Users\enewt\Downloads\OCXS27.109-15-14-7>fastboot flash bluetooth BTFM.bin
(bootloader) is-logical:bluetooth__a: not found
Sending 'bluetooth__a' (4500 KB) OKAY [ 0.122s] Writing 'bluetooth__a' (bootloader) Invalid partition name bluetooth__a FAILED (remote: '')
fastboot: error: Command failed C:\Users\enewt\Downloads\OCXS27.109-15-14-7>fastboot flash dsp adspso.bin
(bootloader) is-logical:dsp__a: not found
Sending 'dsp__a' (16384 KB) OKAY [ 0.488s]
Writing 'dsp__a' (bootloader) Invalid partition name dsp__a
FAILED (remote: '')
fastboot: error: Command failed C:\Users\enewt\Downloads\OCXS27.109-15-14-7>fastboot flash logo logo.bin
(bootloader) is-logical:logo__a: not found
Sending 'logo__a' (3151 KB)
OKAY [ 0.100s]
Writing 'logo__a'
(bootloader) Invalid partition name logo__a
FAILED (remote: '')
fastboot: error: Command failed C:\Users\enewt\Downloads\OCXS27.109-15-14-7>fastboot flash boot boot.img
(bootloader) is-logical:boot__a: not found
Sending 'boot__a' (23361 KB)
OKAY [ 0.717s]
Writing 'boot__a'
(bootloader) Invalid partition name boot__a
FAILED (remote: '')
fastboot: error: Command failed C:\Users\enewt\Downloads\OCXS27.109-15-14-7>fastboot flash system system.img_sparsechunk.0
(bootloader) is-logical:system__a: not found
Sending 'system__a' (516201 KB)
OKAY [ 16.302s]
Writing 'system__a'
(bootloader) Invalid partition name system__a
FAILED (remote: '')
fastboot: error: Command failed C:\Users\enewt\Downloads\OCXS27.109-15-14-7>fastboot flash system system.img_sparsechunk.1
(bootloader) is-logical:system__a: not found
Sending 'system__a' (495129 KB) OKAY [ 15.174s]
Writing 'system__a'
(bootloader) Invalid partition name system__a
FAILED (remote: '')
fastboot: error: Command failed C:\Users\enewt\Downloads\OCXS27.109-15-14-7>fastboot flash system system.img_sparsechunk.2
(bootloader) is-logical:system__a: not found
Sending 'system__a' (519381 KB) OKAY [ 16.144s]
Writing 'system__a'
(bootloader) Invalid partition name system__a
FAILED (remote: '')
fastboot: error: Command failed C:\Users\enewt\Downloads\OCXS27.109-15-14-7>fastboot flash system system.img_sparsechunk.3
(bootloader) is-logical:system__a: not found
Sending 'system__a' (523787 KB) OKAY [ 16.147s]
Writing 'system__a'
(bootloader) Invalid partition name system__a FAILED (remote: '')
fastboot: error: Command failed C:\Users\enewt\Downloads\OCXS27.109-15-14-7>fastboot flash system system.img_sparsechunk.4
(bootloader) is-logical:system__a: not found
Sending 'system__a' (516413 KB) OKAY [ 16.205s]
Writing 'system__a'
(bootloader) Invalid partition name system__a FAILED (remote: '')
fastboot: error: Command failed C:\Users\enewt\Downloads\OCXS27.109-15-14-7>fastboot flash system system.img_sparsechunk.5
(bootloader) is-logical:system__a: not found
Sending 'system__a' (420583 KB) OKAY [ 12.854s]
Writing 'system__a' (bootloader) Invalid partition name system__a
FAILED (remote: '')
fastboot: error: Command failed C:\Users\enewt\Downloads\OCXS27.109-15-14-7>fastboot flash system_b system_b.img_sparsechunk.0
(bootloader) is-logical:system_b: not found
Sending 'system_b' (515183 KB) OKAY [ 15.725s]
Writing 'system_b' (bootloader) flash permission denied
FAILED (remote: '')
fastboot: error: Command failed C:\Users\enewt\Downloads\OCXS27.109-15-14-7>fastboot flash system_b system_b.img_sparsechunk.1
(bootloader) is-logical:system_b: not found
Sending 'system_b' (307220 KB) OKAY [ 9.363s]
Writing 'system_b' (bootloader) flash permission denied
FAILED (remote: '')
fastboot: error: Command failed C:\Users\enewt\Downloads\OCXS27.109-15-14-7>fastboot flash oem oem.img
(bootloader) is-logical:oem__a: not found
Try copying the the commands in the flashall one at a time and adjust accordingly.
For example say you post the command fastboot flash logo logo.bin and it returns fastboot: error: Command failed logo__a: not found
You know it's trying to flash the _a slot, which is fine so tell it to do so manually fastboot flash logo_a logo.bin
With a locked bootloader you might get some permissions denied, especially since you flashed the -05 firmware, which might have mismatched a few things. Keep going to the end of your flashall. You need a bootable os so you can get the bootloader unlocked and hopefully overwrite more wrongs and get back to good.
41rw4lk said:
Try copying the the commands in the flashall one at a time and adjust accordingly.
For example say you post the command fastboot flash logo logo.bin and it returns fastboot: error: Command failed logo__a: not found
You know it's trying to flash the _a slot, which is fine so tell it to do so manually fastboot flash logo_a logo.bin
With a locked bootloader you might get some permissions denied, especially since you flashed the -05 firmware, which might have mismatched a few things. Keep going to the end of your flashall. You need a bootable os so you can get the bootloader unlocked and hopefully overwrite more wrongs and get back to good.
Click to expand...
Click to collapse
Well, permission was denied for all slots except for gpt.bin (consistently the only one to work), which I attempted to analyze to better understand the partion table but I think the tool I used was not designed for moto z. Anyway, this is just how it's been. From here, all boot options stop me at the "your software is corrupt you evil hacker anathema to corporate purity"
While I haven't tried it after this round of 100% failed commands, I have used fastboot boot boot.img and been able to enter a dysfunctional wreck of an OS that can almost but not quite get past pixel setup and allow me to edit prefs. Is there maybe a way to bypass setup and edit settings from here? ( It's too broken to launch adb, but it does persist to some degree, I was able to set a pin that remains. It's just infinitely crashing and never makes it past the checkpoint where I disagree to all of tmobiles usage stats agreements,
urvurm said:
Well, permission was denied for all slots except for gpt.bin (consistently the only one to work), which I attempted to analyze to better understand the partion table but I think the tool I used was not designed for moto z. Anyway, this is just how it's been. From here, all boot options stop me at the "your software is corrupt you evil hacker anathema to corporate purity"
Click to expand...
Click to collapse
I assume you mean the lenovo rescue and smart assistant tool. With a mismatch system it might not recognize the phone (which is moto z 2nd gen for the record).
I'll attach a both slot flashall, maybe the other slot can be sorted a little better. For what it is worth, you might boot to recovery and do a factory reset 1st. Then try the other flashall. You might just be out of luck, but it's worth trying a few things before you call it. Same deal with this flashall too, if you need to manually go line by line do it. Also, when it's all said and done, try another factory reset from recovery if needed.
If you see the no command dead android in recovery, just hold pwr and press vol up to get to the actual recovery.
I just seen your edit, no way to get past setup that I know of. Another user tried forever to find away, but I don't think they did. Also, I wouldn't set any screen security until you're in a clean state. It will only hinder what you're trying to do.
41rw4lk said:
I assume you mean the lenovo rescue and smart assistant tool. With a mismatch system it might not recognize the phone (which is moto z 2nd gen for the record)
Click to expand...
Click to collapse
I was actually referring to this: https://androidforums.com/threads/guide-how-to-create-partition-xml-gpt.1125433/
To see if I could get a better Idea of the partition names, since even when I set --slot all, I get the (permission denied) instead of (command fail) or whatever.
And you're right, LMSA wasn't able to do recognize it and I think it's because of mismatched firmware. I'm glad someone else has seen this broken boot ing. thing before. I know setting a pin was a bad idea, I just felt like I was running out of options.
I'll try this modified flashall you sent me.
41rw4lk said:
For what it is worth, you might boot to recovery and do a factory reset 1st. Then try the other flashall. You might just be out of luck, but it's worth trying a few things before you call it. Same deal with this flashall too, if you need to manually go line by line do it. Also, when it's all said and done, try another factory reset from recovery if needed.
Click to expand...
Click to collapse
No dice.. failed uniformly as flash permission denied or permission denied for the erase commands. Tried line by line and got the same result. Only noteworthy things I saw anyway:
Code:
#after any flash attempt, with both invalid and valid partition names, I get this:
(bootloader) is-logical:<Insert whatever partition name I just attempted _a, _b either way>: not found
#it always says flash permission denied, unless I try an invalid partion name, like radio
(bootloader) is-logical:radio: not found Sending 'radio' (97459 KB) OKAY [ 3.039s] Writing 'radio' (bootloader) Invalid partition name radio FAILED (remote: '') fastboot: error: Command failed
C:\Users\enewt\Downloads\OCXS27.109-15-14-7>fastboot --set-active=other
Setting current slot to '`' FAILED (remote: '')
If you see the no command dead android in recovery, just hold pwr and press vol up to get to the actual recovery.
Click to expand...
Click to collapse
I tried booting to recovery from bootloader, holding power+ vol up, and also just booting with power +vol up. I always get to the "corrupted, can't trust" screen. I think it's trying to boot into TWRP but isn't allowed. It's weird though because I remember trying this before and it just restarting the bootloader, but it might have been a dead battery.
Related
[HELP] AUS/Optus Model - Deleted OS
This is probably the dumbest thing I have to date :C At the start of last year I rooted my device and unlocked it, fast forward to the start of this week I tried updating my device but it kept on launching TWRP, so I decided to factory reset it. However I was a big spud and used advanced wipe - and now the phone will boot straight to the bootloader. Before I post anything else here is the getvar from download mode. Code: (bootloader) kernel: lk (bootloader) product: htc_himauhl (bootloader) version: 1.0 (bootloader) version-main: 2.9.710.2 (bootloader) boot-mode: download (bootloader) version-baseband: 01.04_U11440601_71.02.50709G_F (bootloader) version-bootloader: 1.0.0.0000 (bootloader) mid: 0PJA10000 (bootloader) cid: OPTUS001 The device is currently in s-on, and I can't remember if it was ever in s-off because it was a long time ago when I rooted it. I have tried flashing a custom rom with no success, and just recently I have downloaded and tried to flash "0PJAIMG_HIMA_UHL_L50_SENSE70_hTC_Asia_AUS_1.32.710.16_Radio_01.01_U11440261_56.02.50306G_2_F_release_427214_signed.zip" This is the error I receive while trying to flash the device in fastboot. Code: C:\adb>fastboot oem rebootRUU ... OKAY [ 0.017s] finished. total time: 0.018s C:\adb>fastboot flash zip 0PJAIMG.zip target reported max download size of 800000000 bytes Invalid sparse file format at header magi error: write_sparse_skip_chunk: don't care size 2128996130 is not a multiple of the block size 4096 sending sparse 'zip' (0 KB)... error: write_sparse_skip_chunk: don't care size 2128996130 is not a multiple of the block size 4096 error: write_sparse_skip_chunk: don't care size 2128996130 is not a multiple of the block size 4096 OKAY [ 1.013s] writing 'zip'... (bootloader) HOSD CL#573756 (bootloader) ERR lzipv1_init : Cannot read header len bytes (bootloader) ERR lzipv2_init : Cannot open file /dev/fastboot_download_n (bootloader) A2AxZ FAILED (remote: 99: SD_UNKNOWN_FAIL to flash via downloadzip) finished. total time: 2.048s I don't have any backups of any sort - basically I just want to be able to get this phone running back on stock and leave it at that. Does anyone have any ideas of how I can fix this? My phone has been broken for 3 days and I've wasted a lot of time downloading roms that won't flash (takes a while to download on my crappy ADSL connection). I should also note I do not have an external SD card, hoping to do it without buying one. Thanks heaps.
Please read the ReadMe thread. Its RUU section explains why you can't flash the RUU that you mentioned in your OP and why flashing M9 RUUs in general fails if you use fastboot. After you downloaded the correct files you can try to flash a RUU with the modified fastboot instead of using an SD card. Troubleshooting tips can be found in the FAQ of the same thread. Be aware, that using an SD card is the recommended method since many users aren't able to set up a fastboot environment correctly and using an SD card is less time-consuming than trying to find the user error that prevents fastboot from working correctly.
Pixel XL bricked, bootloader locked and recovery doesn't work.
Does anyone can help me? My Pixel XL brick more than a week ago, and I couldn't. I was installing the 8.0.0 official image from the bootloader with fastboot (a "clean install"), apparently there was an error installing the recovery and I didn't realize, so I lock the recovery (with fastboot oem lock and Up Volume key). After that, I restarted the phone and now it doesn't start (it shows only a "Google" splash and it restarts again). I can't use the recovery mode (to use adb sideload command), try enter to the recovery makes the phone start "bootlooping" too. I seen another thread explaining my problem, but it has almost a year without activiy (I asked on it to the user if he could solve that this problem but it seems like he doesn't use xda anymore): https://forum.xda-developers.com/pixel-xl/help/pixel-xl-soft-bricked-unlock-bootloader-t3540772 I live in Uruguay, so I can't RMA. Summary: - My phone is bricked. - I can enter to bootloader, but it's locked. - I can't enter to recovery mode. - I can't RMA. Useful logs: fastboot getvar all: Code: (bootloader) version:0.5 (bootloader) hw-revision:PVT (bootloader) mid:G-2PW2100 (bootloader) version-main:0.12.999.1 (bootloader) imei:352693081633543 (bootloader) ramdump-mode:false (bootloader) boot-mode:FASTBOOT (bootloader) has-slot:radio:yes (bootloader) has-slot:bootloader:yes (bootloader) has-slot:reserve5:no (bootloader) has-slot:devinfo:no (bootloader) has-slot:fsg:no (bootloader) has-slot:mfg:no (bootloader) has-slot:board_info:no (bootloader) has-slot:reserve4:no (bootloader) has-slot:metadata:no (bootloader) has-slot:pg2fs:no (bootloader) has-slot:pg1fs:no (bootloader) has-slot:ramdump:no (bootloader) has-slot:frp:no (bootloader) has-slot:reserve3:no (bootloader) has-slot:cdt:no (bootloader) has-slot:ddr:no (bootloader) has-slot:modemst2:no (bootloader) has-slot:modemst1:no (bootloader) has-slot:fsc:no (bootloader) has-slot:dip:no (bootloader) has-slot:dpo:no (bootloader) has-slot:devinfobak:no (bootloader) has-slot:sec:no (bootloader) has-slot:persist:no (bootloader) has-slot:ssd:no (bootloader) has-slot:misc:no (bootloader) has-slot:xbl:yes (bootloader) has-slot:reserve0:no (bootloader) has-slot:userdata:no (bootloader) has-slot:system:yes (bootloader) has-slot:vendor:yes (bootloader) has-slot:apdp:yes (bootloader) has-slot:msadp:yes (bootloader) has-slot:modem:yes (bootloader) has-slot:devcfg:yes (bootloader) has-slot:hosd:yes (bootloader) has-slot:boot:yes (bootloader) has-slot:aboot:yes (bootloader) has-slot:cmnlib64:yes (bootloader) has-slot:cmnlib32:yes (bootloader) has-slot:hyp:yes (bootloader) has-slot:pmic:yes (bootloader) has-slot:rpm:yes (bootloader) has-slot:tz:yes (bootloader) has-slot:keymaster:yes (bootloader) has-slot:bootlocker:yes (bootloader) slot-count:2 (bootloader) current-slot:a (bootloader) slot-retry-count:b:0 (bootloader) slot-unbootable:b:no (bootloader) slot-successful:b:no (bootloader) slot-retry-count:a:2 (bootloader) slot-unbootable:a:no (bootloader) slot-successful:a:yes (bootloader) battery-soc-ok:yes (bootloader) battery-voltage:4240000 (bootloader) variant:US (bootloader) secure:yes (bootloader) unlocked:no (bootloader) version-baseband:8996-012901-1702171013 (bootloader) version-bootloader:8996-012001-1704121145 (bootloader) off-mode-charge:1 (bootloader) charger-screen-enabled:1 (bootloader) max-download-size: 0x20000000 (bootloader) partition-type:userdata:ext4 (bootloader) partition-size:userdata: 0x635400000 (bootloader) partition-type:system_b:ext4 (bootloader) partition-size:system_b: 0x80000000 (bootloader) partition-type:system_a:ext4 (bootloader) partition-size:system_a: 0x80000000 (bootloader) partition-type:vendor_b:ext4 (bootloader) partition-size:vendor_b: 0x12c00000 (bootloader) partition-type:vendor_a:ext4 (bootloader) partition-size:vendor_a: 0x12c00000 (bootloader) partition-type:boot_b:raw (bootloader) partition-size:boot_b: 0x2000000 (bootloader) partition-type:boot_a:raw (bootloader) partition-size:boot_a: 0x2000000 (bootloader) serialno:HT7370201155 (bootloader) kernel:lk (bootloader) product:marlin all: finished. total time: 2.243s ./flash-all.sh (8.0.0-stock-opr3.170623.007): Code: target reported max download size of 536870912 bytes sending 'bootloader_a' (32268 KB)... OKAY [ 1.076s] writing 'bootloader_a'... (bootloader) Command is not supported. (bootloader) Please unlock device to enable this command. FAILED (remote failure) finished. total time: 1.175s rebooting into bootloader... OKAY [ 0.046s] finished. total time: 0.275s target reported max download size of 536870912 bytes sending 'radio_a' (57272 KB)... OKAY [ 1.952s] writing 'radio_a'... (bootloader) Command is not supported. (bootloader) Please unlock device to enable this command. FAILED (remote failure) finished. total time: 2.050s rebooting into bootloader... OKAY [ 0.050s] finished. total time: 0.150s target reported max download size of 536870912 bytes archive does not contain 'boot.sig' archive does not contain 'boot_other.img' archive does not contain 'recovery.img' archive does not contain 'system.sig' W/ziparchive(10452): Zip: unable to allocate 818872552 bytes at offset 0 : No space left on device failed to extract 'system_other.img': I/O Error W/ziparchive(10452): Zip: unable to allocate 263934088 bytes at offset 0 : No space left on device failed to extract 'vendor.img': I/O Error archive does not contain 'vendor_other.img' wiping userdata... Creating filesystem with parameters: Size: 26663190528 Block size: 4096 Blocks per group: 32768 Inodes per group: 8192 Inode size: 256 Journal blocks: 32768 Label: Blocks: 6509568 Block groups: 199 Reserved block group size: 1024 Created filesystem with 11/1630208 inodes and 146354/6509568 blocks error: file_write: write: No space left on device -------------------------------------------- Bootloader Version...: 8996-012001-1704121145 Baseband Version.....: 8996-012901-1702171013 Serial Number........: HT7370201155 -------------------------------------------- checking product... OKAY [ 0.050s] checking version-bootloader... FAILED Device version-bootloader is '8996-012001-1704121145'. Update requires '8996-012001-1706221457'. finished. total time: 0.300s ./flash-all.sh (7.1.2-stock-njh47d): Code: target reported max download size of 536870912 bytes sending 'bootloader_a' (32380 KB)... OKAY [ 1.088s] writing 'bootloader_a'... (bootloader) Command is not supported. (bootloader) Please unlock device to enable this command. FAILED (remote failure) finished. total time: 1.187s rebooting into bootloader... OKAY [ 0.046s] finished. total time: 0.247s target reported max download size of 536870912 bytes sending 'radio_a' (57240 KB)... OKAY [ 1.924s] writing 'radio_a'... (bootloader) Command is not supported. (bootloader) Please unlock device to enable this command. FAILED (remote failure) finished. total time: 2.022s rebooting into bootloader... OKAY [ 0.050s] finished. total time: 0.250s target reported max download size of 536870912 bytes archive does not contain 'boot.sig' archive does not contain 'boot_other.img' archive does not contain 'recovery.img' archive does not contain 'system.sig' W/ziparchive(10714): Zip: unable to allocate 1721085316 bytes at offset 0 : No space left on device failed to extract 'system_other.img': I/O Error archive does not contain 'vendor.sig' archive does not contain 'vendor_other.img' wiping userdata... Creating filesystem with parameters: Size: 26663190528 Block size: 4096 Blocks per group: 32768 Inodes per group: 8192 Inode size: 256 Journal blocks: 32768 Label: Blocks: 6509568 Block groups: 199 Reserved block group size: 1024 Created filesystem with 11/1630208 inodes and 146354/6509568 blocks -------------------------------------------- Bootloader Version...: 8996-012001-1704121145 Baseband Version.....: 8996-012901-1702171013 Serial Number........: HT7370201155 -------------------------------------------- checking product... OKAY [ 0.050s] checking version-bootloader... OKAY [ 0.050s] checking version-baseband... OKAY [ 0.050s] sending 'boot_a' (26001 KB)... OKAY [ 0.951s] writing 'boot_a'... (bootloader) Command is not supported. (bootloader) Please unlock device to enable this command. FAILED (remote failure) finished. total time: 1.401s
zades9 said: Does anyone can help me? My Pixel XL brick more than a week ago, and I couldn't. I was installing the 8.0.0 official image from the bootloader with fastboot (a "clean install"), apparently there was an error installing the recovery and I didn't realize, so I lock the recovery (with fastboot oem lock and Up Volume key). After that, I restarted the phone and now it doesn't start (it shows only a "Google" splash and it restarts again). I can't use the recovery mode (to use adb sideload command), try enter to the recovery makes the phone start "bootlooping" too. I seen another thread explaining my problem, but it has almost a year without activiy (I asked on it to the user if he could solve that this problem but it seems like he doesn't use xda anymore): https://forum.xda-developers.com/pixel-xl/help/pixel-xl-soft-bricked-unlock-bootloader-t3540772 I live in Uruguay, so I can't RMA. Summary: - My phone is bricked. - I can enter to bootloader, but it's locked. - I can't enter to recovery mode. - I can't RMA. Click to expand... Click to collapse I assume that you have tried fastboot boot with the correct twrp image?
I understand you locked the bootloader, however, maybe the stock images didn't flash correctly to reset the "allow oem unlocking" in the developer options.. If that's the case, try unlocking the bootloader again with "fastboot flashing unlock".
mikefnz said: I assume that you have tried fastboot boot with the correct twrp image? Click to expand... Click to collapse I get this log: Code: [cristian: PixelXL]$ fastboot boot twrp-3.0.2-0-alpha2-fastboot-marlin.img downloading 'boot.img'... OKAY [ 0.901s] booting... (bootloader) Command is not supported. (bootloader) Please unlock device to enable this command. FAILED (remote failure) finished. total time: 1.001s
Pain-N-Panic said: I understand you locked the bootloader, however, maybe the stock images didn't flash correctly to reset the "allow oem unlocking" in the developer options.. If that's the case, try unlocking the bootloader again with "fastboot flashing unlock". Click to expand... Click to collapse Code: [cristian: PixelXL]$ fastboot oem unlock ... FAILED (remote: oem unlock is not allowed) finished. total time: 0.043s [cristian: PixelXL]$ fastboot flashing unlock ... FAILED (remote: oem unlock is not allowed) finished. total time: 0.044s
I have no idea man... hopefully someone a lot more experienced than me comes around with a valid solution.
zades9 said: Code: [cristian: PixelXL]$ fastboot oem unlock ... FAILED (remote: oem unlock is not allowed) finished. total time: 0.043s [cristian: PixelXL]$ fastboot flashing unlock ... FAILED (remote: oem unlock is not allowed) finished. total time: 0.044s Click to expand... Click to collapse I'm no expert but have you tried the Skipsoft Toolkit? https://forum.xda-developers.com/pixel-xl/development/tool-skipsoft-android-toolkit-google-t3482767 And checked this guide? https://forum.xda-developers.com/pixel-xl/how-to/info-how-restored-to-stock-soft-t3494478/page20
mikefnz said: I'm no expert but have you tried the Skipsoft Toolkit? https://forum.xda-developers.com/pixel-xl/development/tool-skipsoft-android-toolkit-google-t3482767 And checked this guide? https://forum.xda-developers.com/pixel-xl/how-to/info-how-restored-to-stock-soft-t3494478/page20 Click to expand... Click to collapse I can't enable Bootloader Unlocking from the developer settings because the device is bricked.
@zades9 I have an idea. Try downloading an OTA image to 8.0 and flashing that from stock recovery if you can access it (twrp might be cool too idk). If it will not let you flash an ota because you're already on 8.... 8.1 is coming out soon lol Is your bootloader messed up somehow? Fastboot flashing unlock_critical unlocks the bootloader but I don't know much about it. Let me rephrase it allows the bootloader to be flashed over.
Yea I'd try:fastboot flashing unlock_critical Is it possible to switch to the bootloader_b slot and reboot-bootloader... possibly flash the b slot?
comat0se said: Yea I'd try:fastboot flashing unlock_critical Is it possible to switch to the bootloader_b slot and reboot-bootloader... possibly flash the b slot? Click to expand... Click to collapse [cristian: ~]$ fastboot flashing unlock_critical ... FAILED (remote: oem unlock is not allowed) finished. total time: 0.044s
tdct12 said: @zades9 I have an idea. Try downloading an OTA image to 8.0 and flashing that from stock recovery if you can access it (twrp might be cool too idk). If it will not let you flash an ota because you're already on 8.... 8.1 is coming out soon lol Is your bootloader messed up somehow? Fastboot flashing unlock_critical unlocks the bootloader but I don't know much about it. Let me rephrase it allows the bootloader to be flashed over. Click to expand... Click to collapse For what I know, you can't flash anything if your bootloader is locked. Code: [cristian: ~]$ fastboot flashing unlock_critical ... FAILED (remote: oem unlock is not allowed) finished. total time: 0.044s
I know about 6 months ago in the Nexus 6p forum, someone created a zip that could be flashed in recovery to toggle bootloader unlock in developer settings. It might be worth looking for to see if there's some sort of adb shell script that you could possibly use to toggle that switch. So you didn't boot after flashing factory image before locking? Also be sure to be using the most up to date adb and fastboot tools as that can cause issue too. IDK, I wish you luck!
Bryanx86 said: I know about 6 months ago in the Nexus 6p forum, someone created a zip that could be flashed in recovery to toggle bootloader unlock in developer settings. It might be worth looking for to see if there's some sort of adb shell script that you could possibly use to toggle that switch. So you didn't boot after flashing factory image before locking? Also be sure to be using the most up to date adb and fastboot tools as that can cause issue too. IDK, I wish you luck! Click to expand... Click to collapse If I could flash something in recovery mode I could flash the stock rom with "adb sideload file.zip", so I would not need unlock bootoader. And yeah, I didn't boot after locking oem again :/
zades9 said: For what I know, you can't flash anything if your bootloader is locked. Code: [cristian: ~]$ fastboot flashing unlock_critical ... FAILED (remote: oem unlock is not allowed) finished. total time: 0.044s Click to expand... Click to collapse Actually that's not true. You can flash factory ota updates on a locked bootlader from stock recovery, idk about twrp though.
zades9 said: If I could flash something in recovery mode I could flash the stock rom with "adb sideload file.zip", so I would not need unlock bootoader. And yeah, I didn't boot after locking oem again :/ Click to expand... Click to collapse I wasn't referring to flashing that zip file, but looking inside to see if it's an adb shell script, you have a booting phone with a working bootloader, the recovery is compromised. There has to be a way to get your phone fixed. Only when it's totally dead do you give up hope
Well, while we are grasping at straws, make sure your fastboot is the very latest version. The version I use is marked as ~$ fastboot --version fastboot version -4022467 I would also give the November image a try.
Crap I bricked mine too! Was on rooted Stock with twrp. Did factory reset (to unroot), then relock bootloader (all done with Skipsoft Toolkit). Thought I'd be in the clear, but now it's just bootlooping a half second Google logo and then black. I can get into the bootloader but nothing else works, not recovery, nothing. Can't flash anything since bootloader is locked now. Tried adb commands like fastboot continue but nothing works... Any updates or ideas on this!?? Device is bricked! I bought mine new on Craigslist so may have some trouble with RMA.... Yikes!
Please let this be a lesson to people to stop locking their bootloader's, or know what the heck they are doing before they do. I'm tired of reading about this across all forums. Whoever is explaining the steps to unlock the bootloader, need to give explicit knowledge on what to do and not do. I honestly wish I could be of more help, but it's a pain to get sorted on devices with regular partitions, so on this device I have no clue. It would be great if you could somehow force it to boot using the alternate slot To OP, it looks like you're using slot A. Can you try switching to slot B and thing to boot? fastboot --set-active=_b
dictionary said: Please let this be a lesson to people to stick locking their bootloader's, or know what the heck they are doing. I'm tired of reading about this across all forums. Whoever is explaining the steps to unlock the bootloader, need to give explicit knowledge on what to do and not do. I honestly wish I could be of more help, but it's a pain to get sorted on devices with regular partitions, so on this device I have no clue. It would be great if you could somehow force it to boot using the alternate slot To OP, it looks like you're using slot A. Can you try switching to slot B and thing to boot? fastboot --set-active=_b Click to expand... Click to collapse Code: C:\Users\cristian>fastboot --set-active=_b Setting current slot to 'b'... (bootloader) Command is not supported. (bootloader) Please unlock device to enable this command. FAILED (remote failure) finished. total time: 0.076s C:\Users\cristian>fastboot --set-active=b Setting current slot to 'b'... (bootloader) Command is not supported. (bootloader) Please unlock device to enable this command. FAILED (remote failure) finished. total time: 0.292s I posted my problem on the Pixel User Community, but that thread is dead: https://groups.google.com/a/googlep...forums.com?utm_medium=email&utm_source=footer
Downgrade from AOSiP 9 to Stock Rom
Hello, I'm using the AOSiP 9 ROM on my moto z play, and i want to go back to stock rom. I'm tried this tutorial but when i do the command: Code: .\fastboot.exe flash partition gpt.bin i got the error: Code: (bootloader) has-slot:partition: not found (bootloader) is-logical:partition: not found Sending 'partition' (45 KB) OKAY [ 0.170s] Writing 'partition' (bootloader) Validating 'gpt.default.xml' (bootloader) Security version downgrade (bootloader) Image primary_gpt failed validation (bootloader) Preflash validation failed (bootloader) Cancelling 'gpt.default.xml' FAILED (remote: '') fastboot: error: Command failed My MZP model is XT-1635-02. Somebody can help-me to go back to stock MZP rom? Thanks! :good:
Download and extract this firmware and then follow the flashing order from this GUIDE I would recommend to use minimal adb and fastboot to execute those commands, and exactly how the guide describes
It worked! I will try to use this article to block the bootloader again. Thanks for the help!
(SOLVED)Need somebody really expert on unlock bootloader on this phone, please halp
So i brough this weird phone, and i guess i will need somebody really expert on this unlock bootloader thing this time. 0 - Locked bootloader, but in motorola software says it have root 1 - I can boot to system normaly, use sim, imeis are all ok (but there is no gapps and no way to flash it) 2 - LineageOS Pie rom 3 - i can acess fastboot (that says is locked) 4- i cannot acess recovery (when select this option, returns to fastboot) 5 - there is no "oem unlock" option in "developer options" 6 - my phone is elegible to unlock, so i already got the motorola code through the site (to use with "fastboot oem unlock CODE", but when i do the command line, says that i need to turn on the oem unlock option that doesnt exist in "developer options" 7 - If i try to boot any twrp img in fastboot mode (to flash twrp zip), the phone reboot to fastboot again (as i said, i have no acess to recovery) 8- If i update the magisk (comes with lineageOS), the system wont boot anymore, and says its corrupt, shows a recovery red window but only with "factory format" option (and if i do, the phone just format as it was in the beginning) 9 - if i try to flash anything in fastboot, i will fail coz of couse, its locked. 10- i have the box, original items, papers and documents (but its out of warranty). 11 - tried Lenovo Moto Smart Assistant, but when i put my model and awaits to fastboot, says that cannot do nothing. I just want to use stock oreo, nothing more, is too much to ask? :crying: :crying: :crying: Please dont ask me what the previous owner did to this phone, i dont know(he neighter, said only that after trying to install custom rom, bricked the phone, but somehow could install this lineageOS :crying: :crying: Any help to this poor soul? Thanks already :crying: :crying:
What is the model, what does it say by the charger port? XT1789-?? In fastboot issue 'fastboot getvar all' w/o quotes and post that info here -minus your imei# that will give an idea of what firmware you need to flash to get back to stock and unlock.
41rw4lk said: What is the model, what does it say by the charger port? XT1789-?? In fastboot issue 'fastboot getvar all' w/o quotes and post that info here -minus your imei# that will give an idea of what firmware you need to flash to get back to stock and unlock. Click to expand... Click to collapse Thanks thanks for comment <3 its a XT1789-05, and the info you asked: (bootloader) kernel: uefi (bootloader) version-bootloader: MBM-3.0-nash_retail-43c7c77-190608 (bootloader) product: nash (bootloader) board: nash (bootloader) secure: yes (bootloader) hwrev: PVT (bootloader) radio: ROW (bootloader) storage-type: UFS (bootloader) emmc: N/A (bootloader) ufs: 64GB SAMSUNG KLUCG4J1ED-B0C1 FV=0200 (bootloader) ram: 6GB SAMSUNG LP4x DIE=12Gb M5=01 M6=06 M7=00 M8=0E (bootloader) cpu: MSM8998 2.1 (4) (bootloader) serialno: 0049486108 (bootloader) cid: 0x0032 (bootloader) channelid: 0x19 (bootloader) uid: 5291F1FC (bootloader) securestate: flashing_locked (bootloader) verity-state: disabled (0) (bootloader) iswarrantyvoid: yes (bootloader) max-download-size: 536870912 (bootloader) reason: Volume down key pressed (bootloader) imei: xxxxxxxxxxxxxxxx (bootloader) meid: (bootloader) date: 03-22-2019 (bootloader) sku: XT1789-05 (bootloader) carrier_sku: (bootloader) battid: (bootloader) battery-voltage: 4051 (bootloader) iccid: (bootloader) cust_md5: (bootloader) max-sparse-size: 268435456 (bootloader) ro.build.fingerprint[0]: motorola/nash/nash:9/PPX29.159-19/ (bootloader) ro.build.fingerprint[1]: 02844:user/release-keys (bootloader) poweroffalarm: 0 (bootloader) ro.build.version.full[0]: Blur_Version.29.11.19.nash.retail (bootloader) ro.build.version.full[1]: .en.US (bootloader) ro.build.version.qcom: LA.UM.7.2.r1-06500-sdm660.0 (bootloader) version-baseband: M8998_50.71.02.95R NRD (bootloader) kernel.version[0]: Linux version 4.4.153-perf-gf9e16d5 (hud (bootloader) kernel.version[1]: [email protected]) (gcc version 4.9.x 2015 (bootloader) kernel.version[2]: 0123 (prerelease) (GCC) ) #1 SMP PREEMPT (bootloader) kernel.version[3]: Sat Jun 8 12:34:38 CDT 2019 (bootloader) git:abl: MBM-3.0-nash_retail-43c7c77-190608 (bootloader) git:xbl: MBM-3.0-nash_retail-4fc2afc-190608 (bootloader) gitmic: MBM-3.0-nash_retail-4fc2afc-190608 (bootloader) git:rpm: MBM-3.0-nash_retail-404f7ba-190608 (bootloader) git:tz: MBM-3.0-nash_retail-3537781-190608 (bootloader) git:hyp: MBM-3.0-nash_retail-3537781-190608 (bootloader) git:devcfg: MBM-3.0-nash_retail-3537781-190608 (bootloader) git:cmnlib: MBM-3.0-nash_retail-3537781-190608 (bootloader) git:cmnlib64: MBM-3.0-nash_retail-3537781-190608 (bootloader) git:keymaster: MBM-3.0-nash_retail-3537781-190608 (bootloader) git:storsec: MBM-3.0-nash_retail-3537781-190608 (bootloader) gitrov: MBM-3.0-nash_retail-3537781-190608 (bootloader) frp-state: no protection (0) (bootloader) ro.carrier: retbr (bootloader) current-slot: a (bootloader) running-bl-slot: _a/_a (bootloader) running-boot-lun: 2 (bootloader) slot-count: 2 (bootloader) slot-successful:_a: yes (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.453s
From what I see what I've been able to confirm, it looks like your phone was updated to pie at some point. So going back to oreo isn't an option since the modem won't jive. Everything seems to be retail Brazil firmware, so you need the retbr 9.0 firmware. The only thing concerning is the previous owner and whatever they did, especially since it resulted in a brick and they jimmied up this concoction. Just to verify, when you boot to os you do have a signal and all that correct? If that is correct then retbr modem works for you and you should be able to flash stock pie and everything should work. Then you'll be able to unlock and all that. So if your signal is there then jump to this forum and follow the directions to flash retbr pie. Feel free to ask questions about flashing there. They seem to have retbr sorted and working there. https://forum.xda-developers.com/z2-force/how-to/update-android-pie-t3893509/page72
41rw4lk said: From what I see what I've been able to confirm, it looks like your phone was updated to pie at some point. So going back to oreo isn't an option since the modem won't jive. Everything seems to be retail Brazil firmware, so you need the retbr 9.0 firmware. The only thing concerning is the previous owner and whatever they did, especially since it resulted in a brick and they jimmied up this concoction. Just to verify, when you boot to os you do have a signal and all that correct? If that is correct then retbr modem works for you and you should be able to flash stock pie and everything should work. Then you'll be able to unlock and all that. So if your signal is there then jump to this forum and follow the directions to flash retbr pie. Feel free to ask questions about flashing there. They seem to have retbr sorted and working there. https://forum.xda-developers.com/z2-force/how-to/update-android-pie-t3893509/page72 Click to expand... Click to collapse Yes all works fine, sim cards, wifi, etc. But i already tried to flash stock oreo but the phone dont even allow any file flash because of locked bootloader. The pie files will bypass that? Anyways thanks thanks again to your answer, i will try what you said and follow the link (since i fix my notebook psu that screew up just now )
41rw4lk said: From what I see what I've been able to confirm, it looks like your phone was updated to pie at some point. So going back to oreo isn't an option since the modem won't jive. Everything seems to be retail Brazil firmware, so you need the retbr 9.0 firmware. The only thing concerning is the previous owner and whatever they did, especially since it resulted in a brick and they jimmied up this concoction. Just to verify, when you boot to os you do have a signal and all that correct? If that is correct then retbr modem works for you and you should be able to flash stock pie and everything should work. Then you'll be able to unlock and all that. So if your signal is there then jump to this forum and follow the directions to flash retbr pie. Feel free to ask questions about flashing there. They seem to have retbr sorted and working there. https://forum.xda-developers.com/z2-force/how-to/update-android-pie-t3893509/page72 Click to expand... Click to collapse not worked :crying: did all he said : Unzip the 2 files (flashall ... and firm ...) and place them in a folder Click on "Preparation.bat", you must generate a "flash.bat file", double click with the phone in download mode It's all, really clean installation It was what I did, I am not responsible for damage to your equipment but nothing can be flashed because of bootloader locked: C:\Users\Usuario\Desktop\Nova pasta\NASH_RETAIL_9.0_PPX29.159-19_subsidy-DEFAULT _regulatory-DEFAULT_CFC.xml>echo off max-sparse-size: 268435456 finished. total time: 0.003s ... OKAY [ 0.009s] finished. total time: 0.010s target reported max download size of 536870912 bytes sending 'partition' (206 KB)... OKAY [ 0.050s] writing 'partition'... (bootloader) Validating 'gpt.default.xml' (bootloader) Committing 'gpt.default.xml' (bootloader) - flashing 'gpt_main0.bin' to 'partition:0' (bootloader) - flashing 'gpt_main1.bin' to 'partition:1' (bootloader) - flashing 'gpt_main2.bin' to 'partition:2' (bootloader) - flashing 'gpt_main3.bin' to 'partition:3' (bootloader) - flashing 'gpt_main4.bin' to 'partition:4' (bootloader) - flashing 'gpt_main5.bin' to 'partition:5' OKAY [ 0.229s] finished. total time: 0.281s target reported max download size of 536870912 bytes sending 'bootloader' (9884 KB)... OKAY [ 0.384s] writing 'bootloader'... (bootloader) Validating 'bootloader.default.xml' (bootloader) flash permission denied (bootloader) flash permission denied (bootloader) flash permission denied (bootloader) flash permission denied (bootloader) flash permission denied (bootloader) flash permission denied (bootloader) flash permission denied (bootloader) flash permission denied (bootloader) flash permission denied (bootloader) flash permission denied (bootloader) flash permission denied (bootloader) flash permission denied (bootloader) Cancelling 'bootloader.default.xml' FAILED (remote failure) finished. total time: 0.546s target reported max download size of 536870912 bytes sending 'modem_a' (78412 KB)... OKAY [ 4.390s] writing 'modem_a'... (bootloader) flash permission denied FAILED (remote failure) finished. total time: 4.417s any more ideas ? :crying: :crying: :crying:
brunojborges said: not worked :crying: did all he said : Unzip the 2 files (flashall ... and firm ...) and place them in a folder Click on "Preparation.bat", you must generate a "flash.bat file", double click with the phone in download mode It's all, really clean installation It was what I did, I am not responsible for damage to your equipment but nothing can be flashed because of bootloader locked: C:\Users\Usuario\Desktop\Nova pasta\NASH_RETAIL_9.0_PPX29.159-19_subsidy-DEFAULT _regulatory-DEFAULT_CFC.xml>echo off max-sparse-size: 268435456 finished. total time: 0.003s ... OKAY [ 0.009s] finished. total time: 0.010s target reported max download size of 536870912 bytes sending 'partition' (206 KB)... OKAY [ 0.050s] writing 'partition'... (bootloader) Validating 'gpt.default.xml' (bootloader) Committing 'gpt.default.xml' (bootloader) - flashing 'gpt_main0.bin' to 'partition:0' (bootloader) - flashing 'gpt_main1.bin' to 'partition:1' (bootloader) - flashing 'gpt_main2.bin' to 'partition:2' (bootloader) - flashing 'gpt_main3.bin' to 'partition:3' (bootloader) - flashing 'gpt_main4.bin' to 'partition:4' (bootloader) - flashing 'gpt_main5.bin' to 'partition:5' OKAY [ 0.229s] finished. total time: 0.281s target reported max download size of 536870912 bytes sending 'bootloader' (9884 KB)... OKAY [ 0.384s] writing 'bootloader'... (bootloader) Validating 'bootloader.default.xml' (bootloader) flash permission denied (bootloader) flash permission denied (bootloader) flash permission denied (bootloader) flash permission denied (bootloader) flash permission denied (bootloader) flash permission denied (bootloader) flash permission denied (bootloader) flash permission denied (bootloader) flash permission denied (bootloader) flash permission denied (bootloader) flash permission denied (bootloader) flash permission denied (bootloader) Cancelling 'bootloader.default.xml' FAILED (remote failure) finished. total time: 0.546s target reported max download size of 536870912 bytes sending 'modem_a' (78412 KB)... OKAY [ 4.390s] writing 'modem_a'... (bootloader) flash permission denied FAILED (remote failure) finished. total time: 4.417s any more ideas ? :crying: :crying: :crying: Click to expand... Click to collapse well, I recommend that you download the Lenovo moto application, something like that is the name, after installing it, connect the terminal in Lenovo moto app in fastboot mode, click on the Flash option and then where it says to recover, complete the information that asks you wait for it to finish, an official ROM flashed, and from there you can start with the bootloader unlock
Have you signed into a google account on the phone? Do you see developer options in settings? I know you said you didn't see oem unlocking so that's why I ask. We'll try to tackle those and get you unlocked. It's possible that you pbl and trust zone is messed up so a blankflash might be needed to sort that. With a locked bootloader you should able to flash the same firmware version or newer, but if your chain of trust is compromised it's a little difficult, but not impossible.
41rw4lk said: Have you signed into a google account on the phone? Do you see developer options in settings? I know you said you didn't see oem unlocking so that's why I ask. We'll try to tackle those and get you unlocked. It's possible that you pbl and trust zone is messed up so a blankflash might be needed to sort that. With a locked bootloader you should able to flash the same firmware version or newer, but if your chain of trust is compromised it's a little difficult, but not impossible. Click to expand... Click to collapse i cant sign into google accouts because there is no gapps pre installed on LineageOS, and i cant flash anything because the bootloader locked. There is developer options but only the adb debbug option, there is no "oem unlock" option (thats why when i try to fastboot oem unlock "CODE", the prompt says that i need to first activate the "oem unlock" option into the system, but as i said, there is no OEM option inside developer options. Maybe could be this "chain of thrust" thing. What should i do? thanks
brunojborges said: i cant sign into google accouts because there is no gapps pre installed on LineageOS, and i cant flash anything because the bootloader locked. There is developer options but only the adb debbug option, there is no "oem unlock" option (thats why when i try to fastboot oem unlock "CODE", the prompt says that i need to first activate the "oem unlock" option into the system, but as i said, there is no OEM option inside developer options. Maybe could be this "chain of thrust" thing. What should i do? thanks Click to expand... Click to collapse Can you not sign into google from accounts in settings? Also, you can download the playstore apk and install it manually. Usually to enable oem unlocking you have to be signed into google. So check accounts and see if you can sign in there, and/or d/l the apk and sign in there. Reboot and check dev options again for oem unlocking once you've signed in.
Heridg said: well, I recommend that you download the Lenovo moto application, something like that is the name, after installing it, connect the terminal in Lenovo moto app in fastboot mode, click on the Flash option and then where it says to recover, complete the information that asks you wait for it to finish, an official ROM flashed, and from there you can start with the bootloader unlock Click to expand... Click to collapse i need unlock bootloader just to revert to stock. I dont want to keep unlocked, or install custom stuff. If i just had the "oem unlock" option in developer options, i could fix that. And about moto smart assistant, when i put my phone and do this steps, after choosing my phone number and model, after the program detect my phone in fastboot mode, it shows a message, "this device is not supported".
41rw4lk said: Can you not sign into google from accounts in settings? Also, you can download the playstore apk and install it manually. Usually to enable oem unlocking you have to be signed into google. So check accounts and see if you can sign in there, and/or d/l the apk and sign in there. Reboot and check dev options again for oem unlocking once you've signed in. Click to expand... Click to collapse installed both, play store and services apk's from different sites. Tried clean cache, and anything else, but there is always a message forcing to close app. Cant open them.
(bootloader) slot-successful:_a: yes (bootloader) slot-successful:_b: no maybe isnt this messing this phone ?
Well the bottom line is you got a mismatched system, no recovery, a locked bootloader, no gapps; what a mess. First I would hit fastboot and issue 'fastboot -w' w/o quotes. That will format data and get rid of potentially any bits of garbage. Once that is done reboot to system and you should have to do setup again. Part of setup is signing into google, so once that is done check dev settings again to see if oem unlocking has become available. It's odd that it's just not there. Most times it's there and possibly just greyed out. If that doesn't yield any changes then a blankflash is the only option you have left to sort it, that's the dicey part that will either make it or break it. We'll worry about that if and when we get there. Just be warned this part will be the most dangerous so it's your decision to proceed from here. Whoever gave you that phone didn't do you any favors.
41rw4lk said: Well the bottom line is you got a mismatched system, no recovery, a locked bootloader, no gapps; what a mess. First I would hit fastboot and issue 'fastboot -w' w/o quotes. That will format data and get rid of potentially any bits of garbage. Once that is done reboot to system and you should have to do setup again. Part of setup is signing into google, so once that is done check dev settings again to see if oem unlocking has become available. It's odd that it's just not there. Most times it's there and possibly just greyed out. If that doesn't yield any changes then a blankflash is the only option you have left to sort it, that's the dicey part that will either make it or break it. We'll worry about that if and when we get there. Just be warned this part will be the most dangerous so it's your decision to proceed from here. Whoever gave you that phone didn't do you any favors. Click to expand... Click to collapse Please sr teach me how to do this blankflash thing, in the truth, i could bring back imeis erased from a axon 7 i had, making A LOT of crazy and dangerous moves (deleting partitions, backup binary files, editing and return back, etc), but im new with this motorola. Please teach me :crying: :crying:
41rw4lk said: Well the bottom line is you got a mismatched system, no recovery, a locked bootloader, no gapps; what a mess. First I would hit fastboot and issue 'fastboot -w' w/o quotes. That will format data and get rid of potentially any bits of garbage. Once that is done reboot to system and you should have to do setup again. Part of setup is signing into google, so once that is done check dev settings again to see if oem unlocking has become available. It's odd that it's just not there. Most times it's there and possibly just greyed out. If that doesn't yield any changes then a blankflash is the only option you have left to sort it, that's the dicey part that will either make it or break it. We'll worry about that if and when we get there. Just be warned this part will be the most dangerous so it's your decision to proceed from here. Whoever gave you that phone didn't do you any favors. Click to expand... Click to collapse C:\Users\Usuario\Desktop\Nova pasta\NASH_RETAIL_9.0_PPX29.159-19_subsidy-DEFAULT _regulatory-DEFAULT_CFC.xml>fastboot -w wiping userdata... Erase successful, but not automatically formatting. File system type raw not supported. erasing 'userdata'... (bootloader) Permission denied FAILED (remote failure) finished. total time: 0.012s didnt worked. I have to do this blankflash.
brunojborges said: Please sr teach me how to do this blankflash thing, in the truth, i could bring back imeis erased from a axon 7 i had, making A LOT of crazy and dangerous moves (deleting partitions, backup binary files, editing and return back, etc), but im new with this motorola. Please teach me :crying: :crying: Click to expand... Click to collapse If you've already tried 'fastboot -w' and nothing has changed for you then you can try to blankflash and reflash the pie firmware you downloaded previously. Read the whole post before you try and just know that there is a real chance of failure. Plenty have recovered their phone, even with locked bootloaders, but it's not 100% success. I think the biggest problem you might face is finding the proper firmware to flash, but I would start with the pie firmware you already have since it seems that pie is already on your phone (sort of). Here is the blankflash post. Follow the directions closely, read it all, and be warned what you do is your choice. https://forum.xda-developers.com/showpost.php?p=77623934&postcount=5
41rw4lk said: If you've already tried 'fastboot -w' and nothing has changed for you then you can try to blankflash and reflash the pie firmware you downloaded previously. Read the whole post before you try and just know that there is a real chance of failure. Plenty have recovered their phone, even with locked bootloaders, but it's not 100% success. I think the biggest problem you might face is finding the proper firmware to flash, but I would start with the pie firmware you already have since it seems that pie is already on your phone (sort of). Here is the blankflash post. Follow the directions closely, read it all, and be warned what you do is your choice. https://forum.xda-developers.com/showpost.php?p=77623934&postcount=5 Click to expand... Click to collapse thanks, i will read 10x before do anytyhing, and will do carefully. i had nothing else to do. This will fix my phone or it will turn a paper weight. Im warned. Thank you sir, wish me luck and i will tell u if i have any sucess.
41rw4lk said: If you've already tried 'fastboot -w' and nothing has changed for you then you can try to blankflash and reflash the pie firmware you downloaded previously. Read the whole post before you try and just know that there is a real chance of failure. Plenty have recovered their phone, even with locked bootloaders, but it's not 100% success. I think the biggest problem you might face is finding the proper firmware to flash, but I would start with the pie firmware you already have since it seems that pie is already on your phone (sort of). Here is the blankflash post. Follow the directions closely, read it all, and be warned what you do is your choice. https://forum.xda-developers.com/showpost.php?p=77623934&postcount=5 Click to expand... Click to collapse if i click on .bat file: C:\Users\Usuario\Desktop\Nova pasta\NASH_RETAIL_9.0_PPX29.159-19_subsidy-DEFAULT _regulatory-DEFAULT_CFC.xml>.\qboot.exe blank-flash < waiting for device > and if i do manually "fastboot oem blankflash": C:\Users\Usuario\Desktop\Nova pasta\NASH_RETAIL_9.0_PPX29.159-19_subsidy-DEFAULT _regulatory-DEFAULT_CFC.xml>fastboot oem blankflash ... (bootloader) Command Restricted FAILED (remote failure) finished. total time: 0.012s :crying: :crying: :crying: :crying: :crying: :crying: :crying: there is any way to force hard brick and them enter in Qualcomm HS-USB QDLoader 900 mode? Maybe this way will be easier :crying: :crying:
brunojborges said: if i click on .bat file: C:\Users\Usuario\Desktop\Nova pasta\NASH_RETAIL_9.0_PPX29.159-19_subsidy-DEFAULT _regulatory-DEFAULT_CFC.xml>.\qboot.exe blank-flash < waiting for device > and if i do manually "fastboot oem blankflash": C:\Users\Usuario\Desktop\Nova pasta\NASH_RETAIL_9.0_PPX29.159-19_subsidy-DEFAULT _regulatory-DEFAULT_CFC.xml>fastboot oem blankflash ... (bootloader) Command Restricted FAILED (remote failure) finished. total time: 0.012s :crying: :crying: :crying: :crying: :crying: :crying: :crying: there is any way to force hard brick and them enter in Qualcomm HS-USB QDLoader 900 mode? Maybe this way will be easier :crying: :crying: Click to expand... Click to collapse boot to os, make sure adb debugging is enabled, then open a cmd prompt and enter 'adb reboot edl' w/o quotes
Question Preflash validation failed on REVVLRY+ (G7 Plus), XT1965-T
Dear Experts, Today I was trying to convert a REVVLRY+ (G7 Plus via TMobile) to Lineage microg 20, but got the error: Preflash validation failed ... Phone was sold via TMobile. On the back is printed the T logo, and at the bottom: REVVL Phone is OEM unlocked. ... Downloaded the latest Lineage microg files from: lake download.lineage.microg.org adb reboot bootloader fastboot flash boot C:\...20.0-20230213-microG-lake-boot.img (bootloader) is-logical:boot_a: not found Sending 'boot_a' (26545 KB) OKAY [ 0.630s] Writing 'boot_a' (bootloader) Preflash validation failed FAILED (remote: '') fastboot: error: Command failed ... Some data from adb shell: ... getprop | grep -i "model" [media.recorder.show_manufacturer_and_model]: [true] [ro.opa.device_model_id]: [motorola-lake_n] [ro.product.model]: [REVVLRY+] [ro.product.odm.model]: [REVVLRY+] [ro.product.system.model]: [REVVLRY+] [ro.product.vendor.model]: [REVVLRY+] ... No instances of G7 in the properties. getprop | grep -i "g" | grep -i "7" [dalvik.vm.heaptargetutilization]: [0.75] [ro.com.google.rlz_ap_whitelist]: [y0,y5,y6,y7,y8,YH] [ro.gwfcactivation.disabled_carriers]: [1187,576,1962,1895,2020,1403,1404,2021,2008,1492,28,1839] [ro.mot.build.guid]: [27f8f602936ea71] [ro.mot.gms.rlz_ap_whitelist]: [y0,y5,y6,y7,y8,YH] ... XT1965-T getprop | grep -i "sku" [ro.boot.hardware.sku]: [XT1965-T] [ro.boot.product.hardware.sku]: [n] [ro.vendor.product.hardware.sku.variant]: [n] ... In the properties, there are variations of "lake" lake_revvl lake lake_n getprop | grep -i "lake" [ro.mot.build.oem.product]: [lake_rv] [ro.mot.hab.product]: [lake] [ro.opa.device_model_id]: [motorola-lake_n] [ro.product.device]: [lake_n] [ro.product.name]: [lake_revvl_n] [ro.product.odm.device]: [lake] [ro.product.odm.name]: [lake_revvl] [ro.product.product.name]: [lake_revvl] [ro.product.system.device]: [lake] [ro.product.system.name]: [lake_revvl] [ro.product.vendor.device]: [lake] [ro.product.vendor.name]: [lake_revvl] [ro.vendor.hw.device]: [lake] [ro.vendor.product.device]: [lake_n] [ro.vendor.product.name]: [lake_n] ... I'm suspecting that this phone had a specific build. It's not the stock lake build for the standard Motorola G7 Plus. Is that correct? Is it possible to install Lineage on this phone? Either stock, or microg? If so, where can I find the correct binaries? And, any special instructions if necessary? Thanks a lot!
Some more info. The same error is happening with other Lineage versions, and even another phone. With the same phone, I tried installing Stock Lineage, version 20 Same issue. ... Then, with another phone, a stock G7 Plus, there was also the same issue. Lineage 19, microg Lineage 19, stock fastboot flash boot C:\Download\LineageOS\lake\lineage-19.1-20221025-recovery-lake.img (bootloader) is-logical:boot_a: not found Sending 'boot_a' (24969 KB) OKAY [ 0.598s] Writing 'boot_a' (bootloader) Preflash validation failed FAILED (remote: '') fastboot: error: Command failed --- More info from the first phone mentioned: fastboot getvar all (bootloader) securestate: oem_locked (bootloader) iswarrantyvoid: no (bootloader) date: 05-15-2020 (bootloader) sku: XT1965-T (bootloader) carrier_sku: XT1965-T (bootloader) current-slot: a (bootloader) running-bl-slot: _a/_a (bootloader) running-boot-lun: 0 (bootloader) slot-count: 2 (bootloader) slot-successful:_a: yes (bootloader) slot-successful:_b: no (bootloader) slot-unbootable:_a: no (bootloader) slot-unbootable:_b: yes (bootloader) slot-retry-count:_a: 6 (bootloader) slot-retry-count:_b: 0 ---- fastboot oem partition ... (bootloader) boot_a: offset=376192KB, size=65536KB (bootloader) boot_b: offset=441728KB, size=65536KB ---- Any ideas? Is there something I'm missing? Thanks
Ok, I figured it out the solution: You have to do the unlock command, not once, but twice fastboot oem unlock UNIQUE_KEY fastboot oem unlock UNIQUE_KEY fastboot reboot Then, on reboot, you will now see the unlock warning Takes a while to reboot. Reboots to stock Android: 'Hi There' ... Posted just in case any other poor soul has this error.