Development [CLOSED][RECOVERY] [12L] [OFFICIAL] TWRP 3.6.2-12.1-0 | Team Win Recovery Project | Moto G60/G40 | - Moto G40 / G60

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Note - Iam Not Responsible for bricked devices
About Team win recovery project
TWRP is an open source, community project. TWRP development is done by roughly 4 people at this point. We also have a large support community with many people who are willing to answer questions and help people with their devices either through our IRC channel or on forums like xda-developers.
Team Win was originally formed to work on porting WiMAX to CM7 for the HTC EVO 4G. After our work on the EVO 4G we wanted to work on a project that would work on more devices than just the EVO 4G and we settled on working on a recovery. Today TWRP is the leading custom recovery for Android phones.
Note - as of now only android 11 based twrp builds available in the official twrp.me website. twrp team yet to prepare and merge android 12L based support to official in the later september 2022 or august third week atleast ( Just my expectations & no guarantee with the time frame for exact release date or month ). So consider my android 12L twrp builds as UNOFFICIAL until twrp team officially release android 12L based twrp builds via twrp.me website.
Installation procedure
• download twrp-xyz.img & twrp-installer-xyz.zip
• fastboot boot twrp-xyz.img ( for temporary installation )
• flash twrp-installer-xyz.zip ( for permanent installation )
Whats working?
• Magisk zip installation
• Rom zip installation
• Custom kernel zip installation
• GApps zip installation
• TWRP permanent zip installation
• Slot switch by itself while flashing Rom zip
• Manual slot switch support
• Back-up & restore
• Full device dump support from each partition
• Stock Full OTA zip installation support
• individual image flash support
• Decryption works on Android 11/12/12L
Credits
• TWRP team for recovery source
• Motorola for prebuilt kernel , dtbo , dtb & vendor
• Moderators (For Giving Freedom To Post Threads)​​
Download Android-11 OFFICIAL TWRP
Download Android-12/12L UNOFFICIAL TWRP
Join Community Group
Maintainers : Raghu varma
Kernel source code : android_kernel_motorola_sm6150
Source code: https://github.com/TeamWin
Device source code : android_device_motorola_hanoip
​

Reserved

Awesome work ... Gonna try it...

PLease guide us to flash lineage 12 with magiisk through twrp as touch is not working when we are in twrp recovery..need installation process through twrp..

Great work! Can I root my phone with this recovery?
And How could I to do it? Thanks

Changelog Fri Jun 10 17:27:35 IST 2022
==========================
• Updated Super partition size value
• Updated dynamic partition size value
• Updated prebuilt kernel , dtbo & dtbo from RRIS31.Q1-42-51-12-1
• Updated touch modules & firmware from RRIS31.Q1-42-51-12-1
• Added TWRP permanent zip support

Announcement
==========
A big massive thank you for TWRP team for allowing our device source and considering our request to mark it as official.
Now we are official folks.
Here we go - https://twrp.me/motorola/motorolamotog60g40fusion.html

Possibility to get root with custom ROM?

Hi there.
I'm trying to boot TWRP from image to backup original partitions before rooting. ADB part is going fine:
Code:
d:\Programs\android-sdk-windows\platform-tools>adb reboot bootloader
d:\Programs\android-sdk-windows\platform-tools>fastboot boot twrp.img
Sending 'boot.img' (31072 KB) OKAY [ 0.778s]
Booting OKAY [ 10.365s]
Finished. Total time: 11.300s
But after that the phone just reboots and loads original system.
Is there any way to enable some sort of logging for TWRP, to see where the problem is coming from?
Code:
(bootloader) kernel: uefi
(bootloader) version-bootloader: MBM-3.0-hanoip_retail-c29b299de02-220502
(bootloader) product: hanoip
(bootloader) board: hanoip
(bootloader) secure: yes
(bootloader) hwrev: PVT
(bootloader) radio: EUAPEM
(bootloader) storage-type: UFS
(bootloader) emmc: N/A
(bootloader) ufs: 128GB SKhynix H9HQ15AECMBDAR FV=A002 WB=0
(bootloader) ram: 6GB SKHYNIX LP4x DIE=16Gb M5-M8=06 06 00 11
(bootloader) cpu: SM7150 1.0
(bootloader) serialno: ***
(bootloader) cid: 0x0032
(bootloader) channelid: 0x00
(bootloader) uid: FC26B259
(bootloader) securestate: flashing_unlocked
(bootloader) factory-modes: disabled
(bootloader) verity-state: enforcing (0)
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 805306368
(bootloader) reason: Reboot mode set to fastboot
(bootloader) imei: ***
(bootloader) imei2: ***
(bootloader) meid:
(bootloader) date: 12-08-2021
(bootloader) sku: XT2135-2
(bootloader) carrier_sku: XT2135-2
(bootloader) battid: SB18D01687
(bootloader) battery-voltage: 4422
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) poweroffalarm: 0
(bootloader) ro.carrier: teleu
(bootloader) ro.build.fingerprint: motorola/hanoip_retailnq/hanoip:11/RRIS31.Q1-42-51-12-4/24f96:user/release-keys
(bootloader) ro.build.version.qcom: LA.UM.9.1.r1-07700-SMxxx0.0
(bootloader) version-baseband: M7150_09.297.01.75.01R HANOIP_EUAPEMDSDS_CUST
(bootloader) kernel.version: Linux version 4.14.190-perf+ ([email protected]) (clang version 10.0.7 for Android NDK, GNU ld (binutils-2.27-bd24d23f) 2.27.0.20170315) #1 SMP PREEMPT Mon May 2 07:50:18 CDT 2022
(bootloader) git:xbl: MBM-3.0-hanoip_retail-008fd4343-220502
(bootloader) git:xbl_config: MBM-3.0-hanoip_retail-008fd4343-220502
(bootloader) git:aop: MBM-3.0-hanoip_retail-4bfd5e5-220502
(bootloader) git:tz: MBM-3.0-hanoip_retail-1a950cdaf-220502
(bootloader) git:hyp: MBM-3.0-hanoip_retail-1a950cdaf-220502
(bootloader) git:devcfg: MBM-3.0-hanoip_retail-1a950cdaf-220502
(bootloader) git:cmnlib: MBM-3.0-hanoip_retail-1a950cdaf-220502
(bootloader) git:keymaster: MBM-3.0-hanoip_retail-c232249-220502
(bootloader) git:storsec: MBM-3.0-hanoip_retail-1a950cdaf-220502
(bootloader) git:prov: MBM-3.0-hanoip_retail-1a950cdaf-220502
(bootloader) git:abl: MBM-3.0-hanoip_retail-c29b299de02-220502
(bootloader) git:qupfw: MBM-3.0-hanoip_retail-734604a-220502
(bootloader) git:uefisecapp: MBM-3.0-hanoip_retail-1a950cdaf-220502
(bootloader) frp-state: protected (144)
(bootloader) current-slot: a
(bootloader) running-bl-slot: _a/_a
(bootloader) running-boot-lun: 2
(bootloader) slot-count: 2
(bootloader) slot-successful:_a: yes
(bootloader) slot-successful:_b: yes
(bootloader) slot-unbootable:_a: no
(bootloader) slot-unbootable:_b: no
(bootloader) slot-retry-count:_a: 6
(bootloader) slot-retry-count:_b: 6
(bootloader) logical-block-size: 0x1000
(bootloader) erase-block-size: 0x1000
(bootloader) is-userspace: no
(bootloader) pcb-part-no: SB28D03127
(bootloader) primary-display: tm_ili7807s_fhd_vid
(bootloader) secondary-display:

