So I tried to flash a custom recovery and rom but when I flashed my rom it booted to boot loader and it said oem_locked when I had it unlocked 2 minutes ago. So I try to go into twrp and I can’t, says start up failed. I tried using the software but it said it can’t identify my device and it can’t fix anything. I also tried to flash stock rom via and but it said it can’t find and can’t mount any partitions. This leads me to believe that my partitions are gone or corrupt. Can anyone help? Im not sure the model number but I know the phone is a Moto g7 Power from t-mobile that was completely unlocked, boot loader and all.
Can you get into fastboot mode? Try using the command, fastboot getvar all, it should give you information about partitions available.
Try flashing one image at a time.
You probably need to use an unbrick firmware and (100)% the correct driver.
An unbrick software will format your device ssd and create all the partitions again.
JonasHS said:
Can you get into fastboot mode? Try using the command, fastboot getvar all, it should give you information about partitions available.
Try flashing one image at a time.
You probably need to use an unbrick firmware and (100)% the correct driver.
An unbrick software will format your device ssd and create all the partitions again.
Click to expand...
Click to collapse
I ran getvar and it spat out this.
(bootloader) version: 0.5
(bootloader) version-bootloader: MBM-2.1-ocean_t-16222030b3b-210202
(bootloader) product: ocean
(bootloader) board: ocean
(bootloader) secure: yes
(bootloader) hwrev: PVT1
(bootloader) radio: 1
(bootloader) storage-type: emmc
(bootloader) emmc: 32GB SKHYNIX hB8aP> RV=08 PV=03 FV=0000000034303030
(bootloader) ram: 3GB SKHYNIX LP3 DIE=8Gb M5=06 M6=03 M7=01 M8=5F
(bootloader) cpu: SDM632
(bootloader) serialno: 751d40d
(bootloader) cid: 0xDEAD
(bootloader) channelid: 0x00
(bootloader) uid: 0000000000000000000000000000
(bootloader) securestate: oem_locked
(bootloader) factory-modes: disabled
(bootloader) iswarrantyvoid: n/a
(bootloader) max-download-size: 536870912
(bootloader) reason: Failed to initialize partition table
(bootloader) imei:
(bootloader) imei2:
(bootloader) meid:
(bootloader) date:
(bootloader) sku:
(bootloader) carrier_sku:
(bootloader) battid:
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time:
(bootloader) ro.build.fingerprint:
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full:
(bootloader) ro.build.version.qcom:
(bootloader) version-baseband:
(bootloader) kernel.version:
(bootloader) sbl1.git: sbl1.git
(bootloader) rpm.git: rpm.git
(bootloader) tz.git: tz.git
(bootloader) devcfg.git: devcfg.git
(bootloader) keymaster.git: keymaster.git
(bootloader) cmnlib.git: cmnlib.git
(bootloader) cmnlib64.git: cmnlib64.git
(bootloader) prov.git: prov.git
(bootloader) aboot.git: MBM-2.1-ocean_t-16222030b3b-210202
(bootloader) frp-state: no protection (err)
(bootloader) ro.carrier:
(bootloader) current-slot:
(bootloader) running-boot-lun: must + g->mlen
(bootloader) running-slot:
(bootloader) slot-suffixes: _a
(bootloader) slot-count: 1
(bootloader) slot-successful:_a: INVALID
(bootloader) slot-successful:_b: INVALID
(bootloader) slot-bootable:_a: INVALID
(bootloader) slot-bootable:_b: INVALID
(bootloader) slot-retry-count:_a: unknown
(bootloader) slot-retry-count:_b: unknown
(bootloader) pcb-part-no:
Also when I try to run Motorola's software it does this
The second picture is what it says when I try to use manual. I click use anyway and it just goes back to saying not appropriate firmware.
Also trying to install the images one by one also didnt work.
Unbrick tools
Have your phone edl mode? Snapdragon =Qualcomm?
Once you have installed custom ROM, your partition should not be the same a / b order.
You are need to use moto's unbrick tool in edl.
JonasHS said:
Once you have installed custom ROM, your partition should not be the same a / b order.
You are need to use moto's unbrick tool in edl.
Click to expand...
Click to collapse
I tried to get into Edl mode but my phone doesn't have Edl mode
also that was Motorola's unbrick tool and it didn't work.
Your CPU is Qualcomm Snapdragon. You have it. Edl is same some bios on PC. Is built in your phone. Try to boot into it, your are need PC and USB and driver for edl.
I hope you know then you are in edl mode have your phone black screen.
JonasHS said:
Your CPU is Qualcomm Snapdragon. You have it. Edl is same some bios on PC. Is built in your phone. Try to boot into it, your are need PC and USB and driver for edl.
I hope you know then you are in edl mode have your phone black screen.
Click to expand...
Click to collapse
I tried. It said unknown command. I patched the fastboot exe to tell it to go to edl mode and it says unknown command.
that_one_gamer said:
I tried. It said unknown command. I patched the fastboot exe to tell it to go to edl mode and it says unknown command.
Click to expand...
Click to collapse
I have the driver and everything. Doesn’t work.
Fastboot can't reboot you into edl, you are need to connect phone to USB to PC and hold vol - and vol+ and power on same time and see device on PC
Have you never used del before?
JonasHS said:
Have you never used del before?
Click to expand...
Click to collapse
I tried doing that and it just goes to the boot loader.
JonasHS said:
Click to expand...
Click to collapse
That’s not edl mode. That’s bootloader. Plus that’s what I did and the software didn’t work. I included screenshots in one of the other reply’s.
You don't understand How did you think android come on SSD. Factory install it with download mode.
JonasHS said:
You don't understand How did you think android come on SSD. Factory install it with download mode.
Click to expand...
Click to collapse
I do understand, the software does not allow me to reflash with download mode. If I try to reflash manually it fails because partitions cannot be mounted.
This is what the software says
that_one_gamer said:
This is what the software says
Click to expand...
Click to collapse
Look at the screenshots. And I also cannot access recovery mode.
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 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?
Flashed TWRP now I have no recovery at all and it just reboots when I try going to recovery on Moto G Power.
I got the zip from the Moto TWRP thread and it's twrp 3.5 supposedly the latest.
I've been flashing it with the file on my PC "fastboot flash recovery c:\recovery.img" where can I place the recovery on my phone so I can flash it from the phone. I don't know the path for the phone directories so can't qualify its pathname on the phone.
piiman said:
Flashed TWRP now I have no recovery at all and it just reboots when I try going to recovery on Moto G Power.
I got the zip from the Moto TWRP thread and it's twrp 3.5 supposedly the latest.
I've been flashing it with the file on my PC "fastboot flash recovery c:\recovery.img" where can I place the recovery on my phone so I can flash it from the phone. I don't know the path for the phone directories so can't qualify its pathname on the phone.
Click to expand...
Click to collapse
I'm having something close to this, though mine is blackview. I'm guessing this is a new problem as mine happen about a week now and I've gat sleepless night ransacking the internet with no success yet.
I unlocked my BV9600pro with Android8.1 bootloader using fastboot then flashed on it TWRP before I learnt I just could have patched the Boot.img and flash in to get root, which I’ve done, now the device is rooted and when I’m trying to boot to recovery it display Orange State and goes to No Command screen.
I have tried some keys combinations on the No Command screen like the Vol+ and Power button but the device booted to bootloader options and when I selected recovery mode again I was back to Orange State and to no command, then I tried vol- and power button but that booted to Orange State then normal boot.
I edited lk.img and flashed on my bv9600pro it just remove the Orange State Display but won't still give access to recovery, I had to reflash on the device the stock lk.img and stock recovery.img and still can't boot to recovery. I'm guessing it's all as a result of the unlocking. Please any other way to fix this to enable me access recovery with the root?
I actually want to have the TWRP on the device to allow Nandroid backup and eaisily flashing on the device my custom ROMs.
piiman said:
Flashed TWRP now I have no recovery at all and it just reboots when I try going to recovery on Moto G Power.
I got the zip from the Moto TWRP thread and it's twrp 3.5 supposedly the latest.
I've been flashing it with the file on my PC "fastboot flash recovery c:\recovery.img" where can I place the recovery on my phone so I can flash it from the phone. I don't know the path for the phone directories so can't qualify its pathname on the phone.
Click to expand...
Click to collapse
What does getvar all say?
Code:
fastboot getvar all
Rukkyakakporo said:
I'm having something close to this, though mine is blackview. I'm guessing this is a new problem as mine happen about a week now and I've gat sleepless night ransacking the internet with no success yet.
I unlocked my BV9600pro with Android8.1 bootloader using fastboot then flashed on it TWRP before I learnt I just could have patched the Boot.img and flash in to get root, which I’ve done, now the device is rooted and when I’m trying to boot to recovery it display Orange State and goes to No Command screen.
I have tried some keys combinations on the No Command screen like the Vol+ and Power button but the device booted to bootloader options and when I selected recovery mode again I was back to Orange State and to no command, then I tried vol- and power button but that booted to Orange State then normal boot.
I edited lk.img and flashed on my bv9600pro it just remove the Orange State Display but won't still give access to recovery, I had to reflash on the device the stock lk.img and stock recovery.img and still can't boot to recovery. I'm guessing it's all as a result of the unlocking. Please any other way to fix this to enable me access recovery with the root?
I actually want to have the TWRP on the device to allow Nandroid backup and eaisily flashing on the device my custom ROMs.
Click to expand...
Click to collapse
more likely the unofficial twrp. The unlocking shouldn't cause issues since its unlockable by Moto itself. .
Mine seem to flash the recovery very quickly (under 2 secs) so I'm wondering if I have the proper rights and it isn't actually writing the .img file but just guessing.
thanks for the reply
sd_shadow said:
What does getvar all say?
Code:
fastboot getvar all
Click to expand...
Click to collapse
(bootloader) kernel: uefi
(bootloader) version-bootloader: MBM-3.0-borneo_retail-bfe8cf6b47-201209
(bootloader) product: borneo
(bootloader) board: borneo
(bootloader) secure: yes
(bootloader) hwrev: PVT
(bootloader) radio: NA
(bootloader) storage-type: eMMC
(bootloader) emmc: 64GB MICRON S0J9K8 RV=08 PV=10 FV=0000000000000004
(bootloader) ufs: N/A
(bootloader) ram: 4GB MICRON LP4x DIE=16Gb M5-M8=FF 04 10 10
(bootloader) cpu: SM_KAMORTA_H 1.0
(bootloader) serialno: ZY22BVJSBS
(bootloader) cid: 0x0032
(bootloader) channelid: 0x8d
(bootloader) uid: 6F15AE13
(bootloader) securestate: flashing_unlocked
(bootloader) factory-modes: disabled
(bootloader) verity-state: enforcing (0)
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 804474880
(bootloader) reason: Reboot mode set to fastboot
(bootloader) imei: 356891111389229
(bootloader) imei2:
(bootloader) meid:
(bootloader) date: 02-28-2021
(bootloader) sku: XT2117-4
(bootloader) carrier_sku: XT2117-4
(bootloader) battid: SB18C77591
(bootloader) battery-voltage: 4327
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) poweroffalarm: 0
(bootloader) ro.carrier: retus
(bootloader) ro.build.fingerprint[0]: motorola/borneo_retail/borneo:10/Q
(bootloader) ro.build.fingerprint[1]: ZB30.Q4-43-35/7ad68:user/release-k
(bootloader) ro.build.fingerprint[2]: eys
(bootloader) ro.build.version.qcom: LA.UM.8.15.r1-06600-KAMORTA.0
(bootloader) version-baseband: HA10_18.534.02.57R BORNEO_NA_CUST
(bootloader) kernel.version[0]: Linux version 4.19.95-perf+ ([email protected]
(bootloader) kernel.version[1]: oid-build) (clang version 8.0.16 for And
(bootloader) kernel.version[2]: roid NDK) #1 SMP PREEMPT Wed Dec 9 02:44
(bootloader) kernel.version[3]: :38 CST 2020
(bootloader) git:xbl: MBM-3.0-borneo_retail-9304f2ad5-201209
(bootloader) git:xbl_config: MBM-3.0-borneo_retail-9304f2ad5-201209
(bootloader) git:abl: MBM-3.0-borneo_retail-bfe8cf6b47-201209
(bootloader) git:rpm: MBM-3.0-borneo_retail-6b0a297-201209
(bootloader) git:tz: MBM-3.0-borneo_retail-9de24c4c-201209
(bootloader) git:hyp: MBM-3.0-borneo_retail-9de24c4c-201209
(bootloader) git:devcfg: MBM-3.0-borneo_retail-9de24c4c-201209
(bootloader) git:keymaster: MBM-3.0-borneo_retail-3b8c7a4-201209
(bootloader) git:storsec: MBM-3.0-borneo_retail-3b8c7a4-201209
(bootloader) git:uefisecapp: MBM-3.0-borneo_retail-3b8c7a4-201209
(bootloader) gitrov: MBM-3.0-borneo_retail-9de24c4c-201209
(bootloader) git:qupfw: MBM-3.0-borneo_retail-f07d142-201209
(bootloader) frp-state: protected (77)
(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: 6
(bootloader) slot-retry-count:_b: 0
(bootloader) logical-block-size: 0x200
(bootloader) erase-block-size: 0x200
(bootloader) is-userspace: no
(bootloader) pcb-part-no: SB28C86870
(bootloader) primary-display: djn_nt36672a_video_display
(bootloader) secondary-display:
all: listed above
finished. total time: 0.091s
piiman said:
(bootloader) kernel: uefi
(bootloader) version-bootloader: MBM-3.0-borneo_retail-bfe8cf6b47-201209
(bootloader) product: borneo
(bootloader) board: borneo
(bootloader) secure: yes
(bootloader) hwrev: PVT
(bootloader) radio: NA
(bootloader) storage-type: eMMC
(bootloader) emmc: 64GB MICRON S0J9K8 RV=08 PV=10 FV=0000000000000004
(bootloader) ufs: N/A
(bootloader) ram: 4GB MICRON LP4x DIE=16Gb M5-M8=FF 04 10 10
(bootloader) cpu: SM_KAMORTA_H 1.0
(bootloader) serialno: ZY22BVJSBS
(bootloader) cid: 0x0032
(bootloader) channelid: 0x8d
(bootloader) uid: 6F15AE13
(bootloader) securestate: flashing_unlocked
(bootloader) factory-modes: disabled
(bootloader) verity-state: enforcing (0)
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 804474880
(bootloader) reason: Reboot mode set to fastboot
(bootloader) imei: 356891111389229
(bootloader) imei2:
(bootloader) meid:
(bootloader) date: 02-28-2021
(bootloader) sku: XT2117-4
(bootloader) carrier_sku: XT2117-4
(bootloader) battid: SB18C77591
(bootloader) battery-voltage: 4327
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) poweroffalarm: 0
(bootloader) ro.carrier: retus
(bootloader) ro.build.fingerprint[0]: motorola/borneo_retail/borneo:10/Q
(bootloader) ro.build.fingerprint[1]: ZB30.Q4-43-35/7ad68:user/release-k
(bootloader) ro.build.fingerprint[2]: eys
(bootloader) ro.build.version.qcom: LA.UM.8.15.r1-06600-KAMORTA.0
(bootloader) version-baseband: HA10_18.534.02.57R BORNEO_NA_CUST
(bootloader) kernel.version[0]: Linux version 4.19.95-perf+ ([email protected]
(bootloader) kernel.version[1]: oid-build) (clang version 8.0.16 for And
(bootloader) kernel.version[2]: roid NDK) #1 SMP PREEMPT Wed Dec 9 02:44
(bootloader) kernel.version[3]: :38 CST 2020
(bootloader) git:xbl: MBM-3.0-borneo_retail-9304f2ad5-201209
(bootloader) git:xbl_config: MBM-3.0-borneo_retail-9304f2ad5-201209
(bootloader) git:abl: MBM-3.0-borneo_retail-bfe8cf6b47-201209
(bootloader) git:rpm: MBM-3.0-borneo_retail-6b0a297-201209
(bootloader) git:tz: MBM-3.0-borneo_retail-9de24c4c-201209
(bootloader) git:hyp: MBM-3.0-borneo_retail-9de24c4c-201209
(bootloader) git:devcfg: MBM-3.0-borneo_retail-9de24c4c-201209
(bootloader) git:keymaster: MBM-3.0-borneo_retail-3b8c7a4-201209
(bootloader) git:storsec: MBM-3.0-borneo_retail-3b8c7a4-201209
(bootloader) git:uefisecapp: MBM-3.0-borneo_retail-3b8c7a4-201209
(bootloader) gitrov: MBM-3.0-borneo_retail-9de24c4c-201209
(bootloader) git:qupfw: MBM-3.0-borneo_retail-f07d142-201209
(bootloader) frp-state: protected (77)
(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: 6
(bootloader) slot-retry-count:_b: 0
(bootloader) logical-block-size: 0x200
(bootloader) erase-block-size: 0x200
(bootloader) is-userspace: no
(bootloader) pcb-part-no: SB28C86870
(bootloader) primary-display: djn_nt36672a_video_display
(bootloader) secondary-display:
all: listed above
finished. total time: 0.091s
Click to expand...
Click to collapse
Where did you find Twrp for borneo?
Rukkyakakporo said:
I'm having something close to this, though mine is blackview. I'm guessing this is a new problem as mine happen about a week now and I've gat sleepless night ransacking the internet with no success yet.
I unlocked my BV9600pro with Android8.1 bootloader using fastboot then flashed on it TWRP before I learnt I just could have patched the Boot.img and flash in to get root, which I’ve done, now the device is rooted and when I’m trying to boot to recovery it display Orange State and goes to No Command screen.
I have tried some keys combinations on the No Command screen like the Vol+ and Power button but the device booted to bootloader options and when I selected recovery mode again I was back to Orange State and to no command, then I tried vol- and power button but that booted to Orange State then normal boot.
I edited lk.img and flashed on my bv9600pro it just remove the Orange State Display but won't still give access to recovery, I had to reflash on the device the stock lk.img and stock recovery.img and still can't boot to recovery. I'm guessing it's all as a result of the unlocking. Please any other way to fix this to enable me access recovery with the root?
I actually want to have the TWRP on the device to allow Nandroid backup and eaisily flashing on the device my custom ROMs.
Click to expand...
Click to collapse
This is a forum for Moto G Power (2021)
Try asking in
General Questions and Answers
This forum is for all questions, big or small, you might have. Please read the rules in this forum before submitting any Q&A.This forum is a Questions section, which means each reply is treated as an answer that can be up/down voted by the community. Then, the original poster can choose the best...
forum.xda-developers.com
sd_shadow said:
Where did you find Twrp for borneo?
Click to expand...
Click to collapse
don't remember but it was from XDA and I think it was this thread https://forum.xda-developers.com/t/sofia-p-r-recovery-wip-twrp-3-4-0-0.4128353/ and the zip was
twrp-3.5.0-0-rav-sofia.img <- most recent
piiman said:
don't remember but it was from XDA and I think it was this thread https://forum.xda-developers.com/t/sofia-p-r-recovery-wip-twrp-3-4-0-0.4128353/ and the zip was
twrp-3.5.0-0-rav-sofia.img <- most recent
Click to expand...
Click to collapse
That's not for your device
sd_shadow said:
That's not for your device
Click to expand...
Click to collapse
Then which is? Trying to find this stuff is a nightmare. and is there a way to go back?
piiman said:
Then which is? Trying to find this stuff is a nightmare. and is there a way to go back?
Click to expand...
Click to collapse
If you have a windows pc try LMSA'S flash rescue
Download firmware with lmsa
Then flash with lmsa or just find the firmware folder and reflash recovery.img
[Guide] Using Fastboot.exe with Motorola devices
Guide: Using Fastboot.exe with Motorola Devices If your device has its own section please post in that section. You can ping me with @sd_shadow MediaTek or Qualcomm Chip? Do I have a MediaTek Device? see post #26 Info: If you have a MediaTek...
forum.xda-developers.com
If you just want to root.
[Guide] Root Motorola with Magisk (UnLocked Bootloader)(Non-TWRP method)
Root Motorola Devices with Magisk Note: This method has been working with most Moto Devices that the Bootloader can be UnLocked. If the Bootloader cannot be Unlocked this method will not work. Please only use this as a reference. If you require...
forum.xda-developers.com
sd_shadow said:
If you have a windows pc try LMSA'S flash rescue
Download firmware with lmsa
Then flash with lmsa or just find the firmware folder and reflash recovery.img
[Guide] Using Fastboot.exe with Motorola devices
Guide: Using Fastboot.exe with Motorola Devices If your device has its own section please post in that section. You can ping me with @sd_shadow MediaTek or Qualcomm Chip? Do I have a MediaTek Device? see post #26 Info: If you have a MediaTek...
forum.xda-developers.com
Click to expand...
Click to collapse
Will try later, thanks for your insight.
sd_shadow said:
If you just want to root.
[Guide] Root Motorola with Magisk (UnLocked Bootloader)(Non-TWRP method)
Root Motorola Devices with Magisk Note: This method has been working with most Moto Devices that the Bootloader can be UnLocked. If the Bootloader cannot be Unlocked this method will not work. Please only use this as a reference. If you require...
forum.xda-developers.com
Click to expand...
Click to collapse
Was hoping to use twrp for that but I guess I'll have to do it this way. Thanks
sd_shadow said:
If you have a windows pc try LMSA'S flash rescue
Download firmware with lmsa
Then flash with lmsa or just find the firmware folder and reflash recovery.img
[Guide] Using Fastboot.exe with Motorola devices
Guide: Using Fastboot.exe with Motorola Devices If your device has its own section please post in that section. You can ping me with @sd_shadow MediaTek or Qualcomm Chip? Do I have a MediaTek Device? see post #26 Info: If you have a MediaTek...
forum.xda-developers.com
Click to expand...
Click to collapse
went looking for this and when I enter the serial number it says no products found. Now what? I copied the serial number from the VAR's I posted above is that the correct serial number?
piiman said:
went looking for this and when I enter the serial number it says no products found. Now what? I copied the serial number from the VAR's I posted above is that the correct serial number?
Click to expand...
Click to collapse
No go direct to rescue, the serial thing is stupid
sd_shadow said:
No go direct to rescue, the serial thing is stupid
Click to expand...
Click to collapse
Thanks I'll give that a try
sd_shadow said:
No go direct to rescue, the serial thing is stupid
Click to expand...
Click to collapse
OK I have the firmware downloaded and it's in XML format. How can I get the recovery.img out of that so I can flash it?
piiman said:
OK I have the firmware downloaded and it's in XML format. How can I get the recovery.img out of that so I can flash it?
Click to expand...
Click to collapse
.xml is a text format, if you used lmsa it would be a folder, if you downloaded from somewhere else it will be a .zip
sd_shadow said:
.xml is a text format, if you used lmsa it would be a folder, if you downloaded from somewhere else it will be a .zip
Click to expand...
Click to collapse
I used LMSA and the xml file acts like a folder can I just copy it out of there?
Hey gang. I unlocked a motorola g play 2021 rooted it and tried to flash twrp onto it whch didnt work. So I flashed the boot.img file and it restarted as a new phone would. The next morning. bear with me here. It states no OS present to boot. So I restart the phone to the bootloader and it states the bootloader is locked and now will only restart to the bootloader. When I try to flash the recovery or boot image it just stated bootloader permission denied then it fails. I have been flashing samsungs for years with no problems and when there is I can usually solve it easily. But ths damn motorola has me stumped.. Here is the getvar all info. Any help possible would be greatly appreciated. Guess Im still more of an amature then i thought. Please advise. Thanks
I tried going through the unlock bootloader sequence and this is what it tells me.
C:\Android\platform-tools>fastboot oem unlock CSSPP***#*#********
(bootloader) Check 'OEM unlocking' in Android Settings > Developer
(bootloader) Options
FAILED (remote: '')
fastboot: error: Command failed
this got me back to Android recovery page. But when I try to do a factory reset it says no directory or file present
fastboot --c "console=ttyHSL0,115200,n8" boot recovery.img
The Lenovo rescue tool fails at 40% every time.
Unlock Code: CSSPP***************
get var all
(bootloader) kernel: uefi
(bootloader) version-bootloader: MBM-3.0-guamna_t-bfe8cf6b47-210609
(bootloader) product: guamna
(bootloader) board: guamna
(bootloader) secure: yes
(bootloader) hwrev: PVT
(bootloader) radio: GWLC
(bootloader) storage-type: eMMC
(bootloader) emmc: 32GB SKHYNIX hB8aP> RV=08 PV=03 FV=0000000034303030
(bootloader) ufs: N/A
(bootloader) ram: 3GB SKHYNIX LP4x DIE=12Gb M5-M8=06 05 00 0D
(bootloader) cpu: SM_KAMORTA 1.0
(bootloader) serialno: ZY22BQWX4M
(bootloader) cid: 0x0015
(bootloader) channelid: 0x8e
(bootloader) uid: F66B2378
(bootloader) securestate: flashing_locked
(bootloader) factory-modes: disabled
(bootloader) verity-state: enforcing (0)
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 798750720
(bootloader) reason: Reboot mode set to fastboot
(bootloader) imei: 351647111426774
(bootloader) imei2:
(bootloader) meid:
(bootloader) date: 01-20-2021
(bootloader) sku: XT2093-3
(bootloader) carrier_sku: XT2093-3
(bootloader) battid: SB18C77591
(bootloader) battery-voltage: 3854
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) poweroffalarm: 0
(bootloader) ro.carrier: metropcs
(bootloader) ro.build.fingerprint[0]: motorola/guamna_t/guamna:10/QZAS30
(bootloader) ro.build.fingerprint[1]: .Q4-39-57-2-2-1-1-3-3/882ca7:user/
(bootloader) ro.build.fingerprint[2]: release-keys
(bootloader) ro.build.version.qcom: LA.UM.8.15.r1-06600-KAMORTA.0
(bootloader) version-baseband: HA10_18.534.02.73.08R GUAMNA_GWLC_CUST
(bootloader) kernel.version[0]: Linux version 4.19.95-perf+ ([email protected]
(bootloader) kernel.version[1]: oid-build) (clang version 8.0.16 for And
(bootloader) kernel.version[2]: roid NDK) #1 SMP PREEMPT Wed Jun 9 07:26
(bootloader) kernel.version[3]: :55 CDT 2021
(bootloader) git:xbl: MBM-3.0-guamna_t-c904c5c3f-210609
(bootloader) git:xbl_config: MBM-3.0-guamna_t-c904c5c3f-210609
(bootloader) git:abl: MBM-3.0-guamna_t-bfe8cf6b47-210609
(bootloader) git:rpm: MBM-3.0-guamna_t-6b0a297-210609
(bootloader) git:tz: MBM-3.0-guamna_t-9de24c4c2-210609
(bootloader) git:hyp: MBM-3.0-guamna_t-9de24c4c2-210609
(bootloader) git:devcfg: MBM-3.0-guamna_t-9de24c4c2-210609
(bootloader) git:keymaster: MBM-3.0-guamna_t-3b8c7a4-210609
(bootloader) git:storsec: MBM-3.0-guamna_t-3b8c7a4-210609
(bootloader) git:uefisecapp: MBM-3.0-guamna_t-3b8c7a4-210609
(bootloader) gitrov: MBM-3.0-guamna_t-9de24c4c2-210609
(bootloader) git:qupfw: MBM-3.0-guamna_t-f07d142-210609
(bootloader) frp-state: protected (77)
(bootloader) current-slot: b
(bootloader) running-bl-slot: _b/_b
(bootloader) running-boot-lun: 0
(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: 1
(bootloader) logical-block-size: 0x200
(bootloader) erase-block-size: 0x200
(bootloader) is-userspace: no
(bootloader) pcb-part-no: SB28C86657
(bootloader) primary-display: hlt_hx83102d_video_display
(bootloader) secondary-display:
all: listed above
Finished. Total time: 0.267s
Mikeo31 said:
Hey gang. I unlocked a motorola g play 2021 rooted it and tried to flash twrp onto it whch didnt work. So I flashed the boot.img file and it restarted as a new phone would. The next morning. bear with me here. It states no OS present to boot. So I restart the phone to the bootloader and it states the bootloader is locked and now will only restart to the bootloader. When I try to flash the recovery or boot image it just stated bootloader permission denied then it fails. I have been flashing samsungs for years with no problems and when there is I can usually solve it easily. But ths damn motorola has me stumped.. Here is the getvar all info. Any help possible would be greatly appreciated. Guess Im still more of an amature then i thought. Please advise. Thanks
I tried going through the unlock bootloader sequence and this is what it tells me.
C:\Android\platform-tools>fastboot oem unlock CSSPP***#*#********
(bootloader) Check 'OEM unlocking' in Android Settings > Developer
(bootloader) Options
FAILED (remote: '')
fastboot: error: Command failed
this got me back to Android recovery page. But when I try to do a factory reset it says no directory or file present
fastboot --c "console=ttyHSL0,115200,n8" boot recovery.img
The Lenovo rescue tool fails at 40% every time.
Unlock Code: CSSPP***************
get var all
(bootloader) kernel: uefi
(bootloader) version-bootloader: MBM-3.0-guamna_t-bfe8cf6b47-210609
(bootloader) product: guamna
(bootloader) board: guamna
(bootloader) secure: yes
(bootloader) hwrev: PVT
(bootloader) radio: GWLC
(bootloader) storage-type: eMMC
(bootloader) emmc: 32GB SKHYNIX hB8aP> RV=08 PV=03 FV=0000000034303030
(bootloader) ufs: N/A
(bootloader) ram: 3GB SKHYNIX LP4x DIE=12Gb M5-M8=06 05 00 0D
(bootloader) cpu: SM_KAMORTA 1.0
(bootloader) serialno: ZY22BQWX4M
(bootloader) cid: 0x0015
(bootloader) channelid: 0x8e
(bootloader) uid: F66B2378
(bootloader) securestate: flashing_locked
(bootloader) factory-modes: disabled
(bootloader) verity-state: enforcing (0)
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 798750720
(bootloader) reason: Reboot mode set to fastboot
(bootloader) imei: 351647111426774
(bootloader) imei2:
(bootloader) meid:
(bootloader) date: 01-20-2021
(bootloader) sku: XT2093-3
(bootloader) carrier_sku: XT2093-3
(bootloader) battid: SB18C77591
(bootloader) battery-voltage: 3854
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) poweroffalarm: 0
(bootloader) ro.carrier: metropcs
(bootloader) ro.build.fingerprint[0]: motorola/guamna_t/guamna:10/QZAS30
(bootloader) ro.build.fingerprint[1]: .Q4-39-57-2-2-1-1-3-3/882ca7:user/
(bootloader) ro.build.fingerprint[2]: release-keys
(bootloader) ro.build.version.qcom: LA.UM.8.15.r1-06600-KAMORTA.0
(bootloader) version-baseband: HA10_18.534.02.73.08R GUAMNA_GWLC_CUST
(bootloader) kernel.version[0]: Linux version 4.19.95-perf+ ([email protected]
(bootloader) kernel.version[1]: oid-build) (clang version 8.0.16 for And
(bootloader) kernel.version[2]: roid NDK) #1 SMP PREEMPT Wed Jun 9 07:26
(bootloader) kernel.version[3]: :55 CDT 2021
(bootloader) git:xbl: MBM-3.0-guamna_t-c904c5c3f-210609
(bootloader) git:xbl_config: MBM-3.0-guamna_t-c904c5c3f-210609
(bootloader) git:abl: MBM-3.0-guamna_t-bfe8cf6b47-210609
(bootloader) git:rpm: MBM-3.0-guamna_t-6b0a297-210609
(bootloader) git:tz: MBM-3.0-guamna_t-9de24c4c2-210609
(bootloader) git:hyp: MBM-3.0-guamna_t-9de24c4c2-210609
(bootloader) git:devcfg: MBM-3.0-guamna_t-9de24c4c2-210609
(bootloader) git:keymaster: MBM-3.0-guamna_t-3b8c7a4-210609
(bootloader) git:storsec: MBM-3.0-guamna_t-3b8c7a4-210609
(bootloader) git:uefisecapp: MBM-3.0-guamna_t-3b8c7a4-210609
(bootloader) gitrov: MBM-3.0-guamna_t-9de24c4c2-210609
(bootloader) git:qupfw: MBM-3.0-guamna_t-f07d142-210609
(bootloader) frp-state: protected (77)
(bootloader) current-slot: b
(bootloader) running-bl-slot: _b/_b
(bootloader) running-boot-lun: 0
(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: 1
(bootloader) logical-block-size: 0x200
(bootloader) erase-block-size: 0x200
(bootloader) is-userspace: no
(bootloader) pcb-part-no: SB28C86657
(bootloader) primary-display: hlt_hx83102d_video_display
(bootloader) secondary-display:
all: listed above
Finished. Total time: 0.267s
Click to expand...
Click to collapse
Try flashing manually
LMSA should have a copy of firmware in C:\ProgramData\LMSA\Download\RomFiles
Or you can download it from
https://mirrors.lolinet.com/firmware/moto/guamna/official/MetroPCS/
XT2093-3_GUAMNA_METROPCS_10_QZAS30.Q4-39-57-2-2-1-1-3-3_subsidy-MPCS_RSU_QCOM_regulatory-DEFAULT_CFC.xml.zip
Unzip
First try
Code:
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot oem fb_mode_clear
fastboot reboot
It might boot normally
if not try
Code:
fastboot getvar max-sparse-size
fastboot oem fb_mode_set
reboot bootloader
then try LMSA again
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
[Guide] Using Fastboot.exe with Motorola devices
Guide: Using Fastboot.exe with Motorola Devices If your device has its own section please post in that section. You can ping me with @sd_shadow MediaTek or Qualcomm Chip? Do I have a MediaTek Device? see post #26 Info: If you have a MediaTek...
forum.xda-developers.com
sd_shadow said:
Try flashing manually
LMSA should have a copy of firmware in C:\ProgramData\LMSA\Download\RomFiles
Or you can download it from
https://mirrors.lolinet.com/firmware/moto/guamna/official/MetroPCS/
XT2093-3_GUAMNA_METROPCS_10_QZAS30.Q4-39-57-2-2-1-1-3-3_subsidy-MPCS_RSU_QCOM_regulatory-DEFAULT_CFC.xml.zip
Unzip
First try
Code:
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot oem fb_mode_clear
fastboot reboot
It might boot normally
if not try
Code:
fastboot getvar max-sparse-size
fastboot oem fb_mode_set
reboot bootloader
then try LMSA again
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
[Guide] Using Fastboot.exe with Motorola devices
Guide: Using Fastboot.exe with Motorola Devices If your device has its own section please post in that section. You can ping me with @sd_shadow MediaTek or Qualcomm Chip? Do I have a MediaTek Device? see post #26 Info: If you have a MediaTek...
forum.xda-developers.com
Click to expand...
Click to collapse
thanks very much I'll give it a go and repost. @sd_shadow
Mikeo31 said:
thanks very much I'll give it a go and repost. @sd_shadow
Click to expand...
Click to collapse
No good. on the first method.
C:\adb>fastboot flash partition gpt.bin
target reported max download size of 798763008 bytes
sending 'partition' (37 KB)...
OKAY [ 0.009s]
writing 'partition'...
(bootloader) Validating 'gpt.default.xml'
(bootloader) flash permission denied
(bootloader) Cancelling 'gpt.default.xml'
FAILED (remote failure)
finished. total time: 0.167s
No good on the 2nd method
Permission denied
FAILED(remote failure)
and the LMSA gets as far as 50% depending on which time I ran it and states
Flashboot Flash single partition
Flash failed please try again
Could it be something to do with the A/B Partition.? I flashed Magisk on one of them and it restarted. I went to bed and got up the next morning and here we are.
Hi I'm Steve I'm new here and I'm just learning how to root my phone and be a developer so if anybody could help me I really appreciate it
Is there a blank flash.zip yet for this phone? Usually I've seen mirrors.lolinet.com include blankflash files with each variant of moto phones. This one is an exception. Or can anyone make one perhaps?
I transferred the fastboot.exe out of the LMSA or RSA file, because I noticed it's something like 7.5mb, and seemed to gain extra fastboot functionality. This was when I encountered, maybe not exactly the same, but a similar issue with relocking the bootloader.
I used the command (after copying the Lincoln log of a fastboot executable to my working directory):
fastboot -b flash boot boot.img
And by some stroke of luck, it booted into the OS. I know that command looks weird, but I was so frustrated, I just started going down the list and trying everything I could. If you haven't tried switching boot slots, you may give that a whirl as well. I do hope this helps.
My setup is an old dual core Intel, with windows 10 version 20H1....one of the older windows 10 releases.
Mikeo31 said:
No good. on the first method.
C:\adb>fastboot flash partition gpt.bin
target reported max download size of 798763008 bytes
sending 'partition' (37 KB)...
OKAY [ 0.009s]
writing 'partition'...
(bootloader) Validating 'gpt.default.xml'
(bootloader) flash permission denied
(bootloader) Cancelling 'gpt.default.xml'
FAILED (remote failure)
finished. total time: 0.167s
Click to expand...
Click to collapse
Did you fastboot oem fb_mode_set first?
Hello Everyone.
This is my first post so please if i did anything wrong or posted this in the wrong place please let me know.
I have a Moto G Pure that im trying to root. I have to unlock the bootloader first from what i gather. I downloaded the adb, fastboot and drivers for the phone installed everything and went on motos website and used there bootloader unlock string tool and it says "your device does not qualify for bootloader unlocking". Not sure why that's coming up? Does anyone know a work around by chance? Here is the Unlock Data, the sting I used and the getvar info.
C:\\Desktop\platform-tools>fastboot oem get_unlock_data
(bootloader) Unlock data:
(bootloader) 3A85832508840061#5A593232444C4B
(bootloader) 474433006D6F746F2067200000#F797
(bootloader) DDD03416481B0F85B69548533550013
(bootloader) 97C6CAAC01B02F6D820BD2048F29F#0
(bootloader) DF077A6F1E7E5E80000000000000000
OKAY [ 0.050s]
Finished. Total time: 0.052
3A85832508840061#5A593232444C4B474433006D6F746F2067200000#F797DDD03416481B0F85B6954853355001397C6CAAC01B02F6D820BD2048F29F#0DF077A6F1E7E5E80000000000000000
C:\\Desktop\platform-tools>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: MBM-2.1-ellis_a-320aeee45-211101
(bootloader) product: ellis
(bootloader) board: ellis
(bootloader) secure: yes
(bootloader) hwrev: PVT1
(bootloader) radio: 4
(bootloader) storage-type: eMMC
(bootloader) emmc: 32GB SAMSUNG DX68MB RV=08 PV=00 FV=0000000000000003
(bootloader) ram: 3GB SAMSUNG N NVM DIE=512Mb M5=01 M6=07 M7=00 M8=0E
(bootloader) cpu: MT6762G
(bootloader) serialno: XXXXXXXXXX
(bootloader) cid: 0x0001
(bootloader) channelid: 0x88
(bootloader) uid: 0DF077A6F1E7E5E8000000000000
(bootloader) securestate: oem_locked
(bootloader) factory-modes: disabled
(bootloader) iswarrantyvoid: no
(bootloader) max-download-size: 268435456
(bootloader) reason: Volume down key pressed
(bootloader) imei: XXXXXXXXXXXXXXX
(bootloader) imei2:
(bootloader) meid:
(bootloader) date: 11-18-2021
(bootloader) sku: XT2163-6
(bootloader) carrier_sku: XT2163-6
(bootloader) battid: SB18D15249
(bootloader) iccid: 89012803320393497037
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Fri Apr 15 12:24:29 UTC 2022"
(bootloader) ro.build.fingerprint[0]: motorola/ellis_a/ellis:11/RRH31.Q3
(bootloader) ro.build.fingerprint[1]: -46-50-2/20fec:user/release-keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.mtk: alps-mp-r0.mp1.tc2sp-V1.66
(bootloader) version-baseband: MT6762_TC2.PR2.SP.V8.2.P20.01.66.54R
(bootloader) kernel.version[0]: Linux version 4.19.127+ ([email protected]
(bootloader) kernel.version[1]: build) (Android (6443078 based on r38390
(bootloader) kernel.version[2]: 2) clang version 11.0.1 (https://android
(bootloader) kernel.version[3]: .googlesource.com/toolchain/llvm-project
(bootloader) kernel.version[4]: b397f81060ce6d701042b782172ed13bee898b7
(bootloader) kernel.version[5]: 9), LLD 11.0.1 (/buildbot/tmp/tmp6_m7QH
(bootloader) kernel.version[6]: b397f81060ce6d701042b782172ed13bee898b79
(bootloader) kernel.version[7]: )) #1 SMP PREEMPT Mon Nov 1 05:00:56 CDT
(bootloader) kernel.version[8]: 2021
(bootloader) frp-state: no protection (144)
(bootloader) ro.carrier: attpre
(bootloader) current-slot: a
(bootloader) running-boot-lun: 1
(bootloader) running-slot: _a
(bootloader) slot-successful:_a: yes
(bootloader) slot-successful:_b: no
(bootloader) slot-bootable:_a: Yes
(bootloader) slot-bootable:_b: Yes
(bootloader) slot-retry-count:_a: 1
(bootloader) slot-retry-count:_b: 7
(bootloader) slot-suffixes: _a,_b
(bootloader) slot-count: 2
(bootloader) pcb-part-no: SB28D31556
(bootloader) is-userspace: no
(bootloader) is-logical:
(bootloader) snapshot-update-status: none
all: listed above
Finished. Total time: 0.078s
Any pointers would surly be appreciated. Been pulling my hair out. haha!
Thanks for reading!
-BB
@Biggitybaked
The model you have (XT2163-6) is the AT&T variant of the Moto G Pure. The carrier doesn't allow unlocking the bootloader.
With that said, you can give an unofficial MediaTek reverse engineering tool named MTKClient a try. Only proceed if you know what you're doing.
That's what I figured. Ill never buy as phone from a carrier again. Thank you for confirming. And ima look into that MTKClient and see if I can do it. Wish me luck. haha!
Have you tested the mtkclient, work ?
meegosgift said:
Have you tested the mtkclient, work ?
Click to expand...
Click to collapse
The main issue preventing mtk client from working seems to be this: I have no clue on how to make my XT2163-2 phone enter the MediaTek ... brom mode!
There's a program it may not technically be for your peticular phone, so not responsible for any damage or problems I'm just saying I think it's like mtk auth bypass tool, it can get you to brom mode,
But ... what are the prerequisites (along with that app from MediaTek) for making the phone enter brom mode? Without JTAG, serial interface or "test points". A way for mere mortals like me, to allow me to unlock the damn bootloader, which Motorola (aka Lenovo) was plotting with Verizons, to keep us, legitimate owners of their stupid phones, out of the bootloader...
how to boot to brom on this phone? anyone figured it out?
smihaila said:
The main issue preventing mtk client from working seems to be this: I have no clue on how to make my XT2163-2 phone enter the MediaTek ... brom mode!
Click to expand...
Click to collapse
When using mtk client, power off the phone and disconnect the usb. While off, hold both VOL - & VOL + then plug in the usb while the client is running. Mtk client will automatically recognize your device I've used the same method for all versions of mtk devices with 100% success. The partitions pull as bin files but i just use a converter to solve that issue
yah2000 said:
how to boot to brom on this phone? anyone figured it out?
Click to expand...
Click to collapse
While Mtk client is running:
1. Power off device & disconnect the usb
2. Plug in usb while holding VOL - & VOL +
Mtk Client will automatically recognize mtk device
Biggitybaked said:
Hello Everyone.
This is my first post so please if i did anything wrong or posted this in the wrong place please let me know.
I have a Moto G Pure that im trying to root. I have to unlock the bootloader first from what i gather. I downloaded the adb, fastboot and drivers for the phone installed everything and went on motos website and used there bootloader unlock string tool and it says "your device does not qualify for bootloader unlocking". Not sure why that's coming up? Does anyone know a work around by chance? Here is the Unlock Data, the sting I used and the getvar info.
C:\\Desktop\platform-tools>fastboot oem get_unlock_data
(bootloader) Unlock data:
(bootloader) 3A85832508840061#5A593232444C4B
(bootloader) 474433006D6F746F2067200000#F797
(bootloader) DDD03416481B0F85B69548533550013
(bootloader) 97C6CAAC01B02F6D820BD2048F29F#0
(bootloader) DF077A6F1E7E5E80000000000000000
OKAY [ 0.050s]
Finished. Total time: 0.052
3A85832508840061#5A593232444C4B474433006D6F746F2067200000#F797DDD03416481B0F85B6954853355001397C6CAAC01B02F6D820BD2048F29F#0DF077A6F1E7E5E80000000000000000
C:\\Desktop\platform-tools>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: MBM-2.1-ellis_a-320aeee45-211101
(bootloader) product: ellis
(bootloader) board: ellis
(bootloader) secure: yes
(bootloader) hwrev: PVT1
(bootloader) radio: 4
(bootloader) storage-type: eMMC
(bootloader) emmc: 32GB SAMSUNG DX68MB RV=08 PV=00 FV=0000000000000003
(bootloader) ram: 3GB SAMSUNG N NVM DIE=512Mb M5=01 M6=07 M7=00 M8=0E
(bootloader) cpu: MT6762G
(bootloader) serialno: XXXXXXXXXX
(bootloader) cid: 0x0001
(bootloader) channelid: 0x88
(bootloader) uid: 0DF077A6F1E7E5E8000000000000
(bootloader) securestate: oem_locked
(bootloader) factory-modes: disabled
(bootloader) iswarrantyvoid: no
(bootloader) max-download-size: 268435456
(bootloader) reason: Volume down key pressed
(bootloader) imei: XXXXXXXXXXXXXXX
(bootloader) imei2:
(bootloader) meid:
(bootloader) date: 11-18-2021
(bootloader) sku: XT2163-6
(bootloader) carrier_sku: XT2163-6
(bootloader) battid: SB18D15249
(bootloader) iccid: 89012803320393497037
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Fri Apr 15 12:24:29 UTC 2022"
(bootloader) ro.build.fingerprint[0]: motorola/ellis_a/ellis:11/RRH31.Q3
(bootloader) ro.build.fingerprint[1]: -46-50-2/20fec:user/release-keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.mtk: alps-mp-r0.mp1.tc2sp-V1.66
(bootloader) version-baseband: MT6762_TC2.PR2.SP.V8.2.P20.01.66.54R
(bootloader) kernel.version[0]: Linux version 4.19.127+ ([email protected]
(bootloader) kernel.version[1]: build) (Android (6443078 based on r38390
(bootloader) kernel.version[2]: 2) clang version 11.0.1 (https://android
(bootloader) kernel.version[3]: .googlesource.com/toolchain/llvm-project
(bootloader) kernel.version[4]: b397f81060ce6d701042b782172ed13bee898b7
(bootloader) kernel.version[5]: 9), LLD 11.0.1 (/buildbot/tmp/tmp6_m7QH
(bootloader) kernel.version[6]: b397f81060ce6d701042b782172ed13bee898b79
(bootloader) kernel.version[7]: )) #1 SMP PREEMPT Mon Nov 1 05:00:56 CDT
(bootloader) kernel.version[8]: 2021
(bootloader) frp-state: no protection (144)
(bootloader) ro.carrier: attpre
(bootloader) current-slot: a
(bootloader) running-boot-lun: 1
(bootloader) running-slot: _a
(bootloader) slot-successful:_a: yes
(bootloader) slot-successful:_b: no
(bootloader) slot-bootable:_a: Yes
(bootloader) slot-bootable:_b: Yes
(bootloader) slot-retry-count:_a: 1
(bootloader) slot-retry-count:_b: 7
(bootloader) slot-suffixes: _a,_b
(bootloader) slot-count: 2
(bootloader) pcb-part-no: SB28D31556
(bootloader) is-userspace: no
(bootloader) is-logical:
(bootloader) snapshot-update-status: none
all: listed above
Finished. Total time: 0.078s
Any pointers would surly be appreciated. Been pulling my hair out. haha!
Thanks for reading!
-BB
Click to expand...
Click to collapse
Successfully rooted my Moto G Pure (RRHS31.Q3-46-110-13):
OEM unlock was grayed out, so I used Motorola RSA to download the stock ROM, then after locating the ROM files, used Magisk 25.2 to patch the boot.img. I flashed the stock ROM using the RESCUE option in RSA then setup my phone once the process was complete. I enabled Developer Options as well as, the now available, OEM unlock and went through the steps to flash the patched boot.img from earlier. I've attached the stock boot and am currently using LSPosed in place of EdXposed
Rescue and Smart Assistant Tool - Motorola
<h6><span style="color:#FFFFFF"><strong>Our Rescue and Smart Assistant tool</strong><br />can help diagnose and resolve issues on your<br />Motorola phone or Lenovo phone/tablet.</span></h6>
www.motorola.com
Moto G Pure - XT2163-4 root? is there a root out there? thx
alan2424m said:
Moto G Pure - XT2163-4 root? is there a root out there? thx
Click to expand...
Click to collapse
Yes. I'm currently using a Moto G Pure TMO (Ellis) updated to Android 12 (S3RH32.20-42-10-2-3) with Magisk 25.2. I'll include my boot.img below which is Android 12-4.19.191+ Magisk patched (25.2) with HuskyDG bootloop protection. I also used LSPosed 1.8.5 (6695) zygisk with [email protected] GS Ram Drive (20GB swap). I had to use Motorola's Rescue & Smart Assistant to re-flash my phone before I could toggle OEM unlock, then I used the generated key to unlock my bootloader.
KMerrimanJr said:
Yes. I'm currently using a Moto G Pure TMO (Ellis) updated to Android 12 (S3RH32.20-42-10-2-3) with Magisk 25.2. I'll include my boot.img below which is Android 12-4.19.191+ Magisk patched (25.2) with HuskyDG bootloop protection. I also used LSPosed 1.8.5 (6695) zygisk with [email protected] GS Ram Drive (20GB swap). I had to use Motorola's Rescue & Smart Assistant to re-flash my phone before I could toggle OEM unlock, then I used the generated key to unlock my bootloader.
Click to expand...
Click to collapse
thx man does it matter that mine is android version 11 XT2163-4?
i got it unlocked already
alan2424m said:
i got it unlocked already
Click to expand...
Click to collapse
No, mine started as Android 11 but Google recently release an Android 12 update for the XT2163-4. ELLIS_T_S3RH32.20_42_10_2_3_subsidy_TMO_UNI_RSU_QCOM_regulatory_DEFAULT_CFC.xml is the latest T-Mobile rom released by Google. Check out the site below to download the official ROM. All carriers are listed
lolinet mirrors - firmware, software, iso etc.
lolinet mirrors - powered by h5ai
mirrors.lolinet.com
alan2424m said:
thx man does it matter that mine is android version 11 XT2163-4
Click to expand...
Click to collapse
Android 12 tightened up on security so you might want to stay on 11. I use App Manager and overlayFS to "uninstall" any apps I don't want but I can't directly delete from the system dir. On 11 I could
KMerrimanJr said:
No, mine started as Android 11 but Google recently release an Android 12 update for the XT2163-4. ELLIS_T_S3RH32.20_42_10_2_3_subsidy_TMO_UNI_RSU_QCOM_regulatory_DEFAULT_CFC.xml is the latest T-Mobile rom released by Google. Check out the site below to download the official ROM. All carriers are listed
lolinet mirrors - firmware, software, iso etc.
lolinet mirrors - powered by h5ai
mirrors.lolinet.com
Click to expand...
Click to collapse
ok mine is boost mobile but that shouldnt change anything right?
here is mine ELLIS_T_RRHS31.Q3_46_110_13_subsidy_BOOST_DISH_SHORT_regulatory_DEFAULT_CFC.xml
yours is tmobile like i said hopefully that doesnt change anything