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, Guys.
I have the following problem:
My watch is with stock international 2.3.9.0.
I've tried to install STRATOSfied v28, but the recovery file from https://gitlab.com/Neuer_User/PACEfied_AmazFit/wikis/permanent-install isn't working as it is expected.
The watch reboots, but the "#" sign is not available in the adb shell.
Also it gaves an error in fastboot mode (fastboot boot recovery.img(whatever the name is).
too many links, FAILED etc...
So i have Ubuntu18.10 and windows10 - no difference in both OS. Also I've tried on separated laptop (windows 10 again) with no positive effect.
Before 2.3.9.0 i was with version 26 and some previous ones (by permanent install, not only update via "sh" script in the shell) - No problems with all previous versions i've tested
So.. maybe there is a new bootloader and it needs a new recovery to temporary root the device. I don't know, but the normal installation isn't working anymore, so I've flashed clean 2.3.9.0 via Fastboot and I am staying in Stock ROM until something is changed.
Thank you if you have solution of this. I'll try it
post your fastboot getvar all output
1immortal said:
post your fastboot getvar all output
Click to expand...
Click to collapse
(bootloader) version-bootloader: U-Boot 2013.07-00146-g43d9f8c
(bootloader) version-baseband: N/A
(bootloader) version-hardware: V1.1 20130322
(bootloader) version-cdma: N/A
(bootloader) variant: watch
(bootloader) serialno: 16191828090306
(bootloader) product: watch
(bootloader) secure: no
(bootloader) unlocked: yes
(bootloader) uart-on: NO
(bootloader) partition-size:bootloader: 0x0000
(bootloader) partition-type:bootloader: emmc
(bootloader) partition-size:recovery: 0x1000
(bootloader) partition-type:recovery: emmc
(bootloader) partition-size:boot: 0x2000
(bootloader) partition-type:boot: emmc
(bootloader) partition-size:system: 0x3000
(bootloader) partition-type:system: ext4
(bootloader) partition-size:cache: 0x4000
(bootloader) partition-type:cache: ext4
(bootloader) partition-size:userdata: 0x5000
(bootloader) partition-type:userdata: ext4
(bootloader) max-download-size: 0x4000000
help me!!!
I did a youtube tutorial on how to install rom stock on my moto g7 power and now the phone does not exit fastboot mode.
Before the tutorial the phone worked normally, but I went to give a relative then prefer to install the rom stock factory, but it did not work.
In the installation of rom it said:
'' SMM: Android image roll back: 1.7 in red. ''
Now after Setup says:
'' SMM: Android image roll back: 5.7 in red
failed to validity boot image in purple
ERROR: Failed to pass validaton, backup to fastboot ''.
Tried to use Lenovo Moto Smart Assistant and this error:
'' Failed to match the connected device.
Please plug it out, and try again. ''
My device locked bootloader
my getvar all info:
C: \ Users \ Luanm \ Desktop \ platform-tools> fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: MBM-2.1-ocean_retail-a5c9d71-190702
(bootloader) product: ocean
(bootloader) board: ocean
(bootloader) secure: yes
(bootloader) hwrev: PVT1
(bootloader) radio: 4
(bootloader) storage-type: emmc
(bootloader) emmc: 32GB SAMSUNG GD6BMB RV = 08 PV = 01 FV = 0000000000000001
(bootloader) ram: 3GB SAMSUNG LP3 DIE = 8Gb M5 = 01 M6 = 06 M7 = 00 M8 = 5F
(bootloader) cpu: SDM632
(bootloader) serialno: ZF5225C2PW
(bootloader) cid: 0x0032
(bootloader) channelid: 0x19
(bootloader) uid: 3B8FE9F300000000000000000000
(bootloader) securestate: oem_locked
(bootloader) iswarrantyvoid: no
(bootloader) max-download-size: 536870912
(bootloader) reason: Fall-through from normal boot mode
(bootloader) imei: 354128100724492
(bootloader) meid:
(bootloader) date: 01-24-2019
(bootloader) sku: XT1955-1
(bootloader) carrier_sku: XT1955-1
(bootloader) battid: SB18C28956
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Mon Aug 5 22:26:10 UTC 2019"
(bootloader) ro.build.fingerprint [0]: motorola / ocean_t / ocean_t: 9 / PPOS29.
(bootloader) ro.build.fingerprint [1]: 114-134-2 / 0d27: user / release-keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full [0]: Blur_Version.29.281.2.ocean.retai
(bootloader) ro.build.version.full [1]: l.en.US
(bootloader) ro.build.version.qcom: LA.UM.7.6.2.r1-04600-89xx.0
(bootloader) version-baseband: <not found>
(bootloader) kernel.version [0]: Linux version 4.9.112-perf + (hudsoncm @ il
(bootloader) kernel.version [1]: clbld34) (gcc version 4.9.x 20150123 (pr
(bootloader) kernel.version [2]: erelease) (GCC)) # 1 SMP PREEMPT Sun Aug
(bootloader) kernel.version [3]: 4 11:49:12 CDT 2019
(bootloader) sbl1.git: MBM-2.1-ocean_retail-b508f3a-190702
(bootloader) rpm.git: MBM-2.1-ocean_retail-22daab3-190702
(bootloader) tz.git: MBM-2.1-ocean_retail-8798b8e-dirty-190702
(bootloader) devcfg.git: MBM-2.1-ocean_retail-8798b8e-dirty-190702
(bootloader) keymaster.git: MBM-2.1-ocean_retail-8798b8e-dirty-190702
(bootloader) cmnlib.git: MBM-2.1-ocean_retail-8798b8e-dirty-190702
(bootloader) cmnlib64.git: MBM-2.1-ocean_retail-8798b8e-dirty-190702
(bootloader) prov.git: MBM-2.1-ocean_retail-8798b8e-dirty-190702
(bootloader) aboot.git: MBM-2.1-ocean_retail-a5c9d71-190702
(bootloader) frp-state: no protection (0)
(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.083s
Help me please!!!!!!!!!
English is not my native language. :Boa:
You probably tried to downgrade or update with a wrong channel firmware with your oem locked. You can't do that. You'll need install the same firmware (can be a up version) and channel (retbr) that you're using before.
mirrors.lolinet.com/software/windows/Motorola/RSDLite/6.2.4/
mirrors.lolinet.com/firmware/moto/ocean/official/RETBR/
MurkBRA said:
You probably tried to downgrade or update with a wrong channel firmware with your oem locked. You can't do that. You'll need install the same firmware (can be a up version) and channel (retbr) that you're using before.
mirrors.lolinet.com/software/windows/Motorola/RSDLite/6.2.4/
mirrors.lolinet.com/firmware/moto/ocean/official/RETBR/
Click to expand...
Click to collapse
Thanks for the answer.
I tried to do what you told me but it did not work, I saw that when I button to install rom stock appears the error in '' boot.img '' and '' dtbo.img ''. I used rom Retail and RETBR but neither were.
I even modified flashfile to remove the installation of boot.img and dtbo.img but it didn't work out.
at the end of the reboot appears written:
Start Up Failed:
Your device didn't start up successfully.
Use the Software Repair Assistant on computer to repair your device.
Connect your device to your computer to get the software repair Assistant.
AP Fastboot Flash Mode (Secure)
SSM: Android image roll back: 5,7
failed to validade boot image
ERROR: failed to pass validaton. backup to fastboot
If you had the newer version of August you have to wait for the new firmware to come out, PPO29.114-134-2. So far, not available for download.
MurkBRA said:
If you had the newer version of August you have to wait for the new firmware to come out, PPO29.114-134-2. So far, not available for download.
Click to expand...
Click to collapse
thank you, when you have released this newer version I will install and talk if it worked.
Good news, there's a new release today:
mirrors.lolinet.com/firmware/moto/ocean/official/RETBR/
Download the RSD Lite and just flash the firmware.
MurkBRA said:
Good news, there's a new release today:
mirrors.lolinet.com/firmware/moto/ocean/official/RETBR/
Download the RSD Lite and just flash the firmware.
Click to expand...
Click to collapse
Thank you very much, I did what I said about using rsd lite and the new rom and managed to resurrect my cell phone. :victory:
Hola amigos.. tengo el mismo problema con mi moto G7 Power XT1955-2 en el link que dejaron solo vi la Version XT1955-1 hay algun problema si intento instalar esa que esta publicada???
Start Up Failed:
Your device didn't start up successfully.
...
Blocked into fastboot - Bootloader logs after wrong firmware adb flashing.
Flashed the android 10 update via lenovo moto smart assistant, it worked, after that it wouldn't recognise my phone, had the boot message "Your device has failed verification and may not work properly" and I tried to get rid of it plus that android 10 looked laggy in comparison with android 9, so i tried to flash the lastest android 9 rom so I bricked my phone. Tried to flash the android 10 rom available here and every rom I found for my phone. My bootloader is locked, i cannot unlock it bc i forgot to unlock oem and I'm stuck with the bricked phone. Tried to flash via RSD Lite, didn't recognise, flashed via adb, via Moto Flash Tool, tried everything. I know it could be blankflashed via EDL Mode, but I cannot get it in EDL mode, i don't have an EDL cable, i can't pin or i don't know how to short-circuit the pinpoint and don't have the tools to disassemble the phone. Please help me, I bought this phone like a week ago and I bricked it in the third day. Thank you very much!
Info form fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: MBM-2.1-deen_retail-c30fda1-200130
(bootloader) product: deen
(bootloader) board: deen
(bootloader) secure: yes
(bootloader) hwrev: PVT2
(bootloader) radio: 7
(bootloader) storage-type: emmc
(bootloader) emmc: 32GB SAMSUNG GD6BMB RV=08 PV=01 FV=0000000000000001
(bootloader) ram: 3GB SAMSUNG LP3 DIE=8Gb M5=01 M6=06 M7=00 M8=5F
(bootloader) cpu: MSM8953
(bootloader) serialno: ZY326936FS
(bootloader) cid: 0x0032
(bootloader) channelid: 0x00
(bootloader) uid: 01EF607800000000000000000000
(bootloader) securestate: oem_locked
(bootloader) iswarrantyvoid: no
(bootloader) max-download-size: 534773760
(bootloader) reason: Fall-through from normal boot mode
(bootloader) imei: 359548095218017
(bootloader) meid:
(bootloader) date: 06-18-2019
(bootloader) sku: XT1941-4
(bootloader) carrier_sku: XT1941-4
(bootloader) battid: SB18C30734
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Tue Mar 31 11:14:27 UTC 2020"
(bootloader) ro.build.fingerprint[0]: motorola/deen/deen_sprout:10/QPK30
(bootloader) ro.build.fingerprint[1]: .54-22/6add:user/release-keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full: <not found>
(bootloader) ro.build.version.qcom: LA.UM.8.6.r1-02600-89xx.0
(bootloader) version-baseband: M8953_37.155.02.28R DEEN_APACDSDS_CUST
(bootloader) kernel.version[0]: Linux version 3.18.124-perf-gb0c3168-dir
(bootloader) kernel.version[1]: ty ([email protected]) (gcc version 4
(bootloader) kernel.version[2]: .9.x 20150123 (prerelease) (GCC) ) #1 SM
(bootloader) kernel.version[3]: P PREEMPT Thu Jan 30 10:24:24 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-c30fda1-200130
(bootloader) frp-state: protected (77)
(bootloader) ro.carrier: reteu
(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.180s
Thank you!
claudiusuflea said:
Start Up Failed:
Your device didn't start up successfully.
...
Blocked into fastboot - Bootloader logs after wrong firmware adb flashing.
Flashed the android 10 update via lenovo moto smart assistant, it worked, after that it wouldn't recognise my phone, had the boot message "Your device has failed verification and may not work properly" and I tried to get rid of it plus that android 10 looked laggy in comparison with android 9, so i tried to flash the lastest android 9 rom so I bricked my phone. Tried to flash the android 10 rom available here and every rom I found for my phone. My bootloader is locked, i cannot unlock it bc i forgot to unlock oem and I'm stuck with the bricked phone. Tried to flash via RSD Lite, didn't recognise, flashed via adb, via Moto Flash Tool, tried everything. I know it could be blankflashed via EDL Mode, but I cannot get it in EDL mode, i don't have an EDL cable, i can't pin or i don't know how to short-circuit the pinpoint and don't have the tools to disassemble the phone. Please help me, I bought this phone like a week ago and I bricked it in the third day. Thank you very much!
Info form fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: MBM-2.1-deen_retail-c30fda1-200130
(bootloader) product: deen
(bootloader) board: deen
(bootloader) secure: yes
(bootloader) hwrev: PVT2
(bootloader) radio: 7
(bootloader) storage-type: emmc
(bootloader) emmc: 32GB SAMSUNG GD6BMB RV=08 PV=01 FV=0000000000000001
(bootloader) ram: 3GB SAMSUNG LP3 DIE=8Gb M5=01 M6=06 M7=00 M8=5F
(bootloader) cpu: MSM8953
(bootloader) serialno: ZY326936FS
(bootloader) cid: 0x0032
(bootloader) channelid: 0x00
(bootloader) uid: 01EF607800000000000000000000
(bootloader) securestate: oem_locked
(bootloader) iswarrantyvoid: no
(bootloader) max-download-size: 534773760
(bootloader) reason: Fall-through from normal boot mode
(bootloader) imei: 359548095218017
(bootloader) meid:
(bootloader) date: 06-18-2019
(bootloader) sku: XT1941-4
(bootloader) carrier_sku: XT1941-4
(bootloader) battid: SB18C30734
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Tue Mar 31 11:14:27 UTC 2020"
(bootloader) ro.build.fingerprint[0]: motorola/deen/deen_sprout:10/QPK30
(bootloader) ro.build.fingerprint[1]: .54-22/6add:user/release-keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full: <not found>
(bootloader) ro.build.version.qcom: LA.UM.8.6.r1-02600-89xx.0
(bootloader) version-baseband: M8953_37.155.02.28R DEEN_APACDSDS_CUST
(bootloader) kernel.version[0]: Linux version 3.18.124-perf-gb0c3168-dir
(bootloader) kernel.version[1]: ty ([email protected]) (gcc version 4
(bootloader) kernel.version[2]: .9.x 20150123 (prerelease) (GCC) ) #1 SM
(bootloader) kernel.version[3]: P PREEMPT Thu Jan 30 10:24:24 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-c30fda1-200130
(bootloader) frp-state: protected (77)
(bootloader) ro.carrier: reteu
(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.180s
Thank you!
Click to expand...
Click to collapse
You cannot downgrade firmware with a locked bootloader.
There is no Android 10 for Dean/RetEU
https://mirrors.lolinet.com/firmware/moto/deen/official/RETEU/
There will be no fix until there is Android 10 firmware for your device.
sd_shadow said:
You cannot downgrade firmware with a locked bootloader.
There is no Android 10 for Dean/RetEU
https://mirrors.lolinet.com/firmware/moto/deen/official/RETEU/
There will be no fix until there is Android 10 firmware for your device.
Click to expand...
Click to collapse
Also tried the beta for android 10 for deen-reteu, retail, retbr, and everything I found on the internet, didn't work, once android 10 stable for reteu would roll out is this phone fixable by the fastboot flashing method?
Also LMSA deleted my ro.build.version.full, it appears null on the getvar
claudiusuflea said:
Also tried the beta for android 10 for deen-reteu, retail, retbr, and everything I found on the internet, didn't work, once android 10 stable for reteu would roll out is this phone fixable by the fastboot flashing method?
Also LMSA deleted my ro.build.version.full, it appears null on the getvar
Click to expand...
Click to collapse
You may have flashed so many incompatible versions there is no fixing
Sent from my ocean using XDA Labs
sd_shadow said:
You may have flashed so many incompatible versions there is no fixing
Sent from my ocean using XDA Labs
Click to expand...
Click to collapse
I guess i have to wait or take it to a technician if the stable android 10 won't work, my wrong I didn't unlock the bootloader. Thank you very much!
sd_shadow said:
you cannot downgrade firmware with a locked bootloader.
There is no android 10 for dean/reteu
https://mirrors.lolinet.com/firmware/moto/deen/official/reteu/
there will be no fix until there is android 10 firmware for your device.
Click to expand...
Click to collapse
reteu got 10
there was 1 more ota after that for march update
n1kolaa said:
reteu got 10
there was 1 more ota after that for march update
Click to expand...
Click to collapse
Ok, do you have a copy of the firmware?
I haven't seen it.
Sent from my ali using XDA Labs
sd_shadow said:
Ok, do you have a copy of the firmware?
I haven't seen it.
Sent from my ali using XDA Labs
Click to expand...
Click to collapse
Didnt saved it, can provide fw id.
edit:
n1kolaa said:
Didnt saved it, can provide fw id.
edit:
Click to expand...
Click to collapse
also new LSMA version, it did recognise my phone now, but still after rescue it would have the same error
also we have android 10 roms on lolinet
trying the reteu android 10 from lolinet as last try
claudiusuflea said:
also new LSMA version, it did recognise my phone now, but still after rescue it would have the same error
also we have android 10 roms on lolinet
trying the reteu android 10 from lolinet as last try
Click to expand...
Click to collapse
Dead. Nothing worked again. So the phone is doomed, I will try once I can to take it to a gsm. It's the emmc partition which causes this problem.
Always unlock bootloader or at least enable oem unlock in developer settings before messing with firmwares (specially when downgrading). You got a really expensive papper weight.
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