Changelog Mon Jun 20 12:07:22 IST 2022
============================
• Updated prebuilt dtbo , dtb & kernel from OSS kernel
• Added all device specific partitions to twrp
• Added FULL device dump support from each partition
• Added stock Full OTA zip installation support
• Redesigned the entire logic for touchscreen fix on any rom & kernel. ( Yes ! It's universal now and will work on any Android version and any kernel/rom )
• Fixed architecture configuration from source.

Support GSI roms?

Awsome job

since there is no g50 ibiza twrp i decided togive yours a try and it booted by miracle but witout touch just freezing screen would you sir build one for g50 and do a favor for g50 community

Hey i am getting this error while switching to slot A....... ( ERROR CHANGING BOOTLOADER BOOT SLOT TO A ).....can anyone help me please i am not able to flash custom rom.....

can someone help me regarding problem of (bootloader) Invalid partition name recovery
please

When will we get twrp for moto g52

Devilme said:
Hey i am getting this error while switching to slot A....... ( ERROR CHANGING BOOTLOADER BOOT SLOT TO A ).....can anyone help me please i am not able to flash custom rom.....
Click to expand...
Click to collapse
flash back stock rom and reflash custom rom from step 1.
godslayer.04 said:
can someone help me regarding problem of (bootloader) Invalid partition name recovery
please
Click to expand...
Click to collapse
fastboot boot twrp-xyz.img

Changelog Sat Jul 30 19:48:53 UTC 2022
============================
• initial Android 12/12L TWRP support
• working perfectly on any Android 11/12/12L rom ( including custom & stock )
• fixed ROM flashing issue from custom to custom & stock to custom ( no need to flash back stock rom anymore to install custom rom from scratch )
Note - as of now only android 11 based twrp builds available in the official twrp.me website. twrp team yet to prepare and merge android 12L based support to official in the later september 2022 or august third week atleast ( Just my expectations & no guarantee with the time frame for exact release date or month ). So consider my android 12L twrp builds as UNOFFICIAL until twrp team officially release android 12L based twrp builds via twrp.me website.
Do you like my work? please consider donation. It helps me to take development forward & manage my server.
My Paypal email id - [email protected]​My UPI id - [email protected]​Thank you!

Dear brother, @Raghu varma
First of all thank you very much for preparing Recovery+Rom (complete package) of moto g60 for moto g60 users community !!! Your time spent, brain exercise and hard work can be gauged by looking at your work.I pray to God that you continue to progress in your work like this...
So, again Thanks a lot....
I sow your recovery on github and t.me site, but i want to know that which recovery i should install either github's or t.me's. if i have nothing to do with official/non official but should be top most perfect among these recovery. (My personal experience is that there is no difference between official / non official except just the name tag ,, so I am asking,, sometimes unofficial can be better than official)
which recovery (either 11 recovery or 12/12L) i should install if, i am on stock 11 or on your rom 12/12L lineage/pixle rom.
Onemore, Can I flash magisk.zip via your recovery for root, because this time recommendations is going to flash patched boot.img via fastboot on AB device.
Thanks..

How to root g60 using twrp ?
Any guide. I need to run work apps related to my employer

Related

[Help Thread][Moto G8 Play](2019) Ask Any Question, Noob Friendly

[SIZE=+2]This thread has been created
for
Questions & Answers/Troubleshooting[/SIZE]​[SIZE=+2]Specific to[/SIZE]
Moto G8 Play
​
Please feel free to share issues, questions and offer help. Noob questions are welcomed.
It is always best to use the Thanks button , in lieu of simply posting "Thank you".
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Please keep discussion focused, on questions pertaining to this Device
List of supporters...
...
...
...​To those seeking help: Please don't bombard the supporters with PMs asking for help. Instead, ask your question here in the thread so others can benefit from the solution to your problem as well. If you want to be sure someone particular gets notified of your question, put his / her username directly after an @.
If you have ROM related questions, post in the relevant ROM Q&A thread (if there is one) or directly in the ROM development thread. Thank you!
Supporters: If you want to be put on or off the list, just make a request here in the thread!
Before posting anything, I strongly advise you to read
Forum Rules
[GUIDE] - XDA New User Guide - Getting started on XDA
XDA Tour
FAQs for Device Thread link
Index for Device Thread Link
Please look for a similar thread when visiting another device forum.
If you would like to create a [Help Thread] please Click Here.
​
I'm not planning on adding every Rom or Mod,
but if you have a suggestion for other links
Please post them here.
FAQs
UnLocking the Bootloader
ReLocking the Bootloader
[Fixing] Baseband <not found> / IMEI=0 / No Network After Flash / Issues
Fixing your Moto stuck in Qualcomm QHSUSB_Bulk or qloader mode
Unfortunately LMSA doesn't work with G8 Play -14 April 2020
[*]Using Lenovo's MOTO Smart Assistant to Update/Repair/Backup
Custom Roms/Recovery/Root/
Firmware
Firmware should be avalible here
https://mirrors.lolinet.com/firmware/moto/
Specs
Help Please !
Hi to everyone, i've seen all the guides you post but i cant find the correct frimware for my moto g8 play, i have tried a few lima pmds 99.70-81-5 but anything seems to work :c, also i havent unlocked OEM so i need to install the same firmware version to unbrick it :c, can anyone help me to find the correct one? Thanks for all your guides !
version: 0.5
version-bootloader: MBM-2.1-lima_32_retail-210600d2e-200306
product: lima
board: lima
secure: yes
hwrev: PVT
radio: 2
storage-type: eMMC
emmc: 32GB SAMSUNG 4X6KMB RV=08 PV=00 FV=0000000000000003
ram: 2GB SAMSUNG LP4x DIE=16Gb M5=01 M6=07 M7=00 M8=12
cpu: MT6771V/WL
serialno: ZY2274B5F3
cid: 0x0032
channelid: 0x0a
uid: 64D5498EF4027FFC000000000000
securestate: oem_locked
factory-modes: disabled
iswarrantyvoid: no
max-download-size: 268435456
reason: No bootable A/B slot
imei: 359100103691791
imei2:
meid:
date: 12-07-2019
sku: XT2015-2
carrier_sku: XT2015-2
battid: SB18C51711
iccid:
max-sparse-size: 268435456
current-time: "Tue Jan 1 1: 4:28 UTC 2019"
ro.build.fingerprint[0]: motorola/lima_32/lima:9/PMDS29.70-
ro.build.fingerprint[1]: 81-5/1fa4a:user/release-keys
poweroffalarm: 0
ro.build.version.full[0]: Blur_Version.29.201.7.lima_32.ret
ro.build.version.full[1]: ail.en.US
ro.build.version.mtk: alps-mp-p0.mp1.tc2sp-V1.47
version-baseband: <not found>
kernel.version[0]: Linux version 4.4.146+ ([email protected]
kernel.version[1]: 159) (gcc version 4.9.x 20150123 (prerel
kernel.version[2]: ease) (GCC) ) #1 SMP PREEMPT Thu Jun 25
kernel.version[3]: 08:09:39 CDT 2020
frp-state: protected (144)
ro.carrier: tefmx
current-slot: a
running-boot-lun: 0
running-slot: _a
slot-successful:_a: no
slot-successful:_b: no
slot-bootable:_a: no
slot-bootable:_b: no
slot-retry-count:_a: 0
slot-retry-count:_b: 0
slot-suffixes: _a,_b
slot-count: 2
pcb-part-no: SB28C70228
all: listed above
strako777 said:
Hi to everyone, i've seen all the guides you post but i cant find the correct frimware for my moto g8 play, i have tried a few lima pmds 99.70-81-5 but anything seems to work :c, also i havent unlocked OEM so i need to install the same firmware version to unbrick it :c, can anyone help me to find the correct one? Thanks for all your guides !
version: 0.5
version-bootloader: MBM-2.1-lima_32_retail-210600d2e-200306
product: lima
board: lima
secure: yes
hwrev: PVT
radio: 2
storage-type: eMMC
emmc: 32GB SAMSUNG 4X6KMB RV=08 PV=00 FV=0000000000000003
ram: 2GB SAMSUNG LP4x DIE=16Gb M5=01 M6=07 M7=00 M8=12
cpu: MT6771V/WL
serialno: ZY2274B5F3
cid: 0x0032
channelid: 0x0a
uid: 64D5498EF4027FFC000000000000
securestate: oem_locked
factory-modes: disabled
iswarrantyvoid: no
max-download-size: 268435456
reason: No bootable A/B slot
imei: 359100103691791
imei2:
meid:
date: 12-07-2019
sku: XT2015-2
carrier_sku: XT2015-2
battid: SB18C51711
iccid:
max-sparse-size: 268435456
current-time: "Tue Jan 1 1: 4:28 UTC 2019"
ro.build.fingerprint[0]: motorola/lima_32/lima:9/PMDS29.70-
ro.build.fingerprint[1]: 81-5/1fa4a:user/release-keys
poweroffalarm: 0
ro.build.version.full[0]: Blur_Version.29.201.7.lima_32.ret
ro.build.version.full[1]: ail.en.US
ro.build.version.mtk: alps-mp-p0.mp1.tc2sp-V1.47
version-baseband: <not found>
kernel.version[0]: Linux version 4.4.146+ ([email protected]
kernel.version[1]: 159) (gcc version 4.9.x 20150123 (prerel
kernel.version[2]: ease) (GCC) ) #1 SMP PREEMPT Thu Jun 25
kernel.version[3]: 08:09:39 CDT 2020
frp-state: protected (144)
ro.carrier: tefmx
current-slot: a
running-boot-lun: 0
running-slot: _a
slot-successful:_a: no
slot-successful:_b: no
slot-bootable:_a: no
slot-bootable:_b: no
slot-retry-count:_a: 0
slot-retry-count:_b: 0
slot-suffixes: _a,_b
slot-count: 2
pcb-part-no: SB28C70228
all: listed above
Click to expand...
Click to collapse
I believe you should be using lima_32
https://mirrors.lolinet.com/firmware/moto/lima_32/official/TIMBR/
Flashing firmware with an locked bootloader is tricky sometimes
https://forum.xda-developers.com/general/rooting-roms/guide-flashing-motorola-firmware-t4042039
But I recommend trying LMSA's Flash Rescue option
https://forum.xda-developers.com/general/general/update-moto-lenovo-moto-smart-assistant-t3951714
Sent from my Moto E (4) using Tapatalk
dont know what to do :C
sd_shadow said:
I believe you should be using lima_32
https://mirrors.lolinet.com/firmware/moto/lima_32/official/TIMBR/
Flashing firmware with an locked bootloader is tricky sometimes
https://forum.xda-developers.com/general/rooting-roms/guide-flashing-motorola-firmware-t4042039
But I recommend trying LMSA's Flash Rescue option
https://forum.xda-developers.com/general/general/update-moto-lenovo-moto-smart-assistant-t3951714
Sent from my Moto E (4) using Tapatalk
Click to expand...
Click to collapse
I alredy tried a few variants of Lima_32 (Tefmx because of the rio.carrier, retail, retla, openmx,timbr) and all of this was on the PMDS 29.70-81-5, didnt know what to, i read somewhere that i need to install the same factory firmware to avoid the"Startup Failed" Error or rather the lastest firmware, you think that if i wait to a new firmware update cold be able to install it? why i cant boot with any firmware ?
Help!! I installed a ROM in my moto g8 play and doesn´t respond
Hi to everyone, i have seeing old guide´s to recover urs motorolas devices
my problem is that i installed a different ROM on my devices and now doesn´t boot
when i run
[fastboot getvar all]
the CMD respond with this
(bootloader) version: 0.5
(bootloader) version-bootloader: MBM-2.1-lima_32_retail-b64a50bf6-211028
(bootloader) product: lima
(bootloader) board: lima
(bootloader) secure: yes
(bootloader) hwrev: PVT
(bootloader) radio: 2
(bootloader) storage-type: eMMC
(bootloader) emmc: 32GB SAMSUNG 4X6KMB RV=08 PV=00 FV=0000000000000003
(bootloader) ram: 2GB SAMSUNG LP4x DIE=16Gb M5=01 M6=07 M7=01 M8=12
(bootloader) cpu: MT6771V/WL
(bootloader) serialno: ZY2278J5NG
(bootloader) cid: 0x0032
(bootloader) channelid: 0x23
(bootloader) uid: E2BC718F707B06B3000000000000
(bootloader) securestate: oem_locked
(bootloader) factory-modes: disabled
(bootloader) iswarrantyvoid: no
(bootloader) max-download-size: 268435456
(bootloader) reason: No bootable A/B slot
(bootloader) imei:
(bootloader) imei2:
(bootloader) meid:
(bootloader) date: 01-13-2020
(bootloader) sku: XT2015-2
(bootloader) carrier_sku: XT2015-2
(bootloader) battid: SB18C51711
(bootloader) iccid:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Mon Jan 14 15:57:56 UTC 2019"
(bootloader) ro.build.fingerprint[0]: motorola/lima_32/lima:10/QMDS30.47
(bootloader) ro.build.fingerprint[1]: -33-5/7e278:user/release-keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.mtk: alps-mp-q0.mp1.tc2sp-V1.53
(bootloader) version-baseband: <not found>
(bootloader) kernel.version[0]: Linux version 4.14.141+ ([email protected]
(bootloader) kernel.version[1]: build) (gcc version 4.9.x 20150123 (prer
(bootloader) kernel.version[2]: elease) (GCC)) #1 SMP PREEMPT Thu Oct 28
(bootloader) kernel.version[3]: 10:57:32 CDT 2021
(bootloader) frp-state: no protection (0)
(bootloader) ro.carrier: attmx
(bootloader) current-slot: a
(bootloader) running-boot-lun: 0
(bootloader) running-slot: _a
(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
(bootloader) slot-suffixes: _a,_b
(bootloader) slot-count: 2
the problem in this case is tnat i installed a new ROM, at this point all was ok but after that i installed a new one i don´t check correctly the name and i finally installed QMDS30.47-33-5/7e278:user/release-keys0 and my devides accept LIMA_32_PMDS29.70-85-3_subsidy-IUSMXLA_regulatory-XT2015_2_IFETEL_CFC
as the original ROM i don´t understand whats the problem right now ´cause i installed all in the correct order, my conclusion was that i installed a different ROM no compatible with my motorola device and now as it says up here the problem is no bootalbe slot a/b and now is stucked on a no compatible ROM and it doesn´t boot also the OEM is locked and isn´t rootable, someone who can help me pls. i realy need the cellphone its my unic work tool and metod of comunication. THNKS for read
FrxncLpz said:
Help!! I installed a ROM in my moto g8 play and doesn´t respond
Hi to everyone, i have seeing old guide´s to recover urs motorolas devices
my problem is that i installed a different ROM on my devices and now doesn´t boot
when i run
[fastboot getvar all]
the CMD respond with this
(bootloader) version: 0.5
(bootloader) version-bootloader: MBM-2.1-lima_32_retail-b64a50bf6-211028
(bootloader) product: lima
(bootloader) board: lima
(bootloader) secure: yes
(bootloader) hwrev: PVT
(bootloader) radio: 2
(bootloader) storage-type: eMMC
(bootloader) emmc: 32GB SAMSUNG 4X6KMB RV=08 PV=00 FV=0000000000000003
(bootloader) ram: 2GB SAMSUNG LP4x DIE=16Gb M5=01 M6=07 M7=01 M8=12
(bootloader) cpu: MT6771V/WL
(bootloader) serialno: ZY2278J5NG
(bootloader) cid: 0x0032
(bootloader) channelid: 0x23
(bootloader) uid: E2BC718F707B06B3000000000000
(bootloader) securestate: oem_locked
(bootloader) factory-modes: disabled
(bootloader) iswarrantyvoid: no
(bootloader) max-download-size: 268435456
(bootloader) reason: No bootable A/B slot
(bootloader) imei:
(bootloader) imei2:
(bootloader) meid:
(bootloader) date: 01-13-2020
(bootloader) sku: XT2015-2
(bootloader) carrier_sku: XT2015-2
(bootloader) battid: SB18C51711
(bootloader) iccid:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Mon Jan 14 15:57:56 UTC 2019"
(bootloader) ro.build.fingerprint[0]: motorola/lima_32/lima:10/QMDS30.47
(bootloader) ro.build.fingerprint[1]: -33-5/7e278:user/release-keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.mtk: alps-mp-q0.mp1.tc2sp-V1.53
(bootloader) version-baseband: <not found>
(bootloader) kernel.version[0]: Linux version 4.14.141+ ([email protected]
(bootloader) kernel.version[1]: build) (gcc version 4.9.x 20150123 (prer
(bootloader) kernel.version[2]: elease) (GCC)) #1 SMP PREEMPT Thu Oct 28
(bootloader) kernel.version[3]: 10:57:32 CDT 2021
(bootloader) frp-state: no protection (0)
(bootloader) ro.carrier: attmx
(bootloader) current-slot: a
(bootloader) running-boot-lun: 0
(bootloader) running-slot: _a
(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
(bootloader) slot-suffixes: _a,_b
(bootloader) slot-count: 2
the problem in this case is tnat i installed a new ROM, at this point all was ok but after that i installed a new one i don´t check correctly the name and i finally installed QMDS30.47-33-5/7e278:user/release-keys0 and my devides accept LIMA_32_PMDS29.70-85-3_subsidy-IUSMXLA_regulatory-XT2015_2_IFETEL_CFC
as the original ROM i don´t understand whats the problem right now ´cause i installed all in the correct order, my conclusion was that i installed a different ROM no compatible with my motorola device and now as it says up here the problem is no bootalbe slot a/b and now is stucked on a no compatible ROM and it doesn´t boot also the OEM is locked and isn´t rootable, someone who can help me pls. i realy need the cellphone its my unic work tool and metod of comunication. THNKS for read
Click to expand...
Click to collapse
Rescue and Smart Assistant (LMSA)(Motorola/Lenovo Only)
Rescue and Smart Assistant LMSA: Lenovo's Motorola Smart Assistant (PC) For Lenovo and Motorola Devices Only Rescue and Smart Assistant (LMSA) is an official tool installs on PC. Can help to manage smart device (include all Lenovo android phone...
forum.xda-developers.com
sd_shadow said:
Rescue and Smart Assistant (LMSA)(Motorola/Lenovo Only)
Rescue and Smart Assistant LMSA: Lenovo's Motorola Smart Assistant (PC) For Lenovo and Motorola Devices Only Rescue and Smart Assistant (LMSA) is an official tool installs on PC. Can help to manage smart device (include all Lenovo android phone...
forum.xda-developers.com
Click to expand...
Click to collapse
Hi, my motorola is locked on the other ROM so if it searhes the unique ROM that its "available" for my phone is the replacement for the new ROM where its stucked and if y try to use de ROM with CMD doesn´t work. I´m realy stucked on this for a mond. :C

OCX"S"27.1.4 FOTA failed to install TMO - German SIM

Hi,
I got a Moto Z2 Force. It is a T-Mobile US ROM and I think also a TMO device. Not sure if it is a "test sample". I think I have somewhere seen something like "testkeys" or similar.
I bought this via internet - not in a Telekom Store.
So out of my experience from HTC devices - it could be anything.
I use this device in Europe, actually with a Telefonica SIM.
My device get´s a permanent update notification for a OTA which leads into an error: Cannot install OCXS27.1.4. I am actually on OCX27.1.3 BUILD
Note there is no "S" - whatever this means.
This device is not tached from my side. Though I don´t know what the seller has done before.
Baseband is: M8998TMO_20207.117.02.41.02R NUS
So I did not root the device.
There is no unlocked Bootloader, and I do not see the point
Patchlevel is sep. the first 2018
I would like to update to the latest official TMO ROM, shouldn´t be too big of an issue.
On Huawei Devices I updated the OTA manually, with no issues and fast. Or a complete official ROM over an older one.
HTC devices have been easy to update also, if you stay in its path, like official or testkeys, same with regions (regarding ROMs).
Is there a similar way for Motos? This is actually my first Motorola since my MPX 220 (IF anyone nows what I mean)
TMO is XT1789-04 which should be seen by the charging port. You can boot into bootloader and run the command fastboot getvar all to see the status of your phone. I suspect that it is in fact bootloader unlocked and has had a custom logo flashed to hide the bootloader unlocked warning, which also will keep an OTA from installing.
Post the output of the getvar command if you're not sure and I can help you sort it.
Hi,
sorry missed your reply because I did not get an notification. anyway:
fastboot getvar all
(bootloader) kernel: uefi
(bootloader) version-bootloader: MBM-3.0-nash_tmo-1f35305-180905
(bootloader) product: nash
(bootloader) board: nash
(bootloader) secure: yes
(bootloader) hwrev: PVT
(bootloader) radio: NA_UMTS
(bootloader) storage-type: UFS
(bootloader) emmc: N/A
(bootloader) ufs: 64GB SAMSUNG KLUCG4J1ED-B0C1 FV=0200
(bootloader) ram: 4GB SAMSUNG LP4x DIE=16Gb M5=01 M6=06 M7=10 M8=12
(bootloader) cpu: MSM8998 2.1 (0)
(bootloader) serialno: ZY224WX6BN
(bootloader) cid: 0x0015
(bootloader) channelid: 0x85
(bootloader) uid: 1F21F01A
(bootloader) securestate: oem_locked
(bootloader) verity-state: enforcing (0)
(bootloader) iswarrantyvoid: no
(bootloader) max-download-size: 536870912
(bootloader) reason: Volume down key pressed
(bootloader) imei: 356503081281xxx
(bootloader) meid:
(bootloader) date: 03-26-2018
(bootloader) sku: XT1789-04
(bootloader) carrier_sku: XT1789-04
(bootloader) battid: SNN5987A
(bootloader) battery-voltage: 4287
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) ro.build.fingerprint[0]: motorola/nash_tmo_c/nash:8.0.0/OCX
(bootloader) ro.build.fingerprint[1]: 27.109-51-11/4:user/release-keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.27.301.4.nash_tmo_c.
(bootloader) ro.build.version.full[1]: tmo.en.US
(bootloader) ro.build.version.qcom: LA.UM.6.4.r1-04300-8x98.0
(bootloader) version-baseband: M8998TMO_20207.117.02.41.02R NUS
(bootloader) kernel.version[0]: Linux version 4.4.78-perf-g15222f4 (huds
(bootloader) kernel.version[1]: [email protected]) (gcc version 4.9.x 20150
(bootloader) kernel.version[2]: 123 (prerelease) (GCC) ) #1 SMP PREEMPT
(bootloader) kernel.version[3]: Wed Sep 5 05:41:24 CDT 2018
(bootloader) git:abl: MBM-3.0-nash_tmo-1f35305-180905
(bootloader) git:xbl: MBM-3.0-nash_tmo-9869834-180905
(bootloader) gitmic: MBM-3.0-nash_tmo-9869834-180905
(bootloader) git:rpm: MBM-3.0-nash_tmo-b13e14f-180905
(bootloader) git:tz: MBM-3.0-nash_tmo-7d478e6-180905
(bootloader) git:hyp: MBM-3.0-nash_tmo-7d478e6-180905
(bootloader) git:devcfg: MBM-3.0-nash_tmo-7d478e6-180905
(bootloader) git:cmnlib: MBM-3.0-nash_tmo-7d478e6-180905
(bootloader) git:cmnlib64: MBM-3.0-nash_tmo-7d478e6-180905
(bootloader) git:keymaster: MBM-3.0-nash_tmo-7d478e6-180905
(bootloader) git:storsec: MBM-3.0-nash_tmo-7d478e6-180905
(bootloader) gitrov: MBM-3.0-nash_tmo-7d478e6-180905
(bootloader) qe: "qe 0/0"
(bootloader) frp-state: protected (77)
(bootloader) ro.carrier: tmo
(bootloader) current-slot: _b
(bootloader) running-bl-slot: _b/_b
(bootloader) running-boot-lun: 3
(bootloader) slot-suffixes: _a,_b
(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: 7
(bootloader) slot-retry-count:_b: 6
all: listed above
Finished. Total time: 0.109s
I do not have any marking on my device, like the TMO XT ....
Does "PVT" has anything to say? Hardware Revision - I think.
Looks pretty clean, the easiest way would be to use lenovo moto smart assistant to upgrade.
Mtot Device manager says:
There is no noew software for my device.
Current version:
N/A
Not a good sign. The Software does´t read my device at all.
41rw4lk said:
Looks pretty clean, the easiest way would be to use lenovo moto smart assistant to upgrade.
Click to expand...
Click to collapse
So I actually misunderstood the Moto Software tool you ment. When I googled I found "Motorola Device Manager". You ment - obviously "Lenovo moto smart assistant", which, interestingly is a totally different software. Maybe this has something to do with regions. I don´t know.
To round up this thread:
I read twice, searched the Tool you ment (the US version, although I use an EU SIM), it installed nicely and connected correctly to my device. It found the latest update and updated directly to the lastet. From .4 to version .7. So the file had a size of 2GB.
Although the software (LMSA) says differently, it does NOT wipe my device.
Edit: Connection to my PC did NOT work via USB 3.0! Interestingly it worked via a keyboard extend USB Hub 2.0 though.

[HELP] (bootloader) Permission denied.

EDIT: SOLVED* (can delete)
Type:
Code:
fastboot flashing unlock
then flash as usual....phewww
I was trying to revert to stock Android from a custom rom with an unlocked bootloader.
Something happened that the bootloader re-locked but did not flash the stock firmware properly. (using this signed image: https://forum.xda-developers.com/moto-z-play/how-to/guide-relock-oreo-bootloader-to-stock-t3784621)
Problem #1 seems to be that I cannot flash anything because the bootloader re-locked.
Problem #2 seems to be that I cannot unlock the bootloader either because the phone is in an "invalid boot state" meaning "Allow OEM Unlocking" is supposedly not enabled in Settings > Developer.
Problem #3: When I go into Recovery Mode the device reads "I have loaded a different operating system"
Here is my getvar all:
Code:
[HIDE](bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) version: 0.5
(bootloader) version-bootloader: moto-msm8953-C1.82
(bootloader) product: addison
(bootloader) board: addison
(bootloader) secure: yes
(bootloader) hwrev: P7
(bootloader) radio: 2
(bootloader) storage-type: emmc
(bootloader) emmc: 32GB SAMSUNG RX1BMB RV=08 PV=07 FV=0000000000000007
(bootloader) ram: 3GB SAMSUNG LP3 DIE=6Gb M5=01 M6=05 M7=00 M8=7B
(bootloader) cpu: MSM8953
(bootloader) serialno: #####
(bootloader) cid: 0x0032
(bootloader) channelid: 0x8f
(bootloader) uid: 5CC656CD00000000000000000000
(bootloader) securestate: flashing_locked
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 534773760
(bootloader) reason: Reboot mode set to fastboot
(bootloader) imei: #######
(bootloader) meid:
(bootloader) date: 08-30-2016
(bootloader) sku: XT1635-02
(bootloader) battid: SNN5974A
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Thu Jan 1 3:48:49 UTC 1970"
(bootloader) ro.build.fingerprint: <not found>
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full: <not found>
(bootloader) ro.build.version.qcom: LA.UM.6.6.r1-04400-89xx.0
(bootloader) version-baseband: <not found>
(bootloader) kernel.version[0]: Linux version 3.18.71-perf-g174984b (hud
(bootloader) kernel.version[1]: [email protected]) (gcc version 4.9.x 2015
(bootloader) kernel.version[2]: 0123 (prerelease) (GCC) ) #1 SMP PREEMPT
(bootloader) kernel.version[3]: Mon Mar 26 08:27:14 CDT 2018
(bootloader) sbl1.git: git=MBM-NG-VC1.82-0-g3523998
(bootloader) rpm.git: git=bd19194
(bootloader) tz.git: git=fbd9875-dirty
(bootloader) devcfg.git: git=fbd9875-dirty
(bootloader) keymaster.git: git=fbd9875-dirty
(bootloader) cmnlib.git: git=fbd9875-dirty
(bootloader) cmnlib64.git: git=fbd9875-dirty
(bootloader) prov.git: git=fbd9875-dirty
(bootloader) aboot.git: git=MBM-NG-VC1.82-0-g345bd7e
(bootloader) frp-state: no protection (0)
(bootloader) ro.carrier: rcica
all: listed above
finished. total time: 0.322s[/HIDE]
Anyone have any ideas? On how I can get this phone to boot? I don't really care how I get it back to boot, even if its back to a custom rom, at this point I just want it to POST a boot.
I tried the Lenovo Rescue and Smart Assistant tool but the software could not recognise the device.
I was looking at RSD LITE tool. I never used this. Anyone have any experience with this tool?
mzp_user said:
EDIT: SOLVED* (can delete)
Type:
Code:
fastboot flashing unlock
then flash as usual....phewww
I was trying to revert to stock Android from a custom rom with an unlocked bootloader.
Something happened that the bootloader re-locked but did not flash the stock firmware properly. (using this signed image: https://forum.xda-developers.com/moto-z-play/how-to/guide-relock-oreo-bootloader-to-stock-t3784621)
Problem #1 seems to be that I cannot flash anything because the bootloader re-locked.
Problem #2 seems to be that I cannot unlock the bootloader either because the phone is in an "invalid boot state" meaning "Allow OEM Unlocking" is supposedly not enabled in Settings > Developer.
Problem #3: When I go into Recovery Mode the device reads "I have loaded a different operating system"
Here is my getvar all:
Code:
[HIDE](bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) version: 0.5
(bootloader) version-bootloader: moto-msm8953-C1.82
(bootloader) product: addison
(bootloader) board: addison
(bootloader) secure: yes
(bootloader) hwrev: P7
(bootloader) radio: 2
(bootloader) storage-type: emmc
(bootloader) emmc: 32GB SAMSUNG RX1BMB RV=08 PV=07 FV=0000000000000007
(bootloader) ram: 3GB SAMSUNG LP3 DIE=6Gb M5=01 M6=05 M7=00 M8=7B
(bootloader) cpu: MSM8953
(bootloader) serialno: #####
(bootloader) cid: 0x0032
(bootloader) channelid: 0x8f
(bootloader) uid: 5CC656CD00000000000000000000
(bootloader) securestate: flashing_locked
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 534773760
(bootloader) reason: Reboot mode set to fastboot
(bootloader) imei: #######
(bootloader) meid:
(bootloader) date: 08-30-2016
(bootloader) sku: XT1635-02
(bootloader) battid: SNN5974A
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Thu Jan 1 3:48:49 UTC 1970"
(bootloader) ro.build.fingerprint: <not found>
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full: <not found>
(bootloader) ro.build.version.qcom: LA.UM.6.6.r1-04400-89xx.0
(bootloader) version-baseband: <not found>
(bootloader) kernel.version[0]: Linux version 3.18.71-perf-g174984b (hud
(bootloader) kernel.version[1]: [email protected]) (gcc version 4.9.x 2015
(bootloader) kernel.version[2]: 0123 (prerelease) (GCC) ) #1 SMP PREEMPT
(bootloader) kernel.version[3]: Mon Mar 26 08:27:14 CDT 2018
(bootloader) sbl1.git: git=MBM-NG-VC1.82-0-g3523998
(bootloader) rpm.git: git=bd19194
(bootloader) tz.git: git=fbd9875-dirty
(bootloader) devcfg.git: git=fbd9875-dirty
(bootloader) keymaster.git: git=fbd9875-dirty
(bootloader) cmnlib.git: git=fbd9875-dirty
(bootloader) cmnlib64.git: git=fbd9875-dirty
(bootloader) prov.git: git=fbd9875-dirty
(bootloader) aboot.git: git=MBM-NG-VC1.82-0-g345bd7e
(bootloader) frp-state: no protection (0)
(bootloader) ro.carrier: rcica
all: listed above
finished. total time: 0.322s[/HIDE]
Anyone have any ideas? On how I can get this phone to boot? I don't really care how I get it back to boot, even if its back to a custom rom, at this point I just want it to POST a boot.
I tried the Lenovo Rescue and Smart Assistant tool but the software could not recognise the device.
I was looking at RSD LITE tool. I never used this. Anyone have any experience with this tool?
Click to expand...
Click to collapse
I'm having the same problem. Did you find any solution?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Moto z2 Force stuck on boot loop xt1789-06 dual sim 6gb

hello xda members,
My name is Peter Marx . I live actually in Peru ... I hope someone can help me i would support with pay pal fee
mi phone stucks on bootloop... i have tried to wipe out data but
After selecting in bootloader factory reset , the phone reboot. (loop)
After selecting in bootloader recovery mode, the phone reboot, (loop)
After selecting in bootloader BPtools , the phone reboot.(loop)
I only can only enable and disable *switch tools mode*
Phone especificacion xt1789-06 dual sim !!! Buyed in Peru second hand 2 years ago.. seller had buyed it from store in peru
i have tried to add pictures but it dont work i send url ibb.co/HzRfNF7
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I need only a little tutorial how to flash and which version of rom to use with links ... its dual sim ... and which tools to use ... i can support with paypal
i hope i have a good solution from someone thanks
perawima said:
hello xda members,
My name is Peter Marx . I live actually in Peru ... I hope someone can help me i would support with pay pal fee
mi phone stucks on bootloop... i have tried to wipe out data but
After selecting in bootloader factory reset , the phone reboot. (loop)
After selecting in bootloader recovery mode, the phone reboot, (loop)
After selecting in bootloader BPtools , the phone reboot.(loop)
I only can only enable and disable *switch tools mode*
Phone especificacion xt1789-06 dual sim !!! Buyed in Peru second hand 2 years ago.. seller had buyed it from store in peru
i have tried to add pictures but it dont work i send url ibb.co/HzRfNF7
I need only a little tutorial how to flash and which version of rom to use with links ... its dual sim ... and which tools to use ... i can support with paypal
i hope i have a good solution from someone thanks
Click to expand...
Click to collapse
I would try LMSA's Flash Rescue
https://forum.xda-developers.com/general/general/update-moto-lenovo-moto-smart-assistant-t3951714
If that doesn't work what does getvar all say?
Code:
fastboot getvar all
https://forum.xda-developers.com/general/rooting-roms/guide-flashing-motorola-firmware-t4042039
Sent from my Moto E (4) using Tapatalk
sd_shadow said:
I would try LMSA's Flash Rescue
https://forum.xda-developers.com/general/general/update-moto-lenovo-moto-smart-assistant-t3951714
If that doesn't work what does getvar all say?
Code:
fastboot getvar all
https://forum.xda-developers.com/general/rooting-roms/guide-flashing-motorola-firmware-t4042039
Sent from my Moto E (4) using Tapatalk
Click to expand...
Click to collapse
thanks for the reply
i was trying with Rescue and Smart Assistant version 5.3.0
in rescue (fastboot mode) after selecting product name and model i receive: unable to match the appropiate firmware some key information cannot be read from the device
getvar says :
C:\platform-tools>fastboot getvar all
(bootloader) kernel: uefi
(bootloader) version-bootloader: MBM-3.0-nash_retail-43c7c77-190920
(bootloader) product: nash
(bootloader) board: nash
(bootloader) secure: yes
(bootloader) hwrev: PVT
(bootloader) radio: EMEA
(bootloader) storage-type: UFS
(bootloader) emmc: N/A
(bootloader) ufs: 64GB SAMSUNG KLUCG4J1ED-B0C1 FV=0200
(bootloader) ram: 6GB SAMSUNG LP4x DIE=12Gb M5=01 M6=06 M7=00 M8=0E
(bootloader) cpu: MSM8998 2.1 (0)
(bootloader) serialno: ZY224GPDJ3
(bootloader) cid: 0x0032
(bootloader) channelid: 0x40
(bootloader) uid: BC73665A
(bootloader) securestate: oem_locked
(bootloader) verity-state: enforcing (0)
(bootloader) iswarrantyvoid: no
(bootloader) max-download-size: 536870912
(bootloader) reason: Volume down key pressed
(bootloader) imei: xxx5xxx8xxx5xxx
(bootloader) meid:
(bootloader) date: 09-19-2017
(bootloader) sku: XT1789-06
(bootloader) carrier_sku:
(bootloader) battid: SNN5987A
(bootloader) battery-voltage: 4044
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) ro.build.fingerprint[0]: motorola/nash/nash:9/PPX29.159-24/
(bootloader) ro.build.fingerprint[1]: e78f1:user/release-keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.29.11.24.nash.retail
(bootloader) ro.build.version.full[1]: .en.US
(bootloader) ro.build.version.qcom: LA.UM.7.2.r1-06500-sdm660.0
(bootloader) version-baseband: <not found>
(bootloader) kernel.version[0]: Linux version 4.4.153-perf-g1f14820 (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 Fri Sep 20 09:23:35 CDT 2019
(bootloader) git:abl: MBM-3.0-nash_retail-43c7c77-190920
(bootloader) git:xbl: MBM-3.0-nash_retail-4fc2afc-190920
(bootloader) gitmic: MBM-3.0-nash_retail-4fc2afc-190920
(bootloader) git:rpm: MBM-3.0-nash_retail-404f7ba-190920
(bootloader) git:tz: MBM-3.0-nash_retail-3537781-190920
(bootloader) git:hyp: MBM-3.0-nash_retail-3537781-190920
(bootloader) git:devcfg: MBM-3.0-nash_retail-3537781-190920
(bootloader) git:cmnlib: MBM-3.0-nash_retail-3537781-190920
(bootloader) git:cmnlib64: MBM-3.0-nash_retail-3537781-190920
(bootloader) git:keymaster: MBM-3.0-nash_retail-3537781-190920
(bootloader) git:storsec: MBM-3.0-nash_retail-3537781-190920
(bootloader) gitrov: MBM-3.0-nash_retail-3537781-190920
(bootloader) frp-state: protected (144)
(bootloader) ro.carrier: reteu
(bootloader) current-slot: a
(bootloader) running-bl-slot: _a/_a
(bootloader) running-boot-lun: 2
(bootloader) slot-count: 2
(bootloader) slot-successful:_a: yes
(bootloader) slot-successful:_b: yes
(bootloader) slot-unbootable:_a: no
(bootloader) slot-unbootable:_b: no
(bootloader) slot-retry-count:_a: 6
(bootloader) slot-retry-count:_b: 6
all: listed above
Finished. Total time: 0.167s
THANKS for the HELP
Dear members experts, what would be next step ? thsi phone is dual sim should i download a special rom ?
Hy, I have a
Motorola Moto Z2 Force XT1789-4 64G T-MOBILE.
After having installed
lineage-16.0-20191217-recovery-nash.img
the phone was stuck in a boot loop and I accidentally relocked the boot loader.
Is there a rescue procedure?
Txs
Aleha10 said:
Hy, I have a
Motorola Moto Z2 Force XT1789-4 64G T-MOBILE.
After having installed
lineage-16.0-20191217-recovery-nash.img
the phone was stuck in a boot loop and I accidentally relocked the boot loader.
Is there a rescue procedure?
Txs
Click to expand...
Click to collapse
I think you can try flashing stock TMO oreo. Official firmwares can be flashed even if you have locked bootloader

Question Australian Moto G30 stock rom

Hi.
I've just bought an unlocked Austarlian model Moto G30. I'd like to install Magisk but I'm having trouble locating a stock rom. No roms are found either by searching, normal connection or fastboot connection by the Lenovo Rescue and Smart Assistance app. A dump from fastboot reads as follows (with serial numbers, IMEIs omitted):
C:\adb>fastboot getvar all
(bootloader) kernel: uefi
(bootloader) version-bootloader: MBM-3.0-caprip_retail-7d6811cfd7-210209
(bootloader) product: caprip
(bootloader) board: caprip
(bootloader) secure: yes
(bootloader) hwrev: PVT
(bootloader) radio: EUAPEM
(bootloader) storage-type: eMMC
(bootloader) emmc: 128GB SAMSUNG DV6DAB RV=08 PV=02 FV=0000000000000002
(bootloader) ufs: N/A
(bootloader) ram: 4GB SAMSUNG LP4x DIE=16Gb M5-M8=01 07 01 12
(bootloader) cpu: SM_KAMORTA_H 1.0
(bootloader) serialno: *****
(bootloader) cid: 0x0032
(bootloader) channelid: 0x51
(bootloader) uid: 1AFA7FED
(bootloader) securestate: oem_locked
(bootloader) factory-modes: disabled
(bootloader) verity-state: enforcing (0)
(bootloader) iswarrantyvoid: no
(bootloader) max-download-size: 804474880
(bootloader) reason: Reboot mode set to fastboot
(bootloader) imei: *****
(bootloader) imei2: *****
(bootloader) meid:
(bootloader) date: 07-21-2021
(bootloader) sku: XT2129-2
(bootloader) carrier_sku: XT2129-2
(bootloader) battid: SB18C98449
(bootloader) battery-voltage: 3976
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) poweroffalarm: 0
(bootloader) ro.carrier: retapac
(bootloader) ro.build.fingerprint[0]: motorola/caprip_retailn/caprip:11/
(bootloader) ro.build.fingerprint[1]: RRC31.Q1-3-34-1/7ff77b:user/releas
(bootloader) ro.build.fingerprint[2]: e-keys
(bootloader) ro.build.version.qcom: LA.UM.9.15.r1-01800-KAMORTA.0
(bootloader) version-baseband[0]: HAK10_18.534.02.65R CAPRIP_EUAPEMDSDS_
(bootloader) version-baseband[1]: CUST
(bootloader) kernel.version[0]: Linux version 4.19.136-perf+ ([email protected]
(bootloader) kernel.version[1]: roid-build) (clang version 10.0.7 for An
(bootloader) kernel.version[2]: droid NDK, GNU ld (binutils-2.27-bd24d23
(bootloader) kernel.version[3]: f) 2.27.0.20170315) #1 SMP PREEMPT Tue F
(bootloader) kernel.version[4]: eb 9 10:48:17 CST 2021
(bootloader) git:xbl: MBM-3.0-caprip_retail-e9fd6e369-210209
(bootloader) git:xbl_config: MBM-3.0-caprip_retail-e9fd6e369-210209
(bootloader) git:abl: MBM-3.0-caprip_retail-7d6811cfd7-210209
(bootloader) git:rpm: MBM-3.0-caprip_retail-f43cd45-210209
(bootloader) git:tz: MBM-3.0-caprip_retail-dc0cdb2b-210209
(bootloader) git:hyp: MBM-3.0-caprip_retail-dc0cdb2b-210209
(bootloader) git:devcfg: MBM-3.0-caprip_retail-dc0cdb2b-210209
(bootloader) git:keymaster: MBM-3.0-caprip_retail-a2e51bf-210209
(bootloader) git:storsec: MBM-3.0-caprip_retail-a2e51bf-210209
(bootloader) git:uefisecapp: MBM-3.0-caprip_retail-a2e51bf-210209
(bootloader) gitrov: MBM-3.0-caprip_retail-dc0cdb2b-210209
(bootloader) git:qupfw: MBM-3.0-caprip_retail-349f4d1-210209
(bootloader) frp-state: no protection (0)
(bootloader) current-slot: a
(bootloader) running-bl-slot: _a/_a
(bootloader) running-boot-lun: 0
(bootloader) slot-count: 2
(bootloader) slot-successful:_a: yes
(bootloader) slot-successful:_b: no
(bootloader) slot-unbootable:_a: no
(bootloader) slot-unbootable:_b: no
(bootloader) slot-retry-count:_a: 7
(bootloader) slot-retry-count:_b: 0
(bootloader) logical-block-size: 0x200
(bootloader) erase-block-size: 0x200
(bootloader) is-userspace: no
(bootloader) pcb-part-no: SP69A6PBEP
(bootloader) primary-display: djn_nt36525c_652_vid_display
(bootloader) secondary-display:
all: listed above
finished. total time: 0.244s
​So far I've only managed to find one site (under a couple different names/addresses) that has the (bootloader) ro.build.fingerprint[1] and (bootloader) ro.build.fingerprint[2] strings of:
RRC31.Q1-3-34-1/7ff77b:user/release-keys
It doesn't look like the file has been downloaded at all so I'm a little dubious. Can anyone possibly point me to a surer source, or another stock rom that has worked with an Australian moto g30 and Magisk?
Cheers.
cedwich said:
Hi.
I've just bought an unlocked Austarlian model Moto G30. I'd like to install Magisk but I'm having trouble locating a stock rom. No roms are found either by searching, normal connection or fastboot connection by the Lenovo Rescue and Smart Assistance app. A dump from fastboot reads as follows (with serial numbers, IMEIs omitted):
C:\adb>fastboot getvar all
(bootloader) kernel: uefi
(bootloader) version-bootloader: MBM-3.0-caprip_retail-7d6811cfd7-210209
(bootloader) product: caprip
(bootloader) board: caprip
(bootloader) secure: yes
(bootloader) hwrev: PVT
(bootloader) radio: EUAPEM
(bootloader) storage-type: eMMC
(bootloader) emmc: 128GB SAMSUNG DV6DAB RV=08 PV=02 FV=0000000000000002
(bootloader) ufs: N/A
(bootloader) ram: 4GB SAMSUNG LP4x DIE=16Gb M5-M8=01 07 01 12
(bootloader) cpu: SM_KAMORTA_H 1.0
(bootloader) serialno: *****
(bootloader) cid: 0x0032
(bootloader) channelid: 0x51
(bootloader) uid: 1AFA7FED
(bootloader) securestate: oem_locked
(bootloader) factory-modes: disabled
(bootloader) verity-state: enforcing (0)
(bootloader) iswarrantyvoid: no
(bootloader) max-download-size: 804474880
(bootloader) reason: Reboot mode set to fastboot
(bootloader) imei: *****
(bootloader) imei2: *****
(bootloader) meid:
(bootloader) date: 07-21-2021
(bootloader) sku: XT2129-2
(bootloader) carrier_sku: XT2129-2
(bootloader) battid: SB18C98449
(bootloader) battery-voltage: 3976
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) poweroffalarm: 0
(bootloader) ro.carrier: retapac
(bootloader) ro.build.fingerprint[0]: motorola/caprip_retailn/caprip:11/
(bootloader) ro.build.fingerprint[1]: RRC31.Q1-3-34-1/7ff77b:user/releas
(bootloader) ro.build.fingerprint[2]: e-keys
(bootloader) ro.build.version.qcom: LA.UM.9.15.r1-01800-KAMORTA.0
(bootloader) version-baseband[0]: HAK10_18.534.02.65R CAPRIP_EUAPEMDSDS_
(bootloader) version-baseband[1]: CUST
(bootloader) kernel.version[0]: Linux version 4.19.136-perf+ ([email protected]
(bootloader) kernel.version[1]: roid-build) (clang version 10.0.7 for An
(bootloader) kernel.version[2]: droid NDK, GNU ld (binutils-2.27-bd24d23
(bootloader) kernel.version[3]: f) 2.27.0.20170315) #1 SMP PREEMPT Tue F
(bootloader) kernel.version[4]: eb 9 10:48:17 CST 2021
(bootloader) git:xbl: MBM-3.0-caprip_retail-e9fd6e369-210209
(bootloader) git:xbl_config: MBM-3.0-caprip_retail-e9fd6e369-210209
(bootloader) git:abl: MBM-3.0-caprip_retail-7d6811cfd7-210209
(bootloader) git:rpm: MBM-3.0-caprip_retail-f43cd45-210209
(bootloader) git:tz: MBM-3.0-caprip_retail-dc0cdb2b-210209
(bootloader) git:hyp: MBM-3.0-caprip_retail-dc0cdb2b-210209
(bootloader) git:devcfg: MBM-3.0-caprip_retail-dc0cdb2b-210209
(bootloader) git:keymaster: MBM-3.0-caprip_retail-a2e51bf-210209
(bootloader) git:storsec: MBM-3.0-caprip_retail-a2e51bf-210209
(bootloader) git:uefisecapp: MBM-3.0-caprip_retail-a2e51bf-210209
(bootloader) gitrov: MBM-3.0-caprip_retail-dc0cdb2b-210209
(bootloader) git:qupfw: MBM-3.0-caprip_retail-349f4d1-210209
(bootloader) frp-state: no protection (0)
(bootloader) current-slot: a
(bootloader) running-bl-slot: _a/_a
(bootloader) running-boot-lun: 0
(bootloader) slot-count: 2
(bootloader) slot-successful:_a: yes
(bootloader) slot-successful:_b: no
(bootloader) slot-unbootable:_a: no
(bootloader) slot-unbootable:_b: no
(bootloader) slot-retry-count:_a: 7
(bootloader) slot-retry-count:_b: 0
(bootloader) logical-block-size: 0x200
(bootloader) erase-block-size: 0x200
(bootloader) is-userspace: no
(bootloader) pcb-part-no: SP69A6PBEP
(bootloader) primary-display: djn_nt36525c_652_vid_display
(bootloader) secondary-display:
all: listed above
finished. total time: 0.244s
​So far I've only managed to find one site (under a couple different names/addresses) that has the (bootloader) ro.build.fingerprint[1] and (bootloader) ro.build.fingerprint[2] strings of:
RRC31.Q1-3-34-1/7ff77b:user/release-keys
It doesn't look like the file has been downloaded at all so I'm a little dubious. Can anyone possibly point me to a surer source, or another stock rom that has worked with an Australian moto g30 and Magisk?
Cheers.
Click to expand...
Click to collapse
I think you know this but
You look for these lines
Code:
sku: XT2129-2
ro.carrier: retapac
product: caprip
ro.build.fingerprint:...RRC31.Q1-3-34-1/...
and
Code:
imei: *****
imei2: *****
Means you have Dual sim, there may be firmware that is for a single sim, you do not want to use that.
There a few sources for stock moto firmware.
I prefer LMSA, it is the official Moto flashing program for Windows
The 2 other sources I like are run by the same people
lolinet mirrors - firmware, software, iso etc.
lolinet mirrors - powered by h5ai
mirrors.lolinet.com
and
Moto Updates Tracker
An automated channel that tracks Motorola updates releases. By @vachounet and @yshalsager https://mirrors.lolinet.com/firmware/motorola More automated channels that you may like: @yshalsager_projects
t.me
Looks like you are running an older build and lolinet may have removed it already, you could use a newer version
you will need to flash the full firmware.
Moto Update Tracker has this
Codename: #capri
Carrier(s): Australia
Phone Model(s): XT2127-2-DS/PAMN0016AU
Version: RRBS31.Q1-3-34-1-2
Android: 11
Download: Here
Click to expand...
Click to collapse
CAPRI_RETAIL_RRBS31.Q1-3-34-1-2_subsidy-DEFAULT_regulatory-XT2127-2-APEM-SAR_CFC.xml.zip
again if you have a Windows PC I recommend LMSA
Rescue and Smart Assistant (LMSA)(Motorola/Lenovo Only)
Rescue and Smart Assistant LMSA: Lenovo's Motorola Smart Assistant (PC) For Lenovo and Motorola Devices Only Rescue and Smart Assistant (LMSA) is an official tool installs on PC. Can help to manage smart device (include all Lenovo android phone...
forum.xda-developers.com
sd_shadow said:
I think you know this but
You look for these lines
Code:
sku: XT2129-2
ro.carrier: retapac
product: caprip
ro.build.fingerprint:...RRC31.Q1-3-34-1/...
and
Code:
imei: *****
imei2: *****
Means you have Dual sim, there may be firmware that is for a single sim, you do not want to use that.
There a few sources for stock moto firmware.
I prefer LMSA, it is the official Moto flashing program for Windows
The 2 other sources I like are run by the same people
lolinet mirrors - firmware, software, iso etc.
lolinet mirrors - powered by h5ai
mirrors.lolinet.com
and
Moto Updates Tracker
An automated channel that tracks Motorola updates releases. By @vachounet and @yshalsager https://mirrors.lolinet.com/firmware/motorola More automated channels that you may like: @yshalsager_projects
t.me
Looks like you are running an older build and lolinet may have removed it already, you could use a newer version
you will need to flash the full firmware.
Moto Update Tracker has this
CAPRI_RETAIL_RRBS31.Q1-3-34-1-2_subsidy-DEFAULT_regulatory-XT2127-2-APEM-SAR_CFC.xml.zip
again if you have a Windows PC I recommend LMSA
Rescue and Smart Assistant (LMSA)(Motorola/Lenovo Only)
Rescue and Smart Assistant LMSA: Lenovo's Motorola Smart Assistant (PC) For Lenovo and Motorola Devices Only Rescue and Smart Assistant (LMSA) is an official tool installs on PC. Can help to manage smart device (include all Lenovo android phone...
forum.xda-developers.com
Click to expand...
Click to collapse
Awesome, many thanks for your help and suggestions, i'll definately take them on board. I tried the LMSA tool straight up and it couldn't find any compatable stock roms via either usb debug or fastboot. I also couldn't find anything searching by name. I did trying searching a few sites for stock roms but the phone doesn't show system updates as being available so i didn"t think to search on more recent versions. *blushes* Thanks again for your digging, you've hopefully helped save me a few more grey hairs!

Categories

Resources