Hi, Guys.
I have the following problem:
My watch is with stock international 2.3.9.0.
I've tried to install STRATOSfied v28, but the recovery file from https://gitlab.com/Neuer_User/PACEfied_AmazFit/wikis/permanent-install isn't working as it is expected.
The watch reboots, but the "#" sign is not available in the adb shell.
Also it gaves an error in fastboot mode (fastboot boot recovery.img(whatever the name is).
too many links, FAILED etc...
So i have Ubuntu18.10 and windows10 - no difference in both OS. Also I've tried on separated laptop (windows 10 again) with no positive effect.
Before 2.3.9.0 i was with version 26 and some previous ones (by permanent install, not only update via "sh" script in the shell) - No problems with all previous versions i've tested
So.. maybe there is a new bootloader and it needs a new recovery to temporary root the device. I don't know, but the normal installation isn't working anymore, so I've flashed clean 2.3.9.0 via Fastboot and I am staying in Stock ROM until something is changed.
Thank you if you have solution of this. I'll try it
post your fastboot getvar all output
1immortal said:
post your fastboot getvar all output
Click to expand...
Click to collapse
(bootloader) version-bootloader: U-Boot 2013.07-00146-g43d9f8c
(bootloader) version-baseband: N/A
(bootloader) version-hardware: V1.1 20130322
(bootloader) version-cdma: N/A
(bootloader) variant: watch
(bootloader) serialno: 16191828090306
(bootloader) product: watch
(bootloader) secure: no
(bootloader) unlocked: yes
(bootloader) uart-on: NO
(bootloader) partition-size:bootloader: 0x0000
(bootloader) partition-type:bootloader: emmc
(bootloader) partition-size:recovery: 0x1000
(bootloader) partition-type:recovery: emmc
(bootloader) partition-size:boot: 0x2000
(bootloader) partition-type:boot: emmc
(bootloader) partition-size:system: 0x3000
(bootloader) partition-type:system: ext4
(bootloader) partition-size:cache: 0x4000
(bootloader) partition-type:cache: ext4
(bootloader) partition-size:userdata: 0x5000
(bootloader) partition-type:userdata: ext4
(bootloader) max-download-size: 0x4000000
Related
Guys please help... I'm desperate right now...
My father got an AT&T Moto E, I tried to flash 6.0 on it, The bootloader.img file flashed but nothing else flashed from that 6.0 firmwaRE.
I realised AT&T wont allow us to do that so I left the phone on 5.1...
Today, a security patch update dropped for the phone... I insalled it but it turned off and it can't boot anymore.
I can enter bootloader and use fastboot commands, but when I try to flash the stock firmware from AT&T using fastboot it says
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
and the bootloader log says
Invalid PIV signed system image
It seems to be a problem with signature verification or something related to it...
Im trying to flash this fitmware: SURNIA_ATT_5.1_LPI23.29-18.9-2_cid1_subsidy-ATT_CFC.xml.zip which is the last one available for this AT&T variant.
So, is there a way to flash this AT&T variant? I also tried RSD Lite but no success on recognizing the phone..
Any help will be appreciated... thanks in advance..
What is running on your XT1527 now (stock/factory rom 5.1 compatible for AT&T) ?? Bootloader status ?
One of my SIL has this and I just updated her's with the latest update, download OTA and just flashed/upgraded directly, took about 20 minutes - easy & didn't have any issues with it at all, nothing (as described). She is on T-Mobile and all is good.
Backup all important data & contents, especially those on the mSD card/storage partition, be sure to do a full wipe/factory reset before trying the upgrade. If necessary, do a basic setup as a new device, wait a little while for everything to be updated & settle down, reboot it for good measures & then do the system check for upgrade.
Of course, my own XT1521 not getting this & running Nougat 7.1.1 nicely - unlike the XT1527 that can't be rooted to run custom Rom's.
Letitride said:
What is running on your XT1527 now (stock/factory rom 5.1 compatible for AT&T) ?? Bootloader status ?
One of my SIL has this and I just updated her's with the latest update, download OTA and just flashed/upgraded directly, took about 20 minutes - easy & didn't have any issues with it at all, nothing (as described). She is on T-Mobile and all is good.
Backup all important data & contents, especially those on the mSD card/storage partition, be sure to do a full wipe/factory reset before trying the upgrade. If necessary, do a basic setup as a new device, wait a little while for everything to be updated & settle down, reboot it for good measures & then do the system check for upgrade.
Of course, my own XT1521 not getting this & running Nougat 7.1.1 nicely - unlike the XT1527 that can't be rooted to run custom Rom's.
Click to expand...
Click to collapse
This device was on 5.1 stock... as it is from AT&T, bootloader is locked. I can enter fastboot mode, so it is not bricked, but when I try to reflash the latest AT&T firmware available for this phone it keeps saying that prevalidation error and invalid piv signed system image, even though I have the exact same firmware that was running before the OTA dropped...
As the AT&T webpage for XT1527 states, this is the OTA I accepted on the device:
Release date: December 16, 2016
Android version: 5.1
Baseband version: M8916_2020602.05.03.21.07R
Build number: LPI23.29-18.9-6
File size: 48.38MB
System version: 23.211.6.en.US
But when I run the command mfastboot getvar all, the phone shows it has the LPI23.29-18.9-2 build number installed! So, something went wrong during the update that corrupted (I guess) the kernel, because the device can't boot up normally. Just stays as it was off. It can access fastboot mode via vol down + power buttons. Also, when you plug it to the wall charger, it shows the offline charging screen, with the big battery icon and everything...
So, should I wait for the official AT&T firmware image for this OTA? Since I cant flash anything on it because of that prevalidation error crap!
LOG OF THE PHONE
C:\XT1527>mfastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: moto-msm8916-80.10
(bootloader) product: surnia
(bootloader) board: surnia
(bootloader) secure: yes
(bootloader) hwrev: 0x8300
(bootloader) radio: 0x1
(bootloader) emmc: 8GB Micron REV=06 PRV=12 TYPE=17
(bootloader) ram: 1024MB Elpida S8 SDRAM DIE=4Gb
(bootloader) cpu: MSM8916 ES1.0
(bootloader) serialno: TA3970BWQA
(bootloader) cid: 0x0001
(bootloader) channelid: 0x84
(bootloader) uid: A5D76A1500000000000000000000
(bootloader) securestate: locked
(bootloader) iswarrantyvoid: no
(bootloader) mot_sst: 0
(bootloader) max-download-size: 268435456
(bootloader) reason: Volume down key pressed
(bootloader) imei: Hidden
(bootloader) meid:
(bootloader) date: 01-09-2016
(bootloader) sku: XT1527
(bootloader) iccid: 89014103278783002002
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Wed Dec 16 20: 0: 5 UTC 2015"
(bootloader) ro.build.fingerprint[0]: motorola/surnia_att/surnia_umts:5.
(bootloader) ro.build.fingerprint[1]: 1/LPIS23.29-18.9-2/2:user/release-
(bootloader) ro.build.fingerprint[2]: keys
(bootloader) ro.build.version.full[0]: Blur_Version.23.201.2.surnia_att.
(bootloader) ro.build.version.full[1]: att.en.US
(bootloader) ro.build.version.qcom[0]: AU_LINUX_ANDROID_LA.BR.1.1.3_RB1.
(bootloader) ro.build.version.qcom[1]: 05.00.02.032.013
(bootloader) version-baseband[0]: M8916_2020602.05.03.21.07R SURNIA_ATT_
(bootloader) version-baseband[1]: CUST
(bootloader) kernel.version[0]: Linux version 3.10.49-gf2d7a94 (hudsoncm
(bootloader) kernel.version[1]: @ilclbld52) (gcc version 4.8 (GCC) ) #1
(bootloader) kernel.version[2]: SMP PREEMPT Mon Mar 28 02:49:46 CDT 2016
(bootloader) sbl1.git: git=MBM-NG-V80.10-0-g8f1d925
(bootloader) rpm.git: git=MBM-NG-V80.10-0-g099cb06
(bootloader) tz.git: git=MBM-NG-V80.10-0-g434e28a
(bootloader) hyp.git: git=MBM-NG-V80.10-0-g434e28a
(bootloader) aboot.git: git=MBM-NG-V80.10-0-g43dddc5
(bootloader) partition-type:modem: raw
(bootloader) partition-type:sbl1: raw
(bootloader) partition-typeDR: raw
(bootloader) partition-type:aboot: raw
(bootloader) partition-type:rpm: raw
(bootloader) partition-type:tz: raw
(bootloader) partition-type:hyp: raw
(bootloader) partition-type:utags: raw
(bootloader) partition-type:logs: raw
(bootloader) partition-type:sec: raw
(bootloader) partition-type:factorytune1: raw
(bootloader) partition-typeadA: raw
(bootloader) partition-type:metadata: raw
(bootloader) partition-type:abootBackup: raw
(bootloader) partition-type:rpmBackup: raw
(bootloader) partition-type:tzBackup: raw
(bootloader) partition-type:utagsBackup: raw
(bootloader) partition-type:hypBackup: raw
(bootloader) partition-typeadB: raw
(bootloader) partition-type:frp: raw
(bootloader) partition-type:modemst1: raw
(bootloader) partition-type:modemst2: raw
(bootloader) partition-type:hob: raw
(bootloader) partition-type:dhob: raw
(bootloader) partition-type:fsg: raw
(bootloader) partition-type:fsc: raw
(bootloader) partition-type:ssd: raw
(bootloader) partition-type:cid: raw
(bootloader) partition-type:logo: raw
(bootloader) partition-type:clogo: raw
(bootloader) partition-typeersist: raw
(bootloader) partition-type:misc: raw
(bootloader) partition-type:boot: raw
(bootloader) partition-type:recovery: raw
(bootloader) partition-type:factorytune2: raw
(bootloader) partition-type:kpan: raw
(bootloader) partition-typeadC: raw
(bootloader) partition-type:sp: raw
(bootloader) partition-type:keystore: raw
(bootloader) partition-typeem: raw
(bootloader) partition-type:carrier: ext4
(bootloader) partition-type:system: raw
(bootloader) partition-type:cache: raw
(bootloader) partition-type:userdata: raw
(bootloader) partition-size:modem: 0x0000000004000000
(bootloader) partition-size:sbl1: 0x0000000000080000
(bootloader) partition-sizeDR: 0x0000000000008000
(bootloader) partition-size:aboot: 0x0000000000100000
(bootloader) partition-size:rpm: 0x000000000003e800
(bootloader) partition-size:tz: 0x000000000007d000
(bootloader) partition-size:hyp: 0x0000000000020000
(bootloader) partition-size:utags: 0x0000000000080000
(bootloader) partition-size:logs: 0x0000000000200000
(bootloader) partition-size:sec: 0x0000000000004000
(bootloader) partition-size:factorytune1: 0x0000000000371000
(bootloader) partition-sizeadA: 0x00000000001af000
(bootloader) partition-size:metadata: 0x0000000000080000
(bootloader) partition-size:abootBackup: 0x0000000000100000
(bootloader) partition-size:rpmBackup: 0x000000000003e800
(bootloader) partition-size:tzBackup: 0x000000000007d000
(bootloader) partition-size:utagsBackup: 0x0000000000080000
(bootloader) partition-size:hypBackup: 0x0000000000020000
(bootloader) partition-sizeadB: 0x000000000048f000
(bootloader) partition-size:frp: 0x0000000000080000
(bootloader) partition-size:modemst1: 0x0000000000180000
(bootloader) partition-size:modemst2: 0x0000000000180000
(bootloader) partition-size:hob: 0x000000000007a000
(bootloader) partition-size:dhob: 0x0000000000008000
(bootloader) partition-size:fsg: 0x0000000000180000
(bootloader) partition-size:fsc: 0x0000000000000400
(bootloader) partition-size:ssd: 0x0000000000002000
(bootloader) partition-size:cid: 0x0000000000020000
(bootloader) partition-size:logo: 0x0000000000400000
(bootloader) partition-size:clogo: 0x0000000000400000
(bootloader) partition-sizeersist: 0x0000000000800000
(bootloader) partition-size:misc: 0x0000000000080000
(bootloader) partition-size:boot: 0x0000000002000000
(bootloader) partition-size:recovery: 0x0000000001ffc000
(bootloader) partition-size:factorytune2: 0x0000000000a0e000
(bootloader) partition-size:kpan: 0x0000000000800000
(bootloader) partition-sizeadC: 0x0000000000380000
(bootloader) partition-size:sp: 0x0000000001000000
(bootloader) partition-size:keystore: 0x0000000001000000
(bootloader) partition-sizeem: 0x0000000001000000
(bootloader) partition-size:carrier: 0x0000000001000000
(bootloader) partition-size:system: 0x0000000071000000
(bootloader) partition-size:cache: 0x0000000010000000
(bootloader) partition-size:userdata: 0x000000013ffe0000
(bootloader) qe: qe 0/0
(bootloader) ro.carrier: att
all: listed above
finished. total time: 0.275s
MarckozZ said:
This device was on 5.1 stock... as it is from AT&T, bootloader is locked. I can enter fastboot mode, so it is not bricked, but ...
So, should I wait for the official AT&T firmware image for this OTA? Since I cant flash anything on it because of that prevalidation error crap! ...
Click to expand...
Click to collapse
With the bootloader locked, there's not much you can do, whether the downloaded update is corrupted or not - not as easy to find & erase that "update" and start over. Wait for a newer OTA and then, cross your fingers & cycle thru the cautions & warnings; and, hit that "Go" or "Yes" bottom and hopefully the magic will take care of itself.
My SIL's XT1527 did fine with the AT&T update, and, she's on T-Mo USA network - so far so good, no complaints and just works.
Letitride said:
With the bootloader locked, there's not much you can do, whether the downloaded update is corrupted or not - not as easy to find & erase that "update" and start over. Wait for a newer OTA and then, cross your fingers & cycle thru the cautions & warnings; and, hit that "Go" or "Yes" bottom and hopefully the magic will take care of itself.
My SIL's XT1527 did fine with the AT&T update, and, she's on T-Mo USA network - so far so good, no complaints and just works.
Click to expand...
Click to collapse
Could you help me with something? Can you tell me which build number does her phone have right now? Go to Settings > About phone and please tell me the build number and build date under kernel version... And if you have time, use fastboot and /fastboot getvar all, so I can see the exact version... maybe that can help me figure this out! Thanks in advance...
Here's the link to the screenshot of her XT1527 after it updated - I took a screenshot afterward, just in case.
https://goo.gl/photos/38HQicN1bq6KzQoC8
It looked identical to what you have ?? Her Moto E is working just fine as I would've heard otherwise, (she's on T-Mobile) been a few days now. I won't get a chance to do anything or run those command until this Saturday when we gather. I suspect your download might've been corrupted and/or somehow one of the extracted file or those on the device had error.
So glad that mine (as a backup) is XT1521 and bootloader unlocked, now running custom Nougat 7.1.1 (ResurrectionRemix) and it's on T-Mobile also. Maybe time to look for one of these pre-owned ones on eBay.
Letitride said:
Here's the link to the screenshot of her XT1527 after it updated - I took a screenshot afterward, just in case.
https://goo.gl/photos/38HQicN1bq6KzQoC8
It looked identical to what you have ?? Her Moto E is working just fine as I would've heard otherwise, (she's on T-Mobile) been a few days now. I won't get a chance to do anything or run those command until this Saturday when we gather. I suspect your download might've been corrupted and/or somehow one of the extracted file or those on the device had error.
So glad that mine (as a backup) is XT1521 and bootloader unlocked, now running custom Nougat 7.1.1 (ResurrectionRemix) and it's on T-Mobile also. Maybe time to look for one of these pre-owned ones on eBay.
Click to expand...
Click to collapse
Thanks a LOT!! I'm looking forward to your meeting with your SIL LOL... My dad's had a different build number and kernel date, thats all. Everything else was the same..
Please, If you could do that command thing I'll be so thankful, so I can complete my research on what happened and how to fix this thing!
Up to now, all I have discovered is this:
* If you try to turn on the phone using the power button, the screen will stay off, as if it was hardbricked...
* To see some sign of life, the only way to turn this phone on is pressing vol down + power, so then I can enter fastboot mode.
* In fastboot mode I can't enter recovery mode: fastboot screen just freezes until you do the vol down + power combination. The same thing happens when you select "START" option in fastboot mode.As the screen freezes or stays off when trying to boot up, I assume that the kernel got corrupted.
* Only way to turn the phone off is selecting the POWER OFF option in fastboot. If the phone is off and I plug it into the wall charger, it will turn on showing the M logo as usual and then the big battery charging, but thats all. (Who is in charge of the offline battery animation? logo.img? boot.img? bootloader.img?)
* Flashing using fastboot.exe or mfastboot.exe doesn't help at all. Despite the fact I can flash bootloader.img and logo.img, I can't flash gpt.bin nor boot.img or the system sparsechunks due to "Preflash validation failed" error, even though I have the exact same firmware the phone had before the OTA (and it is the same firmware that the phone says it has installed when running the getvar all command). I'm still able to run erase userdata and erase cache commands with an OKAY as answer, but still the phone doesn't boot up.
So... I'm trapped with this situation! I gave my dad my Moto G3 as a compensation LOL!
Please, remember to do the /fastboot getvar all to your SIL's phone this saturday! Please!!!
Hi friends,
I just ordered an English UI Amazfit Pace on Lazada, but they sent me the one with Chinese UI. At first, I want to return the item, but it will take a long time so I try to flash it with the English flash file.
Follow tutorial, I enter unlockamazfit.com and when checking with Fastboot, I found out that my watch's SN is 0123456789abcdef.
Code:
C:\adb>fastboot getvar all
(bootloader) version-bootloader: U-Boot 2013.07-00127-g50e0e97
(bootloader) version-baseband: N/A
(bootloader) version-hardware: V1.1 20130322
(bootloader) version-cdma: N/A
(bootloader) variant: watch
(bootloader) serialno: 0123456789abcdef
(bootloader) product: watch
(bootloader) secure: no
(bootloader) unlocked: yes
(bootloader) uart-on: NO
(bootloader) partition-size:bootloader: 0x0000
(bootloader) partition-type:bootloader: emmc
(bootloader) partition-size:recovery: 0x1000
(bootloader) partition-type:recovery: emmc
(bootloader) partition-size:boot: 0x2000
(bootloader) partition-type:boot: emmc
(bootloader) partition-size:system: 0x3000
(bootloader) partition-type:system: ext4
(bootloader) partition-size:cache: 0x4000
(bootloader) partition-type:cache: ext4
(bootloader) partition-size:userdata: 0x5000
(bootloader) partition-type:userdata: ext4
(bootloader) max-download-size: 0x4000000
Can you give me some advise so that I can go on. As of now, I was stucked in get serial number step. Is there any way to get the English UI on my watch without unlock the boot loader?
Thank you!
dvckbiz said:
Hi friends,
I just ordered an English UI Amazfit Pace on Lazada, but they sent me the one with Chinese UI. At first, I want to return the item, but it will take a long time so I try to flash it with the English flash file.
Follow tutorial, I enter unlockamazfit.com and when checking with Fastboot, I found out that my watch's SN is 0123456789abcdef.
Code:
C:\adb>fastboot getvar all
(bootloader) version-bootloader: U-Boot 2013.07-00127-g50e0e97
(bootloader) version-baseband: N/A
(bootloader) version-hardware: V1.1 20130322
(bootloader) version-cdma: N/A
(bootloader) variant: watch
(bootloader) serialno: 0123456789abcdef
(bootloader) product: watch
(bootloader) secure: no
(bootloader) unlocked: yes
(bootloader) uart-on: NO
(bootloader) partition-size:bootloader: 0x0000
(bootloader) partition-type:bootloader: emmc
(bootloader) partition-size:recovery: 0x1000
(bootloader) partition-type:recovery: emmc
(bootloader) partition-size:boot: 0x2000
(bootloader) partition-type:boot: emmc
(bootloader) partition-size:system: 0x3000
(bootloader) partition-type:system: ext4
(bootloader) partition-size:cache: 0x4000
(bootloader) partition-type:cache: ext4
(bootloader) partition-size:userdata: 0x5000
(bootloader) partition-type:userdata: ext4
(bootloader) max-download-size: 0x4000000
Can you give me some advise so that I can go on. As of now, I was stucked in get serial number step. Is there any way to get the English UI on my watch without unlock the boot loader?
Thank you!
Click to expand...
Click to collapse
It seems already unlocked. Look at variable "unlocked", its value is yes: "unlocked: yes"
yep, its unlocked, just go to the unbrick your watch thread and follow the steps.
Hi,
Thank you for your support. I follow this tutorial and have my watch working fine.
Code:
https://gitlab.com/Neuer_User/PACEfied_AmazFit/wikis/permanent-install
This version will be installed on the system partition and replace the currently installed firmware on the watch. It will therefore survive reboots without any additional activities (no PC needed when booted). In case, you want to go back, you would need to reflash the original firmware. (I will provide installers for going back.)
This install features my "unbrickable" boot image. This is a boot image that will still allow adb access to the watch, even if the system partition has been completely damaged. While it is surely not 100% unbrickable, it will cover for most of the typical brick cases.
Together with using the recovery for installation (same as Huami is using), this process should be pretty safe.
INSTALLATION INSTRUCTIONS:
Download the zip file to your PC and unzip the content
connect your watch to the PC and validate it is visible: "adb devices". You should see your watch listed.
push the following files onto the sdcard of the watch (you need to have at least 700MB free on the watch):
Code:
"adb push update.zip /sdcard/" (This will take several minutes.)
"adb push recovery.img /sdcard/"
"adb push start_update.sh /sdcard/"
"adb push md5s.txt /sdcard/"
You need to have root available on the watch for installation. This can be achieved via:
In case you are already running PACEfied 1.2.5a or 1.2.6b, you have root and don't need to do anything.
In case you are running a later version of PACEfied, then you need to type "adb root" to switch to root mode.
in case you are running an original firmware (US or CN version), you need to download this file link1 link2 and follow the included instructions.
Enter the shell on the watch: "adb shell". You should see a "#" and not a "$". This shows, you have root access on the watch.
Start the installation process: "cd /sdcard/; sh start_update.sh". You should see something like this:
Code:
# Validating files...
# Flashing recovery...
# Rebooting into recovery for installation...
The system will then boot into recovery, where the PACEfied ROM is installed. PLEASE DO NOT INTERRUPT THE PROCESS. The process can take about 10 minutes. The recovery will automatically reboot the watch when it is finished.
Enjoy.
Click to expand...
Click to collapse
Long story short, I softbricked a Razer 1 by using Razer's own flash_all batch/shell script. At this point I can't determine exactly when the "oh ****" happened, but I've tried a lot of things and have been asking in the Newbie sticky post as well. Basically, I have the OEM factory defaults archive which supposedly will at least get a recovery partition and image back so I can move forward, but I only have fastboot/Download Mode. I can issue nearly any command I've tried to it, but the biggest issue right now is that it won't recognize or respond or accept any slot changes and a "fastboot getvar slot" returns an empty field. When I try setting the slot to a or b, or when I just do --set-active=other, I get an error that this device does not support slots. Obviously that's bad because this device does indeed us slot partitioning and has no true recovery partition.
What should I try? I have mkbootimg, abootimg, a Windows or Linux box with each able to manipulate Android devices and I even have Android Studio setup on my Windows PC. Magisk looks promising since I understand the concepts of tar and cpio as a linux admin, but obviously that's meaningless until I can boot into some kind of recovery. The device does still know its serial number, so I'm assuming the firmware flashed manufacturer stuff and hopefully any kind of PGP or cert or key is all still intact and untouched.
EDIT UPDATE:
< waiting for any device >
(bootloader) unlocked:yes
(bootloader) off-mode-charge:1
(bootloader) charger-screen-enabled:1
(bootloader) battery-soc-ok:yes
(bootloader) battery-voltage:4127
(bootloader) version-baseband:
(bootloader) version-bootloader:
(bootloader) variant:MSM UFS
(bootloader) partition-type:userdata:ext4
(bootloader) partition-size:userdata: 0xC72DD7000
(bootloader) partition-type:system_a:ext4
(bootloader) partition-size:system_a: 0xE0000000
(bootloader) has-slot:modem:yes
(bootloader) has-slot:system:yes
(bootloader) current-slot:a
(bootloader) has-slot:boot:yes
(bootloader) slot-retry-count:b:0
(bootloader) slot-unbootable:b:no
(bootloader) slot-successful:b:no
(bootloader) slot-retry-count:a:0
(bootloader) slot-unbootable:a:yes
(bootloader) slot-successful:a:no
(bootloader) slot-count:2
(bootloader) slot-suffixes:_a,_b,
(bootloader) secure:yes
(bootloader) serialno:181812V00402779
(bootloader) product:cheryl
(bootloader) max-download-size:0x20000000
(bootloader) kernel:uefi
(bootloader) version:0.0
all:
Finished. Total time: 0.032s
That is now my current getvar output, and it looks fine, but now I cannot set_active to _b and after the reboot, it seems to revert back to slot a automatically, like it is trying to enter recovery, but cannot.
Replying to bump and update:
Several attempts at running flash_all.bat from Razer, I can get as far as the first reboot in the script before it hangs and no longer takes input. I think that's because the stupid script isn't properly setting the active slot and it tries to flash partitions on the active slot (slot a in this case). So I am now going to manually run each command, but alternate active slots each time and see. This is new output of "getvar all"
< waiting for any device >
(bootloader) unlocked:yes
(bootloader) off-mode-charge:1
(bootloader) charger-screen-enabled:1
(bootloader) battery-soc-ok:yes
(bootloader) battery-voltage:4127
(bootloader) version-baseband:
(bootloader) version-bootloader:
(bootloader) variant:MSM UFS
(bootloader) partition-type:userdata:ext4
(bootloader) partition-size:userdata: 0xC72DD7000
(bootloader) partition-type:system_a:ext4
(bootloader) partition-size:system_a: 0xE0000000
(bootloader) has-slot:modem:yes
(bootloader) has-slot:system:yes
(bootloader) current-slot:a
(bootloader) has-slot:boot:yes
(bootloader) slot-retry-count:b:0
(bootloader) slot-unbootable:b:no
(bootloader) slot-successful:b:no
(bootloader) slot-retry-count:a:0
(bootloader) slot-unbootable:a:yes
(bootloader) slot-successful:a:no
(bootloader) slot-count:2
(bootloader) slot-suffixes:_a,_b,
(bootloader) secure:yes
(bootloader) serialno:181812V00402779
(bootloader) product:cheryl
(bootloader) max-download-size:0x20000000
(bootloader) kernel:uefi
(bootloader) version:0.0
all:
Finished. Total time: 0.032s
Hi there, I'm trying to recovery a Moto One xt1941-3 but even after a successful flash, I get the following message:
Fastboot AP Flash Mode (Secure)
SSM: Android checking failed.
No bootable A / B slot
Failed to boot Linux, failing back to fastboot
Fastboot Reason: Falling Through Normal Boot Mode
Tried multiple firmwares, with RSD Lite or Lenovo Moto Smart Assistant but always getting the same error.
Any thoughts? I'm really desperate right now.
No one?
DogDorgs said:
No one?
Click to expand...
Click to collapse
I doubt I have a fix, but what do you get with
Code:
fastboot getvar all
Please post it here after you remove the IMEI line
Sent from my ali using XDA Labs
sd_shadow said:
I doubt I have a fix, but what do you get with
Code:
fastboot getvar all
Please post it here after you remove the IMEI line
Sent from my ali using XDA Labs
Click to expand...
Click to collapse
Hey, thanks for the response.
So I've tested and I get different results of the getvar-all. I'll explain:
If I enter the fastboot mode manually (without trying to boot normally) I get this result
Code:
(bootloader) version: 0.5
(bootloader) version-bootloader: MBM-2.1-deen_retail-4658d8b-200123
(bootloader) product: deen
(bootloader) board: deen
(bootloader) secure: yes
(bootloader) hwrev: PVT1
(bootloader) radio: 2
(bootloader) storage-type: emmc
(bootloader) emmc: 64GB SAMSUNG RH64AB RV=08 PV=05 FV=0000000000000005
(bootloader) ram: 4GB SAMSUNG LP3 DIE=8Gb M5=01 M6=06 M7=00 M8=5F
(bootloader) cpu: MSM8953
(bootloader) serialno: 0053993482
(bootloader) cid: 0x0032
(bootloader) channelid: 0x19
(bootloader) uid: 508356F900000000000000000000
(bootloader) securestate: oem_locked
(bootloader) iswarrantyvoid: no
(bootloader) max-download-size: 534773760
(bootloader) reason: Volume down key pressed
(bootloader) imei:
(bootloader) meid:
(bootloader) date: 02-04-2019
(bootloader) sku: XT1941-3
(bootloader) carrier_sku: XT1941-3
(bootloader) battid:
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Sun Oct 13 13:11:54 UTC 2019"
(bootloader) ro.build.fingerprint[0]: motorola/deen/deen_sprout:9/PPKS29
(bootloader) ro.build.fingerprint[1]: .68-16-21-20/e4a64:user/release-ke
(bootloader) ro.build.fingerprint[2]: ys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.39.426.30.deen.retai
(bootloader) ro.build.version.full[1]: l.en.US
(bootloader) ro.build.version.qcom: LA.UM.7.6.r1-02500-89xx.0
(bootloader) version-baseband: M8953_01.02.04.02R DEEN_LATAMDSDS_CUST
(bootloader) kernel.version[0]: Linux version 3.18.115-perf-g91db513 (hu
(bootloader) kernel.version[1]: [email protected]) (gcc version 4.9.x 20
(bootloader) kernel.version[2]: 150123 (prerelease) (GCC) ) #1 SMP PREEM
(bootloader) kernel.version[3]: PT Thu Jan 23 05:01:46 CST 2020
(bootloader) sbl1.git: MBM-2.1-deen_retail-b314434-200123
(bootloader) rpm.git: MBM-2.1-deen_retail-80327a1-200123
(bootloader) tz.git: MBM-2.1-deen_retail-29778c6-200123
(bootloader) devcfg.git: MBM-2.1-deen_retail-29778c6-200123
(bootloader) keymaster.git: MBM-2.1-deen_retail-29778c6-200123
(bootloader) cmnlib.git: MBM-2.1-deen_retail-29778c6-200123
(bootloader) cmnlib64.git: MBM-2.1-deen_retail-29778c6-200123
(bootloader) prov.git: MBM-2.1-deen_retail-29778c6-200123
(bootloader) aboot.git: MBM-2.1-deen_retail-4658d8b-200123
(bootloader) frp-state: protected (77)
(bootloader) ro.carrier: retbr
(bootloader) current-slot: _b
(bootloader) running-boot-lun: 0
(bootloader) running-slot: _b
(bootloader) slot-suffixes: _a,_b
(bootloader) slot-count: 2
(bootloader) slot-successful:_a: No
(bootloader) slot-successful:_b: No
(bootloader) slot-bootable:_a: No
(bootloader) slot-bootable:_b: Yes
(bootloader) slot-retry-count:_a: 0
(bootloader) slot-retry-count:_b: 5
all: listed above
Finished. Total time: 0.225s
And If I try to boot and fall back to fastboot I get this message
Code:
(bootloader) version: 0.5
(bootloader) version-bootloader: MBM-2.1-deen_retail-4658d8b-200123
(bootloader) product: deen
(bootloader) board: deen
(bootloader) secure: yes
(bootloader) hwrev: PVT1
(bootloader) radio: 2
(bootloader) storage-type: emmc
(bootloader) emmc: 64GB SAMSUNG RH64AB RV=08 PV=05 FV=0000000000000005
(bootloader) ram: 4GB SAMSUNG LP3 DIE=8Gb M5=01 M6=06 M7=00 M8=5F
(bootloader) cpu: MSM8953
(bootloader) serialno: 0053993482
(bootloader) cid: 0x0032
(bootloader) channelid: 0x19
(bootloader) uid: 508356F900000000000000000000
(bootloader) securestate: oem_locked
(bootloader) iswarrantyvoid: no
(bootloader) max-download-size: 534773760
(bootloader) reason: Fall-through from normal boot mode
(bootloader) imei:
(bootloader) meid:
(bootloader) date: 02-04-2019
(bootloader) sku: XT1941-3
(bootloader) carrier_sku: XT1941-3
(bootloader) battid:
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Sun Oct 13 13:15:59 UTC 2019"
(bootloader) ro.build.fingerprint[0]: motorola/deen/deen_sprout:9/PPKS29
(bootloader) ro.build.fingerprint[1]: .68-16-21-20/e4a64:user/release-ke
(bootloader) ro.build.fingerprint[2]: ys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.39.426.30.deen.retai
(bootloader) ro.build.version.full[1]: l.en.US
(bootloader) ro.build.version.qcom: LA.UM.7.6.r1-02500-89xx.0
(bootloader) version-baseband: M8953_01.02.04.02R DEEN_LATAMDSDS_CUST
(bootloader) kernel.version[0]: Linux version 3.18.115-perf-g91db513 (hu
(bootloader) kernel.version[1]: [email protected]) (gcc version 4.9.x 20
(bootloader) kernel.version[2]: 150123 (prerelease) (GCC) ) #1 SMP PREEM
(bootloader) kernel.version[3]: PT Thu Jan 23 05:01:46 CST 2020
(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: MBM-2.1-deen_retail-4658d8b-200123
(bootloader) frp-state: protected (77)
(bootloader) ro.carrier: retbr
(bootloader) current-slot:
(bootloader) running-boot-lun: 0
(bootloader) running-slot:
(bootloader) slot-suffixes: _a,_b
(bootloader) slot-count: 2
(bootloader) slot-successful:_a: No
(bootloader) slot-successful:_b: No
(bootloader) slot-bootable:_a: No
(bootloader) slot-bootable:_b: No
(bootloader) slot-retry-count:_a: 0
(bootloader) slot-retry-count:_b: 0
all: listed above
Finished. Total time: 0.217s
It's interesting because if I don't try to boot to the system, it says that the slot B is bootable.
DogDorgs said:
I doubt I have a fix, but what do you get with
Hey, thanks for the response.
So I've tested and I get different results of the getvar-all. I'll explain:
If I enter the fastboot mode manually (without trying to boot normally) I get this result
And If I try to boot and fall back to fastboot I get this message
It's interesting because if I don't try to boot to the system, it says that the slot B is bootable.
Click to expand...
Click to collapse
I don't suppose you checked
Oem lock Developer option before it stopped working?
If you did likely the bootloader could be unlocked.
You would have had to enable dev options first.
If none of those sound familiar you didn't do it.
Other than that I don't think there's a solution.
You can try
Fastboot wipe all
Or
Fastboot wipe misc
LMSA saves the firmware it downloaded.
Was that blur version 29.xxx.xx or 30.xxx?
Sent from my ali using XDA Labs
---------- Post added at 02:37 AM ---------- Previous post was at 02:31 AM ----------
Are these the firmware versions you used with RSD Lite?
https://mirrors.lolinet.com/firmware/moto/deen/official/RETBR/
XT1941-3_DEEN_RETBR_10_QPK30.54-22_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
Or
XT1941-3_DEEN_RETBR_9.0_PPKS29.68-16-21-20_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
Sent from my ali using XDA Labs
sd_shadow said:
I don't suppose you checked
Oem lock Developer option before it stopped working?
If you did likely the bootloader could be unlocked.
You would have had to enable dev options first.
If none of those sound familiar you didn't do it.
Other than that I don't think there's a solution.
You can try
Fastboot wipe all
Or
Fastboot wipe misc
LMSA saves the firmware it downloaded.
Was that blur version 29.xxx.xx or 30.xxx?
Sent from my ali using XDA Labs
---------- Post added at 02:37 AM ---------- Previous post was at 02:31 AM ----------
Are these the firmware versions you used with RSD Lite?
https://mirrors.lolinet.com/firmware/moto/deen/official/RETBR/
XT1941-3_DEEN_RETBR_10_QPK30.54-22_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
Or
XT1941-3_DEEN_RETBR_9.0_PPKS29.68-16-21-20_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
Sent from my ali using XDA Labs
Click to expand...
Click to collapse
Hi, so the version LMSA downloaded first was a 29.xxx and then downloaded the 30.xxx, with both of them installing flawlessly. I've tried to unlock the bootloader but nope, the OEM unlock was not enabled.
Another thing that I've tried was bricking the phone by installing an older Oreo rom, and then I've performed a blankflash in order to flash another time. The flash was a success but the phone still not booting.
And about those commands, seems like my fastboot is not recognizing it, when I try to boot I get this message:
Code:
fastboot wipe all
fastboot: usage: unknown command wipe
Thanks for the attention!
EDIT: Yeah, I've tried some roms from this site you've linked, included those two.
DogDorgs said:
Hi, so the version LMSA downloaded first was a 29.xxx and then downloaded the 30.xxx, with both of them installing flawlessly. I've tried to unlock the bootloader but nope, the OEM unlock was not enabled.
Another thing that I've tried was bricking the phone by installing an older Oreo rom, and then I've performed a blankflash in order to flash another time. The flash was a success but the phone still not booting.
And about those commands, seems like my fastboot is not recognizing it, when I try to boot I get this message:
Code:
fastboot wipe all
fastboot: usage: unknown command wipe
Thanks for the attention!
EDIT: Yeah, I've tried some roms from this site you've linked, included those two.
Click to expand...
Click to collapse
Sorry wrong commands
It should have been
Fastboot erase misc
Or
Fastboot erase all
Sent from my Moto E (4) using Tapatalk
sd_shadow said:
Sorry wrong commands
It should have been
Fastboot erase misc
Or
Fastboot erase all
Sent from my Moto E (4) using Tapatalk
Click to expand...
Click to collapse
So I've tried to run those commands, the misc says "access denied" and the "erase all" did work. I've run those two commands and re-flashed the last rom. No lucky thought. :/
Same
I have exactly the same problem... I can't toggle the option "Allow OEM unlock" because my phone suddenly bricked. One day it was working perfectly and the next day it shows "boot up failed". I've already try flashing several roms but nothing changes in "fastboot getvar all". My warranty isn't valid because my phone is from another country.
DogDorgs said:
So I've tried to run those commands, the misc says "access denied" and the "erase all" did work. I've run those two commands and re-flashed the last rom. No lucky thought. :/
Click to expand...
Click to collapse
did u found a solution?
Hello people, I have a problem with my moto g power, my bootloader is blocked and my device is only in fastboot mode, I can't boot the system to activate the OEM option in the settings, I've tried the original rom but it doesn't install due to the bootloader is blocked, how can I do anything?
need help !
jhonn2700 said:
Hello people, I have a problem with my moto g power, my bootloader is blocked and my device is only in fastboot mode, I can't boot the system to activate the OEM option in the settings, I've tried the original rom but it doesn't install due to the bootloader is blocked, how can I do anything?
need help !
Click to expand...
Click to collapse
Use Lenovo rescue (LMSA) and restore
and if LMSA is not able to fix it, there might be a hardware issue , maybe corrupted ram? so i'd say return it for warranty.
the system should not suddenly stop working without manually breaking some stuff
does not work, fastboot single partition error
The LMSA does not work, a single partition fastboot error appears and new updated rom's stock. someone help me!
I have the same problem. Tried to install a stock rom, then i did "fastboot oem lock", now i get the message "your device is corrupted. It cannot be trusted and will not boot". In the Fastboot Flash Mode it shows "Flashing... Locked".
Tried to run Fastboot oem unlock <Code Provided>, but i get the error:
(bootloader) Check 'OEM unlocking' in Android Settings > Developer
(bootloader) Options
FAILED (remote failure)
finished. total time: 0.011s
Tried to boot most recent Stock Rom, but get "Permission Denied" errors.
Tried Lenovo Resue but it fails at 50%. Log shows access denied errors.
Below, the result for getvar all:
(bootloader) kernel: uefi
(bootloader) version-bootloader: MBM-3.0-rav_retail-dfa2a6b4b2-201028
(bootloader) product: rav
(bootloader) board: rav
(bootloader) secure: yes
(bootloader) hwrev: PVT1
(bootloader) radio: LATAM
(bootloader) storage-type: eMMC
(bootloader) emmc: 64GB MICRON S0J9K8 RV=08 PV=10 FV=0000000000000004
(bootloader) ufs: N/A
(bootloader) ram: 4GB MICRON LP4 DIE=16Gb M5-M8=FF 04 10 10
(bootloader) cpu: SM_NICOBAR 1.0
(bootloader) serialno: ZF5232L9LB
(bootloader) cid: 0x0032
(bootloader) channelid: 0x19
(bootloader) uid: 2A2B3EA1
(bootloader) securestate: flashing_locked
(bootloader) factory-modes: disabled
(bootloader) verity-state: enforcing (0)
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 805259264
(bootloader) reason: Volume down key pressed
(bootloader) imei:
(bootloader) imei2:
(bootloader) meid:
(bootloader) date: 04-18-2020
(bootloader) sku: XT2045-1
(bootloader) carrier_sku: XT2045-1
(bootloader) battid: SB18C55376
(bootloader) battery-voltage: 4257
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) ro.build.fingerprint[0]: motorola/rav_retail/rav:10/QPJS30.
(bootloader) ro.build.fingerprint[1]: 63-35-1-15/37df17:user/release-key
(bootloader) ro.build.fingerprint[2]: s
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full: <not found>
(bootloader) ro.build.version.qcom: LA.UM.8.11.r1-01800-NICOBAR.0
(bootloader) version-baseband: M6125_34.30.03.38R RAV_LATAMDSDS_CUST
(bootloader) kernel.version[0]: Linux version 4.14.117-perf+ ([email protected]
(bootloader) kernel.version[1]: roid-build) (clang version 8.0.12 for An
(bootloader) kernel.version[2]: droid NDK) #1 SMP PREEMPT Wed Oct 28 19:
(bootloader) kernel.version[3]: 22:27 CDT 2020
(bootloader) git:xbl: MBM-3.0-rav_retail-60f322a3b-201028
(bootloader) git:xbl_config: MBM-3.0-rav_retail-60f322a3b-201028
(bootloader) git:rpm: MBM-3.0-rav_retail-ffcccb0-201028
(bootloader) git:tz: MBM-3.0-rav_retail-056b6062-201028
(bootloader) git:hyp: MBM-3.0-rav_retail-056b6062-201028
(bootloader) git:devcfg: MBM-3.0-rav_retail-056b6062-201028
(bootloader) git:cmnlib: MBM-3.0-rav_retail-056b6062-201028
(bootloader) git:cmnlib64: MBM-3.0-rav_retail-056b6062-201028
(bootloader) git:keymaster: MBM-3.0-rav_retail-056b6062-201028
(bootloader) gitrov: MBM-3.0-rav_retail-056b6062-201028
(bootloader) git:abl: MBM-3.0-rav_retail-dfa2a6b4b2-201028
(bootloader) git:qupfw: MBM-3.0-rav_retail-f848623-201028
(bootloader) git:uefisecapp: MBM-3.0-rav_retail-056b6062-201028
(bootloader) frp-state: protected (77)
(bootloader) ro.carrier: retbr
(bootloader) current-slot: b
(bootloader) running-bl-slot: _b/_b
(bootloader) running-boot-lun: 0
(bootloader) slot-count: 2
(bootloader) slot-successful:_a: no
(bootloader) slot-successful:_b: yes
(bootloader) slot-unbootable:_a: yes
(bootloader) slot-unbootable:_b: no
(bootloader) slot-retry-count:_a: 0
(bootloader) slot-retry-count:_b: 5
(bootloader) logical-block-size: 0x200
(bootloader) erase-block-size: 0x200
(bootloader) is-userspace: no
(bootloader) pcb-part-no: SB28C73901
all: listed above
did you manage to solve it in any way?
I still have this problem
jhonn2700 said:
did you manage to solve it in any way?
I still have this problem
Click to expand...
Click to collapse
I took it to the Motorola technical assistance and they replaced the Logic Board. Coudn't find another solution.