Related
Dear all,
I have a question about Android N 7.0, what time will XT1650 - 03 RETEU stock firmware be released ?
Due to in this share drive: https://firmware.center/firmware/Motorola/Moto Z/Stock/XT1650-03/
Many of devices' firmware are released, like RETUS, RETMX ROGERS and so on, but I cannot find any about EU, my device is British Version.
I also searched lot of forums, in China or other region, but still have not.
I want to flash the full firmware.
Thank you.
any one knows the one I have to use for the unlocked version running on t-mobil?
Thanks
If somebody comes up with the firmware, I pledge €10 for beer via PayPal . Need to relock my bootloader after a dual SIM upgrade
apocalypse_bg said:
If somebody comes up with the firmware, I pledge €10 for beer via PayPal . Need to relock my bootloader after a dual SIM upgrade
Click to expand...
Click to collapse
Lol
What exactly package you want?
What's your blur version?
Goto bootloader, connect to pc and :
"fastboot getvar all"
Already went through your site, maybe I've done something wrong, as I found only the OTAs
It's reported as Sheridan, though it's actually a Griffin as I followed this guide for enabling the second SIM on an EU XT1650-03.
The FW is currently NPL26.118-20. Maybe I could get away with just flashing boot, recovery, oem to achieve the bootloader relocking..
Code:
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) version: 0.5
(bootloader) version-bootloader: moto-msm8996-91.07
(bootloader) product: sheridan
(bootloader) board: sheridan
(bootloader) secure: yes
(bootloader) hwrev: P3B
(bootloader) radio: 2
(bootloader) storage-type: ufs
(bootloader) ufs: 32GB SAMSUNG KLUBG4G1CE-B0B1 FV=0800
(bootloader) ram: 4GB SAMSUNG LP4 DIE=8Gb M5=01 M6=05 M7=00 M8=08
(bootloader) cpu: MSM8996
(bootloader) cid: 0x0032
(bootloader) channelid: 0x40
(bootloader) uid: 5674E70400000000000000000000
(bootloader) securestate: flashing_unlocked
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 536870912
(bootloader) reason: Volume down key pressed
(bootloader) imei: 358180071434300
(bootloader) meid:
(bootloader) date: 12-30-2016
(bootloader) sku: XT1650-03
(bootloader) battid:
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Thu Jan 1 0: 3:18 UTC 1970"
(bootloader) ro.build.fingerprint: <not found>
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full: <not found>
(bootloader) ro.build.version.qcom: LA.UM.5.6.r1-03800-89xx.0
(bootloader) version-baseband: <not found>
(bootloader) kernel.version[0]: Linux version 3.18.31-perf-g3b78496-0000
(bootloader) kernel.version[1]: 5-ge5590f6 ([email protected]) (gcc ver
(bootloader) kernel.version[2]: sion 4.9 20150123 (prerelease) (GCC) ) #
(bootloader) kernel.version[3]: 1 SMP PREEMPT Mon Jul 3 07:56:13 CDT 201
(bootloader) kernel.version[4]: 7
(bootloader) xbl.git: git=MBM-NG-V91.07-0-gd081b7e
(bootloader) rpm.git: git=684d06d
(bootloader) tz.git: git=9b7ad76-dirty
(bootloader) hyp.git: git=9b7ad76-dirty
(bootloader) devcfg.git: git=9b7ad76-dirty
(bootloader) keymaster.git: git=9b7ad76-dirty
(bootloader) cmnlib.git: git=9b7ad76-dirty
(bootloader) cmnlib64.git: git=9b7ad76-dirty
(bootloader) prov.git: git=9b7ad76-dirty
(bootloader) pmic.git: git=MBM-NG-V91.07-0-gd081b7e
(bootloader) aboot.git: git=MBM-NG-V91.07-0-g3c86d99
(bootloader) qe: qe 0/0
(bootloader) frp-state: no protection (0)
(bootloader) ro.carrier: reteu
all: listed above
finished. total time: 0.075s
apocalypse_bg said:
Already went through your site, maybe I've done something wrong, as I found only the OTAs
It's reported as Sheridan, though it's actually a Griffin as I followed this guide for enabling the second SIM on an EU XT1650-03.
The FW is currently NPL26.118-20. Maybe I could get away with just flashing boot, recovery, oem to achieve the bootloader relocking..
Click to expand...
Click to collapse
Yes it's only OTA
I can give you all boot and recovery images but you destroyed your blurversion as i can see in your getvar so not sure it works
Do you remember what was your firmware version when you unlocked bootloader and enabled second Sim?
erfanoabdi said:
Yes it's only OTA
I can give you all boot and recovery images but you destroyed your blurversion as i can see in your getvar so not sure it works
Do you remember what was your firmware version when you unlocked bootloader and enabled second Sim?
Click to expand...
Click to collapse
Unfortunately, I didn't check that, as from my reading of the guide it should've been safe and easy to relock.. And no idea how I've messed the fw version by only changing the hex value and flashing TWRP.... everything else stock. I have TWRP backups of boot, recovery, system_image, system and firmware, is it possible to extract the value somehow from there?
ADB reports Blur_Version.26.51.19.griffin.retail.en.US from fully booted Android with reteu carrier.
I need the firmware for Moto Z xt1605-03
This is the blur version : Blur_Version.26.211.5.griffin.ret
Thanks in advance
I hope you guys know there is an official portal for all the Moto firmwares released. Just google it and you'll find it. I cannot share it because external links are not allowed.
Hey guys,
my Wifi and BT are somehow broken and are working only occassionally. I flashed back to 7.0 and rerun all the OTAs available with the OTA Downloader. After that an "offiicial" System Update appeared and I also installed that successfully. No change. Still having issues with my WiFi and BT.
Did I flash the wrong Firmware so the modem partition is faulty? Is this even possible as I was able to relock my bootloader? Could anybody provide a stock modem for NPLS26.118-20-5-11 for RETEU? Or should I flash the 7.0 modem without patches? Or even the 6.0 RETEU modem?
If it helps here is my fastboot getvar all
Code:
(bootloader) version: 0.5
(bootloader) version-bootloader: moto-msm8996-91.08
(bootloader) product: sheridan
(bootloader) board: sheridan
(bootloader) secure: yes
(bootloader) hwrev: P3B
(bootloader) radio: 2
(bootloader) storage-type: ufs
(bootloader) ufs: 32GB SAMSUNG KLUBG4G1CE-B0B1 FV=0800
(bootloader) ram: 4GB SKHYNIX LP4 DIE=8Gb M5=06 M6=03 M7=00 M8=08
(bootloader) cpu: MSM8996
(bootloader) serialno: ZY223LZ4TZ
(bootloader) cid: 0x0032
(bootloader) channelid: 0x40
(bootloader) uid: 1F62096E00000000000000000000
(bootloader) securestate: flashing_unlocked
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 536870912
(bootloader) reason: Reboot mode set to fastboot
(bootloader) imei: 358180000000000 (edited)
(bootloader) meid:
(bootloader) date: 10-12-2016
(bootloader) sku: XT1650-03
(bootloader) battid:
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Thu Jan 1 2:16:30 UTC 1970"
(bootloader) ro.build.fingerprint[0]: motorola/griffin/griffin:7.1.1/NPL
(bootloader) ro.build.fingerprint[1]: S26.118-20-5-11/14:user/release-ke
(bootloader) ro.build.fingerprint[2]: ys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.26.241.14.griffin.re
(bootloader) ro.build.version.full[1]: tail.en.US
(bootloader) ro.build.version.qcom: LA.UM.5.6.r1-03800-89xx.0
(bootloader) version-baseband: M8996_1239.53.01.126.04.01R SRS
(bootloader) kernel.version[0]: Linux version 3.18.31-perf-g0444692 (hud
(bootloader) kernel.version[1]: [email protected]) (gcc version 4.9 201501
(bootloader) kernel.version[2]: 23 (prerelease) (GCC) ) #1 SMP PREEMPT W
(bootloader) kernel.version[3]: ed Dec 6 04:07:21 CST 2017
(bootloader) xbl.git: git=MBM-NG-V91.08-0-g2e876a3
(bootloader) rpm.git: git=684d06d
(bootloader) tz.git: git=9b7ad76-dirty
(bootloader) hyp.git: git=9b7ad76-dirty
(bootloader) devcfg.git: git=9b7ad76-dirty
(bootloader) keymaster.git: git=9b7ad76-dirty
(bootloader) cmnlib.git: git=9b7ad76-dirty
(bootloader) cmnlib64.git: git=9b7ad76-dirty
(bootloader) prov.git: git=9b7ad76-dirty
(bootloader) pmic.git: git=MBM-NG-V91.08-0-g2e876a3
(bootloader) aboot.git: git=MBM-NG-V91.08-0-gab592a8
(bootloader) qe: qe 0/1
(bootloader) frp-state: no protection (77)
(bootloader) ro.carrier: reteu
Thanks in advance.
stunner2002 said:
Hey guys,
my Wifi and BT are somehow broken and are working only occassionally. I flashed back to 7.0 and rerun all the OTAs available with the OTA Downloader. After that an "offiicial" System Update appeared and I also installed that successfully. No change. Still having issues with my WiFi and BT.
Did I flash the wrong Firmware so the modem partition is faulty? Is this even possible as I was able to relock my bootloader? Could anybody provide a stock modem for NPLS26.118-20-5-11 for RETEU? Or should I flash the 7.0 modem without patches? Or even the 6.0 RETEU modem?
If it helps here is my fastboot getvar all
Code:
(bootloader) version: 0.5
(bootloader) version-bootloader: moto-msm8996-91.08
(bootloader) product: sheridan
(bootloader) board: sheridan
(bootloader) secure: yes
(bootloader) hwrev: P3B
(bootloader) radio: 2
(bootloader) storage-type: ufs
(bootloader) ufs: 32GB SAMSUNG KLUBG4G1CE-B0B1 FV=0800
(bootloader) ram: 4GB SKHYNIX LP4 DIE=8Gb M5=06 M6=03 M7=00 M8=08
(bootloader) cpu: MSM8996
(bootloader) serialno: ZY223LZ4TZ
(bootloader) cid: 0x0032
(bootloader) channelid: 0x40
(bootloader) uid: 1F62096E00000000000000000000
(bootloader) securestate: flashing_unlocked
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 536870912
(bootloader) reason: Reboot mode set to fastboot
(bootloader) imei: 358180000000000 (edited)
(bootloader) meid:
(bootloader) date: 10-12-2016
(bootloader) sku: XT1650-03
(bootloader) battid:
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Thu Jan 1 2:16:30 UTC 1970"
(bootloader) ro.build.fingerprint[0]: motorola/griffin/griffin:7.1.1/NPL
(bootloader) ro.build.fingerprint[1]: S26.118-20-5-11/14:user/release-ke
(bootloader) ro.build.fingerprint[2]: ys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.26.241.14.griffin.re
(bootloader) ro.build.version.full[1]: tail.en.US
(bootloader) ro.build.version.qcom: LA.UM.5.6.r1-03800-89xx.0
(bootloader) version-baseband: M8996_1239.53.01.126.04.01R SRS
(bootloader) kernel.version[0]: Linux version 3.18.31-perf-g0444692 (hud
(bootloader) kernel.version[1]: [email protected]) (gcc version 4.9 201501
(bootloader) kernel.version[2]: 23 (prerelease) (GCC) ) #1 SMP PREEMPT W
(bootloader) kernel.version[3]: ed Dec 6 04:07:21 CST 2017
(bootloader) xbl.git: git=MBM-NG-V91.08-0-g2e876a3
(bootloader) rpm.git: git=684d06d
(bootloader) tz.git: git=9b7ad76-dirty
(bootloader) hyp.git: git=9b7ad76-dirty
(bootloader) devcfg.git: git=9b7ad76-dirty
(bootloader) keymaster.git: git=9b7ad76-dirty
(bootloader) cmnlib.git: git=9b7ad76-dirty
(bootloader) cmnlib64.git: git=9b7ad76-dirty
(bootloader) prov.git: git=9b7ad76-dirty
(bootloader) pmic.git: git=MBM-NG-V91.08-0-g2e876a3
(bootloader) aboot.git: git=MBM-NG-V91.08-0-gab592a8
(bootloader) qe: qe 0/1
(bootloader) frp-state: no protection (77)
(bootloader) ro.carrier: reteu
Thanks in advance.
Click to expand...
Click to collapse
Hi I found this folder, hope it can help https://mirrors.lolinet.com/firmware/moto/griffin/official/RETUS/
Does anyone have the full official stock ROM for INDIA? need android 7.1.1 or oreo
Hello everyone,
My Moto Z TX1650 was updated automatically by OTA, restart by itself and - bricked. (awesome job, Moto.)
I was going through a maze of topics until I found the blankflash script that actually owrked and made my phone trun on in fastboot again. It was in black screen no signal whatsoever even for charger - I though it was dead, but aint. (i´m posting here the blankflash used so anyone is facing the very same issue)
script to bring back your phone from dead - https://forum.xda-developers.com/attachment.php?attachmentid=4372614&d=1514473892
But now my phone is oem_locked, I dont have system (ROM) functional to enable oem in developer mode, and I cannot jump into any menu - Recovery Mode, for example, to try t o bootup using ADB, for there´s nothing in those partitions.
Recovery Mode
Startup Failed
Your device didnt start up correctly.
I´m trying to use fastboot oem unlock, I have the code, but in the end asked me to unlock it in the system.
Well if I had a system to boot into, i wasnt even trying to unlock it.
Anyone got any suggestion on how to unlock my phone OEM through fastboot only?
Thank you all.
edit:
Fastboot reason: Failed to Initialize partition table
phone specs:
fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: moto-msm8996-91.08(*)
(bootloader) product: sheridan
(bootloader) board: sheridan
(bootloader) secure: yes
(bootloader) hwrev: P3B
(bootloader) radio: 2
(bootloader) storage-type: ufs
(bootloader) ufs: 64GB SAMSUNG KLUCG4J1CB-B0B1 FV=0800
(bootloader) ram: 4GB SAMSUNG LP4 DIE=8Gb M5=01 M6=05 M7=00 M8=08
(bootloader) cpu: MSM8996
(bootloader) serialno: 1f45b71
(bootloader) cid: 0x0032
(bootloader) channelid: 0x19
(bootloader) uid: 89F9DDB400000000000000000000
(bootloader) securestate: oem_locked
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 536870912
(bootloader) reason: Failed to initialize partition table
(bootloader) imei: 000000000000000
(bootloader) meid:
(bootloader) date: 01-01-1970
(bootloader) sku: 000000000000000
(bootloader) battid:
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time:
(bootloader) ro.build.fingerprint:
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full:
(bootloader) ro.build.version.qcom:
(bootloader) version-baseband:
(bootloader) kernel.version:
(bootloader) xbl.git: xbl.git
(bootloader) rpm.git: rpm.git
(bootloader) tz.git: tz.git
(bootloader) hyp.git: hyp.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) pmic.git: pmic.git
(bootloader) aboot.git: git=MBM-NG-V91.08-0-gab592a8
(bootloader) qe:
(bootloader) frp-state: no protection (err)
(bootloader) ro.carrier:
all: listed above
finished. total time: 0.079s
I have the same problem. I am following.
Daniel Nascimento said:
Hello everyone,
My Moto Z TX1650 was updated automatically by OTA, restart by itself and - bricked. (awesome job, Moto.)
I was going through a maze of topics until I found the blankflash script that actually owrked and made my phone trun on in fastboot again. It was in black screen no signal whatsoever even for charger - I though it was dead, but aint. (i´m posting here the blankflash used so anyone is facing the very same issue)
script to bring back your phone from dead - https://forum.xda-developers.com/attachment.php?attachmentid=4372614&d=1514473892
But now my phone is oem_locked, I dont have system (ROM) functional to enable oem in developer mode, and I cannot jump into any menu - Recovery Mode, for example, to try t o bootup using ADB, for there´s nothing in those partitions.
Recovery Mode
Startup Failed
Your device didnt start up correctly.
I´m trying to use fastboot oem unlock, I have the code, but in the end asked me to unlock it in the system.
Well if I had a system to boot into, i wasnt even trying to unlock it.
Anyone got any suggestion on how to unlock my phone OEM through fastboot only?
Thank you all.
edit:
Fastboot reason: Failed to Initialize partition table
phone specs:
fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: moto-msm8996-91.08(*)
(bootloader) product: sheridan
(bootloader) board: sheridan
(bootloader) secure: yes
(bootloader) hwrev: P3B
(bootloader) radio: 2
(bootloader) storage-type: ufs
(bootloader) ufs: 64GB SAMSUNG KLUCG4J1CB-B0B1 FV=0800
(bootloader) ram: 4GB SAMSUNG LP4 DIE=8Gb M5=01 M6=05 M7=00 M8=08
(bootloader) cpu: MSM8996
(bootloader) serialno: 1f45b71
(bootloader) cid: 0x0032
(bootloader) channelid: 0x19
(bootloader) uid: 89F9DDB400000000000000000000
(bootloader) securestate: oem_locked
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 536870912
(bootloader) reason: Failed to initialize partition table
(bootloader) imei: 000000000000000
(bootloader) meid:
(bootloader) date: 01-01-1970
(bootloader) sku: 000000000000000
(bootloader) battid:
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time:
(bootloader) ro.build.fingerprint:
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full:
(bootloader) ro.build.version.qcom:
(bootloader) version-baseband:
(bootloader) kernel.version:
(bootloader) xbl.git: xbl.git
(bootloader) rpm.git: rpm.git
(bootloader) tz.git: tz.git
(bootloader) hyp.git: hyp.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) pmic.git: pmic.git
(bootloader) aboot.git: git=MBM-NG-V91.08-0-gab592a8
(bootloader) qe:
(bootloader) frp-state: no protection (err)
(bootloader) ro.carrier:
all: listed above
finished. total time: 0.079s
Click to expand...
Click to collapse
Sorry but you may have to change your motherboard because your I'm is corrupted
You must flash a Fastboot Image with the System that was last installed on your smartphone with the right Bootloader Version or upgrade your Bootloader with the upcoming Oreo Fastboot Image.
I have the same proble
i have the same problem any sugestión?
SOLUTION
INSTALL THE OFFICIAL FIRMWARE THAT YOU HAD BEFORE UPDATING OR THE MOST CURRENT FIRMWARE, WITH THAT IT IS SOLVED
IN THE PAGE "FIRMWARE CENTER"
sorry for my bad english
I'll try but always get error on adb and RSD LITE say error phone returned fail
Please I need help. I flashed a RETUS oreo firmware over my RETEU 7.0 april 2017 update.
The upgrade was successful using the official full firmware but it gets to the stage where it encrypts the phone then it reboots and constantly gets in a reboot loop. I really need help as I have been searching for hours with no solution.
I downloaded and flashed XT1650-03_GRIFFIN_RETUS_8.0.0_OPL27.76-51_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
Device is locked and I enabled oem unlock prior to update but i didn't unlock bootloader. I wish I had. Now I'm stuck.
I know I made mistake and I really need help. I would appreciate any help rendered
The flashing was successful. I think I shouldn't have flashed the gpt.bin file. Maybe thats the cause of the problem?
Please I am in desperate need for solution.
I got this using fastboot
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot getvar all
< waiting for any device >
(bootloader) version: 0.5
(bootloader) version-bootloader: moto-msm8996-92.03
(bootloader) product: sheridan
(bootloader) board: sheridan
(bootloader) secure: yes
(bootloader) hwrev: P3B
(bootloader) radio: 2
(bootloader) storage-type: ufs
(bootloader) ufs: 32GB SAMSUNG KLUBG4G1CE-B0B1 FV=0800
(bootloader) ram: 4GB SKHYNIX LP4 DIE=8Gb M5=06 M6=03 M7=00 M8=08
(bootloader) cpu: MSM8996
(bootloader) serialno: ZY223MT6CR
(bootloader) cid: 0x0032
(bootloader) channelid: 0x40
(bootloader) uid: AAA5AE1400000000000000000000
(bootloader) securestate: oem_locked
(bootloader) iswarrantyvoid: no
(bootloader) max-download-size: 536870912
(bootloader) reason: Reboot mode set to fastboot
(bootloader) imei: 35xxxxxxxxxxxxxx
(bootloader) meid:
(bootloader) date: 10-17-2016
(bootloader) sku: XT1650-03
(bootloader) battid:
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Thu Jan 1 0:30:29 UTC 1970"
(bootloader) ro.build.fingerprint[0]: motorola/griffin/griffin:8.0.0/OPL
(bootloader) ro.build.fingerprint[1]: 27.76-51/58:user/release-keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.27.11.58.griffin.ret
(bootloader) ro.build.version.full[1]: ail.en.US
(bootloader) ro.build.version.qcom: LA.UM.6.6.r1-04400-89xx.0
(bootloader) version-baseband: <not found>
(bootloader) kernel.version[0]: Linux version 3.18.71-perf-g72b40d5 (hud
(bootloader) kernel.version[1]: [email protected]) (gcc version 4.9.x 2015
(bootloader) kernel.version[2]: 0123 (prerelease) (GCC) ) #1 SMP PREEMPT
(bootloader) kernel.version[3]: Mon Feb 26 05:47:32 CST 2018
(bootloader) xbl.git: git=MBM-NG-V92.03-0-gcdce58f
(bootloader) rpm.git: git=MBM-NG-V92.02-0-g722a114
(bootloader) tz.git: git=b5f954a-dirty
(bootloader) hyp.git: git=b5f954a-dirty
(bootloader) devcfg.git: git=b5f954a-dirty
(bootloader) keymaster.git: git=b5f954a-dirty
(bootloader) cmnlib.git: git=b5f954a-dirty
(bootloader) cmnlib64.git: git=b5f954a-dirty
(bootloader) prov.git: git=b5f954a-dirty
(bootloader) pmic.git: git=MBM-NG-V92.03-0-gcdce58f
(bootloader) aboot.git: git=MBM-NG-V92.03-0-gfb81184
(bootloader) qe: qe 0/0
(bootloader) frp-state: no protection (0)
(bootloader) ro.carrier: reteu
all: listed above
finished. total time: 0.164s
Click to expand...
Click to collapse
FINALLY FIXED AFTER 12HOURS.
I was lucky because the phone came on and I quickly enabled "oem unlock" and unlocked bootloader then flashed stock 7.1.1 suing fastboot
It worked like a charm afterwards. Maybe the software 8.0.0 is too much for the phone.
Thanks for the support.
http://erfanoabdi.000webhostapp.com....11.58.griffin.retail.en.US&carrier=reteu&sn= there is for you phone, try flashing that
eLaDiio said:
http://erfanoabdi.000webhostapp.com....11.58.griffin.retail.en.US&carrier=reteu&sn= there is for you phone, try flashing that
Click to expand...
Click to collapse
This is a 94.4mb update file. Please how is it going to work because the phone doesn't boot up?
I am in bigger trouble now. I flashed the zip and I have qhusb_bulk
sorry my bad, and try to reflash all again?
eLaDiio said:
sorry my bad, and try to reflash all again?
Click to expand...
Click to collapse
I have just flashed oreo blankflash to restore the device but still the same issue. It stays in a reboot loop. and sometimes the modem will disappear in the fastboot mode. I cant get the device to boot up. Please any help?
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