Related
Recently acquired a bricked moto x pure. No way of knowing for sure how it was bricked but I'm guessing attempted downgrade. When starting up the Bootloader logs say:
AP fastboot flash mode (secure)
failed to validate boot image
ERROR: Failed to pass validation, backup to fastboot
Fastboot reason: Fall-through from charger boot mode
CID read failure
Invalid CID status 0x69
Click to expand...
Click to collapse
fastboot getvar all gives:
(bootloader) version: 0.5
(bootloader) version-bootloader: moto-msm8992-A0.48(*)
(bootloader) product: clark
(bootloader) board: clark
(bootloader) secure: yes
(bootloader) hwrev: 0x83C0
(bootloader) radio: 0x2
(bootloader) emmc: 16GB Samsung REV=07 PRV=01 TYPE=57 PNM=AGND3R
(bootloader) ram[0]: 3072MB SK Hynix S8 SDRAM DIE=6Gb M5=x6 M6=x3 M7=x0
(bootloader) ram[1]: M8=x3B
(bootloader) cpu: MSM8992
(bootloader) serialno: TA084034CW
(bootloader) cid: 0xDEAD
(bootloader) channelid: 0x8d
(bootloader) uid: 3862CC001E000000000000000000
(bootloader) unlocked: no
(bootloader) securestate: locked
(bootloader) iswarrantyvoid: no
(bootloader) mot_sst: 0
(bootloader) max-download-size: 536870912
(bootloader) reason: Fall-through from charger boot mode
(bootloader) date: 10-07-2015
(bootloader) sku: XT1575
(bootloader) battid:
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Wed Mar 9 14:23:32 UTC 2016"
(bootloader) ro.build.fingerprint[0]: motorola/clark_retus/clark:6.0/MPH
(bootloader) ro.build.fingerprint[1]: S24.49-18-3/3:user/release-keys
(bootloader) ro.build.version.full[0]: Blur_Version.24.201.3.clark_retus
(bootloader) ro.build.version.full[1]: .retus.en.US
(bootloader) ro.build.version.qcom: <not found>
(bootloader) version-baseband: M8992_1255331.29.01.88.02R SUPER_NA
(bootloader) kernel.version[0]: Linux version 3.10.84-perf-g6898f68 (hud
(bootloader) kernel.version[1]: [email protected]) (gcc version 4.9.x-goog
(bootloader) kernel.version[2]: le 20140827 (prerelease) (GCC) ) #1 SMP
(bootloader) kernel.version[3]: PREEMPT Sat Jan 30 14:35:02 CST 2016
(bootloader) sbl1.git: sbl1.git
(bootloader) rpm.git: rpm.git
(bootloader) tz.git: tz.git
(bootloader) hyp.git: hyp.git
(bootloader) sdi.git: sdi.git
(bootloader) pmic.git: pmic.git
(bootloader) aboot.git: git=MBM-NG-VA0.48-0-g8c942c6
(bootloader) qe:
(bootloader) frp-state: no protection (err)
(bootloader) ro.carrier: retus
all: listed above
finished. total time: 0.422s
Click to expand...
Click to collapse
I attempted to flash the CLARK_RETUS_6.0_MPHS24.49-18-3_cid9_subsidy-DEFAULT_CFC.xml stock firmware but got the following error:
fastboot flash partition gpt.bin
target reported max download size of 536870912 bytes
sending 'partition' (32 KB)...
OKAY [ 0.094s]
writing 'partition'...
(bootloader) This may take a few seconds, if a
(bootloader) different partition table is being
(bootloader) flashed since we need to backup
(bootloader) and restore a few partitions
(bootloader) Flashing primary GPT image...
(bootloader) Failed to write primary GPT.
(bootloader) Failed to program partition table
FAILED (remote failure)
finished. total time: 0.953s
Click to expand...
Click to collapse
I also tried using mfastboot, with the same results. Anybody know how to fix this?
Is your bootloader locked?
thebaconbox said:
Is your bootloader locked?
Click to expand...
Click to collapse
Yes it is. Tried to unlock it already but I get:
>fastboot oem get_unlock_data
...
(bootloader) Failed to get unlock data, please try again!
FAILED (remote failure)
finished. total time: 0.016s
Click to expand...
Click to collapse
Just ignore the gpt.bin error and continue... The partition table hasn't changed since Marshmallow released on this device.
Any reason not to use the 18-4 firmware? It is readily available...
acejavelin said:
Just ignore the gpt.bin error and continue... The partition table hasn't changed since Marshmallow released on this device.
Any reason not to use the 18-4 firmware? It is readily available...
Click to expand...
Click to collapse
I tried 18-4 as well and got the same results. 18-3 seemed to be what was on the device before it was bricked so I tried that one first. If I continue get more errors:
>fastboot flash bootloader bootloader.img
target reported max download size of 536870912 bytes
sending 'bootloader' (2699 KB)...
OKAY [ 0.094s]
writing 'bootloader'...
(bootloader) flashing aboot ...
(bootloader) Failed to erase partition
(bootloader) Failed to flash aboot
FAILED (remote failure)
finished. total time: 1.961s
>fastboot flash logo logo.bin
target reported max download size of 536870912 bytes
sending 'logo' (3687 KB)...
OKAY [ 0.141s]
writing 'logo'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition logo
FAILED (remote failure)
finished. total time: 0.234s
Click to expand...
Click to collapse
I get the same errors if I try to flash anything.
jml1290 said:
I tried 18-4 as well and got the same results. 18-3 seemed to be what was on the device before it was bricked so I tried that one first. If I continue get more errors:
I get the same errors if I try to flash anything.
Click to expand...
Click to collapse
Try 'fastboot oem fb_mode_clear' followed by 'fastboot oem fb_mode_set' and try again.
acejavelin said:
Try 'fastboot oem fb_mode_clear' followed by 'fastboot oem fb_mode_set' and try again.
Click to expand...
Click to collapse
Here's what I get:
>fastboot oem fb_mode_clear
...
OKAY [ 0.000s]
finished. total time: 0.000s
>fastboot oem fb_mode_set
...
FAILED (remote failure)
finished. total time: 0.000s
>fastboot flash bootloader bootloader.img
target reported max download size of 536870912 bytes
sending 'bootloader' (2699 KB)...
OKAY [ 0.078s]
writing 'bootloader'...
(bootloader) flashing aboot ...
(bootloader) Failed to erase partition
(bootloader) Failed to flash aboot
FAILED (remote failure)
finished. total time: 1.561s
Click to expand...
Click to collapse
jml1290 said:
Here's what I get:
Click to expand...
Click to collapse
Hmm... Looks bad... Nothing will write, erase, or format, like the emmc module is bad.
acejavelin said:
Hmm... Looks bad... Nothing will write, erase, or format, like the emmc module is bad.
Click to expand...
Click to collapse
That's what I was afraid of. My only other idea was to try and force the phone into HS-USB QDLoader mode and fix it from there. But I have no idea how to do this and if there was something physically wrong with the emmc I doubt it would help anyway. Thanks for the input!
jml1290 said:
That's what I was afraid of. My only other idea was to try and force the phone into HS-USB QDLoader mode and fix it from there. But I have no idea how to do this and if there was something physically wrong with the emmc I doubt it would help anyway. Thanks for the input!
Click to expand...
Click to collapse
Sorry... But if the bootloader is locked you might be able to register it on your Motorola account and file a warranty claim, couldn't hurt to try.
Hello there,
I am trying to root my nokia 6 TA - 1033.
(bootloader) version:0.5
(bootloader) battery-soc-ok:yes
(bootloader) battery-voltage:4029000
(bootloader) variant:FIH eMMC
(bootloader) unlocked:no
(bootloader) secure:yes
(bootloader) version-baseband:
(bootloader) version-bootloader:
(bootloader) display-panel:
(bootloader) off-mode-charge:0
(bootloader) charger-screen-enabled:0
(bootloader) max-download-size: 0xf0000000
(bootloader) partition-type:userdata:ext4
(bootloader) kernel:lk
(bootloader) product1C
1. cmd : fastboot oem dm-verity XXXXXXXXXXXXXXXXXXXXXXXX (MD5 number)
FAILED (remote: unknown command)
finished. total time: 0.005s
2. no help with this cmd too : adb reboot "dm-verity enforcing"
fastboot oem disable_dm_verity
3. fastboot flash recovery /home/$USER/me.twrp.twrpapp-26.apk
target reported max download size of 535822336 bytes
sending 'recovery' (2703 KB)...
OKAY [ 0.109s]
writing 'recovery'...
FAILED (remote: Partition flashing is not allowed)
finished. total time: 0.113s
gaganhere said:
Hello there,
I am trying to root my nokia 6 TA - 1033.
(bootloader) version:0.5
(bootloader) battery-soc-ok:yes
(bootloader) battery-voltage:4029000
(bootloader) variant:FIH eMMC
(bootloader) unlocked:no
(bootloader) secure:yes
(bootloader) version-baseband:
(bootloader) version-bootloader:
(bootloader) display-panel:
(bootloader) off-mode-charge:0
(bootloader) charger-screen-enabled:0
(bootloader) max-download-size: 0xf0000000
(bootloader) partition-type:userdata:ext4
(bootloader) kernel:lk
(bootloader) product1C
1. cmd : fastboot oem dm-verity XXXXXXXXXXXXXXXXXXXXXXXX (MD5 number)
FAILED (remote: unknown command)
finished. total time: 0.005s
2. no help with this cmd too : adb reboot "dm-verity enforcing"
fastboot oem disable_dm_verity
3. fastboot flash recovery /home/$USER/me.twrp.twrpapp-26.apk
target reported max download size of 535822336 bytes
sending 'recovery' (2703 KB)...
OKAY [ 0.109s]
writing 'recovery'...
FAILED (remote: Partition flashing is not allowed)
finished. total time: 0.113s
Click to expand...
Click to collapse
WhatsApp me at 9650710447 for bootloader unlock
sltushar said:
WhatsApp me at 9650710447 for bootloader unlock
Click to expand...
Click to collapse
I also want to root nokia 6.1 plus
rohitgnw said:
I also want to root nokia 6.1 plus
Click to expand...
Click to collapse
I also want to root my device.... Any help?
rohitgnw said:
I also want to root nokia 6.1 plus
Click to expand...
Click to collapse
You need bootloader unlock key, pm me for that on WhatsApp
Edit: SOLVED. Flashed 8.1.0 October update before rebooting and everything went fine
First I unlocked the bootloader using this guide.
Then I immediately flashed TWRP using this guide from the TWRP site. After rebooting, I was unable to access "Recovery" in the bootloader as I was shown an error message, "Moto G5 Plus is unlocked and can't be trusted, bad key error", as seen in this post. A user on the post said to flash the stock ROM and then reflash TWRP.
I rebooted into bootloader and flashed the Android 7.1 stock rom. While still in the bootloader, I then realized that I messed up and should've flashed the the 8.1.0 stock ROM as that is what the device initially had. I then download the 8.1.0 ROM from here and flash it in fastboot using this guide.
However, while flashing 8.1.0, the following errors were output (I removed the successful outputs):
HTML:
fastboot oem fb_mode_set
OKAY [ 0.002s]
Finished. Total time: 0.003s
PS C:\Users\subha\Downloads\POTTER_RETAIL_8.1.0_OPS28.85-17_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml> fastboot f
lash partition gpt.bin
Sending 'partition' (45 KB) OKAY [ 0.006s]
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 failure)
Finished. Total time: 0.079s
PS C:\Users\subha\Downloads\POTTER_RETAIL_8.1.0_OPS28.85-17_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml> fastboot f
lash boot boot.img
Sending 'boot' (16384 KB) OKAY [ 0.383s]
Writing 'boot' (bootloader) Image signed with key bad key
OKAY [ 0.258s]
Finished. Total time: 0.645s
PS C:\Users\subha\Downloads\POTTER_RETAIL_8.1.0_OPS28.85-17_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml> fastboot f
lash recovery recovery.img
Sending 'recovery' (20580 KB) OKAY [ 0.467s]
Writing 'recovery' (bootloader) Image signed with key bad key
OKAY [ 0.350s]
Finished. Total time: 0.823s
PS C:\Users\subha\Downloads\POTTER_RETAIL_8.1.0_OPS28.85-17_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml> fastboot e
rase customize
Erasing 'customize' (bootloader) Permission denied
FAILED (remote failure)
Finished. Total time: 0.007s
PS C:\Users\subha\Downloads\POTTER_RETAIL_8.1.0_OPS28.85-17_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml> fastboot e
rase clogo
Erasing 'clogo' (bootloader) Permission denied
FAILED (remote failure)
Finished. Total time: 0.120s
I'm still sitting in the bootloader as I'm afraid of rebooting in fear of potentially hardbricking the device. The
HTML:
image_primary gpt
error in particular seems kind of scary - Googling it, it seems people only encountered it when hardbricking the device.
Here is an output of my
HTML:
fastboot gervar all
:
HTML:
(bootloader) version: 0.5
(bootloader) version-bootloader: moto-msm8953-C0.92
(bootloader) product: potter
(bootloader) board: potter
(bootloader) secure: yes
(bootloader) hwrev: P3B
(bootloader) radio: 1
(bootloader) storage-type: emmc
(bootloader) emmc: 64GB SAMSUNG RC14MB RV=08 PV=07 FV=0000000000000007
(bootloader) ram: 4GB SAMSUNG LP3 DIE=8Gb M5=01 M6=05 M7=00 M8=5F
(bootloader) cpu: MSM8953
(bootloader) serialno: removed
(bootloader) cid: 0x0032
(bootloader) channelid: 0x8d
(bootloader) uid: removed
(bootloader) securestate: flashing_unlocked
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 534773760
(bootloader) reason: Reboot mode set to fastboot
(bootloader) imei: removed
(bootloader) meid:
(bootloader) date: 03-12-2017
(bootloader) sku: XT1687
(bootloader) carrier_sku:
(bootloader) battid:
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Fri Jan 16 3:38:17 UTC 1970"
(bootloader) ro.build.fingerprint[0]: motorola/potter/potter:8.1.0/OPSS2
(bootloader) ro.build.fingerprint[1]: 8.85-17-2/945e:user/release-keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.28.211.2.potter.reta
(bootloader) ro.build.version.full[1]: il.en.US
(bootloader) ro.build.version.qcom: LA.UM.6.6.r1-08600-89xx.0
(bootloader) version-baseband: M8953_41.50.07.85R POTTER_NA_CUST
(bootloader) kernel.version[0]: Linux version 3.18.71-perf-gea366bb-0000
(bootloader) kernel.version[1]: 4-g7402761 ([email protected]) (gcc ver
(bootloader) kernel.version[2]: sion 4.9.x 20150123 (prerelease) (GCC) )
(bootloader) kernel.version[3]: #1 SMP PREEMPT Wed Oct 10 09:19:54 CDT
(bootloader) kernel.version[4]: 2018
(bootloader) sbl1.git: git=MBM-NG-VC0.92-0-gd009c3b
(bootloader) rpm.git: git=MBM-NG-VC0.91-0-g92e5e21-dirty
(bootloader) tz.git: git=MBM-NG-VC0.91-2-g26cc248-dirty
(bootloader) devcfg.git: git=MBM-NG-VC0.91-2-g26cc248-dirty
(bootloader) keymaster.git: git=MBM-NG-VC0.91-2-g26cc248-dirty
(bootloader) cmnlib.git: git=MBM-NG-VC0.91-2-g26cc248-dirty
(bootloader) cmnlib64.git: git=MBM-NG-VC0.91-2-g26cc248-dirty
(bootloader) prov.git: git=MBM-NG-VC0.91-2-g26cc248-dirty
(bootloader) aboot.git: git=MBM-NG-VC0.92-0-g3ea8df0
(bootloader) frp-state: no protection (0)
(bootloader) ro.carrier: retus
(bootloader) current-slot:
(bootloader) slot-suffixes: _a
(bootloader) slot-count: 1
(bootloader) slot-successful:_a: INVALID
(bootloader) slot-successful:_b: INVALID
(bootloader) slot-bootable:_a: INVALID
(bootloader) slot-bootable:_b: INVALID
(bootloader) slot-retry-count:_a: unknown
(bootloader) slot-retry-count:_b: unknown
all: listed above
Finished. Total time: 0.273s
Is my device okay, and am I okay to reboot? If something is wrong, is there anything I can do to fix it? Thanks!
Hi team,
I need help. I have a Moto G5 Plus (XT1687). A few weeks ago, it kept rebooting. Went to shut it down. Never rebooted again... After investigation, I understood it was hard bricked. I then followed some guide and managed to get it softbricked. Now, I don't actually remember which blank flash I used, but I have the feeling I used the wrong one (possibly for model XT1686), because I just can't flash anything else now (like Potter).
I don't need or want to root the phone, I just want to go back to the stock OS. I am not actually quite sure if I had Potter v.7 or 8 (or another version?).
I am far from an expert, so I am just trying to follow guides, but I don't really know what I am doing.
Anyway... I tried again to follow this guide https://forum.xda-developers.com/g5-plus/how-to/solution-to-flash-stock-romfactory-t3691396 but I don't actually go far.
Let me explain what I see...
When booting the phone, I get this screen:
https://drive.google.com/file/d/1dgwGtsSLh3VYOaD6PKJhJ2_Z5DpczY0k/view?usp=sharing
I then move to Recovery mode, and*this is what I see:
https://drive.google.com/file/d/18fPYBMkxU2N9P9zD6UB5ouKZ5w3AebQu/view?usp=sharing
In the Windows command prompt, when I type fasboot devices, I get the result
a58c134 fastboot
though nothing shows up on the phone. But I assume this is correct.
Then, when I start typing the first lines of code, I get errors in the command prompt:
https://drive.google.com/file/d/14t-amwAzANZjroGBgsnzOeE6pQgQCUdL/view?usp=sharing
Now, I do see there is some communication going on with the phone, as the phone displays something. This is what I get with the commands:
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
https://drive.google.com/file/d/1pujKmNB0zYrswztGXwJYNGNLPCeD0ZQe/view?usp=sharing
So... That's where I am. Don't really know if I managed to flash anything in the phone, but since I get all those issues, I guess that nothing is transferred. Please help!
Glencoe said:
Hi team,
I need help. I have a Moto G5 Plus (XT1687). A few weeks ago, it kept rebooting. Went to shut it down. Never rebooted again... After investigation, I understood it was hard bricked. I then followed some guide and managed to get it softbricked. Now, I don't actually remember which blank flash I used, but I have the feeling I used the wrong one (possibly for model XT1686), because I just can't flash anything else now (like Potter).
I don't need or want to root the phone, I just want to go back to the stock OS. I am not actually quite sure if I had Potter v.7 or 8 (or another version?).
I am far from an expert, so I am just trying to follow guides, but I don't really know what I am doing.
Anyway... I tried again to follow this guide https://forum.xda-developers.com/g5-plus/how-to/solution-to-flash-stock-romfactory-t3691396 but I don't actually go far.
Let me explain what I see...
When booting the phone, I get this screen:
https://drive.google.com/file/d/1dgwGtsSLh3VYOaD6PKJhJ2_Z5DpczY0k/view?usp=sharing
I then move to Recovery mode, and*this is what I see:
https://drive.google.com/file/d/18fPYBMkxU2N9P9zD6UB5ouKZ5w3AebQu/view?usp=sharing
In the Windows command prompt, when I type fasboot devices, I get the result
a58c134 fastboot
though nothing shows up on the phone. But I assume this is correct.
Then, when I start typing the first lines of code, I get errors in the command prompt:
https://drive.google.com/file/d/14t-amwAzANZjroGBgsnzOeE6pQgQCUdL/view?usp=sharing
Now, I do see there is some communication going on with the phone, as the phone displays something. This is what I get with the commands:
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
https://drive.google.com/file/d/1pujKmNB0zYrswztGXwJYNGNLPCeD0ZQe/view?usp=sharing
So... That's where I am. Don't really know if I managed to flash anything in the phone, but since I get all those issues, I guess that nothing is transferred. Please help!
Click to expand...
Click to collapse
run
Code:
fastboot getvar all
Please post it here after you remove the IMEI line
Sent from my ali using XDA Labs
sd_shadow said:
run
Code:
fastboot getvar all
Please post it here after you remove the IMEI line
Click to expand...
Click to collapse
Thanks sd_shadow! So this is what I get:
c:\adb>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: moto-msm8953-C0.C5(*)
(bootloader) product: potter
(bootloader) board: potter
(bootloader) secure: yes
(bootloader) hwrev: P3B
(bootloader) radio: 1
(bootloader) storage-type: emmc
(bootloader) emmc: 32GB SKHYNIX HBG4a2 RV=08 PV=A5 FV=00000000000000A5
(bootloader) ram: 2GB SKHYNIX LP3 DIE=8Gb M5=06 M6=03 M7=00 M8=1F
(bootloader) cpu: MSM8953
(bootloader) serialno: a58c134
(bootloader) cid: 0xDEAD
(bootloader) channelid: 0x00
(bootloader) uid: 0000000000000000000000000000
(bootloader) securestate: oem_locked
(bootloader) iswarrantyvoid: n/a
(bootloader) max-download-size: 536870912
(bootloader) reason: Failed to initialize partition table
(bootloader) imei: 000000000000000
(bootloader) meid:
(bootloader) date: 01-01-1970
(bootloader) sku: 000000000000000
(bootloader) battid:
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time:
(bootloader) ro.build.fingerprint:
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full:
(bootloader) ro.build.version.qcom:
(bootloader) version-baseband:
(bootloader) kernel.version:
(bootloader) sbl1.git: sbl1.git
(bootloader) rpm.git: rpm.git
(bootloader) tz.git: tz.git
(bootloader) devcfg.git: devcfg.git
(bootloader) keymaster.git: keymaster.git
(bootloader) cmnlib.git: cmnlib.git
(bootloader) cmnlib64.git: cmnlib64.git
(bootloader) prov.git: prov.git
(bootloader) aboot.git: git=MBM-NG-VC0.C5-0-g99aa1c1
(bootloader) qe:
(bootloader) frp-state: no protection (err)
(bootloader) ro.carrier:
all: listed above
finished. total time: 0.178s
What should I do know?
Glencoe said:
run
Thanks sd_shadow! So this is what I get:
c:\adb>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: moto-msm8953-C0.C5(*)
(bootloader) product: potter
(bootloader) board: potter
(bootloader) secure: yes
(bootloader) hwrev: P3B
(bootloader) radio: 1
(bootloader) storage-type: emmc
(bootloader) emmc: 32GB SKHYNIX HBG4a2 RV=08 PV=A5 FV=00000000000000A5
(bootloader) ram: 2GB SKHYNIX LP3 DIE=8Gb M5=06 M6=03 M7=00 M8=1F
(bootloader) cpu: MSM8953
(bootloader) serialno: a58c134
(bootloader) cid: 0xDEAD
(bootloader) channelid: 0x00
(bootloader) uid: 0000000000000000000000000000
(bootloader) securestate: oem_locked
(bootloader) iswarrantyvoid: n/a
(bootloader) max-download-size: 536870912
(bootloader) reason: Failed to initialize partition table
(bootloader) imei: 000000000000000
(bootloader) meid:
(bootloader) date: 01-01-1970
(bootloader) sku: 000000000000000
(bootloader) battid:
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time:
(bootloader) ro.build.fingerprint:
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full:
(bootloader) ro.build.version.qcom:
(bootloader) version-baseband:
(bootloader) kernel.version:
(bootloader) sbl1.git: sbl1.git
(bootloader) rpm.git: rpm.git
(bootloader) tz.git: tz.git
(bootloader) devcfg.git: devcfg.git
(bootloader) keymaster.git: keymaster.git
(bootloader) cmnlib.git: cmnlib.git
(bootloader) cmnlib64.git: cmnlib64.git
(bootloader) prov.git: prov.git
(bootloader) aboot.git: git=MBM-NG-VC0.C5-0-g99aa1c1
(bootloader) qe:
(bootloader) frp-state: no protection (err)
(bootloader) ro.carrier:
all: listed above
finished. total time: 0.178s
What should I do know?
Click to expand...
Click to collapse
Don't suppose you know which software channel it was on?
Verizon, Retail, RetEU...
I would try LMSA'S Flash rescue
Unlikely that will work though.
https://forum.xda-developers.com/general/general/update-moto-lenovo-moto-smart-assistant-t3951714
If you are in the USA and not sure which software channel try RetUS
https://mirrors.lolinet.com/firmware/moto/potter/official
Maybe try mfastboot.exe
Motorola Flashing Guide
https://forum.xda-developers.com/general/rooting-roms/guide-flashing-motorola-firmware-t4042039
Sent from my ali using XDA Labs
sd_shadow said:
Don't suppose you know which software channel it was on?
Verizon, Retail, RetEU...
Click to expand...
Click to collapse
I am from Canada, and my carrier is Videotron, though we bougth the (unlocked) phone from Target, in the US, so I'd think the channel may be RetUS indeed.
sd_shadow said:
I would try LMSA'S Flash rescue
Unlikely that will work though.
Click to expand...
Click to collapse
I should have mentioned I had already tried it, and it didn't work indeed. Just checked again, and all it says is "Failed to match the connected device..."
sd_shadow said:
Maybe try mfastboot.exe
Motorola Flashing Guide
https://forum.xda-developers.com/general/rooting-roms/guide-flashing-motorola-firmware-t4042039
Click to expand...
Click to collapse
I followed your guide (my, I realise you are a guru on here!), and tried flashing with mfastboot (while sending each system.img chunck separately, as I have 8 system.img_sparsechunck.* files)... Looks like it failed again!
This is what I get from the Command prompt:
C:\adb\mfastboot-v2>mfastboot devices
a58c134 fastboot
C:\adb\mfastboot-v2>mfastboot flash modem NON-HLOS.bin
target max-sparse-size: 256MB
sending 'modem' (71921 KB)...
OKAY [ 2.055s]
writing 'modem'...
(bootloader) Invalid partition name modem
FAILED (remote failure)
finished. total time: 2.076s
C:\adb\mfastboot-v2>mfastboot erase modemst1
erasing 'modemst1'...
(bootloader) Permission denied
FAILED (remote failure)
finished. total time: 0.022s
C:\adb\mfastboot-v2>mfastboot erase modemst2
erasing 'modemst2'...
(bootloader) Permission denied
FAILED (remote failure)
finished. total time: 0.010s
C:\adb\mfastboot-v2>mfastboot flash system system.img_sparsechunk.0
target max-sparse-size: 256MB
sending 'system' (258396 KB)...
OKAY [ 7.375s]
writing 'system'...
(bootloader) Invalid partition name system
FAILED (remote failure)
finished. total time: 7.388s
C:\adb\mfastboot-v2>mfastboot flash system system.img_sparsechunk.1
target max-sparse-size: 256MB
sending 'system' (256514 KB)...
OKAY [ 7.375s]
writing 'system'...
(bootloader) Invalid partition name system
FAILED (remote failure)
finished. total time: 7.399s
C:\adb\mfastboot-v2>mfastboot flash system system.img_sparsechunk.2
target max-sparse-size: 256MB
sending 'system' (246302 KB)...
OKAY [ 7.090s]
writing 'system'...
(bootloader) Invalid partition name system
FAILED (remote failure)
finished. total time: 7.104s
C:\adb\mfastboot-v2>mfastboot flash system system.img_sparsechunk.3
target max-sparse-size: 256MB
sending 'system' (262141 KB)...
OKAY [ 7.494s]
writing 'system'...
(bootloader) Invalid partition name system
FAILED (remote failure)
finished. total time: 7.518s
C:\adb\mfastboot-v2>mfastboot flash system system.img_sparsechunk.4
target max-sparse-size: 256MB
sending 'system' (262141 KB)...
OKAY [ 7.507s]
writing 'system'...
(bootloader) Invalid partition name system
FAILED (remote failure)
finished. total time: 7.530s
C:\adb\mfastboot-v2>mfastboot flash system system.img_sparsechunk.5
target max-sparse-size: 256MB
sending 'system' (262141 KB)...
OKAY [ 7.504s]
writing 'system'...
(bootloader) Invalid partition name system
FAILED (remote failure)
finished. total time: 7.524s
C:\adb\mfastboot-v2>mfastboot flash system system.img_sparsechunk.6
target max-sparse-size: 256MB
sending 'system' (250531 KB)...
OKAY [ 7.203s]
writing 'system'...
(bootloader) Invalid partition name system
FAILED (remote failure)
finished. total time: 7.232s
C:\adb\mfastboot-v2>mfastboot flash system system.img_sparsechunk.7
target max-sparse-size: 256MB
sending 'system' (262059 KB)...
OKAY [ 7.509s]
writing 'system'...
(bootloader) Invalid partition name system
FAILED (remote failure)
finished. total time: 7.538s
C:\adb\mfastboot-v2>mfastboot flash system system.img_sparsechunk.8
target max-sparse-size: 256MB
sending 'system' (254142 KB)...
OKAY [ 7.289s]
writing 'system'...
(bootloader) Invalid partition name system
FAILED (remote failure)
finished. total time: 7.318s
C:\adb\mfastboot-v2>mfastboot flash boot boot.img
target max-sparse-size: 256MB
sending 'boot' (16384 KB)...
OKAY [ 0.496s]
writing 'boot'...
(bootloader) Invalid partition name boot
FAILED (remote failure)
finished. total time: 0.522s
C:\adb\mfastboot-v2>mfastboot flash recovery recovery.img
target max-sparse-size: 256MB
sending 'recovery' (20580 KB)...
OKAY [ 0.614s]
writing 'recovery'...
(bootloader) Invalid partition name recovery
FAILED (remote failure)
finished. total time: 0.643s
C:\adb\mfastboot-v2>fastboot erase cache
erasing 'cache'...
(bootloader) Permission denied
FAILED (remote failure)
finished. total time: 0.022s
C:\adb\mfastboot-v2>fastboot erase userdata
erasing 'userdata'...
(bootloader) Permission denied
FAILED (remote failure)
finished. total time: 0.038s
C:\adb\mfastboot-v2>mfastboot reboot
rebooting...
finished. total time: 0.006s
C:\adb\mfastboot-v2>mfastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: moto-msm8953-C0.C5(*)
(bootloader) product: potter
(bootloader) board: potter
(bootloader) secure: yes
(bootloader) hwrev: P3B
(bootloader) radio: 1
(bootloader) storage-type: emmc
(bootloader) emmc: 32GB SKHYNIX HBG4a2 RV=08 PV=A5 FV=00000000000000A5
(bootloader) ram: 2GB SKHYNIX LP3 DIE=8Gb M5=06 M6=03 M7=00 M8=1F
(bootloader) cpu: MSM8953
(bootloader) serialno: a58c134
(bootloader) cid: 0xDEAD
(bootloader) channelid: 0x00
(bootloader) uid: 0000000000000000000000000000
(bootloader) securestate: oem_locked
(bootloader) iswarrantyvoid: n/a
(bootloader) max-download-size: 536870912
(bootloader) reason: Failed to initialize partition table
(bootloader) imei: 000000000000000
(bootloader) meid:
(bootloader) date: 01-01-1970
(bootloader) sku: 000000000000000
(bootloader) battid:
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time:
(bootloader) ro.build.fingerprint:
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full:
(bootloader) ro.build.version.qcom:
(bootloader) version-baseband:
(bootloader) kernel.version:
(bootloader) sbl1.git: sbl1.git
(bootloader) rpm.git: rpm.git
(bootloader) tz.git: tz.git
(bootloader) devcfg.git: devcfg.git
(bootloader) keymaster.git: keymaster.git
(bootloader) cmnlib.git: cmnlib.git
(bootloader) cmnlib64.git: cmnlib64.git
(bootloader) prov.git: prov.git
(bootloader) aboot.git: git=MBM-NG-VC0.C5-0-g99aa1c1
(bootloader) qe:
(bootloader) frp-state: no protection (err)
(bootloader) ro.carrier:
all: listed above
finished. total time: 0.152s
I will try to uninstall all drivers and try again, just in case, but if you see anything else, let me know! I really appreciate your help!
Glencoe said:
I am from Canada, and my carrier is Videotron, though we bougth the (unlocked) phone from Target, in the US, so I'd think the channel may be RetUS indeed.
I should have mentioned I had already tried it, and it didn't work indeed. Just checked again, and all it says is "Failed to match the connected device..."
I followed your guide (my, I realise you are a guru on here!), and tried flashing with mfastboot (while sending each system.img chunck separately, as I have 8 system.img_sparsechunck.* files)... Looks like it failed again!
This is what I get from the Command prompt:
C:\adb\mfastboot-v2>mfastboot devices
a58c134 fastboot
C:\adb\mfastboot-v2>mfastboot flash modem NON-HLOS.bin
target max-sparse-size: 256MB
sending 'modem' (71921 KB)...
OKAY [ 2.055s]
writing 'modem'...
(bootloader) Invalid partition name modem
FAILED (remote failure)
finished. total time: 2.076s
C:\adb\mfastboot-v2>mfastboot erase modemst1
erasing 'modemst1'...
(bootloader) Permission denied
FAILED (remote failure)
finished. total time: 0.022s
C:\adb\mfastboot-v2>mfastboot erase modemst2
erasing 'modemst2'...
(bootloader) Permission denied
FAILED (remote failure)
finished. total time: 0.010s
C:\adb\mfastboot-v2>mfastboot flash system system.img_sparsechunk.0
target max-sparse-size: 256MB
sending 'system' (258396 KB)...
OKAY [ 7.375s]
writing 'system'...
(bootloader) Invalid partition name system
FAILED (remote failure)
finished. total time: 7.388s
C:\adb\mfastboot-v2>mfastboot flash system system.img_sparsechunk.1
target max-sparse-size: 256MB
sending 'system' (256514 KB)...
OKAY [ 7.375s]
writing 'system'...
(bootloader) Invalid partition name system
FAILED (remote failure)
finished. total time: 7.399s
C:\adb\mfastboot-v2>mfastboot flash system system.img_sparsechunk.2
target max-sparse-size: 256MB
sending 'system' (246302 KB)...
OKAY [ 7.090s]
writing 'system'...
(bootloader) Invalid partition name system
FAILED (remote failure)
finished. total time: 7.104s
C:\adb\mfastboot-v2>mfastboot flash system system.img_sparsechunk.3
target max-sparse-size: 256MB
sending 'system' (262141 KB)...
OKAY [ 7.494s]
writing 'system'...
(bootloader) Invalid partition name system
FAILED (remote failure)
finished. total time: 7.518s
C:\adb\mfastboot-v2>mfastboot flash system system.img_sparsechunk.4
target max-sparse-size: 256MB
sending 'system' (262141 KB)...
OKAY [ 7.507s]
writing 'system'...
(bootloader) Invalid partition name system
FAILED (remote failure)
finished. total time: 7.530s
C:\adb\mfastboot-v2>mfastboot flash system system.img_sparsechunk.5
target max-sparse-size: 256MB
sending 'system' (262141 KB)...
OKAY [ 7.504s]
writing 'system'...
(bootloader) Invalid partition name system
FAILED (remote failure)
finished. total time: 7.524s
C:\adb\mfastboot-v2>mfastboot flash system system.img_sparsechunk.6
target max-sparse-size: 256MB
sending 'system' (250531 KB)...
OKAY [ 7.203s]
writing 'system'...
(bootloader) Invalid partition name system
FAILED (remote failure)
finished. total time: 7.232s
C:\adb\mfastboot-v2>mfastboot flash system system.img_sparsechunk.7
target max-sparse-size: 256MB
sending 'system' (262059 KB)...
OKAY [ 7.509s]
writing 'system'...
(bootloader) Invalid partition name system
FAILED (remote failure)
finished. total time: 7.538s
C:\adb\mfastboot-v2>mfastboot flash system system.img_sparsechunk.8
target max-sparse-size: 256MB
sending 'system' (254142 KB)...
OKAY [ 7.289s]
writing 'system'...
(bootloader) Invalid partition name system
FAILED (remote failure)
finished. total time: 7.318s
C:\adb\mfastboot-v2>mfastboot flash boot boot.img
target max-sparse-size: 256MB
sending 'boot' (16384 KB)...
OKAY [ 0.496s]
writing 'boot'...
(bootloader) Invalid partition name boot
FAILED (remote failure)
finished. total time: 0.522s
C:\adb\mfastboot-v2>mfastboot flash recovery recovery.img
target max-sparse-size: 256MB
sending 'recovery' (20580 KB)...
OKAY [ 0.614s]
writing 'recovery'...
(bootloader) Invalid partition name recovery
FAILED (remote failure)
finished. total time: 0.643s
C:\adb\mfastboot-v2>fastboot erase cache
erasing 'cache'...
(bootloader) Permission denied
FAILED (remote failure)
finished. total time: 0.022s
C:\adb\mfastboot-v2>fastboot erase userdata
erasing 'userdata'...
(bootloader) Permission denied
FAILED (remote failure)
finished. total time: 0.038s
C:\adb\mfastboot-v2>mfastboot reboot
rebooting...
finished. total time: 0.006s
C:\adb\mfastboot-v2>mfastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: moto-msm8953-C0.C5(*)
(bootloader) product: potter
(bootloader) board: potter
(bootloader) secure: yes
(bootloader) hwrev: P3B
(bootloader) radio: 1
(bootloader) storage-type: emmc
(bootloader) emmc: 32GB SKHYNIX HBG4a2 RV=08 PV=A5 FV=00000000000000A5
(bootloader) ram: 2GB SKHYNIX LP3 DIE=8Gb M5=06 M6=03 M7=00 M8=1F
(bootloader) cpu: MSM8953
(bootloader) serialno: a58c134
(bootloader) cid: 0xDEAD
(bootloader) channelid: 0x00
(bootloader) uid: 0000000000000000000000000000
(bootloader) securestate: oem_locked
(bootloader) iswarrantyvoid: n/a
(bootloader) max-download-size: 536870912
(bootloader) reason: Failed to initialize partition table
(bootloader) imei: 000000000000000
(bootloader) meid:
(bootloader) date: 01-01-1970
(bootloader) sku: 000000000000000
(bootloader) battid:
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time:
(bootloader) ro.build.fingerprint:
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full:
(bootloader) ro.build.version.qcom:
(bootloader) version-baseband:
(bootloader) kernel.version:
(bootloader) sbl1.git: sbl1.git
(bootloader) rpm.git: rpm.git
(bootloader) tz.git: tz.git
(bootloader) devcfg.git: devcfg.git
(bootloader) keymaster.git: keymaster.git
(bootloader) cmnlib.git: cmnlib.git
(bootloader) cmnlib64.git: cmnlib64.git
(bootloader) prov.git: prov.git
(bootloader) aboot.git: git=MBM-NG-VC0.C5-0-g99aa1c1
(bootloader) qe:
(bootloader) frp-state: no protection (err)
(bootloader) ro.carrier:
all: listed above
finished. total time: 0.152s
I will try to uninstall all drivers and try again, just in case, but if you see anything else, let me know! I really appreciate your help!
Click to expand...
Click to collapse
Well I'm not hopeful.
You could try
Code:
mfastboot oem fb_mode_set
mfastboot flash partition gpt.bin
mfastboot flash bootloader bootloader.img
mfastboot flash logo logo.bin
mfastboot flash boot boot.img
Sent from my jerry_cheets using XDA Labs
sd_shadow said:
Well I'm not hopeful.
You could try
Code:
mfastboot oem fb_mode_set
mfastboot flash partition gpt.bin
mfastboot flash bootloader bootloader.img
mfastboot flash logo logo.bin
mfastboot flash boot boot.img
Click to expand...
Click to collapse
This is something I had already tried... Without luck!
C:\adb\mfastboot-v2>mfastboot oem fb_mode_set
...
FAILED (remote failure)
finished. total time: 0.006s
C:\adb\mfastboot-v2>mfastboot flash partition gpt.bin
target max-sparse-size: 256MB
sending 'partition' (45 KB)...
OKAY [ 0.025s]
writing 'partition'...
(bootloader) Validating 'gpt.default.xml'
(bootloader) Image primary_gpt failed validation
(bootloader) Preflash validation failed
(bootloader) Cancelling 'gpt.default.xml'
FAILED (remote failure)
finished. total time: 0.137s
C:\adb\mfastboot-v2>mfastboot flash bootloader bootloader.img
target max-sparse-size: 256MB
sending 'bootloader' (5115 KB)...
OKAY [ 0.153s]
writing 'bootloader'...
(bootloader) Validating 'bootloader.default.xml'
(bootloader) Invalid partition name aboot
(bootloader) Invalid partition name rpm
(bootloader) Invalid partition name tz
(bootloader) Invalid partition name devcfg
(bootloader) Invalid partition name cmnlib
(bootloader) Invalid partition name cmnlib64
(bootloader) Invalid partition name keymaster
(bootloader) Invalid partition name prov
(bootloader) Invalid partition name sbl1
(bootloader) Cancelling 'bootloader.default.xml'
FAILED (remote failure)
finished. total time: 0.284s
C:\adb\mfastboot-v2>mfastboot flash logo logo.bin
target max-sparse-size: 256MB
sending 'logo' (2186 KB)...
OKAY [ 0.084s]
writing 'logo'...
(bootloader) Invalid partition name logo
FAILED (remote failure)
finished. total time: 0.102s
C:\adb\mfastboot-v2>mfastboot flash boot boot.img
target max-sparse-size: 256MB
sending 'boot' (16384 KB)...
OKAY [ 0.496s]
writing 'boot'...
(bootloader) Invalid partition name boot
FAILED (remote failure)
finished. total time: 0.509s
Am I using the right firmware? I tried with the Potter RETUS 8.1.0...
Could it be that the bootloader is locked? If so, how do I unlock it?
Should I try to flash a blank file again? If so, how?
Or should I try to flash a bootable image on an SD card?
I am willing to try anything you can think of. This phone is already useless as is, so I have nothing to lose... I like challenges, but this one is very frustrating! But it is also a great learning experience!
Glencoe said:
T
Am I using the right firmware? I tried with the Potter RETUS 8.1.0...
Click to expand...
Click to collapse
I don't know, getvar isn't giving enough info to tell.
Do you remember where you found the blankflash?
Could you upload it somewhere? Drive, Mega, ...
Could it be that the bootloader is locked? If so, how do I unlock it?
Click to expand...
Click to collapse
bootloader is locked
Code:
(bootloader) securestate: oem_locked
Very unlikely you could unlock the bootloader as
OEM unlocking must be allowed in Dev options
which requires the phone to boot normally
but you could try
https://forum.xda-developers.com/general/rooting-roms/guide-locking-motorola-bootloader-t4079111
Should I try to flash a blank file again? If so, how?
Or should I try to flash a bootable image on an SD card?
Click to expand...
Click to collapse
Unfortunately, these are not options
The device needs to be in emergency download mode (edl)
There is no way to enter edl with a locked bootloader.
I am willing to try anything you can think of. This phone is already useless as is, so I have nothing to lose... I like challenges, but this one is very frustrating! But it is also a great learning experience!
Click to expand...
Click to collapse
sd_shadow said:
I don't know, getvar isn't giving enough info to tell.
Do you remember where you found the blankflash?
Could you upload it somewhere? Drive, Mega, ....
Click to expand...
Click to collapse
I don't actually remember where I got the blankflash, but I know I have 2 files, and I think I used the wrong one (XT1686)... Maybe that's the issue...
Those are the 2 files I have:
Don't remember, possibly XT1687: https://drive.google.com/file/d/1A5fpqO6tVSGJfQynwjlDex0LS4-yuMm9/view?usp=sharing
XT1686: https://drive.google.com/file/d/19pa9aR0j110Yk07wdwQ-AY-yHoH0nvw0/view?usp=sharing
Let me know what you think! If you have a better version, I am willing to try, if there is still a way to flash it...
sd_shadow said:
bootloader is locked
Code:
(bootloader) securestate: oem_locked
Click to expand...
Click to collapse
That's what I thought...
sd_shadow said:
Very unlikely you could unlock the bootloader as
OEM unlocking must be allowed in Dev options
which requires the phone to boot normally
but you could try
https://forum.xda-developers.com/general/rooting-roms/guide-locking-motorola-bootloader-t4079111
Click to expand...
Click to collapse
I'll give it a try!
sd_shadow said:
Unfortunately, these are not options
The device needs to be in emergency download mode (edl)
There is no way to enter edl with a locked bootloader.
Click to expand...
Click to collapse
In other words, there is no much hope to revive it...
Glencoe said:
I don't actually remember where I got the blankflash, but I know I have 2 files, and I think I used the wrong one (XT1686)... Maybe that's the issue...
Those are the 2 files I have:
Don't remember, possibly XT1687: https://drive.google.com/file/d/1A5fpqO6tVSGJfQynwjlDex0LS4-yuMm9/view?usp=sharing
XT1686: https://drive.google.com/file/d/19pa9aR0j110Yk07wdwQ-AY-yHoH0nvw0/view?usp=sharing
Let me know what you think! If you have a better version, I am willing to try, if there is still a way to flash it...
That's what I thought...
I'll give it a try!
In other words, there is no much hope to revive it...
Click to expand...
Click to collapse
I guess you could try RetIN I think it's the only XT1686 firmware
https://mirrors.lolinet.com/firmware/moto/potter/official/RETIN/
sd_shadow said:
I guess you could try RetIN I think it's the only XT1686 firmware
https://mirrors.lolinet.com/firmware/moto/potter/official/RETIN/
Click to expand...
Click to collapse
Really? Knowing my phone is XT1687? Or should I try it if I flashed the XT1686 blankflash?
Glencoe said:
Really? Knowing my phone is XT1687? Or should I try it if I flashed the XT1686 blankflash?
Click to expand...
Click to collapse
At this point I don't think it will hurt anything.
Sent from my ali using XDA Labs
sd_shadow said:
At this point I don't think it will hurt anything.
Click to expand...
Click to collapse
You're right! But I will try you other suggestion to unlock first and see how it goes (hopefully later today). Will let you know the outcome! Thanks for helping me! I really appreciate it!
Soft brick after trying to root g5 plus. Have recovery installed and working, and initially installed no-verify-opt-encrypt-5.1.zip ->reboot and install magisk-v11.6.zip with no root success. I downloaded newer versions of both 6.1 and 20.4 respectively, and now it is frozen at "Your device has been unlocked and can't be trusted" . Good news, I can still get into recovery.
jayray1 said:
Soft brick after trying to root g5 plus. Have recovery installed and working, and initially installed no-verify-opt-encrypt-5.1.zip ->reboot and install magisk-v11.6.zip with no root success. I downloaded newer versions of both 6.1 and 20.4 respectively, and now it is frozen at "Your device has been unlocked and can't be trusted" . Good news, I can still get into recovery.
Click to expand...
Click to collapse
Flash Magisk uninstaller from here: https://github.com/topjohnwu/Magisk/releases/tag/v20.4
(releases, tap on assets).
Flash it through TWRP and reboot. When your device is running again flash Magisk 20.4 again without flashing any older version before. Should work that way.
I ran the uninstaller, but it gives an error "Cannot access /data, please uninstall with Magisk manager" and still no boot. Thank you for the help!
jayray1 said:
I ran the uninstaller, but it gives an error "Cannot access /data, please uninstall with Magisk manager" and still no boot. Thank you for the help!
Click to expand...
Click to collapse
So your data partition seems to be encrypted.
Here are some tips:
https://www.didgeridoohan.com/magisk/MagiskUninstallIssues#
Possible solutions:
Try one of the following:
Restore your stock boot image (there's a copy of it stored in /data, named stock_boot_<sha1>.img.gz).
Flash a no-verity zip directly after uninstalling Magisk/restoring your stock boot image.
Dirty flash your ROM/factory image/firmware package.
Clean flash your ROM/factory image/firmware package.
It's also possible that a previous version of the uninstaller zip works, if the current one doesn't. You'll find earlier releases on GitHub.
First I would try to restore your stock boot image (beside the stored one in data that you maybe can't reach because of the encryption you can use the boot.img found inside your actual firmware), unzip it from the firmware. It has to be the one you're running.
Firmwares can be found here:https://mirrors.lolinet.com/firmware/moto/potter/official/RETAIL/
I'll just ask the easy question. I'm trying to DD out the data partition so I can recover lost photos since the phone was reset at the store. Is that possible? If so whats the ez way to do that, idc if the phone boots in a usable state otherwise.
jayray1 said:
I'll just ask the easy question. I'm trying to DD out the data partition so I can recover lost photos since the phone was reset at the store. Is that possible? If so whats the ez way to do that, idc if the phone boots in a usable state otherwise.
Click to expand...
Click to collapse
If the device has been reset completely (and that's what they do in the store) there's no way to save anything. As the /data partition is encrypted there's also no way to get access to it. Flashing signed firmware seems to be the only way to get the device running again.
I guess I need to just wipe it back to a factory image. How do I know which one I need since I cant boot it and check. And is this the best method? https://www.the***********.com/restore-stock-firmware-on-moto-devices/
jayray1 said:
I guess I need to just wipe it back to a factory image. How do I know which one I need since I cant boot it and check. And is this the best method? https://www.the***********.com/restore-stock-firmware-on-moto-devices/
Click to expand...
Click to collapse
Here you should find all information you need:
https://forum.xda-developers.com/g5...solve-imei0-explanation-t3825147/post80478329
As you don't know which firmware you were running last I recommend to use the latest one released by Motorola (as written in the tutorial, 8.1.0_OPS28.85-17-6-2). Than it depends on your location if it's retin (India), reteu (Europe), retus (United States) or any other. All versions are linked there.
The 2nd part is about rooting and decrypting.
Got it back to factory boot, but have a few messages about bad key. How do I relock and have it 100% back to factory? Do I just "fastboot oem lock" at the end before reboot in the script? Below is output
Code:
./flashallO.sh
OKAY [ 0.001s]
Finished. Total time: 0.002s
(bootloader) is-logical:partition: not found
Sending 'partition' (45 KB) OKAY [ 0.170s]
Writing 'partition' (bootloader) Validating 'gpt.default.xml'
(bootloader) Committing 'gpt.default.xml'
(bootloader) - flashing 'gpt_main0.bin' to 'partition:0'
(bootloader) Flashing primary GPT image...
(bootloader) Flashing backup GPT image...
OKAY [ 0.078s]
Finished. Total time: 0.248s
(bootloader) is-logical:bootloader: not found
Sending 'bootloader' (5115 KB) OKAY [ 0.300s]
Writing 'bootloader' (bootloader) Validating 'bootloader.default.xml'
(bootloader) Committing 'bootloader.default.xml'
(bootloader) - flashing 'emmc_appsboot.mbn' to 'aboot'
(bootloader) - flashing 'rpm.mbn' to 'rpm'
(bootloader) - flashing 'tz.mbn' to 'tz'
(bootloader) - flashing 'devcfg.mbn' to 'devcfg'
(bootloader) - flashing 'cmnlib.mbn' to 'cmnlib'
(bootloader) - flashing 'cmnlib64.mbn' to 'cmnlib64'
(bootloader) - flashing 'keymaster.mbn' to 'keymaster'
(bootloader) - flashing 'prov.mbn' to 'prov'
(bootloader) - flashing 'sbl1.mbn' to 'sbl1'
OKAY [ 0.554s]
Finished. Total time: 0.855s
(bootloader) is-logical:modem: not found
Sending 'modem' (71921 KB) OKAY [ 1.955s]
Writing 'modem' OKAY [ 1.089s]
Finished. Total time: 3.047s
(bootloader) is-logical:fsg: not found
Sending 'fsg' (3012 KB) OKAY [ 0.244s]
Writing 'fsg' OKAY [ 0.119s]
Finished. Total time: 0.364s
Erasing 'modemst1' OKAY [ 0.034s]
Finished. Total time: 0.034s
Erasing 'modemst2' OKAY [ 0.034s]
Finished. Total time: 0.034s
(bootloader) is-logical:dsp: not found
Sending 'dsp' (16384 KB) OKAY [ 0.577s]
Writing 'dsp' OKAY [ 0.280s]
Finished. Total time: 0.858s
(bootloader) is-logical:logo: not found
Sending 'logo' (2186 KB) OKAY [ 0.224s]
Writing 'logo' OKAY [ 0.116s]
Finished. Total time: 0.340s
(bootloader) is-logical:boot: not found
Sending 'boot' (16384 KB) OKAY [ 0.600s]
Writing 'boot' (bootloader) Image signed with key bad key
OKAY [ 0.378s]
Finished. Total time: 0.979s
(bootloader) is-logical:recovery: not found
Sending 'recovery' (20580 KB) OKAY [ 0.690s]
Writing 'recovery' (bootloader) Image signed with key bad key
OKAY [ 0.481s]
Finished. Total time: 1.172s
(bootloader) is-logical:system: not found
Sending 'system' (258396 KB) OKAY [ 6.581s]
Writing 'system' OKAY [ 3.730s]
Finished. Total time: 10.313s
(bootloader) is-logical:system: not found
Sending 'system' (256514 KB) OKAY [ 6.543s]
Writing 'system' OKAY [ 3.332s]
Finished. Total time: 9.877s
(bootloader) is-logical:system: not found
Sending 'system' (246302 KB) OKAY [ 6.347s]
Writing 'system' OKAY [ 3.631s]
Finished. Total time: 9.985s
(bootloader) is-logical:system: not found
Sending 'system' (262141 KB) OKAY [ 6.670s]
Writing 'system' OKAY [ 3.350s]
Finished. Total time: 10.022s
(bootloader) is-logical:system: not found
Sending 'system' (262141 KB) OKAY [ 6.679s]
Writing 'system' OKAY [ 3.421s]
Finished. Total time: 10.104s
(bootloader) is-logical:system: not found
Sending 'system' (262141 KB) OKAY [ 6.686s]
Writing 'system' OKAY [ 3.323s]
Finished. Total time: 10.011s
(bootloader) is-logical:system: not found
Sending 'system' (250531 KB) OKAY [ 6.416s]
Writing 'system' OKAY [ 3.666s]
Finished. Total time: 10.089s
(bootloader) is-logical:system: not found
Sending 'system' (262059 KB) OKAY [ 6.693s]
Writing 'system' OKAY [ 3.740s]
Finished. Total time: 10.444s
(bootloader) is-logical:system: not found
Sending 'system' (254142 KB) OKAY [ 6.485s]
Writing 'system' OKAY [ 3.301s]
Finished. Total time: 9.789s
(bootloader) is-logical:oem: not found
Sending 'oem' (104608 KB) OKAY [ 2.766s]
Writing 'oem' OKAY [ 1.373s]
Finished. Total time: 4.143s
Erasing 'cache' OKAY [ 0.019s]
Finished. Total time: 0.019s
Erasing 'userdata' OKAY [ 0.185s]
Finished. Total time: 0.185s
Erasing 'DDR' OKAY [ 0.002s]
Finished. Total time: 0.003s
OKAY [ 0.001s]
Finished. Total time: 0.002s
Rebooting OKAY [ 0.000s]
Finished. Total time: 0.151s
jayray1 said:
Got it back to factory boot, but have a few messages about bad key. How do I relock and have it 100% back to factory? Do I just "fastboot oem lock" at the end before reboot in the script? Below is output
Click to expand...
Click to collapse
If it says bad key don't lock it.
What does getvar all say?
Code:
fastboot getvar all
Code:
(bootloader) version: 0.5
(bootloader) version-bootloader: moto-msm8953-C0.92
(bootloader) product: potter
(bootloader) board: potter
(bootloader) secure: yes
(bootloader) hwrev: P3B
(bootloader) radio: 1
(bootloader) storage-type: emmc
(bootloader) emmc: 32GB SAMSUNG QX13MB RV=08 PV=07 FV=0000000000000007
(bootloader) ram: 2GB SAMSUNG LP3 DIE=8Gb M5=01 M6=05 M7=00 M8=1F
(bootloader) cpu: MSM8953
(bootloader) serialno: ZY223ZQBWJ
(bootloader) cid: 0x0032
(bootloader) channelid: 0x8d
(bootloader) uid: 8A7144F900000000000000000000
(bootloader) securestate: flashing_unlocked
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 534773760
(bootloader) reason: Volume down key pressed
(bootloader) imei: 351856080531619
(bootloader) meid:
(bootloader) date: 03-10-2017
(bootloader) sku: XT1687
(bootloader) carrier_sku:
(bootloader) battid:
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Sat Jan 24 8:15:41 UTC 1970"
(bootloader) ro.build.fingerprint[0]: motorola/potter/potter:8.1.0/OPS28
(bootloader) ro.build.fingerprint[1]: .85-17-6-2/77e7:user/release-keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.28.261.2.potter.reta
(bootloader) ro.build.version.full[1]: il.en.US
(bootloader) ro.build.version.qcom: LA.UM.6.6.r1-08600-89xx.0
(bootloader) version-baseband: M8953_46.55.07.90R POTTER_NA_CUST
(bootloader) kernel.version[0]: Linux version 3.18.71-perf-g7b625a0 (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 Mon Mar 4 14:31:59 CST 2019
(bootloader) sbl1.git: git=MBM-NG-VC0.92-0-gd009c3b
(bootloader) rpm.git: git=92e5e21-dirty
(bootloader) tz.git: git=27e6e4b-dirty
(bootloader) devcfg.git: git=27e6e4b-dirty
(bootloader) keymaster.git: git=27e6e4b-dirty
(bootloader) cmnlib.git: git=27e6e4b-dirty
(bootloader) cmnlib64.git: git=27e6e4b-dirty
(bootloader) prov.git: git=27e6e4b-dirty
(bootloader) aboot.git: git=MBM-NG-VC0.92-0-g3ea8df0
(bootloader) frp-state: no protection (0)
(bootloader) ro.carrier: retus
(bootloader) current-slot:
(bootloader) slot-suffixes: _a
(bootloader) slot-count: 1
(bootloader) slot-successful:_a: INVALID
(bootloader) slot-successful:_b: INVALID
(bootloader) slot-bootable:_a: INVALID
(bootloader) slot-bootable:_b: INVALID
(bootloader) slot-retry-count:_a: unknown
(bootloader) slot-retry-count:_b: unknown
all: listed above
Finished. Total time: 0.007s
[[email protected] fw]$ fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: moto-msm8953-C0.92
(bootloader) product: potter
(bootloader) board: potter
(bootloader) secure: yes
(bootloader) hwrev: P3B
(bootloader) radio: 1
(bootloader) storage-type: emmc
(bootloader) emmc: 32GB SAMSUNG QX13MB RV=08 PV=07 FV=0000000000000007
(bootloader) ram: 2GB SAMSUNG LP3 DIE=8Gb M5=01 M6=05 M7=00 M8=1F
(bootloader) cpu: MSM8953
(bootloader) serialno: ZY223ZQBWJ
(bootloader) cid: 0x0032
(bootloader) channelid: 0x8d
(bootloader) uid: 8A7144F900000000000000000000
(bootloader) securestate: flashing_unlocked
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 534773760
(bootloader) reason: Volume down key pressed
(bootloader) imei: 351856080531619
(bootloader) meid:
(bootloader) date: 03-10-2017
(bootloader) sku: XT1687
(bootloader) carrier_sku:
(bootloader) battid:
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Sat Jan 24 8:15:46 UTC 1970"
(bootloader) ro.build.fingerprint[0]: motorola/potter/potter:8.1.0/OPS28
(bootloader) ro.build.fingerprint[1]: .85-17-6-2/77e7:user/release-keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.28.261.2.potter.reta
(bootloader) ro.build.version.full[1]: il.en.US
(bootloader) ro.build.version.qcom: LA.UM.6.6.r1-08600-89xx.0
(bootloader) version-baseband: M8953_46.55.07.90R POTTER_NA_CUST
(bootloader) kernel.version[0]: Linux version 3.18.71-perf-g7b625a0 (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 Mon Mar 4 14:31:59 CST 2019
(bootloader) sbl1.git: git=MBM-NG-VC0.92-0-gd009c3b
(bootloader) rpm.git: git=92e5e21-dirty
(bootloader) tz.git: git=27e6e4b-dirty
(bootloader) devcfg.git: git=27e6e4b-dirty
(bootloader) keymaster.git: git=27e6e4b-dirty
(bootloader) cmnlib.git: git=27e6e4b-dirty
(bootloader) cmnlib64.git: git=27e6e4b-dirty
(bootloader) prov.git: git=27e6e4b-dirty
(bootloader) aboot.git: git=MBM-NG-VC0.92-0-g3ea8df0
(bootloader) frp-state: no protection (0)
(bootloader) ro.carrier: retus
(bootloader) current-slot:
(bootloader) slot-suffixes: _a
(bootloader) slot-count: 1
(bootloader) slot-successful:_a: INVALID
(bootloader) slot-successful:_b: INVALID
(bootloader) slot-bootable:_a: INVALID
(bootloader) slot-bootable:_b: INVALID
(bootloader) slot-retry-count:_a: unknown
(bootloader) slot-retry-count:_b: unknown
all: listed above
Finished. Total time: 0.008s
Did you use RetUS firmware?
Sent from my ali using XDA Labs
I did, XT1687_POTTER_RETUS_8.1.0_OPS28.85-17-6-2_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
jayray1 said:
I did, XT1687_POTTER_RETUS_8.1.0_OPS28.85-17-6-2_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
Click to expand...
Click to collapse
You could try LMSA Flash Rescue option
Connect device to PC while in fastboot mode.
And see which firmware it wants to download/install.
Sent from my ali using XDA Labs
I'll have to get back to you on that.. no windows pc. any other options?
jayray1 said:
I'll have to get back to you on that.. no windows pc. any other options?
Click to expand...
Click to collapse
The bad key should be just a warning that the boot.img signature was missing/corrupted/ mismatched.
Does it work otherwise?
Sent from my ali using XDA Labs
no, now after flash it is booting to "no command" on a recovery background
jayray1 said:
no, now after flash it is booting to "no command" on a recovery background
Click to expand...
Click to collapse
Hold the Power button, then press and release the Volume Up button to display the recovery menu options.
Sent from my Moto E (4) using Tapatalk
jayray1 said:
no, now after flash it is booting to "no command" on a recovery background
Click to expand...
Click to collapse
For me it seems you need the RETLA (Latin America) firmware and not RETUS. Is your location Brasil?
If yes and you don't have access to a Windows machine I would try to flash that firmware. Couldn't make it worse in my opinion.
https://mirrors.lolinet.com/firmware/moto/potter/official/RETLA/